Related
When I saw the port for ICS come out I got really excited and flashed it right away. Then I realized for whatever reason I didnt have SU permissions so I couldn't tether to my computer. I was disappointed but I thought, "no biggie, I'll just restore from my back up." When I flashed my back up the SU app was in my app drawer but I still couldn't tether. As a matter of fact I can't do anything that requires SU but the bootloader still reads unlocked. WTF?
I can't flash a new recovery either. I tried installing from ROM manager, I tried pushing it from my computer but I can't get to the recovery any more. ROM manager says that I have CWM 5.0.2.0 currently installed but I can't get to it at all. Again, WTF?
Sent from my Nexus S 4G using XDA App
^clearly the phone is working perfectly fine with the stock ROM from the back up but obviously I want my SU back.
Root your phone and read the development thread versus making blog posts.
Sent from my Nexus S 4G using xda premium
Flash this http://www.tylerwatt12.com/XDA/ics/root_and_theme.zip and please post in right section
Sent from my Nexus S 4G using xda premium
Thanks for not answering my questions. The bootloader is unlocked but I don't have root and I don't have access to recovery mode even tho ROM Manager says I have Clockwork Mod 5.0.2.0 currently installed. I cannot access the recovery mode AT ALL. I cannot flash or push a new recovery but it fully boots into Gingerbread w/o any issues. What is wrong with my phone and how do I fix it.
Sent from my Nexus S 4G using XDA App
Try from rom manager to reinstall a previous recovery version.
Sent from my LG-P920 using XDA App
That doesn't work either. It goes through the prompts but it doesn't actually reboot do the installation.
I just tried unrooting and then re - rooting but that didn't work and I think that actually wiped my phone completely. I don't even know where an SD card would get into this thing.
Sent from my Nexus S 4G using XDA App
Use adb on your computer and push a clockworkmod recovery.img. And we are trying to help u no need for the sarcasm
Sent from my Xoom using xda premium
I'm sorry but I'm just really frustrated right now. Nothing I have tried has worked. Maybe its my commands? To push that recovery image what would I type?
Sent from my Nexus S 4G using XDA App
I also I can't download that zip you linked to. Every time I try it just says failed.
Sent from my Nexus S 4G using XDA App
obsydian2k7 said:
I'm sorry but I'm just really frustrated right now. Nothing I have tried has worked. Maybe its my commands? To push that recovery image what would I type?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
I get it
Fastboot flash recovery recovery-xxxxxxxxx.img and hit enter
Sent from my Xoom using xda premium
Esteway.619 said:
I get it
Fastboot flash recovery recovery-xxxxxxxxx.img and hit enter
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Get cwm image from here CWM Recovery
Sent from my Xoom using xda premium
relock the phone then unlock it again i had the same problem
I tried relocking and unlocking again then pushed the recovery I just (finally) downloaded but it didn't work. Terminal says error cannot load 'recovery-clockwork-5.0.2.0-crespo4g.img'
Sent from my Nexus S 4G using XDA App
obsydian2k7 said:
I tried relocking and unlocking again then pushed the recovery I just (finally) downloaded but it didn't work. Terminal says error cannot load 'recovery-clockwork-5.0.2.0-crespo4g.img'
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Is that the right name of the recovery img? Try renaming it to just recovery and see if that works.
Edit: make sure your phone is in debugging mode. And uninstall then reinstall the drivers on your computer
Sent from my Nexus S 4G using xda premium
Esteway.619 said:
Is that the right name of the recovery img? Try renaming it to just recovery and see if that works.
Edit: make sure your phone is in debugging mode. And uninstall then reinstall the drivers on your computer
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
manually go into recovery with volume down and power flash the su.zip and u should be good to go that wat I did
Sent from my Nexus S 4G using xda premium
No suggestions have worked so far. It does not matter what the recovery image name is, whenever I try the flash it Terminal says that it cannot load "***.img" or if I try an install command it says that it cannot find "***.zip" I'm on a snow leopard iMac so I don't need drivers n such.
Let me pose the question like this, what would I do to completely restore the phone to factory condition and try to root it again? Like I said before, the bootloader says that it is unlocked but I do not have any root privileges, could not access the recovery I had before nor install a new recovery after having locked the unlocked the phone's bootloader again.
Sent from my Nexus S 4G using XDA App
http://forum.xda-developers.com/showpost.php?p=13773677&postcount=1
go to the link above and follow the directions for returning to stock.
find yourself a one-click root method on XDA that includes superuser, busybox, and CWM.
EDIT: Also, double check the md5 sum for the CWM .zip. use
Code:
md5 recovery-aaaaaa.img
in the terminal and make sure the output matches whatever is given on the CWM site. if they dont have one up, ask for it
NS4g one-click root app:
http://www.mediafire.com/?2jx8xtx2602hi23
this will:
unlock the bootloader
install cwm 5.0.2.0
root
No commands, no messing with pushing files manually, etc. This thing has already saved me from major headaches while restoring my phone once and I've only had it for 3 weeks lol
hp420 said:
NS4g one-click root app:
http://www.mediafire.com/?2jx8xtx2602hi23
this will:
unlock the bootloader
install cwm 5.0.2.0
root
No commands, no messing with pushing files manually, etc. This thing has already saved me from major headaches while restoring my phone once and I've only had it for 3 weeks lol
Click to expand...
Click to collapse
im assuming this is for windows. he said he has a mac so that wouldnt work for him. here this is for mac http://forum.xda-developers.com/showthread.php?t=1129759 just copy and past everything thats there in terminal
Esteway.619 said:
im assuming this is for windows. he said he has a mac so that wouldnt work for him. here this is for mac http://forum.xda-developers.com/showthread.php?t=1129759 just copy and past everything thats there in terminal
Click to expand...
Click to collapse
I missed that...my mistake
Let's start from the top. I have a razr m running the leaked 4.1.1 jb rom with the modified root that uses SuperSu instead of superuser. I went into the filesystem and swapped out my build.prop with the one from a Google galaxy nexus thinking it would allow me to download more apps from the play store. (Google wallet, etc) the phone wouldnt boot, it just locked on the motorola logo, so i went into recovery and wiped data as well as cache and tried to reinstall the jb leak, it failed because the build.prop didnt match. I fired up RSD lite and tried to fastboot back to ICS but it keeps failing on step 17/22 where its flashing the system.image.ext4. Because of the partial fastboot now the phone wont even boot to recovery, it just goes straight to the fastboot menu. If anyone could help all posts would be greatly appreciated! Thank you!
Your phone is repeatedly booting into fast boot because of the failed flash. This is normal and will continue until you have a successful flash. What version of RSD are you using? What does it say when it fails?
Sent from my XT907 using xda app-developers app
I am running RSD lite V5.7 on a windows XP SP3 machine. it says FAIL in the result box and ity fails system.image.ext4 because "phone returned FAIL"
Try RSD 6.1.4 and/or I seem to remember some people having to run as admin on XP if I'm not mistaken.
Sent from my XT907 using xda app-developers app
Incydeu said:
Try RSD 6.1.4 and/or I seem to remember some people having to run as admin on XP if I'm not mistaken.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
That did it perfectly, so glad i came to XDA before going to the verizon store and begging them not to rape my wallet! you saved my life man, youll be getting a thanks from me!
Ok, tired of waiting for the OTA KitKat update for my Nexus 7 2012 tablet, I downloaded the OTA update and sideloaded it with adb. Got a status 7 error and now it's stuck on a bootloop. Thing is, my Windows 8 laptop won't recognize the device anymore (code 43 error on device manager) when on recovery or bootloader. There's even no way to instal google's usb drivers or anything because it says the device malfunctioned. I downloaded the factory image but, obviously, can't sideload it or do anything with it.
Please give me a hand with this, I'm really desperate.
More detail would be nice. What did the bootloop go between? Had you installed any custom recovery like CWM?
Are you still able to access fastboot mode?
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
More detail would be nice. What did the bootloop go between? Had you installed any custom recovery like CWM?
Are you still able to access fastboot mode?
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Sorry, wasn't sure what you needed. The bootloop esentially goes from recovery to off and then to recovery again. I am able to go to fastboot normally (power and volume down when off).
Wanting to root the device a while ago, I unlocked it and rooted it whitout issues. Since the 4.3 update though, it was a little more difficult to root so having no time to research I just left it at that. That's all that was done to the Nexus 7. No Custom Recovery, no ROM, no nothing. Now, waiting for 3 weeks for KitKat, decided to sideload the OTA update (I did check the version was my device's version) the status 7 error appeared and all hell broke loose with the computer not recognizing the device.
Well, since you still have access to your fastboot menu, there isn't anything to worry about. Once you resolve the driver issue, you must be able to re flash the image.
Sent from my GT-S5570 using xda app-developers app
Duplicate post. Please erase.
nobody_nowhere said:
Well, since you still have access to your fastboot menu, there isn't anything to worry about. Once you resolve the driver issue, you must be able to re flash the image.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Yeah, that's what relaxes me a bit, but I can't seem to fix it for 20 hours straight. I use this for studying.
Well, I suggest using another computer (a friend's or relatives') or installing a Linux distro like ubuntu. Oses other than Windows usually don't have such problems. I suggest you download something called adb gui which as I recall did a pretty fine job of 're installing the drivers for me.
But then, please do correct me if I'm wrong... I think that you must first use the device on adb and get the drivers installed and then only can you use it by the fastboot interface.
Sent from my GT-S5570 using xda app-developers app
I used Wug nexus root toolkit to install drivers (windows 8.1) there are clear instructions (if you click manual or something similar) how to get drivers to work.
Yeah, actually I did use the toolkit when I was trying to update to KitKat. Thing is, it doesn't work since the bricking occurred.
Yeah, I'll try on another pc, and I'll keep you posted.
Thanks
Sent from my Nexus 4 using xda app-developers app
I'm having a very similar issue. Mine will try and bootup but just stays on the boot animation for as long as I could wait, 10 minutes or more. bootloader is working just fine and I should be able to use fastboot commands to resolve the issue. I'm not able to get to recovery for one reason or another, but it is updated to the latest CWM.
The trouble I am having is the same though. I cannot for the life of me get the drivers to work. I have tried it on one win8 pc, and one win7 pc. I haven't tried any of the toolkits to help with driver installation on the win8 pc yet. I also have another pc that I am going to try also has win8 on it as well. If you can get the drivers installed, please post a reply as to what you did here, and I will do the same, from what I have been able to find you and I aren't the only ones that are having this issue.
If the windows route doesn't work, I have a copy of Ubuntu that will be going on the computer to see if that resolves my issues. Also, may want to try another cord, I have a couple that are charge cords only. Once getting the drivers working it should be a very simple job.
Johnson90512 said:
I'm having a very similar issue. Mine will try and bootup but just stays on the boot animation for as long as I could wait, 10 minutes or more. bootloader is working just fine and I should be able to use fastboot commands to resolve the issue. I'm not able to get to recovery for one reason or another, but it is updated to the latest CWM.
The trouble I am having is the same though. I cannot for the life of me get the drivers to work. I have tried it on one win8 pc, and one win7 pc. I haven't tried any of the toolkits to help with driver installation on the win8 pc yet. I also have another pc that I am going to try also has win8 on it as well. If you can get the drivers installed, please post a reply as to what you did here, and I will do the same, from what I have been able to find you and I aren't the only ones that are having this issue.
If the windows route doesn't work, I have a copy of Ubuntu that will be going on the computer to see if that resolves my issues. Also, may want to try another cord, I have a couple that are charge cords only. Once getting the drivers working it should be a very simple job.
Click to expand...
Click to collapse
Since you say that you do have ubuntu I suggest using that to fix your issue.... just download and execute the command fastboot from the terminal
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
Since you say that you do have ubuntu I suggest using that to fix your issue.... just download and execute the command fastboot from the terminal
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Johnson90512 said:
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Click to expand...
Click to collapse
It pretty much cancels out any problems with drivers.
It is easy to do.
It takes 5 minutes to boot up and test? Try it for yourself
Sent from my Nexus 5
Johnson90512 said:
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Click to expand...
Click to collapse
If I did have any driver issues, the first thing I'd do is reinstall drivers, and if necessary, Windows itself, because I like everything to be working perfectly.
But supposing that that was not an option and I needed my phone or tab real bad, ubuntu would be my first choice. Especially because the concept of installing 'drivers' doesn't exist in ubuntu.
No, that should be fine. As long as you have used terminal before and you know the basics.
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
If I did have any driver issues, the first thing I'd do is reinstall drivers, and if necessary, Windows itself, because I like everything to be working perfectly.
But supposing that that was not an option and I needed my phone or tab real bad, ubuntu would be my first choice. Especially because the concept of installing 'drivers' doesn't exist in ubuntu.
No, that should be fine. As long as you have used terminal before and you know the basics.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
I appreciate the advice, I will give it a shot this evening, and let you know if this works. I'm sure that it will.
Alright, so I got SDK up and running on Linux! It was a little bit of a pain, but it installed just fine. Once I got it all installed I was able to see the nexus 7 through fastboot! From there I was able to reinstall the bootloader. Then was able to get to recovery to do an adb push to get a rom of 4.4 on to it. 4.4 installed just fine. All problems are fixed Good suggestions guys!
hey guys
I decided to flash back to stock today and recovered my backup but it wouldn't boot so I turned the tablet off and put it into it's bootloader and tried to flash a stock image but fastboot refuses to flash anything to the tablet at all :/ i can't at this point boot into anything any help?
I can for some reason put the userdata on and off but nothing else will flash onto the tablet :S
Check out the 2nd and third post here
http://forum.xda-developers.com/showthread.php?t=2670400
Also please write down all info from bootloader and input/output from terminal when running any commands
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Check out the 2nd and third post here
http://forum.xda-developers.com/showthread.php?t=2670400
Also please write down all info from bootloader and input/output from terminal when running any commands
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah I know all the commands and stuff and how it all works I've been using fastboot and adb etc since launch of the nexus 4. There's no output the commands just stop for instance when I use the flashall.bat from the factory images it wipes everything but won't put anything actually on the tablet it just hangs at the first sending and never finishes it just hangs there.
I've tried flashing the files manually swell but again they won't go on. The only thing that does finish is userdata.img but nothing else finishes going on the tablet at all turning on the tablet it vibrates twice and just boots onto the bootloader and nothing else opens not even the recovery
EDIT: Hooooly smeg it actually started working! it's alive again
Not trying to say you don't know, but the more information you give the better your help would be
Knowing what bootloader you have and if unlocked or not will help determine proper steps
Knowing the exact input/output can help as well as knowing the os you are using
Also if tab was working 100% before the attempt to return to stock, prior recovery and rom, any other issues you have had, etc
But its fine if you don't want to post this
Next steps would be
Make sure fastboot binaries on PC are up to date
Quality USB cable
Check md5sum for files you are to flash
If manually flashing stops at sending what happens when you manually erase?
What happens if you just try and boot a recovery through fastboot?
The more info you are willing to give the better your answers will be
Best of luck
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Not trying to say you don't know, but the more information you give the better your help would be
Knowing what bootloader you have and if unlocked or not will help determine proper steps
Knowing the exact input/output can help as well as knowing the os you are using
Also if tab was working 100% before the attempt to return to stock, prior recovery and rom, any other issues you have had, etc
But its fine if you don't want to post this
Next steps would be
Make sure fastboot binaries on PC are up to date
Quality USB cable
Check md5sum for files you are to flash
If manually flashing stops at sending what happens when you manually erase?
What happens if you just try and boot a recovery through fastboot?
The more info you are willing to give the better your answers will be
Best of luck
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh I apologize if I came across as being rude it wasn't my intention
It's all ok for some strange reason on the 50th odd attempt it finally started taking the data from fastboot. for some reason before hand when I tried manually the command would just sit there as "sending recovery" or whichever i tried and wouldn't move even waited 20 mins earlier just incase. i'm not sure at all what was happening there but now it's booted and fine
Hey guys,
a few hours ago I tried flashing the new Ldroid Rom onto my Nexus 7. After flashing the rom my tablet took ages to boot up and after the bootup it said i had to enter a password to encrypt the data (i never set encryption). after entering a random password android reported that the password was right but the data corrupt and i'd have to do a factory reset. after entering twrp i realized that the device couldn't mount anything except system. i wiped/formated everything except system and tried booting into android. this time i was stuck at the google logo. after entering recovery mode again now twrp couldn't mount system and sdcard. so i formated both and now i'm here with an absolutely empty nexus 7. i tried to use adb sideload to flash a new rom but my pc doesn't recognize the device and neither does fastboot. i tried reinstalling adb and fastboot drivers, i used universal drivers, i used drivers from toolkits, i did many many pc and tablet restarts, i reinstalled android sdk several times, i used different adb/fastboot locations, i even tried using a different pc trying the same steps. no change, only thing i get is that the tablet gets recognized by the device manager as an adb/fastboot device, nothing more.
Does anyone of you know a possible sollution for my issue?
Thanks in advance
P.S.: i've been researching the internet for this issue for the past hours and couldn't find any sollutions, so please don't say stuff like "use search function"
P.P.S.: My other devices get recognized without any issues with the same cable.
I would suggest using wugs awesome software you need to make sure all partitions are wiped and repaired to which ever format you are trying to use ext4 or f2fs and through wugs you can flash new ROM through fastboot wigs has save my ass a few times one should not try to do tedious tasks after a long night of drinking hope this helps let me know if ya need more
Sent from my d2lte using XDA Free mobile app
Masterloki666 said:
I would suggest using wugs awesome software you need to make sure all partitions are wiped and repaired to which ever format you are trying to use ext4 or f2fs and through wugs you can flash new ROM through fastboot wigs has save my ass a few times one should not try to do tedious tasks after a long night of drinking hope this helps let me know if ya need more
Sent from my d2lte using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the reply.
The thing is that the device doesn't get recognized in fastboot mode by the fastboot interface. But I'll try anyways as soon as I'm at home again...
Wugss also has a option to restore soft bricked devices that should do the trick for ya if all else fails
Sent from my d2lte using XDA Free mobile app
Masterloki666 said:
Wugss also has a option to restore soft bricked devices that should do the trick for ya if all else fails
Sent from my d2lte using XDA Free mobile app
Click to expand...
Click to collapse
didn't work :/ device doesn't get recognized by fastboot but it's shown as fastboot device in the device manager
OK check verify all partitions are set and you can try to use adb and you can push a new os I believe that should work
Sent from my AOSP on Grouper using XDA Free mobile app
Masterloki666 said:
OK check verify all partitions are set and you can try to use adb and you can push a new os I believe that should work
Sent from my AOSP on Grouper using XDA Free mobile app
Click to expand...
Click to collapse
how can i do that?
http://forum.xda-developers.com/showthread.php?p=56749959 here's a post with syteps to fix and get you set up
Sent from my AOSP on Grouper using XDA Free mobile app
Masterloki666 said:
http://forum.xda-developers.com/showthread.php?p=56749959 here's a post with syteps to fix and get you set up
Sent from my AOSP on Grouper using XDA Free mobile app
Click to expand...
Click to collapse
Will not work as my device doesn't get recognized by fastboot.
OK are you on the latest twrp recovery if so you can go into that and enable mtp get the ROM and gapps and all other files you want to flash and drop them onto your device the only thing is it for some reason won't let you transfer zip files that's fine just rename from zip to txt
And it should work sorry for the delay in response hope that works for you lol
Sent from my d2lte using XDA Free mobile app
Excuse me I do not write good English. Today I had a similar problem. Tablet remained in bootloader and laptop does not see it
I used NRT function Back to Stock and click on Soft-Bricked / Bootloop.
Tablet runs on Lolipop
wwarrel: Dobrý:
Masterloki666 said:
OK are you on the latest twrp recovery if so you can go into that and enable mtp get the ROM and gapps and all other files you want to flash and drop them onto your device the only thing is it for some reason won't let you transfer zip files that's fine just rename from zip to txt
And it should work sorry for the delay in response hope that works for you lol
Sent from my d2lte using XDA Free mobile app
Click to expand...
Click to collapse
no I don't even if I had, it wouldn't work because I have no system on the tablet...
wwarrel said:
Excuse me I do not write good English. Today I had a similar problem. Tablet remained in bootloader and laptop does not see it
I used NRT function Back to Stock and click on Soft-Bricked / Bootloop.
Tablet runs on Lolipop
wwarrel: Dobrý:
Click to expand...
Click to collapse
Will not work because you need fastboot for it which is not working for me...
Alright I used my macbook for adb/fastboot and there it somehow recognized my device and I could use fastboot to do a factory reset. I still don't know why two independent windows systems did not recognize my Nexus 7 but I got it fixed. Anyways thanks to everyone who tried to help me in this thread!