Hopefully not but probably a brick - Samsung Galaxy Nexus

Long story short, I flashed an alleged gps fix file for liquid and it bootlooped the phone to the point of killing the battery within 5 minutes. Now really stuck..
Tried to flash a google image, nothing would "write" on the phone.
Tried Odin. There, it gets stuck stuck at "NAND write start" and phone gets really really hot. Phone didn't boot to Download mode when pressing volume down-power. I have a picture of phone-yellow exclamation-computer on the screen.
Stuck..

Check the box to replace the bootloader and try odin again.
Then see if you can boot into fastboot (both volume buttons and power from an off state).
Also try (and this is a direct quote from a user who supposedly found success)
"Open CF_ODIN_YAKJU_IMM76D_full and remove the radio.img file that it is failing on"

Jubakuba said:
Check the box to replace the bootloader and try odin again.
Then see if you can boot into fastboot (both volume buttons and power from an off state).
Also try (and this is a direct quote from a user who supposedly found success)
"Open CF_ODIN_YAKJU_IMM76D_full and remove the radio.img file that it is failing on"
Click to expand...
Click to collapse
THANK YOU!!!
Green bar started moving & I thought it was over; now it's stuck at about 30% (<ID:0/003> system.img), at least it showed life. It did bootloader, boot & recovery.img
Do I need to perhaps check Phone and CSC as well?

Vangelis13 said:
THANK YOU!!!
Green bar started moving & I thought it was over; now it's stuck at about 30% (<ID:0/003> system.img), at least it showed life. It did bootloader, boot & recovery.img
Do I need to perhaps check Phone and CSC as well?
Click to expand...
Click to collapse
Am at total loss right now, nothing works..
Called Samsung Germany and will send it in for repair unless anyone has a work around.

If you can, boot into recovery. Wipe cache, dalvik cache, factory reset, and battery stats. If you were rooted, then don't send it in. Rooting does violate you agreement to use the device. It will also void your warrenty. Do everything you can your self, and send it in at a complete last resort.

Vangelis13 said:
Am at total loss right now, nothing works..
Called Samsung Germany and will send it in for repair unless anyone has a work around.
Click to expand...
Click to collapse
if odin wrote to the bootloader, try using fastboot at this point. see if it can get you anywhere.

Can't get into anything, all I see on the screen is the attached...
Odin doesn't do anything either anymore, stops at "NAND write start".
Sent from my Nexus S using xda premium

gregory99mar said:
If you can, boot into recovery. Wipe cache, dalvik cache, factory reset, and battery stats. If you were rooted, then don't send it in. Rooting does violate you agreement to use the device. It will also void your warrenty. Do everything you can your self, and send it in at a complete last resort.
Click to expand...
Click to collapse
Hopefully they'll oversee that if I have to send it in; I did however manage before all this to lock & unlock the bootloader so everything must be gone..

Any ideas guys?
Sent from my Nexus S using xda premium

Vangelis13 said:
Any ideas guys?
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Try running odin again, but this time, only leave the bootloader, boot and recovery images in the .tar. As well, try clicking "start" on odin first, then plugging your device into your PC. Hopefully that will restore your bootloader and you'll be able to use fastboot to flash the system image.

efrant said:
Try running odin again, but this time, only leave the bootloader, boot and recovery images in the .tar. As well, try clicking "start" on odin first, then plugging your device into your PC. Hopefully that will restore your bootloader and you'll be able to use fastboot to flash the system image.
Click to expand...
Click to collapse
Thank you efrant!
It gets stuck at "NAND Write Start!!". Yesterday, when I was trying to send through fastboot, it wouldn't write anything either. It kept returning "too many links". Something got really borked, what ever the fck I did..
Service it is then probably.

Related

Help phone stuck at boot screen

Hello. I just tried to unlock the bootloader on on Verizon Galaxy nexus. Now it's stuck at the bootscreen with the lock image. I did a search and couldn't find a exact answer for my issue. I hope I haven't bricked my phone. Anyway, any help would be appreciated.
I wasn't trying to root just unlock the bootloader. It appeared everything went ok but, now I'm stuck. I used the same method for unlocking the bootloader on my GSM G-nex and it worked.
I know I've done something wrong or this may be something simple. I just need help so I can use my phone.
are you able to boot into the bootloader? if so you should be able to recover and can't worry a little less.
same thing here... I posted a request for a LTE boot.img since can still get into the bootloader
Goat_For_Sale said:
are you able to boot into the bootloader? if so you should be able to recover and can't worry a little less.
Click to expand...
Click to collapse
No I don't believe I can. When I type fastboot it just says "waiting on device" I can hold the volume down & power buttons and get to the screen were it says "start" at the top and below that "downloding"
Yea, that was what I was eluding too, The device just came out and google released the GSM image. I am sure that it will appear online in the near future.
if you are able to get into the bootloader does it say that its unlocked ? is your google splash screen showing the unlocked padlock ? you could also try fastboot flash recovery to get cwm on there and provide additional potential solutions.
---------- Post added at 11:40 AM ---------- Previous post was at 11:39 AM ----------
qnet said:
No I don't believe I can. When I type fastboot it just says "waiting on device" I can hold the volume down & power buttons and get to the screen were it says "start" at the top and below that "downloding"
Click to expand...
Click to collapse
That is download mode used for odin.
hold BOTH volumn buttons and power to get into the bootloader/fastboot
Goat_For_Sale said:
Yea, that was what I was eluding too, The device just came out and google released the GSM image. I am sure that it will appear online in the near future.
if you are able to get into the bootloader does it say that its unlocked ? is your google splash screen showing the unlocked padlock ? you could also try fastboot flash recovery to get cwm on there and provide additional potential solutions.
---------- Post added at 11:40 AM ---------- Previous post was at 11:39 AM ----------
That is download mode used for odin.
hold BOTH volumn buttons and power to get into the bootloader/fastboot
Click to expand...
Click to collapse
Yeah, when I did the procedure it said that it was unlocked. Everything looked ok , it booted show the unlock symbol under Google. It then went to the colorful animation and was stuck there. At that time I pulled the battery and, it's been stuck at the screen showing google and the unlock image.
qnet said:
Yeah, when I did the procedure it said that it was unlocked. Everything looked ok , it booted show the unlock symbol under Google. It then went to the colorful animation and was stuck there. At that time I pulled the battery and, it's been stuck at the screen showing google and the unlock image.
Click to expand...
Click to collapse
you should have let the animation run for like 10 minutes the phone has to rebuild the first boot can take like 15 minutes sometimes.
try booting into the bootloader see if that works still
Sorry I wasn't paying attention and didn't read the part were you told me how to get to the fastboot screen. I'm there now. Can I just relock or fix the bootloader from problem there? It shows it unlocked at the fastboot screen.
qnet said:
Sorry I wasn't paying attention and didn't read the part were you told me how to get to the fastboot screen. I'm there now. Can I just relock or fix the bootloader from problem there? It shows it unlocked at the fastboot screen.
Click to expand...
Click to collapse
you could try fastboot oem lock and see if that works but if the phone wasn't booting i don't know if that will fix it but worth a shot.
try it out and see. it shouldn't do any harm to try
I had the issue with the failure to boot up after doing the fastboot oem unlock (I had to use the pda net drivers to get my device recognized to get even that far). I did a lot of things like pulling the battery, locking again and then unlocking and nothing worked until I went here http://rootzwiki.com/topic/11732-galaxy-nexus-root-procedure-adb-method/, then downloaded the files following their directions and doing the fastboot boot boot.img command. It took a LONG time to boot up, but it did boot finally.
GirLuvsDroid said:
I had the issue with the failure to boot up after doing the fastboot oem unlock (I had to use the pda net drivers to get my device recognized to get even that far). I did a lot of things like pulling the battery, locking again and then unlocking and nothing worked until I went here http://rootzwiki.com/topic/11732-galaxy-nexus-root-procedure-adb-method/, then downloaded the files following their directions and doing the fastboot boot boot.img command. It took a LONG time to boot up, but it did boot finally.
Click to expand...
Click to collapse
Thank you, I'll try that.
I have another question. One of the selections on the fastboot screen is recovery mode. Can I try that or is this something were you have to have a rom stored on a sd-card?
qnet said:
I have another question. One of the selections on the fastboot screen is recovery mode. Can I try that or is this something were you have to have a rom stored on a sd-card?
Click to expand...
Click to collapse
you could download the recovery image from
http://forum.xda-developers.com/showthread.php?t=1392336
then when connected in fast boot flash it with
fastboot flash recovery recovery.img
(rename the file from the linked thread to recovery.img)
this should write your custom recovery partition.
once you have that though you are still not going to be able to boot but it would allow you to flash a nandroid backup if someone made one for you or a LTE based rom
EDIT: you could also try a factory data reset and wipe dalvk cache from withing cwm. that may fix your boot problem
I had this problem, too.
I downloaded Clockwork Recovery and used 'fastboot boot LTErecovery_cwr.img' to boot into it, I wiped data and cache / factory reset and then rebooted. It rebooted twice, but after ten minutes or so I was back to the ICS Welcome screen. All of the files I'd put on my internal storage were wiped (during the oem unlock, I assume) but I'm in the stock rom but Superuser was installed and I have root access.
Hope it helps.
EDIT: looks like this is the same thing Goat_For_Sale posted above, but his command flashes CWM where mine temporarily boots into it. Since most of us will be installing CWM anyway I'd recommend using his command instead.
mixedlemon said:
I had this problem, too.
I downloaded Clockwork Recovery and used 'fastboot boot LTErecovery_cwr.img' to boot into it, I wiped data and cache / factory reset and then rebooted. It rebooted twice, but after ten minutes or so I was back to the ICS Welcome screen.
Hope it helps.
Click to expand...
Click to collapse
where did you get the lterecovery_cwr.img ? could you link to it please
I linked to the thread in my post, but here's a link to the mediafire upload from that thread: http://www.mediafire.com/?mdf0mtacskob5yg
mixedlemon said:
I linked to the thread in my post, but here's a link to the mediafire upload from that thread: http://www.mediafire.com/?mdf0mtacskob5yg
Click to expand...
Click to collapse
Thanks, my bad I didn't realize you were refering to the recovery image, thought it was the boot image for the LTE device.
Goat_For_Sale said:
Thanks, my bad I didn't realize you were refering to the recovery image, thought it was the boot image for the LTE device.
Click to expand...
Click to collapse
Ahh no problem.
I got pretty worried for a second that I'd already broke my shiny new Nexus, so I'm really hoping I can help out someone else that had the same problem.
Solved
I believe it's fixed now. I use the method that GirLuvsDroid posted from the Rootzwiki forum. Once it rebooted, I stopped there and didn't root the phone. I was just happy to get it booted.
It's downloading all my apps and settings now. Thanks to everyone who tried to help me, I really appreciate. This was a good learning experience for me.
qnet said:
I believe it's fixed now. I use the method that GirLuvsDroid posted from the Rootzwiki forum. Once it rebooted, I stopped there and didn't root the phone. I was just happy to get it booted.
It's downloading all my apps and settings now. Thanks to everyone who tried to help me, I really appreciate. This was a good learning experience for me.
Click to expand...
Click to collapse
So you were just able to go through the Rootzwiki method? Were you stuck at "Downloading...Do not turn off target !!" screen when you went to boot screen originally? My device still can't be detected :/

GN not starting

hi,
i need help my GN is not starting after I flashed a theme all i can just get into clock mode recovery even i didn't have any back up or any restore point it just shows google logo when i start. Please helppppppppppppppppppp pleaseeeeeee
thankzzz
now i am stuck on below attachment please help thnkzz so much for all reply till now
since you didn't do a Android your basically screwed so all you data is gone you only hope is to transfer a file through fastboot(can you even do that?) Or boot to Odin mode and flash a stock image
Sent from my Galaxy Nexus using XDA App
GSM or LTE Gnex? What ROM were you running?
Golden rule: Do a backup before doing anything to your phone!
Now all you can do is to download EXACTLY same ROM as you were using by now, wipe cache/dalvik-cache, flash this ROM once again and hope that i'll boot. If it won't you'll have to wipe /data is well.
Sleuth255 said:
GSM or LTE Gnex? What ROM were you running?
Click to expand...
Click to collapse
HI
its gsm i tried to flashed the same rom but still the same only i can access is to recovery
cordell507 said:
since you didn't do a Android your basically screwed so all you data is gone you only hope is to transfer a file through fastboot(can you even do that?) Or boot to Odin mode and flash a stock image
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
tnkz bro but i am new to android please help how to do it with Odin
well since you can boot into recovery try searching in your sdcard folders if youve left a ROM .zip there laying around and if this is the case just flash it and youre back on track
nonione said:
well since you can boot into recovery try searching in your sdcard folders if youve left a ROM .zip there laying around and if this is the case just flash it and youre back on track
Click to expand...
Click to collapse
unfortunatly i delete system file and data file also in recovery i tried to flash the zip update but no result helpppppppppppppppp
salym said:
unfortunatly i delete system file and data file also in recovery i tried to flash the zip update but no result helpppppppppppppppp
Click to expand...
Click to collapse
This will help you get back to stock
http://forum.xda-developers.com/showthread.php?t=1392310
Sent from my GNex {GSM} T-Mobile
Change your spark plugs.
Sent from my Nexus in Texas.
spaceman860 said:
This will help you get back to stock
http://forum.xda-developers.com/showthread.php?t=1392310
Sent from my GNex {GSM} T-Mobile
Click to expand...
Click to collapse
Hi bro i tired with Odin but stops on userdata any help thnkzzzz
salym said:
hi,
i need help my GN is not starting after I flashed a theme all i can just get into clock mode recovery even i didn't have any back up or any restore point it just shows google logo when i start. Please helppppppppppppppppppp pleaseeeeeee
thankzzz
Click to expand...
Click to collapse
i am stuck on this now please help
ouch... softbrick.
put your phone down.
take a deep breath or two.
If you are old enough, grab a beer and relax for a bit. Think calming thoughts.
Now, start learning about how to mod your GNex. We can help.
Here's your First assignment:
find out if you still have a bootloader by booting into fastboot mode. Report back with your findings and a screenshot!
Sleuth255 said:
ouch... softbrick.
put your phone down.
take a deep breath or two.
If you are old enough, grab a beer and relax for a bit. Think calming thoughts.
Now, start learning about how to mod your GNex. We can help.
Here's your First assignment:
find out if you still have a bootloader by booting into fastboot mode. Report back with your findings and a screenshot!
Click to expand...
Click to collapse
Still have a bootloader? Are you serious? You need to learn how to use an android device as well.
To the OP: Do a factory reset in Clockwork and go to mounts
and format /system. Flash the ROM zip. Profit.
Absolutely serious. Have you been reading this thread? The OP needs to start at ground zero and stop just trying every tool he/she sees. My purpose was to get this person to do some research and I was establishing a knowledge baseline. One plan I was considering was to help the OP install the GNex toolkit then locate stock images and obtain a working build. Your cryptic one liner bit should prove vastly more useful to this guy though. I'll let you have at it and go back to my dev work. lol at least this post was a good way to make sure gapps/root capabilities are properly cooked into my latest test build ....
Sent from my Full AOSP on Toro using xda premium
Sleuth255 said:
ouch... softbrick.
put your phone down.
take a deep breath or two.
If you are old enough, grab a beer and relax for a bit. Think calming thoughts.
Now, start learning about how to mod your GNex. We can help.
Here's your First assignment:
find out if you still have a bootloader by booting into fastboot mode. Report back with your findings and a screenshot!
Click to expand...
Click to collapse
U r right i am not good in android but i tried to be and this happens, meanwhile nothing shows after i start the device it shows the !!!! mark with device the PC logo,this happens due to ODin actually the SUMSUNG ADB interface shows ! mark because i cant debug from device even no bootloader works any more thnkz for replying
*facepalm*
OP, you are holding it wrong.
I can think of at least 2 ways to recover from a situation like this. Both are well described in these forums (search works 99% of the time).
....
Oh come on, you don't have the zip of the last rom you flashed, get another one, hey, its free right? **** we dont know nothing about but we'll flash it anyways!
Man...If you have cwm recovery, you're safe. No need to go messing with fastboot (forget odin) just yet. Now stop wasting everybody's time and learn to help yourself.
Here's a few tags to get you started:
cwm, recovery, adb, bootloader, fastboot
bk201doesntexist said:
*facepalm*
OP, you are holding it wrong.
I can think of at least 2 ways to recover from a situation like this. Both are well described in these forums (search works 99% of the time).
....
Oh come on, you don't have the zip of the last rom you flashed, get another one, hey, its free right? **** we dont know nothing about but we'll flash it anyways!
Man...If you have cwm recovery, you're safe. No need to go messing with fastboot (forget odin) just yet. Now stop wasting everybody's time and learn to help yourself.
Here's a few tags to get you started:
cwm, recovery, adb, bootloader, fastboot
Click to expand...
Click to collapse
i tried more than one day on this issue its only starts with !!! mark on it nothing else, i have attached the pic i cant access any bootloader or any cwm or any thing all i did with Odin and stuck to attached pic even i start the device its shows the same pic.
http://www.youtube.com/watch?v=WdM2M8Nz6QQ this I used on Odin
thnkzz
As I suspected earlier, it appears that the OP may have trashed his bootloader partition when he tried using Odin to flash the 4.0.2 factory image (which includes a bootloader). At one point he had CWM but not any more since he can't boot to the recovery partition.
Another possibility is that the Odin tool itself places the device in this mode and it can't be manually reverted by starting up in fastboot mode. Looking at the picture, it literally appears that the phone is saying that a flashing operation is half finished but the phone has lost the PC connection... This would be a lot like what I've experienced with iPhones.
In either case, I can deduce that Odin is the tool to use to clear this softbrick.
Hopefully, it'll be flame-off now Sdobron. Perhaps you might want to help out here since I'm not up to speed on the Odin tool myself and would like to learn more about it.
@salym: I know this may be redundant but I need to establish your problem baseline empirically. Once again, can you verify that when you hold vol down/vol up then press power that you get the image you posted?
Use Fastboot!
Dude, it looks like your problem is with crappy boot sector.
While turning on your phone, hold both volume up and volume down buttons, and long press power button untill you feel single vibrate feedback.
Then connect your phone to the computer via USB, and if it doesn't detect drivers, google "samsung android usb driver". Additionally you can install PDANet application (X64 or x86 depending on you system).
THen download Fastboot - there are plenty of instructions how to flash it, and flash stock images (that come with radio, boot sector, rom itself, etc) - there are also plenty of discussions about how to do it. PM if you have any other questions!

[Q] bootloop no recovery

Wife's Verizon Galaxy Nexus 4.2.2
Bone stock, completely un-tampered with, stuck in bootloop. If I try to access recovery I just get the Android dude with the red exclamation point sign, and eventually it reboots and back to the bootloop problem.
I need to save the data on the phone (pictures/videos). Flashing factory image erases all data, but could a person use Odin to flash the Verizon 4.2.2 OTA update? Is it possible or will Odin erase everything anyway?
That is stock recovery. Odin flash also wipes user data. Is the bootloader unlocked?
a maguro wrote this.
Oh, sorry for my ignorance, and the bootloader is locked.
You may try this awesome method: http://forum.xda-developers.com/showthread.php?t=2016628
The thread talks about GSM Nexus but may also work on your device (I think they have same CPU and bootloader). No warranties.
My Gnexi said:
You may try this awesome method: http://forum.xda-developers.com/showthread.php?t=2016628
The thread talks about GSM Nexus but may also work on your device (I think they have same CPU and bootloader). No warranties.
Click to expand...
Click to collapse
Exactly, do it at your own risk.
a manta wrote this.
Does seems like the most promising option at this point. Now if I can just find the OMAPFlash, the link is no longer good.
I think I have a copy on my laptop, will check later.
Edit: No need for my copy. The original post from gsmhosting.com by legija has a link that led me to http://d-h.st/XNv it's on dev-host and by efrant so it must be good
My Gnexi said:
I think I have a copy on my laptop, will check later.
Edit: No need for my copy. The original post from gsmhosting.com by legija has a link that led me to http://d-h.st/XNv it's on dev-host and by efrant so it must be good
Click to expand...
Click to collapse
Yes, its the same file.
a manta wrote this.
woohoo, it worked, I now have an unlocked bootloader. If I am correct I should now be able to flash a no-wipe recovery onto her device? I've been searching like crazy, but it seems like every other thread I find contradicts the previous so I'm still pretty lost.
hillbillymo said:
woohoo, it worked, I now have an unlocked bootloader. If I am correct I should now be able to flash a no-wipe recovery onto her device? I've been searching like crazy, but it seems like every other thread I find contradicts the previous so I'm still pretty lost.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1812959
You will be able to flash a custom recovery or even only boot a custom recovery through fastboot ('fastboot flash recovery recovery.img' for the first, 'fastboot boot recovery.img' for the latter). Read that first post on the thread I linked you to. It will teach you what is what and how to interact with the tools.
Amazing, I managed to load CWM, however it appears to me that all I will really be able to do from it is a factory reset, is that correct? Also do the fastboot flashes take even if USB Debugging is turned off?
hillbillymo said:
Amazing, I managed to load CWM, however it appears to me that all I will really be able to do from it is a factory reset, is that correct? Also do the fastboot flashes take even if USB Debugging is turned off?
Click to expand...
Click to collapse
USB debugging only has an effect when the OS is booted
Sent from my Galaxy Nexus
hillbillymo said:
Amazing, I managed to load CWM, however it appears to me that all I will really be able to do from it is a factory reset, is that correct? Also do the fastboot flashes take even if USB Debugging is turned off?
Click to expand...
Click to collapse
While on CWM, ADB/USB debugging is active.
Use 'adb pull /sdcard/' to pull all contents under /sdcard/.
a manta wrote this.
Success...kind of. The "adb pull /sdcard/" command did not work, for some reason it kept freezing on the first file it found. I then navigated to the Camera folder and pulled all the .jpg files, which is what I was primarily after. ADB did not like pulling .mp4 files so I just called it good there.
After that I tried using fastboot to flash boot, system, recovery, and even radio images, but phone was still in bootloop. I then ran the flash all batch file that came with the factory image I downloaded, everything went fine, but still no boot. Also tried Odin to flash factory image, but every time I clicked on "Start" I would get a "program stopped responding" error message(no matter what version of Odin I used).
At this point I believe the phone has a major problem that cannot be repaired with software, time to lock the bootloader and send it in I suppose. If anybody has any other ideas let me know, but I'm not very hopeful.
Thank you to everyone that contributed to my data recovery, this really is an awesome place, guess I'll stick around.

Bricked s4

so i tried rooting my phone and it bricked...i had the "recovery in kies " error but now i got the screen blocked in boot ..than i tried to install costum roms using odin but aparently odint doesn't work....i had this same problem on my s2 and i solved it but now i cant solve this anymore...i have read about this on other threads but i couldnt fix it...i can only put my phone on download mode ...i dont know what to do anymore since odin doesnt work at all ( it keeps saying fail) ..i got the drivers installed ..please some1 help me i've spent 5 hours trying to solve this ..and now again i get the firmware upgrade encountred an issue .....but as i said cant solve it with samsung kies
smeen23 said:
so i tried rooting my phone and it bricked...i had the "recovery in kies " error but now i got the screen blocked in boot ..than i tried to install costum roms using odin but aparently odint doesn't work....i had this same problem on my s2 and i solved it but now i cant solve this anymore...i have read about this on other threads but i couldnt fix it...i can only put my phone on download mode ...i dont know what to do anymore since odin doesnt work at all ( it keeps saying fail) ..i got the drivers installed ..please some1 help me i've spent 5 hours trying to solve this ..and now again i get the firmware upgrade encountred an issue .....but as i said cant solve it with samsung kies
Click to expand...
Click to collapse
If you can put your phone in download mode you're not bricked.
Use Odin to get back to stock
http://forum.xda-developers.com/showthread.php?t=2258628
Once that is done use CF Root to root with Odin
http://forum.xda-developers.com/showthread.php?t=2294005
baseballfanz said:
If you can put your phone in download mode you're not bricked.
Use Odin to get back to stock
http://forum.xda-developers.com/showthread.php?t=2258628
Once that is done use CF Root to root with Odin
http://forum.xda-developers.com/showthread.php?t=2294005
Click to expand...
Click to collapse
i still get fail from odin....thats actually the thing i dont get....can it be from drivers?
Are you using the cable that came with the phone? I had the same problem and its because I was using another cable. If Odin isn't working. Kies should work as well. P.m. me if you need more help.
Sent from my SGH-M919 using XDA Premium 4 mobile app
eddies92 said:
Are you using the cable that came with the phone? I had the same problem and its because I was using another cable. If Odin isn't working. Kies should work as well. P.m. me if you need more help.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes i am using the cable....and my problem keeps switching from firmware issue to stuck at boot....i tried with kies but it doesnt recognize my phone when i try emergency firmware recovery and when i try firmware upgrade and initialisation it says that it need 6gb free and i dont have enough space....i installed kies in another partition where i have 43gb free and still that error
smeen23 said:
yes i am using the cable....and my problem keeps switching from firmware issue to stuck at boot....i tried with kies but it doesnt recognize my phone when i try emergency firmware recovery and when i try firmware upgrade and initialisation it says that it need 6gb free and i dont have enough space....i installed kies in another partition where i have 43gb free and still that error and btw when i connect my phone to kies it says connecting... and i et to troubleshot the error and when i do it replace the driver over and over...thats why i assumed it from drivers..i already inatlled the drivers from different places but still nothing
Click to expand...
Click to collapse
smeen23 said:
yes i am using the cable....and my problem keeps switching from firmware issue to stuck at boot....i tried with kies but it doesnt recognize my phone when i try emergency firmware recovery and when i try firmware upgrade and initialisation it says that it need 6gb free and i dont have enough space....i installed kies in another partition where i have 43gb free and still that error
Click to expand...
Click to collapse
If you are stuck in a bootloop after running the recovery file in odin (it's 1.6 GB unzipped), which is the way things sound, pull the battery and go into stock recovery. Do this by replacing the battery, holding volume up, home, and power button until the ble recovery shows in the upper left then let go. In stock recovery, scroll down 9using volume button) to wipe data/factory reset. Coose that option with the power button. You will lose ALL data on your phone and you will have to go thru setup again. When it's done choose reboot in the menu and let it reboot. Don't freak if it takes a while. In a minute or 2 you will see the screen dim and it will boot. Go thru setup, root again, install custom recovery, and if you were wise enough to have done a backup tp your SD card, you can get it back.
Good luck, there are tutorials on Youtube if you care to search for them. Here's a good one -
http://youtu.be/yEJSv9MrVAg
@getsum
Good suggestion :good:
I think the issue is that he's making things more complicated than he needs to.
A step by step by the op would be helpful if your suggestion doesn't resolve the issue
---------- Post added at 01:51 AM ---------- Previous post was at 01:39 AM ----------
Op, you're a little confusing.
Are you able to successfully use ODIN and flash stock firmware, but get stuck in a boot loop or freeze on Samsung splash?
Or ODIN fails?
From you're posts it sounds like both issues are occurring, but I think it's a posting conflict, and your issue is one or the other, unless I'm wrong, which I've been before
when i try recovery it goes to boot saying loading recovery than it goes full off and after boot screen again...i tried twrp and still nothing but the good thing is that odin passed that ..the only thing it didnt fail....maybe i didnt have the right rom ...i am downloading the official i9505 rom and i hope it will work this time....but plz if any1 can help i would apriciate it
Odin problem
I am also having a odin problem. I have tried jdownloader2 as well. Everything is giving me an error on extraction. My phone is stuck on the pulsing T-Mobile 4G LTE. Please help...my wife is looking at me like I just wasted money on a useless brick :silly:
Make sure you guys ODIN the correct Stock Firmware for your model device.
Make sure you ODIN the correct Custom Recovery for your model device.
And if you're Rooting, for example with CF-AUTO-ROOT by Chain fire, make sure you ODIN the proper version for your device.
In addition, check your USB cable to ensure it's working properly 100% of the time and have enough battery juice to perform the above procedures.
Odin problem
I have double check all the stock firmware. Got the files from 247extreme.com, given to me by DarkMenace. Several downloads of the same files...nothing seems to pass the MD5 check. The USB cable is 100%.
Biker1 said:
Make sure you guys ODIN the correct Stock Firmware for your model device.
Make sure you ODIN the correct Custom Recovery for your model device.
And if you're Rooting, for example with CF-AUTO-ROOT by Chain fire, make sure you ODIN the proper version for your device.
In addition, check your USB cable to ensure it's working properly 100% of the time and have enough battery juice to perform the above procedures.
Click to expand...
Click to collapse
jtcovington said:
I have double check all the stock firmware. Got the files from 247extreme.com, given to me by DarkMenace. Several downloads of the same files...nothing seems to pass the MD5 check. The USB cable is 100%.
Click to expand...
Click to collapse
I used the file from here to Odin back to stock when soft bricked.
http://forum.xda-developers.com/showthread.php?t=2258628
☞Sent from here☜
baseballfanz said:
I used the file from here to Odin back to stock when soft bricked.
http://forum.xda-developers.com/showthread.php?t=2258628
☞Sent from here☜
Click to expand...
Click to collapse
I have tried all of those. Everyone is an MD5 error. I feel like I may be missing something. My recovery screen has a android on his back with a red triangle. I can get to the Tmobile screen, should it stay there longer than 5 minutes?
jtcovington said:
I have tried all of those. Everyone is an MD5 error. I feel like I may be missing something. My recovery screen has a android on his back with a red triangle. I can get to the Tmobile screen, should it stay there longer than 5 minutes?
Click to expand...
Click to collapse
Go into Stock Recovery
Wipe data and Factory Reset option
Boot
And everything will be good
I had the same happen to me regarding the Android on his back with a Red X.
I had to research to find what this mmeant and what to do.
After ODIN, I would freezeion Samsung splash twice.
Pull battery
Install battery
Press Power and Vol up buttons till you see the upper left hand blue script, andtrelease buttons to get into Recovery.
I went into Stock Recovery and chose the option where it says Factory Reset.
I then Booted Successfully.
Afterwards, I ODIN'd Custom Recovery, TWRP 2.5.0.2
Biker1 said:
Go into Stock Recovery
Wipe data and Factory Reset option
Boot
And everything will be good
I had the same happen to me regarding the Android on his back with a Red X.
I had to research to find what this mmeant and what to do.
After ODIN, I would freezeion Samsung splash twice.
I went into Stock Recovery and chose the option where it says Factory Reset.
I then Booted Successfully.
Afterwards, I ODIN'd Custom Recovery, TWRP 2.5.0.2
Click to expand...
Click to collapse
How long should it sit in the Tmobile 4G LTE screen?
jtcovington said:
How long should it sit in the Tmobile 4G LTE screen?
Click to expand...
Click to collapse
Could be several minutes, and a little longer.
Just wait it out after you choose Factory Reset/wipe option and Boot.
Biker1 said:
Could be several minutes, and a little longer.
Just wait it out after you choose Factory Reset/wipe option and Boot.
Click to expand...
Click to collapse
I am now stuck on the samsung logo with the blue writing on the top. What the hell have I done? PLEASE HELP! I probably need instructions like I am 2 years old...at least that is how this process is making me feel. I did read that as long as I can get to download mode it is okay. But I can't seem to get a good file for odin to work with.
jtcovington said:
I am now stuck on the samsung logo with the blue writing on the top. What the hell have I done? PLEASE HELP! I probably need instructions like I am 2 years old...at least that is how this process is making me feel. I did read that as long as I can get to download mode it is okay. But I can't seem to get a good file for odin to work with.
Click to expand...
Click to collapse
Pull battery
Install battery
Press Power and Vol up buttons together
When you see tiny blue script in upper left, immediately release buttons
See if you boot into Recovery.
If you can't boot into recovery and stuck with the tiny blue letters
Then......
Start again.
ODIN Stock Firmware
Make sure only the Auto Reboot and F reset boxes are checked
Click the PDA box and load the tar file
It will take a couple of minutes for the md5 checksum match
Then the file will auto load into the PDA box
Press Start
Will take about 8 minutes to complete
Your will see the upper left ODIN box turn Blue and Pass
Let the device boot
Wait several minutes
If stuck on Samsung Splash
Pull battery
Install battery
Don't power on device
Press Power and Vol up buttons
Enter Recovery
Scroll to Factory Reset/ option with Vol toggle
Press Power once Factory reset is highlighted
Let device Boot
Could take 10 minutes or so
Have Patience
If above successful
ODIN your Custom Recovery
Also Root if needed, but do the ODIN first tossee if it gets done.
Good luck
Biker1 said:
Pull battery
Install battery
Press Power and Vol up buttons together
When you see tiny blue script in upper left, immediately release buttons
See if you boot into Recovery.
If you can't boot into recovery and stuck with the tiny blue letters
Then......
Start again.
ODIN Stock Firmware
Make sure only the Auto Reboot and F reset boxes are checked
Click the PDA box and load the tar file
It will take a couple of minutes for the md5 checksum match
Then the file will auto load into the PDA box
Press Start
Will take about 8 minutes to complete
Your will see the upper left ODIN box turn Blue and Pass
Let the device boot
Wait several minutes
If stuck on Samsung Splash
Pull battery
Install battery
Don't power on device
Press Power and Vol up buttons
Enter Recovery
Scroll to Factory Reset/ option with Vol toggle
Press Power once Factory reset is highlighted
Let device Boot
Could take 10 minutes or so
Have Patience
If above successful
ODIN your Custom Recovery
Also Root if needed, but do the ODIN first tossee if it gets done.
Good luck
Click to expand...
Click to collapse
Okay, I was stuck on the recovery at first followed instructions.
ODIN to PASS...yeah!
Reboots...stuck on Tmobile 4G LTE
Pulled battery...got to recovery
Wipe/factory reset
says complete....reboot now
Stuck on Tmobile 4G LTE screen.
I am following instructions to the letter! I can only think that the file I using for ODIN is wrong.
Wife is getting very suspicious...uh oh!

[Q] [Nexus 7 - 2013, wifi, 16G]Got stuck at Google logo

Hi everybody,
I'm so angry with my Nexus 7 (wifi 2013) because I just made it mess up.
Let me tell you how stupid I was.
First, I tried to root but it failed.
Second, I used 'Back to Stock' with 'Nexus Root Toolkit v1.7.2'. Finally, I got stuck at Google logo
I tried some solutions on the internet but it still unchanged anything.
Could you show me how to fix it, please?
Thank you so much.
This is the images of error that I got (I'm sorry I cannot insert image because I'm a new member of this forum, could you go to the link below to see more details?)
s1019.photobucket.com/user/namserious/media/Error_Nexus7.png.html
Your /system is broken.
Try restoring factory defaults using this post:
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279
Restoring Successfully
sfhub said:
Your /system is broken.
Try restoring factory defaults using this post:
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279
Click to expand...
Click to collapse
Awesome, sfhub :good: :laugh:
Thank you so much. I have restored successfully.
This is my result
i1019.photobucket.com/albums/af319/namserious/WP_20131018_001.jpg
How did you do that?
namserious said:
Awesome, sfhub :good: :laugh:
Thank you so much. I have restored successfully.
This is my result
i1019.photobucket.com/albums/af319/namserious/WP_20131018_001.jpg
Click to expand...
Click to collapse
Hey namserious,
How did you get it working? Did you use the Mini guide given by sfhub? I'm having the same issues with my nexus 7 (2013). I only used for one day. Restarted on the second day and never got anything after the Google logo. Also, my phone wasn't rooted, so I didn't have developer options turned on and since I can't get into the system, I can't turn it on either. Will that make a difference?
Thanks.
nexussucks said:
Hey namserious,
How did you get it working? Did you use the Mini guide given by sfhub? I'm having the same issues with my nexus 7 (2013). I only used for one day. Restarted on the second day and never got anything after the Google logo. Also, my phone wasn't rooted, so I didn't have developer options turned on and since I can't get into the system, I can't turn it on either. Will that make a difference?
Thanks.
Click to expand...
Click to collapse
If you didn't root the device or do anything else with it, you should be able to get into Recovery Mode and do a factory reset.
https://support.google.com/nexus/answer/2668187?hl=en
Even recovery doesn't work
I'm not able to get into recovery mode. When I select recovery mode, the tablet starts and displays Google logo again and gets stuck there again.
nexussucks said:
I'm not able to get into recovery mode. When I select recovery mode, the tablet starts and displays Google logo again and gets stuck there again.
Click to expand...
Click to collapse
When you get into recovery you will see just the droid and the red triangle. At this screen you will need to push the power button then Vol Up and release. I had to do that about 3 times then I was able to get the menu items. From there I did a factory reset. After that I was good to go. Hope this helps!
Kind Regards,
Rb
RenderBroken said:
When you get into recovery you will see just the droid and the red triangle. At this screen you will need to push the power button then Vol Up and release. I had to do that about 3 times then I was able to get the menu items. From there I did a factory reset. After that I was good to go. Hope this helps!
Kind Regards,
Rb
Click to expand...
Click to collapse
Thanks Rb, But the thing is I don't get the droid and red triangle at all after I select recovery mode. I have tried everything but nothing happens. I still end up with dreadful Google logo. Suddenly I'm beginning to really hate it.
nexussucks said:
Thanks Rb, But the thing is I don't get the droid and red triangle at all after I select recovery mode. I have tried everything but nothing happens. I still end up with dreadful Google logo. Suddenly I'm beginning to really hate it.
Click to expand...
Click to collapse
You could try re-flashing the factory image.
http://forum.xda-developers.com/showthread.php?t=2487757
Latest factory image build is JSS15R
https://developers.google.com/android/nexus/images#razor
nexussucks said:
Thanks Rb, But the thing is I don't get the droid and red triangle at all after I select recovery mode. I have tried everything but nothing happens. I still end up with dreadful Google logo. Suddenly I'm beginning to really hate it.
Click to expand...
Click to collapse
Im sorry, I didnt read correctly. I had issues too restoring back to Stock since my setup was all changed. I had to use these steps. I am going to assume you know how to use fastboot and what it is.
DISCALAIMER! These steps will delete your user data!!!!
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader BOOTLOADER.img
> fastboot reboot-bootloader
> fastboot -w update IMAGE.zip
So after that I was able to get past the google logo but just stuck at the boot logo (Multi Colored X) I then had to get into recovery using the steps I stated above then did a factory reset.
Success
Rb, I just tried your instructions. YOU ARE A SAVIOUR :laugh:. After 2 days of continous troubleshooting, I had given up my hopes and was thinking of returning it. But suddenly after getting used to seeing the Google logo, I just noticed the android robot on the screen. And after a few seconds I saw the welcome screen... Viola.
Thanks man, I really appreciate your help. :good:
nexussucks said:
Rb, I just tried your instructions. YOU ARE A SAVIOUR :laugh:. After 2 days of continous troubleshooting, I had given up my hopes and was thinking of returning it. But suddenly after getting used to seeing the Google logo, I just noticed the android robot on the screen. And after a few seconds I saw the welcome screen... Viola.
Thanks man, I really appreciate your help. :good:
Click to expand...
Click to collapse
Glad to help! The best thing about Nexus devices are the different fail-safes. If the Rom is screwed up you can flash a new one from recovery. If recovery is screwed you flash a new one from the boot loader. If the boot loader is screwed you can flash another from recovery. Also the N7 2013 tablet is the best for the money. I user mine for work. I am a tech admin for a school district and have certain tools located on my desktop (Active Directory, Printer Manager, etc) and I have RDP installed on my N7. Now when I need to reset a password or whatever i can just RDP to my desktop. This tablet has made my life easier and hopefully yours will too now.
Kind Regards
Rb
Name change
RenderBroken said:
Glad to help! The best thing about Nexus devices are the different fail-safes. If the Rom is screwed up you can flash a new one from recovery. If recovery is screwed you flash a new one from the boot loader. If the boot loader is screwed you can flash another from recovery. Also the N7 2013 tablet is the best for the money. I user mine for work. I am a tech admin for a school district and have certain tools located on my desktop (Active Directory, Printer Manager, etc) and I have RDP installed on my N7. Now when I need to reset a password or whatever i can just RDP to my desktop. This tablet has made my life easier and hopefully yours will too now.
Kind Regards
Rb
Click to expand...
Click to collapse
This is my first experience with a Nexus device and I might have judged it in a wrong way. But I think the problem is not the device but the information regarding the latest Nexus devices. Hopefully there will be more workarounds of the new Nexus devices.
I guess I will have to change my username
nexussucks said:
This is my first experience with a Nexus device and I might have judged it in a wrong way. But I think the problem is not the device but the information regarding the latest Nexus devices. Hopefully there will be more workarounds of the new Nexus devices.
I guess I will have to change my username
Click to expand...
Click to collapse
This is the price we pay for the cutting edge. Also , at least for me, this is part of the fun. Now I have a much better understanding of Android than if I did being an avg. user. I was thinking the same about the name change. lol
RenderBroken said:
Glad to help! The best thing about Nexus devices are the different fail-safes. If the Rom is screwed up you can flash a new one from recovery. If recovery is screwed you flash a new one from the boot loader. If the boot loader is screwed you can flash another from recovery. Also the N7 2013 tablet is the best for the money. I user mine for work. I am a tech admin for a school district and have certain tools located on my desktop (Active Directory, Printer Manager, etc) and I have RDP installed on my N7. Now when I need to reset a password or whatever i can just RDP to my desktop. This tablet has made my life easier and hopefully yours will too now.
Kind Regards
Rb
Click to expand...
Click to collapse
Hey, know it's been a little bit but my nexus 7 says no OS in TWRP recovery. I tried flashing it back to stock but it doesn't work. The bootloader is locked and when I try to do anything manually it just hangs on stuff like erasing 'system'/cache etc... in fastboot. I have not been able to find anything to work. And when I try to fastboot oem unlock it gets stuck when i press volume up and power to accept unlocking it. I have tried different cables and another computer. maybe I should try a third computer.. Do you have any suggestions?
RenderBroken said:
Im sorry, I didnt read correctly. I had issues too restoring back to Stock since my setup was all changed. I had to use these steps. I am going to assume you know how to use fastboot and what it is.
DISCALAIMER! These steps will delete your user data!!!!
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader BOOTLOADER.img
> fastboot reboot-bootloader
> fastboot -w update IMAGE.zip
So after that I was able to get past the google logo but just stuck at the boot logo (Multi Colored X) I then had to get into recovery using the steps I stated above then did a factory reset.
Click to expand...
Click to collapse
I know this is an old thread, but I'm having this exact issue. I'm just stuck on the google screen. I can get into the bootloader just fine, but not the recovery. I followed these directions. Flashed the factory image and everything. But I still can't get past the google logo. I've followed every bit of advice I could find on this issue and I can't seem to get it working. Any help would be greatly appreciated!
*bump*
Does anyone know what's going on? I've tried everything I could find. Multiple times. From the suggestions listed here to the WUG kit to this http://forum.xda-developers.com/showthread.php?t=2381582
Nothing is working. I goes through the reflashing successfully. The command prompt says that everything is done. And then it just gets stuck at the Google screen again. I'm at my wits end and have no idea what to try next. I know that because I can get into the bootloader still, there has to be SOMETHING that will work. But I just don't know. Any ideas?
is there a android L Developers Preview flashable zip? thanks
Sent from my Nexus 7 using XDA Free mobile app
Anyone figure out what is causing this? I got a remanufactured 2nd Gen N7 16G yesterday. Updated to 4.4.4 over the air. Then unlocked the bootloader and rooted. Everything went fine. I installed Franco's latest kernel (r17) over stock and all was well. However, this morning, while using the device in the middle of GoW, it rebooted to the Google Screen and froze there. I could boot into the bootloader and have my comp recognize the device, so could ADB and Fastboot, however, I could not get into recovery. (I had installed TWRP 2.7.1.1 when I rooted). Trying to get into recovery would just freeze at the Google Screen.
So, I then tried both manually ADB'ing commands, as well as using Wug's Toolkit, and both methods seemed to complete successfully without error (I was using the latest Razor-Flo 4.4.4 files from Google's Dev Page so it is not an issue where I am using the Gen 1 files for Grouper or anything like that in error), however, neither method allowed me to boot into recovery, and left me at the same place. No matter what I did, I was stuck at that screen. I ended up calling Asus to RMA.
So, while it is not a current issue for me, I am interested to know if anyone has sorted what the root cause is, and whether it is an issue on the hardware side. I am not a complete noob to the N7 (I have 2 Groupers), and have been modding for a few years on Samsungs, and until this morning, have never had a soft brick I could not fix. This time, I gave up.
Same problem here, I have a Deb 32g, it went a little wonky and then rebooted. No amount of flashing and wiping and fastbooting has been able to recovery it. Gets stuck on Google Logo no matter what I do. Can't get recovery. Can't boot past Google. It will do fastboot without errors, but that's the only thing it will do.

Categories

Resources