Related
So i got the new 4.3 update notification on my phone today. Eager to get it i started the installation (battery level was about 90%). After a while the installation went into a constant reboot, always went untill halfway of the progress bar and then phone went off and started again to same screen. I knew it was ****ed up so i went into recovery mode but then it starts to do the update again and i got the "ERROR" message. So i went into recovery again and now i get the "NO COMMAND". I was running 4.2.2 with everything stock, device was not even rooted...
Any ideas?
ybuedts said:
So i got the new 4.3 update notification on my phone today. Eager to get it i started the installation (battery level was about 90%). After a while the installation went into a constant reboot, always went untill halfway of the progress bar and then phone went off and started again to same screen. I knew it was ****ed up so i went into recovery mode but then it starts to do the update again and i got the "ERROR" message. So i went into recovery again and now i get the "NO COMMAND". I was running 4.2.2 with everything stock, device was not even rooted...
Any ideas?
Click to expand...
Click to collapse
Unlock your bootloader, and flash the stock 4.3 image manually. Download it from here
https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
After that, you can relock your bootloader if you want.
abaaaabbbb63 said:
Unlock your bootloader, and flash the stock 4.3 image manually. Download it from here
After that, you can relock your bootloader if you want.
Click to expand...
Click to collapse
I've got very basic knowledge of android so i don't really know what to do... I imagine if i flash the stock manually i will lose all my data? Because in that case i might aswell go to the store and ask a new one since i still have my warranty...
ybuedts said:
I've got very basic knowledge of android so i don't really know what to do... I imagine if i flash the stock manually i will lose all my data? Because in that case i might aswell go to the store and ask a new one since i still have my warranty...
Click to expand...
Click to collapse
Ok, if you have a store nearby, go to them. They will fix it properly. With basic knowledge, it's pretty dangerous.
Similar Prob
Hey guys,
I have a similar problem. Tried the upgrade to 4.3 and it stucked.... well now i constantly see the Google-X-symbol and thats all. Tried to unlock the bootloader via developer tools (for later flashing to Stock ROM) but there's no connection. Tried to replug it, etc.
When I start the bootlaoder (via Vol-Down and On-Button) I can choose the options (but recovery is not possible) But hm, the bootloader doesn't seem to be broken.
Can anyone help me? I'm not really a developer (although I work for a software-company) but I already unlocked and rooted devices and I have experiences in changing deep settings.
Help would be great!!! I don't want to sent it to google - I am lost without my S-Phone....
Thanks!
I have a similar issue, I found the update notification on my phone, went ahead with the update and it took ages! The battery was nearly full and the battery fully discharged while it was updating. I was at a friends house so no charger. When I got home I fully charged the phone and switched the phone on and got the nexus cross animation and thats all. I tried to enter recovery mode but got the no command icon.
Any help would be appreciated, I do have experience of rooting and flashing custom roms on my HTC Desire but have not touched the nexus since I got it. So everything on the phone is stock
Heres interesting, My wife tagged me into a facebook post telling peeps my phone was out of order, as she did it, the facebook app on my phone notified me of the tag!! Still got the nexus boot animation showing on the screen!
waynehardy said:
I have a similar issue, I found the update notification on my phone, went ahead with the update and it took ages! The battery was nearly full and the battery fully discharged while it was updating. I was at a friends house so no charger. When I got home I fully charged the phone and switched the phone on and got the nexus cross animation and thats all. I tried to enter recovery mode but got the no command icon.
Any help would be appreciated, I do have experience of rooting and flashing custom roms on my HTC Desire but have not touched the nexus since I got it. So everything on the phone is stock
Heres interesting, My wife tagged me into a facebook post telling peeps my phone was out of order, as she did it, the facebook app on my phone notified me of the tag!! Still got the nexus boot animation showing on the screen!
Click to expand...
Click to collapse
Ha, that's exactly the same issue.... Thank God I'm not the only one (sorry )
I got the "no command" error after my update this morning. My battery was pretty low, but the phone was docked. I just left the phone alone while I came here to investigate, and it eventually rebooted itself. Then it stuck on the loading X for around 5 minutes, but now it is optimizing my apps. Looks like it is going to work after all.
Mine has been on for a while but its not seeming to play. what mkes no sense is that it is switched on in the background but the nexus animation is the only thing it shows
I'm having the exact issue. I got my update notification this morning and it failed, going into an endless loop. I called google and they didn't know what was happening, so they're sending me a new phone. I don't want to wait for the new one, so I'm trying to fix this one still. I can start the bootloader, but I can't get into recovery. Is there a way to correct this through ADB?
justin1701 said:
I'm having the exact issue. I got my update notification this morning and it failed, going into an endless loop. I called google and they didn't know what was happening, so they're sending me a new phone. I don't want to wait for the new one, so I'm trying to fix this one still. I can start the bootloader, but I can't get into recovery. Is there a way to correct this through ADB?
Click to expand...
Click to collapse
When you get to the screen with "NoCommand" on it.
1. Press and hold power button
2. Then once you pressing the power button, press the Vol - Up
Thats it
OrangeNik
Here is the fix for everyone
Ok, I just got off a chat with an Asus rep.
Step 1: Hold the power and volume up/down to get the android with the "start" option
Step 2: Use the volume down to select "recovery mode" It will now power off and power back up with the dead android and "no command" below it
Step 3: While holding the power button TAP, but DO NOT hold the volume up button. You will get an option to wipe all data. Do that.
Blammo the world's problems are solved
LG Nexus 4 E960
Work perfectly for me
Nexus Root Toolkit v2.1.4
I can't post a link because I don't have 10 posts!!!
Hello,
This morning I tried to root my phone so that I can force everything to be moved to a sd card since the storage of the system is low not enough to install apps and to install A mod that is more updated then the current GingerBread OS.
I managed to soft brick the device the rom clearly said e405 obviously the developer has a few bugs anyway I manage to recover from my soft brick by A software 'KDZ' Only issue I have now is when I press volume up on boot I get A notice icon trying to say something (image of the icon is attached below) and when I use ROM Manager to reboot to recovery it will attempt to go there, Instead of going to recovery it goes to A loading page then this erases all my data/apps except SuperUser/Root.
Tried everything and it still does it?
When I use the LG Emergency Software it just goes to a page saying not responding??
Any help and ideas would be grateful so I can fix this issue and move on also im mostly A samsung user and im fairly new to lg.
See thee error message below
Once i get the idea of what the icon is actually trying to say I should be in the right direction.
Thanks,
Spudster
umm
Anyone??
Spudster1 said:
Anyone??
Click to expand...
Click to collapse
Perhaps you can go to ROM Manager, uninstall Recovery, then re-install it?
I don't really know. I'm sorta new to this stuff.
hard reset
Spudster1 said:
Hello,
This morning I tried to root my phone so that I can force everything to be moved to a sd card since the storage of the system is low not enough to install apps and to install A mod that is more updated then the current GingerBread OS.
I managed to soft brick the device the rom clearly said e405 obviously the developer has a few bugs anyway I manage to recover from my soft brick by A software 'KDZ' Only issue I have now is when I press volume up on boot I get A notice icon trying to say something (image of the icon is attached below) and when I use ROM Manager to reboot to recovery it will attempt to go there, Instead of going to recovery it goes to A loading page then this erases all my data/apps except SuperUser/Root.
Tried everything and it still does it?
When I use the LG Emergency Software it just goes to a page saying not responding??
Any help and ideas would be grateful so I can fix this issue and move on also im mostly A samsung user and im fairly new to lg.
See thee error message below
Once i get the idea of what the icon is actually trying to say I should be in the right direction.
Thanks,
Spudster
Click to expand...
Click to collapse
I saw that icon after flashing back to stock rom with KDZ and a hard reset worked for me. Pull the battery, make sure you not connected to USB or charger, then press and hold home key and down volume while you press power on. Release power when you see LG logo, hold the down and home for a while until you see android unpacking a box. It takes about a minute to see this, so you gotta wait for it. The phone reboots or shut downs, don't rememberwhich
reply
kurtstraker said:
I saw that icon after flashing back to stock rom with KDZ and a hard reset worked for me. Pull the battery, make sure you not connected to USB or charger, then press and hold home key and down volume while you press power on. Release power when you see LG logo, hold the down and home for a while until you see android unpacking a box. It takes about a minute to see this, so you gotta wait for it. The phone reboots or shut downs, don't rememberwhich
Click to expand...
Click to collapse
Ok I will try that and let you know if it works in a few hours I gave the phone to my brother for free since I bought A samsung (used to samsungs and love then
Anyway should also mention that when I try to reboot into recovery with rom manager it reboots goes to the loading box thing then it wipes my data Like i said I tried that method in a few hours and get back to you here.
nope
didn't work ;.(
Man go to the screen u have posted the images above , then use KDZ to flash back Man!
This is "DIAG MODE" so select it in KDZ program
So select KDZ file ( download if u have tried urs so far)
No error .. when u click to start upgrade ur phone will apper in emergency mode. Then the KDZ will flash flawslessly
Sent From ... Lg e400 <-- {[Brasilian Here]}
Still didnt work it flash though but still didnt fix the recovery..
These lg are actually useless a simple firmware flash should do the job.
LG staff are also rude to be honest rang up and because I tried to root and I was doing the right thing going back to stock they denied support and hang up without me giving A reply. Glad ive switched back to samsung s4 and Apple IPhone 5C.
Thanks for attempting to help :.)
Hello XDAers,
I am a real noob at rooting or android-related, and a true one voided of any knowledge regarding anything IT- related.
So dear veterans, please go easy on me.
Due to my prior success of rooting and flashing my Nexus 4 successfully a few months back with no issues, I decided to give it a try to flash a custom ROM for my dad's LG Optimus L7 - which seemed an easy task compared to configuring my Nexus 4 - since there was no need for inputting any command lines or any dealing with the abd (using the easy shortcut, that is).
So, I followed the guide here: http://forum.xda-developers.com/showthread.php?t=1906133 ...
I first factory resettled the phone because it was bloated, then applied the "RunMe.bat" from the "What you desire!" folder. (Everything was already backed-up beforehand.) But the process didn't success until I've retried again and again by re-plugging the USB in because the application/PC couldn't detect the phone. In the same time, I was running KDZ_FW_UPD.exe in the background, so unexpectedly for me the phone shut itself and pushed itself to a vividly green emergency screen, then in a few seconds switched back to a screen of purple-white-blue glitches. I had to close KDZ_FW_UPD.exe without knowing what quite happened since it seemed to be the cause and restarted the process with RunMe.bat.
I didn't manage to "Restore" it first due to the fact that the phone stopped responding due to a lag asking for an encryption key. It was lagging so hard and I had to close the cmd around 5 tries while it was processing, but succeeded later on.
And then, to verify whether I've actually suceeded in rooting L7, I installed Root Checker from the Play Store. And again, for the first few tries the program froze on screen for a long period of time due to "system performance", but after rebooting and restarting the app a few times again, the ROOTING proves to be a success. Just to be sure, around this time I've reloaded KDZ_FW_UPD.exe and it suceeded.
So I went to install CWM and ES. CWM for recovery boot and ES for removing pre-installed system apps as the phone was lagging so badly. I've downloaded the CWM restoring(something like ~6.0.28?) first and tried fastbooting immediately right after, but instead of getting the fastboot menu I got a screen emptied in black with these words:
[5020] "Secure booting error"
[5020] "Cause: boot certification verify"
No hard keys could do anything on the presumed "fastboot", and so I had to hard boot again. I thought that it might be due to the lack of memory(checked on ES later on that it was 310~MB/2GB), and so I've used ES to uninstall a lot of system apps which I deemed uneccessary. So I've Googled a bit and it became apparent to me that that I've didn't unlock the device properly, so lurked around and found a file called L7CWM that is supposedly to resolve my problem, but I presume that it's the CWM recovery image that I've installed. So in the end, I didn't bother with it but kept it on tab just in case.
I repeated the same process with CWM again, but this time, the screen was joined with all kinds of flowery glitches. Restarted the device, and it went only downhill: now the Home launcher stayed all pitch black and nothing appeared. I waited a few minutes, but nothing there until the notification bar appeared. The home screen is apparently dead, and so are the menu keys. Switched to Nova Launcher(installed it just in case Home Launcher fails), and still dead. I couldn't access using any of the menu keys and had unusable launchers.
Hopefully I could still access to the settings from my status bar, but when I did, it started crashing immediately.
I've repeated the attempt a few times after restarting the device a few times, but nothing helped. It only got worse that the when the launcher did SEEM to work. It only showed the wallpaper without showing any of the icons/apps. And crashes again.
I could still access to the App menu via the settings, but couldn't open any of them and when I tried to uninstall them, the screen frozes immediately right after I gain access to the page (white page though) and gain this message: "Unfortunately Package Uninstaller Stopped!"
Then I convinced myself that the only thing I could do at the time was to factory reset the phone and then everything would go alright since I've just had to restore the system apps.
But then the black screen of death came right along with it:
"Secure booting error"
It seems that I'm out of luck... ... But just to check if I'm still left with resorts, I've downloaded the L7CWM file online...
... ...but it still didn't help.
So now I'm being left with no other choices other than asking for help. I never really understand what KDZ_FW_UPD.exe does since I had the LG Driver already before installing it, which I presume was for updating the phone to a newer or older version. And too complex tech articles are kind of alien for me.
EDIT(1 hour later): Okay, now I figured out the reason why L7CWM didn't work was because I didn't extract it to the right folder (after double checked via notepad that I was supposed to directly put it into the C:\ drive). Now it worked(?), but then it didn't.
After launching Flash_Bootloader.bat:
This message now appeared on the L7:
"Sorry!"
"SuperSU is not responding.
Would you like to close it?"
"Wait - Report - Close"
and a few minutes later
"Sorry!"
"Unfortunately, SuperSU has stopped."
"Report - OK"
Now I think the bugs till now happened was due to the fact that I've deleted a file that was required for me to launch apps... Now I just need the right fix.
After 5 minutes of screen inactivity the phone restarted by itself, kind of creepy... ...
Flash_Recovery.bat did nothing.
Reboot2Recovery.bat made it reboot but still struck on the same menu.
Nothing seems to be effective via the phone anymore, seems like I have to rely on abd but then again I don't know how... ... My dad is also f*cking pissed off ^ ^;...
__________________________________
I think that I explained the logs pretty precisely in case I missed something... I'll be very very very very very very thankful if someone could tell me what has caused my phone to fail though.
For references, here are the phone's specifications:
Model Number: LG-P705g
Android version: 4.0.3 (Stock)
Rooted:Yes (root checker)
Baseband version: MSM7227A-1-AA
Kernel version: 3.0.8-perf
Build number: IML74K
Software version: V10e-AUG-10-2012
If I don't get the phone fixed to being usable soon I think that I will get butchered real hard... ... Preferably needs a step-by-step guide made for toddlers... ...
remove the battery for 10 seconds,put it back pres VOL+ and VOL - same time and than press the power button.when you feel a vibration press for many times the button wich is down in right,try for many times and maybe it will working :}
Cydes said:
Hello XDAers,
If I don't get the phone fixed to being usable soon I think that I will get butchered real hard... ... Preferably needs a step-by-step guide made for toddlers... ...
Click to expand...
Click to collapse
simple answer for your
just download your stock rom
go to emergency mode
and flash that stock rom
Hi guys, my phone is a LG L7 p705g unlocked, since 2 weeks from now it was working really weird, having lag, performance issues and even random reboots, i didnt care that much because i was using it to call and check whatsapp, after 2 days my whatsapp stopped working and asked me to reinstall it and so i did. I went to the play store, downloaded the app again and it kept saying "Whatsapp has a problem and it needs to be installed again". I tried to download it via .apk and it didn't work either, via whatsapp.com directly through the .apk and then using a file explorer and it didn't work either.
After a while i started to get frustrated and tried to do a hard reset, but guess what, it didn't work, i went through settings->security-> factory data reset, but it didn't work, it was just rebooting and that was it. Therefore i tried via hardware vol- , power and then menu. But it wasnt working either, it was just rebooting as well. My phone had the original KDZ that came from the factory and did a factory reset once, and it worked great that time.
Then i tried to reinstall the software but i couldn't find one that was for my country (venezuela movistar) and i used another one (from here: lg-phone -firmware. com/index.php?id_mod=13 and used the one "39 TFR/TELEFONICA(ECUADOR) V10B LGP705G" because it was the same "v10b" that my phone said so and using KDZ i flashed that firmware, it worked great, it worked for around 15mins or so, but i couldnt install whatsapp, kept saying the same error as before, and then 5mins later, it didn't turn on any more, and it isn't working. Somebody told me that it's a hard brick and it's unfixable, is it true?
PS: I can connect the phone to the PC and it says "FOUND NEW HARDWARE" but it won't turn on, i've tried the same to connect it with emergency mode (vol + vol - and power and then plug) but it isnt working. And my home button is broken, it has like 6 months not working so.. i cant use it in case you need some buttons sequence to be done.
Any idea what could be going wrong and if it's possible to fix it?
Sorry about my really long post and my awful english,
Please help me. I have a Huawei Y625 (a bit more than a year old), it is NOT rooted. I have never attempted to customize it/tinker around with it. I don't even know the exact terminology so I'm sorry if I get something wrong.
Yesterday it suddenly went into a bootloop, it kept saying "DataBackupStart" with a bunch of processes failing.
I held volume down + power button, which opened a menu entirely in Chinese.
I clicked everything on that menu, but those were just some tests, like camera and sound test.
Then I powered it off, held volume down+volume up+power button this time, and it finally got me to recovery mode I think.
I wiped cache, and I wiped all data, which did a factory reset. It was OK with me because I just want it to work.
Then I tried to reboot it, but then it started behaving even worse. It will not turn on until I remove and put back the battery, and then it will vibrate, show the Huawei logo for a few seconds and then turn off again. It never got past that logo, except if I turn on recovery mode.
I found its official stock files, put the 'update.app' in the dload folder on sdcard, then tried to activate that rom in the recovery mode. It says 'error, status 7, installation aborted'. I googled it but I do not understand a thing, I really don't get these tutorials and I don't know what to do about that.
I tried downloading Marshmallow 6.0 version, because I thought maybe upgrading Android would help, but I cannot find any download links that work.
I am out of my mind, I need my phone and nothing I found on the Internet has been helpful. I don't even know how it came to this since I have never even attempted to root my phone! Please help me, thank you. :crying::crying::crying: