Hey,
I just wanted to inform you about an issue that happens in TWRP. I just bricked my Pixel by switching to slot B without flashing a bootloader in slot B. I think TWRP should inform the user that rebooting will brick the device. What are your thought on that? It could be done similar to how TWRP informs the user to install supersu if the phone isnt rooted.
This would be really helpful as it would prevent many people like myself from bricking their phones.
Now if I connect my pixel it only shows Qualcomm HS-USB Diagnostics 900E (COM3). No bootloader, fastboot, or recovery is present.
Here are a coupe of links of other people that did the same thing:
https://productforums.google.com/forum/#!topic/phone-by-google/sXjCoQ8glac
http://forum.xda-developers.com/pixel-xl/help/pixelxl-bricked-t3517310
Thanks!
Edit
I contacted the devolper of TWRP and he says that it should have boot loader regardless.
Here is the history: At work 3pm, froze Android system apk and some other telephone apps to troubleshoot something, I know I shouldn't do this. Resulted into boot loop. Go into twrp recovery and wipe data. It boots up fine and I see it downloading updates but it never goes through, I attempt to go back to recovery and apparently it's back to the stock recovery even though I originally had TWRP rc1.
I get home at 7 pm, I want to install TWRP rc1 so I send the command to boot into TWRP and then I install the zip, then I install sr5 SuperSU. I change to slot b and it's been bricked since.
It arrived November patch and it stayed like that since I was rooted. It attempted to install 7.1.1 but it returns installation problem. I think the bootloader was removed because of the failed update.
Your in download mode. I had this happen once on my Nexus 7. I held power for 90 seconds and it went back to bootloader. However I dont know about the pixel. Its still a new and uncharted device.
You also have to realize TWRP is in an unstable stage. You really should not flash anything until its in final release mode. I know I know... Hindsight is 20/20.
If you have insurance you could get it replaced.
Good luck.
sorry to hear dude..
bahehs said:
I think TWRP should inform the user that rebooting will brick the device. What are your thought on that?
Click to expand...
Click to collapse
I'm just curious. Have you ever donated any money to TWRP for the free developmental software they provide for free to the community to try/test with for free?
bahehs said:
I just bricked my Pixel by switching to slot B without flashing a bootloader in slot B.
Click to expand...
Click to collapse
Does anyone have an understanding about how something like this could potentially happen? Do these phones ship without information on the second slot? After my phone OTA updated, I switched slots without issue back to the previous version by following the information from Android Police. I'm not clear on what exactly would need to happen for the noted situation, and how someone could potentially get into a similar situation, unless the phone ships without information on the second slot. Switching slots worked without issue the times I tried it, but my phone had been through a typical OTA update before switching slots, so there was definitely information on both slots when I tried it.
Just an FYI: I am running Slot B on my device. Never tried Slot A. Just an FYI
Scott said:
Just an FYI: I am running Slot B on my device. Never tried Slot A. Just an FYI
Click to expand...
Click to collapse
Same, mine is on slot B. Dunno if it came that way, but it is only two days old. I let it take the OTA then flashed Francos kernel and then booted the root su image.
I really regret not watching more closely how all of impacted which slot it was on.
Sent from my Pixel XL using XDA Labs
Everytime you get OTA update you will switch slots. If you update via flashall it will say on the same slot.
This mode can't be a complete brick but it doesn't look like anyone has a solution yet. Maybe we will need some HTC tool?
Also when you root or modify you take responsibility for anything that happens. There is always a chance of a brick. At least Google will still probably warranty these devices.
Sent from my Pixel using Tapatalk
CZ Eddie said:
I'm just curious. Have you ever donated any money to TWRP for the free developmental software they provide for free to the community to try/test with for free?
Click to expand...
Click to collapse
This comment is unnecessary and serves no purpose in this thread.
Sent from my Pixel XL using XDA-Developers mobile app
I'm okay with that.
Updated op with more info
I installed TWRP while in the car riding with my girlfriend. I had some issues with the mobile radio showing no SIM card. Due to my limited options, I tried switching rom slots. It booted into the old software and said there was an update etc. I don't think switching rom slots leads to bricking if no other mods were done.
reb1995 said:
I installed TWRP while in the car riding with my girlfriend. I had some issues with the mobile radio showing no SIM card. Due to my limited options, I tried switching rom slots. It booted into the old software and said there was an update etc. I don't think switching rom slots leads to bricking if no other mods were done.
Click to expand...
Click to collapse
were you rooted because I had an ota in process wich failed while I was rooted which I think was the cause of the issue.
I kind of had the impression none of the stuff we're flashing is the bootloader itself. Isn't the bootloader the Android equivalent of Windows BIOS? Doesn't the bootloader load the boot image? Then the boot image mounts the system partition? So how could anything we're flashing cripple the bootloader?
Sent from my Pixel XL using Tapatalk
bahehs said:
were you rooted because I had an ota in process wich failed while I was rooted which I think was the cause of the issue.
Click to expand...
Click to collapse
Sorry for the long delay. No I was not rooted.
yearn2burn said:
I kind of had the impression none of the stuff we're flashing is the bootloader itself. Isn't the bootloader the Android equivalent of Windows BIOS? Doesn't the bootloader load the boot image? Then the boot image mounts the system partition? So how could anything we're flashing cripple the bootloader?
Click to expand...
Click to collapse
Bump
The problem is that the phone ships with an empty slot. If you try to boot it your permanently bricked do to having no bootloader on that slot. Once you take an OTA both slots have data and you're safe.
bahehs said:
were you rooted because I had an ota in process wich failed while I was rooted which I think was the cause of the issue.
Click to expand...
Click to collapse
You are right a failed OTA could brick a pixel phone
DR3W5K1 said:
The problem is that the phone ships with an empty slot. If you try to boot it your permanently bricked do to having no bootloader on that slot. Once you take an OTA both slots have data and you're safe.
You are right a failed OTA could brick a pixel phone
Click to expand...
Click to collapse
There is only one bootloader though so that's the confusing part. Still not sure how some people bricked completely. The bootloader is the first thing to load and tells the phone which slot to boot. Each slot does have its own boot, system, and vendor though. Been discussing this a lot on some other threads and there is still no answer has to what some of these people did internally that messed up their phones
aholeinthewor1d said:
There is only one bootloader though so that's the confusing part. Still not sure how some people bricked completely. The bootloader is the first thing to load and tells the phone which slot to boot. Each slot does have its own boot, system, and vendor though. Been discussing this a lot on some other threads and there is still no answer has to what some of these people did internally that messed up their phones
Click to expand...
Click to collapse
Failed bootloader flash? The Google .IMG files contain bootloader's.
EDIT I do believe the flash_all.sh flashes the bootloader
So you cant even run ADB commands ( a.k.a Bootloader / Recovery mode ), its a hard brick or soft ?
Does your PC detect the device when its on and connected via USB ?
Why did you switch slots in the first place ? if your taking an OTA on a rooted device with SU an OTA wont even apply via TWRP, you have to manually flash with the flash-all.bat script or part by part and the A / B boot slots are handles by the updates so you don't accidentally boot with a slot with no bootloader.
There is no need to swap A / B manually and if your going to flash and want to play with the A / B slots you should at least flash the partitions first but hindsight is a wonderful thing.
Aboot here might be your friend, but as this device is still quite new to many devs and or the tools might not be publicly available . . .
Related
So here's my story,
I bought this Zte phone off someone on craigslist a couple of weeks ago, and I've loved it every since. In fact, I have yet to turn it off, I've kept it on the entire time. Today the new update 29 came out for the US, and I tried downloading. To my dismay when the phone restarted I was greeted with a bootloader screen, and then a TWRP screen. I freaked out and panicked and emailed the guy I bought the phone from since I heard that unlocking bootloader on your phone voids the warranty. He told me he had done it in such a way OTA framework that it didn't void the warranty and also I can always relock the phone but be careful because I might brick it. I'm not a very tech savvy person and have no idea what to do to relock the phone so I can download this new update. Could someone please help me out and walk it out with me step by step so I know what to do. Thanks so much guys!
Look in the section rooms, recoveries,etc... look for one the says roms update stock DrakenFX
Since you are not tech savvy, you could just keep it unlocked and use those twrp flashable files to update B29.
http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
credit: @DrakenFX
However If you will wish to restore to locked state without twrp, I will be happy to guide you but you'll have many more steps to do.
Nik2424 said:
Since you are not tech savvy, you could just keep it unlocked and use those twrp flashable files to update B29.
http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
credit: @DrakenFX
However If you will wish to restore to locked state without twrp, I will be happy to guide you but you'll have many more steps to do.
Click to expand...
Click to collapse
I would much rather just restore to locked state without twrp so I don't have to worry about this situation again. I don't need bootloader or twrp and just wanna remove both. Would you please guide me through this?
ctran1996 said:
I would much rather just restore to locked state without twrp so I don't have to worry about this situation again. I don't need bootloader or twrp and just wanna remove both. Would you please guide me through this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/axon-7/how-to/b20-factory-image-posted-t3492552 click the link in this post. It will take you to the ZTE site with the official B20 firnware. You flash this in stock recovery and you will have a fully locked Axon 7.
tabletalker7 said:
http://forum.xda-developers.com/axon-7/how-to/b20-factory-image-posted-t3492552 click the link in this post. It will take you to the ZTE site with the official B20 firnware. You flash this in stock recovery and you will have a fully locked Axon 7.
Click to expand...
Click to collapse
How do I flash to stock recovery with teamwin keeps popping up and restarting and not allowing me to flash it?
ctran1996 said:
I would much rather just restore to locked state without twrp so I don't have to worry about this situation again. I don't need bootloader or twrp and just wanna remove both. Would you please guide me through this?
Click to expand...
Click to collapse
If you're not tech savvy, you probably don't want to do this. It's not simple and for whatever reason, some people (who would consider themselves more tech savvy) have had some issues.
Your best bet is to copy all of your data from internal memory (just in case), flash a new copy of TWRP (recovery only, you don't need to do boot) using tenfar's tool (http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204), then follow the steps in DrakenFX's thread to get B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
I'm happy to write you a guide for getting back to bone stock, but I'm not going to do it until next week when I have time at work and as I said earlier, some folks have had issues. For what it's worth, you likely won't hard brick the phone. So far, we've only seen soft bricks AFAIK.
rczrider said:
if you're not tech savvy, you probably don't want to do this. It's not simple and for whatever reason, some people (who would consider themselves more tech savvy) have had some issues.
Your best bet is to copy all of your data from internal memory (just in case), flash a new copy of TWRP (recovery only, you don't need to do boot) using tenfar's tool (http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204), then follow the steps in DrakenFX's thread to get B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
I'm happy to write you a guide for getting back to bone stock, but I'm not going to do it until next week when I have time at work and as I said earlier, some folks have had issues. For what it's worth, you likely won't hard brick the phone. So far, we've only seen soft bricks AFAIK.
Click to expand...
Click to collapse
Are they really hard to follow?? I mean my guides?
If I could I love to redo Tenfar tool guide ,but don't think he will allow me recreate that thread in a more clean way (guide wise)
ctran1996 said:
How do I flash to stock recovery with teamwin keeps popping up and restarting and not allowing me to flash it?
Click to expand...
Click to collapse
http://www.mediafire.com/file/1jw9b24glt5fd7t/recovery.img put this on your SD card
Boot to TWRP
Push Install (top left)
Push Install Image (bottom right)
find the recovery.img and push it - TWRP will install it for you.
Then reboot into recovery.
You will now be in stock recovery and can use it to install update from SD card and install the B20 firmware from ZTE
BE WARNED - THIS WILL FACTORY RESET YOUR PHONE WHEN YOU ARE DONE!!!!!
DrakenFX said:
Are they really hard to follow?? I mean my guides?
If I could I love to redo Tenfar tool guide ,but don't think he will allow me recreate that thread in a more clean way (guide wise)
Click to expand...
Click to collapse
Hah, no, your guides are not hard to follow. They're great
I think the bigger problem is that there are a lot of threads to wade through and there are various posts within in each thread that address specific issues users have run into. If someone who claims not to be "tech savvy" doesn't understand something in your thread (not because it's unclear but because they have zero experience with this and need some hand-holding) and then happens to read something else in the thread and tries that, it can get messy.
rczrider said:
Hah, no, your guides are not hard to follow. They're great
I think the bigger problem is that there are a lot of threads to wade through and there are various posts within in each thread that address specific issues users have run into. If someone who claims not to be "tech savvy" doesn't understand something in your thread (not because it's unclear but because they have zero experience with this and need some hand-holding) and then happens to read something else in the thread and tries that, it can get messy.
Click to expand...
Click to collapse
That is my problem entirely! I AM tech savvy as I have worked as a Microsoft/VMware Systems engineer for over 20 years and when I try to make heads or tails of doing some of the things necessary to flash a ROM, or root, or unlock the bootloader.... after my eyes glaze over I just stick with Nova Prime and hope the original manufacturers get everything worked out. What's really needed is a well written manual detailing step-by-step basics on what all these various things do as well as how to do them. Then more specific guides on a per phone basis. I know, it's asking too much! LOL :silly:
ctran1996 said:
So here's my story,
I bought this Zte phone off someone on craigslist a couple of weeks ago, and I've loved it every since. In fact, I have yet to turn it off, I've kept it on the entire time. Today the new update 29 came out for the US, and I tried downloading. To my dismay when the phone restarted I was greeted with a bootloader screen, and then a TWRP screen. I freaked out and panicked and emailed the guy I bought the phone from since I heard that unlocking bootloader on your phone voids the warranty. He told me he had done it in such a way OTA framework that it didn't void the warranty and also I can always relock the phone but be careful because I might brick it. I'm not a very tech savvy person and have no idea what to do to relock the phone so I can download this new update. Could someone please help me out and walk it out with me step by step so I know what to do. Thanks so much guys!
Click to expand...
Click to collapse
OK. Step by Step to get it back to B20
1) Move anything you want to save off your internal storage to your sd card or computer.
2) Download B20 image button.
3) Save file to SD card
4) Boot into Recovery by shutting it down and then push Volume Up Button+Power Button
5) When screen comes up boot into Recovery
6) in TWRP click Install, choose Select Storage, Choose Micro SDCard, Locate your update.zip file and click it
7) Swipe to confirm flash
WARNING: This will clean out your phone and turn it to B20. @DrakenFX can tell you how to not wipe the internal storage if you want to edit the update.zip file.
Hope this helps.
Thank you this is exactly what I was looking for. However, when I tried this the other day, it reset my phone as planned, but TWRP and bootloader were still on there. Any way of getting them off?
swehes said:
OK. Step by Step to get it back to B20
1) Move anything you want to save off your internal storage to your sd card or computer.
2) Download B20 image button.
3) Save file to SD card
4) Boot into Recovery by shutting it down and then push Volume Up Button+Power Button
5) When screen comes up boot into Recovery
6) in TWRP click Install, choose Select Storage, Choose Micro SDCard, Locate your update.zip file and click it
7) Swipe to confirm flash
WARNING: This will clean out your phone and turn it to B20. @DrakenFX can tell you how to not wipe the internal storage if you want to edit the update.zip file.
Hope this helps.
Click to expand...
Click to collapse
So I've seen slot of people discussing and people complaing about people discussing it in other OPs and figured I'd just make one here to openly discuss this massively confusing matter.
This a good start. I have tried dual slot boot, but end up losing the ability to access quick settings, developer options etc. also, switching from one slot to another is not convenient.
Hope in the near future, some one can make the dual slot boot be helpful
bush911 said:
This a good start. I have tried dual slot boot, but end up losing the ability to access quick settings, developer options etc.
Click to expand...
Click to collapse
Same here, how did you fix this bug ? I had to do a factory reset to fix it, because when I update the rom the bugs still here.
So I've a question: it is possible to use the 2 slots of Pixel to dualboot it or it's just a dream ? Stock rom on Slot A and Pure Nexus rom on Slot B for exemple
Edit : and what is the action who activate the "bug-mode"?
Finally, after wiped userdata, everything gets back.
by the way, some time I can switch between slots, some times I can't via twrp.
So, it's long way to go maybe.
billiepreks said:
Same here, how did you fix this bug ? I had to do a factory reset to fix it, because when I update the rom the bugs still here.
So I've a question: it is possible to use the 2 slots of Pixel to dualboot it or it's just a dream ? Stock rom on Slot A and Pure Nexus rom on Slot B for exemple
Edit : and what is the action who activate the "bug-mode"?
Click to expand...
Click to collapse
Just to be clear I have no knowledge other than what I've read on the many threads and and insatiable need for knowledge....I'm not a dev or themer or modder.
My Google factory Image flashing experience.
Active Slot
Radio
Bootloader
Vendor
Boot Image
System
Inactive Slot
System_other Image
I believe this based on command prompt output and the fact that after flashing custom rom and switching slots, I had the old (previous) bootloader
Radio
Vendor in the new slot.
I hear people having different command prompt outputs?
Running latest Android sdk 2.5.03
Golf c said:
My Google factory Image flashing experience.
Active Slot
Radio
Bootloader
Vendor
Boot Image
System
Inactive Slot
System_other Image
I believe this based on command prompt output and the fact that after flashing custom rom and switching slots, I had the old (previous) bootloader
Radio
Vendor in the new slot.
I hear people having different command prompt outputs?
Running latest Android sdk 2.5.03
Click to expand...
Click to collapse
I'm gona be starting completely over today. Don't have to but I'm more curious to figure some stuff out. So how do I go about flashing complete stock to both slots. Trying to make it like it was out of the box
aholeinthewor1d said:
I'm gona be starting completely over today. Don't have to but I'm more curious to figure some stuff out. So how do I go about flashing complete stock to both slots. Trying to make it like it was out of the box
Click to expand...
Click to collapse
Thats the question? I have no idea how it came out of the box. I can figure it out from my own flashing history though. One issue is OTA'S switch slots, factory images do not. So you would have to pay attention to your flashing history to know what's in your inactive slot.
I have never messed with what slot to flash to. I have been flashing it just like my nexus and have never had any problems.
jasonsamms666 said:
I have never messed with what slot to flash to. I have been flashing it just like my nexus and have never had any problems.
Click to expand...
Click to collapse
This phone is far from a Nexus. TWRP and Root are in the kernel now. Flashing is definitely different.
Are you taking OTA'S or keeping the same slot with factory images?
billiepreks said:
Same here, how did you fix this bug ? I had to do a factory reset to fix it, because when I update the rom the bugs still here.
So I've a question: it is possible to use the 2 slots of Pixel to dualboot it or it's just a dream ? Stock rom on Slot A and Pure Nexus rom on Slot B for exemple
Edit : and what is the action who activate the "bug-mode"?
Click to expand...
Click to collapse
I think in the coming weeks we should be getting more insight into our capabilities so hold tight grab a beer enjoy the ride this Cadillac phone will take us on
Golf c said:
This phone is far from a Nexus. TWRP and Root are in the kernel now. Flashing is definitely different.
Are you taking OTA'S or keeping the same slot with factory images?
Click to expand...
Click to collapse
I have not taken an ota.
jasonsamms666 said:
I have not taken an ota.
Click to expand...
Click to collapse
Me too. I think it's a little safer and easier. Depending on what your flashing, you probably have old
boot,
Bootloader,
Radio,
Vendor
in your inactive slot.
Which is easily fixed and would only come into play when switching slots on custom roms
Golf c said:
Me too. I think it's a little safer and easier. Depending on what your flashing, you probably have old
boot,
Bootloader,
Radio,
Vendor
in your inactive slot.
Which is easily fixed and would only come into play when switching slots on custom roms
Click to expand...
Click to collapse
I don't really understand how the slots work. As long as I don't tell fastboot to switch slots everything should be fine? I read that people are actually bricking these things.
Golf c said:
Thats the question? I have no idea how it came out of the box. I can figure it out from my own flashing history though. One issue is OTA'S switch slots, factory images do not. So you would have to pay attention to your flashing history to know what's in your inactive slot.
Click to expand...
Click to collapse
I know what's on each of my slots now. Slot A is NMF26U stock unrooted. Slot B is pure nexus rooted. That doesn't matter though I just wanna doublt check how to flash both slots back to factory. I think I have to flashall twice but I'm not sure
aholeinthewor1d said:
I know what's on each of my slots now. Slot A is NMF26U stock unrooted. Slot B is pure nexus rooted. That doesn't matter though I just wanna doublt check how to flash both slots back to factory. I think I have to flashall twice but I'm not sure
Click to expand...
Click to collapse
I don't think flash all twice will work because of that System_other Image? It will make all the partitions the same though, except for the system. We have to figure out the edit or command to flash twice and switch slots.
I flash all'd both by switching the active slots. What ever slot was inactive after doing this would bootloop. Tried several times. No idea what is going on, I know there are several peeps that have dual boot working.
And yes, I think the system_other might be part of it. But just guessing.
TonikJDK said:
I flash all'd both by switching the active slots. What ever slot was inactive after doing this would bootloop. Tried several times. No idea what is going on, I know there are several peeps that have dual boot working.
And yes, I think the system_other might be part of it. But just guessing.
Click to expand...
Click to collapse
I believe there is a fastboot command for switching active slots. I don't know it yet. I noticed when you throw an error in fastboot, a list of commands comes up. We have to take a look at that. I seen the - w command in there.
---------- Post added at 03:31 PM ---------- Previous post was at 03:26 PM ----------
Here is some of the commands, certainly not all of them.
https://forum.xda-developers.com/pixel-xl/how-to/pixel-xl-fastboot-commands-t3490080/post69366928
Golf c said:
I believe there is a fastboot command for switching active slots. I don't know it yet. I noticed when you throw an error in fastboot, a list of commands comes up. We have to take a look at that. I seen the - w command in there.
Click to expand...
Click to collapse
Yes, I am using it. Fastboot set_active a
Let me reexplain what I tried.
Slot a active ran flashall.
Slot a boots fine. Then next I switched slots with
Fastboot set_active b
Flashall
B boots fine
Then made a active again.
A now bootloops.
Here is a link to the commands for fast boot.
https://forum.xda-developers.com/pixel-xl/how-to/pixel-xl-fastboot-commands-t3490080/page1
TonikJDK said:
Yes, I am using it. Fastboot set_active a
Let me reexplain what I tried.
Slot a active ran flashall.
Slot a boots fine. Then next I switched slots with
Fastboot set_active b
Flashall
B boots fine
Then made a active again.
A now bootloops.
Here is a link to the commands for fast boot.
https://forum.xda-developers.com/pixel-xl/how-to/pixel-xl-fastboot-commands-t3490080/page1
Click to expand...
Click to collapse
Out of thanks for the day. Thank you. Your example is interesting. Maybe your right, that System_other Image?
So i have this A2017G owned by a cousin of mine. He had never tempered with anything except updating OTAs from the settings app. Meaning Stock everything and BL locked. Now, all of a sudden his device lags a lot (after the N-B06 update). When booting the device the boot animation lags like crazy. And it almost never gets past the boot animation (always restarts at Axon 7). The times it does reach past the boot screen, the device hangs after a minute or so and restarts.
Things that i have tried:
# Factory resetting through stock recovery.
# Downloading update.zips from ZTE and trying SD Card update trough stock recovery. Which always fails saying Signature verification failed.
# Booted to factory test mode and tried adb devices on cmd. Nothing comes up as there is no new device on the device manager. Also no sound.
# Booted to EDL mode and flashed N-B06 from this post: https://forum.xda-developers.com/axon-7/how-to/guide-ztea2017v2-0-0b08-t3658636
Nothing helped. Same old lags. And of course, the device is unusable.
What to do? Suggestions?
nsabir said:
So i have this A2017G owned by a cousin of mine. He had never tempered with anything except updating OTAs from the settings app. Meaning Stock everything and BL locked. Now, all of a sudden his device lags a lot (after the N-B06 update). When booting the device the boot animation lags like crazy. And it almost never gets past the boot animation (always restarts at Axon 7). The times it does reach past the boot screen, the device hangs after a minute or so and restarts.
Things that i have tried:
# Factory resetting through stock recovery.
# Downloading update.zips from ZTE and trying SD Card update trough stock recovery. Which always fails saying Signature verification failed.
# Booted to factory test mode and tried adb devices on cmd. Nothing comes up as there is no new device on the device manager. Also no sound.
# Booted to EDL mode and flashed N-B06 from this post: https://forum.xda-developers.com/axon-7/how-to/guide-ztea2017v2-0-0b08-t3658636
Nothing helped. Same old lags. And of course, the device is unusable.
What to do? Suggestions?
Click to expand...
Click to collapse
Get a new phone. Unfortunately I think it's some hardware that is broken. But in case it's not try to flash b05 instead?
I don't see anything else you could do since adb doesn't seems to work. I'd just RMA it with the warranty still being in effect. And if it was purchased trough amazon you'll probably just get a new one ! (that's what happened to me last time).
nsabir said:
So i have this A2017G owned by a cousin of mine. He had never tempered with anything except updating OTAs from the settings app. Meaning Stock everything and BL locked. Now, all of a sudden his device lags a lot (after the N-B06 update). When booting the device the boot animation lags like crazy. And it almost never gets past the boot animation (always restarts at Axon 7). The times it does reach past the boot screen, the device hangs after a minute or so and restarts.
Things that i have tried:
# Factory resetting through stock recovery.
# Downloading update.zips from ZTE and trying SD Card update trough stock recovery. Which always fails saying Signature verification failed.
# Booted to factory test mode and tried adb devices on cmd. Nothing comes up as there is no new device on the device manager. Also no sound.
# Booted to EDL mode and flashed N-B06 from this post: https://forum.xda-developers.com/axon-7/how-to/guide-ztea2017v2-0-0b08-t3658636
Nothing helped. Same old lags. And of course, the device is unusable.
What to do? Suggestions?
Click to expand...
Click to collapse
Did you try downgrading through EDL? I'll post the link to MM B10 for you to install through EDL, see if that helps. I seriously doubt that it's a hardware issue since it would not even boot if that was the case (take the Nexus 6P and 5X as an example: big cores busted and the phones wouldn't get past the boot logo).
Don't unlock the bootloader if you can't fix it, it'd make matters worse if LOS-based ROMs didn't work.
Edit: Here are a couple of links for B10 from 4pda. should be the same file:
https://drive.google.com/file/d/0Bynn_Z9_tfeOZWZmN1o2U09pWVU/view
https://mega.nz/#!ZhwR1BAD!PuIWa5Vivk3DxZ1Dgk-wAoITxiKmBiR-j1U8wZZidTw
Choose an username... said:
Did you try downgrading through EDL? I'll post the link to MM B10 for you to install through EDL, see if that helps. I seriously doubt that it's a hardware issue since it would not even boot if that was the case (take the Nexus 6P and 5X as an example: big cores busted and the phones wouldn't get past the boot logo).
Don't unlock the bootloader if you can't fix it, it'd make matters worse if LOS-based ROMs didn't work.
Edit: Here are a couple of links for B10 from 4pda. should be the same file:
https://drive.google.com/file/d/0Bynn_Z9_tfeOZWZmN1o2U09pWVU/view
https://mega.nz/#!ZhwR1BAD!PuIWa5Vivk3DxZ1Dgk-wAoITxiKmBiR-j1U8wZZidTw
Click to expand...
Click to collapse
I have tried this EDL package as well. Most of the time it says can not found programmer file. Only once it said can not find hello packet, reset status. That also ended up in error.
The N-B06 EDL package flashes fine. But the problem still persists.
I have also tried replacing N-B06 recovery.img with TWRP recovery.img and flashed it. But that just bricks the recovery.
Currently the 2 EDL packages i know are these two. N-B06 and MM-B10 for the G. The N one works fine while the MM one doesn't. Do u have any other EDL packages?
I too think it's a software problem since he has never dropped the phone and only used it for 2 months.
nsabir said:
I have tried this EDL package as well. Most of the time it says can not found programmer file. Only once it said can not find hello packet, reset status. That also ended up in error.
The N-B06 EDL package flashes fine. But the problem still persists.
I have also tried replacing N-B06 recovery.img with TWRP recovery.img and flashed it. But that just bricks the recovery.
Currently the 2 EDL packages i know are these two. N-B06 and MM-B10 for the G. The N one works fine while the MM one doesn't. Do u have any other EDL packages?
I too think it's a software problem since he has never dropped the phone and only used it for 2 months.
Click to expand...
Click to collapse
I think something is wrong with the hardware. I had a similar problem as u with my last phone a honor 8, it frozed up and it was nothing I couldnt do other than go back to the store with it. I got a new one.
nsabir said:
I have tried this EDL package as well. Most of the time it says can not found programmer file. Only once it said can not find hello packet, reset status. That also ended up in error.
The N-B06 EDL package flashes fine. But the problem still persists.
I have also tried replacing N-B06 recovery.img with TWRP recovery.img and flashed it. But that just bricks the recovery.
Currently the 2 EDL packages i know are these two. N-B06 and MM-B10 for the G. The N one works fine while the MM one doesn't. Do u have any other EDL packages?
I too think it's a software problem since he has never dropped the phone and only used it for 2 months.
Click to expand...
Click to collapse
I got that package from 4pda. if you go to the 4th category brick repair manual, then enter the link that says "Qualcomm drivers and MiFlash" it will redirect you to 4pda. no need to translate: just open the spoilers (I think it's the 2nd) and you'll find all of the images. You obviously have to use the A2017G ones. there's B10, i think B11, B05, B06 and maybe another N package too
The thing is that it'd be best if you could downgrade to Marshmallow, as that would probably do some other stuff that N packages don't do.
Do you have an external SD card plugged in? Try to use without external sd, i already had lags because of a defective sd card (that couldnt be rescued nor reformatted )
Perru said:
Do you have an external SD card plugged in? Try to use without external sd, i already had lags because of a defective sd card (that couldnt be rescued nor reformatted )
Click to expand...
Click to collapse
I was gonna suggest that, but a read-only SD card wouldn't provoke that. I had one that got read-only after using it as swap for a long time, and you would only notice in twrp (booted in ~2 minutes). If he was able to try to install a system update through the recovery, he was able to write to the SD card --> it's not dead
Perru said:
Do you have an external SD card plugged in? Try to use without external sd, i already had lags because of a defective sd card (that couldnt be rescued nor reformatted )
Click to expand...
Click to collapse
It lags the same. Regardless a sd card is inserted or not.
Choose an username... said:
I got that package from 4pda. if you go to the 4th category brick repair manual, then enter the link that says "Qualcomm drivers and MiFlash" it will redirect you to 4pda. no need to translate: just open the spoilers (I think it's the 2nd) and you'll find all of the images. You obviously have to use the A2017G ones. there's B10, i think B11, B05, B06 and maybe another N package too
The thing is that it'd be best if you could downgrade to Marshmallow, as that would probably do some other stuff that N packages don't do.
Click to expand...
Click to collapse
Thank you for mentioning there is EDL packages in 4pda. I just tried the packages that are available for the G variant on 4pda. But the problem still persists.
I was thinking that too. Trying to downgrade through EDL. But so far i've found only one MM so far, B10. But that ends up in error during flashing process.
Is there any way to install TWRP through EDL without unlocking bootloader? Also, is there any way to unlock BL without adb? If i could at least unlock the BL, i could flash twrp through EDL. There are EDL packages available for flashing TWRP.
Thanks.
nsabir said:
Thank you for mentioning there is EDL packages in 4pda. I just tried the packages that are available for the G variant on 4pda. But the problem still persists.
I was thinking that too. Trying to downgrade through EDL. But so far i've found only one MM so far, B10. But that ends up in error during flashing process.
Is there any way to install TWRP through EDL without unlocking bootloader? Also, is there any way to unlock BL without adb? If i could at least unlock the BL, i could flash twrp through EDL. There are EDL packages available for flashing TWRP.
Thanks.
Click to expand...
Click to collapse
Why don't u just go back to the store with it and get a new one? Its clearly something that can't be fixed by yourself unfortunately.
jw1985 said:
Why don't u just go back to the store with it and get a new one? Its clearly something that can't be fixed by yourself unfortunately.
Click to expand...
Click to collapse
Not all that clear, but yeah the last thing I'd do is unlock the bootloader.
Choose an username... said:
Not all that clear, but yeah the last thing I'd do is unlock the bootloader.
Click to expand...
Click to collapse
Mabey but I think as in my case that something has happened with the hardware. I think it is a hardware's fault that has come up to the surface when he updated the phone like it did 2 me. But hey, it's just my theory.
jw1985 said:
Why don't u just go back to the store with it and get a new one? Its clearly something that can't be fixed by yourself unfortunately.
Click to expand...
Click to collapse
Choose an username... said:
Not all that clear, but yeah the last thing I'd do is unlock the bootloader.
Click to expand...
Click to collapse
jw1985 said:
Mabey but I think as in my case that something has happened with the hardware. I think it is a hardware's fault that has come up to the surface when he updated the phone like it did 2 me. But hey, it's just my theory.
Click to expand...
Click to collapse
The problem is axon 7 is not available in our country. If he has to rma it then he has to send it to a relative in Sweden. Then the relative can do that for him. That's why he asked me to do what i can to revive the phone. RMA is the last resort for him.
Now, i guess i will give up and tell him i did everything i could.
Anyways, thank you all for helping.
I'll put the long story below..but spare those that don't want to read. The short is, I'm not able to ADB Sideload the OTA images as it always fails to verifiy signature at about 40-47%. I've searched many places and not found a fix. So I'm hoping the genuises here at XDA which I frequent can help.
The long story. I've flashed roms for many years. My current device was the Nexus 6p. Running XE Rom I think it was. Flashed an update all was well, but my sim card would not show up. I was on MetroPCS and remembered needing a different radio. Flashed that,still no sim. Decided I'd go back to Stock since those had been updated to 8 by now. Flashed the OTA and followed some steps by another thread on XDA, one of the last was locking the bootloader. I had not booted up so I didn't know if my system was working. My big mistake! I locked my bootloader and don't have a system to boot into so I can enable OEM Unlocking. So now I only have adb sideload, can't flash individual images through fastboot! I think it can be recovered but for some reason the signature verification issue keeps coming up no matter what cable or PC I use.
If anyone has any thoughts I'd love to hear them. I have since moved to a Hauwei Mate SE and am pretty pleased but will not be a flashing phone I don't think. I loved my 6p and it still had lot's of life for me. I hate to sell it for parts at this point.... Thanks for anyone willing to chime in.
tcoursey said:
I'll put the long story below..but spare those that don't want to read. The short is, I'm not able to ADB Sideload the OTA images as it always fails to verifiy signature at about 40-47%. I've searched many places and not found a fix. So I'm hoping the genuises here at XDA which I frequent can help.
The long story. I've flashed roms for many years. My current device was the Nexus 6p. Running XE Rom I think it was. Flashed an update all was well, but my sim card would not show up. I was on MetroPCS and remembered needing a different radio. Flashed that,still no sim. Decided I'd go back to Stock since those had been updated to 8 by now. Flashed the OTA and followed some steps by another thread on XDA, one of the last was locking the bootloader. I had not booted up so I didn't know if my system was working. My big mistake! I locked my bootloader and don't have a system to boot into so I can enable OEM Unlocking. So now I only have adb sideload, can't flash individual images through fastboot! I think it can be recovered but for some reason the signature verification issue keeps coming up no matter what cable or PC I use.
If anyone has any thoughts I'd love to hear them. I have since moved to a Hauwei Mate SE and am pretty pleased but will not be a flashing phone I don't think. I loved my 6p and it still had lot's of life for me. I hate to sell it for parts at this point.... Thanks for anyone willing to chime in.
Click to expand...
Click to collapse
First, if i understand right you tried to flash OTA over custom rom to return to stock?? To go to stock you must flash full system image, not OTA.
And second, why the hell did you lock the bootloader??...you dont lock the BL unless you are 100% stock..
I know i didnt help you much, but if your BL is locked, dont know how to help...maybe someone else know how to unlock it again
Meanwhile read this guide,it will help you to understand some things:
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
scrin378 said:
First, if i understand right you tried to flash OTA over custom rom to return to stock?? To go to stock you must flash full system image, not OTA.
And second, why the hell did you lock the bootloader??...you dont lock the BL unless you are 100% stock..
I know i didnt help you much, but if your BL is locked, dont know how to help...maybe someone else know how to unlock it again
Meanwhile read this guide,it will help you to understand some things:
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Oh believe me my head hit the wall for sure! I got careless and wasn't thinking straight. No reason to lock the boot loader except it was on a list of steps to get back to stock..and I guess it was late! doh.
There are lot's of posts/videos I've seen that should allow what I'm trying to do with sideload adb but mine keeps getting a signature verification error. Each new full version of a release 7.0 8.0 etc..has the entire rom, images etc. So your suppose to be able to flash those even though they are OTA updates... *shrug*
It's a blur what I did exactly in some areas. I at one point may have tried to flash the set of Stock IMG files as well. But for sure now all I'm left with is a locked phone with who knows what on it! Stock recovery...some form of 7.0.0 that has NYC as letters...that I can find NOWHERE! on any official releases...
Prob trash, I really want that night back..lol.
Hello all. I am about done with this phone. Let me give you a quick timeline.
I had a bootloader error, so I flashed the NPN25.137-35 images to get it working
I used it for about 1 week, installing all of the OTA security updates
One morning, my phone had restarted (I know because "You must enter your pattern after a restart")
Over the course of this day, google apps starting force closing and opening some of them would soft reboot the phone.
The next day, random apps were doing it too
Finally, after one crash, the OS never came back up, it was bootlooping
Upon a hard restart, the phone only boots into bootloader.
This is where I am now. I have downloaded NPN...35-5, NPNS...93-10, and NPNS...92.14. Unfortunately, trying to flash any of these give me a "prevaildation failed security update downgrade" error on every partition I try to flash. The phone just bootloops when I try to restart it.
Things I have tried:
Using fastboot to manually install one of the 3 packages mentioned above.
Using a toolkit to automate the install of the 3 packages.
Using Motorola Device Manager (Never got it to launch)
Flashing the blankflash bin (No usable image file found)
Android OEM unlock setting was not set before this crash, so I cannot unlock the bootloader.
Praying to various deities.
Unzipping the packages, editing the *info.txt file into androidinfo.txt and rezipping to use as an update package (Invalid info.txt error)
I have no idea what to do next. I find it frustrating that Motorola doesn't differentiate between 32GB, 64GB, Amazon ads, no amazon ads, US, EU, or indian variant in it's model numbers! Everything is just "XT1687" and none of the update files are named with words, so knowing what the hell I'm flashing is impossible.
So, frustrations aside, does anyone have any suggestions as to how I can get this phone working again. On a side note, the only thing that I can think of that would cause such a cascading failure from Stock OS is RAM or Storage corruption / failing. Any thoughts on that as well?
=~=~=~=~= SOLUTION FOUND =~=~=~=~=
This may not be a good solution for anyone else that has this issue, but recently Oreo came out and the OTA update was captured. I was able to flash the new OTA because it had a higher security level and at least got the phone bootable.
Do you know what software channel you were on? E.g. retus, retla, etc? If your phone was completely up to date with the OTA, then you can't use a firmware version of less than 92-14 or 93-14. Whether or not you use 92 or 93 depends on the channel.
Locked bootloader limits other possibilities unfortunately.
Retus. I can't guarantee it, but that looks familiar to me, like I had seen it somewhere in the "about phone" section. Is there a released Stock image that has the current security patch? I can't find it on XDA and I'm not trusting androidfixfiles.info or a link in a youtube video.
93-14 hasn't been leaked yet. So you'll be stuck for now.
Kilo__ said:
I have no idea what to do next. I find it frustrating that Motorola doesn't differentiate between 32GB, 64GB, Amazon ads, no amazon ads, US, EU, or indian variant in it's model numbers! Everything is just "XT1687" and none of the update files are named with words, so knowing what the hell I'm flashing is impossible.
So, frustrations aside, does anyone have any suggestions as to how I can get this phone working again. On a side note, the only thing that I can think of that would cause such a cascading failure from Stock OS is RAM or Storage corruption / failing. Any thoughts on that as well?
Click to expand...
Click to collapse
As a last resort you might try booting TWRP in fastboot mode, download and flash the TWRP flashable version of NPNS25.137-93-14. and see if that gets you back to a working phone. Just a suggestion. I don't know if it will boot when the bootloader is locked but it is worth a try.
pastorbob62 said:
As a last resort you might try booting TWRP in fastboot mode, download and flash the TWRP flashable version of NPNS25.137-93-14. and see if that gets you back to a working phone. Just a suggestion. I don't know if it will boot when the bootloader is locked but it is worth a try.
Click to expand...
Click to collapse
The phone was completely stock. It has the stock recovery and bootloader.
Kilo__ said:
The phone was completely stock. It has the stock recovery and bootloader.
Click to expand...
Click to collapse
I get that. What I am suggesting is not installing TWRP, but booting it from fastboot, if it is even possible. Given your results trying to flash a ROM I would say not. But what do you have to lose by trying?
pastorbob62 said:
I get that. What I am suggesting is not installing TWRP, but booting it from fastboot, if it is even possible. Given your results trying to flash a ROM I would say not. But what do you have to lose by trying?
Click to expand...
Click to collapse
I've tried that with a locked bootloader myself, it doesn't allow a non-signed image to boot. OP should give it a go as a 'hail Mary' attempt, but I wouldn't be holding my breath.
I've never heard of a phone that was fully stock with no mods or flashing ever done on it getting a bootloader error. The only bootloader error I am aware of is when the bootloader and ROM build are mismatched which doesn't happen unless the phone is being manually flashed. Was the phone on a custom ROM and you tried to return to full stock? Did you purchase the phone used?
If no to both exactly what did you see when you got the bootloader error? What was the message and what was the phone doing?
People who are on full stock with a locked bootloader don't usually flash system images so your story is a little hard for me to understand unless there is more to it. Normally a factory reset would be the logical solution when your phone is acting odd--flashing a system image seems pretty extreme and it sounds like flashing the wrong system image might be the cause of your current problems.
jhs39 said:
I've never heard of a phone that was fully stock with no mods or flashing ever done on it getting a bootloader error. The only bootloader error I am aware of is when the bootloader and ROM build are mismatched which doesn't happen unless the phone is being manually flashed. Was the phone on a custom ROM and you tried to return to full stock? Did you purchase the phone used?
If no to both exactly what did you see when you got the bootloader error? What was the message and what was the phone doing?
People who are on full stock with a locked bootloader don't usually flash system images so your story is a little hard for me to understand unless there is more to it. Normally a factory reset would be the logical solution when your phone is acting odd--flashing a system image seems pretty extreme and it sounds like flashing the wrong system image might be the cause of your current problems.
Click to expand...
Click to collapse
I agree. :good:
While my phone was wholly stock, I am not new to phone rooting or custom ROMS. I bought the phone from someone who was trying to unlock it. They screwed something up and couldn't get the phone to boot. I bought it, flashed the NPN25.137-35 image after reading plenty of XDA posts about it. This one was the Retus / North America stock image. Flashed using the suggested guidelines that are along the lines of "fb_oem_mode ... flash oem oem.bin ... flash partition sparsechunk1.img" (Something like that). That got it running and once booted, it had many OTAs update in quick succession. After about a week the phone started having trouble. Google apps would crash frequently, then non-google apps started crashing and restarting my phone. After one said restart, the phone would only bootloop. I tried rebooting into recovery to do a factory reset and got the bootloader instead. I can go take a look at the bootloader and see if it says it's secure / oem or what
Kilo__ said:
While my phone was wholly stock, I am not new to phone rooting or custom ROMS. I bought the phone from someone who was trying to unlock it. They screwed something up and couldn't get the phone to boot. I bought it, flashed the NPN25.137-35 image after reading plenty of XDA posts about it. This one was the Retus / North America stock image. Flashed using the suggested guidelines that are along the lines of "fb_oem_mode ... flash oem oem.bin ... flash partition sparsechunk1.img" (Something like that). That got it running and once booted, it had many OTAs update in quick succession. After about a week the phone started having trouble. Google apps would crash frequently, then non-google apps started crashing and restarting my phone. After one said restart, the phone would only bootloop. I tried rebooting into recovery to do a factory reset and got the bootloader instead. I can go take a look at the bootloader and see if it says it's secure / oem or what
Click to expand...
Click to collapse
Try flashing just the stock recovery, as it sounds like that is corrupt. Ideally you'd want to get a recovery that was the same build as you were on after all the OTAs had installed. At least you'd hope that that would give you the factory reset option.
If that doesn't work, there's fastboot commands to erase user data, cache, which would be pretty much what a factory reset would do. Hope you had your data backed up.
Oreo OTA came out recently. Someone grabbed the update file and uploaded it. I was able to flash it and get the phone to boot. The verdict is still out on if it'll be stable.