Related
powered up with PWR and (-) key and wont come out of it
Hold the power down for at least 5 seconds. You should see the screen go completely dark (better in a semi-dark room, as it's easier to see).
still stuck
tried your solution, nothing.
let it charge overnight to make sure I wasnt being a total scrub and the battery was dead....nothing
Any other suggestions would be greatly appreciated.
skip this, finally woke it up...on to next problem thanks all
When I first tried to flash to 1.1a, something like this happened. I don't think it was the ROM -- I think something malfunctioned inside the file system.
It was in the continuous Off/VS Birds/G-TabletLogo loop and even the power switch would not turn it off!
I wound up flashing CWM, and when I got into CWM I re-partitioned and re-formatted everything and then was able to successfully re-flash to TnT 2.2.0. (With the file system fixed, I am guessing I probably could have gone back to 1.01a if I have wanted to.)
Glad you are back working.
Rev
ARGHH!!
So has anyone found a definitive way to get these devices out of APX mode? I did a full restore on new device to clean up all the partitions and such, now nothing seems to get this thing to come out of APX. I suppose I could power it up with nvflash and leave it on the nvflashing screen until the battery dies, but there had to be a better way than burning the battery down overnight...
I have tried all sorts of combinations of powering on and off, is there a magic sequence lol...
my gtab wont boot up
my gtab wont go past the viewsonic and then gtab screne pleaseeeeeee some one help do i need to return it. i installed the tnt lite last night then this morning i couldnt sink mu gmail account then all of a sudden this....help
georgetirone said:
my gtab wont go past the viewsonic and then gtab screne pleaseeeeeee some one help do i need to return it. i installed the tnt lite last night then this morning i couldnt sink mu gmail account then all of a sudden this....help
Click to expand...
Click to collapse
Please don't hijack threads. There are LOTS of threads about boot loops. Check out some of the boot loop threads.
I was able to finally get the device unlocked and running much better. I used the nvflash recovery to get back to stock, then used Z4Root to get the device rooted stock. The rooting seems to have un-apx'd the device, and it works fine from there. So I would recommend keeping z4root on your drive so you can install it and root the device if it gets stuck in apx mode lol. It's a dirty hack but it worked for me when nothing else did.
Both of you,
I don't see that the thread was hijacked -- both of you are/were stuck in loops. Or at least something I think have a common cause.
What I was saying in my earlier post is that I am seriously wondering if the boot loops are caused by problems with the file system. Say, the system malfunctions or a flash makes something so it can't find the files it need to start.......
From my reading, it seems like most of the loops wind with the file system having to be fixed, or a new mod flashed over it, etc.
If we could determine that, perhaps we could know if loading CWM and fixing, or some such -- might save a tablet w/o having to re-flash.
Ideas or opinions?
Rev
butchconner said:
Both of you,
I don't see that the thread was hijacked -- both of you are/were stuck in loops. Or at least something I think have a common cause.
What I was saying in my earlier post is that I am seriously wondering if the boot loops are caused by problems with the file system. Say, the system malfunctions or a flash makes something so it can't find the files it need to start.......
From my reading, it seems like most of the loops wind with the file system having to be fixed, or a new mod flashed over it, etc.
If we could determine that, perhaps we could know if loading CWM and fixing, or some such -- might save a tablet w/o having to re-flash.
Ideas or opinions?
Rev
Click to expand...
Click to collapse
Hi,
Would a logcat (adb logcat) show anything?
Just a thought...
Jim
blue tooth stuck in apx
my bluetooth was stuck in apx. i unstuck it by installing a bluetooth switcher from the market.
Hop this helps someone.
roebeet said:
Hold the power down for at least 5 seconds. You should see the screen go completely dark (better in a semi-dark room, as it's easier to see).
Click to expand...
Click to collapse
what worked for me is holding down the same buttons to getting into apx mode.
both +/- volume buttons and then power until the screen turns off.
nickmaccombs said:
skip this, finally woke it up...on to next problem thanks all
Click to expand...
Click to collapse
May I ask how you got it started up? The only way I can get it to start is to NVFLASH. If I turn it off again, it'll be stuck in APX mode...
Hello, i recently bought a xoom (wifi only) and now im in a quite frustrating situation.
When i got it first i flashed CWM recovery and rooted it successfully, it worked all fine for a few days.
yesterday i left the xoom on charger over night and today morning it was stuck on the red M logo saying "Dual Core Technology".
well, my situation is like:
- i can restart the xoom using power + volume up, but every time it stucks on the M logo again
- i can boot into RSD with volume up while starting
- i can boot into fastboot with volume down while starting
- i can NOT boot into recovery, when i try it gets stuck at "Reading ODM fuse: 1"
i reflashed the original ROM from MOTODEV, but the device still behaves the same like before..
normal boot gets stuck at the M logo, recovery gets stuck on Reading ODM fuse: 1, just fastboot working fine (unlocking & flashing works fine)
i also searched for similar problems on the forums, but any promising solution links to filesonic links wich are not working/down
any ideas what i can do now? any help is appreciated
thanks
unlock the bootloader and flash Rogue Recovery v1.3.0
then try to enter cwm
are u on stock? or customrom? and have u tried to lock the bootloader using a customrom? cauz locking the bootloader with customrom = not good
hi, thanks for your reply.
im on stock rom and my bootloader is unlocked. i did relock the bootloader once, but only after flashing the original ROM from MOTODEV to my device, now it is unlocked again.
i first flashed the CWM 3.2.0.0 wich is available as .img via fastboot, but it does not start (Stuck on "Reading ODM Fuse: 1").
now i flashed the recovery.img inside of Rogue Recovery 1.3.0 (since i read in the corresponding thread that it works also this way), but again: Stuck on "Reading ODM Fuse: 1"
Maybe u r 2 quick? Turn on your xoom - if u see the M wait 3 sec then press vol down and then vol up
But as i said wait 3 secs - if u r 2 quick it will stuck at entering recovery
okay, so you flashed a new recovery image (did you verify the images md5-sum?) and without trying to reboot into android you cannot get into recovery? That is really odd.
If so, I suspect that something has really screwed up your internal memory. You might be able to fix it using a factory cable.
Btw: after flashing the recovery image, does the xoom say that it succeeded in writing the recovery image to its memory?
There should be a command to reboot the device to recovery? A function reboot to recovery is possible on eos 1.0 maybe theres a adb or fastboot command 4 that?
llama-power said:
okay, so you flashed a new recovery image (did you verify the images md5-sum?) and without trying to reboot into android you cannot get into recovery? That is really odd.
If so, I suspect that something has really screwed up your internal memory. You might be able to fix it using a factory cable.
Btw: after flashing the recovery image, does the xoom say that it succeeded in writing the recovery image to its memory?
Click to expand...
Click to collapse
after flashing the recovery, i can read
"Flashing StorMgr partition recovery STATUS: done!" on the xoom
the recovery image is fine, and until today i was able to boot into CWM 3.2.0.0
what is the thing with the factory cable?
about the factory cable: seems to be a modified usb-cable with two terminals on the micro-usb end being connected with each other. As far as I read, it should enable you to write to the xooms memory as long as the hardware is still okay, no matter how much you f***ed up your software I haven't had to use yet, though.
@what Unholy said: sure, adb reboot recovery will boot your xoom into recovery, but only if you have a working android running and usb-debugging enabled.
Reading ODM Fuse: 1, according to my information, means that the thing is trying to boot into recovery. Why nothing else shows up: I have no clue.
here is a thread where some us-users had a similar problem. They tried to root their xoom after getting the 4g-upgrade and ended up with the red M-Logo. After some screwing around, they even managed to wreck the fastboot-mode, thus only enabling rsd access. So no help on that side.
What especially bothers me about your problem is that it just appeared on its own. Right before your xoom showed its issues, you weren't flashing anything. Just charging shouldn't cause any of this.
I am beginning to suspect a hardware failure that can naturally be only fixed by motorola. But that's only my current opinion.
If I was you, I would try downloading the files from motorola again, check their md5-sums and then flash those using fastboot using these instructions.
If that still doesn't help, there may be a way to get a .sbf file from motorola for your xoom. That is a file which can be flashed using the windows software rsd-lite, but I haven't used that in a long time and it has been reported to not work really well with the xoom.
Next, I'd research a little on the factory cable thing, but I'd be careful with that.
As a last resort, I'd send the xoom to my dealer. Unluckily, there is a way to determine if you have had your bootloader unlocked, at least as long as fastboot is still working...
About the factory cable - with that cable u can flash your xoom if nothing else is working anymore (adb or cwm)
To build a factory cable u have to tie pin 1 (+) to pin 4 on the micro usb plug
I build one but never used it and hope i will never have to
i did download the original ROM from motodev again, checked the md5, and flashed according to the tutorial posted by llama-power, but the device still wont boot neither the rom nor into recovery.
since its now on 15% battery i think i will let it run out of power and then try to boot again...
The_Revenge said:
i did download the original ROM from motodev again, checked the md5, and flashed according to the tutorial posted by llama-power, but the device still wont boot neither the rom nor into recovery.
since its now on 15% battery i think i will let it run out of power and then try to boot again...
Click to expand...
Click to collapse
does the xoom charge when connected to ac power? I know that other devices (cellphones) wouldn't charge without working os.
However, I do not think that letting the battery run low will help you. Lithium ion batteries should not be low discharged as that will most likely destroy them and lead to a massive risk of explosion upon the next charge. Because of that, devices powered by a lithium ion battery will power down before depleting the battery, the xooms mainboard itself will most likely still be supplied with some power.
If you really want to cut the power supply to the mainboard, you'll have to open the xoom (two screws) and unplug the battery (the connector is held down by another two screws) for a couple of seconds. (here is a teardown of the xoom with pictures)
by the way, if you want to track your battery status without booting android (as that would obviously not work), you can use fastboot getvar battery-status.
well my xoom actually charges when i connect it to power, and the LED also lights up, so (thinking of what you said) it seems like the os and everything still is present, just like the bootloader cant load it or something?! is there maybe any way to update the bootloader itself?
yeah, i can also check the battery status when i'm booting with power and volume up (RSD) =)
well i'm actually thinking about disconnecting the battery, but i'm a bit unsure, i will study that now..
The_Revenge said:
well my xoom actually charges when i connect it to power, and the LED also lights up, so (thinking of what you said) it seems like the os and everything still is present, just like the bootloader cant load it or something?!
Click to expand...
Click to collapse
not neccessarily. Maybe the xoom just doesn't need any software to charge the battery.
The_Revenge said:
is there maybe any way to update the bootloader itself?
Click to expand...
Click to collapse
don't know, but since fastboot works I suspect that the bootloader itself is still fine.
The_Revenge said:
well i'm actually thinking about disconnecting the battery, but i'm a bit unsure, i will study that now..
Click to expand...
Click to collapse
have fun, but I wouldn't get my hopes up too high. I still suspect some sort of a hardware failure... Also, opening the device might leave some traces (botched screws, etc) that could lead motorola to say that you messed with your xoom if you should finally decide to send it in
well thats the same i thought about opening the device..
do you know any way to dump the partitions to the pc (maybe with fastboot?)
The_Revenge said:
do you know any way to dump the partitions to the pc (maybe with fastboot?)
Click to expand...
Click to collapse
nope, not without a working recovery.
fastboot erase partition_name should be able to clear your partitions, though. Replace partition_name with boot, system, userdata, cache or recovery
http://www.xoomforums.com/forum/xoo...ery-stuck-red-m-logo-fastboot-works-help.html
apparently that user seems to have had the same problem, he says he fixed it using 1.35 Everest Bootloader (SBF).
i also had that idea some time earlier and found a thread with the SBF files here on xda, also for the wifi model, but the only links i could find to SBF files were filesonic links wich are not working ._.
i'm now up to googling for SBF files (for the wifi only model), if i cant find anything promising i'll send it back tomorrow.
btw, erasing the partitions does not help, i've already tried that
Have u done the lte update?
UnholyX said:
Have u done the lte update?
Click to expand...
Click to collapse
he's got an wifi-only model (as stated in post #1) and is from germany (at least that's what his location and flag says). LTE upgrade is neither available in germany, nor for wifi-only-xooms. So I'd say no
@OP: that sounds quite promising. .sbf-files still seem to be available on some sites, downloading one for my xoom right now, just in case that site goes down in the future...
Yes he got the wifi version like me but something must happened ,-)
I also charge my xoom and nothing happens. He got wifi version but he maybe flashed a false update or so
There r people flashing stingray instead of the wingray version etc. - just asking what happened before - thats the reason - something must happened before ;-)
it seemed promising, but i cannot find any usable sbf file
i think i'll send the unit back tomorrow
I am on a Verizon Razr Maxx HD (xt926). This all started when I decided to cleanly flash the newest version of CM10.2. I had been running it before. I wanted to start from a blank slate, so I went into TWRP and did the format wipe. Installed the newest CM10.2 nightly and gapps. This went fine and I booted into the ROM and started recovering all of my stuff. I installed F-droid and AdAway, and rebooted for that. The phone never got past the Bootloader Unlocked warning screen. I turned it off and went into TWRP to try some things. I tried to fix permissions, but it failed, referencing something to do with fdroid. I wiped again and reinstalled CM, but I still couldn't get past the Bootloader Unlocked warning.
I booted into TWRP again and wiped what I could, and accidentally wiped my external SD, and I had no card readers lying around to get the ROM zips back onto it. I downloaded the Razr HD utility, used the batch file, and tried to flash the stock rom through fastboot, but it got stuck in some kind of loop and would not flash correctly. I then tried to do it manually, but got some sort of buffer error. I tried again, and it started ok but I never saw it actually finish flashing.
By this time I finagled the ROM zips onto the SD card and stopped the fastboot and booted into TWRP. I did another set of wipes, and rebooted into TWRP again. I flashed the CM and Gapps. The ROM booted fine from TWRP and I was able to start setting up my account again. I tried rebooting after the initial setup just to see if it was working correctly, and was met with the fastboot screen with fastboot reason: Flash failed. I rebooted into TWRP from there, and tried to boot normally, but it still brought me to the fastboot. I went to the boot menu and tried the normal boot selection, and now my phone is stuck on the Bootloader Warning screen and now it won't even turn off when I hold the power button.
I have no idea what is going on, or why I could get to the working ROM once but not again. Does anyone know anything that could help me?
Kopiok said:
I am on a Verizon Razr Maxx HD (xt926). This all started when I decided to cleanly flash the newest version of CM10.2. I had been running it before. I wanted to start from a blank slate, so I went into TWRP and did the format wipe. Installed the newest CM10.2 nightly and gapps. This went fine and I booted into the ROM and started recovering all of my stuff. I installed F-droid and AdAway, and rebooted for that. The phone never got past the Bootloader Unlocked warning screen. I turned it off and went into TWRP to try some things. I tried to fix permissions, but it failed, referencing something to do with fdroid. I wiped again and reinstalled CM, but I still couldn't get past the Bootloader Unlocked warning.
I booted into TWRP again and wiped what I could, and accidentally wiped my external SD, and I had no card readers lying around to get the ROM zips back onto it. I downloaded the Razr HD utility, used the batch file, and tried to flash the stock rom through fastboot, but it got stuck in some kind of loop and would not flash correctly. I then tried to do it manually, but got some sort of buffer error. I tried again, and it started ok but I never saw it actually finish flashing.
By this time I finagled the ROM zips onto the SD card and stopped the fastboot and booted into TWRP. I did another set of wipes, and rebooted into TWRP again. I flashed the CM and Gapps. The ROM booted fine from TWRP and I was able to start setting up my account again. I tried rebooting after the initial setup just to see if it was working correctly, and was met with the fastboot screen with fastboot reason: Flash failed. I rebooted into TWRP from there, and tried to boot normally, but it still brought me to the fastboot. I went to the boot menu and tried the normal boot selection, and now my phone is stuck on the Bootloader Warning screen and now it won't even turn off when I hold the power button.
I have no idea what is going on, or why I could get to the working ROM once but not again. Does anyone know anything that could help me?
Click to expand...
Click to collapse
Try the solution in the last few posts on this thread. http://forum.xda-developers.com/showthread.php?t=2465695
I hope you get more knowledgeable advice than mine but, were I in your situation, my primary goal would be to get back to STOCK. Forget CM and modding for now. Either through TWRP or through the recovery settings on the phone itself I'd get to where I could do a factory reset. If you're continuously able to boot into TWRP I don't see how your phone could be bricked. My experience is, if I can get a phone to do ANYTHING I've got a shot at figuring out how to get out of whatever mess I've created. I don't know if this could be a factor but I'd put in a different micro SD card too, in case there's something on the card you've got in there.
Just an update. So, I got it to go back to fastboot this morning and I tried using the Razr Utility to flash back stock and stock recovery, but I got a "Failed" line with the reason "Remote Failure". Not sure what that's about. When it reset it got back to the Cyanogenmod boot graphic, but it never started. I left it there for a good 12 minutes.
Right now it's sitting in TWRP. I'm going to let it charge to 100% (it was a little less when I tried all of this) and attempt it again at 100% battery. Thanks for the help so far!
So, I tried using the Razr Utility to flash the system, kernel, radio and for system it was unsuccessful (something about too many threads or strings, something to that effect), but the rest said OK. Now my phone doesn't seem to turn on. My computer still makes the device plugged in sound when it's plugged/unplugged, but I cannot get the screen to show anything or seem to turn on the phone.
Is this it? Is it... bricked!? ;-;
Edit: I ordered the Factory Adapter as a last resort sort of thing. This is lame.
Edit Edit: I've seen the boot logo since my last edit! But... it's not coming back and I still can't even bring up the bootloader. I don't know why it will sometimes turn on or sometimes not. In any case, I'm now hopeful that not ALL is lost.
Bottom line, the adapter will allow you to fix your phone and flash the stock FXZ in RSD Lite or fastboot and get back to a clean slate and start over.
That's why we went to the trouble of making them!
cellzealot said:
Bottom line, the adapter will allow you to fix your phone and flash the stock FXZ in RSD Lite or fastboot and get back to a clean slate and start over.
That's why we went to the trouble of making them!
Click to expand...
Click to collapse
That's the plan! One odd thing happening now... My phone's screen isn't showing anything, so I assumed it was off. I left it unplugged and went to see a movie..... and the phone is still warm. This leads me to believe the phone is still drawing power, for some reason... God this is weird. I'll wait for the adapter and try again. Thanks for the help!
cellzealot said:
Bottom line, the adapter will allow you to fix your phone and flash the stock FXZ in RSD Lite or fastboot and get back to a clean slate and start over.
That's why we went to the trouble of making them!
Click to expand...
Click to collapse
according to the packaging on mine from tbh a chinaman made it, just sayin
Yes, we designed them and contracted through our US supplier who produced all of our cables who, in turn, had them produced in China according to our specifications. There is no longer any injection molded plastic production done in the US that can work at this small scale for affordable rates.
Sorry...that's the way the world works these days.
cellzealot said:
Yes, we designed them and contracted through our US supplier who produced all of our cables who, in turn, had them produced in China according to our specifications. There is no longer any injection molded plastic production done in the US that can work at this small scale for affordable rates.
Sorry...that's the way the world works these days.
Click to expand...
Click to collapse
thanks for making it either way, better to have and not need.
havent had to use it so far
bweN diorD said:
thanks for making it either way, better to have and not need.
havent had to use it so far
Click to expand...
Click to collapse
You're welcome! They are definitely the best $10 investment you can make in any Motorola phone.
Next time you want to invest many thousands of dollars of your own money in a wild, hairbrained scheme to help a bunch of anonymous people on the internet fix their phones that they recently finished destroying themselves, let us know...we have just the plan!
cellzealot said:
You're welcome! They are definitely the best $10 investment you can make in any Motorola phone.
Next time you want to invest many thousands of dollars of your own money in a wild, hairbrained scheme to help a bunch of anonymous people on the internet fix their phones that they recently finished destroying themselves, let us know...we have just the plan!
Click to expand...
Click to collapse
how many thousands, and whats the plan?
I got the Factory Adapter and used RSD Lite to flash stock. And it works! Yay! It's starting up reliably and everything.
Except... it won't start up without the cable attached, and the battery icon has a big question mark on it. It also won't connect to the cell network (but does connect to WiFi). What do I do now?
Edit: So I noticed that while the battery status said "Unknown", it did go from 2% to 3% charge level when I plugged it in normally for a little. My plan at the moment is to try leaving it plugged in for a while and then try taking the OTA update to see if that fixes everything. Good plan?
Edit Edit: Never mind! I just had to let it charge for a bit. It seems to be back in working order, now! Thank you so much for all the help everyone!
That is exactly what is supposed to happen. Congrats on fixing your phone!
The factory cable/adapter does not charge the device but powers it directly, allowing it to boot no matter what state the battery is in or even without a battery at all.
You cannot charge in bootloader, which is why the cable/adapter is so valuable. Once the device can boot/charge normally then you are all set.
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you try flashing factory images?
ryukiri said:
Did you try flashing factory images?
Click to expand...
Click to collapse
Yeah, that was what I flashed :/
If you can get into fastboot you "should" be able to flash stock images... Obviously this will revert any root and you will need to flash TWRP/CWM recovery after.
I assume you have a Windows PC with fastboot/adb setup and all drivers etc..
- Download latest "stock" hammerhead images (I cannot post links due to XDA rules... so: "developers.google.com/android/nexus/images#hammerhead"
- Extract the .tgz archive contents on your PC into a folder
- Boot the N5 into fastboot and plug USB cable from phone into your PC
- Go to the folder with the extracted files and run the "flash-all.bat" script on Windows
**Hopefully at this point your device will start to respond.. I.e, on fastboot screen, at the bottom you will see "writing" or something, as the script runs on the command window on your PC.**
If this works, you should be able to reboot once complete and then wait to see if you can get back into your phone.. then you can fastboot again and flash custom recovery, and then whatever rom.
If however you have a hardware issue (i.e, even after the above process it fails) then I am not sure what you could do... I guess ensure it has a complete charge. If you can get into fastboot and the buttons are responsive then it should not be a faulty power button.
Hope this helps :good:
Have you tried a simple factory reset? Reason I ask is it was working fine so sounds like something needs "flushing out" clear cache etc.
kyle313 said:
Hey folks...I'm running into a problem I was hoping someone might be able to help with.
Earlier today I pulled my phone out of my pocket at work and saw that it was off...I thought that the battery must have died sooner than I thought. I started charging it in the car on the way home and it wouldn't boot up like normal. It would get to the google or "dots" screen and then reboot. I again thought that the battery might just be really low. After getting home and charging the phone all the way I still can't get it to boot up. As of now, one of 3 things will happen...
1-The phone will turn on, get to the google screen and bootloop (usually when plugged in).
2-The phone will turn on, get to the google screen and freeze.
3-Get to the "dots" screen and either swirl forever or eventually reboot and do one of the above again.
I've read some threads where people suggest this is a faulty power button, that doesn't seem to be the case for me though because I can get into fastboot and it won't select anything or turn off without me doing it.
I've used WugFresh NRT and wiped/reflashed android. I'm running out of ideas. Do you have any others?
I was running the stock 5.0.1, unlocked, not currently rooted.
Thanks!
Click to expand...
Click to collapse
Did you choose the right model and firmware before you flash in WugFresh NRT?
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
howard bamber said:
The above could be right, however when I've used it, it's pointed out if I made that mistake. Having used his software dozens of times I've found it will bring any Nexus 5 back to life.
Click to expand...
Click to collapse
Hello! I am apologize for that I didn't read the OP carefully. This happened to me once in that particulary way, but it was immediately after flashing. OP says that it happened suddenly, without reason. So now I am the one, who doesn't read, right? Sorry for that.
Regards, Zagor
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
kyle313 said:
Thanks for the responses, but I'm still having trouble.
I have been able to successfully write the newest stock android 3 times (1 without full wipe, 2 with) and the phone still can't boot up and goes through one of the three issues above.
I've also been able to get to the system recovery from the bootloader and I've tried wiping the cache and doing a factory reset from there and the problem remains.
I'd contact google, but I bought it at launch so I don't think they'll do anything for me since it's been 1+ years.
Click to expand...
Click to collapse
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
theesotericone said:
Sounds like you have a bad nand sector. From fastboot try:
Code:
fastboot oem lock
Then reboot into fastboot and check if it's locked or not. If the device isn't locked your emmc is corrupt and there is nothing you can do. If that is the case call Google and they will most likely help you out with a RMA.
Click to expand...
Click to collapse
I was actually able to relock the phone.
Luckily I called google and they're going to send me a replacement.
If anyone else has any other ideas, I'll still take them...I'd rather not be without a phone for the next week!
You won't be without a phone - they are sending a refurbish unit to you , putting a block on your credit card and waiting for you phone to arive at them. Once that happens they will release the funds.
Hello guys,
It is my first time yesterday to flash and root my Xperia Z5 since the camera app always says that it is currently in use.
I used this guide by sceryavuz . And it turned out great, I have used my phone for a day without any errors or problems encountered. But the thing is, I still cannot use the camera app and it has the same currently used by other application message so I decided to downgrade it to Marshmallow this morning. So I went to the same routine, downloaded an FTF file and loaded it into the flashtool.
After clicking Flash device in the flashtool and waited for the flashmode, I connected and pressed the volume down button of my phone but the flashtool is not reading and recognizing my phone. So I decided to open the TWRP and assumed that factory resetting my phone will do the work and it turns out that it just removed the /system folder and now I have a bigger problem with my phone.
When I'm connecting in flashmode the LED is turning to red, green, then will turn off, and then will do the same cycle if left unattended.
Could you guys please help me out with this. You'll be greatly appreciated guys. Thanks!
My phone is E6653 Xperia Z5
Well, you should reflash the system, by a custom rom of your choice or even the stock rom if you want to.
I'm using a custom rom and I highly recommend you to do so if you already lost your data, give it a try.
You don't need to downgrade to MM, it not an android version issue, I would recommend you carbon rom. Go to it's thread and figure out how to flash it, if you need help ask over there or quote me back in this thread.
Another option could be restoring your phone with xperia companion but you will need to relock the bootloader and get flashmode to work again. You can also try flashtool from your computer. Anyway I recommend you to do so ONLY and ONLY if you want your phone to run stock again as it was when you bought it.
Otherwise yep, figure out what's a customrom and how to flash it, you find tons of custom roms in xda threads. having already TWRP is an advantage, less sketchy stuff to do.
Hope it helped, as I said, quote me back if you need help
Edit: if you need the files we're running the exact same device, if you don't find em (and only if you can't find em) i could send them to you.
ofmoll said:
Well, you should reflash the system, by a custom rom of your choice or even the stock rom if you want to.
I'm using a custom rom and I highly recommend you to do so if you already lost your data, give it a try.
You don't need to downgrade to MM, it not an android version issue, I would recommend you carbon rom. Go to it's thread and figure out how to flash it, if you need help ask over there or quote me back in this thread.
Another option could be restoring your phone with xperia companion but you will need to relock the bootloader and get flashmode to work again. You can also try flashtool from your computer. Anyway I recommend you to do so ONLY and ONLY if you want your phone to run stock again as it was when you bought it.
Otherwise yep, figure out what's a customrom and how to flash it, you find tons of custom roms in xda threads. having already TWRP is an advantage, less sketchy stuff to do.
Hope it helped, as I said, quote me back if you need help
Edit: if you need the files we're running the exact same device, if you don't find em (and only if you can't find em) i could send them to you.
Click to expand...
Click to collapse
Hi ofmoll,
I'm sorry for the very late response, I had an internet connection issue this past week. I have tried your suggestion by using Carbon Rom, it works perfectly fine but I have one problem. It is not charging and the battery keeps saying that it is on 100% even if it is not. I'm trying to reflash other ROMs and I'll get back to you as soon as I finish flashing. Happy new year! Thanks!
Hi,
I tried to flash my phone a carbon rom and a crdroid rom and it was successful, my problem was it wasn't charging, and whenever I try to use flashtool, and I am entering flashmode, the phone turns red then green then after a minute it turns red again and then green after I press volume down and connect the phone to my PC. And the PC seems cannot recognize my device since no sounds are going off my computer when I connect it. I hope you can share your expertise regarding this.
Toshiiiiiiii said:
Hi,
I tried to flash my phone a carbon rom and a crdroid rom and it was successful, my problem was it wasn't charging, and whenever I try to use flashtool, and I am entering flashmode, the phone turns red then green then after a minute it turns red again and then green after I press volume down and connect the phone to my PC. And the PC seems cannot recognize my device since no sounds are going off my computer when I connect it. I hope you can share your expertise regarding this.
Click to expand...
Click to collapse
So you say it's not charging? Or did you manage to solve that? You don't really need flashtool at this point (unless you want to relock the bootloader, but I guess there are backdoors for that as well)
If it's not charging, well, the options are this: either it's a hardware problem, for example charger or charge port, or a software problem, because some files are needed for the phone to detect a charger source plugged in.
1. If the software is crashing you can try going into TWRP and wipe cache and dalvik cache, may help may not, try. If you get it yo work remember to calibrate the battery after it, it might be important because after flahsing roms and having this kind of issues the battery could not be showing the actual percentage of battery. So just calibrate, it's easy, Google it.
2. It could happen that the phone is charging but the battery status icon won't show it, I'm not too sure about this but I heard that could happen, might not be the case.
3. In none of that works, search, make a lot of research of people with your same problem and try amd try and try, If nothing works a clean reflash should solve it, usually does, if not try another rom, another kernel or go back to stock. It's your choice, but anyway I guess a clean reflash should get it working. I had the same issue with LineageOS and wiping Dalvik Cache solved it.
If you wipe dalvik expect a long reboot time, I don't suggest you to turn the phone off while it boots up. Wiping Dalvik means all cache files have to be built again the next time you reboot your phone, so yeah, expect some battery drain and a hot device while it boots up, but don't panic, it's totally normal.
Happy new year, hope you get it working again
Remember to hit thanks, cheers!
ofmoll said:
So you say it's not charging? Or did you manage to solve that? You don't really need flashtool at this point (unless you want to relock the bootloader, but I guess there are backdoors for that as well)
If it's not charging, well, the options are this: either it's a hardware problem, for example charger or charge port, or a software problem, because some files are needed for the phone to detect a charger source plugged in.
1. If the software is crashing you can try going into TWRP and wipe cache and dalvik cache, may help may not, try. If you get it yo work remember to calibrate the battery after it, it might be important because after flahsing roms and having this kind of issues the battery could not be showing the actual percentage of battery. So just calibrate, it's easy, Google it.
2. It could happen that the phone is charging but the battery status icon won't show it, I'm not too sure about this but I heard that could happen, might not be the case.
3. In none of that works, search, make a lot of research of people with your same problem and try amd try and try, If nothing works a clean reflash should solve it, usually does, if not try another rom, another kernel or go back to stock. It's your choice, but anyway I guess a clean reflash should get it working. I had the same issue with LineageOS and wiping Dalvik Cache solved it.
If you wipe dalvik expect a long reboot time, I don't suggest you to turn the phone off while it boots up. Wiping Dalvik means all cache files have to be built again the next time you reboot your phone, so yeah, expect some battery drain and a hot device while it boots up, but don't panic, it's totally normal.
Happy new year, hope you get it working again
Remember to hit thanks, cheers!
Click to expand...
Click to collapse
Hi Sir,
Happy new year! Thanks for your reply and I really appreciated it. When I connect the phone to my charger when it's off, it turns on then shows the screen of charging 0% by carbon rom then immediately dies after 2 bars being filled. I hope that it is not a hardware problem since when I connect my phone to my computer via the usb, it lights on but the computer can't recognize it. I am suspecting that this is a rom problem with my phone since the phone shows that it's charging connected to AC and 100% even if it is not connected to a charger. I am trying to get the flashmode to work again so I can flash a stock rom to it because the stock rom works perfectly fine but the camera. I will try all your suggestions tomorrow and I'll research harder to solve this. Will post an update once done. Cheers!
Toshiiiiiiii said:
Hi Sir,
Happy new year! Thanks for your reply and I really appreciated it. When I connect the phone to my charger when it's off, it turns on then shows the screen of charging 0% by carbon rom then immediately dies after 2 bars being filled. I hope that it is not a hardware problem since when I connect my phone to my computer via the usb, it lights on but the computer can't recognize it. I am suspecting that this is a rom problem with my phone since the phone shows that it's charging connected to AC and 100% even if it is not connected to a charger. I am trying to get the flashmode to work again so I can flash a stock rom to it because the stock rom works perfectly fine but the camera. I will try all your suggestions tomorrow and I'll research harder to solve this. Will post an update once done. Cheers!
Click to expand...
Click to collapse
As said, first of all try what I said. It nothing of that solves it, I suggest you 3 options
1. Either go stock, try using XPeria Companion, but I think since you flashed custom it doesn't work, at least for me. For Companion you'll need to relock bootloader. Or go stock by flashing a stock rom via TWRP. Note that after flashing a custom rom you'll never go back to the "real" stock if you don't have a backup, but you can always flash a stock rom.
2. You can also try to reflash the rom and see if that works.
3. Download a Custom kernel, then go to TWRP, wipe everything, then first of all flash the Kernel (remember to ensure that's a kernel for your device). Then reflash the ROM. This could look stupid because the ROM comes with a built-in kernel itself, but it solved an issue I had with random reboots. I didn't read this anywhere, I tried and for me it solved a problem I had which everybody was telling me that was caused by hardware, then it came out to be a Kernel issue. Try to if you want.
Try what I said before as well. This is all I know
Cheers
Edit: I forgot to tell you that PC Companion won't recognize your phone if it's running a customROM. Use Android File Transfer instead. You also need to check "use usb to transfer files" on the notifications pannel. Enable USB debugging as well, I guess you know how to do it, in case: you need to go to "about phone" in settings, hit 8 times Build Number, then the developer options should appear and check Android Debugging. That's it.