Related
So just so I could see how the whole process worked I decided to SBF. Well, it seems to have failed. It gets to a point in the flash process where it says "Switching phone to BP pass through". It fails on this step at 99% then says FAIL on the process. So now the only way to turn it off is to pull the battery. As soon as I put the battery back in it goes to the bootloader screen and says "Code Corrupt" but down on the other part it says "OK to Program"
anyone know anything I can try? Different computer perhaps?
can you get into recovery mode?
dekend said:
can you get into recovery mode?
Click to expand...
Click to collapse
Nope, only to the bootloader.
what OS are you using? 32bit?
Have you tried another comp yet?
possible driver corruption.
I'm assuming you've tried to reflash it again. In the past back flashing Moto flip phones I've had RSD Lite fail like that also. Just took flashing it again until it finally took and was good to go. Heck I remember I was flashing a v3c to Telus software and the darn power went out in the middle of it. Took me about 10 flashes after that to get it to take as something got corrupted because the power went out in the middle of the flash. Kinda why I always flash with my laptop nowdays....lol.
dekend said:
what OS are you using? 32bit?
Have you tried another comp yet?
possible driver corruption.
Click to expand...
Click to collapse
I was using 64bit Windows 7, but I was using it in VMware. I've got 32bit XP up and running on a new machine now (not virtual) and I'm about to try with that.
Never had a problem flashing with VMs before but that may be the problem. Who knows.
mrnosox said:
I was using 64bit Windows 7, but I was using it in VMware. I've got 32bit XP up and running on a new machine now (not virtual) and I'm about to try with that.
Never had a problem flashing with VMs before but that may be the problem. Who knows.
Click to expand...
Click to collapse
VM is definitely the problem -- I had the same issue with my D1. I think it's not loading the drivers correctly when the USB mode switches between ADB Flash interface and whetever comes next. I was able to re-SBF it using native XP 32-bit, so hopefully you can, too.
The same exact thing happened to me. Turned out the problem was that i was using an old version of RSD Lite. You NEED 4.7 for it to flash correctly. I was using 4.6. As soon as I updated, I plugged in via usb while in "Code Corrupt" bootloader and reflashed. Worked fine after that.
Sent from my DROIDX using XDA App
btdownloads7 said:
VM is definitely the problem -- I had the same issue with my D1. I think it's not loading the drivers correctly when the USB mode switches between ADB Flash interface and whetever comes next. I was able to re-SBF it using native XP 32-bit, so hopefully you can, too.
Click to expand...
Click to collapse
Yep, I loaded XP on my MBP in a bootcamp parition and it flashed the first time. It's Alive!
mrnosox said:
Yep, I loaded XP on my MBP in a bootcamp parition and it flashed the first time. It's Alive!
Click to expand...
Click to collapse
Nice, glad to hear you got it back going again.
I have a question...ok my phone is rooted used easy root....ok then I download boot strap now I want go back top stock what I have to do
Sent from my DROIDX using XDA App
If you still want to use some sort of virtual software on your mac, I recommend Parallels. I have the 5.0 version and running XP on the newer generation MBP.
SBF works like a charm. I don't use Boot Camp simply because I want access to both OS's at the same time.
If you can setup a Linux box, I'd use sbf_flash. Sooooo much easier.
i seem to have a problem with mounting the internal storage on the phone, it doesnt ask me to mount when i plug the phone in like it normally would so i tried mounting through recovery but still cant do it through there, tried 3 different roms and all the same issue, are there any kernels with this issue? im running newest nscollab with the kernel it comes with...not sure what to do
are you running the latest recovery? can you use the storage space with apps on the phone?
I have been having the exact same problems. Nothing seems to work. Can't mount through CW and I have the most recent version. Randomly it started to work again by turning the phone off. Plugging phone into computer. Turning phone back on. It would recognize it until now. Now that doesn't work....
I am using Mac and Linux and neither one need drivers so that has nothing to do with it.
I'm screwed if I have to take the phone in for warranty work because I am rooted.
Anyone come up with something to fix this?
Or is there a way to "force it to mount?"
Its really f'in annoying
Sent from my Nexus S 4G using XDA App
xcolt45 said:
I have been having the exact same problems. Nothing seems to work. Can't mount through CW and I have the most recent version. Randomly it started to work again by turning the phone off. Plugging phone into computer. Turning phone back on. It would recognize it until now. Now that doesn't work....
I am using Mac and Linux and neither one need drivers so that has nothing to do with it.
I'm screwed if I have to take the phone in for warranty work because I am rooted.
Anyone come up with something to fix this?
Or is there a way to "force it to mount?"
Its really f'in annoying
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
So it's showing the storage on the phone and not on the computer, correct?
Can you select to mount the USB when you plug it in?
Does the device show up in the System Profiler app in Mac OS X?
derekwilkinson said:
So it's showing the storage on the phone and not on the computer, correct?
Can you select to mount the USB when you plug it in?
Does the device show up in the System Profiler app in Mac OS X?
Click to expand...
Click to collapse
That is incorrect. It does not show up on the phone. When it shows up on the phone it mounts to the computer. It is not even recognizing it on the phone now. For awhile it was working and now its not again. Haven't done anything else to the phone.
When it doesn't show up on my phone it is not recognized by the system profiler.
Never had a problem with any other android device except on my epic 4g when I tried running the miui beta for it. But it would still mount in clockwork.
It is not the cable because I have four different cables. One of which works flawlessly on my epic. Which had a lot of problems when using the stock cable.
Is this hardware related or is it because of the rooting process?
What r some possible fixes if any?
I really would not mind going back to stock and starting over. But the only way to get back to stock is by USB. And nothing recognizes it. Adb. Fastboot. Odin (heimdall in Mac terms) nothing recognized it
Sent from my Nexus S 4G using XDA App
xcolt45 said:
That is incorrect. It does not show up on the phone. When it shows up on the phone it mounts to the computer. It is not even recognizing it on the phone now. For awhile it was working and now its not again. Haven't done anything else to the phone.
When it doesn't show up on my phone it is not recognized by the system profiler.
Never had a problem with any other android device except on my epic 4g when I tried running the miui beta for it. But it would still mount in clockwork.
It is not the cable because I have four different cables. One of which works flawlessly on my epic. Which had a lot of problems when using the stock cable.
Is this hardware related or is it because of the rooting process?
What r some possible fixes if any?
I really would not mind going back to stock and starting over. But the only way to get back to stock is by USB. And nothing recognizes it. Adb. Fastboot. Odin (heimdall in Mac terms) nothing recognized it
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
okay, I had this issue when the nexus s 4g was first released and the first roms/recoveries came out. I would just start over. backup using titanium backup and flash the stock files in fastboot, then unlock again, flash the recoveries, etc.
How exactly would I revert to stock if commands from my computer in fastboot do not recognize the device?
Sent from my Nexus S 4G using XDA App
Try es file explorer and give root access ... this was u can atleast access files from your phone...
PROBLEM SOLVED... at least for me
Found out when flashing to a stock rom (currently running MIUI) that my usb port on my phone is loose. Just have to be careful with it. Makes sense that it was randomly happening.
With MIUI it wouldn't show right away because I had it set to auto-mount. But when i flashed the stock rom. The pop-up to mount-sd would show up and go away show up and go away....
Darn.
I put Ubuntu on my 7 using the Ubuntu desktop installer (had to do it manually, but yea...) that came out semi-recently and I want to go back to good ol' Andy so I can try out some cool USB OTG stuff I saw recently. I'm having a bit of trouble finding out how to flash Android back to it. Clockwork is gone and I tried an unbrick method and it didn't work. Anyone have any ideas?
Thanks!!
rmp5s said:
I put Ubuntu on my 7 using the Ubuntu desktop installer (had to do it manually, but yea...) that came out semi-recently and I want to go back to good ol' Andy so I can try out some cool USB OTG stuff I saw recently. I'm having a bit of trouble finding out how to flash Android back to it. Clockwork is gone and I tried an unbrick method and it didn't work. Anyone have any ideas?
Thanks!!
Click to expand...
Click to collapse
There might be a better way of doing this but I always use wug fresh's toolkit and use the flash stock button. All it requires is bootloader with required drivers. That will flash the stock android and stock recovery!
Sent from my Nexus 7 using xda app-developers app
I shall give it a shot right meow. Thanks!
Edit: HA!! That's how I rooted my N4! I already have it and everything! Didn't recognize the name. I'll let everyone know how it goes.
After getting every damn error in the world and having to do it manually-ish, I got it. Thanks! Forgot about that program!
Well.... no effing clue whats happened.... it must've updated recently as no longer rooted or using golauncher... getting rather annoyed at the inability to access the internal storage via usb...
Windows brings up a massive message that when i googled it the fix was to apparently unplug the pc.... which resolved a few issues but still get the same issues with the kindle... which sucks.... managed to connect briefly with Linux but now it just seem to not acknowledge it at all....
I had what i thought were the latest drivers as i only installed them a couple of days ago.. (rediscovered scummvm!!!)
Any ideas what I can do? I want to re root and flash a totally new rom as the amazon one is truely awful
And which is the best root method for 7.4.6? If there is one....
Thanks again peeps!
Sent from my KFTT using Tapatalk now Free
shugs81 said:
Well.... no effing clue whats happened.... it must've updated recently as no longer rooted or using golauncher... getting rather annoyed at the inability to access the internal storage via usb...
Windows brings up a massive message that when i googled it the fix was to apparently unplug the pc.... which resolved a few issues but still get the same issues with the kindle... which sucks.... managed to connect briefly with Linux but now it just seem to not acknowledge it at all....
I had what i thought were the latest drivers as i only installed them a couple of days ago.. (rediscovered scummvm!!!)
Any ideas what I can do? I want to re root and flash a totally new rom as the amazon one is truely awful
And which is the best root method for 7.4.6? If there is one....
Thanks again peeps!
Sent from my KFTT using Tapatalk now Free
Click to expand...
Click to collapse
You would probably benefit most by using KFFA to return to 7.2.3 then root, remove OTA updates and install GApps. This way when you go to install a custom ROM, you have a matching boot loader. In order to put a custom ROM on, you need to flash a 2nd boot loader and TWRP. All this is covered in great detail on here. If you have questions do ask.
Sent from my Kindle Fire HD 7 running 4.3 Paranoid Android using xda app-developers app
I recommend Paranoid Android indeed!
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!