Develop Bugs

[FTF][STOCK] C6902 - Customized USA - Lollipop 14.5.A.0.242 + [Root&Recovery GUIDE]

[FTF][STOCK] C6902 - Customized USA - Lollipop 14.5.A.0.242 + [Root&Recovery GUIDE]
{
"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 have compiled a CLEAN completely unmodified FTF for C6902.
Yes, it does include all original system languages, as this is the Stock Firmware.
Download
When you install, allow ~5 minutes for first boot to fully install.
For Recovery & Root:
- Boot in flashmode and flash either of these images #1 or #2 (The one I used)
--For #1 use the command
Code:
fastboot flash recovery twrp-z1-2860.img
--For #2 you must extract the boot.img from the .zip and move it alongside the fastboot.exe file
--For #2 use the command
Code:
fastboot flash boot boot.img
- Put this into your SD card.
- Boot into Recovery and wipe cache/dalvik (recommended but optional), and flash SuperSU zip file.
- Do NOT reboot, and then flash [NUT]'s XZDRecovery Flashable ZIP Z1-lockeddualrecovery2.8.12-RELEASE.flashable.zip
- Now reboot, and enjoy root! (Rhyme unintended)

グリッチ said:
I have compiled a CLEAN completely unmodified FTF for C6902.
Yes, it does include all original system languages, as this is the Stock Firmware.
Download
When you install, allow ~5 minutes for first boot to fully install.
For root, you must first install the FTF, then enable USB debugging and install this.
Then when you have finished installing, reboot to recovery and install this.
Click to expand...
Click to collapse
Only for usa??
I have C6902 but indian.

gauravbhakuni90 said:
Only for usa??
I have C6902 but indian.
Click to expand...
Click to collapse
For C6902 all market

How can we root ?? and get recovery :3 :3. Don't work :3

グリッチ said:
I have compiled a CLEAN completely unmodified FTF for C6902.
Yes, it does include all original system languages, as this is the Stock Firmware.
Download
When you install, allow ~5 minutes for first boot to fully install.
For root, you must first install the FTF, then enable USB debugging and install a recovery, such as: this or a custom kernel with a recovery, etc.
Then when you have finished installing, reboot to recovery and install SuperSU this.
Click to expand...
Click to collapse
Thank you so much kind sir! Many appreciations

Rooting a Funai Philips Android TV

I've got a 65-inch 4K Funai/Philips Android TV. Is this TV rootable or flashable? The OS is so laggy on this device it makes it almost unbearable to use. Opening specific screens takes seconds because of all the quirky animations. I'd much rather prefer flashing a different version of Android TV that doesn't lag any time I scroll to the next app on the home screen.

I have successfully unlocked the bootloader through fastboot. I'm not experienced to go any farther than that though.
Originally,
Code:
fastboot flashing get_unlock_ability
returned "(bootloader) lock"
After running
Code:
fastboot flashing unlock
it appears to unlock bootloader.
It factory resets tv after unlock, and persists through reboots.
{
"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'd love nothing more than to get root working on this TV! Any suggestions on what to do next from people smarter/more experienced than me, throw it out there.

OTA firmware: https://android.googleapis.com/packages/ota-api/package/374df80dffab69614dcb3d2b1f8c689d1ee96e23.zip
System, Vendor, boot, and magisk-patched boot .img files https://mega.nz/folder/MpwB3ISK#0CQFgDQhV2bbTL35XoKycw
So I believe as long as I'm on the OTA firmware that's linked above, I theoretically should be able to achieve root by:
Code:
fastboot flash boot magisk.boot.img

vincentanzalone said:
OTA firmware: https://android.googleapis.com/packages/ota-api/package/374df80dffab69614dcb3d2b1f8c689d1ee96e23.zip
System, Vendor, boot, and magisk-patched boot .img files https://mega.nz/folder/MpwB3ISK#0CQFgDQhV2bbTL35XoKycw
So I believe as long as I'm on the OTA firmware that's linked above, I theoretically should be able to achieve root by:
Code:
fastboot flash boot magisk.boot.img
Click to expand...
Click to collapse
any idea how i go about grabbing the ota firmware or any firmware for my tv ? it's the phillips walmart 75 inch model, i was able to unlock bootloader but mtk client doesn't work with it, no way to get to brom mode to test. want a proper dump before i start essing with anything. Thanks much

vincentanzalone said:
OTA firmware: https://android.googleapis.com/packages/ota-api/package/374df80dffab69614dcb3d2b1f8c689d1ee96e23.zip
System, Vendor, boot, and magisk-patched boot .img files https://mega.nz/folder/MpwB3ISK#0CQFgDQhV2bbTL35XoKycw
So I believe as long as I'm on the OTA firmware that's linked above, I theoretically should be able to achieve root by:
Code:
fastboot flash boot magisk.boot.img
Click to expand...
Click to collapse
well, I find myself in a soft brick situation. I cannot get the OTA zip to load from USB, do you happen to have the file as it came or is this it ?

[GUIDE] Unlocking Realme 7 5G Bootloader + Root.

DISCLAIMER: I AM NOT RESPONSIBLE FOR ANY DAMAGES TO YOUR DEVICE. PLEASE GO AHEAD WITH CAUTION.
NOTE: This will void your warranty! & Will reset your device!
Hi!
I'm sharing a way to unlock the bootloader of the Realme 7 5G.
Prerequisites:
ADB + Fastboot
Realme 6 In-depth APK (Trust me, It works!)
TWRP if you want to root aswell as a Magisk.zip (rename magisk.apk to magisk.zip)
MTK Drivers
USB Cable, stock is fine.
Ok, once you've gathered all those things, first make sure you have enabled bootloader unlocking and debugging. Then open the in-depth test and start the test.
Now follow the steps:
1. Plug RMX2111 (Realme 7 5g) into PC
2. Run
Rich (BB code):
adb devices
in your terminal to make sure your device is recognized.
3. Run
Rich (BB code):
adb reboot bootloader
to get in the bootloader
4. Optional: run
Rich (BB code):
fastboot devices
to verify your device is fastboot mode.
5. Run
Rich (BB code):
fastboot flashing unlock
to unlock the bootloader (press the volume button to unlock)
Congratulations! You've unlocked the bootloader. Now to root:
1. Grab the required recovery.
2. Boot back into bootloader in step 2.
3. Run
Code:
fastboot --disable-verification flash vbmeta PATH-TO-VBMETA.img
4. Run
Code:
fastboot erase recovery
5. Run
Code:
fastboot flash recovery PATH-TO-RECOVERY.img
6. Once you are in recovery, press 'install' and select the magisk.zip where ever you stored it.
7. Swipe to flash and then reboot.
Now you are rooted!
Hope this works guys! Enjoy!
(someone plz make custom rom for this device)

was this on android 11 & UI version 2?
thnks

z3213v said:
was this on android 11 & UI version 2?
thnks
Click to expand...
Click to collapse
yep

thank you!

ok i have tried this - no luck for me with RealMe 6 In-Depth APK unfortunately
app crashing on wifi connection

z3213v said:
ok i have tried this - no luck for me with RealMe 6 In-Depth APK unfortunately
app crashing on wifi connection
Click to expand...
Click to collapse
sorry to hear that, make sure you have developer tools and select oem unlocking. also try different indepth, and also try turning off wifi.

z3213v said:
was this on android 11 & UI version 2?
thnks
Click to expand...
Click to collapse
Where can I download the necessary in-depth test? Do I need to upgrade to version 11? I have version 10 and it doesn't work for me (https://c.realme.com/in/post-details/1273238614934814720). Thanks!

kromls said:
Where can I download the necessary in-depth test? Do I need to upgrade to version 11? I have version 10 and it doesn't work for me (https://c.realme.com/in/post-details/1273238614934814720). Thanks!
Click to expand...
Click to collapse
i dont really know where i got it from, another method is using mtkclient and unlocking it. Go to the github page of mtkclient to find out.

Hi.. How to fix it.
{
"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"
}

Question help me extract recovery.img

Hello all, I am trying to make a custom recovery for my new phone, the realme gt me rmx3363. However this is my first phone that is A/B partitioned so I don't know what to do fully. I am trying to extract the recovery.img because that is whats needed in order to make a custom recovery. However, when I look into the device firmware the only image files I see are: boot, bootloader, dbto, radio, vbmeta, vbmeta_system and vendor_boot. The system files are all seperated into "sparsechunks".
On a non-A/B device getting the recovery was as easy as downloading the stock firmware, extracting, and then recovery.img was right there. Now it seems to be different and I don't know what to do, I couldn't find anything on google about how to do this. I am sure it is easy enough though. Thank you in advance.
{
"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"
}

NextB said:
Hello all, I am trying to make a custom recovery for my new phone, the realme gt me rmx3363. However this is my first phone that is A/B partitioned so I don't know what to do fully. I am trying to extract the recovery.img because that is whats needed in order to make a custom recovery. However, when I look into the device firmware the only image files I see are: boot, bootloader, dbto, radio, vbmeta, vbmeta_system and vendor_boot. The system files are all seperated into "sparsechunks".
On a non-A/B device getting the recovery was as easy as downloading the stock firmware, extracting, and then recovery.img was right there. Now it seems to be different and I don't know what to do, I couldn't find anything on google about how to do this. I am sure it is easy enough though. Thank you in advance.View attachment 5549789
Click to expand...
Click to collapse
I have the same proble with my tecno camon 17 pro mediatek mt6587 helio g95 on android11. let me know if you find a solution.. thanks

Try
https://github.com/twrpdtgen/twrpdtgen
It says supports Android 12.
"Create a TWRP-compatible device tree only from an Android recovery image (or a boot image if the device uses non-dynamic partitions A/B) of your device's stock ROM It has been confirmed that this script supports images built starting from Android 4.4 up to Android 12"

@NextB Having the exact same issue on my Blackview BV8800.
The recovery partition is nowhere to be seen. Here's an Interesting article mentioning this scenario from the android docs. Basically, it says that the recovery code is shipped in boot_vendor.img !
@retiredtab Pardon me if I do not follow, how can mapping out a device tree help us here?

I have a feeling that this tool might help us get done: https://github.com/cfig/Android_boot_image_editor.
Basically, the flow I am thinking about is:
1. Grab vendor_boot.img unpack with it.
2. Grab twrp.img unpack with it.
3. Replace recovery code in 1 with the one in 2.
4. Repack boot_vendor.img.
5. Flash boot_vendor.img with fastboot.
Now, in my case with a mediatek processor, it's more complicated as I have to "port" twrp first, and to do that, I first need a vanilla recovery.img, so I will have to reconstruct that too at some point.

Just found an interesting method with Carliv Image Kitchen tool, seems very promising, and maybe that it the solution we seek: Here's a video demo'ing the method:
And according to the video above, the recovery code is in boot.img not boot_vendor.img!

Question Fastboot loop - Unable to use MSM - TWRP Lessons Learn't

Hi Peeps,
Further to my issue within thread >> https://forum.xda-developers.com/t/bricked-oneplus9-pro-unlocked-options-for-newbie.4577539
Listed below is how I/we overcame the fastboot constant boot issue. A little background in case someone comes against the same issues.
I bought a OnePlus 9 Pro in the hope to have a degoogled phone. Following the lineageOS instructions I somehow corrupted my device and when issuing Volume Down & Power got stuck in a fastboot loop.
Failed Resolutions:
1/ MSM
Part of the resolutions mentioned usiing the MSM tool (windows only) However in my case, My windows vm only recognised my phone has a Android Phone nothing else. I should also point out it couldn't go into edl(Both volumes+power) either. Probably why not recognised as OnePlus 9 Pro by windows.
{
"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"
}
2/ Fastboot & Extract payload.bin .img files) & Fastboot Enhanced tool
a/ https://droidwin.com/unbrick-oneplus-9-pro-fastboot-commands/
b/ https://forum.xda-developers.com/t/...enhance-payload-dumper-image-flasher.4310553/
Both methods needed to reboot in fastbootd mode unfortunately my phone failed with both methods. Got a message regarding failing to boot into userspace
These methods possible would work if windows could recognise the phone/edl is functional.
(Thanks to @TheGhost1951)
Successful Resolution Below - Big thanks goes to @immortalwon
TWRP Method:
[RECOVERY][3.7.0-12.1][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9 pro, but it was confirmed to work on regular OP9 too. As always I'm not responsible for...
forum.xda-developers.com
Download link: https://drive.google.com/drive/folders/1MXANZupY0c08n3AZsmqmLJ-isbRYev6m Download from the latest folder.
Official Firmware OnePlus 9 Pro Link: https://oxygenos.oneplus.net/OnePlus9ProOxygen_22.E.13_OTA_0130_all_2111112110_8b4d5c8737d04612.zip
Prerequisites:​1/ platform tools installed & path set. (works both on windows/linux) I finished mine on linux due to vm usb issues.
2/ fastboot devices recognises your device,
Initially not entirely sure if this next step was still required or maybe the 2nd option(renaming & moving .img into platform-tools folder) will suffice? maybe someone can advise? I just know it worked for me
1/ Extract zip from above download link to folder.
2/ Issue fastboot boot boot-oos13-firmware.img
After completion my phone had the below options
After clicking reboot & sliding to confirm as advised went into fastboot mode,
Final Successful Method:
1/ Rename file boot-oos13-firmware.img to twrp.img
2/ Place twrp.img inside your platform tools folder.
3/ Now from the command prompt, type this exactly: fastboot boot twrp.img
After completion we had a lot more options within TWRP as below:
1 Now click on advanced, adb sideload and swipe right. If you see options Wipe Dalvik Cache & Wipe Cache DO NOT SELECT!
2/ Move official OnePlus 9 Pro firmware into platform-tools folder & rename to a shorter name, I renamed to twpr.zip
3/ Issue adb sideload twrp.zip (During this stage I moved to my local linux machine as vm wasn't playing nicely with usb.
May see some errors on successful completion.
Upon Reboot Happy Days!
Sorry not really a writer as you can probably tell Thanks for all the guys who assisted me. Happy to report I now have a fully functional LineageOS de-ggogled phone I hope this helps someone in the future. Thanks Daz

Glad you got a functioning phone!