So my nexus one froze today, and now whenever I pull the battery and put it back in, it will vibrate 7 times and wont boot. Is it bricked, or what can I do to fix this?
Thanks
What were u doin when this happened and what does the boot animation come up
Sent from my Nexus One using XDA App
I opened up the navigation app and it froze. Puller the battery and had that problem. I then decided to pull the battery, press the power button a few times to discharge the phone and it booted back up. So hopefully it wont happen again
Same thing happened to me. I was experimenting with an undervolted kernel which up until then had been behaving well. Received a bunch of texts and notifications simultaneously. By the time I got to my phone, it had gone to sleep. I was able to power on, but the screen was completely unresponsive. The powering on was also very delayed. I couldn't shutdown with the power button so I pulled the battery.
It could only do a 7-vibrate boot/freeze every single time I pulled the battery and replaced it. Finally, with the above advice, I left it out for several minutes, hit the power button a few times, then replaced the battery and got it to finally boot.
This happened to me today too, I took out my SD and it booted up just fine after that..not sure what happened. I checked my SD for errors but it didn't have any and had no problems after I put it back in.
hmm havent faced these errors yet, have u modded the rom at all?
mine just did it now when i changed the sd card.
taking the card out doesn't help.
i'm guessing it thinks the battery is flat or something similar, will try charging.
edit: just kept trying and it eventually worked.
I have the same problem, hitting the power button does nothing, I leave the battery out for ~ 5 minutes and eventually get a fastboot screen and 7 times vibrate, but no control, power button, volume and trackball not working. I have to pull the battery out, wait another 5 minutes or so and try again.
Does anyone have a clue about what that 7 times vibrate means? sounds like an error code.
If after have pulled out the battery for 5 minutes I keep pressed the volume down and the power, I eventually have a fastboot working screen, but choosing recovery from the menu takes me back to the fastboot screen with 7 times vibrate. Taking the card out or the sim does not make a difference.
How did I get here: Was using Cyanogen 2.2, rooted, screen froze one day, pulled the battery out and here I am.
Tried to do a reset with volume down and power, it freezed during the procedure and now it won't boot at all.
I'm still able just to start in fastboot. Recovery and clear storage do nothing useful. Booting normally gives me the nexus logo for a while and then the screen blanks after a few seconds.
I can do fastboot flash boot, but I can't do fastboot flash system, it just says sending and that's it:
Code:
[[email protected] apps]# ./fastboot erase userdata
erasing 'userdata'... FAILED (remote: not allowed)
[[email protected] apps]# ./fastboot erase cache
erasing 'cache'... OKAY
[[email protected] apps]# ./fastboot flash boot Passion\ Google\ WWE\ 1.01.1700.1_ERD79/boot.img
sending 'boot' (2044 KB)... OKAY
writing 'boot'... OKAY
[[email protected] apps]# ./fastboot flash system Passion\ Google\ WWE\ 1.01.1700.1_ERD79/system.img
sending 'system' (116663 KB)...
Any ideas anyone ?
alexxed said:
I'm still able just to start in fastboot. Recovery and clear storage do nothing useful. Booting normally gives me the nexus logo for a while and then the screen blanks after a few seconds.
I can do fastboot flash boot, but I can't do fastboot flash system, it just says sending and that's it:
Code:
[[email protected] apps]# ./fastboot erase userdata
erasing 'userdata'... FAILED (remote: not allowed)
[[email protected] apps]# ./fastboot erase cache
erasing 'cache'... OKAY
[[email protected] apps]# ./fastboot flash boot Passion\ Google\ WWE\ 1.01.1700.1_ERD79/boot.img
sending 'boot' (2044 KB)... OKAY
writing 'boot'... OKAY
[[email protected] apps]# ./fastboot flash system Passion\ Google\ WWE\ 1.01.1700.1_ERD79/system.img
sending 'system' (116663 KB)...
Any ideas anyone ?
Click to expand...
Click to collapse
Since you said you were using CyanogenMod, I will assume you are using CM6 RC2 not that it matters now. So you are running a custom recovery right? Try to wipe everything, data, cache, and the dalvik cache. Then flash a different ROM, either stock or any other really to see if that helps.
edited.
sent back to HTC
There are a batch of n1 that has this problem. I had bought a new att 3g version in june and returned it for a new. I also had the booting problem. It would constantly reboot or be stuck at the nexus boot logo. Its a hardware issue. Call google and they will transfer you to htc and work out a exchange or repair for you.
Sent from my GT-I9000 using XDA App
Vakman said:
Since you said you were using CyanogenMod, I will assume you are using CM6 RC2 not that it matters now. So you are running a custom recovery right? Try to wipe everything, data, cache, and the dalvik cache. Then flash a different ROM, either stock or any other really to see if that helps.
Click to expand...
Click to collapse
I'm trying to flash the stock image following the instructions here: #614850
Flashing hangs in various steps of flashing system.img, so I tried repeatedly until I succeeded, but still no success in booting afterwards, so I suspect I need to match the radio with the system as I've read that the radio boots before system. Right now I have FRF50 (4.06.00.12_7).
The problem is that once I leave the phone off for a while with battery in, the phone does not start in any mode (power, power + volume down, power + trackball) until I leave it with battery out for 2-3 days after which I can boot in any of the three modes above, the power button shows the nexus logo for a few seconds than the image scrambles and the phone goes off. If I choose to go in recovery I see the nexus logo forever.
Fastboot works, but as said, it hangs when flashing about 90% of the time.
I'll keep trying as sending off the phone for repair is a tricky option considering that I'm not in US, I haven't bought the phone from US, and so on.
Ive had this problem for awhile. It first started when i updated to froyo. I called htc Tech support an they told me it was probably caused by an app but i dont know if thats true or not. Iam curious to know what the 7 vibrations mean
In case you can't/don't want to send it back for warranty repair, it seems that leaving the phone charging for 12-24 fixes the issue (though it might look dead during those hours).
maxdadev said:
In case you can't/don't want to send it back for warranty repair, it seems that leaving the phone charging for 12-24 fixes the issue (though it might look dead during those hours).
Click to expand...
Click to collapse
Tried that and almost anything I could have imagine. Finally I sent the phone to HTC and they were kind enough to repair it free of charge, I only paid for the shipping to them, they paid the shipping back.
The interesting part is that I got the same phone (it has the same IMEI), but locked again, so I guess that means there is a way to lock the phone back.
I hate to revive an old thread, but it's probably better than making a new one about the same issue.
A friend of mine said this happened on his Nexus and now it won't boot past the "X" splash screen, and it vibrates 7 times. He gave it to me to try to fix, and I've done everything I can think of. When I try to use a PASSIMG.zip through Hboot the progress bar on the side fills, then it says "Checking PASSIMG.zip," but then it just returns to the Hboot screen.
I've tried using Fastboot to install Amon_Ra's recovery and Clockworkmod recovery, even a radio update, but any .img file I try tells me "FAILED (remote: signature verify fail)"
Has anyone found a fix for this, or have any suggestions?
If I have to call Google/htc can I still have it replaced, even if the bootloader has been unlocked, voiding the warranty?
Thanks.
You have to unlock the bootloader to use fastboot.
I have unlocked the bootloader. It says ***Unlocked*** at the top, it's still S-ON though.
I can't access recovery or ADB to tell if it's rooted or not, either.
*** UNLOCKED ***
NEXUSONE PVT SHIP S-ON
HBOOT-0.33.0012
MICROP-0b15
RADIO-4.06.00.12_7
OK, that's weird then. I've never heard of fastboot failing before.
Related
Nexus One running 2.2 on T-Mobile.
I rooted yesterday using one of the one click root apps. This went fine.
I installed several apps from the marketplace for rooted phones.
These include: Titanium Backup, ROM Manager, Quick Reboot, Eris Market Fix and a boot animation replacer
I did a backup using the ROM Manager first. Named it 'Original'
I ran the Eris Market Fix which said it was successful but needed a reboot. I figured since I was rebooting I might as well mess w/ the animation. I opened the app but it was not immediately apparent how it works so I left it alone for the time being. I used the quick reboot app to reboot.
The phone rebooted, I saw the initial X but it won't go further. At the point where the animation should start it just goes blank. About a minute after that the screen lights up very faintly and the buttons at the bottom (home, etc) light up and it just sits there.
If I reboot it (holding power, volume down and the trackball) then hold the volume down button I can get to the bootloader screen. Options are: fastboot, recovery, clear storage, simlock.
If I select recovery I get the exclamation point w/ the little android guy and it just sits there. From there if I push the volume up and power buttons I get the android system recovery. Options are: reboot system now, apply sdcard:update.zip, wipe data/factory, wipe cache partition.
I tried most of the options in both of those screens to no avail.
I just now figured out how to connect to it using fastboot so I guess I need to do something there just not super sure how to proceed.
I'm thinking that if I can get it back to stock, root and install the ROM Manager then i should be able to restore the backup I made earlier, is this correct?
Thanks in advance for the help.
crickets_chirping.mp3
...
It looks as though I should be able to load a recovery image and restore the backup I made before the incident according to what I've read since the original post.
Question: Since the ROM Manager used Clockwork to make the backup do I need to use it as well? Does it matter?
I have half a mind to just throw CM on there but there is some data in the backup that I'd like to have backed up by Titanium rather than a ROM image.
OK, trying to get clockwork to flash.
I get this:
fastboot flash recovery recovery-clockwork-2.5.0.7-passion.img
sending 'recovery' (2906 KB)... OKAY [ 0.478s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.978s
Had to fastboot oem unlock first
Then tried to flash clockworkmod, said it was successful, rebooted and got the '!'
Flashed Superboot
Rebooted
Flashed clockworkmod again
rebooted
started recovery (finally!)
It is now restoring my earlier made backup. Hopefully it will work.
Thanks for all the help guyz!
Hey guys, I hope you can help me out with this one. Before I begin I just have to say that I was on factory image from Google + root.
So I was downloading a torrent, and in the mean time I was streaming a movie from an app. Suddenly I couldn't do anything, the movie kept on playing but I couldn't push any buttons or anything. So I held down the power button for about 15-20 seconds and then it powered of, but it booted it self again, by it self. But it got stuck at Google logo, so I powered it off again, but it kept trying to rebooting. Always stuck at Google logo. Weird. So I booted into bootloader and connected it to my pc. I came up with the idea that if I wipes cache and dalvik it will maybe boot. So I booted it into cwm, went down to advanced-> dalvik cache, then it just showed me the cwm icon and the background. And I tried the same a multiple times. No luck. So I booted it into twrp, but it got stuck on their logo. So my only option was to flash factory image from Google again. So I tried. Erased boot, cache, system, recovery, userdata. And then I were about to flash the bootloader. Yeah, in my dreams. I got this:
C:\Android>fastboot flash bootloader C:\Android\bootloader-grouper-4.13.img
sending 'bootloader' (2096 KB)... FAILED (remote: (Unkown error code))
finished. total time: 0.021s
I tried it a couple of times, but no luck. So I came up with another idea, maybe the supidest of them all. Relock and then unlock the bootloader again! Yay. Worst ever. I locked it, which went fine, then I was going to unlock it again and got this:
C:\Android>fastboot oem unlock
... INFOerasing userdata...
INFOerasing userdata done
INFOerasing cache...
INFOerasing cache done
INFOunlocking...
FAILED (remote: (Unknown error code))
finished. total time: 3.980s
Awesome. How am I supposed to flash the factory image now? I've tried to unlock it many times, without luck. And I can't try to boot it either since the boot.img is erased and I can't flash a new one.
Can anyone help me? I'm crying over here! I would be so happy if someone could help me out with this.
Thank you so much.
tjackbjorn said:
Hey guys, I hope you can help me out with this one. Before I begin I just have to say that I was on factory image from Google + root.
So I was downloading a torrent, and in the mean time I was streaming a movie from an app. Suddenly I couldn't do anything, the movie kept on playing but I couldn't push any buttons or anything. So I held down the power button for about 15-20 seconds and then it powered of, but it booted it self again, by it self. But it got stuck at Google logo, so I powered it off again, but it kept trying to rebooting. Always stuck at Google logo. Weird. So I booted into bootloader and connected it to my pc. I came up with the idea that if I wipes cache and dalvik it will maybe boot. So I booted it into cwm, went down to advanced-> dalvik cache, then it just showed me the cwm icon and the background. And I tried the same a multiple times. No luck. So I booted it into twrp, but it got stuck on their logo. So my only option was to flash factory image from Google again. So I tried. Erased boot, cache, system, recovery, userdata. And then I were about to flash the bootloader. Yeah, in my dreams. I got this:
C:\Android>fastboot flash bootloader C:\Android\bootloader-grouper-4.13.img
sending 'bootloader' (2096 KB)... FAILED (remote: (Unkown error code))
finished. total time: 0.021s
I tried it a couple of times, but no luck. So I came up with another idea, maybe the supidest of them all. Relock and then unlock the bootloader again! Yay. Worst ever. I locked it, which went fine, then I was going to unlock it again and got this:
C:\Android>fastboot oem unlock
... INFOerasing userdata...
INFOerasing userdata done
INFOerasing cache...
INFOerasing cache done
INFOunlocking...
FAILED (remote: (Unknown error code))
finished. total time: 3.980s
Awesome. How am I supposed to flash the factory image now? I've tried to unlock it many times, without luck. And I can't try to boot it either since the boot.img is erased and I can't flash a new one.
Can anyone help me? I'm crying over here! I would be so happy if someone could help me out with this.
Thank you so much.
Click to expand...
Click to collapse
Try a different cable or port first. Sounds like your solid state took a dump on that partition. Clean your charging port as well. Any of these may help. Does it show the charging animation when powered off? You can power all the way down through boot loader or battery pull (obvious).
Sent from my SGH-I747 using xda premium
gunz.jones said:
Try a different cable or port first. Sounds like your solid state took a dump on that partition. Clean your charging port as well. Any of these may help. Does it show the charging animation when powered off? You can power all the way down through boot loader or battery pull (obvious).
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Ok, I will try it. I doubt cleaning the port will help, but I will try it No it doesn't shows the charging animation when it's powered off.
I'll do anything exept a battery pull ^^
Sent from my super fast Prime filled with beans.
tjackbjorn said:
Ok, I will try it. I doubt cleaning the port will help, but I will try it No it doesn't shows the charging animation when it's powered off.
I'll do anything exept a battery pull ^^
Sent from my super fast Prime filled with beans.
Click to expand...
Click to collapse
My bad, forwarded from gnex thread. Hehehe....
Sent from my SGH-I747 using xda premium
Hmm.. Simms said that it could be a faultt storage.. I smell sending it to warranty ..
Sent from my Nexus Prime
thegtfusion said:
Hmm.. Simms said that it could be a faultt storage.. I smell sending it to warranty ..
Sent from my Nexus Prime
Click to expand...
Click to collapse
Same conclusion.
Sent from my SAMSUNG-SGH-I747 using xda premium
Ok... Thanks. I will talk to asus and see what they are saying.
Sent from my super fast Prime filled with beans.
My motorola Nexus 6 won't turn on, when I try to power it on, it shows the Google sign then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, it flashes fine but it still shuts off immediately while showing the google sign. It won't even boot into recovery after the flash, it just shuts off after the google sign. This isn't my first nexus, in know that flashing factory image should fix 99% of issues. Please help.
P.S I didn't purchase officially from google or Motorola, bought it from a guy who claimed he bricked it trying to install a font pack so I figured let me buy it and restore factory image. Didn't work. I tried flashing manually, the process went fine, but it it still turns off at google splash image. I tried Wugfresh toolkit also to no avail. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and it wouldn't boot past google screen after that. It doesnt even get to the boot animation. It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I spoke to my friend who has a local repair shop and he says there is nothing out for his z3x or his other boxes for the nexus 6 because it is such a new and rare device. His theory is that the partition tables have been corrupted somehow and need to be rewritten manually. Please any help would be appreciated. I can promise a hefty $$ reward for any individual that helps me recover it to a working state.
can you get a custom recovery on successfully.........?
did you flash the stock image manually?
mediaman123 said:
can you get a custom recovery on successfully.........?
did you flash the stock image manually?
Click to expand...
Click to collapse
Yes I tried pushing the stock recovery individually and it succeeded in the command prompt, but won't enter recovery, just shows google and shuts off. I tried pushing twrp too but same outcome. Yes I had flashed the stock image manually, everything flashed well from what the command promt said, but when it should reboot to recovery after flash to wipe, just shuts off.
jeromechrome1 said:
Yes I tried pushing the stock recovery individually and it succeeded in the command prompt, but won't enter recovery, just shows google and shuts off. I tried pushing twrp too but same outcome. Yes I had flashed the stock image manually, everything flashed well from what the command promt said, but when it should reboot to recovery after flash to wipe, just shuts off.
Click to expand...
Click to collapse
Please! Anyone!
by manually do you mean flashing all the separate parts of the stock image separately, system, boot, recovery, cache and so on..........
I don't know what else to do after going through with that process.....
Make sure you have the latest fastboot by updating SDK Manager. Then reflash bootloader then reboot back to bootloader to reset. Then proceed to flash each partition again. Directions below.
fastboot flash bootloader bootloader.img <-- rename bootloader to this to make it easier
fastboot flash radio radio.img <--- again rename to make easier
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fasyboot flash system system.img
Hope this helps.
I'm a total newb here so take what I tell you with a grain of salt. I had your exact same problem on my Nexus 5. Every single thing you just described is what happened to my N5. And just like your N6...I was able to boot up into recovery (stock and TWRP), I was able to flash all the things manually and even used Wug's NRT. But then whenever I tried to actually boot up the device it could never pass the Google logo....basically EVERYTHING THAT IS HAPPENING TO YOU.
What I did to fix everything? Changed my battery. Sounds stupid and totally irrelevant but that did the trick. When I opened up my phone I noticed my battery had a nasty bulge and realized it was defective. Bought a new one for $25 and have never had any issues ever since. I suggest you look at your battery and see if that is the root of your problem. I have heard of the N6 having some batteries expanding and causing the back covers to pop off...this could be related to your problem.
Like I said I am a newb and thought I'd share my experience in the hopes it solves your problem.
Good luck buddy! :good:
my N6 is actually away getting repaired for the exact issue you described, expanding battery [assumed], and cover coming away from the bezel.....
I believe though that if you keep the device plugged into the wall when trying to boot up with this battery defect it will get through the boot, at least in the beginning anyway....
I believe also that if it was a battery issue the device would power off first, as opposed to just sticking on the Google logo.........
ldkud50 said:
Make sure you have the latest fastboot by updating SDK Manager. Then reflash bootloader then reboot back to bootloader to reset. Then proceed to flash each partition again. Directions below.
fastboot flash bootloader bootloader.img <-- rename bootloader to this to make it easier
fastboot flash radio radio.img <--- again rename to make easier
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fasyboot flash system system.img
Hope this helps.
Click to expand...
Click to collapse
I tried all of that already bro, it takes the files fine i did each individually including the bootloader. yes i have the latest sdk and latest fasboot. same issue no matter what i try. thank you all for ur help so far, really appreciate it.
jeromechrome1 said:
I tried all of that already bro, it takes the files fine i did each individually including the bootloader. yes i have the latest sdk and latest fasboot. same issue no matter what i try. thank you all for ur help so far, really appreciate it.
Click to expand...
Click to collapse
Thats too bad. Maybe the device is hosed. RMA for a new one.
Same thing happened to me. As soon as I updated to the newest version of fastboot on my computer, everything worked...
jeromechrome1 said:
My motorola Nexus 6 won't turn on, when I try to power it on, it shows the Google sign then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, it flashes fine but it still shuts off immediately while showing the google sign. It won't even boot into recovery after the flash, it just shuts off after the google sign. This isn't my first nexus, in know that flashing factory image should fix 99% of issues. Please help.
P.S I didn't purchase officially from google or Motorola, bought it from a guy who claimed he bricked it trying to install a font pack so I figured let me buy it and restore factory image. Didn't work. I tried flashing manually, the process went fine, but it it still turns off at google splash image. I tried Wugfresh toolkit also to no avail. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and it wouldn't boot past google screen after that. It doesnt even get to the boot animation. It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I spoke to my friend who has a local repair shop and he says there is nothing out for his z3x or his other boxes for the nexus 6 because it is such a new and rare device. His theory is that the partition tables have been corrupted somehow and need to be rewritten manually. Please any help would be appreciated. I can promise a hefty $$ reward for any individual that helps me recover it to a working state.
Click to expand...
Click to collapse
I know, it's been a long time, but coud you tell me what happened to the phone?
As above, helping an acquaintance on a local forum to post this. Not 100% clear how it got to this state, from what I know his phone had issues, and he tried to flash back to factory settings using Wugfresh. It worked, but after a while he started seeing this issue out of the blue.
The phone boots up, after the Google logo and the dancing dots, the screen shows this weird confetti before boot looping again.
Still able to get into bootloader, still able to get into stock recovery, fastboot detects the phone just find on terminal/cmd. I tried flashing factory images manually on both Windows 7 and on Mac OSX, the terminal indicated the flashing was successful, sending and writing onto the phone.
Since this is the first time i tried the N6, the only thing off was that when flashing system.img, it said "sending sparse data" instead of just "sending data"?
Video here.
https://instagram.com/p/zzq6E-Gc-G/
Anyway, i don't have the phone with me anymore, so it's more for my curiosity than anything else. I was thinking hardware failure (emmc?) of some sort, but would love to hear more input if any.
Cheers!
I had this issue once on my N6. I then flashed the cache partition (had skipped it earlier) from the dev images and it booted fine after that.
I attempted to OTA update my stock Nexus 6 to 5.1 last night, setting it aside to do its thing and went to bed. When I turned the phone on this morning it went into the boot animation which just goes on indefinitely. I have attempted to clear the cache which did nothing. I was wondering if there is a work around without having to wipe the phone and thus lose all my data.
I have seen the first boot take up to 20 minutes you didn't turn off before then did you?
Sent from my Google N6 on VZ
No I left it in my pocket on my commute to work and tried to restart the phone over 2 hours later
Andrew_3 said:
No I left it in my pocket on my commute to work and tried to restart the phone over 2 hours later
Click to expand...
Click to collapse
Leave it booting for over 20 minutes. If it isnt booting after that, it isnt going to.
The next option is using fastboot to wipe the phone.
fastboot erase cache
fasboot erase userdata
Agreed 20 minutes is probably too long but I wanted to understand how long he was waiting. I know I get crazy impatient
Sent from my Google N6 on VZ
So left it over 20 mins and it did nothing. I have installed the 15 seconds ADB installer with all the drivers. Fastboot can recognise the device but the code >adb devices can't find anything! I even plugged in my Nexus 9 which works just fine with no result.
If during the upgrading process you used the command "fastboot erase cache" and received the message "did you mean format?" or something like that, then you need toflash the cache.img.
"fastboot flash cache chache.img"
I was stuck in a infinite boot animation at one point also. Did the above, and the phone booted in 15 seconds.
Andrew_3 said:
So left it over 20 mins and it did nothing. I have installed the 15 seconds ADB installer with all the drivers. Fastboot can recognise the device but the code >adb devices can't find anything! I even plugged in my Nexus 9 which works just fine with no result.
Click to expand...
Click to collapse
adb devices won't find fastboot devices. Adb works only in android or recovery. Fastboot only works in bootloader.
I didn't do the upgrade myself it was OTA!
Won't re flashing the image wipe the phone though?
Andrew_3 said:
I didn't do the upgrade myself it was OTA!
Won't re flashing the image wipe the phone though?
Click to expand...
Click to collapse
Yes, it will, but at this point, you either have a phone that won't boot, or the possibility of a phone that will afterwards, which one do you want?
I'd flash the image and see what you get. It's a small tradeoff at the moment.
Oh, and RootSU, like the new avatar!
My friend got the exact same problem - tried the OTA update, and after that the phone is stuck at the boot animation. I tried to clear cache/factory reset, and once it even booted up, but after showing the android logo it displayed something like "services stopped" (it was too fast to read carefully) and it powered down. And now no matter what I do, it stays on the boot animation. Is there anything I can do about it without my friend loosing his warranty?
PS. And when I tried the "fastboot erase cache" it displayed the "did you mean format?". Where can I find the "cache.img" to flash - and will it void the warranty?
Edit: Ok - I have flashed the Cache.img - now the phone boots quite fast, but immediately after the "android" logo I get "exchange services stopped", and "Print spooler stopped" with an "ok" that I can't click :/
Edit2: If I would have to flash the whole rom, which one should I choose? LMY47 - D, E, I ?
Edit 3: I have flashed the "I" version, and my friends phone works again