I am traveling to Europe soon and would like to SIM-unlock my phone.
I have the unlock code, but since I am currently on Fulmics 5.3, the unlock code doesn't work.
I think I need to get back to some stock-based rom.
My issue is, I am having trouble finding such a rom, and I am afraid to brick the device that's working fine right now.
Could someone please point me to a stock-based rom which would allow me to SIM-unlock?
Should I just install this ROM?
http://forum.xda-developers.com/att-lg-g3/development/rom-lg-d850-20f-lollipop-5-0-1-extras-t3052041
Kind of scared of going back to Lollipop from a MM-based rom.
Thanks in advance.
Edit: Went with installing the ROM linked above. Went smooth. SIM unlock also went smooth. Currently restoring nandroid backup, hope this works out as it should.
Edit2: All is well.
Related
So I want to do the new sw update but can't because I deleted some stock apps so the checksum wouldn't match and a hard reset won't restore them I guess so I would flash a stock rom but am I right thinking there isn't one yet? So how can I get to an original rom and then update or maybe make the new update work?
D2G stock rom
I don't know if the update will be compatible or not but from my understanding this is pretty much the stock rom that Motorola handed Verizon to put all their bloatware on then release the phone. I did load this rom on my d2g and it works flawlessly. Might be worth a try, not a direct link but will get you headed in the right direction. The rom manager gives you the opportunity to load the barebones stock google rom or the Vanilla based version, it just downloads and flashes, works perfect I didn't even have to re-activate. It is already pre-rooted so maybe the update won't work but I just wanted to make you aware of it. I work at verizon and did the update to the floor model and my dad's stock d2g also and didn't notice any difference really. I think vzw is just fixing some of the bugs that they created anyway so having the stock rom may end up with the same result, a rom that functions perfectly, good luck!.......droidforums.net/forum/droid-x-roms/106629-rom-fission-2-4-droidx-vanilla-generic-android-aosp-like-fission-rom-manager.html
@evil yeah im kind of in the same boat, let me know if srensber solution works for you.
I froze a bunch of apps with Titanium Backup and renamed some stuff with Root Explorer. I recently just re-named everything i changed back to the factory stuff (bak -> apk) but it still doesnt seem to do any good.
I did create a number of back ups using Rom manager but i cant seem to find out where they are located and how to restore them. hmm. Not sure what to do.
Ah i realize what ive done wrong ... i didnt know you had to have bootstrap installed along with clockwork recoveryy in order to make a backup hmm. Going to need a rom of stock d2g lol.
clockwork recovery installs a boot hijack, which might be the culpirt
srensber said:
I don't know if the update will be compatible or not but from my understanding this is pretty much the stock rom that Motorola handed Verizon to put all their bloatware on then release the phone. I did load this rom on my d2g and it works flawlessly. Might be worth a try, not a direct link but will get you headed in the right direction. The rom manager gives you the opportunity to load the barebones stock google rom or the Vanilla based version, it just downloads and flashes, works perfect I didn't even have to re-activate. It is already pre-rooted so maybe the update won't work but I just wanted to make you aware of it. I work at verizon and did the update to the floor model and my dad's stock d2g also and didn't notice any difference really. I think vzw is just fixing some of the bugs that they created anyway so having the stock rom may end up with the same result, a rom that functions perfectly, good luck!.......droidforums.net/forum/droid-x-roms/106629-rom-fission-2-4-droidx-vanilla-generic-android-aosp-like-fission-rom-manager.html
Click to expand...
Click to collapse
I cant seem to find the download link anywhere... and after you loaded this rom did you try to update to 2.4.3 ?
If anyone else has any input about this please help!
Hello,
I got a doubleshot off eBay. Everything seems to be going well with it - tested fine on T-Mobile SIM, rooted it, upgraded the ROM to Cyanogenmod 9.1. However I am having a problem SIM unlocking it.
I followed this guide:
http://forum.xda-developers.com/showthread.php?t=1232107
...and was able to get the unlock code no problem. When I put the Rogers SIM card in, I enter the code, and I get an "Network Unlock Successful" message. But then I have no service. When I reboot, it asks for the unlock code again.
I did some searching, it may have to do with my radio version (which I can't find in recovery, but I'm S-ON, HBOOT-1.45.0013, MICROP-0353, Nov 21 2011, 20:20:47), but it could be CM itself, other than that I am stumped. Does anyone have any suggestions what to do next?
Many thanks.
joel.maxuel said:
Hello,
I got a doubleshot off eBay. Everything seems to be going well with it - tested fine on T-Mobile SIM, rooted it, upgraded the ROM to Cyanogenmod 9.1. However I am having a problem SIM unlocking it.
I followed this guide:
http://forum.xda-developers.com/showthread.php?t=1232107
...and was able to get the unlock code no problem. When I put the Rogers SIM card in, I enter the code, and I get an "Network Unlock Successful" message. But then I have no service. When I reboot, it asks for the unlock code again.
I did some searching, it may have to do with my radio version (which I can't find in recovery, but I'm S-ON, HBOOT-1.45.0013, MICROP-0353, Nov 21 2011, 20:20:47), but it could be CM itself, other than that I am stumped. Does anyone have any suggestions what to do next?
Many thanks.
Click to expand...
Click to collapse
I'm fairly certain that the phone needs to be unlocked while on a stock ROM, or a stock-based ROM. Flash back stock or MiKtouch and enter your unlock code, and then you will be free to flash back to any ROM you like :good:
Ziida said:
I'm fairly certain that the phone needs to be unlocked while on a stock ROM, or a stock-based ROM. Flash back stock or MiKtouch and enter your unlock code, and then you will be free to flash back to any ROM you like :good:
Click to expand...
Click to collapse
Thanks Ziida, I will try out MikTouch when I get home tonight...
http://forum.xda-developers.com/showthread.php?t=1613917
Thought I could save a step by going directly to CM (didn't on my previous doubleshot) but this answer makes sense. Will let you know how it turns out.
Solved!
Ziida said:
I'm fairly certain that the phone needs to be unlocked while on a stock ROM, or a stock-based ROM. Flash back stock or MiKtouch and enter your unlock code, and then you will be free to flash back to any ROM you like :good:
Click to expand...
Click to collapse
(Being a little verbose in case someone else has this issue...)
So I downloaded MikTouch. Had to look for the download, luckily you had a link in the comments section of the above thread (would post the direct/outside link but I don't have enough posts yet to do to):
http://forum.xda-developers.com/showthread.php?t=1613917&page=60
So once the image was on the device, I rebooted into recovery, and performed a nandroid backup of my current ROM (I had things the way I liked them). Then it was wiping data and applying the MikTouch image.
The second reboot was sketchy (first being setting myself up to fastboot the boot image). I was able to enter my unlock code, which it promptly rebooted. I tested the phone once everything was back up, and success!
So back to recovery, I wiped data and cache, applied CM9.1 and GApps, rebooted, did the old "sudo fastboot flash boot boot.img", went into CWM again to restore my nandroid backup. Rebooted (everything was back), tested the phone once more, and we were all good.
Thank you for your suggestions!
Hey all, need a quick hand with my T-Mo LG G2 d801- 4.4.2 stock rom.
Process so far: towelroot>supersu>autorec>twrp>...
Tried flashing CM11, but after about 20min I figured I did something wrong, lol.
What version of cyanogenmod should I be flashing, 10 or 11? From the description of what AutoRec does to deal with the bootloader, it downgrades to the last vulnerable rom to install/enable custom recovery, correct? If so, does it stay downgraded or is that just to get the custom recovery in place?
Don't want to brick my phone experimenting, so here I am. Thanks in advance!
Also should have waited till after work, as I have no more time tonight to mess with it unfortunately. Back in 8hrs! :silly:
Nevermind, I got it working.
fleshybits said:
Nevermind, I got it working.
Click to expand...
Click to collapse
Consider that while others might not have had an answer to your question, your thread could have been frequented in order to see the answer.
So, how did you resolve your issue? ?
fleshybits said:
Hey all, need a quick hand with my T-Mo LG G2 d801- 4.4.2 stock rom.
Process so far: towelroot>supersu>autorec>twrp>...
Tried flashing CM11, but after about 20min I figured I did something wrong, lol.
What version of cyanogenmod should I be flashing, 10 or 11? From the description of what AutoRec does to deal with the bootloader, it downgrades to the last vulnerable rom to install/enable custom recovery, correct? If so, does it stay downgraded or is that just to get the custom recovery in place?
Don't want to brick my phone experimenting, so here I am. Thanks in advance!
Also should have waited till after work, as I have no more time tonight to mess with it unfortunately. Back in 8hrs! :silly:
Click to expand...
Click to collapse
Autorec just flashes an older boot loader, with a stock based KK kernel that's compatible. Once up and running any stock based kernel can be flashed if running a stock ROM. It also supports running any after market ROM, however, if running a jb based ROM one needs to be on a jb modem, and if running KK a compatible modem. These are pretty much the only prerequisites.
Sorry, that was rather rude of me wasn't it? Apologies. Not fair to ask for help if I can't return the favor when I can.
Well, instead of looking around on the CM downloads page to get the most stable release, I just got the most recent snapshot of CM 11. Silly me
Turns out the right file to flash first was, of course, the last stable release for the G2 D801, which was CM 10.2.0 (at least at the time of this writing, as far as I know.) After getting the right file and trying again, I was rocking my first custom ROM. Go me! :good:
I have not yet tried the snapshot again to see if I could upgrade to CM11, as I hit another snag: I can't connect to my carrier anymore. I can see T-Mobile in the list for networks but selecting them does nothing, I get no service. Restoring the stock ROM works just fine, its like nothing happened, but running CM I can't connect. Any suggestions?
So, I'm buying this to replace my evo 4g and I was wondering how I would go about using a custom ROM for this and having the apns and data working correctly.
I plan to activate it on Ting.
To be a bit clearer, I want to use a custom ROM and I want to be sure that it'll work. So first, can anyone on Ting confirm that they're running a custom ROM (preferably KitKat) with no problems?
And I assume I'd have to activate the phone first, then install a custom ROM. Would I have any problems doing that? Would the apns be messed up? Or should everything be fine as long as I activate the phone and update everything on stock before installing a ROM? Reason I ask is because I know some Roms don't allow the *#*# thing needed to activate a phone on a new network.
Thanks!
I am using mine on Ting. I had used my first Q as unrooted stock JB, which worked pretty well for a year, but then it reached a near--bricked state where it wouldn't boot past the yellow Sprint screen. I couldn't resolve this in a timely fashion, so wound up buying a second Q which runs stock ICS, but failed to download the stock JB update.
In the meantime, I unlocked both phones' bootloaders, and tried a few kItkat ROMs on my original phone before settling on CM 10.2, which is a JB ROM. I then switched my Ting activation (back) to this phone. The lack of #*# commands isn't really a problem with respect to re-activation, but it is a problem with respect to PRLs and (perhaps) APNs. I recommend Ting activation and a PRL update prior to installing your custom ROM.
Like others, I would like to learn about a stable kitkat ROM where bluetooth, wifi, and phone data/sms/calling all work reliably. My other primary requirement is the ability to play DRM'd downloaded Amazon Prime Music, which didn't work on the kitkat ROMs I tried, but does work on my JB ROM.
Sent from my XT897 using Tapatalk
I need some assistance please! I am truly baffled by what I am experiencing and would like to know why and hopefully how to fix it. Here's the details:
CARRIER: Verizon
MODEL: HTC One M8
S-OFF: Yes (Sunshine)
ROOT: Yes
HBOOT: 3.19
RADIO: 1.09.20.0926
OpenDSP: 46.2.2
OS: 3.28.605.4
First off, sorry for the book, but I figured more details would be better at this point to figure out what is up, so I appreciate any assistance in advance! PS: I bolded the key items to the story for those that like to skim.
Prior to S-Off and Root, I was on OTA version 4.4.4 waiting in anticipation for 5.0 to come to my device. Was unsure about spending $25 for Sunshine's method, but finally decided to take the plunge. At first things seemed great and very smooth. Following all instructions from Sunshine I was finally with S-Off status. I then used WeakSauce2 to gain temp root of the Stock ROM so that I could install Flashify and TWRP. Rebooted and loaded up TWRP Recovery and completed the first Nandroid. SUCCESS! Next up was Titanium Backup and such and copied everything off to my computer for safe keeping. So far so good and then loaded up a few ROM files and whatnot to the External SD Card so I could start flashing a new ROM. Feeling good up to this point, but here's where the troubles begin...
I have had great success with CyanogenMod in the past on previous devices and always very pleased. I read CM12 for others was great and stable and performed well, so I decided to grab the latest CM12 Nightly and the GApps package. Did the normal Wipe / System Wipe for initial flash of a new ROM and then installed both ZIPs no problem. The ROM boots up and everything seems okay, only I do not have LTE at all, only 3G. I also tried the GPE rom by Digitalhigh and experienced the same thing! Restoring from Nandroid also did not fix LTE, so at this point I got worried I broke my phone somehow.
To make a long story short after lots of testing I found a fix for getting LTE back on my original ROM. I found the 4.4.4 RUU and placed the 1.7 GB zip file (0P6BIMG.zip) on the root of my external SD Card, booted into HBOOT and ran the update. It did it's thing and booted up into the Stock ROM. Still no LTE! So then I found a comment somewhere about once that is done, do a Factory Reset from HBOOT using the Stock Recovery and it is supposed to reset the NV Radio Partition, so I did this and when it booted back up, SUCCESS! I have LTE back.
Once that was done I can now flash GPE, (but unusable because SMS is not working for some reason... I am using Google Voice BTW), so I am back to my original 4.4.4 TWRP Recovered ROM. I tried just for kicks to see if after the "fix" if I could make CM12 work, but again will bring it down to an unworking LTE status. Rinse and repeat the "fix" and got LTE back and did Nandroid Recovery. I paid the money to get S-Off and Root access so I could enjoy the Custom ROM's, but now I feel I am stuck...
All that being said... Can someone please explain to me what is going on?? And is there any way I can fix this so I can use CM12 and have LTE, and even then some other ROMs? I will post in Digitalhigh's forum for resolution to the SMS issue, but I have never had this much trouble with a device before and do not know enough about the different partitions and how they work and such. Any assistance and advice is MUCH appreciated!
Thank you!
Nobody has any advise or explanation?
I don't know the version numbers you posted from you bootloader off the top of my head but did you update your firmware to one of the unofficial ones around before flashing one of the lollipop roms? Is so, are you sure it took completely as sometimes you have to flash it twice.
Alternatively you could wait for our official firmware to drop any minute now and have pretty good odds of working for you.
cntryby429 said:
I don't know the version numbers you posted from you bootloader off the top of my head but did you update your firmware to one of the unofficial ones around before flashing one of the lollipop roms? Is so, are you sure it took completely as sometimes you have to flash it twice.
Alternatively you could wait for our official firmware to drop any minute now and have pretty good odds of working for you.
Click to expand...
Click to collapse
Yes I did use official firmware, and flashed twice per recommendations. I have it working with GPE, but every time I flash CM12 it breaks LTE. I have seen articles and posts of others running CM12 on their M8's with VZW and stating "zero issues"... Lack of LTE sounds like an issue to me. So my big question at hand is, why does CM12 break LTE, and is there a fix? Everything else seemed to work great otherwise.
kjparenteau said:
So my big question at hand is, why does CM12 break LTE, and is there a fix? Everything else seemed to work great otherwise.
Click to expand...
Click to collapse
I was reading the CM12 m8 thread earlier this week and many reported that LTE did not work on builds from late Feb. early March. CM12 is in no way stable and results will vary from phone to phone. Even the speaker issues have not been fully resolved. Bummer, because I'd really like it to be more stable.
http://forum.xda-developers.com/htc...genmod-12-0-nightlies-htc-one-t2998070/page75
Thank you for your reply. Definitely wanting CM since I used to run that regularly on my older devices with no troubles at all. The speed and simplicity are what I am going for. Sense is okay, but the difference of less than 300 megs with CM compared to over a gig for stock is unreal. WAY less overhead.