Compatible Devices:
LG K8+
LG Aristo 2, 2+
LG K9
LG Phoenix 4
Thanks to @AustinGarrick1818 who discovered that this TWRP originally started and developed for the Aristo 2, by @messi2050 and @armandop_, then later updated to the latest version by @tecknight, was able to be flash on the Phoenix 4 leading to the idea that any cv1 device is cable of a ROOT method/TWRP Recovery.
Pre-Requisites:
USB Debugging Enabled
OEM Unlock Enabled
ADB/Fastboot Device Drivers
Your Phone/Brain
Hey guys! Just a heads up, I'm not responsible for any bricked devices or broken devices. So flash at your own risk! This TWRP has the Oreo Kernel from the Aristo 2's Oreo Firmware release.
Downloads
Latest Recovery by @tecknight Here --> https://www.androidfilehost.com/?fid=11410963190603906754Latest USB Drivers --> https://www.lg.com/us/support/software-firmware-drivers
Instructions:
1. Install the ADB Drivers from above. If you have them don't bother. Just move on. If you don't then make sure to install them somewhere easily accessible, as your gonna want to get to them easily.
2. Place the TWRP image in the ADB Folder for later use and plug your phone into your PC. Then press (Shift+Right Click) and select "Open Command Prompt Here".
3. After that type the next few lines of code:
Code:
adb devices
Code:
adb reboot bootloader
4. It should boot into fastboot mode. From there type:
Code:
fasboot devices
Code:
fastboot flashing unlock
5. To prevent fastboot from encrypting cache and data type:
Code:
fastboot erase userdata
Code:
fastboot erase cache
6.Remember the Recovery image? Rename it to rec.img and flash it like this:
Code:
fastboot flash recovery rec.img
7. Now that you've flashed TWRP test it:
Code:
fastboot reboot recovery
NOTE: Anytime you boot up your phone you will get a message saying that the bootloader is locked and you need to lock it. Don't do it. If you do then you phone will soft brick and get stuck in a bootloop. Just let it boot.
8. If you did everything right you should be brought to TWRP.
PLEASE LEAVE A THANKS! THANKS!
Downgrade?
Hey man thanks for pointing out that this will work with the all cv1 devices... I have the Aristo 2 on Metro... Is it possible to flash twrp while on the official Oreo firmware or do I have to downgrade to Nougat?
Last time I was on xda it was stated that you couldn't flash in fastboot while on official Oreo...
tdawgg777 said:
Hey man thanks for pointing out that this will work with the all cv1 devices... I have the Aristo 2 on Metro... Is it possible to flash twrp while on the official Oreo firmware or do I have to downgrade to Nougat?
Last time I was on xda it was stated that you couldn't flash in fastboot while on official Oreo...
Click to expand...
Click to collapse
Yah, it's still like that unfortunately. But you can downgrade to Nougat with LG Uppercut. You should just flash the TWRP on Nougat firmware because it's not locked. So when you downgrade just follow these steps to get Oreo. Also don't install Tec's version of Oreo Firmware. Just jump to my other thread for my Custom Stock ROM. Tec's flashes Oreo Firmware with Oreo Stock Rooted. But mine just flashes the nesassary Oreo Boot and System. The links on my signature.
By the way for anyone wondering the LG Phoenix 4 can be Rooted this way to.
NonStickAtom785 said:
Compatible Devices:
LG K8+
LG Aristo 2, 2+
LG K9
LG Phoenix 4
Thanks to @AustinGarrick1818 who discovered that this TWRP originally started and developed for the Aristo 2, by @messi2050 and @armandop_, then later updated to the latest version by @tecknight, was able to be flash on the Phoenix 4 leading to the idea that any cv1 device is cable of a ROOT method/TWRP Recovery.
Pre-Requisites:
USB Debugging Enabled
OEM Unlock Enabled
ADB/Fastboot Device Drivers
Your Phone/Brain
Hey guys! Just a heads up, I'm not responsible for any bricked devices or broken devices. So flash at your own risk! This TWRP has the Oreo Kernel from the Aristo 2's Oreo Firmware release.
Downloads
Latest Recovery by @tecknight Here --> https://www.androidfilehost.com/?fid=11410963190603906754
Latest USB Drivers --> http://tool.cdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Instructions:
1. Install the ADB Drivers from above. If you have them don't bother. Just move on. If you don't then make sure to install them somewhere easily accessible, as your gonna want to get to them easily.
2. Place the TWRP image in the ADB Folder for later use and plug your phone into your PC. Then press (Shift+Right Click) and select "Open Command Prompt Here".
3. After that type the next few lines of code:
4. It should boot into fastboot mode. From there type:
5. To prevent fastboot from encrypting cache and data type:
6.Remember the Recovery image? Rename it to rec.img and flash it like this:
7. Now that you've flashed TWRP test it:
NOTE: Anytime you boot up your phone you will get a message saying that the bootloader is locked and you need to lock it. Don't do it. If you do then you phone will soft brick and get stuck in a bootloop. Just let it boot.
8. If you did everything right you should be brought to TWRP.
PLEASE LEAVE A THANKS! THANKS!
Click to expand...
Click to collapse
If fastboot flashing unlock fails try fastboot oem unlock
tdawgg777 said:
Hey man thanks for pointing out that this will work with the all cv1 devices... I have the Aristo 2 on Metro... Is it possible to flash twrp while on the official Oreo firmware or do I have to downgrade to Nougat?
Last time I was on xda it was stated that you couldn't flash in fastboot while on official Oreo...
Click to expand...
Click to collapse
As long as your bootloader is unlocked it won't be a problem at least on the LG Phoenix 4 it can have TWRP with Oreo
hello good night I can not enter bootloader mode I always reboot in normal mode the phone, I do it this way c: adb / adb reboot bootloader but I started normal tengop a lg k9 x210em I do not understand the truth any suggestion excuse my English
hello good night I can not enter bootloader mode I always reboot in normal mode the phone, I do it this way c: adb / adb reboot bootloader but I started normal, a lg k9 x210hm I do not understand the truth any suggestion
tazlooney89 said:
hello good night I can not enter bootloader mode I always reboot in normal mode the phone, I do it this way c: adb / adb reboot bootloader but I started normal, a lg k9 x210hm I do not understand the truth any suggestion
Click to expand...
Click to collapse
on my device is the same
Problem!!!
I do what you write in tutorial but my phone dont run on fastboot mode Please HELP!!!
Do we know anything about unbricking these phones? I've got a US Cellular K8+ (LG-X210ULM) that my wife accidentally bricked a while back while trying to flash TWRP (not this particular build, obviously). I think she said everything seemed fine and then on reboot...well, it just never turned on again. PC doesn't pick it up at all, no Qualcomm mode or anything. Based on that, I had assumed it was a lost cause that would take JTAG to bring back, and it may well be...
...but then I noticed something unusual the other day. For the hell of it, I decided to plug it into a charger and let it sit for a while. I got what I expected, which was nothing at all. Oh well. Anyway, I happened to be working with another X210 at the time but only had one battery handy, so I just popped the one out of the "dead" phone without unplugging it and went about with what I was doing. After about 5-10 minutes, something caught my eye - sure enough, the dead phone's screen was now on, displaying the "?" battery screen. I put the battery back into the phone and got unceremoniously dumped straight back to black nothingness. Oh well.
So yeah, the phone still doesn't seem to respond to anything when connected to the PC with no battery, so it's probably a no-go, but the fact that it still shows the no-battery screen tells me it's not quite *as* bricked as I thought it was at least. Any ideas? Are we lucky enough to do a boot-from-SD trick on this phone?
Lmx210cm twrp
Do you happen to have anything for the lmx210cm?
Ausboz said:
Do you happen to have anything for the lmx210cm?
Click to expand...
Click to collapse
Just created a whole EDL firmware for the Aristo 2 aka Phoenix 4. PM me for the links if you'd like a copy. I also found our prog_emmc_firehose_8917_ddr.mbn to flash with (it works)
---------- Post added at 05:16 AM ---------- Previous post was at 05:13 AM ----------
tdawgg777 said:
Hey man thanks for pointing out that this will work with the all cv1 devices... I have the Aristo 2 on Metro... Is it possible to flash twrp while on the official Oreo firmware or do I have to downgrade to Nougat?
Last time I was on xda it was stated that you couldn't flash in fastboot while on official Oreo...
Click to expand...
Click to collapse
I tested oreo and it works file
AustinGarrick1818 said:
Just created a whole EDL firmware for the Aristo 2 aka Phoenix 4. PM me for the links if you'd like a copy. I also found our prog_emmc_firehose_8917_ddr.mbn to flash with (it works)
---------- Post added at 05:16 AM ---------- Previous post was at 05:13 AM ----------
I tested oreo and it works file
Click to expand...
Click to collapse
Hi would mind telling how to flash that firmware amd whats the prog_+++++++ddr.mbn to flash i have aristo 2 android 8.1 metro and i cant do any flash in fastboot or root it anything you know about it will be appreciated so much...
@NonStickAtom785 Any solution to start fastboot mode, the phone? Whenever I try to start it from CMD the phone restarts normally, there is no way to get into fastboot mode.
I already probe manually, with combination of buttons, and it does not work either, the model is the LX210HM
tazlooney89 said:
@NonStickAtom785 Any solution to start fastboot mode, the phone? Whenever I try to start it from CMD the phone restarts normally, there is no way to get into fastboot mode.
I already probe manually, with combination of buttons, and it does not work either, the model is the LX210HM
Click to expand...
Click to collapse
Have you tried installing the Aristo 2 firmware on your phone? In theory these phones have the same build and processors. Also in theory, but proven to work on some other cv1 devices (LG Phoenix 4), you should be able to flash Aristo 2 firmware and unlock your phone that way. I would also check your system.img to see if anything such as a security patch is in place to keep your phone from rebooting to the bootloader. You can backup the system.img manually and send me the img and I will look for anything that different from the Aristo 2 system.img.
Also by backing up the system.img and sending it to me, I can retrieve any "extra" carrier settings and add them to the cv1 img. I'm working on a full stock cv1 firmware img that will work on all the cv1 devices as a root strategy.
I have Lg K9 ( lmx210em ) and it's IMPOSSIBLE enter in fastboot mode, either with key combinations, either with adb command... The phone always boot in normalk mode !!!
Download mode and recowery mode work properly, but fastboot mode DID NOT !!!
urgent
i need the firmware the phoenix 4 please
NonStickAtom785 said:
Compatible Devices:
LG K8+
LG Aristo 2, 2+
LG K9
LG Phoenix 4
Thanks to @AustinGarrick1818 who discovered that this TWRP originally started and developed for the Aristo 2, by @messi2050 and @armandop_, then later updated to the latest version by @tecknight, was able to be flash on the Phoenix 4 leading to the idea that any cv1 device is cable of a ROOT method/TWRP Recovery.
..............
[/COLOR][/SIZE]
Click to expand...
Click to collapse
I'm assuming this will not work on the LG Aristo 2 Verizon PrePaid LM-X210VPP ? Or am i wrong? I have one here in inventory that just needs a new LCD and Digitizer ($20) and I was thinking about fixing it and modding it but worried about Verizon and the bootloader being locked. Have not found a lot of info on this device just yet so debating whether or not to keep / fix or get rid of it.
---------- Post added at 01:24 AM ---------- Previous post was at 01:22 AM ----------
AustinGarrick1818 said:
Just created a whole EDL firmware for the Aristo 2 aka Phoenix 4. PM me for the links if you'd like a copy. I also found our prog_emmc_firehose_8917_ddr.mbn to flash with (it works)
---------- Post added at 05:16 AM ---------- Previous post was at 05:13 AM ----------
I tested oreo and it works file
Click to expand...
Click to collapse
Did anyone get this guys debrick package? And does it have the xml's already created? Either way I would like a copy. If someone can pm me a link to a download or email me it that would be awesome.
i installed twrp and rooted the lmx210cm however now when i boot i shows a black bar at bottom of screen... top of image is cut off and touch screen is unresponsive.... works fine in twrp... what did i do wrong?
jdthomas4181 said:
i installed twrp and rooted the lmx210cm however now when i boot i shows a black bar at bottom of screen... top of image is cut off and touch screen is unresponsive.... works fine in twrp... what did i do wrong?
Click to expand...
Click to collapse
The issue you describe appears to be caused by kernel incompatibilities between certain partitions of the phone.
The fact that TWRP does not have the screen glitching issue implies that the kernel embedded in the TWRP image you flashed IS compatible, but perhaps the kernel within your boot image is NOT.
My first question would be:
You mention that you rooted your phone from fastboot.
Did you:
1. patch the stock boot image on your phone or
2. flash a pre-rooted boot image to your boot partition or
3. Flash a pre rooted ROM to your phone
If you answered #2 or #3, then my secondary question would be:
Specifically which boot image or ROM did you flash to your phone ?
---------- Post added at 08:35 PM ---------- Previous post was at 08:32 PM ----------
noidodroid said:
I'm assuming this will not work on the LG Aristo 2 Verizon PrePaid LM-X210VPP ? Or am i wrong? I have one here in inventory that just needs a new LCD and Digitizer ($20) and I was thinking about fixing it and modding it but worried about Verizon and the bootloader being locked. Have not found a lot of info on this device just yet so debating whether or not to keep / fix or get rid of it.
---------- Post added at 01:24 AM ---------- Previous post was at 01:22 AM ----------
Did anyone get this guys debrick package? And does it have the xml's already created? Either way I would like a copy. If someone can pm me a link to a download or email me it that would be awesome.
Click to expand...
Click to collapse
I did not get the edl package, but I really want it and of course his account is suspended.
Anybody have it ?
Also this method should be capable of working on your phone, as it is a cv1 device.
You may have to downgrade the firmware to Nougat before proceeding if the device is currently running Oreo.
If the device is currently running Oreo or later, you can downgrade the phone to Nougat using the LGUP utility
Related
I've followed instructions to unlock my bootloader which is done. I'm not sure if - "Device is unlocked. Status Code 3:" is correct or not, but that is what I see.
After unlocking I flashed TWRP 2.6.3.0-xt1032.img and it flashed correctly according to adb (attached). When I reboot the phone into bootloader and select recovery the screen just goes blank. I also tried "recovery-clockwork-touch-6.0.4.7-falcon.img", which seemed to flash OK in adb. The bootloader screen goes blank when I select recovery on the phone for CWM as well.
Both recovery flashes showed a similar result on the phone - this paste is for CWM
In Moto bootmode:
USB Connected
cmd: getvarartition-type:recovery
cmd: getvar:max-download-size
cmd: download:07b2000
cmd: flash:recovery
Mismatched partition zize (recovery)
The phone has stock Android 5.0.2 installed and still works, but I can't get any further than flashing the recovery image in adb. I did flash the logo.bin in adb and it seemed to flash correctly .
I'm running Windows 8.1, USB 3 ports.
Is there something I'm missing, or a different way to do the root? I'm stuck at this point, but luckily can run with the stock ROM for now.
I would appreciate any help I can get, Thanks
both recoveries you have used are seemingly outdated for lollipop bootloader. i would suggest you to try out the newly built TWRP (which is not yet publicly released) cant post URLs here yet but search for '[RECOVERY][falcon]TWRP 2.8.7.0 touch recovery [2015-06-24]' here in XDA
---------- Post added at 11:14 PM ---------- Previous post was at 11:03 PM ----------
here is the URL: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
koshikas said:
both recoveries you have used are seemingly outdated for lollipop bootloader. i would suggest you to try out the newly built TWRP (which is not yet publicly released) cant post URLs here yet but search for '[RECOVERY][falcon]TWRP 2.8.7.0 touch recovery [2015-06-24]' here in XDA
---------- Post added at 11:14 PM ---------- Previous post was at 11:03 PM ----------
here is the URL: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Click to expand...
Click to collapse
I tried and same result. After flashing with adb - disconnect USB , boot into bootloader, down to recovery, push power button and blank screen. Normal power up does the same thing as does factory. Ad I can confirm the version is 41.18.
Thanks
jjcdennis said:
I tried and same result. After flashing with adb - disconnect USB , boot into bootloader, down to recovery, push power button and blank screen. Normal power up does the same thing as does factory. Ad I can confirm the version is 41.18.
Thanks
Click to expand...
Click to collapse
these blank screens are quiet frustrating, can you get hold of the stock firmware for your model and flash back the stock recovery first and then try again with latest custom recoveries
koshikas said:
these blank screens are quiet frustrating, can you get hold of the stock firmware for your model and flash back the stock recovery first and then try again with latest custom recoveries
Click to expand...
Click to collapse
I had problems last weekend after trying to go to CM12.1 after rooting and ending up in a bootloader loop. I ended up using a KitKat stock rom and mfastboot2 and typed in all of the lines - it worked. The phone then updated to 5.0.2 via auto update.
I don't have that stock from the network update, but found this one - XT1034_Retail_Canada_502_Stock_Untouched which contains 3 files, Meta-inf, system and boot.img. I don't see a recovery in the folder. I'm not really sure what to look for and how to do this.
Thanks
jjcdennis said:
I had problems last weekend after trying to go to CM12.1 after rooting and ending up in a bootloader loop. I ended up using a KitKat stock rom and mfastboot2 and typed in all of the lines - it worked. The phone then updated to 5.0.2 via auto update.
I don't have that stock from the network update, but found this one - XT1034_Retail_Canada_502_Stock_Untouched which contains 3 files, Meta-inf, system and boot.img. I don't see a recovery in the folder. I'm not really sure what to look for and how to do this.
Thanks
Click to expand...
Click to collapse
make sure you get exactly a stock ROM that is made for your model. trying firmware made for other models is surefire way of bricking you phone. usually the stock firmware images ending with '*.xml.zip' do have a 'recovery.img' in them.
koshikas said:
make sure you get exactly a stock ROM that is made for your model. trying firmware made for other models is surefire way of bricking you phone. usually the stock firmware images ending with '*.xml.zip' do have a 'recovery.img' in them.
Click to expand...
Click to collapse
Thanks again.
If I find a correct ROM (I do have a KitKat 4.4.4 version), do I flash back with adb, or with mfastbootv2?
The ROM I showed was from here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
I have also found a firmware link on this thread "http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795" that looks to be in the correct format. There are thorough instructions on how to flash the firmware, but I am not sure if this will fix my issue or not.
Would appreciate any advice on how to proceed.
Thanks
I finally understood your comment "...can you get hold of the stock firmware for your model and flash back the stock recovery first and then try again with latest custom recoveries". I got a copy of the stock firmware, extracted the recovery from it and flashed it via adb to the phone - ok. I then tried to get into phone fastboot recovery, but was faced with the blank screen again. I flashed twrp 2.8.7.0 and the same thing in fastboot recovery - blank screen. I also tried cwm 6.0.5.1 and the same thing, blank screen.
ADB sees the device and accepts the commands, but the Motorola fastboot recovery doesn't open any of the recoveries. Nothing else in the bootloader seems to work ie: Factory - blank screen.
Every one of the recovery files other than the stock recovery shows a pink colored error "Mismatched partition size (recovery).
Anybody have any ideas as to what I can do to get a recovery to work?
Is there a different way to root this phone?
@jjcdennis i think you should post this to one of the active threads, since nobody with experience (this is well beyond mine) has dropped in yet. i would highly recommend; http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Moved to http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Easy Flash to Nougat Tutorial (Unlocked Retail Devices)
Prerequisites:
Download RSD lite XML to Batch Script from https://www.androidfilehost.com/?fid=24651430732235266
Download ROGERS_MPL24.246-45 from https://mega.nz/#!nssGEDiT!hhLkcTM106hmqbH_fiWfAytEV-fgdlYOhUwpcd_sGJY
Download Nougat firmware from https://mega.nz/#!608HGYqB!kKTc1196PhimDtVte6OdCWF6aXSWGSNLToEkvUePymE
Steps:
Unpack RSDLite XML to Batch Script to a folder on your computer
Unpack Rogers 24.246-45 firmware to the SAME folder
Run 2-rsd-flash-flashfile-windows.bat
Batch File #2 will convert the flashfile.xml file (included in Rogers zip) to a Batch file
Run flashfile.bat which will flash the Rogers firmware to your device (WILL WIPE EVERYTHING EXCEPT MICRO SD CARD)
Wait till its done!
Your device should now have Rogers 24.246-45 Firmware.
From the Bootloader, select Recovery Mode.
If you see No Command don't panic! That's normal. Press the power button for a couple seconds and press volume up or down (not sure if you need volume buttons but I always do anyway)
Once it displays on screen, Select ADB Sideload
From an adb capable command prompt, enter ADB Sideload <name and location of Nougat.zip> (minus the <> obviously)
This will take time. Leave it alone!
Once complete, simply reboot from recovery and let the device start like normal.
TROUBLESHOOTING:
If ADB Sideload gives you a Can't Read error, try these steps:
1. Download Large Address Awareness from here https://www.techpowerup.com/forums/threads/large-address-aware.112556/
2. Download ADB from here http://forum.xda-developers.com/showthread.php?t=2588979
3. Start Task Manager and kill adb.exe if its running
4. Load the adb.exe file from Large Address Awareness and check the flag button
5. Continue on with adb sideload
I've tested this process multiple times today and it should work well. Let me know if you have any trouble!
I want to mention I have had NO success backing up with TWRP and restoring after this. Something changed with Nougat and any modification to System causes a soft brick (it did for me anyway). Do not attempt to flash system mode TWRP or flash the TurboZ kernel. They don't work and they will cause a boot loop.
UPDATE:
This method might not be for everyone, and if you're not interested in sticking with stock 7.0 and potentially want to roll around to other ROMs you should follow this guide instead; http://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
Great thank you! Question:
Will all the radio bands (T-MOBILE) still work as normal?
Have you try this out with Google Day Dream VR yet?
I had the note 7 and the Galaxy VR., Kinda of miss that.
dallas90733 said:
Great thank you! Question:
Will all the radio bands (T-MOBILE) still work as normal?
Have you try this out with Google Day Dream VR yet?
I had the note 7 and the Galaxy VR., Kinda of miss that.
Click to expand...
Click to collapse
Daydream works from what I can tell. Also I'm on att so I haven't checked T-Mobile bands but im assuming they work fine. I know there's an app to check which bands your device supports. I'll try downloading it and let you know
So I get to the point to sideload the nougat update and it always says "can't read..." I've done factory resets and everything else I could think of, still no go for me.
Prfndhatrdofman said:
...
I want to mention I have had NO success backing up with TWRP and restoring after this. Something changed with Nougat and any modification to System causes a soft brick (it did for me anyway). Do not attempt to flash system mode TWRP or flash the TurboZ kernel. They don't work and they will cause a boot loop.
Click to expand...
Click to collapse
So... are you of the opinion that recovering a Nougat boot+system TWRP backup on a MM phone would cause a soft brick too?
What type of soft brick do you faced exactly?
Prfndhatrdofman said:
Easy Flash to Nougat Tutorial (Unlocked Retail Devices)
Prerequisites:
Download RSD lite XML to Batch Script from https://www.androidfilehost.com/?fid=24651430732235266
Download ROGERS_MPL24.246-45 from https://mega.nz/#!nssGEDiT!hhLkcTM106hmqbH_fiWfAytEV-fgdlYOhUwpcd_sGJY
Download Nougat firmware from https://mega.nz/#!608HGYqB!kKTc1196PhimDtVte6OdCWF6aXSWGSNLToEkvUePymE
Steps:
Unpack RSDLite XML to Batch Script to a folder on your computer
Unpack Rogers 24.246-45 firmware to the SAME folder
Run 2-rsd-flash-flashfile-windows.bat
Batch File #2 will convert the flashfile.xml file (included in Rogers zip) to a Batch file
Run flashfile.bat which will flash the Rogers firmware to your device (WILL WIPE EVERYTHING EXCEPT MICRO SD CARD)
Wait till its done!
Your device should now have Rogers 24.246-45 Firmware.
From the Bootloader, select Recovery Mode.
If you see No Command don't panic! That's normal. Press the power button for a couple seconds and press volume up or down (not sure if you need volume buttons but I always do anyway)
Once it displays on screen, Select ADB Sideload
From an adb capable command prompt, enter ADB Sideload <name and location of Nougat.zip> (minus the <> obviously)
This will take time. Leave it alone!
Once complete, simply reboot from recovery and let the device start like normal.
I've tested this process multiple times today and it should work well. Let me know if you have any trouble!
I want to mention I have had NO success backing up with TWRP and restoring after this. Something changed with Nougat and any modification to System causes a soft brick (it did for me anyway). Do not attempt to flash system mode TWRP or flash the TurboZ kernel. They don't work and they will cause a boot loop.
Click to expand...
Click to collapse
I did up until this
From the Bootloader, select Recovery Mode.
If you see No Command don't panic! That's normal. Press the power button for a couple seconds and press volume up or down (not sure if you need volume buttons but I always do anyway)
Once it displays on screen, Select ADB Sideload
From an adb capable command prompt, enter ADB Sideload <name and location of Nougat.zip> (minus the <> obviously)
But when I boot up i have no wifi and I am unable to get the no command to go away to select sideload any ideas?
pieman13 said:
So I get to the point to sideload the nougat update and it always says "can't read..." I've done factory resets and everything else I could think of, still no go for me.
Click to expand...
Click to collapse
Same here, did you find a fix? Tried re-downloading Blur_Version.24.21.46.griffin.retail.en.US.zip and got the same error...
pixelens said:
Same here, did you find a fix? Tried re-downloading Blur_Version.24.21.46.griffin.retail.en.US.zip and got the same error...
Click to expand...
Click to collapse
This happened to me as well. I think it came down to being an ADB Driver issue for me. I reinstalled a different set of ADB drivers and it had no issue after that.
enetec said:
So... are you of the opinion that recovering a Nougat boot+system TWRP backup on a MM phone would cause a soft brick too?
What type of soft brick do you faced exactly?
Click to expand...
Click to collapse
Didn't work for me. As soon as the system partition was mounted R/W My device would boot loop. Could be a symptom of something else but im not sure.
Prfndhatrdofman said:
This happened to me as well. I think it came down to being an ADB Driver issue for me. I reinstalled a different set of ADB drivers and it had no issue after that.
Click to expand...
Click to collapse
Interesting... I'm using the adb drivers from Android Studio.
---------- Post added at 02:27 PM ---------- Previous post was at 02:16 PM ----------
Tried using the ADB drivers from Minimal ADB and Fastboot, same result. Oh well.
pixelens said:
Interesting... I'm using the adb drivers from Android Studio.
---------- Post added at 02:27 PM ---------- Previous post was at 02:16 PM ----------
Tried using the ADB drivers from Minimal ADB and Fastboot, same result. Oh well.
Click to expand...
Click to collapse
Yeah i struggled for about 3 hours trying to get sideload to work. I dunno why but after i completely deleted the driver, rebooted, reinstalled from ADB it finally worked. Its definitely not your device or the image its just ADB being a pain in the ass. I even tried multiple versions of ADB. One guy just tried on a different computer and it worked. I dunno why
Prfndhatrdofman said:
Yeah i struggled for about 3 hours trying to get sideload to work. I dunno why but after i completely deleted the driver, rebooted, reinstalled from ADB it finally worked. Its definitely not your device or the image its just ADB being a pain in the ass. I even tried multiple versions of ADB. One guy just tried on a different computer and it worked. I dunno why
Click to expand...
Click to collapse
Yah, I've had similar experiences in the past - been ages since I've done this though (Samsung Galaxy SII Skyrocket days) so just wanted to make sure I wasn't missing something.
Quick question though, title says "unlocked retail devices" - does that mean the bootloader has to be unlocked? Or will this work with a locked bootloader? Cheers.
pixelens said:
Yah, I've had similar experiences in the past - been ages since I've done this though (Samsung Galaxy SII Skyrocket days) so just wanted to make sure I wasn't missing something.
Quick question though, title says "unlocked retail devices" - does that mean the bootloader has to be unlocked? Or will this work with a locked bootloader? Cheers.
Click to expand...
Click to collapse
I specifically meant network unlocked. Really just any device purchased directly from Motorola.
But yeah i think you might need to have an unlocked bootloader as well.
pixelens said:
Same here, did you find a fix? Tried re-downloading Blur_Version.24.21.46.griffin.retail.en.US.zip and got the same error...
Click to expand...
Click to collapse
Fix was I went back to my pixel and sold the Z.
Mine has unlocked bootloader. Unlocked thru Motorola's website since the first hour I got it
Got the Nougat update to sideload (yay!) - tried a different computer that had no adb drivers installed, used the ones from Minimal ADB and Fastboot and they worked no problem.
Is it possible to lock the bootloader after the Nougat update? I tried and received "(bootloader) still require signed boot.img" message.
pixelens said:
Got the Nougat update to sideload (yay!) - tried a different computer that had no adb drivers installed, used the ones from Minimal ADB and Fastboot and they worked no problem.
Is it possible to lock the bootloader after the Nougat update? I tried and received "(bootloader) still require signed boot.img" message.
Click to expand...
Click to collapse
Dunno. I get the same error.
Thank you for this guide!
Prfndhatrdofman said:
Easy Flash to Nougat Tutorial (Unlocked Retail Devices)
Prerequisites:
Download RSD lite XML to Batch Script from https://www.androidfilehost.com/?fid=24651430732235266
Download ROGERS_MPL24.246-45 from https://mega.nz/#!nssGEDiT!hhLkcTM106hmqbH_fiWfAytEV-fgdlYOhUwpcd_sGJY
Download Nougat firmware from https://mega.nz/#!608HGYqB!kKTc1196PhimDtVte6OdCWF6aXSWGSNLToEkvUePymE
Steps:
Unpack RSDLite XML to Batch Script to a folder on your computer
Unpack Rogers 24.246-45 firmware to the SAME folder
Run 2-rsd-flash-flashfile-windows.bat
Batch File #2 will convert the flashfile.xml file (included in Rogers zip) to a Batch file
Run flashfile.bat which will flash the Rogers firmware to your device (WILL WIPE EVERYTHING EXCEPT MICRO SD CARD)
Wait till its done!
Your device should now have Rogers 24.246-45 Firmware.
From the Bootloader, select Recovery Mode.
If you see No Command don't panic! That's normal. Press the power button for a couple seconds and press volume up or down (not sure if you need volume buttons but I always do anyway)
Once it displays on screen, Select ADB Sideload
From an adb capable command prompt, enter ADB Sideload <name and location of Nougat.zip> (minus the <> obviously)
This will take time. Leave it alone!
Once complete, simply reboot from recovery and let the device start like normal.
I've tested this process multiple times today and it should work well. Let me know if you have any trouble!
I want to mention I have had NO success backing up with TWRP and restoring after this. Something changed with Nougat and any modification to System causes a soft brick (it did for me anyway). Do not attempt to flash system mode TWRP or flash the TurboZ kernel. They don't work and they will cause a boot loop.
Click to expand...
Click to collapse
Hello
I flashed the rogers 45 firmware, but when I go to recovery mode I can't get the ADB menu to appear. I've held power and down, power and up, nothing, etc. Am I missing something? I did the rogers install, then went to homescreen, then powered off.
EDIT
after restarting my phone like 10 times in 5 minutes (rest in peace...) I finally figured it out. Now my issue is that I can't seem to get the sideload to work. I am going to try uninstalling android studio and start again. Did you guys figure out why it says * cannot read ' blur.....' * ?
I found how to fix the adb problem about being unable to read from another thread on XDA
1. Download Large Address Awareness from here https://www.techpowerup.com/forums/threads/large-address-aware.112556/
2. Download ADB from here http://forum.xda-developers.com/showthread.php?t=2588979
3. Start Task Manager and kill adb.exe if its running
4. Load the adb.exe file from Large Address Awareess and check the flag button
5. Continue on with adb sideload
---------- Post added at 09:42 AM ---------- Previous post was at 09:40 AM ----------
Porcelainfog said:
Hello
I flashed the rogers 45 firmware, but when I go to recovery mode I can't get the ADB menu to appear. I've held power and down, power and up, nothing, etc. Am I missing something? I did the rogers install, then went to homescreen, then powered off.
Click to expand...
Click to collapse
Do you see the "No command" picture after choosing Recover Mode? Once you get to that, I hold down power and tap volume up and down again and again
Hi. After using this method to fix dozens of G4's and 5X's, I bumped on one bootlooping V10. As there's no modified kernels that would boot V10 on only 4 cores, I present to you:
V10 kernel that will resurrect your bootlooping beauty!
Requirements and Guide:
1: Working ADB and Fastboot
2A: If you already checked OEM unlock in developer options, try booting to fastboot using this method:
Remove battery from phone
Insert USB cable from PC to phone (with battery removed)
On your phone screen there should now be battery icon with question mark inside
Hold volume down, and while holding, insert the battery in the phone, you should be inside fastboot
From there, unlock bootloader, if you haven't already, and flash 4cores kernel for your version of phone and software
- or -
2B: If you previously didn't enable OEM unlocking, AND/OR you can't boot directly to fastboot:
You must be able to boot the phone at least for 30 seconds to do this
Go to developer options and check OEM Unlocking and USB Debugging
Go to LG site and follow instructions on how to unlock bootloader
After unlocking bootloader, while still on fastboot screen, flash my custom 4cores kernel
Code:
fastboot flash boot boot.img
NOTE: As of now, I only modified 30b and 20e versions for H960a variant, and 20e for H901... It might work on others versions, but I'm not sure. I tested 30B and 20e for H960, H901 is untested at the moment. If you have other software, feel free to contact me and I will make the kernel for specified software version, or use LGUP to flash software version that has 4cores kernel...
Now you have a kernel with max 4 CPUs and the faulty CPUs disabled. Enjoy your resurrected phone.
NOTE: For anyone that didn't have OEM unlock checked at the time of bootloop, I guess you have trouble booting your phone to tick that option. You have few options, and here are only few of them... You can try refrigerator or freezer for 30 minutes to 1 hour, and try to boot your phone. In most cases it will boot long enough to go to developer options and tick the boxes, and then boot to Fastboot. Also, you can try hairdryer for around 10 minutes, it is also confirmed that this method has worked for some people...
If this method helps fixing your phone, feel free to hit thanks button
Donations are not expected or required, but are welcome:
Donate Me!
EDIT:
Added TWRP booting on 4 cores!
Credits:
Big thanks to following people for making this method possible:
@XCnathan32
@steadfasterX
@XeniX_Force
@rudi666
stojshic said:
Hi. After using this fix for few G4's and 5X's, I bumped on V10 with the same problem, but as I found out, no one still made modified kernel that would boot on 4 cores only, so, here it is:
Requirements and Guide:
Working ADB and Fastboot
Unlocked device with access to fastboot (if that's possible on V10?)
- or -
You must be able to boot the phone at least for 30 seconds to do this
Go to developer options and check OEM Unlocking and USB Debugging
Go to LG site and follow instructions on how to unlock bootloader
After unlocking bootloader, while still on fastboot screen, flash my custom 4cores kernel
Code:
fastboot flash boot boot_30b.img
NOTE: As of now, I only modified 30b kernel for h960a variant... It might work on others versions, but I'm not sure. I tested it on my V10 with 30B software installed. If you have other software, feel free to contact me and I will make the kernel for specified software version, or use LGUP to flash 30B, and after that flash this kernel.
Now you have a kernel with max 4 CPUs and the faulty CPUs disabled. Enjoy your resurrected phone.
NOTE: Considering you have bootlooping phone, I guess it's the question how to enter fastboot, as to my knowledge LG disabled booting directly to fastboot. If you know the way to boot directly to fastboot, than you are fine (and please share how), and for everyone else, you must manage to boot the phone somehow. You can try refrigerator or freezer for 30 minutes to 1 hour, and try to boot your phone. In most cases it will boot long enough to go to developer options and tick the boxes, and then boot to Fastboot. Also, you can try hairdryer for around 10 minutes, it is also confirmed that this method has worked for some people...
If this method helps fixing your phone, feel free to hit thanks button
Donations are not expected or required, but are welcome: Donate Me!
Credits:
Big thanks to following people for making this method possible:
@XCnathan32
@steadfasterX
@XeniX_Force
Click to expand...
Click to collapse
this kernel is from V10 or from G4? i mean my V10 is work perfect with Nougat but i want to do as much as i can to keeping it so, can i flash this on H960A International Model? i have unlocked bootloader and i can boot into fastboot...
sun_is_shinning said:
this kernel is from V10 or from G4? i mean my V10 is work perfect with Nougat but i want to do as much as i can to keeping it so, can i flash this on H960A International Model? i have unlocked bootloader and i can boot into fastboot...
Click to expand...
Click to collapse
It's modified V10 kernel that utilizes only 4 cores. You can't use G4 kernel on V10. If you have 30b software on your H960A, you should be safe to boot in fastboot and flash this kernel. After that, you can install cpu-z and verify that only 4 cores are online
Sent from my ZTE Axon 7 using Tapatalk
stojshic said:
It's modified V10 kernel that utilizes only 4 cores. You can't use G4 kernel on V10. If you have 30b software on your H960A, you should be safe to boot in fastboot and flash this kernel. After that, you can install cpu-z and verify that only 4 cores are online
Sent from my ZTE Axon 7 using Tapatalk
Click to expand...
Click to collapse
very very thanks...its working!!! NOW I ONLY HAVE 4 CORES active and the crappy ones is gone!
EDIT: i lose root when flash this, and need to flash TWRP again and supersu again, but root is not working now...i try it twice but nothing, it keep giving error!
can you help?
DISCLAIMER TO THIS THREAD: If you flash this Kernel you will lose the hability to flash SuperSU, and so you wont be able to have root on your device.
P.S.: Dev should put a SELinux Permissive right in Kernel and some add ons like KCAL display calibration and core control. This only disable the little cores and the battery will be more hungry now...
i know this only are made to rescue your V10 from bootloop but i think it deserve some devlopment because this can be a great Kernel.
Thanks for suggestion. For now, this is, like it is stated, pure stock kernel with disabled cores, for those in bootloop. I will think about modified versions in the future, but until further testing, it's going to stay stock...
Sent from my ZTE Axon 7 using Tapatalk
stojshic said:
NOTE: As of now, I only modified 30b kernel for h960a variant... It might work on others versions, but I'm not sure. I tested it on my V10 with 30B software installed. If you have other software, feel free to contact me and I will make the kernel for specified software version, or use LGUP to flash 30B, and after that flash this kernel.
Click to expand...
Click to collapse
Great work. 30b KDZ is easily available here. I think one should flash it and use this boot image instead of asking for developing a boot image for their specific firmwares.
However, I would suggest to kindly release a custom boot image for H901 20e. Because H901 (Tmobile) is also bootloader unlockable and its 20e KDZ is also easily available here. This way both unlockable variants of V10 i.e. H960A and H901 will be covered. :angel:
NOTE: Considering you have bootlooping phone, I guess it's the question how to enter fastboot, as to my knowledge LG disabled booting directly to fastboot. If you know the way to boot directly to fastboot, than you are fine (and please share how).
Click to expand...
Click to collapse
I myself booted to fastboot easily on a bootlooped LG V10 H961N (HongKong) by:
1. Turning the phone off.
2. Pressing Vol down.
3. Connecting the phone with computer with data cable.
4. Releasing the Vol down upon seeing the phone booted into fastboot.
Dont know if the same would work on other variants or not.
rizkhan999 said:
Great work. 30b KDZ is easily available here. I think one should flash it and use this boot image instead of asking for developing a boot image for their specific firmwares.
However, I would suggest to kindly release a custom boot image for H901 20e. Because H901 (Tmobile) is also bootloader unlockable and its 20e KDZ is also easily available here. This way both unlockable variants of V10 i.e. H960A and H901 will be covered. :angel:
I myself booted to fastboot easily on a bootlooped LG V10 H961N (HongKong) by:
1. Turning the phone off.
2. Pressing Vol down.
3. Connecting the phone with computer with data cable.
4. Releasing the Vol down upon seeing the phone booted into fastboot.
Dont know if the same would work on other variants or not.
Click to expand...
Click to collapse
Yeah, I heard about that way of booting, but never managed to boot to fastboot using that method. I will edit my post to include it... Also, thanks for the link for the software, will edit that kernel soon, and post 4cores version of it here...
Sent from my ZTE A2017U using Tapatalk
I never had bootloop on my h960a. how is that possible?
stojshic said:
Yeah, I heard about that way of booting, but never managed to boot to fastboot using that method. I will edit my post to include it... Also, thanks for the link for the software, will edit that kernel soon, and post 4cores version of it here...
Click to expand...
Click to collapse
Someone whom I know has h901 software on his vs990. I asked him to follow this procedure. And he also successfully booted into fastboot mode and shared this image with me which I have uploaded here. Means its working on other models too.
rizkhan999 said:
Someone whom I know has h901 software on his vs990. I asked him to follow this procedure. And he also successfully booted into fastboot mode and shared this image with me which I have uploaded here. Means its working on other models too.
Click to expand...
Click to collapse
Thanks for info! I Added it to first post...
Also, I just uploaded two new versions of kernel:
h901 version 20e
h960a version 20e
stojshic said:
Thanks for info! I Added it to first post...
Also, I just uploaded two new versions of kernel:
h901 version 20e
h960a version 20e
Click to expand...
Click to collapse
Awesome work.:good::victory:
stojshic said:
Thanks for info! I Added it to first post...
Also, I just uploaded two new versions of kernel:
h901 version 20e
h960a version 20e
Click to expand...
Click to collapse
Can we also get the TWRP recoveries with big cores disabled?
For H901 it is available here and here. And for H960A it is available here.
I would really be grateful.
rizkhan999 said:
Can we also get the TWRP recoveries with big cores disabled?
For H901 it is available here and here. And for H960A it is available here.
I would really be grateful.
Click to expand...
Click to collapse
I'll try to make them one of these days. I'm really busy ATM, but will try to find some time to modify the images
Sent from my ZTE A2017U using Tapatalk
I can get into fastboot, but any fastboot commands like
Code:
fastboot flash boot boot.img
or
Code:
fastboot boot recovery twrp.img
or
Code:
fastboot boot twrp.img
fail with unknown command error. My bootloader is unlocked so it can't be that. Any ideas on how to flash this with that it mind?
galaxymover said:
I can get into fastboot, but any fastboot commands like
Code:
fastboot flash boot boot.img
or
Code:
fastboot boot recovery twrp.img
or
Code:
fastboot boot twrp.img
fail with unknown command error. My bootloader is unlocked so it can't be that. Any ideas on how to flash this with that it mind?
Click to expand...
Click to collapse
with the phone off, volume up key pressed connect the phone into pc and keep pressed the volume up key, then go to "minimal adb and fastboot" - its a cmd dedicated to use for this - and there do the follow command:
adb devices
(you should see yours saying conected, then do the follow)
adb reboot fastboot
(and now you are in fastboot, if you want to boot in bootloader do the command bellow)
adb reboot bootloader
- and thats it. if you are trying to flash TWRP you need to download the img of TWRP in some thread in V10 section and put it on the root of the fastboot tool you are using and to install it when in fastboot do the follow command:
fastboot flash recovery (name-of-twrp-file).img
and you done.
sun_is_shinning said:
with the phone off, volume up key pressed connect the phone into pc and keep pressed the volume up key, then go to "minimal adb and fastboot" - its a cmd dedicated to use for this - and there do the follow command:
adb devices
(you should see yours saying conected, then do the follow)
adb reboot fastboot
(and now you are in fastboot, if you want to boot in bootloader do the command bellow)
adb reboot bootloader
- and thats it. if you are trying to flash TWRP you need to download the img of TWRP in some thread in V10 section and put it on the root of the fastboot tool you are using and to install it when in fastboot do the follow command:
fastboot flash recovery (name-of-twrp-file).img
and you done.
Click to expand...
Click to collapse
I tried doing those commands and got the same error that I mentioned in my previous post.
galaxymover said:
I tried doing those commands and got the same error that I mentioned in my previous post.
Click to expand...
Click to collapse
Do you see the device when execute "fastboot devices" command? Also try it on linux after installing "adb" or "android-tools". Because it may be drivers issue on windows. If nothing works, flash a different KDZ. May be this firmware has some limitations in its fastboot.
EDIT: Also check if you have unlocked the bootloader or not. These commands will work if it is unlocked. Although commands should still be recognized but still, just a check.
---------- Post added at 11:05 AM ---------- Previous post was at 10:45 AM ----------
stojshic said:
I'll try to make them one of these days. I'm really busy ATM, but will try to find some time to modify the images
Click to expand...
Click to collapse
Thanks. I have TWRP with big cores disabled in my G4 H815. But when I boot into TWRP and execute cat /sys/devices/system/cpu/cpuX/online from its terminal, I see that only the online file of cpu0 core has the value of 1, while the online files of all the rest cpu cores has 0 value. So if TWRP works on only 1 core by default (just like Download Mode), we may not have to make a TWRP with big cores disabled! But the question is that does TWRP really work on only 1 core by default, as also seem to be the case with that TWRP on my phone?
I would also request you to kindly make a custom boot image with big cores disabled for H901 with 30b firmware from its KDZ. I have attached its boot.img herewith, after extracting it with this tool, so that you may not have to download the whole 30b KDZ for that.
I am sorry to bother you so much but the reason why I am requesting for a 30b custom boot image in presence of 20e for the same model (H901) is that 20e is on ARBv1 while 30b is on ARBv2, and I cannot flash 20e over 30b using LGUP.
hi all, so with htis methode even with the h961n we can getout from the bootloop?, does the undercloked way helps? thanks a lot!!
rizkhan999 said:
Do you see the device when execute "fastboot devices" command? Also try it on linux after installing "adb" or "android-tools". Because it may be drivers issue on windows. If nothing works, flash a different KDZ. May be this firmware has some limitations in its fastboot.
EDIT: Also check if you have unlocked the bootloader or not. These commands will work if it is unlocked. Although commands should still be recognized but still, just a check.
Click to expand...
Click to collapse
While I can see the device in
Code:
fastboot devices
, I cannot see it in LGUP/LG Bridge/LG PC Suite. I will fire up a Linux VM and see if that helps. Also, I have definitely unlocked the bootloader.
No single blackview s8 unique rom
MTom said:
No single blackview s8 unique rom
Click to expand...
Click to collapse
Nope.
Im trying to root this device but no success. Did you manage to root it?
mellowbug said:
Nope.
Im trying to root this device but no success. Did you manage to root it?
Click to expand...
Click to collapse
I have not tried
maybe it works
https://www.getdroidtips.com/twrp-recovery-on-blackview-s8-root/
this is my primary phone, I can't experiment.
MTom said:
I have not tried
maybe it works
https://www.getdroidtips.com/twrp-recovery-on-blackview-s8-root/
this is my primary phone, I can't experiment.
Click to expand...
Click to collapse
That tutorial is fake. As far as i know this device has no working fastboot/bootloader mode. With the device connected : adb reboot bootloader / fastboot the device just restarts and charging.
And reboot bootloader from within the recovery it just turns off.
So basically every tut. that even mentions fastboot (regarding the blackview s8) is fake.. click bait, copy paste lies.
It has verified boot (avb 1.0 according to magisk) and dm-verity. So i cant even flash the patched boot.img.
Im stuck. Any thoughts?
Btw. Did you came across or do you know a way to get the device into bootloader / fastboot mode?
mellowbug said:
That tutorial is fake. As far as i know this device has no working fastboot/bootloader mode. With the device connected : adb reboot bootloader / fastboot the device just restarts and charging.
And reboot bootloader from within the recovery it just turns off.
So basically every tut. that even mentions fastboot (regarding the blackview s8) is fake.. click bait, copy paste lies.
It has verified boot (avb 1.0 according to magisk) and dm-verity. So i cant even flash the patched boot.img.
Im stuck. Any thoughts?
Btw. Did you came across or do you know a way to get the device into bootloader / fastboot mode?
Click to expand...
Click to collapse
Unfortunately I can not help. sorry
no one can know root access
MTom said:
I have not tried
maybe it works
https://www.getdroidtips.com/twrp-recovery-on-blackview-s8-root/
this is my primary phone, I can't experiment.
Click to expand...
Click to collapse
Those trick doesn't work, most post the probably automated copy paste bs just for the click bait topic. It causing my phone to stuck at boot following that tutorial. I'll ended reflash my phone. mine not s8 but a9 pro.
All i wanted i to root my phone so i can use firewall app, but i think blackview is a minority in the market so no one bother to make custom rom for it.
MTom said:
No single blackview s8 unique rom
Click to expand...
Click to collapse
Hey, i own Blackview A60 Pro and the answer is quietly no, Blackview does not make the device trees public for their devices.
Sure a developer could make these but their devices are not popular enough.
On my A60 Pro I run AOSP GSI (Generic System Images) tremble from phhusson with magisk root.
There are also unofficial LinageOS GSI Images available maybe you could try these.
---------- Post added at 08:46 PM ---------- Previous post was at 08:38 PM ----------
mellowbug said:
That tutorial is fake. As far as i know this device has no working fastboot/bootloader mode. With the device connected : adb reboot bootloader / fastboot the device just restarts and charging.
And reboot bootloader from within the recovery it just turns off.
So basically every tut. that even mentions fastboot (regarding the blackview s8) is fake.. click bait, copy paste lies.
It has verified boot (avb 1.0 according to magisk) and dm-verity. So i cant even flash the patched boot.img.
Im stuck. Any thoughts?
Btw. Did you came across or do you know a way to get the device into bootloader / fastboot mode?
Click to expand...
Click to collapse
Have you tried to disconnect the cable after you hit the command "adb reboot bootloader"?
You can easily disable verified boot with "fastboot --disable-verification flash vbmeta vbmeta.img" when you can acces fastboot....
str8unknown said:
Hey, i own Blackview A60 Pro and the answer is quietly no, Blackview does not make the device trees public for their devices.
Sure a developer could make these but their devices are not popular enough.
On my A60 Pro I run AOSP GSI (Generic System Images) tremble from phhusson with magisk root.
There are also unofficial LinageOS GSI Images available maybe you could try these.
---------- Post added at 08:46 PM ---------- Previous post was at 08:38 PM ----------
Have you tried to disconnect the cable after you hit the command "adb reboot bootloader"?
You can easily disable verified boot with "fastboot --disable-verification flash vbmeta vbmeta.img" when you can acces fastboot....
Click to expand...
Click to collapse
Hi, I have a Blackview A80 Pro, and I unlocked the bootlader but I can't install TWRP, can you help me?
I've tried to restore to Stock using a few of the different ROM's from the Android File Host site, but I'm constantly stuck in a revolving Fastboot mode.
The Sprint bootloader unlock here worked fine:
https://forum.xda-developers.com/on...otloader-unlock-sprint-oneplus-7-pro-t4042145
At one point I had the TWRP zip installed and working fine, so I'm not sure why I can't reboot to recovery anymore. It always boots to fastboot.
I've also tried ADB commands to run from a different slot (A/B/Other). Both slots produce this error when trying to flash the twrp.img to either slot:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Any ideas are appreciated. I thought all the Stock ROMs provided work for all variants. My phone connects successfully with TOOL_ALL_IN_ONE, and flashing a Stock image seems successful, but the phone reverts back to Fastboot loop.
Edit: I tried the Guac for All unbrick tool and method specified here:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
I made sure to install the L2 drivers certificate and use the original cable that came with my phone in a USB 2.0 port. However, on the last MSM Tool's Status of Communication called Param Preload, I get an error that says Device does not match image. I'm guessing the Guac for All tool has a unified ROM, but it doesn't seem to work for my SM1925 (Sprint). I'll keep trying other methods and updating.
aktiv8d said:
I've tried to restore to Stock using a few of the different ROM's from the Android File Host site, but I'm constantly stuck in a revolving Fastboot mode.
The Sprint bootloader unlock here worked fine:
https://forum.xda-developers.com/on...otloader-unlock-sprint-oneplus-7-pro-t4042145
At one point I had the TWRP zip installed and working fine, so I'm not sure why I can't reboot to recovery anymore. It always boots to fastboot.
I've also tried ADB commands to run from a different slot (A/B/Other). Both slots produce this error when trying to flash the twrp.img to either slot:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Any ideas are appreciated. I thought all the Stock ROMs provided work for all variants. My phone connects successfully with TOOL_ALL_IN_ONE, and flashing a Stock image seems successful, but the phone reverts back to Fastboot loop.
Edit: I tried the Guac for All unbrick tool and method specified here:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
I made sure to install the L2 drivers certificate and use the original cable that came with my phone in a USB 2.0 port. However, on the last MSM Tool's Status of Communication called Param Preload, I get an error that says Device does not match image. I'm guessing the Guac for All tool has a unified ROM, but it doesn't seem to work for my SM1925 (Sprint). I'll keep trying other methods and updating.
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=4349826312261604268
Flash this, install the 9.5.17 ota and try to re-unlock
Whoareyou said:
https://androidfilehost.com/?fid=4349826312261604268
Flash this, install the 9.5.17 ota and try to re-unlock
Click to expand...
Click to collapse
Thank you so much for your help. I followed your instructions exactly.
After the MSM Tool's flash with the image provided, it no longer fastboot cycled and booted normally to 9.5.12. It paused on the 5G logo for a couple mins and then loaded into the phone setup screen. I think updated to 9.15.17 ota as instructed. Everything is now working properly.
Can I ask where you found this version of the MSM tool's stock image that works for the GM1925? I searched and searched, but couldn't find anything. Even searching for that zip's filename returned 0 results for me. I saved that file, but if new compatible stock ROM's are released, I'd like to be able to find them, too.
aktiv8d said:
Thank you so much for your help. I followed your instructions exactly.
After the MSM Tool's flash with the image provided, it no longer fastboot cycled and booted normally to 9.5.12. It paused on the 5G logo for a couple mins and then loaded into the phone setup screen. I think updated to 9.15.17 ota as instructed. Everything is now working properly.
Can I ask where you found this version of the MSM tool's stock image that works for the GM1925? I searched and searched, but couldn't find anything. Even searching for that zip's filename returned 0 results for me. I saved that file, but if new compatible stock ROM's are released, I'd like to be able to find them, too.
Click to expand...
Click to collapse
They're only sent out by OnePlus when someone needs to restore their phone due to malfunction, not released on any regular basis, but this one has been around for a while.
Hi, I am in the exact same position as you were. I downloaded the .rar file provided, but how do I flash it?
Thanks!
---------- Post added at 03:51 AM ---------- Previous post was at 03:37 AM ----------
mimat1 said:
Hi, I am in the exact same position as you were. I downloaded the .rar file provided, but how do I flash it?
Thanks!
Click to expand...
Click to collapse
UPDATE: I flashed it by starting the MSMDownloader while in EDL mode. Much thanks for this method and fix. My phone thanks you for revival!
Narwhal73 said:
Ok so for future people who run into the same problem and are clueless like me! The RAR file contains the system image and an MSM Tool. Unrar it, open the tool, put your phone in EDL mode, make sure the tool recognizes the device, then click "start".
Cheers!
Click to expand...
Click to collapse
Alright, sorry for hijacking this thread... It seems like after flashing this image, the phone has been SIM locked to Sprint?! I purchased this phone unlocked, and it was working with Public Mobile prior to trying to unlock the bootloader. @Whoareyou any advice?
---------- Post added at 07:36 PM ---------- Previous post was at 07:22 PM ----------
Narwhal73 said:
Alright, sorry for hijacking this thread... It seems like after flashing this image, the phone has been SIM locked to Sprint?! I purchased this phone unlocked, and it was working with Public Mobile prior to trying to unlock the bootloader. @Whoareyou any advice?
Click to expand...
Click to collapse
Ok, I was really spooked by the Android 9 ROM saying my device was SIM locked when I bought it unlocked.
On point with answering my own questions: applying the OTA update now shows that my phone is unlocked (as it should be!) under Settings > System updates > UICC unlock.
My phone always reboots to fastboot. I've opened MSM tool and my phone doesn't appear there. It does appear using fastboot devices command on CMD though. How can I flash this? Restart recovery or restart bootloader does nothing, always back to fastboot.