Phone Stuck on Cyanogen Logo - ONE Q&A, Help & Troubleshooting

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...

Related

PD15IMG.zip not working Bricked Phone

I rooted my phone using the gfree method, i still have the file that saves to your phone when you perform that method. I got perm s-off with hboot 0.85.2007 I was and had been on a gorilla sense rom it was cool was working great, i already had flashed the zip that allowed me to go from clockwork 2.... to 3.... but before i went to thunderbolt rom I used trueblue_drew's updated zip the one he got from option94. I flashed the zip in recovery from clockwork 2....I did a nandroid and of the gorilla sense rom, booted back up and went into recovery again wiped data, partition and dalvik i then flashed thunderbolt from my sd card everything went through smooth. I rebooted completed the steps to set it up and was running smooth then out of nowhere my phone just turned off and went into bootloops, sowing the thunderbolt splash screen, i took off the battery and started my phone again and it wouldnt get past the first splash screen which is the initial my touch 4g splash but i had changed that screen a while back to a black screen from cynogen that reads rooted mytouch 4g with the green droid. I then took the battery out again then went into recovery by holding volume and power at this point i got the "cant mount" messages in clockwork i wiped the data but everytime it was done the "cant mount" messages would appear i tried to nandroid restore everyone i had on my sdcard and nothing worked. I tried flashing a older version of thunderbolt and nothing it just stays stuck on the first splash screen.
When i put the PD15IMG zip on my sd card it reads it then the blue status bar pops up and does its thing, it then asks me if i want to install update i press the volume button up for yes and a few seconds go by and on the first one 1.Bootloader i get the "fail PU" message and just says press power to reboot, i do and it takes me to the first splash screen and sits there.
When i am in Hboot screen and plug my phone in i see that it changes to "hboot usb plug" my system info is
sn-sh11yrmo7858
lcd-so-c2
touch panel-atmelc12_20aay
commit-7eafc656
os ver.-1.17.531.2
imei-359637039172891
cid-11111111
ram-768mb
emmc-samsung 2151mb 4407295 sectors
Like i said i have saved the part7backup file from the gfree method, and i have the clockwork folder saved everything else was wiped from my sd card.
I doubt i have adb set up correctly because i type a command and it says "the system cannot find the patch specified" Im slowly losing hope here i didnt think it was possible to brick a phone especially from what i did but i guess it is
Can you boot and get into the HBoot in your current status?
Did you check the MD5SUM of the download?
Sent from my HTC Glacier using Tapatalk
1 more thing that makes me mad ITS NOT BRICKED!!!!
if its a brick you cant get into Hboot or Recovery
anyways it should work also check if your SDCard is formatted to FAT32 (i think)
sounds like your SD card isn't formatted right or could be corrupted. you're not bricked if you can hboot
I am having the same issue, stating "it isn't bricked" without any explanation isn't very helpful. I have tried reformatting my SD card with no avail even tried a different SD card. as far as I am aware unless you have the eng-hboot there isn't a way to fix this since fastboot does not work
accido said:
I am having the same issue, stating "it isn't bricked" without any explanation isn't very helpful. I have tried reformatting my SD card with no avail even tried a different SD card. as far as I am aware unless you have the eng-hboot there isn't a way to fix this since fastboot does not work
Click to expand...
Click to collapse
If you can get into Fastboot or the Recovery Screen simply means just that it's not bricked. A truly bricked phone you cannot get into the engineering screen nor the recovery image.
On the HBoot screen can you get to recovery and access it? If so what comes up?
I dont understand the problem. it sounds like he got a bad download. If his sd was formated wrong it wouldnt load at all. oance you have clockwork installed it is impossabl to brick. You can pull your battery in the middle of a rom load and be fine
Sent from my HTC Glacier using XDA Premium App
When i hold the volume down and power it takes me into the hboot screen, if i have the PD15IMG.zip on my sdcard it automatically reads it then the blue status bar appears it loads then it asks if i want to start update, I press volume up and it fails. I noticed towards the bottom it says "Partition update fail" and under that "update fail"
I can go into recovery, ClockworkMod 3.0.0.5 recovery but i get a messages stating
E:cant mount ?cache/recovery/command
E:cant mount /cache/recovery/log
E:cant open /cache/recovery/log
E:cant mount /cache/recovery/last_log
E:cant open /cache/recovery/last_log
neidlinger said:
Can you boot and get into the HBoot in your current status?
Did you check the MD5SUM of the download?
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
TheHypebeast said:
When i hold the volume down and power it takes me into the hboot screen, if i have the PD15IMG.zip on my sdcard it automatically reads it then the blue status bar appears it loads then it asks if i want to start update, I press volume up and it fails. I noticed towards the bottom it says "Partition update fail" and under that "update fail"
I can go into recovery, ClockworkMod 3.0.0.5 recovery but i get a messages stating
E:cant mount ?cache/recovery/command
E:cant mount /cache/recovery/log
E:cant open /cache/recovery/log
E:cant mount /cache/recovery/last_log
E:cant open /cache/recovery/last_log
Click to expand...
Click to collapse
Read through this thread, their should be some guidance hidden with in the scroll.
Link
I read through it, same issue im having only that he was on .86.0000 and im on .85.2007 and he was able to fix and restore with PD15IMG and i get the partition fail
neidlinger said:
Read through this thread, their should be some guidance hidden with in the scroll.
Link
Click to expand...
Click to collapse
Try flashing it through clockwork recovery. Put the zip image in a folder then boot holding volume down and power. When you can chose options in hboot go to recovery hit trackball. You should no what to do from there
Sent from my HTC Glacier using XDA Premium App
Keep looking for a better answer, but if you find nothing you can try this. You'll need adb and fastboot working.
Find an only nandroid, and put the system.img, boot.img and recovery.img from it in your android sdk tools folder.
Reboot into hboot by pressing volume down and power.
Scroll to fastboot and press power.
then type
Code:
fastboot erase system -w
fastboot erase boot
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
Then fastboot reboot and you should be ok.
lowandbehold helped me.
http://forum.xda-developers.com/showthread.php?t=992283&highlight=rom+manager+question
After the first "fastboot erase system -w" i get "erasing system..." and it just sits there i waited for about ten minutes, how long should that first one take?
option94 said:
Keep looking for a better answer, but if you find nothing you can try this. You'll need adb and fastboot working.
Find an only nandroid, and put the system.img, boot.img and recovery.img from it in your android sdk tools folder.
Reboot into hboot by pressing volume down and power.
Scroll to fastboot and press power.
then type
Code:
fastboot erase system -w
fastboot erase boot
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
Then fastboot reboot and you should be ok.
Click to expand...
Click to collapse
TheHypebeast said:
After the first "fastboot erase system -w" i get "erasing system..." and it just sits there i waited for about ten minutes, how long should that first one take?
Click to expand...
Click to collapse
Should only take a few seconds.
You may have a hardware problem at this point.
Yeah after i waited a good ten minutes i just unplugged my phone and immediately got "FAILED <status read failed <Too many links>> finished. total time: 510.438s
option94 said:
Should only take a few seconds.
You may have a hardware problem at this point.
Click to expand...
Click to collapse
after several tries now it just fails within seconds of running "fastboot erase system -w"
How can I get my computer to recognize my phone? I can't power up and no hboot with holding down power + vol down. Please help !!
TheHypebeast said:
Yeah after i waited a good ten minutes i just unplugged my phone and immediately got "FAILED <status read failed <Too many links>> finished. total time: 510.438s
after several tries now it just fails within seconds of running "fastboot erase system -w"
Click to expand...
Click to collapse
Could the partitions be wrong somehow? I do not know how to fix that, someone else may. I know sometimes the partitions can get out of wack, or at least I have heard of it on other devices, I think I recall it for this one as well.
Also, try downloading the img file again. I believe you must extract it one time to get the proper zip file needed to flash it. I believe the version I downloaded was the pd15img.zip compressed further into a second zip file. when you look in the file you should see several img files, not a folder.
Also, make sure you are using the proper recovery for the ROM, ROM manager app tells you to update your recovery every time you start it if you are not using 3.0.0.5, if you do update, the phone will keep running but if you later flash a new froyo ROM then you will have issues.
At this point, I would try re-downloading the pd15img file and trying fresh to rule out bad downloads, or flashing a known good ROM zip, and ensuring it works with your recovery version.
zion1827 said:
How can I get my computer to recognize my phone? I can't power up and no hboot with holding down power + vol down. Please help !!
Click to expand...
Click to collapse
Sounds like you are full bricked. That means you can not fix it.
It can be fixed, but only with special equipment that can flash information straight to the internal memory chips. Meaning you need access to the internal components along with the software and equipment. So that means HTC engineering dept is about the only ones who can.
It is really hard to brick a device. Only times you can do it are anytime the Hboot file is flashed or the radio is flashed. As those two files are what boots the hardware and readies the software to boot. Thing is, you don't flash those often. Just once for Hboot, and radio firmware updates are very rare.
Dev posts on rooting need to state that flashing the engineering Hboot should be optional AND only for those experienced in flashing and rooting. First time flashers should probably avoid it for a while.
Thing is, flashing the pd15img file can brick a device as it flashes Hboot and radio.
Try this method, let me know if it works for you..
----> Try not to plug Your device on your computer , Put your image in sd card/ then Reboot into the hboot-- and the phone the automatically detects you image in the sdcard and the phone do the rest.. If you see in the upper right corner a bar thats ok its fine.. The phone loads the image and wait be patient.. the it would ask you when its done if you want those settings to be back to stock ROM. Just Click the Up Volume button , and thats it... Try Backing up after you made some changes on the phone.... <------
chipis said:
----> Try not to plug Your device on your computer , Put your image in sd card/ then Reboot into the hboot-- and the phone the automatically detects you image in the sdcard and the phone do the rest.. If you see in the upper right corner a bar thats ok its fine.. The phone loads the image and wait be patient.. the it would ask you when its done if you want those settings to be back to stock ROM. Just Click the Up Volume button , and thats it... Try Backing up after you made some changes on the phone.... <------
Click to expand...
Click to collapse
Its not Brick it just stuck on something undone....

[Q] HTC ONE S no rom no adb no sd card

Hi !
I have been trying to fix my htc one s (s4) for several days now, and i'm stuck.
I tried to update my HBOOT and get back to stock rom by flashing a RUU but I got the wrong one (signature verification fail) but I'm not sure that's what caused the problem.
When I plug my phone in in recovery (TWRP or CWM) an empty disk is detected on my computer but no sd card so i can't format it or load another ROM to be flashed.
I did a factory reset to see if it would fix it but it did not.
I have no ROM left on my phone, no backup available, adb does not work ( each adb command gets me a error:device not found ) and adb devices can't see my phone.
My HTC Drivers are updated.
Fastboot and bootloader, however, still work.
I have tried changing cable.
When I wipe dalvik in TWRP, I get this line among the other ones in the log:
/sd-ext not present, skipping
when i do a factory reset one of the line is
E: unknowv olume for path [/sd-ext]
And sometimes, although I'm not sure what triggers it, I get a bunch of
Unable to open ums lunfile (No such file or directory)
My phone is S-ON, H-BOOT is 1.14.0002
I don't know what to try anymore I hope I'm not the owner of a shiny little brick.
Does anyone have any ideas what my fix it ?
I apologize for my english if my grammar is poor, I'm French.
Any help would be appreciated. Thanks.
dominolapin said:
Hi !
I have been trying to fix my htc one s (s4) for several days now, and i'm stuck.
I tried to update my HBOOT and get back to stock rom by flashing a RUU but I got the wrong one (signature verification fail) but I'm not sure that's what caused the problem.
When I plug my phone in in recovery (TWRP or CWM) an empty disk is detected on my computer but no sd card so i can't format it or load another ROM to be flashed.
I did a factory reset to see if it would fix it but it did not.
I have no ROM left on my phone, no backup available, adb does not work ( each adb command gets me a error:device not found ) and adb devices can't see my phone.
My HTC Drivers are updated.
Fastboot and bootloader, however, still work.
I have tried changing cable.
When I wipe dalvik in TWRP, I get this line among the other ones in the log:
/sd-ext not present, skipping
when i do a factory reset one of the line is
E: unknowv olume for path [/sd-ext]
And sometimes, although I'm not sure what triggers it, I get a bunch of
Unable to open ums lunfile (No such file or directory)
My phone is S-ON, H-BOOT is 1.14.0002
I don't know what to try anymore I hope I'm not the owner of a shiny little brick.
Does anyone have any ideas what my fix it ?
I apologize for my english if my grammar is poor, I'm French.
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Well the good thing is you don't have a bricked device your just in a bad spot atm so
Wipe the sd card in twrp from wipe menu
Download the newist ruu before you do that flash stock recovery and relock bootloader then flash the ruu
Sent from my HTC One S using Tapatalk 4
Flashalot said:
Well the good thing is you don't have a bricked device your just in a bad spot atm so
Wipe the sd card in twrp from wipe menu
Download the newist ruu before you do that flash stock recovery and relock bootloader then flash the ruu
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
dominolapin said:
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
Click to expand...
Click to collapse
I tried nevertheless to lock and run the ruu.
upon lock:
c:\fastboot>fastboot oem lock
< waiting for device >
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Unknown error))
finished. total time: 0.944s
upon ruu:
it starts normally and then ERROR 131 error id client
and that's it.
my ruu is RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
dominolapin said:
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
Click to expand...
Click to collapse
I tried nevertheless to lock and run the ruu.
upon lock:
c:\fastboot>fastboot oem lock
< waiting for device >
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Unknown error))
finished. total time: 0.944s
upon ruu:
it starts normally and then ERROR 131 error id client
and that's it.
my ruu is RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
dominolapin said:
First, thanks for the quick reponse.
So I flashed a custom recovery but instead of having a menu i get a red triangle and it stops. Then after several minutes the phone goes into bootloop.
Any ideas !
Click to expand...
Click to collapse
"STOCK" recovery. I think you have tried with CUSTOM recovery.
Here is the link for stock recovery. The second download link is the stock recovery image
Flash stock recovery, then relock boot loader and then follow the above procedure :good:
Actually I did flash the stock recovery I just typed custom by mistake. Sorry about that. The one I flashed even came from the same link .
I searched on the forums and I might not have flashed the right ruu.
But i can't seam to find the right one, because strangely "fastboot getvar version-main" gives a blank result.
Hboot 1.14.0002
radio 1.08es.50.02.16
CID HTC_247

nexus 5 softbrick

Hey,
Hopefully you guys can give me some help with the problem ive been having,
My nexus 5 is stuck in bootloop, i can get into the bootloader and the lockstate is unlocked but no custom recovery is appearing like it used to. I tried flashing using ADB but my phone doesn't show up as a device on my pc.
i have tried to wipe the cache ect and it comes up with "E:failed to mount /cache (invalid argument)
I only really know the basics of this stuff (only ever used the basic stuff to root and flash my phone)
You must use fastboot commands while being into the bootloader, not adb.
mworley1991 said:
Hey,
Hopefully you guys can give me some help with the problem ive been having,
My nexus 5 is stuck in bootloop, i can get into the bootloader and the lockstate is unlocked but no custom recovery is appearing like it used to. I tried flashing using ADB but my phone doesn't show up as a device on my pc.
i have tried to wipe the cache ect and it comes up with "E:failed to mount /cache (invalid argument)
I only really know the basics of this stuff (only ever used the basic stuff to root and flash my phone)
Click to expand...
Click to collapse
Yeah, exactly what primokorn says...
Primokorn said:
You must use fastboot commands while being into the bootloader, not adb.
Click to expand...
Click to collapse
If you use the command "fastboot devices" and your phone with a code appears in the command prompt then there's no problem with your drivers.
Just reflash the factory image, you can use the automatic process if you run "flash all". You can also flash the images manually but if you go for that option make sure you don't forget to flash the cache image, that will fix your problem with mounting the cache partition.
ADB commands are used when the phone is booted into the ROM.
Flash the latest stock ROM from here to see if it solves the issue: https://developers.google.com/android/nexus/images
If the phone still bootloops, flash the userdata.img in fastboot. After flashing the userdata.img file in fastboot, boot directly into stock recovery using the power/volume buttons, perform a factory wipe, and reboot.

[Softbricked Phone] Help needed

Hi everyone.
3 days ago, my OPO has gone softbricked during the night while charging. Don't know why, i haven't make any change during the past days.
Anyway, it's current state:
- Stuck on boot screen (screen with "Cyanogen Mod Ready")
- Can access fastboot
- Can access TWRP recovery
- Bootloader is unlocked
- Phone is found in the PC "Device Manager"
- No change if using an other cable or USB port
And what i can't do:
- with adb tools : phone is not found with cmd adb devices (no answer in "list of devices attached"), changing drivers multiple times don't change that
- during recovery : can't wipe data / cache / factory reset (it says "Unable to mount /data" "Unable to mount /cache", "Unable to mount storage")
- during fastboot : can't flash anything (for instance with the OPO Toolbox, the answer is always "FAILED (remote : flash write failure)", or with command fastboot flash XXXX get the same FAILED answer)
After reading internet threads and sites, it seems that the problem is a corrupted partition, but i can't find something which can solve my problem.
Any advises?
Thx in advance!
3th3lk4 said:
Hi everyone.
3 days ago, my OPO has gone softbricked during the night while charging. Don't know why, i haven't make any change during the past days.
Anyway, it's current state:
- Stuck on boot screen (screen with "Cyanogen Mod Ready")
- Can access fastboot
- Can access TWRP recovery
- Bootloader is unlocked
- Phone is found in the PC "Device Manager"
- No change if using an other cable or USB port
And what i can't do:
- with adb tools : phone is not found with cmd adb devices (no answer in "list of devices attached"), changing drivers multiple times don't change that
- during recovery : can't wipe data / cache / factory reset (it says "Unable to mount /data" "Unable to mount /cache", "Unable to mount storage")
- during fastboot : can't flash anything (for instance with the OPO Toolbox, the answer is always "FAILED (remote : flash write failure)", or with command fastboot flash XXXX get the same FAILED answer)
After reading internet threads and sites, it seems that the problem is a corrupted partition, but i can't find something which can solve my problem.
Any advises?
Thx in advance!
Click to expand...
Click to collapse
Is your bootloader unlocked?If not try it with this command:
fastboot oem unlock
Click to expand...
Click to collapse
After that try wiping your partitions via fastboot for ex.
fastboot erase userdata
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
Click to expand...
Click to collapse
And then try flashing again.
Hope it helps:good:
Regards,
acervenky
Hi acervenky,
Bootloader is unlocked, yes.
Unfortunately, wiping partitions with those commands didn't work.
For the 5 commands, i have the answer : FAILED (remote : failed to erase partition).
This phone is going to drive me insane!
So a little update status of my phone.
I have sent a question at request at the oneplus one support.
They have answered quite fast. They made a "rendez-vous" to try to unbrick it by phone but all that was tried have been already done.
They send me instructions for sending the phone to a factory in a foreign contry.
I have received the phone this afternoon, 1 week after it was sent.
Seems to work perfectely fine.
They say that they have changed the Motherboard, which is the problem here.
So if u have the same problem, don't hesitate to use the oneplus one support.
Is there a way to change the title to show that it was a motherboard problem?

Need help..Soft bricked.. Bootloop..unable to unlock

Hi,
My OnePlus one suddenly goes into bootloop.
I was on stock COS. I was not enabled USB debuggung so adb not recognizing device. Phone was never unlocked as well.
I'm able to go into cynogen recovery but when I tried to clear cache or factory reset, I'm getting unable to erase partition error.
I'm able to go into fastboot but unable to unlock, as soon as I gave fastboot oem unlock command, device reboots into recovery. I'm unable to flash anything as device is locked.
I tried to sideload cynogen factory firmware but it results in same error of unable to erase partition. Fastboot erase system also giving same error.
I found somewhere that the following command will work in TWRP. But I don't have TWRP recovery and I'm unable to flash it because device is locked.
Unable to use adb shell command as well because adb not detecting my device because I was not enabled USB debuggung.
make_ext4fs /dev/block/mmcblk0p15
Can anyone help me, my device is dead from 2 weeks with this.
SreeSri444 said:
Hi,
My OnePlus one suddenly goes into bootloop.
I was on stock COS. I was not enabled USB debuggung so adb not recognizing device. Phone was never unlocked as well.
I'm able to go into cynogen recovery but when I tried to clear cache or factory reset, I'm getting unable to erase partition error.
I'm able to go into fastboot but unable to unlock, as soon as I gave fastboot oem unlock command, device reboots into recovery. I'm unable to flash anything as device is locked.
I tried to sideload cynogen factory firmware but it results in same error of unable to erase partition. Fastboot erase system also giving same error.
I found somewhere that the following command will work in TWRP. But I don't have TWRP recovery and I'm unable to flash it because device is locked.
Unable to use adb shell command as well because adb not detecting my device because I was not enabled USB debuggung.
make_ext4fs /dev/block/mmcblk0p15
Can anyone help me, my device is dead from 2 weeks with this.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
I tried that too, after 8974_msimage.mbn, device reboots and showing usbIA , I tried press power+volume up but same repeats.. what shall I do now?
SreeSri444 said:
I tried that too, after 8974_msimage.mbn, device reboots and showing usbIA , I tried press power+volume up but same repeats.. what shall I do now?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
The above thread is saying only for hard bricked device not for soft bricked device. Mine, able to open cynogen recovery and fastboot as well.
SreeSri444 said:
The above thread is saying only for hard bricked device not for soft bricked device. Mine, able to open cynogen recovery and fastboot as well.
Click to expand...
Click to collapse
It'll work for soft bricked devices as well.Since you're not able to unlock bootloader,fastboot is pretty much useless atm.
Mr.Ak said:
It'll work for soft bricked devices as well.Since you're not able to unlock bootloader,fastboot is pretty much useless atm.
Click to expand...
Click to collapse
Again same happening with Color.zip too, after 8974_msimage.mbn, device reboots and showing usbIA , I tried press power+volume up but same repeats..
SreeSri444 said:
Again same happening with Color.zip too, after 8974_msimage.mbn, device reboots and showing usbIA , I tried press power+volume up but same repeats..
Click to expand...
Click to collapse
I'm afraid flash ic might be corrupt then.You'll have to replace pcb.
Mr.Ak said:
I'm afraid flash ic might be corrupt then.You'll have to replace pcb.
Click to expand...
Click to collapse
How can I do this? Can you explain in detail?
SreeSri444 said:
How can I do this? Can you explain in detail?
Click to expand...
Click to collapse
Pcb=logic board=motherboard
Unless it was taken from another phone sold off as parts, you can't buy the logic board on its own. The same applies for most smartphones out there.
In short,sell parts of your one,and buy a new device.

Categories

Resources