Hi fellows,
I contacted the Motorola support and they said that Vivo's Motorola RAZR is about to get an update to improve the cellphone performance. When it is ready, it will become available by OTA system.
Thanks,
Ronan.
Hello,
I got my phone on Vivo, and it came with version 651.73.240.XT910.Vivo.en.BR.
This version is very buggy and some bad localization, like for example the function to merge contacts was translated to "Conferência", wich means "Conference", and clearly does not have anything to do with "Merge".
I then used Motorola Software Update to download an update, and since it was failing to update the phone, I used RSD Lite to manually update it.
Now I am using 651.73.2062.XT910.Vino.en.BR, and the phone performance is much better, the localization is fixed but I still see some bugs with the camera app and 3G modem dropping data, but its still better than stock.
You say that this OTA will be appied on top of 2062, or maybe its the 2062 itself but an OTA version?
Or its a complete new OTA that can be applied on top of 2062 and 240?
casaroli said:
Hello,
I got my phone on Vivo, and it came with version 651.73.240.XT910.Vivo.en.BR.
This version is very buggy and some bad localization, like for example the function to merge contacts was translated to "Conferência", wich means "Conference", and clearly does not have anything to do with "Merge".
I then used Motorola Software Update to download an update, and since it was failing to update the phone, I used RSD Lite to manually update it.
Now I am using 651.73.2062.XT910.Vino.en.BR, and the phone performance is much better, the localization is fixed but I still see some bugs with the camera app and 3G modem dropping data, but its still better than stock.
You say that this OTA will be appied on top of 2062, or maybe its the 2062 itself but an OTA version?
Or its a complete new OTA that can be applied on top of 2062 and 240?
Click to expand...
Click to collapse
Hi fellow!
I'm pretty sure it will be 2062.
I haven't noticed that the version here on XDA is 2062. I thought it was 206 and, since mine is 240, then I hasn't updated
Can you help me to update my RAZR to 2062? I has a very big experience with Samsung devices, but to achieve it, I hard bricked my Galaxy TAB Since I really don't want to be without a cellphone and Samsung devices doesn't use fastboot, can you give some tips how can I flash this update by fastboot?
By the way, I have something that might be useful for Brazilian RAZR owners:
From Motorola support chat:
Marivaldo: A informação que temos é que será o primeiro aparelho Motorola a receber a versão 4.0 do android, até segundo semestre de 2012.
(The information available to us is that Motorola RAZR will be the first phone to receive android 4.0, which will happen until second semester 2012)
Ronan Jardim : nossa, muito bom!
Ronan Jardim : obrigado!
Ronan Jardim : então a Motorola do Brasil atualizará sim?
(Very good, thanks, so Motorola will update this device in Brazil also, won't it?)
Marivaldo: Sim, sem sobra de dúvidas.
Marivaldo: É uma atualização aguardada por todos.
(For sure, it is an update expected by everyone)
...
So, how much do you believe that?!
Ronan
Until second semester?
Oh, lord. If Moto keeps following their schedule the way they're doing now, it probably means we won't see this ICS update any time before october.
brunoerre said:
Until second semester?
Oh, lord. If Moto keeps following their schedule the way they're doing now, it probably means we won't see this ICS update any time before october.
Click to expand...
Click to collapse
Well, considering my past experience with Motorola Brazil, I'll be glad if Moto update RAZR no matter when
And also, I have lost faith in Motorola's schedules a long time ago
Nevermind
I managed to do that... very simple and straightforward...
I'm now with 2062 version that was build on Dec 6 (or 16 can't remember), the other was built on 20 Oct.
I'll post the differences I saw tomorrow.
Thanks,
Ronan
Ronis_BR said:
Nevermind
I managed to do that... very simple and straightforward...
I'm now with 2062 version that was build on Dec 6 (or 16 can't remember), the other was built on 20 Oct.
I'll post the differences I saw tomorrow.
Thanks,
Ronan
Click to expand...
Click to collapse
Would you mind to show how you managed to update? Appreciate that! Thanks!
njoismartguys said:
Would you mind to show how you managed to update? Appreciate that! Thanks!
Click to expand...
Click to collapse
Start here: ht tp: // direct.motorola.com/hellomoto/support/update/[/url]
select your country, then your carrier, or "retail" for retail version.
Download that software and *DO NOT INSTALL TO "c:\program files (x86)\motorola mobility\software update" because the file paths will get too long and you will have problems.
To avoid these long filepaths problems, install it to somewhere else shorter, like for example "c:\moto"
Run the software updater while connected to the Internet, connect your phone to the computer and follow the steps on the update.
The do not forget to root again
Good luck!
casaroli said:
Start here: ht tp: // direct.motorola.com/hellomoto/support/update/[/url]
select your country, then your carrier, or "retail" for retail version.
Download that software and *DO NOT INSTALL TO "c:\program files (x86)\motorola mobility\software update" because the file paths will get too long and you will have problems.
To avoid these long filepaths problems, install it to somewhere else shorter, like for example "c:\moto"
Run the software updater while connected to the Internet, connect your phone to the computer and follow the steps on the update.
The do not forget to root again
Good luck!
Click to expand...
Click to collapse
I wasn't able to perform the update with software update by motorola...
The only way possible was to use RSD Lite and fastboot files here.
Thanks!
Ronan
Ronis_BR said:
I haven't noticed that the version here on XDA is 2062. I thought it was 206 and, since mine is 240, then I hasn't updated
Click to expand...
Click to collapse
I was confused also when I first saw. Perhaps someone need to notify the EternityProject thread about the version number so it does not cause more confusion.
I still can't post to that thead , so maybe someone else could do it.
BTW, After the update, running Motorola Software Update does not update anymore, since we are already at the latest version.
I guess using Motorola Software Update is the safest way to upgrade and for sure it should not void your warranty.
Thanks
casaroli said:
I was confused also when I first saw. Perhaps someone need to notify the EternityProject thread about the version number so it does not cause more confusion.
I still can't post to that thead , so maybe someone else could do it.
BTW, After the update, running Motorola Software Update does not update anymore, since we are already at the latest version.
I guess using Motorola Software Update is the safest way to upgrade and for sure it should not void your warranty.
Thanks
Click to expand...
Click to collapse
Software Update will do exactly what RSD Lite and the fastboot files is doing. There isn't anyway to know which kind of method was used to update the cellphone. So, if you have a Vivo cellphone and flashed a Vivo stock ROM from here, if you don't do anything wrong, then you are "safe".
Ronis_BR said:
I wasn't able to perform the update with software update by motorola...
The only way possible was to use RSD Lite and fastboot files here.
Thanks!
Ronan
Click to expand...
Click to collapse
Did you install to the default location? Open the software update folder, find the ZIP and try to extract it, you will see that it will create an empty folder (with very long name), and will give an error to extract the file contents. Motorola Software Update just fails to install the update and does not describe the error. Using windows to extract, you should see the error.
Moving the whole software update folder to c:\moto should work, since the extraction works.
If it does not work, you can manually flash by RSD Lite, and use the downloaded zip in the software update folder.
casaroli said:
Did you install to the default location? Open the software update folder, find the ZIP and try to extract it, you will see that it will create an empty folder (with very long name), and will give an error to extract the file contents. Motorola Software Update just fails to install the update and does not describe the error. Using windows to extract, you should see the error.
Moving the whole software update folder to c:\moto should work, since the extraction works.
If it does not work, you can manually flash by RSD Lite, and use the downloaded zip in the software update folder.
Click to expand...
Click to collapse
I think that Motorola Software Upgrade doesn't need to extract update.zip. Normally, it is pushed to the phone and than extracted. If update.zip is extracted in Windows (NTFS partition) I think that it will have problems with permissions and links that must be defined in RAZR's ext3 partition.
But it is only my guess
I'm pretty sure that Software Updates (and RSD Lite) extracts the ZIP because I could see the empty folder created on the software update folder.
Also, the contents of the ZIP are not the actual files on the phone (i.e. the ext3 fs contents), they are flash images, like radio.img, filesystem image, webtop, and so on. Also, there is the file mapping so software update knows where to flash each image.
Extracting this file should not lead to any error on permissions.
I'm not at my computer right now, so I'm not able to extract the zip contents and post here. I could do it later.
casaroli said:
I'm pretty sure that Software Updates (and RSD Lite) extracts the ZIP because I could see the empty folder created on the software update folder.
Also, the contents of the ZIP are not the actual files on the phone (i.e. the ext3 fs contents), they are flash images, like radio.img, filesystem image, webtop, and so on. Also, there is the file mapping so software update knows where to flash each image.
Extracting this file should not lead to any error on permissions.
I'm not at my computer right now, so I'm not able to extract the zip contents and post here. I could do it later.
Click to expand...
Click to collapse
Yes, if it is images than you are right!
Unfortunately, I have already updated my RAZR, so we can't test it
Yes, I think you are right.
I saw the file in software upgrade's folder and it is the same file (same md5sum and name) I have flashed using RSD Lite 5.6.
Well, here the differences I saw:
- As casaroli commented, some translations were fixed.
- GPS is 100x faster. I think they really enable AGPS. I can see the option in GPS Status apk, which didn't exist before. In a cold start and using the network (AGPS), I got a satellite fix in less than 25 seconds inside my home (near a window obviously).
- The operational system is much more stable.
- I think (didn't test it) that WiFi connection is better.
- Windows Live apk is installed.
- Compass problem wasn't solved
It is a very good update, my RAZR is much more stable and I recommend to everyone who have a Vivo RAZR.
I won't explain how to use RSD Lite since you can brick your device. First, try what casaroli said and try to update by Software Upgrade by Motorola. It is the safest way always.
Now we have to see how can we flash android 2.3.6 here
casaroli said:
Start here: ht tp: // direct.motorola.com/hellomoto/support/update/[/url]
select your country, then your carrier, or "retail" for retail version.
Download that software and *DO NOT INSTALL TO "c:\program files (x86)\motorola mobility\software update" because the file paths will get too long and you will have problems.
To avoid these long filepaths problems, install it to somewhere else shorter, like for example "c:\moto"
Run the software updater while connected to the Internet, connect your phone to the computer and follow the steps on the update.
The do not forget to root again
Good luck!
Click to expand...
Click to collapse
Thanks! The ROM on the official ROM page from the development section has 2062 (as you figured already)
Ronis_BR said:
Now we have to see how can we flash android 2.3.6 here
Click to expand...
Click to collapse
Yes looking forward for this. Plainly I am so disappointed with Moto's update schedule for different regions. Thought Google acquisition would speed up the process, but doesn't seem like it.
MY I updated to 2.3.6
Update via RSD LITE
Man, can you please describe exactly what you did? Is your razr from vivo?
Thanks and great job!
Ronan
Sent from my XT910 using xda premium
Related
Hello everybody!
I am starting this new thread to try compile a simple to follow and reasonably written complete guide for rooting an Xperia Neo 2.3.3. I am doing this because, although there are enough information and software on this forum and on the internet in general, these are not really structured and gathered in a way that a non-experienced user (a.k.a. "noob") can easily manage, and the process of rooting 2.3.3. is a bit more complicated than 2.3.2 with Gingerbreak for instance.
This guide is for Xperia Neo running Android 2.3.3 with locked bootloader. Other devices with 2.3.3. might be rooted in a similar fashion.
Update: 2.3.4. for the Neo is out. Everything here still works as described with the difference that you get the latest 2.3.4 when updating OTA.
WARNING: some users reported that after downgrading from 2.3.4 to 2.3.2 in order to root, the battery meter showed 0%. I am not yet aware of a solution to this problem. So beware if your Neo already has the latest version.
Warning: Neither myself, nor anyone else but YOU is responsible if you damage your phone in any way or lose any information after trying to root your phone by folowing this guide! Also note that your warranty will expire when you root. However, unrooting should be possible, in principle.
--- Guide start ---
1. Back up your data. You could do this using an app called Backup Master from the Android Market. Additionally, I had my contacts and calendar synchronized with my Google account. SMS messages were not properly backed up, but I didn't care about them anyway. If you do care, you might want to save them to your SD card, using the built-in option or just use another app. Also make sure your battery is at least half charged before starting.
2. Download FlashTool from here or directly here. Install it by simply unpacking it somewhere.
3. Download the generic firmware 2.3.2 from here or directly here. You do this because Gingerbreak (will come to that) uses a security vulnerability to gain root rights in 2.3.2. that has been fixed with the new 2.3.3. Extract the .ftf file from the .rar archive you just downloaded to the sub-folder "firmwares" of your Flashtools installation from step 2. (You might need WinRar for extracting)
4. Go to your Flashtool installation to the folder "drivers" and install ggsetup-2.2.0.10.exe. Download the USB drivers for your Neo from here. Unpack the contents of the archived folder "amd64" (if on Windows 64) or "i386" (if on Windows 32) to the folder "amd64" or "x86" respectively of the installation folder of Gordons Gate. The path might be something like "c:\Program Files (x86)\Sony Ericsson\Gordons Gate\". Run DPInst.exe to install the drivers.
Alternatively to this step, I think you could install the drivers by just installing PCCompanion and plugging in your phone, but I did it the hard way.
5. Run the file X10FlashTool.exe; click Flash; you should see the firmware you downloaded in step 3 in the appearing window if you extracted it correctly; click OK (I recommend you leave the option "wipe data" checked, although some users reported that it worked for them even without wiping the data); follow the instructions (note that the back button on the Neo is on the other side as pictured); the flashing should take no more than a couple of minutes; start your phone - this will take a bit longer the first time. If after the reboot the battery meter is showing 1%, shut down and take out the battery for a minute, then boot up again.
6. Get Gingerbreak from here of directly here. This is the exploit that actually roots the phone. Copy it to your phone and install. You can do this a number of ways. For example: install ES File Explorer from the Android Market, access your PC via WLAN with it and install it directly from there. You will be prompted to change the setting to allow the installation of apps from unknown sources in case you didn't change it already. Also allow USB-debugging in the same settings menu under "developer".
7. Run Gingerbreak and tap "root device". This shouldn't take more than a couple of minutes, although some users reported it taking hours. If it is taking very long, you might want to try inserting another SD card and repeating the attempt. When it's done, it will reboot. Now you have a rooted 2.3.2. You can check this by installing the app "root checker" from the Android Market. When you start "root checker" you will be asked by an app called "superuser" if you want to grant root access to this program. This "superuser" app was installed by Gingerbreak after rooting and manages which program has root permissions.
8. Now before doing anything, go to settings>info>software update> update now and get the new Android 2.3.3 OTA (= over the air, i.e. via WLAN or 3G). Do not do this via your PC, because you will unroot the phone. There have been a lot of problems reported with this step. If right after you tap "update now" you get the message "unable to connect" try shutting down, waiting a minute and booting up again or also try setting the date and time to the correct values, in case you have something like 01 Jan 1980. Other users said, it just took a lot of attempts before it worked and that the problem might be with the SonyEricsson servers... If after the update was downloaded you get some kind of error message like "cannot update" it might be because you did some changes to system files or possibly you used a non-original firmware in step 3.
After the update was done, check again for root access with the "root checker"
9. Restore the data you backed up in step 1 and enjoy.
Update: I managed to update to 2.3.4. Unfortunately I could not simply update OTA from my rooted 2.3.3. I kept getting an error message after downloading the update, probably because I had changed system files. So I did all the above steps again, with the difference that in step 8 I got the 2.3.4. from the SE server.
--- Guide end ---
Please click the Thanks button and/or reply to this post and write your own experience or suggestions/corrections.
A similar guide/tutorial/how-to has been posted before (Here). Perhaps not as detailed as yours but nonetheless, it's been done. And do give credit to the necessary people.
But good job on taking the time and writing this up. I'm sure a lot of Neo users will appreciate it.
Cheers!
xtacy! said:
A similar guide/tutorial/how-to has been posted before (Here). Perhaps not as detailed as yours but nonetheless, it's been done. And do give credit to the necessary people.
!
Click to expand...
Click to collapse
Actually, I did link directly to the thread you wrote, because it was one of my starting points. And to be rigorous, the steps enumerated there are from here, but with the firmware for Neo. The real credit goes to the programmers of Gingerbreak, Flashtool etc.
Like I said, I was just gathering information and detailing them, I don't take credit for anything other than taking the time to write the post.
Yup, I had actually included that initially i.e. that most of us already know these steps from the original thread but then wanted to give you credit for doing what you did.
And when I said give credit where it is due, I meant the actual people behind the programs and kistigun for his tutorial.
guys after i root my neo according to this guide the ota firmware i get will be unbranded? right?
By the way thanks for the guide, i might use it one day after i gain more knowledge about those things...
If you've flashed the generic firmware, then yes, you would be unbranded BUT you will still be locked to your network until you purchase the unlock key.
Unbranding would remove all your network specific apps (part of bloatware).
marcindpol said:
guys after i root my neo according to this guide the ota firmware i get will be unbranded? right?
By the way thanks for the guide, i might use it one day after i gain more knowledge about those things...
Click to expand...
Click to collapse
An OTA update won't remove the branding, but flashing will. It's what I describe in step 5.
I was just like you a couple of days ago, but I managed to learn all this over the weekend and did all I described here. (and a few things more ) Don't rush into it. Read everything coherent and helpful you can find first.
xtacy! said:
If you've flashed the generic firmware, then yes, you would be unbranded BUT you will still be locked to your network until you purchase the unlock key.
Click to expand...
Click to collapse
Thanks for the info. I didn't have any network locks or branding on mine, but it's good to know that for future reference.
Vorsprung said:
An OTA update won't remove the branding, but flashing will. It's what I describe in step 5.
I was just like you a couple of days ago, but I managed to learn all this over the weekend and did all I described here. (and a few things more ) Don't rush into it. Read everything coherent and helpful you can find first.
Click to expand...
Click to collapse
ok i think i understand now, but just to clarify:
if i flash generic (unbranded?) and then do the OTA or Pc Companion update, the update i get will also be unbranded?.
also will all the future updates be unbranded too?
Another question: since my neo is Irish Vodafone branded phone, which generic software i should flash in step 5?
Thanks a lot for help and please do not get annoyed by my questions as i am totally noob when it comes to those things, also sorry for my poor English...
marcindpol said:
ok i think i understand now, but just to clarify:
if i flash generic (unbranded?) and then do the OTA or Pc Companion update, the update i get will also be unbranded?.
also will all the future updates be unbranded too?
Click to expand...
Click to collapse
The answer should be yes to both questions. Once you've debranded your phone, it will not get "rebranded" (except if you flash it with a branded firmware). The generic firmware linked here is of course without any branding.
marcindpol said:
Another question: since my neo is Irish Vodafone branded phone, which generic software i should flash in step 5?
Click to expand...
Click to collapse
You could use the generic one, but you will lose the branding. I'm guessing you don't have a problem with that.
marcindpol said:
Thanks a lot for help and please do not get annoyed by my questions as i am totally noob when it comes to those things, also sorry for my poor English...
Click to expand...
Click to collapse
You're welcome! I'm not exactly experienced myself, so I don't guarantee that my answers are 100% accurate and correct...
I don't think your English is bad at all. Don't you speak English in Ireland?
Can anybody give more details on the branding issue?
Vorsprung said:
The answer should be yes to both questions. Once you've debranded your phone, it will not get "rebranded" (except if you flash it with a branded firmware). The generic firmware linked here is of course without any branding.
You could use the generic one, but you will lose the branding. I'm guessing you don't have a problem with that.
You're welcome! I'm not exactly experienced myself, so I don't guarantee that my answers are 100% accurate and correct...
I don't think your English is bad at all. Don't you speak English in Ireland?
Can anybody give more details on the branding issue?
Click to expand...
Click to collapse
Thanks a lot for the answers
hehe yes people in general speak English here in Ireland but lets not forget there are thousands of emigrants from around the world living here too, i am one of them
Can you please also write which generic firmware should i flash, UK, World or any other? (perhaps there is IE one?), and will it affect the frequency of getting future official updates from SE? (yes i want to get rid of Vodafone from my phone and stay with a 100% SE official firmware).
Thanks
Once you flash a generic firmware, future updates will all be generic updates as well.
Some of the plus points that I can see of having a generic firmware is that
a) updates are rolled out faster (as compared to branded firmware).
b) you get rid of a lot of junk that network providers seem to put in i.e. bloatware.
OK I am now on generic, unbranded Global International 1247-0875_R11C , of course 2.3.3, however I did not root my phone and used SEUS instead OTA.
Thanks a lot Vorsprung and others for help
I just flashed my Xperia Neo 2.3.2 global, applied Gingerbreak, and updated OTA to the last 2.3.3 firmware (4.0.A.2.368)
I confirm I kept root!
Kalram said:
I just flashed my Xperia Neo 2.3.2 global, applied Gingerbreak, and updated OTA to the last 2.3.3 firmware (4.0.A.2.368)
I confirm I kept root!
Click to expand...
Click to collapse
Same here
I follow this guide and got my Xperia Neo rooted! Thanks Vorsprung!!!
I wanted it root to install Google Talk with video! It works very well!
Now I want a way to unlock the bootloader, as I want to run Cyanogen mod
Ask the Admin for your own forum section about the Neo, all this OTA-root with the latest firmware just making me jealous.
flashmode
Hi guys!
well I just can follow till step 5. Opening the "X10FlashTool.exe" --> Click On flash. that's it. It tells me to enter the flash mode but how? I pressed&hold the menu button before plugging the usb cable onto my PC. Instead entering the flash mode it only starts charging my battery. Can somebody help ?
thanks a lot !
i was clicking the wrong button
I have rooted 2.3.2 (checked with rootchecker) but when I try to update OTA it says "Your phone already has the latest software".. Please help!!
Edit: Even says up to date using pc companion.
Hey all,
Came from the Nexus 4 forums, just recently picked up a VZW Moto X. I have a Dell Venue 8 Pro with Windows 8.1, and RSD Lite doesn't work on it. I wanted to restore to 4.2.2 and then later after rooting, back to 4.4 stock and RSD Lite wouldn't see my phone, but adb and fastboot would. I made a quick script which will restore your Moto X, after of course, downloading the correct firmware from http://sbf.droid-developers.org/ghost_rcica/list.php. This is tested working on VZW and if there is enough interest, I can make more for the T-Mobile and AT&T versions.
Instructions:
1. Download and extract the kit zip. It includes install.bat (the script), mfastboot (found on a file share site, if someone is due credit for this please let me know and I'll update) and adb. with associated files.
2. Download and extract your Moto X firmware.
3. Drop the files from the kit in the file with all the extracted Moto X firmware files.
4. Ensure your phone is backed up, if applicable.
5. Plug your phone in and make sure the drivers are loaded (install Motorola Device Manager if needed).
6. Open CMD prompt and navigate to folder with your Moto X firmware files and the files from the kit.
7. Type
install.bat
Click to expand...
Click to collapse
and wait for process to complete. Note the system install takes a bit longer than the rest, as it is a big file.
Please feel free to tweak the batch file if you need. Enjoy!
EDIT: This will not work for anything but VZW as of right now as there are some carrier specific commands in there. Anyone need this for a different carrier? I can download the firmware you need it for and make the batch.
Nice!!!!!! And as you said in the EDIT
Can you provide a file for this carrier?
ClaroChile_XT1058_4.2.2-13.9.0Q2.X-116-LCX-26-25_cid12_CFC_1FF_svc.xml.zip
Click to expand...
Click to collapse
The 4th link in this list
http://sbf.droid-developers.org/ghost/list.php
I'll be appreciated.
Thank you very much for your work.
This wont work with the Sprint Moto X, right?
Edit: Didnt see the bold text...lol. I know that KitKat is going to be pushed to the Sprint Variant next week so if you could make one then, that'd be great
I'm getting a 404 - Not Found error on the Kit download link.
Does this preserve user data?
andino said:
Does this preserve user data?
Click to expand...
Click to collapse
I'm pretty positive it doesn't. All the partitions get wiped and flashed to stock.
cvhovey said:
I'm getting a 404 - Not Found error on the Kit download link.
Click to expand...
Click to collapse
It's hosted on XDA, I don't know why that would be.
d14gvn said:
Nice!!!!!! And as you said in the EDIT
Can you provide a file for this carrier?
The 4th link in this list
http://sbf.droid-developers.org/ghost/list.php
I'll be appreciated.
Thank you very much for your work.
Click to expand...
Click to collapse
Sure, I am on a slow internet provider right now so I'll try to get it done by tomorrow. Gotta let it download tonight.
karn101 said:
I'm pretty positive it doesn't. All the partitions get wiped and flashed to stock.
Click to expand...
Click to collapse
Correct, this is a complete wipe and return to stock (or whatever version you download from the site).
Most people will not need this kit. If RSD Lite works on your machine, I would recommend using that as it is widely accepted.
Claro Chile Install added. Just drop the file inside the ZIP into the directory with the rest of the files, and run ClaroChileInstall.bat instead of the regular install.bat.
I'd be happy to have a version for my TMo DevEd phone. No big rush, but it would be great to have this on hand since I know I'll be restoring to stock at some point soon.
Thank you!
varxx said:
I'd be happy to have a version for my TMo DevEd phone. No big rush, but it would be great to have this on hand since I know I'll be restoring to stock at some point soon.
Thank you!
Click to expand...
Click to collapse
No problem! I'll try to whip something up tonight.
jlink38 said:
Hey all,
Came from the Nexus 4 forums, just recently picked up a VZW Moto X. I have a Dell Venue 8 Pro with Windows 8.1, and RSD Lite doesn't work on it. I wanted to restore to 4.2.2 and then later after rooting, back to 4.4 stock and RSD Lite wouldn't see my phone, but adb and fastboot would. I made a quick script which will restore your Moto X, after of course, downloading the correct firmware from http://sbf.droid-developers.org/ghost_rcica/list.php. This is tested working on VZW and if there is enough interest, I can make more for the T-Mobile and AT&T versions.
Instructions:
1. Download and extract the kit zip. It includes install.bat (the script), mfastboot (found on a file share site, if someone is due credit for this please let me know and I'll update) and adb. with associated files.
2. Download and extract your Moto X firmware.
3. Drop the files from the kit in the file with all the extracted Moto X firmware files.
4. Ensure your phone is backed up, if applicable.
5. Plug your phone in and make sure the drivers are loaded (install Motorola Device Manager if needed).
6. Open CMD prompt and navigate to folder with your Moto X firmware files and the files from the kit.
7. Type and wait for process to complete. Note the system install takes a bit longer than the rest, as it is a big file.
Please feel free to tweak the batch file if you need. Enjoy!
EDIT: This will not work for anything but VZW as of right now as there are some carrier specific commands in there. Anyone need this for a different carrier? I can download the firmware you need it for and make the batch.
Click to expand...
Click to collapse
Will this work on the Verizon Developer Edition Moto X? I want to unroot and relock the bootloader.
Not sure. As long as you have the proper ROM, all this does is flash it.
Sent from my XT1060 using Tapatalk
Does it work in xt1058 from AT&T?
Sent from my XT1058 using xda app-developers app
I would like to thank the OP. This worked perfectly. The exchange email part of 4.4 is broken, so I needed to downgrade so I could check email without buying a play store application. Thanks, again.
jlink38 said:
Hey all,
Came from the Nexus 4 forums, just recently picked up a VZW Moto X. I have a Dell Venue 8 Pro with Windows 8.1, and RSD Lite doesn't work on it. I wanted to restore to 4.2.2 and then later after rooting, back to 4.4 stock and RSD Lite wouldn't see my phone, but adb and fastboot would. I made a quick script which will restore your Moto X, after of course, downloading the correct firmware from http://sbf.droid-developers.org/ghost_rcica/list.php. This is tested working on VZW and if there is enough interest, I can make more for the T-Mobile and AT&T versions.
Instructions:
1. Download and extract the kit zip. It includes install.bat (the script), mfastboot (found on a file share site, if someone is due credit for this please let me know and I'll update) and adb. with associated files.
2. Download and extract your Moto X firmware.
3. Drop the files from the kit in the file with all the extracted Moto X firmware files.
4. Ensure your phone is backed up, if applicable.
5. Plug your phone in and make sure the drivers are loaded (install Motorola Device Manager if needed).
6. Open CMD prompt and navigate to folder with your Moto X firmware files and the files from the kit.
7. Type and wait for process to complete. Note the system install takes a bit longer than the rest, as it is a big file.
Please feel free to tweak the batch file if you need. Enjoy!
EDIT: This will not work for anything but VZW as of right now as there are some carrier specific commands in there. Anyone need this for a different carrier? I can download the firmware you need it for and make the batch.
Click to expand...
Click to collapse
Claro Puerto Rico
jlink38 said:
Claro Chile Install added. Just drop the file inside the ZIP into the directory with the rest of the files, and run ClaroChileInstall.bat instead of the regular install.bat.
Click to expand...
Click to collapse
Can you make it to Claro Puerto Rico?
Android 4.2.2
Blur_Version.139.12.35.ghost_row.AmericaMovil.en.PR > http://sbf.droid-developers.org/download.php?device=0&file=51
Thanks!
Updated
I use the Moto X Install Kit.zip and if works without problem in the Claro Puerto Rico firmware. Thanks a lot!!!
Can you please work on a version for the ATT MotoX? I'll try to look through what you have done and do it manually for myself... But, I've had so many issues with Win8 and have wasted so much time... I don't know if I'll be able to tackle it....
jlink38 said:
No problem! I'll try to whip something up tonight.
Click to expand...
Click to collapse
Have you had time to do this for the T-Mobile Dev Version
Sent from my Nexus 7 using XDA Premium 4 mobile app
Hello my friends.
What is mean the commands below?
mfastboot oem fb_mode_set
mfastboot oem fb_mode_clear
Solved
Nikolay82 said:
Hello. I am fairly new to the XDA forums and I would like to say hello to everyone.
I am looking for someone to help me with the following problem.
I flashed CID to take in any RUU. I've tried many even the USA T-mobile. It worked but had problems using mobile data. Now I use stock european one where version is:1.32.401.17
RUU_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.17_Radio_01.01_U11440261_56.02.50306G_2_F_release_429340_signed_.exe
. I got this version through official RUU. Device is currently S-OFF rooted and has twrp on it.
But now problems are here. I am aware european models got the 5.1 OTA update and I do have it downloaded.
File Says:
OTA_HIMA_UHL_L51_SENSE70_MR_HTC_Europe_2.10.401.1-1.40.401.8_release_444119.zip
Now when I try to update OTA through twrp it doesnt let me. Says something about Err_message. That being said, sideload wont work either. Now my question is, how do I get the OTA to my device? Note; when checking for updates via settings in the phone it says no updates available, regardless of updated airing for a while now. Now i wonder if can update from :1.32.401.17 to 2.10.401.1 with OTA or do I need to update first to 1.40.401.8 (I have 1.40.401.8 flash file).
Please if someone can help me I would thankful. Thanks.
Click to expand...
Click to collapse
OTAs can only be used with the stock recovery. I don't recommend doing a stock OTA if you have modded parts of the system. Better to flash a rom through TWRP. You might need to update the firmware as well.
Are you referring to 0PJAMIG*.zip file? in that case i have them plenty and one I need that matches my phone is like missing some files in the zip. Sadly, I can't post the link yet.
Let me explain this better please:
1. I do have RUUs,; RUU_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.17_Radio_01.01_U11440261_56.02.50306G_2_F_release_429340_signed_2_4
2. I do have 0PJAIMG Files as well: 0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.8_Radio_01.01_U11440261_56.02.50306G_2_F_release_425571_signed_Hboot.zip
3. And I believe I have proper firmware and recoveries for said 0PJAIMG. I have every one of them downloaded for gradual update.
Problem is; I don't have the automatic RUU for version 1.32.401.8, the exe stuff. And I am having hard time installing the 0PJAIMG file on the phone because it gives errors and missing files inside from the looks.
File size of 0PJAIMG is 2gb but content withing the zip is barely 40mb but it says 2gb...
If I am able to get everything related with 1.32.401.8 I could most likely do the all process till latest update.
I am aware I can't post links but for this sake I would like to post it like this: tinyurl[dot]com/m9roms
Just replace "[dot]" with "."
moderator can remove the link however but I need urgent help. If someone can guide me what to I would appreciate it.
Today I have pulled an MM Firmware-Over-The-Air update from my AT&T Galaxy S7 and uploaded the original .CFG file and my compiled .ZIP files for flashing via recovery. Download the file of your choice and place it onto your devices external storage, reboot into recovery, select "Apply Update From External Storage", search for the downloaded file, select it, click yes, and wait for the flash to complete.
Another note: As normal, this WILL NOT wipe any of your personal data. But just know that your recovery might not allow you to flash from External storage if your device is rooted, which means you will either have to completely unroot and restore dm-verity status or try flashing the file via ADB.
If you have any troubles please feel free to write below about it. If this helped you, please be sure to hit the thanks button.
To be clear, I will capture the Nougat update for this device once it is OFFICIALLY released. The update file in this thread is a MM update.
PDA Version: G930AUCU4APJ4
CSC Version: G930AATT4APJ4
--Download links--
Original .CFG File: https://mega.nz/#!D4wzSbhR!IyQKit5s0M-s4_5XbYb0sOWVePk1zcU-TJDJMffwL5A
Compiled .ZIP File: https://mega.nz/#!e0w1RaIa!SmKZ0Gr8iN7ETEUmEUdWljgGZZc_x-x_qhxvXQfUBm8
Cheers!
anyone tried to flash this that's on the unofficial Nougat (G930AUCU4BQA4)
Looking at the CSCVersion.txt File inside the ZIP shows that this is G930AATT4APJ4 for anyone wondering which version
elijahblake said:
anyone tried to flash this that's on the unofficial Nougat (G930AUCU4BQA4)
Click to expand...
Click to collapse
Note that I believe this is just an update to MM. I would expect that you'd need to get the ODIN files for the G930AATT4APJ4 build and do a full flash / wipe to this one.
thelostsoul said:
Note that I believe this is just an update to MM. I would expect that you'd need to get the ODIN files for the G930AATT4APJ4 build and do a full flash / wipe to this one.
Click to expand...
Click to collapse
Is it possible to ask you to flash the update to tell me if it truly works? If it doesn't I'll replace the files.
KingOfTheNet said:
Is it possible to ask you to flash the update to tell me if it truly works? If it doesn't I'll replace the files.
Click to expand...
Click to collapse
Sorry, I already have Nougat on my phone and I'm holding out for the official release before I start flashing again.
thelostsoul said:
Sorry, I already have Nougat on my phone and I'm holding out for the official release before I start flashing again.
Click to expand...
Click to collapse
Most likely be Spring with AT&T and their release record.
thelostsoul said:
Sorry, I already have Nougat on my phone and I'm holding out for the official release before I start flashing again.
Click to expand...
Click to collapse
It's fine, I just flashed it to mine and it's just a security patch for MM. I will capture the official Nougat FOTA release once it comes out.
4APJ4 is Old (October) the latest is 4APK1 (MM)
4=Bootloader Version
A=Marshmallow
P=2016
K=November
1=Build Number
And latest for Nougat is 4BQA6
4=Bootloader Version
B=Nougat
Q=2017
A=January
6=Build
Omar04 said:
4APJ4 is Old (October) the latest is 4APK1 (MM)
4=Bootloader Version
A=Marshmallow
P=2016
K=November
1=Build Number
And latest for Nougat is 4BQA6
4=Bootloader Version
B=Nougat
Q=2017
A=January
6=Build
Click to expand...
Click to collapse
One issue with that... qa6 is feb update...
twizt3d said:
One issue with that... qa6 is feb update...
Click to expand...
Click to collapse
Added screenshot
twizt3d said:
One issue with that... qa6 is feb update...
Click to expand...
Click to collapse
Yeap it doesnt apply for Beta they are always ahead of time only official releases match. (There's always that one build that wants to break the rules, but only happen with unreleased builds mostly because they apply the security patch early for testing and compiler gives that build code.)
It always has been that way with Samsung since the OG Galaxy S.
Check my posts from several years ago on earlier galaxies and you'll notice.
KingOfTheNet said:
Today I have pulled an MM Firmware-Over-The-Air update from my AT&T Galaxy S7 and uploaded the original .CFG file and my compiled .ZIP files for flashing via recovery. Download the file of your choice and place it onto your devices external storage, reboot into recovery, select "Apply Update From External Storage", search for the downloaded file, select it, click yes, and wait for the flash to complete.
Another note: As normal, this WILL NOT wipe any of your personal data. But just know that your recovery might not allow you to flash from External storage if your device is rooted, which means you will either have to completely unroot and restore dm-verity status or try flashing the file via ADB.
If you have any troubles please feel free to write below about it. If this helped you, please be sure to hit the thanks button.
To be clear, I will capture the Nougat update for this device once it is OFFICIALLY released. The update file in this thread is a MM update.
PDA Version: G930AUCU4APJ4
CSC Version: G930AATT4APJ4
--Download links--
Original .CFG File: https://mega.nz/#!D4wzSbhR!IyQKit5s0M-s4_5XbYb0sOWVePk1zcU-TJDJMffwL5A
Compiled .ZIP File: https://mega.nz/#!e0w1RaIa!SmKZ0Gr8iN7ETEUmEUdWljgGZZc_x-x_qhxvXQfUBm8
Cheers!
Click to expand...
Click to collapse
Can I ask you a question? how did you manage to compile .Zip file to flash from recovery? is it flashable from stock recovery? how did you manage to add original signature?
suyash1629 said:
Can I ask you a question? how did you manage to compile .Zip file to flash from recovery? is it flashable from stock recovery? how did you manage to add original signature?
Click to expand...
Click to collapse
There was no compiling. You can flash the ota update files from stock recovery after renaming the file name extension from .cfg to .zip.
suyash1629 said:
Can I ask you a question? how did you manage to compile .Zip file to flash from recovery? is it flashable from stock recovery? how did you manage to add original signature?
Click to expand...
Click to collapse
I didn't flash the update file itself, I had the ODIN files for it. They're the same thing.
When it comes to official updates, no signature modification should be necessary (Or possible, for that matter. I don't think there's a way to modify the signature. If there is, I don't know about it.). The only thing different between the 2 files is the file format.
Hope I answered your questions.
Cheers!
Can You Supply the Latest FOTA roms For.
G930AUCU4BQK2
G930AUCS4BQJ2
G930AUCS4BQH1
I have an Unlocked G930A (not really unlocked just using a cricket SIM) But I cannot Get the Software Updates For it because of AT&T. I have seen the information on reflashing it to the U software but i really dont want to have to restore everything to my phone unless i have to..
The Version currently running on my phone is vulnerable to the bluebourne exploit and im trying to get that patched. :/
On a side note. are you able to do a packet capture while scanning for the updates? There is one on the play store that will also let you perform a MITM on the application and you should be able to capture anything sent over SSL in plain text/hex/etc
I did Want to Ask you a quick question. How did you capture the FOTA package to begin with?
I wonder if it is possible to setup an Authoritative only dns server and then use it to spoof the location of the update servers. to create a DNS method that would allow the FOTA to be pushed to devices no longer on AT&T
Anywho if you can get those firmwares and get me full packet captures of just the update application while it is checking and downloading the update, i might be able to create a web application that is able to capture the headers sent by the phone that identify its model/fw version/etc and be able to push the firmware update Via the built in option in the settings, (although you may need to swap your dns settings for a moment and install a CA cert that allows validation of a connection. im not too sure if a CA cert will need to be installed because im not sure if they push the updates over a SSL/TLS connection. Using the data collected here may also pave the way to enable this to work with other models and carriers and manufacturers. (my hypothesis is that packet captures would be needed on any firmware updates "you" would want to push with this)
Basically Im thinking it might be possible to download those zip files along with the packet capture data to create a simple web application that is able to tell the phone there is a software update available. It would require using a 3rd party DNS server to "redirect" the connection to a server that doesnt care if your an at&t customer. It might also need a self signed CA cert installed into the device to Validate TLS/SSL. From there it might be possible to have the server 301 redirect the zipfile to another url that is behind a CDN to reduce the risk of ddos and keep the server(s) stable keeping the downloads reliable and fast.
Seeing how the Firmware update is already digitally signed by Samsung and/or AT&T it should probably install without an issue. I dont see the possibility of the wrong stock firmware being flashed on the wrong phone provided the manufactuer had a proper assert statement in place to verify the model and sw/hw versions, and im pretty sure a stock recovery wont accept a firmware signed by any key.
I might be Going off topic here, But one more question.
Do i actually need AT&T service to download the OTA updates from the Software update function in the phone settings.
What i mean by this is does the SIM card need to have an active plan on it? or can it just be provisioned to their network with out a phone plan and downloaded over wifi?
UPDATE: It Can Now be officially confirmed that Carriers and Samsung Deliberately block OTA updates when you unlock the device. there are thousands if not tens of thousands out there on a variety of devices as far back as the S4 that may not have been able to get updates. just because they used a Cricket Sim or unlocked the device. I also Spoke with AT&T customer support today and got told the blatant Lie that they push the same OTA updates through the cricket network to ensure that AT&T devices on it can be updates. I also went to samsung service center at bestbuy and they told me my phone was up to date when its not. Samsung Smart Switch Also Reports that my device is up to date when i know for a 900% fact it is not.
So it looks like Someone is going to have to write an app that Hijacks the Requests and replays a valid packet capture just to get the phone to update in its orignial intended built in method.
The sad part is the carriers would see this and just write a patch to prevent it rather then change their policies.
Basically The carrier has the right to deny you a software update because you left their network and leave you exposed to Critical Security Vulnerabilities.
That is their way of sticking up their Middle Finger at the FCC for mandating carriers unlock their devices and the end user who either met his/her contract obligation or outright paid for his/her device
[SARCASM] basically its like saying hey we know you paid for your device, but **** you, you left our network and even though the updates come from a samsung controlled server were going to ensure our middleware deliberately blocks your device from updating so you remain vulnerable and you information is stolen, That'l teach you for unlocking your device and leaving our network because we charge literally an arm and leg for service, how dare you as a customer go against our big monopoly that seeks to buy out every major ISP and cable provider in america but hey thats alright were still winning but because you left our network we will block these updates so we can further Sell your information and viewing browsing habits off to the NSA (Google TITANPOINTE tinfoil hatters!!!!) unless you want to send your phone off to one of our service centers where one of our butthurt technicians will see you rooted your phone and say it has damage and turn our free reflashing service into a paid repair and charge you through the ass for service, also did we mention were not going to update the software because our application is designed not to tell you there is an update available if you unlocked it or used our Subsidary cricket SIM in the device and didnt unlock it Or you can go on XDA and grab an odin package an potentially invalidate your warranty and then when your device comes to us for a cracked screen we can deny you the repair even though the modifcation wasnt a modifcation and has nothing to do with a cracked screen. [/SARCASM]
Anywho im going to Bite the Bullet and Grab an Assortment of AT&T contract Sims and Go Phone sims and Other Carriers, Im going to go to the local pawn shops and buy an assortment of devices and attempt to downgrade each and every single one of them back to their old original firmware versions, Dump all the FOTA updates and dump the packet captures and i guess i will have to research the possibility And be that asshole who gets sued for reverse engineering their software.
YOU CAN FIND THE FULL G930AUCU8CSA3 FIRMWARE HERE:
https://forum.xda-developers.com/att-galaxy-s7/how-to/g930a-oreo-8-0-stock-att-odin-files-t3869871
G930AUCU4CRE4 to G930AUCS4CRG5:
Download link: https://drive.google.com/file/d/1MoJ0be2exLMoji2ZURR6tbEiHCqWSszG/view
G930AUCS4CRG5 to G930AUCU4CRI2:
Download link: https://drive.google.com/file/d/1Fdrcy4m49Qtl-__dUE0Etuqmyn8UhYbe/view
G930AUCU4CRI2 to G930AUCS8CRJ2
Download link: https://drive.google.com/file/d/1bhVx5Rt_CTXmG5YQrY5azS10RO3lWj1r/view
G930AUCS8CRJ2 to G930AUCS8CRK1
Download link: https://drive.google.com/file/d/1lepPXVZIiZM4i_VMOUOvDvVHvGY4ifwv/view
G930AUCS8CRK1 to G930AUCS8CRL1
Download link: https://drive.google.com/file/d/1CUJOVWnDsk3LL378vxLO0vp8y3AdQjmr/view
If i helped you don't forget to hit thanks button
G930aucu4cri2
friend you have the security patch of August 1 the new update its version is G930AUCU4CRI2 weighs between 456MB or 472MB
Juliowwwe said:
friend you have the security patch of August 1 the new update its version is G930AUCU4CRI2 weighs between 456MB or 472MB
Click to expand...
Click to collapse
Link is UP
thank you very much
thank you very much
New October update is UP
Hello,
How to install these updates ?
I've succeed to install the 8.0 update with ODIN and with 4 files : AP & BL & CP & CSC.
But here there is no such files into the updates you uploaded.
lahlah said:
Hello,
How to install these updates ?
I've succeed to install the 8.0 update with ODIN and with 4 files : AP & BL & CP & CSC.
But here there is no such files into the updates you uploaded.
Click to expand...
Click to collapse
1.) Turn off the phone. Hold down Volume Up + Home + Power until you see a little Android guy. It will say Applying System Update or something like that possibly, and just let it do it's thing until a menu comes up.
2.) Select "Apply update from ADB". You can scroll using the volume buttons and select using the power button.
3.) Make sure you have ADB and the proper drivers installed on your PC:
http://dl.adbdriver.com/upload/adbdriver.zip
4.)Put the firmware in the ADB folder. You can rename it to anything easy to remember like "FIRMWARE".
5.) In the ADB folder, hold SHIFT + right mouse click and choose "Open command window here". Then type the command "adb sideload FIRMWARE" (where FIRMWARE is how you named your file).
6.) Wait patiently.
7.) The phone will reboot and will hang at AT&T logo. This can take another 10 minutes, just wait until it's done
Ok, so I'm a novice at best on flashing with Odin... just flashed my AT&T S7 for the second time today, loading the SM-G930U version of Oreo (G930UUEU8CRJ2).
My understanding is that the 8 in the firmware version (G930UUEU8CRJ2) indicates that it is bootloader v. 8. I also understand that once you update the bootloader, it is impossible to downgrade it... So when I realized I couldnt enable Wifi calling on SM-G930U firmwares I thought I would flash back to the AT&T firmware, and then debloat it to improve the performance. But i cant find an SM-G930A Oreo Rom with BL v. 8.
I thought this one might be, but the 3 files seem to be independant of each other, and the 3rd file that lloked like it might be BL8, is less than 50MB...
So Im hoping you can provide some guidance, and im hoping i didnt shoot myself in the foot with this SM-G930U firmware.
Thank you
Sam
samhnky said:
Ok, so I'm a novice at best on flashing with Odin... just flashed my AT&T S7 for the second time today, loading the SM-G930U version of Oreo (G930UUEU8CRJ2).
My understanding is that the 8 in the firmware version (G930UUEU8CRJ2) indicates that it is bootloader v. 8. I also understand that once you update the bootloader, it is impossible to downgrade it... So when I realized I couldnt enable Wifi calling on SM-G930U firmwares I thought I would flash back to the AT&T firmware, and then debloat it to improve the performance. But i cant find an SM-G930A Oreo Rom with BL v. 8.
I thought this one might be, but the 3 files seem to be independant of each other, and the 3rd file that lloked like it might be BL8, is less than 50MB...
So Im hoping you can provide some guidance, and im hoping i didnt shoot myself in the foot with this SM-G930U firmware.
Thank you
Sam
Click to expand...
Click to collapse
The bootloader binary was updated to 8. After you flash this you'll be stuck on Oreo.
Full firmware for G930A G930AUCS8CRJ2 will be uploaded later today.
stek-kravari said:
The bootloader binary was updated to 8. After you flash this you'll be stuck on Oreo.
Full firmware for G930A G930AUCS8CRJ2 will be uploaded later today.
Click to expand...
Click to collapse
Awesome! Thank you, thank you!
I actually really like Oreo, just trying to get Oreo and WiFi calling working on my phone (My Office at work fights all day for 1 bar of cell signal), I had hoped that WiFi calling worked in the SM-G930U variant since everyone talked about it running so much better, but alas, it still doesn't support WiFi Calling (Stupid me for thinking it might have had support added recently).
Thank you again
(My Wife is sure to get upset with me once again working on my phone again today... whoops)
Thanks , G930AUCS8CRJ2 is working fine so far. Do you mind sharing how you go about 'converting' a set of ODIN files to a flashable adb zip? Do you just unextract every single archive in the .md5 files? and then zip it all up? And would rooting to G930AUCU4CRI2 brick my phone now that I am on CRJ2? My bad for all of the questions.
bnn0 said:
Thanks , G930AUCS8CRJ2 is working fine so far. Do you mind sharing how you go about 'converting' a set of ODIN files to a flashable adb zip? Do you just unextract every single archive in the .md5 files? and then zip it all up? And would rooting to G930AUCU4CRI2 brick my phone now that I am on CRJ2? My bad for all of the questions.
Click to expand...
Click to collapse
You mean about G930AUCS8CRJ2 sideload with adb? Im just pulling the update from AT&T servers and uploading it here. I don't know how to make sideload zip. And for the rooting part I don't know if its possible now because the bootloader binary was updated to 8, try to search here on xda and see if you can find root methods for this firmware
new update, check first post
----
I can ask you a question? please. My baseband is SMG930AUCU4CRE4 can i update to G930AUCS8CRK1? :/
Maury Yarik said:
I can ask you a question? please. My baseband is SMG930AUCU4CRE4 can i update to G930AUCS8CRK1? :/
Click to expand...
Click to collapse
First you need to install this:
https://forum.xda-developers.com/att-galaxy-s7/how-to/g930a-oreo-8-0-stock-att-odin-files-t3869871 (G930AUCS8CRJ2)
Then you need to go from G930AUCS8CRJ2 to G930AUCS8CRK1, G930AUCS8CRK1 to G930AUCS8CRL1 and you will have the latest update.
I actually have a S7 G930A. Rooted before, not rooted now.. Is there a way to do any of these updates without hooking up to a PC? I actually have no charge port functions and can only use wireless charger to charge the phone till i get the port fixed someday to do these features. I am on Android 8.0 oreo that i installed to sd card and updated from there like a year ago? Is that possible to do? Use SD card update.. Or. Would love to root the phone again, but cent seem to find a one click root app that will work with this phone..
Josh
Josh13400 said:
I actually have a S7 G930A. Rooted before, not rooted now.. Is there a way to do any of these updates without hooking up to a PC? I actually have no charge port functions and can only use wireless charger to charge the phone till i get the port fixed someday to do these features. I am on Android 8.0 oreo that i installed to sd card and updated from there like a year ago? Is that possible to do? Use SD card update.. Or. Would love to root the phone again, but cent seem to find a one click root app that will work with this phone..
Josh
Click to expand...
Click to collapse
Yes, you can update your phone without pc, just download the update you need from your phone, put the update in your sd card, go to recovery and select the option "Apply update from SD card"
stek-kravari said:
Yes, you can update your phone without pc, just download the update you need from your phone, put the update in your sd card, go to recovery and select the option "Apply update from SD card"
Click to expand...
Click to collapse
I was thinking something like that was possible. I have baseband version G930AUCU4CRB5 Android 8.0.0 on the AT&T Gal S7 as mentioned, I never saw any updates from this version to go up to a newer version or get into regular updates from OTA. 2 issues I would like to also fixed, that came with the manual update to 8.0 oreo on my phone was the HR heart rate sensor on the back by your flash(red LED) always goes off.. And have tried to go to Samsung health and do some settings to turn it off, but seems to show back up eventually. Also, the issue of not having a working LED indicator, works fine when the phone is POWERED off. and charges. But in OS, it won't work, screen off or on bc of the update. If anyone knows how those issues could be fixed and if there is a possible newer update from my baseband mentioned below. And thanks for the response.
HI, Help needed
Hi,
I wanted to check if it is possible to flash the latest Oreo firmware you have here for downloading dirrectly to my samsung s7 that is currently running on 7.0? Current BaseBand is G930AUCU4BQK2
Basically what happened was that i lost all my contacts on my phone, I ended up download Dr.Phone to my laptop, which i used to try and recover my numbers. What i didnt know was that dr.phone rooted my device which has caused me nothing but headaches.
I now want to flash my phone and get updated to oreo and have my phone working normally again. Since dr.phone did whatever it did to my phone I lost use of my finger print scanner, had to disable samsung health as it kept trying to open on its own, my phone is lagging and freezing constantly..
I just want my phone to be normal again and unrooted and updated.
Lastly my phone is an AT&T device, that i bought second hand in Dubai, if i flash stock firmware is it going to carrier lock my device to AT&T again?
Any advice and help with this matter would be greatly appreciated.