I got a problem with that CWM on L7. After using "flash_bootloader.bat" phone restarts but gets stuck on battery logo. Any solutions?
I've got the same issues whit the stock rom, I don't know why but if I try to reboot or simply boot my phone when it's connected via USB to pc or in charge it boot in ''charging mode'' instead of booting android.
If you can boot it when it's non connected to the cable everything is fine, don't worry, proceed with flashing cwm.
Related
hi all
I rooted my lg g2 , and then installed twrp. I downloaded my custom rom to the phones memory, I installed the rom threw twrp and said successfully done so I restarted the phone and it booted with lg logo then this
[800] fastboot mode started
[850] udc_start()
I can get into twrp recovery and also can get into the lg software tpo flash stock rom but sticks at 49% and states try again done all this for past 5 hrs and nothing ,
computer picks up phone when on txt screen when usb plugged in but I don't know what to do.
Which carrier phone are you using?
I tried to flash CM11 on my VS980, but I just got stuck in LG logo bootloop. I managed to factory reset and get into CWM, but my PC refuses to recognize it as an adb device, and I can't mount USB OTG with CWM for some reason. I've tried various uninstalls/reinstalls of the drivers to no avail. What's my next step?
Hi guys
I have a big problem with my note 3 hlte that i have never heard off... I run cyanogenmod 12 and i noticed when i flashed it that cwm recovery went back to stock recovery so i used app called Flashify and i "flashed" cwm that flashfy offerd me.
Afther that it offerd me to reboot into recovery witch i selected and now my phone is stuck in recovery boot loop....
It doesnt want to boot into recovery and i cant boot it normaly or download mode because its stuck in loop..
i tried removeing battery, draining power, leaving it for some time but every time when i return the battery and try to turn it on, its stuck..
very hard to explain, if you want i can record and upload it
(i would usualy flash a cwm via odin but i was to lazy to turn on my pc )
sorry for some gramatical mistakes
found solution
Volume down + home and pluging in usb automaticly boots into download mode
Find the correct cwn/twrp for your phone model & bootloader(4.3/4.4). Flash with odin.
The recovery corrupted, no big deal.
Sent from my SM-N9005
I Tried To Flash Twrp On My Grand 2 And Rebooted The Device And Its Stuck On Boot Loop, From Then On When I Placed The battery The Phone Automatically Switches On and then Starts To Reboot. I Tried To Get Into Download Mode But It Shows Up For A Second And Then Reboots , The Same Happened Everytime When I Tried To Boot Into Recovery And Download Mode. Please Help Me Guys I Cant Use My Phone Since 20/2/17. Pls Hlp !!!!!!
I think your device is bricked
Is your phone pluged-in to your comp when you got into bootloader ? Also try reinstall drivers for samsung & odin.
hi,
i have an old S4 which I wanted to update to new LineageOS. First I tried to flash TWRP by JCDteam, but I got error, and now recovery does not boot - it simply restarts the phone. The problem is, that the USB port is dead on the phone (shows Device has malfuncationed when connecting to PC), so I cannot use Odin to flash new recovery. Is there any way to flash TWRP to Recovery partition from the phone itself (it boots and works fine and has root)?
Try to use genuine cable first not some Chinese fake things.
Plenty of apps available to flash recovery, try to install twrp app
I think I've bricked. it. I've tried to do dd from terminal but when I rebooted, the recovery still doesn't boot (starts booting then reboots), the phone doesn't boot anymore (stuck on LineageOS logo), and if I boot to download mode and connect usb cable (and i've tried tons of them) it just says unknown device
Anything else I can do?
mrQQ said:
Anything else I can do?
Click to expand...
Click to collapse
Replace the USB port so you can flash a system image through Ofin. If I recall correctly the port is on its own board, so if replacing the port isn't feasible, replacing the board the port is on with one from a different S4 should work. Of course only you can determine whether doing so is worth the time and energy.