Related
So I messed. Accidentally formatted my phone and now it's screwed. Tried to use fastboot to put boot.img on, but my computer won't recognize my phone when I do "fastboot devices" or any commands. It won't boot or anything. I dunno what to do, kinda need a phone. Any help would be greatly appreciated and rewarded duly.
Cynicsatire said:
So I messed. Accidentally formatted my phone and now it's screwed. Tried to use fastboot to put boot.img on, but my computer won't recognize my phone when I do "fastboot devices" or any commands. It won't boot or anything. I dunno what to do, kinda need a phone. Any help would be greatly appreciated and rewarded duly.
Click to expand...
Click to collapse
so no signs of life at all? can you get to the bootloader? how exactly did you format your phone?
the XDA brains trust is going to need a bit more info.
codeprimate said:
so no signs of life at all? can you get to the bootloader? how exactly did you format your phone?
the XDA brains trust is going to need a bit more info.
Click to expand...
Click to collapse
Sorry, there are signs of life. I can get to the bootloader and recovery. And I honestly clicked the wrong button, that's what happens when you don't sleep and decide to try to flash a new rom.
Are you sure you didn't flash a new Rom
Cynicsatire said:
Sorry, there are signs of life. I can get to the bootloader and recovery. And I honestly clicked the wrong button, that's what happens when you don't sleep and decide to try to flash a new rom.
Click to expand...
Click to collapse
If you can get to bootloader and recovery, you're not bricked. You just need to flash a new rom, this time remembering to flash the boot.img in fastboot like the instructions say.
Oops I thought he Saud there are no signs of life..Elvis spots all
iElvis said:
If you can get to bootloader and recovery, you're not bricked. You just need to flash a new rom, this time remembering to flash the boot.img in fastboot like the instructions say.
Click to expand...
Click to collapse
the problem is my computer isn't registering the device when i do fastboot.
Cynicsatire said:
the problem is my computer isn't registering the device when i do fastboot.
Click to expand...
Click to collapse
If 'fastboot devices' returns nothing, then you are most likely missing drivers. Easiest way to get drivers is install HTC Sync Manager. It will install the app and the drivers, you can safely uninstall the app later and still have the drivers stay installed
Sent from my One X
reboot to fastboot, but do not select bootloader (it should say "Fastboot" in red writing just underneath the green text and above the orange text.
connect it via usb to your pc, and it should say "fastboot usb", then you should be able to use fastboot commands. if it doen't allow you to use fastboot commands, try a different usb port, or reinstalling the drivers.
codeprimate said:
reboot to fastboot, but do not select bootloader (it should say "Fastboot" in red writing just underneath the green text and above the orange text.
connect it via usb to your pc, and it should say "fastboot usb", then you should be able to use fastboot commands. if it doen't allow you to use fastboot commands, try a different usb port, or reinstalling the drivers.
Click to expand...
Click to collapse
Did this, now it's stuck at the htc screen. Any suggestions?
Cynicsatire said:
Did this, now it's stuck at the htc screen. Any suggestions?
Click to expand...
Click to collapse
Hmmm, when it rebooted it stopped at the htc screen? This sounds like it's not going to the fastboot mode. Reboot with the volume held down. That should get to the fastboot mode.
codeprimate said:
Hmmm, when it rebooted it stopped at the htc screen? This sounds like it's not going to the fastboot mode. Reboot with the volume held down. That should get to the fastboot mode.
Click to expand...
Click to collapse
After I push the boot.img through fastboot, when I reboot it just sticks on the HTC boot screen. I can get to the fastboot screen but I already have the boot.img on there. What next? should it work?
Cynicsatire said:
After I push the boot.img through fastboot, when I reboot it just sticks on the HTC boot screen. I can get to the fastboot screen but I already have the boot.img on there. What next? should it work?
Click to expand...
Click to collapse
go to your recovery and flash the ROM (the boot.img is just the kernel) if you haven't done that.
codeprimate said:
go to your recovery and flash the ROM (the boot.img is just the kernel) if you haven't done that.
Click to expand...
Click to collapse
Oh. That makes sense. It works now. Thanks a million. I owe you one.
os deleted and just stuck on one+ logo can boot in to twrp or fast boot what can i do?
brooklynchildxbc said:
os deleted and just stuck on one+ logo can boot in to twrp or fast boot what can i do?
Click to expand...
Click to collapse
Push a custom rom via adb and flash in recovery or flash stock images via fastboot
acuicultor said:
Push a custom rom via adb and flash in recovery or flash stock images via fastboot
Click to expand...
Click to collapse
i tried adb won't work and fastboot not doing anything i keeping getting a error saying that bootloader locked or can't erase
what really pisses me off i didn't even brick it a dumbass friend of mine did thinking he knew what he was doing.
brooklynchildxbc said:
i tried adb won't work and fastboot not doing anything i keeping getting a error saying that bootloader locked or can't erase
what really pisses me off i didn't even brick it a dumbass friend of mine did thinking he knew what he was doing.
Click to expand...
Click to collapse
Is fastboot working? Unlock bootloader and push custom recovery there. Go to adb sideload and that should work eventually. I had an issue with HTC One M7 - someone deleted sytem, and cyanogenmod installer helped, because it pushed CWM recovery, maybe try that one as well?
boober78 said:
Is fastboot working? Unlock bootloader and push custom recovery there. Go to adb sideload and that should work eventually. I had an issue with HTC One M7 - someone deleted sytem, and cyanogenmod installer helped, because it pushed CWM recovery, maybe try that one as well?
Click to expand...
Click to collapse
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
brooklynchildxbc said:
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
Click to expand...
Click to collapse
No problem. I'm glad I could help
Sent from my One using Tapatalk
brooklynchildxbc said:
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
Click to expand...
Click to collapse
Don't give up.... I was in the same position like you for a couple days....and now is fix by my self..... If you unlock your bootloader try to lock back (fastboot oem lock) now try to flash via fastboot Philz Recovery ( try until is rebooting himself into recovery) .... After that put on a memory stick the new system .... You may need to mount the USB flash drive ..... That's exactly what I have done....Good Luck ...
It is damn near IMPOSSIBLE to actualy, truly "brick" these devices. There are way too many safeguards in place.
Be careful before announcing that you are "bricked". Bootlooping (which is what your device was doing) is not "bricked". As long as you have fastboot, you can always reflash recovery, and then use recovery to reflash your custom ROM (or you can bypass all of that and reflash the factory images from fastboot).
Don't panic, you know more than you think you know. Just don't get freaked out, and read. You'll be fine.
I have searched and tried different things but I'm getting nowhere. I have been running Purity rom on this for a while but when I woke up this morning, I found my screen black and only being able to boot to the bootloader and and google screen (which quickly goes away and goes black again). When I tried to go to recovery at first I believe it was just shutting off. Now it goes to a light black screen.
The first thing I did was flashed the factory image .bat file and everything seemed to go ok but when trying to go to recovery after it went to the light black screen. I turned it off and it booted to the Google screen then off again. Then it booted to the google screen and it froze that way. I can always get it back to the bootloader screen and got it to recovery once by flashing TWRP again using ADB.
TWRP opened once and I tried to do a factory reset but it couldn't find anything and couldn't mount to anything. I got it back to the bootloader again but the recovery has disappeared again. I tried to flash the factory image again but it definitely failed this time.
Please help.
aburn95 said:
I have searched and tried different things but I'm getting nowhere. I have been running Purity rom on this for a while but when I woke up this morning, I found my screen black and only being able to boot to the bootloader and and google screen (which quickly goes away and goes black again). When I tried to go to recovery at first I believe it was just shutting off. Now it goes to a light black screen.
The first thing I did was flashed the factory image .bat file and everything seemed to go ok but when trying to go to recovery after it went to the light black screen. I turned it off and it booted to the Google screen then off again. Then it booted to the google screen and it froze that way. I can always get it back to the bootloader screen and got it to recovery once by flashing TWRP again using ADB.
TWRP opened once and I tried to do a factory reset but it couldn't find anything and couldn't mount to anything. I got it back to the bootloader again but the recovery has disappeared again. I tried to flash the factory image again but it definitely failed this time.
Please help.
Click to expand...
Click to collapse
@bitdomo might be able to help you lol
Might be bad eMMC or something?
when youre flashing recovery, which command are you using.. fastboot boot recovery recoveryname.img or fastboot flash recovery recoveryname.img?
aburn95 said:
I have searched and tried different things but I'm getting nowhere. I have been running Purity rom on this for a while but when I woke up this morning, I found my screen black and only being able to boot to the bootloader and and google screen (which quickly goes away and goes black again). When I tried to go to recovery at first I believe it was just shutting off. Now it goes to a light black screen.
The first thing I did was flashed the factory image .bat file and everything seemed to go ok but when trying to go to recovery after it went to the light black screen. I turned it off and it booted to the Google screen then off again. Then it booted to the google screen and it froze that way. I can always get it back to the bootloader screen and got it to recovery once by flashing TWRP again using ADB.
TWRP opened once and I tried to do a factory reset but it couldn't find anything and couldn't mount to anything. I got it back to the bootloader again but the recovery has disappeared again. I tried to flash the factory image again but it definitely failed this time.
Please help.
Click to expand...
Click to collapse
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
simms22 said:
when youre flashing recovery, which command are you using.. fastboot boot recovery recoveryname.img or fastboot flash recovery recoveryname.img?
Click to expand...
Click to collapse
Hey I'm using "fastboot flash recovery recovery.img" and that's what I've used in the past. I've had a fully functioning rom with fully functioning recovery for a while until yesterday.
bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Ok thanks I'll try this and check the text in fastboot after work today. Thanks for the responses guys.
After reading some more last night I'm afraid it's an emmc problem but I like to be proven wrong sometimes.
Maybe also try this?
http://forum.xda-developers.com/showthread.php?t=2577447
beekay201 said:
Maybe also try this?
http://forum.xda-developers.com/showthread.php?t=2577447
Click to expand...
Click to collapse
I actually have that thread open on my computer. It was my next attempt of repair before starting the thread late last night. Thanks for the suggestion I will certainly try it.
Update: I tried pushing Philz recovery to the phone which seemed to work fine until I selected go to recovery mode. It just went back to that barely light black screen. I'll try again when I get home. Going to try Bitdomo's advice about locking bootloader first.
bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Out of curiosity what's the reason for using two brands, or were they just available so they were used?
bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Bitdomo I'm trying the Flashtool but it's staying at 0% on the firmware update and nothing is popping up on computer or in Device Manager. Had no connection issues prior to the brick or with adb/fastboot. My Ports aren't evening showing at all in DM even if I select show hidden devices.
aburn95 said:
How do I lock the bootloader without being able to put the .zip on my internal memory?
Click to expand...
Click to collapse
In fastboot type
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
In fastboot type
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I honestly wanted to do that but it seemed too easy. I was trying to lock it like I did before when i had to send original back to T-Mobile. Sorry and thanks.
bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Ok so it stayed locked so that's a start. I'm back in download mode again but it's staying at 0% and nothing on computer.
I tried to re-download the factory images and flash again using adb. It failed again. Here's a picture of what happened:
Unzip the zip and use manual flash commands. Clikc the link in my signature and read my "adb and fastboot. What is it?" thread of you're unsure of the commands.
Sent from my Nexus 5 using Tapatalk
aburn95 said:
I tried to re-download the factory images and flash again using adb. It failed again. Here's a picture of what happened:
Click to expand...
Click to collapse
You have "remote: flash write failure" error. It means your emmc (internal storage) is broken and you cannot modify the data on it. You have to rma your device.
Just for matter of research can you enter to fastboot and post the variable line here?
Mine is: hammerhead D821(H) 16GB
bitdomo said:
You have "remote: flash write failure" error. It means your emmc (internal storage) is broken and you cannot modify the data on it. You have to rma your device.
Just for matter of research can you enter to fastboot and post the variable line here?
Mine is: hammerhead D821(H) 16GB
Click to expand...
Click to collapse
Sorry I meant to tell you yesterday... D820H 16GB. Should I still be able to toggle the tamper tag so they will take it back with no problems? Or am I screwed?
aburn95 said:
Sorry I meant to tell you yesterday... 820H. Should I still be able to toggle the tamper so they will take it back with no problems? Or am I screwed?
Click to expand...
Click to collapse
You should be able to if you managed to lock the bootloader. The name of the zip does not came into my mind which you have to flash, but you have to do it with the adb sideload command because you cant copy anything to your phone, or use adb push command to push it to the "/" folder because it is mounted to the ram which you can write not like your storage . If you bought your phone from google it does not matter you have tamper flag set to 1.
bitdomo said:
You should be able to if you managed to lock the bootloader. The name of the zip does not came into my mind which you have to flash, but you have to do it with the adb sideload command because you cant copy anything to your phone, or use adb push command to push it to the "/" folder because it is mounted to the ram which you can write not like your storage . If you bought your phone from google it does not matter you have tamper flag set to 1.
Click to expand...
Click to collapse
Ok thanks. I haven't quite figured out the adb sideload function yet. I tried doing it through TWRP but it just sits there and does nothing after selecting. Maybe I'm trying the wrong thing. I got my phone from T-Mobile so I'll need to solve this. Thanks for the help.
This phone is being a real a-hole. I'm trying to boot to stock recovery but it just sits on a screen with a really big android with wiggling antennae. I pressed up+power many times but it stayed that way. So I tried booting to TWRP again and it did but went immediately to an "OpenRecoveryScript," had a little bar at the bottom for a while with some other stuff on the screen, then turned off.
I tried stock recovery again and it went to the little dead android this time but still nothing when I press up+power.
I may have bricked, want to know what went wrong and if it's permanent. Thanks, here's how it happened.
I was running one of the Omnirom nightly builds. I got a notification saying there was a new build, I decided to try it hoping it would improve my battery life. I had TWRP installed so I thought it would be ok (I chose to let it update automatically which I guess was my mistake). It did the update or tried to at least, but when it tried to boot it just gets stuck on the Asus screen. The one with the loading bar. Volume up or down with power button does nothing but get back to the same screen. Reset (using a pin) and volume up or down does the same thing. I thought the only way to permanently boot was doing the wipe option on the recovery menu, but maybe I am wrong. Is it possible to permanently brick doing what I did? Thanks. Any possible solutions?
mechz01 said:
Is it possible to permanently brick doing what I did? Thanks. Any possible solutions?
Click to expand...
Click to collapse
Unlikely. What always works, if you can put it into fastboot, is install the Asus stock ROM. That will reformat/reinstall every partition.
Berend de Boer said:
Unlikely. What always works, if you can put it into fastboot, is install the Asus stock ROM. That will reformat/reinstall every partition.
Click to expand...
Click to collapse
That's holding the reset button down plus volume down right? Doesn't seem to work.
mechz01 said:
That's holding the reset button down plus volume down right? Doesn't seem to work.
Click to expand...
Click to collapse
Try long holding VOL DOWN & POWER BUTTON ....
Can you get to the bootloader this way ?
Thx Josh
lj50036 said:
Try long holding VOL DOWN & POWER BUTTON ....
Can you get to the bootloader this way ?
Thx Josh
Click to expand...
Click to collapse
Thanks for the Reply
No, it just gets me back to the same screen. This is supposed to get me to the recovery menu right?
If it matters,my bootloader is unlocked.
mechz01 said:
Thanks for the Reply
No, it just gets me back to the same screen. This is supposed to get me to the recovery menu right?
If it matters,my bootloader is unlocked.
Click to expand...
Click to collapse
Well there is not much that can be done then.....
No fastboot with a locked bootloader .....
No bootloader to boot into recoovery .....
No nvflash blobs with a locked bootloader ..
Short of a motherboard you have a paperweight .....
Sorry for the back news ......
Thx Josh
Hello
Hi
I had basically the same situation of this topic, the only i can access to fastboot.
I formated all my tablet, basically is nothing in the memory
when i tried to access over the recovery, is stuck, only blink.
Fastboot commands works but i dont know how i can recover all.
I know i need to install everything.
Can someone let me know what i can install (Kernel, firmware, rom(I want lollipop).
I had already TWRP 2.8.0
Thanks in advance
lj50036 said:
Well there is not much that can be done then.....
No fastboot with a locked bootloader .....
No bootloader to boot into recoovery .....
No nvflash blobs with a locked bootloader ..
Short of a motherboard you have a paperweight .....
Sorry for the back news ......
Thx Josh
Click to expand...
Click to collapse
My bootloader is unlocked, unless I am misunderstanding what you're saying. On the Asus screen it says this device is unlocked. Not sure why I can't access any of the options though, unless my volume buttons is busted or something.
jcbeau09 said:
Hi
I had basically the same situation of this topic, the only i can access to fastboot.
I formated all my tablet, basically is nothing in the memory
when i tried to access over the recovery, is stuck, only blink.
Fastboot commands works but i dont know how i can recover all.
I know i need to install everything.
Can someone let me know what i can install (Kernel, firmware, rom(I want lollipop).
I had already TWRP 2.8.0
Thanks in advance
Click to expand...
Click to collapse
First step: Install new TWRP
1. Download TWRP recovery from here: http://techerrata.com/browse/twrp2/tf300t; I would advise v. 2.8.4.0
2. Put 'openrecovery-twrp-2.8.3.0-tf300t.blob' in fastboot folder of pc and rename to twrp.blob for faster typing.
3. Put tab in fasboot mode and connect.
4. Use command
Code:
fastboot -i 0x0b05 flash staging twrp.blob[enter]
fastboot -i 0x0b05 reboot[enter]
5. Let tab reboot to OS (will stay on ASUS screen, because you don't have OS as of now).
6. Reboot to bootloader screen and go to recovery (RCK); now you can flash any custom ROM you like.
Good luck!
mechz01 said:
No, it just gets me back to the same screen. This is supposed to get me to the recovery menu right?
Click to expand...
Click to collapse
No! Recovery comes way after fastboot mode. Recovery is loaded from your memory card. But something went wrong with your memory card, so you can't load that.
Once you booted your tablet into fastboot, type :"fastboot devices" on your PC. If it shows your tablet, you can easily flash a new ROM.
Berend de Boer said:
No! Recovery comes way after fastboot mode. Recovery is loaded from your memory card. But something went wrong with your memory card, so you can't load that.
Once you booted your tablet into fastboot, type :"fastboot devices" on your PC. If it shows your tablet, you can easily flash a new ROM.
Click to expand...
Click to collapse
I would like to know how you are going to flash a new rom with fastboot ?
Thx Josh
Hey so I am having a problem unlocking the bootloader.
This is my friends phone and he messed it up bad. What he told me is that he was trying to install a custom ROM on his phone which was already rooted and unlocked. When he went to install it he told me that the ROM locked his bootloader and earased everything on the phone.
When I got the phone it would only boot into fastboot and nothing else. The screen would just be blank.
I have run that color installed and now I get the opo screen when i turn it on and I can also boot into fastboot. I cannot boot into recovery because it is gone I think.
When I try and install the recovery through fastboot I cannot because the bootloader is still locked.
I also tried loading up the custom recovery with the command fastboot boot recovery recovery.img
This doesn't work because I am getting the error "cannot load 'recovery' : Permission denied
I am out of ideas and any help will be greatly appreciated.
smertz said:
Hey so I am having a problem unlocking the bootloader.
This is my friends phone and he messed it up bad. What he told me is that he was trying to install a custom ROM on his phone which was already rooted and unlocked. When he went to install it he told me that the ROM locked his bootloader and earased everything on the phone.
When I got the phone it would only boot into fastboot and nothing else. The screen would just be blank.
I have run that color installed and now I get the opo screen when i turn it on and I can also boot into fastboot. I cannot boot into recovery because it is gone I think.
When I try and install the recovery through fastboot I cannot because the bootloader is still locked.
I also tried loading up the custom recovery with the command fastboot boot recovery recovery.img
This doesn't work because I am getting the error "cannot load 'recovery' : Permission denied
I am out of ideas and any help will be greatly appreciated.
Click to expand...
Click to collapse
I think your friend is giving you dodgy information, flashing a ROM doesn't lock the bootloader. So can you get into recovery at all by using the recovery button combo? Hold power to turn the phone off. Hold volume down, then hold power (so you're holding them together), when you see the OnePlus boot logo let go of power but keep holding volume down until you reach recovery.
Heisenberg said:
I think your friend is giving you dodgy information, flashing a ROM doesn't lock the bootloader. So can you get into recovery at all by using the recovery button combo? Hold power to turn the phone off. Hold volume down, then hold power (so you're holding them together), when you see the OnePlus boot logo let go of power but keep holding volume down until you reach recovery.
Click to expand...
Click to collapse
I am sure there is something he isn't telling me.
I have tried booting into recovery and I will hold down the button for several minutes but it never boots into recovery.
The phone will only boot into fastboot.
smertz said:
I am sure there is something he isn't telling me.
I have tried booting into recovery and I will hold down the button for several minutes but it never boots into recovery.
The phone will only boot into fastboot.
Click to expand...
Click to collapse
There isn't much you can do then, without recovery and without being able to unlock the bootloader you're pretty much stuck.
Heisenberg said:
There isn't much you can do then, without recovery and without being able to unlock the bootloader you're pretty much stuck.
Click to expand...
Click to collapse
Darn. I was hoping there was some other way of unlocking the booloader. I know I can install a recovery if it was only unlocked.
smertz said:
Darn. I was hoping there was some other way of unlocking the booloader. I know I can install a recovery if it was only unlocked.
Click to expand...
Click to collapse
That's right, recovery install requires an unlocked bootloader. It doesn't really fit your situation but this might be worth looking into.
Heisenberg said:
That's right, recovery install requires an unlocked bootloader. It doesn't really fit your situation but this might be worth looking into.
Click to expand...
Click to collapse
Thanks! But I have already tried it. The second half of it requires that you have an unlocked bootloader to use fastboot.
smertz said:
Thanks! But I have already tried it. The second half of it requires that you have an unlocked bootloader to use fastboot.
Click to expand...
Click to collapse
Oh yeah, I forgot you mentioned that in the OP. Well there's really nothing you can do unfortunately.
Heisenberg said:
Oh yeah, I forgot you mentioned that in the OP. Well there's really nothing you can do unfortunately.
Click to expand...
Click to collapse
Ugh darn I was hoping there was something I could do. Thanks for the help!