Related
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,
I have a rooted Galaxy Nexus on Android 4.0.2 (GSM, not bound to carrier) and today I wanted to install the Franco kernel. I was on the road and had no idea how it would work (stupid, I know) but I figured I needed to auto-flash to make it work. It rebooted and got stuck at the Google logo after a very long time. I rebooted into recovery mode, but all I got was a red triangle.
When I got home I got into recovery mode and hooked it up to my pc (W7). I then tried to restore factory rom from google. All I could find was the yakju-imm76i 4.0.4 tgz file and it seemed to be working, however it still won't boot up (stuck at Google logo).
I am very new to Android and I have no idea what to do next. Can anyone help me?
did you installed the yakju-imm76i 4.0.4 or not?
if no please install it
if yes, did you installed the system file?
I tried installing it using the Galaxy Nexus Toolkit, but I am still unable to get past the Google logo. So I don't know if it succesfully installed or not. And I don't know anything about the system file you are talking about :/ Was I supposed to?
wouwousoft said:
I tried installing it using the Galaxy Nexus Toolkit, but I am still unable to get past the Google logo. So I don't know if it succesfully installed or not. And I don't know anything about the system file you are talking about :/ Was I supposed to?
Click to expand...
Click to collapse
I dont know about toolkits, search around by posts from efrant, me, and others i dont remember right now on how to return to stock through fastboot, erasing first, flashing afterwards.
Edit:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase recovery
this will wipe /data/media as well; if you don't want it to, leave 'fastboot erase userdata' out
Sent from my i9250
i made a huge tutorial about this subject, too bad it's in arabic only
if you wan't you can visit my profile here: http://forum.xda-developers.com/member.php?u=4598933
and find my contact info then add me
and i'll tell you every thing step by step until you boot it
ahmad.afef said:
i made a huge tutorial about this subject, too bad it's in arabic only
if you wan't you can visit my profile here: http://forum.xda-developers.com/member.php?u=4598933
and find my contact info then add me
and i'll tell you every thing step by step until you boot it
Click to expand...
Click to collapse
Thanks dude, that would be awesome! So I just add you on MSN then?
yah sure just all me
ahmad.afef said:
i made a huge tutorial about this subject, too bad it's in arabic only
if you wan't you can visit my profile here: http://forum.xda-developers.com/member.php?u=4598933
and find my contact info then add me
and i'll tell you every thing step by step until you boot it
Click to expand...
Click to collapse
Dude, thank you very much for taking the time to help me! I really appreciate it!
u are very welcome
Hello Members
I need a Official recovery.img dump for this ICS version
ACER_AV041_A100_0.002.00_ww_GEN1 link >>http://vache-android.com/v1/download.php?fileID=116
my recovery does not install update.zip patches and power key does not select any opition
http://youtu.be/CWFlA1W08wE
this is my bootloader version
Bootloader v0.03.11-ICS: Starting Fastboot USB download protocol
help me please
You Can make a backup this IMG with "Acer recovery tool" downloaded from the google play store
thanks
Ill attach the stock recovery for one of the ICS roms that vache posted, but I can't remember the exact build #. I know it's not the leak version, and if it helps I also used it to flash back to stock after some funny business.
I just noticed something, you are aware that image you linked to is a A101 image, right?
masr1979 said:
Ill attach the stock recovery for one of the ICS roms that vache posted, but I can't remember the exact build #. I know it's not the leak version, and if it helps I also used it to flash back to stock after some funny business.
Click to expand...
Click to collapse
thanks now works
u save my tab
rollidark said:
thanks now works
u save my tab
Click to expand...
Click to collapse
I'm glad it worked out for you, but if this fixed your device that you made a previous bricked thread about, could you please to back, and post an update to that thread discribing what you did, and how you did it, to get the device back up again? It'll definatly help anyone else with this same issue.
You're welcomed, we are here to help each other after all. You should follow pio's advice and describe what you did so others can benefit from your experience. We have to make such info as readily available as possible.
Having the same issue described
I have a locked bootloader tried many different A100 update.zip files. Please tell me how you fixed it with the recovery image I have the locked bootloader v 0.03 up.
citricube said:
I have a locked bootloader tried many different A100 update.zip files. Please tell me how you fixed it with the recovery image I have the locked bootloader v 0.03 up.
Click to expand...
Click to collapse
He had a brick not a locked bootloader, you can't flash a bootloader directly if its locked with fast boot.
Tapatalked from my Galaxy S II.
Awesome
Looks like my tablet is going back to Acer Repair for the second time in about a month. :cyclops:
citricube said:
Looks like my tablet is going back to Acer Repair for the second time in about a month. :cyclops:
Click to expand...
Click to collapse
Wow that's a pretty bad run, what's wrong with either one?
Yes I know holy threadjack Batman
Tapatalked from my Galaxy S II.
masr1979 said:
Ill attach the stock recovery for one of the ICS roms that vache posted, but I can't remember the exact build #. I know it's not the leak version, and if it helps I also used it to flash back to stock after some funny business.
Click to expand...
Click to collapse
Hi, I have the same problem as rollidark. What do you do with this recovery image. It seems rollidark used it to fix his issue.
thanks
liltyke said:
Hi, I have the same problem as rollidark. What do you do with this recovery image. It seems rollidark used it to fix his issue.
thanks
Click to expand...
Click to collapse
Put an stock rom update on the root of your external sdcard (vache & zeronull have released some), rename it update.zip. I'd don't recommend recommend relocking your bootloader unless you're absolutely sure what you are doing, so that means that if the rom you downloaded has a bootloader.blob you need to delete it, or look for one that doesn't have it (I think vache's don't have it)
Now reboot into fastboot
adb reboot bootloader
Click to expand...
Click to collapse
once in fastboot
fastboot erase recovery
Click to expand...
Click to collapse
then
fastboot flash recovery "recovery.img file location"
Click to expand...
Click to collapse
That should give you stock recovery, after that I usually hold down the volume button closest to the lock switch and run
fastboot reboot
Click to expand...
Click to collapse
After you see the green android with the progress bar in the bottom your rom should be flashing, and hopefully once finished you'll be ready to re-root, and reflash your rom... if you were careful and had a nandroid-backup you could even restore your /data (I don't usually restore my /system or other partitions).
Godspeed in your flashing endeavors my friend.
masr1979 said:
Put an stock rom update on the root of your external sdcard (vache & zeronull have released some), rename it update.zip. I'd don't recommend recommend relocking your bootloader unless you're absolutely sure what you are doing, so that means that if the rom you downloaded has a bootloader.blob you need to delete it, or look for one that doesn't have it (I think vache's don't have it)
Now reboot into fastboot
once in fastboot
then
That should give you stock recovery, after that I usually hold down the volume button closest to the lock switch and run
After you see the green android with the progress bar in the bottom your rom should be flashing, and hopefully once finished you'll be ready to re-root, and reflash your rom... if you were careful and had a nandroid-backup you could even restore your /data (I don't usually restore my /system or other partitions).
Godspeed in your flashing endeavors my friend.
Click to expand...
Click to collapse
Nicely done, masr1979!:good:
masr1979 said:
Put an stock rom update on the root of your external sdcard (vache & zeronull have released some), rename it update.zip. I'd don't recommend recommend relocking your bootloader unless you're absolutely sure what you are doing, so that means that if the rom you downloaded has a bootloader.blob you need to delete it, or look for one that doesn't have it (I think vache's don't have it)
Now reboot into fastboot
once in fastboot
then
That should give you stock recovery, after that I usually hold down the volume button closest to the lock switch and run
After you see the green android with the progress bar in the bottom your rom should be flashing, and hopefully once finished you'll be ready to re-root, and reflash your rom... if you were careful and had a nandroid-backup you could even restore your /data (I don't usually restore my /system or other partitions).
Godspeed in your flashing endeavors my friend.
Click to expand...
Click to collapse
thank you very much for the detailed explanation masr1979. I'll give it a shot when I get home from work.
Basically I got the rear camera replaced, it was working great. About a couple weeks later It's running sluggishly because I was running too many apps at once. So I decided to press the reset button while It was lagging out, next thing I know It's stuck at the silver android logo forever. I tried using some update.zip's but that just made the problem worse.
Well it seems my knowledge level was a few steps back from where it needed to be to fully understand the instructions as posted, so the last 24 hours have been a whole lot of 'old dog learning new tricks'. I have adb and fastboot installed now via one of the threads found through googling. When I enter 'adb reboot bootloader' everything seems to go fine, but when I enter 'fastboot erase recovery' I get 'ersaing 'recovery' ... FAILED (remote: (00000002)) ANy tips from you pros?? I've been beating my head against the wall for a while and neither my head or the wall are looking too good right now Thanks for any help anyone may offer.
liltyke said:
Well it seems my knowledge level was a few steps back from where it needed to be to fully understand the instructions as posted, so the last 24 hours have been a whole lot of 'old dog learning new tricks'. I have adb and fastboot installed now via one of the threads found through googling. When I enter 'adb reboot bootloader' everything seems to go fine, but when I enter 'fastboot erase recovery' I get 'ersaing 'recovery' ... FAILED (remote: (00000002)) ANy tips from you pros?? I've been beating my head against the wall for a while and neither my head or the wall are looking too good right now Thanks for any help anyone may offer.
Click to expand...
Click to collapse
Need a little more information first.
What android version are you on now? What boot loader version does it show upper left on boot? What all have you done to this point?
Tapatalked from my Galaxy S II.
pio_masaki said:
Need a little more information first.
What android version are you on now? What boot loader version does it show upper left on boot? What all have you done to this point?
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Thanks for jumping in here pio_masaki. It's very much appreciated.
Sorry for the lack of details, I realize that I should have given that info from in my first post.
Android version is 4.0.3 ,I flashed it with the first ICS leak that showed up here on XDA.
Bootloader version is v0-03.11-ICS
The A100 is not rooted.
After the official ICS update was being streamed I realized that I wasn't getting it. Figured it was because I had already flashed the early leak. I saw here on XDA a few threads where people were trying to get back to HC because they were having the same problem. I followed steps and advice listed in those other threads but nothing was working for me. I always got the dead android logo any time I tried to recover using an 'update.zip' on my external sd card. When I get the dead android logo and press the home button I do get the recovery menu button soon noticed that even though I could scroll through the menu I could not select any of the options. I saw this thread and it seemed to be very similar to my situation.
thanks again for your time.
liltyke said:
Thanks for jumping in here pio_masaki. It's very much appreciated.
Sorry for the lack of details, I realize that I should have given that info from in my first post.
Android version is 4.0.3 ,I flashed it with the first ICS leak that showed up here on XDA.
Bootloader version is v0-03.11-ICS
The A100 is not rooted.
After the official ICS update was being streamed I realized that I wasn't getting it. Figured it was because I had already flashed the early leak. I saw here on XDA a few threads where people were trying to get back to HC because they were having the same problem. I followed steps and advice listed in those other threads but nothing was working for me. I always got the dead android logo any time I tried to recover using an 'update.zip' on my external sd card. When I get the dead android logo and press the home button I do get the recovery menu button soon noticed that even though I could scroll through the menu I could not select any of the options. I saw this thread and it seemed to be very similar to my situation.
thanks again for your time.
Click to expand...
Click to collapse
So...you flashed the bootloader to get back to HC and now it won't use update.zip? What about booting into android, does that still work? Or fast boot? Or uhm...I seem to recall having to do a hard reset to get the downgrade to work, have you done this too? I never downgraded just seemed pointless when I was already on ics so I'm not experienced with it, just recall seeing the boot loader needing a hard reset to work.
Tapatalked from my Galaxy S II.
No, I never flashed the bootloader, not unless that happens while trying to run an update.zip. adb and fastboot seem to be working. Based on the earlier instructions 'adb reboot bootloader' does restart the A100 and gives me the bootloader message at the top left of the screen. When I run the ' fastboot erase recovery' command I get the FAILED message in the command prompt window and also get a message in red text on the A100 saying 'Fastboot: not support the command in lockmode, failed to process command erase: recovery error (0x2)'. When I run the 'fastboot reboot' command the A100 does restart. So all that leads to believe that the communication from my computer to the A100 is ok.
Booting into Android. The A100 starts and works fine if that is what you are referring too. As far as the hard reset, if that's the process of holding down the volume button while powering up and flipping the lock switch back and forth to reset the unit, then yes I have done that and it does work. My whole goal here is to get the unit to running ICS legitimately and get updates from ACER. I don't care what I have to do, it's just a couple of the other threads mentioned the need to go back to HC to get the official ICS update. So that's why I tried that. But the last time a update.zip worked was when I flashed the leaked ICS. I have got the dead android logo every time since.
Sorry if some of this info is redundant from my earlier post, I just wanted to get it all in the same place.
Thanks again for your help.
I don't normally ask for advice as generally I don't run into issues rooting my phones or I solve them myself but I'm a little stuck here.
My cousin tried to root his one x using the method on onexroot.
He got to stage 41 but said he could not enter storage mode due to a sense update that apparently blocks him. This left him stuck rooting but he did unlock the bootloader.
At this point he thought it a good idea to try another method on theunlockr.
This time he got to step 7a, clicks the batch file and a cmd window pops up and gets to a point and freezing. Forgive my memory but I believe it said something about daemon. The process was left for 30 minutes with no progress on several occasions.
Afterwards the phone now does not boot past the HTC logo but will go into bootloader. I can't tell 100% what's gone on as I wasn't there but I take it there was an issue flashing his boot.img file.
The question is what is the best way of proceeding unbricking his phone. I have looked up several ways but all seem to reference a point where cwm has already been installed. Is there a way to sort this out using fastboot alone? If so does it matter where I download the fast boot files from and what commands shall I use.
Apologies for the length. I'm not into rooting htc's much and not really sure what I should be doing with this. Give me a nexus to root any day lol. Thanks for your help.
Sent from my Nexus 4
Daemon server is out of date **Killing** ???
OK so what's the up to date alternative?
Sent from my Nexus 4
delete HTCSync (manager) completely
download this driver and install it
https://www.dropbox.com/s/rq4yxhn2q50l4v0/HTCDriver3.0.0.007.exe
then you open a command window inside the fastboot folder and you put the phone in the bootloader.....then type
fastboot devices
serial pops up ? yes....continue with what you wanted to do.....
Make sure you use the original HTC USB cable and USB 2.0 ports. No USB 3.0 ports.....fastboot has trouble with that....
Maybe this helps !
Before trying the above, ive made a little bit of headway but im still bootlooping.
I downloaded CM10 nightly ROM and One X all in one toolkit. I used the toolkit to flash the kernel with the boot.img from the CM10 ROM then push CWM to the phone which i can now get into. I also installed the rom fine etc but rebooting the phone stil results in bootloop
Flash this boot.img and try again
http://db.tt/uDdWaAtH
I should also add that i cannot use those drivers you linked to (i have already tried) as i run windows 8 64 bit
Ah oke .....but flashing a kernel works now or do you need anything else ?
Mr Hofs said:
Flash this boot.img and try again
http://db.tt/uDdWaAtH
Click to expand...
Click to collapse
Thanks! its working thank god. How do i buy you a beer?
Check my signature
I was going to link you here
http://forum.xda-developers.com/showthread.php?t=1775870
Mr Hofs said:
Check my signature
I was going to link you here
http://forum.xda-developers.com/showthread.php?t=1775870
Click to expand...
Click to collapse
For some reason paypal isnt letting me log in like that, ill send it manually in a second.
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.