so i got one of these mk809iv red slider one seems to be different from everyone else i look at
its got kitkat 4.4.2 ktu84q 20150330 . 192513 test keys its got a rk3128 and rtl8723bs wifi everything works well enough
but to start its got a small 1gb user.img and a huge 5.6gb userdata.img makes no sence ran out of app space right away so heres where my problems started
looking for more info i found out this seems to be a clone as most have different wifi chip and even different main chip as most are rk3188
what i wanted to do was change user and userdata basically swap the sizes no luck then i tried to find alternate software not much luck everything i find seems to be for a different version
next i tried dump firmware no luck i can dump partions but not a complete image file
next i tried to root it no luck again
seems this model mounts its partition as mmc and as such non of the romdump stuff works errors out when it cant find /proc/mtd
so if anyone else needs the stock ktu84q 192513 from 20150330 i got it in partion files that i can give
but if anyone else has one of these and came up with any solutions it would be great
I successfuly root similar stick (mk809iv with rk3128) with an app on the playstore. (https://play.google.com/store/apps/details?id=com.quillapps.root.android.without.computer&hl=fr) This app suggest another app in fact that is Kingroot. Not kingoroot.
Maybe you can help me... Do you know if it's possible to install twrp on this stick? Or just reboot into recovery? I tried to boot into recovery mode but it stuck with the android guy with a red triangle and a ! in it. Thank you!
Hello. Can you upload the room? I have RK3128 with RTL8723BS wifi, but i can't find the rom. Thanks
Hi guys.
Disclaimer:
Changing or messing up with IMEI may be banned in your area or country of residence. Please check with your local regulations before attempting to modify the IMEI and related information of your phone. I take no responsibility whatsoever for your attempts to change any such information. This thread does not support in anyway to deliberately modify the identity of the phone.
Click to expand...
Click to collapse
1. PDS partition does not determine IMEI.
As you know PDS is actually at /dev/block/mmcblk0p26 or /dev/block/platform/msm_sdc.1/by-name/pds. When the phone boot it mounts this partition at /pds. After blowng up my IMEI, this partition was still mounting at /pds and had data untouched in it. So this partition is really not important. Also i read on another thread, people with backup also cud not restore their IMEI.
2.When giving command "fastboot erase all", the following partitions are erased:
a. hob (located at /dev/block/platform/msm_sdcc.1/by-name/hob)
b. dhob (located at /dev/block/platform/msm_sdcc.1/by-name/dhob)
c. fsc (located at /dev/block/platform/msm_sdcc.1/by-name/fsc)
There are other partitions erased as well such as fsg,modemst1, modemst2 etc. But these partitions are restored when we flash stock ROM. So they can be taken out of picture.
Possible solutions:
1.Restoring a QCN backup through QPST after putting the phone in BP Tools mode.
Unfortunately this doesn't work as the NV area of the Moto E2(possibly all motos) is write protected.i.e,we won't be able to restore the modified qcn file.
So no luck here.
2.Restoring fsc,hob and dhob files from a working Moto E 2015.
This is something that could work.
As confirmed by many users,restoring these partitions from a working device gives back the radio functionalities but not the IMEI.
If any has more info,they are more than welcome.
Let's get these babies working again.
Sources:http://forum.xda-developers.com/moto-g/help/info-moto-g-imei0-t2925970 and ofcourse me(solutions part).
Friends, along with greeting I want to tell my story.
It turns out that I wanted to start my Huawei GR5 (MM, ROM I got for Google), and not starting with VOL + and POWER, I decided to search the internet for a way to boot it via Android terminal with the file RECOVERY.img from the memory card. THE TUTORIAL
What I remember from the commands was that one wrote about the file dev / block / mmcblk0p18 (something like that), and after that the mobile has not started again.
I have booted with fastboot and through TWRP installed the official IMGs both LP and MM and none works.
"I believe" that the file mmblk0p18 has a lot to do with the error, and if I do not have (after having formatted my laptop) my NANDROID BACKUP.
In the end, is it possible that someone has a NANDROID of the KII L23 clean to share, or do you have some original file mmcblk0p18 to share?
At the moment I think they are the only possible solutions, in advance thank you very much. :victory:
Hello, I've got a bricked Wiko Ridge 4G. I tried everything so far to get it to work.
The problem is that Wiko original app doesn't finish the flashing.
I can flash with fastboot. I flashed all files except system, cache and data.
I booted TWRP, it shows that these partitions have 0 space.
Basically I can explore internal storage with file explorer in TWRP, but system folder is empty, as well as the other two.
I think I could fix this by flashing in fastboot mode.
I extracted the ROM from Wiko flasher, but the files for system, data and cache partition are sparsed.
Does anyone know how to flash this or compile it into one file?
They are all in .img format.
Every second file has only 8 kB, others are all around 128 MB, but are not exactly that much.
All partitions are detected in fastboot when you try to flash something.
I tried to do getvar for all partitions, but it never gives any output.
Other thing that might help my case (I think so) would be a nandroid backup. If someone has a working device, I would appreciate to get me some backups of these 3 partitions
Jovan Riparazioni said:
Hello, I've got a bricked Wiko Ridge 4G. I tried everything so far to get it to work...
Click to expand...
Click to collapse
I don't have this device but, the following thread may be helpful for what you need and don't be afraid to ask for some member guidance too.
https://forum.xda-developers.com/showthread.php?t=3586572
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Ibuprophen said:
I don't have this device but, the following thread may be helpful for what you need and don't be afraid to ask for some member guidance too.
https://forum.xda-developers.com/showthread.php?t=3586572
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Hey, thanks for a quick reply. I already flashed it a dozen of times in EDL. I tried with QFIL, Huiye Qualcomm flasher and even some other tools.
As it starts flashing those partitions, it stops getting readback from sectors.
Out of respect to you and hope I tried to flash it with those Blu firmwares.
Both end normally, but nothing is changed, not even the logo.
I think it's due to having encryption or Google Account removed at the time of rooting, but I'm not sure, because I can flash pretty much any partition other than those (which I can't cuz chunks...).
I can erase config, oem, there isn't even FRP partition.
I found supersu folder in the root directory with TWRP. When TWRP boots, it says something about failing to mount data partition due to wrong or missing encryption header.
As far as I understand, this could also be due to small incompatibilities of existing TWRP for L5510.
When I try to do anything with those partitions, it gives out an error 8.
Only copying files from internal to SD I know works for sure, I haven't tried other way.
I formated system, cache and userdata normally with fastboot format:ext4, but TWRP still reports 0 size with some subdirectories inside the main folders (partitions) in root directory.
Is there a way to compile the system from those system_x.img chunks?
I'm using Windows 10, so it's a bit more difficult to work with .ext4 fs images, I don't really know of a really 'smart' and universal tool which can do my work.
I had an idea to manually copy the content of system.img to system partition with twrp, as well with other partitions. I know it's a pain in the butt, but I don't really know what to do anymore.
I'm an ex repairman, I'm let's say "specialised" for software type of work. I'm quite familiar with deep flash, partitions, sectors, memory addressing and stuff. I at least understand how it works.
Only thing I haven't tried is the above mentioned: copying files manually (which might not work, no matter I can copy files without trouble), nandroid, or compiling/extracting those chunks into something I can actually work with. If you know something, please enlighten me. I bought this unit cheep for 30 euro while I was still in business, but now I need a new phone for myself, and I know Wiko isn't much comparing to my current HTC M7, but this M7 is dying literally, so I'm good as far as it's Qualcomm haha
i have the same problem as you with my ridge 4g
did you find any solutions ?????
plzzzz help me
_6ix._.9ine said:
i have the same problem as you with my ridge 4g
did you find any solutions ?????
plzzzz help me
Click to expand...
Click to collapse
Nope, seems like nobody will give us a nandroid
wiko ridge 4g
Jovan Riparazioni said:
Nope, seems like nobody will give us a nandroid
Click to expand...
Click to collapse
did u find q solution ???
Hi,
On Redmi 6 i noticed, that IMEI is stored in different way than in previous Xiaomi models. File MD0B_001 does not exist, instead we have LD0B_001. File format for sure has changed. New file has 384B while old one had as i remember 32B(?).
Is there any known way to change IMEI on this device? Replacing LD file with old MD does not produce any good results. Something is restoring LD01_001 on reboot if you will replace it inside /vendor/nvdata/md/NVRAM/NVD_IMEI. Tried after remounting, in TWRP, etc. Result is always the same. Probably u have to replace both nvdata and nvram.
For sure AT+EGMR method does not work either (tested on Treble rom). On this device im receiving just ERROR when im executing AT command to /dev/radio/pttycmd1
MAUI 10 is unable to connect to this device. Computer is for sure configured correctly and has proper drivers (im using couple phones and others connecting).
Any one tried to change IMEI on new Xiaomi Treble ready MTK phones? Does any1 managed to find method how to change IMEIs on those devices?
Best regards
Daveron81 said:
Hi,
On Redmi 6 i noticed, that IMEI is stored in different way than in previous Xiaomi models. File MD0B_001 does not exist, instead we have LD0B_001. File format for sure has changed. New file has 384B while old one had as i remember 32B(?).
Is there any known way to change IMEI on this device? Replacing LD file with old MD does not produce any good results. Something is restoring LD01_001 on reboot if you will replace it inside /vendor/nvdata/md/NVRAM/NVD_IMEI. Tried after remounting, in TWRP, etc. Result is always the same. Probably u have to replace both nvdata and nvram.
For sure AT+EGMR method does not work either (tested on Treble rom). On this device im receiving just ERROR when im executing AT command to /dev/radio/pttycmd1
MAUI 10 is unable to connect to this device. Computer is for sure configured correctly and has proper drivers (im using couple phones and others connecting).
Any one tried to change IMEI on new Xiaomi Treble ready MTK phones? Does any1 managed to find method how to change IMEIs on those devices?
Best regards
Click to expand...
Click to collapse
Please I need change my device IMIE