I'm currently running an 8.9" HDX with a working AOSP - thanks to all the help I got on this forum and specifically followed this thread:
http://forum.xda-developers.com/showthread.php?t=2582773
but the main applications that I now need to use for work are iOS only (don't ask... NOT happy) so I'm back to carrying an iPad around everywhere and as such I'm going to sell my HDX. Before I do that I need to return it back to stock... I found a number of threads referencing how to do this but wanted to be extra careful. At present I'm just running Safestrap with a second ROM slot that I boot with all the non-standard stuff, I got there via SuperSU.
What's the right sequence of de-activates / un-installs / magic incantations to get this thing back to "boring, stock" just like it would come from Amazon? Is it as simple as re-enabling over-the-air updates and letting it "fix" itself? Or do I need to specifically back out some of the safestrap/superSU stuff first?
Help? (and THANKS)
ljwobker said:
I'm currently running an 8.9" HDX with a working AOSP - thanks to all the help I got on this forum and specifically followed this thread:
http://forum.xda-developers.com/showthread.php?t=2582773
but the main applications that I now need to use for work are iOS only (don't ask... NOT happy) so I'm back to carrying an iPad around everywhere and as such I'm going to sell my HDX. Before I do that I need to return it back to stock... I found a number of threads referencing how to do this but wanted to be extra careful. At present I'm just running Safestrap with a second ROM slot that I boot with all the non-standard stuff, I got there via SuperSU.
What's the right sequence of de-activates / un-installs / magic incantations to get this thing back to "boring, stock" just like it would come from Amazon? Is it as simple as re-enabling over-the-air updates and letting it "fix" itself? Or do I need to specifically back out some of the safestrap/superSU stuff first?
Help? (and THANKS)
Click to expand...
Click to collapse
Depends on how you used SafeStrap. If you ONLY installed in the stock rom, then an update likely would do it. If you installed safestrap a second time from the working rom-slot as well, then updates won't work, because the BL & Kernel CANNOT be flashed.
The best thing is to remove all wifi connections with "forget network", then go into safe strap & activate stock rom. Then go back to the boot options & delete the rom-slot you created. Boot back into stock partition, uninstall Safestrap & then reconnect to wifi & check for updates.
I would HIGHLY recommend you follow my directions about forgetting nearby, if not all, wifi networks. If you turn wifi off in a slot, but not in stock, or vice versa, it can cause boot issues , as well as wifi issues.
I would not return it to stock. That device could go for a premium right now to other users simply because you can get AOSP and so many cannot yet.
EniGmA1987 said:
I would not return it to stock. That device could go for a premium right now to other users simply because you can get AOSP and so many cannot yet.
Click to expand...
Click to collapse
Why would it go for a premium? It is absolutely 100% rootable. It has not been patched against the VolumeManager/vold ASEC exploit. In fact, I am nearly certain the bootloader can bed unlocked from my investigation. Unfortunately that part is beyond my abilities & exceeds the time I would need to get caught up on the msm89xx+ SoC, but I would just about bet the farm that it can be done.
GSLEON3 said:
Why would it go for a premium? It is absolutely 100% rootable. It has not been patched against the VolumeManager/vold ASEC exploit. In fact, I am nearly certain the bootloader can bed unlocked from my investigation. Unfortunately that part is beyond my abilities & exceeds the time I would need to get caught up on the msm89xx+ SoC, but I would just about bet the farm that it can be done.
Click to expand...
Click to collapse
Because when I posted that we had no root, and it was still a "hopefully sometime soon" with 9/10 of the HDX's on a version that couldnt be rooted.
It is nice that we have one Chinese method now and that you might get something soon, though I think you are suddenly pretty full of yourself on these forums with the little bit of knowledge you gained recently. Much better people at this have not been able to get the bootloader cracked. But best of luck to you.
EniGmA1987 said:
Because when I posted that we had no root, and it was still a "hopefully sometime soon" with 9/10 of the HDX's on a version that couldnt be rooted.
It is nice that we have one Chinese method now and that you might get something soon, though I think you are suddenly pretty full of yourself on these forums with the little bit of knowledge you gained recently. Much better people at this have not been able to get the bootloader cracked. But best of luck to you.
Click to expand...
Click to collapse
Actually, the little time I've been around is well over a decade. This ain't my first username. Secondly, there is already an ASEC based root that WAS created by someone better with this stuff than me, so it's not full of myself, it is FACT. I am rooted, have been each & every time, without blocking anything & without having to sacrifice connectivity, another FACT. Coincidentally, the reason it was never published, well I'd venture a guess that it's because of stupid posts & self-entitled people ignorantly writing or PM'ing to insist that things be done for them on their terms. Another fact, it was that kind of crap that made me leave this forum a few months ago. So, I don't know what "better people" you are talking about that have failed at it, but I do know the better people that have done it.
Another fact, anyone at all can read & discover just how small the patch for the ASEC vulnerability was. It doesn't take a genius to then decompile the vold & search for the that one event which was used to patch it, which subsequently tells all you need to know.
GSLEON3 said:
Actually, the little time I've been around is well over a decade. This ain't my first username. Secondly, there is already an ASEC based root that WAS created by someone better with this stuff than me, so it's not full of myself, it is FACT. I am rooted, have been each & every time, without blocking anything & without having to sacrifice connectivity, another FACT. Coincidentally, the reason it was never published, well I'd venture a guess that it's because of stupid posts & self-entitled people ignorantly writing or PM'ing to insist that things be done for them on their terms. Another fact, it was that kind of crap that made me leave this forum a few months ago. So, I don't know what "better people" you are talking about that have failed at it, but I do know the better people that have done it.
Another fact, anyone at all can read & discover just how small the patch for the ASEC vulnerability was. It doesn't take a genius to then decompile the vold & search for the that one event which was used to patch it, which subsequently tells all you need to know.
Click to expand...
Click to collapse
lol. I am glad you know your FACTS. No need to act so butthurt.
Related
ive read the thread in the general forum for noobs.
but i still dont quite understand all these things and what purpose they serve.
im SUPER new with all this stuff. so my apologies.
could someone help a brother out?
what is your question specifically?
just curious about what they are and do basically.
kevinallen4325 said:
ive read the thread in the general forum for noobs.
but i still dont quite understand all these things and what purpose they serve.
im SUPER new with all this stuff. so my apologies.
could someone help a brother out?
Click to expand...
Click to collapse
I'll try and help.
First you must ROOT your phone. This basically grants you access/permission to FIDDLE with a lot of things you can't normally. I use the word *fiddle* loosley, meaning you can install root tools (like overclock) custom Roms, change system settings, flash themes... the list goes on. It's kind of like the equivalent to "jailbreaking"
Rooting is the "first and foremost"... basically do this first. and all other things follow.
kevinallen4325 said:
just curious about what they are and do basically.
Click to expand...
Click to collapse
Well the sticky in the main forum really is a good place to start, as all these terms are defined there:
http://forum.xda-developers.com/showthread.php?t=1483113
As well as step-by-step instructions how to root. That should get you started!
ok so root first. got it. would any of this benefit my phone in anyway? or is it mainly just to put custom themes and such on?
kevinallen4325 said:
ok so root first. got it. would any of this benefit my phone in anyway? or is it mainly just to put custom themes and such on?
Click to expand...
Click to collapse
It is much more than that. I wrote this out before, so I will copy it again:
People have problems when rooted because they are not careful or do not know what they are doing. Rooting gives you (to put in Windows terms) full Administrator rights to your phone. With this right comes responsibility, so you must be careful and do research. This is why rooting also voids the warranty. The phone is now open for the user to do whatever they want, and circumvent any restrictions put on the phone by the manufacturer (including those in place to prevent harm to the device). But like a computer with Admin rights, rooting allows you to install any application, any "OS theme", and tweak the hardware to do what YOU want with it, not what the manufacturer wants.
So please be sure to READ READ READ all you can before you start!!! You don't want a $600 phone coaster. Just browse the forums for a couple weeks and learn from the posts.
kevinallen4325 said:
ok so root first. got it. would any of this benefit my phone in anyway? or is it mainly just to put custom themes and such on?
Click to expand...
Click to collapse
It depends what you consider a benefit. Sure..theming can be a benefit, but rooting provides the gateway to address any negative or less than ideal aspects of a device. For instance, The Note has been perceived as being somewhat laggy. So rooting allows you to free up system resources by eliminating unneeded bloatware that you can't remove if you remain stock. Also the lagginess has been addressed by overclocking, modding and building kernels that do specific things and of course making custom roms. The Note is still very early in the developmental process, so many things to improve the user experience of the device will become available over the course of time....but it all starts with being rooted.
Sent from my Samsung Galaxy Note LTE™
kevinallen4325 said:
ok so root first. got it. would any of this benefit my phone in anyway? or is it mainly just to put custom themes and such on?
Click to expand...
Click to collapse
Android isn't like iOS. I had an iPhone for four years before my Note and I know where you coming from. What the other guy was saying is that rooting can be viewed similar to jailbreaking, but it is kind of completely different. You don't need to be rooted to use themes (or most of the stuff on Cydia). Rooting allows you to back up apps, flash custom ROMs, etc. Otherwise, you most likely don't need root.
tbran said:
It depends what you consider a benefit. Sure..theming can be a benefit, but rooting provides the gateway to address any negative or less than ideal aspects of a device. For instance, The Note has been perceived as being somewhat laggy. So rooting allows you to free up system resources by eliminating unneeded bloatware that you can't remove if you remain stock. Also the lagginess has been addressed by overclocking, modding and building kernels that do specific things and of course making custom roms. The Note is still very early in the developmental process, so many things to improve the user experience of the device will become available over the course of time....but it all starts with being rooted.
Sent from my Samsung Galaxy Note LTE™
Click to expand...
Click to collapse
if i were to root it and do whatever else would that affect the notes ability to update itself when the time comes?
like if i were to put some custom rom or whatever on it and lets say ics came out (lulz) would it still be able to update to it, and would it basically remove everything i did to it
kevinallen4325 said:
if i were to root it and do whatever else would that affect the notes ability to update itself when the time comes?
like if i were to put some custom rom or whatever on it and lets say ics came out (lulz) would it still be able to update to it, and would it basically remove everything i did to it
Click to expand...
Click to collapse
Trust me, if you go the root and custom rom way, you will never install an official update. not because you can't, but because it will be leaked and debloated months before it is official.
i installed saurom. with and ics theme. i like it alot. but i cant get into setcpu or any program that requires root access. which is kind of an issue. no one else seems to be having that as an issue.
I rooted my Note a couple days ago and am still trying to figure out the benefits of doing so. I guess just spend time reading through this forum for the answers. That's what I am doing, but so far I see no benefit at all. The phone does all I want it to do so far. Maybe I am missing something.
Also, When i run quadrant, the scores are consistently lower after rooting the device then they were before. Not sure why though.
You are correct that the Note and newer phones may need no help. Not like two years ago. But, the big advantage to rooting even if you don't want to flash roms is Titanium Backup for app mgt and nandroids or full image backups--imho. The other like mentioned is earlier os releases. I have had ICS on my N1 for quite awhile and is still not on most new phones.
Ken
kevinallen4325 said:
i installed saurom. with and ics theme. i like it alot. but i cant get into setcpu or any program that requires root access. which is kind of an issue. no one else seems to be having that as an issue.
Click to expand...
Click to collapse
If you are sure you are rooted, a dialog box with a little Android head wearing an eyepatch will pop up asking if you want to allow the application to have root access. You must allow it here.
I have a Nook Tablet 8gig that I rooted about 10 months ago with no problems. I have had no complaints so I have not mucked around with it, but now I am wondering about updating a bit. The issue is that I want to be able to use an external keryboard dock with my NT, and I read that it was only possible with CM7 (not sure if that means CM7 and above). I rooted the NT using the great instructions and files recommended in the developers thread, but to be honest I have no idea what my nook is rooted with- it works well so I have not messed with it.
I am essentially looking for instructions on how to re-root my NT after I re-set it to factory, or how to alter my current root to run CM7. My screen is half wonked, and I may take it back since I got the extended warrenty, especially if I have to re-root it for this anyway.
Also...what is CM7? Is that an Android version?
As a side note: Can anyone confirm that you can use an external keyboard with CM7 or above?
What do you want to do first?...do you want to return to stock so that you can return your nt...or do you want to flash cm7? (cm7 is a ROM by the way a version of Android os)
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
systems6 said:
What do you want to do first?...do you want to return to stock so that you can return your nt...or do you want to flash cm7? (cm7 is a ROM by the way a version of Android os)
Click to expand...
Click to collapse
Ultimately what I want to do is run an external keyboard, and the information I have is that they will run on CM7. I will probably (assuming my warranty will cover this) be getting this one fixed to replaced soon, so I will need to re-root when I get it back, but for now I don't see the need to re-root if I don't have to.
What does it mean to "flash" cm7?
drworm73 said:
What does it mean to "flash" cm7?
Click to expand...
Click to collapse
If your nook is broken already, why bother doing anything to it? Just get it fixed then address the things you want to address. And while you are waiting for the replacement see the next line.
After reading above quote along with your original post you honestly need to read...A LOT. You need to learn at least the basic lingo before you even make an attempt to do anything. Failure to have even an iota of understanding will only lead to failure, complaints, and frustration. Spend a few hours going through the posts on here. There are several new user guides. Read them. Re-Read them. Read them again. Learn to understand what people are talking about when someone says something like "Flash x, y, or z".
As for the keyboard question, I am fairly certain that it doesn't work on ANY rom. They are working on getting the OTG portion of the kernel ironed out. While it is called a tablet it is a glorified E-Reader. The devs have done an awesome job making the Nooks into what they are today (for those of us that have modified them),
SlowCobra96 said:
After reading above quote along with your original post you honestly need to read...A LOT. You need to learn at least the basic lingo before you even make an attempt to do anything. Failure to have even an iota of understanding will only lead to failure, complaints, and frustration. Spend a few hours going through the posts on here. There are several new user guides. Read them. Re-Read them. Read them again. Learn to understand what people are talking about when someone says something like "Flash x, y, or z"
Click to expand...
Click to collapse
Any good links to layman information sites or tutorials? I was able to Root it easily (it is pretty simple), but I will admit that some of the android specific terminology does go over my head.
As for the keyboard question, I am fairly certain that it doesn't work on ANY rom. They are working on getting the OTG portion of the kernel ironed out. While it is called a tablet it is a glorified E-Reader. The devs have done an awesome job making the Nooks into what they are today (for those of us that have modified them),
Click to expand...
Click to collapse
I have read several places where cm7 has allowed keyboard use for users. They are not expensive, and I would really like to try.
As for getting it fixed...well I love my nook and use it every day, so I have been loathe to take it in. I suppose that is silly.
drworm73 said:
Any good links to layman information sites or tutorials? I was able to Root it easily (it is pretty simple), but I will admit that some of the android specific terminology does go over my head.
I have read several places where cm7 has allowed keyboard use for users. They are not expensive, and I would really like to try.
As for getting it fixed...well I love my nook and use it every day, so I have been loathe to take it in. I suppose that is silly.
Click to expand...
Click to collapse
You will love it more when it works completely and isn't "wonky". You will survive without it for a little bit. Trust me you won't die. Also because CM7 allows for a keyboard doesn't mean every device running CM7 will. Search the forums for more information. I know that some of the developers have been working on it for CM10 but I don't recall seeing any posts saying that they have it working definitively.
As for specific sites or tutorials. Just visit the various android boards and look for the Noob guides. Search google for more details on subjects you want to know about.
SlowCobra96 said:
You will love it more when it works completely and isn't "wonky". You will survive without it for a little bit. Trust me you won't die. Also because CM7 allows for a keyboard doesn't mean every device running CM7 will. Search the forums for more information. I know that some of the developers have been working on it for CM10 but I don't recall seeing any posts saying that they have it working definitively.
As for specific sites or tutorials. Just visit the various android boards and look for the Noob guides. Search google for more details on subjects you want to know about.
Click to expand...
Click to collapse
Thank, I just took it back to Best Buy and they replaced it with an HD. I thought about an HD+, but I use my nook for reading more than anything (lots of comics, some novels), and the 9" is much less comfortable for that. Now I need to root this bad boy, and I don't have to monkey around with roms other than rooting because the HD already has support for an external keyboard.
This can be closed, as far as I am concerned. Thanks.
I've read countless forums on the rooting and roms and kernels and I have the most basic grasp of what each do. It seems that every time I read an article or forum post at some point something is mentioned that is over my head or that I don't fully grasp. I would love to not brick my phone. I need someone to explain my options and what I can do like I'm 5. What is Odex or Deodex? HOW do I find roms and kernels that work for my phone. What is clockworkmod and ADB? And what can I do to make sure I don't completely brick my phone.
I currently have an AT&T S4 that I rooted with Casual. Through casual it also loaded TWRP. I made a backup of everything it would let me check. I need to get a kernel onto this phone that will allow me to run Call Recorder "http://forum.xda-developers.com/showthread.php?t=1441643"
I am required to have a call recording feature on my cell phone or I'm tied to a landline for work. I had a Galaxy S2 Skyrocket that this program worked perfectly on.
I would like to for the most part keep the phone looking stock. Although I'm not sure what features I could add by going with a different rom.
I'm sorry for the noob questions.
There is a 1% chance of your device bricking if you follow all the correct root steps. Clockworkmod is like twrp. It is a custom recovery to let you put custom Roms on. ADB is the android device bridge. It let's you control your android from Ubuntu command prompt. Hope this helped
Sent from my SCH-I545 using xda app-developers app
No offense meant, I honestly can't suggest you Root or ROM your phone if you can't follow the root procedure without getting confused. If you don't understand the basics how are you going to take care of issues that will inevitably come up? Desperately asking for help when your phone is looping isn't a good answer.
ADB
Odex and Deodex
ATT galaxy s4 forums, kernels are under Original Development
TWRP and CWM are just different types of recoveries. I don't like CWM because the wipe options aren't all in one menu which is bothersome. But both work well. I suggest TWRP to all my friends to limit the amount of "my phone won't boot" phone calls I get.
And the only way to ensure you don't mess up your phone is by not messing with it at all.
Mebct76 said:
I've read countless forums on the rooting and roms and kernels and I have the most basic grasp of what each do. It seems that every time I read an article or forum post at some point something is mentioned that is over my head or that I don't fully grasp. I would love to not brick my phone. I need someone to explain my options and what I can do like I'm 5. What is Odex or Deodex? HOW do I find roms and kernels that work for my phone. What is clockworkmod and ADB? And what can I do to make sure I don't completely brick my phone.
I currently have an AT&T S4 that I rooted with Casual. Through casual it also loaded TWRP. I made a backup of everything it would let me check. I need to get a kernel onto this phone that will allow me to run Call Recorder "http://forum.xda-developers.com/showthread.php?t=1441643"
I am required to have a call recording feature on my cell phone or I'm tied to a landline for work. I had a Galaxy S2 Skyrocket that this program worked perfectly on.
I would like to for the most part keep the phone looking stock. Although I'm not sure what features I could add by going with a different rom.
I'm sorry for the noob questions.
Click to expand...
Click to collapse
Every last one of those questions can and would be answered through very few Google searches. Hell, searching this site will return a lot of the same results. There's even an XDA Wiki for such FAQ. And why are you posting in Verizon if you have AT&T and there's and AT&T section for the S4? Just sayin'
Wrong forum
I would also like to suggest you make sure to post in the correct forum for your device to ensure any answers you get are applicable to what you're using. The OP indicates you have an AT&T S4, yet you posted in the Verizon forum. Should you ever have an issue with your device and need further assistance, getting responses specific to the Verizon device versus your actual device could cause further problems for you.
EDIT: Didn't see Delakit's response before posting mine
Delakit said:
Every last one of those questions can and would be answered through very few Google searches. Hell, searching this site will return a lot of the same results. There's even an XDA Wiki for such FAQ. And why are you posting in Verizon if you have AT&T and there's and AT&T section for the S4? Just sayin'
Click to expand...
Click to collapse
Yeah I just noticed it was in the Verizon section. My bad. It appears I wasn't paying close enough attention when I posted that.
Dubbsy said:
No offense meant, I honestly can't suggest you Root or ROM your phone if you can't follow the root procedure without getting confused. If you don't understand the basics how are you going to take care of issues that will inevitably come up? Desperately asking for help when your phone is looping isn't a good answer.
ADB
Odex and Deodex
ATT galaxy s4 forums, kernels are under Original Development
TWRP and CWM are just different types of recoveries. I don't like CWM because the wipe options aren't all in one menu which is bothersome. But both work well. I suggest TWRP to all my friends to limit the amount of "my phone won't boot" phone calls I get.
And the only way to ensure you don't mess up your phone is by not messing with it at all.
Click to expand...
Click to collapse
I can follow the root procedure just fine and have rooted my phone. How can I learn if I just sit back and say "well guess I can't do it". Your right there are going to be the inevitable issues. The only way to ensure that I never learn this stuff is to not mess with it. I'm fully aware of the risks and potential rewards of this. But I'd like to figure it out. It is probably difficult for the senior guys such as yourself to remember what it was like first starting out. You've got multiple devices with multiple influences on the current setup of the phone at stock and because of the multiple hands in the making of each phone you have different rules and procedures for each one. The sprint S4 is different from the AT&T s4 which is different from the T-mobile S4. So following a guide doesn't always help if you don't completely understand the terminology. Can I use a mod kernel on a stock rom? From what i've read, yes but if it is AT&T it must be loki'd, ok What does loki do, why does it need to be loki'd, can I loki any S4 designed kernel, and HOW do i Loki something. I have yet to find something that answers all of those. Would you like to try? Maybe someone has answered them and I just can't find it.
Also, it appears I posted this in the Verizon forum instead of the AT&T forum. It was late and I wasn't paying that close of attention. My apologies.
Icculus760 said:
I would also like to suggest you make sure to post in the correct forum for your device to ensure any answers you get are applicable to what you're using. The OP indicates you have an AT&T S4, yet you posted in the Verizon forum. Should you ever have an issue with your device and need further assistance, getting responses specific to the Verizon device versus your actual device could cause further problems for you.
EDIT: Didn't see Delakit's response before posting mine
Click to expand...
Click to collapse
Thanks...I wasn't paying close enough attention when I posted that.
Mebct76 said:
I can follow the root procedure just fine and have rooted my phone. How can I learn if I just sit back and say "well guess I can't do it". Your right there are going to be the inevitable issues. The only way to ensure that I never learn this stuff is to not mess with it. I'm fully aware of the risks and potential rewards of this. But I'd like to figure it out. It is probably difficult for the senior guys such as yourself to remember what it was like first starting out. You've got multiple devices with multiple influences on the current setup of the phone at stock and because of the multiple hands in the making of each phone you have different rules and procedures for each one. The sprint S4 is different from the AT&T s4 which is different from the T-mobile S4. So following a guide doesn't always help if you don't completely understand the terminology. Can I use a mod kernel on a stock rom? From what i've read, yes but if it is AT&T it must be loki'd, ok What does loki do, why does it need to be loki'd, can I loki any S4 designed kernel, and HOW do i Loki something. I have yet to find something that answers all of those. Would you like to try? Maybe someone has answered them and I just can't find it.
Also, it appears I posted this in the Verizon forum instead of the AT&T forum. It was late and I wasn't paying that close of attention. My apologies.
Click to expand...
Click to collapse
Holy crap, hyper questions. Let me try to tackle them.
I remember what is was like. As weird as it sounds, I've never been hesitant about breaking my phone even when it was my only device. But everyone is different. I have learned the most when I've made my device unusable for a few days. Everyone learns and functions differently though. In Psychology they call it the Theory of Multiple Intelligences. Some people are brilliant but can't visualize anything. Some are brilliant and can't take tests. I could go on and rant about our school's piss poor management of teaching children correctly according to their "intelligences" but I'll just stop there.
GSM is different than the CDMA versions because the radios are looking for entirely different signals. Srint, USC, Metro, and Verizon all being CDMA. Radios are the biggest pain when trying to port IMO.
Loki is an exploit to work around the locked bootloaders of ATT and VZW. There is a thread somewhere on exactly how it works. But there are also loki patches posted and the better recoveries all automatically loki patch boot.img's for you.
Almost every gs4 version has their own versions of each kernel built off of the aboot and boot images of the stock files. For instance ktoonsez has a kernel available for all the carriers and one for touchwiz and one for aosp. If you are running stock you would simply flash his kernel for TW and it would install just fine on the stock ROM without you knowing anything about loki or how it works.
To be honest, I don't know enough about the actual vulnerabilities and exploits to FULLY understand loki. But I don't need to. It works. I plan to learn more about root vulnerabilities later. But I can only work on so much at once.
You can flash other carrier's kernels, but I wouldn't recommend it if there are kernels that suit your need for your carrier. I say this because I did loki the 4.3 kernel designed for the 9505 and got it working on my vzw gs4. BUT things may be broken or not fully working due to the differences in the kernels themselves. If you don't want to tear into things, it's best to just run the one for your phone.
I think I got it all. Maybe not though.
The best way to learn is with a nexus device. You can't brick that thing if you tried, and even if you were trying, you'd have to know what you were doing to brick it.
I mean, as long as you have the money to replace your phone, and don't mind not having an operational phone, dive right in. I've gone a weekend without a phone, stayed up til 2am trying to fix my phone when I had to be at work at 6:30, but I like to tinker with stuff and I'm fine with that.
Sent from my SCH-I545 using Tapatalk 4 Beta
Yeah I've bricked my gnex before and I learned a lot from it. There is almost always a way to fix a bricked phone whether its Odin or somehow flashing a new ROM. And like what was said before there is only a 1% chance you'll actually brick your phone. A lot of people think they are bricked when it is only a soft brick instead.
Sent from my Galaxy Nexus using xda app-developers app
First, and foremost, hello. I am new here, and I'm glad to be a part of the forum. Secondly, I'd like to apologize if I am posting this in the wrong section.
The topic I'd like to ask you a few questions about today is ROM Flashing, and the steps I should be taking to stay safe. I originally started playing around with Android devices around a year ago, but I recently started to delve deeper. I am the proud owner of an AT&T ZTE Z998 Mustang, and I have rooted it successfully. While in the process of rooting, I saw all of the warnings of how I should do a NANDROID backup, so that was my first instinct. I tried installing Clockworkmod, but to my dismay, they did not have an official version for my phone. I did happen to get lucky and find a version someone ported on their own. I attempted for a whole night before falling prey to error after error, and decided to give up. I went on without any backups, fiddling with my device. Luckily, I did not mess anything up, except for "accidentally" deleting the AT&T startup animation. (Haha.) Tonight, though, I happened to get the urge again, so I made some more attempts. After receiving the same error, I decided to look that error up word for word, and found that I did not have enough room on my Micro SD. I managed to clear enough room, and jumped in joy when I saw that I could delete an app, then restore and have it be back again. It was quite a big accomplishment for me. I've decided that I want to try flashing a custom ROM. The ROM I have chosen is the MIUI ROM. It seems quite popular, and I enjoy the iOS-esq feel of it, as well as its seamless theme changing. The only problem is, there is not an official release for my device. In fact, I have yet to find any ROM with an official release for my device. That is why I am coming to you guys.
My Questions:
Can I use a ROM that has not been specifically made for my device?
Will I still be connected to the AT&T Network?
If so, can I expect errors?
Am I truly safe with this newly acquired backup?
Anything you think I should know?
I'd like to thank you for any help in advance.
BrendonButton said:
First, and foremost, hello. I am new here, and I'm glad to be a part of the forum. Secondly, I'd like to apologize if I am posting this in the wrong section.
The topic I'd like to ask you a few questions about today is ROM Flashing, and the steps I should be taking to stay safe. I originally started playing around with Android devices around a year ago, but I recently started to delve deeper. I am the proud owner of an AT&T ZTE Z998 Mustang, and I have rooted it successfully. While in the process of rooting, I saw all of the warnings of how I should do a NANDROID backup, so that was my first instinct. I tried installing Clockworkmod, but to my dismay, they did not have an official version for my phone. I did happen to get lucky and find a version someone ported on their own. I attempted for a whole night before falling prey to error after error, and decided to give up. I went on without any backups, fiddling with my device. Luckily, I did not mess anything up, except for "accidentally" deleting the AT&T startup animation. (Haha.) Tonight, though, I happened to get the urge again, so I made some more attempts. After receiving the same error, I decided to look that error up word for word, and found that I did not have enough room on my Micro SD. I managed to clear enough room, and jumped in joy when I saw that I could delete an app, then restore and have it be back again. It was quite a big accomplishment for me. I've decided that I want to try flashing a custom ROM. The ROM I have chosen is the MIUI ROM. It seems quite popular, and I enjoy the iOS-esq feel of it, as well as its seamless theme changing. The only problem is, there is not an official release for my device. In fact, I have yet to find any ROM with an official release for my device. That is why I am coming to you guys.
My Questions:
Can I use a ROM that has not been specifically made for my device?
Will I still be connected to the AT&T Network?
If so, can I expect errors?
Am I truly safe with this newly acquired backup?
Anything you think I should know?
I'd like to thank you for any help in advance.
Click to expand...
Click to collapse
Bump.
Hi there. Welcome to the forums!
Unfortunately, the bad thing about phones that aren't very popular in the grand scheme of things means less people have them = less people making stuff for it. Developers often end up picking phones that are going to have more support from the manufacturer and more people will be able to enjoy the fruits of their labors. This of course, is a general rule, and of course there are exceptions, but your phone doesn't seem to be one of them. Companies like ZTE aren't concerned about putting out the source code for phones like this means that it is hard, to almost impossible, to make a really custom rom work correctly due to driver issues among other things.
So to answer the questions:
1) Sometimes, but very dependent on the models, carriers, and which software updates. General rule of thumb is that if it isn't based off the same chipset, it won't have a chance of working. But there are lots of other things to consider to, like radio versions, bootloader status, partition layout, etc. Long story short, there's no easy answer and there are lots of caveats.
2) + 3) See above.
4) You SHOULD be safe if CWM told you that the nandroid was completed successfully, but just like any other software based things, things happen.
Best way to be safe is to be able to reflash the original firmware for the phone back to it, but not even sure if that's an option for you - which goes back to ZTE not giving a $^!* about these cheap little phones for small prepaid companies. They save money by not doing any extra work like providing firmware, updates, source code, etc.
The only forums I know that mess with these kinds of things are:
http://unleashedprepaids.com/forum-1491.html
Not for your phone specifically, but similar ones:
http://androidarea51.com/zte-phones/
So yea, slim pickings.
es0tericcha0s said:
Helpful Info.
Click to expand...
Click to collapse
First, thank you! I was waiting all day. I was a little disappointed with the answer, though. v.v Do you know if there are any ROMS that will work with ANY device? Like even bare minerals versions of AOSP ROMS that have yet to be touched?
Also, I am slowly saving for a 64GB Black Nexus 5, so I shouldn't be stuck but more than a month or more so.
BrendonButton said:
First, thank you! I was waiting all day. I was a little disappointed with the answer, though. v.v Do you know if there are any ROMS that will work with ANY device? Like even bare minerals versions of AOSP ROMS that have yet to be touched?
Also, I am slowly saving for a 64GB Black Nexus 5, so I shouldn't be stuck but more than a month or more so.
Click to expand...
Click to collapse
No, sorry. It's just not possible. Your best hope would be to use the debloated rom in the unleashed prepaids forum and use the Xposed Framework.
http://unleashedprepaids.com/thread-8769.html
http://unleashedprepaids.com/thread-8771.html
http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401
http://repo.xposed.info/module-overview
I have the Nexus 5 (don't think they come in 64 - only 16/32) but it's awesome and there are so many roms that it'll make your head spin. lol
es0tericcha0s said:
No, sorry. It's just not possible. Your best hope would be to use the debloated rom in the unleashed prepaids forum and use the Xposed Framework.
http://unleashedprepaids.com/thread-8769.html
http://unleashedprepaids.com/thread-8771.html
http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401
http://repo.xposed.info/module-overview
I have the Nexus 5 (don't think they come in 64 - only 16/32) but it's awesome and there are so many roms that it'll make your head spin. lol
Click to expand...
Click to collapse
Oops, sorry, yeah, that's what I meant. xD
But, I can not wait for it!
Just some final thoughts and questions:
I do have Xposed installed already, but have yet to look around in it due to the hundreds of modules. Do you have any suggestions about which I should look at for cosmetic needs? I have tried to use Gravitybox, but it force closed upon entry every time I used it, so I deleted it.
I understand that the limitation is very high because of the fact that it is a closed sourced company, but many ZTE Devices are listed to have compatible ROMS, such as MIUI ROM. If I try to use a ROM specified for a different phone, do you know what could happen? I feel that it may not even open, or if it does, it'll have tons of errors and not work upon entry, or even work but have certain things like the camera that will not connect. I'm only worried about high margins of fatal breakage. If it is some silly error that I won't have to "worry" about, I'm okay with fooling around.
If I do try to install a new ROM, but want to go back, will it affect anything on my previous backup? I know backups copy EVERYTHING, but I'd just like to make sure I won't do serious damage.
Lastly, thank you for all the help. It means a ton.
BrendonButton said:
Oops, sorry, yeah, that's what I meant. xD
But, I can not wait for it!
Just some final thoughts and questions:
I do have Xposed installed already, but have yet to look around in it due to the hundreds of modules. Do you have any suggestions about which I should look at for cosmetic needs? I have tried to use Gravitybox, but it force closed upon entry every time I used it, so I deleted it.
I understand that the limitation is very high because of the fact that it is a closed sourced company, but many ZTE Devices are listed to have compatible ROMS, such as MIUI ROM. If I try to use a ROM specified for a different phone, do you know what could happen? I feel that it may not even open, or if it does, it'll have tons of errors and not work upon entry, or even work but have certain things like the camera that will not connect. I'm only worried about high margins of fatal breakage. If it is some silly error that I won't have to "worry" about, I'm okay with fooling around.
If I do try to install a new ROM, but want to go back, will it affect anything on my previous backup? I know backups copy EVERYTHING, but I'd just like to make sure I won't do serious damage.
Lastly, thank you for all the help. It means a ton.
Click to expand...
Click to collapse
Gravity Box wouldn't work because it is for more AOSP based things. As far as theming goes, you can try HK Theme Manager or Ex Themer. For the idea of trying to install a rom for another ZTE phone, well, best case scenario is that it doesn't flash at all. Worst case is that it does flash, and you lose something like your IMEI, baseband, or one or more of your other partitions and all of those are potentially unrecoverable, no matter what kind of backups you have. This wouldn't be one of those, "Oh, shoot, that didn't work, I'll just factory reset or restore my backup and be good to go..." kind of situations.
es0tericcha0s said:
Gravity Box wouldn't work because it is for more AOSP based things. As far as theming goes, you can try HK Theme Manager or Ex Themer. For the idea of trying to install a rom for another ZTE phone, well, best case scenario is that it doesn't flash at all. Worst case is that it does flash, and you lose something like your IMEI, baseband, or one or more of your other partitions and all of those are potentially unrecoverable, no matter what kind of backups you have. This wouldn't be one of those, "Oh, shoot, that didn't work, I'll just factory reset or restore my backup and be good to go..." kind of situations.
Click to expand...
Click to collapse
Oh, wow! Thanks! I'm glad you pointed that out before I tried. So, I should be okay as long as I flash that ROM from the Unleashed Prepaid page? Now I am afraid, but curious.
Also, thank you for the theme modules names, I will kindly note them.
Should be fine. It's 95% stock and I'm sure they only had one version of android for the phone so should be pretty close to what you have now. Benefits would be the unsecured boot.img which is easier for root and other things to stick, init.d which allows you to run scripts (everything from being able to mount a partition of an SD card to use for extra space for apps to memory management stuff like V6 Supercharger), and a bit easier to theme and debloat.
es0tericcha0s said:
Should be fine. It's 95% stock and I'm sure they only had one version of android for the phone so should be pretty close to what you have now. Benefits would be the unsecured boot.img which is easier for root and other things to stick, init.d which allows you to run scripts (everything from being able to mount a partition of an SD card to use for extra space for apps to memory management stuff like V6 Supercharger), and a bit easier to theme and debloat.
Click to expand...
Click to collapse
Thank you.
I'll look into it tonight. I will try and tell about what happens tomorrow-ish.
Cool. Good luck.
Hi all. I am hoping for some very basic advice. I got a Kindle HDX 7 a few days ago. I have not connected it to wifi yet to avoid automatic updating of the firmware. When I go to settings>device>system update it tells me that my current firmware version is 13.3.0.5 installed on Jul, 30, 2013. From all I have read that is a good thing if I want to root my device.
The big question I have is if I actually should?
In a perfect scenario I could just replace the fire OS with a normal version of Android and not have any hassles. But I have heard that could play hell with battery life and I haven't actually found a good guide on how to do that safely with a KF HDX, so back to just rooting.
-Is there a comprehensive tutorial on how to root my device with it's current settings? I have looked but it is difficult to judge what is old/outdated information and what still works.
-How safe is this aka. how likely am I to brick my device just by rooting it (I'm a tech savvy user, but I wouldn't dare delve deeper than that) and how buggy are rooted devices if at all?
-How would I keep my device from upgrading automatically after rooting?
-Isn't the point of upgrades also to plug security holes that would compromise personal data? How would that work with never upgrading?
I would appreciate if the experienced rooters amongst you could advise me on this. Thank you!
Welcome. It is nice to see these questions asked before you have broken your device, as opposed to after. While I am by no means an expert, here are a few answers to get the ball rolling.
snorklm said:
In a perfect scenario I could just replace the fire OS with a normal version of Android and not have any hassles. But I have heard that could play hell with battery life and I haven't actually found a good guide on how to do that safely with a KF HDX, so back to just rooting.
Click to expand...
Click to collapse
This is entirely doable, not all builds are buggy.
snorklm said:
Is there a comprehensive tutorial on how to root my device with it's current settings? I have looked but it is difficult to judge what is old/outdated information and what still works.
Click to expand...
Click to collapse
Not completely, but since root is what you are after currently, go to the dev section and check out the roundup on the rooting tool. Read through the posts.
However, it is simple for you to root. You can go to towelroot and do it that way. Regardless, I suggest reading the dev threads to see some of the other options. Also, there is some good info in the rollback, now what? Threads in this section.
snorklm said:
How safe is this aka. how likely am I to brick my device just by rooting it (I'm a tech savvy user, but I wouldn't dare delve deeper than that) and how buggy are rooted devices if at all?
Click to expand...
Click to collapse
All it does is give you the option of allowing root permissions to an app. Root in it of itself is perfectly harmless. It won't change the function of the device at all if you do not utilize this new power. However, if an app (or you), change the wrong file, it could be devastating.
snorklm said:
How would I keep my device from upgrading automatically after rooting?
Click to expand...
Click to collapse
There are some block updates threads. Probably the easiest is to use the kindle fire xposed plugin (I think that still works). Be careful with xposed. It does allow you to make changes which can make your device unstable.
snorklm said:
Isn't the point of upgrades also to plug security holes that would compromise personal data? How would that work with never upgrading?
Click to expand...
Click to collapse
Yes, and achieving root access is looked at as a security hole by Amazon. You also will be missing out on new "Features." This could include KitKat. Although, you can flash the new software with TWRP which if done correctly will be stable, but that will require a lot more reading. It is really only the custom builds which are unstable. They are buggy because they are not quite finished. Head over to the dev section to find out more. In the end, it all comes down to what you plan to do with it, and how much you plan to learn along the way.
Good luck,
Leko
Sent from my KFTHWI using Tapatalk
Hi Snorklm - welcome to the forums. The title of your post made my day
If you haven't already read through the response from Leko. Hits all the important points and mirrors what I was going to write (beat me to the punch).
Some additional thoughts:
- Be sure to block OTAs before connecting to WiFi. Your options will become much more restricted if Amazon pushes an update.
- I prefer HDX Toolkit to block OTAs. Xposed is great (I use many modules) but does carry some minor risks as Leko mentioned. Note HDX toolkit requires a tethered connection (standard USB cable is fine) along with installation of Kindle drivers on the host machine.
- While a bit more involved I suggest you consider installing TWRP which will provide more robust recovery options should something go wrong. It is very easy to do given your current firmware level. Life without TWRP (or similar recovery) is like driving without a seatbelt.
- I have been using ggow's excellent implementation of the Nexus ROM. Rock solid and functional. The only minor downside is its Jellybean roots. ggrow is currently working on bringing newer variants to the table; Lollipop seems likely at some point. CM11 and CM12 are also available (or being worked on) but have some minor issues that may or may not matter to you.
I know you were hoping for a step-by-step tutorial. While that may become reality someday I suggest you spend an evening reading through the forums before deciding on a course of action. Yup, a ton of information is old/confusing but there is no one right answer for everyone. Ask questions along the way. Lots of folks are happy/willing to help if you've done your homework.
Good luck!
lekofraggle said:
Welcome. It is nice to see these questions asked before you have broken your device, as opposed to after. While I am by no means an expert, here are a few answers to get the ball rolling.
Click to expand...
Click to collapse
Thanks for the overview and answering my questions! I'm still iffy on the whole process but I'm going to do some reading before I decide if this is for me .
Davey126 said:
Some additional thoughts:
- Be sure to block OTAs before connecting to WiFi. Your options will become much more restricted if Amazon pushes an update.
- I prefer HDX Toolkit to block OTAs. Xposed is great (I use many modules) but does carry some minor risks as Leko mentioned. Note HDX toolkit requires a tethered connection (standard USB cable is fine) along with installation of Kindle drivers on the host machine.
- While a bit more involved I suggest you consider installing TWRP which will provide more robust recovery options should something go wrong. It is very easy to do given your current firmware level. Life without TWRP (or similar recovery) is like driving without a seatbelt.
- I have been using ggow's excellent implementation of the Nexus ROM. Rock solid and functional. The only minor downside is its Jellybean roots. ggrow is currently working on bringing newer variants to the table; Lollipop seems likely at some point. CM11 and CM12 are also available (or being worked on) but have some minor issues that may or may not matter to you.
Click to expand...
Click to collapse
Thanks for the reply. I'm especially grateful that you name-dropped some specific recommendations because it gives me a starting point to research. I have already read about TWRP (though as of yet I have no idea how to install it) and I will definitely take a look at HDX Toolkit.
I am probably going to try rooting while keeping an eye on the stock Android variant. I'm not sure if I'm ever going to be brave/clever enough to dare try that though. Bricking my device would seriously make me cry .
I have one more question about the Firmware versions (well, I probably have several, but this is the only one I remember right now.) I have seen somewhere on this forum that you can also upgrade the amazon firmware manually until you have the version you want instead of getting pushed to the newest one from amazon itself. Is that correct? If yes, which is the best version to stop on while still being able to root and keeping the option of stock Android open? I ask because I would like to strike a balance between a reasonably upgraded OS and one I still can do stuff with without getting nannied by amazon.
Here is where I recomend you start reading.
http://forum.xda-developers.com/showthread.php?t=2986004
This is the link for the thor twrp.
Here is how a normal device works.
You gain root permissions, and then if you mess up, you jump into a recovery and fix things. You probably (definitely) will lose some data, but you learn, curse, and move on with your life.
However, the bootloader of the Kindle hdx is locked. This means that if you cannot boot right, and you cannot get to recovery, you have a 200 paperweight.
Now, on the old firmware, brilliant people found a way to unlock (sort of) the bootloader. So, you have a pretty universal reset switch. This is why the recommendation is there to grab twrp. It really is helpful if you have a hankering to tinker. In reality there is less of a risk of bricking the device with it. Once you have it, then you can update to the newest firmware (in theory) if you do so the right way, you still keep twrp.
Now, if you want root and do not care about the safety belt, update to 13.4.5.2 and root it, but block updates.
But know, you lose the option of twrp at that point.
I hope this helps.
~Leko
Sent from my KFTHWI using Tapatalk
Edit: whether you go the easy route, and choose towelroot (just google it or go to towelroot.com for that route), the more involved twrp, or something in between, I highly recommend you learn what adb is and how to use it. The hdx toolkit comes with the drivers and it is not too difficult to use, but it is essential if you get into a sticky situation. Here is the toolkit link.
http://forum.xda-developers.com/showthread.php?t=2665683
lekofraggle said:
I hope this helps.
~Leko
Click to expand...
Click to collapse
Yes, this helps. Thank you! :good:
lekofraggle said:
Now, if you want root and do not care about the safety belt, update to 13.4.5.2 and root it, but block updates.
But know, you lose the option of twrp at that point.
Click to expand...
Click to collapse
@snorklm - you can go up to 13.3.2.6, secure root and still retain the option to later install TWRP and a different ROM without having to engage Amazon for a downgrade (you will still have to roll your device back to an earlier FW before installing TWRP but you can do this yourself). Note the 13.3.x.x series is based on the previous version of Fire OS (which in turn is based on Jellybean) but it remains perfectly serviceable. A lot is happening with more recent Amazon firmwares which ultimately may allow other ROMs and recoveries to be installed without having to downgrade to 13.3.x.x. Keep an eye on the forums.
Thanks for starting this topic snorklm. I was thinking in the same way whether it's worth to get it rooted or not.
I don't mind about the warranty as I think I will not break my Kindle Fire some how, just care about the services from Amazon Prime.
Actually I already contact Amazon service to roll back to version 3.2.5 and I'm waiting for the instruction email. My plan is going to root it, play around with the device then if something doesn't satisfy me, I will do un-root.
Would anyone show us the real advantages of rooting Kindle Fire here? As far as I know basic users just root their device to install Google Play Store which can be done on other un-rooted ones (like the method of Imma Wake) I still like Amazon service for Movies streaming so I'm a bit confused of what to do next, keep update it accordingly or give Rooting a try
Please share more your stories here.
Thank you
leoclark said:
Thanks for starting this topic snorklm. I was thinking in the same way whether it's worth to get it rooted or not.
Would anyone show us the real advantages of rooting Kindle Fire here?
Thank you
Click to expand...
Click to collapse
I ran with 3.2.6 (rooted) for nearly a year before installing a different ROM. I was able to obtain most apps from either the Amazon store or 1Moble. The primary reason I rooted was to squash various Amazon services that launch at boot and consume resources in the background (CPU, memory, battery). Goodreads, FreeTime and numerous communication services to name a few. I also wanted to install Xposed for a few modules I find especially handy and block OTAs to retain maximum flexibility. I side loaded many gapps but never installed the play store and associated services. Also Opera (never liked Silk). I retained my Prime privileges and for the most part enjoyed the mostly stock tablet as Amazon intended. Ultimately I began to miss some purchased apps not available elsewhere and longed for Apex or Nova. Other launchers can be made to run on Fire OS but the experience isn't as fluid. There is also something to be said about having a fairly consistent UI across my various Android devices.
While Fire OS isn't horrible I recommend rooting (when possible) and blocking OTAs to maximize current/future options As others have pointed out the act of rooting generally does not introduce instability unless the method used to exploit a vulnerability has side effects or the conditions for root are not fully met. There are some risks as you now have the power to brick your device. SuperSU (or similar privilege manager) is your friend and should keep you out of trouble if used judiciously.