I know there probably aren't many people concerned with these old phones anymore. I don't care about the phone at all, its extremely old, but I think it might have some data on it that I want to recover. It has been stuck in bootloop for years and I abandoned it until recently. I messed around with a blow dryer, then a heat gun to no avail. I was trying to take it apart a couple months ago and destroyed the screen, so I replaced the screen and battery. It is now re-assembled and back to its bootlooping ways.
The bootloader is locked, I can get to the recovery screen sometimes. I downloaded some stuff that I'm very unfamiliar with, like Minimal ADB and Fastboot. If I connect the phone to my computer and enter "adb devices", it doesn't show up. If I enter "fastboot devices" it will show up.
The bootloader shows up in my device manager. I used some guide and downloaded some google USB driver and installed it to the bootloader device, but it didn't do anything.
I'm so far out of my element messing with this thing, I'm paranoid I'm just going to brick it or accidentally wipe the data by messing around, if I haven't already.
If anyone out there could help me out, or point me in the right direction, I'd be so grateful. Not sure if this stuff matters, but I ran "fastboot getvar all" and here's what I got.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
Today I was reading about people having problems with the Market and JF 1.5. I went into the market to see if I was having the same problems. I was distracted by something on the tv, and when I cam back, the phone was frozen.
To unfreeze the phone I had to remove the battery. After removing the battery,the phone would not boot.
I have since been able to reflash the bootloader, rom, and recovery files.
At this point in time I can access the bootloader. Anything else brings up the T-Mobile G1 screen and then it shuts down or restarts.
Anyone have any ideas?
Thanks.
If this is in the wrong section, please move
Edit: It appears that removing the MicroSD card has helped get the phone back on. Could the SD card have been the issue, and if it is, will a format help fix this?
Edit 2: The phone has just restarted on me multiple times. I will look at the restarting threads to find a possible solution.
Edit 3: I managed to get the phone back to the stock rc29, bootloader, and recovery mode. Unfortunately the problem is still occuring, which leads me to believe this is a hardware issue.
On the times when I can actually get the phone booted, If I slide open the keyboard, it causes the phone to freeze. If I start with the keyboard open and press a button once the phone is on, the phone restarts. Does anyone have any ideas?
Just attempted to turn the phone on and this is what I got....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I got an email from my aunt today and both my niece and nephew's Nexus 7 tablets wont boot up anymore. I think they took an update that bricked them both. They are codenamed grouper which I think is this 2012 version right? Anyway, Ill attach a picture of what they look like and maybe it is a common enough issue that the people here on this subforum can help me out on what to do I have used a Nexus before so I know how to do fastboot commands and ADB stuff and can push a ROM and kernel that way, but my aunt tells me that neither device will come up on the PC when plugged in even after downloading the newest drivers. Ill see for myself tomorrow, because I doubt she downloaded fastboot and ADB drivers to try. But figured I would post here about it and hope I can get some answers to start me off on what to do when I pick up the tablets. Both tablets are fully stock so no unlocking or rotting done to them, they were purchased last year.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I got them working. It had some issues because it kept saying invalid argument when I tried to flash stuff, but I eventually got it and now they are working again and both running unlocked with CM11 M9
EDIT: never mind, it doesn't actually do anything, fastboot commands like "boot" still don't work
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I booted into fastboot (using a regular cable) and then used a Kindle Fire fastboot cable to enter "fastboot oem unlock"
This happened. Not sure if it actually allows me to flash/boot unsigned images though, I don't really want a brick at the moment
well
JordanRulz said:
So I booted into fastboot (using a regular cable) and then used a Kindle Fire fastboot cable to enter "fastboot oem unlock"
This happened. Not sure if it actually allows me to flash/boot unsigned images though, I don't really want a brick at the moment
Click to expand...
Click to collapse
I can't remember exactly where I read it may be in development or original development here it's been fairly recently I believe it is awaiting some hex key codes or some type of ID numbers I'm not sure which but I do not believe that you are unlocked..I do know it is in some of the very recent development stuffthat some of our higher end developers were discussing this.
It doesn't do anything.
I was trying to root and mod my spare Galaxy S8 and during the process the battery died... now it is stuck on the boot screen. When it turns on it opens to the custom Samsung boot screen and does not change or boot any further. When I reboot it with the button combination it boots into upload mode. From there I must reboot again. I can still get into download mode and into android recovery mode, but have been unsuccessful at and attempts of flashing with Odin, ADB, or from the SD card. I am completely confused. Any advice will help and be greatly appreciated!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Use modded Odin with the latest firmware which is QL1.
Stop trying to root
I having a similar problem, just that it DID finished updating. Now it's stuck at boot screen even after updating it to the last version available (AQL1). I don't know what else to do....
well I gave up and finally went to Best Buy and spoke with a samsung employee.
I was able to get my phone back in 100% working order! He just used his special scan tool and flashed it the very first time. For FREE!!!!!
Hi all
I had a LG G2 ( d802 ) which was broken and I tried to meddle with it a bit. It isn't booting up and when it booted, either it stucks at bootlogo or boots up to PIN screen, locks itself up and reboots.
So after couple of failings I finally booted it up in download mode and tried to flash stock rom (kdz file) from there. It succesfully flashed, booted up and stuck at welcome screen again and shut itself down. When I tried to open it, the phone still stucks at bootlogo. However when I connect it in download mode to my computer and look to the Windows Disk Management, device storage is fragmented into a lot of pieces. Is there a fix for this ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
All of this pieces belongs to the phone ( all of disk 2 ) and there is more, I couldnt fit all of them into a single image.
Yeah this is exactly what happened to me the past few days. Whatever you do, don't delete those random partitions. They will render your phone completely inoperable.
I tried this https://www.youtube.com/watch?v=ERZvlJIC9dE without much luck. Still lots of fragmentation and could not enter download mode for more than a couple of seconds or recovery either.