Develop Bugs

New version of FreeGee used; stuck in CWM bootloop

I have done this before but I used what seems to be a different version of freegee (didn't have the option to backup efs or flash TWRP) so I unlocked my device and after it had completed I rebooted and then powered down. I put my phone in to CWM and flashed the stock debloated ROM. After flashing this ROM I was stuck in a bootloop. I ended up using LG Tool to get it back to stock. I thought it must have been a random once off issue so I tried again with Freegee, same thing happened, only this time no matter what I do I can not get LG Tool to fix the issue as it keeps giving me the error of low battery even though it is at full capacity. I then tried to use BC2 to flash a kdz file and I get the same error. I have since tried factory resetting, sideloading different recoveries, ROMs and basebands without boot. I have tried to use LG Tool about 50 times and it is not working. I have changed USB ports, reinstalled drivers etc, just keeps giving me that error. Yes I have set permission in the app and I am using Windows 7

uppon2 said:
I have done this before but I used what seems to be a different version of freegee (didn't have the option to backup efs or flash TWRP) so I unlocked my device and after it had completed I rebooted and then powered down. I put my phone in to CWM and flashed the stock debloated ROM. After flashing this ROM I was stuck in a bootloop. I ended up using LG Tool to get it back to stock. I thought it must have been a random once off issue so I tried again with Freegee, same thing happened, only this time no matter what I do I can not get LG Tool to fix the issue as it keeps giving me the error of low battery even though it is at full capacity. I then tried to use BC2 to flash a kdz file and I get the same error. I have since tried factory resetting, sideloading different recoveries, ROMs and basebands without boot. I have tried to use LG Tool about 50 times and it is not working. I have changed USB ports, reinstalled drivers etc, just keeps giving me that error. Yes I have set permission in the app and I am using Windows 7
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=48205695&postcount=13

atifsh said:
http://forum.xda-developers.com/showpost.php?p=48205695&postcount=13
Click to expand...
Click to collapse
Thank you, I will use that if I ever get LG Tool to stop throwing me the low battery warning. What a stupid program to not give you the option to bypass it. Surely there is a way I can do this. My battery is at 99%. I just flashing madmack hacked and lockified recovery and now I can't even get in to recovery to do sideloads. I am running out of options, my only way is to get LG Tool or B2C to work
EDIT* I have recovery back. GRR why is this stupid message about low battery keep popping up

uppon2 said:
Thank you, I will use that if I ever get LG Tool to stop throwing me the low battery warning. What a stupid program to not give you the option to bypass it. Surely there is a way I can do this. My battery is at 99%. I just flashing madmack hacked and lockified recovery and now I can't even get in to recovery to do sideloads. I am running out of options, my only way is to get LG Tool or B2C to work
EDIT* I have recovery back. GRR why is this stupid message about low battery keep popping up
Click to expand...
Click to collapse
have not tested this from cm rom but works from any stock. bytheway i have optimus G not pro
from recovery adb push rom.zip (your rom)
adb push rom.zip /sdcard/0
(0 required for cwm and cm10.2)
flash that rom
enable debugging
run lgflash tool one that supports large files or the online one it will pass the battery and auto restart in download mode there it will give error just unplug replug and retry and it will be flashed this time.

atifsh said:
have not tested this from cm rom but works from any stock. bytheway i have optimus G not pro
from recovery adb push rom.zip (your rom)
adb push rom.zip /sdcard/0
(0 required for cwm and cm10.2)
flash that rom
enable debugging
run lgflash tool one that supports large files or the online one it will pass the battery and auto restart in download mode there it will give error just unplug replug and retry and it will be flashed this time.
Click to expand...
Click to collapse
I am unsure what this is but I am interested? Thanks, I ended up doing what I was trying to do in the first place and IT WORKED
To anybody that faces the same issue:
in recovery sideload install madmacks TWRP file attached below
after that is installed flash CM11 using the same sideload
The command in adb is adb sideload (your file name in here without the brackets.zip) You must include .zip
It is strange because it didn't work the first 3 times I flashed the ROM and on the fourth it worked, so keep trying

i can fix bootloop to cwm or recovery just 2 minutes. but u have to backup your stock recovery fírst before install cwm or twrp.
so thiss step to solve after u have boot loop. that u need to restore back your stock recovery on mmcblk0p28 then reboot. you will stuck at factory software repair. keep ur fone connected with the computer and type adb reboot. then u can boot into android os. and final step. u reinstall your custom recovery again and Enjoy. this fixing not for newbie and im typing it on my fone. someone can make automation script to help People solve it im lazy
Sent from my Optimus G Pro using Tapatalk

thaiminhan said:
i can fix bootloop to cwm or recovery just 2 minutes. but u have to backup your stock recovery fírst before install cwm or twrp.
so thiss step to solve after u have boot loop. that u need to restore back your stock recovery on mmcblk0p28 then reboot. you will stuck at factory software repair. keep ur fone connected with the computer and type adb reboot. then u can boot into android os. and final step. u reinstall your custom recovery again and Enjoy. this fixing not for newbie and im typing it on my fone. someone can make automation script to help People solve it im lazy
Sent from my Optimus G Pro using Tapatalk
Click to expand...
Click to collapse
Thanks for trying to help. I am not running stock and can not get a stock ROM to work (with locked bootloader obviously)
LG Tool is requesting for a TOT file which the E988 doesn't have, I have tried using E98810D_00.kdz file in the software field but it is not recognising the cab file. The DLL file is recognised but I don't know what else to do from there.
LG Mobile Support Tool keeps failing on me due to low battery error which as you can see, I have been trying my hardest to get it to work. Battery is at 99% but it still won't flash! - I am stuch with a custom ROM and a dodgy unlocked bootloader due to the latest release FreeGee.
I tried the old file you attached but it fails to download the image file to unlock my bootloaders, I guess because it is already unlocked.
What I need now is to find a way to relock my bootloader that doesn't involve LG Tool/LG Mobile Tool and then try the old FreeGee app again. Or I find a way to get passed this stupid battery warning

uppon2 said:
I have done this before but I used what seems to be a different version of freegee (didn't have the option to backup efs or flash TWRP) so I unlocked my device and after it had completed I rebooted and then powered down. I put my phone in to CWM and flashed the stock debloated ROM. After flashing this ROM I was stuck in a bootloop. I ended up using LG Tool to get it back to stock. I thought it must have been a random once off issue so I tried again with Freegee, same thing happened, only this time no matter what I do I can not get LG Tool to fix the issue as it keeps giving me the error of low battery even though it is at full capacity. I then tried to use BC2 to flash a kdz file and I get the same error. I have since tried factory resetting, sideloading different recoveries, ROMs and basebands without boot. I have tried to use LG Tool about 50 times and it is not working. I have changed USB ports, reinstalled drivers etc, just keeps giving me that error. Yes I have set permission in the app and I am using Windows 7
Click to expand...
Click to collapse
i have same problem with you, anyone have solution??

kuwir said:
i have same problem with you, anyone have solution??
Click to expand...
Click to collapse
Check this
http://forum.xda-developers.com/showthread.php?p=48225776
Sent from my LG-E980 using XDA Premium HD app

kuwir said:
i have same problem with you, anyone have solution??
Click to expand...
Click to collapse
First try to use LG Mobile Tool. All files and instructions found here CLICK ME
If that doesn't work the follow the instructions I posted earlier and it will get your phone booting again. As for getting back to stock and unlocking the bootloaders without causing kernel issues, I am still waiting for a response from Seth. He has been making a lot of changing as this is a known problem. The latest version is supposed to work like it used to now.

uppon2 said:
I am unsure what this is but I am interested? Thanks, I ended up doing what I was trying to do in the first place and IT WORKED
To anybody that faces the same issue:
in recovery sideload install madmacks TWRP file attached below
after that is installed flash CM11 using the same sideload
The command in adb is adb sideload (your file name in here without the brackets.zip) You must include .zip
It is strange because it didn't work the first 3 times I flashed the ROM and on the fourth it worked, so keep trying
Click to expand...
Click to collapse
Thanks! This worked 100%. Something's really up with the freegee CWM, totally useless. Had 3 days of a headache till I saw this post. I used to be a CWM guy, now TWRP all the way...! The interface is touch based and much easier to handle than CWM. Best of all it doesn't go into a bootloop! Cheers! :good::good:

bootlooped and cannot do anything in ADB

Hi,
I have ZE551ML. I rooted using method 2 (temporary CWM). Before installing the latest OTA, I did full unroot in SuperSU and uninstalled Xposed. I proceeded with the normal OTA. Upon restart, it was stuck in bootloop. I can get to fastboot and select recovery mode there. My main problem is I can't see the device in ADB. Whenever I type adb devices, I just keep getting "list of devices attached" and my device is nowhere there. I'm pretty sure I have the Intel drivers and ADB tools since I used the same PC in flashing/rooting this device and an older Zenfone 5.
Is there any way I can unbrick my phone. Or is there any way I can fix the ADB not showing my device?

Jaymz123 said:
Hi,
I have ZE551ML. I rooted using method 2 (temporary CWM). Before installing the latest OTA, I did full unroot in SuperSU and uninstalled Xposed. I proceeded with the normal OTA. Upon restart, it was stuck in bootloop. I can get to fastboot and select recovery mode there. My main problem is I can't see the device in ADB. Whenever I type adb devices, I just keep getting "list of devices attached" and my device is nowhere there. I'm pretty sure I have the Intel drivers and ADB tools since I used the same PC in flashing/rooting this device and an older Zenfone 5.
Is there any way I can unbrick my phone. Or is there any way I can fix the ADB not showing my device?
Click to expand...
Click to collapse
maybe u didn't remove xposed framework files, that's the reason for bootloop/brick

Siddk007 said:
maybe u didn't remove xposed framework files, that's the reason for bootloop/brick
Click to expand...
Click to collapse
you mean the modules like greenify?

Jaymz123 said:
you mean the modules like greenify?
Click to expand...
Click to collapse
no, not modules. xposed framework which u installed using installxposedframework.bat from pc

Ok, I was able to recover my phone by flashing the pre-rooted system.img (method 1). I want to sideload the whole stock firmware but my problem remains. If I boot my phone normally, adb devices command shows my phone. But whenever I go to fastboot either by typing adb reboot bootloader or by holding ON/vol up, my phone is not showing up in ADB, therefore I can't sideload anything.
Is there any way I can unroot or revert back to a stock ROM? I'm kind afraid to unroot in SuperSU because I bootlooped yesterday (might have been the xposed though as suggested by Skid). Is there any stock system.img out there?

Jaymz123 said:
Ok, I was able to recover my phone by flashing the pre-rooted system.img (method 1). I want to sideload the whole stock firmware but my problem remains. If I boot my phone normally, adb devices command shows my phone. But whenever I go to fastboot either by typing adb reboot bootloader or by holding ON/vol up, my phone is not showing up in ADB, therefore I can't sideload anything.
Is there any way I can unroot or revert back to a stock ROM? I'm kind afraid to unroot in SuperSU because I bootlooped yesterday (might have been the xposed though as suggested by Skid). Is there any stock system.img out there?
Click to expand...
Click to collapse
Put the update file onto your sd card, rename to MOFD_SDUPDATE.zip.
Reboot and it should update as long as the pre-root image was 19.40.22 .
Reflash TWRP if the bootloader is unlocked and you have a rooted phone with custom recovery...
Yes it works, and yes I did it yesterday exactly like that...
I have a 64gb 2.3ghz 551ML with unlocked bootloader. Don't know if the unlocked bootloader might be the factor that allows this to work...

I just went on and made full unroot from SuperSU. It went smoothly. I guess the one that caused my bootloop was the uinstalled xposed framework.
Bootloader is locked now. The only problem I have now is the ADB thing. My phone is not detected when in recovery but works just fine when normally booted. I have the latest USB driver from Intel and the other one from ASUS. I also have installed ADB installer, the one with the blue screen and where you press Y few times to install.

Help required with bricked Oneplus 3

Hi,
I have installed MIUI in my OP3 this morning, which was working fine. There was an OTA update, after installing it, device rebooted and entered into recovery mode and it was hanging there for more than an hour. Whrn I tried to reboot, it was off and never came up. Tried unbrick using MSM Download Tool and then I am able to get into boot loader screen. From there I have tried to flash TWRP, but if I reboot, I am getting this message only. Currently I have access to bootloader, if I flash TWRP and choose to boot from recovery (from pc), I have access to OTG also. But even after flashing a ROM, If I reboot, I am getting attached screen only.
I have access to TWRP, only when I chiose to reboot from All in one tool from PC.
Please help me.

you have to use method 2of unbrick not method1.it will flash whole stock rom , then reboot enable developer options etc then flash twrp recovery then go ahead.

Use Method 2. Make sure to follow all steps. Please do quote me otherwise i do not know if you need any further help.

You flashed oficial beta update on mui rom and you have a mess.
Download official OP 4.1.6 rom and try to flash it.
if its not fixed the try wipe everythng (system data ect) and then flash the rom

Puddi_Puddin said:
Use Method 2. Make sure to follow all steps. Please do quote me otherwise i do not know if you need any further help.
Click to expand...
Click to collapse
Hi,
I am following method 2 now. I have switched off the phone and connecting to laptop, as soon as I connect to laptop, it is getting into bootloop (without pressing any button). Phone is not detected in laptop.

colossus_r said:
You flashed oficial beta update on mui rom and you have a mess.
Download official OP 4.1.6 rom and try to flash it.
if its not fixed the try wipe everythng (system data ect) and then flash the rom
Click to expand...
Click to collapse
I have tried to by wiping everything and tried to restore from OTG pendrive. Tried to flash Firmware + Modem, tried to flash different ROM. Nothing helped.
I am in travel now, having limited internet connectivity. I will reach home and then try to download official OP as you suggested.
I do not have data in phone, all the data is already copied to laptop.

colossus_r said:
You flashed oficial beta update on mui rom and you have a mess.
Download official OP 4.1.6 rom and try to flash it.
if its not fixed the try wipe everythng (system data ect) and then flash the rom
Click to expand...
Click to collapse
Finally, method 2 worked. Thanks a lot.

nagurvidyasagar said:
Finally, method 2 worked. Thanks a lot.
Click to expand...
Click to collapse
I was having the same problem like you how did you solve it ?

Install Magisk without PC and root

Hello everyone,
Since I'm facing difficulties connecting my Nexus 5X to my PC (believe me, I have tried nearly everything), I was wondering if it is possible to flash Magisk to my phone without the use of a PC. The bootloader is still unlocked because i've rooted my phone previously (when it still could connect to my PC). All the possibilities I ran into require either root or a PC.
I hope one of you guys knows a way how to handle this without losing all my data.
Thanks in advance!

Assuming you don't have a custom recovery installed either?? What's the "difficulty with trying to hook to a PC?

No, I don't have a custom recovery installed. There are more people facing this problem: https://forum.xda-developers.com/nexus-5x/help/unlock-bootloader-fastboot-detecting-t3236946/page4. Solution is not working for me for some reason.

To install magisk you need a custom recovery. And to install a custom recovery you need a pc.
Sent from my [device_name] using XDA-Developers Legacy app

I was afraid of that. Maybe i'll go with a factory reset then. Thanks tot the help anyways.

jd1639 said:
To install magisk you need a custom recovery. And to install a custom recovery you need a pc.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Not true, you just need a working adb connection with a computer. You can flash patched boot image with fastboot then

_Hitman47 said:
Not true, you just need a working adb connection with a computer. You can flash patched boot image with fastboot then
Click to expand...
Click to collapse
So..... The bottom line is..... You still need a PC.

_Hitman47 said:
Not true, you just need a working adb connection with a computer. You can flash patched boot image with fastboot then
Click to expand...
Click to collapse
You're right. You can flash a boot image with fastboot. Is there a boot image that has magisk as party of it?

Well, I have installed Magisk Manager, and it gives me the option to patch a boot image-file. When I choose this option it askes me to select te original boot image-dump (.img or .img.tar). Since I'm no expert and I don't know where to find this and what this does, I'm afraid of losing my data or bricking my phone.

bluesh4rk said:
Well, I have installed Magisk Manager, and it gives me the option to patch a boot image-file. When I choose this option it askes me to select te original boot image-dump (.img or .img.tar). Since I'm no expert and I don't know where to find this and what this does, I'm afraid of losing my data or bricking my phone.
Click to expand...
Click to collapse
You would use the boot.img from the factory image that your rom is based on. Find your device below and download the 1 GB zip. Inside this zip is another zip you'll need to open to find the boot image (boot.img). Flashing boot images doesn't wipe internal storage, but it does remove root if you had it installed.
Factory images:
https://developers.google.com/android/images?hl=en
There's not really a collection of stock boot images besides what's included in the factory image.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
You would use the boot.img from the factory image that your rom is based on. Find your device below and download the 1 GB zip. Inside this zip is another zip you'll need to open to find the boot image (boot.img). Flashing boot images doesn't wipe internal storage, but it does remove root if you had it installed.
Factory images:
https://developers.google.com/android/images?hl=en
There's not really a collection of stock boot images besides what's included in the factory image.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Instead of downloading the entire ROM, you might find what you need here: https://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169

bluesh4rk said:
Hello everyone,
Since I'm facing difficulties connecting my Nexus 5X to my PC (believe me, I have tried nearly everything), I was wondering if it is possible to flash Magisk to my phone without the use of a PC. The bootloader is still unlocked because i've rooted my phone previously (when it still could connect to my PC). All the possibilities I ran into require either root or a PC.
I hope one of you guys knows a way how to handle this without losing all my data.
Thanks in advance!
Click to expand...
Click to collapse
Hello there ,
I have same as your issue.
My pixel 2 xl non rooted with unlocked bootloader.
So, Is it possible to flash latest OTA update directly through the phone via stock recovery?
As you aware that with the known and common pixel 2 xl issue which you can't get it connected to PC.
I'm stuck on October update and I'd be glad if someone could help me out on this matter.

Hi I'm new to rooting. I have a ZTE n9137 tempo x looking to root .I can't get this done.no recovery no boot.img no custom recovery none what so ever .the olny I keep reading is that I have to have a PC I don't like I said I'm new to root but I'm trying anything to get this done I unlocked the oem but I don't thing that it is enabled.?.?and I don't think that the phone can do this ota so now what ?? If I'm wrong plzz tell me where at I'm wrong and how to gain root thanks for all the help

Update not got root

hi everybody i wanted to root a samsung a3 2018(idk what version it is because it is still my grandma's phone) and as i know there isn't any twrp version for that phone

Bootloop after installing magisk

hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?

mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
try to flash stock boot.img and recovery.img

sonn3 said:
try to flash stock boot.img and recovery.img
Click to expand...
Click to collapse
Same issue. So how would we go about flashing properly?

Search for recovery.img and boot.img in stock rom and flash in fastboot mode.

mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
Did you select close avb 2.0 in twrp and factory reset?

mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
We would need further details on which device (region) which MIUI version (number, android, region) you were on when you attempted to install Magisk. Of course we assume here you had unlocked your bootloader first, otherwise any attempt to flash anything will result in bootloop.
Many have successfully rooted on Android 9 regardless of MIUI version.
Complication often comes with Chineses devices from what I read, Global not so much so if you are on Global device consider yourself lucky
Easiest root is probably to flash LR team TWRP If you can still access fastboot mode (voloume - + power) version 09.24 or 11.04 if you are on Android 9 or version 12.10 if you are on Android 10. Note that you probably have more chances of success being on Android 9.
And use the root feature from WITHIN that TWRP to install root on your device.
You have a complete guide of the steps to reproduce here:
Guide
I have tested on Android 9, EEA device, EEA rom MIUI 11.0.2.0 and it works without an issue if you follow the guide provided above.
If you still want to manually flash Magisk from any other recovery, make sure to use version 19.04 which seems to have the higher odds of success (update afterward from Manager).
Also as mentioned by @wang1chung do not forget to close avb 2.0.
Myself I also had RM Force encrypt option used (just in case) even if not mentionned in the thread.
But unlike what was suggested in those threads I did not wipe data.
That said since I do not want to have TWRP to stick for now, I actually want it to automatically be replaced by stock recovery all went fine for me, and Magisk is there.
And when I need TWRP for something I just flash it again and do my stuff.
Hope this helps.
Good luck!

Same problem here. Luckly fastboot was still working (vol down + power after Redmi logo gets off). Then, I've downloaded stock ROM, and tryied manually execute fastboot commands, without success. Then, I've found a .bat file inside the root folder of the stock ROM .tar.gz archive, then executed the .bat file. Phone is working back. So, whats the catch about install Magisk? Any tips?

allxdadev said:
Same problem here. Luckly fastboot was still working (vol down + power after Redmi logo gets off). Then, I've downloaded stock ROM, and tryied manually execute fastboot commands, without success. Then, I've found a .bat file inside the root folder of the stock ROM .tar.gz archive, then executed the .bat file. Phone is working back. So, whats the catch about install Magisk? Any tips?
Click to expand...
Click to collapse
Personally I used the hassle-free method pressing the button to root directly from within the LR-TWRP (09.24, or 11.04 on Android 9 MIUI), swiped, then pressed that other provided button to close AVB 2.0, swiped and it worked on first attempt.
Of course TWRP got replaced on first reboot by system recovery, but I dont care as I do not want it to stick on my device. I just flash it again when I need it.
Magisk stayed, updated it from Manager (well manager updated first to that new ugly theme.... yurk!), then Magisk updated, no problem.
Note that I am on EU Phone running EEA MIUI 11.0.2.0. You might get a different outcome with other devices/roms.
Side note, LR-TWRP 09.24 installs Magisk 19.04 which has been reported numerous time to work on most Android 9 MIUI regional versions. LR-TWRP 11.04 howevers installs Magisk 20.0 fyi.
Hope this helps,
Regards,

regarding the thread title, i had the same problem. right when i was about to retart everything all over from 0, i was glad i was able to just go into twrp and just unroot. rebooted and it started as if nothing hsppended. now i jjust gotta find which module made me bootloop.

try this n give us the result