I am on my second OTA and my phone gets encrypted during the process. Is there a to update without forced encryption being reactivated on my device? I want to disable encryption so that my N6 runs faster but I don't want to have to wipe my device every time there's a new OTA.
marsdiamond said:
I am on my second OTA and my phone gets encrypted during the process. Is there a to update without forced encryption being reactivated on my device? I want to disable encryption so that my N6 runs faster but I don't want to have to wipe my device every time there's a new OTA.
Click to expand...
Click to collapse
How are you OTA-ing? OTA checks for modified kernel and should fail... You need edited kernel to have forced encryption disabled.
The best way to update would be to fastboot flash the system.img and then flash a matching boot.img wit forced encryption disabled.
I am using the Wug Fresh Toolkit...
But when I flash an image with encryption disabled, won't that wipe my device?
marsdiamond said:
I am using the Wug Fresh Toolkit...
But when I flash an image with encryption disabled, won't that wipe my device?
Click to expand...
Click to collapse
No idea. I suggested using fastboot. If you're using s toolkit, you're on your own. At least from me.
Here is my generic toolkit statement
There's nothing wrong with toolkits themselves.* They can be great, useful tools.* We're not even saying they cause bricks either - though users not understanding things *could* cause one...Toolkits are necessary on many devices, but on Nexuses, the manual steps are very easy.
Ultimately it's fine to use a toolkit but *only* if you already know how to do all these steps manually.* If you do not know how to do that then you should do it manually so that you do know. * The reason for this is if something goes wrong further down the line, we don't want to have to teach you the basics AND tell you what you need to do to fix whatever issue you have.* We just want to do the latter - because teaching someone the basics that they should already know when they are frustrated and panicking is not a good set of circumstances to be teaching under and it is frustrating to us more than you and putting us in that situation is a little bit selfish
rootSU said:
No idea. I suggested using fastboot. If you're using s toolkit, you're on your own. At least from me.
Here is my generic toolkit statement
There's nothing wrong with toolkits themselves.* They can be great, useful tools.* We're not even saying they cause bricks either - though users not understanding things *could* cause one...Toolkits are necessary on many devices, but on Nexuses, the manual steps are very easy.
Ultimately it's fine to use a toolkit but *only* if you already know how to do all these steps manually.* If you do not know how to do that then you should do it manually so that you do know. * The reason for this is if something goes wrong further down the line, we don't want to have to teach you the basics AND tell you what you need to do to fix whatever issue you have.* We just want to do the latter - because teaching someone the basics that they should already know when they are frustrated and panicking is not a good set of circumstances to be teaching under and it is frustrating to us more than you and putting us in that situation is a little bit selfish
Click to expand...
Click to collapse
Do you keep this statement somewhere so you can copy and paste or do you type it out every time?
Evolution_Freak said:
Do you keep this statement somewhere so you can copy and paste or do you type it out every time?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rootSU said:
Click to expand...
Click to collapse
Touché.
rootSU said:
No idea. I suggested using fastboot. If you're using s toolkit, you're on your own. At least from me.
Here is my generic toolkit statement
There's nothing wrong with toolkits themselves.* They can be great, useful tools.* We're not even saying they cause bricks either - though users not understanding things *could* cause one...Toolkits are necessary on many devices, but on Nexuses, the manual steps are very easy.
Ultimately it's fine to use a toolkit but *only* if you already know how to do all these steps manually.* If you do not know how to do that then you should do it manually so that you do know. * The reason for this is if something goes wrong further down the line, we don't want to have to teach you the basics AND tell you what you need to do to fix whatever issue you have.* We just want to do the latter - because teaching someone the basics that they should already know when they are frustrated and panicking is not a good set of circumstances to be teaching under and it is frustrating to us more than you and putting us in that situation is a little bit selfish
Click to expand...
Click to collapse
rootSU...Thank you for you candid response. I do agree with you. I should know how to manually control my device. I bricked (no OS found) my N6 with my first lollipop OTA update using the toolkit. I looked up some manual instructions to flash the OS back to my device. I would have, but my third attempt/configuration with the toolkit I got it back. I plan on learning how to manually maintain my N6. Do you have a link to a thread that you suggest to get me started?
Also, if I manually flash OTA updates, is there a way that I can keep my encryption disabled? That is currently my biggest problem. Each time I update with the toolkit it re-encrypts my phone during the process.
marsdiamond said:
rootSU...Thank you for you candid response. I do agree with you. I should know how to manually control my device. I bricked (no OS found) my N6 with my first lollipop OTA update using the toolkit. I looked up some manual instructions to flash the OS back to my device. I would have, but my third attempt/configuration with the toolkit I got it back. I plan on learning how to manually maintain my N6. Do you have a link to a thread that you suggest to get me started?
Click to expand...
Click to collapse
Just go to General > Sticky Roll-up thread.
All "important" threads are there.
marsdiamond said:
Also, if I manually flash OTA updates, is there a way that I can keep my encryption disabled? That is currently my biggest problem. Each time I update with the toolkit it re-encrypts my phone during the process.
Click to expand...
Click to collapse
You cannot flash OTA if you have any customisations in the ROM or kernel and if you're unencrypted, you have a custom kernel.
If you're wishing to stay rooted or unencypted, you should either install a rom.zip, custom kernel and SuperSU from custom recovery or download the factory image and fastboot flash the system.img, a custom kernel (recovery or fastboot) and SuperSU (recovery)
Related
Hi guys, I just managed to pull the stock firmware image off the Sprat, with the assistance of @Dees_Troy. We've been working on this for a few days. Lots of highs and lots of lows. Lots of hardware glitches, device overheating, reading kernel logs to troubleshoot problems... And you know what? All of it could have been avoided if Samsung had released a stock image.
Without any further ado, though, you can find a factory image for this device here: https://builds.casual-dev.com/index.php?dir=random/sprat/
Here is the first custom kernel created for this device. It's mostly dees troy's work, he compiled it and made it operate, but I had to reimage it a few times to make it operate properly. If you absolutely need root for checking something out right now, you can fastboot boot this image and get it.
If you'd like to pull your OWN firwmare including the EFS(serial info) for the device, you can use this command in adb root shell after booting the above image.
Code:
cd /dev/block/platform/msm_sdcc.1/by-name;
f=`ls`;
for f in $x;
do
dd if=$f of=/data/local/tmp/$f.img;
done;
rm /data/local/tmp/userdata.img
exit;
adb pull /data/local/tmp/
the contents of the entire device will come to your computer
now clean up the temp folder.
Code:
adb shell rm /data/local/tmp/*
You now have the firmware above + EFS data.
[rant]
I mean seriously.. Samsung, WTF? I've been working on this for 5 straight days now.
Why did I have to go through the process of keeping this Quad-core watch cool while i tinkered with UART, and continuously rebooted it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Why did I have to wade knee deep in your kernel problems to get this done?
Is it becoming apparent that Samsung doesn't want people messing with their "open devices"? I mean, I can think of no other reason they haven't released a stock image for a device which can be destroyed with a bad flash.
[/rant]
Either way, we finally have a stock image and that means Dees_Troy can release a TWRP, ROM devs can begin working with the system, and those in need of stock firmware now have access to it. Pretty good news if you ask me.
Thank you Adam and I suppose I can speak for every Live owner here when I say we really do appreciate it. I can't wait to start tinkering with it and lets hope we can get that WatchFace API soon. I'm dying for a more sophisticated looking face with a more blue and silver brushed metal look to it. Can't find one anywhere. Thanks again Adam. What would we do without u?
---------- Post added at 09:03 PM ---------- Previous post was at 09:01 PM ----------
Oh and if you add any more green text to your display... just go head on and Follow The White Rabbit....
Sweet Adam, you made a lot of progress since Friday
thanks for all this work! Now to start working on port for Gear 1... Haven't messed with this stuff since HD2 days....Ugh.
Chris
I'd like to get someone to test some TWRP images for me. Need someone that's set up to use adb and fastboot and has basic working knowledge of how to use them. Find me in #twrp on Freenode.
Dees_Troy said:
I'd like to get someone to test some TWRP images for me. Need someone that's set up to use adb and fastboot and has basic working knowledge of how to use them. Find me in #twrp on Freenode.
Click to expand...
Click to collapse
Contacting now.
Dees_Troy said:
I'd like to get someone to test some TWRP images for me. Need someone that's set up to use adb and fastboot and has basic working knowledge of how to use them. Find me in #twrp on Freenode.
Click to expand...
Click to collapse
Incase you missed the link on iirc, http://pastebin.com/5rUD9X0t
Annnnnd this is why i ditched Samsung after the SGSII, Im so glad I got the G Watch instead.
Seems to be a Thing now that Samsung is playing hard to beat with factory images and source, Devs should jump on some form of anti Sammy bandwagon because although this is sure a great feat in hacking but for people here who Crack flash and test stuff for devs on their devices this is a pain and slows down evolution.
if sammy continue with his imagine all the ideas they can't steal from the clever devs here at XDA, I say screw them and buy devices from companies who truly keep android open source
Can this be used in Odin?
Krunk_Kracker said:
Can this be used in Odin?
Click to expand...
Click to collapse
No, it is a fastboot image
How do I actually use this!? Sorry for the noobness haha. I understand I have to unlock my bootloader first, but how do I actually obtain root after I do that? TIA!
Joe0113 said:
How do I actually use this!? Sorry for the noobness haha. I understand I have to unlock my bootloader first, but how do I actually obtain root after I do that? TIA!
Click to expand...
Click to collapse
Hello,
As these are ADB/Fastboot packages, you will need do the following
1) Setup the Android SDK (for ADB and Fastboot)
2) Unlock the bootloader
3) Use the "fastboot boot <filename.img>" (replace this with the location of the extracted content from the zip file)
I honestly would recommend against trying this unless you are a bit seasoned as breakage is possible.
Boot into TWRP
Mount the system
Use the TWRP terminal emulator
rm /system/app/SuperSU.apk
OK so these are the instructions I was given to root. I am currently sitting in TWRP, system was mounted, when I hit reboot system, it told me I wasnt rooted, so I swiped to root...rebooted back to recovery...clicked terminal command which opened up a directory telling me to choose a starting folder :|
this is where im lost.. Also how do I type anything into the terminal commands once I get it open since theres no keyboard lol
Manually removed it using the file manager though its called superuser.apk and it works..Guess im rooted given I can use the rebooter that Adam posted!
KMyers said:
Hello,
As these are ADB/Fastboot packages, you will need do the following
1) Setup the Android SDK (for ADB and Fastboot)
2) Unlock the bootloader
3) Use the "fastboot boot <filename.img>" (replace this with the location of the extracted content from the zip file)
I honestly would recommend against trying this unless you are a bit seasoned as breakage is possible.
Click to expand...
Click to collapse
Do we have to do each individual img? I downloaded the file, extracted it and theres 23 img files lol. I have yet to do anything with a .tar file also
Im debating on returning to stock and taking the watch back to wait for the 360,
Instructions on returning to Stock??
Could someone please post some instructions on returning to Stock? I flash the Octa Rom and did not make a back up and then tried returning to stock by flashing the system.img and it would not boot. I have returned to stock with Nexus devices in the past but looking at the stock firmware image files here I'm not getting how this works. PLEASE HELP
AdamOutler said:
Hi guys, I just managed to pull the stock firmware image off the Sprat, with the assistance of @Dees_Troy. We've been working on this for a few days. Lots of highs and lots of lows. Lots of hardware glitches, device overheating, reading kernel logs to troubleshoot problems... And you know what? All of it could have been avoided if Samsung had released a stock image.
Without any further ado, though, you can find a factory image for this device here: https://builds.casual-dev.com/index.php?dir=random/sprat/
Here is the first custom kernel created for this device. It's mostly dees troy's work, he compiled it and made it operate, but I had to reimage it a few times to make it operate properly. If you absolutely need root for checking something out right now, you can fastboot boot this image and get it.
If you'd like to pull your OWN firwmare including the EFS(serial info) for the device, you can use this command in adb root shell after booting the above image.
Code:
cd /dev/block/platform/msm_sdcc.1/by-name;
f=`ls`;
for f in $x;
do
dd if=$f of=/data/local/tmp/$f.img;
done;
rm /data/local/tmp/userdata.img
exit;
adb pull /data/local/tmp/
the contents of the entire device will come to your computer
now clean up the temp folder.
Code:
adb shell rm /data/local/tmp/*
You now have the firmware above + EFS data.
[rant]
I mean seriously.. Samsung, WTF? I've been working on this for 5 straight days now.
Why did I have to go through the process of keeping this Quad-core watch cool while i tinkered with UART, and continuously rebooted it?
Why did I have to wade knee deep in your kernel problems to get this done?
Is it becoming apparent that Samsung doesn't want people messing with their "open devices"? I mean, I can think of no other reason they haven't released a stock image for a device which can be destroyed with a bad flash.
[/rant]
Either way, we finally have a stock image and that means Dees_Troy can release a TWRP, ROM devs can begin working with the system, and those in need of stock firmware now have access to it. Pretty good news if you ask me.
Click to expand...
Click to collapse
Hi adam i have a Gear Live with Build KMV78Y and when i fastboot boot rootADB.img my device freezes at the bootloader screen and never reboots. i have to adb reboot to get out of it. which is the funny part since i am still on the bootloader screen but adb works. any idea of what is going on here thanks.
Tom
Edit Never Mind i got it just wasnt expecting it to work this way. pretty funny temp root. why not make it perminant root?
Tomsgt said:
Hi adam i have a Gear Live with Build KMV78Y and when i fastboot boot rootADB.img my device freezes at the bootloader screen and never reboots. i have to adb reboot to get out of it. which is the funny part since i am still on the bootloader screen but adb works. any idea of what is going on here thanks.
Tom
Edit Never Mind i got it just wasnt expecting it to work this way. pretty funny temp root. why not make it perminant root?
Click to expand...
Click to collapse
Hiyas Tom..did you really get your Gear?!?!?!
Tower1972 said:
Hiyas Tom..did you really get your Gear?!?!?!
Click to expand...
Click to collapse
yes got it today and working on the Restore Tool like my LG G Watch restore tool. right now its tested and working just cleaning it up
Tomsgt said:
yes got it today and working on the Restore Tool like my LG G Watch restore tool. right now its tested and working just cleaning it up
Click to expand...
Click to collapse
That's the best news I've heard all day!
Tower1972 said:
That's the best news I've heard all day!
Click to expand...
Click to collapse
Samsung Gear Live Tool is up click here and enjoy
hello. I just received the 4.4.4 OTA update, but I have a problem,
I clicked on "update now" and then the phone just shut off. and after it boot, it stuck on this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it's says, "partition (recovery) security version downgraded. fastboot reason boot failure"
so now, every time that I try to boot the phone, it's shut down and go to recovery.
recovery don't work either.
I don't understand why this is happening. the 4.4.2 OTA I received without any problems!
What should I do now? the phone is currently useless.
this is xt1060 model locked bootloader.
Thank you for your help!
ghgh1 said:
hello. I just received the 4.4.4 OTA update, but I have a problem,
I clicked on "update now" and then the phone just shut off. and after it boot, it stuck on this screen:
it's says, "partition (recovery) security version downgraded. fastboot reason boot failure"
so now, every time that I try to boot the phone, it's shut down and go to recovery.
recovery don't work either.
I don't understand why this is happening. the 4.4.2 OTA I received without any problems!
What should I do now? the phone is currently useless.
this is xt1060 model locked bootloader.
Thank you for your help!
Click to expand...
Click to collapse
This is what it appears to me: At SOME point, you flashed a newer firmware than 4.4.2
I believe this because it is the ONLY thing I have EVER seen cause this error. Did you ever flash the 4.4.3 T-Mobile Rom?
It could certainly be something else...never know.
Anyways, find the thread for the 4.4.4 VZW FXZ (in General sub-forum), and simply flash the entire FXZ per the instructions in that thread, OR the Return to 100% Stock thread (also in General sub-forum). The FXZ is a keep-data FXZ, so you won't lose your data. In fact, there is absolutely NO benefit to taking the OTA, over flashing the FXZ. In fact, one could argue (I would...) that the FXZ is superiour in that it can actually FIX a corrupted filesystem (it re-writes all partitions, except /data), while an OTA cannot.
Good Luck, keep us updated.
omanyo4 was
thank you for your reply!
now, after few reboots, the phone showed me a message that the update was unsuccessful and it's stopped to shut off, so I backed up all the stuff that I need.
I'm not sure about the FXZ(what is it mean? is that different than the regular OTA?). is the FXZ erase data?
because if it is, I just can do factory reset and take the OTA in a normal way(I guess)...
edit: I don't care so much about the data. I care about the root - so this is why I'm asking
thanks again
ghgh1 said:
thank you for your reply!
now, after few reboots, the phone showed me a message that the update was unsuccessful and it's stopped to shut off, so I backed up all the stuff that I need.
I'm not sure about the FXZ(what is it mean? is that different than the regular OTA?). is the FXZ erase data?
because if it is, I just can do factory reset and take the OTA in a normal way(I guess)...
edit: I don't care so much about the data. I care about the root - so this is why I'm asking
thanks again
Click to expand...
Click to collapse
Unless your bootloader is unlocked, you will permanently lose root once on 4.4.4 -- you should have known this before you attempted to take the OTA.
FXZ is an acronym for Full XML Zip file and is the format for most dual core Motorola firmware files.
They are an archive of all of the stock partition images for a given device to be flashed in fastboot with either RSD lite or using adb and the fastboot binary.
In contrast to an OTA will only flash successfully if the manifest verifies several files and their checksums, an FXZ can actually REPAIR a corrupted filesystem, and restore all partitions to stock.
This particular FXZ (the 4.4.4 one I suggested that you use) is a "keep data" fxz -- it won't erase your data.
Now tell me how you are / were rooted? Again you should have already known before trying to take the OTA, that 4.4.4 patches all known root-exploits -- if you didn't, then you failed to do your research....
IF (and only if) your bootloader is unlocked, you can re-root EASILY afterwards, by simply flashing TWRP via fastboot, and it will root for you.
Clarify all the questions I've asked you and I might be able to help you proceed....
I did the FXZ method and now the phone on 4.4.4
I lose my root, but I feel that the touch is softer now.
I hope that will be root to the locked bootloader devices.
the good thing is that I didn't lose my data!
Thank you very much, samwathegreat!
moto x 2013
Guys i have the same message i really don't know how to proceed, what to do, what to download... Is there any guide? If yes i'll really appreciate if you can link me something. Thanks
!
Hello, and thank you in advance for any support on my issues. I have done some extensive searching regarding my issues but am coming up empty. I consider myself a relative noob and am now facing multiple questions and issues with my phone.
Device Info:
Verizon LG G2
Rooted, stock
Android Version 4.2.2
Software Version VS98011A
I did not personally root my phone - I paid to have it done for me remotely.
I have been using Titanium Backup to freeze or remove applications and bloat.
I also have used the paid version of ROM Manager for when/if I need it - I have never personally flashed a custom ROM or Kernel, etc.
I did personally side load the HotSpotProvision apk to use the Verizon Hotspot feature with my unlimited data and it worked great.
I also have the Verizon versions of the Galaxy S5 and LG G3. I recently did a 4G LTE speed test with all 3 devices and got insane speeds (attached) with the S5 and G5 but not the G2. I tried researching whether KitKat was the reason for being able to access XLTE speeds or not but couldn't find anything definitive there either. So I decided to attempt the Verizon OTA KitKat update for the G2. Here is where my nightmare begins...
To my knowledge, no backup had ever been done to my phone unless it was done when it was rooted. Regardless, I wanted to do one before making any changes to the phone but I have a feeling I was unsuccessful. After more searches on how to perform a backup and trying 6 times with ROM Manager (unsuccessfully), I decided to try the physical key option to launch into Recovery Mode. Based on what I did find online, this method would take you to the FDR screen but not to worry and to continue because it would actually take you to the TWRP home screen. Well, it did not. My phone reset and I lost everything in my gallery, etc. On reboot, I did see that I was still rooted but not able to do the OTA (because I am still rooted, I assume?). I have done 2 more FDRs and now my phone is acting out of it's mind.
Issues:
Touch screen unresponsive or turning off/on all by itself
Contact info not syncing to native messaging app
Previously installed free or purchased apps not reinstalling (although they did after the first FDR)
Can't receive OTA
At this point, I might as well do whatever I need to do to get things working correctly since I'm already reset.
My questions are:
How can I check if I do in fact have, or don't have a backup that I can access?
How do I create a backup so this doesn't happen again?
What do I need to do to get the OTA and will KK allow me to access the XLTE band?
Can I still do a Factory Data Reset and get back to the true "out of the box" version of the phone? If so, how?
I think that's it for now!! Thanks for any help that can be offered. Cheers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sounds like whoever you paid to root the phone didn't install a recovery or you lost it from applying the KK OTA.
You can install TWRP using Autorec if you're on KK (4.4.2) now.
http://forum.xda-developers.com/showthread.php?t=2715496
Personally I'd start clean to see if it clears up your issues, the touch screen thing sounds more like a hardware problem. If all is well after returning it to stock, re-root it yourself using ioroot/towelroot and install a recovery again and make a back up to save somewhere once you get it set up the way you want it.
http://forum.xda-developers.com/showthread.php?t=2448960
Thank you very much, Matt.
KK never did get installed...I am still on 4.2.2 and every time I try to go back to stock through various methods on this site I get the attached image. I would definitely like to start with the out-of-box device again, OTA KK and re-root but I'm not even having any luck with that either. This whole project began with the thinking that I needed KK to access the XLTE network since I was getting incredible speeds with the G3 and S5...do you know if that is accurate?
mjones73 said:
Sounds like whoever you paid to root the phone didn't install a recovery or you lost it from applying the KK OTA.
You can install TWRP using Autorec if you're on KK (4.4.2) now.
http://forum.xda-developers.com/showthread.php?t=2715496
Personally I'd start clean to see if it clears up your issues, the touch screen thing sounds more like a hardware problem. If all is well after returning it to stock, re-root it yourself using ioroot/towelroot and install a recovery again and make a back up to save somewhere once you get it set up the way you want it.
http://forum.xda-developers.com/showthread.php?t=2448960
Click to expand...
Click to collapse
lantzman said:
Thank you very much, Matt.
KK never did get installed...I am still on 4.2.2 and every time I try to go back to stock through various methods on this site I get the attached image. I would definitely like to start with the out-of-box device again, OTA KK and re-root but I'm not even having any luck with that either. This whole project began with the thinking that I needed KK to access the XLTE network since I was getting incredible speeds with the G3 and S5...do you know if that is accurate?
Click to expand...
Click to collapse
Follow the directions in the return to stock guide provided, see if you can get the phone in download mode...
Install the LG Flash Tool and drivers then try this.
1) Go ahead and put phone in Download mode by VolUp + plug in USB to PC. At this time your computer should install the device, if it hadnt already. Open device manager to check if un der "Ports (Com and LPT)" it shows up as LGE AndroidNet for VZW USB Serial Port (COM##) IF the COM number is anything other than 41, which it probably will be. Right click it in device manager and choose peroperties, then go to port settings tab and click advanced. On the bottom choose COM41 and hit OK. (if you get an error about it being in use I'll write more about that later)
hit ok and all that and close out the properties.
Click to expand...
Click to collapse
OK, I'm on download mode, the computer installed drivers and I changed to COM41. Phone still shows "Firmware Update" screen and 0% on progress. Where do I go from here?
mjones73 said:
Follow the directions in the return to stock guide provided, see if you can get the phone in download mode...
Install the LG Flash Tool and drivers then try this.
Click to expand...
Click to collapse
lantzman said:
OK, I'm on download mode, the computer installed drivers and I changed to COM41. Phone still shows "Firmware Update" screen and 0% on progress. Where do I go from here?
Click to expand...
Click to collapse
Did you unplug and replug in the phone?
I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
mjones73 said:
Did you unplug and replug in the phone?
Click to expand...
Click to collapse
OK, it's doing the OTA!
lantzman said:
I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
Click to expand...
Click to collapse
lantzman said:
I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
Click to expand...
Click to collapse
Yes, returns the phone to out of the box stock basically. Now if you want to re-root, you can use ioroot25 or towelroot.
ioroot25 - http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Once rooted, use autorec to install a recovery (kitkat requires some additional steps besides just flashing a recovery and it does them for you)
http://forum.xda-developers.com/showthread.php?t=2715496
Make sure you grab the vs980 version of autorec.
So I can't create a stock recovery prior to root, correct...so that I can go back to stock from root?
mjones73 said:
Yes, returns the phone to out of the box stock basically. Now if you want to re-root, you can use ioroot25 or towelroot.
ioroot25 - http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Once rooted, use autorec to install a recovery (kitkat requires some additional steps besides just flashing a recovery and it does them for you)
http://forum.xda-developers.com/showthread.php?t=2715496
Make sure you grab the vs980 version of autorec.
Click to expand...
Click to collapse
lantzman said:
So I can't create a stock recovery prior to root, correct...so that I can go back to stock from root?
Click to expand...
Click to collapse
No, you need to root it first if you want to back it up.
OK, so I can root with the Towelroot app and use Autorec for backup. Does it give me TWRP?
mjones73 said:
No, you need to root it first if you want to back it up.
Click to expand...
Click to collapse
and where do I find the process for installing Autorec?
lantzman said:
OK, so I can root with the Towelroot app and use Autorec for backup. Does it give me TWRP?
Click to expand...
Click to collapse
sorry, I was making this way too difficult. I ran Towelroot and Autorec and I believe we are good to go. Now, when would I use Autorec...when I have an issue flashing other ROMs, kernels, etc?
How do you prefer to receive donations? I really appreciate your help...you've been great!
lantzman said:
sorry, I was making this way too difficult. I ran Towelroot and Autorec and I believe we are good to go. Now, when would I use Autorec...when I have an issue flashing other ROMs, kernels, etc?
How do you prefer to receive donations? I really appreciate your help...you've been great!
Click to expand...
Click to collapse
Autorec is a one and done, you can remove it now, it installs TWRP, that's all you need it for. You should now be able to get into recovery using the same sequence you used before if it installed clean for you. Any flashing of rom, kernels, etc would be via TWRP.
One last note, don't install any OTA's while you're rooted.
You don't have to donate anything but if you really want to, just hit the Donate to Me button under my name.
OK, thank you. One last question: it seems the touch screen may be starting to fail. If I needed to unroot or at least show unrooted to turn it in for a warranty replacement, can that be done and if so, how?
lantzman said:
OK, thank you. One last question: it seems the touch screen may be starting to fail. If I needed to unroot or at least show unrooted to turn it in for a warranty replacement, can that be done and if so, how?
Click to expand...
Click to collapse
This will get you back to stock. Make sure you read the first page before you do this...if needed. FYI: Device needs to be off to get into download mode and you should be in download mode before installing the drivers. http://forum.xda-developers.com/showthread.php?t=2448960
Sent from my XDABBEB VS98025A v2.0.0 using XDA free mobile app
Perfect, that's the process I just did from root so I could get the KK OTA. Just wasn't sure if there was an easier way to just show "unrooted" in "about phone" before having them look at it. Love your call sign/avatar. Huge Huge Huge Zeppelin fan here! Ever since hearing "Stairway" in 7th grade! Mght need to see if "LantZeppelin" is available! Thanks again.
All I know is that the wugfresh nexus root toolkit is the way to go. I discovered that windows application early on in my Nexus 5 ownership and haven't looked back. Sure, back in the day I would SDK and ADB and root and rom when it was cool and almost mandatory to bring in the cutting edge features on my incredible and galaxy nexus but there's just no need for it anymore with Lollipop having all the must-haves. And with the toolkit all I did was fire it up and the app put my N5 to sleep, poured it some warm milk, and rubbed its belly until it purred. 5 minutes later I'm up from 5.01 to 5.1 and I still have root, TWRP, and didn't even have to lose my ex-girlfriends phone number with a wipe. It even pre-downloaded 5.1 for me and checked md5. I really can't say enough good things about how painfree it is. Essentially 1 click.
If no-wipe turns out to be crap, I'll just click the OTHER button and be good to go. Thanks WUG!! You ROCK!
So far so good on the dirty flash...
What are you looking for? Validation? An argument? Validation through argument? Help me out here.
Wakamatsu said:
What are you looking for? Validation? An argument? Validation through argument? Help me out here.
Click to expand...
Click to collapse
Hahah, you're right. I was just sharing the solution. When the last update came out everyone who had root/custom recovery was freaking out and having issues with upgrading and they had all these how-to threads, etc. Wug's application is just so easy. And I wanted to poll to see how many people are using a toolkit vs. ADB.
rabaker07 said:
Hahah, you're right. I was just sharing the solution. When the last update came out everyone who had root/custom recovery was freaking out and having issues with upgrading and they had all these how-to threads, etc. Wug's application is just so easy. And I wanted to poll to see how many people are using a toolkit vs. ADB.
Click to expand...
Click to collapse
Probably some people are like me and prefer doing it the tough way by flashing files manually, instead of using a tool kit.
Wugfreshes toolkit is the best. As you probably know most of the senior pple discuss and ridicule toolkits. I've never had trouble with his.
ADB is hassle if you are new. We all know driver issues. Thats a nightmare b4 you even start. I've since learnt ADB commands but still would only use it as a last stop. It was the toolkit that found and loaded the driver allowing ADB.
To be honest I think, subconsciously, ADB users see them selves as superior to the rest of us.
I'm happy with the years Rug fresh has been there for me. The tool updates automatically.
Sent from a Toolbox rooted and flashed phone
Sent from my Nexus 5
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But seriously:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
boot into custom recovery
flash SuperSU/other stuff if desired
isn't that hard.
Driver issues? If you had driver issues your toolkit wouldn't work either. All it does is literally the above—if that is so hard, then maybe you shouldn't modify your device.
Also, ADB ≠ fastboot, they are separate binaries and have a completely different purpose.
@Elluel
Agreed. Just to notice you - Wug's Toolkit recognize ADB or fastboot by itself.
@rabaker07
Was using Wug's Toolkit for a long time. But I don't prefere anymore that app itself take so much space and not necessary files on my PC. So this is much better solution: @rootSU http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
@zerosum0
To be honest. Yes, there are people that feel superior at XDA. But hey, they have reasons.
Problem is, that if you got a bootloop or something like that, its very hard to help people, because they actually don't know what they were doing with their phones before that happened. And if they are also yellers then we got to much threads here like "OMG, please help. :crying:"
I got the drivers on my computer with the kit,after trying everything. That did it in seconds. I do take notice and have written all the commands needed should something go wrong and no toolkit.
A lot of people just are not computer literate.
If push comes to shove I could do it that way but say I want to flash a factory image. The toolkit fetches it, after sorting out the connection between phone and computer. It then flashes it, with a step by step account. Quick and simple. I've never had trouble with it. Toolkits have come along way and I guess there are bad ones out there. Horses for courses. And if someone screws up with a toolkit OR ADB. They should eat humble pie before asking for help.
Sent from my Nexus 5
rabaker07 said:
All I know is that the wugfresh nexus root toolkit is the way to go. I discovered that windows application early on in my Nexus 5 ownership and haven't looked back. Sure, back in the day I would SDK and ADB and root and rom when it was cool and almost mandatory to bring in the cutting edge features on my incredible and galaxy nexus but there's just no need for it anymore with Lollipop having all the must-haves. And with the toolkit all I did was fire it up and the app put my N5 to sleep, poured it some warm milk, and rubbed its belly until it purred. 5 minutes later I'm up from 5.01 to 5.1 and I still have root, TWRP, and didn't even have to lose my ex-girlfriends phone number with a wipe. It even pre-downloaded 5.1 for me and checked md5. I really can't say enough good things about how painfree it is. Essentially 1 click.
If no-wipe turns out to be crap, I'll just click the OTHER button and be good to go. Thanks WUG!! You ROCK!
Click to expand...
Click to collapse
Thank you for sharing your experiences
Glad it worked for you
Thread closed
For some reason my Pixel 4XL got stuck on the "G" screen. I realize this means I'm probably going to have to reset my phone, but I really need to recover the photos and videos that are on it. I know, I know, I need to back-up regularly. But I didn't, and now my kid has no digital memories of his pet that died last weekend. I followed some instructions posted by "Techno Bill" a few years ago to sideload an OTA image onto the phone, and everything went very smoothly, but when I re-booted the phone, it is still stuck on the G screen. The first time I got a "No error" error (...?),so I checked for a more recent version of the image and found one. Tried that one twice, seemed like it worked both times, but both times I was still stuck on the G screen. I'm wondering if its because I already had *210305.006* on my phone, which is the one I'm trying to sideload. Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ChrisH78 said:
For some reason my Pixel 4XL got stuck on the "G" screen. I realize this means I'm probably going to have to reset my phone, but I really need to recover the photos and videos that are on it. I know, I know, I need to back-up regularly. But I didn't, and now my kid has no digital memories of his pet that died last weekend. I followed some instructions posted by "Techno Bill" a few years ago to sideload an OTA image onto the phone, and everything went very smoothly, but when I re-booted the phone, it is still stuck on the G screen. The first time I got a "No error" error (...?),so I checked for a more recent version of the image and found one. Tried that one twice, seemed like it worked both times, but both times I was still stuck on the G screen. I'm wondering if its because I already had *210305.006* on my phone, which is the one I'm trying to sideload. Any ideas?
View attachment 5253543
View attachment 5253545
Click to expand...
Click to collapse
Are you rooted? Did you ever enable usb debugging in developer settings?
Tulsadiver said:
Are you rooted? Did you ever enable usb debugging in developer settings?
Click to expand...
Click to collapse
I'm not, I haven't rooted a phone since my first gen Galaxy, haha. The only things I've done so far are in this instruction (https://drive.google.com/file/d/0Bz6x7k-VkpUJMlZ1aEliVnhMOHM/view). Installed ADB, Fastboot, and necessary drivers. Downloaded an OTA file from developers.google.com, and installed it using the "Apply Update from ADB" option in the recovery menu. My biggest concern is the data. If I can get those photos and videos off I'm perfectly happy nuking the install afterwards and going back to stock. Would rooting it wipe the data?
ChrisH78 said:
I'm not, I haven't rooted a phone since my first gen Galaxy, haha. The only things I've done so far are in this instruction (https://drive.google.com/file/d/0Bz6x7k-VkpUJMlZ1aEliVnhMOHM/view). Installed ADB, Fastboot, and necessary drivers. Downloaded an OTA file from developers.google.com, and installed it using the "Apply Update from ADB" option in the recovery menu. My biggest concern is the data. If I can get those photos and videos off I'm perfectly happy nuking the install afterwards and going back to stock. Would rooting it wipe the data?
Click to expand...
Click to collapse
Yes, you have to unlock the bootloader and that wipes the data. Your phone would have to be able to boot up for that to happen. Just wondering if you flashed something that didn't agree with your phone. Without usb debugging enabled, I don't know a way to pull anything off.
ChrisH78 said:
For some reason my Pixel 4XL got stuck on the "G" screen. I realize this means I'm probably going to have to reset my phone, but I really need to recover the photos and videos that are on it. I know, I know, I need to back-up regularly. But I didn't, and now my kid has no digital memories of his pet that died last weekend. I followed some instructions posted by "Techno Bill" a few years ago to sideload an OTA image onto the phone, and everything went very smoothly, but when I re-booted the phone, it is still stuck on the G screen. The first time I got a "No error" error (...?),so I checked for a more recent version of the image and found one. Tried that one twice, seemed like it worked both times, but both times I was still stuck on the G screen. I'm wondering if its because I already had *210305.006* on my phone, which is the one I'm trying to sideload. Any ideas?
Click to expand...
Click to collapse
At this point you may be lucky to recover your phone at all. It would be helpful to know how you got to this point. You started with the "rescue ota" method which is the last ditch effort for most to reflash a phone with a locked bootloader. Knowing what happened beforehand would be useful information. Since you have flashed the full OTA numerous times via ADB, the only thing left is a factory data reset. At some point you will have to abandon the data and move to the next step in recovering your phone. Even if you never intend to root your phone, you should ALWAYS unlock the bootloader so when the **** hits the fan you have more options to save your data. Wishing you a successful recovery.
v12xke said:
At this point you may be lucky to recover your phone at all. It would be helpful to know how you got to this point. You started with the "rescue ota" method which is the last ditch effort for most to reflash a phone with a locked bootloader. Knowing what happened beforehand would be useful information. Since you have flashed the full OTA numerous times via ADB, the only thing left is a factory data reset. At some point you will have to abandon the data and move to the next step in recovering your phone. Even if you never intend to root your phone, you should ALWAYS unlock the bootloader so when the **** hits the fan you have more options to save your data. Wishing you a successful recovery.
Click to expand...
Click to collapse
Thanks for the reply. I basically got here because every Google post I saw said that I was screwed and would be lucky to save my phone, forget about the data. Except for one, and that one told me to go this route. In the future I'll absolutely unlock my bootloader, but just for my own edification, where would have been a good first place to start with a locked bootloader?
v12xke said:
Wishing you a successful recovery.
Click to expand...
Click to collapse
Would the mount /system option be of any use to me?
ChrisH78 said:
Thanks for the reply. I basically got here because every Google post I saw said that I was screwed and would be lucky to save my phone, forget about the data. Except for one, and that one told me to go this route. In the future I'll absolutely unlock my bootloader, but just for my own edification, where would have been a good first place to start with a locked bootloader?
Click to expand...
Click to collapse
You would use fastboot to dirty flash a full image, removing the wipe flag (-w) from the flash-all script beforehand. This wipes and replaces the boot partition but leaves your data intact.
ChrisH78 said:
Would the mount /system option be of any use to me?
Click to expand...
Click to collapse
No. Even unlocked and rooted we cannot write to the system partition anymore. Any luck on getting your phone working again?