[Q] Help I botched It!!! - Kindle Fire General

Hi there i have a rotted kindle fire with burrito root.
I rooted it yesterday and everything was fine, then i turned it off and back on later it worked fine.
the next day it hangs on the boot logo (it is animated no triangle)
adb recognizes it yet i cant access adb root, remount etc Permission denied.
I cant install TWRP
What i wanted to do was go to the /sdcard directory and push the update.zip there. but i cant because it read-only. How do i change any of these? Ive read 6 other posts on possible fixes none of which work.

Have you tried pressing the power button for 20 seconds and then restarting it?

nope
Yes i did that does not help.
adb says it cannot be root in production builds. I looked up how to do it but its either vague or makes no sense or does not work. why is it a production buold? it didnt do that when i rooted my fire in the first place so why is it doing it now?

What i believed happened is that when i went to past the andoid market's vending.apk into the system/app folder it deleted all of the things in the folder and nothing worked not even the GUI. I hard reset and then i got stuck at the logo. Dont know if that would clarify anything

that clariefys a lot - if you messed up your /system this should help you:
http://forum.xda-developers.com/showthread.php?t=1414832
then you should be able to install twrp
hopefully ...

Thanks but that did not help. It isnt recognized in adb like that.

Can you get into recovery? When you boot it up do you see FireFireFire at all?

No it says KindeFire and its animated.

sorry but i think you'll need a factory cable to get in fastboot mode
you'r not the first one ...

I have a micro usb and it works to connect (well until i followed that link and followed the instructions )

melmantheman said:
No it says KindeFire and its animated.
Click to expand...
Click to collapse
Hi,
Did you have a look at this too:
http://forum.xda-developers.com/showthread.php?t=1356257
I had quite the same issue with mine ...Device was not recognizable at all on Windows (unknown drivers)
I used this guide and it just worked like a charm.
regards
mjay

melmantheman said:
I have a micro usb and it works to connect (well until i followed that link and followed the instructions )
Click to expand...
Click to collapse
i think you did'nt understand what a factory cable is
it's a special cable which forces the kf in fastboot mode
you can build or buy one
make a search for "factory cable" and you'll know ...

http://forum.xda-developers.com/showpost.php?p=21151545&postcount=118

Related

[Q] Another Bricked KF for the Pile [SOLVED]

I looked through A LOT of bricked KF threads but I can't fix the issue that I'm having. Before I found this forum and the very useful looking tools that it provides (KFU, etc) I managed to root my KF by using adb and pushing / installing burritoroot by the command prompt. Everything looked OK, I installed su and got root access to work in the adb shell as well as for apps.
I attempted, without much success, to get the Android Market working on my KF but it always crashed. I messed with some permissions like for /system/app, but I changed that one back to match the other folders in /system.
I may have deleted an apk out of /system/app that wasn't the Android Market, but I'm not sure...
Anyway, I tried to reboot my KF and it got stuck in a boot logo loop. It reports a boot mode of 4000 (normal).
I tried the fastboot recovery method and also KFU, but there are some issues:
Root access seems to have disappeared (access through adb shell cannot be elevated)
Burritoroot will not install anymore through KFU (I get the message "Error: Could not access the Package Manager. Is the system running?"
The above message also occurs when I try to use the adb install command
Fastboot never recognizes the device. It sits on <Waiting for Device> forever.
I've tried rebooting the KF while connected and reconnecting the USB.
I made a Factory Cable, but the Fastboot condition is the same.
I uninstalled my Windows drivers until it showed up as "Kindle" in the Device Manager and installed the files that came with KFU.
I tried the KF Unbrick utility, but that didn't seem to do anything that I missed.
Additionally, when I connect with adb shell I have limited file system access. I can is through /system and some other folders, but I can't access /sdcard and I can't seem to mount the sd card
After writing all this and thinking it through, I decided to compare the /system/app directory on my KF with one in an update.zip file that I downloaded.
It looks like I deleted the file ApplicationsProvider.apk from /system/app
That seems to be the only thing missing.
Is this a Try-to-return-your-KF important file? Is my KF hosed?
fonetik said:
Is this a Try-to-return-your-KF important file? Is my KF hosed?
Click to expand...
Click to collapse
Nope, if you can get fastboot working it doesn't matter how broken /system is. Try this to sidestep the Windows driver problems I think you're having:
http://forum.xda-developers.com/showthread.php?t=1430038
Once you get TWRP installed you can restore from the stock update which will wipe and replace /system.
Thanks I'll give this a shot. I had some issues with Windows when trying to install Cyanogen on my Droid X and a Linux Live-CD got me back on track. Hopefully this will do the trick. I'll report back.
Well, I'm in Ubuntu and I got the firekit stuff up, but it does the same thing. It refuses to connect with fastboot. It just sits at < Waiting for Device >.
I had a similar problem and it was my usb driver set up:
/etc/udev/rules.d/##-android.rules
the ## for Meerkat is 70
SUBSYSTEM==”usb”, ATTR{idVendor}==”0bb4″, MODE=”0666″
Vendorid is 1949 for KF
link that got me going: http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/
sorry if you already know this.
I'm new to this so thanks. I'll try it tomorrow when I get a chance.
fonetik said:
Well, I'm in Ubuntu and I got the firekit stuff up, but it does the same thing. It refuses to connect with fastboot. It just sits at < Waiting for Device >.
Click to expand...
Click to collapse
Are you sure you're in fastboot at that point? Are you using your factory cable? Try doing this to get into fastboot mode and use a different USB cable to connect with fastboot. If that doesn't work, do the same but use Firekit in case the fastboot drivers are messed up.
I'm probably not in fastboot. I'll give this a shot. Thanks again.
Edit:
That seems to have gotten me into Fastboot! I'll see if I can get TWRP installed.
There's a faint pulse =)
Edit 2: TWRP installed OK and I used it to try and install the stock update.zip. It rebooted and then got stuck at the logo again, but I'm going to keep working on it. At least I have a tool I can use.
Edit3: I seemed to be stuck at the TWRP yellow triangle, I think I managed to install FireFireFire, and managed to get back into TWRP. I cleared all my caches and did a factory reset. Then I installed a pre-rooted version of 6.2.1. It did a little reboot dance for a while and then came up into the OS!
Thanks a ton pokey9000. I'm happy to send a couple $$ your way.
fonetik said:
Edit3: I seemed to be stuck at the TWRP yellow triangle, I think I managed to install FireFireFire, and managed to get back into TWRP.
Click to expand...
Click to collapse
Just in case someone else reads this... The Yellow Triangle is not TWRP... it is FireFireFire... TWRP by default is the blue themed screens you get after the FireFireFire icon and will start out saying TEAMWIN in Landscape mode.
BTW, good to hear you fixed the problem. You should edit the original post and change the Subject adding [SOLVED]
krelvinaz said:
Just in case someone else reads this... The Yellow Triangle is not TWRP... it is FireFireFire... TWRP by default is the blue themed screens you get after the FireFireFire icon and will start out saying TEAMWIN in Landscape mode.
BTW, good to hear you fixed the problem. You should edit the original post and change the Subject adding [SOLVED]
Click to expand...
Click to collapse
Sorry about the confusion. It was the FFF triangle, but the KF wasn't going into recovery when I held the power button down. I reinstalled with FFF using adb and it worked. Original post subject updated.

Kindle Fire Boots to Team Win Recovery Program Screen

Help! For Christmas my parents bought me a Kindle Fire but before I got it, they gave it to my sisters boyfriend who is a techy kind of guy and he put twrp and hacked the kindle. Well the other day I was trying to download something and it rebooted and went straight to the TWRP gray screen (the one with the options to install, backup, restore, wipe, etc.) I do not know what to do! I have searched through threads on the forum about using the kindle fire utility, it doesnt work. My computer recognizes the kindle as an android phone and when i run the utility, it says my boot status is unknown so i dont think that the program is detecting my kindle? Please help!
Are you having trouble getting out of TWRP, or what?
Just click on Reboot --> System and that should get you back into the normal system.
You may also want to check into this if you have further problems:
http://forum.xda-developers.com/showthread.php?t=1356257
I have tried the link that you have given me before and it didnt work as well. I've also tried the reboot -> system and the other option given. Neither of them work. My problem is, whenever i start up my Kindle, it goes straight to that screen after the yellow triangle screen. Any help?
Dakdak234 said:
I have tried the link that you have given me before and it didnt work as well. I've also tried the reboot -> system and the other option given. Neither of them work. My problem is, whenever i start up my Kindle, it goes straight to that screen after the yellow triangle screen. Any help?
Click to expand...
Click to collapse
I'm assuming you accidentally hit "reboot into recovery. If you are not a "techy" guy, you need to get in that mode and follow the link dude provided. You will need to download a couple programs to your pc, and acquire a microusb cable. Follow directions to the TEE' and you'll be ready to go in no time.
Sent from my Amazon Kindle Fire using xda premium
kfu is just good for what you need - regardless what status it reports try option1 and bootmode normal
if it does not work check your drivers - in device manager it should show up under android phones - if not update the driver - try to run install_drivers.bat in the kfu directory first - if it does'nt work try to update manually - it is in the drivers\kindle directory of kfu
regarding drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
then retry kfu option 1 bootmode normal
Okay so i remembered using winRAR you need to extract the folder and I did and the kfu is working properly now except for one thing, it says the ABD status is offline... i dont know what to do about this
the adb status is offline - this is normal when the kf is in fastboot mode
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
Sorry but i'm confused on what youre telling me to do :/
- run kfu
- select option 1 (bootmode menu)
- select option 1 (bootmode normal)
that's it
Thank you a million! I just realized that i was typing in "4000" instead of "1" and it wasnt recognizing the command!
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
Okay 1 last thing and im really sorry for putting you through all this... when its booting up, it gets past the black screen with the yellow triangle but after that the screen is just black, its not shutoff because i can see that the backlight is on... Is this a problem thats fixable?> :/
hold the power button for ~20sec till it turns off - power on again
Did like you told me to... Got past the yellow triangle fire fire fire screen and just sits there with the backlight on...
what did you try to install ? it seems the kf can't boot into a system ...
and as you asked earlier - everything (besides hardware failures) is fixable
but a hardware failure seems not to be your problem
I cant exactly remember but i remember it downloaded and then the kindle randomly shut off and when i turned it back on it just went straight to the recovery... ive tried resetting the kindle several times right now and even going back into the recovery mode and nothing is working :/ i believe the problem has gotten worse
you can install a new rom now - which one did you have before ?
i can give you the download location and how it is done ...
Like i mentioned before, i didnt set it up. I cant tell you what rom was downloaded but i do remember some programs that ive seen before in guides?? There were like the golauncher and other "go" programs... if that doesnt stand out to any specific one i believe there were some cryogen (or however its spelled) stuff on it... i know it was set up just like his verizon phone
then i would think it it was cm7 - download from here: http://www.mediafire.com/download.php?hmdc0lmgvnlbg97
this is the update version - i would try this one first so you should not loose anything
- boot into twrp
- now you should see the kf on your computer
- copy the downloaded file on the kf
- tap install
- select the file and install
try this first
Okay thank you. Is it okay if i PM you if something goes wrong? You seem to know alot about this

[Q] a2107 adb recovery?

I screwed up.
I just experimented with enabling phone mode on that device, after i had it rooted.
so i modified recomipled and signed the framework.apk but i had a typo in my script and the name of the new file is botched up.
My device instantly crashed of course. This is pretty forward to fix once i get access to /system in any way.. also i have a backup of that file on the pc.
Needless to say, without framework it wont boot. I *can* however get into recovery. but there is no adb option in there.
while i am in that menu, the pc recognices the device as "lenovo adb composite" but the adb does not seem to recognize it.
The drivers are set up correctly. the adb worked on the fully running device before the crash. (obviously, since i rooted it that way)
Any suggestions?
and what is the recovery menu point "download cap-firmware" doing exactly?
any help and potential helpfull links very much appreciated, i googled half the night and found next to nothing..
Solved
Solved.
appearantly the decive announces itself slightly differently in this mode.
solution:
The aur version of adb (arch linux) handles this correctly. no drivers needed.
so for all having problems, with this device, my recommendation for now: archlinux or archbang bang live, "packer -S adb" .. "adb shell"
Hi,
you managed to root your A2107A? I've been googling for two weeks and I didn't figure out... Could you please me tell me how you achieve that?
Cheers
da root
FiltroMan said:
Hi,
you managed to root your A2107A? I've been googling for two weeks and I didn't figure out... Could you please me tell me how you achieve that?
Cheers
Click to expand...
Click to collapse
sure thing.
as always first check, that all batteries are charged. (laptop, tablet, ..)
** first you need to enable usb debugging in the menu.
** then plug it in and check on windows that it is recognized properly.
it should show up as "lenovo(or android) composite adb interface" somewhere in device manager.
otherwise tell me, and i'll try to find the proper drivers. (on archlinux it worked without drivers, so if you fail on windows for some reason, that is an option too,)
** after that you need this:
https://dl.dropbox.com/u/31794772/Root_with_Restore_by_Bin4ry_v15.rar
i don't remember where exactly i found this on xda-deverlopers. credits to whoever put that up in the first place, sry.
** choose option 1 in the script.
follow the instructions on the tool. it will ask you at some point to push restore on the tablet, no worries, this is completely intended you wont loose any data if it works right. just leave all fields blank and hit restore.
congrats, you are now rootet. the device might require a reboot and might do that from itself (dont remember)
:good:
ps: doing backup like this first is generally a good idea: http://forum.xda-developers.com/showthread.php?t=1420351
I have the a2107-F will this root process work too?
valravn said:
I screwed up.
I just experimented with enabling phone mode on that device, after i had it rooted.
so i modified recomipled and signed the framework.apk but i had a typo in my script and the name of the new file is botched up.
My device instantly crashed of course. This is pretty forward to fix once i get access to /system in any way.. also i have a backup of that file on the pc.
Needless to say, without framework it wont boot. I *can* however get into recovery. but there is no adb option in there.
while i am in that menu, the pc recognices the device as "lenovo adb composite" but the adb does not seem to recognize it.
The drivers are set up correctly. the adb worked on the fully running device before the crash. (obviously, since i rooted it that way)
Any suggestions?
and what is the recovery menu point "download cap-firmware" doing exactly?
any help and potential helpfull links very much appreciated, i googled half the night and found next to nothing..
Click to expand...
Click to collapse
valravn,
Can you please elaborate a bit on modifying the framework.apk?
The solutions I found require flashing a whole rom which I wouldn't like to do (looks like I got the tablet with the latest FW).
Your help will be much appreciated.
Thanks.
I think i bricked my ideatab. i tried to update the CWM via ROM Manager unfortunately when i restarted the device, it got stuck on the menu showing "Press and select the Country Code". after pressing and selecting one of the choices it will just restart and return to the same menu.
Can you please help me guys? thanks in advance.

Unlocked but can't root/install CWM

I used the toolkit for mac and it unlocked me, but when it came to the next steps it said device not found and then told me to highlight recovery and press start, when I do I get the android with the red ! symbol.
Can someone help me?
That symbol is a security feature within the stock recovery, volume up and power to access the stock recovery.
Sent from my Nexus 4 using Tapatalk 4
I tried that it's not working I press up then power the phone reboots and the red ! symbol shows up...
I searched and saw hold power and press up when I see the red ! but it just reboots the phone...
help please?
Sent from my GT-N5110 using Tapatalk 4
ADB wont work in stock recovery
roguedroid said:
I tried that it's not working I press up then power the phone reboots and the red ! symbol shows up...do you know the adb instructions on how to push supersymmetric and cwm?
edit my adb now won't recognize my phone even though it did a few mins ago...
I'm frustrated, been trying to access the stock recovery for the past several mins and simply can't.
help please?
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
For me also Stock recovery never worked. Just try to flash CWM or TWRP.
Btw, What toolkit did you use and how did you install the drivers. Please answer these, so that someone can help you better.(Or is it just the 'mac toolkit' ?)
My suggestion: PLZ DO NOT USE TOOLKIT. If you are stuck at some point while using the toolkit, then you'll not know what went wrong and how you can correct it. Do it manually. It is the most hassle-free method. Trust me.
I think that ADB will not work in stock recovery(may be you can boot normally into your phone and then try adb). The thing which you are looking for is 'fastboot'.
1) Restart ur phone (Power Button + Volume Down, i guess) and land in the bootloader and connect your phone to PC.
2) In CMD prompt(or Terminal), type 'fastboot devices'. If your device gets listed here, then fastboot is working and drivers are properly installed. If not, then drivers are not properly installed in your PC. You need both ADB and FASTBOOT drivers. Install them properly.
PS: For MAC, i think the command is slightly different. Something like './fastboot devices' . Please look for the same in this forum or just google it and find out.
3) Follow this guide for flashing CWM and Rooting.
http://forum.xda-developers.com/showthread.php?t=2266654
4) For properly installing the Drivers, read " A. Install the drivers " in the below thread (actually you can read the entire thread )
http://forum.xda-developers.com/showthread.php?t=2010312&highlight=cwm+6+0+3+5
My knowledge is limited to Windows PC, sorry if I am not of much help. Thanks !
badhri said:
For me also Stock recovery never worked. Just try to flash CWM or TWRP.
Btw, What toolkit did you use and how did you install the drivers. Please answer these, so that someone can help you better.(Or is it just the 'mac toolkit' ?)
My suggestion: PLZ DO NOT USE TOOLKIT. If you are stuck at some point while using the toolkit, then you'll not know what went wrong and how you can correct it. Do it manually. It is the most hassle-free method. Trust me.
I think that ADB will not work in stock recovery(may be you can boot normally into your phone and then try adb). The thing which you are looking for is 'fastboot'.
1) Restart ur phone (Power Button + Volume Down, i guess) and land in the bootloader and connect your phone to PC.
2) In CMD prompt(or Terminal), type 'fastboot devices'. If your device gets listed here, then fastboot is working and drivers are properly installed. If not, then drivers are not properly installed in your PC. You need both ADB and FASTBOOT drivers. Install them properly.
PS: For MAC, i think the command is slightly different. Something like './fastboot devices' . Please look for the same in this forum or just google it and find out.
3) Follow this guide for flashing CWM and Rooting.
http://forum.xda-developers.com/showthread.php?t=2266654
4) For properly installing the Drivers, read " A. Install the drivers " in the below thread (actually you can read the entire thread )
http://forum.xda-developers.com/showthread.php?t=2010312&highlight=cwm+6+0+3+5
My knowledge is limited to Windows PC, sorry if I am not of much help. Thanks !
Click to expand...
Click to collapse
I used the nexus 4 Mac rootkit I found in here.
It unlocked my phone fine. But when it came to installing a recovery and root it didn't.
Neither my adb or fastboot are working now before I unlocked and I messed around and they worked now nada ...
I went to YouTube saw my problem tried pressing volume up and power like in the video and it just gives me a black screen and either turns the phone off or reboots it normally...not sure if in supposed to hold power and let go of volume or vice versa.
I placed all the files on the storage I just need to access stock recovery which I strangely cannot now...
Tried framearoot and got nowhere.
Very frustrating
Sent from my GT-N5110 using Tapatalk 4
Sort out the drivers and adb,fastboot
roguedroid said:
I used the nexus 4 Mac rootkit I found in here.
It unlocked my phone fine. But when it came to installing a recovery and root it didn't.
Neither my adb or fastboot are working now before I unlocked and I messed around and they worked now nada ...
I went to YouTube saw my problem tried pressing volume up and power like in the video and it just gives me a black screen and either turns the phone off or reboots it normally...not sure if in supposed to hold power and let go of volume or vice versa.
I placed all the files on the storage I just need to access stock recovery which I strangely cannot now...
Tried framearoot and got nowhere.
Very frustrating
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
Just as I mentioned, i also had the same problem with stock recovery. So I simply flashed a Custom one(CWM, in my case)
Get the ADB and FASTBOOT working and that'll solve your recovery problem. Try fiddling with your drivers again. Not sure how to do that in MAC. If FASTBOOT is working, the you can boot into a Custom Recovery(you need not even flash it) and perform whatever you need to.
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Again, look at the efrant's guide i referred above; i took this from there only.Remember to replace 'customrecovery.img', with the actual downloaded custom recovery image name.
Or you can try posting your problem with the toolkit, in mac toolkit's thread.
I have been youtubing everything and finally got to
Reboot system
apply update from adb
wipe data/factory reset
wipe cache partition.
I now can get adb working so I tried ./adb sideload cwm from my desktop and it is giving me signature verification failed. installation aborted.
What can I do to resolve this?
I searched xda and no one can solve this issue from the threads I've read.
I fixed it! Whooohoooo! Installed cwm and root ....now to install pa rom.
Thanks for the help!
Sent from my GT-N5110 using Tapatalk 4

[Q] D802 Bricked, computer won't recognize it

Hi,
I recently updated to the official 4.4.2 kitkat update.I then proceeded to root the phone, and then stupidly, installed CWM. I rebooted, and was greeted with an endless LG Splash screen. Now, I tried a HEAP of ways to restore to stock, all of them returning the same problem, my computer won't pick up my phone. In download mode, nothing happens, nothing in device manager, and same when I'm stuck on the LG splash screen. When I go into CWM, it then recogizes my phone, but the methods of restoring to stock won't work with CWM running in the background. CWM also won't let me mount the usb...
The methods return the same error: Phone not detected, please plug the USB cable and retry.
Ubuntu won't recognize the phone in all three modes, and another computer does the same thing. (Both Windows 8)
Methods of stock restoration tried:
-KDZ
-LGMobile support tool
-Ubuntu (This: http://forum.xda-developers.com/showthread.php?t=2582142)
Can anyone help?
MintLord said:
Hi,
I recently updated to the official 4.4.2 kitkat update.I then proceeded to root the phone, and then stupidly, installed CWM. I rebooted, and was greeted with an endless LG Splash screen. Now, I tried a HEAP of ways to restore to stock, all of them returning the same problem, my computer won't pick up my phone. In download mode, nothing happens, nothing in device manager, and same when I'm stuck on the LG splash screen. When I go into CWM, it then recogizes my phone, but the methods of restoring to stock won't work with CWM running in the background. CWM also won't let me mount the usb...
The methods return the same error: Phone not detected, please plug the USB cable and retry.
Ubuntu won't recognize the phone in all three modes, and another computer does the same thing. (Both Windows 8)
Methods of stock restoration tried:
-KDZ
-LGMobile support tool
-Ubuntu (This: http://forum.xda-developers.com/showthread.php?t=2582142)
Can anyone help?
Click to expand...
Click to collapse
Have you tried adb sideload
raahult said:
Have you tried adb sideload
Click to expand...
Click to collapse
I don't know how to do that, And no, I don't think I have. Could you give me a guide on doing that?
MintLord said:
I don't know how to do that, And no, I don't think I have. Could you give me a guide on doing that?
Click to expand...
Click to collapse
Install http://forum.xda-developers.com/showthread.php?t=2588979
then go to recovery and try adb devices on command prompt on your PC to check if your device is listed
if it shows your devices then just search any thread that tell how to push flashable rom to your device.
raahult said:
Install http://forum.xda-developers.com/showthread.php?t=2588979
then go to recovery and try adb devices on command prompt on your PC to check if your device is listed
if it shows your devices then just search any thread that tell how to push flashable rom to your device.
Click to expand...
Click to collapse
No luck...
raahult said:
Install http://forum.xda-developers.com/showthread.php?t=2588979
then go to recovery and try adb devices on command prompt on your PC to check if your device is listed
if it shows your devices then just search any thread that tell how to push flashable rom to your device.
Click to expand...
Click to collapse
Wait, I got it working!
MintLord said:
Wait, I got it working!
Click to expand...
Click to collapse
Was your phone able to connect to the PC afterwards? I have a D800 that I am unable to get any PC to recognize. I need to restore it to stock but no matter what I do it does not show up in device manager (and I have a working rom on it).
crawlgsx said:
Was your phone able to connect to the PC afterwards? I have a D800 that I am unable to get any PC to recognize. I need to restore it to stock but no matter what I do it does not show up in device manager (and I have a working rom on it).
Click to expand...
Click to collapse
Yes, it does work now. I was able to restore to stock by adb pushing phillz recovery, and then flashing that, then adb pushing the stock ROM. Everything works as it should, now.
MintLord said:
Yes, it does work now. I was able to restore to stock by adb pushing phillz recovery, and then flashing that, then adb pushing the stock ROM. Everything works as it should, now.
Click to expand...
Click to collapse
Ah nice. Unfortunately I can't get device manager to see mine at all so I can't even ADB .
crawlgsx said:
Ah nice. Unfortunately I can't get device manager to see mine at all so I can't even ADB .
Click to expand...
Click to collapse
Does it recognize your phone when it's in the custom recovery? That was the only way I could do it on my phone.
Good luck!
I tried ADB devices nothing came out.
I have the same problem as listed in this thread. Tried everything to SHort circuit the chip. Basically everything.
I think the last thing i haven't try is dump it into the bin.
MintLord said:
Does it recognize your phone when it's in the custom recovery? That was the only way I could do it on my phone.
Good luck!
Click to expand...
Click to collapse
On TWRP it's detect my phone as "LGE Android MTP device" and i can't copy anything from my PC to my phone,
I can't ADB push too, it was error Read-only system
Any ideas?
Hi, sorry to post in this 1 year old post buy mt G2 is totally dead, I can sometimes get LG Logo and the main problem is i cannot get it into QHS-USB mode or anything.
Is there any key combinaison to do that ?

Categories

Resources