Cannot load android system. Your data may be corrupt. - Moto G Stylus (Moto G Pro) Questions & Answers

When booting up, I am getting the error: "Cannot load android system. Your data may be corrupt." I have MotoG Stylus with an unlocked bootloader and rooted with Magisk. The last thing I was doing was uninstalling apps with Debloat in the terminal... so maybe I removed one I shouldnt have... but all I was trying to do was disable the system Phone app and was trying to be careful.
I can get to bootloader screen and to recovery screen. I was hoping I could get a shell with my Macbook and get to Debloat and restore the apps. However, it seems like I won't be able to get shell from Bootloader or Recovery screen. I think I could sideload from the recovery screen

Reflash stock rom
Sent from my moto g stylus using Tapatalk

Related

[Help] Installing VenomXL+ on AT&T HTC One X+

Before I get into the gist of my current problem I think it might be relevant to provide some backstory. I decided I wanted to try and root my phone so I could install a new custom ROM. I had done some jailbreaking back when the iPod touches came out, back when jailbreaking was extremely ghetto and unreliable, so I figured I could teach myself this fairly easily. I unlocked bootloader using the htcdev method without an issue, and, following a guide, downloaded something called Rootboot to flash the phone. There was only one step to this portion, so I assumed it would be easy. Running the rootboot started rooting my phone, however after a couple of lines in the command prompt it said something about the adb, failed, and the phone was stuck in a boot loop with no roms on it at all. I stayed up all night with the damn thing attempting to fix it, and at one point, actually got it to load up the stock ROM from the computer using some combination of RUU's and fastboot commands. I have no clue how I did it, all I know is that it was not through adb sideload because the recovery I had at the time wouldn't work with adb sideload for whatever reason. It was the recovery that came with the All-In-One toolkit, for the AT&T / TELUS version. At this point I figured since the phone was working I would just install the VenomROM, and after a few hours of playing around with fastboot and the bootloader trying to get a ROM loaded, I figured I was familiar enough with all of them to load the ROM.
Which is what brings me to my current issue. I KNOW the boot.img is flashed to the device because I used the All-In-One Toolkit to do it, erased the cache, did it again using fastboot commands in the command prompt, erased the cache, and continued to use recovery to install the ROM. I got it to load and install, cleared the darvik cache, data, and cache, but when booting, the phone would get to the lock screen, upon which sliding to unlock, presented me with a white screen that says "htc" on it instead of a launcher. After a couple of seconds of waiting, it says, "setup has quit responding" and gives me the option to close or to wait. Either option results in the phone rebooting wherein I only see a black screen with the notification bar at the top displaying my battery and no internet/network connection. I have gone back and flashed the boot.img again and cleared cache, darvik cache, and data several times and just have no clue what I'm doing wrong to not get this phone to boot with the ROM. I can reflash at any point from my sideload.zip file and the installation process has an option to flash the kernel (boot.img) because it is included in the zip. Any help would be much appreciated. I highly doubt theres anything wrong with the ROM or boot.img, it is probably me just not doing it right.
I am using (or attempting to use) the 1.2.7 version of VenomXL+ on the HTC One X+ along with TWRP 2.5 as the recovery.

LG volt apparently has no bootloader. Recovery and factory reset both broken.

I didn't find a thread for the Volt, model LS740 on Virgin Mobile. Rooted by the original owner. So I'm posting it here. I'm using adb on Ubuntu.
So I'm trying to repair a broken system by reflashing the stock ROM. I suspect the previous owner(who rooted) may have removed multiple important system apps. Upon doing a factory reset it has no home launcher or keyboard. As soon as the screen turns off it loops a com.android.systemui has stopped. Every boot you need to do a factory reset to get it to work: booting once, then again will loop the systemui crash, requiring a factory reset to work.
The android recovery works, I can get to it, but it offers install update from cache, adb, or sd card. The phone will not recognize sd card while it is in recovery, and adb doesn't work in recovery, only while booted. Copying recovery image to cache fails at 71%, I suspect the phone does not have enough RAM to move 1.17 GB from A to B. The phone may also not have spare storage space. I'm working on finding an sd card so I can try copying from there.
"adb reboot bootloader" reboots the phone normally. If there's a bootloader it skips it entirely. I found threads that say uncheck fast boot in power/battery options, but I have no such check box.
Right now, I have adb, images/zips for twrp recovery and stock rom, and I can push apks for a launcher and keyboard. But I apparently can't access bootloader or install rom via recovery. I don't have an sd card to try and copy the rom to cache, which I will try as soon as I get a card.
Adb cannot run as root, I get "adbd cannot run as root on production builds. So I can't directly push the rom to /cache/backup using adb.
Any help? I tried to get it all out there so that you guys could help better. Thanks for reading all that.
Fixed it by finding an LG recovery reflash utility and reflashing a factory version.

My Moto G XT1033 Hard Bricked

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:

[Completed] Help with reinstalling bootloader

Hi.
I am relatively experienced user who has rooted and installed custom roms on samsung galaxy and HTC desire phones before.
I have now attempted to root my alcatel onetouch pixi 4 (4034X) using instructions from this thread :- https://forum.xda-developers.com/android/general/alcatel-one-touch-pixi-4-t3376597
I got as far as flashing twrp recovery and now the phone is stuck in constant reboot. I downloaded alcatels mobile upgrade tool in hopes of reflashing the stock rom but it seems to be looking for a later rom than the one I have installed and keeps telling me I have the lastest and so wont flash.
So can I recover from this at all or have I just bricked my phone? Is there a way to FORCE the mobile upgrade tool to reflash the current rom rather than looking for an upgrade?
It seems that everything except the bootloader is intact so is there another tool I can use to restore the bootloader?
Any help would be greatly appreciated.
Looks like I managed to unbrick using a combination of SP Flash tool and an SPFT rom for the 4034X I found on the internet. will now try reflashing a different recovery tool.
O.K. so I think what is happening is an issue when unlocking the bootloader and not when flashing recovery.
This is what I did:-
1. Enabled developer mode.
2. Turned on usb debugging and unlocked bootloader oem
3. Rebooted phone, plugged in cable and accepted connection authorisation.
4. From windows typed adb reboot bootloader. Went into to fastboot.
5. Typed fastboot oem unlock, Pressed volume up on phone.
At this point I was put back in fastboot but none of the buttons worked and the phone looked like it had frozen. Was It wiping data at this point? There was no indication that it was doing anything.
I removed the battery and reinserted but when I restarted I got the same boot loop problem. Had to restore stock firmware AGAIN.
Am I doing something wrong?
Update: I managed to install caliv touch recovery without unlocking the bootloader by using the same sp flash tool I used to restore the stock rom. However, I cant install root. The recovery will only let me sideload and I could only find the chainfire SU binaries for sideload (SuperSU 2.78-SR1 and superSU 2.46). Both of these seem to flash ok using adb sideload with ctr recovery but the phone hangs at the boot logo. I also had superuser-r197 (ph's sueruser) but that wouldn't sideload.
So I now have a custom recovery but still can't root
Has anyone succesfully rooted the 4034X (UK)? If so, how?
nyarlathotep_uk said:
Update: I managed to install caliv touch recovery without unlocking the bootloader by using the same sp flash tool I used to restore the stock rom. However, I cant install root. The recovery will only let me sideload and I could only find the chainfire SU binaries for sideload (SuperSU 2.78-SR1 and superSU 2.46). Both of these seem to flash ok using adb sideload with ctr recovery but the phone hangs at the boot logo. I also had superuser-r197 (ph's sueruser) but that wouldn't sideload.
So I now have a custom recovery but still can't root
Has anyone succesfully rooted the 4034X (UK)? If so, how?
Click to expand...
Click to collapse
Hi & welcome to xda-assist,
you can try to force the installation of supersu systemless by this step, chances are good that this will make it boot properly.
boot into twrp >go to the terminal > and type:
echo SYSTEMLESS=false>>/data/.supersu
Don't know if the recovery you use has this terminal option but it's very likely.
You can do additional a Google search on "force SuperSU systemless" to get more information / background information..
Good luck
Sent from my OnePlus 2 using XDA Labs
Thanks for your reply Sam.
I only read that after I had found a copy of a CM13 Rom that worked with The 4034X. I basically flashed superSU first then did a wipe, then installed the custom rom and google apps nano before downloading the supersu apk from google play and reinstalling. Now I have a rooted phone with a custom rom and am somewhat happier. The reason I wanted to root was to remove the bloatware that was taking up 1.5 GB of my already measly 2GB internal memory and this new ROM only takes up .5 GB.
I still have some pain. For example many of the Rom Toolbox Pro functions don't work and I think its because the system image seems protected and refuses to mount rw no matter what I do. Even issuing a remount command using the device name from cat /proc/mounts tells me the block device is read only. I also seem to be unable to verify if I have busybox or install it due to the same reason.
It also took me some time to work out that the boot animations weren't stored in /data/local or /system/media but to /data/system/theme.
This used to be so much easier in the days of ice cream sandwich and lollipop. Ah well!
Update:- Managed to flash busybox 1.26 using a flashable zip via adb sideload in Caliv Recovery (Caliv can't see my adopted storage for some reason).
I'm happy now! Would still like to have a rw system so I can remove some system apps I don't use but its no biggie.

Issues rooting my oneplus 7 pro / installing twrp properly

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 ?

Categories

Resources