Related
Hey all,
I'm getting my G Tablet tomorrow and I'd just like to get some things clarified.
I know, the first thing some will say is USE SEARCH! Well, I did - and that's actually why I just want to get some things straight before I go down the path of modifying the device software. See, reading it all has managed to confuse me more than help me get a definitive instruction set for forging ahead.
I'm seeing the update "****s on CWM" according to a user...and then a 'fix' for that. Than I see that Gapps causes FCs for some, while it works for others. So...yeah, a little back and forth on what to do and who's instructions to follow.
Alright, so first thing's first....Should I flash the Clockwork Mod that I'm seeing available - 0.8? or is there something else I should consider or that I've missed? or maybe wait for a newer version? Should I even flash CWM if I get the newest (and I WILL be getting the newest) S/W version? Are there any downsides at all to flashing CWM on there in terms of messing with OTA updates, etc?
I read this:
"All the ROMS use a standard firmware updater that can be used by non-technical users. Here is an explanation on how it works:...."
Sooo, does that mean I can live without CWM? If an update doesn't work for some reason, will I be able to fix it or overwrite it somehow if I can't get into the tablet at all from the tablet itself? I read something about going into APX mode and putting things on through Windows, is this an infallible method?
Second of all, I read the FAQ thoroughly (I think and hope) but I'm still not 100% on what Gapps to DL or how to put a working Android Market on there especially with this new S/W update. I've seen how to 'fix' the Market to see missing apps, but not how to actually install it on the G Tablet. I may have missed that post somewhere on here.
I'm also unclear if I should get Gapps or not at all, as I've read that some have FCs on there while others do not - so what's the general consensus in light of this update that was just released as of Dec. 21, 2010?
Ultimately, here is what I'd like from my GTab:
I'd like to run the new official Tapn'Tap released recently first and foremost.
I'd like to have the official/unofficial (w/e) Google Market.
I'd like to run Google Apps (Gtalk, Gmail, etc.).
IF I don't like Tapn'Tap, and this is a worse case scenario situation, as in if I HATE TnT - I'd like to have the option to slap something else on there and I'd like to make sure I don't brick my Tablet. Whether that means storing an original official TnT ROM or whatever.
Point me in the right direction please, especially considering things may have changed as of the new S/W update.
Thanks much and sorry for all the questions. I assure you I used search and I attempted to put it together on my own. It's been a long time since I've modded (G1 was the last time) and I don't do it often. Also, apologies if I posted this in the wrong section....I considered posting it in Dev. section but this one seemed better suited.
Thanks again, XDA rocks.
Neoprimal said:
Hey all,
I'm getting my G Tablet tomorrow and I'd just like to get some things clarified.
I know, the first thing some will say is USE SEARCH! Well, I did - and that's actually why I just want to get some things straight before I go down the path of modifying the device software. See, reading it all has managed to confuse me more than help me get a definitive instruction set for forging ahead.
I'm seeing the update "****s on CWM" according to a user...and then a 'fix' for that. Than I see that Gapps causes FCs for some, while it works for others. So...yeah, a little back and forth on what to do and who's instructions to follow.
Alright, so first thing's first....Should I flash the Clockwork Mod that I'm seeing available - 0.8? or is there something else I should consider or that I've missed? or maybe wait for a newer version? Should I even flash CWM if I get the newest (and I WILL be getting the newest) S/W version? Are there any downsides at all to flashing CWM on there in terms of messing with OTA updates, etc?
I read this:
"All the ROMS use a standard firmware updater that can be used by non-technical users. Here is an explanation on how it works:...."
Sooo, does that mean I can live without CWM? If an update doesn't work for some reason, will I be able to fix it or overwrite it somehow if I can't get into the tablet at all from the tablet itself? I read something about going into APX mode and putting things on through Windows, is this an infallible method?
Second of all, I read the FAQ thoroughly (I think and hope) but I'm still not 100% on what Gapps to DL or how to put a working Android Market on there especially with this new S/W update. I've seen how to 'fix' the Market to see missing apps, but not how to actually install it on the G Tablet. I may have missed that post somewhere on here.
I'm also unclear if I should get Gapps or not at all, as I've read that some have FCs on there while others do not - so what's the general consensus in light of this update that was just released as of Dec. 21, 2010?
Ultimately, here is what I'd like from my GTab:
I'd like to run the new official Tapn'Tap released recently first and foremost.
I'd like to have the official/unofficial (w/e) Google Market.
I'd like to run Google Apps (Gtalk, Gmail, etc.).
IF I don't like Tapn'Tap, and this is a worse case scenario situation, as in if I HATE TnT - I'd like to have the option to slap something else on there and I'd like to make sure I don't brick my Tablet. Whether that means storing an original official TnT ROM or whatever.
Point me in the right direction please, especially considering things may have changed as of the new S/W update.
Thanks much and sorry for all the questions. I assure you I used search and I attempted to put it together on my own. It's been a long time since I've modded (G1 was the last time) and I don't do it often. Also, apologies if I posted this in the wrong section....I considered posting it in Dev. section but this one seemed better suited.
Thanks again, XDA rocks.
Click to expand...
Click to collapse
I don't know how much direction pointing I can do but here goes..
Clockwork mod in my opinion is a necessity. Version 0.8 is the best one for most people because of how it deals with the memory locations. Yes, you can do things without it. The update process is as simple as putting an update.zip file, and a recovery folder with a command file in it on an sdcard and holding the vol + button while hitting power. It is easy. Clockwork has a lot of little features though that make life easier. You can make a complete system backup with it. You can install updates, and new firmware with it. You can completely lock up your tablet and using clockwork and your backup be back in business in about 3-4 minutes. You can load new roms and if you hate them you can go back to your old working stuff in minutes. Yes, there are ways to make one of these tablets work again when they get stuck. I don't think anyone has actually bricked one. Some may think they have, but I doubt it.
Unless you are dead set on wanting the stock TnT interface the easiest way to get what you want is to load one of the roms. Yes, there are ways to get most of it without loading a new rom. Most everyone that has gone the I have to stay stock but want all the mods has eventually just loaded a rom. TnT3.0 is based on the latest stock stuff. It has the market, flash, etc. already in it. VegaN is what I use mostly but they are both stable and fast.
Before you flash something brand new that just came out I would read about it and see what others have to say about issues. It usually only takes about 30 minutes until you can tell if it is going to be good or not.
All of the roms for this tablet have there own little quirks. The stock has gotten better with each update but it still is not as good as the ones I named.
Finally.. This tablet is very easy to play with. It is pretty much unbrickable. Anything you can possibly break one of us has probably already broken before and fixed. There are some people that seem to have problems doing every little thing. Most don't. So I wouldn't let any of it scare you off because none of it is that hard.
With a little bit of searching almost everything you may want it to do can be done. I really love mine, and when I got it almost 2 months ago I hated it...
"Finally.. This tablet is very easy to play with. It is pretty much unbrickable. Anything you can possibly break one of us has probably already broken before and fixed. There are some people that seem to have problems doing every little thing. Most don't. So I wouldn't let any of it scare you off because none of it is that hard."
"Sigh" of relief. Then I'm not too worried. As I said I've dabbled in modifying my G1 and it is mostly cake. But I've just been seeing conflicting posts on whether cwm works with the newest official tnt release or not so I wasn't sure what to do.
Thanks for your advice. And when I said pointers, I meant like this as well as pointing me to any posts I may have missed on how to do whatever. Though I THINK I found most of them.
Neoprimal said:
"Finally.. This tablet is very easy to play with. It is pretty much unbrickable. Anything you can possibly break one of us has probably already broken before and fixed. There are some people that seem to have problems doing every little thing. Most don't. So I wouldn't let any of it scare you off because none of it is that hard."
"Sigh" of relief. Then I'm not too worried. As I said I've dabbled in modifying my G1 and it is mostly cake. But I've just been seeing conflicting posts on whether cwm works with the newest official tnt release or not so I wasn't sure what to do.
Thanks for your advice. And when I said pointers, I meant like this as well as pointing me to any posts I may have missed on how to do whatever. Though I THINK I found most of them.
Click to expand...
Click to collapse
The new release overwrites clockwork. But it is not hard to put back. Always a good idea to copy the clockwork backups folder to your pc, or somewhere they won't be lost. The custom roms typically leave the recovery image alone and can be installed with or without clockwork by either extracting the zip contents for stock recovery, or installing it as is in clockwork.
Sprdtyf350 said:
Finally.. This tablet is very easy to play with. It is pretty much unbrickable.
Click to expand...
Click to collapse
I can vouch for that. Erased system, boot, data and cache in preparation for a new ROM. Accidentally rebooted and couldn't get into recovery. Booted it into APX mode, flashed stock and was on my way.
I would just run ZRoot, then upload the TnTLite 3.0 recovery and update.zip and then do the recovery mode process. You should have a microsd handy just in case it doesn't work, but so far I haven't needed that.
This tablet is much easier to work with and very forgiving since VS never took the time to lock down the bootloader etc like Motorola did with my Droid X. You really shouldn't fear changing files out etc, provided you're getting a ROM from one of the people providing them here. If you can press and hold two buttons at once, you can make your gTab an awesome little tablet. It benchmarks about 1000 points higher than my Droid X on quadrant. Can't wait to see what these guys can do with Gingerbread.
Sprdtyf350 said:
The new release overwrites clockwork. But it is not hard to put back. Always a good idea to copy the clockwork backups folder to your pc, or somewhere they won't be lost. The custom roms typically leave the recovery image alone and can be installed with or without clockwork by either extracting the zip contents for stock recovery, or installing it as is in clockwork.
Click to expand...
Click to collapse
It is also not hard to alter the update so that it does not overwrite clockwork.
Open update.zip
Find updater-script, Open in notepad++
Remove the line that references recovery.img
Flash update
hogasswild said:
I would just run ZRoot, then upload the TnTLite 3.0 recovery and update.zip and then do the recovery mode process. You should have a microsd handy just in case it doesn't work, but so far I haven't needed that.
This tablet is much easier to work with and very forgiving since VS never took the time to lock down the bootloader etc like Motorola did with my Droid X. You really shouldn't fear changing files out etc, provided you're getting a ROM from one of the people providing them here. If you can press and hold two buttons at once, you can make your gTab an awesome little tablet. It benchmarks about 1000 points higher than my Droid X on quadrant. Can't wait to see what these guys can do with Gingerbread.
Click to expand...
Click to collapse
with the new update however does the z4root still work? i heard it may not anymore. just curious also since im hopefully getting mine on sat for xmas
rothnic said:
It is also not hard to alter the update so that it does not overwrite clockwork.
Open update.zip
Find updater-script, Open in notepad++
Remove the line that references recovery.img
Flash update
Click to expand...
Click to collapse
Thanks for the info Rothnic! I had already flashed it before I figured out it removed Clockwork. Learning new stuff every day is good... Thanks..
dragonfly1113 said:
with the new update however does the z4root still work? i heard it may not anymore. just curious also since im hopefully getting mine on sat for xmas
Click to expand...
Click to collapse
The very first time I rooted, I used ZRoot and installed 2.4.0. I didn't change anything and used the exact same process of simply copying over the 3.0.0 files over to the root directory of the internal memory and did the recovery procedure (vol+ and pwr keys). It worked like a charm.
hogasswild said:
The very first time I rooted, I used ZRoot and installed 2.4.0. I didn't change anything and used the exact same process of simply copying over the 3.0.0 files over to the root directory of the internal memory and did the recovery procedure (vol+ and pwr keys). It worked like a charm.
Click to expand...
Click to collapse
Ok cool, thanks cant wait for my g tablet hopefully sat morning
I think you'll like it a lot. I also own an iPad. While they are similar they are also a little different. Merry Christmas!
hogasswild said:
I think you'll like it a lot. I also own an iPad. While they are similar they are also a little different. Merry Christmas!
Click to expand...
Click to collapse
my mom has an ipad and my dad could only buy it while i was on my honeymoon bc he knew i wouldnt approve of an apple device in the house haha.
rothnic said:
It is also not hard to alter the update so that it does not overwrite clockwork.
Open update.zip
Find updater-script, Open in notepad++
Remove the line that references recovery.img
Flash update
Click to expand...
Click to collapse
My device hasn't come yet (damn you FedEx!) but I'm eagerly awaiting it.
My plan:
Unbox, start it....do a factory reset from the getgo if it has enough juice.
Set it back up. Charge it to full. If whatever comes on it is as unbearable as I've seen in on Youtube - start modifications.
Will CWM install on it AFTER I do the update if it's available to me? I've seen that the update messes with it if it's already there - but noone's mentioned putting it on there after the fact. I may just go that route for simplicity sake.
Thanks for this!, and thank you all for chiming in with your experience. I feel much better about just getting my hands dirty in it all. I had wrote something to someone yesterday about jumping in and just doing it, but when it comes to dealing with it yourself it can be a daunting task - especially when it still has that new smell, lol. Anyway, thanks again. You guys really rock.
Will stop back later on after I've done my thing
I think they are both nice devices. There are trade off for both of them. I think the screen on the iPad is wonderful, where the gTab's is okay. But the gTab has a forward facing camera, you can print from it, and you can modify it fairly easily too.
Sprdtyf350 said:
Finally.. This tablet is very easy to play with. It is pretty much unbrickable.
Click to expand...
Click to collapse
...famous last words...
Seriously though...trust the directions from the great devs like roebeet. Follow their instructions word for word. You can switch ROMs and then flash back if you want. No worries...
Off topic!
Well...disappointment! Fedex had my package out for delivery at 8am and at 8pm, they're not here. This is why I like UPS, they show up at my door on the day of delivery, no exceptions - they have shown up at almost 9pm before. The Archos 101 I got was sent out at 8am as well but got here at 1:30pm - I suppose that was before the holiday rush.
Checking the details of my tracking I'm seeing a "delivery exception" at 7:30pm (I guess it was time to get back to the facility so they can clock out by 8pm?) and upon calling them I get a somewhat stumbling but polite CS who tells me the delivery went out "late" - upon which I asked if 8am was considered late, especially from a distribution facility WITHIN the same zip code as I am, and all he could say was "Very sorry about this".
Aaaanyway....I guess it will be tomorrow before I can report my adventures.
Think I'll be able to get my $3.99 back from Amazon? I have Prime and with that the package would have come tomorrow anyway. Basically my $3.99 is wasted. Imagine if I didn't have Prime though? Whew.
ima_UNC_fan said:
...famous last words...
Click to expand...
Click to collapse
If you can figure out how to brick it you will probably get an award.. It won't be a good award but probably one of those top ten dumb things people do awards. So far unless you plug the motherboard into a wall socket no one has bricked one. May think they have, but like I said before I doubt it..
And your right.. If it can be done, someone eventually will figure out how. And then we will all laugh at them.. At least I will
I finally got the G tablet tonight and...alright, don't flame me for this - but I don't see what all the complaints about the screen being horrendous or the device being molasses slow are about?
I don't know how people are trying to view it...but when looking at it or setting it on a stand to watch media, I'm not seeing any problem with the viewing angles. It's about the same as my laptop so I watch it the same way.
It's not even a 1/4 as slow as the stuff I've seen on Youtube or in some of the review videos I've seen around the net. I haven't gotten a single FC. Granted, I haven't put in a SD Card yet so maybe problems will start then?
I guess I should note, the very first thing I did was did a factory reset. Then I hooked it up to Wifi and got the 3053 update. I'm one of those who will be waiting for the 'official' update on the 24th.
I set up the time and date, restarted and everything works. I haven't installed flash yet (don't need it that much) and stuff that I DO want on there right now works fine (skype, pandora, fring, dropbox, evernote). I'm slowly figuring out a list of what I want/need from my Mytouch 4G to port to the VS GTab. Figure I don't really NEED Gtalk, Gmail on there because I have these on my phone AND PC - do I really want them making noises all around my home on 3 devices? I was concerned about getting the Google Apps on but now I'm finding I really don't need them. So it seems to me this will be a matter of learning to separate what I need on a tablet vs. my phone - I was of the mentality that I should just get whatever's on my phone on the tablet, this is something others apparently do as they seem to want everything that's on their phone, on their tablets as well.
I personally don't see the point in that. Had I had the Google Market, that would have escaped me as I'd have used Appbrain to just get my motherload of apps from the MT4G to the GTab. Not having it has slowed me, and now I get to re-evaluate before I do grab apps for it.
Now I just have to merge/convert my HTPC into a NAS device as well and find an app that will allow me to DLNA stream media from it and I'll be in mobile heaven.
I haven't had my wifi drop at all anywhere in my home and I've marched all over with it (I use full Wifi N, no G compat. so maybe my range is wider?). Tried email, etc. to replicate crashes and force closes but haven't so far. No surfing issues. I DID find that one app got 'stuck' being downloaded and I had to delete the file before the 'downloading' icon would go away, even after restart.
Maybe the trick to getting a workable GTab in the first place is to factory reset it before first use? Iunno. Things may change and issues may pop up the more I use it and as time passes - but so far, so good!
Again, I can't thank XDA enough for the advice and info. I've found and been given.
Sprdtyf350 said:
If you can figure out how to brick it you will probably get an award.. It won't be a good award but probably one of those top ten dumb things people do awards. So far unless you plug the motherboard into a wall socket no one has bricked one. May think they have, but like I said before I doubt it..
And your right.. If it can be done, someone eventually will figure out how. And then we will all laugh at them.. At least I will
Click to expand...
Click to collapse
I figured it out. Accidentally hit one of the devkit nvflash .cabs and boom
Hey folks. I`m new to Android, but I am well versed in how to manipulate Linux systems and I've got a new SGH-i896 that Ive been itching to tear apart.
I've never touched a phone in regards to hacking, and I know there's a lot of system stuff that can be screwed up while tweaking. What I'd like to do is explore these custom ROMs and see which is best for my specific phone.
If anyone could talk me through a good first option for trying out, it would be great. I see so many options, but I'm not seeing a popular choice, or a safe "for-dummies" ROM. Thanks for any help.
JavaMac said:
Hey folks. I`m new to Android, but I am well versed in how to manipulate Linux systems and I've got a new SGH-i896 that Ive been itching to tear apart.
I've never touched a phone in regards to hacking, and I know there's a lot of system stuff that can be screwed up while tweaking. What I'd like to do is explore these custom ROMs and see which is best for my specific phone.
If anyone could talk me through a good first option for trying out, it would be great. I see so many options, but I'm not seeing a popular choice, or a safe "for-dummies" ROM. Thanks for any help.
Click to expand...
Click to collapse
Welcome!
Now first you must get your tools (Android SDK, Odin3) and study them a bit before flashing anything. Nothing is safe but if it's done properly your chance of bricking your phone are close to none.
Look in the Dev and Q&A for sticky post regarding flashing roms and how to start.
I would recommend you stay away from Gingerbread roms (2.3) for the moment. It requires to flash a new bootloader and you need a good understanding of how to flash and how to use Odin3 options before you venture there.
For your first flash i would recommend flashing Firefly rom but your free to select the one you prefer. Always read the first post of the rom to learn what it offers and don't.
Happy flashing
JavaMac said:
Hey folks. I`m new to Android, but I am well versed in how to manipulate Linux systems and I've got a new SGH-i896 that Ive been itching to tear apart.
I've never touched a phone in regards to hacking, and I know there's a lot of system stuff that can be screwed up while tweaking. What I'd like to do is explore these custom ROMs and see which is best for my specific phone.
If anyone could talk me through a good first option for trying out, it would be great. I see so many options, but I'm not seeing a popular choice, or a safe "for-dummies" ROM. Thanks for any help.
Click to expand...
Click to collapse
What he said^^^
I would start out reading a lot. Start here and here. Use this program to get started. This will allow you to flash FROYO. You can now flash FROYO custom ROMs.To flash Gingerbread go here read post 1 to get directions after flashing Stock FROYO. Once you have the GB bootloaders installed you should be able to flash custom GB ROMs. I stress read a lot before flashing. You can brick your phone easily if you don't. Good luck and welcome to the world of ROM flashing!
silvertag said:
Welcome!
For your first flash i would recommend flashing Firefly rom but your free to select the one you prefer. Always read the first post of the rom to learn what it offers and don't.
Happy flashing
Click to expand...
Click to collapse
I'll second firefly, very nice smooth rom, i used it for over 2 months.
I already had the Android SDK, as well as SuperOneClick. I went ahead and downloaded Odin3, and the Captivate Toolbox and the other linked tools. Thanks for the links by the way. I've also already taken a look at how to flash a custom ROM. I'm going to read a bit more and settle on a choice by tonight.
Thanks for all the help.
Having a bit of trouble on my first go
Hey folks. I went over the reading material that was provided and I went ahead with this guide
[link]http://forum.xda-developers.com/showthread.php?t=884364[/link]
I got through to the point where I had to use Odin. When I clicked start on Odin, it ran through the predicted cycles and claimed to be successful. My device won't mount now though. I can't see it in my computer anywhere, and I'm not sure how to continue.
Any thoughts would be appreciated. Thanks.
You were on stock 2.1 or 2.2 ?
What rom did you flash ?
What files did you put in Odin and with what boxes checked ?
Is the phone booting normally ?
What part does not mount ? (It's not detected by windows but charges when you plug in the usb cable ?)
Settings>applications>usb settings. Make sure thats set to mass storage.
stock has that checked to kies by default.
Let me clarify:
My phone is currently only sitting at the battery screen, with an empty battery image and a spinner.
I can bring up an AT&T splash screen that says "World Phone" below it if I follow the instructions to recovery mode, but it still does nothing.
I'm afraid I've bricked the phone, and I'm missing some clue as to why.
if something comes up on the screen it is not bricked.....i hate that word
you are not bricked. any sign of life at all means not bricked.
what odin did you use? im guessing odin one click, which means you have a newer build phone and it bootloops when odin one click is used.
get into download at this point you may need a jig, once in download mode use this package and you will be ok (you are canadian right?)http://forum.xda-developers.com/showthread.php?t=979133
Thanks for the tip pirateghost.
Hmm, I might be offended a little.
You thank the guy who pops in just to correct your jargon and not the guy giving you a link to help you?
studacris said:
Hmm, I might be offended a little.
You thank the guy who pops in just to correct your jargon and not the guy giving you a link to help you?
Click to expand...
Click to collapse
LOL
damn, studa, tryin to drag me into the dirt
I'm wondering if there's a way to do this without a jig. I don't really want to get that involved if I don't have to.
If I do have to, I will, but let's try to keep this in the software department if we can.
Thanks to everyone who's been helping out here.
Lol I was only joking
no harm done
there are a couple button combos to try if those don't work a jig is needed, but it's a very cheap and easy process to make one not "involved" at all or under 10 us dollars if you were to buy one.
Alright button combos to try:
Both volumes held plug in usb cable.
Cable in, pull the battery, hold the volume buttons while reinserting the battery.
JavaMac said:
I'm wondering if there's a way to do this without a jig. I don't really want to get that involved if I don't have to.
If I do have to, I will, but let's try to keep this in the software department if we can.
Thanks to everyone who's been helping out here.
Click to expand...
Click to collapse
-Remove the battery
-Remove the sim card
-Remove any external sd-card
-Pop battery in
-Hold BOTH volume buttons (on the left) and plug usb cable.
Are you back in download mode ?
Okay, I tried all the button combos, and it did nothing different.
I've only got the one micro usb right now. I guess that means I've got to go out and get another, along with some resistors?
This sucks. I guess I should have remained happy with the Android Rogers gave me.
If you insulate the resistors well enough you don't need to chop up the cable... You can touch the leads of the resistor loop thing you made directly to pins 4 and 5 on the phones usb port. Granted that way takes ALOT more fiddling with to work, but you don't have to hack a cable.
studacris said:
If you insulate the resistors well enough you don't need to chop up the cable... You can touch the leads of the resistor loop thing you made directly to pins 4 and 5 on the phones usb port. Granted that way takes ALOT more fiddling with to work, but you don't have to hack a cable.
Click to expand...
Click to collapse
So if I get the proper resistors, protect my thumb and finger, and apply them carefully to pins four and five on the phone's connection, it works the same way?
Looks great spec wise: microSD, no notch garbage, headphone jack.
I need something to replace my OP5 and need a headphone jack and microSD slot.
How is linageOS and flashing? Fairly simple or is it one of those really complicated phones?
I recently got this phone, and the phone itself is pretty great. The flip camera is amazing, and I impress everyone I go to take a selfie with.
Flashing LOS 17 is pretty normal I'd say. This was my first A/B device so it took a bit of getting use to, but a few tries, and I got it down.
As far as support, I think this phone has been pretty lucky to have as these people working on it, like luca for the LOS build, mauronofrio for his 9.0 TWRP builds, and bigbiff for this current TWRP builds, just to name a few. (Thanks to everyone out there helping as well!)
However, as always, the information on some of the details about this phone are scattered around the internet, and its taken me a few weeks to get a good grasp on what my options are with this phone, and some things im still not clear on. Sometimes, a particular detail is only mentioned once in one specific thread, and I guess there just arent enough users with this phone to spread the information around.
Specifically, this is some information I wish I knew about before I tried flashing this phone:
- On LOS 17 (the Android 10 versions), you will have a horrible camera experience. Not sure if its just me, but I havent found a camera app that works correctly, and has modern features like save to SD card / panorama / slow motion / etc. You would think the flipping camera would be the problem, but that actually works fine! One thing that seems completely botched is autoflash. I know nobody probobly uses autoflash, but it seems to use flash at random, in any camera app. The stock lineage camera app is extremely basic, and the quality isnt as great as stock, but if you can live with ONLY pictures and video, then I guess it works (autoflash still doesnt work). There are a couple of GCam ports. I havent tried them all, but they are patchy. The best one I tried only didn't have slow motion working (and autoflash). To my knowledge, there is no way to get the stock Asus camera app on LOS 17. There is, however, a flashable zip for the Asus camera for LOS 16 (Android 9), but that leads me to the next point.
- LOS 16 is a major pain to flash. I am actually going to try and flash LOS 16 right after this, so wish me luck. Ill update this if it goes well. Something is wrong with flashing these versions of LOS. I don't fully understand, so I dont want to say something wrong here and spread misinformation. The steps dont seem to be the same as flashing LOS 17. There are sometimes issues mounting partitions, and some people mention using the unofficial mauronofrio builds over the offical builds for some problem with encryption? Trying to boot into the Lineage Recovery for the 16.0 builds takes like 10 minutes, I almost thought my phone was just stuck, but leaving it there long enough, it finally opens recovery! Its just a pain. Lineage sometimes doesnt work if it wasnt installed using its own recovery, so i try to install LOS with LOSRecovery, and then switch to mauronofrio TWRP to install gapps, magisk and the asus camera app, but i havent gotten a working flash yet. I have to keep trying different combonations and it just takes forever for recovery to start and to flash things in the right order.
-There was an update released for this phone for Eastern countries for VoLTE/VoWifi, but it never made it to the west, and someone said they spoke to Asus, and said they dont plan to release that here (in America, canada, etc) Im not even sure if euro countries got it, but dont quote me on that. Point is, this phone _can_ use VoLTE/VoWifi, but you have to enable it yourself. This amazing man has a guide for the ROG Phone II, but i followed his steps, and it works perfectly on the Zenfone 6! https://forum.xda-developers.com/rog-phone-2/how-to/guide-enabling-volte-vowifi-v2-t4028073
Shoutout to HomerSP. Thank god this works. Why Asus wouldnt ship this phone without VoLTE amidst the 3G shutdown, i have no idea, but this features seems almost necessary to make and receive good quality calls anymore. So yea, if you get it, follow his guide. You need root for most of the steps. It seems complicated but its very easy if you just sit down and do it.
Uh yea, thats what I can think of right now.
Sorry for the wall of text.
I wish this phone was perfect, but flashing LOS and getting everything working correctly is taking me a while to figure out. I don't understand why I cant get LOS 16 to work, but If i get something working Ill post what I did incase anyone else is searching for an answer like me.
For anyone else looking to get this phone, Im starting to think just sticking with Stock firmware with Magisk is the way to go. Killer chipset, amazing cameras and app, 3.5mm, duel sim AND SD card (seriously wide tray, 3 slots!) The only thing this is missing is an AMOLED (if you prefer) and Band 66+71 (T-Mobiles best bands aside from 5G)
Alright, enough of my ranting. Message back with any questions, ill do my best to respond.
bobs50000 said:
I recently got this phone, and the phone itself is pretty great. The flip camera is amazing, and I impress everyone I go to take a selfie with.
Flashing LOS 17 is pretty normal I'd say. This was my first A/B device so it took a bit of getting use to, but a few tries, and I got it down.
As far as support, I think this phone has been pretty lucky to have as these people working on it, like luca for the LOS build, mauronofrio for his 9.0 TWRP builds, and bigbiff for this current TWRP builds, just to name a few. (Thanks to everyone out there helping as well!)
However, as always, the information on some of the details about this phone are scattered around the internet, and its taken me a few weeks to get a good grasp on what my options are with this phone, and some things im still not clear on. Sometimes, a particular detail is only mentioned once in one specific thread, and I guess there just arent enough users with this phone to spread the information around.
Specifically, this is some information I wish usenew about before I tried flashing this phone:
- On LOS 17 (the Android 10 versions), you will have a horrible camera experience. Not sure if its just me, but I havent found a camera app that works correctly, and has modern features like save to SD card / panorama / slow motion / etc. You would think the flipping camera would be the problem, but that actually works fine! One thing that seems completely botched is autoflash. I know nobody probobly uses autoflash, but it seems to use flash at random, in any camera app. The stock lineage camera app is extremely basic, and the quality isnt as great as stock, but if you can live with ONLY pictures and video, then I guess it works (autoflash still doesnt work). There are a couple of GCam ports. I havent tried them all, but they are patchy. The best one I tried only didn't have slow motion working (and autoflash). To my knowledge, there is no way to get the stock Asus camera app on LOS 17. There is, however, a flashable zip for the Asus camera for LOS 16 (Android 9), but that leads me to the next point.
- LOS 16 is a major pain to flash. I am actually going to try and flash LOS 16 right after this, so wish me luck. Ill update this if it goes well. Something is wrong with flashing these versions of LOS. I don't fully understand, so I dont want to say something wrong here and spread misinformation. The steps dont seem to be the same as flashing LOS 17. There are sometimes issues mounting partitions, and some people mention using the unofficial mauronofrio builds over the offical builds for some problem with encryption? Trying to boot into the Lineage Recovery for the 16.0 builds takes like 10 minutes, I almost thought my phone was just stuck, but leaving it there long enough, it finally opens recovery! Its just a pain. Lineage sometimes doesnt work if it wasnt installed using its own recovery, so i try to install LOS with LOSRecovery, and then switch to mauronofrio TWRP to install gapps, magisk and the asus camera app, but i havent gotten a working flash yet. I have to keep trying different combonations and it just takes forever for recovery to start and to flash things in the right order.
-There was an update released for this phone for Eastern countries for VoLTE/VoWifi, but it never made it to the west, and someone said they spoke to Asus, and said they dont plan to release that here (in America, canada, etc) Im not even sure if euro countries got it, but dont quote me on that. Point is, this phone _can_ use VoLTE/VoWifi, but you have to enable it yourself. This amazing man has a guide for the ROG Phone II, but i followed his steps, and it works perfectly on the Zenfone 6! https://forum.xda-developers.com/rog-phone-2/how-to/guide-enabling-volte-vowifi-v2-t4028073
Shoutout to HomerSP. Thank god this works. Why Asus wouldnt ship this phone with VoLTE amidst the 3G shutdown, i have no idea, but this features seems almost necessary to make and receive good quality calls anymore. So yea, if you get it, follow his guide. You need root for most of the steps. It seems complicated but its very easy if you just sit down and do it.
Uh yea, thats what I can think of right now.
Sorry for the wall of text.
I wish this phone was perfect, but flashing LOS and getting everything working correctly is taking me a while to figure out. I don't understand why I cant get LOS 16 to work, but If i get something working Ill post what I did incase anyone else is searching for an answer like me.
For anyone else looking to get this phone, Im starting to think just sticking with Stock firmware with Magisk is the way to go. Killer chipset, amazing cameras and app, 3.5mm, duel sim AND SD card (seriously wide tray, 3 slots!) The only thing this is missing is an AMOLED (if you prefer) and Band 66+71 (T-Mobiles best bands aside from 5G)
Alright, enough of my ranting. Message back with any questions, ill do my best to respond.
Click to expand...
Click to collapse
Hot damn this was an excellent read. I will say I'm deathly afraid of this new A/B partition nonsense. I swear google did it just to screw with us modders. I don't mind putting some work in but I hate when it feels like I'm flying blind in a volcano lol.
I debated the OP7 Pro, but not having and SD card slot or a 3.5mm jack is just unacceptable at this point honestly.
I do prefer IPS, but I would hate to miss out on 66+71 ...dang that stinks
So it looks like this phone is a strong maybe, might just be the best I guess as I can't find any other better options. Though maybe I should look at the ROG Phone II?
Let me know how LOS16 goes if you don't mind, especially if it fixes the camera.
Alright. I know it's been a while since my other post, but I wanted to leave my latest here for any body else reading.
I could not get LineageOS 16 to work at all. The best I was able to get was LineageOS 16 booting, getting to the first time setup saying "Just a sec...", and then a black screen. Holding the power button or using the volume buttons caused the side controls to show up, like the "Power off", "Reboot", or the volume slider to appear, but the rest of the screen was black. After about a minute or two. It would actually freeze up, and restart. But that was it. I mentioned it in my other post, but the recovery for LineageOS 16 takes 5 minutes to boot, I timed it. Its unusual, something must be wrong.
So my options were LineageOS 17 (Android 10) with a horrible camera, or Stock ZenUI (also Android 10).
So I'm choosing Stock, so that I can have a decent camera experience. I really wish I could have LineageOS on this phone, and is one of the major reasons I bought this phone, but the camera app on LOS 17 breaks it for me. I'm just going to have to put up with Stock shenanigans and limitations.
Because I have been flashing so many different times, the state of my device is quite messy. I've been following these steps I wrote down to get a good install every time:
Boot into the bootloader
Use flashall.cmd to revert Slot A back to Android 9 ZenUI v1906.167
Without entering the system, boot into recovery
I edited the end of flashall.cmd so that it wouldn't automatically reboot to system
Apply the ZenUI v1909.194 update, which will end up in slot B
While still in the recovery, use the "Wipe data/factory reset" option
Boot into the bootloader, then back into recovery, to end up in slot B
Reapply the ZenUI v1909.194 update, which will now end up in Slot A. Both slots now have ZenUI v1909.194
Wipe data/factory reset
Bootloader, recovery, your in slot A
Apply the Android 10 ZenUI update, which ends up on slot B
Wipe data/factory reset
Bootloader, recovery, your in slot B
Reapply the Android 10 ZenUI update, which ends up on slot A. Both slots now have Android 10 ZenUI
Wipe data/factory reset
Go into the bootloader once more to get into slot A
Boot into the latest TWRP for Android 10
Swipe to allow system modifications
Check to make sure there are no mounting errors in the log
Flash the TWRP installer
Flash the latest Magisk
And your all done! Reboot to system.
Swipe to install the TWRP app on your way out
flashall.cmd is from the Sevice Firmware zip I downloaded from somewhere. It was in an unbricking guide, but It helps me by downgrading to Android 9, and setting up the partitions correctly again, in case they got messed up (which they have been throughout my testing)
The ZenUI updates I downloaded directly off of Asus's support page for this phone. You just have to pay attention to the fact that these are incremental updates, and need to have a specific firmware already installed in order to be flashed correctly (They say which once in the description). They also only can be installed with the stock recovery. (or at least, twrp never got very far when trying to flash them). I'd say just stick with the stock recovery for installing updates.
Speaking of TWRP, it has issues with restoring backups. It normally ends up with an error like "TarFork() Error 255", but apparently that can mean a bunch of different problems, so its not very helpful. I found that if you want any chance of the backup being restored correctly, you need:
- To be on the same Android version the backup is for (Android 9 restoring Android 9 / Android 10 restoring Android 10 / etc)
- Make sure TWRP doesn't have any mounting errors. This seems obvious, but most times, I had issues where TWRP couldn't mount a partition for some reason.
- You MUST have the option "Use rm -rf instead of formatting" enabled. I never got a backup to work without it enabled
Even after all that, sometimes the backup STILL wont apply. Once a backup fails to apply, nothing will work until I flash the service firmware and incremental updates again in order to try again. It's very time consuming.
Now, I don't know as much as I probobly should about linux or android, but that last option makes me tells me that instead of actually formatting / recreating the correct partitions, it just deletes all files and puts back the ones from your backup. That works great and all, but if the partitions get messed up somehow, the only way I know to restore them is by flashing the stock ZenUI updates in order (Service Firmware -> ZenUI v1906.167 -> Android 10 ZenUI). To add to the confusion, I'm not actually sure if TWRP backups/restores include both slots, or just the slot you are on. For good measure, I make sure to update both slots evenly, so that they end up with the same firmware version, however, I have only flashed one slot per update, and gotten a backup to work also. For example, instead of flashing each update twice, to get it on both slots, I have only flashed each update once, so that Slot A gets the service firmware, then flashes slot B with Android 9, then flashes slot A again with Android 10, and then restore, and It works. Its all very confusing and seems inconsistent. Maybe I'm missing an important detail, but I can't figure it out.
One last thing about restoring backups. I have a hunch that going through the first-time setup of the phone (specifically, adding a figerprint/pin) does something to the system or data partition. Whenever I was restoring a backup, I had a better chance of it working if I went through first time setup, and skipped adding a fingerprint/pin. I would then get to the home screen, and restart into recovery to restore.
Sorry if this is confusing to read. I'm kinda just dumping all my information for me or someone else to read later if they are as frustrated as I am now.
I wish it would all just work, or at least give more descriptive errors. Trying to google any leads I find reveal almost nothing. I feel like If I'm not a retired developer, there's no way to understand any of this.
Also, if you know how something works better than I do, or if I'm explaining something wrong here, please let me know! Really, I need all the help I can get on these topics.
Uh yea, so that's all I got. I have my fingers crossed that all the pieces can come together for this phone, but I know its going to take a long time if its going to happen at all. The Zenfone 7/Pro just got announced(released?) and maybe everyone will just abandon the 6 now. That seems to be the trend now anyways.
I am now running stock Android 8 with ezV2020 kernel for the DS version. Boot loader unlocked and Rooted.
As far as I can see, it is pretty stable. It was a long and tough process, but having already done the LG F800K it just took some hours to do the LG H990N and not days as the former did to break free.
So... just wanted to tell you guys, and let you know, it is possible. Both Sims are working, screen working, seems smooth and stable and all that.
Well, it was a lot of hoops, but I did think it might be possible - and it was and is.
Used my experience from the F800K on this little guy, and it seemed to have payed off, even if I had forgotten a lot of things or had to gather my thoughts on it.
But what a fight... But there you go.
Although it seems like it might be locked on the 4G, and I wanna have it run 3G as the radiation is much much much smaller compared to 4G. Like it is amazing to see the difference between the 2, one being nearly always in the Green by the testing instrument and the other nearly always in the Red. Just utter terrible. But I a have an app that should work that out, or maybe it just need a code and adjustment. dunno what they done to this. But should be workable. There was this code with putting the mobile number into it that got you into a menu... But I found an application for my new used LG mobile that could do the trick which name alludes me... but wait a minute and I will get it. That will most likely be my first try to fix the issue. 4G Switcher is the name of the app and it should be all clean and free!
Dearly regards
- Darkijah
Update... the good news first.
The H990N is running very smooth with the A8 Rooted with the DS kernel of ezV2020... The bad news... the Rotation and Camera does not work.
Not sure if this was something that happened after I installed Lineage 17.1 A10 and then stored it or if it was a problem before that. I just don't know. It looked like it did fine for me, and yet... apparently some issues. I tried to install a foreign kernel like I had done before, but TWRP would not flash it because the kernel file was foreign to the system. Which is odd as I flashed the mobile with the F800K kernel to get it working first hand, ezV2020 1.0 if I recall correct.
Maybe fastboot or something could installed it, adb whatever - still confused by it all...
Lineage by the way was somewhat horrible, and when I found out the sound from the Phone Jack was utter horrible I quickly turned around back to A8 stock. Although now witnessing these issues. I don't know if those issues where there before or not - or if it was something coming after the restoration from Lineage. A lot of factors can make issues.
But the mobile overall, works with network and it does run very smooth compared to my F800K, at least I seem to feel a difference here. One is slower to react, and the other is just butter smooth.
Not sure if I should toy more around with the stuff... I still have my new mobile incoming at some point when they change the broken screen. Getting a little sick and tired of the Android nonsense everywhere, which is literally is, everywhere. Issues, and looking for work arounds and what not, it is never ending.
Rooting should be as easy as pushing a button - and in my opinion should be default out of the box. No user should need to tinker and toy around with there expensive device to get things in order - the criminal companies purposely working against the users on so many levels. Highjacked the whole thing and filling it up with nonsense in the name of security or what not.
To early to say, but I might have found a fix. That took hours and hours... And still at it. But I have the Camera working and the rotation and it seems to still be running smooth. So... Hopefully no more issues, but I will further test it and try some things. It seems this issue is in all H990N20h stock Roms - I have one left to try out. I just tried a DS stock Rom and after installing the kernel and all, doing all the steps I am now into the system, need more testing if everything works, but... Well the Kernel ezV2020 is DS and now the system is DS, also known as Global if I recall. The TWRP is H990 another dual variant. There are absolutely some options to do, but they only allow 2 images being downloaded from the site and it takes a lot of time trying things out, installing it and making it work in the first place. Hours and hours wasted on this :/
But... just wanted to make an update for you guys Found a solution it seems - although there might come up new issues, usual do with Android, but hopefully it everything works!
You have to use the old version of TWRP to fix the lock issue if you get a screen like that. Very annoying, but the oldest version I have breaks it, and then you can install another higher version thereafter. Wipe out the data, and I have wiped out all else except system, not sure if it is needed overall... But in any case, that is my observations for now. I have used TWRP versions before 3.3.0 to unlock this locking issue.
Another issue is that if you go into the system it seems to delete TWRP, so... There are all these steps to do to make it work, *Sigh*.
H990N20f_00_OPEN_HK_DS_OP_1214 - camera and rotation not working.kdz
H990N20h_00_OPEN_HK_DS_OP_0225 - camera and rotation not working.kdz
H990ds20b_00_OPEN_AU_DS_OP_1108 - Newest DS version and working.kdz
H990N20d_00_OPEN_HK_DS_OP_0920 - Oldest H990N A8 but working.kdz
Here are my data so far.
I don't get it, Android is a madhouse. So after having tried things to get the Camera and the rotation to work in the stock A8, kernels and all... Then now installing the newest that did not work. Now it work all of the sudden. Makes zero sense and typical Android. I thought it might work and just for lunacy of it all I tried to install it to verify it still did not work - and now all of the sudden things that did not work, works even if I did the exact same things. It is an utter madhouse. And just typical Android...
After trying different kernels and what not... Downloading another version that did not work, downloading another and another variant of the DS... Then trying the DS that worked, then trying the oldest of the H990N working, and then trying the Newest of the H990N, and now working...
So once again I seemingly wasted hours and hours on something that now just works... Like this is something that happens all the time working with Android I have found out.
The only thing I can conclude by this, is that the installation of the DS in Partioning DL with boot and recovery unchecked, 4 unchecked in total. Must have done something to it, so it could apparently work for the other main images. At least, that's the best I can do, although I don't see why it would be related to fixing it, but it works now with the main and newest H990N image...
I wonder if my old backups would work with camera and rotation if I installed them... but... I'm not so sure I wanna try... But then again... If so, it would make zero sense. In any case I am now making a backup of the one I know 100% to work with camera and rotation H990N. Then I can always try to restore my old backups and see if the problem is there.
First older backup with the camera and rotation not working, restoring crashed the system now before being restored. *Sigh* Trying the first backup that also had the camera and rotation issue.
Well... At least I got it working, it seems. So, so far so good I guess...
My oldest backup got restored, and the Camera and rotation now works... Seems far out, but it is android so not a big surprize I guess. Faulty by design.
Anyway I will try to restore my second backup again and hope for the best... It must have been the H990DS Rom that fixed something while installing it, although have no idea why, and can make no sense of it.
Got my second backup up restored this time... The Camera and Rotation works... Like... I just don't know what could change here. But it started out working when I installed the H990ds stock so I guess it must have something to do with that, beside that I have no idea.
Seems the sickness went away from one mobile and planted itself on the other... I feel more and more that Satans minions are doing these things... Whatever the case, now my daily working mobile is having Camera problems all of the sudden... This is insane, 2 mobiles which should have nothing to do with each other, one mobile having a camera issue, and solving itself all of the sudden, and now the other mobile is infected... Like, just, just give me a break...
You gotta be kidding me, it now also have the turn issue!... This is utter insanity... Like seriously.... *Sigh* What is going on here.
Thinking seriously that a hammer can fix everything!
I downloaded US996 now that US996 is used so much for the F800 mobiles variants, well my F800K did absolutely not like that, I tried it twice and got nothing. It changes partitions apparently - It never loaded up in the system at all.
Anyway, so knowing that the H990DS stock seemed to have fixed the screen issue and rotation issue on my H990N version, I installed that on the F800K and the system worked, and with camera and rotation, although you need a lower version of TWRP to get through the security nonsense as seems to be standard. Well, the H990DS version worked on the F800K and I wonder if it might be a better choice overall to use for it. But it did look pretty good and no Korean nonsense text. Well... I am now restoring my backup of my former system with the sickness that I made before all this, and see if it has fixed it like it did with my H990N. Need to restore +50 GB because of TWRP programming nonsense and then we will see if the Camera and rotation has sorted itself out.
Interesting if it fixes both variant phones... And maybe then it might be better just to use that version on both phones, not sure...
If it sorts it out at least, I think we have a good indication that the DS version H990ds20b_00_OPEN_AU_DS_OP_1108 is a cure for this sickness, it seems.
The F800K seemed to become more sick and skype did not work and it was terrible slow to respond :/ And then of cause the camera and the rotation did not work either. Not sure what is up with that sadly. Not sure what the overall issue is. Maybe I need to keep to the older versions of TWRP or... Dunno...
But I might try the DS version on both systems, if it fixes the 2 main issues, it might not ever come on it. Maybe... Or maybe it just fixes it overall after having been installed, no idea.
I wonder if twrp-3.2.3-0-h990 might also be used on the F800K - if the US996 is not so compatible with the phone, maybe the TWRP is not so compatible either... And the H990 should be close to the DS and H990N version as far as I know...
Restoration failed.... ohh no.... hmmm - might be that the H990DS is different in regards of partitions I wonder...
I will try again and if it fails again, I will install the right stock image and see if it wanna change some partitions and thereby show if there is anything different which might break the beta full partitioning backup. The foolish nonsense of backing up a lot of empty space. Utter insane, but overall Android is insanity.
I feel that the TWRP programmers are lead by Satan, some of these choices that is found is just outrageous. But if you wipe out the competition you can rule over it all, the same with Magisk if there is no competition then it is easy for them to stir the boat. If programs takes the lead and crush everybody else, then they can begin to play tyrants and promote insanity.
Anyway, most likely will get another fail with the backup, partitioning being different in size or something. As TWRP forces this bull**** on the users, and many other things. But can't complain about it, then the blotting pen comes by here on the forum. Censorship, as always, nothing new these Satanic days of hating Truth.
Anyway, I will fix the F800K image and then restore things, that should do it. Then again, it might be better to jump on that DS image overall... *Sigh*
And see if I can get my data with me... Usually also makes issues, because programmers makes it near impossible for users to easily do what they wanna do.
We can't have to much freedom you see...
58 GB's... insanity and waste of time. Programmers love to put that bull**** on us, Android is faulty by design and the programmers outrageous following blindly along pushing more garbage - oh how I wish the Linux Pine or Librem phones had been closer to running as a daily. I would not be on this Android jail bull****, and insanity land of wasting my time with things which should have taken 1 second to fix without breaking anything and yet ends up taking months. Sick sick sick.
Android seem nothing related to Linux, no freedom, no nothing. Just Tyrant companies and programmers, ads all over and other filth. Well the progress is 42 GB and going, getting close to the breaking point I guess.
XDA is full of ads as well, same as all the website with any android stuff - ugly and disgusting filth. Because no website can be run without any ads, apparently...
Yup the restoration failed... but if the partitioning is different then it is no surprise when TWRP programmers program like drunkards full of demons.
Hopefully will soon have figure this out so I can wipe out windows 10 and get on linux... but using LGUP which is running on windows. Don't think there is a Linux version as far as I know. Okay system installed, although it did not give me any warnings of changing the partitioning... I wonder... If it will now restore my backup and if not... then I am in trouble. As this was my main phone... I should have copied everything from the internal to the Micro SD card before doing this.
Should have taken my precautions as Android never seem to do what is expected of it. Always new wacky loony things incoming from all sides. A backup should work but don't expect it too.... Because, Bull****.
Insanity: doing the same thing over and over again and expecting different results. Albert Einstein
I guess he never tried Android...
The error restoration in TWRP could also be related to the version of TWRP, dunno I might have used the old version. Can't remember, but have to take that into consideration as well... As it did not seem to do anything with any partitioning when I ran the H990N stock image.
In any case the H990N stock image is loaded this time - I will restore it with the old TWRP, and if that fails again try a newer version of TWRP and redo it again again again...
So many factors play in, and downgrading for this and upgrading for that. Because... that's Android.
Well, it restored it although with some errors, but not the overall error. Something about some folders it could not enter, which I have seen before. I don't think it is a problem but... I will just test out the Camera and rotation and then go back and restore it with the newest version of TWRP that I have working and see if I get the same issues. The BIG moment... Have it worked? Rotation works... next... Camera works!
Whatever seems to be the issue the H990ds20b_00_OPEN_AU_DS_OP_1108.kdz takes care of it and one can just return to the former stock version or restore the backup.
And I do wonder if I should just install the H990ds20b version on both mobiles really... Seems to be able to run on both variants of the LG that I have.
ok boys and girls i scewed up. i was installing HAL9 mod 5 and i hit the erase data button twice and saw the box unchecked as i hit the install button. m y heart sunk and the install continued. i thought to myself well i'll just go into recovery and erase the cache and do what i can there. well guys i have not been able to get into recovery. i have tried every method i found online which i'm guessing isnt all of them. ... i hope. i dont have any buttons beisdes a touch button that lights up when i turn my lights on. this button is a mute button while android is loaded. i also have a reset button which ive hit in every combo i could find. so far i have tried holding down the reset button for 15 to who knows how long waiting for the mute button to flash which it never does. i have tried hitting the screen while i let out the reset button in every corner and with 5 fingers. sounds wierd to me but i saw it work on youtube haha. ive contacted the seller through amazon for firmware and directions to get into recovery but i dont have high hopes. does anyone have any ideas? ive attatched some info pics.
also this head unit came with android 10 installed
It would be cool if people posted all the ways they get into recovery or maybe i should of made a post about all the different ways to get into recovery on android head units so there is a one stop shop for people looking at how they could possibly get into recovery mode.
FloppyDiks said:
It would be cool if people posted all the ways they get into recovery or maybe i should of made a post about all the different ways to get into recovery on android head units so there is a one stop shop for people looking at how they could possibly get into recovery mode.
Click to expand...
Click to collapse
You miss the posts for getting into recovery on mtcd type units
No I found them. I don't know if I found them all but I've read a lot the last couple days. I've tried maybe 4 or 5 different ways that didn't work for me along with reading various posts i thought might help me. I guess want to be absolutely sure i have to build an otg cable and opening up my head unit. But I did research before my post. I also found a lot of posts similar to mine that got zero replies. But I think it's from no research before posting and that's understandable. I have tried to make a usb to boot from using the SD card tool from hal9 older mod and files from a new Ota but it didn't boot from there using the directions I found.
FloppyDiks said:
No I found them. I don't know if I found them all but I've read a lot the last couple days. I've tried maybe 4 or 5 different ways that didn't work for me along with reading various posts i thought might help me. I guess want to be absolutely sure i have to build an otg cable and opening up my head unit. But I did research before my post. I also found a lot of posts similar to mine that got zero replies. But I think it's from no research before posting and that's understandable. I have tried to make a usb to boot from using the SD card tool from hal9 older mod and files from a new Ota but it didn't boot from there using the directions I found.
Click to expand...
Click to collapse
Yep, sounds like partitions are now bad. OTG is the only way to restore that.
So will the forums about px5 work on px6? I do have the mcu and system files from the manufacturer. It's crazy to me that they're systems that have no way to enter recovery or bootloader at all. My system isn't bricked bricked it still tries to load android but stays on the android loading screen until enough time passes that it will restart.
Hi there, now it's me- same issue...
did someone found a solution meanwhile?
23rocky23 said:
Hi there, now it's me- same issue...
did someone found a solution meanwhile?
Click to expand...
Click to collapse
Only hundreds. Toast n jam.