Nexus 7 (2013) LTE is not coming up - Nexus 7 (2013) Q&A

Hi there,
I had rooted Nexus 7 (2013) LTE with 5.0.2 stack version.
The tablet was rooted with Nexus Root Toolkit. I received notification about new (5.1.0) Android version. Tried to upgrade, but received error message during the installation (Error with android symbol and "!"). Tried to upgrade using Nexus Root Toolkit and got the same problem. Tried to do factory default and after that tablet is not coming up. Get stuck with "Google" and unlocked lock over the black screen. Get rebooted a few times and then "No command" over the android symbol. Open fastboot and tried to restore using Nexus Tool Kit but received error message that "Command not found" (please see the pic). Was able to reformat system and boot partition as well as userdata, but still got the same problem during OS installation...
Please advise...

vadim_se said:
Hi there,
Do not PM me for questions. Next time I'd not reply to PM questions.
I had rooted Nexus 7 (2013) LTE with 5.0.2 stack version.
The tablet was rooted with Nexus Root Toolkit. I received notification about new (5.1.0) Android version. Tried to upgrade, but received error message during the installation (Error with android symbol and "!"). Tried to upgrade using Nexus Root Toolkit and got the same problem. Tried to do factory default and after that tablet is not coming up. Get stuck with "Google" and unlocked lock over the black screen. Get rebooted a few times and then "No command" over the android symbol. Open fastboot and tried to restore using Nexus Tool Kit but received error message that "Command not found" (please see the pic). Was able to reformat system and boot partition as well as userdata, but still got the same problem during OS installation...
Please advise...
Click to expand...
Click to collapse
Hello, first download the latest stock ROM from Google nexus images. Make sure you have the right device image. Use winrar to unzip it . you'll again have a file which you'll need again to extract by selecting rar to extract it. (On PC)
Then download platform tools, and paste them in the folder you extracted.
Click on install.bat or something and it'd run fine.
I'll attach platform tools in a bit or update it with a link. Find platform tools below.
forum.xda-developers.com/showthread.php?t=2415668
Quote me next time if you expect a reply

Hnk1 said:
Hello, first download the latest stock ROM from Google nexus images. Make sure you have the right device image. Use winrar to unzip it . you'll again have a file which you'll need again to extract by selecting rar to extract it. (On PC)
Then download platform tools, and paste them in the folder you extracted.
Click on install.bat or something and it'd run fine.
I'll attach platform tools in a bit or update it with a link. Find platform tools below.
forum.xda-developers.com/showthread.php?t=2415668
Quote me next time if you expect a reply
Click to expand...
Click to collapse
Thank you for your answer.
I've unzipped platorm tools and the Android latest release. There is no install.bat or anything like that. When I'm trying to run any of adb commands (adb reboot bootloader, for example) I receive error message that device can't be found. However, Nexus Root Tool is able to reboot device.
Please advise...

vadim_se said:
Thank you for your answer.
I've unzipped platorm tools and the Android latest release. There is no install.bat or anything like that. When I'm trying to run any of adb commands (adb reboot bootloader, for example) I receive error message that device can't be found. However, Nexus Root Tool is able to reboot device.
Please advise...
Click to expand...
Click to collapse
Are you on unlocked boot loader? Do you have all the drivers installed from wugfresh tool kit?
Read this guide but you'll need nexus 7 2013 lte image
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312

Hnk1 said:
Are you on unlocked boot loader? Do you have all the drivers installed from wugfresh tool kit?
Read this guide but you'll need nexus 7 2013 lte image
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Click to expand...
Click to collapse
Hnk1,
Thank you very much. Sorry for PM. I've manually flashed all partitions using fastboot command and the tablet came back up. It is locked now and I'm not sure if I want to unlock it since the only rooted components I was using were application restart blocker and TB.

vadim_se said:
Hnk1,
Thank you very much. Sorry for PM. I've manually flashed all partitions using fastboot command and the tablet came back up. It is locked now and I'm not sure if I want to unlock it since the only rooted components I was using were application restart blocker and TB.
Click to expand...
Click to collapse
I'm glad everything is working fine. Unlocked boot loader isn't a problem at all. All of my devices are developer unlocked . So it isn't a problem if you like flashing/changing Roms.
Just keep it as you feel comfortable. If you have any other queries /questions, quote me and I be glad to answer your questions.

Related

can someone help me update without losing root?

ok, i recently got galaxy nexus.
it took me 6 hours to unlock it and root it. (yes i'm a total noob.. i followed the guide exactly but my computer won't install the drivers and took me more than 10 tries to finally do it).
so my nexus is rooted and running 4.0.2 NON yakuju build.
now i want to update to 4.0.4 yakuju build without losing root.
what's the simplest idiot-proof method of doing this?
i searched all over but couldn't find a simple guide.
please help me, thank you.
dlxowhd said:
ok, i recently got galaxy nexus.
it took me 6 hours to unlock it and root it. (yes i'm a total noob.. i followed the guide exactly but my computer won't install the drivers and took me more than 10 tries to finally do it).
so my nexus is rooted and running 4.0.2 NON yakuju build.
now i want to update to 4.0.4 yakuju build without losing root.
what's the simplest idiot-proof method of doing this?
i searched all over but couldn't find a simple guide.
please help me, thank you.
Click to expand...
Click to collapse
Geez 6 hours...it takes me no more than 10 minutes to unlock and root. By the way this is a question so next time you might want to stick this in the Q&A threads.
Anyway, if your unlocked you should have a recovery or something on your phone to flash ROMS, I think there is a stock rooted ZIP floating around you can use to update. But use the search and browse the development threads I'm sure you will find something.
---------- Post added at 10:37 AM ---------- Previous post was at 10:31 AM ----------
dlxowhd said:
ok, i recently got galaxy nexus.
it took me 6 hours to unlock it and root it. (yes i'm a total noob.. i followed the guide exactly but my computer won't install the drivers and took me more than 10 tries to finally do it).
so my nexus is rooted and running 4.0.2 NON yakuju build.
now i want to update to 4.0.4 yakuju build without losing root.
what's the simplest idiot-proof method of doing this?
i searched all over but couldn't find a simple guide.
please help me, thank you.
Click to expand...
Click to collapse
Did a search off IMM7k6 and found the following link. Hope that helps. Trust me searching is your friend
http://forum.xda-developers.com/showthread.php?t=1630349&highlight=imm76k
thanks but my phone is not verizon.
i got it from wind mobile... one that needs sim card inside..
is there a guide for wind mobile galaxy nexus?
Just use OTA RootKeeper to backup SU and restore it after you update.
ok i downloaded ota root keeper.
but how do i update to 4.0.4 YAKUJU?
sorry but i need a step by step instruction..
Now that you have the drivers installed, updating to anything should be easy. If you lose root, then just use the GNex toolkit to get it back. Using the toolkit, it should take somewhere around 90 seconds to root your phone.
ok that's good,
but is there a clear step-by-step instruction on how to go from 4.0.2 non-yakuju to 4.0.4 yakuju without losing root?
because all this is pretty confusing to me.
i need a step by step guide... for example:
step 1: go here and download this file
step 2: connect your phone to your pc
step 3: put this file into ...
etc..
dlxowhd said:
ok i downloaded ota root keeper.
but how do i update to 4.0.4 YAKUJU?
sorry but i need a step by step instruction..
Click to expand...
Click to collapse
If you want to switch to yakju 4.0.4, see here.
If you want to update your non-yakju build to 4.0.4, see if the update is available here.
To root, after either method (given your bootloader is unlocked), follow method 1 here.
thank you efrant,
so if i understand correctly, i should follow your 2nd link and just skip the 1st link, right?
and how do i find out what version mine is?
i know it's not official yakju but i don't know if it's yakjuxx or yakjukkk or something else.
dlxowhd said:
thank you efrant,
so if i understand correctly, i should follow your 2nd link and just skip the 1st link, right?
Click to expand...
Click to collapse
No, that's not what I was saying.
I was saying if you want to convert to yakju, follow the first link. You will be on yakju and 4.0.4. I would recommend this.
If you do not want to switch to yakju (i.e., you want to keep your current non-yakju build), then see if the 4.0.4 update is available for your build in the second link.
dlxowhd said:
and how do i find out what version mine is?
i know it's not official yakju but i don't know if it's yakjuxx or yakjukkk or something else.
Click to expand...
Click to collapse
Look in this file and see what it says: /system/build.prop
ok,
i definately want yakju so i will follow the 1st link and ignore the 2nd link.
my phone just ran out of battery so i will have to go home first then charge it and try it out!
if i get stuck or screw up, please help me!
thank you so much.
hi,
ok i'm stuck.
i'm doing the part C of your guide.
you said extract the file and there should br 6 files ending with .img.
so i got those 6 files and put them into a folder (i named the folder 'yakju').
but where does this folder go?
do i put this folder onto my phone's sd card? or do i just leave it on my pc (they are inside my 'document' folder).
then your guide says : 8) Open a command prompt in the same directory and do the following:
but where do i open a command prompt?
in C:\android-sdk-windows\platform-tools?
dlxowhd said:
hi,
ok i'm stuck.
i'm doing the part C of your guide.
you said extract the file and there should br 6 files ending with .img.
so i got those 6 files and put them into a folder (i named the folder 'yakju').
but where does this folder go?
do i put this folder onto my phone's sd card? or do i just leave it on my pc (they are inside my 'document' folder).
then your guide says : 8) Open a command prompt in the same directory and do the following:
but where do i open a command prompt?
in C:\android-sdk-windows\platform-tools?
Click to expand...
Click to collapse
Everything stays on your PC. You need to put the files from the attachment in the same folder as the .img files. Then you open a command prompt in THAT directory.
Did you read the whole post before starting like it was stated at the beginning?
Sent from my Galaxy Nexus using Tapatalk 2
ok i open the command prompt in that directory and when i type 'fastboot devices', it says 'fastboot is not recognized as an internal or external command, operable program or batch file'.
dlxowhd said:
ok i open the command prompt in that directory and when i type 'fastboot devices', it says 'fastboot is not recognized as an internal or external command, operable program or batch file'.
Click to expand...
Click to collapse
That's probably because you didn't unzip the files in the attachment into the same directory.
Sent from my Galaxy Nexus using Tapatalk 2
ok, i followed your download link, and downloaded 'Factory Images "yakju" for Galaxy Nexus "maguro"'
then i got 'yakju-imm76i-factory-8001e72f.tar' file... but your guide says .tgz file?
so maybe i downloaded a wrong file.
anyway, then i unzipped it with 7zip and i got this folder called 'yakju-imm76i-factory-8001e72f'
inside that folder, i get this file 'yakju-imm76i-factory-8001e72f' with no file extension.
then i upzipped that file with 7zip and i get this folder named 'yakju-imm76i'.
inside that folder, i have bootloader-maguro-primela03.img, flash-all.sh, flash-base.sh, radio-maguro-i9250xxla02.img and image-yakju-imm76i.zip.
so i unzip image-yakju-imm76i.zip and i get this folder called image-yakju-imm76i and inside that folder i have 5 files : userdata.img, android-info.txt, boot.img, recovery.img, and system.img..
so where do i open a command prompt?
right now my folder structure/tree looks like this:
libraries -> documents -> yakju-imm76i-factory-8001e72f -> yakju-imm76i-factory-8001e72f~ -> yakju-imm76i -> image-yakju-imm76i
ok i think i may have found the problem.
your guide says: '2) Download the attachment from this post and extract the contents to the directory created in step 1.'
but there is no actual link.
can you please verify?
Lol. Think of the bright side guys. At least you're not doing it for him. You'd probably be getting calls at 4am. No offense op. First time is the hardest. But after the first the learning curve is easier.
let it be.
hi @rbiter.
can you please verify?
efants' guide says "'2) Download the attachment from this post and extract the contents to the directory created in step 1.''
but there is no actual link... right?
Scroll down and download that. Extract those files, platform tools into the folder you just made. That platform tools will be very important from here on out.
let it be.

[Q] Senior needs help rooted Nexus 7 and lollipop update

Please help and please be kind and patient with this senior citizen.
I have a rooted Nexus 7(2013). It is rooted at 4.4.4.
I saw the released Android updates to lollipop that I want to use and I need help with the procedures as I have to deroot my Nexus 7 first?
I also want to break it down to steps.
I assume that to update to lollipop, I would need to:
Backup using Nandroid
Deroot my Nexus.
Go to the Android site, then update to the latest version of lollipop.
When the upgrade if over, then re-root.
Even, though I was able to root my Nexus 7, I have forgotten many of the specifics.
Please help guide me as I think I need to:
Backup my Nexus 7 – I have both Titanium Backup Pro and Nanroid Backup Pro
Should I use Nandoid Online backup to ensure I can recover?
Nandroid Settings - Please help me with these Nanroid settings aftger selecting Custom Backup.
Backup Name – UTZ Timezone
Type – TWRP or Clockworkmod – I assume I select TWRP
Normal Backup Mode?
Do I select any of Yaffs2 as Tar or Exclude Dalvik Cache, Exclude Google Music Files.I have to admit, I have no idea what Dalvik and Yaffs2 are.
I will move to TWRP backup to my PC because it winds up being about 3gb and I haisve a 16gb Nexus 7.
This is where I get very confused. What exactly do I do and use start the derooting? Should I use the WugFresh(1.99) toolkit?
After derooting, I should NOT restore anything. I do an upgrade of Android to lollipop.
After my Nexus 7 is lollipop, I would need to do a recovery/restore of my Nandroid backup??
I have the following products that might help:
Titanium Backup Pro
Nandroid Backup Pro
BusyBox Pro
SuperSu
Root Checker Basic
NoBloat Free
Thank you for your time, expertise, kindness and patience in advance
Jon
Need a little more information. Understand you are rooted, but do you have custom recovery installed?
You actually don't need to remove the root before you update to lollipop if you use a factory image from Google.
Nexus7 and lollipop
SwoRNLeaDejZ said:
Need a little more information. Understand you are rooted, but do you have custom recovery installed?
You actually don't need to remove the root before you update to lollipop if you use a factory image from Google.
Click to expand...
Click to collapse
This is where I get confused and think that I am overcomplicating things.
I don't know if I have a custom recovery installed? I assume that I would have had to have made one. :crying:
How can I check? In Nanroid?
Can I make a new one?
It is great if I don't have to remove the root to upgrade to lollipop. When I was promoted by Google to update to lollipop, it failed, because I was rooted.
The bottom line is that I want to upgrade to 5.x and want my Nexus 7 rooted. :good:
Please tell me what information you need.
Thank you,
Jon
jolo100 said:
This is where I get confused and think that I am overcomplicating things.
I don't know if I have a custom recovery installed? I assume that I would have had to have made one. :crying:
How can I check? In Nanroid?
Can I make a new one?
It is great if I don't have to remove the root to upgrade to lollipop. When I was promoted by Google to update to lollipop, it failed, because I was rooted.
The bottom line is that I want to upgrade to 5.x and want my Nexus 7 rooted. :good:
Please tell me what information you need.
Thank you,
Jon
Click to expand...
Click to collapse
Alright, so the fact that your Nexus received the prompt to update tells me that you do not have custom recovery installed.
What you are going to want to do (easiest way to update as far as I am concerned) is just flash a factory image from Google. In order to do this, you will need to get your hands on a few things first:
1.) Windows PC/Laptop
2.) Micro USB cable
3.) ADB and Fastboot files (http://forum.xda-developers.com/showthread.php?t=2588979)
4.) Factory Image from Google for Lollipop for the N7 (https://developers.google.com/android/nexus/images - If you have the 2013 N7, get the one that says 5.0.1 (LRX22C) under the heading "Factory Images "razor" for Nexus 7 [2013] (Wi-Fi)")
5.) ADB/Fastboot USB drivers (your Nexus should install them when plugged in while booted to the Bootloader)
Now, download the ADB and fastboot files. Go to that thread, and follow the instructions to install ADB and Fastboot SYSTEM WIDE so that ADB and Fastboot will work from any directory (makes the rest of this process VERY easy). Once you run through that installer, and everything is good, download the system image listed above. Once it is downloaded, go to the directory it was downloaded to, and UNZIP it (right click it and select Extract here, or open the file and select Extract All).
Now, power off your N7, and then power it on, holding VOLUME DOWN. You will be booted into the BOOTLOADER, this is known as FASTBOOT MODE. Now, connect USB cable to the Nexus 7. The computer will probably say "Installing Device Driver Software". Let it finish. Now, press the START button, and in the search box, type CMD. A command window will open up. Type in the following without the quotes: "fastboot devices".
Now it should show something like this:
Code:
List of attached devices
HJFK54HSWE fastboot
If it says nothing, then the drivers are not working. Reply back to this thread, and I will explain how to update the drivers (don't want to confuse you now). Now assuming that everything is working correctly, all you still have to do is flash the 5.0.1 factory image. Close the command window that is open, and go to the directory where you downloaded the factory image. There is a file inside that folder called "flash-all.bat". With the tablet connected and in fastboot mode, double click the flash-all file. That will do EVERYTHING necessary to flash the factory image, and your tablet will reboot in lollipop.
Now, I don't think this will overwrite the root. If it does, and when you reboot, SuperSU or Superuser (whichever you were using before) isn't in your app draw, then reply here, and we will root you up.
"Factory Images "razor" for Nexus 7 [2013]
Why the hell is it named 'razor' in DL area?? This machine is 'FLO', right???
Razor is the name for all 2013 Nexus 7s. From there, you have deb and flo to differentiate between the LTE and Wi-Fi models.
nhizzat said:
Razor is the name for all 2013 Nexus 7s. From there, you have deb and flo to differentiate between the LTE and Wi-Fi models.
Click to expand...
Click to collapse
Actually, Razor is Google's code name for the Flo, and the Deb is the RazorG. Just like the Nexus 9 is the Flounder on XDA and Volantis on the Google image site. There are almost always two code names for Nexus devices (the community code name, and then Google's, just to keep everything as confusing as humanly possible..)
^^ LOL, but how totally stupid. In their own factory images download area, there are SEPARATE download areas for WIFI/LTE... why in God's name don't they use DEB/FLO? -______-

[Q] Lollipop 5.0.2 Update via TWRP

Hi Guys
I am running stock Android 5.0.1 LRX22C on my Nexus 2013 which is rooted and has TWRP installed.
I just got a notification that an update (9.8Mb) to 5.0.2 was available - however when I accept the update & the device reboots - it boots to TWRP?
Do I have to unroot / uninstall TWRP (go back to stock recovery) to be able to update to 5.0.2 or is there an easier way?
Thanks in advance for any help
You don't have to uninstall twrp.. You do have to unroot though.. If you use wugfresh's nexus root toolkit, it's pretty easy.. You just need to backup your important apps /data, and click the unroot /back to stock button. Select which version of Android you are currently running, and it will unroot your tablet. Then go back in and become a developer (settings, about, and tap on the build number 8 times) .. Then go into developer options, and re enable usb debugging.. After that, install the update.. Finally go back into nexus root toolkit, and re root the device... Fairly easy
BSnapp said:
You don't have to uninstall twrp.. You do have to unroot though.. If you use wugfresh's nexus root toolkit, it's pretty easy.. You just need to backup your important apps /data, and click the unroot /back to stock button. Select which version of Android you are currently running, and it will unroot your tablet. Then go back in and become a developer (settings, about, and tap on the build number 8 times) .. Then go into developer options, and re enable usb debugging.. After that, install the update.. Finally go back into nexus root toolkit, and re root the device... Fairly easy
Click to expand...
Click to collapse
Nice one - thanks very much. Not tried the WUGFRESH toolkit as I have always used the MJSkip version - so will give it a whirl
I unrooted (manally.. toolkits.. meh) and did the OTA last night, but just got bloops...
I downloaded the full package and flashed system.img, back up and running.
khaytsus said:
I unrooted (manally.. toolkits.. meh) and did the OTA last night, but just got bloops...
I downloaded the full package and flashed system.img, back up and running.
Click to expand...
Click to collapse
What did you use to flash the system.img? Will Flashify or Odin do it or do you have to hook up to a Windows PC and do it that way?
jellywobbles said:
What did you use to flash the system.img? Will Flashify or Odin do it or do you have to hook up to a Windows PC and do it that way?
Click to expand...
Click to collapse
fastboot for Nexus devices. Always.
khaytsus said:
fastboot for Nexus devices. Always.
Click to expand...
Click to collapse
could you upload the sytem.img file?
keep running on root and no delete any apps after update to this way?
zikario507 said:
could you upload the sytem.img file?
keep running on root and no delete any apps after update to this way?
Click to expand...
Click to collapse
If you download Factory Images 5.0.2 (LRX22G) then you can extract only the system.img from the pack.
You have to flash su.zip
khaytsus said:
fastboot for Nexus devices. Always.
Click to expand...
Click to collapse
Cheers - am in business - now running 5.0.2 & TWRP 2.7.1.1
Have a weird issue - I have made a TWRP backup which I can see in the TWRP folder on my SD card when I use the built in file manager in TWRP.
However - when I boot Android 5.0.2 & use ES File Explorer the TWRP directory on the SD card of the Nexus 7 is not visible.
I have an iMac & when I connect the Nexus 7 to the Mac (using Android File Transfer (special app for Mac) I still cannot see the TWRP directory
How do I make this visible to Android? I need to copy over the TWRP backup to the PC for safe keeping & the free up some space on the Nexus 7.
Thanks
jellywobbles said:
Cheers - am in business - now running 5.0.2 & TWRP 2.7.1.1
Have a weird issue - I have made a TWRP backup which I can see in the TWRP folder on my SD card when I use the built in file manager in TWRP.
However - when I boot Android 5.0.2 & use ES File Explorer the TWRP directory on the SD card of the Nexus 7 is not visible.
I have an iMac & when I connect the Nexus 7 to the Mac (using Android File Transfer (special app for Mac) I still cannot see the TWRP directory
How do I make this visible to Android? I need to copy over the TWRP backup to the PC for safe keeping & the free up some space on the Nexus 7.
Thanks
Click to expand...
Click to collapse
Try this:
SwoRNLeaDejZ said:
Download terminal emulator and run the commands below.
Code:
su
Code:
restorecon -FR /data/media/0
Should be fine after that.
Click to expand...
Click to collapse
jellywobbles said:
Cheers - am in business - now running 5.0.2 & TWRP 2.7.1.1
Have a weird issue - I have made a TWRP backup which I can see in the TWRP folder on my SD card when I use the built in file manager in TWRP.
However - when I boot Android 5.0.2 & use ES File Explorer the TWRP directory on the SD card of the Nexus 7 is not visible.
I have an iMac & when I connect the Nexus 7 to the Mac (using Android File Transfer (special app for Mac) I still cannot see the TWRP directory
How do I make this visible to Android? I need to copy over the TWRP backup to the PC for safe keeping & the free up some space on the Nexus 7.
Thanks
Click to expand...
Click to collapse
Any reason you went with a version of TWRP from six months ago instead of the latest version? http://techerrata.com/browse/twrp2/flo
As for pulling stuff from SD, I have no idea, maybe try the thing someone suggested with selinux (restorecon). I don't use MTP to do any transfers, all of my sd card backup stuff is done using rsync and automated by Tasker.
kilroystyx said:
If you download Factory Images 5.0.2 (LRX22G) then you can extract only the system.img from the pack.
You have to flash su.zip
Click to expand...
Click to collapse
@kilroystyx lrx22g puts me in a boot animation loop and all above versions on my nexus 7 2013. Only 4.4.4 factory image works for me but google play services and store crash. How can I upgrade without being stuck on the boot animation? This is driving me nuts. Tried cleaning cache, factory resets, formatting, etc. Please help! Thanks, Cindy

Problem with "cannot read update.bin" in 4.6.4 to 4.6.3 downgrade

I have 4.6.4 AT&T OS and I want to downgrade to 4.6.3 unlock OS. In recovery mode the phone is connected with computer, I see serial number and "sideload" next, the update.bin file is in ADB folder, but at next step I get the message
"cannot read update.bin" . I run Win 10 on computer, I try also on Win 7, same problem. I downloaded
4.6.3 unlock OS first with Microsoft Edge, it has .zip extension, then downloaded with Chrome it came with .bin extension, neither one work. Any ideas ? Because I ran out.
That sounds confusing and frustrating. Where did you get the .bin from? I downloaded the one linked in this post and had no problems: http://forum.xda-developers.com/showpost.php?p=62768812&postcount=2
You definitely want a .bin file, not a zip (the .bin should be around 1.2gb). There's also the distinct possibility that ADB is improperly installed. If that's the case, there should be more info in that link that will help you.
In my signature, I link to a walkthrough describing everything I did to get my phone downgraded, rooted, etc. Maybe take a look and see if you missed any steps.
munkymack said:
That sounds confusing and frustrating. Where did you get the .bin from? I downloaded the one linked in this post and had no problems: http://forum.xda-developers.com/showpost.php?p=62768812&postcount=2
You definitely want a .bin file, not a zip (the .bin should be around 1.2gb). There's also the distinct possibility that ADB is improperly installed. If that's the case, there should be more info in that link that will help you.
In my signature, I link to a walkthrough describing everything I did to get my phone downgraded, rooted, etc. Maybe take a look and see if you missed any steps.
Click to expand...
Click to collapse
I downloaded 4.6.3 OS from 3-4 diffrent links from forum including that in your post, also direct from amazon. With Microsoft Edge, Internet Explorer the file is downloaded with .zip, no matter the link I used, so I thought that's the problem so I used Mozzila and Chrome, it came with .bin extension. The .bin file seems to be ok, I can open and extract folders and files from it with WinRAR so it's not corrupt.
About ADB, I read before how to deal with it, seems to work correctly, I can connect the phone in windows with phone on, also in recovery mode the phone appear sideload like it should. So at this point I don't no what to do.
markmm said:
I have 4.6.4 AT&T OS and I want to downgrade to 4.6.3 unlock OS. In recovery mode the phone is connected with computer, I see serial number and "sideload" next, the update.bin file is in ADB folder, but at next step I get the message
"cannot read update.bin" . I run Win 10 on computer, I try also on Win 7, same problem. I downloaded
4.6.3 unlock OS first with Microsoft Edge, it has .zip extension, then downloaded with Chrome it came with .bin extension, neither one work. Any ideas ? Because I ran out.
Click to expand...
Click to collapse
Microsoft Edge and Internet Explorer downloaded the 4.6.3 update as a zip file for me also. I've had the same error (cannot read update.bin) once when trying to sideload an update.bin. I never could figure out what the problem was, so I downgraded my phone using Safestrap. It is not recommended that you use Safestrap to update or downgrade your phone, but a few people including me have updated or downgraded their phone with Safestrap without any problems.
You will need to root your phone if you want to use Safestrap for the downgrade:
See Installing Root, Safestrap, CM11 for how to root and install Safestrap on your phone. You do not need to install CM11.
Launch Safestrap and select Install Recovery.
Download the 4.6.3 flashable-stock-image you will need for the downgrade and put the file on your phone.
Power your phone off, then power it back on.
When Safestrap starts, select RECOVERY> Install>
Browse to and select ss_update-fire-phone-35.4.6.3_user_463001620.zip.
Swipe to the right Swipe to Confirm Flash.
When the flash is complete, select Reboot System> CONTINUE>.
If you don’t want your phone rooted, launch Safestrap and uninstall Recovery, launch Kingroot and unroot your phone. I would also do a factory reset.
Edited to add: To unroot Kingroot 4.0, launch Kinguser, tap gear icon> Root authorization settings> Remove Root permission> Clear>. For Kingroot 4.5, launch Kingroot, tap gear icon> Root authorization settings> Remove Root permission> Continue> OK>. Manually uninstall any Kingroot apps that are still installed on your phone.
jack9955 said:
Microsoft Edge and Internet Explorer downloaded the 4.6.3 update as a zip file for me also. I've had the same error (cannot read update.bin) once when trying to sideload an update.bin. I never could figure out what the problem was, so I downgraded my phone using Safestrap. It is not recommended that you use Safestrap to update or downgrade your phone, but a few people including me have updated or downgraded their phone with Safestrap without any problems.
You will need to root your phone if you want to use Safestrap for the downgrade:
See Installing Root, Safestrap, CM11 for how to root and install Safestrap on your phone. You do not need to install CM11.
Launch Safestrap and select Install Recovery.
Download the 4.6.3 flashable-stock-image you will need for the downgrade and put the file on your phone.
Power your phone off, then power it back on.
When Safestrap starts, select RECOVERY> Install>
Browse to and select ss_update-fire-phone-35.4.6.3_user_463001620.zip.
Swipe to the right Swipe to Confirm Flash.
When the flash is complete, select Reboot System> CONTINUE>.
If you don’t want your phone rooted, launch Safestrap and uninstall Recovery, launch Kingroot and unroot your phone. I would also do a factory reset.
Click to expand...
Click to collapse
Thank you for your reply, I read about root/safestrap method but initially I did not want to root the phone.
Now seems to be the only choice, so thank you for info about this.
If you just type "adb devices" on the PC with the phone connected, do you see the phone? If not, then you have a driver issue. If that is the issue, the Amazon Dev. Service "Connecting your device" page may help.
Yes, at adb devices command the phone appear with serial number........ sideload. Appear connected whith phone on, I can copy on it and also in recovery mode after "apply update from ADB" . I belive that's not the problem.
I'm having the same problem. Cannot read update.bin when trying to sideload 4.6.3.
vkramac said:
I'm having the same problem. Cannot read update.bin when trying to sideload 4.6.3.
Click to expand...
Click to collapse
See this post, on how you may be able to correct your problem.
jack9955 said:
See this post, on how you may be able to correct your problem.
Click to expand...
Click to collapse
Thanks for linking this post. Regrettably, it still doesn't work...no worries though
vkramac said:
Thanks for linking this post. Regrettably, it still doesn't work...no worries though
Click to expand...
Click to collapse
I have had the exact same problem when trying to install the 4.6.3 update (cannot read update.bin), I had to use Safestrap to downgrade my phone. When you downloaded the update, was the extension a .bin or a .zip? When you say "it still doesn't work", do mean Safestrap doesn't work as well?
jack9955 said:
I have had the exact same problem when trying to install the 4.6.3 update (cannot read update.bin), I had to use Safestrap to downgrade my phone. When you downloaded the update, was the extension a .bin or a .zip? When you say "it still doesn't work", do mean Safestrap doesn't work as well?
Click to expand...
Click to collapse
I've been trying to do this through stock recovery. The file extension was .bin retrieved from Amazon's website.
I'm not interested in using Safestrap.
vkramac said:
I've been trying to do this through stock recovery. The file extension was .bin retrieved from Amazon's website.
I'm not interested in using Safestrap.
Click to expand...
Click to collapse
Yep. Can't figure this out at all. Most adb commands are working fine. ADB kill-server. ADB start-server. ADB devices. ADB reboot recovery.
Its just the ADB sideload that gets the error. Cannot read update.bin.
I'm starting to think this is WIN 10 ****ing with me.
vkramac said:
Yep. Can't figure this out at all. Most adb commands are working fine. ADB kill-server. ADB start-server. ADB devices. ADB reboot recovery.
Its just the ADB sideload that gets the error. Cannot read update.bin.
I'm starting to think this is WIN 10 ****ing with me.
Click to expand...
Click to collapse
OK, should you find a solution to the "cannot read update.bin", please post how you was able to fix the problem, your fix may help others. From an internet search, I see the most common reason for the "cannot read . . ." error is the file has a double extension of .zip.zip, bin.bin, or bin.zip.
vkramac said:
Yep. Can't figure this out at all. Most adb commands are working fine. ADB kill-server. ADB start-server. ADB devices. ADB reboot recovery.
Its just the ADB sideload that gets the error. Cannot read update.bin.
I'm starting to think this is WIN 10 ****ing with me.
Click to expand...
Click to collapse
Maybe a stupid question- But did you change the name of the downloaded bin file to "update.bin"?
Years later, but maybe it'll help. For me, it was a combo of WIndows and Bitdefender: Under properties of the update file, it said access was blocked due to the file being from another PC - checking the box there and disabling Bitdefender (only one at a time didn't help) solves the issue.
jack9955 said:
Microsoft Edge and Internet Explorer downloaded the 4.6.3 update as a zip file for me also. I've had the same error (cannot read update.bin) once when trying to sideload an update.bin. I never could figure out what the problem was, so I downgraded my phone using Safestrap. It is not recommended that you use Safestrap to update or downgrade your phone, but a few people including me have updated or downgraded their phone with Safestrap without any problems.
You will need to root your phone if you want to use Safestrap for the downgrade:
See Installing Root, Safestrap, CM11 for how to root and install Safestrap on your phone. You do not need to install CM11.
Launch Safestrap and select Install Recovery.
Download the 4.6.3 flashable-stock-image you will need for the downgrade and put the file on your phone.
Power your phone off, then power it back on.
When Safestrap starts, select RECOVERY> Install>
Browse to and select ss_update-fire-phone-35.4.6.3_user_463001620.zip.
Swipe to the right Swipe to Confirm Flash.
When the flash is complete, select Reboot System> CONTINUE>.
If you don’t want your phone rooted, launch Safestrap and uninstall Recovery, launch Kingroot and unroot your phone. I would also do a factory reset.
Edited to add: To unroot Kingroot 4.0, launch Kinguser, tap gear icon> Root authorization settings> Remove Root permission> Clear>. For Kingroot 4.5, launch Kingroot, tap gear icon> Root authorization settings> Remove Root permission> Continue> OK>. Manually uninstall any Kingroot apps that are still installed on your phone.
Click to expand...
Click to collapse
i am facing the same issue but the problem is i cant turn my phone on because it get bricked when i was trying to install MIUI 7 in it. Now it is just stuck to the amazon logo and i tried to do all these stuff to download amazon latest and installing it through adb but in command prompt it says *cannot read update.bin i cant understand what is going over here please help me out to solve this issue or i will not be able to buy a new phone dew to some financial conditions.
hamza said:
i am facing the same issue but the problem is i cant turn my phone on because it get bricked when i was trying to install MIUI 7 in it. Now it is just stuck to the amazon logo and i tried to do all these stuff to download amazon latest and installing it through adb but in command prompt it says *cannot read update.bin i cant understand what is going over here please help me out to solve this issue or i will not be able to buy a new phone dew to some financial conditions.
Click to expand...
Click to collapse
Hi, I found out your computer may block files that appears to be malicious. See this thread for information on how to unblock it.
Got it to work
I was having the same problem. I kept getting the message" cannot read file"
I was able to get it to work by typing "adb sideload" and then dragging the file in the command window right behind "adb sideload". the string will look like this
"PS C:\Users\Ryan\Desktop> adb sideload C:\Users\Ryan\Desktop\update.bin.bin
and then press enter.

LG G3 Root help

Hello, I am running an ATT LG G3 and I have tried every root method and I just can't get past the firmware update stage. I get to the firmware update screen, phone stays on 0%, whatever rooting tool i am using then says that supersu has failed to boot/install/whatever because it has not started within 1 minute. I turn off the phone by taking the battery out and when it boots up I do not have SuperSu. Note, I read somewhere if i get the LED showing a blue and green color then something is wrong? My phone does flash those colors, what should i do.
PS needed info?
ATT LG G3
-D850
-5.0.1
-Note: I also had rooted on kitkat, didnt like it. unrooted and then restored stock lollipop. If that makes a difference
Have you already tried the second method in this thread?...
[GUIDE][ROOT] Newest Root Method for LG devices
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
Make sure to download and extract the New_LG_Root_v0.1_by_dig.zip file from the OP, then open a command prompt w/ admin rights from within the extracted directory.
i also had this problem. i tried every root method but nothing worked.
i found a "solution" that said that you need to go back to stuck (android kit kat 4.4.2) and then try to root.
it worked for me.
some says that there is a problem with rooting lollipop. :-\
hope it will work for you too
@redduc900 yes I have, I have not tried it with admin rights yet tho. I will try it and update you. But I am sure that the same firmware update stuck stage will occur.
Post a pic of the command prompt window open, showing the results after entering each of the commands from the second method of that thread.
Unable to root LG G3 V20T
redduc900 said:
Post a pic of the command prompt window open, showing the results after entering each of the commands from the second method of that thread.
Click to expand...
Click to collapse
I also have problems with this, I have V20T version of LG G3 .
The first method didn't work, i get to where i enter download mode manually, then nothing.
The same goes for the second method. when i get to the point where i use the send_command.exe \\.\com3 < root it tells me that it can't open the port.
I've verified that com3 is used. however the device shows up in the device managare with a warning.
This warning is only shown when the phone is in download mode.
Any help with this is appreciated, could this problem be due to the recent security update by LG?
Perhaps downgrading to a more recent version of lollipop (before the september 2015 update) will enable me to root?
......
I solved the problem by upgrading the drivers. I was running driver version 3.14 but when i upgraded to 4.0 i now got the extra diag device on Com4.
Now i could run the send_command with root. I was not able to run the second command to reboot but insetad i pulled the battery and then booted up.
Now i'm root and everything is good
\Mattias
While in Download mode, and after running the ports.bat script, you're entering the COM port that's adjacent to the \Device\LGANDNETDIAG1 entry? Also make sure you have the latest LG drivers installed beforehand...
http://androidxda.com/download-lg-usb-drivers
Where did you find the version 4.0? perhaps that is also a possible issue
MattiasG said:
I also have problems with this, I have V20T version of LG G3 .
The first method didn't work, i get to where i enter download mode manually, then nothing.
The same goes for the second method. when i get to the point where i use the send_command.exe \\.\com3 < root it tells me that it can't open the port.
I've verified that com3 is used. however the device shows up in the device managare with a warning.
This warning is only shown when the phone is in download mode.
Any help with this is appreciated, could this problem be due to the recent security update by LG?
Perhaps downgrading to a more recent version of lollipop (before the september 2015 update) will enable me to root?
......
I solved the problem by upgrading the drivers. I was running driver version 3.14 but when i upgraded to 4.0 i now got the extra diag device on Com4.
Now i could run the send_command with root. I was not able to run the second command to reboot but insetad i pulled the battery and then booted up.
Now i'm root and everything is good
\Mattias
Click to expand...
Click to collapse
How can i exactly run command prompt with admin privileges if i want to shift + MOUSE2 when i open the command prompt within the directory?
Now i have a new problem, great. When i send the first command nothing even happens.
yes i have usb debugging checked
Here is a screenshot of what I get
imgur.com/
CiWWU1Y
*cant post hyper link due to spam issues on the forum?*
redduc900 said:
Post a pic of the command prompt window open, showing the results after entering each of the commands from the second method of that thread.
Click to expand...
Click to collapse
You can get the latest version 4.0.2 of the LGMobileDriver from LG here...
http://www.lg.com/us/support/software-firmware
... and instead of using Shift+Right-click to open a command prompt from within the directory, type CMD from the Start--> Search field, right-click and select Run as administrator. Then just CD to the directory.

Categories

Resources