Related
Hi all,
I have had my N1 for 1year and two weeks now (yes, warranty just expired). I was charging the device and it seemed to overheat and reboot. I unplugged it, took the battery out, let it rest for a bit and tried to boot it again. The phone now gets stuck on the X logo (not moving) and never boots.
I'm currently abroad (in the UK) and can't have it sent back for repair (I'd have to pay the repair too).
Will rooting the phone and installing an alternate OS fix my phone?
Is there any way to get HTC to honor the warranty after two weeks of expiration (I've been getting this problem for a while now, but that was only an issue if I made extensive use of the device while charging, which I almost never do so I didn't bother.)
Is there any way to fix this issue without messing with rooting? I'm abroad right now and all I want is my phone to work.
Any suggestions are welcome.
Try booting into bootloader from power off (vol- pwr) if that doesn't work then try the 3 figure salute (pwr vol- tb) your phone should boot into fastboot then just select bootloader.
If either of these work the your good you can get the static x fixed all you need to do is passimg (search wiki if you don't know what it is) as for the charging problem passimg will factory reset the phone so if that doesn't fix it then no you'll need to try rooting or it might be hardware.
Yes, I'm able to go into the bootloader.
I tried clearing the storage, choosing fastboot, etc. The phone seems to be working, just won't boot past the static X.
From your last reply, you're saying passimg has good chances to fix my phone. What does that involve? Do you have a link to a how-to that I could follow (it would really be a bad time for me to brick my phone, a good how-to would be really appreciated).
Cheers!
Yes passimg is used for many things it just reflashes a shipment ROM to the phone through bootloader. Like I said you can visit the wiki to have a how to here is a link http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_%26_Tutorials scroll down to "Unroot / Restore your Nexus" then follow the instructions. This should restore you to frg33 then you just need to update back to 2.3.4.
NOTE: this will wipe your data.
Ahh there's a way to unroot the nexus one now!
I had no idea! This is good to know (last time I checked was in December I think).
I will give that passimg a try as soon as I get home.
Can anyone confirm that this ("Attention: Latest stock ROMs don't flash using PASSIMG.ZIP method. Use the provided latest Froyo PASSIMG, and upgrade it after flashing.") means I can still reflash using this if I have the latest ROM (2.3.4) but will simply have to update again after (which I might not do given the issues I'm facing).
Cheers!
Confirmed - Dude is giving you good info... xD
Just to verify, unrooting is not the same as relocking. If you unlocked your bootloader (have a little lock symbol under the X screen), there is no way to relock it.
But the passimg is a good option. It will take you back to an older version of Android, and then you just let the system update itself.
Since you are out of your warranty, I can highly suggest looking into custom firmwares. These give you a lot more features and in many cases, perform better. CyanogenMod is probably the most popular one. These will fully replace your Android OS. CyanogenMod really doesn't even differ in look from stock all that much. Most people probably wouldn't even have a clue they are running something different, except for the stability and performance increases.
You can read up about this stuff in the wiki as well.
Oh, I see, thanks for the info.
I'm actually trying to get the FRG83 passimg file but the link is dead. Does anyone have an alternate one?
Use the FRG33 image
Alright,
I unlocked the device, used fastboot to write the recovery "Amon_Ra's Recovery".
Then I rebooted, went to the bootloader (trackball + power), went to "recovery" but the phone still gets stucked on the X (with the unlocked padlock logo).
Any advices?
Try the passimg, but it's possible that you are looking at hardware failure...
ldiamond2 said:
Alright,
I unlocked the device, used fastboot to write the recovery "Amon_Ra's Recovery".
Then I rebooted, went to the bootloader (trackball + power), went to "recovery" but the phone still gets stucked on the X (with the unlocked padlock logo).
Any advices?
Click to expand...
Click to collapse
If you are still running stock Android, you can't reboot between installing the recovery and getting into it. Stock Android will replace it. Try to go back to the bootloader and select recovery then, or fastboot to load the recovery, and then use fastboot to boot off of it.
Code:
fastboot flash recovery "c:\location to\recovery.img"
fastboot boot recovery "c:\location to\recovery.img"
Hopefully this will get you into Amon_RA so you can try again.
But the passimg method is used in the bootloader, not in recovery. You don't need a custom recovery to use the passimg method.
Amazing, thanks for pointing out my mistake, that give me a little bit of hope now . (I was at the point where I'd open the thing and look for a broken solder joint.)
I will try this as soon as I get home!
**Edit** I actually am not sure if I really rebooted or went straight to recovery. I'll update this thread tonight.
According to some other people, this would be a common issue with the internal memory dieing.
Is there a utility I can use to check the state of the memory?
None that I know of. Our phone internal memory uses the yaffs2 (Yet Another Flash File System v2) file system. I haven't heard of any programs that can check it.
Same situation
Hello, all. I haven't signed in on here in ages just because I've been so happy with how my Nexus has been running.
I ran into the same problem as OP stated.
I think I have some sort of hardware issue because my phone used to randomly freeze and couldn't be restarted unless I pulled the battery. Now it's at the point where I can't even turn it on because nothing happens when I press the power button or if I try to boot into recovery. This is really frustrating.
Is there any way to check for hardware damage? My warranty is over as well so I'd have to pay for any repairs to my phone if I sent it in.
If it's running, you can try to pull a log, and see what error reports you get?
andythefan said:
Now it's at the point where I can't even turn it on because nothing happens when I press the power button or if I try to boot into recovery. This is really frustrating.
Click to expand...
Click to collapse
Your power button might just be dead. Try having the phone plugged into a power source and removing and reinserting the battery. While you are doing that, hold the Volume Down button. This will get you into the bootloader which would allow a passimg to be performed. Hopefully your reboots aren't a hardware problem.
So , after pulling my battery, pulling the sim and the sd card, it finally turned on and went to recovery without freezing. I was able to wipe and reflash cyan 7. It's working well for now, but I'm really afraid this is going to happen again because this isn't the first time that it's just froze repeatedly.
Does anyone know what the problem could be?
Alright,
I did "fastboot flash recovery MYIMG" then "fastboot boot MYIMG", didn't work.
Then I tried "fastboot flash recovery MYIMG" then go to bootloader (without rebooting) and selected recovery.
Still no luck.
It always freezes on the static X logo. What else can I do? Will using passimg be any different (I don't have any way to put the file on the micro SD card but I can manage to do it if it's worth the shot).
Thanks
So this is my first xda thread. I spent hours searching without finding a solution for my particular case.
I am using a LG L90 D415 (T-Mobile version) and I got bored of it and so I started playing with the system (not the first phone I'm doing that with, so I know a bit about that sutff). So I tried to install the new Android L home launcher from here http://forum.xda-developers.com/showthread.php?t=2796019
I did everything like explained, installed it and changed the build.prop like described. But after I rebooted my phone, expecting a new home launcher, the phone boots, I am at the lockscreen, but after like 4 seconds I receive multiple errors (like gapps stopped working) and than everything freezes and it reboots.
Unfortunaly I didn't install a recovery or unlocked fastboot. So I can access download mode, but that's it. My computer doesn't see my phone (because usb debugging deactivated?) and so I don't know what to do. I think that's a pretty tough case but I hope some smart person can help me
Thank you
mcfiish said:
So this is my first xda thread. I spent hours searching without finding a solution for my particular case.
I am using a LG L90 D415 (T-Mobile version) and I got bored of it and so I started playing with the system (not the first phone I'm doing that with, so I know a bit about that sutff). So I tried to install the new Android L home launcher from here http://forum.xda-developers.com/showthread.php?t=2796019
I did everything like explained, installed it and changed the build.prop like described. But after I rebooted my phone, expecting a new home launcher, the phone boots, I am at the lockscreen, but after like 4 seconds I receive multiple errors (like gapps stopped working) and than everything freezes and it reboots.
Unfortunaly I didn't install a recovery or unlocked fastboot. So I can access download mode, but that's it. My computer doesn't see my phone (because usb debugging deactivated?) and so I don't know what to do. I think that's a pretty tough case but I hope some smart person can help me
Thank you
Click to expand...
Click to collapse
No custom recovery and no fastboot? Factory reset is your only option. See this post. Scroll down to Q14. Even though it's titled something else, the same button presses apply for your device in it's current state, ie; no recovery, no fastboot
shinobisoft said:
No custom recovery and no fastboot? Factory reset is your only option. See this post. Scroll down to Q14. Even though it's titled something else, the same button presses apply for your device in it's current state, ie; no recovery, no fastboot
Click to expand...
Click to collapse
First thanks for the fast answer. So I figuered that I only need to delete the build.prop file and replace it with my backup file. Isn't there any way to rescue my files and/or access the /system folder? I'm an exchange student now and I don't wanna lose my picture memories
And btw I know that I build the perfect worst case scenario right now
Oh and in the L90 faq it says that when you flashed a recovery and you navigate to factory reset it won't reset but boot into recovery. Does something like this work even without recovery, so I could try doing stuff with adb?
mcfiish said:
First thanks for the fast answer. So I figuered that I only need to delete the build.prop file and replace it with my backup file. Isn't there any way to rescue my files and/or access the /system folder? I'm an exchange student now and I don't wanna lose my picture memories
And btw I know that I build the perfect worst case scenario right now
Click to expand...
Click to collapse
If adb isn't detecting the phone, no. There isn't any other way.
mcfiish said:
Oh and in the L90 faq it says that when you flashed a recovery and you navigate to factory reset it won't reset but boot into recovery. Does something like this work even without recovery, so I could try doing stuff with adb?
Click to expand...
Click to collapse
Unfortunately, no.
Factory reset will not erase your sdcard. It will however erase internal data. It will return the phone to the state it was in the first time it was powered on.
Hi everyone, I'm having a lot of problems with my phone: last night, after it dropped to 0% battery life, it wouldn't charge. So i waited a while and ifinally managed to turn it on, but It wouldn't go past the Cyanogenmod logo. So i tried few things,first wiping cache, then factory reset from TWRP and I even tried the "Factory" option in the fastboot screen. Nothing worked, and it even got worse I think, TWRP says it's unable to mount /data partition and /storage partition. I don't know what caused it, and i don't remember the precise moment it became "unmountable" for the first time (since I've been trying to fix this thing for like 24 hours now).
Since i couldn't fix it via recovery, I tried looking for people who had the same problem on the internet, and I tried everything i could find. (like this: http://forum.xda-developers.com/showthread.php?t=2683787).
I then tried to go back to stock rom via adb and fastboot, but without success.
The main problem with fastboot is the fact that it doesn't change anything in my phone, it gives no errors when i try to flash the stock rom, but when i reboot my phone, nothing changes, or at least this is my opinion, since I still get the cyanogenmod logo, and TWRP doesn't get replaced (while it should go away, since when in the whole process of flashing the rom, i also flash recovery.img, which shouldn't be TWRP).
I tried a whole lot of other commands too, like "fastboot erase recovery", but TWRP is still there, and so is the cyanogenmod logo.
This is why i think fastboot is unable to write in my phone, but if that's the case, it should at least give errors.
So, wrapping up, my data partition seems to be corrupted, and flashing the stock rom still gets my into a bootloop (with the logo from the previous rom and TWRP still there).
Do you have any advice?
P.S: my phone is a xt1068
Are you able to pull logcat?
Logcat command works, i don't get errors in the terminal, but in the text file there's only this line : "/sbin/sh: exec: line 1: logcat: not found"
Dmesg works though, I don't know if it's helpful
"
dagrot said:
I then tried to go back to stock rom via adb and fastboot, but without success.
The main problem with fastboot is the fact that it doesn't change anything in my phone, it gives no errors when i try to flash the stock rom, but when i reboot my phone, nothing changes, or at least this is my opinion, since I still get the cyanogenmod logo, and TWRP doesn't get replaced (while it should go away, since when in the whole process of flashing the rom, i also flash recovery.img, which shouldn't be TWRP).
I tried a whole lot of other commands too, like "fastboot erase recovery", but TWRP is still there, and so is the cyanogenmod logo.
This is why i think fastboot is unable to write in my phone, but if that's the case, it should at least give errors.
So, wrapping up, my data partition seems to be corrupted, and flashing the stock rom still gets my into a bootloop (with the logo from the previous rom and TWRP still there).
Do you have any advice?
P.S: my phone is a xt1068
Click to expand...
Click to collapse
I have same phone, you mentioned you also tried to flash stock rom without success, did you flash the partition file aswell before flashing system and the rest of files ? Check the flashfile.xml file into the stock firmware folder to make sure you not missing anything.
Code:
fastboot flash partition gpt.bin
Good luck.
i'm on the same boat. It seems it's a NAND issue, but how come it happens randomly?
It seems to happen (its a bit rare, so don't get worried) when you let your battery drop to 0% and the phone suddently turn off, like what happened to the OP.
Sent from my XT1063 using XDA Free mobile app
Lynse said:
It seems to happen (its a bit rare, so don't get worried) when you let your battery drop to 0% and the phone suddently turn off, like what happened to the OP.
Sent from my XT1063 using XDA Free mobile app
Click to expand...
Click to collapse
If it's a bit rare, how come there are a rather interesting quantity of posts regarding that matter? I'd like to know WHY I can't write even with fastboot. There should be a way of unlocking the NAND / partitions. Even if I try to hard brick it, it's impossible.
PS: can we someone a look at this? http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
Possibly if we can force the way to QHSUSB mode, phone can be saved.
jhonnyx said:
PS: can we someone a look at this? http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
Possibly if we can force the way to QHSUSB mode, phone can be saved.
Click to expand...
Click to collapse
Unfortunately I didn't quite understand what that is about, if you happen to try it out let us know.
Anyway, if we don't manage to fix it, I guess I'm going to try and take it back to the store, since it is a common problem. Only problem is I'm on a custom rom and I can't even go back to stock and relock the bootloader, so I don't think they are going to replace it, but it's worth a try.
You can try by helping me to look for a circuit PDF from the board or trying it yourself.
I could try and disassemble it, but you're gonna have to wait a few days, I'm not at home and I'm gonna be back on the weekend.
As for the circuit pdf, I was only able to find videos and guides on how to disassemble it, unfortunately
Dude, no worries. Ive took the back out with all the screws, but I have nothng to make shorts with.... I'll come up with something. Take your time and keep me posted.
any news concerning this problem? i have tried searching for a manual but I did not succeed.
Anyways after finding the manual, we can short circuit the 2 capacitors there and the phone will be in qhsusb mode.
And after that ?
gbb14 said:
any news concerning this problem? i have tried searching for a manual but I did not succeed.
Anyways after finding the manual, we can short circuit the 2 capacitors there and the phone will be in qhsusb mode.
And after that ?
Click to expand...
Click to collapse
After that.... well.... after some research, we'll be needing singleimage.bin to use the blankflash utility for lollipop phones (mbm-ci 5.0 lollipop) so somebody can generate the singleimage.bin for us.
Once we have that, we can try to flash the phone at lowlevel to see what happens.
I will search the internets in hoping to find the schematics of this phone.
Keep me informed if you find it faster .
Cheers mate
we can connect through hangouts / etc.
look up for my user at gmail
Moto X 2014: unrooted with bootloader unlocked. It's running Stock 5.1 and I haven't messed with anything on it. I gave it to my Dad after a few months of using it, so I factory reset it and gave it to him, 2 weeks later he tells me it has stopped working. It boots up normally, but from then on it is black, I can access minor parts of the OS such as the power off menu, the camera (by shaking) and Moto Display, but everything else doesn't work. I have never seen anything like this before, and I am well accustomed to flashing custom ROMs and rooting Android. If it comes down to it I will factory reset it or flash stock, but I can't even plug it into my PC and retrieve any files. Anyone have any idea whats gone wrong?
I have attached a video demonstrating what's happened to help diagnose the problem.
thomaswilloughby said:
Moto X 2014: unrooted with bootloader unlocked. It's running Stock 5.1 and I haven't messed with anything on it. I gave it to my Dad after a few months of using it, so I factory reset it and gave it to him, 2 weeks later he tells me it has stopped working. It boots up normally, but from then on it is black, I can access minor parts of the OS such as the power off menu, the camera (by shaking) and Moto Display, but everything else doesn't work. I have never seen anything like this before, and I am well accustomed to flashing custom ROMs and rooting Android. If it comes down to it I will factory reset it or flash stock, but I can't even plug it into my PC and retrieve any files. Anyone have any idea whats gone wrong?
I have attached a video demonstrating what's happened to help diagnose the problem.
Click to expand...
Click to collapse
If you search the forum here for "black screen" it has happened to other people as well on stock 5.1. Supposedly the fix is a factory reset.
Sent from my XT1095 using Tapatalk
AGISCI said:
If you search the forum here for "black screen" it has happened to other people as well on stock 5.1. Supposedly the fix is a factory reset.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Ok, It was just really surprising thats all. I will factory reset then. Thanks
I am having the exact same issue. Have you had a luck resolving it short of a factory reset?
My phone battery died last night. I plugged my phone in, let it get about 15% charge, then tried to turn it back on. The phone boots like normal, but after the boot animation goes away, the screen is black. Active notifications still seem to work, and I can hold the power button to get the Power Down option. I can boot into the bootloader & access recovery just fine. However, my phone is fully stock (no root, no bootloader unlock, no anything). I can't seem to access ADB when the phone is powered normally (ie, when I'm at this mysterious black screen), but it's possible that USB debugging isn't even enabled.
So far, I've found a few people who've said a full factory reset will fix the problem, but I'm looking for another solution, or at least a way to grab my data before I reset. Since my bootloader's still locked, I can't seem to use fastboot boot to boot into TWRP, and I can't find any other way to access my data to copy it off the phone. I've tried wiping the cache using the stock recovery to no avail. Any suggestions?
bjg222 said:
I am having the exact same issue. Have you had a luck resolving it short of a factory reset?
My phone battery died last night. I plugged my phone in, let it get about 15% charge, then tried to turn it back on. The phone boots like normal, but after the boot animation goes away, the screen is black. Active notifications still seem to work, and I can hold the power button to get the Power Down option. I can boot into the bootloader & access recovery just fine. However, my phone is fully stock (no root, no bootloader unlock, no anything). I can't seem to access ADB when the phone is powered normally (ie, when I'm at this mysterious black screen), but it's possible that USB debugging isn't even enabled.
So far, I've found a few people who've said a full factory reset will fix the problem, but I'm looking for another solution, or at least a way to grab my data before I reset. Since my bootloader's still locked, I can't seem to use fastboot boot to boot into TWRP, and I can't find any other way to access my data to copy it off the phone. I've tried wiping the cache using the stock recovery to no avail. Any suggestions?
Click to expand...
Click to collapse
Unfortunately I couldn't retreive any data from the phone, I can confirm however that a factory reset does fix the issue. The Android automatic backup does work in the broken state so I did manage to restore my settings and apps. But the internal sd card was wiped upon factory reseting. Just an idea of the top of my head: Try running adb backup and see if that works, and then unlocking the bootloader, flashing twrp, restoring the backup, and finally transfering the internal sd card data to a mounted drive using twrp. Thats just a stab in the dark and i dont have the phone on me to test it. Give it a try and lets hope Motorola will fix this bug soon.
Ok, thanks. I did try adb backup, but adb won't recognize the device when it's "booted" & sitting at the blank screen, and the stock recovery doesn't give full adb access. I'm currently looking into the various data recovery options to maybe pull some stuff off after reseting. It's really only a few files that I need, so maybe that will work?
bjg222 said:
Ok, thanks. I did try adb backup, but adb won't recognize the device when it's "booted" & sitting at the blank screen, and the stock recovery doesn't give full adb access. I'm currently looking into the various data recovery options to maybe pull some stuff off after reseting. It's really only a few files that I need, so maybe that will work?
Click to expand...
Click to collapse
Unfortunately the internal SD card mounts using MTP and not like a flash drive, so using the usual methods through Windows to recover wont work. However you could try and restore your internal sd card using this solution: http://goo.gl/OKdV14
As for accessing adb through recovery, you could try this method: http://goo.gl/5T7bhq
Hopefully one of these methods should work, so you can at least recover some of your files.
I had the same problem today. I tried to backup a twrp backup I have made few weeks ago but I still had the black screen. The only solution is to factory reset...
Happily I could have saved my data when I was on TWRP. Anyone knows how to restore sms from the data I have saved ?
Hey people, I have been on this forum and using the CM12.1 ROM by New Maclaw since it came out, but I'm afraid my S3 Mini is dead now Saturday night it turned off by itself while charging, and it wouldn't turn on again. I let it charge a little, and after a while it turned on again, but was stuck on the CM12.1 boot animation. I tried rebooting multiple times, but it always got stuck on the boot animation. I tried booting into TWRP, but it got stuck on the Galaxy SIII Mini splash screen and wouldn't even go any further.
I was getting my hopes up when I saw download modus still working, so I flashed TWRP again with Odin, but nothing changed. I flashed the entire CM12.1 package again with Odin, but it had no effect whatsoever, can't boot into TWRP and regular boot is stuck on CM boot logo.
Since I had no options left, I decided to follow this guide: [GUIDE] Unroot / Unbrick, Flash official stock firmware on Galaxy SIII Mini GT-I8190 to flash original ROM again, first flashing the original recovery as linked in the thread, then the ROM itself, and checking after each step if anything changed. But even after I flashed the stock ROM, it would show the CM 12.1 boot animation on boot, and recovery was still not working at all. I continued by flashing the params.tar as linked in the post, but my phone still shows the CM 12.1 boot animation, and I can't get any further
What's really concerning to me is the fact that all the flash operations via Odin are going through, I get a PASS every time, but it doesn't seem to have any effect, so I'm afraid the memory chip on my phone has died There are so many great minds in here that know everything about this phone, maybe someone has an idea to help me get my trusted S3 mini back
Super weird. It's not soft bricked, it's completely f#cked up:laugh: OK, have you tried to remove the battery for some minutes!? Or go in recovery through adb instead!? If you have a backup (that's why, we always need a backup) maybe you can restore it through adb. Search on XDA for adb tutorials or something like that or some case like yours. I want to believe that you're not the first one with that issue. I know that's frustrating when we don't know what's going on. Good luck
mauam said:
Super weird. It's not soft bricked, it's completely f#cked up:laugh: OK, have you tried to remove the battery for some minutes!? Or go in recovery through adb instead!? If you have a backup (that's why, we always need a backup) maybe you can restore it through adb. Search on XDA for adb tutorials or something like that or some case like yours. I want to believe that you're not the first one with that issue. I know that's frustrating when we don't know what's going on. Good luck
Click to expand...
Click to collapse
I don't really care about backups, all my important data is on the SD anyway, I just want to bring the phone back to life if possible at all.
While on the CM12.1 boot screen I can find the phone with adb, but since I never set up adb my computer is unauthorized, and I can't authorize it without being able to boot. I'm not all that familiar with adb, I asked some people, but nobody has an idea how I can authorize my computer without having access to the phone system.