Related
Are there any custom ROMs that support device encryption? My phone needs to be encrypted to allow me to access my work email. I had recently been running SlimKat when my work email changed to require encryption. I tried to encrypt phone but it did nothing. Then I read somewhere that maybe none of the Androd 4.4.x ROMs support device encryption, so I thought I would try Android 5 since I read that Android 5 enables encryption by default. I flashed CM12, but found that encryption isn't working in it either.
I've read that you need to unroot phone in order to get encryption to work. I did try that with SlimKat with no success. I haven't tried it yet on CM12, but I'm a little nervous that it might work just well enough to leave me with an unusable phone. Especially since the change log for the unofficial CM12 ROM specifically says that encryption doesn't work. Searching for "encryption" turns up lots of posts about unsuccessful encryption resulting in bricked devices.
I have gotten used to and really like the features of KitKat and Lollipop, and I don't want to have to downgrade all the way to stock ROM with Jellybean. But I do need to get to my work email from my phone. Does anyone know of any ROMs for the Razr out there with working device encryption?
Thanks in advance.
Another question along the same lines. If I boot the stock rom from the safestrap safe slot I should be able to encrypt my phone. I read that I may have to temporarily unroot it by killing the su process via adb to get it to start encrypting, but that should be no problem. Then once it's encrypted I'd want to go back to my custom ROM. It sounds easy enough, but since device encryption is not reversible I really want to know if it's going to work before I try it. It would suck to be trapped in stock ROM. If device encryption only affects the data partition and /sdcard then recovery should be ok (maybe), but I don't know if the safestrap ROM slots will still be functional/bootable after encryption.
Anyone have any experience with device encryption? Thanks in advance for any advice or thoughts on this.
THIS IS A CLOSED CASE, GO HOME. The answer is Hairybean found in step 2 of here [ROM] [TF201] KatKiss 5.1.1 - v30 [MultiWindow] [Stable] [RRO] Read the rest of this post if you're a sadist or want to know of people in the same pain boat as you.
Part 1: My life's story. Skip to Update if you just want to hear of my current problem.
So approximately 12 hours ago, I decided, "Hey, I want to upgrade my tablet so I can download the newest and coolest apps. Since I need to upgrade to a newer OS (ICS>KK ?) I may as well go through the extra hurdle and download a nice, fast custom ROM because the stock feels like crap for the lightweight that is the TF201."
Now me, not having ever touched an android in my life before this tablet, knew this was going to be a challenge. After doing plenty of research into unlocking, flashing a custom recovery, general custom ROM flashing etiquette, and following this guide ([ROM] [MM 6.0.1] KatshMallow v29 [TF201]), I encountered my first of many hurdles. This being: I was able to boot just fine, but the Wifi was in a perpetual state of "Wifi turning on..." I put a total of a couple or so hours into researching this and easily found others having the same issue, albeit not specifically to the exact ROM and device in question. I also tinkered a bit in these hours, reflashing and rebooting and all that jazz. I eventually settled upon one of three conclusions:
The "/persist" folder had gotten deleted which contains vital wifi/network configuration data
wlan0 was borked on a hardware level and I managed to completely kill an hope of wifi on my device
There was a MAC address somewhere that I needed to manually edit (that WASN'T in the persist file)
Considering the fact that I could not see nor change directory via adb terminal (yes, with su) into a "/persist" folder, and that the hardware-broken devices other users had were most if not all cellphones, I pushed on ahead assuming #1 to be my problem. ("See" includes dropping and installing a file explorer onto the tablet as well.)
With this is mind, the next course of action was to somehow get this "/persist" folder back. It seemed like the best way to do this would be to flash a stock ROM (link in Part 2) or ask the community to give me files without even trying to solve things on my own. So in the spirit of remaining a lurker I chose the former. Flashed fine, booted fine, ran.... okay-ish (the status bar "System UI" would crash every 10 seconds, ROM was a means to an end so I didn't care), but the Wifi WORKED! However, I still didn't find a /persist folder and the tablet didn't show up in windows... "Weird but okay, whatever let's do this." Load up recovery again, wipe everything, see if I can get Katshmallow to load again...
Part 1.5: And here we are. tl;dr I'm a scrub at anything android and after 12+ hours of tom****ery, I'm in a bootloop using Katshmallow v29 (v27 made no difference). The "bootloop" is in the form of the ASUS logo appearing with the usual "UnLocked" message in the top for a minute or two, then a reset, rinse, repeat. I am able to boot into recovery and mess around in TWRP just fine, so my ignorance hasn't completely wrecked me... yet.
The information that I believe is most pertinent to my current issue is:
I unlocked using ASUS' utility for the TF700. It worked no problem and with how compatible things seem to be between the two, I don't think this is an issue (especially considering I've flashed and booted system more-or-less just fine).
The most recent ROM I flashed was this [ROM] TF201 JB JRO03C 10.4.2.15 (US) Stock Deodexed + Mods [Unlocked BL]. I figure that this did something (maybe changed the bootloader?) that Katshmallow does not agree with. If I hadn't already spent the better half of a day working on trying to get things working, maybe I would do more research and figure out the inner workings on my own, but I'm done bashing my head against a brick wall that's only pushing me further back.
I am currently running KANG TWRP 2.8.7.2 for the TF201T (yes, the device I'm specifically running). The problem existed with some TWRP 2.8.x for the TF300 as well.
The bootloader message is "Android card-hu-user bootloader <1.00e> released by "US_epad-10.4.2.15-20120917" A03 ... Oh son of a-
Part 2: So I'm a dumb*** who can't read. Okay, I need to know how to get from my current bootloader (10.4.2.15) to the one Katshmallow requires (10.6.1.27.1). In typing this, I realized that the stock ROM I used to test stuff is why I've been screwed for the past 5 hours (coupled with my ignorance of course). In my quick 2 minutes of research I found this: [GUIDE][13/11]Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked/Locked Devices. I fancy methods 2 and 3, I can do those, but that doesn't change the fact that I know NOTHING about the bootloader and what I need to update it (but apparently I know how to give myself a headache by downgrading it).
Any help will be greatly appreciated. Oh, and if you know of how to solve the Wifi issue or the likely related /persist folder issue in the wall of text above, please I beseech you to tell me.
Disclaimer: My "research" is not at all limited to the links in the post. I've spent 90% (or more) of what's now probably 13-14 hours working on getting this piece of- getting things to just go right. So... tired...
Update: The problem has changed to my second post that I will be pasting here to save people the trouble:
So the problem as it stands now. I'm cannot seem to flash a different custom recovery and whenever I try to flash a ROM I get "E:Error executing updater binary in zip" The line above it, "symlink: some symlinks failed". I give up for now... Maybe I'll try again tonight. I'm running bootloader 10.4.2.15 and TWRP KANG 2.8.7.2 (which seems to require a 14.10 bootloader). In this mess, I don't know what to fix nor how to fix it. The angles I see are fix the custom recovery or fix the error/symlink problem since the bootloader version seems to be dependent on successfully flashing ROMs.
Update2: So I managed to upgrade the bootloader by somewhat forcefully flashing Hairybean. While Katshmallow said "JB 4.2.1 BOOTLOADER VERSION 10.6.1.27.1," I glazed over this because I didn't know the importance of the bootloader and there was no other mention of the bootloader in the post (no mention of Hairybean or a download link or a "More information" link). I still have no one but myself to blame, just bitter that I have to blame myself in the first place.
For the time being, I'm following the somewhat better instruction on found in this thread([ROM] [TF201] KatKiss 5.1.1 - v30 [MultiWindow] [Stable] [RRO]) and will be picking up Katshmallow at the "wipe" step (currently waiting on the /data format). I downloaded the newest version of TWRP for TF201T and it's working just fine (note how that thread also doesn't mention anything aside from "MUST BE ON THE HAIRYBEAN BOOTLOADER ENDING IN 27.1" While that's such an obvious and blatant statement that should have inspired some research, my ignorance blinded me).
Now that I know for a fact that I am running the right TWRP and the right bootloader, I am going to pray that I can at VERY LEAST flash and boot into Katshmallow. Whether or not the Wifi problem persists will be for another thread.
IT BOOTS! YAAASSS. How do I close this embrassment of a thead?
Sorry I can't be of more help but what I CAN say is:
- read instructions thoroughly with any release. Sometimes a modified TWRP or other file is posted that you must use even if you have a newer version. You might also have to bounce around to other posts along the way to install/update all of the necessary files.
- keep a written log of changes you've made with notes on reversing them. Changing the bootloader means you can't go back unless you revert it back first. I can back track everything I've done based on my own notes, much easier to understand than someone else's notes or directions.
Good luck and be patient. Don't make more than one change at a time and get it working or revert back before trying something totally different.
Sent from my LG-H811 using Tapatalk
HorthLithperer said:
Sorry I can't be of more help but what I CAN say is:
- read instructions thoroughly with any release. Sometimes a modified TWRP or other file is posted that you must use even if you have a newer version. You might also have to bounce around to other posts along the way to install/update all of the necessary files.
- keep a written log of changes you've made with notes on reversing them. Changing the bootloader means you can't go back unless you revert it back first. I can back track everything I've done based on my own notes, much easier to understand than someone else's notes or directions.
Good luck and be patient. Don't make more than one change at a time and get it working or revert back before trying something totally different.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Thank you for replying nonetheless. I'll keep the note thing in mind. Regarding the bouncing around to get the files necessary, I've done plenty of that. When installing a new ROM, I made sure to follow the links as they were given and did further research where things weren't clear. My current problem stems from that fact that, 1: I have no point in which to restore back to due to my aforementioned ignorance and oversight of basic Android terminology; and 2: The next step is to revert the bootloader, that of which I have no clue how to do or where to start since my preliminary google search. Even if I had been taking notes, no one mentions how to do this without a backup. And so I'm on a hunt to find this information and for posterity, I'll post my quest here:
Google search: "tf201 bootloader version"
Upgrading from ICS Bootloader > [ROM] [TF201] [JB Bootloader] CyanogenMod 10 Unofficial - JZO54K - Oct 30 2012 - I learned that apparently certain ROMs can overwrite the bootloader, extrapolated from:
4) Needs the new Jelly Bean 10.4.2.15 bootloader [IMPORTANT: Flashing over an incorrect bootloader can permanently brick you device. The Oct 13 2012 build includes the bootloader upgrade and can be flashed over any ROM/bootloader]
Google search: " update tf201 bootloader"
[GUIDE] How to manually update/restore firmware (TF101, TF201, TF300, TF700, TF701) - Post #2 sent me to ASUS official support wherein I downloaded "V10.4.2.18." This is a test in hopes that I can get a ROM running and see if the bootloader changes. I'm not able to use the methods in that thread as I do not have a system nor a microSD, as such I'll flash it the way I have been. Same custom recovery as before. Run the usual wipe (Dalvik, System, Cache, Data, Internal). Drop ASUS ROM onto pad's internal. Attempt flash... Error: "E:Error executing updater binary in zip"
More research, now trying to find out what this error is. Tried this and read a couple pages from here. Settled on reflashing TWRP. While looking up the command again, I came upon here, then went to the first post of that thread here, then from the TWRP link in that post to here (yes, I see the big TF700T at the top, I also see the big MUST BE ON A BOOTLOADER ENDING IN 14.10).
Okay so, I have 10.4.2.15 and am going to have to jump through several hoops to get to the mysterious 10.6.1.27.1. Annnnd It seems as though I have a custom flash that doesn't support my bootloader (which I feel should've been an issue up until now?) I just want to boot into A ROM, so either I find a ROM that supports the bootloader and probably flash a recovery that does as well...
Googled: "10.4.2.15 tf201" Came upon this, tried to flash twrp2.3.1.0 for the tf201 (downloaded straight from their website)... Still in 2.8.7.2 ... Okay, what? FINE! Screw it, redownload the stock ROM that got me into this mess (here) and see if I can even flash that. Wipe all the usual but internal storage because I'm lazy and afaik it doesn't need to be wiped anyway. Error: "E:Error executing updater binary in zip" The line above it, "symlink: some symlinks failed". Popped into here, unmounted the things, reformatted /data to f2fs (this may just be a Marshmallow thing though... it was ext_4 before I reformatted) Same error... Kill me.
So the problem as it stands now. I'm cannot seem to flash a different custom recovery and whenever I try to flash a ROM I get "E:Error executing updater binary in zip" The line above it, "symlink: some symlinks failed". I give up for now... Maybe I'll try again tonight. I'm running bootloader 10.4.2.15 and TWRP KANG 2.8.7.2 (which seems to require a 14.10 bootloader). In this mess, I don't know what to fix nor how to fix it. The angles I see are fix the custom recovery or fix the error/symlink problem since the bootloader version seems to be dependent on successfully flashing ROMs.
I'm sure there's someone out that that can point to me the correct tree in this forest using their superior knowledge of the subject. Having grown up with computers, even a new error message is something to work with. But when you can't even get results (success nor detailed failure), then it becomes downright no fun.
Hi, I am new here, but have recently gotten into rooting phones etc, but my knowledge base is still Novice at best. I have an AT&T Optimus G that was rooted and had CWM, Free G and Kitkat. Long story short, a co-worker who claimed to know what they were doing has reset my phone, wiped my external sd card and totally factory reset my phone. When I turn it on now ClockworkMod Recovery comes on, but all of my back ups etc have been wiped. I am assuming that it is now just a machine with no info on it. What do I do now? I'm sure that the answer to this will be very involved so if anyone could possibly suggest a thread to read or somewhere to start I would greatly appreciate it. I'm sorry for the inconvenience guys...
The google account that this was linked to is my current one so no issues with reset protection once it gets running or what not. Any info I can provide on my end if need be feel free to let me know. I know one of the specifics to the device was: geefhd???
Here is the current update: Android 4.4.2 KitKat
The details
Release date: September 29, 2015
Android version: 4.4.2
Baseband version: APQ8064/MDM9x15M
Kernel version: 3.4.0
Build number: KOT49I.E98020i
File size: 9.47MB
Software version: E98020i
EMT803 said:
Hi, I am new here, but have recently gotten into rooting phones etc, but my knowledge base is still Novice at best. I have an AT&T Optimus G that was rooted and had CWM, Free G and Kitkat. Long story short, a co-worker who claimed to know what they were doing has reset my phone, wiped my external sd card and totally factory reset my phone. When I turn it on now ClockworkMod Recovery comes on, but all of my back ups etc have been wiped. I am assuming that it is now just a machine with no info on it. What do I do now? I'm sure that the answer to this will be very involved so if anyone could possibly suggest a thread to read or somewhere to start I would greatly appreciate it. I'm sorry for the inconvenience guys...
The google account that this was linked to is my current one so no issues with reset protection once it gets running or what not. Any info I can provide on my end if need be feel free to let me know. I know one of the specifics to the device was: geefhd???
Click to expand...
Click to collapse
Since your phone has been wiped, you are going to have to re-install your ROM either via LGNPST, which will return your phone to stock, or you will need to install your favorite custom ROM via adb sideload.
If going back to stock via LGNPST refer to FAQ Number 3 here http://forum.xda-developers.com/showthread.php?t=2006946
If installing custom rom via ADB Sideload refer here http://www.droidviews.com/sideload-roms-mods-using-adb-sideload/
Kilogrm said:
Since your phone has been wiped, you are going to have to re-install your ROM either via LGNPST, which will return your phone to stock, or you will need to install your favorite custom ROM via adb sideload.
If going back to stock via LGNPST refer to FAQ Number 3 here http://forum.xda-developers.com/showthread.php?t=2006946
If installing custom rom via ADB Sideload refer here http://www.droidviews.com/sideload-roms-mods-using-adb-sideload/
Click to expand...
Click to collapse
I was able to fix the problem late the night of this post, but I REALLY DO APPRECIATE the advice.
I had to reinstall the firmware ultimately. I did learn the commands and process for the sideload, so that was cool, and the program zips did show as downloading from 0-100% and attempted to install, but the 4g part of "this device is geef4g" was an error that I was unable to surmount. I attempted to install the madmack version of TWRP to no avail. I am lucky I figured out the tool ONLY by accidentally stumbling over the advice referencing turning back the clock on the pc.
Moving Forward...
Ok... Had to at least stop in and say thank you for the response and post the conclusion to the handful of people that stopped and looked at the thread and at the least not be one of the members that pops on to fix their device and lurks around until they need help to post again. I wouldn't be back to stock with my Optimus if others did that. I do apologize that I was able to find onsite and unable to do it at the time of the threads origin. I wont re-post links, FlashTool the fix was figuring out the right order to go in with the drivers and eventually flashing the stock AT&T firmware with the LG FlashTool. I kept on getting an error when placing the dll file and the tot in to the Tool and it was total mental error on my part when "organizing" everything beforehand. It did require me to wipe my pc back down to Windows 8.1 simply because this is all new to me and I had files EVERYWHERE from rooting every thing I can get my hands on recently. I'm having fun, but this Optimus is my heart for some reason. Originally I had her rooted with Towelroot (I believe), it could of been the LG one click flash thing that I grabbed from here, and I remember Freegee and KitKat recovery being part of the process, but I attempted to install TWRP (personal preference for me from messing with a Kindle Fire for weeks installing CM) but during reboot always went back to CWM 6.0.2.1 (or similiar). Ultimately CM was the goal on this device but was never possible, for me at least, due to my device being "geef4g" yada yada. I think I have read the fix for this in another post, so I will re study up on all that again if need by, but I wanted to pose this question simply because the "Mystique" of successfully installing CM has passed, and while I love the interface and style of that ROM, I kinda liked AndroidArea51 Rom and another ROM whose name escapes me at the moment that I put on some OLD LG phones that I practiced on in the beginning. So this is my goal. I would love it if one or two of you guys would take the time to look at what I want to accomplish and point me in the right direction as far as the procedure and order I should install these modifications to this device and if you have preferences I would love to hear them. I will look up the threads on how to do everything, so I'm not asking for an easy way out of hitting the search box, but I am WAY behind you guys as far as skill set and knowledge base is concerned and trial and error is not the method I wanted to use on this particular machine. If I need to begin a new thread or if a MOD wants/requires me to rename this thread or move it I understand. Stand by for what my goal is ultimately......
OBJECTIVE
AT&T Optimus Pro G (will HOPEFULLY be accepted by StraightTalk and used on their network or whatnot)
I ran the IMEI through their BYOD tool and it was accepted initially a week or so ago while "rooted", so I am assuming that since it is mine from another network they wont sweat me. HOWEVER, if they are going to send any code or require me to allow them modifications during the activation process that is going to in anyway alter my device down to the castrated ST standard they sell, I will have to weigh finances and options again. I realize that Tethering will be frowned upon, traceable, and grounds for termination in either case, but the subject of Mobile Hotspots is what brought me to you guys here in the first place. It irks me.
In my original "build" of this phone I attempted to dabble in "Over-Clocking" with Kernel Booster and Kernel Auditor. I didn't have a f******* clue what any of that $hiT meant. If the app's pretty much optimized it I did so for SPEED rather than battery. I don't know why, I want this thing to FLY in a noticeable fashion for performance and so that I can whip it out and show my family and friends just what the hell it is that I am accomplishing.
1. Optimize it for speed, but I would like the eventual permanent ROM to be stable PERIOD. Whether I customize the Kernel and then place the ROM, or build the ROM and then mess with the Kernel is a hurdle that I don't understand how to approach really, so when you guys talk about it I just think it sounds cool. I am assuming that "Xposed" is something I should maybe begin studying? Build props through ES File Explorer has peaked my interest as well. Long story short, if CM is what you guys suggest I install, I dont want to Optimize the hell out of the stock only to have all of it be replaced when the custom ROM is flashed. I hope that makes sense.
2. I want to optimize the range on my WIFI and every other manner of device communication without losing security. I have numerous friends that are very generous with their personal accounts that allow me to randomly log in to strangers spots (EX. Xfinity accouts), in order to truly connect to it, I have to sit outside in the yard like a weirdo at 3am with my phone in my backyard, much to the disgust of every dog in the neighborhood. I dont want to be that guy. Honestly, I am really curious in learning how to access the internet and/or any other data networks that are out there with out using these major carriers at all. I feel like there is a lot more out there than the average person is aware of. Maybe they are super low key because they are owned by the upper rich 1% or the military etc etc, but if other networks exist that facilitate the same communications that us peasants pay $100/month to access I want in on it.
3. Optimize the picture, color and clarity of the screen for any and everything being shown on it, optimize the Audio with a good "Music Player"(currently what I use) which I generally heard through head phones and when in the car pushed to that system via FM signal. I currently have over 1000 tracks, discovering a cost efficient way of adding to that Library would be wonderful (ie: spend $0), but I have been out of the music file sharing game for a while so I dont know if this is realistic. Optimizing my camera to take the best shots possible on this phone. I generally shoot nature shots, sunsets, sunrises.... unsuspecting women in doggy, the usual... I will not be loading movies and super large files. I am a NAZI with my storage. If I could expand upon the internal or external factory specs that would be great. In other words, real life applications... I haven't been a gamer for decades so nothing crazy, but this device's beautiful picture is what I fell in love with.
4. A kick ass ROM UI that is eye catching and user friendly... sorry so long winded. Got to go run calls at work now....
It seems I know just enough to get myself into trouble and not enough to get myself out of it.
Firstly, my Kindle Fire is running just fine. It's not bricked. I've got TWRP as a recovery partition and I've installed LineageOS 14.1-20190920-UNOFFICIAL-thor.
What I didn't do was back things up before I started.
What I want to do is restore my device back to it's factory default. No TWRP and back to the standard Amazon Fire OS version 4.5.5.3.
I've downloaded the current official firmware from the Amazon site.
But try as I might, I can't figure out how to reset it.
Using TWRP's sideload generates an error 7 ("This package is for 'thor' products; this is a 'lineage-thor'".) -- which I assume means the official archive doesn't think my HDX is a HDX because Lineage is loaded. (and obviously I'm not sure how to get rid of LineageOS without risking other issues).
Using "fastboot update {filename}.bin" complains the archive does not contain an 'android-info.txt" file... which it doesn't.
The Amazon recovery option to sideload via ADB isn't there - because TWRP replaced the recovery process.
Before yesterday, I hadn't tried anything like this. So assume no prior knowledge on my part.
Yes, I know I could leave it like this... that isn't my question. My question is how do I return it to stock... Not because I need to, but because I want to.
79flavors said:
It seems I know just enough to get myself into trouble and not enough to get myself out of it.
Firstly, my Kindle Fire is running just fine. It's not bricked. I've got TWRP as a recovery partition and I've installed LineageOS 14.1-20190920-UNOFFICIAL-thor.
What I didn't do was back things up before I started.
What I want to do is restore my device back to it's factory default. No TWRP and back to the standard Amazon Fire OS version 4.5.5.3.
I've downloaded the current official firmware from the Amazon site.
But try as I might, I can't figure out how to reset it.
Using TWRP's sideload generates an error 7 ("This package is for 'thor' products; this is a 'lineage-thor'".) -- which I assume means the official archive doesn't think my HDX is a HDX because Lineage is loaded. (and obviously I'm not sure how to get rid of LineageOS without risking other issues).
Using "fastboot update {filename}.bin" complains the archive does not contain an 'android-info.txt" file... which it doesn't.
The Amazon recovery option to sideload via ADB isn't there - because TWRP replaced the recovery process.
Before yesterday, I hadn't tried anything like this. So assume no prior knowledge on my part.
Yes, I know I could leave it like this... that isn't my question. My question is how do I return it to stock... Not because I need to, but because I want to.
Click to expand...
Click to collapse
There is not an easy path back to pure stock on 3rd gen HDX devices once you have traversed the path taken to get where you are. Yes, it can be done but the steps are numerous, tedious and require you roll your own components. I have yet to see someone get through the entire process.
DB126 said:
There is not an easy path back to pure stock on 3rd gen HDX devices once you have traversed the path taken to get where you are. Yes, it can be done but the steps are numerous, tedious and require you roll your own components. I have yet to see someone get through the entire process.
Click to expand...
Click to collapse
In my mind, there would be four steps (yes, yes, naive I know)...
Use TWRP's "wipe" to fully remove LineageOS from the system partition.
Use TWRP's ADB sideload to restore the stock OS to version 4.5.5.3.
Magicially find the original versions of the aboot and recovery partitions somewhere on the net.
Reverse the replacement of twrp_cubed/aboot_vuln with there originals.
Except... having realized the extent of my ignorance - I'm looking for a little reassurance I'm on the right track.
Specifically...
I'm terrified that I end up wiping out the system partition with ill advised wipe options leads to my device being unusable.
I'm unsure that removing LineageOS WILL actually permit the sideload of the base OS.
I've no clue if the original recovery/aboot partitions for my device are anywhere I might find them.
I'm not tied to any given solution. As I've stated in my original post, the device is working.
Realistically, I'd settle for the Amazon OS being back on the device, still using TWRP.
It's less about restoring the device to stock and more about me learning what is and isn't possible and what my various options are.
(Primarily LineageOS is something I stumbled into. It works, but it wasn't an informed decision - just a result of a series of seemingly random choices).
So perhaps I could limit my changes for the moment and change my original question...
Could someone suggest the steps I would need to take to remove LineageOS and replace it with the stock Amazon OS...
Thanks in advance.
79flavors said:
In my mind, there would be four steps (yes, yes, naive I know)...
Use TWRP's "wipe" to fully remove LineageOS from the system partition.
Use TWRP's ADB sideload to restore the stock OS to version 4.5.5.3.
Magicially find the original versions of the aboot and recovery partitions somewhere on the net.
Reverse the replacement of twrp_cubed/aboot_vuln with there originals.
Except... having realized the extent of my ignorance - I'm looking for a little reassurance I'm on the right track.
Specifically...
I'm terrified that I end up wiping out the system partition with ill advised wipe options leads to my device being unusable.
I'm unsure that removing LineageOS WILL actually permit the sideload of the base OS.
I've no clue if the original recovery/aboot partitions for my device are anywhere I might find them.
I'm not tied to any given solution. As I've stated in my original post, the device is working.
Realistically, I'd settle for the Amazon OS being back on the device, still using TWRP.
It's less about restoring the device to stock and more about me learning what is and isn't possible and what my various options are.
(Primarily LineageOS is something I stumbled into. It works, but it wasn't an informed decision - just a result of a series of seemingly random choices).
So perhaps I could limit my changes for the moment and change my original question...
Could someone suggest the steps I would need to take to remove LineageOS and replace it with the stock Amazon OS...
Thanks in advance.
Click to expand...
Click to collapse
Sure - 4 major steps with multiple substeps; slice and dice as you wish.
Use images from one of the following threads (your choice; both will work) to flash FireOS v4 to the system partition. No benefit in doing so (still munged builds) other than to satisfying a tinker twinge. Those threads will also provide clues on how to roll your own flashable stock recovery which will bring you back close to full OEM. Pushing a newer (non-vulnerable) aboot involves more risk with no obvious benefit. Good luck.
https://forum.xda-developers.com/ki.../hdx-stock-images-pre-rooted-updates-t2911954
https://forum.xda-developers.com/kindle-fire-hdx/development/twrp-flashable-stock-images-t3194914
Am I right in assuming SafeStrap is just an alternative to TWRP?
And yeah. I take your point about not risking swapping the aboot_vuln for a more 'legit' aboot.
The threads are great, but seem to rely on a presumption of a certain level of knowledge I just don't have yet (or may never have).
Now I just need to figure out which partitions/areas it's safe/safer to wipe with TWRP's wipe.
(Dalvik, Data, Internal Storage, Cache, System)
I'm tempted to do all 5. But not knowing the consequences makes it feel a little risky. More reading required I guess.
79flavors said:
Am I right in assuming SafeStrap is just an alternative to TWRP?
And yeah. I take your point about not risking swapping the aboot_vuln for a more 'legit' aboot.
The threads are great, but seem to rely on a presumption of a certain level of knowledge I just don't have yet (or may never have).
Now I just need to figure out which partitions/areas it's safe/safer to wipe with TWRP's wipe.
(Dalvik, Data, Internal Storage, Cache, System)
I'm tempted to do all 5. But not knowing the consequences makes it feel a little risky. More reading required I guess.
Click to expand...
Click to collapse
Everything but internal storage. You could get by with less but there's really no point since you are not trying to preserve user apps/data.
Hi Interweb!
I was wondering just how many people were still "in the know" on the topic of rooting, unlocking bootloader and general Android development for the Tesco hudl2 [HTFA4B] tablet. Obviously with Tesco's little trick of shutting down the servers, two thirds of us were left with Kitkat, and having had enough of it, I decided to root. Everything went fine. I booted back into Android KitKat (stock) and then installed Xposed Framework. Presumably the installation failed, as upon rebooting, the tablet booted straight into stock recovery. I have been seeing this for two months now, having removed the battery several times, refitting it and trying to reinstall android with the ROM form this link:
hudl2_ota_rel.android-build.20150803.092218_to_rel.android-build.20150917.142239.zip | GEM-FLASH Firmware
firmware.gem-flash.com
Either way, I am now faced with a soft brick. Does anyone know how to fix? The exact text displayed in Stock Recovery is down below.
To be clear, I occasionally DO see the "powered by android" screen before booting into recovery, but not every time.
A possible solution would be if there is a fastboot mode I can access, I may can use Odin and flash a Custom ROM onto the tab. Or, alternatively, if anyone has, or knows someone who may have Tesco's key signature, that too would be useful in building a ROM.
I've had this tablet since I was 7 years old, and it's been part of my life for many years now. If anyone can help please do
Many Thanks.
[TAGGING SOME PEOPLE WHO MAY BE ABLE TO HELP]
@Rickav
@droident
People not on XDA who may can help:
Kirwan Lyster - Head of Facebook's Android department and former head of Tesco Connected Devices (hudl) software team. [email protected]
The Guardian Consumer Champions
BBC Watchdog
Martin Lewis - Money Saving Expert.
Android system recovery <3e>
K0T49H.rel.android-build.20151102.170607 release-keys
Volume up/down to move highlight:
power button to select.
reboot system now
wipe data/factory reset
wipe cache partition
apply update from ADB
apply update from external storage
apply update from cache
[ANDROID WITH OPEN BELLY]
No Command.
Click to expand...
Click to collapse
Hey, just got pinged by XDA after a long time. It's all so sleek-looking now.
I'll cut to the chase—Unfortunately, I've got nothing to help with here. I'm a fan of the Hudl2 as well and still have it around as a backup ebook reader as the screen works reliably. It's running walking stock Lollipop and it occasionally throws up Play Services errors (which appears to be resolvable).
Following the dead download link on the MoDaCo forum post, I searched for stock ROMs and landed on the same Gem Flash site that you linked. Specifically, I found 3 results linked to the Hudl2. For the sake of future visitors, I've downloaded and attached all 3 of them to this post (in case it's locked, the password is "www.gem-flash.com").
I wouldn't get my hopes up, but it might be worth giving each a go. Honestly, I wouldn't even know where to begin with flashing but I think you're way ahead of me here.
Genuinely wishing you the best of luck, and I really hope it works out.
Rickav said:
Hey, just got pinged by XDA after a long time. It's all so sleek-looking now.
I'll cut to the chase—Unfortunately, I've got nothing to help with here. I'm a fan of the Hudl2 as well and still have it around as a backup ebook reader as the screen works reliably. It's running walking stock Lollipop and it occasionally throws up Play Services errors (which appears to be resolvable).
Following the dead download link on the MoDaCo forum post, I searched for stock ROMs and landed on the same Gem Flash site that you linked. Specifically, I found 3 results linked to the Hudl2. For the sake of future visitors, I've downloaded and attached all 3 of them to this post (in case it's locked, the password is "www.gem-flash.com").
I wouldn't get my hopes up, but it might be worth giving each a go. Honestly, I wouldn't even know where to begin with flashing but I think you're way ahead of me here.
Genuinely wishing you the best of luck, and I really hope it works out.
Click to expand...
Click to collapse
Thanks @Rickav . Presumably you saw my DM.
All three come out with:
Code:
Finding update package...
Opening update package...
Verifying update package...
E:end of footer from /tmp/update.zip not 0xFFF (File exists)
E:signature verification failed
Installation aborted
once adb sideloaded in stock recovery (all I have access to).
Is there any chance of you making a nandroid backup zip using the CWM fastboot custom recovery in "hudl2 root stuff.zip" on MoDaCo? I know it's asking a lot. @paulobrien might send me a system image and couple of OTA zips and other assorteds for a start which may help. Before I attempted Xposed I was trying to get Lollipop but the OTA server has been decommissioned (confirmed by Kirwan Lyster, head of hudl2 software), so if I can do that by other means that'd be great. Fist priority though: get it running. You can see by the video what is happening.
Many thanks,
Cessna
If can't do this, may need to try to unlock bootloader. Any ideas, also useful.
@Rickav I really appreciate your assistance, but going by this link:
New update Sept 15
www.modaco.com
It looks like my tablet is dead. What do you think of this?
Hi,
In case anyone is looking for clear instructions on how to overcome the problem after a factory reset of the Tesco Hudl 1 & 2 you will find them here (works for Hudl 2 as well). Use a date between 27 June 2019 and 26 June 2020 :
HUDL bricked after factory reset and how to fix it - Hey Munky!
I did a factory reset on my HUDL and bricked it. Here's a quick step-by-step guide on how to unbrick it after a factory reset.
www.heymunky.co.uk
Or the same with pictures but remember to use a date between 27 June 2019 and 26 June 2020 :
Rob's stuff - Hudl - Fix
Update 23 May 2023: This mechanism for recovery of a factory reset Hudl 1 no longer works. Due to the Tesco server at https://device.tesco.mobile.com/ no longer responding correctly to requests this technique no longer works and will fail after Step 18. As far as I know my Custom ROM is now the
rob.themayfamily.me.uk
(If this date solution ever fails then another option is to create a new user in the settings menu and reboot into it.)
Post if it works for you
I am going to try and update my hudl 2 to lollipop android 5. ADB sideload fails so i need to update from sdcard or from cache folder, just a case of where the cache folders are and how to add to them.
Hi @ushilives
Whatever you do, please don't do that! Doing so causes your device to become unbootable, and unrecoverable!!!
It will end up like mine did, and, trust me, you ain't getting it back, KitKat, Lollipop, or else.
Sorry to let you down, I just don't want to see another Hudl killed.
Regards,
Cessna
Did yours brick before or after you installed xposed?
CessnaBroon said:
Hi @ushilives
Whatever you do, please don't do that! Doing so causes your device to become unbootable, and unrecoverable!!!
It will end up like mine did, and, trust me, you ain't getting it back, KitKat, Lollipop, or else.
Sorry to let you down, I just don't want to see another Hudl killed.
Regards,
Cessna
Click to expand...
Click to collapse
Did yours brick before or after you installed xposed?
ushilives said:
Did yours brick before or after you installed xposed?
Click to expand...
Click to collapse
When I rebooted after installing xposed. I also know people who bricked it from sideloading other builds in ADB, due to Tesco's locked bootloader having extra security measures.
CessnaBroon said:
When I rebooted after installing xposed. I also know people who bricked it from sideloading other builds in ADB, due to Tesco's locked bootloader having extra security measures.
Click to expand...
Click to collapse
Ah OK thanks. I'll have a read more into it Rather than using recovery
Please do. Just check for me please, does it still boot? If yes, what have you attempted so far? Thanks