yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Nil253259:
Guys..I just flashed V 2.6.1.1 in the zip format. But no matter what I do it always reboots in recovery mode. Then if I select reboot into system it again reboot into recovery each time. I am stuck there. What to do?
[Nexus 4 Original Android Development] Lownita:
Thanks I already donated for mskips toolkit so I might use that instead. But I already flashed latest TWRP with recovery tools now, cm rom was the culprit. No problems on aosp.
[Nexus 4 Original Android Development] Nil253259:
Anyone guys...After flashing even through WugFresh it reboots temporarily into TWRP and then could not detect the device anymore..stuck there...Pls help needed..
[Nexus 4 Original Android Development] Z-Man™:
Do you have a ROM to flash? Maybe you wiped your system and there's no OS to boot into.
[Nexus 4 Original Android Development] Nil253259:
Yup.....many many thanks..I really got scared.....there was no OS....flashed a new one..and everything is OK now...thanks man!
[Nexus 4 Original Android Development] Z-Man™:
Glad you got it figured out
[Nexus 4 Original Android Development] dave4391:
do I flash the V 2.6.1.1 img file as a boot inage or a recovery inage

ta Dave
[Nexus 4 Original Android Development] Michealtbh:
Recovery of course
[Nexus 4 Original Android Development] slickw:
2.6.2.0 is up

anyone have changelog ?
[Nexus 4 Original Android Development] yethz:
TWRP v2.6.2.0 Flashable Zip

Mirror link for all....

Warning:

As always flash at your own risk. I dont take responsibility if your device brick in flashing this.

http://www.mediafire.com/?ymhfa7lxr97xnet
[Nexus 4 Original Android Development] xanthrax:
original img here

http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.6.2.0-mako.img

and all available img , here

http://techerrata.com/browse/twrp2/mako
[Nexus 4 Original Android Development] sordna:
That's great but ... what's new in 2.6.2.0 ?
[Nexus 4 Original Android Development] xanthrax:
not posted yet , awaiting for it too :cowboy:
[Nexus 4 Original Android Development] Adizzzle:
Lemon and Lime version after I get back hone from vacation. Thanks [MENTION=3946657]xanthrax[/MENTION]

Nexus⁴?
[Nexus 4 Original Android Development] xanthrax:
Take your time mate , I will flash it after I see the change log anyway

Nice theme this lime :thumbup:

sent from my Darkside of Nexus 4
[Nexus 4 Original Android Development] beckham_totti:
is it normal that my twrp start up screen doesnt allign?? its kinda left sided... on the right side there were around 3cm tickness with black backgrounds instead all full screen.. happened when i flahsed 2.6.1.1 then tried 2.6.2.0 and still the same..
[Nexus 4 Original Android Development] xanthrax:
Yup , that's normal

sent from my Darkside of Nexus 4
[Nexus 4 Original Android Development] sordna:
Ok, there are comments about it in the google+ page that's listed in the OP. Read the latest comments under the August 30 post titled "WRP 2.6.1.0 is out". The comment from about 2 hours ago says that 2.6.2.0 is only available on grouper and mako and that it's the first recovery able to back up and restore SELinux contexts.
[Nexus 4 Original Android Development] ak:
Do you have compiled twrp from source?
[Nexus 4 Original Android Development] cb474:
Thanks for the tip.

Just for the sake of providing his comments at Google+ here also, Dees Troy writes:
[Nexus 4 Original Android Development] D3VI0US:
anybody having problem restoring stock JWR66Y backup ? ... i tried from 2.5.0.0 up to 2.6.2.0

what the hell is wrong with android 4.3 ?
[Nexus 4 Original Android Development] lorolouis:
WOW!

New releases, no changelogs, "some" SELinux explanations, unanswered questions and people already "themed" and hacked it, other people keep flashing new TWRPs by using all kind of methods.

Half of them not working, the other half don't even know what they are doing :)

Nice.

It use to be the most clean, stable and conservative thread :) here.

---------- Post added at 11:18 AM ---------- Previous post was at 10:34 AM ----------

Got the Dees_Troy master on IRC chat, here is the story, hope it will help others to understand better what happens:

From IRC, (cleaned), Today Sep 06, 2013:

<lorol> hi, 2.6.2.0 changelog?

<@Dees_Troy> I merged in all patches from AOSP bringing TWRP up to a 4.3 base. I merged in all patches from AOSP bringing TWRP up to a 4.3 base. Further, 2.6.2.0 is (I believe) the first recovery to be able to back up and restore SELinux contexts thanks to a patch set from Tassadar.﻿

I also fixed an issue with signature checking when building TWRP against CM 10.2. CM added an extra signature key that caused a problem for us. I suspect that the additional key is going to be used for signing their official builds once CM finishes going commercial

<lorol>I am runing now PA 3.99. How low should I go to make sure all is fully working? Is just flashing the new recovery "over" will be enough as update or I should blank all down to bootloader?

<@Dees_Troy> I'm not sure what you mean. Flashing a new recovery replaces the old one recovery is not a file system, it's a raw image, so there's no way for the contents of the old recovery to affect the new one

<lorol> SELinux s***t - how can confirm it is set properly on runing ROM?

<@Dees_Troy> toolbox's ls command with -V will list the contexts whether it's set up properly by the ROM maker is another story

However if you make or restore a backup from any version of TWRP earlier than 2.6.2.x your SELinux contexts will be lost

<lorol> Do TWRP and ROM share files that setup SElinux while booting, or each one "does" own contexts?

<@Dees_Troy> Right now the latest TWRP builds have things like /file_contexts in the ramdisk but those files come from CM. PA uses a different file_contexts.

I added some code to TWRP to check for and extract file_contexts from update zips

The file_contexts from our ramdisk were breaking the SELinux contexts that were supposed to be set during the zip install of PA because the PA zip was trying to use the CM file_contexts

Frankly that's all a big mess and the blame should go all the way up to Google

the update binary in the zip should be extracting and using the file_contexts from the zip and not hoping/praying that the ramdisk has a proper file_contexts already in place

<lorol> Perfect, Dees_Troy. So from now you detect the ROM's contects and backup/restore them propery? But NOT old backups.

<@Dees_Troy> lorol, that's pretty much the case... the contexts weren't being stored in the backup before so there's no way to restore them from old backups

<lorol> AAAALRIIGHT. Best Regards !!!
[Nexus 4 Original Android Development] wolfboy1984:
I have a borked phone. I am only in recovery... Nothing else is available.

I have a twrp backup I can see in the recovery file manager but I can't move it successfully so that it appears in 'restore' option... Renaming didn't help.

Suggestions please.
[Nexus 4 Original Android Development] Lownita:
So what if I dirty reflash a rom, will file context be proper set again if they were lost through a backup/restore process?
[Nexus 4 Original Android Development] Andre_Vitto:
My goo manager does not install the latest one.. :(..

i dont have rights to install drivers in my office laptop.. so cant flash anything.. I will only be able to get to my personal computer after 3 weeks.. dnt want to wait that long.. any way for me to install the latest version..?
[Nexus 4 Original Android Development] lorolouis:
Some more information about SELinux contexts, 2 shell commands that show you what (if) your ROM has set:

id

ls -Z

Not sure how the output should be interpreted though :)
[Nexus 4 Original Android Development] sordna:
Forget goo manager, just use any browser to download the .img file to your phone, and then flash with an app like:

Recovery Tools

Flash Image GUI

Flashify
[Nexus 4 Original Android Development] ELB27:
Anybody has a 2.6.2.0 flashable zip?
[Nexus 4 Original Android Development] rskyline:
Don't cross post mate. Post over one thread and wait for help. You are getting helped over the cm q&a already.

Enviado desde mi Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] id242:
It was just posted less than 20 posts ago...

http://xdaforums.com/showpost.php?p=45331521&postcount=1461
[Nexus 4 Original Android Development] ELB27:
Thanks.. Missed it somehow
[Nexus 4 Original Android Development] Dungeon47:
2.6 compatible themes appear to be working okay with 2.6.2.0.
[Nexus 4 Original Android Development] stankyou:
I had the impression that the vanishing baseband bug was already fixed but I just tried flashing Cataclysm rom and I lost baseband... I'm on 2.6.2.0. Anyone else still having issues with missing baseband? Or it's the ROM already?
[Nexus 4 Original Android Development] Lownita:
2.6.2.0 hasn't been officially posted here and is not available on goo manager, so it's not bug free I guess?

Tapatalked from my Nexus 4
[Nexus 4 Original Android Development] vikas_toad:
updated to 2.6.1.1 via goomanager

and now touch not working in recovery

flashed via fastboot... still no touch!!!:crying::crying::crying:
[Nexus 4 Original Android Development] zephiK:
Its available on their website, GooManager and thread just haven't been updated.

http://teamw.in/project/twrp2/129

http://techerrata.com/browse/twrp2/mako

Please don't make any assumptions.
[Nexus 4 Original Android Development] lorolouis:
I am duplicating my request from another thread, sorry guys, want to reach the bottom of this bu*******t.

Could someone who did absolutely clean flash of PA 3.99 by using TWRP 2.6.2.0 go to some shell terminal on the phone or ADB, and post what "getenforce" shell command will return.

Appreciated.
[Nexus 4 Original Android Development] Bill Gamble:
Same here. Flashed the latest Cataclysm update using 2.6.2.0 and lost baseband. Downgraded to 2.5.0.0, reflashed and voilà! Baseband.
[Nexus 4 Original Android Development] bronko15344:
Jup same issue here
[Nexus 4 Original Android Development] zephiK:
Baseband fine here. On .33/.54 hybrid
[Nexus 4 Original Android Development] shubu000:
I'm having problem with baseband as well.
[Nexus 4 Original Android Development] lorolouis:
Several questions [MENTION=912474]Dees_Troy[/MENTION] :

When, by who SELinux setenforce state is applied (in general)?

PA ROMs seem to operate on "Permissive" mode, so how come these "foreign" CM10.2 contexts could cause "broken" permissions when the ROM normally doesn't enforces the security ?

Regards
[Nexus 4 Original Android Development] nokiagye:
Hi the compressed backup is the same like the normal or maby something missing? Thanks
[Nexus 4 Original Android Development] vikas_toad:
Anyone??
[Nexus 4 Original Android Development] Bill Gamble:
deleted
[Nexus 4 Original Android Development] karanrajpal14:
[MENTION=912474]Dees_Troy[/MENTION] Hey man, i want to request a feature and I hope you don't mind adding it when possible. Could you add a hardware button test mode link what CWM has? My button doesn't seem to be working properly and it would be useful to test it within recovery because it's easy to rule out if it's a software issue. Hope you oblige! Thanks!
[Nexus 4 Original Android Development] wcn:
Same situation here. Flashed modem in TWRP 2.6.2.0. Working fine now.
[Nexus 4 Original Android Development] thebrainkafka:
Is there a ZIP for 2620?

THX!!
[Nexus 4 Original Android Development] wcn:
http://xdaforums.com/showpost.php?p=45331521&postcount=1461
[Nexus 4 Original Android Development] bronko15344:
Lucky guy. For me it doesn't work :(
[Nexus 4 Original Android Development] Stryder5:
TWRP 2.6.2.0 works fine with the PAC 09/07 nightly. No modem/baseband problems.
[Nexus 4 Original Android Development] apatal:
Did a couple of clean flashes yesterday using 2.6.2.0, and the baseband stayed put. I guess I'm one of the lucky ones. :)
[Nexus 4 Original Android Development] itechengine:
Dees_Troy - I am currently using TWRP 2.4 on my MT6589 Xolo Q800 device, will the latest version compatible with my device?
[Nexus 4 Original Android Development] xanthrax:
Check the website and get the latest for your device

http://www.teamw.in/project/twrp2

sent from my Darkside of Nexus 4
[Nexus 4 Original Android Development] itechengine:
My device (or any other similar device) is not available in the list, can you help me locate one, as i said i am currently using V2.4.1.0
[Nexus 4 Original Android Development] xanthrax:
have you tried to use goo manager ?

go to settings/ install openrecovery script and check which official version is available

and check here for more Xolo Q800 stuffs , you`ll see twrp 2.5 somewhere ... :rolleyes:

http://www.androidjugaad.com/smf/index.php?board=23.0&action=kitsitemap
[Nexus 4 Original Android Development] itechengine:
openrecovery script not helped, On this website (twrp 2.5.0.0) image is corrupt, many users are trapped and lost their baseband and IMEI (including me)
[Nexus 4 Original Android Development] Lownita:
I recently flashed cm with 2.6.2.0 and got no problems.

Tapatalked from my Nexus 4
[Nexus 4 Original Android Development] :
+1

Gesendet von meinem Nexus 10 mit Tapatalk 4
[Nexus 4 Original Android Development] kenkiller:
The problem appears to be only related to Paranoid Android, so those on other variants, you're most probably contributing to nothing. :D
[Nexus 4 Original Android Development] Gustave17:
Nandroid Backup seems not working for me.

It says ok but files are very small ~350 MB...

Using TWRP 2.6.0.0 or 2.6.1.1 or 2.6.2.0...

It worked 3 days ago...

Any idea ?
[Nexus 4 Original Android Development] ferry.82:
Hi i have a problem...i install goo manager, open menu, download And install recovery 2.6.1.1 but when i reboot in recovery i see 2.5.0.0....why this??
[Nexus 4 Original Android Development] lorolouis:
The worst thing is that reporting "2.6.2.0 working fine" with various ROMs means almost nothing in regards of the "(SELinux contexts) issue / fix" neither.
[Nexus 4 Original Android Development] TKD29:
I have the same problem....
[Nexus 4 Original Android Development] xanthrax:
did anyone tried this ?

http://xdaforums.com/showpost.php?p=45170945&postcount=1282
[Nexus 4 Original Android Development] Gustave17:
Seems to be related with my data...

Data backup is just 65 MB...

And twrp shows partition with more than 1000 MB... :what:
[Nexus 4 Original Android Development] TKD29:
Can`t uninstall goo manager..
[Nexus 4 Original Android Development] xanthrax:
hmm ... go to my sig and you`ll find nice guys there ... this thread has been spoiled enough ...
[Nexus 4 Original Android Development] NPuter:
Ok, sorry if this has been already explained, but I've read the past 10 or so pages, and am still quite confused.

Let me first say that I am definitely new to the android modding.

I just got my nexus 4 (replacing a gnex) and would like to get PA 3.99 up and running (what I have on my gnex). Can I just flash the PA zip with 2.6.2.0? Or do I need to use a different version of TWRP. I'm getting really confused with all of these reports of people loosing their baseband, etc.
[Nexus 4 Original Android Development] Adizzzle:
To preserve baseband / radio, use TWRP 2.5.0.0 or 2.6.1.1 also reported working on 2.6.2.0, just read peoples comments and test for yourself. ?

Nexus⁴?
[Nexus 4 Original Android Development] NPuter:
Thank you for the reply! I guess I'm just worried about permanently hurting the phone. From what I gather now, that's not a concern.
[Nexus 4 Original Android Development] Andre_Vitto:
You can use CWM as well.. I prefer TWRP but with all the recent hiccups with TWRP i am doing all my flashing with CWM for the time being...
[Nexus 4 Original Android Development] occtec:
Got a link for the latest cwm for mako ;)

NEXUS 4 | PA3.99 | FAUX
[Nexus 4 Original Android Development] Gustave17:
Please, i need help !

All working but no backup...

With CWM, backup are about 1.51 GB

With TWRP, backup are about 345 MB
[Nexus 4 Original Android Development] Andre_Vitto:
need to search.. I use rom manager to install CWM
[Nexus 4 Original Android Development] paranoid android85:
Go to clockworkmod recovery page and you can flash cwm touch img for free. You have to pay with rom manager I think
[Nexus 4 Original Android Development] NPuter:
Just clean flashed PA 3.99 w/ TWRP 2.6.2.0 and all seems to be working. Nandroid appears to be working correctly as well (judging by the backup size, haven't tried to restore anything).
[Nexus 4 Original Android Development] Andre_Vitto:
Yeah i know.. but I am not kinda recovery fanatic who would theme and dazzle with recoveries.. cwm does my job fine.. and i dnt flash stuffs that often.. mostly stable rom updates.. and they are not that frequent.. so i dnt spend a lot of time in recovery.. Thanks anyways.. :)
[Nexus 4 Original Android Development] defffizz:
Latest twrp always tells me (when I'm in recovery and want to reboot) that my root is lost and asks if I want to fix root permissions (su binary). I installed 2.6.2.0 today via goo manager, and flashed supersu 1.60 after that, but it didn't help. My root works but every time I reboot recovery I get that message. Any fix? Tnx a lot

CM 10.2 + franco
[Nexus 4 Original Android Development] VivaErBetis:
Chainfire, author of SuperSU, said in SuperSU's thread TeamWin is working to fix the issue. As you said root isn't lose.
[Nexus 4 Original Android Development] Jur1nator:
if i try to update via Goomanager.. it downloads the file, says it installed.. but if i boot up into the recovery i am still on 2.6.0

somebody any ideas?

thanks in advance.
[Nexus 4 Original Android Development] carlos67:
Yes there is a fix. I was having exact same issue and ended up tearing my hair out over it.

Basically, if your on twrp 2.6.2.0 you need to completely uninstall SuperSU in supersu settings menu (think it says complete uninstall and cleanup). Then you need to reboot into recovery and flash SuperSU v1.55 and reboot. Once rebooted go to play store and update SuperSU to v1.6 (or latest?).

I did this and it solved it. No more annoying blah blah blah when rebooting out of recovery. ;)
[Nexus 4 Original Android Development] occtec:
Please update to latest Super SU v1.65 http://apicdn.viglink.com/api/click...chainfire.eu/supersu&loc=http://xdaforums.com this will fix lost root issue when rebooting out of recovery. ;)

NEXUS 4 | PA3.99 | FAUX
[Nexus 4 Original Android Development] sordna:
I just installed SuperSU 1.65 via the app store, it asked me to update the binary and reboot. I used normal update of the binary. I then turned off the phone, and went into recovery (TWRP 2.6.1.1) to test, and when I hit reboot the recovery said root might be lost, and whether to fix it. I said no, booted into android, and still have root access.

So I don't think the issue is fixed, if TWRP prompts me to "fix" something that is not proken.
[Nexus 4 Original Android Development] occtec:
Sorry my bad, works with TWRP 2.6.2.0 ;)

NEXUS 4 | PA3.99 | FAUX
[Nexus 4 Original Android Development] Bill Gamble:
Didn't work for me.
[Nexus 4 Original Android Development] VivaErBetis:
The "solution" of reflashing (via play or using the zip file) only works for the first reboot. As said before, SuperSU's programmer Chainfire said that TeamWin is working in a fix.
[Nexus 4 Original Android Development] whisper13:
Quick question, does 2.6.2.0 still has baseband issues?
[Nexus 4 Original Android Development] Bill Gamble:
In my experience, yes.
[Nexus 4 Original Android Development] paranoid android85:
On cm10.2, no problems here
[Nexus 4 Original Android Development] Stryder5:
Works fine with PAC 4.3
[Nexus 4 Original Android Development] Andre_Vitto:
The baseband issue is only with PA rom.. All other roms are fine.. its known..
[Nexus 4 Original Android Development] paranoid android85:
Someone asked, I answered
[Nexus 4 Original Android Development] Whoops!:
Other ROMS and baseband loss

2.6.2.0 Lost my baseband when I flashed Purity20130908
[Nexus 4 Original Android Development] Lownita:
Flashed the same rom yesterday, no problems!

Tapatalked from my Nexus 4
[Nexus 4 Original Android Development] bronko15344:
Flashed cataclysm Rom and lost my baseband too
[Nexus 4 Original Android Development] itechengine:
I tried 2.6.1.1 on my Q800 MT6589 ROM, but had baseband issues, never tried 2.6.2.0
[Nexus 4 Original Android Development] occtec:
2.6.2.0 seems to fix this issue ;)

NEXUS 4 | PA3.99 | FAUX
[Nexus 4 Original Android Development] itechengine:
Could you please point me to the download of 2.6.2.0 compatible for MT6589?
[Nexus 4 Original Android Development] occtec:
Just have to search the forums my friend :eek:

NEXUS 4 | PA3.99 | FAUX

---------- Post added at 03:07 PM ---------- Previous post was at 03:02 PM ----------

You may find something here http://xdaforums.com/showthread.php?t=1825722 don't forget to hit thanks ;)

NEXUS 4 | PA3.99 | FAUX
[Nexus 4 Original Android Development] itechengine:
2.6.2.0 isn't available at that thread...
[Nexus 4 Original Android Development] MykeChester:
Install OpenRecovery via GooManager but still my version is 2.6.0.0 ... running on CM10.2
[Nexus 4 Original Android Development] rskyline:
Try READING the thread, that's been answered before.

Enviado desde mi Nexus 4 usando Tapatalk 4
[Nexus 4 Original Android Development] TKD29:
Is any method to update TWRP without Goo manager?
[Nexus 4 Original Android Development] Ipse_Tase:
Wow...what happened to TWRP? This used to be "set and forget" type of bullet-proof recovery. Now I have to go read 50 pages of possible fixes and see if they are applicable to me, make changes to even export a recovery folder, etc.

I hope it's a transient phase and things will get stable again...I want my peace of mind that I can restore no matter where I am :)
[Nexus 4 Original Android Development] ben_pyett:
Been using recovery for a while. Gone to recover my 4.2.2 backup after trying 4.3 and wanting to revert to daily driver and the restore screen it's empty. Even though there is a backup there sdcard/TWRP/BACKUPS that I can see contains correctly sized backup files.

I did rename the directory to a more sensible name could that have caused this. Although new name has No spaces..

Could I copy backup onto pc and restore them from there?

Any ideas. The only Backup i have was taken using 2622. I can see the files on sdcard but the recovery can't?
[Nexus 4 Original Android Development] jak3z:
Make sure the folder inside BACKUPS contains the serianumber of your device, and inside that one, the backups.
[Nexus 4 Original Android Development] rsdunlop:
Probably your easiest option is to do a backup in TWRP of just the boot partition which will re-create the folder structure for you, then move your 4.2.2 backup into this folder again and it should show up when you try to restore.
[Nexus 4 Original Android Development] manu4204:
for the lazy guys like me searching for the zip :P
[Nexus 4 Original Android Development] itechengine:
Manu - Do you think i should experiment with 2.6.0.0 on my MT6589 device? I tried running 2.6.1.1 and it never worked, baseband issue...
[Nexus 4 Original Android Development] ben_pyett:
brilliant, just needed to backup boot as you suggested and the old backup appeared....as if like magic.

Although, when I tried to perform full restore TWRP said "Failed!" - Ahh!

But it permitted me to individually restore the individual partitions from my backup - strange?!, I did that for each one until I'd done the lot - so fortunately the sum of the parts.....Great

Many thanks

EDIT:

Also had issue with vanishing baseband (but strangely not every time), but that was resolved by reflashing radio when it did happen.
[Nexus 4 Original Android Development] OldGaf:
Just use goomanager....
[Nexus 4 Original Android Development] NPuter:
Clean flashed PA 3.99 on my new N4 (that was already running 4.3) using 2.6.2.0 without any problems at all.
[Nexus 4 Original Android Development] manu4204:
im no dev to advise you

but try it out bro :good:

also try the 2.5.0.0 version:good:

lemme me know the resuts :)
[Nexus 4 Original Android Development] Fr33L4nc3r:
Hope it will fix the issue some user encountered :
[Nexus 4 Original Android Development] eng.stk:
TWRP 2.6.3.0 flash zip

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

MD5 hash: B9A5D2A5C10C648379F9E7BD9FDE5458