Related
I would like to install CM7 from http://forum.cyanogenmod.com/topic/...f0000dangerous-test-releasecolor/#entry148754
But to restore back to Froyo, it says to use ODIN to do a restore with the re-partition option. I thought I read that the re-part option would brick a SGH-I896.
Is this correct? or am I just imagining it.
In other words, does the repartition option work properly on Rogers SGH-I896?
Thanks for any answers you guys give.
You want to run an experimental beta ROM for an i897 phone on your i896? Trying to find the fastest way to brick your phone?
Miami_Son said:
You want to run an experimental beta ROM for an i897 phone on your i896? Trying to find the fastest way to brick your phone?
Click to expand...
Click to collapse
I do not believe it will brick the phone. The board is an I897 with slight revisions. I was just wondering about the method used to go back to froyo. I am not a complete noob and am not worried about bricking to install the rom. Just going back.
But I do appreciate your input.
DO NOT USE PIT / RE- PARTITION ( the p in PIT is for partition )
i did that and on reboot had an error
E: cant mount dev/dbdata...
was STUCK. only option was to do ONE CLICK ODIN, even after flashing EVERY AVAILABLE rogers stock image, on the net and my own, I CANNOT GET RID OF ATT bootscreen without the cheap hack of replaceing the ATT image with the origninal (still named ATT boot).
the CM7 is still not ready, you will just be going back to what you have now,
WAIT for it to be ready.
Everything I've read on CM7 up to this point is that it is not yet ready for use other than for developers trying to fix its remaining bugs. A number of threads opened up on it over the past week have been almost immediately closed because of the potential to mislead people to try it and end up with bricked phones.
I flashed there and back with no problem. I did not use the re-partition option to install.
Well answered
Trusselo said:
DO NOT USE PIT / RE- PARTITION ( the p in PIT is for partition )
i did that and on reboot had an error
E: cant mount dev/dbdata...
was STUCK. only option was to do ONE CLICK ODIN, even after flashing EVERY AVAILABLE rogers stock image, on the net and my own, I CANNOT GET RID OF ATT bootscreen without the cheap hack of replaceing the ATT image with the origninal (still named ATT boot).
the CM7 is still not ready, you will just be going back to what you have now,
WAIT for it to be ready.
Click to expand...
Click to collapse
Thats what I was afraid of, I didn't want to be stuck with att junk on the phone.
Guess i'll wait a little more, sad to say I can only play with gingerbready on by HTC Dream . for now anyways.
Thanks for the answer
Cm7 is largely stable with some bugs. If you do not read the known issues some funky stuff will happen. Speaking from experience ; ) it is everything the hype says it is. Running since the morning. My one concern is battery but I need to let it cycle a couple of times.
Sent from my Captivate using XDA Premium App
Been running CM7 since late January, and did some of the early dev work on porting it to the Captivate. I have an i896. Trust me, it won't brick it.
To op, there will never be a non-one click revert. CM7 changes the setup of the mtd blocks (basically the nand where the rom is installed), meaning you MUST repartition to go back to a Samsung rom. However, none of the Rogers images contain all of the rom, meaning if you repartition, you will be missing parts of the rom, and will just bootloop/be stuck in recovery.
Tl;dr: If you flash it, and want to revert, you must use one-click, and that won't change, even when it's at "stable".
TheEscapist said:
Been running CM7 since late January, and did some of the early dev work on porting it to the Captivate. I have an i896. Trust me, it won't brick it.
To op, there will never be a non-one click revert. CM7 changes the setup of the mtd blocks (basically the nand where the rom is installed), meaning you MUST repartition to go back to a Samsung rom. However, none of the Rogers images contain all of the rom, meaning if you repartition, you will be missing parts of the rom, and will just bootloop/be stuck in recovery.
Tl;dr: If you flash it, and want to revert, you must use one-click, and that won't change, even when it's at "stable".
Click to expand...
Click to collapse
Best advice, straight from the source. And OP, as was said before, make sure you know what the known issues are. The CM7 thread has a lot of complaints about issues that were already noted and known. If you can live with those, jump in!
Hello Everyone,
I have i896 captivate. I am currently on serendipity 7 and like it. However, I need to go back to stock rogers rom, which I did. The problem is, while booting up the phone, the order of screen animations is:
a. galaxy gt i9000
b. i896
c. rogers.
The phone boots and works fine.
Is there a way to remove the gt i9000 screen. Any advice is most welcome.
Thanks
You would need to reflash the stock rogers bootloaders. Unless you're planning on returning it for warranty repairs or something, I would recommend against it and just live with the i9000 screen.
As a matter of fact, I was planning to return it for repairs. I do have the i896 stock rogers rom, where can i find the bootloader files and how do i flash it. Thanks for the prompt response.
No idea where you'd get the stock i896 bootloaders.. sorry dude :/
I'd imagine they'd come packaged with a leaked stock i896 rom (maybe samfirmware.com?). If you find one that has the bootloaders (you can find them by extracting the rom packages and looking for sbl.bin and boot.bin), make sure you have BOTH sbl.bin and boot.bin, otherwise you'll hard-brick your phone. To flash the bootloaders, just flash the entire leaked rom with odin as usual.
No luck there. Maybe I'll live with this screen and get an upgrade in 2 months. Thanks a lot for your response
http://forum.xda-developers.com/showthread.php?t=979133
i think this is what youre looking for. i suggest 1click odin back to att stock first like the guy states then flash the rogers files
Fantastic, works like a charm. Thanks a lot.
So from reading the threads and searching I was not finding a clear answer for my questions. I recently went from a Gnex to a S3. The Rooting/Bootloader process is obviously different on a Gnex. I understand the Odin process my questions more relate to the specifics that often don't get brought up in guides. Here are my questions.
1. Using the Unlock Bootloader and Root methods in these threads on XDA the only thing really (other then a potential brick) that is concerning is the flash counter. Are you unable to flash beyond a certain amount of counted flashes or is this merely used to identify a "rooted" phone for warranty purposes?(I am aware of triangle away)
2. Restoring to a stock config is a basic as Running Triangle away and the stock ODIN image?
3. The reason I have a SGS3 now is because my Gnex was having constant data drops. Are the radios the same as the Gnex? (I have not experienced them yet in fact perfect 4G everywhere)
4. Are there any pitfalls to SGS3 flashing that I should avoid? (other then flashing a ODIN for another carrier/model)
5. I have noticed that while Facebook indicates a contact sync it doesn't actually sync the picture to the profiles is there a fix?
6. Lastly.. d2vzw I can't seem to get a solid definition of the term in regards to what it is and the context it's being used in the development section. Can you please enlighten me?
Thanks for taking the time to answer my questions. Please the more information the better.
DeadPhoenix said:
So from reading the threads and searching I was not finding a clear answer for my questions. I recently went from a Gnex to a S3. The Rooting/Bootloader process is obviously different on a Gnex. I understand the Odin process my questions more relate to the specifics that often don't get brought up in guides. Here are my questions.
1. Using the Unlock Bootloader and Root methods in these threads on XDA the only thing really (other then a potential brick) that is concerning is the flash counter. Are you unable to flash beyond a certain amount of counted flashes or is this merely used to identify a "rooted" phone for warranty purposes?(I am aware of triangle away)
2. Restoring to a stock config is a basic as Running Triangle away and the stock ODIN image?
3. The reason I have a SGS3 now is because my Gnex was having constant data drops. Are the radios the same as the Gnex? (I have not experienced them yet in fact perfect 4G everywhere)
4. Are there any pitfalls to SGS3 flashing that I should avoid? (other then flashing a ODIN for another carrier/model)
5. I have noticed that while Facebook indicates a contact sync it doesn't actually sync the picture to the profiles is there a fix?
6. Lastly.. d2vzw I can't seem to get a solid definition of the term in regards to what it is and the context it's being used in the development section. Can you please enlighten me?
Thanks for taking the time to answer my questions. Please the more information the better.
Click to expand...
Click to collapse
1) the only thing that trips the flash counter is using ODIN to flash back to stock since it flashes the image files that signifies that you've been tampering with secure images
2) restoring to stock is as easy as just using the root66.tar image (whether it be the jellybean tar leak or the stock ics tar file), running triangle away is only needed when you go past your flash counts
3) TW roms don't really experience much data drops, at least not the ones i ran....now CM10/AOSP/AOKP roms do seem to have data issues but if you're in a strong signal area it shouldn't drop that much, it's just fringe connections that are kinda the issue
4) you should back up your IMEI manually since samsung borked the imei backup partition and it has corrupted images in it which can cause you to lose your IMEI
5) there are apps in the play store that can fix this
6) d2vzw is the definition of our phone, essentially all versions of the galaxy s3 are dubbed d2<carrier label here>, such at d2att, d2spr, d2vzw, so if you flash a d2spr rom to your verizon galaxy s3, you're gonna potentially break something
digitalsynner85 said:
1) the only thing that trips the flash counter is using ODIN to flash back to stock since it flashes the image files that signifies that you've been tampering with secure images
2) restoring to stock is as easy as just using the root66.tar image (whether it be the jellybean tar leak or the stock ics tar file), running triangle away is only needed when you go past your flash counts
3) TW roms don't really experience much data drops, at least not the ones i ran....now CM10/AOSP/AOKP roms do seem to have data issues but if you're in a strong signal area it shouldn't drop that much, it's just fringe connections that are kinda the issue
4) you should back up your IMEI manually since samsung borked the imei backup partition and it has corrupted images in it which can cause you to lose your IMEI
5) there are apps in the play store that can fix this
6) d2vzw is the definition of our phone, essentially all versions of the galaxy s3 are dubbed d2<carrier label here>, such at d2att, d2spr, d2vzw, so if you flash a d2spr rom to your verizon galaxy s3, you're gonna potentially break something
Click to expand...
Click to collapse
Thanks for taking the time to answer my questions. A few follow up questions.
1. You said Triangle away is only for when you go past you flash counts. What is the number in which you exceed the flash count if any?
2. What is the IMEI? I think I have a idea but I rather be fully educated to phrase future questions in context.
3. Are there any Custom roms that include the Facebook sync capability in their frameworks?
4. What is the Aroma Installer. (This is new to me.)
Again thanks for answering my questions.
I was always under the assumption that you only trip you flash counter when flashing non samsung signed images/kernels. Odin'ing back to stock doesnt trip it at all.
x714x said:
I was always under the assumption that you only trip you flash counter when flashing non samsung signed images/kernels. Odin'ing back to stock doesnt trip it at all.
Click to expand...
Click to collapse
So I guess I need more clarification and verification that is the case.
Well you dont really, if you go into download mode it will tell you how many times its been tripped. If it has been tripped you just grab the app Triangle Away and run it to reset it back to 0.
As for IMEI that is a number that is used to identify the device to a network iirc, for GSM phones (LTE in this case). A MEID is a CDMA equivalent. Pretty much like a fancier ESN.
A aroma installer is a installer used to pick options during a install. i.e. If a custom rom gives you a choice of the stock camera and gallery or say the Note 2's, you would check which one you want. Instead of a script just installing everything that you cant pick options. http://www.amarullz.com/articles/img/introducing-aroma-installer.1.jpg
As for facebook the jelly bean OTA that we should get in the near future will have this, it will sync photos and such. If you flash a rom based on it then it will have that.
x714x said:
Well you dont really, if you go into download mode it will tell you how many times its been tripped. If it has been tripped you just grab the app Triangle Away and run it to reset it back to 0.
As for IMEI that is a number that is used to identify the device to a network iirc, for GSM phones (LTE in this case). A MEID is a CDMA equivalent. Pretty much like a fancier ESN.
A aroma installer is a installer used to pick options during a install. i.e. If a custom rom gives you a choice of the stock camera and gallery or say the Note 2's, you would check which one you want. Instead of a script just installing everything that you cant pick options. http://www.amarullz.com/articles/img/introducing-aroma-installer.1.jpg
As for facebook the jelly bean OTA that we should get in the near future will have this, it will sync photos and such. If you flash a rom based on it then it will have that.
Click to expand...
Click to collapse
Very helpful. Thanks
Do we have any ROMs for d2vzw that are note3/S4 ports? Besides the older Hyperdrive?
Sorry of I am in the wrong thread,
very new to this.
Sent from my SCH-I545 powered by T-Mobile Unlimited Plan
suckmikehawk88 said:
Do we have any ROMs for d2vzw that are note3/S4 ports? Besides the older Hyperdrive?
Sorry of I am in the wrong thread,
very new to this.
Sent from my SCH-I545 powered by T-Mobile Unlimited Plan
Click to expand...
Click to collapse
No, hyperdrive wasn't even a port for this phone. Why are you asking? It looks like you're in the wrong forum. You have an s4 phone model.
Sent from my SCH-I535 using Tapatalk 2
suckmikehawk88 said:
Do we have any ROMs for d2vzw that are note3/S4 ports? Besides the older Hyperdrive?
Sorry of I am in the wrong thread,
very new to this.
Sent from my SCH-I545 powered by T-Mobile Unlimited Plan
Click to expand...
Click to collapse
I have a Verizon S3 I just like to mess around with right now as a learning tool
Sent from my SCH-I545 powered by T-Mobile Unlimited Plan
suckmikehawk88 said:
I have a Verizon S3 I just like to mess around with right now as a learning tool
Sent from my SCH-I545 powered by T-Mobile Unlimited Plan
Click to expand...
Click to collapse
OK got it.
I know hyperdrive and bonestock both went to the s4 after they were released on our device, but they are not ports, the devs just moved on to different devices and built from those bases.
There are no roms specifically from the note 3 or s4 that were ported to this phone.
Sent from my SCH-I535 using Tapatalk 2
Alright, so i am having a bit of an issue. And it's probably because i'm a complete noob....
So, I have a new GS3, and wanted to give my (already rooted and flashed with Cyanogenmod 10) Skyrocket to my mom to use on Simple mobile (a company using T-mobile's towers).
I read that you can flash radios for T-mobile onto the phone, and so I figured everything would work.
Here is what I did.
I unlocked the phone while in Cyanogenmod10
Flashed LiquidSmooth RC9 - read it had less bugs
tried flashing multiple Tmobile Radios
I get NO service. I cant pick any of them up..
Baseband comes up as UNKNOWN...
So i'm currently downloading ODIN and going to try to flash to stock and just start from scratch...
Any suggestions on what to do?
Do you still have an imei?
Try unlocking the phone after you've gone back to stock. I don't know how you did it with cm10. I don't think it works with anything but stock.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
No, the IMEI is blank when i do the *#06# code....
also, when i put the simple mobile sim in the phone, it automatically came up asking for the network unlock code. That's how i was able to unlock it.
Did you ever backup your imei? Flashing back to stock will hopefully bring it back if not you may have some issues. Also as mentioned above it's better to unlock from a stock ROM or at least stock based.
Alright, Flashed to stock, IMEI is back (thank god), and i'm getting service.
Now here are the issues ahead of me, and any help would be greatly appreciated.
I am on STOCK ATT ICS Rom.
I GET SERVICE (however, it's only 2g) i know i need to flash the radios for Tmobile,
Was going to use this ---> Blaze_4G_LB7_ICS_Radio_MOD ...... Direct DL, CAN BE USED FOR T-MOBILE/WIND ON ICS (from the skyrocket reference thread)
First i know i have to root, install CWM, all that.
Now, should i flash a custom rom? If so, which one would you suggest. ( i assume, i have to give her ICS, not JB, right?)
Also, you said backup my IMEI, i'll look this up in the meantime, but if you could include a link in your post on a how-to just in case i dont find it, i would really appreciate it.
Also, is there anything else i should do to get this working properly?
thank you very much for all your help.
eternalcold said:
Alright, Flashed to stock, IMEI is back (thank god), and i'm getting service.
Now here are the issues ahead of me, and any help would be greatly appreciated.
I am on STOCK ATT ICS Rom.
I GET SERVICE (however, it's only 2g) i know i need to flash the radios for Tmobile,
Was going to use this ---> Blaze_4G_LB7_ICS_Radio_MOD ...... Direct DL, CAN BE USED FOR T-MOBILE/WIND ON ICS (from the skyrocket reference thread)
First i know i have to root, install CWM, all that.
Now, should i flash a custom rom? If so, which one would you suggest. ( i assume, i have to give her ICS, not JB, right?)
Also, you said backup my IMEI, i'll look this up in the meantime, but if you could include a link in your post on a how-to just in case i dont find it, i would really appreciate it.
Also, is there anything else i should do to get this working properly?
thank you very much for all your help.
Click to expand...
Click to collapse
Custom ROM is your choice. There are a lot of JB ROMS that are pretty stable. Also a new stock JB leak in the dev section. As far as backing up your imei. You'll need to root first as soon as you do get a file explorer and copy the whole EFS folder to your external SDcard. Then also copy it to your computer. The imei is held within the EFS folder. From now on do this as soon as you root BEFORE you flash anything. lol
hechoen said:
Custom ROM is your choice. There are a lot of JB ROMS that are pretty stable. Also a new stock JB leak in the dev section. As far as backing up your imei. You'll need to root first as soon as you do get a file explorer and copy the whole EFS folder to your external SDcard. Then also copy it to your computer. The imei is held within the EFS folder. From now on do this as soon as you root BEFORE you flash anything. lol
Click to expand...
Click to collapse
Thank you very much! I'll start rooting now and back it up immediately. I would love to give her a JB rom, mainly for google now. However, that radio is for ICS. Is that going to cause a problem? or will it even work on JB?
I've been on JB for months using an ICS radio. I'm on ATT so I can't say for certain but it shouldn't be an issue. Just go to the DEV thread and spend a few hours reading up on what's available. Like I said most of the ROMs are pretty stable at this point.
FYI, on skyrocket the IMEI is stored in mmcblk0p18 and mmcblk0p19, not /efs partition. Might really want to back those up, especially before attempting a usb unlock. The /efs only really stores exports of certain properties from mmcblk0p18.
cschmitt said:
FYI, on skyrocket the IMEI is stored in mmcblk0p18 and mmcblk0p19, not /efs partition. Might really want to back those up, especially before attempting a usb unlock. The /efs only really stores exports of certain properties from mmcblk0p18.
Click to expand...
Click to collapse
Thanks for the heads up. lol I thought for sure they'd be stored in the same place they where for my SGS4G. So what is stored in the imei folder in EFS then?
feed my curiosity if you can:
In theory, transplanting the modem file from a sprint rom to the rom from another variant and flashing a matching kernel would give me a functioning rom for me to use? I have a sprint variant but i'm overseas and do not care about CDMA at all.
I'm doing it later today when i come back from work, but i'd like to confirm if my assumption is correct.
Thank you!
I'm a bit curious too. I guess you won't be able to install it straight due to differences in partitions mapping (partition names and size may differ) but if it happenes to be the same your theory looks reasonable to me.
lorendroll said:
I'm a bit curious too. I guess you won't be able to install it straight due to differences in partitions mapping (partition names and size may differ) but if it happenes to be the same your theory looks reasonable to me.
Click to expand...
Click to collapse
I was able to boot an international variant rom but had no service. flashed the modem using twrp, no dice.