Hi can u help me please, I'm trying to put my mojo in recovery mode, I download a quick reboot app and installed it, my mojo turns off and I get the android with the red exclamation mark above it then it boots back to original screen, I'm using a controller as don't have a keyboard, what am I doing wrong??
Markbeale1974 said:
Hi can u help me please, I'm trying to put my mojo in recovery mode, I download a quick reboot app and installed it, my mojo turns off and I get the android with the red exclamation mark above it then it boots back to original screen, I'm using a controller as don't have a keyboard, what am I doing wrong??
Click to expand...
Click to collapse
Forgive the question, but is your MOJO rooted? I believe the method you're using should work if you're rooted. (Someone please correct me if I'm missing something.)
Sent from my C6730 using Tapatalk
Hi I believe so, I followed towel root, how else can I tell if it's rooted?
Markbeale1974 said:
Hi I believe so, I followed towel root, how else can I tell if it's rooted?
Click to expand...
Click to collapse
If you haven't already, you can get SuperSU from the Play store and I believe it should tell you if you're not rooted (you'll likely need it anyway if you are rooted). You can also get a root checker app from the play store, or if you have an app that has root functions (like es explorer), you can open it and try to enable them.
Sent from my C6730 using Tapatalk
Ok cool so when I try to put it in recovery mode and I see the exclamation mark above the android what do I do then or should it automatically go in recovery mode?
I'm struggling
Sent from my iPhone using Tapatalk
Sorry about forgetting this earlier, but I should have remembered if you're using quick reboot successfully, then that pretty much would mean you're rooted.
Markbeale1974 said:
Ok cool so when I try to put it in recovery mode and I see the exclamation mark above the android what do I do then or should it automatically go in recovery mode?
Click to expand...
Click to collapse
So it looks like the red triangle is the stock recovery. http://forum.xda-developers.com/showpost.php?p=39315483&postcount=5
Sorry, but I never keep stock recovery, so I guess that's why I didn't notice.
So you're probably going to want to flash TWRP recovery so you can actually take advantage of your modded MOJO. Flashify is the easiest method to do this without a computer. You can also backup your stock recovery with Flashify so you can return you're MOJO to it's original state at some point.
Here's where you can find TWRP recovery:
http://forum.xda-developers.com/mad...overy-twrp-2-8-2-0-recovery-mad-catz-t2973640
Just download the zip file to your MOJO, backup your original recovery in Flashify, then flash TWRP recovery with Flashify. You should then be able to boot into recovery. The towelroot/Flashify method is what I used, so I expect it to work fine for you.
Even if something goes south, the MOJO is a great device to screw around and learn about root stuff as you can't really brick it. You're always just a male to male USB plug away from fastboot resurrection.
Sent from my C6730 using Tapatalk
Ok cool so if I go into stock recovery will it come back un rooted?
Sent from my iPhone using Tapatalk
Markbeale1974 said:
Ok cool so if I go into stock recovery will it come back un rooted?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
It shouldn't. The only thing I can think of that would make your MOJO lose root is if you flash one of unjustified's roms (other than cyanogenmod) without flashing the SuperSU zip immediately after.
Sent from my C6730 using Tapatalk
Ok so last night I flashed twrp I think and still got the red exclamation mark
Sent from my iPhone using Tapatalk
Maybe I have not got it rooted then
Sent from my iPhone using Tapatalk
I downloaded twrp last night but when I clicked on it it said cannot open
Sent from my iPhone using Tapatalk
As u can see, I'm useless lol
Sent from my iPhone using Tapatalk
Markbeale1974 said:
I downloaded twrp last night but when I clicked on it it said cannot open
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Hmm, I seem to remember that happening to me once, and then when I opened Flashify before clicking on the TWRP zip, it worked. Have you opened Flashify, and if so, did a SuperSU permissions request popup?
Sent from my C6730 using Tapatalk
Ok so it all worked, I install cyanmod but didn't like it, now I can't get rid of it, I can't root now either, I'm in a right state
Sent from my iPhone using Tapatalk
Markbeale1974 said:
Ok so it all worked, I install cyanmod but didn't like it, now I can't get rid of it, I can't root now either, I'm in a right state
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
In that case, you should be able to enable root in the CyanogenMod settings under developer options as stated here:
http://forum.xda-developers.com/showpost.php?p=63238624&postcount=273
And then you can flash the stock MOJO rom found here:
http://forum.xda-developers.com/mad-catz-mojo/general/stock-rom-mojo-please-help-t3040895
Alternatively, if you previously made a backup of your stock MOJO rom in TWRP, then you can flash that instead.
Your a genius thanks
Sent from my iPhone using Tapatalk
Markbeale1974 said:
Your a genius thanks
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Glad to help.
Related
When I saw the port for ICS come out I got really excited and flashed it right away. Then I realized for whatever reason I didnt have SU permissions so I couldn't tether to my computer. I was disappointed but I thought, "no biggie, I'll just restore from my back up." When I flashed my back up the SU app was in my app drawer but I still couldn't tether. As a matter of fact I can't do anything that requires SU but the bootloader still reads unlocked. WTF?
I can't flash a new recovery either. I tried installing from ROM manager, I tried pushing it from my computer but I can't get to the recovery any more. ROM manager says that I have CWM 5.0.2.0 currently installed but I can't get to it at all. Again, WTF?
Sent from my Nexus S 4G using XDA App
^clearly the phone is working perfectly fine with the stock ROM from the back up but obviously I want my SU back.
Root your phone and read the development thread versus making blog posts.
Sent from my Nexus S 4G using xda premium
Flash this http://www.tylerwatt12.com/XDA/ics/root_and_theme.zip and please post in right section
Sent from my Nexus S 4G using xda premium
Thanks for not answering my questions. The bootloader is unlocked but I don't have root and I don't have access to recovery mode even tho ROM Manager says I have Clockwork Mod 5.0.2.0 currently installed. I cannot access the recovery mode AT ALL. I cannot flash or push a new recovery but it fully boots into Gingerbread w/o any issues. What is wrong with my phone and how do I fix it.
Sent from my Nexus S 4G using XDA App
Try from rom manager to reinstall a previous recovery version.
Sent from my LG-P920 using XDA App
That doesn't work either. It goes through the prompts but it doesn't actually reboot do the installation.
I just tried unrooting and then re - rooting but that didn't work and I think that actually wiped my phone completely. I don't even know where an SD card would get into this thing.
Sent from my Nexus S 4G using XDA App
Use adb on your computer and push a clockworkmod recovery.img. And we are trying to help u no need for the sarcasm
Sent from my Xoom using xda premium
I'm sorry but I'm just really frustrated right now. Nothing I have tried has worked. Maybe its my commands? To push that recovery image what would I type?
Sent from my Nexus S 4G using XDA App
I also I can't download that zip you linked to. Every time I try it just says failed.
Sent from my Nexus S 4G using XDA App
obsydian2k7 said:
I'm sorry but I'm just really frustrated right now. Nothing I have tried has worked. Maybe its my commands? To push that recovery image what would I type?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
I get it
Fastboot flash recovery recovery-xxxxxxxxx.img and hit enter
Sent from my Xoom using xda premium
Esteway.619 said:
I get it
Fastboot flash recovery recovery-xxxxxxxxx.img and hit enter
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Get cwm image from here CWM Recovery
Sent from my Xoom using xda premium
relock the phone then unlock it again i had the same problem
I tried relocking and unlocking again then pushed the recovery I just (finally) downloaded but it didn't work. Terminal says error cannot load 'recovery-clockwork-5.0.2.0-crespo4g.img'
Sent from my Nexus S 4G using XDA App
obsydian2k7 said:
I tried relocking and unlocking again then pushed the recovery I just (finally) downloaded but it didn't work. Terminal says error cannot load 'recovery-clockwork-5.0.2.0-crespo4g.img'
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Is that the right name of the recovery img? Try renaming it to just recovery and see if that works.
Edit: make sure your phone is in debugging mode. And uninstall then reinstall the drivers on your computer
Sent from my Nexus S 4G using xda premium
Esteway.619 said:
Is that the right name of the recovery img? Try renaming it to just recovery and see if that works.
Edit: make sure your phone is in debugging mode. And uninstall then reinstall the drivers on your computer
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
manually go into recovery with volume down and power flash the su.zip and u should be good to go that wat I did
Sent from my Nexus S 4G using xda premium
No suggestions have worked so far. It does not matter what the recovery image name is, whenever I try the flash it Terminal says that it cannot load "***.img" or if I try an install command it says that it cannot find "***.zip" I'm on a snow leopard iMac so I don't need drivers n such.
Let me pose the question like this, what would I do to completely restore the phone to factory condition and try to root it again? Like I said before, the bootloader says that it is unlocked but I do not have any root privileges, could not access the recovery I had before nor install a new recovery after having locked the unlocked the phone's bootloader again.
Sent from my Nexus S 4G using XDA App
http://forum.xda-developers.com/showpost.php?p=13773677&postcount=1
go to the link above and follow the directions for returning to stock.
find yourself a one-click root method on XDA that includes superuser, busybox, and CWM.
EDIT: Also, double check the md5 sum for the CWM .zip. use
Code:
md5 recovery-aaaaaa.img
in the terminal and make sure the output matches whatever is given on the CWM site. if they dont have one up, ask for it
NS4g one-click root app:
http://www.mediafire.com/?2jx8xtx2602hi23
this will:
unlock the bootloader
install cwm 5.0.2.0
root
No commands, no messing with pushing files manually, etc. This thing has already saved me from major headaches while restoring my phone once and I've only had it for 3 weeks lol
hp420 said:
NS4g one-click root app:
http://www.mediafire.com/?2jx8xtx2602hi23
this will:
unlock the bootloader
install cwm 5.0.2.0
root
No commands, no messing with pushing files manually, etc. This thing has already saved me from major headaches while restoring my phone once and I've only had it for 3 weeks lol
Click to expand...
Click to collapse
im assuming this is for windows. he said he has a mac so that wouldnt work for him. here this is for mac http://forum.xda-developers.com/showthread.php?t=1129759 just copy and past everything thats there in terminal
Esteway.619 said:
im assuming this is for windows. he said he has a mac so that wouldnt work for him. here this is for mac http://forum.xda-developers.com/showthread.php?t=1129759 just copy and past everything thats there in terminal
Click to expand...
Click to collapse
I missed that...my mistake
I just sideloaded the 4.2.2 update and now my recovery mode shows the red triangle error. I can still boot into Android fine and what have you, but TWRP is gone. I tried to factory rest the device in the error screen, but that didn't fix it. Again I can still boot fine, but TWRP is replaced with the red triangle. Any ideas how to fix it? Thanks!
Koopa777 said:
I just sideloaded the 4.2.2 update and now my recovery mode shows the red triangle error. I can still boot into Android fine and what have you, but TWRP is gone. I tried to factory rest the device in the error screen, but that didn't fix it. Again I can still boot fine, but TWRP is replaced with the red triangle. Any ideas how to fix it? Thanks!
Click to expand...
Click to collapse
Assuming you're rooted...? Download and install goomanager from the Play store. Open it and tap the menu button (three dots at upper right) and select Install Open Recovery script. It will prompt for confirmation and then download and install TWRP for you.
... beamed from my Nexus 10 to your planet
Koopa777 said:
I just sideloaded the 4.2.2 update and now my recovery mode shows the red triangle error. I can still boot into Android fine and what have you, but TWRP is gone. I tried to factory rest the device in the error screen, but that didn't fix it. Again I can still boot fine, but TWRP is replaced with the red triangle. Any ideas how to fix it? Thanks!
Click to expand...
Click to collapse
Use fastboot flash recovery openrecovery-twrp-x.x.x.x-manta.img to get TWRP back?
Wow I completely forgot about this. Exams happened and then I forgot to reply. I was a moron and was trying to flash the Toshiba Thrive TWRP(2.4.1.3) not reading that it was for the Thrive. Flashed 2.4.1.0 manta and it took no problem. Thanks anyhow! I'm going to leave this topic in case anyone else is as dumb as I am(I sure hope not ) so they don't freak out over TWRP disappearing.
Wow your fortunate you didn't do something worse lol. Becareful if you ever use fastboot, a few wrong commands and your fubard
Sent from my Nexus 10 using Tapatalk HD
altimax98 said:
Wow your fortunate you didn't do something worse lol. Becareful if you ever use fastboot, a few wrong commands and your fubard
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
A few wrong commands? Huh no, only if you flash the wrong files...
Sent from my Nexus
Try fastboot erase bootloader and don't follow up with your write command... the show will end real quick
Sent from my Nexus 10 using Tapatalk HD
altimax98 said:
Try fastboot erase bootloader and don't follow up with your write command... the show will end real quick
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Maybe on this Nexus... On Galaxy Nexus you still got OMAPflash.
Sent from my Nexus
bk201doesntexist said:
Maybe on this Nexus... On Galaxy Nexus you still got OMAPflash.
Sent from my Nexus
Click to expand...
Click to collapse
I've never personally done it, but I've heard alot of people having issues with omap flash and the partition tables
Sent from my Nexus 10 using Tapatalk HD
This is extremely frustrating.
I successfully rooted my galaxy s4.
I then downloaded CMW and touch, and downloaded this rom: http://forum.xda-developers.com/showthread.php?t=2341376
I then booted into recovery, and wiped etc and then installed the rom. I read on the later part of that page that there wasn't a need for loki so I did not download loki.
I then rebooted, and got the yellow triangle sign saying that the software is not approved by ATT.
This is where I am stuck. I have a mac and am running vmware windows 8.
I tried downloading kies on the mac, and it does not recognize the phone. I did not try kies for windows yet, nor do I know what to do after if I am able to get kies to recognize the s4.
I also downloaded odin, and the firmware, but odin is not recognizing the phone under windows even when I select to use the phone under windows.
I tried the stock usb cable, and a different usb cable, and 2 different usb ports. I do not have a regular windows computer. Is there a way to do this with a mac?
Guess I should have downloaded the loki, is not downloading the loki the whole reason this is happening?
I appreciate everyones help! I just wanted stock android! :good:
I do not have a s4 but have a s2 but its like the same.
1. Why would you not already have Odin installed and kies?! Just in case
2. No backup made?...
3. Can you still get into recovery and download mode if so then you have hope.. wait for someone to give you steps to get out of this
4. If you can't get into either... well :banghead:
Sent from my SPH-D710 using Tapatalk 2
XxlemonxX said:
I do not have a s4 but have a s2 but its like the same.
1. Why would you not already have Odin installed and kies?! Just in case
2. No backup made?...
3. Can you still get into recovery and download mode if so then you have hope.. wait for someone to give you steps to get out of this
4. If you can't get into either... well :banghead:
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Thanks,
1. I have odin and kies installed, they are just not recognizing the phone.
2. I made a backup using titanium backup but not really sure how it works... I've never restored from a backup using titanium
3.Yes I am able to get into download mode by holding the volume, home and power key...
drew1204 said:
Thanks,
1. I have odin and kies installed, they are just not recognizing the phone.
2. I made a backup using titanium backup but not really sure how it works... I've never restored from a backup using titanium
3.Yes I am able to get into download mode by holding the volume, home and power key...
Click to expand...
Click to collapse
Mmm alright... Go into download mode and take out your SD card and download the Loki file in the ROM thread then transfer to sdcard on PC. Then place back in phone.. Then go intro recovery and flash the file and it should work.
But wait before anything can you get into recovery? If so then you go to mounts and storage and mount sdcard and transfer the Loki file from your PC right there.
Sent from my SPH-D710 using Tapatalk 2
I have installed kies on the windows version and it notices the phone is connected, but it just keeps saying "connecting..." and a little thing spinning. Not sure how long it should take to connect...
why not download the loki zip to sd card, then put back on phone, reboot to recovery and install from sd card...
XxlemonxX said:
Mmm alright... Go into download mode and take out your SD card and download the Loki file in the ROM thread then transfer to sdcard on PC. Then place back in phone.. Then go intro recovery and flash the file and it should work.
But wait before anything can you get into recovery? If so then you go to mounts and storage and mount sdcard and transfer the Loki file from your PC right there.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Yes I can boot into recovery.
Wow I didn't even think of that... Sorry I am a noob.
Okay I fixed it (you fixed it thank you so much!) I booted into recovery, and then into the zip file and installed loki, and all is well.
STOCK ANDROID!!! Whew that was scary...
drew1204 said:
Yes I can boot into recovery.
Wow I didn't even think of that... Sorry I am a noob.
Okay I fixed it (you fixed it thank you so much!) I booted into recovery, and then into the zip file and installed loki, and all is well.
STOCK ANDROID!!! Whew that was scary...
Click to expand...
Click to collapse
Welcome
Sent from my SPH-D710 using Tapatalk 2
XxlemonxX said:
Welcome
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Because noobs don't get it.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
Because noobs don't get it.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Cool
drew1204 said:
Cool
Click to expand...
Click to collapse
You could thank him for helping you. Or is that too hard for you? There's even a thanks button to make it easy
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
You could thank him for helping you. Or is that too hard for you? There's even a thanks button to make it easy
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Mate don't be so arrogant, he did thank him.
Sent from my GT-I9305 using xda premium
ozgame said:
Mate don't be so arrogant, he did thank him.
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Mate,I don't see that
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
drew1204 said:
Yes I can boot into recovery.
Wow I didn't even think of that... Sorry I am a noob.
Okay I fixed it (you fixed it thank you so much!) I booted into recovery, and then into the zip file and installed loki, and all is well.
STOCK ANDROID!!! Whew that was scary...
Click to expand...
Click to collapse
the OP of that ROM lists these specific installation instructions:
HOW TO INSTALL:
* Download the ROM (NO NEED FOR GAPPS)
* Reboot to Recovery
* Wipe data/factory reset
* Flash the ROM
* U.S. MODELS - Flash Loki Patch - http://tau.shadowchild.nl/files/loki-doki.zip (CANADIAN USERS DO NOT INSTALL)
* Reboot your Galaxy S4
* Enjoy
remember to read everything first and understand what you are doing before proceeding. cheers
And only 5 simple steps. One sec of reading. And it matters. Or kaboom.
Let me start off by saying I apologize if this is posted somewhere already.
Here's my situation. A couple days ago I lgflashed back to stock. All went well. I then rooted and installed TWRP. No issues at all. I didn't take an update, modify the stock ROM or even flash another ROM. Just ran stock rooted. Today, I pick my phone up, go to turn it on and I'm in recovery. No big deal, right? Well I can't get out of TWRP. My backups are still showing, but when I restore it and reboot the phone I'm right back in recovery.
I can't get into download mode either. Not sure what happened and everything was fine earlier in the day. Any thoughts?
Sent from my Nexus 5 using Tapatalk
I should also say that adb doesn't recognize my phone.
Sent from my Nexus 5 using Tapatalk
droidiac13 said:
I should also say that adb doesn't recognize my phone.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm in your same boat right now, working on a buddy's phone cept when i formatted phone to stick a rom on it the nandroid i made got file 13'd
dcillusions77 said:
I'm in your same boat right now, working on a buddy's phone cept when i formatted phone to stick a rom on it the nandroid i made got file 13'd
Click to expand...
Click to collapse
I'm back up and running. I used this thread HERE and did the command through TWRP.
As long as you have a ROM on the phone, you should be good to go.
droidiac13 said:
I'm back up and running. I used this thread HERE and did the command through TWRP.
As long as you have a ROM on the phone, you should be good to go.
Click to expand...
Click to collapse
Tried it but it didn't work :\.....
Mine is stuck in fastboot mode whenever I try to reboot it into recovery what files are missing? Anyone know why whenever I reboot it into recovery it boots fastboot instead? Any help would be much appreciated
If you stuck in fastboot mode. Just push
laf file through fastboot to your phone.
Sent from my LG-F320L using xda app-developers app
droidiac13 said:
I'm back up and running. I used this thread HERE and did the command through TWRP.
As long as you have a ROM on the phone, you should be good to go.
Click to expand...
Click to collapse
I'm so glad your back up and running again. I've been following your thread. And thanks for sharing the fix.
Does that mean that without your knowledge, your phone may have probably automatically updated itself (OTA) when you left your phone overnight? That's why you were stucked in recovery? Because it seems so odd that you didn't do anything wrong and it suddenly behaved that way. And I have read somewhere here that OTA just installed itself automatically without user intervention. So confusing if that did happen. How is that even possible?
Sent from my LG-D802 using Tapatalk
cccho said:
If you stuck in fastboot mode. Just push
laf file through fastboot to your phone.
Sent from my LG-F320L using xda app-developers app
Click to expand...
Click to collapse
Got it up and running by downloading the FreeGee app from play store and installing TWRp that way. I had tried it before just didnt stick the first time
mrm43 said:
I'm so glad your back up and running again. I've been following your thread. And thanks for sharing the fix.
Does that mean that without your knowledge, your phone may have probably automatically updated itself (OTA) when you left your phone overnight? That's why you were stucked in recovery? Because it seems so odd that you didn't do anything wrong and it suddenly behaved that way. And I have read somewhere here that OTA just installed itself automatically without user intervention. So confusing if that did happen. How is that even possible?
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
I can only guess that it updated by itself. I really don't know what else it could be.
Sent from my LG-D800 using Tapatalk
droidiac13 said:
I can only guess that it updated by itself. I really don't know what else it could be.
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Yes it might seem that way. Thanks
Sent from my LG-D802 using Tapatalk
Not sure exactly what I did but I had installed a stock rom and while using the rom I got a software update. I tried to install the update and it said phone will reboot so I rebooted it. It took me to my recovery (Philz Touch recovery) then I attempted to reboot my phone but now it just keeps going back to recovery and wont go any further. I've tried to install another rom but it still goes right back to recovery after I reboot. Please someone help me out here. I'm pretty I'm not bricked but cant figure out what to do to get to my phone. I'm thinking I need to restore my phone back to factory and start again.
corybucher said:
Not sure exactly what I did but I had installed a stock rom and while using the rom I got a software update. I tried to install the update and it said phone will reboot so I rebooted it. It took me to my recovery (Philz Touch recovery) then I attempted to reboot my phone but now it just keeps going back to recovery and wont go any further. I've tried to install another rom but it still goes right back to recovery after I reboot. Please someone help me out here. I'm pretty I'm not bricked but cant figure out what to do to get to my phone. I'm thinking I need to restore my phone back to factory and start again.
Click to expand...
Click to collapse
Hello, if you made a backup of your previous Rom, you don't have to do a factory reset, if you didn't make a backup in recovery mode, you can factory reset.[emoji4][emoji4]
Sent from my LG-LS980 using Tapatalk
TechGirl90 said:
Hello, if you made a backup of your previous Rom, you don't have to do a factory reset, if you didn't make a backup in recovery mode, you can factory reset.[emoji4][emoji4]
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
Tried that as well but it still goes back to recovery
corybucher said:
Tried that as well but it still goes back to recovery
Click to expand...
Click to collapse
What's your phone variant?
Sent from my LG-LS980 using Tapatalk
TechGirl90 said:
What's your phone variant?
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
AT&T D800
corybucher said:
AT&T D800
Click to expand...
Click to collapse
Try this[emoji4]
http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/
READ THE INSTRUCTIONS VERY CAREFULLY
Sent from my LG-LS980 using Tapatalk
TechGirl90 said:
Try this[emoji4]
http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/
READ THE INSTRUCTIONS VERY CAREFULLY
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
Cant go to DL mode so this wont work. I can only go to recovery and nothing else.
I think you need to do this
http://forum.xda-developers.com/showthread.php?t=2451696
Sent from my LG-D802 using Tapatalk
Rule #1. NEVER INSTALL OTA UPDATES IF YOURE ROOTED!
Just saw your other thread. If you are not confident using adb just get yourself an otg cable, put twrp on a memory stick, mount the otg in philz and flash twrp from the memory stick. You can then use the terminal in twrp.
PS. A micro usb drive would work just as well.
Sent from my LG-D802 using Tapatalk