Related
I'd like to ask those wishing help with troubleshooting to please help us to help you.
When reporting a problem it is useful to get as much information as possible, the more information we have, the easier it is to help.
Is it running from SD or Nand.
What radio version.
What build are you having the problem with.
What kernel/nbh are you using.
If you can, try to post any error messages.
Please try to post your questions in the thread for the build you are having issues with, it's more likely to get noticed there, and other users of that build may have the solution you need.
All this information saves a lot of time, and helps cut down on confusion, especially the SD/Nand part.
I have trouble with signal, it's weak than WM, when I used WM my radio is 1.65, I'm up to 1.71.09.01 and flash Android (NAND menthod) and the signal so weak
So Android support radio 1.65??? I want to back 1.65
I'm using TYTN 2 Kaiser _ WarmDonut version
Another Qs:
Q.How can I use my fone like a modem? I see in Menu have Modem but I don't know how to connect with my PC as a modem
Q.How can I connect to my PC via Wifi ad-hoc? (if available, please guide step by step- because I'm... chicken )
Q.GPS so slow and weak (in Vietnam)
Q.It so hard to power off (It's hang)
Best regard
I had issues with 1.71.xx radios too, and went back to 1.65.21.14 and my signal was good once more.
To change radio, download the radio you wish to use from this thread http://forum.xda-developers.com/showthread.php?t=393182, post 3 has the download links you need.
Once you have it downloaded, rename the ruu_signed.nbh to kaisimg.nbh and copy to SD card, flash using the power+camera method you used to flash the nand nbh, you will not have to reinstall Android when you do this.
The modem in question refers to the gprs modem used for data, it should be possible to use the phone as a modem, but as far as I know this is not working properly yet.
Not sure if you can do this either, I know wifi works for data transmission, but accessing the computer this way with android may not be possible, yet.
Gps problems may depend on which nbh you have installed, some of the more recent nbh's perform better than older ones. I'd recommend Kallt_Kaffes NBH's as I know these are quite good for gps, for me at least. http://forum.xda-developers.com/showthread.php?t=660158, you will need to load the nbh into the editor and set the correct panel type, keyboard, and 3d type, ( donut in your case), then save as kaisimg.nbh and copy to SD and flash using power+camera, again this will not affect your android install.
Power off issues may be nbh related also, however this can still happen anyway, usually pulling out the battery will sort out the reboot issues.
many thank for quick reply, I love Android on my phone
thank you again
I was wondering what steps to take when the android loader gets stuck in a loop, when I install andriod right after install it boots fine but when I try to boot second time, after andriod appears on the bottom of the screen it will go into some kind of loop. I have tried different radios and a different version of hardspl, and a few nbh panels as well as reinstalling the system, any help would greatly appreciated.
Phone: AT&T Branded TILT
OS: Nand w/Incubus Super Froyo Installed
Radio: 1.70.18.02
NBH: kaisimg-panel2-320-tilt-froyo-07-07-10
HardSPL: v3.34.hard
Everything looks fine, although I haven't used that particular build, however bootloops are commonly build or kernel related.
Have you tried other builds? Or is it just this build that does this?
Generally panel type only affects the display on the screen itself, or sometimes problems with sleep mode.
Since you have a froyo kernel installed, maybe you could install this build to see if it helps? http://forum.xda-developers.com/showthread.php?t=724821
Yeah I have tried other Froyo builds and they worked, but I just like the way Super Froyo build is put together. But if it is the build then its is the build. Oh well maybe next release. Ok thank you for your time, guess I will give the GZO build or the one you suggested a try.
Installed the kernel you suggested, it works. It boot looped once, then I cleared the dalvik cache and it booted again after install. I don't know if that is what it is used for, but it worked after that.
It is a awesome build, battery life works correctly, signal is good with radio, and wi-fi works good. But I had one more questions.
1. What is up with live wallpapers, on some builds I have used some work on one build but not the other, I have looked through the forums, but can find no solution for this. Is it because of the amount of RAM in the TILT as I saw somewhere or is there a fix. Even in this build when I try to load a live wallpaper on a couple of them is just stays on wallpaper loading and stay black screen.
I would like to take a minute to thank the people that make this awesome stuff, now my TILT has more current software than my BACKFLIP, so my older phone is now newer than my new phone, and I would also like to thank the people who help others out on this forum, I don't think a lot of people like myself would get anywhere without your help.
Forgot to mention dalvik cache. oops, ah well, you found it anyway
It's another of those occasionally useful things, like fix permissions, I have used it before to fix unusual behaviour, but not tried it on a bootloop.
Live wallpapers are usually pretty buggy at best, it's complicated, memory is one problem, cpu speed another, and 3d handling yet another, some wallpapers work ok, but slow, others just won't, ever. I just delete them before install, along with a few other minor customisations such as deleting a few ringtones and notification sounds, changing boot animations, nothing that affects the core of the build, just personalising a bit
I'm using:
1)incubus's Super Eclair 6.1, with the downgraded settings.apk which enables wifi (another member offered the settings.apk from a previous version (3, I think) as an androidupdate.tar)
2) Currently radio 1.71.09.01 (thinking of switching to 1.65.21.18 to improve reception)
3.) Currently using the latest Dzo kernel for eclair (07-02-2010, I think)
My problem is that my data connection doesn't work (and this has been an issue on just about every release, save for one Froyo install where the data autostarted once, and then I never saw a 2g/3g notification and mobile internet didn't work).
I'm currently in India, and I've used the correct APN settings (they have worked on other phones including Nokias, iPhone, and a USB modem). I've tried asking the question in the SuperEclair vogue thread, but alas, no love. I'd really appreciate if you could help me on this, or at least guide me in the right direction, because android (especially eclair) is too awesome to abandon for this single issue.
By the way, everything else works, Wifi (with the mentioned update), GPS, Voice, and SuperEclair is the fastest that I've found so far.
I have seen a number of issues with data such as this, and i'm afraid none have had a truly satisfying resolution.
However I would try:
Downgrade the radio as planned, this may help, and certainly won't hurt.
Boot to installer, and run fix permissions and clear dalvik cache, this has been known to fix various issues, not certain why yet.
Double check the apn settings, especially the MCC and MCN settings, a lot of online guides seem to miss these two, but they are important.
Not sure where to point you after this, apart from a long trawl through the thread here, however if you do get it resolved please post back, and if not, try another post on it in the build thread, along with the steps you have taken to resolve it, it may convince someone to have a closer look at this issue.
data connection
I too have had this problem after installing a recent froyo build to nand....I had checked no.start data when flashing dzo's latest kernel using nbh editor and had to reset my apn settings. Remember to open your modem utility and press connect twice....this actually starts the connection......Radio type could also be an issue..Ive had good luck with the 165's with 2 different froyo builds....Hope this helps.....
Thanks for the replies! I'm going to try this out (need to recharge the data service on my prepaid) but one thing I did notice was that the MNC/MMC were different that those listed on my providers website. Hopefully this will help.
I have tried to switch on the data using the modem utility, and the utility itself says that data is connected, but it never really worked. In settings, there is an on/off switch for mobile internet, and a mobile internet settings. When I click the on/off switch, then mobile internet just goes gray and does nothing. I'll try to post back to the Super Eclair vogue board, but I think that Incubus might have moved on...
I'll update once I get my gprs service paid up. Again, thanks for the help!
The process com.android.phone has stopped
Those are my first Android experiences, so I`ve got problems .
Phone : Kaiser (TyTN II)
OS : Win Mo 6 Profess (original-not flashed)
Radio : 1.27.15.32
I`m trying to install Android on the SD card, without additional partitioning. I`m currently trying this Android version : Eclair 2.1 for Kaiser/Vogue/Polaris -- polymod 2.1 gamma [Based on OpenEclair 1.2.2 (XDA thread)]
and using this too : How to run Polymod’s AWESOME 2.1 Eclare Build and Updates (the forum didn`t allow me to post links for the Android versions). I`ve tryed this too : VaniljEclair RLS7c - A fast and stable CM 5.0.8 for Vogue/Kaiser/Polaris [2010-07-02] - the same result
I`ve done everything according the instructions... Starting Haret.. Hit D-Pad, Install, clear data... etc. etc... It actually starts to install... and everything seems fine... At some point it brings me again the install menu, I`m hitting exit, and then come some errors ?!? I forgot to type them down... Something like that some files cannot be found... And after rolling errors for a while the Android actually boots ! But then come errors too... At the first time it brings me the dial pad to enter my pin-code... I entered it , but it says it is wrong...I wasn`t wrong ofc . For the next time I simply disabled my pin in Win Mobile and try again... After the Android booted it says : The process com.android.phone has stopped unexpectedly. Please try again. , and some button like "cancel" or something like that. I'm hitting it , the Android guy appears and a message " Hit the android to begin" with a hand pointing it. I`m hitting the android - nothing happened !
I`ll be greatfull if someone can help me , or at least give me some clues !
Thank you .
p.s. sorry for my english... not my native language ;-)
Your problems are mainly in the OS version, 6.0 is not recent enough to run Android, and the radio version will also give problems, my advice would be to update to the most recent stock version, which would enable you to run Android.
This would of course wipe your present installed OS and a more recent version may or may not exist for your language, ( with the wiki down I can't be more specific with which files would suit you best).
Thanks
zenity said:
Your problems are mainly in the OS version, 6.0 is not recent enough to run Android, and the radio version will also give problems, my advice would be to update to the most recent stock version, which would enable you to run Android.
This would of course wipe your present installed OS and a more recent version may or may not exist for your language, ( with the wiki down I can't be more specific with which files would suit you best).
Click to expand...
Click to collapse
Thank you for your fast response . But I`ve tryed (I`ve tryed again today) before to download an official WinMo 6.1 ROM from HTC_com , but according to my TyTN II`s serial number , they said : "Sorry, this software download is not suitable for your device". And I want an original ROM... I`m not sure that I can manage to flash a cooked one on my HTC . So I guess I`ll stay with the original WinMo 6.0 withut Android .
Thanks anyway
To flash a cooked rom you would need HardSPL, it is possible to do this for WM 6.0.
Regarding an upgrade to WM6.1, this too should be possible, I'd tend to disregard the warnings about upgrades being 'unsuitable'. The unavailability of certain upgrades is more to do with them being designed for certain providers or areas, rather than their actual unsuitability for the device itself.
If you have a need for a language specific rom this too is probably available from another source, if the wiki was available then there is a table of rom upgrades that would almost certainly contain just what you would need.
Note that the wiki links are all official HTC roms, and would not need HardSPL.
@Zenity - You had given me some advice on getting the gprs working on my eclair install (Eclair problems/Android problems thread). Well, I ended up ditching Super Eclair for polymod 2.1d, and mobile data started working out of the box (which is odd, because it wasn't really working before, but who am I to question?!). Now my only issue is that if I activate wifi without first deactivating mobile data, then wifi gets caught in a loop and won't connect (i.e "Connecting, obtaining address, unsuccessful, connecting, obtaining address, unsuccessful" and on on on...). Then if I try to deactivate data or wifi, both get grayed out and say turning off, but never do. I'm fairly positive this is some conflict between data and wifi, because I've connected to the same AP without any issues while the data connection is off. Regardless, this is the most fully functional implementation that I've found. Still playing around, now that I have the time I'm diving a little further into tweaking and hacking through these releases.
Thanks for the help man. I've been on xda-devs since I first got this Att Tilt, mainly reading and learning, but I've noticed that a fair number of people don't take the time to further explicate and help people through problems and troubleshooting. You and kallt_kafee are both awesome when it comes to responding to less knowledgable users, and I for one really appreciate it. So Cheers, bro!
Thanks matcha, the main reason I still find polymod 2.1D my build of choice is that of them all, it just works, all the other builds do to, but I have found less issues from users on Polymod than the other builds, perhaps it's age has something to do with it, it has less 'new' features than the others, so less to go wrong, and perhaps also that it has grown with the whole android on kaiser project.
Anyway, appreciate the vote of confidence, really I'm just trying to give back a small measure of what Xda-Developers has given me
How many people on here would be interested in flashing a custom ROM (currently the way we do official updating) that incorporates rooting, ad-hoc support, some other parts of touchnooter, and an attempt at working bluetooth? Given something like this would completely void our warranties. Just curious to see if there are enough people interested, therefore I may build something.
Count me in ... ! CM7 would be very nice ...8)
Whenever you root you are already voiding your warranty. As mine is far gone (lasted for a couple of hours only), I'm ready to flash it, mostly for increased support on hardware buttons, ready-made ad-hoc access and maybe BT (BT keyboard on Nook! WTF!).
GO AHEAD, DrNookington.
Count me in. I like it.
Correct me if I'm wrong but if rooted aren't there ways to restore to factory image and remove root.
Yes... I support you !! Please make an custom update. This can be done without root the nook?
And another question, is there any way to run android without root the nook touch? I mean, I can run android from sdcard without root the nook (like a dual boot that nook color have).
Thanks
Muadiv
I'd be in.
I probably wouldn't be interested in a rooted stock setup that I could do manually with a little more work. But a full CM7 or similar, definitely yes! Is there a working recovery yet? I think Nemith mentioned something about CWM awhile ago, but I'm not sure if he ever looked into it.
working bluetooth would be great. id love to be able to listen to music, answer calls and read books all on the same device at the gym.
+ 1.
Also agree something like cm7 would be tops.
Count me in
Demand = Demand + 1
Count me in. It would be great if market search worked.
Count me in too.
A better launcher (Maybe nook-styled) would be great, so that we can easily access our reading docs (pdf, epub, what-ever) and easily do mail/calendar/internet stuff.
Bluetooth is not really important to me as I can do fine with the touch keyboard (short emails anyway).
Booting from the SD card would be a plus... although I do not care about the warranty. I just want to read my pdfs and my docs (mainly work related I must say).
I would love too see a custom rom even it was simply stock cause then I'd have a base to make my own changes too
A ROM with a working market, gmail, etc, would be awesome. I had my nook working properly once, back at v1.0.0 firmware, but since i went back to stock to get the v1.0.1 firmware, i have not been able to get the market to search, and while trying to fix that, i end up messing other apps up. Every time. And i've gone back to my stock image twice and did a factory reset and data reset at least three additional times.
Frustrating to say the least.
I´m also very happy with cm7 on my sgs. It would be the very best solution for the new nook...
I am interested. This needs at least a Froyo update so we can do app2sd. CM would work best, then we can use apps that give issues (Kobo etc)
Of course I would love to flash a custom rom. That is the only reason I read the forums in xda is to learn about flashing custom roms. Stock roms are usually too limited.
Count me in as a alpha, beta, or whatever tester.
Yes please
CM7 would be fabulous...
working gapps and a new launcher pro style launcher would make me as happy as a clam in mud.... a hobo on a ham sandwhich.... a boy living next to an all girl school....
So i'm fairly new in these things (custom ROMs and such), and recently installed Hashcode's cyanogen mod from here.
After failing the first time and temporarily bricking my kindle (after making the stupid decision to wipe all my data), I luckily managed to get the rom into the data folder and flashed it from there with TWRP. So now i've got the mod working, but for some reason, the wifi isn't working. I try to turn it on but it doesn't seem to be detecting anything.
Anyway, i've searched around that this problem does tend to happen with certain ROMs, and I wanted to know if this is a current limitation of the unofficial release. I'd post in the other thread, but i'm a new member ,etc. so I thought i'd try my luck here
Works for me..
Sent from my Amazon Kindle Fire2 using Tapatalk 2
cerial13 said:
So i'm fairly new in these things (custom ROMs and such), and recently installed Hashcode's cyanogen mod from here.
After failing the first time and temporarily bricking my kindle (after making the stupid decision to wipe all my data), I luckily managed to get the rom into the data folder and flashed it from there with TWRP. So now i've got the mod working, but for some reason, the wifi isn't working. I try to turn it on but it doesn't seem to be detecting anything.
Anyway, i've searched around that this problem does tend to happen with certain ROMs, and I wanted to know if this is a current limitation of the unofficial release. I'd post in the other thread, but i'm a new member ,etc. so I thought i'd try my luck here
Click to expand...
Click to collapse
I'm sure Hashcode himself would help you if you joined the freenode irc channel, #kindlefire-dev or #kf2-dev . All you have to do is show up and ask for help.
Wifi on KF2
It also worked for me. Did you use the "20130131 image here: http://tinyw.in/CBnF
Did you install / flash the Gapps zip from TWRP?
http://forum.xda-developers.com/showthread.php?t=2105077
I would consider reflashing both entirely,
Joe
yudanjah said:
It also worked for me. Did you use the "20130131 image here: http://tinyw.in/CBnF
Did you install / flash the Gapps zip from TWRP?
http://forum.xda-developers.com/showthread.php?t=2105077
I would consider reflashing both entirely,
Joe
Click to expand...
Click to collapse
wifi connectivity on the wifi chip is not the best. Amazon's choice was bad there, and I'm talking to hash about what could be going wrong in the wifi firmware department.
Hello,
I've read through the Everything thread on Development, as well as searched using the xda search and google site search, but come up with nothing.
The Everything thread mentions that the current version of CWRM won't charge when the phone is off or in recovery, but I can't find anything about which version is the 'latest' (6.0.1.2, 5.0.2.7), nor if this also affects the TWRP recoveries (2.6.3, 2.4.1)? For that matter, I can't find anything that even mentions the charging problems at all aside from the Everything thread!
If there is a charging problem with all of the third party ROMs, is there a method to go back to the stock recovery after flashing in a ROM and backing up /efs/? I'm basically shooting for a fully functional phone and I don't plan on changing ROMs all over the place, just root and ICS.
Help?
Thanks!
TooG435 said:
Hello,
I've read through the Everything thread on Development, as well as searched using the xda search and google site search, but come up with nothing.
The Everything thread mentions that the current version of CWRM won't charge when the phone is off or in recovery, but I can't find anything about which version is the 'latest' (6.0.1.2, 5.0.2.7), nor if this also affects the TWRP recoveries (2.6.3, 2.4.1)? For that matter, I can't find anything that even mentions the charging problems at all aside from the Everything thread!
If there is a charging problem with all of the third party ROMs, is there a method to go back to the stock recovery after flashing in a ROM and backing up /efs/? I'm basically shooting for a fully functional phone and I don't plan on changing ROMs all over the place, just root and ICS.
Help?
Thanks!
Click to expand...
Click to collapse
I think something like 6.0.4 the latest CWMR. ( you can build with http://builder.clockworkmod.com/ , Existing Device option doesnt work)
It charges in latest TWRP, you can see "+" char when on charge next to the battery level.
Stock uses recovery for official upgrade, and factory reset. We have only offline charge issue, but recovery has no effect on it. Offline charger works with a limitation. I wouldnt bother you with the explanation, since you said you would like to use stock ICS.
You can backup efs in rooted rom without recovery. You can always flash recovery with odin phone in download mode.
Thanks.
I guess I had assumed the comment was referring to the builds in the Development forum, not the overall CWMR project! Is there a currently recommended recovery, or is it a toss up to personal preference? I'm not so much tied to ICS as tied to a completely working ROM - especially as I see all the bluetooth and skype issues with the JB ROMs, which (as far as I can tell) are still unresolved / unknown?
TooG435 said:
Thanks.
I guess I had assumed the comment was referring to the builds in the Development forum, not the overall CWMR project! Is there a currently recommended recovery, or is it a toss up to personal preference? I'm not so much tied to ICS as tied to a completely working ROM - especially as I see all the bluetooth and skype issues with the JB ROMs, which (as far as I can tell) are still unresolved / unknown?
Click to expand...
Click to collapse
I make TWRP for i927, we dont have other up to date, but you can build yourself.
Dont you have issue with stock ICS? I made up to date issue list in me CM 10.2, you could decide it suit for you or not, you may know stock limitation already.
I hope voip issue would be resolved soon.
bubor said:
I make TWRP for i927, we dont have other up to date, but you can build yourself.
Dont you have issue with stock ICS? I made up to date issue list in me CM 10.2, you could decide it suit for you or not, you may know stock limitation already.
I hope voip issue would be resolved soon.
Click to expand...
Click to collapse
My only real requirement in a phone is that it be reliable - I don't want to have to pop out batteries or have no audio on calls if I get stranded in the middle of nowhere. At this point, my phone is still in the mail - got a used one from a friend, but it hasn't arrived, so I haven't had much ability to experiment yet.
My Android experience is exclusively with a Transformer TF101, which had 4.0.4 ICS stock and is currently running Katkiss JB 4.2.2_226 (Katkiss 4.3 isn't stable enough for me yet, was getting daily crashes last time I tried). All of the phone components are new to me - and the Glide seems to have a more fragmented recovery scene than the TF101, which is pretty much TWRP or nothin'
Thanks again for your help!
Sorry in advance as I'm sure these questions are added somewhere. Just looking to be pointed to some threads or other places with good info.
I just got a new 2013 N7 and it came with 4.3 build A# JWR66N.
Upon first run, there are a couple of system updates available that I am hesitant to install. I'm guessing they are to update it to the newest 4.4. Just wondering if I should do this or if it will cripple or lock anything else having to do with rooting or flashing custom ROM's
First thing I noticed is it looks just like the custom EOS 4.1.1 I flashed into my Xoom tablet a few years ago and coming from a Galaxy tab, there is no option to clear all recent apps (the Galaxy has a small garbage can symbol in the recent apps list that gets rid of everything with one touch). I was wondering if there is something like this for the N7 (either an app or a custom ROM that has it).
Also, I knew before buying it that OTG was crippled. My friend has one and said he rooted and used stickmount to get full OTG read-write access. Wondering if there is a better alternative (or if there is a custom ROM with this already fixed).
I have been seeing a lot of stuff about a N7 FLO. What is this and how do I know if I have it?
Last, I am definitely interested in unlocking/rooting/adding a custom ROM to it but looking for some good direction for this. I have been searching through these boards and my head is spinning from all the different info. Last time I rooted and flashed a custom rom was a few years ago with my Motorola Xoom and I did it all manually with ADB and some other stuff and it went smooth. It seems like everything written on here is made for people that already know what they are doing and although I have done it before, and have no problems following instructions, it's been a few years I am looking for a good link or links to some beginner guides so I can kinda go back to the beginning and refresh myself before going into this. I am also not opposed to using WUG's toolkit or similar but would still like to better understand doing things manually in case something goes wrong.
Any info you can provide would be greatly appreciated.
happy4ya said:
Sorry in advance as I'm sure these questions are added somewhere. Just looking to be pointed to some threads or other places with good info.
I just got a new 2013 N7 and it came with 4.3 build A# JWR66N.
Upon first run, there are a couple of system updates available that I am hesitant to install. I'm guessing they are to update it to the newest 4.4. Just wondering if I should do this or if it will cripple or lock anything else having to do with rooting or flashing custom ROM's
First thing I noticed is it looks just like the custom EOS 4.1.1 I flashed into my Xoom tablet a few years ago and coming from a Galaxy tab, there is no option to clear all recent apps (the Galaxy has a small garbage can symbol in the recent apps list that gets rid of everything with one touch). I was wondering if there is something like this for the N7 (either an app or a custom ROM that has it).
Also, I knew before buying it that OTG was crippled. My friend has one and said he rooted and used stickmount to get full OTG read-write access. Wondering if there is a better alternative (or if there is a custom ROM with this already fixed).
I have been seeing a lot of stuff about a N7 FLO. What is this and how do I know if I have it?
Last, I am definitely interested in unlocking/rooting/adding a custom ROM to it but looking for some good direction for this. I have been searching through these boards and my head is spinning from all the different info. Last time I rooted and flashed a custom rom was a few years ago with my Motorola Xoom and I did it all manually with ADB and some other stuff and it went smooth. It seems like everything written on here is made for people that already know what they are doing and although I have done it before, and have no problems following instructions, it's been a few years I am looking for a good link or links to some beginner guides so I can kinda go back to the beginning and refresh myself before going into this. I am also not opposed to using WUG's toolkit or similar but would still like to better understand doing things manually in case something goes wrong.
Any info you can provide would be greatly appreciated.
Click to expand...
Click to collapse
Do not use a toolkit. If there is one thing you take from this response, take that.
N7 2013 has two models, flo and deb. flo is the wifi version, deb is the LTE version.
Updating a Nexus device will not hinder your ability to root/unlock the bootloader. Other OEMs do this, and that's why I'm not using their devices anymore. Done with them.
Clear all recents button is removed on later Android versions. Custom ROMs or Xposed/GravityBox to get it back.
OTG/Stickmount issue: I believe that if you have a custom kernel that supports it, not an issue, don't need Stickmount. No experience in this area, however.
The stock look of a Google OS is standard AOSP. That's why the ROM you flashed on your Xoom looks very similar.
If you are new to Nexus devices, I would probably recommend using stock for a while. When you become tired of the absolute lack of customization, switch to SlimKat and use Banks' minimal gapps package. The gapps thread is in the N5 apps section, but works just the same on N7.
If you are going to unlock the bootloader anyhow, here is what you want to do to update to the newest version without the extra steps.
You need to install the drivers, get ADB+fastboot, and download the KTU84P factory image for your device. All links in signature. If you have the wifi model, razor, if you have the LTE model, razorg. razor=flo, razorg=deb.
You can find the fastboot tuts all over the internet, and it's too long to type. But basically, you want:
fastboot oem unlock (this will wipe your device, but only needs to be done one time)
fastboot reboot-bootloader
<you can run the flash-all.bat file that came with your fasctory image now>
after that's done, you'll want to go back into bootloader mode and flash TWRP (link in signature).
fastboot flash recovery twrp.img
That's a lot of information written with very poor coherence. If you need elaboration, just ask. But it has you pointed in the right direction.
Aerowinder said:
Do not use a toolkit. If there is one thing you take from this response, take that.
N7 2013 has two models, flo and deb. flo is the wifi version, deb is the LTE version.
Updating a Nexus device will not hinder your ability to root/unlock the bootloader. Other OEMs do this, and that's why I'm not using their devices anymore. Done with them.
Clear all recents button is removed on later Android versions. Custom ROMs or Xposed/GravityBox to get it back.
OTG/Stickmount issue: I believe that if you have a custom kernel that supports it, not an issue, don't need Stickmount. No experience in this area, however.
The stock look of a Google OS is standard AOSP. That's why the ROM you flashed on your Xoom looks very similar.
If you are new to Nexus devices, I would probably recommend using stock for a while. When you become tired of the absolute lack of customization, switch to SlimKat and use Banks' minimal gapps package. The gapps thread is in the N5 apps section, but works just the same on N7.
If you are going to unlock the bootloader anyhow, here is what you want to do to update to the newest version without the extra steps.
You need to install the drivers, get ADB+fastboot, and download the KTU84P factory image for your device. All links in signature. If you have the wifi model, razor, if you have the LTE model, razorg. razor=flo, razorg=deb.
You can find the fastboot tuts all over the internet, and it's too long to type. But basically, you want:
fastboot oem unlock (this will wipe your device, but only needs to be done one time)
fastboot reboot-bootloader
<you can run the flash-all.bat file that came with your fasctory image now>
after that's done, you'll want to go back into bootloader mode and flash TWRP (link in signature).
fastboot flash recovery twrp.img
That's a lot of information written with very poor coherence. If you need elaboration, just ask. But it has you pointed in the right direction.
Click to expand...
Click to collapse
Thanks for all the info. So I definitely have the FLO model.
I would like to use Titanium Backup for Root and a few other things that need root access so I definitely want to do this.
Also, being that this tablet has no micro SD, I definitely want to have read-write access with a USB drive. I've had this for almost a week already and I haven't loaded anything into it yet because I figured I'd be wiping it. I really don't want to mess with stock because of the lack of a few things. I really just can't stand having devices with restricted use. That's not what I paid for.
I never used Kit Kat before and not sure if I'll like it. Do you know if you can go back to 4.3? I know with some of the other devices (like my Galaxy S3 phone), once you update it OTA, they lock stuff up and you cannot roll back.
Also, does anyone have any idea on a completely new out of the box unit what is killing the battery so fast? On my galaxy 7 tab, it would last over a week in standby. This thing was dead in about a day and a half after I took it off the charger. and I charger it full a couple of times already. Or does battery life just suck on this tablet?
I did find a post somewhere that said to turn off google location and I just did that. We'll see if it does anything.
happy4ya said:
Also, does anyone have any idea on a completely new out of the box unit what is killing the battery so fast? On my galaxy 7 tab, it would last over a week in standby. This thing was dead in about a day and a half after I took it off the charger. and I charger it full a couple of times already. Or does battery life just suck on this tablet?
I did find a post somewhere that said to turn off google location and I just did that. We'll see if it does anything.
Click to expand...
Click to collapse
You can roll back to 4.3. Google hasn't gone full Apple yet. But I strongly advise against doing so, as it's a large step backwards.
Understood on stock OS, agree no options anywhere. Slimkat+franco.kernel+banks gapps. You won't look back. Also in developer options, switch to ART. Dalvik sucks. If you're using Banks' minimal gapps, the lack of some syncing libs (for the AOSP calendar nobody uses) will cause random FCs until you reboot a second time. Nothing to worry about. Just grab the Google Calendar, or whatever calendar you use, from the play store and freeze the AOSP one with TiBu. Another FC you might see is gms.location. It should only happen once. Something with play services.
Once you are rooted, you can grab BetterBatteryStats to see what's killing your battery. On stock installs, it's mostly going to be location-based stuff keeping it awake. You already turned off reporting, but you also need to switch location mode to Device only.