Related
I know this topic is not popular and most people may skip over it but please read. I am NO expert when it comes to this so if anybody can help out it would be most appreciated. I have a T-mobile My touch 4g( NOT the slide version) running ginger bread 2.3.4. I wanted to play a game called "Clash of clans" but it says i need firmware 4.1 or higher. I was bummed because T mobile stopped making upgrades for this phone a long time ago. I saw online from different threads and videos that I need to downgrade the firmware and go back to fre3vo 2.2. OK i'm fine with that. I had no Idea how adb worked so I saw a post on xda this site how to use it for dummies. I now know how to. I followed ALL steps from http://forum.xda-developers.com/showthread.php?t=1178912 on how I should go about this process. Everything went smooth up until the "Downgrading steps." I finally learned how to place the zip file named "PD15IMG.zip" in the root of sd card. Ok i had it. I also followed the manual downgrade routine. The phone went into boot-loader mode. The phone scanned the file and that took maybe 2 min before it asked me to update. I hit yes to update. I waited for the phone to update then it shut off. I guess the phone restarted to a black screen. The only thing I could see was the top portion bar where the battery and time info is. The rest of the screen was completely black. I took the battery out thinking that maybe the phone just needed to be restarted and this was the worst thing to happen. I turned the phone on and now the screen will NOT boot past the "t mobile mytouch 4g logo screen. I have no idea what to do from here. I went to go back to clockworkmod to see if i could repeat the process. The package scans like before then it asks me to update then I said yes. This is where the phone says its "updating" in pink letter on the side but NO progress is being made. Nothing happens and the phone seems unresponsive. I took the battery out and went back to clockworkmod. I tried to hit 'Factory Reset' but it just stays highlighted on factory reset and it wont move up and down. Nothing works. I took the battery out and re tried clockworkmod. I tried hitting recovery and then a "phone with a "green arrow" below shows up then the screen goes black and the phone vibrates 7 times then nothing else happens. I can no longer access the phone on my computer. Normally when I plugged it in the F: drive folder came up indicating I could change contents in the Sd card. I heard that you can change the setting using terminal and when i try typing "adb shell" it said it cannot find my phone and that my phone inst connected although it is connected to my computer. I have windows 7 Toshiba satellite so nothing is bad on the PC. Battery, cable, everything is fine no defects with the phone.
Also
A little information when ClockWorkMod is up. This is exactly what it says and this is exactly the color as it shows.
GLACIER PUT SHIP S-ON
HBOOT-0.89.0005
MICROP-0429
RADIO-26.11.04.03_M
eMMC-boot
Apr 14 2011, 13;18;22
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Since I can no longer access the phone on my pc I took the micro sim sd out and placed it in my samsung galaxy player 3.6 From there I can at least change what goes into the Sd card. I have searched countless hours and nothing else comes up. I CANNOT go back to the normal mode my phone used to be. I just freezes past mytouch4g screen. Please help anybody. I want to downgrade ginger bread 2.3.4 to fre3vo 2.2 so i can root and upgrade to jelly bean or something higher to play clash of clans since this phone wasn't compatable. Please somebody help. Can I ever use my phone again? Does this mean it's bricked? I'm an apple user so I have little experience with android. Somebody anybody help me out?
Here are a few links i used in the process
http://lifehacker.com/5853519/how-do-i-fix-my-bricked-android-phone
http://forum.xda-developers.com/showthread.php?t=863899
help me please
Bolt34 said:
I know this topic is not popular and most people may skip over it but please read. I am NO expert when it comes to this so if anybody can help out it would be most appreciated. I have a T-mobile My touch 4g( NOT the slide version) running ginger bread 2.3.4. I wanted to play a game called "Clash of clans" but it says i need firmware 4.1 or higher. I was bummed because T mobile stopped making upgrades for this phone a long time ago. I saw online from different threads and videos that I need to downgrade the firmware and go back to fre3vo 2.2. OK i'm fine with that. I had no Idea how adb worked so I saw a post on xda this site how to use it for dummies. I now know how to. I followed ALL steps from http://forum.xda-developers.com/showthread.php?t=1178912 on how I should go about this process. Everything went smooth up until the "Downgrading steps." I finally learned how to place the zip file named "PD15IMG.zip" in the root of sd card. Ok i had it. I also followed the manual downgrade routine. The phone went into boot-loader mode. The phone scanned the file and that took maybe 2 min before it asked me to update. I hit yes to update. I waited for the phone to update then it shut off. I guess the phone restarted to a black screen. The only thing I could see was the top portion bar where the battery and time info is. The rest of the screen was completely black. I took the battery out thinking that maybe the phone just needed to be restarted and this was the worst thing to happen. I turned the phone on and now the screen will NOT boot past the "t mobile mytouch 4g logo screen. I have no idea what to do from here. I went to go back to clockworkmod to see if i could repeat the process. The package scans like before then it asks me to update then I said yes. This is where the phone says its "updating" in pink letter on the side but NO progress is being made. Nothing happens and the phone seems unresponsive. I took the battery out and went back to clockworkmod. I tried to hit 'Factory Reset' but it just stays highlighted on factory reset and it wont move up and down. Nothing works. I took the battery out and re tried clockworkmod. I tried hitting recovery and then a "phone with a "green arrow" below shows up then the screen goes black and the phone vibrates 7 times then nothing else happens. I can no longer access the phone on my computer. Normally when I plugged it in the F: drive folder came up indicating I could change contents in the Sd card. I heard that you can change the setting using terminal and when i try typing "adb shell" it said it cannot find my phone and that my phone inst connected although it is connected to my computer. I have windows 7 Toshiba satellite so nothing is bad on the PC. Battery, cable, everything is fine no defects with the phone.
Also
A little information when ClockWorkMod is up. This is exactly what it says and this is exactly the color as it shows.
GLACIER PUT SHIP S-ON
HBOOT-0.89.0005
MICROP-0429
RADIO-26.11.04.03_M
eMMC-boot
Apr 14 2011, 13;18;22
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Since I can no longer access the phone on my pc I took the micro sim sd out and placed it in my samsung galaxy player 3.6 From there I can at least change what goes into the Sd card. I have searched countless hours and nothing else comes up. I CANNOT go back to the normal mode my phone used to be. I just freezes past mytouch4g screen. Please help anybody. I want to downgrade ginger bread 2.3.4 to fre3vo 2.2 so i can root and upgrade to jelly bean or something higher to play clash of clans since this phone wasn't compatable. Please somebody help. Can I ever use my phone again? Does this mean it's bricked? I'm an apple user so I have little experience with android. Somebody anybody help me out?
Here are a few links i used in the process
http://lifehacker.com/5853519/how-do-i-fix-my-bricked-android-phone
http://forum.xda-developers.com/showthread.php?t=863899
help me please
Click to expand...
Click to collapse
Bro calm down. I've been though panic attacks like this too lol
Open clockworkmod
To select or scroll use the TRACKPAD
Put a rom on your sdcard, find any in the resource bible in the development section
Do a factory reset and flash that rom
And yay,
N_otori0us_ said:
Bro calm down. I've been though panic attacks like this too lol
Open clockworkmod
To select or scroll use the TRACKPAD
Put a rom on your sdcard, find any in the resource bible in the development section
Do a factory reset and flash that rom
And yay,
Click to expand...
Click to collapse
-It won't allow me to use the track pad I can only use the volume up and down buttons to scroll. What rom should I put on my sd card? If you have a link or something that would be great.. Also when I try to factory reset the phone just freezes. I don't know what to do.
any rom
That screen you posted information from is called H-BOOT, it's like the factory boot loader. Clockwork MOD will show up after that but from what I'm gathering you didn't even install that in the first place. In H-BOOT you can only use the volume buttons and the power button to select so that is all normal.
So you downloaded the stock ROM and in the process of downgrading got stuck. If the SD card still works in other devices do you still have PD15IMG.zip on the card?
Also did you make sure to download the proper drivers for ADB and also for your phone? The ADB ones you should be able to find on this forum and the HTC ones you could get directly from you carriers website, and most likely somewhere on this forum. It will be up to you to really read, read, read, but I don't mind point you in the right direction.
You will find links of information with in this post http://forum.xda-developers.com/showthread.php?t=2288189
I would read through s-off / s-on and true rooting. I feel like you're missing drivers and basically just have nothing installed on the phone. So you aren't bricked, you just need to do more research. Bricked is the phone shows no screen at all and won't even turn on. I've done it once, and you are luckily not there. I believe the first time I rooted this phone I had the same problem of "is it installing...did I miss something...eff it, battery pull...oh no!"
Also select the recovery option and let me know what happens, if it advances you to the next screen that is what is actually Clockwork Mod recovery. If you actually have that then we are even better. I'll keep checking back tonight for ya.
tonyMEGAphone said:
That screen you posted information from is called H-BOOT, it's like the factory boot loader. Clockwork MOD will show up after that but from what I'm gathering you didn't even install that in the first place. In H-BOOT you can only use the volume buttons and the power button to select so that is all normal.
So you downloaded the stock ROM and in the process of downgrading got stuck. If the SD card still works in other devices do you still have PD15IMG.zip on the card?
Also did you make sure to download the proper drivers for ADB and also for your phone? The ADB ones you should be able to find on this forum and the HTC ones you could get directly from you carriers website, and most likely somewhere on this forum. It will be up to you to really read, read, read, but I don't mind point you in the right direction.
You will find links of information with in this post http://forum.xda-developers.com/showthread.php?t=2288189
I would read through s-off / s-on and true rooting. I feel like you're missing drivers and basically just have nothing installed on the phone. So you aren't bricked, you just need to do more research. Bricked is the phone shows no screen at all and won't even turn on. I've done it once, and you are luckily not there. I believe the first time I rooted this phone I had the same problem of "is it installing...did I miss something...eff it, battery pull...oh no!"
Also select the recovery option and let me know what happens, if it advances you to the next screen that is what is actually Clockwork Mod recovery. If you actually have that then we are even better. I'll keep checking back tonight for ya.
Click to expand...
Click to collapse
I appreciate the comment and help. Sorry i didn't know that I wasnt in colckworkmod just yet. Im new to android as I am an apple person. Some of the links i've found on this site are outdated or used by sites that are no longer running. If possible could you help direct me to the appropriate link so that I can download the correct rom? thank you so much!
first
First in your Hboot screen scroll with the volume button to "Recovery" and let me know what happens.
---------- Post added at 04:36 PM ---------- Previous post was at 04:29 PM ----------
Also did you go to tmobile and install the HTC drivers under the support menu for your phone?
These are all must I read through your post and also am currently reading the link you said you followed but if you didn't do all these prerequisite work it's no wonder why you froze up.
---------- Post added at 04:52 PM ---------- Previous post was at 04:36 PM ----------
I see, you said the Recovery goes black and vibrates 7 times. Something didn't install right. At this stage of working with your phone you won't see the F: drive pop up until we fully get you downgraded and get the ROM operational.
See what you can do with this link. Follow it and even redownload items from it. It's more updated then the one you used.
http://forum.xda-developers.com/showthread.php?t=928370
And let me know how it goes, and if I helped click the little thanks button~ like i said before I'll have time tonight to go back and forth and try and make this work. You just need to read your face off. HTC's can be tricky but at least it's not MOTOROLA...
---------- Post added at 05:11 PM ---------- Previous post was at 04:52 PM ----------
Found another thread too
http://forum.xda-developers.com/showthread.php?t=1538859&page=6
Page 4 has a link to some PD15IMG.zip files that could work, Page 5 has someone confirming which one works and then Page 6 this guy posts a video on how he fixed his.
Also make sure the phone is charged a low battery can cause boot loops, try and format the SD card and only have PD15IMG.zip be the only file.
lol I missed the fact that he's still in bootloader.
Bro just try flashing that stock img again
tonyMEGAphone said:
First in your Hboot screen scroll with the volume button to "Recovery" and let me know what happens.
---------- Post added at 04:36 PM ---------- Previous post was at 04:29 PM ----------
Also did you go to tmobile and install the HTC drivers under the support menu for your phone?
These are all must I read through your post and also am currently reading the link you said you followed but if you didn't do all these prerequisite work it's no wonder why you froze up.
---------- Post added at 04:52 PM ---------- Previous post was at 04:36 PM ----------
I see, you said the Recovery goes black and vibrates 7 times. Something didn't install right. At this stage of working with your phone you won't see the F: drive pop up until we fully get you downgraded and get the ROM operational.
See what you can do with this link. Follow it and even redownload items from it. It's more updated then the one you used.
http://forum.xda-developers.com/showthread.php?t=928370
And let me know how it goes, and if I helped click the little thanks button~ like i said before I'll have time tonight to go back and forth and try and make this work. You just need to read your face off. HTC's can be tricky but at least it's not MOTOROLA...
---------- Post added at 05:11 PM ---------- Previous post was at 04:52 PM ----------
Found another thread too
http://forum.xda-developers.com/showthread.php?t=1538859&page=6
Page 4 has a link to some PD15IMG.zip files that could work, Page 5 has someone confirming which one works and then Page 6 this guy posts a video on how he fixed his.
Also make sure the phone is charged a low battery can cause boot loops, try and format the SD card and only have PD15IMG.zip be the only file.
Click to expand...
Click to collapse
Ok Im going to try this now. Just hold on in there for me.
Lets see if this works
tonyMEGAphone said:
First in your Hboot screen scroll with the volume button to "Recovery" and let me know what happens.
---------- Post added at 04:36 PM ---------- Previous post was at 04:29 PM ----------
Also did you go to tmobile and install the HTC drivers under the support menu for your phone?
These are all must I read through your post and also am currently reading the link you said you followed but if you didn't do all these prerequisite work it's no wonder why you froze up.
---------- Post added at 04:52 PM ---------- Previous post was at 04:36 PM ----------
I see, you said the Recovery goes black and vibrates 7 times. Something didn't install right. At this stage of working with your phone you won't see the F: drive pop up until we fully get you downgraded and get the ROM operational.
See what you can do with this link. Follow it and even redownload items from it. It's more updated then the one you used.
http://forum.xda-developers.com/showthread.php?t=928370
And let me know how it goes, and if I helped click the little thanks button~ like i said before I'll have time tonight to go back and forth and try and make this work. You just need to read your face off. HTC's can be tricky but at least it's not MOTOROLA...
---------- Post added at 05:11 PM ---------- Previous post was at 04:52 PM ----------
Found another thread too
http://forum.xda-developers.com/showthread.php?t=1538859&page=6
Page 4 has a link to some PD15IMG.zip files that could work, Page 5 has someone confirming which one works and then Page 6 this guy posts a video on how he fixed his.
Also make sure the phone is charged a low battery can cause boot loops, try and format the SD card and only have PD15IMG.zip be the only file.
Click to expand...
Click to collapse
So I found a new img file and the same thing happens. It says it's updating but doesnt make any progess and it looks like its frozen. What should I do?
N_otori0us_ said:
lol I missed the fact that he's still in bootloader.
Bro just try flashing that stock img again
Click to expand...
Click to collapse
tonyMEGAphone said:
First in your Hboot screen scroll with the volume button to "Recovery" and let me know what happens.
---------- Post added at 04:36 PM ---------- Previous post was at 04:29 PM ----------
Also did you go to tmobile and install the HTC drivers under the support menu for your phone?
These are all must I read through your post and also am currently reading the link you said you followed but if you didn't do all these prerequisite work it's no wonder why you froze up.
---------- Post added at 04:52 PM ---------- Previous post was at 04:36 PM ----------
I see, you said the Recovery goes black and vibrates 7 times. Something didn't install right. At this stage of working with your phone you won't see the F: drive pop up until we fully get you downgraded and get the ROM operational.
See what you can do with this link. Follow it and even redownload items from it. It's more updated then the one you used.
http://forum.xda-developers.com/showthread.php?t=928370
And let me know how it goes, and if I helped click the little thanks button~ like i said before I'll have time tonight to go back and forth and try and make this work. You just need to read your face off. HTC's can be tricky but at least it's not MOTOROLA...
---------- Post added at 05:11 PM ---------- Previous post was at 04:52 PM ----------
Found another thread too
http://forum.xda-developers.com/showthread.php?t=1538859&page=6
Page 4 has a link to some PD15IMG.zip files that could work, Page 5 has someone confirming which one works and then Page 6 this guy posts a video on how he fixed his.
Also make sure the phone is charged a low battery can cause boot loops, try and format the SD card and only have PD15IMG.zip be the only file.
Click to expand...
Click to collapse
When I went to recovery mode..it went to a black screen with like a green symbol and box. Then the entire screen went blank and I noticed the phone vibrated "7" times. What should I do?
Bolt34 said:
When I went to recovery mode..it went to a black screen with like a green symbol and box. Then the entire screen went blank and I noticed the phone vibrated "7" times. What should I do?
Click to expand...
Click to collapse
7 vibrates of death.
Dun dun daaaaaa.
That's a brick. I think.
Sent from my HTC Glacier
N_otori0us_ said:
7 vibrates of death.
Dun dun daaaaaa.
That's a brick. I think.
Sent from my HTC Glacier
Click to expand...
Click to collapse
So in other words...I can't fix the phone then?
N_otori0us_ said:
7 vibrates of death.
Dun dun daaaaaa.
That's a brick. I think.
Sent from my HTC Glacier
Click to expand...
Click to collapse
Couldn't that just be due to a low battery also?
---------- Post added at 05:08 PM ---------- Previous post was at 05:00 PM ----------
These people couldn't even get into the Bootloader. That's why I believe there is slightly still hope for you.
http://forum.xda-developers.com/showthread.php?t=2188591
tonyMEGAphone said:
Couldn't that just be due to a low battery also?
---------- Post added at 05:08 PM ---------- Previous post was at 05:00 PM ----------
These people couldn't even get into the Bootloader. That's why I believe there is slightly still hope for you.
http://forum.xda-developers.com/showthread.php?t=2188591
Click to expand...
Click to collapse
I made sure the phone was fully charged and I had it plugged in. That couldn't be it.
last
Bolt34 said:
I made sure the phone was fully charged and I had it plugged in. That couldn't be it.
Click to expand...
Click to collapse
My last thread attempt, and if this doesn't work. I'd say check out Craigslist for a new phone. My Glacier 4G antenna, the actual hardware, I believe is shot. So I'm going to have to down grade and run through a similar process so I can send it back for a replacement. These things can get tricky so I feel your bricked pain. I've bricked a Motorola Atrix before.
http://forum.xda-developers.com/showthread.php?t=2329869
If none of this works. It's time to put it in a shoe box and bury it in the back yard.
Hey all! My Nexus 6P that has been on N Preview since day 2 is now stuck in a boot loop. It will usually just display the Google logo and then reboot. Sometimes it will get to the very beginning of the Android boot animation, but rarely.
Unfortunately, I didn't even know about the OEM Unucking setting until I've been trying to get my phone to boot again. I've tried using clearing cache, factory restore, adb sideload, and the flashing instructions Google provides. I've also tried using SkipSoft Android ToolKit with no avail as well. At this point I don't care if I end up with Marshmallow or back on N. I just want my phone working again xP
Does anyone have any ideas on how to restore my phone back to a working state? Thanks!
It also might be good to mention is I'm not all that well versed in a lot of the android development tools. I'm not afraid to get my hands dirty though.
UPDATE (Thanks @NeoAcheron)
While this didn't work for me, this seems to work for some.
NeoAcheron shared the OTA update Google sends out to go from N to Marshmallow. YMMV, so best of luck to you!
If anyone has any other idea's to try, I'd be eternally grateful!
And remember kids, always enable OEM Unlocking like good boys and girls. (Settings -> Developer Options -> OEM Unlocking)
JPT62089 said:
Hey all! My Nexus 6P that has been on N Preview since day 2 is now stuck in a boot loop. It will usually just display the Google logo and then reboot. Sometimes it will get to the very beginning of the Android boot animation, but rarely.
Unfortunately, I didn't even know about the OEM Unucking setting until I've been trying to get my phone to boot again. I've tried using clearing cache, factory restore, adb sideload, and the flashing instructions Google provides. I've also tried using SkipSoft Android ToolKit with no avail as well. At this point I don't care if I end up with Marshmallow or back on N. I just want my phone working again xP
Does anyone have any ideas on how to restore my phone back to a working state? Thanks!
It also might be good to mention is I'm not all that well versed in a lot of the android development tools. I'm not afraid to get my hands dirty though.
Click to expand...
Click to collapse
If you can use fastboot fastboot system that should work out wipe userdata
jaythenut said:
If you can use fastboot fastboot system that should work out wipe userdata
Click to expand...
Click to collapse
Unfortunately, that didn't seem to work
Code:
> fastboot format userdata
Creating filesystem with parameters:
Size: 58688266240
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14328190
Block groups: 438
Reserved block group size: 1024
Created filesystem with 11/3588096 inodes and 271280/14328190 blocks
target reported max download size of 494927872 bytes
erasing 'userdata'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.013s
From the bootloader page on the phone...
Code:
Console: NULL
Battery OK
Device is LOCKED
Qfuse Status: ENABLED
Off-mode-charge: ENABLED
Download Mode: DISABLED.
Also worth a note...
Code:
> fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.005s
format from stock recovery ?
@JPT62089 You are not alone. My Nexus 6P is experiencing the same problem now. Signed up for the Dev Preview, phone behaved strangely today, reboot the device as per usual, and now its stuck on the boot screen...
I have tried applying the preview OTA update, and the Factory firmware reset, with the same results as you.
This is awesome considering I didn't unlock the bootloader, because I would have thought installing stock firmware would be possible.
This sucks... Lets hope Google releases a fix soon.
---------- Post added at 03:02 PM ---------- Previous post was at 03:01 PM ----------
csjneek said:
format from stock recovery ?
Click to expand...
Click to collapse
Unfortunately telling the device to reset to factory doesn't help either. Seems like the latest update broke the OS completely.
Wooohooo! Glad I'm not the only one It's unfortunate to have such a major issue as Preview 3 has been extremely stable for me up until yesterday...
NeoAcheron said:
@JPT62089 You are not alone. My Nexus 6P is experiencing the same problem now. Signed up for the Dev Preview, phone behaved strangely today, reboot the device as per usual, and now its stuck on the boot screen...
I have tried applying the preview OTA update, and the Factory firmware reset, with the same results as you.
This is awesome considering I didn't unlock the bootloader, because I would have thought installing stock firmware would be possible.
This sucks... Lets hope Google releases a fix soon.
---------- Post added at 03:02 PM ---------- Previous post was at 03:01 PM ----------
Unfortunately telling the device to reset to factory doesn't help either. Seems like the latest update broke the OS completely.
Click to expand...
Click to collapse
JPT62089 said:
Wooohooo! Glad I'm not the only one It's unfortunate to have such a major issue as Preview 3 has been extremely stable for me up until yesterday...
Click to expand...
Click to collapse
The Developer Preview was never meant to be signed up by any average user without prior knowledge on Android Development. If you sign up for the beta program, then it's always imperative that you have the bootloader previously unlocked, in case this exact situation happen. Did you actually think that you can just sign up for the Beta program and hope that it will not cause any problems?
ttminh1997 said:
The Developer Preview was never meant to be signed up by any average user without prior knowledge on Android Development. If you sign up for the beta program, then it's always imperative that you have the bootloader previously unlocked, in case this exact situation happen. Did you actually think that you can just sign up for the Beta program and hope that it will not cause any problems?
Click to expand...
Click to collapse
I am a software technical lead, knowing full well what the implications might be of running beta software on any piece of computing equipment. However, not at any point when I signed up was there a statement that I need to unlock the bootloader. Booloader unlocking in my mind (and on previous devices, like the HTC One) was only required when you wanted to deviate from the Stock firmware on the device. This is stock firmware, from Google.
I'm generally quite excited to test new things and I report my findings often with details about my experience and how the software behaved upto that point. But this has left a bad experience and I am not participating in the program anymore due to this.
Coming back now to say "oh you shoulda known" is not constructive. I am interested in a solution, because Google pretty much bricked my device without me touching it. The update (and the beta version since the announcement) applied seamlessly, and was working fine until I rebooted the device today.
---------- Post added at 04:18 PM ---------- Previous post was at 04:09 PM ----------
Found this: https://www.reddit.com/r/Nexus6P/comments/4jzp1o/soft_bricked_nexus_6p_with_locked_bootloader_need/
Might be possible to reproduce the special ZIP file to create a "special" downgrade OTA zip file to unbrick it, just to unlock the bootloader (at the very least).
I will have to look into it later, as I am still at work, and need to tend to some other tasks before getting back to this.
Will keep everyone updated...
NeoAcheron said:
I am a software technical lead, knowing full well what the implications might be of running beta software on any piece of computing equipment. However, not at any point when I signed up was there a statement that I need to unlock the bootloader. Booloader unlocking in my mind (and on previous devices, like the HTC One) was only required when you wanted to deviate from the Stock firmware on the device. This is stock firmware, from Google.
I'm generally quite excited to test new things and I report my findings often with details about my experience and how the software behaved upto that point. But this has left a bad experience and I am not participating in the program anymore due to this.
Coming back now to say "oh you shoulda known" is not constructive. I am interested in a solution, because Google pretty much bricked my device without me touching it. The update (and the beta version since the announcement) applied seamlessly, and was working fine until I rebooted the device today.
Click to expand...
Click to collapse
Bootloader unlocks are extremely important if you want to do any system-level mods (rooting, flashing custom recoveries, rom). Not only does it allow you to deviate from stock firmwares, like you said, but it also opens a gateway in which you can just flash a factory image and resolve any potential problems that may arise from otherwise stock Android or any custom roms you have. And stock firmwares, whether from Google, Samsung or even Apple, don't always mean good, or even stable. They may be stable 99% of the time, but eventually bugs and glitches are bound to happen; that's why they are continually updated, and that's why the 2011 Samsung ICS brick fiasco happened.
I did not mean to insult you or anything in the reply. That being said, yes, you really should have known before venturing into flashing firmwares without unlocking the bootloader and creating a backup first. As for solution, have you recently installed any apps that may not be compatible with N? Can you boot into safemode and disable some apps? If you can actually go into safemode, check allow oem unlock, unlock the bootloader and reflash factory image.
ttminh1997 said:
Bootloader unlocks are extremely important if you want to do any system-level mods (rooting, flashing custom recoveries, rom). Not only does it allow you to deviate from stock firmwares, like you said, but it also opens a gateway in which you can just flash a factory image and resolve any potential problems that may arise from otherwise stock Android or any custom roms you have. And stock firmwares, whether from Google, Samsung or even Apple, don't always mean good, or even stable. They may be stable 99% of the time, but eventually bugs and glitches are bound to happen; that's why they are continually updated, and that's why the 2011 Samsung ICS brick fiasco happened.
I did not mean to insult you or anything in the reply. That being said, yes, you really should have known before venturing into flashing firmwares without unlocking the bootloader and creating a backup first. As for solution, have you recently installed any apps that may not be compatible with N? Can you boot into safemode and disable some apps? If you can actually go into safemode, check allow oem unlock, unlock the bootloader and reflash factory image.
Click to expand...
Click to collapse
No offence taken, but I will make sure to unlock the device once I get it back up. Unfortunately the device doesn't boot at all, I cannot get it into safemode either (using the volume keys during boot).
What I do have though is the thread that is mentioned in the reddit post, I will need to check if this works before unleashing it here...
Will update when any developments made.
---------- Post added at 05:08 PM ---------- Previous post was at 04:46 PM ----------
HEY HEY! It worked!
So you need to get this file: https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
NeoAcheron said:
No offence taken, but I will make sure to unlock the device once I get it back up. Unfortunately the device doesn't boot at all, I cannot get it into safemode either (using the volume keys during boot).
What I do have though is the thread that is mentioned in the reddit post, I will need to check if this works before unleashing it here...
Will update when any developments made.
---------- Post added at 05:08 PM ---------- Previous post was at 04:46 PM ----------
HEY HEY! It worked!
So you need to get this file: https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Click to expand...
Click to collapse
Glad you could make your phone work again. Make sure that you unlock your bootloader before unlocking or testing any new roms.
NeoAcheron said:
No offence taken, but I will make sure to unlock the device once I get it back up. Unfortunately the device doesn't boot at all, I cannot get it into safemode either (using the volume keys during boot).
What I do have though is the thread that is mentioned in the reddit post, I will need to check if this works before unleashing it here...
Will update when any developments made.
---------- Post added at 05:08 PM ---------- Previous post was at 04:46 PM ----------
HEY HEY! It worked!
So you need to get this file: https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Click to expand...
Click to collapse
Did you just flash every .img file? There does not appear to be any other way.
NeoAcheron said:
HEY HEY! It worked!
So you need to get this file: https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Click to expand...
Click to collapse
Thanks for posting this NeoAcheron, I sideloaded this yesterday and was actually able to perform an adb sideload this time (found a handy tip... Once the phone is waiting for adb commands, unplug and plug it back into the computer as it may not already see it)
It didn't seem to immediately help, unfortunately. I let it bootloop for a while before giving up and then tried again last night. I had left it on my desk bootlooping for a while and then all of a sudden it was booted and waiting for me to set it up. I quickly did so and immediate went to settings to enable the OEM Flashing setting and just as I did so it went to the red warning screen and then proceeded to bootloop again... I tried to run fastboot flashing unlock again in hopes that my changing the setting took before it bootlooped, but still got the FAILED message. I've since tried every which way of factory resetting, sideloading again, leaving it for hours in bootloop, and still nothing
Anyone have any more ideas?
Maybe a dumb question...but
ttminh1997 said:
Glad you could make your phone work again. Make sure that you unlock your bootloader before unlocking or testing any new roms.
Click to expand...
Click to collapse
Deleted
---------- Post added at 10:19 PM ---------- Previous post was at 09:59 PM ----------
So you need to get this file: https://android.googleapis.com/packa...cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Can I flash this ( https://android.googleapis.com/packa...cd4f52b800.zip) in TWRP ? I am running N5...I wanted to go back to Marshmallow to be able to flash some roms.
Thanks
NeoAcheron said:
No offence taken, but I will make sure to unlock the device once I get it back up. Unfortunately the device doesn't boot at all, I cannot get it into safemode either (using the volume keys during boot).
What I do have though is the thread that is mentioned in the reddit post, I will need to check if this works before unleashing it here...
Will update when any developments made.
---------- Post added at 05:08 PM ---------- Previous post was at 04:46 PM ----------
HEY HEY! It worked!
So you need to get this file:
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Click to expand...
Click to collapse
Hey NeoAcheron. I'm having a similar issue. After years of flashing custom ROMs, I joined the Beta programme so I could do things 'properly' on my Nexus 6P. Been working fine for a fortnight, until today when it randomly froze, crashed, and is now stuck in a bootloop on the 'Google' screen. I can get into the bootloader menu, but every option I select takes me back to the 'Google' bootloop screen. I can't even get my PC to recognise it as a device so I can't sideload a workaround.
Any ideas, or is it basically useless? Google have offered me a replacement phone, but I'd like to try and rescue this one first
Thanks in advance
kristianj79 said:
Hey NeoAcheron. I'm having a similar issue. After years of flashing custom ROMs, I joined the Beta programme so I could do things 'properly' on my Nexus 6P. Been working fine for a fortnight, until today when it randomly froze, crashed, and is now stuck in a bootloop on the 'Google' screen. I can get into the bootloader menu, but every option I select takes me back to the 'Google' bootloop screen. I can't even get my PC to recognise it as a device so I can't sideload a workaround.
Any ideas, or is it basically useless? Google have offered me a replacement phone, but I'd like to try and rescue this one first
Thanks in advance
Click to expand...
Click to collapse
The first thing you could try wiping cache from the stock recovery, and see if it works. Do you have any data on the device that you desperately wanna save, and can't loose?
DJBhardwaj said:
The first thing you could try wiping cache from the stock recovery, and see if it works. Do you have any data on the device that you desperately wanna save, and can't loose?
Click to expand...
Click to collapse
Thanks DJBhardwaj - I'm all backed up. I just wanted to see if I could fix it myself because I'd rather not be without a decent phone for a week. I'm no expert and I usually need my hand holding, but I've managed to get out of a few scrapes in the past with custom ROMs and bootloops!
My issue is that I can't even access stock recovery. I can get into the fastboot menu using the hardware keys but selecting any ption from there throws the device into a bootloop again. I also can't get my PC to see the device and wrestle beck control using adb commands, so I'm a bit stuck :/
kristianj79 said:
Thanks DJBhardwaj - I'm all backed up. I just wanted to see if I could fix it myself because I'd rather not be without a decent phone for a week. I'm no expert and I usually need my hand holding, but I've managed to get out of a few scrapes in the past with custom ROMs and bootloops!
My issue is that I can't even access stock recovery. I can get into the fastboot menu using the hardware keys but selecting any ption from there throws the device into a bootloop again. I also can't get my PC to see the device and wrestle beck control using adb commands, so I'm a bit stuck :/
Click to expand...
Click to collapse
Have you tried on any other Windows or Mac PC? If you can get it to detect, then the problem would be pretty easily solved. To confirm if your device is being recognized, type in the following command in CMD/Terminal:
Code:
fastboot devices
I need help, my phone went into a Bootloop. I have tried to flash the factory image (7.0 and 6.0.1) using NRT and manually and still does not pass the Google logo. It does not let me enter the recovery, it only restarts continuously. When flashing the factory image did not give me any error, even the computer detects it in fastboot mode.
All this happened when I was about to open an application and suddenly I shut down and began to restart continuously. I had using android 7.0 stock.
Exact thing happened to me and I flashed both 7 and 6.0.1 and wiped data and caches multiple times.. nothing seems to work.. any ideas?
Tried everything but still bootloops.
Same thing here, although I was on a 7.1 build. There must be a flaw that can cause this to happen in recent build(s), I was trying to share a picture and it froze and bricked like this suddenly. I tried every combination of formatting and flashing stock images and whatnot but no luck.
Seanmiz said:
Same thing here, although I was on a 7.1 build. There must be a flaw that can cause this to happen in recent build(s), I was trying to share a picture and it froze and bricked like this suddenly. I tried every combination of formatting and flashing stock images and whatnot but no luck.
Click to expand...
Click to collapse
Your Nexus 6P uses Samsung eMMC doesn't?
I've seen countless threads here and on reddit about this.
My phone hard bricked last week and I suspect the Samsung emmc is to blame, too many people are having the exact same issue without a solution in sight. I am absolutely unable to access the recovery or anything on the emmc for that matter.
See if you're still covered under warranty (mine was 5 days past its warranty, and Google refused to help), otherwise you're SOL. I think we need to make some noise about it and have AP or another site pick up on this.
darksmartz said:
Your Nexus 6P uses Samsung eMMC doesn't?
Click to expand...
Click to collapse
I believe it was Samsung, yes. I RMA'd it right away after exhausting all flashing efforts.
darksmartz said:
Your Nexus 6P uses Samsung eMMC doesn't?
Click to expand...
Click to collapse
How do I know if my 6p uses Samsung eMMC? What is this, btw?
Edit
Nevermind. I just figured out. Mine is Toshiba, btw.
Rafsxd said:
How do I know if my 6p uses Samsung eMMC? What is this, btw?
Edit
Nevermind. I just figured out. Mine is Toshiba, btw.
Click to expand...
Click to collapse
how did you find this out ? would be nice to tell people so they can check to find out if they will be at risk
brichardson1991 said:
how did you find this out ? would be nice to tell people so they can check to find out if they will be at risk
Click to expand...
Click to collapse
You can find this information on the Bootloader screen listed under eMMC about halfway down the list.
Same problem, samsung memory here
Same for me too,i send my phone back to amazon
Envoyé de mon HUAWEI VNS-L31 en utilisant Tapatalk
Mine uses a Toshiba eMMC and bootloops nevertheless. Not sure if this is actually what's causing it. At this point my only thought is that there was a bad batch of devices as so far no one could find a pattern on what exactly causes the bootloops.
seco2004 said:
Mine uses a Toshiba eMMC and bootloops nevertheless. Not sure if this is actually what's causing it. At this point my only thought is that there was a bad batch of devices as so far no one could find a pattern on what exactly causes the bootloops.
Click to expand...
Click to collapse
Yeah, it doesn't actually seem to be related to eMMC brand. It was very strange, because after it happened, I was able to flash 7.0 stock and regain OS use on a very touchy level. I couldn't access USB connectivity, the home button didn't work most of the time, and if I tried to do too much with it, it would go right back into infinite bootloops. After accomplishing this 2 or 3 times, I could never again get back into the OS.
I could wipe and flash all of the partitions with no errors, I could always get into stock recovery, but TWRP never worked.
Was anyone *not* on the November patch level of v7.0+?
Seanmiz said:
Yeah, it doesn't actually seem to be related to eMMC brand. It was very strange, because after it happened, I was able to flash 7.0 stock and regain OS use on a very touchy level. I couldn't access USB connectivity, the home button didn't work most of the time, and if I tried to do too much with it, it would go right back into infinite bootloops. After accomplishing this 2 or 3 times, I could never again get back into the OS.
I could wipe and flash all of the partitions with no errors, I could always get into stock recovery, but TWRP never worked.
Was anyone *not* on the November patch level of v7.0+?
Click to expand...
Click to collapse
When this first started for me I was on the latest beta build, October security patch.
Same issue here - 64MB Samsung memory.
Google support are aware of the issue, they sent out a replacement no questions asked. For some reason, the guy suggested (but he said unofficially) tapping on the power button. Anybody have any clue why this would be relevant?
Regardless, I'm in a position where I can access fastboot, but nothing else. Can anyone think of any data recovery options at this point?
---------- Post added at 12:26 PM ---------- Previous post was at 12:20 PM ----------
To follow up on my previous post - just before I hit a reboot that threw me into the bootloop, I encountered a hard freeze. I received a bug report after the hard freeze and this is now sitting in my gmail drafts. Would this bug report have any pertinent information here?
thisisgil said:
For some reason, the guy suggested (but he said unofficially) tapping on the power button. Anybody have any clue why this would be relevant?
Click to expand...
Click to collapse
I know exactly why it's relevant!
He's trying to make sure it's not a shoddy power button. My Galaxy SII back in the day had a common power button failure where it would think that you are just constantly hitting/holding the power button if you even breathed on it. My phone would bootloop or suddenly reboot constantly because it was getting power button commands from the poor quality button. Better quality buttons along with other methods of locking/unlocking the phone to reduce power presses have mostly prevented this sort of thing these days.
Hi, guys.
Today, my OP5 decided to troll me. I was using normally him, when suddenly it started to lags pretty bad. I restarted and he continued to lags and freeze. I made a wipe cache via stock recovery (i didnt made any change at all in it, no unlocked bootloader, no root). That's when my nightmare begins. It begins to bootloop. Sometimes i was able to start the boot animation, but then it just restarts to the beginning. I tried a lot of tips, wiping cache, system, etc. Then, i left it charging. When i tried to turn on again, it worked like nothing ever happened to him. I made a backup of my personal data fast, scared to him suddenly restart again. After that, i decided to made a Factory Reset, clean up everything. When i did it, he started the lag and freezes again. I was at lost. That's was when i decided to use the official unbrick tool, to make the cleanest OP5 ever possible. I grabbed the archives from this link and followed this tutorial. When i was executing the programa, in the userdate.img, he showed a error. When i saw it, i just stopped and closed the program. Now, my OP5 is hardbricked. The only sign of life that i get from him is when i connect him at the PC. I can identify it as qualcoom 9008, but when i try to run the program, he just fail and show me error 258.
Plz, i need some orientations. I have been read things for about 10 hours and didnt found a solution. I live abroad for any oneplus tech center, and i believe, for the other posts that i read, that online tech support wouldn't help me a lot. I really don't like to make this kind of post but i am kind of desesperate. I dont have money to afford another phone
Again, sry to disturb you all. Sry if i broke some rule of the forum too. And sry for my bad english, i hope that i was able to communicate right.
EDIT: I just tried in another computer. Same error appears. :'(
Hummm why follow a Unbrick Topic with tools for ...3T ?
Maybe you have a encryption problem, all your Tools/Topic are so old for the actual versions (Oreo 8.X OOS / 8.1 OOS)
I advise to you (in the first time), to flash this TWRP (using fastboot, very simple) just follow this guide : here
If you can flash TWRP, your phone is not bricked, you will boot in TWRP:
- Format Data > tape "yes" > Reboot in TWRP
- Copy/Past xXx 10.0 ROM to test, install and xXx Rom will fix/install for you the best OOS Custom ROM for your OP5 with a great Aroma Installer.
If TWRP with this rom work perfectly, you wil able to restore a official stock OOS for sure, just flash original/stock recovery (fastboot), wipe all data/partitions, install your OOS rom and it's fine
I think @cidsantiago says they bootloader isn't unlocked.
He needs to know that unlock the bootloader implies lost all /sdcard data and also installed apps and settings) before start the TWRP install process...
Pho3nX said:
Hummm why follow a Unbrick Topic with tools for ...3T ?
Maybe you have a encryption problem, all your Tools/Topic are so old for the actual versions (Oreo 8.X OOS / 8.1 OOS)
I advise to you (in the first time), to flash this TWRP (using fastboot, very simple) just follow this guide : here
If you can flash TWRP, your phone is not bricked, you will boot in TWRP:
- Format Data > tape "yes" > Reboot in TWRP
- Copy/Past xXx 10.0 ROM to test, install and xXx Rom will fix/install for you the best OOS Custom ROM for your OP5 with a great Aroma Installer.
If TWRP with this rom work perfectly, you wil able to restore a official stock OOS for sure, just flash original/stock recovery (fastboot), wipe all data/partitions, install your OOS rom and it's fine
Click to expand...
Click to collapse
Pho3nX said:
Hummm why follow a Unbrick Topic with tools for ...3T ?
Click to expand...
Click to collapse
I used the tools for 5. Just the procedure that i get from this topic. :T I am gonna try the method that you gave me now brb.
EDIT: Just tried this. My cellphone cant be recognized in fastboot devices. As a said, i am not getting any response for him, just when i plug it in the PC. So i wasn't able to unlock bootload or anything like that. I tried just to plug it and see if fastboot was able to identifying it, but it wasn't.
bartito said:
I think @cidsantiago says they bootloader isn't unlocked.
He needs to know that unlock the bootloader implies lost all /sdcard data and also installed apps and settings) before start the TWRP install process...
Click to expand...
Click to collapse
Yes, it should not be unlocked. But at the moment, i am taking anything, really. I just want to use my phone.
cidsantiago said:
Yes, it should not be unlocked. But at the moment, i am taking anything, really. I just want to use my phone.
Click to expand...
Click to collapse
Wipe your device data from the stock recovery.
You loss the settings and downloaded apps but not requires to unlock the bootloader.
bartito said:
Wipe your device data from the stock recovery.
You loss the settings and downloaded apps but not requires to unlock the bootloader.
Click to expand...
Click to collapse
I can't access recovery anymore, as i said. The only sign of life that i get is when i connect it in the PC.
I guess i have to do something to restore the basics partitions of my cellphone. Like recovery, boot, etc. But i just have the official tool to do that. There is another way? Like transfering directly by the COM port?
Have you tried following this guide? https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
I had the same exact problem with my old One plus One. Spent like 4 days trying to unbrick it. That msm tool did the fix for me. Also, in that link to the guide you provided, doesn't it flash the Chinese version of the OS? If that's the case, I don't think it was a good idea to do so lol
Mash1ro said:
Have you tried following this guide? https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
I had the same exact problem with my old One plus One. Spent like 4 days trying to unbrick it. That msm tool did the fix for me. Also, in that link to the guide you provided, doesn't it flash the Chinese version of the OS? If that's the case, I don't think it was a good idea to do so lol
Click to expand...
Click to collapse
In one of the links, it had the OOS and the HOS. I tried to use the msm tool in one of them, but it didnt worked I'm gonna try the archives in this link that you gave me. It may work brb with updates.
Don't worry though, it happens to plenty of people. It happened to me as well, and everyone eventually fixes it. It is unlikely that it is a hardware problem, so just following the correct steps should get it working. Keep trying stuff out, it's very good that your computer recognizes it as a qualcomm port, as far as I know that's all you need to flash the necessary things in order for it to boot.
I am getting the same error 258 in this post. :T I posted there to see if the OP can help me. But thx for your help @Mash1ro
Mash1ro said:
Don't worry though, it happens to plenty of people. It happened to me as well, and everyone eventually fixes it. It is unlikely that it is a hardware problem, so just following the correct steps should get it working. Keep trying stuff out, it's very good that your computer recognizes it as a qualcomm port, as far as I know that's all you need to flash the necessary things in order for it to boot.
Click to expand...
Click to collapse
Thx for your support! I will continue to try stuff
Try reading the comments from this post as well https://forum.xda-developers.com/oneplus-3t/help/hard-bricked-op3t-t3574720/page2
2 of the people had the same error as you, and one of them solved the issue by changing the USB port.
---------- Post added at 02:26 PM ---------- Previous post was at 02:23 PM ----------
But don't use the same files and all that stuff, since that's for the 3T. Try to pick out the things that might help but use the files for the OnePlus 5 only
After try the unbrick procedure in 3 different PCs, using about 10 different USB ports, i still getting the same error in the same step. When downloading cache.img, he stuck in about mid bar, and shows me the warning: SendProgramCommand Failed, Error: 258". Besides that, he turns on the green led and stop being recognize by the PC. Then i have to hold power and turn off the green led. :T Maybe i can use a linux to access the partitions?
cidsantiago said:
After try the unbrick procedure in 3 different PCs, using about 10 different USB ports, i still getting the same error in the same step. When downloading cache.img, he stuck in about mid bar, and shows me the warning: SendProgramCommand Failed, Error: 258". Besides that, he turns on the green led and stop being recognize by the PC. Then i have to hold power and turn off the green led. :T Maybe i can use a linux to access the partitions?
Click to expand...
Click to collapse
it seems like a hardware problem, i was facing this on different phone ( 5X )
Apayah said:
it seems like a hardware problem, i was facing this on different phone ( 5X )
Click to expand...
Click to collapse
yeah... But it is kind of weird. He was running smoothly, until suddenly started lag and freeze. He didn't fall or any of that... I think is just a defective phone. Doesn't find another explanation to that.
I think your best option is to RMA the device through OnePlus. Since you haven't rooted it or anything, they should repair it for you.
david19au said:
I think your best option is to RMA the device through OnePlus. Since you haven't rooted it or anything, they should repair it for you.
Click to expand...
Click to collapse
I already contact the store that i bought to get my warranty. Unfortunately, i didn't bought it in oneplus.net, bcs they don't deliver in my country. I am hoping that everything work out
Guys, in the end, i RMA my device back to the seller and gonna have a refund Thank you for your help. So sad that this phone came faulty :T
Best regards to you all!
Bought a secondary essent, figuring if I was going to brick up something, better to brick up a 20$ cracked up POS than my day to day user.
Everything was going as planned, didnt use the 15 second loader used the platform tools...
unlocked her, added BMG's twerp file....there's my mistake...I didnt rename the file.
As I wrote that I realized that.
Cannot get the device to reconize thru adb tools but windows see's her as Meta(or something) tried the different commands but adb doesnt see it.
Cannot turn phone off, tried volume up down power every which way,,,,
Big white lock on the 'keep system on read only screen" and cannot move....in any fashion.
Help me if ya can please,,,phone is at 84%....maybe just letting her die off?
back to bootloader and
I am not sure what sequence of buttons did it, but it was not a rename problem, its a unresponsive twerp problem. Using the original twerp has not accounted for the updates this phone has gone thru....I think BMG got one that a bit more "user friendly"....so I will keep trying with this 20$ phone....also in any of the "tutorials there is mention of an A/B partition but no instruction on it...learning on the fly...
pen101 said:
Bought a secondary essent, figuring if I was going to brick up something, better to brick up a 20$ cracked up POS than my day to day user.
Everything was going as planned, didnt use the 15 second loader used the platform tools...
unlocked her, added BMG's twerp file....there's my mistake...I didnt rename the file.
As I wrote that I realized that.
Cannot get the device to reconize thru adb tools but windows see's her as Meta(or something) tried the different commands but adb doesnt see it.
Cannot turn phone off, tried volume up down power every which way,,,,
Big white lock on the 'keep system on read only screen" and cannot move....in any fashion.
Help me if ya can please,,,phone is at 84%....maybe just letting her die off?
Click to expand...
Click to collapse
Hold power longer than 10 seconds (hard reboot) then volume down and it'll boot bootloader. From there flash a working boot image with working TWRP patched for the Rom you are on.
Sent from my PH-1 using Tapatalk
---------- Post added at 05:34 PM ---------- Previous post was at 05:32 PM ----------
pen101 said:
I am not sure what sequence of buttons did it, but it was not a rename problem, its a unresponsive twerp problem. Using the original twerp has not accounted for the updates this phone has gone thru....I think BMG got one that a bit more "user friendly"....so I will keep trying with this 20$ phone....also in any of the "tutorials there is mention of an A/B partition but no instruction on it...learning on the fly...
Click to expand...
Click to collapse
https://www.youtube.com/channel/UCucUjVNJshybBA8JWftayVA check out my channel where I provide tutorials, reviews and files in links to complete pretty much any task for essential.
Sent from my PH-1 using Tapatalk
First and foremost,,,,
THANKS FOR THE REPLIES AND ADVISE.
Got up, drank a cup, dragged a brush across me head...booted up bootloader, hit on recovery mode and now back to square one with the latest pie flavor.
Sometimes you "over work" the problem.
As a mechanic I sometime got "stuck" and instead of getting frustrated, I simply walked away and came back to it, only to find (as with this) a simple solution.
I am expecting a tv box (PIE, 4 and 64)....should be a head scratcher.
Great forum, good peeps...MANY THANKS!