My Nexus s is stuck at GOOGLE LOGO
Here is the Boot Loader Details.
Boot Loader version is : I9020XXKA3
baseband : I9020XXKB1
Locked sTate : LOCKEd
I have downloaded the stock nandroid , but not able to put it on the phone memory.
then tried to unlock the BOOT Loader in order to install Clock..Recovery , but there also after selecting Yes while Running Fastboot oem unlock , phone does not do anything.
then tried to load the file using ADB mode, but when i run adb devices , it doesnt show any device. or when i run adb remount it says "Error device not found"
Please help me get out of it.....
The order to unlock bootloader is:
download all drivers for nxs
download sdk tools
unzip sdk tools on your hdd
start a cmd prompt
navigate to the /tools folder inside sdk (if some adb files are missing get them here, they go into the /tools folder)
connect nxs via usb (enable usb debugging)
type "adb devices" in cmd (should return the device number)
type "adb reload bootloader"
after phone rebooted into fastboot mode type "fastboot oem unlock"
[without the ""s and install drivers if needed]
when i run adb devices it just shows this as shown below.. it doesnt give device serial number,although when i type adb remount it says device not found.
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
running ADB reboot says "Device not found"
although i can see in device manager as "android bootloader interface"
moreover when i run fastboot devices
it does show me my device serial number.
JUST to Emphasize I Am not able to start the phone so cant enable usb Debugging
Did you install the PDAnet drivers? I don't think your PC detects your phone correctly for this to work.
Install those drivers, hook the NS up to your PC and boot into bootloader. Running the adb and fastboot commands should work then.
Greetz
I did try try to install pdanet but it also fails eventually , and installation aborts .
I wonder when fastboot mode is detecting right it does display the interactive screen for unlocking boot loader on my phone .then could it still be driver issue
Can you confirm if adb needs "USB DEbugging enabled" which i can't do as mentioned
Yes you need USB debugging for adb
Sent from my Nexus S using Tapatalk
is there a way to enable usb debugging without phone getting started.
justsahid said:
is there a way to enable usb debugging without phone getting started.
Click to expand...
Click to collapse
If fastboot devices showed your serial number, you should be fine. Adb is for when android is up and running. You can mount the sdcard in recovery to copy the image files over for nandroid. If that doesn't work you can always flash in fastboot.
Yes but I am with Stock Recovery ,
IN order to mount SD card I need Clock work recovery and clock work recovery needs UNlocked Boot Loader
SO when I run the COmmand "Fastboot OEM Unlock"
My phone shows me one screen to choose Yes or NO
then I choose "YES" and hit the power button to unlock but then it stays there forever and never Unlocks the Boot Loader.
justsahid said:
Yes but I am with Stock Recovery ,
IN order to mount SD card I need Clock work recovery and clock work recovery needs UNlocked Boot Loader
SO when I run the COmmand "Fastboot OEM Unlock"
My phone shows me one screen to choose Yes or NO
then I choose "YES" and hit the power button to unlock but then it stays there forever and never Unlocks the Boot Loader.
Click to expand...
Click to collapse
If you do Fastboot OEM Unlock and then you wait for a while, and pull the battery, then put it back in and hold volume up + power and go back into bootloader mode, does it say LOCKED or UNLOCKED?
I waited for around 15 mins and then pulled out the battery , and then again went to boot loader it still says LOCKED.
IS it possible to execute Nandorid.zip using fastbot mode ?
Use Odin?
Sent from my Nexus S using XDA App
justsahid said:
I waited for around 15 mins and then pulled out the battery , and then again went to boot loader it still says LOCKED.
IS it possible to execute Nandorid.zip using fastbot mode ?
Click to expand...
Click to collapse
Exactly what all did you do before you tried fastboot oem unlock?
I opened the boot loader and run the command Fastboot Devices it did show me my device
then i run fastboot oem unlock , with which my phone showed up one screen confirming boot loader unlock where i chose "Yes" and hit the power button
i waited for 15 mins , tried multiple times and waited even more than an hour
nothing happens in the cmd promt neither on the phone.
Maximilian Mary said:
If fastboot devices showed your serial number, you should be fine. Adb is for when android is up and running. You can mount the sdcard in recovery to copy the image files over for nandroid. If that doesn't work you can always flash in fastboot.
Click to expand...
Click to collapse
Please help me how can i flash using fastboot I tried Fastboot update update.zip(2.3.3 official update)
it gave me following error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Justsahid - I'm in the exact same predicament as you (as of this morning). I'm still trying to figure out how to get the phone to unlock. I noticed there isn't any post regarding success or if you still have this issue
To all:
When trying to wipe data/factory reset in the recovery mode I receive the following error message:
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/blockplatform/s3c-sdhci.0/by-name/userdata
Formating Cache...
Data wipe complete
Then when I go and try to "apply update from /sdcard" is shows this message:
E:failed to mount /sdcard
I just wanted to know if those messages would indicate that the "Internal memory" is inaccessible and that all attempts to fix this issue is futile. Keep in mind, I'm also getting the same error message as Justsahid when trying to fastboot the update.
Eskaycee
Eskaycee said:
Justsahid - I'm in the exact same predicament as you (as of this morning). I'm still trying to figure out how to get the phone to unlock. I noticed there isn't any post regarding success or if you still have this issue
To all:
When trying to wipe data/factory reset in the recovery mode I receive the following error message:
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/blockplatform/s3c-sdhci.0/by-name/userdata
Formating Cache...
Data wipe complete
Then when I go and try to "apply update from /sdcard" is shows this message:
E:failed to mount /sdcard
I just wanted to know if those messages would indicate that the "Internal memory" is inaccessible and that all attempts to fix this issue is futile. Keep in mind, I'm also getting the same error message as Justsahid when trying to fastboot the update.
Eskaycee
Click to expand...
Click to collapse
I tried everything with no success...then finly I sent the phone go samsung ..as per them there was some electrical part malfunctionining so they replaced it... I hope I will get my phone back by Tuesday
Wow. That's good to know. Thanks for sharing.
Sent from my Nexus S 4G using XDA App
Time for a odin flash
I waiting????????????????????
Hello Guys,
I'm now in deep deep trouble as my Nexus 5 has got soft bricked and now stuck in a bootloop. Yesterday evening i unrooted my device, flashed everything to stock and locked the bootloader back because i was getting a really awful battery life upon rooting. Hence thought of reverting to stock. So flashed the stock image of 4.4.2 and setup my phone just like it came from a factory. Only thing i did this time was disable some Google Apps i.e Play News, Games & Magazines, Movies etc. Till midnight it was working too good with only a marginal battery drain on idle i.e 1% in 2 hrs or so.
Today morning when i woke up, i just entered the PIN code and unlocked the homescreen and then it just got stuck. I restarted my device and since then, its just stuck in a bootloop and whenever the phone tries to restart the OS, its gives numerous errors all related to Play sErvices and something like android.process.acore and Media.
I tried to factory reset by going through the stock recovery but even in that it gives the errors " Failed to mount /cache" and "Failed to mount /cache/recovery" with invalid arguments in the brackets.
Now i can't even flash stock as the Bootloader is in Locked State. I'm able to flash unlock Bootloader but when it asks to restart "fastboot reboot", it again gets stuck on the Google Play services error resulting again in locked state. That leaves me with a LOCKED BOOTLOADER, STOCK RECOVERY & NO USB DEBUGGING ENABLED.
What can i do now to get my device working people ? Feel like :crying: since its happened. Moreover, i can't RMA it as I'm now in a different country from where the phone wasn't purchased.
BBThumbHealer said:
Hello Guys,
I'm now in deep deep trouble as my Nexus 5 has got soft bricked and now stuck in a bootloop. Yesterday evening i unrooted my device, flashed everything to stock and locked the bootloader back because i was getting a really awful battery life upon rooting. Hence thought of reverting to stock. So flashed the stock image of 4.4.2 and setup my phone just like it came from a factory. Only thing i did this time was disable some Google Apps i.e Play News, Games & Magazines, Movies etc. Till midnight it was working too good with only a marginal battery drain on idle i.e 1% in 2 hrs or so.
Today morning when i woke up, i just entered the PIN code and unlocked the homescreen and then it just got stuck. I restarted my device and since then, its just stuck in a bootloop and whenever the phone tries to restart the OS, its gives numerous errors all related to Play sErvices and something like android.process.acore and Media.
I tried to factory reset by going through the stock recovery but even in that it gives the errors " Failed to mount /cache" and "Failed to mount /cache/recovery" with invalid arguments in the brackets.
Now i can't even flash stock as the Bootloader is in Locked State. I'm able to flash unlock Bootloader but when it asks to restart "fastboot reboot", it again gets stuck on the Google Play services error resulting again in locked state. That leaves me with a LOCKED BOOTLOADER, STOCK RECOVERY & NO USB DEBUGGING ENABLED.
What can i do now to get my device working people ? Feel like :crying: since its happened. Moreover, i can't RMA it as I'm now in a different country from where the phone wasn't purchased.
Click to expand...
Click to collapse
I had the same problem.
just download this :
http://liciousroms.com/nexus5_restore.html
and do this instructions :
INSTRUCTIONS::
1) Download and install DRIVERS
2) Download and extract Nexus_5_KOT49H_Restore.zip,
3) Turn on your phone, and connect your phone to the computer (make sure you have USB Debugging enabled on the tablet)
4) Open up folder where you extracted the Nexus_5_KOT49H_Restore.zip
5) Double Click on the "Recovery_Nexus7.bat" and follow the instructions,,,,it really is that easy! (watch video and follow along)
6) If your phone will not boot and you need to restore, boot your phone into fastboot (volume down and power) and click the "Dead_Nexus5.bat" file found in the folder
2) Download and extract Nexus_5_KOT49H_Restore.zip,
3) Turn on your phone, and connect your phone to the computer (make sure you have USB Debugging enabled on the tablet)
4) Open up folder where you extracted the Nexus_5_KOT49H_Restore.zip
5) Double Click on the "Recovery_Nexus7.bat" and follow the instructions,,,,it really is that easy! (watch video and follow along)
6) If your phone will not boot and you need to restore, boot your phone into fastboot (volume down and power) and click the "Dead_Nexus5.bat" file found in the folder
^ I can't enable USB debugging as i'm unable to boot into OS.
Guys please HELP ! I'm only looking upto XDA to rescue me out. :crying:
BBThumbHealer said:
Guys please HELP ! I'm only looking upto XDA to rescue me out. :crying:
Click to expand...
Click to collapse
Hi! Check this http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833.
Tapatalk-kal küldve az én Nexus 5-el
^ I can't enable USB debugging as i'm unable to boot into OS.
Click to expand...
Click to collapse
Read this:
6) If your phone will not boot and you need to restore, boot your phone into fastboot (volume down and power) and click the "Dead_Nexus5.bat" file found in the folder
Click to expand...
Click to collapse
And try suggested instruction. You don't even need to boot into OS.
Rip95 said:
Read this:
And try suggested instruction. You don't even need to boot into OS.
Click to expand...
Click to collapse
The tool specifically asks for Unlocked Bootloader and like i've already mentioned, its in a lock state. To unlock that, i need to have USB debugging enabled which i can't enable as i'm not able to even see the lockscreen, just stuck in a bootloop. :crying: I'm able to launch the Fastboot Mode and also partially unlock the bootloader but as soon as i type the command "fastboot reboot", the device again goes into bootloop starting the cycle again
Any more suggestions guys or should i assume my Nexus to be a paperweight ?
BBThumbHealer said:
The tool specifically asks for Unlocked Bootloader and like i've already mentioned, its in a lock state. To unlock that, i need to have USB debugging enabled which i can't enable as i'm not able to even see the lockscreen, just stuck in a bootloop. :crying: I'm able to launch the Fastboot Mode and also partially unlock the bootloader but as soon as i type the command "fastboot reboot", the device again goes into bootloop starting the cycle again
Any more suggestions guys or should i assume my Nexus to be a paperweight ?
Click to expand...
Click to collapse
Go to the stock recovery and format cache.. Do it a couple of times till the /cache errors go away and then go to the bootloader and flash the stock factory images again. After flashing the stock images, don't boot it up, head over to the stock recovery and perform a factory reset and then reboot!
The tool specifically asks for Unlocked Bootloader and like i've already mentioned, its in a lock state. To unlock that, i need to have USB debugging enabled which i can't enable as i'm not able to even see the lockscreen, just stuck in a bootloop. I'm able to launch the Fastboot Mode and also partially unlock the bootloader but as soon as i type the command "fastboot reboot", the device again goes into bootloop starting the cycle again
Click to expand...
Click to collapse
You can use command in fastboot "fastboot oem unlock" to unlock then reboot in fastboot again, and try this instruction (since you unlocked you should be able to do this).
BBThumbHealer said:
The tool specifically asks for Unlocked Bootloader and like i've already mentioned, its in a lock state. To unlock that, i need to have USB debugging enabled which i can't enable as i'm not able to even see the lockscreen, just stuck in a bootloop. :crying: I'm able to launch the Fastboot Mode and also partially unlock the bootloader but as soon as i type the command "fastboot reboot", the device again goes into bootloop starting the cycle again
Any more suggestions guys or should i assume my Nexus to be a paperweight ?
Click to expand...
Click to collapse
Here:
bitdomo said:
Hi! Check this http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833.
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
(BTW you dont have to reboot after bl unlock.
fastboot oem unlock
then flash stock images iwhtout reboot)
What? USB Debugging doesn't have to be enabled. Bootloader unlocking is done from fastboot via 'fastboot oem unlock'.
bitdomo said:
Here:
(BTW you dont have to reboot after bl unlock.
fastboot oem unlock
then flash stock images iwhtout reboot)
Click to expand...
Click to collapse
Bitdomo tried you awesome tool which gave me a slight hope that could revive my Nexus but sadly it didn't :crying: Memory size is matched 32G but userdata erase fails and at last the Download FAIL error is there I just don't know what is preventing the Cache and User Data to erase. Same is the case in Stock Recovery as well.
Can you please get me a solution on this. Would be highly obliged :good:
GldRush98 said:
What? USB Debugging doesn't have to be enabled. Bootloader unlocking is done from fastboot via 'fastboot oem unlock'.
Click to expand...
Click to collapse
BBThumbHealer said:
Bitdomo tried you awesome tool which gave me a slight hope that could revive my Nexus but sadly it didn't :crying: Memory size is matched 32G but userdata erase fails and at last the Download FAIL error is there I just don't know what is preventing the Cache and User Data to erase. Same is the case in Stock Recovery as well.
Can you please get me a solution on this. Would be highly obliged :good:
Click to expand...
Click to collapse
unlock bootloader: fastboot oem unlock DONT restart
download twrp recovery
boot twrp recovery: fastboot boot path_to_twrp_recovery.img
wait until it boots up, if the phone restarts try again.
in wipe settings select format data type yes then ok, if it winished slide the bar to factory reset.
and in cmd terminal type: adb shell then cat /proc/partitions and post the a screenshot about that.
bitdomo said:
unlock bootloader: fastboot oem unlock DONT restart
download twrp recovery
boot twrp recovery: fastboot boot path_to_twrp_recovery.img
wait until it boots up, if the phone restarts try again.
in wipe settings select format data type yes then ok, if it winished slide the bar to factory reset.
and in cmd terminal type: adb shell then cat /proc/partitions and post the a screenshot about that.
Click to expand...
Click to collapse
Successfully unlocked bootloader finally and installed TWRP. Booted in TWRP and performed Data Wipe and it failed. Again unable to mount /cache /persist /data etc commands showed. Then it tried formatting using make_ext4fs function but it failed. Swiped for a factory reset and it failed.
Used your ADB command afterwards and it displayed first daemon started successfully on port 5037 and then error in cmd : device not found.
What next ?
EDIT : Just noticed on the TWRP screen that my internal storage space is being shown as Zero (0) MB Now does this means my flash storage has died ? If that's the case and i need to RMA it, how to relock the bootloader , reset tamper flag and load stock recovery so that google doesn't cause any warranty issues. Please help me in that case as well.
EDIT 2 : Using fastboot, tried flash stock cache.img and userdata.img, it failed. When i flash system.img it went through perfectly. Also, got to know that the steps which you mentioned earlier, TWRP was booted temporarily and bootloader was unlocked temporarily. So does this means i don't need to relock or flash back something ? And, if i've unlocked and relocked the bootloader numerous times, how do i reset tamper flag ?
BBThumbHealer said:
Successfully unlocked bootloader finally and installed TWRP. Booted in TWRP and performed Data Wipe and it failed. Again unable to mount /cache /persist /data etc commands showed. Then it tried formatting using make_ext4fs function but it failed. Swiped for a factory reset and it failed.
Used your ADB command afterwards and it displayed first daemon started successfully on port 5037 and then error in cmd : device not found.
What next ?
EDIT : Just noticed on the TWRP screen that my internal storage space is being shown as Zero (0) MB Now does this means my flash storage has died ? If that's the case and i need to RMA it, how to relock the bootloader , reset tamper flag and load stock recovery so that google doesn't cause any warranty issues. Please help me in that case as well.
EDIT 2 : Using fastboot, tried flash stock cache.img and userdata.img, it failed. When i flash system.img it went through perfectly. Also, got to know that the steps which you mentioned earlier, TWRP was booted temporarily and bootloader was unlocked temporarily. So does this means i don't need to relock or flash back something ? And, if i've unlocked and relocked the bootloader numerous times, how do i reset tamper flag ?
Click to expand...
Click to collapse
Read the stickies in the general section.. It will tell you how to reset the tamper flag.
- Sent from an IceCold Hammerhead!
BBThumbHealer said:
Successfully unlocked bootloader finally and installed TWRP. Booted in TWRP and performed Data Wipe and it failed. Again unable to mount /cache /persist /data etc commands showed. Then it tried formatting using make_ext4fs function but it failed. Swiped for a factory reset and it failed.
Used your ADB command afterwards and it displayed first daemon started successfully on port 5037 and then error in cmd : device not found.
What next ?
EDIT : Just noticed on the TWRP screen that my internal storage space is being shown as Zero (0) MB Now does this means my flash storage has died ? If that's the case and i need to RMA it, how to relock the bootloader , reset tamper flag and load stock recovery so that google doesn't cause any warranty issues. Please help me in that case as well.
EDIT 2 : Using fastboot, tried flash stock cache.img and userdata.img, it failed. When i flash system.img it went through perfectly. Also, got to know that the steps which you mentioned earlier, TWRP was booted temporarily and bootloader was unlocked temporarily. So does this means i don't need to relock or flash back something ? And, if i've unlocked and relocked the bootloader numerous times, how do i reset tamper flag ?
Click to expand...
Click to collapse
You could try one more thing. Format the /presist partition, For some reason it magically fixed other's devices, like for this guy and for an other in that same thread, but if you format it you will lose your wifi and bluetooth mac address, and some kind of DRM stuff. I made a tutorial how to fix wifi and bluetoot mac address problem after the formating, but I cant tell anything about the drm kind of files, because I still didnt get answers form the guys in that thread. That could mean they are experiencing no problems. Here is the zip which formats persist partition.
BBThumbHealer said:
The tool specifically asks for Unlocked Bootloader and like i've already mentioned, its in a lock state. To unlock that, i need to have USB debugging enabled which i can't enable as i'm not able to even see the lockscreen, just stuck in a bootloop. :crying: I'm able to launch the Fastboot Mode and also partially unlock the bootloader but as soon as i type the command "fastboot reboot", the device again goes into bootloop starting the cycle again
Any more suggestions guys or should i assume my Nexus to be a paperweight ?
Click to expand...
Click to collapse
please quote for me to the next time.
just run "Dead_Nexus" and it's will do all the whole thing though the bootloader...
Aviatar2 said:
please quote for me to the next time.
just run "Dead_Nexus" and it's will do all the whole thing though the bootloader...
Click to expand...
Click to collapse
I tried all sort of things before finally giving up. Ultimately sent the device for RMA. Thanks for your inputs as well
@bitdomo, i have realised it was a case of dead memory chip only. I managed to relock the bootloader and reset the tamper flag (oem device info showed Tamper as "false") but now my only cause of concern is the LG Flash Tool. When i flashed the KOT9H firmware, it changed the original device version as mine came with 4.4 OOTB instead of 4.4.2. Can Google refuse the RMA citing this now ? Rest all, the kernel, recovery, bootloader, tamper flag is all stock. I coudn't even change that back to the original device version as i couldn't transfer any zip to the internal storage as it was dead.
BBThumbHealer said:
I tried all sort of things before finally giving up. Ultimately sent the device for RMA. Thanks for your inputs as well
@bitdomo, i have realised it was a case of dead memory chip only. I managed to relock the bootloader and reset the tamper flag (oem device info showed Tamper as "false") but now my only cause of concern is the LG Flash Tool. When i flashed the KOT9H firmware, it changed the original device version as mine came with 4.4 OOTB instead of 4.4.2. Can Google refuse the RMA citing this now ? Rest all, the kernel, recovery, bootloader, tamper flag is all stock. I coudn't even change that back to the original device version as i couldn't transfer any zip to the internal storage as it was dead.
Click to expand...
Click to collapse
Google can't get your actual device factory version, because it is only visible with lg flashtool, and that tool is an internal lg software. Google has nothing to with that tool.
By the way this lgfalsh tool makes your phone offical, because this is the offical tool used in LG service centres!!!!
Can you imagine a guy at google who takes your phone flashes a custom recovery, reads back the misc partition and search for the factory device version in the hex code. Then he checks your phone serial number and sees 310K then denies your rma request because your device factory version cant be that because in oktober 2013 there were no 4.4.2? I think no.
But if it bothers you then, you can flash krt16m, or if your nexus 5 had to do big update ~150 mb ota update then flash kfs78n if your device is D821 or flash kqs81m if your device is D820. Converted roms work too without problems I have tested them.
bitdomo said:
Google can't get your actual device factory version, because it is only visible with lg flashtool, and that tool is an internal lg software. Google has nothing to with that tool.
By the way this lgfalsh tool makes your phone offical, because this is the offical tool used in LG service centres!!!!
Can you imagine a guy at google who takes your phone flashes a custom recovery, reads back the misc partition and search for the factory device version in the hex code. Then he checks your phone serial number and sees 310K then denies your rma request because your device factory version cant be that because in oktober 2013 there were no 4.4.2? I think no.
But if it bothers you then, you can flash krt16m, or if your nexus 5 had to do big update ~150 mb ota update then flash kfs78n if your device is D821 or flash kqs81m if your device is D820. Converted roms work too without problems I have tested them.
Click to expand...
Click to collapse
I have already sent the defective one for RMA so there's no question of flashing any files now. Google sends the new replacement device and and lieu of that they block temporarily the device's price for a period of 14-21 days in which the service centre ppl check for the issues what got the device in. And i think LG only is handling that as it made the device ? So my question still remains now can the LG guys intimate Google that the phone was flashed. ? But on the positive, the flash tool was of LG and it can't be turned unofficial What say ? I don't wish to pay again for a new device. If the service centre guys gives a thumbs up that phone indeed died as a result of hardware failure like emmc chip, then the card block is removed.
BTW, i am not aware whether Google itself handles the service or asks LG to do the same! Any inputs ?
I was charging my phone when I noticed it restarted itself and then now it's stuck on the Cyanogen Logo screen.
I've gone into Recovery, pressed wipe data/factory reset but nothing actually happens. A bunch of stuff shows up saying
E:failed to mount / cache (Invalid argument)
E:Can't mount / cache / recovery /last install
E: can't open /cache recovery/last install
I tried pressing wipe cache partition, same thing
I pressed wipe media, same thing.
Reboot to bootloader, it just stuck on Fastboot logo.
I havn't done anything to the phone such as rooting or unlocking bootloader. I just left the phone as it is and only did system updates provided by Cyanogen.
Any idea?
megamonkey said:
I was charging my phone when I noticed it restarted itself and then now it's stuck on the Cyanogen Logo screen.
I've gone into Recovery, pressed wipe data/factory reset but nothing actually happens. A bunch of stuff shows up saying
E:failed to mount / cache (Invalid argument)
E:Can't mount / cache / recovery /last install
E: can't open /cache recovery/last install
I tried pressing wipe cache partition, same thing
I pressed wipe media, same thing.
Reboot to bootloader, it just stuck on Fastboot logo.
I havn't done anything to the phone such as rooting or unlocking bootloader. I just left the phone as it is and only did system updates provided by Cyanogen.
Any idea?
Click to expand...
Click to collapse
You probably have a corrupt persist partition. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/view?usp=docslist_api
You'll need to unlock your bootloader, which will wipe your device, but it's the only way. I have a guide here that explains how to unlock it (also how to install adb/fastboot and the drivers). Once you've unlocked your bootloader, put the persist file in your fastboot folder, open a command prompt from within your fastboot folder (shift + right click, then select open command prompt here), and issue these commands:
Code:
fastboot erase persist
fastboot flash persist persist.img
Once it's done flashing you can try rebooting your phone. If it still doesn't boot you'll have to go back to my guide and follow the instructions in section 8 to flash the stock images.
There's no way of saving my photos is there? I assume no...but might as well ask.
Thanks so much for the help!
megamonkey said:
There's no way of saving my photos is there? I assume no...but might as well ask.
Thanks so much for the help!
Click to expand...
Click to collapse
Unfortunately not if you can't boot into the OS.
I typed: fastboot oem unlock
It says OKAY
So when I type: fastboot oem device-info
<bootloader> Device tampered:true
<bootloader> Device unocked: false
<bootloader> Charger screen enabled: false
I assume something went wrong?
megamonkey said:
I typed: fastboot oem unlock
It says OKAY
So when I type: fastboot oem device-info
<bootloader> Device tampered:true
<bootloader> Device unocked: false
<bootloader> Charger screen enabled: false
I assume something went wrong?
Click to expand...
Click to collapse
Yeah, this happens sometimes. I can only suggest you try again in the hope that it works, without the bootloader unlocked there's gonna be nothing you can really do.
So I keep typing it till it shows true for "Device unlocked"?
I typed it 4 times now....it still doesn't say Device Unlocked True...
megamonkey said:
So I keep typing it till it shows true for "Device unlocked"?
I typed it 4 times now....it still doesn't say Device Unlocked True...
Click to expand...
Click to collapse
It isn't going to work. You're only other option is to try this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
I know you're not hard-bricked but this is likely your only chance to get the phone working again.
Heisenberg said:
It isn't going to work. You're only other option is to try this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
I know you're not hard-bricked but this is likely your only chance to get the phone working again.
Click to expand...
Click to collapse
I'll try doing all over again one last time. But I was reading the guide you gave me, it says it won't work on soft-brick, will it still work tho?
megamonkey said:
I'll try doing all over again one last time. But I was reading the guide you gave me, it says it won't work on soft-brick, will it still work tho?
Click to expand...
Click to collapse
I'm pretty sure others in similar situations to you have used it, I could be wrong.
Heisenberg said:
I'm pretty sure others in similar situations to you have used it, I could be wrong.
Click to expand...
Click to collapse
I tried using the method but I'm not sure why it isn't working. I ran the program and it gave me a few problems letting me know what's wrong with my phone:
userdata_64G.img: FAILED
boot.img: FAILED
persist.img: FAILED
recovery.img: FAILED
system.img: FAILED
I'm running near the end where nothing is going my way and I may need to either ask someone to attempt to fix it or buy a new phone...