Related
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?
Update: Now you can download the updater-scripts from Android file host. Zip contains two updater-scripts [updater-script_Z00E-R for ZE500KL/G and updater-script_generic for other variants]
You were running a custom ROM but at some point of time you decided to go back to stock. Unfortunately, you do not have a TWRP backup. Or probably there is an official update but you can't flash the FOTA because you are running a custom ROM. One way of flashingf FOTA would be to flash stock recovery from fastboot and then downgrade to a lower firmware (say the last lollipop fota) and then flash the new update (say MM fota). many a times, update fails at verifying system image! Then you have to do everything again. Maaaaahhhhhhhnnnnnnnnnnn. This is so painful.
Solution? Just by editing the updater script of any ota, you will be able flash it via TWRP. But then you probably don't know what to edit. Moreover, if you edited it incorrectly, you may hard brick your device. So here I have edited updater-scripts for you. Just delete the updater-script from your ota zip and add edited updater-script for your device to the zip. Flash via TWRP recovery. Simple!
INSTRUCTIONS & DOWNLOADS
ZE500KL & ZE500KG
Usage:
Upgrade to MM without reverting to stock lollipop
Downgrade to any stock firmware version
Go back to stock
Recover from failed custom ROM installs
Download updater-script_Z00E-R (link changed to mediafire)
[NOTE: Rename it to "updater-script" ]
A proof that this works is here
All other variants
Edited updater-script for these devices will only flash system and boot. You have to flash last lollipop update and then only you can upgrade to MM
But there's is one benefit of this over other methods. You don't need to find and flash stock recovery!
How?
> Flash last lollipop update that your device was running using the edited updater-script.
> Reboot device and Do all the set up.
> Reboot again but this time INTERRUPT the reboot by holding power button till screen turns off.
> Asus Logo will appear again. Allow Rebooting this time.
> Voila! Your stock recovery is back. You can upgrade to MM now using the regular method.
( All FOTAs contain back up stock recovery but not in .img form. A failed boot causes auto installation of this stock recovery back up)
Other Usage:
Go back to stock
Downgrade to any stock firmware version without affecting bootloader and modem
Recover from failed custom ROM installs
Download link: updater-script_generic (link changed to mediafire)
[NOTE: Rename it to "updater-script"]
Don't forget to hit thanks
Why the can't I make updater-script for these variannts the way I made for ZE500KL/G ?
There are 6 variants (excluding ZE500KL/G) . Each variant has 3 sub variants. Each sub variant comes with upto 4 SKUs.
Every FOTA contains critical firmware files like aboot, hyp, etc of all variants and cross-flashing these would hard brick. Hence, the edited updater-script_generic will only flash system and boot.
.
Thanks man. It would really be helpful.
Hit Thanks If I Helped
sziraqui said:
You were running a custom ROM but at some point of time you decided to go back to stock. Unfortunately, you do not have a TWRP backup. Or probably there is an official update but you can't flash the ota because you are running a custom ROM. One way of flashing ota would be to flash stock recovery from fastboot and then upgrade to a lower firmware (say the last lollipop ota) and then flash the new update (say MM ota)... Maaaaahhhhhhhnnnnnnnnnnn. This is so painful.
Solution? Just by editing the updater script of any ota, you will be able flash it via TWRP. But then you probably don't know what to edit. So here I have edited updater-scripts for you. Just delete the updater-script from your ota zip and add edited updater-script for your device and android version to the zip. Flash via TWRP recovery. Simple!
DOWNLOAD LINK
Choose correct updater-script accorind to filename suffix
Z00L-T_MM = ZE550KL, ZE551KL, ZE601KL, ZE550KG, ZD551KL for Marshmallow OTAs
Z00L-T_LP = ZE550KL, ZE551KL, ZE601KL, ZE550KG, ZD551KL for Lollipop OTAs
Z00E-R_MM = ZE500KL, ZE500KG for Marshmallow OTA
Z00E-R_LP = ZE500KL, ZE500KG for Lollipop OTA
Rename file to "updater-script" before adding to zip.
Click to expand...
Click to collapse
Just no, it will cause many devices to flash wrong firmware leading to non working display and/or modem
TWRP label the device Z00T or Z00L unlike asus that for every variant ( ZE/ZD 550/551/600/601 ) they label it in a different way
This label is checked by the updater-script to flash the proper firmware and modem ( ex, it checks if the display is fhd or hd, check soc msm8929, msm8939, msm8916 )
Ex you have Z00L with the following specs: soc msm8939 && codename ZE600KL -> your script will flash msm8916 firmware and ZE551KL modem probably totally bricking the device
Remove the download links as fast as you can
Device- Z00LD
What I did- unpacked the MM OTA zip via 7zip.
Replaced the MM updater-script from MM OTA.
Repacked it.
Wiped everything through TWRP prior flashing it.
(Was on stock latest LP)
Flashed it.
But, while flashing was in process, it ended up with following line-
Updater process ended with signal: 11.
Overall, it simply didn't work
Hit Thanks If I Helped
sziraqui said:
You were running a custom ROM but at some point of time you decided to go back to stock. Unfortunately, you do not have a TWRP backup. Or probably there is an official update but you can't flash the ota because you are running a custom ROM. One way of flashing ota would be to flash stock recovery from fastboot and then upgrade to a lower firmware (say the last lollipop ota) and then flash the new update (say MM ota)... Maaaaahhhhhhhnnnnnnnnnnn. This is so painful.
Solution? Just by editing the updater script of any ota, you will be able flash it via TWRP. But then you probably don't know what to edit. So here I have edited updater-scripts for you. Just delete the updater-script from your ota zip and add edited updater-script for your device and android version to the zip. Flash via TWRP recovery. Simple!
DOWNLOAD LINK
Choose correct updater-script accorind to filename suffix
Z00L-T_MM = ZE550KL, ZE551KL, ZE601KL, ZE550KG, ZD551KL for Marshmallow OTAs
Z00L-T_LP = ZE550KL, ZE551KL, ZE601KL, ZE550KG, ZD551KL for Lollipop OTAs
Z00E-R_MM = ZE500KL, ZE500KG for Marshmallow OTA
Z00E-R_LP = ZE500KL, ZE500KG for Lollipop OTA
Rename file to "updater-script" before adding to zip.
Click to expand...
Click to collapse
The first line in the original updater-script check if you have the required firmware to install the new one. If you flash on the wrong firmware your device will break your phone. When you update from LL to MM the zip needs to flash the new "firmware-update" No?
luca020400 said:
Just no, it will cause many devices to flash wrong firmware leading to non working display and/or modem
TWRP label the device Z00T or Z00L unlike asus that for every variant ( ZE/ZD 550/551/600/601 ) they label it in a different way
This label is checked by the updater-script to flash the proper firmware and modem ( ex, it checks if the display is fhd or hd, check soc msm8929, msm8939, msm8916 )
Ex you have Z00L with the following specs: soc msm8939 && codename ZE600KL -> your script will flash msm8916 firmware and ZE551KL modem probably totally bricking the device
Remove the download links as fast as you can
Click to expand...
Click to collapse
Well, just to check if it works, I flashed RR ROM and then Flashed Stock MM ota with edited updater-script. My phone booted up without any problem (ASUS_Z00L_63)
I know, custom ROMs label our devices differently. On RR, there was not ro.product.device=, line/ The updater -scripts will flash firmware-update package only if ro.product.device= is the same as that labeled by asus.. For all variants ro.product.device= have a suffix "ASUS_" which is completely differnt than what is provided by cm/rr/beanstalk and any other custom ROM. Just beacuse I respect you a lot, I am removing download links for now and I will look at all possibilities of brick. If found, i will remove the radio part of the script so that users don't end up flashing incorrect firmware. Thanks
edit: Just forgot to mention, I have modified the updater-script to prevent brick. Its 100% safe now.
sziraqui said:
Well, just to check if it works, I flashed RR ROM and then Flashed Stock MM ota with edited updater-script. My phone booted up without any problem (ASUS_Z00L_63)
I know, custom ROMs label our devices differently. On RR, there was not ro.product.device=, line/ The updater -scripts will flash firmware-update package only if ro.product.device= is the same as that labeled by asus.. For all variants ro.product.device= have a suffix "ASUS_" which is completely differnt than what is provided by cm/rr/beanstalk and any other custom ROM. Just beacuse I respect you a lot, I am removing download links for now and I will look at all possibilities of brick. If found, i will remove the radio part of the script so that users don't end up flashing incorrect firmware. Thanks
Click to expand...
Click to collapse
Modem is the easiest problem to fix, but if you flash wrong firmware it will be a big problem
Sent from my ASUS_Z00TD using Tapatalk
luca020400 said:
Modem is the easiest problem to fix, but if you flash wrong firmware it will be a big problem
Sent from my ASUS_Z00TD using Tapatalk
Click to expand...
Click to collapse
By "radio" I meant lines of the script below "radio works" line. In short, removing entire firmware package update part of the script, so that it only flashes system and boot. But then this will it be only for those who want to revert to a stock firmware version that was flashes on their device at some point in time. Still useful
I think that the ideea is not bad. But sure, some checks should be in place.
I had to go back to stock several times just to get the latest baseband. It would be easier to flash the stock via TWRP - instead of flashing the factory recovery, factory firmware and then fastboot to go back to TWRP.
Would also help if we could get the newest baseband some other way - (like form OP links).
SoNic67 said:
I think that the ideea is not bad. But sure, some checks should be in place.
I had to go back to stock several times just to get the latest baseband. It would be easier to flash the stock via TWRP - instead of flashing the factory recovery, factory firmware and then fastboot to go back to TWRP.
Would also help if we could get the newest baseband some other way - (like form OP links).
Click to expand...
Click to collapse
Look at my signature, I have made a thread which has TWRP flashable baseband for all variants
Thank you for your Script
I have ZD551KL
I updated script file as you mentioned to Last LP OTA
i flashed updated zip file with twrp
more than 30 min its still on " patching system image unconditionally......"
Previously i installed RR Rom, and i try to revert to stock its not installing, so try to your method,
Kindly advice me to solve it.
Thank you.
Pretty useful. Thanks
You can also flash the files from CM13 then do the generic update script without going back to LP. That's what I did with mine.
Posted using a calculator and delayed by AT&T.
Not to be stupid but what and how do I use the updater script generic?
corybucher said:
Not to be stupid but what and how do I use the updater script generic?
Click to expand...
Click to collapse
Replace the same file in the stock update file that you downloaded from Asus or any other source.
Posted using a calculator and delayed by AT&T.
Hello, I don't understand, is the "stock recovery" the ROM zip file from the official website ? If so I don't find any updater-script file in it :/ ? Thanks
Edit : I finally find it in google folder, but still not working with TWRP when I try ton install, it says Zip file is corrupted :/
Can anybody give me an OTA stock ROM which is working with this ? I tried with 2 ota, replacing the system file, each time I got an error in TWRP saying can't find update-binary in the zip file :/
I'm using this ROM today [ROM][6.0.1] Smoothified Stock ROM [ALL VARIANTS] http://forum.xda-developers.com/zenfone-2-laser/development/rom-smoothified-stock-rom-t3404050
And wanna go back to an official one, please, thanks
Bibi86 said:
Can anybody give me an OTA stock ROM which is working with this ? I tried with 2 ota, replacing the system file, each time I got an error in TWRP saying can't find update-binary in the zip file :/
I'm using this ROM today [ROM][6.0.1] Smoothified Stock ROM [ALL VARIANTS] http://forum.xda-developers.com/zenfone-2-laser/development/rom-smoothified-stock-rom-t3404050
And wanna go back to an official one, please, thanks
Click to expand...
Click to collapse
Just download the OTA from asus website. Replace the update script. Then flash it.
Posted using a calculator and delayed by AT&T.
Thank you, but I already tried this, doesn't work for me :/ I can't access the recovery anymore (volume down+power on) so I've tried to flash it using twrp but it's not working :/
Can you give me a link for official ota please, thanks
sziraqui said:
You were running a custom ROM but at some point of time you decided to go back to stock. Unfortunately, you do not have a TWRP backup. Or probably there is an official update but you can't flash the FOTA because you are running a custom ROM. One way of flashingf FOTA would be to flash stock recovery from fastboot and then downgrade to a lower firmware (say the last lollipop fota) and then flash the new update (say MM fota). many a times, update fails at verifying system image! Then you have to do everything again. Maaaaahhhhhhhnnnnnnnnnnn. This is so painful.
Solution? Just by editing the updater script of any ota, you will be able flash it via TWRP. But then you probably don't know what to edit. Moreover, if you edited it incorrectly, you may hard brick your device. So here I have edited updater-scripts for you. Just delete the updater-script from your ota zip and add edited updater-script for your device to the zip. Flash via TWRP recovery. Simple!
INSTRUCTIONS & DOWNLOADS
ZE500KL & ZE500KG
Usage:
Upgrade to MM without reverting to stock lollipop
Downgrade to any stock firmware version
Go back to stock
Recover from failed custom ROM installs
Download updater-script_Z00E-R
[NOTE: Rename it to "updater-script" ]
A proof that this works is here
All other variants
Edited updater-script for these devices will only flash system and boot. You have to flash last lollipop update and then only you can upgrade to MM
But there's is one benefit of this over other methods. You don't need to find and flash stock recovery!
How?
> Flash last lollipop update that your device was running using the edited updater-script.
> Reboot device and Do all the set up.
> Reboot again but this time INTERRUPT the reboot by holding power button till screen turns off.
> Asus Logo will appear again. Allow Rebooting this time.
> Voila! Your stock recovery is back. You can upgrade to MM now using the regular method.
( All FOTAs contain back up stock recovery but not in .img form. A failed boot causes auto installation of this stock recovery back up)
Other Usage:
Go back to stock
Downgrade to any stock firmware version without affecting bootloader and modem
Recover from failed custom ROM installs
Download link: updater-script_generic
[NOTE: Rename it to "updater-script"]
Don't forget to hit thanks
Why the can't I make updater-script for these variannts the way I made for ZE500KL/G ?
There are 6 variants (excluding ZE500KL/G) . Each variant has 3 sub variants. Each sub variant comes with upto 4 SKUs.
Every FOTA contains critical firmware files like aboot, hyp, etc of all variants and cross-flashing these would hard brick. Hence, the edited updater-script_generic will only flash system and boot.
.
Click to expand...
Click to collapse
hello.
my phone is asus zenfone 2 laser ze500kl
i have removed OS by mistake. now TWRP says no OS found. my bootloader is not unlocked and i have perfect running TWRP.
when i flashed stock rom it was showing this error. This is for WW phones. this phone is asus zooed
when i followed your script it successfully flashed but when i reboot i stuck at the asus logo.
did i do the correct process? please help me. i need your help. thanks in advance. waiting for your reply
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
As with my thread related to https://forum.xda-developers.com/nokia-8/help/nokia-8-sudden-restart-occurred-randomly-t3852357
I would like to flash the latest System stock OS (since there is no custom ROM yet) and decided to wipe all. I do have TWRP and all I need is system.img, boot.img or full zip to be flashed in TWRP. Does anyone have the file? Any latest up to September or October is okay if it is out there. If anyone does have it, may I request Google drive File sharing since that's the fastest file host that I can download. If there is no one have it, I will just take the obsolete one. However, I won't know if it will solve the problem.
Thank you.
Nokia 8 have more version . 1052,1004,1012...
-In version 1052 . so congratulations u have a f**king phone. The phone can't use ost tool or boot to edl mode
-There nothing rom or zip flash via twrp . only firmware flash via ost tool and ntool.
- If ur phone brick, for easily try ntool.
If u want a hard way, alrealdy have. There is a link of firmware nokia file nbo https://drive.google.com/drive/mobile/folders/1t64iHuQQjmMnzcujZtjYplh6ipbiF6Cw?usp=sharing
.
.
Then use https://www.google.com.vn/amp/s/for...eneral/nb0-unpacker-packer-tool-t3699464/amp/ for extract file nbo then u can flash system.img in this... But remember dont flash boot will break ur wifi.. However i find a way to make this worrking again ... But i dont sure my tutorial work or not although my phone save wifi again...
ValKyre said:
Nokia 8 have more version . 1052,1004,1012...
-In version 1052 . so congratulations u have a f**king phone. The phone can't use ost tool or boot to edl mode
My bad, I haven't told the phone version. It is TA-1004
-There nothing rom or zip flash via twrp . only firmware flash via ost tool and ntool.
Uh, there is a TWRP already which we can flash the system.img and boot.img or we can use fastboot to flash them.
- If ur phone brick, for easily try ntool.
Ntool is the least thing I want to do cause of many errors.
If u want a hard way, alrealdy have. There is a link of firmware nokia file nbo https://drive.google.com/drive/mobile/folders/1t64iHuQQjmMnzcujZtjYplh6ipbiF6Cw?usp=sharing
.
.
Then use https://www.google.com.vn/amp/s/for...eneral/nb0-unpacker-packer-tool-t3699464/amp/ for extract file nbo then u can flash system.img in this... But remember dont flash boot will break ur wifi.. However i find a way to make this worrking again ... But i dont sure my tutorial work or not although my phone save wifi again...
Click to expand...
Click to collapse
I already have that file. I need the latest October Patch 2018 System.img and boot.img. Anyone has it?
Hi everyone!
I think I managed to brick it... Can it be recovered from this?
Model Alcatel 1SE 5030D
Idea was to get it rooted...
I managed to finally unlock the bootloader.
I unpacked the official rom with SPD Tool and then patched the boot.img with magisk in order to flash it with fastboot.
Once this done, phone rebooted and is stuck at the very beginning.
It goes no further than the screen with alcatel logo and powered by android with the message of "lock flag unlocked" at the top left.
Cannot reboot to recovery or fastboot.
Cannot be recognized by windows or linux.
Thank you in advance.
the boot.img is embedded to the rom, sometimes as a payload.bin or an encrypted file (Inside a scatter file) , usually located in /dev/mtd/ or /system/bin , and so on .
To READ the encrypted Boot.Img from the Rom you actually need to read The SCATTER FILE, SPD TOOL, or SP Flashtools are the tools that help you -- LOAD THE ROM and read the scatter file. You could open a whole rom on your own and browse the files inside and you will never find the boot.img , you have to open the rom as a scatter file, as far as i know.
With root you can actually extract the boot.img file if you know the location of it for example:
dd if=/dev/mtd/mtd2 of=/sdcard/boot.img
or
dd if=/dev/block/***** of=/sdcard/boot.img
_____
The problem with these devices is that they dont accept flashing anything into it besides system.img
To allow to flash recovery.img or boot.img , you'll have to input special codes with a special software from the Alcatel Company (we don't have those, cuz they're not leaked)
What you did was trigger a lock, a block to the phone by trying to bypass that security code they placed onto the device.
You took the boot.img out, patched, and then placed back inside/reflashed it as an individual file, with spd tool or adb, if you did with a flashing tool then, this triggered the security of the phone, and maybe other img's got patched and flashed too (or corrupted) such as recovery.img, boot.img, vendor.img , product.img , etc etc, (these are all just regions of the ROM read through the scatter file) ( i guess this locked ur device)
Repairing it :
1) IF YOU can still access into fastboot mode (bootloader) somehow.
** I think just reflashing a new ARM ROM compatible with ur storage partitioning can fix it
(A only or AB )
(try booting the phone and then connecting it to the usb cable , to the pc, and doing
command: fastboot reboot bootloader
or fastboot devices
if you're lucky and its detected , or goes into bootloader you can just do fastboot flash systyem /name/of/rom.img
and this could flash a new rom and revert the boot.img, recovery and everything else to default
thus helping you boot ur phone again.
2) If you can't even access recovery or bootloader (fastboot mode)
** What i think you have to do to repair it is the following, REFLASH the full rom again onto the phone with sp-flash tool
GET the UNPATCHED Boot.img (i hope you made a backup of it), get the whole intact rom, (or any other compatible working rom) the scatter file intact and reflash the WHOLE full rom back again with SP FLASH TOOL
(forget about Placing the PATCHED boot.img in the scatter file) we wanna use the unpatched files, all virgin.
SP FLASH TOOL gives you an option to reflash A WHOLE ROM, i suggest to try reflashing the stock ROM (considering its good) or Reflash another Android ARM AOSP ROM, you can find plenty here in XDA, i can give you links (make sure to HAVE A GOOD ROM this could also be the reason your phone got corrupted, the boot img and files you were handling were probably already corrupted or flashing them simply broke the security code thats about it) that is why you want a ROM that is known, and good for any phone/tablet, preferrably with the same chip as yours or with enough reviews or comments from others, 90% of the roms we can find in google have viruses or are corrupted, specially considering its ALCATEL no one handles this, AND WE ALWAYS WANT TO MAKE SURE OUR PHONE ACCEPTS recovery.img, boot.img , etc without trigering any security codes, if you extracted your own ROM/stock firmware then its alright, thats fine. but you forgot about the security codes, you triggered those i think. Make sure that scatter file loads into SPFT without error, SPFT checks the PRELOADER and DSP_BL and if they aren't in the scatter directory, it will fail and maybe crash. the regions/files can get corrupted. Everything is in green, everything is setup, then you can click " Flash whole rom " this is what you need i think that way you revert everything to default , Boot.img, recovery.img all of it that got locked (you triggered the security code, i think so, because if it wasn't so , it would just boot loop, since yours boot loops and then WARNS you, it means you triggered some code or corrupted something)
3rd option return that Alcatel Toaster, to the company and pay them to repair it , cuz they have the softwares to do all this in just a few clicks.
The issue is the company, they suck hard, and all phones they make are low quality phones .