So randomly, haven't figured out what is causing it or tracking it. Used an SD card for a few days but every time I lock the screen (for any length of time) and turn it back on, it scans the SD card. Almost acts like it unmounts itself. Got to the point where it corrupted the SD card. I've taken it out and only using the internal storage. Now it is losing/unmounting itself. My downloaded ringtones and notification sounds don't work. When I open solid explorer, pops up with a message saying access denied and there's no folders.
Only way I've noticed to bring it back, I opened stock camera app and click on the camera roll. Once exited out, reopened solid explorer and the folders are back like nothing happened?!
Currently only have bootloader unlocked and rooted with magisk
You have to play back your bootloader backup because you have the bootloader with fastboot on the phone.
bootloader with fastboot = no mtp, ptp mode and the sd card is constantly ejected and re-scanned
The edl tool flashet a 160kb abl.img for bootloader unlock ( with fastboot)
What do you mean I have to play back the bootloader?
I did make a backup of the full device before I did the unlock option. Do I restore just the bootloader?
EDIT: I did read through the other thread about los. I've downloaded both yours (disabler) and DrakenFX abl.zip files. Which one do I flash in twrp?
Sent from my Moto Z2 Force using XDA Labs
amoot329 said:
What do you mean I have to play back the bootloader?
I did make a backup of the full device before I did the unlock option. Do I restore just the bootloader?
EDIT: I did read through the other thread about los. I've downloaded both yours (disabler) and DrakenFX abl.zip files. Which one do I flash in twrp?
Sent from my Moto Z2 Force using XDA Labs
Click to expand...
Click to collapse
Flash Axon10 Fastboot Disnabler.zip
Thank you so much, will do so once I get home from work. Was bout ready to return the phone because of the storage issue.
Sent from my Moto Z2 Force using XDA Labs
if you have twrp on the axon you can flash it with twrp.
otherwise with the edl tool
wenns with the edl tool but do not forget the file in abl_a.img and abl_b.img to name.
amoot329 said:
Thank you so much, will do so once I get home from work. Was bout ready to return the phone because of the storage issue.
Sent from my Moto Z2 Force using XDA Labs
Click to expand...
Click to collapse
Wait. You were about to return the phone because YOU messed it up by unlocking the bootloader and modifying it? Here's an idea. Stop fking with the phone and modifying the software and maybe it will work correctly! SMH.
xphyle1971 said:
Wait. You were about to return the phone because YOU messed it up by unlocking the bootloader and modifying it? Here's an idea. Stop fking with the phone and modifying the software and maybe it will work correctly! SMH.
Click to expand...
Click to collapse
Understandable, I do like some control over my phone. Rooting helps with that. If I'm not able to unlock it then it defeats the purpose for me owning it. Yes I've returned a Pixel 3xl when they sent me a verizon model. The oem unlock was disabled and I wasn't able to unlock the bootloader.
Sent from my Moto Z2 Force using XDA Labs
Related
About 4 weeks ago my phone spontaneously rebooted itself. Once it did I lost all (including the internal SD card) data. So basically a hard factory reset. Additionally TWRP and the recovery was borked. After much struggling I managed to get adb to put TWRP back. But now. Every necessary file system is effectively read only. (I can't mount them in
TWRP at all and when in the phone via ADB. no love) I say effectively, because although it lists it in mount as being rw. I can't even do a simple touch. nothing writes. I'm still rooted, I still have the ability to configure (as in initial setup) however if you restart the phone, all is lost, and you need to reconfigure.
Any suggestions recommendations or sympathy would be appreciated. The one thing I do see is that on the ext4 file systems (which are the ones that are effectively read only) there is an error with the journal that normally is fixed by deleting the journal and trying again. Because of this I can't re-install the OS etc. Thanks again for allowing me to whimper. Sucks that it did this 2 months before the 6.... I had to bite the bullet and replace. LG and Google both say it sucks to be me. :crying:
Backup your files. Fastboot flash userdata.img
Sent from my Nexus 5 using Tapatalk
rootSU said:
Backup your files. Fastboot flash userdata.img
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
yeah, i tried that and it keeps giving me errors related to not being able to write to the file system because the bootloader is locked. Additional. the bootloader relocked, if I unlock it, it unlocks in word but the restart to bootloader shows it is again locked. Thanks for the help though. any idea appreciated.
linuxrebel said:
yeah, i tried that and it keeps giving me errors related to not being able to write to the file system because the bootloader is locked. Additional. the bootloader relocked, if I unlock it, it unlocks in word but the restart to bootloader shows it is again locked. Thanks for the help though. any idea appreciated.
Click to expand...
Click to collapse
Your NAND is fried. Device needs sending for repair
Sent from my Nexus 5 using Tapatalk
After the OTA update both my wife and son's M8s offered them 100GB of Google Drive Storage. Jealous that they got it first I went through and updated to 5.0.1 but now Google Drive says the device can't be verified. I asked HTC in a live chat and they said it was because I was unlocked. I can understand that they are trying to prevent someone from scamming the system but now I want my 100GB upgrade. Short of locking and unlocking again (Is that even possible yet in lollipop?) does anyone have another option? Much appreciated!
Try this out
http://forum.xda-developers.com/showthread.php?t=2698548
Save the Manuals!!!
Thanks Moto. I hadn't read all the way through the thread. I'll just keep trying.
redjak said:
Thanks Moto. I hadn't read all the way through the thread. I'll just keep trying.
Click to expand...
Click to collapse
Easiest sure fire way to do it yourself is to manually relock your boot loader using the adb command. Reboot phone. Go to app manager and slide to right to get to all. Wipe data for drive and drive activator. Open drive. Claim prize. Re-unlock boot loader using adb command and reboot. Done.
dottat said:
Easiest sure fire way to do it yourself is to manually relock your boot loader using the adb command. Reboot phone. Go to app manager and slide to right to get to all. Wipe data for drive and drive activator. Open drive. Claim prize. Re-unlock boot loader using adb command and reboot. Done.
Click to expand...
Click to collapse
That's what I wanted to avoid I'm afraid of dorking up my phone again after it took me several days already to get it running with lollipop. I need to go refresh myself on ADB commands now. Thanks Dottat!
Well as Marshmallow requires you to physically select mtp mode every f*cking time you plug the phone in. Is there a way to do this with a faulty screen, because otherwise I can't copy all the pictures etc off the phone before getting it repaired/replaced?
What a clever design Google!
Ben36 said:
Well as Marshmallow requires you to physically select mtp mode every f*cking time you plug the phone in. Is there a way to do this with a faulty screen, because otherwise I can't copy all the pictures etc off the phone before getting it repaired/replaced?
What a clever design Google!
Click to expand...
Click to collapse
Ummm Actually its ur fault that ur screen is damaged .. Don't blame Google for it! And yes u "COULD" HV changed the charging option permenantly to MTP from developer options
Actually it's my missus's fault as it's her phone and I've tried before setting it as default, it just reverts back every time i unplug it.
Sent from my Xperia Z5 using XDA Labs
Ben36 said:
Well as Marshmallow requires you to physically select mtp mode every f*cking time you plug the phone in. Is there a way to do this with a faulty screen, because otherwise I can't copy all the pictures etc off the phone before getting it repaired/replaced?
What a clever design Google!
Click to expand...
Click to collapse
Boot into TWRP, MTP is enable by default.
It's unrooted and completely stock. Doh.
Sent from my Xperia Z5 using XDA Labs
Ben36 said:
It's unrooted and completely stock. Doh.
Sent from my Xperia Z5 using XDA Labs
Click to expand...
Click to collapse
You could always try a Toolkit and use that to install TWRP. Those programs, while some are against them, actually have benefits (and is probably your only solution at this moment). Look around the Original Development forum and you'll find them for PC and MAC/Linux, depending on your setup.
True, but doing that wipes data so I'm screwed either way. Lol.
What was wrong with the way kitkat worked? Plug in phone. Folders appear to view. Job done. No messing. Bloody Google!
Sent from my Xperia Z5 using XDA Labs
Ben36 said:
True, but doing that wipes data so I'm screwed either way. Lol.
What was wrong with the way kitkat worked? Plug in phone. Folders appear to view. Job done. No messing. Bloody Google!
Sent from my Xperia Z5 using XDA Labs
Click to expand...
Click to collapse
Is your bootloader locked? If so then yes, my method wouldn't work for you.
However if it is unlocked you would just be installing TWRP to the recovery partition - it doesn't erase data.
One other method would be to use a program like AirDroid and copy your files that way. If your screen isn't completely useless this may work.
Yup bootloader is locked and the screen is completely useless so I believe I'm pretty boned!
Sent from my Xperia Z5 using XDA Labs
I already wrote something like this in a similar thread, but for another device (read the device name wrong), so I thought i should post it in the right place.
I have been playing too much with stuff that i probably shouldn't have been so hasty about. So i have finally arrived here on the ERROR MODE (with unstoppable boot loop), which looks exactly like the bootloader only it says ERROR MODE instead of whatever, where i can't get into any other type of recovery or fastboot mode, no matter what button combinations i do. I previously could get to the fastboot mode, but i was still stuck so..... I made the very wise choice of relocking (since i hadn't tried that) my device, and now I can't even access fastboot (nothing. tried every button combination i can think of). So I am sitting here wondering if this is the end of the journey with my... relatively new phone... So, yes. No way of accessing anything and my phone is in a reboot loop i can't stop. Only thing is the error code i get "ERROR!":
"Func NO : 16 (lpm3 image)"
"Error NO : 1 (security verify failed!)"
Is there hope? or no?
Also noticed the light flashes green 3 times then red 1, then continues this pattern. Idk if that's useful or not.
Here's a pic.
It doesn't seem to have fastboot connection here, either.
OP were you ever able to fix this issue?
@Kimuchuu its not clear from OP had you relocked your bootloader if yes then you cant modify your system you need to have unlocked bootloader inorder to perform system modifications.
Ah. Yes, unfortunately I relocked it. I ended up sending it to service with no hopes of getting it back working, but they sent me a brand new one. So that's that.
I guess I was lucky, but really there was not a single thing I could do at that state.
You can be really happy that they sent you a new one, but it's not a unique case, in CZ there were few people who had same or similar issue and Repair service gave them new phone too.
Kimuchuu said:
Ah. Yes, unfortunately I relocked it. I ended up sending it to service with no hopes of getting it back working, but they sent me a brand new one. So that's that.
I guess I was lucky, but really there was not a single thing I could do at that state.
Click to expand...
Click to collapse
You got lucky they sent you a new one considering that you messed up the previous one. Take good care this time.
Sent from my Honor 8 using XDA Labs
Kimuchuu said:
Ah. Yes, unfortunately I relocked it. I ended up sending it to service with no hopes of getting it back working, but they sent me a brand new one. So that's that.
I guess I was lucky, but really there was not a single thing I could do at that state.
Click to expand...
Click to collapse
thats nice to hear ,man you are lucky
How exactly did you reach out to the service center?
I'm in the same situation and right now im typing the e-mail.
Im wondering what to write in the hope of getting a new one, too.
oberfeldwedler said:
How exactly did you reach out to the service center?
I'm in the same situation and right now im typing the e-mail.
Im wondering what to write in the hope of getting a new one, too.
Click to expand...
Click to collapse
In which country do you live? Just go to the nearest authorized Huawei service center. You can find them in Google.
Sent from my Honor 8 using XDA Labs
I also had this problem, trying to screw around and force a ota update via flash fire onto a modified system... Reached rhe same sddor mode, luckily I was able to manually flash all the partitions back to stock using ADB and finally once all partitions were back in order it allowed me to enter recovery mode and download and install system software threw recovery... Took me about 4 days of non stop tinkering to finally get it working again, I had all but lost hope in all honesty... Thankfully I was persistent and all is well now!
BigBrad75 said:
I also had this problem, trying to screw around and force a ota update via flash fire onto a modified system... Reached rhe same sddor mode, luckily I was able to manually flash all the partitions back to stock using ADB and finally once all partitions were back in order it allowed me to enter recovery mode and download and install system software threw recovery... Took me about 4 days of non stop tinkering to finally get it working again, I had all but lost hope in all honesty... Thankfully I was persistent and all is well now!
Click to expand...
Click to collapse
A guide how you solved your problem would help others who screwed their device to solve their problem
Update: I let the battery drain completly in this error mode and after plugging it in the Huawei eRecovery appeared...
i think i can dLoad it and get it back to work...
---------- Post added at 11:41 AM ---------- Previous post was at 11:35 AM ----------
BigBrad75 said:
I also had this problem, trying to screw around and force a ota update via flash fire onto a modified system... Reached rhe same sddor mode, luckily I was able to manually flash all the partitions back to stock using ADB and finally once all partitions were back in order it allowed me to enter recovery mode and download and install system software threw recovery... Took me about 4 days of non stop tinkering to finally get it working again, I had all but lost hope in all honesty... Thankfully I was persistent and all is well now!
Click to expand...
Click to collapse
But your bootloader wasn't locked i guess...
oberfeldwedler said:
Update: I let the battery drain completly in this error mode and after plugging it in the Huawei eRecovery appeared...
i think i can dLoad it and get it back to work...
Click to expand...
Click to collapse
But did you try the first option in erecovery?
Sent from my Honor 8 using XDA Labs
adriansticoid said:
But did you try the first option in erecovery?
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
No success
Then i tried to unlock my bootloader but got ERROR MODE again...
I'm letting the battary drain so i can enter eRecovery. Hopefully dLoad works.
By the way does anyone know whats the difference between Recovery.img an recovery2.img?
I remember flashing one of them before relocking my bootloader.
oberfeldwedler said:
No success
Click to expand...
Click to collapse
Then dload is your next choice.
Sent from my Honor 8 using XDA Labs
oberfeldwedler said:
No success
Then i tried to unlock my bootloader but got ERROR MODE again...
I'm letting the battary drain so i can enter eRecovery. Hopefully dLoad works.
By the way does anyone know whats the difference between Recovery.img an recovery2.img?
I remember flashing one of them before relocking my bootloader.
Click to expand...
Click to collapse
Recovery is the one which installs ota updates . Erecovery is an emergency recovery. It can help u restore ur phone to previous version by flashing full original firmware
I got it back to work....
I dloaded the rollback update.app
and then the real stock software
I think the thing that saved me was that i flashed stock recovery before having the glorious idea of relocking the bootlaoder.
So for anybody:
If ur device is not working DO NOT LOCK YOUR BOOTLOADER
oberfeldwedler said:
I got it back to work....
I dloaded the rollback update.app
and then the real stock software
I think the thing that saved me was that i flashed stock recovery before having the glorious idea of relocking the bootlaoder.
So for anybody:
If ur device is not working DO NOT LOCK YOUR BOOTLAODER
Click to expand...
Click to collapse
Well , great that unbricked and your last line , it is to be in bold . Thanks for it. Headsup:victory:
oberfeldwedler said:
I got it back to work....
I dloaded the rollback update.app
and then the real stock software
I think the thing that saved me was that i flashed stock recovery before having the glorious idea of relocking the bootlaoder.
So for anybody:
If ur device is not working DO NOT LOCK YOUR BOOTLAODER
Click to expand...
Click to collapse
yup thats the main point if you are not fully stock and soft bricked you are not advised to lock your bootloader. Once you locked your bootloader you can no more modify your system.
after update experienced problem with BLOD.
after freezing I've managed to boot but for short time.
is there any fix that available like for nexus6p and nexus5x?
Can you get to fastboot/bootloader?
yes, except bootloader locked. can't get enough time to unlock it in settings
Tried to boot recovery from bootloader? I believe it's possible to flash a full ota image with lock bootloader, but someone correct me if i am wrong.
Cheers
Sent from my Google Pixel using XDA Labs
thanks for suggesting, but it wouldn't fix the phone. in order to get to recovery i still have to heat up phone to start appropriately
guotti said:
thanks for suggesting, but it wouldn't fix the phone. in order to get to recovery i still have to heat up phone to start appropriately
Click to expand...
Click to collapse
Have you uhhhhhhhh /tried it/
KittyRgnarok said:
Have you uhhhhhhhh /tried it/
Click to expand...
Click to collapse
yes, the phone reboots before finish
So, it is heating when you try booting bootloader and then recovery?
Sent from my Google Pixel using XDA Labs
yep, it won't start without heating
So it's heating itself even when booted to only bootloader?
That's very weird, never heard of that before.
When that's the case, maybe it's time for a replacement
Any warranty left maybe?
Sent from my Google Pixel using XDA Labs
Sgace said:
Tried to boot recovery from bootloader? I believe it's possible to flash a full ota image with lock bootloader, but someone correct me if i am wrong.
Cheers
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Bro, i also have the same problem as OP. I am able to reach recovery and i also did a OTA flash but the device is still bootlooping. Presently, I am trying to flash a factory image but my device's bootloader is locked and i cant turn on OEM unlock from developer options as its greyed out and unpressable.
Please help me in flashing the factory image, the phone has no passwords or google account signed in atm.
Thanks in advance, I will be waiting anxiously for ur reply.
Cosmic Radiation said:
Bro, i also have the same problem as OP. I am able to reach recovery and i also did a OTA flash but the device is still bootlooping. Presently, I am trying to flash a factory image but my device's bootloader is locked and i cant turn on OEM unlock from developer options as its greyed out and unpressable.
Please help me in flashing the factory image, the phone has no passwords or google account signed in atm.
Thanks in advance, I will be waiting anxiously for ur reply.
Click to expand...
Click to collapse
If it's bootlooping, how did you see OEM unlock is greyed out?
Sent from my Google Pixel using XDA Labs
Cosmic Radiation said:
Bro, i also have the same problem as OP. I am able to reach recovery and i also did a OTA flash but the device is still bootlooping. Presently, I am trying to flash a factory image but my device's bootloader is locked and i cant turn on OEM unlock from developer options as its greyed out and unpressable.
Please help me in flashing the factory image, the phone has no passwords or google account signed in atm.
Thanks in advance, I will be waiting anxiously for ur reply.
Click to expand...
Click to collapse
I have 2 Pixels that both have the same symptom. I was lucky enough to get them to boot so I could unlock the bootloader, but flashing the factory image didn't make any difference. Based on what I've seen on the Google forums, it appears some of theses devices have faulty memory which is most likely the cause of the bootloop. Both of mine have Samsung memory. I'd be curious if your device does as well.
Sgace said:
If it's bootlooping, how did you see OEM unlock is greyed out?
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
It boots up sometimes for 2-3 mins, reaches the lockscreen etc, i can get to the settings and turn on dev tools and then i see thats its greyed out. Within 2-3mins, the device restarts again
jman315 said:
I have 2 Pixels that both have the same symptom. I was lucky enough to get them to boot so I could unlock the bootloader, but flashing the factory image didn't make any difference. Based on what I've seen on the Google forums, it appears some of theses devices have faulty memory which is most likely the cause of the bootloop. Both of mine have Samsung memory. I'd be curious if your device does as well.
Click to expand...
Click to collapse
Yes, in the bootloader its written that mine also has samsung memory. Is this repairable? have you gotten yours working?
Cosmic Radiation said:
It boots up sometimes for 2-3 mins, reaches the lockscreen etc, i can get to the settings and turn on dev tools and then i see thats its greyed out. Within 2-3mins, the device restarts again
Yes, in the bootloader its written that mine also has samsung memory. Is this repairable? have you gotten yours working?
Click to expand...
Click to collapse
Do you have a Verizon pixel maybe? Cause OEM unlock should not be grayed out, even with locked bootloader.
Sent from my Google Pixel using XDA Labs
Cosmic Radiation said:
It boots up sometimes for 2-3 mins, reaches the lockscreen etc, i can get to the settings and turn on dev tools and then i see thats its greyed out. Within 2-3mins, the device restarts again
Yes, in the bootloader its written that mine also has samsung memory. Is this repairable? have you gotten yours working?
Click to expand...
Click to collapse
No, neither device is reliable or usable. Sometimes after it's been off for a while, it will power on and be functional for a short period of time. If the memory is faulty, then I believe the motherboard has to be replaced which isn't worth the cost of the repair. I may contact google support and see if they may give me a trade in credit for a pixel 2 or 3.
my pixel turned out to be verizon, i was able to unlock bootloader and flash a factory image.. The problem still exists. Bootloops are still happening:crying:
Cosmic Radiation said:
my pixel turned out to be verizon, i was able to unlock bootloader and flash a factory image.. The problem still exists. Bootloops are still happening:crying:
Click to expand...
Click to collapse
Yep. Same issue here. Our devices are likely paperweights I'm afraid.
Can confirm, I woke up to an infinite bootloop this morning after applying the December security patch. Seems to be a hardware issue that just kills the phone.
Have you guys have tried to cool the phone down like putting it on top of an ice bag with saltwater, like a zip lock bag, give it a minute on top of the brine and then try? Should give you some time until you can get into the rom and tap the unlock button?