Hi, I have built cm code for my nexus 7 wifi model. $OUT directory did not generate any .zip file.I tried to install each image file individually but nexus 7 did not boot it gets stuck on Google text screen.
I issued fastboot -w flashall command also . But still not working.
Someone please tell some method to get my fresh build working.Thanks.
Problem is that i am unable to generate cm<blah>.zip file.
Sent from my Moto G using Tapatalk
Related
Hey guys,
I downloaded the JB source and created my own device/myvendor/myproduct folder. I copied the full_grouper.mk file into it and renamed it for full_myproduct.mk.
I basically inherit everything full_grouper.mk does but my own vendor and device. Should I even do that or just edit everything inside device/asus/grouper?
I did the . build/envsetup.sh and lunch and all went fine.
I ran make -j4 and the build was successful. Now how do I flash the system.img into the device? Will it also work ? I havent changed anything in the source I just want to flash my own build and then move on with some changes.
Do I need to have my file as an update.zip? Is update.zip a combination of installing the boot/recovery/system into one file? Is there a quick way to test my image works without flashing it permanently?
Final question: when I build the grouper source etc, does it mean the emulator will work too? It appears it does not.
Sorry for the newbish questions, I've looked around for other topics but I cant find a simple tutorial to just flash my own build. All I want is to flash the source code in which I assume would not have the Google apps and then I'll will take it from there.
You start your device in the boot loader by the button combo, or typing adb reboot-bootloader ( not sure on specifics) then while in boot loader type, fastboot flash system system.IMG . I would advice doing a fast boot --help to avoid bricking by using the wrong commands
Sent from my Nexus 7 using xda app-developers app
I have a new rooted and unlocked Nexus 7. I flashed a kernel and can't get past the nexus boot screen. My battery is about dead. What do I need to do! I have the tookkit, but I can't get it to do anything! Please help! My battery is almost gone!
Infuser86 said:
I have a new rooted and unlocked Nexus 7. I flashed a kernel and can't get past the nexus boot screen. My battery is about dead. What do I need to do! I have the tookkit, but I can't get it to do anything! Please help! My battery is almost gone!
Click to expand...
Click to collapse
And I don't have any backup ROMS or kernels to flash...
Infuser86 said:
And I don't have any backup ROMS or kernels to flash...
Click to expand...
Click to collapse
Battery just died. I could not turn it off. Everytime I tried to, it booted right back up. I was in recovery, but as I said, I have no roms or kernels to flash. I tried to mount the device, but was unsuccessful. I clicked mount system and nothing showed up on computer. Couldn't click mount sd card.
Someone please help me.
Always make a back up... we'll starting now
Let it charge, try again to get the proper kernel and flash in recovery. If it won't let you mount SD to transfer, extract the boot.img from the ROM you were using and flash via fastboot.
fastboot flash boot boot.img
fastboot reboot
See what happens
Sent from my Nexus 7 using xda premium
Can you please explain how to do that? I am new to the Nexus. I can get into Fastboot and then recovery. But how would I flash via flashboot. I do not see that option.
Edit
I do suggest reading up a bit on android or you are bound to find yourself in these situations. Also try and stay away from toolkits, you would already know what to do if you weren't using them
Download rom of choice to computer
Extract the boot.img from the .zip
After you charge nexus a bit, plug into computer and boot into bootloader
Open command/terminal on computer in the same location the boot.img is and type
fastboot devices
If you get 'waiting for device' you need to download the proper drivers, and or need to change directories to where fastboot.exe is located on PC, or just make sure you download everything from the platform-tools in the sdk and I recommend changing the path in environmental variables to include adb/fastboot
If you see your serial number proceed
fastboot flash boot boot.img
fastboot reboot
this should replace the kernel causing your boot loop with and all is well
Sent from my Nexus 7 using xda premium
demkantor said:
I do suggest reading up a bit on android or you are bound to find yourself in these situations. Also try and stay away from toolkits, you would already know what to do if you weren't using them
Download rom of choice to computer
Extract the boot.img from the .zip
After you charge nexus a bit, plug into computer and boot into bootloader
Open command/terminal on computer in the same location the boot.img is and type
fastboot devices
If you get 'waiting for device' you need to download the proper drivers, and or need to change directories to where fastboot.exe is located on PC, or just make sure you download everything from the platform-tools in the sdk and I recommend changing the path in environmental variables to include adb/fastboot
If you see your serial number proceed
fastboot flash boot boot.img
fastboot reboot
this should replace the kernel causing your boot loop with and all is well
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Learned that the hard way! So if I download the ParanoidAndroid ROM, just extract it and get the IMG file?
Infuser86 said:
Learned that the hard way! So if I download the ParanoidAndroid ROM, just extract it and get the IMG file?
Click to expand...
Click to collapse
Took the img from the ROM and fastbooted it and it wrote, but tablet won't load past Google screen...
So the only thing you did to cause it to get stuck originally was flash a kernel? If that was it and then Fashing the right kernel doesn't work and recovery won't let you Mount to put a ROM on SD, I would flash one of the official full ROM updates through fastboot.
There are a bunch of them posted here just grab one and flash it and she what happens
Sent from my Nexus 7 using xda premium
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.
I decided yesterday to flash my Nexus 7 to kit kat from the last OTA update 4.3. I am using Mac 10.9 btw. Download Android SDK installed it every thing so far at that point. Took my Nexus tapped my about tablet until I unlocked developer tools. Went in and checked developer tools. Then downloaded the 2012 nexus 7 WiFi packet. I extracted it and placed it in the same folder as my fastboot.
So I plugged it in and ran the devices command and there it was. Then I unlocked the boot loader no problem so far and rebooted back into bootloader.
Now the fun begins. Tried to run the script and nothing. So I opened it with text editor. So I ran the codes by hand. I did all the erase codes and the device responded.
So now copy and pasted the fastboot flash bootloader bootloader......IMG I dont have it in front of me now and got the error: CANNOT READ FILE. I copy the code even with the -Mac extension. I tried to flash 4.3 and 4.2.2 same error.
So now I am stuck my Nexus is softbricked luckily still have access to boot loader but not recovery mode. Does anyone know of an image that will work. I have included a pic of the bootloader screen
Sent from my Nexus 4 using xda app-developers app
Seams I can't upload the pic but here is the text
Fastboot mode
Product name- grouper
Variant- grouper
HW version -er3
Boot loader version- 4.23
Basel and version - n/a
Serial number- my serial number
Signing- not defined yet
Lock state- unlocked
Sent from my Nexus 4 using xda app-developers app
Fixed used my my parents windows machine and nexus toolkit 4.4 and Gel up and running
Sent from my Nexus 4 using xda app-developers app
i have access to ADB and fastboot mode.
i also try google factory image(see the attach picture for the result)
niceguy01 said:
i have access to ADB and fastboot mode.
i also try google factory image(see the attach picture for the result)
Click to expand...
Click to collapse
Yes, me too. I can't load anything except ADB & Fastboot. I used the Nexus 7 Toolkit to try to update to Kit Kat and now I have a soft bricked device. HELP!!!:crying:
Have you tried using adb shell command prompt to push the files to your device instead of a root toolkit?
cr0wnest said:
Have you tried using adb shell command prompt to push the files to your device instead of a root toolkit?
Click to expand...
Click to collapse
what file do i need to push in my device??
Effing toolkits again. When will they be banned for once and for all?
Oh that's right. They bring in ad revenue from lazy people.
Sent from my Nexus 5
niceguy01 said:
what file do i need to push in my device??
Click to expand...
Click to collapse
Check out this sticky here, it gives instructions on how to do it and what files are required. Its quite a lengthy guide, but its the safest method. http://forum.xda-developers.com/showthread.php?t=1907796
Pirateghost said:
Effing toolkits again. When will they be banned for once and for all?
Oh that's right. They bring in ad revenue from lazy people.
Sent from my Nexus 5
Click to expand...
Click to collapse
sorry im just a newbie:angel:
UPDATE: booting failed already gone by flashing cyanogen rom
the problem now is stuck in booting.see the attach picture
what is the meaning of
archive does not contain boot.sig
archive does not contain recovery.sig
archive does not contain system.sig
Got the same problem...I used RTK to flash 4.4 and ended up with a soft bricked N7.
Well initially I haven't been able to update any newer versions of CM. I was stuck on 10.2 nightly. I got a notification that there's an update so I downloaded it and tried installing. I get stuck when my N7 will go into recovery, I'll always get the droid with the red exclamation point and I have to stop the update. But I will always be able to do a system reboot and use the N7. After flashing using the RTK, all I can do is boot into the Bootloader mode. Choice at that point it Recovery, Reboot Recovert, Reboot Bootloader and Power Off. If I choose Recovery nothing happens. So the real choice is only to power off or reboot the bootloader.
I tried using fast boot but the guide I got was asking me to put the tablet in debugging mode (which I can't really do). And I get an error when doing the steps in CMD. I think I wasn't able to properly load the drivers because I am not seeing my device listed with serial number when I run >dab devices.
Kindda stuck and waiting where this thread will lead to as well so I can fix my N7.
Also, when I get the factory image (JWR66V) and run 7-zip on it, I don't see these files: bootloader-grouper-4.23.img, image-nakasi-jwr66y.zip, flash-all.sh, flash-base.sh. I only see 1 file.
As mentioned in about 5 billion threads, USB debugging has nothing to do outside of a booted OS.
Fix your drivers.
Unzip the factory image archive.
Sent from my Nexus 5
^Fixed my drivers (via SDK). PC recognised the device via fast boot devices. Ran a set of commands fast boot erase boot, cache, recovery, system, and user data. Flashed boot loader and reboot boot loader. Flashed 4.3 factory image (extracted via 7zip). Flashing/Update FAILED (I think the error was 'too mani links') and it went back to a blinking cursor.
@niceguy01 - just wait for CMD to process the entire thing. I was worried as well when I saw the system does not contain boot.sig etc error. Waited for it and started getting some scripts after. Wasn't able to complete the flash though but little steps getting there.
where should i flash radio.img?
boot,bootloader,recovery.system or userdata??see the picture
thanks
None of the above
Sent from my Nexus 5
Pirateghost said:
None of the above
Sent from my Nexus 5
Click to expand...
Click to collapse
thanks:good:
finally i got manage to fix my N7,thanks anyone who help me:good:
-----------thread close------------
i use google nexus toolkit v4 and install sdk drivers