yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] mattb3:
Is the location of the nandroid backups the intended behavior? Both TWRP and CWM place backups in /data/media, which is especially inconvenient because none of the nandroid utilities are setup to look there. Seems like a bug.
[Nexus 4 Original Android Development] stankyou:
I'm all for disabling cores if needed. I don't think a recovery needs four cores anyway. :p

via xda app
[Nexus 4 Original Android Development] rmkilc:
But it's so fast with 4 cores!
[Nexus 4 Original Android Development] Dees_Troy:
The pigz compression tool that we use is multi threaded & should be able to take advantage of all 4 cores so shutting off some cores would probably slow down compressed backups. Other than that it probably won't make a significant difference.
[Nexus 4 Original Android Development] joshndroid:
edit: this was for old version... removed so as to not confuse with new version
[Nexus 4 Original Android Development] kai_:
Even though this issue with 2.6.1.0 is easily resolved (once you know how) , I think the suggestions for doing so from some more senior members are slightly condescending.

In my personal situation, I had a brand new Nexus 4 and out of the box was running stock. First I had to unlock the bootloader, then flash a custom recovery - of which I chose TWRP over CWM. Of course being green to Nexus, I just chose the latest version of TWRP - how was I supposed to know any better?

Finally, I chose to factory wipe as I'm coming from a different ROM. This is generally accepted as best practice when flashing. If you follow the steps listed on Paranoid Android, it tells you what to do including doing a factory reset. If you follow those steps from where I was you will encounter this issue.

I wasted several hours figuring out how to solve the problem (in the end I went with CWM)

No one is getting the blame here but something has to either be done about this as the idea is to help each other out. Not everyone has had a Nexus 4 from release date and knows everything about it inside out. We will also see quite a few reports I think because of the recent price drop and so many more 'newbies' will be coming on board.
[Nexus 4 Original Android Development] peikojose:
Tried to copy one backup to my PC using windows 7 and it didn't copy it.. I copy pasted and it pasted only some files... I am using 2.6
[Nexus 4 Original Android Development] Adizzzle:
Known issue. Flash 2.5

Nexus⁴?
[Nexus 4 Original Android Development] cb474:
Other than the fact that backups are not easily copied to one's pc, if they were made with 2.6.0.0, is there anything wrong with these backups? They can still be restored properly, can't they?

I figured out how to copy the backup, per others suggestions, by booting into recovery and using adb pull. But I just want to be sure if I transfer one of these backups back to my phone it will be possible to restore it.

Also, is this the only reason some people currently prefer 2.5.0.0 over 2.6.0.0? Thanks.
[Nexus 4 Original Android Development] Andre_Vitto:
yeah backups are fine.. No other issue with 2.6.0.0
[Nexus 4 Original Android Development] CamoGeko:
Awesome!

I'm waiting for my mate fisha21 to get his TWRP theme resized for the N4.
[Nexus 4 Original Android Development] Geordie Boyo:
Is it right there is issues with 2.6.1.0 ?

If thats the case, i'd better downgrade, is there a flash zip file for the most stable release?

Ive found the 2.6.0.0 flash file

and here is 2.5.0.0 recovery flashable zip file
[Nexus 4 Original Android Development] lorolouis:
Yep man, I already downgraded to 2.6.0.0.

I think, only 1 or 2 persons in total reported that "weird thing of bad radio flash by 2.6.1.0"

Crazy enough to let people like you and me getting concerned and going on "safer side".

However, see what "bad thing" I found happening on 2.6.0.0 but not happening on 2.6.1.0 for example:

Nexus 4 PA 3.99 ROM

1. Boot to Recovery 2.6.0.0.

2. Mount the system

3. Terminal command -> navigate to /system/lib as starting folder

4. Try a command like ls -al -> gives "segmentation fault"

5. Repeat all with 2.6.1.0 - no problems

Can someone reproduce this please?

Also with 2.5.0.0 if possible.

I am almost ready to go down to 2.5.0.0 if all is stable with it and backups made on 2.6.0.0 are still compatible with it.

BTW, for painless flashing different TWRP revisions I am using Wug's Nexus Root Toolkit v1.7.2 by "advanced" -> "permanent flash" -> then select the .img file (and having md5 sum file near it) downloaded from here

http://techerrata.com/browse/twrp2/mako
[Nexus 4 Original Android Development] Adizzzle:
2.5.0.0 is flawless, have been running it for months with not a single hiccup!! If you want stability 2.5 is the recovery to use!!

Nexus⁴?
[Nexus 4 Original Android Development] lorolouis:
Could you confirm that on 2.5.0.0

Advanced - Mount system -Terminal - /system/lib as starting - "ls" doesn't throw "segmentation fault" ?

BTW, what ROM/Kernel you are running?
[Nexus 4 Original Android Development] Adizzzle:
I have been using PacRom, at least until Rootbox is back in action.

I don't touch my kernels really, never have on my Nexus4.

I can give it a go however I never use the terminal either. :P

---------- Post added at 09:48 AM ---------- Previous post was at 09:04 AM ----------

TWRP 2.5.0.0 Lime-ified!

So here is a custom TWRP 2.5.0.0 .img that has a custom curtain,

and is completely themed green instead of the default blue.

It's been tested and runs just fine, not a single bug at all.

Download:

https://www.dropbox.com/s/88gm0dbn22gmt3m/openrecovery-twrp-2.5.0.0-mako-green.img

Flashify

in the Google Play store will flash recovery .img's for free,

it is a flawless app, and has awesome reviews, check it out!
[Nexus 4 Original Android Development] lorolouis:
Thanks for the colorful answer, but it did not give me what I needed.

BTW, I can live with the original boring gray "theme" as far as functionality and compatibility from non-encrypted backups made by 2.6.0.0 and 2.6.1.0 are proven.

I don feel the recovery a place where I like to say long and enjoy fancy buttons or colors.

Anyway ... it looks like I'll downgrade tonight to 2.5.0.0 and forget about it for next several months.
[Nexus 4 Original Android Development] Adizzzle:
your welcome
[Nexus 4 Original Android Development] Dees_Troy:
I'm going to address the issues with Paranoid Android here and I hope that I only have to do this once:

Android 4.3 started using SELinux. SELinux creates a whole new world of issues that the Android community will need to address. AOSP recovery doesn't really address (and doesn't need to address) the fact that different ROMs may have different contexts. Unfortunately, AOSP recovery chose to locate the default contexts in the ramdisk of recovery. There's currently no good way for a ROM to install / load their own contexts before the zip install. As such when Paranoid Android 3.94 gets installed, files get installed with the CM10.2 SELinux default contexts (TWRP is currently built in CM trees). The CM10.2 SELinux default contexts break some permissions that prevent PA from being able to access certain files/folders which causes it to appear that the radio/baseband and IMEI are broken.

To prove that these items are not broken, you can boot TWRP 2.6.1.0, delete /file_contexts, /property_contexts, /sepolicy, and /seapp_contexts (these files would have to be removed on every reboot) then killall recovery. This causes recovery to restart but it won't be able to find the SELinux contexts during boot. You can go to Wipe -> Advanced and wipe system, then reinstall PA and all will be working fine.
[Nexus 4 Original Android Development] lorolouis:
Thanks Dees_Troy.

Just 2 questions, please:

- Good explanation, but is there anything wrong if for PA we simple use the old 2.5.0.0 instead?

- what "segmentation fault" means on 2.5.0.0 and 2.6.0.0 when I am trying s simple "ls" terminal command at /system/lib? (on 2.6.1.0 is OK)

Best regards
[Nexus 4 Original Android Development] Dees_Troy:
For now I've made a 2.6.1.1 with this patch set:

http://review.teamw.in/#/c/737/

This should resolve for now the issues with installing PA. There's nothing terribly wrong with 2.5.0.0 except that 2.5.0.0 doesn't have any of the SELinux stuff so it will fail to set up SELinux policies and contexts. Most of the time this will be "okay" but it probably means that SELinux won't be working the way that it's supposed to.

Your seg fault is due to the way that TWRP is built (linked libraries and binaries). When you tried to ls in /system/lib it was trying to link busybox to the libs in /system/lib instead of the ones in /sbin which wasn't working right. If you cd to /system instead of /system/lib then ls ./lib you would get the contents of the lib folder like you would expect.
[Nexus 4 Original Android Development] lorolouis:
Appreciated your prompt solution and clarification.

Thank you!
[Nexus 4 Original Android Development] 21plays:
Had that no radio problem happen to me too. PA 3.99
[Nexus 4 Original Android Development] albaoe:
Yesterday, i was using TWRP 2.6.1.0 and flashed Cataclysm, and i got no signal, no IMEI, baseband unknown, etc. So i changed to TWRP 2.6.0.0 and reflashed the rom. All OK again.

Today I flashed PA 3.99 and no problems at all (still TWRP 2.6.0.0).

Really appreciate the work.
[Nexus 4 Original Android Development] apatal:
So 2.6.1.1 resolves the issue of the "vanishing baseband"? :)
[Nexus 4 Original Android Development] kenkiller:
So PA is the root of the problem.....
[Nexus 4 Original Android Development] sordna:
The changelog talks about a test patch. So I guess people need to test and report to the thread.
[Nexus 4 Original Android Development] freddienuxx:
bootloop

on twrp 2600 when i restore backup it says failed and when i do a rom and gapps its stuck on boot loop

please help thx in advance

---------- Post added at 07:37 PM ---------- Previous post was at 07:15 PM ----------

Can someone help me please

Sent from nexus4
[Nexus 4 Original Android Development] Adizzzle:
What did you do exactly before the restore failed?

Nexus⁴?
[Nexus 4 Original Android Development] cb474:
Thanks for the explanation. I'm not sure I fully understand it. Does this mean that it is no longer possible to make a recovery that will work with all ROMs? Or does it simply mean that the way PA set up the SELinux contexts is wrong and needs to be corrected by PA? Does it really only effect PA or does it effect all AOSP based ROMs, but not CM based ROMs?

Is this also true for those of us who reverted to 2.6.0.0 and then installed PA? Are our SELinux policies also not set up correctly? If so, will installing 2.6.1.1 and dirty flashing PA correct the problem, or would it be necessary to install 2.6.1.1 and do a full factory reset before resinstalling PA?

Thanks for any further explanation.
[Nexus 4 Original Android Development] playya:
have you tried loading up an older version of TWRP and reloading up your rom?
[Nexus 4 Original Android Development] freddienuxx:
I tried vanir rom didn't like it so I went into recovery and did a full wipe and then restored and nothing and when it wants to restore it gets stuck on Google logo! But I figured it out I just wiped it out wit the format
[Nexus 4 Original Android Development] Adizzzle:
So all TWRP hiccups aside,

why is the screen off in the recoveries?

Just wondering, cause I had an i747m,

and the TWRP for that device wasn't

off at all..

By "off" I mean, not centered.
[Nexus 4 Original Android Development] occtec:
IMHO, I have absolutely no issues with 2.6.0.0 TWRP. I am currently on PA3.99 and am able to backup and restore with NO hiccups ;)

NEXUS 4 | PA3.99 | FAUX

---------- Post added at 11:05 AM ---------- Previous post was at 11:04 AM ----------

EDIT: I do my backups using Online Nandroid from the play store and restore with TWRP.

NEXUS 4 | PA3.99 | FAUX
[Nexus 4 Original Android Development] cb474:
Except that if you read Dees_Troy's posts and you used 2.6.0.0 to install PA3.99, then this means that your SELinux policies are probably not set up correctly. SELinux is a very significant new security protocol (actually it's been around for a long time in Linux, but it's new to Android 4.3). It isolates apps and limits the ability of malicious code to operate on your phone.

So as long as you're fine with throwing this security protocol out the door, then it makes sense to say one has no issues with 2.6.0.0.

Whether this is ultimately a problem with PA or with TWRP, it's a significant problem, to which people should pay attention. And it's all the more insidious, because people reverting to older versions of TWRP in order to install the latest versions of PA, based on 4.3, are unwittingly breaking an important part of the security in 4.3. Having a situation where some people break an important part of the security in Android 4.3 and are not even aware that they've done it seems pretty bad to me.
[Nexus 4 Original Android Development] ridikolous:
Anyone got 2.6.1.1 zip?
[Nexus 4 Original Android Development] xanthrax:
get the img file from here

i`ll make a zip asap

http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.6.1.1-mako.img
[Nexus 4 Original Android Development] Holcomb227:
2.6.1.1 is working great when the rom has file_contexts. But I'm getting "No OS Installed" after flashing. I reboot and everything is fine.
[Nexus 4 Original Android Development] 21plays:
6.1.1 works fine

I am on PA 3.99 and had the no radio problem with 6.1. Flashed 6.0 then rom, etc and everything works fine. Now i flashed this new 6.1.1 and no problems. )
[Nexus 4 Original Android Development] Fr33L4nc3r:
Since I made one for myself yesterday, I can share it here :

https://www.dropbox.com/s/wqawtx41yttpbms/TWRP-2.6.1.1-mako_flashable.zip
[Nexus 4 Original Android Development] ciprianruse88:
No more problems with 2.6.1.1 :thumbup::thumbup::thumbup:
[Nexus 4 Original Android Development] nattesh:
I flashed it (2.6.1.1) with goo manager but when i enter the recovery it just says (on the top of the screen) 2.6.0.0. is it correct or goo mngr has failed the flashing operation?

Edit: flashed the .zip. Now it says 2.6.1.1 correctly.

Now I wonder why .img files have troubles to be flashed. With goo manager and so with flashify...

Inviato dal mio Nexus 4 rigato da un momento di entusiazzo
[Nexus 4 Original Android Development] eng.stk:
TWRP 2.6.1.1 flash zip

As usual, here's the flashable zip, the one and original ;) Enjoy!

MD5 hash: 59AB792EAC47D0CB4AA96B06399C0AB2
[Nexus 4 Original Android Development] VivaErBetis:
I never used Goo Manager. But I use Flashify without any problem. It just execute this command under root:

You may try the command yourself using terminal emulation in order to know if there is any error given.
[Nexus 4 Original Android Development] xanthrax:
this is what i`ve done for goo manager to work

http://xdaforums.com/showpost.php?p=45170945&postcount=1282

and yes , flashify works fine also
[Nexus 4 Original Android Development] Geordie Boyo:
So to clarify is 2.6.1.1 the most "stable" version to run? More stable than 2.5.0.0 which the majority of users say is the most stable version?
[Nexus 4 Original Android Development] VivaErBetis:
Maybe 2.6.1.1 is not the most stable but have some advantages that 2.5.0.0 version don't have. For instance, it can create encrypted backups, something very important for those, like me, that doesn't believe in cloud security.

Currently I don't see a point to have an older version installed because there are no antimony bugs in the newer version (that I know).
[Nexus 4 Original Android Development] lorolouis:
BTW, after you flash an recovery image by using such fast, one-shot methods like by Flashify apk from a running ROM,

do you see your TWRP backup folder when start the recovery?

I prefer to use another way to replace the Recovery - WugFresh suite.
[Nexus 4 Original Android Development] RoliSoft:
2.6.0.0 had the backup permission bug, 2.6.1.0 had the baseband removal issue, but in 2.6.1.1 these are all fixed, why wouldn't 2.6.1.1 be more stable (or as stable as) 2.5.0.0? It has new features, updated kernel, and most likely lots of behind-the-scenes small fixes.

Just flashed it with GooManager and everything worked perfectly. For those of you getting older versions and wondering, GooManager does install 2.6.1.1 when clicking on Install OpenRecoveryScript, you should try clearing your data/cache.
[Nexus 4 Original Android Development] VivaErBetis:
Yes. It's like flashing it using fastboot.

---------- Post added at 03:33 PM ---------- Previous post was at 03:29 PM ----------

I think you've answered yourself :)

IMHO these new features needs to be widely tested in order to know it's real stability. But it worth the effort :thumbup:
[Nexus 4 Original Android Development] RoliSoft:
That was mostly aimed at those who still claim that 2.5.0.0 is the latest stable one, I just accidentally quoted you instead of the post above you.
[Nexus 4 Original Android Development] Adizzzle:
TWRP 2.6.1.1

Lime-ified!

So here is a custom TWRP 2.6.1.1 .img that has a custom curtain,

and is completely themed green instead of the default blue.

I have personally tested it, in a few different aspects, No issues so far.

:good:

Download:

https://www.dropbox.com/s/2jnytn51jnxdxmm/openrecovery-twrp-2.6.1.1-mako-green.img

Flashify

in the Google Play store will flash recovery .img's for free,

it is a flawless app, and has awesome reviews, check it out!

Thanks:

[MENTION=3873953]eng.stk[/MENTION]

[MENTION=912474]Dees_Troy[/MENTION]

[MENTION=3946657]xanthrax[/MENTION]

[MENTION=2719389]z31s1g[/MENTION]
[Nexus 4 Original Android Development] xanthrax:
Flashify let's you flash only 3 stuffs a day on free version

I've got the paid one BTW

Good job adizzzle :thumbup:

sent from my Darkside of Nexus 4
[Nexus 4 Original Android Development] Adizzzle:
Oh I didn't realize Flashify had any limitations on the free version.

Thanks for mentioning that, and thank you for the originial .img :good:
[Nexus 4 Original Android Development] sordna:
For free unlimited flashes there is Recovery Tools.

Also Flash Image GUI is free if you download from its xda thread.
[Nexus 4 Original Android Development] Adizzzle:
I'm not sure which one, but I tried flashing an .img

with one of those, and it didn't properly flash.

I think it may have been Flash Image GUI
[Nexus 4 Original Android Development] sordna:
It used to have an issue some time back, I reported it here and it was resolved via an update one day later, the developer is very responsive !
[Nexus 4 Original Android Development] keviv77:
Twice I have faced problems with flashify in past. While flashing kernels and ending up in bootloop. So now just prefer adb fastboot.
[Nexus 4 Original Android Development] Ipse_Tase:
I hope 2.6.1.1 fixes the file permission problem as going from 2.6 back to 2.5 I still ran into problems that required manual intervention.

Noob question: is there a way from Goo manager to flash a DIFFERENT recovery than the latest one? I couldn't find a way to point it to a file.
[Nexus 4 Original Android Development] sordna:
2.6.1.0 and 2.6.1.1 have the permission issue fixed. However, any old backups taken with 2.6.0.0 will still have the bad permission, so I suggest you use the TWRP -> Advanced -> Terminal option to chmod 777 the files.

Haven't used goo manager, but if you use Recovery Tools or Flash Image GUI, both of them allow you to flash a recovery that's already downloaded to your phone. I use a regular web browser to download the .img, and one of those apps to flash it.
[Nexus 4 Original Android Development] Lownita:
I can't successfully flash twrp with either recovery tools or flashify. Just doesn't update from 2.6.0.0.

Tapatalked from my Nexus 4
[Nexus 4 Original Android Development] sordna:
Are you sure you downloaded this file: http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.6.1.1-mako.img ?

The MD5 sum should be d0653e025aa202849ecfff533267325a double check this is the case with your file! I suspect goo manager may sometimes download the wrong file, so I always download it straight from the techerrata website with a browser.

I flashed 2.6.1.0 with Flash Image GUI, and later 2.6.1.1 with Recovery Tools, and both worked fine, so what you are reporting is strange. Try one more time after verifying the md5sum and if it still doesn't work, use a cable and do it with fastboot.
[Nexus 4 Original Android Development] Lownita:
Yes, file is good! Backup of recovery doesn't work either. Just says it was successful, but there is no backup there. Perhaps the apps are reading from the wrong mountpoint. I am using cm10 with Franco's kernel r178.

Tapatalked from my Nexus 4
[Nexus 4 Original Android Development] gadgetguy08:
I had similar problems on a 4.3 ROM and had to set the Goomanager download path to /storage/emulated/legacy/goomanager/ in order for it to install successfully.

Not sure if that is your issue or not.
[Nexus 4 Original Android Development] Lownita:
Really seems to be the problem, here's the log from recovery tools:

Command:

su -c dd if=/storage/emulated/0/Download/openrecovery-twrp-2.6.1.1-mako-green.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

Output:

/storage/emulated/0/Download/openrecovery-twrp-2.6.1.1-mako-green.img: cannot open for read: No such file or directory

Command:

su -c dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/storage/emulated/0/Recovery-Tools/backups/5-8-2013-1:28.img

Output:

/storage/emulated/0/Recovery-Tools/backups/5-8-2013-1:28.img: cannot open for write: No such file or directory

Tapatalked from my Nexus 4
[Nexus 4 Original Android Development] j0hnh0lmes:
Yes. If you already have twrp. Download the version you want. When its done it'll prompt to install. Done.
[Nexus 4 Original Android Development] sordna:
Ok, looks like there's not sufficient error checking in the Recovery Tools app, and there could be something different in your ROM compared to stock. The app has a thread here on XDA so you should report this:

http://xdaforums.com/showthread.php?t=2334554
[Nexus 4 Original Android Development] EstarlinMReyes:
Can someone help me with a problem? I want to update the recovery via fastboot but my computer doesn't recognize my devices and I have the drivers installed.
[Nexus 4 Original Android Development] benjdm:
I was having the same problem and this fixed me up.
[Nexus 4 Original Android Development] technojinn:
Just rooted my phone. So CWN got installed. Trying to switch to TWRP. however, when i try to install from Goomanager, it says it installed, but when i reboot recovery it still has CWM installed. How to successfully change it? I am coming from a GSII.
[Nexus 4 Original Android Development] rmkilc:
See the post right before yours.
[Nexus 4 Original Android Development] technojinn:
THank you. I should have read the thread more. All good now.
[Nexus 4 Original Android Development] blankit:
Is the issue with twrp that it removed the radio modem fixed?
[Nexus 4 Original Android Development] id242:
Read about 20 posts just above yours...

http://xdaforums.com/showpost.php?p=45285955&postcount=1424
[Nexus 4 Original Android Development] lorolouis:
Try WugFresh solution.

http://xdaforums.com/showthread.php?t=2015469

1. Setup the PC drivers

2. Select your current phone / rom OS level

3. Advanced -> Flash(permanent) -> Recovery

It does/fixes everything right , from any situation.

Just be patient because it reboots the phone several times to complete the process!

I think, flashing the Recovery is not a straightforward thing.

In contrast to Radio(Baseband) and Bootloader, which are low level firmware binaries,

the Recovery is a Linux OS itself.

To work properly it should boot and setup its partitions and files properly.

Now, it is even more complex because of SELinux "conflicts" with the 4.3 ROMs
[Nexus 4 Original Android Development] Ipse_Tase:
+1 for WugFresh...it's a powerful tool that takes care of most flashing one would need done. Well worth donating to the author.

That's what I ended up using for TWRP to avoid any mess-up.