Related
Hello Everyone,
Thank you in advance for any help on this item.
I have an HTC Sensation phone which is already S-off and has CWM in it.
It also has "su" previleges in it and I was able to modify CID too.
The ROM inside it is stock ROM.
I have been reading and following several guides on how to modify default.prop for other devices. And from what I gather I have to do the following :
1. Unpack boot.img.
2. Modify default.prop.
3. And repack boot.img.
The problem here is that I tried all sorts of things only to end up failing in the "repacking" stage.
I want to modify default.prop to be able to set adb daemon (adbd) to have root previleges and eventually be able to "inject" into HTC sensation my own custom-made versions of framework.jar and other files.
Is modifying default.prop possible?
Is the method I am using correct?
Is it possible to have my own customized framework.jar inside the HTC Sensation?
I hope you guys can point me to some sites and links which can help me in what I intend to do.
Thank you all very much.
Use dsixda kitchen.
Hello Sebastian,
Thanks for your response.
I also tried to use the dsixda kitchen.
What I did was :
1. Downloaded a backup of my phone using ClockworkMod Recovery.
2. I took the boot.img file from the backup generated.
3. Unpacked boot.img using the kitchen.
4. And then repacked it using the kitchen again.
5. I then flashed the generated boot.img into the phone.
6. The phone went into a forever loop in the start up screen.
Did I do it right?
I am rechecking the notes on the kitchen again though. I might have missed something.
Thanks again.
Upload your boot.img, I'll check it. Do you use fastboot.exe to flash boot?
Hello Again,
Thanks once again for the support Sebastian.
"Upload your boot.img, I'll check it. Do you use fastboot.exe to flash boot?"
I use fastboot.exe first and then try to use the ClockworkMod Recovery Advanced option to update the "boot" only part.
I am attaching here my dsixda-kitchen generated boot.img.
This boot .img was generated with the following steps :
1. Unpack htc stock rom boot.img generated by CWM nandroid backup.
2. No changes were made in the ramdisk nor in the kernel part.
3. Repack the ramdisk and kernel using dsixda kitchen.
4. Used fastboot.exe to flash the boot part. "fastboot flash boot boot.img"
5. Wiped the cache partition of the phone.
6. Wiped the /data/dalvik-cache directory.
7. Restarted phone in normal mode.
8. Phone hanged up in startup image.
Many thanks again and more power.
Hello all,
I really need, for a commercial project, to flash a great number (>100) of Galaxy Camera 2 (EK-GC200() device, all with the same firmware, rooted and modified as I need.
I have to flash boot.img (modified by me) and system.img (rooted).
I have now to root the camera, then start the system, enable developer options, enable adb debug and at the end flash a new boot.img, and the system.img itself (adb shell, dd ...).
This is time consuming, and error prone.
I'm sure the boot.img & system.img are correct, cause I can flash them without error (and they work fine) with dd from the internal emulated sdcard.
I can see two viable alternatives:
1. A custom recovery, from where I could make a nandroid backup, which I can use later on to update all the rest of the cameras.
But:
I tried to port the EK-GC100 cwm recovery, I've been able to boot it up, but the touchscreen is unusable and I got a lot of error coming from the file system.
Please help me! Any suggestion, half project, everything is really appreciated!
2. To create an Odin package, using the .img files I can optain with dd from a ready camera.
But:
I tried all I can do to build a Odin package, but every time I got an error (Odin Fail) when I try to flash system.img.
I tried to build a package containing recovery.img + boot.img, and that works.
I tried to build a package containing only system.img, and it doesn't work, every time I got a Fail from Odin.
I tried manual compression (tar + md5sum on Linux), and automated scripts you can find on XDA, both under Linux and Windows.
Why is system.img impossible to flash?
What am I missing?
Thank you in advance.
Ciao,
Giovanni
Code:
[CENTER][COLOR="Red"]Your warranty is now void.[/COLOR]
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 before asking help and reporting bugs and please read the entire OP.
YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
A lot.[/CENTER]
All suggestions and helps are welcome here so please help me in improving this thread by suggesting your ideas.
This guide will work for any SPRD phone (any SPRD chip) from Old versions of android to latest Oreo but recoveries that I provided in this thread will work for devices from KitKat to Marshmallow no guarantees for older or newer versions.
Buckup! Backup! Backup!
Before modifying system it's highly recommended to have full dump of your device. So don't forget to take backup.
It's simple to get custom recovery for rooted users as they can directly backup, modify and flash recovery or boot images on the go with the help of root. But non-rooted users need to do some extra which will be explained later. Follow the below steps:
=>Download and setup AIK (Android Image Kitchen)
=>Grab your stock_recovery.img
For rooted usersInstall Flashify, Rashr, Partitions Backup or like apps (available on play store for free) and backup the stock recovery. If you are using Flashify to backup you have to rename the backed up image with .img extention
For non-rooted usersDownload your stock firmware which will be in .pac extension extract it using this guide and copy the recovery.img
=>Now download custom recovery (for downloads see 2nd post)
=>Port recovery
For PC version of AIK
• Extract the AIK on desktop in a folder (extracting inside other folder(s) is not recommended)
• Place stock_recovery.img (use the name recovery.img only I added stock to refer the image) in earlier extracted folder
• Now double click on 'unpacking.bat'
• Now you'll see two folders 'ramdisk (mostly executables)' and 'split-img (kernel to boot recovery) rename those folders like this 'ramdisk.s' and 'split_img.s' (renaming is used to avoid copying/moving needed files)
• Now delete the earlier pasted stock_recovery.img and paste custom_recovery.img (rename it to recovery.img)
• Unpack it just like stock_recovery
• Delete the split-img and rename the 'split_img.s' to split_img
• Open recovery.fstab from /ramdisk.s/etc (stock recovery's fstab) and /ramdisk/etc (custom recovery's fstab) using Notepad++ or with your favorite note editor. In case of TWRP recovery this file will be named as twrp.fstab if there is recovery. fstab you can ignore it.
• Edit the partition names and mount points in custom recovery with your stock recovery's fstab. But in most cases the mount points will be shown like this 'mmclbk0p17 for system partition' in that case you need to change custom recovery.fstab with the mount points of your device, to find out mount points of partitions install Diskinfo from play store and enable all options in it which will show complete information regarding each and every partition on your device
• At last double click on 'repackimg.bat' now you'll see 'image-new.img' which is ported custom_recovery.img for your device
• The final step is flashing the recovery. It's easy for rooted users simply use Flashify app to flash. For non-Root users you need to flash it over fastboot mode for this look at this thread.
For mobile version of AIK
You can also port the recovery on-the-go using AIK-Mobile unfortunately to use this needs your device must be rooted with BusyBox (Stephen (stericson) is recommended) installed.
It's a flashable zip but you can extract the zip and place the files manually. Follow below steps for setup:
• Extract the AIK-Mobile.zip
• Paste the AIK-Mobile folder under data/local of extracted zip to /data/local
• Paste files under /bin of extracted zip to /data/local/AIK-Mobile/bin
• Make sure all files including folders are having these permissions "-rwrx-xr-x-".
For placing files, changing permissions and executing scripts 'Explorer' by speed software is recommended.
For porting follow above steps (steps in PC version of AIK) the only difference here is .bat files of PC version will be as .sh in mobile version which are to be executed as root for unpacking and repackaging images.
Note:Follow the instructions properly, don't quote entire OP while asking for help. Due to some touch related drivers missing in kernel of recovery in some devices touch recovery won't work in that case please use Non-Touch recovery. In lollipop or later versions don't flash <3.x.x versions which may result in SD card mounting issues and even flashing errors. First test the recovery that you ported by flash a simple mode (I prefer AIK-Mobile since it doesn't modify the system partition hence there is not chance of bootloop. Also see whether wipe options works properly or not in some devices wiping (even cache) takes ~10m in that case goto settings check the option "use rm -rf instead of formatting".
Hit thanks button instead of posting thanks it'll boost me to create more threads like this.
Credits:
Advan S4P [Official] (fb group), SuDroid Tech (fb group), @@ki , @Jitheshwar (it's me), and some aliens from other universe.
Created: 27-09-2017
Last Updated: 27-09-2017
Custom recovery downloads
1) TWRP recovery images
2.7.0-0
2.8.5-0
2.8.5-0
3.0.0-0
3.0.2-0
3.0.2-0
3.0.2-0
3.1.1-0
2)Cyanogen recovery (for lollipop)
3)Cyanogen recovery (for kikat)
4)MIUI recovery
5)Ultra CWM
6)Temporary CWM (only for KitKat and older
7)Temporary Philz (only for KitKat and older)
Temporary recoveries provided here are not for porting. You can flash those zips directly from you stock recovery these recoveries will have basic functions like flashing ROMs, Wiping (in some devices it'll take too long to wipe so just use factory reset option of stock recovery and then flash this recovery finally the ROM. Back up option of recovery might not be fully functional. Scrolling is glitchy but it'll work when you press button. These are more for users who are unable get working recovery
Reserved for FAQ.
Do you know how to port boot to help twrp recovery mode boot up ? Please guide me.
Boot Secure & twrp
Jitheshwar said:
Click to expand...
Click to collapse
I have fpt x50 , vn phone , which runs android 7.0 with sc7731c
Will this guide work ??
Jitheshwar said:
..
Click to expand...
Click to collapse
Sir...
you wrote that delete only split_img.s.....
but not ramdisk.s.......
Is there any problem will arise when repacking with ramdisk.s with ramdisk and split_img of custom recovery?
HemanthJabalpuri said:
Sir...
you wrote that delete only split_img.s.....
but not ramdisk.s.......
Is there any problem will arise when repacking with ramdisk.s with ramdisk and split_img of custom recovery?
Click to expand...
Click to collapse
Read again carefully you have to pack custom recoveries ramdisk with stock split_img and reversing the process will mess up the recovery and then you have to flash the stock recovery. So read the guide carefully step-by-step and follow the process exactly unless you know different working method.
unknown said:
I have fpt x50 , vn phone , which runs android 7.0 with sc7731c
Will this guide work ??
Click to expand...
Click to collapse
Give it a try it may work. But none of the recoveries that are provided here will work for your device, you need to find Android 7.0 and later recoveries which will be compatible with your chipset model.
kaew158 said:
Do you know how to port boot to help twrp recovery mode boot up ? Please guide me.
Boot Secure & twrp
Click to expand...
Click to collapse
TWRP has nothing to do with boot.img. If you are not able to boot to recovery try different key combination. Is you messed up recovery too then flash it via fastboot and then flash the stock Rom.
Jitheshwar said:
Click to expand...
Click to collapse
Sir finally the process is to pack
⇛split_img of stock recovery ......
⇛ramdisk of custom recovery you listed by replacing recovery.fstab file
Some doubt are ... from where the recoveries are taken sir?
another one is can i port a custom recovery made for similar device to my device by using these steps?
Thanks for supporting spreadtrum devices....
HemanthJabalpuri said:
Sir finally the process is to pack
⇛ramdisk of recovery you listed by replacing recovery.fstab file
⇛spit_img of stock recovery right......
Some doubt are ... from where the recoveries are taken sir?
another one is can i port a custom recovery made for similar device to my device by using these steps?
Thanks for supporting spreadtrum devices....
Click to expand...
Click to collapse
Kindly go through the entire post carefully, I believe I provided sufficient info that even a newbie can port.
Jitheshwar said:
Kindly go through the entire post carefully, I believe I provided sufficient info that even a newbie can port.
Click to expand...
Click to collapse
Sir I read entire post...
But there is no line that states to delete ramdisk of stock recovery....
Check and add that line sir....
Also process of installing AIK for Mobile changed...
We directly install and use the AIK as all other apps on playstore
HemanthJabalpuri said:
Sir I read entire post...
But there is no line that states to delete ramdisk of stock recovery....
Check and add that line sir....
Also process of installing AIK for Mobile changed...
We directly install and use the AIK as all other apps on playstore
Click to expand...
Click to collapse
I clearly stated all the steps in an easy and simple way. My kind request to you to read the post again. And one more thing if you want to use apk version use it I don't have any issues but don't ask me if anything goes wrong.
i ported twrp 3.2.1 to sc8830 sucessfully but touch is not working , can you help?
where can i find non-touch recovery
I'm using android 5.1
What is specification kernel architecture in this tutorial?. I have HH Advan S50 same with the name of chipset version.I still doubt fo following your tutorial.
denmasgie said:
What is specification kernel architecture in this tutorial?. I have HH Advan S50 same with the name of chipset version.I still doubt fo following your tutorial.
Click to expand...
Click to collapse
This is just some copy&paste guide thath will not work on most bootloader locked spreadtrum OEM phones
Please fix the twrp links!!!
@Vortex said:
This is just some copy&paste guide thath will not work on most bootloader locked spreadtrum OEM phones
Click to expand...
Click to collapse
No custom recovery will work on bootloader locked devices...
denmasgie said:
What is specification kernel architecture in this tutorial?. I have HH Advan S50 same with the name of chipset version.I still doubt fo following your tutorial.
Click to expand...
Click to collapse
Kernel architecture is ARM.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I successfully ported TWRP to Panasonic Eluga Note (MTK6753) after a four day effort. Not a dev here. First time doing this.
<TLDR? skip this>
When I started using android in my HTC HD2, every ROM was pre rooted. I took it for granted.
So I get this cheapo MTK and breaking into it is like banging head against a wall!! I was frustrated with the battery drain: Device never sleeps since the last OTA!
So I learnt SP flash tools and downgraded. ( wiped nvram and created another mess in the process- which is a different story. I solved it)
I could spend this effort and time to stop that pesky "Panasonic" bootaudio too. And that's the first thing I deleted after I booted TWRP, even before rooting.
</TLDR? skipped this>
First things first, enable ADB, enable OEM unlock in developer options, and go to bootloader to unlock it <fastboot oem unlock> THIS WILL WIPE DATA!!
Second thing: Backup nvram.img by sp flash readback and learn how to flash it back (search XDA)- Sometimes you can learn from other's mistakes too! I spent a day and half writing back IMEI and WIFI Mac.
Process (if you don't trust me and want to reproduce the steps yourself)
1. Download stock firmware. (google knows)
2. Patch boot.img so that it doesn't overwrite TWRP with stock recovery on each boot (extract by Carliv Image kitchen and hash out the three lines 663, 664 and 665 mentioning "service flash_recovery /system/bin/install-recovery.sh" in init.rc). I created two copies in the same folder (boot.img, and boot-verified.img) and copied scatter into the same folder for flashing. That's what I saw in the firmware folder.
3. Port TWRP using Carliv Image Kitchen method. I downloaded TWRP from here https://forum.xda-developers.com/android/software/twrp-porter-maker-mediatek-mt67xx-32-t3681861 but didn't use their method. It didn't work. The TWRP for this chip was stated as android N, but worked well.
4. Flash ported TWRP after copying scatter file to the Carliv Imagekitchen output folder and selecting that scatter in SP droid tools. I again created recovery.img and recovery-verified.img. Don't know if its needed that way. You could wait and flash boot and recovery together from the same folder.
5. That's it, you can enter custom recovery now. Get that pesky "panasonic" bootaudio off the system/media folder now! You can stay content after this or proceed to root.
<nandroid backup now, including Nvram and NVdata. Just in case>
6. Download Supersu zip flashable and flash it via TWRP. https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip?retrieve_file=1 worked for me.
7. Reboot, check root!
If you're more daredevil,
8. Download Xposed flashable zip SDK23 and flash it. Download Xposed installer and copy it to SDcard too.
9. Reboot to recovery and flash the zip. Reboot, install xposed installer. Reboot again.
You're done!
I'll upload my boot.img and ported TWRP if anyone shows any interest in this.
Cheers!
(Bonus: this phone has built in IPtables support in the kernel! I used to flash custom kernel for this ability in other Stock ROMs. AFfirewall works "out of the box"- after rooting, of course!)
Edit: uploaded my modded boot.img and ported TWRP. find it here https://drive.google.com/file/d/1sM1BnyBUFN7PfncFcM7vzIet6gKt3G_L/view?usp=sharing
If you want to go the easy route, unzip the folder and flash it with sp flash. You'll be able to boot into recovery and do the other steps for rooting.
Rememer ONLY DOWNLOAD, don't format, or format and download, or anything!
Brilliant Work man. I also was sort of in your situation as well . i have a panasonic Eluga A3 (Qmobile Noir E2) in my country. Stock Qmobile rom was horrendous. so i flashed the panasonic rom but hated the boot audio and the bloatware that came with it. so i decided to make a slimmed down version of it and successfully did it by using superr's kitchen. and also using the kitchen i removed the encryption on the boot.img and then patched it using magisk for easy rooting without recovery. when flashed together with the modded system.img and modded boot.img and twrp, i was totally in control of my device.
If you need any help with anything mtk send me a pm
also are you able to access internal storage in twrp or not ??
andromodgod said:
If you need any help with anything mtk send me a pm
also are you able to access internal storage in twrp or not ??
Click to expand...
Click to collapse
I can access internal storage in twrp. There's a choice to select the internal storage. Havent backed up to it or anything. But its there. I copied a file into it through TWRP now, and it works. I think its all about the fstab. If you don't get access to internal storage, see for any red errors in TWRP output. I can look into my fstab to see what's relevant.
I have a little hiccup though. Now my network drops (both sim at a time), even during a call. But maybe its because I swapped sim 1 and sim 2. I'll let things settle and see if it will persist. In the meanwhile, I swapped sims back to original.
bad.bid said:
I can access internal storage in twrp. There's a choice to select the internal storage. Havent backed up to it or anything. But its there. I copied a file into it through TWRP now, and it works. I think its all about the fstab. If you don't get access to internal storage, see for any red errors in TWRP output. I can look into my fstab to see what's relevant.
I have a little hiccup though. Now my network drops (both sim at a time), even during a call. But maybe its because I swapped sim 1 and sim 2. I'll let things settle and see if it will persist. In the meanwhile, I swapped sims back to original.
Click to expand...
Click to collapse
i wasn't able to access internal storage at first because device was encrypted beforehand. also sim issues might be caused by imei/nvram . check if your device imei matches your imei on the device box.
andromodgod said:
i wasn't able to access internal storage at first because device was encrypted beforehand. also sim issues might be caused by imei/nvram . check if your device imei matches your imei on the device box.
Click to expand...
Click to collapse
Ya, I fixed Imei issues. this one is like a signal drop once every 15 minutes.
bad.bid said:
I successfully ported TWRP to Panasonic Eluga Note (MTK6753) after a four day effort. Not a dev here. First time doing this.
<TLDR? skip this>
When I started using android in my HTC HD2, every ROM was pre rooted. I took it for granted.
So I get this cheapo MTK and breaking into it is like banging head against a wall!! I was frustrated with the battery drain: Device never sleeps since the last OTA!
So I learnt SP flash tools and downgraded. ( wiped nvram and created another mess in the process- which is a different story. I solved it)
I could spend this effort and time to stop that pesky "Panasonic" bootaudio too. And that's the first thing I deleted after I booted TWRP, even before rooting.
</TLDR? skipped this>
First things first, enable ADB, enable OEM unlock in developer options, and go to bootloader to unlock it <fastboot oem unlock> THIS WILL WIPE DATA!!
Second thing: Backup nvram.img by sp flash readback and learn how to flash it back (search XDA)- Sometimes you can learn from other's mistakes too! I spent a day and half writing back IMEI and WIFI Mac.
Process (if you don't trust me and want to reproduce the steps yourself)
1. Download stock firmware. (google knows)
2. Patch boot.img so that it doesn't overwrite TWRP with stock recovery on each boot (extract by Carliv Image kitchen and hash out the three lines 663, 664 and 665 mentioning "service flash_recovery /system/bin/install-recovery.sh" in init.rc). I created two copies in the same folder (boot.img, and boot-verified.img) and copied scatter into the same folder for flashing. That's what I saw in the firmware folder.
3. Port TWRP using Carliv Image Kitchen method. I downloaded TWRP from here https://forum.xda-developers.com/android/software/twrp-porter-maker-mediatek-mt67xx-32-t3681861 but didn't use their method. It didn't work. The TWRP for this chip was stated as android N, but worked well.
4. Flash ported TWRP after copying scatter file to the Carliv Imagekitchen output folder and selecting that scatter in SP droid tools. I again created recovery.img and recovery-verified.img. Don't know if its needed that way. You could wait and flash boot and recovery together from the same folder.
5. That's it, you can enter custom recovery now. Get that pesky "panasonic" bootaudio off the system/media folder now! You can stay content after this or proceed to root.
<nandroid backup now, including Nvram and NVdata. Just in case>
6. Download Supersu zip flashable and flash it via TWRP. https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip?retrieve_file=1 worked for me.
7. Reboot, check root!
If you're more daredevil,
8. Download Xposed flashable zip SDK23 and flash it. Download Xposed installer and copy it to SDcard too.
9. Reboot to recovery and flash the zip. Reboot, install xposed installer. Reboot again.
You're done!
I'll upload my boot.img and ported TWRP if anyone shows any interest in this.
Cheers!
(Bonus: this phone has built in IPtables support in the kernel! I used to flash custom kernel for this ability in other Stock ROMs. AFfirewall works "out of the box"- after rooting, of course!)
Edit: uploaded my modded boot.img and ported TWRP. find it here https://drive.google.com/file/d/1sM1BnyBUFN7PfncFcM7vzIet6gKt3G_L/view?usp=sharing
If you want to go the easy route, unzip the folder and flash it with sp flash. You'll be able to boot into recovery and do the other steps for rooting.
Rememer ONLY DOWNLOAD, don't format, or format and download, or anything!
Click to expand...
Click to collapse
Can you please mention the steps and software needed for rooting the device plz plz plz
gt612 said:
Can you please mention the steps and software needed for rooting the device plz plz plz
Click to expand...
Click to collapse
No need to quote the whole post!
Download twrp and boot from here. https://drive.google.com/file/d/1sM1BnyBUFN7PfncFcM7vzIet6gKt3G_L/view?usp=sharing
download super su from the link in original post. flash iso files in the twrp boot zip (they are for the updated latest version of android 6.0.1). flash supersu via twrp. search for how to do these things.
Hello. I have an Allveiw V2 Viper S (the romanian version fo the eluga note). I got a stock rom (not from my phone) from where i took and modified both the boot.img and the recovery.img and also used the scatter from here to. I couldn`t make mtk droid tools to see my device. I managed to unlock the bootloader, but when i tried to flash the boot and recovery spft gave me a " Obtain DRAM Faild" error. Can you please help?
Thanks!
madhogg said:
Hello. I have an Allveiw V2 Viper S (the romanian version fo the eluga note). I got a stock rom (not from my phone) from where i took and modified both the boot.img and the recovery.img and also used the scatter from here to. I couldn`t make mtk droid tools to see my device. I managed to unlock the bootloader, but when i tried to flash the boot and recovery spft gave me a " Obtain DRAM Faild" error. Can you please help?
Thanks!
Click to expand...
Click to collapse
This was an impulse project. I learned many things in the way. But I have left that effort behind. So, for now: no idea. Hope google helps!
bad.bid said:
I successfully ported TWRP to Panasonic Eluga Note (MTK6753) after a four day effort. Not a dev here. First time doing this.
<TLDR? skip this>
When I started using android in my HTC HD2, every ROM was pre rooted. I took it for granted.
So I get this cheapo MTK and breaking into it is like banging head against a wall!! I was frustrated with the battery drain: Device never sleeps since the last OTA!
So I learnt SP flash tools and downgraded. ( wiped nvram and created another mess in the process- which is a different story. I solved it)
I could spend this effort and time to stop that pesky "Panasonic" bootaudio too. And that's the first thing I deleted after I booted TWRP, even before rooting.
</TLDR? skipped this>
First things first, enable ADB, enable OEM unlock in developer options, and go to bootloader to unlock it <fastboot oem unlock> THIS WILL WIPE DATA!!
Second thing: Backup nvram.img by sp flash readback and learn how to flash it back (search XDA)- Sometimes you can learn from other's mistakes too! I spent a day and half writing back IMEI and WIFI Mac.
Process (if you don't trust me and want to reproduce the steps yourself)
1. Download stock firmware. (google knows)
2. Patch boot.img so that it doesn't overwrite TWRP with stock recovery on each boot (extract by Carliv Image kitchen and hash out the three lines 663, 664 and 665 mentioning "service flash_recovery /system/bin/install-recovery.sh" in init.rc). I created two copies in the same folder (boot.img, and boot-verified.img) and copied scatter into the same folder for flashing. That's what I saw in the firmware folder.
3. Port TWRP using Carliv Image Kitchen method. I downloaded TWRP from here https://forum.xda-developers.com/android/software/twrp-porter-maker-mediatek-mt67xx-32-t3681861 but didn't use their method. It didn't work. The TWRP for this chip was stated as android N, but worked well.
4. Flash ported TWRP after copying scatter file to the Carliv Imagekitchen output folder and selecting that scatter in SP droid tools. I again created recovery.img and recovery-verified.img. Don't know if its needed that way. You could wait and flash boot and recovery together from the same folder.
5. That's it, you can enter custom recovery now. Get that pesky "panasonic" bootaudio off the system/media folder now! You can stay content after this or proceed to root.
<nandroid backup now, including Nvram and NVdata. Just in case>
6. Download Supersu zip flashable and flash it via TWRP. https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip?retrieve_file=1 worked for me.
7. Reboot, check root!
If you're more daredevil,
8. Download Xposed flashable zip SDK23 and flash it. Download Xposed installer and copy it to SDcard too.
9. Reboot to recovery and flash the zip. Reboot, install xposed installer. Reboot again.
You're done!
I'll upload my boot.img and ported TWRP if anyone shows any interest in this.
Cheers!
(Bonus: this phone has built in IPtables support in the kernel! I used to flash custom kernel for this ability in other Stock ROMs. AFfirewall works "out of the box"- after rooting, of course!)
Edit: uploaded my modded boot.img and ported TWRP. find it here https://drive.google.com/file/d/1sM1BnyBUFN7PfncFcM7vzIet6gKt3G_L/view?usp=sharing
If you want to go the easy route, unzip the folder and flash it with sp flash. You'll be able to boot into recovery and do the other steps for rooting.
Rememer ONLY DOWNLOAD, don't format, or format and download, or anything!
Click to expand...
Click to collapse
Brother i try this method at Panasonic eluga ray 700 (MT6753_EB_90S55ER7_V1008) flash complete and successful install problem my set dead not On so i install original Panasonic eluga ray 700 (MT6753_EB_90S55ER7_V1008) flash set is dead and not connecting to pc plz help me what i can do ......
andromodgod said:
Brilliant Work man. I also was sort of in your situation as well . i have a panasonic Eluga A3 (Qmobile Noir E2) in my country. Stock Qmobile rom was horrendous. so i flashed the panasonic rom but hated the boot audio and the bloatware that came with it. so i decided to make a slimmed down version of it and successfully did it by using superr's kitchen. and also using the kitchen i removed the encryption on the boot.img and then patched it using magisk for easy rooting without recovery. when flashed together with the modded system.img and modded boot.img and twrp, i was totally in control of my device.
If you need any help with anything mtk send me a pm
also are you able to access internal storage in twrp or not ??
Click to expand...
Click to collapse
Panasonic eluga ray 700 (MT6753_EB_90S55ER7_V1008) after flash set is dead and not connecting to pc plz help us expert......
....
Network drop
Hello dear friend I successfully flash twrp 3.0.2 but I see network signal problem signal drop many time..
Pls tell me how to resolve these issue..
Singnal drop
bad.bid said:
Ya, I fixed Imei issues. this one is like a signal drop once every 15 minutes.
Click to expand...
Click to collapse
Dear sir panasonic eluga note network signal drop many time a day after installing ur ported twrp ..Pls tell me how to resolve signal drop issue..
Really wanna do it but your steps sound way complicated for "non-MTK pro guy". I have that device lying unused. it would be awesome if you could throw a "readme" file in your drive or here with simpler guidance steps like other "TWRP & root installation guide" we have for other phones. Plus You seem like you could port/build a ROM for this device and make substratum friendly. I know it's a big ask & I have a feeling that you like dark UI for that device too . Hoping for the best response.
If you're more daredevil,
8. Download Xposed flashable zip SDK23 and flash it. Download Xposed installer and copy it to SDcard too.
9. Reboot to recovery and flash the zip. Reboot, install xposed installer. Reboot again.
I have a doubt about these two steps
Should i have to flash it twice and have to download two separate file which is one flashable zip and installer. And in the next step 9th which zip file should i flash.
My questions might sound silly but i am asking so because when last time i tried i installed xposed, installed its firmware and then downloaded a module it was cynolockscreen something and applied it. It asked ne to reboot i did but then my phone crashed. Screen was going on and off then i rebooted to recovery and did a factory reset amd since then i haven't done any thing in my phone not even flashed the SuperSU...
Can you please help me with the further steps...
rooting eluga note
can u pls tell me how to root eluga note? i've tried many apps to root it but nothing worked
in a guide now removed, whose instructions i will not repeat here, it was documented that a Kiev could be reverted to its stock OS by obtaining img files of recovery, boot, etc. and sparsechunks of the super partition, and then flashing them with fastboot. i really like this approach to wipe and restore the phone to an imaged state.
my question is: would it be possible to convert a TWRP backup of the phone in a custom state to the format used for this? how could i start with this? success here would be for me to create a bash script that converts a TWRP backup folder into a series of fastboot-flashable img files. if i succeed, i wwould be happy to share the results. i just need advice on what would need done to TWRP backups to make them workable with fastboot.
i am about to begin a project involving Kiev, and it would be very useful if i could simply use fastboot to restore my phone to any arbitrary state, as opposed to relying on TWRP.
I guess it'd be possible to create images, format, and extract the backup into them. Save a lot of effort by just dumping the partitions with dd imo.