Related
Firstly, this device has never been rooted or had anything flashed to it. It is completely stock.
My step-daughter has been having issues with her Droid 4. About a month back or so, she started noticing that it wouldn't boot. It would flash the Motorola logo, and then the screen would just hang on the bootanimation. Eventually if we rebooted (power+vol down) enough times it would boot up.
Last night however, this happened again and it would not boot at all. I tried rebooting many times and it would never get past the bootanimation. After about 20 or so reboots I figured it was time for a Factory Reset. After the reset however, it wouldn't even display the bootanimation. It would still display the Motorola splash screen, but after that the screen would just go black with the display is still on. I Factory Reset several more times and nothing. Eventually after a number of times rebooting, it finally booted up. Well that was yesterday. Today she had to reboot it and it wouldn't boot again. Would just hang on a black screen.
I'm about ready to send it back since it's still under warranty, but figured I would check here to see if any of the amazing XDA guru's had experienced this and found a solution. I searched Google and this forum and didn't really see anything. Any help would be greatly appreciated!
jdiamond7 said:
Firstly, this device has never been rooted or had anything flashed to it. It is completely stock.
My step-daughter has been having issues with her Droid 4. About a month back or so, she started noticing that it wouldn't boot. It would flash the Motorola logo, and then the screen would just hang on the bootanimation. Eventually if we rebooted (power+vol down) enough times it would boot up.
Last night however, this happened again and it would not boot at all. I tried rebooting many times and it would never get past the bootanimation. After about 20 or so reboots I figured it was time for a Factory Reset. After the reset however, it wouldn't even display the bootanimation. It would still display the Motorola splash screen, but after that the screen would just go black with the display is still on. I Factory Reset several more times and nothing. Eventually after a number of times rebooting, it finally booted up. Well that was yesterday. Today she had to reboot it and it wouldn't boot again. Would just hang on a black screen.
I'm about ready to send it back since it's still under warranty, but figured I would check here to see if any of the amazing XDA guru's had experienced this and found a solution. I searched Google and this forum and didn't really see anything. Any help would be greatly appreciated!
Click to expand...
Click to collapse
Only other I can think to do would be to flash the fastboot files. A factory reset basically just wipes data while fastbooting it should reset the system itself to complete bone stock. You can do this using rsdlite or download a utility like jsnweitzel's ICS Only Utility in the Dev section.
Really sounds like a hardware issue to me since it's not rooted or anything but still might be worth a shot.
Sent from my Droid 4 - LiquidSmooth
kwyrt said:
Only other I can think to do would be to flash the fastboot files. A factory reset basically just wipes data while fastbooting it should reset the system itself to complete bone stock. You can do this using rsdlite or download a utility like jsnweitzel's ICS Only Utility in the Dev section.
Really sounds like a hardware issue to me since it's not rooted or anything but still might be worth a shot.
Click to expand...
Click to collapse
Thank you very much for the quick reply. I've downloaded jsnweitzel's ICS Only Utility and am charging up the phones battery so I can use it.
Just a quick question before I do this. I'm assuming that running the restore through ICS Only Utility is flashing a stock system image. That image is not rooted is it? Not that I would typically care, but if I do have to bring it back to Verizon I don't want them hassling me for rooting the device.
jdiamond7 said:
Thank you very much for the quick reply. I've downloaded jsnweitzel's ICS Only Utility and am charging up the phones battery so I can use it.
Just a quick question before I do this. I'm assuming that running the restore through ICS Only Utility is flashing a stock system image. That image is not rooted is it? Not that I would typically care, but if I do have to bring it back to Verizon I don't want them hassling me for rooting the device.
Click to expand...
Click to collapse
The image flashed in the fastboot process is completly stock, unrooted.
Sent from my Droid 4 - LiquidSmooth
Thanks for the help but that didn't do it. Guess I'll be taking it back to Verizon!
Sent from my SCH-I535 using xda app-developers app
First of all my Moto X is a stock nothing has been modified. My provider is Verizon running the latest version of android as far as I know.
The problem I'm facing is that my phone is stuck on the Motorola M and powered by android screen when you first start the phone. I first thought it was in an infinite boot loop because no matter what I did from the phone it would not get off that screen. I tried going into the boot options by holding the power button and the volume down screen this was successful, but selecting any of the options form the list would result in the phone returning to the screen with the Motorola symbol on it and powered by android. The battery is now all the way drained and will not charge it seems. The battery is at 0% screen appears sometimes plugged into the charger then the Motorola symbol screen with the powered by android screen will come on until the phone runs out of power. Mind you this is while the phone is connected to the charger via the wall outlet. Also sometimes the phone boots up normally but after 10-60 seconds the phone turns off and returns to the Motorola symbol screen with the powered by android at the bottom.
I have been trying all day to get it to do some things. I have successfully gotten in to boot in safe mode and it still powers off and returns to the Motorola screen with the powered by android. I have got it to boot in recovery mode and I wiped the cache. I have not done a hard reset yet because I cant get it to go past the Motorola screen with the powered by android at the bottom.
I said what the heck and tried to flash a new ROM onto the phone but the phone isn't detected on the computer by gda so I never did anything with flashing.
Any solutions would be much appreciated.
sirlancealot77 said:
First of all my Moto X is a stock nothing has been modified. My provider is Verizon running the latest version of android as far as I know.
The problem I'm facing is that my phone is stuck on the Motorola M and powered by android screen when you first start the phone. I first thought it was in an infinite boot loop because no matter what I did from the phone it would not get off that screen. I tried going into the boot options by holding the power button and the volume down screen this was successful, but selecting any of the options form the list would result in the phone returning to the screen with the Motorola symbol on it and powered by android. The battery is now all the way drained and will not charge it seems. The battery is at 0% screen appears sometimes plugged into the charger then the Motorola symbol screen with the powered by android screen will come on until the phone runs out of power. Mind you this is while the phone is connected to the charger via the wall outlet. Also sometimes the phone boots up normally but after 10-60 seconds the phone turns off and returns to the Motorola symbol screen with the powered by android at the bottom.
I have been trying all day to get it to do some things. I have successfully gotten in to boot in safe mode and it still powers off and returns to the Motorola screen with the powered by android. I have got it to boot in recovery mode and I wiped the cache. I have not done a hard reset yet because I cant get it to go past the Motorola screen with the powered by android at the bottom.
I said what the heck and tried to flash a new ROM onto the phone but the phone isn't detected on the computer by gda so I never did anything with flashing.
Any solutions would be much appreciated.
Click to expand...
Click to collapse
the stock logo/bootanimation does not say "powered by android", so if yours does, it is modified.
if it doesn't get past the boot logo, you will likely need to flash at least the system partition with fastboot or rsd lite. although, if your battery is very low, flashing will probably not work. here is a solution to allow flashing with a low battery:
http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm
if it does get past the boot logo, but boot loops on the animation, you probably just need to wipe data and cache in recovery (same as hard reset from the settings menu).
Not modified.
Q9Nap said:
the stock logo/bootanimation does not say "powered by android", so if yours does, it is modified.
if it doesn't get past the boot logo, you will likely need to flash at least the system partition with fastboot or rsd lite. although, if your battery is very low, flashing will probably not work. here is a solution to allow flashing with a low battery:
if it does get past the boot logo, but boot loops on the animation, you probably just need to wipe data and cache in recovery (same as hard reset from the settings menu).
Click to expand...
Click to collapse
I haven't done any modifications to the phone or had anyone do anything to it. Maybe this is the animation screen it is getting stuck on the big M and the powered by android at the bottom? Would you still suggest flashing the system partition?
Q9Nap said:
the stock logo/bootanimation does not say "powered by android", so if yours does, it is modified.
if it doesn't get past the boot logo, you will likely need to flash at least the system partition with fastboot or rsd lite. although, if your battery is very low, flashing will probably not work. here is a solution to allow flashing with a low battery:
http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm
if it does get past the boot logo, but boot loops on the animation, you probably just need to wipe data and cache in recovery (same as hard reset from the settings menu).
Click to expand...
Click to collapse
This in incorrect. Motorola recently updated their apps and in turn changed the boot logo and animation. it is all over the forums.
Cyphir said:
This in incorrect. Motorola recently updated their apps and in turn changed the boot logo and animation. it is all over the forums.
Click to expand...
Click to collapse
So any solutions?
Cyphir said:
This in incorrect. Motorola recently updated their apps and in turn changed the boot logo and animation. it is all over the forums.
Click to expand...
Click to collapse
ok, thanks for the correction.
i'm running heavily debloated stock with custom logo and animation, and don't spend a lot of time on the forums.
the information on how to recover from a brick is correct.
If you didn't modify anything at all....then its probably an app you loaded recently. Perhaps one NOT from the play store???
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
kj2112 said:
If you didn't modify anything at all....then its probably an app you loaded recently. Perhaps one NOT from the play store???
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
I booted in safe mode that doesn't run any applications except the necessary applications and it restarts about 10-60 seconds in. The time varies.
Can I buy that piece to act like a factory cable locally?
sirlancealot77 said:
I booted in safe mode that doesn't run any applications except the necessary applications and it restarts about 10-60 seconds in. The time varies.
Can I buy that piece to act like a factory cable locally?
Click to expand...
Click to collapse
I am facing the same problem you are facing? Did you find a solution? How did you boot into safe mode?
sirlancealot77 said:
I tried going into the boot options by holding the power button and the volume down screen this was successful, but selecting any of the options form the list would result in the phone returning to the screen with the Motorola symbol on it and powered by android.
Click to expand...
Click to collapse
Are you using volume up to select an option? This sounds like you are using power to select - power does not select it instead reboots your phone.
---------- Post added at 02:54 AM ---------- Previous post was at 02:52 AM ----------
sirlancealot77 said:
The problem I'm facing is that my phone is stuck on the Motorola M and powered by android screen when you first start the phone.
Click to expand...
Click to collapse
Download and install Motorola Device Manager on your computer. Then put your phone in bootloader mode, then plug it into your computer and start MDM. It should attempt to repair your phone.
JulesJam said:
Are you using volume up to select an option? This sounds like you are using power to select - power does not select it instead reboots your phone.
---------- Post added at 02:54 AM ---------- Previous post was at 02:52 AM ----------
Download and install Motorola Device Manager on your computer. Then put your phone in bootloader mode, then plug it into your computer and start MDM. It should attempt to repair your phone.
Click to expand...
Click to collapse
Question, since you have experience with MDM. Do you need to be fully stock to use MDM. For example if I have TWRP will it just write over my previous images or will it fail like a OTA would?
I agree getting the stock images right away would be nice. I have always received them from Moto within a day when requested but I do see the advantages of getting it right away for safe keepings. I always make sure to have a copy of my most recent images to return to stock. I have always used fastboot or Mfastboot since the gnex, I stay away from toolkits, but it sounds like MDM is Moto's version of their toolkit?
Travisdroidx2 said:
Question, since you have experience with MDM. Do you need to be fully stock to use MDM. For example if I have TWRP will it just write over my previous images or will it fail like a OTA would?
Click to expand...
Click to collapse
I believe it will fail.
---------- Post added at 06:26 PM ---------- Previous post was at 06:24 PM ----------
Travisdroidx2 said:
I agree getting the stock images right away would be nice. I have always received them from Moto within a day when requested
Click to expand...
Click to collapse
From what I am reading on the Motorola forums, Motorola has still not produced the 5.0 stock images, just kit kat.
---------- Post added at 06:31 PM ---------- Previous post was at 06:26 PM ----------
Travisdroidx2 said:
I stay away from toolkits, but it sounds like MDM is Moto's version of their toolkit?
Click to expand...
Click to collapse
I don't know what your definition of a tool kit is but MDM is a piece of software produced by Motorola that can run some sort of diagnostic on your phone and either update it to the latest version of the software or repair it if your system is damaged.
So i got a new lg g2 for verizon last week. ive had good experiences with cyanomod and other roms so i figured off the bat that i would install one of these. turns out they were alot more problems than it was worth. so i went back to stock rom and rooted. for some reason i took OTA. now phone is stuck in fastboot. so i went through this thread http://forum.xda-developers.com/showthread.php?t=2582142. so i got everything done and figured out (running live ubuntu so getting automount to stop was a challenge and then figuring out the new file paths). so now i reboot phone and try to get into twrp (from complete power off hold power button and volume down, release when logo shows and press again). so i get the "do you want factory reset" screen and i click yes, yes then it just goes into fast boot again. problem is now not even linux is reconizing the device. device doesnt go into twrp. cant get into download mode to reflash. all i got is "[16370]fastboot mode started [16420]udc_start() [16590]-reset- [1660]-portcharge- [16640] fastboot: processing commands.
do i have any hope? the phone is new from a third party so i dont think i have a chance to return to the seller, and im not sure if lg will take it either
added info
also, just read and possibly part of problem, twrp was 2.7.1.0, either way though im still stuck with it at this point
ok, so just a bit more info. now when the phone is plugged into windows 7 computer it automatically installed a driver "USB Movem Phone ADB port". so i figured id try to run adb devices and see if it showed, no luck. dont know if this puts me in a different situation or not...
Did you try via terminal $ reboot-bootloader you may be able to force into bootloader for adb sideload twrp 2.7.0.0
Sent from my VS980 4G using XDA Premium 4 mobile app
---------- Post added at 09:12 PM ---------- Previous post was at 09:03 PM ----------
Adb and fastboot are two different programs. If your in fastboot mode computer won't recognize adb devices. While in fastboot mode, reboot-bootloader then see if you can get adb through toggling vol + or -
Sent from my VS980 4G using XDA Premium 4 mobile app
actually i just got a step farther.... now i have twrp installed and working (turns out version 2.7.1.0 and 2.7.0.0 both didnt work with my phone even though i specifically got the versions for my phone. now im using 2.6.3.2 in case anyone else is having issues).
so twrp is on the phone. by random luck i apparently had all the rom zips left on the SD card. so i was able to flash a known working rom (at least it was working well enough to get by...). so i flashed the rom and rebooted the phone. unfortunatly it went straight back into twrp. i dont know if there is a flag i havent set or what. i thought i saw a walkthrough about what to do at this point, so im still working on it and i will update if i can fix it... but as i stated right now have twrp 2.6.3.2 working, still no download mode apparently(ill mess with this more because originally this is how i was flashing back to stock when things went wrong), and even though twrp installed a known working rom its still booting straight into twrp (without the whole power and volume down seqeunce...)
Some ROMs won't work on 2.6.3.2
Sent from my VS980 4G using XDA Premium 4 mobile app
would it automatically go to twrp if the rom didnt work? the reason im asking is because when i was messing around with the roms throughout the week some of them didnt work (either black screen at boot, or bootloop with logo). and i would have to manually shut the phone off, then go through factory reset, then it would turn on twrp. right now the phone just turns on and goes straight to twrp
If recovery doesn't detect a compatible ROM it bootloops. That or corrupt download itself, make sure to verify md5s whenever possible.
Sent from my VS980 4G using XDA Premium 4 mobile app
YAY, got it mostly back kinda sorta. so i followed this http://forum.xda-developers.com/showthread.php?t=2451696 after getting back into twrp. i dont know what this did or if it helped. then i flashed a new rom (which i also by chance had on the SD already) i believe it was malladus 1.2.9 and it worked (except i didnt put gapps or anything so it was having a fit about play... now its restarted and i have download mode back so ill just flash the whole thing with the regular rom (the rom on this website might even be older than the phone, but for me it worked well...). here is that website i case anyone needs it http://www.lg-phones.org/guide-to-flash-restore-unbirck-verizon-lg-g2.html i will reflash and post results, hopefully a bone stock phone to start over with...
glenn3451 said:
would it automatically go to twrp if the rom didnt work? the reason im asking is because when i was messing around with the roms throughout the week some of them didnt work (either black screen at boot, or bootloop with logo). and i would have to manually shut the phone off, then go through factory reset, then it would turn on twrp. right now the phone just turns on and goes straight to twrp
Click to expand...
Click to collapse
As far as a straight to recovery, I haven't had that problem on my g2. On my tablet,I run multi ROM recovery and it will go straight to recovery if a ROM is not installed. I would think it would do the same on vs980 twrp.
Sent from my VS980 4G using XDA Premium 4 mobile app
btw thankyou for suggesting a different rom, wouldve probably been stuck for awhile without that advice. so flashed verizon stock firmware(which also deletes everything) and its 100% running with the exception of the activation (switched back to old phone while working on getting this guy running again). i feel like ive learned alot more than i ever wanted so ill stay subscribed to this thread and if anyone has similar issues when you post hopefully ill be able to help alittle... no promises though
Hi i have a serious problem i am running cm-12-20150217-NIGHTLY-ghost.zip for the last five days. Now this is where my problems started yesterday i flashed a new boot animation after which the device refuses to boot . when switch on i just keep hearing a vibrating sound untill i hold down vol button and go into twrp recovery. I had made a nandroid backup of the functioning cm12 which i know works because i tested it once. But this time it wont work anymore. After restoring the backup i get the same problem vibrates then stops and the occasional flicker of light. i have no idea how to get back to stock i cannot find kitkat .4.4.4 stock for xt1053 anywhere and i think ive bricked the device anyway. I think i flashed the wrong boot animation which may have corrupted sys files.
Any help much very much appreciated im all ears.
sam0056 said:
Hi i have a serious problem i am running cm-12-20150217-NIGHTLY-ghost.zip for the last five days. Now this is where my problems started yesterday i flashed a new boot animation after which the device refuses to boot . when switch on i just keep hearing a vibrating sound untill i hold down vol button and go into twrp recovery. I had made a nandroid backup of the functioning cm12 which i know works because i tested it once. But this time it wont work anymore. After restoring the backup i get the same problem vibrates then stops and the occasional flicker of light. i have no idea how to get back to stock i cannot find kitkat .4.4.4 stock for xt1053 anywhere and i think ive bricked the device anyway. I think i flashed the wrong boot animation which may have corrupted sys files.
Any help much very much appreciated im all ears.
Click to expand...
Click to collapse
Wrong section, but I'll help. Next time use the Q&A...but okay. Flash the cm12 nightly after wiping and see if it'll boot. And if you got into recovery I'm pretty sure your not bricked.
Edit: if you can't get cm12 to boot without flashing cm11 first, then just flash cm11. If anything boots then it was just your setup.
Smash2Bash said:
Wrong section, but I'll help. Next time use the Q&A...but okay. Flash the cm12 nightly after wiping and see if it'll boot. And if you got into recovery I'm pretty sure your not bricked.
Edit: if you can't get cm12 to boot without flashing cm11 first, then just flash cm11. If anything boots then it was just your setup.
Click to expand...
Click to collapse
hello first of all my apologies for posting in the wrong section . I have just now erased everything cache,dalvic cache,internal storage basically everything and sideloaded cm11 which i know worked before and its been sitting their with the spinning logo for 25mins i guess i must still be doing something quite wrong.
sam0056 said:
hello first of all my apologies for posting in the wrong section . I have just now erased everything cache,dalvic cache,internal storage basically everything and sideloaded cm11 which i know worked before and its been sitting their with the spinning logo for 25mins i guess i must still be doing something quite wrong.
Click to expand...
Click to collapse
It's cool man, And you wiped data for sure? If you wiped data for sure, are you sure the cm11 has ghost in the file name? And can you tell me what was the boot animation zip you flashed.
Smash2Bash said:
It's cool man, And you wiped data for sure? If you wiped data for sure, are you sure the cm11 has ghost in the file name? And can you tell me what was the boot animation zip you flashed.
Click to expand...
Click to collapse
Ok perhaps we are getting somwhere now i had changed the file name before flashing to make it easier for me to type in i wasnt aware it would have any relevance. the boot animation i used was one from here in the moto x boot animations section and was about 26mb which i thought odd but i flashed it anyway like an idiot. What i dont understand is why my Nand flash didnt work after that. This is the animation i flashed.
sam0056 said:
Ok perhaps we are getting somwhere now i had changed the file name before flashing to make it easier for me to type in i wasnt aware it would have any relevance. the boot animation i used was one from here in the moto x boot animations section and was about 26mb which i thought odd but i flashed it anyway like an idiot. What i dont understand is why my Nand flash didnt work after that. This is the animation i flashed.
Click to expand...
Click to collapse
This is available in our forum which you should get it from but....sad part is this boot animation only works on stock I believe. I flashed last week before coming back to 5.0 did you also flash the logo?
Smash2Bash said:
This is available in our forum which you should get it from but....sad part is this boot animation only works on stock I believe. I flashed last week before coming back to 5.0 did you also flash the logo?
Click to expand...
Click to collapse
Yes i did now im in the shi% i have just flashed the correct cm12 nightly and same problem just keeps vibrating every 2 seconds and i have to force recovery. cant think what to do next.
I under you are in serious problem, we would like to help you ..please post this Q/A forum..
sam0056 said:
Yes i did now im in the shi% i have just flashed the correct cm12 nightly and same problem just keeps vibrating every 2 seconds and i have to force recovery. cant think what to do next.
Click to expand...
Click to collapse
Go ahead and post this in Q&A if this doesn't fix it please, flash this boot logo and animation from recovery and then reflash cm11 or twelve and see from there. http://www.mediafire.com/?mgv23moyuqwaoot it's the logo you wanted but for the X2013
Sent from my ghost
Smash2Bash said:
Go ahead and post this in Q&A if this doesn't fix it please, flash this boot logo and animation from recovery and then reflash cm11 or twelve and see from there. http://www.mediafire.com/?mgv23moyuqwaoot it's the logo you wanted but for the X2013
Sent from my ghost
Click to expand...
Click to collapse
Omg you just saved my A$$ man i have been working on this thing for nearly 10 hours. It was all to do with that boot animation i just flashed what you sent me and everything fired up your a lifesaver you should be so proud. Thanks again
sam0056 said:
Omg you just saved my A$$ man i have been working on this thing for nearly 10 hours. It was all to do with that boot animation i just flashed what you sent me and everything fired up your a lifesaver you should be so proud. Thanks again
Click to expand...
Click to collapse
No problem. Glad to help! [emoji3]
Sent from my ghost
Has anyone managed to get any Treble ROMs working? I tried the 3 from this post but they just cause a bootloop https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
Do yourself a favour and remove your password / pin / pattern as i've just flashed one via fastboot (no treble recovery)
And it didn't work, now i can't get back into TWRP.
Any ideas?
No new treble ROMs work with our P20 pro's.. its the same for me which is why I'm back on stock for now... As every new version of treble ROMs I have tried do not boot for me they just stick me in a boot loop as well, its the same for the new version of lineageos.. Not sure if it will ever be fixed in the future though on newer builds considering the whole Huawei locking bootloader permanently thing... will probably put developers off Huawei phones all together...
danielfrancisarthurs said:
No new treble ROMs work with our P20 pro's.. its the same for me which is why I'm back on stock for now... As every new version of treble ROMs I have tried do not boot for me they just stick me in a boot loop as well, its the same for the new version of lineageos.. Not sure if it will ever be fixed in the future though on newer builds considering the whole Huawei locking bootloader permanently thing... will probably put developers off Huawei phones all together...
Click to expand...
Click to collapse
How did you get back to Stock? I have no OS now at all lol, i'm in limbo
Erecovery I used.. when booting and you get the unlock boot screen it will tell you to hold volume up I think for 3 seconds to go to erecovery and then just download and restore stock firmware and recovery and let the phone do it's work!
danielfrancisarthurs said:
Erecovery I used.. when booting and you get the unlock boot screen it will tell you to hold volume up I think for 3 seconds to go to erecovery and then just download and restore stock firmware and recovery and let the phone do it's work!
Click to expand...
Click to collapse
Yea i used eRecovery a little earlier myself, we really need twrp which actually allows decryption or even twrp which allows treble
Either that or decrypt and use no verity, haven't bothered with all that yet.
After today though, jesus i'm thinking about it, i literally ended up with nothing, all my wifi networks in work need a second log in, something which eRecovery can't offer.
Completed it when i got home.
Have you managed to install any treble roms? Has anybody?
I don't think it's possible on my device in it's current state, i tried TWRP, Fastboot, several different roms on both and nothing.
Spotted this earlier, might actually work on our devices, what do you think?
https://forum.xda-developers.com/hu...rp-3-2-1-0-t3782866/post76668571#post76668571
It's a treble recovery from the p20 lite forum, similar device, might work, anyone fancy trying it
PS: If i flash this can i just flash my Unofficial TWRP from our forum should it not work? Or can damage be done?
I have no idea! I assume the issues are because of twrp or something in that area.. I have tried flashing system images via fastboot but for some reason I get errors trying it.. I'm not sure what the main issue is on why they don't boot but i would strongly suggest to not try flashing any twrp that's not specifically for our device as you could brick or even break your phone!
danielfrancisarthurs said:
I have no idea! I assume the issues are because of twrp or something in that area.. I have tried flashing system images via fastboot but for some reason I get errors trying it.. I'm not sure what the main issue is on why they don't boot but i would strongly suggest to not try flashing any twrp that's not specifically for our device as you could brick or even break your phone!
Click to expand...
Click to collapse
Apparently you don't need to use twrp at all, I've successfully flashed system images, via fastboot, but they've never booted which is horrible because there's just nothing else here.
In regards to flashing twrp, again apparently if it goes wrong then we can just flash the stock recovery, personally I think flashing another functional recovery would work too. But in all fairness the one in the p20 lite thread doesn't work any more than ours does in the pro thread.
Just hoping things move along.
Yeah I'd assume so.. I haven't been able to flash any image via fastboot but I'd assume it's the ROMs not the recovery.. anyway just heard that Huawei have released the Source code for the P20 so maybe it might be good news for the treble ROMs if they were to implement fixes for the boot loops!
danielfrancisarthurs said:
Yeah I'd assume so.. I haven't been able to flash any image via fastboot but I'd assume it's the ROMs not the recovery.. anyway just heard that Huawei have released the Source code for the P20 so maybe it might be good news for the treble ROMs if they were to implement fixes for the boot loops!
Click to expand...
Click to collapse
Sounds superb on any other flagship in the world, really hope this one picks up, it's a great device, never been happier with a stock ROM before, I think with all aosp lineage ROMs there's going to be huge issues fixing the cameras. Twos hard enough, 3 lol very hard.
Not trying to be negative just a bit worried is all
Can someone take a video of the boot loop
There's actually a method to how this phone loops. It could indicate the problem
Not sure about the camera but there's always ports into the future.. anything is possible! But could be a while till we are able to be booting any decent treble ROMs.. but then again as the source code has been released it may not be that long.. depends how quick the developers for treble react and whether or not they have a Huawei device to work with to fix our issues..
All we can do is hope!
---------- Post added at 11:12 PM ---------- Previous post was at 11:09 PM ----------
I will give it a try flashing a system image again tomorrow and take a video of it if I'm able to! But someone else needs to give it a try too just incase I don't get time please? The best way I can explain it is once the system.img is flashed in twrp I restart system as normal and it boots up normally with the Huawei logo when phone turns on then goes to bootloader unlocked screen and press different buttons for different options to boot from or wait until device boots normally so I wait for it to boot normally and soon as I get past the unlocked bootloader screen it just instantly reboots and just keeps rebooting doing that!
virtyx said:
Can someone take a video of the boot loop
There's actually a method to how this phone loops. It could indicate the problem
Click to expand...
Click to collapse
What signs are you looking for?
First time I tried it went from the press up for 3 seconds page then black, then vibrate then back to solid white Huawei, repeated 3 times until eRecovery asked to wipe.
For me after that point I flashed another and it went through to a lower case android sign, changing times from white to silver in a flow type effect, it stayed that way for around 10 minutes then back to eRecovery, flashing another treble ROM did the same thing.
Currently running: c782, 110, L09 p20 Pro, unofficial twrp and magisk.
The initial installation was via twrp, subsequent flashes wereb performed via fastboot.
Thats pretty much the same for me of what happens! Just boots then get a boot loop and black screen and back to the Huawei logo again from the start.. never able to actually boot a rom..
danielfrancisarthurs said:
Thats pretty much the same for me of what happens! Just boots then get a boot loop and black screen and back to the Huawei logo again from the start.. never able to actually boot a rom..
Click to expand...
Click to collapse
I thought the idea of treble was to match the Android version?
Seems as though it's trial and error with what's allowed.
Treble is still a work in development at the moment.. it doesn't help as well that Huawei are being assholes and making developers want to stay away from Huawei completely due to the whole locking bootloader thing but hopefully there are a couple of developers out there that keeps our devices in mind and hopefully means we will see a fix for our devices soon.. but when that is I have no idea..
danielfrancisarthurs said:
Treble is still a work in development at the moment.. it doesn't help as well that Huawei are being assholes and making developers want to stay away from Huawei completely due to the whole locking bootloader thing but hopefully there are a couple of developers out there that keeps our devices in mind and hopefully means we will see a fix for our devices soon.. but when that is I have no idea..
Click to expand...
Click to collapse
Aye it looks grim, that being said though, the stock ROM with a few tweaks is excellent, I've never once liked a stock ROM before on any device.
Root is easy, twrp is workable, bootloader was a breeze, we only have one actual ROM (LOS) but by all accounts even the p20 Pro camera works exactly the same on that, with that in mind what more do we need?
Course I'd like to be up to my neck in baked ROMs but if you're honest we truly only stick with one or two, as it turns out the two we have are pretty great.
Maybe I'm being optimistic
Just had a reply from another thread, quite interesting...
dladz said:
So in order...
Wipe
Flash ROM / IMG
Factory rest via twrp?
We're you referring to me by the way?
Click to expand...
Click to collapse
Yes, lol
the way i did it was with a stock recovery and system image
boot into erecovery and do a factory reset or a fastboot -w
boot back into the bootloader
flash the system image for the treble rom
then go into erecovery and do a factory reset
and then it should boot no problem at all
twrp cant wipe properly on treble roms
ive done the same on my p20 lite today, all stock and no issues booting at all
let me know how you get on
:good:
From this thread
https://forum.xda-developers.com/huawei-p20-lite/development/recovery-twrp-3-2-1-0-t3782866/page2
Hi, i have been occupied all day to get this to work, it just doesnt. i have followed the exact steps you layed out but when i try to factory reset after flashing the treble rom using fastboot it just gives me the error: "reset failed". I have tried using other GSI images but none work, had to restore my phone thrice because of this. I dont know what is the issue. These are the steps i followed:
1. Went completely stock ( no twrp or root )
2. Successfully factory reset my device.
3. Boot into fastboot and then flash a treble GSI.
4. as soon as the device turned on, went to the recovery to attempt a data wipe but at around 60% of the process completion the recovery gives the error with a red exclamation mark enclosed in the circle.
My device is a CLT-29 (C185). Was really looking forward to treble as my previous device was a Oneplus.
psycho.b94 said:
Hi, i have been occupied all day to get this to work, it just doesnt. i have followed the exact steps you layed out but when i try to factory reset after flashing the treble rom using fastboot it just gives me the error: "reset failed". I have tried using other GSI images but none work, had to restore my phone thrice because of this. I dont know what is the issue. These are the steps i followed:
1. Went completely stock ( no twrp or root )
2. Successfully factory reset my device.
3. Boot into fastboot and then flash a treble GSI.
4. as soon as the device turned on, went to the recovery to attempt a data wipe but at around 60% of the process completion the recovery gives the error with a red exclamation mark enclosed in the circle.
My device is a CLT-29 (C185). Was really looking forward to treble as my previous device was a Oneplus.
Click to expand...
Click to collapse
Ah the OnePlus , got the 5 still with me, great phone, great development.
Perhaps if your device was debrand? Could that be it?
Maybe it's just not meant to be