Database Develop

Very Frustrated(not getting past bootanimation despite every try

I just got my motorola yesterday. I did quite a few things like unlocking it and rooting it..After my first initial root it worked fine but earlier today i decided to install lollipop. I was using the twrp version 2.7 to install the rom but i realised it wasnt working till i tried a few more time and it finally it. I tried back up my stock 4.4.4 room before i installed my new rom but it failed several times because i think the recovery was faulty to say the least. Anyways my lollipop worked very fine but i notice anytime i restarted the phone it took a long freaking time to restart but it was working normal as usual until i restarted my phone another time and realised i couldn't go past the bootanimation.It takes forever but i never get past it. I then decided to flash the twrp 2.8.0.1. After flashing i realised I could do a backup but it was too late. I tried a few tricks I've always used to get past the bootanimation like mounting the storage but it never shows up on my pc. I also tried side loading the rom using the adb sideload command but it never workedd.it always shows up saying "error: device not found" but when i go back to the bootloader and use the fastbootdevices command it shows up my device. IS there any recovery that will allow me to sucessfully mount my storage or sideload my rom without all this hussle?Even my the the bootloader unlock warning reboots several times before getting to the never ending bootanimation
rom:TitanPrimeROMv1.3-XT1068-69_RC1
XT1068
Rooted
TWRP 2.0.8.1
Window 8.1 64bit
I already have my mini sdk files

There's a number of guides in this subforum that goes through flashing the stock firmware for your phone. The reason you're getting bootloops is because there's currently no stable way to get root access on Lollipop for this phone, but it is being worked on.
ADB can be a bit finicky, so it'd probably be easier to have your ROM on the phone itself, whether in the data/media/ folder in Internal Storage, or on an SD card, since neither are wiped whenever you factory reset or clean your phone. TWRP 2.8.2.0 and above allows you to enable MTP mode so you can move your files straight onto or off your phone.

Actaully i managed to root my phone using chainfare's auto rode for the moto G.I just also installed twrp 2.8.0.3. Unfortunately,I dont have any rom on my phone which is bummer. Yh I do get to MTP enable my device in recovery but it never shows up on my pc.I have had issues like this before and I got it done in minutes without no problem..This is my first motorola device and I'm regretting my choice in buying this phone

sleekykenny said:
Actaully i managed to root my phone using chainfare's auto rode for the moto G.I just also installed twrp 2.8.0.3. Unfortunately,I dont have any rom on my phone which is bummer. Yh I do get to MTP enable my device in recovery but it never shows up on my pc.I have had issues like this before and I got it done in minutes without no problem..This is my first motorola device and I'm regretting my choice in buying this phone
Click to expand...
Click to collapse
Did you try manually selecting the driver is device manager?

http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 This thread is your best friend. The other thing is that you'll probably need to uninstall the drivers for your phone from Hardware Manager on your OS, unplug your phone, then plug it back in when you're in recovery, and your OS should pull the right drivers to get ADB working. Still, you've got fastboot so the best option for you at the moment is to just restore your phone to stock and go from there.
As I said, though, root doesn't work on Lollipop for our phone yet, and AFAIK we don't have the kernel sources yet for Chainfire (the developer of SuperSU amongst other things) to get root access working without causing bootloops.

Traediras said:
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 This thread is your best friend. The other thing is that you'll probably need to uninstall the drivers for your phone from Hardware Manager on your OS, unplug your phone, then plug it back in when you're in recovery, and your OS should pull the right drivers to get ADB working. Still, you've got fastboot so the best option for you at the moment is to just restore your phone to stock and go from there.
As I said, though, root doesn't work on Lollipop for our phone yet, and AFAIK we don't have the kernel sources yet for Chainfire (the developer of SuperSU amongst other things) to get root access working without causing bootloops.
Click to expand...
Click to collapse
I tried this thread but the problem is that the required mfastboot-v2 file link is not working for me.Anytime i try downloading it i get the message "Sorry, this file is infected with a virus,Only the owner is allowed to download infected files."

sleekykenny said:
I tried this thread but the problem is that the required mfastboot-v2 file link is not working for me.Anytime i try downloading it i get the message "Sorry, this file is infected with a virus,Only the owner is allowed to download infected files."
Click to expand...
Click to collapse
Huh.
http://forum.xda-developers.com/showpost.php?p=47820707 This contains just the mfastboot.exe file for each OS, it /should/ work since it's essentially the same file. Just put the files in that .zip into your folder with adb and fastboot in it, and you should be good to go.

Traediras said:
Huh.
http://forum.xda-developers.com/showpost.php?p=47820707 This contains just the mfastboot.exe file for each OS, it /should/ work since it's essentially the same file. Just put the files in that .zip into your folder with adb and fastboot in it, and you should be good to go.
Click to expand...
Click to collapse
Thanks Dude, After your last message I rechecked the mfastboot-v2 folder on the thread and realised the only new file in there was the mfastboot.exe file so i quickly googled it and saw another thread in which i found the file.I downloaded it and then executed all the commands. Goshh I finally saw my phone boot up in a long time which brought a huge smile to my face.
I would like Thank all of you guys who took the time out to visit this thread and give me suggestions. THANK YOU BROS
I really appreaciate it. Happy new year

Glad to hear everything worked out for you. Happy New Year to you too.

Duplicate thread created by OP
Original is here
Please do not create multiple threads again.
Thread closed

Nexus 6 - Can't boot TWRP recovery

I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.

briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.

simms22 said:
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
Click to expand...
Click to collapse
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.

briman0094 said:
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
Click to expand...
Click to collapse
important thing to forget to mention

So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?

simms22 said:
important thing to forget to mention
Click to expand...
Click to collapse
I guess I assumed that when I said "continues to boot normally" people would assume I could re-enable "OEM Unlock" if needed
scryan said:
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
Click to expand...
Click to collapse
All the console output indicates success, and it boots to the initial "TEAMWIN" logo for a few seconds and reboots.

No Recovery Similiar issue
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.

ray6279 said:
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
Click to expand...
Click to collapse
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .

briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it.
Click to expand...
Click to collapse
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.

nhizzat said:
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
Click to expand...
Click to collapse
A screenshot of an e-mail from a Google employee regarding Android Pay and SafetyNet.

50% JOY No Fastboot?
simms22 said:
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
Click to expand...
Click to collapse
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.

ray6279 said:
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
Click to expand...
Click to collapse
one question.. what is perm recovery?? the only recovery that works on the n6 is twrp recovery.
and when you are in her recovery, is it showing you the right location where the files should be? if nit, you csn change the lication.

Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.

ray6279 said:
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
Click to expand...
Click to collapse
your welcome, but you are still off in one bit of fact. you use fastboot, not adb, to flash a recovery(and system.img)
edit.. you can use apps like flashify to flash recovery, if you have root already.

So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.

ray6279 said:
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
Click to expand...
Click to collapse
ok, when wiping, dont do the first option wipe, itll wipe your whole phone clean. you need to select the advanced options and pick what you want wiped. fastboot is the way to unlock your bootloader, or flash a recovery. also, you use it to flash a system.img or any part of it.
adb is a general linux that can be used with android, anywhere but in the bootloader(only fastboot in the bootloader).
bootloader isnt the usb connection between the device and the pc, its part of the phone that boots it and decides if the rom is safe to run. thats why we unlock it. so we can flash roms eithout googles key.
fastboot is the tool that you use to do whatever needs to be fone in the bootloader, adb everywhere else.
a recovery you need if you want to flash custom roms, kernels, supersu, or other mods. you can also wipe different partitions with the recovery, or make a "nandroid' backup. thats a bavkup of everything. its like a complete snapshot of everything during the time you made it. if you ever mess up your phone, you can restore it, and you will be at the exact same place when you made the backup.
anything else?

I simply cannot flash recovery

I nearly bricked my Razr i XT when downgrading from a Kitkat update to JB 4.1.2 but thanks to the great work here I am making some progress but cannot get Recovery or Root. the unlocking of bootloader via the Motorola website went fine and thanks to this post
http://forum.xda-developers.com/showthread.php?t=2239706 I got the rom I wanted, and it's fine.
I have read many other tutorials on installing a recovery and have downloaded and tried 6 or 7 CWM and TWRP images
but it never completes - fastboot says it has, but the phone stubbornly hangs at the flashing.
I have no problems getting into fastboot, but failed many times, and in desperation have tried with USB debugging on and off
and with and without sim and sdcard inserted.
attached are some photos to show where I am stuck at, and I would greatly appreciate some help

carkev said:
I nearly bricked my Razr i XT when downgrading from a Kitkat update to JB 4.1.2 but thanks to the great work here I am making some progress but cannot get Recovery or Root. the unlocking of bootloader via the Motorola website went fine and thanks to this post
http://forum.xda-developers.com/showthread.php?t=2239706 I got the rom I wanted, and it's fine.
I have read many other tutorials on installing a recovery and have downloaded and tried 6 or 7 CWM and TWRP images
but it never completes - fastboot says it has, but the phone stubbornly hangs at the flashing.
I have no problems getting into fastboot, but failed many times, and in desperation have tried with USB debugging on and off
and with and without sim and sdcard inserted.
attached are some photos to show where I am stuck at, and I would greatly appreciate some help
Click to expand...
Click to collapse
U said fastboot hangs at flashing the recovery, but on the command lines on your PC it says finished. Have u tried booting into recovery?
What recovery did u use and where did u get it?
USB debugging, simcard and sdcard don't have anything to do with fastboot. But it is likely that u didn't know that

thanks for looking at this.
I did try booting into recovery from my PC by after rebooting it and then taking the recovery option, but the phone hung at the Motorola bootloader unlocked warning screen.
this link was typical of the various tutorials I used: http://androidteen.com/motorola-razr-i-how-to-root-and-install-clockworkmod-cwm-recovery-on-android-4-1-2-jelly-bean-firmware/
to be fair I cannot recall where I got all the recovery images from - I have that many, and had to rename them recovery.img, so cannot remember the original download names

update:
I have just tried an app from the google play named Root Android, which advised trying other apps - Kingroot, Framaroot & Towelroot,
but they all failed .
what did catch my eye yesterday was the yellow text when in fastboot that says 'dismatched partition entry'
I ignored it as the img files I was trying to flash are all much smaller than the 100mb stated,
but today I am beginning to think that perhaps my recovery partition is corrupt and look for ways to repair it.
does that make any sense?

carkev said:
update:
I have just tried an app from the google play named Root Android, which advised trying other apps - Kingroot, Framaroot & Towelroot,
but they all failed .
what did catch my eye yesterday was the yellow text when in fastboot that says 'dismatched partition entry'
I ignored it as the img files I was trying to flash are all much smaller than the 100mb stated,
but today I am beginning to think that perhaps my recovery partition is corrupt and look for ways to repair it.
does that make any sense?
Click to expand...
Click to collapse
That could be it. Try flashing a rsd lite package from JB. Than go to the recovery and see if u have stock back.

Hazou said:
That could be it. Try flashing a rsd lite package from JB. Than go to the recovery and see if u have stock back.
Click to expand...
Click to collapse
thanks HazouPH, I'll give that a go

I have solved my problem with CWM:victory:
whilst I am not 100% certain I am pretty much sure it was a driver problem - for those who this may benefit, here is what I did.
1. I did not reflash my phone, but stayed with the one in my original post.
2. remember that the main problem was that Fastboot said I had succeeded in flashing a Recovery image, but that the phone 'hung'
at flash as in my photo. and then from my phone I could not get to recovery from the fastboot menu .
3. I stumbled across a posting (on XDA, but I cannot remember where) that said the Motorola drivers were not as good as they should be and that the Motohelper one's would be fine - so I downloaded them, and have attached the zip below.
4. I then decided to tidy up my PC and uninstalled all mobile phone drivers, plus any redundant USB Device drivers
5 for the USB tidying up I tend to use USBdview, which is superb and can be found here
6 when all this was done I simply tried the reflash of CWM - and got the same situation I had been having all along
but amazingly, when I selected 'recovery' it went in CWM - I nearly fainted with surprise!
from all this I can only assume it was a driver problem as I had changed nothing else.
perhaps it was Motohelper drivers- perhaps it was USBdview that did it for me - I will never really know, nor care!
I now have CWM v6.0.1.9 - it is touchscreen and permanent, plus I use the cute Reboot by app by Petrus to control my phone.
happy days!

Softbrick achieved, need help

P8 Lite, I can boot into Fastboot&Rescue, normal boot gives a black screen after the Huawei logo. Recovery and force download from SD does not work.
I can boot into EMUI recovery by holding Vol Up in Fastboot, which gives me the options of Reboot, Shutdown and "Download new version and recovery" (which fails).
I tried the Unbrick steps from the Mega-Thread, and also flashed the Huawei P8 Lite version of TWRP to recovery - but it still only loads the EMUI Huawei eRecovery. Bootloader is unlocked.
Any ideas on what to do next before my girlfriend is going to kill me?

I tried everything in this thread:
http://forum.xda-developers.com/p8lite/general/hand-fixing-bootloop-t3464740
to no avail. One thing I noticed is that the link given in the Fastboot menu links to a Chinese (?) website - http://zh.ui.vmall.com/emotiondownload.php?mod=restore - I'm not sure if this is indicative of me having a device for the East Asian markets and if there are any software differences?

Sorry for the triple post - now I actually managed to boot into TWRP (the trick is disconnecting the USB cable before booting into recovery), I wiped everything, re-tried the flash all from the Mega thread, and it's still not working - Huawei logo is shown, then black screen/power off(?).

GfIsGonnaKillMe said:
Sorry for the triple post - now I actually managed to boot into TWRP (the trick is disconnecting the USB cable before booting into recovery), I wiped everything, re-tried the flash all from the Mega thread, and it's still not working - Huawei logo is shown, then black screen/power off(?).
Click to expand...
Click to collapse
Hi, when you power on your device to boot into EMUI, does it just show the red Huawei logo, or does it also show the boot animation (the same logo dancing and moving on the screen and then becomes static)?

XePeleato said:
Hi, when you power on your device to boot into EMUI, does it just show the red Huawei logo, or does it also show the boot animation (the same logo dancing and moving on the screen and then becomes static)?
Click to expand...
Click to collapse
Just the very static image, it doesn't even go into the animation.
Edit: this is a newly bought P8 Lite, the Box says Android 5.0, don't know if relevant?
by now I've wiped stuff with TWRP more times than I can count, and tried manually flashing the boot, recovery, cust and system of b132, b170, b190, and b564 to no avail

GfIsGonnaKillMe said:
Just the very static image, it doesn't even go into the animation.
Click to expand...
Click to collapse
Alright, so, since you can get into TWRP, inside TWRP go to Advanced > File manager and get this file: /sys/fs/pstore/console-ramoops and paste it to the internal storage or the sdcard, then via USB paste it to your computer and upload it somewhere, I'd like to check it.

XePeleato said:
Alright, so, since you can get into TWRP, inside TWRP go to Advanced > File manager and get this file: /sys/fs/pstore/console-ramoops and paste it to the internal storage or the sdcard, then via USB paste it to your computer and upload it somewhere, I'd like to check it.
Click to expand...
Click to collapse
http://pastebin.com/Hchyjqcz
I hope I did everything right! Currently flashed 132 boot, system and cust with TWRP in recovery

GfIsGonnaKillMe said:
http://pastebin.com/Hchyjqcz
I hope I did everything right! Currently flashed 132 boot, system and cust with TWRP in recovery
Click to expand...
Click to collapse
Yes, I found what I wanted, the kernel panics. What have you exactly done to the device? That would definitely help to know how to solve it.

XePeleato said:
Yes, I found what I wanted, the kernel panics. What have you exactly done to the device? That would definitely help to know how to solve it.
Click to expand...
Click to collapse
I wish I knew! I tried to root it the same way I rooted my other P8 Lite, which worked fine in the beginning (unlocking bootloader) and ****ed up somewhere between pushing SuperSU to the device and executing it. Then I tried to flash stockrecovery.img back, and suddenly the device was broken. Next thing I did was follow the guide in the Mega Thread (I think resetting to b052) which didn't help either. Then worked my way through the suggestion in the other thread. :silly:
edit: judging by my google history, the problems started when the recovery returned a segmentation fault instead of installing SuperSU as it would've been supposed to.

GfIsGonnaKillMe said:
I wish I knew! I tried to root it the same way I rooted my other P8 Lite, which worked fine in the beginning (unlocking bootloader) and ****ed up somewhere between pushing SuperSU to the device and executing it. Then I tried to flash stockrecovery.img back, and suddenly the device was broken. Next thing I did was follow the guide in the Mega Thread (I think resetting to b052) which didn't help either. Then worked my way through the suggestion in the other thread. :silly:
edit: judging by my google history, the problems started when the recovery returned a segmentation fault instead of installing SuperSU as it would've been supposed to.
Click to expand...
Click to collapse
[ 8.389146s][pid:1,cpu1,init]BUG: failure at /cloud/jenkinswh/ci/workspace/Alice_Channel_ANDROID/android_code/kernel/drivers/video/hisi/hi6220/balong_compose.c:613/vpu_on_notice_ade()!
This is suspicious, ADE is related to graphics, I don't really know how could that happen jsut by flashing a couple of things, but I'll look into it, I just need some time.

XePeleato said:
This is suspicious, ADE is related to graphics, I don't really know how could that happen jsut by flashing a couple of things, but I'll look into it, I just need some time.
Click to expand...
Click to collapse
It is very nice of you to look into this! Worst case scenario, the device was broken from the start and has now lost its warranty (though I booted it up once without problems right in the beginning).
For the main problem - which is my gf - I simply factory reset my own P8 Lite and put the stickers from the new one on it. Now I don't have a phone, but at least I get to keep my relationship
ninja edit: checking my terminal history, I remember trying to fix the not-installing SuperSU by trying fastboot -w and fastboot format cache as recommended elsewhere, but both failed
Playing around with it again, it seems the only fastboot commands working are fastboot flash and fastboot reboot, everything else is giving a "FAILED (remote: Command not allowed)" error, even for things like getvar
flashing b564 allows me to get into stock recovery, will try dload update now!!
EDIT: IT WORKS!!!
Things I learned from this:
- it is important to flash right update version
- use dload if you can boot into stock recovery
- recovery will only be loaded if not connected via USB, otherwise EMUI crap will launch
- vendors do not always have correct information on device package!!

GfIsGonnaKillMe said:
P8 Lite, I can boot into Fastboot&Rescue, normal boot gives a black screen after the Huawei logo. Recovery and force download from SD does not work.
I can boot into EMUI recovery by holding Vol Up in Fastboot, which gives me the options of Reboot, Shutdown and "Download new version and recovery" (which fails).
I tried the Unbrick steps from the Mega-Thread, and also flashed the Huawei P8 Lite version of TWRP to recovery - but it still only loads the EMUI Huawei eRecovery. Bootloader is unlocked.
Any ideas on what to do next before my girlfriend is going to kill me?
Click to expand...
Click to collapse
delete

For unbrick, its easy if your bootloader is unlocked.
Just need time and flash few files by adb (downgrade)and update your device's to the android version you want.
If you want I have all the necessary files.
After your device's is like at his first boot.
Sent from my SM-N9005 powered by QS-N9005-LP

Moto E5 play only boots to TWRP.

Hello! I just got a Moto E5 Play, my plan was to add TWRP/root and Magisk.
I followed the directions in the TWRP/Root thread but got to a point where the phone only boots into TWRP, never into the android OS.
What I did:
-unlocked the bootloader with code emailed to me
-fastbooted the no-verity.img
-ran the "adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor" (successfully) in the command window
-tried the "adb push fstab.qcom /vendor/etc/fstab.qcom" always gave me an error, I could never mount the '/vendor' partition, it was never visible in 'mount' option in TWRP.
Booting up after unlocking bootloader, it said 'bad key' when starting up and booted normally into Android. Then after installing TWRP, it says 'N/A' when booting up then loads TWRP.
Since then it only boots into TWRP. TWRP is fully functional, I thought I could continue on and flash Magisk beta from a mini SD (since android never loads) and it was successful. However it's useless because, I'm stuck in TWRP recovery. Trying to reboot into android recovery gives me the red triangle android and says 'no command', booting into System goes straight to TWRP. Booting into bootloader loads the AP Fastboot Flash Mode.
Any idea how I can get back into the Android OS? Thanks in advance.
This is my experimental phone and it's empty, so I can do whatever is needed.

foxcell said:
Hello! I just got a Moto E5 Play, my plan was to add TWRP/root and Magisk.
I followed the directions in the TWRP/Root thread but got to a point where the phone only boots into TWRP, never into the android OS.
What I did:
-unlocked the bootloader with code emailed to me
-fastbooted the no-verity.img
-ran the "adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor" (successfully) in the command window
-tried the "adb push fstab.qcom /vendor/etc/fstab.qcom" always gave me an error, I could never mount the '/vendor' partition, it was never visible in 'mount' option in TWRP.
Booting up after unlocking bootloader, it said 'bad key' when starting up and booted normally into Android. Then after installing TWRP, it says 'N/A' when booting up then loads TWRP.
Since then it only boots into TWRP. TWRP is fully functional, I thought I could continue on and flash Magisk beta from a mini SD (since android never loads) and it was successful. However it's useless because, I'm stuck in TWRP recovery. Trying to reboot into android recovery gives me the red triangle android and says 'no command', booting into System goes straight to TWRP. Booting into bootloader loads the AP Fastboot Flash Mode.
Any idea how I can get back into the Android OS? Thanks in advance.
This is my experimental phone and it's empty, so I can do whatever is needed.
Click to expand...
Click to collapse
Which Moto E5 Play do you have? There are several variants. Look for your model number in SETTINGS>>ABOUT PHONE and I should be able to help you out. As long as your device boots into TWRP normally, a fix shouldn't be difficult.
By the way, the "bad key" and "N/A" notofications are completely normal, and will occur even when your device does boot normally into the Android OS. However, there are custom boot logos you can flash to hide the screen.

MotoJunkie01 said:
Which Moto E5 Play do you have? There are several variants. Look for your model number in SETTINGS>>ABOUT PHONE and I should be able to help you out. As long as your device boots into TWRP normally, a fix shouldn't be difficult.
By the way, the "bad key" and "N/A" notofications are completely normal, and will occur even when your device does boot normally into the Android OS. However, there are custom boot logos you can flash to hide the screen.
Click to expand...
Click to collapse
Thank you for replying! In TWRP I don't see any 'About Phone' in Settings, it just has General (with check boxes), Time Zone, Screen, Vibration, and Language.
However, product/variant does appear when I boot into bootloader, it says: Product/Variant: james XT1921-5 16GB P3

foxcell said:
Thank you for replying! In TWRP I don't see any 'About Phone' in Settings, it just has General (with check boxes), Time Zone, Screen, Vibration, and Language.
However, product/variant does appear when I boot into bootloader, it says: Product/Variant: james XT1921-5 16GB P3
Click to expand...
Click to collapse
Yeah I wasn't even thinking -- with no way to boot up, you can't check settings. But, xt1921-5 is good news. That's the variant I own and support.
Ok, go to my thread here and download the stock ROM in the download link. Get the most recent one I have listed, which is the current stock ROM. Download it on a PC preferably. Connect your device and PC and copy the ROM over to your external SD card (external SD is necessary because /data needs to be formatted). In TWRP recovery mode you can transfer the ROM from PC to device. Once ROM is on external storage, follow the precise instructions in my thread. You'll be up and going before you know it.
https://forum.xda-developers.com/mo...tock-android-8-0-0-rom-moto-e5-t3806530/page2

MotoJunkie01 said:
Yeah I wasn't even thinking -- with no way to boot up, you can't check settings. But, xt1921-5 is good news. That's the variant I own and support.
Ok, go to my thread here and download the stock ROM in the download link. Get the most recent one I have listed, which is the current stock ROM. Download it on a PC preferably. Connect your device and PC and copy the ROM over to your external SD card (external SD is necessary because /data needs to be formatted). In TWRP recovery mode you can transfer the ROM from PC to device. Once ROM is on external storage, follow the precise instructions in my thread. You'll be up and going before you know it.
https://forum.xda-developers.com/mo...tock-android-8-0-0-rom-moto-e5-t3806530/page2
Click to expand...
Click to collapse
Thank you, I will try it and report back, if not today then tomorrow. Thanks again!

foxcell said:
Thank you, I will try it and report back, if not today then tomorrow. Thanks again!
Click to expand...
Click to collapse
Good luck. And just follow the instructions to the letter and it'll go smoothly.

Well I got some bad news... phone is stuck in a boot loop now, and no longer loads TWRP. I followed your directions and Oreo installed with no errors or warnings. Since going to Reboot -> System, it boots, says "N/A", then reboots.
I can get out of the boot loop by pressing volume down + power key, and from there I can access Android recovery (says 'bad key' when booting, instead of 'N/A') which gives me various options. It can still read SD cards and even says the proper OS.
I think it can still be saved since I can access Android recovery. I haven't tried the format system or cache options from Android recovery, because that might permanently screw it up.
Anyways... I'm here if you have any advice on what I can do. Maybe I should of bought an E4, lol.

Would you suggest I follow this?
https://forum.xda-developers.com/moto-e5/how-to/firmware-restoring-moto-e5-play-to-t3820053
I have no data on the phone so everything can be wiped no problem.

MotoJunkie01 said:
Good luck. And just follow the instructions to the letter and it'll go smoothly.
Click to expand...
Click to collapse
Would you suggest I follow this?
https://forum.xda-developers.com/mot...ay-to-t3820053
I have no data on the phone so everything can be wiped no problem.

foxcell said:
Would you suggest I follow this?
https://forum.xda-developers.com/mot...ay-to-t3820053
I have no data on the phone so everything can be wiped no problem.
Click to expand...
Click to collapse
Yes. Follow that guide to the letter. However, avoid flashing gpt.bin and bootloader.img. Otherwise, follow the instructions exactly. Please note that the "bad key" and/or "N/A" notifications you see during boot up are completely normal and have no real significance here. There are custom boot logos you can install to hide the notifications.

MotoJunkie01 said:
Yes. Follow that guide to the letter. However, avoid flashing gpt.bin and bootloader.img. Otherwise, follow the instructions exactly. Please note that the "bad key" and/or "N/A" notifications you see during boot up are completely normal and have no real significance here. There are custom boot logos you can install to hide the notifications.
Click to expand...
Click to collapse
I did as followed, and phone is restored!!! Now when starting up it says "bad key" so I assume that means bootloader is still unlocked?
I still want to root and such, but I think I'll wait because rooting instructions I found were vague and trying to follow them got me into the situation I was in, lol.
Thanks for your help!!

foxcell said:
Hello! I just got a Moto E5 Play, my plan was to add TWRP/root and Magisk.
I followed the directions in the TWRP/Root thread but got to a point where the phone only boots into TWRP, never into the android OS.
What I did:
-unlocked the bootloader with code emailed to me
-fastbooted the no-verity.img
-ran the "adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor" (successfully) in the command window
-tried the "adb push fstab.qcom /vendor/etc/fstab.qcom" always gave me an error, I could never mount the '/vendor' partition, it was never visible in 'mount' option in TWRP.
Booting up after unlocking bootloader, it said 'bad key' when starting up and booted normally into Android. Then after installing TWRP, it says 'N/A' when booting up then loads TWRP.
Since then it only boots into TWRP. TWRP is fully functional, I thought I could continue on and flash Magisk beta from a mini SD (since android never loads) and it was successful. However it's useless because, I'm stuck in TWRP recovery. Trying to reboot into android recovery gives me the red triangle android and says 'no command', booting into System goes straight to TWRP. Booting into bootloader loads the AP Fastboot Flash Mode.
Any idea how I can get back into the Android OS? Thanks in advance.
This is my experimental phone and it's empty, so I can do whatever is needed.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=77283595&postcount=196