Hi,
I just got my HDX und now i want to install custom recovery and root the device. I have just a few questions before i do so an got no exect answers by searching the forum:
1. If I do a backup with custom recovery can I go fully back to stock?
2. Is there some sort of Factory Image to download to override custom revocery?
3. Can I Undo and go back to stock recovery If i have to send the device back to Amazon?
I just want to know if I can totaly revert all changes bevore I change something.
thx
maroc84 said:
Hi,
I just got my HDX und now i want to install custom recovery and root the device. I have just a few questions before i do so an got no exect answers by searching the forum:
1. If I do a backup with custom recovery can I go fully back to stock?
2. Is there some sort of Factory Image to download to override custom revocery?
3. Can I Undo and go back to stock recovery If i have to send the device back to Amazon?
I just want to know if I can totaly revert all changes bevore I change something.
thx
Click to expand...
Click to collapse
If you are new to this device you probably should read the first post here http://forum.xda-developers.com/showthread.php?t=2786190.. And the answer to all your questions are technically yes. If you do not brick or break your tablet anywhere along the way and providing that you are willing to do all homework necessary and then some before attempting to do anything.. You probably need to read through all the threads about brick devices to know what things not to attempt that will cause you to break your device.. Remember all the information is here if you learn how to use this forum and remember each section of the forum has several pages of threads of information.. You have a whole lot of reading to do if you do not want to end up another of this devices victims lmao
Don't get me wrong. I own a nexus 5 and the nexus 7 (2013) (rooted, custom kernel, exposed etc.) but due to the open system and bootloader so as the asop makes it easier to handle it. I already read the warnings but the Windows supported root tool should be a easy way.... not?
Okay obviously
maroc84 said:
Don't get me wrong. I own a nexus 5 and the nexus 7 (2013) (rooted, custom kernel, exposed etc.) but due to the open system and bootloader so as the asop makes it easier to handle it. I already read the warnings but the Windows supported root tool should be a easy way.... not?
Click to expand...
Click to collapse
there is not a problem getting it rooted you may have read the warning but you're not understanding it.The problem is not rooting the device. The problem is what people are deciding to do with their root access . And it may be my imagination or may not but this seems to be a favorite tablet for mommy and daddy to buy the kiddies.. Then they come here not knowing how to do their own research and find the easy way to root their device , There n fine there again not a real problem it's what they are doing ...BRICKING! There again not really a problem for me but when they come to this forum acting like somebody owes them something or somebody better step up and hurry hurry come help them fix their device before mommy and daddy find out ... Burying perfectly good information that I like to access under redundant questions because they are too lazy to do their own homework .. Repeatedly asking the same questions over and over again that have already been answered over and over again they just refuse to read the information and expect others to first to come to their special lil thread and inform them like this is kindergarten again . And somebody should be holding their hand because mommy and daddy bought them a special kindle fire..THAT IS LOCKED DOWN.. With no fast boot capabilities currently working there is a lot of talk about it but no consistent.... Repeat there is not a one click fix for this device ....... unlike most other tablets like I said one of your questions asked if you can just flash and fix ... At this time NO. If you really know what you are doing and you are not afraid of or can afford to turn your tablet into a paperweight.. There are ways to get your system flashed too repair mistakes or goofy behavior (even return to stock) but not from BRICK STATE. Long story short your 1 Click Easy Way to root.. Through ignorance, laziness , and the comprehension level of a fruit fly .. For this device in the wrong hands might as well be a sledge hammer ... Repeat in no way is a Nexus 5 ,at the moment remotely similar other then android base, to this tablet... Is what you should have gotten from the thread that I posted a link to... flash and modify at your own risk and Responsibly.. Nobody here is responsible for anything you do to your tablet. Or responsible for coming to rescue you if or when you screw it up... Please read all the brick threads to save everybody lots of famed face palms and headaches... Us and yourself trust me.
Thanks. I know it can be depressing to tell people "you question or problem was answered just two days ago, just read and collect the right information you need" I don't want to change necessary files like build.prop or do things where there is an exact warning to do so because it's not really stable...
The warning pinned to this forum just got me unquestioning if there are serious problems in every usually customisation (root, custom recovery, gapps) so doing just that could probably brick the tab because maybe the closed system makes everything risky and unpredictable in contrast to a vanilla android device.
well
maroc84 said:
Thanks. I know it can be depressing to tell people "you question or problem was answered just two days ago, just read and collect the right information you need" I don't want to change necessary files like build.prop or do things where there is an exact warning to do so because it's not really stable...
The warning pinned to this forum just got me unquestioning if there are serious problems in every usually customisation (root, custom recovery, gapps) so doing just that could probably brick the tab because maybe the closed system makes everything risky and unpredictable in contrast to a vanilla android device.
Click to expand...
Click to collapse
Well for example I am only a mechanic I'm 42 years old I am not well-versed in computers but android have been a hobby of mine for about five years .. But I have very little problems following directions. And I have been able to accomplish anything I wanted to do with many many phones and tablets including this one... So if you're willing and have the understanding that this thing is very fickle and likes to actup
Where other devices would not be problems... It can be a very nice device for the right person and a very big headache for the wrong one. There are currently a lot a bugs with pretty much anything that you try to do with this thing if not done with absolute precision and patience. And perseverance. I currently own three different HDX tablets with several other Samsung.. And I switch frequently. I do have Google on my HDX but I do not depend on them for all of my Google needs. Remember at least for now while these things are locked up tight they are pretty much only an Amazon media device along with if you are willing to brave and yada yada yada you may get some Google services working like many of us have. Enjoy all of my HDX thoroughly but I also have a understanding of the current limitations.
Related
Ok I need help i have just Unlocked my prime , and I have a lot of questions. First let me say Im aking because i have already researched so please no smart a$$ comments! I am on ICS .28
1) what do I do next?
2) do i need to root or do the roms give me root
3) do i need to do nv flash i looked at the instructions and im lost.
4) I dont have any other progrms so not sure what i need
5) do I install clockwork recovery mod or twrp does it matter?
I really need help to make my prime great , please help!!!!!!
jaisan72980 said:
Ok I need help i have just Unlocked my prime , and I have a lot of questions. First let me say Im aking because i have already researched so please no smart a$$ comments !
Click to expand...
Click to collapse
Simple advice: read more! The questions you ask are all very basic and have been answered in depth on this forum. It is really important you understand what you are doing before proceeding further since Asus in their wisdom have adopted a policy which makes their devices particularly easy to brick.
It is a very good thing you are on ICS so whether you find it difficult or not your first step must be to understand and implement NVFlash. This is your insurance policy and you really should go no further without it .
Why exactly did you unlock your Prime? What was the limitation or the roadblock that you ran into that unlocking solved?
Jgrimoldy said:
Why exactly did you unlock your Prime? What was the limitation or the roadblock that you ran into that unlocking solved?
Click to expand...
Click to collapse
did you miss this part "to make my prime great"?
whycali said:
did you miss this part "to make my prime great"?
Click to expand...
Click to collapse
Actually, I saw that. I was a little curious about specifics. Among the countless threads of folks bricking their Primes, it's amusing to read a justification of "to make it great".
I partially unlocked in order to replace the stock ROM with one that didn't have a gimped download manager. The default download manager will give a fake error and then actively delete the file upon completing any .APK (yes, it judges on the extension) download from a website that doesn't give it specific headers, which is used to stop people from pirating apps via common file sharing sites (which are not set to give these headers)... but also stops a lot of normal android dev page downloads from working as well (for example emulator programs not available in the market).
Previously I needed to download things with Opera (which has it's own download manager and thus doesn't pass files to the stock one) in order to get around this anti-piracy code, but that's just a chore. After swapping ROMs, I haven't had that happen (though the ROM I swapped to forgot to remove similar protection on bluetooth files, which I'm going to report now as soon as I get 10 damn posts).
Also when I updated to Jelly Bean, I lost root (Voodoo root keeper was used but it failed, read around to see I'm not the only one that had the root backup wiped out when doing the official Jelly Bean upgrade), and so far unlocking in order to be able to flash custom updates is the only way to regain it.
Anyways the OP will want to install some recovery.flash thing like TWRP so they can flash their own files to the ROM, like the su binary, which is needed to root.
Hi! I'm a total cell newbie, so pardon.
I want to root my phone just so I can actually put apps on my SD card. There's a few bits I want to understand first:
I've read that I am not going to want to accept OTAs. I've also read that some phones automatically accept OTAs. Since I don't plan to change my ROM (and I am not entirely sure what ROM refers to... is my "TouchWiz" a ROM?), how can I be sure that my default software isn't going to go trying to install OTAs without asking me?
Is a bricked device actually completely worthless? There's no way to get it back into a working state at ALL, or just no way to get it working without help from your carrier? And what is a "soft brick"?
If I manage to root my phone with the CASUAL one-touch program, how do I unroot if I were interested in doing so?
Please either avoid or explain any jargon you may use in your reply. For instance, if you refer to opening an app.... please just do the courtesy of saying it's an app rather than just assuming I know. If you use an acronym, assume I have no idea what it stands for. It took me forever to figure out what an OTA was, and I still don't quite understand what a ROM is... and that's the extent of my acronyms.
Thanks.
Wow, a lot of demands. Why not start here, as it should answer many of your questions. Threads are stickied for a reason.
http://forum.xda-developers.com/showthread.php?t=2024207
Mandolin Bee said:
Hi! I'm a total cell newbie, so pardon.
I want to root my phone just so I can actually put apps on my SD card. There's a few bits I want to understand first:
I've read that I am not going to want to accept OTAs. I've also read that some phones automatically accept OTAs. Since I don't plan to change my ROM (and I am not entirely sure what ROM refers to... is my "TouchWiz" a ROM?), how can I be sure that my default software isn't going to go trying to install OTAs without asking me?
Is a bricked device actually completely worthless? There's no way to get it back into a working state at ALL, or just no way to get it working without help from your carrier? And what is a "soft brick"?
If I manage to root my phone with the CASUAL one-touch program, how do I unroot if I were interested in doing so?
Please either avoid or explain any jargon you may use in your reply. For instance, if you refer to opening an app.... please just do the courtesy of saying it's an app rather than just assuming I know. If you use an acronym, assume I have no idea what it stands for. It took me forever to figure out what an OTA was, and I still don't quite understand what a ROM is... and that's the extent of my acronyms.
Thanks.
Click to expand...
Click to collapse
Touch wiz is a style of ROM if you will.
Touch wiz roms for Samsung.
Motor blur roms for Motorola.
Sense roms for HTC
Aosp roms for nexus phones.
When you have a "touch wiz ROM"
It builds from the stock base code basically. They add freatures and themes and basically ROMs are endless to what they can do.
My phone never tells me about OTAs.
I believe the only time they do this is when on a stock rooted ROM is when something bad could go wrong
Never had any problems on custom ROMs however.
Next,
Bricked devices are very rare and only happen out of stupidity or carelessness in most cases.
Google will tell you how to fix. But I wouldn't worry about it.
As a very frequent flasher of ROMs I have experienced many of times a soft brick. Or a phone in boot loop.
This is when the device powers on but will not boot up. ( stuck on boot animation or splash screen are most common.)
ALL OF THESE ARE FIXABLE.
You can always wipe in a recovery and normally that fixes it.
Soft bricks normally happen from not wiping or bad download.
Also remember you have Odin as a last resort.
Also you can read the sticky threads in android development to figure out how to unroot
They will give you a better explanation on how to do so.
All this is answered by xda and Google.
They are what taught me what I know
They will teach you as well over time.
PM me if you have any other questions
Hit the thanks button so I feel important!
Haha
God bless the American people.
Hello XDA!
I opened a new thread hopefully to open a discussion about improvements I think are beneficial, my experience over the last 24 hours that a couple sticky edits would have saved me (and others) time.
My Story:
Yesterday (5/3) I saw I had around a 250 mb OTA. Excited (hoping for 4.2, assuming was the 4.1.2 that VZW released recently) I kick on WiFi, download and watch as it reboots and appears to install successfully. Time for work to end, grabbed phone off charger as it appeared to be rebooting after successful install, and ran out to catch train home.
Downstairs, at train stop, take a look at phone and heart sinks as it is in a fast splash screen loop, blinking the VZW Galaxy Note 2 screen for about 1 second in endless loop. As I had never seen before was thinking firmware update bricked it and I was looking at least until Tuesday before I'd have a working phone. Luckily, I was able to quickly see that I could still get into download mode, so knew I was (likely) going to be ok.
Get home and a Quick Robin, to the Internetz! later I'm browsing XDA and following the t=t=2024207 walkthu to restore stock. FYI, my device prior to the failed OTA was unrooted stock. At this point I'm not sure if it's going to restore, so I'm trying to do the true stock, no unlocked bootloader in case it has to be RMA'd. I've downloaded all my files, waited patiently for the slow hosting service for the FXZ(?) to download and am grinding through it and of course it fails at the system.img. Luckily, blessedly the awesome community here had released the image that included the unlocked bootloader which I was (after waiting to download, etc etc again) able to successfully get installed via Odin, booted up and working successfully.
So, while the first post section regarding restore to stock does indicate users with latest firmware "L4 OTA Only" shouldn't be attempting to use the Official VRAL I didn't think it applied to me. I would say that a fair amount of individuals looking to take the drastic step of a full restore to stock might be in a scenario like mine, where something significant has happened and likely confirming what OS/firmware/etc you are on might not be feasible. In my case, I assumed never rooted/unlocked vanilla device should be about as receptacle to an "official" restore as any. In this scenario, where a 100% for all devices stock recovery ("alternative") works, 'I feel that it should have been pushed harder than the official or at least blurbed with if you don't know what you are on, use this' While I understand that it is the "official" image, it has requirements for it to work. A co-worker had an ASUS TF300T that tried pushing a recovery image for ICS after he had upgraded to JB and it hard bricked his tablet, with ASUS wanting to charge him about 60% cost of the tablet to replace motherboard. That's heartbreaking, and I am sure since a hard brick wasn't a likely scenario here, why it wasn't mentioned.
Also: The download link for the Alternate Restore lists the file as: I605_VRALJB_Restore.tar.md5.xz which requires that it be unpacked using 7zip AND also that once extracted, it needs to be renamed to kick of the extra extension md5 in order for ODIN to see it properly as a PDA image file. (I605_VRALJB_Restore.tar.md5 ) Neither step is mentioned in the original post, and I had to read through to I believe the 11th page or so before realizing that was the problem. I'm sure with most of the people that are daily users of this forum knew automatically that these steps were required, but I would counter that a thread explaining how to restore Stock is one of the few threads that is likely to reach a larger, inexperienced demographic who would need to know such details.
Lastly, since (I thought) I had an unlocked bootloader, but otherwsie working phone again (Thank you, thank you thank you!) might as well get it rooted, and grab a ODEX'd stripped ROM with the OS release because getting the Software Update nag and not being able to complete or even brick my phone makes my OCD gland flex mightily. Was delighted to see an on-device APK root option which threw me back to the ease of z4root a few years ago with my Droid X. APK installs, and it roots so easily, like it had the functionality out of the box. I grab goo.im manager and install TWRP. Go to boot into custom recovery so I can install my sexy updated OS ROM and enjoy my fun device without all the yucky bloatware I've just ignored/dealt with for the last 2 months and I get the dreaded and in my opinion illegal "VZW unauthorized software" software brick.
Back to the forums, see I need another stock 'alternative' restore to fix AND a little confused, but believe I need to run a "jailbreak" bootloader unlock (CASUAL ?t=2118348) Which I haven't done yet. I have all files downloaded, just paused to post my experiences here.
So, this was main reason for my post, as I can understand some of why walkthru is laid out the way it is above, but why not have this included as part of the stickied root walkthru? It's mentioned thusly:
section 1a is a old method and no longer needs to be used unless the end user wants root only. proceed to Adam Outler's "JAILBREAK" thread linked at the bottom of this section for rooting and unlocking bootloader so custom roms can be flashed!!!
Click to expand...
Click to collapse
I couldn't find the link it refers to at bottom of section? I ended up googling to find guide. ((t=202420)
if this is still a requirement for root, custom ROM/Recovery, I would have made this steps 1-x of the root guide. is it because another person authored it? It would be nice to be able to credit and quote, I know alot of what drives contributors is the 'Thanks" and Donations, be great if XDA admins could round table and find a solution that allows for a consolidated guide for each device and still give each contributor a way to get their +1's and plug donation/web/twitter handle url's
So, is my understanding incorrect of what is needed or do folks agree with me that current setup is not the most efficient way XDA community could be offering instructive guides on Root/Mods? It would be wonderful if XDA Mods upon announcement of devices, when creating the forum threads for device (Development, OG Development, General, etc etc) created a blank thread for the how to root et.al and then allowed it to be edited by the community as a Wiki. Or even if an individual created, allow that person to allow x amount of other community members to edit, add and adjust.
I see droidstyle created a thread about questions for softbrick, and I might have to look at the original sticky thread about how to stock restore, but it seems he/she might have better saturation if this info was included in the original post. The stickied How To recover stock is direct accessible from a google search. I doubt his Q&A thread is or definitely not going to be one of the highest page-ranked sites.
So, please let me know if I'm just out of my mind, off the mark. I will give myself a small escape clause based on the fact that I probably scored about 2 hours of sleep last night messing around trying to get the note running again. I am actually concerned that the instructions for Return to Stock/Root/Etc for the VZW i605 doesn't have the link to unlock bootloader via casual and am hoping that following that process before rooting/customrecovery/ROM is correct, and not going to be another BrickGate for me. I know as OS versions are updated and/or Big Red and Big Blue constantly push patches trying to lock people out of their phones that instructions change and methods break. As new directions are implemented it's easy to lose steps as edits occur on the fly.
Most importanly! I hope this thread comes across as constructive criticism/suggestions, I have nothing but the highest respect for this community and it's contributors. Even skewed, outdated and conflicting information is better than no information and I SUPER appreciate the hard work required to get it out to us. I am most definitely not expressing displeasure with my experience or the content, only using the threads I mentioned as examples of what I personally see as opportunity for improvements XDA could implement that would allow for easier dissemination of the information the community is sharing so unselfishly. I only open it for discussion, so that others like me can access the information quicker with less confusion. I read comments of disgust and exasperation as people are directed to search, rather than post, and they are right, the information is invariably there, and most often or not within the first 5 posts of a thread. But sometimes when a developer talks to another developer, the tiny and considered minor details are not mentioned because it's considered common knowledge, and thats where the noobs, soccer moms and Grandmas can get left scratching their heads trying to puzzle how you got from point a to b. (Stereotypes used for comedic effect, please take no offense) I believe it would save alot of people having to answer the same questions over and over again time and frustration and freeing them to focus their talents on making us the next epic ROM/Kernel/App
thanks for reading! Also, I'm not just drive-by b*tching, if anyone is interested, I would love to show a mock-up of the i605 guide these great contributors have created as I would compile it. I'm passionate about mobile technology and customization, sadly my talents don't lie in the creation of such, only the enjoyment of it. But I'm a hell of a document admin. I create wiki's and KB's/sharepoint admin for a living, and would love to contribute what I know in that way
TeamWin Recovery Version: 2.5.0.0
I encrypted my device about two weeks ago. Today I tried flashing a new rom, which was Android 4.1.2. When it prompted me for my encryption password, I entered it correctly but it wouldn't accept it. I tried flashing another rom, which was 4.3, it accepted the encryption password but got bootlooped. My old device was on 4.3 to my belief. When I tried wiping /data in recovery it says it cannot mount /data. Help please?
Flash back to stock and decide if you want encryption or a device you want to flash.
That Won't Help.
imnuts said:
Flash back to stock and decide if you want encryption or a device you want to flash.
Click to expand...
Click to collapse
I've tried Google and that already. Sarcasm will not fix my problem so if you don't have a solution please move on and stop spamming.
...
Can anyone help?
So you used Odin and flashed your phone back to stock? No where in your post did you mention anything like that, or even allude to the fact that you flashed back to stock with Odin. If you want help, post better information, or figure it out yourself. Also, you can't have a device you want to be flash happy with on ROMs and an encrypted device. The two don't work, so you choose one or the other, not both.
Um...
imnuts said:
So you used Odin and flashed your phone back to stock? No where in your post did you mention anything like that, or even allude to the fact that you flashed back to stock with Odin. If you want help, post better information, or figure it out yourself. Also, you can't have a device you want to be flash happy with on ROMs and an encrypted device. The two don't work, so you choose one or the other, not both.
Click to expand...
Click to collapse
...How can I fix this. I flashed it using my recovery.
imnuts said:
So you used Odin and flashed your phone back to stock? No where in your post did you mention anything like that, or even allude to the fact that you flashed back to stock with Odin. If you want help, post better information, or figure it out yourself. Also, you can't have a device you want to be flash happy with on ROMs and an encrypted device. The two don't work, so you choose one or the other, not both.
Click to expand...
Click to collapse
Do you know how to do this or is this something you can't fix?
Read droidstyles thread at the top of this section. It has all of the information you will need to flash back to stock.
Sent from my SCH-I605 using Tapatalk 2
*Sigh*
This is why XDA annoys me. The "Recognized Developers" waste their time and other forum members time about how what they typed wasn't good enough for them. They could save a lot more time just asking questions that would help them understand the situation rather that be a nanny and tell the user how they didn't type up to their expectations, what they can do to make them satisfied, and then not respond for another 30 minutes.
ninten7 said:
This is why XDA annoys me. The "Recognized Developers" waste their time and other forum members time about how what they typed wasn't good enough for them. They could save a lot more time just asking questions that would help them understand the situation rather that be a nanny and tell the user how they didn't type up to their expectations, what they can do to make them satisfied, and then not respond for another 30 minutes.
Click to expand...
Click to collapse
You screwed yourself by saying I wasn't be helpful and to stop the sarcasm. You want help, don't bite the hand that feeds you. Flashing back to stock is a very simple process and well documented here and in other Samsung device forums. If you can't figure it out on your own, pay someone to do it for you, and then leave your phone stock. Rule 1 of modifying your phone should always be know how to recover, which you apparently do not. And posts like the two you've now made in this thread are not how you get help, and will most certainly turn everyone else that may have offered it away as well, since you're apparently too good to do any work on your own and criticize people when they aren't spoon feeding you.
Um
imnuts said:
You screwed yourself by saying I wasn't be helpful and to stop the sarcasm. You want help, don't bite the hand that feeds you. Flashing back to stock is a very simple process and well documented here and in other Samsung device forums. If you can't figure it out on your own, pay someone to do it for you, and then leave your phone stock. Rule 1 of modifying your phone should always be know how to recover, which you apparently do not. And posts like the two you've now made in this thread are not how you get help, and will most certainly turn everyone else that may have offered it away as well, since you're apparently too good to do any work on your own and criticize people when they aren't spoon feeding you.
Click to expand...
Click to collapse
He/she didn't bite the hand that fed them because you didn't help at all lol. I agree with this users statement and the only other complaint I have is how you need to make 10 posts before being able to post links but that I understand.
Is there any lolipop custom rom available on here for mediapad youth 2 s7-721w
Ive tried the links online , but I cant get past the ads even with inputting valid info
Please help me. Im looking everywhere with no luck, and my current system is wrecked
thanks
dermot31 said:
Is there any lolipop custom rom available on here for mediapad youth 2 s7-721w
Ive tried the links online , but I cant get past the ads even with inputting valid info
Please help me. Im looking everywhere with no luck, and my current system is wrecked
thanks
Click to expand...
Click to collapse
I have seen several links that "claim" to be custom Lollipop roms for the mediapad. However, as you had already noticed its all garbage ad links.
The good news is there are guides on youTube to get past all that junk (I tried it myself and it worked). I forgot which provider I used to give you exact instructions, but try a search on YouTube
The bad news is any lollipop rom for mediapad is "at best", some custom one with questionable legitimacy. I'd say avoid it for now. Adding insult to injury the general public worldwide isn't lining up outside stores for Medipad devices, much less Huawei in general, so Huawei has very little motivation to push out lollipop on Mediapads.
Also on a final note, a lot of these links for custom roms may come preloaded with malware that will not ask you for permission but take over your machine.
I strongly urge you to stay as is. Any benefits provided by lollipop over Kitkat are not worth the risk involved.
The Mediapad x2 was recently announced, so you may want to hold off and see what Huawei does
Sorry i couldn't be of more help.
shassouneh said:
I have seen several links that "claim" to be custom Lollipop roms for the mediapad. However, as you had already noticed its all garbage ad links.
The good news is there are guides on youTube to get past all that junk (I tried it myself and it worked). I forgot which provider I used to give you exact instructions, but try a search on YouTube
The bad news is any lollipop rom for mediapad is "at best", some custom one with questionable legitimacy. I'd say avoid it for now. Adding insult to injury the general public worldwide isn't lining up outside stores for Medipad devices, much less Huawei in general, so Huawei has very little motivation to push out lollipop on Mediapads.
Also on a final note, a lot of these links for custom roms may come preloaded with malware that will not ask you for permission but take over your machine.
I strongly urge you to stay as is. Any benefits provided by lollipop over Kitkat are not worth the risk involved.
The Mediapad x2 was recently announced, so you may want to hold off and see what Huawei does
Sorry i couldn't be of more help.
Click to expand...
Click to collapse
Thanks for the reply, I think you've confirmed what I already thought. I think Ill steer clear. I was only considering them as an option because Im not sure what else I can do with the tablet. I have bought it a couple of weeks ago for college. to test some apps Im working on.. The jelly ban 4.3 OS on it isnt too bad. I was quite happy with it up until lately. I think Ive messed up the gps on it somehow as one of my apps uses it and which I need in order for the app to work. Ive tried resetting the device, but this doesnt help.
Perhaps you could advise me further. I downloaded an official update file from huawei in the form of update.APP. I believe if I could start fresh with this,(completely refresh my system), the problem might go away. The problem is that none of the android recovery apps recognize this format( .APP). Ive tried changing the extension to .zip, but no joy.
Maybe there are some other alternatives, you mentioned kitkat,, and whats next with Mediapad x2.
Is it possible for me to take an update meant for another huawei device. Wouldn't this screw up my tablet.?
Thanks for your help. I just need something to completely refresh my system. I think if i could refresh it using the update.APP file id be sorted, but anything will do at this stage
General Tips
dermot31 said:
Thanks for the reply, I think you've confirmed what I already thought. I think Ill steer clear. I was only considering them as an option because Im not sure what else I can do with the tablet. I have bought it a couple of weeks ago for college. to test some apps Im working on.. The jelly ban 4.3 OS on it isnt too bad. I was quite happy with it up until lately. I think Ive messed up the gps on it somehow as one of my apps uses it and which I need in order for the app to work. Ive tried resetting the device, but this doesnt help.
Perhaps you could advise me further. I downloaded an official update file from huawei in the form of update.APP. I believe if I could start fresh with this,(completely refresh my system), the problem might go away. The problem is that none of the android recovery apps recognize this format( .APP). Ive tried changing the extension to .zip, but no joy.
Maybe there are some other alternatives, you mentioned kitkat,, and whats next with Mediapad x2.
Is it possible for me to take an update meant for another huawei device. Wouldn't this screw up my tablet.?
Thanks for your help. I just need something to completely refresh my system. I think if i could refresh it using the update.APP file id be sorted, but anything will do at this stage
Click to expand...
Click to collapse
I don't have any idea what an APP file is, so I cannot attest to how (if at all) it would work. Also, the device I have is the Mediapad (honor) X1, which is technically a different device than yours, but there was an OTA update to KitKat (4.4.2) which i installed.
Also, NEVER EVER EVER (DID I ALREADY SAY EVER) TAKE AN UPDATE MEANT FOR A DIFFERENT DEVICE. To give you an idea how serious I am I wouldn't even take an update designed for the 3G-only version of my mediapad (even though it would be very close, if not identical, software). This is an almost guaranteed way to (at best) render your device useless until you flash back to a working rom, or (at worst) permanently brick your device. Follow the golden rule of thumb: If in doubt, steer clear - better safe than sorry
Try the following, in order:
The steps below are very generic, and you probably already know most, if not all, of them, but it never hurts to post them here just in case some other person reads this thread and benefits from it.
1.) Backup any data you care about (this goes without saying, but just in case). Don't forget contacts, bookmarks, photos, music, etc
2.) Check for an OTA update (Settings --> About Phone or Settings --> Updater (depending on your device and OS). If there's anything, install it, reboot, etc. You may have to do this 2 or 3 times to get fully updated.
3.) Now you're ready to roll back. (Settings --> Backup & reset --> Factory data reset)
4.) The very first thing you should do at this point is to check to see if everything is working right. Don't bother setting up your phone/tablet just yet! Check to see if the GPS issue is fixed. If all is well, you can proceed to step 5
5.) Assuming you're good to go after step 4, you may want to familiarize yourself with loading up google services on your phone/tablet by glancing at
a.) This post
b.) my other thread
Don't forget that my device is different than yours, so be very cautious before you do anything!
6.) Set up your phone/tablet the way you like
7.) Optional but highly recommended: Perform a full phone/tablet backup. I have never done this myself, so I cannot walk you through this. But search here on XDA and on google for "NAND phone backup" and do some reading This will help you get back into a working state if you dink around with your phone/tablet and screw things up again.
8.) Optional but highly recommended: Search here on XDA for a "stock" ROM specific to your device. This would come in handy if all else fails and you want to force your phone/tablet back to the way it was as shipped off the factory line. Its probably a good idea to hang on to that file anyways. You never know when you want to restore everything to factory settings if you want to return the device for warranty, or if you want to gift it or sell it
Best of luck
In short, the best advice Captain Obvious can give you is READ, Re-ead, Re-re-read, and google like crazy before you do anything
Thanks for the reply, but I think I can manage a basic reset of my device