Related
I rebooted my device, and suddenly it didn't get any signal
I have the sim card inserted, and it says No signal.
Any way to fix this?
sungm64 said:
I rebooted my device, and suddenly it didn't get any signal
I have the sim card inserted, and it says No signal.
Any way to fix this?
Click to expand...
Click to collapse
Did you pay for and activate the service? Just asking as your not providing much information.
kzoodroid said:
Did you pay for and activate the service? Just asking as your not providing much information.
Click to expand...
Click to collapse
Well Yeahh;;
And to add, this happened before, but it strangely dissappeared when I flashed a different kernel.
And it suddenly happened again. I have no idea what is going on;;
sungm64 said:
Well Yeahh;;
And to add, this happened before, but it strangely dissappeared when I flashed a different kernel.
And it suddenly happened again. I have no idea what is going on;;
Click to expand...
Click to collapse
Ahh okay so you're flashing kernels no wonder you're having issues. Have you tried returning to stock?
Here are the things people like to know to help you:
Are you running a stock or custom ROM, what kernel are you using, is the sim a true micro sim or one you cut down to fit, who's your carrier. When this first happened did you do any modifications to the phone or was it completely stock? There could be any number of reasons why this happens and the more info you provide the better the quality of the help you receive.
kzoodroid said:
Ahh okay so you're flashing kernels no wonder you're having issues. Have you tried returning to stock?
Click to expand...
Click to collapse
I didn't, but the first thing i tried was to backup to original stock state it was in like 2 weeks ago. Still had no signal issues. But I know that the hardware is not broken, because it fixed itself before somehow. I don't know what I did though;;
I am running a xylon rom, and I was using a clemsynExtreme battery saver, and it is a true micro sim card. I have tmobile, but using a unlocked google play store n4. When this happened, I first had a matrix kernel with the xylon rom
Were you playing around with your APN settings?
Here are some reason I can think of why you could be losing signal:
1. a buggy custom ROM
2. a buggy custom kernel
3. improperly cut sim card
4. wrong apn serttings
5. flashing the wrong radio, I believe this will cause a brick more than just losing signal
Typically when **** just keeps going wrong for me I just revert back to stock and start over. This is either done by restoring a nandroid backup I've made, preferable as I don't like to go fully back to factory stock very often, or if you don't have one by flashing the stock image (restores back to factory condition). I would maybe go into the thread for the kernel you are using in the development section and see if anyone else is having the same issue before going nuclear and restoring a stock image.
http://forum.xda-developers.com/showthread.php?t=2010312
kzoodroid said:
Were you playing around with your APN settings?
Here are some reason I can think of why you could be losing signal:
1. a buggy custom ROM
2. a buggy custom kernel
3. improperly cut sim card
4. wrong apn serttings
5. flashing the wrong radio, I believe this will cause a brick more than just losing signal
Typically when **** just keeps going wrong for me I just revert back to stock and start over. This is either done by restoring a nandroid backup I've made, preferable as I don't like to go fully back to factory stock very often, or if you don't have one by flashing the stock image (restores back to factory condition). I would maybe go into the thread for the kernel you are using in the development section and see if anyone else is having the same issue before going nuclear and restoring a stock image.
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
I am not by the computer, but i will try restoring the device later. Thank you
sungm64 said:
I didn't, but the first thing i tried was to backup to original stock state it was in like 2 weeks ago. Still had no signal issues. But I know that the hardware is not broken, because it fixed itself before somehow. I don't know what I did though;;
I am running a xylon rom, and I was using a clemsynExtreme battery saver, and it is a true micro sim card. I have tmobile, but using a unlocked google play store n4. When this happened, I first had a matrix kernel with the xylon rom
Click to expand...
Click to collapse
The battery saver could be your problem as it most likely turns off your radio when not in use to save the battery. Also go into the xylon rom thread and the matrix kernel threads and do a search for signal loss and see if any one else there is also having the same problems. Not sure if you can post in development without 10 post here first but you're on your way.
---------- Post added at 08:16 PM ---------- Previous post was at 08:15 PM ----------
sungm64 said:
I am not by the computer, but i will try restoring the device later. Thank you
Click to expand...
Click to collapse
get rid of the battery saver first and see if that helps
---------- Post added at 08:28 PM ---------- Previous post was at 08:16 PM ----------
kzoodroid said:
The battery saver could be your problem as it most likely turns off your radio when not in use to save the battery. Also go into the xylon rom thread and the matrix kernel threads and do a search for signal loss and see if any one else there is also having the same problems. Not sure if you can post in development without 10 post here first but you're on your way.
---------- Post added at 08:16 PM ---------- Previous post was at 08:15 PM ----------
get rid of the battery saver first and see if that helps
Click to expand...
Click to collapse
Wait a minute clemsyn is a kernel, does he even make one for the Nexus 4? I would image your problem is kernel related. If you made a backup of your stock image I would just restore that first through recovery and go from there.
---------- Post added at 08:40 PM ---------- Previous post was at 08:28 PM ----------
Did a search in development and other people report problems of signal loss with some versions of that kernel. Try flashing a newer version, not sure why I didn't think of that earlier, but I haven't had any reason to flash a kernel in a long time as I gave up on the whole custom thing a long time ago. Same goes for the ROM if a newer version of the kernel doesn't work. these guys are constantly working on these things and things break between versions, they are always a work in progress and things are always breaking and being repaired.
kzoodroid said:
The battery saver could be your problem as it most likely turns off your radio when not in use to save the battery. Also go into the xylon rom thread and the matrix kernel threads and do a search for signal loss and see if any one else there is also having the same problems. Not sure if you can post in development without 10 post here first but you're on your way.
---------- Post added at 08:16 PM ---------- Previous post was at 08:15 PM ----------
get rid of the battery saver first and see if that helps
---------- Post added at 08:28 PM ---------- Previous post was at 08:16 PM ----------
Wait a minute clemsyn is a kernel, does he even make one for the Nexus 4? I would image your problem is kernel related. If you made a backup of your stock image I would just restore that first through recovery and go from there.
---------- Post added at 08:40 PM ---------- Previous post was at 08:28 PM ----------
Did a search in development and other people report problems of signal loss with some versions of that kernel. Try flashing a newer version, not sure why I didn't think of that earlier, but I haven't had any reason to flash a kernel in a long time as I gave up on the whole custom thing a long time ago. Same goes for the ROM if a newer version of the kernel doesn't work. these guys are constantly working on these things and things break between versions, they are always a work in progress and things are always breaking and being repaired.
Click to expand...
Click to collapse
From what I am looking at, Clemsyn is a nexus 7 kernel. I think i flashed a wrong kernel??? wow, but it didn't cause any problems when i flashed it into the nexus 4. Worked fine for ~week
sungm64 said:
From what I am looking at, Clemsyn is a nexus 7 kernel. I think i flashed a wrong kernel??? wow, but it didn't cause any problems when i flashed it into the nexus 4. Worked fine for ~week
Click to expand...
Click to collapse
Kernels can work between different devices usually with some modifications done for screen size and resolution but they need to share hardware, cpu in particular. You get in to real trouble when you flash radios from different devices, that will brick it solid.
I would try flashing the latest version of the matrix kernel and see if that helps.
kzoodroid said:
Kernels can work between different devices usually with some modifcations done for screen size and resolution, you get in to real trouble when you flash radios from different devices, that will brick it solid.
I would try flashing the latest version of the matrix kernel and see if that helps.
Click to expand...
Click to collapse
I tried flashing different kernels including matrix and stock. It flashes like normal, but signal loss is still present
sungm64 said:
I tried flashing different kernels including matrix and stock. It flashes like normal, but signal loss is still present
Click to expand...
Click to collapse
Try toggling airplane mode on and off and see if it comes back on.
If not restoring a backup or flashing the system image may be your only options left.
If you think you made a backup earlier go into recovery, (I'm assuming you have a custom recovery installed) make another backup just in case even though you have no signal its just good habit to make a backup before you do any thing then restore the previous backup. You don't need to be on the pc to do this if you installed a custom recovery, you just need to boot into it. If you used a toolkit then I guess you need to be hooked up to a pc.
kzoodroid said:
Try toggling airplane mode on and off and see if it comes back on.
If not restoring a backup or flashing the system image may be your only options left.
If you think you made a backup earlier go into recovery, (I'm assuming you have a custom recovery installed) make another backup just in case even though you have no signal its just good habit to make a backup before you do any thing then restore the previous backup. You don't need to be on the pc to do this if you installed a custom recovery, you just need to boot into it. If you used a toolkit then I guess you need to be hooked up to a pc.
Click to expand...
Click to collapse
I tried restoring to the previous backup. This was just rooted, no custom roms or kernels. But custom recovery.
I don't know if there is a way to fix this. But, the thing is, it was being exactly like this, but I got it fixed somehow. I rebooted after failed attempt and it randomly had signal;;.
After that, I tried flashing a kernel, and ever since it has been no signal
sungm64 said:
I tried restoring to the previous backup. This was just rooted, no custom roms or kernels. But custom recovery.
I don't know if there is a way to fix this. But, the thing is, it was being exactly like this, but I got it fixed somehow. I rebooted after failed attempt and it randomly had signal;;.
After that, I tried flashing a kernel, and ever since it has been no signal
Click to expand...
Click to collapse
Have you set the correct APN settings for your carrier?
kzoodroid said:
Have you set the correct APN settings for your carrier?
Click to expand...
Click to collapse
Well, the signal worked fine before, I don't know if setting the APN can help
What I am saying is just make sure that they are the correct ones for your carrier as that could be the cause of the signal loss.
kzoodroid said:
What I am saying is just make sure that they are the correct ones for your carrier as that could be the cause of the signal loss.
Click to expand...
Click to collapse
It didn't Help.
WOW... Now I have no idea what to do. Nexus 4 broken???
try this
sungm64 said:
It didn't Help.
WOW... Now I have no idea what to do. Nexus 4 broken???
Click to expand...
Click to collapse
Its a hardware thing. Had it a couple of weeks ago after running with the phone. Eventually worked out after removing the sim tray, reposition the card and put it back.
i have noticed the same issue after shutting my phone off and turning it back off sometimes. no signal or takes a while to connect. i have to restart my phone and it seems to go away. i am running stock rom so i think its a bug in jelly bean.
Did you try taking out the sum card and putting it back in?
For Nexus S
For Changelog
http://www.cmxlog.com/11/crespo/
For bugs:
https://jira.cyanogenmod.org/
For Download Nightly 12/04/2015
http://download.cyanogenmod.org/get/jenkins/106751/cm-11-20150412-NIGHTLY-crespo.zip
http://get.cm/get/oop
For Download M12 Snapshot 12/11/2014
http://download.cyanogenmod.org/get/jenkins/90440/cm-11-20141112-SNAPSHOT-M12-crespo.zip
http://get.cm/get/l99
For gapps
http://wiki.cyanogenmod.org/w/Gapps
xbs said:
OP should mention that CWM 6.0.4.3 (or PhilZ 6.01.0) is mandatory.
TWRP won't work!!!
Click to expand...
Click to collapse
khimois said:
Just wanna share...
I've experienced the Messaging errors before but that was because I'm restoring SMS through TB. After I've used the SMS Backup & Restore, the problem does not appear anymore and I've flashed through clean install.
Cheers!
Click to expand...
Click to collapse
jtrvk said:
After searching a bit, got the photo sphere working thanks to this
http://forum.xda-developers.com/showthread.php?t=2506740 ( backup the files to prevent any future problems)
Be sure to keep the low ram value to false in build.prop ( This I discovered by pure luck)
Reboot
Enjoy
Click to expand...
Click to collapse
First!
Also, awesome. Looks promising
anyone tried it yet? how're things going? any major bug/ instability? mine on download....
Yes, it's very awesome, but some settings are still missing. To be expected from a first build
OMG! There's a release already!!!
How's the RAM performance? Max free? Anyone?
The phone runs smooth. I am currently in the process of trying out ART. Don't know max free. It will take a while for that to appear since only a handful of people flashed it.
I mean approximately? In Kitkang they got 170MB I think?
---------- Post added at 04:52 PM ---------- Previous post was at 04:43 PM ----------
By the way, after installation of this can we do updates with dirty flashing from this build? Even if we use ART?
Just had a reboot on ART around 1 minute after booting. Stay tuned.
EDIT: false alarm. Everything seems to be in order with ART. And a tad snappier too
What do you use to backup and restore SMS?
I'm using Nandroid Manager but it doesn't seem to work. OTL
Go Backup. Works like a charm.
But I only have Nandroid backup... OTL
---------- Post added at 06:11 PM ---------- Previous post was at 05:58 PM ----------
Ended up reverting to my backup ROM. Gotta figure out first how to backup and restore SMS without hassle.
Any known bug? Issues?
Full wipe before flashing from 10.2 is mandatory?
Phoenixct said:
Any known bug? Issues?
Full wipe before flashing from 10.2 is mandatory?
Click to expand...
Click to collapse
Haven't seen any bugs, just features that haven't been ported yet. I did a dirty flash and it looks fine but I intend to do a full wipe and only restore apps tomorrow or the day after that.
andrei1015 said:
Haven't seen any bugs, just features that haven't been ported yet. I did a dirty flash and it looks fine but I intend to do a full wipe and only restore apps tomorrow or the day after that.
Click to expand...
Click to collapse
I think i'll give it a try
--------------------------------
Edit:
It reports me an error in flashing:
"set_metadata_recursives: some data changes failed
E:Error in /sdcard/cm-11-20131206-NIGHTLY-crespo.zip
(Status 7)
Installation aborted"
Md5 was right, i'll try with a full wipe.
--------------------------------
Edit (2):
Same error even after a full wipe...
Phoenixct said:
I think i'll give it a try
--------------------------------
Edit:
It reports me an error in flashing:
"set_metadata_recursives: some data changes failed
E:Error in /sdcard/cm-11-20131206-NIGHTLY-crespo.zip
(Status 7)
Installation aborted"
Md5 was right, i'll try with a full wipe.
--------------------------------
Edit (2):
Same error even after a full wipe...
Click to expand...
Click to collapse
Update to the latest CWM version. This has already been discussed on the Google+ Page and they said to update CWM.
Phoenixct said:
It reports me an error in flashing:
"set_metadata_recursives: some data changes failed
E:Error in /sdcard/cm-11-20131206-NIGHTLY-crespo.zip
(Status 7)
Installation aborted"
Click to expand...
Click to collapse
Had also an error (did not write it down, maybe the same) when trying to flash with TWRP.
Flashing with CWM Recovery worked
andrei1015 said:
Update to the latest CWM version. This has already been discussed on the Google+ Page and they said to update CWM.
Click to expand...
Click to collapse
What if i use latest philz_touch?
Edit:
It Works.
---------- Post added at 12:30 PM ---------- Previous post was at 12:13 PM ----------
First impression:
The insert pin screen resolution was larger than the screen so numbers are cut.
One reboot after selected the launcher.
Question:
Launcher3 was a CM fork of Google launcher?
Phoenixct said:
What if i use latest philz_touch?
Edit:
It Works.
---------- Post added at 12:30 PM ---------- Previous post was at 12:13 PM ----------
First impression:
The insert pin screen resolution was larger than the screen so numbers are cut.
One reboot after selected the launcher.
Question:
Launcher3 was a CM fork of Google launcher?
Click to expand...
Click to collapse
About the cut numbers, again, it's a first build. To be expected. About the launcher, yes, think so.
andrei1015 said:
About the cut numbers, again, it's a first build. To be expected. About the launcher, yes, think so.
Click to expand...
Click to collapse
I know I know, I'm just report this for who do not want to try it so early.
All was almost fully functional, I think in few weeks we can have a version of cm11 stable and fully usable.
OP should mention that CWM 6.0.4.3 (or PhilZ 6.01.0) is mandatory.
TWRP won't work!!!
Hi, it's my first time posting so I do apologize if I posted this in the wrong thread.
So I recently flashed the latest CM12 Nightly Rom for my S4 I9505. But I realised I needed to restore my backup (which I did with Nandroid before I flashed the ROM). So I went to CWM Recovery, tried to restore with the backup I did.
Everything was fine until I got this : "Error while restoring /system". I thought maybe the one in the phone was corrupted so i copied the one from my PC and still i get this error.
I'm hoping someone can help me on this.
Thanks!
just follow the following steps
1. full wipe data+dalvik cache
2. copy your backup to pc
3. open nandroid.md5 in notepad
4. delete everything and save it
5. now copy the backup to sdcard and restore it.
Enjoy
Hit thanks if I helped you.
chaos03 said:
Hi, it's my first time posting so I do apologize if I posted this in the wrong thread.
So I recently flashed the latest CM12 Nightly Rom for my S4 I9505. But I realised I needed to restore my backup (which I did with Nandroid before I flashed the ROM). So I went to CWM Recovery, tried to restore with the backup I did.
Everything was fine until I got this : "Error while restoring /system". I thought maybe the one in the phone was corrupted so i copied the one from my PC and still i get this error.
I'm hoping someone can help me on this.
Thanks!
Click to expand...
Click to collapse
I hope the nandroid backup (you did before flash the custom ROM) wasn't of one STOCK Rom :fingers-crossed:.
Joku1981 said:
I hope the nandroid backup (you did before flash the custom ROM) wasn't of one STOCK Rom :fingers-crossed:.
Click to expand...
Click to collapse
Oh it was.. does that mean I'm kinda screwed?
there is no issue in restoring nandroid backup of stock roms.
but recovery may be an issue.
yourshubhamkansal said:
there is no issue in restoring nandroid backup of stock roms.
but recovery may be an issue.
Click to expand...
Click to collapse
Well, i don't agree with you sorry.
---------- Post added at 18:00 ---------- Previous post was at 17:55 ----------
chaos03 said:
Oh it was.. does that mean I'm kinda screwed?
Click to expand...
Click to collapse
Don't be.
1. Reflash stock Rom via ODIN, root and custom recovery.
2. Flash Custom ROM then again. But don't restore the backup you did before.
3. Done.
I may be wrong , but I have restore nandroid backup of stock roms many times.
I didn't even faced a single issue.
yourshubhamkansal said:
I may be wrong , but I have restore nandroid backup of stock roms many times.
I didn't even faced a single issue.
Click to expand...
Click to collapse
Hi, I tried what you suggested, deleting everything in nandroid.md5. And I manage to restore it.
But now there is another problem. this message "unfortunately the process com.google.process.gapps has stopped" pops up almost every 5 seconds. Any idea how to fix this?
yourshubhamkansal said:
I may be wrong , but I have restore nandroid backup of stock roms many times.
I didn't even faced a single issue.
Click to expand...
Click to collapse
Sure? Restoring nandroid backups of stock roms to CUSTOM ROMS?? I don't think so bro . Anyway you can help @chaos03 better than me . Good luck :highfive:
First, remove your Google account (no big deal, you can sign back in in a few minutes). Then, go to Settings>Apps>All> Scroll down to the G's until you get the first thing that has Google in it's name. The first one on my phone (galaxy nexus, CM) is called "Google Account Manager". Click on it and hit "Clear Data". Repeat this process for everything Google in the list. Now sign back into your Google account. You should never see that message again!
Hit thanks if I helped you!
---------- Post added at 11:39 PM ---------- Previous post was at 11:10 PM ----------
clear cache and data of all google apps
as well as signout and signin your google account again!
yourshubhamkansal said:
First, remove your Google account (no big deal, you can sign back in in a few minutes). Then, go to Settings>Apps>All> Scroll down to the G's until you get the first thing that has Google in it's name. The first one on my phone (galaxy nexus, CM) is called "Google Account Manager". Click on it and hit "Clear Data". Repeat this process for everything Google in the list. Now sign back into your Google account. You should never see that message again!
Hit thanks if I helped you!
---------- Post added at 11:39 PM ---------- Previous post was at 11:10 PM ----------
clear cache and data of all google apps
as well as signout and signin your google account again!
Click to expand...
Click to collapse
I'm trying to do as you said, but the problem is the message pops up again the moment i dismiss it, and i cant even do anything else (only able to switch the phone on and off). And I also notice that some apps are starting to crash too.. is it possible to first flash an official Stock Rom and then do a restore?
maybe or maybe not
but I will suggest u to restore it once again and then do a factory reset , maybe it will work.
restoring it after installing stock will be always an option, but can't guarantee that you will not face the com.gapps.... has stopped working error.
.
---------- Post added at 12:10 AM ---------- Previous post was at 12:10 AM ----------
r u recieving this single error or there are more apps crashing
?
This error and also error messages for some of the apps that say the apps stopped working.
I'm just worried that the backup is corrupted (Praying hard that it isnt the case)
Oh btw I'm using a CWM from ROM Manager version 6.0.4.7, I did some reading and they say there's a chance that it doesnt work well with Samsung phones. Do you think I should use another?
there is one more option also, which I think may work
just download gapps package from the given link and flash it using recovery
make sure you choose the right package as per your android version
http://www.android.gs/download-install-and-flash-google-apps-for-android/
After updating PureNexus (November Build) to December build, I got thebrick that other users have been getting. I will do a quick summary
Shortened Version: Flashed new version of PureNexus, didn't boot. Did clean flash, still didn't boot. Backup didn't work.
Long version: Wiped System, Dalvik Cache (& Cache) at first
Flashed Pure Nexus, Gapps, Kernel, and then SuperSU
Rebooted, not working
--
Restored to my backup of the November build I made before I flashed
Rebooted, not working
---
Wiped EVERYTHING besides internal storage, flashed old build.
Not working.
Update before I restore: Checked bootloader, everything looks normal from there. Going to backup my data from TWRP before I do the flash
Currently going to restore to stock and see if this does any magic. Will report back!
UPDATE: Restoring to stock and clearing EFS seemed to do the trick, interesting.
What twrp version do you use to backup ?
TnT_ said:
After updating PureNexus (November Build) to December build, I got thebrick that other users have been getting. I will do a quick summary
Shortened Version: Flashed new version of PureNexus, didn't boot. Did clean flash, still didn't boot. Backup didn't work.
Long version:Wiped System, Dalvik Cache (& Cache) at first
Flashed Pure Nexus, Gapps, Kernel, and then SuperSU
Rebooted, not working
--
Restored to my backup of the November build I made before I flashed
Rebooted, not working
---
Wiped EVERYTHING besides internal storage, flashed old build.
Not working.
Update before I restore: Checked bootloader, everything looks normal from there. Going to backup my data from TWRP before I do the flash
Currently going to restore to stock and see if this does any magic. Will report back!
UPDATE: Restoring to stock and clearing EFS seemed to do the trick, interesting.
Click to expand...
Click to collapse
I had a similar problem flashing a new build of Cortex. I ended up in a boot loop couldn't restore my backup and had to flash stock to get my phone back. I was using TWRP 3.0.3-0 but have since returned to 3.0.2-3.
ariefabuzaky said:
What twrp version do you use to backup ?
Click to expand...
Click to collapse
jhs39 said:
I was using TWRP 3.0.3-0 but have since returned to 3.0.2-3.
Click to expand...
Click to collapse
I was also using 3.0.3-0, could this be a issue with the recovery?
I bricked mine as well, although i have no access to fastboot mode, mine is completely dead :/ Any ways in which i could fix this?
TnT_ said:
I was also using 3.0.3-0, could this be a issue with the recovery?
Click to expand...
Click to collapse
I know my ROM dev suggested sticking with 3.0.2-3, although not for that specific reason. It does seem like the new build is buggy for some people based on things I've been reading.
---------- Post added at 11:53 PM ---------- Previous post was at 11:52 PM ----------
harrypakhale said:
I bricked mine as well, although i have no access to fastboot mode, mine is completely dead :/ Any ways in which i could fix this?
Click to expand...
Click to collapse
By dead do you mean blank screen or Google logo or what?
i mean blank screen, cant even access fastboot mode
i mean blank screen, not even charging when i plug it for charge.
harrypakhale said:
i mean blank screen, not even charging when i plug it for charge.
Click to expand...
Click to collapse
That's odd. Are you charging via USB, car charger or wall plug? I have read instances of a phone like yours coming back to life if it's plugged into a wall outlet overnight.
If you hard press the power button do you get LED lights or anything,? Try playing with the buttons. Press power + volume up. Power + volume down. Try repeatedly with different button combinations and see if you get any response from your phone.
Hello,
i seem to have badluck this time with custom rom and development for this device. Last i was struggling with encryption problem (when the great @DarthJabba9 showed me the right path) and now a strange thing happened.
So when i successfully booted into xiaomi.eu (latest) first time without encrypting my recovery function, everything was working fine and good, until i installed whatsapp provided all the permissions then suddenly it didnt look for my backup and acted like there was no backup (i nearly got a heart attack) and after setting up the name and so, i got to know it cant create backup, nor do anything which involve the use of internal storage because it is not writing nor reading internal storage, then i backoff and flashed back 11.6.0 stable, whatsapp start working normally, tried again with other xiaomi.eu and miglobe versions - failed same result, whatsapp only working in stable 11.6.0 and not working in other roms. Also, search function didnt work for me this time (so i found out i am the only one with this problem). does any body has a fix other than telling me to unsinstall, reinstall, clearing data etc.
- except whatsapp everything is working fine (TILL NOW)
Oh....please.....nobody has a clue???
The best was is to backup, then flash the right fastboot rom, OrangeFox the last build and then u rom with the right steps! Step by step... Good luck
---------- Post added at 09:55 PM ---------- Previous post was at 09:50 PM ----------
Maybe to copy all to a computer before u flash the fastboot rom. Look on the options from mi flashtool...
joke19 said:
The best was is to backup, then flash the right fastboot rom, OrangeFox the last build and then u rom with the right steps! Step by step... Good luck
---------- Post added at 09:55 PM ---------- Previous post was at 09:50 PM ----------
Maybe to copy all to a computer before u flash the fastboot rom. Look on the options from mi flashtool...
Click to expand...
Click to collapse
Well thanks for the advice, but i am looking for a fix, and what you said is same as wiping internal/formatting data/clean flash, ah.....so already tried. Does anybody have a fix?? Oh.....please....i am waiting...
You can try a modded whatsapp like Fouad whatsapp. It might solve the issue + extra goodies. Search it on web.
Make sure you backup your chats before uninstalling the app.
Walden0 said:
You can try a modded whatsapp like Fouad whatsapp. It might solve the issue + extra goodies. Search it on web.
Make sure you backup your chats before uninstalling the app.
Click to expand...
Click to collapse
Well, already tried......no luck.
mr.badman said:
Well, already tried......no luck.
Click to expand...
Click to collapse
Strange. Really hard to blind guess what might be the issue. Guess you should try using an aosp based rom.
Walden0 said:
Strange. Really hard to blind guess what might be the issue. Guess you should try using an aosp based rom.
Click to expand...
Click to collapse
Yeah, thats what i was thinking. But whatsapp is not going to send otp again and again, might block me. Need to use another number. (Can i have yours...??, Ha.......just kidding)
Will try and update.
mr.badman said:
Yeah, thats what i was thinking. But whatsapp is not going to send otp again and again, might block me. Need to use another number. (Can i have yours...??, Ha.......just kidding)
Will try and update.
Click to expand...
Click to collapse
Whatsapp does not block you if you ask for otp multiple times in a day. It will restrict the sms for some hours after three attempts i guess, after that you can get it via call. Four times is enough for a day.
And having my number would not help as I wont be giving you the otp.
probably you use deep clean and erase the WP data.