Related
Hi, I am using a desire HD with the sabsa prime 6.0 rom installed. Version 7.0 is already out and I want to know how to update my rom from 6.0 to 7.0 without deleting anything and with everything to stay the same just like stock rom updates. Is this possible? Please reply.
Sure it's easy. Just flash the new version in recovery without wiping anything and you're good to go.
I have done this many times before with no problems.
Muikkuman said:
Sure it's easy. Just flash the new version in recovery without wiping anything and you're good to go.
I have done this many times before with no problems.
Click to expand...
Click to collapse
Thanks bro
I know its a pain in the ass to restore everything and it always seems more easier to flash ROMs without wiping anything. But I'd still suggest wiping before flashing for stability reasons. You might encounter some FC's or even crashes.. say if you lose your data because of a crash.. then you'll have no way to recover because you were lazy and never backed up anything.
There are ways to backup almost everything : sms, call logs, apps, etc.. Use them. Or at the very least take a nandroid backup before you flash a new version without wiping.
Yes Do that. Make a Nandroid backup before flashing without full wipe. Some crash can happen so you can come back to 6.0 version. If there's no crash and no lags it would be cool for you.
Sent from my Light Tab 2 using xda premium
hi, i recently got an ATT note 2. The phone I got already got Clean ROM 3.5, so I presume it is rooted, with custom recovery (TWRP when I checked). I am thinking of flashing to a diff rom and just want to ask a few questions.
1-do I need to run triangle away every time I flash to a diff rom?
2-since the phone already has a custom rom, I should not have to root it, am I correct?
3-If I want to install custom, ROMs, can I just put the ROM in the external SD and flash it that way (of course with clear cash, davik, etc as states in the rom).
4-I am thinking of playing with the CleanROM 4.2.4 or the ACE version? any issue with either one compare to the 3.5 that I am using now? any recommendation?
5-anything I need ot watch out before I flash it? I have flashed a coupole of time with htc phone and this is my first samsung phone so I don't watn to brick it.
thanks a lot guys, XDA rocks.
PUTALE said:
hi, i recently got an ATT note 2. The phone I got already got Clean ROM 3.5, so I presume it is rooted, with custom recovery (TWRP when I checked). I am thinking of flashing to a diff rom and just want to ask a few questions.
1-do I need to run triangle away every time I flash to a diff rom?
2-since the phone already has a custom rom, I should not have to root it, am I correct?
3-If I want to install custom, ROMs, can I just put the ROM in the external SD and flash it that way (of course with clear cash, davik, etc as states in the rom).
4-I am thinking of playing with the CleanROM 4.2.4 or the ACE version? any issue with either one compare to the 3.5 that I am using now? any recommendation?
5-anything I need ot watch out before I flash it? I have flashed a coupole of time with htc phone and this is my first samsung phone so I don't watn to brick it.
thanks a lot guys, XDA rocks.
Click to expand...
Click to collapse
1. No you do not need to run triangle away usually only have to run it if you are going back to stock and may want to return the phone.
2.Nope it has a Rom you are rooted !
3.That is what I do when installing a new rom factory reset wipe davlik and cache and install you may have to fix permissions with some installs as well after installing.
4.From the bit I played with the new Clean rom it is very stable with minimum if any grief Jedi 9 is also a awesome ROM and my current fave.
5.Just read up lots before you do it follow every step they tell you to take your time it is easy just make sure ya know what you are doing before you start.
6.Enjoy they are a awesome phone !!
Thanks a lot for your prompt reply. It heped a lot. I will definitelycheck the roms. I am using 3.5 and it runs really good and hate to ruin it.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
PUTALE said:
Thanks a lot for your prompt reply. It heped a lot. I will definitelycheck the roms. I am using 3.5 and it runs really good and hate to ruin it.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
do a backup in twrp before flashing a new one, you can always come back
thanks for the info. That brings me to another question with TWRP, when I do TWRP backup, should I backup everything, modem, efs, etc. Also, if I use that backup and I do restore, does it restore everything, program, rom, setting, etc?
Also, if I want to flash the stock ROM, would that mess up my root, recovery etc? Do I need to do anything if I flash the stock ROM? From my past experience, sometimes, it is good to flash the stock rom once in awhile since that seem to do some sort of clean up and it also helped to keep the modem and such up to date.Probaby won't keep the stock for a long time but just thought I may flash it to play with it and keep the modem files up to date. Then flash custom rom. I also read that if I want to use triangle, I must be on stock rom or it will brick my phone, so I want to make sure before I start playing with diff roms.
thanks a lot guys
PUTALE said:
thanks for the info. That brings me to another question with TWRP, when I do TWRP backup, should I backup everything, modem, efs, etc. Also, if I use that backup and I do restore, does it restore everything, program, rom, setting, etc?
Also, if I want to flash the stock ROM, would that mess up my root, recovery etc? Do I need to do anything if I flash the stock ROM? From my past experience, sometimes, it is good to flash the stock rom once in awhile since that seem to do some sort of clean up and it also helped to keep the modem and such up to date.Probaby won't keep the stock for a long time but just thought I may flash it to play with it and keep the modem files up to date. Then flash custom rom. I also read that if I want to use triangle, I must be on stock rom or it will brick my phone, so I want to make sure before I start playing with diff roms.
thanks a lot guys
Click to expand...
Click to collapse
This is one of nice features of TWRP... ability to backup/restore individual partitions. Android stores various blocks in different partitions. To name a few, System, Data, Modem, Recovery, Boot, Cache, etc. If you just want to backup your modem for example, just check the "modem" box (and I recommend naming the folder to something significant so down the road you'll know which modem it is). When you restore, that folder will only have your modem.. so you can restore a different modem without having to change your rom, (etc). Kernels are stored in the "boot" partitions.. again, if you want to change kernels, backup the boot partition and name it properly if case you want to reflash that kernel. Generally, after my first flash of a new ROM, kernel, modem, I'll create a "boot" backup, "modem" backup, and ROM (system/data/boot) partition backups. If you look in the TWRP folders themselves, you can see the blocks which are backed up... or will be restored. Hope that helps.
PUTALE said:
thanks for the info. That brings me to another question with TWRP, when I do TWRP backup, should I backup everything, modem, efs, etc. Also, if I use that backup and I do restore, does it restore everything, program, rom, setting, etc?
Also, if I want to flash the stock ROM, would that mess up my root, recovery etc? Do I need to do anything if I flash the stock ROM? From my past experience, sometimes, it is good to flash the stock rom once in awhile since that seem to do some sort of clean up and it also helped to keep the modem and such up to date.Probaby won't keep the stock for a long time but just thought I may flash it to play with it and keep the modem files up to date. Then flash custom rom. I also read that if I want to use triangle, I must be on stock rom or it will brick my phone, so I want to make sure before I start playing with diff roms.
thanks a lot guys
Click to expand...
Click to collapse
When I back up in TWRP, I usually just go with what is default checked off. You will not mess up your root unless you really really tried to. The last time I ever had to flash back to stock then to a custom was on my Xperia X10a... You should be fine flashing a new rom without having to go back to stock as long as you do a good wipe (Wipe System, Factory Rest, Davlik, and Cache is what I do only because it doesn't hurt... I've read you do not need to do all those steps but I do them nonetheless). Do not use Triangle Away unless you plan on returning your phone or send it in for warranty. Only then should you start asking questions about that tool.
The only issue that may cause SOME confusion (not too much but some) is flashing back and forth between a 4.1.2 and a 4.2.1 since the SD card adjusts to User settings (some folders open up for individual users on 4.2 but as far as my experience goes, I have not had any issues with it, I just needed to study my SD card after each flash).
So you should be fine... just do backups, rename them to make sure you know which rom belongs to which backup, delete the old ones from the RESTORE menu in TWRP in case you are backing up the same rom to save you some space (my backups take around 2 gigs sometimes EACH) and you should be good to go... Enjoy tweaking out on your roms!
DoctorQMM said:
This is one of nice features of TWRP... ability to backup/restore individual partitions. Android stores various blocks in different partitions. To name a few, System, Data, Modem, Recovery, Boot, Cache, etc. If you just want to backup your modem for example, just check the "modem" box (and I recommend naming the folder to something significant so down the road you'll know which modem it is). When you restore, that folder will only have your modem.. so you can restore a different modem without having to change your rom, (etc). Kernels are stored in the "boot" partitions.. again, if you want to change kernels, backup the boot partition and name it properly if case you want to reflash that kernel. Generally, after my first flash of a new ROM, kernel, modem, I'll create a "boot" backup, "modem" backup, and ROM (system/data/boot) partition backups. If you look in the TWRP folders themselves, you can see the blocks which are backed up... or will be restored. Hope that helps.
Click to expand...
Click to collapse
Much appreciated for your detail explanation on the TWRP. I did a quick backup and selected all of the option and now I see the files in my external SD:
modem.emmc.win
data.ext4.win
cache.ext4.win
recovery.emmc.win
boot.emmc.win
efs.ext4.win
data.ext4.win
system.ext4.win
Quick question. If I understand correctly, the modem and efs is not ROM backup, so if I just want to revert to the rom I am currently running with all apps and such, I only need to backup system, boot, data, am I correct?
Also, is there any way that I can retain my data, settings, and apps, without re-download and re-configurate everything after I flash to a new ROM? I am thinking that maybe data will do such thing but not too certain. In the past, whenever I flash to a new rom, I always download all apps again from market and setup everything again, a bit hassle but that's how I did
[email protected] said:
When I back up in TWRP, I usually just go with what is default checked off. You will not mess up your root unless you really really tried to. The last time I ever had to flash back to stock then to a custom was on my Xperia X10a... You should be fine flashing a new rom without having to go back to stock as long as you do a good wipe (Wipe System, Factory Rest, Davlik, and Cache is what I do only because it doesn't hurt... I've read you do not need to do all those steps but I do them nonetheless). Do not use Triangle Away unless you plan on returning your phone or send it in for warranty. Only then should you start asking questions about that tool.
The only issue that may cause SOME confusion (not too much but some) is flashing back and forth between a 4.1.2 and a 4.2.1 since the SD card adjusts to User settings (some folders open up for individual users on 4.2 but as far as my experience goes, I have not had any issues with it, I just needed to study my SD card after each flash).
So you should be fine... just do backups, rename them to make sure you know which rom belongs to which backup, delete the old ones from the RESTORE menu in TWRP in case you are backing up the same rom to save you some space (my backups take around 2 gigs sometimes EACH) and you should be good to go... Enjoy tweaking out on your roms!
Click to expand...
Click to collapse
thanks for the info/warning on the triangle. I read that it can brick the phone and also needs to be on the stock to use it. Also read that if there's too many counts, it may not work. I guess for now, I just won't touch it.
Since there's no 4.2 roms available (at least not what I have seen and want to play, CleanRom or Jedi as they are highly rated), I guess for now I do not have to worry much on the SD card issue. It will be safer I guess for now just stick with 4.1.2 until the kinks are worked out.
For the wipe system, factory, davlik, cache, do I do that before flashing it?watched a couple of video and instruction and they all have diff answers. Some people said do factory reset, flash, and then wipe davik and cache.
Again, really really appreciate all of the support guys.
PUTALE said:
Much appreciated for your detail explanation on the TWRP. I did a quick backup and selected all of the option and now I see the files in my external SD:
modem.emmc.win
data.ext4.win
cache.ext4.win
recovery.emmc.win
boot.emmc.win
efs.ext4.win
data.ext4.win
system.ext4.win
Quick question. If I understand correctly, the modem and efs is not ROM backup, so if I just want to revert to the rom I am currently running with all apps and such, I only need to backup system, boot, data, am I correct?
Also, is there any way that I can retain my data, settings, and apps, without re-download and re-configurate everything after I flash to a new ROM? I am thinking that maybe data will do such thing but not too certain. In the past, whenever I flash to a new rom, I always download all apps again from market and setup everything again, a bit hassle but that's how I did
thanks for the info/warning on the triangle. I read that it can brick the phone and also needs to be on the stock to use it. Also read that if there's too many counts, it may not work. I guess for now, I just won't touch it.
Since there's no 4.2 roms available (at least not what I have seen and want to play, CleanRom or Jedi as they are highly rated), I guess for now I do not have to worry much on the SD card issue. It will be safer I guess for now just stick with 4.1.2 until the kinks are worked out.
For the wipe system, factory, davlik, cache, do I do that before flashing it?watched a couple of video and instruction and they all have diff answers. Some people said do factory reset, flash, and then wipe davik and cache.
Again, really really appreciate all of the support guys.
Click to expand...
Click to collapse
Think of your Nandroid (TWRP) backup as a roll back to what you are comfortable with (check everything off so you do not lose a thing if you want) in case you find that the new thing you flashed isn't all that it was cracked up to be for you or something messes up. The Nandroid backup is EVERYONE's friend.
As for flashing a new ROM and having to start all over, I will use this as an example: I have two backups; one for Paranoid Android (4.2.1 AOSPA) and Clean 4.2.5 (4.1.2). When I originally flashed my stock to Clean, I must've gotten lucky by just wiping the system (ROM only and not a factory reset) and all my data transferred over just fine with no issues... but when flashing to PA, I had to do a full wipe then start from scratch (which was not bad if you sync your apps and contacts thru Google). Also, you might want to get another backup system such as Super Backup to back up your contacts and SMS messages (be careful with backing up call logs if you go to 4.2.1 ROMs because for some reason, things went wacky for me). Titanium is a good system to use for power users but sometimes, to keep it as simple as possible, count on Google at first for your app syncing (and if you get Amazon App Store, you will have to get that APK to download the apps from that store).
Anyway, from there (if you want to play with multiple ROMs) you now have a foundation. Dirty flashing (flashing a new version of a ROM you currently have without doing a full wipe... just in case you didn't know... for me, I just wipe System [no factory reset] then flash the upgrade) should be fine... again, I'm typing from experience because there are some people who do run into issues dirty flashing and is usually not supported by the devs unless you do a full wipe and flash. I have not had any issues whatsoever dirty flashing both PA and Clean versions.
As for methods of wiping, honestly they're all right... I just posted what I usually do when I want to do a full wipe. Only if you want to do a dirty flash, you won't have to wipe or do a partial wipe (I partial wipe e.g. Clean 4.0.5 to 4.2.5: Delete last Clean Rom backup through the Restore menu, Nandroid Back Up current working Clean Rom 4.0.5, Wipe System, Install the new 4.2.5, wipe Davlik and Cache (again, I do this just in case but some devs say it's unnecessary), then reboot and wait for the apps to reset... all was where it was when I left 4.0.5.
PUTALE said:
Quick question. If I understand correctly, the modem and efs is not ROM backup, so if I just want to revert to the rom I am currently running with all apps and such, I only need to backup system, boot, data, am I correct?
Also, is there any way that I can retain my data, settings, and apps, without re-download and re-configurate everything after I flash to a new ROM? I am thinking that maybe data will do such thing but not too certain. In the past, whenever I flash to a new rom, I always download all apps again from market and setup everything again, a bit hassle but that's how I did
Click to expand...
Click to collapse
Yes... if you're retaining your current modem and recovery... to restore a rom just as it was when you backed it up, restore boot (which has the kernel), system and data. One your second question, when restoring a different rom , it's best to always restore system/data/boot together. You can use TiBu to restore your user app DATA, and individual apps usually have their own backup files you can restore (like Nova/Apex launchers [which can restore your widgets], calendar, etc).
much appreciated guys. thanks so much. I think I got it. Will get ready to pick a good ROM and starts flashing.
one little thing, I saw this rom here: http://forum.xda-developers.com/showthread.php?t=2124182
it says stock rooted, does that mean that it is essentailly identical to what is found on the stock rom except that it will not mess up with my recovery and rooting if I use it to flash as oppose to the guide I saw online to flash to completely stock using ODIN.
Also, I did the unlock with what I found on the thread, would that mess got messed up when I flash to different ROM?
PUTALE said:
much appreciated guys. thanks so much. I think I got it. Will get ready to pick a good ROM and starts flashing.
one little thing, I saw this rom here: http://forum.xda-developers.com/showthread.php?t=2124182
it says stock rooted, does that mean that it is essentailly identical to what is found on the stock rom except that it will not mess up with my recovery and rooting if I use it to flash as oppose to the guide I saw online to flash to completely stock using ODIN.
Also, I did the unlock with what I found on the thread, would that mess got messed up when I flash to different ROM?
Click to expand...
Click to collapse
I have never used that rom so I can't say for sure. Try it out and see what happens. If you don't like it, restore your backup.
PUTALE said:
much appreciated guys. thanks so much. I think I got it. Will get ready to pick a good ROM and starts flashing.
one little thing, I saw this rom here: http://forum.xda-developers.com/showthread.php?t=2124182
it says stock rooted, does that mean that it is essentailly identical to what is found on the stock rom except that it will not mess up with my recovery and rooting if I use it to flash as oppose to the guide I saw online to flash to completely stock using ODIN.
Also, I did the unlock with what I found on the thread, would that mess got messed up when I flash to different ROM?
Click to expand...
Click to collapse
That rom is one of the most recent 7105 (note2 international) samsung firmware releases... supposedly better battery life than LL7 or LL4. It's the stock MA6 pre rooted (i.e., has SuperSU app and binaries included). No other features added like you would find with CleanROM 4.2.5 for example. It includes rom and kernel... so it will write to your system, data, and boot partitions. Whatever custom recovery you have now and flash this with will not be touched.
thanks again.
I rooted my GS3 a week ago. I had installed titanium back up, battery calibration, wifi tether, pimp my rom. Everything was going fine and then i installed AdFree which supposely removes ads. Well this ended up crashing my phone. I managed to delete it. And now whenever i use a launcher like Apex and Espiere (the iphone launcher i think its Espiege not sure) they crash. I open up titanium back up and other apps and it crashes. Even when i call comes in it goes black screen and i cant see who is calling or amswer or ignore. Please help is there any way i can fix this? I dont want to unroot. I wanna keep my root but i cant restore anything since most of my apps crashes.
By the way im using a Sprint galaxy s3 and i have root with Stock Rom. My version is 4.1.1
If you have a flashable zip of your ROM, you can simply reflash it without wiping /data. This will keep your apps in tact, while removing anything that may have conflicted with the /system partition.
Also - any apps that are closing, I'd recommend going into settings > Applications > (app that's crashing) > Clear Data.
Otherwise, you may need to re-odin the stock package and fully wipe the device.
Overstew said:
If you have a flashable zip of your ROM, you can simply reflash it without wiping /data. This will keep your apps in tact, while removing anything that may have conflicted with the /system partition.
Also - any apps that are closing, I'd recommend going into settings > Applications > (app that's crashing) > Clear Data.
Otherwise, you may need to re-odin the stock package and fully wipe the device.
Click to expand...
Click to collapse
How should i do this? Do i do it from my computer or can i do it from my phone? Im new at this so im a bigtime noob lol
I would just start by booting into recovery and wiping cache and dalvik cache, then fix permissions.
Sent from a planet far far away.
First: Try booting to recovery and wiping cache/dalvik/fix permissions as said above. Then reboot and see if that helps. If it does go to settings, app, and clear that ad free cache and data.
if no luck there: Download a stock rom (http://forum.xda-developers.com/showthread.php?t=1737859) and flash the zip from recovery. If you do not know how to do any of this please search and read as much as possible to educate yourself.
if no luck there you may be doing a full wipe or even reformatting and then flashing your new rom. I recommend CM10 personally.
COOKtheKILLA said:
First: Try booting to recovery and wiping cache/dalvik/fix permissions as said above. Then reboot and see if that helps. If it does go to settings, app, and clear that ad free cache and data.
if no luck there: Download a stock rom (http://forum.xda-developers.com/showthread.php?t=1737859) and flash the zip from recovery. If you do not know how to do any of this please search and read as much as possible to educate yourself.
if no luck there you may be doing a full wipe or even reformatting and then flashing your new rom. I recommend CM10 personally.
Click to expand...
Click to collapse
If i just do a factory reset will that remove my root access? How do i boot into recovery? (Like what do i install or press?)
Start fresh. http://forum.xda-developers.com/showthread.php?p=34726404
Go into download mode and just do the one click application. You'll start fresh with stock rooted ROM. Make sure to get the jellybean one. And back up anything you can if you want.
Ninja25 said:
Start fresh. http://forum.xda-developers.com/showthread.php?p=34726404
Go into download mode and just do the one click application. You'll start fresh with stock rooted ROM. Make sure to get the jellybean one. And back up anything you can if you want.
Click to expand...
Click to collapse
How do i go to download mode? And click the one click app? Do i set it in recovery mode? I get so confuse.
YouTube qbking77 Samsung Galaxy s3. You'll find instructional videos.
Sent from a planet far far away.
Questions go in Q&A
Thread moved
Friendly Neighborhood Moderator
Speedin07si said:
YouTube qbking77 Samsung Galaxy s3. You'll find instructional videos.
Sent from a planet far far away.
Click to expand...
Click to collapse
NICE!!! Good videos and good instructions.
Ok I wrote this for the OP of my ROM because the issues some people were PMing me about were just plain out dumb, This phone has been out quite a long time and still almost every thread I goto, you got people flashing in way's I didn't even know were possible and posting weird issues that were not being reproduced by the community. so I'm just gonna post this guide for all the developers sake and in hopes the people that actually need this information, receive it before posting and clogging up development threads
If you're having issues on rom's that no one else is reporting, or the DEV has not reproduced on his phone, read the following.
1) Full wipe
2) Do not restore System data or data from CWM
3) Do not dirty flash from other ROM's
4) When was the last time you did a odin to stock? this is important in my opinion and I'm not saying you need to do one but I just want to explain that custom zip's that I make and other dev's make in the shape of "roms" only affect
a few partitions on your device, other's do not get touched and can get messy/corrupt over the months (This explains why the GPS icon disappears in some peoples cases during rom switch) and this is why I get posts in this thread about people wondering why their baseband hasn't been updated after flashing my rom when my post states "MF1"
With this being said my personal rule of thumb is to odin to stock latest and then boot into stock recovery and factory reset, wipe cache/dalvik (BACKUP YOUR SD CARD TO YOUR COMPUTER), this gives your phone fresh partitions everywhere, a fresh system to root and the latest bootloader (which you need for any AOSP 4.2 rom). This is also a good time to unlock your phone if you have not already, then reroot and install custom recovery, update the recovery if need be and flash again on a brand new system. here are my steps
1) backup all user apps and data with titanium backup, DO NOT BACKUP SYSTEM APP'S
2) backup internal storage onto PC
3) Odin to stock latest
4) wait for phone to boot then reboot into stock recovery and full wipe and clear all cache
5) reboot and root the phone and custom recovery
6) flash away and put what you need on your internal storage back onto your phone via usb, see my 2nd set of instructions below
this fixes more issues then you will realize. some of the way people flash rom's on XDA and complain to me with problems is rather funny considering I have the install instructions in the OP, not to mention many of you rooted your phone when you first got it in the ICS 4.0.4 day's and haven't done an odin to stock jellybean to update all your partitions including your bootloader, now I will go over my every day flashing step's.
1)backup all USER APPS/DATA with titanium backup, DO NOT BACKUP SYSTEM APP'S (skip this if you did a odin flash to stock)
2)reboot recovery
3)nandroid (skip this if you did a odin flash to stock)
4)factory reset, wipe system, wipe both cache/dalvik
5)install rom
6)boot system
7)*(OPTIONAL) reboot to install a kernel now if needed, always wipe cache/dalvik and fix permissions after installing a kernel
8)setup phone and download titanium backup from the market
9)restore all user apps and data (you will have to put the titanium backup folder that is backed up on your computer back onto your internal storage via usb first)
Every 6 months, backup internal storage to PC and I odin to stock, much like formatting a computer
6 months is actually a long time considering how much I flash, but this device can take a beating let me tell you =P
I DO THIS WITH EVERY ROM I INSTALL, AOSP or TW
Great info, that is actually my same process when I have an issue with anything
Good read. A lot of common sense for seasoned flashers, will be great for people who are unsure.
Sent from my SGH-T999 using xda app-developers app
KorGuy123 said:
Good read. A lot of common sense for seasoned flashers, will be great for people who are unsure.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
thanks man, hoping this gets a sticky.
Danvdh said:
thanks man, hoping this gets a sticky.
Click to expand...
Click to collapse
I'll add it to my sticky
Galaxy S3 / AoCP / V4A / Turbocharged
s3 unrooting issues
I have been having some big problems with unrooting my telus SGH I747 Galaxy s3. I have flashed the stock rom using odin, did a factory reset and wiped cache and everytime i reboot it loads up the same roms i had on there at first. I have had a lot of issues with roms as well such as slow messaging times, echoing voice calls using AOKP and when i use an AOSP rom i cant connect to my phone carriers data connection at all. I read this form and decided its probably a good idea to re root as you said due to updates or whatever else but now im runing into this issue. I have ask on other forms and no one seemed to have heard of this issue. If anyone has any ideas or knows a fix i would really appreciate the help.
Custom ROM data issue
dannyteo14 said:
I have been having some big problems with unrooting my telus SGH I747 Galaxy s3. I have flashed the stock rom using odin, did a factory reset and wiped cache and everytime i reboot it loads up the same roms i had on there at first. I have had a lot of issues with roms as well such as slow messaging times, echoing voice calls using AOKP and when i use an AOSP rom i cant connect to my phone carriers data connection at all. I read this form and decided its probably a good idea to re root as you said due to updates or whatever else but now im runing into this issue. I have ask on other forms and no one seemed to have heard of this issue. If anyone has any ideas or knows a fix i would really appreciate the help.
Click to expand...
Click to collapse
So scrap the unrooting issue i have that figured out now, i just reinstalled the rom and again it doesnt have data, it is the deadly venom rom, anyone else that i know who is using this rom has absolutely no problem. I have tried a few fixes i have found via youtube, google, etc.... but none were successful. If anyone knows a fix or has any ideas please let me know.
I have an I747M S3 from a friend and trying to get it back to stable stock. It had lost it's IMEI and some NVdata corruption but I was able to resolve that searching the forums, But it has issues with apps crashing and rebooting quiet frequently. It can sometimes go feeling pretty stable ofr awhile then just kind of blows up. I have cleared away the flash counter and restored factory stock images from Odin and Keis, still having the issues. Is there a partion or something that could be getting missed? Or possible further problems related to the NVdata issues?
if you have any ideas I would appreciate it.
I used twrp to back up system, data, and boot, should I still use titanium back up to back up anything else, or is that enough to be relatively safe?
Not sure what happened, but this is what's going' on. I'm working with SM-T210R / updated to the 4.4.2 - Did not like the issues with Custom Recoveries, so I got into TWRP - Restored my stock rom backup and everything restored fine and as expected. I went to Root the device, using RootJunky's TWRP recovery and root on YouTube (which I've done many times and never had an issue - I'm not a noob, but, still have a lot to learn) Anyways - when you go swipe to reboot the system, TWRP asks you about installing Supersu for Root access, and of course, you go with it. Well, since that swipe - it keeps rebooting into TWRP - I cant get to the system. I used Odin to install Philz and same thing, kept rebooting into Philz. I've tried re-restoring my back up and now it wont .... it acts like it is, but then it keeps throwing me back into the custom recovery being used ... any ideas or help is greatly appreciated!
PS - Thank you to gr8nole and RootJunky - I'm always using your guys' methods and suggestions.
jonstowe78 said:
Not sure what happened, but this is what's going' on. I'm working with SM-T210R / updated to the 4.4.2 - Did not like the issues with Custom Recoveries, so I got into TWRP - Restored my stock rom backup and everything restored fine and as expected. I went to Root the device, using RootJunky's TWRP recovery and root on YouTube (which I've done many times and never had an issue - I'm not a noob, but, still have a lot to learn) Anyways - when you go swipe to reboot the system, TWRP asks you about installing Supersu for Root access, and of course, you go with it. Well, since that swipe - it keeps rebooting into TWRP - I cant get to the system. I used Odin to install Philz and same thing, kept rebooting into Philz. I've tried re-restoring my back up and now it wont .... it acts like it is, but then it keeps throwing me back into the custom recovery being used ... any ideas or help is greatly appreciated!
PS - Thank you to gr8nole and RootJunky - I'm always using your guys' methods and suggestions.
Click to expand...
Click to collapse
Install stock recovery from Odin to get out of recovery bootloop
Sent from my SM-T211 using XDA Free mobile app
sscsps said:
Install stock recovery from Odin to get out of recovery bootloop
Sent from my SM-T211 using XDA Free mobile app
Click to expand...
Click to collapse
ok I will try that now ... I hope youre right!
If you reboot to recovery using any method other than the three button reboot, you'll be stuck in recovery.
Sent from my ATRIX HD using XDA Free mobile app
bmatney said:
If you reboot to recovery using any method other than the three button reboot, you'll be stuck in recovery.
Sent from my ATRIX HD using XDA Free mobile app
Click to expand...
Click to collapse
Well, yeah, that's the reason,
According to gr8nole, bootloader is responsible for this, the updated version of bootloader have this problem
Sent from my SM-T211 using XDA Free mobile app
bmatney said:
If you reboot to recovery using any method other than the three button reboot, you'll be stuck in recovery.
Sent from my ATRIX HD using XDA Free mobile app
Click to expand...
Click to collapse
That's IF you are using the Stock 4.4.2 ... I restored my Stock 4.1.2 before all this started happening ... Regardless, thank you guys for your suggestions, but its all good now. After work I came home and decided to give it one more try, using Odin to put Philz on and go from there, and this time it took. Once I got Philz on, I was able to (again) restore my 4.1.2 stock backup (fix the flickering screen of course) and the get back to Nolekat v1.9 - thank GOD!
jonstowe78 said:
That's IF you are using the Stock 4.4.2 ... I restored my Stock 4.1.2 before all this started happening ... Regardless, thank you guys for your suggestions, but its all good now. After work I came home and decided to give it one more try, using Odin to put Philz on and go from there, and this time it took. Once I got Philz on, I was able to (again) restore my 4.1.2 stock backup (fix the flickering screen of course) and the get back to Nolekat v1.9 - thank GOD!
Click to expand...
Click to collapse
No, it can happen if you are on 4.1.2 too, it happened to me on my SM-T211 while running 4.1.2 and I did used a software method to reboot to recovery and was stuck in recovery bootloop
Sent from my SM-T211 using XDA Free mobile app
jonstowe78 said:
That's IF you are using the Stock 4.4.2 ... I restored my Stock 4.1.2 before all this started happening ... Regardless, thank you guys for your suggestions, but its all good now. After work I came home and decided to give it one more try, using Odin to put Philz on and go from there, and this time it took. Once I got Philz on, I was able to (again) restore my 4.1.2 stock backup (fix the flickering screen of course) and the get back to Nolekat v1.9 - thank GOD!
Click to expand...
Click to collapse
It will happen if you ever updated the firmware once, no matter if you revert back to previous version later
Sent from my SM-T211 using XDA Free mobile app
sscsps said:
It will happen if you ever updated the firmware once, no matter if you revert back to previous version later
Sent from my SM-T211 using XDA Free mobile app
Click to expand...
Click to collapse
Good to know ... GREAT, so since I updated that ONE time, from now on I can NEVER boot into recovery via software? It'll always be the 3B method .... that sucks! lol
jonstowe78 said:
Good to know ... GREAT, so since I updated that ONE time, from now on I can NEVER boot into recovery via software? It'll always be the 3B method .... that sucks! lol
Click to expand...
Click to collapse
Yes
Unless someone makes a fix for that!
Sent from my SM-T211 using XDA Free mobile app
jonstowe78 said:
That's IF you are using the Stock 4.4.2 ... I restored my Stock 4.1.2 before all this started happening ... Regardless, thank you guys for your suggestions, but its all good now. After work I came home and decided to give it one more try, using Odin to put Philz on and go from there, and this time it took. Once I got Philz on, I was able to (again) restore my 4.1.2 stock backup (fix the flickering screen of course) and the get back to Nolekat v1.9 - thank GOD!
Click to expand...
Click to collapse
I've been trying to find a way to downgrade back to 4.1.2 after finding out about kitkat's flaws. After I installed it, I noticed three things:
- NO extSD card permission
- FASTER battery drainage (it takes a whole day to charge it back from 0)
- Games like Temple Run can no longer be played cause tilt sensor malfunctions - accelerometer issues)
The first two are a major let down. If I had known about this prior the upgrade, I would have kept JB 4.1.2.
Now I'm looking for ways to safely downgrade back to Jelly Bean. From what I'd read, people are getting stuck in custom recovery because the kitkat bootloader or whatever is not compatible (or something like that)? Also, those who have successfully managed to get back to JB now have the issue of not being able to charge their sm-t210R unless it's turned ON. So if we fix one issue, we still got the other.
@jonstowe78, are you having any issues with charging while your device is turned off?
I read about flashing Philz custom recovery for sm-t20R, and after a (failed) attempt to root my tab 3 (which put me off from rooting), I know a bit about the 3B method to reboot. I flashed a custom 4.1.2 JB stock rom using Odin and that's how I got rid of the messed up screen that happened after I rooted.
I would LIKE to root to NoleKat, but like I said, one bad experience with rooting, forever leery of it. Unless someone can help me, please?
sscsps said:
Install stock recovery from Odin to get out of recovery bootloop
Sent from my SM-T211 using XDA Free mobile app
Click to expand...
Click to collapse
Ditto that. I got the firmware from sammobile.com & flashed (AP mode in Odin 3.09) and I was no longer stuck. At that point, I had stock 4.4.2. I then flashed phil via Odin 3.09 (AP) - the gr8nole version (check the nolekat thread) and was able to install any ROM I wanted.
Good luck
ameva said:
I've been trying to find a way to downgrade back to 4.1.2 after finding out about kitkat's flaws. After I installed it, I noticed three things:
- NO extSD card permission
- FASTER battery drainage (it takes a whole day to charge it back from 0)
- Games like Temple Run can no longer be played cause tilt sensor malfunctions - accelerometer issues)
The first two are a major let down. If I had known about this prior the upgrade, I would have kept JB 4.1.2.
Now I'm looking for ways to safely downgrade back to Jelly Bean. From what I'd read, people are getting stuck in custom recovery because the kitkat bootloader or whatever is not compatible (or something like that)? Also, those who have successfully managed to get back to JB now have the issue of not being able to charge their sm-t210R unless it's turned ON. So if we fix one issue, we still got the other.
@jonstowe78, are you having any issues with charging while your device is turned off?
I read about flashing Philz custom recovery for sm-t20R, and after a (failed) attempt to root my tab 3 (which put me off from rooting), I know a bit about the 3B method to reboot. I flashed a custom 4.1.2 JB stock rom using Odin and that's how I got rid of the messed up screen that happened after I rooted.
I would LIKE to root to NoleKat, but like I said, one bad experience with rooting, forever leery of it. Unless someone can help me, please?
Click to expand...
Click to collapse
Download stock md5 of 4.1.2 for your country from sammobile.com and flash it from Odin to downgrade to 4.1.2,
For rooting, take a look at this:
http://forum.xda-developers.com/showthread.php?t=2822307
How to root any android device, easy, Noob friendly!
Sent from my SM-T211 using XDA Free mobile app
sscsps said:
Download stock md5 of 4.1.2 for your country from sammobile.com and flash it from Odin to downgrade to 4.1.2,
For rooting, take a look at this:
http://forum.xda-developers.com/showthread.php?t=2822307
How to root any android device, easy, Noob friendly!
Sent from my SM-T211 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you for your feedback!
The truth is, after I made that post, I did a lot of reading on custom recovery like TWRP, Philz Touch, and CWM, and then I read some more about NoleKat v2.0, and how it basically is like KK but it gives you root access and sd card rights back, so now I've decided to not downgrade. I've learned a lot from when I first tried to root (which ended in failure and a dim screen with flickering colors), so I'm more confident in how the process goes.
I was wondering though. If I install custom recovery (from any of those three), will they wipe my data? I know you can back up your data using the custom recovery, but which one do you think is the least likely to have issues with KK bootloader (assuming the custom recovs have all been updated to 'play nicely' with the KK so people won't get stuck in custom recov bootloop?)
ameva said:
Thank you for your feedback!
The truth is, after I made that post, I did a lot of reading on custom recovery like TWRP, Philz Touch, and CWM, and then I read some more about NoleKat v2.0, and how it basically is like KK but it gives you root access and sd card rights back, so now I've decided to not downgrade. I've learned a lot from when I first tried to root (which ended in failure and a dim screen with flickering colors), so I'm more confident in how the process goes.
I was wondering though. If I install custom recovery (from any of those three), will they wipe my data? I know you can back up your data using the custom recovery, but which one do you think is the least likely to have issues with KK bootloader (assuming the custom recovs have all been updated to 'play nicely' with the KK so people won't get stuck in custom recov bootloop?)
Click to expand...
Click to collapse
Gr8nole have updated the recovery for SM-T210 to not stuck in recovery bootloop(it used to happen only and only if you use any software method to enter in to recovery mode) download cwm for SM-T210 and you are good to go,
And none of the recovery will wipe your data, even if you select factory wipe from custom recovery, it will only delete all the installed applications,
And of you flash(install) a recovery, it won't delete any data/app
Sent from my SM-T211 using XDA Free mobile app
@gr8nole Please prepare two PARAM image from JB and KitKat firmware. Try both PARAM on your device, maybe one of it is the solution of this recovery bootloop issue.
To create Odin flashable param:
Code:
tar -H ustar -c param.bin > param.tar
md5sum -t param.tar >> param.tar
mv param.tar param.tar.md5
sscsps said:
Gr8nole have updated the recovery for SM-T210 to not stuck in recovery bootloop(it used to happen only and only if you use any software method to enter in to recovery mode) download cwm for SM-T210 and you are good to go,
And none of the recovery will wipe your data, even if you select factory wipe from custom recovery, it will only delete all the installed applications,
And of you flash(install) a recovery, it won't delete any data/app
Sent from my SM-T211 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks again for your feedback!
Wait, you mean the installed apps that came pre-installed with KK? Because that's what it sounds like if you say that the recovery will not wipe my data like game progress, rss feeds, recordings, etc?
So if that's true, should I still create a backup through the custom recovery?
Would that be called a dirty flash? Or a full wipe?
I've spent nearly this whole day reading through the NoleKat thread from v0.1 to v.2. I can see it's come a long way. Gr8nole is truly an amazing developer! I've seen issues like charging offline, recovery bootloop, boot animation issues fixed as each new update gets better and better.
ameva said:
Thanks again for your feedback!
Wait, you mean the installed apps that came pre-installed with KK? Because that's what it sounds like if you say that the recovery will not wipe my data like game progress, rss feeds, recordings, etc?
So if that's true, should I still create a backup through the custom recovery?
Would that be called a dirty flash? Or a full wipe?
I've spent nearly this whole day reading through the NoleKat thread from v0.1 to v.2. I can see it's come a long way. Gr8nole is truly an amazing developer! I've seen issues like charging offline, recovery bootloop, boot animation issues fixed as each new update gets better and better.
Click to expand...
Click to collapse
No, not the pre-installed apps, but the apps you installed will be uninstalled is you perform a wipe operation from recovery(custom)
It's just a apps wipe, it will leave only personal data like photos, songs, etc.
Sent from my SM-T211 using XDA Free mobile app
Hmm, I guess I'm just going to have to do a dirty flash then, mainly because I have this one game app, and even though it stores my game info in a folder, if I delete the app, I lose my account, and it's huge hassle to get it back.
So just to be clear, dirty flashing is basically no factory wipe/reset at all, right? Then what does the davlik or wiping cache do? I think we're still suppose to do that after flashing custom rom.
ameva said:
Hmm, I guess I'm just going to have to do a dirty flash then, mainly because I have this one game app, and even though it stores my game info in a folder, if I delete the app, I lose my account, and it's huge hassle to get it back.
So just to be clear, dirty flashing is basically no factory wipe/reset at all, right? Then what does the davlik or wiping cache do? I think we're still suppose to do that after flashing custom rom.
Click to expand...
Click to collapse
You can flash it without any risk of anything being deleted, flashing recovery won't delete anything (neither any app)
Cache memory stores dynamic things which helps apps to run smoothly, if you wipe that, your apps will have to make that memory again(when it runs for the first time/first time after you clear cache) to run smoothly in future, but Delvik cache helps android to run smoothly, every rom need different things to run smoothly, so we need to clear previous rom's Delvik cache in order to allow new rom to create is own Delvik cache of its own, this is the reason the first boot takes a bit longer time to compleat because it takes time to write is own Delvik cache, sometimes, different roms' Delvik cache conflicts, so it can be like you get stuck on boot screen, just clear Delvik cache to fix it
Hope it is clear, I might be wrong, but this is what I think it is!
Sent from my SM-T211 using XDA Free mobile app