Hi all, I really messed up my 6T today, after messing with the new update and root, I ran the flash_all.bat file (from https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516) to restore images but didn't realize it would clear all my data, I stopped the process after it ran for a few seconds in a panic but now my phone only has the fastboot screen and fastboot.exe from my cmd shell is unable to do anything (just errors out for most commands), is there a way for me to at least retrieve my photos from my phone? I've tried 3rd party software and they all require usb debugging which I can't activate due to my phone not having a boot image. Any help would be a miracle, thanks.
I would try fastbooting a TWRP image. From there you may get access to your internal storage. You can then copy it off to a PC. I say may because you could encounter encryption issues when trying to first boot into TWRP.
If you do hit encryption issues, you could modify the "flash all" batch file to remove the -w command so it doesnt format. However, I thought that it gave you an option to wipe or not?
If it did wipe first, your a gonner my friend. You are too late.
Hope this gives you some insight on where to go from here.
Thanks, that's what some others have been telling me, I have tried to fastboot flash a few versions of TWRP and blu spark (I had the latest android version I believe, so even tried the Q version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482), but none of them are working, I get a failed to load/authenticate error when doing fastboot flash <img name> and fastboot flash boot <img> doesn't error out but I still can't get past the fastboot menu.
I see the flash_all script has the -w in it, but yeah it never prompted me about wiping all data. I managed to kill the process a few seconds in, so even if it was deleting, large files like my photos and videos should still be existent on the drive somewhere, right? Unless the -w command does a really fast purge of the files?
christmasdesparation said:
Thanks, that's what some others have been telling me, I have tried to fastboot flash a few versions of TWRP and blu spark (I had the latest android version I believe, so even tried the Q version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482), but none of them are working, I get a failed to load/authenticate error when doing fastboot flash <img name> and fastboot flash boot <img> doesn't error out but I still can't get past the fastboot menu.
I see the flash_all script has the -w in it, but yeah it never prompted me about wiping all data. I managed to kill the process a few seconds in, so even if it was deleting, large files like my photos and videos should still be existent on the drive somewhere, right? Unless the -w command does a really fast purge of the files?
Click to expand...
Click to collapse
THe -w command does a very fast wipe. So if it was at the beginning of the scrip that more than likely like your files are gone.
Run the script again, this time delete the -w command. This will be your best chance of finding any data.
I see, if the wipe has already happened, are there more low-level ways to retrieve the data? Since it couldn't have purged from the disk all 20 gigs of photos in such a short time span. Though I'm guessing even if there are fragments left like that they're most likely corrupted and unusable?
Anyway, I took it to a shop today since I couldn't do much else my self, we'll see what happens. Lesson learned to always back up before messing with the boot.
Thanks
christmasdesparation said:
Lesson learned to always back up before messing with the boot.
Click to expand...
Click to collapse
And to properly read and understand what it is you're attempting to do.
sssarg said:
And to properly read and understand what it is you're attempting to do.
Click to expand...
Click to collapse
lol yes but in my defense I was already kind of freaking out since the fastboot wasn't working like it did previous times and messed up my normal boot
christmasdesparation said:
I see, if the wipe has already happened, are there more low-level ways to retrieve the data? Since it couldn't have purged from the disk all 20 gigs of photos in such a short time span. Though I'm guessing even if there are fragments left like that they're most likely corrupted and unusable?
Click to expand...
Click to collapse
Probably not possible as user data are stored in a virtual filesystem, mounted over an encrypted partition.
That's the reason why police forces regularly ask phone makers to put a backdoor, it's very hard even for a high tech forensic specialist to find data on a phone
So I actually re-ran the flash_all.bat script without the -w flag and I was able to fast boot flash into twrp (twrp-3.3.1-30-fajita-Q-mauronofrio to be specific). I can see what i believe are my files in the internal storage, but encrypted, however twrp never prompted me for a password, also going to the twrp terminal and entering twrp decrypt <passcode> did not work. Anybody know how to get twrp to decrypt? For some reason flash_all.bat did not restore my original boot or anything so I am only able to boot into recovery mode or twrp from the fastboot on my PC. doing fastboot getvar all shows that my slot-unbootable:a is "yes" if anyone knows how to make sense of this, it would be appreciated, even if I just need to copy my phones internal storage on to my computer and run 3rd party software to decrypt it that is fine
Thank you
Final update: fixed my device completely, turns out I was using the flash all for update 41, all I had to do was use the same script for the 42 update without the -w flag and now my phone is back to normal, everything is where it originally was
christmasdesparation said:
Final update: fixed my device completely, turns out I was using the flash all for update 41, all I had to do was use the same script for the 42 update without the -w flag and now my phone is back to normal, everything is where it originally was
Click to expand...
Click to collapse
Could have used msm tool. You would have lost everything but at least phone would have worked
jamescable said:
Could have used msm tool. You would have lost everything but at least phone would have worked
Click to expand...
Click to collapse
Yeah, he was trying hard to avoid that.
christmasdesparation said:
Final update: fixed my device completely, turns out I was using the flash all for update 41, all I had to do was use the same script for the 42 update without the -w flag and now my phone is back to normal, everything is where it originally was
Click to expand...
Click to collapse
Im glad it did not wipe the phone the like I feared it may have. Glad you got it going.
Scott said:
Im glad it did not wipe the phone the like I feared it may have. Glad you got it going.
Click to expand...
Click to collapse
Thanks, I owe it to you, your original advice was spot on and all I failed to do was check the version number
jamescable said:
Could have used msm tool. You would have lost everything but at least phone would have worked
Click to expand...
Click to collapse
Well to me "everything" on my phone was worth more to me than the phone itself
Related
Is there anyone around with a Rogers HTC Dream?
if so, could you please do a nandroid backup of your phone and sent me the files?
I can't boot my phone after messing up reflashing it with incompatable firmware
Thanks in advance!
they are here
Yep they are there and I plan to leave them on that server permanently.
would i install these using fastboot... or what would I use?
the nandroid gives me errors
it refuses to back up my data and will not restore anything
if i use nandroid-mobile.sh backup in the console it says
error reading recovery no space left on device
PurpleFries said:
would i install these using fastboot... or what would I use?
the nandroid gives me errors
it refuses to back up my data and will not restore anything
if i use nandroid-mobile.sh backup in the console it says
error reading recovery no space left on device
Click to expand...
Click to collapse
yup fastboot.
k heres what i used
fastboot flash boot boot.img
fastboot flash system system.img
restarted and
still stuck on rogers screen
no change whatsoever
When I semi-bricked my phone these are the instructions I used.
Since you can get into fastboot you should be able to reload to factory settings no problem.
should be...
hmmmm, looks like you did the correct thing.
Just to let you know, after you reload the fresh copy of boot.img and system.img it will take much longer for your phone to turn on the first time, typically 5-10 minutes. It has to re-install the OS on the phone.
thats essentially what i did
however the link you gave me did not include a data.img
DISREGARD TEMPORARILY, waiting those 5-10 minutes
it doesnt work if i just flash the boot and system
also, would i need to reflash the recovery with the stock rom? because then i need the stock recovery rom as well
PurpleFries said:
thats essentially what i did
however the link you gave me did not include a data.img
Click to expand...
Click to collapse
The data.img would be personal. It's not needed, but if you don't have when you flash your Dream it'll be like you're starting over for the first time.
it doesnt work if i just flash the boot and system
also, would i need to reflash the recovery with the stock rom? because then i need the stock recovery rom as well
Click to expand...
Click to collapse
AFAIK, the stock from is the system.img file. How lond did you leave it on the Rogers screen before you manually restarted your phone?
as of now, it's been approx 10 minutes.
after ur post edit i wiped and re-fastboot-ed the stuff
gonna let it run for about 20 minutes before i conclude its still not workin
EDIT
18 minutes so far...
not looking favorable T.T
EDIT2
yea its been 20 minutes, no change...
any other ideas?
EDIT3
30 minutes...
def not working
PurpleFries said:
as of now, it's been approx 10 minutes.
after ur post edit i wiped and re-fastboot-ed the stuff
gonna let it run for about 20 minutes before i conclude its still not workin
Click to expand...
Click to collapse
yeah after 20 minutes it's certainly too long. I think mine only took about 5 minutes, but good luck. eeep
edit: worse comes to worse, take it back to the store and tell them your phone wont turn on.
Also you might be able to get more help tomorrow on the subject. I'm a fairly big newbie here so I don't know that much. There is a way for your computer to see at what point your phone may be frozen at but I can't remember how.
edit 2:
17. It's taking forever to boot!
The first boot will take longer than normal because dexopt needs to run. If you are nervous, connect USB and run "adb logcat" to watch the progress.
Click to expand...
Click to collapse
That is from cyanogen, but it should give you some insight as to what your phone may be doing.
doesnt help
it doesnt see my device as attached.
adb devices doesnt list a device
and adb logcat tells me its waiting for devices
I'm sure ill need some sort of explanation as to why it doesnt turn on... what could I say?
also, not sure if i thanked you before, but thanks for all of the assistance
EDIT
it sees the device if it is attached in recovery mode
I still cant logcat tho
it says: /sbin/sh: exec: line 1: logcat: not found
PurpleFries said:
doesnt help
it doesnt see my device as attached.
adb devices doesnt list a device
and adb logcat tells me its waiting for devices
I'm sure ill need some sort of explanation as to why it doesnt turn on... what could I say?
also, not sure if i thanked you before, but thanks for all of the assistance
EDIT
it sees the device if it is attached in recovery mode
I still cant logcat tho
it says: /sbin/sh: exec: line 1: logcat: not found
Click to expand...
Click to collapse
I would just tell them I turned it on this morning and this happened. Ask them if they can fix it and see what happens. Mention nothing about trying to root it.
Just to make sure you're doing the steps correctly.
You're downloading the files I provided for you and placing them in your android/sdk..../tools folder right?
Then you boot the phone into fastboot?
Then I think you press the talk button to usb connect
from there you type in the commands.
Is that what you're doing?
exactly word for word.
during entering the commands:
i flash the boot and system.img
and press the back button to reboot
then i do the adb logcat and it cannot detect the device
PurpleFries said:
exactly word for word.
during entering the commands:
i flash the boot and system.img
and press the back button to reboot
then i do the adb logcat and it cannot detect the device
Click to expand...
Click to collapse
have you applied the update.zip file? Perhaps try applying that again first and then try the recover again.
which update.zip?
you never told me to install an update.zip previously
it's done through the recovery menu correct?
PurpleFries said:
which update.zip?
you never told me to install an update.zip previously
it's done through the recovery menu correct?
Click to expand...
Click to collapse
Well from that earlier psot I showed you that linked to HOFO step #1 had this.
Assuming you installed the update.zip before or after rooting (you can do it at any point really), now you can begin the recovery. First, enter the following into the command prompt
Click to expand...
Click to collapse
So it looks like the phone has to be rooted before you can apply the backup and to root the phone correctly you need the update.zip file.
The instructions to install the update.zip file and the file itself can be found here
Perhaps try to follow all of those steps, well skip the nandroid backup and see if your phone boots after that. If it does not but you can install the update.zip file then try the recovery method you have been trying.
tried updating with the files given (update.zip, boot.img, recovery.img)
could not go into recovery mode, would not boot
tried updating with update.zip and other files from before(update.zip, boot.img, system.img)
still no booting
my phone was, however already root-ed before it stopped working
PurpleFries said:
tried updating with the files given (update.zip, boot.img, recovery.img)
could not go into recovery mode, would not boot
tried updating with update.zip and other files from before(update.zip, boot.img, system.img)
still no booting
my phone was, however already root-ed before it stopped working
Click to expand...
Click to collapse
Sorry then. I'm out of ways to help. I don't really know all that much about the process. Perhaps your phone is slightly different than the rest of our Rogers phones so my backup files wont work on yours.
how long ago did you get it?
this thursday
I rarely use my Nexus 7, but today decided to update it to 4.2.2. I flashed everything from android sdk: bootloader, clockworkmod recovery, franco kernel, system, and userdata. Then I sideloaded the SuperSU zip to root the tablet before my first boot up. Now when it boots up, it asks me to type my password to decrypt the storage. I never set a password on the tablet and the other people that used the tablet in my home as far as I know, did not encrypt the storage. Now, I even wiped/factory reset the device from clockworkmod as well as reflashing system and userdata. Why is this occurring?
Bump.
Boot your device in the bootloader (fastboot) and type
Code:
fastboot format userdata
Or if this won't work you could format every partition and after formatting it you flash the images again
Sent from my Nexus 7 running Android 4.2.2
I woke up with the same problem. Tried to boot into recovery and got the "No Command" message. I ended up having to call Google Customer Care and they are sending me a new tablet for free. I just have to send the defective device back to them within days. May be helpful if you bought you device from the Google Play Store.
Hi guys,
I woke up to the same thing too, but I'm afraid to call customer service because my tablet is unlocked..(but it's running stock android and this issue just showed up the day after I updated it to 4.2.2...
P.S: I bought it from the Play Store as well.
Thanks!
mihahn said:
Boot your device in the bootloader (fastboot) and type
Code:
fastboot format userdata
Or if this won't work you could format every partition and after formatting it you flash the images again
Sent from my Nexus 7 running Android 4.2.2
Click to expand...
Click to collapse
I tried that before and it didn't work. Thanks.
Xavion2004 said:
I woke up with the same problem. Tried to boot into recovery and got the "No Command" message. I ended up having to call Google Customer Care and they are sending me a new tablet for free. I just have to send the defective device back to them within days. May be helpful if you bought you device from the Google Play Store.
Click to expand...
Click to collapse
I called up Nexus Support and they had setup for me to send it back to them; however, I fixed it after I got off the phone with them. Very strange bug; If I flash clockworkmod recovery, the tablet will boot into the type password to decrypt storage. The factory data reset on clockworkmod recovery doesn't fix it either. If I flash back to the stock recovery and factory data reset, the tablet works fine. I probably don't even need to factory data reset - it's stock recovery that fixes this. I didn't have the "No Command" message though which the Nexus Support guy thought I would have. So I guess I don't have to send my tablet back after all . I wanted to because it's an 8gb and I probably would of got upgraded to a 16gb since the 8gb model is no longer manufactured, haha.
Abhitha said:
Hi guys,
I woke up to the same thing too, but I'm afraid to call customer service because my tablet is unlocked..(but it's running stock android and this issue just showed up the day after I updated it to 4.2.2...
P.S: I bought it from the Play Store as well.
Thanks!
Click to expand...
Click to collapse
Download android sdk on your pc, go to platform-tools, open command prompt, boot tablet into the bootloader, type 'fastboot oem lock' to lock the tablet again.
Download android sdk on your pc, go to platform-tools, open command prompt, boot tablet into the bootloader, type 'fastboot oem lock' to lock the tablet again.
Click to expand...
Click to collapse
Thanks. I will try this when I get home today and post back after a call to customer support :good:
Download android sdk on your pc, go to platform-tools, open command prompt, boot tablet into the bootloader, type 'fastboot oem lock' to lock the tablet again.
Click to expand...
Click to collapse
Hm I tried locking the tablet as per your instructions, and it succeeded (at least according to the command prompt), however the unlocked symbol is still there. I called support and they told me they can't RMA is till I relock it...
EDIT:
I followed instructions at another post on XDA to flash back the stock 4.2.2 rom as well as perform another oem lock, however the unlocked symbol is still there on the Google splash screen, not to mention the encryption message is still there.
I just wanted to point out: in my experience, you can't sideload anything before first boot after reflashing userdata.img or doing a wipe from fastboot, because it doesn't initialize the data partition until you take it through a boot cycle into the ROM. This may be the cause of the erroneous encryption message in custom recovery.
If you boot the tablet, and then after boot and proper shutdown go into custom recovery, do you still get the same message?
Sent from my Nexus 7 using Tapatalk HD
Was there ever a resolution for this issue? I ran into the same thing today - I turned on my n7 after months of no use, and it asked for a decryption password which I never set.
jmusso said:
Was there ever a resolution for this issue? I ran into the same thing today - I turned on my n7 after months of no use, and it asked for a decryption password which I never set.
Click to expand...
Click to collapse
Resolution, I don't know. I do have a a few more tidbits of information, though.
I could reproduce the "enter password" symptom by doing a "fastboot erase userdata" followed by a boot of the custom recovery. That is, by not having any filesystem at all, I could produce the symptom with TWRP - even though I have never encrypted the /data partition. So, at least certain versions (2.4.1.0?) of that custom recovery seems to regard a mount failure to mean that "your data paritition is encrypted" - that certainly is a "red herring".
iirc, there is supposed to be a "crypto footer" in the last 16k bytes of the partition which lives outside of the end of the ext4 filesystem. I suppose that if you knew the exact size of your data partition, you could write zeros (dd if=/dev/zero ...) using the custom recovery to the last 16k of that partition and see if that clears anything up. Search the (above) link near the places where it mentions the "crypto footer". If that last 16k were all zeros, I would think that would cause "vold" to realize that there is no valid keys, etc in there. (But that's a little bit of a guess).
None of it explains why a device can sit on a shelf for months and suddenly start behaving differently on it's next boot, though. That smells a lot like bit rot or hardware failure in the eMMC flash memory.
But if the alternative is to throw the tablet out, it can't hurt to do a factory reset (stock devices) or a "fastboot erase userdata ; fastboot format userdata" (unlocked device). Both of those will nuke all data (including what's on the psuedo-SD card).
Anyhow, there's two ideas.
good luck
bftb0 said:
Resolution, I don't know. I do have a a few more tidbits of information, though.
I could reproduce the "enter password" symptom by doing a "fastboot erase userdata" followed by a boot of the custom recovery. That is, by not having any filesystem at all, I could produce the symptom with TWRP - even though I have never encrypted the /data partition. So, at least certain versions (2.4.1.0?) of that custom recovery seems to regard a mount failure to mean that "your data paritition is encrypted" - that certainly is a "red herring".
iirc, there is supposed to be a "crypto footer" in the last 16k bytes of the partition which lives outside of the end of the ext4 filesystem. I suppose that if you knew the exact size of your data partition, you could write zeros (dd if=/dev/zero ...) using the custom recovery to the last 16k of that partition and see if that clears anything up. Search the (above) link near the places where it mentions the "crypto footer". If that last 16k were all zeros, I would think that would cause "vold" to realize that there is no valid keys, etc in there. (But that's a little bit of a guess).
None of it explains why a device can sit on a shelf for months and suddenly start behaving differently on it's next boot, though. That smells a lot like bit rot or hardware failure in the eMMC flash memory.
But if the alternative is to throw the tablet out, it can't hurt to do a factory reset (stock devices) or a "fastboot erase userdata ; fastboot format userdata" (unlocked device). Both of those will nuke all data (including what's on the psuedo-SD card).
Anyhow, there's two ideas.
good luck
Click to expand...
Click to collapse
I'm just responding to say this fix worked for me. I only did a "fastboot erase userdata" from the adb terminal in Windows, however. Thanks for the help, and good luck to anyone else running into this problem.
Nexus 5, Flash write failure
Hey guys,
I am getting flash write errors whenever i try to fastboot stock images..
Nothing seems to be working.
I am able to temporarily boot into Philz recovery using the Nexus Rootkit and get adb functionality also.
But the phone doesn't boot into anything and i am forced to use TWRP recovery. Any other recovery doesn't work other than booting temporarily.
TWRP is also asking for a password i didnt set.
PLEASEEEE HELPPPP SOMEONEEE
Either your device is permanently bricked, or you have driver problems on the computer running fastboot. Try a different computer, different USB cable, etc.
Sent from my Nexus 7 using Tapatalk
i have done factory restore; data format full system, advanced wipes and reloads forever, but at the end of the day, that damn decrypt message is still there. at this point, i don't care about data. i just want the phone back up and running. i don't care which rom, even factory. i am on a htc evo 4g lte, with hboot 2.10.0000. and i have tried several recoveries.
I cannot get my phone to accept ADB commands while in the Bootloader. The phone has been doing some strange stuff so I decided to start from scratch and reinstall everything. I tried to use the "Restore to Stock Tool" but once it reboots to the bootloader, I get "device not found" until it gets to the erase commands, phone restarts and is wiped but still on the 6.0 update. I tried "adb devices" and the device shows up but if I try "adb reboot bootloader" it reboots to the bootloader but "adb devices" doesn't see the device anymore. The only thing I can think that could cause this is a corrupt bootloader but how can you correct the problem if you can't flash anything? If someone can suggest anything I can try, I would appreciate it.
6.0 is the current update...
Flash twrp then try flashing a custom ROM. Honestly it sounds like you might be doing something wrong, or maybe a bad USB cable? Keep trying I don't think you're screwed
Steeleio said:
I cannot get my phone to accept ADB commands while in the Bootloader. The phone has been doing some strange stuff so I decided to start from scratch and reinstall everything. I tried to use the "Restore to Stock Tool" but once it reboots to the bootloader, I get "device not found" until it gets to the erase commands, phone restarts and is wiped but still on the 6.0 update. I tried "adb devices" and the device shows up but if I try "adb reboot bootloader" it reboots to the bootloader but "adb devices" doesn't see the device anymore. The only thing I can think that could cause this is a corrupt bootloader but how can you correct the problem if you can't flash anything? If someone can suggest anything I can try, I would appreciate it.
Click to expand...
Click to collapse
Do you still have an custom recovery installed? TWRP?
Steeleio said:
I cannot get my phone to accept ADB commands while in the Bootloader. The phone has been doing some strange stuff so I decided to start from scratch and reinstall everything. I tried to use the "Restore to Stock Tool" but once it reboots to the bootloader, I get "device not found" until it gets to the erase commands, phone restarts and is wiped but still on the 6.0 update. I tried "adb devices" and the device shows up but if I try "adb reboot bootloader" it reboots to the bootloader but "adb devices" doesn't see the device anymore. The only thing I can think that could cause this is a corrupt bootloader but how can you correct the problem if you can't flash anything? If someone can suggest anything I can try, I would appreciate it.
Click to expand...
Click to collapse
Frankly, I would be surprised if your "SCREWED"... it sounds more like your misinformed.
ADB will NEVER work in the bootloader, it isn't intended to, that is what fastboot is for. ADB stands for Android Debugging Bridge because it is the computer's "bridge" to Android, you can think of it as the connection to the operating system, meaning the phone must be booted and running Android for it to work or there is nothing to "bridge" to.
Fastboot is a more limited tool designed to talk to the bootloader and get the phone so that operating system can boot or it can be returned to it's factory state, fastboot cannot talk or "bridge" to Android. They are different and unique tools with different purposes that are used at different times.
This is another case of why one-click or scripting tools are not recommended... even if they work 90% of the time or more, there is still failure due to automation.
I would suggest grabbing the full factory firmware package and install it MANUALLY with the fastboot commands and you will likely be fine. Remember to give it time on the first boot, it can be 20 minutes or more before things look like they are progressing initially.
acejavelin said:
Frankly, I would be surprised if your "SCREWED"... it sounds more like your misinformed.
ADB will NEVER work in the bootloader, it isn't intended to, that is what fastboot is for. ADB stands for Android Debugging Bridge because it is the computer's "bridge" to Android, you can think of it as the connection to the operating system, meaning the phone must be booted and running Android for it to work or there is nothing to "bridge" to.
Fastboot is a more limited tool designed to talk to the bootloader and get the phone so that operating system can boot or it can be returned to it's factory state, fastboot cannot talk or "bridge" to Android. They are different and unique tools with different purposes that are used at different times.
This is another case of why one-click or scripting tools are not recommended... even if they work 90% of the time or more, there is still failure due to automation.
I would suggest grabbing the full factory firmware package and install it MANUALLY with the fastboot commands and you will likely be fine. Remember to give it time on the first boot, it can be 20 minutes or more before things look like they are progressing initially.
Click to expand...
Click to collapse
So I got the computer to recognize the phone. I reset everything back to stock 5.1.1. Once I had it reset, the Bluetooth would not turn on (which was one of my original problems). So I took all the OTAs to get back to 6.0. For some reason when It got to about the 3rd update, it wouldn't complete. It failed but didn't specify a reason. I tried this 2 times without any luck. I left it at the update it was on and used it for a day. The Bluetooth still would not turn on and I was experiencing random data drops which required a reboot. I finally gave up because I was so frustrated. I figured something must be going wrong some hardware inside the phone.
Steeleio said:
So I got the computer to recognize the phone. I reset everything back to stock 5.1.1. Once I had it reset, the Bluetooth would not turn on (which was one of my original problems). So I took all the OTAs to get back to 6.0. For some reason when It got to about the 3rd update, it wouldn't complete. It failed but didn't specify a reason. I tried this 2 times without any luck. I left it at the update it was on and used it for a day. The Bluetooth still would not turn on and I was experiencing random data drops which required a reboot. I finally gave up because I was so frustrated. I figured something must be going wrong some hardware inside the phone.
Click to expand...
Click to collapse
Style or Pure? And why flash 5.1.1 when 6.0 images are available? http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Also, I see many guides don't show flashing the Bluetooth firmware for some reason, so depending on the guide you used might be wrong, always look at the XML file in the image.
fastboot flash bluetooth BTFM.bin
Sent from my XT1575 using Tapatalk
acejavelin said:
Style or Pure? And why flash 5.1.1 when 6.0 images are available? http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Also, I see many guides don't show flashing the Bluetooth firmware for some reason, so depending on the guide you used might be wrong, always look at the XML file in the image.
fastboot flash bluetooth BTFM.bin
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Pure. I figured if I start all the way over from the beginning it would work out. Like I said, even one of the OTA's failed. I tried flashing the BTFM.bin file but that didn't work either. I will try some other stuff when I get off work today.
So I tried starting from scratch again. I get a "validation failed" when I try to flash the gpt.bin file. Everything else worked. Bluetooth and data are working now. Could I have a corrupt partition that is causing the validation to fail? Does anyone know the partition sizes for the Pure?
Steeleio said:
So I tried starting from scratch again. I get a "validation failed" when I try to flash the gpt.bin file. Everything else worked. Bluetooth and data are working now. Could I have a corrupt partition that is causing the validation to fail? Does anyone know the partition sizes for the Pure?
Click to expand...
Click to collapse
No, in fact it is quite common to get that message with the partition information... Ignore it, if everything else went fine and you having no more problems, your good to go.
I need your help, after upgrading to 7.1.1 the phone is dialed and restarted all the time in this way.
I would appreciate a solution, I leave an exact example of what happens to me.
OEM is not unlocked and debugging mode either because I can not start the phone
My problem is that it does not unlock OEM and I was not active debugging, the phone just let me enter Fastboot but at the time of choosing RECOVERY it restarts
emmafer44 said:
I need your help, after upgrading to 7.1.1 the phone is dialed and restarted all the time in this way.
I would appreciate a solution, I leave an exact example of what happens to me.
OEM is not unlocked and debugging mode either because I can not start the phone
Click to expand...
Click to collapse
Dude try Nexus toolkit my Wugfresh (NRT Toolkit) you have to boot to bootloader and use the application to clean install
I have this same problem. flashed MegaPixel6P, tried using the camera, and then my phone shut off and just keeps rebooting. i think /data and /system are corrupted. any attempt to nandroid backup or restore fails and causes TWRP to reboot.
Alot of users are facing this bootloop issue. So far no one has been able to figure out a pattern that will give us insight into what kind of devices might be affected by this issue. I have created this survey on GoogleForums so far there are very few responses. Please participate to help the community figure out the probable cause for this bootloop
https://docs.google.com/forms/d/1nGAVdnjbkOE1ohvZvqbntb_7afT4p2OzbFIJjJWiy9Q/edit?c=0&w=1
BTW what's your phone's manufacturing date? were you using Magisk or SuHide?
Dadud said:
I have this same problem. flashed MegaPixel6P, tried using the camera, and then my phone shut off and just keeps rebooting. i think /data and /system are corrupted. any attempt to nandroid backup or restore fails and causes TWRP to reboot.
Click to expand...
Click to collapse
If you can get to TWRP, you can just reflash via fastboot (or use NRT). You may be able to apply your TWRP backup afterwards if it is not corrupted.
As for OP, if the bootloader is locked, and "Allow OEM Unlock" is toggled off, your options are slim to none. If this setting was enabled before upgrading then it is still enabled. If it was not, you cannot unlock the bootloader.
v12xke said:
If you can get to TWRP, you can just reflash via fastboot (or use NRT). You may be able to apply your TWRP backup afterwards if it is not corrupted.
As for OP, if the bootloader is locked, and "Allow OEM Unlock" is toggled off, your options are slim to none. If this setting was enabled before upgrading then it is still enabled. If it was not, you cannot unlock the bootloader.
Click to expand...
Click to collapse
Ive tried literally every fix, its dead jim.
Dadud said:
Ive tried literally every fix, its dead jim.
Click to expand...
Click to collapse
Have you tried FORMATTING boot, system, data & vendor and then reflash? Format, not erase/wipe. Move your TWRP backup off to PC and try that. If you are rusty in ADB/Fastboot, then use NRT to do same in advanced tools. If you have a working recovery and your bootloader is unlocked, I would not give up yet. Good luck!
Dadud said:
I have this same problem. flashed MegaPixel6P, tried using the camera, and then my phone shut off and just keeps rebooting. i think /data and /system are corrupted. any attempt to nandroid backup or restore fails and causes TWRP to reboot.
Click to expand...
Click to collapse
Yeah your problem is a bit different that others and it's worth investigating.
To verify your complete emmc, you could try this command in twrp -> advanced settings -> terminal.
dd if=/dev/block/mmcblk0 of=/dev/null
Basically doing a read test by copying the complete mmc to the void. It should give you a status at the end that you can post here.
By the way, the recommended factory flashing is by using flash-all script that is inside the factory image itself. And you need the latests android SDK.
rchtk said:
Yeah your problem is a bit different that others and it's worth investigating.
To verify your complete emmc, you could try this command in twrp -> advanced settings -> terminal.
dd if=/dev/block/mmcblk0 of=/dev/null
Basically doing a read test by copying the complete mmc to the void. It should give you a status at the end that you can post here.
By the way, the recommended factory flashing is by using flash-all script that is inside the factory image itself. And you need the latests android SDK.
Click to expand...
Click to collapse
nope. i enter the command and it does nothing for about a minute before turning itself off
also, im not some complete n00b, so trust me when i say i've tried everything. any time i restore a backup, once it starts applying just /data or /system it'll shut off and bootloop without finishing.
Dadud said:
nope. i enter the command and it does nothing for about a minute before turning itself off
also, im not some complete n00b, so trust me when i say i've tried everything. any time i restore a backup, once it starts applying just /data or /system it'll shut off and bootloop without finishing.
Click to expand...
Click to collapse
You never know the level of the person you're talking about eh. Just tought you hadn't tried the dd.
So dd shutting down before completing wasn't expected but now if I read again your posts, you said doing a photo shuts down the phone and that's quite typical of power related problems. Sh*t.
Could be the battery not holding discharge. Can the device stay in twrp with screen off? Did you try to let it fully discharge and charge it with a slow charge?
There are a lot of information in /sys/ or dmesg but it won't solve your issue.
Still under warranty?
Dadud said:
nope. i enter the command and it does nothing for about a minute before turning itself off
also, im not some complete n00b, so trust me when i say i've tried everything. any time i restore a backup, once it starts applying just /data or /system it'll shut off and bootloop without finishing.
Click to expand...
Click to collapse
Forget restoring your backup for now. You're not a noob, so transfer your TWRP backup to PC, then FORMAT each partition first, including userdata and then reflash using a Google Imagehere. Ensure you are using the latest version of ADB/Fastboot. You didn't mention you have already attempted to Fastboot flash the NMF26F image. What was your result then? The reason I'm asking is that the Google script erases the partitions- does not format, but running the script will tell you which partition failed during writing.
Huawei Customer Service!!
Had the exact same problem creep up on me this past weekend. I ended up calling Huawei and they are doing a free warranty repair on my phone even though I'm almost two months out of warranty.
Make sure you are on SDK 25, I had the problem synonymous. I have been hunted at Huawei and only when I had already given it I realized that I was not on SDK 25 and I know of some others that was the reason with most.
Whether it was the reason with me, I know tomorrow, the device is back and can be picked up,
Tylog said:
Make sure you are on SDK 25...
Click to expand...
Click to collapse
Yes, the latest ADB / Fastboot is required. The rest of the SDK is not mandatory. You can get a minimalist ADB-Fastboot-Driver install from an XDA dev here.
Also, TWRP updated for Angler recently here. This update solved a persistent backup problem I had with the previous v3.0.2-2
bought it second hand, and the previous owner bought it at launch, so im just a month or so out of warranty. im trying to get the original receipt to attempt to RMA it. Huawei's IMEI lookup says its under warranty till april 4th next year.
Tylog said:
Make sure you are on SDK 25, I had the problem synonymous. I have been hunted at Huawei and only when I had already given it I realized that I was not on SDK 25 and I know of some others that was the reason with most.
Whether it was the reason with me, I know tomorrow, the device is back and can be picked up,
Click to expand...
Click to collapse
Was your phone stuck in Bootloop of death as well? How did you fix it? What do think causes this issue and how can it be avoided?
After flashing a rom my phone got hot, and I didn't want to run any more roms for awhile. So i decided it was time for a fresh install of factory image. I read the guide lines closely to fastbooting the latest factory image. Now im in a boot loop with the google unlock icon and the corruption screen . I tried going to stock recovery and factory wipe and still bootlooping. It's been doing this for awhile. Please help!
Did you verify the checksum of the image prior to executing the flash-all script?
redduc900 said:
Did you verify the checksum of the image prior to executing the flash-all script?
Click to expand...
Click to collapse
I don't use flash all script. I flashed each img individually like it's posted in the guide
redduc900 said:
Did you verify the checksum of the image prior to executing the flash-all script?
Click to expand...
Click to collapse
Yes the checksum was verified
XMayhem2099 said:
After flashing a rom my phone got hot, and I didn't want to run any more roms for awhile. So i decided it was time for a fresh install of factory image. I read the guide lines closely to fastbooting the latest factory image. Now im in a boot loop with the google unlock icon and the corruption screen . I tried going to stock recovery and factory wipe and still bootlooping. It's been doing this for awhile. Please help!
Click to expand...
Click to collapse
Don't panic yet. Try formatting both userdata and cache and then flash all the image files again. Any errors?
v12xke said:
Don't panic yet. Try formatting both userdata and cache and then flash all the image files again. Any errors?
Click to expand...
Click to collapse
Did both still the same bootloop
XMayhem2099 said:
Did both still the same bootloop
Click to expand...
Click to collapse
1. Ok, so format, not erase. Exactly which img files did you flash... and you did not get any errors back from fastboot, meaning it always finished cleanly? Have you tried using the flashall.bat?
2. Do you have any saved backups to restore (even of the old custom rom).
3. May sound funny, but have you tried NRT? Wug has a flash to stock/unroot routine with the option for a bootlooping case. It will also allow you to "point" it to the Google image you are using, but you may try allowing NRT to re-download and hash check it again just in case.
You should be able to recover from this. Don't try lock/unlock the bootloader. Leave it unlocked.
v12xke said:
1. Ok, so format, not erase. Exactly which img files did you flash... and you did not get any errors back from fastboot, meaning it always finished cleanly? Have you tried using the flashall.bat?
2. Do you have any saved backups to restore (even of the old custom rom).
3. May sound funny, but have you tried NRT? Wug has a flash to stock/unroot routine with the option for a bootlooping case. It will also allow you to "point" it to the Google image you are using, but you may try allowing NRT to re-download and hash check it again just in case.
You should be able to recover from this. Don't try lock/unlock the bootloader. Leave it unlocked.
Click to expand...
Click to collapse
Absolutely no errors from fastboot which is weird. I'll try the fashall.bat . Nope no custom backups, i tried nexus toolkit and the hashcheck matched still in bootloop. I haven't messed with the bootloader it's always been unlocked
XMayhem2099 said:
Absolutely no errors from fastboot which is weird. I'll try the fashall.bat . Nope no custom backups, i tried nexus toolkit and the hashcheck matched still in bootloop. I haven't messed with the bootloader it's always been unlocked
Click to expand...
Click to collapse
Gotcha. Which partitions did you flash, and in what order? If you look at the flashall.bat in a text editor, there is a check/requirement for a certain bootloader version level to for system (at least, and maybe more) ....anyway when manually flashing, bootloader.img should be the first, and then fastboot reboot into that bootloader before proceeding with all the other partitions. Look for any errors during the flashall batch run.
Edit: You may also want to re-run NRT, confirming the "soft brick mode" is ticked, and check the log window for ANYTHING out of the ordinary. Could also try NRT to revert back to 7.0 release.
v12xke said:
Gotcha. Which partitions did you flash, and in what order? If you look at the flashall.bat in a text editor, there is a check/requirement for a certain bootloader version level to for system (at least, and maybe more) ....anyway when manually flashing, bootloader.img should be the first, and then fastboot reboot into that bootloader before proceeding with all the other partitions. Look for any errors during the flashall batch run.
Edit: You may also want to re-run NRT, confirming the "soft brick mode" is ticked, and check the log window for ANYTHING out of the ordinary. Could also try NRT to revert back to 7.0 release.
Click to expand...
Click to collapse
I did the flash all command it ran successfully. Looks like im still getting a bootloop. I'll let it sit for an hour or so. If it doesn't run ill flash an older factory image. Thanks for the help, Ill let you know what happens.
Mine started doing the same thing last night, so far nothing I have tried has worked. Wireless provider is no help maybe Huawei will replace.
I'm active in a couple threads myself over this exact scenario. What the hell is going on with these phones?
Sent from my Nexus 6 using XDA-Developers mobile app
CyberpodS2 said:
I'm active in a couple threads myself over this exact scenario. What the hell is going on with these phones?
Click to expand...
Click to collapse
Huawei seems to have done a crappy job manufacturing them. Mine bootloops every time I update to a new ROM build, every time I switch ROMs and every time I try to restore a backup. Thankfully I've been able to get out of it every time so far but I've owned a lot of phones and none went into bootloops as often as the 6P. I've resigned myself to the fact that this phone is a time bomb and that it likely won't have a very long life. Would never buy another phone made by Huawei.
Problem google and hawuei (hardware) RMA
People facing bootloop of death.
1. How long have you been using your phone?
2. What's your EMMC and RAM name in bootloader?
3. What's your manufacturing date in bootloader?
4. Do you play games on your phone?
5. Does your phone get hot often?
fapste said:
People facing bootloop of death.
1. How long have you been using your phone?
2. What's your EMMC and RAM name in bootloader?
3. What's your manufacturing date in bootloader?
4. Do you play games on your phone?
5. Does your phone get hot often?
Click to expand...
Click to collapse
1. In general or when it happened? Averaged 4 hours SOT in 14-16 hours total.
2. 128 Toshiba
3. 3-29-2016
4. No
5. No
Same issue on a buddies 6p.. Fastboot commands go through the script with no errors but no results.. Still stuck in this bootloop. Has to be hardware causing this bootloop.
I'm having the same issue
Sent the device to Huawei and they say they'll repair it but I'm not sure if that's possible
My question is when they replace them, is the defect still waiting to pop up again??
Sent from my Nexus 6 using XDA-Developers Legacy app
Bought 2nd hand phone, managed to coax original sales receipt from Google store out of seller. Sent it in for an RMA and they swapped out my motherboard. Was also out of warranty by 2 months