Hello everyone, I have recently flashed new custom ROM on my device - Realme 7 rmx 2151 and everything went as planned. I used unlocking and flashing guide new from XDA webpage... I flashed PixelPlus UI3.9 from here, XDA ... I was really loooking forward to try new things etc... and do not know where I messed up but can not turn ON Wi-Fi and BLUETOOTH. Please any advice ? Thank you in advance...
Could be a problem with the rom,try to flash evolution x to see if that works
Ok. thank you for advice, I will do that within a next two hours. lets try...
I Have just installed Evolution X And probleem still remains... I am pi**ed off where I went Wrong...anyway I appreciate your help.
RobertoSt25 said:
I Have just installed Evolution X And probleem still remains... I am pi**ed off where I went Wrong...anyway I appreciate your help.
Click to expand...
Click to collapse
Try restoring the persist partition.
RobertoSt25 said:
I Have just installed Evolution X And probleem still remains... I am pi**ed off where I went Wrong...anyway I appreciate your help.
Click to expand...
Click to collapse
Were you on a.87 before flashing the ROM?
SubwayChamp said:
Try restoring the persist partition.
Click to expand...
Click to collapse
I would if I knew how... I am newbie, but if you could help me out, I would be grateful.
OrthodoxOxygen said:
Were you on a.87 before flashing the ROM?
Click to expand...
Click to collapse
Not sure buddy, but honestly can say either 87 or 91....
RobertoSt25 said:
I would if I knew how... I am newbie, but if you could help me out, I would be grateful.
Click to expand...
Click to collapse
Unfortunately this is a very problematic device, if you didn't make a backup before... the ofp file doesn't contain one, so you need that someone else take a backup of persist partition from a good/working phone and upload the file for you, then you can flash it back using fastboot.
RobertoSt25 said:
I would if I knew how... I am newbie, but if you could help me out, I would be grateful.
Click to expand...
Click to collapse
Other people had this exact issue. It's the device firmware that you were on before flashing that is detrimental. Are you RMX2155 or RMX2151?
OrthodoxOxygen said:
Other people had this exact issue. It's the device firmware that you were on before flashing that is detrimental. Are you RMX2155 or RMX2151?
Click to expand...
Click to collapse
So I think, the best would be to purchase a new one as soon as possible , never mind, thats fine, I should have thought twice before I did something ... Its REALME RMX 2151 , but on the BACK of the phone its written model RMX 2155
SubwayChamp said:
Unfortunately this is a very problematic device, if you didn't make a backup before... the ofp file doesn't contain one, so you need that someone else take a backup of persist partition from a good/working phone and upload the file for you, then you can flash it back using fastboot.
Click to expand...
Click to collapse
Alright... I will be thinking of buying a new one probably , anyway I will give it a one more try and will do as you saying.. Taking a backup of persist has to be the exact same model RMX ? or could it be for example ONEPLUS ,completely different mobile ? Thanks.
RobertoSt25 said:
Alright... I will be thinking of buying a new one probably , anyway I will give it a one more try and will do as you saying.. Taking a backup of persist has to be the exact same model RMX ? or could it be for example ONEPLUS ,completely different mobile ? Thanks.
Click to expand...
Click to collapse
No, it must be from the same model, it is a very sensitive partition, used from other different device/model could brick your device.
I backed up one from my device while it was in bricked state, if this functionality weren't broken at this time then it would work for you, if you want to give it a try I'll upload it soon.
RobertoSt25 said:
So I think, the best would be to purchase a new one as soon as possible , never mind, thats fine, I should have thought twice before I did something ... Its REALME RMX 2151 , but on the BACK of the phone its written model RMX 2155
Click to expand...
Click to collapse
You don't need to uy a new one. You just need to reflash the correct firmware, and then reflash the ROM you're trying to use after that.
SubwayChamp said:
No, it must be from the same model, it is a very sensitive partition, used from other different device/model could brick your device.
I backed up one from my device while it was in bricked state, if this functionality weren't broken at this time then it would work for you, if you want to give it a try I'll upload it soon.
Click to expand...
Click to collapse
cheers buddy, I will give it a try for sure, but are you sure its ok to flash it from bricked device?
alright I will do that, what would you recon, how to flash it ? I mean the best and the easiest way to do that...? Thank you very much.
RobertoSt25 said:
cheers buddy, I will give it a try for sure, but are you sure its ok to flash it from bricked device?
Click to expand...
Click to collapse
If the firmware is not cased sensitive, then it shouldn't.
But to be completely sure backup first your persist partition, also you can back up the others aswell
Reboot to your custom recovery and type the next one by one:
adb shell
dd if=/dev/block//by-name/persist of=/sdcard/persist.img
After that, you'll have your persist image in the main directory of your sdcard (internal memory)
After that you can copy/transfer it directly to your PC (don't forget to keep it in a safe place, not in your device)
Or you can pull it with:
Exit first from the shell (just one time, in case you are not rooted) with:
exit
adb pull /sdcard/persist.img
This will copy (really pull/move) the file to the same directory where you ran the command.
You can flash it using fastboot.
SubwayChamp said:
If the firmware is not cased sensitive, then it shouldn't.
But to be completely sure backup first your persist partition, also you can back up the others aswell
Reboot to your custom recovery and type the next one by one:
adb shell
dd if=/dev/block//by-name/persist of=/sdcard/persist.img
After that, you'll have your persist image in the main directory of your sdcard (internal memory)
After that you can copy/transfer it directly to your PC (don't forget to keep it in a safe place, not in your device)
Or you can pull it with:
Exit first from the shell (just one time, in case you are not rooted) with:
exit
adb pull /sdcard/persist.img
This will copy (really pull/move) the file to the same directory where you ran the command.
You can flash it using fastboot.
Click to expand...
Click to collapse
lovely, you are No,1, I will do that exactly the way you described. Thank you very much for that.
I did everything exactly the way you said and still wifi and bluetooth won´t turn on my friend... Shoul I flash new custom ROM ?
RobertoSt25 said:
I did everything exactly the way you said and still wifi and bluetooth won´t turn on my friend... Shoul I flash new custom ROM ?
Click to expand...
Click to collapse
You just need to flash a.87 back onto your device. Did you need to follow an elaborate guide to unlock your phone's bootloader, or did you just submit an application via the DeepTest APK? I need to know this in order to link you the correct files to flash.
Related
So I am fond of flashing custom ROMs and stuff on my mido and I carry knowledge about what I'm doing. Day before yesterday I was flashing Oreo 8.1 ROMs via TWRP. Accidentally I deleted everything in "/" folder (I suppose its called root folder idk). Terminal gave output saying something like rm -rf i don't recall exactly .. i thought i didn't mess up so i went forward flashing AEX 5.1 Beta ROM. The ROM booted perfectly but only issue I got was No WiFi and data signals... I thought i messed up with firmware so i went ahead and flashed sock ROM via MI FLASH. It flashed successfully but when my device rebooted I started setting it up until it started rebooting again and again... It's not normal boot-loop... i am getting past Mi logo and even able to go through setup wizard but unable to complete it... when i start setting device up it freezes and then restarts and that's it!
what i have tried:
1) Flashing in EDL mode
2) Flashing TWRP/ RedWolf recovery and formatting data
3) Flashing Custom ROM (The issue persisits the device boots succesfully the reboots)
4) Tried flashing via QFIL but cant seem to make it work (fh_loader stops working)
Is it software issue or hardware? It must be software right? or else phone wouldnot have booted successfully
P.S: Under Device Info it shows MAC as 20:00:00:00:00:00 and WiFi wont turn on, same with Bluetooth (Mobile signals work perfectly)
I think i messed up with partitions someone PLEASE HELP!
addymishra said:
So I am fond of flashing custom ROMs and stuff on my mido and I carry knowledge about what I'm doing. Day before yesterday I was flashing Oreo 8.1 ROMs via TWRP. Accidentally I deleted everything in "/" folder (I suppose its called root folder idk). Terminal gave output saying something like rm -rf i don't recall exactly .. i thought i didn't mess up so i went forward flashing AEX 5.1 Beta ROM. The ROM booted perfectly but only issue I got was No WiFi and data signals... I thought i messed up with firmware so i went ahead and flashed sock ROM via MI FLASH. It flashed successfully but when my device rebooted I started setting it up until it started rebooting again and again... It's not normal boot-loop... i am getting past Mi logo and even able to go through setup wizard but unable to complete it... when i start setting device up it freezes and then restarts and that's it!
what i have tried:
1) Flashing in EDL mode
2) Flashing TWRP/ RedWolf recovery and formatting data
3) Flashing Custom ROM (The issue persisits the device boots succesfully the reboots)
4) Tried flashing via QFIL but cant seem to make it work (fh_loader stops working)
Is it software issue or hardware? It must be software right? or else phone wouldnot have booted successfully
P.S: Under Device Info it shows MAC as 20:00:00:00:00:00 and WiFi wont turn on, same with Bluetooth (Mobile signals work perfectly)
I think i messed up with partitions someone PLEASE HELP!
Click to expand...
Click to collapse
you actually messed up your device bad. basically the '/' directory has folders containing files which the linux os requires. there are dev scripts which perform the backend tasks, and if they all are deleted, well sorry to say, the device then is just an expensive paperweight. not sure how you are still able to boot. Basically rm -rf command deletes all the writable partitions of android. maybe the device is booting up on the support of blobs. but there are very little chances to get back normal. sorry but unable to help
MyNameIsRage said:
you actually messed up your device bad. basically the '/' directory has folders containing files which the linux os requires. there are dev scripts which perform the backend tasks, and if they all are deleted, well sorry to say, the device then is just an expensive paperweight. not sure how you are still able to boot. Basically rm -rf command deletes all the writable partitions of android. maybe the device is booting up on the support of blobs. but there are very little chances to get back normal. sorry but unable to help
Click to expand...
Click to collapse
Hey, I got it working up and fine. What actually helped was flashing the stock rom with QFIL tool. The device booted up successfully and right now I'm writing this with my mido only ? All the partitions have been recovered successfully and WiFi and Bluetooth are up and running too! The only issue is that QFIL wiped my IMEI. I'm sure there must be some way to write IMEI back. If you know you may help too ?
addymishra said:
Hey, I got it working up and fine. What actually helped was flashing the stock rom with QFIL tool. The device booted up successfully and right now I'm writing this with my mido only All the partitions have been recovered successfully and WiFi and Bluetooth are up and running too! The only issue is that QFIL wiped my IMEI. I'm sure there must be some way to write IMEI back. If you know you may help too
Click to expand...
Click to collapse
God save QFIL!
btw check this video for imei
https://www.youtube.com/watch?v=m9hq-FiDn58
MyNameIsRage said:
God save QFIL!
btw check this video for imei
https://www.youtube.com/watch?v=m9hq-FiDn58
Click to expand...
Click to collapse
No worries! Fixed it myself! Hahaha!! I'm so happy!! Thank you so much! God bless XDA!! ?????
addymishra said:
No worries! Fixed it myself! Hahaha!! I'm so happy!! Thank you so much! God bless XDA!!
Click to expand...
Click to collapse
lol, god bless our redmi note 4.
MyNameIsRage said:
lol, god bless our redmi note 4.
Click to expand...
Click to collapse
Yes!
addymishra said:
Yes!
Click to expand...
Click to collapse
Hey, I have the same problem with you. I tried to flash stock rom with QFIL tool but I get an error when downloading. I followed this guide
http://en.miui.com/thread-432217-1-1.html
I get the following error: Download Fail: FireHose Fail FHLoader Failrocess fail
any help?
Jimmy_979 said:
Hey, I have the same problem with you. I tried to flash stock rom with QFIL tool but I get an error when downloading. I followed this guide
http://en.miui.com/thread-432217-1-1.html
I get the following error: Download Fail: FireHose Fail FHLoader Failrocess fail
any help?
Click to expand...
Click to collapse
Hey, sorry for late I'm here now! Listen, I followed the same procedure as mentioned in Mi forum. I got the same error! It might say that fh_loader stopped working right? The solution was to flash stock miui rom. By stock I mean out of the box rom i.e. V8.1.10.0.MCFMIDI which you can find here: http://bigota.d.miui.com/V8.1.10.0....DI_20161228.0000.00_6.0_global_7557bfe334.tgz
Download the above linked ROM and flash it via QFIL (Run as administrator) and you should be good to go! I hope it works out! If you face any problem then keep me posted All the best!
addymishra said:
Hey, sorry for late I'm here now! Listen, I followed the same procedure as mentioned in Mi forum. I got the same error! It might say that fh_loader stopped working right? The solution was to flash stock miui rom. By stock I mean out of the box rom i.e. V8.1.10.0.MCFMIDI which you can find here: http://bigota.d.miui.com/V8.1.10.0....DI_20161228.0000.00_6.0_global_7557bfe334.tgz
Download the above linked ROM and flash it via QFIL (Run as administrator) and you should be good to go! I hope it works out! If you face any problem then keep me posted All the best!
Click to expand...
Click to collapse
Yeaaah it worked!!!!! Thank you a lot guys!!! And my imei numbers were there (I called *#06# to see). Now I have one question:
How can I install properly a custom rom without bricking my phone again?
Jimmy_979 said:
Yeaaah it worked!!!!! Thank you a lot guys!!! And my imei numbers were there (I called *#06# to see). Now I have one question:
How can I install properly a custom rom without bricking my phone again?
Click to expand...
Click to collapse
@Jimmy_979 Yessss i am so happppyyy for you alll!!! Dammmm @addymishra you should probably start a new thread describing how to fix this problem!
Jimmy_979 said:
Yeaaah it worked!!!!! Thank you a lot guys!!! And my imei numbers were there (I called *#06# to see). Now I have one question:
How can I install properly a custom rom without bricking my phone again?
Click to expand...
Click to collapse
Haha thats great congrats! Tip for custom rom installation is to follow install guide carefully and don't ever touch root partition lol! I've stopped flashing roms now... I'm on miui now permanently with bootloader locked lol
MyNameIsRage said:
@Jimmy_979 Yessss i am so happppyyy for you alll!!! Dammmm @addymishra you should probably start a new thread describing how to fix this problem!
Click to expand...
Click to collapse
Haha @MyNameIsRage I'm thinking so ???
I m stuck in this same problem
But i never tried qflash
Wellll
I buy new op5t but i still wnt back to rn4
Will tell ya guys tonight nd please help me with proper procrdure
I downloaded everything but wich file have to flash
Or any video out there?
Saved my rn4
Thank u all
Thnx alot
my phone keeps rebooting
addymishra said:
So I am fond of flashing custom ROMs and stuff on my mido and I carry knowledge about what I'm doing. Day before yesterday I was flashing Oreo 8.1 ROMs via TWRP. Accidentally I deleted everything in "/" folder (I suppose its called root folder idk). Terminal gave output saying something like rm -rf i don't recall exactly .. i thought i didn't mess up so i went forward flashing AEX 5.1 Beta ROM. The ROM booted perfectly but only issue I got was No WiFi and data signals... I thought i messed up with firmware so i went ahead and flashed sock ROM via MI FLASH. It flashed successfully but when my device rebooted I started setting it up until it started rebooting again and again... It's not normal boot-loop... i am getting past Mi logo and even able to go through setup wizard but unable to complete it... when i start setting device up it freezes and then restarts and that's it!
what i have tried:
1) Flashing in EDL mode
2) Flashing TWRP/ RedWolf recovery and formatting data
3) Flashing Custom ROM (The issue persisits the device boots succesfully the reboots)
4) Tried flashing via QFIL but cant seem to make it work (fh_loader stops working)
Is it software issue or hardware? It must be software right? or else phone wouldnot have booted successfully
P.S: Under Device Info it shows MAC as 20:00:00:00:00:00 and WiFi wont turn on, same with Bluetooth (Mobile signals work perfectly)
I think i messed up with partitions someone PLEASE HELP!
Click to expand...
Click to collapse
Pls bro am going Tru this same problem flashed through recovery flashed through fastboot but it keeps rebooting pls help me out with the exact steps u used to fix urs
addymishra said:
Hey, I got it working up and fine. What actually helped was flashing the stock rom with QFIL tool. The device booted up successfully and right now I'm writing this with my mido only All the partitions have been recovered successfully and WiFi and Bluetooth are up and running too! The only issue is that QFIL wiped my IMEI. I'm sure there must be some way to write IMEI back. If you know you may help too
Click to expand...
Click to collapse
I am in same problem on mido. Can you help me how to get in edl mode because QFIL Not detecting PORT.
Also my adb not detecting the device so i cant use adb commands.
But i can flash Stock ROM using MI Flash Tools.
Jimmy_979 said:
Yeaaah it worked!!!!! Thank you a lot guys!!! And my imei numbers were there (I called *#06# to see). Now I have one question:
How can I install properly a custom rom without bricking my phone again?
Click to expand...
Click to collapse
hey guyz i have the same problem , please help me i tried all written in the replies but faces the same problem in the QFIL.
please reply, i'm dead :"(
Hello everyone.
I'm new in the forum and I'm looking for help.
Habitually I try to solve my problems by myself but this time I need your help.
I recently acquired a pixel 3. And everything works fine until I had to flash the factory image.
I find the factory image file on google dev website and I follow the instructions.
I also tried different tutos but I always have the same issues.
My pixel 3 restart but I can't turn on WiFi.
My Bluetooth is ok
Finally, it feels like the pixel is more slowly since I flash the factory image. (Setting app crash half of the time).
Is anyone had the same issues or have a solutions ?
Thanks by advance.
totib38 said:
Hello everyone.
I'm new in the forum and I'm looking for help.
Habitually I try to solve my problems by myself but this time I need your help.
I recently acquired a pixel 3. And everything works fine until I had to flash the factory image.
I find the factory image file on google dev website and I follow the instructions.
I also tried different tutos but I always have the same issues.
My pixel 3 restart but I can't turn on WiFi.
My Bluetooth is ok
Finally, it feels like the pixel is more slowly since I flash the factory image. (Setting app crash half of the time).
Is anyone had the same issues or have a solutions ?
Thanks by advance.
Click to expand...
Click to collapse
Make sure you have the latest sdk platform tools, r28.
Then download the factory image again, it might have been corrupted. Use 7zip to extract the zip file.
Flash the factory image again using the flash-all batch file. Note, this will wipe your device.
If that doesn't work then you might have a hardware issue.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Make sure you have the latest sdk platform tools, r28.
Then download the factory image again, it might have been corrupted. Use 7zip to extract the zip file.
Flash the factory image again using the flash-all batch file. Note, this will wipe your device.
If that doesn't work then you might have a hardware issue.
Click to expand...
Click to collapse
Thanks for your answer.
I will retry tonight at home.
One more detail : so I have to modified flash-all batch file ?
In some discussion I saw some people delete -w of the script.
I will inform if the process is ok
totib38 said:
Thanks for your answer.
I will retry tonight at home.
One more detail : so I have to modified flash-all batch file ?
In some discussion I saw some people delete -w of the script.
I will inform if the process is ok
Click to expand...
Click to collapse
If you delete the -w it will not wipe your device. You can try that, but if problem still is there then include the -w. Wiping your device is a better trouble shooting solution but you will have to setup your device like it was new. It's up to you.
Sent from my [device_name] using XDA-Developers Legacy app
Thanks for your support.
I just tried several flash factory image but the result is always the same.
I can't turn on wifi setting ....
Everything else seems to work.
I'm really disappointed and I don't know what to do.
It seems there is a issue with vendor.img
After my first boot, I download Es explorer and I navigate in :
'System>vendor>ECT>wifi' and it seems files are missing compare to my others devices.
Is there a way to modify the field with root permission?
Maybe you need to unlock the critical partition before flashing?
gm007 said:
Maybe you need to unlock the critical partition before flashing?
Click to expand...
Click to collapse
Hello gm007
How can I unlock the critical partition before flashing ?
Thanks by advance ?
totib38 said:
Hello gm007
How can I unlock the critical partition before flashing ?
Thanks by advance ?
Click to expand...
Click to collapse
fastboot flashing unlock_critical
Not sure if it's needed.
this will wipe ur phone same as unlocking bootloader.
gm007 said:
fastboot flashing unlock_critical
Not sure if it's needed.
this will wipe ur phone same as unlocking bootloader.
Click to expand...
Click to collapse
It's failed...
It's indicate 'Invalid argument unlock_critical'
totib38 said:
Thanks for your support.
I just tried several flash factory image but the result is always the same.
I can't turn on wifi setting ....
Everything else seems to work.
I'm really disappointed and I don't know what to do.
It seems there is a issue with vendor.img
After my first boot, I download Es explorer and I navigate in :
'System>vendor>ECT>wifi' and it seems files are missing compare to my others devices.
Is there a way to modify the field with root permission?
Click to expand...
Click to collapse
I don't know what you're seeing in the etc folder but this is what I have in the pixel 3,
jd1639 said:
I don't know what you're seeing in the etc folder but this is what I have in the pixel 3,
Click to expand...
Click to collapse
Ah .....
Ok so the vendor.img should be ok.
I'm completely lost .
Everything works except that. And the phone has just a week so I don't think it's a hardware issue.
If I don't find the solution i will keep this device in my desk ?
totib38 said:
Ah .....
Ok so the vendor.img should be ok.
I'm completely lost .
Everything works except that. And the phone has just a week so I don't think it's a hardware issue.
If I don't find the solution i will keep this device in my desk [emoji25]
Click to expand...
Click to collapse
Did the wifi work when you first got the phone? When you flashed the factory image did you wipe the device or use the flash all with the -w removed? If you wiped the device I'm guessing it is a hardware issue.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Did the wifi work when you first got the phone? When you flashed the factory image did you wipe the device or use the flash all with the -w removed? If you wiped the device I'm guessing it is a hardware issue.
Click to expand...
Click to collapse
Yes the wifi worked at the first boot.
I'm guessing I have wipe the device and that's the reason wifi there is a problem.
Is there any way to recover wifi drivers or anything else ?
What are my possibilities ?
Go on a sav and change wifi hardware ?
totib38 said:
Yes the wifi worked at the first boot.
I'm guessing I have wipe the device and that's the reason wifi there is a problem.
Is there any way to recover wifi drivers or anything else ?
What are my possibilities ?
Go on a sav and change wifi hardware ?
Click to expand...
Click to collapse
I don't know how flahing the factory image would cause the problem. But a couple of things to check. First, make sure you're using the latest sdk platform tools (fastboot and adb), r28. Then make sure you're using the correct factory image, there one for docomo or something like that which is for the Japanese variant, and redownload it in case you got something corrupted.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I don't know how flahing the factory image would cause the problem. But a couple of things to check. First, make sure you're using the latest sdk platform tools (fastboot and adb), r28. Then make sure you're using the correct factory image, there one for docomo or something like that which is for the Japanese variant, and redownload it in case you got something corrupted.
Click to expand...
Click to collapse
I will try again tonight but I have no hope
I use the last SDK platform tools r28.0.1
And I took the factory image from google devs website.
My Mac address is block on 02:00:00:00:00:00 to be more precise.
totib38 said:
It's failed...
It's indicate 'Invalid argument unlock_critical'
Click to expand...
Click to collapse
Seems you have outdated sdk try to remove and install the latest one as suggested above. Or try another pc.
gm007 said:
Seems you have outdated sdk try to remove and install the latest one as suggested above. Or try another pc.
Click to expand...
Click to collapse
It Is not because fastboot flashing unlock_critical is a command for pixel 3 XL ?
I got the pixel 3 device
totib38 said:
Hello everyone.
I'm new in the forum and I'm looking for help.
Habitually I try to solve my problems by myself but this time I need your help.
I recently acquired a pixel 3. And everything works fine until I had to flash the factory image.
I find the factory image file on google dev website and I follow the instructions.
I also tried different tutos but I always have the same issues.
My pixel 3 restart but I can't turn on WiFi.
My Bluetooth is ok
Finally, it feels like the pixel is more slowly since I flash the factory image. (Setting app crash half of the time).
Is anyone had the same issues or have a solutions ?
Thanks by advance.
Click to expand...
Click to collapse
I think you're platform-tools are not up to date. Download them from here:
https://developer.android.com/studio/releases/platform-tools
Put the facrory image in the same folder as the platform-tools and execute flash-all from there.
I thougt mine were up to date, but not everyting from the image got flashed.
With the latest platform tools everyting was ok.
rhino666 said:
I think you're platform-tools are not up to date. Download them from here:
https://developer.android.com/studio/releases/platform-tools
Put the facrory image in the same folder as the platform-tools and execute flash-all from there.
I thougt mine were up to date, but not everyting from the image got flashed.
With the latest platform tools everyting was ok.
Click to expand...
Click to collapse
Thanks for your help.
This is precisely the one I took yesterday and I always have the same issues
totib38 said:
Thanks for your help.
This is precisely the one I took yesterday and I always have the same issues
Click to expand...
Click to collapse
Then the only thing I can think of is for you to try another cable or computer.
<removed>
I think Moto Moto don't like us
Command should be "dd if=/dev/block/mmcblk0p40 of=/external_sd/boot.img" then, and don't forget to mount micro sd in twrp first.
Ofc it works fine to execute command from adb shell when booted to twrp, which makes it a bit easier to type.
When I try to boot from patched image, phone is stuck on 'Android One' logo.
I'm on firmware version OPENEU_9.0_PPK29.68-16-21. I guess this firmware version isn't rootable .
Well, I'll wait for some custom ROM to enjoy rooted phone (maybe that Ressurection Remix ROM which was announced few days ago) .
gregory678 said:
When I try to boot from patched image, phone is stuck on 'Android One' logo.
I'm on firmware version OPENEU_9.0_PPK29.68-16-21. I guess this firmware version isn't rootable .
Well, I'll wait for some custom ROM to enjoy rooted phone (maybe that Ressurection Remix ROM which was announced few days ago) .
Click to expand...
Click to collapse
Propably you patch wrong boot image, try to extract from your device stock
tys0n said:
Command should be "dd if=/dev/block/mmcblk0p40 of=/external_sd/boot.img" then, and don't forget to mount micro sd in twrp first.
Ofc it works fine to execute command from adb shell when booted to twrp, which makes it a bit easier to type.
Click to expand...
Click to collapse
It's not universal path so i BOLD the path to change
[email protected] said:
It's not universal path so i BOLD the path to change
Click to expand...
Click to collapse
That's understood, but if you're booted to twrp, then "of=/external_sd/boot.img"" is pretty much your only option since internal is encrypted.
tys0n said:
That's understood, but if you're booted to twrp, then "of=/external_sd/boot.img"" is pretty much your only option since internal is encrypted.
Click to expand...
Click to collapse
Edited
[email protected] said:
Propably you patch wrong boot image, try to extract from your device stock
Click to expand...
Click to collapse
That didn't help as well. Now I'm sure that only some custom ROM will be my way to enjoy root. I will not flash any other stock ROM, I'm not that desperate (I'm also a bit afraid of doing so) .
gregory678 said:
That didn't help as well. Now I'm sure that only some custom ROM will be my way to enjoy root. I will not flash any other stock ROM, I'm not that desperate (I'm also a bit afraid of doing so) .
Click to expand...
Click to collapse
Okay, contact me on Telegram @Zmianek, and be a Tester of RessuectionRemix ! I always need to wait till the weekend with tests that slow's down development speed
gregory678 said:
That didn't help as well. Now I'm sure that only some custom ROM will be my way to enjoy root. I will not flash any other stock ROM, I'm not that desperate (I'm also a bit afraid of doing so) .
Click to expand...
Click to collapse
It should work. I've patched boot after every update without problems.
XT1941-4
Sent from my moto one
[email protected] said:
Okay, contact me on Telegram @Zmianek, and be a Tester of RessuectionRemix ! I always need to wait till the weekend with tests that slow's down development speed
Click to expand...
Click to collapse
I would like to, but is there some way of backing up stock ROM? I know that current version of TWRP has some issues with /data partition, that's why I ask .
And what about installing this ROM? Would I need to use that TWRP we have now? Is it safe?
tys0n said:
It should work. I've patched boot after every update without problems.
XT1941-4
Click to expand...
Click to collapse
Well, you have different software channel, I think that's the only reason why it works for you and it doesn't work for me . OPENEU seems to be bulletproof. (I have XT1941-4 too)
Someone correct me if I'm wrong, maybe for someone with OPENEU it does work.
I Request close due to failures
seccfg, nvcfg, nvdata, nvram, persist, proinfo, protect1, protect2.
super partition: my_*, odm, product, system, vendor.
I need all these partitions please let me know anyone could help me or not as my imei is not working because i foolishly erased the paritions and flashed the stock image
without realizing i needed to make a backup first so if possible someone please give me their partition backup .
I dont care about the fingerprint as far as the mobile can make calls and would be in a functioning condition .
1 guy here in our forums even flashed the persist image and fixed his camera so i believe flashing the appropriate partitions would help me get my phone to a working condition
and do not ask me to go to svc as i already did that and they were of no help and asked me for a motherboard change and they flashed the phone but the imei problem and the
fingerprint problem was not solved at all so i dont trust these guys at all . As the SVC usually always wants to shell out money from our pockets .
rohit4989 said:
seccfg, nvcfg, nvdata, nvram, persist, proinfo, protect1, protect2.
super partition: my_*, odm, product, system, vendor.
I need all these partitions please let me know anyone could help me or not as my imei is not working because i foolishly erased the paritions and flashed the stock image
without realizing i needed to make a backup first so if possible someone please give me their partition backup .
I dont care about the fingerprint as far as the mobile can make calls and would be in a functioning condition .
1 guy here in our forums even flashed the persist image and fixed his camera so i believe flashing the appropriate partitions would help me get my phone to a working condition
and do not ask me to go to svc as i already did that and they were of no help and asked me for a motherboard change and they flashed the phone but the imei problem and the
fingerprint problem was not solved at all so i dont trust these guys at all . As the SVC usually always wants to shell out money from our pockets .
Click to expand...
Click to collapse
I will provide my partitions backup by the evening.
Chaitanya Dixit said:
I will provide my partitions backup by the evening.
Click to expand...
Click to collapse
May god bless your soul
just a small note that do provide all the backup of all the system partitions ,
Thank you soo much
rohit4989 said:
May god bless your soul
just a small note that do provide all the backup of all the system partitions ,
Thank you soo much
Click to expand...
Click to collapse
Yes, I know that.
Chaitanya Dixit said:
Yes, I know that.
Click to expand...
Click to collapse
By chance if you do not have enough cloud storage or something like that then you can send me the files using sendanywhere application . Also thank you very much again for helping me with the system partitions .
rohit4989 said:
By chance if you do not have enough cloud storage or something like that then you can send me the files using sendanywhere application . Also thank you very much again for helping me with the system partitions .
Click to expand...
Click to collapse
I have some cloud storage and uploading now to onedrive.
rohit4989 said:
seccfg, nvcfg, nvdata, nvram, persist, proinfo, protect1, protect2.
super partition: my_*, odm, product, system, vendor.
I need all these partitions please let me know anyone could help me or not as my imei is not working because i foolishly erased the paritions and flashed the stock image
without realizing i needed to make a backup first so if possible someone please give me their partition backup .
I dont care about the fingerprint as far as the mobile can make calls and would be in a functioning condition .
1 guy here in our forums even flashed the persist image and fixed his camera so i believe flashing the appropriate partitions would help me get my phone to a working condition
and do not ask me to go to svc as i already did that and they were of no help and asked me for a motherboard change and they flashed the phone but the imei problem and the
fingerprint problem was not solved at all so i dont trust these guys at all . As the SVC usually always wants to shell out money from our pockets .
Click to expand...
Click to collapse
Cheers! Here is the link https://1drv.ms/u/s!ArF9gnfEP0UVg2bEHr2lxiVuUAS8?e=hfgnh7
I have backed up every partition except userdata.
Good luck. Inform me if something is missing.
Chaitanya Dixit said:
Cheers! Here is the link https://1drv.ms/u/s!ArF9gnfEP0UVg2bEHr2lxiVuUAS8?e=hfgnh7
I have backed up every partition except userdata.
Good luck. Inform me if something is missing.
Click to expand...
Click to collapse
Thanks a ton , also do i need to be on the same version of oxygenos ? this backup is of which version of oxygenos ?
rohit4989 said:
Thanks a ton , also do i need to be on the same version of oxygenos ? this backup is of which version of oxygenos ?
Click to expand...
Click to collapse
From any version, you can flash these partitions with mtkclient.
These are the partitions of Oxygen OS 11.3 DN2101_11_A.11 Version.
rohit4989 said:
Thanks a ton , also do i need to be on the same version of oxygenos ? this backup is of which version of oxygenos ?
Click to expand...
Click to collapse
Anytime buddy. If you are stuck anywhere, inform me.
Chaitanya Dixit said:
Anytime buddy. If you are stuck anywhere, inform me.
Click to expand...
Click to collapse
Thank you very much , do you have the link to fastboot drivers ? I have adb and mtk Vcom drivers but not the fastboot drivers . My device
Chaitanya Dixit said:
From any version, you can flash these partitions with mtkclient.
These are the partitions of Oxygen OS 11.3 DN2101_11_A.11 Version.
Click to expand...
Click to collapse
Ok no problem ill use the MTK client then
rohit4989 said:
Thank you very much , do you have the link to fastboot drivers ? I have adb and mtk Vcom drivers but not the fastboot drivers . My device
Ok no problem ill use the MTK client then
Click to expand...
Click to collapse
Okay, use platform tools. Link - https://dl.google.com/android/repository/platform-tools_r33.0.3-windows.zip
@rohit4989 Have you flashed firmware?
Chaitanya Dixit said:
@rohit4989 Have you flashed firmware?
Click to expand...
Click to collapse
Sir the pc went dead yesterday , so replacing the components of my pc to make it alive , ill update not only you but ill make a thread if the flash files work for me .
rohit4989 said:
Sir the pc went dead yesterday , so replacing the components of my pc to make it alive , ill update not only you but ill make a thread if thr flash files work for me .
Click to expand...
Click to collapse
Exactly, So other people make use of it.
Chaitanya Dixit said:
Exactly, So other people make use of it.
Click to expand...
Click to collapse
It didnt work , may i know from where did you get these files ?
because it should have worked except for the fingerprint sensor
i guess the imei baseband file must be on preloader
rohit4989 said:
It didnt work , may i know from where did you get these files ?
because it should have worked except for the fingerprint sensor
i guess the imei baseband file must be on preloader
Click to expand...
Click to collapse
It's my own partitions.
What is the issue?
Chaitanya Dixit said:
It's my own partitions.
What is the issue?
Click to expand...
Click to collapse
Ok when did you make this partitions backup ?
rohit4989 said:
Ok when did you make this partitions backup ?
Click to expand...
Click to collapse
About 1 month back.
Chaitanya Dixit said:
About 1 month back.
Click to expand...
Click to collapse
You didnt update your oneplus at all ? You just kept it like that for a year ? Can you give proof that it was backedup 1 month ago ?
See post by JimmyTian on Oneplus 11 Forum:Post Link
Could someone with an original Oneplus 11R (CPH2487) with root access help extract and share their ocdt.img
Using ADB:
Code:
adb shell
su
dd if=/dev/block/bootdevice/by-name/ocdt of=/sdcard/ocdt.img
exit
EDIT: CPH2487 ocdt.img #1 added (not working, need another img for byte comparison)
simima30 said:
See post by JimmyTian on Oneplus 11 Forum:Post Link
Could someone with an original Oneplus 11R (CPH2487) with root access help extract and share their ocdt.img
Using ADB:
Code:
adb shell
su
dd if=/dev/block/bootdevice/by-name/ocdt of=/sdcard/ocdt.img
exit
Click to expand...
Click to collapse
Thanks for the help, just wanted to make sure you have the original Indian variant of 11R?
simima30 said:
Thanks for the help, just wanted to make sure you have the original Indian variant of 11R?
Click to expand...
Click to collapse
dump made from original 11r indian version , not ace2 with Oxygen.
unsubscribe about the result after flashing ocdt img
before flashing the new ocdt.img, do not forget to backup your old one on Ace2
Rastatorba said:
before flashing the new ocdt.img, do not forget to backup your old one on Ace2
Click to expand...
Click to collapse
Yep. Noted with thanks.
Rastatorba said:
dump made from original 11r indian version , not ace2 with Oxygen.
unsubscribe about the result after flashing ocdt img
Click to expand...
Click to collapse
What do you mean by unsubscribe?
simima30 said:
Yep. Noted with thanks.
What do you mean by unsubscribe?
Click to expand...
Click to collapse
about the result, whether it helped or not.
Ah okay, sure. I'll try to get it done within 3 weeks. Meanwhile, anyone who attempts it beforehand please let us know the results.
simima30 said:
Ah okay, sure. I'll try to get it done within 3 weeks. Meanwhile, anyone who attempts it beforehand please let us know the results.
Click to expand...
Click to collapse
please give it a try sooner, this could be a life saver for many of us
After flash global ocdt - screen not showing anything, but phone is booting
I reboot phone to bootloader (on screen still nothing) and just restore original ocdt
GTAstar said:
After flash global ocdt - screen not showing anything, but phone is booting
I reboot phone to bootloader (on screen still nothing) and just restore original ocdt
Click to expand...
Click to collapse
that's too bad, i was hoping it would solve the screen flicker for good
GTAstar said:
After flash global ocdt - screen not showing anything, but phone is booting
I reboot phone to bootloader (on screen still nothing) and just restore original ocdt
Click to expand...
Click to collapse
Did you flash it in both fastbootd and fastboot enhance?
simima30 said:
Did you flash it in both fastbootd and fastboot enhance?
Click to expand...
Click to collapse
Yes
After trying - phone stop powering on, official flash through edl don't recognise phone
How can I enter fastboot mode when I reach the recovery screen and select the language, but there is no fastboot option available?
Use ADB on your pc while connecting your phone to it.
Just follow this post: Link
waiting for the solution
Dude, what you guys need is that same file but from Color OS, because it could be hardware difference too... And it works normally on Color OS for this model, so it should technically work, if it is compatible with Oxygen OS
We need the odct.img file of original 11R OxygenOS devices. We can obtain the ColorOS IMG already.
jopac84 said:
Dude, what you guys need is that same file but from Color OS, because it could be hardware difference too... And it works normally on Color OS for this model, so it should technically work, if it is compatible with Oxygen OS
Click to expand...
Click to collapse
I thought the issue is caused by ODCT not flashing when we flash Color OS to Oxygen OS.
leo52307 said:
I thought the issue is caused by ODCT not flashing when we flash Color OS to Oxygen OS.
Click to expand...
Click to collapse
Which is why we need the OxygenOS OCDT file.
But I'm wondering why @Rastatorba OCDT not working