Database Info

Please assist - Unusable Razr HD ( Spent 5-6 hours so far no luck )

Hi team,
Wondering is someone can assist or point me in right direction for fixing my wife's Razr HD. ( Australian Telstra GSM )
Issue - Currently phones starts goes to OS , however all andriod apps / core services are stopping making it unusable, usually phone will start ask for pin and within 30 seconds all apps and core services stop ( with error messages etc ).
So here is what happens and i have tried.
1. Tried uninstalling apps ( eg whatsapp / facebook etc .. ) it uninstalls sometime before the freezing / errors - but once you reboot those apps come back as there never uninstalled :|
2. Erase all data it never works it lets me press the button , but on reboot come back to original problem OS.
So i decided i should root / install custom rom or even stock rom ).
1. Boot Loader - Unlocked ( did that on motorola website no issues )
2. Tried Installing customer recovery in fastboot ( it flashes , however it goes to original recovery dead gread andriod with red traingle with belly open !, after flash i have not let it boot to OS still the same issue) - i think it has original-recovery.p file in system i cant delete it or rename it ..
3, Rooting - tried rooting no luck .. i can connect via ADB however system is read only ( doesnt let SU , busy box etc to copy or execute at all ) - tried motochoppper/ saferoot no luck .. it cant write or copy or exceute SU.
So i tried few other extreme measures as below..
fastboot erase system or -w
fastboot erase data
fastboot erase cache
All successful , however after that still boot to original OS.
Tried installing Stock ROM/Firmware using - RSDLite , it seems to install copied the files on reboot .. same old OS ..
i can goto fastboot , i can run adb shell command ( but its read only system ).
i am really stuck here wondering if you guys help / much appreciated.
rgds.

Have you tried factory reset? Or boot into safe mode?

Zeljko1234 said:
Have you tried factory reset? Or boot into safe mode?
Click to expand...
Click to collapse
Factory reset yes , however after device reboot it does nothing comes back t same faulty OS.
Safe mode?

Safe mode.
You may try to flash rom again but be very careful with unlocked bootloader. It's strange that you cannot boot into custom recovery holding volume down and power after you flashed it.

Zeljko1234 said:
Safe mode.
You may try to flash rom again but be very careful with unlocked bootloader. It's strange that you cannot boot into custom recovery holding volume down and power after you flashed it.
Click to expand...
Click to collapse
Tried flashing , in safe mode no luck either , any other suggestions?
Cheers,

You probably left your USB plugged in after you flashed Recovery and that set you back to Stock Recovery.....unplug the usb....

Hmm sounds like symptons that my dad's old Nook color experienced being stuck in read only mode. Tried everything but it was stuck in that read only state no matter what I did. Hopefully that is not the case for your phone. Have you tried house of moto or other compatible utility to restore back to stock?

this happened a few times on an older faulty version of twrp. until someone can figure out how to remove the write only from fastboot, there is no utility or script that will fix it.
no one was able to figure it out before, unfortunately, your phone is likely toast.

Just saw this thread and it sounds exactly like what just started happening to my phone yesterday. I was unlocked, and rooted, with stock VZW (US) ROM. All was fine. Then started getting app error popups like you state and tried using TWRP recovery to install a backup I had made and it appears to work only if I DO NOT check the 'data' box. When I try and wipe data, it errors out as well. I am worried something caused it to get stuck in read only mode like one of the last comments in this thread and the phone is toast, but not just.
If you find anything or figure it out please let me know, I'll do the same....
desitunez said:
Hi team,
Wondering is someone can assist or point me in right direction for fixing my wife's Razr HD. ( Australian Telstra GSM )
Issue - Currently phones starts goes to OS , however all andriod apps / core services are stopping making it unusable, usually phone will start ask for pin and within 30 seconds all apps and core services stop ( with error messages etc ).
So here is what happens and i have tried.
1. Tried uninstalling apps ( eg whatsapp / facebook etc .. ) it uninstalls sometime before the freezing / errors - but once you reboot those apps come back as there never uninstalled :|
2. Erase all data it never works it lets me press the button , but on reboot come back to original problem OS.
So i decided i should root / install custom rom or even stock rom ).
1. Boot Loader - Unlocked ( did that on motorola website no issues )
2. Tried Installing customer recovery in fastboot ( it flashes , however it goes to original recovery dead gread andriod with red traingle with belly open !, after flash i have not let it boot to OS still the same issue) - i think it has original-recovery.p file in system i cant delete it or rename it ..
3, Rooting - tried rooting no luck .. i can connect via ADB however system is read only ( doesnt let SU , busy box etc to copy or execute at all ) - tried motochoppper/ saferoot no luck .. it cant write or copy or exceute SU.
So i tried few other extreme measures as below..
fastboot erase system or -w
fastboot erase data
fastboot erase cache
All successful , however after that still boot to original OS.
Tried installing Stock ROM/Firmware using - RSDLite , it seems to install copied the files on reboot .. same old OS ..
i can goto fastboot , i can run adb shell command ( but its read only system ).
i am really stuck here wondering if you guys help / much appreciated.
rgds.
Click to expand...
Click to collapse
---------- Post added at 03:02 PM ---------- Previous post was at 02:52 PM ----------
I am guessing this might be the issue and I am experiencing it as well. However, I have no idea how that could have happened in the first place. I never tried to do anything with TWRP until after the phone began acting funny with all apps crashing (pop ups stating that) and the phone essentially becoming unusable.
When I am in TWRP and do wipes (factory reset, or advanced wipes) it seems to wipe everything fine, even the data partition. However, when I try and write to that partition it fails (i.e. restoring a backup including the data partition). If I don't include the data partition the restore works, but the phone is still crap.
Does this sound like the issue you mention below (data is stuck on read only and there is no way around it)?? If so, anyone in the market for a decent looking paperweight??
bweN diorD said:
this happened a few times on an older faulty version of twrp. until someone can figure out how to remove the write only from fastboot, there is no utility or script that will fix it.
no one was able to figure it out before, unfortunately, your phone is likely toast.
Click to expand...
Click to collapse

surfmly said:
Just saw this thread and it sounds exactly like what just started happening to my phone yesterday. I was unlocked, and rooted, with stock VZW (US) ROM. All was fine. Then started getting app error popups like you state and tried using TWRP recovery to install a backup I had made and it appears to work only if I DO NOT check the 'data' box. When I try and wipe data, it errors out as well. I am worried something caused it to get stuck in read only mode like one of the last comments in this thread and the phone is toast, but not just.
If you find anything or figure it out please let me know, I'll do the same....
---------- Post added at 03:02 PM ---------- Previous post was at 02:52 PM ----------
I am guessing this might be the issue and I am experiencing it as well. However, I have no idea how that could have happened in the first place. I never tried to do anything with TWRP until after the phone began acting funny with all apps crashing (pop ups stating that) and the phone essentially becoming unusable.
When I am in TWRP and do wipes (factory reset, or advanced wipes) it seems to wipe everything fine, even the data partition. However, when I try and write to that partition it fails (i.e. restoring a backup including the data partition). If I don't include the data partition the restore works, but the phone is still crap.
Does this sound like the issue you mention below (data is stuck on read only and there is no way around it)?? If so, anyone in the market for a decent looking paperweight??
Click to expand...
Click to collapse
if your phone goes to read only because of that faulty version of twrp, its toast. i am sorry for your loss

He can try to flash correct twrp...

Zeljko1234 said:
He can try to flash correct twrp...
Click to expand...
Click to collapse
that may work in some rare cases.
i hope this poster is one of them!!! that it works.
if the entire phone goes to read only. i havent seen a solution on any forum.

bweN diorD said:
that may work in some rare cases.
i hope this poster is one of them!!! that it works.
if the entire phone goes to read only. i havent seen a solution on any forum.
Click to expand...
Click to collapse
Well it looks like I was able to get through some of it. I followed the instructions here: http://www.droidrzr.com/index.php/topic/49699-1834614xt926-ota/. I did the extra step of going to stock 183 (unrooted) and then flashed the update in that and the phone is working fine. I am already unlocked (have been for long time), but not rooted at the moment. I believe I can root now (being that I am unlocked) but haven't tackled that yet. At the very least I have a phone that works for my upcoming business trip.....
BTW - the TWRP I had installed has been used on my phone for a long time (8-12 months??) so not sure why that version all of a sudden would have caused the issue, but at this point it doesn't appear to have been that issue (with data locked in read only mode).

I'm really glad that you found solution for you and for all of us who may have the same problem in the future. Thx.

Qualcomm Crash Dump

Hey guys was using my phone, Bluetooth on music streaming and I was typing away on WhatsApp and all of a sudden my phone froze up and then black screen. Then a few seconds later got a Qualcomm Crash dump screen with something about modem crash?
Anyone have this issue? Was able to reboot device after holding volume up and power button for a few seconds.

I havent had the issue myself but I've heard other OnePlus devices with this problem. Luckily you were able to fix it with a reboot but worse comes to worse you'll have to use the MSM tool.

What does the msm tool do? I've seen weird things with the phone, it does this shift to the screen sort of like you are taking a screen shot of the screen.

I do have this problem too since 2 weeks. I´m not rooted and not Bootloader unlocked. (waiting for my favourit rom)
It happens randomly. I didn´t had the time to go into it.

This is the issue see image

ludester said:
This is the issue see image
Click to expand...
Click to collapse
Yesterday, after flashing OOS 10.0.1 again to go back to stock kernel and after flashed xXx_NoLimits_module, and while REBOOTING, I got into Qualcomm Crash dump screen and somehow I managed to boot back to system.
After trying couple times to enter twrp(VolDown+Power Button), with VolUp+Power Button I got into system again

id get that when is select wrong slot in twrp but when i change it back to slotA it reboots as normal i never get it at random though came up when selecting slot b to active.

refedit said:
Yesterday, after flashing OOS 10.0.1 again to go back to stock kernel and after flashed xXx_NoLimits_module, and while REBOOTING, I got into Qualcomm Crash dump screen and somehow I managed to boot back to system.
After trying couple times to enter twrp(VolDown+Power Button), with VolUp+Power Button I got into system again
Click to expand...
Click to collapse
Use msm tool to load everything to stock and then try update again. Using msm tool fixed my issue

ludester said:
Use msm tool to load everything to stock and then try update again. Using msm tool fixed my issue
Click to expand...
Click to collapse
So far I'm good. It didn´t boot to QUalcomm screen again.
Although, to prevent future issue, I'm backing up everything so I use the msmtool. Although, I don't if the issue isn't related from Upgrading from Android Q to A10. So I rather'd use the msm tool with Android 10. As far as I know, there's no msm tool for BA version

Oneplus6 qualcomm crashdump mode

Hello,
I really need help in figuring out what possible way to fix this issue that suddenly happened to my phone yesterday. I just open a sling tv app and it happened immediately. I never modified the phone nor unlocked the bootloader. It's still the same phone as I got from the company. I really like my phone and I took care of it very well and I am pissed that this error showed up yesterday and it's completely bricked now.
I tried to msm tool method to install the factory firmware but I am still getting the same error
I would appreciate any help.
Thanks,
Dan

Check this:
tiga016 said:
It's hardware issue and cannot be fixed by software. Motherboard replacement might fix the issue. Anyway here is the message from some telegram channels like Evolution X:
"If your phone has gotten the qualcomm crashdump mode screen, please follow these steps:
1. DO NOT REBOOT YOUR PHONE
2. Put your phone in the freezer for 15~20 minutes or until it feels like an ice cube (yes, I'm serious)
3. If you are rooted, reboot your phone ONLY ONCE back to the rom. If you are not rooted then reboot your phone ONLY ONCE to recovery.
4. Using TWRP or a root file manager such as Fx, navigate to /sys/fs/pstore and copy all files to /sdcard/. REBOOTING MORE THAN ONCE WILL DELETE THESE FILES.
Send console-ramoops and/or pmsg-ramoops log files to us."
I personally do not recommend this because I didn't test it yet because my phone does not experience crashdump. It's for you to decide. Here is the message link for your reference.
Click to expand...
Click to collapse
And yes, it's not recommended (unless you're totally hopeless).
Anyhow, this is a guide with a good success rate, check it:
Qualcomm Crashdump Mode

Mohamedkam000 said:
Check this:
And yes, it's not recommended (unless you're totally hopeless).
Anyhow, this is a guide with a good success rate, check it:
Qualcomm Crashdump Mode
Click to expand...
Click to collapse
As I have said earlier it is hardware issue not software so MSM tool has low chance of fixing it. It might succeed and boot but crashdump will come back again.

drsaog said:
Hello,
I really need help in figuring out what possible way to fix this issue that suddenly happened to my phone yesterday. I just open a sling tv app and it happened immediately. I never modified the phone nor unlocked the bootloader. It's still the same phone as I got from the company. I really like my phone and I took care of it very well and I am pissed that this error showed up yesterday and it's completely bricked now.
I tried to msm tool method to install the factory firmware but I am still getting the same error
I would appreciate any help.
Thanks,
Dan
Click to expand...
Click to collapse
Same here..
Now i'm scared of using OOS

[OnePlus 6] Possibly soft bricked?

My op 6 recently just decided to die? I was using it normally and locked then turned it back one and it crashed going into "Qualcomm Crashdump Mode" with no error message.
I tried re-flashing stock, lineageOS and then found the "Qualcomm MSM tool" which was supposed to fix everything... but it didn't.
So now my op6 is bricked? and has a locked bootloader
Can anyone help? Maybe lol?

ThatHumanTho said:
My op 6 recently just decided to die? I was using it normally and locked then turned it back one and it crashed going into "Qualcomm Crashdump Mode" with no error message.
I tried re-flashing stock, lineageOS and then found the "Qualcomm MSM tool" which was supposed to fix everything... but it didn't.
So now my op6 is bricked? and has a locked bootloader
Can anyone help? Maybe lol?
Click to expand...
Click to collapse
It's hardware issue and cannot be fixed by software. Motherboard replacement might fix the issue. Anyway here is the message from some telegram channels like Evolution X:
"If your phone has gotten the qualcomm crashdump mode screen, please follow these steps:
1. DO NOT REBOOT YOUR PHONE
2. Put your phone in the freezer for 15~20 minutes or until it feels like an ice cube (yes, I'm serious)
3. If you are rooted, reboot your phone ONLY ONCE back to the rom. If you are not rooted then reboot your phone ONLY ONCE to recovery.
4. Using TWRP or a root file manager such as Fx, navigate to /sys/fs/pstore and copy all files to /sdcard/. REBOOTING MORE THAN ONCE WILL DELETE THESE FILES.
Send console-ramoops and/or pmsg-ramoops log files to us."
I personally do not recommend this because I didn't test it yet because my phone does not experience crashdump. It's for you to decide. Here is the message link for your reference.

tiga016 said:
It's hardware issue and cannot be fixed by software. Motherboard replacement might fix the issue. Anyway here is the message from some telegram channels like Evolution X:
"If your phone has gotten the qualcomm crashdump mode screen, please follow these steps:
1. DO NOT REBOOT YOUR PHONE
2. Put your phone in the freezer for 15~20 minutes or until it feels like an ice cube (yes, I'm serious)
3. If you are rooted, reboot your phone ONLY ONCE back to the rom. If you are not rooted then reboot your phone ONLY ONCE to recovery.
4. Using TWRP or a root file manager such as Fx, navigate to /sys/fs/pstore and copy all files to /sdcard/. REBOOTING MORE THAN ONCE WILL DELETE THESE FILES.
Send console-ramoops and/or pmsg-ramoops log files to us."
I personally do not recommend this because I didn't test it yet because my phone does not experience crashdump. It's for you to decide. Here is the message link for your reference.
Click to expand...
Click to collapse
Thanks for the reply, I will try this as a last resort, but I've already rebooted my phone many times and I can't boot into OOS..

tiga016 said:
2. Put your phone in the freezer for 15~20 minutes or until it feels like an ice cube (yes, I'm serious)
Click to expand...
Click to collapse
Good God, please don't do this.
Putting your phone in the freezer and thawing it out will create a ton of condensation in the mainboard that's extremely difficult to get rid of & dry (it may take several weeks to months). Powering on the device while it's still wet like this can and most probably will short the circuits on the board, making the problem even worse.
OP, if the problem is software, it should be solvable with the MSM Tool.
Else if it's hardware, then the safest solution would be taking it to a certified service center and get the board replaced entirely.

adeklipse said:
Good God, please don't do this.
Putting your phone in the freezer and thawing it out will create a ton of condensation in the mainboard that's extremely difficult to get rid of & dry (it may take several weeks to months). Powering on the device while it's still wet like this can and most probably will short the circuits on the board, making the problem even worse.
OP, if the problem is software, it should be solvable with the MSM Tool.
Else if it's hardware, then the safest solution would be taking it to a certified service center and get the board replaced entirely.
Click to expand...
Click to collapse
The same thing happened to me about a year ago. After completing the msm tool procedure my phone got stuck in a permanent bootloop w/ the bootloader locked of course. I suggest using the msm tool sparingly as this happened to me after about the tenth time I used it.

First of all thanks to the contributors here for pulling together the user guides for unbricking the phone. I am in a rather weird situation. While trying to flash my hard-bricked onePlus 6 - I think the battery was low, and the download did not complete fully. Since then, I have recharged the phone but the download gets stuck on this error: Firehose GetUSInfo Failed
I think my phone does not power-off fully somehow. I keep holding the powerbutton for over a minute, but the minute I connect the phone to my PC, it gets recognized immediately with the correct Qualcomm 9008 port. So the drivers are correct, and the PC recognizes the phone correctly.
Any idea how to switch off the phone fully, and then how to get past the 'Firehose GetUSInfo Failed' error?
Thanks in advance!

bro izi fix, i get this before and oneplus agen in jordan cant fix it so i fix it by myself, now im going to sleep pls send me a msg on telegram ( @NotReal0 ) i will learn you how to fix it but pls tomorrow u go to any pro dev shot ask them to get you the imei partation EFC that file have imei number and mac address you will need it for real
just send me a msg so i can help you step by step
( i dont need your money )
ThatHumanTho said:
My op 6 recently just decided to die? I was using it normally and locked then turned it back one and it crashed going into "Qualcomm Crashdump Mode" with no error message.
I tried re-flashing stock, lineageOS and then found the "Qualcomm MSM tool" which was supposed to fix everything... but it didn't.
So now my op6 is bricked? and has a locked bootloader
Can anyone help? Maybe lol?
Click to expand...
Click to collapse

OP 8 IN2017 (T-Mobile) / Hard Brick / Help with MSM or QFIL

Hey guys,
Recently after a software update my OP 8 started to crash and after that it would restart itself up. One day it just decided not to do it again, power button did nothing and it just wouldn't boot at all. I thought that the phone was dead, but after a couple of weeks I decided to connect the phone to my computer and after a "low battery warning" it boot up. When booting up, after a while it did the same thing as before, it crashed and decided to restart itself up. I did a factory reset and the same thing happened when I got to the android set up screen.
The same day, I decided that I needed to change the ROM since there could be a problem with it. While trying to unlock the bootloader I realized that I need a code from T Mobile (which I'm solicited and still waiting on), I decided to turn the phone off (so that it didn't restart or crashed) and wait for the code to get to me.
The next day, I tried to boot up the phone and it didn't. When connected to my pc i saw that it was recognized as a QCBulk (something like that), I learned about Qualcomm EDL, downloaded drivers and the phone is kinda talking to my pc. Now, I have used MSM tool to install new firmware but after installing the phone doesn't boot back up but stays on the same EDL mode.
So I need some advice,
1. I thought of waiting on the battery to run out and maybe the phone would get out of EDL mode that way.
2. Keep trying to flash different OOS roms via MSM tool and hope that the phone boots back up afterwards.
3. Using QFIL (one of Qualcomm tools) install need firmware. Problem is, I need a .efl or .mbn file which should be included in the firmware but can't find anywhere.
Please help me guys,
I just bought the phone and I miss it
THANKS!

I would think MSM tool is your only hope. Are you using the MSM tool for the tmobile version?

Did you fix your problem yet? @Gipsydanger120

I can give you the .efl firehose for the device if you want it, but it's almost useless cuz you can only use it with partition manager thats all.

L0ND0NB0Y said:
I can give you the .efl firehose for the device if you want it, but it's almost useless cuz you can only use it with partition manager thats all.
Click to expand...
Click to collapse
I would appreciate if you could give me the .efl file. I can use QFIL to flash it. Maybe that works cause I haven't been able to make it work, I'm still in EDL mode

Gipsydanger120 said:
I would appreciate if you could give me the .efl file. I can use QFIL to flash it. Maybe that works cause I haven't been able to make it work, I'm still in EDL mode
Click to expand...
Click to collapse
Alright I'll give it to you as soon as I get home

There you go @Gipsydanger120 !

Report back how it goes @Gipsydanger120

L0ND0NB0Y said:
Report back how it goes @Gipsydanger120
Click to expand...
Click to collapse
Thank you very much, I'll let you know if it works

trinidude4 said:
I would think MSM tool is your only hope. Are you using the MSM tool for the tmobile version?
Click to expand...
Click to collapse
Yes, I'm but it's no help. After installing, the phone disconnects and then goes back into EDL mode. I can tell since my pc makes a noise every time something connects/disconnects. I thought auto-reboot in MSM would help, but it doesn't.

L0ND0NB0Y said:
Report back how it goes @Gipsydanger120
Click to expand...
Click to collapse
So I tried to use QFIL with the efl file along side the "firmware" that i downloaded from OnePlus site, but it looks like I need some other type of file. I was following a tutorial and they mentioned that the firmware usually came with this efl file and maybe an XML file too.
So my conclusion is that I need other type of files too be able to use QFIL.
Any advice? Or am I missing something?

Gipsydanger120 said:
Yes, I'm but it's no help. After installing, the phone disconnects and then goes back into EDL mode. I can tell since my pc makes a noise every time something connects/disconnects. I thought auto-reboot in MSM would help, but it doesn't.
Click to expand...
Click to collapse
You know you could force restart the phone out of EDL mode by disconnecting USB holding all buttons at once for about 10 or 12 secs the phone should boot, but if there is a problem with a partition the phone will reboot once again to EDL. If it does reboot to EDL again, your last option would be a SMT download which will 100% make it boot but you will lose your IMEI and widevine certificates. It's a problem to solve another problem.

Gipsydanger120 said:
So I tried to use QFIL with the efl file along side the "firmware" that i downloaded from OnePlus site, but it looks like I need some other type of file. I was following a tutorial and they mentioned that the firmware usually came with this efl file and maybe an XML file too.
So my conclusion is that I need other type of files too be able to use QFIL.
Any advice? Or am I missing something?
Click to expand...
Click to collapse
That's what I was referring above to "it's almost useless", you won't be able to flash it with qfil unless you have the rawprogram.xml and patch.xml for EACH LUN, so that's 5 pairs of xml files.

L0ND0NB0Y said:
You know you could force restart the phone out of EDL mode by disconnecting USB holding all buttons at once for about 10 or 12 secs the phone should boot, but if there is a problem with a partition the phone will reboot once again to EDL. If it does reboot to EDL again, your last option would be a SMT download which will 100% make it boot but you will lose your IMEI and widevine certificates. It's a problem to solve another problem.
Click to expand...
Click to collapse
I've tried to get it out of EDL but i can't. Any key combination doesn't work, that's the main problem.
What's wrong about losing my IMEI? I can probably live without widevine certificates, but what about IMEI?

L0ND0NB0Y said:
That's what I was referring above to "it's almost useless", you won't be able to flash it with qfil unless you have the rawprogram.xml and patch.xml for EACH LUN, so that's 5 pairs of xml files.
Click to expand...
Click to collapse
And after you create the xmls and arrange them in folders with firmware files you are going to realize that QFIL can't flash the files for some reason and all your work have gone.

L0ND0NB0Y said:
That's what I was referring above to "it's almost useless", you won't be able to flash it with qfil unless you have the rawprogram.xml and patch.xml for EACH LUN, so that's 5 pairs of xml files.
Click to expand...
Click to collapse
Dang, and do you have any idea where can I get all that? It really sucks that I can't find anything for this phone.

Gipsydanger120 said:
I've tried to get it out of EDL but i can't. Any key combination doesn't work, that's the main problem.
What's wrong about losing my IMEI? I can probably live without widevine certificates, but what about IMEI?
Click to expand...
Click to collapse
No signal, no data!!!
and most important you will lose the ability of flashing the unlock_token cuz it's gonna say "Verify failed" obviously because of the null imei.

Gipsydanger120 said:
Dang, and do you have any idea where can I get all that? It really sucks that I can't find anything for this phone.
Click to expand...
Click to collapse
Dude, I spent nights creating them I have them but QFIL won't flash our phones idk maybe because of secure boot.

L0ND0NB0Y said:
No signal, no data!!!
and most important you will lose the ability of flashing the unlock_token cuz it's gonna say "Verify failed" obviously because of the null imei.
Click to expand...
Click to collapse
Hmm is it possible to get another IMEI? What if I already have the unlock_token? I'm guessing it won't even work since it doesn't have the IMEI anymore

L0ND0NB0Y said:
Dude, I spent nights creating them I have them but QFIL won't flash our phones idk maybe because of secure boot.
Click to expand...
Click to collapse
Man that sucks! I don't even know how my phone got so messed up in the first place.