Related
Hi guys,
after two days of unsuccessful trying I really need your help now. I was owner of a HD2 Leo and am used to flashing roms and stuff, so I'm not a total noob - anyway:
I bought a Galaxy Nexus on eBay. The seller wrote that the phone itself work, but there it's only on airplane mode. I bought it and thought with flashing it would be fine.
The problem is:
Baseband-Version: unkown
Network: unkown
IMEI: unkown
I am not been asked for a PIN when turning on the device. No network connection is available.
In two days I tried:
- Galaxy Nexus Toolkit > flashing Google Stock 4.0.1, 4.0.4 and 4.1.1
- Flashing several Radios including i.E. UGLC1 via Fastboot
- This thing here: [TOOLS] Unbrick dead Samsung GT-i9250 Galaxy Nexus 32GB / Prime via USB cable http://forum.xda-developers.com/showthread.php?t=1640443&page=1
I actually don't know how to continue and from todays view I bought an expensive MP3-Player for 250 bucks.
I would really appreciate if you guys could help me out.
Thanks in advice.
- Sebastian
Uh, EFS partition is borked.
Look at this thread, maybe the restoring IMEI part is relevant.
Pew ... this loos tricky. I'll try that.
baseband unkown IMEI unkown
Mach3.2 said:
Uh, EFS partition is borked.
Look at this thread, maybe the restoring IMEI part is relevant.
Click to expand...
Click to collapse
I have looked at this and also tried it but with no luck it seems. I really need help can someone offer me some advice. My Gn also keeps rocking between radio off and radio on.
Thanks
Download from play store: get ril
Sent from my Galaxy Nexus using xda app-developers app
ntorresla said:
Download from play store: get ril
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That will not do anything for the issue described.
Sent from my Galaxy Nexus using Tapatalk 2
As I already wrote in another topic - had the same problem and at last brought my nexus to the service. They changed motherboard and said that this problem is not related to broken efs partition, as I was thinking before.
Sent from my Galaxy Nexus using xda premium
edijs said:
As I already wrote in another topic - had the same problem and at last brought my nexus to the service. They changed motherboard and said that this problem is not related to broken efs partition, as I was thinking before.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It could be related, it's either broken hardware or corrupted /factory folder.
The files in the /factory folder holds your IMEI, it's proven beyond doubt.
Beamed from my Grouper.
Galaxy Nexus baseband issue
Hi, I have the same issue.
The phone was working fine and it just stopped working. So I flashed the factory images once again but no luck.
Then I suspected EFS partition issue but after rooting, I could list the files under /factory, cat/read the md5 files, copy them etc. So I think EFS is not the issue but don't know what has gone bad.
Still my phone is not working
Found this, dunno if it'll help, though...
http://forum.xda-developers.com/showthread.php?t=1510906
http://forum.xda-developers.com/showthread.php?t=1428988
Fixed by sending in for warranty
Just an update...I was having all of these symptoms...unknown IMEI, Baseband, etc...basically gave me an expensive media player for a few months while waiting for a fix on XDA. After no update I decided to call up Samsung and after talking to 3 different technicians, I was able to send it in. Just a note for anyone about to do the same, they will try very hard to blame it on the carrier/SIM card, so save yourself some trouble and just say you already went to the physical store of your carrier (calling isn't enough)and they couldn't get it working. Once you get past that, they will email you a printable 2-day UPS shipping label so you can ship it to them for free. It took 2 weeks from the time I called to having a working phone back in my hands.
This was their fix:
Problem found:
NO PCS SERVICE
Solution:
REPLACED PBA
After a quick search I found that the PBA is the motherboard, so it's definitely a hardware issue. Hope you guys are still under warranty because I've heard this is ~$200 to fix otherwise.
Good luck.
My Galaxy Nexus got run over by a car, and the screen was damaged pretty bad. I understand that it can't be repaired and that I'll be lucky to get anything off of it, but I'm hoping since the boards inside weren't damaged much that a data recovery company might be able to pull off my data. The reason for my question is that when I spoke to them they asked me and I didn't know the answer so I'd like to get a clear understanding from someone who knows.
Does the Galaxy Nexus have a flash memory controller or does it have an uncontrolled MTD chip? Judging from the fact that it's got a couple ext4 partitions (according to this post http://forum.xda-developers.com/showthread.php?t=1469490 ) I would guess it's a controlled chip but I just want to make sure.
Also does the fact that it's under "/dev/block/mmcblk0" mean that it uses an MultiMedia Card controller?
Finally if it is a controlled device that means that if the controller is damaged the data is irretrievable right? Is the controller part of the Samsung multi-memory chip or is it separate on the board?
When I get back to them I want to give them as much information as I can so answers to any or all of these questions would be greatly appreciated.
P.S. If anyone knows of a good data recovery service in Canada that they could recommend I'd greatly appreciate it. I understand it won't be cheap but all of the ones I've seen are ridiculous (like $300 dollars to undelete files on a windows OS which you can do with free software in 10 minutes)
UPDATE:
Confirmation reflow fixes 5x hardware bootloop
http://forum.xda-developers.com/nex...-cause-fix-t3476794/post70123267#post70123267
UPDATE:
If you are having what appears to be hardware bootloop problem update this Poll
https://goo.gl/forms/Ga8gZgG7GEgBIply1
or see results
https://docs.google.com/forms/d/e/1...D4IdwEWZYb2NKA/viewanalytics?usp=form_confirm
====
I was looking into the eMMC chip on this phone on the assumption it was causing the bootloop. I wanted to look at other phones that have the same Toshiba HS400 chip we use. I found some references to LG G4 and then started seeing LG G4 phones were also having a bootloop problem with similar symptoms, phone just turns off all of a sudden then is stuck in bootloop.
This led to finding articles that LG acknowledged a hardware problem with solder connections on the LG G4 mainboard.
I am wondering if this is the same problem affecting Nexus 5x since the LG G4 is pretty much a cousin of the 5x.
I don't know for sure this is the problem we are seeing, just a potential culprit.
This article has more information
http://www.trustedreviews.com/opinions/lg-g4-bootloop-problem-how-to-diagnose-and-fix
In the article there is mention of a special TOT file that can be flashed on the G4 that turns off the big cores and lets the phone boot in a slow mode running on just the small cores.
This video shows you can use a SMD rework station to heat up the CPU and eMMC memory chip, reestablishing the solder connections underneath the chips and getting your phone to work again.
https://www.youtube.com/watch?v=jeuMBD9r4GI
This is the statement LG made about the LG G4
http://www.androidauthority.com/lg-g4-bootloop-petition-669421/
Here’s the full statement LG made to Android Authority:
LG Electronics has been made aware of a booting issue with the LG G4 smartphone that has now been identified as resulting from a loose contact between components. Customers who are experiencing booting issues with their LG G4s should contact their local carrier from where the G4 was purchased or a nearby LG Service Center (www.lg.com/common) for repair under full warranty.
Customers who purchased their G4 devices from non-carrier retailers should contact an LG Service Center with the understanding that warranty conditions will differ. LG Electronics is committed to providing the highest standards of product quality and customer service and apologizes for the inconvenience caused to some of our customers who initially received incorrect diagnoses.
Click to expand...
Click to collapse
sfhub said:
I was looking into the eMMC chip on this phone on the assumption it was causing the bootloop. I wanted to look at other phones that have the same Toshiba HS400 chip we use. I found the LG G4 used the same chip and then started seeing LG G4 phones were also having a bootloop problem with similar symptoms, phone just turns off all of a sudden then is stuck in bootloop.
This led to finding articles that LG acknowledged a hardware problem with solder connections on the LG G4 mainboard.
I am wondering if this is the same problem affecting Nexus 5x since the LG G4 is pretty much a cousin of the 5x.
I don't know for sure this is the problem we are seeing, just a potential culprit.
This article has more information
http://www.trustedreviews.com/opinions/lg-g4-bootloop-problem-how-to-diagnose-and-fix
In the article there is mention of a special TOT file that can be flashed on the G4 that turns off the big cores and lets the phone boot in a slow mode running on just the small cores.
This video shows you can use a SMD rework station to heat up the CPU and eMMC memory chip, reestablishing the solder connection and getting your phone to work again.
https://www.youtube.com/watch?v=jeuMBD9r4GI
Click to expand...
Click to collapse
I do know that LG gave me a new motherboard in my Nexus 5X
Hi. I tested my 5x https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=pl. It showed that emmc is Toshiba 032G74. Test passed without problems. I haven't updated to 7 yet, because I would like to avoid eventually problem with bootloop.
Wuzimu said:
Hi. I tested my 5x https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=pl. It showed that emmc is Toshiba 032G74. Test passed without problems. I haven't updated to 7 yet, because I would like to avoid eventually problem with bootloop.
Click to expand...
Click to collapse
The problem that was pointed out for the LG G4 cousin of this 5x phone is not that the eMMC chip is defective, rather the solder connection to either the eMMC or the CPU is faulty, so in that case it wouldn't matter which eMMC chip you had.
I am trying to get some discussion about what the cause of the problem is on the 5x using the G4 bootloop problem as a starting point.
As to the eMMC info, if you want the information about your emmc you can also do
Code:
su
cd /sys/bus/mmc/devices/mmc0:0001/
cat name date fwrev hwrev manfid oemid
032G74
07/1999
0x0
0x0
0x000011
0x0100
also you can reboot your phone and type
Code:
bullhead:/ $ dmesg | grep mmc0
[ 1.914434] mmc0: no vqmmc regulator found
[ 1.914459] mmc0: no vmmc regulator found
[ 1.914736] mmc0: SDHCI controller on f9824900.sdhci [f9824900.sdhci] using 32-bit ADMA
[ 2.046259] mmc0: BKOPS_EN bit = 0
[ 2.063777] mmc0: new HS400 MMC card at address 0001
[ 2.064305] mmcblk0: mmc0:0001 032G74 29.1 GiB
I found this post on google forum.
#210 [email protected]
Fixed !
A little bit tricky:
- Unlock your phone (this will wipe your data)
- Flash the lasted Nougat release NRD90S with the wipe option (fastboot -w ...) You have to flash all the partitions including userdata.
- Boot
- Do a factory reset, this is important, in some case, the userdata partition has a wrong size.
- Done !
It seems that the last OTA Nougat update bricks the phone. This not an hardware issue in my case.
Google, I hope that the next OTA update won't brick the phone !
Click to expand...
Click to collapse
Is there any info about Nexus 5x or LG G4 reliability (ratio manufactured / repaired or bootloop) like the one in hard drive reliability report? I'm curious how many phones actually got real hardware problem with this nougat bootloop because it seems google / LG hasn't responded quickly for this problem or at least address the root cause of it.
Wuzimu said:
I found this post on google forum.
Click to expand...
Click to collapse
Not all bootloops are hardware problems.
If people experience a random reboot, then bootloop issue using total stock with locked bootloader, this is almost definitely a hardware issue.
This is further confirmed if they go through the effort of flashing TOT file using LGUP and it still doesn't work. With that extra step and the above conditions, it can almost be guaranteed it is a hardware problem.
If one has unlocked bootloader and has been playing with different kernels, restoring stuff in TWRP, switching back between nougat and marshmallow, etc. then yes it could be software problem.
BTW in that post the person indicated needing to do factory reset because the userdata size is wrong. That indicates he at one point flashed the userdata partition by hand, because if you flash the userdata as part of the zip file using -w option (ie what the factory image script does) you will never have the problem of userdata being wrong size.
innov said:
Is there any info about Nexus 5x or LG G4 reliability (ratio manufactured / repaired or bootloop) like the one in hard drive reliability report? I'm curious how many phones actually got real hardware problem with this nougat bootloop because it seems google / LG hasn't responded quickly for this problem or at least address the root cause of it.
Click to expand...
Click to collapse
There is a petition for LG G4 where people were signing on to get LG to replace the G4s. It is unclear if everyone signing on was affected or not but they were up to 8k signature.
https://www.change.org/p/lg-mobile-launch-a-replacement-program-for-defective-lg-g4s
Android Authority mentioned LG acknowledged the problem and would fix phones affected but the details seemed kind of lacking. Main issue being if these would be fixed outside of warranty.
http://www.androidauthority.com/lg-g4-bootloop-petition-669421/
Here’s the full statement LG made to Android Authority:
LG Electronics has been made aware of a booting issue with the LG G4 smartphone that has now been identified as resulting from a loose contact between components. Customers who are experiencing booting issues with their LG G4s should contact their local carrier from where the G4 was purchased or a nearby LG Service Center (www.lg.com/common) for repair under full warranty.
Customers who purchased their G4 devices from non-carrier retailers should contact an LG Service Center with the understanding that warranty conditions will differ. LG Electronics is committed to providing the highest standards of product quality and customer service and apologizes for the inconvenience caused to some of our customers who initially received incorrect diagnoses.
Click to expand...
Click to collapse
I had this bootloop too, after updatong to 7.0. I spent whole day to repair my phone. Wipe, and flashing diffrent images did not work, even twrp backups with working efs. After 20 times of flashing stock images + another twrp backup phone just suddenly booted fine, and working to this day without any problem.
Soo DONT GIVE UP GUYS!
Siljorfag said:
I had this bootloop too, after updatong to 7.0. I spent whole day to repair my phone. Wipe, and flashing diffrent images did not work, even twrp backups with working efs. After 20 times of flashing stock images + another twrp backup phone just suddenly booted fine, and working to this day without any problem.
Click to expand...
Click to collapse
Sometimes if it is emmc eventually it locks out enough bad blocks to start working again.
sfhub said:
Sometimes if it is emmc eventually it locks out enough bad blocks to start working again.
Click to expand...
Click to collapse
Yeah i got mines from Google, so i would rather just replace it, plus i got a few scratches on the screen.
I'm in the same boat. I was scrolling through Instagram when the phone froze, restarted, and then just kept restarting without being able to get past the Google logo. I was on stock 7.0 (but August or September security update), stock kernel, but rooted with SuperSU 2.76 and TWRP 3.0.2-1. I couldn't even boot into TWRP, it would bootloop at the Google logo just the same. After placing it in the freezer for 30min to an hour I was able to boot into TWRP long enough to save all my data. (My original thread: http://forum.xda-developers.com/nexu...osing-t3479986)
Google also sent me a replacement, manufactured 10/2015, the original being 09/2015. I'm afraid this will likely happen again! The problem is we only get the original warranty, so I have until January 21st, 2017.
Flyview said:
The problem is we only get the original warranty, so I have until January 21st, 2017.
Click to expand...
Click to collapse
Wait really? Google said that? If so then my replacement I got a couple weeks ago runs out end of the month. That's kind of BS since its a totally different device.
Sent from my Nexus 5X using Tapatalk
EeZeEpEe said:
Wait really? Google said that? If so then my replacement I got a couple weeks ago runs out end of the month. That's kind of BS since its a totally different device.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Yea I asked them twice but please confirm and report back.
Sent from my Nexus 5X using Tapatalk
Flyview said:
Yea I asked them twice but please confirm and report back.
Click to expand...
Click to collapse
Not directed at you, but honestly, for this type of problem, where it is almost definitely a manufacturing defect in components or assembly, I think the least they could do is give you a full warranty from the replacement date. It isn't like you are the only example of this.
If people wanted to organize, from the standpoint of publicity, things could look a lot worse with the media looking for stuff like this after Note 7 and now some reports of iPhone 7 batteries issues.
LG/Google have their own melting USB port problem in addition to the solder joints and/or eMMC chip problem.
Does anyone got this problem with custom rom or just on stock?
slobo2712 said:
Does anyone got this problem with custom rom or just on stock?
Click to expand...
Click to collapse
If it's really a hardware issue (which it seems like) then it doesn't matter which one.
Sent from my Nexus 5X using Tapatalk
Same here. My 5x rebooted on chrome on stock 7.1.1 and on the next boot it has frozen with graphics artefacts on google logo. On the next restart frozen again after few seconds on the settings tab. Before the die, i've reverted to 6.0 and locked the bootloader. After that definetely died. The graphics artefacts led me to think about an hardware issue...
Just realized you had a survey, filled it out, and checked out the results. Good info.
Sent from my Nexus 5X using Tapatalk
Going back to M will not reduce the risk?
Hello guys,
My 5X is infected by this "bootloop" issues which I posted here https://forum.xda-developers.com/nexus-5x/help/help-screen-freeze-stuck-lines-reboot-t3528689, well I manage to temporary fixed it but yeah sometimes it still reboot or hang by itself like once in a week.
I know it's not a big deal but I'm afraid it will lead to something worse in the future, so I think I should try to fix the hardware.
Some people says it was the EMMC thou other say it gotta be something else, then I asked one of phone repair technician in my place to help to fix the EMMC, well after I told him, he agreed that it's has problem with the EMMC. So he offer to change the EMMC with the one from Samsung, but as I look into the spreadsheet the original one is made by Toshiba, then he tell me that it will make no difference since they both are made for phone.
So I'm asking for help from anyone who knows about this technical or maybe an expert at repairing a phone is it true ?
Is there anything to notice before changing the EMMC on the phone ? like the EMMC specification ? since the Toshiba one has "5.0" on it and I'm sure it meaning something but I couldnt figure it out.
Please any advice will be appriciated.
Thanks in advanced.
please help anyone ? or someone with experienced in tearing down the phone components ?
I owned G3 before i facing screen faded,bootloop
first method i use piece of paper to push EMMC it work for few day
second method i reheat EMMC with baker for 8min 200'c it work for a week then i sell it
you should reheat you EMMC and add pressure to EMMC to make more contact in mainboard.
Duckscreen said:
I owned G3 before i facing screen faded,bootloop
first method i use piece of paper to push EMMC it work for few day
second method i reheat EMMC with baker for 8min 200'c it work for a week then i sell it
you should reheat you EMMC and add pressure to EMMC to make more contact in mainboard.
Click to expand...
Click to collapse
thanks for your response
so are two of those method just works for temporary ?
do you know by a chance that it is possible to change the EMMC with another EMMC different from the original one ?
Here!
https://www.xda-developers.com/nexus-5-hardware-modded-to-64gb-internal-storage-by-replacing-emmc/
second method i reheat it but i didnt add pressure on the chip so you might try it,before change the emmc.
Heat it up and press on the chip to make more contact on mainboard
when you press try to not move to chip it might malfunctional.
Duckscreen said:
Here!
https://www.xda-developers.com/nexus-5-hardware-modded-to-64gb-internal-storage-by-replacing-emmc/
second method i reheat it but i didnt add pressure on the chip so you might try it,before change the emmc.
Heat it up and press on the chip to make more contact on mainboard
when you press try to not move to chip it might malfunctional.
Click to expand...
Click to collapse
I tried to pm you but it appear I can't
So here it is....I want to try your method about heating the chip but I need to ask few questions and hope you help me on this.
How much temperature needed to heat the chip and how long it took ?
Is it the processor chip or the emmc one ?
Thanks in advance.
8min at 200 degrees Celsius.
Sent from my Pixel using Tapatalk
Hello, I have a somewhat odd issue, so please bear with me and I apologize in advance for the long post.
I have a Google Pixel 2XL that began flashing at the lock screen. After about 30 flashes it restarts and says it can not load the android system. Here is a youtube video with the exact problem I'm having I can't post an outside link but if you search "NLrI6bIsTNM" on youtube it will come up.
I'm honestly not worried about the phone itself, but am looking for a way to save my photos and other possible data before wiping and/or sending in for replacement. My father recently passed away and my last pictures of us are on there as well as pictures from my engagement overseas etc. Pictures NOT backed up on google photos.
Though I do have USB debugging turned on, the bootloader is locked on this phone, so I can not get into ADB recovery mode to pull my data off the phone. I can only get into ADB sideload and ADB fastboot which of course don't allow me to push/pull. I did sideload the newest version of tainmen to no avail.
My thought was to see if it was possible to remove the 64GB UFS memory chip which is soldered on the logic board and to solder it to an identical logic board I will purchase which already has the bootloader unlocked, then with the phone back together I can use ADB recovery mode to pull my data off the phone.
I have a local mobile repair tech who does micro soldering but I'm not sure this is even feasible, I have 2 major worries:
A: The bootloader is stored in the memory chip and not the RAM hence will just transplant my problem from one logic board to another
and
B: Does the memory chip have anything that ties it specifically to my logic board
I know I'm grasping at straws but I appreciate any info or help that I can get. Thank you if you made it this far reading! Stay safe everyone!
infinitedrive06 said:
Hello, I have a somewhat odd issue, so please bear with me and I apologize in advance for the long post.
I have a Google Pixel 2XL that began flashing at the lock screen. After about 30 flashes it restarts and says it can not load the android system. Here is a youtube video with the exact problem I'm having I can't post an outside link but if you search "NLrI6bIsTNM" on youtube it will come up.
I'm honestly not worried about the phone itself, but am looking for a way to save my photos and other possible data before wiping and/or sending in for replacement. My father recently passed away and my last pictures of us are on there as well as pictures from my engagement overseas etc. Pictures NOT backed up on google photos.
Though I do have USB debugging turned on, the bootloader is locked on this phone, so I can not get into ADB recovery mode to pull my data off the phone. I can only get into ADB sideload and ADB fastboot which of course don't allow me to push/pull. I did sideload the newest version of tainmen to no avail.
My thought was to see if it was possible to remove the 64GB UFS memory chip which is soldered on the logic board and to solder it to an identical logic board I will purchase which already has the bootloader unlocked, then with the phone back together I can use ADB recovery mode to pull my data off the phone.
I have a local mobile repair tech who does micro soldering but I'm not sure this is even feasible, I have 2 major worries:
A: The bootloader is stored in the memory chip and not the RAM hence will just transplant my problem from one logic board to another
and
B: Does the memory chip have anything that ties it specifically to my logic board
I know I'm grasping at straws but I appreciate any info or help that I can get. Thank you if you made it this far reading! Stay safe everyone!
Click to expand...
Click to collapse
I'm not 100% sure but there should be a way to re-flash the firmware without losing any data. I think that would be your best bet at the moment.
Have you tried booting the other slot? You can set the active slot through fastboot.
Coming back to bump. Still have this issue, using a crappy Blu phone temporarily. I will pay if someone can solve this issue for me.
EDIT: ISSUE SOLVED
Apparently, Google finally addressed the situation and in their August OTA they fixed the issue. What's funny is I sideloaded each months OTA in hopes of it working and I stopped at August for no good reason. I just loaded it after hours of trying other things and it worked like normal. Almost teared up lol. Thank God I didn't wipe my data. This originally happened in April and I have been holding off in hopes of a fix. Thank you all!
Good to hear this