{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello guys. I see many of you struggling to find the new compatible version of TWRP that actually works with the new version of JellyBean 4.2.
The issue can be reviewed HERE
Elaborating the above issue in simpler words; it's all due to multi-account stuff in Android 4.2. There's a file called .layout_version in /data partition, when you factory resetted your device using the recovery, the .layout_version file was also wiped during factory reset process as the recovery is supposed to wipe /data (ofcourse excluding the /data/media/ partition as it is the sdcard) partition in this process. So when Android sees that there's no .layout_version file in /data partition it moves the existing data from /data/media/0/ to /data/media/0/0/ and thus forming an infinite loophole of data being moved to other locations at every reset.
So TWRP team came up with an easy solution, that is; not to wipe .layout_version when user executes factory reset command.
There are also many other bug fixes regarding backups and fixing permissions!
You can download here the latest (2.3.2.0) version of TWRP which fixes this bug:
DOWNLOAD
//Thanks to unforgivenmercy for pointing this out: you can also use Goo Manager app from Play Store and flash it by tapping the 3 dots at the top right and then tapping Install OpenRecoveryScript.
Credits:
TWRP Development Team (esp. Dees_Troy for explaining me stuff)
Google
Hope I helped you in any or the other way around.
5pace said:
Hello guys. I see many of you struggling to find the new compatible version of TWRP that actually works with the new version of JellyBean 4.2.
The issue can be reviewed HERE
Elaborating the above issue in simpler words; it's all due to multi-account stuff in Android 4.2. There's a file called .layout_version in /data partition, when you factory resetted your device using the recovery, the .layout_version file was also wiped during factory reset process as the recovery is supposed to wipe /data (ofcourse excluding the /data/media/ partition as it is the sdcard) partition in this process. So when Android sees that there's no .layout_version file in /data partition it moves the existing data from /data/media/0/ to /data/media/0/0/ and thus forming an infinite loophole of data being moved to other locations at every reset.
So TWRP team came up with an easy solution, that is; not to wipe .layout_version when user executes factory reset command.
You can download here the latest (2.3.2.0) version of TWRP which fixes this bug:
DOWNLOAD
Credits:
TWRP Development Team (esp. Dees_Troy for explaining me stuff)
Google
Hope I helped you in any or the other way around.
Click to expand...
Click to collapse
They can also download from goo manager and it will install automatically.
Sent from my Galaxy Nexus using Tapatalk 2
Why would you post this? He has his own thread.
Sent from my Galaxy Nexus using Tapatalk 2
Close this please
Sent from my Galaxy Nexus using xda premium
jriv said:
Close this please
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Why?
God bless...
Why did you make another thread since you are sharing the same thing?
drmxmyt said:
Why did you make another thread since you are sharing the same thing?
Click to expand...
Click to collapse
He is getting the word out there twice as much... twrp should be thankful and if you are for twrp you should be thankful as well...
God bless...
Rule of thumb here: If you did not create it, do not post it.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have decided to post the wipe scripts here for those KernelHolics & Flashaholics that are flashing kernels and ROMs constantly. I've made small modifications to these scripts FULL credit to the originator of them Credits below.
These are compatible with CWM, TWRP.
Since there have been numerous kernels recently being posted and people wondering what to wipe or what not to wiped here is the Kernel Cleaner.
1. Place the file in the root of your /sdcard
2. Flash Kernel Cleaner
3. Flash/Fastboot Kernel
4. Reboot.
Download: http://d-h.st/lkH
This second script I'm sure everyone is familiar with SUPERWIPE script.
Tired of wiping after every ROM or not knowing what to wipe to flash a ROM and have a clean install? Just flash this script & flash ROM easy right?
1. Place Wipe-Script in root of /sdcard
2. Flash Wipe-Script
3. Flash ROM
4. Reboot.
Download: http://d-h.st/9yt
Debug
If it doesn't flash please tell me what recovery your using.
ONLY works for the NEXUS 10 ONLY will be available for other devices as well.
Credit goes to the following people.
Mike1986
AmazingLarry31
Jivy26
I-777
Myself
IF YOU USE/DOWNLOAD THIS SCRIPT PLEASE PRESS THE THANKS BUTTON
Reserved for other Awesome Scripts to make your life easier.
So I do apologize for asking this, I am currently headed out the door or I would look deeper into this the super wipe would also involve wiping our /0 storage right? All of our titanium backup files, game saves...etc etc?
Sent from my SCH-I535 using xda app-developers app
duarian said:
So I do apologize for asking this, I am currently headed out the door or I would look deeper into this the super wipe would also involve wiping our /0 storage right? All of our titanium backup files, game saves...etc etc?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Nope doesn't touch Storage just system, cache, & data. Not /0 or /sdcard. You nor I nor anybody else would want to lose they storage..
Sent from my HTC One S using Tapatalk 2
You sure are Awesome! thanks man
Added to my Index for N10...Good stuff :good:
Found a typo in the awesome wipe.
Instead of saying 'wipe complete you may now flash your ROM'
It says 'wipe complete you may NOT flash your rom'
Otherwise works great !
Sent from my SCH-I535 using xda app-developers app
duarian said:
Found a typo in the awesome wipe.
Instead of saying 'wipe complete you may now flash your ROM'
It says 'wipe complete you may NOT flash your rom'
Otherwise works great !
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I meant NOW thanks I will fix that
Sent from my HTC One S using Tapatalk 2
Superwipe
Hi I i just flashed the superwipe and all my data was erased from the sdcard. Am not sure where to go now? Cant go to the os since theres none... Do i have to go back to factory rom?
Thank you in advance
I have resisted updating my rooted Nexus 7 running stock 4.3 (JSS15R) to kitkat but am now ready to do so.
I know to do a nandroid backup (is doing it via rom toolbox good enough? ) and a fresh tibu backup.
But I have some last minute questions.
1. should I just accept the ota update or as recommended elsewhere should I use the file from
http://forum.xda-developers.com/showthread.php?t=2380113
2. will the update make me lose root? Can that be prevented? (I always have trouble getting the correct drivers to access the Nexus)
3. any other precautions?
Finally : to prevent accidental update before I was ready, I had renamed the system update file when it first downloaded. Now I don't remember where I found it and system will not re-download it with a message that verification failed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Its a nexus device, even if you lose root, it takes like 3 seconds to root it again.. I want to say doing the ota when I first got my nexus 7 did not result in losing root, but I might be incorrect on that one..
Sent from my Nexus 7 using Tapatalk
SwoRNLeaDejZ said:
Its a nexus device, even if you lose root, it takes like 3 seconds to root it again.. I want to say doing the ota when I first got my nexus 7 did not result in losing root, but I might be incorrect on that one..
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I know that is true for most people, but it always takes me a couple of days to get the right drivers working for my windows 7 laptop to communicate properly with the Nexus. Then, once adb and fastboot can access the device, you are correct and the rooting is a breeze. That is why I cringe at having to go through that again.
The drivers are simple.. Just Google "nexus adb drivers" and download them from Google directly. Once you have them downloaded go into device manager, find your nexus, right click it, and select update driver. Choose the have disk option and navigate to the nexus drivers. Should be all set after that. I'll research where the update is stored on your device and reply in a minute.
EDIT: All updates should be downloaded to your /cache partition.
Sent from my Nexus 7 using Tapatalk
SwoRNLeaDejZ said:
EDIT: All updates should be downloaded to your /cache partition.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
My /cache contains 3 folders
Where would I find the ota update file? Maybe I can install it directly.
Anderson2 said:
My /cache contains 3 folders
Where would I find the ota update file? Maybe I can install it directly.
Click to expand...
Click to collapse
If memory serves, when I looked for it before, it was in a "fota" directory under /cache. Look for a zip file.
I don't believe you can install it directly, nor would I want to try anyway.
Once you find it, delete it and then redownload it
Sent from my Nexus 7 using Tapatalk
So has anyone applied the security update and maintained root? I ask this because the update says it will fix security flaws and malicious exploits (root falls here) so has anyone had problems with it and root??? Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I clicked it.
I clicked it and I still have root. Now I am wondering if I screwed up.
Mee too....you probably didn't but I wanted to make sure it didn't break root
4.4 debrick file needed
crazymonkey05 said:
Mee too....you probably didn't but I wanted to make sure it didn't break root
Click to expand...
Click to collapse
sir as u have rooted ur phone please do me a favour please make a debrick file and uplad it if u dont mind as i hardbricked my phone after 4.4 update thanks in advance
OK so I applied the update and root is fine so we are good there.... [saqib] I'm not entirely sure how to create a debrick image
In the how to debrick thread I posted a recovery flashable script you can use. Just flash in recovery and itll do the rest. Once done just upload the debrick.img it created on your sdcard.
If you cant find the script, let me know. Might be several pages back in the thread.
crazymonkey05 said:
OK so I applied the update and root is fine so we are good there.... [saqib] I'm not entirely sure how to create a debrick image
Click to expand...
Click to collapse
How were you notified of the security update? I'm on TMS3KK-1.1-KOT49H.1747UCUFNE4. It's a TW rooted ROM
Is the script for stock recoveries?
And @OKAstro it was in my status bar....you can also go sys. Settings>more>security>security updates
crazymonkey05 said:
And @OKAstro it was in my status bar....you can also go sys. Settings>more>security>security updates
Click to expand...
Click to collapse
I don't see "security updates" under Security
Here is my system info everyone in case its changed
OKAstro said:
I don't see "security updates" under Security
Click to expand...
Click to collapse
If you are on a custom rom it was probably removed by the dev, along with the software update service
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
debrick file method
crazymonkey05 said:
Is the script for stock recoveries?
Click to expand...
Click to collapse
After updating SuperSU, it gave me options to disable KNOX, which disabled the annoying blocking of apps(I believe it did).
2.I installed busybox from the Play Store. I also installed Android Terminal Emulator from the Play Store.
3. I opened Android Terminal Emulator and entered these two lines, entering between them After entering the first, I granted root access, then ran the second line.
su
busybox dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128
4. After those two lines were ran, the debrick.img file was on the root of either the external or internal sdcard. I copied that file to my desktop, and inserted my sd card into my computer(Using the MicroSD to SD Adapter).
5.Finally, I used Win32DiskImager to write the files to the Micro SDcard. After that, I pulled my battery and inserted the Micro SDCard into my phone and it was able to boot into recovery and download mode.
THESE ARE NIGHTLY BUILDS, THERE WILL BE BUGS.
Disclaimer: I take no responsibility for bad things that happen as a result of flashing this.
Prereqs:
- Use kitkat recovery
- Must have unlocked bootloader
Notes:
- Mobile data takes roughly a minute or 2 to come up after a reboot
GAPPS: https://www.androidfilehost.com/?fid=95832962473400228
Nightlies: http://download.cyanogenmod.org/?device=i925
******* OLD BUILDS **********
ROM[1/8/15]: https://www.androidfilehost.com/?fid=95887005526788620
All sources are up on CM's github (cm-12.1 branch): http://github.com/CyanogenMod
Kernel: https://github.com/CyanogenMod/andro...g_smdk4412.git
nice to see you doing more builds, I may try mod this for N8020 with your permission?
This is great work! One question though. Anyone else experiencing slower data speeds even when on LTE?
Is it OK to post the N8020 compatible versions here?
ROM for N8020:
https://mega.nz/#!kQElFSQA!p4hGC9wI95OHS3Ba4YVAfhSBW9oLhKcts6MIUi0Qx-g 14/03/2016 build
Gapps: http://forum.xda-developers.com/android/software/tk-gapps-t3116347
installation steps:
1) Install recovery with odin
2) Wipe Data / Factory Reset in recovery
3) Wipe Cache Partition in recovery
4) Advanced -> Wipe Dalvik Cache
5) Install cm12.1 zip
6) Install Gapps zip
7) Wipe Data / Factory Reset in recovery (just for sure)
8) Advanced -> Wipe Dalvik Cache (just for sure)
9) reboot
Using it now and liking it ??
smegg said:
Is it OK to post the N8020 compatible versions here?
Click to expand...
Click to collapse
sure thing
Sent from my SCH-I605
Here ya go folks...
cm12.1.n8020.zip 229.0 MB
https://mega.co.nz/#!7dAHgJKK!9fOSwj2zsX_W128pQdDeT-GfMj3eCQcHAUPuJaguNNM
30/4/15 build https://mega.co.nz/#!ORIkhb6Z!EBeMkWmzczK0u-sfKB67UO9Ke7LX-rPrQACDuuluvpA
Thank you for your great work!
I want to try N8020 version, but i don't understand well what "Use kitkat recovery" and " Must have unlocked bootloader" means.
My tablet has N8020-CWM-noTouch-6.0.3.6 recovery and root. Is this enough?
smegg said:
Here ya go folks...
cm12.1.n8020.zip 229.0 MB
https://mega.co.nz/#!7dAHgJKK!9fOSwj2zsX_W128pQdDeT-GfMj3eCQcHAUPuJaguNNM
Click to expand...
Click to collapse
Use philZ recovery to install with the GAPPS as well. Also, you' ll need to skip through setup and enable hardware keyboard toggle in language and input to get software keyboard to work. Also you'll need to set mobile network to global and wait a bit for signal to be set up. I recommend the cm spen app from the play store to recognise spen input and it will switch keyboards as well. I used stylus keyboard to write this and it is miles better than Samsung's
Goodluck!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi,
Have flashed the n8020 version and I must say it looks and feels fantastic.
Only issue is netflix and afl (sport streaming app) are not working. YouTube, Hulu and others seem fine.
I understand this is embryonic, but just wondering if others are experiencing similar and have any solutions?
Thanks for any help
Cheers,
crikey! no footy! I'll look into it (if you're not a pies fan..) ?
Not all apps are 5.1.1 ready though...
Ha, indeed no footy would be sad. No, not a pies supporter but have to live with 2 of them.
Using a bit of Google fu I've found a couple of possible fixes
edit 1: I should add the error for Netflix is - sorry we could not reach the netflix service. please try again later. (-9)
Will let you know if I have any success
edit 2:AFL app sorted - uninstall and reinstall did the trick
Cheers
I have the same netflix error... doh!
@smegg, any common bugs that you noticed so far that can impact normal everyday use? Does it feel better than 4.4?
I love it, nice and stable, very snappy, main bug so far is broken video streaming
Respect for your work, developers!
I tested briefly this rom. It looks great and work very good! Thank you, both!
I saw a bug when i did a phone call: couldn't end the call.
Thank you for this rom!
What are the changes in 30.04.2015 release?
And what app can we use for S pen?
Thanks in advance!
Any way to get this for p-605?
vladutgm said:
What are the changes in 30.04.2015 release?
And what app can we use for S pen?
Thanks in advance!
Click to expand...
Click to collapse
cm spen from play store
Hey there,
I want to switch to these htt ps://download .lineageos. org/oneplus2 LOS 14.1 builds as I'm currently using LOS 14.1 by daktak. (Sorry, not allowed to post links right now..)
There haven't been any updates for almost 3 weeks now and I don't think that this will be updated any further.
Well, simply booting into recovery mode and flashing the newest LOS zip doesn't work for me. I guess it's because I'm not wiping my system partition, just data + dalvik cache... I thought I can simply switch/update from an older version of LOS? Do I really need to wipe everything again so I can install the LOS builds I've mentioned above?
Also I don't really understand the difference between signed and unsigned zips. The zip I want to flash is signed. Is this why I get "Failed to flash" as an error message in recovery? Does "signed" mean, I need to root my OP2 again and my current root will be removed?
Current LOS version 14.1-20170213-UNOFFICIAL-oneplus2 by daktak
Yakumichan said:
Hey there,
I want to switch to these htt ps://download .lineageos. org/oneplus2 LOS 14.1 builds as I'm currently using LOS 14.1 by daktak. (Sorry, not allowed to post links right now..)
There haven't been any updates for almost 3 weeks now and I don't think that this will be updated any further.
Well, simply booting into recovery mode and flashing the newest LOS zip doesn't work for me. I guess it's because I'm not wiping my system partition, just data + dalvik cache... I thought I can simply switch/update from an older version of LOS? Do I really need to wipe everything again so I can install the LOS builds I've mentioned above?
Also I don't really understand the difference between signed and unsigned zips. The zip I want to flash is signed. Is this why I get "Failed to flash" as an error message in recovery? Does "signed" mean, I need to root my OP2 again and my current root will be removed?
Current LOS version 14.1-20170213-UNOFFICIAL-oneplus2 by daktak
Click to expand...
Click to collapse
It is all explained here:
http://lineageos.org/Update-and-Build-Prep/
jhedfors said:
It is all explained here:
http://lineageos.org/Update-and-Build-Prep/
Click to expand...
Click to collapse
Thank you for your quick reply! After some issues using adb I could not fix (but I don't need to as I already did this somehow earlier for CM13) I managed to install LOS14.1 HYPE!
Maybe you could help me with my problem?
"No command 'fastboot' found"... But I can find my phone using adb devices.
Screenshot attached...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yakumichan said:
Thank you for your quick reply! After some issues using adb I could not fix (but I don't need to as I already did dis somehow earlier for CM13) I managed to install LOS14.1 HYPE!
Maybe you could help me with my problem?
"No command 'fastboot' found"... But I can find my phone using adb devices.
Screenshot attached...
Click to expand...
Click to collapse
I am not an expert on adb/fastboot, but is the fastboot binary in the directory? It is also a little difficult to interpret the language in your sceenshot.
jhedfors said:
I am not an expert on adb/fastboot, but is the fastboot binary in the directory? It is also a little difficult to interpret the language in your sceenshot.
Click to expand...
Click to collapse
Right, sorry. It's German and it says that the command "fastboot" either has been written wrong or hasn't been found.
And also: Yes, it is:
I think you need to check your drivers
The device should be connected via adb interface driver or android driver
After that you should be able to see ur device