Alright I installed CHAINFIRE 3D which resulted in a BOOT LOOP. My android is a LG G3 it has stock OS and it is rooted. For some reason I can't boot to recovery and I don't have a CUSTOM RECOVERY, I tried to get one but It wouldn't reboot to recovery and to use it I had to redownload it as a update and open it when its done. I am aware of applications such as ONECLICKROOT but my android will not pop up on my MAC and I do not know if this is a result of driver issues or because I did not turn on usb debugging. I also have a 64 GB micro sd card if thats any help and I also do not have any experience with boot loader. SO CAN SOMEONE PLEASE HELP ME!!!!!!!!
Related
I'm new to rooting and all of this type of thing, i figured I would first start with my HTC Flyer. I successfully unlocked the bootloader, and installed SuperUser, upon installing greenify and i tried to install the Xposed Framework, and my device now is stuck in a boot loop.
When enter the bootloader and do a factory reset or try to enter factory it completely freezes, and when i try to connect it to my PC via fastboot the PC says that the USB device that is connected cannot be recognized and fastboot will not work. Did i completely fry this device? Also if you have time I couldnt figure out a proper way to flash a custom rom so if anyone has a guide for that I would appreciate a link to that as well.
Thank you so much!!
AH **** I REALLY MESSED UP! I unlocked my bootloader then later on I wanted to try out a different version of CM so I went ahead and booted into my CWM touch and I never did replace that v6.bin yet so my touch screen is wonky still. I installed CM 10.2 by BobZhome and now I can't get back into CWM to cat the v6.bin file to fix the touch screen. I also don't have any gapps installed and when I plug in my phone to my computer it won't let me transfer files to the phone memory storage. I also don't have a SD card now because I lost it. I was able to use the fastboot trick to flash the cwm recovery but it still won't let me back into recovery.. I think because the internal memory is blank because of me installing cm 10.2.. I also tried enabling usb debugging mode on the phone with cm 10.2 so I could try to adb and get a shell but it won't work it keeps saying the device is offline... WHAT SHOULD I DO SOMEONE PLEASE HALP ME!!!
CygnusBlack said:
AH **** I REALLY MESSED UP! I unlocked my bootloader then later on I wanted to try out a different version of CM so I went ahead and booted into my CWM touch and I never did replace that v6.bin yet so my touch screen is wonky still. I installed CM 10.2 by BobZhome and now I can't get back into CWM to cat the v6.bin file to fix the touch screen. I also don't have any gapps installed and when I plug in my phone to my computer it won't let me transfer files to the phone memory storage. I also don't have a SD card now because I lost it. I was able to use the fastboot trick to flash the cwm recovery but it still won't let me back into recovery.. I think because the internal memory is blank because of me installing cm 10.2.. I also tried enabling usb debugging mode on the phone with cm 10.2 so I could try to adb and get a shell but it won't work it keeps saying the device is offline... WHAT SHOULD I DO SOMEONE PLEASE HALP ME!!!
Click to expand...
Click to collapse
I had never succeded in unlocking my P768, but everytime i messed up this bad with the phone, the only way to fix it was by reinstalling the software with LG Tool. I don't know if this "locks" the bootloader again, it shoudn't but at least you will have a phone by doing this. Not even adb is accessible in your case, complicated..
My advice is reflash stock rom via LGTool, then you install CM/CWM againwith the screen fixed
back at it again
Ok I just got off work again and I was messing around with it again. I am able to reboot into the touch recovery from CM 10.2 because I was able to enable the developer options and then enable reboot into recovery option from reboot menu. I tried enabling debugging mode but the computer will not recognize the device at all. I use to be able to use adb from CWM Recovery by changing the driver to adb in the device manager however now my device manager is not even showing adb as an option to install now! LOL! I was trying to use the terminal emulator in CM 10.2 but it's ****ing impossible to use with that wonky touch screen. I wrote a shell script and uploaded it to a SD card I got today and then I ran the terminal emulator and managed to do the su command and then I did cd into the external sd card and I tried to bash the script by doing ./a.sh
cat v6.bin > ../../../../../../sys/devices/virtual/input/lge_touch/firmware
then it told me permission denied even though I was SU! LMFAO!!!!!
I'm at my wits ****ing end with this thing I mean HOLY ****! I just can't be bothered with it anymore. I think I'll take it outside later and smash it to pieces.
unless someone knows of anything I can do?! Please don't say to restore original rom because for some reason the computer just won't recognize this ****ing thing.. even in S/W upgrade mode it doesn't install the driver!
CygnusBlack said:
Ok I just got off work again and I was messing around with it again. I am able to reboot into the touch recovery from CM 10.2 because I was able to enable the developer options and then enable reboot into recovery option from reboot menu. I tried enabling debugging mode but the computer will not recognize the device at all. I use to be able to use adb from CWM Recovery by changing the driver to adb in the device manager however now my device manager is not even showing adb as an option to install now! LOL! I was trying to use the terminal emulator in CM 10.2 but it's ****ing impossible to use with that wonky touch screen. I wrote a shell script and uploaded it to a SD card I got today and then I ran the terminal emulator and managed to do the su command and then I did cd into the external sd card and I tried to bash the script by doing ./a.sh
cat v6.bin > ../../../../../../sys/devices/virtual/input/lge_touch/firmware
then it told me permission denied even though I was SU! LMFAO!!!!!
I'm at my wits ****ing end with this thing I mean HOLY ****! I just can't be bothered with it anymore. I think I'll take it outside later and smash it to pieces.
unless someone knows of anything I can do?! Please don't say to restore original rom because for some reason the computer just won't recognize this ****ing thing.. even in S/W upgrade mode it doesn't install the driver!
Click to expand...
Click to collapse
cant you fastboot recovery and do it that way?
Cobra11Murderer said:
cant you fastboot recovery and do it that way?
Click to expand...
Click to collapse
I already used the fastboot trick to flash recovery. I flashed the CWM touch.img then in cyanogenmod i can make it reboot into cwm recovery. But the thing is now my computer will not recognize the drivers for this device so I can't get adb to work with it. ADB will also not work in cyanogenmod for me because of the drivers not being recognized. ADB doesn't even show up in my device manager in windows when I tried to force it to be recognized as an adb interface. Now I think I need adb to work in CWM recovery because that's the only way I can cat the v6.bin file to fix the wonky touch screen. I can't use the terminal emulator to cat the bin file while within cyanogenmod because it's being used while in cyanogenmod that's why I got a permission denied result when I tried to run the command.
I also don't have a backup of my rom or I would have already restored backup from cwm to get the computer to recognize the drivers and then I would have reinstalled the original rom/firmware with lg flash tool.
It won't even let me restore the rom/firmware while in S/W upgrade mode because the lg tool won't recognize the device!
The only way I see out of this now is to get someone here to make me a CWM backup of their europe open rom so then I can download your backup put it on my sd card and restore it from there.. then drivers will recognize and I can flash back to stock rom with lg tool then reroot, rerecovery install and then install cyanogenmod 11 kitkat.
So if someone could do that for me I would be eternally grateful.
FIXED IT!!!
Nevermind. I was able to find a flashable zip that fixes the touch screen issue. Thank God I found that and was able to get a new SD Card otherwise I wouldn't have been able to flash that touch screen fix from the CWM Recovery! Woo! Now I can complete my other guide so no one else comes across these problems!
i recently rooted it and made 4 back ups. I deleted two of them and tried to roboot to fastboot. but it says 'No OS installed" . My computers reconize it as a disk drive and when i click on it, it asks me to insert a disk...
HTC One m8 with AT&T.
I am S-On, and I don't know to turn it off.
I have TWRP as my current recovery. I can boot into recovered successfully.
I do not have a SD card.
I have a laptop, a cable, and the phone, but the laptop does not recognize the phone.
TWRP is version 2.7.0.2.
I'd like to get the SkyDragon ROM as well... But it seems I need some help. Since I seem to be having trouble, I think a working ROM should take priority.
What should I do? Please and thank you.
flash the boot.img of the custom OS via fastboot with fastboot "Fastboot flash boot bootname.img"
I was running CM12 and everything was fine. I received a notification to update to CM 13 and I selected yes. It installed OK, but no GAPPS. I tried everything I could think of to install GAPPS, and kept getting errors. IN my frustrated efforts, something happened to my TWRP and now I only have CM Recovery. I'm trying to reinstall TWRP but my phone is being recognized as a "Marshall London Bootloader Interface" ONLY when in the Fastboot and Recovery mode. I have Huawei Hisuite installed and it recognizes the phone fine when powered on, but as soon as I boot into Fastboot and Rescue mode, it reverts to the MLB interface. I am at my wits end as to how to get my PC to recognize my phone properly when in Fastboot and recovery. I did try removing and reinstalling drivers when in Fastboot, but the Marshall Interface keeps on getting inserted. Any suggestions?????? (I also seem to have erased the SD card that has my original system backup files on it. I tried to flash several downloaded stock ROMs using CM recovery, but they all error out. )
I was finally able to re load TWRP using the Huawei Hi Suite. I flashed Carbon ROM and GAPPS and everything seems to be OK but I still cannot use ADB because the phone is recognized by Windows as a Marshall device ONLY when in bootloader mode and ADB does not find the device. When I connect normally it is recognized as a Mate 2 and it connects normally to Hi Suite. I have no idea what could be wrong, but I have read of other people who have this mysterious "Marshall" device show only up when in bootloader mode. Anyone have any ideas????? Can I go back to stock from here if I don't have a saved recovery image to see if I can fix this???
I have no idea what Marshall device means. Is it possible to place the stock 5.1 ROM on a blank micro SD card and follow the flashing instructions? (boot to download mode or whatever it's called)
ScoobSTi said:
I have no idea what Marshall device means. Is it possible to place the stock 5.1 ROM on a blank micro SD card and follow the flashing instructions? (boot to download mode or whatever it's called)
Click to expand...
Click to collapse
I explained what "Marshall Device" is in the first post. I ended up going back to stock (322) and loosing root. I then updated to 5.1 using the SD card. Everything seems to be working OK. Maybe I'll root again and start over when I have more time.
Device:
Lenovo A916. (I don't think that matters for this isue though)
Issue:
Since the one and only firmware lenovo released was kitkat 4.4.1, i wanted to update to 5.1.
Rooted phone, managed to install TWRP, flashed to lollipop 5.1, so far so good. But had some problems with the custom ROM (no SIM detected), so i decided to download a stock ROM recovery and installed it.
When rebooted device i was stuck on CWM and custom rom installations give me errors and can't access USB storage on PC.
When i try to install a custom rom i get a no file_contexts warning and it fails.
Is there a way to fix this (maybe enter again to TWRP so i can flash a rom again? i don't know) or is my phone ruined forever? It was on USB debug mode, if that helps.
For some weird reason, it turns on by itself when connected via USB cable.
Any help would be greatly appreciated!