I am overjoyed to see that there is finally an official gingerbread update that I can flash, and then a CM7 for this kernel, that doesn't have any bugs that are too annoying. However, it's been a while since I became an expert on flashing my old LG Eve. Is there a thread somewhere that outlines exactly how to do this for this exact phone and mod?
I've got a D2G, with Fission ROM. the phone is unlocked and rooted. I have an original ROM saved to flash to the phone if need be. Everything I would ever need is backed up using Titanium Backup. I've downloaded the GB update and CM7. I think I'm ready to go.
Questions:
- Is there a thread that answers all this already?
- Am I going to run into any problems being unlocked or rooted?
- Does the phone revert back to being locked once the new GB is installed? That would not be good considering I'm in Canada, not on Verizon. I bought my phone unlocked so I don't know how to just unlock it again.
- I remember using nandroid before to make a complete backup of the contents of my phone so that if I screwed up I could just go back to it seamlessly. Same thing this time around?
- I'm not completely illiterate here though, so I'm going to give it a go and you can just correct me where I am wrong. First, put the CM7 and GB files on the SD card. then do a nandroid backup of the phone. Clear data, clear cache. Then use clockworkmod to flash the GB update. then use clockworkmod again to flash CM7. then use clockworkmod again to flash gapps. Start up phone, do a complete restore with Titanium and I'll have all my apps and settings, call history and texts back. I'm probably wrong somewhere in all this, but where?
If there's not already a comprehensive thread on this, let this be it!
You will need to SBF to stock to be able to install the update.
Refer to the following for some instructions:
http://droid.koumakan.jp/wiki/SBF
http://droid.koumakan.jp/wiki/4.5.607_Firmware
http://droid.koumakan.jp/wiki/CyanogenMod
Ok, I read these all over about 5 times. So in a nutshell, these are the steps:
- use rsdlite to put your phone back to the stock firmware 2.4.330
- unroot and remove cwm
- use android recovery to install gingerbread 4.5.607
- root again and install cwm again
- use cwm to install cyanogen and gapps.
Correct?
Also, I am running fission. According to my system info it is firmware 2.4.3. I would rather skip step 1 and just install gingerbread. I am guessing I can't, but please confirm.
Sent from my DROID2 GLOBAL using XDA App
You don't need to unroot and remove CWM after flashing the SBF.
Otherwise everything's correct.
You cannot install the official Gingerbread firmware update onto a phone that is not running stock unrooted 2.4.330 without CWM and with all bundled software intact.
Note: if you need to backup your applications and configuration data, you can do so with CWM. Make a backup under Fission, then perform all those steps above, and once you're running CM7 on 4.5.607, use CWM's advanced restore feature to only restore /data.
So here I am in Gingerbread on my D2G (already further than I thought I'd get!) and you would think it would be smooth sailing from here... except I can't root it now! Is there a different technique for rooting in Gingerbread? I used Z4 before, and it worked in seconds.
OK, I figured out how to root using another thread. and when i am in adb shell I get "#" and not "$" after entering a string of commands.
But, apps think that I'm not rooted. All I need is to install CWM, but it runs into errors, presumably because I am not rooted.
The phone is in some sort of weird half-rooted state.
really weird experience with rooting. I realized that I hadn't done the additional steps where you push superuser to the phone and a couple other commands. So I did that, and then root check said i was rooted. I rebooted, and adb shell was acting like I wasn't rooted! yet root check still said I was. I was able to flash CWM and reboot, and then install CM7. Everything seems great!
except, right from the start I was getting repeated FCs for com.android.phone.
I remember that there's an issue with needing to reboot after switching to GSM... so I'm trying that now. Let's hope that stops the FCs.
So what ended up happening was, I rebooted and stopped getting the FCs for the phone after switching to GSM. So that is good. However, aside from the two minor bugs that I was prepared to live with, this is happening now:
- I have phone and SMS service, just no data. Wireless works fine, and so do GPS and Bluetooth to my knowledge.
- When attempting to select a network to register on, I get the dreaded “Your SIM card does not allow connection to this network” message. I have tried doing this with data/roaming enabled/disabled and with “only 2G” selected. I have also tried a couple of tips I found online such as removing the battery for 15 minutes and also getting a new SIM card.
- At first I was able to enter new APNs, but they wouldn’t save. I hit menu, then save, but it goes back to the APN screen and none are listed. Now, what happens is, if I hit menu, then “add new apn”, nothing happens.
I went into the telephony.db file to manually enter my APNs, and it seems that they are already there, which is good. I re-entered them all manually using sqlite anyway. This did not work. I also noticed that Verizon was listed with a “1” in current, which probably means that Verizon is my current APN. So I removed that 1 and placed it on all my rogers APN entries. Still, nothing is saved at the APN screen in settings, and I can’t enter them through that screen, either. And no data.
Suppose it turns out that this is just a bug with CM7 right now and it’s unusable for me. Obviously I don’t want to go all the way back to Fission on Froyo when I can use gingerbread. How far back into this process do I have to go? Can I just flash GB and it will overwrite CM7?
Did you make a CWM backup of your freshly installed Gingerbread? If so, just restore.
If not, I don't see how you're going to “just flash Gingerbread” without SBF'ing to 2.4.x.
Well, I have done a lot of testing and troubleshooting. I went back to the start of this whole process, and I backed up my APNs and fully tested the phone at every turn, and my conclusion is that CM7 is not friendly to APNs. There was no problem with stock Froyo or stock Gingerbread. With the working APNs that I had, I was able to use data on both. Once CM7 was installed, it was a no go.
I used a couple of apps to backup my APNs both in Froyo and Gingerbread prior to installing CM7, and when CM7 inevitably didn't allow me to use data, I tried to restore my APNs using these programs as well. They say that they worked, and it's true that if you go into root explorer the APNs are there as you entered them or restored them using a program. But it seems these APNs are not going to work unless you actually see them at the APN page in settings. And nothing I have tried up to this point has been able to make any APN show up at that screen.
I think the “Your SIM card does not allow connection to this network” message at the network operators screen, as well as my inability to enter APNs, are 100% related. I also bet there is a simple solution to it!
If anyone has any ideas about how to make an APN stick, and how to force a phone to start using it, please let me know. I'll also post this at the CM7 forum.
Related
I'm obviously new to this so bare with me.
I just rooted my Sprint HTC Hero and the first thing I would like to do is use it to tether. I've tried both versions of Android_wifi_tether (1.52, 1.6) but have had no luck in getting it functional. Basically; It broadcasts the signal (I'm at work so the only way to test it was with a Macbook) just fine. The Macbook even connects to it and my phone shows "3KB down 7.8KB up" meaning it detected something has connected. Once that happens nothing else works. The Macbook indicates it has no internet connection.
I was wondering if anyone has been able to get this to work? I'm a little hesitant on installing a custom ROM because it seems like a lot of work and I'm not too knowledgeable when it comes to Linux.
Also, can my phone still be updated or is that still unkown? If I install a root app and the update kills root does that mean I lose it entirely or just for anything I try to install post update?
As a side note: Someone should make a post with step by step guides to follow. What I mean by this is put the guides in chronological order.
1) Root your phone (guide link)
2) Run Nandroid backup (guide link)
3) etc.
Anyway, really appreciate the work! This is exciting.
fatkitty420 said:
I'm obviously new to this so bare with me.
I just rooted my Sprint HTC Hero and the first thing I would like to do is use it to tether. I've tried both versions of Android_wifi_tether (1.52, 1.6) but have had no luck in getting it functional. Basically; It broadcasts the signal (I'm at work so the only way to test it was with a Macbook) just fine. The Macbook even connects to it and my phone shows "3KB down 7.8KB up" meaning it detected something has connected. Once that happens nothing else works. The Macbook indicates it has no internet connection.
I was wondering if anyone has been able to get this to work? I'm a little hesitant on installing a custom ROM because it seems like a lot of work and I'm not too knowledgeable when it comes to Linux.
Also, can my phone still be updated or is that still unkown? If I install a root app and the update kills root does that mean I lose it entirely or just for anything I try to install post update?
As a side note: Someone should make a post with step by step guides to follow. What I mean by this is put the guides in chronological order.
1) Root your phone (guide link)
2) Run Nandroid backup (guide link)
3) etc.
Anyway, really appreciate the work! This is exciting.
Click to expand...
Click to collapse
Currently the only phones that have wifi tethering working are the ones who installed MoDaCo's ROM...something in there is configured differently to allow it to work.
thecodemonk said:
Currently the only phones that have wifi tethering working are the ones who installed MoDaCo's ROM...something in there is configured differently to allow it to work.
Click to expand...
Click to collapse
How functional is the ROM?
The one thing I'm scared of is that if I install a ROM I'll be dependent on this community to make future things work?
I mean, can you still access the Market? What about future updates? Will applications I purchased already still be available?
Like I said, I'm still fairly noobish.
fatkitty420 said:
How functional is the ROM?
The one thing I'm scared of is that if I install a ROM I'll be dependent on this community to make future things work?
I mean, can you still access the Market? What about future updates? Will applications I purchased already still be available?
Like I said, I'm still fairly noobish.
Click to expand...
Click to collapse
No sweat! If you look at my join date and postcount, you can see I'm not exactly the veteran around here either.
The MoDaCo ROM doesn't modify very much yet...just adds functionality (it's not the heavily optimized kernel that the GSM users have for example). I'm finding it fairly stable...there's a few quirks but those have fixes pretty easily found so far.
I can still purchase from the market...the stuff you purchased already is tied to your google account, not your phone. I bought Docs2Go before I rooted and flashed and I was able to redownload and install without any hassle or added cost.
On a custom ROM, future updates do depend on the person who is building the ROM. However, MoDaCo has proven pretty reliable thus far in keeping up with releases so it's a bit of a trust thing, do you trust MoDaCo to continue that trend or would you rather place your trust in the manufacturer? (It's a preference thing and willingness to risk either way).
The upside is that once you root to a recovery image (Not even changing your OS), you can take a Nandroid backup of your phone, which is an image you can drop back on there to get back to stock/manufacturer spec (as if you never left).
Any changes to your phone since the backup will not show up but that's kindof the risk.
thecodemonk said:
k on there to get back to stock/manufacturer spec (as if you never left).
Any changes to your phone since the backup will not show up but that's kindof the risk.
Click to expand...
Click to collapse
This is somewhat confusing for me. My phone is currently rooted. If I restore it factory default will it still be rooted?
If not,
Then should I restore to factory default first, take a Nandroid back up (this looks difficult), then root my phone?
The recovery image is basically replacing the "Factory reset" image, right?
fatkitty420 said:
This is somewhat confusing for me. My phone is currently rooted. If I restore it factory default will it still be rooted?
If not,
Then should I restore to factory default first, take a Nandroid back up (this looks difficult), then root my phone?
The recovery image is basically replacing the "Factory reset" image, right?
Click to expand...
Click to collapse
Ah ok...the recovery image is like a second mini OS you are booting into that has menu options and specializes in updating your phone with a custom ROM, running Nandroid for backups, and enabling you to mount your SDCard to your computer, so installing that doesn't actually do anything to your phone's running OS.
Nandoid takes a backup of the phone's OS (the one you use every day) as it is right now. It places the backup onto your sdcard under a folder called "nandroid" (where you can take a copy of it and put it on your computer to be safe). So whenever you Nandroid your phone, it's taking a snapshot of how your phone is currently configured (the whole thing) and if you restore from that three weeks from now after doing a bunch of things...it restores to the phone as if you hadn't done anything to it in those three weeks.
So to make an example: if you take a backup of your phone right now (rooted, right?) and then you do a bunch of things to it...then restore from that backup, it's as if you didn't do any of those things you did since the backup (but it will still be rooted since you backed up a rooted phone).
Second Example: If you nandroid your phone when it's running MoDaCo's ROM...when you restore it, it will be running MoDaCo's rom and configured however it was configured then.
I wouldn't worry about trying to get to factory default first...HTC has an official utility that can get you back to the state your phone was in when you first openned it out of the box. (http://forum.xda-developers.com/showthread.php?t=559622)
thecodemonk said:
Ah ok...the recovery image is like a second mini OS you are booting into that has menu options and specializes in updating your phone with a custom ROM, running Nandroid for backups, and enabling you to mount your SDCard to your computer, so installing that doesn't actually do anything to your phone's running OS.
Nandoid takes a backup of the phone's OS (the one you use every day) as it is right now. It places the backup onto your sdcard under a folder called "nandroid" (where you can take a copy of it and put it on your computer to be safe). So whenever you Nandroid your phone, it's taking a snapshot of how your phone is currently configured (the whole thing) and if you restore from that three weeks from now after doing a bunch of things...it restores to the phone as if you hadn't done anything to it in those three weeks.
So to make an example: if you take a backup of your phone right now (rooted, right?) and then you do a bunch of things to it...then restore from that backup, it's as if you didn't do any of those things you did since the backup (but it will still be rooted since you backed up a rooted phone).
Second Example: If you nandroid your phone when it's running MoDaCo's ROM...when you restore it, it will be running MoDaCo's rom and configured however it was configured then.
I wouldn't worry about trying to get to factory default first...HTC has an official utility that can get you back to the state your phone was in when you first openned it out of the box. (http://forum.xda-developers.com/showthread.php?t=559622)
Click to expand...
Click to collapse
Great, this really clarified things.
I love technology but, like most of these things, it's very overwhelming at first.
Ok, so I purchased my Thunderbolt yesterday, and of course, first thing's first. Root.
I am familiar with the OG Droid, and rooted it using the RSDLite method. I am also familiar with using ADB to push/pull files, as well as using apkmanager to modify apks, primarily for themeing purposes, but I do a little bit of XML editing, as well.
I am also familiar with my wife's HTC Incredible, and I have rooted it (Using the UnRevoked method) and flashed a few custom ROMs to it, as well.
I took on the manual rooting instructions for the Thunderbolt, and all went easy peasy, other than being a bit time consuming. I thought I had it all worked out, and was running Plain Jane (flashed using CWM Recovery) and with the recommended baseband/radio (flashed from hBoot).
But I noticed when I left my house (where I was using wi-fi the whole time) that I wasn't getting any 4g/3g/1x service whatsoever. I had cell signal, full bars in fact, but no data transfer.
So, I tried flashing a few different radios, and I just ended up flahing BAMF Sense 3.0 with the mr2 baseband update for gingerbread ROMs.
I still have the same problem. I get cell reception, but no data transfer. I can get momentary data if I tell the software to check for a software update. 3g pops up, it checks for an update, and when it is done, 3g goes away and I once again have absolutely no data transfer. Can't surf the web, or use any apk that requires data.
Anybody have any pointers? I have made sure that the mobile network option is checked in the settings. Aside from that, I have no clue where to begin.
Any help is greatly appreciated! TIA!
Only thing I can think of is the radio. I'm using the .627 radio from the inj3cttheory rom post in dev section.
http://forum.xda-developers.com/showthread.php?t=1155986
Hi, and welcome to the tbot community!
a few quick questions,
prior to flashing did you check MD5 sums on both the radio and rom?
and did you delete the PG05IMG.zip file you flashed during the rooting process from your sdcard?
also this may sound like overkill but did you wipe everything (data/cache/dalvik/bat-stats) 3 times?
i would recommend re-downloading both the rom and the radio and check MD5 sums. then put them on your sdcard and make sure their is only one PG05IMG.zip on the root of the sdcard. this next stuff is important; connect phone to your computer and verify that adb recognizes your device. then reboot into recovery and wipe data/cache/dalvik/bat-stats 3 times each. and after that re-flash the rom first, let it do its thing as normal. after the rom is installed do not reboot just stay in recovery. at this time you need to use adb to reboot into the bootloader to flash the radio. after that just reboot like normal
Sent from me, using this app on this thing.
blazednova said:
Hi, and welcome to the tbot community!
a few quick questions,
prior to flashing did you check MD5 sums on both the radio and rom?
and did you delete the PG05IMG.zip file you flashed during the rooting process from your sdcard?
also this may sound like overkill but did you wipe everything (data/cache/dalvik/bat-stats) 3 times?
i would recommend re-downloading both the rom and the radio and check MD5 sums. then put them on your sdcard and make sure their is only one PG05IMG.zip on the root of the sdcard. this next stuff is important; connect phone to your computer and verify that adb recognizes your device. then reboot into recovery and wipe data/cache/dalvik/bat-stats 3 times each. and after that re-flash the rom first, let it do its thing as normal. after the rom is installed do not reboot just stay in recovery. at this time you need to use adb to reboot into the bootloader to flash the radio. after that just reboot like normal
Click to expand...
Click to collapse
Thanks for taking the time to write up your response.
To answer a few of your questions, I did check the MD5 for both the radio and the ROM, and found them both to match.
I did wipe thoroughly, at least 3 times, in fact I went so far as to go into the "Mounts" section of CWM Recovery, and I wiped everything (Data, Cache, System...) from there as well (save it be for the SDCard).
What I did NOT do, however, is ensure that the phone rebooted directly to the bootloader. Instead, I selected "reboot system now" from recovery, and just tried to catch the boot cycle to put it into the bootloader, but that failed.
I will re-wipe everything, and re-install the ROM, and this time I will make sure to reboot using adb directly into the bootloader and see how things go from there.
Thanks for the pointers. I will report back once I finish.
If that doesn't do it, I suppose I'll have to try some different radios...
EDIT: I also did delete the radio/baseband update from the SDCard after booting back up.
If that doesn't work it may be your SIM card. There have been reports where SIM cards randomly fail and data is unavailable. I don't think it has anything to with the rooting or flashing process that causes SIM failure. You may have to unroot to get SIM replacement though.
Sent from my ADR6400L using Tapatalk
OK, I went through the entire process over again, this time ensuring that I rebooted to the bootloader immediately after installing the ROM and letting it install the mr2 radio/baseband.
Results = no love.
Still no 4g/3g/1x.
I am now contemplating going completely back to stock to see if things work in stock form, and if they don't, then I suppose the sim card may be the issue.
OK, quick update. After little contemplation, I decided that reverting back to stock-unrooted was the most logical next step to take. I followed the steps outlined in the following thread: http://forum.xda-developers.com/showthread.php?t=1009423
I only flashed the 1st file (PG05IMG_MR1_no_hboot.zip), and left the bootloader alone. So, as far as I understand, I still have an unlocked, s-off bootloader.
I now have data back.
My next question is, am I able to gain root on the software that is currently on the phone (1.13.605.7) without having to do any downgrades? Or are the exploits only functional on an older/downgraded build?
And my other question is, are there any ROMs in an RUU format that I can simply flash from my bootloader since it's still unlocked with s-off?
Success!
After reverting back to stock, I decided to attempt the rooting process again. Took the exact same steps as the first time, only this time I made sure I allowed the data connection to connect between each downgrade/upgrade/reboot before continuing on with the next step. I'm not sure if that's what made the difference, but it really is the only thing I changed. I didn't redownload any of the files. Simply used the same ones I used previously.
Anyway, I hope this thread serves as an aid to anyone else that might run into this issue.
Thanks for all the suggestions and help.
Congrats! Now get to flashing some awesome ROMs!
Sent from my ADR6400L using Tapatalk
MrHawaii said:
Congrats! Now get to flashing some awesome ROMs!
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Done, and done. Currently running das BAMF RC4.9 with the MR2 radio. So far, running awesome!
I am novice when it comes to flashing, rooting, SBFing, etc. I spent endless hours trying to figure out how to get my rooted VZ Froyo to GB. Finally I found a great download that allowed me to boot from a CD on my computer and flash the SBF back to my phone. It worked great I didn't even have to wipe the cache. The phone updated and GB was running. I got it rooted and thought all was going well. Now the only reason I root is to run wireless tether, here is where things went awry.
I find out that it is a big hassle to get tethering to work on GB, thanks Google. So i decide to try and revert back to Froyo. I use the same CD method that worked before, but this time it gets stuck in boot loop. Now I have to wipe the cache and lose all my settings and apps. Finally I get it all back together, minus many apps, I will have to remember them as I go along and re install them. All is all a serious pain in my ass, but a good learning experience.
Now, I wanted to ask a question about Bootstrapper backups. After the SBF and wipe, I rooted again and added Bootstrapper. Then I noticed that some of my backups where still there, (presumable on the SD card). So I tried to load on but it didn't work and the phone got stuck on the Moto icon boot. At this point I thought I had bricked it, but was able to do the CD SBF thing again and just start from scratch. Would there be anyway I could restore one of my backups successfully.
Use Advanced recovery and only restore /data.
Can you tell me what application you used for installing GB? Mine won't update and I don't care that much about tethering.
There's no “application” like that. There's OTA update that can be installed either automatically or via the stock Recovery. You must have your /system FS intact, however. z4root is OK, Droid 2 Bootstrap Recovery isn't. Removing CWM was discussed multiple times, google for “logwrapper.bin” or something like that.
#1 a backup from gb won't work with froyo & vice versa.
#2 tethering is NOT a problem on gb. (After rooting) Just use "open garden" free in market.
#3 I think I know which cd program you are using, it does not install the official ota but a rooted leak (I could be wrong)
There are guides on how to sbf (reset to factory out of box).
And there are guides on rooting and roming
---Here is one ---> http://rootzwiki.com/index.php?/topic/4922-CM7-for-Droid2-Global-User's-Thread#entry113470
Remember, read,read,read... know how to sbf and have a plan for when things DO go wrong.
Droid2 Global CM4D2G-GB-20111217 ***CM7 RevNumbers Kang***
Hi, i've been a noob-lurker at this forum since joining the android community in december, but this is my first post so i'd like to start off by saying hello to everyone. As i mentioned before, my knowledge of this OS is fairly limited, so i may occasionally need for things to be a little dumbed down for me to understand.
That all being said, i recently decided to try flashing the Eagle Blood ROM (a T-Mobile based ROM) on my ATT skyrocket using CWM. The process was completed without my phone being connected to my computer, as i decided to flash a ROM available through CWM itself.
Before i flashed the ROM, the phone was rooted, had superuser, Titanium backup, etc. I believe CWM had a fairly recent backup of all my stuff as well. Once the phone booted into the new ROM, i noticed that i had none of my apps present, none of my data (contacts, messages, pictures, etc), was no longer rooted, and could no longer connect to the data network (my internet will not run without wifi). I do remember that at some point in the reboot process the log showed that it had not recognized my external SD card. I'm not sure but it might be that all my apps were on the card and none of the info loaded because of that. Additionally, because i am running on a mac and have not yet been able to reliably connect my phone to the computer, i do not have any of the more valuable data stored there either.
Essentially i'd like to know if i can recover any or all of the data (either through finding some backup buried in the system) or through pulling the contacts, etc. from the google cloud i assume they are in, and then lastly if someone could point to what exactly i did wrong in the process -- it would be nice to continue flashing ROMs and what not. If i left out any important pieces of information, please let me know.
Thank you so much!
Restore your backup. And ya, you either wiped data before flash or the rom did it for you. You can backup apps+data in tibu but you have to restore them after flash. That will restore app data. Not att data. Chances are your T-Mobile rom had T-Mobile apn's...ect. try the T-Mobile conversion zip. Its in the skyrocket dev section.
Sent from my SAMSUNG-SGH-I727 using xda premium
I'm not sure where i would find those backups -- they were all on the apps themselves and (unless titanium or CWM automatically pushes the backups to another server). Both of those are not on the phone any more (or at least not in the application folder).
I will look into the T mobile conversion, that should be a good first step.
And, a quick update, all my pictures are still on the phone. Contacts, etc. are still missing.
Did youake a cwm backup before flashing?
Sent from my SAMSUNG-SGH-I727 using xda premium
Yes and no. I downloaded CWM a while back and decided to make a backup right off the bat. Functionally speaking it would have all my stuff on it, but i also did not understand flashing recovery mode at that point, so i'm not sure it would have worked.
But no, not right before i flashed the ROM
Boot into recovery, go to backup and restore, go to restore. See if there is a file available. I'm kinda confused. Did you or didn't you make a cwm backup?
Sent from my SAMSUNG-SGH-I727 using xda premium
am.rawr said:
Hi, i've been a noob-lurker at this forum since joining the android community in december, but this is my first post so i'd like to start off by saying hello to everyone. As i mentioned before, my knowledge of this OS is fairly limited, so i may occasionally need for things to be a little dumbed down for me to understand.
That all being said, i recently decided to try flashing the Eagle Blood ROM (a T-Mobile based ROM) on my ATT skyrocket using CWM. The process was completed without my phone being connected to my computer, as i decided to flash a ROM available through CWM itself.
Before i flashed the ROM, the phone was rooted, had superuser, Titanium backup, etc. I believe CWM had a fairly recent backup of all my stuff as well. Once the phone booted into the new ROM, i noticed that i had none of my apps present, none of my data (contacts, messages, pictures, etc), was no longer rooted, and could no longer connect to the data network (my internet will not run without wifi). I do remember that at some point in the reboot process the log showed that it had not recognized my external SD card. I'm not sure but it might be that all my apps were on the card and none of the info loaded because of that. Additionally, because i am running on a mac and have not yet been able to reliably connect my phone to the computer, i do not have any of the more valuable data stored there either.
Essentially i'd like to know if i can recover any or all of the data (either through finding some backup buried in the system) or through pulling the contacts, etc. from the google cloud i assume they are in, and then lastly if someone could point to what exactly i did wrong in the process -- it would be nice to continue flashing ROMs and what not. If i left out any important pieces of information, please let me know.
Thank you so much!
Click to expand...
Click to collapse
When flashing any TMobile t989 ROM, you must also flash the conversion package as well. It contains the kernel and other files that are required. You can find that conversion package from the t989 dev thread. I strongly recommend performing a full wipe, flash the rom again, then flash conversion package BEFORE you reboot.
You may also need to manually input the correct APN settings.
Sent from my SAMSUNG-SGH-I727 using XDA Premium App
I just tried booting into recovery: the phone powers down and then just buzzes in 3 second intervals until i let go.
The only thing about performing a full wipe and working from there is that it would need a computer, which i am still currently unable to connect the phone with...
am.rawr said:
I just tried booting into recovery: the phone powers down and then just buzzes in 3 second intervals until i let go.
The only thing about performing a full wipe and working from there is that it would need a computer, which i am still currently unable to connect the phone with...
Click to expand...
Click to collapse
With the Skyrocket, press and hold volume +&- and power, once you see the Samsung splash, then release the power button (continue holding volume) m, wait a few seconds and it should load recovery. You don't need a computer to perform a full wipe. Ypu can download Darkside Super Wipe Script. That will completly wipe your phone (won't wipe sd or emmc memory).
Sent from my SAMSUNG-SGH-I727 using XDA Premium App
Okay, i was able to boot into recovery (sorry about the confusion, for a second i forgot that it was possible to get into recovery outside of the app).
I found the backup i had made a while back (accidentally made another, current backup while doing this) and have tried loading it twice, but it throws up "Error while formatting /system!"
sorry, a closer yields the full text as...
"E:format_volume: no MTD partition "/dev/block/mmcblk0p24"
Error while formatting /systems!"
Just tried to boot back into the system and now i have a message saying
"warning
A custom OS can cause critical problems in phone and installed applications"
i can either boot into the custom anyways or "restart phone".
Restart? Or would that mean i would have to get it reactivated?
what i did so far. used odin to flash h1 baseband rom so i can root. rooted with cydia. downloaded e-z recovery. installed cwm. that didnt read my storage and nothing in it would work. installed twrp with e-z recovery. same problem.(edit: when I got to twrp it said "no o.s. found" so I then had to reboot into download mode and flashed the stock rom) Then downloaded android terminal emulator. downloaded cwm and installed by typing in the commands. got into cwm and made a backup. wiped data, cache, dalvik. tried to install "cm-11-20150831-SNAPSHOT-XNG3CAO3FN-d2lte". it installed but went into a boot loop and would end up back at cwm every time. wiped data, factory reset, restored backup. tried again, same thing, restored again. tried installing "cm-12.1-20150915-NIGHTLY-d2vzw" this time. it got stuck saying "patching system image unconditionally.....". wiped data, restored stock, tried again this time with "cm-10.0.0-d2vzw". it didnt even install. now im restoring again to stock.
the reason im trying vzw roms also is because i have a verizon note 2 on straight talk and was gonna try to use that sim card in my s3.
http://forum.xda-developers.com/galaxy-s3-verizon/help/straight-talk-sch-s986c-t3036314/page3
^^this thread has some info about it but im new here and havent found anything else about it. before i try getting it to work with my verizon cdma sim card i at least would like to just get cyanogenmod working on my s3.
am i using the wrong roms? is this in the right forum?
thanks
now supersu is gone from my phone. i just installed es file explorer and checked allow root permissions and supersu didnt even come up. i uninstalled and reinstalled in the play store also and nothing happened
cory733 said:
now supersu is gone from my phone. i just installed es file explorer and checked allow root permissions and supersu didnt even come up. i uninstalled and reinstalled in the play store also and nothing happened
Click to expand...
Click to collapse
You need the d2vzw ROMs, if you are using lollipop then you need to go to developer options and turn on root access, set it to apps and adb.
There is a TWRP made specifically for d2tfnvzw, it has our source code in it, the other d2vzw TWRPs don't mount our devices correctly.
I worked with a dev at OctOS to get our device fully supported, all their d2vzw stiff has our code in it now. I can link you to the TWRP if you have trouble finding it.
I know pretty much whatever you need on this phone, just hit me up with anything you need help with and I'll get you straight.
Have you backed up your IMEI in terminal emulator yet, I recommend doing so because this phone has a habit of losing IMEI when flashing back and forth between ROMs, flashing stock tar won't fix this.
Droidriven said:
You need the d2vzw ROMs, if you are using lollipop then you need to go to developer options and turn on root access, set it to apps and adb.
There is a TWRP made specifically for d2tfnvzw, it has our source code in it, the other d2vzw TWRPs don't mou t our devices correctly.
I worked with a dev at OctOS to get our device fully supported, all their d2vzw stiff has our code in it now. I can link you to the TWRP if you have trouble finding it.
I know pretty much whatever you need on this phone, just hit me up with anything you need help with and I'll get you straight.
Have you backed up your IMEI in terminal emulator yet, I recommend doing so because this phone has a habit of losing IMEI when flashing back and forth between ROMs, flashing stock tar won't fix this.
Click to expand...
Click to collapse
hey droid thanks for getting back to me. i cant find the twrp for the d2tfnvzw, just the d2vzw. were you saying that i could use the d2vzw because it has the straight talk code in it or i need the exact straight talk version? yes if you have the link i would appreciate it because i didnt see anything except the d2vzw. how would i install it with cwm already on there? would it just overwrite it?
i had no idea about backing up imei until today. but this is already after installing the h1 rom and getting it rooted. then trying cm 4 different times. if my info was lost, would it just be blank? or would it have different numbers that are just useless to me. because its still there but i didnt write down the numbers before i did all this. but anyway today i think thats what i did, ive done so much with this phone that i cant even remember exactly, but i opened up terminal emulator, typed in something involving rebootnv/ something and it rebooted then i copied the efs folder from my phone and put a copy on my computer.
i just did another restore of the first backup i made. supersu is still gone. i downloaded my android tools and it says that supersu was still an enabled app. i never hid it or disabled it in any way that im aware of. i tried uninstall and reinstall from play store and the terminal emulator command and the #*#* numbers on the phone dialer. nothing. es file manager also got root access without supersu coming up.
also it seems like its not getting 3g at all. usually it goes from 3g to just 2 bars or one bar where i live. but now its just steady at two bars. even with wifi off. does 3g stop showing up if the phone is not in service? i dont remember.
btw this phone has android 4.1.2
cory733 said:
hey droid thanks for getting back to me. i cant find the twrp for the d2tfnvzw, just the d2vzw. were you saying that i could use the d2vzw because it has the straight talk code in it or i need the exact straight talk version? yes if you have the link i would appreciate it because i didnt see anything except the d2vzw. how would i install it with cwm already on there? would it just overwrite it?
i had no idea about backing up imei until today. but this is already after installing the h1 rom and getting it rooted. then trying cm 4 different times. if my info was lost, would it just be blank? or would it have different numbers that are just useless to me. because its still there but i didnt write down the numbers before i did all this. but anyway today i think thats what i did, ive done so much with this phone that i cant even remember exactly, but i opened up terminal emulator, typed in something involving rebootnv/ something and it rebooted then i copied the efs folder from my phone and put a copy on my computer.
i just did another restore of the first backup i made. supersu is still gone. i downloaded my android tools and it says that supersu was still an enabled app. i never hid it or disabled it in any way that im aware of. i tried uninstall and reinstall from play store and the terminal emulator command and the #*#* numbers on the phone dialer. nothing. es file manager also got root access without supersu coming up.
also it seems like its not getting 3g at all. usually it goes from 3g to just 2 bars or one bar where i live. but now its just steady at two bars. even with wifi off. does 3g stop showing up if the phone is not in service? i dont remember.
btw this phone has android 4.1.2
Click to expand...
Click to collapse
If you want a working TWRP then you'll need the d2tfnvzw version, any d2vzw or d2lte ROM should work fine for you.
If you lose IMEI it won't show in settings. The reboot nvbackup that you did in terminal emulator was the IMEI backup I mentioned, it sounds like you did it correctly, if it gets wiped out for whatever reason then you can restore it by typing "reboot nvrestore", it is saved in a safe place on internal that won't get wiped out between flashes and wipes unless you format internal memory, it will be erased if you do that. As long as the only format options you use are to format system and data partitions then you won't have to worry about losing the NV backup, don't format anything other than system and data, do not format internal SD and you'll be fine. If you ever have to restore the NV backup then you'll have to create a new one like the first time because restoring it erases it from where the backup was kept, to stay backed up after restoring you need to make another.
SuperSU won't show as an app, its built in to system settings.
Did you enable root access in system settings>developer options? It has to be set to " apps and adb" or the device will act like it isn't rooted. When you flashed in CWM and rebooted it should have prompted you to "fix root", select yes if it does.
Yes, the 3G disappears when you don't have service and need to renew time on the device.
Here is the TWRP for d2tfnvzw
https://plus.google.com/+DonaldHoskins/posts/FLdc2CkSHRu
Flash it in CWM then go to the advanced options in CWM and select "reboot to recovery" this will boot you straight from CWM into TWRP, then make your backup and youll keep TWRP and wont need CWM, it would be a good idea to restore your stock nandroid in CWM and boot into it then boot back to CWM then flash the TWRP then reboot into it then make a nandroid of your stock in TWRP because TWRP will not restore CWM nandroids, doing what I just instructed allows you to keep TWRP and a stock nandroid that you can actually restore. After getting TWRP and a stock nandroid in TWRP you can delete the CWM backup from your internal SD if you aren't going back to CWM at any time, you won't need it if you do as I instructed.
Droidriven said:
You need the d2vzw ROMs, if you are using lollipop then you need to go to developer options and turn on root access, set it to apps and adb.
There is a TWRP made specifically for d2tfnvzw, it has our source code in it, the other d2vzw TWRPs don't mou t our devices correctly.
I worked with a dev at OctOS to get our device fully supported, all their d2vzw stiff has our code in it now. I can link you to the TWRP if you have trouble finding it.
I know pretty much whatever you need on this phone, just hit me up with anything you need help with and I'll get you straight.
Have you backed up your IMEI in terminal emulator yet, I recommend doing so because this phone has a habit of losing IMEI when flashing back and forth between ROMs, flashing stock tar won't fix this.
Click to expand...
Click to collapse
Droidriven said:
If you want a working TWRP then you'll need the d2tfnvzw version, any d2vzw or d2lte ROM should work fine for you.
If you lose IMEI it won't show in settings. The reboot nvbackup that you did in terminal emulator was the IMEI backup I mentioned, it sounds like you did it correctly, if it gets wiped out for whatever reason then you can restore it by typing "reboot nvrestore", it is saved in a safe place on internal that won't get wiped out between flashes and wipes unless you format internal memory, it will be erased if you do that. As long as the only format options you use are to format system and data partitions then you won't have to worry about losing the NV backup, don't format anything other than system and data, do not format internal SD and you'll be fine. If you ever have to restore the NV backup then you'll have to create a new one like the first time because restoring it erases it from where the backup was kept, to stay backed up after restoring you need to make another.
SuperSU won't show as an app, its built in to system settings.
Did you enable root access in system settings>developer options? It has to be set to " apps and adb" or the device will act like it isn't rooted. When you flashed in CWM and rebooted it should have prompted you to "fix root", select yes if it does.
Yes, the 3G disappears when you don't have service and need to renew time on the device.
Here is the TWRP for d2tfnvzw
https://plus.google.com/+DonaldHoskins/posts/FLdc2CkSHRu
Flash it in CWM then go to the advanced options in CWM and select "reboot to recovery" this will boot you straight from CWM into TWRP, then make your backup and youll keep TWRP and wont need CWM, it would be a good idea to restore your stock nandroid in CWM and boot into it then boot back to CWM then flash the TWRP then reboot into it then make a nandroid of your stock in TWRP because TWRP will not restore CWM nandroids, doing what I just instructed allows you to keep TWRP and a stock nandroid that you can actually restore. After getting TWRP and a stock nandroid in TWRP you can delete the CWM backup from your internal SD if you aren't going back to CWM at any time, you won't need it if you do as I instructed.
Click to expand...
Click to collapse
thanks for the link and info, ill work on that next. this phone actually never had an IMEI. not even behind the battery. it just has a 2 line section called MEID that shows a Dec and a Hex number. i give one or both of these numbers to straight talk when they activate the phone. (had this phone activated,deactivated and reactivated a couple times)
i had supersu as an app because i installed it from the play store. it was showing before and i use it on my note 2. but now the pop up for granting superuser permission isnt even coming up.
since i cant just switch the sim cards between my two phones, is it even worth putting a verizon rom on my s3? i would still have to call straight talk and have it switched anyway. or is that because the d2lte roms dont work for mms.. is that the only reason to use the verizon roms instead? you said before in pm that if i put my note 2s sim in my s3(after installing verizon rom) that i would have to press *228 to reset the prl. and that might mess it up for the note 2 that im using. would i just have to repeat dialing *228 in my note 2 if i switched the sim back to that one? also i believe you said in a different thread that theres no way to get 4g on these phones? that was also one of my reasons for wanting to put a verizon rom on the s3. basically this phone is a backup that has just become a learning experiment now
cory733 said:
thanks for the link and info, ill work on that next. this phone actually never had an IMEI. not even behind the battery. it just has a 2 line section called MEID that shows a Dec and a Hex number. i give one or both of these numbers to straight talk when they activate the phone. (had this phone activated,deactivated and reactivated a couple times)
i had supersu as an app because i installed it from the play store. it was showing before and i use it on my note 2. but now the pop up for granting superuser permission isnt even coming up.
since i cant just switch the sim cards between my two phones, is it even worth putting a verizon rom on my s3? i would still have to call straight talk and have it switched anyway. or is that because the d2lte roms dont work for mms.. is that the only reason to use the verizon roms instead? you said before in pm that if i put my note 2s sim in my s3(after installing verizon rom) that i would have to press *228 to reset the prl. and that might mess it up for the note 2 that im using. would i just have to repeat dialing *228 in my note 2 if i switched the sim back to that one? also i believe you said in a different thread that theres no way to get 4g on these phones? that was also one of my reasons for wanting to put a verizon rom on the s3. basically this phone is a backup that has just become a learning experiment now
Click to expand...
Click to collapse
I don't know what you've got going on with superSU, does root checker verify you are rooted? If you have root access as normal and everything works then I wouldn't worry about it as long as it works.
Your IMEI should show in system settings>about phone. IMEI has several names: ESN, IMEI and a few more, they are all the same thing, it's what the network uses to identify your device as that particular device and not another. That number is what registers on the network, without it the device is useless, it won't even work on WiFi if its NV bricked.
Dialing *228 on a Verizon SIM ruins it for Verizon, from what I know, it won't work for Verizon after that no matter what you dial. Using the SIM on the ST S3 is only to get signal and data, it doesn't have to be activated by any process, just inserted and OTA programmed in the device. Actually any CDMA SIM works but the Verizon 4G specifically gets the stock MMS working, it even corrects MMS issues on non rooted stock ST S3. The 4G SIM is needed to get the ROMs working because the ROMs are actually built for the Verizon S3 which is a 4G device that requires 4G SIM, that is how Verizon regulates their 4G data, this makes our device require the SIM when running Verizon ROMs, even the d2lte ROMs require SIM because they are built for LTE(4G) devices, hence d2 "lte". The ROMs have to follow their programming, their programming says they must have SIM so a SIM must be used regardless of what the device is.
The 4G was hardware disabled in the device, it can't be re-enabled. This device actually has the Verizon S3's motherboard in it even though it says it is an SCH-S968C, if you open it up and look inside you'll see SCH-I535 stamped in more than one place on the hardware pieces. Its a rebranded Verizon S3 basically with 4G disabled.
Is any of this making any sense yet?
I have a thread that I ran across where a guy used his active Verizon SIM in a ST S3 by going to his verizon user account online and entering the phone info, this is not really a legit way to do it, the network is fooled into thinking one device is the other without the second device actually being legitimately activated on the Verizon network, this is a shady practice and isn't recommended because if the network catches on they'll kill you ESN(IMEI) and the device will be useless and un-repairable. It can be done but isn't worth the risk, I will tell you how to do this, its against the rules on XDA, if you do so then do not come posting here about it no matter what issues you are having, the practice is frowned on around here and most won't help you with it if they are serious about XDA.
Droidriven said:
I don't know what you've got going on with superSU, does root checker verify you are rooted? If you have root access as normal and everything works then I wouldn't worry about it as long as it works.
Your IMEI should show in system settings>about phone. IMEI has several names: ESN, IMEI and a few more, they are all the same thing, it's what the network uses to identify your device as that particular device and not another. That number is what registers on the network, without it the device is useless, it won't even work on WiFi if its NV bricked.
Dialing *228 on a Verizon SIM ruins it for Verizon, from what I know, it won't work for Verizon after that no matter what you dial. Using the SIM on the ST S3 is only to get signal and data, it doesn't have to be activated by any process, just inserted and OTA programmed in the device. Actually any CDMA SIM works but the Verizon 4G specifically gets the stock MMS working, it even corrects MMS issues on non rooted stock ST S3. The 4G SIM is needed to get the ROMs working because the ROMs are actually built for the Verizon S3 which is a 4G device that requires 4G SIM, that is how Verizon regulates their 4G data, this makes our device require the SIM when running Verizon ROMs, even the d2lte ROMs require SIM because they are built for LTE(4G) devices, hence d2 "lte". The ROMs have to follow their programming, their programming says they must have SIM so a SIM must be used regardless of what the device is.
The 4G was hardware disabled in the device, it can't be re-enabled. This device actually has the Verizon S3's motherboard in it even though it says it is an SCH-S968C, if you open it up and look inside you'll see SCH-I535 stamped in more than one place on the hardware pieces. Its a rebranded Verizon S3 basically with 4G disabled.
Is any of this making any sense yet?
I have a thread that I ran across where a guy used his active Verizon SIM in a ST S3 by going to his verizon user account online and entering the phone info, this is not really a legit way to do it, the network is fooled into thinking one device is the other without the second device actually being legitimately activated on the Verizon network, this is a shady practice and isn't recommended because if the network catches on they'll kill you ESN(IMEI) and the device will be useless and un-repairable. It can be done but isn't worth the risk, I will tell you how to do this, its against the rules on XDA, if you do so then do not come posting here about it no matter what issues you are having, the practice is frowned on around here and most won't help you with it if they are serious about XDA.
Click to expand...
Click to collapse
yeah i dont use verizon its just a verizon phone on straight talk.
my copy of the stock rom is this one that im sure youve seen before
COMBINATION_S968CUDUAMH1_S968CTFNAMH1_1304014_REV09_user_low_ship.tar.md5
since i couldnt make a copy of my actual stock on my non rooted h2 stock rom.
so youre saying to revert to this before i install twrp? i would install it as a zip and not as a restore correct?
cory733 said:
yeah i dont use verizon its just a verizon phone on straight talk.
my copy of the stock rom is this one that im sure youve seen before
COMBINATION_S968CUDUAMH1_S968CTFNAMH1_1304014_REV09_user_low_ship.tar.md5
since i couldnt make a copy of my actual stock on my non rooted h2 stock rom.
so youre saying to revert to this before i install twrp? i would install it as a zip and not as a restore correct?
Click to expand...
Click to collapse
Restore your stock nandroid in CWM, then reboot into system normally, then boot back to CWM and flash the TWRP .zip, then go to advanced options in CWM and select "reboot recovery" it will boot straight to TWRP then you make a nandroid of your stock in TWRP then you don't need CWM or the stock nandroid that was created in CWM.
I'm just trying to explain how to get TWRP and have a stock nandroid in TWRP because the nandroid made in CWM won't work in TWRP, if you're gonna run and keep TWRP then you'll need a stock nandroid to use in TWRP if you ever need it. Otherwise you would have to go back to CWM to restore the stock nandroid that you made in CWM. Doing what I'm saying eliminates the hassle of going back and forth between CWM and TWRP.
If you're already on stock then you don't need to restore the nandroid in CWM, you just need to flash TWRP .zip then reboot to it from within CWM and make a TWRP nandroid and do away with CWM and the nandroid you created in it, your CWM nandroid van be found on your extsd in Clockworkmod/backups folder, just delete the entire Clockworkmod folder.
Droidriven said:
Restore your stock nandroid in CWM, then reboot into system normally, then boot back to CWM and flash the TWRP .zip, then go to advanced options in CWM and select "reboot recovery" it will boot straight to TWRP then you make a nandroid of your stock in TWRP then you don't need CWM or the stock nandroid that was created in CWM.
I'm just trying to explain how to get TWRP and have a stock nandroid in TWRP because the nandroid made in CWM won't work in TWRP, if you're gonna run and keep TWRP then you'll need a stock nandroid to use in TWRP if you ever need it. Otherwise you would have to go back to CWM to restore the stock nandroid that you made in CWM. Doing what I'm saying eliminates the hassle of going back and forth between CWM and TWRP.
If you're already on stock then you don't need to restore the nandroid in CWM, you just need to flash TWRP .zip then reboot to it from within CWM and make a TWRP nandroid and do away with CWM and the nandroid you created in it, your CWM nandroid van be found on your extsd in Clockworkmod/backups folder, just delete the entire Clockworkmod folder.
Click to expand...
Click to collapse
kinda forgot about this project for a while but decided to finish it. i installed the version of TWRP you showed me and it and cyanogenmod installed just fine this time. i actually just installed this twrp from twrp itself. tried putting the sim from my note 2 in my s3 just to try. it didnt work. i didnt dial *288 or anything. but i ordered another sim. will see if everything works when i get the sim.
thanks for your help
maybe spoke too soon. now its not letting me boot into twrp for some reason. even though i already did before and made a backup. i get the blue letters up top saying its booting to recovery but then it just skips it
edit: works when enabling advanced reboot options and rebooting to recovery from phone
cory733 said:
maybe spoke too soon. now its not letting me boot into twrp for some reason. even though i already did before and made a backup. i get the blue letters up top saying its booting to recovery but then it just skips it
edit: works when enabling advanced reboot options and rebooting to recovery from phone
Click to expand...
Click to collapse
Hmm, sounds fishy. Try going back to the TWRP you already had if it worked fine, why the d2tfnvzw is acting funny I couldn't tell you. When you put the SIM in it the ROM should work without having to do anything, dialing *228 and setting APNs is only to get MMS working and only works with the Verizon 4G LTE SIM that I know of.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
Hmm, sounds fishy. Try going back to the TWRP you already had if it worked fine, why the d2tfnvzw is acting funny I couldn't tell you. When you put the SIM in it the ROM should work without having to do anything, dialing *228 and setting APNs is only to get MMS working and only works with the Verizon 4G LTE SIM that I know of.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
the twrp i had before couldnt install cm correctly for some reason. now that im on cm12 can i still install that twrp?
the rom seems to be working fine, i can still get into everything else without the sim, it just says no sim. With that sim i didnt get service, i got the "welcome to verizon wireless" when trying to make a call. installing apps seems slow.
somehow ive lost root. supersu wont install the binaries either, im gonna try to figure out how to do that with twrp.
cory733 said:
the twrp i had before couldnt install cm correctly for some reason. now that im on cm12 can i still install that twrp?
the rom seems to be working fine, i can still get into everything else without the sim, it just says no sim. With that sim i didnt get service, i got the "welcome to verizon wireless" when trying to make a call. installing apps seems slow.
somehow ive lost root. supersu wont install the binaries either, im gonna try to figure out how to do that with twrp.
Click to expand...
Click to collapse
As for your root being gone, its probably not, you've got to go into developer settings and set root access to "apps and adb", do that and verify whether you have root after that, also get ES file explorer and set your mount permissions to R/W
If the SIM is a Verizon SIM it should work.
I recommend flashing the newest OctOS d2vzw CM12 has always been too buggy in my opinion, OctOS is super stable, its the best ROM out if all the d2vzw ROMs. The SIM will probably work with OctOS, myself and hundreds of others have been using it with no issues.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
As for your root being gone, its probably not, you've got to go into developer settings and set root access to "apps and adb", do that and verify whether you have root after that, also get ES file explorer and set your mount permissions to R/W
If the SIM is a Verizon SIM it should work.
I recommend flashing the newest OctOS d2vzw CM12 has always been too buggy in my opinion, OctOS is super stable, its the best ROM out if all the d2vzw ROMs. The SIM will probably work with OctOS, myself and hundreds of others have been using it with no issues.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
ok cool got root, you were right, the root access setting was set to disabled. the sim is a straight talk CDMA for verizon. its from the bring your own phone sim card kit that has sims for every carrier. i didnt want to try *288 since you said it could ruin it for my Note 2. but another one is on the way theyre $1.07 from walmarts website.
do you have a link for octos? its based off cm12? im also trying to get an app called drivedroid to work since i cant do much with my note 2's useless locked bootloader. google search for OctOs is bringing me to liquidsmooth.
cory733 said:
ok cool got root, you were right, the root access setting was set to disabled. the sim is a straight talk CDMA for verizon. its from the bring your own phone sim card kit that has sims for every carrier. i didnt want to try *288 since you said it could ruin it for my Note 2. but another one is on the way theyre $1.07 from walmarts website.
do you have a link for octos? its based off cm12? im also trying to get an app called drivedroid to work since i cant do much with my note 2's useless locked bootloader. google search for OctOs is bringing me to liquidsmooth.
Click to expand...
Click to collapse
teamoctos.com ,find the download page and get the newest d2vzw.
I'm not sure that the straight talk SIM will work like the actual Verizon SIM does, in the year that I've been following development on this device I've seen no posts that say the ST BYOP 4G SIM works. I recommend an actual Verizon one, they are only $2-4 on eBay, that's cheaper than the ST SIM and guaranteed to work.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
teamoctos.com ,find the download page and get the newest d2vzw.
I'm not sure that the straight talk SIM will work like the actual Verizon SIM does, in the year that I've been following development on this device I've seen no posts that say the ST BYOP 4G SIM works. I recommend an actual Verizon one, they are only $2-4 on eBay, that's cheaper than the ST SIM and guaranteed to work.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
should i try switching TWRP's before installing this rom?
cory733 said:
should i try switching TWRP's before installing this rom?
Click to expand...
Click to collapse
No, try the d2tfnvzw one first
Sent from my SCH-I535 using Tapatalk
Droidriven said:
No, try the d2tfnvzw one first
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
ok im on OctOs now. stayed with the same TWRP d2tfnvzw version. Same thing with the sim. "welcome to verizon wireless, your mobile number is either not active, or invalid" does *228 do anything besides getting mms to work?
edit: the signal bar icon has a ! in it and when i click on it it says Verizon Wireless 2 GB warning
cory733 said:
ok im on OctOs now. stayed with the same TWRP d2tfnvzw version. Same thing with the sim. "welcome to verizon wireless, your mobile number is either not active, or invalid" does *228 do anything besides getting mms to work?
Click to expand...
Click to collapse
It is supposed to auto program the SIM. I'm not sure it will work on the ST SIM, I know it works for the Verizon SIM, don't try it on the ST SIM, I might fry it and make it useless.
Verify you still have IME, has the phone itself been activated on straight talk, your IMEI has to be registered and activated on the straight talk network. Are you showing any signal bars or the 3G symbol?
Sent from my SCH-I535 using Tapatalk