Related
Bought K3 Note some days ago and tried to root it, but, after finding loads of cryptic roots often with needed files missing, I first reduced the phone to a bootloop and finally to a brick.
Yesterday, I got SP Flash Tool working with a previous version of Lollpop (5.0) and have unbricked it. (This ROM keeps throwing up obnoxious notifications for apps & wallpapers, etc.)
I've tried to find a version of Android 5.1.1 (English/Chinese?) with scatter file that I can flash to return the phone to factory standard. I last downloaded VIBEUI_V2.8_1535_5.128.1_ST_K50-T5.zip which was posted somewhere in February, but SP Flash Tool did not recognize the scatter file, which reads:
Code:
preloader 0x0
pgpt 0x0
proinfo 0x80000
nvram 0x380000
protect1 0x880000
protect2 0x1280000
seccfg 0x1c80000
lk 0x1cc0000
boot 0x1d20000
recovery 0x2d20000
secro 0x3d20000
para 0x4320000
logo 0x43a0000
expdb 0x4ba0000
tee1 0x55a0000
tee2 0x5aa0000
metadata 0x5fa0000
frp 0x7fa0000
system 0x8800000
cache 0xa8800000
userdata 0xc3000000
flashinfo 0xFFFF0084
sgpt 0xFFFF0004
It looks nothing like the usual scatter files I've seen in the past days. So I guess that's a gigabyte download blown because of a 500byte file. (The following are the files that make up VIBEUI_V2.8_1535_5.128.1_ST_K50-T5.zip.)
Code:
[META-INF]
[sig]
boot.img
file_contents
logo.img
mobicore.bin
scatter.txt
SEC_VER.txt
system.new.dat
system.patch.dat
system.transfer.list
type.txt
uboot.img
These files don't look like what I would expect to come with a scatter file.
I've had enough practice with SP Flash Tool so I feel comfortable using it and would like to continue with it (rather than the other 57 apps & tools I've fiddled with), but I can't see any ROMs at NeedROM that are advertized as Flash Tool friendly (ie with correct scatter file).
-------------------
So is there a link out there for a stock Android 5.1.1 ROM with scatter file for the k50-t5? (Or is there a simple way to make a scatter file for the above ROM?) Once I can get the phone basically back to factory form, I can root it with tools I understand.
Thanks for any help.
While looking around for a stock ROM, I thought I'd try VibeUI_Xancin listed in the "[Index Thread] Lenovo K3 Note" because the ROM I'd flashed—thinking it was stock as indicated—was aggressively intrusive with ads. That's gone thankfully, but Xancin is extremely spartan, almost no apps of note—I can live with that—but no way I can see to make it look pretty—which I can't live with.
I so need an official stock Android 5.1.1 ROM for the K3! —hopefully with scatter file for SP Flash Tool.
doktorspin said:
While looking around for a stock ROM, I thought I'd try VibeUI_Xancin listed in the "[Index Thread] Lenovo K3 Note" because the ROM I'd flashed—thinking it was stock as indicated—was aggressively intrusive with ads. That's gone thankfully, but Xancin is extremely spartan, almost no apps of note—I can live with that—but no way I can see to make it look pretty—which I can't live with.
I so need an official stock Android 5.1.1 ROM for the K3! —hopefully with scatter file for SP Flash Tool.
Click to expand...
Click to collapse
so far i see only this india stock rom K50a40_S112_150610_ROW have scatterfile that recognize by SP Flashtool
h t t p://firmwarefile.com/lenovo-k3-note
here u go...for vebui roms its no MT6752_Android_scatter file
i dont know if we only just can rename it on other stock k3n roms coz others stock rom just only have scatterfile..without that MT6752_Android_ extensions on it..
im oso just a noob..:silly:
btw bro..i try use stock india roms and just use CWM recovery to flash other China roms and customs roms..and its work..
i dont use SP Flashtools...i using SP flashtool only for flashing CWM recovery
redmi_3g said:
so far i see only this india stock rom K50a40_S112_150610_ROW have scatterfile that recognize by SP Flashtool
h t t p://firmwarefile.com/lenovo-k3-note
here u go...for vebui roms its no MT6752_Android_scatter file
i dont know if we only just can rename it on other stock k3n roms coz others stock rom just only have scatterfile..without that MT6752_Android_ extensions on it..
im oso just a noob..:silly:
btw bro..i try use stock india roms and just use CWM recovery to flash other China roms and customs roms..and its work..
i dont use SP Flashtools...i using SP flashtool only for flashing CWM recovery
Click to expand...
Click to collapse
Thanks for the response. I was trying to set the phone up for someone else, so I left CyanogenMod on it because I couldn't find a stock ROM and CM as stable, unlike all other ROMs I tried. The user seems happy after two months, even though warranty is void.
I have bought a new SP, and gave my last one to my wife, so I have a chance to start fresh.
I can't stand the bloating on the phone, and would like a light, fast lollipop ROM on it that still lets me use Sony's photo apps if possible. This one seems right for me (http://forum.xda-developers.com/xperia-sp/development/rom-cyanogenmod-12-1-sabermod-t3219230).
The problem I am experiencing is that when I go to various builds, I am having trouble understanding the instructions, and how to do what they are asking. I understand that I need to break the bootloader first, and then do something after that, and then install drivers, etc.. but I feel like a bit of an idiot because I just don't get it.
The instructions for one that I was thinking of putting on reads as follows :
* place the phone in fastboot mode, and flash the boot.img from the latest build: sudo fastboot flash boot boot.img
* enter Cyanogen Recovery
* flash the TWRP zip you downloaded via Cyanogen Recovery.
* shutdown and reboot into TWRP recovery.
* wipe/format /system /data /cache /dalvik.
* flash latest available build, and flash gapps.
* reboot and you're done.
Questions
- How do I flash the boot.img from the latest build? What is boot.img? What does "sudo fastboot flash boot boot.img " mean?
- How do I enter Cyanogen Recovery? What is it? Where do I get it?
- How do I flash the TWRP zip?
I could go on. I really need a step by step guide, or some systematic way to educate myself.
Can you suggest a ROM with a step by step guide, or one with a youtube video showing how it is done (walkthrough) or similar?
http://forum.xda-developers.com/showthread.php?t=2888579
Use this Guide to understand about Custom ROMs, Bootloaders, Flashing ROMs, Kernel and Recovery. Specific to Xperia SP.
Take your time to read, if didn't understand something, search for it on Google, you'll understand things
There are many more generic device Guides, but this Guide is Specifically for our Device.
Once you read the guide, then you'll understand the Instructions given in any ROM thread.
Sent from my Q1010i using Tapatalk
make backup of drm partition, unlock bootloader then start flashing roms
Hi,
I'm having a problem installing TWRP on my doogee X5, in order to root the device. I have tried to flash the recovery with sp flash tool, and every time I try, I can boot to the boot mode menu, select "recovery" and see the doogee logo for a while, then a black screen, then the doogee logo again, following into a normal boot.
This is the X5, not the X5 pro.
firmware on phone: "DOOGEE-X5-B-Android5.1-2016.03.18"
Any help?
PS: I don't want to use kingroot to root the phone, as I also want xposed.
I'm looking for a solution to that very problem too. Let's see if someone comes to help!
Exactly the same goes here too. Probably there's not an updated TWRP for V18 which I am using. I have not the slightest idea who could help us.
Rooting Doogee X5 / TWRP install
Here's what worked for me, thought I'd share this.
Out of the box was on version 18 and wanted to root , so i blindly installed King Root which did work, i then installed Supeer SU me which changed the king root to super user. After that over a week i read that TWRP 3.0.2 worked for one person so using Flashify i flashed the recovery image , after changing it to recovery.img and it worked . Such luck right, i went on to read the forums as im in love with this device , Wakefield helpful was NEEDROM.com , you need to register but there are many roms and tools for mediatek 6580soc . Out of curiosity i downloaded some rar. File roms ACS different fish tools. The best to use if you've only got oneX5 is SP flash tool. Also look for mediatek vcom drivers which auto installs the correct drivers. There are easy to follow you tube videos fur flashing using SP Flash tool. The latest version had been updated for simplicity. the process basically is ( load .bin file in its respective area,( from Flash tool) and load scatter.txt in its box ( from rar. File) the whole interface will polemist populate plug go to format hit start plug in turned off phone without battery, it'll give red then yellow bar and a check, then unplug hi to firmware screen and choose to start dload only except bootloader, start , plug wait for coloured bars and check your done. i even had gotten errors due to a faulty dload and repeated the process till i got it. I understand that not all have the patience for this, therefore i suggest using flash tool of king root messes up though that's rare.
An alternative to supersu me is to root with king root then install twrp with flashify then you can uninstall / repack king root and flash Updateroot.Script available by someone on needrom. That includes super user and busy box. Then installxposed. Etc.
* Each process in the above proven tuturial has been obtained online from other sites not just xda. I've chosen 5.1 as an idealOS for me, I can't say the route to take fur Marshmallow.
This is for -b and non b only version 18, and 19. All others take your own chances but it's resilient chip so have fun.
(SOLVED just flash DOOGEE-X5-HOT2-6.0.zip and the twrp from the rom is installed and works after rebooting in recovery mode.) after flashing CWM recovery
Listed: 10/28/2016 11:16 pm
ROM Version: 6.0 / 5.1 to my doogeex5 (flashing succeed) i got an green android logo with an error sighn(see picture)and some chinese letters...
in normal boot no problem,also upgrading to android 6 (flashed) gave no problem...
how to get new recovery(flashing other recovery`s gave same output exept the chinese sighns disapeard)
kingroot V4.80 couldnt root my doogeex5 after 27%rooting it says cant root device
also doesnt the system update in `my device` recognice the memory card ...no sd card inserted...
any suggestions?
I have a similar problem. Unlocking the boot loader works fine, but i can't seem to find a working twrp file for my phone.
I have an X5 pro (x5pro-android5.1-r17-2015.07.01). I tried different twrp recoverys from needrom and i can flash them to the device, but if i try to boot into recovery i only get the robot with the red warning triangle. Rest of the phone works fine, but i'd like to get a working custom recovery.
Can anyone help me?
So i rooted my phone with kingroot and i wanted to install a custom recovery without breaking the device how should i move next ? My X5 is an old motherboard version android 5.1 V15-2015.11.02 and that was the last official fota update for me. Is there any ofgicial upgrade suitable for my model like android 6.0 ? Two more things. My battery goes down rapidly and i dont know if its battery or chargers problem what should i do ?
http://www.needrom.com/category/doogee/serial-x-doogee/x5-doogee/
even without rooted phone you can flash a lot of roms from above link and read how to
Yeah i noticed this site man but says you need to register first. And one more thing spft always detects scatter files as invalid or maybe not legal even from the official site of doogee. I use the spft from doogeemobile site.
I am using SP_Flash_Tool_exe_Linux_v5.1520.00.100 with ubuntu(linux) maybe try an other flashtool edition,registering needrom is simple just making username and make a password when you are registered take the inifix hot 2.6.0 for the x5 flash it and you have got also a TWRP from wich you can root or install also the .zip roms etc.
I mentioned the inifix hot2.6.0 because that was the one i had succes even with a bricked recovery caused by flashing a cwm recovery without rooting first.
Well i just want for sure make a backup of my current rom without wiping it. I guess the infinit will delete all. Plus i also want to install recovery having rooted it 1st which is easy i think on 5.1. I have the one with the old motherboard not the -b. To sum up i want to install the official updated rom V20 via sd (which i tried and didnt work) luckily it didnt brick or via spft which doesnt load scatter file says is not valid no matter if i use latest or older version of spft in order to flash it manually. Its risky to root and install a recovery by an apk without having my rom backed up 1st. And even with the spft i cant do that. I just want to fix my battery status. Thats all. I use xp pro os.
indeed it is hard to install android 5.1 roms on the doogee x5with a twrp,al the 5.1 roms i could flash,but then i bricked the recovery,wich made no differend for the installed 5.1 roms,they just work.i can only install a working twrp by flashing Infinix Hot 2 6.0,wich is a 6.0 rom,but as far as i know you cant install a 5.1 rom with a 6.0 twrp... error 7.
Thats why we will end this discussion for now and wait for future solutions. Thx for your concern man. I just dont want to brick it since it runs smoothly with 5.1. As i said before i wanted to install the latest (official stock) V20 rom recently released. But i cant do it even from the tutorial that exists on their forum. It's a use of spft but i cant manage to do it. Scatter file always invalid.V20 Rom fixes some bugs and displays your interface like on 6.0 android version. We talk mate.
Hello !
Any news on the matter ?
I have got an X5 with Android 6 (!) on it. Have tried to root it with several one-click tools but this does not work.
Any suggestions?
Hi! What room do you recommend The most stable, And best, Under flashtool To Doogee X5? Thanks in advance for help!
hello i need help on my doogee x5 all 6.0 custom rom flash give me error 11 on twrp how to fix please ,
Any help please?
I have error 7 on all rom
Help?
Having tried to install TWRP it is rejected
Having downloaded twrp_x5max.img from needrom and used the adp method of installing the TWRP.img (https://www.xda-developers.com/how-to-install-twrp/). I get the following error message. "writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed".
So How do I get the TWRP img loaded into the Doogee X5Max (not pro) android with marshmallow?
I have tried using SP FlashTool and it says installed successfully, but I still get the default recovery program, after the dead robot with triangle and a exclamation mark inside, when booting into recovery using keys or adb command.
Is there another way of getting this image file loaded into the recovery partition?
I have followed all the set up steps in developers mode, so why cannot I use adb?
Code:
/*
* 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 the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
Hello people.
Due to the fact that I have a tablet built around the MTK8127 SOC I decided to adapt some stuff for the Amazon Fire 2015
I need to mention that I don`t own the tablet so I don`t have the means to test the recovery.
The recovery is built from source using CM 12.1 and is based on the classic CWM with further additions designed for MTK devices like backup of important partitions (uboot. tee1, tee2 and so on)
What could be wrong:
-mounting points, as I used the default ones that are being used for twrp
-resolution (the recovery might not fit properly on the screen.
-other random stuff
Features
-full touch recovery
- all cwm functionalities (adb, sideload, backup, restore, install, mass storage...).
-in Carliv menu there is now a new section for flashing boot and recovery images.
-a special menu from where you can restore specific partitions
-multizip flashing function
The main sources used are here:
https://bitbucket.org/amazonfire2015/cm_device_amazon_ford/src
I have not uploaded yet the device tree that I am using as I don`t know if the build is actually working (it should), Will do when I have some days off from work .
If someone is willing to flash and tell me what are the flaws, I will address the issues.
Credits to @carliv aka @bluefirebird for his efforts in continuing the CWM project in his new form as CTR.
globula_neagra said:
Hello people.
Due to the fact that I have a tablet built around the MTK8127 SOC I decided to adapt some stuff for the Amazon Fire 2015
I need to mention that I don`t own the tablet so I don`t have the means to test the recovery.
The recovery is built from source using CM 12.1 and is based on the classic CWM with further additions designed for MTK devices like backup of important partitions (uboot. tee1, tee2 and so on)
What could be wrong:
-mounting points, as I used the default ones that are being used for twrp
-resolution (the recovery might not fit properly on the screen.
-other random stuff
Features
-full touch recovery
- all cwm functionalities (adb, sideload, backup, restore, install, mass storage...).
-in Carliv menu there is now a new section for flashing boot and recovery images.
-a special menu from where you can restore specific partitions
-multizip flashing function
The main sources used are here:
https://bitbucket.org/amazonfire2015/cm_device_amazon_ford/src
I have not uploaded yet the device tree that I am using as I don`t know if the build is actually working (it should), Will do when I have some days off from work .
If someone is willing to flash and tell me what are the flaws, I will address the issues.
Credits to @carliv aka @bluefirebird for his efforts in continuing the CWM project in his new form as CTR.
Click to expand...
Click to collapse
For awareness:
- this (any) custom recovery can only be started from fastboot on devices with 5.0.x bootloaders (rather rare)
- no custom recovery can be flashed (installed) on this device as bootloader remains locked.
globula_neagra said:
If someone is willing to flash and tell me what are the flaws, I will address the issues.
Click to expand...
Click to collapse
Thanks for your work but... no one will flash this because it's impossible on Fire due to the locked bootloader. People with the 5.0.1-based fastboot implementation will be able to boot it but not to flash it. I will try it and report back as I use this recovery on my MTK-base Asus and I love it.
A bootloader downgrade should be achievable with SP flash tools.
Are there any bootloaders uploaded somewhere ?
globula_neagra said:
A bootloader downgrade should be achievable with SP flash tools.
Are there any bootloaders uploaded somewhere ?
Click to expand...
Click to collapse
Have a look at the various threads in the different sections of the "Amazon Fire" forum. There are some downgrade protections from Amazon on these devices and hard bricks are unfortunately not so difficult.
I will get one on BF just to see if I can sort something out regarding the bootloader.
The SP flash tools have access to the lowest level of flashing, from where you can literally re-write the flash from top to bottom so I can`t see how it can go wrong unless they are changing the partitions sizes during firmware upgrades.
But I don`t understand a thing, how come TWRP is working and the one that I compiled is not working. Does the recovery partition get`s re-flashed after boot ?
I will get one on BF just to see if I can sort something out regarding the bootloader.
The SP flash tools have access to the lowest level of flashing, from where you can literally re-write the flash from top to bottom so I can`t see how it can go wrong unless they are changing the partitions sizes during firmware upgrades.
But I don`t understand a thing, how come TWRP is working and the one that I compiled is not working. Does the recovery partition get`s re-flashed after boot ?
globula_neagra said:
I will get one on BF just to see if I can sort something out regarding the bootloader.
The SP flash tools have access to the lowest level of flashing, from where you can literally re-write the flash from top to bottom so I can`t see how it can go wrong unless they are changing the partitions sizes during firmware upgrades.
But I don`t understand a thing, how come TWRP is working and the one that I compiled is not working. Does the recovery partition get`s re-flashed after boot ?
Click to expand...
Click to collapse
Partial responses:
- no one has successfully flashed twrp or any other custom recovery
- a custom recovery could be booted from fastboot on early devices; the 'vulnerability' was closed with bootloader 5.1.x and above
- bootloaders 5.1.x+ can not be rolled back to 5.0.x; hard brick
- Amazon rollback efuse has proven to be fairly robust; was never cracked on 3rd/4th gen devices that enjoyed a 2+ year run (albeit on a different chipset)
globula_neagra said:
I will get one on BF just to see if I can sort something out regarding the bootloader.
The SP flash tools have access to the lowest level of flashing, from where you can literally re-write the flash from top to bottom so I can`t see how it can go wrong unless they are changing the partitions sizes during firmware upgrades.
But I don`t understand a thing, how come TWRP is working and the one that I compiled is not working. Does the recovery partition get`s re-flashed after boot ?
Click to expand...
Click to collapse
We don't have .auth file for authentication. SP Flash tool useless without it (we can't even readback). We have secured chip.
*delete thread*
Please...?
?
quick review:
recovery boot fine
resolution seems to be off
buttons don't work
touch screen is off
sd_shadow said:
quick review:
recovery boot fine
resolution seems to be off
buttons don't work
touch screen is off
Click to expand...
Click to collapse
Sounds like a home run
I have a rare phone running Android 6.0 on a MT6750 with an unlocked bootloader (might be MT6750T since it is 1920x1080, but the only things I have found say MT6750)
I have been unable to get TWRP working on this phone after trying several porting guides and TWRP images. Almost all port attempts result in the boot image (logo.bin - android logo), followed by a black screen for a few seconds, then it reboots into Android.
Is it possible to manually patch the boot.img to gain root? If so, can someone point me to a guide for it? I found https://forum.xda-developers.com/android/software-hacking/systemless-root-mediatek-t3309909 but PATH doesnt seem to be set anywhere in my boot image (grep -nrw 'boot.img-ramdisk' -e "PATH"). I tried adding "export PATH $PATH:/data/bin" or "export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin::/data/bin" to init.environ.rc with other exports, but I get a boot loop
try recompile the decompiled boot.img without doing any changes and flash the compiled boot.img to see that there is no problem with respect to compilation of boot.img
shankar_vl said:
try recompile the decompiled boot.img without doing any changes and flash the compiled boot.img to see that there is no problem with respect to compilation of boot.img
Click to expand...
Click to collapse
i decompiled and recompiled without any changes using kitchen tools and flashed back ... but its showing error.
same with recovery.img also
btw im using oppo f3 mt6750t
rajeshca911 said:
i decompiled and recompiled without any changes using kitchen tools and flashed back ... but its showing error.
same with recovery.img also
btw im using oppo f3 mt6750t
Click to expand...
Click to collapse
Then its a compilation error. Its not being compiled correctly.
Btw, systemless root by supersu and magisk do a lot things like starting sudaemon, injecting supolicy changes, mounting su.img, etc. Its better to port a custom recovery and let supersu or magisk zip do all the required things to root your device.
Or if you want to be ambitious, dirty your hands with hackings, unzip these zip files and try to implement manually what is programmed there.
My suggestion is go for porting recovery from devices matching your device specs ( need not be 100%). There are several threads on this forum helping you out on this. I think chances of porting a workable custom recovery are brighter than manually compiling su compatible boot.img.
There's the problem..
I did port custom recovery.
But when I flash it back to device it's showin error.
I understand that I need to dirt my hands more to get root my device
So I decided to compile revovery.. But oppO f3 source files r not available. I tried with omni Tom source. But it failed
rajeshca911 said:
i decompiled and recompiled without any changes using kitchen tools and flashed back ... but its showing error.
same with recovery.img also
btw im using oppo f3 mt6750t
Click to expand...
Click to collapse
rajeshca911 said:
There's the problem..
I did port custom recovery.
But when I flash it back to device it's showin error.
I understand that I need to dirt my hands more to get root my device
So I decided to compile revovery.. But oppO f3 source files r not available. I tried with omni Tom source. But it failed
Click to expand...
Click to collapse
You said that even the imgs just compiled without any changes made to decompiled files are not able to boot. Then there must be something wrong with compiling. Your tools for compiling may not be correctly working.
There are carlive image kitchen tools. get them here https://forum.xda-developers.com/android/development/tool-cika-carliv-image-kitchen-android-t3013658. They are known for flawless working.
What is more important now is that you have right tools for compiling imgs. Then you can think of further.
shankar_vl said:
You said that even the imgs just compiled without any changes made to decompiled files are not able to boot. Then there must be something wrong with compiling. Your tools for compiling may not be correctly working.
There are carlive image kitchen tools. get them here https://forum.xda-developers.com/android/development/tool-cika-carliv-image-kitchen-android-t3013658. They are known for flawless working.
What is more important now is that you have right tools for compiling imgs. Then you can think of further.
Click to expand...
Click to collapse
Thanks bro. But im using carliv kitchen tools only.
I didn't tried with other kitchen tools yet.. So i give a try other tools
rajeshca911 said:
Thanks bro. But im using carliv kitchen tools only.
I didn't tried with other kitchen tools yet.. So i give a try other tools
Click to expand...
Click to collapse
no need. carliv tools are perfect. stick with them.
are you able to successfully flash imgs with sp flash tools? no matter whether you are able to boot with them.
as for porting, use twrp or any other custom recovery of SoC as yours, mt6750t and of OS version similar to yours as well.
shankar_vl said:
no need. carliv tools are perfect. stick with them.
are you able to successfully flash imgs with sp flash tools? no matter whether you are able to boot with them.
as for porting, use twrp or any other custom recovery of SoC as yours, mt6750t.
Click to expand...
Click to collapse
Ok.. I stick with carliv as u suggested. And... Yes... Im able to flash img files to phone but not with sp flash tools. Im using professional tools ( uni tools from volcano) and also flashing using a cracked download tool meant for oppo devices. ( the download tool was created on base of sp flash tools only)
Then...
I just tried twrp porting only ( same soc mt6750t quitel k6000 plus i think.. Which chipset is mt6750t)
Also tried with oppo f1s twrp which chipset is mt6750.. ( not 6750t.. ) both went wrong..
seniors and xda developrs ( zackie& a guy from Indonesia unfortunately i forgot his name) also tried to. Port twrp for me. I also tried flashing their img files ..everything went not well.. There i have understood that either compiling or flashing causing error in my device
Thats y im trying to find other wayz.. There i found ur thread .& fetching useful checklist:good:
rajeshca911 said:
Ok.. I stick with carliv as u suggested. And... Yes... Im able to flash img files to phone but not with sp flash tools. Im using professional tools ( uni tools from volcano) and also flashing using a cracked download tool meant for oppo devices. ( the download tool was created on base of sp flash tools only)
Then...
I just tried twrp porting only ( same soc mt6750t quitel k6000 plus i think.. Which chipset is mt6750t)
Also tried with oppo f1s twrp which chipset is mt6750.. ( not 6750t.. ) both went wrong..
seniors and xda developrs ( zackie& a guy from Indonesia unfortunately i forgot his name) also tried to. Port twrp for me. I also tried flashing their img files ..everything went not well.. There i have understood that either compiling or flashing causing error in my device
Thats y im trying to find other wayz.. There i found ur thread .& fetching useful checklist:good:
Click to expand...
Click to collapse
As you tried various flashing methods, you might have already known all the related intricasies of flashing. still I just want to mention that I presume you might have then known vcom drivers, creating scatter file with mtkdroid tools, loading scatter file and, most importantly switching off phone and plugging phone to PC just after clicking on flash button in sp flash tool.
And about the other tools of flashing you mentioned, sorry I will not be helpful.
A thing to mention regarding porting is taking care of mount points in fstab file and a similar file if any at /etc folder in ramdisk of decompiled port recovery. mount points should be same as fstab of your boot.img.
Besides, ensure kernel (Imaze) of port recovery is replaced with that of boot.img.
shankar_vl said:
As you tried various flashing methods, you might have already known all the related intricasies of flashing. still I just want to mention that I presume you might have then known vcom drivers, creating scatter file with mtkdroid tools, loading scatter file and, most importantly switching off phone and plugging phone to PC just after clicking on flash button in sp flash tool.
And about the other tools of flashing you mentioned, sorry I will not be helpful.
A thing to mention regarding porting is taking care of mount points in fstab file and a similar file if any at /etc folder in ramdisk of decompiled port recovery. mount points should be same as fstab of your boot.img.
Besides, ensure kernel (Imaze) of port recovery is replaced with that of boot.img.
Click to expand...
Click to collapse
Your not helpfull??.. I don't agree with that. May be im Not in the position to catch your mind.
However.. Im not going to miss single chance to upgrade myself ( yes ofcourse from devs n seniors like u)
As you said
1) i have installed vcom drivers & fetched scatter file. ( again not from mtk droid tools) . I heard mtkdroid tools nOt fully supporting mt67xx Series. Even i tried modified mtkdroid tools developed by dev havoc.. And droid tool showed some info like cpu info.. Etc. But right hand side there was an error which saying that its usable to fetch info. . I presume the error may b causing by oppo. Own OS ( Color OS based on android 6.0).. And my last try was 2 months ago. So i dont know if there is any improvements in droid tools or not. Please privide me links if they updated/ supported 67xx series
2)yes i agree with mount points you mentioned. I was just replacing fstab file from stock to. Port. I didnt edit any. . I will check again and update u.
3) Actually im in dilemma to blame on cimpiling or flashing.. The device is not booting even i didn't modify any item after repack. I need solution for that. If that resolved... Automatically everything will b set up by themselves.. Pls share any views regarding this..
I know its difficult to u to guide until u have hands on it or personally seen d procedures & results
I may upload videos / pictures/ share Team viewer etc.. if u want to see it personally.. So.. U can better understand my problem , my flaws where i need to b improved ( onlynif u wish) however i need a mentor to guide n judge methods im following
rajeshca911 said:
Your not helpfull??.. I don't agree with that. May be im Not in the position to catch your mind.
However.. Im not going to miss single chance to upgrade myself ( yes ofcourse from devs n seniors like u)
As you said
1) i have installed vcom drivers & fetched scatter file. ( again not from mtk droid tools) . I heard mtkdroid tools nOt fully supporting mt67xx Series. Even i tried modified mtkdroid tools developed by dev havoc.. And droid tool showed some info like cpu info.. Etc. But right hand side there was an error which saying that its usable to fetch info. . I presume the error may b causing by oppo. Own OS ( Color OS based on android 6.0).. And my last try was 2 months ago. So i dont know if there is any improvements in droid tools or not. Please privide me links if they updated/ supported 67xx series
2)yes i agree with mount points you mentioned. I was just replacing fstab file from stock to. Port. I didnt edit any. . I will check again and update u.
3) Actually im in dilemma to blame on cimpiling or flashing.. The device is not booting even i didn't modify any item after repack. I need solution for that. If that resolved... Automatically everything will b set up by themselves.. Pls share any views regarding this..
I know its difficult to u to guide until u have hands on it or personally seen d procedures & results
I may upload videos / pictures/ share Team viewer etc.. if u want to see it personally.. So.. U can better understand my problem , my flaws where i need to b improved ( onlynif u wish) however i need a mentor to guide n judge methods im following
Click to expand...
Click to collapse
I empathize with your frustration.
Truth is that with the devices which have not caught the fancy of developers, not having proven root methods, custom recovery, etc only, we take initiatives ourselves and learn the things the hard way which is essentially a true way learning. With popular devices having already so many developments, there is no scope for adventurism and fun as well.
Just see back what are all you gained in doing the things you did with your device for gaining root. Could it have been possible with the so called popular devices?
Now let's come to the issue. In all times of failed booting on compiled imgs, how did you restore them? flashing again stock boot and recovery imgs? and with tools you mentioned?
If you could flash stock boot and recovery with the tools you mentioned, then there is no problem with those flashing tools. Then it comes to the decompiling and recompiling of imgs.
If it could be possible, can you share here stock boot.img, and custom recovery you have selected for porting (also mention the device name, recovery pertained). Let me try.
Yup.. Bro.
What have you said all true.. during this journey i have learned so manythings like porting custom recovery , read back firmware etc and i cant forget what i have learned.. so many trail and errors
below link is the stock and custom recovery i tried to port
https://drive.google.com/file/d/0B6wWbhnrRZ_-V2RZQXByYjc4QVU/view?usp=drive_web
and a developer also tried to to port recovery for me .. below is the link which he modified for me
https://www.androidfilehost.com/?fid=745425885120760137
Im also enclosing stock boot.img
https://mega.nz/#!MF1ySQ4D!ku6RWfOP8QTkm75sNq_1_n-_Af0y843J0I0tiCHRa8k
My Device Details are
Manufacture : Oppo
Device name : Oppo f3
Model No : CPH1609
chipset : MT6750T , 4gb Ram , 64 Gb storage
[ I Really praying Inside ....:angel: god may give result for our endless efforts }
@rajeshca911 can you give details for the custom recovery you have given links, like name of the device, its os ( lollipop, marshmallow, like), and chipset if possible, it pertained to.
shankar_vl said:
@rajeshca911 can you give details for the custom recovery you have given links, like name of the device, its os ( lollipop, marshmallow, like), and chipset if possible, it pertained to.
Click to expand...
Click to collapse
Aquired custom recovery from
Device : qukitel K6000 plus, chipset MT6750T
android version 6.0 (from below)
https://www.google.co.in/amp/s/foru...al/oukitel-k6000-plus-twrp-root-t3620241/amp/
rajeshca911 said:
Aquired custom recovery from
Device : qukitel K6000 plus, chipset MT6750T
android version 6.0 (from below)
https://www.google.co.in/amp/s/foru...al/oukitel-k6000-plus-twrp-root-t3620241/amp/
Click to expand...
Click to collapse
I think the signature of the boot.img gets changed. Try to sign it after decompiling and recompiling by AVB patcher from here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
anandverma458 said:
I think the signature of the boot.img gets changed. Try to sign it after decompiling and recompiling by AVB patcher from here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Click to expand...
Click to collapse
Shall i sign both boot.img and recovery.img as well?? or is it enough to sign compiled recovery.img ?
---------- Post added at 07:57 AM ---------- Previous post was at 07:44 AM ----------
i generated public and private keys also signed and generated
boot_signed.img
recovery_signed.img
first i flashed both the images... result was soft brick and i had to flash original boot.img
second i flashed only signed recovery.img and same was repeated.
rajeshca911 said:
Shall i sign both boot.img and recovery.img as well?? or is it enough to sign compiled recovery.img ?
---------- Post added at 07:57 AM ---------- Previous post was at 07:44 AM ----------
i generated public and private keys also signed and generated
boot_signed.img
recovery_signed.img
first i flashed both the images... result was soft brick and i had to flash original boot.img
second i flashed only signed recovery.img and same was repeated.
Click to expand...
Click to collapse
Actually, I had the same problem (I have vivo 1603). When I flashed boot.img after decompiling and recompiling,it bootlooped. I had twrp installed, so I first restored the backup of stock boot.img, and then installed the recompiled boot.img without rebooting. That worked for me
As you don't have custom recovery, I suggest that you first flash stock boot.img, and after the process completes, flash the recompiled boot.img without rebooting your device.
Hey bro, I decompiled the stock boot.img to see that if 'verify' flag was preventing booting the system with other than stock recovery. Dm-verity is a recent security control for preventing booting with changed/modified kernel/system. But I could not find any such flags, but found verity_key, so I just deleted it and decompiled the boot.img. I am not sure whether it can solve your booting problem. Let's see will this now allow to boot with custom kernel. Here is the modified stock boot.img. http://www.mediafire.com/file/tc1k1ghmy76nfqd/modified_oppo_boot.img
Flash first this boot.img and then flash the custom recovery.imgs (you can try your recoveries also)
I have also ported two recovery.imgs. Both are ported from the twrps for the same device, K6000 plus. However, what I found for this k6000 plus was different in size. So I ported two twrp recovery imgs. Here are two twrp ported recoveries, one is from you have given links to and another is from what I found on this forum.
http://www.mediafire.com/file/4als7qmpwdz1iv4/oppo_port_twrpv1.img
http://www.mediafire.com/file/5xz7387at6rr0dy/oppo_port_twrpv2.img
Once again, I reiterate that first flash the modified boot.img and then try flashing the recoveries.
Best of luck
anandverma458 said:
Actually, I had the same problem (I have vivo 1603). When I flashed boot.img after decompiling and recompiling,it bootlooped. I had twrp installed, so I first restored the backup of stock boot.img, and then installed the recompiled boot.img without rebooting. That worked for me
As you don't have custom recovery, I suggest that you first flash stock boot.img, and after the process completes, flash the recompiled boot.img without rebooting your device.
Click to expand...
Click to collapse
Bro thanks for your advice.. and i did same what you have said.. i flashed stock boot.img with out rebooting flashed recompiled boot.img the device didnt boot up.. i think culprit is something else .. that prevets booting custom images