Galaxy Nexus Bricked - erase data/userdata wipe or write failed - Samsung Galaxy Nexus

sorry guys, I don't speak much English
I did a factory reset by menu Android. The GNEXUS has restarted and remained on "deletion".
I've tried Nexus toolkit with Rom stock, Odin with stock rom, from command in fastboot mode, but everytime the process stops.
ODIN fails during the "UserData" process. Even with the toolkit hangs around during the operation "erase userdata".
With ODIN I was able to flash a version 4.2.2 no wipe (no delete userdata) but once restarted remains on Google screen.
At this time I can go to fastboot mode or Download mode (No Recovery mode!!!)
I cannot enable the debug mode...
I must bring in assistance or I can try other methods to flash?
please help me, TKS

Related

[Q] Stuck in bootloop Jellybean

Hello All, I flashed the V2 version of the JB Rom on my CDMA GNex and it was working great until I rebooted my phone. Now It is bootlooping.
I can boot into recovery
This is what I have done:
Battery/Sim Card Pull
Catch Wipe/Factory data reset
Tried to Nanodroid back to an older rom
Tried to install AOKP back
All lead to bootlooping
I am sorry if this is has been addressed but any help would be greatly appreciated.
I got it to boot. After many tries it just turned on. Go figure.
How did you exactly get it to work. You said after many tries it just worked. What kind of "tries" did you do because I'm having the same issue? I tried nandroid restore, full system wipe, reinstall of AOKP build40, etc. It keeps bootlooping. Help
If all else fails, Nexus Factory Images will always be available.
Its been so long since I done the fastboot and stock 4.0.4. I'm afraid I have forgotten. I looked at that page and downloaded the stock image but I'm not sure how to use the fastboot and adb commands anymore.
elusiveaura said:
Its been so long since I done the fastboot and stock 4.0.4. I'm afraid I have forgotten. I looked at that page and downloaded the stock image but I'm not sure how to use the fastboot and adb commands anymore.
Click to expand...
Click to collapse
Well, if you have ADB and fastboot installed, that's a good start. All you need to do is unzip the file and place it where your terminal will recognize it. Then turn on USB debugging on in developer settings, then boot into your boot loader (Power + Volume Up + Volume Down) and type in "sh flash-all.sh" or you can do it manually, "fastboot flash recovery recovery.img, fastboot flash bootloader bootloader.img" etc... This will wipe all your data, including your SD card.

Galaxy Nexus reboot loop flashing error FAIL Exceed Buffer Size

My Galaxy Nexus reboots a few seconds after starting up. I don't have anything other than stock installed and I've tried following several guides here trying to flash it myself since the built-in recovery mode wipe data/factory reset does nothing.
I did notice something strange which following a guide, when I oem unlock and reboot the fastboot mode it locks itself again like I didn't do anything at all. This was a problem when I was using the Android Toolkit too but I managed to over ride my own fastboot oem unlock commands in between its batch file commands and got to an error "FAIL Exceed Buffer Size"
I believe if I can fix or know what to do with that error I can successfully bring my phone back to factory defaults I just don't know what to do! I tried looking for the error on this forum and it came up with 0 results and google isn't helping much either.
I'd appreciate any help regarding this, even if it means my phone is beyond repair I just want to know!
Thanks guys!
celeadyne said:
My Galaxy Nexus reboots a few seconds after starting up. I don't have anything other than stock installed and I've tried following several guides here trying to flash it myself since the built-in recovery mode wipe data/factory reset does nothing.
I did notice something strange which following a guide, when I oem unlock and reboot the fastboot mode it locks itself again like I didn't do anything at all. This was a problem when I was using the Android Toolkit too but I managed to over ride my own fastboot oem unlock commands in between its batch file commands and got to an error "FAIL Exceed Buffer Size"
I believe if I can fix or know what to do with that error I can successfully bring my phone back to factory defaults I just don't know what to do! I tried looking for the error on this forum and it came up with 0 results and google isn't helping much either.
I'd appreciate any help regarding this, even if it means my phone is beyond repair I just want to know!
Thanks guys!
Click to expand...
Click to collapse
best advice,flash back to stock,root the phone,and use bootunlock on your phone to unlock it,it wont wipe your data,then download a recovery.img and flash it with the flashify app,almost everything done with apps and no data loss.
pattyboi:) said:
best advice,flash back to stock,root the phone,and use bootunlock on your phone to unlock it,it wont wipe your data,then download a recovery.img and flash it with the flashify app,almost everything done with apps and no data loss.
Click to expand...
Click to collapse
I can't flash the phone to stock because of that FAIL error, and I can't root the phone because it reboot loops before I can enable USB debugging in the OS.
celeadyne said:
I can't flash the phone to stock because of that FAIL error, and I can't root the phone because it reboot loops before I can enable USB debugging in the OS.
Click to expand...
Click to collapse
i mean not using toolkit,using actual fasboot. BTW: do you have a custom recovery? if so you could just adb sideload & if you can get the phone into fastboot mode and just flash a recovery then adb sideload after wiping all partitions && did you try using odin to flash back to stock (i dunno if there are odin images available,i apoligize if not)

[Q] Nexus 7 2013 become a brick (soft or hard?)

Today my tablet had been frozen and not react to anything. (It was in idle state, I try to turn on the screen, but it remain black) I decided to restart my tablet, but now it struck at the Google logo.
I tried to wipe cache with no success ( imgur.com/QfDObvr)
I tried to make a factory reset with no success. (imgur.com/Wg4Y5sp )
(I am not friendly with android development, but I try to flash a new stock image on it with the guidance of this article:
blog.laptopmag.com/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
But it failed at the adb erase commands because them cant reach the partition too.
The problem look like is the system can not access the cache and other drives, my question is it a hardware error or software error?
Any help appreciated! Thanks!
NoNameProvided said:
Today my tablet had been frozen and not react to anything. (It was in idle state, I try to turn on the screen, but it remain black) I decided to restart my tablet, but now it struck at the Google logo.
I tried to wipe cache with no success ( imgur.com/QfDObvr)
I tried to make a factory reset with no success. (imgur.com/Wg4Y5sp )
(I am not friendly with android development, but I try to flash a new stock image on it with the guidance of this article:
blog.laptopmag.com/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
But it failed at the adb erase commands because them cant reach the partition too.
The problem look like is the system can not access the cache and other drives, my question is it a hardware error or software error?
Any help appreciated! Thanks!
Click to expand...
Click to collapse
Make sure you have adb and fastboot working.
download proper image from here:
https://developers.google.com/android/nexus/images
extract the tgz to your computer and navigate to the folder.
plugin phone and put it in fastboot mode
from a terminal run flash-all.bat (if windows) or flash-all.sh (if Linux)
you can edit flash-all to remove the -w if you don't want to wipe your user data.

[Q] [HELP] Bricked Galaxy Nexus (maguro)

Hello guys, a friend of mine has a galaxy nexus with some problems.
When I turn on the phone, it starts booting normally, but a few seconds after getting into "desktop" it starts popping up errors saying that the process as stopped.
I've already tried a few things, but without success. I'm running out of ideas and here I'm asking for your help.
Things I've tried:
-Boot into recovery mode and wipe all data.
The phone says that the operation completed successfully, but after rebooting the phone remains the same. All apps, wallpaper, lock screen, etc. It seems that nothing was changed by this process.
-Flash a original google ROM
Following the tutorials, the first step is to unlock the bootloader with fastboot oem unlock. The phone shows a confirmation asking if I want to unlock it, I say yes, and it shows "status: unlocked". But after rebooting the phone it is locked again!!!
I tried to flash the room without rebooting the phone after unlocking it,
Code:
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-maguro-i9250xxla02.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-takju-imm76i.zip
The first command to flash the bootloader also says that completes successfully, but when I'm flashing the radio it will complain saying that the phone has the wrong bootloader version installed.
-Flashing via Odin
It fails when is flashing system.img to the phone
-Flash custom recovery - fastboot flash recovery recovery.img
The process completes "successfully" but when I boot into recovery mode, there is the original one and not the one I just flashed.
-emmc brickbug - partition scanner
I found this thread http://forum.xda-developers.com/showthread.php?t=1823918 and tried to run the partition scanner. As I can't have the phone on enough time to use adb shell, I tried to use this scanner via adb sideload but the phones returns an error when running it. (probably because it doesn't have busybox installed, not sure)
After trying all of steps above, the phone is still the same... nothing changed. Once, I managed to connect it to the pc as an usb storage device, and was able to copy some photos from the phone and deleted them. But after rebooting they were all there again. It seems that all write changes are not persistent.
I'm out of ideas now... Do you have any idea of what is the problem? Or any suggestion for me to try?
Thanks in advance
I believe that there is a script in the android SDK tools called flashall.bat which will reflash the kernel, bootloader, recovery, ROM ect. I'm not sure how to use it, but you could potentially try that
Hi, thanks for you suggestion, but unfortunately it didn't work.
I had a look at the flashall.bat script and it runs the same commands I run manually.
I think that the phone might have some hardware problem... Normally I would buy a new phone, but I'm trying to fix it because it is important for my friend and for me because it is challenging.
I guess that the next thing I will try, will be trying to run emmc_find_brick script by @hg42 via sideload
Try formatting /system and reinstall android. Power your device into bootloader mode. Make sure your device is unlocked. Also, make sure you have the factory image downloaded. After your device is plugged in into your computer, use this fastboot command: fastboot erase system. This will delete everything from /system. Also format /data and /cache: fastboot erase data and fastboot erase cache. After that, try installing the factory image again.

Android bot error blinking on boot after wipe partition cache process

Model: Asus Zenfone 2 ZE551ML
After updating to latest version i decided to wipe partition cache while on the process it showed erasing android bot then restarted and hung on asus logo for nearly an hour so i decided there is some problem and force switched off then after switching on it shows the blinking android error bot.........im unable to enter neither recovery mode nor fastboot mode(when entering it shows for a some seconds waiting fastboot cmd bt then comes again to the normal boot screen)....
Its been nearly a week i went thru various post and tried most of the methods like entering recovery mode thru adb(as im unable to enter fastboot mode it shows in cmd waiting for device) and pressing both buttons same for stock recovery(it shows some lines saying in last line can't mount recovery)
SO CAN SOMEBODY THROW LIGHT ON WHAT EXACTLY NEEDS TO BE DONE TO RECOVER MY PHONE FROM THIS ERROR.... would be grateful and thanks in advance.
Feel like you for the same worries as I did.
Try to flash bootdroid.img / boot.img / recovery.img with fastboot commands and that should do the trick.
For recovery I renamed twrp.img to recovery.img to get twrp right away
cuberio1 said:
Feel like you for the same worries as I did.
Try to flash bootdroid.img / boot.img / recovery.img with fastboot commands and that should do the trick.
For recovery I renamed twrp.img to recovery.img to get twrp right away
Click to expand...
Click to collapse
now i got some idea bt can u tell a bit elaborate what exactly i need to do..... (downloads and cmd commands)
Rockybala90 said:
Model: Asus Zenfone 2 ZE551ML
After updating to latest version i decided to wipe partition cache while on the process it showed erasing android bot then restarted and hung on asus logo for nearly an hour so i decided there is some problem and force switched off then after switching on it shows the blinking android error bot.........im unable to enter neither recovery mode nor fastboot mode(when entering it shows for a some seconds waiting fastboot cmd bt then comes again to the normal boot screen)....
Its been nearly a week i went thru various post and tried most of the methods like entering recovery mode thru adb(as im unable to enter fastboot mode it shows in cmd waiting for device) and pressing both buttons same for stock recovery(it shows some lines saying in last line can't mount recovery)
SO CAN SOMEBODY THROW LIGHT ON WHAT EXACTLY NEEDS TO BE DONE TO RECOVER MY PHONE FROM THIS ERROR.... would be grateful and thanks in advance.
Click to expand...
Click to collapse
maybe you have flashed wrong droidboot img for fastboot partition.. if you manage to enter fastboot mode, you may try to type
fastboot erase cache
but only if you able to enter fastboot..usually wiping cache from stock recovery may stuck but it can be cleared with that command.. but if you are unable to enter fastboot mode sorry then, hope that someone expert can help you..

Categories

Resources