Database Users

Flashed 4.4, got some issues

Hello, I was using the nexus 5 port, but this morning I wanted to install the official 4.4 for the nexus 4. I did everything in CWM, including flashing new radio and bootloader. I rebooted the system but I got a bootloop at the google logo. I went to my pc and downloaded the factory image, and I flashed everything, except the userdata.img. now everything booted fine, but I havent got a lock screen, got no quick settings, apps arent working, ...
Is this because I didnt flash the userdata.img? I didnt want to lose my pictures, but since they are on Google+ I guess I am going to flash everything again.
Could someone confirm this?
Sent from my Nexus 4 using xda app-developers app

jst download the factory image and connect your phone wth the pc and keep ur phone on bootloader and jst follow this steps
http://forum.xda-developers.com/showthread.php?t=2531374
Sent from my Nexus 4 using xda app-developers app

Thibaultvw said:
........
Is this because I didnt flash the userdata.img? I didnt want to lose my pictures, but since they are on Google+ I guess I am going to flash everything again.
Click to expand...
Click to collapse
I flashed to KitKat 4.4 without losing data. I removed the '-w' option in flash-all.bat. This file is in the factory image.
Updated Nexus 4 to KitKat 4.4 with the Google factory image as follows:
The Nexus 4 bootloader must be unlocked.
DOWNLOAD
Download 1: Nexus Root Toolkit v1.7.7: http://www.wugfresh.com/nrt/
Download 2: Factory image 4.4(KRT160): https://developers.google.com/android/nexus/images?hl=de#occamkrt16o
Play Store: Unlock boot: https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
BACKUP
Backup with Nexus Root Toolkit: emulated SDcard. (Just to be sure)
SETTINGS
Nexus 4 Developer options -> USB debugging ON.
WINDOWS PC
On the PC, extract the downloaded factory image: occam-krt16o-factory-75ccae7a
Result is a directory: occam-krt16o, with the following files
bootloader-mako-makoz20i.img
flash-all.bat (must be changed)
flash-all.sh
flash-base.sh
image-occam-krt16o.zip (remove "userdata.img" )
radio-mako-m9615a-cefwmazm-2.0.1700.84.img
Copied to this directory from the Android SDK or Nexus Root Toolkit v1.7.7:
AdbWinApi.dll
AdbWinUsbApi.dll
Fastboot.exe
Edit flash-all.bat: remove the '-w' option after 'fastboot'
FASTBOOT MODE
Switch off Nexus 4. Restart by pressing the lower Volume + Power buttons simultaneously.
TEST USB CONNECTION PC -> Nexus 4
Testing while Nexus 4 is in Fastboot mode:
1. The Nexus screen must show LOCK STATE - unlocked.
2. Test USB-connection: in a dosbox enter the command: fastboot devices
(A message must be shown: '<hex-number> fastboot')
FLASH
After editing. Run the changed flash-all.bat
ROOT
After the flashing 'root access' is gone.
Root the N4 (again) with the Nexus Root Toolkit.
Edit: NEXUS 7 UPDATE
The same method used for updating a Nexus 7 (2012 - Wifi only) with the factory image: nakasi-krt16o-factory-b27054b8.tgz
I did not remove the file "userdata.img".
The updating worked, but the data was lost. The Nexus 7 was updated to Android 4.4 and reset to factory mode.

Need help flashing bootloader. Nothing works!

My wife's Nexus 7 is on the 4.13 bootloader. I've tried to change it before to no avail. I tried to use Wug's kit to flash the latest 4.4.2(coming from the 66Y build) but I got the error on the bootloader flash. So everything got wiped but the bootloader and left an empty device. All attempts to flash after that failed to get past the first line(erasing boot), I guess 'cause it was already erased? I flashed the individual img' s(boot, system, etc) and got the Nexus to boot up into kit Kat 4.4.2, but there is this little glitch in between the "google" splash screen and the boot animation where I can see recovery flash for a split second. I want to flash the proper bootloader and redo the process clean, but for the life of me I can't get the bootloader to take. I flash in Wug's, the same way I flashed the other img's, but fastboot screen still shows 4.13. Adb shows connected but says "offline" next to device, which is making the adb reboot command fail(unless I'm done now something else wrong there). Can anyone help? My wife is not pleased.
Sent from my SCH-I535 using Tapatalk

Your wife is displeased because of a momentary flash of the screen while booting? **
Or maybe she's displeased with the idea of you fooling with her tablet and that's the only straw to grasp at?
You need to say exactly what the error is, not "an error occurred". You can cut-n-paste right here into your posts.
Also, you should verify the checksum (e.g. MD5) of the bootloader image file you are attempting to flash to make sure you are really using a valid bootloader file.
(In particular, the one shipped in the KOT49H = 4.4.2 factory image is corrupted)
Note [WARNING][URGENT] N7 grouper (2012 WiFi) bootloader .img files from Google
Honestly, I would avoid flashing your bootloader unless it was absolutely, positively necessary. It's the riskiest flashing operation that you could possibly perform on your tablet. Unless I missed something, you didn't really indicate anything else was particularly wrong with the tablet.
good luck
** I think I saw a bug report about fleeting screen flashes in KitKat 4.4.2 (you see an "old" screen briefly appear when you are on your way to doing something else; they are quite noticeable because they are "out of sequence"). For instance I've seen my settings screen appear momentarily when I am moving between two running apps. I think I saw this reported as a KitKat bug - not something due to the bootloader.
.

Well, bootloader now says 4.23, but I still get the invalid state error when flashing the latest kit kat img. Is there a way to force request an OTA? The 4.4.2 OTA failed because I was on a custom rom/recovery, but now it seems to say I am up-to-date even if I downgrade. Is there a way to clear the memory or get the OTA to attempt?

How do you flash? Using a toolkit? Fastboot? ADB? On what operating system? What is the error message and at what step does occur?
It's a bit difficult to give suggestions how to solve a problem when one has only little information.
If you have a 4.23 bootloader installed, flashing boot.img and system.img is sufficient to get a running system, I.e.
Fastboot flash boot boot.img
Fastboot flash system system.img
While boot.img and system.img are extracted from the factory image, but without having detailed information ...
Sent from my Nexus 7 using xda app-developers app

I tried to update using Wug's NTK in fastboot. I got an "invalid state" error when it was flashing bootloader during 4.4.2 return to stock process, and that part fails. I've read this problem has to do with the current bootloader. So I flashed back to the V build and everything flashes fine in NTK. But I get the error again trying to flash stock and unroot to 4.4.2. So I flashed just the boot and system img files in NRK and it's running 4.4.2 now, but I can't flash it in Wug's the normal way. I've read others have solved this error but I haven't been able to.
Sent from my SCH-I535 using Tapatalk

jackdubl said:
I tried to update using Wug's NTK in fastboot. I got an "invalid state" error when it was flashing bootloader during 4.4.2 return to stock process, and that part fails. I've read this problem has to do with the current bootloader. So I flashed back to the V build and everything flashes fine in NTK. But I get the error again trying to flash stock and unroot to 4.4.2. So I flashed just the boot and system img files in NRK and it's running 4.4.2 now, but I can't flash it in Wug's the normal way. I've read others have solved this error but I haven't been able to.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
It may be that the file is corrupt, but it could also mean that your usb port is faulty. Try plugging it in on a different usb port.

First suggestion: try to avoid any toolkit
Second suggestion: get familiar with fastboot
Third suggestion: try to use a decent OS, i.e. Linux / OS X
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
First suggestion: try to avoid any toolkit
Second suggestion: get familiar with fastboot
Third suggestion: try to use a decent OS, i.e. Linux / OS X
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I thought I mentioned that I couldn't get adb to reboot into the bootloader because device said "offline" so I couldn't run in fastboot. The toolkit lets you flash in fastboot without using adb so that's how I flashed the system and boot. I'll just leave it the way it is. Seems to run fine and no slow charging issue.
Sent from my SCH-I535 using Tapatalk

Excuse me, but adb and fastboot are two completely different things ...
Btw. You can boot your device into bootloader (fastboot) mode by pressing vol-down + power while booting it.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
Excuse me, but adb and fastboot are two completely different things ...
Btw. You can boot your device into bootloader (fastboot) mode by pressing vol-down + power while booting it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I know that part. But how do you enter the commands after that?
Sent from my SCH-I535 using Tapatalk

[Q] Wugfresh stucks on: send bootloader(1280kb)

Well, i tried to install stock Bootloader, stock recovery and stockrom with wugfresh tool under "Back to Stock", and so thats the problem:
When i try to send the bootloader, it stucks and the tablet posts under the infos on the bootloader screen: FASTBOOT STATUS - DATA00140000.
And thats it. I waited 2 hour, it still stucks on sending bootloader. So i downloaded the Unified Android Toolkit, install the fastboot driver and tick the option to install a new recovery... It still stucks on sending bootloader. In Youtube Videos, i saw, that the sending finished about 0,2 s. Thats 1280kb! Why doesnt work it on my tablet. I had root, but i didnt tick the usb debugging. So when i switch on my tablet, it comes to the bootloader, and its the activated bootloader( i can switch to recovery, reboot bootloader, power off, reboot system,..) and its unlocked. If i reboot into the recovery, it also comes to the activated bootloader. Its also when i tick the reboot system. So what can i do? Is it hardware bricked? Or whats the problem? I have the bootloader version MANTAMF01 and the H/W Version 8. Can anyone helps me?
And yes, i am the Admin on my PC

The problem is the toolkit, just use fastboot
fastboot flash bootloader nameofbootloader.img
And your done
But after doing so you effectively wipe a few of your partitions so then flash recovery and ROM as well, the method on doing so slightly varies depending if your going back to stock or what something custom
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
The problem is the toolkit, just use fastboot
fastboot flash bootloader nameofbootloader.img
And your done
But after doing so you effectively wipe a few of your partitions so then flash recovery and ROM as well, the method on doing so slightly varies depending if your going back to stock or what something custom
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am having the same exact problem, and I tried doing as you said with fastboot, but I still can't receive any files. Any other suggestions? Any help would be greatly appreciated.

funkym0nkee said:
I am having the same exact problem, and I tried doing as you said with fastboot, but I still can't receive any files. Any other suggestions? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Are you trying to return to stock? Download the appropriate factory image (just Google android factory image) extract all and flash with fastboot.
If you want more detailed explanation boot to bootloader and write down all info on that screen, pet me know the os of your PC, and the explain a little more what's wrong, I'm not sure what can't receive any files means. It is often helpful to copy and paste all input/output from cmd/terminal
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Are you trying to return to stock? Download the appropriate factory image (just Google android factory image) extract all and flash with fastboot.
If you want more detailed explanation boot to bootloader and write down all info on that screen, pet me know the os of your PC, and the explain a little more what's wrong, I'm not sure what can't receive any files means. It is often helpful to copy and paste all input/output from cmd/terminal
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just resolved this issue on my own about a minute before your response lol. The problem was that I wasn't using the stock USB cord. Holy cheese and rice, I've been sitting here for the past 5 hours at wits end trying to figure out the problem. My problem was exactly like MrCreeper's, it was just stuck on "sending 'bootloader'" with no progress whatsoever on either PC or tablet. Who woulda thunk the problem was simply that I was using the incorrect USB cord -_- *sigh*
Anyway, thank you for your prompt reply. I did use a few of your tips from your other posts when I ran into other problems trying to flash stock image, so cheers for that!

[Q] Nexus 10 stuck on Google logo

Hi I've done stupid thing for myself:
i tried flashing 4.4.2 stock rom. coming from 4.2 (i think) did the usual format data/cache. then rebooted then it loops on google logo. I can go to recovery mode.

So are you rooted? Custom recovery? Looking to flash stock? What bootloader do you have? Ota flash? Fastboot flash?
Sent from my Nexus 4 using XDA Premium 4 mobile app

Hoygl3n said:
Hi I've done stupid thing for myself:
i tried flashing 4.4.2 stock rom. coming from 4.2 (i think) did the usual format data/cache. then rebooted then it loops on google logo. I can go to recovery mode.
Click to expand...
Click to collapse
Read this fourm I just help this user recover from the same thing!!
http://forum.xda-developers.com/showthread.php?t=2663286

lj50036 said:
Read this fourm I just help this user recover from the same thing!!
http://forum.xda-developers.com/showthread.php?t=2663286
Click to expand...
Click to collapse
demkantor said:
So are you rooted? Custom recovery? Looking to flash stock? What bootloader do you have? Ota flash? Fastboot flash?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
hi i followed all the instruction till CMD and tried typing fastboot
and nothing came up.

This will help
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
This will help
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I still cant get fastboot up. ive used minimal fastboot and/or SDK Package. also changed the path for environmental variables.

So more info will help, usually the more info you give the faster your issues can be fixed
Are you in bootloader mode? I take it your using windows, what version? Has adb or fastboot ever worked before? When you type
fastboot devices
You get nothing? Can you post a screen shot of terminal, of environmental variables? Are all proper drivers installed? Does anything pop up in device manager when tablet is plugged into USB while in fastboot, recovery or os? Are you using factory USB cable?
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
So more info will help, usually the more info you give the faster your issues can be fixed
Are you in bootloader mode? I take it your using windows, what version? Has adb or fastboot ever worked before? When you type
fastboot devices
You get nothing? Can you post a screen shot of terminal, of environmental variables? Are all proper drivers installed? Does anything pop up in device manager when tablet is plugged into USB while in fastboot, recovery or os? Are you using factory USB cable?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sorry about that.
im in fastboot mode with power and both volumes pressed. i can also go into recovery mode TWRP v2.5.0.0
also rooted and yes windows 7 64 bit. recovery mode or fastboot mode . it doesnt recognized my nexus.
not sure if i have the right drivers. i cant find any drivers to download for nexus 10
Does anything pop up in device manager when tablet is plugged into USB while in fastboot, recovery or os? - No
and yes im using nexus 10 OEM cable.
i really appreciate the time to help me out with this issue.

Its no problem,
The SDK should have the drivers you need, or you can install the universal drivers made by koush or a number of others as well. Just Google search or a search xda for terms like
Nexus 10 drivers
Universal android drivers
Android naked drivers
You will find many that will work just fine for you
If in cmd you type
fastboot
And you see a list of commands than you know you have it installed
When you type
fastboot devices
And you see your serial number your good, if just a blank line then you need to get tab to communicate, this is most often a driver issue. If you can't find ones that work let me know and I'll link some to you, also you may need to uninstall old drivers and than manually install new ones, windows doesn't always do the best job of picking the correct drivers
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Its no problem,
The SDK should have the drivers you need, or you can install the universal drivers made by koush or a number of others as well. Just Google search or a search xda for terms like
Nexus 10 drivers
Universal android drivers
Android naked drivers
You will find many that will work just fine for you
If in cmd you type
fastboot
And you see a list of commands than you know you have it installed
When you type
fastboot devices
And you see your serial number your good, if just a blank line then you need to get tab to communicate, this is most often a driver issue. If you can't find ones that work let me know and I'll link some to you, also you may need to uninstall old drivers and than manually install new ones, windows doesn't always do the best job of picking the correct drivers
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
finally found the driver that works and now
i get R32D2009DAT
Im assuming thats serial number whats the next step

Google search
Android factory images
Here you will download the correct one, latest manta for the nexus 10
Then extract the contents of the zip
Now if you want to keep custom recovery that's a good idea but if you want KitKat you will need stock or at least update to the newest twrp (as you current one won't flash kk)
So if you want twrp then google search
Twrp recovery manta
And then find the latest image, 2.6.x?
Oh and its a good idea to check md5sum for both the zip from android source and for the recovery image, both will tell you what it should be in download screen and there are many ways to check, just google search
Windows md5
There is both official and none official, I personally use Linux command line and can't recall the name of the program I use for windows off hand
Also note that the following commands will wipe all from tablet, it is good to do this but if there is anything real important back it up first
Now from fastboot, enter these commands
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now find the bootloader image you extracted from the android .zip
fastboot flash bootloader nameofbootloader.img
Now if you want stock find the system image
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
Now find the twrp recovery image
fastboot flash recovery nameofrecovery.img
Here you can boot to new recovery and install superuser or just boot to pure stock, or if you want one of the many great custom ROMs you can boot to recovery and use adb sideload to flash one
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
google search
android factory images
here you will download the correct one, latest manta for the nexus 10
then extract the contents of the zip
now if you want to keep custom recovery that's a good idea but if you want kitkat you will need stock or at least update to the newest twrp (as you current one won't flash kk)
so if you want twrp then google search
twrp recovery manta
and then find the latest image, 2.6.x?
Oh and its a good idea to check md5sum for both the zip from android source and for the recovery image, both will tell you what it should be in download screen and there are many ways to check, just google search
windows md5
there is both official and none official, i personally use linux command line and can't recall the name of the program i use for windows off hand
also note that the following commands will wipe all from tablet, it is good to do this but if there is anything real important back it up first
now from fastboot, enter these commands
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
now find the bootloader image you extracted from the android .zip
fastboot flash bootloader nameofbootloader.img
now if you want stock find the system image
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
now find the twrp recovery image
fastboot flash recovery nameofrecovery.img
here you can boot to new recovery and install superuser or just boot to pure stock, or if you want one of the many great custom roms you can boot to recovery and use adb sideload to flash one
sent from my nexus 4 using xda premium 4 mobile app
Click to expand...
Click to collapse
never mind its fixed
you are the man!
Thank you so much!

[Q] Nexus 7 stuck on Google Logo

Hi guys, hoping someone can help me here.
My Nexus 7 is stuck on the Google logo after trying to update to Lollipop using the Nexus Root toolkit.
It will boot into fastboot with this underneath:
Product name - grouper
Variant - grouper
MW version - ER3
Bootloader Version - 4.23
Baseband version - N/A
Serial Number -
Signing - not yet defined
Lock state - unlocked
I have tried a few things so far like using the root toolkit to root it, using the flash stock & unroot on soft brick setting, it'll download the package etc but when it comes to install them on the device it keeps coming back as failed on everything.
I also tried using the Minimal ADB & Fastboot from this thread here http://forum.xda-developers.com/showthread.php?t=2317790 to erase boot, cache, recovery, system data & user data all which come back as FAILED.
Is my Nexus beyond repair, or is there any chance I can bring it back from the dead.
Thanks :good:

Bandit1988 said:
Hi guys, hoping someone can help me here.
My Nexus 7 is stuck on the Google logo after trying to update to Lollipop using the Nexus Root toolkit.
It will boot into fastboot with this underneath:
Product name - grouper
Variant - grouper
MW version - ER3
Bootloader Version - 4.23
Baseband version - N/A
Serial Number -
Signing - not yet defined
Lock state - unlocked
I have tried a few things so far like using the root toolkit to root it, using the flash stock & unroot on soft brick setting, it'll download the package etc but when it comes to install them on the device it keeps coming back as failed on everything.
I also tried using the Minimal ADB & Fastboot from this thread here http://forum.xda-developers.com/showthread.php?t=2317790 to erase boot, cache, recovery, system data & user data all which come back as FAILED.
Is my Nexus beyond repair, or is there any chance I can bring it back from the dead.
Thanks :good:
Click to expand...
Click to collapse
Why did you try 'erase' commands on flashboot, instead of trying to flash the system/boot/cache and recovery stock partitions from the factory image? (just wondering). I think the problem you have may be that the toolkit failed to flash the bootloader and so the process stopped and didn't flash any other parition? We can't know for sure I think because the stock images bootloaders for grouper are ****ed hard mostly and all of them from 4.3? onwards have the same version 4.23 wrong labeled (source) :S
NEVER USE TOOLKITS, they can mess up the phone hard.. In your case I think you shouldn't have any problem to flash the system/boot/cache and recovery stock partitions from the stock factory image, or at least I'd try that. But do not touch the bootloader whatever you do!!!
Also for 5.0 and onwards you needed the 1.2 version of Minimal ADB and Fastboot, I think, be sure ur not using another one.