Swipe to right from lockscreen and you run the camera.
[ROM] CyanogenMod 11 [OFFICIAL] [NIGHTLIES]
- Thread starter eak1080
- Start date
-
- Tags
- 4.2.1 nexus 7 3g tilapia
You need to install a camera launcher app. All this does is add the icon for the camera application included in the ROM.
I use this app and it works very well for me.
when update to new rom....suddently my nexus 7 just bootloop....try to downgrade but still the same...try different version rom but still cant see the cyanogenmod logo....is my device bricked....please help me....
yes...still cant pass the boot screen...also cant make a backup from twrp recovery 2.6.3.0...
Update to TWRP 2.6.3.1. I had similar issues on TWRP 2.6.3.0. There were some updates for KitKat in 2.6.3.1.
Hi guys,
today there is the snapshot-m3 of cm11 for tilapia, but when i flash it i take this error from cwm:
set metadata recursive some changes failed status 7
Other cm11 nightly everything works. Maybe corrupted file?
today there is the snapshot-m3 of cm11 for tilapia, but when i flash it i take this error from cwm:
set metadata recursive some changes failed status 7
Other cm11 nightly everything works. Maybe corrupted file?
Flashing process of snapshot m3 worked fine with me. I am using recovery twrp 2.6.3.1. You may check the version of cwm recovery you are using and md5 of rom .zip file you downloaded.
hello
im using TWRP 2.6.3.1(latest) not the TWRP 2.6.3.0 when im got the bootloop issues....are my NAND is problem as i cant even make a backup from TWRP menu...
how to know if my NAND is problem?
please help, am i loosing this device
hello
please help
n7 (2012) on one of the lastest cm11 nightly, started random freezes a couple of days ago.
this morning, stuck at 'google' logo, blank screen on trying to boot recovery
tried to read similar cases, decided to try factory image KOT49H.
I did
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-grouper-4.23.img
at that point I got an error.
not knowing what to do and thinking the os was already gone with my erase commands, I desperately tried a few fastboot commands.
stress, no power backup, scheduled loadshedding (in my city, country)
i am not sure if ever did 'fastboot erase bootloader'
but I am sure I tried oem lock and unlock
then i read that that particular bootloader had an error, but.. i downloaded 3 different images
and i still failed to flash any of them. I have not rebooted for fear that i may have mistakenly
erased the bootloader, even though that could maybe help (maybe not).
now i have bootloader from nakasi-krt16s (md5 df53028033c9eccf4fe5ba7bc198ce24 that is version that should flash).
but everytime i try
> sudo ./fastboot flash bootloader bootloader-grouper-4.23.img
I get
sending 'bootloader' (2100 KB)...
OKAY [ 2.257s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 2.399s
what shall I do? is there a way to figure out if the bootloader is still there? Is there another bootloader that I should try to flash. Will it reboot to bootloader?
The display reads v 4.18
thank you so much for helping.
ps: i use a stand alone version of fastboot that came with ADB 1.0.31 (I do not remember the source), again that was practical because of power supply problems I have and use a knoppix in readonly mode.
a './fastboot devices' still show the device and there are 2 lines of 'Signature mismatch.' in the upper left corner.
hello
please help
n7 (2012) on one of the lastest cm11 nightly, started random freezes a couple of days ago.
this morning, stuck at 'google' logo, blank screen on trying to boot recovery
tried to read similar cases, decided to try factory image KOT49H.
I did
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-grouper-4.23.img
at that point I got an error.
not knowing what to do and thinking the os was already gone with my erase commands, I desperately tried a few fastboot commands.
stress, no power backup, scheduled loadshedding (in my city, country)
i am not sure if ever did 'fastboot erase bootloader'
but I am sure I tried oem lock and unlock
then i read that that particular bootloader had an error, but.. i downloaded 3 different images
and i still failed to flash any of them. I have not rebooted for fear that i may have mistakenly
erased the bootloader, even though that could maybe help (maybe not).
now i have bootloader from nakasi-krt16s (md5 df53028033c9eccf4fe5ba7bc198ce24 that is version that should flash).
but everytime i try
> sudo ./fastboot flash bootloader bootloader-grouper-4.23.img
I get
sending 'bootloader' (2100 KB)...
OKAY [ 2.257s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 2.399s
what shall I do? is there a way to figure out if the bootloader is still there? Is there another bootloader that I should try to flash. Will it reboot to bootloader?
The display reads v 4.18
thank you so much for helping.
ps: i use a stand alone version of fastboot that came with ADB 1.0.31 (I do not remember the source), again that was practical because of power supply problems I have and use a knoppix in readonly mode.
a './fastboot devices' still show the device and there are 2 lines of 'Signature mismatch.' in the upper left corner.
Last edited:
Did you download the right factory image for your device? It seems you downloaded the image for the Wi-Fi version, not the 3G one. You should download the image for "nakasig", NOT "nakasi". They're here.
At this point, your bootloader should still be there, so you can just download the right factory image and flash it.
I recently installed yesterday's nightly to my N7, and upon enabling ART, I experienced issues with Play Store on a fresh install (it would open and freeze). Upon using today's nightly, enabling ART caused either a bootloop, or extremely long boot time.
Last I was on RastaKat, ART worked flawlessly.
Just curious if anyone here had any luck with ART and CM11?
Last I was on RastaKat, ART worked flawlessly.
Just curious if anyone here had any luck with ART and CM11?
@frantisek.nesveda
My device is wifi only version, therefore I think I have the correct downloaded images.
Is there a way to tell if the bootloader is still there before I try reboot it? Why do you think I can not write the bootloaders at this point?
please help, it has been standing there on bootloader for 3 days.
regards
thank you.
My device is wifi only version, therefore I think I have the correct downloaded images.
Is there a way to tell if the bootloader is still there before I try reboot it? Why do you think I can not write the bootloaders at this point?
please help, it has been standing there on bootloader for 3 days.
regards
I was confused because you're writing in the Nexus 7 3G section, so I thought you have the 3G version, nakasig.
Anyway, I didn't completely understand in what state your device is in at the moment. You are now in the bootloader? Could you possibly send a photo of how what it displays?
I'm not entirely sure what the problem might be right now, but we can try to think of something.
Did you restore to a factory image before with the same or similar method? So we would know if it worked before, or not.
How old are your fastboot binaries? Did you try updating them and trying again? Maybe they're just too old and don't work with the N7 well. I don't know if it can cause this type of problems, but you can't be sure.
Did you try an older factory image? If I remember correctly, the 4.3 factory image has the same bootloader version as you do, so you don't have to update the bootloader, you can just flash everything else. You can try flashing 4.3 and then updating via OTA.
Hope something from this helps.
Last edited:
I am sorry, I am am here in the wrong section, the device is WiFi only. the fact is, for personal reasons, it is very important that i do not loose this tablet. and in the panic, i happened to land here. but you guys are sweet. thank you so much for understanding.
I will first try to answer briefly to question you ask:
I have never tried to revert back to factory image before.
I can not see the fastboot version, it does not show it. I got it about 6 months ago, together with DB v. 1.0.31.
before trying to flash any version of anything -i need to make sure that the tablet will be able to boot to bootloader.
now i will what happened (trying to be brief and to the point):
it was running CM11 nightly a couple of days old. It had bootloader 4.18.
after it froze at google logo on normal boot, i tried to get to recovery mode -where i got a blank display. so i was only left with bootloader.
i thought i would have to start by a fresh factory image. followed a guide in this forum, i downloaded the 4.4.2 image, typed fastboot commands step by step. while flashing the bootloader, it came with an error -i am not sure any more of the exact message. I could not understand it, i thought i had done something wrong. so i kept on trying.. I remember that i tried to lock and unlock commands, and tried to flash again.. I tried writing system image. I then went back to reading the forum messages. I still don't understand it. folks are writing the bootloader in the kot49h has an error. I do not understand that google would still make it publicly available for download if it was causing so much error/confusion.. I then downloaded and tried to flash different versions (4.23, 4.18), including the one that comes with jwr66v. I keep getting the same error message:
writing 'bootloader'...
FAILED (remote: (Unknown error code))
current situation:
right now, it still is as it was 4 days ago (in the same bootloader mode). the dispay shows the usual bootloader screen + two lines of 'signature mismatch' in the upper left corner.
my understanding is, if somehow I had erased the existing bootloader I should not reboot it, it would be bricked. I then do not understand the point in having the possibility to type such a command..
more?
I am not happy to write long messages in the forums. i also want to avoid any confusion. i live in a place (oh hell, it is called kathmandu), where the power supply is, politely put, irregular on top of scheduled 12 hours of power interruptions a day.. Reason why i choose to run knoppix on an ext4 partition. It made sense to download a standalone version of 'fastboot executable' compiled by someone nice on the Net.
am i repeating myself?
brief, should i try to get a proper version of the adb/fastboot. could it be the problem. i personally have a feeling, it is not.
Either I need to make sure that it will reboot at least bootloader or successfully write a new boot loader. so far I have tried 4.23 with the correct md5 ad mentioned in some guides. I have also tried to overwrite 4.18.
thank you for your patience. please help me.
to write everything publicly
i bought this for my young kid, we have been both very happy to own it. it would work independent of power supply, it was portable.. we are both very disappointed.. he can not look up wikipedia for his school. STOP.
regards
Hmmm... I searched through XDA and some people with the same issue say that updating their USB drivers or fastboot helped. If you have ADB vs 1.0.31, the fastboot that came with this ADB version should be all right, though.
I just tried this bootloader and it flashed fine for me: http://www.androidfilehost.com/?fid=23060877489996594. Could you try it too?
md5
df53028033c9eccf4fe5ba7bc198ce24
I have tried that file, gives me the same error
regards
Guys, I m Using CM11Snapshot M1. Did you wipe data to install M3?
May I use CWM 6.0.4.3 to install
May I use CWM 6.0.4.3 to install
Last edited:
it's always recommended to wipe data but it's not neccessary
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone