It appears that my LG Flex(sprint) cannot access fastboot..Each time I hit enter (via adb command) the phone reboots and brings me back to the LG logo and the phone's desktop..I'm able to control the phone and the recovery mode via adb, however for some reason I cannot command (via adb) while the phone is in "download mode" whenever the phone is in download mode, adb displays a no device listed..lastly each time I try to push a recovery file, I receive a "permission denied" from adb..curious what are some alternatives to place fastboot and a recovery on the phone? (Btw phone is rooted) Thanks.
If you're on the latest update, they did away with download mode/ fastboot. I guess to stop development for this device. I'm not sure why when that goes against everything OPENHANDSETALLIANCE.COM stands for.
mattwheat said:
If you're on the latest update, they did away with download mode/ fastboot. I guess to stop development for this device. I'm not sure why when that goes against everything OPENHANDSETALLIANCE.COM stands for.
Click to expand...
Click to collapse
Just to be clear you're saying taking the official OTA update from JB to KK. And this did away with download mode/ fastboot is that correct?
If so that's insane.
Not sure about from jb to kk update for Sprint but most other variants lost it on the latest kk
---------- Post added at 12:53 PM ---------- Previous post was at 12:52 PM ----------
The LG Pc suite will still trigger it but manual is a no go
Related
My phone got bricked and I can't go in recovery and I got bootloop right after Samsung logo. I decided to "adb reboot recovery" via ADB. So far so good. Connected my phone via USB.. I followed these steps, but when I get to the step when I must write "adb reboot recovery" ADB says device not found..What should I do? Here are the steps I followed:
1. Go here and download SDK: http://developer.android.com/sdk/index.html
2. Extract it anywhere
3. Run SDK Manager.exe
4. Wait it to load packages
5. Check Android SDK Tools and Android SDK Platform-tools
6. Click Install Packages
7. Exit SDK Manager
8. Turn your phone on and connect it to computer (USB)
9. Now go to sdk folder and right click on platform-tools and click on Open Command Window Here
10. Write adb and press enter
11. Write adb reboot recovery and press enter
12. Wait till phone enters recovery and do factory reset
Help. Thanks in advance
why do you create new threads for all your problems? Probably the USB debugging is disabled. Just take it to the service center.
If i can reset the count and yellow triangle I will take it to the service center..
Well, i think you cannot since you need a booting phone to use triangleaway. What did you do? Why did you brick jena? Have you forgotten those golden rule of jena? Too much coffee is bad for jena. Also too much courage is bad.
sando99 said:
If i can reset the count and yellow triangle I will take it to the service center..
Click to expand...
Click to collapse
did you try to force it in download mode via USB JIG?.
.too bad for you.
I said I can go in download mode, just the phone is soft-bricked.
sando99 said:
I said I can go in download mode, just the phone is soft-bricked.
Click to expand...
Click to collapse
It can be a silly question, but do you have install Samsung Kies/Samsung Driver for Phone?
Whatever u did on pc is perfectly all riight, but from ur mobile side there is no response,
So do something on mobile,..before had u onned usb debugging?..
................................................................................................
---------- Post added 31st March 2013 at 12:20 AM ---------- Previous post was 30th March 2013 at 11:47 PM ----------
Got my point?:beer:
................................................................................................
sando99 said:
I said I can go in download mode, just the phone is soft-bricked.
Click to expand...
Click to collapse
follow the flashing part on my signature.
damn. as long as you can go to download mode it can be fixed by flashing a stock rom via odin.
after you flashed stock rom to your phone enable USB debugging in settings and install the correct drivers so you can use ADB.
Did you solve your problem or did you take your device to the service center? I just experienced this problem too, the device didn't boot into recovery, instead only black screen was on as if it was powered on. In this state, it was not possible to boot into download mode nor perform normal boot. Luckily for me, I could do adb reboot recovery since I was running custom ROM. The device booted in recovery and I could restore backup. I have no idea what could cause this bug, it could be either Samsung's bootloader bug or hardware fault, but I don't know what is triggering it.
Nope, I'm gonna take it to the service center soon. I am running stock 2.3.6 (obviously) and USB debugging is not enabled and it isn't rooted.. soo no way of ADB (tryed on 2 PCs). I'm quite sure that this problem is caused by the downgrading from JB to GB Maybe the partitions are messed up... I really dunno where is the problem.
It has nothing to do with partitions and/or downgrading.
Need help. After wiping and formatting data (like a dummy) I'm stuck on bootloader with no os or backup. When I go into fastboot and enter fastboot devices, nothing shows up. fastboot was working earlier as that is how i unlocked and rooted. When I go into TWRP recovery, I am unable to mount usb. In bootloader it now shows "Tampered" "unlocked". Is there a way for unbricking this? How about adb sideload. How do you do this? I'm still able to get into TWRP. Thanks.
go back into fastboot, plug it into your pc and check device manager and is Android Bootloader Interface there?
adb sideload is an option if you download a copy of a stock rom or whatever rom you want
---------- Post added at 07:50 PM ---------- Previous post was at 07:45 PM ----------
download the stock odexed rom from here: http://forum.xda-developers.com/showthread.php?t=2224752 and sideload it. does TWRP have a sideload option?
Well, anyway, adb sideload doesn't load as it shows as "failed"....I don't see Android Bootloader Interface there. It's like it is not recognizing it is there anymore...
this is why i dont use twrp lol.. last time i used it on my nexus it did weird stuff.
check your cable maybe? usb 3.0 ports have issues sometimes.
the wording tampered and unlocked is normal its on mine and it works fine.
Ok...HTC sync manager was asking for an update when I restarted it and now my device shows up!...flashing now...good luck to me
So I assume it only shows "unlocked" before you root it and then "tampered" after rooting?
Darn, after flash showed complete...stuck on HTC logo screen...try another rom? maybe stock?
Just downloaded the ruu .exe file. does anyone know how to flash this? Thanks.
Run it on your computer it removes your root
Use CWM instead of TWRP. This happened to me and twrp wouldn't allow sideloading. use cwm and sideload using the console.
Great! After everything else failed. This little video did the trick:
http://www.youtube.com/watch?v=1g5gEf2wgS4
I am stuck in a bootloop right now due to being an idiot and performing the OTA after being rooted. Now I cannot hard reset via the power/vol down or the menu of the phone. I am not familiar with adb or command prompts, etc and I don't know what fastbooting means? I have downloaded the adb/fastboot rar and when i click either all they do is zoom through a list of words and close? what do i have to do to get my phone working again?!
I feel your pain!
I am having the same issues! I get about 30 seconds to quickly flick to something before it powers off again. I found that I can keep it powered off and I can get to a boot menu but all of the options cause the screen to go blank then it restarts again. PLEASE help! my phone is my lifeline and it is required for my work!
NovaSS369 said:
I am stuck in a bootloop right now due to being an idiot and performing the OTA after being rooted. Now I cannot hard reset via the power/vol down or the menu of the phone. I am not familiar with adb or command prompts, etc and I don't know what fastbooting means? I have downloaded the adb/fastboot rar and when i click either all they do is zoom through a list of words and close? what do i have to do to get my phone working again?!
Click to expand...
Click to collapse
You both need to use RSD to flash back to stock firmware.
http://forum.xda-developers.com/showthread.php?t=2446515
You DONT have to rsd !!!! Just fastboot erase user cache
---------- Post added at 03:59 AM ---------- Previous post was at 03:55 AM ----------
http://www.droidrzr.com/index.php/t...et-up-adb-and-fastboot-for-your-windows-7-pc/
If you don't know fastboot/adb here is a good guide how to set it up.
got it to do the fastboot, every time i install the update though i get the same viscious cycle :/
Hi all, I did a dumb thing and I took the recent Verizon OTA on my dev ed moto x with a custom recovery installed (TWRP).
Now my phone seems to always stop booting at recovery, then if i hit 'reboot system' from recovery, I can get into my system for about 2-3 minutes, and then it reboots to recovery again.
Any help would be greatly appreciated!
boot your phone into fastboot/bootloader mode, then flash stock Recovery on your phone and reboot normally.
KidJoe said:
boot your phone into fastboot/bootloader mode, then flash stock Recovery on your phone and reboot normally.
Click to expand...
Click to collapse
Thanks KidJoe - I'm reading through your post on xda right now to see how you flash back to the stock recovery and I'm currently downloading the stock image from one of your links.
While I'm waiting, I'm going over my options for how to actually flash the stock recovery - your post said that i should try Rashr - however my device probably won't stay 'on' long enough for me to get through that process. After it boots into the system (e.g. I see my launcher and apps), it wants to restart since I guess it's trying to the upgrade. So I'm thinking of instead using adb to flash the recovery.img file. Is that the right path to take?
Also - would it be okay to use adb to flash the recovery.img using TWRP's adb sideload feature? I seem to be able to connect using adb that way, but for some reason 'adb devices' doesn't list anything under fastboot.
switch81 said:
Thanks KidJoe - I'm reading through your post on xda right now to see how you flash back to the stock recovery and I'm currently downloading the stock image from one of your links.
While I'm waiting, I'm going over my options for how to actually flash the stock recovery - your post said that i should try Rashr - however my device probably won't stay 'on' long enough for me to get through that process. After it boots into the system (e.g. I see my launcher and apps), it wants to restart since I guess it's trying to the upgrade. So I'm thinking of instead using adb to flash the recovery.img file. Is that the right path to take?
Also - would it be okay to use adb to flash the recovery.img using TWRP's adb sideload feature? I seem to be able to connect using adb that way, but for some reason 'adb devices' doesn't list anything under fastboot.
Click to expand...
Click to collapse
First, if you can't boot your phone into Android, you can't use Rashr.
Next... ADB needs you to be up in Android, and have the "USB Debugging" options checked. Also, it can not be used to flash the components of the SBF/ROM like recovery.img.
Fastboot mode works with Fastboot.exe or mFastboot.exe... ADB commands do not work when the phone is in fastboot mode.
Here is what you want to do AFTER you have the stock reocvery.img you want to flash... (this is pretty much exactly what you did to flash TWRP on there in the first place, except you will be flashing a stock recovery.img instead)
have the latest Moto drivers installed. You can get them from -> https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Make sure you have the Android SDK/Platform Tools installed (don't know how, see -> http://mark.cdmaforums.com/ADB.htm )
You need the latest version of Moto's fastboot, and it needs to be put in your windows Path (there are steps on -> http://mark.cdmaforums.com/ADB.htm )
Once you have that... do the following...
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in fastboot menu on phone.
Connect to PC.
open command prompt file and change to the folder you have your recovery.img you want to flash
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery recovery.img
mfastboot reboot-bootloader
The device will display different BOOT OPTIONS
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
The device will display the Motorola logo and then the Android in distress (logo with Exclamation mark)
Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key
You should enter STOCK recovery.
use the VOL DOWN Key to scroll and the POWER Key to select reboot.
The phone should reboot and and be ready for the update
I did the same thing and was able to undo it by clearing the cache. Now I'm back to where I was before, with the constant notification to update.
Wondering what the correct way to go about updating is..
*Edit: Thanks!
Moto X Dev
Thanks! I'm back up and running!
Sorry for the confusion on the adb vs fastboot stuff - I always mix those kinds of things up since I do it once ages ago to get myself into this mess, then I forget how I did it and what tools I used.
So basically what I did was use fastboot like you said and first booted into fastboot, then did a 'fastboot flash recovery recovery.img' from a stock recovery.
After a full reboot, android ended up giving me a 'update was unsuccessful' which I am totally 100% okay with. I ended pushing 'update' the first time really because I was tired of getting nagged - this time i just said 'don't install' and hopefully it won't bother me agian.
Thanks again!
slynke said:
I did the same thing and was able to undo it by clearing the cache. Now I'm back to where I was before, with the constant notification to update.
Wondering what the correct way to go about updating is..
*Edit: Thanks!
Moto X Dev
Click to expand...
Click to collapse
I'm sure KidJoe will respond, but I found this thread of his very useful:
http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079
switch81 said:
Thanks! I'm back up and running!
Sorry for the confusion on the adb vs fastboot stuff - I always mix those kinds of things up since I do it once ages ago to get myself into this mess, then I forget how I did it and what tools I used.
So basically what I did was use fastboot like you said and first booted into fastboot, then did a 'fastboot flash recovery recovery.img' from a stock recovery.
After a full reboot, android ended up giving me a 'update was unsuccessful' which I am totally 100% okay with. I ended pushing 'update' the first time really because I was tired of getting nagged - this time i just said 'don't install' and hopefully it won't bother me agian.
Thanks again!
Click to expand...
Click to collapse
I was able to flash back to stock recovery and take the 212.166.3 build KXA21.12-L1.26-3 (which is still 4.4.4) OTA that Verizon is pushing out.
I didn't even have to disable Xposed or anything else. Then again, other than Xposed, root and twrp, I'm running stock. No tethering hacks, build.prop changes, no system files removed or renamed, etc.
---------- Post added at 01:18 PM ---------- Previous post was at 01:16 PM ----------
slynke said:
I did the same thing and was able to undo it by clearing the cache. Now I'm back to where I was before, with the constant notification to update.
Wondering what the correct way to go about updating is..
*Edit: Thanks!
Moto X Dev
Click to expand...
Click to collapse
Yup., Clearing cache will delete the OTA ZIP file that was downloaded. So the next time you reboot, it wont try to install, instead you'll be back to being notified that an update is available asking you if you want to download it.
But yup, those instructions I just typed should work...
This OTA seems so minimal in changes, any suggestions/recommendations if I should take it at all?
I'm also pretty much stock now as well - only root, xposed installed.
switch81 said:
This OTA seems so minimal in changes, any suggestions/recommendations if I should take it at all?
I'm also pretty much stock now as well - only root, xposed installed.
Click to expand...
Click to collapse
The release notes on VZW's page only seems to mention bug fixes.. no real details.
So far I haven't noticed any changes.
It will likely be a required step to get to lollipop. So either take it now, or wait and take it later, just before you upgrade to Lolliop
I tried going back to stock and now it won't go past fastboot. It won't boot to recovery, it won't start normally. It won't do anything except boot to fastboot.
Update
Got it to start and now I'm trying to remove the verity unlocked text or whatever. When in fastboot every command I give comes back with failed. Remote unknown command.
always6s said:
I tried going back to stock and now it won't go past fastboot. It won't boot to recovery, it won't start normally. It won't do anything except boot to fastboot.
Update
Got it to start and now I'm trying to remove the verity unlocked text or whatever. When in fastboot every command I give comes back with failed. Remote unknown command.
Click to expand...
Click to collapse
Did you go into developer settings and tick the "allow oem unlock" ? And allow us debugging option.
---------- Post added at 05:03 AM ---------- Previous post was at 05:02 AM ----------
I would suggest restoring with the Motorola Lenovo smart assistant rescue tool , it's able to rescue your broken device!
Moto X Pure XT1575 said:
Did you go into developer settings and tick the "allow oem unlock" ? And allow us debugging option.
---------- Post added at 05:03 AM ---------- Previous post was at 05:02 AM ----------
I would suggest restoring with the Motorola Lenovo smart assistant rescue tool , it's able to rescue your broken device!
Click to expand...
Click to collapse
I got it working. IDK what I did but it ended up letting me boot twrp then I restored my backup.