My brother was using his Moto G just regularly, (after I enabled the swap partition for better RAM management, it had some out of memory issues before that and that fixed it), when the screen went black. I looked at the panel and it appeared to be still on but showing black. We weren't at home by the time it happened, so I couldn't check via ADB if it was still online. The panel went off after a while and now I can't even boot it up to the bootloader. I plugged it in to charge it for quite a while, it still doesn't boot into the bootloader. I can't do anything now. I hope though that Roehsoft Swap (the App I am using) didn't wipe accidentally a vital partition (but I doubt that the bootloader can be corrupted from withing the OS). I tried everything to make it boot at least into the recovery or the bootloader, without any success. The device has an unlocked bootloader, TWRP MultiROM recovery, The Green Machine Kernel and PA5Alpha1. Is the nand storage faulty or any component (mainboard, CPU, etc)?
I dont understand why did you enable SWAP partition in the 1st place. 1GB is more than enough also Android's Built-In RAM management is totally optimized to take care of the memory and the running apps.
SWAP comes into play when your RAM is completely used and the system swaps the last unused memory blocks into the swap partition to free up the RAM. I hope the swap hasnt affected the memory nand chip.
Charge the phone till 100%, unplug the charger wait for some time and then try to boot into "Bootloader".
If you are able to boot in to "bootloader" flash factory firmware to restore your all partitions to stock.
If all else fails, that means your phone has "HARD BRICKED", you will have to go to the Service Center to get the motherboard replaced.
Related
As of today my Diamond won't boot properly. The phone is completely retail, no custom roms. When I turn it on it will display the T-Mobile image and then just hangs. I did a couple of hard resets, but didn't format the internal memory.
I can get into the tri-color screen and make an USB connection. Since the phone is still under warranty I made some arrangements to get it repaired. However, I recently made a backup using PIM and that file is stored on the internal memory.
My question is: can I access the internal memory and get my backup file? Otherwise I think I'll be loosing all my phone numbers when the phone is back from repairs.
Denthaman said:
As of today my Diamond won't boot properly. The phone is completely retail, no custom roms. When I turn it on it will display the T-Mobile image and then just hangs. I did a couple of hard resets, but didn't format the internal memory.
I can get into the tri-color screen and make an USB connection. Since the phone is still under warranty I made some arrangements to get it repaired. However, I recently made a backup using PIM and that file is stored on the internal memory.
My question is: can I access the internal memory and get my backup file? Otherwise I think I'll be loosing all my phone numbers when the phone is back from repairs.
Click to expand...
Click to collapse
Did you try to take the battery out, wait a few minutes and put it back again?
I don't believe that there is a way to access the internal memory without booting the device.
I don't want to be a know-it-all, but a backup makes always sense ... sorry ...
Yeah, I also tried a hard-reset.
I managed to flash an original rom and finally booted again into windows. It left the internal memory intact so I managed to make a backup to a pc. The device seems to be in working order again.
Still clueless about what has happened.
Absolute NooB to the NC here, so please be gentle!
I've got four issues that should be no-brainers but they are beating me up. I've split them into four separate posts to keep things clean.
2. Restore stock image
I've burned the stock B&N image to a 2GB SDcard, so I'm good on rolling back if I have to. (And it is sooooo nice to have another device like my original Droid... essentially unbrickable)
But I've read that there is actually a recovery partition on the eMMC which can be accessed by interrupting the power-on sequence eight times in a row.
Sounds really simple. But I can't make it work.
Whenever I try, the second time I interrupt the power-on, it doesn't actually power down. It looks like it is but then it continues the boot.
So, does this recovery partition really exist? And, if so, how do you activate it?
I read someplace that there is a stock firmware image tucked away internally on the NC, and the system will automatically try to restore if on x number of consecutive boot failures.
You would have to wipe /data and /system and then powercycle the device without your CWM boot SD. I think this would engage the "fail loop" that triggers the internal recovery process.
scriptx said:
I read someplace that there is a stock firmware image tucked away internally on the NC, and the system will automatically try to restore if on x number of consecutive boot failures.
You would have to wipe /data and /system and then powercycle the device without your CWM boot SD. I think this would engage the "fail loop" that triggers the internal recovery process.
Click to expand...
Click to collapse
That worked.
Not that I really need to use it, just interested in learning all the moving pieces on this hardware.
Hello all.
I got my hands on very interesting phone, if I flash any GB ROM including stock, phone may or may not start boot looping (can't get past first screen). Now the interesting thing is that after 3-20 attempts it boots and then works perfectly (app install, taking pictures etc.) until it again gets rebooted or turned off.
If I install ICS ROM's on start-up I get Encryption unsuccessful screen and then again it takes 3-20 reboots to get the phone working. No need to do factory resets etc. Now I am no guru on Samsung HW and Android but my guess is that on boot android fails to mount /data and /emmc partition. Now I understand that this can be caused by either Corrupted partition or hardware failure. The interesting thing is that I cannot call my partitions corrupt - as I don't loose any data and I cannot call it a hardware failure - as after phone boots I can access all storage space. Tired repartitioning using Odin/Heimdall and only trick that seems to work is using External SD card as "internal".
Any ideas what this wonder is?
just search encryption unsuccessful bug on vibrant....and you will find TONS of information about it.....take your time and read it.....and btw you will be unable to access your internal sd( 16gb mem) anymore...
Up until a few weeks ago, my N1 worked fine. Rooted, CM7.
Then I got lots of FCs and decided to re-flash CM7.
It worked fine for a week or so until last night. It was fine before I fell asleep but dead next morning.
I can VOL.DN + POWER on and switch between FASTBOOT and BOOTLOADER/HBOOT
I can boot into ClockworkMod recovery.
Booting CM7 presents coloured X; then a blank screen (it may be off) and sometimes I get softkeys lit or flash once. Usually N1 vibrates slightly every 5 seconds or so. Only way out of this is to remove battery.
I have a very recent backup. but it or any of it's img files have MD5 errors.
So, either this image is bad, or perhaps I have a RAM error that also prevents phone booting?
Is there a log file I could look at (I can connect using adb)?
Is there a way to test RAM? Is there a PASSDIAG.ZIP or PASSDIAG.NBH image I could try?
I also tried re-flashing CM7 - no change.
Any other ideas?
Did you try to use another SD card to use in your device? It could be a SD card failure and is easier to fix than a RAM failure. I also remember reading in other threads that a SIM failure could make reboots and freezes in these devices
I had a similar problem in my Nexus One with the original ROM, but in my case I think that the failure was in some corrupted file in the system partition.
Doubt SD card nor SIM is issue
Same defect when SD card and/or SIM removed (except I can not attempt a restore with SD card removed).
So I don't think either is at fault.
SD card mounts fine when USB connected to a linux laptop under FASTBOOT (I think I did this) or RECOVERY.
Mine have a like problem, i only do a full wipe and start without SD and it worked
Alright, so I noticed that my Xperia V wasn't utilizing the SD Card fully so I tried partitioning some of the unused memory with TWRP.
I selected 1024 mb, 0 mb swap size, and ext4 and then swiped.
After this my phone just went black and I get "qhsusb_dload" everytime I connect it to my PC.
Worth noting is that before this I made a backup with TWRP, if it's possible in anyway to force this on my phone.
I read around about qhsusb_dload and it seems to correlate to the phone being bricked. So is my phone doomed or did I just mess up my SD Card so it can't boot?
Is there anything I can do about this? As said, I've got a full backup of my Boot, System and Data on my PC.
Edit:
I've tried doing the 24 hour charge thing. Got 5 more hours to go and both the charger and phone don't seem to be doing anything. They're both cold, and not warm like when they're charging.
I've also tried using flashtool but it can't detect my phone because of the qhsusb_dload drivers "missing".
I downloaded Xperia/PC Companion and it can't detect or repair my phone either.
Am I screwed?
Did u fixed ur phone?
Do you have any idea, how to resolve it?
My phone Xperia T LT30p
I set interrnal sdcard so lower amount 10GB to 6GB and after reboot phone is in mode qhsusb_dload.