Database Users

[CWM]STOCKw/{N.E.A.K v2.0x}[ICS-4.0.3]{DeOdexed}I9100XWLP4_I9100XXLPS_I9100LUXLP1

This is stock Samsung ICS with the N.E.A.K v2.0x (The Return of the Jedi) Kernel.
I wasnt going to put this in developer as i DIDNT develop this at all. I just put a good kernel with the recent ICS and added some stuff.
NEAK Configurator is installed with this rom.
check out the NEAK v2.0x thread for more details
http://forum.xda-developers.com/showthread.php?t=1576355
Android OS version : 4.0.3
Device : GT-I9100
Model : GT-I9100
ROM Name : IML74K.XWLP4
CSC version : I9100LUXLP1
Rooted (Superuser.apk + su) : YES
BusyBox installed : YES
Apps2SD (Apps to EXT) enabled : NO
/data/app enabled : YES
Custom boot animation allowed : YES
Nano text editor installed : NO
Bash shell support : NO
/system/framework is deodexed : YES
/system/app is deodexed : YES
modem.bin found : YES
ROM will wipe all data : NO
CWM Manager : YES
NEAK Configurator : YES
Custom Boot animation has been enabled, put your boot animation
under the /data/local folder as 'bootanimation.zip'.
LP4 appears to have 2 extra apps, these have been kept in this rom.
./system/app/MMM_for_Smartphone.1.7.3.apk
./system/app/Barcode_Scanner-76.apk
Flash this via CWM - **REMEMBER ALWAYS BACKUP FIRST**
ZIP should be flash from Internal memory card not Externel SD
[CWM]{N.E.A.K_v2.0x}[ICS-4.0.3]{DeOdexed}I9100XWLP4_I9100XXLPS_I9100LUXLP1.zip
[CWM]{N.E.A.K_v2.0x}[ICS-4.0.3]{DeOdexed}I9100XWLP4_I9100XXLPS_I9100LUXLP1.zip
[CWM]{N.E.A.K_v2.0x}[ICS-4.0.3]{DeOdexed}I9100XWLP4_I9100XXLPS_I9100LUXLP1.zip -- sorry for the wait time on this
Currently uploading to other sites should you have difficulty from my Minus account
Credit to
DXIDA
Simone201

[Q] Howto update 41 item pcs of Acer A500 to ICS

Hi all,
I'm newbie in updating android firmware. We have about 41 acer A500, with 3.1 (gingerbread), and want to update all of them to 4 (ICS) official.
I know it just download iconia tab ehnhance from PlayStore + click update.
I just feel update manual of 41 devices is kinda pain with just only 2MB int;l connection.
My POF is save the file in the /cache directory , save to pc, and copy to another tab.
btw i've root all of tab, and familiar with linux command.
1. install terminal > #cp /cache/* /sdcard
arrg whereis the cp command here?
2. install ES File Explorer, copy /cache/* copy to /sdcard
just got a blank folder
3. install cacheDownload2SD
Hoping the cache will appear in /sdcard when the tab download update, nothing happen
I've try coupleof method, not good sor far could someone give enlightment?
Thanks before

Well 41 tabs, u got a mission on yr hands lol....best way is a stock update.zip copy to ext.sd and flash. Not sure if the Acer enhancement app needs to be installed, that may be only for an over the air update...
Getting hold of a full version update.zip might be the hardest part, a lot of the links are dead now. As I remember the stock ics Rom was pretty scrappy almost everyone ran a custom Rom. So I guess it depends on what or how u are using your 41 tabs ???
Sent from my HTC_PN071 using Tapatalk

[ZIP][C6903] 14.6.A.0.368 Central Europe 1, Pre-Rooted, XZDR-locked BL

Hi members.
As the title says i created a flashable zip for myself.
I did not want to wait more to upgrade from my rooted customized ge .270 to .368.
If anybody is intereted i can upload the zip.
DOWNLOAD --> https://drive.google.com/file/d/0Bw5LFMK1hMKmVmdXeEltN20wVmM/view?usp=sharing
I used
XZDualRecovery locked bootloaders v 2.8.21
SuperSU v 2.46
Stock C6903 Customized CE1 1276-4318 14.6.A.0.368 R2D
I flashed the zip with latest twrp recovery and all went fine.
Please use twrp because i red other custom recoverys can cause bootloop.
I wiped cache and dalvik before flashing the zip. Thats all.
Some screens that the flash went fine.

Please members if anybody has downloaded and flashed the zip it would be nice if you can confirm that it is working for you or not.
Sent from my C6903 using XDA Free mobile app

may originate from 146.A.0.368
may originate from 146.A.0.368

Dangba said:
may originate from 146.A.0.368
Click to expand...
Click to collapse
Yes, you can start from .368, but only if you already have a custom recovery installed (e.g., TWRP, clockworkmod, etc.). If you do not, you must downgrade to .270, root, install the recovery, then flash the .368 zip.
Since you are already using .368, my guess is that you do not have custom recovery, so you will need to downgrade, root, then upgrade.

Thanks for creating the flashable zip.
I'll update this post and leave feedback when I get up and running.
Edit:
Hey, been up and running now for a few hours and everything is working as it should.
No problems with root, recovery nor any loss of data.
Cheers again for your efforts, motorazrv3, good job.

Can i flash 5.1.1 from kitkat?

Hello,
I'm having a little problem here... I flashed on top of a rooted .270. I used twrp to flash and wiped cache and dalvik cache before flashing. Flashing itself seemed to work fine. I then restarted the system. Now then phones screen won't turn on. It seems the touch capability of the screen is still working, when i boot the phone, i get the green led and vibration from dualrecovery. If i press down, to enter twrp, the violet led lights up, and it seems i'm booted into twrp, but the screen is still blank. if i tap on the screen, i get vibrarions as usual when tapping on twrp buttons, so i guess twrp is actually running. just the screen does not display anything.I would greatly appreciate any help!
EDIT: Nevermind, it was my own stupidity.... I actually own a Sony Xperia Z1 Compact, so it's obvious this does not work correctly. I was able to get my device back up running by installing the correct zip via adb.

Gamer4Life said:
Can i flash 5.1.1 from kitkat?
Click to expand...
Click to collapse
Yes, if you have custom recovery installed.

I have just installed it and it works without any problems, even with Xposed :good:

DrAcHe981 said:
I have just installed it and it works without any problems, even with Xposed :good:
Click to expand...
Click to collapse
Clean or dirty flash?
Sent from my C6903 using XDA Free mobile app

motorazrv3 said:
Clean or dirty flash?
Sent from my C6903 using XDA Free mobile app
Click to expand...
Click to collapse
Dirty, but for safety I have installed supersu and xzdr again, because I have read that some had problems with the r / w access to the system partition
~sorry when my English is Not the best...

Dirty flash here too (but I also flashed supersu and xzdr again for safety)
Only thing that was odd was I didn't get network, had to go search for it. Pretty sure a reboot would've fixed it.

Dirty flashed from rooted stock .270, all went well!

Root isn't working?
So i downloaded this - wiped with Team Win Recovery, installed this zip rebootet....
- Rom works
- Dual Recovery works
- Root isn't working - tested with Total commander - i gave it root Permission after the app asked for it, but i can't remount /system in rw.
Remount Reboot fix from nut isn't working also:
any ideas? I mean srsly, bootloader is unlocked and i can't use root to edit the freakin host-file -.- For everything else Root is somehow working
Code:
==============================================
= =
= [NUT]'s definitive Remount-Reboot fixer =
= A.K.A. 'the rootfix' =
= =
==============================================
[ 1. SuperSU ]
[ 2. SuperUser ]
[ 3. Abort ]
Which root app do you use? [1,2,3]?1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found
=============================================
Sending the rootfix files.
=============================================
34 KB/s (560 bytes in 0.016s)
503 KB/s (1551 bytes in 0.003s)
33 KB/s (82 bytes in 0.002s)
4014 KB/s (657704 bytes in 0.160s)
1044 KB/s (3217 bytes in 0.003s)
=============================================
Installing the rootfix.
NOTE: If your device reboots without prior
notification, the installation failed
Please take a screenshot or copy
Der Befehl "paste" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
contents of this dosbox to the topic on XDA.
=============================================
Look at your device and grant supersu access
Press any key to continue AFTER granting root access.
-rwxr-xr-x shell shell 657704 2013-06-24 12:59 busybox
Drücken Sie eine beliebige Taste . . .
=============================================
= STARTING ON DEVICE INSTALLATION! =
=============================================
= NOTE: YOUR DEVICE SHOULD NOT REBOOT =
= UNTIL THE INSTALLER SAYS IT WILL! =
=============================================
killing RIC, remount /system rw and temporarily disabling the RIC service...
mount: permission denied (are you root?)
Unable to chmod /sbin/ric: Read-only file system
mount: permission denied (are you root?)
Found busybox, checking if it supports nohup...
It does, EXCELLENT! :)
copying the rootfix files to /system/bin...
cp: can't create '/system/bin/killric.sh': Read-only file system
rm: can't remove '/system/bin/ctrlaltdel': Read-only file system
cp: can't create '/system/bin/ctrlaltdel': File exists
chmod: /system/bin/killric.sh: No such file or directory
chmod: /system/bin/ctrlaltdel: Read-only file system
=============================================
= DONE WITH THE INSTALLATION! =
= NOTE: YOUR DEVICE WILL NOW REBOOT! =
=============================================
Waiting for your device to reconnect.
Remounting system to see if it worked OK
mount: permission denied (are you root?)
Wait 40 seconds to see if it worked, then
Drücken Sie eine beliebige Taste . . .
=============================================
Installation finished. Enjoy your trouble
free root experience
=============================================
Drücken Sie eine beliebige Taste . . ./CODE]

i have resurrection remix 5.1.1 installed can i flash this with twrp or do i need to flash stock rom first? sorry noob question.

Oppoxda said:
i have resurrection remix 5.1.1 installed can i flash this with twrp or do i need to flash stock rom first? sorry noob question.
Click to expand...
Click to collapse
You don't need to flash back to stock first. Flashing this via your custom recovery like twrp does the same as flashing stock with the help of Sony pc companion or any other method.
You only have to decide if you want to go 'totally' clean by wiping your data partition with twrp or doing it 'dirty' and keeping your current data.
Good luck.

Some problem with xPosed installer

Hello,
I have a problem when i want to install xPosed on my phone :
xPosed is not (yet) compatible with Android SDK version 21 or architecture of your processor (armeabi-v7a).(i'm french so i turned the french sentence in english)
CANNOT LINK EXECUTABLE: could not load library "libdvm.so" needed by "/data/data/de.robv.android.xposed.installer/cache/app_process"; caused by library "libdvm.so" not found.
I can't show you a picture because i have under 10 posts...

Go to rovo89's XDA thread for the zip files and download according to your android version (22 for 5.1.1 and 23 for 6.0, etc.) then flash in recovery.

iovyroot - (temp) root tool

Today I present you
iovyroot - (temp) root tool
based on CVE-2015-1805​
Requirements
USB debugging enabled
Settings => About phone => Click 7 times on Android Build to unlock developer options
adb drivers installed
LP Kernel <= Dec 2015
Components
Binary to get root shell
root/iovyroot
Simple TA Backup / Restore script
The author takes no responsibility
tabackup.bat & tarestore.bat (read second post for restore)
Download v0.4
If you found this tool useful, please consider donating (click here)
Supported models:
Code:
- M5 (all variants) (30.0.A.1.23 & 30.1.A.1.33)
- M5 Dual (all variants) (30.0.B.1.23 & 30.1.B.1.33)
- E5803 (32.0.A.6.200)
- E5823 (32.0.A.6.200)
- E6533 (28.0.A.8.266)
- E6553 (28.0.A.8.266)
- E6603 (32.0.A.6.152)
- E6633 (32.0.A.6.152)
- E6653 (32.0.A.6.152 & 32.0.A.6.200)
- E6683 (32.0.A.6.152)
- E6833 (32.0.A.6.170)
- E6853 (32.0.A.6.170 & 32.0.A.6.200)
- E6883 (32.0.A.6.160 & 32.0.A.6.170 & 32.0.A.6.209)
- SGP771 (28.0.A.8.260)
- SGP712 (28.0.A.8.260)
- LG G Flex 2 (5.1.1 LMY47S)
- Possibly all other devices with LP kernel from Dec 2015 or older
Credits:
- @idler1984 for his poc and great help
- @ninestarkoko and @rimmeda for testing
- @ipromeh for fixing ta scripts
XDA:DevDB Information
iovyroot - (temp) root tool, Tool/Utility for the Sony Xperia Z5 Compact
Contributors
zxz0O0, idler1984
Source Code: https://github.com/dosomder/iovyroot
Version Information
Status: Beta
Created 2016-04-01
Last Updated 2016-04-01

Reserved
Questions
Is it possible to get full root without bootloader unlock?
No, dm-verity prevents write access to system
Can we disable dm-verity?
Temporarily yes, but it will be enabled again at next reboot. Any modification to /system would thus result in a bootloop. dm-verity resides in the kernel which we can't modify on locked bootloader.
Can we restore TA partition after unlocking bootloader?
Yes but this will also relock the bootloader. To keep bootloader unlocked and get DRM features back you can use this: http://forum.xda-developers.com/xperia-z5/development/sony-credentials-restore-unlocking-t3296383
A step by step guide by @koonkii can be found at: http://twigstechtips.blogspot.ch/2016/04/sony-z5-compact-root-without-losing-ta.html
How to restore TA partition?
Method 1:
Flash stock firmware from flashtool (supported by iovyroot) (you are now unrooted)
Use tarestore.bat from iovyroot
Method 2 (fully rooted & unlocked bootloader):
Use BackupTA and option "Convert v4 backup"
Restore backup with BackupTA
Flash stock firmware with flashtool

Couldn't download

nice job! reserved for something else..
Please download the latest version by zxz0O0
E5803 (32.0.A.6.200) Malaysia Firmware (FTF)
Google drive link: https://drive.google.com/file/d/0B_uYldsE-h2sRmNlUjZOQVgwQlU/view?usp=sharing
<-- Outdated fixes for v0.1 -->
Fixes:
This file will fix "TA.img" not found issue (backup script fix)
https://drive.google.com/file/d/0B_uYldsE-h2sb1FKM19HMi02TzQ/view?usp=sharing
This file will fix Z5C E5803 malaysia firmware "device not supported" issue and also included TA fix
https://drive.google.com/file/d/0B_uYldsE-h2sTnQ1cUVGX2xfSTg/view?usp=sharing
Older post:
Edit:
E5803 (32.0.A.6.200) Malaysia Firmware (FTF)
Google drive link: https://drive.google.com/file/d/0B_uYldsE-h2sRmNlUjZOQVgwQlU/view?usp=sharing
Edit 2:
@zxz0O0 , there's something wrong with the binary device verification with the E5803 (32.0.A.6.200) Malaysia Firmware. It says "Error: Device not supported"
This modified binary file will work with this firmware:
https://drive.google.com/file/d/0B_uYldsE-h2sMTZKUi1VcjFjM3c/view?usp=sharing
Edit 3:
The backup TA script is not working, looks like the /dev partition style is different with the previous Z series
here is the dir list of the /dev/block
Code:
[email protected]:/dev/block $ ls
ls
bootdevice
dm-0
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p13
mmcblk0p14
mmcblk0p15
mmcblk0p16
mmcblk0p17
mmcblk0p18
mmcblk0p19
mmcblk0p2
mmcblk0p20
mmcblk0p21
mmcblk0p22
mmcblk0p23
mmcblk0p24
mmcblk0p25
mmcblk0p26
mmcblk0p27
mmcblk0p28
mmcblk0p29
mmcblk0p3
mmcblk0p30
mmcblk0p31
mmcblk0p32
mmcblk0p33
mmcblk0p34
mmcblk0p35
mmcblk0p36
mmcblk0p37
mmcblk0p38
mmcblk0p39
mmcblk0p4
mmcblk0p40
mmcblk0p41
mmcblk0p42
mmcblk0p43
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
mmcblk0rpmb
mmcblk1
mmcblk1p1
platform
ram0
ram1
ram10
ram11
ram12
ram13
ram14
ram15
ram2
ram3
ram4
ram5
ram6
ram7
ram8
ram9
vold
zram0
Code:
[email protected]:/dev/block/platform $ ls
f9824900.sdhci
f98a4900.sdhci
anyway, it's confirmed that i got temp root access with this. Great job!
Edit 4:
Okay guys, confirmed that the TA partition for Z5 Compact is located at /dev/block/platform/f9824900.sdhci/by-name/TA
output of the terminal with fix
Code:
iovyroot by zxz0O0
poc by idler1984
[+] Changing fd limit from 1024 to 4096
[+] Changing process priority to highest
[+] Getting pipes
[+] Allocating memory
[+] Installing JOP
[+] Patching address 0xffffffc00194f630
[+] Start map/unmap thread
[+] Start write thread
[+] Spraying kernel heap
[+] Start read thread
[+] Done
[+] Patching addr_limit
[+] Patching address 0xffffffc05b324008
[+] Start map/unmap thread
[+] Start write thread
[+] Spraying kernel heap
[+] Start read thread
[+] Done
[+] Removing JOP
got root lmao
TA.img copied successfully
Press any key to continue . . .
Have a nice day!

Since this is a temp root, presumably we cannot root then upgrade the firmware (to MM) as root will stop working? Correct?

Couldn't download

Here is a mirror in my Google Drive for people struggling to download: https://drive.google.com/open?id=0B3WEA4Yi_XRaeXV0MzdNOHMySE0

devilmaycry2020 said:
Couldn't download
Click to expand...
Click to collapse
anjelz2012 said:
Couldn't download
Click to expand...
Click to collapse
Refresh and try again
3Shirts said:
Since this is a temp root, presumably we cannot root then upgrade the firmware (to MM) as root will stop working? Correct?
Click to expand...
Click to collapse
The exploit here permits to gain temporary Root Command Shell # and backup/restore TA partition using it.
This has nothing to do with SuperSU: you cannot install it and phone apps cannot gain root access using this package. Installing SuperSU (nowadays) involves /system or /boot partition modification, that are prevented by dm-verity, as stated in the 2nd post.

I see, sorry for the dumb question.
So we back up TA partition with this, then unlock the bootloader and get root that way. This just means we can then restore the device later, thanks to backed up TA?
Presumably you cannot restore the TA partition with the bootloader unlocked? Again, sorry if this seems dumb.

Thanks!
Enviado desde mi E6653 usando Tapatalk 2

ipromeh said:
nice job! reserved for something else..
Edit 3:
The backup TA script is not working, looks like the /dev partition style is different with the previous Z series
here is the dir list of the /dev/block
Code:
[email protected]:/dev/block/platform $ ls
f9824900.sdhci
f98a4900.sdhci
anyway, it's confirmed that i got temp root access with this. Great job!
Edit 4:
Okay guys, confirmed that the TA partition for Z5 Compact is located at /dev/block/platform/f9824900.sdhci/by-name/TA
Have a nice day!
Click to expand...
Click to collapse
I do agree, Z5 compact E5823 here.
TA backup script not working NOW: please wait for an update from Zxz0O0 or if you want to correct the backup script yourself, just run the exploit iovyroot and use the command " ls -l /dev/block/platform "
EDIT: fix in the third post thanks to ipromeh

ninestarkoko said:
I do agree, Z5 compact E5823 here.
TA backup script not working NOW: please wait for an update from Zxz0O0 or if you want to correct the backup script yourself, just run the exploit iovyroot and use the command " ls -l /dev/block/platform "
Click to expand...
Click to collapse
You'll have to modify backup.sh to change the command (as root user)
Anyway, I've uploaded a fix at post #4 in case someone need it. I hope zxz0O0 can update his op too :victory:

@ipromeh So did you get backup image and try to restore it?

ipromeh said:
You'll have to modify backup.sh to change the command (as root user)
Anyway, I've uploaded a fix at post #4 in case someone need it. I hope zxz0O0 can update his op too :victory:
Click to expand...
Click to collapse
Thanks for the fix. I changed the script to use the first folder in "/dev/block/platform". This way there is also compatibility for those with msm_sdcc.1

thank you for the great work...
So,
1) backup TA partition with temp root,
2) unlock the bootloader and root the device permanently
3) then we can use DRM restore to have all that SONY stuff working while having root
So the question is in case of re-locking the bootloader and restoring factory condition...is it how it should work?
flash stock firmware, restore TA partition and then re-locking bootloader

3Shirts said:
I see, sorry for the dumb question.
So we back up TA partition with this, then unlock the bootloader and get root that way. This just means we can then restore the device later, thanks to backed up TA?
Presumably you cannot restore the TA partition with the bootloader unlocked? Again, sorry if this seems dumb.
Click to expand...
Click to collapse
Please, wait for the fix in the first post before unlocking or use the fix from ipromeh in the 4th post.
No problem, that's a good question.
After you successfully backup TA partion, if you want SuperSU and root for apps you must unlock the bootloader.
If you want to restore the TA partition in the future, you must/should flash a stock original .tft firmware because if it is like previous Xperia Z phones, restoring TA backup would RELOCK the bootloader and so custom kernel (needed for root) won't boot and the phone would go in bootloop (because locked bootloader refuses to boot not-SOny-signed kernel).
So, you cannot have permanent root (SuperSU) and TA partition restored at the same time.
If you want DRM key functions and root, you must stay unlocked and use the DRM patch provided by Tobias.waldvogel.
These are my thoughts based on my knoledge and experience taken from previous Xperia Z devices.

ninestarkoko said:
Please, wait for the fix in the first post before unlocking or use the fix from ipromeh in the 4th post.
No problem, that's a good question.
After you successfully backup TA partion, if you want SuperSU and root for apps you must unlock the bootloader.
If you want to restore the TA partition in the future, you must/should flash a stock original .tft firmware because if it is like previous Xperia Z phones, restoring TA backup would RELOCK the bootloader and so custom kernel (needed for root) won't boot and the phone would go in bootloop (because locked bootloader refuses to boot not-SOny-signed kernel).
So, you cannot have permanent root (SuperSU) and TA partition restored at the same time.
If you want DRM key functions and root, you must stay unlocked and use the DRM patch provided by Tobias.waldvogel.
These are my thoughts based on my knoledge and experience taken from previous Xperia Z devices.
Click to expand...
Click to collapse
So we can't restore TA backup while using custom kernel? We must flash stock rom then restore TA, Right?

zxz0O0 said:
Supported models:
Code:
- E5803 (32.0.A.6.200)
- E5823 (32.0.A.6.200)
- E6533 (28.0.A.8.266)
- E6603 (32.0.A.6.152)
- E6633 (32.0.A.6.152)
- E6653 (32.0.A.6.152 & 32.0.A.6.200)
- E6683 (32.0.A.6.152)
- E6833 (32.0.A.6.170)
- E6853 (32.0.A.6.170 & 32.0.A.6.200)
- E6883 (32.0.A.6.160 & 32.0.A.6.170 & 32.0.A.6.209)
- Possibly all other devices with LP kernel from Dec 2015 or older
Click to expand...
Click to collapse
Is it possible to add support for Xperia Tablet Z4? And if so, what can I provide to facilitate it? Thanks in advance.

najoor said:
Is it possible to add support for Xperia Tablet Z4? And if so, what can I provide to facilitate it? Thanks in advance.
Click to expand...
Click to collapse
You can try does it work for your device or not, if it doesn't, then you give kernel.elf from LP firmware to OP.

devilmaycry2020 said:
So we can't restore TA backup while using custom kernel? We must flash stock rom then restore TA, Right?
Click to expand...
Click to collapse
If it's like previous Xperia Z devices, yes, you must restore stock pure original firmware (particularly the kernel) because TA restore would automatically relock the bootloader, thus giving device bootloop. And you cannot have permanent root on pure stock kernel (kernel signed by Sony, i'm not talking about stock-based custom kernels), as stated before, so No permanent root and restored TA partition at the same time.
Though, until someone tests it, we cannot be 100% sure that restoring TA partition relocks the bootloader on Z5 devices like it happens on Xperia Z2, Z3,,..