First i ran the phone with stock 4.0.2, and one morning when i woke up(the phone was in the charger) the phone was in a boot loop(turned off when the google letters came up), so I ended up with a factory reset.
Some days later I rooted the phone and installed AOPK rom and installed google apps. 2 days later it got into a boot loop again, but now it booted all the way till where I tyoe in the SIM code, if I did it really fast I could also get past the sim code but just seconds after it booted again. I tried everything from CWM, restore an older backup, wipe cache/data but the phone couldn't find the boot or something like that. So ended up push adb stock rom.
Is this something thats normal? I got 2 friends with the same phone, never had any problem, they both run stock 4.0.2.
I too had a problem with my Gnex, it kept freezing up and switching off, if you are getting this problem on stock and custom roms its likely hardware, so send it off to Sammy, just a heads up but mine was sent off 10.02.12 first time then 2 more finally they said thay would replace it .... That was a month ago, rang them yesterday and they said it would be another week .. what I'm getting at if your insurance could offer a quicker fix I'd go with that
Have you tried flashing google's stock images and going from there?
Yeah, I did flash 4.0.2 stock again from that site, been running it for 2-3 days now.
Related
Hi all,
I was running CM7rc3 for quite a while and wanted to see what 2.3 was like with sense so I flashed back to my backup to stock and attempted to update, didn't work, tried the unroot process and stuff, still couldn't get it going, so I thought f it and tried to put CM7 back on. I turned S-OFF and what not, went into clockwork recovery, cleared the data/cache installed from zip.
It said installed and I rebooted, only to have the HTC logo come up and it hung there for 40 mins before I took the battery out and tried again... Still no luck.
So now I can't boot my phone and I have lost my original back up.
I have recently moved cities and really need my phone up asap.
What can I do?
all good, managed to find a stock rom online for my service provider and get it going again
I was updating some apps in the market, as suddenly the phone reboots without any warnings.
OK, **** happens i thought and let it boot. But now the phone starts the ROMs boot animation for about 4-5 seconds and then reboots over and over again.
I pulled the battery and started into recovery. I made a nandroid and wiped cache and dalvik. Reboot with same behavior.
Recovery again: wiped everything and flashed a new AOKP M3 - result: reboot and loop again
Back to recovery: tried to flash the before made nandroid - MD5 checksum error
Flashed an older nandroid and got boot loops again.
So, i think this piece is for the service now...
What is the best way to reset this GN? Using ToolKit to put back stock recovery and lock the bootloader? Or should i try something else?
Update:
Flashed Stock Google Image via ToolKit 5.4 and after that the phone is booting normal?!?
I reflashed the touch recovery and pushed the AOKP build 27 back to the phone and flashed it.
So far so good - I have to start from the bottom now, because flashing the stock rom wiped the whole phone and EVERYTHING on sdcard is gone
Do you think there is a hardware failure? Perhaps some sort of memory malfunktion or something like that?
Same thing just happened to me, thi is the second time
lighthammerhh said:
I was updating some apps in the market, as suddenly the phone reboots without any warnings.
OK, **** happens i thought and let it boot. But now the phone starts the ROMs boot animation for about 4-5 seconds and then reboots over and over again.
I pulled the battery and started into recovery. I made a nandroid and wiped cache and dalvik. Reboot with same behavior.
Recovery again: wiped everything and flashed a new AOKP M3 - result: reboot and loop again
Back to recovery: tried to flash the before made nandroid - MD5 checksum error
Flashed an older nandroid and got boot loops again.
So, i think this piece is for the service now...
What is the best way to reset this GN? Using ToolKit to put back stock recovery and lock the bootloader? Or should i try something else?
Update:
Flashed Stock Google Image via ToolKit 5.4 and after that the phone is booting normal?!?
I reflashed the touch recovery and pushed the AOKP build 27 back to the phone and flashed it.
So far so good - I have to start from the bottom now, because flashing the stock rom wiped the whole phone and EVERYTHING on sdcard is gone
Do you think there is a hardware failure? Perhaps some sort of memory malfunktion or something like that?
Click to expand...
Click to collapse
Firstly when you get bootloops or any other problem do NOT do a nandroid as it backs up EVERYTHING, including the problem.
When you "wiped everything" did you go to mounts and storage and format system, cache and data?
If not then you didn't do a proper full wipe.
This is my own experience, but I want to warn you guys. I had a similar problem with my GNex. The first time it happened, my phone rebooted itself every 5 seconds. I completely restored it using factory image and it ran fine for 3 weeks, then one day, the phone just rebooted itself and got stuck at the boot image. I had to factory reset it again to make it work.
After the second time, I called Samsung and sent it in for repair last week. They are shipping me a replacement unit. It seems the problem was hardware related.
econometrician said:
This is my own experience, but I want to warn you guys. I had a similar problem with my GNex. The first time it happened, my phone rebooted itself every 5 seconds. I completely restored it using factory image and it ran fine for 3 weeks, then one day, the phone just rebooted itself and got stuck at the boot image. I had to factory reset it again to make it work.
After the second time, I called Samsung and sent it in for repair last week. They are shipping me a replacement unit. It seems the problem was hardware related.
Click to expand...
Click to collapse
For 3 weeks... exactly 3 weeks, 21 days?
I can tell you that my first boot loop brick was 20 days after I bought the phone. The second was later that day. But the third one was... again, 20 days after the last successful restore. Is there something magical about the 3-week mark???
I am currently taking nightly nandroid backups, so when I had my third boot loop brick my backup was just under a day old. If this is ultimately a hardware problem that can be warrantied, I guess I'll have to try that next time. I would have to make sure I return it with the bootloader locked, stock recovery, but without the wipe because it has to still be boot looping to prove there's an issue!
Anyway, things I will point out:
- It's the complete wipe in bootloader that blanks the internal storage.
- If you have CWM installed, you can back up the internal storage over USB via adb pull /sdcard/ ./sdcard/ (correct me if I got the syntax wrong)
- When the boot loop brick has happened, CWM is not capable of properly reformatting or restoring to the data partition. I have not found a way to repair it without blanking /sdcard (which on the GN is actually in /data/media), so if you don't want to lose those files the only way to keep them is to pipe them out, blank the phone, and then pipe them back in afterwards.
- After a complete wipe in bootloader (either by flashing userdata.img or by relocking/unlocking bootloader), you must boot the phone once into the OS in order to complete the reformatting of /data. If you try booting straight into recovery after a wipe in the bootloader, CWM cannot read or write from that partition.
Can't say for sure whether it's exactly 21 days but it's definitely around 3 weeks. Why don't u give Samsung a call? The phone is not supposed to behave this way. Plenty of people don't have this problem. My wild guess is that the internal flash memory is faulty.
econometrician said:
Can't say for sure whether it's exactly 21 days but it's definitely around 3 weeks. Why don't u give Samsung a call? The phone is not supposed to behave this way. Plenty of people don't have this problem. My wild guess is that the internal flash memory is faulty.
Click to expand...
Click to collapse
I'll warranty it through my carrier next time as they do exchanges on site. The trouble is, once I've recovered the phone, there's no evidence of the problem anymore. The best way to prove it is to show it fritzing out.
Sent from my Galaxy Nexus using Tapatalk
I think this is a known problem. You shouldn't have to prove it to them. They should be aware of it.
It bricked again today so I warrantied it in-store at my carrier. They gave me a brand new one after being unable to find a solution when fiddling with it. As a bonus, all the little hairline scratches on my screen are gone too
The store guy said he's never seen this issue, and it's one of only two warranty locations for my carrier in the Vancouver area. So I can only hope this was a rare hardware problem and not something that pervades every GN they're going to sell.
I can tell this one is from a different batch because it came preloaded with 4.0.2.
Good for you. hopefully my new phone will behave
Hi,
I had installed custom ROM developer by @Ziyan 5.1.1. I believe it was AOSP (ROM link) around 5-6 months back. Everything was working correctly.
Last friday night it switched off and since, then it hasn't started up yet. Sometimes the home screen comes but it immediately reboots. It is continuously rebooting and i have to remove the battery from stopping itself from rebooting.
I tried going back to official stock rom 4.3 and used the command fastboot -w flashall and everything happened correctly..atleast that's what it said on the command prompt but it still the phone tries to boot up the 5.1.1 version. It's been a week and i haven't been able to get past this issue. I gave it in the service centre but even they haven't been able to get past the issue.
What issue are you guys suspecting ? Any help would be greatly appreciated !
Thanks,
Adithya
I came back to look here and it is sad to still see phones die this way.. I am sorry dude.. You can try to lock the bootloader and if it is still unlocked upon rebooting the EMMC is fried (internal storage). The only solution is a new motherboard..
I'm stuck and confused:
Had a Nexus 4 and 5 for years. Decided to upgrade this past November to the LG G4 (T-Mobile H811)
Got it to root without touching the boot loader.
In came MM and then I had issues of repeating the process.
I came across a solution, to unlock my bootloader. So I did it and managed to get my G4 rooted while running stock LG MM (H81120i).
Everything was running well for several months, but then I started to see erratic behavior. It would heat-up in my pocket for no reason. It would not save pictures. Connections via WiFi and LTE were breaking up. All in all, I wasn't happy and I missed the stock Google interface.
So I've decided to install CM13. Had many issues of getting it to work for several days, which included persistent closings of Google Play services (and many others) and not being able to make/receive calls (it would automatically reboot) After several different attempts, I managed to get it all working. Cleared/Wiped everything off my internal drive, installed the "LG-H81120i-Flashable.COMPLETE" and "cm-13.0-201605xx-NIGHTLY-h811" and "open_gapps-arm64-6.0-nano-201605xx", all back to back. And then installed manual everything as needed Gmail, Maps, etc.
Everything worked great for about 2-days, until then next morning my screen locked up. Then the phone rebooted. After the reboot, it lasted for about 10-15 seconds in CM13 and rebooted again manually. Continued to reboot over and over, till it then stopped booting with CM13. I thought that maybe I needed to install the latest CM13 zip file, but found I couldn't get into recovery. The first reboot screen, showing "Bootloader State: Bootloader unlocked? and the LG logo would be in a loop. During that time, I could feel the phone getting hotter and hotter.
Sometimes, the phone would boot up into CM fully and last for 5 to 10 minutes. Then reboot again and stay in the first reboot screen.
I managed to get into TWRP recovery and thought that putting back the stock MRA58K image would help. During the install in recovery, the phone rebooted! I never thought it could do that. Eventually I got the stock LG back-up up and running, but it didn’t help, and same rebooting occurred.
I'm stuck and out of options. I would like to get the phone BACK TO STOCK and then perform an RMA. I’m afraid that with the BOOTLOADER UNLOCKED that my RMA will be denied and I’m stuck with what I have.
So can the H811's bootloader be re-locked?
PiCASSiMO said:
I'm stuck and confused:
Had a Nexus 4 and 5 for years. Decided to upgrade this past November to the LG G4 (T-Mobile H811)
Got it to root without touching the boot loader.
In came MM and then I had issues of repeating the process.
I came across a solution, to unlock my bootloader. So I did it and managed to get my G4 rooted while running stock LG MM (H81120i).
Everything was running well for several months, but then I started to see erratic behavior. It would heat-up in my pocket for no reason. It would not save pictures. Connections via WiFi and LTE were breaking up. All in all, I wasn't happy and I missed the stock Google interface.
So I've decided to install CM13. Had many issues of getting it to work for several days, which included persistent closings of Google Play services (and many others) and not being able to make/receive calls (it would automatically reboot) After several different attempts, I managed to get it all working. Cleared/Wiped everything off my internal drive, installed the "LG-H81120i-Flashable.COMPLETE" and "cm-13.0-201605xx-NIGHTLY-h811" and "open_gapps-arm64-6.0-nano-201605xx", all back to back. And then installed manual everything as needed Gmail, Maps, etc.
Everything worked great for about 2-days, until then next morning my screen locked up. Then the phone rebooted. After the reboot, it lasted for about 10-15 seconds in CM13 and rebooted again manually. Continued to reboot over and over, till it then stopped booting with CM13. I thought that maybe I needed to install the latest CM13 zip file, but found I couldn't get into recovery. The first reboot screen, showing "Bootloader State: Bootloader unlocked? and the LG logo would be in a loop. During that time, I could feel the phone getting hotter and hotter.
Sometimes, the phone would boot up into CM fully and last for 5 to 10 minutes. Then reboot again and stay in the first reboot screen.
I managed to get into TWRP recovery and thought that putting back the stock MRA58K image would help. During the install in recovery, the phone rebooted! I never thought it could do that. Eventually I got the stock LG back-up up and running, but it didn’t help, and same rebooting occurred.
I'm stuck and out of options. I would like to get the phone BACK TO STOCK and then perform an RMA. I’m afraid that with the BOOTLOADER UNLOCKED that my RMA will be denied and I’m stuck with what I have.
So can the H811's bootloader be re-locked?
Click to expand...
Click to collapse
Since you live in the US your only option is to apply over voltage to the battery terminal and burn the mobo so that it wont even boot up. The exact method is somewhere around here in xda so you should look it up since you have no other choice
Edit: To answer your question: No
sirsomething said:
Since you live in the US your only option is to apply over voltage to the battery terminal and burn the mobo so that it wont even boot up. The exact method is somewhere around here in xda so you should look it up since you have no other choice
Edit: To answer your question: No
Click to expand...
Click to collapse
If I can't re-lock the bootloader, has anyone had the success of returning their phones under warranty? Through T-Mobile?
Hi guys, bit of a saga here so bear with me...and also it should be mentioned I have little experience/understanding of tech stuff, so that isn't helpful either lol
I've had a Nexus 5x running 7.1.2 for not quite a week; it came with an unlocked bootloader (strangely). Tried to do the usual install twrp & root as I've done with previous phones (all pre-nougat) but all attempts failed. Couldn't boot into stock recovery from the bootloader at all, it would just boot into the system. OK, next thought was that an OTA upgrade to Oreo might work to restore a recovery - but got the BLOD (naturally lol). I found a fix in a modded 4-core Twrp 3.2.1 -0 fbe img + workaround injector zip from osm0sis & XCnathan32 which by some miracle worked.
So far, so good. Ffwd a few days and google play store keeps crashing on opening; I had the feeling that some glitch happened while it was updating, so I tried all the usual fixes like app cache/data wipes and uninstall updates/renistall google play, delete google account etc which failed. Next I tried a cache & data device wipe through twrp - also unsuccessful. Finally, I thought the only thing left to try would be to restore a backup I made on twrp - this led to the current issue of not booting, stuck on the google logo screen. I even thought what the hell! and attempted a factory reset with twrp - same result, where I am now. Google logo screen, however I still have an unlocked bootloader.
Would anyone be able to suggest where I might go from here? I'm pretty sure the version is N2G48C, if that helps.
Any suggestions very much appreciated...wouldn't mind getting to the 1 week mark with a functioning phone lol
Saga #2
Still no idea what's going on. I realised that I'd backed up and recovered the system and vendor .img files, which according to this thread would be a cause of the issue https://forum.xda-developers.com/nexus-6p/help/stuck-google-logo-twrp-backup-restore-t3320840/page3
So I made another backup without those images, did a full wipe and restored it - still does not boot, still only sitting on the google logo. Tried next to open a cmd terminal to see if I could reflash a stock image, but adb could not connect (maybe because the phone would have been on charging and not file transfer mode?)
Last resort as I saw it was to try the NRT, and see if it would flash stock via the bootloop/softbrick option. Process seemed to be OK, judging by the log - but it did not reboot to the system. Now there is a looping bootloop between the google logo and the unlocked bootloader warning.
Following wugfresh's instructions to factory reset from the recovery (the phone won't turn off via the power button so I just booted straight into the bootloader) Looked for the recovery option, selected....and nothing!!
So there isn't a stock recovery??? How does that work?
And what hope is there for this phone now? (I can't think of anything else )
Anyone have an idea? I've never heard of this before tbh!
Well, my problem has been sorted. In the absence of knowing what the hell I should do lol I managed to get a refund for the phone even though it was a refurb to begin with (something to be said for an honest seller who provides a 3 month warranty!) and I picked up a brand new N5x, which was unboxed on Tuesday. Not even 6 hours into setting it up, the phone started to get progressively hotter and then went into bootloop. Got into the bootloader and tried a factory reset - all seemed OK but halfway through the setup process it bootlooped again. Fortunately it was still within the 2 year warranty, and LG didn't argue about authorising a repair for a phone which didn't get even half a day's use on it lol
Authorised Wednesday, walked into the service centre Thursday and a 1 hour wait later had phone in hand with the PCB/motherboard replaced. Has been working fine (and cool!) ever since. Definitely feel lucky to have hopefully dodged a bullet on this one.
Bonus that they upgraded from 6.0 to 7.2.1 while they were at it; apparently LG considers nougat the "latest" stable version for the 5x.