yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Vangelis13:
Any kind soul has the 2.6.0.0 zip handy..?
[Nexus 4 Original Android Development] playya:
I am happy and all works as advertise so I am not in a hurry to change. Just as I am still on 4.2 boot loader since no need to update IMHO
[Nexus 4 Original Android Development] Adizzzle:
If you plan on moving backups or copying them, may I suggest searching in this thread for 'Twrp 2.5.0.0'?

Nexus⁴?
[Nexus 4 Original Android Development] Vangelis13:
2.5.0.0 zip post link: http://xdaforums.com/showthread.php?p=40107184
[Nexus 4 Original Android Development] sordna:
Forks, this seems pretty serious, can one of you file a bug on the twrp github issues page?

https://github.com/TeamWin/Team-Win-Recovery-Project/issues?page=1&state=open

...since in the OP they say they don't follow the various many TWRP threads they use for announcements but need issues properly reported. That's how they fixed the permissions bug, which is now in the "closed" section.
[Nexus 4 Original Android Development] Kocai:
Couldn't you use flashify to flash 2.6.0 img file? Anyway, I use [MENTION=2966468]azrash[/MENTION] 2.6.1 zip file. Here's the 2.6.0 zip file: https://www.dropbox.com/s/mvtgg88334zzqt2/openrecovery-twrp-2.6.0.0-mako.zip
[Nexus 4 Original Android Development] xanthrax:
Twrp 2.6.0.0 zip

http://db.tt/cVhPYXk5

sent from my Darkside of Nexus 4
[Nexus 4 Original Android Development] Emama:
I am coming to ask if 2.6.1.0 fix the copying files to PC (and it seems yes)

but I see new bugs in 2.6.1.0?

So the most stable one is 2.5 now?

Another question is,

since I am coming from CWM and they have the "DUP" mode which can save a lot of space if one is a flashing nerd.

How do you guys do with TWRP?

Like put every backup back to PC and only keep one in the phone?

I just hate that CWM has none of the simple settings like renaming backup nor changing time zone.

Thanks:victory:
[Nexus 4 Original Android Development] casonswag:
What new bugs are on 2.6.1?
[Nexus 4 Original Android Development] occtec:
So guys which is the most stable? 2.6 or 2.5

NEXUS 4 | PA3.99 | FAUX
[Nexus 4 Original Android Development] DesignGrits:
I also lost all signal and data functions after updating and wiping cache/dalvik. Is there a solution for this? Can I just flash 2.6 and then flash radio and baseband?
[Nexus 4 Original Android Development] cb474:
Well, I was trying to upgrade from PA 4.2 to PA 4.3, so restoring my nandroid would have returned me to where I started from. I also wasn't sure if PA 4.2 would have been okay to use with the new radio and bootloader and assumed I would have had to flash back to the older verions.

I don't think it has anything to do with corrupt system files, though I don't really know much about this stuff. But I tried flashing the new bootloader and radio, factory reset, and the flashing the PA ROM and GAPPS several times, always with the same results.

*

So you're having the problem on a ROM other than PA?

*

I'm also curious why people think 2.5.0.0 is more stable than 2.6.0.0.
[Nexus 4 Original Android Development] Chochiwpg:
Yes, I am currently on Purity and I tried to flash PSX with TWRP 2.6.1.0 and couldn't get a network connection. Booted up fine, waited for more than 5 mins and no signal. Booted back into recovery factory reset again and reflashed same issue. Restored my nandroid and network connection was back again. Others were running the same build of the ROM so I don't think it is ROM related.

I have gone back to 2.6.0.0 now so I will test later, but it should be good.
[Nexus 4 Original Android Development] DesignGrits:
I did a full restore and still have no signal....what did you guys do to fix this?
[Nexus 4 Original Android Development] playya:
As a person who had no radio before after wiping and upgrading a rom I found after flashing a radio and wiping like crazy a nandroid which is like I said flashing images of sort to be what got it working for me. Also with TWRP we are talking about what 3 minutes to find out if it works or not. Now as far as flashing bootloader and radio that is not necessary for 4.3, this info can be found within xda. I am on 4.3 with 4.2 bootloader and hybrid radio for quite some time now with no issues. Also if there was an issue you would see if in every thread about 4.3

Now as I have lightly followed TWRP thread and 2.6 I have heard others complain about this recovery and it seems that most are happy with 2.5. As I said earlier I am on 2.4 since it has not caused me any issues at all. Its a recovery and its been a good one for a while and the upgrades in my eye do not bring anything ground breaking that I can not do myself or something I feel I need.

"If it aint broke"

---------- Post added at 06:51 PM ---------- Previous post was at 06:49 PM ----------

did you change recoveries prior to restoring? Going back to an earlier TWRP? If you did and it did not work I guess you may have to flash stock images
[Nexus 4 Original Android Development] occtec:
For those having issue with baseband not showing after upgrade to 2.6.1 Go to recovery and flash 2.6.0.0 reboot recovery. Flash your radio THEN wipe cache THEN wipe dalvik. Now reboot into system. :)

TWRP 2.6.0.0 http://xdaforums.com/showthread.php?p=45200675

THANKS to xanthrax for download link ;)
[Nexus 4 Original Android Development] cb474:
You need to revert to an earlier version of TWRP. If you're using 2.6.1.0 that's causing the problem. TWRP 2.6.0.0 works okay. The solution is discussed above in this thread.

I'm not really sure I understand your point.

As someone noted above, reflashing a nandroid does not reflash the radio and bootloader. And as I said, that would have just gotten me back to my 4.2 version of Paranoidandroid and I was trying to upgrade to 4.3, which was not possible to do with TWRP 2.6.1.0, without messing up the radio. So a nandroid restore just was not a solution for me or anyone trying to upgrade.

In additon, the devs for Paranoidandroid recommend flashing the new bootloader and radio, before upgrading to their version of 4.3. So I'm going to go with what the devs recommend.

I spent hours trying to solve this problem, not 3 minutes. And since the upgrade to 4.3 required a factory reset that also made the process not a couple minute simple thing (I had to restore and redo all my user apps and system data). I'm not going to mess with it now that I got it working.

I understand that you've had similar problems with basebands in the past, but that doesn't mean it's actually the same problem that TWRP 2.6.1.0 seems to be causing now.
[Nexus 4 Original Android Development] DesignGrits:
I don't have a backup to restore to because I just restored to stock JWR66V, rooted and flashed TWRP 2.6 and still no signal. I just flashed the bootloader and radio and custom rom....booting

Second time that I had to do this with an update with twrp....frustrating.
[Nexus 4 Original Android Development] cb474:
As suggested above, I posted to the bug report on this. Right now only me and one other person are reporting the issue there. Others might want to contribute:

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/206
[Nexus 4 Original Android Development] playya:
no problem check post above yours for another way of fixing. Also within my post I was assuming you would then flash an older version of TWRP, generally the one you had prior and try to restore your nandroid.

No biggie though Good Luck and hope it all works out for you :good:
[Nexus 4 Original Android Development] DesignGrits:
The first thing I did when I found out it was an issue with twrp 2.6.1 was I flashed back to 2.6. Been on it since.
[Nexus 4 Original Android Development] playya:
Yea my rule of thumb with TWRP is too never flash it when it first comes out. I have been on other devices and have seen people have issues. I generally stick with what works for me. Upgrading my recovery is normally not as important to me as updating say my rom or radio.. good luck :good:
[Nexus 4 Original Android Development] cb474:
I guess I just don't see the point of the step of restoring the nandroid, if one is upgrading, doing a factory reset, and reflashing everything anyway? It would just add an unnecessary step and not address the real issue, which is TWRP 2.6.1.0.
[Nexus 4 Original Android Development] playya:
The issue is TWRP you are using is flawed, you flash a working TWRP then nandroid your last fully working rom. Now hopefully you boot up and all is well, then you can move forward with new rom knowing that all should work well. Its a step taken strictly to make sure things are back to normal. Its what I would do to test but I understand if you think its unnecessary.

To each his own
[Nexus 4 Original Android Development] cb474:
If you're already on 2.6.0.0, I think you may need to not just reflash the bootloader and radio, but also do a factory reset and reflash your rom and gapps also. I'm just guessing, since I did not try restoring 2.6.0.0 and only flashing the bootloader and radio--you can see above in this thread my description of the steps that solved the problem for me. But some are suggesting it's the wipe of data, done in a factory reset, that may cause the problem. And so perhaps it's also redoing this step with 2.6.0.0 that solves the problem.

That's my best guess. Unfortunately, the factory reset will wipe all your user apps and settings. Hope that helps.

---------- Post added at 04:21 PM ---------- Previous post was at 04:15 PM ----------

I guess that step might have been reassuring for a moment, but it would not have demonstrated to me that the problem wasn't going to recur when I did the upgrade again, that the problem wasn't the new bootloader or radio in conjunction with the 4.3 version of the PA rom or just the new rom itself. So it still seems unnecessary to me. And by leaving that step out, it clearly identified TWRP as the problem. So there was a benefit to not restoring the nandroid (the temporary reassurance that such a step might have provided notwithstanding).
[Nexus 4 Original Android Development] playya:
Being the first to have problems like this simply mean we have to all get together and try and figure it out. Remember there may be more than one solution and from that we can all come to a simplified solution. Either way you unfortunately have to try something so pick one and start there...
[Nexus 4 Original Android Development] DesignGrits:
I did a full restore using N-Cry Toolkit and Nexus Root Toolkit. I fully wiped my device clean, restored to stock JWR66V, rooted my device, flashed 2.6 twrp recovery, flashed customer rom, still no signal so I flashed .27 LTE radio wiped cache/dalvik, updated mobile and phone app settings.. walking around my house trying to get signal, which I usually do. My wife has signal so I know its not a network thing.
[Nexus 4 Original Android Development] cb474:
Okay, but no one else in this thread or in the PA thread is suggesting restoring a nandroid, everyone is saying TWRP is the problem, revert to the older version of TWRP, and then proceed with the upgrade to 4.3. So I guess for others reading this, I'm just trying to save them an unecessary step if upgrading is really their goal. If on the other hand, it's too much of a hassel and they'd rather just stick with their working nandroid of 4.2, then by all means that seems reasonable, but they still need to understand that TWRP 2.6.1.0 is the problem and simply restoring the nandroid is not going to fix the problem, they need to go back to the earlier version of TWRP first.

I think by insisting on the nandroid as a step, it can create some confusion that this will in itself solve the problem. But apparently it won't, either way people need to revert to an earlier version of TWRP, understanding that this is the issue, and only after that do a nandroid or uprade with factory reset and everything.
[Nexus 4 Original Android Development] playya:
ok ok ok man you fail to understand it was a suggestion within troubleshooting and if no one tries it how you can say its unnecessary and wont work but its ok... I am done discussing it, it was merely a suggestion from a user that has come across a few issues in his day thats all. Again To Each His Own....

edit: PM me if you we must discuss this further

Good Luck to everyone and hope you all work out your issues

Playya Out!
[Nexus 4 Original Android Development] cb474:
Did you have a signal after you did the restore and before you rooted, flashed twrp and the custom rom and everything? That seems worth checking, if you didn't.

Unfortunately, I don't really have any other ideas if the steps I used don't solve your problem. Perhaps you have a different problem, from the one related to TWRP?

You might want to look at this thread: http://xdaforums.com/showthread.php?t=2347060. I did not try anything in that guide, so I can't vouch for it. But I came upon it when I was trying to solve this problem, before I realized that reverting TWRP to 2.6.0.0 was the solution for me.

Sorry I don't have any better ideas to help you.

---------- Post added at 04:41 PM ---------- Previous post was at 04:38 PM ----------

I understand your suggestion quite well. I'm just trying to save people some confusion about what this particular issue with TWRP is. I'm just trying to clarify and add information to what you suggested. I'm not sure why you see that as a problem. And I do think insisting repeatedly on the nandroid step, could confuse people about what the issue is, so if it was just a suggestion, I'm not sure why you keep repeating it after me and several other people have more clearly defined the problem.
[Nexus 4 Original Android Development] DesignGrits:
I checked the signal all through out all my steps, still have nothing. I used the NCry tool to restore and it flashes the bootloader, radio, and mako images..it fully restored my device, there should be no reason why I can't get any signal.
[Nexus 4 Original Android Development] cb474:
It seems like if you had no signal after you did the restore and before you did anything else (rooted, flashed custom TWRP recovery, etc.) then the problem you're having is probably not related to the problem with 2.6.1.0. In which case, perhaps the guide I linked to could help you. I really don't know. At this point, it's beyond my level of knowledge.
[Nexus 4 Original Android Development] Adizzzle:
I can't seem to find the radios just in case, and I'm wondering if someone had a link to them for future reference?

Nexus⁴?
[Nexus 4 Original Android Development] sordna:
Google for: factory images for nexus devices, they are part of the stock ROMs
[Nexus 4 Original Android Development] DontPushButtons:
http://xdaforums.com/showthread.php?t=2183555

That thread is pretty much a one-stop shop for reference. Should be a link to a mako modem collection thread in the OP.
[Nexus 4 Original Android Development] ciprianruse88:
I can confirm having no signal after flashing a rom with 2.6.1.0 ...reverting back to 2.6.0.0 or 2.5.0.0(<-- which I recommend) and flashing the rom again with system/data wipe is a fix :thumbup:
[Nexus 4 Original Android Development] DesignGrits:
I'm still at my computer trying to fix this issue, twrp really did a number on my day. Hope I can fix this.
[Nexus 4 Original Android Development] Adizzzle:
Did you try reverting back to an older version of TWRP like the above post?

Nexus⁴?
[Nexus 4 Original Android Development] DesignGrits:
Yep. Tried everything I could think of. Just finished reverting to stock again using adb...as if right now I have no signal. Going to try and flash two other radios and see if it helps. This will be the fourth time I have restored my device via image files/adb...
[Nexus 4 Original Android Development] Adizzzle:
May I suggest Wug's Nexus Toolkit? It had an amazing restore option that saved my phone once already. Just a suggestion.. Hope you get it fixed dude!

Nexus⁴?
[Nexus 4 Original Android Development] DesignGrits:
Thank you but I have already tried it. I've been going back and forth from that toolkit and NCry toolkit and manual adb.

I wish it was as easy as getting a restore from 2.6 from someone else, but I don't know what else to try
[Nexus 4 Original Android Development] Adizzzle:
This is a serious bug for sure especially if it has been giving you this much trouble...

I had updated earlier as well and am now scared ****less to flash any ROM.. ?

Nexus⁴?
[Nexus 4 Original Android Development] VivaErBetis:
Do you know guys where is the IMEI stored? Maybe this TWRP version overwrites it when using the restore option and it causes a complete baseband breakdown.
[Nexus 4 Original Android Development] DesignGrits:
If there is a way for me to make logs or something, please let me know. I am not sure how to document this.
[Nexus 4 Original Android Development] VivaErBetis:
In /cache/recovery there should be a text file called last_log with the actions done in the last TWRP session.
[Nexus 4 Original Android Development] DesignGrits:
Are you referring to the temp file located in the TWRP folder?
[Nexus 4 Original Android Development] VivaErBetis:
No. Once you restarted the normal system after using TWRP, just go to the folder "/cache/recovery" and look for the file "last_log".

To see the file contents in a terminal session use the commands:

su

cat /cache/recovery/last_log
[Nexus 4 Original Android Development] DesignGrits:
FIXED! After this last restore all of a sudden I got signal again. Dang I got like a thousand notifications all at once. Thanks for the help guys. It appears as though the devs are aware of this issue and are checking it out. See google+ for twrp for my info.
[Nexus 4 Original Android Development] Adizzzle:
I'm super happy for you dude!

Nexus⁴?
[Nexus 4 Original Android Development] DesignGrits:
Thank you, I honestly don't know what happened or how I fixed it. Everything I tired I have done before. Now I can sleep in peace. Thanks guys! :D
[Nexus 4 Original Android Development] sordna:
Are you sure they are checking the issue? Can you point to any comments they made (link) ?
[Nexus 4 Original Android Development] DesignGrits:
Sorry, I deleted my post on their google+ by mistake. There was a discussion about it, I believe it was Dees Troy that is the owner of the Google+ account that was responding to my thread. He was going to take a look at all of the report as soon as he has time. You can go to the community and ask for him to clarify the issues.

https://plus.google.com/communities/106804207647688456928
[Nexus 4 Original Android Development] Holcomb227:
I think I've found the issue with 2.6.1.0. The updater script for roms tell the recovery to place parts of the zip into root locations on the device. /boot is set to "/dev/block/mmcblk0p6". Many roms have an updater script that use "/dev/block/platform/msm_sdcc.1/by-name/boot" to send boot.img. Maybe 2.6.1.0 has an issue when using "/dev/block/platform/msm_sdcc.1/by-name/boot"?

I don't know anything this is all a guess. But test it, I've managed to keep data in roms that normally have broken data when flashed.
[Nexus 4 Original Android Development] ciprianruse88:
If this is true then cm based(custom libs/custom recovery scripts) roms I think they will not have any problem with 2.6.1.0

Edit: yep...on slim bean no problem.I think the problem will have most of the users flashing aosp based roms.
[Nexus 4 Original Android Development] Geordie Boyo:
Is there a .zip file that can be flashed through recovery available for the latest 2.6.1.0 version for the Nexus 4 please?
[Nexus 4 Original Android Development] rawdealer:
http://xdaforums.com/search.php?searchid=216442131
[Nexus 4 Original Android Development] xanthrax:
that`s right !

i`ve dome it with vanir n no problems regarding signal as i`ve stated before

someone else with more knowledge than me must find the cause of this issue
[Nexus 4 Original Android Development] Geordie Boyo:
?? When I click the link I just get "Sorry - no matches. Please try some different terms."
[Nexus 4 Original Android Development] xanthrax:
http://xdaforums.com/showpost.php?p=45145766
[Nexus 4 Original Android Development] rmkilc:
There is not a 2.3.3.3 at the moment.
[Nexus 4 Original Android Development] DangKid:
Well how about upgrading recoveries? Because goomanager doesn't have an option for that iirc.
[Nexus 4 Original Android Development] rmkilc:
Yes it does.
[Nexus 4 Original Android Development] cwappy:
There is the install option on the menu in goomanager. However, I can't get that or anything else in there to work. Always says there is no version available for my phone. I have to install TWRP manually.
[Nexus 4 Original Android Development] robto:
Y is, it a issue with compression and temperature: kernel protection does not work in recovery mode.

Just do it with unplugged micro USB power and ..... Check n4 y not too hot before doing an nandroid. Also can blow the back during nandroid.

It n4 shutsdown during nandroid, just wait 5 minutes and restart

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] rmkilc:
What ROM are you using?
[Nexus 4 Original Android Development] ViViDboarder:
Exactly what device do you have? You sure it's mako? Also, are you already rooted? GooManager can't install it without it being rooted yet.
[Nexus 4 Original Android Development] DONNY TRUMP:
Can someone please explain a couple things to me please? 1) everytime I make a backup its usually around 1GB. I thought TWRP compressed backups to make them pretty small in size. Also, 2) when making a back up, do I need to/ SHOULD i keep the "data" box checked? this seems to be 500mb and I made a backup without this checked and everything seemed to work fine. What data is it actually backing up? Only having 16gb of onboard memory I need to save space any where I can. I have titaniumbackup so I could always restore data that way. Any help would be great. Thanks in advance.
[Nexus 4 Original Android Development] rmkilc:
1) Do you have compression enabled? Remember, stuff can only be compressed so far... Mine are usually around 1gb.

2) If you don't back up data, you won't be able to restore any of your personal settings. This is akin to a factory reset, where you are starting out fresh. Personally, the data portion is the most important part of a nandroid. You shouldn't use titanium backup to restore system app data. When backing up data, this is backing up your data partition, as in all your apps and their data/settings. Not miscellaneous files on your internal memory (pictures, music, etc.).
[Nexus 4 Original Android Development] nphil:
I've noticed about half an inch of blank space to the right of the phone using this recovery, seems like its not scaling properly. Tiny annoyance, just thought I'd point it out. I love twrp on all my android devices.
[Nexus 4 Original Android Development] rmkilc:
The Nexus 4's screen is 1280 x 768. TWRP for the Nexus 4 is using the 1280 x 720 theme, since it is pretty close. Hence the extra 48 pixels of black space on the right side of the screen.
[Nexus 4 Original Android Development] jasonwc:
Compressed backups work for me. No issues.
[Nexus 4 Original Android Development] cwappy:
AOKP, from here: http://xdaforums.com/showthread.php?t=2025939

I'm not too concerned about it not working with my ROM (I don't think this AOKP is on goo), but it should at least allow me to install TWRP that way. Right?

---------- Post added at 03:57 PM ---------- Previous post was at 03:52 PM ----------

Pretty darn sure I have a Nexus 4, rooted, running mako versions of TWRP recovery, faux123 kernel, and AOKP. ;) Everything works just fine except, of course, when I go to back up and my phone nearly dies. :rolleyes:
[Nexus 4 Original Android Development] rmkilc:
If the build.prop file is wrong, goo manager won't know your device is a Nexus 4.
[Nexus 4 Original Android Development] Dees_Troy:
The latest version should not be nearly as rough on the battery & should not have the heat issues that earlier versions had. If it's still too much I can downclock the cores further or disable a couple of cores.