I have a galaxy nexus that is stuck on the google screen and boots to download mode and fastboot but not recovery. I have tried reverting back to stock with fastboot and odin but no luck. I am offering 30 dollars via paypal or anything for whoever can fix it.
Suggestions: (You aren't bricked)
1.Uninstall Redownload Drivers for computer
2. Try a different USB port on the computer
3. Try a different USB cord
4. Restart Computer
5. After doing all 4 above boot into download mode. make sure you have a good tar file and use odin to go back to stock
No reward needed if you fix it with above
A thanks would suffice
davidrules7778 said:
Suggestions: (You aren't bricked)
1.Uninstall Redownload Drivers for computer
2. Try a different USB port on the computer
3. Try a different USB cord
4. Restart Computer
5. After doing all 4 above boot into download mode. make sure you have a good tar file and use odin to go back to stock
No reward needed if you fix it with above
A thanks would suffice
Click to expand...
Click to collapse
I have tried that and nothing
samiaziz said:
I have a galaxy nexus that is stuck on the google screen and boots to download mode and fastboot but not recovery. I have tried reverting back to stock with fastboot and odin but no luck. I am offering 30 dollars via paypal or anything for whoever can fix it.
Click to expand...
Click to collapse
If it boots to fastboot have you tried flashing a new recovery??
can you give me a link for the drivers please i would like to try again
samiaziz said:
can you give me a link for the drivers please i would like to try again
Click to expand...
Click to collapse
Here is the link to odin thread: http://forum.xda-developers.com/showthread.php?t=1620036
Give me a sec for a drivers link:
EDIT: Drivers are on step 2 of odin thread
---------- Post added at 04:08 PM ---------- Previous post was at 03:55 PM ----------
samiaziz said:
I have a galaxy nexus that is stuck on the google screen and boots to download mode and fastboot but not recovery. I have tried reverting back to stock with fastboot and odin but no luck. I am offering 30 dollars via paypal or anything for whoever can fix it.
Click to expand...
Click to collapse
oh wait, what version of galaxy nexus do u have? I linked to sprint galaxy nexus thread..
Sorry
If you can get into bootloader and download mode, you certainly aren't bricked. If you're in bootloader mode, use fastboot and the factory restore images to get your phone back to stock. Then restart and see if your phone works. From there, go back to the rom/kernel/recovery you were using before.
nodstuff said:
If it boots to fastboot have you tried flashing a new recovery??
Click to expand...
Click to collapse
Ive tried flashing a recovery however it is not rooted bot the bootloader is unlocked
imnuts said:
If you can get into bootloader and download mode, you certainly aren't bricked. If you're in bootloader mode, use fastboot and the factory restore images to get your phone back to stock. Then restart and see if your phone works. From there, go back to the rom/kernel/recovery you were using before.
Click to expand...
Click to collapse
When ever its done flashing it goes back to the google screen and just stays like that
just research how to flash stock rom....if you can fastboot then ur phone is not bricked.....
Sent from my HTC One X using XDA
samiaziz said:
When ever its done flashing it goes back to the google screen and just stays like that
Click to expand...
Click to collapse
What version of the Nexus do you have? VZW, Sprint, or GSM?
imnuts said:
What version of the Nexus do you have? VZW, Sprint, or GSM?
Click to expand...
Click to collapse
GSM
Are you flashing the full package?
Have you tried using heimdall?
Sent from my SAMSUNG-SGH-I997 using XDA unbricked my phone 3 times
imnuts said:
Are you flashing the full package?
Click to expand...
Click to collapse
Cold you give me the link for an entire package also i have noticed an error on the bottom of my fastboot screen and it says "Fastboot Command Read Error -2147483647"
No need to use heimdall or whatever, just try flash a recovery through fastboot and tell us if its successful, if it isn't what does it say etc.
If you can boot into the bootloader then it should be straight forward to fix your phone.
samiaziz said:
Cold you give me the link for an entire package also i have noticed an error on the bottom of my fastboot screen and it says "Fastboot Command Read Error -2147483647"
Click to expand...
Click to collapse
You can get the full package from here
imnuts said:
Are you flashing the full package?
Click to expand...
Click to collapse
nodstuff said:
No need to use heimdall or whatever, just try flash a recovery through fastboot and tell us if its successful, if it isn't what does it say etc.
If you can boot into the bootloader then it should be straight forward to fix your phone.
Click to expand...
Click to collapse
Which recovery im not rooted just stock?
imnuts said:
You can get the full package from here
Click to expand...
Click to collapse
nothing
samiaziz said:
Which recovery im not rooted just stock?
Click to expand...
Click to collapse
Are you completely stock?
Clockwork mod recovery.
Maybe if you get that to boot you can flash a rom from there.
Otherwise try flash the factory images through fastboot.
---------- Post added at 12:46 AM ---------- Previous post was at 12:41 AM ----------
samiaziz said:
nothing
Click to expand...
Click to collapse
Did you download the factory image for your variant and flash it?
It should work if you did.
All the details are there on the download page.
Related
Hello.
I have Galaxy S3 model t-999(T-Mobile) and after installing ROM(CM 10.1 4.2.2) and G-apps I got the problem with "Setup Wizard has stopped".
apparently the version of th G-apps was for 4.2.1 but beacuse my PC doesn't recognize my Galaxy S3 I could not switch the G-apps to the G-apps with the right version( I have tried a lot of times to fix it with some methods but still doesn't work ).
After that, I somehow got into recovery mode, wiped factory data, partition cache and dalvik cache.
That also didn't work, and the problem with "Setup Wizard" continued..
I was desperate and probably formatted all the system data and a few more things there(Man, i am stupid..).
So now, recovery mode won't work, the device won't be activated at all and the PC as I said before, won't recognize it.
I am pretty sure that after i deleted everything(probably) there is no solution.
So if there is a any chance to fix it(even if the chances of success are slim) I will be glad to hear it .
Thank you very much.
Fool132 said:
Hello.
I have Galaxy S3 model t-999(T-Mobile) and after installing ROM(CM 10.1 4.2.2) and G-apps I got the problem with "Setup Wizard has stopped".
apparently the version of th G-apps was for 4.2.1 but beacuse my PC doesn't recognize my Galaxy S3 I could not switch the G-apps to the G-apps with the right version( I have tried a lot of times to fix it with some methods but still doesn't work ).
After that, I somehow got into recovery mode, wiped factory data, partition cache and dalvik cache.
That also didn't work, and the problem with "Setup Wizard" continued..
I was desperate and probably formatted all the system data and a few more things there(Man, i am stupid..).
So now, recovery mode won't work, the device won't be activated at all and the PC as I said before, won't recognize it.
I am pretty sure that after i deleted everything(probably) there is no solution.
So if there is a any chance to fix it(even if the chances of success are slim) I will be glad to hear it .
Thank you very much.
Click to expand...
Click to collapse
Can you get into download mode?
Fool132 said:
Hello.
I have Galaxy S3 model t-999(T-Mobile) and after installing ROM(CM 10.1 4.2.2) and G-apps I got the problem with "Setup Wizard has stopped".
apparently the version of th G-apps was for 4.2.1 but beacuse my PC doesn't recognize my Galaxy S3 I could not switch the G-apps to the G-apps with the right version( I have tried a lot of times to fix it with some methods but still doesn't work ).
After that, I somehow got into recovery mode, wiped factory data, partition cache and dalvik cache.
That also didn't work, and the problem with "Setup Wizard" continued..
I was desperate and probably formatted all the system data and a few more things there(Man, i am stupid..).
So now, recovery mode won't work, the device won't be activated at all and the PC as I said before, won't recognize it.
I am pretty sure that after i deleted everything(probably) there is no solution.
So if there is a any chance to fix it(even if the chances of success are slim) I will be glad to hear it .
Thank you very much.
Click to expand...
Click to collapse
Well, theres two ways this can work for you. You need Odin and a copy of the stock firmware. Instead of going directly into recovery you need to get to download mode. Vol-down and home key along with power button. Once booted, press the vol-up key to get to download mode. This should work regardless if you have a custom cwm or twrp recovery or not. Once you get that far, you need to download the Sammy usb drivers for your computer to recognize the phone. Open Odin and flash the stock recovery, make sure you have the f.reset and reboot checked, flash the stock recovery through pda in Odin. Wait about 8 mins, and let it do its thing, the reroot after your recovery is redone, flash your Rom you want, wipe data, dalvick, cache. Flash your gapps (correct version) then reboot= win.
Sent from my SGH-T999
Don_Perrignon said:
Can you get into download mode?
Click to expand...
Click to collapse
No.
jay4mont78 said:
Well, theres two ways this can work for you. You need Odin and a copy of the stock firmware. Instead of going directly into recovery you need to get to download mode. Vol-down and home key along with power button. Once booted, press the vol-up key to get to download mode. This should work regardless if you have a custom cwm or twrp recovery or not. Once you get that far, you need to download the Sammy usb drivers for your computer to recognize the phone. Open Odin and flash the stock recovery, make sure you have the f.reset and reboot checked, flash the stock recovery through pda in Odin. Wait about 8 mins, and let it do its thing, the reroot after your recovery is redone, flash your Rom you want, wipe data, dalvick, cache. Flash your gapps (correct version) then reboot= win.
Sent from my SGH-T999
Click to expand...
Click to collapse
I can't even get to download mode...
Fool132 said:
No.
I can't even get to download mode...
Click to expand...
Click to collapse
Sounds to me you flashed the wrong thing then, you could have a brick, did you wipe the system partition? Can you get into a recovery?
Sent from my SGH-T999
---------- Post added at 03:16 PM ---------- Previous post was at 03:09 PM ----------
Last resort, you may have to send it out to get a jtag dine to it, and have it put back to stock. You will have to look it up.
Sent from my SGH-T999
jay4mont78 said:
Sounds to me you flashed the wrong thing then, you could have a brick, did you wipe the system partition? Can you get into a recovery?
Sent from my SGH-T999
---------- Post added at 03:16 PM ---------- Previous post was at 03:09 PM ----------
Last resort, you may have to send it out to get a jtag dine to it, and have it put back to stock. You will have to look it up.
Sent from my SGH-T999
Click to expand...
Click to collapse
I did wipe the system partition, I can't get into recovery mode.
what is jtag dine?
Your phone got bricked if it can't boot to download mode.
You can send your phone for repair if you want.
This thread can help.
http://forum.xda-developers.com/showthread.php?t=2271708
Sent from my SGH-T999 using xda app-developers app
Just to mention it, if you are referring to the setup wizard that appears when you first boot a new Rom.. All that basically does is setup your Google account. Other then that it's Pretty much useless. Once it force closes, just go into settings and mmanually add it. Unless I'm missing something.
Sent from my SGH-T999 using Tapatalk 2
If you can't get into download mode and it is bricked, you can get it repaired by the guys at mobiletechvideos.com. I had to use their services when I flashed an international ROM onto my T-999. You can get a JIG from them too. Got my phone back in less than a week fully recovered to stock.
IXChicharitoXI said:
Your phone got bricked if it can't boot to download mode.
You can send your phone for repair if you want.
This thread can help.
http://forum.xda-developers.com/showthread.php?t=2271708
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Ok, thanks.
tp2215 said:
Just to mention it, if you are referring to the setup wizard that appears when you first boot a new Rom.. All that basically does is setup your Google account. Other then that it's Pretty much useless. Once it force closes, just go into settings and mmanually add it. Unless I'm missing something.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I couldn't go to the settings, but that doesn't matter anymore..
Thanks anyway.
radar9 said:
If you can't get into download mode and it is bricked, you can get it repaired by the guys at mobiletechvideos.com. I had to use their services when I flashed an international ROM onto my T-999. You can get a JIG from them too. Got my phone back in less than a week fully recovered to stock.
Click to expand...
Click to collapse
Ok thanks.
More answers?
Unfortunately no. If you can't get download mode or recovery you will need to send it in for repair as suggested.
Does anything happen when you try to turn it on?
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Unfortunately no. If you can't get download mode or recovery you will need to send it in for repair as suggested.
Does anything happen when you try to turn it on?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
It shows the image of Samsung Galaxy S III with "CyanogenMod" android(I have installed this ROM before all that has happened) and when i try to turn it off it just reboot.
Thanks, More answers?
re: download mode
Fool132 said:
It shows the image of Samsung Galaxy S III with "CyanogenMod" android(I have installed this ROM before all that has happened) and when i try to turn it off it just reboot.
Thanks, More answers?
Click to expand...
Click to collapse
If you can see the Cyanogen Android then your phone is NOT bricked, you just need to get it into download mode.
Remove the battery for a few seconds and replace it, then press the HOME+VOLUME DOWN+POWER BUTTONS all
at the same time for a few seconds and your phone should go into the download mode screen.
In download mode you can Odin flash either the stock T999 Samsung Jellybean 4.1.2 firmware (rom).
OR you can Odin flash the stock-rooted T999 Samsung Jellybean 4.1.2 firmware (rom).
Misterjunky said:
If you can see the Cyanogen Android then your phone is NOT bricked, you just need to get it into download mode.
Remove the battery for a few seconds and replace it, then press the HOME+VOLUME DOWN+POWER BUTTONS all
at the same time for a few seconds and your phone should go into the download mode screen.
In download mode you can Odin flash either the stock T999 Samsung Jellybean 4.1.2 firmware (rom).
OR you can Odin flash the stock-rooted T999 Samsung Jellybean 4.1.2 firmware (rom).
Click to expand...
Click to collapse
i got into download mode(YES! thanks!), but now i have the problem with the usb (my PC won't recognize it).
i have tried a lot of things but still no solution (reg edit,device manager,disk managment).
Does somebody have a way that worked for him?
Uninstall kies and/or sammys usb drivers. Download the latest version of tge drivrrs only (check my sig).
Reboot the phone and computer and try again.
Also, try every usb port on your PC. Youd be surprised how often only one of tge ports works for this.
Sent from my SGH-T999 using xda premium
hello xda!
my s3 suddenly restarted itself and is now stuck in bootloop. i'm able to get into download mode but recovery mode. i've tried to flash cwm/twrp but to no avail. i'm out of ideas. can someone please tell me what's the problem?
thanks in advance!
lolduck said:
hello xda!
my s3 suddenly restarted itself and is now stuck in bootloop. i'm able to get into download mode but recovery mode. i've tried to flash cwm/twrp but to no avail. i'm out of ideas. can someone please tell me what's the problem?
thanks in advance!
Click to expand...
Click to collapse
If you can get into recovery you can wipe/factory reset and that should get you past boot loop. your other option is to flash stock via Odin.
BCSC said:
If you can get into recovery you can wipe/factory reset and that should get you past boot loop. your other option is to flash stock via Odin.
Click to expand...
Click to collapse
that's exactly the problem; i can't get into recovery mode to do anything.
lolduck said:
that's exactly the problem; i can't get into recovery mode to do anything.
Click to expand...
Click to collapse
You can enter download mode and reflash stock image with Odin. If you were running the stock rom you may not lose your data. Let me know if you don't know how to do this and I will direct you. It seems that something has become corrupted, but Odin will fix that
BCSC said:
You can enter download mode and reflash stock image with Odin. If you were running the stock rom you may not lose your data. Let me know if you don't know how to do this and I will direct you. It seems that something has become corrupted, but Odin will fix that
Click to expand...
Click to collapse
i've tried doing that but the logo still comes up after i flash with odin
lolduck said:
i've tried doing that but the logo still comes up after i flash with odin
Click to expand...
Click to collapse
After flashing Odin you should have access to the 3e recovery. Unless something is wrong with your hardware (Volume broken?), I can not see why you would not be able to enter recovery.
You can also try this tool to boot a custom kernel with recovery attached. Here is a forum with a similar problem. http://forum.xda-developers.com/showthread.php?t=2011636&highlight=i9300
Here is the tool: http://forum.xda-developers.com/showthread.php?t=1746665
All of this is done through download mode.
BCSC said:
You can also try this tool to boot a custom kernel with recovery attached. Here is a forum with a similar problem. http://forum.xda-developers.com/showthread.php?t=2011636&highlight=i9300
Here is the tool: http://forum.xda-developers.com/showthread.php?t=1746665
All of this is done through download mode.
Click to expand...
Click to collapse
it doesn't allow me to do anything in the toolkit. it asks for adb mode and usb debugging.
it also says recovery booting when i attempt to boot into recovery mode but it goes directly to the s3 logo
lolduck said:
it also says recovery booting when i attempt to boot into recovery mode but it goes directly to the s3 logo
Click to expand...
Click to collapse
You can download an Odin flashable recovery from here. http://techerrata.com/browse/twrp2/d2att. you will want the .tar file.
Beyond this i'm running out of ideas. Not too sure if this will work if you have gone stock with Odin as it may have taken root from you. Worth a try though.
Maybe an emergency recovery through Kies... http://forum.xda-developers.com/showthread.php?t=1984717
Beyond that try Odin again and re download the stock Rom from a different source. You may have gotten a bad download. I have read of it happening. Maybe even an older firmware or Canadian one (i'm assuming you're ATT): http://samsung-updates.com/device/?id=SGH-I747
http://samsung-updates.com/device/?id=SGH-I747M
BCSC said:
You can download an Odin flashable recovery from here. http://techerrata.com/browse/twrp2/d2att. you will want the .tar file.
Beyond this i'm running out of ideas. Not too sure if this will work if you have gone stock with Odin as it may have taken root from you. Worth a try though.
Maybe an emergency recovery through Kies... http://forum.xda-developers.com/showthread.php?t=1984717
Beyond that try Odin again and re download the stock Rom from a different source. You may have gotten a bad download. I have read of it happening. Maybe even an older firmware or Canadian one (i'm assuming you're ATT): http://samsung-updates.com/device/?id=SGH-I747
http://samsung-updates.com/device/?id=SGH-I747M
Click to expand...
Click to collapse
i've tried both those methods but it still hasn't solved the problem. i'm going to try to flash ics. hopefully something good happens; i don't want to have to pay to get it fixed.
lolduck said:
i've tried both those methods but it still hasn't solved the problem. i'm going to try to flash ics. hopefully something good happens; i don't want to have to pay to get it fixed.
Click to expand...
Click to collapse
Sorry I couldn't help. Good luck.
BCSC said:
Sorry I couldn't help. Good luck.
Click to expand...
Click to collapse
thanks for your help. sucks that you couldn't find the problem.
Hey guys, I'm new to the HTC one, and I made a mistake. I accidentally formatted my device, the sdcard, firmware, and data, and I'm unable to mount the sdcard and data. I have clockworkmod recovery installed, and the bootloader unlocked, but I'm unable to do much else. When I attempt to flash a rom using sideloader, the screen will just reboot several times. I tried two different roms, CyanogenMod and Stock Rom, by either installing through sideloader or adb, but again, I can't see my SD card. I need help.
How can I fix my phone at this point? I'd be okay with either Stock Rom or CyanogenMod, I just need my phone working.
Please give a newbie a hand guys.
Thanks in advance.
dddmcd77 said:
Hey guys, I'm new to the HTC one, and I made a mistake. I accidentally formatted my device, the sd and data, and I'm unable to mount the two. I have clockworkmod recovery installed, and the bootloader unlocked, but I'm unable to do much else. When I attempt to flash a rom, the screen will just reboot several times. I tried two different roms, CyanogenMod and Stock Rom, by either installing through sideloader or adb, but again, I can't see my SD card. I need help.
How can I fix my phone at this point? I'd be okay with either Stock Rom or CyanogenMod, I just need my phone working.
Please give a newbie a hand guys.
Thanks in advance.
Click to expand...
Click to collapse
I don't know, but maybe try loading this by following the directions. Maybe you formatted the actual OS completely? This will get you to CM and then from there hopefully flash again
http://wiki.cyanogenmod.org/w/Install_CM_for_m7vzw
Also, try rebooting JUST the recovery, because then your SD shows up again.
Sent from my HTC6500LVW using Tapatalk
thanks for the reply
justinisloco said:
I don't know, but maybe try loading this by following the directions. Maybe you formatted the actual OS completely? This will get you to CM and then from there hopefully flash again
Also, try rebooting JUST the recovery, because then your SD shows up again.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
thanks I'll give it a shot. but I did reboot recovery, and I'm still unable to see my SD, it still claims it can't mount it.
Also I forgot to include that it is a verizon phone.
dddmcd77 said:
thanks I'll give it a shot. but I did reboot recovery, and I'm still unable to see my SD, it still claims it can't mount it.
Also I forgot to include that it is a verizon phone.
Click to expand...
Click to collapse
Did you flash the correct recovery for the vzw model?
Sent from my Nexus 7 using Tapatalk 4
version
dottat said:
Did you flash the correct recovery for the vzw model?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I attempted to flash the latest nightly file of cm-10.2-20131130-NIGHTLY-m7vzw.zip
dddmcd77 said:
I attempted to flash the latest nightly file of cm-10.2-20131130-NIGHTLY-m7vzw.zip
Click to expand...
Click to collapse
He asked about recovery.
cm-10.2-20131130-NIGHTLY-m7vzw.zip appears to be a ROM?
Oops
carm01 said:
He asked about recovery.
cm-10.2-20131130-NIGHTLY-m7vzw.zip appears to be a ROM?
Click to expand...
Click to collapse
Oh I'm sorry, I read that wrong. My bad. Yes, the recovery worked fine, no issues there.
dddmcd77 said:
Hey guys, I'm new to the HTC one, and I made a mistake. I accidentally formatted my device, the sdcard, firmware, and data, and I'm unable to mount the sdcard and data. I have clockworkmod recovery installed, and the bootloader unlocked, but I'm unable to do much else. When I attempt to flash a rom using sideloader, the screen will just reboot several times. I tried two different roms, CyanogenMod and Stock Rom, by either installing through sideloader or adb, but again, I can't see my SD card. I need help.
How can I fix my phone at this point? I'd be okay with either Stock Rom or CyanogenMod, I just need my phone working.
Please give a newbie a hand guys.
Thanks in advance.
Click to expand...
Click to collapse
Can you walk us through your steps of sideloading? Wondering if you're doing it correctly.
Also, you should reflash the recovery so that you're 100% positive it is for the VZW One.
can do
karn101 said:
Can you walk us through your steps of sideloading? Wondering if you're doing it correctly.
Also, you should reflash the recovery so that you're 100% positive it is for the VZW One.
Click to expand...
Click to collapse
Sure, I boot into recovery and use the command adb sideload "zip file here" and get the loading progess percentage and then it loads on my phone, yet it doesn't work right. Also, for some reason, my phone's bootloader has "relocked" when I know for a fact I avoided that command for fear of ruining my chances to fix the phone, now if I attempt to flash recovery to double check, I'm told its not allowed and it fails.
dddmcd77 said:
Sure, I boot into recovery and use the command adb sideload "zip file here" and get the loading progess percentage and then it loads on my phone, yet it doesn't work right.
Click to expand...
Click to collapse
I'd try a different recovery. Flash TWRP and try it again. If it doesn't work, then I'm out of ideas for you. Last thing I can think about is RUU'ing your phone.
karn101 said:
I'd try a different recovery. Flash TWRP and try it again. If it doesn't work, then I'm out of ideas for you. Last thing I can think about is RUU'ing your phone.
Click to expand...
Click to collapse
Also you can try this method, although i never done it this way
Can Try :
Are you attempting to flash from fastboot or from ruu mode
fastboot oem rebootRUU
fastboot flash zip zipname.zip
fastboot reboot
if it fails try again.
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash romzip.zip
fastboot reboot
Might want to get a full stock ROM here: http://forum.xda-developers.com/showthread.php?t=2485319
I tried RUU
karn101 said:
I'd try a different recovery. Flash TWRP and try it again. If it doesn't work, then I'm out of ideas for you. Last thing I can think about is RUU'ing your phone.
Click to expand...
Click to collapse
I just tried RUUing a few minutes ago, when I attempted to flash stock recovery I was unable, the instructions for VZW told me to flash stock recovery and boot, but I recieved failure notices.
dddmcd77 said:
I just tried RUUing a few minutes ago, when I attempted to flash stock recovery I was unable, the instructions for VZW told me to flash stock recovery and boot, but I recieved failure notices.
Click to expand...
Click to collapse
What firmware you on?
thank you very much
carm01 said:
Also you can try this method, although i never done it this way
Can Try :
Are you attempting to flash from fastboot or from ruu mode
fastboot oem rebootRUU
fastboot flash zip zipname.zip
fastboot reboot
if it fails try again.
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash romzip.zip
fastboot reboot
Might want to get a full stock ROM here: http://forum.xda-developers.com/showthread.php?t=2485319
Click to expand...
Click to collapse
Thanks, I'll give this method a shot right now and report back. my firmware was one of the things that was messed up, and I tried flashing the stock but it was unsucessful.
dddmcd77 said:
Thanks, I'll give this method a shot right now and report back.
Click to expand...
Click to collapse
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot
my firmware
carm01 said:
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot
Click to expand...
Click to collapse
To answer your other question, the firmware was one of the many things messed up. Flash attempts of the stock firmware were unsuccessful.
dddmcd77 said:
I just tried RUUing a few minutes ago, when I attempted to flash stock recovery I was unable, the instructions for VZW told me to flash stock recovery and boot, but I recieved failure notices.
Click to expand...
Click to collapse
You don't need to flash the stock recovery.
http://forum.xda-developers.com/showthread.php?t=2475216
The RUU flashes stock recovery. You can skip the first portion (ADB shell) and the last (write secure flag) in the instructions above.
Basically, just start at
fastboot oem rebootRUU
problem with that.
karn101 said:
You don't need to flash the stock recovery.
http://forum.xda-developers.com/showthread.php?t=2475216
The RUU flashes stock recovery. You can skip the first portion (ADB shell) and the last (write secure flag) in the instructions above.
Basically, just start at
fastboot oem rebootRUU
Click to expand...
Click to collapse
My bootloader relocked for some reason. Is that gonna be a problem?
thread closed
hey guys thanks for the help, I just got my phone to stock. Thanks again so much, I owe you all one. You're great people.
dddmcd77 said:
hey guys thanks for the help, I just got my phone to stock. Thanks again so much, I owe you all one. You're great people.
Click to expand...
Click to collapse
What fixed it for you?
I cant format,update,or enter revovery mode.Ive tried to turn off the phone and do that power button and volume up.Then i go press recovery,then the phone restarts and go to the same screen.Theres no error thingy showing.
Hi,
Reflash your recovery via fastboot command:
Code:
fastboot flash recovery [color="red"]recovery.img[/color]
Replace recovery.img with your prefered recovery's filename.
Sent from my GT-I9500
krasCGQ said:
Hi,
Reflash your recovery via fastboot command:
Code:
fastboot flash recovery [color="red"]recovery.img[/color]
Replace recovery.img with your prefered recovery's filename.
Sent from my GT-I9500
Click to expand...
Click to collapse
Fastboot undetected
haridzk said:
Fastboot undetected
Click to expand...
Click to collapse
Have you installed the USB driver?
Sent from my GT-I9500
krasCGQ said:
Have you installed the USB driver?
Sent from my GT-I9500
Click to expand...
Click to collapse
You mean using conputer?
New Z00A ZE551ML 3.15 firmware can't upgrade OTA manually
I have the same problem, although it is not likely the drivers.
When attempting to sideload the full firmware image, it errors out after a few seconds, stating that it cannot detect the device. I reboot the phone manually, then reboot bootloader from command prompt. try again and the same thing happens. First, I tried placing the file on an sd card, renaming it to MOFD_SDUPDATE but it failed after 25% and left me with the screen showing the "unplugged" icon. Now I cannot enter recovery at all. Attempted root, tethered, untethered, and no luck with any. I used an app before trying any of this to make sure it was not rooted or unlocked already. I'm running out of ideas. When I get home, I will try flashing just the droidboot.img as suggested in this thread: http://forum.xda-developers.com/zenfone2/help/unlock-bootloader-read-fix-t3138837.
Any other advice would be greatly appreciated. As I said my phone has
VERSION: WW-ASUS_Z00A-2.15.40.13 and failed to manually upgrade to 2.19.40
haridzk said:
You mean using conputer?
Click to expand...
Click to collapse
No, I mean USB Driver, for real. You can't do anything related to debugging without having the related drivers installed.
Sent from my GT-I9500
Quadro1972 said:
I have the same problem, although it is not likely the drivers.
When attempting to sideload the full firmware image, it errors out after a few seconds, stating that it cannot detect the device. I reboot the phone manually, then reboot bootloader from command prompt. try again and the same thing happens. First, I tried placing the file on an sd card, renaming it to MOFD_SDUPDATE but it failed after 25% and left me with the screen showing the "unplugged" icon. Now I cannot enter recovery at all. Attempted root, tethered, untethered, and no luck with any. I used an app before trying any of this to make sure it was not rooted or unlocked already. I'm running out of ideas. When I get home, I will try flashing just the droidboot.img as suggested in this thread: http://forum.xda-developers.com/zenfone2/help/unlock-bootloader-read-fix-t3138837.
Any other advice would be greatly appreciated. As I said my phone has
VERSION: WW-ASUS_Z00A-2.15.40.13 and failed to manually upgrade to 2.19.40
Click to expand...
Click to collapse
If you are getting the USB logo on your screen you're sh!t out of luck as it is a hard brick... You'll need to send back to ASUS to get rom put back on phone...
ultramag69 said:
If you are getting the USB logo on your screen you're sh!t out of luck as it is a hard brick... You'll need to send back to ASUS to get rom put back on phone...
Click to expand...
Click to collapse
I was very fortunate that it would still boot into the bootloader. As a result I was able to fix using these instructions and pre-rooted images, including an Asus recovery image:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
---------- Post added at 04:37 AM ---------- Previous post was at 04:33 AM ----------
Quadro1972 said:
I was very fortunate that it would still boot into the bootloader. As a result I was able to fix using these instructions and pre-rooted images, including an Asus recovery image:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Click to expand...
Click to collapse
Also, if anyone else attempts this fix, download the images using Google Chrome or it will error out, fail checksum
While flashing a stock rom on odin and it got interrupted, the error showed after rebooting. I have tried with kies but it only keeps on disconnecting when plugged in. It no longer allows me to enter into download mode.
I know that there are threads here regarding this issue, but there is no solution that worked for me.
Please help me I have tried every solution that I have found based on different samsung devices. Nothing works for me.
SM-T210
What device is it? On older devices like my TAB3 the error screen that you get that tells you to use kies to fix is download mode and Odin should recognize it. I've tried a few things that have left me in this situation.
RealWelder said:
What device is it? On older devices like my TAB3 the error screen that you get that tells you to use kies to fix is download mode and Odin should recognize it. I've tried a few things that have left me in this situation.
Click to expand...
Click to collapse
Thank you for replying. The model device name is SM-T210. Yes, Odin can still recognize it but no luck on kies. Did you fix yours?
Yes, i have a 210R. I've done this many times. What I always do use odin to flash @gr8nole's TWRP recovery. Then in TWRP either restore a backup or download my custom ROM and install it in TWRP. (I did my ROM off of 210 firmware so it would be compatible with both the 210 and the 210R)
---------- Post added at 01:23 PM ---------- Previous post was at 01:18 PM ----------
Here is my ROMs thread.
https://forum.xda-developers.com/showthread.php?t=3510449
The zip will flash a raw system image and boot image and should get you going. If not I can upload a twrp backup for you.
RealWelder said:
Yes, i have a 210R. I've done this many times. What I always do use odin to flash @gr8nole's TWRP recovery. Then in TWRP either restore a backup or download my custom ROM and install it in TWRP. (I did my ROM off of 210 firmware so it would be compatible with both the 210 and the 210R)
Click to expand...
Click to collapse
That's good to hear. Is this the one that you used? https://forum.xda-developers.com/showthread.php?t=2437219
So in flashing TWRP on Odin, do I need to uncheck the auto reboot and directly boot it to TWRP after flashing is done?
gamzybaby said:
That's good to hear. Is this the one that you used? https://forum.xda-developers.com/showthread.php?t=2437219
So in flashing TWRP on Odin, do I need to uncheck the auto reboot and directly boot it to TWRP after flashing is done?
Click to expand...
Click to collapse
Yep that's the one. Honestly, it should work either way...since no OS is installed if you try to boot it should automatically reboot to TWRP.
RealWelder said:
Yep that's the one. Honestly, it should work either way...since no OS is installed if you try to boot it should automatically reboot to TWRP.
Click to expand...
Click to collapse
Thank you so much for your help. I am currently downloading your ROM and will update you later. 300kbps download speed
gamzybaby said:
Thank you so much for your help. I am currently downloading your ROM and will update you later. 300kbps download speed
Click to expand...
Click to collapse
No problem. I'll be off and on throughout the day, if you need anything.
RealWelder said:
No problem. I'll be off and on throughout the day, if you need anything.
Click to expand...
Click to collapse
There's no problem flashing the TWRP but it still goes back to the problem. I'll show you a picture of the error.
gamzybaby said:
There's no problem flashing the TWRP but it still goes back to the problem. I'll show you a picture of the error.
Click to expand...
Click to collapse
Try holding vol+, home, and power until the tab3 splash comes up, then release power but keep the other 2 held in. It should boot to TWRP recovery.
RealWelder said:
Try holding vol+, home, and power until the tab3 splash comes up, then release power but keep the other 2 held in. It should boot to TWRP recovery.
Click to expand...
Click to collapse
I tried that but the tab3 splash doesn't come up. The one that I showed you will show.
gamzybaby said:
I tried that but the tab3 splash doesn't come up. The one that I showed you will show.
Click to expand...
Click to collapse
Do you have adb? If so, does the adb recognize the tab?
RealWelder said:
Do you have adb? If so, does the adb recognize the tab?
Click to expand...
Click to collapse
Sorry. I have no knowledge about Adb. But I'm willing to learn.
First let's go ahead and retry your stock firmware with Odin. If it is successful, you can reflash TWRP and then try my ROM or just run stock. If that doesn't work, then we'll try adb. After your odin flash, even if it fails, if the splash screen comes back, you can flash TWRP and then enter recovery.
RealWelder said:
First let's go ahead and retry your stock firmware with Odin. If it is successful, you can reflash TWRP and then try my ROM or just run stock. If that doesn't work, then we'll try adb. After your odin flash, even if it fails, if the splash screen comes back, you can flash TWRP and then enter recovery.
Click to expand...
Click to collapse
Just know that I can't go into download mode. Though Odin can still detect and flash. But I will try what you said and reflash the stock firmware i downloaded from sammobile.
RealWelder said:
First let's go ahead and retry your stock firmware with Odin. If it is successful, you can reflash TWRP and then try my ROM or just run stock. If that doesn't work, then we'll try adb. After your odin flash, even if it fails, if the splash screen comes back, you can flash TWRP and then enter recovery.
Click to expand...
Click to collapse
Theres no problem in flashing. Everything is fine but it still returns to the error.
Hmm. Is it the correct firmware? I'm gonna go ahead and prepare you a file that will have adb, fastboot, and a cmd window. I'll upload it shortly, just extract it into a folder on your desktop or somewhere where it is easy to get to.
---------- Post added at 03:14 PM ---------- Previous post was at 03:12 PM ----------
https://drive.google.com/file/d/0B3XczzpnAnvwcmdRb1YxRDlyR00/view?usp=drivesdk
Here is adb. After you extract it, open the cmd window and type adb devices with the tab plugged in. Hopefully it will show it.
RealWelder said:
Hmm. Is it the correct firmware? I'm gonna go ahead and prepare you a file that will have adb, fastboot, and a cmd window. I'll upload it shortly, just extract it into a folder on your desktop or somewhere where it is easy to get to.
Click to expand...
Click to collapse
Now that I don't know. But I searched for Sm-t210. Okay. Thank you so much for your time and effort.
gamzybaby said:
Now that I don't know. But I searched for Sm-t210. Okay. Thank you so much for your time and effort.
Click to expand...
Click to collapse
https://www.sammobile.com/firmwares/database/SM-T210/
If I remember right we want the UK version.
RealWelder said:
https://www.sammobile.com/firmwares/database/SM-T210/
If I remember right we want the UK version.
Click to expand...
Click to collapse
The adb that you gave me didnt work. It says it lacks .dll. So I downloaded this https://forum.xda-developers.com/showthread.php?t=2317790
I dont know if that works. and I tried adb devices.
https://drive.google.com/file/d/0B2KHvn5cNuHcOWFYXzM0c1RhWmc/view?usp=sharing