Hey. Just a few days ago I learned hhow to use CWM and all that stuff (what a noob ikr). I installed CM12 and Elemental X kernel. I tried to install Xposed Framework but it did not work and ever since, my phone will not boot up properly. It shows the google logo, shuts down, shows google logo again and then it does the CM12 Boot animation but doesnt do anything after that. I have tried everything. Sadly, I did not have a backup for when this did not occur so I have 1 backup that has this error. I already tried clearing devlik cache and factory reseting from recovery but it doesnt work. I think if someone could tell me a very noob friendky way to install the stock rom would help. Very noob friendly.
Imperisum said:
Hey. Just a few days ago I learned hhow to use CWM and all that stuff (what a noob ikr). I installed CM12 and Elemental X kernel. I tried to install Xposed Framework but it did not work and ever since, my phone will not boot up properly. It shows the google logo, shuts down, shows google logo again and then it does the CM12 Boot animation but doesnt do anything after that. I have tried everything. Sadly, I did not have a backup for when this did not occur so I have 1 backup that has this error. I already tried clearing devlik cache and factory reseting from recovery but it doesnt work. I think if someone could tell me a very noob friendky way to install the stock rom would help. Very noob friendly.
Click to expand...
Click to collapse
Also, I am running Lollipop 5.1.1
Take A look at
developers.google.com/android/nexus/images
Gesendet von meinem Nexus 5 mit Tapatalk
I have, but do not understand how to do it.
Easiest way I can think of: The CM12 zip file is still on your phone. Flash it again (+ GApps) to remove Xposed again
Flashing the nightly will clear the /system partition including Xposed and overwrite it with the CM12 system again -> without Xposed. Then you should be able to boot
experience7 said:
Easiest way I can think of: The CM12 zip file is still on your phone. Flash it again (+ GApps) to remove Xposed again
Flashing the nightly will clear the /system partition including Xposed and overwrite it with the CM12 system again -> without Xposed. Then you should be able to boot
Click to expand...
Click to collapse
Yeah, not gonna work. I was being an idiot and deleted all files in download section so I can't get the nightly zip again. Should I try the CM installer from pc to android?
Nope.. Let's try to keep it as easy as possible
What recovery are you running?
experience7 said:
Nope.. Let's try to keep it as easy as possible
What recovery are you running?
Click to expand...
Click to collapse
Clockwork
First of all: Change your recovery to TWRP ( it has MTP available, so you can transfer files from the PC when you are in the recovery ). Use this tutorial: http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
After that, reboot into recovery and TWRP should appear. There, go to " Mount " and tap on " Enable MTP " or something like that. After that, go to your computer and find a ROM that works ( and gapps, if you want) , connect your phone to the computer, after that copy it to your phone. Then go to " WIPE " and swipe to do a factory reset. After that go to install, select your ROM zip and flash it. After that select " Reboot to system " and if it says something about rooting your ROM, deny it ( if you want root, you'll do it later by flashing yourself the latest SuperSU, it is explained in the link with the recovery tutorial ). This should make your phone boot again, having a new ROM installed.
SilentGTX said:
First of all: Change your recovery to TWRP ( it has MTP available, so you can transfer files from the PC when you are in the recovery ). Use this tutorial: http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
After that, reboot into recovery and TWRP should appear. There, go to " Mount " and tap on " Enable MTP " or something like that. After that, go to your computer and find a ROM that works ( and gapps, if you want) , connect your phone to the computer, after that copy it to your phone. Then go to " WIPE " and swipe to do a factory reset. After that go to install, select your ROM zip and flash it. After that select " Reboot to system " and if it says something about rooting your ROM, deny it ( if you want root, you'll do it later by flashing yourself the latest SuperSU, it is explained in the link with the recovery tutorial ). This should make your phone boot again, having a new ROM installed.
Click to expand...
Click to collapse
Err, not very noob friendly. For me at least. Have any other solutions?
Imperisum said:
Err, not very noob friendly. For me at least. Have any other solutions?
Click to expand...
Click to collapse
It is really really easy, everything is wrote up, you just have to follow those steps. This is one of the best ways to do it. It is easy, just try it.
SilentGTX said:
It is really really easy, everything is wrote up, you just have to follow those steps. This is one of the best ways to do it. It is easy, just try it.
Click to expand...
Click to collapse
Do I have to enable USB Debugging? I dont think I can enable USB Debugging if my phone is bricked.
SilentGTX said:
It is really really easy, everything is wrote up, you just have to follow those steps. This is one of the best ways to do it. It is easy, just try it.
Click to expand...
Click to collapse
Also, I tried it and it says ADB not found/ fastboot not found. I tried to install these things, but being a super noob, I don't think
I installed them correctly.
Imperisum said:
Also, I tried it and it says ADB not found/ fastboot not found. I tried to install these things, but being a super noob, I don't think
I installed them correctly.
Click to expand...
Click to collapse
Follow the steps that are in the link, everything is written over there, you don't need ADB Debugging to be activated ( you can't activate it even if you want to since your phone doesn't boot) enter fastboot ( as it is shown in the tutorial and then follow the other steps)
Imperisum said:
Also, I tried it and it says ADB not found/ fastboot not found. I tried to install these things, but being a super noob, I don't think
I installed them correctly.
Click to expand...
Click to collapse
Ok. Being that you are a super noob lol.. This could be the easiest option for you at the moment. I will give you a link to Wugs Link which should get you back to stock. But I would recommend that you learn how to use a pc to get your device back to working order in the future. Also there are tons of videos that tech you how to use adb etc. Please just read and look up tutorials and make sure you educate yourself first before diving into stuff that you are really not familiar with. Good luck...
#Team Android
SilentGTX said:
Follow the steps that are in the link, everything is written over there, you don't need ADB Debugging to be activated ( you can't activate it even if you want to since your phone doesn't boot) enter fastboot ( as it is shown in the tutorial and then follow the other steps)
Click to expand...
Click to collapse
Does it matter that my PC will not recognize my Nexus 5 when I plug it in? It says unspecified device in the add device option in control panel.
Imperisum said:
Does it matter that my PC will not recognize my Nexus 5 when I plug it in? It says unspecified device in the add device option in control panel.
Click to expand...
Click to collapse
It does matter. Go into device manager on your pc. There is probably an icon with a yellow exclamation mark, right click and go to where you can choose a driver from a list on your computer. Choose android adb composite interface.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
It does matter. Go into device manager on your pc. There is probably an icon with a yellow exclamation mark, right click and go to where you can choose a driver from a list on your computer. Choose android adb composite interface.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
But it doesn't say anything Nexus 5 related there.. F*** my life.
Imperisum said:
But it doesn't say anything Nexus 5 related there.. F*** my life.
Click to expand...
Click to collapse
OK, it sounds like you have a couple issues. No adb/fastboot and no drivers. Google 15 second adb install xda. Install that. That should solve both problems.
Sent from my Nexus 5 using XDA Free mobile app
Who cares if it's hard, not every solution is easy. Just learn and do it
Related
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
Hi geeks of this forum
I am stuck up at Fastboot mode- no boot or recovery image after i tried flashing my jz054k to JRO03E ... i was using nexus root toolkit 1.6.3. SO i happened to restore which lead to this problem. I am trying my best to get through it but all failures. PLs help me!
I love my Nexus s
Model number i9020kc1 :crying:
Him85 said:
Hi geeks of this forum
I am stuck up at Fastboot mode- no boot or recovery image after i tried flashing my jz054k to JRO03E ... i was using nexus root toolkit 1.6.3. SO i happened to restore which lead to this problem. I am trying my best to get through it but all failures. PLs help me!
I love my Nexus s
Model number i9020kc1 :crying:
Click to expand...
Click to collapse
... ... http://forum.xda-developers.com/showthread.php?p=42324740#post42324740 ... ...
Setting.Out said:
... ... http://forum.xda-developers.com/showthread.php?p=42324740#post42324740 ... ...
Click to expand...
Click to collapse
i have tried some CMW 6.x.x.x.IMG recovery types... but al failures... Unable to atleast see the home screen to do something. Only "NO BOOT OR RECOVERY IMAGE" is seen all time...
Pls Guide Me Through Proper Instruction..."Setting Out" ..pls..
Him85 said:
i have tried some CMW 6.x.x.x.IMG recovery types... but al failures... Unable to atleast see the home screen to do something. Only "NO BOOT OR RECOVERY IMAGE" is seen all time...
Pls Guide Me Through Proper Instruction..."Setting Out" ..pls..
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1766475
Download this program for your computer, follow the instructions, Flash your phone back to stock (using bricked mode), You will need to re-install a custom recovery, and then flash in the rom ect...
Make sure you do a clean flash, for ANYTHING you install on your phone..
Setting.Out said:
http://forum.xda-developers.com/showthread.php?t=1766475
Download this program for your computer, follow the instructions, Flash your phone back to stock (using bricked mode), You will need to re-install a custom recovery, and then flash in the rom ect...
Make sure you do a clean flash, for ANYTHING you install on your phone..
Click to expand...
Click to collapse
yeah had actually installed this program and have gone into this mess.. Can u guide me .....i kno w i am going kiddish in this .. but yes ofcourse for this time because i want to see my nexus back to life
Him85 said:
yeah had actually installed this program and have gone into this mess.. Can u guide me .....i kno w i am going kiddish in this .. but yes ofcourse for this time because i want to see my nexus back to life
Click to expand...
Click to collapse
1. make some coffee
2. get a comfy chair
3. read, read, read...
4. now that you have read about your issue and how to use the toolkit.. (while you are shaking your head no, and are just continuing to read only this...)
5. I am assuming that you are unlocked and have the correct drivers installed, because you already read and followed the instructions.. ;P
6. Boot into your bootloader.. (volume + and power)
7. Open the program (nexus root toolkit)
8. Plug your phone into your computer using the usb cable
9. Using the program, click the "flash to stock" (bricked) option.. If your device isn't recognized, or connected.. You missed a step while you were reading and learning about how to use the toolkit.. or if you don't have a recovery image, you need to find one, or possibly the tookit can download it for you..
10. Keep clicking "ok"
11. A black box will open on your computer.. telling you that it's fixing your phone.. your phone will reboot and you'll celebrate!!..
Now you have a restored to stock phone, without a custom recovery, it isn't rooted, but it is unlocked..
12. You want a custom phone?
13. Use the toolkit that you have now mastered.. because you read on how to do this..
14. Download the .zip files you want to install on your phone (making sure that it is for your phone, as wrong files will break your phone) transfer them to your phone...
15. You open and use the toolkit, ADVANCED/ BOOT RECOVERY... WIPE (DALVIK, CACHE, DATA)/ INSTALL ZIP(s) wiping dalvik and cache for additional installs.. ROM, then KERNEL, then ect..
16. You become addicted to flashing, thinking you can make it better, faster, better battery..
17. You break it again and re-read this, and the other forums you didn't read the first time.. and start over again.. lol..
Setting.Out said:
1. make some coffee
2. get a comfy chair
3. read, read, read...
4. now that you have read about your issue and how to use the toolkit.. (while you are shaking your head no, and are just continuing to read only this...)
5. I am assuming that you are unlocked and have the correct drivers installed, because you already read and followed the instructions.. ;P
6. Boot into your bootloader.. (volume + and power)
7. Open the program (nexus root toolkit)
8. Plug your phone into your computer using the usb cable
9. Using the program, click the "flash to stock" (bricked) option.. If your device isn't recognized, or connected.. You missed a step while you were reading and learning about how to use the toolkit.. or if you don't have a recovery image, you need to find one, or possibly the tookit can download it for you..
10. Keep clicking "ok"
11. A black box will open on your computer.. telling you that it's fixing your phone.. your phone will reboot and you'll celebrate!!..
Now you have a restored to stock phone, without a custom recovery, it isn't rooted, but it is unlocked..
12. You want a custom phone?
13. Use the toolkit that you have now mastered.. because you read on how to do this..
14. Download the .zip files you want to install on your phone (making sure that it is for your phone, as wrong files will break your phone) transfer them to your phone...
15. You open and use the toolkit, ADVANCED/ BOOT RECOVERY... WIPE (DALVIK, CACHE, DATA)/ INSTALL ZIP(s) wiping dalvik and cache for additional installs.. ROM, then KERNEL, then ect..
16. You become addicted to flashing, thinking you can make it better, faster, better battery..
17. You break it again and re-read this, and the other forums you didn't read the first time.. and start over again.. lol..
Click to expand...
Click to collapse
Hey!!
Thanks for awesome tip
I could finally do it
Thanks a ton for sparing your precious time U rock!!
odin
Him85 said:
Hi geeks of this forum
I am stuck up at Fastboot mode- no boot or recovery image after i tried flashing my jz054k to JRO03E ... i was using nexus root toolkit 1.6.3. SO i happened to restore which lead to this problem. I am trying my best to get through it but all failures. PLs help me!
I love my Nexus s
Model number i9020kc1 :crying:
Click to expand...
Click to collapse
you can try a odin file to reinstall rom.
Well, I was trying to install CM11 and did something wrong... most likely I was flashing with TWRP instead of clockworkmod recovery.
Moreover, shame on me, I did a "wipe data" or similar thing while in the confusion and now I have just the message "the device is unlocked" when booting - no access to TWRP when holding power+volume down, nothing else... am I in a dead-end? any suggestion?
Thanks in advance!
Fastboot
pippolino123 said:
Well, I was trying to install CM11 and did something wrong... most likely I was flashing with TWRP instead of clockworkmod recovery.
Moreover, shame on me, I did a "wipe data" or similar thing while in the confusion and now I have just the message "the device is unlocked" when booting - no access to TWRP when holding power+volume down, nothing else... am I in a dead-end? any suggestion?
Thanks in advance!
Click to expand...
Click to collapse
Does it go into fastboot after you see the unlock device, do you get the three icons you would normally see??
lj50036 said:
Does it go into fastboot after you see the unlock device, do you get the three icons you would normally see??
Click to expand...
Click to collapse
unfortunately not... I don't see the three icons it is stuck with the ASUS logo
nvflash
pippolino123 said:
unfortunately not... I don't see the three icons it is stuck with the ASUS logo
Click to expand...
Click to collapse
Do you have your Blob files from enabling nvflash??
lj50036 said:
Do you have your Blob files from enabling nvflash??
Click to expand...
Click to collapse
sorry don't understand what you mean. Can you please clarify. ..?
nvflash
pippolino123 said:
sorry don't understand what you mean. Can you please clarify. ..?
Click to expand...
Click to collapse
Sorry to say if you don't know what nvflash is or blobs and you don't have fastboot access.. time to send it to asus
You needed to do this first!!!!!
https://www.androidroot.mobi/nvflash-for-tegra3-transformer-tf700t/
lj50036 said:
Sorry to say if you don't know what nvflash is or blobs and you don't have fastboot access.. time to send it to asus
You needed to do this first!!!!!
https://www.androidroot.mobi/nvflash-for-tegra3-transformer-tf700t/
Click to expand...
Click to collapse
yes, I think you are right... didn't know about the nvflash stuff. Thanks either way for your help!
Well if you do send it in... When you get it back look me up... We will get your blobs off it so you can't brick it!!!!!
Sent from my One using XDA Premium 4 mobile app
lj50036 said:
Well if you do send it in... When you get it back look me up... We will get your blobs off it so you can't brick it!!!!!
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sure I will... thanks again and happy holidays
So since I feel like I have a complex problem that I can't seem to search for, I'm piggy backing this thread. It's been a year since I rooted this tablet, and I went on deployment with it. Worst ROM ever, couldn't get YouTube, WiFi was sketchy at best so I came back and it even had the OTA updater to update to a newer version, well that wouldn't load at all.
So I was in the process of trying to kill this crap ROM and upload I think CYA.. eh it's not the issue. So the first thing it asked me to do was this TWRP (which is new to me from a year ago) and I installed v2.5.0.0. When the tablet was working, that program seemed to work just fine, but when I rebooted in to RCK, it's so skewed and off center that I can't see half the screen. So when I tried to update to this new ROM, I kept getting download faults, so I figured I was stuck with this crap ROM because basically I quit trying. Well I tried to restart my tablet and this TWRP thing came up and asked if I wanted to run this (NEWVERSION).zip (I don't want to call out the development team, I'm sure their most recent update is much better) but basically it was the new version of the ROM I was running, so I let TWRP (from the loaded up tablet) to "install new zip" so I of course wiped data, cache and dalvik (I didn't save anything to this tablet, nothing to lose)
Well now, I'm stuck in the bricked mode of ASUS screen. If I hold down volume and power, I get RCK/Android/Wipe Data. I ever get the computer asking me to install new drivers, but of course it won't recognize the TF700 as a disk.
Any suggestions on how to get this thing back?
First the good news:
The page with the three icons is the bootloader menu which means you should have fastboot access to your tablet from your computer.
You can use fastboot to flash a new recovery (TWRP) and once that is installed you can flash the new rom.
So this can be fixed relatively easy, but you have to do some reading before attempting it. Done correctly this is a safe procedure. Done without understanding what you are doing could leave you with a hard brick - right now you're probably just soft bricked.
s14owner95 said:
So I was in the process of trying to kill this crap ROM and upload I think CYA.. eh it's not the issue. So the first thing it asked me to do was this TWRP (which is new to me from a year ago) and I installed v2.5.0.0. When the tablet was working, that program seemed to work just fine, but when I rebooted in to RCK, it's so skewed and off center that I can't see half the screen.
Click to expand...
Click to collapse
I am not sure what happened here. I have used TWRP since version 2.3.x and never had the problem you describe. I suspect you installed a version for a different device - not the one specific for the TF700.
Well I tried to restart my tablet and this TWRP thing came up and asked if I wanted to run this (NEWVERSION).zip (I don't want to call out the development team, I'm sure their most recent update is much better) but basically it was the new version of the ROM I was running, so I let TWRP (from the loaded up tablet) to "install new zip" so I of course wiped data, cache and dalvik.
Click to expand...
Click to collapse
Are you sure you had TWRP installed???
If I understand this correctly, you booted the tablet normally and got a notification to upgrade the STOCK rom to a newer STOCK version? TWRP would not do that - it just doesn't have the functionality to recognize a newer firmware version.
If you say you "let TWRP from the loaded up tablet to install new zip" - do you mean you were booted into Android? You were running the system? That would clinch it: Whatever you were using (and I am afraid it was ROMToolbox or some such) - it was not TWRP. TWRP is your custom recovery. You have to boot into it to use it.
Well now, I'm stuck in the bricked mode of ASUS screen. If I hold down volume and power, I get RCK/Android/Wipe Data. I ever get the computer asking me to install new drivers, but of course it won't recognize the TF700 as a disk.
Any suggestions on how to get this thing back?
Click to expand...
Click to collapse
Question: Did you unlock the tablet? Did you use the Asus Unlock Tool to unlock the bootloader or did you just root it? When you booted it up: Do you remember seeing "This device is unlocked" in tiny script in the upper left?
I assumed you were unlocked, but writing this post I developed doubt. I suspect you just rooted, downloaded ROMToolbox and tried to flash a new rom through it.
That does not work on this device. You have to unlock the bootloader, install a custom recovery and then you can flash a custom rom. Do not use ROMToolbox on this device!
So before I even attempt to explain the fastboot procedure, I have to know if you unlocked your TF700.
If not, you can't use fastboot.
Your last option then would be to pray that the stock recovery still works and flash the stock firmware.
berndblb said:
First the good news:
I am not sure what happened here. I have used TWRP since version 2.3.x and never had the problem you describe. I suspect you installed a version for a different device - not the one specific for the TF700.
Click to expand...
Click to collapse
That's a good possibility since I was trying to locate what I wanted via my phone, my laptop crashed last week, which is really the only reason I busted out this tablet, I borrowed a computer to try to get this fixed
berndblb said:
Are you sure you had TWRP installed???
If I understand this correctly, you booted the tablet normally and got a notification to upgrade the STOCK rom to a newer STOCK version? TWRP would not do that - it just doesn't have the functionality to recognize a newer firmware version.
If you say you "let TWRP from the loaded up tablet to install new zip" - do you mean you were booted into Android? You were running the system? That would clinch it: Whatever you were using (and I am afraid it was ROMToolbox or some such) - it was not TWRP. TWRP is your custom recovery. You have to boot into it to use it.
Click to expand...
Click to collapse
TWRP didn't ask me about the update, the OTA Updater built into the ROM that I installed at the beginning of the year did. After I unsuccessfully tried to install the TWRP and CYNA ROM, I rebooted and the OTA came up saying a newer version was available, once it went to reboot into recovery, TWRP came up
berndblb said:
Question: Did you unlock the tablet? Did you use the Asus Unlock Tool to unlock the bootloader or did you just root it? When you booted it up: Do you remember seeing "This device is unlocked" in tiny script in the upper left?
I assumed you were unlocked, but writing this post I developed doubt. I suspect you just rooted, downloaded ROMToolbox and tried to flash a new rom through it.
That does not work on this device. You have unlock the bootloader, install a custom recovery and then you can flash a custom rom. Do not use ROMToolbox on this device!
So before I even attempt to explain the fastboot procedure, I have to know if you unlocked your TF700.
If not, you can't use fastboot.
Your last option then would be to pray that the stock recovery still works and flash the stock firmware.
Click to expand...
Click to collapse
I know I went to the ASUS website and unlocked the tablet, it does say "This device is unlocked" at the top left once I turn on the computer.. I'm going to try to screen shot from my phone and update what TWRP looks like on the tablet in recovery
Hope this worked
s14owner95 said:
That's a good possibility since I was trying to locate what I wanted via my phone, my laptop crashed last week, which is really the only reason I busted out this tablet, I borrowed a computer to try to get this fixed
TWRP didn't ask me about the update, the OTA Updater built into the ROM that I installed at the beginning of the year did. After I unsuccessfully tried to install the TWRP and CYNA ROM, I rebooted and the OTA came up saying a newer version was available, once it went to reboot into recovery, TWRP came up
I know I went to the ASUS website and unlocked the tablet, it does say "This device is unlocked" at the top left once I turn on the computer.. I'm going to try to screen shot from my phone and update what TWRP looks like on the tablet in recovery
Click to expand...
Click to collapse
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???
berndblb said:
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???
Click to expand...
Click to collapse
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
berndblb said:
Never mind! You don't want to boot into an incompatible recovery if you can help it!
But that's good new!
Check out this post I wrote a little while back and let me know if you have questions:
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Edit: What I don't understand is how you got a notification for an OTA update.... You shouldn't if you are unlocked....
What rom are you running???
Click to expand...
Click to collapse
The ROM I was running had an "OTA Updater" which updated the ROM I was using, I don't want to blast them, but it's just not a good ROM.
So now, I was able to "fastboot devices" and it says 015d25681a481802 fastboot" It let me type the command "fastboot -i 0x05B0 flas recovery twrp.blob
But now I can't flash anything else. Like I said, I can't get the drivers to fully install so I can't mount the tablet like an external drive, I can't even get it passed the "ASUS" title page. Is there a way I can push this 4.2.1 CROMi ROM through fastboot?
s14owner95 said:
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
Click to expand...
Click to collapse
Mmmhh, your tablet may need a little deeper cleaning. Check out buster99's post (#12). His method has helped dozens recover from worse than you have right now.
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
His instructions are for the TF300. naturally you want to flash the blob for the TF700. That would get you back to a healthy stock system. Then you can again flash TWRP and through it a custom rom.
Good luck!
---------- Post added at 05:36 PM ---------- Previous post was at 05:28 PM ----------
s14owner95 said:
OK, so my computer never actually installs the drivers for the TF700, but ADB worked and I flashed TWRP 2.6.3.2 because it was the newest version, everything went through, it says OKAY and finished, it allowed me to reboot, but I still get the frozen ASUS screen and if I reboot into recovery, I still have that screwed up screen that I posted a few screen shots back. I need to download another ROM.. I have this other one on here, but I can't push the zip, I forgot how. I'm researching..
Thank you so much for the help so far
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
The ROM I was running had an "OTA Updater" which updated the ROM I was using, I don't want to blast them, but it's just not a good ROM.
So now, I was able to "fastboot devices" and it says 015d25681a481802 fastboot" It let me type the command "fastboot -i 0x05B0 flas recovery twrp.blob
But now I can't flash anything else. Like I said, I can't get the drivers to fully install so I can't mount the tablet like an external drive, I can't even get it passed the "ASUS" title page. Is there a way I can push this 4.2.1 CROMi ROM through fastboot?
Click to expand...
Click to collapse
Are you saying the twrp flash went ok?
You don't flash the rom in fastboot. You boot back into recovery, choose "Install" and select the CROMi-X zip you downloaded.
But before you do that I would seriously suggest you format your data partition. That means you have to have the downlaoded rom zip on your external card (otherwise you will erase it with the format).
So boot into TWRP, choose Wipe > Advanced > Format data
Then go back to TWRP Home, choose Install and navigate to the CromiX zip. Make sure the box "verify zip signature" is checked and flash the rom.
Do this only if you have a working recovery!!! Do not attempt with your busted one!!
You can only access the tablet in MTP (as an external drive) if your system is working. It's not - yet.
OK, so here's the lastest for me. I tried to "adb push ROM.zip ROM.zip/sdcard/" - error: device not found. I also tried "adb sideload" -error: device not found.
Also now, instead of the computer asking me to install drivers for my new device, it's registered as a "android bootloader interface" I tried to download the ASUS android USB drivers and update them, but Windows thinks my drivers are up to date.
s14owner95 said:
OK, so here's the lastest for me. I tried to "adb push ROM.zip ROM.zip/sdcard/" - error: device not found. I also tried "adb sideload" -error: device not found.
Also now, instead of the computer asking me to install drivers for my new device, it's registered as a "android bootloader interface" I tried to download the ASUS android USB drivers and update them, but Windows thinks my drivers are up to date.
Click to expand...
Click to collapse
To use ADB you have to be in your recovery or the Android system needs to run.
If you have a working recovery back - why do you want to mess with ADB unless you are familiar with it? You are treading on thin ice doing stuff without really understanding what you are doing! What's the rush?
The problem is that I don't have a working recovery back. i still have that screwed up screen that only shows a portion of TWRP. It let me push that recovery to it, but I can't see enough of the recovery to actually flash something to it..
I tried to download the drivers and push those manually, but windows doesn't recognize it
s14owner95 said:
The problem is that I don't have a working recovery back. i still have that screwed up screen that only shows a portion of TWRP. It let me push that recovery to it, but I can't see enough of the recovery to actually flash something to it..
I tried to download the drivers and push those manually, but windows doesn't recognize it
Click to expand...
Click to collapse
Your drivers are working. You need different sets of drivers for different modes: fastboot drivers, adb drivers, mtp drivers.
Your tablet shows up as a bootloader interface because it is in fastboot mode - ergo the fastboot drivers are working.
You HAVE to get a working recovery onto the tablet. It will NOT work without a recovery. To push a rom zip to the tablet is useless - the only thing working on your tablet is fastboot mode.
If the recovery flash fails, try buster99's method. That should clean all the crud off your partitions.
But you need to have the Asus firmware blob file for this! You cannot do this with any rom zip!!
Edit: You did push the correct recovery this time, did you?
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Click to expand...
Click to collapse
Did you ever try pull out the battery, reinsert, reboot system with 3 buttons combination? I got several fastboot mode as you're facing, and the system works just fine using above method.
I think you got just soft brick. Please, keep the device stay untouched until someone with such expertise to solve the problem will guide you. I think @akiratoriyama can share his bad experience bricking his lovely p500.
Wish you luck.
PS.
You must to press three buttons a bit longer, do not release it, until recovery mode appearing. Otherwise fastboot mode or blank screen showing instead.
Sent from my Optimus One using xda app-developers app
agk.ganesh said:
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Click to expand...
Click to collapse
Two years ago I bricked my phone also after using ROM manger. Though I will never ever use this or similar tools again. But at least, if I remember correctly, I could revive my phone with the "fastboot erase recovery" method http://forum.xda-developers.com/showthread.php?t=1088046. But since you failed is seems to be another problem. I am not a fastboot expert , but since you bricked your phone with ROM manager too, I wanted to share my success story with above mentioned method and installing AmonRa recovery. So maybe you will give it a second try? All I can remember is, that it is extremely important to follow the instructions exactly.
xu3sno said:
Did you ever try pull out the battery, reinsert, reboot system with 3 buttons combination? I got several fastboot mode as you're facing, and the system works just fine using above method.
I think you got just soft brick. Please, keep the device stay untouched until someone with such expertise to solve the problem will guide you. I think @akiratoriyama can share his bad experience bricking his lovely p500.
Wish you luck.
PS.
You must to press three buttons a bit longer, do not release it, until recovery mode appearing. Otherwise fastboot mode or blank screen showing instead.
Sent from my Optimus One using xda app-developers app
Click to expand...
Click to collapse
androidck said:
Two years ago I bricked my phone also after using ROM manger. Though I will never ever use this or similar tools again. But at least, if I remember correctly, I could revive my phone with the "fastboot erase recovery" method http://forum.xda-developers.com/showthread.php?t=1088046. But since you failed is seems to be another problem. I am not a fastboot expert , but since you bricked your phone with ROM manager too, I wanted to share my success story with above mentioned method and installing AmonRa recovery. So maybe you will give it a second try? All I can remember is, that it is extremely important to follow the instructions exactly.
Click to expand...
Click to collapse
Thanks @xu3sno & @androidck
I am also getting help from mukulsoni & others in Official CM11 version 10 thread.
I am able to go into the flash tool (pointed by mukulsoni, http://forum.xda-developers.com/showpost.php?p=49567169&postcount=45)
and able to go 'Select kernel to hotboot' with recovery.img (CWMod-6.4.0.6-Jan16)
But rebooting by HOME+Volume DOWN+POWER --> goes into CWM recovery of v5.0.2.0 (which i installed initially)
I am thinking, what to do next.
I will keep my progress posted here.
Thanks for listening..
agk.ganesh said:
Thanks @xu3sno & @androidck
I am also getting help from mukulsoni & others in Official CM11 version 10 thread.
I am able to go into the flash tool (pointed by mukulsoni, http://forum.xda-developers.com/showpost.php?p=49567169&postcount=45)
and able to go 'Select kernel to hotboot' with recovery.img (CWMod-6.4.0.6-Jan16)
But rebooting by HOME+Volume DOWN+POWER --> goes into CWM recovery of v5.0.2.0 (which i installed initially)
I am thinking, what to do next.
I will keep my progress posted here.
Thanks for listening..
Click to expand...
Click to collapse
Are you sure that you are booting into cwm v5.0.2.0? Version is listed at the top. If that is true, then either the flash tool failed to flash cwm v6.4.0.6, or you have chosen the wrong recovery.img. This can easily happen since they all have the same name. Try to flash it again, but make sure that you use the correct image.
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Edit: Here is a link to cm-10.1.6:
http://jenkins.androidarmv6.org/view/All/job/android/597/
Gapps already included.
Sent from my LG-P509 using Tapatalk 2
ibub said:
Are you sure that you are booting into cwm v5.0.2.0?
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Click to expand...
Click to collapse
+1
CM10.1.6 worked
ibub said:
Are you sure that you are booting into cwm v5.0.2.0? Version is listed at the top. If that is true, then either the flash tool failed to flash cwm v6.4.0.6, or you have chosen the wrong recovery.img. This can easily happen since they all have the same name. Try to flash it again, but make sure that you use the correct image.
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Edit: Here is a link to cm-10.1.6:
http://jenkins.androidarmv6.org/view/All/job/android/597/
Gapps already included.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Thanks @ibub for your helping hand.
I will check why recovery image not upgrading as expected. (I didn't manually download CWM5.xx version to my PC. I got it via ROM manager app, so i hope I haven't chosen wrong image)
Yes, I got CM10.1.6 from your link and installation went successfully and able to boot up..
But, it is very slow. (May be it will take some time?!) I will check it.
Between, @mukulsoni advised to install CWM6.xxx via CWM5.0.2.0. I will check how it goes.
mns123 said:
+1
Click to expand...
Click to collapse
Thanks.
agk.ganesh said:
Thanks @ibub for your helping hand.
I will check why recovery image not upgrading as expected. (I didn't manually download CWM5.xx version to my PC. I got it via ROM manager app, so i hope I haven't chosen wrong image)
Yes, I got CM10.1.6 from your link and installation went successfully and able to boot up..
But, it is very slow. (May be it will take some time?!) I will check it.
Between, @mukulsoni advised to install CWM6.xxx via CWM5.0.2.0. I will check how it goes.
Thanks.
Click to expand...
Click to collapse
Yeah, I chose to post that link only to make sure that your phone is healthy. Now you can install any recovery/rom that you want. If your volume keys are broken, I suggest that you flash to twrp recovery. It's touch driven.
Sent from my LG-P509 using Tapatalk 2
Thanks
ibub said:
Yeah, I chose to post that link only to make sure that your phone is healthy. Now you can install any recovery/rom that you want. If your volume keys are broken, I suggest that you flash to twrp recovery. It's touch driven.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I will try installing now new recovery and then new ROM.
Very glad to see the support from you guys... Thanks ibub and all..
[rant] NEVER EVER USE KDZ. PERIOD. :crying: [/rant]
Best of luck on your ROM journey :good:
Thanks
akiratoriyama said:
[rant] NEVER EVER USE KDZ. PERIOD. :crying: [/rant]
Best of luck on your ROM journey :good:
Click to expand...
Click to collapse
Thanks @akiratoriyama.
I have upgraded CWM recovery 6.xx through CWM 5.0.2.0 and successfully installed MukulSoni's Kitkat ROM.
And enjoying eating kitkat..
Thanks all..
Hi...i have a nexus 5 with custom rom + twrp...i tried to restore to factory setting and from that point everything went wrong...the phone restart and stuck on google logo...after alot of searching in the post i tried several things finally i install adb driver so i can see the phone on my windows. With the adb i push a new official flash rom to the phone but when i try to install it with twrp i got failed....i attached pic with the renarks i get...maybe that will help to understand the problem
I realy appreciate any help...since the phone now is stuck on google logo and i only can enter to twrp menu
Have u tried to wipe /system?
Inviato dal mio Nexus 5 utilizzando Tapatalk
polipom said:
Hi...i have a nexus 5 with custom rom + twrp...i tried to restore to factory setting and from that point everything went wrong...the phone restart and stuck on google logo...after alot of searching in the post i tried several things finally i install adb driver so i can see the phone on my windows. With the adb i push a new official flash rom to the phone but when i try to install it with twrp i got failed....i attached pic with the renarks i get...maybe that will help to understand the problem
I realy appreciate any help...since the phone now is stuck on google logo and i only can enter to twrp menu
Click to expand...
Click to collapse
just return to stock via method 1 in this THREAD
after that flash twrp using fastboot:
Code:
fastboot flash recovery \path\to\twrp-recovery.img
fastboot reboot-bootloader
and from there you can install your zips (supersu or custom rom) via twrp install menu.
ps:
if you're searching for some additional guides... see this STICKY THREAD
I use wug fresh you can even return to stock and lock your boot loader
Sent from my Nexus 5 using XDA Free mobile app
still stuck...
i try to return to stock via method 1 in above THREAD
it didnt finish install the os - pls look at the attached file
but now when i power on the phone instead of the google logo i stuck on the 4 round color of google
pls try to help...
any advice?
tnx
It looks like fastboot is having an issue with the size of the userdata.img. I would skip to method two in the linked thread and flash them all individually. Make sure that you have nothing running in the background on your PC to ensure it can handle the load.
Sent from my Nexus 5 using Tapatalk
polipom said:
any advice?
tnx
Click to expand...
Click to collapse
You need to update your version of fastboot. Older versions don't handle the large system.img. Easiest way is to Google 15 second adb install xda. Just run that.
Sent from my Nexus 9 using XDA Free mobile app
I install the android sdk driver and i think its include the updated adb fastboot...can u specify your instructions it will really help to to understand...
Tnx alot for helping me
just use it mate.
http://www.wugfresh.com/nrt/
if you are stuck on the boot animation, possibly your persist partition is corrupt. If you can use adb (usb driver installed properly, usb debugging enabled) then all you need to do is root the device and read the steps in this guide:
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
(The part of the fix for BT and wifi is optional IMHO) Once you fix the persist partition you can boot normally. Then you can reflash to stock.