Related
Welp, tried to root the Nexus S 4g.
On rebooting, it gets stuck at the Nexus S bootscreen, pauses, keeps going, etc.
Got CWM 3.0.0.5, and can fastboot, get into CWMRecovery.
From there, I'm at a loss. Tried to restore Nandroid backup, but it says a whole bunch of stuff, basically saying E: failed to find "cache" partition, Can't mount /cache/recovery/last_log, etc.
Tried to apply zip from CWM backup, it says "No files found."
Tried going into mounts/storage to mount USB storage, but nothing appears on desktop of either Mac or PC, so I can't get move files onto the SD card.
Now, when I just power up, it just says "Google," and there's a unlock icon at the bottom. Nothing else.
Anyone have any solutions?
Yeah stop using that old version. Of ClockworkMod recovery
Seriously use 3.0.2.4. Its in the clockwork thread in the dev section.
Sent from my Nexus S using XDA App
Would if I could, but I can't get anything on the SD card!
Trying to mount USB storage from CWM-- no drive shows up on Mac or PC for me to move stuff onto it.
Boot into fastboot by turning off phone, turn back on while holding volume rocker up. Leave it at the screen where you could select reboot, recovery etc. Download the above mentioned clockwork recovery image from the thread to your computer. Flash using fastboot command. No need to copy anything to SD card.
Sent from my Nexus S using XDA App
Having the exact same issue. Nothing appears in the nandroid folder now either after replacing the recovery image with 3.0.2.4 and I can't mount the USB storage or get anything onto the SD card. Phone won't boot. Unsure of the folder structure on this phone to try pushing a file with adb or fastboot.
Same issues here. I was able to flash CWM recovery 3.0.2.4, but when I go to "mounts and storage" and "mount USB storage", I the drive does not appear on both Mac and PC. I'd like to transfer the stock NS4G image onto the phone so I can install the zip from the sdcard...
When I try to use the command, "adb push", it can't find the SD card.
Same problem
I flashed it , and since then i cannot mount the device , i have a good image to push but the device is not opening up the storage for me to push the image.
I had the same problem. Got it all fixed up.
peabody42 said:
Welp, tried to root the Nexus S 4g.
On rebooting, it gets stuck at the Nexus S bootscreen, pauses, keeps going, etc.
Got CWM 3.0.0.5, and can fastboot, get into CWMRecovery.
From there, I'm at a loss. Tried to restore Nandroid backup, but it says a whole bunch of stuff, basically saying E: failed to find "cache" partition, Can't mount /cache/recovery/last_log, etc.
Tried to apply zip from CWM backup, it says "No files found."
Tried going into mounts/storage to mount USB storage, but nothing appears on desktop of either Mac or PC, so I can't get move files onto the SD card.
Now, when I just power up, it just says "Google," and there's a unlock icon at the bottom. Nothing else.
Anyone have any solutions?
Click to expand...
Click to collapse
I had the same problem this morning:
I posted a workaround that worked well for me in Post #35
http://forum.xda-developers.com/showthread.php?t=1072698&page=4
If it works for you click 'Thanks'
Figured it out
Alright , this is what i did to fix the problem, i booted up the system with the bad image i had, connected to wifi and downloaded the Nexus S 4G deoxed image that is out there directly from the internet to the phone. Then i moved it from the download folder to the root using file manager.
I rebooted into recovery and was able to wipe and then flash the recovery image and reboot. Once i rebooted i regained control over the usb and memory card. hope it helps you guys.
How Do I Fix "REALLY" Bricked and DEAD Nexus S4g?
All posts on this thread presuppose a working Nexus S 4g. When I use the term bricked, I mean dead. About a month ago I followed directions on one of these threads on how to easily and with one click route my jellybean running phone. For some reason the process never completed, and all I was able to accomplish was unlocking the phone. When I ran the check to see if it was truly rooted, the response showed the phone was still unrooted. About 30 days later it was deader than a brick. Somewhere I read that Jellybean on Sprint might be the culprit. Anyway, I have a dead phone. Sprint wouldn't even check it because the screen was cracked. Fortunately, I bought a new one, new to me anyway, on eBay for $37. It is still running android 2.3.7(Gingerbread), and the phone is attempting to push the Ice Cream Sandwich update. I am fighting the update until I figure out what killed my phone.
Just wondering whether there is anything I can do with my old phone, even if I only use it like an old iTouch for music and surfing via Wi-Fi. Anyone?
I attempted the one click method described here, but my desktop cannot find any devices. So it truly is dead. Comments appreciated. I have used several different cables, unsuccessfully.
sexynexy said:
All posts on this thread presuppose a working Nexus S 4g. When I use the term bricked, I mean dead. About a month ago I followed directions on one of these threads on how to easily and with one click route my jellybean running phone. For some reason the process never completed, and all I was able to accomplish was unlocking the phone. When I ran the check to see if it was truly rooted, the response showed the phone was still unrooted. About 30 days later it was deader than a brick. Somewhere I read that Jellybean on Sprint might be the culprit. Anyway, I have a dead phone. Sprint wouldn't even check it because the screen was cracked. Fortunately, I bought a new one, new to me anyway, on eBay for $37. It is still running android 2.3.7(Gingerbread), and the phone is attempting to push the Ice Cream Sandwich update. I am fighting the update until I figure out what killed my phone.
Just wondering whether there is anything I can do with my old phone, even if I only use it like an old iTouch for music and surfing via Wi-Fi. Anyone?
I attempted the one click method described here, but my desktop cannot find any devices. So it truly is dead. Comments appreciated. I have used several different cables, unsuccessfully.
Click to expand...
Click to collapse
Hi,
What method did u use to root? What thread? Cuz it may need to newest version of the recovery.
anyways...
Try charging up a battery on newer phone and put in dead phone... but instead if turning on normally, boot into recovery.
If it worked then use a back up to flash it back to stock. Assuming u were able to back it up b4 root.
If not plug into computer. See if it turns on or can go into either recovery or boat loader mode and if so perhaps computer will recognize it.
Vs Nexus S4G using tapatalk2
Hi all,
Here is my sad saga.
Today, I decided I wanted to move up to ICS. I had 2.3.4 on a Koodoo phone that I decided was ready for the brave new world of ICS (bought it off Kijiji, now running it on Rogers which means I have no option of bringing it into a shop).
Ran into some issues but some good folks saved my butt in a number of tough spots. However, my grave seems to have been dug deeper by the minute. Essentially, I have managed to upgrade to 4.0.3. but am stuck with no 3G connection, hence no phone signal. This is a HUGE issue since I require my phone for work (foolish move #1 of the night).
Here are things I have tried and the challenges I have faced thus far:
1) CWM. Have not been able to access it or install it successfully. However have somehow managed to root the device. I did it through a one-click root/CWM tool I found online but have never been able to access CWM from the recovery screen, only stock recovery.
2) Changing the radio baseband version. Fail, since I have no CWM. Or Root Explorer because...
3) I can't access the google Market as I have no data connection. And did I mention no wireless? I live out in a rural area (sad story #1). It's ethernet only, sadly
4) Also, I have very limited access to a PC. I do have one at work, but I have my own macbook. Although I could use the PC at work to try some stuff out, I can't be spending my entire day Googling for help. Seems like employers would frown greatly on it. I've already spent a solid 4 hours on the forums and Internet tonight trying to find something that works. Absolutely no dice.
5) Attempted to get back to 2.3.6. No joy. Phone won't budge from 4.0.3. and I think it has to do a huge part with no CWM.
6) Factory reset a number of times. Still stuck on 4.0.3. with no 3G connection.
7) Reset APNs to default. Still no luck. Perhaps it isn't the radio baseband after all?
8) Also tried entering and leaving airplane mode a number of times. Zero luck.
9) I have a pretty low comfort level with PCs to be honest. I am open to all instructions, as long as they are detailed and written For Dummies.
Please help. I really, truly do not know what else to do or where else to turn but the forums. I've tried everything I could think of and I'm afraid this will impact my job since I need to be in constant phone contact for work. I'm exhausted from stress and worry. I swear this will be the last time I experiment with my phone (I know I've said it before, but this time I MEAN it!)
Thank you all you kind-hearted folk out there for anything you can do to help.
first cell phone model you have and that you had changed baseband before all ... You can also try a new version of CMW in case, can also be kernel problem that uses TO in the mobile ...
So you have a nexus with barely PC access running ics minus a recovery. Good news is your in luck. You need proper tools to do the job. Easiest method is either on that Mac or at work, install the phones drivers. search Google for the fastboot binary for the operating system your using. Once the drivers are installed boot to fast boot not recovery but the screen where you choose recovery. Open a terminal on the PC and type fastboot devices. No period. Should return a serial number on the screen. Your good to go. When you download the fastboot program, put it in a folder on the PC. Also put cwm for your phone in a .img format not a .zip. That should give you a name like cwm-2.5.5.0.img. When you open the terminal, navigate to the folder with both files. After typing fastboot devices and seeing the number type fastboot flash recovery cwm-and-whatever.img
That should give you cwm.
Also you got root have you tried downloading rommanager apk from the net putting it on the sd then installing. Once it installs try to flash recovery from the app
Sent from my Galaxy Nexus using Tapatalk 2
You have to relax first lol. When you're panicky nothing gets done so calm down. Do what the guy above says. Install cwm with fast boot. First install the android sdk then get the drivers. Get fast boot file down as well. Remember that the command fastboot flash whatever varies from operating systems.
With cwm installed, do a test. Backup your efs folder , which is essentially extremely important. You would better do a nandroud backup. Then, try various radios. See if that's your issue. If not change to trying out new roms . Worse case scenario go back to your 2.3.6 rom by flashing with cwm or install cyanogen mod 7.
Best of luck
Sent from my Nexus S using Tapatalk 2
dreamsforgotten said:
So you have a nexus with barely PC access running ics minus a recovery. Good news is your in luck. You need proper tools to do the job. Easiest method is either on that Mac or at work, install the phones drivers. search Google for the fastboot binary for the operating system your using. Once the drivers are installed boot to fast boot not recovery but the screen where you choose recovery. Open a terminal on the PC and type fastboot devices. No period. Should return a serial number on the screen. Your good to go. When you download the fastboot program, put it in a folder on the PC. Also put cwm for your phone in a .img format not a .zip. That should give you a name like cwm-2.5.5.0.img. When you open the terminal, navigate to the folder with both files. After typing fastboot devices and seeing the number type fastboot flash recovery cwm-and-whatever.img
That should give you cwm.
Also you got root have you tried downloading rommanager apk from the net putting it on the sd then installing. Once it installs try to flash recovery from the app
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Follow dreamsforgotten's instructions should get you out of the problem.
And yeah, relax.
You flashed the wrong ROM. the i9020a never got 4.0.3, it went straight from 2.3.6 to 4.0.4. you flashed a ROM for the i9020/i9023. This means that you have a US modem, a problem with those in the gingerbread days is that if you toggled 3G off, you lost it.
Now, I'm not 100% sure this will fix your issue, it *will* bring you back to proper stock image for your phone. Also, keep in mind, that you are responsible for anything you do to your phone, I in no way take any responsibility.
Instructions are for windows
Start by downloading the factory image:
Factory image for your phone
(ref) https://developers.google.com/android/nexus/images
Uncompress this file, you will need the following files:
Image-sojua-imm76d.zip
bootloader-crespo-i9020xxkl1.img
radio-crespo-i9020uckj1.img
Put these all in a folder, you'll need them shortly
Now you need to connect your phone to the computer. follow this guide, part 1 ONLY:
http://forum.xda-developers.com/showthread.php?t=1007782
You should still be in the bootloader when you do the following steps, (turn phone off, press and hold the volume down, power up the phone)
Grab a copy of fastboot.exe and put it in the folder with the IMG files (PM me if you can't find one)
Now, test to make sure your phone is seen by fastboot:
Open a cmd prompt and go to the folder where the img files and fastboot are stored.
Type: fastboot devices
you should get a response like this:
C:\temp\nexus image files>fastboot devices
xxxxxxxxxxxxxxxx fastboot
(x's will be alphanumeric)
This means that fastboot can now see your device. if you get nothing, something went wrong above.. troubleshoot that.
If everything is good, start flashing:
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020uckj1.img
fastboot reboot-bootloader
fastboot -w update image-sojua-imm76d.zip
Reboot your phone and be *Very* patient with the first boot.
You should now be good.
Thanks all so very much for all the help! It was extremely helpful and really helped to get my head around things.
What I ended up doing was (for those who might be stuck in the same situation as me):
1) Wipe everything. EVERYTHING. Used fastboot into CWM to help me do that.
2) Put in Kustom Kream found here:
http://forum.xda-developers.com/showthread.php?t=1399956
3) CM9 from here:
http://download.cyanogenmod.com/?type=nightly&device=crespo
* Not super stable to be honest; I've had at least three times where my entire phone randomly shut down and went into the CM9 boot screen and was stuck there until I did a battery pull. Reinstalled each time through CWM. Hope this gets fixed soon!
I found that Kustom Kream put CWM AND rooted my phone AND had everything working in terms of radio bands, sending SMS, etc. I originally had major issues with radios but now I have KB3 although the signal is kind of weak. Maybe because I live in a relatively far out suburban area?
But this solved my problems. Good luck to anyone out there stuck where I am, I feel your pain!
I would recommend that you at least flash a radio that is designed to work with your model - ucjk. That way you won't have any issues if you toggle to 2G.
Sent from my Galaxy Nexus
Hello, so it looks like i screwed up here and got ripped of on ebay. I bought a nexus i9020t for a friend at work to bring back to india.
The seller said it had a rom install badly on it, but it could still get into the bootloader. He claimed with some effort it was likely fixable..which me and 33 other bidders agreed (*dumb move*)
Unfortunately with some further research I think this phone is having the eemc problem where it can't read its internal memory. It is stuck on the google boot screen, but bootload is accessible. When i go to look in the sdcard from recovery, it can't mount it.
"Fastboot oem unlock" won't work and from what i read, its because its trying to wipe the internal memory..but it can't access it, it freezes and when i boot back into bootloader its still locked. Also the phone boots into android every once in a blue moon, like after 20 battery pulls it will boot into 2.3.4. I've tried Wugs tool to try unlock to no avail, driver setup checks out according to the UI.
I need to unlock the bootloader to do anything, i even need to unlock bootloader to put on clockwork mod. Anyone know of a .zip package that will install clockworkmod, so i don't have to do "fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img" because that requires unlock.
Also i'm having trouble seeing the point to all this because even if I get the bootloader unlocked thats not going to help a hardward problem.
The fact it boots into 2.3.4 on ocassion indicates to me that its freezing at boot because the internal memory..i mean if there was no rom on there it would never load jack.
So other than my clockworkmod .zip install question, anyone know if the internal sd card can be replaced? I mean ill go in there if its an actual sd card and not attached to the board or something. Need some guidence here, I see the problem around, but is there reall a solution so this?
Have you tried flashing with odin ? Mabey tick the repartition option.
Sent from my Nexus S using xda app-developers app
Yea I will do that this afternoon, also I will try using the PA drivers and Wugs tool on another machine.
I'm not sure but you could try to root the phone with the gingerbreak exploit over an adb shell. After doing this you could install ROM manager and flash cwm. The ROM manager app doesn't need an unlocked boot loader. It just needs root permissions.
After doing this you should be able to boot into cwm.. BUT I don't how it could help you with your hardware problems.
Sent from my Nexus S using xda premium
I'd get a refund. If it boots once in a blue moon, something isn't right hardware wise. It either boots or never boots, not "when it feels like it".
Yea idk i hoped the guy had just super effed up the software.
Now where i'm at is i got the bootloader unlocked using the fastboot command, i had to try serveral times, but it worked eventually.
Now i need to load something or do something that will alow me to repartition system.
Basically once bootloader was unlocked i used wugs tool to "flash stock + unroot" from "can't boot" status. It worked on recovery, bootloader ect..alle the way up until it tried to write the system, and gave an error "write failed (unable to remote write)" or something like that.
So now i'm basically tyring to get the "sabra root toolkit.zip" on the device so that i can use clockwork to partion the /system. Or some other way of partiioning /system.
But i'm having difficulty pushing files to the device because wugs tool is expecting you to be booted with usb developing on, and i can't boot.
I've tried "pushing files", and "installing .zip packages from my machine" under wugs tool, and it fails every time because adb device not found, and i think its because i'm not fully booted.
Still recommending a refund. This isn't easy to fix, it's actually not fixable by commoners.
Okiedoke here's the update, I got this puppy working. Just as I did with the "fastboot eom unlock" command, I just kept trying the wugfresh "flash stock + unroot" with the "can't boot" option checked. Several times it failed when trying to write to /system, eventually I tried and it worked. Now I havnt had a boot go bad since the fix (knock on wood) and its running jelly bean.
As for the troubles couple things I noticed
1. I don't think ABD works unless you're fully booted and you have USB debugging on.
As a result not much of wugfresh's options work, only the fastboot ones do.
So the "can't boot" option only uses fastboot so it works while in bootloader.
While the unlock option won't work, because it's trying to use ABD in the beginning.
In fact the only option that doesn't use ABD that I can think of is the cant boot.
So if youre locked like I was, you need to use the command line.
2. I think the problem was the rom the guy had on before had a full blown bad flash.
The /system and I think the bootloader was messed up as well.
Luckily sometimes the device could communicate with its storage, but most of the time it couldn't.
3. Getting the drivers right is a total pain, sometimes one set of driver will work for one thing, and fail for others.
I used two laptops and switched back and forth messing with the 3 available driver settings in wugfresh.
For my problem the pnet drivers are not an option...because you have to be booted to install them, so I just switched between signed and raw. Also the USB ports you use deffidently matter so switch between those as well, if using a desktop use only the back ports.
Here are the steps I took, unfortunately they weren't precise so I can't really say what did it.
1. Download wugfresh, do the raw driver install (if you can use another machine and do the signed driver install).
2. Download the adroid sdk.zip, and extract it.
3. Use command line and go to the tools folder in the adroid sdk folder (I forget exact path, but it's the tools folder somewhere in the extracted folder).
4. Now type "fastboot oem unlock".
5. If fastboot is working right you should get the unlock screen, choose yes.
6. Mine froze here and I had to try several times until it worked..switch back and forth between the 2 comps if you have that option.
7. Once unlocked do the wugfresh "flash stock + unroot" with the "can't boot" option checked.
8. It may fail, but again switch back and forth between machines, and USB ports, if it works then you should be good to go.
One thing I noticed is that recovery showed it couldn't mount my sdcard, but after option 7, and it failed to write the /system, my bootloader changed to a more up to date version (android laying down) and it was able to see the sdcard (which shows me the recovery/bootloader where kinda screwed up in the first place). After I tried again after that maybe 1 or 2 times writing system was successful.
Thanks for all your help I'll click thanks on all you guys.
So like the genius that I am, I decided to mess with my Nexus S 4G. Right now, my PC will not detect my phone at all (won't show up at ALL, in my Device Manager or any toolkit that I've tried). Please note I had little experience and will probably look like a complete idiot, but bare with me.
So the steps I took were as followed (my phone came already unlocked)
1.) I first installed PDANet to get my computer to recognize my phone and install the right drivers
2.) After that, I flashed the latest, stable clockwork recovery mod
3.) Then, I downloaded the Hellybean ROM and installed it via clockwork recovery mod, with no problems
4.) I downloaded the Google Apps archive and dropped it onto my sdcard
5.) I then installed the google apps zip and then it all went down hill from then
Every time I turned on my phone, the nice Cyanogen mod logo popped up, and then once it was done booting up, it popped up with two error messages:
Code:
Unfortunately, the process com.google.process.gapps has stopped.
Unfortunately, SetUp wizard has stopped.
Both of these error messages will not stop popping up and my phone is currently useless at this stage.
So, I went back into fastboot mode, and tried to fix it with these steps:
1.) I downloaded the "Factory Image "sojua" for Nexus S (850MHz version, i9020a)" images, and followed the instructions on this thread
2.) Once I flashed the bootloader image, my PC no longer detected my phone. It won't show up on my device manages (not even as an unrecognized Android 1.0 phone)
I installed the bootloader image because it was apart of the tutorial on how to do a complete factory reset, I now know that was stupid and not necessary.
So, you can obviously see I didn't know what I was doing, and what I did was quite stupid and careless. So unless you have any suggestions or want to help me, please do not patronize me, I am already mad enough at myself.
With that said, I am unable to even flash anything to my phone anymore, and I don't know what I can do. I tried using Wug's Nexus Toolkit to try and install the drivers, but it won't detect anything. On top of that, I am not sure if I have even flashed the correct bootloader image. Any help or suggestions would be very much appreciated.
Carbon131 said:
So like the genius that I am, I decided to mess with my Nexus S 4G. Right now, my PC will not detect my phone at all (won't show up at ALL, in my Device Manager or any toolkit that I've tried). Please not I had little experience and will probably look like a complete idiot, but bare with me.
So the steps I took were as followed (my phone came already unlocked)
1.) I first installed PDANet to get my computer to recognize my phone and install the right drivers
2.) After that, I flashed the latest, stable clockwork recovery mod
3.) Then, I downloaded the Hellybean ROM and installed it via clockwork recovery mod, with no problems
4.) I downloaded the Google Apps archive and dropped it onto my sdcard
5.) I then installed the google apps zip and then it all went down hill from then
Every time I turned on my phone, the nice Cyanogen mod logo popped up, and then once it was done booting up, it popped up with two error messages:
Code:
Unfortunately, the process com.google.process.gapps has stopped.
Unfortunately, SetUp wizard has stopped.
Both of these error messages will not stop popping up and my phone is currently useless at this stage.
So, I went back into fastboot mode, and tried to fix it with these steps:
1.) I downloaded the "Factory Image "sojua" for Nexus S (850MHz version, i9020a)" images, and followed the instructions on this thread
2.) Once I flashed the bootloader image, my PC no longer detected my phone. It won't show up on my device manages (not even as an unrecognized Android 1.0 phone)
I installed the bootloader image because it was apart of the tutorial on how to do a complete factory reset, I now know that was stupid and not necessary.
So, you can obviously see I didn't know what I was doing, and what I did was quite stupid and careless. So unless you have any suggestions or want to help me, please do not patronage me, I am already mad enough at myself.
With that said, I am unable to even flash anything to my phone anymore, and I don't know what I can do. I tried using Wug's Nexus Toolkit to try and install the drivers, but it won't detect anything. On top of that, I am not sure if I have even flashed the correct bootloader image flashed. Any help or suggestions would be very much appreciated.
Click to expand...
Click to collapse
Good luck. Flashed a sojua stock ROM on a sojus phone, bootloader and all. I don't know if you'll ever be able to fix this. :|
polobunny said:
Good luck. Flashed a sojua stock ROM on a sojus phone, bootloader and all. I don't know if you'll ever be able to fix this. :|
Click to expand...
Click to collapse
Hopefully someone may know what to do.
Carbon131 said:
Hopefully someone may know what to do.
Click to expand...
Click to collapse
If you can put it into download mode you might be able to use Odin with a factory image to bring it back to life.
polobunny said:
If you can put it into download mode you might be able to use Odin with a factory image to bring it back to life.
Click to expand...
Click to collapse
Yeah I can't seem to do that.
Carbon131 said:
Yeah I can't seem to do that.
Click to expand...
Click to collapse
Make sure your cable is connected when you try to put your phone in download mode. Turn off the phone, then hold both volume + and -, and press power. Continue holding volume buttons until you see download mode.
Ok, I'm an idiot. A big one.
I was looking to flash back to stock after using some lollipop roms. I was using TK's toolbox which was an extremely handy utility but in the peak of my madness, I hit lock bootloader with TWRP still installed.
Since hitting lock bootloader i'm not stuck with TWRP and it's crippled my phone since the current ROM no longer seems to be fully functional...I can't seem to download anything else from the web. Everything seems to fail.
I've tried fastboot oem unlock and it goes through the process that appears to be successful but it just boots back into TWRP and it's not unlocked. Does anyone have any suggestions or do I have a $300 paper weight. haha
Tonymhoffman said:
Ok, I'm an idiot. A big one.
I was looking to flash back to stock after using some lollipop roms. I was using TK's toolbox which was an extremely handy utility but in the peak of my madness, I hit lock bootloader with TWRP still installed.
Since hitting lock bootloader i'm not stuck with TWRP and it's crippled my phone since the current ROM no longer seems to be fully functional...I can't seem to download anything else from the web. Everything seems to fail.
I've tried fastboot oem unlock and it goes through the process that appears to be successful but it just boots back into TWRP and it's not unlocked. Does anyone have any suggestions or do I have a $300 paper weight. haha
Click to expand...
Click to collapse
Believe it or not, I have the same problem since yesterday. Its driving me mad since I'm no expert on rooting/unlocking
Phone gets detected by PC and by the toolbox but I can not unlock my phone again.
I am now stuck with TWRP and the only rom I can flash is Slimkat, all the others fail. If I hit unlock bootloader in the toolbox it goes through the process (fast) and it gives no error, boots back up to TWRP and thats it, but it is still locked
I just want it back locked and stocl CM11
Firstly, don't use toolkits. They are often the cause of issues.
Follow this thread to solve your problem: http://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
Fixed it!
Solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
PewLaserBeam said:
Fixed it!
Solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Click to expand...
Click to collapse
Damn you're lucky!
I'm having more issues because my phone won't let me download anything. It's like there is no SD card detected. I can't get that file onto my phone to flash it. Any ideas how I can do it?
I have ADB enabled and it shows up in my devices but it won't respond to adb sideload oneplusone-bootunlocker.zip
It responds to fastboot commands.. it just won't let me download anything off the net onto the device. IT will however update phone apps.. It's so damn frustrating.
Tonymhoffman said:
Damn you're lucky!
I'm having more issues because my phone won't let me download anything. It's like there is no SD card detected. I can't get that file onto my phone to flash it. Any ideas how I can do it?
I have ADB enabled and it shows up in my devices but it won't respond to adb sideload oneplusone-bootunlocker.zip
It responds to fastboot commands.. it just won't let me download anything off the net onto the device. IT will however update phone apps.. It's so damn frustrating.
Click to expand...
Click to collapse
I had this yesterday + I kept getting the message 'No OS installed'. Since it was already half 'broken', out of frustration I clicked everything and used all sorts of commands I could find (not the best idea I know :angel untill my PC detected the internal memory and then I downloaded 6-7 roms just to be sure. Slimkat was the only one without a fail.
How did you get the files over to your phone then if it wouldn't let you send them to it?
I finally got my internal memory to show up by mounting the system in the TWRP recovery.. But still getting an error that the device stopped responding or is disconnected.. However, it will let me open and view any file on the system, it just won't let me write to it.
Adb sideload did the fix for me after a while.
But it looks loke you have another problem.
Tonymhoffman said:
How did you get the files over to your phone then if it wouldn't let you send them to it?
I finally got my internal memory to show up by mounting the system in the TWRP recovery.. But still getting an error that the device stopped responding or is disconnected.. However, it will let me open and view any file on the system, it just won't let me write to it.
Click to expand...
Click to collapse
Instead of trying to sideload the unlocker zip have you tried using the adb push command?
Timma
Thanks for the reply. The solution for me was to mount the phone in TWRP. This allowed my SD card to be explored in Windows. However, it still would not allow me to copy files to the main directory and just out of frustration I quickly drag and dropped a PDF file that landed on a folder in the SD directory and it worked. Haha. So I then tried to copy the file inside another folder instead of the main directory. Success. What a headache and big ass mistake I'll never make again.
Note to self. Do not lock the bootloader with a custom recovery still installed. Ever.