bluetooth or wifi and cellurlar network aren't working after flashing twrp and roms...
I've also restored stock roms with fastboot method.
anyone has a fix or solution?
also restored stock rom
ilmervanhattem said:
bluetooth or wifi and cellurlar network aren't working after flashing twrp and roms...
I've also restored stock roms with fastboot method.
anyone has a fix or solution?
Click to expand...
Click to collapse
I believe this is because you wiped your PDS/EFS partition. If you can get this from someone, you can flash theirs (but make sure to replace all data in it, like IMEI and MAC addresses).
Related
So, today i've tried to flas PAC on top of my omega 4.3 rom, after changing recovery and flashing this rom i noticed i had lost signal.. i decided to get back to omega but maybe changing recovery had deleted my backups, so i installed it from full wipe (only after many try, beacouse i didn't pass bootanimation) and now i still don't have 3g or any type of signal, any ideas?
no problem
noooooo said:
So, today i've tried to flas PAC on top of my omega 4.3 rom, after changing recovery and flashing this rom i noticed i had lost signal.. i decided to get back to omega but maybe changing recovery had deleted my backups, so i installed it from full wipe (only after many try, beacouse i didn't pass bootanimation) and now i still don't have 3g or any type of signal, any ideas?
Click to expand...
Click to collapse
Go to the phone setting and see your imei, if is is not what was before then you can do the following.
Getting no signals means you have corrupted imei.
If you previously haved saved any backup of efs flash it. It may solve your problem of no signals.
flash latest modem through odin.you can flash modem from your phone but flash it through pc.
Pc Odin*- open extracted file ".tar.(md5)" as*PHONE-
Phone Custom Recovery*- flash*modem.zip*from SDCard*
There is some problem with the recoveries that when you flash any aosp 4.3 rom you might not get boot animation this is normal.you can try twrp recovery you will get boot animation.Happened same with me.
alifarrukhsss said:
Go to the phone setting and see your imei, if is is not what was before then you can do the following.
Getting no signals means you have corrupted imei.
If you previously haved saved any backup of efs flash it. It may solve your problem of no signals.
flash latest modem through odin.you can flash modem from your phone but flash it through pc.
Pc Odin*- open extracted file ".tar.(md5)" as*PHONE-
Phone Custom Recovery*- flash*modem.zip*from SDCard*
There is some problem with the recoveries that when you flash any aosp 4.3 rom you might not get boot animation this is normal.you can try twrp recovery you will get boot animation.Happened same with me.
Click to expand...
Click to collapse
Yeah, i didn't check imei but falshing modem again solved my problem, thanks anyway, a lot
Regardless of what recovery I used, (yash28, regalstreak, official twrp) or even starting from the scratch( flashing stock OxygenOS using the Oneplus tools) and then reflashing the recovery, my attempts to succesfully load into a ROM has been futile. As of now, I am pretty much unable to boot into any recovery, and I am stuck using the stock OxygenOS. I tried flashing modem, first attempt was clean flashing the new modem, then flashing it dirty after flashing my rom, I tried doing the same thing with the old modem, my attempts have been futile. If anyone could shed light in this situation, it would be great, I would hate to be stuck using the stock OxygenOS rom, and not try out the great roms that are developed. I can however flash oxygenOS stock rom.
i have the same problem and i cant find any solution i thought of starting fromt he scratch as it didnt help u it might not help me too
Have the same, I've done everything. I've made the phone full stock again and still won't boot.
I have finally found the solution to my own problem
Apparently what made this impossible was due to sensors, as I noticed some of my sensors werent working. That could have made me unable to flash anything but OOS. Anyway, the solution is to fastboot erase persist, and reflash persist.img (Instructions are here: http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591). I hope this fixes your guys problem.
abhisek1994 said:
Apparently what made this impossible was due to sensors, as I noticed some of my sensors werent working. That could have made me unable to flash anything but OOS. Anyway, the solution is to fastboot erase persist, and reflash persist.img (Instructions are here: http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591). I hope this fixes your guys problem.
Click to expand...
Click to collapse
So now youre able to flash CM13 without bootloops?
yousuf.shareef said:
So now youre able to flash CM13 without bootloops?
Click to expand...
Click to collapse
Yep! Also make sure you are using official TWRP (https://dl.twrp.me/oneplus2/) Good luck.
abhisek1994 said:
Apparently what made this impossible was due to sensors, as I noticed some of my sensors werent working. That could have made me unable to flash anything but OOS. Anyway, the solution is to fastboot erase persist, and reflash persist.img (Instructions are here: http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591). I hope this fixes your guys problem.
Click to expand...
Click to collapse
FINALLY! Thank you!! Ive been stuck all day without getting ANY MM ROM to boot,. and this ...thing...fixed it! Thanks again
Finally someone found the answer! Unfortunately I wiped whole internal memory and forgot to take backup of whatsapp backup so i lost that. Oh well, all works good now, thank you!
JudderArts said:
Finally someone found the answer! Unfortunately I wiped whole internal memory and forgot to take backup of whatsapp backup so i lost that. Oh well, all works good now, thank you!
Click to expand...
Click to collapse
Dont forget to thank people.
abhisek1994 said:
Dont forget to thank people.
Click to expand...
Click to collapse
JudderArts said:
thank you!
Click to expand...
Click to collapse
That's exactly what I did.
I think i faced the same problem, im using h2os 6.0.1 close beta, with twrp 3.0, but without rooting. I can restore my rom tru twrp without problem. But my try to flash grarak cm13 and new mokee os 6.0 ended up with bootloops, both stuck at oneplus logo
abhisek1994 said:
Apparently what made this impossible was due to sensors, as I noticed some of my sensors werent working. That could have made me unable to flash anything but OOS. Anyway, the solution is to fastboot erase persist, and reflash persist.img (Instructions are here: http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591). I hope this fixes your guys problem.
Click to expand...
Click to collapse
Do you have to go back to the stock rom before flashing persist and then install cm13? or can i do it while i am on the boot logo screen...i tried going into fastboot while stuck on the boot logo (which i was able to) and flashed persist and rebooted but it is still stuck on the boot logo screen
muthukumarc said:
Do you have to go back to the stock rom before flashing persist and then install cm13? or can i do it while i am on the boot logo screen...i tried going into fastboot while stuck on the boot logo (which i was able to) and flashed persist and rebooted but it is still stuck on the boot logo screen
Click to expand...
Click to collapse
You have to downgrade fastboot/bootloader to the Lollipop one (just flash the usual revert_to_lollipop.zip found in these forums as usual).
Hi!
I am getting crazy because I cannot understand the reason about this weird behavior.
This morning I got stuck in bootloop (rom pure nexus).
I tried a dirty flash but it didn't work so I made a data factory reset and flashed it again. I had some weird stuff like Bluetooth errors and so on. I restarted the phone and again I got stuck in bootloop.
So I flashed different rom by USB OTG (e.g. Bliss Rom, BEnzo Rom) and the problems are more or less the same: I flash the rom, I boot the rom and I get weird errors (e.g., I cannot use Titanium Backup) and if I restart the phone I got stuck in bootloop.
What is going on? Is it possible I have problem with the internal SD Card?
Thank you
sounds like your system is fcucked currenty. should probably boot to fastboot and flash the image:
system
bootloader
vendor
radio
kernel
Try booting up after that.
e753 said:
Hi!
I am getting crazy because I cannot understand the reason about this weird behavior.
This morning I got stuck in bootloop (rom pure nexus).
I tried a dirty flash but it didn't work so I made a data factory reset and flashed it again. I had some weird stuff like Bluetooth errors and so on. I restarted the phone and again I got stuck in bootloop.
So I flashed different rom by USB OTG (e.g. Bliss Rom, BEnzo Rom) and the problems are more or less the same: I flash the rom, I boot the rom and I get weird errors (e.g., I cannot use Titanium Backup) and if I restart the phone I got stuck in bootloop.
What is going on? Is it possible I have problem with the internal SD Card?
Thank you
Click to expand...
Click to collapse
When flashing these ROMs are you wiping properly (system, data, cache, dalvik cache) first? You should try going back to stock, but you'll need to do more than the previous person who replied has said. First you need to wipe data in TWRP, then you need to flash the full factory images, not just the ones mentioned above. You'll find instructions for that in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
After these steps it seems working.
boot to fastboot and flash the image:
system
bootloader
vendor
radio
kernel
It's very strange though..
I had that problem today. I traced it down to my wifi. Turning off wifi allowed me to boot with no further issues.
1) Boot loop as soon as I got to work.
2) Dirty flashed the ROM
3) Restored backup from 4 days ago.
4) Wiped system and reflashed ROM and gapps. Same issue.
Finally chased it to the wifi. The instant it connected, bootloop. I ran and app called FXR Wifi fixer. Ill see if it bootloops tomorrow at work. No problems on my home wifi after all of this.
e753 said:
After these steps it seems working.
boot to fastboot and flash the image:
system
bootloader
vendor
radio
kernel
It's very strange though..
Click to expand...
Click to collapse
i wouldn't consider this to be strange really. something was not correct in the system partition probably. pretty standard when flashing different ROMs
Hi guys.
I installed TWRP and rootet my phone with magisk and everything worked fine. I then tried a couple of custom kernels before I restored my TWRP backup. Now I can not turn WiFi on. Can someone please help me.
Is there any way to restore it safely and correctly, maby some file I can download that fixes the problem? I really don't want to flash original firmware allover again..
chrb1985 said:
Hi guys.
I installed TWRP and rootet my phone with magisk and everything worked fine. I then tried a couple of custom kernels before I restored my TWRP backup. Now I can not turn WiFi on. Can someone please help me.
Is there any way to restore it safely and correctly, maby some file I can download that fixes the problem? I really don't want to flash original firmware allover again..
Click to expand...
Click to collapse
May it is enough if you flash the boot.img of the rom from which you made the twrp backup. I guess you have the rom file on your sdcard, unzip and flash the boot.img with twrp. Or dirty flash the rom if you're to lazy for a clean install.
I was on stock android 8.0.. So I guess that won't work.
chrb1985 said:
I was on stock android 8.0.. So I guess that won't work.
Click to expand...
Click to collapse
Why this shouldn't work ?? You can flash boot,system,recovery and vendor.img of the unzip factory image with twrp, except bootloader and radio of course, but that's not necessary anyway.
chrb1985 said:
..... Can someone please help me. I really don't want to flash original firmware allover again :crying:..
Click to expand...
Click to collapse
LOL, fastboot flash stock boot, system, vendor.
Btw, if you're flashing to test some custom kernels you should have always the original boot.img from the
rom you're using on your sdcard. First flash the boot.img before you flash the next custom kernel, and don't flash a custom kernel over the next custom kernel.
Do you guys mean my backed up boot? Or should I download this files from somewhere?
If you backuped the original with TWRP, you can use it.
Otherwise download your rom, unzip and look for the file.
To solve your WiFi issue u have to dirty or clean flash anyway with TWRP,fastboot or flashfire. Whatever you prefer.
Okay. Yes i backed up the original. I will try it now
It worked when I only recovered system, boot and data
Suddenly at around 11:30 today calling and texting quit working. The Sim status says that data is connected but voice is not. I haven't done anything what might have caused this. I tried doing a factory reset and reflashing my rom and I'm running out of options.
Which rom are you on?
debdeep98 said:
Which rom are you on?
Click to expand...
Click to collapse
Was on crdroid when it started. Tried factory reset and reflashing ROM. When none of that worked I flashed resurrection remix because maybe it was a problem with crdroid but that didn't work.
If it still didn't work then you can flash stock oreo from NZedPred's thread. Get the twrp flashable zip. That would fix persist and efs and restore calling.
debdeep98 said:
If it still didn't work then you can flash stock oreo from NZedPred's thread. Get the twrp flashable zip. That would fix persist and efs and restore calling.
Click to expand...
Click to collapse
Flashed stock then reflashed crdroid and calling and texting is working again