yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Original Android Development] dc66:
TWRP 2.8.3.0/CM12/Encryption issue

Hi

I was using TWRP 2.8.1.0 with CM11. Encrypted. Worked fine.

I then upgraded to TWRP 2.8.3.0 and installed CM12. CM12 works fine (asks me for encryption password at start). TWRP also asking for an encryption password, but when entering correct password, I get message "Password Failed".

I then reinstalled TWRP 2.8.1.0, which propose to 'Decrypt Data', but password also fails.

Any idea??

Thanks
[Galaxy Note II Original Android Development] bigbiff:
Hard to say without the log. Guess I broke my signature rule V
[Galaxy Note II Original Android Development] dc66:
Thanks

As the issue is when I am in TWRP, I assume I should get the log from there. When I try to get it, I get message that there is no such file. If Data cannot be decrypted, is a log saved? Sorry, but I am stuck...
[Galaxy Note II Original Android Development] BaGRoS:
2.7.2.1 & 2.8.0.1 I can't clear Dalvik Cache...

Always restart phone to recovery :/

메가 서명.
[Galaxy Note II Original Android Development] DirtyHarrx:
Why don´t you guys provide logs? Neither bigbiff nor any other developer is a clairvoyant.
[Galaxy Note II Original Android Development] BaGRoS:
Because after the restart log is deleted.

메가 서명.
[Galaxy Note II Original Android Development] DirtyHarrx:
You sure about this? Regarding the ways to pull a recovery log let me quote Dees_Troy. I am pretty sure that your log does not get deleted and that one of the following ways will work:
[Galaxy Note II Original Android Development] DarrenNewsgroup:
I used TWRP 2.8.3.0 and formatted the /data and /system to F2FS and set TWRP to remove files rather than format partitions, reinstalled my backup and noticed my ROM seemed more responsive. Yay for F2FS! This was fine for a few days, then I downloaded a .ZIP update for my ROM and booted back into TWRP to do the upgrade. This is when I discovered the boot loop when going into TWRP. I would get the NOTE II boot screen, then TWRP boot screen, then black screen as it rebooted and so the cycle continued.

I tried the recovery from your mat9v link (http://xdaforums.com/showthread.php?t=2637042) which linked to http://www.mediafire.com/download/38pr3a68h8ripwp/Devil-n7100-recovery-signed.zip. The problem here is that is a .ZIP file recovery and unfortunately, I can't boot into TWRP to flash the .ZIP so I tried Odin 3.09 but this wanted a .TAR file. I found a webpage (http://xdaforums.com/showpost.php?p=25866654&postcount=1) that showed how to create a .TAR file. It was originally for converting .ZIP kernel images into .TAR format to use in Odin. I modified it to make the recovery version. I have posted my modified .ZIP to .TAR generator here (https://drive.google.com/file/d/0B9qmMqtg-PQzRmMxYTJZaVBseVU/view?usp=sharing).

So in summary, to get my Note 2 back working I

- downloaded https://drive.google.com/file/d/0B9qmMqtg-PQzRmMxYTJZaVBseVU/view?usp=sharing

- extracted it to a folder called CreateTarForRecovery

- downloaded http://www.mediafire.com/download/38pr3a68h8ripwp/Devil-n7100-recovery-signed.zip

- extracted the recovery.img and put it in the CreateTarForRecovery folder

- ran the tar.bat file in the CreateTarForRecovery folder to create recovery.img.tar file

- flashed the recovery.img.tar file via Odin 3.09

- rebooted my phone and it is back working again

However, it now has Devil Recovery on it and I would like to get it back to TWRP so I can upgrade my ROM (since I don't know if Devil Recovery will format /system and /data back to ext4 or not - I know TWRP will only remove old files rather than format, since I set that option).
[Galaxy Note II Original Android Development] DarrenNewsgroup:
Here are the results after I did the process described in my previous post (http://xdaforums.com/showpost.php?p=58100661&postcount=1934). This may contain the TWRP log files that you need to help track down this boot loop after formatting /system and /data to F2FS.

I got the results via "adb pull" whilst in the Devil Recovery so the /tmp/recovery.log might have Devil Recovery details. However, perhaps the /cache/recovery files have the TWRP logs you are after.

EDIT: I noticed that the /cache/recovery/last_log.1 mentioned f2fs so that might contain something useful.

Now I can recover my phone I am willing to flash TWRP 2.8.3.0 again if you need more log files.
[Galaxy Note II Original Android Development] guma55:
i got the same problem f2fs doesnt worked for me either. cm12 by ivan
[Galaxy Note II Original Android Development] bigbiff:
Does /proc/last_kmsg exist in android after TWRP panics and reboots to android?
[Galaxy Note II Original Android Development] DarrenNewsgroup:
I will try and flash TWRP tonight (from devil recovery), hopefully it will boot loop, then flash devil recovery, then adb pull the information.
[Galaxy Note II Original Android Development] DarrenNewsgroup:
Here is what I did when I got home...

Installed TWRP via Devil Recovery

Powered-off via Devil Recovery

Power on came back in TWRP OK (although I would have expected back in ROM)

Got some logs (results 2)

Powered-off via TWRP

Power on came back in TWRP OK (although I would have expected back in ROM)

Rebooted to ROM via TWRP

Got some logs via ES File Explorer (results 3)

Powered-off in ROM

Power on came back in ROM (as expected)

Powered-off in ROM

Boot with Power+VolUp+HOME (got "Downloading... Do not turn off target!!") - not sure why

Battery pull

Boot with Power+VolUp+HOME (got TWRP boot screen, then black screen, then Note 2 screen, then got ROM)

--- The above was a TWRP crash but did not boot loop forever like before

Got some logs via ES File Explorer (results 4)

Powered-off in ROM

Power on came back in ROM (as expected)

Powered-off in ROM

Boot with Power+VolUp+HOME (let go of buttons after Note 2 screen appeared twice - got TWRP boot screen, then normal TWRP front page - TWRP working OK)

Reboot to system via TWRP

Got some logs via ES File Explorer (results 5)

Rebooted to TWRP via ROM (note - I had powered off in previous cases, this case I used the 4 way reboot menu to recovery)

On reboot I got the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"

Battery pull

Power on (with just the power button) booted into TWRP boot screen, black screen, Note 2 screen, TWRP screen and so on (boot loop)

Battery pull

Power on (with just the power button) - got TWRP boot loop

Flashed Devil Recovery via Odin (auto rebooted into Devil Recovery)

Rebooted to first (and only) system via Devil Recovery - which booted up in ROM (as expected)

Got some logs via ES File Explorer (results 6)

I guess the boot loop is because the bootloader sees the "request to boot into recovery" and TWRP crashes which restarts the phone, bootloader sees the "request to boot into recovery" and TWRP crashes and so on (boot loop). Perhaps most people use the 4 way restart menu in ROM to boot straight to recovery (I certainly do) rather than "power off" in ROM and Power+VolUp+HOME to get into recovery at which point TWRP crashes, phone reboots, but this time bootloader see "request to boot into ROM" so boots into ROM.

Obviously this is all caused by something in TWRP crashing.

Hopefully you can make sense of something in my log files.

Darren
[Galaxy Note II Original Android Development] BaGRoS:
After installation 2.8.3.0, after my attempt to enter into recovery, I always have bootloop, twrp-> restart-> twrp-> restart ...

I tried to install via ODIN older version, it does not change anything, still bootloop.

I had to go to the philz_touch.
[Galaxy Note II Original Android Development] BaGRoS:
LuckyPatcher clear dalvik cache without any problem.

메가 서명.
[Galaxy Note II Original Android Development] bigbiff:
It looks like my kernel is dumping on f2fs corruption that might be handled in devil's recovery kernel. Let me see if I can use a different kernel source. I will attempt to send you a test with DerTeufel's sources.
[Galaxy Note II Original Android Development] DarrenNewsgroup:
Ok, standing by for orders :)
[Galaxy Note II Original Android Development] George_Orever:
I have a TWRP bootloop after converting partitions to F2FS. I will try another CWM to boot system again. [MENTION=2638973]bigbiff[/MENTION], How can help you to solve this problem.
[Galaxy Note II Original Android Development] simo.scorpion:
2.8.4.0 is out !!

Inviato dal mio OnePlus One
[Galaxy Note II Original Android Development] NorthLight:
need help

Hi !

I have a fiend who have a GT-N7105, he has installed TWRP 2.8.4.0 for N7105 by Odin and he lost his imei ... :crying:

Someone have an idea ?

Thanks by advance.
[Galaxy Note II Original Android Development] bigbiff:
TWRP doesn't touch anything unless he restored a bad EFS or something. Did he do anything after installing TWRP? backup/restore of something?
[Galaxy Note II Original Android Development] NorthLight:
No ...

He took this file : http://techerrata.com/file/twrp2/t0lte/openrecovery-twrp-2.8.4.0-t0ltetwrp.img.tar and flashed with Odin.

Odin said RESET and PASSED but TWRP not installed.

I don't understand what was wrong ...

Thanks for answer.

Edit : I know that Recovery not installed after first post ...
[Galaxy Note II Original Android Development] DarrenNewsgroup:
I had a PM from BigBiff saying that he is trying to get kernel sources to make a new build for us to help identify/fix the problem with F2FS. We will need to WAIT until he has done it. In the meantime flash another recovery using my process described in an earlier post.
[Galaxy Note II Original Android Development] George_Orever:
Thank you [MENTION=3931436]DarrenNewsgroup[/MENTION]. You know that, it's insane.

[MENTION=2638973]bigbiff[/MENTION], Finally I successfully convert system (system, cache, data) to F2FS.

More details:

1. Flashed Rom as usual (DN4 v5.2).

2. Created a full backup.

3. Format partitions to F2FS.

4. When restoring breakup, TWRP failed. (After some investigations I figured that, TWRP can't restore backup from second part (like system.ext4.win001).

5. Formatting partitions again to EXT4.

6. Restoring backup, TWRP success to restore from first, second parts.

7. Deleted some apk files from system, uninstalling some apps, to reduce backup size (to make backup one part only) for system and data.

8. Created a full backup aging.

9. Format partitions to F2FS again.

10. Restoring backup, TWRP success.

Also I can boot to TWRP (v2.8.4.0) without bootloop. I don't know why. It's insane like I said before.

Another thing important.

I figured out something don't know if it's normal or not, if you formatting DATA to F2FS it will be remove all folders including (data/media/0) folder. Then if you trying to flash a zip like Agni kernel, it will failed, because Agni kernel need to copy file like (AGNi_reset_oc-uv_on_boot_failure.zip) to (data/media/0) it's already not exist.

So you have two options to solve this issue:

1. Boot to Rom it will create (0) folder in (data/media) again.

2. If you don't have Rom, From TWRP run aroma fm and create (0) folder in (data/media).

Then you can flash Agni kernel or any zip need to access to (0) folder.

Some Roms like DN4 it's including Agni kernel in their Rom. If you formatting DATA partition to F2FS and trying to flash DN4 it will failed because it need (0) folder to be exist.

Can you give TWRP ability to create (0) folder in (data/media), in case we formatting DATA to F2FS.

Thanks.
[Galaxy Note II Original Android Development] bigbiff:
Can you upload recovery.log after a wipe of f2fs for /data?
[Galaxy Note II Original Android Development] George_Orever:
Of course. Please give me some time.
[Galaxy Note II Original Android Development] George_Orever:
So I formatted /data to ext4 and reboot to recovery again and format /data to fsfs. log attached.

Also TWRP failed to backup /data with f2fs. another log attached.

Hope that helps. Thanks.
[Galaxy Note II Original Android Development] bigbiff:
For /data/media we are not creating the 0 subdirectory for backwards compatibility with previous versions of android. I am looking into possible reading a file to see if we should create it or not called .layout_version.

For your backup, it is having issues with /data/app/com.asksven.betterbatterystats_xdaedition-1.apk

Try to see if the file is readable. I have a feeling F2FS is causing file corruption for you.
[Galaxy Note II Original Android Development] javvadi:
Alternate link to download openrecovery-twrp-2.8.4.0-t03g.zip

Is there an alternate download link for openrecovery-twrp-2.8.4.0-t03g.zip? Not able to download from techerrata.com and its not available on goo.im

Thanks
[Galaxy Note II Original Android Development] George_Orever:
Thank you [MENTION=2638973]bigbiff[/MENTION] for answer, Yes F2FS filesystem is the reason for /data partition issues. I tried to backup /data partition after removing above apk, but problem still exist. Tried to backup /data in extsdcard and intsdcard with and without compression, but with no luck.

But, good news is, TWRP success to backup /system (F2FS), /boot, /kernel, /modem and /cache.

So, for now the only solution is back to EXT4 until you solve this issues.

Also, the only way to make TWRP boot (with F2FS, EXT4 working well), is flashing another recovery from odin, clear /cache, flash TWRP again, that makes TWRP work, if I trid to boot TWRP from system, have bootloop.

At the end, I attach a log for my tries (Extract it and see).

Thanks.
[Galaxy Note II Original Android Development] bigbiff:
Whatever f2fs is doing in android, it's corrupting files in /data

You might want to stick to f2fs on read only system and not on writing data to the /data partition. Your files aren't getting synced properly...
[Galaxy Note II Original Android Development] George_Orever:
What can I do in this case, back to EXT4, or there is another solution.

Please can you tell me, it's recovery matter or not.
[Galaxy Note II Original Android Development] bigbiff:
That particular issue is from android where data is being written.

Use f2fs -> system/cache

Use ext4 -> data
[Galaxy Note II Original Android Development] George_Orever:
Thank you [MENTION=2638973]bigbiff[/MENTION] for help. Also soon I will try official Rom, because DN4 is leaked from S3.
[Galaxy Note II Original Android Development] vincentshjuan:
I am on t0lte N7105, flashed the latest 2.8.4.0 and lost TWRP, back to stock recovery. Any idea why this happened?
[Galaxy Note II Original Android Development] apuntigam:
+1 for me, have the same problem. After reading that someone lost IMEI after flashing 2.8.4.0 with Odin, I'm VERY hesitant to try that...
[Galaxy Note II Original Android Development] vincentshjuan:
Will have to revert back to 2.8.1.0 via Odin....
[Galaxy Note II Original Android Development] papei:
Same thing happened to me. I even rebooted into recovery after flashing 2.8.4.0, all was fine. Then when I rebooted into recovery again to flash the latest CM nightly, I got the stock recovery with the robot with a red triangle in his belly. I reflashed 2.8.4.0 with heimdall. 2.8.4.0 seems to be sticking but when I flash the latestest CM12 nightlies it just boot loops.
[Galaxy Note II Original Android Development] apuntigam:
Going back to 2.8.1.0 worked, I'll just keep an eye on this thread until someone says something about 2.8.4.0 being fixed and stable.
[Galaxy Note II Original Android Development] NorthLight:
@ all

I don't know why but you need a rooted N7105 for install a recovery custom.

Root with CF-Auto-Root and it will work perfect ;)
[Galaxy Note II Original Android Development] bigbiff:
Can you do me a favor and get the output of cat /proc/partitions
[Galaxy Note II Original Android Development] vincentshjuan:
Yup Odin back to 2.8.1.0 and I am all good again....
[Galaxy Note II Original Android Development] apuntigam:
Is this what you're after? I hope I did it right...
[Galaxy Note II Original Android Development] bigbiff:
So for you guys who are losing IMEI, it's because part of modem is getting overwritten by recovery. I need to widdle the size of recovery down. You should be able to restore modem to get everything working again.

Can someone test http://techerrata.com/bigbiff/openrecovery-twrp-2.8.4.0-t0ltetwrp.img.tar
[Galaxy Note II Original Android Development] xhizorsz:
Load Modem from Backup

The Tipp with Modem helped me!

I updated my recovery from 2.8.1.0 to 2.8.4.0 with a zip file in the recovery but it reverted me back to stock recovery.

Then I flashed 2.8.4.0 via Odin. I was able to enter Recovery Menu but the ROM don't boots up anymore.

I tried to flash new ROMs, reverted back to 2.8.1.0 tried falshing ROMs again but nothing worked. Every time endless bootscreen.

Loading only the Modem file from an old TWRP backup solved the problem. Maybe this helps some people:good:

Just one other question? Wich TWRP Version do i minimum need to install CM12 nightlies?
[Galaxy Note II Original Android Development] scrin378:
I always update my TWRP recovery with Flashify app from play store...never had any problems...
[Galaxy Note II Original Android Development] keenblade:
I flashed twrp-2.8.4.0 zip file via twrp. No problem here. So I wonder why for some people modem part is overwritten and not for the others? Isn't the boot partition size same for all of our note2? And which partition is the modem flashed into? Boot?
[Galaxy Note II Original Android Development] papei:
I was not able to flash CM12 nightlies with either TWRP 2.8.4.0. or TWRP 2.8.1.0. The phone would just boot loop. In the end I moved to CWM 6.0.4.1 and it worked for me. I don't know what the problem is but somehow TWRP CM12 on the N/105 don't jibe. It is shame as I have been using TWRP for some time now and I appreciate the extra features that it offers.
[Galaxy Note II Original Android Development] bigbiff:
Can you test the tar flashable odin I posted a few posts back please?
[Galaxy Note II Original Android Development] keenblade:
Ok, I will.

Edit: bigbiff, I looked at the tar file you provided, but it is for lte. I have n7100 not n7105. So please post the one for n7100, so I can test. Maybe the problem is only for lte ones.
[Galaxy Note II Original Android Development] bigbiff:
Yes, only the LTE version has the issue so far.
[Galaxy Note II Original Android Development] xhizorsz:
Testet and it don't worked for me. Startet from working Rom + working 2.8.1.0 Recovery. Flashed via Odin and after flashing I can't enter Recovery and Rom don't boot up an second time. Just black screen after the Samsung Galaxy Note II Logo.
[Galaxy Note II Original Android Development] bigbiff:
Did you get /proc/last_kmsg
[Galaxy Note II Original Android Development] xhizorsz:
After I was not able to start anything I flashed 2.8.1.0 with Odin. Is it okay to copy file now?

Here ist the file (Its in a zip folder because single file gets Upload Error):

View attachment last_kmsg.zip:
[Samsung Galaxy Nexus] gavin-phelan:
I just came across this on twiiter about android 4.2 kind of seem real to be honest

http://www.androidpolice.com/2012/1...ick-settings-the-second-pulldown-panel-video/

What do you all think?
[Samsung Galaxy Nexus] Lesicnik1:
Seems awkward.

Especially for one handed usage.
[Samsung Galaxy Nexus] adrynalyne:
Yeah I have a feeling that will get reworked.
[Samsung Galaxy Nexus] WiredPirate:
Double pull down sounds like cluttering to me, I hope not.
[Samsung Galaxy Nexus] raze599:
Seems ok. I would think of an alternative method to access those controls though. They are kind of hidden away to be fair. Maybe implement tabs such as in Sense or Miui.
[Samsung Galaxy Nexus] skyrocket727:
cool i like it :D
[Samsung Galaxy Nexus] jordache16:
Double pull-down for settings make total sense to me. One thing I don't like about the SIII and TouchWiz is with the quick settings and everything at the top there is less room for notifications (as the article points out). It also looks cluttered and it seems like there is way too much going on on the pull down menu. Plus I don't change my settings that often but when I do it's somewhat awkward to pull down the notification bar and then click the little settings icon. It would be easier to swipe down once for notifications and then swipe down a second time for settings. Or, what they could do is have two finger swipe down go directly to quick settings.
[Samsung Galaxy Nexus] NaterTots:
This is from a sense 1.0 rom. Obviously custom but works similar to the 4.2 2 panel set up.

Super convenient.

Interesting how much stuff the devs on xda have created that is merging into official android.

Naters
[Samsung Galaxy Nexus] norpan111:
No let's hope it's exactly like that... It's awesome! It the opposite of cluttered..

Skickat från min Galaxy Nexus via Tapatalk 2
[Samsung Galaxy Nexus] adrynalyne:
Sense 2.1, actually.
[Samsung Galaxy Nexus] I Am Marino:
Interesting to say the least.

-Brought to you by Marino's Galaxy Nexus-
[Samsung Galaxy Nexus] SupaDupaFly24:
I like it! Can't wait for 4.2!
[Samsung Galaxy Nexus] spencer88:
I was gonna say...yeah that's not a Sense 1.0 ROM.
[Samsung Galaxy Nexus] NaterTots:
It is. It was put together by tommy tomato for the evo 4G. It is called classic 1.0.

Quite possible it originated on 2.1. I was just showing people that have only used aosp stuff that is works really well with the double panel pull down.
[Samsung Galaxy Nexus] speedyink:
This was a feature taken from newer releases of Sense that were brought to older releases. My first Android phone was an HTC with Sense 1.0...the toggles were never seen until Sense 2.1 got released, then devs got to porting them to older releases.

Not really a "classic" rom if it has a bunch of Sense 2.1 features...
[Samsung Galaxy Nexus] NaterTots:
Hey I didn't name it. I just used it.
[Samsung Galaxy Nexus] 063_XOBX:
I don't know about anybody else but I'm sold on the double notification bar. Seems like the best middle ground between notification widgets and the settings menu without obstructing the notification panel.
[Samsung Galaxy Nexus] tgyberg:
Ditto :good:
[Samsung Galaxy Nexus] Sinful Animosity:
Great article. I liked how he asked you to try out the double swipe. Not awkward at all.
[Samsung Galaxy Nexus] enik_fox:
I really like the way Motorola implemented it on the droid M. I'd like to see that!
[Samsung Galaxy Nexus] martonikaj:
Except some of the lame cartoon-like icons.
[Samsung Galaxy Nexus] MikeyMike01:
Why not just change the settings button to become a toggle button, like AOKP? The settings button doesn't have much use if you've got a quick panel thing.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] withbloodskies:
Could care less about double swipe, 4.2 sounds nice and I'll be happy to run it when it comes around. Thanks for the post.
[Samsung Galaxy Nexus] Jasonhunterx:
Really good idea it keeps the clean look of android
[Samsung Galaxy Nexus] miketoasty:
As long as 4.2 comes with RoadRunner I will be more than happy!!! (Obvious sarcasm, btw).
[Samsung Galaxy Nexus] spencer88:
Aren't you trying to sell your Galaxy Nexus?
[Samsung Galaxy Nexus] Big ZD:
I know that's sarcasm, but I think there is a half truth to that myth. 4.1.2 seems to have brought much better battery life to the majority of devices now running it (stock and custom). Although that isn't the code name, it's definitely something Google has sought to improve. Do you agree?
[Samsung Galaxy Nexus] Lesicnik1:
Why don't they just make the toggles scroll down along with the notifications when you scroll down?
[Samsung Galaxy Nexus] adrynalyne:
Look at the actual changelog. What change increased battery life?
[Samsung Galaxy Nexus] withbloodskies:
Well.. ever since I tried a 4.1.2 ROM not only was battery better but I had absolutely 0% stutter and slug. It never slowed down at all. So I'd assume 4.1.2 did some vast improvements for performance and battery.
[Samsung Galaxy Nexus] pfmiller:
I've noticed an increase in battery life too. The AOSP change logs are only part of the picture. Google Now is part of Google's proprietary Search app, so any changes to that would not be documented.