I was having a problem with my Moto G XT1033 yesterday as most apps get closed automatically at launch. this morning i installed AVG to do a scan, i also used Root file manager to clean up some files (junks, duplicates etc)
I then did a restart after which my phone will not boot to home screen again.
It boots up showing the boot animation bout after that i get a black blank screen which back light on.
Things i have tried
did cache partition wipe
did wipe/restore
all to no avail
I then downloaded a stock ROM from Blur_Version.221.21.56.falcon_umtsds.AsiaRetail.en.03.zip
downloaded minimal ADB and fastbook.
- put the phone to fastboot
- on android system recovery mode i clicked apply update from ADB
then on PC i confirmed it can see my phone by typing adb devices, my phone get listed.
I then do adb sideload Blur_Version.221.21.56.falcon_umtsds.AsiaRetail.en.03.zip
Finding update package.........
Opening update package........
Verifying update package........
Installing update..........
Then i get Package expects build fingerprint of motorola/falcon_asia_ds/falcon_umtsds:5.0./LXB22.46-28/30:user/release-keys or motorola/falcon_asia_ds/falcon_umtsds:5.1/PB23.13-56:user/release-keys; this device has motorola/falcon_asia_ds/falcon_umtsds:5.1/LPBS
E:Error in /sodeload/package.zip (status 7)
Install aborted.
Device Details
Moto G
XT1033
build LPBS23
Indian version
running Android 5.1.1 (running latest android for the device, i only do OTA updates/upgrades)
Not rooted
no custom OS
I will really appreciate any help to get the device up again
wasconet said:
I was having a problem with my Moto G XT1033 yesterday as most apps get closed automatically at launch. this morning i installed AVG to do a scan, i also used Root file manager to clean up some files (junks, duplicates etc)
I then did a restart after which my phone will not boot to home screen again.
It boots up showing the boot animation bout after that i get a black blank screen which back light on.
Things i have tried
did cache partition wipe
did wipe/restore
all to no avail
I then downloaded a stock ROM from Blur_Version.221.21.56.falcon_umtsds.AsiaRetail.en.03.zip
downloaded minimal ADB and fastbook.
- put the phone to fastboot
- on android system recovery mode i clicked apply update from ADB
then on PC i confirmed it can see my phone by typing adb devices, my phone get listed.
I then do adb sideload Blur_Version.221.21.56.falcon_umtsds.AsiaRetail.en.03.zip
Finding update package.........
Opening update package........
Verifying update package........
Installing update..........
Then i get Package expects build fingerprint of motorola/falcon_asia_ds/falcon_umtsds:5.0./LXB22.46-28/30:user/release-keys or motorola/falcon_asia_ds/falcon_umtsds:5.1/PB23.13-56:user/release-keys; this device has motorola/falcon_asia_ds/falcon_umtsds:5.1/LPBS
E:Error in /sodeload/package.zip (status 7)
Install aborted.
Device Details
Moto G
XT1033
build LPBS23
Indian version
running Android 5.1.1 (running latest android for the device, i only do OTA updates/upgrades)
Not rooted
no custom OS
I will really appreciate any help to get the device up again
Click to expand...
Click to collapse
Firstly, I would like to point out that your phone is merely soft-bricked. Hard bricks are much more serious and happen when your phone does not turn on at all. So, in future, please do not complain about a hard brick where there is none.
Onto the actual issue, it appears to be an easy fix. The problem was simply that you were attempting to sideload an OTA update, as opposed to flashing full firmware, which will not work. So all you need to do is flash the full factory firmware using fastboot flash, not adb sideload. To do this, flash factory firmware from here using the fastboot commands linked on that thread.
Professor Gibbins said:
Firstly, I would like to point out that your phone is merely soft-bricked. Hard bricks are much more serious and happen when your phone does not turn on at all. So, in future, please do not complain about a hard brick where there is none.
Onto the actual issue, it appears to be an easy fix. The problem was simply that you were attempting to sideload an OTA update, as opposed to flashing full firmware, which will not work. So all you need to do is flash the full factory firmware using fastboot flash, not adb sideload. To do this, flash factory firmware from here using the fastboot commands linked on that thread.
Click to expand...
Click to collapse
im sorry for the false alarm.
Thanks! :good:
Hey,
It's been always a huge headache since when the Android 10 beta and stables updates are out to root and install twrp. I've tried almost every way possible but every-time, end up being stuck at TWRP or being half way rooted. This time I've tried doing that again :
* I was at OxygenOs Android 10 stable version,
* My bootloader was unlocked as well as OEM unlocking and usb debugging was on,
* I turned my phone into fastboot, and flash the twrp image as:
fastboot flash boot file.img
Then after my phone booted into TWRP since once or twice showing that 0mb internal storage, I flashed the Magisk.zip from adb command, and rebooted it.
Since then, my phone is completely stucked at fastboot, I've tried and followed almost every xda suggestion and everything, I've tried flashing flash.bat file, I've tried flashing stock recovery, In fact I've tried flashing complete fastboot Rom (with all in one app)and it everytime boots me into Fatboot.
Please, help me out guys. I'm stressed out of this problem since yesterday's night.
Let me know your suggestions.
Maybe THIS can help you?
Actually this thread helped me just now in the same situation:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
That thread Jonsat mentioned didn't help me either, at all. Its not very clear that thread, telling in the thread to unbrick a OP7 to look at the thread of the OP6, there send them to OP5 and so on, eventually having to use a short written manual for the OP3 which mentions different versions and so on, its not the best for inexperienced people like me, it just send me on a wild chase downloading drivers and other things that eventually didnt work at all. Maybe I will try to rewrite it, as soon as I have enough experience to do so, i own this device for just a week.
Next time, read before you peform the install steps. It's nowhere like the older devices due to the A/B Recovery.
1. Use MSM Downloader to put you back to stock.
2. Upgrade to Android 10
3. Factory Reset to Clean out your phone (don't forget to unlock bootloader)
4. Initialize phone
5. Boot twrp (specific to Android Q + OP7 Pro)
6. Install TWRP and Magisk from TWRP
7. reboot and enjoy your rooted phone
lloydlim996 said:
Next time, read before you peform the install steps. It's nowhere like the older devices due to the A/B Recovery.
1. Use MSM Downloader to put you back to stock.
2. Upgrade to Android 10
3. Factory Reset to Clean out your phone (don't forget to unlock bootloader)
4. Initialize phone
5. Boot twrp (specific to Android Q + OP7 Pro)
6. Install TWRP and Magisk from TWRP
7. reboot and enjoy your rooted phone
Click to expand...
Click to collapse
What is MSM download tool? I'm going to try using All in One.
On searching for MSM tool, I found https://www.techoxygen.com/msm-download-tool/ is that correct?
Scratch this, MSMdownload is part of zip, I'll read through https://forum.xda-developers.com/showpost.php?p=79972789&postcount=50 and see how it goes
Dear oneplus community,
the recent days I wanted to update my stock system and keep my magisk at the same time. But somehow things messed up and lost my root status so I had to go back and flash magisk via twrp again. Since I didn't install twrp as default recovery, I had to boot manually into it.
Here is one of the first issues: the command "fastboot boot recovery.img" had an output line which said that the file is unauthorized. That is quite a common error so I booted into twrp via the all in one tool. Alright here I am in the recovery, ready to install magisk again as usual. Now I am facing the unable to mount vendor, storage and system error, so I fixed it by going to exfat and back to ext4 if I am correct.
Now somehow things messed up even more because at this point I was stuck in a boot loop. I managed to get out of it with the MSM back to stock method.
So in the end I got a stock android 10 oxygenos system I want to have magisk on it again. But when I try to get into the recovery mode sometimes itll work and sometimes it wont. Sometimes the command prompt gives me the unauthorized error message again and sometimes I get stuck in the fastboot mode screen with the oneplus logo.
Eventually I get into the recovery by using various methods e.g. all in one tool, but also here it happenes that the command prompt gives me the unauthorized error.
At this point everything seems to be okay with the installation of magisk (no errors, etc.). But when I'm trying to boot up from the recovery it says that I have no OS installed whether I have magisk installed or not. In a second and third try I additionally tried to flash a rom before installing magisk so I am sure to actually having a OS installed. But it still gives me the same error.
Any ideas how to deal with that, so that I can install magisk on my stock rom properly without having these weird issues.
At this point I'm losing the belief in myself because it shouldn't be that hard at all, since I already rooted my previous phones like mi6 the oneplus 6 haswell..
I will post error codes later.
Thank you.
I actually just started a thread about installing TWRP and magisk yesterday. I am having the same problem installing. I assume it's the versions of each file that I am using that are incompatible, because I am following the instructions as written.
https://forum.xda-developers.com/oneplus-7-pro/help/current-twrp-magisk-unlocked-oneplus-7-t4094307
At this point, since no one seems to know what the problem is, I'm just gonna stay on stock, unlocked bootloader, no root. Which defeats the purpose of even having an unlocked bootloader, but at least I'll have functioning phone. If you need to install an OS on your phone, follow this method.
https://forum.xda-developers.com/oneplus-7-pro/how-to/bricked-oneplus-7-pro-stuck-fastboot-t3972469
This will get you back to factory settings, unlocked bootloader.
+1 here, actually quite confused how to get TWRP properly so it sticks, amd confused about two slots situation.
Now going back to stock via MSM Method. Im in a bootloop/bricked device again.
I'll try to do it one more time and i'll document my steps detailed, so more experienced users can follow the steps better.
Silencex33 said:
Now going back to stock via MSM Method. Im in a bootloop/bricked device again.
I'll try to do it one more time and i'll document my steps detailed, so more experienced users can follow the steps better.
Click to expand...
Click to collapse
Get twrp from here https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3932943. 3.3.1-79
im about to try this on my tmob oneplus 7 pro, any suggestions as to if I should wait for new updates ?
I have always used the "restore images" method to keep my Magisk after applying OTA updates (Magisk Manager -> Uninstall -> Restore images -> [update without rebooting] -> Magisk Manager -> Install to inactive slot), but after today's update, it didn't quite work. Now my phone won't boot, saying "Can't load Android system. Your data may be corrupt".
Now, I didn't realize it at first, but this was a more major update - an upgrade from Android 9 to Android 10, which is likely the problem. The error screen shows: "motorola/ocean_retail/ocean10/QPO30.52-29". The most I can do is perform a big factory reset (which might not even work) or reboot to stock recovery (do not have TWRP, as I installed Magisk before it was available for G7 Power and missed its release since).
Now, my go-to idea for a solution is to download the most recent ROM I can find - which unfortunately can't be the brand new Android 10 one, as it seems it's nowhere to be found yet - and flash the boot.img from it (and worry about reinstalling Magisk later, shouldn't be that much of a problem). However, I'm not sure if it's going to work, as perhaps an update this big has changed more than usual. Obviously I'd like to restore my phone to a state as close as possible to what it was yesterday, so before reflashing the entire ROM, I'd like to seek advice regarding any other solutions if possible.
I've also considered trying to use the Rescue and Assistant Tool to possibly download a good ROM. Does anyone have experience with this app?
I'd very much appreciate any and all help.
eworm92 said:
I have always used the "restore images" method to keep my Magisk after applying OTA updates (Magisk Manager -> Uninstall -> Restore images -> [update without rebooting] -> Magisk Manager -> Install to inactive slot), but after today's update, it didn't quite work. Now my phone won't boot, saying "Can't load Android system. Your data may be corrupt".
Now, I didn't realize it at first, but this was a more major update - an upgrade from Android 9 to Android 10, which is likely the problem. The error screen shows: "motorola/ocean_retail/ocean10/QPO30.52-29". The most I can do is perform a big factory reset (which might not even work) or reboot to stock recovery (do not have TWRP, as I installed Magisk before it was available for G7 Power and missed its release since).
Now, my go-to idea for a solution is to download the most recent ROM I can find - which unfortunately can't be the brand new Android 10 one, as it seems it's nowhere to be found yet - and flash the boot.img from it (and worry about reinstalling Magisk later, shouldn't be that much of a problem). However, I'm not sure if it's going to work, as perhaps an update this big has changed more than usual. Obviously I'd like to restore my phone to a state as close as possible to what it was yesterday, so before reflashing the entire ROM, I'd like to seek advice regarding any other solutions if possible.
I've also considered trying to use the Rescue and Assistant Tool to possibly download a good ROM. Does anyone have experience with this app?
I'd very much appreciate any and all help.
Click to expand...
Click to collapse
Hi. What software channel does your device have? There's already android 10 firmware available
LuisLFSS said:
Hi. What software channel does your device have? There's already android 10 firmware available
Click to expand...
Click to collapse
I've been running a RETAIL ROM and despite the software update channel showing in the settings as RETEU, the other OTA updates installed fine.
In this case what I've done is:
a) tried to "restore images" and install OTA normally. This didn't work - had to reflash the Android 9 ROM
b) tried to download and install the Android 10 RETAIL ROM from lolinet. This also didn't work. Reflashed again.
c) tried to flash the Android 10 RETEU ROM from lolinet. Same result again.
d) tried to flash the Android 9 RETEU ROM from lolinet. This actually worked no problem and I am now on this ROM, matching my software update channel.
e) tried to "restore images" and install OTA normally again, now that the software update channel is the same as the ROM I'm running. Still didn't work.
f) tried to uninstall Magisk and then install OTA normally. Even this didn't work.
I really have no idea what is wrong. For now, I've decided to simply not update but if someone has an idea on what might help, I'd be glad to hear it.
On a side note, when I got to that screen, not even re-flashing the OTA, correctly this time, (beware, new updates have 10 sparse system chunks instead of 9...) let me get past it, so the solution was to erase userdata. (no re-flashing involved) As for Magisk, I just re-patch/flash boot.img at every update, it's not like it's updated that frequently
eworm92 said:
I've been running a RETAIL ROM and despite the software update channel showing in the settings as RETEU, the other OTA updates installed fine.
In this case what I've done is:
a) tried to "restore images" and install OTA normally. This didn't work - had to reflash the Android 9 ROM
b) tried to download and install the Android 10 RETAIL ROM from lolinet. This also didn't work. Reflashed again.
c) tried to flash the Android 10 RETEU ROM from lolinet. Same result again.
d) tried to flash the Android 9 RETEU ROM from lolinet. This actually worked no problem and I am now on this ROM, matching my software update channel.
e) tried to "restore images" and install OTA normally again, now that the software update channel is the same as the ROM I'm running. Still didn't work.
f) tried to uninstall Magisk and then install OTA normally. Even this didn't work.
I really have no idea what is wrong. For now, I've decided to simply not update but if someone has an idea on what might help, I'd be glad to hear it.
Click to expand...
Click to collapse
This is kinda weird because reflash stock ROM android 10 should work for you... What errors did you get when trying to flash android 10?
eworm92 said:
I have always used the "restore images" method to keep my Magisk after applying OTA updates (Magisk Manager -> Uninstall -> Restore images -> [update without rebooting] -> Magisk Manager -> Install to inactive slot), but after today's update, it didn't quite work. Now my phone won't boot, saying "Can't load Android system. Your data may be corrupt".
Now, I didn't realize it at first, but this was a more major update - an upgrade from Android 9 to Android 10, which is likely the problem. The error screen shows: "motorola/ocean_retail/ocean10/QPO30.52-29". The most I can do is perform a big factory reset (which might not even work) or reboot to stock recovery (do not have TWRP, as I installed Magisk before it was available for G7 Power and missed its release since).
Now, my go-to idea for a solution is to download the most recent ROM I can find - which unfortunately can't be the brand new Android 10 one, as it seems it's nowhere to be found yet - and flash the boot.img from it (and worry about reinstalling Magisk later, shouldn't be that much of a problem). However, I'm not sure if it's going to work, as perhaps an update this big has changed more than usual. Obviously I'd like to restore my phone to a state as close as possible to what it was yesterday, so before reflashing the entire ROM, I'd like to seek advice regarding any other solutions if possible.
I've also considered trying to use the Rescue and Assistant Tool to possibly download a good ROM. Does anyone have experience with this app?
I'd very much appreciate any and all help.
Click to expand...
Click to collapse
Next time do the following:
1. Restart to bootloader
2. connect to PC, open ADB terminal and type
"fastboot getvar all" to get active slot
3. change active slot by
"fastboot -aa" => change to slot _a
"fastboot -ab" => change to slot _b
You are running a A/B device. Is there is any error after an update then change the slot to the last working one.
eworm92 said:
I've been running a RETAIL ROM and despite the software update channel showing in the settings as RETEU, the other OTA updates installed fine.
In this case what I've done is:
a) tried to "restore images" and install OTA normally. This didn't work - had to reflash the Android 9 ROM
b) tried to download and install the Android 10 RETAIL ROM from lolinet. This also didn't work. Reflashed again.
c) tried to flash the Android 10 RETEU ROM from lolinet. Same result again.
d) tried to flash the Android 9 RETEU ROM from lolinet. This actually worked no problem and I am now on this ROM, matching my software update channel.
e) tried to "restore images" and install OTA normally again, now that the software update channel is the same as the ROM I'm running. Still didn't work.
f) tried to uninstall Magisk and then install OTA normally. Even this didn't work.
I really have no idea what is wrong. For now, I've decided to simply not update but if someone has an idea on what might help, I'd be glad to hear it.
Click to expand...
Click to collapse
Check if you're running 10 sparse system image flash commands instead of 9 (The only difference between flashing Android 9/10)
I've tried everything proposed above: flashed to both slots, made sure to flash all 10 system sparsechunks.
I guess the solution is to erase userdata, which I've avoided doing thus far. What exactly am I gonna lose if I do?
eworm92 said:
I've tried everything proposed above: flashed to both slots, made sure to flash all 10 system sparsechunks.
I guess the solution is to erase userdata, which I've avoided doing thus far. What exactly am I gonna lose if I do?
Click to expand...
Click to collapse
Erasing userdata will make it like you had just bought the phone. (factory reset) I also had to do that, but I assumed it was because I'd forgotten to flash the 10th system sparsechunk, which caused a bootloop asking me to do a factory reset no matter what I did. (Unless blankflash/flashing Android 9 image was the solution, I just flashed the missing sparsechunk and erased userdata)
I'm just confused because it is an update. I'm supposed to be able to keep my data.
eworm92 said:
I'm just confused because it is an update. I'm supposed to be able to keep my data.
Click to expand...
Click to collapse
You're right, you should keep your data. But I had the same issue on my Moto G6 plus. It was only a security patch update without an Android upgrade.
After it was successfully installed I wasn't able to boot and had to erase my data.
Before factory reset, try switching partition for backup
I basically ran into the same problem today, the update banner popped up at an unfortunate moment and I clicked it in accident. I was also running a RETAIL rom.
The G7 Power didn't boot anymore, instead complaining that the image was corrupted, and did not go into recovery.
adb saw nothing, fastboot saw the device after the usual reboot into bootloader.
A mate of mine suggested switching to partition b with `fastboot set_active b` (or a if yours is set to b already) and after rebooting it failed to start ocean 9 instead of 10. Success ?! On the second reboot it came back up normal, which allowed me to do a normal backup of things before getting into the hassle of upgrading (which I have put off until I have more time).
ElFalko said:
I basically ran into the same problem today, the update banner popped up at an unfortunate moment and I clicked it in accident. I was also running a RETAIL rom.
The G7 Power didn't boot anymore, instead complaining that the image was corrupted, and did not go into recovery.
adb saw nothing, fastboot saw the device after the usual reboot into bootloader.
A mate of mine suggested switching to partition b with `fastboot set_active b` (or a if yours is set to b already) and after rebooting it failed to start ocean 9 instead of 10. Success ?! On the second reboot it came back up normal, which allowed me to do a normal backup of things before getting into the hassle of upgrading (which I have put off until I have more time).
Click to expand...
Click to collapse
That's the advantage of the A/B partition scheme. I already advised him to do so in post #6...
BTW: "adb devices" will recognizes your device only when fully booted up into system or TWRP.
WoKoschekk said:
That's the advantage of the A/B partition scheme. I already advised him to do so in post #6...
BTW: "adb devices" will recognizes your device only when fully booted up into system or TWRP.
Click to expand...
Click to collapse
Seems I was selectively blind I read #5 and #7 and somehow skipped that one exactly.
It's been a while since I did anything with adb, so I wasn't sure about when it detects things. I tried getting into TWRP, but at least on the A partition TWRP had been wiped by the update.
Anyway thanks for the solid advice!