hi guys,
my problem is that my nexus reboots randomly every few minutes. I've googled and i tryed a lot, but i think that my problem is another. First of all, i tell you what i've even tryed:
In the time when my nexus is completey bootet I tryed to remove the latest app. If the phone does not reboot in the meanwhile I hoped that after a normal reboot the app will be deleted. BUT after every restart all my apps are still there, even some other changes on the settings or something like that. After the next reboot everything is the same as before (before this strange thing happend)
So i tought that maybe flashing the ROM will help. But there is also the same problem. I did everything to unlock the bootloader and flash the recovery with fastboot. BUT there is the same problem, no changes on the bootloader will be saved, even the bootloader is locked again after reboot. And of course the recoverymod is also not changed/saved.
So now is my question: is this probably an issue of bricked hardware like the memory-manager-unit? I don't have any other ideas I can try to figure out whats going on (or not) on this phone. But before I'll give it to repair I will eliminate the possibility that this is a software issue. So does someone have an idea what else i can do?
Thanks to all answers,
Helme
your emmc is fried if you unlocked your bootloader and it restarted and said it was locked.
im pretty sure there is nothing you can do to fix
I have the exact same issue... is there no way to fix this ?
For emmc repair, check out mobiletech videos.com. They also have a YouTube channel.
Sent from my Verizon Gnex
Yea
Related
Recently I had a brick on my Desire, which caused that I couldn't boot past the HTC Boot logo. I already made a thread about it, but without a solution. I sent my desire back for repair, but I think it wouldn't be a good idea if we all had to do this. So I would advice everyone to unroot, untill one of the genius devs has found a solution.
Symptoms:
-Boot stuck at HTC Boot Logo
-Going in to recovery takes a long time
-Recovery usually doesn't even work
Posible Solution:
-Some users are reporting, they can boot without SD and SIM (dont know if repartitioning the sd totally solves everything)
-Some users report, say that the situation is solved if you flash a diffirent rom (didn't work for me)
Finally I would like to motivate my opinion why people should unroot.
When I posted my first entry I though I was the only one, but now more and more people are getting this problem.
This problem is as said above probably something which can be solved but right now its a dangerous development.
This is the first I've heard of this issue and it not being solved by the SD card removal or reformatting.
How many people have this problem unresolved, and what exactly were you running when it happened? What rom, radio, which recovery was used etc.
I have rooted my phone and flashed about 20-30 ROM's and haven't had a single problem.
I must have been lucky to get a phone that don't brick so easy. I hope that you who have problem with this get a solution soon.
socktug said:
This is the first I've heard of this issue and it not being solved by the SD card removal or reformatting.
How many people have this problem unresolved, and what exactly were you running when it happened? What rom, radio, which recovery was used etc.
Click to expand...
Click to collapse
I've read about 5 diffirent posts about this. All the post are on the first two pages i think. I was running DeFrost, and used r5's recovery. And I was running the most recent radio that is now availible
@Milioo So what you said make me feel like you blame all the devs here at XDA comminity bricking your phone and have to be responsible for your bricked phone and it was bricked because of THEM. Hello, when you first rooted it and started to get cooked roms into it, you should have known there are chance that you phone would be bricked. That's always the first thing you need to put in your mind and every single dev has told so.
So if I were you, I would just shut and find the way to solve the problem or ask for solution. Anyone here would try to help. Clearly, you are not asking for solution but complaining.
khoaitaychienvn said:
@Milioo So what you said make me feel like you blame all the devs here at XDA comminity bricking your phone and have to be responsible for your bricked phone and it was bricked because of THEM. Hello, when you first rooted it and started to get cooked roms into it, you should have known there are chance that you phone would be bricked. That's always the first thing you need to put in your mind and every single dev has told so.
So if I were you, I would just shut and find the way to solve the problem or ask for solution. Anyone here would try to help. Clearly, you are not asking for solution but complaining.
Click to expand...
Click to collapse
I'm really sorry if i made you or anyone else feel like that. I've always have great respect for the devs who work their asses of to make great roms for us. and always look forward to new cooked roms made by them. The only reason the I made this thread is that i don't want other people to get bricked.
Could you please tell me where i implied that the devs were a fault here?
And finally, if anyone is to blame its HTC who are working so strongly against people putting custom roms on their phone, who ust want to make their user experience better.
I've had the same problem that the phone wont boot at all and get stuck at the white HTC Logo.
But it was easy fixed with a run of all the wipe options, and then flash the rom again.
Giland said:
I've had the same problem that the phone wont boot at all and get stuck at the white HTC Logo.
But it was easy fixed with a run of all the wipe options, and then flash the rom again.
Click to expand...
Click to collapse
Ok guys i'm sorry for posting this thread, clearly it isn't really a problem. I just wanted to post it because these instructions dind't work for me. But i will gladly remove this thread (If its possible)
hi mate .
I have the exact problem and I think it is a real problem - see my thread
Can someone help me - stuck on htc boot - very strange situation -- I was not allowed to put the link to it...
I did everything do get it started but no luck at all. is strange that can access fastboot, the pc recognize the device but the recovery didn't work at all, even one time I couldn't get it: when I push the power button the logo htc screen just appear and get stuck there.
so if every one has any idea what could be please help us,there are more than a week I tried every day to get it work again.
many thanks.
I had this problem months ago I was running my desire on a custom rom had a2sd installed formated the sd card and the phone wouldnt boot reflashed a fresh rom and everything worked fine again.
I too had this problem...
You didn't by any chance apply the unrevoked recovery did you? If so, did you also use ROM Manager.
If you read the top page of the unrevoked thread you'll see that it says that the two combined cause a problem with flash memory. To fix the brick I ran an offical HTC RUU, re-rooted using Paul's method, and then re applied unrevoked. I now definitely DO NOT use Rom manager.
Hope it was some help mate.
Yes best option if u can access hboot is to go back to stock using ruu
then re root it shd solve all probs
in my case I can acces hboot.
I did also stock ruu and PB99IMG.zip, and installed ok but just won't load OS getting stuck again on htc logo screen. I mention that I had hboot 0.75 and after stock ruu I got hboot 0.80...
still in truble, really don't know what else to try, because recovery don't work at all and I can't install a new recovery.
Is there a way to flash a recovery from fastoob???
RUU
When I flashed a RUU, it was still stuck at the bootloop.
Milioo said:
When I flashed a RUU, it was still stuck at the bootloop.
Click to expand...
Click to collapse
If you can do a logcat of the boot-loop and pastebin it. We'll see what the problem is...
In terminal or command, write adb logcat or adb-windows logcat and then run it for the duration of the loop.
laupc said:
in my case I can acces hboot.
I did also stock ruu and PB99IMG.zip, and installed ok but just won't load OS getting stuck again on htc logo screen. I mention that I had hboot 0.75 and after stock ruu I got hboot 0.80...
still in truble, really don't know what else to try, because recovery don't work at all and I can't install a new recovery.
Is there a way to flash a recovery from fastoob???
Click to expand...
Click to collapse
Yea the RUU upgrades your H-boot, Does just running the RUU achieve anything, you should just have a fresh clean non-rooted ROM load up on your device straight after running it?
Pop onto irc and visit the modaco chat room....we can have a talk about possible fixes
chat.freenode.net
#modaco
Feel free to look for me, and message me
just give the adb logcat comand while in bootloop and saying waiting for device and that's all
Have you tried restoring a good misc image? Just incase this could be related to that like other forms of brick are...
how can I restore the misc?
laupc said:
how can I restore the misc?
Click to expand...
Click to collapse
http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
Although... with the mention of recovery taking an age, is that standard recovery, unrevoked or fake flash?
The above method uses the standard HTC recovery image, similar to fakeflash does. Worth a try *if* you can get it to work... May or may not resolve the issue though (I'm just guessing here) but could possibly in a weird kinda way help you to do a successful RUU restore using the PB image method...
Hello.
This my first thread. I have done some reading, but I can't find a similar problem, so I really hope that this is posted in the correct location...
I have an odd problem with my phone. I did a flash a few months ago, and I also (attempted to) update the modem and bootloader. After the reboot, I had to begin pulling the battery to get the phone to power back on after the power was off or after a restart. I've replaced the battery, charger, and installed SEVERAL new roms, but the problem persists. I don't know if I need to do something else, or if the phone is damaged...
But if it IS a programming problem, and not physical damage, then here's the real problem...
I have installed the latest version of CWM. I am running CM 11 with Kitkat 4.4.2. I would like to just flash the stock rom and see if that fixes it, but I have read that once you are running a 4.3 or beyond bootloader, you WILL brick your phone if you try to downgrade. So that stops that.
Another issue is that if I try to install a different/newer bootloader in CWM, it fails every time. I also cannot flash another version of CWM or TWRP. About halfway through the process, Odin says it has failed, no matter what version of Odin, CWM, or TWRP I am using.
So the short version of this is, based on what I've listed, how do I fix this rebooting issue?
I know that this is a long post, but I'm trying not to leave anything out. If anyone has any ideas, please feel free to let me know.
Thank you in advance
biga72112 said:
Hello.
This my first thread. I have done some reading, but I can't find a similar problem, so I really hope that this is posted in the correct location...
I have an odd problem with my phone. I did a flash a few months ago, and I also (attempted to) update the modem and bootloader. After the reboot, I had to begin pulling the battery to get the phone to power back on after the power was off or after a restart. I've replaced the battery, charger, and installed SEVERAL new roms, but the problem persists. I don't know if I need to do something else, or if the phone is damaged...
But if it IS a programming problem, and not physical damage, then here's the real problem...
I have installed the latest version of CWM. I am running CM 11 with Kitkat 4.4.2. I would like to just flash the stock rom and see if that fixes it, but I have read that once you are running a 4.3 or beyond bootloader, you WILL brick your phone if you try to downgrade. So that stops that.
Another issue is that if I try to install a different/newer bootloader in CWM, it fails every time. I also cannot flash another version of CWM or TWRP. About halfway through the process, Odin says it has failed, no matter what version of Odin, CWM, or TWRP I am using.
So the short version of this is, based on what I've listed, how do I fix this rebooting issue?
I know that this is a long post, but I'm trying not to leave anything out. If anyone has any ideas, please feel free to let me know.
Thank you in advance
Click to expand...
Click to collapse
Edit: --> I was able to install TWRP using Mobile Odin. Now I'm going to change the bootloader and see if that fixes the problem.
biga72112 said:
Hello.
This my first thread. I have done some reading, but I can't find a similar problem, so I really hope that this is posted in the correct location...
I have an odd problem with my phone. I did a flash a few months ago, and I also (attempted to) update the modem and bootloader. After the reboot, I had to begin pulling the battery to get the phone to power back on after the power was off or after a restart. I've replaced the battery, charger, and installed SEVERAL new roms, but the problem persists. I don't know if I need to do something else, or if the phone is damaged...
But if it IS a programming problem, and not physical damage, then here's the real problem...
I have installed the latest version of CWM. I am running CM 11 with Kitkat 4.4.2. I would like to just flash the stock rom and see if that fixes it, but I have read that once you are running a 4.3 or beyond bootloader, you WILL brick your phone if you try to downgrade. So that stops that.
Another issue is that if I try to install a different/newer bootloader in CWM, it fails every time. I also cannot flash another version of CWM or TWRP. About halfway through the process, Odin says it has failed, no matter what version of Odin, CWM, or TWRP I am using.
So the short version of this is, based on what I've listed, how do I fix this rebooting issue?
I know that this is a long post, but I'm trying not to leave anything out. If anyone has any ideas, please feel free to let me know.
Thank you in advance
Click to expand...
Click to collapse
If the phone powers on itself immediately the battery is replaced, i.e. without you having to press the power button, chances are 99% you have a stuck power button problem. It's not uncommon with this device and can be routinely fixed at any repair shop or by DIY if you have the right tools and technical resources.
If the phone is working OK (other than the booting issue), I'd stay off flashing bootloaders to avoid bricking
Larry2999 said:
If the phone is working OK (other than the booting issue), I'd stay off flashing bootloaders to avoid bricking
Click to expand...
Click to collapse
Thank you very much for the reply!
No its not a power button issue. I DO have to hold the power button to power on. Here's what happens when the restart fails...
I have to:
1) pull the battery
2) sometimes, I have to hold the power button WITHOUT the battery in for a few seconds (I've had laptops that have this issue before. I think it's a static buildup of some sort.)
3) reinsert the battery
4) hold the power button, and
5) if I'm lucky, the phone will boot up.
This is only about 50% successful. Sometimes I have to do this 3-4 times.
Now, I don't know if this is a hardware issue, or a firmware/software issue. If it IS a hardware problem, then I may just replace the phone. If it's a firmware/software problem, then hopefully it can be fixed. If it's a problem with the bootloader, and a fix isn't possible, then I'll just keep on truckin' till I get a new phone.
biga72112 said:
Thank you very much for the reply!
No its not a power button issue. I DO have to hold the power button to power on. Here's what happens when the restart fails...
I have to:
1) pull the battery
2) sometimes, I have to hold the power button WITHOUT the battery in for a few seconds (I've had laptops that have this issue before. I think it's a static buildup of some sort.)
3) reinsert the battery
4) hold the power button, and
5) if I'm lucky, the phone will boot up.
This is only about 50% successful. Sometimes I have to do this 3-4 times.
Now, I don't know if this is a hardware issue, or a firmware/software issue. If it IS a hardware problem, then I may just replace the phone. If it's a firmware/software problem, then hopefully it can be fixed. If it's a problem with the bootloader, and a fix isn't possible, then I'll just keep on truckin' till I get a new phone.
Click to expand...
Click to collapse
It's almost certainly an hardware issue. Very unlikely a firmware problem would cause this and even more likely the bootloader would. With a bootloader issue, your phone likely wouldn't even boot at all. Power button problems present in several ways and a loose power button could cause the kind of issues you've described. I'd take it to a local tech shop for a quick look before giving up on it.
Larry2999 said:
It's almost certainly an hardware issue. Very unlikely a firmware problem would cause this and even more likely the bootloader would. With a bootloader issue, your phone likely wouldn't even boot at all. Power button problems present in several ways and a loose power button could cause the kind of issues you've described. I'd take it to a local tech shop for a quick look before giving up on it.
Click to expand...
Click to collapse
I may just wait and get me a new phone in a few months. I'm expecting a bonus from work, and I'll likely just get the new S5. Thanks for the information
So a little background first. Over the past couple of weeks I've been having an issue where my phone just all of a sudden tells me that my sim is not recognized. Usually a power down and back up fixes it, but it's been getting worse and worse. I tried getting a new sim card but that didn't help.
So today the problem occurs again, and when I restart I get a McAffee screen telling me my phone is locked because it's been rooted (it has not). From what I can tell, the only thing it will let me do is enter a pin that I don't know. Do I have any options here, or am I totally bricked? Any help would be appreciated, I'm starting to panic.
Don't worry, your phone till okay.
the last option you can do is hard reset or try to flash stock
Edit: found similar topic here: http://forum.xda-developers.com/showthread.php?t=2796958
Hi!
So earlier today I was using the phone as usual and I decided to update some apps because I had wifi available for once.
I go to the Xposed installer and updated a youtube addon and Gravitybox, about 20 seconds later the phone freezes and turns off (before I even get to reboot myself).
Since then it continues to bootloop - I try to access TWRP and the phone just freezes on the kernel bootscreen, or restarts.
My computer won't recognize the phone and there's nothing I can do.
Sometimes my phone actually goes further than just the kernel bootscreen, it acctually boots the system, but it always freezes before I get to do anything (but the time is random)
Although the phone doesn't freeze when I'm in the recovery menu (the white one, but as soon as i click yes for twrp, it gets stuck)
I have a regular H815, BL is unlocked and im using the Genysis Rom. (Marshmallow)
What I've tried:
Access TWRP through ADB
Access TWRP through the phone ( vol down etc)
Access Download Mode, computer won't recognize the device.
Boot normally.
Remove SD/Sim and do the above.
I'm stumped guys. So I came here. Any help would be apprecieted.
Deciding to bump this popular thread by updating my progress.
I managed to make download mode work, I flashed a KDZ matching my current rom, it was successfull according to the LGUP program, but the phone is still rebooting, I cleared data, but it's still not booting up.
I later tried downgrading and wiping the whole phone. Flashed the original rom i had when I bought the device... The screen with Lg and (Bootloader is unlocked) is still the only screen I get, anything I do doesn't seem to work and I'm starting to lose hope.
Although I've noticed, that everytime I flash KDZ, it still shows the same rom of origin, even if i just flashed another, meaning the flash wasn't effective. Is there any other programs than LGup? the LG flashtool won't find it, although Up will
It seems like the phone broke completely, yet it's still actually starting up. After googling I found that there was a common flaw with it actually bootlooping because of hardware issues - which I'm starting to think is the issue.
What S/N is it? ..if its starts with 505-509 it definitely has the hardware problem that causes the device to bootloop which you can read about in reddit(there are tons of reports there) also by quick searching in this same forum you can see threads of report of same issue... this is a known issue and LG themselves announce that there was a solder of some kind that causes the bootloop...if its still on warranty I suggest you go with that. They usually change the mobo itself to latest 601-60* and probably the screen if your having burn ins on the lcd..goodluck
innocence07 said:
What S/N is it? ..if its starts with 505-509 it definitely has the hardware problem that causes the device to bootloop which you can read about in reddit(there are tons of reports there) also by quick searching in this same forum you can see threads of report of same issue... this is a known issue and LG themselves announce that there was a solder of some kind that causes the bootloop...if its still on warranty I suggest you go with that. They usually change the mobo itself to latest 601-60* and probably the screen if your having burn ins on the lcd..goodluck
Click to expand...
Click to collapse
It's definetly a 505... lol.
y bootloaders been unlocked, meaning warranty is void. How would you reccomend hiding the fact its UBL?
Perhaps I could dirtyflash it with the wrong kernel, making it completely bricked. And just cluelessly leave it for warranty, but although I feel like that's a risk.
As far as I know there is no going back once you Unlock your bootloader and no warranty will be given whatever you do as IMEI of your phone is sent to LG when you unlock the device thru their site so when you do claim your warranty they will check to see if yours are unlock/lock. If you still push for a warranty they will charge you 200-250 dollars(estimated cost in our country) for the mobo replacement. Friendly advice, since its a paperweight now you could just sell it on ebay for 80-100 so dollars and buy a new phone.
Heya folks,
So my HTC 10 just randomly crapped out on me a few weeks ago. Been trying a few things to try to flash a new ROM on there, but I'm not having much luck and need advice. I was using my phone like I would any other time and all of a sudden the phone froze and restarted, but when it restarted it was taking forever to load back up (was just stuck at the HTC logo). I tried turning it off and on again and realized the thing was bootlooping on me. It wouldn't boot into system, download, recovery, nothing.
Now, here's the issue. My phone's S-ON and the bootloader is Locked. I've never done anything to the software on it before (but for some reason the software status is "Modified", which is weird. I did buy this phone used, so that could mean something, but I've never seen a modified software status on a bootloader that was not unlocked). The symptoms are pretty weird. I tried flashing the ROM using an official HTC RUU EXE, but the thing keeps saying that my phone is below 30%, and when I charge the phone it always starts charging at 22% (all the more reason I think the software is just completely kaputs). I found this thread where people were talking about the SD Card solution, but I'm quite sure the only way this would work is if my bootloader is unlocked.
So what do you guys think? Am I in a catch 22? Am I missing something? Any and all replies or questions would definitely help.