Related
hello, I have Touch pro 2 and want to maybe update the rom with official rom (from verizon) or installing a new rom from here XDA..
My question is, if I don't like my new rom, can I just make a hardreset to get back to my current (official and default) rom ? Or it will reset the default settings of the new rom ??
thanks !
If you don't like whatever rom you flash you need to flash a new one.
Hard reset will restore the default settings for the last ROM you flashed. If that was the stock ROM, then a hard reset will set it back to defaults for that ROM. If it was a custom ROM, then the custom ROM would be restored. If you want to go back to a stock ROM after flashing a custom ROM, then just flash it back when you're ready.
Hey All
I'm in need of some help. For some reason this whole SBF thing is completely confused me
My Defy
System Version: Moto_Version.34.30.3601.MB525.Vodacome.en.GB
Firmware Version: 2.2.2
Baseband Version: EPU93_U_00.59.02
Build number: JEM_3.4.3-36-1
(Unsure if these will help)
Anyway, I'm wanting to put CM7 or another custom rom onto my phone, but they all seem to be version 2.3 or so, but I want to be able to drop down to my original rom in case I need to return the phone for something
I did the official update to 2.2.2 from 2.1, which was lucky as with my 2.1 stock rom Clockworkmod couldn't read my memory card, seemed to be a common glitch with the SBF version it had, but it seems fine now
I read somewhere to use a Nordic nandroid backup for some reason, cant remember, just found it in my download folder from attempting to get clockworkmod to work on 2.1, restored the image onto my phone, which worked fine, but that seemed to be a no risk flash
So now I'm confused on how to proceed to putting on a custom rom, I fear that I'm going to **** up something, or going to run into issues if I try change to different custom roms
I'm possibly just over thinking what is meant to be done, and it is way simpler than it seems at the moment
anyone have some advice?
Using nordic as a base is old, custom runs like cm7 work on any base.
As long as you don't flash full sbf of gingerbread builds via rsdlite you can always go back to your original 2.2 by flashing full sbf through rsdlite.
Okay coming to installation of custom roms, first thing is to root it. You can use super one click for that. Then install defy 2ndinit after that boot menu and recovery.then you are all set to install custom roms.
For cm7, down load the zip and install through cwm.
Restart phone and as soon you see blue led press volume down, this would put you into boot menu.then select custom/stable recovery. Select wipe user data/factory reset.then go to advanced and select wipe dalvik cache. Come back and select install from zip and give cm7 zip, after finished reboot. It will now boot with cm7, first boot will take few minutes 2-3. It is generally cm7 first boot is in loop, if you are stuck just remove battery and put back and restart.
You can go through cm7 installation thread for better clarity.
Enjoy flashing!
Sent from my MB526 using XDA App
Thanks for the reply
So basicly I just flash the rom straight in clock work mod, no need for fixed SBF's or anything?
Do I need to back up/make full SBF of my stock SBF or something?
Is CM7 7.1 based on Froyo, and you'd just flash it straight from the memory card in Clockwork mod?
Or have I missed the point and meant to flash a fixed SBF to allow for gingerbread or any roms and then reflash 2.2 back on when I want to retore stock again?
Well I went ahead and installed Motogamer, which I downloaded last night and its working fine, but it seems to be based on the froyo kernal
I'm still a little confused as CM7.1 looks like its gingerbread, unsure of the downgradeability to my froyo stock rom, but this rom had no issue when I used my nandroid backup to restore to my stock rom
Thanks for the help
CM7.1 stable is android 2.3.7 with froyo kernel. And there is CM7.2 nightlies with both froyo and gingerbread kernels. I use the defy+ CM7.2 with gingerbread kernel from Quarx (this gives me better battery life) http://quarx2k.ru/, since i have redlens defy.
You dont have worry about the downgradability as long as you dont flash full sbf of gingerbread using rsdlite. All the dev custom roms have no problem in downgrading back to your original stock froyo. Look at if there is any WARNING IN RED regarding downgradability when you download any rom.
There are good number of ROMs to try, whenever you change ROM remember to do full wipe (factory reset and wipe dalvik cache), back up your apps and other information before you do this. If you are upgrading to night revision of same ROM, for example next nightly of CM7.2 we dont have do to full wipe, just cache and dalvik cache wipe would be fine.
If you like Stock ROM, try MS2ginger3.0 which gives awesome battery life and with full blur functionality if you like.
Awesome, thanks
I'm really keen to try more custom roms out, really happy so far with this new one at the moment, but will probably try CM7 soon
Thanks for the advice, not sure I'll go back to stock rom for a long time, just feared that I'd **** something up and not be able to return to stock if needed to
Really keen to start seeing what android really has to offer now
this is just weird, as i have been installing custom ROM like crazy...
but for some time i was on CM 10.1.2 and didnt install any custom ROM, but i felt like coming back to TW based ROMs, so tried installing DeTmobilized 1.5, but phone stuck at boot screen, i tried to restart by pulling battery out but phone displayed "encryption failed" and kept on showing phone.apk stopped working (something similar). so i decided to ODIN to stock and start fresh, this time i tried installed Dandroid 3.8.1 and it worked, so i thought of giving DeTmobilized one more try, but again it got stuck at samsung letters at the boot.
so i decided to stick with Dandroid for a while, but now i cannot install that too. it gets stuck while booting. but if i ODIN to stock everything works fine on stock firmware, its only the custom ROMs that are not working.
i also tried repartitioning using PIT file along with stock md5 hoping that would solve this issue, but it hasnt.
i need help, i cannot stay on stock ROM.
thank you.
chirantan.f said:
this is just weird, as i have been installing custom ROM like crazy...
but for some time i was on CM 10.1.2 and didnt install any custom ROM, but i felt like coming back to TW based ROMs, so tried installing DeTmobilized 1.5, but phone stuck at boot screen, i tried to restart by pulling battery out but phone displayed "encryption failed" and kept on showing phone.apk stopped working (something similar). so i decided to ODIN to stock and start fresh, this time i tried installed Dandroid 3.8.1 and it worked, so i thought of giving DeTmobilized one more try, but again it got stuck at samsung letters at the boot.
so i decided to stick with Dandroid for a while, but now i cannot install that too. it gets stuck while booting. but if i ODIN to stock everything works fine on stock firmware, its only the custom ROMs that are not working.
i also tried repartitioning using PIT file along with stock md5 hoping that would solve this issue, but it hasnt.
i need help, i cannot stay on stock ROM.
thank you.
Click to expand...
Click to collapse
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
also make sure you're using the latest custom recovery (either twrp or cwm)
i would also like to note here that i tried installing AOSP based ROMs also, and AOKP didnt work, got stuck at nexus like boot animation forever, but when i tried installing CM10.1.2 (which is what i was running when i tried to get back to TW based ROM) it worked perfectly, so for now i am back to CM, but i would really get back to flashing different ROMs and trying them out. just makes me wonder if CM is the reason i am not able to install anything else, just a thought...
has anybody else tried going to any other ROMs from CM 10.1.2?
your help is appreciated!
pcshano said:
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
Click to expand...
Click to collapse
thanks for your reply, but i have tried doing that, i also wipe data and system along with cache and dalvik before installing any new ROM.
pcshano said:
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
also make sure you're using the latest custom recovery (either twrp or cwm)
Click to expand...
Click to collapse
i have latest recovery , TWRP 2.6.0.0 and i have given more than an hour to boot up and still nothing. i have been flashing ROMs like an addict since i got this phone last year, but when CM 10.1 stable was released i stayed on it till today, but now i cannot install any other ROM, i can odin to stock 4.1.1 ROM or install cm 10.1.2 which i did just now, but no other ROM, either TW based on AOSP based is working...which is very weird for me.
Were you able to fix this issue at all? I am facing the same issue, in my case, the phone was encrypted on stock TW. I roooted and put in CM 10.1.2 and now when I try installing Dandroid, the install itself would work but I am struck at the "type password to unlock the screen". If I reflash CM10.1.2, I can login fine. Any pointers?
I've been jumping lately between various AOSP Jellybean roms, and Lollipop roms without issue on my I747m. Now, I'm upgrading my phone and want to give my S3 to my dad. He will just make basic calls and take pics. I want him to be on Touchwiz as i think the camera will be best for him in that regard.
I've tried 3 TW roms in a row, and they all give me the same error, "cannot connect to camera", as if another app is using the camera. Going back to my usual AOSP/CM roms in between attempts show the camera to work just fine. While on the touchwiz roms, I've cleared the camera cache, pulled the battery, etc etc... all the usual stuff. These are full wipes, clean installs with absolutely nothing being done to the phone (not even downloading an app). I install the ROM, wait a few minutes, then try the camera to no avail.
Any thoughts on what could be doing this? I have gone to touchwiz roms in the past (briefly) with no issue, but haven't tried in quite some time. I'm on the MK5 bootloader, if it matters.
Thanks.
Holmes108 said:
I've been jumping lately between various AOSP Jellybean roms, and Lollipop roms without issue on my I747m. Now, I'm upgrading my phone and want to give my S3 to my dad. He will just make basic calls and take pics. I want him to be on Touchwiz as i think the camera will be best for him in that regard.
I've tried 3 TW roms in a row, and they all give me the same error, "cannot connect to camera", as if another app is using the camera. Going back to my usual AOSP/CM roms in between attempts show the camera to work just fine. While on the touchwiz roms, I've cleared the camera cache, pulled the battery, etc etc... all the usual stuff. These are full wipes, clean installs with absolutely nothing being done to the phone (not even downloading an app). I install the ROM, wait a few minutes, then try the camera to no avail.
Any thoughts on what could be doing this? I have gone to touchwiz roms in the past (briefly) with no issue, but haven't tried in quite some time. I'm on the MK5 bootloader, if it matters.
Thanks.
Click to expand...
Click to collapse
I can think of a couple of things that may help.
MK5 is a 4.3 bootloader and modem. Were the TouchWiz ROMs you flashed Android 4.3 or KitKat ROMs? If they were Kitkat, Android 4.4.2, then the fix may be as simple as flashing the ROM and then flashing one of the custom kernels, either ibuddler's, found in the OP of the Likewise ROM, or the TW kernel by ktoonsez.
If you were flashing a 4.3 TW ROM, or if the custom kernel did not help with a 4.4.2 ROM; then you may need to flash a stock MK5 ROM, followed with a factory reset from the stock recovery. After that flash the custom recovery of your choice, root, and flash the TW ROM you like best.
dawgdoc said:
I can think of a couple of things that may help.
MK5 is a 4.3 bootloader and modem. Were the TouchWiz ROMs you flashed Android 4.3 or KitKat ROMs? If they were Kitkat, Android 4.4.2, then the fix may be as simple as flashing the ROM and then flashing one of the custom kernels, either ibuddler's, found in the OP of the Likewise ROM, or the TW kernel by ktoonsez.
If you were flashing a 4.3 TW ROM, or if the custom kernel did not help with a 4.4.2 ROM; then you may need to flash a stock MK5 ROM, followed with a factory reset from the stock recovery. After that flash the custom recovery of your choice, root, and flash the TW ROM you like best.
Click to expand...
Click to collapse
I had tried both 4.1 and 4.4 rom. Thanks for the tips though. I'll def look into all of that. I appreciate it!
I have been trying to install a custom rom and everytime I slide to install the ROM it keeps rebooting.
I tried installing a different ROM and I still get the same results. Its on 5.0 Rooted with TWRP version 3.0.2-1
The current ROM is stock and has never been modified. Now the phone does have a bad battery and I am waiting for the new one to come in later on today.
Has anyone had this issue before or does anyone have any suggestions for me. Thanks
I suggest trying TWRP 2.87.