Related
Hi, sorry if this is in the wrong place, XDA won't let me post to the mahdi thread because I'm new.
I clean flashed the 6/28 Mahdi Rom for my Vs980 and audio didn't work whatsoever. Everything else was fine. Here are a couple of examples of what I mean:
Poweramp play button will be clickable but will return an error and revert to the play button
Youtube will constantly prepare to play (load, attemp to play then continue to load again)
Placing phone calls results in a black screen, then call ended screen 20 seconds later
Receiving phone calls don't show up, rings once (on the phone placing the call not my vs980) then goes to voicemail
Volume up and down doesn't give tones.
Apollo player gives "DSP manager crashed" errors
I tried freezing DSP manager, but that didn't work.
I should also mention I didn't restore using titanium, I tried reflashing 3 or 4 times, and I used the PA 4.4.4 gapps.
I can't find anyone else with this issue, hopefully someone knows what's up.
Thanks for helping if you respond!
Have you tried a different rom? One specifically for our service. I know Mahdi is compatible, but just to see.
Sent from my VS980 4G using XDA Premium 4 mobile app
[removed reply, see below]
njstein said:
Have you tried a different rom? One specifically for our service. I know Mahdi is compatible, but just to see.
Click to expand...
Click to collapse
Yes I have, I'm currently running a 4.4.2 build of Mahdi that works fine (2.4-g2-20140211). It's just the 6/25 and 6/28 that have the audio issues for me.
Nextcue said:
Yes I have, I'm currently running a 4.4.2 build of Mahdi that works fine (2.4-g2-20140211). It's just the 6/25 and 6/28 that have the audio issues for me.
Click to expand...
Click to collapse
Huh, that's weird. You probably can't post in that for trouble shooting, so have you tried a different gapps? Maybe PA is doing something? Banks gapps is an excellent package (just keep the convo going so you can hit 10 posts).
Here's a link to Banks:
http://forum.xda-developers.com/showthread.php?t=2012857
Sent from my VS980 4G using XDA Premium 4 mobile app
njstein said:
Huh, that's weird. You probably can't post in that for trouble shooting, so have you tried a different gapps? Maybe PA is doing something? Banks gapps is an excellent package (just keep the convo going so you can hit 10 posts).
Click to expand...
Click to collapse
Hmm, I'll check that out when I get a chance. Thanks so much for replying
Nextcue said:
Hmm, I'll check that out when I get a chance. Thanks so much for replying
Click to expand...
Click to collapse
I guess you are on the stock unmodded Kit Kat modem right?
JRJ442 said:
I guess you are on the stock unmodded Kit Kat modem right?
Click to expand...
Click to collapse
Maybe, how would I find out? When I first rooted I flashed Mahdi over 24a I think.
Nextcue said:
Maybe, how would I find out? When I first rooted I flashed Mahdi over 24a I think.
Click to expand...
Click to collapse
How did you get to 24A? If it was from an OTA its the stock modem. Post a picture of your baseband if you can
JRJ442 said:
How did you get to 24A? If it was from an OTA its the stock modem.
Click to expand...
Click to collapse
It was the OTA, so yes it is the stock modem.
Nextcue said:
It was the OTA, so yes it is the stock modem.
Click to expand...
Click to collapse
The current build you're on where everything works shouldn't even boot if you're on 24A. As old as that build is(2.4), its still using the JB kernel, requiring the 12b radio. I think you should go to the Malladus thread, download his baseband updater, and the ROM. And flash that. It should straighten out whatever happened. Some sound drivers are tied in with the modem/baseband for some reason on KK. That's what makes me think something with the baseband is messed up. I think I have the Malladus stuff in my Dropbox if you want links. After you get a good GPS lock in maps with Malladus. Then flash the newest build of Mahdi, not the 2.4 build you're running.
JRJ442 said:
The current build you're on where everything works shouldn't even boot if you're on 24A. As old as that build is(2.4), its still using the JB kernel, requiring the 12b radio. I think you should go to the Malladus thread, download his baseband updater, and the ROM. And flash that. It should straighten out whatever happened. Some sound drivers are tied in with the modem/baseband for some reason on KK. That's what makes me think something with the baseband is messed up. I think I have the Malladus stuff in my Dropbox if you want links. After you get a good GPS lock in maps with Malladus. Then flash the newest build of Mahdi, not the 2.4 build you're running.
Click to expand...
Click to collapse
Thank you so much, links would be very appreciated.
JRJ442 said:
The current build you're on where everything works shouldn't even boot if you're on 24A. As old as that build is(2.4), its still using the JB kernel, requiring the 12b radio.
Click to expand...
Click to collapse
Also I just checked, definitely still on the 12b radio.
Nextcue said:
Thank you so much, links would be very appreciated.
Click to expand...
Click to collapse
First question, are you using TWRP? The wipe instructions below are for TWRP
Here's the ROM https://copy.com/PDixihCzNxqLSBp
Here's the baseband updater https://copy.com/mVY1Qi2cVg3EgXS and the md5 is 941f657383ab5a6ddc8c6f4c0ee4183c make sure t matches before you flash.
Reboot to recovery and flash the baseband updater. Then hit the back button. Select wipe -> advanced wipe. Select dalvik, cache, system, data. Be absolutely sure you don't select internal. Flash Malladus and whatever gapps you prefer.
JRJ442 said:
First question, are you using TWRP? The wipe instructions below are for TWRP
Reboot to recovery and flash the baseband updater. Then hit the back button. Select wipe -> advanced wipe. Select dalvik, cache, system, data. Be absolutely sure you don't select internal. Flash Malladus and whatever gapps you prefer.
Click to expand...
Click to collapse
I am using TWRP. So after I follow your steps, go into the malladus rom and check the gps, then do I flash the latest Mahdi?
Nextcue said:
I am using TWRP. So after I follow your steps, go into the malladus rom and check the gps, then do I flash the latest Mahdi?
Click to expand...
Click to collapse
Yes, actually download maps and ensure it get a GPS lock on you. Then reboot to recovery, go to advanced wipe and select dalvik, cache, system, and data. Then flash the newest mahdi and the newest patch. The ROM is 6-28 and the patch is V6 I believe. Then gapps. You should be good to go then.
JRJ442 said:
Yes, actually download maps and ensure it get a GPS lock on you. Then reboot to recovery, go to advanced wipe and select dalvik, cache, system, and data. Then flash the newest mahdi and the newest patch. The ROM is 6-28 and the patch is V6 I believe. Then gapps. You should be good to go then.
Click to expand...
Click to collapse
Thank you so much, really, I appreciate all of your help!
Nextcue said:
Thank you so much, really, I appreciate all of your help!
Click to expand...
Click to collapse
No problem. Report back too please. And definitely make sure the md5 matches on your download for that baseband updater. That's super important
JRJ442 said:
No problem. Report back too please. And definitely make sure the md5 matches on your download for that baseband updater. That's super important
Click to expand...
Click to collapse
Will absolutely report back. I will be testing it later tonight.Just in case though: What do I do in the event I do not get a gps lock on maps?
Nextcue said:
Will absolutely report back. I will be testing it later tonight.Just in case though: What do I do in the event I do not get a gps lock on maps?
Click to expand...
Click to collapse
You'll get one. No need to worry about not getting one. You just have to do it because sometimes coming from 12B JB source, the sensors won't calibrate correctly on a ROM with true KK source. But I'm not really sure what you could do if you don't to be honest. You should get a lock fairly quick though. Just make sure location is on high accuracy and it will lock
I can no longer write any custom roms to my N6. Started with PURE 3.5 but now effects any rom i try to flash. I have brought my N6 back to factory state multiple times even relocking it. Only thing I can do is Fastboot flash N6 image from google manually piece by piece. I do have working 5.01 and phone works. Roms either hang or have errors. or just write the boot.img file. TWRP works other wise i can backup and restore, I am using 2.8.3.1. I have searched all over for a fix....
There used to be some weird mounting stuff that would make roms not boot. Thought that was worked out in pure shamu 3.1 ish.
Where do the roms hang? Did you ever fix permissions using twrp? Any kind of log you can pull?
dipstik said:
There used to be some weird mounting stuff that would make roms not boot. Thought that was worked out in pure shamu 3.1 ish.
Where do the roms hang? Did you ever fix permissions using twrp? Any kind of log you can pull?
Click to expand...
Click to collapse
I had no problem updating Pure for over a month from like 2.0 to 3.4.
they all hang when writing to system as far as i can tell. happens regardless of Pure....from a fresh clean image of 5.0 or 5.01 i can not flash any roms. driving me nutzo....i can no longer flash pure 3.4 either but i can restore the phone from a nandroid backup i had on my pc and run Pure 3.4 just fine.
Did you wipe everything except internal storage first? I had this issue earlier until I realized that I forgot to do that when coming from the stock ROM.
Pilz said:
Did you wipe everything except internal storage first? I had this issue earlier until I realized that I forgot to do that when coming from the stock ROM.
Click to expand...
Click to collapse
yes and both cache.....
also made sure system not mounted.
very frustrating.
Bignoze73 said:
yes and both cache.....
also made sure system not mounted.
very frustrating.
Click to expand...
Click to collapse
That is very odd, did you try reflashing TWRP or using a different version.
Pilz said:
That is very odd, did you try reflashing TWRP or using a different version.
Click to expand...
Click to collapse
mutiple times......tried all versions of TWRP too.
I can write a custom kernal like elementalx no problem.....just not roms.
Bignoze73 said:
mutiple times......tried all versions of TWRP too.
Click to expand...
Click to collapse
It doesn't make sense considering you also flashed back to stock. Have you also tried to flash a ROM from your PC rather than from your phone? There has to be some reasonable explanation for why it's not working.
Pilz said:
It doesn't make sense considering you also flashed back to stock. Have you also tried to flash a ROM from your PC rather than from your phone? There has to be some reasonable explanation for why it's not working.
Click to expand...
Click to collapse
how do you do that? the custom roms dont have system.img file like N6 image. The Pure 3.92 is in .dat format, another rom is folders. I also get checksum errors when extracting.
I also noticed in the last 24 hours there are 2 other threads with people have almost the same issues flashing roms. I think it has something to do with TWRP but no matter becuase no version works for me.
Bignoze73 said:
how do you do that? the custom roms dont have system.img file like N6 image. The Pure 3.92 is in .dat format, another rom is folders. I also get checksum errors when extracting.
I also noticed in the last 24 hours there are 2 other threads with people have almost the same issues flashing roms. I think it has something to do with TWRP but no matter becuase no version works for me.
Click to expand...
Click to collapse
If you restore your stock recovery on your phone you could try this.
Make sure TWRP is not installed on your phone and that the stock recovery is installed and working:
Have TWRP in your platform tools folder named however you want
Then use "fastboot boot recovery 'whatever you named TWRP' "
This will boot TWRP without installed it. Then try to flash the ROM using TWRP. You can also use the"adb push" to sideload the ROM onto your phone so you can find it via TWRP.
nope did not work.....roms just hang or flash new boot.img only.
i even tried erasing recovery partion and reflashing stock than twrp 2.8.3.1......that did not work either....something is stopping TWRP from writing to system.
thanks for your help
Bignoze73 said:
nope did not work.....roms just hang or flash new boot.img only.
i even tried erasing recovery partion and reflashing stock than twrp 2.8.3.1......that did not work either....something is stopping TWRP from writing to system.
thanks for your help
Click to expand...
Click to collapse
You're welcome, have you tried to contact some of the devs here to see if maybe they could help? I think the worst case scenario would be to RMA the phone.
Pilz said:
You're welcome, have you tried to contact some of the devs here to see if maybe they could help? I think the worst case scenario would be to RMA the phone.
Click to expand...
Click to collapse
RMA the phone??? ?What are you gonna tell them?? ? That you can't flash any custom Roms through TWRP?? ?
laureanop said:
RMA the phone??? ?What are you gonna tell them?? ? That you can't flash any custom Roms through TWRP?? ?
Click to expand...
Click to collapse
No obviously not look, but if you have other issues (in assuming you might if you can't flash a ROM) then that's the worst case scenario option.
Pilz said:
No obviously not look, but if you have other issues (in assuming you might if you can't flash a ROM) then that's the worst case scenario option.
Click to expand...
Click to collapse
This is a tough one cause if his factory image works without issues they're gonna have no reason to send him a replacement
laureanop said:
This is a tough one cause if his factory image works without issues they're gonna have no reason to send him a replacement
Click to expand...
Click to collapse
That's true, but there must be something wrong if he can't flash anything else so I'm sure he could find some issues.
Pilz said:
That's true, but there must be something wrong if he can't flash anything else so I'm sure he could find some issues.
Click to expand...
Click to collapse
Is there a tool or command to do a full memcheck of both ram and storage
rgraville said:
Is there a tool or command to do a full memcheck of both ram and storage
Click to expand...
Click to collapse
I'm not sure I've never had the need to do one from adb or fastboot
Pilz said:
I'm not sure I've never had the need to do one from adb or fastboot
Click to expand...
Click to collapse
yeah its pretty nuts....how can I return a phone that works fine other than the fact it wont flash a custom rom?
Must be another way to write a rom but TWRP......
thanks!
Bignoze73 said:
yeah its pretty nuts....how can I return a phone that works fine other than the fact it wont flash a custom rom?
Must be another way to write a rom but TWRP......
thanks!
Click to expand...
Click to collapse
I assume you are also out of the return window. Well if you are unlucky or lucky (depending on how you view it) you could have an issue eventually. They will RMA for burn in, camera issues etc... The camera issue was common in the earlier production models that I had. There should be another method, I would look into it if you have time.
i bricked my nexus 6 and i flashed stock once again, but snow in free space is 23gb and before it was 25gb? how could this happen? or how to get that space again.
You must factory reset using stock recovery.
Z-Man™ said:
You must factory reset using stock recovery.
Click to expand...
Click to collapse
with stock rom or custom rom?
23gb is the normal amount if you are running stock, not 25gb.
simms22 said:
23gb is the normal amount if you are running stock, not 25gb.
Click to expand...
Click to collapse
that's weird, i though i had 25gb :v
yunior597 said:
that's weird, i though i had 25gb :v
Click to expand...
Click to collapse
have you updated since seeing 25gb? i mean i have 25gb right now, but im running rastapop on android 5.0.2. rastapop removes some fat, so itll be a little more space left over. but when i was on stock android 5.0, it said 23gb.
simms22 said:
have you updated since seeing 25gb? i mean i have 25gb right now, but im running rastapop on android 5.0.2. rastapop removes some fat, so itll be a little more space left over. but when i was on stock android 5.0, it said 23gb.
Click to expand...
Click to collapse
at the moment using a custom rom, would have to go back to stock and try.
yunior597 said:
at the moment using a custom rom, would have to go back to stock and try.
Click to expand...
Click to collapse
ah, i see. yes then, each rom takes up a differing amount of room.
what about if i install stock recovery and factory reset it with the custom rom installed?
yunior597 said:
what about if i install stock recovery and factory reset it with the custom rom installed?
Click to expand...
Click to collapse
itll just clear your data. it wont change your total amount of storage.
simms22 said:
23gb is the normal amount if you are running stock, not 25gb.
Click to expand...
Click to collapse
25 is with stock but its just like the last 2 nexus devices sometimes when you flash stock you lose a little storage and a factory reset running stock recovery will solve this. I just had this happen. Here's a SS on stock ROM. When I flashed stock I had like 23 until the reset.
yunior597 said:
with stock rom or custom rom?
Click to expand...
Click to collapse
Stock recovery. Not sure about while a custom ROM is installed I always do the reset right after flashing stock.
So i got a nexus 6 and i need to update it to android 5.1.0 ?
Status: Unlocked though ADB rooted though c.f auto root and recovery though adb. encrypted stock 5.0.1 rom.
And i want to install chroma rom with android lollipop 5.1.0? how do i do that? do i need some sort of new bootloader or radio as i heard someone talking about?
Thx.
XDAcube said:
So i got a nexus 6 and i need to update it to android 5.1.0 ?
Status: Unlocked though ADB rooted though c.f auto root and recovery though adb. encrypted stock 5.0.1 rom.
And i want to install chroma rom with android lollipop 5.1.0? how do i do that? do i need some sort of new bootloader or radio as i heard someone talking about?
Thx.
Click to expand...
Click to collapse
If you unlocked the boot loader, rooted and have TWRP custom recovery, you just need to :
1. Download rom and gapps to your phone. Links should be found in the OP of the ROM's thread. If you wish Google to restore your apps be sure you have selected the backup-auto restore in settings.
2. Do unencryption now if you wish.
3. Boot into TWRP recovery and wipe a couple times.
4. From TWRP, install the rom and gapps.
5. Reboot system, sign into your Google account and let it download and restore your apps.
6. Reboot system once more & you should be gtg.
wtherrell said:
If you unlocked the boot loader, rooted and have TWRP custom recovery, you just need to :
1. Download rom and gapps to your phone. Links should be found in the OP of the ROM's thread. If you wish Google to restore your apps be sure you have selected the backup-auto restore in settings.
2. Do unencryption now if you wish.
3. Boot into TWRP recovery and wipe a couple times.
4. From TWRP, install the rom and gapps.
5. Reboot system, sign into your Google account and let it download and restore your apps.
6. Reboot system once more & you should be gtg.
Click to expand...
Click to collapse
So i dont need to wipe? or flash a bootloader and radio since im coming from 5.0.1? you know like vanillapop 5.1 requires you to flash bootloader and radio if coming from 5.0.X?
XDAcube said:
So i dont need to wipe? or flash a bootloader and radio since im coming from 5.0.1? you know like vanillapop 5.1 requires you to flash bootloader and radio if coming from 5.0.X?
Click to expand...
Click to collapse
Should be in the Chroma OP or close thereby as to whether you need the boot loader.
I would think for sure a wipe or two. Boot loader, maybe. Radio, at your discretion.
wtherrell said:
Should be in the Chroma OP or close thereby as to whether you need the boot loader.
I would think for sure a wipe or two. Boot loader, maybe. Radio, at your discretion.
Click to expand...
Click to collapse
Cool we look in there again later thx for help
XDAcube said:
Cool we look in there again later thx for help
Click to expand...
Click to collapse
I checked. Instructions and prerequisites are in the OP of the Chroma thread.
I also updated my Nexus 6 with 5.0.1, unlock and root, to 5.1 without losing data. I just had to re-root it afterwards.
I used Wugfresh Nexus root toolkit.
In short I used "Flash stock + unroot", in which I selected "Enable no-wipe" and "force-flash".
After this I rerooted the device from within NRT.
Worked like a charm!
wtherrell said:
I checked. Instructions and prerequisites are in the OP of the Chroma thread.
Click to expand...
Click to collapse
So no need to flash bootloader or radio then?
XDAcube said:
So no need to flash bootloader or radio then?
Click to expand...
Click to collapse
Doesn't appear so.
thijsniehof said:
I also updated my Nexus 6 with 5.0.1, unlock and root, to 5.1 without losing data. I just had to re-root it afterwards.
I used Wugfresh Nexus root toolkit.
In short I used "Flash stock + unroot", in which I selected "Enable no-wipe" and "force-flash".
After this I rerooted the device from within NRT.
Worked like a charm!
Click to expand...
Click to collapse
Well thats stock rom right? i want something custom and cool
wtherrell said:
Doesn't appear so.
Click to expand...
Click to collapse
Okay thanks will look into it!
XDAcube said:
Well thats stock rom right? i want something custom and cool
Okay thanks will look into it!
Click to expand...
Click to collapse
Checkout 2nd post in that thread. Also check out the other exciting rom choices in the Nexus 6 android development threads.
wtherrell said:
Checkout 2nd post in that thread. Also check out the other exciting rom choices in the Nexus 6 android development threads.
Click to expand...
Click to collapse
Will do thanks great device! i just got it from criagslist today already flashing! i have something to play with tonight!
XDAcube said:
Well thats stock rom right? i want something custom and cool
Click to expand...
Click to collapse
Yup stock indeed... Stock ROM, stock recovery..
thijsniehof said:
Yup stock indeed... Stock ROM, stock recovery..
Click to expand...
Click to collapse
Just what i thought!
wtherrell said:
Checkout 2nd post in that thread. Also check out the other exciting rom choices in the Nexus 6 android development threads.
Click to expand...
Click to collapse
Do i need the android 5.1 bseband for chroma?
And the bootloader wasn,t need right? scared to brick it
XDAcube said:
Do i need the android 5.1 bseband for chroma?
And the bootloader wasn,t need right? scared to brick it
Click to expand...
Click to collapse
Oooook... I'm confused too. I'm on dirty unicorns 5.0.2.. I want to upgrade to 5.1... Some instructions say to flash the unencrypted kernel and I also have looked into the boot img and baseband thread.. But when would I need to do all of this? I need someone willing to explain it like I'm five how and when to update the baseband, etc.. I already backed up my internal storage so I'm ready to do whatever I have to to flash Chroma or any other non stock 5.1 ROM.
kaslopis said:
Oooook... I'm confused too. I'm on dirty unicorns 5.0.2.. I want to upgrade to 5.1... Some instructions say to flash the unencrypted kernel and I also have looked into the boot img and baseband thread.. But when would I need to do all of this? I need someone willing to explain it like I'm five how and when to update the baseband, etc.. I already backed up my internal storage so I'm ready to do whatever I have to to flash Chroma or any other non stock 5.1 ROM.
Click to expand...
Click to collapse
Well can you be my guinea pig and flash chroma without doing everything else? worst thing that could happen is it not boot into the rom and wrong radio will just make your phone not pickking up signel intil you flashed radio. but chroma dont say anything about flashing bootloader so i dont think its needed.
BTW ims still on rooted stock 5.0.1.
Bump!
Good night. Has anyone noticed the flashing of the cell network signal when using custom ROM? Sometimes even the signal disappears completely as if it did not have a chip and does not give a network being that return the operation just by restarting. If someone has already experienced this and has the solution, please report it. I have already used all the customs for the x4 bike and they all stay that way.
appreciate
What custom ROM are you using?
How did you install it?
Did you use the partitions zip before installing the ROM?
dougo007 said:
What custom ROM are you using?
Any custom ROM.
How did you install it?
Boot to TWRP.
Flash copy partition
Swipe to factory reset
Boot back to TWRP recovery
flash Rom + TWRP zip
Boot back to TWRP recovery
Flash GApps
Wipe Cache + Dalvik
Reboot to System
Did you use the partitions zip before installing the ROM?
Click to expand...
Click to collapse
Yes, i do it.
Ok; you're steps appear correct.
A thought occurred to me and this is easier to do than anything else.
Are you having any issue with the SIM card?
Is it making good contact?
Are you using Google Fi by chance?
dougo007 said:
Ok; you're steps appear correct.
A thought occurred to me and this is easier to do than anything else.
Are you having any issue with the SIM card?
R: No.
Is it making good contact?
R: Yes
Are you using Google Fi by chance?
Click to expand...
Click to collapse
R: No
Noslineg said:
R: No
Click to expand...
Click to collapse
Which ROM?
dhinesh_cool said:
Which ROM?
Click to expand...
Click to collapse
Payton PPW29.69-26. I already used itnup tobGoogle FI, but the problem came up.
I suggest trying one of the solutions here: https://www.technobezz.com/fix-no-signal-android/
They recommend to first restore your phone to stock, make sure you get the right variant.
Just try to flash another radio (modem) . I had similar issues with RETBR modem ) Now I`m using FI modem and everything is OK (Havoc 2.1 ROM)