Database Users

[Q] Help! Screwed up my TPT!

Well, I was all happy to have rooted. Installed Titanium and when going to remove Lenovo system apps (bloatware), the window had all the boxes checked. So I unchecked what I didn't want and clicked go. Guess what, I uninstalled everything, damn. So now, I turn off the tablet, go into recovery mode to factory restore, cleared cache, now all I get is the never ending Lenovo boot logo. Anyone? How can I restore back using the external storage option in the recovery menu. I have a ROW. Thanks.

you do have a backup in CWM right? (before messing around you always make a backup)
did you try to restore?
If you do not have a backup here is mine(ROW ICS):
http://we.tl/Nb9qAKSlXm
The link is deleted automatically on feb 9.
It should work just fine.
If not then you can try using Nvflash. I can provide images of partitions that you need..

berbecverde said:
you do have a backup in CWM right? (before messing around you always make a backup)
did you try to restore?
If you do not have a backup here is mine(ROW ICS):
http://we.tl/Nb9qAKSlXm
The link is deleted automatically on feb 9.
It should work just fine.
If not then you can try using Nvflash. I can provide images of partitions that you need..
Click to expand...
Click to collapse
Thanks for your help.
No, never got to install CWM. I was under stock ICS rooted when all of this happened. What's next?

Anyone?

well i think that you can not install cwm if your tpt is not booting.
But you could try to see if adb is working.
If not you can use nvflash to restore your partitions.
Since you have the ROW version of the tablet your bootloader should be unlocked, and allow you to use nvflash to restore the partitions to your tpt.
if you need the partitions just let me know.
http://forum.xda-developers.com/showthread.php?t=1745450&highlight=nvflash

berbecverde said:
well i think that you can not install cwm if your tpt is not booting.
But you could try to see if adb is working.
If not you can use nvflash to restore your partitions.
Since you have the ROW version of the tablet your bootloader should be unlocked, and allow you to use nvflash to restore the partitions to your tpt.
if you need the partitions just let me know.
http://forum.xda-developers.com/showthread.php?t=1745450&highlight=nvflash
Click to expand...
Click to collapse
I do need the partitions.
Thanks very much for your help and patience.

did you try to see if nvflash is working?
first you should try and see if it works.
i was thinking that if you use nvflash to flash only the recovery partition then you would have cwm recovery on the tpt and the use it to restore a backup.
i am going to upload the partitions soon.(about 1 hour max).:good:

here is the recovery image.
try it an see what happens.
these are the rest of the image files(2-10):
http://we.tl/cQQ0G2s2RD
NOTE: the 04.ebt.img is the file provided in the nvflash thread not my backup.use it with nvflash like descibed in the thread.
more image files (11-16):
http://we.tl/7vJ49hs0id.
image no. 15 is not there because it is the user data(sdcard).
2. BCT StartSector=0 NumSectors=1024 Boot Configuration Table
3. PT StartSector=1024 NumSectors=512 Partition Table
4. EBT StartSector=1536 NumSectors=1536 Bootloader Table
5. GP1 StartSector=3072 NumSectors=512 ?
6. SOS StartSector=3584 NumSectors=1536 Recovery
7. LNX StartSector=5120 NumSectors=2048 Kernel
8. APP StartSector=7168 NumSectors=196608 Applications in System/ROM
9. CAC StartSector=203776 NumSectors=230400 CAChe
10. MSC StartSector=434176 NumSectors=512 ?
11. PIA StartSector=434688 NumSectors=131072 Pre-Install APK
12. SEC StartSector=565760 NumSectors=5120 ?
13. USP StartSector=570880 NumSectors=35840 ?
14. PDA StartSector=606720 NumSectors=5120 ?
15. UDA StartSector=611840 NumSectors=3234816 User Data (/sdcard)
16. GPT StartSector=3846656 NumSectors=512 ?

berbecverde said:
here is the recovery image.
try it an see what happens.
these are the rest of the image files(2-10):
http://we.tl/cQQ0G2s2RD
NOTE: the 04.ebt.img is the file provided in the nvflash thread not my backup.use it with nvflash like descibed in the thread.
more image files (11-16):
http://we.tl/7vJ49hs0id.
image no. 15 is not there because it is the user data(sdcard).
2. BCT StartSector=0 NumSectors=1024 Boot Configuration Table
3. PT StartSector=1024 NumSectors=512 Partition Table
4. EBT StartSector=1536 NumSectors=1536 Bootloader Table
5. GP1 StartSector=3072 NumSectors=512 ?
6. SOS StartSector=3584 NumSectors=1536 Recovery
7. LNX StartSector=5120 NumSectors=2048 Kernel
8. APP StartSector=7168 NumSectors=196608 Applications in System/ROM
9. CAC StartSector=203776 NumSectors=230400 CAChe
10. MSC StartSector=434176 NumSectors=512 ?
11. PIA StartSector=434688 NumSectors=131072 Pre-Install APK
12. SEC StartSector=565760 NumSectors=5120 ?
13. USP StartSector=570880 NumSectors=35840 ?
14. PDA StartSector=606720 NumSectors=5120 ?
15. UDA StartSector=611840 NumSectors=3234816 User Data (/sdcard)
16. GPT StartSector=3846656 NumSectors=512 ?
Click to expand...
Click to collapse
Great, thanks. I'll give it a shot.

All files are downloaded. Thanks again.
Can't understand the instructions here: http://forum.xda-developers.com/showthread.php?t=1745450
Tablet is seen and installed in device manager (apx) (red think light on) and bootloader seems unlocked, what now?
Detailed instructions ? On the page you sent me it seems that the instructions posted are not pertaining to my situation.

well...
using nvflash you can restore all the partitions on the tablet.
first you must start nvflash, the instructions are quite staight.
" nvflash -w --bl 04.EBT.img --go "
after this you should be able to continue to the next step restore the recovery partition.
(if the 04.ebt.img file is in the same folder as the nvflash, if not you must specify the path, but it is easyer to copy it to the same folder)
you must use the download command
in your case to restore the recovery partition you should use :
" nvflash -r --download 6 6.sos.img "
this will download from the computer the 6.sos.img file to partition no.6 on the tablet, in our case no.6 is the recovery.
after that you should have the CWM recovery, because when i made the backup i had the CWM recovery.
and then try to restore a backup.
another option is to restore the partition that contains the files you deleted.(or all the partitions i provided.)
but that is more complicated since i do not know what partition are we talking about.

berbecverde said:
well...
using nvflash you can restore all the partitions on the tablet.
first you must start nvflash, the instructions are quite staight.
" nvflash -w --bl 04.EBT.img --go "
after this you should be able to continue to the next step restore the recovery partition.
(if the 04.ebt.img file is in the same folder as the nvflash, if not you must specify the path, but it is easyer to copy it to the same folder)
you must use the download command
in your case to restore the recovery partition you should use :
" nvflash -r --download 6 6.sos.img "
this will download from the computer the 6.sos.img file to partition no.6 on the tablet, in our case no.6 is the recovery.
after that you should have the CWM recovery, because when i made the backup i had the CWM recovery.
and then try to restore a backup.
another option is to restore the partition that contains the files you deleted.(or all the partitions i provided.)
but that is more complicated since i do not know what partition are we talking about.
Click to expand...
Click to collapse
Whenever i run nvflash or any command I get the following: pic 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"
}

thisis the nvflash i use and it is working.

berbecverde said:
thisis the nvflash i use and it is working.
Click to expand...
Click to collapse
So many thanks. Worked like a charm. :laugh::laugh::laugh::good::good::good:

Hey,
maybe some of you could help me by my question:
Is it possible to flash a US nandroid Backup to a WE device?
My problem is, that I did not backed up anything and installed CM 9 by Koshu.
Now, I lost the CM9 zip-file, my device is wiped and the links provided by Koshus post are dead
So... right now I got a 64Gb TPT with nothing but CWM and no android version to flash.
I would be really glad if someone could just give me a hint for a solution because I don't know what to do anymore...
Thank you very much in advance for any hint!

not sure it is a good idea to mix the 2 versions.
you should ask someone for a CWM backup.

Thank you very much for your quick answer.
Could anyone provide me at least ZIP-File of CM9 for the Tablet by Koshu?
Maybe I found a solution to restore the original Lenovo-System:
...Try this instead. Assuming you have adb set up and functioning here (none of this will work if you don't.) Also, have USB Debugging turned on and have your TPT set for Charge Only.
Go here: http: // download . lenovo . com / slates / think / tablet1
Download the correct zip for the version of software you're currently running (ThinkPadTablet_A310_02_0039_0086_US.zip is the latest OTA for the 32GB USA Model.)
Open that up and extract the install-recovery.sh file from recovery\etc folder inside of that zip.
Copy that to your android-platform-tools directory (if you don't have that folder added to your path in system variables.)
Open up a command prompt and change to the android-platform-tools folder (if you don't have that folder added to your path in system variables.)
Run the following commands:
Code: [Select]
adb push install-recovery.sh /data/local
adb shell
su
mount -o rw,remount /system
cat /data/local/install-recovery.sh > /system/etc/install-recovery.sh
dd if=/system/recovery-from-boot.p of=/dev/block/mmcblk0p1
Power off your TPT.
Power on your TPT.
Let it boot fully then power off your TPT again.
Power on your TPT while rapidly hitting Vol +
With luck, you'll be booted back into the stock recovery.
Click to expand...
Click to collapse
What do you guys think about this solution? If someone could provide me a working ROM (like CM9) I could connect via adb and get the stuff right.
Thank you in advance for your help!

[n80xx] CyanogenMod 10.2 Dual Boot

{
"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"
}
For anyone interested, below are the steps for getting your device dual-booting with CyanogenMod 10.2.
Why?
I don't want to erase native firmware and want to give a try to CyanogenMod
I want to have both native and CM, because I like native Samsung S-Pen apps, but want to have more fresh Android too
I like experimenting - it's cool!
The Idea
Our Android device has 2 boot partitions - for normal boot, and to boot into recovery. If I want to boot CyanogenMod, I need to place its boot image instead one of those boot partitions. E.g. if I want to have both native firmware and cyanogen - then obviously I need to replace recovery partition. However I can do the backup of recovery and restore it later if needed.
But, I also need to place cyanogen system and data partitions somewhere. Putting it on the external sdcard makes CM working really slow, repartitioning internal memory might be good idea, but it is not so easy and is not necessary for experimenting. Thus I've created 2 image files and put it to native data partition (mmcblk0p12) to media folder, e.g. into internal sdcard, then changed cyanogen boot image to mount those image files on boot as system and data partitions.
Prerequisites:
Rooted Samsung Galaxy Note 10.1 2012 Edition
2GB of free disk space at internal sdcard
Recovery partition backup, because we are going to replace it with CyanogenMod boot image
Clear understanding of what you are doing, because you potentially can break your device
Downloads:
CM 10.2 boot image
CM 10.2 data partition image
CM 10.2 system partition image
Steps
This manual suggests that you are going to do the recovery backup to external sdcard and has native firmware which means that recovery partition is mmcblk0p6, data partition is mmcblk0p12 and internal sdcard is /mnt/sdcard folder (otherwise you need to change the commands appropriately and might need to fix cyanogen boot image too).
Download 3 files by the links above and upload to internal sdcard of your device. Connect to your device via ADB and run ADB shell, or type the next commands in terminal emulator:
Code:
# become root
su -
# go to external sdcard to create recovery backup
cd /mnt/extSdCard
dd if=/dev/block/mmcblk0p6 of=./recovery.img
# go to internal sdcard folder
cd /mnt/sdcard
# unpack partition images - each is 1Gb of disk space
gunzip ./system.img.gz
gunzip ./data.img.gz
# write CM boot image to recovery partition
dd if=./cyanogen.img of=/dev/block/mmcblk0p6
# finish
exit
exit
Now you can reboot your device into recovery mode and see CyanogenMod booting.
Restoring native recovery:
If you got tired from CyanogenMod and/or would like to take back your recovery, please use the backup you've done before. Lets say it is placed on your external sdcard, then connect to your device via ADB and run ADB shell, or type the next commands in terminal emulator:
Code:
# become root
su -
# go to the folder with recovery backup
cd /mnt/extSdCard
# write recovery image over recovery partition
dd if=./recovery.img of=/dev/block/mmcblk0p6
Please let me know If I missed anything in my steps.
P.S. What I've changed in Cyanogen boot.img to make it using img files instead of partitions in form of patch: View attachment cyanogen_boot_img.patch. It is also necessary to create /host folder in initrd folder tree.

wow!!
it's really hard to be done xD
i thought it will be as easy as it was on my old Galaxy S2
all what i needed to do is to restart the phone and press home to boot to second Rom
i hope it's going to be easier soon
and thank you for you efforts toward our device Development

MoNsTeRmUk said:
wow!!
it's really hard to be done xD
Click to expand...
Click to collapse
Well, it is not as hard as it probably seems Download 3 files and overwrite recovery partition.
Probably I need to compose something like zip file for CWM or TWRP when I have free time... But if would be really nice if someone get it working too following current steps

X-Stranger said:
Well, it is not as hard as it probably seems Download 3 files and overwrite recovery partition.
Probably I need to compose something like zip file for CWM or TWRP when I have free time... But if would be really nice if someone get it working too following current steps
Click to expand...
Click to collapse
I really Appreciate your work here brother And as it seems our device is not getting much of the attention unlike other devices
And what i meant by hard is it's possible to be done without any mistakes , but i take sometime to do so and you need a computer every time you want to change the Rom so it's not a solution for every time use .
I wish you good luck and Thank you for your support

MoNsTeRmUk said:
I really Appreciate your work here brother And as it seems our device is not getting much of the attention unlike other devices
And what i meant by hard is it's possible to be done without any mistakes , but i take sometime to do so and you need a computer every time you want to change the Rom so it's not a solution for every time use .
I wish you good luck and Thank you for your support
Click to expand...
Click to collapse
Thanks for kind words Actually you don't need to have the computer to change ROM, you can type commands from terminal emulator directly from Android. I'm also thinking about creating small Android app which can be installed to each ROM and will be able to switch boot partition within one click.

Thanks for this superb work. Can't download last file ?
Please if can make someone flashable zip it would be great I am a noob but I want try this thanks again
Sent from my GT-N8000 using Tapatalk HD

other roms
Can I do this this with another rom

maro_X said:
Can I do this this with another rom
Click to expand...
Click to collapse
It is possible, but your another rom must be specially modified for this.
What rom are you talking about exactly?

Multi-boot solution
I've tired of writing images to boot partition every time I want to switch between native firmware and Cyanogen, so decided to compose a little program that I was talking before. So let me introduce you N8xx Boot Manager!
The idea:
You put your boot images files to some folder on your sdcard, lets say to /mnt/extSdCard/images/boot
And recovery boot images to /mnt/extSdCard/images/recovery
Now you run Boot Manager and select what you want to boot as normal boot or as recovery
As soon as you selected it, the application asks you if you would like to write this image to the appropriate partition (boot or recovery)
After successful writing it will ask you for booting from that partition, e.g. propose to reboot into your another rom or recovery
For sure all the settings like path where to keep images and boot/recovery partition names can be fixed appropriately to your device at the Settings tab
For sure the application requires root permissions, e.g. your device must be rooted. You can also check this from Settings tab
The application file: View attachment bootmanager-1.0.apk - feel free to install it to your device and use posting me bug reports
P.S. The only thing I've forgotten - the button to create native boot image file backup You still need to do it manually, sorry Hopefully in next release, if there be people interested in N8xx Boot Manager
P.P.S. Generally this program can be used for any device - just put correct images and correct boot partition names
P.P.P.S. Why N8xx and not N8xxx or N80xx? Because I've missed one symbol when typed application name in Android Studio and was too lazy to change that later :laugh:

N80xx Boot Manager
Updated version of N80xx Boot Manager: View attachment bootmanager-1.1.apk
Changelog:
Fixed application name
Fixed images path detection when no settings were changes
Added "Backup boot partiton" and "Backup recovery partition" buttons
Thus, now to install CM 10.2 as dual boot you don't need to go to ADB or terminal - just upload 3 img files to your device proper locations, installl boot manager apk, create stock boot/recovery partitions backup, then select what you want to boot and boot to that rom!
P.S. Going to update first post of this thread with steps based on Boot Manager, just would be nice if someone confirm that it works.

swamimahesh said:
Can't download last file
Click to expand...
Click to collapse
Re-uploaded.

I love u man
Finally alittle love for our device :crying:

Do I have to reinstall apps when booting to cm?
edit: I dont really understand the first step when you extract data and system.img. Can you explain more clearly the procedure?
edit2: did anyone do this dualboot successfully?

data.img.gz
Hi,
Thanks for this post !
The unpack data.img.gz don't work for me, an error occurs (with several softwares).
The md5 is ok.
Could you repost this file ?
TY.
:angel:

I can not use the n80xx boot manager app. It was failed to back up recovery or boot img. And it can not detect backup folders also. I am using revolution hd9 on n8000
Sent from my GT-N8000 using Tapatalk

netj said:
Hi,
Thanks for this post !
The unpack data.img.gz don't work for me, an error occurs (with several softwares).
The md5 is ok.
Could you repost this file ?
TY.
:angel:
Click to expand...
Click to collapse
Looks like file hosting has disk issues thus my files become broken. System.img re-uploaded already. Now please try that View attachment data.img.gz and let me know if it works for you.

muop_92 said:
I can not use the n80xx boot manager app. It was failed to back up recovery or boot img. And it can not detect backup folders also. I am using revolution hd9 on n8000
Sent from my GT-N8000 using Tapatalk
Click to expand...
Click to collapse
I'm using the same Revolution HD 9.0 by mike1986 and it works for me. The backup might fail if backup folder is not available. By default it is trying to use external sdcard for backups, it is looking for /mnt/extSdCard/images/boot and /mnt/extSdCard/images/recovery paths for the purpose. Please create those folders if you don't have it, or change boot manager settings according to your thought where the backups should be. The boot and recovery folders should exist anyway, e.g. it is up to you to create them.

X-Stranger said:
I'm using the same Revolution HD 9.0 by mike1986 and it works for me. The backup might fail if backup folder is not available. By default it is trying to use external sdcard for backups, it is looking for /mnt/extSdCard/images/boot and /mnt/extSdCard/images/recovery paths for the purpose. Please create those folders if you don't have it, or change boot manager settings according to your thought where the backups should be. The boot and recovery folders should exist anyway, e.g. it is up to you to create them.
Click to expand...
Click to collapse
Where is /mnt ? I saw in my device only /storage/extSdCard
Sent from my GT-I8160 using Tapatalk 2

muop_92 said:
Where is /mnt ? I saw in my device only /storage/extSdCard
Click to expand...
Click to collapse
It's the same. External sdcard is available on both these paths as far as I know. You can change it otherwise in application settings tab.

Ok !
X-Stranger said:
Looks like file hosting has disk issues thus my files become broken. System.img re-uploaded already. Now please try that View attachment 2519204 and let me know if it works for you.
Click to expand...
Click to collapse
Hi,
It's Ok !
Thanks !
I have just modify the paths :
dd if=/dev/mmcblk0p6 of=./recovery.img --> dd if=/dev/block/mmcblk0p6 of=./recovery.img
dd if=./cyanogen.img of=/dev/mmcblk0p6 --> dd if=./cyanogen.img of=/dev/block/mmcblk0p6
:good:

[ROOT] Verizon X8.3 VK815 OTA [root injection] + Images

This method is not mine. Original thread is HERE. I am simply making it work for our Verizon LG x8.3 VK815.
With the introduction to the newer OTA update, rooting ability using the old method has been broken. This means we have to follow the new method for achieving root similar to the LG G4. This requires pulling the system image, injecting root, pushing the system image back to the device.
Here are the steps to Root your Verizon LG x8.3 VK815
Follow JUST the first step here to get setup with the Download Mode and send_command:
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
It has links to the VERIZON drivers and the resources to get this done.
Here is the specifics for the LG VK815 to backup SYSTEM image:
STEP 1: BACKUP SYSTEM IMAGE said:
From Download Mode, using the send_command.exe
Code:
dd if=/dev/block/mmcblk0 bs=8192 skip=44992 count=458752 of=/data/media/0/system.img
Once that is done, we have to change permissions
Code:
mv /data/media/0/system.img /data/media/0/Download
Code:
chown media_rw:media_rw /data/media/0/Download/system.img
Code:
chmod 664 /data/media/0/Download/system.img
Code:
chcon "u:object_r:media_rw_data_file:s0" /data/media/0/Download/system.img
Type LEAVE to reboot back into Android. Open a ADB terminal and copy the System.img to your PC
Code:
adb pull /storage/sdcard0/Download/system.img .
Click to expand...
Click to collapse
STEP 2: INJECT ROOT (SKIP STEP IF VERSION ISN'T LISTED BELOW) said:
You need a Linux environment for this.
I used VirtualBox and this Ubuntu 12.10 Image:
http://sourceforge.net/projects/vir...untu Linux/12.10/ubuntu-12.10-desktop-i386.7z
user/pass: ubuntu/reverse
Load up Ubuntu and Log in. Download Inject Root Files. Copy system.img and contents of Inject_Root_G4.zip to desktop.
Load up a Terminal and "cd Desktop"
Code:
sudo chmod +x autoroot.sh
sudo ./autoroot.sh
Your "system.img" should change to "rootedsystem.img"
Copy this out of your VM and copy back to the root of your internal storage on your LG G Tab x8.3 VK815
Click to expand...
Click to collapse
I am uploading the 11A Stock OTA System Image Here:
StockSystem
Code:
MD5:cda4e8ce36f009403a45f00f29c58fff
Here is the ROOTED 11A OTA System Image:
Download Rooted System Image - Mirror
Code:
MD5: 165bc9152f20e66623477870c574500b
STEP 3: PUSH ROOTED SYSTEM IMAGE said:
Boot back into Download Mode. Now we copy and install the rootedsystem.img into our operating system partition:
Code:
dd if=/data/media/0/rootedsystem.img bs=8192 seek=44992 count=458752 of=/dev/block/mmcblk0
Type LEAVE and reboot.
Click to expand...
Click to collapse
ENJOY!
Special Thanks to @smason for help and @hackarchive for the original walkthrough!
{
"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"
}

Wrong device, wrong Forum.
Please ask in the Q and Forum for your device - thanks.

Yea the new update breaks the existing root methods. There currently is no way TO root, but I think we can root it similarly like we do on the G4.
You basically pull the system image (using the command I posted), open it up on the PC, copy in the root files, and push the whole root system image (3.5gb) back to the phone.
I would recommend doing a factory reset and do not sign in to google, install apps, etc. The tablet is 16gb and you'll have both images on your G4. You might not have enough internal storage space with apps installed.
I do not have the UPDATE installed, nor do I want the update unless I KNOW it can be rooted. So if you can pull the system image for me and upload it, I will try to inject the root and you can try it. You'll have BOTH system images on your tablet, so if the rooted one doesn't work, you can just flash the original.

Anyone on the OTA able to pull a stock system image to upload?
I have no intention of taking the OTA if it cannot be rooted. I will help anyone looking to root the new update.

player911 said:
Anyone on the OTA able to pull a stock system image to upload?
I have no intention of taking the OTA if it cannot be rooted. I will help anyone looking to root the new update.
Click to expand...
Click to collapse
Hi there, im now trying to root it using this method. If its right i would update my img :cyclops:

I am having problems copying the image off of the device. I tried doing it though adb pull and shell and just a straight copy. Keep getting permission errors. I rerooted my 11A tab to try permissions.

player911 said:
I am having problems copying the image off of the device. I tried doing it though adb pull and shell and just a straight copy. Keep getting permission errors. I rerooted my 11A tab to try permissions.
Click to expand...
Click to collapse
I have the same problem too, i can't move/copy the system.img. Any solutions of this?

Update to pull system.img
Code:
#mv /data/media/0/system.img /data/media/0/Download
#chown media_rw:media_rw /data/media/0/Download/system.img
#chmod 664 /data/media/0/Download/system.img
#chcon "u:object_r:media_rw_data_file:s0" /data/media/0/Download/system.img
#ls -laZ /data/media/0/Download/system.img
-rw------- media_rw media_rw u:object_r:media_rw_data_file:s0 system.img
#
Thanks to @smason for the help.

I have pulled the stock OTA system image, injected root, and about to flash it now. If successful, I will upload the rooted system.img.
The OP is sort of a mess right now while I am adding notes and steps. If I am successful, I will organize it better. The steps for flashing is 1 line
EDIT!
SUCCESS!

Another thread that should be stickied.

Agreed as this method will probably be the standard for all updates going forward unless LG blocks it.
Unlike the G4, additional steps need to be taken to get the image off your device because they locked down permissions.
I am interested in hearing of how this works for others. I've been all over this for a while and my instructions may skip details.

Is the link for the rooted system file broken?

Skizzy034 said:
Is the link for the rooted system file broken?
Click to expand...
Click to collapse
I confirm that the download link doesn't work for me. Like you said in the other thread, it just takes me to the site's main page.

roirraW "edor" ehT said:
I confirm that the download link doesn't work for me. Like you said in the other thread, it just takes me to the site's main page.
Click to expand...
Click to collapse
=/ That sucks.

This worked for me. I FINALLY got my x8.3 rooted. Uploading the rootedsystem.img file to FileDropper right now. Will share the link as soon as it is uploaded.
Edit:
FileDropper wouldn't hand over the link to the file so I'm uploading it to MediaFire now. Will post link as soon as it is uploaded.
Edit:
File is uploaded (Remove spaces): www . mediafire .com /download/ qnx4f9bzxage96o/ rootedsystem.img

Cool!
I'll update the OP links with your mirror.
Can you provide a MD5 checksum? I think I zipped the original to save file size so the MD5 will be different.
Looks like both of my links have died. I'll reupload the Original and Rooted images up to other services tonight. I was excited when I finally got it and threw it up on the first host that would support the size.

player911 said:
Cool!
I'll update the OP links with your mirror.
Can you provide a MD5 checksum? I think I zipped the original to save file size so the MD5 will be different.
Looks like both of my links have died. I'll reupload the Original and Rooted images up to other services tonight. I was excited when I finally got it and threw it up on the first host that would support the size.
Click to expand...
Click to collapse
I'd be glad to post the MD5... as soon as I figure out how to get that... I have no idea, never done that before. xD Normally I just wait for everyone else to fix things like this and I download their hard work but I decided it was time for me to step up to the plate.
EDIT:
I believe I got the MD5 for it. I used WinMD5Free v1.20 so I hope I'm not just being an idiot here (Never learn until you stick your neck out.)
MD5: 5e151c2126263423a1602fd39eb2db47

So the only step we need to do is push the system image you provided?

I would back up your system image too, but not needed.
You should just copy the rootedsystem.img to your internal storage and use the DD command from Download mode to copy it over.

player911 said:
I would back up your system image too, but not needed.
You should just copy the rootedsystem.img to your internal storage and use the DD command from Download mode to copy it over.
Click to expand...
Click to collapse
Will an android terminal work?

[GUIDE] How to Change Boot Logo (Splash Screen) for Redmi Note 4

Note:
This is not bootanimation, this is the splash screen (the 'Mi' boot logo which is displayed when device is switched ON)
This is for Xiaomi Redmi Note 4 (mido/whatever) Only (Snapdragon Variants)..
(For variants other than mido, please post your splash.img here so that I can check if it can work in your device)
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Xiaomi Redmi Note 4 (Snapdragon) (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
(For devices with latest firmware, use this tool: https://forum.xda-developers.com/showpost.php?p=75231024&postcount=48)
1. Download & Extract this: Redmi_Note_4_Splash_Maker.zip
2. Make sure you have a picture with resolution 1080x1920 or lower.
Note:
Redmi Note 4 logo has a fixed size of 100kB allocated for splash image frame buffer, so only very light-weight pictures can be used.
(If you alter this limit in the script, fastboot picture will not appear in fastboot mode..)
It's recommended to use picture with 3 or 2 colors only, like Black & White pictures.
So you'll have to try many pictures till you get a successful one.
3. Now rename your picture as logo.png or logo.jpg according to its format & replace it inside "pics" folder of the extracted folder.
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img , which you can find inside the "output" folder after completion.
Note:
You'll get an error like "PICTURE IS LARGE IN SIZE" if it's not possible to create a logo with that picture.
In that case, try any one of these below:
a. Try compressPNG.com to reduce no. of colors in PNG picture.
Upload your picture, click Settings, reduce number of colors to 2, Apply & download it & try again.
b. Reduce the picture resolution.
For example, this picture:
{
"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"
}
can edited to something like this:
(Hope you understand what I say)
c. Try some other picture.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
(Not necessary though.. You may get it from the stock firmware itself.)
Now, Choose any one easy method to install:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Credits:
1. Based on my original tool for Redmi Note 3
2. @Ravi Kumawat who provided the stock splash.img of Redmi Note 4 (mido - Snapdragon) & tested this tool.
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
FOR MEDIATEK VARIANTS:
For MTK devices, you might have a different partition for that called 'logo'.
Browse in /dev directory to find out where that is present.
After you have found out, dump the logo.bin file by:
Code:
dd if=/<the_directory_where_logo_is_present>/logo of=/sdcard/logo.bin
Now you can edit the logo.bin using this tool:
Changing Boot Logo (logo.bin) - LOGO BUILDER Program
After editing, you can reflash it by:
Code:
dd if=/sdcard/logo.bin of=/<the_directory_where_logo_is_present>/logo
If you did this successfully, please share the details of how you did it so that it will be helpful for others..
Or if that tool doesn't work, send me your logo.bin or splash.img, I'll check it..

Thanks @GokuINC for the tool.?

Haha - just like the Moto G - pretty neat. ?

Thank you so much for this tool! I can't seem to flash a particular logo. It automatically flashes a black and white Google logo instead. I've attached the image here. Please look into it.

google splash for redmi note 4 thanks to @GokulNC for tool
Google - https://www.androidfilehost.com/?fid=673368273298958840
Iphone - https://www.androidfilehost.com/?fid=745425885120736058

Thanks buddy! You made my day today!
---------- Post added at 18:09 ---------- Previous post was at 17:40 ----------
getting this error
-------------------------------------------
Creating splash.img ........
Traceback (most recent call last):
File "bin\logo_gen.py", line 291, in <module>
MakeLogoImage(GetPNGFile(), "output.img")
File "bin\logo_gen.py", line 260, in MakeLogoImage
body = GetImageBody(img, SUPPORT_RLE24_COMPRESSIONT)
File "bin\logo_gen.py", line 250, in GetImageBody
return encodeRLE24(background)
File "bin\logo_gen.py", line 217, in encodeRLE24
assert bytesProcessedInBody <= payloadLimit, "\n\n\nPICTURE IS LARGE IN SIZE..\nQuitting..."
AssertionError:
PICTURE IS LARGE IN SIZE..
Quitting...
PICTURE IS LARGE IN SIZE
Quitting
Press any key to continue . . .
---------- Post added at 18:19 ---------- Previous post was at 18:09 ----------
get img file as output. how to flash in twrp recovery
---------- Post added at 18:39 ---------- Previous post was at 18:19 ----------
Problem Solved
to reduce the picture size you may use half pixel eg (1080*1920)/2,3 etc

GokulNC said:
Note:
This is not bootanimation, this is the splash screen (the 'Mi' boot logo which is displayed when device is switched ON)
This is for Xiaomi Redmi Note 4 (mido/whatever) Only (Snapdragon Variants)..
(For variants other than mido, please post your splash.img here so that I can check if it can work in your device)
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Xiaomi Redmi Note 4 (Snapdragon) (any ROM)
2. Optional:Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
1. Download & Extract this: Redmi_Note_4_Splash_Maker.zip
2. Make sure you have a picture with resolution 1080x1920 or lower.
Note:
Redmi Note 4 logo has a fixed size of 100kB allocated for splash image frame buffer, so only very light-weight pictures can be used.
(If you alter this limit in the script, fastboot picture will not appear in fastboot mode..)
It's recommended to use picture with 3 or 2 colors only, like Black & White pictures.
So you'll have to try many pictures till you get a successful one.
3. Now rename your picture as logo.png or logo.jpg according to its format & replace it inside "pics" folder of the extracted folder.
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img , which you can find inside the "output" folder after completion.
Note:
You'll get an error like "PICTURE IS LARGE IN SIZE" if it's not possible to create a logo with that picture.
In that case, try any one of these below:
a. Try compressPNG.com to reduce no. of colors in PNG picture.
Upload your picture, click Settings, reduce number of colors to 2, Apply & download it & try again.
b. Reduce the picture resolution.
For example, this picture: can edited to something like this:
(Hope you understand what I say)
c. Try some other picture.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
(Not necessary though.. You may get it from the stock firmware itself.)
Now, Choose any one easy method to install:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
c. To flash from Fastboot mode:
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Credits:
1. Based on my original tool for Redmi Note 3
2. @Ravi Kumawat who provided the stock splash.img of Redmi Note 4 (mido - Snapdragon) & tested this tool.
Hit the Thanks:good: button if it worked for you
You're welcome to post the splash images that you created..
FOR MEDIATEK VARIANTS:
For MTK devices, you might have a different partition for that called 'logo'.
Browse in /dev directory to find out where that is present.
After you have found out, dump the logo.bin file by:
Now you can edit the logo.bin using this tool:
Changing Boot Logo (logo.bin) - LOGO BUILDER Program
After editing, you can reflash it by:
If you did this successfully, please share the details of how you did it so that it will be helpful for others..
Or if that tool doesn't work, send me your logo.bin or splash.img, I'll check it..
Click to expand...
Click to collapse
I used 46KB pic of size 354x354 all blackandwhite, still large pic size error

yashgumaste said:
I used 46KB pic of size 354x354 all blackandwhite, still large pic size error
Click to expand...
Click to collapse
compress to 3 kb

rameshurfrnd1 said:
google splash for redmi note 4 thanks to @GokulNC for tool
Google - https://www.androidfilehost.com/?fid=673368273298958840
Iphone - https://www.androidfilehost.com/?fid=745425885120736058
Click to expand...
Click to collapse
It's funny because the only images that worked are the ones you posted here as .zip files. I tried numerous 1080x1920 jpgs, tried compressing and resizing them to 720x1280 etc. etc, even tried compressing a .png file all were black and white and sized lower than 100kb and nothing worked, it phone always used a stock Google logo.

Deleted

naren12 said:
Hey it works. I'm not using that google logo. I modified it and it works for me. I'm free all the time. If u want some i can create one for u. Just post the image. I will do for u
Click to expand...
Click to collapse
http://i65.tinypic.com/28mpwxw.jpg
Can you please try converting this one to a zip?

menskiz0r said:
http://i65.tinypic.com/28mpwxw.jpg
Can you please try converting this one to a zip?
Click to expand...
Click to collapse
Yes.

naren12 said:
Yes.
Click to expand...
Click to collapse
Thanks, it worked. But it's not stretched for a full screen. Is it compressed to a very small size?

menskiz0r said:
Thanks, it worked. But it's not stretched for a full screen. Is it compressed to a very small size?
Click to expand...
Click to collapse
I don't know. But is of lower resolution. I will try to make another one with 1900x1080 resolution. Is it ok for u if the background color was black?

naren12 said:
I don't know. But is of lower resolution. I will try to make another one with 1900x1080 resolution. Is it ok for u if the background color was black?
Click to expand...
Click to collapse
yeah sure

menskiz0r said:
yeah sure
Click to expand...
Click to collapse
Try this

a Bug found though ;_;
http://imgur.com/tJzjUh6.png
ps: fixed

thamk man, but i have a problem here, ive tried many file but cannot change, still linux logo, any way to fix i? thanks

erwanPutra said:
thamk man, but i have a problem here, ive tried many file but cannot change, still linux logo, any way to fix i? thanks
Click to expand...
Click to collapse
Can u explain in detail?

thankyou so much

[F3111][Guide][N][33.3.A.1.115] Root with Working patched DRM fix (without ta backup)

Hi all!
Happy to share a workaround for root and successful DRM fix.
If you lose your drm key, that's okay, this fix will restore all function which depends on it (picture quality, super vivid mode, etc.....). There's nothing satisfying than using your phone at its full potential with your own custom. Spot the difference!!!!
1. Unlock bootloader
2. Flash boot.img (Patched to be compatible with the drmfix)
>>> fastboot flash boot boot.img
3. Flash recovery.img
>>> fastboot flash recovery recovery.img
4. Boot to recovery by holding vol - and power; then swipe to allow modification and Format data (mandatory)
5. Flash drmfix.zip
6. Flash Magisk 14.0
7. Boot to android, you're done!!!
Type *#*#7378423#*#* then >>Service info>>Configuration or >>Service tests>>Security to check if all your keys are active.
{
"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"
}
Download link:
# For boot.img here!!!
# For recovery.img here!!!
# For drmfix This does the trick

@pa7taloha Recovery Download link not working for me. Is normal TWRP also okay?
Edit: Nevermind, just saw its for F3311 not for F3111.

F3311? You mean Xperia XA or Xperia E5?

okhayko said:
F3311? You mean Xperia XA or Xperia E5?
Click to expand...
Click to collapse
I mean Xperia xa F3111. OP corrected, Thank you

Hi OP, still not working, all my is are "unknown"

okhayko said:
Hi OP, still not working, all my is are "unknown"
Click to expand...
Click to collapse
That's Strange, can you provide further info, like did you got any error when flashing the drmfix?

pa7taloha said:
That's Strange, can you provide further info, like did you got any error when flashing the drmfix?
Click to expand...
Click to collapse
Unfortunately, it's flashed well, no error.
Before i flash the drmfix, just 2 first lines are [Unknow Error] and the other lines are all [Active], Number or something like that
After i flash the drmfix, all of them are [Unknow Error]

okhayko said:
Unfortunately, it's flashed well, no error.
Before i flash the drmfix, just 2 first lines are [Unknow Error] and the other lines are all [Active], Number or something like that
After i flash the drmfix, all of them are [Unknow Error]
Click to expand...
Click to collapse
That means the drmfix you've flashed has deleted your credential which is located at /data/credmgr/ . For sure the linked drmfix here will not delete anything in your system.
Note: This drmfix will not be compatible with another boot.img different from the O.P. You have to do some mod in your boot.img to make this working. If you want to, let me know.

pa7taloha said:
That means the drmfix you've flashed has deleted your credential which is located at /data/credmgr/ . For sure the linked drmfix here will not delete anything in your system.
Note: This drmfix will not be compatible with another boot.img different from the O.P. You have to do some mod in your boot.img to make this working. If you want to, let me know.
Click to expand...
Click to collapse
Hi, can i ask a question?
My model is F3116, can i do step by step with this guide to make it work?
Sorry but i did not flash your boot.img file, i flashed boot.img file from the other thread, i though it the same. i will try your method but can you answer me that this will work with my model TY!

okhayko said:
Hi, can i ask a question?
My model is F3116, can i do step by step with this guide to make it work?
Sorry but i did not flash your boot.img file, i flashed boot.img file from the other thread, i though it the same. i will try your method but can you answer me that this will work with my model TY!
Click to expand...
Click to collapse
Post here your boot.img then, I will try to mod it. But make sure you still have your credmgr.db file which is located at /data/credmgr, this Fix won't work without it.

pa7taloha said:
Post here your boot.img then, I will try to mod it. But make sure you still have your credmgr.db file which is located at /data/credmgr, this Fix won't work without it.
Click to expand...
Click to collapse
Thanks buddy. Here is my boot.img that i was flash
boot.img file

For F3116 [33.3.A.1.97]
okhayko said:
Thanks buddy. Here is my boot.img that i was flash
boot.img file
Click to expand...
Click to collapse
Now
1. flash this bootF3116.img file, using the command "fastboot flash boot bootF3116.img" (without quotes)
2. Go to twrp recovery and "format data" (I suppose you already have flashed twrp)
3. Flash drmfix.zip
4. Flash Magisk if you need root.
5. Reboot
Download link
bootF3116.img
The compatible drmfix.zip
If you still have any problem let me know

Hi,
i had a F3112, is the DRM fix compatible ?
thanks

bobladure said:
Hi,
i had a F3112, is the DRM fix compatible ?
thanks
Click to expand...
Click to collapse
Hi, F3112 and F3116 has the same boot.img file so you can try to flash the boot.img, and drmfix.zip above your post and post your feedback here

Hi @pa7taloha,
Can you share your kernel drm fix changes (github or some other cloud server)? I'm trying to implement some custom changes in the kernel and I could add this as well. Thanks.

cojocar.andrei said:
Hi @pa7taloha,
Can you share your kernel drm fix changes (github or some other cloud server)? I'm trying to implement some custom changes in the kernel and I could add this as well. Thanks.
Click to expand...
Click to collapse
Sorry for late reply.
I will try to be clear as much as I can(bad english speaker).
We have tested this workaround to: xperia xa f3111(Mediatek, Nougat) and xperia x perfomance(qualcom, Nougat and 0reo) and it work fine in Nougat and Oreo too. I hope this will work too to the other xperia devices, so we can relate it.
I did not compile kernel from source, I have just extracted it with flashtool kernel.elf and unpacked/repacked it with AIK Linux/Carliv-image-kitchen. I am a Linux user.
For mediatek processor,
In the kernel, unpack it and edit.
1. disable dm-verity
2. edit init.rc
add this red line in on early-init, .
Code:
on early-init
[COLOR="Red"]restorecon /vendor/lib64/libdrmfix.so
restorecon /vendor/lib/libdrmfix.so[/COLOR]
# Set init and its forked children's oom_adj.
write /proc/1/oom_score_adj -1000
# Disable sysrq from keyboard
write /proc/sys/kernel/sysrq 0
3. edit init.aee.rc
add this red line in on init
Code:
on init
export LD_PRELOAD libdirect-coredump.so
write /proc/self/coredump_filter 39
setprop ro.aee.enperf off
[COLOR="Red"]export LD_PRELOAD libdrmfix.so[/COLOR]
4. edit default.prop
change the value of "ro.secure=0" to "ro.secure=1"
7. Open "fstab.mt6755" and copy in new text file the path to your system, it should be in the first line, we will use this later in the drmfix.zip
6. repack your kernel
II. We will do some mod to the drmfix.zip
open with the "open archive manager" the drmfix.zip and edit the updater-script in drmfix/META-INF/com/google/android/
This red line in the updater-script should be the same path to your system found in "fstab.mt6755" file in the boot.img (you've copied in step 5 in kernel)
Code:
ui_print(" ==================================");
mount("ext4", "EMMC", "[COLOR="red"]/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system[/COLOR]", "/system");
ui_print("updating..");
package_extract_dir("system", "/system");
unmount("/system");
ui_print("Done!!!");
save it and update the drmfix.zip
For Qualcom processor
In the kernel, unpack it and edit.
1. disable dm-verity
2. edit init.rc
add this red line in on early-init
Code:
on early-init
[COLOR="red"]restorecon /vendor/lib64/libdrmfix.so
restorecon /vendor/lib/libdrmfix.so[/COLOR]
# Set init and its forked children's oom_adj.
write /proc/1/oom_score_adj -1000
# Disable sysrq from keyboard
write /proc/sys/kernel/sysrq 0
3. edit init.environ.rc
add this red line to the last line.
Code:
export SYSTEMSERVERCLASSPATH /system/framework/services.jar:/system/framework/ethernet-service.jar:/system/framework/wifi-service.jar
[COLOR="red"]export LD_PRELOAD libdrmfix.so[/COLOR]
4. edit default.prop
change the value of "ro.secure=0" to "ro.secure=1"
5. Open "fstab.qcom" and copy in new text file the path to your system, we will use this later in the drmfix.zip
6. repack your kernel, flash it
II. We will do some mod to the drmfix.zip
open with the "open archive manager" the drmfix.zip and edit the updater-script in drmfix/META-INF/com/google/android/
This red line in the updater-script should be the same path to your system found in "fstab.qcom" file in the boot.img (you've copied in step 5 in kernel)
Code:
ui_print(" ==================================");
mount("ext4", "EMMC", "[COLOR="red"]/dev/block/bootdevice/by-name/system[/COLOR]", "/system");
ui_print("updating..");
package_extract_dir("system", "/system");
unmount("/system");
ui_print("Done!!!");
save it and update the drmfix.zip, and flash it.
Avalaible for clarification.

https://imgur.com/OHuNKyk
Guys I can't seem to get it to work, tried reflashing your boot.img and recovery.img, tried formatting data and factory reset after every flash and wipe cache/dalvik cache after drm.zip install, nothing seems to get rid of those "Unknown error", btw I'm using F3111 single SIM on 33.3.A.1.97.
Almost forgot, when i plug my phone in fastboot and flash the files i don't get that flash status on the phone itself, only on cmd screen that it's done.

matan290 said:
https://imgur.com/OHuNKyk
Guys I can't seem to get it to work, tried reflashing your boot.img and recovery.img, tried formatting data and factory reset after every flash and wipe cache/dalvik cache after drm.zip install, nothing seems to get rid of those "Unknown error", btw I'm using F3111 single SIM on 33.3.A.1.97.
Almost forgot, when i plug my phone in fastboot and flash the files i don't get that flash status on the phone itself, only on cmd screen that it's done.
Click to expand...
Click to collapse
Sorry to hear that, It is always recommended to do a full nandroid backup before flashing anything. To get rid of those Unknown error you have to reflash your firmware. What causes these error is that the drm.zip you've flashed has deleted the credmgr.db file in /data/credmgr/, this contains all your phone credential. May be you've flashed any drmfix(old drmfix in other thread) before flashing this, because this fix will not delete anything in your system. And no need to wipe cache/dalvik after flashing it.

Yeah that's the problem,cause i flashed the other DRM fix few weeks ago. Can you please post a link or something for a firmware I can flash or should I try the PC Companion.

matan290 said:
Yeah that's the problem,cause i flashed the other DRM fix few weeks ago. Can you please post a link or something for a firmware I can flash or should I try the PC Companion.
Click to expand...
Click to collapse
You can use flashtool and download a frimware the latest version by xperifirm which is integrated in the flashtool. Or if you want to use Pc Companion you have to relock your bootloader and unlock after it's done.