yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Q&A] jakubmi9:
Hello everyone!

I suspect that my N7(2013) bricked itself overnight. Before going to sleep, I was watching videos on YouTube. If I remember correctly it was around 45% of battery left. I just put it to sleep as usually, and gone to sleep. In the morning it was dead, so I plugged it to charger and left it that way. After an hour, when I came back I turned it on. It showed the google screen and I put it down. After a while I noticed, that it's still on google logo. I decided to hold the power button so it could reboot. After a reboot, nothing has changed. Next idea I came up with was to enter the bootloader. Tablet booted to bootloader normally and then:

-Start option hangs on google logo

-power off works just fine

-reboot bootloader also works

-recovery mode hangs indefinitely on TeamWin logo.

By now, I have no idea what to do with it. The point is would like to save my data. Is there anything that could be done?

Nexus 7 (2013) Wi-Fi

Stock KOT49H - rooted with Xposed Framework

Stock kernel

TWRP 2.6.3.0 if i'm not mistaken

Thanks in advance.
[Nexus 7 (2013) Q&A] thisguysayswht:
Sound like pretty much your only option is to flash a factory image thru fastboot, you can download them from here

https://developers.google.com/android/nexus/images#razor

Make sure your boot loader is unlocked

Boot the tablet in to fastboot and run the flash-all.bat file if your using windows, of flash-all.sh for Mac and Linux.you should now have a stock tablet, with the stock recovery, I would also perform a factory data reset thru the stock recovery before rebooting the tablet.

If you would rather use a toolkit, wugs fresh is a good toolkit, and should be able to automate the above steps.

http://www.wugfresh.com

I should also point out that you need to have the proper driver's installed on your PC wugs fresh should guide you thru the process, if you don't already have them installed
[Nexus 7 (2013) Q&A] jakubmi9:
I forgot to mention: Yes my bl is unlocked, but doesn't flashing factory image wipe all data? I have one more question: On my PC xperia fastboot drivers are installed. Can I use them, or do I have to install some other drivers? Fastboot recognizes device but I want to be sure.
[Nexus 7 (2013) Q&A] thisguysayswht:
If it is recognize in fastboot you should be good to go, and yes it will wipe you data :( unfortunately if you can't enter recovery, there's not much that can be done. I have never been in this situation myself, and maybe someone with more experience than I will have a solution, such as reformatting your partitions thru fastboot, but as I said I've never found myself in this situation, and if it were me I would just flash back to stock, if you happen to have a backup on your PC, you can reinstall your recovery, and restore your backup, anything else is above my understanding of this, or is not possible.
[Nexus 7 (2013) Q&A] jakubmi9:
All backups are on tablet both titanium and TWRP. I just wanted to know if it's possible to recover it. I'll try to flash everything w/out wiping data. I think there was such option in wugfresh's toolkit. Maybe it's just one partition that's broken. But I've got feeling like it's going to be data partition that's broken. Thanks for help anyway. I'll try that tomorrow, because it's late night now.
[Nexus 7 (2013) Q&A] Captain Sweatpants:
If adb is working then you can adb pull your files assuming the file path it not corrupted

Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
[Nexus 7 (2013) Q&A] LinearEquation:
Just Swipe to factory reset in TWRP (leaves data in tact) and flash your Nandroid. Then reboot into system. You can adb sideload onto TWRP from your computer as well. This requires adb not fastboot.
[Nexus 7 (2013) Q&A] mdamaged:
There is a file called flash-all in the factory images, open it and remove the -w from the command line, that is what wipes the data.
[Nexus 7 (2013) Q&A] thisguysayswht:
I believe he cannot boot into recovery, so he cannot simply factory reset, no? I also thought that to use the adb side load feature, you had to be able to access twrp advanced>adb Sideload and that's for installing zips, no? I was thinking maybe he could adb pull a backup from the device, then install factory image, flash twrp, then restore from there? Or maybe simply reflashing the recovery? (I personally wasn't going to recommend any of this, since I don't have any personal experience in the situation) Maybe I'm missing something? or maybe I'm just an idiot, and I'm in over my head, and I need to read into things more before I post? feel free to tell me so. I'm always trying to learn about anything I can, and someone with more experience setting me straight is always a good way to achieve this lol. I like mpdamaged idea, but isn't that pretty much a dirty flash, and carries some inherent risks, seeing as how he's using xposed, I know it doesn't make any permanent changes to your system, but wouldn't this be the same concept as accepting an ota, in witch case you would need to first remove the xposed framework? Anyway hopefully someone can fill me in and he fixes his tablet, and I learn something lol.
[Nexus 7 (2013) Q&A] Raverbunny:
This. You can flash a factory image without data getting cleared and it's a very simple mod. Alternative is to extract the factory image until U have all .img files extracted (have to extract twice if I remember right) then u can fastboot flash system.img and boot.img only and that should work

Another thing, have you tried to reflash TWRP since it stopped working? Could just be corrupted and a reflash could fix it.

Nexus 7 LTE

Carbon Rom

Faux Kernel

---------- Post added at 01:04 PM ---------- Previous post was at 12:58 PM ----------

@ Thisguysayswht flashing just the system.img will wipe any system mods such as Xposed, used to do it when I was on stock to be able to install OTA

Nexus 7 LTE

Carbon Rom

Faux Kernel
[Nexus 7 (2013) Q&A] hcfte:
Don't know if you figured out how to save your data before flashing factory image but there is a very easy way to save your Titanium Backups and TWRP backups,

Plug your Nexus 7 into your computer and using MTP (assuming that still works) and look for the TB and TWRP files you can copy them to your computer and once you get your N7 back working just copy the files back to your N 7 and all your backups will be there for you to use. You can even open the files and save just what is important or save everything.
[Nexus 7 (2013) Q&A] jakubmi9:
Yes I know that, but as I said tablet is totally unconnectable via adb. Can't boot to Android and can't boot to recovery. By the way I realized that when I hotbooted stock kernel from fastboot it froze on the bootloader screen but I left it plugged to PC and after a while my PC recognized "unknown MTP device" but couldn't find any drivers for it. If I hotboot TWRP.img is it gonna boot to recovery or it doesn't work like that?
[Nexus 7 (2013) Q&A] mdamaged:
TWRP will work like that.

fastboot boot twrp-whaetver.img
[Nexus 7 (2013) Q&A] jakubmi9:
If my memory serves me right, Titanium Backup can restore apps from TWRP backup, right? That way I should be able to save all my data.
[Nexus 7 (2013) Q&A] mdamaged:
Yes, so does Nandroid Manager.
[Nexus 7 (2013) Q&A] jakubmi9:
I've just tried to hotboot TWRP 2.7 but it got stuck on TeamWin logo. It's been two or three minutes now. I don't think it will boot anymore, am I right?
[Nexus 7 (2013) Q&A] mdamaged:
Yeah, it would come up pretty quick. Something's not right...try an older version to rule that out, I know 2.6.3 worked for me using fastboot boot.
[Nexus 7 (2013) Q&A] jakubmi9:
TWRP is still hanged but device manager showed up "nexus 7" with everything else unknown and code 28 which is no driver installed. Which driver should I install for it?
[Nexus 7 (2013) Q&A] mdamaged:
Officially these: http://developer.android.com/sdk/win-usb.html#download

This one worked for me until I figured out how to do it right but must be with PTP not MTP: http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi
[Nexus 7 (2013) Q&A] jakubmi9:
I think that my nexus boots up everything normally but the screen just hangs on first frame of that thing. Any ideas what would that mean?
[Nexus 7 (2013) Q&A] jakubmi9:
That's very weird, but now, after about fifteen minutes TWRP just showed up. Any clues why does it take so long? I'm starting to think about leaving it for a night on Google screen. Who knows, maybe it'll turn on?

EDIT:

All partitions are showing as 0 mb, and in console, there is a ton of errors like:

Unable to mount system, data, cache, internal storage, and unable to set emmc bootloader message. It seems that partitions messed up. How to fix it?
[Nexus 7 (2013) Q&A] mdamaged:
Dunno, maybe it was hung trying to initialize something then timed out. Leaving it all night on the Google screen would probably kill the battery and not do much good...and would not trust doing it with a charger on it. While twrp is up, I'd do a nandroid, wipe dalvik/cache, and if you have a copy of your ROM on usb try and flash your ROM or stock rom (you can use tassadars stock zip here: http://goo.im/devs/Tassadar/stock_zips).

But this happening all of the sudden like this really makes me think this won't work, and that something is amiss with the EMMC or something.

EDIT: It could even be a bad block, maybe an fsck would fix this...but if it's under warranty it's better to send it back.
[Nexus 7 (2013) Q&A] jakubmi9:
I don't think that doing nandroid would do much good now. Also, it's constantly trying to mount data from what I see. Is it possible to lock the bootloader in that state? I'm slowly starting to think about warranty.
[Nexus 7 (2013) Q&A] mdamaged:
If you can get those fastboot adb drivers detecting your device, and fastboot devices shows your id, then oem lock should work, or it might hang.

A little hint, when you install the drivers, reboot the PC first, then plug the device into the PC while the device is on, then reboot the device while it is plugged into the PC, you may have to go into device manager and uninstall the driver and repeat the process if fastboot still is not detecting the device.
[Nexus 7 (2013) Q&A] jakubmi9:
Fastboot drivers are working for me, but adb ones do not. Are adb drivers required for locking? I'll try to lock it tomorrow and I'll send it to repair. Also when I tried to power off within TWRP it also froze at the end of the slider.
[Nexus 7 (2013) Q&A] mdamaged:
No, you use fastboot to oem lock, don't need adb.

Good luck, hope it works out for you.
[Nexus 7 (2013) Q&A] jakubmi9:
It would be wise to erase TWRP before sending it, or does relocking bl erase it? With no partitions left, there would be no way to determine, whether it was modified or not, right?
[Nexus 7 (2013) Q&A] mdamaged:
You could try using fastboot erase or reformat on each of the partitions before oem locking it...or better yet try flashing stock recovery manually if possible.
[Nexus 7 (2013) Q&A] jakubmi9:
I still didn't send it back, because i realized that there were threads like this before, with nexuses showing no internal storages. I (hopefully) found a way to repair it, but now I'm wondering. Is it normal for N7 to brick like that? Is it flawed hardware or just bad luck? Also my old recovery is still working (after 15 min of booting), but asks for a password to decrypt. After cancelling, it shows /data being around 28 GB, but can't browse it because of that password. The thread that's supposed to repair it from that state, suggests wiping it. I just don't know is it worth spending my time on, or is it flawed h/w and will happen again. Any clues on it?
[Nexus 7 (2013) Q&A] thisguysayswht:
By chance was your storage completely full? There a couple people in this thread with similar problems, and 2 of them reported to have almost completely filled storage.

http://xdaforums.com/showthread.php?t=2471341&page=2

As far as it thinking your data is encrypted, I believe based on the comments in this article, that your data is corrupted, so it thinks its encrypted, because it cannot be read.

http://www.xda-developers.com/android/f2fs-put-to-the-test-against-ext4/
[Nexus 4 Q&A, Help & Troubleshooting] dr.4dmin:
how install Recents App SlimKat in rom 4.4.2 stock ??
[Galaxy S II Q&A, Help & Troubleshooting] Mert-K:
Is it possible on android to do such things: http://www.iphonefaq.org/archives/973176 ?
[Galaxy S II Q&A, Help & Troubleshooting] Abel669:
If your phone is rooted..yes.
[Xperia Z1 Compact Android Development] OmarEinea:
Hello Everyone!!

So here is a new ROM I compiled yesterday, it does have a lot of features and it is called SONIC OPEN KANG PROJECT

I didn't open a new thread for it because I'm not gonna be updating it unless many users encourage me to do so...

Anyway I thought I should share it with you guys, for who ever wanna test it :)

Here is this ROM's features:

http://sonic-developers.com/?page_id=160

Also here is a quick review for the ROM:

[YOUTUBE]C-qgBllvcI0[/YOUTUBE]

And for more info visit their website:

http://sonic-developers.com

Download Link:

I've started uploading my files to androidfilehost.com , hoping you like it more than Dev-host

SOKP-MS-04-KK444-KTU84Q-20140726-amami.zip

Here are my screenhots as well:
[Xperia Z1 Compact Android Development] OmarEinea:
Hello Guys,

Since our lovely Z1C is relatively new, it doesn't have many CM based ROMs, so I thought why not porting some:)

from the closest phone to ours (which is obviously Xperia Z1).

So I'll be presenting five ports for five ROMs as mentioned in the title, but I'm gonna start with a simple guide for how to port the ROM yourselves:p

All you have to do to port a CM11 based ROM from Z1 is:

Download the Z1 ROM and extract it wherever you want

Open META-INF\com\google\android\updater-script with any text editor and remove first five lines (assert)

Download This for old builds, and This for new builds, then unzip it

Copy and replace "boot.img" from the previous zip to your Z1 ROM

Copy and replace "modules" folder to system\lib\modules in your Z1 ROM

Open system/build.prop with any text editor and change this value:

# Graphics
ro.sf.lcd_density=480

to become:

# Graphics
ro.sf.lcd_density=320

that is it, although there are optional things you may do before compressing the ported ROM:

In system/build.prop search for honami and replace them with amami

And then search for C6903 and replace them with D5503

Also you may wonna add "Compact" here:

You may also open META-INF\com\android\metadata and do the same replaces

Resign the ROM.zip after compressing it

Important Notes:

DO THIS ON YOUR OWN RISK

You must be running KK ROM before flashing these ROMs down below

This method won't work on Slimkat, although you can grab it from Here

All bugs in these ROMs are related to the original ROM not issues caused by posting

Fell free to report any bugs you face though, and I'll enlist them in known issues

PacMan ROM and MoKee ROM are officially supported, so there is no need to port them ;)

Instructions for all ROMs down below:

Copy the zip to your device

Reboot into recovery

Backup of your system (optional)

Do a factory reset and format [/system]

Flash the Zip
[Xperia Z1 Compact Android Development] OmarEinea:
XenonHD & BeanStalk

:::The XenonHD ROM:::

This was built in (2014-04-02) [Build 5]

It contains CM11 FXP312 Kernel

Zip is resigned

Screenshots:

Download link:

update-XenonHD-04-02-14-signed-amami.zip - 238.44 MB

New build's port can be found here: (Not tested by me)

http://xdaforums.com/showthread.php?p=53365536

For more info and screenshots, visit the Original Thread

:::The BeanStalk ROM:::

This was built in (2014-03-11) [Build 3]

It contains It contains CM11 FXP312 Kernel

It has random reboot bug

Zip is resigned

Screenshots:

Download link:

BeanStalk-4.4.255-20140311-amami.zip - 251.39 MB

For more info and screenshots, visit the Original Thread
[Xperia Z1 Compact Android Development] OmarEinea:
:::Gapps:::

GApps Standard 4.4.2 (10/5)

Removes AOSP Camera and AOSP Gallery and Replaces it with the Google variants

Removes AOSP Launcher2/Launcher 3 and CM Trebuchet and Replaces it with Google Now Launcher

Adds Google Search aka Google Now

All necessary syncing apks and libs

GApps Minimal 4.4.2 (10/5)

~20 MB

Playstore

Syncing apks and libs, etc.

Google Camera 4.4.2 (16/1)

Automatically removes AOSP Camera/Gallery and adds Google Camera/Gallery

FaceLock 4.4.2 (10/5)

Adds Face unlock

GenieWidget 4.4.2 (10/5)

Adds stock news and weather widget

AOSP Calendar Sync 4.4.2 (16/1)

Adds syncing ability for AOSP Calendar (not in Core or Standard packages)

AOSP Browser Sync 4.4.2 (16/1)

Adds syncing ability for AOSP Browser (not in Core or Standard packages)

This was copied and pasted from Original Thread (you can find more Gapps mirrors here)

Personally I prefer [and have tested] the minimal Gapps package, it is the best
[Xperia Z1 Compact Android Development] juried:
Great work!

I wonder if you would do Slimrom also, it is a mainstream ROM with many innovations that other ROMs have copied.

[edit] Duh I just read your comment about slimkat. That'll learn me to read OPs properly...
[Xperia Z1 Compact Android Development] xhizors:
wow, this looks good, i think ill try MoKee, just one question, is everything working ?

Just flash rom and some gapps ?
[Xperia Z1 Compact Android Development] OmarEinea:
actually, just today; [MENTION=2677528]akshaybz[/MENTION] has opened a thread for slimkat (not ported, compiled) here:

[ROM][4.4.2][KOT49H] SlimKat - Amami [Build 4][Alpha][UNOFFICIAL]

Enjoy;)

Well I didn't test everything, but the ROM was flawless, wifi is OK

Yes just flash rom and some gapps, try it and give a nice feedback;)
[Xperia Z1 Compact Android Development] RevokOne:
Might be a dumb question, but will updating them through the rom settings mess anything up?
[Xperia Z1 Compact Android Development] OmarEinea:
I don't expect updates to appear in the ROM's settings, but if they do,

yes updating that way should mess up a lot, it should make a bootloop.

anyway if you see an update for the ROM you're using, just tell me and I'll port the new release right away;)
[Xperia Z1 Compact Android Development] jenkins-84:
I been building ROMs on linux trying and testing build from source..Im new to it and the device has been a long time HTC user. So guess all are from Z1 with afew changes you posted similar to the stock port way. I built a few roms so apart from the one I'm supporting. Carbon and PAC ROM has shown View attachment 2664197View attachment 2664198
[Xperia Z1 Compact Android Development] OmarEinea:
Thread Updated

Ported MoKee 2014-03-31 Release

Ported Carbon 2014-04-01 (Build 2)

Also updated kernel in OP and in these two builds to 3.4.0 CM11 gb37510f From FXP313

I think I'll be updating the thread every week from now on, until these ROMs get a compiled version;)

Enjoy
[Xperia Z1 Compact Android Development] slonn:
How are the cameras qualities on these roms?

---

Sendt fra LG G Pad
[Xperia Z1 Compact Android Development] OmarEinea:
Exactly like in CM11.0
[Xperia Z1 Compact Android Development] e2zippo:
And how exactly is the quality in CM11, I can't seem to find a definitive answer in either CM thread?

Any updates on the roms btw?

Cheers! :good:
[Xperia Z1 Compact Android Development] OmarEinea:
Thread Updated

I don't know how to describe its quality, I think the best way to know is by trying;)

Yeah it's been a week, so here are the Updates of this week:

Updated Carbon ROM to build 4 (2014-04-09)

Updated MoKee ROM to build 2014-04-04 (its kernel was updated to FXP314)

Added XenonHD ROM latest release build 5 [2014-04-02] (download link in second post)

it is very customizable (can't describe it enough)

you can check more info about it in its main thread

about the kernel update, it seems like FXP team have messed up thier kernel a little

so when I tried it on Carbon and XenonHD I got some sort of bootloop,

but it worked fine on MoKee, so MoKee is the only ROM that has FXP314 kernel,

I don't recommended anyone to use it for porting so I didn't upload it:p
[Xperia Z1 Compact Android Development] TheQwertiest:
Actually the problem is not much with the latest kernel, but rather with the ROMs:

Recently there was a huge changeset merged in CM tree, among other things it took in kernel a lot of CAF code\blobs from 4.4 Sony sources, and Xperia CM ROM was rebased on this CAF kernel.

It means, that the ROMs based on CM must be rebuild using latest sources, otherwise they'll have a bootloop with the new CAF kernel =)
[Xperia Z1 Compact Android Development] OmarEinea:
Huh, Thanks for the info bro,

seems like I should read more very now and then to know this kind of stuff.:o
[Xperia Z1 Compact Android Development] OmarEinea:
Thread Updated

Added Paranoid Android ROM

This was built in (2014-04-15)

It contains CM11 20140410-Nightly kernel

Updated MoKee ROM

This was built in (2014-04-14)

The ROM was deodexed (original ROM was odexed)

It contains CM11 20140410-Nightly kernel
[Xperia Z1 Compact Android Development] canteo:
hi, should i have a unlock bootloader for test this roms? i can´t unlock it
[Xperia Z1 Compact Android Development] OmarEinea:
unfortunately yes, if you want to flash a custom kernel, you have to have an unlocked bootloader (and that is required to flash custom ROM)
[Xperia Z1 Compact Android Development] tracyn:
Thanks for the effort! I just installed MoKee, it runs flawlessly so far. One question, though... does ART work for these ported ROMs?

EDIT: I tried enabling it on MoKee but got a bootloop (even after 15 mins the phone won't boot) with ART enabled.
[Xperia Z1 Compact Android Development] OmarEinea:
that is weird, cuz I have tested ART function on previous MoKee port release and it was working just fine...:confused:
[Xperia Z1 Compact Android Development] Lorenzoval:
I think ART doesn't work because OP deodexed the ROM.
[Xperia Z1 Compact Android Development] tracyn:
Ah, okay. Is there anything I can do on my end, or do I have to wait for an odexed release?
[Xperia Z1 Compact Android Development] Lorenzoval:
For me the best thing to do is to wait for an odexed version.

If you can't really wait, search for a tool that makes your rom odexed.
[Xperia Z1 Compact Android Development] OmarEinea:
Hmmm, that might be it, thanks for the info,

I'll test ART on odexed and deodexed in the next port and see,

the original ROM is always odexed, but this last port I thought it would be nice to deodex it,

I think I'll stop deodexing it from now on
[Xperia Z1 Compact Android Development] tracyn:
Alright, thank you! I'll wait for the new version then, no worries.
[Xperia Z1 Compact Android Development] tracyn:
I got a bit of a problem. I've set up the MoKee port on my z1c and it works great - I really like the look and feel of this rom, more than any of the others I've tried. However, now I noticed that I don't get any noficications in standby - even after turning the screen on, my notifications (from SMS or Pushbullet, for example) don't ring or vibrate at all. I've setup Active Display (which doesn't really work, either, especially the Pocket Mode) and custom LED colors, so I tried disabling them, but that doesn't fix the notification issue. I'm also using Greenify and BatteryGuru, but turning them off doesn't help, either.

Any thoughts what might cause this behaviour? I was on XenonHD for a couple of hours and notifcations worked all right there, but I didn't really like that rom.

EDIT: This is weird. I just did some more testing, and looks like Vibration doesn't work anymore at all....
[Xperia Z1 Compact Android Development] OmarEinea:
So what's the version of MoKee ROM did you port, and did you include the kernel from OP (cuz it is old for MoKee)

and did you encounter these issues on the deodexed MoKee I provided ???

Tomorrow is wednesday (the weekly update date)

Hopefully I'll bring some updates (especially for Mokee), so stay tuned;)