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!
Related
Hi,
my phone (XT890 EU version running JB 4.1.2) is stuck at the Motorola logo when booting up. A couple of days ago,it started acting sluggish and would power itself down. It would take much longer than normal to boot up and then yesterday it got stuck on the M logo.
I have tried wiping the cache and doing a factory restore through Recover via the fastboot option,but still no success.
The bootloader is not unlocked.
I have tired flashing through RSD but with both ROMs (EU & GB) abort during the flashing process at step 8 of 12.
The error message reads:
Flashing process failed 8/12 flash system "sytem_signed" -> phone returned
The two JB roms i used were: CFC_9.8.2I-50_SMI-29_S7_USASMIJBRTGB.xml and CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml.
I also tried to flash a smaller ROM (57mb) through SD card when in Recovery mode (Blur_Version.81.5.31006.XT890.Retail.en.EU), but it craps out during install.
Will another ROM work or is it totally screwed?
Have you tried wiping system and dalvik cache before installing any of the ROMs you mentioned above?
Sent from my XT890 using XDA Premium 4 mobile app
Yes I have done both but only 1 time before trying to flash.
Should i have wiped again before trying to flash another ROM?
eoinoc79 said:
Yes I have done both but only 1 time before trying to flash.
Should i have wiped again before trying to flash another ROM?
Click to expand...
Click to collapse
Well, I always wipe system and dalvik because old system files may conflict with the new ROM you're installing and getting your phone not to boot, so you should have wiped it before installing ROMs. If you wouldn't like to lose anything while installing a ROM do a nandroid backup and if something goes wrong you can solve it with a simple restore.
Sent from my XT890 using XDA Premium 4 mobile app
Hashmutz said:
Well, I always wipe system and dalvik because old system files may conflict with the new ROM you're installing and getting your phone not to boot, so you should have wiped it before installing ROMs. If you wouldn't like to lose anything while installing a ROM do a nandroid backup and if something goes wrong you can solve it with a simple restore.
Sent from my XT890 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did another cache wipe and factory restore and tried to flash again but RSD failed at same point again.
the phone said the following during flashing.......
fastboot reason: reboot to bootloader
fastboot: max download size: 100mb
USB connected
Downloading....
Flashing boot....
Downloading...
Flashing recovery.....
Downloading...
Flashing motobp...
Motobp image flashed
Downloading...
Fastboot command failed
Can you unlock your bootloader? Because you may be getting error because the file is larger than 100mb.
Sent from my XT890 using XDA Premium 4 mobile app
No I cant unlock it. It was unlocked on ICS but after I took the OTA JB update, it locked it again. I have tried to unlock it through the Motorola site but it tells me my device cant be unlocked
eoinoc79 said:
No I cant unlock it. It was unlocked on ICS but after I took the OTA JB update, it locked it again. I have tried to unlock it through the Motorola site but it tells me my device cant be unlocked
Click to expand...
Click to collapse
Does it show the red M unlocked logo at start up?
Hashmutz said:
Does it show the red M unlocked logo at start up?
Click to expand...
Click to collapse
just a red M,no lock or unlock symbol
I'm almost sure it's caused by the locked bootloader..., I guess you should keep trying to unlock it.
Sent from my XT890 using XDA Premium 4 mobile app
Hashmutz said:
I'm almost sure it's caused by the locked bootloader..., I guess you should keep trying to unlock it.
Sent from my XT890 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, I also think so and it seems that the moto unlock site is kind of buggy, I needed 4 tries to get the unlock code.
Gesendet von meinem XT890 mit Tapatalk
cupioscire said:
Yes, I also think so and it seems that the moto unlock site is kind of buggy, I needed 4 tries to get the unlock code.
Gesendet von meinem XT890 mit Tapatalk
Click to expand...
Click to collapse
Hello, i dont speak english... translate please xD
Si borras la linea de comando del archivo XML, te permite instalar el sistema (incompleto...)
Tengo el mismo problema, y puedo instalar JB -> luego instalar KITKAT pero todo sin bandabase.
no he encontrado ninguna solución aún.
mmm i have the same problem, but, i erase the comand, "<step operation="flash" partition="motobp" filename="motobp" MD5="30aed3a6217273b8c681dce7a92270f4"/>" and then, i have razr without baseband..
i tried whit, bootloader lock and unlock, and the result is the same.
eso.
lucky
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.
Hi guys, I really got in trouble, i messed with some framework res apk,the phone rebooted but got stuck at the htc one image, tried several tomes to reboot but with no succes
I entered TWRP recovery, tried wipe cache, system, but nothing helps, when asked for reboot twrp says that no os is installed
I do have a backup but on the computer, but without USB Debugging activated so I don't know how to get it on the phone
I would appreciate some advices on how to get back to life my precious one
Thank you
Do a adb sideload of a rom, boot up and send your backup to your phone.
tudorlv said:
Hi guys, I really got in trouble, i messed with some framework res apk,the phone rebooted but got stuck at the htc one image, tried several tomes to reboot but with no succes
I entered TWRP recovery, tried wipe cache, system, but nothing helps, when asked for reboot twrp says that no os is installed
I do have a backup but on the computer, but without USB Debugging activated so I don't know how to get it on the phone
I would appreciate some advices on how to get back to life my precious one
Thank you
Click to expand...
Click to collapse
Michiel0912 said:
Do a adb sideload of a rom, boot up and send your backup to your phone.
Click to expand...
Click to collapse
You don't have to load a rom to be able to send your backup to the phone. You can use adb from twrp. Boot your phone in twrp and push your backup to the right directory. If you used twrp then:
adb push your_backup_folder_name /data/media/0/TWRP/BACKUPS/your_sn/your_backup_folder_name
then restore your backup
dont forget to put ''your_back_folder_name'' in the same folder you have adb/fastboot in
That's one for in the book!
alray said:
You don't have to load a rom to be able to send your backup to the phone. You can use adb from twrp. Boot your phone in twrp and push your backup to the right directory. If you used twrp then:
adb push your_backup_folder_name /data/media/0/TWRP/BACKUPS/your_sn/your_backup_folder_name
then restore your backup
dont forget to put ''your_back_folder_name'' in the same folder you have adb/fastboot in
Click to expand...
Click to collapse
Thank you sir,
but still doesn't work, it gives me error: device not found either adb push or adb sideload, even if I selected adb sideload in TWRP
other suggestions?
Install drivers
Wysłane z mojego HTC One przy użyciu Tapatalka
oldfield said:
Install drivers
Wysłane z mojego HTC One przy użyciu Tapatalka
Click to expand...
Click to collapse
I did install the drivers, for example fastboot works, but adb not, I think because I have not the USB debugging enabled
If your in TWRP, adb should be working without USB debugging enabled. So i suggest to check adb drivers.
Wysłane z mojego HTC One przy użyciu Tapatalka
oldfield said:
If your in TWRP, adb should be working without USB debugging enabled. So i suggest to check adb drivers.
Wysłane z mojego HTC One przy użyciu Tapatalka
Click to expand...
Click to collapse
Thanks for advice, but doesn't work
How do I install a rom from computer without whiping sdcard
Should I install hboot 1.44?
Solved, with a RUU, but lost everything on sdcard
tudorlv said:
Solved, with a RUU, but lost everything on sdcard
Click to expand...
Click to collapse
curious how you solved. i have a situation where adb doesnt find the device, but fastboot does. i cant sideload anything
diceman725 said:
curious how you solved. i have a situation where adb doesnt find the device, but fastboot does. i cant sideload anything
Click to expand...
Click to collapse
adb only works in custom recovery or when the phone is booted to the OS
diceman725 said:
curious how you solved. i have a situation where adb doesnt find the device, but fastboot does. i cant sideload anything
Click to expand...
Click to collapse
I found a RUU, flashed 1.4 something base and run the RUU
tudorlv said:
Solved, with a RUU, but lost everything on sdcard
Click to expand...
Click to collapse
you can side load a ROM via recovery
Sent from my One using Tapatalk
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?
Hi Guys,
Am facing this problem, and that is my Moto X-Ghost device can boot directly into system OS when I press power key to switch on the device but rather goes to Recovery/TWRP . And also when I I'm in TWRP recovery or any other recovery, I can't reboot to System and it rather boot back to TWRP again.
Please what fix do I need and how to solve this.
Please any help and guide is welcome.
Sent from my Moto X using Tapatalk
Sounds like there is no system on the phone or maybe corrupted partition.
First try formatting,restoring /system partition (a trick to have a clean partition would be to format it to f2fs and then back to ext4), once done flash a ROM on top with TWRP. Backup your /data partition , then make a factory reset and reboot .
If that doest work use RSD lite or Fastboot tools to flash stock ROM including stock recovery so you'll have to start from scratch.
Enviado desde mi Moto X mediante Tapatalk
lavero.burgos said:
Sounds like there is no system on the phone or maybe corrupted partition.
First try formatting,restoring /system partition (a trick to have a clean partition would be to format it to f2fs and then back to ext4), once done flash a ROM on top with TWRP. Backup your /data partition , then make a factory reset and reboot .
If that doest work use RSD lite or Fastboot tools to flash stock ROM including stock recovery so you'll have to start from scratch.
Enviado desde mi Moto X mediante Tapatalk
Click to expand...
Click to collapse
Am on ext4, but am able to use the device if only am able to boot to fastboot and select "Normal Reboot" then its able to boot to system.
Sent from my Moto X using Tapatalk
iykeDROID™ said:
Am on ext4, but am able to use the device if only am able to boot to fastboot and select "Normal Reboot" then its able to boot to system.
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
Then reflash recovery, probably that's what is causing it. Use fastboot to flash it.
Enviado desde mi Moto X mediante Tapatalk
lavero.burgos said:
Then reflash recovery, probably that's what is causing it. Use fastboot to flash it.
Enviado desde mi Moto X mediante Tapatalk
Click to expand...
Click to collapse
okay bro...
thanks and I will do that
Sent from my Moto X using Tapatalk
Does your pb fixed?
iykeDROID™ said:
okay bro...
thanks and I will do that
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
Thanks Very Much bro, it worked as you said I should should do......now I can boot, reboot, and do any sort of boot/reboot-related actions.....
Thanks, Nice.
Sent from my XT1053 using Tapatalk
iykeDROID™ said:
Thanks Very Much bro, it worked as you said I should should do......now I can boot, reboot, and do any sort of boot/reboot-related actions.....
Thanks, Nice.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
I have the exact same issue..but flashing the recovery again doesn't work :/ (already tried with Win, Ubuntu, Arch...)
Rahh1112 said:
I have the exact same issue..but flashing the recovery again doesn't work :/ (already tried with Win, Ubuntu, Arch...)
Click to expand...
Click to collapse
Flash official TWRP 2.8.7.0 , after you download the image check md5sum to make sure its not corrupted.
If that doesn't work reflash full stock ROM with RSD lite or via fastboot and start from scratch.
Enviado desde mi Moto X mediante Tapatalk