Related
Hi
Since updating my OPO to YOG4PAS1N0 I couldn't reboot my OPO. Since the last update it won't even boot any more. I've reflashed to stock 4.4.4, installed every update and had the same issue. I even tried to flash the zip true recovery, but i got an error while doing it. So, after three times of updating, I'm back to square one.
After going back to stock I have to factory reset in recovery, otherwise the OPO won't boot.
But of course I'd like to install Lollipop (and later Marshmallow). What can I do? I have a Mac with OSX 10.11 and a laptop with Windows 7, so I'm able to use both.
I did the flashing on my Macbook with the Toolkit found here. But I don't think there's an issue with this, as it uses the terminal. It's just easier then to type it all myself
Thanks in advance.
erdeebee said:
Hi
Since updating my OPO to YOG4PAS1N0 I couldn't reboot my OPO. Since the last update it won't even boot any more. I've reflashed to stock 4.4.4, installed every update and had the same issue. I even tried to flash the zip true recovery, but i got an error while doing it. So, after three times of updating, I'm back to square one.
After going back to stock I have to factory reset in recovery, otherwise the OPO won't boot.
But of course I'd like to install Lollipop (and later Marshmallow). What can I do? I have a Mac with OSX 10.11 and a laptop with Windows 7, so I'm able to use both.
I did the flashing on my Macbook with the Toolkit found here. But I don't think there's an issue with this, as it uses the terminal. It's just easier then to type it all myself
Thanks in advance.
Click to expand...
Click to collapse
It'd help if you actually posted what errors you're getting, without information like that it's virtually impossible to troubleshoot. Anyway, your best bet is probably just to flash the stock images with fastboot. Back up anything important first as this will wipe your device. See section 8 of my guide:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
The only error I got, was that it's impossible to boot. I'll try your guide asap
Heisenberg said:
It'd help if you actually posted what errors you're getting, without information like that it's virtually impossible to troubleshoot. Anyway, your best bet is probably just to flash the stock images with fastboot. Back up anything important first as this will wipe your device. See section 8 of my guide:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Click to expand...
Click to collapse
I unlocked the bootloader.
I installed the latest fastboot image.
Now my OPO is stuck again at the 1+ / Powered by Android-screen. I can't boot into recovery, but fastboot mode is still possible.
Everything up to cm-12.0-YNG1TAS2XK-bacon-signed-fastboot seems to work fine.
erdeebee said:
I unlocked the bootloader.
I installed the latest fastboot image.
Now my OPO is stuck again at the 1+ / Powered by Android-screen. I can't boot into recovery, but fastboot mode is still possible.
Click to expand...
Click to collapse
erdeebee said:
Everything up to cm-12.0-YNG1TAS2XK-bacon-signed-fastboot seems to work fine.
Click to expand...
Click to collapse
Is there a reason you're using that particular build instead of the latest? How are you installing it?
Heisenberg said:
Is there a reason you're using that particular build instead of the latest? How are you installing it?
Click to expand...
Click to collapse
I'm sorry, I thought my message was clear. The latest build gives the same problem. With this build, I'm able to boot. I installed this in terminal as a fastboot-images.
This guy has the exact same problem.
erdeebee said:
This guy has the exact same problem.
Click to expand...
Click to collapse
Assuming that you want to upgrade your OPO to latest available version of Cyanogen
- Flash latest *fastboot* image from here http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
- If you have already tried above step, flash cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip and then upgrade via OTA incremental update zip
Mr hOaX said:
Assuming that you want to upgrade your OPO to latest available version of Cyanogen
- Flash latest *fastboot* image from here http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
- If you have already tried above step, flash cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip and then upgrade via OTA incremental update zip
Click to expand...
Click to collapse
I've tried the first, didn't work. I've tried flashing 11S and started upgrading. I didn't have issues until 12.0. When I got to 12.1 I couldn't reboot (but I could shut down and boot). With the latest update I couldn't even boot normally.
Anyone has some idea?
Verstuurd vanaf mijn A0001 met Tapatalk
erdeebee said:
Anyone has some idea?
Verstuurd vanaf mijn A0001 met Tapatalk
Click to expand...
Click to collapse
Not sure if its a language barrier but first of you are going to have to supply more information than that. Secondly what have you tried to fix it and especially since there are tutorial out the waaaaahzooo in here on how to repair your "bricked" phone.
Please research make some attempts and if any issue please document in full what your issue is. I guarantee you though whatever it is someone here has gone through it already so search thorough
playya said:
Not sure if its a language barrier but first of you are going to have to supply more information than that. Secondly what have you tried to fix it and especially since there are tutorial out the waaaaahzooo in here on how to repair your "bricked" phone.
Please research make some attempts and if any issue please document in full what your issue is. I guarantee you though whatever it is someone here has gone through it already so search thorough
Click to expand...
Click to collapse
What I have tried is on page 1 of this thread.
I tried to install 4.4.4 with a flashable zip and then installed all updates. I installed the 5.1.1 zip. I installed the fastboot 5.1.1 and 4.4.4 and installed all updates.
Now I'm on 5.0.
On the last update I couldn't update reboot or boot anymore. The update before that I couldn't reboot, bu I could boot.
erdeebee said:
What I have tried is on page 1 of this thread.
I tried to install 4.4.4 with a flashable zip and then installed all updates. I installed the 5.1.1 zip. I installed the fastboot 5.1.1 and 4.4.4 and installed all updates.
Now I'm on 5.0.
On the last update I couldn't update reboot or boot anymore. The update before that I couldn't reboot, bu I could boot.
Click to expand...
Click to collapse
My bad on that did not even realize there was another page.. dont know how that happened... Wow I say just start from scratch and go to cm page and download the latest stock software. I am sorry I see others have tried to help you and to be honest your breakdown is a lil confusing. NO worries though hopefully someone will come along to help
Hey folks; I'm hoping I can get some advice or pointers, or maybe just a slap upside the head with something I've missed.
I have one of the original Shield tablets, and played around with it quite a lot, installing various custom ROMs from the marvelous directions I've found here. When the battery thing happened, I submitted the required info and happily received my new tablet. The original was rooted and customised still, kill-switch averted, and I had two working tablets. I gave the new stock one to my wife.
But then, about three months ago, I was playing with mine again installing a newer ROM than the one I was using (I *think* I was going from an older Bliss rom to one of the Cyanogen), and ... Something Happened (tm). The tablet rebooted in the middle of everything, and now won't boot to an image.
I'm on Windows 10 now, and had some fun getting the drivers working, but they seem to. I can communicate with the tablet through Fastboot, but ADB doesn't see it. I've flashed several versions of TWRP to the tablet, and can boot into that recovery - both through Fastboot and the tablet's power+vol-dn buttons. I've used TWRP to flash several different ROMs, and it *appears* to work (there are no errors), but when I reboot the tablet .... nada. Nothing but the Nvidia boot screen for days.
So now... what have I missed? I'm a little reluctant to flash a stock ROM, but I'm at a loss. I used to have more time to fiddle and figure, and I'm afraid that my impatience is going to kill the thing.
Format system and data see if that works
You need to have the latest bootloader to run the latest roms.
Sent from my ZTE A2017U using Tapatalk
skooter32 said:
Format system and data see if that works
Click to expand...
Click to collapse
Have done, but I'll try it again. Thanks
lafester said:
You need to have the latest bootloader to run the latest roms.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I've tried the latest and the not-so-latest, all with similar results.
Hnefatafl said:
I've tried the latest and the not-so-latest, all with similar results.
Click to expand...
Click to collapse
so you wan t your "burning" tablet set again stock?
Did you read about "recovery images" for shield tablet?
If fastboot is working you can flash the recovery image and all will update to the latest(blob,system,boot, etc)
flash latest twrp for shieldtablet.
after that use the nomoreota.zip to prevent the software brick from nvidida
Hnefatafl said:
Have done, but I'll try it again. Thanks
Click to expand...
Click to collapse
Also format data system to something other than ext4 then re format it back
skooter32 said:
Also format data system to something other than ext4 then re format it back
Click to expand...
Click to collapse
can I ask what that should bring?
wiQbold said:
so you wan t your "burning" tablet set again stock?
Did you read about "recovery images" for shield tablet?
If fastboot is working you can flash the recovery image and all will update to the latest(blob,system,boot, etc)
flash latest twrp for shieldtablet.
after that use the nomoreota.zip to prevent the software brick from nvidida
Click to expand...
Click to collapse
No, I don't want it stock at all, I was just worried that was my only option to get this thing to respond again. I was running BlissPop v.somethingorother, but wanted to update. That's when things went awry.
Right, well it looks like I've got this thing going. I could flash TWRP 3.1.0-0, but not any 3.1.1. Cyanogenmod 12 worked. Reading up a little more (it got slow at work for a couple of days...) I flashed the firmware to 5.0, and could now install TWRP 3.1.1-1! Then I could install (in this case) Lineage 14.1, which *almost* worked. It booted, but there's no wifi.
Then I found a suggestion - I think it was on these forums somewhere - and restarted. Wiped all data again, flashed Cyanogenmod 12, no gapps. Restarted, checked everything including wifi, and is good. Rebooted back into recovery, performed a factory reset, then installed Lineage 14.1 and gapps. When it rebooted, everything is working!
So. Firmware. Huh.
Thanks all.
Hnefatafl said:
No, I don't want it stock at all, I was just worried that was my only option to get this thing to respond again. I was running BlissPop v.somethingorother, but wanted to update. That's when things went awry.
Click to expand...
Click to collapse
do not know if you need the bootloader(blob) from nougat to boot up, that lafester told you. but that sounds plausible. skooter says something from re-formating. so if you tried that all and nothing changes? cache and data partition you wiped also, so it has to be work for my understanding.
went always stock, so can t help you..
but you can use recovery images > twrp > bliss/linage. no need to boot up stock?
wiQbold said:
can I ask what that should bring?
Click to expand...
Click to collapse
I have had similar issues and I tried everything even this plus what harm is it going to be and as the fellow below said if ur in fastboot and recovery with no issues then surely u should be flashing stick to fix Ur problem ?
Magisk 16.4. Root
Oxygen 5.1.7
TWRP 3.2.1-0
Hey guys,
I'm noticing an annoying loss of root status on my OP6 on a regular basis now. I think this often happens after the phone went to hibernation mode. The only workaround to fix this is to go back to Recovery and flash it again.
I excluded Magisk from battery optimization already, no improvement.
This did never happen on 5.1.6, so I'm not sure whether the latest update caused this issue or not. I installed the update the official way, through OP's built-in update app (which then downloaded the full Ota anyway).
OPO13R said:
Magisk 16.4. Root
Oxygen 5.1.7
TWRP 3.2.1-0
Hey guys,
I'm noticing an annoying loss of root status on my OP6 on a regular basis now. I think this often happens after the phone went to hibernation mode. The only workaround to fix this is to go back to Recovery and flash it again.
I excluded Magisk from battery optimization already, no improvement.
This did never happen on 5.1.6, so I'm not sure whether the latest update caused this issue or not. I installed the update the official way, through OP's built-in update app (which then downloaded the full Ota anyway).
Click to expand...
Click to collapse
Same thing happened to me after the update, but unfortunately the only way that resolved this,
was to flash the firmware again and wipe everything, at least for me.
samteeee said:
Same thing happened to me after the update, but unfortunately the only way that resolved this,
was to flash the firmware again and wipe everything, at least for me.
Click to expand...
Click to collapse
Looks like I managed to hard-brick my phone at last, by simply reflashing Magisk and doing a factory reset. Can't even fastboot a boot image from my PC any more -.- WTH
OPO13R said:
Looks like I managed to hard-brick my phone at last, by simply reflashing Magisk and doing a factory reset. Can't even fastboot a boot image from my PC any more -.- WTH
Click to expand...
Click to collapse
I doubt it, it's probably "Soft Bricked".
Why don't you boot into the official TWRP and flash the latest OnePlus image(5.1.7)?
samteeee said:
I doubt it, it's probably "Soft Bricked".
Why don't you boot into the official TWRP and flash the latest OnePlus image(5.1.7)?
Click to expand...
Click to collapse
Cause I can't. See, that's what I'm talking about, when I say "hard-bricked". A non-functional fastboot mode means the end of it all :crying:
Have a look here. https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
So, I've flashed OneUI on my phone (I only flashed AP and CSC, no new bootloader), and TWRP doesn't seem to work with it since it can't read or wipe the data partition. Also, booting is a little weird. Sometimes it works perfectly, but sometimes it goes into a freeze bootloop thing where the boot animation freezes, and a few seconds later it reboots. I'm wondering if this has anything to do with me having a treble gsi on the phone before OneUI. Maybe the partition table didn't go back to stock after flashing? (the fstab must have though, since it's in the boot img) Or maybe it has something to do with having a different csc on the phone? (phone is XEH, but the firmware is DBT) I've tried re-flashing it with no luck. (it even freezes just randomly too, then goes into the bootloop.)
VDavid003 said:
So, I've flashed OneUI on my phone (I only flashed AP and CSC, no new bootloader), and TWRP doesn't seem to work with it since it can't read or wipe the data partition. Also, booting is a little weird. Sometimes it works perfectly, but sometimes it goes into a freeze bootloop thing where the boot animation freezes, and a few seconds later it reboots. I'm wondering if this has anything to do with me having a treble gsi on the phone before OneUI. Maybe the partition table didn't go back to stock after flashing? (the fstab must have though, since it's in the boot img) Or maybe it has something to do with having a different csc on the phone? (phone is XEH, but the firmware is DBT) I've tried re-flashing it with no luck. (it even freezes just randomly too, then goes into the bootloop.)
Click to expand...
Click to collapse
Good thing you skip the bootloader and modem.
Are developer who had done kernel and twrp has disappeared.
You can try to send him a pm.
Their are universal twrp that you could try.
What twrp are you using mean build?
mchlbenner said:
What twrp are you using mean build?
Click to expand...
Click to collapse
I tried BlackMesa123's official TWRP, and the treble twrp, none of them worked how they should.
I'm gonna try that one now (actually a little later 'cause personal stuff)...
VDavid003 said:
I tried BlackMesa123's official TWRP, and the treble twrp, none of them worked how they should.
I'm gonna try that one now (actually a little later 'cause personal stuff)...
Click to expand...
Click to collapse
I have flashed the new twrp it seems to work well
From the link I sent you.
https://www.google.com/amp/s/forum....ent/recovery-blackedtwrp-t3881548/amp/?espv=1
Working twrp for ab 2018.
Oh ok, I'll try it soon.
Any idea why do the freezes/bootloops happen tho?
VDavid003 said:
Oh ok, I'll try it soon.
Any idea why do the freezes/bootloops happen tho?
Click to expand...
Click to collapse
I have no I idea I rebooted five times with no mishaps.
Could are twrp is just not fully meant for pie.
mchlbenner said:
I have no I idea I rebooted five times with no mishaps.
Could are twrp is just not fully meant for pie.
Click to expand...
Click to collapse
Idk, currently I'm on stock 9.0 recovery and I'm getting freezes, bootloops but just randomly. I'm thinking maybe somehow it's related to treble... The stock recovery is even complaining about not finding /vendor, and some other partition.
VDavid003 said:
Idk, currently I'm on stock 9.0 recovery and I'm getting freezes, bootloops but just randomly. I'm thinking maybe somehow it's related to treble... The stock recovery is even complaining about not finding /vendor, and some other partition.
Click to expand...
Click to collapse
I would do a reflash .
what did was updated to the new Oreo bootloader then flash a rooted pie backup.
I had no reboots but I rebooted it could take a threw times to reboot.
Since I flash the new twrp I can reboot without issue.
Did you flash your region pie it should not really matter I have a the Russian pie and I flashed a Canadian csc to get volte working.
If you root use magisk 18.1 zip and use the twrp I link you.
mchlbenner said:
I have flashed the new twrp it seems to work well
From the link I sent you.
https://www.google.com/amp/s/forum....ent/recovery-blackedtwrp-t3881548/amp/?espv=1
Working twrp for ab 2018.
Click to expand...
Click to collapse
So I've tried it and same thing... Also, here's what the stock recovery says (sorry for the 2 decades old webcam):
Blackmesa's TWRP:
Treble TWRP:
The one you sent me:
mchlbenner said:
I would do a reflash .
what did was updated to the new Oreo bootloader then flash a rooted pie backup.
I had no reboots but I rebooted it could take a threw times to reboot.
Since I flash the new twrp I can reboot without issue.
Did you flash your region pie it should not really matter I have a the Russian pie and I flashed a Canadian csc to get volte working.
If you root use magisk 18.1 zip and use the twrp I link you.
Click to expand...
Click to collapse
Didn't see you replied. I'll try that - flashing oreo and restoring backup.
VDavid003 said:
So I've tried it and same thing... Also, here's what the stock recovery says (sorry for the 2 decades old webcam):
Blackmesa's TWRP:
Treble TWRP:
The one you sent me:
Click to expand...
Click to collapse
Remember you have to reformat after installing twrp.
It took me only two minutes to find the new twrp.
20 reboots without issue.
mchlbenner said:
Remember you have to reformat after installing twrp.
It took me only two minutes to find the new twrp.
20 reboots without issue.
Click to expand...
Click to collapse
You mean wiping data right?
'cuz that's what's failing on the screenshots.
For me the first about 12 hours was normal, then the freezes and bootloops started happening.
So it didn't fix the bootloops, but at least TWRP works now!
VDavid003 said:
You mean wiping data right?
'cuz that's what's failing on the screenshots.
For me the first about 12 hours was normal, then the freezes and bootloops started happening.
Click to expand...
Click to collapse
No reformat it will whiipe everything mean your downloaded apps
I was able to install TWRP and root with Magisk when the pie update was uploaded on this forum.
---------- Post added at 01:25 PM ---------- Previous post was at 01:24 PM ----------
And yes you need to erase everything
Well, I was able to root and fix twrp, but I still get bootloops and freezes...
I think I'll just wait for pie to be released on my csc and until that, I'll either get used to it or go back to Phh-treble (I've never tought I'd say a custom ROM that is not even meant for this specific device is more stable (for me) than the official)
VDavid003 said:
Well, I was able to root and fix twrp, but I still get bootloops and freezes...
I think I'll just wait for pie to be released on my csc and until that, I'll either get used to it or go back to Phh-treble (I've never tought I'd say a custom ROM that is not even meant for this specific device is more stable (for me) than the official)
Click to expand...
Click to collapse
I am having the exact same issues you are. In fact, are you using my phone when I sleep?
If you want to try out a 9.0 gsi that'll run pretty darn good in the meantime, try aospext's 9. Works well enough to use daily and you'll get a "4g" constant connection.
And since you have the same issues, this should give you a flawless run. If you are just entering a clean treble, wipe it all. Everything including internal. Just not your emovable of course.
Flash the vendor in from A8 that says 8.1 and 9.0 compatible. Flash the .img. Reboot recovery flash vendor again and then gapps. I did magisk after a normal run through and the latest was a 50% pass on safety. Gonna try it again right now for a third time. No issues with booting at all. If you do it differently all hell breaks loose and you'll be booted but with a severe case of "no system webview syndrome" or "chrome ain't no system app useless-lee-itus" The force closing of apps could be mistaken for an old Atari video game..
---------- Post added at 09:28 AM ---------- Previous post was at 08:58 AM ----------
Don't do what i suggested unless you've got a frikken system webview handy from a rom. all nicely in a folder. Toss it rightly in twrp.
mindlery said:
I am having the exact same issues you are. In fact, are you using my phone when I sleep?
If you want to try out a 9.0 gsi that'll run pretty darn good in the meantime, try aospext's 9. Works well enough to use daily and you'll get a "4g" constant connection.
And since you have the same issues, this should give you a flawless run. If you are just entering a clean treble, wipe it all. Everything including internal. Just not your emovable of course.
Flash the vendor in from A8 that says 8.1 and 9.0 compatible. Flash the .img. Reboot recovery flash vendor again and then gapps. I did magisk after a normal run through and the latest was a 50% pass on safety. Gonna try it again right now for a third time. No issues with booting at all. If you do it differently all hell breaks loose and you'll be booted but with a severe case of "no system webview syndrome" or "chrome ain't no system app useless-lee-itus" The force closing of apps could be mistaken for an old Atari video game..
---------- Post added at 09:28 AM ---------- Previous post was at 08:58 AM ----------
Don't do what i suggested unless you've got a frikken system webview handy from a rom. all nicely in a folder. Toss it rightly in twrp.
Click to expand...
Click to collapse
Lol
Well, it's good to see it's not me being stupid or my phone being broken
Soo.. looks like I fixed it.. What I did is downgraded to stock 8.0 and let OTA do it's job. I know it must have updated my bootloader (thus adding new locks to my device) but so far no bootloops,freezes, or anything. It might have been the bootloader, or the modem, or idk.
VDavid003 said:
Soo.. looks like I fixed it.. What I did is downgraded to stock 8.0 and let OTA do it's job. I know it must have updated my bootloader (thus adding new locks to my device) but so far no bootloops,freezes, or anything. It might have been the bootloader, or the modem, or idk.
Click to expand...
Click to collapse
Their where no freezing or issues on Oreo.
Android pie was released and it would freeze at boot and watching videos.
Hi guys,
I made a mistake installing the Android 11 firmware update and afterwards flashing TWRP and installing Magisk.
Second mistake because I couldn't boot I flashed an old Fastboot ROM, but that doesn't help me.
Can anyone please point me to the fastboot rom for android 11 update?
Thank you very much.
ConsoleHax said:
Hi guys,
I made a mistake installing the Android 11 firmware update and afterwards flashing TWRP and installing Magisk.
Second mistake because I couldn't boot I flashed an old Fastboot ROM, but that doesn't help me.
Can anyone please point me to the fastboot rom for android 11 update?
Thank you very much.
Click to expand...
Click to collapse
Did you ever get any help? I am in the same boat.
ConsoleHax said:
Hi guys,
I made a mistake installing the Android 11 firmware update and afterwards flashing TWRP and installing Magisk.
Second mistake because I couldn't boot I flashed an old Fastboot ROM, but that doesn't help me.
Can anyone please point me to the fastboot rom for android 11 update?
Thank you very much.
Click to expand...
Click to collapse
I guess the best way to go back to stock is using msmtool you can find it here: with android 10 for international and European version: Thread '[OP7PRO][LATEST OOS 10.3.8 GM21AA | OOS 10.0.10 GM21BA] Collection of unbrick tools' https://forum.xda-developers.com/t/...0-gm21ba-collection-of-unbrick-tools.3956595/
Piricho said:
Did you ever get any help? I am in the same boat.
Click to expand...
Click to collapse
If you ended with a blinking TWRP just flash the stock/rooted boot.img if you are using stable you can obtain it here(Post in thread 'Android 11 Release - Finally!' https://forum.xda-developers.com/t/android-11-release-finally.4251267/post-84717089)
Or if you are on a Open Beta here: Thread 'OxygenOS Android 11 Betas (OnePlus 7 Pro) released (Open Beta 4 now available)' https://forum.xda-developers.com/t/...o-released-open-beta-4-now-available.4221067/
RokCruz said:
I guess the best way to go back to stock is using msmtool you can find it here: with android 10 for international and European version: Thread '[OP7PRO][LATEST OOS 10.3.8 GM21AA | OOS 10.0.10 GM21BA] Collection of unbrick tools' https://forum.xda-developers.com/t/...0-gm21ba-collection-of-unbrick-tools.3956595/
If you ended with a blinking TWRP just flash the stock/rooted boot.img if you are using stable you can obtain it here(Post in thread 'Android 11 Release - Finally!' https://forum.xda-developers.com/t/android-11-release-finally.4251267/post-84717089)
Or if you are on a Open Beta here: Thread 'OxygenOS Android 11 Betas (OnePlus 7 Pro) released (Open Beta 4 now available)' https://forum.xda-developers.com/t/...o-released-open-beta-4-now-available.4221067/
Click to expand...
Click to collapse
Hey,
I bricked my OP7 after what seemed like successfully installing and using Android 11. I am getting the Teamwin blinking brick.
This(
) seems like something I can do- flashing Fastboot ROM(even though I'll lose data, but wth). Can you please tell me if this comment of yours applies in my case- i.e. is the link you are suggesting for Android 11 Fastboot ROM valid?
saurabh_op7 said:
Hey,
I bricked my OP7 after what seemed like successfully installing and using Android 11. I am getting the Teamwin blinking brick.
This(
) seems like something I can do- flashing Fastboot ROM(even though I'll lose data, but wth). Can you please tell me if this comment of yours applies in my case- i.e. is the link you are suggesting for Android 11 Fastboot ROM valid?
Click to expand...
Click to collapse
Just flash stock boot.img
RokCruz said:
Just flash stock boot.img
Click to expand...
Click to collapse
As a rain check, as I am new to this, and don't want to screw up more,
You mean I can use this method-
Restore OnePlus 7/7T/7T Pro to Stock via Fastboot Commands - DroidWin
to flash the latest stable build on OnePlus support, i.e. this-
https://otafsg1.h2os.com/patch/amaz....P.35_OTA_0350_all_2103221240_3e944b9d067.zip(OnePlus7Oxygen_14.P.32_OTA_032_all_2101280019_b2a62765ba0c485e.zip)
??
Or do you suggest to use the Android 11 firmware available on XDA?
saurabh_op7 said:
As a rain check, as I am new to this, and don't want to screw up more,
You mean I can use this method-
Restore OnePlus 7/7T/7T Pro to Stock via Fastboot Commands - DroidWin
to flash the latest stable build on OnePlus support, i.e. this-
https://otafsg1.h2os.com/patch/amaz....P.35_OTA_0350_all_2103221240_3e944b9d067.zip(OnePlus7Oxygen_14.P.32_OTA_032_all_2101280019_b2a62765ba0c485e.zip)
??
Or do you suggest to use the Android 11 firmware available on XDA?
Click to expand...
Click to collapse
You can do it with the fastboot zip but you need to download all the firmware, in some threads you will find the stock/rooted boot.img from stable and OB, I shared both in this message
RokCruz said:
If you ended with a blinking TWRP just flash the stock/rooted boot.img if you are using stable you can obtain it here(Post in thread 'Android 11 Release - Finally!' https://forum.xda-developers.com/t/android-11-release-finally.4251267/post-84717089)
Or if you are on a Open Beta here: Thread 'OxygenOS Android 11 Betas (OnePlus 7 Pro) released (Open Beta 4 now available)' https://forum.xda-developers.com/t/...o-released-open-beta-4-now-available.4221067/
Click to expand...
Click to collapse
RokCruz said:
You can do it with the fastboot zip but you need to download all the firmware, in some threads you will find the stock/rooted boot.img from stable and OB, I shared both in this message
Click to expand...
Click to collapse
I am pretty sure I know my OS, but is there a way to find out?
I was running the stable, but flashing stock boot just led me to a boot loop with the Original Recovery, it's giving me options to
1. Wipe data and cache
2. Reboot to fastboot
3. Reboot to recovery
The fastboot flash commands above to flash stock OS didn't work, due to one error or another.
Anyhow, I had read somewhere fastboot continue works(here: it wasn't working before for me), so I tried that again, and now I am just stuck on 1+ Fastboot screen. I will wait it out to see if it boots into system.
Otherwise, I am thinking I reload fastboot and flash stock boot just like I did- and from there wipe data, but what do I expect then??
The way I see it, I am just stuck in some serious boot issue, and might eventually have to go down the path of msndownloadtool, any suggestion?
saurabh_op7 said:
I am pretty sure I know my OS, but is there a way to find out?
I was running the stable, but flashing stock boot just led me to a boot loop with the Original Recovery, it's giving me options to
1. Wipe data and cache
2. Reboot to fastboot
3. Reboot to recovery
The fastboot flash commands above to flash stock OS didn't work, due to one error or another.
Anyhow, I had read somewhere fastboot continue works(here: it wasn't working before for me), so I tried that again, and now I am just stuck on 1+ Fastboot screen. I will wait it out to see if it boots into system.
Otherwise, I am thinking I reload fastboot and flash stock boot just like I did- and from there wipe data, but what do I expect then??
The way I see it, I am just stuck in some serious boot issue, and might eventually have to go down the path of msndownloadtool, any suggestion?
Click to expand...
Click to collapse
Flashing the stock boot.img should be enough to boot into system without problems because TWRP can't decrypt data in android 11.
In this point you can try a factory reset from stock recovery this will keep device files but will erase all your config and apps
To figure out what version of firmware you had you can run this command in fastboot
Fastboot getvar all
RokCruz said:
Flashing the stock boot.img should be enough to boot into system without problems because TWRP can't decrypt data in android 11.
In this point you can try a factory reset from stock recovery this will keep device files but will erase all your config and apps
To figure out what version of firmware you had you can run this command in fastboot
Fastboot getvar all
Click to expand...
Click to collapse
Flashing didn't work to boot into system, I was just getting stuck in the Recovery boot loop, it finally booted into system once I wiped my data(files, music, etc -option);
I did try factory reset, only once I cleared the partition, did the boot loop give way to boot into system;
It booted back to Android 11, but it's all glitchy: Boot taking too long, WiFi not switching on, Call not working, Data is working though- basically it's very screwed up, got a couple of errors too- it's like watching an amnesiac old person.. if you get the gist.
So, now I am considering a stable build from Oneplus support website as a local upgrade and booting back to that..
I am hard pressed for options, let me know if you think something else works better, thanks!
saurabh_op7 said:
Flashing didn't work to boot into system, I was just getting stuck in the Recovery boot loop, it finally booted into system once I wiped my data(files, music, etc -option);
I did try factory reset, only once I cleared the partition, did the boot loop give way to boot into system;
It booted back to Android 11, but it's all glitchy: Boot taking too long, WiFi not switching on, Call not working, Data is working though- basically it's very screwed up, got a couple of errors too- it's like watching an amnesiac old person.. if you get the gist.
So, now I am considering a stable build from Oneplus support website as a local upgrade and booting back to that..
I am hard pressed for options, let me know if you think something else works better, thanks!
Click to expand...
Click to collapse
I guess msmtool it's the best way to restore your phone, remember that msmtool will re-lock your bootloader so if you want root you need to unlock your bootloader again.
Use msmtool and instructions form Here(there's an android 9 and android 10 for Global and Europe versions, use android 10)
RokCruz said:
I guess msmtool it's the best way to restore your phone, remember that msmtool will re-lock your bootloader so if you want root you need to unlock your bootloader again.
Use msmtool and instructions form Here(there's an android 9 and android 10 for Global and Europe versions, use android 10)
Click to expand...
Click to collapse
My model is GM1901, in support intro for the link you provided, that's not included?
saurabh_op7 said:
My model is GM1901, in support intro for the link you provided, that's not included?
Click to expand...
Click to collapse
Wait GM1901 is a OnePlus 7(non pro) right?
RokCruz said:
Wait GM1901 is a OnePlus 7(non pro) right?
Click to expand...
Click to collapse
Yeah.. ?
saurabh_op7 said:
Yeah.. ?
Click to expand...
Click to collapse
This is the OnePlus 7 pro forum so, I assume you was a 7 pro user, now all makes sense you don't flash the correct boot.img for your device so all woes wrong.
You need to use msmtool from Here
RokCruz said:
This is the OnePlus 7 pro forum so, I assume you was a 7 pro user, now all makes sense you don't flash the correct boot.img for your device so all woes wrong.
You need to use msmtool from HereI
Click to expand...
Click to collapse
Yeah man, I realised.. anyway, I flashed the boot image from Xda for OP7.. nevertheless, mom tool it is.. thanks..!
RokCruz said:
This is the OnePlus 7 pro forum so, I assume you was a 7 pro user, now all makes sense you don't flash the correct boot.img for your device so all woes wrong.
You need to use msmtool from Here
Click to expand...
Click to collapse
Hey, I am on Mac, I see that Msm is windows-specific.. any way out?
Update: I have been roaming around the corridors of this forum since about a week now. Thanks @RokCruz !!
Finally, used msm tool, although I suspect I still had the option of flashing TWRP and Magisk as I had access to phone and fastboot, but the system was super glitchy.
saurabh_op7 said:
Hey, I am on Mac, I see that Msm is windows-specific.. any way out?
Click to expand...
Click to collapse
I guess that the only way is using the fastboot ROM
RokCruz said:
I guess that the only way is using the fastboot ROM
Click to expand...
Click to collapse
Any idea if we're gonna get one soon?