Related
Hi all, I don't think most Vibrant users worry about it (at least from what I've seen), but do you worry about losing your baseband/EFS partition/IMEI info when flashing?
For those of you who don't know or forgot, basically some flashes can result in a generic IMEI number and you SIM card would no longer be readable under any custom ROM. You would then have to ODIN to stock and stay there forever, as that is the only way your SIM would be readable.
I know this was a problem a while ago when CM7 or MIUI was flashed, but is it even worth worrying about anymore?
Hopefully someone can inform me and others about the issue. Thank you for your time!
I'm not cause I got my efs backed up. Plus AOSP ROMS are no longer tedious to flash..just flash like any other rom. Though odining back to stock is the only way to leave AOSP I don't really care.
Sent from my T959 using XDA App
Hey laylovj,
So we only have to ODIN to stock if we're going from an AOSP rom to some non-AOSP ROM? (How common are these?)
Also, I remember hearing that if we want to go from Gingerbread (specifically CM7) back to Froyo we'd have to ODIN. Not true?
Sent from my SGH-T959
awebster said:
Hey laylovj,
So we only have to ODIN to stock if we're going from an AOSP rom to some non-AOSP ROM? (How common are these?)
Also, I remember hearing that if we want to go from Gingerbread (specifically CM7) back to Froyo we'd have to ODIN. Not true?
Sent from my SGH-T959
Click to expand...
Click to collapse
Yea...there are three for us VIbrant Owners...
You need to Odin back to stock w/ repartition checked if you want to go back to Sammy based roms coming MIUI and any other CM7 based ROMs.
That's great to know, thanks so much for the info laylovj.
Anyone else?
I think i backed up my efs at some point but i dont worry about it too much... at one point, flashing kernels in gb, i lost.my baseband i had 'no imei' according to my phone... i odined to stock and now im back on cm7 texting 24/7 so idk
... itd prob be aa good idea to have a backup
Sent from a cell tower to the XDA server to you.
Why worry now? I could understand worrying when we were toying with fire--i.e. early voodoo, etc. But almost all roms now are easily flashed and provided you follow instructions to the tee, you will have no problems.
TheSneakerWhore said:
Why worry now? I could understand worrying when we were toying with fire--i.e. early voodoo, etc. But almost all roms now are easily flashed and provided you follow instructions to the tee, you will have no problems.
Click to expand...
Click to collapse
I couldn't stand it if I lost my IMEI and was stuck on a stock, Touchwiz ROM. That's the only reason I worry.
younix258, I do have a backup of my EFS folder, but I guess ODINing to stock will also fix the problem like it did for you. Good to know.
Sent from my SGH-T959
I lost my IMEI a long time ago while flashing an unlocker or maybe CM7. I have this generic IMEI that has been working every since though with all the ROMs. Even Tmobile can't identified what phone I am using but they haven't shut down my service probably because I am paying $200 a month on 3 lines,.
Hmm, I wonder how often that's the case though.
From http://forum.xda-developers.com/showthread.php?t=859914,
"In case you screwed your IMEI by playing with the nv_data.bin and you are experiencing issues like:
Fake IMEI (usually 004999010640000)
Unable to download apps from the market
Unable to unlock your SIM card using your PIN
Weird apps are downloading automatically from the market
Blinking SIM card icon on the top tray… ETC"
So I'd definitely like to avoid losing my IMEI, even if everything seems to be fine without it.
I've reloaded rom manager onto my Fascinate. I was going to download one of JT's kernels but it doesn't show anything for the fascinate. It shows roms for the S I9000. How do I change the device it will list for? I've tried reloading it and it does that every time.
I take it your on a eh09 rom... if so you need to manually install jt's kernal via cwm. Honestly I would run far far away from rom manager jmo.
I'm on Pool party but it's been like that for a while I just haven't worried about it. I know I've been on MIUI and then to EH09 PW (yeah I'm a flasher). I don't really remember when I noticed it but I can't fix it.
If you're on pool party that means you're running a kernel with jt's latest commits within your current kernel. In others words don't flash a jt kernel it might end up being older than what you're running now
good day.
But how do I fix it? I've reflashed back to Resurrection 1.1 so I've done a complete wipe. I've reinstalled ROM Manager and it's still giving options for only GalaxyS i9000.
Rom manager on touch wiz and pool party will serve you no purpose. When you first open RM you should have been doing "confirm phone model" as Samsung Fascinate (MTD). And agree to having installed cwm 3.????? or what ever it says. But once again the latest jt kernel on RM is v6 and he is arbitrarily up to v11 almost. RM comes in handy for someone running CM7 and gets the nightlies. I use it personally as my own polish theme engine on pool party. Install rom from sd option and choose one of my own badass themes and I let it do its thing.
good day.
Chopper, that's my point. When I first load RM it asks to confirm phone model and has 2 options. Both options are GalaxyS i9000 (one being MTD), no Fascinate. I would just like to have it working in case I went back to CM7.
Toddw said:
Chopper, that's my point. When I first load RM it asks to confirm phone model and has 2 options. Both options are GalaxyS i9000 (one being MTD), no Fascinate. I would just like to have it working in case I went back to CM7.
Click to expand...
Click to collapse
I told you why...any eh09/ei20 rom is not verizon, so when you are on one of those roms it will come up as i9000. You need to odin back to a verizon rom for rom manager to show your device as a fascinate. Again I would stay away from rom manager anyways. It just causes more confusion that its worth. Yes it works ok for changing nightlies on cm7, but your better off manually flashing in cwm.
any eh09/ei20 rom is not verizon, so when you are on one of those roms it will come up as i9000
Thanks, I didn't understand that part. I'll leave it alone then. Thanks
Toddw said:
any eh09/ei20 rom is not verizon, so when you are on one of those roms it will come up as i9000
Thanks, I didn't understand that part. I'll leave it alone then. Thanks
Click to expand...
Click to collapse
no problem!
To allow Q&A to be separated from bugs/development - this is the Q&A thread for the I9100 Hellraiser found at http://forum.xda-developers.com/showthread.php?t=1335377
I intend to put FAQs here, along with keeping a list of tested ROMs. Keep general discussion here, and only use the other thread for bug reports and development.
In general: If it's listed as a known issue, and you don't have a fix, keep it out of the development thread. If you're not sure if it's Hellraiser-specific and common to multiple ROMs, keep it out of the development thread. In short, if you ask "Is this a bug?" in that thread, I will report it to the moderators. If you report a bug that is ROM-specific and not a Hellraiser issue, I will report those to the moderators starting tomorrow.
Tested ROMs:
I9100 XXKI3 Based:
SensatioN 1.8 by Crysis21 - Tested by myself with Alpha 0.2.1 - Fully working except 0.2.1 Known Issues, defaults to "good" AT&T APNs except for it has the "Broadband" APN which may cause the Tether Police to nail you if you tether. I suggest deleting that one.
VillainROM 3.0 + JKay Deluxe Themes v12 - Tested by myself with all versions, and my current "testbed"
I9100 XXKI4 Based:
CheckROM Revolution HD 2.0.0 - A few user reports indicate this may have WiFi issues when Hellraised similar to UCKJ2/J4 for I777
I9100 XWKJ2 Based:
CriskeloROM V30 + JKay Deluxe V12.1 - Reported by simpl3lang, seems to be working
If you have a report for a ROM, please indicate which I9100 firmware it is based on (XXKI3, XXKI4, etc.)
Also, I have seen reports that XWKK5 bases (like the latest CheckROM as of 1/8/2012) have the same issues with Bluetooth HID not working as UCKK6 - even when not Hellraised.
If someone posts a good, in-depth review of a ROM, I may link to it from this list. (Time permitting...)
Frequently Asked Questions:
Q: The home button lag is back, why?
A: The ROM has the annoying Vlingo double-tap support. Either smali it out (look for tips in the UnNamed ROM git repos, or look for a fix for that ROM.) - A commonly available fix may be flashing a JKay Deluxe Theme appropriate for the base of your ROM
Q: Home button haptic feedback is not working, why?
This is something that can't be "universally fixed" with Hellraiser. It must be modified in an individual manner for every ROM in android.policy.jar with some smali magic. It was the same deal with I9000 ROM ports to the Captivate.
Q: Where do I find themes/mods?
Look through the I9100 Themes/Apps forum for mods/themes appropriate to your ROM. Nothing I do in the Hellraising process should break any of these compatibility-wise.
i finally jumped on board and installed an i9100 rom. so far so good. im loving it. first install went smooth. root working and all. i dont know about battery life (my phone still plugged in while testing this out).
okay here is the rom ive installed "CriskeloRom V30-S-BAR-12/7-Tog-BLN-CallREC-Overscroll-7Locks-PWR-M-Esxt-(XWKJ2-2.3.5)"
http://forum.xda-developers.com/showthread.php?t=1168836
i have also installed JKAY DELUXE SETTINGS v12.1 <--great addon. lets you have multiple slide to unlock (AOSP lockscreen). option to remove home double tap. option to customize power options (extended). crt off/on animation. overscroll glow. all these options and more on this DELUXE SETTINGS app. http://forum.xda-developers.com/showthread.php?t=1154278
so far im loving it. this will be my rom for now. thanks ENTROPY for the great HELLRAISER.. you the man
edit: alright i have tried wifi tether. its not working. i know its mentioned in the known issues. the workaround doesnt seem to work for me at least ......i enabled changed ssid and password. but once i exit settings, it reverts back to borkness lol. any other workaround? thanks
Edit 2: nevermind i figured it out. I rmmbered i replaced the Settings.apk with one that has a theme i like. That borked wifi tether for me. I returned the settings apk i replaced, rebooted, and all is good
I just wanted to bump this to the top... this thread needs to be stickied! How do I ask a mod to sticky it?
Sent from my GT-I9100 using xda premium
Good question - I know in the Infuse section some ROM Q&As were stickied, but they don't do that in other forums.
Plus at least this is CLEARLY linked to from the main Hellraiser thread.
Hellraiser doesn't seem to work with the new 1.9 sensation update, unless I'm doing something wrong. A popup saying the process com.android.phone has stopped unexpectedly comes up repeatedly as the app restarts. Seems like a modem error, the sim card isn't read properly either. I'm about to try hacking the updater script to remove the kernal and modem changes, is there anything I would need to do other than delete those lines and repack it?
I did reinstall hellraiser after the update.
selfassembled said:
Hellraiser doesn't seem to work with the new 1.9 sensation update, unless I'm doing something wrong. A popup saying the process com.android.phone has stopped unexpectedly comes up repeatedly as the app restarts. Seems like a modem error, the sim card isn't read properly either. I'm about to try hacking the updater script to remove the kernal and modem changes, is there anything I would need to do other than delete those lines and repack it?
I did reinstall hellraiser after the update.
Click to expand...
Click to collapse
You must be doing something wrong... I am running 1.9 and have been since the test build.. I will post some screen shots in a moment
Sent from my GT-I9100 using xda premium
Here are some screen shots... check out my battery life ..
I did have it hooked to a computer while 1.9 downloaded and that's why you see that slight bump...
Sent from my GT-I9100 using xda premium
How did you install specifically?
I can't get it running. I've tried updating 1.8 and doing a fresh install and flashing hell raiser afterwards but the com.android.phone app crashes and signal is lost upon reboot. It actually works until I reboot.
selfassembled said:
How did you install specifically?
I can't get it running. I've tried updating 1.8 and doing a fresh install and flashing hell raiser afterwards but the com.android.phone app crashes and signal is lost upon reboot. It actually works until I reboot.
Click to expand...
Click to collapse
I had 1.8 flashed 1.9 on top without wipe.
Mounted system and data and then flashed hellraiser on top. And haven't had any issues.
Sent from my GT-I9100 using xda premium
An i9100 modem/kernel will NOT work, that's for sure.
In fact some of the behaviors you mention sound kind of like a classic example of accidentally running an I9100 modem. The rest sound like a classic example of not wiping or doing an improper TiBu restore.
I'll try to test tonight.
It may have been titanium backup, I also didn't remount before hell raising. I'll get it working if he did
Hi Entropy, do you have any idea why the tethering settings are not persistant?
I remounted before flashing and still had the problem. When restoring backup I used advanced restore and found that the culprit is in system, not boot. I don't have the time for a full wipe today.
If it works for entropy I'll just do another full wipe and not restore anything. Thanks for your time on this.
amtrakcn said:
Hi Entropy, do you have any idea why the tethering settings are not persistant?
Click to expand...
Click to collapse
Not yet, haven't had time to mess with it yet.
selfassembled said:
I remounted before flashing and still had the problem. When restoring backup I used advanced restore and found that the culprit is in system, not boot. I don't have the time for a full wipe today.
If it works for entropy I'll just do another full wipe and not restore anything. Thanks for your time on this.
Click to expand...
Click to collapse
Titanium backup always give me problems so I just don't use it anymore...
Have you tried a fresh install without titanium backup?
Sent from my SGH-I777 using xda premium
CheckROM RevolutionHD v3.1.1
I tried raisin' hell with CheckROM RevolutionHD 3.1.1 last night. This is an XWJK3 based ROM, and seemed to work fine. I was intrigued with the idea of having a kitchen in the ROM to customize it and wanted to check it out. Everything seemed to run and work ok. Home button lag and lack of haptic feedback were known and expected. There were a couple of things though -
1) The phone ran really hot. Like skin singeing hot. There was another post on the CheckROM thread that talked about the phone running hot. But I noticed the same problem with a hellraised VillainROM as well. So not sure if that is a hellraiser issue or a ROM specific issue. I do know about the media scanner crashing due to incompatible codecs between Samsung derived ROMs and CM7/MIUI, I didn't get a chance to see if getting rid of my media would fix it because of issue 2...
2) The kitchen app while great in theory, isn't quite there in practice yet it seems like. I tried installing a few mods from the kitchen, but a lot of times downloads failed. I tried installing the BlueMonkey theme from the kitchen and it caused the phone to bootloop. There are quite a few people talking about bootloops on the ROM page, so I am leaning towards this being a ROM or kernel incompatibility issue. I have never had bootloops or anything nearly as funky with any of the native I777 ROMs. I had to flash back to bone stock to recover. Thank god for Nandroids
So, I guess it is ok to the add XWJK3 based ROMs to the compatible list if Entropy thinks both of the above two issues are not hellraiser related.
I've never had heat problems on VillainROM hellraised.
I've been starting to hear that CheckROM 3.1.1 has a lot of issues with the kitchen app - as in 3.1.1 has issues in general. I've seen lots of comments about people sticking with 2.0.0 until it matures.
I only tried CheckROM VERY briefly - enough to confirm that wifi worked (as there was a negative report on wifi with CR 2.0.0)
I'll update the list later this week.
GingerMod
Thank you for this awesome tool, Entropy! You can add GingerMod (http://forum.xda-developers.com/showthread.php?t=1220283) to your list of XXKI3 ROMs that work well Hellraised.
I've quickly tested out everything I can think of from a fresh install (wipe everything, format/system) and no problems to report. Wifi tethering has the minor problem of reverting to default settings, but they work, so it's not an issue in the slightest for me. Default APN settings are the same as on UnNamed--ATT Phone and ATT WAP. Home button haptic works out of the box--I didn't do anything.
For those interested, some quick hits about this great ROM:
- Most Samsungyness removed, really convincing AOSP feel. It's not just a theme, it's rebuilt. Just a few niceties such as Camera, Browser, FM Radio remain. You can add back whatever Samsung features you want.
- Small, 1/2 size compared to stock ROMs
- There is no lengthy screen on delay during calls when removing phone from your face (present in UnNamed)
- Customizable via included "Extras" settings and JKay app
- Been stable for awhile. Over at the thread, you won't notice a lot of random issues or people clamoring for "fixes". It's just really complete.
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Heatshiver said:
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Click to expand...
Click to collapse
Thank you, Heatshiver!
I always do a full wipe unless I'm doing a dirty flash for a ROM update. I will try reverting back to TWRP 2.5.0.2 (Whichever version that happens to be, I think it's .0.2) tonight and report my results. Also, just to clarify, I always make sure I have the most updated SuperSU/Superuser (Usually the former) and BusyBox.
I appreciate the suggestion.
-Travis
teemunknee said:
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
Click to expand...
Click to collapse
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
As much as I love AOSP, I would have to agree with the poster above. I know TW is a pain but there are some pretty good ROMs in that flavor that you shouldn't have any problems with. I've had the no call issue on AOSP, and even though they are nice and free up quite a bit of room it's not worth missing calls over or constantly flashing. Maybe once our bootloader is unlocked things will become different but I'd stick with TW until that happens. I can confirm that TWRP 2.6 is very buggy...you'll have to download the 2.5 version and flash it instead of goomanager they install they latest version everytime I believe.
andybones said:
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
Click to expand...
Click to collapse
Next time, I'll just say "Soft-bricked". Thank you for your reply.
-Travis
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
slim6596 said:
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
Click to expand...
Click to collapse
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
I also forgot to mention that I haven't been able to connect to 4G radios since before I started having issues with AOSP ROMs. Currently I'm on Eclipse's TW (With AOSP Styling) ROM. Everything appears to be working fine, other than 4G.
I've tried the SIM pull and reset, and nothing. I've tried manually setting it to LTE only, at least when I was able to do so when AOSP ROMs would boot for me, and nothing. I have a Galaxy Nexus that I booted up with this SIM in and I get 4G signal. Any Ideas?
Also, when I was on the stock image (MDK) I didn't have 4G either.
Has anyone else run across this issue? (MODS: Let a me know if I should create another thread, or search more intensively. I haven't seen a thread with this exact same situation. Plenty of 4G issue threads, but none with the same issues I've previously had, and I think it may have something to do with my past modding.)
-Travis
teemunknee said:
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
Click to expand...
Click to collapse
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks! I installed CWM 6.0.3.6 Touch and flashed Eclipse's TW/AOSP ROM and everything works well, but it's still no AOSP ROM.
-Travis
Hi all,
I'd like to thank everyone for the suggestions.
An update: Currently I'm on Eclipse's TW v2.0 ROM (TW, with AOSP Styling) and everything works properly. My current recovery is CWM 6.0.3.6 Touch, and I'm not experiencing any booting or calling issues. 4G is the only thing I don't have working.
I'm hoping that someone with my same problem can give me another idea so I can get an AOSP ROM working, preferably with 4G. I'm sure some, if not most, understand my dislike of TouchWiz and strong preference towards stock Android/stock Android based ROMs. Slim6596 said that he uses Philz Modded CWM Recovery and has no issues anymore. Could that really be my solution?
Again, thank you all for your help and ideas. I love XDA for this reason.
-Travis
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
teemunknee said:
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
Click to expand...
Click to collapse
Loki patched, I believe.
Sent from my SCH-I545
slim6596 said:
Loki patched, I believe.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I have stuck to TW ROMs. Pretty soon I'm probably not going to be flashing anything. Switching to Motorola and giving Vz my MDK S4 back. (Reception and dropped call issues.)
Sent from my SCH-I545 using Tapatalk 2
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
egore93 said:
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
teemunknee said:
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
Click to expand...
Click to collapse
Yes that's it give it a go.
Sent from my SCH-I545 using Tapatalk 4
Edit: They do keep coming!
I looked into doing it, and there is no way in hell that I should be a) doing it, and b) unleashing it onto the world. It would be bad.
I only have the one phone to test it on and can't risk messing it up and I don't have the experience to work on it if it didn't come out perfectly.
I expect that it will be the last Sprint ROM released for this phone, We're nearing the end of support, so it would be good to have these final versions "fixed" and available
...on the off chance a few developers will jump right in and cook up a few mega ROMs for us.
DQG1 Root and Xposed (rewritten)
On a related note, I installed stock DQA1 DQG1, using the usual CF Autoroot, battery pull thingy process Odin for the ROM and TWRP, then booting once, booting into recovery, and then installing SuperSU and it rooted fine. No loss of settings or anything else as far as I can tell.
I did have to install the latest versions of the Xposed files. After rooting and custom recovery (TWRP works fine), install XposedInstaller_3.1.4.apk first like any other apk, then go to recovery and install Wanam v87.1-alt-sdk23-arm-custom-build, but everything (Xprivacy, etc.) worked fine. Keep in mind, you HAVE to use the "alt" (see the "alt" in the file name above?) version or else it won't work. Samsung made some changes, blah, blah, blah. Much thanks to Wanam!
New side note: I did do a factory wipe, and even after reinstalling everything, and using a ROM that contains bloatware, I still have like 40% more space on the phone. I truly don't know what happened there.
Anyone have any thoughts as to kernel? I downloaded Emotion r26 RC1, and BeastModeKernel 1.0BETA, but I haven't tried them yet.
EDIT: Emotion r26 RC1 works fine, but it doesn't seem like CPU freqs are ever going to stick.
No surprise that neither Emotion nor BeastModeKernel worked; I haven't seen anything else that may.
Thoughts anyone?
Both kernels are good, emotion has a few more options to tweak but I took an update a month or two ago and run NotEdge ROM fine , I just use SO launcher with it because I like TW, also latest xposed is 86.1 and I wish I could do what your asking but it probably would be just as bad you'll be fine with that ROM I just suggested it has everything u just requested just make a nandroid and do it at home in case you do something wrong you can always ODIN back your firmware
Sent from my HTC One M9 using XDA-Developers mobile app
D'oh!!
Eating a little crow here. So far, there have been two three 742 updates, maybe there will be more. Who knows?
But I edited the title of the first post. Again. Again. 741 times.
Do you guys have a link to the stock unrooted rom? My phone is royally screwed right now and still stock. I want to do a clean flash and see if that fixes it.
Over a year later, and the still keep coming.
Hmmmm.
I did take another gander around, but it seems that I would need Linux to do it correctly, so I am still opting out of doing it myself.
mictek said:
Do you guys have a link to the stock unrooted rom? My phone is royally screwed right now and still stock. I want to do a clean flash and see if that fixes it.
Click to expand...
Click to collapse
They all arrive here: https://www.sammobile.com/firmwares/galaxy-note-edge/SM-N915P/ eventually.
Hello i got a note 4 Sprint MM 6.0.1 N910PVPU5DQI5 . i am from Argentina, and i bought the phone used from a guy from USA. (i don`t know how but it`s working with the bands here but i dont know if 4g is working, the guy says it works, maybe i don`t have 4g singal in my zone) .
the phone works fine, but has some srpint stuff and ads that bother me. so i flashed TWRP , and now i am looking for any roms and kernels to flash.
for example, is safe to flash this: https://forum.xda-developers.com/note-4-sprint/development/rom-updated-1-14-2017-t3538051
or should i change something first ???.