TWRP error after flashing Nougat Rom - G3 Q&A, Help & Troubleshooting

Guys,
I´ve made a mistake when i flashing @mistercheese 7.0 Nougat Rom, i´ve flashed Mr. Bump before flash supersu, then i lost access to TWRP, the phone give me a black flashing screen and don´t enter the TWRP.
I´ve read and tried many tutorials for root or install TWRP by fastboot but pc don´t recognize my G3 as ADB device, i´ve tried 3 differents pc´s.
Someone have ideas?
PS: Sorry for my bad english, i´m from Brazil

https://m.youtube.com/watch?v=x-cTpsDLNF8

@mistercheese thats don't work for me, i have same black flashing screen with Android robot and red x icon aftet do this procedure.
The screen blinks too fast and i can't read the error message...

I have the same problem. No possibility to flash root from within Nougat ROM and computers not recognizing the phone correctly in fastboot mode. So also no possibility to flash TWRP again via Fastboot.
What to do? Anyone has experiences to go back from Nougat to stock MM via LG Flash Tool?
That would allow me to root again from MM platform with purpledrake or something.

@lal000r have you tested on windows 10 and 8? I've tested only windows 10 and no success on connection on bootloader mode....

I have tested on WIndows 10 and WIndows 7 with no luck on installing the correct driver. Tried different drivers from LG and Universal ADB/Fastboot drivers.

Same for me, well, just sit and wait

Related

Bootloop after Xposed install, Hard Reset not working

Hi there,
i rooted my G3 using Towelroot and all worked fine.
Today i installed the actual Version Xposed Framework and after rebooting it entered a Bootloop.
So i tried to Hard Reset my G3 but when i confirm it the Android with the Gaers show up for a second and then my G3 keeps showing the LG Logo for a few Minutes till i disassamble the Battery.
Next step i try is to flash a firmware in Download mode, but i cant get the Drivers to work... =(
Someone have some hints for me?
patrickn2282 said:
Hi there,
i rooted my G3 using Towelroot and all worked fine.
Today i installed the actual Version Xposed Framework and after rebooting it entered a Bootloop.
So i tried to Hard Reset my G3 but when i confirm it the Android with the Gaers show up for a second and then my G3 keeps showing the LG Logo for a few Minutes till i disassamble the Battery.
Next step i try is to flash a firmware in Download mode, but i cant get the Drivers to work... =(
Someone have some hints for me?
Click to expand...
Click to collapse
Have you choosen ART modality?
If i would say "what the hell is that" ... would u slap me?
No.. i dont have chosen that..
Bigger problem is that i dont get any usb driver working for firmware update in Download mode.. =(
OK... i managed to get the drivers working.
But further Problem ist now that im not able to flash anything on my device...
Neither the TOT Method, nor updating with the Original LG Support Tool is working...
Support Tool tells me my Model Number and that my Version is most actual.
If i update anyway it stucks at 4% and tell me it cant connect.
TOT Tool tells me that my Version Number is not correct... but it is..
With the KDZ Update Tool it stucks at 4% like the Original method.
Same problem here
Any one can help us?
Solution
Hi there,
the Problem was my PC...
I was on a Windows 8.1 64bit.
Switched to a Win7-PC and all is working fine.
You should try to use the Original LG cable, or another "Original" Cable and connect it to a USB-Port on the Back of your PC (directly to the Mainboard)
On a blank Win 7:
- I installed the LG PC Suite
- Updated the PC Suite
- Connected my LG in Download Mode
- Let the PC install all drivers,
- Disconnected the Phone
- Downloaded the actual LG Mobile Support Tool
- Let the Support tool do the work
After this i got my first OTA Update and its working like a charme

Stuck in cwm boot loop, help plz

I have LG optimus g pro E988 (India) , rooted and installed debloted rom from anirudh, done so many stupid things with my phone but never bricked it but my phone model number is changed and now its E980, i was bored with my jb so think about update it to KK so i go to cwm and restore the stock lg rom which was also rooted then hit update and after my phone downloaded update i m stuck in cwm boot loop, did every thing but nothing work because my phone driver is not matching because it is now E980...... i tried to connect adb to delete fota files but there is no adb devices in list, Please help if u can and sorry for bad english.
i tried to fallow this link-
http://forum.xda-developers.com/optimus-g-pro/general/guide-how-to-solve-stuck-cwm-twrp-t2852103
No success yet.
Tried to use LG mobile support tool to go back to stock but no success, what weird is in LG mobile support tool my phone shows as E988(Correct) when i connect with download mode on but when i m in cwm and try to connect to pc in device manager it shows as E980 and yellow exclamation mark. if i can connect to adb, my problem would be solve but how????? can anyone help?????:crying:
No upgrade item to fix
In lg mobile support tool when i try to upgrade recovery it says no upgrade item to fix, help me guys i cant fix my phone yet:crying:
If you're still stock at the cwm loop, try flashing cwm again with a cwm.zip file. That works for me every time when I get stock in the recovery loop.
Edit: Besides flashing the recovery zip file, you also need to flash your ROM and gapp from within the new recovery you just flashed.
yourseone said:
Tried to use LG mobile support tool to go back to stock but no success, what weird is in LG mobile support tool my phone shows as E988(Correct) when i connect with download mode on but when i m in cwm and try to connect to pc in device manager it shows as E980 and yellow exclamation mark. if i can connect to adb, my problem would be solve but how????? can anyone help?????:crying:
Click to expand...
Click to collapse
That is correct, get an ADB working folder in your computer (or download it from Google) and push a ROM with it, search for the commands on how to push a ROM through ADB, I'm not at home or else I'll point it to you step by step, try it on yourself and let me know if you need additional help.
Working now (Fixed)
Fixed it by flashing KDZ
First Method - http://forum.xda-developers.com/showthread.php?t=2420219
Also Thanks for replying guys, I thought OG Pro community is dead, but after searching for lot about it i found the solution. XDA Rocks ..... :good:

Mix 2 bricked?! Flashing went wrong. Need help please.

Hey guys,
so this my problem:
I got the Mix 2 with the Chinese ROM. With the XiaoMiTool by Francesco Tescari I updated to the Global ROM V9.1.2.0 because I didn't want to wait to unlock the bootloader. This worked but I only had the choice to set China as my region. Since this was a common problem with updating the ROM without unlocking the phone I unlocked it and waited for 3 days to unlock.
Today I installed TWRP and installed the ROM xiaomi.eu_multi_MIMix2_7.11.16_v9-7.1. After this I was stuck with the Mi bootup logo. In TWRP I deleted cache, system, data. This worked EXCEPT for system. I thought updating TWRP to the newest version would help solve this issue. But since I'm new to this I didn't update it within TWRP but just installed the newer version via the commandfastboot flash recovery twrp.img. The result is that I can not get in recovery mode anymore. The only option is fastboot mode or the regular Mi logo endless boot.
What I tried so far: EDL flash method via adb/MiFlash but both don't work. The XiaoMiTool won't work too. The Mi PC Suite won't recognise the phone. When I use the edl.cmd the phone will go black for 2-3s and then return to fastboot.
I guess the problem at this point is that usb debugging is not turned on since TWRP installed the EU ROM and I could never get in it to enable the debug mode.
I couldn't find a solution to solve the boot up problem and can't seem to install/flash a new ROM at this point.
So what can I do? Do I need that special usb cable? Will the EDL points help me?
Maybe/Hopefully you can help me out.
EDIT:
When I turn on the phone it will directly go into fastboot mode. A normal start is not possible anymore?!...
EDIT 2:
I am now running the latest Global Rom this guide did it for me: en.miui. com/thread-1351514-1-1. html
Good to hear you got it up and running.
derpaherp said:
Hey guys,
so this my problem:
I got the Mix 2 with the Chinese ROM. With the XiaoMiTool by Francesco Tescari I updated to the Global ROM V9.1.2.0 because I didn't want to wait to unlock the bootloader. This worked but I only had the choice to set China as my region. Since this was a common problem with updating the ROM without unlocking the phone I unlocked it and waited for 3 days to unlock.
Today I installed TWRP and installed the ROM xiaomi.eu_multi_MIMix2_7.11.16_v9-7.1. After this I was stuck with the Mi bootup logo. In TWRP I deleted cache, system, data. This worked EXCEPT for system. I thought updating TWRP to the newest version would help solve this issue. But since I'm new to this I didn't update it within TWRP but just installed the newer version via the commandfastboot flash recovery twrp.img. The result is that I can not get in recovery mode anymore. The only option is fastboot mode or the regular Mi logo endless boot.
What I tried so far: EDL flash method via adb/MiFlash but both don't work. The XiaoMiTool won't work too. The Mi PC Suite won't recognise the phone. When I use the edl.cmd the phone will go black for 2-3s and then return to fastboot.
I guess the problem at this point is that usb debugging is not turned on since TWRP installed the EU ROM and I could never get in it to enable the debug mode.
I couldn't find a solution to solve the boot up problem and can't seem to install/flash a new ROM at this point.
So what can I do? Do I need that special usb cable? Will the EDL points help me?
Maybe/Hopefully you can help me out.
EDIT:
When I turn on the phone it will directly go into fastboot mode. A normal start is not possible anymore?!...
EDIT 2:
I am now running the latest Global Rom this guide did it for me: en.miui. com/thread-1351514-1-1. html
Click to expand...
Click to collapse
hey - how did you get mi unlock to work? im having this problem: mi unlock tool 2.3.803.10. it won't show the mi mix 2 as connected with xiaomi drivers, only with google drivers it will show as connected and then let me click unlock. however, it stops at 50% and shows error "couldnt verify device unkown error (-1)". ive logged on to i.mi.com and located the device through find device. does anyone have any pointers how i can unlock, because i want to switch to global dev rom and miui updater wont let me update through system with error "android version is different".
best, alastair

Letv LeEco Le1s hard bricked

Dear members, this is my first post and the problem is very complicted, so please bear with the long post
Device details:
LeEco Le1s (x500)
MTK6795 chipset
3 GB + 32 GB
Background:
I downgraded my ROM from 19s to 14s with SP Flash tool and the phone booted normally. I went through the initial setup, unlocked Developer mode and USB debugging. Then I opened the adb toolkit on Win 7 x86 machine to unlock bootloader and install twrp custom recovery at single go (instead of letting phone rebot after bootloader unlock and then proceeding with recovery flashing).
Now phone went to soft brick, to overcome which I needed to flash userdata with sp flash tool (I have done this in past also following a tutorial, the same files were used this time). But flashing process resulted in BROM error and I was not successful.
So, I re-flashed the original 14s rom via SP flash tool to get the things back to working, but phone didn't boot properly and bootloop situation was still there. I again reflashed the same ROM and this timephone entered red light of death mode, and didn't boot up after flashing original rom.
Now, I again googled this problem and found that we need to format flash with bootloader. Here the problem complicated further.
As soon as I formatted the flash and the bootloader, laptop stopped detecting the phone via usb cable. Now I can't flash any rom using SP flash tool as the phone is not detectable.
I have reinstalled my windows 7 32 bit operating system and reinstalled all the drivers for MTK smartphone. I have another Le1s phone running on 19s version of EUI marshmallow with stock recovery and locked bootloader which is detecting fine without problems.
Please guide me how can I resolve the problem.
Also guide if the other phone can anyhow help in this matter in terms of software backup for SP flash tool (I couldn't find a way of backing stock rom using SP flash tools.
Problem summary:
1) Flash with bootloader formatted
2) Phone is not detectable on Windows 7 32 bit OS and latest SP flash tools
3) Red LED turns on when phone connected to charger or laptop via usb cable,nothing on LCD display
4) Can't reach bootloader or recovery either
Help will be really appreciated. You all know the value of data stored on smartphones.
Thanks in advance!!

(Solved) Fastboot Devices Shows as Question Mark (?????? Fastboot)

Hello everyone,
So I was just finished flashing MIUI 12 official recovery rom when I found out that I have an issue where the Region is set to China. When I'm about to flash the Region Fix Patch, I encounter another problem where the custom recovery i used to have was replaced by Xiaomi stock recovery.
The biggest problem occurred when I'm about to flash custom recovery. As I typed in Fastboot Devices command, my device ID shows up as bunch of question mark (?????? Fastboot) and I can't flash or boot my device into custom recovery
I have tried toggling USB Debugging on and off, revoking USB Debugging, reinstalling USB driver on my PC, as well as switching the cable I used but none of them seems to fix the problem.
Does anyone ever encounter the same problem as mine? How can you work around this problem and able to flash recovery again? Thank you
I was coming from Lineage OS 18.1 before flashing MIUI 12. Please help me get
SOLVED. I switched to a different PC and it worked flawlessly
Bro same problem I m facing now ....... I m unable to lock bootloader .....during fastboot I face same isuue(????????)..... Bro do uh get the solution of this problem please reply

Categories

Resources