Database Users

[Q] Rooting and CWM in EU?

Hi there,
i'm a bit confused now. My Xoom (German Wi-Fi only, MZ604) should arrive this week and i wanna root it and flash the eos ics-nightly, but from what i've read, there are different root-methods for us and non-us devices and CWM-versions with and without sd-card support.
So, what mehtod is best for rooting? universar xoom root or xoot? and if xoot, what are the benefits of converting to an GDE-device? when rooted, i can flash every rom anayway, or am i wrong?
Second Question: When i root via universal xoom root, i'll have the taiamt recovery, right? so this will be the eos/tiamat recovery, which supports sd-cards? and can i use this CWM together with a regular installation of rom manager?
What about the rouge CWM? this one should also have sd-card support, right? can this also be used together with a regular rom manager or not?
The only thing i should avoid is flashing CWM via rom manager, correct?
Sorry for all the noobish questions, but this is quite different from the DHD handling

root via universal root(I prefer it)
http://forum.xda-developers.com/showthread.php?t=1242241
yup you will have the tiamat recovery
there are currently tow recoveries supported
1.) Rogue recovery
2.) solarnz recovery
I use the rogue recovery as it gives more options(ex flashing from internal sd card along with external)
but both are awesome
No you cannot use the recovery which comes with Rom Manager...
it does not detect the external sd , yup avoid flashing CWM with Rom manager
Advantages of GED device..
all i can say is that it receives update directly from google and the updates come alot faster
and you will have stock android ie no custom ui's like motoblur or so

thank you for the answer
so the work order will be root via universal root, flash the rouge recovery and flash the custom rom (and if needed flash google apps), correct?
GED isnt needed because aosp roms dont get updates from vendors or google.
Last question: should i install rom manager for nandroid management (if rom manager works with rouge cwm) or should i avoid rom manager at all and do backups directly through recovery?
thanks for the help

[Q] GT-I9505 - ROM Manager App / Flashing Co-exist

Hi. I installed ROM Manager from the Play store and also paid for ClockworkMod Touch mode inside the app. Within the app I installed ClockworkMod Recovery which seemed to be confirmed however upon recovery reboot I had no option to backup and no indication that it was not the standard recovery reboot interface. I tired that several times. I then flashed the CWM_6.0.4.7_Touch_GT-I9505 tar file (from the official ClockworkMod website) using Odin. Now, I do have the proper recovery reboot with all the options and ClockworkMod branding /touch capability.
Within the app now however I have the status 'current recovery: ClockworkMod 5.X.X.X. and i am notified upon opening the app that a newer version is available. This is despite the fact that when I review 'Recovery already installed' I get the status 'ROM Manager has been set up to use your existing recovery installation'. This happens when I click 'jflte' as my phone model - the only one listed (which I'm not sure it is), or, 'device not listed above'.
The second backup I have made has been timestamped 31 December 1979 23:00 (not the name of the file which is 1970-10-15.14.68). I'm pretty sure the first backup which I deleted was actually timestamped 1970.
I am a noob and have sort of accidentally got into this and spent time I don't have however I would be very grateful to learn:
1/Do I need the ClockworkMod app? Is the flash I did with Odin enough? How do the two relate? Co-exist? and is the imprecision within the app about the version in use a problem?
2/What's up with the incorrect timestamping? How can I fix this?
3/ General question - could anyone summarise the difference between /mnt/sdcard or extSdCard and /storage/sdcard or exSdCard which is a distinction I have broadly come across since rooting?
Thanks for reading. If I have posted in the wrong section please advise/moderate. I've looked within the app and on the Play Store /web for ROM Manager specific support however I can't find an obvious forum/contact. Again, please point out if I am missing it and direct me.
Best wishes.

In order to get on with my life I simply flashed the latest TWRP recovery using Odin. I have successfully made a backup from recovery reboot.
- Is there anything I can do to check I don't have problems given I did nothing to remove CWM and assumed TWRP would flash 'over' it?
- Does anyone actually vouch for the TWRP Manager app? Play reviews are mixed...

^^^^

You will have No problem with flashing TWRP over CWM.
I have never used an app for twrp or cwm in 3 years of android. I guess you dont need them.
Gesendet von meinem GT-I9505 mit Tapatalk

[Q] Converting my GT-I9505 into (almost) Google Edition

Hi guys, I have read a bit about rooting and flashing custom roms for the GSIV but being my first time (on this phone) I thought it would be better to ask for some help from you experts ^_^
I would like to convert my GSIV as close as possible to a Google Edition one, in the sense that I don't want to have a super custom ultra cool rom, I just want a stock-like one, stock kernel, maybe a few extra features, root, nothing special...
Now, is it possible to do that without voiding warranty, or at least with the possibility to turn back the phone in a warranty covered state?
Could you point me to one simple guide to do so and maybe suggest a rom suited to my needs? It can get a bit confusing, there's too much complicated stuff for a newbie!
Thank you in advance!

Yes, it is possible to convert the i9505 (almost) completely to a Google Play device (though you will not receive OTA updates, so you'll have to download them yourself). It's fairly easy once you have a custom recovery installed.
Though, warranty might be an issue. In many countries, it will be void once you root and install a recovery, though this does vary. This also increments a "counter" in the device, so even if you restore it to its original state, it is still possible to see that you have at some point modified the software (although there are methods to root the device without incrementing the counter, not to mention that many have managed to claim warranty despite this). That said, this will again differ based on your country.
Now, if you're still up for it, there are several guides online which can tell you how to root and install a recovery on the phone. If you're running the stock 4.4.2 firmware from Samsung, then you can follow this guide to root:
samsungsfour.com/tutorials/root-samsung-galaxy-gt-i9505-s4-running-on-android-4-4-2-kitkat.html
Thereafter, you can install a custom recovery from
gadgetsacademy.com/install-cwm-twrp-recovery-on-galaxy-s4-lte-i9505/
(These are just two of the links which you get after a Google search)
Note that you don't really need root for this, just the custom recovery. Though, having root is a nice addition if you want to back up your apps using Titanium Backup.
Once that is done, you can download a Google Play based ROM from here on XDA, such as
http://forum.xda-developers.com/showthread.php?t=2557353
or
http://forum.xda-developers.com/showthread.php?t=2544474
Just reboot into recovery, wipe data, and select the zip file from your sd-card/internal storage.
Though, remember to backup your apps/data first.

Takenoko_, thank you so much for the detailed answer, it has been really helpful! One question, if I understood correctly, it is possible to install a custom recovery WITHOUT rooting, so if I did this and then flashed a rooted ROM I should have root in the end, right?

That's right. As you'll be using Odin, root should, at least in theory, not be needed to install a custom recovery. You can instead gain this by flashing a pre-rooted ROM

Great, all done! Thank you!

No problem

yes you can
just install custom recovery, (philz i like)
then flash dandvh rom
done
it comes rooted
----------
sorry i forgot
in some cases, you need to update modems by flashing
or just update your s4 to 4.4.2 then flash the gpe rom

Rooting Kindle Fire HDX 7 32 GB 3rd Gen Fire OS 13.3.2.1 Wrapup

Rooting Kindle Fire HDX 7 32gb 3rd Gen Fire OS 13.3.2.1
Airplane Mode ON WIFI Off
Kindle Fire ADB Composite Drivers must be installed to working PC
In KFHDX Settings
Set Enable ADB - ON
Set Apps from unknown sources - ON
Faznx's KF-HDX Toolkit v0.95
https://www.androidfilehost.com/?fid=95832962473395302
KFHDX ToolKit v0.95.zip
MD5: 3C1D7DB855E54A39BF2FD59BE6ABA9DC
SHA-256: 614A0D077BEC8B85F6D6B377D2D18EB719AB9ED15B08B41CD5 8968BEED653C0C
Rooted KFHDX using Towelroot in above toolkit. - No Issues
Then applied:
1> SuperSU v2.14 installer in Faznx's KF-HDX Toolkit v0.95 - No Issues
2> Over the air update blocker and re-enabler for all current rootable versions in Faznx's KF-HDX Toolkit v0.95 - No Issues
Airplane Mode ON WIFI Off
Use adb to install ES File Explorer
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
ADB install (installs application) -- adb install c:\com.estrongs.android.pop.apk - No Issues
Checked in ES File Manager to make sure I had root.
Next rename the /system/etc/security/otacerts.zip file - one issue - resolved
Even though I ran the disable OTA updates, I am concerned that some post I have read said their system was update even though they renamed.
I think now it's possible they get around us by running an MD5 hash on files in that folder and compare to the hash they store for that version.
The better idea may be to move that file out of that folder. I did just that.
Here are the directions to rename:
see the contents of that folder with adb shell ls -Ral /system/etc/security
Example:
C:\Users\davcam\AppData\Local\Android\sdk\platform-tools>adb shell ls -Ral /system/etc/security
/system/etc/security:
drwxr-xr-x root root 2014-02-07 04:23 cacerts
-rw-r--r-- root root 1337 2014-02-07 04:23 otacerts.zip
Before you can rename this file you must set the \ and \system file systems to r/w - then you can rename or mv the file.
When completed, change \ and \system file systems back to ro
Next : Safestrap
https://goo.im/devs/Hashcode/thor/safestrap/
I tried Safestrap-Thor-3.72.apk and it did not seem to work. I unistalled recovery and Safestrap-Thor-3.72.apk.
I was able to successfully install Safestrap-Thor-3.75-os3.2.4-B02.apk, install recovery, boot into recovery, backup up stock, create a new rom slot,
change to that Rom slot and restore stock backup into that slot.
Now on startup i get the Safestrap screen.
One thing I noticed was that the stock values for the rom slots are a little small, so keep that in mind.
Thanks to everyone on XDA Forums, especial to EncryptedCurse for the terse, meaningful tips., Faznx's KF-HDX Toolkit v0.95, Geohot's Towelroot,
hashcode0f's Safestrap, OTA disable, and Supersu.
Current Status:
Using a copy of stock on a somewhat larger partition, no otacerts.zip file
Next steps:
0> Thank and donate to the developers I mentioned above.
1> Airplane mode OFF, wifi ON , register with Amz
1.1> Get GAPPS installed on this copy of stock I'm booting into
2>to see if possible to load a CM11 image into one or my bran new slots.
Question: If Amazon were able to push an update to me, would I just be able to recover to my stock image and move on?
Thanks for the help and education!

reggie9 said:
Next steps:
0> Thank and donate to the developers I mentioned above.
1> Airplane mode OFF, wifi ON , register with Amz
1.1> Get GAPPS installed on this copy of stock I'm booting into
2>to see if possible to load a CM11 image into one or my bran new slots.
Question: If Amazon were able to push an update to me, would I just be able to recover to my stock image and move on?
Thanks for the help and education!
Click to expand...
Click to collapse
Dont try to install CM11 with Safestrap!! It wont work, and you will brick your device! You have to install TWRP 2.8.4.0 and only then you can install CM11 safely.
If your device get FW 4.X.X, you lost root and ability to install custom roms through custom recovery (Safestrap, TWRP 2.8.4.0) - and only way to get the root again is rollback from 4.x.x to 3.2.7-8 (by amazon tech support), and then you can use only Safestrap, so no CM11 or Nexus 2.0.4 ROMs for FW 3.2.7-8!

Edit: Looks like jeryll already said it.

jeryll said:
Dont try to install CM11 with Safestrap!! It wont work, and you will brick your device! You have to install TWRP 2.8.4.0 and only then you can install CM11 safely.
If your device get FW 4.X.X, you lost root and ability to install custom roms through custom recovery (Safestrap, TWRP 2.8.4.0) - and only way to get the root again is rollback from 4.x.x to 3.2.7-8 (by amazon tech support), and then you can use only Safestrap, so no CM11 or Nexus 2.0.4 ROMs for FW 3.2.7-8!
Click to expand...
Click to collapse
Thanks! I appreciate the heads up. Any idea where I can locate TWRP 2.8.4.0 for this device?
Sorry - Found it here: http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-twrp-2-8-1-0-thor-t2986004
Reggie9

jeryll said:
Dont try to install CM11 with Safestrap!! It wont work, and you will brick your device! You have to install TWRP 2.8.4.0 and only then you can install CM11 safely.
If your device get FW 4.X.X, you lost root and ability to install custom roms through custom recovery (Safestrap, TWRP 2.8.4.0) - and only way to get the root again is rollback from 4.x.x to 3.2.7-8 (by amazon tech support), and then you can use only Safestrap, so no CM11 or Nexus 2.0.4 ROMs for FW 3.2.7-8!
Click to expand...
Click to collapse
Everything has seemed pretty clear up to now, but I am trying to understand what I should do next? I have Safestrap 3.72 beta installed and I'm running off of a backup of stock running in ROM-Slot 1.
Do I need to wipe rom slot one, remove recovery and uninstall Safestrap? Then install TWRP? Can I take a backup of my current ROM Slot one and use it in TWRP. I am looking for a good install post or video for installing TWRP 2.8.4.0 on KFHDX. It appears that TWRP does not use the concept of ROM slots but actually wipes the main system (that has been backed up to the builtin recovery area?) Then installs an image on the main system? I understand basically what Safestrap is doing, but not TWRP.

reggie9 said:
Everything has seemed pretty clear up to now, but I am trying to understand what I should do next? I have Safestrap 3.72 beta installed and I'm running off of a backup of stock running in ROM-Slot 1.
Do I need to wipe rom slot one, remove recovery and uninstall Safestrap? Then install TWRP? Can I take a backup of my current ROM Slot one and use it in TWRP. I am looking for a good install post or video for installing TWRP 2.8.4.0 on KFHDX. It appears that TWRP does not use the concept of ROM slots but actually wipes the main system (that has been backed up to the builtin recovery area?) Then installs an image on the main system? I understand basically what Safestrap is doing, but not TWRP.
Click to expand...
Click to collapse
You are on compatible firmware so dont complicate things so much If you want to understand how Safestrap or TWRP itself work - google is your friend, you will certainly find plenty of information about how things works: here is little introduction about differencies between them, not all of course...
And here is little something from ggow about how to install twrp and remove safestrap, you can later find safestrap slot image files in data/media/safestrap - and after you have functional TWRP 2.8.4.0, you can delete safestrap folder safely and free some space taken by these image files
Normal way is how TWRP 2.8.4.0 works (IMHO) - only one big playground managed by mighty TWRP recovery always accessible by shortcut when you made mistake and need to repair something...
Safestrap uses multiple slots for (un)modified stock roms simply because is too dangerous to play with stock rom on systems with locked bootloader, so you can play with slot rom instead of stock where small mistake leads to different types of bricks - some repairable, some not
And yes you can make a backup of your current ROM and use it later with TWRP, but here comes catch, Safestrap only backups system and data partition, not boot (contains kernel), so I recommend after you install your preferred CM11 or Nexus 2.0.4, restore only DATA part of your backup

jeryll said:
You are on compatible firmware so dont complicate things so much If you want to understand how Safestrap or TWRP itself work - google is your friend, you will certainly find plenty of information about how things works: here is little introduction about differencies between them, not all of course...
And here is little something from ggow about how to install twrp and remove safestrap, you can later find safestrap slot image files in data/media/safestrap - and after you have functional TWRP 2.8.4.0, you can delete safestrap folder safely and free some space taken by these image files
Normal way is how TWRP 2.8.4.0 works (IMHO) - only one big playground managed by mighty TWRP recovery always accessible by shortcut when you made mistake and need to repair something...
Safestrap uses multiple slots for (un)modified stock roms simply because is too dangerous to play with stock rom on systems with locked bootloader, so you can play with slot rom instead of stock where small mistake leads to different types of bricks - some repairable, some not
And yes you can make a backup of your current ROM and use it later with TWRP, but here comes catch, Safestrap only backups system and data partition, not boot (contains kernel), so I recommend after you install your preferred CM11 or Nexus 2.0.4, restore only DATA part of your backup
Click to expand...
Click to collapse
jeryll - Thanks for the the thoughtful response - will study this. - reggie9

Samsung Galaxy Core Prime SM-G360P TWRP issues

Hello everyone,
I am posting today to bring up the subject of the SM-G360P variant of the Samsung Galaxy Core Prime.
I am having issues with getting TWRP custom recovery to work properly on my device. I am able to flash twrp-3.0.2-0-coreprimelte.img onto my device and it works except for 2 things that i have noticed that makes me very upset and i cant figure out what to do. When i enter recovery mode the back light does not function so i have to use a bright flashlight to see any of the options and the second problem is the GUI is upside down but the button mapping is in the proper place so i have to guess on where to tap on my screen. This makes it very frustrating to use especially when i want to wipe dalvik cache and the regular cache. I accidentally factory reset my device once by tapping the wrong spot. If anyone would be willing to help me out with my problem i am willing to be a guinea pig with anything you can try for the custom recovery to make the GUI reflect the proper button mapping and the back light to work. I can re-flash my device as many times as necessary to get a working custom recovery. I have included the recovery.fstab and the stock recovery along with the version of TWRP custom recovery i have been utilizing to an extent.
I am using the BST Australian variant of SM-G360P which can be rooted with Kingo Root and KingRoot. I used Kingo Root so i could use the SuperUser app rather than just using KingRoot. I have used CROM Service to unlock my bootloader. I have also tried to use CWM custom recovery on my device but it does not register the CWM custom recovery that is available for my device it just goes to a "fake" Odin mode screen. I would really love to get TWRP custom recovery working properly. I have tried to port both TWRP and CWM custom recoveries by using Android Image Kitchen but have not had any success at creating a recovery that works without the same issues i have with TWRP custom recovery. I am running 4.4.4 KitKat OS which is the latest update for SM-G360P and have full root permissions. If you need any other dump files or any other information i will gladly give it to you. I may need directions on how to do some things though.
I will be greatly appreciative if someone would have a look at what the problem may be with TWRP custom recovery and my Variant of SM-G360P. Please help. Thank you for your time and contribution.

Hello @sosthenisRR. I just got this device, the Boost Prevail LTE American version. I was wondering if you've made any headway finding a TWRP for it. I will be trying some things myself... Gotta have TWRP... And I wanted to let you know that if you root with kingroot, super-sume (free version) works to get you supersu.

Odin TWRP 2.8.7.0 for the SM-S820L...it works, i tried V3 as well with no favorable results.
https://forum.xda-developers.com/galaxy-core-prime/development/twrp-2-8-7-0-sm-g360p-t3462592

eeriikk said:
Odin TWRP 2.8.7.0 for the SM-S820L...it works, i tried V3 as well with no favorable results.
https://forum.xda-developers.com/galaxy-core-prime/development/twrp-2-8-7-0-sm-g360p-t3462592
Click to expand...
Click to collapse
If that doesn't work, install and run this apk, this is what finally allowed me to Odin TWRP to my G360P without errors. Now if only we could get a custom ROM for this variant...