Related
Hello, just registered for an account here after trying to fix my problem from 2-3 days worth of "google-ing" related articles and threads of my current problem. Although there has been too many boot loop complications to count, I couldn't seem to stumble upon a scenario in which the user's circumstances were related to my own specifications (I am aware of how important it is to review and research before creating a new thread).
I will proceed to list in, chronological order, the recent alterations my phone has undergone within the last couple of days...
1. Giving the "bootloader" the Boot
I've had my At&t One X for about five to six months and have gotten pretty comfortable with the Android platform, and decided to research in the journey that any brave "pioneer of technology" would partake in, gaining super user-access through rooting! Of course, at the time, I knew as little about the topic that I could have safely assumed that "to root" a phone had to have involved planting your device in soil, adding water, and providing ample sunlight.. SO I began to research and learned quickly that one would need to "unlock the boot loader" on their device before they could proceed to rooting. I figured that I had a green-thumb when it came to following instructions and carried on to "HTCdev's" website to unlock my phone. I installed Sync, updated my Java, and downloaded Android SDK.zip onto my (Windows PC). In the end, I learned both: how to use fastboot in my pc's command prompt, and that my phone was apparently incompatible to be unlocked. At the end i received an error message "Error Code: 160 Error Reason: MID Not Allowed".
2. Root of my Problems
Although I had failed to unlock my phone's boot loader, I was still determined to root my phone and through more research I found I could still "root" my phone, but I would have less options when it comes to flashing roms and some other jive. Since I was only needing root to be able to run "Sixaxis" (to sync a PS3 controller as an IME for my phone) at the time, I was okay with that.
I found a simple root website (Can't upload link due to my "ten-posts-cherry" not being popped yet, but the link was named "How to ROOT HTC AT&T One X with one-click method" in Google) and followed the steps carefully. I downloaded "root-one-x.zip", extracted files, and double-clicked on the batch file. My phone restarted a couple times and everything seemed to run smoothly after rooting.
3. Creative Control Causes Chaos
After being rooted for a week or two, I started to delve into the tweaking possibilities my phone could endure now, such as the ability to change fonts (when I should've been taking advantage of apps like Titanium Backup). I searched the play store for a while and came across an app called "Custom Android Font Switcher" (by Bentotbox), which claimed compatible with my device and boasted the simplicity of switching to hundreds of new fonts for your device. (Seemed pretty neat!) It did note the requirement of "root with busybox?" but I continued to download and install. I launched the app, browsed some obnoxious fonts, settled on a more simplistic variance of my original, and loaded the new font. When finished loading I noticed the new font had correctly taken effect on most parts of my phone, with the latter erroneously displaying in Chinese-like characters. (wasn't sure if it was Japanese or Korean, but in my opinion they all look the same only joking..) Since I am not talented in reading any other language thoroughly enough, I went back into the app to find a way to revert back to the original font, yet found no way to do so. My next decision was to un-install the app hoping that might bring my original font back, and when it didn't I decided a Restart would do the trick! Well now it seems my phone has learned a new trick indeed! Being able to continuously "loop" the loading screen. (Boots to welcome screen, then At&t screen, then flips over to a screen that just shows "ONEx" and stays there until I either: power-down the phone to start the process again OR smash with a hammer)
4. Trial and Error to no Prevail and Much Error
My phone has been in a bootloop since about 2-3 days ago, and like I mentioned, I have searched many forums and threads for solutions (Which I've done all throughout my technological life and usually had no problem finding out how to do something, whether it would be changing a radiator to performing open-heart surgery on a monkey). This is actually the first time I've posted on any forum for help since I usually find a way to fix issues myself from other user's parallel problems.
So far, I have tried the following with no resolution to my phone's boot revolution:
- Enter "Recovery" mode by holding volume-down while powering on the phone.
- Choosing the "Clear Storage" in the phone's hboot menu.
- Choosing the "Factory Reset" in the phone's hboot menu
- (I've read many places to clear cache and dalvic cache?, but cannot seem to find these options)
- (I've read that one can re-flash? CWM recovery to fix loop, but I couldn't do so because it apparently Requires an Unlocked Bootloader)
- Been able to stop the loop by choosing the "Power-Down" option in the hboot menu (Also enables me to charge phone via wallcharger! Also noticed other people on the internet having troubles finding a way to charge their phone in a boot loop. Maybe I stumbled on to a potential universal solution?)
- When I choose the actual option "Recovery" in the hboot or (recovery mode) the screen goes black and eventual shows a phone icon with a red triangle on the screen and stays there until I re-boot. Is this supposed to be the Recovery page?
Conclusion
I know I've made a pretty long "first-post", but I wanted to make sure I gave all the details that might matter when trying to diagnose my problem and might help others with a problem like mine. So anyways, thank you for reading and I appreciate your help in advanced!
-LawyerLounge
What software version were you on? 2.20 is not rootable, and previous versions (1.73, 1.85) correspond with different root methods.
The AT&T One X needs to be rooted and SuperCID before unlocking the bootloader, so that is why unlocking the bootloader failed.
What you have (red exclamation mark) is the stock recovery.
I'm betting that getting the RUU for your particular firmware version and running it, will get your phone back to working order. RUUs and other resources can be found in my index thread: http://forum.xda-developers.com/showthread.php?t=1671237
Verifying Software/Firmware version for RUU
redpoint73 said:
What software version were you on? 2.20 is not rootable, and previous versions (1.73, 1.85) correspond with different root methods.
Click to expand...
Click to collapse
Are you saying that the website I used to root my device (Believe it was ABD Daemon root) shouldn't have worked since if I was on 2.20 it couldn't have been rooted and if I was on (1.73 OR 1.85) a different website/rooting method than I used would've been necessary to root my device?
Also after rooting I wanted to make sure my device was rooted, and searched how to find out. I downloaded an app Root Checker and it verified I had Super user root access or whatnot.
redpoint73 said:
I'm betting that getting the RUU for your particular firmware version and running it, will get your phone back to working order. RUUs and other resources can be found in my index thread: http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
Which RUU do I need? Do they correspond to the software version I am running? Or is firmware version different? Since my phone is in a bootloop are there other ways to determine which software/firmware version I am using?
Once I have the correct RUU to download, do I just boot the device in fastboot and use command prompt to "zap?" it over?
Thank you redpoint73,
-LawyerLounge
Thanks for what you did provide
I installed 1.82 RUU onto my device (found out my version was 1.73) and it factory reset my phone! Thank you for your help, could have had more help explaining how to go about choosing correct RUU, but I figured it out through process of elimination and got the right RUU i guess.
Thanks for your partial help,
LawyerLounge
LawyerLounge said:
Are you saying that the website I used to root my device (Believe it was ABD Daemon root) shouldn't have worked since if I was on 2.20 it couldn't have been rooted and if I was on (1.73 OR 1.85) a different website/rooting method than I used would've been necessary to root my device?
Click to expand...
Click to collapse
No what I am saying is "what firmware are you on", lol
A questions you never did answer.
And no, 2.20 is not rootable, and I don't think you out of everyone here magically found a 2.20 root solution when nobody else (including very talented and experienced developers) has been able to.
---------- Post added at 09:16 AM ---------- Previous post was at 09:12 AM ----------
LawyerLounge said:
Thank you for your help, could have had more help explaining how to go about choosing correct RUU,
Click to expand...
Click to collapse
I wasn't online at the time you asked the question about the RUU.
---------- Post added at 09:22 AM ---------- Previous post was at 09:16 AM ----------
LawyerLounge said:
Which RUU do I need? Do they correspond to the software version I am running? Or is firmware version different? Since my phone is in a bootloop are there other ways to determine which software/firmware version I am using?
Click to expand...
Click to collapse
RUU for your current version is the best way. Higher numbers will also work, but never lower numbers (downgrades are not normally allowed, without things like SuperCID). But I only recommend running a higher number RUU, if you know what has been changed, and are okay with those changes. For instance, 2.20 plugs the holes by which root was obtained, and also has a patched hboot that plugs the holes by which kernels and radios could be flashed from recovery. So I believe the 2.20 RUU would have worked, but also would have left you stuck without root.
I asked the firmware versions, hoping that you already knew what it was. You really shouldn't be rooting and modding the phone, without knowing what firmware version you are on.
Hi Everyone,
Living in Japan, we have no official channel to purchase a OnePlus handset here.
Really wanted to get a OnePlus 7 Pro as I felt it is the best model on the market as of today.
Knowing that, I got mine on Amazon Japan from a HK online shop which had very good reputation.
Now, the problem is these phones always come already opened as they say they need to confirm operation before sending it.
I have been reading news and article about this where we see more third party companies flash their roms with malware/ransomeware already built in...
In these situation, the best way to clean the phone is to do a full re-install of the OS.
I did review a bunch of article on XDA and it seems that now, due to the A/B partition setup, we can't just use official OnePlus image to load from the fastboot easily.
We have to rely on community provided too and stock rom to be able to do so....
When I raised the question to OnePlus and Oneplus forums, they mentioned to me that installed the updated like here (Page: support.oneplus.com/app/answers/detail/a_id/4312/~/oxygen-os-for-oneplus-7-pro)would do the trick using the local update function.
What I was directed to do is use the recovery boot to delete system settings/cache and everything data user and then, run the local update. Doing so, that would do it while not using community tools.
Here are my questions and which I would hope to get your experience:
1 Is the process I did really does use a brand new clean OS and do not rely/integrate part of the OS that came with the handset originally (that was the target).
2 Is there a way for me using OnePlus only provided tools and image to fully delete the phone and install the OS (maybe I am thinking this too much like a PC which I have more experience with...)
3 The OS looks fine and no strange apps shows up at all but how can I be sure nothing dodgy is running? Is there tools I could use to confirm this?
Sorry if I sound paranoid. Ideally, I understand the best thing to do was to buy directly from Oneplus and work a way to have it shipped to Japan but thought it would be interesting for me to learn more about android.
With previous Oneplus, it was easier as they were provided this type of official file for recovery but they stopped...
Thank you again for your time and hopping to learn more about how new android setup works.
Is the bootloader locked? Is Widevine (Netflix HD) certification still there? You can check these things to see if the phone has been tampered with.
brissoukun said:
Hi Everyone,
When I raised the question to OnePlus and Oneplus forums, they mentioned to me that installed the updated like here (Page: support.oneplus.com/app/answers/detail/a_id/4312/~/oxygen-os-for-oneplus-7-pro)would do the trick using the local update function.
What I was directed to do is use the recovery boot to delete system settings/cache and everything data user and then, run the local update. Doing so, that would do it while not using community tools.
Here are my questions and which I would hope to get your experience:
1 Is the process I did really does use a brand new clean OS and do not rely/integrate part of the OS that came with the handset originally (that was the target).
2 Is there a way for me using OnePlus only provided tools and image to fully delete the phone and install the OS (maybe I am thinking this too much like a PC which I have more experience with...)
3 The OS looks fine and no strange apps shows up at all but how can I be sure nothing dodgy is running? Is there tools I could use to confirm this?
Thank you again for your time and hopping to learn more about how new android setup works.
Click to expand...
Click to collapse
Good questions. Before you start, check the model number of your device through Settings > About. I'm assuming it's the international/global/unlocked version (GM1917).
With regard to question 1, a full build downloaded from the link you provided should contain every part of the OS, and flashing it through local update should overwrite anything that was there before. Before flashing, I would perform a full data wipe through recovery like you mentioned.
Q2: There is an MSM tool that will completely flash a system image for the OP7 Pro. I don't think they're generally intended for public use but they always get leaked anyways. They write an image (in the case of OnePlus, a .ops file) to the phone using a PC and USB connection. Here is a link to a thread which contains the MSM tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
Download the tool for the model of your phone (probably the international, firmware GM21AA), and extract its contents into a directory. In order for the tool to work, you need the OnePlus USB drivers installed on your PC. Plug the phone into your PC with it on, and enable USB file transfer. Open File Explorer and you should see a drive labeled "OnePlus drivers" or similar. Open it and run the driver setup executable file. You'll also need ADB to make your phone reboot into a mode that will allow the tool to perform its tasks. Here is a guide to installing ADB:
https://www.xda-developers.com/what-is-adb/
Once you've set that up, make sure the phone is plugged into the PC and the MSM tool is open. Make the phone boot into edl mode by typing
Code:
adb reboot edl
and once it says Connected next to a COM port in the tool, press start. Don't interrupt the process until it completes the download and the status message turns green. The phone should automatically reboot. This method is arguably more risky than using the local upgrade option, so do it at your own risk.
Q3: Make sure that OEM unlocking is turned off in developer settings and that the bootloader is locked (if the bootloader is unlocked, you'll see a yellow warning message after you power on the device from a power off state). Without an unlocked bootloader it would be pretty difficult to make any deep modifications to the device.
Hi @Zocker1304 and @TManchu,
Please let me thank you very much first for your kind and detailed reply, this is really welcome.
@Zocker1304:
I checked using the ADB/Fastboot connection that indeed, the Bootloader is locked so, that looks good.
Also installed (using a separate Google account) DRM Info app to confirm that the Widevine is properly installed and at L1 level which indeed again, looks good.
@TManchu
Thank you again for your very detailed reply! This was exactly what I needed as information.
I did already exactly as mentioned for the #1 so, it looks I should be good now with a proper rom from OnePlus (and did a full wipe in the Recovery boot mode)
For #2, I think I will skip that since as you rightly said, with #1, it should be fine so, prefer to keep with the recommended step.
For #3, we are covering what Zocker1304 mentioned too and I could confirm it.
My only concern about #3 was that you can actually relock the bootloader but (and please correct me If I am wrong), you can only do so if you are using stock OnePlus images (to date...seems like dev teams are working to have this changed? Bootloader locked with custom firmware?) which then means the image is safe.
I suppose the last item was my only open query for your thoughts but so far, the handset looks fine.
Thanks to you and the community, I have learned about the A/B partition scheme, msm tool, Fastboot/Recovery mode and Bootloader and ADB tools.
It is always good to learn more about the tech we use (especially phones, we have so many sensitive information stored into them today).
Not being careful could potentially means quite a lot of troubles down the road with Ransomeware/data leak tools.
Of course again, I could have simply purchased a JP phone from a brick and mortar shop next to my place and be fine with it. :silly:
brissoukun said:
.
For #3, we are covering what Zocker1304 mentioned too and I could confirm it.
My only concern about #3 was that you can actually relock the bootloader but (and please correct me If I am wrong), you can only do so if you are using stock OnePlus images (to date...seems like dev teams are working to have this changed? Bootloader locked with custom firmware?) which then means the image is safe.
I suppose the last item was my only open query for your thoughts but so far, the handset looks fine.
Thanks to you and the community, I have learned about the A/B partition scheme, msm tool, Fastboot/Recovery mode and Bootloader and ADB tools.
It is always good to learn more about the tech we use (especially phones, we have so many sensitive information stored into them today).
Not being careful could potentially means quite a lot of troubles down the road with Ransomeware/data leak tools.
Of course again, I could have simply purchased a JP phone from a brick and mortar shop next to my place and be fine with it. :silly:
Click to expand...
Click to collapse
No problem! I’ve just done some reading and from what I understand, re-locking the bootloader on anything other than a completely stock ROM will result in a bricked phone. I believe this is due to the way Android handles data encryption. If what you’ve heard is true, being able to lock your bootloader on a custom ROM would be great for device security. However, should something go wrong with the ROM having a locked bootloader might make it more difficult to fix.
I know that there are ways to sign system and boot images so that you can lock the bootloader with them installed, but I think that would still show a warning though I'm not sure.
Anyways, if all the build dates and numbers in the system info are correct, the firmware should be stock and as long as the bootloader is locked too, I don't believe you can tamper with that.
Hi Gents,
Thank you very much for the answer to the thread and much appreciated.
Apologies for not getting back to you all earlier as yesterday was family day...haha!
Well, since things looked good on the OS and the build, I went ahead and started to use the phone properly setting up my accounts. It did give me some incentive to get all my sensitive accounts setup with 2FA so that in case I get hacked with my passwords in the future...they would still need the 2fa (using Google Authenticator).
I did check also all system apps/running process and didn't see anything shady.
Just for reference, here were the type of articles I was refering too for the OS being plagued with malware even out of the box:
Page_theverge.com/2019/6/6/18655755/google-android-malware-triada-ota-rom-ads-spam-oem (sorry gents, new account, cannot put links yet)
However here, it seems it is due to lax review from the maker to third party tools which were including malware...
To have the same level on the oneplus I bought from the HK shop, they would have needed access to OnePlus Dev team to inject the malware in official image (knowing anyway I have re-installed a new image from the local update).
Otherwise, I was reading on the web about the fact to relock the bootloader with a custom roam and there seems to have a lot of messages but not concrete steps. It seems it depends a lot on phone model and brand.
When you are checking
Page_gizmochina.com/2019/06/10/relock-bootloader-oneplus-7-pro/
This is where you can read at the end:
"The above method only works if OnePlus 7 Pro is running on stock recovery and stock firmware. The ability to relock devices running custom recovery is expected in the next few weeks. "
That was published last month so, not sure if they got this to work on the OnePlus 7 pro yet.
So that's it, I am now using my new device which looks to work great and hopefully, won't get any bugs down the road.
I appreciate you taking the time to get back to me and will continue to learn about android.:good:
So... I unlocked the bootloader, but I haven't found a way to get root yet. There's no TWRP available, and I can't find a useable boot image. I tried to copy boot_a and boot_b using dd in an ADB shell, but all I got was "permission denied". There don't seem to be any stock images available, so I'm not sure where to get a boot image until there's an OTA update, but even then I might not be able to pull it from the data partition without root. Argh.
Also, Motorola has kernel source at https://github.com/MotorolaMobilityLLC/kernel-msm, but the last commit was over 2 months ago, and I can't find a default config for racer.
https://mirrors.lolinet.com/firmware/moto/racer/official/
Firmware for device
Thanks for that. I also found Lenovo's support app at https://support.lenovo.com/us/en/downloads/ds101291 (Lenovo owns Motorola.) Too tired to mess with this now. I'll try it later.
You can retrieve full ROM and boot.img from LMSA using rescue mode.
You can run rescue to update the ROM, observe the download process, copy the .zip once it reached 100% as well as retrieve boot
Copy boot.img to phone and patch with Magisk Manager, and copy back to host computer
Flash the patched boot
Make sure ADB is up to date
adb reboot fastboot
fastboot flash boot patched_boot.img
Yup, it's working now. Thanks all.
I have successfully rooted mine and having adaway installed
Can you install stock android 10 or even android 11 now?
ROM updated
Since Motorola/Lenovo updated the Edge since this was first posted, I would like to add that coming across the boot image file is a bit more scarce than the original release version for the Edge. However, using Rescue and Smart Assistant, you can downoad the latest ROM version. You may now use the boot image file in the downloaded folder [ProgramData\Lenovo\Downloads\Roms] and use that for Magisk patching to attain root. However, since I am not sure how that EXACTLY works, I am worried about the resulting file size. Original file size is 101MB. Patched file size is 36MB. I am afraid to flash due to this. Another however, I use fastboot to boot the patched file directly and it DOES work, just unsure if there would be any problems with it if I FLASH it, instead. I believe I read in a related thread to Magisk and rooting, that it reduces the file size to remove unnecessary space now that it is patched? Can someone confirm how that works and if it is safe to flash? I really don't want to flash it, then come across a problem and have to flash stock boot image and end up running into some other problems all because I wanted to flash the patched file instead of using fastboot to boot every time I reboot. Thanks for any and all help, guys.
mingkee said:
I have successfully rooted mine and having adaway installed
Click to expand...
Click to collapse
How did you get root?
zrex said:
How did you get root?
Click to expand...
Click to collapse
Magisk patched boot flashing method
TOOLBOYNIN39 said:
Since Motorola/Lenovo updated the Edge since this was first posted, I would like to add that coming across the boot image file is a bit more scarce than the original release version for the Edge. However, using Rescue and Smart Assistant, you can downoad the latest ROM version. You may now use the boot image file in the downloaded folder [ProgramData\Lenovo\Downloads\Roms] and use that for Magisk patching to attain root. However, since I am not sure how that EXACTLY works, I am worried about the resulting file size. Original file size is 101MB. Patched file size is 36MB. I am afraid to flash due to this. Another however, I use fastboot to boot the patched file directly and it DOES work, just unsure if there would be any problems with it if I FLASH it, instead. I believe I read in a related thread to Magisk and rooting, that it reduces the file size to remove unnecessary space now that it is patched? Can someone confirm how that works and if it is safe to flash? I really don't want to flash it, then come across a problem and have to flash stock boot image and end up running into some other problems all because I wanted to flash the patched file instead of using fastboot to boot every time I reboot. Thanks for any and all help, guys.
Click to expand...
Click to collapse
Yes, my patched boot image is smaller too, but it works. I'm guessing the patched image is either sparse or truncated.
Mogster2K said:
Yes, my patched boot image is smaller too, but it works. I'm guessing the patched image is either sparse or truncated.
Click to expand...
Click to collapse
That makes all the sense in the world to me. I flashed it and have been running it for a few days now without issue. Have my usual setup with Magisk, Riru-core, Riru EdXposed, and then GravityBox in EdXposed for the free customization. Only thing I couldn't get was Xblast module. Not compatible at all with Android Q. Only thing I need now is make the nav bar black all the time. Can't do it with GB since it doesn't have an option for that. Xblast had one but... oh well. Phone works nice aside from the occasional app that isn't compatible with edge enable/disable.
minidude2012 said:
https://mirrors.lolinet.com/firmware/moto/racer/official/
Firmware for device
Click to expand...
Click to collapse
WOW! You're a life savor, thank you!
I unlocked my bootloader through moto and downloaded the rom through lmsa and patched the boot img with magisk, then tried to flash it using adb but it put my phone into a boot loop.. can anyone help me out? this phone seems like a pain the ass to root* compared to the last one ive done (about 2 years ago)
edit: i think i found out what i did wrong, not renaming the patch file back to how it should be. and i patch the boot.img correct? or patch the recovery.img? getting conflicting guides
Make sure you flash boot.img in fastbootd
I'm curious of people's opinions of rooting this phone?
I just got mine yesterday, and I don't think I've ever not used rooted android all the way back to my first Android Eclair device over a decade ago now.
But here I find myself worried I'll have some of the display issues so I'm hesitant to root my device or request an unlock code while I'm in the 2 week return window because of the wording of the agreement once the code is used. It very explicitly absolves Moto of every possible responsibility for hardware faults under a blanket accusation that by unlocking the phone I must have broken it. And while I have no doubt the wording would crumple in court or whatever, I don't really want to go to court over a cell phone.
I rooted both my "send-ins". I am on my third and just going to accept the light green haze at low light. I rooted my first two and sent them in within a total of a month. First phone was on day 17. 2nd was about 6 or 7 days. That one was a turn around since it displayed the haze during setup. This third one shows it as well but I don't feel like doing the return and setup all over again. You shouldn't have to worry about the agreement since Lenovo/Motorola is not looking into that as this is a known hardware/software issue from factory.
Does this forum include the edge 5G? I have the US model(6/ram, 256GB). Does twrp still have that builder? There used to be something, to that, don't know if that's continued.
reggjoo said:
Does this forum include the edge 5G? I have the US model(6/ram, 256GB). Does twrp still have that builder? There used to be something, to that, don't know if that's continued.
Click to expand...
Click to collapse
Sorry to be a little late, but I am unsure of your question. This forum IS "Motorola Edge 5G". There is a separate forum under the name of "Motorola Edge+ 5G" for the more expensive version. If you are looking for TWRP for this phone, there never was a release. At least none that I had ever seen around here. I was always on the lookout for one and never came across one. The "plus" version of the phone does have a TWRP, however. Maybe that is the phone you have or at least the one you are confusing the TWRP with?
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.
Looks like I'm gonna get a free P2 from my son. It maybe has 1 update left before Google abandons it. When I get it I want to root and put Lineage on it, or maybe a different rom based on opinions provided.
I have some questions:
1- I'm looking for the simplest method to unlock the bootloader and root, as I am not the most knowledgable Android/Linux user. I'm familiar with adb, although best if I can follow a written script. I would appreciate a recommendation on which method posted on XDA. I've seen Deuces and Nathanchance's methods. They seem easy enough to follow along with.
2- I'm a little confused about the Pixel factory images that folks mention in their posts. I see that Google has images catalogued on their site for downloading. How do you choose which one to flash to the phone after bootloader/root process? Does it matter? I'm located in Canada if that makes a difference.
3- I have used TWRP and never used Magisk for loading roms. I also see from one of the bootloader unlock/root methods that TWRP may not be all that reliable. Would TWRP be good enough to flash the factory image with, or should I get familiar with Magisk?
4- Am I correct in thinking that the Google image is flashed first to get the phone up and running, followed by Lineage (and gapps), or an different rom that would be flashed thereafter with TWRP/Magisk?
5- If I screw up during the unlock/root is there a recovery method available?
Thanks for any help provided.
jjcdennis said:
Looks like I'm gonna get a free P2 from my son. It maybe has 1 update left before Google abandons it. When I get it I want to root and put Lineage on it, or maybe a different rom based on opinions provided.
I have some questions:
1- I'm looking for the simplest method to unlock the bootloader and root, as I am not the most knowledgable Android/Linux user. I'm familiar with adb, although best if I can follow a written script. I would appreciate a recommendation on which method posted on XDA. I've seen Deuces and Nathanchance's methods. They seem easy enough to follow along with.
2- I'm a little confused about the Pixel factory images that folks mention in their posts. I see that Google has images catalogued on their site for downloading. How do you choose which one to flash to the phone after bootloader/root process? Does it matter? I'm located in Canada if that makes a difference.
3- I have used TWRP and never used Magisk for loading roms. I also see from one of the bootloader unlock/root methods that TWRP may not be all that reliable. Would TWRP be good enough to flash the factory image with, or should I get familiar with Magisk?
4- Am I correct in thinking that the Google image is flashed first to get the phone up and running, followed by Lineage (and gapps), or an different rom that would be flashed thereafter with TWRP/Magisk?
5- If I screw up during the unlock/root is there a recovery method available?
Thanks for any help provided.
Click to expand...
Click to collapse
Would appreciate some help...
Pixel 2 was updated to android 11, and will likely continue to to get monthly security updates until the release of android 12, so you should have about another year if staying stock.
As far as rooting, the xda guides as you mentioned are pretty straightforward and comprehensive.
Pixel factory images are the stock system images that are provided by google. They are what you would flash if you wanted to run a stock system, and also the means for 'resetting' the phone back to a factory state in the event of a screwup. On the site, you'll notice that google has each of the images organized by phone type (the Pixel 2 is walleye) and within each phone type is operating system version going from oldest at the top to newest at the bottom. Typically you'd want to flash the newest os version unless you have a special use case. There are also cases where a particular version is only for a particular carrier, in which case google will note it under the version number.
As far as flashing lineage, I'm not too sure. I run stock (rooted) on my P2, but lineage is it's own rom so would be flashed directly via twrp. I would image the lineage thread would have install instructions and q/a.
clcdev said:
Pixel 2 was updated to android 11, and will likely continue to to get monthly security updates until the release of android 12, so you should have about another year if staying stock.
As far as rooting, the xda guides as you mentioned are pretty straightforward and comprehensive.
Pixel factory images are the stock system images that are provided by google. They are what you would flash if you wanted to run a stock system, and also the means for 'resetting' the phone back to a factory state in the event of a screwup. On the site, you'll notice that google has each of the images organized by phone type (the Pixel 2 is walleye) and within each phone type is operating system version going from oldest at the top to newest at the bottom. Typically you'd want to flash the newest os version unless you have a special use case. There are also cases where a particular version is only for a particular carrier, in which case google will note it under the version number.
As far as flashing lineage, I'm not too sure. I run stock (rooted) on my P2, but lineage is it's own rom so would be flashed directly via twrp. I would image the lineage thread would have install instructions and q/a.
Click to expand...
Click to collapse
Thanks very much for the help.