Database Info

[RECOVERY][UNOFFICIAL] TWRP for the Samsung Galaxy S5

Ok folks, thanks to some leakage, some awesome users/testers, Chainfire and his root magic, and me with so of mine, you all have a fully functioning TWRP Recovery.
Official TWRP
Confirmed working on:
G900F
G900T
G900W8
G900I
G900P
G900M
Confirmed not working on:
G900H - exynos - Its recovery can found here
G900V - locked bootloader (thanks Verizon!!!)
G900A - locked bootloader (thanks AT&T!!)
Note: No one but yourself is responsible for what you do to your device.
People to Thank
TeamWin - for their awesome recovery.
TeamWin - for their hlte device repo I ported to the klte (kltexxx in this case)
ricky310711 - for providing dumps and testing
leoaudio13 - for providing access to device and testing
utkanos - for his original work on hlte (which all this is based off of)
Known Issues
Write permissions to internal storage.
How to install via adb shell
Have USB drivers installed
Connect phone to PC
Open terminal or cmd
Code:
adb push recovery.img /data/local/tmp/recovery.img
Code:
adb shell su -c dd if=/data/local/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
How to install with Odin
(USB) Disconnect your phone from your computer
Start Odin3-vX.X.exe
Click the PDA button, and select twrp-klte.tar
Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
(USB) Connect the phone to your computer
Make sure Repartition is NOT checked
Click the Start button
Wait for Android to boot
Done (if it took you more than 30 seconds, you goofed)
NOTE: Sometimes the device does *not* boot into recovery mode. Just do the entire procedure again if this happens. If it still will not install, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
The Goods
twrp-klte.tar - flash with ODIN.
recovery-twrp-klte.img - for manual flashing.
Official TWRP can be found here.
XDA:DevDB Information
TWRP for the Samsung Galaxy S5, Tool/Utility for the Samsung Galaxy S 5
Contributors
PlayfulGod, leoaudio13, utkanos, biggbiff
Version Information
Status: Stable
Stable Release Date: 2014-04-22
Created 2014-03-28
Last Updated 2014-06-08

Test imgs!!!!!!
Reserved

Yep the write permission is painful PG! but i accept to live with it for now )

Does this work on a SM-G900H?

0mega007 said:
Does this work on a SM-G900H?
Click to expand...
Click to collapse
Dunno until someone tries it.

PlayfulGod said:
Dunno until someone tries it.
Click to expand...
Click to collapse
PG, for some reason while flashing the CWM swipe, it fked up the platform.xml in /syste/etc/ . That caused Titanium Backup to stop function properly while doing a backup to external SD. Is it the recovery or its a problem with Kitkat ? I got the same problem with Note 3 ( Exynos and SnapDragon too ). The only way to fix was to do like this picture below :
{
"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"
}
( Source : http://forum.xda-developers.com/showthread.php?t=2537793 )

leoaudio13 said:
PG, for some reason while flashing the CWM swipe, it fked up the platform.xml in /syste/etc/ . That caused Titanium Backup to stop function properly while doing a backup to external SD. Is it the recovery or its a problem with Kitkat ? I got the same problem with Note 3 ( Exynos and SnapDragon too ). The only way to fix was to do like this picture below :
( Source : http://forum.xda-developers.com/showthread.php?t=2537793 )
Click to expand...
Click to collapse
umm I dont see that file in the system dump nor in cwm. So my guess is its a tibu issue.
not to mention, those look like app manifest permissions. And the Write permission overrides the read permission.

PlayfulGod said:
umm I dont see that file in the system dump nor in cwm. So my guess is its a tibu issue.
not to mention, those look like app manifest permissions.
Click to expand...
Click to collapse
Yup maybe. On the Nexus 5 Kitkat, TB made restored apps force closed. But TB team fixed it. But as far as i remember, When i was testing your recovery ( pretty sure it was cwm swipe) after 2 or 3 flashes, problem arose. Ricky and me thought it was an SD card issue ( wrong permission, full sd card or something like that ) but it turned out the problem was the platform.xml . Not so sure as if TB made any change to platform.xml or not.

leoaudio13 said:
PG, for some reason while flashing the CWM swipe, it fked up the platform.xml in /syste/etc/ . That caused Titanium Backup to stop function properly while doing a backup to external SD. Is it the recovery or its a problem with Kitkat ? I got the same problem with Note 3 ( Exynos and SnapDragon too ). The only way to fix was to do like this picture below :
( Source : http://forum.xda-developers.com/showthread.php?t=2537793 )
Click to expand...
Click to collapse
this was on a SM-G900H?
Did the recovery worked?
I just want it to completely wipe the phone before install new roms. so this bug doesnt matter to me if it worked

0mega007 said:
this was on a SM-G900H?
Did the recovery worked?
I just want it to completely wipe the phone before install new roms. so this bug doesnt matter to me if it worked
Click to expand...
Click to collapse
No its a F model. BTW, there is no Rom right now to install. ^^

according to a PM I just got, this doesnt work on G900H. By the description I was giving I think its the kernel and/or dtb. So I asked for a dump of the G900H stock recovery so I can extract the kernel & dtb from it.

PlayfulGod said:
according to a PM I just got, this doesnt work on G900H. By the description I was giving I think its the kernel and/or dtb. So I asked for a dump of the G900H stock recovery so I can extract the kernel & dtb from it.
Click to expand...
Click to collapse
Ok, thanks i hope you release H model recovery soon too

0mega007 said:
Ok, thanks i hope you release H model recovery soon too
Click to expand...
Click to collapse
Do you have one? According to PM CF-Root not working for H either. I told him to contact Chainfire and see what he needed to get that working for it.

PlayfulGod said:
Do you have one? According to PM CF-Root not working for H either. I told him to contact Chainfire and see what he needed to get that working for it.
Click to expand...
Click to collapse
Not yet, in about 2 weeks, but i wont order it until there is a root method available, and if it is from chainfire better

PlayfulGod said:
Do you have one? According to PM CF-Root not working for H either. I told him to contact Chainfire and see what he needed to get that working for it.
Click to expand...
Click to collapse
Different chip maybe ? Pretty sure the one that test the H will be messed up cos there is no stock recovery atm

leoaudio13 said:
Different chip maybe ? Pretty sure the one that test the H will be messed up cos there is no stock recovery atm
Click to expand...
Click to collapse
From what I been told/seen its exynos. :\

PlayfulGod said:
From what I been told/seen its exynos. :\
Click to expand...
Click to collapse
I know its Exynos , but i guess the recovery will be different as well. Thats why i didnt dare to flash the root tool also gotta haave to wait. We can't dump recovery if there is no root ....

leoaudio13 said:
I know its Exynos , but i guess the recovery will be different as well. Thats why i didnt dare to flash the root tool also gotta haave to wait. We can't dump recovery if there is no root ....
Click to expand...
Click to collapse
yea it will be different. Ricky has a plan to try for root. And I'm just waiting for a recovery/boot dump lol

PlayfulGod said:
yea it will be different. Ricky has a plan to try for root. And I'm just waiting for a recovery/boot dump lol
Click to expand...
Click to collapse
Let see how it goes 2mo. I might ask for the H again hehe!:good:

Hi mate,
many thanks for the S5(G900F) TWRP recovery,
i have a question about the backup to extSD, it do not work
Error code:
E: Unable to create folder: /external_sd/TWRP/BACKUPS (error13)
E: Faild to make a backup folder
I have set this folder manuelly but the error comes again
Backup to internal SD works ok (big file with 3,4GB without set all Apps)
thanks in advance

[GUIDE][TWRP][ROOT] Oukitel C4 TWRP (by Jemmini) & (systemless) Root

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!

[TOOL] [TISSOT] Persist Resurrector (v1.0.0.0)

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.

[Guide] Fix and Re-Locking Bootloader From Fake UBL

ULTIMATE GUIDE TO FIX ROM FROM FAKE UNLOCK BOOTLOADER​
Device: Redmi Note 5/Pro (Whyred)
Anti: 3 (required)
Initial Rom: Global/China with ARB v3
Method: Test Point
As we know that buying whyred from a distributor with a red box has a strange rom and also mi account that can't be binded. this is very troublesome when we want to unlock the bootloader..
This method is to really lock the Bootloader again, can bind Mi account and can be used for Unlock bootloader officially.
And finally, this method doesn't need to edit the script anymore, I upload patch scripts and loaders specifically for ROM 9.5.17 below.
It has been tested and the results are successful.
Let's start and DWYOR!
Step:
1. Download ROM 1 and ROM 2 below then extract.
2. Download the Patch then copy and replace it in ROM 1 which has been extracted (in the images folder).
3. Open back cover of the phone carefully and connect to the PC via Test Point (HS-USB QDLoader 9008)
4. Flash ROM 1 that has been patched with MiFlash (I use MiFlash 2017.4.25.0 and PC 64bit during flashing).
5. After success, close the miflash, unplug the cable, and turn it on. Wait a few moments until stuck in recovery mode (pict 1)
6. Connect Whyred to PC again via Test Point and Flash ROM 2 with MiFlash.
7. Wait for the first boot, after entering the system, check unlock status in developer mode and tadaaaa.. it's completely locked now... (pict 2)
8. Bind Mi account, continued unlock bootloader officially.
9. Done! ready to go to custom ROM
Note:
1. Patch is only used for ROM 1 (Global 9.5.17).
2. ROM 2 can use all China ROMs as long as still ARB v3.
Picture:
Pict 1
{
"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"
}
Pict 2
War Equipment:
ROM 1. (Global 9.5.17): LINK
ROM 2. (China 9.5.21): LINK
Patch: LINK
Just Hit THANKS Button for Supporting me..

Any chance this guide can be updated for ARB4? At least the patch file?
Edit:
Nevermind, I see it cannot be done.

poncespr said:
Any chance this guide can be updated for ARB4? At least the patch file?
Edit:
Nevermind, I see it cannot be done.
Click to expand...
Click to collapse
The same mistake is also available

poncespr said:
Any chance this guide can be updated for ARB4? At least the patch file?
Edit:
Nevermind, I see it cannot be done.
Click to expand...
Click to collapse
UtkuAblak said:
The same mistake is also available
Click to expand...
Click to collapse
sorry bro, currently only available for arb 3. refers to the difficulty of flashing if it has arb 4. coz the test point method in arb 4 must use an authorized account.
there is a guide to bypass this authorized account, but there are some reports that still fail.
this weirdness has been made xiaomi itself..

octodellin said:
sorry bro, currently only available for arb 3. refers to the difficulty of flashing if it has arb 4. coz the test point method in arb 4 must use an authorized account.
there is a guide to bypass this authorized account, but there are some reports that still fail.
this weirdness has been made xiaomi itself..
Click to expand...
Click to collapse
Stupid me that updated my RMN5Pro before reading these guides. Still is a great phone. Just wanted a taste of pie.

Mi phone deat
Sir, my nead mi authorized account please help me this my id 1813003637
---------- Post added at 05:50 PM ---------- Previous post was at 05:39 PM ----------
Sir my need mi authorized account please help me
This is my id 1813003637 sorry for my bad english

I have ARB3 device with fake ubl. I want to try this method, but I can not fully understand what we do with battery while short circuit the test points(5th step).
After writing 1st ROM, we connect the battery, then open device and stuck with recovery. After this (6th step), will I disconnect the battery again, while test point?

And another question;
while writing 1st or 2nd ROM which option we select with MiFlash Tool? "Clean_all" or "Clean_all and Lock" ?

How can I check for Fake UBL to be sure for 100% that I need this ?

netlogger said:
I have ARB3 device with fake ubl. I want to try this method, but I can not fully understand what we do with battery while short circuit the test points(5th step).
After writing 1st ROM, we connect the battery, then open device and stuck with recovery. After this (6th step), will I disconnect the battery again, while test point?
Click to expand...
Click to collapse
yes, like the first..
netlogger said:
And another question;
while writing 1st or 2nd ROM which option we select with MiFlash Tool? "Clean_all" or "Clean_all and Lock" ?
Click to expand...
Click to collapse
both can be used, coz basically our whyred is in locked bootloader.
but for sure, you can choose Clean_all and Lock
The4anoni said:
How can I check for Fake UBL to be sure for 100% that I need this ?
Click to expand...
Click to collapse
go to fastboot mode and run fastboot command:
Code:
fastboot getvar anti
if the displayed output is 3, is good. that means you can use this method.
if the displayed output is 4, you can not use this method.

octodellin said:
go to fastboot mode and run fastboot command:
Code:
fastboot getvar anti
if the displayed output is 3, is good. that means you can use this method.
if the displayed output is 4, you can not use this method.
Click to expand...
Click to collapse
I know how to check anti rollback... I want to check does my bootloader is fake unlocked or not

I copied the patch files to the ROM1 images folder.
I open miflash, selected the ROM1 folder.
I made the testpoint method, and I see driver 9008.
then clicked the refresh button then Flash button on miflash program. It writes "flashing".
Flashing process starts, but after that, it stucks while writing keymaster.mbn file. I waited over 20 minutes but nothing happened.
I tried another miflash from may 2018, but same situation.
I tried other USB ports, nothing changed.
I checked the log file. At begining it seems everything normal, but when it came to write keymaster.mbn file(this is the first file to flash)
The log file looks like this:
...
: Write file C:\RN5... ....\images\keymaster.mbn to partition[keymaster] sector 65536
: write file legnth 357392 to partition 65536
: WriteFile position 0, size 0
: WriteFile position 0, size 0
: WriteFile position 0, size 0
: WriteFile position 0, size 0
: WriteFile position 0, size 0
...
And gooes on like this for over 80000 lines. I closed the miflash.
I checked the phone, nothing happened, It opens normally, old rom still there...
what can be the situation?

The4anoni said:
I know how to check anti rollback... I want to check does my bootloader is fake unlocked or not
Click to expand...
Click to collapse
1. check in mi unlock status from developer mode
2. check from fastboot command: fastboot oem device-info
3. test to unlock bootloader
if you face unlocked in mi unlock status but in fastboot showing "Device unlocked: false" even more you can't bind account, thats mean you unlocked is fake.
netlogger said:
I copied the patch files to the ROM1 images folder.
I open miflash, selected the ROM1 folder.
I made the testpoint method, and I see driver 9008.
then clicked the refresh button then Flash button on miflash program. It writes "flashing".
Flashing process starts, but after that, it stucks while writing keymaster.mbn file. I waited over 20 minutes but nothing happened.
I tried another miflash from may 2018, but same situation.
I tried other USB ports, nothing changed.
I checked the log file. At begining it seems everything normal, but when it came to write keymaster.mbn file(this is the first file to flash)
The log file looks like this:
...
: Write file C:\RN5... ....\images\keymaster.mbn to partition[keymaster] sector 65536
: write file legnth 357392 to partition 65536
: WriteFile position 0, size 0
: WriteFile position 0, size 0
: WriteFile position 0, size 0
: WriteFile position 0, size 0
: WriteFile position 0, size 0
...
And gooes on like this for over 80000 lines. I closed the miflash.
I checked the phone, nothing happened, It opens normally, old rom still there...
what can be the situation?
Click to expand...
Click to collapse
1. make sure that you have extracted the patch. there are 3 files that must be replaced to the images folder in ROM 1 (Global 9.5.17)
2. use the miflash that I use
3. try to change clean all or clean all and lock, with flash_all.bat
hope it works for you ..

I allready tried that all of you wrote. But in windows command prompt mode, I tried to execute flash_all.bat with admin rights. It didn't work.
---------- Post added at 10:45 AM ---------- Previous post was at 10:42 AM ----------
I allready tried all. Nothing changes.
I tried to run flash_all.bat from command prompt with admin rights, but that does not work.

Bruh. Thanks a lot. This is the ONLY guide that has helped me fix my Note 5 Pro.
I was on global rom from the seller... I'm flashing a bunch of ARB 3 or lower MIUI roms... I accidently flashed with lock the bootloader...
That bricked my phone. No other roms would work. No china ones, no global. Tried so many patches until this guide which worked for me.
Thanks

[ROM] ZTE Grand X View 2 (K81) Root and Stock firmware

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'