First off let me say this is NOT my work.
Credit and support need to go to Lorenzo Faleschini. Here is his Google + https://plus.google.com/u/0/112669767758185770835/posts
I reached out to the Ubuntu community for help with MTP and he posted a solution.
It works wonderfully, check out the blog post here:
http://penzoditutto.blogspot.it/2012/12/android-mtp-devices-40-mount-scripts.html
I have been also struggling for a very long time to get MTP working with my Nexus 4 on Ubuntu but finally got it working with brilliant tutorial found in here
htt p:// bernaerts.dyndns.org/linux/ 268-ubuntu-automount-any-mtp-device
( just stick the link together - I have too few posts to post an outside link )
Where do I get the 4.3 leak for my Nexus 4?
ROM (CREDITS: gmillz)
New baseband and bootloader (CREDITS: someone enlighten me )
What's new in 4.3?
XDA discussion thread about new changes
Changelog compiled by Sam Tate from Google+
Hands-on video from AndroidCentral using Android 4.3 on the Nexus 4
ROM developers, please make a (rom name here) with 4.3!
Wait for it guys the developers don't Iive to please you and besides, the source code has not been released yet. Give the ROM devs a break and stop filling up the threads with requests for 4.3 in new custom ROMs.
I want to stay on my custom ROM but want to enjoy some of the new stuff in 4.3. How should I go about doing this?
Th3RiddL3r has made an awesome thread including a lot of new apps and other features from Android 4.3, including the font, new camera APK, new bootanimation and other things in 4.3/GE Phones. Check out his thread here.
For the curious:
What's the whole story of this leak?
Quoted directly from AndroidCentral:
A few weeks after Android 4.3 leaked for the the Google Play edition Galaxy S4, today we're seeing the same pre-release build — JWR66N — leaking out online for the Nexus 4. The unofficial firmware comes to us from Jeff Williams on Google+, who bought his Nexus 4 on Craigslist from a Googler, only to find it running the pre-release software. With a little help from the Google+ community, IRC users and XDA, Jeff was able to create a system dump and backup of the ROM. Currently the radio and bootloader are missing from this package — word on the forums is that they'll be provided at a later date.
Click to expand...
Click to collapse
Reddit Thread about the people who helped Jeff Williams:
Quick!! Someone help this guy pull a system dump... Leaked 4.3 ROM for Nexus 4
Redditors/G+ users help a lucky craigslist buyer pull Android 4.3 off of his Nexus 4!
IRC Log from the chat where people helped Jeff Williams: (Credits to BoomChaos from Reddit)
http://pastebin.com/z3TdxjwB
I will be editing this post actively with any improvements and new things people suggest. Credits go to the awesome people on XDA, G+ and Reddit(/r/android) community.
Don't we already have a thread like this?
Sent from my Nexus 4 using Tapatalk 4 Beta
Neefy said:
Don't we already have a thread like this?
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
yes we do.
please close admin. :good:
This thread is silly
Sent from my Nexus 7 using xda premium
another one????
The following are reasonable formats that are suggested when posting a new ROM. We expect your ROM post to look somewhat professional and easy to understand.
1. Requirements (bootloader version, radio version etc)
2. State that it's from an official manufacturer or source base (stock ROM or AOSP-like source).
3. Thread shows a clear overview of changes made, in a way that users can see what has changed.
4. Explicit installation instructions.
5. ROMs need to identify what kernel they are using. If 100% stock then they must state that.
6. If custom kernel they must provide a link to the kernel on XDA (if available) or a link to the kernel source. This is required by GPL. Stock (untouched) kernels can link to the manufacturers source (if available).
7. At least 2-4 images (screen-shots) 1 of which must be of system/device info. Do not use photo hosts thay deluge users with ads and popups when they select the image. You can either attach the images, or use a hosting service such as photo-bucket for example.
8. Links to downloads. A link to a direct download is preferred. Linking to external websites home pages are not allowed, it must be linked to the Downloads page. Also use of "ad-driven" (adfly for example) or "commercial" sites are mostly not allowed. Registration on some sites "may" be allowed, but is subject to XDA Moderation approval.
9. Credits for sources used. Very important.
10. Keep your "asking for donations to a limit. You already have a "Donate" button.
Simply posting a link to some download site "here it is, download it", is not allowed.
Any questions, please feel free to contact any moderator.
Thank You
Moderation Team
The following are reasonable formats that are suggested when posting a new ROM. We expect your ROM post to look somewhat professional and easy to understand.
1. Requirements (bootloader version, radio version etc)
2. State that it's from an official manufacturer or source base (stock ROM or AOSP-like source).
3. Thread shows a clear overview of changes made, in a way that users can see what has changed.
4. Explicit installation instructions.
5. ROMs need to identify what kernel they are using. If 100% stock then they must state that.
6. If custom kernel they must provide a link to the kernel on XDA (if available) or a link to the kernel source. This is required by GPL. Stock (untouched) kernels can link to the manufacturers source (if available).
7. At least 2-4 images (screen-shots) 1 of which must be of system/device info. Do not use photo hosts thay deluge users with ads and popups when they select the image. You can either attach the images, or use a hosting service such as photo-bucket for example.
8. Links to downloads. A link to a direct download is preferred. Linking to external websites home pages are not allowed, it must be linked to the Downloads page. Also use of "ad-driven" (adfly for example) or "commercial" sites are mostly not allowed. Registration on some sites "may" be allowed, but is subject to XDA Moderation approval.
9. Credits for sources used. Very important.
10. Keep your "asking for donations to a limit. You already have a "Donate" button.
Simply posting a link to some download site "here it is, download it", is not allowed.
Any questions, please feel free to contact any moderator.
Thank You
Moderation Team
First off, not my development work; just trying to make a thread to point people to for downloading various current builds of TWRP for the ZUK Z2 Pro in the appropriate section. There's a great guide here by @MariosFFX that includes instructions, but the link is to Mega (fast unless it's filtered where you live) and it's for old versions.
So right now there seem to be three functional builds of TWRP 3.1.x for our Z2121:
1. The one most people seem to be using is 3.1.0 from zukfans.eu by n2k1 that you can find filed in the German forums (instead of in the Z2 Pro section, where it used to be before they closed that thread because all the discussion was in German), in this thread. Direct download link here. But this one may also have error 7 trying to install some ROMs...? I haven't used it in a long time because I think it was failing to install some of SY's newer builds of RR & AICP a few months back, so I switched over to the LR.Team one instead.
2. The "Chinese forums" one people point to has been version 3.1.0 but has been getting updates & modifications all year, with the most recent update being June 17. It has some nice touches (and/or shoot-yourself-in-the-foot buttons) like a button to reboot directly into EDL (port 9008) mode for QPST/QFIL flashing, unroot scripts, prompt to install SuperSU 2.79, and exposes more partitions to the graphical front end for mounting/backup/wiping like /persist. On the other hand, screwing around with those might end up borking all your sensors and baseband firmware and killing your cat while trying to overzealously clean up after a failed flash that's bootlooping, so y'know; YMMV. If you're feeling adventurous and like using Chrome's built-in translate features (or read Chinese), find the Lenovo BBS thread here, Baidu download site here (you'll need to enter "qe3d" as the password before you can select & download). This is not for the faint of heart; it actually wouldn't let me see any files to download in Chrome, but by using that to see how the site worked, I could load it in Edge (all Chinese, good luck!), click the right things, and it started to download.
If you're not feeling brave, I put the June 17 version up on Android File Host here because the only versions I've seen linked here were the March 14 build.
3. Looks like @davidevinavil actually built a version of 3.1.1 for the Z2 Pro along with their incredible work on AEX, and just didn't mention it in that thread. But I went poking on their AFH profile and found a Recovery folder as well, with a working build that I've successfully flashed and used for a week or so. It looks like it was ported straight over from a Z2 Plus version (I mean, the phone identifies itself to my Windows 10 computer as a Z2 Plus instead of Z2 Pro or Z2121 when using that recovery), and there's some interesting translation choices (calling it a "digest" instead of "md5 checksum"), and only shows Cache, System, Data, Firmware, and USB-OTG partitions in the Mount menu. You can find it here. (And broseph, if you want me to take down that link to your work, just let me know.)
Again, none of this is my work. I just see links up in the Q&A section instead of the Development section, or linked from ROM releases, or pointing to old versions, and not an actual thread in the right section for linking to current builds of TWRP. Got another hot lead on active development of TWRP for our Z2121? Put it here!
Thanks for that !
I use the "China/US" LR.Team 3.1.0-0314 version of 2017-03-13 from the original guide of MariosFFX and I had no issue while installing newest ROM.
Thank you ! I'm getting now the latest recovery by L.R Team ! I had a twrp build that reset the rom each time I entered in recovery mod haha. Now with the latest TWRP by L.R team, I will never get an "auto-reset" !
Terminator.J said:
1. The one most people seem to be using is 3.1.0 from zukfans.eu by n2k1 that you can find misfiled for whatever brain damaged reason in the German forums instead of in the Z2 Pro section, in this thread. Direct download link here. But this one may also have error 7 trying to install some ROMs...? I haven't used it in a long time because I think it was failing to install some of SY's newer builds of RR & AICP a few months back, so I switched over to the LR.Team one instead.
Click to expand...
Click to collapse
Misfield brain damaged??
German Dev. and it started with test build in german language and german discussion.
The z2 pro section is english only...
If you use the search function you will see a thread in the Z2 pro section...
https://zukfans.eu/community/index.php?threads/5554/
So i dont know what is brain damaged and Misfield
crisps said:
Misfield brain damaged??
German Dev. and it started with test build in german language and german discussion.
The z2 pro section is english only...
If you use the search function you will see a thread in the Z2 pro section...
https://zukfans.eu/community/index.php?threads/5554/
So i dont know what is brain damaged and Misfield
Click to expand...
Click to collapse
The Z2 Pro section is English only? Okay, that seems more foolish than anything. My apologies.
Surely they don't intend for development threads to be scattered across all the different language discussion areas... The logical thing would be actual flashable ROMs/recoveries/other development in the device section and links to discussion in the appropriate language.
I'll be the first to admit, as an American, I'm jealous to see a thriving multilingual community.
But the thread started in Z2 Pro section (which you linked to), was closed to further responses, and moved to German section by the admins. I'm content to follow the German language discussion using Google translate, but moving the actual development thread out of the device section & closing that thread from further updates is what seemed like a backward way of doing it to me.
But I'm getting off topic. I'll remove my editorial comments from the OP, this probably isn't the place to discuss the behavior of admins of another forum entirely.
You have tried to restore a backup with the recovery of section 2. Chinese forum?
Enviado desde mi ZUK Z2121 mediante Tapatalk