Related
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.
Hi.
So, a quick overview. My laptop suddenly stopped recognizing my Nexus 10 while in the midst of transferring some files over. I decided to finally root. I used the cf-autoroot tool for Nexus 10 Lollipop. The last step of the rooting involves an automatic reboot. Now my Nexus 10 is stuck in the boot.
Details:
theunlockr (DOT) com/2014/11/22/how-to-root-the-nexus-10-on-android-5-0/
That is the guide I used, including the linked cf-autoroot. Sorry for the formatting, I don't have enough posts to post links.
My Nexus 10 is stuck on the step where it shows the four circles moving around. Not sure if that's important.
The cf-autoroot appeared to work successfully except for a piece in the middle that reads:
Same problem. The procedure seemed to go well, except maybe the mounting failed? It says:
Mounting...
- System
- Cache
--- Fail
I tried using the tool several times on two computers, and did my best to update drivers directly from Google (it appears the drivers are all up to date).
My Nexus 10 was on Lollipop. As far as I know, it was up to date, so I think that means it was on 5.0.1
Help?
Hello autoroot is no longer required. Supersu from recovery is enough.
You could just reflash original kernel
Does
Fastboot boot boot. Img works? It boots on the given image without flaging. The boot image is located in the archive to update
Sent from my Xiaomi MI2s
Khaon said:
Hello autoroot is no longer required. Supersu from recovery is enough.
You could just reflash original kernel
Does
Fastboot boot boot. Img works? It boots on the given image without flaging. The boot image is located in the archive to update
Sent from my Xiaomi MI2s
Click to expand...
Click to collapse
This is what I have come here to find out. I'm receiving my Nexus 10 in the mail today. I'm familiar with Nexus devices so I just assume everything is the same with the Nexus 10. But I know since Lollipop came out, there have been changes to how to root on certain devices. Are you saying that everything has been fixed to where I can just install the latest TWRP and flash the latest beta SuperSU on stock ROM and I will be good? If so, then it's the same as my Nexus 5 so I shouldn't have any issues.
jsgraphicart said:
This is what I have come here to find out. I'm receiving my Nexus 10 in the mail today. I'm familiar with Nexus devices so I just assume everything is the same with the Nexus 10. But I know since Lollipop came out, there have been changes to how to root on certain devices. Are you saying that everything has been fixed to where I can just install the latest TWRP and flash the latest beta SuperSU on stock ROM and I will be good? If so, then it's the same as my Nexus 5 so I shouldn't have any issues.
Click to expand...
Click to collapse
Yep, just flash once SU through twrp(in order to get the su binary in the system partition) and then you can use play store to update the binary and the program itself.
CM12 has built in su and nighties are official now.
Khaon said:
Yep, just flash once SU through twrp(in order to get the su binary in the system partition) and then you can use play store to update the binary and the program itself.
CM12 has built in su and nighties are official now.
Click to expand...
Click to collapse
Thanks. I just wanted to double check before I went jumping into it. I'm looking forward to tinkering with it when I get home from work.
Khaon said:
Yep, just flash once SU through twrp(in order to get the su binary in the system partition) and then you can use play store to update the binary and the program itself.
CM12 has built in su and nighties are official now.
Click to expand...
Click to collapse
So I attempted to do all this when I got home yesterday. I found that after unlocking the bootloader, I got stuck in a boot loop. After doing some research I found that this has been an issue with the Nexus 10. Is there a reason for this? I read that locking the bootloader again fixed it, which it did. But I didn't want it locked. So I researched more and found that a a factory reset in stock recovery would fix it. I still had a boot loop. I managed to somehow get everything straightened out with a series of random tries and after installing TWRP and rooting and, again, getting the boot loop I attempted to go back into recovery but accidentally did a simple restart. For some reason, it booted right up after the restart so now I think everything is fine. But why is the Nexus 10 being so difficult? I never had these issues with other Nexus devices. Maybe some of this info will help the OP as well.
Hm unlocking the bootloader does erase whole content but I guess you are already aware of that.
How long did you wait? First boot can take ages much longer than before.
I never had any issues and I have my bootloader unlocked
Khaon said:
Hm unlocking the bootloader does erase whole content but I guess you are already aware of that.
How long did you wait? First boot can take ages much longer than before.
I never had any issues and I have my bootloader unlocked
Click to expand...
Click to collapse
I let it sit for a while. I own a Nexus 5 and I'm familiar with the long first boot. It just seemed like a long time to me. I thought maybe since it was a two year old device that it may take longer. The device is new to me so I'm not familiar with boot times and all that are specific to it yet. But compared to the boot time after I relocked the boot loader, there was a big difference. After re-locking, it booted up in about a minute or two. Flashing TWRP even seemed to mess up some stuff. I think it may have deleted the OS or something. It couldn't mount anything afterwards and even selecting reboot boot loader gave me the prompt that there was no OS installed. So I flashed the system.img, cache.img and userdata.img manually. Which seemed to fix it. And even after I got everything straightened out, it boot up in about a minute or two again. The only time I had issues with getting it to boot is unlocking the boot loader coming from complete stock.
nexus 10 stuck on bootload up
jsgraphicart said:
I let it sit for a while. I own a Nexus 5 and I'm familiar with the long first boot. It just seemed like a long time to me. I thought maybe since it was a two year old device that it may take longer. The device is new to me so I'm not familiar with boot times and all that are specific to it yet. But compared to the boot time after I relocked the boot loader, there was a big difference. After re-locking, it booted up in about a minute or two. Flashing TWRP even seemed to mess up some stuff. I think it may have deleted the OS or something. It couldn't mount anything afterwards and even selecting reboot boot loader gave me the prompt that there was no OS installed. So I flashed the system.img, cache.img and userdata.img manually. Which seemed to fix it. And even after I got everything straightened out, it boot up in about a minute or two again. The only time I had issues with getting it to boot is unlocking the boot loader coming from complete stock.
Click to expand...
Click to collapse
I getting the exact same thing after following instructions to root the machine
I'm not the most experience but I did my nexus 4 & 7 on 4.4.4. now on this 5.0 it seemed a lot hard this time around
I left it on boot load up screen for 3hrs and its still going round? what do I do?
Quick update: I press power +vol up + down and it comes up with the screen saving its unlocked. but the recovery mode just comes up with a android and red exclamation mark.
please help?
regards
Tom
tomistrouble said:
I getting the exact same thing after following instructions to root the machine
I'm not the most experience but I did my nexus 4 & 7 on 4.4.4. now on this 5.0 it seemed a lot hard this time around
I left it on boot load up screen for 3hrs and its still going round? what do I do?
Quick update: I press power +vol up + down and it comes up with the screen saving its unlocked. but the recovery mode just comes up with a android and red exclamation mark.
please help?
regards
Tom
Click to expand...
Click to collapse
Once you get in recovery mode with the android and the red explanation mark, hit all three buttons (Vol up , down and power) until (It can be tricky keep trying) you get a menu. Then use the volume buttons to select "Wipe Data/Factory rest" let it do its thing and reboot. Allow it to boot for 5-10 minutes.
Good luck
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
So I bought one of those onn tablets from Walmart, went to flash phussons quack gsi for Q and whilst the system flashed fine via fastboot it refuses to actually boot (bootloop on the onn screen) I can't get into recovery either. Fastboot -w fails because it can't create an image for the userdata partition (when I go to manually format userdata it says the partition table doesn't exist.) I'm able to flash to the boot, recovery and system partitions no issue.
Android 10 roms I have tried do not work... I have the onn 8 and on 10 w/o keyboard.
Also I had no issues flashing android 9 roms on the 8 but on the 10 all roms have issues with no sound from the speakers but sound through wired & bluetooth headsets some roms have graphical issues some have bluetooth... but all seem to have sound problems... and some will not boot past boot animation.
Roms I got too boot were phh's 9, beast rom, bootleggers, bliss and liquid remix. Liquid remix runs the best so far... but on the 8 not the 10
I also tried the /e/ os gsi Wich is based on pie that didn't boot either, I'll try liquid remix
went to format system before flashing and heres the output i got
Invalid erase-block-size 0: must be a power of 2 and at least 4096.
Invalid logical-block-size 512: must be a power of 2 and at least 4096.
mke2fs 1.44.5 (15-Dec-2018)
/tmp/TemporaryFile-wirxYd: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for system
same type of error i was talking about with my userdata partition
What was your method for flashing?
Unlocked the bootloader with fastboot flashing unlock
Fastboot -u flash system /name/and/location/of/gsi
I had erased my system partitions before i flashed the gsi the first time and I think that's where I screwed up
If I could get into the recovery I'd just adb sideload the ota and start again
Be careful you don't lose your battery charge, it doesn't charge in fastboot, so it can be easy to get into a difficult situation with a battery below 30%
I can get you stock system, boot and recovery images for your model later this evening.
NFSP G35 said:
Be careful you don't lose your battery charge, it doesn't charge in fastboot, so it can be easy to get into a difficult situation with a battery below 30%
I can get you stock system, boot and recovery images for your model later this evening.
Click to expand...
Click to collapse
Alright, thank you and I've already been attempting to use your back up images of stock off xda to try and restore it is there anything special I need to do or are you going to get like a flashall file made?
I am going to get the system and vendor partitions from the ONA19TB007 uploaded (currently only have boot and recovery)
Once those are up, you should be able to flash them via fastboot.
NFSP G35 said:
I am going to get the system and vendor partitions from the ONA19TB007 uploaded (currently only have boot and recovery)
Once those are up, you should be able to flash them via fastboot.
Click to expand...
Click to collapse
Hey, any updates it's been a few hours and I'd love to get the tablet fixed tonight
kanaan360 said:
Hey, any updates it's been a few hours and I'd love to get the tablet fixed tonight
Click to expand...
Click to collapse
Hey, really sorry about that. An emergency came up yesterday.
I'll get that uploaded whenever I can. Sorry again.
NFSP G35 said:
Hey, really sorry about that. An emergency came up yesterday.
I'll get that uploaded whenever I can. Sorry again.
Click to expand...
Click to collapse
You're good man, thanks so much again.
Images from the The May update are here (still waiting on the system image to finish uploading)
https://www.androidfilehost.com/?w=files&flid=301680
NFSP G35 said:
Images from the The May update are here (still waiting on the system image to finish uploading)
https://www.androidfilehost.com/?w=files&flid=301680
Click to expand...
Click to collapse
Awesome thanks, any word on the system image?
kanaan360 said:
Awesome thanks, any word on the system image?
Click to expand...
Click to collapse
I don't know if it's AFH or my internet connection... It's been uploading over 24hrs now... I'm stymied.
89% complete though. Sorry it's taking so long
Finally finished uploading!
https://forum.xda-developers.com/wa...eral/stock-stock-backups-images-otas-t3998227
NFSP G35 said:
I don't know if it's AFH or my internet connection... It's been uploading over 24hrs now... I'm stymied.
89% complete though. Sorry it's taking so long
Click to expand...
Click to collapse
The speed is by server. Quebec seems to be fast for me most the time. If there is It's there decryption on twrp? I have been happy with stock personally but if you need any more images let me know. Also let me what way you want them. I can flash then use twrp or use dd commands but I would need to know what dd you wanted. I don't have sptools installed right now though. I could probably get it working on my Mac os if needed be though since I have many of the Linux libraries/services. Last option would take the longest since it's actually learning new cli commands. I am kind of a slacker but if someone has a bricked device then... I want to help.
Vortell said:
The speed is by server. Quebec seems to be fast for me most the time. If there is It's there decryption on twrp? I have been happy with stock personally but if you need any more images let me know. Also let me what way you want them. I can flash then use twrp or use dd commands but I would need to know what dd you wanted. I don't have sptools installed right now though. I could probably get it working on my Mac os if needed be though since I have many of the Linux libraries/services. Last option would take the longest since it's actually learning new cli commands. I am kind of a slacker but if someone has a bricked device then... I want to help.
Click to expand...
Click to collapse
Thanks, but the files finally finished uploading in the small hours last night.
I figured out its my stupid internet connection at home... apparently, while my download speed is great, my upload speed could be outpaced by a burro carrying floppy disks
Took my laptop to work and everything has been uploading much faster.
@kanaan360, I have images for you at:
https://www.androidfilehost.com/?w=files&flid=301679 or https://forum.xda-developers.com/wa...eral/stock-stock-backups-images-otas-t3998227
The May images are up, October ones will be there in a few minutes.
NFSP G35 said:
Be careful you don't lose your battery charge, it doesn't charge in fastboot, so it can be easy to get into a difficult situation with a battery below 30%
I can get you stock system, boot and recovery images for your model later this evening.
Click to expand...
Click to collapse
so i ran into that situation what do i do. is it bricked beyond repair?
nevor70168 said:
so i ran into that situation what do i do. is it bricked beyond repair?
Click to expand...
Click to collapse
Not hard bricked by a long shot.
Several of us have recovered from this scenario.
Somewhere around here I posted a link to a xda thread with a similar situation that can happen with some HTC phones. Basically, you build a script to constantly reboot it into fastboot.
NFSP G35 said:
Not hard bricked by a long shot.
Several of us have recovered from this scenario.
Somewhere around here I posted a link to a xda thread with a similar situation that can happen with some HTC phones. Basically, you build a script to constantly reboot it into fastboot.
Click to expand...
Click to collapse
everytime i try to boot into fastboot mode it reboots it doesnt go into fastboot mode, is this because the battery life is low and does not want to boot into fastboot mode? Also how would i charge my device it keeps flashing on the low battery icon. any help would be appreciated also a link to your post would help me greatly.
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