Got my ROG phone 6 unlocked, rooted with latest magisk but however I can't get root explorer to mount R/W on root directory to get COUNTRY file changed from CN to WW permanently as i'm still in R/O can't write the COUNTRY file..
Although I could save the file but device info HW app shows my fingerprint is still CN..
I'm only able to manually update WW version once and 2nd update had received "system update failed" likely due to fingerprint isn't changed.
Had my root checker checked too, tried multiple root explorer versions & other file manager with root access but all unable to mount R/W
Some file manager also showed "file is read-only"
I also did a few research and tried a few ADB commands to mount R/W but unable to get it working neither..
It seems like there's no solution for this..
anybody having the same issue? any solution?
Try raw update.
udar_molota said:
Try raw update.
Click to expand...
Click to collapse
Dont have any raw file to update.. would need to find or wait for someone else to release it..
However, I did a reflash of the current raw I have but my fingerprint still remained same as CN..
finallau said:
Dont have any raw file to update.. would need to find or wait for someone else to release it..
However, I did a reflash of the current raw I have but my fingerprint still remained same as CN..
Click to expand...
Click to collapse
Here
udar_molota said:
Here
Click to expand...
Click to collapse
Wow thanks!
Did you managed to fully convert your fingerprint from CN to WW?
You can check this via device info HW app in "system" tab.
If yes, then i'd deeply appreciate if you could tell me how you managed to do it..
I know my COUNTRY file does still remained as WW even after i did a factory reset/reflash raw but I just can't seem to figure out why my fingerprint isn't changed..
I followed some YT tutorials I found and followed exactly what they did but of course using ROG phone 6 files and it din't turned out to be the same for the fingerprint...
udar_molota said:
Here
Click to expand...
Click to collapse
I tried running flashall_AFT.cmd and it pops out CMD and immediately disappears..
Reboot pc & phone, CMD shows my device is listed in fastboot devices but i'm unable to execute the file neither flash_raw_and_wipedata.CMD works...
finallau said:
I tried running flashall_AFT.cmd and it pops out CMD and immediately disappears..
Reboot pc & phone, CMD shows my device is listed in fastboot devices but i'm unable to execute the file neither flash_raw_and_wipedata.CMD works...
Click to expand...
Click to collapse
I got my Tencent with WW already, so less problems with the converting.
1. Your PC see you phone when connected and powered on?
2. Are you using side usb?
3. This is WW raw, if your phone says CN version, so nothing to do with my link
Maybe this can help you? It's called different than WW, but maybe it's good for you, the website says it's CN raw files.
udar_molota said:
I got my Tencent with WW already, so less problems with the converting.
1. Your PC see you phone when connected and powered on?
2. Are you using side usb?
3. This is WW raw, if your phone says CN version, so nothing to do with my link
Click to expand...
Click to collapse
Yea all checked. I have did a raw flash before but this time it failed no matter how many times i tried..
I'll try flash back the old raw i have and then try flash this raw update hopefully it works..
Related
I just downloaded to my XT1575 and I don't know which directory it downloaded to? Any ideas?
glfngmble said:
I just downloaded to my XT1575 and I don't know which directory it downloaded to? Any ideas?
Click to expand...
Click to collapse
/data/data/org.lineageos.updater/app_updates
jhedfors said:
/data/data/org.lineageos.updater/app_updates
Click to expand...
Click to collapse
Thank You.
There is no folder /app_updates. There is just a folder named "files", but this folder is completely empty.
By the way: I got this file structure on my G4: \Android\data\org.lineageos.updater\files.
I had to manually download the package and install it manually in recovery, but the updater says still to update the current version.
rigattoni said:
There is no folder /app_updates. There is just a folder named "files", but this folder is completely empty.
By the way: I got this file structure on my G4: \Android\data\org.lineageos.updater\files.
I had to manually download the package and install it manually in recovery, but the updater says still to update the current version.
Click to expand...
Click to collapse
/data/data/org.lineageos.updater/app_updates
The updater does not recognize what version is installed, just if the update is in the folder.
jhedfors said:
/data/data/org.lineageos.updater/app_updates
The updater does not recognize what version is installed, just if the update is in the folder.
Click to expand...
Click to collapse
If this is reduced to this single folder I can say that my G4 has no folder with this name.
The download completed and the updater asks for updating the unit.
The G4 restarts into recovery mode and nothing happens. Manual search for the downloaded files have not been successful.
I restarted my G4 and searched manually with root rights (just to be sure the files are not hidden in non root search) and I could not find any update file.
The lineage updater still shows to update the phone, even that there whether is a folder named "/data/org.lineageos.updater/app_updates"
nor a file in the "\data\org.lineageos.updater\files.
So... is this an issue with the updater, ROM or is this just not implemented complete?
I have no issues to manually install anything by console or TWRP or what ever else.
Once again: The update file(s) seem to be lost in transit. They are not stored on the system.
The updater still shows the install button even if there is nothing to install.
rigattoni said:
If this is reduced to this single folder I can say that my G4 has no folder with this name.
The download completed and the updater asks for updating the unit.
The G4 restarts into recovery mode and nothing happens. Manual search for the downloaded files have not been successful.
I restarted my G4 and searched manually with root rights (just to be sure the files are not hidden in non root search) and I could not find any update file.
The lineage updater still shows to update the phone, even that there whether is a folder named "/data/org.lineageos.updater/app_updates"
nor a file in the "\data\org.lineageos.updater\files.
So... is this an issue with the updater, ROM or is this just not implemented complete?
I have no issues to manually install anything by console or TWRP or what ever else.
Once again: The update file(s) seem to be lost in transit. They are not stored on the system.
The updater still shows the install button even if there is nothing to install.
Click to expand...
Click to collapse
Are you sure you are looking in the right folder? Your stated path shows :
"\data\org.lineageos.updater"
Was that just a typo?
This where it is in my device:
"/data/data/org.lineageos.updater/app_updates" (note the nested "data" in "data")
Also, I think that if it shows "install" it means that it has been downloaded (and exist), otherwise it would show "download".
jhedfors said:
Are you sure you are looking in the right folder? Your stated path shows :
"\data\org.lineageos.updater"
Was that just a typo?
This where it is in my device:
"/data/data/org.lineageos.updater/app_updates" (note the nested "data" in "data")
Also, I think that if it shows "install" it means that it has been downloaded (and exist), otherwise it would show "download".
Click to expand...
Click to collapse
Shame on me... I searched with root rights and could not find the folder.... Seems I need new glasses.
But the folder is there and yes, the download is in there.
So single issue is, why the updater does not call the update automatically for flashing the update.
rigattoni said:
Shame on me... I searched with root rights and could not find the folder.... Seems I need new glasses.
But the folder is there and yes, the download is in there.
So single issue is, why the updater does not call the update automatically for flashing the update.
Click to expand...
Click to collapse
Hmmm... TWRP should be able to handle the script created by the updater. You may want to check on the G4 forum to see if others have the same issue.
jhedfors said:
Hmmm... TWRP should be able to handle the script created by the updater. You may want to check on the G4 forum to see if others have the same issue.
Click to expand...
Click to collapse
the guys in the G4 forum are mostly connected to the unofficial version. a complete manual installation is required.
But there are some rumors in the German forum, who are using the official LineAgeOS version, where the updater script is not working.
I´ll wait for the next update in a week... may be it´s just a minor issue which will be fixed soon.
is it possible to change that path?
The path *HAS* been changed.
It's now downloading OTA updates to /data/lineageos_updates
Which a pain in the ass, because TWRP already doesn't automatically handle the script as expected on my Note3, and, I'd already gotten used to having to go to /data/data/org.lineageos.updates.
Hrmph.
darrylhadfield said:
The path *HAS* been changed.
It's now downloading OTA updates to /data/lineageos_updates
Which a pain in the ass, because TWRP already doesn't automatically handle the script as expected on my Note3, and, I'd already gotten used to having to go to /data/data/org.lineageos.updates.
Hrmph.
Click to expand...
Click to collapse
Thank you!!!! :victory::victory::victory: It works!!
rarmz said:
Thank you!!!! :victory::victory::victory: It works!!
Click to expand...
Click to collapse
Happy to help!
Now, if I can just get the attention of whoever the device maintainer is, for the Note3, to figure out the TWRP scripting issue...
From The Moderator Oka1 - There are no viable links in this OP therefore, I am closing
Thanks
OK. As i promise to some nice people here, then i get it so here it is.
ADB sideload only update S4CQB2-to-U4EQC6. 1.41 GB file seems to me like nougat update.
Nougat Update Here S4CQB2-to-U4EQC6
MD5 checksum : 903aa5c5f26f430133481c4a2cfcdb69
Thanks for ABD instruction @ColoMtn
Make sure you know how to ADB sideload. I'm not responsible for any damage to your phone.
Steps:
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and file is ready for ADB as you download SS-N920AUCS4CQB2-to-U4EQC6-UP.zip
3. Shutdown your phone
4. Enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd
in my case: cd C:\Users\Norbarb\Desktop\Note5
8. Navigate to the directory that contains the update ‘SS-N920AUCS4CQB2-to-U4EQC6-UP.zip’
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Norbarb\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
10.Type adb sideload SS-N920AUCS4CQB2-to-U4EQC6-UP.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Nougat
EDIT: Please post mirrors if you can. Thanks
For who may need it this is S4CQA1 to U4QC6 update. File is around 1.5 GB and MD5 is 23d4d4c58330b618001e76fc468732d9
Congratulations! Hopefully 928a will have it soon
vista1984 said:
Congratulations! Hopefully 928a will have it soon
Click to expand...
Click to collapse
You are talking about G928A ? I check but only what i get is security update to 4CQB1. If you want i can post it on S6E+ forum.
I just wanted to thank you for this, going to do it now!!!! This day keeps getting better and better!!!!!
norbarb said:
OK. As i promise to some nice people here, then i get it so here it is.
ADB sideload only update S4CQB2-to-U4EQC5. 1.41 GB file seems to me like nougat update.
Nougat Update Here
Thanks for ABD instruction @ColoMtn
Steps:
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and file is ready for ADB as you download SS-N920AUCS4CQB2-to-U4EQC5.zip
3. Shutdown your phone
4. Enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd
in my case: cd C:\Users\Norbarb\Desktop\Note5
8. Navigate to the directory that contains the update ‘SS-N920AUCS4CQB2-to-U4EQC5.zip’
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Norbarb\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
10.Type adb sideload SS-N920AUCS4CQB2-to-U4EQC5.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Nougat
EDIT: Please post mirrors if you can. Thanks
Click to expand...
Click to collapse
Can anyone show a screen shot of the "About Device" section of the phone settings after applying this update? Thank you in advance!
Have you tried it yourself?I got this in recovery when adb it.
" failed to verify whole-file signature", "signature verification failed
"E:failed to verify whole-life signature" "E:signature verification failed"
Installation aborted.
ifanr said:
Have you tried it yourself?I got this in recovery when adb it.
" failed to verify whole-file signature", "signature verification failed
"E:failed to verify whole-life signature" "E:signature verification failed"
Installation aborted.
Click to expand...
Click to collapse
On what firmware currently are you? This update is only from baseband N920AUCS4CQB2. Also you may have corrupted recovery. To fix this you have to ODIN back to latest firmware and try again.
Anyway just in case i'm uploading raw file w/o .zip extension to another place.
norbarb said:
On what firmware currently are you? This update is only from baseband N920AUCS4CQB2. Also you may have corrupted recovery. To fix this you have to ODIN back to latest firmware and try again.
Anyway just in case i'm uploading raw file w/o .zip extension to another place.
Click to expand...
Click to collapse
It's S4CQB2.Could you please give me the md5?And I'm gonna to flash the recovery to work it out.
ifanr said:
It's S4CQB2.Could you please give me the md5?And I'm gonna to flash the recovery to work it out.
Click to expand...
Click to collapse
I post it MD5 in first post.
norbarb said:
I post it MD5 in first post.
Click to expand...
Click to collapse
Matched.I'll try some other ways to work it out.Tks.
ifanr said:
Matched.I'll try some other ways to work it out.Tks.
Click to expand...
Click to collapse
You may try removing .zip extension and try again. Sometimes works
i get cannot read SS-N920AUCS4CQB2-to-U4EQC5.zip
jerrycoffman45 said:
i get cannot read SS-N920AUCS4CQB2-to-U4EQC5.zip
Click to expand...
Click to collapse
Two resons :
1. corrupted file
2. file in wrong place
norbarb said:
Two resons :
1. corrupted file
2. file in wrong place
Click to expand...
Click to collapse
The file may corrupted.When I use winrar to unzip this file.It says there is a checksum error occurred in system\priv-app\Lookout_ATT\oat\arm\Lookout_ATT.odex. The file is corrupt.
I tried your ways but did not work out.
norbarb said:
Two resons :
1. corrupted file
2. file in wrong place
Click to expand...
Click to collapse
thats what i thought too but md5 checks and the files in the same folder as adb and fastboot
ifanr said:
The file may corrupted.When I use winrar to unzip this file.It says there is a checksum error occurred in system\priv-app\Lookout_ATT\oat\arm\Lookout_ATT.odex. The file is corrupt.
I tried your ways but did not work out.
Click to expand...
Click to collapse
I post it link to raw file try other one or re-download.
ifanr said:
The file may corrupted.When I use winrar to unzip this file.It says there is a checksum error occurred in system\priv-app\Lookout_ATT\oat\arm\Lookout_ATT.odex. The file is corrupt.
I tried your ways but did not work out.
Click to expand...
Click to collapse
jerrycoffman45 said:
thats what i thought too but md5 checks and the files in the same folder as adb and fastboot
Click to expand...
Click to collapse
Most of the time it is problem do to recovery. You may have to ODIN firmware back and try again.
Anybody flash this file w/o problems? I'm sorry but only Note 5 i have it is my wife's work phone and i can't mess with it.
norbarb said:
Most of the time it is problem do to recovery. You may have to ODIN firmware back and try again.
Anybody flash this file w/o problems? I'm sorry but only Note 5 i have it is my wife's work phone and i can't mess with it.
Click to expand...
Click to collapse
I'll try it. Looks I already messed up my phone.Lucky it's weekend.lol.
ifanr said:
I'll try it. Looks I already messed up my phone.Lucky it's weekend.lol.
Click to expand...
Click to collapse
ALL WHO TRY PLEASE STOP. Seems like uploaded file got corrupted. I'm uploading once more
norbarb said:
You are talking about G928A ? I check but only what i get is security update to 4CQB1. If you want i can post it on S6E+ forum.
Click to expand...
Click to collapse
It's very thoughtful of you. If you have time please post it at your convenience.
Guys i tried to install MIUI 7 on my amazon firephone i downloaded all the files and did a reboot in recover all going good then when i tried to install miui files it got stuck in the recovery mood and i restarted the phone and now it is stucked on amazon logo nothing doing else even i tried wipe data twice from hard reset mood please help did it brick my phone? help me to solve this.
hamza said:
Guys i tried to install MIUI 7 on my amazon firephone i downloaded all the files and did a reboot in recover all going good then when i tried to install miui files it got stuck in the recovery mood and i restarted the phone and now it is stucked on amazon logo nothing doing else even i tried wipe data twice from hard reset mood please help did it brick my phone? help me to solve this.
Click to expand...
Click to collapse
if you can acces to recovery, the only thing you can do is adb sideload ...bin
with an original stock ROM for your fire phone
(.bin must be the extension of the file, that you can get from official amazon site)
pipataki said:
if you can acces to recovery, the only thing you can do is adb sideload ...bin
with an original stock ROM for your fire phone
(.bin must be the extension of the file, that you can get from official amazon site)
Click to expand...
Click to collapse
Thanks a lot for your help after starting this thread i did a lot of research about it and i got the same solution from Xda and i tried it is same manner as some nice people posted it on this site but now another issue is being created automatically which is adb sideload command is not working when i write the following command
adb sideload "filename.bin"
its shows me an error "*cannot read filename.bin"
i tried it by changing the file name as "update.bin" and also tried it same file name which i downloaded from the amazon site. Please help me to resolve issue. Thanks again.
hamza said:
Thanks a lot for your help after starting this thread i did a lot of research about it and i got the same solution from Xda and i tried it is same manner as some nice people posted it on this site but now another issue is being created automatically which is adb sideload command is not working when i write the following command
adb sideload "filename.bin"
its shows me an error "*cannot read filename.bin"
i tried it by changing the file name as "update.bin" and also tried it same file name which i downloaded from the amazon site. Please help me to resolve issue. Thanks again.
Click to expand...
Click to collapse
filename is the name of file... <file.bin> you have to download that file from amazon or see in index thread
pipataki said:
filename is the name of file... <file.bin> you have to download that file from amazon or see in index thread
Click to expand...
Click to collapse
yeah i downloaded the file from amazon site and its original name was "update-kindle-35.4.6.6_user_466001420.bin" but i changed it to "update.bin" and it didn't work.
hamza said:
yeah i downloaded the file from amazon site and its original name was "update-kindle-35.4.6.6_user_466001420.bin" but i changed it to "update.bin" and it didn't work.
Click to expand...
Click to collapse
its still not working still showing that error "cannot read file.bin"
hamza said:
its still not working still showing that error "cannot read file.bin"
Click to expand...
Click to collapse
If you have the device via adb (with adb devices command) you can do an adb sideload sure... so in your case I supose, the file is corrupted... better dont rename it... but, if you can connect via adb, you can sideload sure...
pipataki said:
If you have the device via adb (with adb devices command) you can do an adb sideload sure... so in your case I supose, the file is corrupted... better dont rename it... but, if you can connect via adb, you can sideload sure...
Click to expand...
Click to collapse
no file was not corrupted because i downloaded another file from another site and it is showing same error i really cant understand what is happening. Is there any administration need?
hamza said:
no file was not corrupted because i downloaded another file from another site and it is showing same error i really cant understand what is happening. Is there any administration need?
Click to expand...
Click to collapse
did you do adb devices first?... first you have to know if adb can connet with the device... that will be listed with that command... adb devices
if you want send an screenshot with the result of making adb devices
Try to sideload what version of fire os you had before MIUI upgrade. If you had fireos 4.6.6, sideload 4.6.6, if you had 3.6.5 sideload 3.6.5
ozan2 said:
Try to sideload what version of fire os you had before MIUI upgrade. If you had fireos 4.6.6, sideload 4.6.6, if you had 3.6.5 sideload 3.6.5
Click to expand...
Click to collapse
i was having 4.6.6 and i sideloaded this version i am shocked that all things i am doing are totally good but why this error is occuring
hamza said:
i was having 4.6.6 and i sideloaded this version i am shocked that all things i am doing are totally good but why this error is occuring
Click to expand...
Click to collapse
I think that here in my computer I have the original update of Stock Rom, If you want I can upload it to my shared folder...
(left 3 hours and 5 minutes, maybe)...
to be sure that the upload and the download then is rigth, I tell you the exactly weight of file...
1314263238 bytes, you can test if the file you had has the same weight...
pipataki said:
I think that here in my computer I have the original update of Stock Rom, If you want I can upload it to my shared folder...
(left 3 hours and 5 minutes, maybe)...
to be sure that the upload and the download then is rigth, I tell you the exactly weight of file...
1314263238 bytes, you can test if the file you had has the same weight...
Click to expand...
Click to collapse
Size of my file is 1.2 GBs which is approximately equal to your file as you told me. I actually download it from amazon original site not any third party site but yeah upload it and please give me the link i will surely be thankful to you. I really appreciate your help and really happy to be new here at Xda developer.
hamza said:
Size of my file is 1.2 GBs which is approximately equal to your file as you told me. I actually download it from amazon original site not any third party site but yeah upload it and please give me the link i will surely be thankful to you. I really appreciate your help and really happy to be new here at Xda developer.
Click to expand...
Click to collapse
is uploaded totally...
the url of shared folder is in my Lollipop thread...
Are you accesing sideload by recovery?...
sideload only works invoked in recovey of the phone, in safestrap or in stock recovery
pipataki said:
is uploaded totally...
the url of shared folder is in my Lollipop thread...
Are you accesing sideload by recovery?...
sideload only works invoked in recovey of the phone, in safestrap or in stock recovery
Click to expand...
Click to collapse
Yes I am accessing it through phone recovery because i cant turn my phone on thats why i cant use safestap thats why i put my phone on recovery mood and selects install from adb option then from laptop i open console by pressing nd holding shift and right click and selecting open command prompt where my original amazon rom is placed then i use to write the sideload command which is adb sideload <filename.bin> and the then it shows error *cannot read <filename.bin>
That is all the procedure what i do everytime and it get failed please let me know if i am doing any thing wrong in it. Thank you
hamza said:
Yes I am accessing it through phone recovery because i cant turn my phone on thats why i cant use safestap thats why i put my phone on recovery mood and selects install from adb option then from laptop i open console by pressing nd holding shift and right click and selecting open command prompt where my original amazon rom is placed then i use to write the sideload command which is adb sideload <filename.bin> and the then it shows error *cannot read <filename.bin>
That is all the procedure what i do everytime and it get failed please let me know if i am doing any thing wrong in it. Thank you
Click to expand...
Click to collapse
Try using another wire and/or another port and/or another file... (the original stock that I had is in my shared folder, that one for exemple or any other one)... I hope you could relive it...
pipataki said:
Try using another wire and/or another port and/or another file... (the original stock that I had is in my shared folder, that one for exemple or any other one)... I hope you could relive it...
Click to expand...
Click to collapse
Thank You so much for your such response got it okay the problem was i didn't unblock the update file which dont know earlier but as you reffer me another link i worked on it and i got my phone back. Once again thank you so much it was really nice to be here. I will suggest all my friends your site.
hamza said:
Thank You so much for your such response got it okay the problem was i didn't unblock the update file which dont know earlier but as you reffer me another link i worked on it and i got my phone back. Once again thank you so much it was really nice to be here. I will suggest all my friends your site.
Click to expand...
Click to collapse
you can go to mobile shop and it will cost only 200 to 300 rupee for software, i also had this issue (soft brick) then i tried alot but finally i go to mobile shop and install the software ..
hamza said:
Yes I am accessing it through phone recovery because i cant turn my phone on thats why i cant use safestap thats why i put my phone on recovery mood and selects install from adb option then from laptop i open console by pressing nd holding shift and right click and selecting open command prompt where my original amazon rom is placed then i use to write the sideload command which is adb sideload <filename.bin> and the then it shows error *cannot read <filename.bin>
That is all the procedure what i do everytime and it get failed please let me know if i am doing any thing wrong in it. Thank you
Click to expand...
Click to collapse
Hello,
This may be a stupid question but did you specify the proper path? ie: c:\'filename"
just a shot, good luck
slim1001 said:
Hello,
This may be a stupid question but did you specify the proper path? ie: c:\'filename"
just a shot, good luck
Click to expand...
Click to collapse
Yes man, his phone is recovered and I had this error, solution for "cannot read" is here: https://forum.xda-developers.com/fire-phone/help/adb-sideload-error-read-t3634246
Hi folks,
I got my RN5 AI Global a couple of days ago and I want to give Lineage OS a spin. Then I read about this dreaded feature of Google called "ARB" - a developer's nightmare!
My current version is 9.5.17 on my phone. When I change into settings I can see that 9.5.19 has been downloaded and is ready for installation, the only action I have to do is reboot. Since 9.5.19 carries ARB feature, I do not power down my phone in order not to install this fix.
So guys, here is my question: Is there any way I can prevent this update from installing on my phone?
Best wishes,
DFahren
Don't install it?
Just power down and go straight to fastboot (power+voldown) then use mi unlock to unlock then flash lineage after doing twrp.
Not that it would matter too much having 9.5.19 since you can bypass it blocking fastboot commands with the arbypass.img file
Nice idea. However my Mi account is not (yet) eligible for unlocking .... This will take 14 days, I suppose.
Delete the update from internal storage/downloaded_rom
And also turn off automatic updates so you don't get it again.
"If you are on MIUI 9, then:
- Go to Settings
- About Phone
- System Updates
- Click on 3 dots above right
- Turn Off both "Download Automatically" and "Download using Mobile Data"."
And you should be able to reboot your device.
Ok, what you are basically saying is: open a CMD on Windows, issue an "adb shell" and in this shell do a "cd xxx/storage/downloaded_rom; rm *", right?!
I have to do this because I do not see this folder downloaded_rom when using MIUI's filemanager. Correct?
Cheers, Dfahren
corkiejp said:
Delete the update from internal storage/downloaded_rom
And also turn off automatic updates so you don't get it again.
"If you are on MIUI 9, then:
- Go to Settings
- About Phone
- System Updates
- Click on 3 dots above right
- Turn Off both "Download Automatically" and "Download using Mobile Data"."
And you should be able to reboot your device.
Click to expand...
Click to collapse
@dfahren
Maybe try a different file manager than stock.
Someone else reported on another forum that they deleted the downloaded update.
Not sure how exactly, I will message them and find out how.
dfahren said:
Ok, what you are basically saying is: open a CMD on Windows, issue an "adb shell" and in this shell do a "cd xxx/storage/downloaded_rom; rm *", right?!
I have to do this because I do not see this folder downloaded_rom when using MIUI's filemanager. Correct?
Cheers, Dfahren
Click to expand...
Click to collapse
corkiejp said:
@dfahren
Maybe try a different file manager than stock.
Someone else reported on another forum that they deleted the downloaded update.
Not sure how exactly, I will message them and find out how.
Click to expand...
Click to collapse
I deleted the update zip file using solid explorer.
Sent from my Redmi Note 5 using Tapatalk
....deleted ....
gsmyth said:
I deleted the update zip file using solid explorer.
Click to expand...
Click to collapse
Yeah, that's also a good way to get rid of the update.
I used ADB with installed drivers. However path to the update was ..../sdcard/downloaded_rom , but that's a minor. Just wanted to let you guys know.
Orginal Title: Sprint LG V50 may get Android 10 beta by End of 2019 (V450PM)
I saw this article here: https://www.mylgphones.com/sprint-lg-v50-thinq-5g-android-10-update-will-release-soon.html?amp
Leaked Frimware details:
Model:LM-V450PM
Size:1508.11MB
Android Pie 9.0: LMV450PMAT-V10p-310-120-SEP-19-2019-ARB00+0
Android 10 Beta: LMV450PMAT-V18a-310-120-OCT-29-2019-ARB00+1
File name: LMV450PM-V10p-310-to-LMV450PM-V18a-310.up
Click to expand...
Click to collapse
The article source won't release the beta frimware though. Anybody know where/how to get this or convince them to share it? However though, this is great news!
Edit: Special Thanks to chortya for purchasing the file. The link to download the file comes from the domain dl01.gdms.lge.com which is a legit source from LG directly. The file received is a .mo file, you just rename it to get a .up file. chortya has graciously shared the OTA file in the mega.nz link below!
chortya said:
https://mega.nz/#!gjJi3KiK!ebsQdxmnXtEYRiG69F5oAlVqNnsZ3c9D7SpWahGI8OQ
even patch name stipulates specific old firmmware version. And yes, I am on v10p.
Click to expand...
Click to collapse
Now lets figure out how to flash it!
Edit 2: Wow, that was fast! Thanks to aiap for figuring out how to flash this OTA.
aiap said:
SUCCESS!
I ended up not using LGUP, instead this is how I did it. (Make sure to backup, for some reason I had to factory reset because mine was stuck rebooting after "android is installing" notification completed.)
STEPS:
1. Download .up file: https://mega.nz/#!gjJi3KiK!ebsQdxmnXtEYRiG69F5oAlVqNnsZ3c9D7SpWahGI8OQ (thanks @chortya)
2. Rename file to LGUP_FOTA.up
3. Place file in root of internal storage on V50.
4. Download "Activity Launcher" from Play Store
5. Find FOTA Update
6. Hit the first option (com.lge.lgfota.permission.FotaTestActivity)
7. Follow prompts.
Click to expand...
Click to collapse
Edit 3: Some screenshots thanks to @aiap
https://forum.xda-developers.com/v5...-beta-2019-t3995429/post80870307#post80870307
I may have found the firmware on a LG firmware site called LGBBS. If someone knows how to purchase from Alipay and risk 50 yuan ($7.10 USD) and would be willing to share the file on Google Drive or so: http://www.lgbbs.com/plugin.php?id=lg_ota&lg_ota=fwbuy&fwid=LCmN1NXswX8eTAJVn1Dhsg==
andrewwm said:
I may have found the firmware on a LG firmware site called LGBBS. If someone knows how to purchase from Alipay and risk 50 yuan ($7.10 USD) and would be willing to share the file on Google Drive or so: http://www.lgbbs.com/plugin.php?id=lg_ota&lg_ota=fwbuy&fwid=LCmN1NXswX8eTAJVn1Dhsg==
Click to expand...
Click to collapse
Maybe you could ask @ngocgiap32 to help you and donate to him... he gave us for free the other 3 korean otas:good::highfive:
Inerent said:
Maybe you could ask @ngocgiap32 to help you and donate to him... he gave us for free the other 3 korean otas:good::highfive:
Click to expand...
Click to collapse
I'd donate. I tried creating an Alipay account but when I went to pay, it wanted a Chinese bank card.
any news?
Hell, I got $7!
hooutoo said:
Hell, I got $7!
Click to expand...
Click to collapse
did u got the rom?
No I'm just saying I would happily contribute the $7
I am not able to install it. Tried multiple options:
- LGUP FOTA upgrade - device protected error
- recovery mode - both SD card recovery and adb are not working. SD card mounting fails and it seems that my V50 is not connecting to PC if in recovery mode so adb does not see it. adb works fine with phone fully booted, so developer options are enabled and phone is authenticated with pc
- lgup_cmd does not even recognize *.up files
Any thoughts?
Does it make sense to move this to the kernel/firmware section?
chortya said:
I am not able to install it. Tried multiple options:
- LGUP FOTA upgrade - device protected error
- recovery mode - both SD card recovery and adb are not working. SD card mounting fails and it seems that my V50 is not connecting to PC if in recovery mode so adb does not see it. adb works fine with phone fully booted, so developer options are enabled and phone is authenticated with pc
- lgup_cmd does not even recognize *.up files
Any thoughts?
Does it make sense to move this to the kernel/firmware section?
Click to expand...
Click to collapse
how did u got the rom?
Paid 50 RMB.
chortya said:
Paid 50 RMB.
Click to expand...
Click to collapse
and they did not explain how to install?
chortya said:
I am not able to install it. Tried multiple options:
- LGUP FOTA upgrade - device protected error
- recovery mode - both SD card recovery and adb are not working. SD card mounting fails and it seems that my V50 is not connecting to PC if in recovery mode so adb does not see it. adb works fine with phone fully booted, so developer options are enabled and phone is authenticated with pc
- lgup_cmd does not even recognize *.up files
Any thoughts?
Does it make sense to move this to the kernel/firmware section?
Click to expand...
Click to collapse
Yes. You must flash it with LG-UP 1.16.0.3.
Install lg USB drivers 4.4.2
Install lgup 1.16.0.3
Install lg common dll 1.40
Download and Copy the ui config file (from the LG-UP thread here on the forum) and paste it where the common dll is.
Then enable USB debugging in dev options
Then connect to pc
Then start lg up
Then chose FOTA upgrade
Then load your android 10 beta fota file. Make sure it has. Up extension
Then click start on lgup. Wait for the minute and it should start flashing.
chortya said:
Paid 50 RMB.
Click to expand...
Click to collapse
Can you share it over Google drive? Also did they have firmware for g8?
Inerent said:
Yes. You must flash it with LG-UP 1.16.0.3.
Install lg USB drivers 4.4.2
Install lgup 1.16.0.3
Install lg common dll 1.40
Download and Copy the ui config file (from the LG-UP thread here on the forum) and paste it where the common dll is.
Then enable USB debugging in dev options
Then connect to pc
Then start lg up
Then chose FOTA upgrade
Then load your android 10 beta fota file. Make sure it has. Up extension
Then click start on lgup. Wait for the minute and it should start flashing.
Click to expand...
Click to collapse
did you test it?
Inerent said:
Yes. You must flash it with LG-UP 1.16.0.3.
Install lg USB drivers 4.4.2
Install lgup 1.16.0.3
Install lg common dll 1.40
Download and Copy the ui config file (from the LG-UP thread here on the forum) and paste it where the common dll is.
Then enable USB debugging in dev options
Then connect to pc
Then start lg up
Then chose FOTA upgrade
Then load your android 10 beta fota file. Make sure it has. Up extension
Then click start on lgup. Wait for the minute and it should start flashing.
Click to expand...
Click to collapse
My setup is exactly as you described. I need to check the version if the USB driver, but don't think this will improve anything.
As I have written I am getting "protected device" error.
My V50 is locked, does it have any influence?
chortya said:
My setup is exactly as you described. I need to check the version if the USB driver, but don't think this will improve anything.
As I have written I am getting "protected device" error.
My V50 is locked, does it have any influence?
Click to expand...
Click to collapse
If you have the right ota it should work.
And also the correct security patch. Maybe this is why it's not working...
Inerent said:
If you have the right ota it should work.
And also the correct security patch. Maybe this is why it's not working...
Click to expand...
Click to collapse
did u tried?
Inerent said:
If you have the right ota it should work.
And also the correct security patch. Maybe this is why it's not working...
Click to expand...
Click to collapse
Can you explain why the security patch matters or why u can only fota upgrade from certain firmwares?
https://mega.nz/#!gjJi3KiK!ebsQdxmnXtEYRiG69F5oAlVqNnsZ3c9D7SpWahGI8OQ
---------- Post added at 09:07 AM ---------- Previous post was at 09:06 AM ----------
antintin said:
Can you explain why the security patch matters or why u can only fota upgrade from certain firmwares?
Click to expand...
Click to collapse
even patch name stipulates specific old firmmware version. And yes, I am on v10p.