Related
\\\Disclaimer: I am not responsible if you mess this up & break your phone///
Checking Your Situation:
*Phone only boots to Fastboot
*Phone does/Doesn't charge
*Power button Seems useless
*Phone Turns on and only shows-
the X screen & Vibrates 7x's
*LED Only shows Green/ Orange
indication light
Things You'll Need:
*Wall Charger
*USB Cable
*Computer (duh)
*Battery (of course)
*FRG83 ROM file http://tinyurl.com/6bym3vg
*Android ADB Setup
*Fingers Crossed
(Tip: if you are using the same Sdcard when the phone messed up, reformat it or use a new one)
Step One:
Download FRG83 ROM file http://tinyurl.com/6bym3vg
and unzip the package into your AndroidSDK Tools Folder
Step Two:
Watch the battery trick video
http://youtu.be/2O5adV-jj64 (Thanks n1newbie)
Once you've analyzed the video enough
plug your phone (while it's off) to the wall
charger and while doing the wall trick !!Make
sure you hold down the Volume-Down Button!! so
you can boot into fastboot.
Step Three:
Once established fastboot, plug the phone
to your computer and let your computer discover the
device.
!!Make sure the device says Fastboot USB!!
Open Command Promt (CMD). If you already
know how to use Android ADB type these commands:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
fastboot devices
!!Make Sure You Device ID Shows UP!!
fastboot erase userdata
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Let the phone run everything through and you should
be one Froyo.
Step Four:
Power down your phone
Reboot into Recovery (to see if your phone is still rooted)
If you are able to get into recovery flash any ROM
you like and Enjoy your UnBricked Nexus One
lilj4321 said:
If anyone needs the fix for this soft brick
let me know so i can post instructions!
Click to expand...
Click to collapse
You might as well write them out. You never know when someone will need them.
taodan said:
You might as well write them out. You never know when someone will need them.
Click to expand...
Click to collapse
+1. will be very useful n helpful when that occurs. so pls explain the method. thanx
Sent from my Nexus One using Tapatalk
n1newbie said:
+1. will be very useful n helpful when that occurs. so pls explain the method. thanx
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
+2, hope it won't occurs
hi lilj4321. thanx for the steps frnd
the youtube link that you provided returns 404 error. so you might use this link for video trick (by myself )
PS- sry if i am wrng. will the device boot into fastboot mode after the seven vibration brick happens
Sent from my Nexus One using Tapatalk
fixed the link!
no the phone will stay on the X screen until your battery dies
which is why you have to do the battery trick while holding the
volume-down button during the whole process.
lilj4321 said:
fixed the link!
no the phone will stay on the X screen until your battery dies
which is why you have to do the battery trick while holding the
volume-down button during the whole process.
Click to expand...
Click to collapse
oh okies. thanx for using my video buddy
will try this if seven vibration brick happens. but ill pray it shdnt happen
will be helpful for all if it is stickied :thumbup:
just my 2 cents ...
Sent from my Nexus One using Tapatalk
I hoped for something much more useful.
The method of reflashing to stock using fastboot commands has been posted on Nexus One Wiki for 2.5 years now.
And of course, it won't solve any overheating phone, and no "7-vibration brick".
Thanks for trying to help, but the post is kinda (very) useless.
Stuck in fastboot
My phone went into this rare phenomonen "7vibrations no boot"... its been 2weeks. Im not able to fix it till now.
Firstly , My phone doesnt respond in hboot screen when the sdcard is inserted. So for entering fastboot, I will take out sdcard and go to fastboot and then put my sdcard when the phone is connected to PC so that it doesnt turnoff when i pullout the battery. this i have been facing for quite long. cudnt fix it.
I tried exactly what you said.. but im stuck in the fastboot now.. im not able to flash anything using adb in fastboot.
im getting errors in fastboot.
when i typed 'fastboot flash system system.img"
it gives an error like "error: cannot load 'system.img' : unknown error"
did "fastboot erase" and it worked.
but flashing is not happening.
please help me out
---------- Post added at 08:22 PM ---------- Previous post was at 08:02 PM ----------
i somehow managed to flash all those things what u said in your post...
but still when rebooted after flashing via fastboot, the same 7 vibrations happening.
My phone doesnt boot..
i havent done the battery trick as you said. Im not able to do it. That video doesnt have any instruction and no audio too.
any instruction on how to do it will be helpful.
ajaymkd said:
My phone went into this rare phenomonen "7vibrations no boot"... its been 2weeks. Im not able to fix it till now.
Firstly , My phone doesnt respond in hboot screen when the sdcard is inserted. So for entering fastboot, I will take out sdcard and go to fastboot and then put my sdcard when the phone is connected to PC so that it doesnt turnoff when i pullout the battery. this i have been facing for quite long. cudnt fix it.
I tried exactly what you said.. but im stuck in the fastboot now.. im not able to flash anything using adb in fastboot.
im getting errors in fastboot.
when i typed 'fastboot flash system system.img"
it gives an error like "error: cannot load 'system.img' : unknown error"
did "fastboot erase" and it worked.
but flashing is not happening.
please help me out
---------- Post added at 08:22 PM ---------- Previous post was at 08:02 PM ----------
i somehow managed to flash all those things what u said in your post...
but still when rebooted after flashing via fastboot, the same 7 vibrations happening.
My phone doesnt boot..
i havent done the battery trick as you said. Im not able to do it. That video doesnt have any instruction and no audio too.
any instruction on how to do it will be helpful.
Click to expand...
Click to collapse
After doing all the stuffs, and after fastboot reboot.. The phone on the same state.. Brick state with 7 vibrate + X sign. Why is that so?
OMG!!! I've hit the end of my rope with this. Let me start off by saying I don't post things, I find answers to them but this problem is killing me.
I have a Sprint Nexus 6 that I am trying to update to 5.0.1. However its being terrible, I reboot into bootloader with with power and volume - or adb reboot bootloader, and attempt to adb sideload (updatefile.zip) and error device not found. I do adb devices and sure enough its not there, however fastboot devices shows it. If I reboot into the OS and issue ADB devices OH **** THERE IS MY PHONE, adb reboot bootloader, and its gone again.
I've tried drivers froom google search direct google usb drivers, naked drivers 0.73, I've uninstalled inside of the os and reinstalled I've uninstalled in bootloader and reinstalled nothing works. I can issue fastboot commands but adb just eats a bag of ****. I also have an issue where adb gives an error that it is out of date and must restart, it then restarts and everything is peachy. I've tried to download something called adb fix, but it says there is nothing wrong. So I have no idea what is going on and if anyone could possibly help me get my phone updated so this notification goes away and I don't go into an OCD rage on everyone around me I would be much appreciative.
Side note
I cannot update via ota, no idea why it says installing then just errors out, I assumed it was because of the unlock, also when I'm in bootloader and I attempt to go into recovery there is just an android dude with his chest open. Now its been a while since I've had a nexus but shouldn't there be like a menu or something there? I also did the whole no encrypt boot.img nonsense here. I thought that was the problem so wiped data and flashed the stock boot.img... I'm seriously out of ideas......
well first off you have the stock recovery... that is the android dude.
I dont really have answers for you but the two things i would try would be a different computer and just using WUG http://www.wugfresh.com/nrt/ i have had issues in the past using an old ADB/fastboot.
If you have modified anything the OTA is going to fail.
Tried on two different computers,I'll try wug. Thanks
first, make sure that you can see the device when it's booted up (assuming usb debug is enabled and the computer is trusted).
other than that, i'm not sure what to say as i've never had that problem (i don't use the updater.zip files though). might be best to just flash the whole 5.0.1 image (minus the cache and userdata).
Maybe I am reading this wrong, but you are trying to adb while in the bootloader?
PaisanNYC said:
Maybe I am reading this wrong, but you are trying to adb while in the bootloader?
Click to expand...
Click to collapse
If you're reading it wrong so am I. Definitely sounds like he is incorrectly trying to use Adb in the bootloader.
---------- Post added at 11:15 PM ---------- Previous post was at 11:13 PM ----------
Lucke said:
first, make sure that you can see the device when it's booted up (assuming usb debug is enabled and the computer is trusted).
other than that, i'm not sure what to say as i've never had that problem (i don't use the updater.zip files though). might be best to just flash the whole 5.0.1 image (minus the cache and userdata).
Click to expand...
Click to collapse
USB debug mode has nothing to do with boot loader or recovery. I'm sure you know this as you said it when booted, but many will read this and think you need debug in recovery or bootloader which wouldn't be true.
Hi all, I did a dumb thing and I took the recent Verizon OTA on my dev ed moto x with a custom recovery installed (TWRP).
Now my phone seems to always stop booting at recovery, then if i hit 'reboot system' from recovery, I can get into my system for about 2-3 minutes, and then it reboots to recovery again.
Any help would be greatly appreciated!
boot your phone into fastboot/bootloader mode, then flash stock Recovery on your phone and reboot normally.
KidJoe said:
boot your phone into fastboot/bootloader mode, then flash stock Recovery on your phone and reboot normally.
Click to expand...
Click to collapse
Thanks KidJoe - I'm reading through your post on xda right now to see how you flash back to the stock recovery and I'm currently downloading the stock image from one of your links.
While I'm waiting, I'm going over my options for how to actually flash the stock recovery - your post said that i should try Rashr - however my device probably won't stay 'on' long enough for me to get through that process. After it boots into the system (e.g. I see my launcher and apps), it wants to restart since I guess it's trying to the upgrade. So I'm thinking of instead using adb to flash the recovery.img file. Is that the right path to take?
Also - would it be okay to use adb to flash the recovery.img using TWRP's adb sideload feature? I seem to be able to connect using adb that way, but for some reason 'adb devices' doesn't list anything under fastboot.
switch81 said:
Thanks KidJoe - I'm reading through your post on xda right now to see how you flash back to the stock recovery and I'm currently downloading the stock image from one of your links.
While I'm waiting, I'm going over my options for how to actually flash the stock recovery - your post said that i should try Rashr - however my device probably won't stay 'on' long enough for me to get through that process. After it boots into the system (e.g. I see my launcher and apps), it wants to restart since I guess it's trying to the upgrade. So I'm thinking of instead using adb to flash the recovery.img file. Is that the right path to take?
Also - would it be okay to use adb to flash the recovery.img using TWRP's adb sideload feature? I seem to be able to connect using adb that way, but for some reason 'adb devices' doesn't list anything under fastboot.
Click to expand...
Click to collapse
First, if you can't boot your phone into Android, you can't use Rashr.
Next... ADB needs you to be up in Android, and have the "USB Debugging" options checked. Also, it can not be used to flash the components of the SBF/ROM like recovery.img.
Fastboot mode works with Fastboot.exe or mFastboot.exe... ADB commands do not work when the phone is in fastboot mode.
Here is what you want to do AFTER you have the stock reocvery.img you want to flash... (this is pretty much exactly what you did to flash TWRP on there in the first place, except you will be flashing a stock recovery.img instead)
have the latest Moto drivers installed. You can get them from -> https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Make sure you have the Android SDK/Platform Tools installed (don't know how, see -> http://mark.cdmaforums.com/ADB.htm )
You need the latest version of Moto's fastboot, and it needs to be put in your windows Path (there are steps on -> http://mark.cdmaforums.com/ADB.htm )
Once you have that... do the following...
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in fastboot menu on phone.
Connect to PC.
open command prompt file and change to the folder you have your recovery.img you want to flash
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery recovery.img
mfastboot reboot-bootloader
The device will display different BOOT OPTIONS
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
The device will display the Motorola logo and then the Android in distress (logo with Exclamation mark)
Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key
You should enter STOCK recovery.
use the VOL DOWN Key to scroll and the POWER Key to select reboot.
The phone should reboot and and be ready for the update
I did the same thing and was able to undo it by clearing the cache. Now I'm back to where I was before, with the constant notification to update.
Wondering what the correct way to go about updating is..
*Edit: Thanks!
Moto X Dev
Thanks! I'm back up and running!
Sorry for the confusion on the adb vs fastboot stuff - I always mix those kinds of things up since I do it once ages ago to get myself into this mess, then I forget how I did it and what tools I used.
So basically what I did was use fastboot like you said and first booted into fastboot, then did a 'fastboot flash recovery recovery.img' from a stock recovery.
After a full reboot, android ended up giving me a 'update was unsuccessful' which I am totally 100% okay with. I ended pushing 'update' the first time really because I was tired of getting nagged - this time i just said 'don't install' and hopefully it won't bother me agian.
Thanks again!
slynke said:
I did the same thing and was able to undo it by clearing the cache. Now I'm back to where I was before, with the constant notification to update.
Wondering what the correct way to go about updating is..
*Edit: Thanks!
Moto X Dev
Click to expand...
Click to collapse
I'm sure KidJoe will respond, but I found this thread of his very useful:
http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079
switch81 said:
Thanks! I'm back up and running!
Sorry for the confusion on the adb vs fastboot stuff - I always mix those kinds of things up since I do it once ages ago to get myself into this mess, then I forget how I did it and what tools I used.
So basically what I did was use fastboot like you said and first booted into fastboot, then did a 'fastboot flash recovery recovery.img' from a stock recovery.
After a full reboot, android ended up giving me a 'update was unsuccessful' which I am totally 100% okay with. I ended pushing 'update' the first time really because I was tired of getting nagged - this time i just said 'don't install' and hopefully it won't bother me agian.
Thanks again!
Click to expand...
Click to collapse
I was able to flash back to stock recovery and take the 212.166.3 build KXA21.12-L1.26-3 (which is still 4.4.4) OTA that Verizon is pushing out.
I didn't even have to disable Xposed or anything else. Then again, other than Xposed, root and twrp, I'm running stock. No tethering hacks, build.prop changes, no system files removed or renamed, etc.
---------- Post added at 01:18 PM ---------- Previous post was at 01:16 PM ----------
slynke said:
I did the same thing and was able to undo it by clearing the cache. Now I'm back to where I was before, with the constant notification to update.
Wondering what the correct way to go about updating is..
*Edit: Thanks!
Moto X Dev
Click to expand...
Click to collapse
Yup., Clearing cache will delete the OTA ZIP file that was downloaded. So the next time you reboot, it wont try to install, instead you'll be back to being notified that an update is available asking you if you want to download it.
But yup, those instructions I just typed should work...
This OTA seems so minimal in changes, any suggestions/recommendations if I should take it at all?
I'm also pretty much stock now as well - only root, xposed installed.
switch81 said:
This OTA seems so minimal in changes, any suggestions/recommendations if I should take it at all?
I'm also pretty much stock now as well - only root, xposed installed.
Click to expand...
Click to collapse
The release notes on VZW's page only seems to mention bug fixes.. no real details.
So far I haven't noticed any changes.
It will likely be a required step to get to lollipop. So either take it now, or wait and take it later, just before you upgrade to Lolliop
The other day I was using my phone and it started to die on me so I plugged it in to charge. I guess it was too low power, so when I plugged it in, it powered down and started charging via phone off. Later I come back to turn it on and it just gets stuck in bootloop. I haveTWRP installed so I cleared the dalvik cache and regular cache. That didn't work. So the next time I just did a factory restore, well after the restore I now have no files on my phone. No OS nothing.
When I plug the phone in via USB the computer chimes and lets me know something was plugged in but I don't get any other messages. If I plug my phone in while in recovery it shows the device with zero folders.
I am sure I can fix it from here, but while using WUGS Root Tool Kit my computer keeps telling me that no "FastBoot Devices" found. How do I fix that?
I would like to just flash an image if possible if someone can walk me through the process or any help would be great.
bannworthrulz said:
The other day I was using my phone and it started to die on me so I plugged it in to charge. I guess it was too low power, so when I plugged it in, it powered down and started charging via phone off. Later I come back to turn it on and it just gets stuck in bootloop. I haveTWRP installed so I cleared the dalvik cache and regular cache. That didn't work. So the next time I just did a factory restore, well after the restore I now have no files on my phone. No OS nothing.
When I plug the phone in via USB the computer chimes and lets me know something was plugged in but I don't get any other messages. If I plug my phone in while in recovery it shows the device with zero folders.
I am sure I can fix it from here, but while using WUGS Root Tool Kit my computer keeps telling me that no "FastBoot Devices" found. How do I fix that?
I would like to just flash an image if possible if someone can walk me through the process or any help would be great.
Click to expand...
Click to collapse
you wiped system, which wipes your rom off your phone. its a VERY easy fix.. just move whatever rom/gapps/supersu to your phone via twrp or adb, then flash it via twrp.
---------- Post added at 12:38 PM ---------- Previous post was at 12:37 PM ----------
btw.. dont use toolkits. LEARN how to things yourself, its much easier.
Hello
simms22 said:
you wiped system, which wipes your rom off your phone. its a VERY easy fix.. just move whatever rom/gapps/supersu to your phone via twrp or adb, then flash it via twrp.
---------- Post added at 12:38 PM ---------- Previous post was at 12:37 PM ----------
btw.. dont use toolkits. LEARN how to things yourself, its much easier.
Click to expand...
Click to collapse
Could you point me in the direction to the rom/gapps/superu?
bannworthrulz said:
Could you point me in the direction to the rom/gapps/superu?
Click to expand...
Click to collapse
which rom? there are many. even a twrp flashable stock rom.
bannworthrulz said:
Could you point me in the direction to the rom/gapps/superu?
Click to expand...
Click to collapse
Also I installed a stock version of android off the factory images page and copied it over to my phone but TWRP cannot find the zip file?
simms22 said:
which rom? there are many. even a twrp flashable stock rom.
Click to expand...
Click to collapse
Just any stock ROM, I downloaded one from https://developers.google.com/android/nexus/images#fugu but it doesn't show up in TWRP.
bannworthrulz said:
Also I installed a stock version of android off the factory images page and copied it over to my phone but TWRP cannot find the zip file?
Click to expand...
Click to collapse
to flash a factory image, you need to flaah it while in the bootloader, using fastboot. its not a zip.
---------- Post added at 01:15 PM ---------- Previous post was at 01:12 PM ----------
a stock-like rom http://forum.xda-developers.com/nexus-6/development/rom-rooted-deoxeded-fast-stable-t3252922
simms22 said:
to flash a factory image, you need to flaah it while in the bootloader, using fastboot. its not a zip.
Click to expand...
Click to collapse
Honestly man, you are talking to someone who doesn't understand a lot about these things. I need detailed instruction on how to do this. I now don't have twrp installed. I tried to install CM13 and now its stuck in cyanogen recovery mode. This really sucks and need help on how to fix it. Also while in bootloader mode. It says FASTBOOT DEVICE NOT FOUND if it were found I would not be having this issue. I would have a stock rom installed and be on my way. Since it isn't able to find a FASTBOOT DEVICE that is why I am in this current situation.
NVM I figured it out. Had to install adb-setup-1.4.2.exe and now my phone is fixed and up and running.
bannworthrulz said:
Honestly man, you are talking to someone who doesn't understand a lot about these things. I need detailed instruction on how to do this. I now don't have twrp installed. I tried to install CM13 and now its stuck in cyanogen recovery mode. This really sucks and need help on how to fix it. Also while in bootloader mode. It says FASTBOOT DEVICE NOT FOUND if it were found I would not be having this issue. I would have a stock rom installed and be on my way. Since it isn't able to find a FASTBOOT DEVICE that is why I am in this current situation.
NVM I figured it out. Had to install adb-setup-1.4.2.exe and now my phone is fixed and up and running.
Click to expand...
Click to collapse
yup, installing it first helps out, a lot :silly:
bannworthrulz said:
... WUGS Root Tool Kit my computer keeps telling me that no "FastBoot Devices" found. How do I fix that?
Click to expand...
Click to collapse
Boot twrp recovery first....
Hey all, so I got the dreaded Func 11 error mode on my device.
I had updated to Oreo, and was attempting to install a Lineage treble build. I think I flashed the wrong one and I tried to flash back to stock by using the oreo update method. Unfortunately what appears to have happened is that I've somehow destroyed my recovery side of things.
I can access Fastboot and tried to flash TWRP, but this fails to load (gets stuck on 'Your device is now booting').
I'm out of ideas as to what to try now. Does anyone have any suggestions? To make matters worse my battery is also now dead.
Any help is much appreciated and apologies if this is just a repeat of another thread.
I had the same error, I sent it to tech service, I have no idea how to fix that, my phone was stuck at "your device is booting now", no way to enter into recovery.
I hope you can fix your phone bro. :/
I did the same as you and got the same problem, I had to send my device away and get it repaired by an authorized repair agent. They ended up having to put in a new main board into my phone.
if you can access fastboot you need wait on error mode screenbattery die,when phone close taje charge your phone wait open otomaticly
---------- Post added at 04:53 AM ---------- Previous post was at 04:49 AM ----------
if you cant access fastboot mode,you need wait battery draind finish, when phone shut down plug the charger and wait phone automatically open,,then try reach fastboot mode,after that flash kernel_ramdik after that flash twrp again for oreo
volpula said:
if you can access fastboot you need wait on error mode screenbattery die,when phone close taje charge your phone wait open otomaticly
---------- Post added at 04:53 AM ---------- Previous post was at 04:49 AM ----------
if you cant access fastboot mode,you need wait battery draind finish, when phone shut down plug the charger and wait phone automatically open,,then try reach fastboot mode,after that flash kernel_ramdik after that flash twrp again for oreo
Click to expand...
Click to collapse
I can access no fastboot no problem. Only problem is battery is completely dead and every time I try to charge it just reboots to error mode when I plug it in. Can't access the recovery unfortunately and I know there isn't any fastboot command for it from what I can find.
if you can access fastboot mode,you need use extractor for your oreo files,extract kernel and ramdisk.img and flash,after that flash twrp recovery again
Well I'm off to work now where I have access to a windows PC. I'll see what I can do, otherwise I'll try DC Unlocker if need be. I don't believe I need to send it back for repair as that seems like a bit much for what's clearly not a hardware issue.
no you dont need send to repair,thats software issues.huawei is really terrible company.kirin chipset its slow then snapdragon or exynos cpu and cpu,camera just take good picture thats all not take good video like galaxy phones,software is very bad recovery system worst in the anroid phones i even use before.developer cant cook custom roms,i never buy huawei phone again and ibcant recoment anybody to buy.they dont deserve that prices
volpula said:
if you can access fastboot mode,you need use extractor for your oreo files,extract kernel and ramdisk.img and flash,after that flash twrp recovery again
Click to expand...
Click to collapse
All images flashed. I still can't get in to recovery however due to the battery being depleted.
It won't simply just charge and reboots to Error Mode. If anyone knows of a way around this that would be great. Are there fastboot instructions to get to recovery?
MrDanMak said:
All images flashed. I still can't get in to recovery however due to the battery being depleted.
It won't simply just charge and reboots to Error Mode. If anyone knows of a way around this that would be great. Are there fastboot instructions to get to recovery?
Click to expand...
Click to collapse
are you sure flash correctly files?you need oreo recovery.img,ramdisk.img and twrp8.img.you need to be access to twrp
volpula said:
if you can access fastboot mode,you need use extractor for your oreo files,extract kernel and ramdisk.img and flash,after that flash twrp recovery again
Click to expand...
Click to collapse
volpula said:
are you sure flash correctly files?you need oreo recovery.img,ramdisk.img and twrp8.img.you need to be access to twrp
Click to expand...
Click to collapse
Yes I have flashed correctly via fastboot. My phone just can't get enough battery charge to be able to boot to recovery it seems.
Ok, I'm on Oreo and I'm gonna give DC Phoenix a shot. Does anyone know which firmware files I need to download? Device is VTR-L09C432
MrDanMak said:
Yes I have flashed correctly via fastboot. My phone just can't get enough battery charge to be able to boot to recovery it seems.
Click to expand...
Click to collapse
you need reach twrp recovery.when you be in twrp take charge your phone %30 or %50.restart your phone press volume up when you see warning you need able to twrp.after that.copy hwota8_update.zip,Mha_recovery nocheck.img and vtr-l09c432b217 files.make new folder HWOTA8 and put this files,make wipe after that flash hwota8_update.zip
---------- Post added at 11:02 AM ---------- Previous post was at 10:59 AM ----------
MrDanMak said:
Ok, I'm on Oreo and I'm gonna give DC Phoenix a shot. Does anyone know which firmware files I need to download? Device is VTR-L09C432
Click to expand...
Click to collapse
if you wanna rollback 7.0 nougat you need VTR-L09B217
Device has been rescued thanks to DC Phoenix and the latest Oreo update.
nice to hear