I have an unrooted and locked Galaxy Nexus which seems to have got stuck in a bootloop and won't start. I had some important data on the sdcard which I want to recover. Any suggestions on how I can do so? Here are more details about the problem -
I tried to upgrade it Jelly Bean a few days back and it didn't happen successfully. However after that the phone was still working properly and one day when I switched on my Bluetooth, the device restarted suddenly and it got stuck at the initial animation after showing the Google logo. So effectively the device doesn't boot and I am assuming the boot partition either got erased or corrupted.
I also tried connecting the device to my computer but it doesn't recognize the device. I tried it in Windows, it didn't work and I assumed it to be a driver problem. So I also tried it in Ubuntu but still no luck. However the phone does get recognized in fastboot mode using "fastboot devices" but I cannot get the device to mount nor get "adb devices" to work.
I bought the device into fastboot and tried to start the recovery mode but even that doesn't start and gets stuck at the Google logo. This was strange since I haven't touched the recovery partition at all and in fact the device hasn't even been unlocked.
hi guys,
tragedy started like that: today i decided to give miui another shot. downloaded latest miui developer rom to sd card of my galaxy nexus, rebooted into recovery and flashed miui zip and tiny kernel afterwards. stupid me i forgot to wipe cache before installing the new rom. hit reboot in cwm, which kindly told me that the new rom could make recovery unusable. here i accidentally selected the obvious wrong choice, which said "dont fix problem" or sth like that. dont know if recovery is gone now... after reboot miui was trying to boot without success (mi logo shown until you turn the phone off). so i went to fastboot by pressing volume down (my volume up is broken!). fastboot acts pretty dead: cant scroll through options by pressing volume down, cant do "normal" start by pressing power, absolute no reaction of the phone. also the phone is not recognized when connecting to pc via usb (tried the samsung original driver). phone is recognized when miui is trying to boot, but i cant send any commands via fastboot.
im thankful for any advice that lets me install a new recovery/boot into recovery/make it boot again!
fastboot mode details:
product name - tuna
variant - maguro 16gb
bootloader version - primemd04
baseband version - i9250xxlj1
carrier info - none
serial number - irrelevant
signing - production
lock state - unlocked
anyone?
Hi everybody,
ok I will try to make this short
I have an experienced user level ROM, recovery, boot, ..
My phone is BRICKED! Is it?
AT THE MOMENT:
- I get into fastboot mode
- I get into odin downloading mode
- I can't start in recovery mode
- I can't start bootloader mode
- I have a connection with a laptop (win XP, as win8.1 didnt work for me)
- The computer can communicate with the phone in fastboot mode
- The computer cant communicate with the phone in Odin mode (at the moment Odin PC SoftWare doesn't recognize the phone)
- I am sure the drivers are installed correctly now. Thanks to the guide with fully stripped drivers.
- Using different, multiple different, no thousand different methods I tried flashing the stock OS (Yakju 4.3)
- I like SkipSoft Android ToolKit (Although I used fastboot and adb commands, I find the toolkit to do the same thing..)
- I always get an Error, when the process of flashing starts.
> PC says : Error
> Phone (in fastboot mode) says: FAILWrite Fail
INTERESTING:
- While I still was able to get into Recovery, the phone couldnt mount the sdcard (=> the internal drive)
- Some of the methods I use make the phone CRASH
> means the screen stops at its position and slowly turns completely purple
- The phone power button doesnt start the phone, to get the phone doing something at all I have to trick it:
..> I plug it into the wall charger
..> I take the battery out
..> I put the battery back in
..> I wait
..> I can get into 3 routines:
^Normal starting routine (of course stuck at google start up, since no Rom is installed)
^fastboot mode (VOL + & - & Power)
^odin mode (VOL - & Power)
..> Then I can just plug the USB cable into the PC
- 2 days ago I had (every single version) of Odin PC Software recognizing the phone (phone was in Odin mode), but it also failed after trying the recommended and unrecommended settings. Ended with an error message.
HOW:
I left my phone overnight in the car (Temp: -2 deg C), while Im sure spotify and maybe other consuming apps were playing.
Next day, my phone battery was empty and I couldnt start my normal ROM. (I had Slim Rom installed)
It was stuck at the "Google" start up display.
First intentions showed that it might be more than just the Software :/
Many days and so many hours of work, research and reading in forums, I decided to take a shot and ask here.
I appreciate everything xda-members have done for me already. Though I never needed to register for my earlier questions.
Phone data:
Product Name - tuna
Variant - maguro 16gb
HW version - 9
Bootloader Version - primemd04
baseband version -
carrier info - none
serial number - -a3c208 ***
signing - production
lock state- unlocked
BUMP!!! I have absolutely the same problem!! I can access everything, i enter the recovery trying to WIPE every single thing data,system,cache,storage etc.. but it seems it doesnt work. The information stays. I tried to "softbrick unroot & stock" with a nexus kit, everything seems ok, but after it finishes installing, it boots up on GOOGLE and after 10-15 min it starts to BOOT MY OLD CUSTOM ROM THAT I HAD BEFORE, after another 15-20 min it finally boots up and the system is EXTREMELY choppy and unresponsive and after a few minutes it restarts itself. I tried ODIN and I faced the same problem, it goes well to ~45% and then it freezes, and after a short delay odin gives FAILED. I tried several more things that i found on the internet and xda but nothing helps. Probably a corrupted partition or something. THE DAMN STORAGE DOESNT WANT TO DELETE ITSELF FFS!! PLEASE IF YOU KNOW ANY FIX/ALREADY FIXED YOURS PLEASE HELP!!! I need my phone!
can you give us more information about the error message?
valkata1212 said:
Click to expand...
Click to collapse
your issue sounds like this one, can you confirm?
Soulaysahmi said:
can you give us more information about the error message?
your issue sounds like this one, can you confirm?
Click to expand...
Click to collapse
Similar, only difference is with fastboot i can successfully flash system.img but nothing happens. With odin it fails at around 45% and then freezes. Only difference is that i cannot boot to old stock and i dont have this pulpish problem. I simply reboot on my old custom ROM configuration with all my last known icons widgets.. but the phone is choppy and unresponsive as hell.
I only get an error without any further message after flashing any of the images...
Any idea anyone? Isn't it some hardware issue?
Noo man i dont think its hardware problem, for me it all happened when my phone suddenly restarted itself and after that it bootloops forever and i have those problems
Anyone?
does erase work?
yes
can you get into recovery?
oxxomexico said:
AT THE MOMENT:
- I get into fastboot mode
- I get into odin downloading mode
- I can't start in recovery mode
- I can't start bootloader mode
- I have a connection with a laptop (win XP, as win8.1 didnt work for me)
- The computer can communicate with the phone in fastboot mode
- The computer cant communicate with the phone in Odin mode (at the moment Odin PC SoftWare doesn't recognize the phone)
- I am sure the drivers are installed correctly now. Thanks to the guide with fully stripped drivers.
Click to expand...
Click to collapse
ka
how do you know that erase works, I mean that what you erased has really been erased?
One of the erase command in the toolkit was succesful, I guess. But I will recheck every error or successful message later tonight.
still NOT working
2 months have passed and I was too busy with other things.
now back to it. the problem hasnt changed.
i try fastboot flash command:
[fastboot flash bootloader x.img]
- in Computer Terminal: 'FAILED(remote:Write Fail) '
- on phone: ' FASTBOOT STATUS - FAILWriteFail '
any idea, please?
I had Pure Nexus running on my Flo with no issues and decided I wanted to flash another kernel (glitched kernel to be exact). I went through the update script and flashed the kernel and noticed that once I hit reboot my device just went black. No Google splash screen like when normally rebooting or anything. After letting it sit for a while I rebooted back into the bootloader and from there I went into TWRP which is now asking me for a password that I never set. Since I haven't set a password I am forced to hit cancel which from there will not let me mount any partition to recover my device. Now This would normally be no issue since I can always Fastboot erase and flash a new recovery or factory image. But I got the device already unlocked from my friend and never had the need to hook it up to my computer. Which means I can't get my Windows 10 computer to get any adb/fastboot connectivity. I downloaded the SDK and installed Google USB Drivers from there but that didn't help me gain adb/fastboot connectivity in the bootloader. When I go my device manager in Windows it just lists the device as "Android!". Does anybody know either a way to disable this password so I can mount my partitions or a way for me to somehow gain adb connectivity in the bootloader without being able to turn on my Nexus 7? Any help would be greatly appreciated. I have exhausted any ideas I can come up with myself.
If it makes a difference the version of TWRP is 2.6.2.0 and says I have no OS installed and when I try to reboot system It just gets hung on the Google splash screen.
EDIT 1 - I was able to gain adb/fastboot connectivity in the bootloader by manually updating drivers. But it seems as if I can't get any partitions to mount in the bootloader. Every partition says "FAILED remote: flash error" when I try to write to it, therefore I can't do anything in the bootloader. I also remembered I had a 4 digit PIN set for the passcode to unlock my device and that doesn't work to unlock recovery either. It does give a very brief output sometimes of failed to decrypt data. Also tried "default_password" and same results. I get failed to decrypt data maybe 1 out of 5 attempts just like my PIN. Any ideas anyone? This is driving me crazy lol.
I don't know what to do anymore. I've been trying for months to try to install TWRP recovery on to my OPPO.
(Backstory)
I wanted to unified the storage of my OPPO Find 7A. So I uninstalled Lineage using the TWRP and I thought I could just install Colour OS and see if that could unified it. However, the moment I got Colour OS it couldn't even open the wifi and the dates are always 1970 Jan 1 at 4 pm, even if you change the dates. As soon as it is turned off and back on it will be the same. So I thought I could just use TWRP to uninstall the Colour OS and install another Custom OS. However, when I press the power button and down volume. it just restarts (Showing the WO chinese logo, it doesn't show the OPPO logo anymore) and goes directly to Colour OS.
So I figured that maybe TWRP was deleted when I was wiping everything. So I tried to install it again with the latest TWRP and ADB in fastboot mode with "fastboot devices" to check if it is connected and "fastboot flash recovery twrp.img". This time it says it is locked and can not flash or erase.
So I tried "fastboot oem unlock" it says Okay and basically restarted itself and went directly to Colour OS. When I put it to fastboot again to check with "fastboot oem device-info" it says it was still locked.
So no matter what I did nothing seems to work.
So far I've tried using different programs like
WinDroid Toolkit v3.1
Oppo_find_7_Recovery_Installer_V1.5
flash_recovery.zip
And I even tried to change to program I'm working with, such as AndroidSDKSlim, ADB-Fastboot-And-Driver-v1.4.3 and changed different TWRP versions (2.8.4.0, 3.0.2-0, 3.2.1-0)
So, now I'm thinking I might have just softbricked it and I'm trying the solution from this post
https://forum.xda-developers.com/find-7/help/how-to-debrick-unbricka-oppo-7-7a-t3717802
So far it has been 45 mins and it does not seem the program is downloading/installing anything on my phone. It's just there doing nothing after I pressed "start".
I'll try leaving it overnight and see what happens but if someone can help please do. (UPDATE: Nothing changed)
PS. the current Colour OS that is running on the phone is version 1.2.0 (it cannot be updated, I've tried using an SD card with the newer version on it to run it with "system updates", it restarts and it goes back to 1.2.0 and nothing has been done.) It is running Android version 4.3 and I have activated developer options and USB debugging but there is no OEM Unlock option under "Developer options")