My phone is rooted. I got update from motorola. I jumped at it. But after the update the phone wont start. It gives error "No Command". kindly anyone give directions how to recover it????
Are you able to run fastboot?
Yes
Then I would suggest you flash a stock motorola firmware file using ADB/Fastboot, If you need any help with this I could reffer you to some guides or give you some instructions, this of course deletes all your data from the phone.
Related
so I rooted my phone and then had to unroot it because I couldn't use isis, I used RSD lite to put the latest firmware 12.15.15, that I downloaded form Motorola firmwares but the ncfee.access.xml doesn't have the right stuff in there all it say is the instructions and how to write the access. and I cannot find a way to edit the system.img and just edit the file myself. im getting the error isis cannot access the secure element. and does anyone know how to unlock the boot loader, I need a code but the Motorola websites says my phone doesn't qualify. your help is appreciated and this is the site I always got to tho this is the first time im posting . I have droid ultra.
supersailor89 said:
so I rooted my phone and then had to unroot it because I couldn't use isis, I used RSD lite to put the latest firmware 12.15.15, that I downloaded form Motorola firmwares but the ncfee.access.xml doesn't have the right stuff in there all it say is the instructions and how to write the access. and I cannot find a way to edit the system.img and just edit the file myself. im getting the error isis cannot access the secure element. and does anyone know how to unlock the boot loader, I need a code but the Motorola websites says my phone doesn't qualify. your help is appreciated and this is the site I always got to tho this is the first time im posting . I have droid ultra.
Click to expand...
Click to collapse
You CANNOT unlock the bootloader on Ultra, only on Developer Edition Maxx and X. Reflash stock firmware using RSD Lite, clearly something went wrong the first time around. That or try a factory reset. DON'T try to mess with the stock firmware you are flashing, it sounds like that is what you are trying to do, that will cause problems
i​Yachter99. I can't its says I canT downgrade when I try RDS lite to put stock firmware
well turns out it was an isis issue that they had to manually change something , and I got a new sim card its all working now im on 4.4
Hi guys, need some help here. I flashed GPE on my XT1033 because I want to install the OTA update for Android Lollipop. Everything was fine except when sideloading the update file. My command prompt keep saying that my device cannot be found. This is the error message, "error: device not found". I was really confused since I have installed motorola device manager so that my laptop can detect my phone. Do someone know the solution for my problem? I really want the Android Lollipop update. Right now I can only flash it if I want it because I didn't get any OTA update. Sorry if my English is bad.
Hello Android gurus
I tried to find the answer to my problem in the other threads, but I'm still not 100% sure if I should proceed.
. I had rooted xt1032 moto g prior to 5.0.2 OTA that came out yesterday.
I used full unroot with supersu prior to applying the OTA thinking it would be ok. I guess I screwed up, my phone is soft bricked.
I can get in stock recovery but otherwise it is on boot loop and ends up with 'no command'.
I have the moving line problem on the bootloader white screen which seems to imply a diferent version of kernel and bootloader, (which I do not full understand)
.. Which makes we wonder if it is unsafe to flash the stock rom 4.4.4 image of my phone.
And if it is safe, will I be able to update via OTA after that?
What are my options? Thanks in advance!
The moving line issue is probably due to the fact that you have the 41.18 bootloader on your phone.
I also have a Koodo xt1032 with the 41.18 bootloader and was able to flash back to stock Telus 4.4.4. Do not flash stock 4.4.2 as other XDA members have said that flashing 4.4.2 would brick your phone.
I'm checking for OTA updates but I keep getting the message that my phone's software is up to date.
I got the 6.0 update on my stock AT&T G3 a couple of days ago. Now I am looking to root the phone, but I am confused with the rooting method because all existing methods seem to either mention Kitkat/Lollipop, or the D855 unlocked version. What's currently THE way to root an AT&T G3 running stock Marshmallow?
Thanks!
svemprala said:
I got the 6.0 update on my stock AT&T G3 a couple of days ago. Now I am looking to root the phone, but I am confused with the rooting method because all existing methods seem to either mention Kitkat/Lollipop, or the D855 unlocked version. What's currently THE way to root an AT&T G3 running stock Marshmallow?
Thanks!
Click to expand...
Click to collapse
You'll need to downgrade using LGUP
You could always try KingRoot, however I'm not sure if it works on AT&T Marshmallow. I know it worked on the D855 Marshmallow. Worth a shot.
hyelton said:
You'll need to downgrade using LGUP
Click to expand...
Click to collapse
in reading the threads for lg up i'm unable to find the kdz for lp for the d850. i tried following the link to download official from lg firmware site and after inputting my imei it says not yet available...
any help greatly appreciated. TIA
my goal is to either install a custom recovery / rom
or downgrade to stock LP so i can root ... and then recovery > custom rom
edit: a bit of an update. I was able to get into adb and reboot to stock recovery. took a few tries. and ended up having to use adb over network (so i could keep the phone plugged in to wall charger, my pc charges it but i don't think very well so when i'd issue the reboot to recovery command it would start the loop again and i'd have to start over. finally got it to reboot to recovery. but now i'm stuck at trying to issue the fastboot boot <TWRP.IMG>
says "waiting for device" im so confused right now.... i did remember to plug it back into the computer after it entered recovery (lil green android guy with the text "no command" underneath)
plz someone save my ass! its almost 2:30 am here
killerskincanoe said:
in reading the threads for lg up i'm unable to find the kdz for lp for the d850. i tried following the link to download official from lg firmware site and after inputting my imei it says not yet available...
any help greatly appreciated. TIA
my goal is to either install a custom recovery / rom
or downgrade to stock LP so i can root ... and then recovery > custom rom
edit: a bit of an update. I was able to get into adb and reboot to stock recovery. took a few tries. and ended up having to use adb over network (so i could keep the phone plugged in to wall charger, my pc charges it but i don't think very well so when i'd issue the reboot to recovery command it would start the loop again and i'd have to start over. finally got it to reboot to recovery. but now i'm stuck at trying to issue the fastboot boot <TWRP.IMG>
says "waiting for device" im so confused right now.... i did remember to plug it back into the computer after it entered recovery (lil green android guy with the text "no command" underneath)
plz someone save my ass! its almost 2:30 am here
Click to expand...
Click to collapse
Here's your problem, as stated in my back to stock guide AT&T models and the D850 is TOT File only. You won't ever find a kdz because there is not one. You only have a kitkat tot file you can flash.
:crying:
My issue is quite complicated. Please be patient and read on.
Less than a week ago, I bought an LG G3 D855. It wasn't brand new and definitely out of warranty.
It was on the 4.4.2 Os version but I couldn't update it because I couldn't locate the UPDATE CENTER and after some research online, I found out it was because it was rooted. I couldn't find a Supersu application anywhere on the phone anyways but Root checker confirmed that it was rooted.
I downloaded the stock kitkat firmware in a .tot format and I tried flashing using LG Flash Tool for TOT but it failed because "Device version is different"
I checked the Imei online and it stated that the device is a Sprint LS990 but the details embedded in the phone all say it is D855
I checked online and found a couple of posts about this error and one user said he was able to fix it by flashing the actual Sprint .tot with the lg flash tool. I tried that but it didn't work. It still said "Device version is different. Check BIN or dll"
I checked online and found results pointing to a generic .dll file for G3s and I downloaded it but when I used it on the Flash tool, it resulted to an error "CrossDL blah blah"
So I found a Marshmallow kdz file. LGUP won't see my device model so I was able to flash it after editting the software in my build.prop to D85510n.
***I have always changed the port to COM41 in all the steps I used
The LG UP detected my model and it flashed to 100% but got stuck on a bootloop by loading the lg screen, freezing and restarting by it self. It never gets to the homescreen.
I downloaded lollipop kdz reflashed using LGUP in a form of downgrade and it got to 100% and got stuck at the lg screen while trying to reboot.
I redownloaded the stock kitkat rom and used the Lg flash tool but it failed. It said 'PID null IMEI Null"
I used LGUP to reflashed. It came to my understanding that the LGUP can flash both kdz and tot. So it flashed to 100% but got stuck at the lg screen and I have tried all I can but it is stuck. It can go into download tho. I don't know what to do about the IMEI. I don't know if the last flash retrieved it. I don't kniw what to do.
It no longer shows as LGE AndroidNet USB Serial
Please can anyone help me?
I just need my phone to work again. I was stubborn and now I regret it. I should have just stuck to kitkat. I'm so desperate to get my phone working that I wouldn't mind Android Froyo Os if it was ever possible.
PLEASE HELP!!!
I also had some what same problem with my old lg device ... Here's what you can do:-
Download any custom rom of your lg g3 Like Cyanogenmod and flash it via recovery.
Recovery can be stock or custom it doesn't matter.
Remember to wipe dalvik cache and wipe data before flashing the ROM. I did it and my device was working fine.
Remember that first boot
always takes 2-3 mins so be patient.
Sent from my Aqua Trend using Tapatalk