going back to official ROM... - 8525, TyTN, MDA Vario II, JasJam ROM Development

i've decided to go back to the official OEM ROM.
none of the ROMs i've installed from here (schaps, tnt, black) give me a notification if someone leaves me a voicemail message, and i keep missing important (business) messages because of this, and losing work & money as a result
i do like the speed and stability of the ROMs ive downloaded from here, but i cannot afford to lose another £1000+ job because i missed an important voicemail
(i have posted on the various ROM threads about this problem but nobody ever seems to notice or reply to them)
however my understanding is that because i've upgraded to hardSPL then the exe supplied by Orange will not work. this exe also includes a radio "upgrade" which will knock my radio back by several versions, which i don't want to do
so how can i get the official Orange ROM back onto my hermes without downgrading the radio as well ?

Look in the offical rom thread (sticky on the top of the page) or go to the orange site and look for the upgrade rom. As a note have you changed your notifications (settings) to notify you when you get a voicemail/email. I flashed schaps 3.60 and had to go in and reconfig my notifications because they had been changed (not notifying for missed calls/new emails).

Although I am not as familiar with "orange" I can tell you I have never had the issue that you mention in regard to vm. As far as reverting to the official shipped rom, I have done so a number of times with perfect success. If you have hard spl on it than why not give it a shot and if it fails go from there. If reverting to the official rom works simply reload the radio of your choice after and you should be happy.
I personally feel it has to be a settings issue on your phone rather than a the os. Maybe check, and double check your settings to ensure they are correct before giving up on the wonderful cooked roms we have all grown so fond of. Additionally i can appreciate using your phone as a part of your business as I do mine but if your experiencing problems why risk it and just stay stock.

I would agree that it must be a configuration or network problem. Never heard of a ROM causing this.
However, the answer to your question is:
1. Download the ROM as instructed above (from Orange, HTC or here)
2. Using WinRAR or similar, unpack the .exe file
(You should get a an .nbh file and a RUU.exe file)
3. Using "dutty's good nbh tool", unpack the .nbh file that you got in step 2
(You should get a small collection of .nb files - radio, os, mainsplash, secondarysplash)
4. Still with dutty's good nbh tool, build an nbh file from the os.nb.
5. Place the newly built os.nbh in a directory alone with Custom RUU (available in here somewhere - search should find it - any post from Olipro has it linked in his sig)
6. Run the RUU.
Done!

Please be carefull when you give these kinds of advices!!!!
With dutty's tool he will extract nb files and not nbh.Afterwards he will have to recompile the ROM choosing the parts that he wants (OS.nb,....) and make a new RUU_signed.nbh which will flash with the RUUWrapper.
It's very pity to brick your device because someone did NOT know what ADVICE to give.Please be careful next time.This time I saw it on time.

Static,
Just before you go bac to the OEM rom consider this: I was on Virgin, then o2, both using Schaps 3.54c, not exprienced the problem you have indicated. Has got to be a network setting.
With my setup I get o2 to notify me of voicemail messages via a text rather than ringing and voice. Why don't you try that option before you jump ship?
Get another phone and call your number to make sure it works.
Good luck.
WB

I have used schaps and black and the only voicemail bug I had was the funny text message with the @ symbol bug, which is easily cured by running rabdo's orange cab.
I have run Black Satin for ages now and always get the voicemail symbol come up.
Make sure you clear all old voicemails and start from scratch for it to work...

that's the voicemail bug - i get the @ symbol thing
where's this orange cab you speak of. i've searched the hell out of these forums, and indeed, this is the 4th time i've posted about it (and the first i've received a response)
i've installed one orange cab i found somewhere, and also before i erased the shipped ROM i opened up the extended_rom and saved all those cabs to my storage card. i've tried installing all of those too and seemingly to no effect.

ok i think i found it - searching for rabdo found it. could have done with this one being in the wiki somewhere, seems everyone on orange had this problem, seems i'm not the only one who got annoyed enough to go back to the shipped rom too !

I wish I'd seen this earlier could have saved you a bit of hassle..
if you have any problems let me know as i've had it working fine on all the wm6 Roms i've tried using the non cab manual method (the cab sometimes fails for some reason)
Just for info: Its not a setting that you have to change its a change to the sms_providers.dll file to handle the weird way orange send the alerts in a text message, theres nothing you can configure as such to solve it without running the cab or installing the file and the devcerts manually.
You can also cook the fix in with a bit of tweaking if that would work better..

I have never had this problem of missing voice messages, both with the official WM6 ROM as well as all the other ROMs from Black and Dutty. I doubt if that has anything to do with the cooked ROMs. I am on Telstra network though.

Related

Official T-Mobile 2003 (RUUv2.07_CEv4.01.16rom) is here

hear we go
www.t-mobileapps.com/downloadcenter/Software/RUUv2.07_CEv4.01.16.exe
:lol:
This version has been pulled back by T-Mo.
Go ahead if you must, but know that 4.01.16 has been pulled by T-Mobile because many people are ending up with paperweights after trying to upgrade with it.
Someone elsewhere has recommended doing a hard reset of your XDA before trying this upgrade to free up as much RAM as possible.
I understand it's a problem with the installer. Use the SD card method and it'll be a lot safer. If you're paranoid then don't install the radio update until it's released.
OK.
I've also read that you need to do an SD-card install anyway if you already have a Beta WM03 version installed -- the upgrade.EXE checks for the version currently installed.
:shock: what? mine upgraded just fine!!
I can't get nine to upgrade either. My error that it gives me is that my ppc isn't connected to the USB port and to try again. I've installed the xda "unlock" rom upgrade so I'm at ver. 3.17.03 instead of the 3.08 that t-mobile says the unit should be at before the upgrade. Should I downgrade and try again or what.
well... make sure activesync is GREEN, and that your battery is FULLY charged, and IS hooked up to AC power supply.
if that dont work, after you run the upgrade, go to its folder, and copy the NBF file to sd, upgrade that way (the first time), then run setup again, to get the radio upgrade done too.
I upgraded mine and I have now W2003 running but my radio stack still 6.18 not 6.25 . thats correct?
If you use the SD card method the radio stack upgrade is a seperate step, so you won't automatically go to 6.25.
I tried copying the rsupgrade and the radio stack file but it fails, any one knows who I can update the radio stack to 6.25?
Here's how...
are the Siemens/AT&T WM2003 version bugs fixed?
At the moment I'm running the Siemens/AT&T official WM2003 ROM on my 32MB Dutch O2 XDA. This works great.
However, this ROM has the notorious sound bug and the memory leak bug. Volume of alarms is too low so I miss appointments frequently because I can't hear the reminder alarm (eg. in a noisy environment) and the memory is drained slowly (a soft reset every day fixes that).
Are these 2 bugs fixed in the T-Mobile WM2003 ROM :?:
OK ntabika,
Every thing is connected (and syncing in other downloads) but still gives same error. I'm new at this (had the thing two days) so I don't I'm unsure of which folder and were to find the nbf file. I've got a sd in and have been able to load but I don't know how to get the upgrade to the sd card
Thx,
David in Boulder
Re: are the Siemens/AT&T WM2003 version bugs fixed?
siliconaddict said:
Are these 2 bugs fixed in the T-Mobile WM2003 ROM :?:
Click to expand...
Click to collapse
Sound bug: Yes.
Memory leak: Time will tell. But might this also be due to an application (MS reader used to be notorious)?
Trials and Tribulations
So, ahh...
I went through it all. Tried to install via .exe and of course that didn't work (already have 2003 beta running).
Then I went to install the radio stack as prescribed in this thread. One recommendation: DON'T TOUCH ANYTHING WHILE IT INSTALLS. I accidentally touched the screen and it went back to the apps and crashed later after boot.
IF that happens to you, it'll sit there at the boot screen for about half hour and then go through and boot all the way up. You can then try to install the radio stack again. Worked for me the second time.
I then also upgraded the rest of the shizit using the WONDERFUL xda-developer tools. Also no word yet on the memory leak, otherwise everything works pretty much same as the AT&T latest official release.
Now if there was some Linux distribution out yet, how hard can it be to get this thing working right??? I'm willing to bet almost anything that it has the memory leak and its usual bugs.
Peace.
____________________________
Want to be eternally worshipped
by your gf? > www.shoespot.com

Problem Installing Apps in Official WWE English WM6 rom.

Hey y'all,
I have decided to update my device to WM6, to which purpose I downloaded the official version after registering for the e-club thing.
Anyways, I was struggling with making BlackBerry Connect live along with syncing to Missing Sync for mac the whole day and got it all figured out... (if anyone needs the answer on how to make BlackBerry Connect 4.0.0.90 and Missing Sync 4.0.0.415 work together give me a shout and I'll post a separate how-to on it to the forum)
So I had it all figured out and wanted to do a clean install of everything mind you this after about 20 or so hard resets. After this point all apps stop installing!!! Pretty much anything which needs some complicated install procedure does not install and just spews up the following:
"Installation was unsuccessfull. The program or setting cannot be installed because it is not digitally signed with a trusted certificate."
So now I am thoroughly confused on how to get around this. I have tried more hard resets and even reflashed with the same version of the ROM two more times, each time the result is exactly the same.
The strange thing is that some things do seem to get through like the PHM RegEdit and TaskManager and one of the JPL4 Dialer Skins... all installed without a hitch...
Trying to install Opera, BBConnect, SecureGSM and HTC Phone Pad brings up the aforementioned message although the install processes mostly seems to get to the aforementioned message. 5/6 hours ago all of these installed without a hitch, although sometimes I did have to try installing two or three times.
I am trying to install to the Storage Card, but the effect is the same if I try built in memory too.
Any one got any ideas? can it be that some certificate went out of date on the 1st of August or something? How could I cure all this?

suspected memory leak issues

I posted earlier in the month about issues with the camera app on the Hermes as I've cooked a WM6.5.3 build 28205, having tried again I got the camera working, seemingly by copying the rgu out of the stock WM6 ROM for the Hermes, I now have an issue where the device gets to a stage where it refuses to install apps, or files mysteriously get partially overwritten and cannot run, and the device will not reboot without a hard reset. I'm not sure if the registry entries in the rgu I copied are to blame or there is another issue that I'm missing, also, the camera, despite working as it should, does not display any text in it's dialogues, again, not sure why that is, and I've not been able to find solutions to any problems like this with google or on the forums here but I am looking to get this resolved soon as I wanted to cook a rom suited to my needs, with only the things I wanted in it, yet I stumble on this issue, if it's of any help I used superjustkitchen to cook it with
Thanks in advance and my apologies if this is the wrong part of the forum to post this

Android Troubleshooting, A Posting Guide.

I'd like to ask those wishing help with troubleshooting to please help us to help you.
When reporting a problem it is useful to get as much information as possible, the more information we have, the easier it is to help.
Is it running from SD or Nand.
What radio version.
What build are you having the problem with.
What kernel/nbh are you using.
If you can, try to post any error messages.
Please try to post your questions in the thread for the build you are having issues with, it's more likely to get noticed there, and other users of that build may have the solution you need.
All this information saves a lot of time, and helps cut down on confusion, especially the SD/Nand part.
I have trouble with signal, it's weak than WM, when I used WM my radio is 1.65, I'm up to 1.71.09.01 and flash Android (NAND menthod) and the signal so weak
So Android support radio 1.65??? I want to back 1.65
I'm using TYTN 2 Kaiser _ WarmDonut version
Another Qs:
Q.How can I use my fone like a modem? I see in Menu have Modem but I don't know how to connect with my PC as a modem
Q.How can I connect to my PC via Wifi ad-hoc? (if available, please guide step by step- because I'm... chicken )
Q.GPS so slow and weak (in Vietnam)
Q.It so hard to power off (It's hang)
Best regard
I had issues with 1.71.xx radios too, and went back to 1.65.21.14 and my signal was good once more.
To change radio, download the radio you wish to use from this thread http://forum.xda-developers.com/showthread.php?t=393182, post 3 has the download links you need.
Once you have it downloaded, rename the ruu_signed.nbh to kaisimg.nbh and copy to SD card, flash using the power+camera method you used to flash the nand nbh, you will not have to reinstall Android when you do this.
The modem in question refers to the gprs modem used for data, it should be possible to use the phone as a modem, but as far as I know this is not working properly yet.
Not sure if you can do this either, I know wifi works for data transmission, but accessing the computer this way with android may not be possible, yet.
Gps problems may depend on which nbh you have installed, some of the more recent nbh's perform better than older ones. I'd recommend Kallt_Kaffes NBH's as I know these are quite good for gps, for me at least. http://forum.xda-developers.com/showthread.php?t=660158, you will need to load the nbh into the editor and set the correct panel type, keyboard, and 3d type, ( donut in your case), then save as kaisimg.nbh and copy to SD and flash using power+camera, again this will not affect your android install.
Power off issues may be nbh related also, however this can still happen anyway, usually pulling out the battery will sort out the reboot issues.
many thank for quick reply, I love Android on my phone
thank you again
I was wondering what steps to take when the android loader gets stuck in a loop, when I install andriod right after install it boots fine but when I try to boot second time, after andriod appears on the bottom of the screen it will go into some kind of loop. I have tried different radios and a different version of hardspl, and a few nbh panels as well as reinstalling the system, any help would greatly appreciated.
Phone: AT&T Branded TILT
OS: Nand w/Incubus Super Froyo Installed
Radio: 1.70.18.02
NBH: kaisimg-panel2-320-tilt-froyo-07-07-10
HardSPL: v3.34.hard
Everything looks fine, although I haven't used that particular build, however bootloops are commonly build or kernel related.
Have you tried other builds? Or is it just this build that does this?
Generally panel type only affects the display on the screen itself, or sometimes problems with sleep mode.
Since you have a froyo kernel installed, maybe you could install this build to see if it helps? http://forum.xda-developers.com/showthread.php?t=724821
Yeah I have tried other Froyo builds and they worked, but I just like the way Super Froyo build is put together. But if it is the build then its is the build. Oh well maybe next release. Ok thank you for your time, guess I will give the GZO build or the one you suggested a try.
Installed the kernel you suggested, it works. It boot looped once, then I cleared the dalvik cache and it booted again after install. I don't know if that is what it is used for, but it worked after that.
It is a awesome build, battery life works correctly, signal is good with radio, and wi-fi works good. But I had one more questions.
1. What is up with live wallpapers, on some builds I have used some work on one build but not the other, I have looked through the forums, but can find no solution for this. Is it because of the amount of RAM in the TILT as I saw somewhere or is there a fix. Even in this build when I try to load a live wallpaper on a couple of them is just stays on wallpaper loading and stay black screen.
I would like to take a minute to thank the people that make this awesome stuff, now my TILT has more current software than my BACKFLIP, so my older phone is now newer than my new phone, and I would also like to thank the people who help others out on this forum, I don't think a lot of people like myself would get anywhere without your help.
Forgot to mention dalvik cache. oops, ah well, you found it anyway
It's another of those occasionally useful things, like fix permissions, I have used it before to fix unusual behaviour, but not tried it on a bootloop.
Live wallpapers are usually pretty buggy at best, it's complicated, memory is one problem, cpu speed another, and 3d handling yet another, some wallpapers work ok, but slow, others just won't, ever. I just delete them before install, along with a few other minor customisations such as deleting a few ringtones and notification sounds, changing boot animations, nothing that affects the core of the build, just personalising a bit
I'm using:
1)incubus's Super Eclair 6.1, with the downgraded settings.apk which enables wifi (another member offered the settings.apk from a previous version (3, I think) as an androidupdate.tar)
2) Currently radio 1.71.09.01 (thinking of switching to 1.65.21.18 to improve reception)
3.) Currently using the latest Dzo kernel for eclair (07-02-2010, I think)
My problem is that my data connection doesn't work (and this has been an issue on just about every release, save for one Froyo install where the data autostarted once, and then I never saw a 2g/3g notification and mobile internet didn't work).
I'm currently in India, and I've used the correct APN settings (they have worked on other phones including Nokias, iPhone, and a USB modem). I've tried asking the question in the SuperEclair vogue thread, but alas, no love. I'd really appreciate if you could help me on this, or at least guide me in the right direction, because android (especially eclair) is too awesome to abandon for this single issue.
By the way, everything else works, Wifi (with the mentioned update), GPS, Voice, and SuperEclair is the fastest that I've found so far.
I have seen a number of issues with data such as this, and i'm afraid none have had a truly satisfying resolution.
However I would try:
Downgrade the radio as planned, this may help, and certainly won't hurt.
Boot to installer, and run fix permissions and clear dalvik cache, this has been known to fix various issues, not certain why yet.
Double check the apn settings, especially the MCC and MCN settings, a lot of online guides seem to miss these two, but they are important.
Not sure where to point you after this, apart from a long trawl through the thread here, however if you do get it resolved please post back, and if not, try another post on it in the build thread, along with the steps you have taken to resolve it, it may convince someone to have a closer look at this issue.
data connection
I too have had this problem after installing a recent froyo build to nand....I had checked no.start data when flashing dzo's latest kernel using nbh editor and had to reset my apn settings. Remember to open your modem utility and press connect twice....this actually starts the connection......Radio type could also be an issue..Ive had good luck with the 165's with 2 different froyo builds....Hope this helps.....
Thanks for the replies! I'm going to try this out (need to recharge the data service on my prepaid) but one thing I did notice was that the MNC/MMC were different that those listed on my providers website. Hopefully this will help.
I have tried to switch on the data using the modem utility, and the utility itself says that data is connected, but it never really worked. In settings, there is an on/off switch for mobile internet, and a mobile internet settings. When I click the on/off switch, then mobile internet just goes gray and does nothing. I'll try to post back to the Super Eclair vogue board, but I think that Incubus might have moved on...
I'll update once I get my gprs service paid up. Again, thanks for the help!
The process com.android.phone has stopped
Those are my first Android experiences, so I`ve got problems .
Phone : Kaiser (TyTN II)
OS : Win Mo 6 Profess (original-not flashed)
Radio : 1.27.15.32
I`m trying to install Android on the SD card, without additional partitioning. I`m currently trying this Android version : Eclair 2.1 for Kaiser/Vogue/Polaris -- polymod 2.1 gamma [Based on OpenEclair 1.2.2 (XDA thread)]
and using this too : How to run Polymod’s AWESOME 2.1 Eclare Build and Updates (the forum didn`t allow me to post links for the Android versions). I`ve tryed this too : VaniljEclair RLS7c - A fast and stable CM 5.0.8 for Vogue/Kaiser/Polaris [2010-07-02] - the same result
I`ve done everything according the instructions... Starting Haret.. Hit D-Pad, Install, clear data... etc. etc... It actually starts to install... and everything seems fine... At some point it brings me again the install menu, I`m hitting exit, and then come some errors ?!? I forgot to type them down... Something like that some files cannot be found... And after rolling errors for a while the Android actually boots ! But then come errors too... At the first time it brings me the dial pad to enter my pin-code... I entered it , but it says it is wrong...I wasn`t wrong ofc . For the next time I simply disabled my pin in Win Mobile and try again... After the Android booted it says : The process com.android.phone has stopped unexpectedly. Please try again. , and some button like "cancel" or something like that. I'm hitting it , the Android guy appears and a message " Hit the android to begin" with a hand pointing it. I`m hitting the android - nothing happened !
I`ll be greatfull if someone can help me , or at least give me some clues !
Thank you .
p.s. sorry for my english... not my native language ;-)
Your problems are mainly in the OS version, 6.0 is not recent enough to run Android, and the radio version will also give problems, my advice would be to update to the most recent stock version, which would enable you to run Android.
This would of course wipe your present installed OS and a more recent version may or may not exist for your language, ( with the wiki down I can't be more specific with which files would suit you best).
Thanks
zenity said:
Your problems are mainly in the OS version, 6.0 is not recent enough to run Android, and the radio version will also give problems, my advice would be to update to the most recent stock version, which would enable you to run Android.
This would of course wipe your present installed OS and a more recent version may or may not exist for your language, ( with the wiki down I can't be more specific with which files would suit you best).
Click to expand...
Click to collapse
Thank you for your fast response . But I`ve tryed (I`ve tryed again today) before to download an official WinMo 6.1 ROM from HTC_com , but according to my TyTN II`s serial number , they said : "Sorry, this software download is not suitable for your device". And I want an original ROM... I`m not sure that I can manage to flash a cooked one on my HTC . So I guess I`ll stay with the original WinMo 6.0 withut Android .
Thanks anyway
To flash a cooked rom you would need HardSPL, it is possible to do this for WM 6.0.
Regarding an upgrade to WM6.1, this too should be possible, I'd tend to disregard the warnings about upgrades being 'unsuitable'. The unavailability of certain upgrades is more to do with them being designed for certain providers or areas, rather than their actual unsuitability for the device itself.
If you have a need for a language specific rom this too is probably available from another source, if the wiki was available then there is a table of rom upgrades that would almost certainly contain just what you would need.
Note that the wiki links are all official HTC roms, and would not need HardSPL.
@Zenity - You had given me some advice on getting the gprs working on my eclair install (Eclair problems/Android problems thread). Well, I ended up ditching Super Eclair for polymod 2.1d, and mobile data started working out of the box (which is odd, because it wasn't really working before, but who am I to question?!). Now my only issue is that if I activate wifi without first deactivating mobile data, then wifi gets caught in a loop and won't connect (i.e "Connecting, obtaining address, unsuccessful, connecting, obtaining address, unsuccessful" and on on on...). Then if I try to deactivate data or wifi, both get grayed out and say turning off, but never do. I'm fairly positive this is some conflict between data and wifi, because I've connected to the same AP without any issues while the data connection is off. Regardless, this is the most fully functional implementation that I've found. Still playing around, now that I have the time I'm diving a little further into tweaking and hacking through these releases.
Thanks for the help man. I've been on xda-devs since I first got this Att Tilt, mainly reading and learning, but I've noticed that a fair number of people don't take the time to further explicate and help people through problems and troubleshooting. You and kallt_kafee are both awesome when it comes to responding to less knowledgable users, and I for one really appreciate it. So Cheers, bro!
Thanks matcha, the main reason I still find polymod 2.1D my build of choice is that of them all, it just works, all the other builds do to, but I have found less issues from users on Polymod than the other builds, perhaps it's age has something to do with it, it has less 'new' features than the others, so less to go wrong, and perhaps also that it has grown with the whole android on kaiser project.
Anyway, appreciate the vote of confidence, really I'm just trying to give back a small measure of what Xda-Developers has given me

Looking for a Touch Pro 2 ROM

Hello, I was looking for a new ROM for my T-Mobile Branded Touch Pro 2, which is unlocked and running on the Simple Mobile network instead of T-Mobile, and currently running the T-Mobile Windows Mobile 6.5 Official ROM.
The main concerns I am having while looking for a ROM is:
T-Mobile has the MMS Settings locked, so I am unable to send MMS while using my Simple Mobile SIM Card in it. I am a social networking junkee, and constantly send pictures to Facebook right after taking them, and don't like wasting time opening the Facebook App to upload them. So picture messaging is a must for both sending and receiving.
Another thing, I love the HTC Sense with TouchFlo 3D, it makes everything a lot easier for me to navigate to, and I don't like the feel of the original Windows Mobile today screen.
Is there a ROM out there that covers both of these? Can someone point me in the right direction?
I'm kinda new to the site, not really sure how to navigate to ROMs, and not really sure where to look for ROMs that cover the things I am looking for.
MMS: Most, if not all, custom ROMs here (make sure to flash the GSM HardSPL and GSM ROMs!) unlock the MMS settings screen (it can also be done via a registry edit). Here is a thread with MMS fixes to apply (I'm guessing this should be done after flash a ROM or unlocking the settings screen with a reg-edit).
Registry edit:
1. Download a Registry Editor like this.
2. Open the editor and navigate to
Code:
HKEY_LOCAL_MACHINE\Software\ArcSoft MMS UA\Config\UI.
3. Change the value of the key EnableServerEdit from 0 to 1.
4. Soft reset (turn off then turn on the phone OR just press the red reset hole on the right side of the device).
5. Go to Messages Tab > All Messages > Menu > MMS Options... > Servers Tab > T-Mobile MMS.
6. Change the settings to make it compatible with your provider.
Most ROMs also have Sense UI cooked in. Now, if you still want fluidity, get a ROM with Sense 2.1 (I think the EnergyROMs have a Sense2.1 variant). If you want quicklinks in your homescreen (like the HD2) but are willing to sacrifice some speed, get a ROM with Sense 2.5 cooked in.
Thank you very much, MMS is now functioning correctly.
I have one question about flashing new ROMs, I might have missed it, or just can't find it on the Hard-SPL post. If I were to flash Hard-SPL, then flash a ROM, but I decide I want to stick with the original T-Mobile 6.5 ROM (I have the ROM install file on my PC still) would I be able to flash back to the T-Mobile ROM?
partyboynx2 said:
Thank you very much, MMS is now functioning correctly.
I have one question about flashing new ROMs, I might have missed it, or just can't find it on the Hard-SPL post. If I were to flash Hard-SPL, then flash a ROM, but I decide I want to stick with the original T-Mobile 6.5 ROM (I have the ROM install file on my PC still) would I be able to flash back to the T-Mobile ROM?
Click to expand...
Click to collapse
You're welcome.
Yes, you can flash back to the stock T-Mobile ROM, just as long as you have access to it. With HardSPL on your phone, you can actually flash any GSM Rhodium ROM, stock or custom. In the event you need to return your phone, you will also need to restore the StockSPL after flashing back the stock ROM.

Categories

Resources