Related
So from what i gathered TWRP doesnt work yet on the razer phone 2 and lineage os doesnt have a build for this phone yet i gotta ask what is available for modding razer and what is the step by step to make that happen. i seen some instructions but other than root there isnt much to do.
SynGreis said:
So from what i gathered TWRP doesnt work yet on the razer phone 2 and lineage os doesnt have a build for this phone yet i gotta ask what is available for modding razer and what is the step by step to make that happen. i seen some instructions but other than root there isnt much to do.
Click to expand...
Click to collapse
TWRP works just fine on this device. It's installed when you fastboot flash arter97 kernel and it works perfect. He just updated it to r10. Good luck!!
Edit: as far as ROMs look around in this forum you'll find a couple of different ones in the same section as arter97 :good:
which one do you suggest? i dont see much of a selection.
SynGreis said:
which one do you suggest? i dont see much of a selection.
Click to expand...
Click to collapse
Right now there really aren't any, although there are a few in development, such as AOSP. I think the initial high price, specialized hardware & relative unpopularity has not helped attract any serious development.
I've noticed that ROM development has decreased significantly in the last few years. I remember the days of the Samsung Galaxy Nexus & the HTC Evo 4G where it seemed as if there was a new ROM released every week. I think its because (a) recent Android operating systems are offering greater customization out of the box, & (b) with the new A/B partitioning scheme, it makes ROM development more difficult.
Cancel your order. Get your money back. This phone while it is awesome at gaming and has a great screen. The OS is ****ty to say the least. I have had more issues with it freezing up. Not wanting to download apps from the play store. Not allowing me to install apps that I have already downloaded on my device. Now it's showing up as the Asus Rog II. This phone is the biggest heaviest piece of **** I've ever had. I promise you if everyone knew the issues this phone has you couldn't give it away free.
mattwheat said:
Cancel your order. Get your money back. This phone while it is awesome at gaming and has a great screen. The OS is ****ty to say the least. I have had more issues with it freezing up. Not wanting to download apps from the play store. Not allowing me to install apps that I have already downloaded on my device. Now it's showing up as the Asus Rog II. This phone is the biggest heaviest piece of **** I've ever had. I promise you if everyone knew the issues this phone has you couldn't give it away free.
Click to expand...
Click to collapse
Mine showed as in rog 2 the last time I reloaded the OS. It's because it searches for "phone 2" and randomly guesses. No biggie, just fix it in the settings. No issues here from playstore, if you do it's common on every Android phone and fixable by clearing the data from the app. Maybe you should reflash the stock firmware? I don't see why you would call this phone ****ty. It's basically running AOSP stock except some theming from Razer. I fixed some freezing issues by reseating the Sim and SD card that I have. This thing rocks, just saying.
I've cleared the play stores cache, data, and dalvic in every method imaginable. Even google play services. I've restored backups, flashed stock .imgs, and flashed the stock odex Ron and the deodexed rom. It doesn't start failing to install play store apps till after I initially install most the apps I normally use then a while later when I think of one I forgot I'll go and try to install. That's when it starts messing up. If I watch a video threw some websites built in player on the webpage I'm viewing... about 15 to 20 seconds into the video everything but sound freezes. And will not correct itself. I have to hold the power button till it reboots. Only videos I can watch without issue is from the YouTube app. It's ridiculous. I've unlocked, rooted, and crack flashed tons of roms on all of my pixel and Nexus devices without any issue besides the random freeze. Which can be quickly fixed by toggling the screen on and off. This **** is ridiculous. So over this phone.
matt that might be just you i havent experienced any issues with this phone whatsoever.
"I think its because (a) recent Android operating systems are offering greater customization out of the box, & (b) with the new A/B partitioning scheme, it makes ROM development more difficult."
can you provide more info on this A/B partition? id love to see what customizable stuff i can do with this.
mattwheat said:
I've cleared the play stores cache, data, and dalvic in every method imaginable. Even google play services. I've restored backups, flashed stock .imgs, and flashed the stock odex Ron and the deodexed rom. It doesn't start failing to install play store apps till after I initially install most the apps I normally use then a while later when I think of one I forgot I'll go and try to install. That's when it starts messing up. If I watch a video threw some websites built in player on the webpage I'm viewing... about 15 to 20 seconds into the video everything but sound freezes. And will not correct itself. I have to hold the power button till it reboots. Only videos I can watch without issue is from the YouTube app. It's ridiculous. I've unlocked, rooted, and crack flashed tons of roms on all of my pixel and Nexus devices without any issue besides the random freeze. Which can be quickly fixed by toggling the screen on and off. This **** is ridiculous. So over this phone.
Click to expand...
Click to collapse
The freezing is due to a bug in Google Chrome. All you have to do to fix this issue is roll back the app version to 72 because version 76 doesn't work on our RP2.
Edit: uncheck auto update
Only freeze I had so far was with the infamous switch switch to the tele lens. Not a single other issue with software.
Other question, if you put the display at 120hz, and you scroll something, does it 'feel' like your finger sticks to text/icons?
I mean, is there no delay like you normally would have at 60hz?
On the Oneplus 7 Pro the 90hz is already a big improvement (less delay) but 120 should really be kickass... anyone?
MasterThiefGarrett said:
Other question, if you put the display at 120hz, and you scroll something, does it 'feel' like your finger sticks to text/icons?
I mean, is there no delay like you normally would have at 60hz?
On the Oneplus 7 Pro the 90hz is already a big improvement (less delay) but 120 should really be kickass... anyone?
Click to expand...
Click to collapse
Take this with a grain of salt, as I just got the RP2, but its the most responsive, "sticky" feeling Android phone I've used. 120hz is like night and day to me.
On a related note, Firefox Fenix with webrender enabled feels significantly more responsive than Chromium atm, as it seemingly renders the whole page instead of stuttering as you scroll like Chrome.
JDBarlow said:
TWRP works just fine on this device. It's installed when you fastboot flash arter97 kernel and it works perfect. He just updated it to r10. Good luck!!
Edit: as far as ROMs look around in this forum you'll find a couple of different ones in the same section as arter97 :good:
Click to expand...
Click to collapse
how can you get twrp in? Everytime i try to flash twrp in i get stuck at powered by android logo.
SynGreis said:
how can you get twrp in? Everytime i try to flash twrp in i get stuck at powered by android logo.
Click to expand...
Click to collapse
Which version of Android are you running currently?
MR1 will be arter97 r11
MR2 will be arter97 r12
http://arter97.com/browse/aura/kernel/
duplicate post
JDBarlow said:
Which version of Android are you running currently?
MR1 will be arter97 r11
MR2 will be arter97 r12
http://arter97.com/browse/aura/kernel/
Click to expand...
Click to collapse
i havent flashed either of those arter because im worried that its gonna screw things up again.
Im sitting on the 9.0 MR1 stock image from razer.
https://developer.razer.com/razer-ph...actory-images/
SynGreis said:
i havent flashed either of those arter because im worried that its gonna screw things up again.
Im sitting on the 9.0 MR1 stock image from razer.
https://developer.razer.com/razer-ph...actory-images/
Click to expand...
Click to collapse
So are you on the global version? If so let it update to MR2 and fastboot flash boot arter97 r12 and you'll be just fine.
Which version are you running then to get stuck on boot logo?
Edit: if you want to stay on MR1 then flash arter97 r11
i tried updating to mr2 but says installation failed.
all i do is
faatboot flash boot kernal.img?
I just rooted MR2 to show you. It took me less than 5 minutes to do the whole process of fastboot flashing kernel booting straight into TWRP recovery which is included then installing magisk immediately rebooting into system and updated magisk. Done
JDBarlow said:
I just rooted MR2 to show you. It took me less than 5 minutes to do the whole process of fastboot flashing kernel booting straight into TWRP recovery which is included then installing magisk immediately rebooting into system and updated magisk. Done
Click to expand...
Click to collapse
My only question is, which version zip of magisk did you use in TWRP to flash? 20 or the latest beta? I'm rooted now with a modded boot.img that someone else used the canary/latest beta. Just don't want to screw myself and end up having to flash mr1 again then taking the update.
Hey all, so yesterday i got my phone stuck in a "boot loop". I was trying to install TWRP and magisk to root my phone, after 2 hours of constantly reinstalling TWRP i finally got it to work. Every time my phone would end up just being on a black screen not being able to get to the TWRP menu but i could still access fastboot, i fixed it by "installing" orangefox TWRP, it never actually installed it but i got back into my phone at least, however now thats not working, and im stuck here only being able to get into fast boot. I followed this tutorial - https://forum.xda-developers.com/k20-pro/how-to/guide-redmi-k20-pro-unlock-root-t3974127. When i eventually did get it to install TWRP its because i used the All in one tool. Im currently stuck in the loop again, all i did was follow a youtube video on overclocking my display to 81hz, so i was in TWRP, made a backup of a file, flashed the 81hz.img and now i cant get into twrp or my phone.....How do i fix this?
Im currently flashing a stock rom with MiFlash, taking a few minutes but this is the last thing i can think of to fix this, no im not using the flash and lock method.
Edit: So i decided to use the All in one tool to flash the rom instead, i can now get into TWRP but the phone still by default boots to Fastboot, it wont actually go into the phone? What do i do?
Edit 2: Okay so that fixed it, now to reinstall TWRP with the all in one tool and reroot my phone.........
Edit 3: Okay so new issue, everything is all good TWRP is installed phone is rooted, but im trying to update to the latest MIUI 10 version (on MIUI 9 atm) and i can't install it? It downloads fine but it wont install? Do i have to flash the update file since it wont update through the updater?
JasonBjorn said:
Hey all, so yesterday i got my phone stuck in a "boot loop". I was trying to install TWRP and magisk to root my phone, after 2 hours of constantly reinstalling TWRP i finally got it to work. Every time my phone would end up just being on a black screen not being able to get to the TWRP menu but i could still access fastboot, i fixed it by "installing" orangefox TWRP, it never actually installed it but i got back into my phone at least, however now thats not working, and im stuck here only being able to get into fast boot. I followed this tutorial - https://forum.xda-developers.com/k20-pro/how-to/guide-redmi-k20-pro-unlock-root-t3974127. When i eventually did get it to install TWRP its because i used the All in one tool. Im currently stuck in the loop again, all i did was follow a youtube video on overclocking my display to 81hz, so i was in TWRP, made a backup of a file, flashed the 81hz.img and now i cant get into twrp or my phone.....How do i fix this?
Im currently flashing a stock rom with MiFlash, taking a few minutes but this is the last thing i can think of to fix this, no im not using the flash and lock method.
Edit: So i decided to use the All in one tool to flash the rom instead, i can now get into TWRP but the phone still by default boots to Fastboot, it wont actually go into the phone? What do i do?
Edit 2: Okay so that fixed it, now to reinstall TWRP with the all in one tool and reroot my phone.........
Click to expand...
Click to collapse
A bit of advice.
If you don't know what your doing, don't follow random YouTube videos.
There are some very good videos and some very bad videos. If you don't know what you're doing, you won't know the difference between a good video and a bad one
Until you're comfortable with flashing mods, etc. stick to advice given here. It might not be instant, but you'll get good advice (if it's not good advice then someone else will point that out).
When asking for help give us more info.
What phone do you have?
What ROM was on the phone before first trying to install TWRP?
What version of TWRP have you been trying to install?
Why did you change from using Mi Flash Tool to the all in one tool?
Did you wait for the Mi Flash Tool to finish but it didn't work, or did you get bored of waiting for it to complete and cancelled it?
I appreciate this is a bit late now and not necessary as you've eventually sorted it yourself, but giving the info I've pointed out, at the time, may have actually got you some useful replies before you actually got there yourself.
Robbo.5000 said:
A bit of advice.
If you don't know what your doing, don't follow random YouTube videos.
There are some very good videos and some very bad videos. If you don't know what you're doing, you won't know the difference between a good video and a bad one
Until you're comfortable with flashing mods, etc. stick to advice given here. It might not be instant, but you'll get good advice (if it's not good advice then someone else will point that out).
When asking for help give us more info.
What phone do you have?
What ROM was on the phone before first trying to install TWRP?
What version of TWRP have you been trying to install?
Why did you change from using Mi Flash Tool to the all in one tool?
Did you wait for the Mi Flash Tool to finish but it didn't work, or did you get bored of waiting for it to complete and cancelled it?
I appreciate this is a bit late now and not necessary as you've eventually sorted it yourself, but giving the info I've pointed out, at the time, may have actually got you some useful replies before you actually got there yourself.
Click to expand...
Click to collapse
I have a rough idea on what im doing i've done all this stuff before loads, but xiaomi just seems to be different idk. Considering this is the k20/k20pro section i assumed its obvious thats what i was using.......Everything is sorted like i said but i cant get MIUI to update, it downloads, i hit reboot and it boots me to TWRP instead of installing the update.......i've come to really like the MIUI without the app drawer but now i have an app drawer as im on Android 9, I flashed the lastest rom but before flashing i didnt have an app drawer and was on the latest build so no idea whats going on there......guess i just have to live with this now?
JasonBjorn said:
I have a rough idea on what im doing i've done all this stuff before loads, but xiaomi just seems to be different idk. Considering this is the k20/k20pro section i assumed its obvious thats what i was using.......Everything is sorted like i said but i cant get MIUI to update, it downloads, i hit reboot and it boots me to TWRP instead of installing the update.......i've come to really like the MIUI without the app drawer but now i have an app drawer as im on Android 9, I flashed the lastest rom but before flashing i didnt have an app drawer and was on the latest build so no idea whats going on there......guess i just have to live with this now?
Click to expand...
Click to collapse
What's not obvious is whether you have a Chinese or Indian K20 Pro, or a global or European 9T Pro. Also whether you're trying to install the version of MIUI that is correct for the phone, or if you're flashing from a different region. As you say Xiaomi does things a bit different, so we're seeing things in these forums that what works on one version of the phone doesn't quite work on another.
Robbo.5000 said:
What's not obvious is whether you have a Chinese or Indian K20 Pro, or a global or European 9T Pro. Also whether you're trying to install the version of MIUI that is correct for the phone, or if you're flashing from a different region. As you say Xiaomi does things a bit different, so we're seeing things in these forums that what works on one version of the phone doesn't quite work on another.
Click to expand...
Click to collapse
well heres the weird thing, i bought the EU version of the phone, which i know is supposed to be the 9t pro, but not only did the site call it the K20 pro, but in the settings its model number is also the K20 pro. I got everything working fine.
So I wanted to "ROOT" my Note 9 "N960F" Model just to overclock the "CPU" and do some fun stuff, for about a month I was studing the ways of opening the Bootloader and Rooting but then I finally did it! Hurray!
One Month later I felt like it was making my Note 9 slower, probably placiboo but I wanted to go back to making it normal again
So I logged in to the Recovery Mode on the "TWRP" Software and by mistake deleted the OS from the phone, it is now impossible to enter the phone, I've tried the most tips and tricks form the web and nothing seems to work. Any solutions?
Always make sure to post asking questions, help and support in device specific Q&A Forum ( when exists) and otherwise General Q&A Forum.
Thanks.
All you have to do is flash the current version again. For example, I did the same thing on my Xiaomi Mi Mix 3. All I had to do was flash the correct .zip for the latest version (doesn't have to be latest, could be older).
Hi everyone,
I had updated my Galaxy Note 9 with March 2020 update and I am one among many poor souls who are suffering from display discoloration, horizontal lines during low brightness and over heating.
- I have tried all possible methods as suggested by Samsung team in their US community page, tried factory reset multiple times, nothing worked. Took screenshots of the screen and shared it to other to check if the problem is with display, but the screenshots were just fine, no colour distortion or verticle lines. So i am of the opinion that, its basically software glitch in March update.
So, I have some following specific queries. I tried looking for these queries in the forum but did not find any, so, have collated all my queries below:
- My current Bootloader version is 5. Is there any process by which i can downgrade my Bootloader from 5 to 4? I would like to go back to January update.
- If I root my phone and install custom rom (latest version of Linage OS. You guys can suggest a good OS, if you have tried one), will the display problem be solved?
- After installing custom rom as mentioned above, can I go back and install stock firmware with Bootloader version 4?
As you can see, I am just trying to find a solution to come out of display problem. Any other suggestions or any tried and tested solutions are welcome.
Thanks everyone in advance
#note9displayproblems, #note9marchupdate
Nagharjun said:
Hi everyone,
I had updated my Galaxy Note 9 with March 2020 update and I am one among many poor souls who are suffering from display discoloration, horizontal lines during low brightness and over heating.
- I have tried all possible methods as suggested by Samsung team in their US community page, tried factory reset multiple times, nothing worked. Took screenshots of the screen and shared it to other to check if the problem is with display, but the screenshots were just fine, no colour distortion or verticle lines. So i am of the opinion that, its basically software glitch in March update.
So, I have some following specific queries. I tried looking for these queries in the forum but did not find any, so, have collated all my queries below:
- My current Bootloader version is 5. Is there any process by which i can downgrade my Bootloader from 5 to 4? I would like to go back to January update.
- If I root my phone and install custom rom (latest version of Linage OS. You guys can suggest a good OS, if you have tried one), will the display problem be solved?
- After installing custom rom as mentioned above, can I go back and install stock firmware with Bootloader version 4?
As you can see, I am just trying to find a solution to come out of display problem. Any other suggestions or any tried and tested solutions are welcome.
Thanks everyone in advance
#note9displayproblems, #note9marchupdate
Click to expand...
Click to collapse
From what i've read, 5 to 4 is impossible.
Rosli59564 said:
From what i've read, 5 to 4 is impossible.
Click to expand...
Click to collapse
There should be some or the other way around for this. May be some developer should help us out here.
Nagharjun said:
Hi everyone,
I had updated my Galaxy Note 9 with March 2020 update and I am one among many poor souls who are suffering from display discoloration, horizontal lines during low brightness and over heating.
- I have tried all possible methods as suggested by Samsung team in their US community page, tried factory reset multiple times, nothing worked. Took screenshots of the screen and shared it to other to check if the problem is with display, but the screenshots were just fine, no colour distortion or verticle lines. So i am of the opinion that, its basically software glitch in March update.
So, I have some following specific queries. I tried looking for these queries in the forum but did not find any, so, have collated all my queries below:
- My current Bootloader version is 5. Is there any process by which i can downgrade my Bootloader from 5 to 4? I would like to go back to January update.
- If I root my phone and install custom rom (latest version of Linage OS. You guys can suggest a good OS, if you have tried one), will the display problem be solved?
- After installing custom rom as mentioned above, can I go back and install stock firmware with Bootloader version 4?
As you can see, I am just trying to find a solution to come out of display problem. Any other suggestions or any tried and tested solutions are welcome.
Thanks everyone in advance
#note9displayproblems, #note9marchupdate
Click to expand...
Click to collapse
I am facing same issue ...display distortion from 20% to 80% ..after that display looks fine.
I tried to downgrade to pie ..still no success...it has same issue...
I also believe that its software issue or some connection issue
Sue samsung for trying to force user to change screen. Samsung's screen is so expensive. Apple was fined for throttling the iphones.
I have same issue on my N9600... :'(
What is causing the distortion? Sofware bug? Can shot a picture showing the issue?
Jlozde said:
What is causing the distortion? Sofware bug? Can shot a picture showing the issue?
Click to expand...
Click to collapse
Ita all over the internet. Just Google Samsung galaxy note 9 display discoloration.
I don't know if this will solve your problem but you would be able to flash a Android 9 ROM on a Android 10 bootloader. If you're like me you hate Android 10. What you do is you flash Android 9 bootloader made for twrp flash the Android 9 rom of your choice. Than flash the Android 10 bootloader that you want via Odin, than fastly reflash twrp for Android 10
For me it works but I kind of jerry-rigged it to work. I regret every day updating to Android 10 but since I'm able to still run Android 9 on an Android 10 bootloader, I'm okay with that.
Hope this kind of help you.
Nagharjun said:
Hi everyone,
I had updated my Galaxy Note 9 with March 2020 update and I am one among many poor souls who are suffering from display discoloration, horizontal lines during low brightness and over heating.
- I have tried all possible methods as suggested by Samsung team in their US community page, tried factory reset multiple times, nothing worked. Took screenshots of the screen and shared it to other to check if the problem is with display, but the screenshots were just fine, no colour distortion or verticle lines. So i am of the opinion that, its basically software glitch in March update.
So, I have some following specific queries. I tried looking for these queries in the forum but did not find any, so, have collated all my queries below:
- My current Bootloader version is 5. Is there any process by which i can downgrade my Bootloader from 5 to 4? I would like to go back to January update.
- If I root my phone and install custom rom (latest version of Linage OS. You guys can suggest a good OS, if you have tried one), will the display problem be solved?
- After installing custom rom as mentioned above, can I go back and install stock firmware with Bootloader version 4?
As you can see, I am just trying to find a solution to come out of display problem. Any other suggestions or any tried and tested solutions are welcome.
Thanks everyone in advance
#note9displayproblems, #note9marchupdate
Click to expand...
Click to collapse
Hi Bro, the same problem here. We have created a group to discuss about the issue. Plz join there and will discuss about this.
https://t.me/samsungDisplayProblem
We have a temporary fix for this but also trying for permanent fix which can solve our issue.
---------- Post added at 01:42 PM ---------- Previous post was at 01:39 PM ----------
sagarabhiwant said:
I am facing same issue ...display distortion from 20% to 80% ..after that display looks fine.
I tried to downgrade to pie ..still no success...it has same issue...
I also believe that its software issue or some connection issue
Click to expand...
Click to collapse
Hi Bro, we are also facing the same issue so we have created a Telegram group to discuss about this and gathering all with this problem. Plz join there.
https://t.me/samsungDisplayProblem
We have two to three temporary fixes but we also trying for permanent fix.
this.guy.lol said:
I don't know if this will solve your problem but you would be able to flash a Android 9 ROM on a Android 10 bootloader. If you're like me you hate Android 10. What you do is you flash Android 9 bootloader made for twrp flash the Android 9 rom of your choice. Than flash the Android 10 bootloader that you want via Odin, than fastly reflash twrp for Android 10
For me it works but I kind of jerry-rigged it to work. I regret every day updating to Android 10 but since I'm able to still run Android 9 on an Android 10 bootloader, I'm okay with that.
Hope this kind of help you.
Click to expand...
Click to collapse
hi i have the same problem and i want downgrade to andoid 9 from 10
can you explain how to do it
thanks
majedabbas said:
hi i have the same problem and i want downgrade to andoid 9 from 10
can you explain how to do it
thanks
Click to expand...
Click to collapse
only way is to trip knox by rooting and then flashing an android 9 rom. as you know once it has been tripped you will instantly lose access to samsung pay, secure folders etc. however on the plus side you have the choice of root or non root.
Hi guys,
Me and my mum are experiencing a similar situation.... I'm trying to downgrade my galaxy Note8 boot-loader, everything was working till I press the button to upgrade. Now I cant use any memory card all i see is 'the Sandisk card is not supported' and for my mum's Note 9 when she activates the biometric sensor the phone restarts each 15 - 30 mins. I always bought Samsung but now I'm considering to don't do it anymore...
How do you install android pie over android 10 BL
this.guy.lol said:
I don't know if this will solve your problem but you would be able to flash a Android 9 ROM on a Android 10 bootloader. If you're like me you hate Android 10. What you do is you flash Android 9 bootloader made for twrp flash the Android 9 rom of your choice. Than flash the Android 10 bootloader that you want via Odin, than fastly reflash twrp for Android 10
For me it works but I kind of jerry-rigged it to work. I regret every day updating to Android 10 but since I'm able to still run Android 9 on an Android 10 bootloader, I'm okay with that.
Hope this kind of help you.
Click to expand...
Click to collapse
can you please tell how to install android pie over android 10 BL?
only way is to trip knox root and then flash/ if you dont want to trip knox its not possible
A|ex said:
only way is to trip knox root and then flash/ if you dont want to trip knox its not possible
Click to expand...
Click to collapse
Hi, ok so assuming we don't care about tripping knox, rooting and flash.. still, how would this be done?
I'm on a SM-N9600 atm, with latest Android 10, rooted and TWRP installed. Where do I find a custom Android 9 Rom (compatible with my model) that I can flash via TWRP?
Thanks in advance
Stefo2332 said:
Hi, ok so assuming we don't care about tripping knox, rooting and flash.. still, how would this be done?
I'm on a SM-N9600 atm, with latest Android 10, rooted and TWRP installed. Where do I find a custom Android 9 Rom (compatible with my model) that I can flash via TWRP?
Thanks in advance
Click to expand...
Click to collapse
All you do is just flash the android 9 rom. Downgrading the bootloader makes no difference if you have already unlocked it. The whole point of it is for people who are on later bootloaders and still have knox and want to go to android 9 which is not possible without the trip.
A|ex said:
All you do is just flash the android 9 rom. Downgrading the bootloader makes no difference if you have already unlocked it. The whole point of it is for people who are on later bootloaders and still have knox and want to go to android 9 which is not possible without the trip.
Click to expand...
Click to collapse
Hi @A|ex , thanks for your answer. I still don't know where I can find a custom Android 9 rom, compatible with Note 9 snapdragon (SM-N9600) that I could flash via TWRP... (Assuming it's impossible to flash stock Android 9 via Odin even if my phone is currently already rooted on latest Android 10 (bootloader == 5).
Here on XDA there are some ROMs for the Exynos model but nothing except the 'WETA' rom for Snapdragon model, which is not a full rom anyway from what I understand.
If you could shed some light on this it would be much appreciated: where can I find a custom Android 9 rom, flashable via TWRP, compatible with a rooted SM-N9600 (currently on latest Android 10, with a BL==5, unlocked)?
Thanks again for any help!!
Hello everyone, i just tried updating to the latest ota on android 13 on a rooted 10 pro using the incremental magisk method and now my phone is bricked. wondering if there is a way to recover without losing data. Phone can boot into fastboot, anything else results in Qualcomm Crashdump mode being displayed on screen. ive connected to a computer and it registers when i type fastboot devices, from that point im pretty much stuck on next steps
I did the same mistake thinking it would work like it would on A12 and ended up sending it in to oneplus to reflash.
In my case I have a NE2215 converted to NE2213, what version are you? Full NE2215?
unsafe8989 said:
In my case I have a NE2215 converted to NE2213, what version are you? Full NE2215?
Click to expand...
Click to collapse
yes full ne2215. quite sad knowing we don't even have proper access to the tools to recover our own phones yet. luckily i kept my op8 for a situation like this.
ltw5ki said:
Hello everyone, i just tried updating to the latest ota on android 13 on a rooted 10 pro using the incremental magisk method and now my phone is bricked. wondering if there is a way to recover without losing data. Phone can boot into fastboot, anything else results in Qualcomm Crashdump mode being displayed on screen. ive connected to a computer and it registers when i type fastboot devices, from that point im pretty much stuck on next steps
Click to expand...
Click to collapse
you are sol. i already told you guys that you'll brick your phone if you use magisk method when updating os versions.
ltw5ki said:
Hello everyone, i just tried updating to the latest ota on android 13 on a rooted 10 pro using the incremental magisk method and now my phone is bricked. wondering if there is a way to recover without losing data. Phone can boot into fastboot, anything else results in Qualcomm Crashdump mode being displayed on screen. ive connected to a computer and it registers when i type fastboot devices, from that point im pretty much stuck on next steps
Click to expand...
Click to collapse
If you did unroot completely you can try to boot into EDL mode, in doing so I managed to flip the boot slot and get mine to boot when I was stuck in crashdump mode.
I updated to C.20 yesterday. The process is to unroot completely with image restore, reboot, then let the the update fully install and reboot. You will update fine but be unrooted. Then you boot a patched boot from bootloader and root directly from Magisk.
Do not forget the reboot after uninstalling Magisk before updating.
I already called op to start the repair process. I am willing to try the edl method in a last ditch effort. Is there a detailed explanation on how to get into edl and the process to flip the boot slot?
ltw5ki said:
I already called op to start the repair process. I am willing to try the edl method in a last ditch effort. Is there a detailed explanation on how to get into edl and the process to flip the boot slot?
Click to expand...
Click to collapse
I'm genuinely not sure how to flip the slot on purpose, it happened to me while I was trying the button combination for EDL mode. I believe you have hold all three buttons (Power, Vol Up&Down) until it restarts, it should vibrate but be a black screen and you can plug the USB in from there to see a port 9008 on the PC. This is very generalized but there are more details all around the forum here.
I will say I believe when it flipped, it booted and I saw the oneplus screen for a split second, the screen sort of glitched, and it immediately rebooted from black screen back to bootloader. I think the switch occurred then.
Also is that from a powered off state or is it possible to do with the phone being on?
Hmmm... I can get into bootloader okay and even launch recovery, but I can't seem to switch the partitions. I contacted support, they can replace the phone, but can't or won't tell me how to switch partitions or load it manually.
Quantumrabbit said:
Hmmm... I can get into bootloader okay and even launch recovery, but I can't seem to switch the partitions. I contacted support, they can replace the phone, but can't or won't tell me how to switch partitions or load it manually.
Click to expand...
Click to collapse
If you can get into bootloader, can you try to fastboot boot a boot image? Does that also lead to a qualcomm crashdump?
Prant said:
If you can get into bootloader, can you try to fastboot boot a boot image? Does that also lead to a qualcomm crashdump?
Click to expand...
Click to collapse
The problem is I don't know if I have any fastbootable images... I have the C19 full zip... would that work to try and fastboot it? Do I fastboot just the C19 bootloader?
I'm not used to being in the situation I'm in right now
Quantumrabbit said:
The problem is I don't know if I have any fastbootable images... I have the C19 full zip... would that work to try and fastboot it? Do I fastboot just the C19 bootloader?
I'm not used to being in the situation I'm in right now
Click to expand...
Click to collapse
Just take a step back and don't do anything rash. Absolutely do not FLASH anything in fastboot, but there are numerous guides around here. You basically want to extract the boot.img from that full upgrade zip's payload.bin file, easiest way being with FastbootEnhance, then use command 'fastboot boot "boot.img"' while you're on bootloader. I'm not sure if this will boot your phone, but it definitely can not damage it as long as you're just booting, so it's worth a shot.
Prant said:
Just take a step back and don't do anything rash. Absolutely do not FLASH anything in fastboot, but there are numerous guides around here. You basically want to extract the boot.img from that full upgrade zip's payload.bin file, easiest way being with FastbootEnhance, then use command 'fastboot boot "boot.img"' while you're on bootloader. I'm not sure if this will boot your phone, but it definitely can not damage it as long as you're just booting, so it's worth a shot.
Click to expand...
Click to collapse
Hey man I'd like to poke at your brain if you don't mind, so I did the same thing as quantumrabbit, didn't reboot after unrooting and got the same issue. My problem was my dumba** tried to follow one of the fastboot guides to try and recover my phone and boy let me tell you I bricked my phone harder then I've ever bricked a phone lol. Anyway I got into contact with OP shipped them the phone, they claim to have repaired it and it should get back to me tomorrow, overall took 2 weeks. I want to avoid doing in this future as root is a must for me, before the 10 Pro I had a 6T. Whenever I was on that device from OOS 9,10 & 11 and custom roms after the update support was over, I was always able to unroot without rebooting, flash the full OTA zip and then install magisk to the next inactive slot. It would work and I would retain root. When I got my 10 Pro, for the first 4 updates that came out for the NE2215 where only incremental. So my method was unroot with no reboot, install the incremental ota, then install root to inactive slot and it worked some how even being incremental updates and without the reboot. Well then, I then converted my NE2215 to a NE2213 using the rollback package, and then update normally until C19 released where I fully unrooted and even factory reset for the OS jump from A12 to A13. C20 came out, and this is where I tried the same stupid method, unroot with no reboot, install full OTA zip, then flash magisk to the inactive slot, this then immediately gave the Qualcomm error people are getting. My question is, is that reboot mandatory and should it always be done, since I never had a issue before hand it slipped my mind. I hope you understand what I'm trying to ask, basically I want to avoid this issue in the future especially with no MSM and OP taking their sweet time to fix my phone, should I always completely unroot and reboot for absolutely any OTA and just manually root again by booting the boot image I'm pretty sure that's a no brainer "yes" to my question but more or less I wanna know what changed from Android 12 where I was able to use the un-recommended method with 4 consecutively updates on NE2215 and about 2 of them on NE2213 after converting. I'd like your insight on why it should be done the correct way and what issues arise etc as you seem knowledgeable. Also the possibilities on how to recover, I saw your solution where you recommend booting a boot image to see if that would work, didn't even cross my mind but I think that would've been the correct approach instead of jumping straight into fastboot flashing like my dumb self did. Thank you!
unsafe8989 said:
Hey man I'd like to poke at your brain if you don't mind, so I did the same thing as quantumrabbit, didn't reboot after unrooting and got the same issue. My problem was my dumba** tried to follow one of the fastboot guides to try and recover my phone and boy let me tell you I bricked my phone harder then I've ever bricked a phone lol. Anyway I got into contact with OP shipped them the phone, they claim to have repaired it and it should get back to me tomorrow, overall took 2 weeks. I want to avoid doing in this future as root is a must for me, before the 10 Pro I had a 6T. Whenever I was on that device from OOS 9,10 & 11 and custom roms after the update support was over, I was always able to unroot without rebooting, flash the full OTA zip and then install magisk to the next inactive slot. It would work and I would retain root. When I got my 10 Pro, for the first 4 updates that came out for the NE2215 where only incremental. So my method was unroot with no reboot, install the incremental ota, then install root to inactive slot and it worked some how even being incremental updates and without the reboot. Well then, I then converted my NE2215 to a NE2213 using the rollback package, and then update normally until C19 released where I fully unrooted and even factory reset for the OS jump from A12 to A13. C20 came out, and this is where I tried the same stupid method, unroot with no reboot, install full OTA zip, then flash magisk to the inactive slot, this then immediately gave the Qualcomm error people are getting. My question is, is that reboot mandatory and should it always be done, since I never had a issue before hand it slipped my mind. I hope you understand what I'm trying to ask, basically I want to avoid this issue in the future especially with no MSM and OP taking their sweet time to fix my phone, should I always completely unroot and reboot for absolutely any OTA and just manually root again by booting the boot image I'm pretty sure that's a no brainer "yes" to my question but more or less I wanna know what changed from Android 12 where I was able to use the un-recommended method with 4 consecutively updates on NE2215 and about 2 of them on NE2213 after converting. I'd like your insight on why it should be done the correct way and what issues arise etc as you seem knowledgeable. Also the possibilities on how to recover, I saw your solution where you recommend booting a boot image to see if that would work, didn't even cross my mind but I think that would've been the correct approach instead of jumping straight into fastboot flashing like my dumb self did. Thank you!
Click to expand...
Click to collapse
your jumping around probably screwed up some partition size. I did not restart for the c20 ota and have no issues.
unsafe8989 said:
Hey man I'd like to poke at your brain if you don't mind, so I did the same thing as quantumrabbit, didn't reboot after unrooting and got the same issue. My problem was my dumba** tried to follow one of the fastboot guides to try and recover my phone and boy let me tell you I bricked my phone harder then I've ever bricked a phone lol. Anyway I got into contact with OP shipped them the phone, they claim to have repaired it and it should get back to me tomorrow, overall took 2 weeks. I want to avoid doing in this future as root is a must for me, before the 10 Pro I had a 6T. Whenever I was on that device from OOS 9,10 & 11 and custom roms after the update support was over, I was always able to unroot without rebooting, flash the full OTA zip and then install magisk to the next inactive slot. It would work and I would retain root. When I got my 10 Pro, for the first 4 updates that came out for the NE2215 where only incremental. So my method was unroot with no reboot, install the incremental ota, then install root to inactive slot and it worked some how even being incremental updates and without the reboot. Well then, I then converted my NE2215 to a NE2213 using the rollback package, and then update normally until C19 released where I fully unrooted and even factory reset for the OS jump from A12 to A13. C20 came out, and this is where I tried the same stupid method, unroot with no reboot, install full OTA zip, then flash magisk to the inactive slot, this then immediately gave the Qualcomm error people are getting. My question is, is that reboot mandatory and should it always be done, since I never had a issue before hand it slipped my mind. I hope you understand what I'm trying to ask, basically I want to avoid this issue in the future especially with no MSM and OP taking their sweet time to fix my phone, should I always completely unroot and reboot for absolutely any OTA and just manually root again by booting the boot image I'm pretty sure that's a no brainer "yes" to my question but more or less I wanna know what changed from Android 12 where I was able to use the un-recommended method with 4 consecutively updates on NE2215 and about 2 of them on NE2213 after converting. I'd like your insight on why it should be done the correct way and what issues arise etc as you seem knowledgeable. Also the possibilities on how to recover, I saw your solution where you recommend booting a boot image to see if that would work, didn't even cross my mind but I think that would've been the correct approach instead of jumping straight into fastboot flashing like my dumb self did. Thank you!
Click to expand...
Click to collapse
Yeah, flashing on this device is a big no go until we get proper recovery tools. 9 times out of 10 you'll make things worse.
While you have people like @g96818 that don't use the full reboot, PC method; when I tried to use that method for C.19, I was the one stuck in qualcomm crash dump last month. When I posted I was informed that with this device, especially since Android 13, doing the incremental systemflash then trying to install magisk to inactive *CAN* leave some weird errors in the system update process.
Either way, for me personally, after that big a scare. I will always update using the full uninstall Magisk with restore images, reboot, flash system update, let it do its thing, then root again using a magisk patched boot image, which is super simple to do. You can use cross region boots, as in 2213 on 2215, done that the past two times. Just remember to never flash, only boot.
Appreciate your guys input, I'll make sure to be extra cautious! Phone comes in today, fingers crossed I successfully update to C20 and root! Lol.
Prant said:
Yeah, flashing on this device is a big no go until we get proper recovery tools. 9 times out of 10 you'll make things worse.
While you have people like @g96818 that don't use the full reboot, PC method; when I tried to use that method for C.19, I was the one stuck in qualcomm crash dump last month. When I posted I was informed that with this device, especially since Android 13, doing the incremental systemflash then trying to install magisk to inactive *CAN* leave some weird errors in the system update process.
Either way, for me personally, after that big a scare. I will always update using the full uninstall Magisk with restore images, reboot, flash system update, let it do its thing, then root again using a magisk patched boot image, which is super simple to do. You can use cross region boots, as in 2213 on 2215, done that the past two times. Just remember to never flash, only boot.
Click to expand...
Click to collapse
One last question, do you remove all your modules first reboot then unroot and reboot?
Prant said:
Yeah, flashing on this device is a big no go until we get proper recovery tools. 9 times out of 10 you'll make things worse.
While you have people like @g96818 that don't use the full reboot, PC method; when I tried to use that method for C.19, I was the one stuck in qualcomm crash dump last month. When I posted I was informed that with this device, especially since Android 13, doing the incremental systemflash then trying to install magisk to inactive *CAN* leave some weird errors in the system update process.
Either way, for me personally, after that big a scare. I will always update using the full uninstall Magisk with restore images, reboot, flash system update, let it do its thing, then root again using a magisk patched boot image, which is super simple to do. You can use cross region boots, as in 2213 on 2215, done that the past two times. Just remember to never flash, only boot.
Click to expand...
Click to collapse
Technically that's on you. I gave a warning that you will brick if you don't fully unroot for c19.
Quantumrabbit said:
The problem is I don't know if I have any fastbootable images... I have the C19 full zip... would that work to try and fastboot it? Do I fastboot just the C19 bootloader?
I'm not used to being in the situation I'm in right now
Click to expand...
Click to collapse
I posted the c20 boots and how to flip the boot so go try it out.