Database Users

[Q] Unable to Flash Nexus 7

hello everyone..
In serious need of help here and hope someone can help..
Due to the massive battery drain issue I have been having, I tried to flash the original stock rom on my nexus 7 and
things have gone downhill really bad..
in the past, I flashed using this guide (http://forum.xda-developers.com/showthread.php?t=1907796)
without any problems but last night.. I encountered errors when trying to flash the bootloader
and radio IMG files.. neeedless to say when it comes to flashing the rom in, it came out with errors and my nexus remain OS-less
the errors when trying to flash the bootloader and radio are
"failed (command write failed (Invalid Argument))"
can anyone help me?
p.s :- if anyone can even suggest me a easier way to flash custom roms in and so forth, your suggestion will be most welcomed..
also, I did try wug's rootkit plus the nexus 7 toolkit or something, both came out errors too when too do any flashing in relating to
the bootloader or system.. thanks

Why were you trying to flash the bootloader? Were you trying to update to 4.18?

Username invalid said:
Why were you trying to flash the bootloader? Were you trying to update to 4.18?
Click to expand...
Click to collapse
actually, my bootloader boots fine, it shows tilapia 4.18.
so does this mean I dont have to flash it?
if I dont have to flash the bootloader, do I have to flash the radio?
sorry, kind of a noob in these things..

Anyway, is it normal for the bootloader flash attempt to fail?

hamiksu said:
Anyway, is it normal for the bootloader flash attempt to fail?
Click to expand...
Click to collapse
No, it's not normal for it to fail.
You really don't need to flash either unless one of them is screwed up or you are upgrading to a newer version. Bootloader flashes are risky anyway. To avoid flashing them, you can either remove code from the updater script or remove them from the factory image files entirely.

korockinout13 said:
No, it's not normal for it to fail.
You really don't need to flash either unless one of them is screwed up or you are upgrading to a newer version. Bootloader flashes are risky anyway. To avoid flashing them, you can either remove code from the updater script or remove them from the factory image files entirely.
Click to expand...
Click to collapse
hmm, ok..
then I will go back home and do the system flashing and try and post out the errors it stated there..
really hope to get my nexus back on line...

This is what I get when I tried to flash the image
Hope someone can guide me on what to do next.

hamiksu said:
This is what I get when I tried to flash the image
Hope someone can guide me on what to do next.
Click to expand...
Click to collapse
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock

ameinild said:
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock
Click to expand...
Click to collapse
it says my bootloader is already unlocked

hamiksu said:
it says my bootloader is already unlocked
Click to expand...
Click to collapse
Then it sounds like something happened to your system partition that should not have happened.
Are you sure the system image you're trying to flash is valid, do the md5 sums match?
How about flashing another system image?
Or flash a custom recovery, and install a new ROM from there?

ameinild said:
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock
Click to expand...
Click to collapse
ameinild said:
Then it sounds like something happened to your system partition that should not have happened. Sorry, can't help you there...
Click to expand...
Click to collapse
meaning my system partition is screwed?
anyone knows how to go around this problem?
p.s :- anyway ameinild, thanks for trying to help

hamiksu said:
p.s :- anyway ameinild, thanks for trying to help
Click to expand...
Click to collapse
I edited my post with some more suggestions to try first

ameinild said:
I edited my post with some more suggestions to try first
Click to expand...
Click to collapse
yup, the image i tried a few.. even tried stock rom image.
tried both nexus 7 toolkit
as well as wugs nexus root tool kit.
they all seem to encounter problems when trying to "push" the rom images in or something.
is there a way to like format the entire thing and install from scratch>?

hamiksu said:
is there a way to like format the entire thing and install from scratch>?
Click to expand...
Click to collapse
Sorry, I can't really find anything for the N7... Hope someone else can chime in.

ameinild said:
Sorry, I can't really find anything for the N7... Hope someone else can chime in.
Click to expand...
Click to collapse
Yea, I hope someone will pop in and be my guardian angel too..
Thanks again, Ameinild

tried to flash stock rom using wug's rootkit..
this is what happens...

hamiksu said:
tried to flash stock rom using wug's rootkit..
this is what happens...
Click to expand...
Click to collapse
As a rule, don't do anything with a toolkit that you don't know how to do yourself with the relevant fastboot or ADB commands. It has a nasty tendency of leaving you in a lurch.
I noticed that your last run of Wug's toolkit did claim to successfully flash your recovery. Have you been able to access it from the fastboot menu on the device? If so, that's a major step forward.
Perhaps most importantly (based on your mentioning of tilapia earlier), are you 100% certain that you are trying to flash the factory image for your model of the Nexus 7?

Rirere said:
As a rule, don't do anything with a toolkit that you don't know how to do yourself with the relevant fastboot or ADB commands. It has a nasty tendency of leaving you in a lurch.
I noticed that your last run of Wug's toolkit did claim to successfully flash your recovery. Have you been able to access it from the fastboot menu on the device? If so, that's a major step forward.
Perhaps most importantly (based on your mentioning of tilapia earlier), are you 100% certain that you are trying to flash the factory image for your model of the Nexus 7?
Click to expand...
Click to collapse
Yes, I am absolutely sure it is the image for my nexus 7.. which is 3g/wifi model, not just wifi only..
image file is downloaded using wug's rootkit too..
file name = nakasig-jdq39-factory-0798439d.tgz
as the snapshot shows.. it keeps showing failed when "sending system"
please tell me you have an idea on why it keeps failing there...
*crosses fingers*
p.s :- after that (numerous) wug's toolkit attempt to flash back stock rom, I tried booting to recovery and it shows the android on its back with a red exclamation mark on its open body chasis

I'm assuming you haven't tried this yet, if you have tried this just ignore.
1 - Download - http://techerrata.com/file/twrp2/grouper/openrecovery-twrp-2.6.0.0-grouper.img
2 - fastboot flash recovery openrecovery-twrp-2.6.0.0-grouper.img
If flashes fine:
Power off Nexus, Hold Volume down and Power on, keep holding power down until you get to recovery.
Then:
Either - Get a USB OTG and put a ROM on a USB Stick, go to "install" - "Use external storage" find the rom and flash it.
or
Plug in to PC whilst in recovery, - Mount Storage - Now the Nexus should pop up on PC, Drag ROM to Nexus. Unmount and then try to flash.
Let me know how you get on with this.
Regards.

hamiksu said:
Yes, I am absolutely sure it is the image for my nexus 7.. which is 3g/wifi model, not just wifi only..
image file is downloaded using wug's rootkit too..
file name = nakasig-jdq39-factory-0798439d.tgz
as the snapshot shows.. it keeps showing failed when "sending system"
please tell me you have an idea on why it keeps failing there...
*crosses fingers*
p.s :- after that (numerous) wug's toolkit attempt to flash back stock rom, I tried booting to recovery and it shows the android on its back with a red exclamation mark on its open body chasis
Click to expand...
Click to collapse
That's because you have stock recovery installed now and it's unable to verify that your device is in working order, hence the red mark. Find TWRP for your device, download the .img and try to flash it with fastboot flash recovery <path-to-recovery.img>. Since you can at least get into a recovery, it's possible you'll be able to use onboard recovery tools to see what state your internal partitions are in.
Until there's a little more info available, there's nothing I can say that's not pure conjecture.

Get softbrick with bootloop

Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.

In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app

nhatminhng said:
Hey guys, I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Fastboot format your partitions and use flash-all.bat with a stock Google image.

nhatminhng said:
Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.

MidnightDevil said:
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
jhs39 said:
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
Click to expand...
Click to collapse
v12xke said:
Fastboot format your partitions and use flash-all.bat with a stock Google image.
Click to expand...
Click to collapse
Thanks guys for helping. I fixed it.
I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...

nhatminhng said:
Thanks guys for helping. I fixed it. I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
Click to expand...
Click to collapse
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.

v12xke said:
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
Click to expand...
Click to collapse
Yes sir of course I read it. But I dont understand this step.
Open a terminal and navigate to the unzipped system image directory.
Click to expand...
Click to collapse
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.

nhatminhng said:
Yes sir of course I read it. But I dont understand this step.
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
Click to expand...
Click to collapse
Hi... Here's a pretty good detailed process on how to unlock/flash, etc...
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page549
Also, before using any toolkit, I suggest using manual commands and getting comfortable with it. At least, you learn exactly what command do what! Simply pressing a button in a program may result in a bricked device. Plus with command line you learn something. :good:

@nhatminhng How did you get your phone fixed? is your phone unlocked?

tjchuot287 said:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
Click to expand...
Click to collapse
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.

nhatminhng said:
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
Click to expand...
Click to collapse
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.

tjchuot287 said:
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
Click to expand...
Click to collapse
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app

CyberpodS2 said:
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes i can. I tried to sideload multiple version of OTA but all have failed.

tjchuot287 said:
Yes i can. I tried to sideload multiple version of OTA but all have failed.
Click to expand...
Click to collapse
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.

v12xke said:
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
Click to expand...
Click to collapse
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Sent from my Nexus 6P using XDA-Developers Legacy app

CyberpodS2 said:
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Click to expand...
Click to collapse
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.

v12xke said:
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
Click to expand...
Click to collapse
Now i have unlocked bootloader but the phone keep restart and stuck at logo again. i followed @Heisenberg thread but same result.

S-Off and got TWRP installed, stuck in bootloader after flashing.

So I just got a 2nd HTC 10 Verizon, I noticed that this phone got S-OFF already so I install TWRP and succeeded.
After that I try flashing others ROM I found here in this HTC 10 Verizon sub-forum but after flashing and reboot, my phone stuck at boot loader and can't get into the OS.
Can you guys please help me out here, it's getting frustrated flashing ROM after ROM and still get stuck like that.
Thanks in advance.

polepoe said:
So I just got a 2nd HTC 10 Verizon, I noticed that this phone got S-OFF already so I install TWRP and succeeded.
After that I try flashing others ROM I found here in this HTC 10 Verizon sub-forum but after flashing and reboot, my phone stuck at boot loader and can't get into the OS.
Can you guys please help me out here, it's getting frustrated flashing ROM after ROM and still get stuck like that.
Thanks in advance.
Click to expand...
Click to collapse
Is the bootloader unlocked? How did you flash the ROM? Have you tried one of the pure stock RUU's in these forums? Do you know which version of the firmware is on it? (These are a few questions which may help diagnose the problem).

hgoldner said:
Is the bootloader unlocked? How did you flash the ROM? Have you tried one of the pure stock RUU's in these forums? Do you know which version of the firmware is on it? (These are a few questions which may help diagnose the problem).
Click to expand...
Click to collapse
I think the boot loader is unlocked because I can access the boot loader screen. It said:
*** Software status: Offcial ***
*** LOCKED ***
*** S-OFF ***
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
REBOOT
REBOOT TO BOOTLOADER
BOOT TO DOWNLOAD MODE
BOOT TO RECOVERY MODE
DDR TEST
DDT TEST (LOOPING)
POWER DOWN
Click to expand...
Click to collapse
Well, I flash the custom ROM using TWRP (copy ROM into SD card, then install the ROM with TWRP).
I did flash the pure stock RUU in those forums and got it working, but I don't want to use it because I'm using the phone out of US, I have countered so many problems and little things that bugging me off.
This is the detail info I get in the boot info:
hTC download mode
*** LOCKED ***
htc_pmewl XC S-OFF
CID-VZW__01
MID-2PS650000
ColorID-WHT00
LK-1.0.0.0000
[email protected]
OpenDSP-v20.0.8996.00007_0809
OS-2.41.605.20
Jun 8 2017, 11:30:46(857212)
Click to expand...
Click to collapse

Wondering whether you have a firmware/ROM mismatch.

polepoe said:
I think the boot loader is unlocked because I can access the boot loader screen. It said:
Well, I flash the custom ROM using TWRP (copy ROM into SD card, then install the ROM with TWRP).
I did flash the pure stock RUU in those forums and got it working, but I don't want to use it because I'm using the phone out of US, I have countered so many problems and little things that bugging me off.
This is the detail info I get in the boot info:
Click to expand...
Click to collapse
what rom are you trying to flash?

aer0zer0 said:
what rom are you trying to flash?
Click to expand...
Click to collapse
Well I did flash PERFUME_WL 2.51.617.1 from this sub-forums.
And others popular Rom like I found in the htc 10 sub-forums

polepoe said:
Well I did flash PERFUME_WL 2.51.617.1 from this sub-forums.
And others popular Rom like I found in the htc 10 sub-forums
Click to expand...
Click to collapse
And they all do the same thing?

aer0zer0 said:
And they all do the same thing?
Click to expand...
Click to collapse
Yes, it stuck in boot loader after done flashing and restart.

polepoe said:
Yes, it stuck in boot loader after done flashing and restart.
Click to expand...
Click to collapse
Hmm, you may have already done this. Did you flash the 2.41.605.20 ruu in the development thread (it will wipe data, back up prior)? That will place all current firmware and stock rom (which reading sounds like you don't want).
Once it boots to at least the login screen, reboot to bootloader, flash twrp, format data (type yes) then reboot to twrp.
From here (making sure you have rom of choice on your SD viper, leedroid etc...) wipe everything but your external sd card, and install the rom. It should work from here...
I also gave you the scorched earth method of making it boot up.. This most definitely should work. I would be more than glad to help if I can.

aer0zer0 said:
Hmm, you may have already done this. Did you flash the 2.41.605.20 ruu in the development thread (it will wipe data, back up prior)? That will place all current firmware and stock rom (which reading sounds like you don't want).
Once it boots to at least the login screen, reboot to bootloader, flash twrp, format data (type yes) then reboot to twrp.
From here (making sure you have rom of choice on your SD viper, leedroid etc...) wipe everything but your external sd card, and install the rom. It should work from here...
I also gave you the scorched earth method of making it boot up.. This most definitely should work. I would be more than glad to help if I can.
Click to expand...
Click to collapse
Thanks, I will try this method, data is not a bit of a problem here so I will wipe that ****.
Let's see where this is going.
Edited: can you send me the link of the 2.41.605.20 ruu ROM, I'm getting a bit confused here.
Thanks.

polepoe said:
Thanks, I will try this method, data is not a bit of a problem here so I will wipe that ****.
Let's see where this is going.
Edited: can you send me the link of the 2.41.605.20 ruu ROM, I'm getting a bit confused here.
Thanks.
Click to expand...
Click to collapse
@aer0zer0's own thread (which you should have looked for first): https://forum.xda-developers.com/verizon-htc-10/how-to/verizon-official-ruu-1-19-605-9-t3377586

hgoldner said:
@aer0zer0's own thread (which you should have looked for first): https://forum.xda-developers.com/verizon-htc-10/how-to/verizon-official-ruu-1-19-605-9-t3377586
Click to expand...
Click to collapse
I did flash this RUU rom 1 week ago, so all I have to do now is the rest of the step right?

polepoe said:
I did flash this RUU rom 1 week ago, so all I have to do now is the rest of the step right?
Click to expand...
Click to collapse
Reread post #9 of this thread.

hgoldner said:
Reread post #9 of this thread.
Click to expand...
Click to collapse
TWRP flashing is done and it freeze at REBOOT phase so I have to hard restart the phone (with volume down + power for 11 seconds)
It still stuck in the boot loader.
This error message show up with the boot loader:
Code:
reboot reason: 0x776655aa
reboot message: KP: init PC:adsp_boot_store+0x2cc/0x368 LR:adsp_boot_store+0x2cc/0x368

polepoe said:
Thanks, I will try this method, data is not a bit of a problem here so I will wipe that ****.
Let's see where this is going.
Edited: can you send me the link of the 2.41.605.20 ruu ROM, I'm getting a bit confused here.
Thanks.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=961840155545582647
https://forum.xda-developers.com/verizon-htc-10/how-to/verizon-official-ruu-1-19-605-9-t3377586
There you go, flash via SD card or fastboot. Any instructions required you can get from there

aer0zer0 said:
https://www.androidfilehost.com/?fid=961840155545582647
https://forum.xda-developers.com/verizon-htc-10/how-to/verizon-official-ruu-1-19-605-9-t3377586
There you go, flash via SD card or fastboot. Any instructions required you can get from there
Click to expand...
Click to collapse
I did flash your rom 4 days ago, and got it working. Then I stop looking for any more ROM flashing stuff.
Now I retried and got the above error message.
So frustrated...

polepoe said:
I did flash your rom 4 days ago, and got it working. Then I stop looking for any more ROM flashing stuff.
Now I retried and got the above error message.
So frustrated...
Click to expand...
Click to collapse
What error message?

polepoe said:
I did flash your rom 4 days ago, and got it working. Then I stop looking for any more ROM flashing stuff.
Now I retried and got the above error message.
So frustrated...
Click to expand...
Click to collapse
Your reboot error appears to be a kernel panic.
What version of Twrp are you using to flash the custom rom/s?
I'm guessing an older one which isn't allowing Magisk to properly root the boot.img/kernel, therefor causing your kernel panics and inability to boot after flashing.
So,....again, what version of Twrp are you using?
You should be using the latest Official build.
Sent from my HTC6545LVW using Tapatalk

aer0zer0 said:
What error message?
Click to expand...
Click to collapse
This
reboot reason: 0x776655aa
reboot message: KP: init PC:adsp_boot_store+0x2cc/0x368 LR:adsp_boot_store+0x2cc/0x368
Click to expand...
Click to collapse
santod040 said:
Your reboot error appears to be a kernel panic.
What version of Twrp are you using to flash the custom rom/s?
I'm guessing an older one which isn't allowing Magisk to properly root the boot.img/kernel, therefor causing your kernel panics and inability to boot after flashing.
So,....again, what version of Twrp are you using?
You should be using the latest Official build.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
I'm using the latest TWRP at this link: https://twrp.me/devices/htc10.html

polepoe said:
This
I'm using the latest TWRP at this link: https://twrp.me/devices/htc10.html
Click to expand...
Click to collapse
And you've made sure to allow system modifications via Twrp swipe option when you first loaded it?
Check under Advanced > Mount and make sure system is not selected as Read Only.
Sent from my HTC6545LVW using Tapatalk

Unsure what I did

but ....... I am in twrp unable to reboot into my rom. When I click on Install I see all these folders with letters and numbers and what my original folders.
Can somone help me boot into my rom again?

ms.journie said:
but ....... I am in twrp unable to reboot into my rom. When I click on Install I see all these folders with letters and numbers and what my original folders.
Can somone help me boot into my rom again?
Click to expand...
Click to collapse
You will more than likely need to format data. This will cause you to loose everything. But that is what you are seeing, those folders, are your data. Just encrypted.
Also make sure you are on the latest version of TWRP. Sometimes the older unsupported version had encryption errors.

Omg this saddens me! So there's no way I am unable to at least retrieve my pictures?
Scott said:
You will more than likely need to format data. This will cause you to loose everything. But that is what you are seeing, those folders, are your data. Just encrypted.
Also make sure you are on the latest version of TWRP. Sometimes the older unsupported version had encryption errors.
Click to expand...
Click to collapse

Have u tested change boot partition ?

yup
J3zz said:
Have u tested change boot partition ?
Click to expand...
Click to collapse

ms.journie said:
yup
Click to expand...
Click to collapse
Simple test are:
- change boot partition
- reflash system
- Say goodbye too all
Got the same problem, Solved After reboot in twrp and enter the good decryption code

I'm right in the middle of reflashing. I am trying everything else before I do say goodbye to my pictures! :crying:
How did you figure out the decryption code?
J3zz said:
Simple test are:
- change boot partition
- reflash system
- Say goodbye too all
Got the same problem, Solved After reboot in twrp and enter the good decryption code
Click to expand...
Click to collapse

ms.journie said:
I'm right in the middle of reflashing. I am trying everything else before I do say goodbye to my pictures! :crying:
How did you figure out the decryption code?
Click to expand...
Click to collapse
First time entering in twrp after flashing update, I did not get folder to flash magisk, did a reboot and get it, just a bad encryption code I think
Did u flash rom or anything else before getting this problem ?

Yup, I sure did! 4am couldn't sleep so I thought I would finally put a fingerprint mod on; which I have done this before with no issues. For the life of me, I don't remember which mod I tried to install thru Magisk.
My phone is currently stuck on "Phone is starting"
I also think it's time to look into some sort of automatic back up service..... Got any ideas?
J3zz said:
First time entering in twrp after flashing update, I did not get folder to flash magisk, did a reboot and get it, just a bad encryption code I think
Did u flash rom or anything else before getting this problem ?
Click to expand...
Click to collapse

ms.journie said:
Yup, I sure did! 4am couldn't sleep so I thought I would finally put a fingerprint mod on; which I have done this before with no issues. For the life of me, I don't remember which mod I tried to install thru Magisk.
My phone is currently stuck on "Phone is starting"
I also think it's time to look into some sort of automatic back up service..... Got any ideas?
Click to expand...
Click to collapse
Use msmdownloadtool, have u tried using magisk uninstall in twrp with zip file ? Then boot and uninstall the "****in" fantastic module... maybe it works

I did try to uninstall Magisk in twrp using adb shell. I never had any luck with that msmdownloadtool and not only that it relocks your bootloader.
I usually go this route [ROM][STOCK][FASTBOOT][OP6T] Stock Fastboot ROMs for OnePlus 6T https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Thanks for trying to me!
J3zz said:
Use msmdownloadtool, have u tried using magisk uninstall in twrp with zip file ?
Click to expand...
Click to collapse

ms.journie said:
I did try to uninstall Magisk in twrp using adb shell. I never had any luck with that msmdownloadtool and not only that it relocks your bootloader.
I usually go this route [ROM][STOCK][FASTBOOT][OP6T] Stock Fastboot ROMs for OnePlus 6T https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Thanks for trying to me!
Click to expand...
Click to collapse
Good luck !!

I saw this happen when I used the official TWRP app.
It went away when I used this TWRP. Hope that helps.

I'm glad you already know not to use the MSM tool. Too many people jump straight to this.....
You just need to boot the correct recovery and your data will decrypt, and you will be able to back it up to a PC, then you can reload your ROM via TWRP or Fastboot to get the phone bootable again. So now it's a question of what ROM were you running before. Do you need a recovery with the latest security patch or something older? What TWRP are you running. Try 3.3.1-6 psychen6 linked too first. Boot that image from Fastboot. See if your password/pin will work to decrypt your data.

Question [Help] Bootloader loop | No access to EDL

I'd like to begin with a little backstory, it consists of me unrooting the phone via magisk android app and re-flashing the bootloader with a non patched .img of the same version. Afterwards I've decided to lock the bootloader, and that's where the problem struck me.
I've tried all unbricking methods I could find, I can't flash product.img as well as odm.img. I tried switching partitions and re-doing the process, however, nothing works...
I came to a conclusion that the only way for me to fix it was the EDL Unbricking tool, however I cannot put the phone into it. I used the replacement fastboot.exe from the forum as well as a separate EDL Reboot v2 .cmd script but the phone just reboots to the bootloader.
P.S: I have re-flashed the super partition multiple times, flashed boot.img and vector_boot.img in order to enter recovery. But, ironically enough, the recovery mode was even more helpless than I am.
These are the methods I've tried:
[GUIDE][HowTo] Unlock and root Nothing Phone (1)
ANNOUNCEMENT: I'M STOPPING THE FOLLOW UP AND UPDATE OF THIS TOPIC TODAY, IF SOMEONE WANTS TO TAKE OVER, CONTACT THE MODERATOR IN THIS LINK. THE TOPIC REMAINS AS IT IS AND WILL NOT BE UPDATED ANYMORE (BY ME ANYWAY!) GOOD CONTINUATION TO ALL...
forum.xda-developers.com
How to unbrick Nothing Phone 1 fastboot bootloop
Welcome to this unbrick tutorial NB: I state immediately that i'm not responsible for any damage that occurs on your phone. This process worked for my Nothing Phone on 1.1.3, but maybe not on yours. I do not suggest following this tutorial if...
forum.xda-developers.com

How are you even able to flash partitions if your bootloader is locked?

TheNewHEROBRINE said:
How are you even able to flash partitions if your bootloader is locked?
Click to expand...
Click to collapse
I have unlocked it after the bootloader loop took place

aChrome said:
I have unlocked it after the bootloader loop took place
Click to expand...
Click to collapse
ah, I didn't know this was possible. Can you tell on what version you were when the problem happened and what versions have you tried flashing so far?

TheNewHEROBRINE said:
ah, I didn't know this was possible. Can you tell on what version you were when the problem happened and what versions have you tried flashing so far?
Click to expand...
Click to collapse
I was on patched 1.5.3, I tried flashing the stock 1.5.3 and thats when the problem happened. After that I tried re-flashing each and every image using 1.1.7, since its the latest Global Full OTA which isnt incremental and can be disassembled using the payload dumper

aChrome said:
I was on patched 1.5.3, I tried flashing the stock 1.5.3 and thats when the problem happened. After that I tried re-flashing each and every image using 1.1.7, since its the latest Global Full OTA which isnt incremental and can be disassembled using the payload dumper
Click to expand...
Click to collapse
Try flashing 1.5.3 hotfix from
[ROM][Restore][Unbrick] Nothing OS v1.5.4 Global/EEA Fastboot ROM(Full ROM) & boot.img & QFIL ROM (EDL)
Update! : 2023/05/05 20:00 (UTC+9:00) Fastboot ROM and boot.img for NothingPhone(1) are now available. v1.5.4 is available. Sorry for my poor English, I'm Japanese... News: The DSU has been restored in this version. It seems to be usable as long...
forum.xda-developers.com

TheNewHEROBRINE said:
Try flashing 1.5.3 hotfix from
[ROM][Restore][Unbrick] Nothing OS v1.5.4 Global/EEA Fastboot ROM(Full ROM) & boot.img & QFIL ROM (EDL)
Update! : 2023/05/05 20:00 (UTC+9:00) Fastboot ROM and boot.img for NothingPhone(1) are now available. v1.5.4 is available. Sorry for my poor English, I'm Japanese... News: The DSU has been restored in this version. It seems to be usable as long...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks, I managed to flash partition b successfully. However, the issue still persists.

Can you send a screenshot of the output in the cmd?

TheNewHEROBRINE said:
Can you send a screenshot of the output in the cmd?
Click to expand...
Click to collapse
Wtf, I just re-flashed it with the same OTA and it booted up. Man you are a magician... Also, am I safe to lock the bootloader now?

aChrome said:
Wtf, I just re-flashed it with the same OTA and it booted up. Man you are a magician... Also, am I safe to lock the bootloader now?
Click to expand...
Click to collapse
You should, but the only way to find out is to try.

TheNewHEROBRINE said:
You should, but the only way to find out is to try.
Click to expand...
Click to collapse
Alright, it worked. Thanks a lot man. You rescued me.

aChrome said:
Alright, it worked. Thanks a lot man. You rescued me.
Click to expand...
Click to collapse
You're welcome