Related
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 :/
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!
Hi, experts, help needed here.
My galaxy nexus (GSM version) was 4.0.4 perviously, then I OTA it to 4.1.1 and my phone's unlocked but never rooted. After OTA to 4.1.1, everything works fine for couples months. But about 1 week ago, when i tried to update an App then an odd thing happeded, right after i pressed the update bottle, screen fliker happened, then the phone stopped responds, after I pull the battey out then put it in, the phone just kept restarting over and over, only showed me an google logo with a un-locked icon...
I tried to get into the recovery mode and flash it with the Galaxy Nexus toolkit for whatever 4.0.4 or 4.1.1 version factory images, but everytime right after starts, then screen fliker occurs and then the toolkit just hung there. - and this even occured while i tried to wipe the phone.
I tried to use the odin tool as well, but still, everytime right after start flash, screen fliker occurs and odin hung there. And the worse thing is, after my last try with Odin, now my phone is showing a phone connects to a computer icons and a yellow triangle...
Is there still a hope? Thanks in advance.
My guess is Odin messed up your partitions. Can you still access the bootloader?
Petrovski80 said:
My guess is Odin messed up your partitions. Can you still access the bootloader?
Click to expand...
Click to collapse
no.. prevously i can access it, but now, only the yellow triangle and the phone and computer's icon shows up.
what can I do? :crying::crying:
not sure if it would be wise to suggest this, but you could try omapflash. I'm curious about it myself, I guess I'll start looking into that. if it has power like nvflash, not sure if that would help, since you have no backup of your "good" partition table. If you have the guts, of course. I would just return the device in to warranty. :victory:
edit: first google hit, title says "gt-i9250", the gsm version, don't know what you roll op.
edit2: read the whole thread. pretty useful insight right there.
bk201doesntexist said:
not sure if it would be wise to suggest this, but you could try omapflash. I'm curious about it myself, I guess I'll start looking into that. if it has power like nvflash, not sure if that would help, since you have no backup of your "good" partition table. If you have the guts, of course. I would just return the device in to warranty. :victory:
edit: first google hit, title says "gt-i9250", the gsm version, don't know what you roll op.
edit2: read the whole thread. pretty useful insight right there.
Click to expand...
Click to collapse
Yup, OMAP Flash should work.
EDIT: Actually, I just re-read the post above: Odin generally will work if you see the screen with the yellow triangle. If not, use OMAP Flash and then re-try Odin.
efrant said:
Yup, OMAP Flash should work.
EDIT: Actually, I just re-read the post above: Odin generally will work if you see the screen with the yellow triangle. If not, use OMAP Flash and then re-try Odin.
Click to expand...
Click to collapse
hmm, i forgot that existed.
seriously, i think that a lot of the issues i see in that thread are probably caused by windows.
maybe OP's device's xloader/uboot went down the drain?
edit: found another good post on this. bookmarked.
edit2: and some more right here.
edit3: Naturally, I deviate away from toolkits or batch scripts, so I'm trying to look at this like nvflash. One thing that I read is that Omapflash commands are issued on the target instead of the host like fastboot, so that is making my mind spin.
edit4: here. "OMAP4460_TUNA_8G_HS_PRO 444007 01 HS" - 8G probably means hardware revision, the one we see in bootloader. HS could be High Speed device. Nope, High Security.
edit5: how many edits this going to have... "OMAP4 Jellybean Release Notes" - omappedia
edit6: totally different idea. OP, do you have an OTG cable? Because we got something called "SYSBOOT"
edit7: this is the most interesting thing yet. i'm salivating right now.
efrant said:
Yup, OMAP Flash should work.
EDIT: Actually, I just re-read the post above: Odin generally will work if you see the screen with the yellow triangle. If not, use OMAP Flash and then re-try Odin.
Click to expand...
Click to collapse
First of all, thanks for all the replys, that really fresh my mind..
For your addition information, yes, odin does recongnize my my while I connects to the PS, I guess the SCREEN FLIKER may be caused by the wrong odin tar packages... For my current situation, which version of the system should I flash? 4.0.4 or 4.1.1 or it doesn't matter? Besides, do you know where can I download a full packages of Odin flash packages which includes the partion table as well? Sorry to ask this stupid questions here cause I'm a newbee here and this is my first Android phone...
I've never used odin but I bookmarked this post just in case (I haven't seen any 4.1.1 ODIN repacks)
ge_johnny said:
First of all, thanks for all the replys, that really fresh my mind..
For your addition information, yes, odin does recongnize my my while I connects to the PS, I guess the SCREEN FLIKER may be caused by the wrong odin tar packages... For my current situation, which version of the system should I flash? 4.0.4 or 4.1.1 or it doesn't matter? Besides, do you know where can I download a full packages of Odin flash packages which includes the partion table as well? Sorry to ask this stupid questions here cause I'm a newbee here and this is my first Android phone...
Click to expand...
Click to collapse
You shouldn't need a partition table. It will work without one. And you can use either a 4.0.4 or a 4.1.1 tar. Both should be available in the dev section. Make sure you pay close attention to which boxes need checks in them - never put a check in box related to repartitioning.
For future reference, I would always recommend to use fastboot before resorting to odin. Less chances of you getting into the situation that you are currently in.
Sent from my Galaxy Nexus using Tapatalk 2
here is the update of the problem.
OMAPlash doesn't solve my problem at all, I run the defaullt omap4460_tuna_hs_pro.txt script, it looks like flash something to my phone but the problem still there.
I tried redownload some odin packages into my phone, but still screen fliker happened...
Any other suggestions?
from what i've read, you now have the ability to enter the target, omapflash commands are issued on the target, not on the host.
you can feed the device the x-loader and uboot, which will then give you fastboot, restoring then a factory image.
someone that has actually done the whole procedure or has more info on this, please share.
Sent from my i9250
Help!!
bk201doesntexist said:
from what i've read, you now have the ability to enter the target, omapflash commands are issued on the target, not on the host.
you can feed the device the x-loader and uboot, which will then give you fastboot, restoring then a factory image.
someone that has actually done the whole procedure or has more info on this, please share.
Sent from my i9250
Click to expand...
Click to collapse
Hey Could you please maybe explain how to go around this? I currently have a yellow triangle brick on my Gnex but it does get detected via USB on Odin so if there is a fix I would like to know!
Thanks in advance!
If I were you, I would just use a jig to get it into download mode, then just reflash. I dont think it will take a flash with that boot error.
Check this thread here.
http://forum.xda-developers.com/showthread.php?t=1925468
Sent from my i9250
Don't think I explained myself very well
bk201doesntexist said:
Check this thread here.
http://forum.xda-developers.com/showthread.php?t=1925468
Sent from my i9250
Click to expand...
Click to collapse
Hey guys thanks a lot for your replies! I don't think I got the severity of the problem across well enough. See, the phone was in bootloop but everything was going fuzzy all the time (including recovery) and the recovery mode was corrupt it wouldn't let me clear cache! and while it was running the clearing process, all I could see was yellow lines of errors saying cache cannot be mounted. After loads of failed attempts of trying to flash Stock ICS and Jellybean (Yakju, without wallet) the phone decided it wanted to brick and so didn't turn on at all! I found a forum online (http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/) which gave me the OMAPFlash method with which I unbricked the phone and got it started a couple of times. I tried to then flash stock again via fastboot, it didn't work it simply couldn't send files to my phone although the phone was connected because it was detected under fastboot devices. After this, I went into download mode and tried to flash using Odin, however, this crashed and the phone crashed too which required me to pull the battery out. From then, all I get is > phone!Pc < and now the phone is detected via USB and via OMAP but the OMAP doesn't bring me back to fastboot its stuck on that yellow triangle screen!
Again, Thanks a lot for all your help! If I don't get this sorted in a few days I'll be sending it to Samsung!
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.
When I boot up my tablet, I get nonstop error messages telling me things have stopped working. I tried getting help from someone else on a different site, and this is what they told me to say: I flashed the GROUPER lollipop ROM onto a FLO. Someone please help me!!! It's a totally clean tablet. no files on it except android.
Go to Google's Nexus firmware page, download the appropriate firmware, follow the instructions: https://developers.google.com/android/nexus/images
Only thing I don't know is whether or not you'll have to repartition the internal flash.
I'm a dummy.
nhizzat said:
Go to Google's Nexus firmware page, download the appropriate firmware, follow the instructions:
Only thing I don't know is whether or not you'll have to repartition the internal flash.
Click to expand...
Click to collapse
i don't understand how to do all that though I'm not good with command prompts... and nexus root tool kit has done me no good. Could you dumb down the instructions for me?
Then it's time for you to learn. The page has step-by-step instructions. There isn't any way too dumb down the instructions.
You have to start somewhere. Now is a good time. If you had learned before, you wouldn't be in this predicament.
So sit down, take a couple deep breaths, then read the instructions a few times. Download the Android SDK and factory image, then get everything set up. Don't panic, it's not nearly as difficult as you're making it out to be. Stop psyching yourself out. Take it step by step. If you get stuck, leave the cmd prompt and post the issue you've run into here.
Might help if you type out the instructions here after you've read them over several times. I'm glad to help but you gotta take ownership of your tablet and put in some effort to learn and educate yourself.
Just try, I'm sure you'll understand it by the end of tonight or the end of the weekend. You don't have to be a master of fastboot and adb, I sure as hell am not. I never recommend the use of toolkits, especially by those with no understanding of fastboot and adb. Once you have a basic understanding of fastboot and adb, go ahead and use any toolkit you want because by then you'll know how to get yourself out of any jams using those 2 tools.
It is almost impossible to hard brick this device, even if you flash the wrong ROM on this device..
Download this utility and it will bring your Nexus back to life....
http://www.wugfresh.com/nrt/
Giving up
nhizzat said:
Then it's time for you to learn. The page has step-by-step instructions. There isn't any way too dumb down the instructions.
You have to start somewhere. Now is a good time. If you had learned before, you wouldn't be in this predicament.
So sit down, take a couple deep breaths, then read the instructions a few times. Download the Android SDK and factory image, then get everything set up. Don't panic, it's not nearly as difficult as you're making it out to be. Stop psyching yourself out. Take it step by step. If you get stuck, leave the cmd prompt and post the issue you've run into here.
Might help if you type out the instructions here after you've read them over several times. I'm glad to help but you gotta take ownership of your tablet and put in some effort to learn and educate yourself.
Just try, I'm sure you'll understand it by the end of tonight or the end of the weekend. You don't have to be a master of fastboot and adb, I sure as hell am not. I never recommend the use of toolkits, especially by those with no understanding of fastboot and adb. Once you have a basic understanding of fastboot and adb, go ahead and use any toolkit you want because by then you'll know how to get yourself out of any jams using those 2 tools.
Click to expand...
Click to collapse
I'm officially giving up. Nothing works. It boots into the OS and then pops up a bunch of error messages. I've tried lollipop, kitkat, cyanogenmod, locked bootloader, unlocked bootloader, and I'm done. GR! Thank you though, for your help.
Boucherwayne78 said:
I'm officially giving up. Nothing works. It boots into the OS and then pops up a bunch of error messages. I've tried lollipop, kitkat, cyanogenmod, locked bootloader, unlocked bootloader, and I'm done. GR! Thank you though, for your help.
Click to expand...
Click to collapse
So that means you will sell it to me for $20?
Boucherwayne78 said:
I'm officially giving up. Nothing works. It boots into the OS and then pops up a bunch of error messages. I've tried lollipop, kitkat, cyanogenmod, locked bootloader, unlocked bootloader, and I'm done. GR! Thank you though, for your help.
Click to expand...
Click to collapse
Nothing works? Just flash the factory image. Flashing Roms in recovery isn't going to help you. Before you give up, just use wugs toolkit to save it. If you give up without even trying the right procedure (fastboot flash factory image) then i recommend you not root again after you fix it. But wugfresh toolkit will fix it for you with a couple clicks.
I tried NRTK
madbat99 said:
Nothing works? Just flash the factory image. Flashing Roms in recovery isn't going to help you. Before you give up, just use wugs toolkit to save it. If you give up without even trying the right procedure (fastboot flash factory image) then i recommend you not root again after you fix it. But wugfresh toolkit will fix it for you with a couple clicks.
Click to expand...
Click to collapse
The toolkit doesn't work. I tried that 9 times, both downloading my own OS to flash, and letting the toolkit download it. Every time it either boot loops it or does the error message spam thing again. That's why I was trying to use SDK... And that didn't work either. And my drivers NEVER INSTALL RIGHT, so it's all just slowly killing me inside...
Make sure fastboots working first. Put the tablet in bootloader mode by shutting it off then holding power and volume down (or up I forget, you want the screen that says start at the top and has device info at the bottom left.)
Connect to computer then go into the platform-tools folder in the SDK folder, hold shift and right click over the window>open command prompt here.
Type fastboot devices and hit enter. Does it show a serial number or does it show nothing? (waiting for device or something like that) If nothing you should uninstall all drivers for the tablet in device manager and install the google usb driver from the sdk manager in the sdk you installed.
Once you see the serial number you're almost done. If your bootloader is locked type fastboot oem unlock
Now from the factory image copy the image-razor.zip, bootloader.img and flash-all.bat to the platform-tools folder.
Double click flash-all.bat
That's it.
I think that it will be beneficial for you to look into using virtual machines (VM's). It allows you to run different operating systems directly from your computer.
The second half to this equation is learning to use Linux (Ubuntu is my choice). Since Android is built from Linux, you don't need special drivers to recognize your devices.
Another option to run Ubuntu is to create a Virtual Hard Drive on your PC, and install Ubuntu onto it (YouTube it, and follow the directions carefully).
Lastly, you can always get a flash drive that is 8gb or greater (16gb or 32gb is recommended), and install Ubuntu onto it was well. It will move little slower than your PC, but your issues will be solved and manageable.
Why am I advocating for Ubuntu? Because it works. PM me if your are interested in learning more, but don't expect me to do all of the work. You need to educate yourself a bit to actually follow my instructions.
____________________________
Please remember to:
Check Q & A forums before asking!
Search forum for similar post before creating!
Hit "thanks" to everyone who may have helped you (it costs nothing)!
Read the OP!!!!
Boucherwayne78 said:
The toolkit doesn't work. I tried that 9 times, both downloading my own OS to flash, and letting the toolkit download it. Every time it either boot loops it or does the error message spam thing again. That's why I was trying to use SDK... And that didn't work either. And my drivers NEVER INSTALL RIGHT, so it's all just slowly killing me inside...
Click to expand...
Click to collapse
First off, let me explain that this device is almost impossible to destroy by flashing the wrong rom. Your over reacting due to inexperience, your Nexus is fine as long as you can boot into Fastboot. When the device is powered down, press the power button and the Volume down key for about 30 seconds, if you can boot into Fastboot, your device is just fine.. Nexus devices are extremely hard to hard brick.. RELAX and realize this is a good time to learn something new, this device is the perfect device to experiment with... You seem to not have the patients and you just need to relax watch a few youtube videos.. No one is going to do it for you.. About 5 years ago I was in the same place you are right now, and I took the time to figure how to fix what ever I did to mess it up.. Its not hard once you realize what your doing. The Toolkit is a swiss army knife of tools that can fix, repair and flash stock roms. Did you unlock the bootloader? Take a breather, give it some time and figure it out like we all did at one time or another, none of us here had our hands held during the learning process with Android devices..
Edit: I'm almost sure you did not unlock your device, to know for sure if your device is unlocked you would see a small padlock that appears to be in the unlocked position at the bottom of your screen while powering on.. If you power your Nexus on, and you DO NOT see a unlocked symbol at the bottom of your screen, you DID NOT unlock your device, thus meaning you have to unlock it to flash it properly.. There are dozens of people in this forum right now that would be more than happy to buy your device cheap and fix it themselves.. If they can do it, you can too..
^Yeah like my last post, those are perfectly fine instructions. If that don't work, stuck at "erasing user data" or something you're ****ed. Most likely.Try a different cord/usb 2.0/computer
Tried a few things. Got any other ideas?
Zaphodspeaks said:
First off, let me explain that this device is almost impossible to destroy by flashing the wrong rom. Your over reacting due to inexperience, your Nexus is fine as long as you can boot into Fastboot. When the device is powered down, press the power button and the Volume down key for about 30 seconds, if you can boot into Fastboot, your device is just fine.. Nexus devices are extremely hard to hard brick.. RELAX and realize this is a good time to learn something new, this device is the perfect device to experiment with... You seem to not have the patients and you just need to relax watch a few youtube videos.. No one is going to do it for you.. About 5 years ago I was in the same place you are right now, and I took the time to figure how to fix what ever I did to mess it up.. Its not hard once you realize what your doing. The Toolkit is a swiss army knife of tools that can fix, repair and flash stock roms. Did you unlock the bootloader? Take a breather, give it some time and figure it out like we all did at one time or another, none of us here had our hands held during the learning process with Android devices..
Edit: I'm almost sure you did not unlock your device, to know for sure if your device is unlocked you would see a small padlock that appears to be in the unlocked position at the bottom of your screen while powering on.. If you power your Nexus on, and you DO NOT see a unlocked symbol at the bottom of your screen, you DID NOT unlock your device, thus meaning you have to unlock it to flash it properly.. There are dozens of people in this forum right now that would be more than happy to buy your device cheap and fix it themselves.. If they can do it, you can too..
Click to expand...
Click to collapse
Thank you for your reply. Do you have any suggestions though for my situation? My bootloader was unlocked. I did try locking it then unlocking it several times though. I've tried two seperate stock ROMs, different usb cables, different usb ports, and it now tells me that fastboot is not working. even a link is greatly appreciated. I think it is a driver problem. My tablet does boot into the OS though. I can use the ui for about 10 seconds, then a notification pops up mid-screen: "unfortunately, the process android.process.acore has stopped." Please, even a link is greatly appreciated. I've tried just about everything to get these drivers working, and to get this tablet working. I will continue to research as well. Wish me luck!
Wug's tool has been invaluable to me in the past. I have gone from KitKat to Lollipop, back and forth, different ROMS, stuck boots, bad flashes. Like Zap says if you can get it to Bootloader then get Wug's tool to connect in fastboot, it will do the rest.
A couple times I have ran into problems where my computer has not seen my Nexus 5 because of the drivers, just google nexus usb drivers and install the latest ones.
azsgolf said:
Wug's tool has been invaluable to me in the past. I have gone from KitKat to Lollipop, back and forth, different ROMS, stuck boots, bad flashes. Like Zap says if you can get it to Bootloader then get Wug's tool to connect in fastboot, it will do the rest.
A couple times I have ran into problems where my computer has not seen my Nexus 5 because of the drivers, just google nexus usb drivers and install the latest ones.
Click to expand...
Click to collapse
Got any ideas on Fastboot.exe stopping working when the flash process begins? it fails sending bootloader and then fastboot.exe fails. It says on the screen when i close the error message it's booting into bootloader, but the tablet never restarts. it stays on bootloader(where i had it in the first place.) It should turn off the screen and go back into bootloader. Please, any feedback is appreciated.
Have you tried selecting the option of hardbrick on the tool?