Normally I can figure out these things my self or find somebody else who has this problem, but not this time and It's driving me crazy.
My Nexus 7 is rooted and bootloader is unlocked and I've have been into custom recovery before, but now it don't want to launch the damn thing, it keeps getting stuck on the Android on it's belly with the red !
I've tried:
The normal way - Holding down power button+both volume buttons and then choosing recovery from the menu and with a USB cable attached to the unit. Result = Stuck on Android with red !
From quick boot app and Nexus Toolkit - Rebooting into to recovery, same result. Both with USB cable in and out.
I also tried reflashing the clockworkmod touch recovery from Nexus 7 Toolkit, no errors and I remembered to use the option 5, so the stock recovery image was renamed. Still no good, didn't leave a working recovery behind.
The latest thing I tried was booting the custom recovery without flashing recovery (option 10 from Nexus Toolkit) and then I updated to Android 4.2 Before I rebooted, the temporary clockworkmod touch recovery warned me that I would loose my recovery and my root and if I wanted to fix it, I choose yes to both. My root didn't go away, but I still don't have a working custom recovery I can boot from the bootloader or eg. the quick boot app.
What am I missing here?
To be on the safe side, just reflash CWM. That should fix it.
Sent from my myTouch_4G_Slide using Tapatalk 2
You got stock recovery.
To get the menu, once you see the android with the red "!", press and hold "Power" and then press "Volume Up", then let go of the buttons.
As the previous poster suggested, flash CWM and all shall be better.
Thanks for the fast replies.
I had an idea that It was stock recovery, didn't knew about the button combination, thanks!
I'm gonna try to flash touch CWM again.
And now it works... well that's strange, no idea why it didn't work before, when I flashed touch CWM from Nexus Tookit.
Oh well, I got my problem fixed and at the same time got more clever, thanks again.
Same/similar problem
I flashed the 4.2 OTA .zip from CWM this morning and it worked fine. As expected I lost root. Unexpectedly, I also lost CWM and I have been unable to flash a custom recovery ever since.
I started off trying to re-flash CWM with the Nexus 7 Toolkit v3.2. When that failed a few times, I also tried TWRP with the same result.
When I say "failed" I mean that toolkit flashes with no errors but when I select recovery after flashing, I get the google logo, then a black screen, then the google logo again, and then a normal boot. If I reboot and manually go into recovery mode I get the Dead Android logo and PWR + VOLUP gives me stock recovery, which I guess is to be expected since I am unable to rename the recovery restore files.
After giving up on the toolkit, I downloaded CWM and flashed it manually with fastboot but I'm getting the same results.
Anyone else run into this? I can only assume 4.2 has introduced some incompatibility with existing tools/recovery images so I'm just going to wait and hope someone sorts this out. 4.2 seems to be working fine though I'd like to get root back.
Sim2 said:
Anyone else run into this? I can only assume 4.2 has introduced some incompatibility with existing tools/recovery images so I'm just going to wait and hope someone sorts this out. 4.2 seems to be working fine though I'd like to get root back.
Click to expand...
Click to collapse
Hm, works fine for me.
After applying the 4.2 OTA I rebooted to bootloader, did a "fastboot flash recovery", went into the CWM directely after flashing it and upon selecting "reboot device now" from CWM it asked me if it should disable the recovery flash from the system.
Working fine since then, no problems.
When I do a "fastboot flash recovery", the image copy appears to work but the Nexus 7 stays in fastboot mode when it's finished. If I manually select recovery, I get the Google logo > black screen > Google Logo > normal boot.
What version of CWM did you flash? I used touch recovery 6.0.1.0 from here: http://clockworkmod.com/rommanager Will try non-touch version today.
It looks like a few others have run into the same problem. http://forum.xda-developers.com/showthread.php?t=1990904
This could have been a pre-existing problem as I don't think I've used recovery since the 4.1.2 update.
HellcatDroid said:
Hm, works fine for me.
After applying the 4.2 OTA I rebooted to bootloader, did a "fastboot flash recovery", went into the CWM directely after flashing it and upon selecting "reboot device now" from CWM it asked me if it should disable the recovery flash from the system.
Working fine since then, no problems.
Click to expand...
Click to collapse
---------- Post added at 10:36 AM ---------- Previous post was at 09:40 AM ----------
So I finally got a custom recovery installed by doing a "fastboot flash recovery" of the latest TWRP (2.3.1.1) from here: http://teamw.in/project/twrp2/103
Neither of the current CWM recoveries (6.0.1.0) would work for me.
I swear I have been having the exact same problem. I will try the other recovery. Question, is yours a 32 GB version? I doubt it's related but still worth a check. Thanks for your info.
Sim2 said:
When I do a "fastboot flash recovery", the image copy appears to work but the Nexus 7 stays in fastboot mode when it's finished. If I manually select recovery, I get the Google logo > black screen > Google Logo > normal boot.
Click to expand...
Click to collapse
SOLUTION: I've had the problem where recovery won't load, it just displays a black screen and loads back into Android.
It seems that ClockworkMod recovery doesn't work with Android 4.2 (at least, for me). I tried reflashing but that didn't work. I wiped my entire device and used TWRP recovery instead, and now I can get back into recovery.
I downloaded the 2.3.1.1 version, works fine! http://techerrata.com/browse/twrp2/grouper
laxet said:
SOLUTION: I've had the problem where recovery won't load, it just displays a black screen and loads back into Android.
It seems that ClockworkMod recovery doesn't work with Android 4.2 (at least, for me). I tried reflashing but that didn't work. I wiped my entire device and used TWRP recovery instead, and now I can get back into recovery.
I downloaded the 2.3.1.1 version, works fine! http://techerrata.com/browse/twrp2/grouper
Click to expand...
Click to collapse
Sure enough that's it. Guess it's a CWM issue. TWRP is working w/o issue. Thanks.
D_Rob said:
Sure enough that's it. Guess it's a CWM issue. TWRP is working w/o issue. Thanks.
Click to expand...
Click to collapse
I just noticed a new 2.3.1.3 test image....
Mine is now suck on the dead andoid /!\, I had latest super su with protection enabled.
I'm rather new to this,
I'm an heavy users and really don't want to loose my settings, I can get in ADB sideloading mode.
Is there anything I could sideload that could fix my device ?
Transisto said:
Mine is now suck on the dead andoid /!\, I had latest super su with protection enabled.
I'm rather new to this,
I'm an heavy users and really don't want to loose my settings, I can get in ADB sideloading mode.
Is there anything I could sideload that could fix my device ?
Click to expand...
Click to collapse
Do you mean that you cannot get out of the Android with (!) screen? If this is all it is just press and hold power button for about 20 seconds or until screen goes black, and then the device should startup normally.:good:
taff2408 said:
Do you mean that you cannot get out of the Android with (!) screen? If this is all it is just press and hold power button for about 20 seconds or until screen goes black, and then the device should startup normally.:good:
Click to expand...
Click to collapse
No it goes there when choosing recovery-mode.
Normal boot is getting stuck on a Google logo with a lock.
Sim2 said:
When I do a "fastboot flash recovery", the image copy appears to work but the Nexus 7 stays in fastboot mode when it's finished. If I manually select recovery, I get the Google logo > black screen > Google Logo > normal boot.
What version of CWM did you flash? I used touch recovery 6.0.1.0 from here: http://clockworkmod.com/rommanager Will try non-touch version today.
It looks like a few others have run into the same problem. http://forum.xda-developers.com/showthread.php?t=1990904
This could have been a pre-existing problem as I don't think I've used recovery since the 4.1.2 update.
---------- Post added at 10:36 AM ---------- Previous post was at 09:40 AM ----------
So I finally got a custom recovery installed by doing a "fastboot flash recovery" of the latest TWRP (2.3.1.1) from here: http://teamw.in/project/twrp2/103
Neither of the current CWM recoveries (6.0.1.0) would work for me.
Click to expand...
Click to collapse
Thanks, you save my day.
How can I try making backup or recover if I managed to get into TWRP ?
My 4.2 doesn't boot either, How can I try making backup or recover if I managed to get into TWRP ?
Flashing CWM ? I have the ADT-bundle installed but don't know much how make use of it.
Thanks you, Any help would be greatly appreciated.
how to fix error on Recovery of CWM
hello all XDA-Developers Members, good day! I have a Lenovo Ideapad A1 and last night is I tried to upgrade my Gingerbread 2.3.4 to Cyanogenmod 7 but it didn't work. It appear a Lenovo word on it after i upgrade it .... And when i bring it back to Recovery mode, it appears like this:
E:can't mount /cache/recover/command
E:can't mount /cache/recovery/log
E:can't open /cache/recovery/log
E:can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
Error mounting /cache!
Whenever I bring it back to Gingerbread, it just always appear a word Lenovo ... I am hoping sir/ ma'am that you could help me with this please!!!
Please sir/ ma'am ...
hi-shino said:
hello all XDA-Developers Members, good day! I have a Lenovo Ideapad A1 and last night is I tried to upgrade my Gingerbread 2.3.4 to Cyanogenmod 7 but it didn't work. It appear a Lenovo word on it after i upgrade it .... And when i bring it back to Recovery mode, it appears like this:
E:can't mount /cache/recover/command
E:can't mount /cache/recovery/log
E:can't open /cache/recovery/log
E:can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
Error mounting /cache!
Whenever I bring it back to Gingerbread, it just always appear a word Lenovo ... I am hoping sir/ ma'am that you could help me with this please!!!
Please sir/ ma'am ...
Click to expand...
Click to collapse
And this has what to do with a nexus 7?
Sent from my Galaxy Nexus
how to fix error on Recovery of CWM
Pirateghost said:
And this has what to do with a nexus 7?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
ahmmm sorry, if i sent a reply to ur post, i was just asking any info if someone knows how maybe ..
hi-shino said:
ahmmm sorry, if i sent a reply to ur post, i was just asking any info if someone knows how maybe ..
Click to expand...
Click to collapse
Don't you think it would be better to ask in a section of the forums where other people have the same device as you? Why would you ask in another devices forum?
Sent from my Galaxy Nexus
Related
Hello,
First of all, I tried to search, but all solutions found did not work.
Now, the problem: I can't boot to ClockWorkMod Recovery anymore (version 2.5.0.7.). The phone just goes to the dreaded Red Triangle with the Exclamation sign. I tried Power + Volume Down, then to recovery, I get and error: "E:Can't open /cache/recovery/command".
I tried to reflash the ClockworkMod recovery from the ROM Manager menu, but it didn't solve the problem.
Thank you for any suggestions.
After the E:Can't open... message appears, wait for a while, and a blue menu appears. There choose "Apply sdcard: update.zip" (which, I believe, is there if you flashed CWM), and that should launch recovery mode.
At least that works for me. Good luck!
Thank you, it works. I then rebooted it and all is ok. Still when tried to access recovery via ClockWorkMod it doesn't work. Any ideas?
What do you mean by "recovery"? CWM recovery screen? You said that it works, after applying the update.zip that should bring you to recovery screen.
The update.zip will not flash your recovery partition. You need S-OFF and to use ADB to flash a new one.
Sent from my S-OFF Bell Canada HTC Legend.
randomXP said:
Hello,
First of all, I tried to search, but all solutions found did not work.
Now, the problem: I can't boot to ClockWorkMod Recovery anymore (version 2.5.0.7.). The phone just goes to the dreaded Red Triangle with the Exclamation sign. I tried Power + Volume Down, then to recovery, I get and error: "E:Can't open /cache/recovery/command".
I tried to reflash the ClockworkMod recovery from the ROM Manager menu, but it didn't solve the problem.
Thank you for any suggestions.
Click to expand...
Click to collapse
I had the same thing, used "Fix Permissions" from within ROM Manager, then reflashed clockwork
let me know if this works for you too
I cannot figure out how to boot into recovery from phone off state. If I go to ROM Toolbox pro and reboot that way into recovery, then it works fine, but NOT from phone off state. Thanks.
Press/hold vol down + press/hold power will get you to the bootloader, then select recovery from there.
CMNein said:
Press/hold vol down + press/hold power will get you to the bootloader, then select recovery from there.
Click to expand...
Click to collapse
Tried that but Then I got the android with Red triangle.
-------
I am going to try to flash TWRP recovery again from GOomanager and see what happens.
ftarules said:
Tried that but Then I got the android with Yellow triangle.
Click to expand...
Click to collapse
Did you "fastboot flash recovery recovery.img" or "fastboot boot recovery.img"?
Got, it. Reinstalling recovery from Goomanager, worked. For whatever reason, my recovery was repalced or gone.
ftarules said:
Got, it. Reinstalling recovery from Goomanager, worked. For whatever reason, my recovery was repalced or gone.
Click to expand...
Click to collapse
I got that as well when I used the root toolkit, had to download ADB+fastboot package and flash manually.
parker09 said:
I got that as well when I used the root toolkit, had to download ADB+fastboot package and flash manually.
Click to expand...
Click to collapse
Hey the same thing is happening to me as I am using my Nexus 5. Can you please show me how to do what you did to find this. I cannot boot into recovery. When I try installing TWRP from GooManager it just says it will download but it never does and then after a while the app shuts down. I tried flashing clockwork mod recovery from Rom Manager and it downloads all the way and than says that a problem occured. Can somebody please help me with my situation. When I press the power button and the volume down button and it brings me to the bootloader and i navigate to recovery, it just brings an android guy with a red triangle. please help me. I just want a custom recovery. I don't care what it is. Either TWRP or clockwork mod.
maxell505 said:
Hey the same thing is happening to me as I am using my Nexus 5. Can you please show me how to do what you did to find this. I cannot boot into recovery. When I try installing TWRP from GooManager it just says it will download but it never does and then after a while the app shuts down. I tried flashing clockwork mod recovery from Rom Manager and it downloads all the way and than says that a problem occured. Can somebody please help me with my situation. When I press the power button and the volume down button and it brings me to the bootloader and i navigate to recovery, it just brings an android guy with a red triangle. please help me. I just want a custom recovery. I don't care what it is. Either TWRP or clockwork mod.
Click to expand...
Click to collapse
I was trying to flash get any version of Android on it so I just extracted the image (https://developers.google.com/android/nexus/images#occam) from the archive to
C:\Program Files (x86)\WugFresh Development\data
where adb.exe is located, booted into the bootloader & ran flash-all.bat
help help help!
Hello forum peoples. Recently I have tried to flashthe paranoid android firmware using flasherfy. I have twrp installed but idk if I was supposed to do with it. My phone is now in a boot loop because of my attempted flash. Please help me fix this. I am able to boot into both firmware update mode and factory reset mode. For the factory reset mode I am able to boot into the reset mode but as soon as I try to wipe it just reboots again. I have tried to use the lg firmware update tool using com5 and com41 and using both they stop at 49% and the phone just disconnects from the program/computer. Help Please! !
EDIT: I have an lg g2
ftarules said:
Tried that but Then I got the android with Red triangle.
-------
I am going to try to flash TWRP recovery again from GOomanager and see what happens.
Click to expand...
Click to collapse
For stock recovery, yes you'll see that screen. On that screen all you have to do is press power button and then press volume up (just one quick press) and it will take you into recovery menu.
---------- Post added at 01:11 AM ---------- Previous post was at 01:08 AM ----------
jcsumlin said:
Hello forum peoples. Recently I have tried to flashthe paranoid android firmware using flasherfy. I have twrp installed but idk if I was supposed to do with it. My phone is now in a boot loop because of my attempted flash. Please help me fix this. I am able to boot into both firmware update mode and factory reset mode. For the factory reset mode I am able to boot into the reset mode but as soon as I try to wipe it just reboots again. I have tried to use the lg firmware update tool using com5 and com41 and using both they stop at 49% and the phone just disconnects from the program/computer. Help Please! !
EDIT: I have an lg g2
Click to expand...
Click to collapse
You have a LG G2, so please. Ask in you device respective forum. LG G2 got its own forum too you know.
Ok, so I flashed cleanrom ex, and on reboot I got a security error.
I tried to get to recovery, but it wipes data and immediately reboots.
I've tried flashing the stock rom, but lg flash tool tells me it's the wrong device (now thinks it's a D802).
I've been trying to get into TWRP on scrosler and samsunggalaxystig's advice, first by repeatedly trying an adb reboot recovery, then by writing a batch script to do it repeatedly in order to catch it before it reboots.
Problem is, I don't know if I had already had ADB drivers installed on this computer for the G2 (had rooted while at work), and despite installing them more than once, I don't think the device actually has enough time to be recognized as I still have an unrecognized "g2" in device manager while TWRP is wiping.
Any ideas? Is there any way I can force the install of the ADB driver without having it connected for more than 20 seconds? Spitballing... would it be possible to actually flash a D802 image so I could then root, change the build.prop to D800, and then flash the D800 image?
Totally at a loss at this point.
did you solve your problem? i have a similar problem and i just bricked an s3. this g2 is brand new and now it's bricked too! if you have found a solution please respond... :crying:
kureta said:
did you solve your problem? i have a similar problem and i just bricked an s3. this g2 is brand new and now it's bricked too! if you have found a solution please respond... :crying:
Click to expand...
Click to collapse
No problem if you brick a sammy phone. its easy to flash stock rom. How did you brick your g2?
---------- Post added at 08:13 PM ---------- Previous post was at 08:11 PM ----------
lastdeadmouse said:
Ok, so I flashed cleanrom ex, and on reboot I got a security error.
I tried to get to recovery, but it wipes data and immediately reboots.
I've tried flashing the stock rom, but lg flash tool tells me it's the wrong device (now thinks it's a D802).
Totally at a loss at this point.
Click to expand...
Click to collapse
Why did flashing a rom leads you to that error? Sorry but not familiar with your roms but is this rom really for your LG G2 model?
lastdeadmouse said:
Ok, so I flashed cleanrom ex, and on reboot I got a security error.
I tried to get to recovery, but it wipes data and immediately reboots.
I've tried flashing the stock rom, but lg flash tool tells me it's the wrong device (now thinks it's a D802).
I've been trying to get into TWRP on scrosler and samsunggalaxystig's advice, first by repeatedly trying an adb reboot recovery, then by writing a batch script to do it repeatedly in order to catch it before it reboots.
Problem is, I don't know if I had already had ADB drivers installed on this computer for the G2 (had rooted while at work), and despite installing them more than once, I don't think the device actually has enough time to be recognized as I still have an unrecognized "g2" in device manager while TWRP is wiping.
Any ideas? Is there any way I can force the install of the ADB driver without having it connected for more than 20 seconds? Spitballing... would it be possible to actually flash a D802 image so I could then root, change the build.prop to D800, and then flash the D800 image?
Totally at a loss at this point.
Click to expand...
Click to collapse
Hey I'm in the exact same position as you... did you manage to figure out a way to get into recovery?
kureta said:
did you solve your problem? i have a similar problem and i just bricked an s3. this g2 is brand new and now it's bricked too! if you have found a solution please respond... :crying:
Click to expand...
Click to collapse
twrp corrupted my cache partition and the phone could not boot. i tried to flash cwm while in twrp and i guess i messed up recovery and/or boot partitions. al i could get was fastboot. i flashed a boot.img i got from somewhere in here. now it says security error and it does not boot. it does not enter into fasboot. i can enter into recovery mode but it is the stock lg recovery and if i choose "delete all data", which is the only option, it gives an error and restarts.
if i try to flash stock firmware as described in this post it stops at 49%.
kureta said:
twrp corrupted my cache partition and the phone could not boot. i tried to flash cwm while in twrp and i guess i messed up recovery and/or boot partitions. al i could get was fastboot. i flashed a boot.img i got from somewhere in here. now it says security error and it does not boot. it does not enter into fasboot. i can enter into recovery mode but it is the stock lg recovery and if i choose "delete all data", which is the only option, it gives an error and restarts.
if i try to flash stock firmware as described in this post it stops at 49%.
Click to expand...
Click to collapse
I am on the same boat, same problem, and don't know what else to do...hope someone could help us out.
Yep me to same issue. Pretty much tried 6 different methods and still stuck
Solution
IF you still have guys this issue i have solusion for you .
This happened to me yesterday too
1. Download ADB drivers for LG G2 LINK
2. Download LG Mobile Support Tool you can find this here LINK
3. HOLD VOLUMEUP + POWER button to enter the download mode and connect your device to pc
4. Run LG Mobile Support Tool ( if your device vas found click settings select upgrade firmware this will download for you 1.9 GB STOCK FIRMWARE
5. Enjoy your mobile
Any luck anyone? I can't get the suggestion in the last post to work because my phone just goes from the LG Logo to Security Error. I can't get to download mode. Or recovery. Or get ABD to see it.
Odd
quatrix1 said:
IF you still have guys this issue i have solusion for you .
This happened to me yesterday too
1. Download ADB drivers for LG G2 LINK
2. Download LG Mobile Support Tool you can find this here LINK
3. HOLD VOLUMEUP + POWER button to enter the download mode and connect your device to pc
4. Run LG Mobile Support Tool ( if your device vas found click settings select upgrade firmware this will download for you 1.9 GB STOCK FIRMWARE
5. Enjoy your mobile
Click to expand...
Click to collapse
i have to choose upgrade recovery and it gets past analyzing then doesnt show a bar for downloading software...
HELP!!!!!!!!!!!!!!!!!!!!!
Can someone help me I successful in installing twrp though autorec apk and the same for rooting my g2. I flashed cm with nightlies and noticed that twrp had a update. I downloaded the zip and try flashing it like flash a recovery in flashify but that din't work and readed that zip flashing though twrp didn't work but renumber this video and though it would update my recovery to 2.7.1 but it was successful in doing so but when I got to recovery it was 2.7.0. That not the problem form there I tried to boot into my system. Then it turn off though that I passed power off instead but when turn my g2 back on I found that I had a security error show up then turn back off. So can someone help show me a tutorial on unbick or a way to remove error. Also I have the d800 and i have some idea without going though unbicking a hard factory rest or flasing twrp form there site in fastboot. Finally that lg mobile support tool say that im up to date. I think doing the autorec twrp recovery locked as my phones recovery like trying to flash a rom with a locked bootloader.
Ok guys i trying to help cause it happen to me too,sorry for my english too slow but i try,when you try go twrp with volume up+power buttom it still show security errow,that ok your device not hardbrick yet,when you try volume down+power buttom it show hard reset it does mean it clear all rom,picture in internal but it go to twrp again,and them just flash another rom in your device and it done,have great day piece
I had the same problem on my G2 was using twrp to flash cyanogenmod not sure what i did and phone rebooted to show security error message. I entered recovery mode (power and volume down release when logo pops up and press power and volume down again hold for a second then tap both buttons a few times) pulled up the option to factory reset so i did and it booted me into twrp and allowed me to flash cyanogenmod correctly this time and the phone started back up with no problems. hope this can help someone else as well.
Anybody know the solution?
I also have the security error boot loop after flashing KK baseband files... I tried to enter recovery mode by holding vol down & power button but it wont work...
it does work when i enter download mode (vol up + power button), but i don't want to have to download the stock LG ROM..
anybody know how to by pass the security error boot loop to allow me to reflash?
kureta said:
did you solve your problem? i have a similar problem and i just bricked an s3. this g2 is brand new and now it's bricked too! if you have found a solution please respond... :crying:
Click to expand...
Click to collapse
if you still bricked. try this
get your tools from here: http://forum.xda-developers.com/showthread.php?t=2432476
keep reading or follow above thread. both will work.
best of luck.
After all the drivers installed correctly
make sure your phone is connected to the
com41 port change it if it already not ( Under device manager > Go to Ports (COM & LPT). You should see LGE AndroidNet etc... Right click it and go to Properties > Port Settings > Advanced > Change COM Port Number to COM41 > OK > OK > Close Device Manager )
run flash tool
1. choose type CDMA
2. chose PhoneMode: DIAG
leave rest as it is.
3. choose your kdz file.
then go to download mode
1. power off
2. press and hold vol + key and plug usb cable
3. done )
We have go 2 flashing modes.
1. Normal Flash is for flash with keeping data
2. CSE flash is totally new start preffered.
hope this helps.
thanks but it was a long time ago and I further messed up things, ended up sending it for warranty. they have replaced the device.
me too messed up my cell 1st i was on cloudy g2 v2.1 installed cm11 nightlies but the camera was not so good so then installed cloudy g2 v2.1 n since then i was having problem regarding sound during call and also some hard noise like siren starts randomly, i searched alot but didnt got any solution. wiped all many times (including internal storage ). but no luck then i thought i might be baseband error so i just downloaded auto recovery n flashed it n then stuck into security error but thank GOD i had custom rom in my sd card that time i flashed it back but still em having the sound error.
lastdeadmouse said:
Ok, so I flashed cleanrom ex, and on reboot I got a security error.
I tried to get to recovery, but it wipes data and immediately reboots.
I've tried flashing the stock rom, but lg flash tool tells me it's the wrong device (now thinks it's a D802).
I've been trying to get into TWRP on scrosler and samsunggalaxystig's advice, first by repeatedly trying an adb reboot recovery, then by writing a batch script to do it repeatedly in order to catch it before it reboots.
Problem is, I don't know if I had already had ADB drivers installed on this computer for the G2 (had rooted while at work), and despite installing them more than once, I don't think the device actually has enough time to be recognized as I still have an unrecognized "g2" in device manager while TWRP is wiping.
Any ideas? Is there any way I can force the install of the ADB driver without having it connected for more than 20 seconds? Spitballing... would it be possible to actually flash a D802 image so I could then root, change the build.prop to D800, and then flash the D800 image?
Totally at a loss at this point.
Click to expand...
Click to collapse
kureta said:
did you solve your problem? i have a similar problem and i just bricked an s3. this g2 is brand new and now it's bricked too! if you have found a solution please respond... :crying:
Click to expand...
Click to collapse
k2thejx5 said:
Yep me to same issue. Pretty much tried 6 different methods and still stuck
Click to expand...
Click to collapse
Hey guys, I was in the same boat for a little but was able to fix it by downloading the 801C firmware and flashing it. The firmware file should be a KDZ extension and you should also download LG Flash Tool 2014. Turn the phone on by holding the Power button and Volum up while it is plugged into your computer(It has to be plugged into a computer with LG phone drivers or it won't work).
Follow this tutorial and you will be set.
http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/
Start at step 17 on Method 1 and you should be golden.
Hope this helps guys!
So, my phone was stuck in No Command bootloop. I’ve done the power+volume up and had cleared cache and even done a factory reset. Those did nothing and my phone is still in stuck No Command loop. I think I’ve made it even worse by trying to Flash Recovery and Reboot options in the Nexus Tool Kit because my phone won’t even get to the No Command screen. It just turns on and turns off after Google comes on. Currently it stuck in that loop and only stops once the battery is completely drained. Please help.
Same problem here (ROOTED NEXUS 4)
Hi yeah I have the same problem as you just to clarify all i see is the new kitkat 4.4 logo over and over again I tried to factory reset it using TWRP didn't work. I think that the mistake I did was once TWRP installed the new system I clicked on "restart system" instead of "restart bootloader". Its still stuck at that stage and wont get past the bootscreen plzzz help
Hold vol down and power........can you get to download mode?
Sent from my Nexus 4 using XDA Premium 4 mobile app
like the above poster has mentioned you will probably have to get into bootloader mode and then factory images...
playya said:
like the above poster has mentioned you will probably have to get into bootloader mode and then factory images...
Click to expand...
Click to collapse
My power + down volume brings me to FastBoot Mode. So only, Start, Power Off Restart bootloader and Recovery mode are the only available option. Recovery Mode does nothing but bring me to the Google loop. Also what do I need and do exactly for "factory images?" I'm a total newb here.
iamj00 said:
My power + down volume brings me to FastBoot Mode. So only, Start, Power Off Restart bootloader and Recovery mode are the only available option. Recovery Mode does nothing but bring me to the Google loop. Also what do I need and do exactly for "factory images?" I'm a total newb here.
Click to expand...
Click to collapse
Think about whether noon or expert your first step is to search your issue. Where do you find factory images for a nexus 4 well search that. How to flash factory images search that. I am driving so can't point you to it but do t hide behind noob tag you caaaaaan doooo it...
It just feels so overwhelming and hard to dissect which of the hundreds of hundreds of posts is what I'm truly looking for.
Anyways, I've been reading this http://forum.xda-developers.com/showthread.php?t=2010312
I also have Nexus Tool Kit by skipsoft.
Hello,
I have the same problem with "no commands" screen...
Later, I tried to update with "OTA.zip" file from recovery mode (apply update from ADB), but I got this error:
"set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)"
I guess I can flash a clean image from flashboot, but before that I would like to recover all my data :S
How could I backup the device if adb is just working in recovery mode where I can just execute sideload commands?
(I have root, but I have not custom recovery)
All kind of help will be welcome!
Thanks!
IS ADB something I have to download?
Same "no command" here after OTA (I am forced ota and I think this was the problem)
I solved flash manually stock room of 4.4 KitKat then I rooted with nexus toolkit (I lost 7 hours of my life find the solution)
What I caught "never force framework in future", have you forced too guys?
Inviato dal mio Nexus 4 utilizzando Tapatalk
Sweet my phone is saved. Just followed these steps http://forum.xda-developers.com/showthread.php?t=2010312
Hi everyone...
Two days ago, and a few hours after installing the 8.1 update, my mom's J7 touchscreen was unresponsive, including the power button. It ran out of battery, and after I restarted it this morning, it goes to recovery mode after it tries installing system update and the No command screen is displayed.
I've searched on the web for hours and hours for solutions but none of them have worked, most probably because it requires the phone to be connected to the PC, and my PC (Windows 10) isn't even seeing the phone via USB (can't use ODIN nor ADB). BTW, the debug option most probably wasn't turned on prior to soft brick.
Phone Info:
SM-J730G J730GDXS5BRK1
No root
Error on recovery screen (the SD card has been taken out):
======================================
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
# MANUAL MODE v1.0.0#
Successfully verified dmverity hash tree
=======================================
Additional info: As I've mentioned, the power button isn't responsive, so I press the volume down button to choose the recovery options. I've tried all recovery options except for:
Wipe data / factory reset, as the phone data isn't backed up (mom doesn't want to lose the personal data as much as possible)
Apply update from ADB
Apply update from SD card
All other options are looping back to the recovery screen after installing system update screen.
Lastly, in recovery, there's an option at the bottom that states "Lacking storage booting". I'm sure that would mean something to someone reading this that would help solve the issue.
An OS downgrade or same 8.1 fix is preferred, as long as the phone data is intact. Any and all help would be much appreciated.
Try "Emergency Software Recovery" feature in Samsung Smart Switch for PC.
It could be a hardware issue as well. Clean your USB charging port with a brush and a drop of alcohol. Then dry with a hair drier.
Good evening, have you tried installing the latest version of the firmware by odin?
If not, try this.
probably its touch stopped working after the update because it was not original (already it has been changed) or it can be other cases ..
if you still can not install the newest firmware downloaded from the sammobile site you can do the second procedure.
Such you will find in this same forum.
In it you use the pc miracle box application and downgrade to 7.1.
this is the title of the post.
follow all procedures.
and it will be all right.
Fix Touch does not work on Samsung J7 Pro (J730G, J730GM) when updating Android 8.1
https://forum.xda-developers.com/ga...ix-touch-samsung-j7-pro-j730g-j730gm-t3850177
PS: Putting it into download mode: Turn the device on by holding the volume down buttons + Home + Power
Thank you. I've tried 3 times now as I am getting stuck at II. Flash TWRP and fix rom. After I flash the nougat rom via TWRP, phone reboots and the logos keep on looping. Either I am doing something wrong or I'm missing a step, or the zip is not working for my mom's phone.
Marius.Banderas said:
Thank you. I've tried 3 times now as I am getting stuck at II. Flash TWRP and fix rom. After I flash the nougat rom via TWRP, phone reboots and the logos keep on looping. Either I am doing something wrong or I'm missing a step, or the zip is not working for my mom's phone.
Click to expand...
Click to collapse
Then when you get to step II open the twrp and go into settings and uncheck the prompt option to install supersu if it is checked. whenever you do something in twrp uncheck this option. I do not know if this will be your problem but this always happens to me, if not clear at the time of restart the cell phone is in the loop screen exactly because of this option.
Cloud1245 said:
Then when you get to step II open the twrp and go into settings and uncheck the prompt option to install supersu if it is checked. whenever you do something in twrp uncheck this option. I do not know if this will be your problem but this always happens to me, if not clear at the time of restart the cell phone is in the loop screen exactly because of this option.
Click to expand...
Click to collapse
Checked TWRP Settings and there's no option / tickbox for supersu. I think one thing that I'm doing wrong is that I'm formatting data in TWRP during the wipe process instead of just sliding it to restore factory settings. I will try again later today after work.
Also, one thing I've noticed after flashing TWRP is that I have to enter recovery mode twice - the first time, it goes to the No command error screen then goes to stock recovery. Only after a reboot in the stock recovery would the phone enter TWRP recovery.
Marius.Banderas said:
Checked TWRP Settings and there's no option / tickbox for supersu. I think one thing that I'm doing wrong is that I'm formatting data in TWRP during the wipe process instead of just sliding it to restore factory settings. I will try again later today after work.
Also, one thing I've noticed after flashing TWRP is that I have to enter recovery mode twice - the first time, it goes to the No command error screen then goes to stock recovery. Only after a reboot in the stock recovery would the phone enter TWRP recovery.
Click to expand...
Click to collapse
Just one more thing. In tutorials on how to install twrp. when you enter twrp the first thing you should do is format the data. then install the rmm state prenormal and bypass files and only then install magisk or a custom rom.
---------- Post added at 11:10 PM ---------- Previous post was at 11:05 PM ----------
Cloud1245 said:
Just one more thing. In tutorials on how to install twrp. when you enter twrp the first thing you should do is format the data. then install the rmm state prenormal and bypass files and only then install magisk or a custom rom.
Click to expand...
Click to collapse
https://youtu.be/UOACi_sUDQY
do only steps 1, 4, 5, 6, 7, and 8 of the video description.
Will be all right!
Marius.Banderas said:
Thank you. I've tried 3 times now as I am getting stuck at II. Flash TWRP and fix rom. After I flash the nougat rom via TWRP, phone reboots and the logos keep on looping. Either I am doing something wrong or I'm missing a step, or the zip is not working for my mom's phone.
Click to expand...
Click to collapse
Before trying to flash TWRP, first flash a full stock firmware and make sure your can at least boot all the way up to the main screen.
Once that works, only then try to flash any custom recovery or custom rom.
Same prob
I've just faced the same problem a few days after my update as well. Did you figure out how to get it back to normal? Thank you!
uz91 said:
I've just faced the same problem a few days after my update as well. Did you figure out how to get it back to normal? Thank you!
Click to expand...
Click to collapse
that is a drk error
you can modification the stock firmware with 7z program
1. open your stock firmware go to AP file
2. click rename than erase the (.md5)
3. extarct the file
4. find (system) file
5. make a (.tar) file with (7z) program with the that system file
6. flash
7. done