Related
Hi everyone, I have rooted my x10 using superoneclick, I deleted the bloat wares i did not want, I flashed multitouch using flashtool, i then restored to factory and re-did all that after my wife deleted txt and dialler while playing with my new faster phone. I have the media i want, the home style and what else that i like but i want to flash a custom rom and be able to still use all my apps ect without downloading everyone of them again! I have installed xrecovery and made a backup of my current phone also. SO - I have downloaded the .rar file of the rom i would like to my computer desktop and not unzipped it and now i want to just tripple check where i save that file to on the phone. do i just save it to general sd card? do i make a new folder in sd card and put it in that? Then after i have saved it to wherever{???} do i enter xrecovery, scroll down then select install custom rom and select it from wherever? THEN {sorry i know this drags on} before i reeboot do i restore my backup to apply my apps ect or do i do that after reeboot?
ANY advice is appreciated. I know these questions sound basic to most of you but im the only person i know that even messes with this stuff none of my mates or work mates are even remotely interested so xda is my support network!
Lastly, to go back from custom rom to "normal" I assume i just run With se support and then run my backup from backup and restore app file?
model X10i
Baseband 2.0.46
Kernel 2.6.29
Build 2.0.A.0.504
Thanks everyone!!
What rom are you looking at? First, the file needs to be in zip format for XRecovery, not rar. RAR files usually are for the flash tool. Confused?
Put zip file anywhere you like on sdcard. Actually, you can download the zip file directly from your phone browser or the xda app. It will save to download folder by default. Then enter XRecovery and wipe cache, then go into advanced options and wipe battery stats and dalvik cache. After that install custom zip from sdcard.
Do NOT use xRecovery restore to restore apps and data. Use titanium backup from the market to backup and restore apps when going between android versions.
Also, why use outdated 2.0.A.0.504 firmware? Use global generic 2.1.A.0.435 firmware, it has dualtouch implementation and lots of other tweaks. Also, custom ROMs are particular about which baseband to use, so double check that. This will also get you ready for the official 2.3.3 Gingerbread update directly from PC Companion or SEUS when available.
if you have a set group of apps you would always want the fastest and best way to reinstall between versions is with an app called 'MyBackup Root' it works better with data between versions. I would also recommend Titanium Backup for just backing up and restoring all apps but MyBackup will restore them all faster for initial setup.
Sent from my X10i using XDA Premium App
agentJBM said:
What rom are you looking at? First, the file needs to be in zip format for XRecovery, not rar. RAR files usually are for the flash tool. Confused?
Put zip file anywhere you like on sdcard. Actually, you can download the zip file directly from your phone browser or the xda app. It will save to download folder by default. Then enter XRecovery and wipe cache, then go into advanced options and wipe battery stats and dalvik cache. After that install custom zip from sdcard.
Do NOT use xRecovery restore to restore apps and data. Use titanium backup from the market to backup and restore apps when going between android versions.
Also, why use outdated 2.0.A.0.504 firmware? Use global generic 2.1.A.0.435 firmware, it has dualtouch implementation and lots of other tweaks. Also, custom ROMs are particular about which baseband to use, so double check that. This will also get you ready for the official 2.3.3 Gingerbread update directly from PC Companion or SEUS when available.
Click to expand...
Click to collapse
You don't do full wipe/factory restore in xrec? You're supposed to
fiscidtox said:
You don't do full wipe/factory restore in xrec? You're supposed to
Click to expand...
Click to collapse
Never have..... and I never had any of the multitude of problems others seem to have. I go between stock 2.1, FreeX10 and WB's CM6 rom quite frequently.
Doesn't flashing a new ROM result in wiping the previous one? You don't have to factory reset before using SEUS or PC Companion...it does it within the process.
agentJBM said:
Never have..... and I never had any of the multitude of problems others seem to have. I go between stock 2.1, FreeX10 and WB's CM6 rom quite frequently.
Doesn't flashing a new ROM result in wiping the previous one? You don't have to factory reset before using SEUS or PC Companion...it does it within the process.
Click to expand...
Click to collapse
I never have problems and I always do, every instruction set I've ever read said to. If that were the case, it also wipes the dalvik and the cache partition too, so you might as well not do any of it.
Since my time with the htc hero, I've always been told to do the three (factory wipe, cache and dalvik cache).
fiscidtox said:
I never have problems and I always do, every instruction set I've ever read said to. If that were the case, it also wipes the dalvik and the cache partition too, so you might as well not do any of it.
Since my time with the htc hero, I've always been told to do the three (factory wipe, cache and dalvik cache).
Click to expand...
Click to collapse
I always thought it was cache, dalvik cache, and battery stats. I guess it might not matter as much as we think. I know that I have never had any problems restoring apps or data either, which everyone else seems to have trouble. Maybe factory wipe is causing the difficulties.
I never read anyone telling others with problems to do a factory wipe. I have only read wipe battery stats and dalvik cache.
I don't know enough to say either way, but in my experience it doesn't appear to be needed. Confused.
agentJBM said:
I always thought it was cache, dalvik cache, and battery stats. I guess it might not matter as much as we think. I know that I have never had any problems restoring apps or data either, which everyone else seems to have trouble. Maybe factory wipe is causing the difficulties.
I never read anyone telling others with problems to do a factory wipe. I have only read wipe battery stats and dalvik cache.
I don't know enough to say either way, but in my experience it doesn't appear to be needed. Confused.
Click to expand...
Click to collapse
hahaha no it definitely isn't causing any issues....
Go read any of the threads for noobs, they all say to do a factory wipe.
From every thread I've ever read, and every dev thread, the ALWAYS recommend to do a factory wipe
Here is just one example, though with search function you will literally find hundreds.
http://forum.xda-developers.com/showthread.php?t=939812
fiscidtox said:
hahaha no it definitely isn't causing any issues....
Go read any of the threads for noobs, they all say to do a factory wipe.
From every thread I've ever read, and every dev thread, the ALWAYS recommend to do a factory wipe
Here is just one example, though with search function you will literally find hundreds.
http://forum.xda-developers.com/showthread.php?t=939812
Click to expand...
Click to collapse
I didn't say that devs don't put it in their guide. I said that I always thought it was cache, dalvik cache, and battery stats.
I beg to differ about issues restoring apps and data. The devs say not to restore data (which would suck btw). I do it all the time between 2.1 and 2.2. I never had any problems with the market, angry birds etc. that others have.
Again, not saying that I know better than anyone. Just saying it is not necessary for me. I can understand the theory behind wiping everything in preparation, but I am proof that it is not required.
I also see some guides that don't say to wipe battery stats, like WB's. However, if you have battery drain that is the first thing you are told to do. Also, there are calibration apps out there that say wiping battery stats and dalvik cache are the two things needed with a new rom.
Wow what a response!
Cool, so first up i should go to the latest spec firmware {using se update service} ?
THEN, the rom i am looking at is [MOD][rendeiro2005]Cyanogen6.1.1_v02 {i now have it in zip}
It looks good from what i have read.... opinions?
So i have titanium backup as well, and ive watched videos on how to use it so ive got that sorted - as far as flashing a new firmware... some posts say you need a new kernel as well?
Sounds like my backup root is a good option, again, if i flash a whole new rom does it stay on the phone somewhere/somehow?
Hey thanks for the info guys its appreciated
If you flashed 2.0.A.0.504 global generic, then update service should work. If you flashed a regional firmware, then you should use the Flash Tool 0.2.9.1 to flash global generic 2.1.A.0.435. Then flash baseband, if needed.
Then use flash tool to root, optimize, and install xRecovery. Do a full backup with xRecovery of 2.1, so you can easily switch back to 2.1 if wanted. Also, backup with Titanium Backup or Mybackup Pro, to restore apps and data on your new rom.
Download rom custom zip to sdcard. Go into xRecovery. Wipe everything. Install custom rom zip. Using custom kernel is not mandatory, I don't think. Just need correct baseband. Restore apps and data with Titanium Backup.
i flashed the new generic no worries, re-rooted phone and installed xrecovery, used titanium backup and that worked well so all my apps and setting were as applied {including mod bootscreen} then after that i thought i should start xrecovery and load restore the backup i had made there.... it went through the process fine then said recovery finished reboot phone, so i did, and phone started to boot as normal, including with the different boot screen but then it just went to blank screen and the light at the top of the phone just shone bright white for a min or two.... then it started doing this and rebooting over and over and over.....for a half hour! so i reflashed the new generic and re-did ti backup, re-rooted and am wondering did xrecovery do that because my recovery file was made under my old firmware? or what else did i do wrong?
When going between firmwares and especially going from 2.1 to 2.2 or 2.3.
I suggest not using your back up from the previous rom.
There are compatibility issues with some apps.
When you clear your battery cache, I suggest you make sure your fully charged.
Font want your phone to think half charge is full.
You don't need to clear your cache......but you should.
It will work with out clearing the cache.
But it could fc or just go bananas.
Sent from my SE_X10i using XDA App and sliding my finger around really fast
Bootloop.... sounds like you are using wrong baseband, or you tried to reinstall xRecovery and Busybox. You don't need to worry about root, JIT, or xRecovery with custom ROMs. It's in there already...
Ive re-flashed phone with new firmware 2.1.A.0.435 Kernel is 2.6.29 Baseband is 2.1.54.
Re-rooted, re-loaded my titanium backup and phone is now as it was before i tried restoring xrecovery backup file and resulting bootloop.
now i will make a new xrecovery backup as my phone is now - All this trial and error stuff is exhausting!
Still thinking i should flash 435 Kernel?
Im happy with that so far - now i am going to try the 3g build.prop mod to see if i can get an improvement there.
Ive got speedtest but every test is so varied {from 1200 up to 420 up next test} so i don't know how well that will go.
Only after ive got a grip on all that stuff i will go for a new rom, mainly because i fly away for a weeks work in two days and wont have time to fix anything i do wrong! thanks again guys ill be donating next week to the helpful souls on here!
Restoring backup file in XRecovery is why you still have Bootloop. You just set it back to the error you had before.
Instead, do a fresh install of the custom rom zip.
You may need to flash the baseband patch if the rom isn't for baseband .54.... Flash the rom, then the baseband patch
Sorry my last post made it sound like i was back to bootloop, what i meant that after i re-flashed to standard, re-rooted ect ect without trying to restore with xrecovery my phone was back to working like it should with all my apps and multi touch ect working! so baseband is the next thing i will look at flashing....... Thanks again
Baseband 54 works for Rendero's rom.
agentJBM said:
Baseband 54 works for Rendero's rom.
Click to expand...
Click to collapse
Our use the patch with any 2.2 based rom. I'm on miui now with .55 and the patch and it works perfectly
I bought my phone almost a week ago, but I only have a 7 day return policy so I need to figure this out quickly.
It's the C6802, bought in China (where I live), with HK firmware 1.4.1.B.0.475. Naturally, right when turning on the phone, it says to update to 532. The phone shop merchant did this for me when I bought it via PC (not sure what software he used), and afterwords the phone would suddenly just go dead and restart.
So I went back to stock 475, worked fine. Once home, I tried firmware 526, using flashtools, to see if it was stable, and same deal. The seller I bought it from says all the other firmwares are really buggy and I should just wait until there is a newer firmware to upgrade. But by that time, I won't be able to return the phone if indeed the problem IS the phone and not the firmware.
I was able to unlock the bootloader, root the phone, and install CWM, but every time I try to use CWM (whether backup, restore, or just navigating), after a couple seconds, the phone goes dead and restarts (same problem when using other firmware). I tried to install TWRP via goodplay, and that didn't work at all. I'm not sure how to flash it so I can use it during recovery because CWM doesn't work and I haven't seen an img of it for the z ultra (I'm still pretty noob at this as you can probably tell).
So does some firmware just bug out on some phones, like in my case, and will future firmwares fix this random death/restart? Do I just have extremely bad luck with CWM and firmware? Or is it a hardware problem and I should return the phone? Or is there a way to update to 532 and fix the crash problems? My first born for some expert advice.
The software you need to update on your PC is the Sony PC Companion suite. It should not prompted you to install it when you first plugged your phone in to your PC. Download that & see if you can update to 532 through there before you try anything else. To me it sounds like a bad flash & redoing it may resolve your issues. Hopefully...
Nuwidol said:
The software you need to update on your PC is the Sony PC Companion suite. It should not prompted you to install it when you first plugged your phone in to your PC. Download that & see if you can update to 532 through there before you try anything else. To me it sounds like a bad flash & redoing it may resolve your issues. Hopefully...
Click to expand...
Click to collapse
OK, I'll do that first thing tmrw morning, right now I'm making back-ups of everything using titanium and nandroid. But I can only use them when the phone is on, they don't work during recovery, nothing does. And using TWRP even with the phone on just causes it to die and reboot as soon as I click "OK" - is this something to be concerned about? It still rebooting even with CWM (in recovery) and TWRP (in normal bootup), even with stock 475 firmware, this certainly shouldn't be normal, right? I'll update how the PCC flash to 532 goes tomorrow...
I agree with Nuwidol, it does sound like a bad flash...
To put thing simple, forget CWM / TWRP for the moment, try 'CLEAN' install your phone with the latest firmware (532), then test using it for a day or two and see if it works properly. Yes, all firmwares released by Song so far for this phone are kind of buggy but nothing serious - just minor issues I would say, and definitely not random death or restart like you said.
To clean install, I like using SUS (Sony Update Service) because, unlike PC Companion which packs with a whole bunch of functions, SUS only deals with one thing, to reinstall or update firmware for your phone, and it works well.
First, backup whatever you find important, then relock you bootloader (restore from your TA partition backup, and flash back any stock FTF... stuff like that...).
Hook up your phone with SUS by following its instruction. Choose 'erase / format everything (...or something like that)' when it provides you with update options. Sit and wait until it finishes.
Turn on your phone, skip WiFi setting as well as the Google account, go straight to Home. Then:
'Settings' --> 'Backup & reset' --> 'Factory data reset'
Choose 'erase / format everything' (or something like that) again.
After reboot, you should have a very clean system by now. Use it as is for a few hours / days and see if anything strange comes up. If nothing strange comes up, then your phone is fine; if not, go return it or ask for exchange.
One minor note, rooting the phone is ok, pretty straightforward and safe to do I would say. But unlocking the bootloader? Well... it is ok too, unless you know what you're doing.
Hope this help.
so far so good
littopillo said:
I agree with Nuwidol, it does sound like a bad flash...
To put thing simple, forget CWM / TWRP for the moment, try 'CLEAN' install your phone with the latest firmware (532), then test using it for a day or two and see if it works properly. Yes, all firmwares released by Song so far for this phone are kind of buggy but nothing serious - just minor issues I would say, and definitely not random death or restart like you said.
To clean install, I like using SUS (Sony Update Service) because, unlike PC Companion which packs with a whole bunch of functions, SUS only deals with one thing, to reinstall or update firmware for your phone, and it works well.
First, backup whatever you find important, then relock you bootloader (restore from your TA partition backup, and flash back any stock FTF... stuff like that...).
Hook up your phone with SUS by following its instruction. Choose 'erase / format everything (...or something like that)' when it provides you with update options. Sit and wait until it finishes.
Turn on your phone, skip WiFi setting as well as the Google account, go straight to Home. Then:
'Settings' --> 'Backup & reset' --> 'Factory data reset'
Choose 'erase / format everything' (or something like that) again.
After reboot, you should have a very clean system by now. Use it as is for a few hours / days and see if anything strange comes up. If nothing strange comes up, then your phone is fine; if not, go return it or ask for exchange.
One minor note, rooting the phone is ok, pretty straightforward and safe to do I would say. But unlocking the bootloader? Well... it is ok too, unless you know what you're doing.
Hope this help.
Click to expand...
Click to collapse
Litto... your awesome. This has probably been one of the single most helpful replies in my history on xda. I did everything you said, step by step, and I was able to flash 532 without any problems, and so far, after using it for half a day, it's been completely stable. Granted, I haven't installed a single app on it yet or synced anything, I'm hesitant, ha. But I'll do that tonight, and Lord willing, nothing will happen. But so far so good. You really helped me a ton, thanks so much. :victory:
As for the issue about unlocking the bootloader, well, I did it because I was told that is the only way you can install custom ROMs and CWM? So for flashing anything besides stock, I would think it's pretty much mandatory, am I wrong? I hope to install radioactive or paranoid android eventually, but of course with it crashing during CWM and any firmware upgrade, that wasn't an option before. I'll use it for awhile longer with the stock (but rooted) 532 and if no problems occur, I'll move onto flashing the CWM/TWRP img by krabappel, which means then I can finally flash a custom ROM. Here's hoping...
Forgive my novice status with both my first Android phone and this site. Galaxy S6 which I rooted using Odin and I believe a kernel it was, from here.
If I run the os upgrade from Smartswitch, what effect will that have one the phone as far as being rooted and all the stuff I've done since being rooted. Thank you very much.
If you update, you will lose root. I would not update via Smart Switch, being that you are rooted with a custom kernel. Your best bet would be to update via Odin. Check the subforum here @ xda for your variant of the S6 for further info. You should find what you need in the General forum of that subforum.
es0tericcha0s said:
If you update, you will lose root. I would not update via Smart Switch, being that you are rooted with a custom kernel. Your best bet would be to update via Odin. Check the subforum here @ xda for your variant of the S6 for further info. You should find what you need in the General forum of that subforum.
Click to expand...
Click to collapse
Thank you sir. Is it simply a matter rerooting the device? Or will every other change I made from root be gone too?
It will wipe your phone, so you will have to redo any mods or settings.
es0tericcha0s said:
It will wipe your phone, so you will have to redo any mods or settings.
Click to expand...
Click to collapse
It wipes the phone every time you do an operating system update? Why would anybody ever do it unless something wasn't working? Unless it's only when rooted? I have good pc skills and some understanding of Linux even, but man I have a lot to learn about these phones.. What about Smart Switch backups? It wipes the phone, how close to before the update will that get somebody? I don't have time to research all this. I may just leave it. This update I'm talking about is a gigabyte btw. That seems pretty huge for a phone.
It wipes the phone when you update via Odin (unless modded by a dev to not wipe for some versions). The reason that this needs to be done is that when you are rooted and have changed system files, OTA updates usually cause issues like bootloops / soft brick. Typically when you have a Samsung with a modded kernel and system, the regular Samsung tools like Kies and Smart Switch fail. Your results may vary, but I would have the firmware downloaded to reload via Odin in case that does not work. I am not familar with Smart Switch as it just came out for the S6 and newer stuff and I have never had use for Samsung's tools like that because I prefer to use Google and Titanium Backup to backup and restore my apps, contacts, texts, call logs, etc. As far as the updates go, 1 GB is actually kind of small for newer versions. It's probably bigger once unzipped. Some newer phones have systems that are well over 2 GBs. Most people here usually update via custom rom as it's easy to do on the phone once you have a working custom recovery and doing a factory reset there will not wipe the internal storage @ /data/media. If you prefer to be stock rooted, there most likely is a version already posted in the subforum for your phone. If you are updating whole Android versions and not minor updates, it might be required to install additional firmware files with Odin or Chainfire's Flashfire tool. If so, the developer will mention that in the OP of the thread.
es0tericcha0s said:
It wipes the phone when you update via Odin (unless modded by a dev to not wipe for some versions). The reason that this needs to be done is that when you are rooted and have changed system files, OTA updates usually cause issues like bootloops / soft brick. Typically when you have a Samsung with a modded kernel and system, the regular Samsung tools like Kies and Smart Switch fail. Your results may vary, but I would have the firmware downloaded to reload via Odin in case that does not work. I am not familar with Smart Switch as it just came out for the S6 and newer stuff and I have never had use for Samsung's tools like that because I prefer to use Google and Titanium Backup to backup and restore my apps, contacts, texts, call logs, etc. As far as the updates go, 1 GB is actually kind of small for newer versions. It's probably bigger once unzipped. Some newer phones have systems that are well over 2 GBs. Most people here usually update via custom rom as it's easy to do on the phone once you have a working custom recovery and doing a factory reset there will not wipe the internal storage @ /data/media. If you prefer to be stock rooted, there most likely is a version already posted in the subforum for your phone. If you are updating whole Android versions and not minor updates, it might be required to install additional firmware files with Odin or Chainfire's Flashfire tool. If so, the developer will mention that in the OP of the thread.
Click to expand...
Click to collapse
It just occurred to me. Firmware IS the Android OS on these phones. That's not the same as a kernel though? With the regular Linux os it isn't. Forgive my ignorance. Like I say this is my first one.
Unfortunalely, firmware is one of those terms that can mean a few different things depending on the situation (like flashing). Firmware in this instance refers to the bootloader and modem files as well for Samsungs. If you don't have the bootloader and modem files (which roms do not install) correctly matched to the OS then you might have issues like not being able to boot or cell service issues.
es0tericcha0s said:
It wipes the phone when you update via Odin (unless modded by a dev to not wipe for some versions). The reason that this needs to be done is that when you are rooted and have changed system files, OTA updates usually cause issues like bootloops / soft brick. Typically when you have a Samsung with a modded kernel and system, the regular Samsung tools like Kies and Smart Switch fail. Your results may vary, but I would have the firmware downloaded to reload via Odin in case that does not work. I am not familar with Smart Switch as it just came out for the S6 and newer stuff and I have never had use for Samsung's tools like that because I prefer to use Google and Titanium Backup to backup and restore my apps, contacts, texts, call logs, etc. As far as the updates go, 1 GB is actually kind of small for newer versions. It's probably bigger once unzipped. Some newer phones have systems that are well over 2 GBs. Most people here usually update via custom rom as it's easy to do on the phone once you have a working custom recovery and doing a factory reset there will not wipe the internal storage @ /data/media. If you prefer to be stock rooted, there most likely is a version already posted in the subforum for your phone. If you are updating whole Android versions and not minor updates, it might be required to install additional firmware files with Odin or Chainfire's Flashfire tool. If so, the developer will mention that in the OP of the thread.
Click to expand...
Click to collapse
What I'm wondering is if there's any to have this galaxy s6 just like it is now after many hours of tweaking after one of these updates. I couldn't make heads or tails out of Titanium update.
You are being very helpful sir. Thank you.
Depends on what tweaks you've done and which update that it is. If it is a minor security update, then usually someone will post a flashable via custom recovery version and often you can get away with installing that over your current system while just wiping cache and dalvik cache. If it is a major update, like when Marshmallow comes out, it would benefit you to do a factory reset before updating. Yea, it sucks having to set up your phone again, though with all the tools available, it's really not that bad, but better to start fresh instead of wondering if the phone is slow or buggy because you didn't.
es0tericcha0s said:
Depends on what tweaks you've done and which update that it is. If it is a minor security update, then usually someone will post a flashable via custom recovery version and often you can get away with installing that over your current system while just wiping cache and dalvik cache. If it is a major update, like when Marshmallow comes out, it would benefit you to do a factory reset before updating. Yea, it sucks having to set up your phone again, though with all the tools available, it's really not that bad, but better to start fresh instead of wondering if the phone is slow or buggy because you didn't.
Click to expand...
Click to collapse
You're making sense. I totally get it. (about starting from scratch) Can I then re-root it with the same UniKernel-v5-920P-072715.tar as before or will I need a new one of those too.? Thanks again.
This is the update SmartSwitch is telling me is available. I don't even know which of this stuff we've been discussing this is. Firmware, ROM or OS update.
Current version: PDA:0H1 / CSC:0H1/ PHONE:0H1 (SPR)
Latest version: PDA:011 / CSC:011 / PHONE:011 (SPR)
Size: 1612 MB
That's just a minor security update. I would not use that kernel to reroot. I believe the only option available for the update you are on and the update that is available is via TWRP + SuperSU zip.
es0tericcha0s said:
That's just a minor security update. I would not use that kernel to reroot. I believe the only option available for the update you are on and the update that is available is via TWRP + SuperSU zip.
Click to expand...
Click to collapse
Whatsa TWRP + SuperSU zip Is that a tool and file for getting this update?
Sorry man. I've had this phone for less than 2 months and it's my very first one.
I do appreciate your patience. I've been a PC support guy for 16 years. I know what it's like.
TWRP = Team Win Recovery Project. It replaces the stock recovery that the phone uses to perform factory resets and updates signed by Samsung. This allows you multiple benefits such as complete system/data/kernel backups, being able to wipe any combo of system/data/caches/internal storage, factory data reset without wiping internal storage, terminal commands, and installing custom files, roms, mods, etc not signed by Samsung to name a few. SuperSU is the popular root binary and root permissions app made by the developer Chainfire. If you needs links, I can provide, but assuming you're familiar with Googling things being a support guy. ☺
es0tericcha0s said:
TWRP = Team Win Recovery Project. It replaces the stock recovery that the phone uses to perform factory resets and updates signed by Samsung. This allows you multiple benefits such as complete system/data/kernel backups, being able to wipe any combo of system/data/caches/internal storage, factory data reset without wiping internal storage, terminal commands, and installing custom files, roms, mods, etc not signed by Samsung to name a few. SuperSU is the popular root binary and root permissions app made by the developer Chainfire. If you needs links, I can provide, but assuming you're familiar with Googling things being a support guy.
Click to expand...
Click to collapse
I have SuperSU already.
These are some truly terrible directions unless you already know enough to not need them.
https://twrp.me/devices/samsunggalaxys6sprint.html
Will installing TWRP effect the root method I've already used?
Will installing recovery effect any of the multitude of configurations I've already done?
Does this then allow manual installs of OTA updates without losing root or any of your configuration customizations?
Is it JUST the recovery partition were dealing which stands alone from the os?
Does Nandroid backup then encompass the recovery and os and rom etc? Meaning are they all backed up and custom recovery via TWRP was what made that possible? Or do you have to make your current config the recovery itself in order to do a ghost style backup and restore if you jack yourself up later? OR is not even this a ghost style restore?
Maybe it's just me, but the terminology is very confusing and I can't make heads or tails of what I'm even talking about with all this.
Tried to make backup with TWRP...
I guess whatever I flashed it with last time won't let it boot into recovery or the bootloader or whatever it's called. If I tell TWRP manager to reboot and do backup it just goes to the menu for rebooting and wiping cache etc. If I specifically go to "reboot to bootloader" it just reboots into android. I went to install a custom recovery and it said that if the location for the recovery is wrong it could brick the phone. I have no idea if it's right or wrong or if the root method I've already used is effecting this or not.
Installing a custom recovery will not affect your OS or any settings (as long as the recovery version is compatible with your phone and update). It is installed in a different partition than where the OS resides. It will not let you install official OTA zips. It is only for installing files not directly signed with Samsung's special key. When you do a nandroid backup, it will give you options on which parts of the phone you would like to backup. The important ones are boot, system, data, and EFS (though this is not typically needed when you restore, just as a precaution because it holds important data and settings of your IMEI and such - only restore if needed). Boot is the kernel, which controls many drivers for stuff like wifi, BT, CPU and GPU processes as well as others. System contains preloaded software, as in if you just restored boot and system, it would be like you factory reset the device and would need to setup your accounts and settings. Data is the apps, data, settings you have changed or added. A factory reset in the stock recovery would also wipe your /data/media storage which your phone sees as your internal storage. TWRP allows a factory reset that skips this so you will not lose the stuff you have accumulated on the phone such as pictures, music, downloads, etc.
The reason that when you are using TWRP Manager to install the recovery and reboot to it and it is still stock is probably due to the system has a script built in that notices if you change the recovery and will rewrite the stock recovery back to it upon rebooting. You can avoid this by renaming the script with a root enabled file browser. You will find this script in /system/etc/install-recovery.sh (or something similar). Just rename it to something like install-recovery.sh.bak.
es0tericcha0s said:
Installing a custom recovery will not affect your OS or any settings (as long as the recovery version is compatible with your phone and update). It is installed in a different partition than where the OS resides. It will not let you install official OTA zips. It is only for installing files not directly signed with Samsung's special key. When you do a nandroid backup, it will give you options on which parts of the phone you would like to backup. The important ones are boot, system, data, and EFS (though this is not typically needed when you restore, just as a precaution because it holds important data and settings of your IMEI and such - only restore if needed). Boot is the kernel, which controls many drivers for stuff like wifi, BT, CPU and GPU processes as well as others. System contains preloaded software, as in if you just restored boot and system, it would be like you factory reset the device and would need to setup your accounts and settings. Data is the apps, data, settings you have changed or added. A factory reset in the stock recovery would also wipe your /data/media storage which your phone sees as your internal storage. TWRP allows a factory reset that skips this so you will not lose the stuff you have accumulated on the phone such as pictures, music, downloads, etc.
The reason that when you are using TWRP Manager to install the recovery and reboot to it and it is still stock is probably due to the system has a script built in that notices if you change the recovery and will rewrite the stock recovery back to it upon rebooting. You can avoid this by renaming the script with a root enabled file browser. You will find this script in /system/etc/install-recovery.sh (or something similar). Just rename it to something like install-recovery.sh.bak.
Click to expand...
Click to collapse
You sir, are one patient and helpful man I very much appreciate your suffering through my whining. Interestingly, the boot loop just stopped in it's own and now I have the TWRP interface in place of the stock menu where the option was to wipe the cache partition.
Does this THIS mean I have a custom recovery now? Meaning, a different restore image than the one that came with the phone? Or does this now let me install that?
About this....
You were saying up HERE that if I run this update with smart switch I would lose root, but if I use TWRP to do it, I won't? Is that right? Thanks again.
Tiribulus said:
You sir, are one patient and helpful man I very much appreciate your suffering through my whining. Interestingly, the boot loop just stopped in it's own and now I have the TWRP interface in place of the stock menu where the option was to wipe the cache partition.
Does this THIS mean I have a custom recovery now? Meaning, a different restore image than the one that came with the phone? Or does this now let me install that?
Click to expand...
Click to collapse
This should mean that the recovery is installed. You can verify by using the app to boot to recovery or via powering the phone on by holding the Power, Volume Up, and Home buttons together as you restart. You should notice a recovery booting message in the top left and then you can let go of the buttons. Once there, you should perform a backup of the boot, system, and data partitions. If you have an EFS option, I would back that up too for safe keeping. It's rare that it would get corrupted, but best to have a backup just in cause.
If you update via Smart Switch, you will definitely lose root, as well as TWRP. Most likely, a developer has posted a rooted version of the update that you can use TWRP to install.
So I was looking into this a little closer for you and realized that the preferred method of updating and rooting the update you are trying to get involves using Odin to install the full update package, then reflashing TWRP, and using a newer version of the kernel to root. However, from some of the user comments about it, it seems like it might be better to wait till Samsung has released the source code of the kernel for the OI1 update. The kernels based on the slightly older 5.1.1 builds will work, but some people were experiencing random issues such as reboots or other oddities. I don't think OI1 has anything in it that would be worth losing root over or possibly having things run oddly. The alternative would be to update via a rom like this http://forum.xda-developers.com/spr...ment/ram9200-ofe-rom-thread-v3-5-1-1-t3173417
So I rooted my Galaxy Grand Prime (SM-G530W android 5.1.1) following this guide: skyneel .com/ root-samsung-galaxy-grand-prime-sm-g530w
Odin gave it a pass and everything works fine and it boots. Except for the part where it boots to a blank homescreen (just the wallpaper that I can't interact with) and then loads the lockscreen like 5 minutes later. I can unlock it from there and access only apps that are in my task manager which include settings and snapchat. I get about 2 minutes before settings crashes, and then all I can access is the lockscreen for a bit until it starts working again. My phone constantly vibrates as everything crashes one by one (it gives me the unfortunately x has stopped message; things like media storage server, contacts, touchwiz crash). I can access camera but cant take pictures because media storage crashes. Same with phone but contacts crashes. I've tried clearing the cache partition but that didn't help. SuperSU IS on my phone
TLDR: rooted phone, now everything is crashing constantly, making phone pretty much unusable. Lock screen and notification center is all that works consistently
I did make a backup before using this guide: techrepublic .com/article/how-to-create-a-full-backup-of-your-android-device-without-root/
Sounds like you might not be on the correct build that that root guide is meant for. Did you confirm that you were on the G530WVLU1AOFB update as shown in Settings > About Phone > Build Number? If so, a factory reset might help. If not, that's what caused this and you will need to reload the original firmware via Odin and root with the method for your particular update.
es0tericcha0s said:
Sounds like you might not be on the correct build that that root guide is meant for. Did you confirm that you were on the G530WVLU1AOFB update as shown in Settings > About Phone > Build Number? If so, a factory reset might help. If not, that's what caused this and you will need to reload the original firmware via Odin and root with the method for your particular update.
Click to expand...
Click to collapse
Yes, I did make absolute that I do have that exact version. I'm currently downloading my stock firmware from SamMobile (I'm with Fido/Canada).
Are you saying to factory reset then try and root again?
It should be rooted already. My suggestion is to reset it now. If that does not work, then flash the stock firmware via Odin and try again.
es0tericcha0s said:
It should be rooted already. My suggestion is to reset it now. If that does not work, then flash the stock firmware via Odin and try again.
Click to expand...
Click to collapse
By reset it, do you mean through settings?
And if I reset it, can I restore from backup? I have some game progress that I don't really want to lose
Yes, or through recovery. Depends on what kind of backup and what kind of game it is as to whether it can be restored.
es0tericcha0s said:
Yes, or through recovery. Depends on what kind of backup and what kind of game it is as to whether it can be restored.
Click to expand...
Click to collapse
It's an adb backup done through android sdk
I dunno what the game is or what kind of backup it supports, so couldn't tell you. Either way, I doubt your phone will be fixed without doing some kind of reset. Either via factory reset or reloading the firmware with Odin, which often resets the phone as well, though it depends on the firmware.
es0tericcha0s said:
I dunno what the game is or what kind of backup it supports, so couldn't tell you. Either way, I doubt your phone will be fixed without doing some kind of reset. Either via factory reset or reloading the firmware with Odin, which often resets the phone as well, though it depends on the firmware.
Click to expand...
Click to collapse
Does the reset keep root?
A factory reset will, but not if you reload the firmware via Odin. Root is placed in the /system partition and a factory data reset wipes /data.
Alright, I'm factory resetting now
Okay apparentlty I'm not root after the factory reset.
Alright, I rooted again, and now it works. Thanks.
Unrelated, but which SDK do I download for Xposed framework? I know it's SDK22, but I'm not sure between arm, arm64, and x86 (for a SM-G530w)
up up up
http://forum.xda-developers.com/grand-prime/help/g530-t3302883
Hello everyone. As you saw in the title my right speaker(or lower one) isn't working properly. It sounds like 25% of the left one (or above one). I noticed that after I flashed stock ROM thru flashtool and I wiped everything and also I ticked MASTER-RESET in TA section. I've flashed XGEN rom thinking it would fix the problem without a success. AFAIK I should still have my guarantee and ofc I can't find my TA Backup anywhere.
What I am thinking right now, if reflashing with flashtool again will fix the problem. And if it won't, should I relock my bootloader without TA and send it to my carrier to try to fix the problem? Also is there anyway to see if your drm stuff is missing when bootloader is locked other than testing camera and etc. Hope you understood me and could help me fix the issue.