Hello, im about to get this thing tomorrow and just wanted to know the best way to root it and all that. (Used to Samsung Galaxy S3 and Note 3 to root via Odin.)
So first of all i am going to tell you abit of what i'm getting here, it's the Xperia Z2 tablet with LTE/4G Android 4.4.2 pre-installed (i guess it's the international device if there is one) and what i can understand of what the model it's going to be "Castor" right?
So my question now is, what tools do i need to root it and install the recovery? and what recovery do you recommend? is it a damn hassle?
and what specific roms will actually work for this device? im looking for a CM based rom such as AOSP/AOSPA or as close to vanilla 4.4.x
Im also having some questions about the build.prop and DPI
Whats stock DPI?
What's the lowest DPI possible to use (still readable)
What DPI are you using/recommending?
Thanks in advance.
Great regards mattish.91
mattish.91 said:
what tools do i need to root?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2784900
mattish.91 said:
Im also having some questions about the build.prop and DPI
Whats stock DPI?
What's the lowest DPI possible to use (still readable)
What DPI are you using/recommending?
Click to expand...
Click to collapse
Stock DPI is 240, and I have actually not changed it so I can't give any advice on that.
Sent from my Xperia Z2 Tablet using Tapatalk
UgloBuglo said:
http://forum.xda-developers.com/showthread.php?t=2784900
Stock DPI is 240, and I have actually not changed it so I can't give any advice on that.
Sent from my Xperia Z2 Tablet using Tapatalk
Click to expand...
Click to collapse
I would be careful which version of the tablet you have. Despite claims to the contrary, it does NOT work with the latest firmware and model information. I highly suggest checking the model numbers of people who got it to work and avoiding model numbers that don't yet work if you need it rooted right now.
EDIT: Actually, maybe it does work on all models. I have SGP561 with Firmware 17.1.D.0.417 and after running it the errors made it look like it failed, but after a reboot and waiting a little while I was able to edit files in Root Explorer (although some editors couldn't edit the files, which was weird) and of course I can't edit bootanimation.zip, but it's mostly rooted by the looks of things.
Elliander said:
I can't edit bootanimation.zip, but it's mostly rooted by the looks of things.
Click to expand...
Click to collapse
I just wanted to let you know that 4.4.x you cant change anything with the bootanimation.zip i have tried on multiple devices and found out that you actually cant unless you use a rom with cm11s features. Im able to change the boot animation trough settings on my note 3 which got some features from cm11s. I would love to see a rom for xperia tablet z2 that is based on temasek71's source. [email protected] @xda and temasek.hopto.org for devices and such. The best rom i have ever used in my life, it's unofficial cm11 and is 90% Of the time stable and fully working.
Thanks for the heads up
mattish.91 said:
I just wanted to let you know that 4.4.x you cant change anything with the bootanimation.zip i have tried on multiple devices and found out that you actually cant unless you use a rom with cm11s features. Im able to change the boot animation trough settings on my note 3 which got some features from cm11s. I would love to see a rom for xperia tablet z2 that is based on temasek71's source. [email protected] @xda and temasek.hopto.org for devices and such. The best rom i have ever used in my life, it's unofficial cm11 and is 90% Of the time stable and fully working.
Thanks for the heads up
Click to expand...
Click to collapse
If I backup the DRM keys, change to a custom ROM, change the boot loader, then restore to an official ROM with DRM keys restored, would the boot loader remain changed?
Is there a simple way to convert a video file to a boot loader?
EDIT: it also appears that I can't copy any files to the root folder. I want to install Ubuntu as a workaround to the fact that flash doesn't work anymore, even the modified version. I was thinking I could install Ubuntu and then install flash on that and get all my flash programs to work again, but for some strange reason I can't mount as read write anything in the root directory even though I can edit files in system. I'm not sure if I could call it being rooted if I don't have access to the root folder.
Elliander said:
If I backup the DRM keys, change to a custom ROM, change the boot loader, then restore to an official ROM with DRM keys restored, would the boot loader remain changed?
Is there a simple way to convert a video file to a boot loader?
EDIT: it also appears that I can't copy any files to the root folder. I want to install Ubuntu as a workaround to the fact that flash doesn't work anymore, even the modified version. I was thinking I could install Ubuntu and then install flash on that and get all my flash programs to work again, but for some strange reason I can't mount as read write anything in the root directory even though I can edit files in system. I'm not sure if I could call it being rooted if I don't have access to the root folder.
Click to expand...
Click to collapse
I guess what you'r trying to say is that you have a video that you want to use as boot animation? There is multiple tools to create pictures from a video and compile the pictures to a bootanimation.zip, even IF you got a boot animation zip, you wouldn't be able to replace the original zip if you are running android 4.4.x i don't know why but you can't. I can't really say why you only can edit some files are u Sure you have su binaries updated? If you wan't to change the bootanimation, i would recommend you to find a rom based on cyanogenmod 11s (the oneplus one version of cm) as far as i know there is none for xperia z2 yet, but when i come to the level of developing for android i will definitly try to compile one ^^. Yesterday i wrote to temasek71 and asked if he were intrested in developing for tablet, but i havn't got an answere yet, it's his birthday today ^^
mattish.91 said:
I guess what you'r trying to say is that you have a video that you want to use as boot animation? There is multiple tools to create pictures from a video and compile the pictures to a bootanimation.zip, even IF you got a boot animation zip, you wouldn't be able to replace the original zip if you are running android 4.4.x i don't know why but you can't. I can't really say why you only can edit some files are u Sure you have su binaries updated? If you wan't to change the bootanimation, i would recommend you to find a rom based on cyanogenmod 11s (the oneplus one version of cm) as far as i know there is none for xperia z2 yet, but when i come to the level of developing for android i will definitly try to compile one ^^. Yesterday i wrote to temasek71 and asked if he were intrested in developing for tablet, but i havn't got an answere yet, it's his birthday today ^^
Click to expand...
Click to collapse
So even an unlocked boot loader can't edit bootanimation.zip ?
Ya, I'm pretty sure it's rooted with su binaries. I was able to edit files in system anyway. It's just that I have no access to the root folder and a few other places. Also, as I posted elsewhere, shortly after getting it rooted a new problem developed where random apps on the Play Store would not allow me to install them because it says there is insufficient storage available, even though I have more than 20 gigabytes free space internal and more than 100 gigabytes free space external. Sideloading those apps don't help, but other apps install without a problem. None of the normal solutions work, and there are no traces of the files I can't install that I can find anyway. It seems as though I triggered some kind of security program at Verizon put on the device when I rooted it. It's so bad I am considering either a factory reset or flashing an updated official ROM without the branding, but I don't know if a factory reset would also wipe the carrier unlock ( from what I read it might or might not) and the only images I can find are for a different model number and I don't know if they work and I also don't know if the DRM keys will remain intact. Its so bad that I would advise anyone with a verizon branded z2 who wants to keep stock firmware to avoid rooting at all. I should have just bought an international version instead.
A custom ROM would be great, but aren't there specific apps that you can only install if you have the DRM keys working? I mean, if I could independently buy them I would probably not miss the DRM keys, but aren't these important features like infrared and video quality?
Correction! It all works!
EDIT: I backed up everything with Titanium Backup (and moved the backup to SD and removed the SD to be safe) and then performed a factory reset. (The APN settings will be wiped, so to anyone reading this: Don't freak out if your mobile data plan doesn't seem to work.) and then performed an Easy Root and this one is looking MUCH cleaner:
Code:
==============================================
= =
= Easy Root Tool v11 =
= Supports various Xperia devices =
= created by zxz0O0 =
= =
= http://forum.xda-developers.com/ =
= showthread.php?p=53448680 =
= =
= Many thanks to: =
= - [NUT] =
= - geohot =
= - MohammadAG =
= - cubeundcube =
= - nhnt11 =
= - xsacha =
= =
==============================================
=============================================
Waiting for Device, connect USB cable now...
Make sure you have only one Android device connected
BlueStacks emulator can also cause problems
=============================================
Device found
=============================================
Getting device variables
=============================================
Device model is SGP561
Firmware is 17.1.D.0.417
=============================================
Sending files
=============================================
35 KB/s (1585 bytes in 0.044s)
3608 KB/s (657704 bytes in 0.178s)
158 KB/s (1133 bytes in 0.007s)
99 KB/s (9496 bytes in 0.093s)
580 KB/s (13672 bytes in 0.023s)
Copying kernel module...
647 KB/s (34473 bytes in 0.052s)
46 KB/s (767 bytes in 0.016s)
948 KB/s (13592 bytes in 0.014s)
Kernel version is 3.4.0-perf-g31245c3
Version does not match 3.4.0-perf-ge4322cd, needs patching...
1+0 records in
0+1 records out
19 bytes transferred in 0.001 secs (19000 bytes/sec)
Kernel module patched.
modulecrcpatch (by zxz0O0)
module_layout: patched to 0xCFADE050
__aeabi_unwind_cpp_pr1: match
kallsyms_lookup_name: not found
printk: not found
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: match
successfully patched
=============================================
Loading towelzxperia
=============================================
698 KB/s (13592 bytes in 0.019s)
2639 KB/s (197320 bytes in 0.073s)
=============================================
Waiting for towelzxperia to exploit...
towelzxperia by zxz0O0 (EasyRootTool Version)
libexploit by geohot
libzxploit.so created
doing the magic
creating vm (loljavasucks)
mount: Operation not permitted
cleaning up
done
Checking if device is rooted...
Device rooted.
=============================================
Checking for Sony RIC
=============================================
Sony RIC Service found.
Installing RIC kill script installmount.sh...
Stock mount does not exist. Creating dir and link
Installing of mount.sh finished
Done. You can now unplug your device.
Enjoy root
=============================================
What to do next?
- Donate to the people involved
- Install SuperSU by Chainfire
- Install dualrecovery by [NUT]
- Backup TA partition
Press any key to continue . . .
I then had absolutely NO problems with TA-backup and was able to run adbd-insecure (which I couldn't before) and was able to successfully create the TA.img file for my DRM keys (which I also couldn't before).
I then had no problems editing Platform.XML to restore SD card access, and I have no problems creating folders in the root and moving files into it (although moving very large files to a folder in the root seems to cause the tablet to freeze up and reboot a few minutes later, which bites because I am trying to get Ubuntu. I'm going to have to go with a smaller image.)
Finally, I was able to restore all of my settings and app data without difficulty with Titanium Backup *AND* I was able to freeze or delete the system apps I so hated! (Unfortunately, even after enabling SD write access, Titanium Backup is oddly unable to write to SD. I had to manually copy the backup folder from SD back to internal and then reboot before I could even restore the backups as well. I thought that was very strange. Especially since I have a Pro version.)
Conclusion: The problems I went through were largely related to all of the failed rooting attempts. Don't try anything EXCEPT "Easy Root". It's all you need, and if you start with it you shouldn't have any problems. If you have the problems I had, you will have to do a factory reset before you can fully root the device.
As a side note, it needs to be mentioned that the Xperia Z2 tablet has a "Rooting Status" flag which is a permanent trigger. Even after a factory reset without root the flag remains triggered. If you are concerned about warranty you should be aware of it. Also, after I performed the factory reset I was unable to get rid of the Verizon "Tablet Activation" message permanently. I didn't have it before, but now I have it.
A Rooting Status Flag??
First time I hear about this with Z2. One of the reasons I've chosen this device and not the Galaxy Tab S.
Could you give more information or a link about this?
Vaetheran2107 said:
A Rooting Status Flag??
First time I hear about this with Z2. One of the reasons I've chosen this device and not the Galaxy Tab S.
Could you give more information or a link about this?
Click to expand...
Click to collapse
Well, mine is a Verizon branded factory unlocked SGP561. In:
System > About Tablet >
There is a setting on the bottom that says "Rooting Status" and beneath that, even before I managed to fully unroot it, the status said "Rooted". If you need it I can send a screenshot of the actual status.
After a factory reset it still said it and I assumed the root would have been lost after that (especially since I used the unroot option in SuperSU after), but a few of my bugs related to the bad rooting attempt resurfaced (not as bad though, and it goes away after a reset and restore of data) and after a subsequent factory reset I noticed I still had root access even without using easy root again. I also found that I could not find a way to unroot. I tried Universal Unroot today and it asked for super user privileges, granted it, and restarted itself, but even it couldn't unroot the device. So at this point I don't know if that flag would go away if the device is unrooted because I don't really know how to unroot at this point.
The important thing is that I was able to backup the DRM keys though, so now I have the option of trying other firmwares and later going back to what I had. My next step is going to be flashing an unbranded firmware over the branded firmware and see how that works for me.
well xD
I got my device today and also had some troubles rooting, adb and fastboot but once I got the thing of it, it was pretty easy, I got some good and some bad answers to my questions but now its all good xD running the latest carbon ROM as I type and it works just great, there is no wayim going back to sonys stock pre installed crap xD, just wanted to let you know that I did a backup but not the img file and hopefully won't need it anytime soon xD. Next step is backup and DPI change in my build.prop file to get everything just a bit smaller than it is right now.
Good luck rooting your devices and remember ALWAYS make an backup of your current system, including if you'd just doing an update. :victory:
mattish.91 said:
I got my device today and also had some troubles rooting, adb and fastboot but once I got the thing of it, it was pretty easy, I got some good and some bad answers to my questions but now its all good xD running the latest carbon ROM as I type and it works just great, there is no wayim going back to sonys stock pre installed crap xD, just wanted to let you know that I did a backup but not the img file and hopefully won't need it anytime soon xD. Next step is backup and DPI change in my build.prop file to get everything just a bit smaller than it is right now.
Good luck rooting your devices and remember ALWAYS make an backup of your current system, including if you'd just doing an update. :victory:
Click to expand...
Click to collapse
When you say backup, do you mean anything more than the user + system apps that Titanium backup makes?
Elliander said:
When you say backup, do you mean anything more than the user + system apps that Titanium backup makes?
Click to expand...
Click to collapse
Yes, like a recovery backup. IF you fu** anything up you can always restore that backup from recovery
wow!
I just changed to 180 dpi instead of 240 and it looks awesome so far all apps tested is working flawlessly, defenitly to recommend definitly looks like a tablet now
Look at it here: https://plus.google.com/+MattiasMagnusson
Related
I was excited about the rollout of Android 2.1 on X10 last November (it finally arrived...), then I was able to install more apps and experience more fun with upgraded os. However, here also comes the problem, I only had 40MB left in my internal memory, and App2sd can only be done with millions of steps...
So I was thinking.. if I have to put in so much effort just to get App2sd working, why not just spend the effort to install a custom ROM with Android 2.2 (where App2sd becomes a build-in capability, and I will be able to do voice actions too!)
Honestly, it was easier than I thought, but there are some details you probably want to pay attention to in the process, so I am writing this comprehensive guide here that can be easily followed (even for newbies!).
[All credits go to the CyanogenMod dev team for the custom ROM, zdzihu for xRecovery, Androxyde and Bin4ry for FlashTool, ShortFuse for SuperOneClick, Froshed Blue for themes.
Thank you all for the incredible work to make this possible! And sorry if I missed anyone...
NOTE: I WILL NOT BE RESPONSIBLE IF ANYTHING GOES WRONG.
1. Back up all your data.
- Use apps in the market such as MyBackupPro to back up all contacts, sms, call log etc. If your phone is rooted, you can also back up app+data with it (so you won't lose your progress on games or apps).
- OR you can sync your contacts etc via your Google account, and back up all apps with Astro.
- DO NOT use the backup & restore app with the stock 2.1, after you flash to 2.2, this app won't be available anymore, and there is no way you could retrive the data from the .sbf file generated by it!
UPDATE: SE Backup & Restore is now available here in the Extras section. I haven't tested it yet but if you want you can give it a try.
2. If you have already updated your phone to baseband 2.1.54 or 2.1.55, skip this step.
- Otherwise, go to here to find and download the most updated firmware (I used X10a _2_1_A_0_435 with DualTouch).
- Download FlashTool v0.29, copy the firmware you downloaded earlier to the firmware folder in FlashTool.
- Now flash your phone with this firmware, follow the instructions on the screen.
3. Root your phone.
- Download SuperOneClick v1.7 from shortfuse.org.
- Root with one simple click.
4. Install Busybox and xRecovery.
- Get Busybox from the market, once it's opened, it will tell you that your phone is rooted, install the newest version into /bin.
- Download xRecovery, rename the apk file to xRecovery.Zip.
- Unpack the file, find ./res/raw folder with 3 files - chargemon, busybox, xrecovery.tar).
- Copy these 3 files into /system/bin using app Root Explorer. (Note: this is the manual installation method, which I found more stable, or you can just use automatic install with the xRecovery.apk downloaded earlier.)
5. Copy the files for ROM installation (CM 6.1.3 V4, Google Apps Pack, and new Android market) onto your SD card.
UPDATE: CM 6.1.3 V4.5.7 is out with Camcorder working, in this step, you will copy CM 6.1.3 V4.5, CM 6.1.3 V4.5.7 instead of V4.
6. Install custom ROM.
- Reboot your phone.
- Right after the SE white text appears, press the back button a few times until xRecovery comes on (if it doesn't work, try one more time or reinstall xRecovery using the manual method if you didn't.)
- In xRecovery, use volume button to move up and down, home to enter.
- Do a Factory Reset, Wipe Cache Partition, Advance Options> Wipe Dalvik Cache, Wipe Battery Stats.
- Then install Custom Zip and choose CM6.1.3-V4.zip (or V4.5) for your SD card for the ROM. (If you are installing V4.5, install Custom Zip - V4.5.7 after this step.)
- Install Custom Zip and choose CM-V4Gapps.zip (or V4.5.7) for Google Apps.
- Reboot your phone, go to programs>sysctl, set the parameters to the following:
vm.min_free_kbytes = 16284
vm.dirty_ratio = 90
vm.dirty_background_ratio = 55
vm.vfs_cache_pressure = 20
oom kill checked- Login to market once, reboot your phone to xRecovery again, install Custom Zip and choose NewMarket.zip.
If you want more selections of theme, check out this thread.
Post Actions
- Restore all your information and apps.
- Get App2SD from market to easily move apps to SD or internal memory, or you can do it manually in settings>application settings>manage application. (Note: if you want to display a widget of an app, keep the app on the phone, DO NOT move it to SD as widget will not be available for apps moved to the SD.)
- MIUI Camera is included with the ROM, or you can use Camera360 (tested working). If you want camera flashlight, use Vigenette.
UPDATE: MIUI Camcorder is working on v4.5.
- Go to settings>cyanogenmod settings and settings>ADWLauncher for more tweaks.
UPDATE: ADWLauncher is been replaced by another launcher (I forgot the name) in V4.4+
_______________________________________________________________________
Read my blog for more reviews and guides of Android - http://baimandy.wordpress.com
Follow me on Twitter: MandyBai
Thanks! This kind of combined all the guide together makes it so much clearer~
Thanks man, that's the guide I was looking for.
One small question, please. If after that i decide (for any reason) to go back to SE android 2.1, is it possible? Using factory reset and plug to PC Companion?
Thank you again
Sent from my X10i using XDA App
mjrabhi said:
Thanks man, that's the guide I was looking for.
One small question, please. If after that i decide (for any reason) to go back to SE android 2.1, is it possible? Using factory reset and plug to PC Companion?
Thank you again
Sent from my X10i using XDA App
Click to expand...
Click to collapse
You can find the stock firmware in the forum and use FlashTool to flash back to android 2.1 (just like step 2 here).
4androidonly said:
You can find the stock firmware in the forum and use FlashTool to flash back to android 2.1 (just like step 2 here).
Click to expand...
Click to collapse
Thank you much much
This ROM is really great, thanks for all the devs, been using this for more than a week now. My only concern is the color of the LED while charging, seems like its over burning or something is there a way to change LED charging color? been searching a lot but in vain.
thanx ... good guide
I was forever feeling hesitant to install custom roms and stuff but after reading your guide I decided to go ahead with it and as u said it was much easier than I thought..
But i prefer Freex10 to CM 6.1.3 , I really dont like CM 6.1.3 interface it does not look good
Thanks a lot mate
gil2004xp said:
This ROM is really great, thanks for all the devs, been using this for more than a week now. My only concern is the color of the LED while charging, seems like its over burning or something is there a way to change LED charging color? been searching a lot but in vain.
Click to expand...
Click to collapse
Hmmm ... never thought of that since it doesn't concern me but if you want to change LED notification color for different apps, you can do it at CMsettings-user interface.
wasiimabbas said:
I was forever feeling hesitant to install custom roms and stuff but after reading your guide I decided to go ahead with it and as u said it was much easier than I thought..
But i prefer Freex10 to CM 6.1.3 , I really dont like CM 6.1.3 interface it does not look good
Thanks a lot mate
Click to expand...
Click to collapse
the rom is just personal preferences~ i am glad the guide helped~
i've done all the said guides and installed 2.2 with cam fix.
but have one problem again, my phone and my computer cant read my sdcard..
how to fix this one? is this really the problem on installing this 2.2 rom?
xriel said:
i've done all the said guides and installed 2.2 with cam fix.
but have one problem again, my phone and my computer cant read my sdcard..
how to fix this one? is this really the problem on installing this 2.2 rom?
Click to expand...
Click to collapse
really? I am not sure how to fix it since I never experienced this. But I do notice with the new 2.2 rom, it takes some time to recognize all the data on SD card at the initial start (both on the phone and on the computer).
The first time I connect to computer (USB storage mode) it took 5 mins for the computer to recognized it, and the phone was kind of froze for a while, but after that it's all fine.. maybe just try to wait a bit?
Mehn thanks for this. Soooooo easy.
becknise said:
Mehn thanks for this. Soooooo easy.
Click to expand...
Click to collapse
you're welcome
I'm just in the process of running through the guide now. Can't wait!!!
I have got a problem with completing Step 4. I have downloaded and install BusyBox from the MarketPlace but when I open it up all I get is a blank OK message and the Status: Looking for BusyBox...
Any ideas??
Also I can open xRecovery but if I click on the "Install xRecovery" button I get the little magnify glass change to a red stop circle.
Any ideas??
This is also I post of the Root Log
SuperOneClick v1.7.0.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
1466 KB/s (585731 bytes in 0.390s)
OK
chmod psneuter...
OK
Running psneuter...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running psneuter...
ROOTED
Pushing busybox...
1614 KB/s (1062992 bytes in 0.643s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/mtdblock2
OK
Reading OS Version properties...
Version: 2.0
OK
Remounting system with read-write access...
OK
Pushing su-v2...
1282 KB/s (26264 bytes in 0.020s)
OK
chmod su...
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Copying busybox (/system/xbin/)...
OK
chmod busybox (/system/xbin/)...
OK
Installing busybox (/system/xbin/)...
OK
Pushing Superuser.apk...
1760 KB/s (196521 bytes in 0.109s)
OK
Remounting system with read-only access...
OK
Running a SU test...
Success!
Thanks
Thank you!!! Your guide was very helpful to me! Sorry for my bad English
Please ignore my last post as I have now figured out what I was doing wrong. I didn't know there was two different BusyBox downloads.
Anyway, I now have it installed, however I cannot figure out where to set the following parms.
If you could point me in the right direction it would be much appericated.
Thanks again
Thanks for this. Quick question, it may seem dumb but what do you mean when you say to :
"Reboot your phone, go to programs>sysctl, set the parameters to the following:
vm.min_free_kbytes = 16284
vm.dirty_ratio = 90
vm.dirty_background_ratio = 55
vm.vfs_cache_pressure = 20
oom kill checked"
Where in the menu do I find "programs" exactly?
NM... I didnt realize Sysctl was an App from the market. When I first completed it, I didnt have service so I couldnt use the Market. Flashed again and it works.
Thanks!
Testsubjec said:
Please ignore my last post as I have now figured out what I was doing wrong. I didn't know there was two different BusyBox downloads.
Anyway, I now have it installed, however I cannot figure out where to set the following parms.
If you could point me in the right direction it would be much appericated.
Thanks again
Click to expand...
Click to collapse
Are you referring to the parms for sysctl? if you go to the list of all applications, there is a pre-installed app called sysctl config (it's like a penguin icon), then you will be able to set the parameters there. hopefully this answers your question!
Hello everyone, i recently purchased one of these from newegg at a reasonable price, but I can't seem to find rom's for them anywhere. Does anyone have any ideas on where to look, i've been hunting on google for hours. It's currently running 4.2.2
Kernel 3.0.36+
Firmware: CT9706_RK610
Im not sure what else to do. I would hate to have to stick with stock considering it's a little laggy with the junk that they piled onto it. Not to mention i know it has the chinese OS installed on it. Luckily i WAS able to root it, and even get cwm installed on it, but i have no rom to flash to it as of yet. Any help is appreciated, thanks!
Soft Bricked Taipad 10s
I have this tablet, and was able to root it, and all was fine until I realized that it was not utilizing the Nandflash. The internal storage was full, and the Nand was empty (ish). SO i decided (as a newb) to pull the boot.img, edit the init.rk3066.rc and attempt to re-route the emulated storage to /mnt/sdcard. Recreated the new_boot.img, and pushed it and cat to mtdblock2 as i got it..(correct base address) - and reboot takes it to recovery. over and over.
I am looking for a rom that will work, from what i find CWR and CWM are a no go due to stopped development, but im still searching. There must be a similar tablet somewhere.
Oh and b4 the softbrick i used to get adb shell cmd line "[email protected] #" or something like that - now i only get "#" - so i could not cat the original boot.img - yay fail.
Adulator12 said:
I have this tablet, and was able to root it, and all was fine until I realized that it was not utilizing the Nandflash. The internal storage was full, and the Nand was empty (ish). SO i decided (as a newb) to pull the boot.img, edit the init.rk3066.rc and attempt to re-route the emulated storage to /mnt/sdcard. Recreated the new_boot.img, and pushed it and cat to mtdblock2 as i got it..(correct base address) - and reboot takes it to recovery. over and over.
I am looking for a rom that will work, from what i find CWR and CWM are a no go due to stopped development, but im still searching. There must be a similar tablet somewhere.
Oh and b4 the softbrick i used to get adb shell cmd line "[email protected] #" or something like that - now i only get "#" - so i could not cat the original boot.img - yay fail.
Click to expand...
Click to collapse
hi... i have a taipd 9x- but i had a mistake.. and i dont have rom files and im stuck!!.. my android os does not work.. and i need the files to make it work the touch and wi fi hardware..can you help me how to do or find that rom file?
MAXIMAURO said:
hi... i have a taipd 9x- but i had a mistake.. and i dont have rom files and im stuck!!.. my android os does not work.. and i need the files to make it work the touch and wi fi hardware..can you help me how to do or find that rom file?
Click to expand...
Click to collapse
Do either of you still have the original firmware for the Taipad 9X? I've essentially bricked mine by loading an incompatible firmware and would love to get back to the original.
I'd be willing to pay a small fee to get it.
Please excuse asking questions as a first post, but I'm at the stage where I'm stumped and a search isn't helping.
Mlais MX28 fresh from MM pre-rooted. Managed to get the ROM backed up and CWM installed with Rua1's excellent MTK Droid Root & Tools. However, removing the Chinese useless (for me - no offence intended) apks proved not to be happening from the one-click button in that excellent piece of software. No bother, thought I, I'll just use adb and remove the relevant apks manually from /system/app. Famous last words.
Here's where things get really odd. I can mount root fine using the usual procedure but mount -o rw,remount /[email protected] /system works once and once only. Even stranger is that the first time gets you a rw mounted filesystem for about 10 seconds, at which point it gets remounted ro and no amount of faff will get it back to rw without a full power off and restart. All it does is spits out
Code:
mount: Read-only file system
Any ideas, please? I suspect there's some write protection going on but I haven't the first idea where to look.
Edit: Having done a little more searching on this issue, it seems there's a few Acers with the same behaviour, caused by a compiled-in kernel option. Looks like it may well be "wait for a custom ROM" is the answer. Not sure if rolling our own is possible unless anyone knows where to get the Mediatek sources for this device from?
Anyway, :good: to all those who have viewed my question. It's appreciated.
Edit 2: There's an S4UI ROM on needrom<dot>com that is rumoured to have solved this issue. Note that if you have installed CWM using the "magic" MTK Droid Root & Tools method, chances are you can't mount /system rw using ADB in CWM either - I suspect they share the same kernel. I haven't tried the S4UI ROM myself as the recovery needed to install it seems to be in Chinese. Possible solution for anyone with a grasp of that language and script but that someone isn't me
[Q] Mlais MX28 Recovery in Chinese Any help with translation
Hello, bud Any help yet also gut stuck in this.
I'm afraid not at the moment. The S4UI ROM on needrom does indeed enable /system rw but the WiFi and Bluetooth will not activate. Replacing mtk_stp_wmt.ko in /system/lib/modules/ with the version from the stock ROM that should fix this issue, doesn't fix this issue. It's a shame as the S4UI ROM is rather pleasant to use and if I could get that fully operational I expect I would be quite happy with this device. Oddly, the stock ROM came back with a different MAC for the WiFi. As I restored from a backup created with MTKDR&T, this is a little perplexing.
I'll update if I find any more clues.
{Possible solution/nasty hack]
Here's a way to get full /system access on the stock ROM. It requires
Clockwork Mod recovery
ADB
Courage
Install/create Clockwork Mod with MTKDR&T. Now boot into recovery by holding Vol+ and power until the boot selection screen appears and then select recovery with Vol+ and press Vol- to accept.
Do not mount /system in CWM.
On your ADB equipped computer, start
Code:
adb shell
Now issue the following at the root shell prompt:
Code:
tune2fs -e continue /dev/block/mmcblk0p5
Reboot the system and enjoy the power of full root.
This may well be a nasty hack. I was convinced the issue was a protected kernel module but it seems the ext4fs image of the system block is corrupt in some way and the default error action is to mount -o ro. We're disabling that default action and letting the mount remain unchanged.
As always with these things, proceed at your own risk. If you break it, you have the privilege of keeping both bits.
Good way around mate, but risky as no CWM yet installed, seem's the mobile gut some bug problem, should expect an official update rom soon enough, Root method you used for this? i intend flashing Clockwork Mod can seem to understand fully as i'm new to android development and customizing, again problem with battery do you get a full day (few moment on screen) light usage? Feel its no actual 25000mah on board.
codedmax said:
Good way around mate, but risky as no CWM yet installed, seem's the mobile gut some bug problem, should expect an official update rom soon enough, Root method you used for this? i intend flashing Clockwork Mod can seem to understand fully as i'm new to android development and customizing, again problem with battery do you get a full day (few moment on screen) light usage? Feel its no actual 25000mah on board.
Click to expand...
Click to collapse
It appears there's an fsck implementation in the shell of CWM as well.
Code:
e2fsck -pfv /dev/block/mmcblk0p5
That should fix most of the errors in the filesystem.
The device came with su and SuperSU installed but it was fairly useless without /system access.
CWM can be easily installed using MTK Droid Root & Tools to extract the boot image, auto-patch, build CWM and install the lot. It really is a slick piece of software.
As for the battery, an even bigger issue is the supplied charger which is puny. Of course, looking at the battery and then looking at a proper, honest-to-goodness 2.2Ah Panasonic 18650 cylindrical cell you have to wonder if 2.5Ah isn't awfully optimistic.
Chron0s said:
It appears there's an fsck implementation in the shell of CWM as well.
Code:
e2fsck -pfv /dev/block/mmcblk0p5
That should fix most of the errors in the filesystem.
The device came with su and SuperSU installed but it was fairly useless without /system access.
CWM can be easily installed using MTK Droid Root & Tools to extract the boot image, auto-patch, build CWM and install the lot. It really is a slick piece of software.
As for the battery, an even bigger issue is the supplied charger which is puny. Of course, looking at the battery and then looking at a proper, honest-to-goodness 2.2Ah Panasonic 18650 cylindrical cell you have to wonder if 2.5Ah isn't awfully optimistic.
Click to expand...
Click to collapse
Very Well concerned,
once again good job, but how do i go about implementing this,
would you be kind enough to put in some more details on the file system code and CWM flashing with MTK Droid root & Tool did you manage to get a translation on the chinese langauage recovery problem,
(a tutorial is just fine) Thanks alot bud.
Okay, give me a little time to set it all up for screenshots as I don't generally use Windows unless I have to. It's all fairly straightforward. The CWM installation is four clicks and some waiting and repairing the /system block is a couple of commands.
Oscarblue48 has a tutorial on installing CWM on Mediatek devices here or here if your MX28 isn't rooted which is the procedure I followed. Then it's just a case of booting into CWM, connecting your device to USB and using adb's shell to fsck the filesystem on that block.
really nice, okay as you say,
i would look forward to it (some screen shots aid), in the main time with full study & concentration on the CWM tutorial you gave, quite interesting if you ask me.
#back to studying, looking forward to a bug free final optimization of the Mlais MX28 as its a great buy for such a price.
codedmax said:
really nice, okay as you say,
i would look forward to it (some screen shots aid), in the main time with full study & concentration on the CWM tutorial you gave, quite interesting if you ask me.
#back to studying, looking forward to a bug free final optimization of the Mlais MX28 as its a great buy for such a price.
Click to expand...
Click to collapse
Sorry for the delay, I ran into a few issues and had to work out what was going on. Basically the e2fsck in CWM cannot write back to the block device so is useless. I extracted the system.ext4.img, added it as a file backed memory disk on my main computer and ran an e2fsck from there, which found and fixed the errors in the FS image. Writing that back after changing a few MD5sums in the file MTKDR&T creates allowed me to flash it back.
However it makes absolutely no difference to the mount behaviour. It still drops back to ro without the tune2fs -e continue set so that is, barring someone else coming up with a more elegant fix, the workaround. In a nutshell, follow the guide for either root or CWM recovery installation that others have posted linked above (no point wasting board space on repetition) and then simply follow my instructions for setting the error behaviour on the mmcblk0p5 slice and you should be good to go.
It's still an awful hack IMHO but, since there's nothing else so far that works, it's the uncomplicated way to get full root. Most of us will install CWM anyway, so it's no big chore just to boot into recovery and type one command "tune2fs -e continue /dev/block/mmcblk0p5" at the ADB shell.
Chron0s said:
Sorry for the delay, I ran into a few issues and had to work out what was going on. Basically the e2fsck in CWM cannot write back to the block device so is useless. I extracted the system.ext4.img, added it as a file backed memory disk on my main computer and ran an e2fsck from there, which found and fixed the errors in the FS image. Writing that back after changing a few MD5sums in the file MTKDR&T creates allowed me to flash it back.
However it makes absolutely no difference to the mount behaviour. It still drops back to ro without the tune2fs -e continue set so that is, barring someone else coming up with a more elegant fix, the workaround. In a nutshell, follow the guide for either root or CWM recovery installation that others have posted linked above (no point wasting board space on repetition) and then simply follow my instructions for setting the error behaviour on the mmcblk0p5 slice and you should be good to go.
It's still an awful hack IMHO but, since there's nothing else so far that works, it's the uncomplicated way to get full root. Most of us will install CWM anyway, so it's no big chore just to boot into recovery and type one command "tune2fs -e continue /dev/block/mmcblk0p5" at the ADB shell.
Click to expand...
Click to collapse
Greetings bud, gut CWM installed, all thanks to you (indeed greatful), have you been lucky with any custom rom as of now that works efficently on your device?
I seem to find a few bug here and there on the manufacturer stock, puny wifi & gps lock in, slight screen maulfuctions a little times.
As with most mtk gps can not finding a lock in hows it with your device.
codedmax said:
Greetings bud, gut CWM installed, all thanks to you (indeed greatful), have you been lucky with any custom rom as of now that works efficently on your device?
Click to expand...
Click to collapse
None of the custom ROMs on needrom work correctly which is a shame. The stock ROM's UI is awful.
codedmax said:
I seem to find a few bug here and there on the manufacturer stock, puny wifi & gps lock in, slight screen maulfuctions a little times. As with most mtk gps can not finding a lock in hows it with your device.
Click to expand...
Click to collapse
Now you have root you can use FasterGPS from FDroid to intialise the gps.conf file with appropriate settings for your location. My GPS is rock solid now, even in a moving vehicle. Not had any screen malfunctions. What version is your stock ROM? Mine's the 20140221 update.
Chron0s said:
None of the custom ROMs on needrom work correctly which is a shame. The stock ROM's UI is awful.
Now you have root you can use FasterGPS from FDroid to intialise the gps.conf file with appropriate settings for your location. My GPS is rock solid now, even in a moving vehicle. Not had any screen malfunctions. What version is your stock ROM? Mine's the 20140221 update.
Click to expand...
Click to collapse
Hello great bud,
Sorry for late reply, been up with alot on my plate from work lately, gps has been improved upon using that wonderful app "FasterGPS" now able lock in under a split couple of min not as before were it take like forever *Nice*
gut the same stock version "20140221" gusse its down to my own unit with the screen ish
Did a little searching around found a recent update from a online retailer outlet via their forum "merimobiles"
forum.merimobilesdotcom.previewdnsdotcom/showthread.php?465-Unified-thread -for-Mlais-MX28-stock-ROM-updates
Hope im not infringing on any xda TOS as i just seek some help.
Thanks
Please i need help, i have a mlais mx28 buy in buyincoins, with the refer gordete200, it´s all ok.
i´m very happy with the mlais mx28, but i used a 8 gigas sd card, it´s all ok.
My problem: i have install with flashtools the new rom stock update : mx28_0312_N2.rar from the official mlais mx28 web
When i have install this ultimate ( update ) ROM, it´s was with reebots, and the wifi and blutooth crash 0_0 !!! what happend?
I back to the Rom stock : 0115 but the sd partitions was changed : 1 gb for apps, and 1.75 gb for internal memory, it´s very strange, before install the Update, i had 2,3 gb for apps and 256 gb for internal memory...
I´m very worry, the actual problem is the sd card:
With 8 gb sd card class 10, it´s all ok, all correct, but when i put the 16 gb sd card class 10, it´s don´t mount sd correctly always.
I´m very crazy for all...
codedmax said:
Hello great bud,
Sorry for late reply, been up with alot on my plate from work lately, gps has been improved upon using that wonderful app "FasterGPS" now able lock in under a split couple of min not as before were it take like forever *Nice*
Click to expand...
Click to collapse
Good stuff. Once you have the gps.conf set up, try using Mobileuncle Tools to pull in the EPO (extended prediction orbit, basically a nice big list of keplers for the satellites so it knows which to expect to be in view at a given time without having to scan the sky for what's actually there) data which should stabilise the GPS even further.
codedmax said:
gut the same stock version "20140221" gusse its down to my own unit with the screen ish
Did a little searching around found a recent update from a online retailer outlet via their forum "merimobiles"
forum.merimobilesdotcom.previewdnsdotcom/showthread.php?465-Unified-thread -for-Mlais-MX28-stock-ROM-updates
Hope im not infringing on any xda TOS as i just seek some help.
Thanks
Click to expand...
Click to collapse
I wonder if it's the bodged Trebuchet they're using? It's a bit of a disaster as they've taken the CM launcher, bodged bits of MIUI into it and given the whole thing a "that'll do" look and feel. I replaced it with the real Trebuchet after a thorough decrapify, along with the AOSP stock keyboard. There's a "modified" apk of Trebuchet (all the dev did was lower the base API level so it would install on 4.1) floating about on the 'net somewhere. The various KitKat-alikes work fairly well but I wanted something open source that I could slam into /system/app without worrying.
It has taken a lot of faff to get to this stage but I now have a very usable and fast device for not a great deal of outlay.
gordo100 said:
Please i need help, i have a mlais mx28 buy in buyincoins, with the refer gordete200, it´s all ok.
i´m very happy with the mlais mx28, but i used a 8 gigas sd card, it´s all ok.
My problem: i have install with flashtools the new rom stock update : mx28_0312_N2.rar from the official mlais mx28 web
When i have install this ultimate ( update ) ROM, it´s was with reebots, and the wifi and blutooth crash 0_0 !!! what happend?
I back to the Rom stock : 0115 but the sd partitions was changed : 1 gb for apps, and 1.75 gb for internal memory, it´s very strange, before install the Update, i had 2,3 gb for apps and 256 gb for internal memory...
I´m very worry, the actual problem is the sd card:
With 8 gb sd card class 10, it´s all ok, all correct, but when i put the 16 gb sd card class 10, it´s don´t mount sd correctly always.
I´m very crazy for all...
Click to expand...
Click to collapse
Do you have a backup of the original ROM and scatter (partition layout) file? You really should (read: MUST) back up these devices before flashing new firmware as there's often bits missing, as you found with the WiFi and Bluetooth issue. MTK Droid Root & Tools will create a useful backup of the partition layout and contents for you without too much difficulty.
Please do not write to the preloader partition with the SP flash tool. Once the preloader is corrupt, your device is a brick which only JTAG will recover. I seriously doubt anyone has a JTAG solution for this device right now. There is no need to rewrite the preloader at all in any case so simply deselect the preloader block in SP Flash tool before downloading.
As for the SD cards, you need to make sure your card is formatted FAT, not NTFS, and the card must be partitioned correctly, i.e. the FAT partition must be the first primary. The MX28 will accept a card of up to 32GB if I recall correctly, which is the limit of SD-HC. Clockwork Mod can format your card for you.
Chron0s said:
Do you have a backup of the original ROM and scatter (partition layout) file? You really should (read: MUST) back up these devices before flashing new firmware as there's often bits missing, as you found with the WiFi and Bluetooth issue. MTK Droid Root & Tools will create a useful backup of the partition layout and contents for you without too much difficulty.
Please do not write to the preloader partition with the SP flash tool. Once the preloader is corrupt, your device is a brick which only JTAG will recover. I seriously doubt anyone has a JTAG solution for this device right now. There is no need to rewrite the preloader at all in any case so simply deselect the preloader block in SP Flash tool before downloading.
As for the SD cards, you need to make sure your card is formatted FAT, not NTFS, and the card must be partitioned correctly, i.e. the FAT partition must be the first primary. The MX28 will accept a card of up to 32GB if I recall correctly, which is the limit of SD-HC. Clockwork Mod can format your card for you.
Click to expand...
Click to collapse
Many thanks for your help. I have a back up of my mlais, i have a back up with mtk droid and tools 2.5.3 ( new version ), but when i put it on the flash tools, the cache and user is missing, and it´s imposible to download it. and then i put a recovery CWM on the mlais with droid and tools ( very easy ), and use a nandroid back up, it´s no problem, but the internal sd partition is always changed : 1 gb for apps and 1.75 for sd internal, i´m very sad because i would like back to the 2,3 gb for apps ( original partition )
Yes... always fat32 sd cards of course, but i have problems with the sd up to 8 gb, the mlais freeze, or sd desmount ( it´s imposible sometimes write in sd external ) i don´t find the problem with this... i have the rom stock : 115.
Other problem, i would like to up the ultimate ROM stock 221. but the wifi and bluetooth crash, and reboot the phone sometimes ( terrible...) , what can i do ? your solution is don´t stick the PRELOADER on the Flashtool when i upload the firmware ? it´s correct? ( i think that if don´t mark the preloader it´s imposible flash... ?¿ )
Many thanks for your help !
gordo100 said:
Other problem, i would like to up the ultimate ROM stock 221. but the wifi and bluetooth crash, and reboot the phone sometimes ( terrible...) , what can i do ? your solution is don´t stick the PRELOADER on the Flashtool when i upload the firmware ? it´s correct? ( i think that if don´t mark the preloader it´s imposible flash... ?¿ )
Click to expand...
Click to collapse
No, what I'm saying is we don't yet know why the WLAN and Bluetooth stop working when a different ROM from the one flashed at the factory is installed. There is clearly some mechanism at work here that is blocking those two devices after an update and it's not the usual shared objects as it is on other devices. It also doesn't seem to be NVRAM related as the MAC and BDaddr remain once the old firmware is re-flashed.
This same problem occurs with all the custom ROMs on needrom.
The reason I say do not needlessly flash the preloader is the danger of a full brick from which you cannot recover. The preloader code very rarely changes - its only purpose is to provide an interface to SP flash tools or boot; think "BIOS" in PC terms - so it is a pointless risk. You most certainly can flash the other blocks with the preloader block deselected.
The bottom line right now is stick with the factory ROM, install CWM, apply the system mount fix and use Xposed and suchlike to customise until we come up with something a little more sensible or at least find out why the WLAN and Bluetooth stop working.
Given that the Wiko Darkmoon is based on the same SoC and has full sources available <EDIT: It isn't. It's just the kernel as usual.>, it may be prudent to wait until someone with more clue than I has a look at what makes these things tick.
Chron0s said:
No, what I'm saying is we don't yet know why the WLAN and Bluetooth stop working when a different ROM from the one flashed at the factory is installed. There is clearly some mechanism at work here that is blocking those two devices after an update and it's not the usual shared objects as it is on other devices. It also doesn't seem to be NVRAM related as the MAC and BDaddr remain once the old firmware is re-flashed.
This same problem occurs with all the custom ROMs on needrom.
The reason I say do not needlessly flash the preloader is the danger of a full brick from which you cannot recover. The preloader code very rarely changes - its only purpose is to provide an interface to SP flash tools or boot; think "BIOS" in PC terms - so it is a pointless risk. You most certainly can flash the other blocks with the preloader block deselected.
The bottom line right now is stick with the factory ROM, install CWM, apply the system mount fix and use Xposed and suchlike to customise until we come up with something a little more sensible or at least find out why the WLAN and Bluetooth stop working.
Given that the Wiko Darkmoon is based on the same SoC and has full sources available <EDIT: It isn't. It's just the kernel as usual.>, it may be prudent to wait until someone with more clue than I has a look at what makes these things tick.
Click to expand...
Click to collapse
Many thanks Chronos!, The problem is also with the official ROMS on mlais.com/mlaismx28 i don´t understand it...
Please i need help to back restore the partitions of my sd internal ( ROM ), i would like back to 2,3 gb for apps, actually i have only 0,98 gb and 1,75 gb internal store.
I think that the solution is back up for flash tools and reflash with the rom stock ( the back up of mlais mx28 of my friend, he have other new mx28 )
But my BIG problem with the flash with flash tools is the USER DATA and CACHE is always empty, and then it´s imposible to reflash it it´s always and error : Rom changed PTM ...
Please, what can i do for have USER DATA and CACHE with mtk droid and tools 2.5.3 versión?? ( in this version to click User data and Cache with to do the back it´s imposible, this option is missing in 2.5.3. version )
http://dl.xda-developers.com/attachdl/b2f11c741aab592a8f66616d932af983/533c2dcc/2/6/6/4/5/2/2/Sin_t_tulo.jpg
[ROM] Official Update
Hello guys, there's a new rom update for the mx28
Official Mlais MX28 version: Mlais_MX28_20140312
www.needrom.com/mobile/mlais-mx28-2/
Try it out seems, it works perfect.
Cheers!!
my concern is that I don't want to lose TA/DRM keys just to root. not sure exactly what Ill be missing out on without it or if i can get the functionality back. also not sure, but if i do unlock bootloader, install the custom kernal, am i free to update the device with normal updates or will that break something? sorry, i went through a lot of the threads, but the info is a bit confusing and lots of redirects thru all the different threads.
edit, if you do unlock bootloader, can you relock without those keys? just worried for warranty purposes, i.e. if i get screen creaking and then can't return it cause i wanted to root but now i cant set it back to stock
No, it's not confusing, it's only confusing for people who are a bit lazy to really read.
It has been very clearly stated numerous times that ATM root is only possible with unlocked bootloader and losing TA data, because for a locked-bootloader-root an exploit is needed. It's very unclear whether such an exploit will be found or whether it's even possible.
You should ask Sony - I can't imagine that the service would refuse warranty when your screen creaks, because that problem very obviously has NOTHING to do with software modifications!
The DRM keys and X-Reality engine are superfluous anyway, so losing TA data should not be a concern when unlocking.
hasenbein1966 said:
No, it's not confusing, it's only confusing for people who are a bit lazy to really read.
Click to expand...
Click to collapse
I also found different statements regarding that matter. BECAUSE I read.
You should ask Sony - I can't imagine that the service would refuse warranty when your screen creaks, because that problem very obviously has NOTHING to do with software modifications!
Click to expand...
Click to collapse
Right !
The DRM keys and X-Reality engine are superfluous anyway, so losing TA data should not be a concern when unlocking.
Click to expand...
Click to collapse
DRM keys are superfluous to people who don't use DRM protected services. If you don't use that services, it doesn't mean others do the same.
X-Reality is a great feature. I compared two Z2s with and without X-Reality: The benefits are real obvious, sometimes close to overwhelming.
Losing X-Reality is the one and only reason for me not to root my Z2, yet.
thanks for the clarification. i wasn't being lazy, there are several threads that redirect to several other threads each (some of which aren't even about the z2 tablet specifically) and the message tends to get blurred after digging through several pages of threads that may or may not even have bearing on what you're trying to do.
i am assuming that without drm keys it will be impossible to return to stock (at least with working bravia engine and other protected services) would this be true? is there any work around to get these services back after you root, or are they gone forever?
also, my main reasons for wanting root are for removing restrictions on SD card, is there any non-root work arounds for this? (also xposed)
My z2 tablet should be arriving today, I am going to try to use it without root for a while to see if i can mentally deal without having xposed and full access to sdcard, hopefully i can hang, cause i'm not crazy about losing functionality (superfluous or not) forever from a brand new device i just paid lots of money for
also still trying to find clarification on updates, once unlocked & rooted can i just use regular updates or will that break the modified kernal and cause issues? i'm not sure if the modded kernals out there are for the latest version on firmware and how that is handled, all of my rooting experience just comes from flashing new updates of ROMs to my device (like AHRD or Hyperdrive), so i've never dealt with system updates to stock firmware while being rooted and unlocked.
thecrunked said:
... and the message tends to get blurred after digging through several pages of threads that may or may not even have bearing on what you're trying to do.
Click to expand...
Click to collapse
Exactly.
i am assuming that without drm keys it will be impossible to return to stock (at least with working bravia engine and other protected services) would this be true? is there any work around to get these services back after you root, or are they gone forever?
Click to expand...
Click to collapse
No workaround, yet, keys and X-Reality seem to be gone forever.
I just don't understand why Sony doesn't provide a means for backing up that data...
also, my main reasons for wanting root are for removing restrictions on SD card, is there any non-root work arounds for this? (also xposed)
Click to expand...
Click to collapse
Nothing known at present. :/
also still trying to find clarification on updates, once unlocked & rooted can i just use regular updates or will that break the modified kernal and cause issues?
Click to expand...
Click to collapse
No regular updates, you need to flash new firmware manually.
Note: I did not root my Z2, yet - because I don't want to lose DRM keys and X-Reality, so my answers are not based on my own experience.
copy this into the search forums
Rooting Sony tablet z2 keeping warranty with locked bootloader
Just reading this thread and something caught my attention; you lose x reality when you root.. Now if I root and keep stock firmware, I would assume I still have x reality. Please correct me if I'm wrong
meteor999 said:
Just reading this thread and something caught my attention; you lose x reality when you root.. Now if I root and keep stock firmware, I would assume I still have x reality. Please correct me if I'm wrong
Click to expand...
Click to collapse
You don't need to unlock your bootloader anymore (for .402 firmware), so you won't lose anything except for a security measurement
thecrunked said:
my concern is that I don't want to lose TA/DRM keys just to root. not sure exactly what Ill be missing out on without it or if i can get the functionality back. also not sure, but if i do unlock bootloader, install the custom kernal, am i free to update the device with normal updates or will that break something? sorry, i went through a lot of the threads, but the info is a bit confusing and lots of redirects thru all the different threads.
edit, if you do unlock bootloader, can you relock without those keys? just worried for warranty purposes, i.e. if i get screen creaking and then can't return it cause i wanted to root but now i cant set it back to stock
Click to expand...
Click to collapse
search "Rooting Sony tablet z2 keeping warranty with locked bootloader" in the forum search bar
I've rooted mine with a locked bootloader.
Currently, probably the easiest way to root it is to just use Towelroot. You will need to download the APK (via clicking the red icon on the site), save the APK, and install it. root it (via the application you just installed, just click the button!), then go over to the Google Play Store and download SuperSU (or any other root manager, altough it seems that SuperSU stands the most supported to date). It will probably ask you to update your SU binary (if it gives you an error doing so, just reboot the device). Once your rooted, head over to the Sony TA Backup forum, download the program (as I know of it only works on MS Windows), run it, and backup your TA's. If you ever need to restore your TA's, just run the script again and follow the menu in the command prompt to restore it (if I am correct it relocks the bootloader too).
Last note, if you need to restore your TA's, whatever you do, DO NOT USE SOMEONE ELSES! This will brick your device as I have read from many.
Also, if you want to unlock the bootloader, you can head over to http://developer.sonymobile.com/unlockbootloader/ and unlock it, however I would use it for a few months just in case if you can't relock it. I would recommend that you do not unlock it until you back up your TA's.
Hope this will save a few hours for some! If anyone wants me to clear up on something too you can ask.
I tried using Towelroot on my Z2 Tablet (SGP561; Build: 17.1.D.0.417) and it said it was successful, but I couldn't get SuperSU or Superuser to work no matter what I tried (and I previously had success rooting other devices) so I am assuming at the moment that it gave me a false positive on success.
I tried a few other methods each without success. Cyanogenmod doesn't support it and neither does "Safe Root". I did appear to have some success with Motochopper n7, but when it failed to reboot the device (didn't give me an option to do it manually) and then cleaned up.
Manually rebooting the device after it finished resulted in no improvements, but trying the Motochopper exploit again indicated that it recognized a previous rooting and so it failed for that reason:
Code:
[*]
[*] Motochopper: Android root exploit (Windows version)
[*] v1.0
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on the Motorola Razr HD, Razr M, Razr Maxx HD, and Atrix HD.
[*] Supports lots of other devices as well. ;)
[*]
[*] Before continuing, ensure that USB debugging is enabled, that you
[*] have the latest USB drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] WARNING: This will likely void the warranty on your device. I am
[*] not responsible for any damage to your phone as a result using this
[*] tool.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Pushing exploit...
2109 KB/s (1283460 bytes in 0.594s)
[*] Pushing root tools...
1952 KB/s (91980 bytes in 0.046s)
2296 KB/s (1867568 bytes in 0.794s)
2446 KB/s (969701 bytes in 0.387s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
[*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.
[*] Cleaning up...
[*] Exploit complete. Press enter to reboot and exit.
Press any key to continue . . .
Of course, root checkers say the device isn't rooted, but on my towelrooted phone it says that anyway unless it is given super user privileges, so I have no way of knowing if it is rooted or if it isn't. I am inclined to believe that it isn't though because TA backup fails:
Code:
[ ------------------------------------------------------------ ]
[ Backup TA v9.11 for Sony Xperia ]
[ ------------------------------------------------------------ ]
[ Initialization ]
[ ]
[ Make sure that you have USB Debugging enabled, you do ]
[ allow your computer ADB access by accepting its RSA key ]
[ (only needed for Android 4.2.2 or higher) and grant this ]
[ ADB process root permissions through superuser. ]
[ ------------------------------------------------------------ ]
Waiting for USB Debugging...OK
Pushing Backup TA Tools...OK
Checking for SU binary...FAILED
Requesting root permissions...FAILED
=======================================
CLEAN UP
=======================================
Deleted file - C:\Users\Elliander\Desktop\Backup-TA-9.11\Backup-TA-9.11\tmpbak\r
ootPermission
Deleted file - C:\Users\Elliander\Desktop\Backup-TA-9.11\Backup-TA-9.11\tmpbak\s
u
Removing Backup TA Tools...OK
Killing ADB Daemon...OK
Press any key to continue . . .
I actually do want to Unlock the boot loader, it's just that I want to back up the DRM keys first. My tablet it already unlocked to be used with any carrier, but I think it's ludicrous that these types of restrictions are allowed on such expensive hardware. At the very least Sony should officially have a tool to backup the keys when unlocking so that it can be restored to the same device.
EDIT: When I looked in:
About Tablet > Status
On the bottom under "Rooting Status" it says "Rooted"
So I'm guessing my only problem is in getting the Super User binaries to work?
EDIT 2: BusyBox Installed (from Play Store) also says my device is rooted, so something I did in the above worked. Unfortunately, the install of Busybox also failed.
I don't know why you've had to jump through hoops, but search for "easyroot"
I ran v5 on the older firmware and v11 on the latest firmware 17.1.2.A.0.314, works perfectly, installed supersu from play store immediately afterwards.
FWIW towelroot did not work for me either on .314 but I never tried it on the last firmware
wintermute000 said:
I don't know why you've had to jump through hoops, but search for "easyroot"
I ran v5 on the older firmware and v11 on the latest firmware 17.1.2.A.0.314, works perfectly, installed supersu from play store immediately afterwards.
FWIW towelroot did not work for me either on .314 but I never tried it on the last firmware
Click to expand...
Click to collapse
It's a nice idea, but it doesn't work. "operation not permitted". Here's the output from Easy Root:
Code:
==============================================
= =
= Easy Root Tool v11 =
= Supports various Xperia devices =
= created by zxz0O0 =
= =
= http://forum.xda-developers.com/ =
= showthread.php?p=53448680 =
= =
= Many thanks to: =
= - [NUT] =
= - geohot =
= - MohammadAG =
= - cubeundcube =
= - nhnt11 =
= - xsacha =
= =
==============================================
=============================================
tr.apk not found. Trying to download from
https://towelroot.com/tr.apk
=============================================
######################################################################## 100.0%
=============================================
Extracting libexploit.so using 7z
=============================================
OK
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
Make sure you have only one Android device connected
BlueStacks emulator can also cause problems
=============================================
Device found
=============================================
Getting device variables
=============================================
Device model is SGP561
Firmware is 17.1.D.0.417
=============================================
Sending files
=============================================
221 KB/s (1585 bytes in 0.007s)
3452 KB/s (657704 bytes in 0.186s)
368 KB/s (1133 bytes in 0.003s)
1854 KB/s (9496 bytes in 0.005s)
2670 KB/s (13672 bytes in 0.005s)
Copying kernel module...
2805 KB/s (34473 bytes in 0.012s)
249 KB/s (767 bytes in 0.003s)
1659 KB/s (13592 bytes in 0.008s)
Kernel version is 3.4.0-perf-g31245c3
Version does not match 3.4.0-perf-ge4322cd, needs patching...
1+0 records in
0+1 records out
19 bytes transferred in 0.001 secs (19000 bytes/sec)
Kernel module patched.
modulecrcpatch (by zxz0O0)
module_layout: patched to 0xCFADE050
__aeabi_unwind_cpp_pr1: match
kallsyms_lookup_name: not found
printk: not found
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: match
successfully patched
=============================================
Loading towelzxperia
=============================================
2211 KB/s (13592 bytes in 0.006s)
3211 KB/s (197320 bytes in 0.060s)
=============================================
Waiting for towelzxperia to exploit...
towelzxperia by zxz0O0 (EasyRootTool Version)
libexploit by geohot
libzxploit.so created
doing the magic
creating vm (loljavasucks)
mount: Operation not permitted
cleaning up
Also, as I said before, my firmware is 17.1.D.0.417. Yours can't be the latest firmware if my firmware is a higher number. I'm still stuck in this limbo where some apps think it's rooted and other apps don't.
EDIT: Despite the error it gave me, I tried installing SuperSU by chainfire again and I seemed to get farther at least, but it failed. Rebooting to try again.
EDIT 2: It also gave me this error on my computer when I rebooted the device:
Code:
Checking if device is rooted...
error: device not found
Error: device not rooted
Press any key to continue . . .
But when I went into SuperSU it didn't give me any errors. I went into Root Explorer and it actually asked me if I wanted to grant super user privileges, but I don't think it's fully rooted though. The root folder is empty, and although I can see the files of other directories, it fails to touch a few things. I kind of expected that would happen to bootanimation.zip, but I also can't edit Platform.XML to restore write permissions. I have done this before on other devices so I know I was doing it correctly, but it just failed to edit. I even tried an app to do so, but it also failed. It's rooted enough to see the files and open them. I can even copy files otherwise hidden and it appears to be able to mount as read/write. It's just that it always fails to do anything with it.
I then went and installed "Mount /system (rw / ro)" and although it appeared to work successfully after granting it super user privileges, it still didn't allow me to edit the files in root explorer, so I installed FX and and it's root add on module. I tried to edit the files, but it wasn't mounted as "Read/Write" as far as it's concerned and when I tried doing so within it's menu it just said "Error" The operation could not be completed"
So... am I rooted or not? Easy Root definitely helped me get farther, but not far enough to actually do what I needed the root to do.
EDIT 3: After a few minutes, for some unknown reason, Root Explorer allowed me to edit Platform.XML to add <group gid=”media_rw” /> under WRITE_EXTERNAL_STORAGE (still won't work in FX though) and of course I still can't edit bootanimation.zip, but as a test I successfully moved some files from the internal memory to the 128 GB micoSD so I'm at least rooted enough to restore access to the SD card so I will give it some time to see how much I can do with it.
P.S. - There is a forum bug. When I edit posts on a tablet there are no problems, but when I do so on a computer it tells me I have to wait 5 minutes before writing a new post to prevent spam - even though it's not a new post, it's an edit of an old post. Just like there is a weird thing where it will let me post links in a tablet, but not in a PC. Unfortunately, there doesn't appear to be any bug report form or moderator contact links so just putting it here.
well sorry no idea what state you're in. I notice you are SGP561 (whatever the heck that is!!! ), I am SGP511.
Can only say that for my device, easyroot worked 100%.
EDIT: I think you are Verizon user? well in that case good luck and get used to it lol. Verizon always have different firmware / build for their devices so you're always in the XDA development minority. Sometimes exploits and/or unlock bootloader is never available.
UPDATE: I was able to debrick the phone. Read my later post for details.
----------------------
Hi All,
Thank you all for having amazing community of hackers and developers here. You guys rock.
I started my search for a new rugged rootable phone recently and I settled on Poptel P60. It is a great phone though slightly bigger than what I normally get. Nontheless, the specs are excellent and the price is fair!
I've had a limited success rooting and customizing this phone. The OEM interface is almost bearable but overall the "Customized UI" felt like a downgrade from stock Oreo. It has a very annoying feature of reverting to stock launcher on startup, even when I selected Nova as my default one. The stock launcher is not that great. This, and the lack of ability to use x.flux, Titanium Backup and other root-only apps drove me to try hacking things again.
After emailing the manufacturer they provided the firmware but it is in CPB format. I tried at least 3 different converters for CPB to MTK Scatter and they all either freeze or hang. No luck.
Instead I did a rom readback with SPFlashTool and then cut up the partitions with Wwr. Now I've finally had the recovery partition! I used CarlivImageKitchen to port TWRP from a similar device, Ulefone Armor 5. The chipset and resolution are same. After some trial and error it worked! I had to use USB-OTG for input and external sd card had a weird label, but I was able to install Magisk from the SD card to root, followed by XPosed, full package. It worked! If anyone needs my ported TWRP Recovery for Poptel P60 just ask!
However, the manufacturer UI did complain a lot about the phone being rooted. Eventually, somehow, Magisk stop receiving root requests. They never showed up and timed out! Very strange, because apps that already received root continued working. I tried a lot but could not fix the issue. I was fed up. I wanted to do a manufacturer reset (in hopes of starting from scratch and then attempting to port Lineage or something) but, as I've mentioned, I have not received a firmware compatible with SPFlashTool. I tried to make one from Armor 5. The partitions were almost the same (both are MT6763 devices). One was out of order, and offsets were different and I patched all those. To be clear, I used all the partitions and layout extracted from my rom readback that was cut up by Wwr. I only used the Armor 5 scatter as a reference for file format. I edited the layout to match everythign I saw in Wwr.
This is where the horror begins. I tried flashing (Download Only) with SPFlashTool but got some error saying something changed. "Do you want to do Format & Download instead?". Being an inexperienced idiot that I am, I said yes!
Now, the phone appears bricked. No lights. No screen output. Cannot enter fastboot. Cannot enter recovery. Cannot boot.
I have a feeling the preloader got corrupted. I'm not sure this is the case because I've omitted the preloder from download. At least the first time the phone started acting bricked. The device still shows as Mediatek USB VCOM device and flashing gets initiated but all attempts to flash result in errors. MA checksum mistmatch or something along that order. I've tried a lot of things and I'm stuck! For good or for worse I've tried flashing Ulefone Armor 5 preloader but I'm getting the same error when trying to flash it.
Here is what I have...
- Stock firmware in SPB format. I can't use it and nothing I tried worked for converting it.
- ROM dump made with SPFlashTool
- Wwr was able to extract every partition except preloader. This includes nvram, etc. I'm not sure why it was not able to extract the bootloader.
- TWRP port that worked. Seems not useful if the phone does not start.
- Preloader for Ulefone Armor 5, (same chipset and resolution)
Clearly I am an idiot for using "Format & Download" option. I've found posts later suggesting against it. I am also over my head for trying to tackle a new device by myself, though I have had a marginal success with porting TWRP and installing Magisk.
Now, I feel like idiot and I am stuck! I beg you, XDA developers, if you have any advice (besides not being an idiot in the future), please share!
Try bringing it back to the carrier and just say that you don't know why it is broken. Maybe they could help you out.
Say maybe something like you wanted to do a factory reset and now everything is broken.
SkylinesHD said:
Try bringing it back to the carrier and just say that you don't know why it is broken. Maybe they could help you out.
Say maybe something like you wanted to do a factory reset and now everything is broken.
Click to expand...
Click to collapse
That wouldn't work, heh. I bought this phone on eBay and rights now it's currently sold by a handful of sites. It is on warranty but returning it back to China would be complicated. At any rate, I live on the edge outside of warranty!
I was just about ready to give up and feel like the biggest reckless loser on Earth... Days of tinkering around with nothing but a phone brick to show for it. Poptel tech support wouldn't provide me with MTK scatter. All they gave me was this SPB firmware that nobody uses and it crashes every converter I threw at it. Useless.... No fastboot. No recovery. No functional bootloader.
The amazing GOOD NEWS is I have debricked the phone... I used a bootloader from another phone's firmware: Cubot_Power_MT6763_180607_8.1.0. Unlike Ulefone Armor 5's preloader this one worked! It seems like it's the only thing I was missing because the phone starts up and everything seems to work. I must have done a good job with all other partitions but I'll try to watch for signs of anything else broken. Right now it seems fine.
I'm not sure if the bootloader was completely gone, corrupted, or an incorrect one was used. All I know is I was able to download Cubot Power's working bootloader (also MT6763) with SPFlashTool. Nothing like a feeling of unbricking your phone!
I will post more updates if that's ok... I'm hoping to port Lineage on it (I've never tried that before) or at least find a way around the manufacturer's clunky UI. The hardware is great otherwise. If anybody wants a working ported TWRP image or the scatter I used for debricking just ask! I will make a post later if I have more success with customizing the phone. The phone is debricked and I have a scatter and images to fall back on if anything goes wrong. Woot! Thank you everyone who developed these great tools.
I have the same phone been looking for info. there's a thread on 4pda with poptel p60 that has the scatter file and firmware. Any chance you could post the twrp for this phone? having trouble trying to port myself cant figure out port 6763 from the guides available.
4pda.ru/forum/index.php?showtopic=933002
Firemware:
drive.google.com/uc?id=1PXA9s2ZgHoH6ZWP5ZJPckE4KyJBwPKuw&export=download
idaman0 said:
Hey man,
Was wondering if you saw my post on your thread. Looking for TWRP for the Poptel P60.
Thanks,
telegram @drmethyl
Click to expand...
Click to collapse
Hey man! Sorry for a slow reply. Was traveling for a few days.
Here is what I have. I started with a TWRP for Armor 5 (also MT6763) and I ported it for Poptel P60 using one of the guides on the forums. It works but it's not perfect. The touchscreen doesn't work, so you have to use USB OTG. Also, internal and external SD card mounts work but labels are confusing, so please be extra careful if wiping/formatting those. I advise popping the SD card out of the phone if wiping/formatting, just in case.
My experience with the phone is it is not the most friendly for rooting. Poptel's customizations are pesky and get in the way. The launcher keeps resetting to default on startup, even after you specify a different one. If you uninstall/disable the OEM launcher there will be red a label on top right of the screen, saying "Customization" that I have not found a way to get rid of. There are other things too, like I keep losing ability to add superuser permission to new apps... Can't figure out why, but sometimes reinstalling Magisk helps. Be very careful when using Magisk Hide, this can turn off your ability to use SIM cards, at least temporarily until you disable hide and restart. Other things is superuser apps don't always launch on startup. Anyway, I don't want to discourage you too much... Here is my twrp port.
https://mega.nz/#!MNVGhaYS!63ovQeowwoP1oE3v6-_ZS8gKx_-mxOh4G4qWcKRbuiQ
Another thing I discovered is GSI builds work mostly well on the phone... with all except one thing, which is mobile data, which seems broken.. Sadly, that's a deal breaker. OEM software is so pesky... It would be so nice to run a clean Android.
Let me know how it goes.
zeromemory_wtf said:
Hey man! Sorry for a slow reply. Was traveling for a few days.
Here is what I have. I started with a TWRP for Armor 5 (also MT6763) and I ported it for Poptel P60 using one of the guides on the forums. It works but it's not perfect. The touchscreen doesn't work, so you have to use USB OTG. Also, internal and external SD card mounts work but labels are confusing, so please be extra careful if wiping/formatting those. I advise popping the SD card out of the phone if wiping/formatting, just in case.
My experience with the phone is it is not the most friendly for rooting. Poptel's customizations are pesky and get in the way. The launcher keeps resetting to default on startup, even after you specify a different one. If you uninstall/disable the OEM launcher there will be red a label on top right of the screen, saying "Customization" that I have not found a way to get rid of. There are other things too, like I keep losing ability to add superuser permission to new apps... Can't figure out why, but sometimes reinstalling Magisk helps. Be very careful when using Magisk Hide, this can turn off your ability to use SIM cards, at least temporarily until you disable hide and restart. Other things is superuser apps don't always launch on startup. Anyway, I don't want to discourage you too much... Here is my twrp port.
Another thing I discovered is GSI builds work mostly well on the phone... with all except one thing, which is mobile data, which seems broken.. Sadly, that's a deal breaker. OEM software is so pesky... It would be so nice to run a clean Android.
Let me know how it goes.
Click to expand...
Click to collapse
sorry man, didn't end up using yours theres a twrp on 4pda now with a mod to flash to keep root. I'll upload for you here if you don;t have an account there.
The patch for the Light-kastomizator v.12 factory firmware.
I decided not to bother with the draining and distribution of modified firmware as a whole, easier to apply the patch, and ... you're done!
If that - the factory firmware v.12 lies with us -HERE, no problem you can return everything back, or (if there is something Kolupaev), first ask her, and then patch.
#
What is done
Будут удалены:
/system/tts
/system/app/QK_LogSystemAbroad_wm_bl
/system/app/QK_Sos
/system/app/QK_PrivacySpace
/system/app/QK_PersonalAssistScreenAbroad_V2
/system/app/BY_3RD_OperaMiniBrowser_OEMBranding
/system/app/BY_3RD_OperaNews_OEMBranding
/system/app/Drive
/system/app/Duo
/system/app/Gmail2
/system/app/GooglePrintRecommendationService
/system/app/LatinImeGoogle
/system/app/Maps
/system/app/Music2
/system/app/PartnerBookmarksProvider
/system/app/Photos
/system/app/YouTube
/system/app/Videos
/system/presetapp/BY_3RD_OperaMiniBrowser
/system/presetapp/BY_3RD_OperaNews
/ system / priv-app / MtkCellBroadcastReceiver
/ system / priv-app / ConfigUpdater
/ system / priv-app / GoogleFeedback
/ system / priv-app / FilesGo
/ system / priv-app / GooglePartnerSetup
/ system / priv-app / QK_MagazineAbroad
/ system / priv-app / Velvet
The system additionally installed:
ES_Provodnik_3.2.5.5 (graphic mode "Panatta-sport")
the SD Maid Pro - system Cleanup (Lite Mod "Breathe of fate" )
Changes:
By default the system is set to Russian language , region and time zone Russia / Moscow. Setupwizard (first assistant settings) is not cut off.
GBoard keyboard replaced by fashion Antonbeard GoogleKeyboard(with a limited access to the Internet is built dictionaries -.. English and Russian)
Google-search is replaced by the latest beta (it is possible to change the style and transparency of the widget)
have been added and changed some default sounds and ringtones, and the default there as a very sadly.
Blocked by advertising the hosts file.
Improved energy efficiency due to shutdown of background update service does not fall asleep GAPPS and downloaders (allowed these services Doze mode).
#
Setting:
1. Throws on micro SD-card this patch.
2. Downloading the last zip-installer " Magisk-v ..... the zip " and also copy it to the SD-card, turn off the phone.
3. Through the SP Flash Tool sewn recovery "TWRP" (the system can not be loaded !!!).
4. Vaypaem userdata (reset to factory settings) through better "factory mode" (volume down inc +) / select "Clear eMMC".
After reset immediately loads in the TWRP (inc + volume up), and from the sd-card in turn apply patches "LiteMod_Poptel_P60_v.12.zip" and "Magisk-v ..... zip". Reboot from the installation refuse twrp-applications.
Done, you have custom firmware!
(If twrp and Ruth is already installed,
After the completion of all the manipulations, it is desirable to flash the stock (factory) rekaveri, then no problem can be used to reset the system from the Android menu and install the firmware update OTA (over the air).
Download: LiteMod_Poptel_P60_v.12.zip
PS. Sberbank + contactless payment working properly, despite the fact that the system has been modified and installed Ruth! :derisive:
Click to expand...
Click to collapse
3.2.3 TWRP by Jemmini for "Poptel P60" ( with the phone port Blackview BV9500): Attached file recovery.img (17,27 MB)
The port used by the kernel to flash Android 8.1.0 version of "POPTEL_V12_20181030"
WARNING !! After installing recovery, subject to permit changes in the system partition, install ROOT is required, otherwise the system will not boot. if not to accept the possibility of changing the system partition and establish the patch-root subsequent restart in overwrite TWRP recovery returned drain-
Attached fileMT6763_Android_scatter.rar(1.28 kb)
#
Getting ROOT
For ROOT set out under TWRP (pre throwing off the memory card), this patch: Attached fileMagisk-v18.0.zip (3,99 MB)
#
Stokovye boot / recovery
from said EEPROM: Attached filestock.rar (22,75 MB)
#
What does not work:
1) Do not see "the internal memory" (can not decipher the "data" section and ask when starting TWRP password).
Solution:
download the patch: Attached filedisable_encryption_P60.zip (133.89 KB)
throw it on the memory card, boot into TWRP, go to the "mount" to put a checkbox on the vendor , then go to the "install" and install the patch.
After installation make data in the "cleaning" cleaning (possibly cleaning does not help but the formatting of data should definitely help)
after data manipulation TWRP be able to work with the data section
2) is not working USB / MTP mode into TWRP
#
Information for those who are "in the tank" :
When TWRP presence in the smartphone in any case and under no circumstances should you do reset through the system.
Resetting takes place only directly through TWRP (standard cleaning sections)
If you run the command via the android in the first place, it can not be executed because it does not understand the TWRP.
and secondly, you get a constant load in TWRP because it has not yet executed the command android you will always be send to recovery /
Solution for "tank": need to install flow-recovery to be completed through a reset command or cancel it.
Another solution I personally do not know
Just do not forget about gratitude : Jemmini,- for the compilation of the TWRP which served as donorUrree,- order TWRP and testing (nothing would have happened without it)Message edited Lomaster_Serg - 6.1.19, 03:02
Click to expand...
Click to collapse
rapidgator.net/file/84ccd2d612ade0256eb927895d4ed37e/LiteMod_Poptel_P60_v.12.zip.html
rapidgator.net/file/c77fec40e349f8083eda14bf7058425c/recovery.img.html
rapidgator.net/file/6621d517cef9aa10abc78b40bcdc8b26/stock.rar.html
rapidgator.net/file/7a7db29c0d35eee169b76698aac6b50b/MT6763_Android_scatter.txt.html
drive.google.com/uc?id=1PXA9s2ZgHoH6ZWP5ZJPckE4KyJBwPKuw&export=download