Database Users

Help! Can't boot / cant get into recovery. ..

I was unlocked and rooted and ready to install CM7. I followed all the instructions in the Official Atrix CM7 OP to the T, but when it rebooted, I got stuck on the boot screen with "unlocked" and the red M logo.
I tried to repeat the process several times and ended kind of giving up, factory wiping, and then trying to restore my backup. It appeared to restore successfully, but when I rebooted the phone now wont boot at all. I can't even get it into recovery. No combination or order of button presses or battery pulls / usb plugins will turn it on. I just have a green light like it's charging but nothing is working.
Is it possible to brick your phone even after you have been successfully unlocked and rooted just while you are trying to install CM7?
Please help. I am really desperate here. . .

jimjenkins said:
I was unlocked and rooted and ready to install CM7. I followed all the instructions in the Official Atrix CM7 OP to the T, but when it rebooted, I got stuck on the boot screen with "unlocked" and the red M logo.
I tried to repeat the process several times and ended kind of giving up, factory wiping, and then trying to restore my backup. It appeared to restore successfully, but when I rebooted the phone now wont boot at all. I can't even get it into recovery. No combination or order of button presses or battery pulls / usb plugins will turn it on. I just have a green light like it's charging but nothing is working.
Is it possible to brick your phone even after you have been successfully unlocked and rooted just while you are trying to install CM7?
Please help. I am really desperate here. . .
Click to expand...
Click to collapse
are you using the right recovery? romracer or rom manager!

i am using the tenfar CWM included in the Atrix 4G Automatic Unlock script package. will this not work?
if not, how do I replace it with the right recovery if I cant even get into the phone?

jimjenkins said:
i am using the tenfar CWM included in the Atrix 4G Automatic Unlock script package. will this not work?
if not, how do I replace it with the right recovery if I cant even get into the phone?
Click to expand...
Click to collapse
no, that the old recovery you can use the rom manager if you have , or romracer latest recovery you can find that in the development section, also ther was instruction in the cm7 thread.

you should have left it alone at the M boot screen because it takes about 5-10min to boot after unlock and flash...
everything you do now will have to be through fastboot DO NOT SBF FLASH ANYTHING!!!
Go here to use Fastboot
then download the system.img and boot.img from here
use fastboot to push the boot.img and system.img to your phone
if it gets stuck at the M boot screen let it sit for at least 10min
EDIT: get Romracer recovery from here and push that through to your phone through fastboot

Yeah youre going to have to fastboot wipe recovery then fastboot flash recovery recovery.img
Just download rom racers and rename it..recovery.img
Sent from my GT-I9100 using xda premium

Great. Sorry to be such a noob, but do I decompress the CWM-recovery-atrix5.zip file and push the recovery.img file that's inside it? or push the CWM-recovery-atrix5.zip itself?
Also - every time I am able to get my phone into fastboot mode, it says my battery is too weak to flash anything. I cant seem to get the battery to charge enough to execute any fastboot commands. Any way around this? a powered usb hub?

jimjenkins said:
Great. Sorry to be such a noob, but do I decompress the CWM-recovery-atrix5.zip file and push the recovery.img file that's inside it? or push the CWM-recovery-atrix5.zip itself?
Also - every time I am able to get my phone into fastboot mode, it says my battery is too weak to flash anything. I cant seem to get the battery to charge enough to execute any fastboot commands. Any way around this? a powered usb hub?
Click to expand...
Click to collapse
If you can borrow another Atrix user's battery, or take yours to an AT&T store and see if they can charge it for you.
If you're able to get back into recovery then you can just flash the zip.
If not, you'll need to extract the recovery.img to use it with fastboot, or just download it directly from the OP in romracer's thread. (The left hand link is just the .img, the right hand side is the CWM .zip) Then place it in the same directory as fastboot.

So I can literally flash a different recovery from within another?

jimjenkins said:
So I can literally flash a different recovery from within another?
Click to expand...
Click to collapse
yes but it MUST be working proper first ! its ok to use rom managers cwm but i just prefer the otherone alawys have but n e way there are only 2 that are current (uptodate )
thoughs 2 and with romracers you can. chose
a color that you like not just blue
Sent from my MB860 using xda premium

Its the recovery from tenfar CWM. When I can get it into recovery it seems to be working - with the obvious exception of successfully installing CM7
So I can flash romracer recovery from inside tenfar recovery?
sorry if im being redundant - just dont want to screw it up!
thanks

Just download rom racers cwm. Img, head into fastboot and then fastboot flash recovery recovery-****** (whatever yer recovery image color u chose is)
Sent from my MB860 using Tapatalk

I was able after a full day of leaving the phone plugged in, to charge it up. Then I flashed the rom racer recovery, rebooted into recovery (new version), installed CM7, installed gapps, and voila! A working CM7 Atrix. thank you soo soo much guys.

Can't boot android/recovery
ClearFire said:
you should have left it alone at the M boot screen because it takes about 5-10min to boot after unlock and flash...
everything you do now will have to be through fastboot DO NOT SBF FLASH ANYTHING!!!
Go here to use Fastboot
then download the system.img and boot.img from here
use fastboot to push the boot.img and system.img to your phone
if it gets stuck at the M boot screen let it sit for at least 10min
EDIT: get Romracer recovery from here and push that through to your phone through fastboot
Click to expand...
Click to collapse
Please help!!!
The phone stuck in boot screen and overheat, then restart.
In recovery mode is just black screen.
Phone has Neutrino 2.6GT+ ROM whit Clemsyn's OC kernel 1.6GHz and it has unlocked bootloader.
Can I change the kernel without booting in os or recovery?
This problem show after I was extracting very big zip file and phone overheat.

firecode95 said:
Please help!!!
The phone stuck in boot screen and overheat, then restart.
In recovery mode is just black screen.
Phone has Neutrino 2.6GT+ ROM whit Clemsyn's OC kernel 1.6GHz and it has unlocked bootloader.
Can I change the kernel without booting in os or recovery?
This problem show after I was extracting very big zip file and phone overheat.
Click to expand...
Click to collapse
I am actually having this same problem.

My warranty-replacement (unrelated ear-piece failure) had 2.3.6 pre-installed. Thinking little of it, I unlocked the BL and rooted the phone as usual. After this, I tried to install a couple of the ROM's (Neutrino and Morrisoft) which I was most happy with on my previous Atrix.
After flashing either Neutrino or Morrislee's ROM, the phone hung on the M screen. Waiting approximately 30 minutes with no change, I pulled the battery.
When trying to enter recovery mode, the phone would state, "entering recovery mode..." Then go black.
I ended up using RSDLite and sbf flashing the stock 2.3.6 sbf file back to the phone. Then, I had to re-unlock the bootloader and re-root.
This never happened up to, and including 2.3.4, but did twice last night on these ROM's using 2.3.6, and I've flashed many ROM's and Kernels.
It happened to a lesser extent when trying to flash Clemsyn's stock enhanced kernel to the stock ROM, as I was able to enter recovery mode. Entering recovery mode, it would give errors: mounting cache, mounting system errors, and errors to accessing recovery and recovery log files.
Restore recovery would fail in this state, giving me the above errors as well.
Trying to mount the cache and system in recovery would fail. Trying to format cache and system then mounting these could occur temporarily, but would revert back to unmounted when a restore was attempted.
For these problems I pushed a recovery through fastboot.

Just one word: Fastboot. See if Fastboot works and flash everything from there. Or, as Alterna suggested, flash through RSDLite, but that a little dangerous and can brick your phone if you don't know what you are doing. Hope it helps.

Problem sloved!!!
Alterna said:
My warranty-replacement (unrelated ear-piece failure) had 2.3.6 pre-installed. Thinking little of it, I unlocked the BL and rooted the phone as usual. After this, I tried to install a couple of the ROM's (Neutrino and Morrisoft) which I was most happy with on my previous Atrix.
After flashing either Neutrino or Morrislee's ROM, the phone hung on the M screen. Waiting approximately 30 minutes with no change, I pulled the battery.
When trying to enter recovery mode, the phone would state, "entering recovery mode..." Then go black.
I ended up using RSDLite and sbf flashing the stock 2.3.6 sbf file back to the phone. Then, I had to re-unlock the bootloader and re-root.
This never happened up to, and including 2.3.4, but did twice last night on these ROM's using 2.3.6, and I've flashed many ROM's and Kernels.
It happened to a lesser extent when trying to flash Clemsyn's stock enhanced kernel to the stock ROM, as I was able to enter recovery mode. Entering recovery mode, it would give errors: mounting cache, mounting system errors, and errors to accessing recovery and recovery log files.
Restore recovery would fail in this state, giving me the above errors as well.
Trying to mount the cache and system in recovery would fail. Trying to format cache and system then mounting these could occur temporarily, but would revert back to unmounted when a restore was attempted.
For these problems I pushed a recovery through fastboot.
Click to expand...
Click to collapse
My problem like that and I use automated unlock tool to recover recovery, this recovery show some errors but I successfully flash cwm touch and reinstall Nutrition 2.6GT+

Why cant they give us MZ602.SBF FILES!!!!

********************************************UPDATE01/17/12***************************************************************************
Allrighty then finally found a fix that is 10x easier to fix ur 4g/lte
1)Unlock bootloader
2)download RSD v5.4.4 and MZ602 .SBF files from my dropbox below
3)use RSD to flash back to stock 3.2.2 should be back and baseband should allow it be shown if not just do a factory reset and after boot up, it should be fixed!!!
BOOTLOADER 1.50
http://dl.dropbox.com/u/47975216/LTE-Baseband.zip
MZ602 .SBF 3g/4g BASEBAND STOCK FIX use the latest RSD v5
http://dl.dropbox.com/u/47975216/VZ...00_03.1A.54_signed_LTEDC_U_05.19.00.combo.rar
RSD VERSION 5.4.4
http://dl.dropbox.com/u/47975216/RSDLite 5.4.4.msi
if baseband does not show go into settings privacy and do a factory reset should fix xoom back to 3.2.2 with radio working
"Its one thing to thank somebody just hit the button and make it a true thank you!"

Thanks a lot!!!
BTW, stuck on the "Starting LTE (USB2) Software Bypass Mode"
ended up RSD says "Phone disconnected"
my Xoom managed to boot though but it doesn't seem to help flash the baseband

Do you flash the bootloader ZIP in ClockworkMod or stock recovery? I would assume stock recovery since the updater script uses a motorola flash function that I would assume is not built into ClockworkMod.

oldblue910 said:
Do you flash the bootloader ZIP in ClockworkMod or stock recovery? I would assume stock recovery since the updater script uses a motorola flash function that I would assume is not built into ClockworkMod.
Click to expand...
Click to collapse
My bootloader is actually v1.50 so there is no need to flash it

Yes but there may be in the future, thus the question.

I would reccomend to just reflash anyways even if your bootloader is at 1.5, I only did this because I flashed 1.35 everest when I f'ed up my xoom from the start

That's my point. So how do you flash it? ClockworkMod or stock recovery? Given that the update script uses some kind of Motorola function to flash the bootloader, I'm assuming stock since I doubt ClockworkMod has Motorola functions built into it. On the off chance that I'm wrong though, can someone verify?
Sent from my Xoom using Tapatalk

oldblue910 said:
That's my point. So how do you flash it? ClockworkMod or stock recovery? Given that the update script uses some kind of Motorola function to flash the bootloader, I'm assuming stock since I doubt ClockworkMod has Motorola functions built into it. On the off chance that I'm wrong though, can someone verify?
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Hey bro just give some time I'll make a in depth tutorial seems like you your going to have to flash back to 3.0 flash the 1.50 boot then go back and flash the mz602
Sent from my Xoom using Tapatalk

amysdadforever said:
Hey bro just give some time I'll make a in depth tutorial seems like you your going to have to flash back to 3.0 flash the 1.50 boot then go back and flash the mz602
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Actually, if you use the bootloader image in combination with the SBF and 3.2.2 fastboot images from developer.motorola.com/xoomsoftware, you can flash back to totally stock with the 1.50 bootloader and the original LTE radio without having to flash back to 3.0.
For my MZ602, I just did the following tonight:
Go into ClockworkMod and flash the bootloader.
Reboot and watch the bootloader update screen.
When it reboots automatically, keep pressing down until you get the prompt.
Go into Fastboot mode.
Fastboot flash the 3.2.2 images (boot, system, recovery, and userdata) for MZ602 found at http://developer.motorola.com/xoomsoftare
Do a fastboot erase cache.
Powercycle the Xoom.
Press down on the bootloader until you get the prompt.
This time go into RSD mode.
Fire up RSD Lite on your PC, load up the SBF file, and press start.
Let it go.
When it's done, you'll be on stock 3.2.2 with the original LTE radio and original bootloader.
Oh, and cool that you're from Clovis. I was born and raised in Madera.

oldblue910 said:
Actually, if you use the bootloader image in combination with the SBF and 3.2.2 fastboot images from developer.motorola.com/xoomsoftware, you can flash back to totally stock with the 1.50 bootloader and the original LTE radio without having to flash back to 3.0.
For my MZ602, I just did the following tonight:
Go into ClockworkMod and flash the bootloader.
Reboot and watch the bootloader update screen.
When it reboots automatically, keep pressing down until you get the prompt.
Go into Fastboot mode.
Fastboot flash the 3.2.2 images (boot, system, recovery, and userdata) for MZ602 found at http://developer.motorola.com/xoomsoftare
Do a fastboot erase cache.
Powercycle the Xoom.
Press down on the bootloader until you get the prompt.
This time go into RSD mode.
Fire up RSD Lite on your PC, load up the SBF file, and press start.
Let it go.
When it's done, you'll be on stock 3.2.2 with the original LTE radio and original bootloader.
Oh, and cool that you're from Clovis. I was born and raised in Madera.
Click to expand...
Click to collapse
Oh cool saves me the troubles of making a tut thanks bro and good job on the fix. I guess your fix does well and yeah awesome why east coast tired of the farms

oldblue910 said:
Actually, if you use the bootloader image in combination with the SBF and 3.2.2 fastboot images from developer.motorola.com/xoomsoftware, you can flash back to totally stock with the 1.50 bootloader and the original LTE radio without having to flash back to 3.0.
For my MZ602, I just did the following tonight:
Go into ClockworkMod and flash the bootloader.
Reboot and watch the bootloader update screen.
When it reboots automatically, keep pressing down until you get the prompt.
Go into Fastboot mode.
Fastboot flash the 3.2.2 images (boot, system, recovery, and userdata) for MZ602 found at http://developer.motorola.com/xoomsoftare
Do a fastboot erase cache.
Powercycle the Xoom.
Press down on the bootloader until you get the prompt.
This time go into RSD mode.
Fire up RSD Lite on your PC, load up the SBF file, and press start.
Let it go.
When it's done, you'll be on stock 3.2.2 with the original LTE radio and original bootloader.
Oh, and cool that you're from Clovis. I was born and raised in Madera.
Click to expand...
Click to collapse
The point is have you seen the "Start LTE Software Bypass Mode" screen? And how did you pass through it? Because when my xoom boot into that screen, it lost connection with my computer(I checked the "Device Manager" actually, there is no unknown devices, no motorola flash interface, etc..)
So what operating system you are using? (I tried both Windows XP and Win7 64bits) And what's the cable you are using(stock cable or program cable)? Also did you plug your power when flash? Did you pull out your sim card? etc..

Its Work with MZ605/MZ601 3G ?

DragonEarth said:
Its Work with MZ605/MZ601 3G ?
Click to expand...
Click to collapse
It will definitely brick your xoom, don't ever try that.

DragonEarth said:
Its Work with MZ605/MZ601 3G ?
Click to expand...
Click to collapse
NOOO! This is for MZ602 (Verizon US 4G LTE version) ONLY!!! If you try this on ANY other Xoom model, you will brick it. Plain and simple.
---------- Post added at 11:18 AM ---------- Previous post was at 11:17 AM ----------
kerry_xu_cs said:
The point is have you seen the "Start LTE Software Bypass Mode" screen? And how did you pass through it? Because when my xoom boot into that screen, it lost connection with my computer(I checked the "Device Manager" actually, there is no unknown devices, no motorola flash interface, etc..)
So what operating system you are using? (I tried both Windows XP and Win7 64bits) And what's the cable you are using(stock cable or program cable)? Also did you plug your power when flash? Did you pull out your sim card? etc..
Click to expand...
Click to collapse
When it got to that screen for me, it lost connection temporarily, then found the device again, installed the motorola driver for it, and kept on going.

[Q] In Bootloop, Can you Help?

I was having some pretty serious radio issues with cyanogenmod so I attempted to use RSD Lite which had previously worked like a charm to go back to stock rom (using what came pre-bundled with matt's script v. 1.2)
My phone is unlocked at the bootloader
I have it rooted.
I get the original droid boot loop.
I can definitely get it into a status code 3 AP Fastboot, but none of the tools for the script or RSD lite have gotten me past the droid eye bootloop.
I'm presuming a wipe of the cache will do the trick, but either my googling skills are gone or I'm just too tired after 6 hours.... but I'm unable to get any type of recovery flashed.
My first question is if I am in AP Fastboot, who knows how to get a recovery image flashed so I can see if it's just a cache issue of trying to go from cyanogenmod to stock firmware.
My second question is - Does anyone have a link to a guide to "re-lock" my bootloader in case I need to get this to tech support?
Thanks

matthew1429 said:
I was having some pretty serious radio issues with cyanogenmod so I attempted to use RSD Lite which had previously worked like a charm to go back to stock rom (using what came pre-bundled with matt's script v. 1.2)
My phone is unlocked at the bootloader
I have it rooted.
I get the original droid boot loop.
I can definitely get it into a status code 3 AP Fastboot, but none of the tools for the script or RSD lite have gotten me past the droid eye bootloop.
I'm presuming a wipe of the cache will do the trick, but either my googling skills are gone or I'm just too tired after 6 hours.... but I'm unable to get any type of recovery flashed.
My first question is if I am in AP Fastboot, who knows how to get a recovery image flashed so I can see if it's just a cache issue of trying to go from cyanogenmod to stock firmware.
My second question is - Does anyone have a link to a guide to "re-lock" my bootloader in case I need to get this to tech support?
Thanks
Click to expand...
Click to collapse
First off, after you flash the firmware via fastboot, go back into recovery and do a factory reset. Second, you can't relock the bootloader.

thanks for responding. I wish it was this easy - it's been caught in a loop after trying factory again. I think I'd be able to resolve this if there were a way to wipe everything clear and build from scratch

RikRong said:
Second, you can't relock the bootloader.
Click to expand...
Click to collapse
No you cannot relock the bootloader...
Download this http://forum.xda-developers.com/showthread.php?p=40682385 chose option one... once flashed boot into recovery factory reset... boot up device... once booted root... install voodoo protect root install update restore root... install custom recovery if desired... I have boot looped I've been stuck at boot logo I've also been stuck with no data n WiFi this has saved me on more times then I can count on 3 separate devices and his utility n what I described has saved me more times then I can count...
Sent from my XT907 using xda app-developers app

I had some issues with aftermarket recoveries and formatting. I'm not sure if you've had any luck or if this is even helpful but assuming you are in fastboot and have the SDK set up...
Extract the stock sbf/XML and grab the recovery image.
At command line enter: "fastboot flash recovery recovery.img"
Reboot with all three buttons and select recovery.
Do factory reset.
Get back into fastboot
And repeat the command above (with different recovery obviously) to reflash a recovery of your choice.
(The official Philz cwm touch posted recently in development subforum works very well with the new 4.3 ROMs)
Hope that helps...if its too basic, please disregard! Good luck.
Sent from my XT907 using Tapatalk 2

fastboot boot on 4.4.4 WORKED!

So here's my story.
My device is :
S-ON, 4.4.4 Droid stock, 3.29.161.9.
Yesterday i tried to get root while keeping stock rom for no tampered msg at bootloader.
I was following guide from http://forum.xda-developers.com/showthread.php?p=51383278&highlight=ota#post51383278
so with unlocked bootloader i tried to fastboot boot CWM recovery image.
and it hanged my phone as everyone reported for > 4.4.3 ..... so i gave up for this time.
Today i was in mood for flashing some custom rom and then rooting, but with TWRP(newest 2.8.3.0).
just for gigles i tried to fastboot boot newest twrp. only thing i did was renaming .img file to recovery.img.
guess what? it worked! so i got root, reboot and started enjoying not tampered stock
So now im sharing this lil'christmas story with you.
Of course if it's irrevelant or already found please delete this topic.
happy christmas nevertheless.!

i'm on 4.1.1 and can't install room with 4.4.4 cus it's request 3.28.401.6 firmware or above and when i do it and trying
fastboot boot recovery.img
Click to expand...
Click to collapse
i can touch the recovery screen but cant see what i'm doing.
now using TWRP 2.8.3.0 the phone just doing reset and not going to recovery
any advice?

Plomiwn said:
...
just for gigles i tried to fastboot boot newest twrp. only thing i did was renaming .img file to recovery.img.
guess what? it worked! ...
Click to expand...
Click to collapse
Oh, really...?
Merry Christmas to you.
mb0 said:
i'm on 4.1.1 and can't install room with 4.4.4 cus it's request 3.28.401.6 firmware or above and when i do it and trying i can touch the recovery screen but cant see what i'm doing.
now using TWRP 2.8.3.0 the phone just doing reset and not going to recovery
any advice?
Click to expand...
Click to collapse
Use older recovery. That one has new display drivers.
Merry Christmas to you too.
Sent from my HTC One_M8 using Tapatalk

this is what i get when upgrading the firmware http://oi58.tinypic.com/e0jxqq.jpg
was using Stock Firmware + NoRedText Hboot from here: http://forum.xda-developers.com/htc-one-m8/development/ota-3-28-401-6-t2899900
been trying the following recovery files:
openrecovery-twrp-2.7.0.1-m8 - not working, screen stuck in fastboot
openrecovery-twrp-2.8.0.0-m8 - going reset
* to be clear: this "no display" in the recovery thing happening only after i flash InsertCoin 5.0.6 http://insertcoin-roms.org/2014/12/...rol-market-ota-icon-packs-stable-performance/
(haven't flashed another room yet)
now i need do what i always do when this happen:
- fastboot oem rebootRUU
- fastboot flash zip 2.22.401.4-Firmware-noredtext
after that go back to recovery and restore the backup i made before.

mb0 said:
this is what i get when upgrading the firmware http://oi58.tinypic.com/e0jxqq.jpg
was using Stock Firmware + NoRedText Hboot from here: http://forum.xda-developers.com/htc-one-m8/development/ota-3-28-401-6-t2899900
been trying the following recovery files:
openrecovery-twrp-2.7.0.1-m8 - not working, screen stuck in fastboot
openrecovery-twrp-2.8.0.0-m8 - going reset
* to be clear: this "no display" in the recovery thing happening only after i flash InsertCoin 5.0.6 http://insertcoin-roms.org/2014/12/...rol-market-ota-icon-packs-stable-performance/
(haven't flashed another room yet)
now i need do what i always do when this happen:
- fastboot oem rebootRUU
- fastboot flash zip 2.22.401.4-Firmware-noredtext
after that go back to recovery and restore the backup i made before.
Click to expand...
Click to collapse
not sure what your point is ? this thread is about booting the LATEST twrp on the LATEST firmware because older ones couldn't boot but could only be flashed.

arg cant get into recovery

ok so i have a razr m i got on ebay. It looks flawless
i unlocked the boot loader and rooted it.
i went into fast boot and pushed cwm 6.0.4.4. I could only get into the boot loader with the key presses "not adb reboot bootloader"
when I go into rom manager i see that i have the latest version of cwm
but I cant boot into recovery
it just shows the boot loader unlocked screen for a while then boots to the regular red eye and regular system
also could not flash cm12 nioghtly from rom manager.
do I just need to rsd the whole thing and start overt?

i retried flashing recovery with mfastboot and it didn't work any better
adb reboot recovery
just the unlocked bootloader screen for a while and then evenutally went into regular boot

ok getting somewhere
i tried a newer version of mfastboot and put the stock recovery back on.
i can now boot to the stock recovery.
i saw that there were issues with the recovery-clockwork-6.0.4.4-xt907.img
what recovery should I be using i am on 4.4.2 183.46.15
i want to get to cm12 eventually
i have tried a number of recoveries. XT901-XT907-TWRP-2.6.3.0-recovery is one

dcooterfrog said:
ok getting somewhere
i tried a newer version of mfastboot and put the stock recovery back on.
i can now boot to the stock recovery.
i saw that there were issues with the recovery-clockwork-6.0.4.4-xt907.img
what recovery should I be using i am on 4.4.2 183.46.15
i want to get to cm12 eventually
i have tried a number of recoveries. XT901-XT907-TWRP-2.6.3.0-recovery is one
Click to expand...
Click to collapse
ha ha this one
cm-recovery-xt907-1-18-15.img
will this one work as well
twrp-2.8.4.2-xt907