Related
SO i think I totally bricked my phone. Any input would be great. MMy phone boots up and is stuck on lg screen. I tried flash CWM and stock recovery but nothing. Any ideas or should i just send back and get a new one
I really mucked this one up
It's not a brick if it turns on! But I'm fairly new to this phone and I'm not familiar with it at all Normally I would suggest to fastboot flash the new OFFICIAL CWM recovery image, but I don't even know where to begin with fastboot on this phone
chillwillo9 said:
SO i think I totally bricked my phone. Any input would be great. MMy phone boots up and is stuck on lg screen. I tried flash CWM and stock recovery but nothing. Any ideas or should i just send back and get a new one
I really mucked this one up
Click to expand...
Click to collapse
It would probably be a little helpful (if you want help) if you let everyone know what you were doing when you "bricked" your phone. That way people know where to start in assisting you.
chillwillo9 said:
SO i think I totally bricked my phone. Any input would be great. MMy phone boots up and is stuck on lg screen. I tried flash CWM and stock recovery but nothing. Any ideas or should i just send back and get a new one
I really mucked this one up
Click to expand...
Click to collapse
I had a infinite loop problem on mine. I just restored to stock.
Turn phone off (pull battery if needed)
Turn on while holding volume down + power button
chillwillo9 said:
SO i think I totally bricked my phone. Any input would be great. MMy phone boots up and is stuck on lg screen. I tried flash CWM and stock recovery but nothing. Any ideas or should i just send back and get a new one
I really mucked this one up
Click to expand...
Click to collapse
What happens when you try to boot into recovery mode?
OK here is what I did to brick my device.
I wanted to do a factory reset and I used clockwork recovery to do so.
Wat I didn't know what that Clockwork recovery was going to format my system.
I can only get into fast boot via vol up+vol+down+power
Cannot get back to stock recovery or CWM. Tried flashing via fastboot method
My phone just goes to LG screen no loading bar
Currently the only function is fastboot
Did you try formatting via Vol-Down + Power?
xenoletum said:
Did you try formatting via Vol-Down + Power?
Click to expand...
Click to collapse
Yes I did but same result stuck Lg screen no loading bar.
Capacitive touch also are not lit appear to be not working
1) Fastboot flash the official CWM recovery image
2) download http://forum.xda-developers.com/showthread.php?t=1048274
3) put the NANDROID in the correct folder on your sdcard: /sdcard/_ExternalSD/clockworkmod/backup/
4) restore via recovery
Thanks for everyones input, Called t-mobile they are shipping a new one out asap. I'm just going to have to suck it up till tuesday.
I love trial and error they only thing i lost is a little time
omarsalmin said:
1) Fastboot flash the official CWM recovery image
2) download http://forum.xda-developers.com/showthread.php?t=1048274
3) put the NANDROID in the correct folder on your sdcard: /sdcard/_ExternalSD/clockworkmod/backup/
4) restore via recovery
Click to expand...
Click to collapse
I flashed official CWM recovery image numerous times via fastboot and phone just gets stuck at lg screen. Once again vol up+power and vol down+pwer does nothing
Is there another fastboot method or adb method to restore CWM?
did the same thing it bricked my phone does nothing else than start up then freezes. f-ING pissed
The best thing with Nvidia phones and tablets is that its barely impossible to brick your phone. If you think you bricked it - you just need NV flash and either the stock rom or stock recovery and you are back to normal
I have done that with my old G-tablet - it was a piece of cake to fix it.
is there an nv flash for mac?
thought i did the same thing!
if you can get it into format hit the home button. hopefully vol+down+power will get you there. pull your battery and you may just get lucky if done enough times? i would keep trying. good luck
Hi. I tried installing a rom and know it just sits at the boot screen. I can get into ADB and it works. I have the Wifi Version. How would I get this thing back up.
Can you please post the links to files I need to download.
ysuleman said:
Hi. I tried installing a rom and know it just sits at the boot screen. I can get into ADB and it works. I have the Wifi Version. How would I get this thing back up.
Can you please post the links to files I need to download.
Click to expand...
Click to collapse
wrong section this belongs in Q&A but all you need to do is get into recovery (adb reboot recovery) and then try wiping data and re flashing the rom
Can you get into Clockwork Mod Recovery? If so, just reflash.
All you have to do is reboot the thing when you see the Motorola Dual Core screen (its red) count 3 seconds and press volume down. Select what ever option you are going to use to fix your device with the volume down. Volume up to select. Its very difficult to "Brick" a Xoom.
If ADB is working just use adb reboot recovery. If thats not working use the method above and use fastboot and reflash recovery, fastboot erase recovery then fastboot flash recovery recovery.img (or flash Tiamat recovery/Rogue).
something like that pretty easy really.
ysuleman said:
Hi. I tried installing a rom and know it just sits at the boot screen. I can get into ADB and it works. I have the Wifi Version. How would I get this thing back up.
Can you please post the links to files I need to download.
Click to expand...
Click to collapse
Go to the appropriate sub forum and ask this.
I rooted my TF101 model B80 using RazorClaw (nvflash is a no-go for this model). Installed CWM, all was well. I tried to install Prime ROM from CWM, and was unimpressed; tried to restore my Nandroid backup of original rooted OS. Now, Transformer will not boot into any recovery (neither CWM or original green android), and screen comes up garbled. Is there any way I can restore my original stock by merely putting a particular image on my external sd card?
Any other suggestions welcome, I just can't get to a screen (recovery or otherwise) where there is any readable text I can respond to. Nor can I turn the device off. It will continue to reboot in this fashion. When I get home today I'll be able to start from a dead battery.
Thanks
Did you wipe before restore?
davebugyi said:
Did you wipe before restore?
Click to expand...
Click to collapse
Yes, I did a full wipe including dalvik cache before all restores. At this point, though, my primary concern is just finding a path back to usability!
DIncLover said:
I rooted my TF101 model B80 using RazorClaw (nvflash is a no-go for this model). Installed CWM, all was well. I tried to install Prime ROM from CWM, and was unimpressed; tried to restore my Nandroid backup of original rooted OS. Now, Transformer will not boot into any recovery (neither CWM or original green android), and screen comes up garbled. Is there any way I can restore my original stock by merely putting a particular image on my external sd card?
Any other suggestions welcome, I just can't get to a screen (recovery or otherwise) where there is any readable text I can respond to. Nor can I turn the device off. It will continue to reboot in this fashion. When I get home today I'll be able to start from a dead battery.
Thanks
Click to expand...
Click to collapse
I had the same situation..I used the unbrick method:
http://forum.xda-developers.com/showthread.php?t=1123429
then you could try restore a backup ..
To turn off the device press the power button for 10-15 seconds..
bruuuno said:
I had the same situation..I used the unbrick method:
http://forum.xda-developers.com/showthread.php?t=1123429
then you could try restore a backup ..
To turn off the device press the power button for 10-15 seconds..
Click to expand...
Click to collapse
I can try this when I get home today.... I'm just concerned because the method involves nvflash .... which I thought didn't work from the newer TF models (I have a model B80). I needed to wait for the RazorClaw exploit because previous attempts at using nvflash failed....
Then NVFlash will fail still...
davebugyi said:
Then NVFlash will fail still...
Click to expand...
Click to collapse
So am I hopelessly hosed?
Sounds like this problem
http://forum.xda-developers.com/showthread.php?t=1321207&highlight=green+screen
Being you can't get back into CWM not sure how you'll flash the stock kernel.
HAve you tried Holding Vol Down button plus Power button till you get prompt to enter recovery at which time immediately push Vol up button withion 5 sec.
baseballfanz said:
Sounds like this problem
http://forum.xda-developers.com/showthread.php?t=1321207&highlight=green+screen
Being you can't get back into CWM not sure how you'll flash the stock kernel.
HAve you tried Holding Vol Down button plus Power button till you get prompt to enter recovery at which time immediately push Vol up button withion 5 sec.
Click to expand...
Click to collapse
OK .... my bad.... I guess I wasn't pressing the buttons in the right sequence/duration. I CAN get to CWM!
So, once again, I try to restore the Nandroid backup and after rebooting, end up with the screen situation as in the reference you provided.
So, I am assuming my Nandroid backup is not restoring the kernel that it needs. I was running a recent OTA update; I believe the version was 8.6.5.19.
Where can I get the appropriate kernel to install from CWM? Does it matter in what order I install the kernel and the Nandroid backup?
DIncLover said:
Where can I get the appropriate kernel to install from CWM? Does it matter in what order I install the kernel and the Nandroid backup?
Click to expand...
Click to collapse
Look here
http://www.gnufabio.com/revolver/dls/
Same issue, no recovery though
Hi,
I have the same issue as the original poster, B80 serial, RazorClaw root. However, when I boot to recovery I get the green android with yellow triangle and exclamation mark.
I need to restore a recovery on my device as I may need to unroot to send to Asus. I have an even deeper problem of having to have the device connected to power for it to turn on after shut down.
However my main question is for that serial number and root method, what is the best way to flash a recovery on my device (stock or CWM) if I can not get into recovery to begin with?
P.S. RecoveryInstaller will not work, after installing the apk, I click the flash recovery button, the system holds for a bit, then nothing happens.
I will continue to search the forms for some answers, any insights or direction will be appreciated.
I can get into apx mode.
Thank you community!
I think you can flash the recovery via the staging partition. Search around the TF section, it's in here somewhere. Although, I wonder why the 1 click recovery didn't work?
gee one said:
I think you can flash the recovery via the staging partition. Search around the TF section, it's in here somewhere. Although, I wonder why the 1 click recovery didn't work?
Click to expand...
Click to collapse
Everything I see in the forms requires one of several conditions which my TF doesn't currently meet.
1. Recovery. I can not go into any recovery, thus I can not perform any flashing of any other rom or recovery.
2. B70 or later. Because of the security in the boot for these new serials, I can not use the NVFlash tools to un-brick / flash.
I am already rooted, however I do not know the reason for lack of recovery on this device. I unfortunately bought it yesterday from Craigslist, so not sure what this guy did before I got it.
I searched for flashing recovery staging partition and did not find anything immediately relevant. Please advice is there is a different wording I should use in my search as I am now getting an immense download on all of this trying to figure out what to do. I am also fairly new to Android devices having 1 other phone that is rooted.
Thank you for all the support and quick response! wonderful community here.
Try searching for posts with /dev/block/mmcblk0p4
This is particularly dangerous because you don't have access to nvflash. If you get bootloops, it is bricked. You have to be sure that whatever you flash will be 100% compatible with what you have now.
Also, when you try to boot into recovery, what does the text at the top say? There should be a version number in there somewhere.
sent from my cyanogen(mod) vision
gee one said:
Try searching for posts with /dev/block/mmcblk0p4
This is particularly dangerous because you don't have access to nvflash. If you get bootloops, it is bricked. You have to be sure that whatever you flash will be 100% compatible with what you have now.
Also, when you try to boot into recovery, what does the text at the top say? There should be a version number in there somewhere.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Thank you gee one. I have since been able to install clockworkmod. My issue with the power not turning on if not plugged in still persists, I have started a separate thread.
I found your post on the staging partition here:
http://forum.xda-developers.com/showthread.php?t=1309949&highlight=power
Do you recommend this for the issue still persisting?
If so, considering I am on 8.6.5.19 will I have to use the blob from that? It is not on Asus website as I got it from the firmware update option in the settings before loading up my new ROM.
Do you recommend this step as the only resolution or is there another way?
Ok let me get this straight:
You have clockworkmod installed. Can you boot into it and do the buttons work?
Are you getting a garbled screen when you boot into the rom? Or are you just trying to unroot?
The tricky part is to avoid the bootloops of death.
sent from my cyanogen(mod) vision
Honestly what i would do if i were you, assuming i understood correctly that you can get into clockworkmod, just reflash the prime rom you didnt like(after wiping everything, including cache and dalvik), and if it boots and everythings okay, at least you know nothings really wrong with ur tablet. As for the plug in situation, make sure your battery isnt simply dead. As far as i know, it wont charge from recovery, so if uve been stuck without a booting rom for a while, it being dead could definitely be possible. Once you are in a working rom and you sorted out the charging issue, then you should worry about getting back to stock.
Thank you camaros,
I am able to load stock ROM successfully.
Battery is not dead as it is fully charged, and will run un tethered after powerup. I will test resetting it although I doubt that is causing it.
What i would like to determine is, is this related to a hardware or software issue?
Also, is there a way to restore stock recovery from CWM?
I accepted the latest over the air update and I need to know if that messed up my chances of obtaining root. I tried photon torpedo and could not get it to work. My device says it is unlocked but I can not boot into recovery. I have flashed several recoveries using sdk-tools but I cannot erase any recoveries. I receive an error. I have tried several things and am at a loss to as what is the most recent way if there is one. Looking for someone with more experience then I to guide me. I previously rooted my EVO 4g and EVO 3d and was away from internet for about 9 months so I mistook the old Motorola Photon for the Photon Q. Didn't realize till way later that I was trying some rooting techniques intended for the old photon on my photon q. Anyways I feel a bit lost. Any help would be greatly appreciated. I can provide any information requested. Will be monitoring this thread all day today and will provide quick responses. Cheers!
Uhm... You tried the rooting steps for the Photon?
I really hope you didn't brick your device - that is a SURE fire way to do it tho.
Anyhoo, why haven't you just tried the official unlock from Moto?
arrrghhh said:
Uhm... You tried the rooting steps for the Photon?
I really hope you didn't brick your device - that is a SURE fire way to do it tho.
Anyhoo, why haven't you just tried the official unlock from Moto?
Click to expand...
Click to collapse
I did try that first. And successfully as far as I know because my bootloader says unlocked. I then went to install supersu and It won't install su binary. Tried to force install su binary and that did not work either. Any ideas? I joined the military so I was busy for 9 months straight. Honestly I'm usually more up to date than that. I think it's an understandable mistake and I understand the risks behind rooting. I bricked my first phone 7 years ago and brought it back using putty.
sent17inel said:
I did try that first. And successfully as far as I know because my bootloader says unlocked. I then went to install supersu and It won't install su binary. Tried to force install su binary and that did not work either. Any ideas? I joined the military so I was busy for 9 months straight. Honestly I'm usually more up to date than that. I think it's an understandable mistake and I understand the risks behind rooting. I bricked my first phone 7 years ago and brought it back using putty.
Click to expand...
Click to collapse
You didn't truly brick the device if you were able to bring it back using putty...
Regardless, you should always be careful with anything you do. Why are you trying to install the SuperSU binary right after unlocking? You need to flash a custom recovery first.
Or do you already have a custom recovery? I'm kinda lost here, you seemed to indicate you were unable to get a custom recovery flashed, but you're trying to force SuperSU without a custom recovery...?
arrrghhh said:
You didn't truly brick the device if you were able to bring it back using putty...
Regardless, you should always be careful with anything you do. Why are you trying to install the SuperSU binary right after unlocking? You need to flash a custom recovery first.
Or do you already have a custom recovery? I'm kinda lost here, you seemed to indicate you were unable to get a custom recovery flashed, but you're trying to force SuperSU without a custom recovery...?
Click to expand...
Click to collapse
Soft bricked . . . I tried to flash a custom recovery. I Tried 2. CW and another one that I can't remember at the moment. They both said they flashed successfully but I was unable to boot into any of them. I got the android with an exclamation mark. I tried to erase them and it gave me an error. Some kind of permission error. I did this all a few days ago. Decided to take a break. Honestly "you should always be careful with anything you do" . . did that really need to be said?
sent17inel said:
Honestly "you should always be careful with anything you do" . . did that really need to be said?
Click to expand...
Click to collapse
Hey, I'm not trying to force SuperSU to apply without a custom recovery here... one step at a time is all I'm trying to say.
Let's get on with it...
sent17inel said:
Soft bricked . . . I tried to flash a custom recovery. I Tried 2. CW and another one that I can't remember at the moment. They both said they flashed successfully but I was unable to boot into any of them. I got the android with an exclamation mark. I tried to erase them and it gave me an error. Some kind of permission error. I did this all a few days ago. Decided to take a break.
Click to expand...
Click to collapse
So you haven't been able to flash a custom recovery. When you flash, it says successful? Perhaps try again. Follow the directions carefully.
arrrghhh said:
Hey, I'm not trying to force SuperSU to apply without a custom recovery here... one step at a time is all I'm trying to say.
Let's get on with it...
So you haven't been able to flash a custom recovery. When you flash, it says successful? Perhaps try again. Follow the directions carefully.
Click to expand...
Click to collapse
I did try again about 5 minutes ago. It says that it won't unlock because it's already unlocked.
I got into the stock recovery. adb reboot recovery and then it will display a green android laying down with a red exclamation point. From there I hit both volume keys and it brings up the stock recovery menu. I should be able to go from here. I think the Update I did changed some things that caused the CW recovery to not flash right or to be rewritten before I can boot into it. I should be good now. Thank you for your help.
sent17inel said:
I got into the stock recovery. adb reboot recovery and then it will display a green android laying down with a red exclamation point. From there I hit both volume keys and it brings up the stock recovery menu. I should be able to go from here. I think the Update I did changed some things that caused the CW recovery to not flash right or to be rewritten before I can boot into it. I should be good now. Thank you for your help.
Click to expand...
Click to collapse
So you managed to flash custom recovery? I didn't mean to say you should try to unlock again - I meant you should try flashing recovery again (CWM, TWRP).
arrrghhh said:
So you managed to flash custom recovery? I didn't mean to say you should try to unlock again - I meant you should try flashing recovery again (CWM, TWRP).
Click to expand...
Click to collapse
With the over the air update it installs a shell script that forces the install of the stock recovery. When you reboot into the stock recovery you are presented with an image that looks like it has failed (android laying down with stomach open and a red exclamation point over it.) it will not do anything from here and eventually time out and reboot itself. If when it is at this image you press both volume keys you will be presented with a Recovery menu. I can take it from here. Thank you.
sent17inel said:
With the over the air update it installs a shell script that forces the install of the stock recovery. When you reboot into the stock recovery you are presented with an image that looks like it has failed (android laying down with stomach open and a red exclamation point over it.) it will not do anything from here and eventually time out and reboot itself. If when it is at this image you press both volume keys you will be presented with a Recovery menu. I can take it from here. Thank you.
Click to expand...
Click to collapse
Ok... Good luck.
Thread moved. Please post in the correct forum sections in future. All questions belong here in Q&A.
Thanks
AvRS
unlocking nd rooting visuals
can someone who owns Photon Q 4G LTE do a visual on rooting nd unlocking the bootloader cause was thinking bout getting this phone & dont wanna brick the phone i have read the guide's nd done tons of reseaching but found no visual's on how to do it can someone help pls?
thanks in advance
1300 said:
can someone who owns Photon Q 4G LTE do a visual on rooting nd unlocking the bootloader cause was thinking bout getting this phone & dont wanna brick the phone i have read the guide's nd done tons of reseaching but found no visual's on how to do it can someone help pls?
thanks in advance
Click to expand...
Click to collapse
Well, I was going to ask you where you are stuck in the process, but it sounds like you haven't even purchased the device yet...
I wouldn't worry about unlocking and rooting until the device is in your hands. We can help out a lot easier when you actually have the thing, hahaha.
To answer your question, I don't think there's any visuals because it's not a very visual thing. fastboot is anything but visually-appealing, and the process is rather dry. Just follow the steps carefully and you'll be fine. It's very straightforward.
Plus you must decide if you prefer to keep the bootloader LOCKED or UNLOCKED and still have root access. Research the differences in the two.
The only thing simple is the belief in simplicity.
Similar problem
Hey, I have similar problem here
I tried to root my phone using howtos on internet, but when I flash cwm img (first try from howtos, second try from CWM page), it take only a second (in every howto is it should take few minutes). But it returns that cwm was flashed sucessfully. Still.... its weird.
Then - when I want to reboot to CWM, I can see only that dead poor green thing. I tried to upload the superuser zip from here, but it returns "signature verification failed".
I still belive, there IS CWM recovery, because img was flashed sucessfully (or am I wrong?) so i tried to reboot to CWM via adb.
And another problem has appeared. ADB doesn`t recognise my phone. I installed the newest drivers from moto pages (USB drivers bit 4.7.1 and DeviceManager 2.3.4) have USB debugging mod ON, restarted my computer (win7 64bit), tried stand on my head, kill black ****.... it still returns "device not found".
Any ideas how to get to the next step? Functional adb would be great...
How long took you to flash cwm image?
Thx
D.Eternity said:
Hey, I have similar problem here
I tried to root my phone using howtos on internet, but when I flash cwm img (first try from howtos, second try from CWM page), it take only a second (in every howto is it should take few minutes). But it returns that cwm was flashed sucessfully. Still.... its weird.
Then - when I want to reboot to CWM, I can see only that dead poor green thing. I tried to upload the superuser zip from here, but it returns "signature verification failed".
I still belive, there IS CWM recovery, because img was flashed sucessfully (or am I wrong?) so i tried to reboot to CWM via adb.
And another problem has appeared. ADB doesn`t recognise my phone. I installed the newest drivers from moto pages (USB drivers bit 4.7.1 and DeviceManager 2.3.4) have USB debugging mod ON, restarted my computer (win7 64bit), tried stand on my head, kill black ****.... it still returns "device not found".
Any ideas how to get to the next step? Functional adb would be great...
How long took you to flash cwm image?
Thx
Click to expand...
Click to collapse
Let's take a step back here.
If you DON'T have ADB, you're NOT going to be able to flash CWM.
Make sure you establish an ADB connection BEFORE trying to flash again.
Good luck.
arrrghhh said:
Let's take a step back here.
If you DON'T have ADB, you're NOT going to be able to flash CWM.
Make sure you establish an ADB connection BEFORE trying to flash again.
Good luck.
Click to expand...
Click to collapse
Ok, but when I ask for fastboot devices, it returns my device (and I can work with fastboot commands). When I type adb device, it returns empty list. How is it possible?
D.Eternity said:
Ok, but when I ask for fastboot devices, it returns my device (and I can work with fastboot commands). When I type adb device, it returns empty list. How is it possible?
Click to expand...
Click to collapse
fastboot and adb are kind of separate things...
You can't access adb when the phone is in fastboot mode, and you can't access fastboot when the phone is in recovery or booted into a ROM. However, in recovery or when booted adb should work. If it's still failing make sure you're using the factory USB cable. Also, try a different port or computer.
Good luck.
arrrghhh said:
fastboot and adb are kind of separate things...
You can't access adb when the phone is in fastboot mode, and you can't access fastboot when the phone is in recovery or booted into a ROM. However, in recovery or when booted adb should work. If it's still failing make sure you're using the factory USB cable. Also, try a different port or computer.
Good luck.
Click to expand...
Click to collapse
I know fastboot and adb are separate things, this is why I assumed cwm recovery image was flashed succesfully (despite it took only a few seconds). Now I`m trying to get into CWM, but when my phone is plugged (standard mode), adb reboot recovery returns Device not found. I haven`t the original cable here, but in the office (where I have motorola cable) it was the same. Truth is both my computers are Win7 64bit. Is it possible adb has problem with 64bit system?
Thank you for helping me
hey , my nexus 5 is dead / ith stuck on boot animation i tried to flash stock rom, format, and tried to intall recovey again
but when i installed the recovery the nexus stuck on the recovery screen (http://www.zaerr.com/images/KindleFire/TeamWinLogo.jpg)
and when i tried to get in the recovery thats what it do (http://i49.tinypic.com/nlr5g2.jpg)
i think that i tried everything, and i think that the memory is dead anyone know where can i order memory 32GB
First, this is the wrong section. It should be in the Q&A section, as this is not development.
Secondly, the image you posted of being in recovery looks like the stock recovery. Have you tried playing with the volume up and power button to get the recovery menu to load?
Do you have access to the bootloader still? If so, have tried using fastboot to fully restore the device to stock? Like downloading the factory image from Google and then running flash-all.
davehasninjas said:
First, this is the wrong section. It should be in the Q&A section, as this is not development.
Secondly, the image you posted of being in recovery looks like the stock recovery. Have you tried playing with the volume up and power button to get the recovery menu to load?
Do you have access to the bootloader still? If so, have tried using fastboot to fully restore the device to stock? Like downloading the factory image from Google and then running flash-all.
Click to expand...
Click to collapse
yes i did and tried this
i tried to get in from bootloader
So what happens when you try to load the bootloader?
davehasninjas said:
First, this is the wrong section. It should be in the Q&A section, as this is not development.
Secondly, the image you posted of being in recovery looks like the stock recovery. Have you tried playing with the volume up and power button to get the recovery menu to load?
Do you have access to the bootloader still? If so, have tried using fastboot to fully restore the device to stock? Like downloading the factory image from Google and then running flash-all.
Click to expand...
Click to collapse
davehasninjas said:
So what happens when you try to load the bootloader?
Click to expand...
Click to collapse
the boot loader is open everything good, but if i want to load the recovery i can't
daniel578 said:
the boot loader is open everything good, but if i want to load the recovery i can't
Click to expand...
Click to collapse
I think you should try to keep it simple and use a tool like WugFresh for Nexus 5. I believe that it's posted in the Android Development section. You can put your phone back to stock settings just by booting up into your bootloader and running the WugFresh app. Sounds like it will be a little simpler than using adb cmd/terminal commands
daniel578 said:
the boot loader is open everything good, but if i want to load the recovery i can't
Click to expand...
Click to collapse
resident0915 said:
I think you should try to keep it simple and use a tool like WugFresh for Nexus 5. I believe that it's posted in the Android Development section. You can put your phone back to stock settings just by booting up into your bootloader and running the WugFresh app. Sounds like it will be a little simpler than using adb cmd/terminal commands
Click to expand...
Click to collapse
Agreed, I was going to recommend using fastboot to flash back, but if there's an up to date tool, it may be easier for you to use that.
If your storage were genuinely fried you more than likely wouldn't be able to access the bootloader. Unfortunately, the storage is soldiered on so there is no replacing it even if it were fried, you would have to replace the entire motherboard which you could possibly get on eBay.