Database Develop

[Q] Moto X 2014 5.0.2 update broke my phone

Hello everybody,
I'm new, I hope someone can help me here ... I'm quite sure somewhere on these forums there must already be answers for my problem but I'm too dumb to find them.
I have the European? 2014 Moto X (not sure how to get the exact model now?!)
Unlocked bootloader, rooted.
Everything was fine, except today I got the 5.0.2 (?) OTA update ...
I didn't want to do it, but it kept asking. The moment I pressed "don't ask again" the phone rebooted
and now it's stuck at the white bootup screen (Motorola logo)
I somehow managed to get into the fastboot? mode once, by somehow pressing buttons at startup ... but, well
My two questions are:
1. Can I still backup my data, photos, textfiles, etc etc
2. How do I go back to a working system. (maybe without loosing my data)
Please tell me if it's possible, and how ... or please push me into the right directions.
But as I'm half panicking detailed instructions would be so fantastic.

Personally, how I would recover data, is boot to fastboot and flash TWRP again (since you indicated you were unlocked boot loader). In TWRP, plug in the device to a computer via USB and your files will be there. Then you can reflash the stock firmware and be good to go. If you are comfortable flashing the firmware through fastboot, you can choose to not wipe data and you should be all set.
It may be worth trying just clearing the cache and seeing if you can boot.
Sent from my Moto X 2015 Pure Edition using Tapatalk

xKroniK13x said:
Personally, how I would recover data, is boot to fastboot and flash TWRP again (since you indicated you were unlocked boot loader). In TWRP, plug in the device to a computer via USB and your files will be there. Then you can reflash the stock firmware and be good to go. If you are comfortable flashing the firmware through fastboot, you can choose to not wipe data and you should be all set.
It may be worth trying just clearing the cache and seeing if you can boot.
Click to expand...
Click to collapse
Hey! Thanks a lot!
I did fastboot boot twrp, and managed to backup my data on the internat storage! Yeah! Thanks!! <3
Now to part 2, I tried to wipe the cache partition in TWRP, but it doesn't help; when I reboot it still only shows the white logo..
Should I wipe other partitions aswell? (davikcache?)
If there's a way without loosing the phone setup, it would be great.
(Installed apps ... open tabs in firefox etc ...)
I also have a "online nandroid" backup, I think from back then, right after I rooted.
Would I restore the system.img from there?
Will this remove installed apps?
Or should I restore all partitions made by online nandroid backup?!
(I thought this would be better than... or how would I find the right stock firmware online for my device?)
Sorry for being such a beginner!!!!

psssss said:
Hey! Thanks a lot!
I did fastboot boot twrp, and managed to backup my data on the internat storage! Yeah! Thanks!! <3
Now to part 2, I tried to wipe the cache partition in TWRP, but it doesn't help; when I reboot it still only shows the white logo..
Should I wipe other partitions aswell? (davikcache?)
If there's a way without loosing the phone setup, it would be great.
(Installed apps ... open tabs in firefox etc ...)
I also have a "online nandroid" backup, I think from back then, right after I rooted.
Would I restore the system.img from there?
Will this remove installed apps?
Or should I restore all partitions made by online nandroid backup?!
(I thought this would be better than... or how would I find the right stock firmware online for my device?)
Sorry for being such a beginner!!!!
Click to expand...
Click to collapse
Lollipop actually doesn't use dalvik, so that won't help. If you have a nandroid, you of course can restore to that but it would likely lose your apps/settings. You can try restoring just the system, it sort of depends on what went wrong. In my experience being stuck not booting, I generally just reflash everything. Not the most convenient but it is the most effective.
Sent from my Moto X 2015 Pure Edition using Tapatalk

xKroniK13x said:
Lollipop actually doesn't use dalvik, so that won't help. If you have a nandroid, you of course can restore to that but it would likely lose your apps/settings. You can try restoring just the system, it sort of depends on what went wrong. In my experience being stuck not booting, I generally just reflash everything. Not the most convenient but it is the most effective.
Click to expand...
Click to collapse
Hey xKroniK13x,
thanks a lot for caring!
Of course, catastrophy happened:
I did fastboot boot twrp and tried to restore system from there, didn't work so I restored system _and boot from my nandroid backup there
guess this was very stupid because
Now my phone boots right into the fastboot mode, and I can't fastboot boot TWRP anymore,
it says "incomplete boot image for booting"
partition sizes wrong, etc etc ...
what I did now was flashing TWRP, at least this worked and I can boot it from the phone now.
So, please, one more time help (for a very stupid user ):
1. I guess keeping my apps and settings is out of discussion now, haha
But is there a way, with unlocked bootloader, TWRP installed to go back to stock?
2. Now ... given my phone is not completely broken, I just thought about installing CM?!
Would this be recommended? is it working fine?
I'm just thinking about it, because with Cyanogenmod I won't have problems like this in the future, right?
(OTA updates destroying my phone because of root....)
Whoa, I'm sorry for posting this here, but ... :angel:

psssss said:
Hey xKroniK13x,
thanks a lot for caring!
Of course, catastrophy happened:
I did fastboot boot twrp and tried to restore system from there, didn't work so I restored system _and boot from my nandroid backup there
guess this was very stupid because
Now my phone boots right into the fastboot mode, and I can't fastboot boot TWRP anymore,
it says "incomplete boot image for booting"
partition sizes wrong, etc etc ...
what I did now was flashing TWRP, at least this worked and I can boot it from the phone now.
So, please, one more time help (for a very stupid user ):
1. I guess keeping my apps and settings is out of discussion now, haha
But is there a way, with unlocked bootloader, TWRP installed to go back to stock?
2. Now ... given my phone is not completely broken, I just thought about installing CM?!
Would this be recommended? is it working fine?
I'm just thinking about it, because with Cyanogenmod I won't have problems like this in the future, right?
(OTA updates destroying my phone because of root....)
Whoa, I'm sorry for posting this here, but ... :angel:
Click to expand...
Click to collapse
If you've been contemplating installing a ROM, now would be a good time to do so. Just remember to wipe the data on the phone even though it doesn't boot. And CM OTA shouldn't cause issues like this, it just flashes the zip file in your recovery. Doesn't care about root or anything of course. Otherwise, if you'd like to do stock, just use MDM to get the firmware and flash away. Hope this helped!
Sent from my Moto X 2015 Pure Edition using Tapatalk

Hi !
I have exactly the same problem.
Can you tell us how you did to fix the bootloop ?
Thank you

benjo22 said:
Hi !
I have exactly the same problem.
Can you tell us how you did to fix the bootloop ?
Thank you
Click to expand...
Click to collapse
Try clearing your cache in a recovery/fastboot, or reflash the firmware! No guarantee the cache will fix it, but sometimes it will.
Sent from my Moto X 2015 Pure Edition using Tapatalk

Thank you for your help.
Clearing the cache doesn't work, so I'm searching for others ways...
Can you tell me how to flash the firmware with adb ?
Thanks
Edit : I have an European version

benjo22 said:
Thank you for your help.
Clearing the cache doesn't work, so I'm searching for others ways...
Can you tell me how to flash the firmware with adb ?
Thanks
Edit : I have an European version
Click to expand...
Click to collapse
That is answered in the FAQ thread... It is a guide for Moto G but it is applicable for this device too. http://forum.xda-developers.com/showthread.php?t=2876769
Sent from my Moto X 2015 Pure Edition using Tapatalk

@xKroniK13x
Hey, thanks for somehow guiding me through this :victory:
MDM didn't work, so I just went for the CM 12.1 nightly.
I also had concerns because in my attempts to clear cache etc etc I had "wrong partition size" etc etc
But CM installed without problems!
(Just one more question- there can't be any problems in the future because of messed up partitions, right? Does CM fix this by installing? Or should I stop caring, if it works, it works, right?!)
In fact, CM runs great, fantastic on my phone.
I lost some app data, and most annoyingly my SMS, but ...
Other than that, I'm really happy with CM :laugh:
@benjo22
Hey, I tried to fix it by clearing cache partitions from a fastboot TWRP (I don't know how you call it, I just booted TWRP without installing it)
This didn't work, so I tried to restore a nandroid backup,
but this made it even worse. (partition errors, only fastboot mode, etc etc)
Just booting with TWRP without installing also didn't work anymore,
so I put TWRP on the phone, which luckily worked, downloaded CM 12.1, installed it via TWRP,
never did it before, but I was lucky, it seems like it worked great!
Even kept my "SD CARD" data, but lost apps and some data ...
So I didn't fix the bootloop, but I hope I made it better, futureproof...

Glad you got up and running. CM shouldn't cause any future issues as far as partitions and such.
Sent from my Moto X 2015 Pure Edition using Tapatalk

Can't Boot Into System, Only TWRP

Here's the whole story:
I was on an unofficial build of RR CM13, encrypted, using TWRP 3.0.2-1.
I wiped data, dalvik, cache, and flashed the newest Official RR 7.1.1 and open-gapps.
I boot into the new ROM and start setting stuff up.
I restore some apps' data using Titanium Backup, then reboot.
On reboot I'm greeted with the device setup screen
I reboot, wipe, reflash a bunch of times
A few times:
When I rebooted after using the system my PIN doesn't decrypt the system/data (booting into the system)
When I rebooted after using TWRP my PIN does decrypt (booting into the system)
At some point during this I try wiping everything from TWRP, but it freezes, goes black, and then the notification LED turns white. I hold the power button and boot back to TWRP.
Apparently wiping /data is the problem (everything else wipes just fine if I do them individually)
I boot back into the system, set it up, and do a full factory reset from there (after offloading my stuff from Internal Storage)
Back to TWRP, now no matter what I flash or restore, I don't end up booting into the system, only into TWRP
I've also tried TWRP 3.0.4-0 (which wouldn't decrypt my data), and I've reflash TWRP a few times.
How do I actually boot into my system? It's been 7 hours, and I'm losing my mind.

Deleted

Boot to your ROM through the power button...
Manually..

Just Passing By said:
Not sure if you've tried this yet, but considering you've already backed your phone up, I'd just recommend to start clean and use the unbricker tool.
Click to expand...
Click to collapse
Do what he said. You've already wiped your internal storage, so just start from scratch.

Just Passing By said:
Not sure if you've tried this yet, but considering you've already backed your phone up, I'd just recommend to start clean and use the unbricker tool.
Click to expand...
Click to collapse
Thanks, that worked, but now when I try to boot into recovery I get a black screen.
I was able to use the Toolkit to boot into TWRP and flash my ROM. Any ideas how to fix this?

RustySpackleford said:
Thanks, that worked, but now when I try to boot into recovery I get a black screen.
I was able to use the Toolkit to boot into TWRP and flash my ROM. Any ideas how to fix this?
Click to expand...
Click to collapse
flash twrp
adb push os zip
adb push su
flash all , if needed format data.
This is what I have done yesterday,
edit: If u brick I don't take any responsibility.

Deleted

TWRP has enormous potential and so does ADB try to use them.
First ensure TWRP is working, If it works you're 80℅ safe , then further do some XDA search as per your need. I am sure it will work again.
This is purely my experience since 6 years I am flashing .

uttam.ace said:
TWRP has enormous potential and so does ADB try to use them.
First ensure TWRP is working, If it works you're 80℅ safe , then further do some XDA search as per your need. I am sure it will work again.
This is purely my experience since 6 years I am flashing .
Click to expand...
Click to collapse
hi bro, i facing 'white led black screen' on my 3T, can you explain what should i do for fix this?
please.. :crying:

bluuquthug said:
hi bro, i facing 'white led black screen' on my 3T, can you explain what should i do for fix this?
please.. :crying:
Click to expand...
Click to collapse
Hi ! Do not worry try this
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

uttam.ace said:
Hi ! Do not worry try this
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
it cant bro, i tried using that unbrick tool but still facing same problem after i update or flashing ROM again.
or can you explain step by step to fix that? almost all ROM i tried but still happening, am i wrong?

bluuquthug said:
it cant bro, i tried using that unbrick tool but still facing same problem after i update or flashing ROM again.
or can you explain step by step to fix that? almost all ROM i tried but still happening, am i wrong?
Click to expand...
Click to collapse
Your TWRP is working right!
go to TWRP/ Advanced/ADB Sideload
type "adb sideload /path/to/rom.zip"

Mate, recommend using ADB Sideload on TWRP itself is the only viable option you have. OR if that doesn't work and you still have the PIN issues, you should definitely use the Unbrick Tool and get everything back to Stock, and then reflash everything
Note: Using the unbrick tool will cause it to relock bootloader, so you're gonna have to start over again.
Cheers!

[Question] Unsuccessful Encryption

Hello, I've softbricked a fair amount of phones and tablets in my time but I must admit never had this show up. After flashing Twrp and a dm-verity thingy, I received this shiny new error on my new 1+3t. While I'm assuming it's a straightforward fix such as:
Booting into Twrp and flashing stock 4.x Oxygen os and the stock recovery to bring phone back to where I started.
My question is, can't I just go straight about flashing a rom? I.e freedom rom, or is it advisable to just try start again?
And is me flashing stock os then recovery got to work?
Everything is still stock there is no root. All I have done is:
Code:
fastboot > oemunlock > reboot > fastboot flash Twrp > Twrp boot > Twrp > swiped to Modify > flashed dm-verity.
I did receive a password request first time round but after I rebooted phone it wasn't there again.
Thank you for helping in advance.

Archtects said:
Hello, I've softbricked a fair amount of phones and tablets in my time but I must admit never had this show up. After flashing Twrp and a dm-verity thingy, I received this shiny new error on my new 1+3t. While I'm assuming it's a straightforward fix such as:
Booting into Twrp and flashing stock 4.x Oxygen os and the stock recovery to bring phone back to where I started.
My question is, can't I just go straight about flashing a rom? I.e freedom rom, or is it advisable to just try start again?
And is me flashing stock os then recovery got to work?
Everything is still stock there is no root. All I have done is:
Code:
fastboot > oemunlock > reboot > fastboot flash Twrp > Twrp boot > Twrp > swiped to Modify > flashed dm-verity.
I did receive a password request first time round but after I rebooted phone it wasn't there again.
Thank you for helping in advance.
Click to expand...
Click to collapse
You had to flash supersu or Magisk after the process to disable force encryption also make sure your are on the nougat supported twrp 3.0.4-1 or later
You can flash any rom if you have an unlocked bootloader and a working twrp
Sent from my Funk Tuned 3T

Funk Wizard said:
You had to flash supersu or Magisk after the process to disable force encryption also make sure your are on the nougat supported twrp 3.0.4-1 or later
You can flash any rom if you have an unlocked bootloader and a working twrp
Click to expand...
Click to collapse
thanks I think that's where I went wrong. I should have flashed Magisk. The guide says so but I only intended to flash a rom. Eh. I'll see if I can flash Magisk. All is not lost. I'll update once I get home. I'm annoyed with my self lol.
-101 xda points

Archtects said:
thanks I think that's where I went wrong. I should have flashed Magisk. The guide says so but I only intended to flash a rom. Eh. I'll see if I can flash Magisk. All is not lost. I'll update once I get home. I'm annoyed with my self lol.
-101 xda points
Click to expand...
Click to collapse
No prob buddy, let me know if you get stuck anywhere :fingers-crossed:
Sent from my OnePlus 3T using XDA Labs

Funk Wizard said:
No prob buddy, let me know if you get stuck anywhere :fingers-crossed:
Click to expand...
Click to collapse
I will do, hopefully it be fine. I'll try different thing if stuff doesn't work and I'll post back what I did incase anyone else has similar problem .

Twrp doesn't see any internal storage what so ever. So Ive flashed stock recovery from fastboot and going to attempt to sideload the stock OS. fingers-crossed

Funk Wizard said:
No prob buddy, let me know if you get stuck anywhere :fingers-crossed:
Click to expand...
Click to collapse
Thanks for your help im back to a working phone!
For anyone who get stuck!
1) download op3t stock recovery and the oxygen OS from oneplus website
2) boot into fastboot.
3) with your pc get up Adb and:
Code:
fastboot flash recovery stock.img
Fastboot boot stock.img
[\CODE]
4) Once you boot into recovery navigate to install from adb.
5) in cmd again on pc type
[CODE] adb sideload filename.zip
[\CODE]
6) then reboot :). You can leave it here if you want.

So I'm back on stock. With Magisk installed. Only dm-verity still come up which I'm not keen on. But I guess I can live with it. But I'm stuck with a bunch of system apps I can't get rid of? I've tried titanium backup, and link2sd my go to but nothing any ideas? Anyone now how to get rid?

Archtects said:
So I'm back on stock. With Magisk installed. Only dm-verity still come up which I'm not keen on. But I guess I can live with it. But I'm stuck with a bunch of system apps I can't get rid of? I've tried titanium backup, and link2sd my go to but nothing any ideas? Anyone now how to get rid?
Click to expand...
Click to collapse
I can recommend OOS Aroma Debloater Credits: @siankatabg :good:

Funk Wizard said:
I can recommend OOS Aroma Debloater Credits: @siankatabg :good:
Click to expand...
Click to collapse
Cheers I found the zip you. Mentioned after I posted the question, worked sort of lol. Some still won't go but it's got rid of a fair chunk an dive just frozen any I don't want.

Can't install any ROM in twrp, stuck in twrp menu. need help ASAP !

Hi guys, i wanted to change my rom, from pixel launchher from october to newest one, as always i downloaded it, and newest twrp for mi a2, I turned phone in fast boot mode, flashed img of twrp using adb, then I copied .zip of newest pixel launcher to phone and wiped system data and cache, then wanted to flash my .zip and I did...but during the 'flashing' it stuck on step 1/2 for about 5 minutes, then changed to step 2/2 for a minute and finally told me thats its done. but its not, when i wanted to reboot it told me that 'no os installed' wth? help me please
tried to repeat all steps, change twrp image to older one, tried to change rom to another (but every one rom i tried was android 10 - no going back to 9 i know), nothing worked.
Im in a big need of this phone getting to work
BIG BEER for someone who will help me

After you flashed the ROM zip in TWRP go to Reboot and from there change slot (if you're on A select B and if you're on B select A). After that, reboot to system, the warning about not having an OS installed is normal, don't worry.

Lurensu said:
After you flashed the ROM zip in TWRP go to Reboot and from there change slot (if you're on A select B and if you're on B select A). After that, reboot to system, the warning about not having an OS installed is normal, don't worry.
Click to expand...
Click to collapse
I've never got that 'no os installed' when i was flashing any custom OS, anyway, wiped everything once again, booted twrp using adb, flashed once again and totally ignored that message, as you said, and wow there is system even if twrp is saying that there is not. thank you bro.

glabarovski said:
I've never got that 'no os installed' when i was flashing any custom OS, anyway, wiped everything once again, booted twrp using adb, flashed once again and totally ignored that message, as you said, and wow there is system even if twrp is saying that there is not. thank you bro.
Click to expand...
Click to collapse
It always happened to me with this device, I don't know why. You're welcome, I'm glad you fixed it

guys please, i need a quick help
I cant find the zip file in twrp, i wiped the data, and its gone now
I need a quick help, please

Question PLEASE HELP Can't Flash EU rom to Mi 11 ultra without Bricking

I'm having a big problem. I've had to unbrick my Mi11 ultra 5 times with the miflash tool because every time I flash the custom rom through TWRP it complete then reboots with no OS. I copy the rom to the phone. Go in to TWRP and then I go to install and find the zip file. I choose it and it goes through the process but it still reboots into TWRP with no OS. I've tried it with and without root with Magisk. WHAT AM I DOING WRONG?! Please help. Here is the link for the ROM I'm trying to use https://androidfilehost.com/?fid=14943124697586336463

Format data after flashing the EU ROM.
The first time you load the system, the screen will stay a loooong time with the MIUI logo; don't panic and be patient.
Hope it works for you.
Regards.

Yes, as above. If you don't format data with the confirmation of yes in the twrp wipe menu, it will alway go back to twrp.
The reason is that when you change kernal branch, there may be partition differences between them. A format clears out old data crossing the new partition layout and allows boot.

portamento said:
Format data after flashing the EU ROM.
The first time you load the system, the screen will stay a loooong time with the MIUI logo; don't panic and be patient.
Hope it works for you.
Regards.
Click to expand...
Click to collapse
Buddy as best try to flash over Fastboot, then after that install TWRP and mount all partitions. Then klick wipe-- factory reset and wipe and after that format data with confirm yes. after that you need to install inject TWRP inject. You can find it in ADVANCED. After that klick fix Contexts. And reboot.
After that the OS will reinstall . Try it, that will work 100%

portamento said:
Format data after flashing the EU ROM.
The first time you load the system, the screen will stay a loooong time with the MIUI logo; don't panic and be patient.
Hope it works for you.
Regards.
Click to expand...
Click to collapse
Sathelp said:
Yes, as above. If you don't format data with the confirmation of yes in the twrp wipe menu, it will alway go back to twrp.
The reason is that when you change kernal branch, there may be partition differences between them. A format clears out old data crossing the new partition layout and allows boot.
Click to expand...
Click to collapse
THANK YOU BOTH!!! IT WAS CAUSE I DIDNT FORMAT DATA AFTER THE ROM INSTALL!! Thank you so much

Mag_e said:
THANK YOU BOTH!!! IT WAS CAUSE I DIDNT FORMAT DATA AFTER THE ROM INSTALL!! Thank you so much
Click to expand...
Click to collapse
Glad to know that it worked . I had the same problem when I changed from European stock ROM to Xiaomi.eu one. The tutorials I read didn't say anything about formatting data after installing the new ROM.

Mag_e said:
I'm having a big problem. I've had to unbrick my Mi11 ultra 5 times with the miflash tool because every time I flash the custom rom through TWRP it complete then reboots with no OS. I copy the rom to the phone. Go in to TWRP and then I go to install and find the zip file. I choose it and it goes through the process but it still reboots into TWRP with no OS. I've tried it with and without root with Magisk. WHAT AM I DOING WRONG?! Please help. Here is the link for the ROM I'm trying to use https://androidfilehost.com/?fid=14943124697586336463
Click to expand...
Click to collapse
Check this steps