Question [SOLVED] Nothing Phone (1) Keeps Rebooting After Persist Partition is Erased - Nothing Phone 1

I see the splash screen with NOTHING logo and "Powered by Android" at the bottom. After 15 seconds or so, the phone reboots.
This started happening after I erased the persist partition using fastboot.
A few things I tried which didn't work:
Sideloading a full 1.1.4 hotfix zip file using adb.
Factory resetting from the recovery and fastboot.
Format persist partition as ext4, "fastboot format:ext4 persist".
I don't see persist.img included in the firmware release. Can anyone extract the persist partition from their Nothing Phone (1)? I can flash persist.img and hopefully get the phone to boot properly.
Or if it's possible to enable diag mode from the recovery image. I don't know if it's possible to set sys.usb.config to diag,adb on recovery. I took a qcn backup beforehand. I can just restore that.
Thanks to @ayed78 providing persist.img from their device, I was able to boot into Android. I restored the qcn backup to restore the IMEIs and therefore restore cellular network connectivity.

arinc9 said:
I see the splash screen with NOTHING logo and "Powered by Android" at the bottom. After 15 seconds or so, the phone reboots.
This started happening after I erased the persist partition using fastboot.
A few things I tried which didn't work:
Sideloading a full 1.1.4 hotfix zip file using adb.
Factory resetting from the recovery and fastboot.
Format persist partition as ext4, "fastboot format:ext4 persist".
I don't see persist.img included in the firmware release. Can anyone extract the persist partition from their Nothing Phone (1)? I can flash persist.img and hopefully get the phone to boot properly.
Or if it's possible to enable diag mode from the recovery image. I don't know if it's possible to set sys.usb.config to diag,adb on recovery. I took a qcn backup beforehand. I can just restore that.
Click to expand...
Click to collapse
I will make a tutorial about brick fix tonight wich worked for me. Hope it'll work for yours

AntoXik72 said:
I will make a tutorial about brick fix tonight wich worked for me. Hope it'll work for yours
Click to expand...
Click to collapse
Great! Keep me posted.

Posting a short version of my reply here, from https://forum.xda-developers.com/t/how-to-unbrick-nothing-phone-1-fastboot-bootloop.4501439/
I've tried this on my Nothing Phone (1) EEA version which bootloops. It doesn't work. Whilst booting from the A slot, there's the 15 seconds of splash screen, then it reboots, same as before.
Flashing to A slot was completed without any errors. I don't think this super image includes the persist partition. My phone started bootlooping after I erased the persist partition. Can anyone upload their persist partition for the global or EEA version?

Related

[Q] Can't get back to stock

I'm having trouble finding a way to fix this:
I have the same problem as this guy
http://forum.xda-developers.com/show....php?t=2704519
I applied a one click root+twrp. Something went wrong and soft bricked my phone.
It boot loops into twrp but twrp's gui is unresponsive. Have got it to factory reset in twrp get but i get "can't mount /data" in red text. I can get into download mode. TOT flash to stock method kind of works. It runs through the process very fast and flash tool returns:
skip system partition
Skip aboot Partition
Skip rpm Partition
Skip boot Partition
Skip tz Partition
Skip misc Partition
Skip persist Partition
skip cache partition
est... for rest of partitions
Finishes the process and phone reboots back into boot loop to broken twrp
the tot and dll files are fine cuz i used them to flash it earlier when i got stuck
I can't get the KDZ method to work. Does anyone know what's wrong
Is there a another way to replace the partitions manually? maybe a linux way? I'm still very noob, hitting a very hard learning curve
KillerMOth said:
I'm having trouble finding a way to fix this:
I have the same problem as this guy
http://forum.xda-developers.com/show....php?t=2704519
I applied a one click root+twrp. Something went wrong and soft bricked my phone.
It boot loops into twrp but twrp's gui is unresponsive. Have got it to factory reset in twrp get but i get "can't mount /data" in red text. I can get into download mode. TOT flash to stock method kind of works. It runs through the process very fast and flash tool returns:
skip system partition
Skip aboot Partition
Skip rpm Partition
Skip boot Partition
Skip tz Partition
Skip misc Partition
Skip persist Partition
skip cache partition
est... for rest of partitions
Finishes the process and phone reboots back into boot loop to broken twrp
the tot and dll files are fine cuz i used them to flash it earlier when i got stuck
I can't get the KDZ method to work. Does anyone know what's wrong
Is there a another way to replace the partitions manually? maybe a linux way? I'm still very noob, hitting a very hard learning curve
Click to expand...
Click to collapse
I don't know how to help you, i can only fix a bricked phone if I have TWRP working..........
But here's a tip, once you fix the phone use IOroot for rooting and AutoRec for TWRP, there is no way you can brick it that way
KillerMOth said:
I'm having trouble finding a way to fix this:
I have the same problem as this guy
http://forum.xda-developers.com/show....php?t=2704519
I applied a one click root+twrp. Something went wrong and soft bricked my phone.
Is there a another way to replace the partitions manually? maybe a linux way? I'm still very noob, hitting a very hard learning curve
Click to expand...
Click to collapse
If you are able to boot into FASTBOOT you may try to manually flash partitions...
4Freedom said:
If you are able to boot into FASTBOOT you may try to manually flash partitions...
Click to expand...
Click to collapse
Yes, I saw few forum posts on doing that.
How can i get into fastboot? Is this possible manually??
KillerMOth said:
Yes, I saw few forum posts on doing that.
How can i get into fastboot? Is this possible manually??
Click to expand...
Click to collapse
Make sure you have installed the last version of d802 driver(search on lg website)
Install "minimal adb and fastboot" search on google or on xda than open windows cmd and type
Code:
cd FOLDER
With folder i mean the path where you have installed adb
Now you can type
Code:
adb devices
If it show something like a number or something that identify your phone
You can type
Code:
adb reboot bootloader
Your phone will be into fastboot mode

Help help help with a hard bricked 6P

Hello guys,
I had my phone rooted with latest twrp. I flashed stock+ rom with Franco Kernel 25r and the A.R.I.S.E file for better sound. I've done the same set up minus the ARISE file and never had an issue.
well to my luck it kept bootlooping and I wasn't able to get back into my custom recovery. When I got home and got my hands on a pc I did a factory reset by manually flashing stock google img . I even used a couple tools since I ran out of ideas and still no luck.
I'm able to do anything through fastboot but I can't seem to get into my recovery at all.
Any ideas or tips of where I should go next?
Not a Hardbrick
As long as you can get to the bootloader mode, you haven't hard bricked your device. Hardbricking is a point where you cant boot your device and in to bootloader so there is no way to flash your device to a useable state.
Now as you can boot to the bootloader, just fastboot boot twrp.img and if you have a factory image zip, copy it in your device internal storage and flash it. Its that simple, provided you are already using an unencrypted boot.img in your current setup. Or else the next step is to flash an decrypted boot.img(you will loose all your userdata and internal storage data.). There are ways to mount the the encrypted filesystem if you are using a pin or password combo with your fingerprint. But without it its a bit more trickier so just for ease and if you dont have any inseparable data in your device now just flash a decrypted boot.img and then you can easily mount your internal storage to your pc and copy the factory image and the rest you already know..
At this point, I'd recommend a full reset.
Flash all the images in the latest Android M factory image (don't flash DP5 or similar N based ROMs): Recovery, Boot, System, Bootloader, Radio, everything.
Once you get stabilized and back into a working phone, then start rooting and messing around with kernels and what not.
To be completely honest, I've flashed nearly every ROM for the 6p, as well as my other Nexus devices, Galaxy phones, Sony phones, and no-name brands and none of those ultra modified kernels did any noticeable change. I tried the F2FS, NTFS, etc file system changes, tweaks to the governors and IO's, all of that, and found the stock kernel was the best. If a kernel with a different IO Scheduler worked even 10% better than the current implementation, and was just as stable, don't you think the Google/Android Engineers would've pushed that to live?
Currently running Pure Nexus July 23rd Update, everything stock that comes with it, Systemless Root/XPosed, and Viper4Android and have never had a performance or stability issue. I'd recommend you do the same.
leninmon said:
As long as you can get to the bootloader mode, you haven't hard bricked your device. Hardbricking is a point where you cant boot your device and in to bootloader so there is no way to flash your device to a useable state.
Now as you can boot to the bootloader, just fastboot boot twrp.img and if you have a factory image zip, copy it in your device internal storage and flash it. Its that simple, provided you are already using an unencrypted boot.img in your current setup. Or else the next step is to flash an decrypted boot.img(you will loose all your userdata and internal storage data.). There are ways to mount the the encrypted filesystem if you are using a pin or password combo with your fingerprint. But without it its a bit more trickier so just for ease and if you dont have any inseparable data in your device now just flash a decrypted boot.img and then you can easily mount your internal storage to your pc and copy the factory image and the rest you already know..
Click to expand...
Click to collapse
First of all thank you for the response.
I've tried flashing the most current twrp and it seems to go through fine on fast boot but when I actually try to get into recovery from the device it will boot loop and just keep doing that.
How can I get into the phones storage through fastboot?
Where can I get the factory zip?
it feels as if everything seems to go good through fastboot but when I actually try to boot the phone nothing seems to work.
Wiltron said:
At this point, I'd recommend a full reset.
Flash all the images in the latest Android M factory image (don't flash DP5 or similar N based ROMs): Recovery, Boot, System, Bootloader, Radio, everything.
Once you get stabilized and back into a working phone, then start rooting and messing around with kernels and what not.
To be completely honest, I've flashed nearly every ROM for the 6p, as well as my other Nexus devices, Galaxy phones, Sony phones, and no-name brands and none of those ultra modified kernels did any noticeable change. I tried the F2FS, NTFS, etc file system changes, tweaks to the governors and IO's, all of that, and found the stock kernel was the best. If a kernel with a different IO Scheduler worked even 10% better than the current implementation, and was just as stable, don't you think the Google/Android Engineers would've pushed that to live?
Currently running Pure Nexus July 23rd Update, everything stock that comes with it, Systemless Root/XPosed, and Viper4Android and have never had a performance or stability issue. I'd recommend you do the same.
Click to expand...
Click to collapse
Thanks for the reply.
I've done the manual flashing already and flashed everything single item the most current factory image. Everything seemed to have gone through okay but when I rebooted the phone it was back to 0.
I'm actually considering getting rid of the phone now since it is my daily =/
Format each partition before flashing.
fastboot format <partition>
wait until it's done, then
fastboot flash <partition> <image>
Some partitions can't be formatted, which there are ways around, but try this first.
Just get to bootloader mode and try booting the twrp.img
fastboot boot twrp.img
From the twrp ui, go to advanced wipe and format your storage.
To mount the internal storage on your PC, enable mtp from twrp screen.
If U are using a decrypted boot.img, it will easily mount ur internal storage. Or try flashing a decrypted boot.img
fastboot flash boot boot.img
Then try the above again..
leninmon said:
Just get to bootloader mode and try booting the twrp.img
fastboot boot twrp.img
From the twrp ui, go to advanced wipe and format your storage.
To mount the internal storage on your PC, enable mtp from twrp screen.
If U are using a decrypted boot.img, it will easily mount ur internal storage. Or try flashing a decrypted boot.img
fastboot flash boot boot.img
Then try the above again..
Click to expand...
Click to collapse
I flashed the twrp.img and it went through successfully at least on the computer it did but when the phone actually tries to get into recovery (twrp) it will start to boot loop and keep on doing that. I tried both an encrypted and decrypted boot img but it still made no difference.
I'm really going crazy over this
Wiltron said:
Format each partition before flashing.
fastboot format <partition>
wait until it's done, then
fastboot flash <partition> <image>
Some partitions can't be formatted, which there are ways around, but try this first.
Click to expand...
Click to collapse
I just tried this and had no luck =/....the phone wont get past the google boot screen
You need to explain more on what you actually tried here.
Just download the latest factory image and try to flash the latest bootloader using fastboot.
Then boot to the bootloader and try formating the device. Not wiping
Then you have to
fastboot boot twrp.img
I believe you have only tried wiping not formating. I faced similar issue before. But once I flashed a decrypted boot.img, it cleared the user data and then I was able to get to twrp.
Maybe your twrp img is corrupted if this didn't work.
leninmon said:
You need to explain more on what you actually tried here.
Just download the latest factory image and try to flash the latest bootloader using fastboot.
Then boot to the bootloader and try formating the device. Not wiping
Then you have to
fastboot boot twrp.img
I believe you have only tried wiping not formating. I faced similar issue before. But once I flashed a decrypted boot.img, it cleared the user data and then I was able to get to twrp.
Maybe your twrp img is corrupted if this didn't work.
Click to expand...
Click to collapse
i just flashed the latest bootloader from the most recent factory image and i did the command format user data and then tried the fastboot boot twrp and the phone will then try to get into recovery, the google logo comes up lasts a couple seconds and boot loops all over to where is says my phone cant be check for corruption
By now i should have been able to get into recovery and it wont go through
edgarted said:
i just flashed the latest bootloader from the most recent factory image and i did the command format user data and then tried the fastboot boot twrp and the phone will then try to get into recovery, the google logo comes up lasts a couple seconds and boot loops all over to where is says my phone cant be check for corruption
By now i should have been able to get into recovery and it wont go through
Click to expand...
Click to collapse
download a factory image and run the flash all file...... it should reboot your phone after 5 minutes and the issue should be resolved.. a hard brick would be a device that does nothing.... in this case i believe that you just didnt do something right.
Then download the latest factory image and extract it
fastboot flash radio.img
fastboot flash bootloader.img
& do a fastboot update the rest archive file as it is
This will flash the rom via fastboot& U don't have to rely on TWRP or CWM
i42o said:
download a factory image and run the flash all file...... it should reboot your phone after 5 minutes and the issue should be resolved.. a hard brick would be a device that does nothing.... in this case i believe that you just didnt do something right.
Click to expand...
Click to collapse
I was really really hoping this would help. I erase/formated everything before flashing anything. I then ran the flash-all file and it took a couple of minutes and it said finished on the command box and my phone restarted and went into the white google logo and rebooted again with a bootloop. I waited around 15 minutes hoping it would start but it didn't.
It honestly feels as if the phone is not processing the full commands but on the pc it seems to go through successfully
is there a way to force an install of a rom and see if maybe a dirty flash over the stock one will allow it to start up?
leninmon said:
Then download the latest factory image and extract it
fastboot flash radio.img
fastboot flash bootloader.img
& do a fastboot update the rest archive file as it is
This will flash the rom via fastboot& U don't have to rely on TWRP or CWM
Click to expand...
Click to collapse
i know how to flash the radio and bootloader but how do i do a fastboot update?
edgarted said:
i know how to flash the radio and bootloader but how do i do a fastboot update?
Click to expand...
Click to collapse
Just unzip the factory image and there U can see the flash shell script files too. Open them in a text editor & U could see the exact command. In a factory img, they also do the same thing via script files. Flashing the radio & bootloader & updating the rest archive
so this is what I've done
I've manually flashed every file needed for the factory image from google.
I also tried wugfresh tool kit which is great but didn't help me much. I flashed stock recovery and treid to boot into to and nothing. I flashed a customer recovery and nothing.
It always does the same thing
the screen that says my phone can't be checked for corruption and then the google sign comes up stays on for a couple seconds and then it bootloops to the can't be checked for corruption.
I try to get into recovery using fastboot commands and the phone does the same exact thing.
I was even able to lock and relock the bootloader and I was able to successfully flash everything at least that is what it showed on the computer
so ive read almost every thread that had to do with bricking and I feel like an expert now but im starting to think it is done =/
edgarted said:
so this is what I've done
I've manually flashed every file needed for the factory image from google.
I also tried wugfresh tool kit which is great but didn't help me much. I flashed stock recovery and treid to boot into to and nothing. I flashed a customer recovery and nothing.
It always does the same thing
the screen that says my phone can't be checked for corruption and then the google sign comes up stays on for a couple seconds and then it bootloops to the can't be checked for corruption.
I try to get into recovery using fastboot commands and the phone does the same exact thing.
I was even able to lock and relock the bootloader and I was able to successfully flash everything at least that is what it showed on the computer
so ive read almost every thread that had to do with bricking and I feel like an expert now but im starting to think it is done =/
Click to expand...
Click to collapse
Hey there. First off make sure to unlock again your bootloader. Then you may follow post # 10 of @Heisenberg 's flashing guide for our device.
First images to flash would be bootloader and radio. First flash bootloader, then make sure to issue the command adb reboot-bootloader. Then afterwards once the phone has rebooted back to bootloader, flash radio, then again do the adb reboot-bootloader again.
Once the phone is again back to bootloader flash the rest of the images except userdata. For the boot.img and recovery.img, flash the stock ones-don't use the decrypted boot.img and don't flash the twrp.img yet. Once all necessary images have been flashed issue the reboot-booloater command one more time, then on the bootloader screen choose the reboot option. Wait anywhere from 3-10 minutes for the phone to load. Let us know how it goes for you.
blitzkriegger said:
Hey there. First off make sure to unlock again your bootloader. Then you may follow post # 10 of @Heisenberg 's flashing guide for our device.
First images to flash would be bootloader and radio. First flash bootloader, then make sure to issue the command adb reboot-bootloader. Then afterwards once the phone has rebooted back to bootloader, flash radio, then again do the adb reboot-bootloader again.
Once the phone is again back to bootloader flash the rest of the images except userdata. For the boot.img and recovery.img, flash the stock ones-don't use the decrypted boot.img and don't flash the twrp.img yet. Once all necessary images have been flashed issue the reboot-booloater command one more time, then on the bootloader screen choose the reboot option. Wait anywhere from 3-10 minutes for the phone to load. Let us know how it goes for you.
Click to expand...
Click to collapse
Hello and thank you for helping.
I tried this method a couple of minutes ago. I flashed them this same way
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
It does the same exact thing it will try and restart the phone, the message that says it can't be checked for corruption the google logo comes up and it repeats it self non stop.
This is what doesn't make sense to me.
This is the file that I had flashed through twrp when it was working fine
Leviticus 1.3 - http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
edgarted said:
Hello and thank you for helping.
I tried this method a couple of minutes ago. I flashed them this same way
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
It does the same exact thing it will try and restart the phone, the message that says it can't be checked for corruption the google logo comes up and it repeats it self non stop.
This is what doesn't make sense to me.
This is the file that I had flashed through twrp when it was working fine
Leviticus 1.3 - http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Click to expand...
Click to collapse
This is weird. What version of the stock factory images did you flash? I've been using leviticus 1.3 since it came out and when i was still on stock rom. I switched over to cm builds and have been flashing every nightly since the 7/24th build, and in the process repeatesly reflashing the aound mod along, and i've had zero issues with the phone booting afterwards.

Messed up data partition, stuck at recovery, flashed EDL but won't start

hey hey,
I am sorry to bother everyone again. After successfully installing RR Oreo yesterday. My phone without a particular reason decided to restart today and go into a bootloop on the zte logo. wipe + reflashing did bring me past the logo but the bootanimation was playing forever (waited 20min). I think I messed it with the data partition encryption because I have been asked for my unlock pattern. I tried wiping and formatting data but twrp was unable to mount it. Therefore I decided to just go back all the way and flashed the B09 EDL from the EDL Tool thread.
edl flash went through smoothly but the system still gets stuck on the bootimage (again waited for 20 minutes now).
when booting the phone it flashes recovery android and then turns black. EDL mode still works.
I HAVE NO IDEA IF ITS CHARGING
however I don't know what else to do and I would really really like to have just a working phone again.
thanks for your help
Try flash full following this post,
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
fleity said:
hey hey,
I am sorry to bother everyone again. After successfully installing RR Oreo yesterday. My phone without a particular reason decided to restart today and go into a bootloop on the zte logo. wipe + reflashing did bring me past the logo but the bootanimation was playing forever (waited 20min). I think I messed it with the data partition encryption because I have been asked for my unlock pattern. I tried wiping and formatting data but twrp was unable to mount it. Therefore I decided to just go back all the way and flashed the B09 EDL from the EDL Tool thread.
edl flash went through smoothly but the system still gets stuck on the bootimage (again waited for 20 minutes now).
when booting the phone it flashes recovery android and then turns black. EDL mode still works.
I HAVE NO IDEA IF ITS CHARGING
however I don't know what else to do and I would really really like to have just a working phone again.
thanks for your help
Click to expand...
Click to collapse
llaalways said:
Try flash full following this post,
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Click to expand...
Click to collapse
exactly what I did to get here :-/
What is the model of your phone? A2017G?
fleity said:
exactly what I did to get here :-/
Click to expand...
Click to collapse
yes it's a G
let me quickly sum up the current state:
the bootloader unlock screen is no longer displayed (which is very weird)
twrp gets stuck on the teamwin screen
holding power or basically any kind of reboot automatically boots into twrp
the phone is charging in this state and it is recognized by adb with the correct id but as "offline" similar to when you would connect it but not unlock it
the EDL I used is a B09 however I am coming from RR-O-v6. EDL full flashs "everything" therefore wondering if the bootstack B32-B10 I flashed only works with oreo roms etc. does not make any sense because twrp should work regardless, right?
I see that the edl tool can unlock the bootloader, does it make sense to actively unlock it (after full edl flashing B09 again) through that option in order to get twrp working correctly?
booting up to the twrp start up image I get adb access in recovery state
trying to actually use the recovery fails though
adb shell recovery --wipe_data
RECOVERY_SDCARD_ON_DATA := true
I:Lun file '/sys/devices/soc/6a00000.ssusb/6a00000.dwc3/gadget/lun0/file'
TW_INCLUDE_CRYPTO := true
I:TW_BRIGHTNESS_PATH := /sys/devices/soc/900000.qcom,mdss_mdp/900000.qcom,mdss_mdp:qcom,mdss_fb_primary/leds/lcd-backlight/brightness
I:Found brightness file at '/sys/devices/soc/900000.qcom,mdss_mdp/900000.qcom,mdss_mdp:qcom,mdss_fb_primary/leds/lcd-backlight/brightness'
I:TWFunc::Set_Brightness: Setting brightness control to 153
I:LANG: en
Click to expand...
Click to collapse
or at least stops at this line.
adb shell commands work mostly apparently
Is it possible to format data with ext4 from adb?
you can put twrp 3.2.1.7 in Axon7_EDL_Tool\flash\recovery and rename it as recovery.img, then flash recovery from Axon7_EDL_Tool.
then check if you can actually use twrp.
fleity said:
booting up to the twrp start up image I get adb access in recovery state
trying to actually use the recovery fails though
or at least stops at this line.
adb shell commands work mostly apparently
Is it possible to format data with ext4 from adb?
Click to expand...
Click to collapse
tried flashing recovery through edl again like you said, both with 3.2.1.7 and 3.2.1.0. This is pretty much the state I am stuck in. After the flash completes successfully I reboot the phone from the tool and it immediately boots to recovery, shows the teamwin / twrp logo screen and stops there.
I can connect through adb in this state. The device is show with the correct id as in recovery. However I can not for example wipe data. If I try to do that the phone fails to respond. adb shell ls works on the other hand.
but still I don't get into twrp in a way in which I could actively do anything
adb works on recovery mode is weird.
you can try following options
1. Axon7_EDL_Tool flash full with A2017G_B11_MARSHMALLOW_FULL_EDL
2. Axon7tool write recovery on edl mode
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
3. Axon7toolkit, you need bypass virus check, there are a lot of options, including flash twrp, restore from hardbrick on edl mode.
https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
4. if everything failed, you can try 4th category brick repair
https://forum.xda-developers.com/axon-7/how-to/guide-dfu-unbrick-guide-disassembly-t3731152
fleity said:
tried flashing recovery through edl again like you said, both with 3.2.1.7 and 3.2.1.0. This is pretty much the state I am stuck in. After the flash completes successfully I reboot the phone from the tool and it immediately boots to recovery, shows the teamwin / twrp logo screen and stops there.
I can connect through adb in this state. The device is show with the correct id as in recovery. However I can not for example wipe data. If I try to do that the phone fails to respond. adb shell ls works on the other hand.
but still I don't get into twrp in a way in which I could actively do anything
Click to expand...
Click to collapse

[OP6T] fastboot erase persist

Hello ALL!
I normally don't message much because usually I can find most of my problems can be fixed by searching threads online. However, this particular case for me has been exhausting because through trial and error I have been unsuccessful in getting my 6T to boot into any rom normally.
I went from a stock T-Mobile to International version to LOS. The reason I did what I did was because I could get a IMEI or SIM to register on LOS. That worked fine on OOS 9.0.11. but as soon a I flash the latest LOS, no sim, bootloader, or IMEI detection.
I was rooted and unlocked. Now I am neither.
While on LOS, someone on another forum suggested to erase the persist partition and reflash to get the sim imei back so the phone would get service, when the phone rebooted it still didn't work and then the second time it rebooted it always gets stuck on the boot screen and never boots into the OS.
I tried to repair and reflash but was unsuccessful.
Since doing all of that, Ive reflashed using msm tool and although that was successful for OOS 9.0.11 and T-Mobile stock rom. It gets stuck on the boot screens for both.
I flashed LOS on A & B so I don't have a stock recovery.
I can't ADB anymore. I can only seem to connect via FASTBOOT but cannot seem to flash anything because the BOOTLOADER is now LOCKED.
How can I get this phone back to its original state? What ever the persist partition is. Removing it had made the phone non-bootable.
What can I do to fix? I greatly appreciate any help to get the phone operational again.
Thank you all!
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
- Go to the thread linked above and download the latest OOS (.13) stable.
- Download latest Magisk.
- Have the latest TWRP .img downloaded and on-hand, you will use a few times as well as the installer .zip.
- Be sure to have adb/fastboot installed.
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
- Put your phone into fastboot mode (reboot to bootloader).
- Go to the folder you downloaded in the first step and run the "flash all.bat".
- Ignore errors. If it's get stuck for more than 45 seconds, just hit enter to keep it going.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP.
- In TWRP, go to Reboot and changed the boot partition to the one NOT CURRENTLY enabled. In other words, switch boot partitions.
- Reboot bootloader.
- Go to the folder you downloaded in the first step and run the "flash all.bat" again.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP again.
- Move Magisk installer and TWRP installer from steps two and three onto the internal memory of your device.
- Flash TWRP, reboot recovery to make sure it sticks.
- Flash Magisk for root.
- Wipe dalvik and reboot system.
You will have the latest stable OOS on both partitions at this point! I literally just did this yesterday. Good luck!
..Cory.. said:
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
- Go to the thread linked above and download the latest OOS (.13) stable.
- Download latest Magisk.
- Have the latest TWRP .img downloaded and on-hand, you will use a few times as well as the installer .zip.
- Be sure to have adb/fastboot installed.
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
***BACK UP DATA, YOUR PHONE WILL BE WIPED. INTERNAL SD AS WELL***
- Put your phone into fastboot mode (reboot to bootloader).
- Go to the folder you downloaded in the first step and run the "flash all.bat".
- Ignore errors. If it's get stuck for more than 45 seconds, just hit enter to keep it going.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP.
- In TWRP, go to Reboot and changed the boot partition to the one NOT CURRENTLY enabled. In other words, switch boot partitions.
- Reboot bootloader.
- Go to the folder you downloaded in the first step and run the "flash all.bat" again.
- OOS will boot. Go to settings, enable developer setting, enable advanced reboot and reboot bootloader again.
- Use "fastboot boot 'twrp-file-name'.img" to boot into TWRP again.
- Move Magisk installer and TWRP installer from steps two and three onto the internal memory of your device.
- Flash TWRP, reboot recovery to make sure it sticks.
- Flash Magisk for root.
- Wipe dalvik and reboot system.
You will have the latest stable OOS on both partitions at this point! I literally just did this yesterday. Good luck!
Click to expand...
Click to collapse
Thank you but how can I flash if my bootloader is locked? Everything I try fails.
I guess the real question is: How can I get the phone to turn on OEM UNLOCK so I can fastboot unlock the Bootloader if it wont boot up the OS?
Is there a way to fix it via the msmdownload tool? Custom file maybe? I've tried the files 9.0.11 & 12 OOS files and all I get is the boot screen white ball logo circling the red ball - stuck in loop and same with stock t-mobile rom.
My friend, sounds like you need to restore your EFS partitions
... I'm trying to figure out how the hell you successfully flashed MSM tool in EDL mode and not have ALL your partitions restored. That tool is supposed to literally write the phone as it came out of the box. Also I think there are different MSM tools for each device respectively, you did use the T-Mobile one right?
Causical said:
My friend, sounds like you need to restore your EFS partitions
... I'm trying to figure out how the hell you successfully flashed MSM tool in EDL mode and not have ALL your partitions restored. That tool is supposed to literally write the phone as it came out of the box. Also I think there are different MSM tools for each device respectively, you did use the T-Mobile one right?
Click to expand...
Click to collapse
My thoughts exactly. So, when it was on LOS I erased the persist partition and that really messed things up. So yes, how can I restore the partition back with a locked bootloader? Every time I've used MSM tool it fixes everything. This time no such luck. I flashed 9.0.11 & 12 and then I did the T-Mobile version. All only boot to the boot screen and hang. In doing so, I wasn't thinking if that failed and it locks the bootloader, then what? I saw an old video somewhere on a oneplus 2 or 3 where the person used the msm tool 3.0 and fixed a bricked locked bootloader phone. Similar to the fastboot method of reformatting. In the msm tool folder he had all the image files for all the partitions not sure if that the same thing as msm tool 4.0 with just one ops image file?
Anyway, is there a way to unlock the bootloader without booting into the OS? Or a way to restore the partitions via msm tool?
defcondoc said:
My thoughts exactly. So, when it was on LOS I erased the persist partition and that really messed things up. So yes, how can I restore the partition back with a locked bootloader? Every time I've used MSM tool it fixes everything. This time no such luck. I flashed 9.0.11 & 12 and then I did the T-Mobile version. All only boot to the boot screen and hang. In doing so, I wasn't thinking if that failed and it locks the bootloader, then what? I saw an old video somewhere on a oneplus 2 or 3 where the person used the msm tool 3.0 and fixed a bricked locked bootloader phone. Similar to the fastboot method of reformatting. In the msm tool folder he had all the image files for all the partitions not sure if that the same thing as msm tool 4.0 with just one ops image file?
Anyway, is there a way to unlock the bootloader without booting into the OS? Or a way to restore the partitions via msm tool?
Click to expand...
Click to collapse
Try this and tell me if it works.
Have you tried this dudes stuff? https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
... Not even sure what it is really, just says collection of unbrick tools.
_Masked_ said:
Try this and tell me if it works.
Click to expand...
Click to collapse
Yes, I did try that. That is what I just flashed with the msm tool. Gets stuck on the OOS boot animation.
Causical said:
Have you tried this dudes stuff? https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
... Not even sure what it is really, just says collection of unbrick tools.
Click to expand...
Click to collapse
Looks like the MSM tool. I'm going to give 9.0.13 a try but I'm thinking I may have the same problem.
Causical said:
Have you tried this dudes stuff? https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746
... Not even sure what it is really, just says collection of unbrick tools.
Click to expand...
Click to collapse
Tried 9.0.13. Still gets stuck on OOS boot animation screen. There's got to be something to flash to fix this.
So you're booting EDL mode then flashing the MSM tool that exactly matches the way your phone came stock? At this point I would discontinue trying to convert it to international or upgrade the OS to a more recent version or any of that. I would focus on strictly flashing it to exactly the way you bought it.
Causical said:
So you're booting EDL mode then flashing the MSM tool that exactly matches the way your phone came stock? At this point I would discontinue trying to convert it to international or upgrade the OS to a more recent version or any of that. I would focus on strictly flashing it to exactly the way you bought it.
Click to expand...
Click to collapse
Yes. I did flash the stock T-Mobile ROM via the MSM tool. Freezes at the pink T-Mobile boot screen. Pretty sure the partitions need to be fixed but I thought the MSM tool would do that? I guess not. Is there a more advanced MSM tool where I can see what's being partitioned or is the MSM tool not doing any partitioning and that's why the phone is having the boot problem?
defcondoc said:
Yes. I did flash the stock T-Mobile ROM via the MSM tool. Freezes at the pink T-Mobile boot screen. Pretty sure the partitions need to be fixed but I thought the MSM tool would do that? I guess not. Is there a more advanced MSM tool where I can see what's being partitioned or is the MSM tool not doing any partitioning and that's why the phone is having the boot problem?
Click to expand...
Click to collapse
I know this is a stupid question but have you tried a factory reset in recovery mode? I know its a stupid question but I did not see it asked or noted.
Scott said:
I know this is a stupid question but have you tried a factory reset in recovery mode? I know its a stupid question but I did not see it asked or noted.
Click to expand...
Click to collapse
No stupid questions and I don't mind repeating answers to questions. I have tried that, but it does nothing. I get wipe cache or reboot to fastboot or reboot to recovery. When I choose system wipe, it takes 1 second to finish. It reboots and it gets stuck on the boot screen. Ever since persist partition was deleted it just freezes on startup and now that the bootloader is locked I cant seem to get anything to work. MSM tool I thought was supposed to fix this sort of thing but it has failed. Someone must know a way to get back into the OS so I can turn on OEM Unlock.
How do you know your bootloader is locked?
Causical said:
How do you know your bootloader is locked?
Click to expand...
Click to collapse
Fastboot says bootloader is locked. Shows it on the fastboot screen. Wont let me transfer any files from pc to phone. I can start the transfer process but it fails.
defcondoc said:
Fastboot says bootloader is locked. Shows it on the fastboot screen. Wont let me transfer any files from pc to phone. I can start the transfer process but it fails.
Click to expand...
Click to collapse
So you're able to enter EDL mode with a locked bootloader? How do you know your computer is seeing your device in EDL mode?
I'm going to place this here for myself for now. I'm just trying to understand your situation a little better, but this is just for later.... maybe, depending on your answer. https://forum.xda-developers.com/an...how-to-reboot-to-edl-fastboot-t3394292/page12
ALSO; If you don't mind can you link the thread that contains the original discussion where your problem began?
Causical said:
So you're able to enter EDL mode with a locked bootloader? How do you know your computer is seeing your device in EDL mode?
I'm going to place this here for myself for now. I'm just trying to understand your situation a little better, but this is just for later.... maybe, depending on your answer. https://forum.xda-developers.com/an...how-to-reboot-to-edl-fastboot-t3394292/page12
ALSO; If you don't mind can you link the thread that contains the original discussion where your problem began?
Click to expand...
Click to collapse
The point of EDL is to get around any restrictions or issues with the device, so yes, you can boot to EDL while locked. Your link will not help much because he can already get to EDL. Not to mention he will have no ADB access. Whatever he does, he has to fix it in EDL.
OP: Are you up and running yet? I am willing to try copying out my partition and sending to you.
Let me know...
---------- Post added at 08:12 PM ---------- Previous post was at 08:08 PM ----------
Wait, I just realized that my persist.img would not work because he has no way to flash it.
Nevermind.

Find device storage corrupted your device is unsafe now.

So I unlocked bootloader on my redmi note 7.
Then I flashed twrp and rooted my device.
Then I flashed pixel experience but it stuck on the Google logo after reboot. I tried factory reset in twrp but it didn't work.
So I restored the backup I did before flashing pixel experience.
And then my phone stuck on bootloop.
So I booted into fastboot mode and flashed the fastboot rom and it worked. I have successfully unbricked my device.
But now it shows "find device storage corrupted your device is unsafe now"
Everything works fine except I can't turn on find device and also can't install miui ota updates via twrp.
(And also when flashing twrp for the first time when I reboot it showed the stock recovery because I hadn't flashed disable dm-verify because when I am in twrp and try to mount my system to my computer my phone doesn't show up in the computer. So first I copied the disable dm-verify file then again flashed twrp then booted into twrp and then flashed disable dm-verify. I don't know if it is necessary to format data when flashing twrp. Maybe that's why the problem occured. I don't know.)
Please help.
Thank you.
Extract persist.img from official fastboot rom and replace the existing persist in Orangefox.
At least it helped me.
Persist.img flash through recovery gonna fix the problem but forget about Netflix and L1!!
Personally speaking had that problem with corrupted message pop up every time i reboot my device and when i flashed the persist.img through OrangeFox recovery i lost L1 forever (and there is no turning back).
If you wanna try that method i highly suggest you to Backup your Persist Partition first.
Yes, but isn't the original persist partition already lost, when you get the "storage corrupted" message?
Lucky-thirteen said:
Yes, but isn't the original persist partition already lost, when you get the "storage corrupted" message?
Click to expand...
Click to collapse
I tried may hours to define the problem's source but i think that's unclear in every situation. Others say that's a persist.img corruption while others had that problem with Mi Account corruption, etc.
Mine corrupted message came when i tried to flash Global Official MIUI in a EU variant device through normal process that doesn't engage any kind of Persist partition rewrite.
I had a backup of persist.img and flashed original from EU fastboot file and finally after that I repatch my old persist.img. The first time i did that process my device and L1 worked properly (even that spam message disappeared) but after a long time that I tried same process for same problem i completely lost my L1 [strange af!].
So, a safe process to try now is to flash back the official fastboot image of your variant (Erase + Lock [for L1]) through MiFlash tool and check that corruption message if it goes away (be careful to flash the correct fastboot image or you will get a a bricked device).
In conclusion it's Extremely advisable to keep a full backup of your partitions and especially Persist partition if you wanna flash Roms and generally unlock bootloader!
I use twrp recovery
I don't know about orange fox recovery
Strange51 said:
I use twrp recovery
I don't know about orange fox recovery
Click to expand...
Click to collapse
Always use OrangeFox for Lavender here is the link (download and test with latest R10.1_02-Stable)

Categories

Resources