Database Users

I think I bricked my nexus (my fault) please help!

Hello all,
I think I may have bricked my nexus one. It is completely my fault for attempting things that I knew little about, so flame away But after the flaming, if anyone is willing to help I would be sooooo thankfull...
I successfully rooted my phone following the instructions on this page: (all links edited with a double asterisk as I don't believe I can post links)
h**p://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
Then successfully installed cyanogenmod (which is awesome!) following this page:
h**p://theunlockr.com/2010/01/08/how-to-load-a-custom-rom-on-the-nexus-one/
All was well, I even got the modaco desire rom up and running, and was happily switching back and forth using the recovery screen. I had nand backups for specific setups, etc.
Then I decided it would be good to know how to go back to stock, and found this page:
h**p://**w.androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/
I followed the instructions to the letter (I think) except for erasing userdata (it said "failed: remote not allowed"). I thought that things would be ok, since I'd recently wiped, so I followed the page till the end.
The phone rebooted, and I got the original nexus boot animation - but it's in an endless loop! What's worse, it that now when I try to go to the bootloader or recovery mode, I get the exclamation triangle with the little android.
Is there any way through a command prompt (or other method) that I can fix this? I tried to re-flash the RA recovery image through the command prompt, but the response was, "waiting for device."
ANYTHING that anyone can suggest to help, I would be so thankful! I've been loving the nexus, and hate to think that I crippled it
Thanks in advance,
Randy

I doubt its bricked.
Noticed you didnt mention that fast boot doesnt work? (power button+trackball) try it.
Once you get to fastboot you can flash any ROM back. (fastboot flash **** commands from a command shell)

Did you ever perform a Nand Backup from Recovery?

It's not bricked, the only way to brick is to interrupt power when flashing a Radio image

Connect phone to PC. Open command prompt.
adb reboot recovery
Wipe, reflash.

So far, nobody has managed to brick a Nexus. There is no way as the fastboot mode can restore the whole phone and can't be messed with. Make sure you have the latest version of the SDK with correct USB drivers and fastboot. Then try and reflash the recovery image.
-------------------------------------
Sent from my Nexus One

nexus5894 said:
So far, nobody has managed to brick a Nexus. There is no way as the fastboot mode can restore the whole phone and can't be messed with. Make sure you have the latest version of the SDK with correct USB drivers and fastboot. Then try and reflash the recovery image.
-------------------------------------
Sent from my Nexus One
Click to expand...
Click to collapse
Actually...
http://forum.xda-developers.com/showpost.php?p=6320068&postcount=404

Paul22000 said:
Actually...
http://forum.xda-developers.com/showpost.php?p=6320068&postcount=404
Click to expand...
Click to collapse
............................

It worked!!!!!
It worked!!
britoso, thank you soooooo much! The only way that I knew to get into bootloader/recovery was via power button/volume down, but power/trackball brought up the bootloader screen, and I clicked on fastboot. I was able to flash the RA recover image through the command terminal via fastboot, then able to get into recovery. I had cyan and modaco sense on the sd, and was able to flash one of them on.
​
I never thought I'd be so happy to see "quietly brilliant"!!! I WILL buy you a beer, a case in fact as soon as money clears my paypal account.
I have learned my lesson, research research research. (I did do some, but not enough to feel comfortable with what I was doing - hence my cry for help!)
Other than the phone and OS itself, the thing I like most about the nexus is the fact that one CAN root, and then customize (sold a Telus moto droid because I could not do that very thing).
I digress... thanks again so much!
And Paul, thanks for your sense ROM; I've had HTC phones from the Touch to the the diamond to the Hero, and missed the UI!

Randy Malkoski said:
It worked!!
britoso, thank you soooooo much! The only way that I knew to get into bootloader/recovery was via power button/volume down, but power/trackball brought up the bootloader screen, and I clicked on fastboot. I was able to flash the RA recover image through the command terminal via fastboot, then able to get into recovery. I had cyan and modaco sense on the sd, and was able to flash one of them on.
​
I never thought I'd be so happy to see "quietly brilliant"!!! I WILL buy you a beer, a case in fact as soon as money clears my paypal account.
I have learned my lesson, research research research. (I did do some, but not enough to feel comfortable with what I was doing - hence my cry for help!)
Other than the phone and OS itself, the thing I like most about the nexus is the fact that one CAN root, and then customize (sold a Telus moto droid because I could not do that very thing).
I digress... thanks again so much!
And Paul, thanks for your sense ROM; I've had HTC phones from the Touch to the the diamond to the Hero, and missed the UI!
Click to expand...
Click to collapse
Glad to hear it. You learn the most by trial and error.

I think i got the same problem. i tried to Unlock Bootloader and Root Google Nexus One which was successful but then i tried to superboot it and when it came to the part where you "double click the ‘install-superboot-windows.bat’ file" i clicked it but it did not go to the nnext screen where the superboot completes it just stayed at the "bootloader screen". i must hve not done something or done something wrong i dont know.
So then i unplugged the phone from the pc and rebooted it. when it reeboted i wasnt getting any network, the phone was slow and the notification bar would not slide down...also i noticed the phone restarting on itself...
/i tried all kinds of "restore to factory settings" but not solved. Can anyone tell me what to do tht will work. I coud not understand what was said in the above thread as i am new to this android n my first time rooting n stuff n i believe that solution would work for me too..if some one could please explain in simple tirms the steps i need to take would be good...
Really appreciate it....

revonomics said:
I think i got the same problem. i tried to Unlock Bootloader and Root Google Nexus One which was successful but then i tried to superboot it and when it came to the part where you "double click the ‘install-superboot-windows.bat’ file" i clicked it but it did not go to the nnext screen where the superboot completes it just stayed at the "bootloader screen". i must hve not done something or done something wrong i dont know.
So then i unplugged the phone from the pc and rebooted it. when it reeboted i wasnt getting any network, the phone was slow and the notification bar would not slide down...also i noticed the phone restarting on itself...
/i tried all kinds of "restore to factory settings" but not solved. Can anyone tell me what to do tht will work. I coud not understand what was said in the above thread as i am new to this android n my first time rooting n stuff n i believe that solution would work for me too..if some one could please explain in simple tirms the steps i need to take would be good...
Really appreciate it....
Click to expand...
Click to collapse
Tell me what i need to download again and how to go about it...i really need my phone working again ((((

1 Click root brick?!

So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App

Arun01 said:
So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Motorola published the factory files for Xoom awhile back so if you still have fastboot, you can recover from it.
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard

I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.

Stop using one click crap. If you don't know what you're then you should not be messing with your device.

Sent from my DROIDX using XDA App

I can. Just won't.

Arun01 said:
I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.
Click to expand...
Click to collapse
Type oem unlock again and then flash the stock images...youll be good to go...also there are really good stickies in here that help..pleasedont forget to search before starting a new thread.

albundy2010 said:
I can. Just won't.
Click to expand...
Click to collapse
And this is rude and uncalled for

The OP stated he read quides etc and none of it made sense to him etc. So instead of asking for help a explanation he tries a one click method. Which is stupid. He than softbricks the device and asked for help here.
Then he is told that moto released the factory images and use fastboot if he still has it to recover the device. He then decides to ignore that entirely and go back and try to unroot/restore with the one click BS again. Then he tries to use it again to go back to where he was. Just flat out stupid. He did something when he had no idea wtf he was doing. Was told what to do. Did not do it. He even said it is like Chinese to him.
So I told him to stop messing with one click crap. Which is correct. I told him to stop messing with the ****ing thing. Which is also correct. He needs to learn/understand wtf he is doing. Instead of basically button mashing/trying crap and hoping it will basically fix itself.
On top of that this posted in the wrong section. Uncalled for my ass. He is the one that was rude when told to not mess with the one click or the device. Now this part is rude. **** his stupid ass.

csseale said:
Type oem unlock again and then flash the stock images...youll be good to go...also there are really good stickies in here that help..pleasedont forget to search before starting a new thread.
Click to expand...
Click to collapse
How do i get to that ..and where do i type it at ..i looked in device manager & does recognize the xoom..it says "Motorola USB Device:Motorola Flash Interface"..In properties under "Driver" it has options for driver details..update driver..disable & uninstall.Can i do anything with them?
I tried opening SDK manager but it never lets me type anything in the box as it's always trying to do some kind of update in another window so when i close the window it closes all of the windows.

Sent from my DROIDX using XDA App

Arun01 said:
So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
If they didnt make sense to you in the first place you probably shoud not be attempting to root... U went straight to an old method that even the developer has marked in hs thread can full brick you and should not be used. The xoom costs like 600 bucks... Why wouldnt you do extensive research on how to root? If you did not understand the terms why didn't you research the methods and learn it?
I hope you can flash the factory imagines back through fastboot and adb, but i just do not understand why people attempt this stuff when they have no idea what the terms even mean...
You need to have sdk, hook up to usb on your computer, and follow one of the unlock guides posted on this site... A real one using adb... Then you need to follow a root one...
Sorry that is not more helpful, but half of this experience is that you need to learn what you are doing and the instructions are out there. If they do not make sense at this point im afraid you are stuck. Now the way your device is you have to figure it out...

Arun01 said:
I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.
Click to expand...
Click to collapse
Please check out this thread.It is called Root heaven for a reason. Just about every viable rooting guide, all the files and explanations you will need are here.
http://forum.xda-developers.com/showthread.php?t=1209341
I urge you to just calm down, read about what is the sdk, what is adb, how to recover from a soft brick and so on. The xda xoom forum is all about learning and teaching. We were all noobies once. The Xoom is a very complex device with many models and vesions and one clicks just don't cut it. There are rooting methods that are relatively simple but you really need to be prepared before you get started.
Good luck and don't despair. You'll get there.

Thanks for the help guys.I'm reading through all of the threads and i see a typo in a post that in the command window would've never let me find the sdk tools on my c drive. But after i retyped it i did it & a bunch of writing came up. Trying to figure out now how to flash the stock images to the xoom.
Sent from my DROIDX using XDA App

Arun01 said:
Thanks for the help guys.I'm reading through all of the threads and i see a typo in a post that in the command window would've never let me find the sdk tools on my c drive. But after i retyped it i did it & a bunch of writing came up. Trying to figure out now how to flash the stock images to the xoom.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
at first, make sure you install android sdk correctly. then go to android sdk-folder in your computer, u will find a folder named platform-tool. Press shift+ right click on it, then choose open command window here. After that, type in "adb devices" or "fastboot devives" to check if your xoom is connected. If yes,you good to go. If no, check your android sdk installed process

After i type in abd devices it says list of devices attached but shows nothing..i did copy the sdk tools folder to the c drive like i was told.

@OP
If you can't do it yourself, getting somebody to help you (in person) is always an option. If you live in a major city, advertise on Craigslist or some equivalent. Offer $50 for debricking + some tutorial.

In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.

albundy2010 said:
In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.
Click to expand...
Click to collapse
That's good advice...no reason to re-lock. But get back to square one so that you're functional and then when you're ready to try again, do it the right way.
Again, good luck!

albundy2010 said:
In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.
Click to expand...
Click to collapse
Thanks a lot.I was able to unlock it then it rebooted & stopped at the Motorola screen then i started the 1st command: fastboot flash boot boot.img & it says waiting on device..but nothing happens so far.Should i move on to the next step or retry?

Bootloop on N6P

Hi there.
So I'm using N6P for a year now and updated to 7.1.2 is I'm not mistaken . My N6P is fully stock with locked bootloader , no tweaking etc.
Was casually browsing through my phone suddenly it restarted and into went into a bootloop. I can only access the bootloader. I have tried going into recovery mode which just starts the loop over again.
I have researched just about everything and tried a lot . I just cant seem to get it working .
I really want my personal data on it , its quite important . If there isn't any more choice, then I will be forced to wipe it but until then any suggestions? Please help , thanks .
By the way , my warranty just expired a week ago so luck is surely not on my side .

Enthusiast09 said:
Hi there.
So I'm using N6P for a year now and updated to 7.1.2 is I'm not mistaken . My N6P is fully stock with locked bootloader , no tweaking etc.
Was casually browsing through my phone suddenly it restarted and into went into a bootloop. I can only access the bootloader. I have tried going into recovery mode which just starts the loop over again.
I have researched just about everything and tried a lot . I just cant seem to get it working .
I really want my personal data on it , its quite important . If there isn't any more choice, then I will be forced to wipe it but until then any suggestions? Please help , thanks .
By the way , my warranty just expired a week ago so luck is surely not on my side .
Click to expand...
Click to collapse
Sorry to hear about that. I had the same problem with my modded 6p and had a full backup on my pc and was still under warranty so it worked out fine for me. Unfortunately for you you are most likely not going to be able to fix it even from wiping it. I had the same problem and because I had an unlocked bootloader I was able to do much more than you could with flashing stock images. If you can't enter recovery then you most likely have a brick and can't fix it. I'm not sure if there is a way via adb and fastboot commands with a locked bootloader to retrieve data but I'll let you know ow if I find one. What kind of data do you have? Google usually syncs things like your photos and apps downloaded will be saved in the google play store. I hope this helped?

DEVILOPS 007 said:
Sorry to hear about that. I had the same problem with my modded 6p and had a full backup on my pc and was still under warranty so it worked out fine for me. Unfortunately for you you are most likely not going to be able to fix it even from wiping it. I had the same problem and because I had an unlocked bootloader I was able to do much more than you could with flashing stock images. If you can't enter recovery then you most likely have a brick and can't fix it. I'm not sure if there is a way via adb and fastboot commands with a locked bootloader to retrieve data but I'll let you know ow if I find one. What kind of data do you have? Google usually syncs things like your photos and apps downloaded will be saved in the google play store. I hope this helped?
Click to expand...
Click to collapse
Yeah I've tried countless things but it all comes down to me not being able to access recovery. Please do let me know if you do find one thanks . I have some very important docs as well as images in it that I need it badly . I disabled that sync feature as it took very long (for me) to back up all the media. Guess it was a big mistake ....

Enthusiast09 said:
Yeah I've tried countless things but it all comes down to me not being able to access recovery. Please do let me know if you do find one thanks . I have some very important docs as well as images in it that I need it badly . I disabled that sync feature as it took very long (for me) to back up all the media. Guess it was a big mistake ....
Click to expand...
Click to collapse
If you had USB debugging enabled then try this
https://forum.xda-developers.com/nexus-4/general/guide-making-backups-adb-t2411965

DEVILOPS 007 said:
If you had USB debugging enabled then try this
https://forum.xda-developers.com/nexus-4/general/guide-making-backups-adb-t2411965
Click to expand...
Click to collapse
I don't , its off by default ? I took a look at that page and tried it , when I fastboot devices , it can detect , but when I adb devices the list is empty .

I'm experiencing boot loop also. It won't boot into recovery. Only bootloader. I'm completely stumped.
Enthusiast09 said:
Hi there.
So I'm using N6P for a year now and updated to 7.1.2 is I'm not mistaken . My N6P is fully stock with locked bootloader , no tweaking etc.
Was casually browsing through my phone suddenly it restarted and into went into a bootloop. I can only access the bootloader. I have tried going into recovery mode which just starts the loop over again.
I have researched just about everything and tried a lot . I just cant seem to get it working .
I really want my personal data on it , its quite important . If there isn't any more choice, then I will be forced to wipe it but until then any suggestions? Please help , thanks .
By the way , my warranty just expired a week ago so luck is surely not on my side .
Click to expand...
Click to collapse

Bootloop here too
Just tried to upgrade 7.1.1 (unlocked usb debugging enabled) to 7.1.2 using Skipsoft Toolkit. Upon reboot, it just keeps going thru the graphic animation. When I connect it it says 7.1.1 detected.
I am going to try again to upgrade it. Seems like it's working. problem is it says detected system is 6.0.1 now.
Hey, it also says it takes a while for the first boot, so I may have gotten all 21st century and impatient on it.
I also tried a factory reset after freaking out that I had laid a brick...
At least with the skipsoft toolkit I was able to communicate with it!
Here's hoping!
---------- Post added at 04:51 AM ---------- Previous post was at 03:56 AM ----------
Well, although I can get to twrp, I am unable to do anything else. I can't find any clues that are up to date and it's a bummer

Didn't need to be a TWRP expert; just booted into recovery mode, selected the latest factory stock image and flashed it. back to a working nexus 6p and all i gotta do is re-root it, edit the build.prop to enable wifi hotspot (I'm on ATT) and all is groovy. Muchos props to mark and skipsoft toolkit!

Yesterday I also got a bootloop. My smartphone hovered and went into reboot. So it did not boot. It reboots. In the recovery he does not go.

Same here but with stock recovery
I am in the same exact situation. No root, everything stock and warranty expired a week ago. Coincidence..?
I have been able to enter the stock Recovery Mode, but from there I can't execute adb commands, only list devices and sideload..
is there anything else i could do from Recovery Mode ?
Thanks

morelo said:
I am in the same exact situation. No root, everything stock and warranty expired a week ago. Coincidence..?
I have been able to enter the stock Recovery Mode, but from there I can't execute adb commands, only list devices and sideload..
is there anything else i could do from Recovery Mode ?
Click to expand...
Click to collapse
Yes. If you haven't wiped/factory reset yet, you can load a newer OTA image from Recovery. Same or older OTA will not work. Set the device to update from ADB and then send it from PC. If you have wiped the phone, obviously the OTA won't work. This will work with a locked bootloader and no usb debugging enabled.

morelo said:
I am in the same exact situation. No root, everything stock and warranty expired a week ago. Coincidence..?
I have been able to enter the stock Recovery Mode, but from there I can't execute adb commands, only list devices and sideload..
is there anything else i could do from Recovery Mode ?
Thanks
Click to expand...
Click to collapse
You could maybe try this ?
https://www.reddit.com/r/Nexus6P/comments/66wsvq/this_might_sound_absurd_but_i_just_fixed_my_nexus/

Please try this if you need to boot it and get your files off the phone, it worked for me and I was able to backup my pictures.
https://www.reddit.com/r/Nexus6P/comments/66wsvq/this_might_sound_absurd_but_i_just_fixed_my_nexus/

Nokia 6.1 Plus wont boot or load or anything

My nokia 6.1 plus wont boot or load, it just goes to the android 1 screen then shows the battery life when off. I made this you tube video to show all of the struggles ive had. Any help is appreciated.
Attachments area
Preview YouTube video Nokia 6.1 plus wont boot or load

barrnunn said:
My nokia 6.1 plus wont boot or load, it just goes to the android 1 screen then shows the battery life when off. I made this you tube video to show all of the struggles ive had. Any help is appreciated.
Attachments area
Preview YouTube video Nokia 6.1 plus wont boot or load
https://youtu.be/OiGgNE34Ks4
Attachments area
Preview YouTube video Nokia 6.1 plus wont boot or load
Click to expand...
Click to collapse
here is the linkn
https://youtu.be/OiGgNE34Ks4

Nokia 6.1 Plus
barrnunn said:
here is the linkn
https://youtu.be/OiGgNE34Ks4
Click to expand...
Click to collapse
Hi, is this phone just stock Android?
Have you unlocked the Bootloader? Or done anything ( mods) etc???
Did this phone work at some stage? when did it start to not boot?
Have you updated to Pie?
Have you tried to get into fastboot - https://www.hardreset.info/devices/nokia/nokia-61-plus/fastboot-mode/
We need more information.... Mabybe able to help...

And should be posted over in the Question and Answer Thread.. ?

Your device is safe . Just go to nearest care point tell them software gone and tell them to reflash the software using ost

slysurfer said:
Hi, is this phone just stock Android?
Have you unlocked the Bootloader? Or done anything ( mods) etc???
Did this phone work at some stage? when did it start to not boot?
Have you updated to Pie?
Have you tried to get into fastboot - https://www.hardreset.info/devices/nokia/nokia-61-plus/fastboot-mode/
We need more information.... Mabybe able to help...
Click to expand...
Click to collapse
Not sure on these questions. I believe it is stock. I bought it from an acquaintance that said he was just upgrading. He showed me it working. I got it a week later and its doing this. Trying to see if its fixable before addressing him. I believe it was stock and with oreo. I just know he was saying its the new android 1 and for 2 years of updates.

lilbrat said:
And should be posted over in the Question and Answer Thread.. ?
Click to expand...
Click to collapse
Ok, I wasnt sure since i need recovery help. Can a moderator move it?

Raghu varma said:
Your device is safe . Just go to nearest care point tell them software gone and tell them to reflash the software using ost
Click to expand...
Click to collapse
Thank you for the reply and hope you have given. I am in texas and travel alot for work so what i care point? Is that simply a tech company or do I need to go to them specifically? Will any others be able to do it? Is it something I can do from the nokia site?

barrnunn said:
Thank you for the reply and hope you have given. I am in texas and travel alot for work so what i care point? Is that simply a tech company or do I need to go to them specifically? Will any others be able to do it? Is it something I can do from the nokia site?
Click to expand...
Click to collapse
Google ...Nokia care centre...and find nearest representative.

Wrong place !!!

X1111 said:
Wrong place !!!
Click to expand...
Click to collapse
I get it! what can I do about it? create a duplicate over there? or wait for a moderator to move it?

slysurfer said:
Google ...Nokia care centre...and find nearest representative.
Click to expand...
Click to collapse
I googled and spoke to nokia. there are no help centers in the usa. does anyone have directions or links to reflash it myself? I saw after googling that they released a fix for the 7.1 plus that was bricking due to the update.

Unbrick Nokia 6.1 plus
barrnunn said:
I googled and spoke to nokia. there are no help centers in the usa. does anyone have directions or links to reflash it myself? I saw after googling that they released a fix for the 7.1 plus that was bricking due to the update.
Click to expand...
Click to collapse
Hi, you'll need to unlock the Bootloader first, which is not possible ( i think ) as Nokia does not allow this as yet, for most devices. On my 6.1 OEM unlocking is greyed out and Nokia just said stay tuned when I asked to get an unlock key. Can you get into Fastboot mode - hold Vol down and power ( while you have a usb connected to power / pc )??
https://www.hardreset.info/devices/nokia/nokia-61-plus/fastboot-mode/
It might be worth trying a factory reset FIRST, which could work.. follow this - https://www.hardreset.info/devices/nokia/nokia-61-plus/recovery-mode/
Let me know how you go

slysurfer said:
Hi, you'll need to unlock the Bootloader first, which is not possible ( i think ) as Nokia does not allow this as yet, for most devices. On my 6.1 OEM unlocking is greyed out and Nokia just said stay tuned when I asked to get an unlock key. Can you get into Fastboot mode - hold Vol down and power ( while you have a usb connected to power / pc )??
https://www.hardreset.info/devices/nokia/nokia-61-plus/fastboot-mode/
It might be worth trying a factory reset FIRST, which could work.. follow this - https://www.hardreset.info/devices/nokia/nokia-61-plus/recovery-mode/
Let me know how you go
Click to expand...
Click to collapse
I tried all of this in the youtube video I posted. is like it doesnt have a boot loader information on it. It seems as thought there is zero software in there excpept for the android one screen and the amount of battery life when its off. When not plugged in I get absolutely zero response from the phone, even though its 100% charged. Is there a way I can put something on a memory card and try to access it from there into boot mode, or maybe use some software to access the phones internals to install through a computer usb?

Lost
barrnunn said:
I tried all of this in the youtube video I posted. is like it doesnt have a boot loader information on it. It seems as thought there is zero software in there excpept for the android one screen and the amount of battery life when its off. When not plugged in I get absolutely zero response from the phone, even though its 100% charged. Is there a way I can put something on a memory card and try to access it from there into boot mode, or maybe use some software to access the phones internals to install through a computer usb?
Click to expand...
Click to collapse
Sorry I missed that, I thought you had to be doing something wrong. I've never been in this sort position & I've been flashing phones for years,anyway, I'm a bit lost as to what to do next. Without a care centre to help, i can not find any other way to get that phone to boot. As every method I know and have read about, requires an unlocked bootloader and or getting into download mode or the recovery. The Nokia online service tool (ost), requires an unlocked bootloader to flash firmware. Also if the PC does not recognise the phone is another issue.
I will keep looking into how to correct this issue & if I find anything, I'll let you know.

This maybe worth reading, as it may hold a solution
barrnunn said:
I tried all of this in the youtube video I posted. is like it doesnt have a boot loader information on it. It seems as thought there is zero software in there excpept for the android one screen and the amount of battery life when its off. When not plugged in I get absolutely zero response from the phone, even though its 100% charged. Is there a way I can put something on a memory card and try to access it from there into boot mode, or maybe use some software to access the phones internals to install through a computer usb?
Click to expand...
Click to collapse
I've doing some reading... https://www.getdroidtips.com/nokia-6-1-plus-stock-firmware/
and https://www.youtube.com/watch?v=DR5-x5iAEls
https://www.techmesto.com/download-nokia-online-service-tool-6-0-4-for-all-phones/
I know its not related to your device specifically, though its interesting. If we can get official OST LA software and someone's log in details, we can flash firmware to Nokia's with locked bootloaders... I'll be back in touch soon.

slysurfer said:
I've doing some reading... https://www.getdroidtips.com/nokia-6-1-plus-stock-firmware/
and https://www.youtube.com/watch?v=DR5-x5iAEls
https://www.techmesto.com/download-nokia-online-service-tool-6-0-4-for-all-phones/
I know its not related to your device specifically, though its interesting. If we can get official OST LA software and someone's log in details, we can flash firmware to Nokia's with locked bootloaders... I'll be back in touch soon.
Click to expand...
Click to collapse
Great! I have hope once again! Why doesnt this apply to my phone? They all reference the nokia x6 or 6.1 plus. I will attempt these steps and see if any success or change occurs while awaiting your response.

Fix Nokia 6.1 Plus
barrnunn said:
Great! I have hope once again! Why doesnt this apply to my phone? They all reference the nokia x6 or 6.1 plus. I will attempt these steps and see if any success or change occurs while awaiting your response.
Click to expand...
Click to collapse
I also found this tool, to flash firmware ( .nbo files ) - https://androidmtk.com/use-sut-l3-tool going to have a look for some firmware for you.
This is one option - https://forum.xda-developers.com/nokia-6-2018/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657
I thought i shared a link about other models, with the same issue ( soft brick ). I was wrong.
---------- Post added at 07:05 AM ---------- Previous post was at 06:06 AM ----------
slysurfer said:
I also found this tool, to flash firmware ( .nbo files ) - https://androidmtk.com/use-sut-l3-tool going to have a look for some firmware for you.
This is one option - https://forum.xda-developers.com/nokia-6-2018/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657
I thought i shared a link about other models, with the same issue ( soft brick ). I was wrong.
Click to expand...
Click to collapse
I have been reading, others are reporting, getting into recovery mode can be difficult.
When phone is on connect with USB cable to PC. Turn phone off, immediately press volume up button after this. Wait for the little Android to appear. Press power + volume down to access the recovery menu. -> this might take a few tries cause you have to be really precise, but this was the same on my Nexus 5X.
When you have time and patience, could you try to get into recovery again.

slysurfer said:
I also found this tool, to flash firmware ( .nbo files ) - https://androidmtk.com/use-sut-l3-tool going to have a look for some firmware for you.
This is one option - https://forum.xda-developers.com/nokia-6-2018/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657
I thought i shared a link about other models, with the same issue ( soft brick ). I was wrong.
---------- Post added at 07:05 AM ---------- Previous post was at 06:06 AM ----------
I have been reading, others are reporting, getting into recovery mode can be difficult.
When phone is on connect with USB cable to PC. Turn phone off, immediately press volume up button after this. Wait for the little Android to appear. Press power + volume down to access the recovery menu. -> this might take a few tries cause you have to be really precise, but this was the same on my Nexus 5X.
When you have time and patience, could you try to get into recovery again.
Click to expand...
Click to collapse
I got the ost installed but I either dont have proper firmware or the phone is that bricked that it will not accept any boot. The image shows the result I get.

Does anyone have any or know of any functional firmware for this phone?

[RE-OPENED] Possibly Bricked My Phone. AGAIN.

Edit: My phone is miraculously recovered, see last post for details. Big thanks to everyone throwing in suggestions! :highfive::good:
Edit 2: Here we go again... Had my phone set up for a day and after installing the "App Systemizer" Magisk module, the restart upon booting is back. Please help, is magisk causing this??
So, I'm reaching out because I'm now at a loss. I have no other ideas as to how I could fix my phone.
Background:
A few days ago, I was setting my alarm for work in the morning and I noticed the UI was extremely sluggish. I then locked my phone with the lock button and a notification saying "Powering down..." came up and proceeded to shut off. At this point, I knew I should re-flash my ROM/boot.img first. Didn't help, every boot up ended in the same "Powering down..." message and shutting down within 15 seconds of unlocking the device. At this point, I think to fully wipe and revert to stock. Now, I try to install the latest stock OOS via fastboot. Same result as before when I booted after the fastboot install. And this is where it ended... I tried to use the MSM tool and the device went BLACK with no response after that.
What I've tried:
- fastboot
-MSM Tool
- randomly pressing/holding all physical buttons in every order
- leaving the device plugged in to charge overnight
Conclusion:
Any suggestions other than what I've tried would greatly be appreciated. If, by some chance, my phone is truly bricked... would anyone know about whether T-Mobile would replace the device for me if I act clueless as to what happened to my device? lol, I'm on the Jump! plan, so this phone isn't even paid off yet.
Thanks!

Only time I saw this "powering down" issue was when I updated my phone without disabling my Magisk modules. That time I just removed the module using TWRP and the phone booted.
When you used the MSM tool did it complete successfully? It should take around 5 minutes to restore. Mine took 302 seconds on the dot. That should clear out any and all software issues. If the problem still persists after a successful MSM restore then my thoughts would be hardware damage.

I assume your battery is still working (?), and you can't reach TWRP either?
Have you tried this https://www.getdroidtips.com/oneplus-6t-black-screen-death-issue/ ?

When my 6T didn't respond at all. It would stay black no matter what but I knew it was charged. All I did was hold volume up and the power button for a good 15 to 30 seconds. Then it booted up
Sent from my [device_name] using XDA-Developers Legacy app

Car Transport in mumbai
Car Transport In Mumbai[/URL]

Hey u...I also had the same issue...SHUTTING DOWN...in every boot....and I had fixed it....anyways if u have fixed it ...m glad....if not whatsapp or telegram me on +918898340211

Jager said:
Only time I saw this "powering down" issue was when I updated my phone without disabling my Magisk modules. That time I just removed the module using TWRP and the phone booted.
When you used the MSM tool did it complete successfully? It should take around 5 minutes to restore. Mine took 302 seconds on the dot. That should clear out any and all software issues. If the problem still persists after a successful MSM restore then my thoughts would be hardware damage.
Click to expand...
Click to collapse
MSM didn't even pick up my device... it said something along the lines of "No communication"
F5:ed said:
I assume your battery is still working (?), and you can't reach TWRP either?
Have you tried this https://www.getdroidtips.com/oneplus-6t-black-screen-death-issue/ ?
Click to expand...
Click to collapse
Thanks for the suggestion! Unfortunately, all steps were tried before seeing this post and didn't help.
i7vSa7vi7y said:
When my 6T didn't respond at all. It would stay black no matter what but I knew it was charged. All I did was hold volume up and the power button for a good 15 to 30 seconds. Then it booted up
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
This is important... but did not help me... initially.
sanjeev7 said:
Hey u...I also had the same issue...SHUTTING DOWN...in every boot....and I had fixed it....anyways if u have fixed it ...m glad....if not whatsapp or telegram me on +918898340211
Click to expand...
Click to collapse
Well boys, she's up and running again!
Here's what happened:
- I left my phone on the stock charger (wall-block and cord) to make sure the battery wasn't just dead. This resulted in nothing, still no response from the device.
- Early in the morning, while getting ready for work, I continued to press all physical buttons in any and every order as well as holding different combinations of the buttons. Nothing.
- Gave up, took it off the charger, and tossed the damned thing to the side. I took my iPhone X to work and hated every minute of it lmao.
- I then get off work and decide to mash the physical buttons in a half fit-of-rage and half last-ditch-effort.. and BOOM! The screen flashes with a screen saying the battery is dead in a few different languages.
(I never plugged a device in to charge so fast... lol)
At this point, I decided to fastboot the latest stock OOS (.13) to both A/B partitions and she's like brand new!!!! I spent the day rooting and reinstalling everything today and I'm honestly relieved. :victory: All of my data is lost... pics of my baby sister after just being born and of my fiance But order has been restored.
tl;dr - My phone is fixed, don't ever underestimate the power of button mashing! :good:

..Cory.. said:
MSM didn't even pick up my device... it said something along the lines of "No communication"
Click to expand...
Click to collapse
I suggest you re-read the thread on the MSM tool. It will always work unless there is physical damage to your device. The reason you got the "No communication" error is because you were not in the Qualcom bootloader mode or whatever, not fastboot and not TWRP, there is a third mode accessible by holding certain buttons while plugging in your phone to the computer, in this mode the screen does not light up or anything. Read the thread, the steps are in there. I guarantee that if you can get the MSM tool to restore your phone everything will be working on it.
I even tested the MSM tool once. I wiped all partitions on the phone including the boot partition. The MSM tool can always fix a Software issue.
Edit: Didn't see that you said it was fixed already. My message here is still valid though. Some day you will have to use the MSM tool so it's a good idea to get familiar with it.

Jager said:
I suggest you re-read the thread on the MSM tool. It will always work unless there is physical damage to your device. The reason you got the "No communication" error is because you were not in the Qualcom bootloader mode or whatever, not fastboot and not TWRP, there is a third mode accessible by holding certain buttons while plugging in your phone to the computer, in this mode the screen does not light up or anything. Read the thread, the steps are in there. I guarantee that if you can get the MSM tool to restore your phone everything will be working on it.
I even tested the MSM tool once. I wiped all partitions on the phone including the boot partition. The MSM tool can always fix a Software issue.
Edit: Didn't see that you said it was fixed already. My message here is still valid though. Some day you will have to use the MSM tool so it's a good idea to get familiar with it.
Click to expand...
Click to collapse
Well, like I said... I couldn't just change modes at will... I was legit stuck with the screen completely off and no response to any physical button being pressed. So as long as switching modes was impossible... so was the MSM tool. I read a F*CK-TON of threads before I posted this, I haven't seen anyone else post about being in my situation of not being able to boot into ANY kind of a mode... at all lol.

Bumping to ask for help again...
I had my phone all set up, stable OOS (.13) on both partitions. I installed the "App Systemizer" Magisk module in order to move an app to the system. When I rebooted after the module installation, the "Phone is rebooting..." message comes up after a few seconds post-boot and go straight to recovery every time.
I'm lost at this point. :/

You'd probably be better off seeking support in the mod thread.

..Cory.. said:
Bumping to ask for help again...
I had my phone all set up, stable OOS (.13) on both partitions. I installed the "App Systemizer" Magisk module in order to move an app to the system. When I rebooted after the module installation, the "Phone is rebooting..." message comes up after a few seconds post-boot and go straight to recovery every time.
I'm lost at this point. :/
Click to expand...
Click to collapse
Go to TWRP
go to file manager
Delete /data/adb/ *all files related to Magisk*
This will work

..Cory.. said:
Bumping to ask for help again...
I had my phone all set up, stable OOS (.13) on both partitions. I installed the "App Systemizer" Magisk module in order to move an app to the system. When I rebooted after the module installation, the "Phone is rebooting..." message comes up after a few seconds post-boot and go straight to recovery every time.
I'm lost at this point. :/
Click to expand...
Click to collapse
I have never read about a really bricked OP6T, there is always a solution (and use MsmDownloadTool if nothing else work....).
Now, when you already have "bricked" your phone once and fixed it, you are asking the community for help again... It's obvious to me that you are fiddling around with your device without any clue, and creates a mess for yourself. Why?
Stay outside what you do not understand, and stick to stock version only in the future.
To try to help you, I suggest you use MsmDownloadTool.

WOOOOOOOW.
So this whole time it was Magisk. I never knew about Magisk Manager for recovery. That thing is a MUST HAVE.
So what happened was the new Magisk update broke a few modules I use daily. After using MM to disable every module one-by-one, I found the culprit.
The thing that always gets me is the A/B partition BS. But I guess Magisk was really the pain in my ass!
Closing thread for good, thanks to everyone giving suggestions!!! :good:

Cablespider said:
You'd probably be better off seeking support in the mod thread.
Click to expand...
Click to collapse
Right, thank you! I just feel as if this section is less intrusive for noob questions haha
sanjeev7 said:
Go to TWRP
go to file manager
Delete /data/adb/ *all files related to Magisk*
This will work
Click to expand...
Click to collapse
Thank you! Used this to clean some of the files up when reinstalling the new stable update.
F5:ed said:
I have never read about a really bricked OP6T, there is always a solution (and use MsmDownloadTool if nothing else work....).
Now, when you already have "bricked" your phone once and fixed it, you are asking the community for help again... It's obvious to me that you are fiddling around with your device without any clue, and creates a mess for yourself. Why?
Stay outside what you do not understand, and stick to stock version only in the future.
To try to help you, I suggest you use MsmDownloadTool.
Click to expand...
Click to collapse
If you don't think I deserve help, move on to another thread! :good: No problems here though; I took advice I found helpful and I fixed my phone :victory:
I'm far from a noob though, this is just my first A/B parition device. I had an iPhone for years and was last active on XDA before Magisk was even released.We all need to brush up on the basics every once in a while, though!

..Cory.. said:
Right, thank you! I just feel as if this section is less intrusive for noob questions haha
Thank you! Used this to clean some of the files up when reinstalling the new stable update.
If you don't think I deserve help, move on to another thread! :good: No problems here though; I took advice I found helpful and I fixed my phone :victory:
I'm far from a noob though, this is just my first A/B parition device. I had an iPhone for years and was last active on XDA before Magisk was even released.We all need to brush up on the basics every once in a while, though!
Click to expand...
Click to collapse
Thank you for the arrogance.
I have already tried to help you (twice, in this your own thread). Your arrogant answer tells me that the iPhone-comfort zone suite you best.
In short: you act as an imbecile (since I have experience of you, and have "discussed" with you, before outside this thread).
So, sell your OP6t and buy an iPhone - problem solved.

F5:ed said:
Thank you for the arrogance.
I have already tried to help you (twice, in this your own thread). Your arrogant answer tells me that the iPhone-comfort zone suite you best.
In short: you act as an imbecile (since I have experience of you, and have "discussed" with you, before outside this thread).
So, sell your OP6t and buy an iPhone - problem solved.
Click to expand...
Click to collapse
That systemize tool is not very stable in my experience. There is two location's of system apps in my experience which is most always only about at least half correct a little less than half the time. Is that if you use something like MiXplorer and move the apk into either system apps or priv apps then reboot it is much easier to do than rely on scripts that may not be setup for the device you are using. It shouldn't take any longer than 25.89 seconds to manually move an app.

..Cory.. said:
WOOOOOOOW.
So this whole time it was Magisk. I never knew about Magisk Manager for recovery. That thing is a MUST HAVE.
So what happened was the new Magisk update broke a few modules I use daily. After using MM to disable every module one-by-one, I found the culprit.
The thing that always gets me is the A/B partition BS. But I guess Magisk was really the pain in my ass!
Closing thread for good, thanks to everyone giving suggestions!!! :good:
Click to expand...
Click to collapse
Download the magisk uninstaller zip , put it on your internal storage
So when magisk modules messing up with your boot
Go to twrp, flash the uninstaller zip , reboot to twrp, reflash magisk and then you're be able to boot again to your rom ..

F5:ed said:
Thank you for the arrogance.
I have already tried to help you (twice, in this your own thread). Your arrogant answer tells me that the iPhone-comfort zone suite you best.
In short: you act as an imbecile (since I have experience of you, and have "discussed" with you, before outside this thread).
So, sell your OP6t and buy an iPhone - problem solved.
Click to expand...
Click to collapse
Sorry, I forgot ur the internet law enforcement. Yes, sir! Please dont shoot! :HandsUp: :ShakingInFear: :Terrified: :NotReally: :WatchOut_InternetBadAss:

Jager said:
I suggest you re-read the thread on the MSM tool. It will always work unless there is physical damage to your device. The reason you got the "No communication" error is because you were not in the Qualcom bootloader mode or whatever, not fastboot and not TWRP, there is a third mode accessible by holding certain buttons while plugging in your phone to the computer, in this mode the screen does not light up or anything. Read the thread, the steps are in there. I guarantee that if you can get the MSM tool to restore your phone everything will be working on it.
I even tested the MSM tool once. I wiped all partitions on the phone including the boot partition. The MSM tool can always fix a Software issue.
Edit: Didn't see that you said it was fixed already. My message here is still valid though. Some day you will have to use the MSM tool so it's a good idea to get familiar with it.
Click to expand...
Click to collapse
The MSM Tool does not fix everything. The 6T I have is brand new was working fine until I installed LOS on A & B and deleted the persist partition. I have flashed the original stock rom as well as 3 other OOS roms. MSM Tool completes the flash no problem with no errors, but on every rom it only makes it to the boot screen and hangs. If the MSM Tool is supposed to fix this, then why isn't it getting fixed? I don't know what else to try to fix? Usually it fixes most problems for me, but on this occasion it is not.