Related
I might be doing it wrong...I'm not an expert with this particular device, but I have managed to root and install custom Roms on an Augen Gentouch, a Nook Color, and a Samsung Moment before I got my G2.
I love the G2, and it took me a while to get up to speed on the lingo for this particular device...but I'm sorta getting it.
Last night I went to work in earnest to root and flash my phone with a custom ROM. Once I found the gfree tutorial and learned what s-off was and all that good stuff, I finally managed to achieve permaroot. Cool.
So I grab Clockwork Rom Manager, which I hear can really make my life easy...unfortunately I had no luck flashing any custom ROMs from there at all. I downloaded each one from the app, rebooted into recovery (yes, it was the most current version), and tried to flash a CM7 nightly. Ended up in an endless boot animation loop.
So I decide maybe I'm pushing my luck w/ Gingerbread as a first custom ROM...so I go in and try the CM6.1 ROM I also had in the downloads folder for Rom Manager. Different logo, another loop. Thinking I'd semi-bricked my device, I start diving in some more. Hey cool...I can use HBoot to flash a stock image back. I do so, and I have a blank, working device. Ok, back to square one.
So yeah...re-root with a clean phone, install Rom Manager, download and flash CM6 and again with the boot loops. :-/
So I'm wondering what I'm doing wrong. Am I supposed to have to navigate to the .zip file when flashing? I mean, when I got to recovery and it didn't start flashing, I assumed I needed to choose and load the ROM of my choice from the clockworkmod/downloads/ folder, but maybe I'm doing it wrong? In any case, I'd love to be able to run one of these snazzy custom ROMs, but for now I'm just gonna have to be happy with permaroot and the Bacon Bits .zip and the kernel that comes with that. Overclocking is nice...I'm eager to try Gingerbread though.
Any thoughts?
I was tring to follow what you have done but got a little confused , do you have a custom recovery flashed? ie. CWM recovery 2.5.1.3. If yes, are you wiping /data and /cache before flashing the custom rom in recovery?
How to flash the rom manually:
Install custom Rom to the root of sd card (and gapps.zip for CM roms)
Boot into recovery
Make a back up of your current rom
wipe data/factory reset
wipe cache partition
go into Advance setting
wipe dalvik cache
return to main menu in recovery
select " install zip from sd card"
select "choose zip from sdcard"
select the rom you want to flash from sdcard
and flash it
if flashing CM Rom you also must flash the gapps .zip
go back to choose zip from sdcard
select "gapps.zip"
flash it
go back to main menu in recovery
select "rebooot system now"
Should boot into the custom Rom you flashed.
If you want to flash Gingerbread roms you need to flash CWM recovery 3.0.0.5, do not mistake this with Rom Manager v3.0.0.7.
Yah u probibly used clockwork 2.1.5 for gingerbread/cm7 Clockwork 3 is stricktly for ginger
Sent from my Toaster
Ah, ok...that makes more sense (all the stuff that needs to be cleared first, etc...). As far as recovery, it looks like I have 3.0.0.0. how do I get 3.0.0.5? I had to do a little hack mentioned in another thread to get 3.0.0.0 on there...do I need to find and rename the .zip for CWR and have ROM Manager flash it? Or is there an official way to do it?
I think you have to flash CWM3.0.0.5 with fastboot.
read the first post in this CM7 thread.
http://forum.xda-developers.com/showthread.php?t=916796
Thanks for the help guys! I started fresh, flashed back to stock, rooted with gfree, and installed CM6.1.1. I am an absolute convert. Cyanogen is utterly brilliant!
I've since installed a custom kernel, OC'd to 1.4Ghz (scaling on demand), flashed Clockwork Recovery 3.0.0.5, eng hboot, and a new radio. I think I've got my head wrapped around this phone now...and I LOVE IT! I'm really tempted to try CM7, but I'm coming off a phone with some real issues (Samsung Moment), and I'm trying to relax and enjoy a stable build for now...but yeah...holy crap is CM awesome! Thanks for the help...XDA is really a great community!
I have a AT&T samsung galaxy S3 rooted by using the samsung galaxy toolkit http://forum.xda-developers.com/showthread.php?t=1746665
I'm interested in flashing the following CM10 Nightly rom http://forum.xda-developers.com/showthread.php?t=1778270 to my phone but have a few questions before I proceed.
1) What precautions should I take before flashing a custom rom? I understand I first need to make a nandoid backup (which I have done) and verify that I have the correct rom for my specific phone model that I will be flashing to. If I were to choose the CM10 Nightly rom, the link from the post goes to http://get.cm/?device=d2att which appears to be correct for my AT&T Samsung Galaxy S3 SGH-1747.
2) Since I flashed with the samsung galaxy toolkit, it flashed the following recovery "CWM-Based Recovery v5.5.0.4 - Do I need to use a different recovery in order to use the CM10 Nightly roms or is this one compatible? If not, how do I go about changing to another recovery?
3) What is the steps for flashing properly? Would I need to update kernel or model or just simply download rom, save to SD card, boot to recovery, then flash the rom in zip form?
I appreciate any your responses in advance. I tend to over analyze and I feel i've read enough about the process of flashing custom roms but I want to be certain. Thank you!
It looks like you got all you ducks in a row, on behalf of the community thanks for being a smart user :good:.
1) You nailed it....make absolutely certain you are downloading the correct software for your device, flashing an incompatible ROM can leave you with a really sexy, expensive paper weight. The d2att identifier is unique to the AT&T variant of the SG3 (i747). Before you flash any new rom or kernel (or anything else for that matter in my opinion) make a nandroid or equivalent backup from your recovery. I do this even for the smallest mod, tweak, theme whatever if for nothing else incase i dont like it it an easy undo 'button'. Besides that i like to keep a fairly recent backup on something other than my phone.
2) For all intensive purposes that version of CWM will work, atleast currently. I would recommend you update it however as that version is several builds behind and there are sometimes updates in the more current ROM builds that may not play nice with older recoveries. The easiest way to do this is download Clockwork Rom Manager from the play store, on the main app screen at the very top is the option to install the latest recovery. It will download, preferably on wifi to minimize downloading errors as much as possible, and then install automatically. There is also atleast one other alternative recovery that i know of, TWRP, which is worth checking out in my opinion. Just keep in mind the backups from the different recoveries are NOT interchangeable.
3) It always best to follow any and all directions in the OP of whatever ROM you are installing as most differ. The generally accepted order for flashing goes something like this although everyone will have an opinion on this i'm sure. ROM > Gapps (if required by the rom) > Reboot > Kernel > Reboot. If you are really concerned you can always just flash one at a time allowing a full reboot in between each flash, personally i think this is overkill but thats just my opinion.
One last personal suggestion, I always keep a copy of my rom, kernel, and any required supporting software on my external sd just in case. It comes in handy if for some reason you try something that doesn't work out the way you had hoped and you are away from a computer and your phone is unable to boot into android. Some would argue that a nandroid makes this unnecessary but with 32 gigs in my current setup its not like im hurting for space. Hope this helps to clarify some things for you, good luck!
dntesinfrno, Thank you very much for your reply and kind words
A lot of the information has been posted on the boards but it can be a little confusing and too much information at once.
You mentioned that I can simply use Rom Manager then click "Flash ClockworkMod Recovery", are there any reports of there being problems in using rom manager to flash the recovery or is the S3 fully supported?
As for the kernel flashing.. I'm really only interested in flashing custom roms (CM10), is it necessary to flash the kernel as well when flashing custom roms? I didn't see anything on the other thread stating anything about flashing kernels so i'm guessing it's not needed?
I'm for sure going to take your recommendation and make a backup of current rom and kernel. Would you recommend Rom Manager to backup the current rom? I see an option that says "Backup current rom" in the application. How do you go about backing those up?
Thank you again! :fingers-crossed:
since I have the cwm-based recovery v5.5.0.4 i'm wondering if I were to use rom manager and flash the latest clockworkmod recovery, would it actually stick after the reboot?
found the following thread here and it looked almost identical to mine: http://forum.xda-developers.com/showthread.php?t=1801534&highlight=cwm-based+recovery
Ended up using rom manager to flash clockworkmod and after rebooting multiple times and booting into recovery, the official clockworkmod recovery is installed. (showing "ClockworkMod 6.0.1.2" now)
As for backing up kernel and everything else, will rom manager do that as well?
Thank you
Hey guys/gals,
I recently bought a Koodo Galaxy s2x. After a few weeks I looked online and saw that there were some JB Roms for my phone. I couldn't resist and tried to flash one after rooting. I didn't have many problems with it, but there were some glitches that started to bug me, so I decided to see about going back to stock (I should have done this first I know). So then after hours(many) of searching, the best I could find was a T-Mobile stock Rom I decided to try and flash it (both times via odin). I also read somewhere that I should use darkside superwipe to clear my cache, so I tried that, but ever since that CWM stopped working on my phone. anytime I tried to do any back up or anything it just froze, and I had to hard boot. Finally I just tried flashing T-Mobile stock ICS, and Odin said "Failed". I decided to just unplug my phone, as I thought I already screwed it up, but after rebooting, the T-mobile Rom worked. I don't understand why it works fine if the Flash Failed. Now, I can no longer connect to kies (I'm hoping official JB will be shipped soon!), and I am wondering if I can somehow return to a stock Koodo Rom, and if it will connect to Kies again, as it previously had. I have looked a lot and have not found anything that I fully understand. I'm not overly experienced, which is why I should not have flashed to begin with. This is the closest thread I have found to help me, but I don't fully understand what all I need to do:
"Haven't seen anyone shared this yet.
Here's the KOODO ICS 4.0.4 stock ROM I used CWM to flash to stock after I tried the custom ROM.
h t t p s : / / sourceforge.net/projects/koo...d.zip/download
I also flashed DARKSIDE.SUPER.WIDE before I flashed this or you can used CWM Recovery 6.0.1.2 to wipe system and cache."
Is it possible for me to get back to stock phone? and still connect to Kies? and then possibly upgrade to JB through Kies if Hercules ends up receiving it?
Thanks for any help you can give me. Here is all my current phone info incase this helps:
Model:
SGH-T989
Android Version:
4.0.3
Baseband version:
T989DTLLG2
Kernel version:
3.0.8-perf-T989UVLE1 -CL508451
[email protected] #1
SMP PREEMPT Sun May 6 15:07:07 KST 2012
Build number:
IML74K.UVLE1
Thanks.
If your ultimate goal is to get Jellybean on your phone, check the development section of this subforum. There are numerous stable and wonderful JB roms (AOKP Milestone 6, Liquid Smooth, CM10).
To get back to your stock ROM, download it from here: https://sourceforge.net/projects/koo...d.zip/download
Then, go into recovery (NOT odin), and flash the rom.
arcsine said:
If your ultimate goal is to get Jellybean on your phone, check the development section of this subforum. There are numerous stable and wonderful JB roms (AOKP Milestone 6, Liquid Smooth, CM10).
To get back to your stock ROM, download it from here: h t t p s ://sourceforge.net/projects/koo...d.zip/download
Then, go into recovery (NOT odin), and flash the rom.
Click to expand...
Click to collapse
That link doesn't work, it says cannot find page. Also, my phone is currently not rooted, does it have to be rooted to flash from recovery? if not what do I do to flash from recovery? I know how to get into recovery, but after that do I use 'apply update from external storage'? Do I have to wipe the cache first?
Thanks.
PS: I just want to be able to get back to stock for now. At least until I learn more about flashing Roms. There is still lots for me to learn, like kernels, radios, Nightly's for official Roms, or even how to properly flash a rom without feeling lost. If I know a way to get back to stock comfortably, It will give me more reason to try some other Roms (once I learn how).
Here is a working link to the stock Koodo ROM: http://sourceforge.net/projects/koodostock/files/KOODO_SGH-T989D_Stock_Signed.zip/download
Are you running a custom ROM right now or your stock ROM? If you're running a custom ROM, it should come with root privileges. If you are running the stock ROM, you can just back it up instead of needing to download the zip from sourceforge. This guide will help you get rooted: http://galaxys2root.com/t-mobile-galaxy-s2/how-to-root-icsgb-on-t-mobile-galaxy-s2-sgh-t989/. After rooting, get into recovery mode (if you can't get the button combinations to work, there is an app. called quick boot which reboots you into recovery/bootloader/etc). If you don't have a recovery or it's corrupt, download ROM manager from google play, and choose the 'install clockwork recovery'. Reboot to recovery to make sure it works, then uninstall rom manager (it's been known to cause bugs if you use it for other things - and I'd recommend other recoveries such as TWRP but it's a bit more advanced). From your recovery's screen, there should be a backup option. Make a complete backup and name it something appropriate. To flash a ROM, download it and put it on your storage drive. Reboot to recovery, and go to wipe. Wipe your data (factory reset), and system (only really need to wipe data in most cases, but be safe). To flash the custom ROM now (or flash the default ROM I just linked), there should be an option to 'install zip from sd card' or something similar. Choose that, browse to your ROM and install it. After installing, go to wipe and wipe your cache+dalvik cache, then reboot. There are several beginner guides sticked in the development forum, along with explanation of terms like radio/kernel/nightly/etc.
arcsine said:
Here is a working link to the stock Koodo ROM:
Are you running a custom ROM right now or your stock ROM? If you're running a custom ROM, it should come with root privileges. If you are running the stock ROM, you can just back it up instead of needing to download the zip from sourceforge. This guide will help you get rooted:. After rooting, get into recovery mode (if you can't get the button combinations to work, there is an app. called quick boot which reboots you into recovery/bootloader/etc). If you don't have a recovery or it's corrupt, download ROM manager from google play, and choose the 'install clockwork recovery'. Reboot to recovery to make sure it works, then uninstall rom manager (it's been known to cause bugs if you use it for other things - and I'd recommend other recoveries such as TWRP but it's a bit more advanced). From your recovery's screen, there should be a backup option. Make a complete backup and name it something appropriate. To flash a ROM, download it and put it on your storage drive. Reboot to recovery, and go to wipe. Wipe your data (factory reset), and system (only really need to wipe data in most cases, but be safe). To flash the custom ROM now (or flash the default ROM I just linked), there should be an option to 'install zip from sd card' or something similar. Choose that, browse to your ROM and install it. After installing, go to wipe and wipe your cache+dalvik cache, then reboot. There are several beginner guides sticked in the development forum, along with explanation of terms like radio/kernel/nightly/etc.
Click to expand...
Click to collapse
Thanks a ton... Worked perfectly! I'm hoping it will connect to Kies once again.. I'll let you know if it works.
Unfortunately, I still can't connect to Kies.. It just sits at the Loading status (for like 10-15 mins). But At least I don't have all of the T-mobile apps and stuff anymore!
Hi all,
I need some expert advice to fix my phone
I would like to flash a custom ROM on my N7105T.
For those who don't know, the 'T' means that I bought my phone through my carrier, which is Telstra in Australia. Telstra seem to bring out their own variations of mobiles; when I bought my Galaxy Nexus it had a 'T' at the end of the model number too, and when I rooted and flashed custom ROMs on that I just always kept the radio coz the radio was supposed to be optimised for their network. So other than that I did the same as everyone else
So I was thinking the same with my Note2. I would like to flash a custom N7105 ROM.
What I have done so far is this:
* I was running that APK that roots and patches the exploit, but I have since deactivated that and uninstalled.
* I then followed step 2, in the 2nd post from here: http://forum.xda-developers.com/showthread.php?t=2032849
The procedure completed, but when I try to boot into recovery, I get the usual boot logo for a second but then the screen goes all crazy and then nothing.
I thought the issue could have been the fact that from the thread above the directions say to flash CWM that is for the N7100, so I downloaded Rom Manager and tried it that way. So it flashed CWM again but I have the same issue.
I did a little searching and found people talking about TWRP, so I tried that, but again have the exact same issue.
I have no idea what I have done wrong... I am a little on the noob side, and even though I flashed custom ROMs on my SGN and my Galaxy S2(a very long time ago) I just can't remember what I did in the past, and can't work out what I need to do to fix my problem.
In case it helps, here is some more info on my phone:
* Currently running stock ROM - 4.1.1
* Stock Kernel
* Build # JRO03C.N7105TDVALK4
* Status says it is modified
Please let me know if more info is needed.
thanks
dean
Download and flash this philz recovery with Odin
http://www.mediafire.com/file/usj6wefv6liy4ll/philz_touch_3.99-n7105.tar.md5
if you have bootloop , wipe cache and data from recovery
If nothing work then flash stock ROM for your device.
dr.ketan said:
Download and flash this philz recovery with Odin
http://www.mediafire.com/file/usj6wefv6liy4ll/philz_touch_3.99-n7105.tar.md5
if you have bootloop , wipe cache and data from recovery
If nothing work then flash stock ROM for your device.
Click to expand...
Click to collapse
Thank you Dr! If my memory serves me correct, it was a guide you wrote that I followed to flash a custom ROM on my old GS2! :good:
I am downloading right now... Am I right in assuming that when I follow your guide, I just replace the CWM file with the one I am downloading now?
yeah it is just recovery and nothing else, it won't replace anything other than recovery.
I have read somewhere Cf auto root also should work, you may need to wipe. but anyway you need CWM so i gave you link for CWM recovery.
otherwise re flash CF auto root then wipe cache and data.
dr.ketan said:
yeah it is just recovery and nothing else, it won't replace anything other than recovery.
I have read somewhere Cf auto root also should work, you may need to wipe. but anyway you need CWM so i gave you link for CWM recovery.
otherwise re flash CF auto root then wipe cache and data.
Click to expand...
Click to collapse
YOU ARE THE MAN!!!!!!!
Thanks so much for your help! I am currently looking at my phone in recovery! Now I gotta find a good custom ROM to try
Another quick question though... The bottom half of the screen lists what looks like two issues; They are to do with failing to mount, and both report the issue to be failing to mount exfat /dev/block/mmcblklpl /external_sd
Would you know if this is going to be a real issue?
I think you can forget the last question about failing to mount.... I remembered that I don't have an external SD card so I think it would be safe to say that that is why it can't mount it!
Hey guys
I am completely new in this topic. I just got an Samsung Galaxy Tab S (SMT700 Wifi) as a present a few days ago. Its my first android device I had so far.... so everyone will call me "noob" and I am okay with it DD
When I realised that there are different android os development projects like CM and Paranoid, I become interested in trying them out. so...
1.) Is it possible to brick the android device completely or is there something like an recovery/dfu mode in iOS devices?
2.) Can I go back to the stock OS contributed bey samsung itself (Touchwiz Kitkat)? If yes are this files online?
3.) Does I need special hardware to perform a custom rom flash? (micros card/special OS on pc (linux,....)
4.) Does the CM blck mod in the official forums contains alle required drivers and blobs already to perform gpu tasks and so on? (are there currently downsides swell?)
Thx :fingers-crossed:
androidnoob222 said:
Hey guys
I am completely new in this topic. I just got an Samsung Galaxy Tab S (SMT700 Wifi) as a present a few days ago. Its my first android device I had so far.... so everyone will call me "noob" and I am okay with it DD
When I realised that there are different android os development projects like CM and Paranoid, I become interested in trying them out. so...
1.) Is it possible to brick the android device completely or is there something like an recovery/dfu mode in iOS devices?
2.) Can I go back to the stock OS contributed bey samsung itself (Touchwiz Kitkat)? If yes are this files online?
3.) Does I need special hardware to perform a custom rom flash? (micros card/special OS on pc (linux,....)
4.) Does the CM blck mod in the official forums contains alle required drivers and blobs already to perform gpu tasks and so on? (are there currently downsides swell?)
Thx :fingers-crossed:
Click to expand...
Click to collapse
1. There is bootloops but hardbricks are rare. You can enter recovery and download mode(flash stock rom on broke os) in a bootloop. Just hold power, home or vol up for recovery and home +power +vol down for download mode.
2. Yes you can go back to any version of stock os unlike apple you have to be on the latest. The files are online for your device at sammobile. (google it) and also samsung updates.
3. All you need to perform a custom rom flash is a custom recovery called twrp and your device. Theres an app on google play for installation of it. (search on youtube on how to do so). But thats just flashing zip based roms(which most custom roms are). For stock rom installation, you will need a pc and a application called odin 309 to flash a stock md5 file rom in which you will need to be in download mode (like installing new update from itunes).
You will need to backup your whole rom with twrp before flashing a custom rom. You may need a micro sd if your short on space. You will also need to be rooted to install custom roms. Please go to the cfautoroot thread of your device to root your device in which you will viod warrenty.
4. Cm rom as of now still has bugs but is still useable for games and such. There should be a list of bugs on the thread and might have some missing features such as ir blaster and finger print scanner. Battery life may vary. So there are downsides.
5. I can go into more depth of custom stuff and flashing if you wish. Right now my fingers hurts xD. Hope this helps!
1) it is very, very unlikely even if you try intentionally to do so
2) yes, no problem. google for Samsung Firwares, it's all online
3) windows PC, Odin Software, and an USB cable, that's all. You can do it with Linux if you prefer. Some Roms are installed via zip file from the device itself, then you need to flash a new Recovery partition first, that is able to do so
4) ?
Thx you very much for the help !
After reading a lot about this topic it seems to be not as difficult as I thought it would be.
But I don't get one thing. Why does I need to make a proper backup only for the flashing propos? If I flash my internal memory, all data will be replaced. And if it goes wrong I will be able to do a complet software reset with odin and the original samsung image found in the Internet?! So why I have to make a backup (there is no data in my current tap I will need in the future)?
And does the cf chain root flash the OS or the firmware ?
As my understanding tell me that the firmware is something comparable to a bios , which should never be flashed to maintain stability.
So as my logic goes further if my device is rooted, after a proper reset it will not be rooted anymore? (Android stock reset function in settings)
Or does armbased devices not have a normal firmware/bios as I mentioned ? And something in the bootprocess itself is manipulated to anable root access?
Hopefully you get what i mean :angel:
androidnoob222 said:
Thx you very much for the help !
After reading a lot about this topic it seems to be not as difficult as I thought it would be.
But I don't get one thing. Why does I need to make a proper backup only for the flashing propos? If I flash my internal memory, all data will be replaced. And if it goes wrong I will be able to do a complet software reset with odin and the original samsung image found in the Internet?! So why I have to make a backup (there is no data in my current tap I will need in the future)?
And does the cf chain root flash the OS or the firmware ?
As my understanding tell me that the firmware is something comparable to a bios , which should never be flashed to maintain stability.
So as my logic goes further if my device is rooted, after a proper reset it will not be rooted anymore? (Android stock reset function in settings)
Or does armbased devices not have a normal firmware/bios as I mentioned ? And something in the bootprocess itself is manipulated to anable root access?
Hopefully you get what i mean :angel:
Click to expand...
Click to collapse
1. Sometimes odin and kies will fail for you. Twrp backups is to be really safe if you get bootlooped and odin fails for you. Its much easyer to restore a twrp backup and easy to make one. Its just if odin or kies fails which twrpnwould be your only hope. Just in case
2. Cfautoroot only flashes supersu and root. It keeps your apps and everything. So when you flash cfautoroot, it will say andriod is upgrading becuase its installing root and restoring back your apps.
3. After a full proper reset, it will not have root and revert back to stock. Thats where you flash cfautoroot to gain root again!
Hope this helps!
So as of now I managed to root my device and also created a twrc backup, which is now transfered to my sd card
Are there major differences between a rom flash with twrc recovery or odin?
androidnoob222 said:
So as of now I managed to root my device and also created a twrc backup, which is now transfered to my sd card
Are there major differences between a rom flash with twrc recovery or odin?
Click to expand...
Click to collapse
Most custom roms are to be flashed with twrp. Meanwhile stock roms/md5 is to be flashed with odin(firmware from website).
Again Thx you very much!! You are awesome!
I managed to install cyanogenmod its insanely fast compared to the touchwiz version
But there is one more thing I have to ask.
I installed TWR in the latest version but the klimwifi (2.8.XX) version (klimtwifixx was not avaible). Is this the right version?
Where exactly does TWR be installed. Afther the wipe and the format it stays, so I have no clue how it can be available even if the internel memory was formated?
I started TWR by the terminal (reboot recovery), becouse I have no clue how to start it instead by button pressing?
And there are no playstore how can i get it on cm11?
androidnoob222 said:
Again Thx you very much!! You are awesome!
I managed to install cyanogenmod its insanely fast compared to the touchwiz version
But there is one more thing I have to ask.
I installed TWR in the latest version but the klimwifi (2.8.XX) version (klimtwifixx was not avaible). Is this the right version?
Where exactly does TWR be installed. Afther the wipe and the format it stays, so I have no clue how it can be available even if the internel memory was formated?
I started TWR by the terminal (reboot recovery), becouse I have no clue how to start it instead by button pressing?
And there are no playstore how can i get it on cm11?
Click to expand...
Click to collapse
2.8 is the latest version of twrp. I dont think your device is klimwifixx. It should be klimwifi. What the wipe and and factory reset in twrp does is that it clears all your apps and wipe cache. It does not wipe any folders and it justs wipes your apps. So internal should not be affected unless you formatted it... You just need to swipe the factory reset on it when installing roms. For google play store you have to flash a file name gapps. There should be a link to it on the thread. To get into recovery, turn off your device, then hold power, home, vol up buttons at the same time to enter recovery. To exit recover just touch the reboot rectangle and hit reboot system. Hope this helps!
Okay now its clear TWRP replace the "downloade mode", which is the standard recoverymode
You said I do not need to format the disk, but why?
In linux distributions (debian for example) you will have similliar structure for example /var /bin /sbin /usr /proc,.....
If there is the stock touchwiz android it will have this structure listed above as well. So it will courrupt the os by overwriting this folders by a custom rom....
. Maybe you wont do it in the TWRP menue, because it will do it automatically by choose you custom rom install script in the zip?
How is the portioning in those devices? Maybe there are /dev/sda1 (android) and /dev/sda2 (with the recovery setup inside)....? I just want to understand those things
androidnoob222 said:
Okay now its clear TWRP replace the "downloade mode", which is the standard recoverymode
You said I do not need to format the disk, but why?
In linux distributions (debian for example) you will have similliar structure for example /var /bin /sbin /usr /proc,.....
If there is the stock touchwiz android it will have this structure listed above as well. So it will courrupt the os by overwriting this folders by a custom rom....
. Maybe you wont do it in the TWRP menue, because it will do it automatically by choose you custom rom install script in the zip?
How is the portioning in those devices? Maybe there are /dev/sda1 (android) and /dev/sda2 (with the recovery setup inside)....? I just want to understand those things
Click to expand...
Click to collapse
No no! Twrp replaces stock recovery. Download mode cannot be replaced. You enter it by holding power, vol down, home button when the device is off. Download mode is when you flash things. Recovery mode is when you clear cache or other stuffs. I have no idea with the linux stuff you explained but custom zip roms just adds some modifications and other stuff to the device. You would need to clear cache and factory reset so you wont have problems installing it. You can easyly go back to stock rooted by restoreing a backup you made in twrp. It has to do something with img and replacing those if thats what your talking about idk. No need to format as the rom add things to it. Just need to factory reset and cleae caches.
But now if I want to enter download mode for testing, it will boot into the twrp recovery. So as for me it looks like that it is already replaced..
androidnoob222 said:
But now if I want to enter download mode for testing, it will boot into the twrp recovery. So as for me it looks like that it is already replaced..
Click to expand...
Click to collapse
It shouldnt be as twrp only replaces recovery. Img did you try doing home, power, vol down?
Hi
I have a quick question I have the Galaxy tab S 10.5 wifi and was wondering can I install TWRP without the tablet being rooted?
Also there are some builds where it states that its rooted, debloated and de-knocked. Does this mean that they can be flashed without rooting the tablet and tripping knox.
Thanks for your replies, still trying to get my head around this.