EDIT:
I was being stupid, wasn't reading the screen properly - novice mistake, should know better
I can get into bootloader and fastboot can see phone
Extracted boot.img from oreo.zip and phone boots
ben_pyett said:
I downloaded and flashed the latest Oreo update - happy days - this booted fine.
I subsequently flashed TWRP and then superSU ever since the device fails to boot, just stays on the oneplus screen, powered by android splash screen...
I was able to get into recovery (TWRP) so I tried to reflash the oreo update by adb sideload, this failed and crashed adb on my Windows 10 PC
At this point I thought that possibly reverting to stock recovery might be an idea, not the best I've had! After this I seemed to go backwards...
I'm using the latest platform tools from google, adb and fastboot cannot find the device.
I am unable to get into the bootloader, by holding volume down and power
Only able to effectively power cycle the device, can't get into recovery or bootloader and the PC can't see the device
Any help or guidance greatly appreciated - getting desperate.
Click to expand...
Click to collapse
Why not try mega unbrick?
Droidcore said:
Why not try mega unbrick?
Click to expand...
Click to collapse
on that now, cheers
I may need this as well. What's Mega Unbrick and where do I find it?
I managed to install open beta 16 successfully, and tried flashing magisk ..but it gets stuck at the boot logo(even after 20 mins)..I tried flashing super su..the same error occurs..please suggest a solution..how to root Oreo ob16 using magisk?
tvakshaykumar said:
I managed to install open beta 16 successfully, and tried flashing magisk ..but it gets stuck at the boot logo(even after 20 mins)..I tried flashing super su..the same error occurs..please suggest a solution..how to root Oreo ob16 using magisk?
Click to expand...
Click to collapse
i think too early to be thinking about rooting OREO. they just released it man. I dont htink Magisk or SuperSU support it at the moment. Could be wrong.
inasar said:
i think too early to be thinking about rooting OREO. they just released it man. I dont htink Magisk or SuperSU support it at the moment. Could be wrong.
Click to expand...
Click to collapse
I keep reading lots of posts where people root Oreo, but whenever I try, even using latest superSU SR5 I get stuck booting.
Any ideas what I'm missing?
ben_pyett said:
I keep reading lots of posts where people root Oreo, but whenever I try, even using latest superSU SR5 I get stuck booting.
Any ideas what I'm missing?
Click to expand...
Click to collapse
How were you able to get into TWRP from your oneplus splash screen?
inasar said:
How were you able to get into TWRP from your oneplus splash screen?
Click to expand...
Click to collapse
AT the options screen, just before the splash screen , make use of the volume buttons to select fastboot and then flash TWRP, reboot fastboot and then choose recovery
inasar said:
i think too early to be thinking about rooting OREO. they just released it man. I dont htink Magisk or SuperSU support it at the moment. Could be wrong.
Click to expand...
Click to collapse
SuperSU SR5 works with the newest beta.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
ben_pyett said:
EDIT:
I was being stupid, wasn't reading the screen properly - novice mistake, should know better
I can get into bootloader and fastboot can see phone
Extracted boot.img from oreo.zip and phone boots
Click to expand...
Click to collapse
thank u, could have used this an hour ago, but i used the mega unbrick and all is well, but thank u, b/c i may mess around with it later.
ben_pyett said:
AT the options screen, just before the splash screen , make use of the volume buttons to select fastboot and then flash TWRP, reboot fastboot and then choose recovery
Click to expand...
Click to collapse
yeah tried that. No cigar. The phone gets stuck on the oneplus logo and nothing happens.
I guess going the unbrick-qualcomm tool way is the only option left now. I was so dreading this...
inasar said:
yeah tried that. No cigar. The phone gets stuck on the oneplus logo and nothing happens.
I guess going the unbrick-qualcomm tool way is the only option left now. I was so dreading this...
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...b16-nougat-t3689356/post74173258#post74173258
Related
I managed to successfully root my phone and install a custom recovery..but I wanted to restore it and that is when all hell broke loose.
I now have no service/wifi and my phones stuck on airplane mode. It came with stock 4.4..4 OS. It's a 2nd gen US Moto G and even though I launch the fastboot flash mode, anytime I try to flash something I get; hab check failed for primary_gpt. I can not flash the Primary GPT at ALL. The firmware I downloaded was Android 4.4.4
Blur_Version.21.11.17.titan_retuaws.retuaws.en.US and nothing will flash through cmd.
Am I totally boned with a $179 dollar paperweight?
MortaLPortaL said:
I managed to successfully root my phone and install a custom recovery..but I wanted to restore it and that is when all hell broke loose.
I now have no service/wifi and my phones stuck on airplane mode. It came with stock 4.4..4 OS. It's a 2nd gen US Moto G and even though I launch the fastboot flash mode, anytime I try to flash something I get; hab check failed for primary_gpt. I can not flash the Primary GPT at ALL. The firmware I downloaded was Android 4.4.4
Blur_Version.21.11.17.titan_retuaws.retuaws.en.US and nothing will flash through cmd.
Am I totally boned with a $179 dollar paperweight?
Click to expand...
Click to collapse
Do you get a pre verification error? I just posted this question yesterday, and I was helped out. I had exactly the same issue as you had, i think
http://forum.xda-developers.com/moto-g-2014/help/help-asap-fastboot-preflash-validation-t2949337
mahendru1992 said:
Do you get a pre verification error? I just posted this question yesterday, and I was helped out. I had exactly the same issue as you had, i think
http://forum.xda-developers.com/moto-g-2014/help/help-asap-fastboot-preflash-validation-t2949337
Click to expand...
Click to collapse
Funny thing is, it was the firmware I was using along with ADB not being installed.
I got everything up and running. Rooted w/ TWRP. But I am unsure if I can unroot and lock the bootloader so I can hopefully get the OTA to 5.0
MortaLPortaL said:
Funny thing is, it was the firmware I was using along with ADB not being installed.
I got everything up and running. Rooted w/ TWRP. But I am unsure if I can unroot and lock the bootloader so I can hopefully get the OTA to 5.0
Click to expand...
Click to collapse
You don't need to lock your bootloader to receive the update. What you need is stock recovery, stock rom which in essence is everything stock. Just let the bootloader remain unlocked as I've heard that there still isn't a way to unlock the bootloader if you upgrade with it locked.
Mind you this is all heresay
mahendru1992 said:
You don't need to lock your bootloader to receive the update. What you need is stock recovery, stock rom which in essence is everything stock. Just let the bootloader remain unlocked as I've heard that there still isn't a way to unlock the bootloader if you upgrade with it locked.
Mind you this is all heresay
Click to expand...
Click to collapse
I tried to flash the recovery with the recovery.img and it worked until it showed the android with the red triangle. never goes any further than that. Reflashing TWRP is fine but stock is a no go.
MortaLPortaL said:
I tried to flash the recovery with the recovery.img and it worked until it showed the android with the red triangle. never goes any further than that. Reflashing TWRP is fine but stock is a no go.
Click to expand...
Click to collapse
The Android with the red exclamation sign IS your recovery! To see the options: press the volume up button for 10-15 seconds. Then press the power button with it, and let go! Voilà: your stock recovery! It's hidden, because it's not meant for the 'common user'.
smitharro said:
The Android with the red exclamation sign IS your recovery! To see the options: press the volume up button for 10-15 seconds. Then press the power button with it, and let go! Voilà: your stock recovery! It's hidden, because it's not meant for the 'common user'.
Click to expand...
Click to collapse
haha well thank you!
I feel hella stupid in a sense..but I appreciate you guys for being awesome and patient.
MortaLPortaL said:
I managed to successfully root my phone and install a custom recovery..but I wanted to restore it and that is when all hell broke loose.
I now have no service/wifi and my phones stuck on airplane mode. It came with stock 4.4..4 OS. It's a 2nd gen US Moto G and even though I launch the fastboot flash mode, anytime I try to flash something I get; hab check failed for primary_gpt. I can not flash the Primary GPT at ALL. The firmware I downloaded was Android 4.4.4
Blur_Version.21.11.17.titan_retuaws.retuaws.en.US and nothing will flash through cmd.
Am I totally boned with a $179 dollar paperweight?
Click to expand...
Click to collapse
your post helpme to find what i was doing wrong.
in my particular case, i just needed to find my own Firmware (stock version) of kitkat 4.4.4 for my country, COLOMBIA. and that just went great. after that, again, flash Titan 2.0.3beta, that was it. Smooth as a criminal!
I currently am trying to install CM12.1 onto my Amazon Fire 7, but unfortunately, it looks like I may have messed up in the process (I am stuck with the Amazon logo re-looping every ~15-20 seconds). I am able to go into the safe recovery mode, so I assume I haven't bricked the device completely, but I was wondering, what exactly is the best way to flash CM12.1 onto this device?
There seems to be an excessive amount of information, but very little organization, so would love to hear what the "best" steps would be to get CM12.1 on this bad boy.
I don't have the device yet but from what i read you need to tell us more info like what was your amazon v. 5.0.1 or 5.1.1 and how you install cm by TWRP or flash fire
Sent from my iPhone using Tapatalk
it will all depend on the version you have, but here you will find most info.
http://forum.xda-developers.com/amazon-fire/general/videos-tutorials-how-to-root-flash-roms-t3254268
shabuboy said:
it will all depend on the version you have, but here you will find most info.
http://forum.xda-developers.com/amazon-fire/general/videos-tutorials-how-to-root-flash-roms-t3254268
Click to expand...
Click to collapse
So I went ahead and installed the original firmware (5.1.1), but now am wondering where do I go from here. I have the device rooted and installed Flashify, but I am not sure how to install TWRP for 5.1.1, as I was using Rootjunky's .bat file.
darkgiant said:
So I went ahead and installed the original firmware (5.1.1), but now am wondering where do I go from here. I have the device rooted and installed Flashify, but I am not sure how to install TWRP for 5.1.1, as I was using Rootjunky's .bat file.
Click to expand...
Click to collapse
You can't install TWRP on 5.11, if you want to flash roms you have to use FlashFire now.
This is due to the 5.11 ota update including a bootloader update which removes the ability to fastboot boot.
Just follow the instructions to install CM 12.1 and wait for it to boot.
Ownster said:
You can't install TWRP on 5.11, if you want to flash roms you have to use FlashFire now.
This is due to the 5.11 ota update including a bootloader update which removes the ability to fastboot boot.
Click to expand...
Click to collapse
Yeah, so I just found that out few seconds ago. I tried to flash and install CM, but after the reboot, it just goes back to the FireOS "Optimizing system storage and applications..." screen, no idea what I am doing wrong...
I am also wiping everything too before I flash the CM and GAPPS zip files
darkgiant said:
I am also wiping everything too before I flash the CM and GAPPS zip files
Click to expand...
Click to collapse
I would be very careful using flashfire if your coming from fire os 5.1.1, we cannot use TWRP and a few people(myself included) have lost access to Amazon recovery, if you get stuck in a boot loop you have no way to recover your device, your best bet is to wait to see if a more secure way appears of flashing a device that has been using fire os 5.1.1.
abacabie said:
I would be very careful using flashfire if your coming from fire os 5.1.1, we cannot use TWRP and a few people(myself included) have lost access to Amazon recovery, if you get stuck in a boot loop you have no way to recover your device, your best bet is to wait to see if a more secure way appears of flashing a device that has been using fire os 5.1.1.
Click to expand...
Click to collapse
I have no idea what you are talking about. You can most certainly reflash the Amazon firmware when you are stuck in the boot cycle by transferring the file from ADB (after holding volume down + power for more than 10 seconds), and than restart the device, and you are back to FireOS 5.1.1.
I have already went ahead and Flashed SlimLP, and so far so good, it seems fine to me, I guess I'll have to wait and see how stable it is.
darkgiant said:
I have no idea what you are talking about. You can most certainly reflash the Amazon firmware when you are stuck in the boot cycle by transferring the file from ADB (after holding volume down + power for more than 10 seconds), and than restart the device, and you are back to FireOS 5.1.1.
Click to expand...
Click to collapse
Glad it worked well for you. Not everyone has been so fortunate. One persons favorable experience does not equate to everyone. Some of those impacted are veteran users who 'lost' devices testing out code and techniques that you are now benefiting from.
darkgiant said:
I have no idea what you are talking about. You can most certainly reflash the Amazon firmware when you are stuck in the boot cycle by transferring the file from ADB (after holding volume down + power for more than 10 seconds), and than restart the device, and you are back to FireOS 5.1.1.
I have already went ahead and Flashed SlimLP, and so far so good, it seems fine to me, I guess I'll have to wait and see how stable it is.
Click to expand...
Click to collapse
If you read my post properly i said " lost access to Amazon recovery" , there is no way to transfer the file from ADB as ADB is not there, due to the fact that there is no Amazon recovery, holding volume down + power does nothing, if you look around the forum you will see this has happened to a few people myself included .
darkgiant said:
I have no idea what you are talking about. You can most certainly reflash the Amazon firmware when you are stuck in the boot cycle by transferring the file from ADB (after holding volume down + power for more than 10 seconds), and than restart the device, and you are back to FireOS 5.1.1.
I have already went ahead and Flashed SlimLP, and so far so good, it seems fine to me, I guess I'll have to wait and see how stable it is.
Click to expand...
Click to collapse
He's talking about how his device got buggered from a dirty Rom load. In his case and for a few others, they've lost the option to sideload back to stock.
Anyway here's the bare minimum process, since it sounds like you've gone through the details parts of Rom loading before.
#1 restore to stock rom 5.1.1
#2 install SuperSU/Root
#3 install flashfire
#4 install CM/SlimLP and Gapps (pico, micro, mini) of your choice, and your done.
When I put CM on my 5.1.1 Fire device, I installed flashfire.apk manually, used open Gapps pico, and the CM 12-30-2015 image.
abacabie said:
If you read my post properly i said " lost access to Amazon recovery" , there is no way to transfer the file from ADB as ADB is not there, due to the fact that there is no Amazon recovery, holding volume down + power does nothing, if you look around the forum you will see this has happened to a few people myself included .
Click to expand...
Click to collapse
Gotcha, didn't know there was level of increments the relooping represented. Well either way, hopefully something gets developed to all the "hard-bricked" users.
Hey, was just setting up my mi5 for custom roms. Got the bootloader unlocked, then installed TWRP via fastboot as per the instructions here (https://twrp.me/devices/xiaomimi5.html).
After I got into TWRP I made a quick backup of the image, and then set the phone to reboot. Now its in a bootloop, flashing the mi logo (and bootloader unlock on the bottom). Doesn't turn off, doesn't do anything when plugged into pc, fastboot reboot doesn't do anything.
Any ideas? Didn't think I had done anything wrong (done this kind of thing a couple times before).
Cheers!
EDIT: Hang on, managed to get into fastboot, I guess I should be able to sort things out from there? What should I aim to do. I can also get into recovery. Still won't boot into system anymore though.
flobbadob said:
Hey, was just setting up my mi5 for custom roms. Got the bootloader unlocked, then installed TWRP via fastboot as per the instructions here (https://twrp.me/devices/xiaomimi5.html).
After I got into TWRP I made a quick backup of the image, and then set the phone to reboot. Now its in a bootloop, flashing the mi logo (and bootloader unlock on the bottom). Doesn't turn off, doesn't do anything when plugged into pc, fastboot reboot doesn't do anything.
Any ideas? Didn't think I had done anything wrong (done this kind of thing a couple times before).
Cheers!
EDIT: Hang on, managed to get into fastboot, I guess I should be able to sort things out from there? What should I aim to do. I can also get into recovery. Still won't boot into system anymore though.
Click to expand...
Click to collapse
Which twrp version are you using?
Did you actually flash any custom rom or do you try to start miui?
Did you change any partition?
Something similar happened to me one time. I solved it by doing the root right after installing the twrp. And magically started my rom.
lanceindie said:
Something similar happened to me one time. I solved it by doing the root right after installing the twrp. And magically started my rom.
Click to expand...
Click to collapse
+1! Thanks :highfive:
Did you solve it? I might have some ideas.
Hey there so, I've recently been trying to root my new Nokia 8. I have successfully unlocked the bootloader via downgrade to Android 8.1, and running HMD's app. I then have updated to 9 via OTA, and flashed TWRP to boot_b (the current active slot). Next i flashed Magisk 18.1 from the official thread here on XDA, using TWRP. Upon reboot, the phone now hangs and does not respond to any input. My only option is to let it go flat. Attempting to charge it afterwards, results in the red battery plug in icon, which does come up if i press any buttons. After it charges enough, it attempts to boot (kind of?) on its own, and just freezes, and i'm back to square one. This is a brand new phone so this would suck so bad if i can't fix it..
Thanks for any help guys
t0r3n0 said:
Hey there so, I've recently been trying to root my new Nokia 8. I have successfully unlocked the bootloader via downgrade to Android 8.1, and running HMD's app. I then have updated to 9 via OTA, and flashed TWRP to boot_b (the current active slot). Next i flashed Magisk 18.1 from the official thread here on XDA, using TWRP. Upon reboot, the phone now hangs and does not respond to any input. My only option is to let it go flat. Attempting to charge it afterwards, results in the red battery plug in icon, which does come up if i press any buttons. After it charges enough, it attempts to boot (kind of?) on its own, and just freezes, and i'm back to square one. This is a brand new phone so this would suck so bad if i can't fix it..
Thanks for any help guys
Click to expand...
Click to collapse
Which version of twrp did you flash ? Where did you get it from?
Flash the stock recovery of your pie version using the right file from here http://bit.ly/nokia-nb1 and then do a factory reset or sideload the pie rom.
Once that is done use the same link to flash the corresponding patched twrp boot img, boot into recovery and then flash magisk from inside twrp
MDV106 said:
Which version of twrp did you flash ? Where did you get it from?
Flash the stock recovery of your pie version using the right file from here bit.ly/nokia-nb1 and then do a factory reset or sideload the pie rom.
Once that is done use the same link to flash the corresponding patched twrp boot img, boot into recovery and then flash magisk from inside twrp
Click to expand...
Click to collapse
I got the TWRP version from the folder from that link actually.
I've managed to get the phone to boot somehow. The phone would expose fastboot for a few seconds after having just enough battery from getting a bit of charge after letting it go flat, before freezing when presumably trying to load the OS. So i managed to send 'fastboot reboot recovery' to it after letting it go flat once again, and successfully entered TWRP, and factory reset. Now my phone boots into Android, TWRP still flashed, and bootloader unlocked, but no root. What would the safest option to install magisk? Wouldn't want to brick the phone again...
t0r3n0 said:
I got the TWRP version from the folder from that link actually.
I've managed to get the phone to boot somehow. The phone would expose fastboot for a few seconds after having just enough battery from getting a bit of charge after letting it go flat, before freezing when presumably trying to load the OS. So i managed to send 'fastboot reboot recovery' to it after letting it go flat once again, and successfully entered TWRP, and factory reset. Now my phone boots into Android, TWRP still flashed, and bootloader unlocked, but no root. What would the safest option to install magisk? Wouldn't want to brick the phone again...
Click to expand...
Click to collapse
you can install it using Magisk Manager apk, or flash the Magisk zip file inside TWRP, your choice. I dont think either of the two menthods are risky
t0r3n0 said:
Hey there so, I've recently been trying to root my new Nokia 8. I have successfully unlocked the bootloader via downgrade to Android 8.1, and running HMD's app. I then have updated to 9 via OTA, and flashed TWRP to boot_b (the current active slot). Next i flashed Magisk 18.1 from the official thread here on XDA, using TWRP. Upon reboot, the phone now hangs and does not respond to any input. My only option is to let it go flat. Attempting to charge it afterwards, results in the red battery plug in icon, which does come up if i press any buttons. After it charges enough, it attempts to boot (kind of?) on its own, and just freezes, and i'm back to square one. This is a brand new phone so this would suck so bad if i can't fix it..
Thanks for any help guys
Click to expand...
Click to collapse
I currently have a similar problem. successfully installed twrp and booted into recovery to see if it works. It did. so now i got the magisk install zip and wanted to install it via twrp, but after executing adb reboot recovery my phone now is stuck on the bootloader unlocked warning screen. The phone doesnt react to any input and doesnt connect to adb or fastboot. currently waiting for the battery to die and try with a fresh reboot after that...
shadow87qft said:
I currently have a similar problem. successfully installed twrp and booted into recovery to see if it works. It did. so now i got the magisk install zip and wanted to install it via twrp, but after executing adb reboot recovery my phone now is stuck on the bootloader unlocked warning screen. The phone doesnt react to any input and doesnt connect to adb or fastboot. currently waiting for the battery to die and try with a fresh reboot after that...
Click to expand...
Click to collapse
For me, i found that fastboot was being exposed for a few seconds when it would start to turn back on after the battery dying out. I was able to send 'fastboot reboot recovery' and it didn't boot into recovery, but it booted into Android... A bit strange.
Hello Everyone
After a series of frustrating efforts to install custom ROM in my Nokia 8 (TA 1004) device, I gave up and ultimately decided to go with the official ROM (stock was android 8) and updated it to android 9 via OTA update and went ahead to install TWRP and Magisk for root.
It was all fine, but then I launched the Magisk app and it said that it needs to download some files, which it did, then it went ahead for a reboot.
And now my phone is stuck on NOKIA logo.
I can't seem to power it off or restart it using any key combinations. Vol UP + Power, Vol Down+ Power, All three keys, I tried everything, even for 50-60 seconds. But it won't change. It's stuck on NOKIA boot logo.
Any help would be really appreciated.
i have the same problem! Please, answer
sharmamadhus said:
Hello Everyone
After a series of frustrating efforts to install custom ROM in my Nokia 8 (TA 1004) device, I gave up and ultimately decided to go with the official ROM (stock was android 8) and updated it to android 9 via OTA update and went ahead to install TWRP and Magisk for root.
It was all fine, but then I launched the Magisk app and it said that it needs to download some files, which it did, then it went ahead for a reboot.
And now my phone is stuck on NOKIA logo.
I can't seem to power it off or restart it using any key combinations. Vol UP + Power, Vol Down+ Power, All three keys, I tried everything, even for 50-60 seconds. But it won't change. It's stuck on NOKIA boot logo.
Any help would be really appreciated.
Click to expand...
Click to collapse
Which TWRP did you install?
OneWayGamer said:
Which TWRP did you install?
Click to expand...
Click to collapse
I installed 3.2.3.1, the last one from their site, for nokia 8
Johnnycazh said:
I installed 3.2.3.1, the last one from their site, for nokia 8
Click to expand...
Click to collapse
Don't use that one. It is buggy. Use the one from XDA
OneWayGamer said:
Don't use that one. It is buggy. Use the one from XDA
Click to expand...
Click to collapse
yes, but now i can't reboot in twrp, or in download mode. It is just stuck on logo and i cant do anything. The phone is at a service rn, and i hope they could flash its original rom. After that, i wanna try to install twrp from XDA. Thanks, anyway!
How could i flash the rom from Nokia when it is recognized as MTP?