I've spent the whole night trying to figure this out, but to no avail. Here goes...
Hey guys, so I was innocently playing around with GravityBox when I restarted my phone so some new settings would kick in, and it sends me into a bootloop. I went into TWRP Recovery, and at first factory reset my phone, hoping it would solve the problem, but it didn't, so I ended up "Formatting Data", which still didn't work. I'm kind of new to this whole flashing/rooting/ business, and I was wondering how I could fix my phone. If turned on, it stays in the booting process with the golden "Axon" letters forever. The model is the US variant, it's bootloader is unlocked via the ZTE Request Form, and it currently has TWRP as it's custom recovery. Help will be much appreciated. Also, it's on OTA B20
Edit: Alright so I've tried to flash to boot.img as well as recovery.img in twrp, but both give me an error. Strangely enough, if I wait out the Axon logo for about 5 minutes, it actually boots up, but as if it was the first time turning it on (asks you to sign in to google, wi-fi setup, fingerpring setup, etc). Another thing I noticed was that it says I only have 4gb of storage, instead of the 64 it originally came with. Every time I reset it/turn it off, it makes me set up the phone again.
Edit #2: Fixed with the help of this thread http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895 Only problem seems to be that Wi-Fi does not work. /:
I had this problem and after restoring system backup in TWRP I losted my signal WiFi Imei ....
But I have 64 GB of storage again
Отправлено с моего HTC One M8 через Tapatalk
raber111 said:
I had this problem and after restoring system backup in TWRP I losted my signal WiFi Imei ....
But I have 64 GB of storage again
Отправлено с моего HTC One M8 через Tapatalk
Click to expand...
Click to collapse
I don't have a TWRP backup to restore to ): if that's what you mean, any other solutions?
I didn't have to but I found a backup on XDA . And I don't really know if you should use it or you should wait till full stock image will release.
Отправлено с моего HTC One M8 через Tapatalk
Did you happen to try the instructions to restore to stock already, http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895
reddrago said:
Did you happen to try the instructions to restore to stock already, http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895
Click to expand...
Click to collapse
I'm in the process of doing this as of right now, thank you. Will update.
It sounds like you're going to restore to stock, so perhaps this won't help at this point, but Xposed has a "safe mode" which can be activated during boot-up and perhaps help to resolve these sorts of issues...here's a thread about it:
http://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336
This once saved me when I had a boot-loop issue with a tablet a while back. Good luck!
Same boat. last day or so of newegg 14 day return. At this point my decision is between Return or Replace. No ZTE image or flashable modem file means there is no fix for this, as far as I can tell.
FYI,. I have tried all of the possible fixes offered.
Barsky said:
Same boat. last day or so of newegg 14 day return. At this point my decision is between Return or Replace. No ZTE image or flashable modem file means there is no fix for this, as far as I can tell.
FYI,. I have tried all of the possible fixes offered.
Click to expand...
Click to collapse
Newegg is 30 day return.
Sent from my FRD-L04 using Tapatalk
flyer_andy said:
It sounds like you're going to restore to stock, so perhaps this won't help at this point, but Xposed has a "safe mode" which can be activated during boot-up and perhaps help to resolve these sorts of issues...here's a thread about it:
http://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336
This once saved me when I had a boot-loop issue with a tablet a while back. Good luck!
Click to expand...
Click to collapse
Actually, I managed to get it to boot up and work normal (for the most part). The only problem is, Wi-Fi doesn't work.
bricky23 said:
Newegg is 30 day return.
Sent from my FRD-L04 using Tapatalk
Click to expand...
Click to collapse
Try doing what this thread says, http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895
If you have any questions feel free to pm,
Pollito788 said:
Actually, I managed to get it to boot up and work normal (for the most part). The only problem is, Wi-Fi doesn't work.
Click to expand...
Click to collapse
I'm in the exact same boat. Did you ever figure out how to get wifi back?
Pollito788 said:
Try doing what this thread says, http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895
If you have any questions feel free to pm,
Click to expand...
Click to collapse
Am I missing something. that dev-host site sends me exploit installers. good thing I do nightly acronis images.
Pollito788 said:
Actually, I managed to get it to boot up and work normal (for the most part). The only problem is, Wi-Fi doesn't work.
Click to expand...
Click to collapse
Flapjack said:
I'm in the exact same boat. Did you ever figure out how to get wifi back?
Click to expand...
Click to collapse
WiFi not working is a mismatch between boot.img and /system, they have to be from the same 'set' so if you flash B20_Boot (BL unlock) boot.img, you have to flash a matching /system as well. We have a problem with numerous file version marked just B20 floating around. From what i know, this
http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53
is for sure the B20_Boot /system image , but i am unsure of anyone posting matching boot.img file. The one on idlekernel might be correct, since the dump came from B20_Boot BL unlocked phone, but it might have been modded. Maybe someone can post one
peramikic said:
WiFi not working is a mismatch between boot.img and /system, they have to be from the same 'set' so if you flash B20_Boot (BL unlock) boot.img, you have to flash a matching /system as well. We have a problem with numerous file version marked just B20 floating around. From what i know, this
http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53
is for sure the B20_Boot /system image , but i am unsure of anyone posting matching boot.img file. The one on idlekernel might be correct, since the dump came from B20_Boot BL unlocked phone, but it might have been modded. Maybe someone can post one
Click to expand...
Click to collapse
Uggg... I'm really frustrated now, because I got it working with tenfar's original modified boot image and rczrider's system backup. Everything was working. Of course, I didn't have root, so like and idiot, I tried to flash SuperSU 2.76. The phone stuck at the LTE screen after that. I tried re-following all my past steps, and can get the phone to boot, but it's acting crazy. I have two empty SIM icons on the taskbar (I had none when it was working fine) and the phone is very jerky and laggy. I cannot shut it down, or connect to PC easily. It will frequently reboot on its own, and I can't even power it down (it'll say "shutting down" for a few minutes, then reboot).
I eventually got it to shutdown, and repeated the "How to reset..." steps, but it's still acting crazy. I've wiped everything except for system. I'm going to try that next.
peramikic said:
WiFi not working is a mismatch between boot.img and /system, they have to be from the same 'set' so if you flash B20_Boot (BL unlock) boot.img, you have to flash a matching /system as well. We have a problem with numerous file version marked just B20 floating around. From what i know, this
http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53
is for sure the B20_Boot /system image , but i am unsure of anyone posting matching boot.img file. The one on idlekernel might be correct, since the dump came from B20_Boot BL unlocked phone, but it might have been modded. Maybe someone can post one
Click to expand...
Click to collapse
Would not mind fixing this rather than shipping my packed up axon7 to newegg. Think I have a few days before it has to ship, so I am open to working on it some more.
Thanks.
---------- Post added 08-29-2016 at 12:00 AM ---------- Previous post was 08-28-2016 at 11:51 PM ----------
Flapjack said:
Uggg... I'm really frustrated now, because I got it working with tenfar's original modified boot image and rczrider's system backup. Everything was working. Of course, I didn't have root, so like and idiot, I tried to flash SuperSU 2.76. The phone stuck at the LTE screen after that. I tried re-following all my past steps, and can get the phone to boot, but it's acting crazy. I have two empty SIM icons on the taskbar (I had none when it was working fine) and the phone is very jerky and laggy. I cannot shut it down, or connect to PC easily. It will frequently reboot on its own, and I can't even power it down (it'll say "shutting down" for a few minutes, then reboot).
I eventually got it to shutdown, and repeated the "How to reset..." steps, but it's still acting crazy. I've wiped everything except for system. I'm going to try that next.
Click to expand...
Click to collapse
Try flashing the 2.65 ver over it
peramikic said:
WiFi not working is a mismatch between boot.img and /system, they have to be from the same 'set' so if you flash B20_Boot (BL unlock) boot.img, you have to flash a matching /system as well. We have a problem with numerous file version marked just B20 floating around. From what i know, this
http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53
is for sure the B20_Boot /system image , but i am unsure of anyone posting matching boot.img file. The one on idlekernel might be correct, since the dump came from B20_Boot BL unlocked phone, but it might have been modded. Maybe someone can post one
Click to expand...
Click to collapse
It kinda late right now but if that is what's needed I'll be uploading my boot
Image tomorrow (b20_boot),
P. S. I know for sure CM13 is just around the corner and that alone is fix for slot of you guys boot problems .
Barsky said:
Try flashing the 2.65 ver over it
Click to expand...
Click to collapse
That's the thing.... I've restored it repeatedly. All traces of 2.67 should be gone. I've completely restored it three times now.
I'm honestly thinking I'm better off returning this phone while it's still working. I wonder if something is wrong with it.
DrakenFX said:
It kinda late right now but if that is what's needed I'll be uploading my boot
Image tomorrow (b20_boot),
P. S. I know for sure CM13 is just around the corner and that alone is fix for slot of you guys boot problems .
Click to expand...
Click to collapse
tysm bro <3
DrakenFX said:
It kinda late right now but if that is what's needed I'll be uploading my boot
Image tomorrow (b20_boot),
P. S. I know for sure CM13 is just around the corner and that alone is fix for slot of you guys boot problems .
Click to expand...
Click to collapse
Brings DrakenFX some coffee and nudges him awake. :cyclops:
Related
I have (attempted)root, and while I have root access when I boot up, I have to boot through fastboot. I tried the verity file published on a few threads, as well as RSD(for Linux, if that makes a difference) and I get no service. Twrp can't be reflashed due to the bootloader message in fastboot saying the boot IMG is corrupted. Anything helps at this point.
Running RR rom as of now, lineage was no different.
Thexmastermind said:
I have (attempted)root, and while I have root access when I boot up, I have to boot through fastboot. I tried the verity file published on a few threads, as well as RSD(for Linux, if that makes a difference) and I get no service. Twrp can't be reflashed due to the bootloader message in fastboot saying the boot IMG is corrupted. Anything helps at this point.
Running RR rom as of now, lineage was no different.
Click to expand...
Click to collapse
Your not going to get a signal with Boost or any other CDMA carrier with custom ROMs right now. They work for GSM models but need to be fixed for CDMA.
Sent from my Moto E (4) using XDA Labs
Right on I'll keep that in mind. Any clue about getting back to stock? I also wanna let everyone know that since I've got an extra device I'll be more than happy to help test.
Thexmastermind said:
Right on I'll keep that in mind. Any clue about getting back to stock? I also wanna let everyone know that since I've got an extra device I'll be more than happy to help test.
Click to expand...
Click to collapse
If you don't already have it, the Boost stock firmware is here: https://firmware.center/firmware/Motorola/Moto E4/Stock/
Download this one:
SPERRY_SPRINT_7.1.1_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
1.6 GiB
If you can't get RSDlite to recognize your device, you'll have to use adb/fastboot to flash the firmware manually piece by piece.
Sent from my Moto E (4) using XDA Labs
RSD recognized device fine, but when I flashed it, nothing changed.
Edit: I did try to use fastboot last night to flash the contained boot.img as well as the recovery.img no luck with those either. Would I need to erase files before flashing first?
Edit2: I very well may have downloaded an incorrect zip from the list last time. I'm going to get the one you mentioned and when I get home from family's house tonight I'll give it a go and holler.
Thexmastermind said:
RSD recognized device fine, but when I flashed it, nothing changed.
Edit: I did try to use fastboot last night to flash the contained boot.img as well as the recovery.img no luck with those either. Would I need to erase files before flashing first?
Edit2: I very well may have downloaded an incorrect zip from the list last time. I'm going to get the one you mentioned and when I get home from family's house tonight I'll give it a go and holler.
Click to expand...
Click to collapse
I'm not sure what your problem could be other than not having the correct firmware. I haven't used RSD with this device (maybe someone who has will chime in) because it wouldn't recognize it so I've just been flashing it with fastboot on Windows with a script to flash everything automatically, so it's just as easy. It's the only time I really ever use Windows. You shouldn't need to erase anything before flashing. I've never had to. Be careful using the erase command, I've seen users screw up partitions using it and ending up with a brick. I only use it erase modem st1 and st2 and to wipe data.
Sent from my Moto E (4) using XDA Labs
I only have Linux ATM. My machine had XP on it till it crashed setting up eclipse lol rsd communicates with the device fine, so I'm assuming it's the firmware. Like I said I'm at family's for the holiday, but I'll keep you posted when I get home.
Well I figured out what was wrong and now she boots up mostly fine. I get a black screen with a "bad key" message right before I get the blue Moto screen. Outside of that, all seems well. Please don't delete this thread just yet as I may have a few more questions after I connect to wifi at work tonight.
Thexmastermind said:
Well I figured out what was wrong and now she boots up mostly fine. I get a black screen with a "bad key" message right before I get the blue Moto screen. Outside of that, all seems well. Please don't delete this thread just yet as I may have a few more questions after I connect to wifi at work tonight.
Click to expand...
Click to collapse
Pretty sure no verity zip or magisk takes care of that (though you get n/a in the corner)
I'll try again tonight when I get back home.
Leave twrp as read only, then flash verity, then su. Is that correct?
Quick question: when I flash twrp, leave it as read only, correct? Then flash verity, then su?
Thexmastermind said:
I'll try again tonight when I get back home.
Leave twrp as read only, then flash verity, then su. Is that correct?
Click to expand...
Click to collapse
No, don't leave it read only.
So just so I have this right...
When prompted, I swipe to allow modifications to system, correct? Sorry if i seem dumb, I'd just rather be safe than sorry here.
Thexmastermind said:
So just so I have this right...
When prompted, I swipe to allow modifications to system, correct? Sorry if i seem dumb, I'd just rather be safe than sorry here.
Click to expand...
Click to collapse
Yes
Alright, so I got an error message about a bad key when I tried flashing twrp. I booted into twrp from fastboot via command line, flashed verity, flashed su "successfully" just waiting on partition details to be updated....
But it feels like it's been a good ten minutes of nothing happening. I ran the following from desktop:
adb shell whoami
Return was:
root
But I'm still waiting for it to update the partition details...
GOT IT! Thank you for your help. Time to debloat! Idk how to delete this thread.
Thexmastermind said:
GOT IT! Thank you for your help. Time to debloat! Idk how to delete this thread.
Click to expand...
Click to collapse
You don't delete it. Be careful debloating.
Yeah I noticed there were a handful of apps that don't want be uninstalled. I saw a thread about it so I'll probably do a little more research.
how recovery?
pretty much same deal... how did you recovery to work
I did a long, messy, and convoluted way of getting root. I messed up several times. Now I think I finally have root and a working phone. But, when I first turn on the phone, it gives me a screen warning me that it can't check for security loopholes, so i should relock my bootloader. That's normal.
But I also get another screen saying that my device is corrupted, and that my device may no longer properly work. Press power to continue. I press power, and it's able to either boot to the phone OS, or boot to TWRP, depending on what I was doing.
Question is, is my phone really corrupted during my messy install? Or is it also normal for all rooted and unlocked phones?
Thanks.
convolution said:
I did a long, messy, and convoluted way of getting root. I messed up several times. Now I think I finally have root and a working phone. But, when I first turn on the phone, it gives me a screen warning me that it can't check for security loopholes, so i should relock my bootloader. That's normal.
But I also get another screen saying that my device is corrupted, and that my device may no longer properly work. Press power to continue. I press power, and it's able to either boot to the phone OS, or boot to TWRP, depending on what I was doing.
Question is, is my phone really corrupted during my messy install? Or is it also normal for all rooted and unlocked phones?
Thanks.
Click to expand...
Click to collapse
I believe the corrupted message is standard for Android on all phones. I always ignored it. There are threads on how to get rid of that message. I never bothered with that.
Sent from my PH-1 using Tapatalk
---------- Post added at 03:43 PM ---------- Previous post was at 03:40 PM ----------
dogen18 said:
I believe the corrupted message is standard for Android on all phones. I always ignored it. There are threads on how to get rid of that message. I never bothered with that.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Oh, the message is normal when bootloader is unlocked. Furthermore, I have read that relocking bootloader can cause problems with Essential Phone, but I don't know why.
Sent from my PH-1 using Tapatalk
dogen18 said:
I believe the corrupted message is standard for Android on all phones. I always ignored it. There are threads on how to get rid of that message. I never bothered with that.
Sent from my PH-1 using Tapatalk
---------- Post added at 03:43 PM ---------- Previous post was at 03:40 PM ----------
Oh, the message is normal when bootloader is unlocked. Furthermore, I have read that relocking bootloader can cause problems with Essential Phone, but I don't know why.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
But the error message I get literally pauses the boot sequence until I press power to acknowledge it. That's normal?
Pretty annoying if it is...
convolution said:
But the error message I get literally pauses the boot sequence until I press power to acknowledge it. That's normal?
Pretty annoying if it is...
Click to expand...
Click to collapse
It has been awhile since I rooted any phone, but yes, pressing power to continue was what I remember. And, yes annoying, but not fatal !
Sent from my PH-1 using Tapatalk
It sounds like you might only have one good slot and the other corrupted. The bootloader message as you indicated is normal but the other message is not. I had this at one point as well because fastboot erased system but failed to flash it. Reflashing stock fixed it.
GryphKid44 said:
It sounds like you might only have one good slot and the other corrupted. The bootloader message as you indicated is normal but the other message is not. I had this at one point as well because fastboot erased system but failed to flash it. Reflashing stock fixed it.
Click to expand...
Click to collapse
How did you flash stock? I tried
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Flashing NMJ88C, and i downloaded it, extracted it, ran the BAT after I have both bootloader and critical unlocked, and now I can load the phone with NMJ88C, but like I said, I got that error. Isn't this method supposed to have fixed both slots?
If you didn't use this method, i was wondering what method you did?
I would think that would do the trick. In my case I knew the system was issue so I just flashed system. I find fastboot extra finicky on this phone. Did you happen to notice if something errored in the script?
convolution said:
How did you flash stock? I tried
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Flashing NMJ88C, and i downloaded it, extracted it, ran the BAT after I have both bootloader and critical unlocked, and now I can load the phone with NMJ88C, but like I said, I got that error. Isn't this method supposed to have fixed both slots?
If you didn't use this method, i was wondering what method you did?
Click to expand...
Click to collapse
http://mata.readthedocs.io/en/latest/
Sounds like you have the red verity message.
Read this guide down toward the bottom it explains it further and there is a fix.
Good Luck
wolfu11 said:
http://mata.readthedocs.io/en/latest/
Sounds like you have the red verity message.
Read this guide down toward the bottom it explains it further and there is a fix.
Good Luck
Click to expand...
Click to collapse
I do... but my wifi doesn't work as well, so I think I did something wrong.
convolution said:
I do... but my wifi doesn't work as well, so I think I did something wrong.
Click to expand...
Click to collapse
https://download.invisiblek.org/mata/boot.fix.red.img
install this via fastboot flash boot boot.fix.red.img
that should clear out your error after a reboot and fix your wifi.
if it doesn't simple go back to stock and start over.
wolfu11 said:
https://download.invisiblek.org/mata/boot.fix.red.img
install this via fastboot flash boot boot.fix.red.img
that should clear out your error after a reboot and fix your wifi.
if it doesn't simple go back to stock and start over.
Click to expand...
Click to collapse
Which stock should I choose? There are so many builds and versions? Do. I have to match my current one?
convolution said:
Which stock should I choose? There are so many builds and versions? Do. I have to match my current one?
Click to expand...
Click to collapse
yeah there are a lot lol I'm using OB 8.1 and it's solid flashed it from the back to stock section then rooted it via modified boot, super easy (no need for twrp)
I would choose the most current one. since it will have the latest security patches. but within a day or 2 we should be getting the March update in a new build.
wolfu11 said:
yeah there are a lot lol I'm using OB 8.1 and it's solid flashed it from the back to stock section then rooted it via modified boot, super easy (no need for twrp)
I would choose the most current one. since it will have the latest security patches. but within a day or 2 we should be getting the March update in a new build.
Click to expand...
Click to collapse
no need for twrp?
you follow this one?
convolution said:
no need for twrp?
you follow this one?
Click to expand...
Click to collapse
What I mean is if you are staying stock and just want magisk and root you don't need to do it via twrp. There are modified boot images you can fastboot flash. But if you want custom ROMs you still need twrp.
I have been satisfied with stock rooted.
wolfu11 said:
What I mean is if you are staying stock and just want magisk and root you don't need to do it via twrp. There are modified boot images you can fastboot flash. But if you want custom ROMs you still need twrp.
I have been satisfied with stock rooted.
Click to expand...
Click to collapse
I think I did it! I'm now running 8.1 + Magisk. But I kind of want to add TWRP so I can run a custom kernel...
convolution said:
I think I did it! I'm now running 8.1 + Magisk. But I kind of want to add TWRP so I can run a custom kernel...
Click to expand...
Click to collapse
You CAN'T add TWRP. It's installed as BOOT, so you need to install it every time you use it.
spotmark said:
You CAN'T add TWRP. It's installed as BOOT, so you need to install it every time you use it.
Click to expand...
Click to collapse
Ahhhh. I had a light bulb moment as to why I had difficulty... I installed twrp but didn't install the boot image after.
Strange how that works. I'm coming from an older school phone that doesn't do that slot system thing.
Any reason why this phone would have TWRP replace the boot image?
Or maybe you know of a thread that explains it?
Thanks.
delete
If it works, you should worry about that message at all.
convolution said:
Ahhhh. I had a light bulb moment as to why I had difficulty... I installed twrp but didn't install the boot image after.
Strange how that works. I'm coming from an older school phone that doesn't do that slot system thing.
Any reason why this phone would have TWRP replace the boot image?
Or maybe you know of a thread that explains it?
Thanks.
Click to expand...
Click to collapse
The slot thing is pretty new in general. This doc has some explanation for the architecture of our phones: http://mata.readthedocs.io/en/latest/
Once you get the hang of it, it's pretty simple to deal with.
BTW, awesome signature. PTL, SDG. :victory:
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
TheZadok42 said:
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
Click to expand...
Click to collapse
Kernel or firmware mismatch
Sent from my PH-1 using Tapatalk
Reflash it
TheZadok42 said:
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
Click to expand...
Click to collapse
Rooting a Beta Rom is usually a bad thing. My only suggestion is reflash following Essential's steps...
Wolfhawke said:
Rooting a Beta Rom is usually a bad thing. My only suggestion is reflash following Essential's steps...
Click to expand...
Click to collapse
Why? Root works fine with it, this has nothing to do with that.
crixley said:
Why? Root works fine with it, this has nothing to do with that.
Click to expand...
Click to collapse
Root works fine with what? A dev preview OS.
If someone is having issues then it must not be working ok.
jmill75 said:
Root works fine with what? A dev preview OS.
If someone is having issues then it must not be working ok.
Click to expand...
Click to collapse
Yes it works fine and the issue has nothing to do with root. Probably half of us using it are rooted without issue
Bit of a thread-dig here, but I just got a PH1 and went straight to P (not rooted yet) and saw no WiFi. Wouldn't even turn on.
The phone came with 7.1.1 and I flashed P via fastboot. Tried rebooting and monkeying with it, but never saw any progress, no list of networks, etc.
7.1.1 did see WiFi for the 5 minutes I ran it.
Flashed latest stable 8.1 and it WiFi worked again immediately.
Then flashed 9 a second time and now WiFi works fine.
My best guess is the 7.1.1->9 transition has some kind of issue (doesn't quite make sense to me, given that I think EVERYTHING is being flashed by the 9 update, but this did fix it).
tliebeck said:
Bit of a thread-dig here, but I just got a PH1 and went straight to P (not rooted yet) and saw no WiFi. Wouldn't even turn on.
The phone came with 7.1.1 and I flashed P via fastboot. Tried rebooting and monkeying with it, but never saw any progress, no list of networks, etc.
7.1.1 did see WiFi for the 5 minutes I ran it.
Flashed latest stable 8.1 and it WiFi worked again immediately.
Then flashed 9 a second time and now WiFi works fine.
My best guess is the 7.1.1->9 transition has some kind of issue (doesn't quite make sense to me, given that I think EVERYTHING is being flashed by the 9 update, but this did fix it).
Click to expand...
Click to collapse
Just got my Essential Phone today as well and did the exact same thing, flashed straight from 7.1.1 to P. I thought I was seriously going to have to send the phone back due to a broken Wi-Fi chip or something. You are seriously a lifesaver!
rignfool said:
Kernel or firmware mismatch
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Saundersmtt said:
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Click to expand...
Click to collapse
If I take your post at face value... You have a bad flash and need to try again... Or blame your cable... And go buy a new one...
Otherwise... You have a bad download... Or there is something wrong wrong with your zip or batch/script... Or you're not completely unlocked
Listen guys, the issue is bc the ota zip for p doesnt flash both slots and the fastboot images zip doesnt either. If u look at the script (flashall. Bat) with a text editor it specifically shows only flashing one slot. To fix the wifi issue, u need the july oreo images file and that flashall. Bat flashes both slots and will fix the lost wifi and or Bluetooth. Once u do that, it reboots twice and go back to dev options and renable usb debugging. Now u reboot bootloader and flash p. Now it should all work. Also, in doing this, you will have to lose your data.
Same here but can't roll back to Oreo
See.issue here but I seem.to not be able.to resolve wifi issue or roll back to Oreo. When I try to reflash it just says it expects a newer version of is. Any ideas?
1jason said:
See.issue here but I seem.to not be able.to resolve wifi issue or roll back to Oreo. When I try to reflash it just says it expects a newer version of is. Any ideas?
Click to expand...
Click to collapse
Yes flash the july oreo flashall. Bat
Saundersmtt said:
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Click to expand...
Click to collapse
I had the same problem. went back to stock on July's build (was on January's stock build previously) and reflashed P. Been smooth sailing ever since
jacksummers said:
Listen guys, the issue is bc the ota zip for p doesnt flash both slots and the fastboot images zip doesnt either. If u look at the script (flashall. Bat) with a text editor it specifically shows only flashing one slot. To fix the wifi issue, u need the july oreo images file and that flashall. Bat flashes both slots and will fix the lost wifi and or Bluetooth. Once u do that, it reboots twice and go back to dev options and renable usb debugging. Now u reboot bootloader and flash p. Now it should all work. Also, in doing this, you will have to lose your data.
Click to expand...
Click to collapse
The reason is because one of the OTAs did not have the partition you're looking for... And it created a mismatch somewhere...
You DO NOT need to have the same software on A and B... It just makes troubleshooting easier from our perspective... And... It forces you to reflash and probably fix the problem...
As intended... There should ALWAYS be a mismatch between A and B... At least a monthly security update... If not an Android versioning difference
Edited. We are all just trying to help others. Lets keep it that way.
so, uhmmm like yea...... there is this thread here, called the stock images thread (link for posterity https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 ) this is firmware images, directly from essential. I have added the remaining images that you dont get from essential, so that way you can reflash, and get the same version of software on both sides. there are wipe and no wipe bat files in there, twrp11 (the working twrp we have), and the fix red boot (in case you broke verity), and a stockboot.img (coincidentally the same file as called boot in the zip, but renamed for your twrp/rooting pleasure).
These images work great, many many many people have used them to go back and forth between O and P, OTA, or recover from catastrophe. As usual, beware of dragons, make SURE SURE SURE SURE you have a working adb/fastboot environment (use the version that comes with essentials drivers) (you can always do ADB VERSION or FASTBOOT --VERSION ) to check your version and where its working out of. It is 1 stop shopping. I also know the guy that makes the zips
jacksummers said:
Edited. We are all just trying to help others. Lets keep it that way.
Click to expand...
Click to collapse
Sorry if my post came off as harsh... I'll edit it... But this forum is literally littered with VAST amounts of guessing and misinformation...
rignfool said:
Sorry if my post came off as harsh... I'll edit it... But this forum is literally littered with VAST amounts of guessing and misinformation...
Click to expand...
Click to collapse
No prob, i understand the frustration.i assure you i was not guessing. I only post what i know is for sure. When faced with the exact same issue as OP i was forced to flash both slots to fix it. Yes, they could boot up with slightly different partitions, but the wifi was broken still. I believe the whole phone needed both slots flashed with each corresponding img simultaneously in order to resolve said issue. For whatever reason, i had both a and b screwed up. At the time i was trying to fix the ril and camera issues on the pixel 2 system image after flashing it on my essential. I want to get that working fully to release as a port.
jacksummers said:
No prob, i understand the frustration.i assure you i was not guessing. I only post what i know is for sure. When faced with the exact same issue as OP i was forced to flash both slots to fix it. Yes, they could boot up with slightly different partitions, but the wifi was broken still. I believe the whole phone needed both slots flashed with each corresponding img simultaneously in order to resolve said issue. For whatever reason, i had both a and b screwed up. At the time i was trying to fix the ril and camera issues on the pixel 2 system image after flashing it on my essential. I want to get that working fully to release as a port.
Click to expand...
Click to collapse
Wouldn't it be easier to attempt to port the 2 or 3 features we don't have as a separate systemui.apk or framework-res.apk?
And use Magisk?
Since we don't have that fancy hardware photo rendering thingymabob
So yeah, that's the title. Stupidly tried to force my US996 to take the Oreo update by flashing the stock recovery (while using a rooted system) and installing the OTA afterward (which results in an error). At this point I started screwing things up by flashing TWRP (using fastboot) immediately after that (without booting to the system again) and ended up in a loop as a result.
Screwed mine up even further later on by using a misc partition-wiping command (from here: https://forum.xda-developers.com/lg-g5/help/stuck-twrp-recovery-t3587077/post71796008#post71796008) and ended up locking the bootloader + making TWRP unusable. Now, only fastboot and download mode works, and I'm seriously out of idea at this point.
I guess there's not much that can be done, but any help would be appreciated.
Also I made a Reddit post about this before, if it helps: https://www.reddit.com/r/lgv20/comments/ac6apr/got_stuck_in_an_endless_twrp_bootloop_tried/
phamanhvu01 said:
So yeah, that's the title. Stupidly tried to force my US996 to take the Oreo update by flashing the stock recovery (while using a rooted system) and installing the OTA afterward (which results in an error). At this point I started screwing things up by flashing TWRP (using fastboot) immediately after that (without booting to the system again) and ended up in a loop as a result.
Screwed mine up even further later on by using a misc partition-wiping command (from here: https://forum.xda-developers.com/lg-g5/help/stuck-twrp-recovery-t3587077/post71796008#post71796008) and ended up locking the bootloader + making TWRP unusable. Now, only fastboot and download mode works, and I'm seriously out of idea at this point.
I guess there's not much that can be done, but any help would be appreciated.
Click to expand...
Click to collapse
Start over with lgup and the oreo.kdz
Theirs forum post on both of these here, search or look around
If you can get into download mode your phone is not bricked
Sent from my PH-1 using Tapatalk
clsA said:
Start over with lgup and the oreo.kdz
Theirs forum post on both of these here, search or look around
If you can get into download mode your phone is not bricked
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I've already tried that when I locked my bootloader accidentally, and just tried it once again - doesn't work. The phone still boots into the recovery, with the "no command" error like before. I suppose that the phone is still trying to initialize the OTA update process at this point.
If it helps, flashing using DL Partition didn't work either. Still more or less the same.
phamanhvu01 said:
I've already tried that when I locked my bootloader accidentally, and just tried it once again - doesn't work. The phone still boots into the recovery, with the "no command" error like before. I suppose that the phone is still trying to initialize the OTA update process at this point.
If it helps, flashing using DL Partition didn't work either. Still more or less the same.
Click to expand...
Click to collapse
I'm in exactly the same boat. Let me know if you figure anything out and I'll do the same. Really frustrating problem.
txenglan said:
I'm in exactly the same boat. Let me know if you figure anything out and I'll do the same. Really frustrating problem.
Click to expand...
Click to collapse
I have a potential solution for you. I'll PM you.
Have you guys tried to wipe data from recovery
Did this solution work? Can you share it?
txenglan said:
I have a potential solution for you. I'll PM you.
Click to expand...
Click to collapse
merrickville said:
Did this solution work? Can you share it?
Click to expand...
Click to collapse
Yes, what I did was religiously follow what was posted at:
https://www.reddit.com/r/lgv20/comments/8b0c44/quite_hard_bricked_what_can_i_do_now/
Try that and let me know what happens.
txenglan said:
Yes, what I did was religiously follow what was posted at:
https://www.reddit.com/r/lgv20/comments/8b0c44/quite_hard_bricked_what_can_i_do_now/
Try that and let me know what happens.
Click to expand...
Click to collapse
Already tried that. My issue is 'no command', I can boot into Download Mode, and I can flash H915, US996, they all flash if I choose the Partition DL.
No matter what I try, LGUP reports my phone as US996, even after successfully flashing H915.
I'm stuck at 'no command' (without a recovery cuz I tried to get to it) and US996 apparently.
merrickville said:
Already tried that. My issue is 'no command', I can boot into Download Mode, and I can flash H915, US996, they all flash if I choose the Partition DL.
No matter what I try, LGUP reports my phone as US996, even after successfully flashing H915.
I'm stuck at 'no command' (without a recovery cuz I tried to get to it) and US996 apparently.
Click to expand...
Click to collapse
Strange. For me, the only thing that solved the issue was to purposely flash the wrong KDZ. I don't recall which one it was exactly but that's definitely what the solution was. Flashing the right ones lead to what you are describing.
txenglan said:
Strange. For me, the only thing that solved the issue was to purposely flash the wrong KDZ. I don't recall which one it was exactly but that's definitely what the solution was. Flashing the right ones lead to what you are describing.
Click to expand...
Click to collapse
My Hardware the U.S. AT&T H910, so both the H915 & US996 are both the wrong KDZ's
Okay, I'm not relegating this to a paper weight just yet.
merrickville said:
My Hardware the U.S. AT&T H910, so both the H915 & US996 are both the wrong KDZ's
Okay, I'm not relegating this to a paper weight just yet.
Click to expand...
Click to collapse
Definitely don't throw it away just yet. I'm certain it can be salvaged. I even had to save mine using the test points and qfil at one point and I've been so close to throwing it away on so many occasions. It's basically impossible to brick these phones
I just went back and re-read that Reddit post by that guy. It's all coming back to me. I have the US996. His post was more inspiration if anything. I think what I did is download every single firmware I could find on lg-firmwares.com (both before and after the Oreo update) and went through them until I hit the "right" wrong one lol. It took me hours but I eventually got one that magically got the phone or of the bootloop so that I could tell move on to flashing something else.
I can't find it now, but I followed a post Reddit post like that, and I had to use a LGUP_Hxxxx.dll file, his instructions were for two others (which provided the DLL's for), so I stopped there, because of the missing DLL file that I can't find with a search>
My phone is stuck at US996 (even when I sucessfuly flash H915 back to it, LGUP still shows it as US99610f).
Do you think I can find a LGUP_US996.dll file anywhere? No. And this post looked promising for getting me out of the 'no command' fix I'm in.
Edit: Here is the what I tried, not Reddit, but here. But, no LGUP_US996.dll. LGUP_common.dll, no, that does not work either.
txenglan said:
Definitely don't throw it away just yet. I'm certain it can be salvaged. I even had to save mine using the test points and qfil at one point and I've been so close to throwing it away on so many occasions. It's basically impossible to brick these phones
I just went back and re-read that Reddit post by that guy. It's all coming back to me. I have the US996. His post was more inspiration if anything. I think what I did is download every single firmware I could find on lg-firmwares.com (both before and after the Oreo update) and went through them until I hit the "right" wrong one lol. It took me hours but I eventually got one that magically got the phone or of the bootloop so that I could tell move on to flashing something else.
Click to expand...
Click to collapse
txenglan said:
Definitely don't throw it away just yet. I'm certain it can be salvaged. I even had to save mine using the test points and qfil at one point and I've been so close to throwing it away on so many occasions. It's basically impossible to brick these phones
I just went back and re-read that Reddit post by that guy. It's all coming back to me. I have the US996. His post was more inspiration if anything. I think what I did is download every single firmware I could find on lg-firmwares.com (both before and after the Oreo update) and went through them until I hit the "right" wrong one lol. It took me hours but I eventually got one that magically got the phone or of the bootloop so that I could tell move on to flashing something else.
Click to expand...
Click to collapse
merrickville said:
I can't find it now, but I followed a post Reddit post like that, and I had to use a LGUP_Hxxxx.dll file, his instructions were for two others (which provided the DLL's for), so I stopped there, because of the missing DLL file that I can't find with a search>
My phone is stuck at US996 (even when I sucessfuly flash H915 back to it, LGUP still shows it as US99610f).
Do you think I can find a LGUP_US996.dll file anywhere? No. And this post looked promising for getting me out of the 'no command' fix I'm in.
Click to expand...
Click to collapse
A couple of things come to mind
First off their only one patched LGUP for the v20
it works for all versions but maybe the H918 or Sprint LS997 model.
Make sure you install it in C:\Program Files (x86)\LG Electronics\LGUP or it will either read the wrong model file (if you had a previous installation of LG UP), or it will not be able to find the model file at all.
Click to expand...
Click to collapse
After using the H915_10e.kdz you have to flash the Full H910 rom on the phone
https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
your choices are the rooted 10r rom or the unrooted 10q Stock rom
I also posted a back to stock Oreo 20G rom here > https://www.androidfilehost.com/?fid=1322778262903991071
Be sure and use TWRP for Oreo to flash it
After flashing those be sure and Format Data / Clear Cache and reboot
Damn....getting the right dll was also part of what I did IIRC. It's too bad it was such a long time ago else I'd have a more clear recollection of the exact steps I took. All I can say for sure, is that if you don't give up, you'll eventually stumble on the right solution.
Thank you for the suggestions.
This is the sequence I just did again as per your suggestion.
Install Patched LGUP (Phone recognized as US996 cuz I flashed that a while ago)
Flashed: H91510e_00_VTR_CA_OP_1205.kdz
Phone reboots to 'no command', injured reclining robot 'quick flashing'
At this point, both adb and fastboot do not see any devices.
End of story. I'm unable to sideload or flash the *.zip files, factory reset, wipe cache, all these options are not available to me due to 'no command' and no access to recovery, adb nor fastboot.
No matter which KDZ I flash, I only get 'no command', and I can always go into download mode.
Thanks again for the tips. I'm sure something will happen.
clsA said:
A couple of things come to mind
First off their only one patched LGUP for the v20
it works for all versions but maybe the H918 or Sprint LS997 model.
After using the H915_10e.kdz you have to flash the Full H910 rom on the phone
https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
your choices are the rooted 10r rom or the unrooted 10q Stock rom
I also posted a back to stock Oreo 20G rom here > https://www.androidfilehost.com/?fid=1322778262903991071
Be sure and use TWRP for Oreo to flash it
After flashing those be sure and Format Data / Clear Cache and reboot
Click to expand...
Click to collapse
merrickville said:
Thank you for the suggestions.
This is the sequence I just did again as per your suggestion.
Install Patched LGUP (Phone recognized as US996 cuz I flashed that a while ago)
Flashed: H91510e_00_VTR_CA_OP_1205.kdz
Phone reboots to 'no command', injured reclining robot 'quick flashing'
At this point, both adb and fastboot do not see any devices.
End of story. I'm unable to sideload or flash the *.zip files, factory reset, wipe cache, all these options are not available to me due to 'no command' and no access to recovery, adb nor fastboot.
No matter which KDZ I flash, I only get 'no command', and I can always go into download mode.
Thanks again for the tips. I'm sure something will happen.
Click to expand...
Click to collapse
I have never seen the screen or error you described. Having a total of 4 v20 I thought I had seen everything.. guess not
Sent from my ONEPLUS A6010 using Tapatalk
merrickville said:
Thank you for the suggestions.
This is the sequence I just did again as per your suggestion.
Install Patched LGUP (Phone recognized as US996 cuz I flashed that a while ago)
Flashed: H91510e_00_VTR_CA_OP_1205.kdz
Phone reboots to 'no command', injured reclining robot 'quick flashing'
At this point, both adb and fastboot do not see any devices.
End of story. I'm unable to sideload or flash the *.zip files, factory reset, wipe cache, all these options are not available to me due to 'no command' and no access to recovery, adb nor fastboot.
No matter which KDZ I flash, I only get 'no command', and I can always go into download mode.
Thanks again for the tips. I'm sure something will happen.
Click to expand...
Click to collapse
I wonder if this might work for you:
https://forum.xda-developers.com/v20/how-to/9008-test-t3855777/page13
It's an annoying process to have to go through but I revived mine when it was completely bricked (I couldn't even get as far as you because the phone wouldn't even turn on).
couple of thing that may help
No command screen is stock recovery being confused.
Try doing a factory reset using the volume - and power method (hold volume -, press power until the screen turns on, then tap power repeatedly until the menu appears)
When I downloaded the lasted OTA update for my OnePlus 8 Pro I thought it was just another hotfix and didn't realize it was a Big Deal Android 11 update. I tried using the normal OTA upgrade processed and kinda screwed myself.
After trying to install in the inactive slot the way I normally upgrade OTA, I ended up bootlooping. So I downloaded the recovery image and tried patching Magisk the long adb way. It wasn't until later that I realized I had to be on the beta channel. I didn't know you needed to disable modules when you upgrade to Android 11, so they might still be in play, but I don't know how to check. I've tried a bunch of stuff without much luck. Here's where I'm at now:
1) Bootloader is unlocked
2) I can get into Recovery Mode fine
3) I can flash the default/unpatched boot.img for my build and boot up fine, but there's no root, and wifi doesn't work and cellular data is really flakey (even though I normally have fine reception here).
4) From an unpatched boot.img I switched Magisk Manager to the beta channel and installed v21.1. Then I patched boot.img to make a new magisk_patched.img from the beta channel.
5) When I try to fastboot flash magisk_patched.img to slot A I bootloop.
6) When I try to fastboot boot magisk_patched.img I get stuck on the red dot with 2 white dots orbiting it for seemingly forever.
7) I think something is wrong in my slot B because I mostly just get stuck in fastboot. This might be an unrelated problem from a while back though.
8) When I try to run adb wait-for-device shell magisk --remove-modules, I just get an error message about magisk not being found.
What can I do to get back to a rooted working patched magisk without wiping all my data and starting from scratch?
I've honestly never seen anyone do this before so I'm curious as to how you'll recover from this
My thought are MSM but you may be able to boot. Problem is the magisk modules are still in play.
The adb command may not work for removal as you may not get that far.
Did the installation go through ok? It was just booting that failed?
Could maybe try to wipe system via recovery and go from there.
I'm not too sure buddy.
Keep us posted how u get on.
Edit: Try to boot the boot img.
What model are you on? BA ? I have the boot images in my guides in the guides section. Feel free to take what you need.
dladz said:
My thought are MSM but you may be able to boot. Problem is the magisk modules are still in play.
Click to expand...
Click to collapse
What is MSM?
dladz said:
Did the installation go through ok? It was just booting that failed?
Click to expand...
Click to collapse
You mean the result of fastboot flash magisk_patched.img? Yeah, that has finished fine every time. I'm either stuck bootlooping or booting up never finishes.
dladz said:
Could maybe try to wipe system via recovery and go from there.
Click to expand...
Click to collapse
Doesn't that delete all my data? I've only tried wiping the cache so far.
dladz said:
Edit: Try to boot the boot img.
Click to expand...
Click to collapse
Do you mean fastboot boot magisk_patched.img? That just spins forever and never finishes booting.
Flashing back to the unpatched boot.img boots up fine, but my wifi won't turn on and my cellular data is flakey (even though I usually have fine reception here).
dladz said:
What model are you on? BA ? I have the boot images in my guides in the guides section. Feel free to take what you need.
Click to expand...
Click to collapse
I have the US hardware, so I extracted the boot.img from 11.IN21AA, which was the same number that showed up after the OTA was applied.
I dunno, I tried a bunch of different stuff, ended up bricking it. Restored it with MSM to Android 11, then unlocked the bootloader, and tried to flash a fresh magisk_patched.img and it refused to boot in the same way, even though everything was completely fresh.
Are we sure the Magisk beta channel is working right now?
Ecna said:
I dunno, I tried a bunch of different stuff, ended up bricking it. Restored it with MSM to Android 11, then unlocked the bootloader, and tried to flash a fresh magisk_patched.img and it refused to boot in the same way, even though everything was completely fresh.
Are we sure the Magisk beta channel is working right now?
Click to expand...
Click to collapse
There hasn't been anyone stating issues.
Are you using lucky patcher?
dladz said:
There hasn't been anyone stating issues.
Are you using lucky patcher?
Click to expand...
Click to collapse
I don't know what lucky patcher is, so I guess not?
Turns out the wifi problem was happening on stock anyway. And EdXposed doesn't support 11 yet either. So I flashed back to 10.5.13 before bothering to set up all my apps. I'm gonna wait a bit longer for until 11 is more ripe.
Ecna said:
I don't know what lucky patcher is, so I guess not?
Turns out the wifi problem was happening on stock anyway. And EdXposed doesn't support 11 yet either. So I flashed back to 10.5.13 before bothering to set up all my apps. I'm gonna wait a bit longer for until 11 is more ripe.
Click to expand...
Click to collapse
Ah ok, that's fine if you don't know what lucky patcher is then that's a good thing
Yes, that patched boot image failed me. Can't boot. Can't find stock to flash. Bumbed.
dladz said:
Ah ok, that's fine if you don't know what lucky patcher is then that's a good thing
Click to expand...
Click to collapse
Hi dladz, can you please give me more info on lucky patcher and how it could affect things. I'm an avid lucky patcher user, and recently had issues with phone not booting, had to do a factory reset. (I wonder if lucky patcher was some how the culprit)
hbhorat said:
Hi dladz, can you please give me more info on lucky patcher and how it could affect things. I'm an avid lucky patcher user, and recently had issues with phone not booting, had to do a factory reset. (I wonder if lucky patcher was some how the culprit)
Click to expand...
Click to collapse
Don't know if you know this or not but you can't even discuss LP on XDA so I'm afraid I can't..
All I know is that it's dodgier than Donald trump's hair and should be avoided like an old woman's waffle.
If you've had problems and lucky patcher was installed that would be top of my list of culprits.
Bootloops, corruption, force closes to name but a few issues, it probably mines for coin using your phone's processor when it's not in use and god only knows what it does with your data, if that's the price of free apps? Id rather pay for them, my data is with more than any app.
Soz mate, that's all I can offer.
Just avoid it.. :good: