Related
I heard this was possible, could someone elaborate on how this is done? Thank you
Do *not* attempt to flash ROMs across devices. Each ROM contains a customized set of drivers and configuration settings specific to your phone. Even if what you suggest is possible (it shouldn't be, but sometimes the safeguards aren't as strict as they should be) and you'll wind up with a phone where the hardware buttons don't work, or the touchscreen is off, or the battery doesn't charge correctly, or... yeah, just don't. Unless the hardware really is the next best thing to identical (and I mean the actual, internal chips and such, not the look of the device's chassis) it is pretty much guaranteed to cause more problems than it will solve.
i hope no one minds a question about a netbook here. i tried to upgrade the RAM in it, Toshiba sent me what is supposed to be a compatible upgrade module, but it doesn't work. the upgrade not working actually seems to possibly be a known issue, so Toshiba is processing a refund.. no problem.
the problem is that now the netbook won't even boot up at all with the original RAM module. i had even swapped back and forth twice, and each time the original module would work fine. i got curious after doing some more reading and tried the new one a third time, to no avail, and NOW the netbook is not booting up at all with the original module. the symptoms are now the same with both modules: some LED lights come on, the fan comes on, but the screen remains completely black.
i don't think i damaged anything, but i guess it's possible. i was careful each time installing the modules. Toshiba might send me a replacement of the original RAM chip that came with the Netbook, so i am hoping that will work. the machine is a Toshiba NB305 N440BL, by the way. just posting here basically in desperation, in case anyone has experience or advice. thanks
yogi2010 said:
i hope no one minds a question about a netbook here. i tried to upgrade the RAM in it, Toshiba sent me what is supposed to be a compatible upgrade module, but it doesn't work. the upgrade not working actually seems to possibly be a known issue, so Toshiba is processing a refund.. no problem.
the problem is that now the netbook won't even boot up at all with the original RAM module. i had even swapped back and forth twice, and each time the original module would work fine. i got curious after doing some more reading and tried the new one a third time, to no avail, and NOW the netbook is not booting up at all with the original module. the symptoms are now the same with both modules: some LED lights come on, the fan comes on, but the screen remains completely black.
i don't think i damaged anything, but i guess it's possible. i was careful each time installing the modules. Toshiba might send me a replacement of the original RAM chip that came with the Netbook, so i am hoping that will work. the machine is a Toshiba NB305 N440BL, by the way. just posting here basically in desperation, in case anyone has experience or advice. thanks
Click to expand...
Click to collapse
The symptoms that you mention here indeed relates to a RAM failure. Did you disconnect the power adapter before swapping the memory module? Since otherwise would result in a short circuit that will damage both the ram and even the motherboard.
Also did you completely insert the ram module into the ram slot, until it locks into place and you here a click sound?
But since you have mentioned about the LED lights coming on, Fan coming on and the screen remaining completely black it is obvious that your motherboard is fine.
Also when handling ram modules or any other sensitive electronic parts such as motherboard or graphics card, you should ensure that you have discharged yourself by standing on the ground with bare foots or using anti static wrist band. This is why they come in special anti static protective covers. ESD (Electro Static Discharge) from your body can damage these ESD sensitive devices.
Moreover, the more you swap the ram modules, the more they are to prone to get damaged.
There is a great chance that the original ram module is damaged. Better not try to make it work. Its much better to wait till you get the original replacement from Toshiba.
Thank you very much for the response, i really appreciate it i am also happy to hear that my motherboard is probably fine.
I disconnected the power source each time i replaced the module, and even the battery as well. And the modules are sitting in the holder as well as they can, and have snapped into place, so to speak. However, i was not too aware of the potential for damage due to my body's own charge. And yeah, i did swap and handle the modules quite a few times!
I feel fairly hopeful now that the original RAM chip simply went bad. I am about to call and make sure that a replacement is being sent asap. Will report back when it arrives and i, carefully, install it. Cheers
Thank you very much for the response, i really appreciate it
Click to expand...
Click to collapse
You are welcome...
I have an idea that there are certain criteria to a Rom working on any device in that :
Hardware speed - eg, maybe a 4.3 Rom cannot function smoothly on a 600mhz single core with 256MB of ram
Hardware existence - eg, maybe no gyroscope means no tilt/rotate function
Device type - Phones V Tablets V "Phablets"
It is somewhat fair to say if you have as much computer knowledge as me that any Rom will work on any device as far as booting up and getting to 'desktop' is concerned but regardless of performance and hardware ability, is this true ?
Does it make a difference if you have a phone or a tablet or the terrible yet funky termed 'phablet' ?
Granted, this really isn't about apps as am I right in thinking it is dependant on hardware and the Rom as to what apps can run. I am mindful of things like screen resolution and probably other relevant things that may dictate what can happen. Do any of these relevant hindsights mean there should be core features for resolution and other such issues ?
That's all I can think of for now as I have a bit of a headache. :good:
My pixel 7 pro freaked out on me the other day and went black on me when I played a game and didn't come back for over 15 minutes then finally was responding again. Any reason why this happened . Hopefully software and not hardware. Hasn't happened since but still concerning .
Anyone ?
Redbeardkevv said:
Anyone ?
Click to expand...
Click to collapse
Flaky game? I never play games on any tool, which a smartphone is. I wish the OEM's would stop trying to make it even possible. Buy a "gaming" phone which is designed specifically for that purpose. In fact, some of the best phones available today (spec wise) are gaming phones! If it only happened while playing the game then that is where I would look.
jaseman said:
Flaky game? I never play games on any tool, which a smartphone is. I wish the OEM's would stop trying to make it even possible. Buy a "gaming" phone which is designed specifically for that purpose. In fact, some of the best phones available today (spec wise) are gaming phones! If it only happened while playing the game then that is where I would look.
Click to expand...
Click to collapse
This is one of the most ridiculous responses I have ever seen. There is nothing that makes a "gaming phone" special. They're using the same hardware and software as any other phone with gaming-specific gimmicks. The phone has a throttle mechanism to prevent any kind of damage.
EtherealRemnant said:
This is one of the most ridiculous responses I have ever seen. There is nothing that makes a "gaming phone" special. They're using the same hardware and software as any other phone with gaming-specific gimmicks. The phone has a throttle mechanism to prevent any kind of damage.
Click to expand...
Click to collapse
Ridiculous...maybe...but the fact remains that you experienced this WHILE playing a game! So I wonder what the problem may be?
Hmmm
jaseman said:
Ridiculous...maybe...but the fact remains that you experienced this WHILE playing a game! So I wonder what the problem may be?
Click to expand...
Click to collapse
That's called a hardware defect if the hardware can't cope. Going blank for 15 minutes is not normal.
Hardware hmm and not software?
Redbeardkevv said:
Hardware hmm and not software?
Click to expand...
Click to collapse
What were you playing? If it was a graphically intensive game, I would definitely lean more towards blaming the hardware. It's very rare that a game can actually make a phone that unstable. In fact I can't remember the last time I've had a game make my phone unresponsive.
Roblox with my nephew
Redbeardkevv said:
Roblox with my nephew
Click to expand...
Click to collapse
I've never played that game but their site seems to suggest some rather low requirements so I would be shocked if an ARMv8 processor like Tensor 2 is going to struggle with it.
Android warning screens
Due to the very large number of Android devices in existence, we cannot be certain that all devices will run optimally even if they are running the correct version of the operating system and do not have a Tegra 2 chipset.
We have 2 levels of unsupported Android devices - skippable and unskippable:
Skippable Devices: These types of devices will get a warning telling you that your device may not be powerful enough to play experiences smoothly. This is just a warning to let you know that while your device isn't specifically supported, experiences might still run though they will likely lag a little (or a lot). Tapping outside the warning box will make it go away and the experience should keep loading.
Unskippable Devices: will get a message that informs you that your device doesn't meet the minimum system requirements. This means the device is not able to play experiences on Roblox. This message usually shows up on devices that use the Tegra 2 graphics chipset or a processor older than ARMv7. These kinds of tablets/phones do not support features that the Roblox needs to be able to function. However, users with these unskippable messages will still be able to access all other parts of the app outside of experiences.
Click to expand...
Click to collapse
https://en.help.roblox.com/hc/en-us/articles/203625474-ROBLOX-Mobile-System-Requirements
Yea I was thinking it had low requirements. Maybe bad coding ??? But then again no other app or game has caused that to happen. Sooo. Yea
I don't think it's software. I already had one screen die. Went black and never came back on. I had it fixed under warranty at a local UbreakIFix (Asurion - Google's warranty partner). Techs were aware of a similar problem with the 5a and replaced my screen same day.
I've had a few wonky screen issues that hard locked my phone. Had one go black, but fortunately came back after holding power down. It once went all yellow with weird shapes/sections. And then just had some freezes with artifacts on the screen.
I'm going away for the holidays so I'll send it back when I get home if I'm still having issues. If you're going away, I'd suggest taking a backup phone just in case. Had mine die the first time when I was visiting my folks out of state. It sucked with no backup.
One thing I noticed is the screen does a fuzzy flash whenever I plug in a USB charger. It's only a split second but it is noticeable. Has anyone else experienced that?
Superguy said:
I don't think it's software. I already had one screen die. Went black and never came back on. I had it fixed under warranty at a local UbreakIFix (Asurion - Google's warranty partner). Techs were aware of a similar problem with the 5a and replaced my screen same day.
Click to expand...
Click to collapse
Most of these failures have been a combination of both hardware and software - nothing is actually wrong with the screen. I'm not sure exactly how it happens, but it seems that this usually involves a OS crash (phone freezing up) followed by an attempt to reboot, but for some reason the bootloader has become corrupted and the device won't start. Fixing it generally involves replacing the mainboard, because most repair centers don't have the QPST or the software needed to perform low level reflash. This is a known issue over several generations of Pixels; the cause is unknown.
V0latyle said:
Most of these failures have been a combination of both hardware and software - nothing is actually wrong with the screen. I'm not sure exactly how it happens, but it seems that this usually involves a OS crash (phone freezing up) followed by an attempt to reboot, but for some reason the bootloader has become corrupted and the device won't start. Fixing it generally involves replacing the mainboard, because most repair centers don't have the QPST or the software needed to perform low level reflash. This is a known issue over several generations of Pixels; the cause is unknown.
Click to expand...
Click to collapse
What was weird is when mine went black, the phone would still boot and in theory was still usable. Pushing the buttons gave haptic feedback like they were bringing up the power menu or adjusting the volume. I just couldn't see what was going on or use touch to give input.
They told me they just replaced the screen. Didn't touch the motherboard.
I was using one of the custom kernels so I ended up having to wipe it and went back to stock kernel with magisk and some modules. It hasn't acted up as much as it did with the custom kernel, but there are still issues. I suppose it could be something that's messed up in the stock kernel, and perhaps tweaks a dev made in theirs may have exasperated it some.
If I end ups ending it back, I'll try a custom kernel again, but for now, I'm just sticking with stock.
*no disrespect intended or implied to any dev
Superguy said:
What was weird is when mine went black, the phone would still boot and in theory was still usable. Pushing the buttons gave haptic feedback like they were bringing up the power menu or adjusting the volume. I just couldn't see what was going on or use touch to give input.
Click to expand...
Click to collapse
Yeah, that's definitely a display issue. I'm talking about when the device doesn't work or respond at all, maybe vibrates on power up but doesn't respond to anything, and usually will come up as "Qualcomm Bulk USB" or something when connected to PC
Superguy said:
They told me they just replaced the screen. Didn't touch the motherboard.
I was using one of the custom kernels so I ended up having to wipe it and went back to stock kernel with magisk and some modules. It hasn't acted up as much as it did with the custom kernel, but there are still issues. I suppose it could be something that's messed up in the stock kernel, and perhaps tweaks a dev made in theirs may have exasperated it some.
If I end ups ending it back, I'll try a custom kernel again, but for now, I'm just sticking with stock.
*no disrespect intended or implied to any dev
Click to expand...
Click to collapse
For sure, active development may or may not have stability issues, it's all a learning process!
I have a Pixel XL that's hardbricked. Took it to a GSM shop they said the charging port works but something something CPU fried. No gsm shop in our city can fix this apparently but he heard that some folks could do it in New York City.
I don't want to recover the phone, just the data on it. Do you guys know shops that can do this ?
gtech99 said:
I have a Pixel XL that's hardbricked. Took it to a GSM shop they said the charging port works but something something CPU fried. No gsm shop in our city can fix this apparently but he heard that some folks could do it in New York City.
I don't want to recover the phone, just the data on it. Do you guys know shops that can do this ?
Click to expand...
Click to collapse
Not at any reasonable price point. What happened to the phone? Recovering the data from the flash devices would involve prohibitively expensive forensic data recovery, to the point of removing the flash devices from the board and interfacing with them using special tools. The people who have the means and the knowledge to do this are few and far between. Assuming there's no physical damage, someone with the Qualcomm Product Support Tool software and the appropriate binaries could potentially perform a low level reflash so the phone will boot...but again, the people who are actually able to do this are few and far between, assuming they even have the necessary files (which are not publicly available). The average repair shop will just replace the board, which means all the data is never recovered.
gtech99 said:
I have a Pixel XL that's hardbricked. Took it to a GSM shop they said the charging port works but something something CPU fried.
Click to expand...
Click to collapse
Speaking of a fried CPU, it means due to overheating CPU’s electrical components like transistors, diodes or capacitors are burned up. You will find overheating happened with some CPUs which didn’t have any fail-safe features or were overclocked by pushing high voltage. Sometimes using a faulty motherboard and faulty PSU can do this type of damage.becauseSo, you if you really ended up with a fried CPU, what is quite rare these days because, as said, modern CPUs have advanced thermal protection ( CPU will shut down automatically if it reaches a high temperature. If CPU temperature rises high due to high clock speed then it reduces the clock speed to a lower level ), you will have the worst luck to recover data from phone.
Note: it’s not possible to fix a fried CPU. Try to replace it with a new one.
V0latyle said:
Not at any reasonable price point. What happened to the phone? Recovering the data from the flash devices would involve prohibitively expensive forensic data recovery, to the point of removing the flash devices from the board and interfacing with them using special tools. The people who have the means and the knowledge to do this are few and far between. Assuming there's no physical damage, someone with the Qualcomm Product Support Tool software and the appropriate binaries could potentially perform a low level reflash so the phone will boot...but again, the people who are actually able to do this are few and far between, assuming they even have the necessary files (which are not publicly available). The average repair shop will just replace the board, which means all the data is never recovered.
Click to expand...
Click to collapse
I haven't done anything special with this phone. Never rooted it or installed other bootloaders, etc. It was a generic bland Pixel XL. It might have overheated a few times in the summer when I was using it in my car for Waze but otherwise nothing.
Before it shutdown for good it had some strange reboots and I think I recall there was some Pixel bug that was causing that. After doing that for a few weeks it stopped turning on completely.
Isn't a procedure like this available for the Pixel ?
https://flashfixers.com/recover-data-dead-phone-chip-off-data-recovery/
gtech99 said:
I haven't done anything special with this phone. Never rooted it or installed other bootloaders, etc. It was a generic bland Pixel XL. It might have overheated a few times in the summer when I was using it in my car for Waze but otherwise nothing.
Before it shutdown for good it had some strange reboots and I think I recall there was some Pixel bug that was causing that. After doing that for a few weeks it stopped turning on completely.
Isn't a procedure like this available for the Pixel ?
https://flashfixers.com/recover-data-dead-phone-chip-off-data-recovery/
Click to expand...
Click to collapse
That's what I was referring to by removing the flash device from the PCB. You would need fairly specialized tools, incluing a reader that's able to interface with the chip, and you'd have to have significant knowledge of how to interpret the raw data as the actual file structure. If you can find someone who thinks they can do this, good luck...but if it were me, I'd be charging about $150 an hour to do it.
And, this is all assuming that the data isn't encrypted. If it is (which Android does by default) then you're SOL.
V0latyle said:
That's what I was referring to by removing the flash device from the PCB. You would need fairly specialized tools, incluing a reader that's able to interface with the chip, and you'd have to have significant knowledge of how to interpret the raw data as the actual file structure. If you can find someone who thinks they can do this, good luck...but if it were me, I'd be charging about $150 an hour to do it.
And, this is all assuming that the data isn't encrypted. If it is (which Android does by default) then you're SOL.
Click to expand...
Click to collapse
Ah, ok. I'd pay 300$ to have this recovered is that reasonable ? Or it might be way more than that ? Guess I need to find a shop that does this sort of thing
gtech99 said:
Ah, ok. I'd pay 300$ to have this recovered is that reasonable ? Or it might be way more than that ? Guess I need to find a shop that does this sort of thing
Click to expand...
Click to collapse
Best of luck to you, honestly I think the money would be better spent elsewhere.