Related
Hi,
it is the second time my Gnex went into endless reboot loop sessions.
It will boot, load crash after few seconds and reboot again.
I had it unlocked in the store i bought it, and had stock rom (Not sure about the version).
Tried to do factory reset from fastboot, from recovery, and from android. Also tried to flash custom boot loader, Nothing works.
Although fastboot writes it successfuly completed the action so does the factory reset. The phone will work for few seconds but no more.
Also tried using WugFresh, for factory reset and for Flash Stock + unroot in soft-break status
I have no ideas what to do next,
Please help.
Mike
Hi Mike, I think more information is required.
- What action did you take immediately prior to having your phone get stuck in the bootloop? Were you trying to install a Custom Recovery or ROM?
- You mention that this is the second time this has happened. Do you know what caused it to bootloop the first time, and if yes what fixed it?
- When your Gnex is in Fastboot/Bootloader mode, and using a tool like Minimal ADB and Fastboot on your computer, does the tool recognize the Device ID after using the fastboot devices command?
You may also want to read through this thread.
AvidPhisherman said:
Hi Mike, I think more information is required.
- What action did you take immediately prior to having your phone get stuck in the bootloop? Were you trying to install a Custom Recovery or ROM?
- You mention that this is the second time this has happened. Do you know what caused it to bootloop the first time, and if yes what fixed it?
- When your Gnex is in Fastboot/Bootloader mode, and using a tool like Minimal ADB and Fastboot on your computer, does the tool recognize the Device ID after using the fastboot devices command?
You may also want to read through this thread.
Click to expand...
Click to collapse
Hi thanks for the reply, i am a simple user, prior to the bootloop i was using whatsapp, actually the android crashes few seconds after getting a whatsaap message (i recieve notification and it goes down). Previous time also i didn't do anything special. i never installed custom recovery or roms... previous time it was fixed by a lab the phone was on warranty.
And yes the tool recognize the device.
So your device receives a WhatsApp message/notification, restarts, and then gets stuck in a bootloop?
That is very strange, as personally I've only ever encountered bootloops after bad ROM flashes (usually after I accidentally skipped a step somewhere during the process). Bootloops usually don't happen to regular users who are just using their phone purchased as-is from a store/carrier.
If you can get it to boot back into Android, try uninstalling WhatsApp and see if that helps. Hopefully it's still under warranty, as you may have to take it back to the store and have them look at it.
AvidPhisherman said:
So your device receives a WhatsApp message/notification, restarts, and then gets stuck in a bootloop?
That is very strange, as personally I've only ever encountered bootloops after bad ROM flashes (usually after I accidentally skipped a step somewhere during the process). Bootloops usually don't happen to regular users who are just using their phone purchased as-is from a store/carrier.
If you can get it to boot back into Android, try uninstalling WhatsApp and see if that helps. Hopefully it's still under warranty, as you may have to take it back to the store and have them look at it.
Click to expand...
Click to collapse
Tried to uninstall whatsapp but it crashes before i manage to do so.
even managed to access memory via TWRP and delete whatsaap manually but somehow it appears again after restart.
Something is terribly wrong
Have you tried using Odin to repartition and restore to stock? Could be a corrupted partition. Check out this guide
nthnlee said:
Have you tried using Odin to repartition and restore to stock? Could be a corrupted partition. Check out this guide
Click to expand...
Click to collapse
Why???
Just use fastboot, Odin is evil. Nexus aren't Touchwiz crap phones.
beekay201 said:
Why???
Just use fastboot, Odin is evil. Nexus aren't Touchwiz crap phones.
Click to expand...
Click to collapse
When fastboot didn't work. i had to try something else. But, odin didn't work either.
mishkap said:
When fastboot didn't work. i had to try something else. But, odin didn't work either.
Click to expand...
Click to collapse
Let's see then. Be prepared to spend at least 30min reading, and re-reading, until you actually feel comfortable in what you're doing/typing in. If you're not sure about the technical terms and what lies behind them, read this thread's #1 First Post.
What's your device variant? maguro? toro? toroplus? This will tell which factory image you need to flash.
You need to flash latest factory image, which is (for maguro variant) Android Build 4.3 (JWR66Y). Read #1 First Post on this thread. And I mean, READ IT! Do not do anything else to your device until you do.
After you flash the factory image, that first boot will take a while to reach Android. Chill out. Go get yourself a drink. Take your time. It should have booted into Android already when you get back. It should be fine, but if not, you need to enable USB debugging under Settings > Developer Options, to check the system log.
If after 15min, it still has booted yet, pull the battery out, wait a few secs, put it back in.
Use the 3bc (3-button combo) to reach fastboot mode again. Flash a custom recovery. That's done by downloading the latest TWRP or CWM (i'll leave that choice up to you, be mindful that you might wanna try them both in the future), and running on the host (the PC):
Code:
fastboot flash recovery recovery_filename_here.img
Don't reboot the device. Use the volume keys to "Reboot to recovery" straight from fastboot. After a few seconds, you should be seeing the custom recovery you've flashed with the fastboot command above.
Now comes the part where ADB is required. I hope you've already read the answers to questions "Where do I get the driver for my PC?" and "Why do I need to install the driver twice?". If not, read them now. Also, read "What is ADB?". TIP: When a custom recovery is actually running on the device, ADB mode is already active by default, so when hooking up to the pc the device will show as an ADB interface, so installing the driver (if needed/not done yet) is piece of cake.
After you get ADB to recognize your device (like, you see your device's SN on the output of command `adb devices`).. You need to copy a custom ROM to your device, and flash it. That will get you, most likely than not, Android's USB debugging by default (read answer to "What is an insecure boot image?" on the first link), and that will allow you to see the system log, WHILE Android is booting up. Why do we wanna do this? Cos we want to see if any errors show up, something that may tell us what's failing.
When choosing a ROM from the Android Development section, ask around in the thread if the ROM has USB debugging enabled by default.
Read "What are the ADB commands?" in the thread I first linked to. You'll need to learn at least `adb push` for now.
Once you get the ROM in your /sdcard/ or whatever folder you like, disconnect the USB cable, wipe data/factory reset, then install zip from sdcard (that zip you pushed before).. Forget about gapps for now.
Connect the usb cable, reboot, and once you see padlock screen go away, start trying to run `adb devices`. Do you see your SN in the output? Once you see it, good, it already connected to adb on the device. Run `adb logcat` and try to look out for errors. Logcat is the system log.
To know how to grab that output to a text file so that you can share it with us.. Google it, my fingers hurt.
Thanks beekay201,
As a matter a fact. shortly before you posted this answer i gave up and gave my phone to a local lab.
But unfortunately they were useless and didn't manage to do anything claiming they don't have spares for my phone, tried to explain that it is not a hardware issue, but all in vain .
Anyway, ill go over your instructions and ill update the results soon.
This is my first post and I am writing it after a Christmas night with the fam, so please expect errors.
This phone has given me problems even before it arrived to my door Christmas eve. My city received too much snow for the mailman to deliver my package to my door, making it more difficult for me to obtain my device on time. Once I received my device it was great, fingerprint sensor was extremely convenient, took great pictures for Christmas, call quality was good, among other little things. Getting to the point of this thread. I got a notification to update my phone to the latest software, because we eating, I tried to set it for later. The "later" button did not work. after 2 hours and the annoying notification, I decided to download the update and install it. These are my steps:
Pluggled in the charger
Downloaded update
let the phone do its thing overnight
I woked up
"Google logo" bootloop
I can't access the recovery partition, it shows the green android logo with the string "no command"
When I manually boot the device using the bootloader:
"Your device is corrupt. It cant be trusted and may not work property
visit this link on another device
g.co/ABH
press power to continue "
please need help, It has been only 12 hours with the device, and I do not have a C to USB adapter to flash anything to the device.
Does bootloader allow you to use adb commands still?
hopesrequiem said:
Does bootloader allow you to use adb commands still?
Click to expand...
Click to collapse
I do not have a USB type C adapter, so I can not use any adb commands with the device.
The "No Commands" happens when I use the volume button to access recovery, as if there was no recovery partition installed
Call Google.
bobby janow said:
Call Google.
Click to expand...
Click to collapse
I would have tried, but the nexus 5 is the only device on the house.
I managed to find a type C cable at my local store (probs the only thing open today) I am going to try to flash a factory image using google's official method.
Any tips would be welcome.
I just checked and my recovery says no commands, I think it always does. To actually get the recovery commands to come up, when you're in recovery, press and hold the power button and then press volume up straightaway. The recovery menu will then come up and I suggest wiping your cache and rebooting. If that fails then u can also factory reset from there.
Sent from my Nexus 5X using Tapatalk
I was not able to flash anything yet.
Hayth said:
I just checked and my recovery says no commands, I think it always does. To actually get the recovery commands to come up, when you're in recovery, press and hold the power button and then press volume up straightaway. The recovery menu will then come up and I suggest wiping your cache and rebooting. If that fails then u can also factory reset from there.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply, when I used your method, a new screen showed up, downloading mode.
Firmware Update
Do not unplug the USB connection until the process is complete.
0%
I tried to adb and fastboot to access the recovery and wipe the cache but no luck.
LeGrassy said:
I was not able to flash anything yet.
Thanks for your reply, when I used your method, a new screen showed up, downloading mode.
Firmware Update
Do not unplug the USB connection until the process is complete.
0%
I tried to adb and fastboot to access the recovery and wipe the cache but no luck.
Click to expand...
Click to collapse
Huh, that is strange.. Sorry to hear it didn't work. Sounds like somethings definitely not quite right, I'd definitely go down the flashing stock images route.. I'm not sure how you can go about unlocking the bootloader though if you haven't already. Now we have the choose the allow oem unlock option in developer options u need to be able to start the phone :/
Sent from my Nexus 5X using Tapatalk
Ok, I uninstall and re-installed all the drivers with SDK tools and I that fixed my fastboot problems.
Now I have to unlock my device, but I can't load the OS, I have the factory image, downloaded from the google developer website.
I have the bullhead LGH790 16GB variant, and downloaded the (MMB29K) 6.01 Marshmallow
The issues as mentioned before is that the OS does not load so I cannot unlock my bootloader.
Is there any way to unlock it to flash a stock rom throught ADB, Fastboot, bootloader, etc?
LeGrassy said:
Ok, I uninstall and re-installed all the drivers with SDK tools and I that fixed my fastboot problems.
Now I have to unlock my device, but I can't load the OS, I have the factory image, downloaded from the google developer website.
I have the bullhead LGH790 16GB variant, and downloaded the (MMB29K) 6.01 Marshmallow
The issues as mentioned before is that the OS does not load so I cannot unlock my bootloader.
Is there any way to unlock it to flash a stock rom throught ADB, Fastboot, bootloader, etc?
Click to expand...
Click to collapse
That my friend is a very good question. I'm curious to hear the solution myself.
Maybe you can try this, adb flash stock recovery, and then load up the recovery like how I mentioned earlier. Then adb sideload this rom, it's completely stock but in zip format. I don't think it flashes the bootloader radio etc but I don't think they've changed since 6.0. If for any reason they have or u wanna flash the stock images thru fastboot to make sure everything's up to date, then u can go about unlocking the bootloader and reflashing the stock image to make sure uv got the right bootloader, radio etc : http://forum.xda-developers.com/showthread.php?t=3267096
Sent from my Nexus 5X using Tapatalk
I think the question is how do I unlock the bootloader if I can't enable developer options since I can't boot into the stock rom? The bootloader command says you can't unlock, thus really you can't do anything like flashing even a stock .img file. How do you bypass that? How are you able to do anything if you can't boot even into stock rom?
I'm not 100% sure if adb sideload needs an unlocked bootloader or not. I know that flashing an OTA thru stock recovery (update via adb) doesn't need an unlocked bootloader, so could be worth trying that if this doesn't work? Obviously gotta make sure you use the right OTA file
Edit: Actually, now that I think about it I think you need a custom recovery to adb sideload. So the only other thing I can think of is trying to flash the same OTA via stock recovery, OTA files can be downloaded here: http://www.droid-life.com/2015/12/09/download-android-6-0-1-marshmallow-updates-for-nexus-devices/
If your stock recovery isn't working properly though and it still just goes into download mode then I'm outta ideas might have to be an RMA to google
Sent from my Nexus 5X using Tapatalk
I extracted all the files from the .tgz I got from the google's website, and tried to flash the recovery ... but I can't really do it.
HTML:
target reported max download size of 536870912 bytes
sending 'recovery' (12509 KB)...
OKAY [ 0.479s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.502s
I am in the phone with google, and their are transferring me to LG, they will probably want me to return the device.
What a Christmas gift I received. The epic hold music is not helping me feel better either
LeGrassy said:
I extracted all the files from the .tgz I got from the google's website, and tried to flash the recovery ... but I can't really do it.
HTML:
target reported max download size of 536870912 bytessending 'recovery' (12509 KB)...OKAY [ 0.479s]writing 'recovery'...FAILED (remote: device is locked. Cannot flash images)finished. total time: 0.502s
I am in the phone with google, and their are transferring me to LG, they will probably want me to return the device.
What a Christmas gift I received. The epic hold music is not helping me feel better either
Click to expand...
Click to collapse
Christmas music?
RMA in process
Edit: "Christmas music? ", it was the classical music you see in the movies when the evil guy is killing innocent people.
Thanks for everybody who replied, you guys were helpful in one way or another.
LG's manufactures warranty said that my problem needed to repaired, the process will take 7-9 business days, if they cannot fix it they would send me a new phone.
Mods; if needed feel free to close this threat. Thanks
There has to be a way to recover from this. All the guides say to do this or that after you boot into rom and allow unlock bootloader. What if you can't get into the rom. Come on guys someone knows what to do. IRC perhaps? All you need to do is unlock the effin' bootloader and you're golden.
---------- Post added at 05:55 PM ---------- Previous post was at 05:53 PM ----------
LeGrassy said:
Edit: "Christmas music? ", it was the classical music you see in the movies when the evil guy is killing innocent people.
<snip lol>
the process will take 7-9 business days
Mods; if needed feel free to close this threat. Thanks
Click to expand...
Click to collapse
BS 7-9 business days is ridic. No!
bobby janow said:
There has to be a way to recover from this. All the guides say to do this or that after you boot into rom and allow unlock bootloader. What if you can't get into the rom. Come on guys someone knows what to do. IRC perhaps? All you need to do is unlock the effin' bootloader and you're golden.
---------- Post added at 05:55 PM ---------- Previous post was at 05:53 PM ----------
BS 7-9 business days is ridic. No!
Click to expand...
Click to collapse
I'm not BSing she said that they would give me a printing label so I can send it, once they receive the device they will take 7-9 days to repair it and then they would ship. I even made a joke to the customer rep, that in 7-9 days I could find a solution and charge them for my service.
She did not laugh
bobby janow said:
There has to be a way to recover from this. All the guides say to do this or that after you boot into rom and allow unlock bootloader. What if you can't get into the rom. Come on guys someone knows what to do. IRC perhaps? All you need to do is unlock the effin' bootloader and you're golden.
---------- Post added at 05:55 PM ---------- Previous post was at 05:53 PM ----------
BS 7-9 business days is ridic. No!
Click to expand...
Click to collapse
yep, all you have to do is unlock the BL, too bad there is no way to do it in this condition. its fairly common knowledge.
bweN diorD said:
yep, all you have to do is unlock the BL, too bad there is no way to do it in this condition. its fairly common knowledge.
Click to expand...
Click to collapse
I did not know that. Very useful information, thanks.
So I recently got a European M8 and thought I would root it which turned out to be a bad idea. To start off with, it didn't root properly anyway so i carried on using it. Today I wanted to recover it back to stock (When I got it out of the box) I did a command using fastboot which was along the lines of fastboot boot boot.img but now my HTC will launch the screen displaying that it is a build for development purposes only and then it goes to a black screen but still turned on. It seems to me like there is no Operating System for the phone to boot from.
PLEASE HELP ME
Issue Solved - 22/01/16
ChiefMustardo said:
So I recently got a European M8 and thought I would root it which turned out to be a bad idea. To start off with, it didn't root properly anyway so i carried on using it.
Click to expand...
Click to collapse
Hard to help, if we don't know exactly what you did. Try to explain in detail (or as best you can) the exact steps (including file names, version numbers, etc.) of what you performed.
ChiefMustardo said:
I did a command using fastboot which was along the lines of fastboot boot boot.img
Click to expand...
Click to collapse
Again, hard to tell what the issue is, if we don't know exactly what you did.
Are you sure you didn't do fastboot flash? I don't think you would do anything permanent with the command fastboot boot.
What exactly were you trying to boot/flash with this command? What was the file name, where did you get it from, and what was the exact intent?
Did you get this idea from a thread or guide?
ChiefMustardo said:
but now my HTC will launch the screen displaying that it is a build for development purposes only and then it goes to a black screen but still turned on. It seems to me like there is no Operating System for the phone to boot from.
Click to expand...
Click to collapse
If you hold power + vol up for a long time (30 seconds or more) does the phone reboot? Then what, black screen again?
Do Power + vol up again. The moment the screen goes dark (but before the HTC logo screen with the red text warning) let go of those buttons, and only hold power down; and don't let go until you see the bootloader screen. If this fails, try again, you probably just got the timing wrong (started pressing vol down too late, or let go of it too early).
Once in bootloader, select fastboot (if not in that mode already) using vol keys, then confirm with power button. Connect to computer and do: fastboot getvar all
Post the getvar output (delete IMEI and serial numbers before you post).
Again, i am really sorry but i do not understand what i did. It asked me to flash the ROM Update Utility and then use fastboot boot boot.img which then screwed it up and yes when i boot up and reboot it just goes to a black screen.
Here is the info:
ChiefMustardo said:
Again, i am really sorry but i do not understand what i did.
Click to expand...
Click to collapse
I seriously doubt that you can't remember any of the steps you did to try to root it.
Just sounds like you are too lazy to type. So why should I put forth more effort than you; when you are the one that wants help?
Describe as best you can, that is all I ask.
ChiefMustardo said:
It asked me to flash the ROM Update Utility and then use fastboot boot boot.img which then screwed it up and yes when i boot up and reboot it just goes to a black screen.
Click to expand...
Click to collapse
Do you have a file in your fastboot folder (wherever fastboot.exe is located) what is actually named boot.img?
And you really can't remember if you got this idea from a thread? You had to come up with it somehow.
What were you even trying to do here? What did you think the command would do?
Again, either you are just being lazy, evasive, or got hit on the head to cause amnesia; if you can't answer the questions.
So I was looking for tutorials on how to root it and I cam across a program (cannot remember the name) which was designed to root it with a few clicks of buttons ect. I already new how to unlock the boot-loader because I owned a HTC desire 510. I went back onto my phone it has twrp installed but I use root checker and it says that proper root access is not granted and I have tried to use SuperSU but I got the binary issue so I gave up. It was working fine but today I decided I wanted to revert it back to stock again but did something which completely messed it up.
Also, i decided i wanted to restore it because if it broke and i needed it to be repaired it would void my warranty. I was thinking when i reset the RUU it would make it stock again but it did not.
Now, that's more like it!
ChiefMustardo said:
So I was looking for tutorials on how to root it and I cam across a program (cannot remember the name) which was designed to root it with a few clicks of buttons ect.
Click to expand...
Click to collapse
An Android app, or PC program?
Either way, one-click type root apps don't work on HTC devices. PC based toolkits worked at one time, but were never updated to support the recent software builds (outdated TWRP versions fail on Lollipop, and outdated SuperSU versions fail).
ChiefMustardo said:
S I decided I wanted to revert it back to stock again but did something which completely messed it up.
Click to expand...
Click to collapse
What did you think you were doing with the fastboot command (fastboot boot boot.img)?
One thing I can say for sure: Don't try mods, fastboot commands, etc. unless you know exactly what you are doing (such as following reputable instructions to the letter). The command you did just isn't right. You either got it from a bad source, or you decided to improvise or experiment (really bad idea). You made the issue much worse than it was to begin with (probably just needed to flash the updated SuperSU zip, maybe also update TWRP).
---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------
You also didn't answer the question:
redpoint73 said:
Do you have a file in your fastboot folder (wherever fastboot.exe is located) what is actually named boot.img?
Click to expand...
Click to collapse
It was a computer application and i thought the command would reboot it with a different kernal/firmware thing. But yeah i followed the instructions like an idiot and messed up my phone and no i don't anymore because i deleted it
ChiefMustardo said:
i thought the command would reboot it with a different kernal/firmware thing.
Click to expand...
Click to collapse
Fastboot boot means you are trying to remote boot something without flashing it. A boot.img isn't bootable. I've only seen this done with recovery.img
I think you meant to do: fastboot flash boot boot.img
The one different word makes a huge difference. The action is to flash, not boot. The "boot" is the location of where to flash to.
Also, even if you properly flashed boot.img, this is just the kernel, and wouldn't change much. To return to stock, you want to flash a full ROM. And kernel, ROM and firmware are not interchangeable terms, so don't for a second think they are.
Ok. Is it possible though to revert it back to stock and if yes, do you think you can help me?
Do the fastboot command: fastboot oem lock. Then download the 4.16.401.10 RUU from the following thread, and run it from PC: http://forum.xda-developers.com/showthread.php?t=2701376
Your alternative is to restore the proper stock TWRP backup. While the relevant files are on that same link, you'll find clearer instruction on the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
It now says Relocked then underneath security warning. Is that good?
ChiefMustardo said:
It now says Relocked then underneath security warning. Is that good?
Click to expand...
Click to collapse
The security warning just means you altered something in the stock software (root, kernel, etc.). It doesn't matter, as the RUU will write all partitions to factory condition.
Will i have to re unlock the boot-loader for the RUU.exe to work?
ChiefMustardo said:
Will i have to re unlock the boot-loader for the RUU.exe to work?
Click to expand...
Click to collapse
NO. Its required to be LOCKED or RELOCKED to run RUU.
Its the only reason I told you to relock it.
Ok because i had the program running all day with it re-locked but it didn't do anything so i am back to square one
ChiefMustardo said:
Ok because i had the program running all day with it re-locked but it didn't do anything so i am back to square one
Click to expand...
Click to collapse
What does your PC screen say? Is the RUU stuck sending?
You probably just need to disconnect the phone and start again. RUU just gets stuck sometimes. It shouldn't take any more than 5 or 10 minutes.
Yeah it says updating 0 out of 7 sending ........................
ChiefMustardo said:
Yeah it says sending 0 out of 7
Click to expand...
Click to collapse
It should be safe to just disconnect the phone and start over with the RUU again.
This is what comes up
It send that 1 had been sent then it said error
Geez i wish haahwhahai would have a working erecovery. This is maddening.
I've been there before. I was able to use the method involving connecting / disconnecting the usb to get into fastboot, adb the recoveries, and reboot, being immediately prompted to factory restore. I don't know if that's helpful at all.
johncro13 said:
I've been there before. I was able to use the method involving connecting / disconnecting the usb to get into fastboot, adb the recoveries, and reboot, being immediately prompted to factory restore. I don't know if that's helpful at all.
Click to expand...
Click to collapse
Do you have a link to this method of restoring kind sir?
Thanks!
If possible, turn the phone completely off.
Plug the USB cable into the phone
Hold vol down
Hold power and IMMEDIATELY plug the other end of the USB cable into the PC.
This should get you into fastboot. From here, you should be able to use ADB.
Here's the thread that helped me most.
johncro13 said:
If possible, turn the phone completely off.
Plug the USB cable into the phone
Hold vol down
Hold power and IMMEDIATELY plug the other end of the USB cable into the PC.
This should get you into fastboot. From here, you should be able to use ADB.
Here's the thread that helped me most.
Click to expand...
Click to collapse
What should i use after i'm in fastboot? I've downloaded the latest full firmware that's out there, but it seems to be corrupt.
lowspeed said:
What should i use after i'm in fastboot? I've downloaded the latest full firmware that's out there, but it seems to be corrupt.
Click to expand...
Click to collapse
Is your bootloader unlocked?
smokinjoe2122 said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Relocked
lowspeed said:
Relocked
Click to expand...
Click to collapse
I'm not sure how much you can do if the device is locked...A guess a few questions (In my tech support voice):
1.) How did it get to that point?
2.) Can you re-open the bootloader, and if you can, are you opposed to it?
3.) What was the last firmware you installed on it?
smokinjoe2122 said:
I'm not sure how much you can do if the device is locked...A guess a few questions (In my tech support voice):
1.) How did it get to that point?
2.) Can you re-open the bootloader, and if you can, are you opposed to it?
3.) What was the last firmware you installed on it?
Click to expand...
Click to collapse
1) I don't recall.
2) I could probably unlock it again. i'll give it a try.
3) it had some weird restore that i used, but that rom didn't have any update option.
I must sound retarded....
lowspeed said:
1) I don't recall.
2) I could probably unlock it again. i'll give it a try.
3) it had some weird restore that i used, but that rom didn't have any update option.
I must sound retarded....
Click to expand...
Click to collapse
Well most of the time, if it's a software issue, it's fixable. I don't know as much about this phone as I'd like, but I do know there's update packages out there you can use to your benefit if you can get the bootloader unlocked. I believe the Update.APP can even be unzipped or decompiled to get the main imgs from it, such as boot, recovery, and system.
im gonna go ahead and throw this out there. i just returned from the hardest brick i have ever done. i managed to make it so the phone wouldnt boot it would bootloop twice and go to erecovery and fail to restore. then i tried flashing the stock img's extracted from the update.app inside twrp and that made it worse. the screen went completely black and wouldnt do ****, the computer recognized it in bootloader mode but i couldnt flash a single thing as it would say i didnt have permission to or something like that(acting as if the bootloader was locked even though it was unlocked, or locked frp) i was about to give up and put my sim card back in my nexus as no matter what i did i couldnt get the screen to even turn on.
Well i found a post on the mate 9 sub-forum about someone who did the same thing and fixed it with dc-phoenix but costed him 18$, i decided 18 was worth it if it meant i had a working phone. and sure enough 5 minutes after paying and clicking flash update.app in the software it was up and running. now i have no idea how dc-phoenix can flash images when adb couldnt...but it works. if your out of options i would 100% say try it as 18$ is much better than a new phone.
---------- Post added at 07:55 PM ---------- Previous post was at 07:54 PM ----------
something i did notice as the software did the commands to flash each image i noticed it started its commands with some kind of backdoor command. so maybe they know a backdoor to bypass a locked bootloader/frp
darkmage1991 said:
im gonna go ahead and throw this out there. i just returned from the hardest brick i have ever done. i managed to make it so the phone wouldnt boot it would bootloop twice and go to erecovery and fail to restore. then i tried flashing the stock img's extracted from the update.app inside twrp and that made it worse. the screen went completely black and wouldnt do ****, the computer recognized it in bootloader mode but i couldnt flash a single thing as it would say i didnt have permission to or something like that(acting as if the bootloader was locked even though it was unlocked, or locked frp) i was about to give up and put my sim card back in my nexus as no matter what i did i couldnt get the screen to even turn on.
Well i found a post on the mate 9 sub-forum about someone who did the same thing and fixed it with dc-phoenix but costed him 18$, i decided 18 was worth it if it meant i had a working phone. and sure enough 5 minutes after paying and clicking flash update.app in the software it was up and running. now i have no idea how dc-phoenix can flash images when adb couldnt...but it works. if your out of options i would 100% say try it as 18$ is much better than a new phone.
---------- Post added at 07:55 PM ---------- Previous post was at 07:54 PM ----------
something i did notice as the software did the commands to flash each image i noticed it started its commands with some kind of backdoor command. so maybe they know a backdoor to bypass a locked bootloader/frp
Click to expand...
Click to collapse
Which files did you flash in DC Phoenix?
Thanks for posting this!
JDBarlow said:
Which files did you flash in DC Phoenix?
Thanks for posting this!
Click to expand...
Click to collapse
downloaded the latest update on firmware finder for my device(l24) and used winrar to pull the update.app from the zip. then you select that in dc phoenix to do the restore/flash
So I just received the phone today and as I always like to do with my new phones I downloaded the latest full ota, installed it through local upgrade and when I pressed reboot the phone rebooted normally.
I went an pressed reboot to recovery and boom the phone just died, no recovery it goes to QUALCOMM crash dump and I am able to boot into bootloader but OEM unlock is still off in the developers options, cant unlock boot loader, cant flash anything in fastboot and there are no MSM tools.
Anyone have any ideas??
Be careful I was on stock rom flashed with stock latest rom with locked bootloader and no funny business and the phone just dead.
I would contact oneplus. I had this once happen to me on my oneplus 3t and they were able to fix it using remote access and walking me through a few steps.
Will check that now
Once in fastboot. Try and run the commands for unlocking the bootloader. That's what worked for me.
speakeasy2 said:
Once in fastboot. Try and run the commands for unlocking the bootloader. That's what worked for me.
Click to expand...
Click to collapse
Won't work, I think its due to the OEM unlock toggle in the Developers options. (Was your toggled on?)
awsan said:
Won't work, I think its due to the OEM unlock toggle in the Developers options. (Was your toggled on?)
Click to expand...
Click to collapse
Yes, did you try and adb the stock.img if you can get into fast boot you should have a chance.
speakeasy2 said:
Yes, did you try and adb the stock.img if you can get into fast boot you should have a chance.
Click to expand...
Click to collapse
Tried that, tried flashing and booting from a boot.img and both returned with failed locked
What model do you have? I don't see why your OEM unlock option would be greyed out...
i just did the same thing, cant get past "device is corrupt and will not boot" i can get into fastboot but no commands work and it will not boot into recovery at all. unlocking the bootloader comes back "flashing unlock not allowed"
any fixes?
i just did the same thing, cant get past "device is corrupt and will not boot" i can get into fastboot but no commands work and it will not boot into recovery at all. unlocking the bootloader comes back "flashing unlock not allowed"
any fixes?
Wrssmithjr04 said:
I would contact oneplus. I had this once happen to me on my oneplus 3t and they were able to fix it using remote access and walking me through a few steps.
Click to expand...
Click to collapse
Thanks it worked, they contacted me and started a remote session and fixed the phone
craznazn said:
What model do you have? I don't see why your OEM unlock option would be greyed out...
Click to expand...
Click to collapse
It was not greyed out I just didnt press it before the phone was corrupted
jammin6996 said:
i just did the same thing, cant get past "device is corrupt and will not boot" i can get into fastboot but no commands work and it will not boot into recovery at all. unlocking the bootloader comes back "flashing unlock not allowed"
any fixes?
Click to expand...
Click to collapse
Chat with oneplus and request a remote session repair they will send you the files and one person will get remote access to fix your phone, Worked for me
awsan said:
Thanks it worked, they contacted me and started a remote session and fixed the phone
It was not greyed out I just didnt press it before the phone was corrupted
Chat with oneplus and request a remote session repair they will send you the files and one person will get remote access to fix your phone, Worked for me
Click to expand...
Click to collapse
thank you for the reply, i have been waiting on that remote session for 16 hours, hopefully they will contact me soon, i keep getting a run around from there live chat.
jammin6996 said:
thank you for the reply, i have been waiting on that remote session for 16 hours, hopefully they will contact me soon, i keep getting a run around from there live chat.
Click to expand...
Click to collapse
All you need is to change the active boot slot to that of before it was messed up.
In fastboot type:
fastboot getvar current-slot
This will tell you what (corrupted) slot you're currently booting from (either a or b). Then just change to the other one with the command:
fastboot --set-active=a
or
fastboot --set-active=b
Then reboot with the command:
fastboot reboot
i did something similar (hello, im an idiot) and oneplus just had me send my phone to a licensed repair place and have them send me a brand new one.
3 days later, sure enough, it was just a new phone. coming form op6, i didnt realize the state of rooting since OP8. Since google handles OPs OTA updates, its a lot harder and op8t was only able to root thanks to a generous insider who leaked the code needed to make MSMdownloadTool work.
purpleman2k said:
All you need is to change the active boot slot to that of before it was messed up.
In fastboot type:
fastboot getvar current-slot
This will tell you what (corrupted) slot you're currently booting from (either a or b). Then just change to the other one with the command:
fastboot --set-active=a
or
fastboot --set-active=b
Then reboot with the command:
fastboot reboot
Click to expand...
Click to collapse
I attempted that however OEM Unlock is not turned on in developer settings and fastboot --set-active just returns an error, something like Commands not allowed.
After 16 hours I finally got my remote session, it took almost 2 hours and they attempted to flash the wrong files on to my device, thank god MSM verifies that first. Then after the tech says "I apologize, my bad, I should have checked that first, we will try again in about 24 hours."
That was a bit ridiculous and if a supervisor isn't able to get it fixed soon, I'm just gonna return it and take my business somewhere else.
jammin6996 said:
I attempted that however OEM Unlock is not turned on in developer settings and fastboot --set-active just returns an error, something like Commands not allowed.
After 16 hours I finally got my remote session, it took almost 2 hours and they attempted to flash the wrong files on to my device, thank god MSM verifies that first. Then after the tech says "I apologize, my bad, I should have checked that first, we will try again in about 24 hours."
That was a bit ridiculous and if a supervisor isn't able to get it fixed soon, I'm just gonna return it and take my business somewhere else.
Click to expand...
Click to collapse
Please return the device, there are way too people messing up their device and can't fix it. You are seriously going to blame the manufacturer for something you messed up?
schmeggy929 said:
Please return the device, there are way too people messing up their device and can't fix it. You are seriously going to blame the manufacturer for something you messed up?
Click to expand...
Click to collapse
No I'm not blaming then for that. I'm blaming then for there lack of communication and the fact that they have me a run around for 16 hours and being transferred between 2 remote technicians, because "we apologize but Agnes is new here and wasn't sure what she was doing" just for the 2nd technician, Olivia, to attempt to flash the wrong files, and then says "we will try again this time tomorrow" that shows me how incompetent they are. They ask for a list of information before hand so that they make sure they have the right device and files.
And to further my reason for return, when I placed my pre-order it was listed as Dual-SIM, just to receive a single sim version. And the phone gets much hotter then most, and the battery life is no where near what it should be. With all that they want nearly the same price as all other flagship devices..
Finally got OnePlus to fix my phone using the MSM tool, and was able to keep an unprotected copy of it. what is the best place to upload and host a 3.5gb file so i can share it here?
Install TWRP through Odin and format data,, then flash factory stock ROM with Odin. Done!!!
Faizanbutt907 said:
Install TWRP through Odin and format data,, then flash factory stock ROM with Odin. Done!!!
Click to expand...
Click to collapse
odin is for samsung. you are on OP9 Pro section.