Some files for Leagoo M8 owners:
SuperSU v2.79
http://ul.to/nzjkfpds
Recovery (TWRP & Scatter File)
http://ul.to/sf9ig4yl
MTK Drivers
http://ul.to/crs6xzlz
SP Flash Tool v5.1540.00
http://ul.to/4wv9y3wj
Screen Overlay Fix (to flash)
http://ul.to/vx2lszbz
Xposed (to flash)
http://dl-xda.xposed.info/framework/sdk23/arm/xposed-v87-sdk23-arm.zip
Xposed (App)
https://forum.xda-developers.com/attachment.php?attachmentid=3921508&d=1477916609
Use SP Flash Tool to flash the Recovery (TWRP) and use then TWRP on your phone to flash SuperSu, Xposed and Screen Overlay Fix
Unable to download files
Can you please upload those files here or Dropbox as I am unable to download from that site. Thank you.
donshady28 said:
Can you please upload those files here or Dropbox as I am unable to download from that site. Thank you.
Click to expand...
Click to collapse
Sorry, too large for XDA. Use Uploaded free user Download. Should work for everyone
Scatter file Missing
After downloading the Recovery Twrp I can't find scatter file. Kindly upload the scatter file. Thank you.
donshady28 said:
After downloading the Recovery Twrp I can't find scatter file. Kindly upload the scatter file. Thank you.
Click to expand...
Click to collapse
Scatter file is inside the TWRP.rar file.
MT6580_Android_scatter.txt
Can anyone confirm that TWRP is fully working? sd card, backups, etc all working?
stephendt0 said:
Can anyone confirm that TWRP is fully working? sd card, backups, etc all working?
Click to expand...
Click to collapse
Yes, it works.
I used it to flash SuperSu and Xposed. :good:
Thanks for confirming it works!!!
SomeOneX said:
Yes, it works.
I used it to flash SuperSu and Xposed. :good:
Click to expand...
Click to collapse
Excellent. Are you able to restore backups? This is something important for me
I'm unable to download the scatter file.
SomeOneX said:
Scatter file is inside the TWRP.rar file.
MT6580_Android_scatter.txt
Click to expand...
Click to collapse
I'm unable to download the scatter file. Can anyone send the scatter file to my mail.
[email protected] Thank you.
donshady28 said:
I'm unable to download the scatter file. Can anyone send the scatter file to my mail.
[email protected] Thank you.
Click to expand...
Click to collapse
{
"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"
}
stephendt0 said:
Excellent. Are you able to restore backups? This is something important for me
Click to expand...
Click to collapse
I used only TitaniumBackup.
SomeOneX said:
I used only TitaniumBackup.
Click to expand...
Click to collapse
OK, I'd like to try Xposed and a few other mods but I'd hate to not be able to restore to stock ROM if backup and restore doesn't work properly (which I've seen a couple of times on MTK devices)
Update! TWRP works well, even backup and restore seems OK. Now to make a debloated ROM :good:
PS: Can someone explain the Overlay fix? I'm not sure exactly what this is supposed to resolve. I am using the 20161213 ROM.
After flashing the TWRP, tried to reboot to recovery but not working. How do I boot into recovery.????
I tried it in 20161213rom and 20170116 ROM!
donshady28 said:
After flashing the TWRP, tried to reboot to recovery but not working. How do I boot into recovery.????
I tried it in 20161213rom and 20170116 ROM!
Click to expand...
Click to collapse
What do you get when you turn your phone off and hold VOL UP + Power? Once I select "recovery" then it shows the Leagoo logo for a moment then boots right in.
When I turn the phone off, I hold the vol + and power and I get recovery, fastboot and reboot. I select the recovery using the vol down. But its keeps showing Leagoo logo
Okay. For whatever reason, it hasn't flashed the recovery properly - it sounds like it's missing. If you have the stock recovery, it shows the Leagoo logo for a moment, then shows the Freeme logo only (no text, just a logo). With TWRP it takes around 2-3 seconds for it to come up. It sounds to me that something went wrong when you tried to flash TWRP. What version of SPFlashTools are you using? Are you sure the right drivers are installed? Perhaps try another computer and USB cable and try with SPFlashTool again.
---------- Post added at 01:35 PM ---------- Previous post was at 12:55 PM ----------
Good news! I uploaded a debloated ROM. Link here: https://forum.xda-developers.com/android/development/6-0-lazy-s-debloated-rom-leagoo-m8-t3574816
It worked for my Leagoo M8 on second reflash with Pack-Flashtool-v5.1640.00.000.
After first attempt with original flashtool I had Freeme's hieroglyph and "no command" text.
Thank you!
Anyone knows if this can work for "Pro" version?
Related
Hi,
I have a Lenovo A516 rooted. I deleted some Lenovo pre-installed files that made my phone unstable and now it's stuck in boot.. I can get into my Android System recovery but what can I do from here? Can I try loading a custom ROM or should I find Lenovos factory ROM and load that?
This is my first time using Android System Recovery.
Help is greatly appreciated! I just bought this phone! :crying:
at system recovery can I try wipe data/factory reset or wipe cache partition?
I'm guessing I should install the ideafriend APK in recovery mode or ADB?
Sojuncoke said:
I'm guessing I should install the ideafriend APK in recovery mode or ADB?
Click to expand...
Click to collapse
Does anyone have instructions to install APK files in recovery without going into the phone and turning on developer mode?
Sojuncoke said:
Does anyone have instructions to install APK files in recovery without going into the phone and turning on developer mode?
Click to expand...
Click to collapse
I'm guessing I'm screwed?
Sojuncoke said:
I'm guessing I'm screwed?
Click to expand...
Click to collapse
Probably.
Do you have a custom recovery? If so I can probably create a flashable zip to get the APK back.
jerbear294 said:
Probably.
Do you have a custom recovery? If so I can probably create a flashable zip to get the APK back.
Click to expand...
Click to collapse
Hey Thanks for the reply. Yes I can get into my recovery by pressin power and volume buttons. And I did find the apk files i deleted. I am in the process of making a zip file out of them. Do I choose "update from SD Card" in recovery mode?
Sojuncoke said:
Hey Thanks for the reply. Yes I can get into my recovery by pressin power and volume buttons. And I did find the apk files i deleted. I am in the process of making a zip file out of them. Do I choose "update from SD Card" in recovery mode?
Click to expand...
Click to collapse
Is this a custom recovery or is it the stock recovery? You might get license errors if you are on the stock recovery.
EDIT: It seems there isn't a custom recovery for your device- Am I correct? That makes things harder.
jerbear294 said:
Probably.
Do you have a custom recovery? If so I can probably create a flashable zip to get the APK back.
Click to expand...
Click to collapse
Looks like I am having trouble with the zip file because it says installation aborted.
jerbear294 said:
Is this a custom recovery or is it the stock recovery? You might get license errors if you are on the stock recovery.
EDIT: It seems there isn't a custom recovery for your device- Am I correct? That makes things harder.
Click to expand...
Click to collapse
Yeah I never installed a custom recovery. So I guess its a stock recovery huh?
this is all it says
{
"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"
}
Sojuncoke said:
this is all it says
Click to expand...
Click to collapse
Yep, that's the stock recovery. You can try the zip you're making but you might get a signature verification later.
Help! I just unbricked my Le Max 2, it reboots with the screen splitted into two, the left half on the right and the right half on the left. Please can anyone kindly help?
{
"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"
}
after unbrick.
I use FlashOne 1.9 and a QFIL rom to unbrick it.
unbrick it again.
AhmadSant said:
unbrick it again.
Click to expand...
Click to collapse
re-unbricked, same result.
ok, can you do firstly reset factory, then try to install another rom.
AhmadSant said:
ok, can you do firstly reset factory, then try to install another rom.
Click to expand...
Click to collapse
factory reset and flashed another rom via fasboot, but reboot stuck at the start screen, just like the left one on the photo I submitted.
Do another unbricking, and everything back to the state I reported.
It's confirmed to be a hardware problem, when the monitor is replaced, everything back to normal.
I think there is problem with build.prop .. try google ... To restore build.prop
It seems that the Kernel is also affected so it must be hardware problem
hi did you solve this?
I have the same problem
KM141 said:
Click to expand...
Click to collapse
Hi, I have exactly the same problem after following the tutorial in here to get rid of the vendor encrypted god damn rom. Everything was working right before it so I don't buy the hardware issue. After flashing using flashone 2.0 I did ended up with my screen like this.
I tried several qfill file from severals sources and always the same result. I even try to go on and flash TWRP and RR rom but screen stay that way.
Please, I'm seriously desperate right now... I need your help guys and looks like i'm not the only one.
KM141 said:
Click to expand...
Click to collapse
Bambulbizarre said:
Hi, I have exactly the same problem after following the tutorial in here to get rid of the vendor encrypted god damn rom. Everything was working right before it so I don't buy the hardware issue. After flashing using flashone 2.0 I did ended up with my screen like this.
I tried several qfill file from severals sources and always the same result. I even try to go on and flash TWRP and RR rom but screen stay that way.
Please, I'm seriously desperate right now... I need your help guys and looks like i'm not the only one.
Click to expand...
Click to collapse
It was solved without replacing the screen!
Ok so, I did as shown in the topic : https://forum.xda-developers.com/le-max-2/help/flash-eui-rom-fastboot-t3525831
download twrp (The one I know didn't had the touchscreen issue)
boot from twrp (wish I had know about it before!) and not from one installed
upload zip file to /sdcard ( here's the catch, while in TWRP in don't have access to adb, the phone doesn't connect to pc or I don't know even I mount it, could be me. So i just put the archive at the root of the phone before booting to twrp from adb)
install rom
reboot
And ... it's ****ING WORKING!*
Really big thanks to ThE_MarD for his help!
For complete version :
https://forum.xda-developers.com/showpost.php?p=74890577&postcount=138
Bambulbizarre said:
It was solved without replacing the screen!
Ok so, I did as shown in the topic : https://forum.xda-developers.com/le-max-2/help/flash-eui-rom-fastboot-t3525831
download twrp (The one I know didn't had the touchscreen issue)
boot from twrp (wish I had know about it before!) and not from one installed
upload zip file to /sdcard ( here's the catch, while in TWRP in don't have access to adb, the phone doesn't connect to pc or I don't know even I mount it, could be me. So i just put the archive at the root of the phone before booting to twrp from adb)
install rom
reboot
And ... it's ****ING WORKING!*
Really big thanks to ThE_MarD for his help!
For complete version :
https://forum.xda-developers.com/showpost.php?p=74890577&postcount=138
Click to expand...
Click to collapse
To put a file on the phone while in twrp just use adb push
KuranKaname said:
To put a file on the phone while in twrp just use adb push
Click to expand...
Click to collapse
That's what I tried but as stated in the last link, I had no connection to adb while in twrp after cleaning up.
Anyway that's settled for me, it's mor for other that have encountered this as well. Replacing screen is not the only way.
{
"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"
}
OFFICIAL DOWNLOADS FOR SUZU:
https://twrp.me/sony/sonyxperiax.htmltwrp-3.x.x_x-x-suzu.img: Official TWRP image
DEVELOPMENT DOWNLOADS FOR SUZU:
Folder: https://sourceforge.net/projects/loire-development/files/twrp-recovery/suzu/twrp-3.x.x_x-x-YYYYMMDD-suzu.zip: Flashable unofficial TWRP to FOTAKerneltwrp-3.x.x_x-x-YYYYMMDD-suzu.img: Unofficial TWRP image
INSTALLATION
MANUALLY TO FOTAFastboot: Adapt the image name and install this way:fastboot flash recovery twrp-3.x.x_x-x-suzu.imgfastboot rebootFROM EXISTING RECOVERY
Enter to the current recovery
Install flashable TWRP
Reboot/Power off
HOW TO ENTER TO THE RECOVERY:
Power off your phone
Press Power and Vol- buttons at the same time until vibration
Wait for TWRP load
Sources:
TWRP device tree: https://github.com/TeamWin/android_device_sony_suzu/tree/android-9.0Kernel: https://github.com/Chippa-a/kernel-copyleft/tree/34.4.A.2.xxxThanks to the TWRP Team!
Backup-Restore function working fine so far, only issue I am seeing is phone is heating up pretty faster than before while backing up in compression mode.
Another minor thing is that earlier when entering recovery mode a purple light used to blink, now its missing.
Just saw this now and I'm really grateful. Big ups to you, man. Great work.
And I was afraid there would be no 3.2.1 for this device;
@Chippa_a makes it possible - intensified thanks! :highfive::good::good:
Thank you!!
I can't flash the zip because twrp does not give access to that part of the storage, weird.
fusk said:
I can't flash the zip because twrp does not give access to that part of the storage, weird.
Click to expand...
Click to collapse
Weird. Try using flash tool to fastboot the image if the flashable zip doesn't work for you.
Updated from TWRP, backup/restore works, no problems so far apart from it needs more than a minute till TWRP GUI appears after boot. Thanks for update.
Do you use the stock kernel? I installed the recovery built by oshmoun in the omnirom thread. It uses the aosp kernel. It starts faster, has a better sdcard naming and can flash oem images. Maybe you could try this kernel.
I use stock kernel (Pexorom 4.5) so this may be the reason for the delay.
I mean the kernel used with the recovery, not the rom kernel.
I_am_Blackford said:
Weird. Try using flash tool to fastboot the image if the flashable zip doesn't work for you.
Click to expand...
Click to collapse
This is what i did. Download img, place file on phone. Download twrp app, pick choose a file, browse to recovery.img, flash. Power off, boot to recovery = win.
Reboot to system, retry installing new update = great success.
mase76 said:
I mean the kernel used with the recovery, not the rom kernel.
Click to expand...
Click to collapse
Sorry, I didn't get it... kernels everywhere.
However, flashing with fastboot leads to the same delayed start. Strange.
privatim said:
Sorry, I didn't get it... kernels everywhere.
However, flashing with fastboot leads to the same delayed start. Strange.
Click to expand...
Click to collapse
I dont know if there is a connection, but i've tested the recovery with OmniROM 7.1.2, where display is not responding. It can be installed, shows 3.2.1, but display remains dead 4 touch.
Give this one a try:
https://forum.xda-developers.com/showpost.php?p=76440401&postcount=333
mase76 said:
Give this one a try:
https://forum.xda-developers.com/showpost.php?p=76440401&postcount=333
Click to expand...
Click to collapse
Same result, whether fastboot or flashtool, display is dead.
Certainly missed ODM LOIRE v12, v11 is installed.
Not really sure is the latest bootloader.
Does restoring a backup change the bootloader as well?
Edit: Solved: the answer is 'yes'.
3.2.1 does not work @7.1.2 restore because of outdated bootloader.
privatim said:
I use stock kernel (Pexorom 4.5) so this may be the reason for the delay.
Click to expand...
Click to collapse
Moved to XGEN ROM and now TWRP starts without delay. :good:
privatim said:
Moved to XGEN ROM and now TWRP starts without delay. :good:
Click to expand...
Click to collapse
What I do not understand, maybe bootloader or encryption, but why is 3.2.1 not backwards compatible on Suzu?
Is Omni 7.1.2 kernel (more I have not tried) or not current boot loader the reason?
Installed on last nougat internal storage 0 help
Inviato dal mio F5121 utilizzando Tapatalk
I'm glad that you finally managed to crack this damn decryption. I felt really bad with my broken promise of delivering the working build. I'm sorry, guys. @Chippa_a congratulations on your hard work
Hello xdadevelopers,
I recently bought myself the Poco F1 and tried to follow LTT's guide on how to make the Poco F1 like a Pixel, but I accidentally wiped everything (by going into additional settings and clicking every box). I can still access TWRP, but can't seem to install the custom rom (errors).
Is there anything I can do to continue with the process of making my phone like a pixel? I'm still a major novice in this so if possible, please use layman terms.
Thanks a lot,
Sirsitu
Hi,
I recently did the same but on purpose. This was advised in the Syberia OS ROM installation instructions. https://forum.xda-developers.com/poco-f1/development/rom-syberia-project-t3862622
You might want to try that(format data, install newest vendor+firmware etc) and then try to install a custom ROM.
SirSitu said:
Hello xdadevelopers,
I recently bought myself the Poco F1 and tried to follow LTT's guide on how to make the Poco F1 like a Pixel, but I accidentally wiped everything (by going into additional settings and clicking every box). I can still access TWRP, but can't seem to install the custom rom (errors).
Is there anything I can do to continue with the process of making my phone like a pixel? I'm still a major novice in this so if possible, please use layman terms.
Thanks a lot,
Sirsitu
Click to expand...
Click to collapse
If you're stuck you can back to stock with fastboot rom
Boot to fastboot and launch Xiaomi Flash on your pc.
SirSitu said:
Hello xdadevelopers,
I recently bought myself the Poco F1 and tried to follow LTT's guide on how to make the Poco F1 like a Pixel, but I accidentally wiped everything (by going into additional settings and clicking every box). I can still access TWRP, but can't seem to install the custom rom (errors).
Is there anything I can do to continue with the process of making my phone like a pixel? I'm still a major novice in this so if possible, please use layman terms.
Thanks a lot,
Sirsitu
Click to expand...
Click to collapse
The best thing that you can do is flash the latest fastboot stock ROM available. It'll reset the phone to as if it was new and also lock the bootloader. But you can unlock it back without the waiting time this time.
FieryAura said:
If you're stuck you can back to stock with fastboot rom
Boot to fastboot and launch Xiaomi Flash on your pc.
Click to expand...
Click to collapse
I've downloaded Xiaomi Flash and the stock rom, but when I try to flash it in, I get an error saying "can not find file flash_all_lock.bat" I think I've bricked my phone
{
"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"
}
SirSitu said:
I've downloaded Xiaomi Flash and the stock rom, but when I try to flash it in, I get an error saying "can not find file flash_all_lock.bat" I think I've bricked my phone
Click to expand...
Click to collapse
Use the latest unofficial twrp, format data, wipe everything and install beta from 24/12 EU (xiaomi.eu)
Share your results afterwards
SirSitu said:
I've downloaded Xiaomi Flash and the stock rom, but when I try to flash it in, I get an error saying "can not find file flash_all_lock.bat" I think I've bricked my phone
Click to expand...
Click to collapse
Try this version its older but compatible with miflash:
http://bigota.d.miui.com/V10.0.6.0....FH_20181113.0000.00_8.1_global_ad6e716a76.tgz
SirSitu said:
I've downloaded Xiaomi Flash and the stock rom, but when I try to flash it in, I get an error saying "can not find file flash_all_lock.bat" I think I've bricked my phone
Click to expand...
Click to collapse
That't not fastboot flashable file, genius. You are trying to flash the full ROM file. Download the fastboot file which comes in .tgz format. Extract it twice and you will get the main file. Once you extract the file, you would see the file name has a lot of "underscore" (_) marks See the attached screenshot). Moreover, you didn't mention what errors are you getting on TWRP while trying to flash the custom ROM. When creating a thread, try to include as much information possible, i you want someone to understand your problem and help you accordingly. Or else, you are just adding up thread counts.
---------- Post added at 14:24 ---------- Previous post was at 14:23 ----------
123Opie said:
Try this version its older but compatible with miflash:
http://bigota.d.miui.com/V10.0.6.0....FH_20181113.0000.00_8.1_global_ad6e716a76.tgz
Click to expand...
Click to collapse
LOL! All stock fastboot ROMs are compatible on MiFlash tool. It doesn't matter which version it is as long as it is fastboot flashable and you know how to extract and place it in the correct place.
"LOL! All stock fastboot ROMs are compatible on MiFlash tool. It doesn't matter which version it is as long as it is fastboot flashable and you know how to extract and place it in the correct place."
Yeah but from what I can see on this is just a normal firmware and has to be updated thru twrp or settings.
But that older version has a fastboot version to flash idk though.
https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
Can anyone help me????? my phone is bricked and i have to flash with firmware........... I tried all process in the google but i could flash the phone....
sadatkabir50 said:
Can anyone help me????? my phone is bricked and i have to flash with firmware........... I tried all process in the google but i could flash the phone....
Click to expand...
Click to collapse
I just seen on oxygen updater app on google play has that stock firmware. if I'm not mistaken... just doubled checked no usa version tho
{
"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"
}
sadatkabir50 said:
Can anyone help me????? my phone is bricked and i have to flash with firmware........... I tried all process in the google but i could flash the phone....
Click to expand...
Click to collapse
maybe i can download that firmware for you an foward a download link.
but def looks like.... we can get something going for you!!! NO PROMISES THO HAHA
halloweenm925 said:
maybe i can download that firmware for you an foward a download link.
but def looks like.... we can get something going for you!!! NO PROMISES THO HAHA
Click to expand...
Click to collapse
bro...my device is running but i got no internet wifi,sim data isnot working.....how to flash this if u send me this....
can u give the boot.img file or full rom ?
I'm having the very same problem right now. I tried to root the device and everything worked well so far, but neither Wifi nor Bluetooth is getting activated. Changing to the other boot slot ended up in a boot loop back to fastboot.
@sadatkabir50 Where did you get the stock rom from or what was your approach to root the device?
hamamama said:
I'm having the very same problem right now. I tried to root the device and everything worked well so far, but neither Wifi nor Bluetooth is getting activated. Changing to the other boot slot ended up in a boot loop back to fastboot.
@sadatkabir50 Where did you get the stock rom from or what was your approach to root the device?
Click to expand...
Click to collapse
Same problem. Everything working fine just Wi-Fi,camera,Bluetooth not working.
Which method did you use to root your device?
I'm following @halloweenm925's advice and downloaded the firmware for the EU version of the CPH2465 with a second device. How would you move forward if you had this file?
this boot img can boot ur phone but wifi and everything not working..
So I got the stock rom but neither the Wifi nor the Bluetooth is coming up. I'm kind of desperate right now. Can anybody support?
hamamama said:
So I got the stock rom but neither the Wifi nor the Bluetooth is coming up. I'm kind of desperate right now. Can anybody support?
Click to expand...
Click to collapse
inbox me bro.. just now i fixed the problem
Solved the problem. Here is how I did it.
1) On a second Android phone, download the Oxygen Updater App
2) Open the app, set it to advanced settings, chose the device with the semi-bricked status, download the full zip
3) the zip file will be downloaded to sdcard's user root => transfer the zip file to your semi-bricked device
4) on your semi-bricked device, go to settings>updates, click on the top right three-point-menue and chose "local installation"
5) select the zip file and do the update
After the unpacking and verification is finished, reboot the phone and things should be back to normal.
If you want, you can now give the rooting a second try. There are a lot of tutorials, I used this one since I had the stock full rom:
Root OnePlus Nord CE 5G using Magisk [No TWRP Required]
Do you own a OnePlus Nord CE 5G android smartphone? If yes, today, we will share with you how you can Root OnePlus Nord CE 5G with the help of the Magisk
magiskapp.com
The full stock rom which is downloaded as described above needs to be extracted with the help of a script: as described here:
[LINUX][GUIDE] ROM Payload Image Dump
Now we have dumpers for Win/Mac/Linux! Great!
forum.xda-developers.com
So the steps to root the device would be
1) download the full rom as described above
2) extract the boot.img with the help of aforementioned python script
3) follow the steps as described in the tutorial linked above
I think what caused the initial issue on my side was that I simply was not on the same OS version on the device as the boot.img which I extracted from the full zip which is totally my own fault because almost every tutorial mentions it explicitly that you have to have the latest update on your to-be-rooted device AND make sure that you have the same ROM available to root your device.
Questions welcome!