A friend got the Motorola Droid 4 (maserati) and gave it to me to install a custom ROM on it, to get rid of the bloat on stock.
I installed the latest stable CyanogenMod on it (cm-10.2.1), but then the phone would not send any SMS, it did received them though.
I tried this guide but it didn't work (the SIM card did work in other phones). I then proceeded to install a snapshot version of CyanogenMod (cm-11-20140708-SNAPSHOT-M8) and followed this guide, that didn't help either.
When I finally gave up, I went back to stock and the SMS sending problem was fixed, but now a new problem came up with the cellular and the WiFi signals being very low and sometimes nonexistent.
Then I found this thread and did the following:
- Rooted and installed custom recovery using @mattlgroff's DROID 4 Utility XT894 Jellybean guide.
- Went into custom recovery and did factory reset.
- WITHOUT EXITING CUSTOM RECOVERY, I installed the latest CM again.
- Again, WITHOUT EXITING CUSTOM RECOVERY , I installed @Mentor.37's Patch to fully enable GSM on Verizon CDMA Android phones patch.
- Success!
SMS sending works now on other ROM besides stock and the low signals on cellular and WiFi, got fixed too.
fixed
I have issues too but no one can help me.
Sent from my SM-G800H using XDA-Developers mobile app
I have not tested this, it's based on other reports in the forum. You can try:
1. Flash stock Lollipop for your phone model through Odin twice (yes, it's weird but some users only had success after the second flash);
2. Flash stock KikKat for your phone model using Odin twice, check if everything works then apply OTA to latest version;
3. For G800H only: you may need to flash an old Russian stock KitKat to fix things, it was reported to fix missing Wi-Fi and no SIM, for instance, then upgrade to Lollipop.
Hi
I have installed many of the Android 7.0 ROMS for Shamu and all of them have this annoying problem:
When I dial out I cannot hear the ring or the other person.
When I receive a call I don't often hear the other person but they may hear me.
Yes I've installed the N6 boot loader and radio and do not load any other mods, custom kernels.
I just can't figure this out. Any ideas? Is there a Android 7.0 firmware that I need to install to prepare my Shamu for Android 7?
Thanks
Aussie
I had this same problem, I had to re flash stock 7.0 and the problem was gone. No idea what caused it
Flashing Stock 7.0
aroy97 said:
I had this same problem, I had to re flash stock 7.0 and the problem was gone. No idea what caused it
Click to expand...
Click to collapse
Did flashing stock 7.0 re-lock bootloader? Were you able to unlock the phone?
Thanks
Aussie
aussie1234 said:
Did flashing stock 7.0 re-lock bootloader? Were you able to unlock the phone?
Thanks
Aussie
Click to expand...
Click to collapse
Flashing stock does not relock the bootloader.
Didn't work
Ok I flashed stock 7.0 using Wugfresh's tool.
But still when I use the phone I can't hear who is on the other end.
Really odd!
Anyone have any suggestions?
Thanks
Aussie
I'm having the same issue on a stock Nougat phone as well. The problem appeared a few days ago out of the blue. The only band aid fix I've found is the sound about app and force assigned the mic and earpiece functions.
Sadly, this doesn't address the main issue in the first place.
none
Why are you using Wugfresh? Plug the phone in the computer and when it communicates with the phone tap the menu bar that says it's charging, when you open that tick allow files/folders, the second option. Then put your files on the root of internal storage, wipe the entire system then flash your rom, you don't need Wugfresh.
If you lose your data who cares, just set the phone up again and you should be good to go, this is much more dependable as I use to use Wugfresh, you do know how to get into recovery and install that way? You will want to do a full wipe, then flash
---------- Post added at 07:53 AM ---------- Previous post was at 07:50 AM ----------
USMC retired said:
Why are you using Wugfresh? Plug the phone in the computer and when it communicates with the phone tap the menu bar that says it's charging, when you open that tick allow files/folders, the second option. Then put your files on the root of internal storage, wipe the entire system then flash your rom, you don't need Wugfresh.
If you lose your data who cares, just set the phone up again and you should be good to go, this is much more dependable as I use to use Wugfresh, you do know how to get into recovery and install that way? You will want to do a full wipe, then flash
Click to expand...
Click to collapse
If you need anything else you can PM me
I didn't realize there was a thread on this already.
I'm using Pure Nexus and the other end would go silent for about 5 seconds and then come back...so that's a bit different than what you guys are experiencing.
stevew84 said:
I didn't realize there was a thread on this already.
I'm using Pure Nexus and the other end would go silent for about 5 seconds and then come back...so that's a bit different than what you guys are experiencing.
Click to expand...
Click to collapse
have you tried reflashing your radio? Maybe try flashing a MM radio as well
Just wanted to chime in, I think this is actually more of a VoLTE/HD issue. It happens to my N6 that's still on MM. Sometimes the dialtone/ring is there, other times it's not. Would love to know of there's a fix!
Found a fix..
Hello all.
I found a fix to Shamu+Nougat ROM problem when I am called I do not hear the other person and vice versa.
To install Factory Nougat from Google: https://developers.google.com/android/nexus/images
FIRST backup your phone (contacts, files, pics, movies etc) as this will totally erase EVERYTHING!
When you are on the Factory Images for Nexus Devices page click "backed up to your Google Account" then go click 'back' on your browser and click on 'Acknowledge' to see the list of Factory Nougat ROMS for Shamu come up on the right.
Download the Android 7.0 Factory ROM for Shamu/Nexus 6.
Do not flash this stock ROM using Wugfresh's tool. Instead follow precisely the 'Flashing Instructions' on the page https://developers.google.com/android/nexus/images. Allow the phone to reboot and fully set up. Restart the phone again.
Then use Wugfresh to Root the phone and also to install custom recovery (I already have unlocked bootloader).
Now, nothing against Wugfresh Tool (I do not know why the flashing method above works better) as Wugfresh has saved my phone many times.. Its just that Googles recommended flashing instructions worked best.
Now I use the phone and not only do I hear the caller and they hear me I have much better reception (Australia). Yes I did previously flash latest radio but the above method seemed to improve my Shamu 100%.
What I have not done yet is flash a custom ROM in case the problem re-appears. But my phone is rooted and unlocked so I can install other mods that work with Nougat.
Hope this works for you.
Cheers
Aussie
Another Fix Part 2
Hi
I stumbled on another method that has seemed to work:
Ensure you have unlocked bootloader.
Flash Tupacs Android 6.0 MOB31H ROM from http://forum.xda-developers.com/nexus-6/development/rom-rooted-deoxeded-fast-stable-t3252922
(*Note I used his MOB31E Android 6.0 ROM so I am presuming current MOB31H will work).
Credit to this ROM goes to tupac4u as I am not a Developer.
I then flashed SuperUser but did not flash a custom kernel.
Setup the ROM as usual.
Selected Settings - About Phone - System updates and let the phone install the Android 7 OTA update. Be aware its a 878Mb download.
Let the update download and fully install. I had TWRP recovery and the update still installed fine.
After installation fully completed I enabled Developer Options and USB Debugging.
Then using WugFresh's excellent tool http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 I applied Root and Custom Recovery.
I also flashed Radio 5.39R which I found works best.
Now my phone works very well and (for now) now I can hear the caller and they can hear me.
Cheers
Aussie
aussie1234 said:
Hi
I stumbled on another method that has seemed to work:
Ensure you have unlocked bootloader.
Flash Tupacs Android 6.0 MOB31H ROM from http://forum.xda-developers.com/nexus-6/development/rom-rooted-deoxeded-fast-stable-t3252922
(*Note I used his MOB31E Android 6.0 ROM so I am presuming current MOB31H will work).
Credit to this ROM goes to tupac4u as I am not a Developer.
I then flashed SuperUser but did not flash a custom kernel.
Setup the ROM as usual.
Selected Settings - About Phone - System updates and let the phone install the Android 7 OTA update. Be aware its a 878Mb download.
Let the update download and fully install. I had TWRP recovery and the update still installed fine.
After installation fully completed I enabled Developer Options and USB Debugging.
Then using WugFresh's excellent tool http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 I applied Root and Custom Recovery.
I also flashed Radio 5.39R which I found works best.
Now my phone works very well and (for now) now I can hear the caller and they can hear me.
Cheers
Aussie
Click to expand...
Click to collapse
Has there been a listed fix for people who haven't rooted their nexus?
This will be for the SM-G935D/SC-02H Japanese variant of the s7 edge.
Stock ODIN firmware: https://www.androidfilehost.com/?fid=457095661767130814 (Marshmallow)
TWRP 3.0.3-0: https://www.androidfilehost.com/?fid=817550096634747128
Rooted Rom: https://www.androidfilehost.com/?fid=385035244224413763
HKernel for hero2qltedcm:https://www.androidfilehost.com/?fid=745425885120706416
Kernel includes:
CVE updated
Permissive
F2FS support
Ramdisk changes the same as hero2qltechn variant. (All changes are the same)
Kernel Change-log:
https://github.com/travismills82/android_kernel_samsung_msm8996/commits/tw-6.0
TWRP Unofficial:
F2FS Support
More partitions supported for backup and restore compared to official version
How to root this device: https://forum.xda-developers.com/s7-edge/how-to/guide-sm-g9350-s7-edge-qualcomm-sd820-t3410969
Reserved
travis82 said:
This will be for the Japanese variant of the s7 edge this is an unlocked model also.
Stock ODIN firmware: https://www.androidfilehost.com/?fid=457095661767130814 (SC02HOMU1APL2)
TWRP: Coming soon
Debloated Rom: Coming soon
Kernel: Coming soon
Click to expand...
Click to collapse
Can this be used for sm g9350 hongkong?
Sent from my SM-G9350 using Tapatalk
Please use common sense and read ITS FOR THE JAPANESE VARIANT.. READ THE MODEL #. Good gosh stop posting stupid questions dude.
Thanks I'll try this when I get to work.
I can't seem to unlock my bootloader, I'm unable to flash TWRP and enter the recovery. It just says Recovery mode -> Warranty bit set: Recovery and enters into a normal boot after trying it a few times.
Edit:
used the official TWRP and recovery now works. Now trying to install the rom
Edit2:
When trying to install it keeps giving me the following error:
This package is for "SC-02h,hero2qledcm" devices; this is a "hero2qltedcm"
Update process ended with ERROR: 7
Error installing zip file '/sdcard/TWRP/SC-02H_Debloated.zip'
Edit3:
I edited the update-script and removed the assert.
However I don't notice any changes in the rom itself. It still has some bloatware (docomo stuff)
ahh ok i thought it would use sco2h not dcm I can fix that sorry, and I assume twrp is doing the same. I will use a dcm kernel in twrp, let me know if that kernel boots please I dont have the device in hand so I am relying on you all to let me know.
USE crom.apk to unlock bootloader you should find it in galaxy apps store. I'm pretty sure others have unlocked their bootloader doing the same thing. I also used to have someone install my hkroms and kernels on the jap variant so I know you can unlock the bootloader.
CROM: https://www.androidfilehost.com/?fid=385035244224394932
can you unlock the bootloader with that, its a link to what we used to unlock ours.
I need you to unlock your bootloader first please. Sounds like that is the issue.
If I run that app it just exits with Crom Service has stopped working.
Your rom works fine, it has root which is what I needed the most.
Just wish there was a way to remove the sim lock from the device without having to beg Docomo.
I bet I have my asserts all messed up here man I'm sorry. I see SC-02H than hero2qltedcm, than SM-G935D soo I need to get this in the correct order. Would you mind shooting me a pm so I can hangouts you so we can knocks this out quickly?
updated op with twrp recovery and kernel.
This works, root and most of the bloated software is gone
Off topic question (need some insight)
You have started to make a working TWRP for the Docomo variant - thank you for your work (hopefully people in JP using the Docomo version find success).
I know this is off topic but I thought you could provide me with a better understanding.
I am currently using the au KDDI variant (SCV33-Snapdragon) and have successfully installed TWRP (3.0.2-0) with ability to mount /data following xda, youtube, and a Vietnamese forum using google translate; BUT I am unable to keep TWRP ability to mount /data after flashing re-engineered boot file via odin to apply root (Snapdragon Variant Root). TWRP can still be used to go into recovery, mount /ext sdcard, and reboot. I've tried many different styles of rooting after and before installing TWRP, in addition to flashing in different ways - but I still failed. It's either have full working TWRP that can mount /data but without root; or, have root but TWRP that can't mount /data (basically useless as it cannot install anything nor, make backups).
I apologize for such long response, any insight or somewhere you can point me to where I can do more research, as this is how far I have come so far, but still fail to acquire both (Yes I have watched numerous YT vids and read countless post stating devs have not yet found a way on the US-Snapdragon variants, which I understand this may apply to the JP variant too) . Thank you.
With the development of ROMs for the Exynos variants (SG935F/FD) moving along apace... I'm wondering if it is feasible to use one of those ROMs with this kernel.
I did something similar to get a custom ROM made for an AT&T S4 onto my DoCoMo S4 (SC-04E) without issues.
Is that a stupid question?
SCV33 looks exactly the same as SC-02H. What's the difference? single sim dual sim? Can you use sc-02h roms for it? I need more information unless you guys want to start donating me devices.
bu06034 said:
With the development of ROMs for the Exynos variants (SG935F/FD) moving along apace... I'm wondering if it is feasible to use one of those ROMs with this kernel.
I did something similar to get a custom ROM made for an AT&T S4 onto my DoCoMo S4 (SC-04E) without issues.
Is that a stupid question?
Click to expand...
Click to collapse
You guys should never flash an engineering kernel anymore. There is no need since you have a custom kernel and ramdisk and twrp now since I made them. Also those are exynos not qualcomm you can port it but it will be a major task to do.
travis82 said:
You guys should never flash an engineering kernel anymore. There is no need since you have a custom kernel and ramdisk and twrp now since I made them. Also those are exynos not qualcomm you can port it but it will be a major task to do.
Click to expand...
Click to collapse
First, I really apprecate the work you have put in on bringing ROOT and TWRP to users in Japan. If I can help by doing some testing for you with my DoCoMo model, I'd be happy to do so!
Regarding my original question, I was not talking about an engineering kernel. I was thinking that if I flashed a custom ROM for the SG-935F Hong Kong (Exynos) model, and then flashed your kernel over it, would it work?
As I understand it, the kernel is the interface between the OS and the hardware. Maybe that is ignorant? The reason I ask is because this process was quite common for Japanese S4 users to employ custom ROMs for US S4s; i.e. Flash the US custom ROM (e.g. Mokee or Albee95) and then flash the Japanese S4 kernel onto it.
I understand the question might seem silly to you, but I don't have the hundreds of hours required to reach your level of expertise. I have invested sufficient time to understand much of the jargon; and the tools and methods employed to get root and flash ROMs. More than that, I rely on asking the experts, like you. :good:
you would have to port firmware framework and a bit of other things, secondly hong kong does not self exynos versions here. It's all Qualcomm.
SCV33 waiting for someone to flash this kernel on it to let me know if its compatible or not.
Anyways updated main thread with BETA 2.
Enjoy,
Travis82
SCV33 test 1
travis82 said:
SCV33 waiting for someone to flash this kernel on it to let me know if its compatible or not.
Anyways updated main thread with BETA 2.
Enjoy,
Travis82
Click to expand...
Click to collapse
Travis,
TESTED (Semi-working)
I've done some testing on my SCV33 variant using what you've made for the SC-02H.
[Kernel]
I flashed the HKernal Beta 2, using the SC-02H FW, and TWRP Unofficial you've provided onto my SCV33 Galaxy S7e and it is really snappy and fast. Very nice kernel. Any DoCoMo users out there should flash this - though still beta it does the job. I had no problems flashing this in TWRP.
[TWRP Unofficial]
I was able to mount all partitions - works. I had no problem flashing this using Odin.
[Problems I've Encountered]
* After rebooting into TWRP Unofficial many times. My log reads "Unable to mount /steady." I have no idea what this is or what partition it belongs too; but, TWRP is still able to do everything else such as mount /data, wipe /system, etc. - I don't think its a big issue to be honest. Just wanted to let you know.
* After installing everything and everything working fine. I do not/cannot communicate with networks (cannot connect to wifi, cannot call, and no data). I had check SIM status = not available, IMEI = Unknown, SN = Unknown. I had made an EFS back up of my KDDI rom with working network communication and restored with with TWRP Unofficial. Installation via TWRP log has stated successful, but upon reboot problem has not been fixed. Any ideas I should try? I also believe the software from the SC-02H OS handles how im about to connect to data towers and catch frequencies. Putting in my own APN does not work.
* Crom Service.apk you've provided at an earlier comment to unlock bootloader, which I've installed, does not work. All it does is FC when trying to open the app - installation is fine. I had also tried getting one from the internet, and looking for it at the Samsung Galaxy App Store - the internet one does the same, FC. Samsung Galaxy App Store does not have Crom Service available. I am assuming SCV33 wont ever be able to unlock bootloader.
* Debloated Rom Zip does not work, after doing a clean install to Stock Odin, installing TWRP Unofficial, system ext4 format, wiping /system /data /internal storage /dalvikArt /cache, and flashing Debloated Rom Zip with TWRP - states installed successful and boots up. Though upon booting I still have all the bloat there. In addition, many FCs from many different apps, even after reboot (e.g. tap and play, google play store, google services). The rom still functions after a couple more reboots after a /dalvikART cache wipe, but it just doesn't seem as fast as the stock one though. I believe this maybe a conflict due to my device, and myself as well.
----
Oh BTW the SCV33 is:
*SM-G935J
*OS 6.0.1
*Single SIM only
I will try my best do to other methods on trying to get this to fully work, but the Network Communication thing always halts my progress. I really dig this kernel man.
Again, thank you for your hard work and dedication to the Snapdragon Variant its very much appreciated :highfive:. Looking at the Exynos sub-forum I get so jelly at times.
OK is yours has a different modem then the rest. Also your partitions might be a bit different, I really need that device in my hands to look at the partition layout. If you can find SCV33 kernel source I will be more than happy to make a kernel for this variant also. I call my kernels beta because it's just how I do it.
Ok found your source for the kernel I'll check out the configs and maybe make a kernel later on this week.
SM-G935J (SCV33)
Here is a test kernel: https://www.androidfilehost.com/?fid=529152257862698452
Rooted rom: https://www.androidfilehost.com/?fid=529152257862698453
Let me know if there is any issues.
I am being plagued by wifi issues ever since i went to a new version of Purenexus. It seems to have something to do with going to 7.1.1
I've tried the older version of the rom that was working fine before, but i still seem to have wifi issues even in these older versions now.
i tried resurection remix, but still have the same issue.
after a while the wifi wont be connected and it says authentication problem, or sometimes shows it as simply discconected.
i can manually forget the network and re add it and it seems to work fine for a while.
Durring troubleshooting today, i have tried to resey my router, even upgraded the firmware,
anyways, i'd like to flash the factory image to test to see if i still have issues. but i want to make sure that if i install 7.1.1 factory image, or 7.0 that i can still re-flash twrp from adb or am i going to have to find a root exploit?
if i flash a factory image does it "relock" my bootloader? i guess that is the more important question
thanks.
citrusfizz said:
I am being plagued by wifi issues ever since i went to a new version of Purenexus. It seems to have something to do with going to 7.1.1
I've tried the older version of the rom that was working fine before, but i still seem to have wifi issues even in these older versions now.
i tried resurection remix, but still have the same issue.
after a while the wifi wont be connected and it says authentication problem, or sometimes shows it as simply discconected.
i can manually forget the network and re add it and it seems to work fine for a while.
Durring troubleshooting today, i have tried to resey my router, even upgraded the firmware,
anyways, i'd like to flash the factory image to test to see if i still have issues. but i want to make sure that if i install 7.1.1 factory image, or 7.0 that i can still re-flash twrp from adb or am i going to have to find a root exploit?
if i flash a factory image does it "relock" my bootloader? i guess that is the more important question
thanks.
Click to expand...
Click to collapse
There will be no locking of the bootloader unless you issue the command. No exploits needed. Just flash away...