[Q] Can't install any 4.2 ROM - Verizon Samsung Galaxy S III

I was hoping to try out one of the 4.2 builds tonight, but every time I try to flash one through TWRP it just says "Failed"; I've tried CM10.1 and Eclipse ROM and they both had the same result. Also tried redownloading ROMs and re-copying them to my SD card, still no change. Can anyone tell me what I'm doing wrong here? I've never had a problem flashing any ROM before.

Devilicus said:
I was hoping to try out one of the 4.2 builds tonight, but every time I try to flash one through TWRP it just says "Failed"; I've tried CM10.1 and Eclipse ROM and they both had the same result. Also tried redownloading ROMs and re-copying them to my SD card, still no change. Can anyone tell me what I'm doing wrong here? I've never had a problem flashing any ROM before.
Click to expand...
Click to collapse
What version of TWRP are you running?
If you haven't done it lately, I would suggest updating your twrp to the latest and trying again.

I'm running the newest TWRP (I think), version 2.4.1.0

Devilicus said:
I'm running the newest TWRP (I think), version 2.4.1.0
Click to expand...
Click to collapse
Weird. I am on that same version and have been flashing 4.2 roms for the last few weeks without any issues.
A few things I would try:
-Double check the md5 of the rom you are flashing
-Make sure it is a d2vzw rom
-Wipe caches, delete user data and wipe system
-Put the rom on the internal sdcard before flashing.
Other than that, I got nothing

Relentless D said:
Weird. I am on that same version and have been flashing 4.2 roms for the last few weeks without any issues.
A few things I would try:
-Double check the md5 of the rom you are flashing
-Make sure it is a d2vzw rom
-Wipe caches, delete user data and wipe system
-Put the rom on the internal sdcard before flashing.
Other than that, I got nothing
Click to expand...
Click to collapse
Damn, yeah I can't figure it out; all the ones I've tried were Verizon ones, made sure to wipe everything as usual, tried putting it on the internal SD card and the external, won't work on either one. Very frustrating. But thanks for the help anyway

Ok, I think I figured out the problem (won't be sure until I try it), but I think what happened is I edited my build.prop to the Sprint GS3 to get Google Wallet to work, forgot to change it back, and updated TWRP (which installed the Sprint version, not Verizon), and that's why the flashes are failing. So if any other people are having the same problem, that might be why. Yes I'm an idiot lol. Hopefully this fixes it

Try carbon ROM.
First to work for me.
Sent from my SCH-I535 using xda app-developers app

Devilicus said:
Ok, I think I figured out the problem (won't be sure until I try it), but I think what happened is I edited my build.prop to the Sprint GS3 to get Google Wallet to work, forgot to change it back, and updated TWRP (which installed the Sprint version, not Verizon), and that's why the flashes are failing. So if any other people are having the same problem, that might be why. Yes I'm an idiot lol. Hopefully this fixes it
Click to expand...
Click to collapse
What baseband [modem] do you have installed? ...and some more info if build prop wasn't the issue. Would also be interested if, "but I think what happened is I edited my build.prop", was the issue and you fixed it. Let us know. Goodluck

JohnAreBee said:
What baseband [modem] do you have installed? ...and some more info if build prop wasn't the issue. Would also be interested if, "but I think what happened is I edited my build.prop", was the issue and you fixed it. Let us know. Goodluck
Click to expand...
Click to collapse
Yeah it turns out that was the problem. I edited my build.prop to match the Sprint GS3, so I could download Google Wallet from the Play Store and use it. I just never bothered to change the build.prop back. And when I updated TWRP through GooManager, it assumed I had a Sprint GS3 and installed the wrong recovery. When I flashed the correct Verizon version of TWRP everything worked fine. Thanks for the suggestions everyone

Devilicus said:
Yeah it turns out that was the problem. I edited my build.prop to match the Sprint GS3, so I could download Google Wallet from the Play Store and use it. I just never bothered to change the build.prop back. And when I updated TWRP through GooManager, it assumed I had a Sprint GS3 and installed the wrong recovery. When I flashed the correct Verizon version of TWRP everything worked fine. Thanks for the suggestions everyone
Click to expand...
Click to collapse
Good call. Might be worth mentioning over in the wallet thread. It could save someone the headache you just experienced. Congrats on getting it working.
Sent from my SCH-I535 using Tapatalk 2

Related

BusyBox Update failed

I'm having an odd problem, and I'm not sure what to do about it.
This morning when I woke up, I noticed that there was a BusyBox update in my notification bar. Upon trying to update it failed.
So, I uninstall BusyBox, and try to reinstall it, but I'm met with a message that I don't have root access. Upon checking with Root Checker, I DO have root access. But, now all of a sudden, my wifi is not working, when it has worked flawlessly up to this point.
I'm not sure what to do. I don't have a nandroid backup to roll back to, and I need my wifi to work. Would doing a factory reset and flashing a new ROM solve this problem?
lukas_s said:
I'm having an odd problem, and I'm not sure what to do about it.
This morning when I woke up, I noticed that there was a BusyBox update in my notification bar. Upon trying to update it failed.
So, I uninstall BusyBox, and try to reinstall it, but I'm met with a message that I don't have root access. Upon checking with Root Checker, I DO have root access. But, now all of a sudden, my wifi is not working, when it has worked flawlessly up to this point.
I'm not sure what to do. I don't have a nandroid backup to roll back to, and I need my wifi to work. Would doing a factory reset and flashing a new ROM solve this problem?
Click to expand...
Click to collapse
What ROM are you on...Gingerbread or ICS?
you must be on a custom rom or you on stock, rooted?
---------- Post added at 04:48 PM ---------- Previous post was at 04:40 PM ----------
ok need to go into CWM and flash these files, should correct it, I had this issue on a ROM dont recall which one or it might of been on a rooted stock....
but before you do anything.....
download these files and put them on your sd card of the phone, NOT THE EXT memory card, you are gonna flash them like you would a ROM ok, in cwm, you can flash them back to back while you are in CWM...kk
download this file first and flash this file first: FLASH ME FIRST
download this file second and flash it second: FLASH ME SECOND
bigjoe2675 said:
What ROM are you on...Gingerbread or ICS?
you must be on a custom rom or you on stock, rooted?
Click to expand...
Click to collapse
I'm on Gingerbread, MIUI 2.3.9
lukas_s said:
I'm on Gingerbread, MIUI 2.3.9
Click to expand...
Click to collapse
try what I suggested and let us know if it works...kk
Didn't seem to work. Still can't install BusyBox. I'm not sure what kinda bearing that has on my wifi, my wifi just stopped working when the BusyBox update failed this morning.
lukas_s said:
Didn't seem to work. Still can't install BusyBox. I'm not sure what kinda bearing that has on my wifi, my wifi just stopped working when the BusyBox update failed this morning.
Click to expand...
Click to collapse
check the MIUI thread...
http://forum.xda-developers.com/showthread.php?t=1294549
I think MIUI occasionally loses recovery. Possible kernel issue.
Read through the thread to see if you can get some additional info.
I'm not sure if it has any bearing on your wifi..possible.
If you know how, you can try extracting the kernel from MIUI rom and reflashing just the kernel using SGS kernel flasher to retain your data.
qkster said:
check the MIUI thread...
http://forum.xda-developers.com/showthread.php?t=1294549
I think MIUI occasionally loses recovery. Possible kernel issue.
Read through the thread to see if you can get some additional info.
I'm not sure if it has any bearing on your wifi..possible.
If you know how, you can try extracting the kernel from MIUI rom and reflashing just the kernel using SGS kernel flasher to retain your data.
Click to expand...
Click to collapse
I definitely don't know how to do that haha. I'm a noob when it comes to this whole game, although I'm slowly learning.
Do you think doing a factory reset, wiping everything, and then flashing a new ROM might fix my issue? I did want to try out one of the new ICS ROMs, so if that will fix my problem I might as well go ahead and try one of them out.
Flashing Uniporn seemed to have fixed my issue. I first re-flashed MIUI and that didn't solve anything, so I guess the issue was with MIUI? Just odd that the wifi would drop out after using it flawlessly for 4 months.
Oh well, got something new to play with again. Thanks for the help guys!
lukas_s said:
Flashing Uniporn seemed to have fixed my issue. I first re-flashed MIUI and that didn't solve anything, so I guess the issue was with MIUI? Just odd that the wifi would drop out after using it flawlessly for 4 months.
Oh well, got something new to play with again. Thanks for the help guys!
Click to expand...
Click to collapse
that bld of miui, i was reading was not stable, idk...coming from the other miui users, but each user has a their ver of the story...
but glad it worked out, thx qkster...and don't forget to thx Nun for the rom he worked on...Uniporn

[Q] Dialer FC

Tried different ROMs & kernels, tried wiping everything and re-flashing, tried flashing the latest RUU(including firmware), changed recovery, did everything I can, the dialer still FCs when I try to make a call.
Driving me crazy.
I used different recoveries as well. TWRP & CWM & Stock after RUU flash.
I do remember using CWM recovery though, but it is the official one.
BreatheHT said:
Tried different ROMs & kernels, tried wiping everything and re-flashing, tried flashing the latest RUU(including firmware), changed recovery, did everything I can, the dialer still FCs when I try to make a call.
Driving me crazy.
I used different recoveries as well. TWRP & CWM & Stock after RUU flash.
I do remember using CWM recovery though, but it is the official one.
Click to expand...
Click to collapse
Well, I don't think a kernel could have anything to do with it. I think you need to backup your ROM. Then go into recovery and wipe system. Then flash the stock AT&T rooted ROM with nothing else, then try.
Mister J said:
Well, I don't think a kernel could have anything to do with it. I think you need to backup your ROM. Then go into recovery and wipe system. Then flash the stock AT&T rooted ROM with nothing else, then try.
Click to expand...
Click to collapse
i've tried everything like mentioned in the original post.... EVEN RUU
BUT AOKP roms works fine.
I'm started having the same problem this morning on every single sense ROM that I tried. I finally had to flash CM because I needed to call someone. RUU, wiping everything, different radios and different recoveries, nothing worked.
Sent from my One X using xda app-developers app
tried everything possible -_-
NobodY??????
I'm going to try a few other things when I get a chance, hopefully tomorrow. I would like to get this solved.
Sent from my One X using xda app-developers app
BreatheHT said:
NobodY??????
Click to expand...
Click to collapse
If you ruu and the problem still exists then its hardware related
Sent from my VENOMized HoxL
area51avenger said:
If you ruu and the problem still exists then its hardware related
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
If it's hardware related then why does the dialer work perfectly with CM?
Sent from my One X using xda app-developers app
sweeterman said:
If it's hardware related then why does the dialer work perfectly with CM?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yep it can't be hardware.
Have you checked HTC for a bug update? I know they have had these problems in the past. Might not hurt to check.
Sent from my HTC One X using xda premium
This sounds a heck of a lot like the issue that cropped up with the old hacked (unofficial) version of CWM, way back last summer. It seemed that going from CM to CleanROM using CWM was the root cause (although I don't think the exact cause was ever discovered), and the oddest thing is that flashing different ROMs and even RUU didn't solve the issue. It was pretty much the event that got most of us to swear off the unofficial CWM, until it finally went official this month.
I think (but this is digging deep in my memory banks) some folks were able to resolve the dialer FC issue by going back to a known good CWM nandroid, then I think going to TWRP after that, and flashing a new ROM. But you might use the search function to find the specifics.
Might be something different going on here. But the persistent dialer FC (even after RUU) combined with CWM and CM10 is looking a bit suspicious.
redpoint73 said:
This sounds a heck of a lot like the issue that cropped up with the old hacked (unofficial) version of CWM, way back last summer. It seemed that going from CM to CleanROM using CWM was the root cause (although I don't think the exact cause was ever discovered), and the oddest thing is that flashing different ROMs and even RUU didn't solve the issue. It was pretty much the event that got most of us to swear off the unofficial CWM, until it finally went official this month.
I think (but this is digging deep in my memory banks) some folks were able to resolve the dialer FC issue by going back to a known good CWM nandroid, then I think going to TWRP after that, and flashing a new ROM. But you might use the search function to find the specifics.
Might be something different going on here. But the persistent dialer FC (even after RUU) combined with CWM and CM10 is looking a bit suspicious.
Click to expand...
Click to collapse
Yeah I've read threads and posts having the same problem.... But I've never used unofficial CWM that's the weird thing... And I don't really have a good backup...
redpoint73 said:
This sounds a heck of a lot like the issue that cropped up with the old hacked (unofficial) version of CWM, way back last summer. It seemed that going from CM to CleanROM using CWM was the root cause (although I don't think the exact cause was ever discovered), and the oddest thing is that flashing different ROMs and even RUU didn't solve the issue. It was pretty much the event that got most of us to swear off the unofficial CWM, until it finally went official this month.
I think (but this is digging deep in my memory banks) some folks were able to resolve the dialer FC issue by going back to a known good CWM nandroid, then I think going to TWRP after that, and flashing a new ROM. But you might use the search function to find the specifics.
Might be something different going on here. But the persistent dialer FC (even after RUU) combined with CWM and CM10 is looking a bit suspicious.
Click to expand...
Click to collapse
Should I flash CWM again? Because last time for some reason CWM Touch(official) stopped working for no reason(cannot get into recovery, screen flashes and reboots) so I flashed TWRP again, and I think that's when the problem began to show.
BreatheHT said:
Should I flash CWM again? Because last time for some reason CWM Touch(official) stopped working for no reason(cannot get into recovery, screen flashes and reboots) so I flashed TWRP again, and I think that's when the problem began to show.
Click to expand...
Click to collapse
Maybe try an older version of TWRP, if youre on one of the newer versions. I've heard a LOT of ppl having issues with the 2.4.x.x versions.
Sent from my now S-Off HTC OneXL
BreatheHT said:
Should I flash CWM again?
Click to expand...
Click to collapse
I'd say it worth a try.
---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------
BreatheHT said:
Yeah I've read threads and posts having the same problem.... But I've never used unofficial CWM that's the weird thing...
Click to expand...
Click to collapse
I don't think it was ever properly discussed whether whatever caused this bug in ythe "old" hacked CWM was resolved (or not an issue) with the "official" CWM. Not trying to knock CWM, and those that worked hard on it. Its just been a lingering question in my mind since it went official. But I'm also a skeptic by nature.
I installed the latest CWM and flashed the rooted att 3.18 rom the dialer now works now. I don't know if there is a bug that once you use CWM, you can't use TWRP. It seems very odd though.
sweeterman said:
I installed the latest CWM and flashed the rooted att 3.18 rom the dialer now works now. I don't know if there is a bug that once you use CWM, you can't use TWRP. It seems very odd though.
Click to expand...
Click to collapse
Good to know...I was thinkin bout flashing CWM, but I guess if I haven't had issues with TWRP, "don't fix what ain't broken."
Sent from my now S-Off HTC OneXL
redpoint73 said:
I'd say it worth a try.
---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------
I don't think it was ever properly discussed whether whatever caused this bug in ythe "old" hacked CWM was resolved (or not an issue) with the "official" CWM. Not trying to knock CWM, and those that worked hard on it. Its just been a lingering question in my mind since it went official. But I'm also a skeptic by nature.
Click to expand...
Click to collapse
Thanks bro
sweeterman said:
I installed the latest CWM and flashed the rooted att 3.18 rom the dialer now works now. I don't know if there is a bug that once you use CWM, you can't use TWRP. It seems very odd though.
Click to expand...
Click to collapse
Will try, thanks bro!
elfysrfr said:
Maybe try an older version of TWRP, if youre on one of the newer versions. I've heard a LOT of ppl having issues with the 2.4.x.x versions.
Sent from my now S-Off HTC OneXL
Click to expand...
Click to collapse
I'm using 2.3.x.x haha 2.4.x.x is so bad... Or not compatible...

Recovery buggy date/time

Had anybody seen a situation where the recovery won't keep the correct date and time? I've flashed TWRP 2.7.1.0, 2.8.0.1, and the latest Philz, and all of them kept changing the time, the timezone, and the date... and they were acting a little buggy in their responsiveness.
Thoughts?
WarAxe said:
Had anybody seen a situation where the recovery won't keep the correct date and time? I've flashed TWRP 2.7.1.0, 2.8.0.1, and the latest Philz, and all of them kept changing the time, the timezone, and the date... and they were acting a little buggy in their responsiveness.
Thoughts?
Click to expand...
Click to collapse
I've experienced the same issue since I got my S5. KT TWRP 2.8.1.0 doesn't have that problem. It also fixes the backup to extSD problem, if you were experiencing that.
Ramer84015 said:
I've experienced the same issue since I got my S5. KT TWRP 2.8.1.0 doesn't have that problem. It also fixes the backup to extSD problem, if you were experiencing that.
Click to expand...
Click to collapse
THANKS! I had KT's downloaded but didn't flash it yet... I certainly will now. And yes, the extSD issue bit me, too.
Nope... date is 1/1/2014 and the time is 3 hours lagging for the timezone.
Let's hope at the very least my nandroid backups won't disappear.
WarAxe said:
Nope... date is 1/1/2014 and the time is 3 hours lagging for the timezone.
Let's hope at the very least my nandroid backups won't disappear.
Click to expand...
Click to collapse
Try this: Using something like Root Explorer, look for the TWRP folder on your internal SD card. There's a file called ".twrps". It's the config file for TWRP. Delete it and then boot back into TWRP. You'll have to redo your setting (timezone, screen timeout etc.). See if that fixes it. If that doesn't do it, not sure what else will.
Ramer84015 said:
Try this: Using something like Root Explorer, look for the TWRP folder on your internal SD card. There's a file called ".twrps". It's the config file for TWRP. Delete it and then boot back into TWRP. You'll have to redo your setting (timezone, screen timeout etc.). See if that fixes it. If that doesn't do it, not sure what else will.
Click to expand...
Click to collapse
I had tried peeking into the file with Notepad++ but nothing jumped out at me. Now I feel silly for not trying what you suggested.
I deleted it and it had no effect. The one I deleted and the one it created had the wrong date/time stamps on them... as did the two backups I created (both in metadata and filename convention).
On the bright side... my two backups are as yet undeleted.
WarAxe said:
I had tried peeking into the file with Notepad++ but nothing jumped out at me. Now I feel silly for not trying what you suggested.
I deleted it and it had no effect. The one I deleted and the one it created had the wrong date/time stamps on them... as did the two backups I created (both in metadata and filename convention).
On the bright side... my two backups are as yet undeleted.
Click to expand...
Click to collapse
Very strange, I was sure that was it. My date/time have been correct since using it. The only other thing I may have done was using KT Kernel as well, but I don't think that was it. If you decide to try KT Kernel and want to go back to stock kernel, here's a link for stock: http://forum.xda-developers.com/showpost.php?p=54632862&postcount=1702
Another thought: What version is your firmware? Should be NE5. If not, here's that link: http://forum.xda-developers.com/showthread.php?t=2798079
Ramer84015 said:
Very strange, I was sure that was it. My date/time have been correct since using it. The only other thing I may have done was using KT Kernel as well, but I don't think that was it. If you decide to try KT Kernel and want to go back to stock kernel, here's a link for stock: http://forum.xda-developers.com/showpost.php?p=54632862&postcount=1702
Another thought: What version is your firmware? Should be NE5. If not, here's that link: http://forum.xda-developers.com/showthread.php?t=2798079
Click to expand...
Click to collapse
Thanks for the links.
I didn't flash the KT Kernel because the post said it needed to be flashed onto a TouchWiz based ROM... and right now I have PacMan (AOKP). I had MOAR (NE5) installed for a bit but I'm not used to stock. Truthfully, MOAR had everything I could want... I may just have to get over my snootiness.
Oh, it's coming back to me... with MOAR I was getting a lot of error popups of processes stopping running. i think "acore" was a common one. I could have troubleshot but didn't.
WarAxe said:
Oh, it's coming back to me... with MOAR I was getting a lot of error popups of processes stopping running. i think "acore" was a common one. I could have troubleshot but didn't.
Click to expand...
Click to collapse
Make sure your backup works and come on over I'm a big supporter of MOAR! Do a clean install though and I bet 99.9% of your problems will be solved
Ramer84015 said:
Make sure your backup works and come on over I'm a big supporter of MOAR! Do a clean install though and I bet 99.9% of your problems will be solved
Click to expand...
Click to collapse
There's the main install 2.1, and the new stuff 1.7, and of course Gapps. Do folks typically flash them all together... Or separately sequentially?
My clean install is usually wiping cache, dalvik, data, and system.
WarAxe said:
There's the main install 2.1, and the new stuff 1.7, and of course Gapps. Do folks typically flash them all together... Or separately sequentially?
My clean install is usually wiping cache, dalvik, data, and system.
Click to expand...
Click to collapse
MOAR is TW, so gapps is included. My FAQ and guide for MOAR may help you get a feel for it.
Ramer84015 said:
MOAR is TW, so gapps is included. My FAQ and guide for MOAR may help you get a feel for it.
Click to expand...
Click to collapse
Okay... MOAR's on there now. I'll read up and tweak to the extent I'm able and see if I have any questions.
WarAxe said:
Okay... MOAR's on there now. I'll read up and tweak to the extent I'm able and see if I have any questions.
Click to expand...
Click to collapse
Feel free to post any questions on the Q&A thread. :good:

Tried installing Xposed, now phone won't boot.

EDIT: Mounted system as R/W and i'm now restoring my stock unrooted backup of the system. But My "System Image" backup gives me ERROR=2?
So I had the xposed disabler zip on my SD, I had a system image backup from before I rooted, a full normal backup as well.
It wouldn't boot after I flashed the Xposed Zip from here: http://forum.xda-developers.com/showthread.php?t=3034811
I flashed the one for SDK21-arm64.
I was like okay, and flashed the disabler, it said no backup of something made so no way to restore.
I sighed and tried restoring the system image, error, I tried restoring the full normal backup, mounted read only can't restore?
What should I do?
I have TWRP installed so I can boot into bootloader and recovery, not sure how to fix this.
Found out how to mount the system as read/write. Trying to restore again.
"Process ended with ERROR=2"
Mounted system as R/W and i'm now restoring my stock unrooted backup of the system. But My "System Image" backup gives me ERROR=2?
Yep. It doesn't work. Basically I just booted twrp, installed the uninstall zip and wiped cache to fix.
I think there's a version 22 that also didn't work. It gave an error trying to install. Here's the thread if you want to try it.
http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
Xposed Framework for Alcatel Idol 3
Was there any error when installing xposed? Did anyone do an adb logcat on bootup to a text file to catch the error? Did anyone report the issue to the Xposed for Lollipop thread? (not sure why you'd be looking in the xposed for 5.1 thread since we are still on 5.0.2 but I found no sign of the words "alcatel" or "idol" in either thread. They can't fix it if they don't know about it.
oh man i wouldnt risk installing it hope theres a build compatible for us
gecko702 said:
oh man i wouldnt risk installing it hope theres a build compatible for us
Click to expand...
Click to collapse
Oh I don't plan on installing it till it's known to work but for folks who already did they should report as much as possible to the xposed thread so it can be corrected although we now have system images to revert to if necessary. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
neilownz said:
Yep. It doesn't work. Basically I just booted twrp, installed the uninstall zip and wiped cache to fix.
I think there's a version 22 that also didn't work. It gave an error trying to install. Here's the thread if you want to try it.
http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
Click to expand...
Click to collapse
don't even try this one it's 5.1 ONLY!!!!
i'll test v68 from romracer as soon as the ****in post office will bring me my phone
famewolf said:
Oh I don't plan on installing it till it's known to work but for folks who already did they should report as much as possible to the xposed thread so it can be corrected although we now have system images to revert to if necessary. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
Click to expand...
Click to collapse
well i went to the xposed unofficial build thread and it says its for 5.1 though still im not going to risk it lol im a very cautious person ><
gecko702 said:
well i went to the xposed unofficial build thread and it says its for 5.1 though still im not going to risk it lol im a very cautious person ><
Click to expand...
Click to collapse
As mentioned multiple times by me and others...no one should be going to the unoffical xposed for android 5.1 thread...if it was gonna work it would be the offical "android for lollipop thread (5.0)". Of course if no one reports the errors then it will never get fixed. Oh well...will re-evaluate it in a few months.
Hopefully this will work soon, I miss Xposed. There was a guy that posted a logcat from his Idol in the Xposed 5.0 thread, but I don't seen any responses to him.
KryPTiCk0d3 said:
Hopefully this will work soon, I miss Xposed. There was a guy that posted a logcat from his Idol in the Xposed 5.0 thread, but I don't seen any responses to him.
Click to expand...
Click to collapse
i miss it too i had once on my htc one sv it was great plus the adblocker for youtube was phenomenal
edit: well heres something for 5.0 maybe should work? http://forum.xda-developers.com/showthread.php?p=62065892#post62065892
gecko702 said:
i miss it too i had once on my htc one sv it was great plus the adblocker for youtube was phenomenal
edit: well heres something for 5.0 maybe should work? http://forum.xda-developers.com/showthread.php?p=62065892#post62065892
Click to expand...
Click to collapse
The OP had a different error, so I'm not sure if that newer version would help... I would try it out, but I have too many things to do this weekend other than fix my phone :laugh::laugh:
Ill give it a shot ill post results later im busy now going to have my coffee now
Edit: i flashed the xposed arm64 version rebooted and i got stuck in the white alcatel logo that says smart move i left it alone for a few minutes and nothing so i flashed the uninstaller and went back to normal not sure if i need to wipe the dalvik after i install the xposed hmmm might retry again
So I flashed xposed-v69-sdk21-arm64.zip, wiped Dalvik & Cache, and it still hung at boot, I did get an adb logcat on boot for it, and I have attached that in the Xposed thread. Hopefully it will help us get this resolved. I was able to revert back with the uninstaller.
KryPTiCk0d3 said:
So I flashed xposed-v69-sdk21-arm64.zip, wiped Dalvik & Cache, and it still hung at boot, I did get an adb logcat on boot for it, and I have attached that in the Xposed thread. Hopefully it will help us get this resolved. I was able to revert back with the uninstaller.
Click to expand...
Click to collapse
oh yeah i havent thought about making a logcat...have you gotten any responses?
gecko702 said:
oh yeah i havent thought about making a logcat...have you gotten any responses?
Click to expand...
Click to collapse
No, I haven't.
had just one answer after posting logcat, they said it was something with odexed rom
tested r70 and still no luck
keyra74 said:
had just one answer after posting logcat, they said it was something with odexed rom
tested r70 and still no luck
Click to expand...
Click to collapse
so we basically need to have a deodexed rom huh?

Ringtones,notification,music and some gallery albums are missing

Hey guys, I'm having a problem here.two days ago I had a problem with my play store which would not open, so I thought of flashing my ROM and gapps again in hopes of getting the problem solved. I wiped my cache partitions along with my system partition and flashed it, everything went well, play store started working again but this time I got a couple of different problems. My ringtones and notification tones are missing, when I click on the options for changing them there's just one option (none). My music player can't read any music files, even though I have many of them. And gallery has some albums missing. I was on cm12.1 and I flashed to liquid smooth v4.1 in hopes of fixing the problem. But the problem still persists, what should I do to fix it. Please help me on this one.
mohdfahad47 said:
Hey guys, I'm having a problem here.two days ago I had a problem with my play store which would not open, so I thought of flashing my ROM and gapps again in hopes of getting the problem solved. I wiped my cache partitions along with my system partition and flashed it, everything went well, play store started working again but this time I got a couple of different problems. My ringtones and notification tones are missing, when I click on the options for changing them there's just one option (none). My music player can't read any music files, even though I have many of them. And gallery has some albums missing. I was on cm12.1 and I flashed to liquid smooth v4.1 in hopes of fixing the problem. But the problem still persists, what should I do to fix it. Please help me on this one.
Click to expand...
Click to collapse
What version of the phone do you have? Also which gapps did you flash?
TrypelZ said:
What version of the phone do you have? Also which gapps did you flash?
Click to expand...
Click to collapse
Well Im using note 3 sm n9005 the international version. And the gapps I downloaded it from highonandroid.com, max lee's site. I'll attach the screen shots.
mohdfahad47 said:
Well Im using note 3 sm n9005 the international version. And the gapps I downloaded it from highonandroid.com, max lee's site. I'll attach the screen shots.
Click to expand...
Click to collapse
Try this gapps : https://www.androidfilehost.com/?fid=24052804347785468
Also try to clean flash your rom again and flash gapps right aftet installing. Im using the same gapps package.
TrypelZ said:
Try this gapps : https://www.androidfilehost.com/?fid=24052804347785468
Also try to clean flash your rom again and flash gapps right aftet installing. Im using the same gapps package.
Click to expand...
Click to collapse
Thanks bud, ill give it a go. So this problems are caused because of the gapps package?
mohdfahad47 said:
Thanks bud, ill give it a go. So this problems are caused because of the gapps package?
Click to expand...
Click to collapse
The playstore problem for sure.
Maybe you can consider updating your bootloader and modem to the latest version if that does not help.
TrypelZ said:
The playstore problem for sure.
Maybe you can consider updating your bootloader and modem to the latest version if that does not help.
Click to expand...
Click to collapse
Well i flashed it all again with the gapps package you told me. The problem still persists. Upgrading the bootloader and modem...how do i do that ? Im new in all this rooting and flashing.and yeah i read some forums on this issue and i read that restoring an old nandroid backup might solve the problem. What do you say, should i try doing that?? And yeah one more thing, do you think that some how a rom can slow up the cellular data speed?? Cuz i think after installing liquidsmooth my data is kinda slow even on lte.
mohdfahad47 said:
Well i flashed it all again with the gapps package you told me. The problem still persists. Upgrading the bootloader and modem...how do i do that ? Im new in all this rooting and flashing.and yeah i read some forums on this issue and i read that restoring an old nandroid backup might solve the problem. What do you say, should i try doing that?? And yeah one more thing, do you think that some how a rom can slow up the cellular data speed?? Cuz i think after installing liquidsmooth my data is kinda slow even on lte.
Click to expand...
Click to collapse
Hmm i don't know that for sure,i only knoe that on some rom's my wifi works better or worse
About your problem : i never had this kind of problems,i had a google play problem once,but after reinstalling gapps it was gone,although im on the latest bootloader and modem : https://www.androidfilehost.com/?fid=24052804347759102
I can't find my guide for flashing it so i can explain a bit :
-Download odin 3.09 on your computer
-unzip modem.zip
-shut down your phone and pull the battery out
- in odin untick auto reboot
- put the battery back in and go straight to download mode ( home,power and vol up i think,if not that vol down ^^ )
- in odin put the modem file in the 'cp' slot or what so called ( it should be cp but better look it up )
-Start flashing and wait untill it's finished ( green button lights up )
-Then reboot your phone and under phone info it should be allright.
TrypelZ said:
Hmm i don't know that for sure,i only knoe that on some rom's my wifi works better or worse
About your problem : i never had this kind of problems,i had a google play problem once,but after reinstalling gapps it was gone,although im on the latest bootloader and modem : https://www.androidfilehost.com/?fid=24052804347759102
I can't find my guide for flashing it so i can explain a bit :
-Download odin 3.09 on your computer
-unzip modem.zip
-shut down your phone and pull the battery out
- in odin untick auto reboot
- put the battery back in and go straight to download mode ( home,power and vol up i think,if not that vol down ^^ )
- in odin put the modem file in the 'cp' slot or what so called ( it should be cp but better look it up )
-Start flashing and wait untill it's finished ( green button lights up )
-Then reboot your phone and under phone info it should be allright.
Click to expand...
Click to collapse
Thanks buddy, ill give it a go. By the way i didn't flash the arter 97 kernel. Ill try flashing that too. Quick question...if i flash the kernel i should flash the latest version right??
mohdfahad47 said:
Thanks buddy, ill give it a go. By the way i didn't flash the arter 97 kernel. Ill try flashing that too. Quick question...if i flash the kernel i should flash the latest version right??
Click to expand...
Click to collapse
Yeah of course. But only flash the AOSP version
TrypelZ said:
Yeah of course. But only flash the AOSP version
Click to expand...
Click to collapse
Hmmm, the version on lord ekos note 3 liquidsmooth thread is aosp right?
mohdfahad47 said:
Hmmm, the version on lord ekos note 3 liquidsmooth thread is aosp right?
Click to expand...
Click to collapse
Yes it is. Resurrection Remix,Blisspop,CM12 by temasek,euphoria os,AICP and liqiudsmooth are all aosp,in the threads of the rom there usually is an indicator of that the rom is like. Touchwiz roms for examble are often more than 1gb files where aosp are only 200-300mb. But the battery on touchwiz for me often is a ton better.
TrypelZ said:
Yes it is. Resurrection Remix,Blisspop,CM12 by temasek,euphoria os,AICP and liqiudsmooth are all aosp,in the threads of the rom there usually is an indicator of that the rom is like. Touchwiz roms for examble are often more than 1gb files where aosp are only 200-300mb. But the battery on touchwiz for me often is a ton better.
Click to expand...
Click to collapse
Ok...well i figured out that the cellular speed issue isdue to the Carrier server problems.so flashing the modem is not necessary i guess? My current baseband version is N9005XXUGNG1. And just out of curiosity, say i flashed the arter kernel and later on for some reason i want to change the rom like i go to cm12.1. The kernel version will change automatically right?
mohdfahad47 said:
Ok...well i figured out that the cellular speed issue isdue to the Carrier server problems.so flashing the modem is not necessary i guess? My current baseband version is N9005XXUGNG1. And just out of curiosity, say i flashed the arter kernel and later on for some reason i want to change the rom like i go to cm12.1. The kernel version will change automatically right?
Click to expand...
Click to collapse
Yes it will. Apparently you have a kitkat modem and bootloader but that SHOULDN'T cause problems,although it can. I can't tell i am flashing newest bootloader and modem every time one comes out.
TrypelZ said:
Yes it will. Apparently you have a kitkat modem and bootloader but that SHOULDN'T cause problems,although it can. I can't tell i am flashing newest bootloader and modem every time one comes out.
Click to expand...
Click to collapse
Hmmm...cool. Can i flash the modem through my phone or it can be done only by odin?
mohdfahad47 said:
Hmmm...cool. Can i flash the modem through my phone or it can be done only by odin?
Click to expand...
Click to collapse
I don't know exactly cause i only flash through Odin on my PC. But it's the easiest way i know.
TrypelZ said:
I don't know exactly cause i only flash through Odin on my PC. But it's the easiest way i know.
Click to expand...
Click to collapse
Hmmm...ok, flashing the modem wipes the data and stuff? Anyways bud thanks for keeping up with me, really appreciate it.
mohdfahad47 said:
Hmmm...ok, flashing the modem wipes the data and stuff? Anyways bud thanks for keeping up with me, really appreciate it.
Click to expand...
Click to collapse
Nah it just updates your radio device. Nothing won't wipe at all. And no problem man,it's a tech forum,you can expect at least a little help
TrypelZ said:
Nah it just updates your radio device. Nothing won't wipe at all. And no problem man,it's a tech forum,you can expect at least a little help
Click to expand...
Click to collapse
Cool. And thanks again.
mohdfahad47 said:
Cool. And thanks again.
Click to expand...
Click to collapse
No problem

Categories

Resources