Database Develop

[Q] Deleted the SYSTEM partition xt980

Well, I deleted the system partition of my Motorola XT 980... I had it rooted and updated to 4.1.2 before that. Now it won't boot, RDS won't find the device and i have no means to restore the system. I haven't been able to find info on that, so if someone could help me (either by telling me how to instal the O.S. again, restoring the SYSTEM partition, or redirecting me to some other post), I'd be so thankful. Sorry to bother you guys, but I have not much experience in this. Thanks, again.
Braulio Alvarez D.

Can you boot on recovery or fastboot?
Enviado desde mi XT890 usando Tapatalk

Marco Lomas said:
Can you boot on recovery or fastboot?
Enviado desde mi XT890 usando Tapatalk
Click to expand...
Click to collapse
no, it wont reboot on either of them.

System partition is damage or deleted files. Cause you should without a problem enter fastboot. If you have problems enter fastboot, it's seems that you had done something more than only delete system partition. Or, If you see red logo Motorola and after that bootloop you should enter fastboot, maybe you don't do it properly
Wysyłane z mojego XT890 za pomocą Tapatalk 2

skupi20 said:
System partition is damage or deleted files. Cause you should without a problem enter fastboot. If you have problems enter fastboot, it's seems that you had done something more than only delete system partition. Or, If you see red logo Motorola and after that bootloop you should enter fastboot, maybe you don't do it properly
Wysyłane z mojego XT890 za pomocą Tapatalk 2
Click to expand...
Click to collapse
I remember I went to recovery menu and choose delete system partition, or something like that. since then, even RDS won't read the phone. Any other ideas? Thank you.

celebdrake said:
I remember I went to recovery menu and choose delete system partition, or something like that. since then, even RDS won't read the phone. Any other ideas? Thank you.
Click to expand...
Click to collapse
1) Download your firmware from the repo.
2) RSDLite.
3) Turned off XT890 -> To USB with a pushed Camera button.
Or simply check out a "unbrick" thread.

solved!
so, i unbricked the razr i. followed several posts... TY xdaDevs!

Problem with titanium backup and root Explorer

Well I'm trying follow the steps of the thread of battery life to try get an 0.1% of drain per hour but when I try to uninstall the apps ( velvet apk, play services and other apps) the apps appear uninstalled then reboot and it's again the apks on system folder any ideas? Or am I doing something wrong? Thanks in advance
Enviado desde mi XT1058 mediante Tapatalk

Do you have system write protection off? You have be able to write to system for changes to stick

gunnyman said:
Do you have system write protection off? You have be able to write to system for changes to stick
Click to expand...
Click to collapse
Maybe that's the problem, where can I change the system write protection, that is the answer to many questions, like I can't use xposed an sole others, so we're can I turn it off? Thanks for the answer
Enviado desde mi XT1058 mediante Tapatalk

hermeshhn said:
Maybe that's the problem, where can I change the system write protection, that is the answer to many questions, like I can't use xposed an some others, so where can I turn it off? Thanks for the answer
Enviado desde mi XT1058 mediante Tapatalk
Click to expand...
Click to collapse
Enviado desde mi XT1058 mediante Tapatalk

Is it the dev edition? If not and you rooted using jcase method, his method replaces stock recovery with a version of Android with write protection off. So just boot into "recovery" and you'll be good
Sent from my Nexus 7 using xda app-developers app

davidtb12 said:
Is it the dev edition? If not and you rooted using jcase method, his method replaces stock recovery with a version of Android with write protection off. So just boot into "recovery" and you'll be good
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Isn't the dev edition, that method is on Android development? Thanks in advance
Enviado desde mi XT1058 mediante Tapatalk

hermeshhn said:
Isn't the dev edition, that method is on Android development? Thanks in advance
Enviado desde mi XT1058 mediante Tapatalk
Click to expand...
Click to collapse
Yes. If you've rooted with Jcase's method, you need to reboot into "recovery" mode to have system writable.
you can either use adb reboot recovery command or install something like quickboot app and choose reboot recovery.

gunnyman said:
Yes. If you've rooted with Jcase's method, you need to reboot into "recovery" mode to have system writable.
you can either use adb reboot recovery command or install something like quickboot app and choose reboot recovery.
Click to expand...
Click to collapse
well I´ve tried what you told me but when I reboot into recovery only appear a green android with a red triangle on him, then reboot but I check the protection with adb shell getprop ro.boot.write_protect and gives me 1, when should be 0, any ideas? I´m rooted with RockMyMoto

hermeshhn said:
well I´ve tried what you told me but when I reboot into recovery only appear a green android with a red triangle on him, then reboot but I check the protection with adb shell getprop ro.boot.write_protect and gives me 1, when should be 0, any ideas? I´m rooted with RockMyMoto
Click to expand...
Click to collapse
if you rooted with jcase's method and you see a recovery like you've described either you've put the stock recovery back on the phone, or you haven't rooted properly.
Putting back stock recovery breaks the system write capability of the root method.

Just 'Freeze' the applications. It should have the same effect on your battery life and it survives without system write protection. It also has the added benefit of being easily reversed if you accidentally disable anything important.

If you rooted using jcase's method, the recovery was hijacked. This means that instead of rebooting into a recovery when you "reboot recovery," it'll reboot the phone normally, but write protection will be off. This allows you to do what you want to do (i.e. remove apps/bloatware). Once that's done, you'd reboot and everything would be normal and write protection would be turned on again.

Trouble flashing

Hi
Im having an strange trouble flashing firms or roms, from adb rsd or fastboot.
I can flash radio, cdrom and everything except for /system.
Another thing: I tried compressing /system (in pc) uploading with adb push and extract the zip, that method work but for sure dont boot.
I have already Motorola unlocked. And i cant pass the recovery or bootloader.
If usefull when i try to adb push each folder of system from system pc folder in any point it stucks forever and i cant mounting again unless erase it.
Btw: sorry for bad english. :silly:

When you flash from fastboot does it show an error?
Sent from my XT1095 using Tapatalk

AGISCI said:
When you flash from fastboot does it show an error?
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Any error Just stucks forever. In fastboot or rsd.
Enviado desde mi GT-S5301 mediante Tapatalk

U said u have a unlocked bootloader and can't pass the recovery. What do u mean by that? Can't flash it or can't boot it from the bootloader menu

Hazou said:
U said u have a unlocked bootloader and can't pass the recovery. What do u mean by that? Can't flash it or can't boot it from the bootloader menu
Click to expand...
Click to collapse
Sorry is my bad english.
What i want to say is i only can see bootloader, the fastboot menú and cwm recovery. But i cant boot the OS
Enviado desde mi GT-S5301 mediante Tapatalk

militellodante said:
Sorry is my bad english.
What i want to say is i only can see bootloader, the fastboot menú and cwm recovery. But i cant boot the OS
Enviado desde mi GT-S5301 mediante Tapatalk
Click to expand...
Click to collapse
Format system through the CWM recovery and try to install one of the ROM zips.

Hazou said:
Format system through the CWM recovery and try to install one of the ROM zips.
Click to expand...
Click to collapse
Stucks on /system too.

militellodante said:
Stucks on /system too.
Click to expand...
Click to collapse
Ok, and "fastboot erase system" also didn't work? Or did it give an error?

Hazou said:
Ok, and "fastboot erase system" also didn't work? Or did it give an error?
Click to expand...
Click to collapse
I get no errors, i can erase from mfastboot or fastboot, and format it from cwm.
But I THINK, is an I/O error... there is a way to do something like "chkdsk" but in android?

Xiaomi Mi A1 Magisk 15.3 (Help)

How to completely uninstall magisk 15.3 installed on my stock 7.1.2
When i tried the latest uninstaller and flash it thru twrp i got bootloop same as when I restore my stock boot image back up from twrp i also got bootloop i wanted to update because i already received the ota of oreo 8.0 January update
Magisk v15.3
Xiaomi mi a1
7.1.2 December Security patch
Sent from my Mi A1 using Tapatalk

Try pulling the boot image file from the December update and flash that.
But, remember that you'll also have to restore your stock recovery to be able to install an OTA. Unless you're using "fastboot boot" to just run TWRP without installing...

Didgeridoohan said:
Try pulling the boot image file from the December update and flash that.
But, remember that you'll also have to restore your stock recovery to be able to install an OTA. Unless you're using "fastboot boot" to just run TWRP without installing...
Click to expand...
Click to collapse
yes i already did that but no luck :crying: still bootloop
i only boot twrp not flash, so i have the stock recovery

paul222008 said:
yes i already did that but no luck :crying:
Click to expand...
Click to collapse
You've obviously got something else going on. Magisk only really modifies your boot image, so if you can't get your device to boot after restoring a stock image it's most likely not Magisk causing it. Your device's forum might be the best place to ask for assistance.
Thought: are you sure it's just not a long boot? If you had decrypted your device, for example, it would start encrypting as soon as you flash a stock boot image and reboot.

Didgeridoohan said:
You've obviously got something else going on. Magisk only really modifies your boot image, so if you can't get your device to boot after restoring a stock image it's most likely not Magisk causing it. Your device's forum might be the best place to ask for assistance.
Thought: are you sure it's just not a long boot? If you had decrypted your device, for example, it would start encrypting as soon as you flash a stock boot image and reboot.
Click to expand...
Click to collapse
Im encrypted also [emoji55]
Sent from my Mi A1 using Tapatalk

What could the best way to do? My concern here is to preserve my app data
Sent from my Mi A1 using Tapatalk

paul222008 said:
What could the best way to do? My concern here is to preserve my app data
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
Dirty flash a full update package (not an OTA file). Don't know if that's possible for you, but it would do it.

Didgeridoohan said:
Dirty flash a full update package (not an OTA file). Don't know if that's possible for you, but it would do it.
Click to expand...
Click to collapse
How? There's only .zip of ota available for my device
Sent from my Mi A1 using Tapatalk

paul222008 said:
How? There's only .zip of ota available for my device
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
Like I said earlier: Your device's forum might be the best place to ask for assistance.

TWRP no os installed

I was trying trying to update color os and messed something up. on twrp im unable to mount system and it shows 0mb. how do i fix this?

xHvlios said:
I was trying trying to update color os and messed something up. on twrp im unable to mount system and it shows 0mb. how do i fix this?
Click to expand...
Click to collapse
You fix that by flashing the vbmeta
Enviado desde mi RMX1931 mediante Tapatalk

Sergiocubano1 said:
You fix that by flashing the vbmeta
Enviado desde mi RMX1931 mediante Tapatalk
Click to expand...
Click to collapse
Did that now its booting straight to bootloader

xHvlios said:
Did that now its booting straight to bootloader
Click to expand...
Click to collapse
also says unhandled flag wrappedkey in twrp

xHvlios said:
also says unhandled flag wrappedkey in twrp
Click to expand...
Click to collapse
install Orange Fox and Orange Fox vbmeta and it will work for you, have you installed any magisk module?
Enviado desde mi RMX1931 mediante Tapatalk

Sergiocubano1 said:
install Orange Fox and Orange Fox vbmeta and it will work for you, have you installed any magisk module?
Enviado desde mi RMX1931 mediante Tapatalk
Click to expand...
Click to collapse
No i formatted data and wiped the partitions.

xHvlios said:
No i formatted data and wiped the partitions.
Click to expand...
Click to collapse
also says failed to mount system

xHvlios said:
also says failed to mount system
Click to expand...
Click to collapse
If that happens with the maroonfrio twrp, but with the Orange Fox and the vbmeta that is in Orange Fox it no longer happens, install and then flash the vbmeta, and if it does not enter, flash the ROM again
Enviado desde mi RMX1931 mediante Tapatalk

Sergiocubano1 said:
If that happens with the maroonfrio twrp, but with the Orange Fox and the vbmeta that is in Orange Fox it no longer happens, install and then flash the vbmeta, and if it does not enter, flash the ROM again
Enviado desde mi RMX1931 mediante Tapatalk
Click to expand...
Click to collapse
Im onm orange fox and it says it as well. it saaid that for data but i fixed it

xHvlios said:
Im onm orange fox and it says it as well. it saaid that for data but i fixed it
Click to expand...
Click to collapse
So you already solved it? Does your mobile already work?
Enviado desde mi RMX1931 mediante Tapatalk

nope goes back to recovery

xHvlios said:
nope goes back to recovery
Click to expand...
Click to collapse
Vale install the ROM and then flash the vbmeta and it should work for you
Enviado desde mi RMX1931 mediante Tapatalk

Sergiocubano1 said:
Vale install the ROM and then flash the vbmeta and it should work for you
I went to flash stock rom and it said failed to mount /dev/block/bootdevice/by-name/userdata at /data device our resource busy
Click to expand...
Click to collapse

should i flash the vbmeta in the recovery?

xHvlios said:
should i flash the vbmeta in the recovery?
Click to expand...
Click to collapse
if from Orange Fox you flash the vbmeta and you flash vbmeta, then it starts normal
Enviado desde mi RMX1931 mediante Tapatalk

Sergiocubano1 said:
if from Orange Fox you flash the vbmeta and you flash vbmeta, then it starts normal
Do i flash it in orange fox? If so what partition does it use? system or what ?
Click to expand...
Click to collapse

xHvlios said:
Sergiocubano1 said:
if from Orange Fox you flash the vbmeta and you flash vbmeta, then it starts normal
Do i flash it in orange fox? If so what partition does it use? system or what ?
Click to expand...
Click to collapse
When you flash the rom, just open the vbmeta and it will tell you where you want to flash it, and you choose to flash in the vbmeta, Then it will open normally, the error you get when flashing the quiet ROM that still works
Enviado desde mi RMX1931 mediante Tapatalk
Click to expand...
Click to collapse

I already typed the command fastboot flash vbmeta vbmeta.img and it said that finished. but i still cant boot into the system

xHvlios said:
I already typed the command fastboot flash vbmeta vbmeta.img and it said that finished. but i still cant boot into the system
Click to expand...
Click to collapse
You have to flash it from the recovery, I did it from the computer and it did not work for me either
Enviado desde mi RMX1931 mediante Tapatalk

Ok i did it with orange recovery and im reflashing the rom. Ill tell you if it works.