Related
So I have upgraded my i927 captivate glide using the ROM from , but I only Androidupdate com called I927UCLH2_I927ATTLH2_I927UCLH2_Home tar md5 but I get a black screen with a slide down menu saying the date ‘Ongoing’ and an option to change the way that the device connects to another computer.
The update stated pass, it booted and proceeded to tell me that it was updating apps or something like that, then a black screen with the pull down menu from the top of the screen near the usb symbol came up but nothing else. I got a message a few hours later stating that the update application or something like that was not responding and an option to wait or quit. I chose wait, but nothing came of it eventually.
I then proceeded to try reflashing the process with no success even after factory reset and rebooting.
I then tried the pre-release ICS update as per XDA developers and other websites. Same thing
I tried a few other ODIN programs and ROMs but no success. Same issues including the hang up on the Samsung logo. I tried rooting it once and for some reason it started up into what looked like the same pull down menu, but it was requesting that I needed an to input a lock code for the network. I assume that is because my sim card was in it by now, but maybe not. I got so frustrated that I tried the bootloader and update bootloader options using the official ICS update ROM for some stupid reason but nothing. The thing is that at least it booted into the pull down menu that i got with a black screen again.
I then flashed with an updated ICS, CWM6 but cannot do the:
Third: Reboot into CWM6 (Volume- and power) install from sdcard (superuser)
Link to superuser: Superuser-3.2-RC2-arm-signed zip
Forth: Repeat third step above but install keyboard fix.
Link to keyboard fix: CWM_keyboard_backlight_fix zip
since I do not have an SD card that is working. I did get the SD Card in the device but I have always had problems with the format of it and I cannot put the zips onto the card due to the computer Win7 not recognizing it. I tried reformatting the device is HPUSB format program and windows. I inserted the card into the device to hopefully have it recognized on windows, and i gave me an option to format the SD card. So I proceeded and success. I was able to put the Zips onto the card. However, I returned to the CWM6 screen by pressing the VOL- and power keys but the files were no where to be found on the SD Card.
I moved on after a few other tries at it, so I tried to go backwards to the Gingerbread ROM. No success, same hanging issue at the Samsung logo.
I then tried to reflash with the devices original ROM as provided by DroidAngel on androidupdate com. Both without success.
I wanted to try the process involved on the 'stuck on boot screen' thread, but I cannot access the zip files on the sdcard in order to be able to do that.
I also bought my phone unlocked from the US (ATT version) and had it sent to me in Canada unlocked so I cannot just return it to the seller to get a new one, so my new phone is pretty useless.
I have spent two days reading through and trying different fixes and updated ROMs on multiple sites but I just cannot figure out what the heck to do now. I know that this site is not to spoon feed people and I am a noob to all of this but I am out of ideas and cannot find anything else to help out.
Where do I go from here. Is there a possibility of reformatting EVERYTHING on the device including all partitions etc etc.? I mean the hardware is fine, it is just a software issue. I do this to my laptop whenever I get into a bind.
Have you tried booting into CWM and restoring factory?
sent from my captivate glide running ICS (NardROM 0.3 Rooted)
Just a note, the SD card you're seeing in CWMR isn't actually your physical SD card, its the internal phone memory. I don't think we have a version of CWMR that reads the real external SD unless modified. So anything you put on it won't show up there. The folder structure will look like ... /sdcard/external_sd/ where /sdcard/ is where you want to put your files for CMWR to see, /external_sd/ is your physical card you can take in/out.
I have tried to reflash with CWM6 using ODIN v3. I didn't realize that the SD card that came up was actually a part of the internal memory. Thanks to you both for the help.
Any other suggestions since no matter what I do now the phone simply stops at the Samsung logo and wont turn off? I press the power button for the required time to shut it down but it automatically restarts by itself to again sit at the Samsung logo.
EaglesIII said:
I have tried to reflash with CWM6 using ODIN v3. I didn't realize that the SD card that came up was actually a part of the internal memory. Thanks to you both for the help.
Any other suggestions since no matter what I do now the phone simply stops at the Samsung logo and wont turn off? I press the power button for the required time to shut it down but it automatically restarts by itself to again sit at the Samsung logo.
Click to expand...
Click to collapse
A few questions about your situation right now:
Can you get into Download mode? (Turn off the device, in your case remove the battery. Press power en volume UP)
Can you get into CWM? (Turn off the device, in your case remove the battery. Press power en volume DOWN)
Does it keep asking you for the Network Key? Are you stuck at that particular point...?
Evil Alex said:
A few questions about your situation right now:
Can you get into Download mode? (Turn off the device, in your case remove the battery. Press power en volume UP)
Can you get into CWM? (Turn off the device, in your case remove the battery. Press power en volume DOWN)
Does it keep asking you for the Network Key? Are you stuck at that particular point...?
Click to expand...
Click to collapse
Okay, so right now I can still get into the download mode to flash, the CWM6 to factory reset and reboot which I have tried already as stated, and I have not been asked for the network key again since the one time quite a long time ago. The network key is only asked when I load one of the other custom ROMS though, but I have not tried any of those in a while.
I am stuck at the black screen with white Samsung logo.
In CWM6, do you see "mounts and storage" (Second to last option)
If so, connect your phone with the USB cable and select "mounts and storage".
In there and select "mount USB storage" (Again, second to last option, you'll have to scroll to get to it)
Now your PC should see the USB storage which is in fact what is marked as internal SD. So the sdcard CWM can actually see and install things from.
Now you can copy a custom ROM to it, and install it through CWM. Or install anything that is in CWM format.
You may get the Network Key Request as before. I do not know if it can be bypassed by starting it without the SIM. If so, you could then try to unlock your device using one of the methods on the forum.
Alternatively, and highly recommended by yours truly, is to buy the unlock code.
It is somewhat common for these devices to re-lock, so having the code handy is very convenient. I used americanunlocker to get mine, and I put the code on the inside of the back-cover should I find myself re-locked in the middle of nowhere. The code works, and isn't that expensive. In fact, it's a steal if you look at your own time invested in all this in terms of hourly wage! Of course, you'll need the IMEI code. You can find that by removing the back-cover and the battery.
Good luck!
Got it running on Bio360 but 'Not Registered on Network' now
Evil Alex said:
In CWM6, do you see "mounts and storage" (Second to last option)
If so, connect your phone with the USB cable and select "mounts and storage".
In there and select "mount USB storage" (Again, second to last option, you'll have to scroll to get to it)
Now your PC should see the USB storage which is in fact what is marked as internal SD. So the sdcard CWM can actually see and install things from.
Now you can copy a custom ROM to it, and install it through CWM. Or install anything that is in CWM format.
You may get the Network Key Request as before. I do not know if it can be bypassed by starting it without the SIM. If so, you could then try to unlock your device using one of the methods on the forum.
Alternatively, and highly recommended by yours truly, is to buy the unlock code.
It is somewhat common for these devices to re-lock, so having the code handy is very convenient. I used americanunlocker to get mine, and I put the code on the inside of the back-cover should I find myself re-locked in the middle of nowhere. The code works, and isn't that expensive. In fact, it's a steal if you look at your own time invested in all this in terms of hourly wage! Of course, you'll need the IMEI code. You can find that by removing the back-cover and the battery.
Good luck!
Click to expand...
Click to collapse
Thank you so much for the feedback, I actually had not thought about the unlock code idea, and since you put it into such perfect terms considering the time and effort that has to go into something like that, it is a good idea for sure to get one. The idea of keeping it on the inside of the back cover is another awesome idea. Kudos to you and thanks!
As for the rest of what you had stated about the mounting and what not; I actually mounted and successfully reflashed and installed all of the required files for the new ICS stock upgrade. The good news was that I got past the Samsung screen again and it said that it was updating all of the applications or whatever again, but then it just gave me the pull down menu again with very limited functionability.
I then used your suggestion to try out another ROM. I tried the Bio360 and followed all directions on the 'phone stuck on boot screen thread'. It worked! I finally have a functional phone again and will be able to get calls from my boss. Thanks!
Now that I know I have one option, I can explore any other options. I still cannot figure out how it is that I will be able to get the ICS upgrade but maybe I will try Kies.
However, I just found that I don't have network access anymore despite that I have a strong cell signal, so I presume that I will have to enter the unlock code somewhere. Where can I put that into? It didn't pop up to tell me anything.
EaglesIII said:
Thank you so much for the feedback, I actually had not thought about the unlock code idea, and since you put it into such perfect terms considering the time and effort that has to go into something like that, it is a good idea for sure to get one. The idea of keeping it on the inside of the back cover is another awesome idea. Kudos to you and thanks!
As for the rest of what you had stated about the mounting and what not; I actually mounted and successfully reflashed and installed all of the required files for the new ICS stock upgrade. The good news was that I got past the Samsung screen again and it said that it was updating all of the applications or whatever again, but then it just gave me the pull down menu again with very limited functionability.
I then used your suggestion to try out another ROM. I tried the Bio360 and followed all directions on the 'phone stuck on boot screen thread'. It worked! I finally have a functional phone again and will be able to get calls from my boss. Thanks!
Now that I know I have one option, I can explore any other options. I still cannot figure out how it is that I will be able to get the ICS upgrade but maybe I will try Kies.
However, I just found that I don't have network access anymore despite that I have a strong cell signal, so I presume that I will have to enter the unlock code somewhere. Where can I put that into? It didn't pop up to tell me anything.
Click to expand...
Click to collapse
You're very welcome! Glad to hear the phone is usable again. In order to get data back you will have to set your APN manually. Stock ROMs come with the APN settings for all providers it is expected to be sold with. But custom ROMs usually come without those settings. You can find the APN settings for your provider online, just do a search. There is even an app for it, but the name eludes me at the moment. You'll need wifi to get the app, though! Once the settings are in place (You put them in under wireless & Networks), you'll have data again.
As for the limited functionality, I had the same thing, at first. The upgrade was broken for me, I guess some settings/apps were causing problems. So, after flashing the upgrade, I did a factory reset in CWM. I also wiped the cache, and the Dalvik cache, for good measure(Under advanced in CWM). It rebooted, said it was upgrading and installing, and I let it sit for a few minutes. Then I was greeted by an initial setup screen, and the phone has been on a working ICS ever since! I did lose all my settings and such, but I had a back-up of those with Titanium Backup, and got those back that way.
Hope this will help as well.
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
SomewhatIrked said:
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
Click to expand...
Click to collapse
Did your phone just reboot in the middle of doing something innocuous then start bootlooping? Were/Are you on total stock with bootloader locked? If both yes, it is probably hardware issue you are encountering.
Regarding sideloading, did you place your Android recovery in sideload mode?
Did you verify adb can "see" your device using "adb devices"?
SomewhatIrked said:
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
Click to expand...
Click to collapse
Well luckily I made this post today.
The more this goes on, the more I believe it to be hardware ...
@sfhub - reasonably innocuous. Had just opened one or 2 apps that morning. Not sure what had updated overnight app/os wise. Not anything interesting as far as I can tell. Once I managed to get it into recovery "adb devices" was returning the phone.
@bardhi92 - I saw that once I got in. However, I couldn't get it to see my phone.
Updated things I have tried and why I've all but thrown in the towel:
After the OTA rescue sideload failed I started trying a few different things. It stopped taking me into recovery mode more frequently, at least it seemed that way - it would just keep bootlooping. My main issue is that I has a locked bootloader, which stopped me whacking TWRP on and loading on a custom rom - just to see if that worked.
I thought it might let me sideload on a factory default img file. Turns out nope.
However I used NRT to "Flash Stock + Unroot" (with "Soft Brick/Bootloop" checked) which for some reason, then allowed me to get back into recovery mode. I had also removed the sim card/tray at this point. May have been either or neither of those that allowed me to get into recovery mode. Can't say for certain.
I cleared /cache and /data and then attempted the OTA rescue update again. This time it failed at 45% (according to my cmd prmpt) with the error: "* failed to read command: No error". I'm not sure text was on the phone at the time. But it did manage to boot into Android. I quickly stepped through the various intro steps (putting in the sim, adding my mail google account details).
I went to get a beer. Only to find it boot looping again.
Not to be deterred, I vowed to try again. Same steps as before (remove sim, nrt voodoo). This time however the OTA rescue worked and fully completed. I went through the intro steps again. This time I quickly turned on dev options, enabled usb debugging and sorted out the OEM bootloader. I thought this would be smart, just in case it hapened again. Once I chose to unlock ("fastboot reboot", selected yes), it decided to start boot looping again.
The main annoyance is: I don't think I have any proof of purchase, even though it's in warranty. That, and I now live in Dubai - so shipping back to the UK where I brought it is going to be killer. But I think it's the path of least resistance at the moment.
SomewhatIrked said:
The more this goes on, the more I believe it to be hardware ...
@sfhub - reasonably innocuous. Had just opened one or 2 apps that morning. Not sure what had updated overnight app/os wise. Not anything interesting as far as I can tell. Once I managed to get it into recovery "adb devices" was returning the phone.
@bardhi92 - I saw that once I got in. However, I couldn't get it to see my phone.
Updated things I have tried and why I've all but thrown in the towel:
After the OTA rescue sideload failed I started trying a few different things. It stopped taking me into recovery mode more frequently, at least it seemed that way - it would just keep bootlooping. My main issue is that I has a locked bootloader, which stopped me whacking TWRP on and loading on a custom rom - just to see if that worked.
I thought it might let me sideload on a factory default img file. Turns out nope.
However I used NRT to "Flash Stock + Unroot" (with "Soft Brick/Bootloop" checked) which for some reason, then allowed me to get back into recovery mode. I had also removed the sim card/tray at this point. May have been either or neither of those that allowed me to get into recovery mode. Can't say for certain.
I cleared /cache and /data and then attempted the OTA rescue update again. This time it failed at 45% (according to my cmd prmpt) with the error: "* failed to read command: No error". I'm not sure text was on the phone at the time. But it did manage to boot into Android. I quickly stepped through the various intro steps (putting in the sim, adding my mail google account details).
I went to get a beer. Only to find it boot looping again.
Not to be deterred, I vowed to try again. Same steps as before (remove sim, nrt voodoo). This time however the OTA rescue worked and fully completed. I went through the intro steps again. This time I quickly turned on dev options, enabled usb debugging and sorted out the OEM bootloader. I thought this would be smart, just in case it hapened again. Once I chose to unlock ("fastboot reboot", selected yes), it decided to start boot looping again.
The main annoyance is: I don't think I have any proof of purchase, even though it's in warranty. That, and I now live in Dubai - so shipping back to the UK where I brought it is going to be killer. But I think it's the path of least resistance at the moment.
Click to expand...
Click to collapse
So, you flashed the .TOT file, sideloaded the given OTA within the stock recovery bootloader that comes with the .TOT file, and cleared cache/factory reset?
Please condense it. If you managed to start up the phone, that's a huge success for people who have not been able to yet.
bardhi92 said:
So, you flashed the .TOT file, sideloaded the given OTA within the stock recovery bootloader that comes with the .TOT file, and cleared cache/factory reset?
Please condense it. If you managed to start up the phone, that's a huge success for people who have not been able to yet.
Click to expand...
Click to collapse
In short:
OTA rescue failed during adb sideload,
Tried bullhead-nbd90w-factory-d2f11c5f.zip & removed sim tray - seemed to allow access to recovery mode,
OTA rescue claims to have failed at 47% during adb sideload- still booted into android. However briefly. Went back to bootloop,
Tried bullhead-nbd90w-factory-d2f11c5f.zip & removed sim tray - seemed to allow access to recovery mode,
OTA rescue completed via adb sideload,
Turned on dev options (usb debug, oem unlock),
Booted to fastboot - unlocked bootloader. Now back to bootlooping
@bardhi92 - I could not get the LG utility to detect my phone. Will attempt again tomorrow.
SomewhatIrked said:
@bardhi92 - I could not get the LG utility to detect my phone. Will attempt again tomorrow.
Click to expand...
Click to collapse
IMO you shouldn't flash the TOT file. If you end up bootlooping again, your phone will be stuck in bootloader locked mode with no ability to unlock it.
If you were able to get your phone to boot into android once, there is really nothing the TOT file will do for you that you can't do from TWRP or bootloader, whereas once it locks your bootloader, there are problems you can no longer fix like EFS corruption (which likely isn't your problem).
In the end, you probably do have eMMC that is slowly starting to fail. There is usually error correction on the eMMC that can lock out bad blocks but if it gets to serious, it'll fail. This is why reflashing stuff over and over sometimes works.
didn't enable developer options on this phone seeing that I was primarily going to use this phone as my daily driver so I carried on using the phone as is. the next day my phone show me an error, it said "Your device is corrupt. It can't be trusted and may not work properly." (Red) and I proceeded to link it showed me to see what the problem might be.
A few minuets after it showed me that error my phone shut down and couldn't turn on. I tried everything to reboot it but to no success, I was able boot it in fastboot mode and downloaded all the appropriate tools to do a flash install of a factory default image,I got the default operating system that the phone came with, as well as adb-tools required to perform a system wide flash seeing as i didn't have that much data on it.
Once everything was set, I followed the step by step instructions that google provided me on the restore to factory setting pages "https://developers.google.com/android/nexus/images". Seeing as I didn't enable developer options when my phone was working, I run into a prerequisite that needed that before I could flash my device.
While running the commands in cmd as an administrator, I run the command -
fastboot flashing unlock command and the console responded with -
FAILED (remote: oem unlock is not allowed)
I went back and reread this step, which was step number 4, It indicated "If necessary, unlock the device's
bootloader by running" the command. so i figured maybe it isn't really necessary, I proceeded to run the flash-all.bat
script, and it FAILED at every step saying -
FAILED (remote: device is locked. Cannot flash) //corresponding .img file//
It failed to flash my nexus 5x at every stage. So I did some research and found out that the problem was
that in the fastboot menu, the Device state was locked in a very assuring green color, and every where I
searched it indicated that this option to unlock the device was in the developer settings in the phones
OS, which is rather odd to put such a feature in the phones OS and fail to include the option in the fastboot menu. I
couldn't find any tool or assistance change the status of the device state to unlocked.
Now my question is, how can I change the device state to unlocked without enabling this options prior in the OS seeing
as i cant do that because my phone isn't coming on at all. any assistance or help would be highly appreciated.
Point of clarification, I have tried everything in accordance to what google nexus support pages have showed
me to the letter.
You can't enable OEM unlock by fastboot/recovery.
But there's another way to rescue your phone.
So
Can you boot into recovery? (Bootloader mode switch to recovery mode using volume keys and press power to choose it)
If it started and you would see an Android with an red triangle press power and hit volume+ to turn on menu. If it works you are safe.
Then download OTA image from Android developers page (OTA, not factory), launch command line (I don't know how it works on Windows, I've never flashed anything on Windows )
And you will need to flash this OTA image by executing adb sideload nameofpackage.zip
Remember to choose adb sideload in recovery first and then executing a command. It should flash and your phone should work.
Good luck!
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
I cant boot in recovery mode... When I tried to boot in recovery stuck in google logo then power off...
Oh that's not good.
Do you have warranty on your phone?
The last thing I keep in mind is flashing using LG tool, but I might take a look on it because I don't know how to use it.
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
No not in warranty....
I contact in LG service center they said chage the motherboard and cost around 170$
That amount so big??
Is there any method to unlock in this case from fastboot?
I need to unlock for custom kernel to flash.
Im on bootloop and oem locked in the system (befor got bootloop)
Help
Domin_PL said:
Oh that's not good.
Do you have warranty on your phone?
The last thing I keep in mind is flashing using LG tool, but I might take a look on it because I don't know how to use it.
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
Click to expand...
Click to collapse
try to >>>Nexus Root Toolkit<<<
Do you your computer can see phone
There where some hidden fastboot commands on XDA. Maybe you can try some of them to see if they can go around this limitation.
Sent from my Nexus 5X using Tapatalk
akins0405 said:
try to >>>Nexus Root Toolkit<<<
Do you your computer can see phone
Click to expand...
Click to collapse
I have the same issue mentioned above. Downloaded Nexus Root Toolkit and i have tried unlock through Nexus Root Toolkit. It seems failure. Because, After detecting my device it reboots and my phone reboots and shows the google logo and reboot again and again... My phone will not boot into recovery mode. While we click on it, it shows google logo and reboots again and again... Is there any solution for this?
OMG!!!
I Have the exact same issue with my bq aquaris x5
I really wish someone would find a solution for this
Seems options are very limited now
Having exact same issue with Huawei Y3. After spending the whole day, came to the conclusion that there is now only two options left: a) Replace the motherboard. b) pay £15 at dc unlock website to unlock oem. Not decided which one should i go for..
I got the same issue.
Nexus 5X has no activated "Allow OEM Unlock".
I tried with the Nexus Root Toolkit.
When I try to unlock Bootloader or the option "Fix Bootloop" he wants me to put the phone into Fastboot.
When I put phone into Fastboot he recognizes it and then restarts the phone. From now on nothing more happens, because noe the bootloop is "active" again.
Recovery Mode is not working, too.
Before I can access it, bootloop starts.
Sound as the same issue as @tomsonmathewv has.
Can someone help me?
EDIT:
While I tried some other solutions my Nexus 5X booted and booted.
And suddenly it booted one time to the Pattern screen. I entered the pattern and waited again for the bootloop after google animation.
But then the google animation finished and a short black screen with s small blue line in the middle of the display appeared. Looked like a "graphics error". But then immediately the normal phone idle screen appeared. The phone started!
I immediately went to the DEV-Options and Allowed OEM-unlock. And I took screenshots of the current configuration.
The current Android is 8.1
Is it recommended to flash an older version of Android to prevent a new Bootloop?
I had the same issue after the latest Android update on my Nexus 5X.
Have you left the device in charge before it manage to start?
Thanks
EDIT: Solved leaving it unplugged.
Hey buddy try Nexus Root Toolkit v2.1.9 it will unlock your bootloader without turning your phone on it worked for me.
aadeekhan79 said:
Hey buddy try Nexus Root Toolkit v2.1.9 it will unlock your bootloader without turning your phone on it worked for me.
Click to expand...
Click to collapse
NRT isn't going to work unless you previously allowed for oem unlock in developer options. If you haven't done that and you can't boot into recovery or the system you're kind of sol.
Sent from my [device_name] using XDA-Developers Legacy app
Shuhan44 said:
Having exact same issue with Huawei Y3. After spending the whole day, came to the conclusion that there is now only two options left: a) Replace the motherboard. b) pay £15 at dc unlock website to unlock oem. Not decided which one should i go for..
Click to expand...
Click to collapse
does that software (dc unlocker) actualy works? i've got the same issue with honor 8 pro, which opt. you have selected.
In my case before my N5X started bootlooping I allowed OEM unlock but didn't enabled USB Debugging Mode in Developer options. Is there a way to unlock bootloader with USB Debugging Mode disabled? I want to try the UNBLOD tool, but unlocked bootloader is a requirement.
xrehpicx said:
OMG!!!
I Have the exact same issue with my bq aquaris x5
I really wish someone would find a solution for this
Click to expand...
Click to collapse
Hi
I also need help of a slightly different nature. I'm somehow locked out of my Huawei P10 whereby my unlock pattern is no longer recognized. USB debugging is not enabled. What are my option as i really do not want to factory reset the phone, did not backup data. Coincidentally enough, this occurred after the latest software update. Please can someone help me.
Thanks
Thanks
Roshan0746 said:
didn't enable developer options on this phone seeing that I was primarily going to use this phone as my daily driver so I carried on using the phone as is. the next day my phone show me an error, it said "Your device is corrupt. It can't be trusted and may not work properly." (Red) and I proceeded to link it showed me to see what the problem might be.
A few minuets after it showed me that error my phone shut down and couldn't turn on. I tried everything to reboot it but to no success, I was able boot it in fastboot mode and downloaded all the appropriate tools to do a flash install of a factory default image,I got the default operating system that the phone came with, as well as adb-tools required to perform a system wide flash seeing as i didn't have that much data on it.
Once everything was set, I followed the step by step instructions that google provided me on the restore to factory setting pages "https://developers.google.com/android/nexus/images". Seeing as I didn't enable developer options when my phone was working, I run into a prerequisite that needed that before I could flash my device.
While running the commands in cmd as an administrator, I run the command -
fastboot flashing unlock command and the console responded with -
FAILED (remote: oem unlock is not allowed)
I went back and reread this step, which was step number 4, It indicated "If necessary, unlock the device's
bootloader by running" the command. so i figured maybe it isn't really necessary, I proceeded to run the flash-all.bat
script, and it FAILED at every step saying -
FAILED (remote: device is locked. Cannot flash) //corresponding .img file//
It failed to flash my nexus 5x at every stage. So I did some research and found out that the problem was
that in the fastboot menu, the Device state was locked in a very assuring green color, and every where I
searched it indicated that this option to unlock the device was in the developer settings in the phones
OS, which is rather odd to put such a feature in the phones OS and fail to include the option in the fastboot menu. I
couldn't find any tool or assistance change the status of the device state to unlocked.
Now my question is, how can I change the device state to unlocked without enabling this options prior in the OS seeing
as i cant do that because my phone isn't coming on at all. any assistance or help would be highly appreciated.
Point of clarification, I have tried everything in accordance to what google nexus support pages have showed
me to the letter.
Click to expand...
Click to collapse
Every phone have boot. Img system . I also have a same fault redmi k20 pro. But i succeed to give rebirth it. Try to using fastboot commands only and flash fastboot flash boot boot. Img it will work definitely
HTC One M9
Android 6
Bootloader Locked
S=On
USB debugging disable
today I found my phone stock on decryption screen! I did not enable encryption mode. now my phone says: your phone is encrypted. to decrypt your phone, enter your Screen lock password.
it does not matter what number I enter! every number I enter, it says: Decryption unsuccessful. the password you entered is correct, but unfortunately, your data is corrupt. to resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account.
But nothing happened when I press the "reset phone" button. I waited 4 hours but it remains on a window named "Factory data reset, Rebooting..." but it can not proceed to reboot.
when I power off and go to bootloader, I can not go to recovery mode. on recovery mode, there is only a triangle with a red exclamation mark.
I download a stock ROM so I can flash it to my phone from download mode, but at the beginning of flashing process it comes with this error
12 RU_ZIP_ERROR
please help me
sjmahmoudi said:
HTC One M9
Android 6
Bootloader Locked
S=On
USB debugging disable
today I found my phone stock on decryption screen! I did not enable encryption mode. now my phone says: your phone is encrypted. to decrypt your phone, enter your Screen lock password.
it does not matter what number I enter! every number I enter, it says: Decryption unsuccessful. the password you entered is correct, but unfortunately, your data is corrupt. to resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account.
But nothing happened when I press the "reset phone" button. I waited 4 hours but it remains on a window named "Factory data reset, Rebooting..." but it can not proceed to reboot.
when I power off and go to bootloader, I can not go to recovery mode. on recovery mode, there is only a triangle with a red exclamation mark.
I download a stock ROM so I can flash it to my phone from download mode, but at the beginning of flashing process it comes with this error
12 RU_ZIP_ERROR
please help me
Click to expand...
Click to collapse
This problem has been posted from time to time by other users - it often indicates a corrupt chip in the motherboard.
Depending on your SKU and whether or not there really is a hardware issue or not, it may be possible to apply a RUU, which would effectively restore your phone to factory state (though it will wipe your internal memory).
Please post your OS version, which will help us determine your phone's SKU.
If you put the phone in download mode and plug it into a pc then run fastboot.exe with the cli command 'fastboot getvar all' you will get a lot of important information.
If you are absolutely sure your phone has never been modified and it shows on the fastboot output "status modified" then you can assume your phone has hardbricked from a faulty nand. Only HTC can fix it in the case.
Beamed in by telepathy.
computerslayer said:
this problem has been posted from time to time by other users - it often indicates a corrupt chip in the motherboard.
Depending on your sku and whether or not there really is a hardware issue or not, it may be possible to apply a ruu, which would effectively restore your phone to factory state (though it will wipe your internal memory).
Please post your os version, which will help us determine your phone's sku.
Click to expand...
Click to collapse
os: 3.35.401.32
shivadow said:
If you put the phone in download mode and plug it into a pc then run fastboot.exe with the cli command 'fastboot getvar all' you will get a lot of important information.
If you are absolutely sure your phone has never been modified and it shows on the fastboot output "status modified" then you can assume your phone has hardbricked from a faulty nand. Only HTC can fix it in the case.
Beamed in by telepathy.
Click to expand...
Click to collapse
I rooted this phone when I first bought it. but 4 months ago I unroot it so I could update it's android to marshmallow. after unrooting, i receive the android update and everything was as normal as a fresh unrooted phone.
I was able to go to download mode when first my phone faced this problem. but now the download mode is not available
it says: failed to boot to download mode
press volume up or down to back to menu
this build is for
development purposes only
do not distribute outside of HTC
without HTC's written permission.
Failure to comply may
lead to legal action.
computerslayer said:
This problem has been posted from time to time by other users - it often indicates a corrupt chip in the motherboard.
Depending on your SKU and whether or not there really is a hardware issue or not, it may be possible to apply an RUU, which would effectively restore your phone to factory state (though it will wipe your internal memory).
Please post your OS version, which will help us determine your phone's SKU.
Click to expand...
Click to collapse
I took my m9 to HTC service center. he said that main chip must be replaced. after replacing the chip, he said that I need a dump.bin file and I do not have it. now after 3 months, my dear m9 is still on the service center . I search all over the net for the dump.bin file but there is nothing at all.
I do not even know what the hell is the dump.bin file. he said that your phone can boot but it will not have antenna without relevant dump file. I'm confused please help me
my phone model ID: 0PJA100
Did you give your phone to an official HTC service center? HTC should have the needed file so the fact that you should provide it to the service center confuses me a bit.
It's impossible to get that file (from a working phone) without a JTAG device and I doubt that many M9 owners have one since they're quite expensive. Sorry for the bad news.
Greetings to all XDAdevelopers community. Please sorry me if that queiston was discussed. I can't find ANY solution of that problem.
I don't even know where to start.
I woke up in the morning, turned on my HTC One M9 and saw: "Your phone is encrypted To decrypt your phone, enter your screen lock password"
Of course I did not do ANYTHING including encryption etc....
By the power of my mind i decided to try to enter the password "0000" (Four zeros). The next phrase was: Decryption unsuccessful. The password you entered is correct, but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your google account.
There was an inscription below stated: "Reset phone"
I clicked "Factory reset" Factory data reset - rebooting ..... That is ALL. Rebooting for about 30 minutes and nothing happens.
I was advised (another forum) to reflash my firmware. (Using SD-card)
I clicked VolumeUP+VolumeDown+Power Button - Reboot to download mode (I have attached a picture below)
The phone saw my SD-card (I have attached a picture below) and the firmware which I uploaded and renamed to my SD-card.
I clicked "Press VolUp to start flash"
"HTC download mode" - written red letters - "Start UI updating'' --- After that the phone is rebooting - HTC letters on a black background - vibration - screen is out - HTC letters on a black background - vibration - screen is out - HTC letters on a black background - vibration - screen is out .... And so on and so on and so on infinitely.
The Question: Could anyone give me an explanation about that issue? I can't find any information about it. I don't know what I should do.
Please sorry for grammar mistakes and incorrect grammar sentence construction sometimes. English is not my native.
Kind regards.
P.S. I have deleted pictures due to forum restriction. I don't have 10 messages.
S-off or s-on?
Did you flash the same firmware version as what was already on the phone?
Any error messages?
Is the phone still responding?
shivadow said:
S-off or s-on?
Did you flash the same firmware version as what was already on the phone?
Any error messages?
Is the phone still responding?
Click to expand...
Click to collapse
Thank you for the respond.
Of course I did flash the same firmware version that was already on the phone previously. I did it not long time ago (I had "google app" error). I exclude "wrong version firmware error" from my side.
The phone is responding to what I have attached on the pictures. I tried to go to recovery mode and made "Wipe data factory" the phone said "error SD is not mounted" or something in that way.....
I went to the service center. They told me eMMC is dead.
Is the google account recoverable to another device using the same password?.
If the phone boots to download mode try flashing from another sd card.
Double check the md5 is correct and that the firmware is EXACTLY the same as the one the phone is currently running. It is important. If not then find another source.
If you get fail90 then flash again and again until successful.
If this steps have been done then your phone will be faulty.
Those pictures would have helped..
shivadow said:
Is the google account recoverable to another device using the same password?.
If the phone boots to download mode try flashing from another sd card.
Double check the md5 is correct and that the firmware is EXACTLY the same as the one the phone is currently running. It is important. If not then find another source.
If you get fail90 then flash again and again until successful.
If this steps have been done then your phone will be faulty.
Those pictures would have helped..
Click to expand...
Click to collapse
Shivadow, thank you for helping me! Yes I did it. Phone is dead.
Kind regards
My HTC ONE M9 is giving me the "Your phone is encrypted" message.
It says that i must enter my screen lock password to decrypt my phone.
Firstly i did not have a screen lock on my phone.
Secondly it happened all of a sudden