NOTE: MAKE SURE THE MOTOROLA DRIVERS ARE INSTALLED AND THE ADB IS ISTALLED.
1ST : go to your phones fastboot mode then flash this firmware using flashfile.bat in the folder and wait until finished. CN FIRMWARE LINK:
File folder on MEGA
mega.nz
2ND : download eu rom from here : https://mirrors.lolinet.com/firmwar...-DEFAULT_regulatory-DEFAULT_cid50_CFC.xml.zip
3RD : in the folder where you extracted the EU FIRMWARE open a adb powershell window. then flash this.
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot erase apdp
fastboot erase apdpb
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot reboot
If you got this error from fastboot flash partition gpt.bin ignore it.
Sending 'partition' (206 KB) OKAY [ 0.007s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
if you got this error from fastboot flash bootloader bootloader.img ignore it just flash.
Sending 'bootloader' (27637 KB) OKAY [ 0.841s]
Writing 'bootloader' (bootloader) no suitable package!
FAILED (remote: '')
fastboot: error: Command failed
after those 2 all systems go.
after the phone has finished booting up. disable the moto app since it has a buggy lockscreen feature.
IF YOU DONT WANT ANYMORE OR YOU HAD A BOOTLOOP. YOU CAN ALWAYS GO BACK TO THE CHINESE FIRMWARE.
Donate me a little money. I hope I can help you guys even more soon. THANKS!
Donate to Elmer Gien Gomez
Help support Elmer Gien Gomez by donating or sharing with your friends.
www.paypal.com
Thank you for tutorial.
Does 5g and NFC work fine ?
مجــاهدـــــ said:
Thank you for tutorial.
Does 5g and NFC work fine ?
Click to expand...
Click to collapse
NFC no
Dope, didnt think it was that easy, coming from the Vivo x70 Pro Plus. Will try this on the x30 pro when the global is launched.
Do OTA updates work?
Killuminati91 said:
Dope, didnt think it was that easy, coming from the Vivo x70 Pro Plus. Will try this on the x30 pro when the global is launched.
Do OTA updates work?
Click to expand...
Click to collapse
On CN yes.
On global?
Killuminati91 said:
On global?
Click to expand...
Click to collapse
i dont know because thats the latest firmware right now.
Hi
Does this Chinese firmware have Google play?
you don't flash the radio ?
''after the phone has finished booting up. disable the moto app since it has a buggy lockscreen feature.''
I disabled or uninstalled the Moto APP,it still have a very big problem.I cant unlock my phone.I cant use my phone at all!
hk56184172 said:
''after the phone has finished booting up. disable the moto app since it has a buggy lockscreen feature.''
I disabled or uninstalled the Moto APP,it still have a very big problem.I cant unlock my phone.I cant use my phone at all!
Click to expand...
Click to collapse
How about YouTube video? Is any lag on It?
hk56184172 said:
''after the phone has finished booting up. disable the moto app since it has a buggy lockscreen feature.''
I disabled or uninstalled the Moto APP,it still have a very big problem.I cant unlock my phone.I cant use my phone at all!
Click to expand...
Click to collapse
there is an app called Moto Display . disable it, remove the update from the market and stop the auto update
I've tried this method on my x30 Pro / Edge 30 Ultra. After the initial setup and accepting Google terms there is a black screen with a non-working back button. I can take a screenshot and force shutdown the phone but always end up at this blackscreen after going through the setup. Is this related to the Moto Display / Moto app? Cant even get to the point where I can disable it.
Edit: Went through the complete setup (including google login) until blackscreen. Then rebooted to fastboot and erased all partitions according to the XML again. Phone boots up, now is the EU version!
Can anyone confirm if doing this will make the TMobile Volte USA work? There is an issue where 5g works but the moment you make a call, the phone switches to 2g/3g. Thanks.
fabien32 said:
there is an app called Moto Display . disable it, remove the update from the market and stop the auto update
Click to expand...
Click to collapse
Same problem here but no Moto Display app to be found either on installed or system apps. Issue is as it recognized an official case switching or some gestures activated as a specific lockscreen that cannot be deblocked. At least this is what is happening to me:
Pablitus_Maximus said:
Same problem here but no Moto Display app to be found either on installed or system apps. Issue is as it recognized an official case switching or some gestures activated as a specific lockscreen that cannot be deblocked. At least this is what is happening to me:
Click to expand...
Click to collapse
As per info, there is the solution in this thread. Worked for me:
Fix screen stylus on Motorola x30
Hi all, I have a problem with motorola edge x30. My phone buy china, I unlock bootloader and flash rom global. But i have a problem. My phone stuck screen stylus, can not unlock screen, i must reboot phone, but when i lock screen, stylus screen...
forum.xda-developers.com
UPDATE: No, it did not. At first I locked and unlocked fine, but when falling into lockscreen due to inactivty, the problem is back. app data is now 0 bytes but still having the issue, and the app is not allowed to be disabled. Any help is welcome!
Now I have another problem. In system, Google Play system update is out of date (January 1st). If I update, then after rebooting it is fine, but then in few minutes it crashes and update is lost. Any ideas?
So is everyone saying it doesn't work?
Hello, I need help, I want to flash my machine according to the tutorial, but I am currently the latest firmware in China, can I follow the tutorial to flash the old version you provided++++
how can i contact with u
Related
Hi
ADB sideload fails at 47%, error in package.zip
The phone is in bootlop. I can't find signed MM images. The bootloader is locked. Any suggestions????
zaver said:
Hi
ADB sideload fails at 47%, error in package.zip
The phone is in bootlop. I can't find signed MM images. The bootloader is locked. Any suggestions????
Click to expand...
Click to collapse
Is your phone rooted? Because the same thing happened to me, but with the Nougat OTA update, not the ADB. I tried to unroot, but It kept failing, until I flashed from scratch the Marshmallow (with ADB).
Then I went through the OTA update again and it worked!
Maybe if you install the MM again, the Nougat may work =)
The phone is stock. I tried flashing MM with adb sideload, but I get "signature verification failed"
I also tried flashing in fastboot, but I can't without signed firmware files.
Have you extract the MM firmware files? I have successfully downgrade to MM my reteu Z play.
-=MoRpH=- said:
Have you extract the MM firmware files? I have successfully downgrade to MM my reteu Z play.
Click to expand...
Click to collapse
I have downloaded this:
https://mirrors.lolinet.com/firmware/moto/addison/official/RETEU/
if i use fastboot flash:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
Output:
.....
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
......
.....
writing 'system'...
(bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
.......
....
Invalid signed image is for every partition action.
First flash this commands:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
than restart the bootloader!
Now flash:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
after that make a wipe in the stock recovery. That works for me yesterday.
{Edit} Is your Bootloader unlocked? And what channel is it? (RETEU?)
Fisrt set of commands goes through OK
For the second set I get "Invalid signed image"
My bootloader is unfortunately locked.
I got the msg that the signature failed also. But the flash finished. Just flash all commands straightforward.
Gesendet von meinem XT1635-02 mit Tapatalk
I did wipe/factory reset in recovery.
Now it starts up MOTO scren, the followed by by an ""Android (like in recovery)" and text "Erasing..."
And it loops.
That's because a broken update. I had the same after trying to root. The only way for me was the downgrade to MM and update till nougat again.
Would you write me a pm with the errors you got at the downgrade process?
Gesendet von meinem XT1635-02 mit Tapatalk
zaver said:
I did wipe/factory reset in recovery.
Now it starts up MOTO scren, the followed by by an ""Android (like in recovery)" and text "Erasing..."
And it loops.
Click to expand...
Click to collapse
is your software status official or modified?
if its modified flash this by fastboot method
https://firmware.center/firmware/Motorola/Moto Z Play/Stock/
check which ur device is and download latest stock firmware... everything will be just fine..
if it fails do report us we all are here to help you
edit: ur bootloader is locked... ur in trouble my son....
unlock it then flash firmware files...it should work out
Sagar_1401 said:
unlock it then flash firmware files...it should work out
Click to expand...
Click to collapse
You are aware that unlocking erases all data and voids warranty?
Without unlocking you may try starting with
fastboot oem lock start
ending with
fastboot oem lock
(Only from memory, don't know what needs to be integrated, should do no harm if it fails, just refuse changes - but have no experience with this)
tag68 said:
You are aware that unlocking erases all data and voids warranty?
Without unlocking you may try starting with
fastboot oem lock start
ending with
fastboot oem lock
(Only from memory, don't know what needs to be integrated, should do no harm if it fails, just refuse changes - but have no experience with this)
Click to expand...
Click to collapse
he anyways need to loose all his data... he has messed up already.. what could he do now?
Maybe the data is lost, but the warranty isn't. At least by now.
Edit: I mean, it may be that the action makes sense. But it is not your decision and you should mention the drawbacks. He may not be aware that the data is lost, and there may be actions avoiding the data loss (may be needed to wait weeks or months to get the right nougat firmware). He may not be aware that warranty will be void, and it may also be an option to use the warranty and give it Lenovo. It is not your decision. Giving hints is fine, but always tell the negative part/alternative ways. You do suggestions, not a guide. The user has to decide himself, otherwise he has some right to get angry if something does not work fine.
Just my 2 cents: He needs a open bootloader to downgrade. If not, he have to wait for an full Android 7 Firmware File what is newer or exact Version of the flashed bootloader; what he flashed already i think. The big Question is: why the update stops. Where do you get the file?
Gesendet von meinem Lenovo TAB 2 A10-70F mit Tapatalk
I cannot unlock bootloader, you need to modify a setting when the phone is running in developer options.
I don't care about the data and I already have the bootloader unlock key. I need to get official signed firmware files so I can flash MM from fastboot. At least that is what I think.
Try other firmware than retail.us. You have already done
Enviado desde mi XT1635-02 mediante Tapatalk
joshua764 said:
Try other firmware than retail.us. You have already done
Enviado desde mi XT1635-02 mediante Tapatalk
Click to expand...
Click to collapse
I tried reteu, retbr 6.01. I cannot flash from fastboot. I get "Invalid signed image", which to my knowledge means, that the image was not signed by motorola/google/lenovo. And I can't find official, signed images anywhere.
For me, the OTA update succeeded, worked a for a while, then at some point it rebooted, whereupon I received the same message as OP.
Using: https://mirrors.lolinet.com/firmware/moto/addison/official/RETEU/
Running
Code:
fastboot flash partition gpt.bin
results in
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.003s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.072s
I assume this is because the update flashed newer firmware than what has been released by Motorola...
Attempting to sideload the .zip results in:
Code:
E: footer is wrong
EL signature verification failed
Installation aborted
So I'm left with the following choices:
1. Send the device back to Motorola for repair - won't have a phone in the meanwhile
2. Wait for Motorola to get a move on with releasing their firmware - phone unusable in the meanwhile
3. Unlock bootloader, void warranty, install LineageOS or similar, no camera until Motorola release the firmware blobs
Unless there are any other options I've missed, this is why you just cough up and go Google Nexus/Pixel gents...
Like I have said numerous times , DON'T ATTEMPT TO FLASH BACK TO MM unless you have a back up plan.
That back up plan would of course be, make sure you have the Nougat firmware for your specific device.
Considering Lenovo has ABANDONED all the phones before 2016, I was about to lose hope on updating the RETEU version of XT 1580, but after finding some tips to flash the Latin American firmware version, I could get a Nougat Update bugs (so far), and fully functional with my SIM. It's my first tutorial attempt in Xda Foruns, so let me know if there's any divergent intel within it
This Tutorial is based on a few others I've searched throughout foruns and Google+ by @miltonfernandez , and since I read the @Alimataei post Helping us to update the Chinese X Force version to Nougat, I could get this working too and now I'd like to tell ya guys how I did.
Step by Step1. Download the setup files:
Firmware Flahser
Career Signal Files
2. Download the required files in order to make your phone elegitable to the OTA update:
RETLA DS FIRMWARE24.78.8.12-12
Blur_Version.25.11.12.kinzie.retla.en.01.zip (NOUGAT OTA)
3. After the files being dowloaded, extract them to your desired pc folder: the firmware flasher and the RETLA UPDATE FILES;
4. Enable the USB Debugging in Settings>Developer Options, if you dont have that option enabled, just go to Settings> About The Phone> Click 7 x in the Version Number tile;
5. Connect your xt 1580 to your computer and open the firmware flasher, it will do all the job, but if you face any issue or if you want to flash the firmware by yourself, open a new comand prompt in this folder(right click > open comand prompt here) and paste the following comands:
fastboot flash partition gpt.biadb reboot bootloader
fastboot getvar max-sparse-size
fastboot oem fb_mode_setn
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
PS. It's normal to face a Fail Hash validation during the NON-HLOS.bin flash due the different modem versions, just flash again and it will be fine, this error doesn't occur during the process with the firmware flasher;
6. After the process completion, transfer the OTA file to your x force internal memory, and then, reboot your cellphone in recovery mode via bootloader menu or via adb with the command:
adb reboot recovery
Click to expand...
Click to collapse
* if you face the "NO COMAND" Screen, just press the VOL UP + POWER Keys at once;
7. In the recovery mode, go to "update from SD card" and choose the OTA File, if all the earlier steps went fine, the updade will work as fine as it should to a Latin American X Force, but it takes about 20 minutes, so hold on for that while...
8. After the long wait, and the "result is /system" status, it's recommended to wipe data and cache, so do these steps before rebooting your phone;
9. Now, you can choose to boot normally or go to the bootloader menu and flash the Career Singnal Files , because the reteu version was supposed to be single SIM, that's why we can't get any SIM recognition with DS (Dual SIM), firmwares. In order to flash the Career Singnal Files you can simply run the .bat file provided in the package attached, or use these comands in the prompted comand folder:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Click to expand...
Click to collapse
10. Your phone is now fully updated to the 7.0 Nougat and SIM Functional!!
Tap the Thanks button if it was useful for you :good:
Just checking.
Is this going to enable dual sim in European xt1580?
wifi is working?
TeddyBeers said:
Just checking.
Is this going to enable dual sim in European xt1580?
Click to expand...
Click to collapse
Dual SIM options are displayed for me, but I can't say if the second SIM tray will work cuz I don't have a second SIM
But if you flash all the provided files as described in the tutorial, your SIM will be fine
LoTableT said:
wifi is working?
Click to expand...
Click to collapse
Yep
I guess this procedure will also work with retmx 6.0 firmware and retmx 7.0 OTA file instead of retla firmware/OTA, right ?
Can confirm this is working. Can't see any bugs so far.
Simple instructions:
1) Flash the DS UPDATE files to allow your device to accept the 7.0 OTA (Warning: the firmware flasher will wipe your user data)
2) Flash the OTA file
3) Flash the RetEU files for modem etc.
the flash failed for me, could someone tell me why ?
do I need to unlock my bootloader (and void my warranty ) ?
Code:
C:\Program Files (x86)\ADB_Fastboot>fastboot getvar max-sparse-size
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
max-sparse-size: 268435456
finished. total time: 0.002s
C:\Program Files (x86)\ADB_Fastboot>fastboot oem fb_mode_set
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.012s]
finished. total time: 0.013s
C:\Program Files (x86)\ADB_Fastboot>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.326s
Dhalsim43 said:
1. do I need to unlock my bootloader (and void my warranty ) ?
2. C:\Program Files (x86)\ADB_Fastboot>fastboot flash partition gpt.bin
Click to expand...
Click to collapse
1. Yes
2. You can not do this. Installing gpt.bin from another phone, for example LA on the EU, can result in a brick.
Enlace de OTA y firmware eliminados por no citar al autor original del post de Google+. Hay que citar los créditos a quien corresponda, no adueñarse y solo traducir el trabajo de otros.
ilia3367 said:
1. Yes
2. You can not do this. Installing gpt.bin from another phone, for example LA on the EU, can result in a brick.
Click to expand...
Click to collapse
Really ?! so why is it in the procedure ?
LoTableT said:
wifi is working?
Click to expand...
Click to collapse
miltonfernandez said:
Enlace de OTA y firmware eliminados por no citar al autor original del post de Google+. Hay que citar los créditos a quien corresponda, no adueñarse y solo traducir el trabajo de otros.
Click to expand...
Click to collapse
You are the author Dude!
Sorry, I totally forgot to mention you on credits, glad to know you're on Xda too
I installed without any problem!
Thanks a lot!
Mirror
Is there a mirror available ? the mega download doe not work anymore
ilia3367 said:
You can not do this. Installing gpt.bin from another phone, for example LA on the EU, can result in a brick.
Click to expand...
Click to collapse
@Felipolas, what do you think about that ?
Felipolas said:
You are the author Dude!
Sorry, I totally forgot to mention you on credits, glad to know you're on Xda too
Click to expand...
Click to collapse
New OTA and Firmware link in the original post of Google+.
LoTableT said:
I installed without any problem!
Thanks a lot!
Click to expand...
Click to collapse
Hi, can you please tell me what phone you have? I tried it on my XT1581 with MM 6 and I am having problems. I cannot go past the 6.01 update, then I have one sim and wifi OK but not second sim. If I use my modem file (from my China rom) I get two sims OK but no wifi!
Crazy
Thanks
Andrea
Alchimista58 said:
Hi, can you please tell me what phone you have? I tried it on my XT1581 with MM 6 and I am having problems. I cannot go past the 6.01 update, then I have one sim and wifi OK but not second sim. If I use my modem file (from my China rom) I get two sims OK but no wifi!
Crazy
Thanks
Andrea
Click to expand...
Click to collapse
this guide is for XT1580 Reteu (european version)
LoTableT said:
this guide is for XT1580 Reteu (european version)
Click to expand...
Click to collapse
Thank you for your immediate reply. Noted, I think I'll give up!
Regards
Andrea
Dhalsim43 said:
@Felipolas, what do you think about that ?
Click to expand...
Click to collapse
That'e true, you can get a softbrick you manage to install a different gpt.bin file that your region is
Hi all!
I installed PIE using the VPN method in the beginning of the month. Now, the update (about 90mb) was released but I'm getting an error message.
I tried several networks, WiFi or cellular but the error persists.
Does any one has an idea on what I can do? I don't have a working windows computer unfortunately.
Regards!
How on earth did you turn on the battery % in the status bar?? I'm also on pie, december update went without errors,
Gregor250385 said:
How on earth did you turn on the battery % in the status bar??
Click to expand...
Click to collapse
asking the real questions!
Gregor250385 said:
How on earth did you turn on the battery % in the status bar?? I'm also on pie, december update went without errors,
Click to expand...
Click to collapse
You can use: https://play.google.com/store/apps/details?id=com.bryancandi.android.uituner
This is what I used and is working without issues.
I'm just not able to update to the lastest version rolled out today. Damn it!
well i would recommand you to make a fresh install with this procedure :
1-unclock the phone
2-grab the latest 8.1 rom on official xiaomi website , unpack it and past the files in the same folder as platform-tools
3- shut down the phone , hold down volume plus power button, run cmd in the folder platform-tools as admin : flash_all
4-the phone reboots with fresh install , go to update and let it download android pie
5-the phone reboots with pie with 0 problems.
if you need that i put more details just say so .
TheAwesomeRB1 said:
well i would recommand you to make a fresh install with this procedure :
1-unclock the phone
2-grab the latest 8.1 rom on official xiaomi website , unpack it and past the files in the same folder as platform-tools
3- shut down the phone , hold down volume plus power button, run cmd in the folder platform-tools as admin : flash_all
4-the phone reboots with fresh install , go to update and let it download android pie
5-the phone reboots with pie with 0 problems.
if you need that i put more details just say so .
Click to expand...
Click to collapse
Thanks for that input.
However, one question. Will this work on a MacBook? My windows computer is simply not working at all. I don't have any other computer at the moment.
senntennce said:
Thanks for that input.
However, one question. Will this work on a MacBook? My windows computer is simply not working at all. I don't have any other computer at the moment.
Click to expand...
Click to collapse
Well you can try to use vmware workstation and emulate windows, theoretically it would work but dont forget to install the drivers otherwise it wont be recognized.
Edit : platform tools exists also for mac os.
reboot and try to update again, do this a few times. mine did this but a reboot or two and it fixed itself, dont know if its the same issue though
DrEzkimo said:
reboot and try to update again, do this a few times. mine did this but a reboot or two and it fixed itself, dont know if its the same issue though
Click to expand...
Click to collapse
I tried that for the day... Like 20 times already and still nothing.
I will give a few more tries.
Thanks!
senntennce said:
I tried that for the day... Like 20 times already and still nothing.
I will give a few more tries.
Thanks!
Click to expand...
Click to collapse
Just do what i told it will be fine, as i said there is a version of platform tools for mac os, if you need further help i ll be here.
TheAwesomeRB1 said:
well i would recommand you to make a fresh install with this procedure :
1-unclock the phone
2-grab the latest 8.1 rom on official xiaomi website , unpack it and past the files in the same folder as platform-tools
3- shut down the phone , hold down volume plus power button, run cmd in the folder platform-tools as admin : flash_all
4-the phone reboots with fresh install , go to update and let it download android pie
5-the phone reboots with pie with 0 problems.
if you need that i put more details just say so .
Click to expand...
Click to collapse
There's literally no reason to revert back to Oreo. OP just need to flash boot and system images from his current version in both slots before updating.
Does this version have the bug as vpn version? For example flash of screen (normale/black)?
croccio said:
Does this version have the bug as vpn version? For example flash of screen (normale/black)?
Click to expand...
Click to collapse
Nope, works perfectly, 0 bugs.
i have problems with wifi
can't connect to any of my saved wifi
tried to reset wifi twice, but it doesn't work
Hakkinan said:
There's literally no reason to revert back to Oreo. OP just need to flash boot and system images from his current version in both slots before updating.
Click to expand...
Click to collapse
I'm currently downloading those files.
The commands that I need will be:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
Correct?
Thanks
Well, for my case i would rather remove everey thing and start from scratch for a fresh start with only One command and zero risk, if you get the same result with fastbooting go ahead.
TheAwesomeRB1 said:
well i would recommand you to make a fresh install with this procedure :
1-unclock the phone
2-grab the latest 8.1 rom on official xiaomi website , unpack it and past the files in the same folder as platform-tools
3- shut down the phone , hold down volume plus power button, run cmd in the folder platform-tools as admin : flash_all
4-the phone reboots with fresh install , go to update and let it download android pie
5-the phone reboots with pie with 0 problems.
if you need that i put more details just say so .
Click to expand...
Click to collapse
XIaomi specifically warns you about NOT reverting to Oreo once you are on Pie.
After doing some research, found that using a macbook, we should change the codes to:
./fastboot flash boot_a boot.img
./fastboot flash boot_b boot.img
./fastboot flash system_a system.img
./fastboot flash system_b system.img
But after doing:
./fastboot flash system_a system.img
I got this error message:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magic
sending sparse 'system_a' 1/4 (522236 KB)...
OKAY [ 18.147s]
writing 'system_a' 1/4...
FAILED (remote: Partition flashing is not allowed)
Tried every code but the message is always the same: FAILED (remote: Partition flashing is not allowed)
I enabled OEM Unlocking in Developer Options and debugging.
What I'm I missing?
Edit: Yeah, after reading some more, it seems that it is required to have the boot loader unlocked and I don't have it. Bummer.
senntennce said:
After doing some research, found that using a macbook, we should change the codes to:
./fastboot flash boot_a boot.img
./fastboot flash boot_b boot.img
./fastboot flash system_a system.img
./fastboot flash system_b system.img
But after doing:
./fastboot flash system_a system.img
I got this error message:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magic
sending sparse 'system_a' 1/4 (522236 KB)...
OKAY [ 18.147s]
writing 'system_a' 1/4...
FAILED (remote: Partition flashing is not allowed)
Tried every code but the message is always the same: FAILED (remote: Partition flashing is not allowed)
I enabled OEM Unlocking in Developer Options and debugging.
What I'm I missing?
Click to expand...
Click to collapse
I'm not sure about MacOS (since i don't have one) but in Windows/Linux this happens when you use an older version of fastboot.
senntennce said:
After doing some research, found that using a macbook, we should change the codes to:
./fastboot flash boot_a boot.img
./fastboot flash boot_b boot.img
./fastboot flash system_a system.img
./fastboot flash system_b system.img
But after doing:
./fastboot flash system_a system.img
I got this error message:
target reported max download size of 534773760 bytes
Invalid sparse file format at header magic
sending sparse 'system_a' 1/4 (522236 KB)...
OKAY [ 18.147s]
writing 'system_a' 1/4...
FAILED (remote: Partition flashing is not allowed)
Tried every code but the message is always the same: FAILED (remote: Partition flashing is not allowed)
I enabled OEM Unlocking in Developer Options and debugging.
What I'm I missing?
Click to expand...
Click to collapse
Since your windows is down, can you try it on a virtual machine (vmware workstation) ?
I've been disappointed with some of the firmware here, like Lineage and Arrow. Havoc has been my favorite, but when we transitioned from Havoc Android 10 (3.*) to Android 11 (4.*) I have lost LTE every morning, which means no texts, no data, no phone calls. I have to power down and up and who knows when I'd lose LTE again.
Also with TWRP I could not slide the unock, and trying to select files the screen mapping is all wrong, meaning I'd touch a file at the bottom and a file toward the top would be selected. I don't know why the problems were because no one has ever been able to communicate the structure and framework of Android coherently. It seems that most just know parts of it intuitively, not the whole intellectually.
So I have to resort to Stock. I thought maybe installing Stock then Havoc 4.8 would solve the LTE problem, but when doing that Havoc's boot just circles around forever.
So without further adieu here is how to install Stock on your Moto G Power. Mine is US T-Mobile on an XT2041-4.
Get the firmware here: https://mirrors.lolinet.com/firmware/moto/sofia/official/
I hit RETUS and RETUS_10 for Retail US Android 10. If you have a different carrier or nation try and decipher which is right for you. Use 10 as Beetle says below. (as of Jan, 2022, Havoc 4.12)
Unzip this file into its own directory and you will get a series of images and .xml files. Boot your phone into fastboot mode by turning it off, then hold {VolDown}{Power} at the same time to go into fastboot mode. In this case you do -not- then reboot into fastbootd mode! Just leave it like this and connect to your computer.
Code:
# fastboot devices
... should give you something like
Code:
ZY227VX6NG fastboot
Good, your computer sees the phone.
Go into the firmware directory. A key file here is flashfile.xml. This tells you exactly how these image files must be applied to the phone and in what order. I'll show below the files and procedure for my phone, but yours may be different so refer to that flashfile for your firmware.
The first file to flash is important. It sets up the partitions on the phone properly:
Code:
# fastboot flash partition gpt.bin
Now just work your way down flashfile. Here's mine:
Code:
# fastboot flash bootloader bootloader.img
# fastboot flash vbmeta vbmeta.img
# fastboot flash radio radio.img
# fastboot flash bluetooth BTFM.bin
# fastboot flash dsp dspso.bin
# fastboot flash logo logo.bin
# fastboot flash boot boot.img
# fastboot flash dtbo dtbo.img
# fastboot flash recovery recovery.img
# fastboot flash super super.img_sparsechunk.0
# fastboot flash super super.img_sparsechunk.1
# fastboot flash super super.img_sparsechunk.2
# fastboot flash super super.img_sparsechunk.3
# fastboot flash super super.img_sparsechunk.4
# fastboot flash super super.img_sparsechunk.5
# fastboot flash super super.img_sparsechunk.6
# fastboot flash super super.img_sparsechunk.7
# fastboot flash super super.img_sparsechunk.8
# fastboot flash super super.img_sparsechunk.9
# fastboot flash super super.img_sparsechunk.10
# fastboot flash super super.img_sparsechunk.11
# fastboot flash super super.img_sparsechunk.12
# fastboot flash super super.img_sparsechunk.13
# fastboot flash super super.img_sparsechunk.14
# fastboot flash super super.img_sparsechunk.15
# fastboot erase carrier
# fastboot erase userdata
# fastboot erase metadata
# fastboot erase ddr
# fastboot oem fb_mode_clear
And that's it. Reboot. It will take a while the first time so don't interrupt it. You're back to stock.
If you were trying to flash havoc over android 11 firmware, it wont work. These roms need android 10 as a base.
Ah, that explains it. I think Havoc is the best, but 4.6 and 4.8 reliably drop LTE for me mornings. It's caused business problems.
I now find that it's impossible to tear G**gle out of Stock, so that's out for me. Maybe Arrow or something.
What carrier do you have? I'm getting ready to put maybe Havoc or Linage on this phone, but need to know what to watch out for.
It seems to be like Android 11 is a common denominator in a lot of the issues I've seen people having. That's why I have no intention of even moving to a custom rom based on 11 for a good while. I'll be staying at Lineage 17 or Havoc 3 until I have no other choice. There's nothing in 11 I need or want, and that will probably be true for 12 and 13 and so on. As for de-googling Android, that's likely going to just get harder and harder with each version.
I seem to be the only one having problems with Android 11 afaict. Haven't seen anyone else posting issues. Decided it's something about my phone, but laying down 11 stock reset everything. I just can't run Havoc anymore.
I highly recommend Havoc 3.*.
I wonder whether laying down Android 10 would fix my issues with Havoc 4.*?
I went back to stock for the same reason as OP. As far as de-googling, it's a chore to get it to a point where I feel a bit comfortable turning wi-fi on, but I'm not very comfortable. Basically I disable all google stuff, including the play store, prevent the google apps installed post-setup, remove permissions from play services, turn off networking for it and everything else, go through settings to disable 'functions' , I use the keepass2android app's keyboard, install a different sms app, keep contacts to device, and firewall everything - I don't allow much networking functionality at all. Of course, I'm rooted., I also use app manager to disable trackers and disable "0" which is 'rough' location for all apps, system included - I eneble it for weather. I use aurora and f-droid for apps, but, mostly just reinstall from dumps. Also, I don't use a lot of apps and for my feng shui, the device (and my edge) works well. I'm likely leaving out a bunch of little tweaks that I do, apologies.
I use nextcloud, adaway, sms backup and restore, acalendar+, fx, firefox focus or bromite, pi-hole is on my LAN. ON my edge, with lineage (17) and tweaked 'my way', I feel reasonably safe. On my g power with stock, tweaked, I feel a little naked. Whereas I'm not shy, I am private. My g power mostly stays turned off kept in a drawer in my office.
I've been running CrDroid (google-free) v7.7 (android 11) with good results. I have data turned off on this screenshot, but have used it in limited amounts (my current plan allows only 1G per month). BTW, I'm on Red Pocket GSMA (ATT).
So I've cleared the decks by laying down Stock Android 10, then installing Havoc 4.8.
If I lose data tomorrow morning I will have to use another firmware, although I'm confident.
+1 on aCalendar+ and its beautiful widget, and add CalendarNotifications for nice popup.
I use SuperBackups to back up apps and call logs to SD card, and also AppBackupRestore just to be sure. Everything on the SD card was preserved during all these latest calisthenics, thankfully, including after the fastboot erases.
I've set up a Davical server at home for calendar and contacts sync, and on the phone DAVx5 to communicate with it. It's a faff to set up, but such a joy to know my calendars and contacts are always synced with home, once set up. (Thunderbird+Lightning for now, maybe soon Kontact)
The phone does all internet access through a WireGuard tunnel to home WG server virtual machine (interface: inWG), and then out the outWG interface to come out appearing that I'm in Switzerland or Spain, using AzireVPN service.
For Android firewall I use the fine AFWall+ and its little on/off widget, and for apps I always try F-Droid first then APKPure. Browser is Vivaldi. To transfer files with LAN I connect with wifi then use SSHDroid as SSH server on the phone and sshfs on the server to mount the phone. (SSHDroid is worrisomely getting old)
Also I use Nova as desktop renderer. I have 5 phone desktops and it takes me a day to rebuild everything with the standard Havoc desktop (Shady Launcher), no offense SkullShady. Nova lets you back up and restore all settings, including complete desktops setup, which is such a pleasure.
G**gle-less. G**gle-free. Sans G**gle. In my Postfix server I kick back all gmail messages with, "THANK YOU FOR SENDING THIS, BUT GMAIL IS CONSIDERED A SECURITY PROBLEM. PLEASE RE-SEND FROM ANOTHER ACCOUNT."
Good sign - I have data this morning.
Deleted. Thank you.
Worked like a charm. Followed this guide, then ran fastboot oem lock, to prepare a phone to give away. Thank you.
I extracted the files straight to my platform-tools folder to simplify.
Quantumstate said:
Good sign - I have data this morning.
Click to expand...
Click to collapse
Remember me? I still have my Sofia, but it's running stock A11 and Nova Launcher 6.2.9 rather that 7x which screws with my Android widgets. So, I've set the Play Store not to auto update apps to keep 6.2.9. This setup is OK, but I'd rather root it, install TWRP, and an updateable/upgradeable custom ROM. Can you offer some step-by-step guidance?
Thanks
jhford said:
Remember me? I still have my Sofia, but it's running stock A11 and Nova Launcher 6.2.9 rather that 7x which screws with my Android widgets. So, I've set the Play Store not to auto update apps to keep 6.2.9. This setup is OK, but I'd rather root it, install TWRP, and an updateable/upgradeable custom ROM. Can you offer some step-by-step guidance?
Thanks
Click to expand...
Click to collapse
Sure I remember you. I just did an install of beetle84's last version of Havoc as above, and as per the directions in his thread, it's worked ever since. Only glitch is I lose mobile data every morning, but just power down and reboot.
I'm afraid of this version as I tried and tried but could not make it work. Phone was down for days.
Beetle84 said:
If you were trying to flash havoc over android 11 firmware, it wont work. These roms need android 10 as a base.
Click to expand...
Click to collapse
I'm researching if I can flash XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip onto my unrooted Android 11 phone, an XT2041-4 that was Android 10 but now Android 11.
I'm not familiar with havoc so I'm curious what you mean. Is that image flashable to my phone or am I wanting to flash havoc over android 11 firmware?
I followed the steps in the oP and bricked my device. I didn't unlock the bootloader so if you follow the tutorial above be sure to unlock the bootloader before wiping the partition.
If anyone knows how to recover from that point I'd appreciate any help. I have the unlock code but I didn't enable unlocking the bootloader before wiping the partition as I didn't know I needed to do that so I hosed myself.
powershift said:
I followed the steps in the oP and bricked my device. I didn't unlock the bootloader so if you follow the tutorial above be sure to unlock the bootloader before wiping the partition.
If anyone knows how to recover from that point I'd appreciate any help. I have the unlock code but I didn't enable unlocking the bootloader before wiping the partition as I didn't know I needed to do that so I hosed myself.
Click to expand...
Click to collapse
Are you still able to boot to the bootloader menu using hardware keys? You should be able to continue unlocking it regardless of what you wiped. Either way that shouldn't stop you from being able to flash the stock rom.
What exactly are you stuck on now?
TaZeR369 said:
Are you still able to boot to the bootloader menu using hardware keys? You should be able to continue unlocking it regardless of what you wiped. Either way that shouldn't stop you from being able to flash the stock rom.
What exactly are you stuck on now?
Click to expand...
Click to collapse
It wouldn't unlock in fastboot. What I did was I downloaded Android 11 and flashed it, then did the boot loader unlock.
But when applying stock Android 10 w/out errors during the flash, on boot the blue Motorola splash screen shows, it acts like it is booting then it reboots and the blue screen goes away and comes back. It will do that boot loop all day. I had to revert back to Android 11, but at least the phone boots now although I'd still like to get Android 10 on there as I'm not at all a fan of V11.
powershift said:
It wouldn't unlock in fastboot. What I did was I downloaded Android 11 and flashed it, then did the boot loader unlock.
But when applying stock Android 10 w/out errors during the flash, on boot the blue Motorola splash screen shows, it acts like it is booting then it reboots and the blue screen goes away and comes back. It will do that boot loop all day. I had to revert back to Android 11, but at least the phone boots now although I'd still like to get Android 10 on there as I'm not at all a fan of V11.
Click to expand...
Click to collapse
I think maybe you should try to flash stock android 10 image again. It's the kind of error that happened to me when I missed a step or forgot a command and looking over your post I think there is something missing or added that shouldn't be there. Also don't flash anything like magisk or twrp along with it, wait until the first boot for anything more.
Heres whats always worked for me (same model phone):
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
TaZeR369 said:
I think maybe you should try to flash stock android 10 image again. It's the kind of error that happened to me when I missed a step or forgot a command and looking over your post I think there is something missing or added that shouldn't be there. Also don't flash anything like magisk or twrp along with it, wait until the first boot for anything more.
Heres whats always worked for me (same model phone):
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
fastboot erase userdata
fastboot erase ddr
fastboot flash dsp dspso.bin
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
That is what my script looks like with one exception, I can't run the flash bootloader bootloader.img successfully because it fails validation. All other steps succeed. Did you have Android 11 bootloader on there and put the Android 10 bootloader back?
In addition to those steps, I tried fastboot getvar max-sparse-size before all others and still no joy. I think the Android 11 bootloader doesn't boot Android 10 and I don't know how to reflash it back to the old bootloader even while unlocked.
Code:
[email protected]:~/android$ sudo /home/anon/android/platform-tools/fastboot oem unlock 2T4ETJZNOSHSA324GL6G
(bootloader) Bootloader is unlocked!
OKAY [ 15.676s]
Finished. Total time: 15.676s
[email protected]:~/android$
[email protected]:~/android/moto_stock_android10$ sudo /home/anon/android/platform-tools/fastboot flash bootloader bootloader.img
Sending 'bootloader' (14204 KB) OKAY [ 0.557s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
[email protected]:~/android/moto_stock_android10$
powershift said:
That is what my script looks like with one exception, I can't run the flash bootloader bootloader.img successfully because it fails validation. All other steps succeed. Did you have Android 11 bootloader on there and put the Android 10 bootloader back?
In addition to those steps, I tried fastboot getvar max-sparse-size before all others and still no joy. I think the Android 11 bootloader doesn't boot Android 10 and I don't know how to reflash it back to the old bootloader even while unlocked.
Code:
[email protected]:~/android$ sudo /home/anon/android/platform-tools/fastboot oem unlock 2T4ETJZNOSHSA324GL6G
(bootloader) Bootloader is unlocked!
OKAY [ 15.676s]
Finished. Total time: 15.676s
[email protected]:~/android$
[email protected]:~/android/moto_stock_android10$ sudo /home/anon/android/platform-tools/fastboot flash bootloader bootloader.img
Sending 'bootloader' (14204 KB) OKAY [ 0.557s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
[email protected]:~/android/moto_stock_android10$
Click to expand...
Click to collapse
It does flash back, I've done it a few times, I didn't have any difficulty. You said you unlocked the bootloader before, but you seem to be entering the code to unlock it again each time you try to flash or? Because once its unlocked you shouldn't be needing to do oem unlock anymore, unless you've locked it again. Also what distro are you using and adb package?
There may be some verification problem here if something is not fully unlocked for some reason, so just to clarify the first time you flashed android 10 over 11 you also had the bootloader failed error, or is this now on the second try?
Perhaps if all else fails can try to change to the next active slot like b, and try to flash there in case something maybe the partition table got screwed up somehow (at the start) "fastboot set_active b", cold booting with a twrp image may be able to fix it in that case.
I mean unless there is some kind of new protection in the lastest versions of 11 that i dont know about...? Maybe as a last resort reflash android 11 but the first version after 10, and then try to downgrade from that? I dunno man sorry... some stuff to think about...
Red Magic 8 Pro stuck fastboot
It no longer has sideload mode in recovery
Did you somehow change your slot? If you haven't upgraded the firmware, then the 2nd slot is empty, and it will not boot anything.
BoJaXz said:
Did you somehow change your slot? If you haven't upgraded the firmware, then the 2nd slot is empty, and it will not boot anything.
Click to expand...
Click to collapse
I switched both slots, but I can't boot up
Mr.PvT said:
I switched both slots, but I can't boot up
Click to expand...
Click to collapse
What steps did you do before you got stuck in fastboot?
BoJaXz said:
What steps did you do before you got stuck in fastboot?
Click to expand...
Click to collapse
I patched the root boot file then flashed it failed, then I flashed each file in the payload, I deleted the super, the files in the super can't be flashed oddly, are you rooted, can backup the whole partition help me
Thank you
Mr.PvT said:
I patched the root boot file then flashed it failed, then I flashed each file in the payload, I deleted the super, the files in the super can't be flashed oddly, are you rooted, can backup the whole partition help me
Thank you
Click to expand...
Click to collapse
Did you oem unlock before you tried flashing? You may have to flash the whole image
BoJaXz said:
Did you oem unlock before you tried flashing? You may have to flash the whole image
Click to expand...
Click to collapse
I unlocked the bootloader, I flashed all the files in the payload but still can't boot, hang fastboot or boot to the logo and then shut down
I need someone to back up all my partitions, that's the only way I can do it
Mr.PvT said:
I unlocked the bootloader, I flashed all the files in the payload but still can't boot, hang fastboot or boot to the logo and then shut down
I need someone to back up all my partitions, that's the only way I can do it
Click to expand...
Click to collapse
Did you flash boot.img or init_boot.img?
It sounds like you are booting the wrong slot.
BoJaXz said:
Did you flash boot.img or init_boot.img?
It sounds like you are booting the wrong slot.
Click to expand...
Click to collapse
I flashed those 2 files and changed both slots but failed to start the phone
I faced with the problem by locking the bootloader with init_boot.img for magisk. Then I unlocked it again and switched aactive slot to b and then to a in "Fastboot Enhance" tool. After that my phone entered to the system.
[TOOL][Windows] Fastboot Enhance [Payload Dumper & Image Flasher]
Fastboot Enhance What it can do? - Show fastboot vars - Switch between fastbootd & bootloader - Switch between A & B slot - Flash Payload.bin in fastbootd - Flash images - Erase partitions - Delete logical partitions - Create logical partitions...
forum.xda-developers.com
@Mr.PvT did you ever make any progress with this? I am in the same boat now. Flashed a GSI and tested it out. DIdnt like it so flashed the 3.18 Payload.bin thru Fastboot enhance and am stuck on Bootloader. Cant access anything else as no matter what I choose it boots to bootloader.
DarkestSpawn said:
@Mr.PvT did you ever make any progress with this? I am in the same boat now. Flashed a GSI and tested it out. DIdnt like it so flashed the 3.18 Payload.bin thru Fastboot enhance and am stuck on Bootloader. Cant access anything else as no matter what I choose it boots to bootloader.
Click to expand...
Click to collapse
I also went from a GSI to stock ROM and this worked, some steps may be unnecessary:
In bootloader change active slot to a
Flash all of payload.bin images
Reboot to fastboot and flash all of payload images
Reboot to recovery
Hold volume down for a few seconds to enable sideload
Connect the phone to a pc and ADB sideload NX729J-update.zip
Then wipe data and reboot
Also did your calls and messages work when using the GSI?
edzchen said:
I also went from a GSI to stock ROM and this worked, some steps may be unnecessary:
In bootloader change active slot to a
Flash all of payload.bin images
Reboot to fastboot and flash all of payload images
Reboot to recovery
Hold volume down for a few seconds to enable sideload
Connect the phone to a pc and ADB sideload NX729J-update.zip
Then wipe data and reboot
Also did your calls and messages work when using the GSI?
Click to expand...
Click to collapse
In bootloader:
fastboot flash odm odm.img
target reported max download size of 805306368 bytes
sending 'odm' (1284 KB)...
OKAY [ 0.032s]
writing 'odm'...
FAILED (remote: (odm_a) No such partition)
finished. total time: 0.038s
F:\Files\Downloads\RM8P\NX729J-update>fastboot flash system_dlkm system_dlkm.img
target reported max download size of 805306368 bytes
sending 'system_dlkm' (428 KB)...
OKAY [ 0.011s]
writing 'system_dlkm'...
FAILED (remote: (system_dlkm_a) No such partition)
finished. total time: 0.018s
F:\Files\Downloads\RM8P\NX729J-update>fastboot flash system_ext system_ext.img
target reported max download size of 805306368 bytes
sending 'system_ext' (730792 KB)...
OKAY [ 17.204s]
writing 'system_ext'...
FAILED (remote: (system_ext_a) No such partition)
finished. total time: 17.211s
Nothing happens when I flash system & vendor.
F:\Files\Downloads\RM8P\NX729J-update>fastboot flash vendor_dlkm vendor_dlkm.img
target reported max download size of 805306368 bytes
sending 'vendor_dlkm' (93564 KB)...
OKAY [ 2.181s]
writing 'vendor_dlkm'...
FAILED (remote: (vendor_dlkm_a) No such partition)
finished. total time: 2.187s
In Fastbootd:
Everything that failed in bootloader, flashed beside system. Could only flash _b slots. Nothing seems to exist for slot a. I did not fastboot format or erase anything to my knowledge unless Fastboot Enhance did so when I flashed the playload.bin thru it without having logs on to watch what it did. If it formated or erased any partitions can they be recreated?
And last when in Recovery:
F:\Files\Downloads\RM8P>adb sideload NX729J-update.zip
loading: 'NX729J-update.zip'
error: closed
DarkestSpawn said:
Everything that failed in bootloader, flashed beside system.
Click to expand...
Click to collapse
What is the error when flashing system?
If it has something to do with not being able to resize the system partition, check this link:
Fix FAILED (remote: 'Not enough space to resize partition')
In this comprehensive tutorial, we will show you the steps to fix the FAILED (remote: 'Not enough space to resize partition') error.
www.droidwin.com
I had this problem too.
Which GSI were u on
edzchen said:
Also did your calls and messages work when using the GSI?
Click to expand...
Click to collapse
edzchen said:
What is the error when flashing system?
If it has something to do with not being able to resize the system partition, check this link:
Fix FAILED (remote: 'Not enough space to resize partition')
In this comprehensive tutorial, we will show you the steps to fix the FAILED (remote: 'Not enough space to resize partition') error.
www.droidwin.com
I had this problem too.
Which GSI were u on
Click to expand...
Click to collapse
I just retried in bootloader with a new outcome this time:
F:\Files\Downloads\RM8P\NX729J-update>fastboot flash system system.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/6 (786364 KB) OKAY [ 18.742s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
I copied the fastboot.exe from fastboot enchanced to the directory of the extracted payload.bin. Was able to recreate partitions. Am attempting to recover from potential brick.
I tried LineageOS TD-based. Didnt attempt calls or messages. Was just checking out the feel of the rom and its capabilities.
Can someone run this fastboot command in bootloader and fastbootd and save the results in a text file?
fastboot getvar all
Omit the serial number in bootloader and fastbootd's printout.
DarkestSpawn said:
Can someone run this fastboot command in bootloader and fastbootd and save the results in a text file?
fastboot getvar all
Omit the serial number in bootloader and fastbootd's printout.
Click to expand...
Click to collapse
Here you go:
ugene1980 said:
Here you go:
Click to expand...
Click to collapse
So looking thru this, the only difference I have is:
(bootloader) partition-size:userdata: 0x718BCD3000 Mine
(bootloader) partition-size:userdata: 0x35F5CD3000 Yours
as well as:
(bootloader) slot-successful:a:yes Yours
(bootloader) slot-successful:a:no Mine
but thats because it hasnt successfully booted since last flash.
I also need the fastbootd's printout. The one provided was from bootloader. The one from fastbootd will give logical partitions and has slot info.
edzchen said:
Also did your calls and messages work when using the GSI?
Click to expand...
Click to collapse
Did you install carrier serivces from google play, setup APN settings for your carrier and Installing new IMS package: Treble Settings -> IMS features -> install IMS for Qualcomm -> install package. I cant remember if that was in there. Still trying to get booted again
DarkestSpawn said:
Did you install carrier serivces from google play, setup APN settings for your carrier and Installing new IMS package: Treble Settings -> IMS features -> install IMS for Qualcomm -> install package. I cant remember if that was in there. Still trying to get booted again
Click to expand...
Click to collapse
Yeap I did all that but calls and texts only half worked. I could do calls but no audio and I could send texts but couldn't receive. Was the main reason why I switched back to stock