Related
Hi smart people!
Just to throw it out there, I am not very tech savvy so excuse me if I misuse terms and such.
I believe I completely bricked my phone (I hope I'm wrong). After I downloaded Cyanogen through ROM Manager, my finger stumbled on the "continue" or "next" button or whatever WITHOUT checking the boxes to clear data, etc. I believe this is where I went wrong as I think I followed all other steps correctly (fyi I used the one click recovery flasher and made a back up).
Now when I turn on my phone, it goes from the stock LG loading screen to a modified LG loading screen (Cyanogen's I'm assuming) but it gets stuck there.
I've been searching on the different threads for quite a while and pressing the different combinations of volume up/volume down/power don't seem to do anything. I cannot get to the recovery screen.
Please help! I will forever be indebted to all of you. I am stupid and shouldn't have tried to do this on my own. Thanks in advance
What you will need to do is flash CWM via NVflash then boot into CWm and install your ROM.
If you flash CWM via ROM Manager it causes problems like what you're describing, I know from my own experience of following a friends instructions and doing that then having that exact issue. After getting my phone working again I then started to frequent the boards here.
As soon as I read the first couple lines I saw rom manager and saw the problem, you to search something that you have typed out all within this thread... I'm not near a computer but you should just search through these threads and you find your solution in detailed description. You need to get recovery from nvflasher just search that
Sent from my LG-P999 using xda premium
thanks for your replies
thank you to both of you for your prompt replies. i will try doing this within the next couple hours and post any results. this is the thread i found with the information you guys gave: http://forum.xda-developers.com/showthread.php?t=1058649
thanks again
No, that's not for G2x. Go here: http://forum.xda-developers.com/showthread.php?t=1056847
Ya it needs to be the one that gunnman wrote out for people.
Sent from my LG-P999 using xda premium
Hey guys...on step #10, it says to "select 'have disk'" but i do not see that option in the list.
Thanks
okay now i realize i should have been doing the cwm recovery. sorry guys and thanks again
reboot error
hey guys,
I successfully was able to boot into cwm and then i restored a backup from yesterday. however when rebooting, it displays the LG logo and then the screen goes black and the back light flickers on and off. not quite sure what to do now...if you guys could let me know what i should do or post a link to another thread, i'd really appreciate it. i honestly have been going through other threads but i guess i'm just not competent enough to know which directions apply to my problem.....
thank you..hopefully this is the last time i'll have to bother you!
The back-up could be corrupt and since the one time I had a problem with a nandroid was when it was created after ROM Manager sent the info to CWM, that's likely the case. Just redownload CM7 to your SD card, along with Gapps, wipe system, data and cache then flash CM7 followed by Gapps.
justintheshark30 said:
hey guys,
I successfully was able to boot into cwm and then i restored a backup from yesterday. however when rebooting, it displays the LG logo and then the screen goes black and the back light flickers on and off. not quite sure what to do now...if you guys could let me know what i should do or post a link to another thread, i'd really appreciate it. i honestly have been going through other threads but i guess i'm just not competent enough to know which directions apply to my problem.....
thank you..hopefully this is the last time i'll have to bother you!
Click to expand...
Click to collapse
Have you wiped everything before restoring your backup through CWM? If not, boot into CWM, wipe data/factory reset, go to mounts and storage, format system, then go into advanced options, wipe delvik cache, then restore your backup.
I'm guessing you did a backup through rom manager, so if this doesn't work, you'll have to download a rom of your choice from the development section of this forum, load it onto your sd card through CWM although this is not recommended but you won't have any other choices, (to mount your sd card in CWM, go to mounts and storage, mount sd card), then wipe everything as mentioned above, then flash the new rom.
Or you can follow the instructions on this thread http://forum.xda-developers.com/showthread.php?t=1248644 to flash 2.3.3 via nvflash to get a working phone for now until you learn how to properly flash custom roms.
Hope this helps
P.S. for future reference, you did not brick your phone, you got stuck in a boot loop, you know your phone is bricked when you don't see anything on the screen when you turn it on, usually it's just a software issue, but sometimes it could be hardware, for example I burned the motherboard on my previous android phone trying to customize it lol
jj_z1 said:
Have you wiped everything before restoring your backup through CWM? If not, boot into CWM, wipe data/factory reset, go to mounts and storage, format system, then go into advanced options, wipe delvik cache, then restore your backup.
I'm guessing you did a backup through rom manager, so if this doesn't work, you'll have to download a rom of your choice from the development section of this forum, load it onto your sd card through CWM although this is not recommended but you won't have any other choices, (to mount your sd card in CWM, go to mounts and storage, mount sd card), then wipe everything as mentioned above, then flash the new rom.
Or you can follow the instructions on this thread http://forum.xda-developers.com/showthread.php?t=1248644 to flash 2.3.3 via nvflash to get a working phone for now until you learn how to properly flash custom roms.
Hope this helps
Click to expand...
Click to collapse
He's already flashed CWM the right way, and tried to restore from a nandroid. I already mentioned getting a different ROM, he's already stated that he got this all started trying to flash CM7. Please read the posts which have already been made, we don't need the same information being posted again, if someone already posted something and you feel it needs clarified then clarify but from what I can tell you read one post and that was it.
Волк said:
He's already flashed CWM the right way, and tried to restore from a nandroid. I already mentioned getting a different ROM, he's already stated that he got this all started trying to flash CM7. Please read the posts which have already been made, we don't need the same information being posted again, if someone already posted something and you feel it needs clarified then clarify but from what I can tell you read one post and that was it.
Click to expand...
Click to collapse
I really hate posting anything that doesn't have to do with anything phone related but I just couldn't stop myself from replying to your post!
1) I actually read all posts in the thread!
2) I did not in any way suggest that he didn't flash CWM the right way, I merely asked if he had done a full wipe before restoring his backup!!
3) Your reply was submitted while I was typing mine, so I'm sorry I didn't check the thread again before submitting my reply!!!
4) I'm well aware of what he tried to do already, but thanks for repeating it!!!!
5) If YOU read all previous posts you'll notice that my post does not exactly replicate any other, there's some new information in there that the OP might find useful!!!!!
6) From what I can tell, you need to work on your english and comprehension skills!!!!!!
To the OP, sorry for trolling your thread with this post, but I just couldn't help it, and to Bonk I hope you'll be the mature one and not reply to this post.
Is that to say you're immature? If one were to judge by the number of exclamation marks you have I'd say yes.
The only "new" thing was asking if he wiped before the restore, which, at this point, would be useless to ask as I already told him to make sure to wipe.
To the OP: How goes everything thus far?
thank you
that's what i ended up doing and it worked. thank you so much for all your help!
Волк said:
The back-up could be corrupt and since the one time I had a problem with a nandroid was when it was created after ROM Manager sent the info to CWM, that's likely the case. Just redownload CM7 to your SD card, along with Gapps, wipe system, data and cache then flash CM7 followed by Gapps.
Click to expand...
Click to collapse
And dalvik cache for good measure, even though it is stored on the cache partition and will probably get wiped when you wipe cache. Sometimes it's good to overdo thing's.
Unable to do anything!
Well i was playing with the phone, rooted and kept playing with different ROMS till i would have found a good stable one, but something happened, I ended up not being able to use any functions in cwm (apply update from..., backup and restore, install from zip). I wiped data/factory reset, cache partition, dalvik and i have the ROMS inside, i can see them in CWM. just can't read them. or any zip i use. what happened? is this bricked? if so do i have to go from scratch with the phone and use SDK?
efrembarrow said:
Well i was playing with the phone, rooted and kept playing with different ROMS till i would have found a good stable one, but something happened, I ended up not being able to use any functions in cwm (apply update from..., backup and restore, install from zip). I wiped data/factory reset, cache partition, dalvik and i have the ROMS inside, i can see them in CWM. just can't read them. or any zip i use. what happened? is this bricked? if so do i have to go from scratch with the phone and use SDK?
Click to expand...
Click to collapse
Start over. Do what it states here: http://forum.xda-developers.com/showthread.php?t=1248644
efrembarrow said:
Well i was playing with the phone, rooted and kept playing with different ROMS till i would have found a good stable one, but something happened, I ended up not being able to use any functions in cwm (apply update from..., backup and restore, install from zip). I wiped data/factory reset, cache partition, dalvik and i have the ROMS inside, i can see them in CWM. just can't read them. or any zip i use. what happened? is this bricked? if so do i have to go from scratch with the phone and use SDK?
Click to expand...
Click to collapse
Did you battery pull and start over?
Sent from my LG-P999 using xda premium
UNROOT help
Hello again smart people,
I was hoping we would never meet again (for the better) but unfortunately i must unroot my phone to receive work emails. I have tried unrooting my LG G2x multiple times but to no avail thus far.
Here is the process I have tried:
1) boot into recovery - wipe cache/data factory reset, wipe cache partition, wipe dalvik cache
2) restore - using stock rom i found online
3) flash stock recovery image using nvflash
4) (attempt to) unroot using superoneclick - AFTER GOING THROUGH MULTIPLE STEPS, IT SAYS "TRUE" UNDER "CHECKING IF ROOTED". (also, i know it is rooted because it says the phone already appears to be rooted when i try to root again).
Do you guys have any idea what the issue could be?
Thank you in advance...
Hi all, I've been rooting and installing custom roms on lots of devices for a couple of years now. I didn't consider myself a noob after successfully getting cyanogen 9 or 10 on tenderloin and cm10.2 on tate.
However, it seems that I have completely missed something while installing EOS4 20130705-199 on the Motorola Xoom.
I had no problems with SDK install, adb, fastboot, got TWRP running w/ root. All this is from stock, mind you, if that makes any difference.
So then I decided to grab teamEOS's EOS4 and run that as the newest Android OS (that is arguably stable) that has been ported to the Xoom.
Well, I think I must have rebooted at a point that I wasn't supposed to, because I lost the ability to load the EOS-stingray-20130705-199.zip via ADB.
So I went into TWRP recovery and attempted to ADB sideload the rom file. Seemed to work for transferring, but after wiping caches and rebooting, I'm stuck on MOTO dual-core logo. I can get back into TWRP, though so I tried doing factory reset, wiping caches, and installing from an 8GB microSD card (/sdcard). Wiped caches again and then reboot... Same result, MOTO dual-core logo.
Ok, so now to barebones... Boot into fastboot mode and flash boot.img from EOS-stingray-20130705-199.zip and then boot back into TWRP and install rom again.... Same result, MOTO dual-core logo.
As you can probably guess at this point I'm getting a bit frustrated. I'm about ready to see how a Xoom flies when launched from a skeet clay launcher. Pull!..... BLAM! Just kidding, but I really do need to get this device back running.
Does anybody have any suggestions?
199 may be bad (and be why it's not booting), try EOS-stingray-20130617-197 instead.
Format system partition first (in TWRP it's in Wipe->advanced), factory reset, then flash the EOS-stingray-20130617-197.zip AND an appropriate Gapps. Do not factory reset after the rom or gapps (for various reasons I am to tired to go into.) Assuming you have a good copy of the 197 it should boot.
airesch said:
199 may be bad (and be why it's not booting), try EOS-stingray-20130617-197 instead.
Format system partition first (in TWRP it's in Wipe->advanced), factory reset, then flash the EOS-stingray-20130617-197.zip AND an appropriate Gapps. Do not factory reset after the rom or gapps (for various reasons I am to tired to go into.) Assuming you have a good copy of the 197 it should boot.
Click to expand...
Click to collapse
Thanks for the reply. I shall give -197 a try.
As an aside, you don't need to feel obligated to explain your reasons for suggestions (re: Do not factory reset). The advice alone is worth it's weight in gold.
Bad news.
I just downloaded -197 fresh from goo, in fact I did it twice because I couldn't believe the results.
It actually fails to install giving the error "cannot open zip file" -199 never did that.
I also tried -131 (cdma) just to prove to myself that I have the right model. Same results, MOTO logo no boot.
Can't actually believe i am saying this, looks like goo's version is corrupt (my md5 doesn't match theirs and I just looked up the cached version of the webpage and it has d81cded40671c9c0963f95273859dbdd (which is what mine is.)
I will try to pm you a link of the file I have on my dropbox in a bit.
Thanks for this AIRESCH
Your version of -197 is working perfectly.
I think we need to sound the alarm here at XDA, because there are going to be a bunch of pissed off people (like me) who think they have a good image to flash when actually they have a bin of gibberish!
Thanks again.
punishermoose said:
Thanks for this AIRESCH
Your version of -197 is working perfectly.
Click to expand...
Click to collapse
Excellent
punishermoose said:
I think we need to sound the alarm here at XDA, because there are going to be a bunch of pissed off people (like me) who think they have a good image to flash when actually they have a bin of gibberish!
Click to expand...
Click to collapse
Not sure this is necessary, goo has been replacing/upgrading hardware and may not have everything up yet (none of the files were there for a good week at the start of the month.) They may get the right files back up before too long. It does suck for anyone trying to get the files right now tho.
I'm glad your up and working.
Do not factory reset after the rom or gapps (for various reasons I am to tired to go into.)
As an aside, you don't need to feel obligated to explain your reasons for suggestions (re: Do not factory reset).
Click to expand...
Click to collapse
ah, but you don't learn if it's not explained
Reason is: the Xoom only has a 256MB system partition and unfortunately the OS+Gapps (which normally resides in system) as of 4.1 or 4.2 comes to well over this amount. The rom developers HAVE been (they are currently trying to change this) making it so that some of Gapps gets enough copied into the data partition to make everything fit and symlink the files back into system. This has the positive effect of being able to have everything work even without enough space. However the downside is that if you factory reset it will wipe out the files in the data partition, leaving broken symlinks pointing to nothing, and makes it so some of it doesn't work anymore (how much depends on what gapps your using.)
In short: We have awesome devs that are still trying to fix the problem, but their current solution requires you to re-flash gapps (at a minimum, i normally recommend re-flashing both system and gapps) after a factory reset (which is not the end of the world (unless you don't have them both anymore.))
Can someone please share a link with me or pm me please? I still haven't found a working copy of 197 anywhere.
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
SgtTeabag said:
Can someone please share a link with me or pm me please? I still haven't found a working copy of 197 anywhere.
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm in the same boat. Need a good download/copy of 197, please! The goo.im 197 download is borked!!
Hello everyone. Wanted to share an experience with my OPO,.
Today i rebooted the phone, and when it booted up it presented me the first configuration wizard. I thought, "ok this is strange" but after i completed again the configuration everything was still there.
Tonight I tried to install the XNPH33R update via TWRP, i loaded the file into the sdcard and rebooted into TWRP.
I thought "let's make a nandroid before, in case of problems", and i saw it could not mount the /system partition. The backup failed and then i tried to reboot. The phone does now not start and when i try to boot into TWRP, it reports that now ALL the partitions are borked and can't be mounted, reporting them 0MB, except for the boot one.
My question is, am i the only one that experienced something similar?!
I'm goin on to flash factory image but this seems a big problem!
Little hint: try to install another recovery (e.g. CWM, Philz...) before returning to stock
I doubt OnePlus (or any other mfg) would count this sort of thing a bug if your phone is running anything other than 100% stock.
CafeKampuchia said:
I doubt OnePlus (or any other mfg) would count this sort of thing a bug if your phone is running anything other than 100% stock.
Click to expand...
Click to collapse
Obviously i don't want to report a "bug" that i want oneplus to fix
I just wanted to know what happened, my partitions corrupted themselves by... rebooting?
since i saw that many users reported being stuck at the oneplus logo after updating to XNPH33R i wanted to know if this is related to their experience :silly:
dreamerguy00 said:
Little hint: try to install another recovery (e.g. CWM, Philz...) before returning to stock
Click to expand...
Click to collapse
I flashed the factory image except for recovery and everything works, same old TWRP now reports everything as ok and running.. it's just strange! i flashed countless devices and i own a Nexus 4 and a Nexus 5!
blackbird5308 said:
Obviously i don't want to report a "bug" that i want oneplus to fix
I just wanted to know what happened, my partitions corrupted themselves by... rebooting?
since i saw that many users reported being stuck at the oneplus logo after updating to XNPH33R i wanted to know if this is related to their experience :silly:
I flashed the factory image except for recovery and everything works, same old TWRP now reports everything as ok and running.. it's just strange! i flashed countless devices and i own a Nexus 4 and a Nexus 5!
Click to expand...
Click to collapse
Sorry wrong thread
Sent from E.P.D.Center
I had the same weird problem last night.....
Except my recovery was also reverted to stock.
it happened after i got notifed about an update available couple days in a row which i canceled.
I even have Droidwall and everything but a few apps are blocked from data usage.
What i would suggest is to freeze the ""system update" system app.
I kinda have a feeling the OTA updates have something to do with it.
This happend to me 1 other time a while back with an HTC One X device. Same pattern, System update notifications then couple days of ignoring .... then pooffff...
blackbird5308 said:
Hello everyone. Wanted to share an experience with my OPO,.
Today i rebooted the phone, and when it booted up it presented me the first configuration wizard. I thought, "ok this is strange" but after i completed again the configuration everything was still there.
Tonight I tried to install the XNPH33R update via TWRP, i loaded the file into the sdcard and rebooted into TWRP.
I thought "let's make a nandroid before, in case of problems", and i saw it could not mount the /system partition. The backup failed and then i tried to reboot. The phone does now not start and when i try to boot into TWRP, it reports that now ALL the partitions are borked and can't be mounted, reporting them 0MB, except for the boot one.
My question is, am i the only one that experienced something similar?!
I'm goin on to flash factory image but this seems a big problem!
Click to expand...
Click to collapse
Hi everyone.
Let's start from the beginning, and by advance excuse me for my poor English : I happen to be a delighted owner of the Oneplus One by the Oneplus company. I've flashed different versions of cyanogen on my phone, rooted it multiple times and I never encountered any kind of problems. Thus, until I decide yesterday to flash the latest release of cyanogen, cm13 (nightly). I did some researches, followed the usual steps, flashed the right opengapps version along with cm13 and.. everything went great. Except that my phone couldn't resolve himself to detect my SIM card anymore. I tried different things in order to solve the problem, including re-wipe the phone "factory reset" style, removing SIM card, wait for the phone to cool down and played with data roaming, but nothing worked. Fortunately I had my fresh nandroid backup waiting to be restored. That's when the real deal start :
even after having restored the full nandroid backup (which make me downgrade to cm12.1), the SIM card wasn't detected.
So I decided to wipe data, dalvik, cache and system, in order to get my phone back to its original state. But the problem remains, and worst of all, the phone now tends to reboot punctually without any reasons.
I surely did something wrong for the phone to end in this state, but I can't see what..
I use TWRP 2.8.7.0 custom recovery, and the phone OS is now cm12.1-YOG4PAS3JL.
Oneplus One 64GB.
Sorry for the length of the complaint, and by advance thanks for your answers.
P.S : I did tried to search for similar threads in the forum, but I didn't manage to found anything that was directly related.
It could be an issue with the modem not being flashed properly when you went from Lollipop to Marshmallow due to TWRP 2.8.7.0. Try TWRP 2.8.6.0, and then either restore the nandroid backup or clean wipe + reflash CM13 nightly.
oble said:
It could be an issue with the modem not being flashed properly when you went from Lollipop to Marshmallow due to TWRP 2.8.7.0. Try TWRP 2.8.6.0, and then either restore the nandroid backup or clean wipe + reflash CM13 nightly.
Click to expand...
Click to collapse
Thanks a lot for your response. I've been searching a lot and the problem effectively seems to be the modem not being flashed properly. So I tried to flash it manually, (found the file 2 threads higher, sorry I can't post links yet) via fastboot and then flashing cm13 (with twrp 2.8.6.0), considering the fact it seems to have worked for others.
But no matter what I do, the issue remains : the phone isn't able to detect SIM card and goes into crash, rebooting every 2mn..
I've tried to flash cm13 unnoficial version by sultan, following his instructions, but no improvement either.
Even my nandroid backup (running cm 12.1) can't detect SIM anymore, have serious wifi connectivity issues, and keeps rebooting randomly at very reguliar intervals..
I'm really beggining to feel hopeless,
but thanks again for your time and your advices, really apreciate it.
It seems that I have same problem..... after flashing CM13 and restoring backup
Any progress with this problem?
Edit - If my phone is connected into PC with USB cable it doesnt restarts
gersa said:
It seems that I have same problem..... after flashing CM13 and restoring backup
Any progress with this problem?
Edit - If my phone is connected into PC with USB cable it doesnt restarts
Click to expand...
Click to collapse
Same for me, the phone stops crashing and rebooting randomly once connected to pc via USB cable. But still doesn't recognize SIM card. Wifi also seems to work better.
No further progress unfortunately, I've tried everything, from restoring the phone to its factory state to flashing all "stable" roms (cyanogen), nothing worked.
MethylHaine said:
Hi everyone.
Let's start from the beginning, and by advance excuse me for my poor English : I happen to be a delighted owner of the Oneplus One by the Oneplus company. I've flashed different versions of cyanogen on my phone, rooted it multiple times and I never encountered any kind of problems. Thus, until I decide yesterday to flash the latest release of cyanogen, cm13 (nightly). I did some researches, followed the usual steps, flashed the right opengapps version along with cm13 and.. everything went great. Except that my phone couldn't resolve himself to detect my SIM card anymore. I tried different things in order to solve the problem, including re-wipe the phone "factory reset" style, removing SIM card, wait for the phone to cool down and played with data roaming, but nothing worked. Fortunately I had my fresh nandroid backup waiting to be restored. That's when the real deal start :
even after having restored the full nandroid backup (which make me downgrade to cm12.1), the SIM card wasn't detected.
So I decided to wipe data, dalvik, cache and system, in order to get my phone back to its original state. But the problem remains, and worst of all, the phone now tends to reboot punctually without any reasons.
I surely did something wrong for the phone to end in this state, but I can't see what..
I use TWRP 2.8.7.0 custom recovery, and the phone OS is now cm12.1-YOG4PAS3JL.
Oneplus One 64GB.
Sorry for the length of the complaint, and by advance thanks for your answers.
P.S : I did tried to search for similar threads in the forum, but I didn't manage to found anything that was directly related.
Click to expand...
Click to collapse
`
Here is solution (for me)
http://forum.xda-developers.com/showpost.php?p=64768887&postcount=3
Read whole, its short
gersa said:
`
Here is solution (for me)
http://forum.xda-developers.com/showpost.php?p=64768887&postcount=3
Read whole, its short
Click to expand...
Click to collapse
Already saw it, but thanks ^^ that's where i found my file modemst.bin
so did it work for you ?
The same thing happened to me last week. I was using Materialized TWRP 2.8.7.0, which I think caused issues with my updating of Sultanxda's 13.1 ROM. SIM card was never detected, phone would restart shortly after every boot. I tried everything I could find to get my baseband and IMEI back.
In the end, only this solution worked for me, and I had to do it twice. I don't know why.
I had the same problem. I got back to TWRP 2.8.6.0 and then flashed the latest CM13(wiped System). after that without wipe i flashed sultans's CM13 then gapps and got the sim working again.
jp.esteban said:
The same thing happened to me last week. I was using Materialized TWRP 2.8.7.0, which I think caused issues with my updating of Sultanxda's 13.1 ROM. SIM card was never detected, phone would restart shortly after every boot. I tried everything I could find to get my baseband and IMEI back.
In the end, only [link] this solution[/URL] worked for me, and I had to do it twice. I don't know why.
Click to expand...
Click to collapse
Thanks for the link. I tried to flash the zip, but twrp(2.8.6.0) gave me an error : Error flashing ONEPLUS+ONE-FIX-Windows.zip
I tried to clean flash it and dirty flash it, nothing seems to work.
ashishsaggu said:
I had the same problem. I got back to TWRP 2.8.6.0 and then flashed the latest CM13(wiped System). after that without wipe i flashed sultans's CM13 then gapps and got the sim working again.
Click to expand...
Click to collapse
I've tried multiple times, it doesn't work. SIM card is not recognized, phones goes to reboot after 30s of use.
Whatever rom I flash the problem ain't solved, even after factory reset from original OS (cm 12.1)..
I really begin to think there is no solution, I've tried to flash my phone at least 20 times with different roms, fix, firmwares, modem, everything that is available on the net and I couldn't notice even the slightest change in the comportment of my phone.
Anyway, thanks a lot for your proposal, I guess it HAVE to work, but for some irrational reason it doesn't...
MethylHaine said:
I've tried multiple times, it doesn't work. SIM card is not recognized, phones goes to reboot after 30s of use.
Whatever rom I flash the problem ain't solved, even after factory reset from original OS (cm 12.1)..
I really begin to think there is no solution, I've tried to flash my phone at least 20 times with different roms, fix, firmwares, modem, everything that is available on the net and I couldn't notice even the slightest change in the comportment of my phone.
Anyway, thanks a lot for your proposal, I guess it HAVE to work, but for some irrational reason it doesn't...
Click to expand...
Click to collapse
Did U flash over TWRP or ADB?
Just popping in to say I have the same problem. I'm trying the various solutions presented in the thread and I'll come back and report if anything worked. I would also appreciate any other suggestions that you may have
For the record, I got into this predicament through the following steps:
1. I was flashing some CM nightly (sorry, I don't remember which one), and after reboot the touch screen didn't work anymore
2. I flashed the OxygenOs .zip that I had saved on internal storage through TWRP
3. After flash touch screen worked but no sim detected
4. Flashed CM 12.1 still no sim
5. Flashed back to OxyOs, still no sim. Curiously I am unable to reboot via software.
Anyway, I basically have all weekend to work on this, so awayyyy we go!
---
<Edit>
Wow that was fast. I followed this guy's instructions (fastboot flashing modemst, then CM12.1) and it seems to be working like a charm! Good luck everybody else!
gersa said:
Did U flash over TWRP or ADB?
Click to expand...
Click to collapse
I flashed via TWRP(2.6.8.0) and via ADB for modemst1.bin and modemst2.bin.
By the way, there's a little improvement : I flashed kalkulin's_stock_OPO Rom and that stopped my phone from rebooting.
Now cm13 is running kinda fine, except it still doesn't detect SIM card, even after reflashing modemst1 and modemst2
Edit : When I try to flash oxygenos, oneplus fix or cm12.1, (roms that are supposed to fix sim detection problem), it doesn't work : Error flashing Zip file. via adb or twrp, that's the same. (excepting the fact that error in adb is about trustzone)
I think my efs partition is somehow corrupt, and unfortunately i have no way to restore it.
MethylHaine said:
Thanks for the link. I tried to flash the zip, but twrp(2.8.6.0) gave me an error : Error flashing ONEPLUS+ONE-FIX-Windows.zip
I tried to clean flash it and dirty flash it, nothing seems to work.
Click to expand...
Click to collapse
It's not supposed to be flashed. Unzip the archive on a Windows PC, then use the .bat files in there to fix your phone.
jp.esteban said:
It's not supposed to be flashed. Unzip the archive on a Windows PC, then use the .bat files in there to fix your phone.
Click to expand...
Click to collapse
Effectively, I kinda did things completely wrong there, sorry. (I'm an exclusive linux user for my defense ^^)
Okay guys, I finally solved my problems.
Here's what I did to fix reboot crashes and SIM detection issues :
-Flash TWRP(2.8.6.0)
-Wipe everything except internal storage
-Flash Calkulin's_Stock_OPO_XNPH44S_ROM_v1.0.zip (can't post links yet, sorry)
-Boot system
-Once done, reboot to bootloader (in command prompt : sudo adb reboot bootloader)
-In command prompt, type the following commands (It will delete modem and /persist partition ! be careful) :
fastboot erase modemst1
fastboot erase modemst2
fastboot erase persist
-If you need to fix "Unable to mount /persist" error in TWRP :
adb shell
make_ext4fs /dev/block/mmcblk0p15
-Flash Oxygen OS (i flashed oxygen_1.0.0_flashable.zip)
That should restore EFS and fix the issues.
Well, that was kind off a pain in the ass, but now my problem is solved, and i'm currently running cm13 quite fine.
Make a backup of your EFS partition.
Thanks to all the people that helped me by posting in this thread !
It's a nightly build, it bound to have some problems.
i am having bootloop issue, tried many roms, erased partition too, still no use. continuous bootloops
---------- Post added at 03:08 AM ---------- Previous post was at 03:07 AM ----------
gersa said:
`
Here is solution (for me)
http://forum.xda-developers.com/showpost.php?p=64768887&postcount=3
Read whole, its short
Click to expand...
Click to collapse
i am having bootloop issue, tried many roms, erased partition too, still no use. continuous bootloops
Hello!
I did search some topic with bootloop problems, and the thread with my ROM itself, but haven't find any solution.
I was trying to install custom rom and end up with a bootloop. Still can go to recovery/download mode.
I was following instruction from this thread: https://forum.xda-developers.com/ga...-android-nougat-7-0-beta-3-zpkk-odex-t3507499
I have SM-G930F Flat. Enable OEM activated, when system (6.1.1?) was going on. Unfortunately I lost my backup. ;(
When flashing TWRP, probably didnt uncheck restart options, but didnt remember what happened next. I think I just flashed it once more to be sure. Then POWER+DOWN, POWER+MENU+UP got me to nice menu of recovery.
But when I tried to install _no-verity-opt-encrypt-2.2.zip_ file (or even create backup or wipe data), my phone tells me that it couldn't mount /data (couples of times, actually).
Ignored it and proceed with wiping and installing of no-verity and ROM itself (with another wipings among resets). Ended up with bootloop for more like 15 mins and clearly something is wrong here.
I tried to check to install newest modem and csc in aroma installer, but it didnt help.
What am I doing wrong here?
Thanks in advance!
Tom
Weird thing. Glitch has gone. After trying to install with new modem&csc (and it didnt work), turned phone down for ~1h. Now error with mounting /data is gone. Installed everything and new ROM is working nice. Interesting thing, will try to close this thread.