Related
G'day guys,
I was trying to install a custom recovery after unlocking the bootloader and something horribly went wrong
during the install, phone seemed to hang, gave it a good amount of time to do it stuff but nothing happend.
Didn't think much of it as i thought i could just start again with the install, but had no joy. Then somehow in
my panic i have managed to lock the bootloader again really making it difficult to do anything.
As it stands at the moment, i can do the following with the phone.
Can get into the fastboot screen
Cannot get into recovery.
Will start normally and show the powered by android screen then will just sit there as if it was starting (which it doesn't)
I was using the following guide :http://forum.xda-developers.com/showthread.php?t=2788632 for the process.
I must also stress that this isn't the 1st time i have tried to root android phones and have successfully rooted my S2,S3 and note 2.
That being said i have totally rooted this OPO.
I have spent the last 3 days basically reading any thread in this forum with the hope of reversing this cockup
and have tried many but to no avail. Basically road blocked i think by the locked bootloader.
The only thing i haven't tried yet is using a computer with Win xp as Win 7 is a pain in the arse for drivers.
Any of you guys got some idea whether this fixable or should i just give up and bin it? I don't want too and would love to be able to get
it back up running but this has really done my head in.
Cheers
U can flash factory images from fastboot:http://forum.xda-developers.com/oneplus-one/orig-development/discussion-cyanogenmod-11s-t2840305
ashishv said:
U can flash factory images from fastboot:http://forum.xda-developers.com/oneplus-one/orig-development/discussion-cyanogenmod-11s-t2840305
Click to expand...
Click to collapse
Not with a locked bootloader.
Transmitted via Bacon
---------- Post added at 07:09 PM ---------- Previous post was at 07:07 PM ----------
Moatmonster said:
G'day guys,
I was trying to install a custom recovery after unlocking the bootloader and something horribly went wrong
during the install, phone seemed to hang, gave it a good amount of time to do it stuff but nothing happend.
Didn't think much of it as i thought i could just start again with the install, but had no joy. Then somehow in
my panic i have managed to lock the bootloader again really making it difficult to do anything.
As it stands at the moment, i can do the following with the phone.
Can get into the fastboot screen
Cannot get into recovery.
Will start normally and show the powered by android screen then will just sit there as if it was starting (which it doesn't)
I was using the following guide :http://forum.xda-developers.com/showthread.php?t=2788632 for the process.
I must also stress that this isn't the 1st time i have tried to root android phones and have successfully rooted my S2,S3 and note 2.
That being said i have totally rooted this OPO.
I have spent the last 3 days basically reading any thread in this forum with the hope of reversing this cockup
and have tried many but to no avail. Basically road blocked i think by the locked bootloader.
The only thing i haven't tried yet is using a computer with Win xp as Win 7 is a pain in the arse for drivers.
Any of you guys got some idea whether this fixable or should i just give up and bin it? I don't want too and would love to be able to get
it back up running but this has really done my head in.
Cheers
Click to expand...
Click to collapse
I'm assuming that all subsequent attempts to unlock the bootloader again (fastboot oem unlock) are failing?
Transmitted via Bacon
timmaaa said:
Not with a locked bootloader.
Transmitted via Bacon
---------- Post added at 07:09 PM ---------- Previous post was at 07:07 PM ----------
I'm assuming that all subsequent attempts to unlock the bootloader again (fastboot oem unlock) are failing?
Transmitted via Bacon
Click to expand...
Click to collapse
Yeah, thats right timmaaa, no joy at all in unlocking again.
It just hangs on the powered by android screen after hitting enter.
Moatmonster said:
Yeah, thats right timmaaa, no joy at all in unlocking again.
It just hangs on the powered by android screen after hitting enter.
Click to expand...
Click to collapse
Let me search for something that might help, leave it with me.
Transmitted via Bacon
Cheers mate.
What build of CM11S are/were you on?
Transmitted via Bacon
timmaaa said:
What build of CM11S are/were you on?
Transmitted via Bacon
Click to expand...
Click to collapse
Pretty sure it was 38R ?, i definitely updated just after i got the phone in early October.
Moatmonster said:
Pretty sure it was 38R ?, i definitely updated just after i got the phone in early October.
Click to expand...
Click to collapse
Ah, that's a shame, the method I was thinking of won't work since that update. This is it:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
It relies on you being able to boot a recovery as opposed to actually flashing it, and then flashing a script with that recovery. I'm 99.9% sure that you can't do that since the 38R update though. It's worth a try, connect your phone in fastboot mode and try to boot a recovery (the following command assumes that you have 'openrecovery-twrp-2.8.1.0-bacon.img' in your fastboot folder).
Code:
fastboot boot openrecovery-twrp-2.8.1.0-bacon.img
Like I said, it probably won't work, but it's worth a shot.
Transmitted via Bacon
Will have a crack when i get home, thanks for your help.
No good mate as you said.
Moatmonster said:
No good mate as you said.
Click to expand...
Click to collapse
Bummer. @zephiK, do you have any ideas?
Transmitted via Bacon
Edit: After looking through some oneplus forums, looks like they have tried to issue out a patch for this issue. Have you tried this? I would try it out first and see if it helps. Again, the below one people were really bricked, hope it helps.
I haven't had to use this, and the thread is long, but a very good read. Please go to this thread. A lot of people were able to get their devices working again by using a few tools on windows machines xp win7 and win 8.1. Basically bricked device like the one you are looking at, then installing color OS somehow brought it back to life. The drivers are in chinese, but just clicking next gets them installed correctly. Mostly everyone there is in QHUSB_Bulk mode, not sure if you are or not, but worth a shot.
I have a problem with rooting my Oneplus One. It all goes well until twrp needs to start.
My screen is all black and its not reacting to anything. I have to wait till the battery is empty to turn off.
Also when its in this stage my laptop gives me an error: 'USB Device is Not Recognized'.
I hope you can help me.
Did you check the md5 of the recovery image before flashing it? Please copy/paste the text from the command prompt on a flash attempt.
Transmitted via Bacon
Can you access fastboot mode?
It all goes well until i have to restart into bootmode where i have to flash su.
Hard reset wont work when the screen turns black.
hazefetish said:
It all goes well until i have to restart into bootmode where i have to flash su.
Hard reset wont work when the screen turns black.
Click to expand...
Click to collapse
That doesn't make sense, what do you mean by bootmode? And you didn't answer either of my questions, I asked those for a reason, if you're not going to provide the information that's needed it's pretty much impossible to help you.
Transmitted via Bacon
You can always turn off your phone by holding the power button for 10 seconds.
Try fastbooting the latest TWRP. => http://techerrata.com/browse/twrp2/bacon
It's possible that you have flashed a corrupted file or even a TWRP for a different device.
Alright
Ive tried it again.
At the moment it should boot into twrp the screen turns black.
It shows up as normal adb device, its still connected but my screen wont show me a picture.
I did it with Oneplus One Toolkit 2.0.
Did everything the steps told me.
You still haven't answered my questions...
Transmitted via Bacon
I didnt check the md5 hash but due to the tool its the right iso.
And i cant copy something out of the command promt because it closes automatically.
When i did it the command promt way i didnt even get a message that something failed.
Stop using a tool to do it and do it yourself. It's simple. I have detailed instructions in my guide thread.
Transmitted via Bacon
timmaaa said:
Stop using a tool to do it and do it yourself. It's simple. I have detailed instructions in my guide thread.
Transmitted via Bacon
Click to expand...
Click to collapse
I have done it myself and it didnt work...
As i said in my previous post
Thread can be closed i renounce rooting my device.
hazefetish said:
I have done it myself and it didnt work...
As i said in my previous post
Thread can be closed i renounce rooting my device.
Click to expand...
Click to collapse
If you actually tried to work with us in solving your problem you'd have it done in no time, this is the easiest phone in the world to root. And at no point did you mention doing it yourself, you've only mentioned using a tool.
Transmitted via Bacon
timmaaa said:
If you actually tried to work with us in solving your problem you'd have it done in no time, this is the easiest phone in the world to root.
Transmitted via Bacon
Click to expand...
Click to collapse
Dude what is your problem?
I said everything i know.
I tried it several times with the tool and command promt.
I did i the exact same way and it wasnt working.
Then you come here, behaving like a pro in this things, turns out: no solution from you.
Just because it worked for you that easy doesnt mean it have to be the same for my opo.
Electronics arent always predictable so why cant it be that something on my opo doesnt work while on yours its working?
I refuse to work with you.
When i did it the command promt way i didnt even get a message that something failed.
Click to expand...
Click to collapse
Plus, you should always check the md5 of any file you're going to flash to your device. It's possible you have a corrupt download. If you flash the recovery yourself the command window won't choose automatically, then you can copy/paste the text here. Bit the first thing I'd be doing is checking the md5.
Transmitted via Bacon
---------- Post added at 08:18 AM ---------- Previous post was at 08:15 AM ----------
hazefetish said:
Dude what is your problem?
I said everything i know.
I tried it several times with the tool and command promt.
I did i the exact same way and it wasnt working.
Then you come here, behaving like a pro in this things, turns out: no solution from you.
Just because it worked for you that easy doesnt mean it have to be the same for my opo.
Electronics arent always predictable so why cant it be that something on my opo doesnt work while on yours its working?
I refuse to work with you.
Click to expand...
Click to collapse
My problem is you came here asking for help, and then it took me asking three times over the course of 19 hours for you to answer me. We need this information in order to help you, which I'm trying to do. Electronics are predictable, this process is predictable, but you need to go about it the right way (checking the md5, flashing manually with fastboot). Now, have you only tried to flash TWRP or have you tried ow odd the other recoveries too?
Transmitted via Bacon
timmaaa said:
Plus, you should always check the md5 of any file you're going to flash to your device. It's possible you have a corrupt download. If you flash the recovery yourself the command window won't choose automatically, then you can copy/paste the text here. Bit the first thing I'd be doing is checking the md5.
Transmitted via Bacon
---------- Post added at 08:18 AM ---------- Previous post was at 08:15 AM ----------
My problem is you came here asking for help, and then it took me asking three times over the course of 31 hours for you to answer me. We need this information in order to help you, which I'm trying to do. Electronics are predictable, this process is predictable, but you need to go about it the right way (checking the md5, flashing manually with fastboot). Now, have you only tried to flash TWRP or have you tried ow odd the other recoveries too?
Transmitted via Bacon
Click to expand...
Click to collapse
I didnt say electronics arent predictable per se. But there are situations where you cant comprehend what went wrong or why it went wrong.
hazefetish said:
I didnt say electronics arent predictable per se. But there are situations where you cant comprehend what went wrong or why it went wrong.
Click to expand...
Click to collapse
We can though, we can find out what went wrong by investigating. I'm trying to help you, but I need this information:
Check the md5, let me know if it matches or not.
Make another manual attempt and copy the text here.
And answer whether you've tried any recovery other than TWRP.
Transmitted via Bacon
timmaaa said:
Stop using a tool to do it and do it yourself. It's simple. I have detailed instructions in my guide thread.
Transmitted via Bacon
Click to expand...
Click to collapse
Listen to Timmaaa.... His guides & other experts from XDA-OPO forums has helped me understand a lot of things about rooting, flashing & other areas.........
Don't be arrogant toward a person trying to help. As he (timmaaa) said its very simple, You need to run about 2 commands and it will take about 5mins. I can make you a batch file if you don't even want to do that.
skyguy126 said:
Don't be arrogant toward a person trying to help. As he (timmaaa) said its very simple, You need to run about 2 commands and it will take about 5mins. I can make you a batch file if you don't even want to do that.
Click to expand...
Click to collapse
It's a nice idea, very generous, but I don't think it's the right way to go, nobody learns anything when using an automated process.
Transmitted via Bacon
I get the following error:
Unfortunately the process com.android.systemui has stopped
The error just keeps repeating if I press OK.
What I did to get this error was:
Backup current ROM using TWRP
Flash a Lollipop ROM (that didn't work)
Restore my backup
and now I'm screwed
I've read somewhere about Italians having this issue and that it had to do with low battery level. I have now recharged my phone to 95% but still no dice And my phone is running US English (though I'm in Denmark).
I'm running CM11 M11.
Can anyone help?
Clean flash.
Transmitted via Bacon
timmaaa said:
Clean flash
Click to expand...
Click to collapse
And how would I do that if I cannot transfer zip files to my phone?
And would I be able to restore my backup afterwards?
You didn't say anything about not being able to transfer zips to your phone, but I'm assuming you mean while booted into Android because of the persistent error. TWRP 2.8.x has MTP enabled so if you connect your phone to your PC while booted into that recovery you can copy a zip across to flash. And no, you can't restore your backup afterwards, the whole point of a clean flash is that it's a clean flash, completely fresh. Plus, restoring a backup after flashing a ROM would overwrite the ROM you just flashed, making it a pointless exercise. Plus, the backup that you have is obviously corrupt and that's what's causing your problem.
In short: download a ROM zip (and gapps), flash the latest TWRP to your phone (if you don't already have it), copy the zips to your phone, perform a full wipe (system, data, cache, dalvik cache), flash the ROM + gapps, reboot and start fresh.
Transmitted via Bacon
The only backup you should be restoring using TiBu after flashing a ROM are user apps, and certainly not system apps. Restoring system apps will cause problems in 99.9% of all cases.
I'm kind of thinking that it's my TWRP that has some issue. I've tried restoring 3 or 4 different backups and they all come up with the same error.
I'll update my TWRP when I get home and hopefully get a bit further...
Gamm86 said:
The only backup you should be restoring using TiBu after flashing a ROM are user apps, and certainly not system apps. Restoring system apps will cause problems in 99.9% of all cases.
Click to expand...
Click to collapse
He's talking about a nandroid backup, not a TiBu backup.
Transmitted via Bacon
timmaaa said:
He's talking about a nandroid backup, not a TiBu backup
Click to expand...
Click to collapse
I know, just talking about restoring backups in general after flashing a ROM.
Hence why I said "The only backup you should be restoring..."
EDIT* misread the OP. My posts were indeed a bit out of context...
Did a clean install - no dice
Then did an install without gapps and then I get to the initial setup where I have to choose language. And then it reboots - over and over. It completely bypasses any indication that there is a SIM card in the phone.
When trying to restore my previous backups I also go straight to my home screen bypassing SIM unlock and phone unlock.
Any other suggestions?
Have you tried step 8 from the following thread: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Gamm86 said:
Have you tried step 8 from the following thread: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Click to expand...
Click to collapse
Either that or this automated tool:
http://forum.xda-developers.com/showthread.php?t=2970390
Transmitted via Bacon
Gamm86 said:
Have you tried step 8 from the following thread: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Click to expand...
Click to collapse
Nope. But I'm going to now Stay tuned...
Well... it's a different bootanim than CM11 - first indication that something has happened
But then Reboot from the language selection screen
I guess I'm coming to an end in terms of my phones life
kroogar said:
Nope. But I'm going to now Stay tuned...
Well... it's a different bootanim than CM11 - first indication that something has happened
But then Reboot from the language selection screen
I guess I'm coming to an end in terms of my phones life
Click to expand...
Click to collapse
Not necessarily. Do you have any signal whatsoever? Can you navigate to Settings/About Phone and see your IMEI? Don't post it here but let me know if it's still showing up.
Transmitted via Bacon
Hmm, sounds like a hardware issue to me if you can't even get passed the welcome setup without your phone rebooting... Especially after a FULL factory reset.
Does the reboot start as soon as you touch the screen? This might indicate some kind of malfunction between hardware and drivers.
Raise a ticket on the OnePlus website and request for an RMA. You might also want to file a Paypal claim to speed things up.
timmaaa said:
Not necessarily. Do you have any signal whatsoever? Can you navigate to Settings/About Phone and see your IMEI? Don't post it here but let me know if it's still showing up.
Click to expand...
Click to collapse
I can't navigate as I'm blocked by the error message. I do know my IMEI from my Google dashboard though.
I'm still puzzled by the fact that it doesn't recognize my SIM card at all.
Okay - breakthrough: I downloaded the package from this post: http://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
Ran all 3 ONEPLUS ONE - x.bat and now it has prompted me to unlock my sim card. Got through to wifi so I have higher hopes this time around Will see how it goes...
kroogar said:
I can't navigate as I'm blocked by the error message. I do know my IMEI from my Google dashboard though.
I'm still puzzled by the fact that it doesn't recognize my SIM card at all.
Click to expand...
Click to collapse
Whether you know your IMEI or not isn't the point, it's whether it's still present on your device that matters. There have been cases where the IMEI simply disappears (along with your baseband) and having no signal is a consequence of that. I hope you made a backup of your EFS at some point because it's looking like this is what's happened.
Have you tried the automated tool I linked to a few posts back?
Transmitted via Bacon
timmaaa said:
Have you tried the automated tool I linked to a few posts back?
Click to expand...
Click to collapse
Se my updated previous post
kroogar said:
Se my updated previous post
Click to expand...
Click to collapse
Ok, so you're all good now? You have mobile signal? You can see your baseband version and IMEI in the settings menu?
Transmitted via Bacon
timmaaa said:
Ok, so you're all good now? You have mobile signal? You can see your baseband version and IMEI in the settings menu?
Click to expand...
Click to collapse
Yes I see it and I can send and receive text messages.
Now I'm going to try to restore one of my previous backups again
Thanks a ton for all the help to the both of you. If I could I'd /dcc you a cold one.
kroogar said:
Yes I see it and I can send and receive text messages.
Now I'm going to try to restore one of my previous backups again
Thanks a ton for all the help to the both of you. If I could I'd /dcc you a cold one.
Click to expand...
Click to collapse
Be careful, I firmly believe it's a backup that caused this problem, and you might not be so lucky next time. I'd seriously suggest just clean flashing now or you could be inviting the devil to your doorstep.
Transmitted via Bacon
Hey guys,
So I flashed this rom two weeks back http://forum.xda-developers.com/oneplus-one/development/rom-paranoidandroid-5-0-alpha1-t2956478
after running cm12s nightlies for a while. The capacitive keys stopped working after I flashed this rom with the PA gapps and they still don't work after trying multiple roms + relocking unlocking bootloader and flashing 44s. Kinda frustrated cause I don't know what I can do. Any ideas?
Thanks
How did you flash 44S?
Transmitted via Bacon
I first tried flashing it through twrp. Then I used the OnePlus customer support recovery tool to get it back to stock 44s. No luck zz
Sanjitha.d said:
I first tried flashing it through twrp. Then I used the OnePlus customer support recovery tool to get it back to stock 44s. No luck zz
Click to expand...
Click to collapse
By recovery tool you mean flashing with fastboot, right?
Transmitted via Bacon
Naah it was an actual tool that OnePlus customer support gave me that restored the device t to stock. But yeah I was in bootloader when I used it. Essentially it reverted the software to factory.
So I was wondering if there were any deeper settings that might have changed. The buttons still light up but don't respond to touch.
Sanjitha.d said:
Naah it was an actual tool that OnePlus customer support gave me that restored the device t to stock. But yeah I was in bootloader when I used it. Essentially it reverted the software to factory.
So I was wondering if there were any deeper settings that might have changed. The buttons still light up but don't respond to touch.
Click to expand...
Click to collapse
That's what I meant, that's flashing with fastboot. The only thing I can think of doing is completely wiping your phone including user data (back up important files first) and flashing the stock images again, but manually this time. You can find a download and instructions in section 8 of my guide thread.
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Alright, I've also tried manually flashing the stuff myself but I'll do it according to your guide to see if it works. You don't think it could be anything software/firmware related after that yeah? I remember there was a guy who said that he had to do a full wipe to make the cap keys to work on the initial pa thread but actually no idea on how this screwed up lel
Yeah, no luck man. I flashed everything manually but no luck zz. There's nothing else I could change to see if it's the problem yeah? I'm pretty sure the problem isnt physical as I haven't dropped it or done any harm to it.
I don't know much about kernels and stuff but that wouldnt be the problem either right?
No other stock firmwares or radios or something I havent heard about?
Sanjitha.d said:
Yeah, no luck man. I flashed everything manually but no luck zz. There's nothing else I could change to see if it's the problem yeah? I'm pretty sure the problem isnt physical as I haven't dropped it or done any harm to it.
I don't know much about kernels and stuff but that wouldnt be the problem either right?
No other stock firmwares or radios or something I havent heard about?
Click to expand...
Click to collapse
So you wiped the whole phone? Even the internal storage? If so, and the problem persists, it's suggesting a hardware problem. You could try a custom kernel though just in case, it wouldn't hurt.
Transmitted via Bacon
timmaaa said:
So you wiped the whole phone? Even the internal storage? If so, and the problem persists, it's suggesting a hardware problem. You could try a custom kernel though just in case, it wouldn't hurt.
Transmitted via Bacon
Click to expand...
Click to collapse
Sorry for the inconvenience but could you suggest a couple? (for cm12 nightlies if possible)
Thanks
And there should be no other software things I could change right?
I was reading before about oneplus not using double sided tape on their digitizers and using glue instead and as such sometimes touch responsiveness in some places might of been removed in some of the earlier models. Although oneplus said that was just a software glitch but iderrrnooooo.
Thanks for the help man c:
Sanjitha.d said:
Sorry for the inconvenience but could you suggest a couple? (for cm12 nightlies if possible)
Thanks
And there should be no other software things I could change right?
I was reading before about oneplus not using double sided tape on their digitizers and using glue instead and as such sometimes touch responsiveness in some places might of been removed in some of the earlier models. Although oneplus said that was just a software glitch but iderrrnooooo.
Thanks for the help man c:
Click to expand...
Click to collapse
Can't really suggest one because I don't use them, but you'll find them all listed in my index thread here:
http://forum.xda-developers.com/showthread.php?t=2843675
I can't think of anything else on the software/firmware side of things, everything has been wiped and reflashed.
Transmitted via Bacon
I have a similar issue. The softkeys stopped working right after i unlocked the bootloader. They light up but do not respond. can anything be done? I unlocked the bootloader via adb.
My phone is stuck in a boot loop.
The Oneplus one toolbox says "waiting for device".
My phone is not recognised by windows. when i try to install the drivers again, "android phone" is not on the list. i dont have twrp installed.
Dont really care about the data at the moment. Can someone help me?
Shounak Gupte said:
My phone is stuck in a boot loop.
The Oneplus one toolbox says "waiting for device".
My phone is not recognised by windows. when i try to install the drivers again, "android phone" is not on the list. i dont have twrp installed.
Dont really care about the data at the moment. Can someone help me?
Click to expand...
Click to collapse
The first thing you need to do is get rid of the toolbox. Nothing but trouble. Plus, if you can't modify your phone without a toolbox you shouldn't be modifying it at all. Uninstall whatever drivers you have installed, reboot the PC, install these drivers, reboot PC again, connect phone, flash stock images (see section 8 of my guide thread).
Exactly how did your phone get into the boot loop?
Transmitted via Bacon
drivers
timmaaa said:
The first thing you need to do is get rid of the toolbox. Nothing but trouble. Plus, if you can't modify your phone without a toolbox you shouldn't be modifying it at all. Uninstall whatever drivers you have installed, reboot the PC, install these drivers, reboot PC again, connect phone, flash stock images (see section 8 of my guide thread).
Exactly how did your phone get into the boot loop?
Transmitted via Bacon
Click to expand...
Click to collapse
i've uninstalled the drivers and installed the ones you suggested. my PC still doesnt recognise the phone(check image attached). any solutions?
i was browsing something on chrome and the phone suddenly got stuck. i restarted the phone, but then was stuck on the loading screen.
Shounak Gupte said:
i've uninstalled the drivers and installed the ones you suggested. my PC still doesnt recognise the phone(check image attached). any solutions?
i was browsing something on chrome and the phone suddenly got stuck. i restarted the phone, but then was stuck on the loading screen.
Click to expand...
Click to collapse
Did you reboot the PC between each uninstall and install? Are you using the official OnePlus usb cable?
Transmitted via Bacon
timmaaa said:
Did you reboot the PC between each uninstall and install? Are you using the official OnePlus usb cable?
Transmitted via Bacon
Click to expand...
Click to collapse
Yes... i did. I was reading somewhere and someone suggested using a different cable or a different PC. i'll try both today at work and report back.
no luck
Shounak Gupte said:
Yes... i did. I was reading somewhere and someone suggested using a different cable or a different PC. i'll try both today at work and report back.
Click to expand...
Click to collapse
ok.. so another computer & cable worked.
I've followed your tutorial.
first unlocked the bootloader.
then section 8 all of it.
still nothing. i'm still on the oneplus loading screen. any other options?
Shounak Gupte said:
ok.. so another computer & cable worked.
I've followed your tutorial.
first unlocked the bootloader.
then section 8 all of it.
still nothing. i'm still on the oneplus loading screen. any other options?
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=2970390
Transmitted via Bacon
timmaaa said:
Try this:
http://forum.xda-developers.com/showthread.php?t=2970390
Transmitted via Bacon
Click to expand...
Click to collapse
awesome!! this worked. i lost all data though.
any tips on how to prevent the magical boot screen?
Shounak Gupte said:
awesome!! this worked. i lost all data though.
any tips on how to prevent the magical boot screen?
Click to expand...
Click to collapse
I'm pretty sure you just got unlucky and had a corrupt persist partition, it's a bug that has happened to a few people, that particular automated flash tool flashes the stock images plus it flashes the persist partition. There isn't really anything you can do it avoid it, but i don't think I've seen it affect the same phone twice.
Transmitted via Bacon
timmaaa said:
I'm pretty sure you just got unlucky and had a corrupt persist partition, it's a bug that has happened to a few people, that particular automated flash tool flashes the stock images plus it flashes the persist partition. There isn't really anything you can do it avoid it, but i don't think I've seen it affect the same phone twice.
Transmitted via Bacon
Click to expand...
Click to collapse
i think i spoke a bit too soon. everything worked fine, but now my phone is getting stuck when it boots. the screen it totally unresponsive. this was the same thing which happened when i restarted my phone. it might be some app i have installed.
i might have to redo the process.
is there a way to find out which one it is?
The only real way to find out would be to start fresh and introduce apps one at a time to see which one is the culprit. But I'd be surprised if an app was causing this.
timmaaa said:
The only real way to find out would be to start fresh and introduce apps one at a time to see which one is the culprit. But I'd be surprised if an app was causing this.
Click to expand...
Click to collapse
I did the whole process 2 times. the phone works fine for a few days and now its stuck in the boot loop again. I have already contacted OPO support, but waiting for them to get back to me.
any solutions in the mean time?
Shounak Gupte said:
I did the whole process 2 times. the phone works fine for a few days and now its stuck in the boot loop again. I have already contacted OPO support, but waiting for them to get back to me.
any solutions in the mean time?
Click to expand...
Click to collapse
Did you install your apps again or is this still happening without them?
timmaaa said:
Did you install your apps again or is this still happening without them?
Click to expand...
Click to collapse
i installed them one at a time. its all the usual apps. nothing special. the phone worked fine until today morning.
I think you'll need to talk to OnePlus support about this, it doesn't seem right especially after using their own reflash tool.
timmaaa said:
I think you'll need to talk to OnePlus support about this, it doesn't seem right especially after using their own reflash tool.
Click to expand...
Click to collapse
the OPO support cannot seem to fix the issue. they have asked me to send them the phone back and i might get a replacement.
the issue is, I'm in Australia. the nearest location I can ship to is HK. There's going to be a long wait for my replacement to arrive. any other solutions?
Shounak Gupte said:
the OPO support cannot seem to fix the issue. they have asked me to send them the phone back and i might get a replacement.
the issue is, I'm in Australia. the nearest location I can ship to is HK. There's going to be a long wait for my replacement to arrive. any other solutions?
Click to expand...
Click to collapse
I've gone through any potential solution that I know of. I'm in Australia too, it sucks, but we took a risk when buying this phone that something like this might happen.
Transmitted via Bacon