Hi All,
I've searched across forum to find also similar cases, but no results so far.
I have a N4 with TWRP and CM (previously running 10.1.2)
Today I decided to install the new 10.2.
Installation went fine but after the restart I've noticed some strange behaviour with some applications (missing from phone, but installed for my play store account)
I've decided to reboot again the phone, and since that time I'm stuck with the black start up Google screen (the one with the lock at the bottom).
Entered recovery mode, I've wiped Dalvik, Cache and System, but no results, rebooting is always stuck on Google screen (I've also left it there for 15+ minutes, no changes)
I've tried to install a previous ROM (zip available on phone storage) but no result even in this case.
Any help or suggestion would be much appreciated, even a link pointing to similar case happened in the past.
Let me know if any further detail may be needed to better understand the situation
Thanks!
mh a wipe/factory reset should be working...
Try pushing a different rom with ADB to your device, then flash it.
Sent from my Nexus 4 with Tapatalk 4
This is usually happening when you don't flash something right. I'd go back, flash it all again with wiping everything and flashing it by the right order and stuff. If it doesn't work, as written above, flash other ROM through ADB or something similar.
Besides, you could always restore your nandroid backup, and if you don't have one, learn from your mistake
Good luck
Sent from my Nexus 4 using xda app-developers app
To be honest, I've already tried to revert back to previous CM and even to the factory image from Google, but it always hang on the google screen.
I've not yet Format/completely wiped the phone, and that's my last option.
Once I'm done with the manual backup I'm doing via adb shell, I will try again to flash a new ROM, and see what happen.
Definitely I'm learning from my mistakes
So, I have read a lot about TWRP sometimes bugging out and randomly encrypting phones and adding a password to which the user either never set it up or that TWRP doesn't accept it. This has recently happened to me and I cannot use my phone and I don't know what to do.
I have had the bootloader of my phone unlocked since day 1 when I bought my phone (release date last year) and have been running PA ever since. I have never had any problems with it, until about 5 days ago, when I grabbed my phone and everything started crashing and the camera was apparently not available. I didn't know what was the deal with it, so I rebooted the phone and it entered a bootloop (it hangs on the Google logo for about 5 minutes and then it hangs on the PA logo screen forever). I went on to the bootloader and started TWRP to see what was the deal. I originally wanted to grab certain files off the phone in case I had to do a system format, but when I got to TWRP, it asked me for a password which I have never set up and I tried every combination I could think of but it always failed. Everything was encrypted and without the password I couldn't get to it. I tried wiping everything including a factory reset before resorting to a system format (which I read about it and apparently is meant to be the solution). Everything failed because it couldn't access the /cache, /data, nothing. I went on to do a system format and although that is meant to wipe the phone and remove encryptions, it also failed to wipe the /cache and although TWRP says that the wipe is successful, the phone is still encrypted, the password is still around and it bootloops. I have tried the system format like 50 times and always the same.
Can anyone help me out with this? I am currently travelling around but am at a hostel where there is great internet and pcs, so I can install drivers, toolkits and such. I actually started looking around for new phones, since I cannot for the life of me get the phone to start again.
Note: The phone was working perfectly fine, I put it down to have dinner and once I finished, I tried to use it and it started to bug out. I also read around about this, and everyone's issue gets fixed after a system format.
Any help, would be greatly appreciated, that phone is the only net device I have on this trip and it sucks to not have any way to contact anyone.
Thanks.
Bump
Don't blame TWRP for something it doesn't do.
Looks like your device have an EMMC failure, sorry.
You can try installing factory image, or last resort restoring by download mode, but I think the flash memory in your phone is gone.
http://forum.xda-developers.com/showthread.php?t=2347060
sent from nexus 4
eksasol said:
Don't blame TWRP for something it doesn't do.
Looks like your device have an EMMC failure, sorry.
You can try installing factory image, or last resort restoring by download mode, but I think the flash memory in your phone is gone.
http://forum.xda-developers.com/showthread.php?t=2347060
sent from nexus 4
Click to expand...
Click to collapse
I didn't mean to blame TWRP. It is just that it was when I am on it that I get asked for the password and I was under the impression that it was TWRP that did the encrypting (I am in no way a developer or even very knowledgeable when it comes to the under the hood stuff, I usually only follow the tutorials). But thanks for the reply and the link, I will try that and hopefully get the phone back working.
Also, I did read in a thread that apparently this can occur due to hardware failure, I was just hoping this wasn't the case.
This happened to me on an old phone. Not sure why. Factory image fixed it. Could be a different issue but its worth a shot.
Sent from my Nexus 4 using XDA Premium 4 mobile app
It's happening to me now too
Sent using T-Mobile S4 4.3 MK2
LEGEND94 said:
It's happening to me now too
Sent using T-Mobile S4 4.3 MK2
Click to expand...
Click to collapse
Did it suddenly happen or did you change ROMs?
I tried a new rom for the first time and then went back to wicked 9.1, I'm thinking that triggered something.
I think I got a fix though, look here: http://forum.xda-developers.com/showthread.php?t=2588377
Sent using T-Mobile S4 4.3 MK2
A few people have had issues with the EFS getting corrupt or wiped on their OPO before they had a working backup. This guide has so far worked for 4 people to restore their EFS allowing them to access mobile data and bluetooth again.
Note: I really don't know why this works, I have contacted the dev of this rom to ask if he has any ideas but still waiting on a response.
1. Flash official TWRP
2. Flash this ColorOS rom using TWRP - http://forum.xda-developers.com/showthread.php?t=2772627 (you can skip all the account setups if you want)
3. Factory reset
4. Boot and setup ColorOS (you should see a network connect now with your sim card inserted, you will need to toggle mobile data on to test that)
5. If you have data in ColorOS you are good to flash back to CM11S anyway you want (you will need to factor reset after flashing back)
6. Save yourself the headache in the future and backup your EFS
Please post if this fix works for you.:victory:
Edit: I've went ahead and downloaded the ROM and I will hold on to it incase the original mirrors go down for some reason. Please PM me if they do.
One of the ones who can confirm this works. Will post in the official thread.
Worked for me also.
Wholy moly ... I have a mobile data network !!
Still on ColorOS, but this is VERY promising !!!
IMEI is correct, it's the one on the box !
Still no WiFi nor Bluetooh mac addresses, though...
Will keep you posted, but this is a HUGE step forward !
Thanx a lot for sharing this !
BTW, serial number is still unchanged and correct.
JP.
EDIT:
Unfortunately it didn't fix my issue, back to CM11S I am greeted by an AudioFX FC... Device pretty much unusable, the FC pops up the milisecond you click OK ...
Will try a different ROM...
EDIT 2:
SlimKat, CM11 Nightly both boot to the welcome screen, then reboot about 1 second later.
Only ColorOS seems to actually run ?!
A bit disgusted right now
tw1tch175 said:
A few people have had issues with the EFS getting corrupt or wiped on their OPO before they had a working backup. This guide has so far worked for 3 people to restore their EFS allowing them to access mobile data and bluetooth again.
Note: I really don't know why this works, I have contacted the dev of this rom to ask if he has any ideas but still waiting on a response.
1. Flash official TWRP
2. Flash this ColorOS rom using TWRP - http://forum.xda-developers.com/showthread.php?t=2772627 (you can skip all the account setups if you want)
3. Factory reset
4. Boot and setup ColorOS (you should see a network connect now with your sim card inserted, you will need to toggle mobile data on to test that)
5. If you have data in ColorOS you are good to flash back to CM11S anyway you want (you will need to factor reset after flashing back)
6. Save yourself the headache in the future and backup your EFS
Please post if this fix works for you.:victory:
Click to expand...
Click to collapse
Hi, i failed and i wiped EVERYTHING of my phone, i only had the fasboot mode, i installed CWM and the cyanogemod rom, now everything works, and i have the imei in the box, however, i dont have the possibility of EFS backup anymore.... any ideas..?
Gambalajillo said:
Hi, i failed and i wiped EVERYTHING of my phone, i only had the fasboot mode, i installed CWM and the cyanogemod rom, now everything works, and i have the imei in the box, however, i dont have the possibility of EFS backup anymore.... any ideas..?
Click to expand...
Click to collapse
Official TWRP doesn't have EFS backup in it, you have the get the unofficial one http://forum.xda-developers.com/oneplus-one/development/recovery-unofficial-twrp-2-7-1-0-t2815247
Yank555 said:
Wholy moly ... I have a mobile data network !!
Still on ColorOS, but this is VERY promising !!!
IMEI is correct, it's the one on the box !
Still no WiFi nor Bluetooh mac addresses, though...
Will keep you posted, but this is a HUGE step forward !
Thanx a lot for sharing this !
BTW, serial number is still unchanged and correct.
JP.
EDIT:
Unfortunately it didn't fix my issue, back to CM11S I am greeted by an AudioFX FC... Device pretty much unusable, the FC pops up the milisecond you click OK ...
Will try a different ROM...
EDIT 2:
SlimKat, CM11 Nightly both boot to the welcome screen, then reboot about 1 second later.
Only ColorOS seems to actually run ?!
A bit disgusted right now
Click to expand...
Click to collapse
Odd, maybe you could try using TWRP to delete everything again including system, then sideload and boot ColorOS.
tw1tch175 said:
Official TWRP doesn't have EFS backup in it, you have the get the unofficial one http://forum.xda-developers.com/oneplus-one/development/recovery-unofficial-twrp-2-7-1-0-t2815247
Click to expand...
Click to collapse
To add to that you can just boot the unofficial recovery using "fastboot boot recovery.img" to do your efs backup if you would prefer to keep the official TWRP installed. That way it only boots that recovery to allow you to do the backup of your EFS partition and doesn't erase your current recovery. That's how I did it.
sabbotage said:
To add to that you can just boot the unofficial recovery using "fastboot boot recovery.img" to do your efs backup if you would prefer to keep the official TWRP installed. That way it only boots that recovery to allow you to do the backup of your EFS partition and doesn't erase your current recovery. That's how I did it.
Click to expand...
Click to collapse
WOW thanks, i do it and and i tell you how did it go in a few minutes.
I see that the OP has been thanked and this thread has a few success stories so I am giving it a bump for others to view in case of the same issue.
I just flashed the factory image... I never had the problem again
Yank555 said:
Wholy moly ... I have a mobile data network !!
Still on ColorOS, but this is VERY promising !!!
IMEI is correct, it's the one on the box !
Still no WiFi nor Bluetooh mac addresses, though...
Will keep you posted, but this is a HUGE step forward !
Thanx a lot for sharing this !
BTW, serial number is still unchanged and correct.
JP.
EDIT:
Unfortunately it didn't fix my issue, back to CM11S I am greeted by an AudioFX FC... Device pretty much unusable, the FC pops up the milisecond you click OK ...
Will try a different ROM...
EDIT 2:
SlimKat, CM11 Nightly both boot to the welcome screen, then reboot about 1 second later.
Only ColorOS seems to actually run ?!
A bit disgusted right now
Click to expand...
Click to collapse
Im having the same problem as you have Yank555. It started with the AudioFX FCs rendering the device useless.
Next i tried to reflash the standard CM11s 25R rom back to get my phone normal again, it didnt work.
Then i remember i have a nandroid from a few days ago. Not thinking to read up on known issues with the OPO EFS i tried a restore.
My EFS is gone and the phone will not work unless im on ColourOs120. Wifi doesnt work, just basic phone functions.
Still waiting for a miracle for this problem.
Any suggestion guys?
jwai85 said:
Im having the same problem as you have Yank555. It started with the AudioFX FCs rendering the device useless.
Next i tried to reflash the standard CM11s 25R rom back to get my phone normal again, it didnt work.
Then i remember i have a nandroid from a few days ago. Not thinking to read up on known issues with the OPO EFS i tried a restore.
My EFS is gone and the phone will not work unless im on ColourOs120. Wifi doesnt work, just basic phone functions.
Still waiting for a miracle for this problem.
Any suggestion guys?
Click to expand...
Click to collapse
Did you open a service request ? Any response ? So far all I got 5 days later was a "please fastboot flash factory images, case closed." which quite obviously did not help, so case reopened, but again nothing from them in 4 days, now.
But I wonder if my first thought is still correct, flawed emmc as flashing seems to work ... might be a radio hardware issue ? Just don't quite get what the AudioFX has to do with that... cause simply rooting the device and installing apps and making a few nandroid backups is no way to brick anything.
But anyway, tbh, OnePlus is mostly dead to me as a company, worst invest ever so far, nice if your device works, but service is not even close to bad, it's pretty much non-existing ... and for a supposedly "best service ever" it's quite, let's say, "impressing"
JP.
Nope, i have not tried opening a ticket, mine is a grey import from China.
There is something terribly wrong somewhere hardware wise. The audiofx problem only happens if i flash the CM11s. After ColourOS i have tried flashing the CM11 M8.
Im also wondering if i should try to use this OPO made rom to see if it can help.
https://forums.oneplus.net/threads/rom-official-4-4-4-oneplus-aosp.65482/
jwai85 said:
Nope, i have not tried opening a ticket, mine is a grey import from China.
There is something terribly wrong somewhere hardware wise. The audiofx problem only happens if i flash the CM11s. After ColourOS i have tried flashing the CM11 M8.
Im also wondering if i should try to use this OPO made rom to see if it can help.
https://forums.oneplus.net/threads/rom-official-4-4-4-oneplus-aosp.65482/
Click to expand...
Click to collapse
Give it a go, not much to lose. Didn't work for me, though.
JP.
Sent from my Nexus 5 running stock rooted AOSP on Yank555.lu v1.0-alpha5 kernel.
This worked for me! I'm back in business! Thanks guys for getting this figured out, I thought my phone was done.
I hate to bring this back up.
I have a Nandroid of my stock CM11S on my phone. I used it for the update to 300 to get firmware, then made a backup of it and went back to the custom Rom I had been on.
Today, I went and restored the backup of CM11S to sideload the newest update. Weirdly, after restoring I have an unknown baseband. But if I go back to the custom Rom backup I still have a baseband.
I wonder if TWRP just didn't backup the correct partitions? I am on the offficial TWRP. But I do have a backup that contains my EFS backup from the other TWRP that has that option.
I think I know what corrupted my efs....I used the official twrp 2.7.1.1 which for some reason saves modemst1. I remember restoring st1 when I corrupted it the first time with the official 2.7.1.1. Well I did it again trying to restore a nandroid with the official twrp 2.7.1.1. Do not restore the saved modemst1 from the official twrp 2.7.1.1. You will encounter problems.
So, this same thing happened to me...i happily using 30O and not really any issues and getting good battery life~17 hrs w/moderate use. And no other bugs.
Found the 33R update here on the forums and downloaded it and flashed through TWRP.
Thats when trouble found me, lost network and wifi stuck trying to turn on but never finds wifi. Then reading through xda someone suggested to check IMEI and it was gone. I had NOT done any prior back ups other than Nandroid prior to flashing update.
Restore still didn't fix it.
I tried this (flash ColorOS and CM11) but still didnt fix it. I was bummed as my OPO is very new and I had been happy with it.
CM11 or by restore, windows will not detect it even with drivers loaded. Flashing colorOS would allow windows XP to recognize internal and allow me to send files so i tried custom ROMs and CM stock and Mahdi but none worked. Luckily my TWRP still works and i am able to boot and get into fasboot.
I finally got mine fixed with rooted stock 33R from here on xda!
Now my OPO is back in business!!!
Save st1 and st2 with vonnegut's method http://forum.xda-developers.com/showthread.php?p=54623075.. Put it in a safe place for later. I uploaded them to google drive and onedrive . It saved me today.
For those of you that were able to recover, did you lose your entire EFS folder? Mine is completely gone and I don't think this ColorOS trick works either. I've tried it all last night and I fell asleep at my desk
My G2 has been acting really funky lately, hanging on boot and not being able to "hold" recovery flashes. I'll start from the beginning of my little story.
On Saturday, I wanted to do a nandroid backup from TWRP (not sure which version, an older one but not terribly old). It failed several times. I went back into the OS (CM 12.1) and backed up all apps and app data to an OTG USB via Titanium Backup. This was successful. I tried to go back into TWRP a second time. Nothing. Recovery is not even there, I get a security error from what I believe is fastboot. I went back to CM and tried to re-flash TWRP. Now I get a security error on the LG screen. Nothing would boot, no recovery mode, I did have download mode although I had no PC with me so I didn't know this at the time. I was away last weekend so I had to go without a phone for a day... which was actually... kind of pleasent. Don't ask me why I carried two 32GB USBs and an OTG adapter on my keychain but no laptop, because I have no idea why I would do this, lol.
Came home Sunday afternoon and decided to nuke the whole phone with a TOT flash. Since I always wanted to try CloudyG2 since we all know AOSP-based ROMs don't do the camera justice, I went ahead and TOT flashed, re-rooted, re-AutoRec, etc. Everything worked wonderfully; I did a full wipe in TWRP, flashed in Cloudy, then the KK radio, then Xposed. Played around with things like XCam and a few Xposed modules. Everything was working awesome, so I did my restore in Titanium. Took a few hours, but Titanium says everything went fine (sans for a few CM apps which did not restore by design I guess). I checked out a few apps, all my data is there, wonderful. Titanium told me to restart so after poking around a bit, I went for the restart. Hang on boot. For several hours. Tried to go to recovery, fastboot security error. Seems it can't "hold" recovery or something else that I'm flashing?
Clearly I am doing something incorrect here with flashing and all that, but I can't figure out what. I'm not new to flashing and modding, and I've flashed regular CM updates and other goodies onto this G2 for quite a while with no issues. I'm going through the same steps I would normally with CM, and I've had plenty of success with that. Any ideas what I am doing wrong here?
Had same issue and know I hard bricked it trying to get it fixed ... Off to a different phone I guess .. Not sure why it wouldn't hold a recovery either after a few hours ... I gave up .. Good luck
Sent from my SCH-I535 using XDA Premium 4 mobile app
Hello all
I am having a little bit of trouble with my TWRP recovery after flashing an updated version of a custom ROM, i have been using for a while.
I am using the latest version of the Pure Nexus ROM, and am currently un-rooted. I earlier want to try and clear my davlik cache as i was having a few little issues with some things, and wiping this has previously fixed the issue, i rebooted into the TWRP, and was asked for a password, which i thought would have been the PIN i use to unlock my phone. This then failed, and it proceeded to try and decrypt the partition. I left it doing this for about 20 mins, but nothing happened.
After reading up a little more, and trying a few different potential passwords to no avail, i read up that the password that TWRP was asking me for was related to the fact i had my phone set to ask for password on boot.
I removed this, and tried again. This time, TWRP just got stuck on the splash screen when trying to boot. Nothing happened for a good 10 minutes.
After putting the PIN settings back on, it goes back to asking for a password, that it wont take.
Whats my next option here, im kinda stuck. I really dont want to have to wipe the phone as i have just spent the best part of a week after flashing my new ROM getting it all back to how it was after flashing the new custom ROM i am using..
All help, much appreciated, thanks in advance
What version of TWRP are you using ?
No issues on TWRP 3.2.0.3
Sent from my Nexus 6P using Tapatalk
I'm on version 30.20