Persist Resurrector
Code:
#include<disclaimer.h>
void main()
{
clrscr();
printf("If you are reading this, your warranty is already void.");
printf("/nYou can't blame me for that. It is your own doing");
printf("/nFor using this software, you need to agree following things");
/* */
/*I am not responsible for bricked devices, dead SD cards,*/
/* thermonuclear war, or you getting fired because the alarm app failed. Please*/
/* do some research if you have any concerns about features included in this software*/
/* before using it! YOU are choosing to make these modifications, and if*/
/* you point the finger at me for messing up your device, I will laugh at you.*/
/* */
getch();
}
Hello everyone!
It has been observed that few custom ROMs of Mi A1 change persist partition. This has no observable (yet) effects when using those ROMs. However after flashing stock ROM back, connecting to Wi-Fi becomes impossible. This happens because the ROM changes your Wi-Fi MAC address. The custom ROMs causing this bug do not depend on Vendor MAC, so Wi-Fi works fine with them.
Reconstructing original vendor MAC address is possible, but ONLY if you have persist partition which belongs to YOUR PHONE. This means you HAVE NOT flashed any of the several persist.img files floating around xda.
If you have flashed someone else's persist image -
You CANNOT use this tool since you have destroyed the last chance to repair original Wi-Fi MAC.
You have lost your original Bluetooth MAC and replaced with someone else's.
You have lost calibration data of various sensors (Unconfirmed, but usually sensor calibration data is stored in /persist)
If you connect to the same Wi-Fi with someone else who is using same persist.img or has same MAC address by coincidance. Same for BT.
Wi-Fi where that MAC is banned won't let you join or if you added MAC filter to your own Wi-Fi it won't recognise your phone anymore.
It is illegal.
CosmicDan said:
Yeah that's actually illegal here in Australia too, and they DO crack down on it in many countries (cloned MAC's are a target for anti-terror units, and ISP's *can* see your device MAC's so that thread really should be taken down)
Click to expand...
Click to collapse
This is when this tool comes into picture. A guide is posted in guides section of Mi A1 forum by SevenSlevin. But it involves completely deleting the contents of the file which stores the MAC address. This deletes the faulty MAC addresses causing problems, but does not give you original Vendor MAC address (from Xiaomi) back. I personally didn't like losing the original MAC address which came from factory. I am sure there would be many of you thinking along the similar lines.
So what this tool does is it reconstructs your Wi-Fi MAC addresses using dark hex magic (pun intended) and pushes it back to your device, puts it in appropriate position if you want and voila!
FAQ (Recommended to read)
Add a MAC randomizer for people who already have destroyed their persist.
=> This looks like on the borderline of legality and illegality. I can add this feature in the next release if this is legal. (Please reply in this thread)
Is this tool safe?
=> I have tested it on 3 different Mi A1s and I haven't found any problem yet.
Will this work if I have xyz ROM?
=> I always use and prefer stock Oreo ROM when testing. So you have to find the answer yourself.
But it is best to be on stock ROM because it is the ROM which has the problem you are here to get fixed.
I have got a warning with an error code or FAILSAFE kicked in.
=> Send the error code here.
What is FAILSAFE?
=> Failsafe is a series of measures to avoid potential problems or damage done made by me for another personal project. Only a very small part is implemented here and this is made 60% failsafe which means there are *some* loopholes left due to time constraints and unnecessary redundancy, but you won't find them unless you are doing terminal stupidity.
This is the main reason why I am not releasing the source code. It is still in its infancy and it will be long before it will be mature.
Stick to the instructions and FAILSAFE won't kick in.
This software is NOT working at all.
=> Post here along with the steps you followed.
Awesome! YOU FIXED MY PHONE!
=> I am glad to hear read this. :highfive:
Requirements -
Mi A1 (stock ROM recommended)
Root access
ADB Drivers installed
Microsoft DOT NET Framework (Tested on v4+, but v3.5+ should work)
Your firstborn
{
"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"
}
(JK JK)
Downloads -
Attached to the bottom of this post.
Current version - 1.0.0.0
Date - 22/04/2018
File: Persist Resurrector v1.0.zip
MD5: 82fd5a6dfc28d2388649db4ae72c4538
SHA-512: a9eb3124315cf0cfe0875f1aae61127a4f71441fd294d63e46efa9fe198971e05a54aa2f15e70ebebfa356ae4b660356b24c424cd2008cefb56fed5fe740b81b
Individual file checksums are included in the zip.
No viruses included.
VirusTotal Scan
Only 1 (Dr Web) gives a False Positive.
Click to expand...
Click to collapse
Changelog -
v0.5, 20th April, 2018
Initial Release
Calculations working as intended
Manual file replacement
v0.7.5, 21th April, 2018
Automated file replacement
Changed code to be more effective and cleaned it up
v1.0, 22th April, 2018
xda release
FAILSAFE implemented
Click to expand...
Click to collapse
Instructions -
Download and extract the zip to any directory. (Avoid Program Files or at the root of Windows Installation Drive, UAC becomes a problem)
Run the Persist Resurrector.exe
Connect the phone via USB cable and unlock screen.
Press the buttons in the sequence as labeled on screen.
Give confirmations to ADB and Root as necessary.
Profit!
Developer of this tool, hnkotnis, has no responsiblity if your phone, memory card or you are bricked, bootlooped or damaged in any other way.
You are using this tool on your own and you take whole responsibility of any damage caused.
Feel free to POST this to your website or blog BUT DO NOT MIRROR DOWNLOAD LINKS. SHARE LINK TO THIS PAGE.
So that I can get the exact download count.
YOU CANNOT MODIFY, DISTRIBUTE (Free or paid), CHANGE or REVERSE ENGINEER THIS SOFTWARE.
Click to expand...
Click to collapse
Reserved
Sent from my epic G900F (CM11, [emoji173]️ Holo) Gadget of Mass Destruction using Tapatalk.
Ay the one that we all needed! Thank you!
Calibration also related to fingerprint sensor?
Nice work
I think a random MAC would be useful, legal issues aside. There are tools out there that anyone can use to freely edit and/or change MAC addresses in many hardware. The tools themselves are not illegal, bit the use of specific MAC's or non-original MAC's in certain situations may be illegal.
It would be good if you could provide an option to enter MAC manually too. The original MAC may be recoverable in some way, possibly by contacting Xiaomi or something. It sadly isn't printed anywhere on the box or anything.
iamshivendu said:
Calibration also related to fingerprint sensor?
Click to expand...
Click to collapse
That's a good point. A corrupt persist may be why some users cannot enrol more than X fingerprints. Not sure though.
Can someone mention which custom ROMs possibly change persist partition?
unos21 said:
Can someone mention which custom ROM possibly change persist partition?
Click to expand...
Click to collapse
All of them do AFAIK. Maybe only all 8.1 firmware.
CosmicDan said:
Nice work
I think a random MAC would be useful, legal issues aside. There are tools out there that anyone can use to freely edit and/or change MAC addresses in many hardware. The tools themselves are not illegal, bit the use of specific MAC's or non-original MAC's in certain situations may be illegal.
It would be good if you could provide an option to enter MAC manually too. The original MAC may be recoverable in some way, possibly by contacting Xiaomi or something. It sadly isn't printed anywhere on the box or anything.
Click to expand...
Click to collapse
I will try to implement both in the next release. Both are easy to add since most of the code remains same. No ETAs but it could be in the next week if possible. But if I cannot do it within next week then the release will be directly after 16th of may.
Sent from my epic G900F (CM11, [emoji173]️ Holo) Gadget of Mass Destruction using Tapatalk.
Am i the only one not having wifi issues after flashing stock rom? I used a lot of custom 8.1 roms and if theres new update in stock rom i flashed back to test it and not having wifi not connecting issues. Hmm ?
t0per666 said:
Am i the only one not having wifi issues after flashing stock rom? I used a lot of custom 8.1 roms and if theres new update in stock rom i flashed back to test it and not having wifi not connecting issues. Hmm ?
Click to expand...
Click to collapse
After flashing custom rom have you tried connecting to 5hz wireless network?
This tool just help me fix my phone , thank you man :v
ShazlieyAzizan said:
This tool just help me fix my phone , thank you man :v
Click to expand...
Click to collapse
and how did you do it? You were in the last rom stock right? I'm going crazy and I can not solve it, thanks.
ruperxl89 said:
and how did you do it? You were in the last rom stock right? I'm going crazy and I can not solve it, thanks.
Click to expand...
Click to collapse
im from cardinal aosp to stock rom based on nougat , i realize that stock rom cant connect to my wifi , then i look up to this thread and follow the instruction . that's it and all fixed now
ShazlieyAzizan said:
im from cardinal aosp to stock rom based on nougat , i realize that stock rom cant connect to my wifi , then i look up to this thread and follow the instruction . that's it and all fixed now
Click to expand...
Click to collapse
thank you i will try this now, i tried with last oreo build yesterday and it failed, sorry for my english
---------- Post added at 11:13 AM ---------- Previous post was at 11:07 AM ----------
ShazlieyAzizan said:
im from cardinal aosp to stock rom based on nougat , i realize that stock rom cant connect to my wifi , then i look up to this thread and follow the instruction . that's it and all fixed now
Click to expand...
Click to collapse
but you have some backup of /persist?
Hi mate, I've lost my persist partition (original), because of that, I've to erase the persist partition and reflash it from the "stock rom image" to stop the continue reboot bug. The IMEIs and S/N work great but the Wi-Fi and Bluetooth Macs are different now from the originals.
I know which were my MACs, is there some method to re-insert them???
Thanks for your time, kind regards.
I totally lost imei , sn , FSN and PSN due wrongly clicked flash_factory.bat , i send back for warranty but they can't fix and refuse to change board ( even i want to pay) .. hope this tools can help me find back my original mac address when i get back my device
ruperxl89 said:
thank you i will try this now, i tried with last oreo build yesterday and it failed, sorry for my english
---------- Post added at 11:13 AM ---------- Previous post was at 11:07 AM ----------
but you have some backup of /persist?
Click to expand...
Click to collapse
yes i do have
---------- Post added at 02:02 PM ---------- Previous post was at 01:59 PM ----------
JoKeRLeE said:
I totally lost imei , sn , FSN and PSN due wrongly clicked flash_factory.bat , i send back for warranty but they can't fix and refuse to change board ( even i want to pay) .. hope this tools can help me find back my original mac address when i get back my device
Click to expand...
Click to collapse
yeah actually they should refuse to check your phone because you the one who mess with the phone . hahah english tak padu type melayu la , imei lost semua tu sebab kacau system dia kan ? kalau betul nak hantar warranty ksi rosak die punya software sampai blank then kata jadi lepas update software , dorang confirm boleh tolong , anyway goodluck
Raskaipika said:
Hi mate, I've lost my persist partition (original), because of that, I've to erase the persist partition and reflash it from the "stock rom image" to stop the continue reboot bug. The IMEIs and S/N work great but the Wi-Fi and Bluetooth Macs are different now from the originals.
I know which were my MACs, is there some method to re-insert them???
Thanks for your time, kind regards.
Click to expand...
Click to collapse
In the v2 there will be a feature to add MAC manually.
Sent from my epic G900F (CM11, [emoji173]️ Holo) Gadget of Mass Destruction using Tapatalk.
It will possible add too the Bluetooth MAC???
Raskaipika said:
It will possible add too the Bluetooth MAC???
Click to expand...
Click to collapse
It is easily possible to add it. But it will need writing the whole code again. I will be busy with exams so it is on top of my to do list as soon as exams are over.
Sent from my epic G900F (CM11, [emoji173]️ Holo) Gadget of Mass Destruction using Tapatalk.
Related
Root Transmission
{
"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"
}
Root Transmission: the ONLY app that allows you to root other phones straight from your own device!
Inspired by Kos's p2p-adb hacking toolkit (http://hak5.org/episodes/hak5-1205), this app is a pleasant, easy way to root other phones while away from your computer! Just two buttons, Root and Unroot! Connect the cable and root away! It couldn't be simpler!
Even has its own terminal window so you can see exactly what's going on while your phone does its thing!
You will need a ROOTED device capable of USB hosting (USB On The Go), a USB OTG cable and one-click root scripts for the devices you wish to root.
Scripts and their associated files should be placed in /sdcard/RootTransmission/*devicename*/*version*/, otherwise it will not be available for use. *devicename* and *version* can be whatever you want.
Note that this is an UNSTABLE version, and you use this app at your own risk. Occasional force closes are to be expected (though they will most likely not break the phone you are trying to root). Incorrectly written scripts can permanently damage or brick both devices involved, so only use trusted 3rd party root scripts and at your own risk.
Click to expand...
Click to collapse
Screenshots
Changelog
1.01unstable
fixed bug that sometimes caused crashing when user closed app
fixed bug that caused app to crash if scripts directory did not exist
Much smaller size (166k)
made it for Android 4.0 and up (accidentally had it for 3.1 and up in Play Store, will re-add Honeycomb support if I find that it works reliably with it)
1.0unstable
initial public release
Click to expand...
Click to collapse
Planned features
Downloading scripts within the app
Nicer GUI
In-app help text
??? Suggest some!
Click to expand...
Click to collapse
(Removed from Play Store because Google said it was "dangerous")
Please do not mirror this apk, it is to be downloaded exclusively from XDA-Developers. Failure to comply will result in the removal of this app from XDA.
I've attached a zip with the files needed to root a Verizon Galaxy S3 (SCH-I535), extract it to /sdcard/RootTransmission/ to use.
Note that since I only have one USB host-capable device (my own S3), no warranty is provided over the functionality of this zip since I am unable to fully test it. (It is a repackaged version of the DebugFS one-click root found at http://forum.xda-developers.com/showthread.php?t=1883984 and thus will only work if the device to be rooted is running ICS, which shouldn't be a problem as of yet.)
Again, this is an unstable test version. It should mostly work, but no guarantees on its functionality.
Reserved for future use
Reserved for future use.
what device is supported? what device supported that can be rooted?
chev said:
what device is supported? what device supported that can be rooted?
Click to expand...
Click to collapse
In order to run the app, your device (the device that is already rooted) must support USB hosting/USB OTG. Most newer devices have this.
This app uses adb and scripts (which you must provide) to root devices. If there is a root method for the device that uses adb, then it will work.
In the case of the Verizon Galaxy S3 (my primary device), the root method for a stock ROM is to use adb to push an exploit that will allow us to install Superuser and the su binary. I believe the Asus Transformer Prime uses a similar method.
If the only root method available involves using a program such as Odin/Heimdall or a manufacturer's phone flashing utility, or a zip must be flashed in recovery in order to gain root, it will definitely not work. In the case of the HTC Sensation, you must flash a recovery and boot into it, then flash a zip containing the su binary as well as a controller app such as Superuser in order to gain root. So the HTC Sensation could NOT be rooted with this.
In the future I plan on building a compatibility chart within the app to determine which phones can run this app and which phones can be rooted with it, as well as downloads for the rooting process. In the meantime, if there is a phone you are looking to root with this, let me know and if possible, I'll craft a zip to use with this.
Updated Root Transmission to 1.01unstable.
Following changes were made:
-bugfix: app occasionally FC'd when closing app
-bugfix: app crashed if scripts directory did not exist
-smaller size (166k, old version was 1.62mb)
-made it available only for 4.0 and up (had it set to 3.1 and up by accident)
Available in first post or in the Play Store.
Keep sending in those bug reports, it really helps!
Also, if you have any new features you want to suggest, let me know.
I'm considering the following so far:
-Downloading scripts in-app
-Nicer GUI
-Help text
Added script for the Asus Transformer tablets (TF101/TF201/TF300T/TF700T) to the first post. It will only root tablets on 4.0 or below.
This app looks promising, keep it up this great work, :fingers-crossed:
Theoretically could this run any script over adb on another device. not just a root one?
one x
Hey does this work with the one x international version?
I believe that in order for the app to work properly, adb must be running as root, so no. It's not possible to use this with a non rooted phone.
HTC One X should be able to be rooted (as well as other devices relying on fastboot), but I haven't added support for it yet. A fastboot binary for ARM is available, so I'll package that into the app for next release. Stay tuned. However, I don't know about unlocked bootloaders and all that on HTC devices, so beware.
I'm also going to take a look at the Heimdall source code later so that you can perform Odin flashes over USB. This means that basically any Samsung phone should be able to be rooted, even without a one click root script.
All this stuff will take time though, and with school still going on it might take some time. But I'm definitely working on it!
Sent from my SCH-I535 using Tapatalk 2
Would it be possible to use this app to flash unsecured boot.img and then recoveries? Basically have it set up to download the recoveries and boot.img from a ftp or something? Can we basically just use the host phone as a standard ADB and Fastboot commander? Using regular commands?
root tranmission
i download the file, and recive the next error while unstalling:
parse error
there is a problem parsing the package
there´s any fix?
thanks in advance
Draciel882 said:
Would it be possible to use this app to flash unsecured boot.img and then recoveries? Basically have it set up to download the recoveries and boot.img from a ftp or something? Can we basically just use the host phone as a standard ADB and Fastboot commander? Using regular commands?
Click to expand...
Click to collapse
This is on my to-do list. I might also include a terminal emulator with access to the app's adb/fastboot binaries.
teran220 said:
i download the file, and recive the next error while unstalling:
parse error
there is a problem parsing the package
there´s any fix?
thanks in advance
Click to expand...
Click to collapse
Try installing from Play Store.
wchill said:
This is on my to-do list. I might also include a terminal emulator with access to the app's adb/fastboot binaries.
Click to expand...
Click to collapse
That would be awesome, let me know if you need some help testing. I've been wanting to be able to do this for awhile. It would pretty much eliminate the need for a computer when flashing roms on devices that have their bootloader already unlocked.
how to check my device is usb otg/host capable ?
anazhd said:
how to check my device is usb otg/host capable ?
Click to expand...
Click to collapse
Use this app by Chainfire
https://play.google.com/store/apps/details?id=eu.chainfire.usbhostdiagnostics
Sent from my SCH-I535 using Tapatalk 2
Wow, the idea behind your software is brillant!
I yet see a future world in which handset liberation is achieved and spread among users in dark corners of the streets! :silly: :laugh:
Hey there wchill , seems like you are an app dev rookie as I seen some stuff , well you aren't so different from me , PM me , I will help you in your project , btw I have seen a small thing , that the Settings button does nothing , to remove it remove in your mainActivity the lines that say onCreateOptionsMenu , as long as you don't need an options menu !
EDIT : No offence for calling you a rookie , I may have underestimated you , because your work is amazing , but I was talking the Java side of your knowledge , sorry if I offended you !
seaskyways said:
Hey there wchill , seems like you are an app dev rookie as I seen some stuff , well you aren't so different from me , PM me , I will help you in your project , btw I have seen a small thing , that the Settings button does nothing , to remove it remove in your mainActivity the lines that say onCreateOptionsMenu , as long as you don't need an options menu !
Click to expand...
Click to collapse
I know that the options menu is there, but I'm planning on adding to its functionality so there's no point in removing it yet. Don't worry, I didn't forget about it
Also, I only have one year of experience in Java, so my skills definitely are not the most top notch out there. I'd say not bad for being self taught though.
Anyway, in app downloads should be working by this weekend, depending on how much homework I get this week. Did a lot of it today, just need to make the frontend for it. After that I'll work on improving the GUI, because I really couldn't be bothered to spend more than 5 minutes making it what it looks like right now.
Expect an update in the next few days
Sent from my SCH-I535 using Tapatalk 2
{
"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"
}
This is an experimental build of the open ROM Omni5.1 for our Samsung GalaxyTab Plus.
Get the media patch for the 20150819 build in the 7.7 thread.
Detail can be found in 7.7 thread
Before you post, read the 7.7 thread first!
*** Post with no detail will be ignored ***
Know issues:
Now is in an early stage. Read carefully before flashing.
1. Wifi direct not fully working
2. May be more....
Downloads: :highfive:
AFH: https://www.androidfilehost.com/user/?w=settings-dev-files&flid=28293
d-h.st: http://d-h.st/users/danielhk/?fld_id=44273#files
mirror: 百度网盘
Use the latest Delta gapps: http://forum.xda-developers.com/showthread.php?t=2997368
** Latest TWRP (2.8.6.x or above) is required.
Omni is not rooted. To root, flash the latest SuperSU-24x.zip in recovery.
Credits: :good:
** The OmniROM team who have such a good idea and their hardworks
** All those who donate to me. Giving me the resources to upgrade my PC and accessories!
** All those who help our cool tab's developments!
Donations:
OMG.i'm such an idiot.roll out and i saw the twpr 2.8.6.0.I wasn' t see that before.flashing succes.Every thing work smoth and fast.
Main problem until now:
1.Brightness slide broke->soluion is download this app and disable "Automatic Brightness" https://play.google.com/store/apps/details?id=net.ailuro.android.settings.screen.brightness
2.Wifi passw clear LOL ~
3.Setting interface xxx
4.Unable to use Simcard
5.HW video notwork.BUT- you can try UC Browser for online video(Fb,youtube,...) like an option https://play.google.com/store/apps/details?id=com.UCMobile.intl .Not done yet,you need to restore the flash cache from 4.4 in titanium backup from the link below,other wise ,it don't work.
6.Can't upload file!
7.I don't see any problem left with reboot.app and system.I'm a BIG dump dump when forget to check update twpr ...what a shame (='.'=)
*.Root: http://download.chainfire.eu/supersu
Trung Gs said:
In TWPR ,after wipe,Omni(27mar2015) p6200 build and gapps5.1 is flashing succes.But,when i reboot system,the screen is black and my tab can't boot into homescreen.I try again with only rom,it still the same problem.It 's hard to say when i have try every way i know. what a shame ≧﹏≦. I hope u can't find out what problem with this build from other people too or the error come from my mistake.
Click to expand...
Click to collapse
Guess might be your tab............works for me. just perform a wipe, reboot the back into recovery and wipe once more.
Install rom, wipe and install rom again.
Reboot and see if it works for you. (can flash gapps later and super su if u need)
Can't access download link
Its weird! AFH says I dont have access to file, Dev-Host just direct me to their homepage, and mirror link is in chinese so I dont have any idea what buttons to hit. Is it just me? Anyone here who can guide me how to download the file?
omike123 said:
Its weird! AFH says I dont have access to file, Dev-Host just direct me to their homepage, and mirror link is in chinese so I dont have any idea what buttons to hit. Is it just me? Anyone here who can guide me how to download the file?
Click to expand...
Click to collapse
Edit 1:
Downloading now! Using google chrome I was able to translate mirror link page to English.
Edit 2:
Successfully flash the Rom via TWRP 2.8.6.0
As mentioned in the OP
- quicksettings pulldown can only be pulled once.
- adjusting brightness slider do nothing
- torch is working
- system apps seems to load faster than cm12.
One thing that caught up my attention is that simcard is not recognized. Have to goto settings/about tablet and found out that baseband version is unknown. Shame cause I really think this rom is more fluid compare to cm12.
I was unable to test user's app due to simcard unavailability, hence 3G as well, as I heavily dependent on it.
Also noticed that 1st & 2nd boot is ok but on 3rd boot is only showing blank screen ( omni bootlogo not showing ) have to longpress power button a couple of times until omni bootscreen appears.. P6200 user here.
Thanks again to this ROM, pretty much stable , no soft reboots. Battery is good, Minor issues i could see.
Video playback is still an issue i believe, even in YouTube.
Thanks again
If this rom could see the daylight I will really love it. It's much better than cm12 . Aside the baseband issue in p6200 really would have preferred this .
Sent from my GT-P6200 using xda Forums PRO
Have just installed latest version 20150518. Installation process without any problem. System is running stable.:good:
But SIM-card is not found. Tried several times.
It's no problem with CM12.1 rom. So I'm back to CM12.1.
uli-hh said:
Have just installed latest version 20150518. Installation process without any problem. System is running stable.:good:
But SIM-card is not found. Tried several times.
It's no problem with CM12.1 rom. So I'm back to CM12.1.
Click to expand...
Click to collapse
So unknown baseband issue has'nt been fix yet?
omike123 said:
So unknown baseband issue has'nt been fix yet?
Click to expand...
Click to collapse
That's what it shows in settings/about phone
uli-hh said:
That's what it shows in settings/about phone
Click to expand...
Click to collapse
Well I guess I'll just have to wait for the next release. I'm sure @daniel_hk would fix this in future updates.
omike123 said:
Well I guess I'll just have to wait for the next release. I'm sure @daniel_hk would fix this in future updates.
Click to expand...
Click to collapse
I don't have problem showing the baseband with or without a sim card. Don't know why some p6200 can't. It's the same modem chip and I'm using the same lib for both too.
Clean flash, Wait for a few minutes, etc.
Can anyone confirm that?
If really can't, in a terminal emulator type:
su (already rooted of course)
rild
see if any error message
here is the result:
WARNING: linker: libsec-ril.so has text relocations. This is wasting memory and prevents security hardening. Please fix.
rm: /data/misc/radio/dlink: permission denied
it is also showing invalid IMEI and unknown baseband version.
PugeAko said:
here is the result:
WARNING: linker: libsec-ril.so has text relocations. This is wasting memory and prevents security hardening. Please fix.
rm: /data/misc/radio/dlink: permission denied
it is also showing invalid IMEI and unknown baseband version.
Click to expand...
Click to collapse
The first one is just a warning because of the only old blob we have.
The second line means the daemon is not start. I'll look into it but I need someone with a p6200 to test for me.
daniel_hk said:
The first one is just a warning because of the only old blob we have.
The second line means the daemon is not start. I'll look into it but I need someone with a p6200 to test for me.
Click to expand...
Click to collapse
Willing to do that.
edwin270 said:
Willing to do that.
Click to expand...
Click to collapse
I think I found the reason. There is a file missing. View attachment libsecril-client.zip
unzip the above zip will get the file libsecril-client.so. Copy the file to /system/lib with a root browser (eg. ES FileExplorer) will do.
Hoping it work for t869 too. t869 owners are welcome to test too.
Good luck!
PS. Will include it in the next build
daniel_hk said:
I think I found the reason. There is a file missing. View attachment 3324813
unzip the above zip will get the file libsecril-client.so. Copy the file to /system/lib with a root browser (eg. ES FileExplorer) will do.
Hoping it work for t869 too. t869 owners are welcome to test too.
Good luck!
Click to expand...
Click to collapse
Was about to try that and alert you. Compared the lib folder for cm12.1 to that of omni and Realized the same missing libsecril-client.so and a couple of others. Looks like you got to it first. Anyway thinking of creating a flashable package for it. [emoji4] [emoji4] [emoji4]
OTG -Wifi???
@daniel_hk This may be stupid but i have to ask u.Does this kernel support USB Wifi with OTG?
Tried the lib files provided and a couple of others from cm12.1...................same old. Installed CM12.1 again and tried the rild check and got the same error as mentioned by PugeAko , though baseband is working with that rom.
Will be pulling the lib from stock MF1 rom for our dear p6200 soon, to see what comes of it.
Will post my findings soon.
Edit:
Checked radio directory in cm12.1 vrs OMni and some files are missing in Omni. Pulled that from cm12.1 but this constant black screen booting of Omni is making me frustrated at the moment. Too much black screen. Trying to see if I can get a boot.
Edit2:
Giving up. Don't know what it is but cannot endure this constant black screen any longer and time is not a luxury that I can afford now, its preventing me from helping figure out how to fix this baseband issue. Going back to the buggy cm12.1 rom. This rom is promising though.
Trung Gs said:
@daniel_hk This may be stupid but i have to ask u.Does this kernel support USB Wifi with OTG?
Click to expand...
Click to collapse
Each USB Wifi probably have different chips which requires drives supplied by the manufacture. For it to work, it requires HAL drivers/firmwares too. Normally there is a CD or place to download. Window might have some driver for a few chips. Linux (Android) would be another story.
Normally, a kernel would only have the drivers for the on board chips.
edwin270 said:
Tried the lib files provided and a couple of others from cm12.1...................same old. Installed CM12.1 again and tried the rild check and got the same error as mentioned by PugeAko , though baseband is working with that rom.
Will be pulling the lib from stock MF1 rom for our dear p6200 soon, to see what comes of it.
Will post my findings soon.
Edit:
Checked radio directory in cm12.1 vrs OMni and some files are missing in Omni. Pulled that from cm12.1 but this constant black screen booting of Omni is making me frustrated at the moment. Too much black screen. Trying to see if I can get a boot.
Edit2:
Giving up. Don't know what it is but cannot endure this constant black screen any longer and time is not a luxury that I can afford now, its preventing me from helping figure out how to fix this baseband issue. Going back to the buggy cm12.1 rom. This rom is promising though.
Click to expand...
Click to collapse
cm12.1 is probably the wrong place to try. Omin for p6800 would be the wiser choice.
Anyway, I will try to get it work on the next build.
DISCLAIMER: all operations descripted here should be done *only* by trained & expert guys... as every "hacking" operations, they involve the risk of soft/hard bricking your device making it unusable temporary or permanently. I will not be responsable in any way for it. So, pay attention and, if not sure, simply don't do it.
WARNING #1: this is a fast guide describing needed steps and providing needed files only for expert guys. It is *not*suitable* for newbies who need detailed instructions on how to install drivers, programs, flash partitions, etc...
WARNING #2: on this phone there are (strangely...) close ties between boot.img and recovery.img content. This involves that changing contents of recovery.img can produce bootloop and changing contents of boot.img can prevent to access recovery too, creating a soft brick condition. I don't know exactly why, BUT you are warned.
WARNING #3: the procedure and files provided are *only* for ROM1 firmware version 14 of 13 Aug 2016. It is indicated as OUKITEL_C4_V14.0_20160813 in "About phone" and as t637d-oq-s08-fdd3m-hd-64g8g-sd internally. If you are on a differently indicated version and/or release date, *don't*even*think* about trying to apply the provided files: bootloops and (at least) soft bricks are easy coming, expecially because of warning #2...
WARNING #4: all provided files are in .zip format only due to forum rules and limitations. They *all* need to be *unpacked* before use them.
CREDITS: this TWRP recovery has been compiled by Jemmini on 4PDA forum. Since of the Russian only language of that forum and the very hard way to subscribe on it for not Russians (needed to download files too...), I'm reporting it here with more explanations and my hints & experiences too...
Said that... Let's start! :highfive:
IF (and *only* if...) your firmware version is reported as OUKITEL_C4_V14.0_20160813 in your phone, these are the steps to follow:
- unlock your bootloader (no special code needed, just enable the apposite option slider in Developers section of Settings and unlock it by the standard fastboot command in fastload mode... you need adb, fastboot and adb/fastboot drivers installed in your pc obviously )
Please remember that, as ever, unlocking your bootloader will factory reset your phone (and void your warranty...), so take it in proper account....
- using SP Flash Tool (recent versions since of the new MT6737 used in C4... tested one is the v.5.1644, just Google for it) just flash the provided twrp-c4.img (by Jemmini on 4PDA) selecting "Download only" on top, using the provided scatter file and selecting only the recovery row (browsing to twrp-c4.img file). Then press Download button and connect your phone in OFF status. If all was OK and you have MTK drivers properly installed (Google for them... search for MT6737 drivers. To test them just try to connect your phone to PC as storage to check if it is properly seen...), you should see a green checking sign "v" on top of SP Flash tool.
If nothing happens, try to reinstall drivers and/or doublecheck your phone is in OFF status when connected.
- don't try to boot to system now. It simply doesn't anyway.
For some unknown reason connected to warning #2, flashing twrp introduces a bootloop (soft brick...) on this phone.
Nothing to be worried of anyway: systemless rooting will fix it!
To root simply flash by TWRP (yes, you need to enable /system modification on first twrp boot...) SuperSU v.2.78 "standard" version in zip format (just Google for it...).
For standard is intended the released one, not SRx or "forced to system" one... (tested version is SuperSU-v2.78-201609011115.zip) .
Just remember that, since of unability to boot system before flashing SuperSU, its zip have to be already on your device before flashing TWRP. Otherwise you can use a microSD card to flash from it...
If you do all fine you now have your rooted & TWRP 3.0.2-x provided Oukitel C4!!! :highfive:
If you are in a bootloop condition you aren't able to fix, just turn off your phone and, ever using SP Flash Tool in the same way, simply reflashing stock boot.img and recovery.img (both provided as zipped-to-to-be-unzipped attachment for... emergency reasons ).
After, if you want, you can install Xposed (in system mode) or busybox by app (it will be automatically installed in systemless mode since of supersu installation method...).
Don't even try to install Magisk v.9 instead: it will not work and will produce a soft brick (with no recovery access too...) that will requires a boot.img and recovery.img reflashing to be solved (with all this procedure to be redone one more time...).
This said... if you have questions... I'm here to answer them. Otherwise... have a nice time with your TWRP provided and systemless Rooted Oukitel C4!!! :fingers-crossed:
Reserved. :silly:
Can you please provide the 4PDA forum link of TWRP for this phone? Thanks for your post anyways
[email protected] said:
Can you please provide the 4PDA forum link of TWRP for this phone? Thanks for your post anyways
Click to expand...
Click to collapse
Added in OP. Don't expect to find more anyway...
I can confirm that this TWRP build also works fine with the newest OUKITEL_C4_V17.0_20161124 Firmware. Important: before flashing TWRP disable your boot lock code, otherwise you will softbrick your device.
Entec do you have an 4pda Account? If yes it would be really awesome if you could add the second TWRP recovery image for oukitel phones with the Rxx_xxxx ROM to OP.
EDIT:
I successfully installed XPOSED on my C4! This rocks the **** out of an 50 EUR budget phone!
Hello thank you for your information, could you provide us also TWRP for 32bits version (R06), I have tried to download from de forum but file is not avalaible.
regards
salvarez01 said:
Hello thank you for your information, could you provide us also TWRP for 32bits version (R06), I have tried to download from de forum but file is not avalaible.
regards
Click to expand...
Click to collapse
We need someone with 4PDA Account....
However, have you tried to install the 64Bit rom? You can get the Stock 64 Bit Rom from needrom.com. I advise you to do the software update before flashing TWRP linked in this thread.
[email protected] said:
We need someone with 4PDA Account....
However, have you tried to install the 64Bit rom? You can get the Stock 64 Bit Rom from needrom.com. I advise you to do the software update before flashing TWRP linked in this thread.
Click to expand...
Click to collapse
Hello thank you I have flashed 64 bits Rom and updated to V17, now all OK with TWRP and SuperSU.
Seam 64 bits version more slow than R06, but OK.
Thanks.
Hello I have tried to use native sip editing the files in /system/etc/permissions but the option is not available in phone menu. Someone know how to activate?
Enviado desde mi Redmi Note 4 mediante Tapatalk
[email protected] said:
Entec do you have an 4pda Account? If yes it would be really awesome if you could add the second TWRP recovery image for oukitel phones with the Rxx_xxxx ROM to OP.
Click to expand...
Click to collapse
[email protected] said:
We need someone with 4PDA Account....
However, have you tried to install the 64Bit rom? You can get the Stock 64 Bit Rom from needrom.com. I advise you to do the software update before flashing TWRP linked in this thread.
Click to expand...
Click to collapse
I managed to create an account on 4pda.ru and downloaded twrp for all firmware versions!
Files are attached!
Use twrp_recovery_C4_V.zip if your phone uses the OUKITEL_C4_VXX.X_XXXXXXXX firmware (Tested with OUKITEL_C4_V17.0_20161124)
Use twrp_recovery_R0x.zip if your phone uses the R0X_XXXXXX firmware. (Tested with R06_102033)
Where is OUKITEL_C4_V17.0_20161124 firm now?
I can't find it at needrom.com.
pop003 said:
Where is OUKITEL_C4_V17.0_20161124 firm now?
I can't find it at needrom.com.
Click to expand...
Click to collapse
Which rom do you have on your device?
Now I have R06_102033 on my C4
pop003 said:
Now I have R06_102033 on my C4
Click to expand...
Click to collapse
No problem, just use the twrp_recovery_R0x.zip from my previous post.
https://forum.xda-developers.com/showpost.php?p=71584701&postcount=10
[email protected] said:
No problem, just use the twrp_recovery_R0x.zip from my previous post.
https://forum.xda-developers.com/showpost.php?p=71584701&postcount=10
(do not forget to give it a like)
Click to expand...
Click to collapse
Thank you. twrp_recovery_R0x installed successfully.
However, in my environment, I needed the latest version of SP_Flash_Tool_v 5.1712_Win.
With other versions of sp_flash_tool, I did not succeed any number of times.
pop003 said:
Thank you. twrp_recovery_R0x installed successfully.
However, in my environment, I needed the latest version of SP_Flash_Tool_v 5.1712_Win.
With other versions of sp_flash_tool, I did not succeed any number of times.
Click to expand...
Click to collapse
Glad to hear it worked!
salvarez01 said:
Hello I have tried to use native sip editing the files in /system/etc/permissions but the option is not available in phone menu. Someone know how to activate?
Enviado desde mi Redmi Note 4 mediante Tapatalk
Click to expand...
Click to collapse
You can configure SIP by using an App called Activity Launcher.
Download and Install Activity Launcher
Start Activity Launcher
Choose 'All Activities'
Search for 'Phone'
Open 'Phone'
Search and Click 'Sip Settings', 'com.android.phone.services.telephony.sip.SipSettings'
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello, yes I know this app to find secret menu. With this you can configure sip settings but when you try to make a call the dialer not offer choice to select calls with sip account
Enviado desde mi Redmi Note 4 mediante Tapatalk
salvarez01 said:
Hello, yes I know this app to find secret menu. With this you can configure sip settings but when you try to make a call the dialer not offer choice to select calls with sip account
Enviado desde mi Redmi Note 4 mediante Tapatalk
Click to expand...
Click to collapse
After you added an Sip account you can choose you default dailing method as follows: Dailer -> Settings -> Accounts -> Dail With
You also see your SIP account as "additional SIM Card" when Opening the dailer!
Thank you!
Stock firmware
Rogers B05 Firmware
https://www.androidfilehost.com/?fid=1395089523397891291
Separate Firehose download
https://www.androidfilehost.com/?fid=1395089523397891292
ZTE Kernel source mirror (We are codenamed Helen)
https://www.androidfilehost.com/?fid=1395089523397891289
Here is a step by step guide on how to flash the stock rom with QFIL and by extension any image.
Download and install the Qualcomm drivers from here
Download the firmware from above
Extract the firmware to a folder that you can easily access them from like your desktop
Download and install QPST from here
Open the QFIL application (Find it in your start menu)
In the "Select Build Type" field select Flat Build
In the "Select Programmer" field navigate to the folder you extracted the firmware and support files to and select the prog_emmc_firehose_8909.mbn file
Select the "Load XML" button and navigate to the folder you extracted the firmware and support files to and select the rawprogram0.xml and then the patch0.xml when prompted.
Plug in your tablet
Run the following adb command "adb reboot edl" (Now the screen should be blank but the led light should be red)
If the text at the top of the QFIL application says "No Port Available" click the "Select Port..." option and pick your device. If your device isn't showing up there you didn't install the drivers properly.
Click the Download Button to begin flashing your device
So the above explains how to flash everything if you want to flash just boot or recovery use the tool in the 2nd post it is a lot easier
Warning
This is a dangerous tool. It can render your device permanently unusable. If you use it, your warranty will likely be void. You accept all responsibility for the consequences.
Acknowledgments
Special thanks to @tdm for taking the firehose I got and creating the k81tool with it!
Note Well
The first rule of intelligent tinkering is to save all the parts.
Always backup your partitions before writing new contents, so that you can get back to where you started.
Never write both boot and recovery in one session. Always make sure that you can boot into the other partition in case something fails.
Preparation
Download magisks patched boot.img from here.
Download k81tool from here.
Setup your computer.
Setup for Windows
Download zadig.
Boot your device in EDL mode (see below).
Windows will want to install the Qualcomm USB driver. We won't be using it so cancel.
Run zadig. Find device 05c6:9008 and install the WinUSB driver for it.
Reboot your device and rerun steps to go back to EDL mode
Booting in EDL mode
Code:
adb reboot edl
Usage
Code:
k81tool.exe <read|write> <boot|recovery> <filename>
Example:
Code:
k81tool.exe read boot stock-boot.img
Code:
k81tool.exe write boot patched_boot.img
Multiple Operations
This is a "one-shot" tool. After performing an operation, it will reset the device with a 5 second countdown. If you wish to perform multiple operations (eg. backup, flash), simply re-enter EDL mode.
Common Problems
Device was not found
First enter EDL mode, then run the tool.
Device is visible in device manager but cannot be found by the tool.
Connect directly to the PC, not through a hub.
Windows says bad file descriptor
The WinUSB driver is not installed.
Once you flash the patched_boot.img all you need to do is install the magisks manager and you will have root enjoy!
Proof of root:
{
"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"
}
Place Holder for TWRP
bad links??
Hi
First, thank-you, thank-you, thank-you x 100. I've been looking for a method to root this device from the day I got it as an add on to my cell plan. Not sure if I am missing something but when I click on the androidfilehost links I get taken to a home page but there is no file to download for all three links. Initially I thought I might have to register so I did that but the links still just take you to the Home advert page Could you update the links when you get a chance - thanks !!
edit - I have a couple of questions -As you have been the first to root the device there are obviously no custom firmware builds available so we stick with stock, correct? We will be able to remove the bloatware on stock because it's rooted though, correct? I also use tasker and the AutoApps suite for automation and I need root for some of my tasks so this is a huge step in the right direction. Lastly in order to root the device do we need to do follow all steps in the first post and then complete the steps in the second post? Or is the second post just a different way to do what was done in post 1? I'm excited to root this so thanks for fixing those links! Thanks again for all your work.
ryanoc75 said:
Hi
First, thank-you, thank-you, thank-you x 100. I've been looking for a method to root this device from the day I got it as an add on to my cell plan. Not sure if I am missing something but when I click on the androidfilehost links I get taken to a home page but there is no file to download for all three links. Initially I thought I might have to register so I did that but the links still just take you to the Home advert page Could you update the links when you get a chance - thanks !!
Click to expand...
Click to collapse
Sorry about that somehow the links broke, I have updated them so now they are proper.
Hey guys. Having a little trouble. I keep on running into "Failed: unknown error" when I try to flash the patched boot.img that was provided. I managed to read the stock boot image with no problems, but writing just runs into this error.
Thoughts?
I am using the Bell variant so I hope that isn't the source of it
Post Root questions
Hi
I'm about to try to root the device, assuming it goes according to plan, can we then install SuperSU? Do we need a TWRP for the device if we want to install another ROM and are there generic ROMS out there that would work on this tablet? Sorry if these are noob questions, I've been an apple jailbreaker for years and just bought and rooted and installed a custom ROM on a Samsung Galaxy S4. I installed a new android tablet NAV in my BMW and I needed a device to act as a hotspot, so I use Tasker and AutoApps with it to automate the process and it works really well. When I rooted the Galaxy S4 there are a ton of ROMS available for every variant so it was easy to follow the instructions. However, this is totally new territory for me. This device isn't nearly as popular so I wondered what options are available to us once we have it rooted?
same issue failed unknown error
Hi
I am using the Rogers K81 and I am encountering the same failed unknown error when I try to write the patched boot file. I also was able to read the firmware file without issue. I rebooted into edl mode and then tried to write the patched file -
NB - for those who have yet to try, move the k81tool.exe and the patched boot file to your c drive and make sure your at the root of c and then remove the B05 in the patch file name so that it can find the file if you are just cutting and pasting the command line instructions above, otherwise you'll get an error that it can't find the file. If the k81tool.exe isn't in the current directory you are in you will get an error saying k81tool.exe is not a known command ..etc.etc. This might seem obvious to some but for those with little command line experience, it will save you from having to post questions about your errors.
There is a product ZTE primetime K92 which is a successor of a ZTE K81.
Do you plan to support root for ZTE Primetime K92?
huaji2333 said:
There is a product ZTE primetime K92 which is a successor of a ZTE K81.
Do you plan to support root for ZTE Primetime K92?
Click to expand...
Click to collapse
A friend of mine has the k92, and currently it has a locked bootloader even with the firehose and all. So he is working to find an exploit to allow it to be unlocked. But no ETA at this time.
Sent from my iPhone using Tapatalk
Thank you for providing this. I have the Virgin Mobile device currently. Just a question before I try this. My past experience with a tablet from Rogers a few years ago was that whenever you put a different sim card in, it would force you to reset the entire device. To get around this, I was lucky that there were other generic firmware available for that device. Does the Rogers firmware that you provide force a reset if you change the sim? I'd ideally like to have the option to change sims when traveling. Thanks.
I own a Virgin Mobile Canada ZTE K81 tablet. As much as I like a rooted device, my goal, if possible, is to replace the Bell firmware with the Rogers firmware. The reason I would want to do this is because Bell has done some nasty things with this tablet. The SIM card is IMEI locked to this tablet, I cannot use the SIM card on anything else. So I decided this tablet could be used as a wifi hotspot. Unfortunately, Bell did something to the firmware to make wifi and bluetooth tethering impossible.
I guess the other question I have is will the IMEI lock still work on this Bell tablet after the Rogers firmware is installed?
wow i didn't think development for this device would've gotten this far already. we're gonna need our own device forum soon
---------- Post added at 12:20 PM ---------- Previous post was at 12:19 PM ----------
bridonca said:
I own a Virgin Mobile Canada ZTE K81 tablet. As much as I like a rooted device, my goal, if possible, is to replace the Bell firmware with the Rogers firmware. The reason I would want to do this is because Bell has done some nasty things with this tablet. The SIM card is IMEI locked to this tablet, I cannot use the SIM card on anything else. So I decided this tablet could be used as a wifi hotspot. Unfortunately, Bell did something to the firmware to make wifi and bluetooth tethering impossible.
I guess the other question I have is will the IMEI lock still work on this Bell tablet after the Rogers firmware is installed?
Click to expand...
Click to collapse
imei locks are independent of the device itself. you need to get the carrier to give you an unlock code
Online Gravy said:
wow i didn't think development for this device would've gotten this far already. we're gonna need our own device forum soon
---------- Post added at 12:20 PM ---------- Previous post was at 12:19 PM ----------
imei locks are independent of the device itself. you need to get the carrier to give you an unlock code
Click to expand...
Click to collapse
I got Bell to IMEI lock the SIM to another, better tablet, a LG G Pad IV 8.0 FHD (LGV533) from Fido. The SIM works perfectly, I can now wifi tether!
That makes it an easier choice to hack at the Bell K81, now that the IMEI lock is not tied to this K81 tablet anymore. If the Bell K81 works with the Rogers firmware, bonus. If it bricks, not the end of the world. My data plan will still work. I just need to find the time to do the hack!
bridonca said:
I got Bell to IMEI lock the SIM to another, better tablet, a LG G Pad IV 8.0 FHD (LGV533) from Fido. The SIM works perfectly, I can now wifi tether!
That makes it an easier choice to hack at the Bell K81, now that the IMEI lock is not tied to this K81 tablet anymore. If the Bell K81 works with the Rogers firmware, bonus. If it bricks, not the end of the world. My data plan will still work. I just need to find the time to do the hack!
Click to expand...
Click to collapse
I have flashed my Bell k81 with Rogers firmware and it works properly.
Sent from my iPhone using Tapatalk
any chance of getting Pie GO installed on this thing, mine lags to even tap and the stock settings leave only 400mb free of ram
I can't successfully flash the rogers firmware on the VM (Bell) device. When the flashing process gets to 'reading through the sparse file' for the userdata.img file, I get an error. The log reads:
{ERROR: sparse_open:1939 Didn't properly read the sparse_header!
If I delete this file as a test (not sure if that was a good idea), it continues on to reading the ddr.img file, but halts again and the error refers to this file being 0 bytes.
I may have missed a step. When is the kernel file used? Is the Rogers firmware file complete?
s_021 said:
I can't successfully flash the rogers firmware on the VM (Bell) device. When the flashing process gets to 'reading through the sparse file' for the userdata.img file, I get an error. The log reads:
{ERROR: sparse_open:1939 Didn't properly read the sparse_header!
If I delete this file as a test (not sure if that was a good idea), it continues on to reading the ddr.img file, but halts again and the error refers to this file being 0 bytes.
I may have missed a step. When is the kernel file used? Is the Rogers firmware file complete?
Click to expand...
Click to collapse
Delete DDR as well and any of the ones it complains about that are empty. When I have sometime I'll upload a new package with those removed.
Decided to try the k81tool to just root instead, but I'm getting the same Failed:unknown error as others have posted.
(Using VM stock firmware)
---------- Post added at 11:20 PM ---------- Previous post was at 11:14 PM ----------
If you put in a Rogers sim, does it attempt to do a hard reset or just the usual reboot?
thanks
deadman96385 said:
I have flashed my Bell k81 with Rogers firmware and it works properly.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
deadman96385 said:
Delete DDR as well and any of the ones it complains about that are empty. When I have sometime I'll upload a new package with those removed.
Click to expand...
Click to collapse
Deleting the files also fails. The error is {ERROR: handleProgram:8615 'ddr.img' not found. You could possibly try --notfiles=ddr.img,OtherFileToSkip.bin (note, exiting since you specified --noprompt)
Adding back ddr.img, the error is
{ERROR: handleProgram:8666 Filesize is 0 bytes. This is usually a mistake!! Please check 'C:\ZTE\rogers\ddr.img'
EDIT: FIXED. I flashed persist.img from version "S250260_210804..." (unzip, flash via `fastboot flash persist persist.img`) https://mirrors.lolinet.com/firmware/lenovo/Tab_P11_Pro/TB-J706F/
Hello dear community,
I am in need of some help. So here is what I did:
* Coming from latest Android 11 ROW, flashed ZUI using QFIL from here: https://mirrors.lolinet.com/firmware/lenovo/Tab_P11_Pro/TB-J706F/
* tried upgrading to ZUI 12.5, 12.6 and 13 but didn't work
* used fastboot to unlock and unlock_critical (i know, i know...)
* used payload_dumper (from some github repo) to extract zui 13 update.zip
* flashed every image I extracted manually using fastboot (I know, I'm stupid)
* Got ZUI 12.0 working, didn't like it and wanted ROW android 11 back
* flashed latest ROW rom using QFIL from lolinet url -> bootloop
* flashed oldest ROW rom using QFIL, updated 3x via OTA to latest version -> few bootloops, then device booted back to android 10 and created notification "failed to install ota"
So I can install any version between TB-J706F_S210002_201015_ROW and TB-J706F_S250260_210804_ROW from lolinet url, but nothing above that. Neither through QFIL, nor using lenovo smart rescue assistent, nor using OTA update from android 10 (which is working fine).
I tried following things to fix this:
* ####6030# -> change to CN and change the NV value to 00
* ####6030# -> change to DE and change the NV value to 02 or 00
* flash latest ROW using QFIL, then change NV value from 02 to 00
nothing of that worked and I'm starting to believe, that I ****ed up some partitions using fastboot. Because I flashed images from ZUI android 11 and I can't install ROW android 11 now.
Could I possibly try restoring a TWRP backup from some other user?
What else could I do to install android 11?
PS: I used QFIL backup and restore tool to change the NV value. Because the nv reader/writer tool didn't seem to work.
It might help, if someone would be kind enough to provide me with the following images (by backing them up with twrp):
* abl
* xbl_a
* xbl_b
Hi there, I also got into this trouble that can't flash any global ROM including TB-J706F_S250260_210804_ROW. What I did is change the NV value to 02 and not 00 using QFIL. After that I was able to update via OTA and currently on the latest global ROM.
Thanks to this thread: https://forum.xda-developers.com/t/check-region-unlock-p11-tb-j606f-l-n.4356451/
MateUserHHTTI have similar problem before, can not flash to Android 11, even ROW or ZUI, bootloop~
please check your J706F screen auto rotate and auto brightness(and pair bluetooth devices) still functional?
If not functional, I'm following below post instruction to flash presist.img, and can upgrade to Android 11, both of ROW & ZUI are available.
<TB-J706F> Auto-rotation & Auto Brightness Broken.But Serial Number shows 123456789ABCDEF, wifi /bluetooth MAC shows 00:00:00... still not solve even functional.
auston said:
But Serial Number shows 123456789ABCDEF, wifi /bluetooth MAC shows 00:00:00... still not solve even functional.
Click to expand...
Click to collapse
I may found a fix for Bluetooth MAC by generating a file for the "NV-items_reader_writer.exe" and wrote it to NV item 447 (some one sait this is BT). Problem was that this item (447) was NOT present at this time inn QCN.
WARNING! May my guess of "Items size" 128 is wrong, I don't know. Use at your own risk and change the file to your MAC.
After that I flashed "persist.img" (matching the actual ROM), some one wrote that this fixed the autorotate. I can confirm this.
But still not found solution for serial, the correct serial is still in NV item 2497.
Okay, Serial number restore can be done the same way.
See here https://forum.xda-developers.com/t/tab-j706f-serial-number.4318901/
Best would be to have the full original QCN file (or an editor for this files)
MateUserHHTT said:
* abl
* xbl_a
* xbl_b
Click to expand...
Click to collapse
abl (_a and _b) = abl.elf
xbl (_a and _b) = xbl.elf
You will find both in the ROM Zip's at lolinet.
Mine updates successfully from 10 to 11 after I have restored BT, Wifi, SN, PN and region lock. And flashed persist.img.
Oh, and you have to set region code in QCN NV 6858, somebody found out that Android 11 checks that value. If it is wrong, device boot loops.
auston said:
please check your J706F screen auto rotate and auto brightness(and pair bluetooth devices) still functional?
Click to expand...
Click to collapse
Firstly, let me thank you for your reply! It's interesting, I indeed noticed just a few days ago, that auto rotation isn't working!
I will follow the guide you linked and update my post accordingly.
Edit: THANK you very much indeed! My problem was solved instantly by this!
Flashed persist.img via fastboot, flashed the latest ROM from lolinet using QFIL and had no issues whatsoever.
Oh, and you have to set region code in QCN NV 6858, somebody found out that Android 11 checks that value. If it is wrong, device boot loops.
Click to expand...
Click to collapse
as I said in my post, I did tried both 00 and 02. I read the thread about the second region code checking.
CryptMan said:
Mine updates successfully from 10 to 11 after I have restored BT, Wifi, SN, PN and region lock. And flashed persist.img.
Click to expand...
Click to collapse
I don't have any problem but just in case...
I guess PN is Product Number where did you change it and where do you get the correct value? I only found a code before the SN that looks unique per tablet but it's not in the box.
MrCrayon said:
I guess PN is Product Number where did you change it and where do you get the correct value?
Click to expand...
Click to collapse
Well I changed the PN in NV item 2497
I found this PN number here: https://forum.xda-developers.com/t/tab-j706f-serial-number.4318901/#post-86315607
My other device, P11 (TB-J606F), has this number: 8SSP69A6PB5XHA6213L0864
Because they look pretty same (length, etc.) I decided to try it.
May somebody would confirm if this PN are the same on all device.
Open settings and type in the search bar "####2222#". That will display PN and SN.
One issue persists though, which is that my widewine level is set to L3.
1. I flashed persist.img from TB-J706F_S250260_210804_ROW
2. I then installed the TB-J706F_S620150_211226_ROW via QFIL and
3. updated to TB-J706F_S630185_220128_ROW via OTA in system settings.
My serial number is also 1-9A-F. My device is locked. I'm unlocking my device and flashing the persist.img of the latest ROM. If that doesn't work, what are my options to restore L1?
CryptMan said:
Well I changed the PN in NV item 2497
I found this PN number here: https://forum.xda-developers.com/t/tab-j706f-serial-number.4318901/#post-86315607
My other device, P11 (TB-J606F), has this number: 8SSP69A6PB5XHA6213L0864
Because they look pretty same (length, etc.) I decided to try it.
May somebody would confirm if this PN are the same on all device.
Open settings and type in the search bar "####2222#". That will display PN and SN.
Click to expand...
Click to collapse
Ah ok, so the number before SN is the PN.
I have two J706F and they have different PN, The last 8-9 digits are different and the other ones are the same.
I could not find that code anywhere else.
MateUserHHTT said:
One issue persists though, which is that my widewine level is set to L3.
Click to expand...
Click to collapse
If you check in play store settings does it say your device is certified?
On my J706F, the one on which I have lost QCN with SN MAC etc. , I have the same problem as MateUserHHTT.
The device lost L1 cert. PlayStore says NOT certified and "DRM Info" app says L3.
I also have a property "sys.lenovo.widevine_security_level" with value "L3".
My guess it that there is a file or partition holding this certifications, but I don' t know which.
And of course I don't have a backup ...
If you check in play store settings does it say your device is certified?
Click to expand...
Click to collapse
It says "Device is not certified"
Now that's curious: my tablet, running the latest Android 11 ROW version, is offering me to upgrade my device to Android Kitkat 4.4. Now that's an offer I can't resist (yes, of course I clicked "update". I want all the new features!)
{
"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"
}
CryptMan said:
The device lost L1 cert. PlayStore says NOT certified and "DRM Info" app says L3.
I also have a property "sys.lenovo.widevine_security_level" with value "L3".
Click to expand...
Click to collapse
Is your bootloader unlocked or did you unlock it previously and relocked?
MateUserHHTT said:
It says "Device is not certified"
Now that's curious: my tablet, running the latest Android 11 ROW version, is offering me to upgrade my device to Android Kitkat 4.4. Now that's an offer I can't resist (yes, of course I clicked "update". I want all the new features!)
Click to expand...
Click to collapse
Maybe the OTA app is getting some wrong data / not set data and that's the result
I tried to decompile that app to get the address called to download updates but my knowledge of android programming is really basic and did not have enough time.
MrCrayon said:
Is your bootloader unlocked or did you unlock it previously and relocked?
Maybe the OTA app is getting some wrong data / not set data and that's the result
I tried to decompile that app to get the address called to download updates but my knowledge of android programming is really basic and did not have enough time.
Click to expand...
Click to collapse
I previousl, unlocked and afterwards relocked it (both flashing lock and flashing lock_critical)
Yes, I once said "erase all before download" and accidentally deleted my original qcn file so some NV fields seem to be missing. Maybe that caused the app to default back to 4.4 it was Lenovo Feature Updater by the way, not the settings - system - update.
If you share your past work in a git repo I will take a look at it. I'm no expert for sure but I'm developing fir android for some years and have stuck my nose a tiny bit under the surface of android rom development (1mm and it was very painful still).
My widewine lvl is L3. Any chance of resetting to L1 myself? I don't know much about how trust attestation works. :/
MateUserHHTT said:
It was Lenovo Feature Updater by the way, not the settings - system - update.
Click to expand...
Click to collapse
I disabled that as soon as I saw it
MateUserHHTT said:
If you share your past work in a git repo I will take a look at it. I'm no expert for sure but I'm developing fir android for some years and have stuck my nose a tiny bit under the surface of android rom development (1mm and it was very painful still).
Click to expand...
Click to collapse
Not much really, I'm not at my desk now but I extracted LenovoOTA from stock ROM and decompiled it with apktools, but even with online tools is probably ok.
Then I see two options:
Recompile that package changing package name and adding a log with full address and parameters or get the code that construct the URL and put it in a new app.
For you probably the last one is easier.
I went for a third I was trying to understand if i could get the data with adb or in files but I did not find documentation.
MateUserHHTT said:
My widewine lvl is L3. Any chance of resetting to L1 myself? I don't know much about how trust attestation works. :/
Click to expand...
Click to collapse
I don't think there is a way to force it, this widevine a thing is a pain.
MrCrayon said:
Is your bootloader unlocked or did you unlock it previously and relocked?
Click to expand...
Click to collapse
Locked, and was never unlocked before.
I tried to unlock now, but does not succeed with flashing sn.img.
Because I'm not interested on Custum ROM, I will leave it locked.
Do you know where the device certification is stored?
I unlocked without flashing sn.img. Does that make a difference?
Did you try monitoring the network traffic with wireshark?