I'm pretty new to all this, I had a Rogers Captivate that had been crashing on me. Everything suggests that if I changed my software it would work.
So I managed to to flash a newer AT&T ROM on to the phone via Odin. (I was pretty chuffed with myself)
However, as soon as I put my sim into it, it became locked. I paid an online service to get an unlock code, but the IMEI number I delivered to them didn't match the network, so I messed that up.
Now I've noticed that I could flash a rooted ROM via Odin, which should save me having to unlock, right ?
I went to the thread http://forum.xda-developers.com/showthread.php?t=1621350 and looked for a suitable ROM (preferably supported).
I went for the PAC ROM, but noticed there is no tar file in the download.
The other ones I wanted to try either suggested it was flashed by another method than Odin (I might be wrong) or the download links for the files themselves were no longer working.
Also, there is talk about Gapps. What is this and what is the process for installing it ?
Thanks in advance for any help you can give me.
Hi there,
You'll need to specify that the phone is still on the Rogers network, as that's how they access the database. Ie., if you have a phone that was supplied to Rogers, the IMEI will be associated with Rogers and if you tell them it's ATT, they won't be able to find it - regardless of what ROM you're running.
Unfortunately, as far as I'm aware you do have to pay to unlock the ROM again but I'm not an expert on this - I know that I had the same problem you did and they told me to put it in as Rogers instead - that got me my unlock code.
I have a rooted Milestone 2 which is running JB now, and it is still operator locked unfortunately.
Apparently the GalaxSim Unlock tool is good but I don't know if it retains your IMEI - I know it does back up your EFS though. Maybe it's worth a try?
Before doing anything with your IMEI i suggest you to backup your efs folder. There's a software for this too.
[sent from my awesome Samsung Captivate Glide]
[AT&T rooted stock ROM]
thank you
Thanks for the feedback, I've reapplied for my unlock code.
What I'd really like to know now is which rooted ROM should I choose to flash via Odin ?
pardoning edeaoh
hkcharlie said:
Thanks for the feedback, I've reapplied for my unlock code.
What I'd really like to know now is which rooted ROM should I choose to flash via Odin ?
Click to expand...
Click to collapse
Hi hkcharlie,
Have a look at the below thread to unlock your sim card. I used it on mine and my friend's S3.
http://forum.xda-developers.com/showthread.php?t=1846451
I suggest reading the "everything about captivate glide" thread here:
http://forum.xda-developers.com/showthread.php?t=1621350
I use CWMR (ClockWork Mod Recovery) from this post:
http://forum.xda-developers.com/showthread.php?t=1458153
You have to flash this acording to ODIN. Afterwards, you can download .zip files directly to your device for flashing, or download them on your computer and copy them to the devices SD card. Select them in recovery mode and they will install.
These two roms I've had a lot of success with:
http://forum.xda-developers.com/showthread.php?t=1945558
http://forum.xda-developers.com/showthread.php?t=2021374
They're both ICS. There is a cm10.1 JB (4.2.2) build as well, and it's *awesome* - but it is missing a few critical features so I won't recommend it for your first time.
Almost any ROM you flash from this forum will already be rooted. Being 'rooted' just means having a kernel that supports it (both ICS rom's above include a root-capable kernel) and a /bin/su and appropriate superuser apk.
Of course, back up your EFS - there are some apps on the market that will help you do this. And backup everything. And test your backup. And your warranty is void, your phone may explode, or impregnate you with mogwai. (do not get wet, do not feed after midnight.)
Happy flashing!
Good evening everyone -
I'm running into some issues with my LRA version of the M8. I am/was rooted and running TWRP fine until I decided to revert back to the stock recovery so I could install the latest OTA that was released to me. Like an idiot I never backed up my stock OTA before flashing TWRP so I extracted the firmware.zip from the OTA download, relocked my bootloader, then used fastboot to flash firmware.zip. All seemed to go well until I rebooted, I'm now stuck at the HTC splash screen and can get no further. Things I've done:
- tried booting into recovery, got red triangle w/red exclamation mark
- unlocked bootloader and installed TWRP, can get into recovery now at least
- tried factory reset
- wiped cache, no luck
Unfortunately the LRA M8 isn't very common it appears so I'm unable to find a stock ROM to try and reinstall. I'm hoping someone might be able to help me get started back up without the need for my stock RUU or nandroid backup. Any assistance would be greatly appreciated, please let me know what other info I could provide to help out. Thanks in advance.
promsos said:
Good evening everyone -
I'm running into some issues with my LRA version of the M8. I am/was rooted and running TWRP fine until I decided to revert back to the stock recovery so I could install the latest OTA that was released to me. Like an idiot I never backed up my stock OTA before flashing TWRP so I extracted the firmware.zip from the OTA download, relocked my bootloader, then used fastboot to flash firmware.zip. All seemed to go well until I rebooted, I'm now stuck at the HTC splash screen and can get no further. Things I've done:
- tried booting into recovery, got red triangle w/red exclamation mark
- unlocked bootloader and installed TWRP, can get into recovery now at least
- tried factory reset
- wiped cache, no luck
Unfortunately the LRA M8 isn't very common it appears so I'm unable to find a stock ROM to try and reinstall. I'm hoping someone might be able to help me get started back up without the need for my stock RUU or nandroid backup. Any assistance would be greatly appreciated, please let me know what other info I could provide to help out. Thanks in advance.
Click to expand...
Click to collapse
Did your firmware.zip have a boot*.img in it? You probably need the old version of the boot.img to match the old software. You might want to find on of the old Verizon RUUs and extract the boot.img from there and try flashing that in fastboot. Message me if the Verizon boot doesn't work for you, I might have some other ideas. I'd say be careful, but you're already in trouble.
Edit: You could also do a nandroid backup and try a custom ROM to get it functional in the short term.
I did eventually grab a nandroid backup and loaded Viper Rom on it, although it's a bit quirky - probably because the LRA version of the phone is slightly different than the stock Verizon version. That being said, the firmware.zip that I loaded did have a boot.img file in it so I'm guessing that's the issue. Do you think the boot.img from a Verizon RUU would work considering my phone is not the same exact version as the Verizon one? Or another way to ask it I guess is if there's really any harm in me restoring my nandroid and loading a standard Verizon boot.img? I'd think it can't render my phone any more useless than it was previously, just wasn't sure how locked in the boot.img file was to the specific model\OS that's on the phone. The whole LRA phone thing is really a kick in the pants.
promsos said:
I did eventually grab a nandroid backup and loaded Viper Rom on it, although it's a bit quirky - probably because the LRA version of the phone is slightly different than the stock Verizon version. That being said, the firmware.zip that I loaded did have a boot.img file in it so I'm guessing that's the issue. Do you think the boot.img from a Verizon RUU would work considering my phone is not the same exact version as the Verizon one? Or another way to ask it I guess is if there's really any harm in me restoring my nandroid and loading a standard Verizon boot.img? I'd think it can't render my phone any more useless than it was previously, just wasn't sure how locked in the boot.img file was to the specific model\OS that's on the phone. The whole LRA phone thing is really a kick in the pants.
Click to expand...
Click to collapse
The boot.img from an older Verizon RUU would probably work, but you might have to try a couple to get the right one. The boot.img is directly tied to the ROM version that is installed, and is often called the kernel and tells the system how to boot the ROM.
Make sure you do a backup of your working Viper before restoring the stock one and trying to flash a boot.img.
I don't understand why you re locked the boot loader and flashed a firmware zip just to revert to stock recovery? All you had to do was pull the stock recovery from the firmware.zip in the OTA then flash it via fast boot. Then go ahead and flash the OTA.
You need to now find and flash a compatible boot.img. Just keep trying different ones until it boots.
I'm making a little progress here, thanks for the help. I downloaded a 4.4.3 Verizon kernel, loaded that (after restoring the old nandroid backup) and I'm able to boot, whew... I'm having two issues now, 1) my wireless won't turn on for some reason and 2) I tried installing the 4.4.4 OTA update my carrier released (downloaded via 4G) and it won't apply - I was hoping successfully applying this OTA would fix the wireless issue. Looking at my software version it looks like I'm actually running 4.4.2, could that cause both of these issues? I'm trying to locate a 4.4.2 kernel to load but figured I'd toss out the question in the meantime.
Ashyx - I wish I had a better answer to why I temporarily relocked the boot loader and flashed firmware.zip other than desperation (trying to get that darn OTA). It was a while ago I flashed the firmware.zip file but I thought that when I initially extracted the recovery from the zip file and flashed it I could no longer boot into a recovery, maybe I'm making that up though - I can hardly remember last week lol. I'm an IT guy, so I'm not completely clueless, but I'm far from proficient with mobile technologies, as I'm sure you gathered already.
Anyways, I'd appreciate any insight, in the mean time I'm going to keep hunting for a 4.4.2 kernel to try on this thing. Thanks again to all.
http://forum.xda-developers.com/showthread.php?t=2723159
Try the zips from here, they should have a boot.img for 4.4.2.
Sent from my One M8 using XDA Free mobile app
Ok, I think I'm back up and running. I was able to find a 4.4.2 boot.img that allowed me to once again use my wireless. After getting the wireless working I had to find valid versions of flashlight.apk and calculator.apk to put in data/preload and the OTA finally took....success at last. I really appreciate the help durgis, I'll be grabbing a nandroid of my now working phone right away so I don't run into issues in the future. Again, thank you for the help, very much appreciated.
I suspect that we are on the same carrier, LRA__001. I've been fighting a similar problem to yours. The only custom rom I've been able to install is Cyanogenmod. It's good, but the battery life is horrible for me. Also, I can't get MMS or 4G to work. Everything other rom I've tried won't boot up for me. Any chance that you could provide a link to your nandroid backup? I'm looking to get back to a more stock rom that I can get OTA updates on. Thanks.
rook79 said:
I suspect that we are on the same carrier, LRA__001. I've been fighting a similar problem to yours. The only custom rom I've been able to install is Cyanogenmod. It's good, but the battery life is horrible for me. Also, I can't get MMS or 4G to work. Everything other rom I've tried won't boot up for me. Any chance that you could provide a link to your nandroid backup? I'm looking to get back to a more stock rom that I can get OTA updates on. Thanks.
Click to expand...
Click to collapse
Hey rook, I do have the same CID, are you on Cellcom out of Wisconsin? I didn't grab a bare bones nandroid, but i can do a backup, uninstall my apps and do one, or rebuild mine from my unbootable one now that I have everything i need. If you want to try a different ROM you could try Viper, it worked decent for me, just a few quirks when i bounced from wireless to 3G for some reason.
I am with Cellcom. My problems started with the recent OTA update. The update wouldn't take, because of the flashlight.apk. I decided it was time to root this phone anyway and try some custom roms. I've done it with my other HTC phones in the past with no problems. Unlocked the bootloader, loaded TWRP and did a backup. Didn't check where the backup was being put and ended up saving it to internal. Put on a new ROM and wiped my backup. Cyanogenmod 11 is the only ROM that I've had success with. Every other rom that I have tried so far will not complete the initial boot. I suspect that I'm missing something stupid, or it has something to do with the OTA update not completing. Are you running Viper, or did you get the Cellcom OTA update to work?
I was running Viper for a while but now have my phone reverted to stock with the 4.4.4 OTA applied. If you want a nandroid of stock Cellcom 4.4.4 I can work on one for you, it may take a couple days to get it but I should be able to get one.
That would be awesome. I've been looking for a stock Rom for a while now. As you know those are nearly impossible to find. Not having a stock nandroid backup or the OTA update zip kind of put me in a SOL position. Thanks for your help.
Finally got around to this, try the download below, it's the stock 4.4.4 ROM and also the stock recovery (for future OTA updates). Let me know if it works out for you. I also have the 4.4.4 OTA updated if needed.
https://www.dropbox.com/s/thd0z8l2zlprt3r/One M8 LRA 4.4.4 Stock.zip?dl=0
That worked awesome. Thanks!!!
Hi Guys, (@rook79 , @promsos)
i have the same model and running into similar problem, i was also not able to flash any other rom than SkyDragon, wanted to be able to flash other roms but no luck, i thought its the firmware that wont let me install so i went for S-Off and flashed one of the firmware from verizon, since there was not much help for this specific model and everyone was referring it as a variant from verizon, i did flash one and my problem started, my phone had no signals after flashing the firmware and was still not able to flash any other ROM, i flashed couple of more firmwares and radios to get my network working but no luck, and i got a new problem that the phone keeps rebooting after a couple of minutes it loads into system.
then somebody helped me with the stock firmware 4.4.4 from here and nandroid from this thread, firmware was still verizon, i managed to restore it but still the same reboot issue and no signals, but i was able to download OTA which wont install, everytime i try to install it, it goes to stock recovery with a progress bar 1% filled and then stuck into boot loop and after n number of attempts it boots into system, where again it reboots after a couple of minutes.
extracted the firmware from OTA and manually flashed it and tried to install OTA but still same, i tried to reboot into stock recovery but every time i do that, it goes to black screen and then keep rebooting, i am not able to get to that red triangle screen.
help less clueless trying to find complete RUU for it (not sure if thats going to help)
my partition table has 2 vzw partitions as well because i flashed dottat's RUU for verizon.
can you guys help me with that?
my phone is m8_wlv CID: LRA_001 MID: 0P6B20000
s-off, and i am on a GSM network (not US).
promsos said:
Finally got around to this, try the download below, it's the stock 4.4.4 ROM and also the stock recovery (for future OTA updates). Let me know if it works out for you. I also have the 4.4.4 OTA updated if needed.
https://www.dropbox.com/s/thd0z8l2zlprt3r/One M8 LRA 4.4.4 Stock.zip?dl=0
Click to expand...
Click to collapse
I'll appreciate if you share the 4.4.4 OTA, I really need it now.
hoang555 said:
I'll appreciate if you share the 4.4.4 OTA, I really need it now.
Click to expand...
Click to collapse
is this what you are looking for? https://www.dropbox.com/s/2oozc291kwe5l9r/OTA_M8_WL_L50_SENSE60_MR_LRA_US_4.21.512.4-3.31.512.2_release_426215.zip?dl=0
hoang555 said:
I'll appreciate if you share the 4.4.4 OTA, I really need it now.
Click to expand...
Click to collapse
Hi
Do you still have that LRA version?? I need some help
I thought I'd put together a basic survey to possibly help others with their Unlocking/rooting questions.
Please only answer if you have successfully completed the steps and have your bootloader unlocked and phone rooted based on information provided by THIS thread. If you don't currently own a Verizon Retail Note 4, respectfully, PLEASE DO NOT post a reply. Thank you.
If you reply, it is assumed that you have completed the process and have successfully turned your Retail Phone into a Developer Phone. If you are still "tinkering" with your phone after the conversion process, feel free to reply and update your reply as needed, to help others.
Before you began:
Your Android Version?
Your build number?
Did you Odin or Flash to get the above Build Number?
What version of KingRoot did you use to Temp Root your phone?
After Converting to Developer Mode/Rooting (Some questions - If Applicable):
SINCE converting, what Android Version/Build Number have you upgraded from/to? Was the upgrade via OTA or Odin?
What confirmed working root apps are you running (other than Root Checker)?
What have you installed onto your phone that requires an unlocked bootloader that are confirmed to be working?
Has this process changed (made better or worse) how your phone reads extended batteries? State which external batteries you have tested, since the root process was made available this week.
Here's my experience.
STARTED WITH:
Your Android Version? 5.0.1
Your build number? BOG5 Safe Upgrade
DOWNGRADED TO (Because I thought I had to which might've been a mistake)
Your Android Version? 4.4.4
Your build number? ANJ5
Flashed via Odin 3.10.7
Results: After starting the HOWTO Guide on converting from Retail to Developer Mode, I got stuck on THIS step, which gave me an error message
Code:
./samsung_unlock_n4-2
Later, I was told that others had reported issues trying to convert from KK. I then took the Safe Upgrade to BP1. Be sure that you are installing the RETAIL version of the ROM, not the Developer Version. You are not there, yet.
Once you are on BP1, download eMMC Brickbug Check from the Play Store. Verify that your CID begins with 15 followed by a bunch of random numbers. Then, follow the steps on the HOWTO Guide on converting your Retail phone to Developer.
After you do this:
Boot to Download Mode (VOLUME DOWN+HOME+POWER) and flash TWRP 2.8.5 recovery via Odin
If you haven't, already, get your MicroSD card, plug it into your computer and load SuperUser and the kernel (see this reply) onto it. Put it back into your phone
Boot to TWRP recovery (VOLUME UP+HOME+POWER)
Install the two files you just loaded
I this point in time, you SHOULD have BPA, Developer Mode AND root.
With that said........
Your Android Version? 5.0.1
Your build number? BP1
Flashed via Odin 3.10.7
What version of KingRoot did you use to Temp Root your phone? KingRoot 4.8.5
Rather than answer my own questions, I'll just state what so far does work that I've tried:
I've installed CM13 via TWRP. I currently do not have root, but that's about to change.
Before you began:
4.4.4
ANJ5
Don't remember
4.8.5
After rooting:
(If applicable) Have you taken an OTA or Flashed via Odin to a more updated build number? If so, what build number?
Upgrade to 5.0.1 N910VVRU2BOG5_StockRestore.tar.md5 using Odin.
Followed directions to unlock Developer mode.
Flashed N910VVRU2BPA1_StockRestore.tar.md5 to get 5.1.1 through Odin.
Reflashed TWRP and rebooted.
copied MultiSystem-Kernel_LP-5.1.1.zip, BETA-SuperSU-v2.67-20160203160253-TruncatedBoot-Fix.zip, and xposed-v75-sdk21-arm-arter97-snapdragon.zip to phone and flashed them through TWRP. Wiped cache and Davlik cache. Rebooted.
(If applicable) What confirmed working root apps are you running (other than Root Checker)?
Titanium Backup, SD Maid, Xposed Framework, TWRP Manager, Call Recorder, BusyBox Free.
(If applicable) What have you installed onto your phone that requires an unlocked bootloader that are confirmed to be working?
You couldn't install TWRP without an unlocked bootloader, so...
(If applicable) Has this process changed (made better or worse) how your phone reads extended batteries? State which external batteries you have tested, since the root process was made available this week.
Haven't tested yet, but I think the MultiSystem-Kernel_LP-5.1.1.zip and screen auto brightness settings are draining battery less. Too soon to tell.