Related
The situation:
No OS, no recovery, and no mountable SD card. Bootloader unlocked and rooted. Currently Relocked.
What I've tried:
"One X ATT All in one kit" gives me this error: (remote: 92 supercid! please flush image again immediately) when doing recovery.
"fastboot boot recovery.img" gives me: FAILED (remote: not allowed)
"fastboot flash recovery recovery.img" gives me INFOsignature checking... FAILED (remote: signature verify fail)
Running the RUU.exe doesnt give me any errors but doesn't work.
When unlocked
"fastboot boot recovery.img" i get: FAILED (remote: reproduce boot image with on-flash ramdisk error)
EDIT: TWRP gives me a black screen.
so what can i do the fix this?
Thanks.
shadyboy039 said:
The situation:
No OS, no recovery, and no mountable SD card. Bootloader unlocked and rooted. Currently Relocked.
What I've tried:
"One X ATT All in one kit" gives me this error: (remote: 92 supercid! please flush image again immediately) when doing recovery.
"fastboot boot recovery.img" gives me: FAILED (remote: not allowed)
"fastboot flash recovery recovery.img" gives me INFOsignature checking... FAILED (remote: signature verify fail)
Running the RUU.exe doesnt give me any errors but doesn't work.
When unlocked
"fastboot boot recovery.img" i get: FAILED (remote: reproduce boot image with on-flash ramdisk error)
EDIT: TWRP gives me a black screen.
so what can i do the fix this?
Thanks.
Click to expand...
Click to collapse
Try to flash RUU Att 2.20
http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe
Sent from my HTC One XL
shadyboy039 said:
The situation:
No OS, no recovery, and no mountable SD card. Bootloader unlocked and rooted. Currently Relocked.
Click to expand...
Click to collapse
How did you get to this point, exactly?
Do you see the device, if you adb the command:
adb devices
If you did a factory reset in bootloader, it corrupted the SD card, which may be why it won't mount. Connect the phone to your PC via USB, and open Device Manager, and see if it shows up. If you have the option to format it, do so as FAT32.
shadyboy039 said:
The situation:
No OS, no recovery, and no mountable SD card. Bootloader unlocked and rooted. Currently Relocked.
What I've tried:
"One X ATT All in one kit" gives me this error: (remote: 92 supercid! please flush image again immediately) when doing recovery.
"fastboot boot recovery.img" gives me: FAILED (remote: not allowed)
"fastboot flash recovery recovery.img" gives me INFOsignature checking... FAILED (remote: signature verify fail)
Running the RUU.exe doesnt give me any errors but doesn't work.
When unlocked
"fastboot boot recovery.img" i get: FAILED (remote: reproduce boot image with on-flash ramdisk error)
EDIT: TWRP gives me a black screen.
so what can i do the fix this?
Thanks.
Click to expand...
Click to collapse
Why did you relock? If you downgraded hboot I do not suggest running the RUU. Unlock bootloader then you can flash twrp recovery then check resources compilation sticky in Android device section for unmountable sd card if still cannot access sd card. Then flash rom. If you did not downgrade hboot you can run your carriers ruu which will bring you back to stock if that is what you were trying to accomplish.
Sent from my One X using xda app-developers app
kaiser347 said:
Try to flash RUU Att 2.20
http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe
Sent from my HTC One XL
Click to expand...
Click to collapse
been using 2.20 RUU
redpoint73 said:
How did you get to this point, exactly?
Do you see the device, if you adb the command:
adb devices
If you did a factory reset in bootloader, it corrupted the SD card, which may be why it won't mount. Connect the phone to your PC via USB, and open Device Manager, and see if it shows up. If you have the option to format it, do so as FAT32.
Click to expand...
Click to collapse
i don't quite understand how i got here. i just kept getting stuck on bootloop even after reflashing to CM10. i only got into twrp once and i've been on loop since.
EDIT: no adb device. and ya the factory reset did screw me over. but after getting loopped even after reflashing twrp, i didnt know what to do.
exad said:
Why did you relock? If you downgraded hboot I do not suggest running the RUU. Unlock bootloader then you can flash twrp recovery then check resources compilation sticky in Android device section for unmountable sd card if still cannot access sd card. Then flash rom. If you did not downgrade hboot you can run your carriers ruu which will bring you back to stock if that is what you were trying to accomplish.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
last i checked you cant downgrade from 2.20. but that was way back when x-factor exploit was released, that's way im doing 2.20 RUU.
Sorry I wasn't descriptive enough on that part.
Well, things took a turn for the worst and now i think it's bricked cause of the QHSUSB_dload thing.
Thanks for the replies.
shadyboy039 said:
been using 2.20 RUU
i don't quite understand how i got here. i just kept getting stuck on bootloop even after reflashing to CM10. i only got into twrp once and i've been on loop since.
EDIT: no adb device. and ya the factory reset did screw me over. but after getting loopped even after reflashing twrp, i didnt know what to do.
last i checked you cant downgrade from 2.20. but that was way back when x-factor exploit was released, that's way im doing 2.20 RUU.
Sorry I wasn't descriptive enough on that part.
Well, things took a turn for the worst and now i think it's bricked cause of the QHSUSB_dload thing.
Thanks for the replies.
Click to expand...
Click to collapse
Can you access bootloader? And yes you can downgrade any hboot. But you do risk a possible brick as the hboot downgrade purposefully bricks to downgrade hboot.
Sent from my One X using xda app-developers app
shadyboy039 said:
Well, things took a turn for the worst and now i think it's bricked cause of the QHSUSB_dload thing.
Click to expand...
Click to collapse
Is the PC actually saying "QHSUSB_dload" or not?
What is the current state of the phone? Any charge LED, or screen come on at all?
exad said:
Can you access bootloader? And yes you can downgrade any hboot. But you do risk a possible brick as the hboot downgrade purposefully bricks to downgrade hboot.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
No hboot. O that's great I'm currently reading up this thread http://forum.xda-developers.com/showthread.php?t=1966850 . Is this the right thread or is there another one?
redpoint73 said:
Is the PC actually saying "QHSUSB_dload" or not?
What is the current state of the phone? Any charge LED, or screen come on at all?
Click to expand...
Click to collapse
No LED. Computer says "QHSUSB_dload" when it trys to install drivers.
It's not turning on with any button combination.
Edit: None of my computers are detecting it anymore.
To go from a simple fix to where u are at now u must of done something. If you state everything you did it might help us help you better. Hopefully you didnt do anything meant for the htc one x(international).
DvineLord said:
To go from a simple fix to where u are at now u must of done something. If you state everything you did it might help us help you better. Hopefully you didnt do anything meant for the htc one x(international).
Click to expand...
Click to collapse
I made sure to stay away from the international board after I accidentally posted there 6 months ago. So that's not possible. Not sure where I went wrong. Been at this for over 12 hours with it turning on and off. Like I said I just couldn't get out of bootloop when I had hboot. Now that it's not turning on anymore I don't know what to do.
EDIT: It's been about 2 hours now. No LED. Haven't touched it yet and don't plan to for a while longer. But I'm thinking about bring it in and asking for a replacement tomorrow. What are the chances that they'll replace it?
If you plug it up to wall charger does the led come on after awhile, if it was battery was dead it can take 10-15 minutes for led to turn on?
DvineLord said:
If you plug it up to wall charger does the led come on after awhile, if it was battery was dead it can take 10-15 minutes for led to turn on?
Click to expand...
Click to collapse
I've left it for for around 20 minutes and still no dice. I'm gonna try leaving it for a few hours and hope it'll bounce back.
EDIT: It's been about 2 hours now. No LED. Haven't touched it yet and don't plan to for a while longer. But I'm thinking about bring it in and asking for a replacement tomorrow. What are the chances that they'll replace it?
EDIT: Don't know if this means anything but the area under the camera is slightly warmer than the rest of the phone. It's been plugged in and it's been hanging at the edge of the table because i don't like setting it on the camera.
shadyboy039 said:
I've left it for for around 20 minutes and still no dice. I'm gonna try leaving it for a few hours and hope it'll bounce back.
EDIT: It's been about 2 hours now. No LED. Haven't touched it yet and don't plan to for a while longer. But I'm thinking about bring it in and asking for a replacement tomorrow. What are the chances that they'll replace it?
EDIT: Don't know if this means anything but the area under the camera is slightly warmer than the rest of the phone. It's been plugged in and it's been hanging at the edge of the table because i don't like setting it on the camera.
Click to expand...
Click to collapse
sounds like it may be bricked. how did you get to this point? you can try the unbricking thread. if you can catch your emmc partitions you may be able to recover.
here's the link just in case youre unable to find it. http://forum.xda-developers.com/showthread.php?t=1966850
shadyboy039 said:
Computer says "QHSUSB_dload" when it trys to install drivers.
Click to expand...
Click to collapse
You're in Qualcomm download mode. No bootloader, so the phone isn't going to boot by itself. You're screwed. Unless you want to try the unbricking thread using a Linux machine, as previously suggested.
---------- Post added at 01:46 PM ---------- Previous post was at 01:41 PM ----------
shadyboy039 said:
ut I'm thinking about bring it in and asking for a replacement tomorrow. What are the chances that they'll replace it?
Click to expand...
Click to collapse
Warranty covers defects by the manufacturer, not damage done by you. You knew the risks of trying to mod the phone.
Hi,
My phone started to fail and give me a lot of errors that it was stopping initiator, android.process.acore, etc... and got stuck in this errors, having to accept the error dialogs all the time and being impossible to make anything with it.
I tried to reset my moto G and wipe all user data. I entered fastboot mode (couldn't do it form phone normal menu) and made a factory reset. No changes after reboot.
Then I tried to reinstall firmware. I've made all the steps in several tutorials found here. The bootloader is unlocked, I put the last firmware , entered recovery mode and ask for wipe/reset user data, but when the phone reboots, there are no changes: I have again the personalized screen image and the gesture blocking, as if the user data remains there, and all the errors.
Is there any way to erase all user data and leave the phone as the first day? Am I making something wrong or need to make something more?
Thanks in advance
Sounds like you might have encrypted it?
BobbaLouie said:
Sounds like you might have encrypted it?
Click to expand...
Click to collapse
Not consciously, the phone had normal use....
If it was encrypted you'd have to enter a password before it even got to the boot logo, so it would be very obvious.
BobbaLouie said:
If it was encrypted you'd have to enter a password before it even got to the boot logo, so it would be very obvious.
Click to expand...
Click to collapse
Then, it is not encrypted.
thanks
Jorge BCN said:
Hi,
My phone started to fail and give me a lot of errors that it was stopping initiator, android.process.acore, etc... and got stuck in this errors, having to accept the error dialogs all the time and being impossible to make anything with it.
I tried to reset my moto G and wipe all user data. I entered fastboot mode (couldn't do it form phone normal menu) and made a factory reset. No changes after reboot.
Then I tried to reinstall firmware. I've made all the steps in several tutorials found here. The bootloader is unlocked, I put the last firmware , entered recovery mode and ask for wipe/reset user data, but when the phone reboots, there are no changes: I have again the personalized screen image and the gesture blocking, as if the user data remains there, and all the errors.
Is there any way to erase all user data and leave the phone as the first day? Am I making something wrong or need to make something more?
Thanks in advance
Click to expand...
Click to collapse
Are you rooted? If so, you might have to FORMAT your phone, which will erase even your storage. I used TWRP and my phone just factory reset after I formatted. I think there must've been some sort of corruption.
Jorge BCN said:
Hi,
My phone started to fail and give me a lot of errors that it was stopping initiator, android.process.acore, etc... and got stuck in this errors, having to accept the error dialogs all the time and being impossible to make anything with it.
I tried to reset my moto G and wipe all user data. I entered fastboot mode (couldn't do it form phone normal menu) and made a factory reset. No changes after reboot.
Then I tried to reinstall firmware. I've made all the steps in several tutorials found here. The bootloader is unlocked, I put the last firmware , entered recovery mode and ask for wipe/reset user data, but when the phone reboots, there are no changes: I have again the personalized screen image and the gesture blocking, as if the user data remains there, and all the errors.
Is there any way to erase all user data and leave the phone as the first day? Am I making something wrong or need to make something more?
Thanks in advance
Click to expand...
Click to collapse
Try clearing data,cache,dalvik cache and reflashing the ROM..if all fails try to clear data and flash the stock ROM through fastboot mode.
KVCmoto said:
Try clearing data,cache,dalvik cache and reflashing the ROM..if all fails try to clear data and flash the stock ROM through fastboot mode.
Click to expand...
Click to collapse
I've made it all, but when reboot, there is the same data there....
Neither can't root the phone, when I make adb sideload supersu.zip, I receive a installation aborted error after verification of the file....
Any Ideas?
Thanks in advance
Jorge BCN said:
I've made it all, but when reboot, there is the same data there....
Neither can't root the phone, when I make adb sideload supersu.zip, I receive a installation aborted error after verification of the file....
Any Ideas?
Thanks in advance
Click to expand...
Click to collapse
Flash the stock ROM once more through boot loader http://forum.xda-developers.com/showthread.php?t=2542219
If you have TWRP installed and your data backed up, I would highly suggest formatting your phone. My phone was having heaps of trouble, including random reboots, the inability for factory data reset, it was slow, having wake time issues, all sorts of shiz. One reformat and it was all better.
MoseIlla said:
If you have TWRP installed and your data backed up, I would highly suggest formatting your phone. My phone was having heaps of trouble, including random reboots, the inability for factory data reset, it was slow, having wake time issues, all sorts of shiz. One reformat and it was all better.
Click to expand...
Click to collapse
What do you mean with reformat? I can't boot into other recovery than stock, and it doesn't allow me erase user data, thats the problem.
When I try to flash other recovery (TWRP, Philz,..) it seems that has been flashed ok but when go to recovery from bootloader menu I have the old stock recovery menu...
Thanks in advance
Jorge BCN said:
What do you mean with reformat? I can't boot into other recovery than stock, and it doesn't allow me erase user data, thats the problem.
When I try to flash other recovery (TWRP, Philz,..) it seems that has been flashed ok but when go to recovery from bootloader menu I have the old stock recovery menu...
Thanks in advance
Click to expand...
Click to collapse
You unlocked the bootloader then, yes? How's your ROM behaving?
MoseIlla said:
You unlocked the bootloader then, yes? How's your ROM behaving?
Click to expand...
Click to collapse
Can you be more explicit?
Are you using the special mfastboot or the generic fastboot executable from the Android SDK?
Execute these commands with the phone in fastboot (bootloader menu):
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
liveroy said:
Are you using the special mfastboot or the generic fastboot executable from the Android SDK?
Execute these commands with the phone in fastboot (bootloader menu):
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Click to expand...
Click to collapse
Hi, the same after rebooting, I have all my user data... (I'm using mfastboot for OSX, but the same result with fastboot under Darwin subfolder of stock firmware)
no errors executing it, no errors in the phone, but no effect in phone user data
$ ./mfastboot erase cache
erasing 'cache'...
OKAY [ 0.017s]
finished. total time: 0.017s
$ ./mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.018s]
finished. total time: 0.019s
$ ./mfastboot reboot
Jorge BCN said:
Can you be more explicit?
Click to expand...
Click to collapse
I just reread your first post. When did your phone start giving you errors? Did you install any new apps, did you let it die completely? The errors had to have started somewhere. Perhaps we can undo a bit of the damage that lead to this and get you back to a somewhat usable state if we have that information.
MoseIlla said:
I just reread your first post. When did your phone start giving you errors? Did you install any new apps, did you let it die completely? The errors had to have started somewhere.
Click to expand...
Click to collapse
No idea. There was not anything special or new app. A month ago it started to give errors. Sometimes I can get 1 or 2 minutes working without errors, but can't delete user data or reset from phone menu (no result when touch the button).
Thanks
Jorge BCN said:
No idea. There was not anything special or new app. A month ago it started to give errors. Sometimes I can get 1 or 2 minutes working without errors, but can't delete user data or reset from phone menu (no result when touch the button).
Thanks
Click to expand...
Click to collapse
Does this coincide with a firmware update (Like Android 4.4.2 to 4.4.3)?
MoseIlla said:
Does this coincide with a firmware update (Like Android 4.4.2 to 4.4.3)?
Click to expand...
Click to collapse
Nopes, as far as I know
Here's what I know about the issue, perhaps it will give someone else an idea:
1. The issue is either caused by or is unaffected by previous factory resets.
2. The issue is either caused by or is unaffected by the installation of new and/or updated ROMs.
3. If it's the same issue I was having, and I believe that it least shares the same root cause, then it is something that gets worse over time; it causes system instability (system UI crashes in increasing number, random reboots, etc...), slowness, and refuses to allow you to hard reset after a while.
4. In the case that it is the same issue, it has different effects on different methods of factory resets. In TWRP the factory reset process just continues on forever, until you hard reboot the device or until the battery drains out. If you press the factory reset button in fastboot it just resets to system, making no changes.
5. In TWRP I used the reformat option and have since had no issues, including better than new performance with crDroid.
Based on my understanding of the Moto G partition tables, I believe that the issue may have to do with gradual data corruption, possibly on the storage partition. This may be because of a software bug in the firmware or maybe a hardware issue. Due to the ubiquity of the lock up/reboot issue, which is well documented and has several guides indicating that a factory reset is in order when this occurs, I'm thinking that it is safe to assume that some resource shared both with the system and storage partitions is to blame.
If that is the case, then I would think it's the cache or a bug with an updated system app that leaves traces in the device storage.
This is all assuming the issues are interrelated, so I may be way off base, but if my assumptions are correct, then the only suggestion I can think of is to completely clear the device storage and cache and then try to factory reset again, as it may be hanging up on removing something there and aborting when it runs into trouble.
Maybe someone has a better idea. Your device may be bricked and since you unlocked the boot loader AFTER the issues started, you voided your warranty with none of the advanced recovery tools that you'd have with a custom recovery.
In other words: You might have to get a new phone.
My nexus 5 was stock when i did a factory reset and something wrong happened and it was stuck on the android guy with the blue sphere thing.
So i decided to try and flash the factory image from Google but it gets stuck at erasing the cache. I have done it both by flash all and by doing each step independently. And its always stuck on clear cache
I then tried the cwm recovery and wiped the cache and tried installing CM11. CM11 was stuck in a bootloop
then i tried TWRP recovery but the phone would not load into it.
Then i tried the WugFresh Nexus Root Toolkit to flash stock and unroot and the phone still gets stuck on erasing cache
Any ideas? What should I try next?
Flash stock recovery and wipe cache and leave it doing that for as long as it takes.
rootSU said:
Flash stock recovery and wipe cache and leave it doing that for as long as it takes.
Click to expand...
Click to collapse
How long is reasonable?
I have waited 45 min in the past before losing patience
Could actually be a bit longer than that. Also, fastboot flash cache.img.on its own.
Thank You I will leave it running for a while and see what happens
It has been a little over an hour. How much longer should I wait?
Hard to say. Each time you interrupt it, you make it worse. Give it another hour. If that doesn't work, maybe try lg flash tool.
My mistake I might have interrupted it more then a few times yesterday. I probably made it fairly bad.
rootSU said:
Hard to say. Each time you interrupt it, you make it worse. Give it another hour. If that doesn't work, maybe try lg flash tool.
Click to expand...
Click to collapse
It has been erasing cache for about 12hrs should I give up on the idea it will do it and try the lg flash tool.
CoolRyder39 said:
It has been erasing cache for about 12hrs should I give up on the idea it will do it and try the lg flash tool.
Click to expand...
Click to collapse
Its probably the only option,
rootSU said:
Its probably the only option,
Click to expand...
Click to collapse
I get userdata erase fail when I run lg flash tool then it says We cant communicate.
Any other ideas
CoolRyder39 said:
I get userdata erase fail when I run lg flash tool then it says We cant communicate.
Any other ideas
Click to expand...
Click to collapse
If you use fastboot to lock the bootloader then reboot the bootloader, is it unlocked again? Please test
rootSU said:
If you use fastboot to lock the bootloader then reboot the bootloader, is it unlocked again? Please test
Click to expand...
Click to collapse
The bootloader is locked
CoolRyder39 said:
The bootloader is locked
Click to expand...
Click to collapse
should rule out nand failure then. All I can suggest is send it to LG, if you've already tried swapping USB cables and ports.
Thanks ill try different ones then give up haha
rootSU said:
should rule out nand failure then. All I can suggest is send it to LG, if you've already tried swapping USB cables and ports.
Click to expand...
Click to collapse
CoolRyder39 said:
Thanks ill try different ones then give up haha
Click to expand...
Click to collapse
Have you tried just formatting cache with fastboot? Tried multiple recoveries and wiping cache through them? If none of this works I'd bet your nand has a bad sector.
It can format erase and flash the cache no problem in fastboot it just wont do it at the end of the process of flashing a custom rom
rootSU said:
Its probably the only option,
Click to expand...
Click to collapse
I am having the same problem trying to flash to 5.0 or 5.0.1. It's to the point where Google says, "well, it's out of warranty, so send it to LG" and LG says, "send it to us and we'll tell you whether we'll charge you for a fix".
Pointer to the aforementioned "lg flash tool" - presumably different from the Google f/w at //developers.google.com/android/nexus/images - would be welcome.
Hey everyone,
I've been tearing out my hair for the past 34 hours (with the exception of sleeping). I restarted my phone yesterday and it got stuck in the boot animation, for hours.
I have never unlocked my bootloader, or flashed any custom rom on this phone, so I was really shocked when this happened. So I took to these forums, because lurking here usually solves all my issues (thanks awesome people), and flashed the stock image as recommended-> bootloop -> factory reset in recovery mode -> bootloop-> repeated this all night and today with multiple flashing methods (fastboot using flash-all and flashing individually, no dice.
I was wondering if I was out of luck, seeing as though my phone just randomly did this to itself, without prior tampering, or if there was something I could try doing. I haven't tried any custom recoveries as I don't really know how that would help me if I am willing to flash back to stock and lose all my data.
I am able to boot into fastboot mode and go to recovery mode, so this indicates to me that my hardware is fine, unless I am wrong
Thanks, I would appreciate all the help I can get
Was fast boot one of those multiple flashing methods?
theesotericone said:
Was fast boot one of those multiple flashing methods?
Click to expand...
Click to collapse
Yeah, both using Flash-all and flashing each individual, Ill update post
ChunksOfLemon said:
Yeah, both using Flash-all and flashing each individual, Ill update post
Click to expand...
Click to collapse
And you didn't receive any errors at all while flashing them individually? If that's the case I'd fastboot format each partition first then flash it. If that doesn't work you're pretty much out of luck. Just so where on the same page it would go like this:
Code:
fastboot format system
fastboot flash system system.img
Then just repeat that for everything.
theesotericone said:
And you didn't receive any errors at all while flashing them individually? If that's the case I'd fastboot format each partition first then flash it. If that doesn't work you're pretty much out of luck. Just so where on the same page it would go like this:
Code:
fastboot format system
fastboot flash system system.img
Then just repeat that for everything.
Click to expand...
Click to collapse
I'll try this now and let you know
theesotericone said:
And you didn't receive any errors at all while flashing them individually? If that's the case I'd fastboot format each partition first then flash it. If that doesn't work you're pretty much out of luck. Just so where on the same page it would go like this:
Code:
fastboot format system
fastboot flash system system.img
Then just repeat that for everything.
Click to expand...
Click to collapse
Yeah, no luck there either
I guess I'll call LG in the morning
ChunksOfLemon said:
Yeah, no luck there either
I guess I'll call LG in the morning
Click to expand...
Click to collapse
First reboot to recovery and wipe cache.
theesotericone said:
First reboot to recovery and wipe cache.
Click to expand...
Click to collapse
Nothing is working, I'll check to see how much it'll be to repair
ChunksOfLemon said:
Nothing is working, I'll check to see how much it'll be to repair
Click to expand...
Click to collapse
Have you tried -> http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576 ?
beekay201 said:
Have you tried -> http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576 ?
Click to expand...
Click to collapse
OMG YES THIS WORKS! Thank you, I read that thread in my initial search, but it didn't seem to apply. But I just tried it and my device booted in like five minutes.
Thanks for helping me guys, don't need to buy another phone
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...