Really frustrated newb - OnePlus 3T Questions & Answers

Just got my 3t and went to do the full upgrade (non-rooted) to 4.0.1 which hung the device.
I can get into recovery mode but all that does is leave the android logo on.
I can get fastboot to recognize the device, but whenever I try do anything other than device I get FAILED since it isn't rooted
And I tried the bricked directions but all that gets is a 258 error as soon as it tries to install cache.img
Any thoughts other than banging my head against the wall that I can try?

Can you tell us what you did step by step?
What recovery do you have?
Is your bootloader locked or unlocked?
USB Debugging and OEM Unlock options enabled in Developer mode?
Did you try the upgrade through sideload or recovery?
Was it a full install or OTA?
Where did you download the files from?
There is an excellent thread about how to do the install step by step.
Follow this and you should be fine.
https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Hope that helps!

Related

Help!!! I need to unlock bootloader, root, install custom recovery on sm-n9200

I've attempted to UNLOCK this thing via ADB using "FASTBOOT OEM UNLOCK" and it just hangs there, for HOURS even.
ODIN won't recognize the phone for some reason.
I can't get it to go into download mode.
Recovery mode is in chinese and I can't understand a damn word it's saying.
PLEASE...anyone with any insight as to how to do this, let me know. I follow instructions very well and im capable just list and fire away! PLEASE!

[Solved]Bricked. Can't recover stock ROM after installing TWRP 3.1.0-3. Nothing works

I have successfully unlocked the bootloader and managed to install TWRP 3.1.0-3 but that's about it. I cannot install any other TWRP version but the one I mentioned. I tried installing Magic Rainbow custom ROM but it doesn't work properly (apps are super slow, entering developer settings makes the settings app crash, can't set a password etc.). So with that I can at least access the phone interface with limited options. Developer settings crashes when I choose it; if I can get through then I can't enable USB debugging, it keeps turning itself off right as I enable it. I can't use update function so I have to use 3 button installation, which randomly fails to work very often. Due to this I haven't been able to install any updates.
I kinda gave up on rooting already, I just want to get my old firmware back at this point but I can't even do that. SRKTools stock marshmallow recovery doesn't work either. It's as if TWRP 3.1.0 has taken over everything. On the rare occasions that I managed to get EMUI update via 3 button installation it would say that the update doesn't match the current version (or something like that). I tried using recover for b378 and managed to run the 3 button update but it always gets stuck at 5%. It gives up after a while, tries booting twice and then goes into eRecovery screen. My bootloader PHONE unlocked text is in red if it matters.
I've been actively trying to fix this for the last 11 hours (yes I'm not exaggerating at all). Please, PLEASE someone help me out with this!
I've also tried using the unbrick tool of the latest SRK Tool 2.0 for b378. It goes flawless, phone restarts and does a factory wipe but then doesn't boot after the Huawei screen. It tries booting twice and then it goes into eRecovery screen. Have I ruined some hardware here?
It seems like 3 button upgrade is my salvation and it doesn't work. Many times I hold it down, I get a slightly different screen but it again hangs at booting text. I managed to flash all recovery, boot and system image files and got the installing update screen in my b378 update, but it hangs at 5%. I couldn't even manage to get the installing update screen for common b136. Also when I try to flash system.img I get an error with flashing system which is FAILED (remote:sparse flash write failure).
First at all: The Magic Rainbow custom ROM is based on B383 so it wont work on B378 firmware thats your fault here.
Just flash the rollback package (find it in my signature) and after this flash B383 or if it not work start with B136. U have to do all with the dload method.
Fast solution?
https://forum.xda-developers.com/p9/development/p9-moonlight-rom-v1-0-b378-stock-t3567223
flash the B378 version. probably your problem is solved by this.
I'm very well aware that Magic Rainbow doesn't work with b378. That's probably the reason I have those issues with it. But it's the only way I can access the phone's interface in case I need to use it for a fix.
I tried flashing b378 already multiple times, without rollback and it did not work. Is it safe to use the rollback though? My oem is c432, would it create any issues to use that? Should I flash c900 oem first or can I go with the rollback right away? I literally cannot install any stock rom without having frozen/looping bootscreen atm so I can't complete any step that requires me to do that.
I've also tried flashing b136 plenty of times already. I can't even flash the system.img. I can't flash the system of any of the b100 series.
Lauran_N said:
I'm very well aware that Magic Rainbow doesn't work with b378. That's probably the reason I have those issues with it. But it's the only way I can access the phone's interface in case I need to use it for a fix.
I tried flashing b378 already multiple times, without rollback and it did not work. Is it safe to use the rollback though? My oem is c432, would it create any issues to use that? Should I flash c900 oem first or can I go with the rollback right away? I literally cannot install any stock rom without having frozen/looping bootscreen atm so I can't complete any step that requires me to do that.
I've also tried flashing b136 plenty of times already. I can't even flash the system.img. I can't flash the system of any of the b100 series.
Click to expand...
Click to collapse
u tried the rom i mentioned?
it is safe to use the rollback package. any firmware after will retrive your oem to c432. so you dont need to flash the oem info package.
1. flash rollback package via dload (watch out to have only the UPDATE.APP file in dload folder)
2. flash B383 via dload (2 files need to be flashed!)
3. flash special SuperSU_for_EMUI5.zip
4. have fun
again if u can boot magic rom then you can flash and use Moonlight rom v1.0
xtcislove said:
u tried the rom i mentioned?
it is safe to use the rollback package. any firmware after will retrive your oem to c432. so you dont need to flash the oem info package.
1. flash rollback package via dload (watch out to have only the UPDATE.APP file in dload folder)
2. flash B383 via dload (2 files need to be flashed!)
3. flash special SuperSU_for_EMUI5.zip
4. have fun
again if u can boot magic rom then you can flash and use Moonlight rom v1.0
Click to expand...
Click to collapse
I cannot flash rollback using 3 buttons method. I see the "your device is booting now" text and then it goes to TWRP menu. Nothing happens. This is what I mean with 3 button method not working. Every single update fails probably because of this. Is there anything else I can do to flash it?
I've also tried flashing b378 and then doing the rollback. Still doesn't work: It hangs at 5% as it did with the b378 update.
Also, is there a special way of flashing those 2 files of b383? Is it just one after another? I doubt I can flash them at the same time since they have the same name.
YES IT WORKED! Thank you the rollback actually made the difference. I had to go for b136 and then upgrade manually through there with the stock OS though. And I believe rollback changed the status to LOCKED instead of RELOCKED. And I was a complete moron for I couldn't do 3 button update because my cable was still plugged in. I had a moment of epiphany when I noticed what the symbol actually represents. It was like discovering who Keyser Soze was lol. Let this idiocy stay here for there might be others like me; this way they might fix it without embarrassing themselves like I did.
Glad it worked for you.
Next time just read the threads in this forum.
There are several toturials how to flash the p9 the right way.
Lauran_N said:
YES IT WORKED! Thank you the rollback actually made the difference. I had to go for b136 and then upgrade manually through there with the stock OS though. And I believe rollback changed the status to LOCKED instead of RELOCKED. And I was a complete moron for I couldn't do 3 button update because my cable was still plugged in. I had a moment of epiphany when I noticed what the symbol actually represents. It was like discovering who Keyser Soze was lol. Let this idiocy stay here for there might be others like me; this way they might fix it without embarrassing themselves like I did.
Click to expand...
Click to collapse
Can you explain in detail how your fact? That would be nice
Genysix said:
Can you explain in detail how your fact? That would be nice
Click to expand...
Click to collapse
1. Flash Rollback Package
2. Flash Firmware Package/s
3.Unlock booloader
4.Flash twrp
5.Flash SuperSU
6.Ready
Just read the threads in this forum guys and you errors will magically dissappear or not even happen
xtcislove said:
1. Flash Rollback Package
2. Flash Firmware Package/s
3.Unlock booloader
4.Flash twrp
5.Flash SuperSU
6.Ready
Just read the threads in this forum guys and you errors will magically dissappear or not even happen
Click to expand...
Click to collapse
Every time I try to flash, with 3 buttons method, it puts me "software install failed"
I tried to flash official rom with twrp but he can't finish the process.
I tried to flash custom rom. When I want to boot, he bootloop.
Hi,
I am at a complete loss and going round in circles. My phone has bootlocker unlocked message at moment. In adb fastboot devices finds the phone, but the SRK tool fails to find it sticking on 'waiting for phone'. I tried to flasg the Huawei rollback but that fails (presumably due to being unlocked). I cannot relock via fastboot as that gives 'remote: command not allowed' error.
Update
- I have just checked fastboot - it says Phone Unlocked & FRP Unlock.
- Next I used Huawei Update Extractor to get boot, recovery, cust & system img from the "HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0_EMUI 4.1_C432B166_United Kingdom_Channel-Others" Package.
It seems I still cannot boot and device still says unlocked etc..
Update 2 :-
Copied the dload/update.app file from the HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0 zip. Managed to get it to start installing, only to get Software Install Failed msg. However reboot let me start the phone. So currently have Build No: EVA-L09C432B166 on.
At this point I just want my phone either back to initial factory state or able to flash roms, whichever is easier to get to. Any help greatly appreciated. I've been getting nowhere following guides I have found, so would really appreciate some help here.
Thank You
Genysix said:
Every time I try to flash, with 3 buttons method, it puts me "software install failed"
I tried to flash official rom with twrp but he can't finish the process.
I tried to flash custom rom. When I want to boot, he bootloop.
Click to expand...
Click to collapse
Ok first of all, using TWRP back up everything you have there (backing up SD card isn't really needed unless you plan to wipe it too). Then, using TWRP again just wipe everything but OEM and SD card (external storage). Then, create a folder called "dload" in the main SD card directory and put ONLY the update.app in it (use the stock b136 as suggested). Now you need to flash a stock recovery using bootloader again. Just use the Huawei Update Extractor and get both recovery.img and boot.img from the rom that you're using to flash (in this case b136). Put them in the same folder as adb. Run adb cmd, write commands "fastboot flash recovery recovery.img" and then "fastboot flash boot boot.img" and finally "fastboot reboot". Quickly unplug your usb cable and use the 3 button force update (Vol Up+Vol Down+Power button all held together and don't let go until you see the update start). It should work without a problem if you had managed to wipe everything using TWRP. If it still doesn't work you could try deleting OEM info as well and flashing a new one (c432) which you can find on the forums. Back up is important in case it still doesn't work, you might need them to undo things.
If it boots, it means you've learned how to do it and you can probably unbrick it as much as you want haha. You can update to Nougat (7.0) and EMUI 5 using Huawei Updater 2.0 along with HiSuite, there is a guide here on the forums to do so by updating to b182 then to b360/b361>b378>b383 which I was unable to find for now. After that you can install a custom rom without an issue. I figured I wouldn't mess with it anymore but frankly it's likely that you are just soft bricking by skipping something very simple and failing because of that unless you went ahead and did things that you are explicitly told not to do so. If you end up having it unlocked/relocked might as well try and get a custom rom really.
If the update gets stuck at 5% or you have the icon of a usb cable end with a lightning on it your mistake is that you didn't unplug it. If the update keeps failing without these it's likely that you're using the wrong firmware and you could try using another one (FULL+PV+MV ones if you're going for a higher one). Or you could try to follow the rollback and then the update as I did. if you do the rollback then the update, your phone might get a LOCKED status again (yes not relocked).
If you are missing something or you think you have a stupid question and too shy to ask it here just PM me.
Phil_UK said:
Hi,
I am at a complete loss and going round in circles. My phone has bootlocker unlocked message at moment. In adb fastboot devices finds the phone, but the SRK tool fails to find it sticking on 'waiting for phone'. I tried to flasg the Huawei rollback but that fails (presumably due to being unlocked). I cannot relock via fastboot as that gives 'remote: command not allowed' error.
Update
- I have just checked fastboot - it says Phone Unlocked & FRP Unlock.
- Next I used Huawei Update Extractor to get boot, recovery, cust & system img from the "HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0_EMUI 4.1_C432B166_United Kingdom_Channel-Others" Package.
It seems I still cannot boot and device still says unlocked etc..
Update 2 :-
Copied the dload/update.app file from the HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0 zip. Managed to get it to start installing, only to get Software Install Failed msg. However reboot let me start the phone. So currently have Build No: EVA-L09C432B166 on.
At this point I just want my phone either back to initial factory state or able to flash roms, whichever is easier to get to. Any help greatly appreciated. I've been getting nowhere following guides I have found, so would really appreciate some help here.
Thank You
Click to expand...
Click to collapse
So you're saying that you're able to boot your phone on stock b166? Then update it to b182 first. I had to keep pressing the check update for a while before it popped up. I was busy at the time so I didn't mind the wait time but I bet you can do it faster forcefully, got to be a guide around here somewhere. Here is the guide to update it all the way to b383 from b182.
Lauran_N said:
So you're saying that you're able to boot your phone on stock b166? Then update it to b182 first. I had to keep pressing the check update for a while before it popped up. I was busy at the time so I didn't mind the wait time but I bet you can do it faster forcefully, got to be a guide around here somewhere. Here is the guide to update it all the way to b383 from b182.
Click to expand...
Click to collapse
I'm on B166 currently. Phone tells me it has update for B182, on reboot I get the device unlocked message and it sticks on 'Your device is booting now'.
Also tried Huawei updater....that sticks at 'Listened on Port 41279'
Thanks
Phil_UK said:
I'm on B166 currently. Phone tells me it has update for B182, on reboot I get the device unlocked message and it sticks on 'Your device is booting now'.
Also tried Huawei updater....that sticks at 'Listened on Port 41279'
Thanks
Click to expand...
Click to collapse
Getting the device unlocked message shouldn't indicate anything, only that you didn't lock it again. It might be that you didn't install your current rom correctly. You could try flashing TWRP, backing up everything and then wiping all of it f. It means you'll be romless for a while but worst case you can recover what you backed up with TWRP and then flash it with a stock rom again. There are guides to flashing everywhere and I've made my own guide here. I can't really give you advice on your situation since I haven't ever been there. I just dabble with these things, so I can't really find a solution for everything.
You are connected to HiSuite while running Huawei Updater right? It needs to be able to see your phone (usb debugging on or HDB mode) and set to usage via proxy.
Lauran_N said:
Getting the device unlocked message shouldn't indicate anything, only that you didn't lock it again. It might be that you didn't install your current rom correctly. You could try flashing TWRP, backing up everything and then wiping all of it f. It means you'll be romless for a while but worst case you can recover what you backed up with TWRP and then flash it with a stock rom again. There are guides to flashing everywhere and I've made my own guide here. I can't really give you advice on your situation since I haven't ever been there. I just dabble with these things, so I can't really find a solution for everything.
You are connected to HiSuite while running Huawei Updater right? It needs to be able to see your phone (usb debugging on or HDB mode) and set to usage via proxy.
Click to expand...
Click to collapse
Thanks for your help. Where do you set the usage to via proxy? Perhaps thats my issue.
Phil_UK said:
Thanks for your help. Where do you set the usage to via proxy? Perhaps thats my issue.
Click to expand...
Click to collapse
Run HiSuite. Make sure your phone is connected to it. Top right you'll see 4 buttons: 3 horizontal stripes, minimise, full screen and X. Press 3 stripes one and choose settings. In the first tab called General under the 4th section you'll see Proxy. Enable it and enter 127.0.0.1 for address and the given listening port as the port. Leave the username and password blank. Press apply. Then you probably have to choose the system upgrade from the main screen of HiSuite. I don't recall exactly but this is about how it goes.
Lauran_N said:
Run HiSuite. Make sure your phone is connected to it. Top right you'll see 4 buttons: 3 horizontal stripes, minimise, full screen and X. Press 3 stripes one and choose settings. In the first tab called General under the 4th section you'll see Proxy. Enable it and enter 127.0.0.1 for address and the given listening port as the port. Leave the username and password blank. Press apply. Then you probably have to choose the system upgrade from the main screen of HiSuite. I don't recall exactly but this is about how it goes.
Click to expand...
Click to collapse
Many Thanks
I managed to flash B360_update.zip via recovery instead. I also have a B360_update_data_full_hw_eu.zip but not sure what that is for.

I really ****ed up

So, I ****ed up.
Earlier this night i hard bricked my device while trying to uninstall Magisk. Used a guide that worked and was back on stock OOS 3.5.0.
In the old Oxygen OS I installed TWRP. But the thing with the recovery was that you needed to boot recovery from the command line with the command
Code:
fastboot boot twrp.img
. If I booted into recovery in any other way the screen is just black and never boots.
When I tried to install OOS 4.0.1 I got error code 7. Googled it and it just told me to relock the bootloader and install the OTA instead.
I relocked it, and when it was done I got the prompt to fill in the password to start Android. But the thing was I did not use any security options, no fingerprint or pin code. So zero luck there. And now I can't boot into recovery because I didn't flash the stock recovery because I'm a retard, so when I'm trying to boot recovery it's just black. So I have no chance to come back. Please help...
So this is not a hard brick. It's a brick for sure, but a Hard Brick is where you cannot boot up your phone whatsoever.
Now, assuming from the vague details you've provided, you can boot into the normal boot logo screen? You should be able to get into fastboot, but if you can't since you've not mentioned it, there are still ways of getting your device back into OOS.
If you can get your device into Fastboot;
1. Boot into FB
2. Unlock your bootloader
3. Reflash TWRP
4. Boot into TWRP
5. Flash ROM of your choice.
If you can't get into Fastboot;
Use this thread ( https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306)
OR use this one if you want the updated tools and follow the instructions on the above Thread (https://forum.xda-developers.com/oneplus-3t/help/ultra-brick-oreo-firmware-ob16-nougat-t3689356)
What you need to know;
Never lock your bootloader when you have a Third Party recovery or ROM installed.
Never interrupt the unbrick process.
Please do a search here on XDA before you post a new thread. There have been similar issues solved multiple times on this Forum.
Good luck!
thes3usa said:
So this is not a hard brick. It's a brick for sure, but a Hard Brick is where you cannot boot up your phone whatsoever.
Now, assuming from the vague details you've provided, you can boot into the normal boot logo screen? You should be able to get into fastboot, but if you can't since you've not mentioned it, there are still ways of getting your device back into OOS.
If you can get your device into Fastboot;
1. Boot into FB
2. Unlock your bootloader
3. Reflash TWRP
4. Boot into TWRP
5. Flash ROM of your choice.
If you can't get into Fastboot;
Use this thread ( https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306)
OR use this one if you want the updated tools and follow the instructions on the above Thread (https://forum.xda-developers.com/oneplus-3t/help/ultra-brick-oreo-firmware-ob16-nougat-t3689356)
What you need to know;
Never lock your bootloader when you have a Third Party recovery or ROM installed.
Never interrupt the unbrick process.
Please do a search here on XDA before you post a new thread. There have been similar issues solved multiple times on this Forum.
Good luck!
Click to expand...
Click to collapse
Thank you for your reply, I tried to do the method with the MSMDownload thing yesterday, but the computer did not recognize the device. It was late in the night (5am) so I went to bed. This morning I took my other computer and plugged my phone in, it recognized it and I was able to fully recover the phone!
avveawesome said:
When I tried to install OOS 4.0.1 I got error code 7. Googled it and it just told me to relock the bootloader and install the OTA instead.
Click to expand...
Click to collapse
This isn't good idea. As already noted, never relock the bootloader on this device with TWRP, root, etc. It should only be relocked after returning to full stock condition.
Also, never install an incremental OTA when you have TWRP (root, etc.), only the full update zips should be used in that case.
Try to stick to these forums for advice. Maybe the guidance your found above is not specific to this device?

No recovery cant format

Hey!
I unlocked bootloader, installed TWRP, and rooted the phone.
Now I cannot get into recovery, the screen just goes black and white led lights up. I tried to factory reset in phone settings, but it wont do nothing. I try to switch off the phone, press vol+ & plug the usb cable to do the unbrick thing, but its not responding to that either.
Fastboot oem device-info says tampered false & bootloader unlock true.
Ned help!
Assuming you have Windows on your PC, if you try to enter download mode (in order to use unbrick method), can you hear a device plugged in sound and/or see the device in Device Manager? Maybe you don't have the drivers.
If fastboot is working too (because you could type "oem device-info" and get an output), you may want to try flashing a custom kernel/ROM or TWRP once again to get it working.
Are you sure you have flashed correct files and haven't mistaken OP3T with OP3?
AFAIK everythings OP3T specific.
Now I ran msmdltool, sideloaded most up-to-date stock rom, managed to flash TWRP and magisk, everythings going smooth this far. I made backups and tried to flash RR rom, but its saying "...this device ( . ) ERROR 7" whats the deal?
*FIXED*
I read that TWRP merged OP3 & OP3T, found a proper dl link for the newest ver TWRP and manage to flash the rom.
So If someone is having same kind of problems like me and trying to figure what can go wrong when you following step-by-step guides, pay attention to details. In this case first after unbrick I forgot to sideload newest ver stock rom. This error 7 thing was a minor and easy to fix, but still can take couple of hours to figure out(find a proper dl link)

Root rog 2

Hello everyone, i got rooted Rog Phone 2 and after rooting my rog phone 2 i dont have wifi signal anymore. i unroot my phone by flashing stock + tried flashing stock boot.img but wifi is still not working, what happened and how can i fix it?
@Barcovn Would you like to share how to deal with this?
https://m.facebook.com/groups/2059277157699287?view=permalink&id=2106812296279106
From my friend. He share the Tut for fixing it. Basically we upgraded new fw after open the phone so the boot.img extracted from the website will be difference with newest ota upgrade. Lost wifi. You have to manual flash the phone again
Barcovn said:
https://m.facebook.com/groups/2059277157699287?view=permalink&id=2106812296279106
From my friend. He share the Tut for fixing it. Basically we upgraded new fw after open the phone so the boot.img extracted from the website will be difference with newest ota upgrade. Lost wifi. You have to manual flash the phone again
Click to expand...
Click to collapse
Right! As I haven't got the phone yet, didn't find out that new OTA have different boot.img. So as for now, rooting means just firmware on website is usable.
In the future if there is an update you will need to unroot, flash the original boot. Flash the rom update and then extract the new boot, patch it with magisk and flash the new patched boot to enjoy root again.
Personally I would rather stay on stock enjoy the timely OTA updates and keep my warranty.
dungnghien said:
Hello everyone, i got rooted Rog Phone 2 and after rooting my rog phone 2 i dont have wifi signal anymore. i unroot my phone by flashing stock + tried flashing stock boot.img but wifi is still not working, what happened and how can i fix it?
Click to expand...
Click to collapse
Hello dungnghien,
Could you please share the steps to root it? Also, where can I find the stock firmware in case things don't go well and I need to rom it.
Would appreciate your help.
So I unlocked bootloader using apk from asus site and patched boot.img using magisk. Now how to flash "magisk_patched.img"?
Can someone help please?
havork said:
So I unlocked bootloader using apk from asus site and patched boot.img using magisk. Now how to flash "magisk_patched.img"?
Can someone help please?
Click to expand...
Click to collapse
Follow the same procedure done for the ROG phone.
https://forum.xda-developers.com/rog-phone/how-to/guide-root-t3865490
Rashad83 said:
Follow the same procedure done for the ROG phone.
https://forum.xda-developers.com/rog-phone/how-to/guide-root-t3865490
Click to expand...
Click to collapse
Tried that already. No luck.
Is the phone supposed to go into some special download mode screen like on Samsung?
havork said:
Tried that already. No luck.
Is the phone supposed to go into some special download mode screen like on Samsung?
Click to expand...
Click to collapse
After patching the boot.img did you boot into fastboot mode and runned the command for flashing the patched boot.img.
Was the flash successfull or not?
Please be specific in what step you are having issues with and what actions you took.
Rashad83 said:
After patching the boot.img did you boot into fastboot mode and runned the command for flashing the patched boot.img.
Was the flash successfull or not?
Please be specific in what step you are having issues with and what actions you took.
Click to expand...
Click to collapse
I'm trying to follow steps from the tutorial.
Device is on, USB debugging on
adb devices list my device
adb reboot recovery reboots into recovery, but I don't see "Select ADB on phone" option antwhere in recovery.
havork said:
I'm trying to follow steps from the tutorial.
Device is on, USB debugging on
adb devices list my device
adb reboot recovery reboots into recovery, but I don't see "Select ADB on phone" option antwhere in recovery.
Click to expand...
Click to collapse
There is no such option with the stock recovery. Any way why do you need that. You don't need to use ADB commands to flash the patched boot.img.
Rashad83 said:
There is no such option with the stock recovery. Any way why do you need that. You don't need to use ADB commands to flash the patched boot.img.
Click to expand...
Click to collapse
So how do I flash the patched image? I really need to root this thing and would appreciate the help.
In Samsung phones it's pretty easy, boot into download mode and flash using odin, how to do that on this phone?
Anyone wanna report if there's any issues after rooting the device?
havork said:
So how do I flash the patched image? I really need to root this thing and would appreciate the help.
In Samsung phones it's pretty easy, boot into download mode and flash using odin, how to do that on this phone?
Click to expand...
Click to collapse
Follow step 8 in the tutorial, are you following the steps in the first page of the link i gave?, because the steps are straight forward.
Step 8
Rashad83 said:
Follow step 8 in the tutorial, are you following the steps in the first page of the link i gave?, because the steps are straight forward.
Click to expand...
Click to collapse
Turn device off.
hold down volume up and power button.
I get these three options you see in screenshot.
No download mode option.
havork said:
Turn device off.
hold down volume up and power button.
I get these three options you see in screenshot.
No download mode option.
Click to expand...
Click to collapse
There used to be a fastboot mode on the ROG phone on Android Oreo, i am not sure if things changed with Android Pie.
Anyway try the hardware method to connect, turn your phone off and connect it to the PC using the side port make sure to hold the low volume key when connecting the phone to the PC. See if a fastboot mode black screen shows up.
If not:
On the bootloader screan the second one you showed. On your PC after going to your platform tools and running the cmd window from there type the command:
Fastboot devices
Does it recognize your device?, if it does run the 2 commands stated in step 8. But do it on your own risk if something goes wrong you might brick the device and if you are not able to flash back the stock boot i am afraid you will end up with a bricked device until a solution is suggested.
I can't get into fast boot mode. Tried all options, volume up, volume down, usb, no usb, debugging on, debugging off...
No luck.
$20 for whoever helps me get this thing rooted.
havork said:
I can't get into fast boot mode. Tried all options, volume up, volume down, usb, no usb, debugging on, debugging off...
No luck.
$20 for whoever helps me get this thing rooted.
Click to expand...
Click to collapse
Maybe @Barcovn can help since he got root.

Categories

Resources