I dowloaded my stock firmware from samfirmware.com and now i would like to flash it. It is a single tar.md5 package. I would like to known how to flash it. I searched, but it was not much help to me. Do i use the single package option in ODIN?
- i have never used odin, but i have flashed alot of roms so im not completely stupid when it comes to this stuff.
Yes, one package
Once you have Odin
To do so
The file "GIO_v0.1.ops"
You will find in the package of Odin
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You put the file you downloaded md5
How do you see "PASS!" disconnect and if appears
"Close serial port and wait until rebooting" a disconnect, and wait until the phone turns on, of course, disconnect the cable.
It says Samsung on the phone remove the battery and enter the Recovery Menu
select "wipe"
select reboot
READY
I already have the new rom
Is it possible to unzip the rom with 7zip and remove the recovery image so i can still have my custom recovery?
AlwaysDroid said:
Is it possible to unzip the rom with 7zip and remove the recovery image so i can still have my custom recovery?
Click to expand...
Click to collapse
Ypu can but must be able to do a md5sum or flash as .tar without md5 check
Sent from my GT-S5660 using xda premium
Cant find?
voetbalremco said:
Ypu can but must be able to do a md5sum or flash as .tar without md5 check
Sent from my GT-S5660 using xda premium
Click to expand...
Click to collapse
Im trying to flash a file called S5660MUGKG3_S5660MBMCKG3_BMC. When ever i try to one package i cant seem to find it? Can anyone help me with this?
Did you unzip it?
If you haven't already, please check "show extensions for known file types" in your Windows Explorer settings.
Darkshado said:
Did you unzip it?
If you haven't already, please check "show extensions for known file types" in your Windows Explorer settings.
Click to expand...
Click to collapse
How do I unzip it? Can I use winrar and extract?
Darkshado said:
Did you unzip it?
If you haven't already, please check "show extensions for known file types" in your Windows Explorer settings.
Click to expand...
Click to collapse
Yay I got it!
Thanks for your help!
Is it fine if it says 1 (COM10) ? and also its keeps on showing the boot animations over over... wont go further and on odin it says pass. should i keep on waiting or is somthing wrong? is it bricked?
1 (COM10) is simply to indicate the serial port number assigned to your phone by Windows and the Samsung USB driver in Odin.
Your phone is boot looping, some might consider this a soft brick. My best guess is that you previously installed a ROM that formatted your /data and /cache partitions from the stock RFS format to ext4 instead. The stock 5660M ROM doesn't support ext4.
Reboot in the stock recovery, either with "adb reboot recovery" or by using the home and power keys simultaneously.
From there, wipe user data and cache, or something similar I don't recall the exact wording, but I do remember they were two separate commands.
Reboot, should work now. Use ddms (part of the Android SDK) to see what's going on under the hood if you feel like it.
I take it computers are a relatively new thing for you to ask how to unzip files. My best advice: make very regular backups and read instructions carefully. Losing data is not cool. Losing someone else's data is worse. (I'm guessing you're on the family computer here...)
Related
can anyone please help???
My friend failed at rooting the desire and now...
No mather what i do my phone always turns on in hboot mode. this is a problem, because volume up and down don't work, neither does the powerbutton.
i tried to lunch the RUU exe on ma computer to instal androind anew but it always says that the battery is under 30%
i also tried to put a rar file with the name PB99IMG_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed
on my sd card... it should install this update automaticly but it does nothing
i red a lot of forums and tried a lot but nothing worked
Any ideas?? please help
Did you rename it to PB99IMG.zip? Because that you must do
Sent from my HTC Desire using xda premium
do i have to have a goldcard that this metod works??
i tried to rename it, didn't work : /
Did you get any errors?
Did you rename with windows? If yes, make sure it's not PB99IMG.zip.zip, because windows hides known file extensions.
Did you get your phone from a carrier or an independent store like amazon?
rename with windows? what do you mean?
i renamed it like every other map or ikon
no errors, it doesn't do anything
ok... i'm cinda confused now. what should i rename into PB99IMG.zip. a shipped rom right?
I mean, with witch OS (windows, linux, android itself) did you rename the downloaded file?
You should download and rename this file:
PB99IMG_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.zip
After downloading, rename it to "PB99IMG.zip". When done, copy it to the root of your SD card (so not in any folder).
Now reboot into HBoot (start phone with pressed volume back and power button) and the file should be recognized.
no, you need to extract rom.zip from the RUU (EDIT: unless you already downloaded the PB99IMG version of it which I can see you did so never mind what I said)
go to my guide and find the right section for you there's a tutorial on how to do it
bortak said:
no, you need to extract rom.zip from the RUU (unless you already downloaded the PB99IMG version of it which I can see you did so never mind what I said)
go to my guide and find the right section for you there's a tutorial on how to do it
Click to expand...
Click to collapse
IMHO its's much easier to download a "prepared" PB99IMG-file directly.
tnx very much guys!!!
i hope it works
if it doesnt... is there anything else i can try??
jann32 said:
if it doesnt... is there anything else i can try??
Click to expand...
Click to collapse
Let's first see if it works. Always take one thing at a time.
it doesn't recognize it.... it does nothing
it isn't rooted... perhaps that is the problem?
do you have another suggestion??
Are you really in Hboot mode (HBOOT in blue highlighted letters)?
Try what bortak said.
it doesnt work
it doesnt do anything
mybe because it isnt rooted??
do you have another suggestion??
Please answer based on my questions instead of repeating what you just wrote, otherwise it's nearly impossbile to help you.
yes i am in hboot.... white screen... blue highlights
do i need a goldcard for the file to be recognized?
No it just must be spelled correctly. PB99IMG.zip
Not zip.zip and also not lower case like pb99img.zip
If you can give us a screen shot of the file name in windows to confirm it is correct please
Sent from my HTC Desire using xda premium
i spelled correctly
mybe it did't work cause i put in on a different sd card and than switch it with the original one
i did it so, because i can't put anything on the broken desire, cause its broken. so i took a different phone and then i put on the sd card that file. then i switch sd cards.
could that be the reason?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Where on the SD card are you putting it?
If its not reading SD card, you need to follow the usb brick tutorials such as
http://androidforums.com/desire-tips-tricks/365476-guide-usb-brick-fix.html
Sent from my HTC Desire using xda premium
hm... mybe you're right!
i'll try that, tnx!
Hello, I did some searching and didn't see anything like this for Windows.
** NOTE: This requires the ADB and bootloader drivers to be installed already **
Google released the original 4.0.1 firmware (including radios and bootloader) in a compressed .tgz file. You can get that here:
https://dl.google.com/android/aosp/mysid-itl41d-factory-516b56c2.tgz
Extract the file into a working directory. Then... extract this (attached) into that directory as well.
Either reboot to bootloader manually or turn on USB Debugging, then run flash-all.bat and everything should go from there!
This is just a modified version of the script Google sent along with the package, so there shouldn't be any issues.
Tested the script on my own phone, and it completed twice. So it should be safe. But as always, you assume the risk!
Thanks, this worked for me. However, it does not re-lock the bootloader. You can tell by when the Google logo is on the screen while booting up, if there is an unlocked lock on the bottom then it is unlocked. To fix this, type in:
flashboot oem lock
Click to expand...
Click to collapse
After that you should be good to go again and be stock.
Why not use the 4.0.2 image? Makes more sense to use the latest version:
https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz
I get a "Missing adbwinapi.dll" error when trying to use your .bat? How do I ensure ADB is installed correctly?
Zzim said:
I get a "Missing adbwinapi.dll" error when trying to use your .bat? How do I ensure ADB is installed correctly?
Click to expand...
Click to collapse
If you've got the SDK installed put the fastboot files in the sdk\tools or sdk\platform folder where adb is located. The adbwinapi.dll should be located in there.
Or just copy adbwinapi.dll into the same folder where you have the "restore kit" files downloaded from the OP.
confirmed working bailed me out on a bootloop when trying to root my CDMA Verizon Galaxy Nexus
error
i have the flash.all file in my platform tools but i got an error device not recognnized message?
how do i get this file in zip form?
https://dl.google.com/android/aosp/m...y-516b56c2.tgz
djeddieone said:
confirmed working bailed me out on a bootloop when trying to root my CDMA Verizon Galaxy Nexus
Click to expand...
Click to collapse
cerotes have galaxy nexuses? hrm
mikedfromaz said:
i have the flash.all file in my platform tools but i got an error device not recognnized message?
how do i get this file in zip form?
https://dl.google.com/android/aosp/m...y-516b56c2.tgz
Click to expand...
Click to collapse
Winzip.. unzip it twice...
Sent from my Galaxy Nexus using XDA App
edit: got it thanks
Thank you for the script..i know it will come in handy one day or another!
Sent from my Galaxy Nexus using xda premium
whenever i try to extract the files using winzip it says it can't read the header etc etc. Any ideas?
bigeric828 said:
whenever i try to extract the files using winzip it says it can't read the header etc etc. Any ideas?
Click to expand...
Click to collapse
It was zipped with WinRAR as a standard zip file. Should be able to be opened on just about anything... Have you tried redownloading?
oops already posted this but i put it in the wrong thread but here it is again sorry.
does anyone know how i can get this working? whenever i run it i just get an error: device not found
waiting for bootloader...
flashing bootloader...
error cannot load "bootloader-toro-primek10.img"
<waiting fo device>
anyone suggestion? ive tried reinstalling the drivers and its still not working
any help is appreciated thanks
so.....how do we run the script? with fastboot? with what commmands? it's late, i'm tired and i just want to start from scratch on my GNex...had Wallet running, then loaded BB, lost Wallet, now wallet won't run on ANY rom i have, even rebuilt to 4.0.2, but need to get back to 4.0.1...i posted a question in the Q&A section if there was an ODIN of 4.0.1 lying around somewhere....hopefully i'll get some help either way...
thanks.
EDIT...got it, double click the bat file...the original post did not say that.....thanks for the last post for mentioning it
|Jason8| said:
Hello, I did some searching and didn't see anything like this for Windows.
** NOTE: This requires the ADB and bootloader drivers to be installed already **
Google released the original 4.0.1 firmware (including radios and bootloader) in a compressed .tgz file. You can get that here:
https://dl.google.com/android/aosp/mysid-itl41d-factory-516b56c2.tgz
Extract the file into a working directory. Then... extract this (attached) into that directory as well.
Either reboot to bootloader manually or turn on USB Debugging, then run flash-all.bat and everything should go from there!
This is just a modified version of the script Google sent along with the package, so there shouldn't be any issues.
Tested the script on my own phone, and it completed twice. So it should be safe. But as always, you assume the risk!
Click to expand...
Click to collapse
Having seen the Nexus S sticky for factory firmware etc., I think its time we see this or another post evolve into the same sort of thing including full restores for 4.0.1, 4.0.2 and the eventual 4.0.3(lte) radio's etc.,
Here's a modified script that will allow you to choose between 4.0.1 and 4.0.2. (as long as you have either image or both) It also has the option to re-lock the bootloader.
I'll also update it when the official 4.0.3 images are released.
I don't take no credit for what was already done, I just modified it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instructions:
=========
1- Extract folder with contents of this package.
2- You will need the Google Factory image for the version you want to restore, or both if you want.
3- Extract the image files to the same folder in step one. Image files should not be in a seperate folder!
So you should have, in one folder, the above files contained in this package plus:
image-mysid-xxxxxx.zip (xxxxxx= pertains to what version)
radio-tor-i515.xxxx.img
radio-cdma-tor-i515.xxxx.img
flash-all.sh
bootloader-tor-primexxxx.img
4- Dbl click on GNexRestore.bat and follow the prompts.
Optionally, if you do have the Android SDK installed, just copy the image files and GNexRestore.bat to the platform-tools folder.
fastboot.exe will also be needed, if you don't have it already, just copy the one in this package to the same location.
Then run GNexRestore.bat
when you extraxt the factory image i get one file and the icon looks like a blank piece of paper. is that how it is suppose to be
When you extract the image, you should see a folder with the files you need.
e.g. this is from 4.0.2
i have root and want to delete setup wizard.apk from priv app
but when i reboot it come back again
i think because it write protected
how can i delete it please ?
elawady.2014 said:
i have root and want to delete setup wizard.apk from priv app
but when i reboot it come back again
i think because it write protected
how can i delete it please ?
Click to expand...
Click to collapse
if you have a custom recovery, reboot into it, eventually mount system r/w, and delete it...
i have custom recovery
but how i mount this >>??
elawady.2014 said:
i have custom recovery
but how i mount this >>??
Click to expand...
Click to collapse
have you tried hitting the mount button (twrp custom recovery here... supposing cwm the same feature is somewhere...) ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Or have you tried to use the file manager to navigate in the system partition ? (maybe there's no need to mount anything.
pagoweb said:
have you tried hitting the mount button (twrp custom recovery here... supposing cwm the same feature is somewhere...) ?
Or have you tried to use the file manager to navigate in the system partition ? (maybe there's no need to mount anything.
Click to expand...
Click to collapse
yes i have root explprer and go to system
but every thing i delete it
come back again after reboot
elawady.2014 said:
yes i have root explprer and go to system
but every thing i delete it
come back again after reboot
Click to expand...
Click to collapse
Are you on stock kernel? If so these will keep coming back so if you want to delete have a look for a moded stock kernel or flash a tweaked kernel then you should be able to remove them. If you dont want to do any of that get a app from the playstore what freezez it.
elawady.2014 said:
yes i have root explprer and go to system
but every thing i delete it
come back again after reboot
Click to expand...
Click to collapse
your doing it in root explorer is why ... they just clearly told you to do it in TWRP / File manager and the file will be gone for good
elawady.2014 said:
i have root and want to delete setup wizard.apk from priv app
but when i reboot it come back again
i think because it write protected
how can i delete it please ?
Click to expand...
Click to collapse
Code:
adb reboot recovery
adb shell mount /system
adb shell rm /system/priv-app/SetupWizard.apk
sorry but i have differient recovery called shawmi
its chienese cuz my phone cheniese
but it like cwm recovery
and i found mount bottom
when i press it
it saied ur storage is mounted
and i don't know what is this mean
thank u very very much
i think it's deleted
nkk71 said:
Code:
adb reboot recovery
adb shell mount /system
adb shell rm /system/priv-app/SetupWizard.apk
Click to expand...
Click to collapse
*****
thank you, I was looking for this location... just a side note if you have root, using root explorer you can easily just delete the setupwizard folder from that location, I had just forgotten where it was... again thanks...
Original Post
Hello, I am running an unlocked Bell S3 (SGH-I747M/d2can, hope this is the right forum) on 4.4.2 official Sept. 2015 update. Screenshot shows the build info.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I had a similar issue with my Skyrocket, although I was able to root it with Saferoot.
I have a MacBook on Yosemite and a Windows Vista PC (don't hurt me). Windows fails to cooperate with any drivers I install on it if they install at all. All I can get is the file transfer. JOdin3 can recognize it, but gives me libusb error -12. It just won't work. Odin..... Nope.
On my Mac, I have access to ADB and file manager. But there are no root tools for Mac.
On the S3 itself, I tried Towelroot v2, Saferoot, Framaroot, Kingo, ActiveRoot, MotoChop, that odd Chinese one, and more. They all failed.
I'd be more than happy on rooted stock, I was rocking that on my Skyrocket (pun intended) for a good 2-3 months, though I would prefer a custom ROM.
Sorry if this has been asked before.
Edit: I managed to get the drivers working by myself after reading about the registry issues.
I had an issue with a partial installation that the installer (or the computer) didn't like. Here is how I fixed it:
Manually reinstalling the Samsung USB Drivers (Windows)
First, open the file explorer (Pro tip: Hold the start button and press E) and in the address bar, type C:\Program Files\SAMSUNG\USB Drivers. If you see Uninstall.exe, right-click it, Run as Administrator, let it uninstall, and you can skip 7-10. Lucky. Otherwise...
Download 7-Zip and install it. I suggest 15.xx beta, the 9.xx is old.
Download the official universal USB driver from Samsung. Don't open it yet.
Now, find the driver ZIP file. This is most likely going to be in your Downloads folder as SAMSUNG_USB_Driver_for_Mobile_Phones.zip
Right-click on it and find 7-Zip > Open Archive...
Drag the file to your Downloads folder, and close 7-Zip.
Right-click on the EXE file with the similar name as the ZIP and do 7-Zip > Open archive...
Hit Extract and it should extract to a directory with the same name.
Open that folder and find the Uninstall.exe and Uninstall_1.exe.
If you're on a 64-bit installation, right click Uninstall_1.exe and select Run as Administrator. Otherwise, choose Uninstall.exe. (Google the way to find it if you are not sure).
Let it uninstall.
Now go back to your Downloads folder and right-click SAMSUNG_USB_Driver_for_Mobile_Phones.exe and Run as Administrator. This installation seems to take a very long time for some reason, don't panic.
Once that is done, you (hopefully) have drivers now! Plug in your phone and you should see "Installing driver software..." and it works!
Click to expand...
Click to collapse
Sent from my SGH-I747M using Tapatalk
You need to be in download mode on the phone, connect it to vista machine, launch Odin, flash twrp from Odin, boot into twrp, flash supersu from twrp, and you will have a rooted stock rom.
audit13 said:
You need to be in download mode on the phone, connect it to vista machine, launch Odin, flash twrp from Odin, boot into twrp, flash supersu from twrp, and you will have a rooted stock rom.
Click to expand...
Click to collapse
No, I can't get Odin to recognize my S3 (or my Skyrocket) in download mode. I tried.
Thanks, though.
Sent from my SGH-I747M using Tapatalk
Does it show up as an unknown device?
audit13 said:
Does it show up as an unknown device?
Click to expand...
Click to collapse
I get nothing. It doesn't see it.
Drivers are not working right or something. I installed Samsung drivers but, even still, each time I plug in my phone it asks to install drivers.
Sent from my SGH-I747M using Tapatalk
Tried different USB cables and USB ports? Doesn't even show up as a device in OS X?
audit13 said:
Tried different USB cables and USB ports? Doesn't even show up as a device in OS X?
Click to expand...
Click to collapse
Yes, yes.
OS X has ADB access and file access, but JOdin3 won't recognize the thing, and when I start it I get a message saying that heimdall-mac.dmg has no mountable filesystems or something.
Sent from my SGH-I747M using Tapatalk
What about running win7 in VMware? Or getting access to a win7 machine to try it out?
audit13 said:
What about running win7 in VMware? Or getting access to a win7 machine to try it out?
Click to expand...
Click to collapse
Can't afford a Win7 disk. But I may be able to try a friend's computer.
Sent from my SGH-I747M using Tapatalk
I ran into the same issue last night trying to root mine.
Win 7 would not install the correct drivers for my S3, I installed kies 3 just for the heck of it, and after that it picked up the correct driver for the S3. After that Odin picked it up right away after plugging it back in and I was able to flash TWRP on it. I installed Kies 1 first. Then Kies 3.
Give it a try, see if it works for you, I spent all day yesterday trying to get TWRP on it.
Good Luck!
Rooting I747m
I know it's answered, but here we go.
1. Flash TWRP.
2. Flash CF Auto-Root.
3. Flash TWRP again.
Done.
The i747m can be rooted by:
1) flashing cfautoroot without TWRP;
2) flashing TWRP, flashing supersu from TWRP; or
3) flashing TWRP, flashing custom rooted ROM from TWRP.
I am a New Pro3 owner, and a old XDA flasher. These days I just want stability and battery life. So given no one is getting OTA updates because the LeEco US office are... well about to close doors? Or at a minimum they are not maintaining the OTA servers as of today (09/06/2017 MM/DD/YEAR). I took it on myself to figure out how to get the updates and how to do them.
What you need:
These three files, nothing else.
5.8.019_sta.zip
5.8.020_sta.zip
5.8.021_sta.zip
Found here.
https://drive.google.com/open?id=0B2EAg2WU3OwpSHRMdEZ0Tks0a3M
It is very simple, but also very finicky.
1. Download 5.8.019_sta.zip, rename to update.zip
2. Place the update.zip on the root directory of your phone storage
3. Go to Settings -> System update (about 3/4 the way down)
4. Top right corner will see three vertical dots, tap the dots and select "local update" (see image)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. When you select "local update" if you did everything correct it should say "Update package found bla bla bla". Click continue.
That's it, it will load the file, reboot in to recovery and flash the file.
Then just follow this process for each file 19s->20s-21s. Make sure you remove the last update.zip before you put the new one in place.
Now, here is how it can be "finicky". For some reason using an android file manager to rename the files to "update.zip" corrupts the file in some way... and the update once you get in to the recovery section of the auto update fails. BEST PRACTICE IS TO DOWN LOAD THE FILES TO YOUR PC, THEN RENAME IT ON YOUR PC TO update.zip AND TRANSFER TO YOUR PHONES ROOT STORAGE.
Why? no clue, but you can try it either way... but if you find it failing try ^^
Hi, thanks for sharing the files, nuch appreciated.
For some reason I cannot acces the files today ?
bethe said:
Hi, thanks for sharing the files, nuch appreciated.
For some reason I cannot acces the files today ?
Click to expand...
Click to collapse
https://drive.google.com/drive/folders/0B2EAg2WU3OwpSHRMdEZ0Tks0a3M?usp=sharing
made a new sharable link
Hi and thanks for sharing. If you don't mind could you tell me
what's included in these updates?
dallorsj said:
Hi and thanks for sharing. If you don't mind could you tell me
what's included in these updates?
Click to expand...
Click to collapse
Just google "5.8.019_sta" (for each one)
You should be able to find the change-log somewhere.
Edward,
Works great! Just some notes for everyone else.
1) Make sure phone is set to MTP (Media Transfer Protocol).
2) If you are using Windows and are 'dragging and dropping' onto the device just copy to the phone icon in file explorer, that will put it at / which is where it needs to be.
3) When I did this and used the local update option, it didn't even prompt for 19S, it just moved forward and started the upgrade and rebooted the phone. All it asked me to confirm was right when I selected local update to 'make sure' I wanted to do it. No version check, etc. I was on 18S, btw.
Are you saying you went straight from 18s to 21s? Without the intermediary updates? Are you bootloader locked or unlocked?
Thanks for all of those OTAs. I was restoring my device to stock and every update kept failing when I tried to manually update it. Note: Update will fail if your OTA is not called update.zip.
IT IS CASE SENSITIVE; in other words, it will fail if you name is 'Update.zip'.
Thanks again and this post should be stickied tbh.
If my phone has twrp and on a custom rom could i use the same steps to go back to stock?
Sent from my LEX727 using XDA-Developers Legacy app
Ugh
I could not resist the $199 sale on Amazon despite knowing all the shortcomings. I am starting to regret this decision ... somewhat ... especially since Amazon no longer lets you return phones & can only exchange within 10 days.
Anyhow, I was excited when I got this phone the next day after I ordered it but my 1st frustration was that I could not do any system updates. I read about all the improvements like app drawer & really wanted them but no, it kept saying my system was up to date (still on 18 mind you). Which led me to this thread ... but now my computer will not recognize the Le Pro 3 when I connect it. I tried different USB ports & cords and no luck so far. I also cannot download the above links from my phone so I am kind of stuck @ the moment ...
I do, however, think that I got the work around for the notification issue as they seem to be coming in now, so that's good.
Overall, the phone mostly works so I am not totally mad at this purchase but getting the updates would be nice.
Quick Question: if I try to install Lineage OS, will the phone still have the T-Mobile wifi calling?
Thank you all for this super helpful forum for basic users like me.
UPDATE: Rebooting the phone got my computer to recognize the phone. However, I have followed all the instructions above (downloaded the file, renamed it update.zip, dragged & dropped it right on the phone in explorer, but it still will not find it with the local update.
I downloaded the Cheetah File Manger which shows you the Root Directory, which did not look like where I put mine. So I tried to move it over to the Root Directory but it would not let me paste it there. So close ...................................... calling it a night ...... sigh
i wanted to follow your guidelines but there is no system update in settings in my device. i ve bought it from banggood if that info is useful.
Could you please add check sums for these files.
Thanks in advance!
Try to update my X727 from 5.8.018s to 5.8.019s:
1. Renamed 5.8.019_sta.zip to update.zip and copied it to phone root.
2. From File Manager pressed on update.zip and choose "Upgrade", it has started updating "Upgrading, do not power off the phone".
3. The phone rebooted and entered to Recovery with an error message: "Failed to update! Cause: Installation failed"
4. Presses Back-button and tried again "Update system" and got an error message "Failed to update! Cause: APK not found"
What's wrong?