Related
Hi there,
My phone has android 6.0.1 and i want it downgraded to android lollipop because ive got problems with android 6.0.1.
Im a total noob with all this stuff, so can someone please advise step by step how i can do this? I have the MOTO G 3rd Gen, SKU is "XT1541", Ram is 1GB and ROM 8GB. My current system version is 24.61.55.osprey_reteu.reteu.en.EU reteu. Build number is MPI24. 107-55. This phone will accept any phone network. Can someone please help? thanks in advance!
There are multiple threads discussing downgrading, it can be done if your device has the bootloader unlocked (which wipes data and voids the warranty)... There are some inherent dangers in doing so, some immediate and some long-term dealing with future updates which have the potential to brick the device.
What are the issues you are having, many times it is better to solve those then to downgrade.
acejavelin said:
There are multiple threads discussing downgrading, it can be done if your device has the bootloader unlocked (which wipes data and voids the warranty)... There are some inherent dangers in doing so, some immediate and some long-term dealing with future updates which have the potential to brick the device.
What are the issues you are having, many times it is better to solve those then to downgrade.
Click to expand...
Click to collapse
Some apps wont run well on android 6.0.1 such as facebook etc (personal and buisness use) and my phone generally ran better with the previous android version. The phone does not have a warranty on it anyway so that does not matter. Trust me, it really cudnt be much worse than it is atm, ive factory reset it and its just not up to standard as it was with android 5. I did have android 6.0 which i didnt like and then i got 6.0.1, which was putting ice on the cake, (in a bad way!). I am 1000% sure i want to downgrade my device. Can you help?
Ryanm353 said:
Some apps wont run well on android 6.0.1 such as facebook etc (personal and buisness use) and my phone generally ran better with the previous android version. The phone does not have a warranty on it anyway so that does not matter. Trust me, it really cudnt be much worse than it is atm, ive factory reset it and its just not up to standard as it was with android 5. I did have android 6.0 which i didnt like and then i got 6.0.1, which was putting ice on the cake, (in a bad way!). I am 1000% sure i want to downgrade my device. Can you help?
Click to expand...
Click to collapse
Not much to it... Unlock the bootloader, factory reset, then use the lollipop factory image from the factory images thread, gpt.bin will fail, just continue to flash everything all the way through. Follow the instructions in how to flash factory images, it's all done in fastboot.
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Not much to it... Unlock the bootloader, factory reset, then use the lollipop factory image from the factory images thread, gpt.bin will fail, just continue to flash everything all the way through. Follow the instructions in how to flash factory images, it's all done in fastboot.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
Thanks. But can you explain all that in more detail step by step? I need clear instructions on how to do all that as ive literally no idea about anything.
Ryanm353 said:
Thanks. But can you explain all that in more detail step by step? I need clear instructions on how to do all that as ive literally no idea about anything.
Click to expand...
Click to collapse
No offense, but this is not something to be taken lightly... there are many steps.
First, backup all your data... it will be lost.
Start by reading the first few posts in this thread... This will give the basics of what is needed to be done, what tools you need, how to do it, and the factory firmware images (you will need the correct one for your device, all the ones available are in this thread.
Next, read the first two posts in this thread... this is the instructions in detail of exactly how to flash a firmware image. Pay attention to the warnings and follow the linked threads with more information and make sure you understand all of it.
Once you have read and understand this part, you need to get fastboot working... this tool is essential to making all this work. Both of the threads I mentioned above have links to the drivers and Minimal ADB & Fastboot you will need. Install them and make sure they are working.
Now you can unlock the bootloader, this will wipe all data on your device. The instructions and process are done directly with Moto here.
Once you have unlocked the bootloader, reboot and start the bootloader and follow the instructions in the threads above, noting that the part where enter the command "fastboot flash partition gpt.bin" will likely fail because you are downgrading, but no other pieces should fail, if they do enter them again (radios are known to need to be done 2-3 times sometimes before taking), and continue all the way to the end. Pay attention to the number of sparcechunks in your image, it can will vary and you need to flash all pieces in order for your device, there could be anywhere from 5-9 pieces.
Keep a log of everything, it is much easier to tell what happened if something goes wrong by looking at the terminal log (scroll back of the terminal window) than just guessing.
TBH... I am not endorsing this method, but it generally does work, and although it is difficult to brick the Moto G 2015 it is not impossible. After you are done, you will need to root the device and freeze the updater service so you are not constantly prompted to update, and taking an OTA update can be problematic since your bootloader and/or partition table will not match the rest of the ROM correctly.
Personally I think since you have to unlock the bootloader anyway, you are probably better off just looking for a custom ROM like CM13, Resurrection Remix, or something like that since there are lots of rock solid Marshmallow aftermarket ROMs. Or if you are dead set on Lollipop, using CyanogenMod 12.1 instead of downgrading.
I know there is a downgrade utility out there, and not to take away from the developers work but I would suggest avoiding it.
Hi everyone,
been looking around and found a lot of stuff to return to stock ROM and so I don't know what to really do...
here's the situation :
i'm running Kangvip B180 on NXT-L29 and would like to return to stock in order to upgrade to nougat the official way.
TWRP 3.0.2 installed
Bootloader unlocked
Rooted
could someone explain or point me to a good tutorial so I can go back to stock and then upgrade normally please ?
(I know what I need is explained somewhere, but all those posts about bricked devices and different methods to do something are just messing with my head and I don't want to screw up)
Any help appreciated
Solved
Oxipitale said:
Hi everyone,
been looking around and found a lot of stuff to return to stock ROM and so I don't know what to really do...
here's the situation :
i'm running Kangvip B180 on NXT-L29 and would like to return to stock in order to upgrade to nougat the official way.
TWRP 3.0.2 installed
Bootloader unlocked
Rooted
could someone explain or point me to a good tutorial so I can go back to stock and then upgrade normally please ?
(I know what I need is explained somewhere, but all those posts about bricked devices and different methods to do something are just messing with my head and I don't want to screw up)
Any help appreciated
Click to expand...
Click to collapse
Hi guys,
I managed to go back to stock.
For those who are like me, here's what got me sweating but was ok
- fastboot flash stock recovery
- previously add an update.app in the dload folder on external SD (B180)
- rebooted with the 3 buttons method
- let it go through the update
- go to settings in order to get the updates available
- it went from B192, to B320 and finally B560
I didn't format anything till being on B560. Things were ****ing slow and crappy while doing the updates so don't worry
once I was on B560, I went down to the parameters and did a factory reset.
everything seems ok now, and I also solved my problem with the Gear S3 I had (not connecting to the mate)
Hope it helps anyone having these sort of problems
Hi,
iam glad this place still exits
I've got a S6 (SM-G920F), more or less a testing-device (poor Batterie^^) . It was on Android 7 Stock, may not updated for 6month+, not 100% sure . Was my first mistake, i don't know any more details...
First i tried a few old stock from sammobile (Android 5.1.1 etc.) and tried to flash with odin. As you may guess it didnt work. I thought "Stocks - should be easy " and there are many outdated guides who tell this. I searched for the error messages (onscreen) and found hints that this problems could be caused by Bootloader who deny downgrading, may also for good reasons. I didnt read any deeper, as i found this Guide here: https://forum.xda-developers.com/galaxy-s6/help/guide-downgrade-sm-g920f-nougat-to-t3639253
Followed this Guide with https://www.sammobile.com/firmwares/galaxy-s6/SM-G920F/DBT/download/G920FXXU2COH2/54694/ as "Source". I worked with the engineering bootloader and the told parts from the Stock. RecoveryMode was broken, but systems seems boot fine and no obvious Errors or Problems. A good guide for that goal, but no guide can teach me whats going up in detail. I want to understand a little bit more, and not searching for a "from any to ANY guide"
Actually iam trying to get on 6.0.1 Stock, but this guide doesnt work for me with a few stock-roms, not booting.
Flashing complete stocks with odin still fails. Flashing dont start or fail at hidden.img.
I came to this page with my first xda, later flashed a lot with my Galaxys...S2-S4, also custom roms- but stayed on stock at some point. So i should have basic knowledge, but i realize its outdated and there a few new "stummbling blocks" etc. Therefore i decided to get more in detail and ask here, before trial and error with other ways (like flashing with recovery)may leads to a brick. Not founded deeper informations myself. In the past i knew which parts a rom/firmware could have and their functions and whats possible with it.
Somebody here with time to help? Where can i find infos which bootloader i got, which others i may can flash (on what way) and which one is working with which Rom^^ Hope that the device wasnt on newest BL, and i still have the choice. Is the Kernel or other parts important as long as iam only trying to jump between stocks?
I backuped efs-partition with TWRP and stored the backup folder on PC, is that enogh to be prevent IMEI lost?
Hints or Links could be enough in some cases.
Thanks for reading and your work
Mattezh said:
Hints or Links could be enough in some cases.
Thanks for reading and your work
Click to expand...
Click to collapse
G920f is international version, so compatible with all roms. Frankly speaking, flashing is basically same as s2 etc. If you're on nougat, then nougat bootloader.
Idk why u want to go to Marshmallow, but some guys managed to flash a Marshmallow custom rom directly from nougat. It's called xtrestolite. It has no support whatsoever. https://forum.xda-developers.com/ga...xtrestolite-deodexed-mod-edition-1-0-t3094423
For TWRP & ROOT, follow the steps in this video https://youtu.be/BV1ELmu8T0I & that's it.
DO NOT USE supersu. USE & flash latest Magisk v15.0+ (stable) from here https://forum.xda-developers.com/app...80cb6-t3618589 Download latest Magisk Manager as well
So the steps are:
From the links in the video, download the specific twrp for g920f. This one: https://eu.dl.twrp.me/zeroflte/twrp-...roflte.img.tar The first file.
Install the Samsung drivers from the link in the video on your pc.
Download & extract Odin.exe.(link in video. Use the same version)
Enable usb debugging on your phone.
Put your phone to download mode
Start odin. Follow the steps in the video to install twrp
When install is complete, immediately reboot to twrp to flash latest Magisk. Wipe Dalvik.
Reboot. Install latest Magisk Manager
Check status in the Magisk Manager.
Done.
If not rooted, flash magisk.zip again in twrp
SuperSu gave problems to some users. Magisk was successfully installed in the first shot!
Nougat roms I'd suggest to flash. They're in S6 unified forum:
MiPa rom, A8 2016 v2, OdexLite v4.1
Try the Nougat roms I've mentioned since you're already on Nougat.
BTW Don't flash any kernels. Stay with those which came with the roms
Hello Guys,
i had bought an Huawei P20 about an year ago. Now you know with all of this "USA-Huawei" Trouble going on, the thought came to my mind that i better start unlocking bootloader and be prepared to flash custom rom if worst come to worst. so far, so good.
now i started looking around if there is an easy method of getting the bootloader unlocked. but oh my, the huawei company is very friendly to us users and say "no, you wont get any unlock code from us anymore". so screw that.
now i want to try some experimental stuff. it looks like this:
my Smartphone has currently the version EML-L29 8.1.0.168(C432). I bought some Credits (i think it is that thing for $4) from DC-Unlocker. Yeah yeah i know, there they say "no support for Huawei P20!!!". But i still want to try. Well i tried, but it doesnt work - what you should expect.
now i read from some other website that there is another way of unlocking it. i only read it diagonal but the one thing i read was the information "unlocking bootloader is only possible till firmware version june 2018". so i jumped to an maaybe interesting conclusion about unlocking the phone with DC-Unlocker or HCU (whatever, i guess maybe both use the same method anyway).
if i do an rollback to the old firmware version *before* June 2018 on the device, wouldnt it be possible to do the unlock? Because the security patches that preventing it unlocked arent on the device then.
So what i have done so far is loading the old firmware version 8.1.0.128(C432). But the source is saying that it is coming from "Asia" but in the next line it reads "Asia, Europe" etc. - do they mean that this version is universal or do i run in trouble if i install one that is having the wrong area?
the next thing that kinda baffles me... all guides are sayin "copy the extracted dload folder to your sd-card". even the p20 guides do that. but.. well you know, the p20 device doesnt even have sd-card support. so how are you intended to use it then? i wonder about that a bit.
i dont think that without unlocked bootloader, flashing an original OTA full update would be impossible. but im not really sure how. there is this shady menu you can reach if you call this strange numbercode. but im very unsure if that will really work out. the phone (it is still a phone without SD-Card-Support) even has the option "apply update from sd-card". so im wondering how this feature they implemented in the original software is intended to use at all. maybe i should push the dload folder on the internal storage? i dunno.
i read about another possibilty of flashing stock roms. they say you can do it per adb command. so no problems would be here, i have adb and the hisuite and all already set. but i have absolutely no idea if that is possible without unlocked bootloader. so the questions arose from my mind are those:
- does an stock rom image from possibly/maybe asia would do any harm to my device like it is getting unbootable or anything like that?
- is it possible to flash an image older android stock rom with methods like this special menu on the device or the adb load?
- do you all think that my plan of downgrading the phone in order to get the bootloader code would work?
i'm looking very forward to your answers )
no_monday said:
Bootloader Unlocking through Downgrade possible?
Click to expand...
Click to collapse
No. Sorry. There's no solution. Reason: It would appear in this forum within minutes and thousands of people would be happy to unlock their bootloaders. Many Huawei-Owners here on XDA invested a lot of brain power to find a way. Noone succeeded. No bootloader code, no unlock.
If you still want to play around with firmwares, please inform us about any progress.
Jan Philipp said:
No. Sorry. There's no solution. Reason: It would appear in this forum within minutes and thousands of people would be happy to unlock their bootloaders. Many Huawei-Owners here on XDA invested a lot of brain power to find a way. Noone succeeded. No bootloader code, no unlock.
If you still want to play around with firmwares, please inform us about any progress.
Click to expand...
Click to collapse
okay so there are basically no real information. look, i dont expect anyone to say like "oh there is an easy method xy" because i know it doesnt exist on this moment in time.
however i made an percent of an progress, it is more a thing for other interested custom rom modders out there.
i downloaded this update.zip and there are all kinds of howtos on the internet about it. the one thing i did is basically create the dload folder. then i put the extracted update.app in there. i rebooted the phone with power, vol down + vol up. i released the power button after the vibrating. the flashing screen indeed appeared! but something very strange has happened and i have no explanation what have happend.
so the emui updater appeared. there was this emui logo in the middle, the circle building up around it. but then it stopped at 5%. i really got panicked that im about to brick my device. so in an mad attempt i wanted to stop the update and power off the phone. glad i didnt do it. the phone always said if i tried to press the power button long enough "the system will crash if it is powered down". i stopped - but i tried it serveral times to stop.
now the strange thing is.. it stuck relatively long on this screen. but after a while (i guess it was 5-6 minutes) it suddenly got dark. and the battery was at 100%, so it wasnt a faulty battery. i just wondered. the phone - other than i would expect - rebooted. after a short while of the logo flashing (for about an half minute) it finally started. first i didnt have any connect to GSM Network. but after a short while that was okay too. all apps are still there. i looked at "about" and the version is still the same as before.
do someone have any imagination what has happened there? so apparently the phone *does* try to install something on this method, but the method seemed to fail. or is there any knowledge out yet for update logs that are getting generated by this process? i try to find any hint in order to tackle this problem atm.
and one thing is still on my mind.. could it be that the update is already through and i just didnt realized it yet because these other custom files werent changed? i mean that could be an possibility to say the least. anyway, i will try to use hcu now if maybe sth has changed. and i give kingoroot as well a shot if this buddy finds everything about rooting the device. maybe with root rights through exploit i can get further.
no_monday said:
okay so there are basically no real information. look, i dont expect anyone to say like "oh there is an easy method xy" because i know it doesnt exist on this moment in time.
however i made an percent of an progress, it is more a thing for other interested custom rom modders out there.
i downloaded this update.zip and there are all kinds of howtos on the internet about it. the one thing i did is basically create the dload folder. then i put the extracted update.app in there. i rebooted the phone with power, vol down + vol up. i released the power button after the vibrating. the flashing screen indeed appeared! but something very strange has happened and i have no explanation what have happend.
so the emui updater appeared. there was this emui logo in the middle, the circle building up around it. but then it stopped at 5%. i really got panicked that im about to brick my device. so in an mad attempt i wanted to stop the update and power off the phone. glad i didnt do it. the phone always said if i tried to press the power button long enough "the system will crash if it is powered down". i stopped - but i tried it serveral times to stop.
now the strange thing is.. it stuck relatively long on this screen. but after a while (i guess it was 5-6 minutes) it suddenly got dark. and the battery was at 100%, so it wasnt a faulty battery. i just wondered. the phone - other than i would expect - rebooted. after a short while of the logo flashing (for about an half minute) it finally started. first i didnt have any connect to GSM Network. but after a short while that was okay too. all apps are still there. i looked at "about" and the version is still the same as before.
do someone have any imagination what has happened there? so apparently the phone *does* try to install something on this method, but the method seemed to fail. or is there any knowledge out yet for update logs that are getting generated by this process? i try to find any hint in order to tackle this problem atm.
and one thing is still on my mind.. could it be that the update is already through and i just didnt realized it yet because these other custom files werent changed? i mean that could be an possibility to say the least. anyway, i will try to use hcu now if maybe sth has changed. and i give kingoroot as well a shot if this buddy finds everything about rooting the device. maybe with root rights through exploit i can get further.
Click to expand...
Click to collapse
It seems you have a couple of questions, pal, I answered to the first one (Bootloader Unlocking through Downgrade possible?). All I said is that it's impossible to unlock the bootloader through a downgrade. If you read all the how-to's you should have noticed that FirmwareFinder doesn'st work anymore since EMUI 9.0. This Information simply means Huawei doesn't allow us to flash updates on our own anymore like we did before. For sure there are some guides how to rollback to Android 8 but even this changes nothing to the bootloader.
Sadly I have no answer to the other questions about the strange behavior, it sounds pretty odd. Never heared something like this. But good luck fixing your phone anyway.
well i found out a couple of things now.
first thing: you know the service menu when you try to apply a zip archive from sd card? well you wont be able to use it UNTIL you use an usb-otg cable and an exFat formatted USB-Stick. Next thing to know is, you have to use the right images. there seem to be an kind of rule how this images are supposed to be and the image i found was from an russian firmware download site it was linked here in the forum in a thread. so i did choose "apply zip from sdcard" and .. IT DOES! the device rebooted, the stick flashed and the flashing process occured! and guys, im back to Version EML-L29 8.1.0.128(C432)! it is clearly stated in the build version view in settings. so.. i guess you *can* roll back even without firmware updater.
so far so good. but lets get back to the problem with the Bootloader. sadly Jan Philipp was totally right.. the bootloader cant be unlocked even in this version with the security patch of 5. may 2018. that is kinda sad. even kingoroot is still no different from before. i guess i have to search now for an way to get the system rooted. however, it must be easier on an earlier security update stage like now instead of the future versions of emui 8.1.
edit: another strange thing i discovered so far is that after this restore.. the play store wasnt able to connect to the google server until i gave permission to a few google processes to calendar and file access (i wonder what that is all about). maybe it has something to do with incompatibilities in the rom versions but now it works just fine as it should).
"unlocking bootloader with exploit is only possible till firmware version june/july 2018" does not apply to 2018's devices with kirin970, kirin980 & kirin710.
You are with kirin970.
So to unlock your kirin970, the only way for now is to wait for 3rd party seller to hypotheticaly start back their dervice:
- In the last 6 months there was only 2 'windows' which lasted 3 or 4 days where you could order your bootloader's unlock code by imei (from 5 to 124 us$).
GuestD0711 said:
another strange thing i discovered so far is that after this restore.. the play store wasnt able to connect to the google server until i gave permission to a few google processes to calendar and file access (i wonder what that is all about). maybe it has something to do with incompatibilities in the rom versions but now it works just fine as it should).
Click to expand...
Click to collapse
Google Play services require all permissions, otherwise won't work.
I also been searching on how to unlock the bootloader and found no solution or hope. I guess we are stuck with EMUI forever.
Reply from Huawei:
You can roll back to earlier versions of EMUI software, but you have to roll back one version at a time. However, our earlier phones operate exclusively on Google Mobile Services so removing it would limit the functionality extremely, however, we do have a range of new devices that no longer rely on Google Mobile Services and use Huawei Mobile Services instead - such as our P40 series.
Here are the instructions for rolling back software:
[Rollback Guideline] EMUI 9.1 (Android 9) Rollback to EMUI 9.0 (Android 9) Operation Instruction
EMUI 9.1 (Android 9) can now be rolled back to the official version of EMUI 9.0 (Android 9) using HiSuite, without downloading any intermediate packages. To ensure that the rollback succeeds, read the instructions carefully and perform the steps as instructed.
1. The following are precautions for roll-back.
a. Rolling back to an earlier version will erase all data on your device. Use an SD card, computer, or Cloud storage to back up all important data before rolling back your phone, and make sure all backed up content is complete and effective.
b. Use a computer running a Windows operating system to visit http://consumer.huawei.com/minisite/HiSuite_en/index.html and download the latest version of HiSuite. If HiSuite is installed on your computer, click the version number in the lower left corner of the page to check if it is the latest version. Make sure HiSuite version is 9.1.0.303 _OVE or above.
c. Before rolling back the phone, make sure your phone has not been upgraded using non-official updates. Otherwise, the roll-back may fail and unknown issues may be introduced. If you have used non-official packages to upgrade your phone, it is recommended that you go to an after-sales service center to roll back your phone.
d. Before rolling back your phone, make sure that your phone system has not been unlocked or rooted. If the system has been unlocked or rooted, it is recommended that you go to an after-sales service center to roll back your phone.
e. Before the roll-back, restore the phone to factory settings to make sure there is enough storage space.
f. Make sure the battery level is more than 50%.
Hi All,
I need assistance to update my EML L29 Huawei P20 phone.
The phone is Locked and FRP Lock
Issue the phone is always booting into recovery mode and not into the main screen.
I tired flashing via CMD using twrp.img file but its not writing.
Need help
I followed a tutorial by Max on XDA's youtube channel (I'm a new user so unfortunately I cannot provide the link but I'm sure you can find it if you wish)
First mistake was going into this thinking it was a simple process to unlock bootloader, install TWRP, and root with Magisk . . .
Anyways I was looking for the fast boot files linked in the description of the video (my build number is 10.3.4 GM21AA) But could not find any past 10.0.5 (which was the most recent uploaded). [Cannot post the link however it is posted on androidfilehost]
I decided to go with the 10.0-GM21AA-OnePlus7ProOxygen_21.O.20_OTA_020_all_1909172051_db7a3f61-FASTBOOT.zip file, i dug into the images.zip folder to find the boot.img file (which is the one I used in my rooting process)
I followed the steps exactly as Max did them in his video but ended up with no camera working, no cellular network, cannot toggle the wifi on, no sound through speakers . . . now suddenly my phone has become a standard wallpaper background and nothing else.
Freaking out (but also I should've known what i was getting into being as naive as I am) I contacted OnePlus Support which basically told me my warranty is void now . . .
I guess I have no choice but to figure out how to root this properly or my 1000$ phone goes into the trash
Do I need to find the boot.img file for the One Plus 7 Pro Oxygen 10.3.4 GM21AA? Was that the mistake I made that messed up everything by deciding to flash the wrong boot.img
Any help is much appreciated!
Thanks guys!
https://www.xda-developers.com/unlock-bootloader-root-oneplus-7-pro/amp/
GeekMcLeod said:
https://www.xda-developers.com/unlock-bootloader-root-oneplus-7-pro/amp/
Click to expand...
Click to collapse
Thanks for your rapid response however that doesn't seem to do it for me I still cannot access camera, wifi, phone calling, and there is no sound . . .
[EDIT] I think I have discovered the problem however I do not know how to fix it. I flashed the wrong boot img file. Issue is that I do not know where to find the boot.img for 10.3.4
The best medicine against such issues is to MSM tool. I'm using you have the 1917, 1910 models i.e. the global editions and not the EU version. If you have EU version, I don't know if the MSM tool will work. Next, if you have successfully complete the MSM setup, then you can go about rooting the device by following this tutorial https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
On a side note, I have been swinging between root and full stock and frankly I don't see the real need to root the device. Stock unrooted OOS is really a good OS and rooting really doesn't add much value IMO.
rapurepie said:
I followed a tutorial by Max on XDA's youtube channel (I'm a new user so unfortunately I cannot provide the link but I'm sure you can find it if you wish)
First mistake was going into this thinking it was a simple process to unlock bootloader, install TWRP, and root with Magisk . . .
Anyways I was looking for the fast boot files linked in the description of the video (my build number is 10.3.4 GM21AA) But could not find any past 10.0.5 (which was the most recent uploaded). [Cannot post the link however it is posted on androidfilehost]
I decided to go with the 10.0-GM21AA-OnePlus7ProOxygen_21.O.20_OTA_020_all_1909172051_db7a3f61-FASTBOOT.zip file, i dug into the images.zip folder to find the boot.img file (which is the one I used in my rooting process)
I followed the steps exactly as Max did them in his video but ended up with no camera working, no cellular network, cannot toggle the wifi on, no sound through speakers . . . now suddenly my phone has become a standard wallpaper background and nothing else.
Freaking out (but also I should've known what i was getting into being as naive as I am) I contacted OnePlus Support which basically told me my warranty is void now . . .
I guess I have no choice but to figure out how to root this properly or my 1000$ phone goes into the trash
Do I need to find the boot.img file for the One Plus 7 Pro Oxygen 10.3.4 GM21AA? Was that the mistake I made that messed up everything by deciding to flash the wrong boot.img
Any help is much appreciated!
Thanks guys!
Click to expand...
Click to collapse
Roll back to 10.3.3 and use the patched boot.img from here: https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
Thanks everyone. I finally solved the issue
From what I know, it's practically impossible to brick a Onleplus, I lost two Samsung's, and a LG, relocking bootloader while rooted, rushing to get the phone up, and forgetting to uninstall Magisk, TWRP, haven't ever had that problem with OnePlus or Xiaomi devices though. I've relocked this bootloader a couple of times while rooted, and nothing happened. Root is still very necessary for me, I don't buy anything I can't hack. I just noticed icon burn-in on my notifications bar, really pissed.