UNIT : Samsung SIII SHV - E210S
Problem:
1. Camera, when you clicked on camera it shuts down and says "Security Policy resrticts the use of Camera"
2. Memory Card - Micro SD is mounted but when booted you can't see the icon on My Files also you can't browse the contents of the memory card but when in download mode / restore mode it reads it.
3. Bluetooth - Icon or setting is there but when you click it on it does not turn into green or won't turn on.
4. On the Drop down menu there's a notification that says "Please install MDM" - i tried installing MDM but when the app is installed it prompts for a "company site code"
Possible Solutions that already tried
1. Restored the phone to it's original state on Device Recovery Mode (Factory Reset) nothing happened
2. Flashed a custom rom (OCHIE ROM) but still the "Please install MDM" on the drop down prompts it and same issues, Cam+MMC+BT restricted
3. Flashed custom kernel (Berzebb), nothing happened "Please install MDM" on the drop down prompts it and same issues, Cam+MMC+BT restricted
4. Tried to locate the Application that restricts the use of the following features by using Titanium Backup PRO and was able to locate 1 app that says DM manager, tried to kill the app using Titanium backup and was able to remove the notification "Please install MDM" on the drop down menu but still same problem Cam+MMC+BT restricted.
** Anyone who can suggest remedies please post on this thread. you're reply would be greatly appreciated. Thank you very much.
Currently I have these settings:
Software number: 4.1.2
Kernel version: 3.0.72-Berrzebb-SGS3-JB-1.8
Baseband version: E210SKSMD2
Build number: JZO54K.E210SKSJMF1
You are posting in the wrong forum, anything you try from this one may brick your phone.
boomboomer said:
You are posting in the wrong forum, anything you try from this one may brick your phone.
Click to expand...
Click to collapse
okay i do understand. my apologies. kindly disregard.. thank you
Haven't you tried stock rom?
Sent from my GT-I8552 using xda app-developers app
boomboomer said:
You are posting in the wrong forum, anything you try from this one may brick your phone.
Click to expand...
Click to collapse
Might not be see posts in General section one of the models that belongs nowhere .
http://forum.xda-developers.com/showthread.php?t=1749214
jje
There is a problem with some MTK phones.
In short: If you recieve and SMS with equal sign "=" phone will reboot.
There is more here: http://forum.xda-developers.com/showthread.php?t=2795982
This is the case with my P780. I've tried to uninstall all sms aps, install 3rd party apps, nothing is helping. Phone can reboot even without displaying any notification abut new sms message.
W would like to trace this and possibly do something to eliminate this "feature".
Maybe you will have some good ideas, maybe we can find the reason together.
What should i test first? Changing baseband maybe?
Gibol666 said:
There is a problem with some MTK phones.
In short: If you recieve and SMS with equal sign "=" phone will reboot.
There is more here: http://forum.xda-developers.com/showthread.php?t=2795982
This is the case with my P780. I've tried to uninstall all sms aps, install 3rd party apps, nothing is helping. Phone can reboot even without displaying any notification abut new sms message.
W would like to trace this and possibly do something to eliminate this "feature".
Maybe you will have some good ideas, maybe we can find the reason together.
What should i test first? Changing baseband maybe?
Click to expand...
Click to collapse
Tested. On my phone Lenovo p780 with stock S228 made before 03.2014 and my wife Lenovo P780 made before 03.2014. Sended = sign and nothing happened.
Here are the configuration of our phones
1. Stock S228 mine and S227 my wifes
2. Modified modem software Xakeps.
3. Removed software like Drive... etc etc
4. Updated Lenovo ideaFriend to version 3.1
5. Rooted SuperSU v. 2.45 from ChainFire
6. Custom recovery TWRP
7. BusyBox ....
Sent from my Lenovo P780
Hello, immediately sorry for my english I hope you understand me
Well... When I wanted to upload ROM into my Lenovo ive loaded TWRP, displays the recovery. After removing wipe, date, it turned out that I can not upload MIUI rom V6. So I reset the phone, switched to the main screen without a problem. Now, however, he does not see the recovery. When I click "update recovery" in the MTK Tools and click on to recovery, the phone resets twice and returns to the main screen. This is the first problem. The second problem is that when I made the root my phone and removed some applications the system appears in the bottom corner, "security problem" and pops up all the time to install Antivirus advertising. I'd most like to upload ROM if someone could help me I was grateful. Regards.
Hello i bought this item
My problem start after installed “rootappdelete” and blicked some apps.
Now when i push on every apps i need i have a error message popup and i can only push ok for close it and come back directly on homepage screen.
I try to reload the blocked apps but nothing change.
Is first time happen this . On other device never.
So i need original rom but i not found.
(mtk6735p) firmware ALPS.L1.MP3.V2+EVEN6735+65U.L1_P34
Somedody can help me?
Thank
I registered my account on this website just to share my awesome experience with Nokia 1.
I am very much thankful to XDA and many other sites whose text assisted me in recovering my mobile.
WARNING: VERY LARGE TEXT BELOW AND ITS JUST MY EXPERIENCE, I AM NOT RESPONSIBLE IF SOMEONE TRY TO GET ANY IDEAS FROM IT AND BRICK HIS PHONE
I purchased Nokia 1 (TA-1047). My only objective was to automatically record sound from 8AM to 2 PM. So I started root process (Devmode: OK, boot loader unlock: OK, TWRP flashing and running: OK)
BUT WHAT? TWRP is asking for a password... this was not provided in the guide. I tried blank password... not OK. Then I searched the Internet and learned that if I cancel on password screen and then Wipe data then it will be fine. I did that, then made full backup (ADB), and flashed Magisk (ADB)..OK. Restarted the phone and "bump": Phone told me it failed to decrypt and then it went into TWRP boot-loop.
Then I searched again and found TA-1060 recovery bin (from this site) and stock images. I flashed TA-1060 recovery (at that time I did not know that I could go to Boot-loader from TWRP and wasted like an hour to do it using buttons - Correct method is: power off the phone, connect the usb cable, press power and volume down till you see android logo). After flashing 1060 recovery I was able to reset phone and "voila" Magisk was also there.
Now I installed Schedule Voice Recorder, Team-Viewer Host (to transfer big files remotely), App locker (to lock settings and play store), Autostart and Stay (because recorder was getting closed), Dropbox and Dropsync --- and you can guess what would have happened. My mobile kept closing them randomly even if I made Recorder and AutoStart system app and whitelisted in developer setting and set to NOT optimized battery. So I tried to disable Nokia bloat-wares and damaged the system again. This happened for a few iterations before I realized that the Nokia 1 RAM is not sufficient to handle all these apps and I got an idea to upload earlier android version (Spoiler! Hard-brick is coming).
I searched on internet for similar mobile and found Huawei Y3 2017 with same chipset and configuration, Y5 with same chipset but higher configuration. Downloaded stock rom for both. First tried flashing boot and system from TWRP but failed saying that size was different? Downloaded SP flash tool, somehow passed through drivers issue (this would require another thread ). Tried flashing (with formatting) both Y3 2017 UO00 (which was different chipset but i altered scatter file) and Y5 but it failed on some check error. After that my phone was hard bricked!
Then I downloaded nokia 1 stock firmware but it was bad scatter file (only nvram and nvdata was showing), altered it, format+flash: failed again. Searched on internet and found that if I flash wrong preloader then I am done. I was not sure if I had already done it. I altered the scatter file again to include only preloader and thankfully it showed success but any other rom after it, it failed to flash. Found something like Nokia 3 DA and tried it but also failed.
FINALLY: I found nokia 1 nb0 rom and nb0 extractor, extracted rom using that, flash it and "voila" my phone was back alive. Tried to root but failed (because serial number was not same as before and new number did not work). Then I started iterations by mixing roms from my backup and using my "proinfo.bin" and stock rom my phone revived with my own serial number. BUT, then I flashed stock preloader and lk but everything else from Huawei, it failed with check error and then also refused to format for stock rom. Searched on internet about manual formatting, did that (WARNING: starting from address where preloader ends otherwise you would format your preloader as well) then it was back okay.
Rooted again, copied scheduler in sys-priv, whitelisted, not optimize battery. Also team viewer host (normal settings) and dropbox and sync (normal settings). As a work around I have now scheduled the app to record 24 hours instead of 8AM to 2PM so that it always remain as foreground app. 11 hour testing so far so good.
QUESTION: Can I not upload lesser android version (e.g. 4.4 or 5 or 6)? If I can then how.?
UPDATE: The Recorder is killed by OS again as well as team viewer host (even when recorder apk was in system/priv-app)
Is there any way to keep it always ON?
Or is there any way to installed some previous version of android?
goodboy84h said:
UPDATE: The Recorder is killed by OS again as well as team viewer host (even when recorder apk was in system/priv-app)
Is there any way to keep it always ON?
Or is there any way to installed some previous version of android?
Click to expand...
Click to collapse
Every Nokia 1 user is facing background app crash problem. Infact Nokia 5 users also. It simply crashes background apps like pressing force close and as of now there is no solution. we have to wait until nokia releases a fix.
By the way which build number are you using?
coolboyforeva said:
Every Nokia 1 user is facing background app crash problem. Infact Nokia 5 users also. It simply crashes background apps like pressing force close and as of now there is no solution. we have to wait until nokia releases a fix.
By the way which build number are you using?
Click to expand...
Click to collapse
TA-1047
coolboyforeva said:
Every Nokia 1 user is facing background app crash problem. Infact Nokia 5 users also. It simply crashes background apps like pressing force close and as of now there is no solution. we have to wait until nokia releases a fix.
By the way which build number are you using?
Click to expand...
Click to collapse
Maybe you have so many apps in the background, I had Instagram, YouTube and Facebook life in the background and I get rare force closes or I might be lucky I have a Nokia 1 TA-1060
mattwhite7102 said:
Maybe you have so many apps in the background, I had Instagram, YouTube and Facebook life in the background and I get rare force closes or I might be lucky I have a Nokia 1 TA-1060
Click to expand...
Click to collapse
No its an os bug from nokia side. It fails to work as it should after a particular update. Maybe u r not facing coz u have only 3 apps that too light ones from good app makers, google and fb. But if u add some more like any call recorder ( as mentioned by op)u would also face same problem i believe. It doesnt thows a FC but simple kills the app in background and u dont get notified.
UPDATE :- Here is the solution
https://forum.xda-developers.com/showpost.php?p=77685710&postcount=4
goodboy84h said:
UPDATE: The Recorder is killed by OS again as well as team viewer host (even when recorder apk was in system/priv-app)
Is there any way to keep it always ON?
Or is there any way to installed some previous version of android?
Click to expand...
Click to collapse
Try this to avoid app crash. it works.
https://forum.xda-developers.com/showpost.php?p=77685710&postcount=4
HELP!!! Mine is stuck at Nokia logo screen
goodboy84h said:
I registered my account on this website just to share my awesome experience with Nokia 1.
I am very much thankful to XDA and many other sites whose text assisted me in recovering my mobile.
WARNING: VERY LARGE TEXT BELOW AND ITS JUST MY EXPERIENCE, I AM NOT RESPONSIBLE IF SOMEONE TRY TO GET ANY IDEAS FROM IT AND BRICK HIS PHONE
I purchased Nokia 1 (TA-1047). My only objective was to automatically record sound from 8AM to 2 PM. So I started root process (Devmode: OK, boot loader unlock: OK, TWRP flashing and running: OK)
BUT WHAT? TWRP is asking for a password... this was not provided in the guide. I tried blank password... not OK. Then I searched the Internet and learned that if I cancel on password screen and then Wipe data then it will be fine. I did that, then made full backup (ADB), and flashed Magisk (ADB)..OK. Restarted the phone and "bump": Phone told me it failed to decrypt and then it went into TWRP boot-loop.
Then I searched again and found TA-1060 recovery bin (from this site) and stock images. I flashed TA-1060 recovery (at that time I did not know that I could go to Boot-loader from TWRP and wasted like an hour to do it using buttons - Correct method is: power off the phone, connect the usb cable, press power and volume down till you see android logo). After flashing 1060 recovery I was able to reset phone and "voila" Magisk was also there.
Now I installed Schedule Voice Recorder, Team-Viewer Host (to transfer big files remotely), App locker (to lock settings and play store), Autostart and Stay (because recorder was getting closed), Dropbox and Dropsync --- and you can guess what would have happened. My mobile kept closing them randomly even if I made Recorder and AutoStart system app and whitelisted in developer setting and set to NOT optimized battery. So I tried to disable Nokia bloat-wares and damaged the system again. This happened for a few iterations before I realized that the Nokia 1 RAM is not sufficient to handle all these apps and I got an idea to upload earlier android version (Spoiler! Hard-brick is coming).
I searched on internet for similar mobile and found Huawei Y3 2017 with same chipset and configuration, Y5 with same chipset but higher configuration. Downloaded stock rom for both. First tried flashing boot and system from TWRP but failed saying that size was different? Downloaded SP flash tool, somehow passed through drivers issue (this would require another thread ). Tried flashing (with formatting) both Y3 2017 UO00 (which was different chipset but i altered scatter file) and Y5 but it failed on some check error. After that my phone was hard bricked!
Then I downloaded nokia 1 stock firmware but it was bad scatter file (only nvram and nvdata was showing), altered it, format+flash: failed again. Searched on internet and found that if I flash wrong preloader then I am done. I was not sure if I had already done it. I altered the scatter file again to include only preloader and thankfully it showed success but any other rom after it, it failed to flash. Found something like Nokia 3 DA and tried it but also failed.
FINALLY: I found nokia 1 nb0 rom and nb0 extractor, extracted rom using that, flash it and "voila" my phone was back alive. Tried to root but failed (because serial number was not same as before and new number did not work). Then I started iterations by mixing roms from my backup and using my "proinfo.bin" and stock rom my phone revived with my own serial number. BUT, then I flashed stock preloader and lk but everything else from Huawei, it failed with check error and then also refused to format for stock rom. Searched on internet about manual formatting, did that (WARNING: starting from address where preloader ends otherwise you would format your preloader as well) then it was back okay.
Rooted again, copied scheduler in sys-priv, whitelisted, not optimize battery. Also team viewer host (normal settings) and dropbox and sync (normal settings). As a work around I have now scheduled the app to record 24 hours instead of 8AM to 2PM so that it always remain as foreground app. 11 hour testing so far so good.
QUESTION: Can I not upload lesser android version (e.g. 4.4 or 5 or 6)? If I can then how.?
Click to expand...
Click to collapse
HELP: mine, TA-1047 is stuck at Nokia logo screen.
Please share me a life saver as you mentioned "I found nokia 1 nb0 rom and nb0 extractor, extracted rom using that, flash it and "voila" my phone was back alive."
I tried many many solutions like SP Flash Tool, Miracle Box, fastboot, .... but still failed and stuck.
I'm suffering day by day trying with no hope and now see your post. Please support me!
Much appreciate!
HELP!!!
My Nokia 1 (TA-1047) was hard bricked and won't turn on. I tried to flash my phone by SP Flashtool but my PC didn't recognize my phone. :crying::crying:
Could you give me the drivers you use and steps to recover my phone. Please help me. Thank u.