I have F320K on Lollipop 5.0.1
Software Version F320k30D
Every time i am flashing this Cloudy 3.3 i am getting a black screen. Here is what i am doing:
1. Root With KingRoot.
2.Recovery with Autorec from Here
3. After Going to Recovery Flashing the Latest TWRP 3.0.2-1
4. Reboot to Latest TWRP 3.0.2-1
5. Flashing KK Bootloader Via Bootloader Changer From Here. I am choosing the BLChanger-F320x-nevax-2.3.2-signed.zip
6. While Flashing the KK Bootloader with Bootloader Changer im getting a massage that : "This package is for device f320k, galbi.... This device is f320" Does that mean im flashing the wrong Bootloader? Also i have selected update recovery field to update TWRP to 2.8.7.1, but nothing happens.
7. Then i am wiping: System, Data, Dalvik, Cache
8. I am installing the ROM.
9. Upon restart im getting a quick LG Logo followed by a black screen.
Am i missing something here? Please help.
Check this thread :http://forum.xda-developers.com/lg-g2/help/installing-cloudyg2-3-3-f320-t3197531
Related
Hello Folks!!!
I was on a Rooted Stock 5.0.2 CM12 ROM with TWRP recovery, when I got the notification for an OTA update (YNG1TAS1K0). I found out that we had to flash stock recovery to install the update, so I did that, but the OTA update wouldn't install and kept throwing error saying something like "unable to update /sideload/". After multiple attempts, I finally flashed the whole ROM (cm-12.0-YNG1TAS1K0-tomato-signed.zip) via the stock recovery, and now I am on the latest stock build (YNG1TAS1K0). Unfortunately, I am stuck on the stock recovery now. Whenever I try to flash the TWRP recovery (TWRP 2.8.6.0 for Lollipop), it goes into bootloop. I have temporarily flashed stock recovery again to make my phone usable again, but I would really like to flash TWRP again and root it. Any advice/suggestions will be appreciated. Thanks. :highfive:
acemccloud1 said:
Hello Folks!!!
I was on a Rooted Stock 5.0.2 CM12 ROM with TWRP recovery, when I got the notification for an OTA update (YNG1TAS1K0). I found out that we had to flash stock recovery to install the update, so I did that, but the OTA update wouldn't install and kept throwing error saying something like "unable to update /sideload/". After multiple attempts, I finally flashed the whole ROM (cm-12.0-YNG1TAS1K0-tomato-signed.zip) via the stock recovery, and now I am on the latest stock build (YNG1TAS1K0). Unfortunately, I am stuck on the stock recovery now. Whenever I try to flash the TWRP recovery (TWRP 2.8.6.0 for Lollipop), it goes into bootloop. I have temporarily flashed stock recovery again to make my phone usable again, but I would really like to flash TWRP again and root it. Any advice/suggestions will be appreciated. Thanks. :highfive:
Click to expand...
Click to collapse
Same problem dude...
I too got same problem, but now solved. Use all in one tool box by gohel.vishal first unlock bootloader, 2] resart phone 3] now enable usb debugging 4] again use toolbox to fash custom recovery 5] after flashing remove battery and restart into recovery, thats all.
Issue fixed using this thread:- http://forum.xda-developers.com/yureka/help/unable-to-flash-custom-recovery-t3108847
(Remember to disable "Update CM recovery" option in Developer Options)
remove battery after install recovery before restarting phone
I'm not necessarily new to the root lifestyle of android but this may be a noob sort of problem
I rooted my LG G2 (t-mobile variant) and installed TWRP 2.6.3.2 if I'm not mistaken so every thing was fine in the beginning, I flashed ROMs (CM 13 PREFERABLY) so afterwards I decided to update my custom recovery from its current version at the time to 2.8.x.x it says that its installed but everytime I attempt to get into recover it give me the lg logo boot with some type of error message for about 2 seconds and then black screen as though there isn't a recovery installed, I've tried flashing it through Flashify and Rashr but to no avail. CAN SOMEONE PLEASE HELP!!!!!
Hi,
I have rooted G2 802 International version, with stock ROM V30B.
Now I try to install TWRP there.
Tried multiple image versions, including from TWRP download site,
last one from here http://techerrata.com/file/twrp2/g2d802/openrecovery-twrp-2.8.5.0-d802.zip
Installed through adb shell,
Code:
dd if=/data/local/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
When I try to enter recovery mode I get a brief "Critical Error" message (in text mode), then promp to choose whether to reboot or enter download mode. No TWRP.
Any ideas ?
You're on LP bootloader which does not allow you boot custom kernel (locked bootloader). Downgrade to KitKat bootloader, custom recoveries and kernels are BUMPED (signed), and KK bootloader thinking these images are official, will pass it to boot.
Use AutoRec for LP from Google Play, it will do everything by one click. Because after flashing KK bootloader, official kernel of Lollipop cannot be booted too as i remember. Anyway AutoRec app will downgrade bootloader, flashes recovery TWRP and modded official kernel image, so will do everything you need.
AutoRec, you had one job...
PolishVodka said:
You're on LP bootloader which does not allow you boot custom kernel (locked bootloader). Downgrade to KitKat bootloader, custom recoveries and kernels are BUMPED (signed), and KK bootloader thinking these images are official, will pass it to boot.
Use AutoRec for LP from Google Play, it will do everything by one click. Because after flashing KK bootloader, official kernel of Lollipop cannot be booted too as i remember. Anyway AutoRec app will downgrade bootloader, flashes recovery TWRP and modded official kernel image, so will do everything you need.
Click to expand...
Click to collapse
AutoRec seems not to work. I installed the VS980 version for the Verizon variant of the phone, but all the app has is a picture of lollipops. Tapping the one at the bottom restores my (corrupted) backup, while tapping the one at the top does absolutely nothing. Any ideas?
UPDATE (8:42PM) -
Figured it out! In the SuperSU app, I disabled "mount namespace separation" and "tapjacking protection" before rebooting and trying AutoRec one more time. This enabled the hidden install button behind the lollipop icon in the app and allowed TWRP to be installed instantly. Hooray!
Hi, I tried to install TWRP using Autorec. But my phone stuck on fastboot mode. although the phone said it is d802 varient after I remove the back it says ls 980. I can run fstboot commands but not adb. Itried 5 different computers with win7/8/10. No good results. worse case is, no download mode at all. So I can not flash the phone. I tried to flash TWRP using fastboot but nothing changed. Can some one please help me
So.... Pokemon Go has a lot to answer for......
I have run into a really strange problem when trying to install an OTA on my *unrooted* Oneplus 2. I have been trying to fix this for days but I have completely run out of ideas.
I originally had a working stock Oxygen 3 (Marshmallow) rom with TWRP recovery on my device (not sure of the version). The device was rooted and apart from not being able to install OTAs, I was fairly happy with the setup. Then along came the Pokemon GO update that banned rooted devices. Ok, "big deal" I thought. I was quite content playing Ingress instead (a far better game by the way that doesn't rely on a "pay to win" structure). I really wasn't too worried but then I found out about "systemless root" and "Magisk". I thought that if I installed this correctly I could still play a bit of Pokemon GO when I wanted to and could toggle a root button in Magisk Manager to install OTAs when they became available.
This is where the problems started.
I followed a guide on how to unroot and install Magisk and "Phh's Superuser". The problem was that the Phh Superuser was being denied permissions for Magisk Manager, there were no pop up notifications prompting me to give it access, just toast notifications. I couldn't for the life of me figure out how to give it permission so the "enable root" slider button kept sliding back, not allowing root. This is when I used SuperSU ver 2.76 (Magisk version) and it seemed to work fine. I now had a stock Marshmallow rom with TWRP and Magisk Manager all working exactly how they should be. I could toggle root and play Pokemon GO, then return to a rooted state when I needed to.
"Awesome, mission accomplished." I thought. Now I just need to toggle root off, download the latest OTA and install it through Flashfire.
First I made a complete nandroid backup (as I've done with other devices many times before) through TWRP. I even copied the backup folder to my PC in case something went wrong.
Well, this is when the nightmare started.
The first mistake I made was to use Flashfire when it clearly stated that Oneplus devices were currently untested. Not sure if it was a big issue or not, but it was a mistake none the less. The second mistake I made was to not stop the stock recovery being replaced when prompted before the reboot. I assumed (and it even states in the app) that the custom recovery should be reverted back to the stock recovery when attempting to apply OTA updates.
So I went ahead and rebooted, waiting for the OTA to install. I'm fairly sure from memory that it went into the stock recovery, flashed the OTA and restarted.
This is when the phone soft bricked.
"Oh well, that is why I made the backup." I thought.
I reflashed TWRP in fastboot mode and attempted to restore my backup. No dice, the phone was still soft bricked.
(And by "soft bricked" and "boot looping" I mean the Oneplus logo was in the middle of the screen, "Powered by Android" was at the bottom and the two blue LEDs for the buttons either side of the fingerprint scanner/home button remained on. This for me was the tell tale sign of the soft brick because these two light go off after a few seconds after rebooting usually.
So from here I have tried EVERYTHING. All I really want now is a working stock (rooted) Marshmallow rom with TWRP. I have downloaded many different full rom zips and attempted to flash them through TWRP with no success, I have returned to stock recovery and tried flashing signed roms with no success, I've even tried flashing the official CM13 rom for Oneplus 2 (with the correct GAPPs and kernel) through TWRP with no luck.
But here is where it gets interesting......
There are a few things that are really weird...
1. I have always been able to get into Fastboot mode and ADB and Fastboot commands "work".
* Operations succeed but don't stick (for example trying to flash TWRP versions 3.0.2-1 and 3.0.2-2 through Fastboot mode result in no recovery being there at all.
2. I can flash TWRP recovery though Fastboot mode but ONLY VERSIONS 3.0.2-0 and lower. I can also successfully flash the stock recovery.
3. I can flash OxygenOS 2.2.1 but NOT ANY VERSION RELEASED AFTER THAT. Doing so results in the soft brick "bootloop" I mentioned earlier.
4. Attempting to flash the official CM13 rom for Oneplus 2 doesn't work either. Originally I got the error 7 message, but after editing "Updater-script" in the rom and re-zipping, the process seemed to work fine in TWRP but the reboot gave me... you guessed it... a softbrick.
I have flashed custom roms on a few different devices before so I'm not a COMPLETE newbie when it comes to this stuff, but I am by no means a developer or even anything close to one. I have bricked this phone in the past (long story, involved getting it without an invite and it being shipped to me with spyware on it) but I used a guide very similar to this and it worked a treat.
www(dot)androidbrick(dot)com/unbrick-oneplus-one-two-3-qualcomm-hs-usb-qdloader-9008
So, thinking that this process would format all partitions and start me from scatch I tried it. It worked fine but I was still unable to upgrade from Oxygen OS 2.2.1 or install TWRP versions 3.0.2-1 or 3.0.2-2.
I have tried all sorts of things. I have wiped, flashed and wiped again. Factory resets, dirty flashes, clean flashes.... everything. All sorts of different sources for the TWRP images and Oxygen roms... nothing seems to work.
It's just so weird considering it's not a hard brick... just a soft brick.
So I really need my phone so I am sitting on this current build because it is the only one that works.
Here are some details of the current build I am using. (using CPU-Z app)
Model: Oneplus 2 (ONE A2001)
Android version: 5.1.1
Oxygen OS version: 2.2.1
Bootloader: Unknown
Build ID: ONE A2001_14_160226
Java VM: ART 2.1.0
OpenGL ES: 3.1
Kernel Architecture: aarch64
Kernel version: 3.10.49-perf+ (56)
Root access: Yes
Super user app: SuperSU Free v2.46 (Chainfire)
OEM unlocking: Enabled
USB debugging: Enabled
And these are some of the ZIPs and IMGs that refuse to be flashed to my device.
TWRP-3.0.2-1-oneplus2
TWRP-3.0.2-2-oneplus2
Grarak's TWRP recovery IMG for Oneplus2 (modified to install CM13) according to this guide:
missingtricks(dot)net/oneplus-2-official-cyanogenmod-13
cm-13.0-20160924-NIGHTLY-oneplus2
OnePlus2Oxygen_14_OTA_019_all_1606041303_bd42fc5cc5cc4ab2
And also my TWRP backup named 2016-09-16--09-44-09
I am really at a loss as to what to do next. ANY help ANYONE could give me would be greatly appreciated. I have been all over the net looking for ways around this bt have had no luck.
As I've said, I'm not a huge tech head, but I'm not a newbie either. The only thing I can think of is that somehow one of the partitions (maybe boot? ) may have been corrupted somehow when messing around with systemless root. But I don't know how considering it's "systemless". If anyone knows how to check for corrupted partitions on the Oneplus 2 please let me know and I'll try it. Maybe formatting these partitions might help (????), but I don't want to permanently brick my phone.
But I don't know how I've got this particular build working if one of the partitions has been corrupted. And the corrupted partition thing is just a guess.....
Please, anyone, someone point me in the right direction. Again, any and all feddback is welcomed and would be very much appreciated.
This is all Pikachu's fault.
Kamakiriash said:
A very long post...
Click to expand...
Click to collapse
The normal way too update from OOS 2 to OOS 3 is:
Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
Reboot recovery via TWRP so that you now have a recovery that's compatible with the new bootloader
Wipe data, cache & dalvik-cache (but not internal storage)
Flash the OOS 3 signed flashable zip again to update the system
Flash one of the modified SuperSU zips if you want root
Reboot system
All the files you need are in post #1 of this thread.
Thank you so much Spannaa!
I was clearly missing a vital step here and let it be a lesson to anyone else in this situation....
As Spannaa said......
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
4. Wipe data, cache & dalvik-cache (but not internal storage)
5. Flash the OOS 3 signed flashable zip AGAIN to update the system.
Again, thankyou Spanna for your quick and accurate response.
The order in which you flash zips and imgs is very important it seems.
You really saved me.
I restored the TWRP backup and I am back to where I started.
Is it now possible to apply OTAs when I toggle the root off in Magisk manager and install using the stock recovery? What do you think would be the best way to do this?
And would it be worth moving to the official build of CM13 for Oneplus 2?
Thanks again, Spannaa. :victory:
Kamakiriash said:
Thank you so much Spannaa!
I was clearly missing a vital step here and let it be a lesson to anyone else in this situation....
As Spannaa said......
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
4. Wipe data, cache & dalvik-cache (but not internal storage)
5. Flash the OOS 3 signed flashable zip AGAIN to update the system.
Again, thankyou Spanna for your quick and accurate response.
The order in which you flash zips and imgs is very important it seems.
You really saved me.
I restored the TWRP backup and I am back to where I started.
Is it now possible to apply OTAs when I toggle the root off in Magisk manager and install using the stock recovery? What do you think would be the best way to do this?
And would it be worth moving to the official build of CM13 for Oneplus 2?
Thanks again, Spannaa. :victory:
Click to expand...
Click to collapse
Glad you're sorted.
Not sure about Magisk as I've never used it.
CM13 is OK but whether it's worth you moving to it is your choice. Personally, I prefer TipsyOS!
Hi,
I face the exact issue with same Oxygen OS and TWRP versions mentioned, I have tried the above steps but there are some problems:
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
Click to expand...
Click to collapse
when I checked the option (Zip signature verification) in TWRP, the installation failed with error "Zip signature verification failed! Error installing zip file '/sdcard/oneplus.zip'", but it's successfully installed when I unchecked (Zip signature verification) option.
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
Click to expand...
Click to collapse
second problem is that after installing the TWRP 3.0.2-2 (or above), then reboot recovery, I can't access the recovery again and the phone stuck on bootloop.
any idea ?
Aood said:
Hi,
I face the exact issue with same Oxygen OS and TWRP versions mentioned, I have tried the above steps but there are some problems:
when I checked the option (Zip signature verification) in TWRP, the installation failed with error "Zip signature verification failed! Error installing zip file '/sdcard/oneplus.zip'", but it's successfully installed when I unchecked (Zip signature verification) option.
second problem is that after installing the TWRP 3.0.2-2 (or above), then reboot recovery, I can't access the recovery again and the phone stuck on bootloop.
any idea ?
Click to expand...
Click to collapse
I don't have a OP2 anymore but that post was seven months ago and the instructions worked for numerous users.
Don't enable zip signature verification in TWRP - it's unnecessary.
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option and then reboot recovery directly from TWRP.
thanx for replay Spannaa,
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option and then reboot recovery directly from TWRP.
Click to expand...
Click to collapse
I have already did that, but same issue once I reboot "directly from TWRP" , the TWRP doesn't show up and bootloop start again.
Aood said:
thanx for replay Spannaa,
I have already did that, but same issue once I reboot "directly from TWRP" , the TWRP doesn't show up and bootloop start again.
Click to expand...
Click to collapse
Last chance and then I'll leave this for someone that has the OP2.
Are you rebooting recovery "directly from TWRP" or rebooting system?
Is your bootloader still unlocked?
Last chance and then I'll leave this for someone that has the OP2.
Are you rebooting recovery "directly from TWRP" or rebooting system?
Is your bootloader still unlocked?
Click to expand...
Click to collapse
Yes, rebooting recovery "directly from TWRP"
and bootloader loader is unlocked,..
anyway it's not important to fix the phone, it's almost one year since last time I use it, yesterday I saw it in the drawer and try to figure out the issue..,
Hi guys,
can someone tell me what can I do to fully install new G6 update: V11i-JAN-08-2018?
Update package downloaded, I tap "install now", I wait for progress bar to go 100% then automatic reboot happens.
The phone boots into TWRP and that's it. No installation progress or what so ever.
I tried to wipe dalvik cache / cache and rebooting the phone. It eventually booted up after 4 or 5 restarts. And I had to download update all over again.
Second try, the same, I tap "install now", wait for progress bar to go all the way, automatic reboot into TWRP.
What can I do to perform this update?
My G6 has bootloader unlock and TWRP, and SuperSu istallation from this guide: https://forum.xda-developers.com/lg-g6/how-to/official-lg-g6-bootloader-unlock-t3614719
Model number
LG-H870
Hardware version
Rev. 1.0
Basedband version
MPSS.TH.2.0.1.c3.1-00017-M8996FAAAANAZM-1.100831.1.103198.5
Kernel version
3.18.31
Build number
NRD90U
Software version
V10t-260-06
Please help.
landorr said:
Hi guys,
can someone tell me what can I do to fully install new G6 update: V11i-JAN-08-2018?
Update package downloaded, I tap "install now", I wait for progress bar to go 100% then automatic reboot happens.
The phone boots into TWRP and that's it. No installation progress or what so ever.
I tried to wipe dalvik cache / cache and rebooting the phone. It eventually booted up after 4 or 5 restarts. And I had to download update all over again.
Second try, the same, I tap "install now", wait for progress bar to go all the way, automatic reboot into TWRP.
What can I do to perform this update?
My G6 has bootloader unlock and TWRP, and SuperSu istallation from this guide: https://forum.xda-developers.com/lg-g6/how-to/official-lg-g6-bootloader-unlock-t3614719
Model number
LG-H870
Hardware version
Rev. 1.0
Basedband version
MPSS.TH.2.0.1.c3.1-00017-M8996FAAAANAZM-1.100831.1.103198.5
Kernel version
3.18.31
Build number
NRD90U
Software version
V10t-260-06
Please help.
Click to expand...
Click to collapse
Never, never, never try to do an OTA update with a Custom Recovery, it could **** up your device, same thing goes for rooted devices or with mods.
You have three options:
- Flash the Kdz trough LGUp+Uppercut, you'll lose both root and TWRP
- Install the update trough LGBridge (It could wipe your device), you'll lose both root and TWRP
- Flash the 11I zip trough TWRP: https://forum.xda-developers.com/lg-g6/development/rom-eu-lg-h870-11i-rom-t3743582
Good luck!
You have custom recovery so you can't install OTA, your way it's flashing ZIP ROM with twrp
https://forum.xda-developers.com/lg-g6/development/rom-eu-lg-h870-11i-rom-t3743582