Related
Hi,
I had a Wildfire S a few months ago, which I had owned for about 4 months (The Wildfire S was terrible) so I decided to root it.
To say I was happy after I had rooted was an understatement, I flashed CM7 onto the device, which extremely improved the phone.
The problem was, as soon as I flashed it, i started developing problems (not rom caused) such as a constant noise when in calls etc.
Now, my question is I own a HOX, which is an absolute epic phone to say the least.
I really want to use Vipers ROM / PerfectAndroid etc, but am so worried about rooting the HOX.
Is it worth rooting the HOX? What can go wrong and what can I expect to happen if I develop issues? (LIKE LAST TIME )
Thanks in advanced.
Wilks3y said:
Hi,
I had a Wildfire S a few months ago, which I had owned for about 4 months (The Wildfire S was terrible) so I decided to root it.
To say I was happy after I had rooted was an understatement, I flashed CM7 onto the device, which extremely improved the phone.
The problem was, as soon as I flashed it, i started developing problems (not rom caused) such as a constant noise when in calls etc.
Now, my question is I own a HOX, which is an absolute epic phone to say the least.
I really want to use Vipers ROM / PerfectAndroid etc, but am so worried about rooting the HOX.
Is it worth rooting the HOX? What can go wrong and what can I expect to happen if I develop issues? (LIKE LAST TIME )
Thanks in advanced.
Click to expand...
Click to collapse
All of the ROMS for the HOX are really good, if you're worried might I suggest ARHD as it's the closest ROM to stock there is, aside from Maximus ROM.
If you follow my guide (in my sig) then the rooting will be okay
It's really not that hard
The-Last-Hylian said:
All of the ROMS for the HOX are really good, if you're worried might I suggest ARHD as it's the closest ROM to stock there is, aside from Maximus ROM.
If you follow my guide (in my sig) then the rooting will be okay
It's really not that hard
Click to expand...
Click to collapse
Thanks for your reply mate, I know rooting isnt a huge process in itself. Its just knowing that if (when?) something goes wrong with my phone, im totally screwed for the warranty.
Which may cause me not able to get replacement/fixed under warranty?
Wilks3y said:
Thanks for your reply mate, I know rooting isnt a huge process in itself. Its just knowing that if (when?) something goes wrong with my phone, im totally screwed for the warranty.
Which may cause me not able to get replacement/fixed under warranty?
Click to expand...
Click to collapse
unlocking your boot loader will void you warranty, but if you have a fault less hox like i got then go for it
Sent from my Transformer TF101 using xda app-developers app
Is it worth it? Always personal ofcourse. Do you want to make backups? Lots of customizations? Just root to delete some system-apps or to install an add-blocker? Get the bloody fast Jelly Bean?
In my opinion: GO FOR IT
I don't know how old your One X is, but perhaps it's wise to wait a couple of weeks to see you have any faults.
Wait one or two weeks to see if it has any faults.
If it's faultfree then go root it
I tested mine 12 days before unlocking the bootloader.
Sent from my HTC One X using xda app-developers app
It's not actually true that it'll void your warranty. Well not completely anyway, more often than not HTC will honor the warranty if it's a hardware issue, if it's software and it's messed up because you fscked up your HOX then it's on your own head... but it's incredibly hard to do so, it's pretty hard to completely brick a phone if you read and follow the guides and if you manage to brick it then you shouldn't even be holding it!
At least that's the general consensus nowadays...
Huubs said:
Is it worth it? Always personal ofcourse. Do you want to make backups? Lots of customizations? Just root to delete some system-apps or to install an add-blocker? Get the bloody fast Jelly Bean?
In my opinion: GO FOR IT
I don't know how old your One X is, but perhaps it's wise to wait a couple of weeks to see you have any faults.
Click to expand...
Click to collapse
My HOX is about 2 months old now, and seen no issues what so ever. I want to be able to customise it to be honest, thats about it. It runs smooth and fast as it is, but I get bored of things so easy and the Sense UI etc is boring me to death now .
And thats another thing putting me off rooting mate, JellyBean is (Should be) just around the corner? So don't know whether to wait, or Root
Flo95 said:
Wait one or two weeks to see if it has any faults.
If it's faultfree then go root it
I tested mine 12 days before unlocking the bootloader.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I have had my phone longer than that, but still very very worried about rooting.
The-Last-Hylian said:
It's not actually true that it'll void your warranty. Well not completely anyway, more often than not HTC will honor the warranty if it's a hardware issue, if it's software and it's messed up because you fscked up your HOX then it's on your own head... but it's incredibly hard to do so, it's pretty hard to completely brick a phone if you read and follow the guides and if you manage to brick it then you shouldn't even be holding it!
At least that's the general consensus nowadays...
Click to expand...
Click to collapse
Ah I see, do you know of any cases where the hardware has gone wrong, and HTC have still honored the warranty even though they were rooted?
Was reading a thread of someone having a convo with HTC, and they adimantly stated that if the bootloader is unlocked you are not covered by warranty, and my understanding is that the bootloader HAS TO BE LOCKED to be rooted?
Thanks all !
It is worth doing it, yes.
I waited tree months staying on stock, but rooted, then i decided to install ARHD 2.3.2. Stock was already very good but a custom rom gives the HOX the rest to be the best phone on market. Battery life increases, the handling is even more fluid and laggless as before.
What can going wrong? Well, the most common failure is to forget flashing boot.img as a separate step, because this is unusual against the procedure done with desire or others.
Also restoring a nandroid backup also requires to flash boot of the backup separately. If you keep the boot images at your PC and the ROM Zips on your device, you are well prepared to do this.
Hi mate,
Yes I will make sure to back EVERYTHING up. I have a couple more questions.
I have seen people saying flash RUU, Flash Kernal, etc.
I don't know what the RUU is and im not very informed about Kernals, I know the ROM is the OS, the Kernal is the Driver? I think (NOT A CLUE ABOUT RUU)
And I have heard of battery life getting drained much quicker etc after root? Or people developing signal problems etc.
Finally, if I do root, and decide I don't like it, can I revert to stock and retain warranty?
Again thanks for all the help so far guys !
had 3 phones...last one had a big gap on the left hand side and had issues with power button. had phone unlocked and rooted...left the phone unlocked but flashed back the stock rom that came with the phone...send it to the repair center and the phone came back brand spanking new and still unlocked and everything was covered by the warranty. as long as you do not fry the motherboard due to overclocking and you are careful what you flash and take time to read and search of what you want to do i say you are good to go mate...and like i said few minutes ago to someone else..if you want to customize and love playing with different themes then Viper is your rom...if you want a clean cut rom but still with the tweaks from Viper then ARHD or Renovate are the great roms and far more faster if you ask me...
plus do not forget there is MIUI based on sense framework which for me is awesome and has so many themes and lockscreens to play with and also JB roms to
Goku80 said:
had 3 phones...last one had a big gap on the left hand side and had issues with power button. had phone unlocked and rooted...left the phone unlocked but flashed back the stock rom that came with the phone...send it to the repair center and the phone came back brand spanking new and still unlocked and everything was covered by the warranty. as long as you do not fry the motherboard due to overclocking and you are careful what you flash and take time to read and search of what you want to do i say you are good to go mate...and like i said few minutes ago to someone else..if you want to customize and love playing with different themes then Viper is your rom...if you want a clean cut rom but still with the tweaks from Viper then ARHD or Renovate are the great roms and far more faster if you ask me...
plus do not forget there is MIUI based on sense framework which for me is awesome and has so many themes and lockscreens to play with and also JB roms to
Click to expand...
Click to collapse
Bah everyone is telling me to Root it, like I said yeah I wan't customisation with themes etc, which Viper has really drawn me into, but on the other hand I want a clean and bugless rom, that just WORKS GREAT.
Thanks for your example of warranty, thats sorted my head out a bit.
Will probably take the plunge within the next few days, and give it a go.
Just building my confidence up to do it !!
THANKS SO MUCH EVERYONE !
Wilks3y said:
Bah everyone is telling me to Root it, like I said yeah I wan't customisation with themes etc, which Viper has really drawn me into, but on the other hand I want a clean and bugless rom, that just WORKS GREAT.
Thanks for your example of warranty, thats sorted my head out a bit.
Will probably take the plunge within the next few days, and give it a go.
Just building my confidence up to do it !!
THANKS SO MUCH EVERYONE !
Click to expand...
Click to collapse
no problem my friend. here is a good start up guide for you
http://forum.xda-developers.com/wiki/HTC_One_X
Wilks3y said:
Bah everyone is telling me to Root it, like I said yeah I wan't customisation with themes etc, which Viper has really drawn me into, but on the other hand I want a clean and bugless rom, that just WORKS GREAT.
!
Click to expand...
Click to collapse
All the roms are great :laugh:. Just pick what suits your needs. And good luck with the flashing!
And if you want bugless, stay away from the Jelly Bean roms. Fast as hell and buttersmooth but not completely bugfree. I'm waiting for the official HTC Jelly Bean-update, i hope the AOSP-rom-developers can bring us some magic than.
Huubs said:
All the roms are great :laugh:. Just pick what suits your needs. And good luck with the flashing!
And if you want bugless, stay away from the Jelly Bean roms. Fast as hell and buttersmooth but not completely bugfree. I'm waiting for the official HTC Jelly Bean-update, i hope the AOSP-rom-developers can bring us some magic than.
Click to expand...
Click to collapse
Don't suppose you know what happens when / if they release the official JB Rom,
Can you go back to stock roms, cuz I think when JB is released, I would want to go back to stock.
I've heard rumors in september. I repeat rumors!!!! Could also be december, you never know with HTC
And it's always possible to go back to stock. Only important thing is that you have a nandroid backup of your stock rom without root.
- unlock bootloader
- flash cwm
- do a nandroid backup!!!! and place a copy on your PC
to go back to stock after flashing custom rom:
- extract boot.img from your stock rom nandroid backup on your PC and flash it via fastboot.
- wipe data/cache, factory reset in cwm
- restore stock rom nandroid backup in cwm
- flash corresponding recovery from your stock rom via fastboot
After that you can OTA-update your One X and you're ready to enjoy some wonderful jelly beans
Happy flashing!
Huubs said:
I've heard rumors in september. I repeat rumors!!!! Could also be december, you never know with HTC
And it's always possible to go back to stock. Only important thing is that you have a nandroid backup of your stock rom without root.
- unlock bootloader
- flash cwm
- do a nandroid backup!!!! and place a copy on your PC
to go back to stock after flashing custom rom:
- extract boot.img from your stock rom nandroid backup on your PC and flash it via fastboot.
- wipe data/cache, factory reset in cwm
- restore stock rom nandroid backup in cwm
- flash corresponding recovery from your stock rom via fastboot
After that you can OTA-update your One X and you're ready to enjoy some wonderful jelly beans
Happy flashing!
Click to expand...
Click to collapse
Hi mate, might have to save what you just said as a notepad when I get home
Don't know why im finding it such a struggle to take the leap of faith and root it, do I worry too much?
Wilks3y said:
Hi mate, might have to save what you just said as a notepad when I get home
Don't know why im finding it such a struggle to take the leap of faith and root it, do I worry too much?
Click to expand...
Click to collapse
I know exactly what you mean. It took me a year before i rooted my desire. You root when you are ready for it.
Here's i.m.o. the best guide for rooting your One X: http://onexroot.com/one-x-root/how-to-root-one-x/
Step 18: go to your location where you put the onexroot-folder
Step 39: Download cwm 5.8.4.0 from here http://forum.xda-developers.com/showthread.php?t=1594819 and place it in the onexroot-folder and flash it with fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
After flashing cwm, make a nandroid backup from your stock rom. Then you continue with step 40.
If you're ready with the guide and it's not ok, you missed something. This almost can't go wrong.
Goodluck :good:
Go for it
exocetdj said:
Go for it
Click to expand...
Click to collapse
See, this morning I was all up for it.
I was like "Yeah, what can go wrong, the ROM's look brilliant, you've rooted and flashed a phone before and it was better after flash".
Now I'm like "No DONT DO IT, if something goes wrong then you'll have to pay for repairs, when you've already spent 500£ on the phone".
BAH why does Vipers ROM exist, I would be able to stay away from rooting without that ROM, I just love the red/blue themes where its all black etc.
Alright folks, this is directed more at the those that have spent a lot of time modding and flashing their GS3's. I recently got myself a GS3, and I gotta be honest, I haven't gotten the itch to customize it more than root yet because it is just that good already.
I modded the hell out of my Vibrant, constantly flashing Roms, modems, kernels, etc. Ran into a few "bumps" along the road where I thought the phone was done for, but I was always able to bring it back. For instance, a few months before I got the GS3 I was flashing a ROM and although I can't remember the details, something screwed up and I was getting the dreaded Phone to PC symbol. I have had this in the past and had a JIG that would always get me into download mode. This time however, it wouldn't work. I couldn't get ADB to send it into download, nor through the hardware keys, nor with the JIG. I thought for sure I was done for.
I decided to plug it into my computer anyway with ODIN up, and even though it wasn't in download mode, ODIN showed a "yellow COM". I said what is there to lose and so I loaded stock and hit start, lo and behold a few minutes later the ol' Vibrant was booting back up to the familiar sound of the T-Mobile jingle. I thoroughly believe that phone is unbrickable.
Now I know I'm going to get the itch sooner or later, especially as more and more ROM development ensues, but how brickable is the GS3? Anyone know if it's as "tough" as the Vibrant was in that respect, or is it quite a bit easier to brick? What is your experience with it so far?
If you flash am i9300 ROM, you will brick. That's about it.
Sent from my SGH-T999
If you know how to read warnings and have a fully functional brain you won't brick.
Posted from what apple calls "basically an iPhone" SGS3
GS3 should be less likely to brick
I flashed an HTC Rom with the vibrant and was still able to get it back to functionality.. not completely for sure about the GS3. I know of someone that hardbricked their GS3, and they are actually getting close to fixing it, but not fully yet.. just read and flash what ur suppose to.
Sent from my SGH-T999 using xda app-developers app
I use to have a vibrant too. Then I switch to this. I am a flashaholic so far everything good . Havent have anu problem that odin cant fix.
Sent from my SGH-T999 using xda app-developers app
If you do eventually decide to fiddle around with your phone, here's some advice:
1. BACKUP YOUR IMEI. No one's 100% sure what causes it (though there are several theories regarding recoveries and wipe scripts). You can inject your IMEI if you don't have a backup but the process takes maybe 10 minutes and I feel like it would save alot of headaches. There are currently two methods. I recommend you do both and keep a copy of the backup files somewhere safe:
Method 1: http://forum.xda-developers.com/showthread.php?t=1808408
Method 2: http://forum.xda-developers.com/showthread.php?t=1804123 (includes instructions on injecting an IMEI.
2. Try to stick to the thread for your particular GS3. I've heard that ATT Roms and kernels are compatible with the TMO version and vice versa. I take a little more comfort knowing a particular ROM or kernel was developed for my specific GS3 variant. Feel free to experiment with ROMS and kernels from other variants but be sure you know what they contain (be especially attentive to different modems/radios, see #3).
3. IMO the biggest source for bricking involves modems/radios. I haven't flashed any because I'm on wind and most of the new modems released have been for TMO. Flashing the wrong radio can brick your phone. Most ROMS don't flash a modem but it never hurts to ask. Be especially attentive to files that require ODIN as I believe some of these files may include modems and recoveries.
4. Since your posting on TMO forum, I'm going to assume yo have a TMO/Wind/Mobilicity variant of the phone. If your looking to root, I recommend using the method in this thread: http://forum.xda-developers.com/showthread.php?t=1771687. Simply download the image for your cell phone company and follow the instructions in OP. It's basically just flash with ODIN. Then install a recovery. You can install CWM using the method in the post. Or you can install TWRP by downloading the goo.im app and installing it with that application..
5. HAVE FUN
I used to have a vibrant as well and had a few close calls. I was always able to finally get it back. The S3 appears to be just as hearty (as long as you don't flash a i9300 rom).
Flash away.
nicky9door said:
If you do eventually decide to fiddle around with your phone, here's some advice:
1. BACKUP YOUR IMEI. No one's 100% sure what causes it (though there are several theories regarding recoveries and wipe scripts). You can inject your IMEI if you don't have a backup but the process takes maybe 10 minutes and I feel like it would save alot of headaches. There are currently two methods. I recommend you do both and keep a copy of the backup files somewhere safe:
Method 1: http://forum.xda-developers.com/showthread.php?t=1808408
Method 2: http://forum.xda-developers.com/showthread.php?t=1804123 (includes instructions on injecting an IMEI.
2. Try to stick to the thread for your particular GS3. I've heard that ATT Roms and kernels are compatible with the TMO version and vice versa. I take a little more comfort knowing a particular ROM or kernel was developed for my specific GS3 variant. Feel free to experiment with ROMS and kernels from other variants but be sure you know what they contain (be especially attentive to different modems/radios, see #3).
3. IMO the biggest source for bricking involves modems/radios. I haven't flashed any because I'm on wind and most of the new modems released have been for TMO. Flashing the wrong radio can brick your phone. Most ROMS don't flash a modem but it never hurts to ask. Be especially attentive to files that require ODIN as I believe some of these files may include modems and recoveries.
4. Since your posting on TMO forum, I'm going to assume yo have a TMO/Wind/Mobilicity variant of the phone. If your looking to root, I recommend using the method in this thread: http://forum.xda-developers.com/showthread.php?t=1771687. Simply download the image for your cell phone company and follow the instructions in OP. It's basically just flash with ODIN. Then install a recovery. You can install CWM using the method in the post. Or you can install TWRP by downloading the goo.im app and installing it with that application..
5. HAVE FUN
Click to expand...
Click to collapse
I did use that method for rooting already, but I didn't realize the issue with the IMEI so that's good to know for when I get the urge to start flashing again. :laugh:
Just got an S3 and I absolutely hate the unpolished and laggy Samsung skinning of Android. I want to flash CM10, but would like to know what I should back up first in case some critical information gets lost. This is a virgin phone, no apps or user data need to be backed so no need to worry about that. However, I would like to know how to back up IMEI, device ID, etc. Is it enough just to back up the /efs partition? If not, what else should I be backing up?
Thanks in advance
loonieryan said:
Just got an S3 and I absolutely hate the unpolished and laggy Samsung skinning of Android. I want to flash CM10, but would like to know what I should back up first in case some critical information gets lost. This is a virgin phone, no apps or user data need to be backed so no need to worry about that. However, I would like to know how to back up IMEI, device ID, etc. Is it enough just to back up the /efs partition? If not, what else should I be backing up?
Thanks in advance
Click to expand...
Click to collapse
Read this and this.
It was pretty overwhelming for me at first, but get through it best you can.
It's easier to do the preventative backup rather than the post repair.
themadproducer said:
Read this and this.
It was pretty overwhelming for me at first, but get through it best you can.
It's easier to do the preventative backup rather than the post repair.
Click to expand...
Click to collapse
Thank you! I've got experience flashing custom kernels and ROMs, so I should be ok. The only thing is that with every phone model what you need to back up is different, so I wanted to make sure I had the right stuff backed up from my stock S3 before I did anything to it.
So is an IMEI back up via QPST the only thing needed? What about device ID, and other details? Do those need to be backed up and how?
loonieryan said:
Thank you! I've got experience flashing custom kernels and ROMs, so I should be ok. The only thing is that with every phone model what you need to back up is different, so I wanted to make sure I had the right stuff backed up from my stock S3 before I did anything to it.
So is an IMEI back up via QPST the only thing needed? What about device ID, and other details? Do those need to be backed up and how?
Click to expand...
Click to collapse
As long as your IMEI is backed up you should be OK. When I first flashed CM10 I made a Nandroid and backed up my IMEI. I have not had any issues with my IMEI or anything but I know people that have.
WattB006 said:
As long as your IMEI is backed up you should be OK. When I first flashed CM10 I made a Nandroid and backed up my IMEI. I have not had any issues with my IMEI or anything but I know people that have.
Click to expand...
Click to collapse
Just so I'm clear, you:
1) Flashed CWM recovery
2) Did a Nandroid backup of the stock ROM and backed up IMEI
3) Flashed CM10
Right?
loonieryan said:
Just so I'm clear, you:
1) Flashed CWM recovery
2) Did a Nandroid backup of the stock ROM and backed up IMEI
3) Flashed CM10
Right?
Click to expand...
Click to collapse
Ever since i got my s3 never had to do anything do the IMEI... If you like wasting time i guess you can.. but if your smart with your phone you wont have to consider that extra step.. MAKE SURE U FLASH SGH-I747 roms only!!! and i mean ONLY... (tmo roms work too just make sure you change the apn settings) dont flash any other variants because they have different hardware. you will **** up the bootloader by flashing anyother variant.. Anyway back to the subject. I backup nandroid, then i use ultimate backup (like titanium backup just faster) its by jrummmy and thats it and im good to go to flash custom roms
amzi said:
Ever since i got my s3 never had to do anything do the IMEI... If you like wasting time i guess you can.. but if your smart with your phone you wont have to consider that extra step.. MAKE SURE U FLASH SGH-I747 roms only!!! and i mean ONLY... (tmo roms work too just make sure you change the apn settings) dont flash any other variants because they have different hardware. you will **** up the bootloader by flashing anyother variant.. Anyway back to the subject. I backup nandroid, then i use ultimate backup (like titanium backup just faster) its by jrummmy and thats it and im good to go to flash custom roms
Click to expand...
Click to collapse
No Offense Amzi,
but I only flashed STOCK OTA rom upgrades and some mods SPECIFIC to my i747m and I lost my IMEI a few months ago. I have tons of Android Flashing experience, and I did a lot of reading before I did my first S3 flash. My heart sank when it happened. When it happens, you lose your data connection and that's what tipped me off. And from all I have read up till now...no one knows why it RANDOMLY happens. So I would HIGHLY ADVISE to backup those files as per the link(s) I provided.
I followed instructions to root it and its rooted, but have never been able to get Cyanogenmod to Install (I always get the same error everyone else does), and when I try to check out different ROMS, no one even posts many pics to show what the difference will be to use that ROM.
My phone looks the same as before and I'm just using ADW launcher to set it up the way I want it to look.
So how can I tell exactly what point of rooting my phone has reached? Do I actually have a different ROM, etc? I don't know much about this stuff and I'm not bricking my phone messing around with it until I know exactly where to start.
What custom recovery and bootloader are currently loaded on the phone?
kmodek said:
So how can I tell exactly what point of rooting my phone has reached? Do I actually have a different ROM, etc?
Click to expand...
Click to collapse
Hi!
Go to your phone's System Settings --> About phone.
In there, you should be able to figure out which Android version is currently installed on your phone; if you have a custom ROM, most of the time ROMs developers will also add an additional line somewhere on that screen to tell exactly what revision of their ROM is installed. If not, you may be able to grab some more information by checking your build number or your kernel revision.
If you tap a few times on where it says Android Version, under Settings>More>About Device , it usually does a little animation of the rom version. Im trying to decide on a rom so mine is kit kat 4.2.2 at the moment and dislpays an Android logo in the Kit Kat logo style.
Since the bootloader version is not displayed on the About Phone page, you will need to determine that with another method. A simple way would be with the Samsung Info app from the PlayStore, the one posted by vndnguyen.
I personally use Terminal Emulator commands to determine phone info.
Code:
getprop ro.bootloader
getprop | grep version.baseband
I got the app from the Play store and it shows I'm on 4.4.2, but that the Knox has been tripped (I know it's rooted because I have an app that verifies root), but other than that, I can't tell any difference from how it was originally.
Guess I just thought rooting it would make it look a lot different and after reading through all of the forums, there seems to be 100 steps just to try out one new ROM and I don't even know what you do if you get it and decide you don't even like it. I just don't want to brick my phone.
kmodek said:
Guess I just thought rooting it would make it look a lot different and after reading through all of the forums, there seems to be 100 steps just to try out one new ROM and I don't even know what you do if you get it and decide you don't even like it. I just don't want to brick my phone.
Click to expand...
Click to collapse
i was watching youtube videos of reviews of the different custom ROMs gave a good idea on the features and layout of each rom. I as well am having difficulty deciding on a ROM to flash as this is my first smart phone and am new to it. ive been reading and watching a bunch of tutorials but finding information on whats currently stable for our particular phone can be somewhat dated. i know moderators want to avoid a "best roms" thread but for those of us just starting out with a rooted phone it sure would be handy to have opinions on what ppl use for the SGH-I747 and why, so its easier to decide on one.
is it reccommended to upgrade or downgrade? in order to compare ROMs its watching a video for 15 min to see what features it had at the time the vid was made and reading the developer forums on each mod to see what bugs are present in the current release but its not all compiled anywhere. its that or randomly flash ROMs on there to test them out and risk making mistakes. its usually always better to have advice from those with expertise and perhaps avoid making commonly made mistakes. ive read a bunch of helpful and handy guides on here but doesnt seem any way to easily compare roms or get feedback on what users have decided on sticking with or anything additional specific to this phone that should be considered before flashing certain ROMs.
kmodek said:
I got the app from the Play store and it shows I'm on 4.4.2, but that the Knox has been tripped (I know it's rooted because I have an app that verifies root), but other than that, I can't tell any difference from how it was originally.
Guess I just thought rooting it would make it look a lot different and after reading through all of the forums, there seems to be 100 steps just to try out one new ROM and I don't even know what you do if you get it and decide you don't even like it. I just don't want to brick my phone.
Click to expand...
Click to collapse
this thread may help to explain some badic things.
http://forum.xda-developers.com/showthread.php?t=2343223
my advice , for what its worth ...
1) READ READ READ
2) make a backup of your current setup so you have it to fall back on.
3) NEVER downgrade your bootloader , flash any ROM/kernel not meant for your device (sure way to brick it).
theres always risk when flashing anything , but the risks can be minimized by understanding what your doing , or rather the process.
as far as flashing roms , its pretty simple once you understand it (as with most things. lol). reading thru a ROMs thread will give a general idea of any features , issues that the users have. the OP , first post ; will tell you alot about the ROM/features.
good luck and happy flashing.!
"all i can really do , is stay out of my own way and let the will of heaven be done"
kmodek said:
.... (I know it's rooted because I have an app that verifies root), but other than that, I can't tell any difference from how it was originally.
Guess I just thought rooting it would make it look a lot different and after reading through all of the forums, there seems to be 100 steps just to try out one new ROM and I don't even know what you do if you get it and decide you don't even like it. I just don't want to brick my phone.
Click to expand...
Click to collapse
The act of rooting does not outwardly change the look and feel of a ROM in any way. It's what you do after rooting that makes the difference.
Some like the Stock Rom of a device and/or do not want to lose some of its unique features. These people will root but not flash a custom ROM.
I've had two android phones and one tablet. Initially I root a new device but leave it on the stock ROM. At that time I will use an app that requires root to freeze any of the pre-installed apps that I don't use (My definition of bloat.) I don't remove/delete them at the beginning. If freezing them breaks some other functionality I want that app still on the device so that I can unfreeze it and make everything work again. Both of my phones have been Samsungs, a SGS Captivate and a SGS3. After a while on rooted stock I have changed to custom ROMs on each. The Captivate went from stock to CyanogenMod to a CM derived ROM. The SGS3 went from stock to a re-themed, custom ROM based on stock but with much removed (carrier bloat) and some other functions added. I expect to soon change to a later version of the same ROM with even more removed. Others want to have a ROM with every bell and whistle possible to have present. It's all individual preference.
havok6669 said:
i was watching youtube videos of reviews of the different custom ROMs gave a good idea on the features and layout of each rom. I as well am having difficulty deciding on a ROM to flash as this is my first smart phone and am new to it. ive been reading and watching a bunch of tutorials but finding information on whats currently stable for our particular phone can be somewhat dated. i know moderators want to avoid a "best roms" thread but for those of us just starting out with a rooted phone it sure would be handy to have opinions on what ppl use for the SGH-I747 and why, so its easier to decide on one.
is it reccommended to upgrade or downgrade? in order to compare ROMs its watching a video for 15 min to see what features it had at the time the vid was made and reading the developer forums on each mod to see what bugs are present in the current release but its not all compiled anywhere. its that or randomly flash ROMs on there to test them out and risk making mistakes. its usually always better to have advice from those with expertise and perhaps avoid making commonly made mistakes. ive read a bunch of helpful and handy guides on here but doesnt seem any way to easily compare roms or get feedback on what users have decided on sticking with or anything additional specific to this phone that should be considered before flashing certain ROMs.
Click to expand...
Click to collapse
There are so many variations on what is possible that a compilation thread to cover all situations would seem as huge as wikipedia. Your approach, reviewing videos and checking rom OPs, has merit but it also has limitations. Unfortunately some of the devs give you almost no information about the features and customizations of their ROMs. Others will simply state that they have made a change or two to some base, expecting you to be familiar with the base. Which means a lot of more reading/reviewing for a person new to customizing their phone.
To advise any one questioner on what can be installed on their phone a responder must first know what bootloader and modem is on the device, are you already rooted, do you have a custom recovery installed yet, are you willing to risk breaking your warranty; the list goes on. Then the hard part comes - they have to recommend something that is in the realm of what you are expecting, even if you do not know what you are expecting.
dawgdoc said:
To advise any one questioner on what can be installed on their phone a responder must first know what bootloader and modem is on the device, are you already rooted, do you have a custom recovery installed yet, are you willing to risk breaking your warranty; the list goes on. Then the hard part comes - they have to recommend something that is in the realm of what you are expecting, even if you do not know what you are expecting.
Click to expand...
Click to collapse
well i made sure i learned a bunch before even attempting to ask a question so i got as much as possible prepared i'll try to provide the best information i can. my phone is rooted with superuser su2.0 i have cwm 6.0.1.2 installed, ive done a cwm nandroid backup which i copied to my pc as well as a backup of my efs folder and done a titanium backup as well. i have odin 3.07 on my pc and am currently running kitkat 4.4.2 on my sgh-i747m (sasktel version) currently trying to figure out how to determine the modem and bootloader versions . i followed the galaxys3root.com guide galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3-on-android-4-34-4-2-new and the highonandroid youtube vid in order to root my phone and made sure i read re read and was very cautious to follow instructions to the letter also read some worst case scenario information first like how to cause a phone to become bricked and how to fix it should it happen etc so before ive done anything else ive made sure to back everything up and ask a few more questions befor ei take the final plunge :] as for what ROM would tickle my tailfeathers was liking how carbon looked but it seems it hasnt been maintained :[ something good on battery life that runs fast n stable and is has a bunch of customization features is what i was hoping for. the main reason i decided to root my phone was to learn more about it and customize my os away from the stock look and feel and unlock some of the potential it has that a stock rom would otherwise neglect. the more i learn the sooner i can help by giving back to the community :]
havok6669 said:
....
my phone is rooted with superuser su2.0 i have cwm 6.0.1.2 installed, ive done a cwm nandroid backup which i copied to my pc as well as a backup of my efs folder
Click to expand...
Click to collapse
CWM 6.0.1.2 is a bit dated, their latest version is 6.0.4.7 and even it is a bit dated. You may find that to flash a current ROM you will need to update CWM. For some of the newer ROMs even 6.0.4.7 is not current enough. You will need to change to Philz Recovery, based on CWM, or TWRP. Bear in mind that if you change to TWRP you will not be able to use your CWM nandroid. I don't know if the same applies to Philz Recovery.
https://www.clockworkmod.com/rommanager
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/ (page is down at the moment)
http://teamw.in/devices/samsunggalaxys3canada.html (d2can TWRP, though I think you can use d2att, check before using d2att)
There is definitely a newer version of SuperSu (by Chainfire) available. It went through a lot of development to handle issues related to Knox that came out with Touchwiz 4.3. SuperSu is now up to 2.49 and I would recommend upgrading it no matter what ROM you should end up choosing. http://forum.xda-developers.com/showthread.php?t=1538053 There is a zip you can flash from you current CWM there.
It's not a bad idea to have several fallbacks for imei/nvdata. Give this tread a look: http://forum.xda-developers.com/showthread.php?t=1852255&highlight=synergy+nvbackup I used the reboot nvbackup from there and EFS Backup developed by wanam
... am currently running kitkat 4.4.2 on my sgh-i747m (sasktel version) currently trying to figure out how to determine the modem and bootloader versions .
Click to expand...
Click to collapse
Sasktel has released 4 versions of Android 4.4.2, each with a different bootloader and modem. Any should be fine no matter what ROM you choose, even a Lollipop based ROM. But to check you can get Phone Info - Samsung by vndnguyen from the Playstore. Or you could use a pair of commands in Terminal Emulator
Code:
getprop ro.bootloader
getprop | grep version.baseband
... as for what ROM would tickle my tailfeathers was liking how carbon looked but it seems it hasnt been maintained :[ something good on battery life that runs fast n stable and is has a bunch of customization features is what i was hoping for. the main reason i decided to root my phone was to learn more about it and customize my os away from the stock look and feel and unlock some of the potential it has that a stock rom would otherwise neglect. the more i learn the sooner i can help by giving back to the community :]
Click to expand...
Click to collapse
You could either go straight a Lollipop based ROM or start with a KitKat ROM. The KK ROM would probably be a bit more stable, although some of the nightly 5.1.1 LP ROMs are looking good according to many of the people installing the nightly versions. If you want something already customized with options for your choosing look to CM and its derivatives or one of the AOSP roms that are already tricked out. The other direction would be to install the most barebones AOSP ROM you could find and use XPosed with the GravityBox or Wanam module to tweak just about everything, but not both at the same time.
wow thanks that all helps a ton ill work on locating and updating all of that :]
Hello,
I've got a Galaxy Tab Pro 8.4 that I bought during the few months when it was the top of the line small tablet from Samsung (before the S series came out). Since it seems clear that Samsung has abandoned it and it won't get an Android update, I want to see what it'll take to upgrade to at least Lollipop. I'm pretty tech savy, but I've never tried to do anything like this with Android and I'm not at all sure where to start.
I've started to read the thread on rooting, but I quickly got a bit lost as I don't understand the terminology.
My goal would be to simply get to stock Lollipop or Marshmallow and have a stable, functional tablet that I don't have to tweak or mess with much. I'd also like to be able to go back if it proves too buggy. Is that feasible, or is rooting plus upgrading pretty much something that will require constant maintenance and tweaking? If it is possible, can someone point me to a how to for complete newbies?
Rooting will not help you upgrade your tablet to Lollipop or Marshmallow as they aren't available for your device. You might want to google "what is rooting" and find out what it does before proceeding.
The only thing you could do to get L or MM is install a custom ROM such as this:
http://forum.xda-developers.com/gal...5-1-x-cyanogenmod-13-0-nightlies-tab-t3256093
CafeKampuchia said:
Rooting will not help you upgrade your tablet to Lollipop or Marshmallow as they aren't available for your device. You might want to google "what is rooting" and find out what it does before proceeding.
The only thing you could do to get L or MM is install a custom ROM such as this:
http://forum.xda-developers.com/gal...5-1-x-cyanogenmod-13-0-nightlies-tab-t3256093
Click to expand...
Click to collapse
What makes you thin that his device is not have any Third Party ROMs (i.e CyanogenMod)? FYI this is the Tab Pro Fourm, and his Device should damned well be able to get to Lollipop or Marshmallow. e.g. CM12.1, or CM13.
As for rooting which you have to do at the start. Will most likely send him back to SamFirmware's where he'll need to likely first downgrade his Firmware to one that has a rootable exploit. i.e. a 'BOC1' ROM for the T325. (Which is the version I have). Through Odin (Samsung's Android Firmware Windows PC flashing Software). Then run something like the CFRoot App to get root.
NOTE: THIS WILL THROW YOUR KNOX FLAG!
This means that you'll never be able to use Knox services on that Device ever again. It will also throw the Warranty Flag as well Alerting Samsung that the Firmware was tampered with. For the moment (As I gather there is no known way to reset either of these Flags.) Not that this should stop you from installing either CM12.1 Lollipop (Seems to have lost support to) CM13 Marshmallow which is currently on a nightly release.
So the better question to ask is which T32x does Op even have? The T320 (Wi-Fi) The most common, and cheapest version has the greatest support. Where as the T325 (LTE), and T321 (3G) versions seem to be leaving behind. though even these are currently well into Marshmallow, and like with most ROMs there are some small bugs. But, on the whole My Device is more or less working as it should be.
Ichijoe said:
What makes you thin that his device is not have any Third Party ROMs (i.e CyanogenMod)? FYI this is the Tab Pro Fourm, and his Device should damned well be able to get to Lollipop or Marshmallow. e.g. CM12.1, or CM13.
As for rooting which you have to do at the start. Will most likely send him back to SamFirmware's where he'll need to likely first downgrade his Firmware to one that has a rootable exploit. i.e. a 'BOC1' ROM for the T325. (Which is the version I have). Through Odin (Samsung's Android Firmware Windows PC flashing Software). Then run something like the CFRoot App to get root.
NOTE: THIS WILL THROW YOUR KNOX FLAG!
This means that you'll never be able to use Knox services on that Device ever again. It will also throw the Warranty Flag as well Alerting Samsung that the Firmware was tampered with. For the moment (As I gather there is no known way to reset either of these Flags.) Not that this should stop you from installing either CM12.1 Lollipop (Seems to have lost support to) CM13 Marshmallow which is currently on a nightly release.
So the better question to ask is which T32x does Op even have? The T320 (Wi-Fi) The most common, and cheapest version has the greatest support. Where as the T325 (LTE), and T321 (3G) versions seem to be leaving behind. though even these are currently well into Marshmallow, and like with most ROMs there are some small bugs. But, on the whole My Device is more or less working as it should be.
Click to expand...
Click to collapse
1) I read the OP. He said, "stock Lollipop or Marshmallow."
2) You don't have to root TouchWiz to install a custom ROM. All you have to do is install TWRP, but it doesn't matter because of #1 above.
Well yes if he wanted Stock then he'd be outta luck. But that is not how I read it. I read it that he has accepted the fact that Samsung have left us in the lurch concerning any future updates.
That's how I read it, so the question follows in how to install a Custom ROM. Granted it should be possible to install TWRP v. 3.0.1-0, though Odin, and then the Device appropriate ROM. It should go without saying that the T320, and T325 are not the same Device, even if they are both collectively known as Galaxy Tab Pro's 8.4. As such it would be upnto the owner to know which version he might need.
Ichijoe said:
Well yes if he wanted Stock then he'd be outta luck. But that is not how I read it.
Click to expand...
Click to collapse
The problem, is folks really need to stop using the word "stock" as it really doesn't mean jack. Or at the least, means so many different things to different people, as to be basically meaningless. I would take stock to mean, what belongs on the device per the manufacturer, so that would be Kitkat TouchWiz in this case. To others (and probably what the OP is getting at) is a "pure" unskinned Google experience like Nexus. But seeing as Nexus is limited to such a small number of devices, I don't personally feel you can consider that "stock". CM is AOSP based, and at one time considered by many to be close to a pure AOSP experience. But those days are long gone, and there are so many proprietary CM features and apps now, you can't even begin to consider this "stock" by any means.
---------- Post added at 03:36 PM ---------- Previous post was at 03:22 PM ----------
_salguod said:
My goal would be to simply get to stock Lollipop or Marshmallow and have a stable, functional tablet that I don't have to tweak or mess with much. I'd also like to be able to go back if it proves too buggy. Is that feasible, or is rooting plus upgrading pretty much something that will require constant maintenance and tweaking?
Click to expand...
Click to collapse
What you are asking for is CM12 or CM13 (LP or MM) or one of the CM based ROMs. Those are really your only choice when it comes to anything past KK on this device. The CM ROMs are are very stable at this point. You might run into an obscure bug, but to be honest, its less laggy and overall a much better experience than the official Samsung TouchWiz ROM. And if you want to be free of Samsung bloat, CM definitely does that as well.
Tweak or maintain? You don't have to do anything after flashing the ROM, if you don't want to. You can decide to update to newer nightly CM builds from time to time, but that is completely optional. And to be honest, even CM13 is so stable at this point, that the nightly updates don't really change much of anything.
Go back? That's a breeze. Just do a backup in TWRP custom recovery before flashing a ROM, and you can restore to that backup (basically a snapshot of your existing configuration).
_salguod said:
If it is possible, can someone point me to a how to for complete newbies?
Click to expand...
Click to collapse
Honestly, just searching and reading are your best friend. You'll learn a lot more that way, than folk spoon-feeding you the info. The process isn't really all that hard. There may be a lot of esoteric lingo, but you can easily Google or use the XDA site search to find out what those terms mean. And once you've gone through the process, you'll likely be happy for the learning experience.
XDA is a wealth of information, for those willing to take the time to learn and search. All the answers you want are here in one form or other. Difficult to wade through at first, I'll agree with that. But all of us here had to go through the same thing at one time or other.
Its really hard to help someone when they say is "I'm a newb, tell me how to do this". Make a lot more sense for you to just dive in, then come back here with some specific questions, which we will gladly answer.
it would help to know what version OS you're running and the build #.
I rooted my tablet late last year (bought it in May 2015). Wasn't hard to do after some reading. Knox is still good too...1 yr warranty will be over soon.
Thanks all, I appreciate it. I've been doing some more digging to try to learn what everything means so I might know what I'm talking about. I started with the Lifehacker rooting guide (I can't post links yet, add this to lifehacker dot com: /5789397/the-always-up-to-date-guide-to-rooting-any-android-phone) and their how to flash a ROM guide (/how-to-flash-a-rom-to-your-android-phone-30885281) as well. Let me know if those aren't good places to start. I've also read through the CyanogenMod how to for the 8.4, which seems pretty thorough.
I definitely appreciate the push to search and learn, but it can feel like drinking from a firehose. Most "how to" posts are written assuming the reader knows the terminology and every post I read means Googling a half a dozen terms to understand it. For example, I have no idea what the Knox flag is or why I'd care if it got triggered. I don't care about the warranty flag, I'm past the 1 year mark so it doesn't really matter, right?
When I said "stock" I was referring to stock out of the box Android, not stock Samsung. Stock Samsung means staying with KitKat which I'd rather not do. My phone is a Motorola Droid Turbo, which I think is pretty close to stock Android Lollipop, so that I'm familiar with that.
However, I think I'm seeing that going stock Android isn't necessarily possible, or rather, other ROMs are easier to come by. Cyanogenmod seems to be the most popular and sounds very stable, I'll likely try that.
So, I don't need to root in order to flash a new ROM. What's unclear is do I need to do anything special to make sure I can go back to the out of the box Samsung KK that I have now in case I really screw it up or just don't like it and want to go back? Will the process of installing Cyanogenmod wipe my device (apps, files, accounts, data, etc.?
Any other surprises that a guy who has never done this might want to know before going in?
Thanks again for your patience and help.
I forgot to mention, I've got the wifi model, T-320. It's running 4.4.2, build number KOT49H.T320UEU1AOC1.
Well you have a number of choices for your T320 (WiFi), Sadly nonmof those stock. Since Samsung has never seen fit to ever giving us one. For me the Samsung (e.g. Vender ROMs), were always the 'Stock' ROMs. 'Pure' ROMs (al-la Nexus), are clearly Custom ROMs.
The best, and quickest way to learn how to update from Stock to Custom would be to hit up YouTube for a few short Vids on the subject.
_salguod said:
I've been doing some more digging to try to learn what everything means so I might know what I'm talking about. I started with the Lifehacker rooting guide (I can't post links yet, add this to lifehacker dot com: /5789397/the-always-up-to-date-guide-to-rooting-any-android-phone) and their how to flash a ROM guide (/how-to-flash-a-rom-to-your-android-phone-30885281) as well. Let me know if those aren't good places to start. I've also read through the CyanogenMod how to for the 8.4, which seems pretty thorough.
Click to expand...
Click to collapse
Those aren't bad general guides, to just introduce you to the basic concepts and terms. Just keep in mind that every different Android device has its nuances, which vary by manufacturer and over time (from one device to another - even from the same manufacturer). So you'll be referring back to Tab Pro 8.4 specific guides eventually.
_salguod said:
I have no idea what the Knox flag is or why I'd care if it got triggered. I don't care about the warranty flag, I'm past the 1 year mark so it doesn't really matter, right?
Click to expand...
Click to collapse
Basically, if you don't know what the Knox flag is, then it probably doesn't matter.
The longer story, Knox is a enterprise mobile solution made by Samsung. If you company doesn't use Knox (and you don't use your device for work), you don't need it. The huge majority of folks will never need Knox or want it.
You're right, that if the warranty is expired, the warranty flag doesn't matter. And honestly, I rooted my device while it still had a valid warranty. I'd rather have a device that I can use how I wish, and install what software I want (especially if Samsung isn't going to support it with updates) and warranty is a secondary concern, at most.
_salguod said:
What's unclear is do I need to do anything special to make sure I can go back to the out of the box Samsung KK that I have now in case I really screw it up or just don't like it and want to go back?
Click to expand...
Click to collapse
Once you install TWRP custom recovery, you can make a backup of the current Samsung TouchWiz KK ROM; and revert to that if needed or desired.
But honestly, you won't want to go back. CM runs faster and smoother, with no Samsung bloat. You won't want to go back to the crappy TouchWiz ROM, that is 2 generations (Android versions) obsolete.
But it is a good idea to have a backup, in case flashing CM doesn't go right the first time, and the device won't boot.
_salguod said:
Will the process of installing Cyanogenmod wipe my device (apps, files, accounts, data, etc.?
Click to expand...
Click to collapse
You will absolute want to wipe user data when installing CM. Not doing so will likely cause major bugs and/or failure to boot. This is the general rule whenever flashing a new ROM. Although for similar ROMs (such as minor CM updates) you can try to keep user data. This is called a "dirty flash".
You can backup a lot of your data before flashing CM:
Apps: After root, you can use the app Titanium Backup (highly recommended) to backup apps and app data
Accounts: Titanium can backup a lot of this stuff, as well. Depends on what you are talking about, specifically.
Files: just move them to SD card or your computer. Or use a cloud solution (there are many)
You should always be backing up your data, anyway, if its important to you.
_salguod said:
I forgot to mention, I've got the wifi model, T-320. It's running 4.4.2, build number KOT49H.T320UEU1AOC1.
Click to expand...
Click to collapse
Same firmware as what I had prior to rooting it.
The cyanogen articles give a good rundown on how to install it. The only thing that I'm not sure about is whether getting the sdcard to be formatted/recognized is still an issue or not.
When last I checked back in Feb. it seemed like that was still unresolved. I have a 64gb card and getting it to be read by CM13 was absolutely critical. So any move to CM13 was postponed.
Running Kitkat is fine for me...after rooting it, I uninstalled/froze a lot of software incl. a lot of Samsung crap that was eating the battery. The battery is my only complaint with the tablet.
AndroidPrince1 said:
The cyanogen articles give a good rundown on how to install it. The only thing that I'm not sure about is whether getting the sdcard to be formatted/recognized is still an issue or not.
When last I checked back in Feb. it seemed like that was still unresolved. I have a 64gb card and getting it to be read by CM13 was absolutely critical. So any move to CM13 was postponed.
Click to expand...
Click to collapse
The SD card issue on CM13 was solved in early March. It was holding me back as well (stayed on CM12.1) , until I saw it was solved. Now I've been using CM13 for over a month. My 64GB card works great with CM13.
AndroidPrince1 said:
Running Kitkat is fine for me...after rooting it, I uninstalled/froze a lot of software incl. a lot of Samsung crap that was eating the battery. The battery is my only complaint with the tablet.
Click to expand...
Click to collapse
If you flash CM, you'll see its a lot smoother and snappier, especially on the home screens, app drawer, etc.
Thanks all, I plan on biting the bullet some time soon. Too much other stuff on my plate (like car repairs, etc.) so it'll have to wait for a bit. I'll check back in when I do. I'm looking forward to it.
redpoint73 said:
The SD card issue on CM13 was solved in early March. It was holding me back as well (stayed on CM12.1) , until I saw it was solved. Now I've been using CM13 for over a month. My 64GB card works great with CM13.
If you flash CM, you'll see its a lot smoother and snappier, especially on the home screens, app drawer, etc.
Click to expand...
Click to collapse
Good to know on the sdcard thing...looks like I'll have to read up again on how to do.
Thanks for the note.
_salguod said:
What's unclear is do I need to do anything special to make sure I can go back to the out of the box Samsung KK that I have now in case I really screw it up or just don't like it and want to go back?
Click to expand...
Click to collapse
BTW, you can always restore your device to 100% stock (Samsung) by downloading the firmware from sammobile.com/firmwares and flashing it using Odin. If you get into trouble, this will help get you back out.
But since flashing CM13 nightlies is relatively easy, I don't think you'll have any serious trouble, just the normal learning curve.
I've had my SM-T320 on Cyanogenmod since the day after I bought it in 2014 and never looked back :good:
CafeKampuchia said:
BTW, you can always restore your device to 100% stock (Samsung) by downloading the firmware from sammobile.com/firmwares and flashing it using Odin. If you get into trouble, this will help get you back out.
But since flashing CM13 nightlies is relatively easy, I don't think you'll have any serious trouble, just the normal learning curve.
I've had my SM-T320 on Cyanogenmod since the day after I bought it in 2014 and never looked back :good:
Click to expand...
Click to collapse
I don't see any US firmwares on the sammobile.com site. Am I looking in the wrong place?
_salguod said:
I don't see any US firmwares on the sammobile.com site. Am I looking in the wrong place?
Click to expand...
Click to collapse
Cellular South is the US firmware for some reason.
I'm trying to load the latest CM 13.0 nightly this morning and running into issues.
I'm following the install instructions on the CM website and the loading of a custom recovery is failing at step 7. I get the start of the blue bar on my tablet, but I get this error in the command prompt:
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
I've tried twice with the the factory cable and a third time with an alternate cable same result.
How do I fix that?
I should mention that I'm working on a Windows 10 computer.