What does this do?
It essentially converts your Optimus G into a full-blown Nexus 4 8gb. It remaps all partitions to the Nexus 4, overwrites all AT&T firmware with Nexus stuff, all the Nexus partitions, etc. Even the bootloader is overwritten by the Nexus 4 bootloader. Bootsplash becomes Google's logo, etc. Essentially it replaces every single thing on your current phone with its Nexus 4 equivalent. With this, you can flash anything from the Nexus 4 forums, including all of their ROMs, kernels, and more with little to no issues. You can even run stock AOSP Nexus 4. Essentially, it converts your entire phone into a Nexus 4. Nothing is needed to install Nexus 4 zips: its just like normal. But after you run the process, everything you do will be from the Nexus 4: things like recovery will have to be their Nexus 4 versions, etc. Besides the external look, your phone will essentially become a Nexus 4.
So to be clear, it converts your phone into a Nexus 4 and allows you to use every single thing they have.
Click to expand...
Click to collapse
-LTE will not work until you flash the AT&T modem (instructions coming soon about this)
-Volume keys are switched in mako ROMs (so, volume up is really volume down, volume down is really volume up)
-SDCard isn't mounting properly
-Only 8gb of the 16gb of internal storage is displayed as being available
-Capacitive buttons aren't working, on screen buttons only for now (the capacitive buttons dont even light up or activate... its as if they arent even there)
-Probably more
Click to expand...
Click to collapse
WARNING: THIS IS SO UBER-HACKY IT IS INCREDIBLE. This device was never meant to do this, and its essentially one giant hack. The device was never meant to run with Nexus 4 partitions. In addition, flashing anything via LGNPST is always risky, so YMMV. Be cautious, and don't blame anyone but yourself if something goes wrong. You are the one taking the chance in flashing this. This replaces every single one of your partitions with a Nexus 4 partition. It is far more risky than just a normal ROM flash. Be careful and backup whatever you need.
I CANNOT EMPHASIZE THIS ENOUGH. IF YOU ARE A NOOB AND HAVE NO CLUE WHAT YOU ARE DOING BESIDES NORMAL ROM FLASHING, DONT FLASH THIS. YOU WILL BRICK. THIS IS EXTREMELY DANGEROUS.
Instructions:
1) Go here: http://forums.team-nocturnal.com/sh...vert-your-LGOG-to-a-Nexus-4?p=16971#post16971 and find the download link on the page
2) Extract the .tot file out of the zip file you just downloaded
3) Rename the .tot file to have a file extension of .bin
(so now the name should be LGE960AT-00-V10c-NXS-XX-OCT-25-2012-JVP15Q-USER+0.bin)
4) Install LGNPST if you haven't already, and the necessary drivers
5) Start LGNPST
6) Connect your phone by putting it into download mode and connecting via USB cable
You can do this by holding Power + Volume Up + Volume Down
7) Wait until your device is recognized by your PC
8) Where it says DLL File select the lgnpst_ls970.dll one
9) In the file selector below that, select the .bin file you renamed before
10) Start the flashing process
11) Let it complete. It should hit 85% and then come up with an error saying the device was disconnected; thats fine, just close out of LGNPST
At this point your phone should be booting with the Google Nexus boot animation
12) Wait for it to boot up. If it doesn't boot in 5 minutes or so, or you just want to start fresh, continue on. If it boots up and you are happy with it, continue to the "Further Notes" section of this guide.
13) If it isn't booting, get into the Nexus bootloader by holding Volume Up + Power.
14) Make sure that "FASTBOOT MODE" is in red on the bootloader and connect your phone again
15) Run the following fastboot command:
fastboot -w
This will wipe ALL of your data. Essentially it is a factory reset.
16) Press the power button to select "START" in the bootloader and cross your fingers
17) It should boot now all the way through.
Further Notes:
- You can now flash anything Nexus and it should work aside from the issues mentioned above
- Flashing other kernels isn't really recommended; I've had some touch issues with some of them, but there should be no harm in trying
- To install a custom recovery:
Download any Nexus 4 recovery you want (I prefer TWRP)
Reboot into the bootloader using Power + Volume Up
Run this command:
fastboot flash recovery <path-to-recovery.img>
How do I return to stock?
Download this zip: http://downloads.codefi.re/thecubed...are/LGE970AT-00-V10o-ATT-US-SEP-29-2012-0.zip
Follow the same procedure as above in flashing the .bin in LGNPST
It should return your device to 100% factory state
Future Notes:
I will continue to work on this method. I will be working on a modified mako tree and fix all the issues that are currently present (hopefully) as mako is fully open source. I have already fixed the volume keys bug (was an easy one, thanks SnowLeopardJB) and I think I also have fixed SDCard mounting. LTE still has to be tested as I am not in an LTE area, but if it isn't working (which it 99.9999% wont be) there's an easy fix for it, from what I hear as well. I'll post workarounds tomorrow when I get some time.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Donate to Team Codefire's Members and Devs! They are:
g33k3r - Donate to Lmarazzi86 [at] gmail [dot] com on paypal!
Shelnutt2
kmdm
synergy
jcase
sextape
xboxfanj
Donate to Team Nocturnal: http://forum.xda-developers.com/donatetome.php?u=3950620
Click to expand...
Click to collapse
xboxfanj for the original idea
SnowLeopardJB for testing on AT&T
sextape for the original tot from the Nexus 4 and LGNPST
XsMagical from Team Nocturnal for buying me this phone
Droidiac13 from Team Nocturnal for buying me this phone
ChongoDroid from Team Nocturnal for buying me this phone
Shelnutt2 for being a boss
And all the rest of Team Codefire for their fantastic work on unlocking this device
Click to expand...
Click to collapse
This would have been nothing without xboxfanj. Please find him and thank him. I am simply continuing down this path to fix the outstanding bugs this has.
Also thank g33k3r! He was the first one to try it on AT&T and got it working!
This is what developing is all about!!
CCCCCCombo BREAKER...
you just killed the game rohan
Can not wait to get to work tomorrow and try this and help workout some of the glitches... an early thumbs up and good job with this! Definitely glad to see this kind of development going for the phone! Team Nocturnal you guys are awesome!
OMG OMG OMG!!!!! flashing now!!!!
Great work everyone!
Sent from my LG-E970 using Tapatalk 2
Mmmm gonna keep an eye on this one.
Way to make use of the phone man, this is just wacky stuff. :good:
Who said ports can't be fully functional..
BoostedSR20 said:
Mmmm gonna keep an eye on this one.
Way to make use of the phone man, this is just wacky stuff. :good:
Click to expand...
Click to collapse
Thanks for selling it!
screen pics please
Forgive my inappropriate mouth, but OHMYB*LL*ACK!!
I love you devs.
chachin said:
screen pics please
Click to expand...
Click to collapse
Have you seen the Nexus 4??
Same as that lol
This rewrites your partitions so you will lose everything and it could brick you. To go back to stock or a stock based ROM, you will need to LGNPST a stock build.
While it is amazing to see AOSP, it is very risky and I would recommend waiting until a more reliable method (which the other team, which I am part of, is working on). However, if you cannot resist the urge and flash it, whatever happens is your responsibility. If you brick, don't say I/we didn't warn you.
So currently only on screen buttons right?
Sent from my LG-E971 using Tapatalk 2
It may sounds dumb, so bear with me.
Does this mean I can have AOSP AND be able to access my external memory card?
Thanks in advance!
Thus use on screen buttons or the capacitive buttons
Sent From My AT&T LG Optimus G
Elisha said:
So currently only on screen buttons right?
Sent from my LG-E971 using Tapatalk 2
Click to expand...
Click to collapse
Yes, thanks, ill add it to the OP
I personally like them more, but YMMV
Elisha said:
So currently only on screen buttons right?
Sent from my LG-E971 using Tapatalk 2
Click to expand...
Click to collapse
yeah. Since you have the Canadian variant, this doesn't benefit you much though, considering that you can already run N4 kernels.
For the volume key, there is 2 way to fix it. You can do it in kernel (Using the N4 source, there is a function to "fix" volume key for mako. Simply remove that function or rework the output. You can also fix them by modifying the keylayout file (/usr/keylayout/keypad_8064.kl) and reverse the number for volume UP / Volume down.
For the partition size, you can extend the partition up to 25GB if you have the 32GB LGOG or 12GB for the 16GB optimus G.
I don't think flashing back the AT&T modem is a good idea. Every time we tried to flash Optimus G modem on Nexus 4 it didnt boot.
Related
Ok guys, first of all I have to say that you cannot access recovery without something like quickboot -or- rom manager so please get your preferred app for this.
I AM NOT LIABLE IF YOU SOMEHOW MANAGE TO **** UP A ONE CLICK APP! Do not ask me for support. Learn something and fix it yourselves.
Next, I will say that AlbertWertz will be making a video, but this is -really- simple.
All you do is click the button corresponding with what you want to flash.
I will work on aesthetics later but for now, it works, checks md5's, and flashes the images.
Problems:
None with my app, however there are sure to be a few bugs on the recovery. Also: this flashes to internal, that's why I included a reset to stock button!
How to fix a borked install: CLICK ME CLICK ME FOR THE FIX!
(Note, you need superuser otherwise not a damn thing will happen!)
Download link:
here
Instructions:
Just click the button that has the recovery you want to flash. It's really simple. Screenshots, credit, and changelog will be posted in the next post.
Wait 10 seconds for the flash to finish then you can reboot if you want.
Please don't mirror
Changelog:
Code:
2.1: Updated with 1.4.3 stock image and the 6.x CWM image.
2.0: Cleaned up the code, added better md5 checking now it won't flash without a good md5.
1.5.5: Fixed md5 hash checking
1.5: Added Reboot Recovery button
1.1: Fixed filename issue for stock recovery
1.0: Initial release.
Credit:
Code:
nemith for the recovery
myself for the image of stock and designing the app
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is my post.
dropbox not working i get error 404 page popup.
Also if we flash the CWM from xboxes thread do we need to uninstall it then flash this one?
Oops! No one could have flashed the stock recovery back because of the simple screwup I did. I didn't have a properly named file. ^_^ Anyway, it was fixed.
promek said:
dropbox not working i get error 404 page popup.
Also if we flash the CWM from xboxes thread do we need to uninstall it then flash this one?
Click to expand...
Click to collapse
It was still uploading. It's done now.
Also no, you shouldn't have to uninstall his CWM. It's the same image, just simply flashes over the old one. It just helps to be able to flash whatever whenever you need it.
dumb question
which one is better to flash, or can you do both
and then switch between on boot
cuz on my xperia x10, i can switch between, both on boot...
Stock recovery is what you need if you plan to use the unroot method, etc. CWM is used for custom software / firmware flashing...No, you can't switch between. You flash CWM if you want to flash zips and if you want to have stock recovery again which doesnt give you a menu, you flash stock.
I'll probably end up packaging my root mods into the flashable zip. I'll see if cfoesh or whatever wants to package up snowball mod.
Indirect said:
Ok guys, first of all I have to say that you cannot access recovery without something like quickboot -or- rom manager so please get your preferred app for this.
Click to expand...
Click to collapse
Hey, wanted to say thanks and wanted to say this: flashed CWM and at first I couldn't access recovey with n+Power, but now I can. Tried shutting down and then n+Power, nothing. Then used ROM Manager's "reboot into recovery" and it booted like normal instead of going to recovery.. then ROM Toolbox and used and "shutdown"... Started back up with n+Power and it worked. Tried again a few times with normal boots and shutdowns, then n+Power and it goes to recovery.. Hoping I remembered exactly what I did but hey, it works like it should on any device now
EDIT-Oh, apparently if I let go of the power button too quick then it doesn't go into recovery... just tried again with quick letoff and booted normal even though I had the 'n' button firmly pressed the whole time.. Gave it a 2 second count next time before letting go and went into recovery
Sent from my BNTV250
Donation sent. Thank you Indirect! I appreciate your efforts.
Update will be pushed out to add a reboot recovery button to the app.
Indirect said:
Update will be pushed out to add a reboot recovery button to the app.
Click to expand...
Click to collapse
What method of recovery did u use internal or sd and also I been seeing all this cool stuff on getting recovery to work but yet can't find the simplest way to root lmafo. Well thank bub and **** haters keep doing u on here and people will soon realize what's the real deal. But thanks again. Just been lurking till its the moment to unwrap that baby and be in love
Sent from my PG86100-EVO3D-using Tapatalk Born Jan 5th 84 and still getting it in eeee
As requested, i have cleaned this thread.
Peace!
Indirect said:
Update will be pushed out to add a reboot recovery button to the app.
Click to expand...
Click to collapse
Thanks again for another great project Indirect, i will wait until the update i trust more in you at the time of releasing such of complex things, though i dont know if its possible yet but have you think about a menu for normal reboot, hot reboot, reboot to recovery and shutdown when you long press power button instead of cancel and shutdown options? that would be an awesome project. Take it as a proposal/request to anyone that can help in make it possible .
Peace!
~ Veronica
Edit: I just realized that all the signature pics went down, weird my twitter logo disappear ... now they are back lmao
Update was just published, same link, just download it.
lavero.burgos said:
Thanks again for another great project Indirect, i will wait until the update i trust more in you at the time of releasing such of complex things, though i dont know if its possible yet but have you think about a menu for normal reboot, hot reboot, reboot to recovery and shutdown when you long press power button instead of cancel and shutdown options? that would be an awesome project. Take it as a proposal/request to anyone that can help in make it possible .
Peace!
~ Veronica
Click to expand...
Click to collapse
Yes I have that on my Asus transformer, like you say it has all the different options in one popup menu. Much more straight forward
Thing is, if it's a sizeable thing to code, is it going to be worthwhile considering cm7/9 is hopefully not far away ?
I know CM9 development seems to have halted (nothing updated on OP in a decent while) but it could still be a lot of work for something that will only be used for a very short period of time.
technically, i should be able to use this to flash back to "complete stock" (including removing cwm)?
It's used to either flash over stock recovery, or over CWM. Depending on which option you choose. It's the same process, just different files. That's it.
Fantastic work. You've made it easy to do and I thank you!
Sent from my ADR6300 using xda premium
Working with a net--restore is working!
Many thanks to bauwks, nemith, goncezilla, and indirect for bringing clockwork mod to the NT. I'm a thorough-going noob and always will be, so I've been waiting for a custom recovery so I could have a nandroid backup to save my hide (and my ui) when I go a-themin'.
For example, I just hacked up my framework-res to try to get rid of some horrible list separators, which of course completely broke the tablet. Power-N, restore from internal sd card, and I'm ready to break things again.
Thanks!
***UPDATE***
As of my latest post here I'm now semi-bricked I think
It's been ages since I last messed with my nook tablet and trying to remember all the little things is tough. Can someone help me boot into my CWM recovery? My goal here is to upgrade from CM7 to CM10. When I hold the Power Key + N button until the black screen with the N comes up. Then I let go of Power Key and remain holding the N key. Then the screen changes and asks me if I would like to factory reset my device (looks to be the internal boot menu and not CWM related).
What am I doing wrong?
Re: Boot into recovery
cartisdm said:
It's been ages since I last messed with my nook tablet and trying to remember all the little things is tough. Can someone help me boot into my CWM recovery? My goal here is to upgrade from CM7 to CM10. When I hold the Power Key + N button until the black screen with the N comes up. Then I let go of Power Key and remain holding the N key. Then the screen changes and asks me if I would like to factory reset my device (looks to be the internal boot menu and not CWM related).
What am I doing wrong?
Click to expand...
Click to collapse
Assuming you're using an internal flash you just wait for it to boot into cyanoboot. Hold down the n button to go to the menu and select recovery. Download the zip file and gapps files from where you want, but 12/31 is the final release.
datallboy said:
Assuming you're using an internal flash you just wait for it to boot into cyanoboot. Hold down the n button to go to the menu and select recovery. Download the zip file and gapps files from where you want, but 12/31 is the final release.
Click to expand...
Click to collapse
I keep holding N even while the factory reset screen is visible? Or do I go through the prompts to "factory reset" but it actually ends up taking me to CWM? I just didn't want to accidentally start factory resetting the device and end up bricking my tablet!
EDIT: Yes, it's an internal flash of CWM/CM7
EDIT 2: Just continuing to hold down the N key while the Factory Reset message is showing doesn't work
EDIT 3: I downloaded that Nook Tablet Recovery Flasher App. I flashed the latest CWM and it was all successful. I used the app to "Reboot into Recovery." When it reboots it goes to the initial N screen then it changes to a different N screen. The second N is a little bigger and has a more detailed gradient color on it. Then my screen goes black and nothing happens.
That recovery flasher app did nothing good for me. At all. If it did anything, it flashed CWM 5.x. wich was of no use to me!
While trying to get things to work I also invovled TWRP and then I was in deep trouble... Had to use the "repart.img" to get out of bootloop. Not saying this is what you have to do though. You're hopefully in better luck!
You could try a bootable CWM sd card instead to get into CWM and maybe go on from there.
Re: Boot into recovery
Don't hold down anything when the nook is turned on. Holding the button when it starts execute the factory reset. Wait for it to boot. If it boots to stock is then cwm is not internally installed. If it boots to cyanobot then hold down n button to go to menu and recovery. It will go to recovery.IMG.
So when you turn on the nook don't press anything. Wait to see what it does. If nothing then make the card for flashing cm10.
Blah, I think I bricked it somehow (or at least semi-bricked it). I can't get it to boot past this stupid N screen anymore. All I did was try to reboot into recovery again from that recovery flasher app but ever since then I can't get back into the OS. I'll probably have to dig into how to unbrick this tablet, bring it to stock, then get onto CM10. Any suggestions?
Powering on the device as normal brings me to the initial "N" screen then a new one comes up with a bigger N and then it eventually turns back off after about 5 seconds
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reflash stock with this repart.img
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Write the image to an SD card, put it in your nook and when the green check mark pops up take out the SD card.
I had great success with the repart.img that is used in this guide: http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Downloaded, burned the card, popped it in the Tablet, booted and kept my fingers crossed... Worked great for me!
datallboy said:
Reflash stock with this repart.img
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Write the image to an SD card, put it in your nook and when the green check mark pops up take out the SD card.
Click to expand...
Click to collapse
asawi said:
I had great success with the repart.img that is used in this guide: http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Downloaded, burned the card, popped it in the Tablet, booted and kept my fingers crossed... Worked great for me!
Click to expand...
Click to collapse
Well that was ridiculously easy to do. Thanks! I know have the tablet 100% back to stock and unrooted. I just need to track down idiot proof instructions on how to root and install CM10 and I'll be golden.
Thanks again!
I did this when I was a complete newbie. I wrote it down with the thought "if I can do it ANYONE can!"
It's not elegant, it's not sophisticated, but it works... (Kind of like me, come to think of it...)
http://forum.xda-developers.com/showthread.php?t=2081981
asawi said:
I did this when I was a complete newbie. I wrote it down with the thought "if I can do it ANYONE can!"
It's not elegant, it's not sophisticated, but it works... (Kind of like me, come to think of it...)
http://forum.xda-developers.com/showthread.php?t=2081981
Click to expand...
Click to collapse
Ended up going with Installing CM10 Internally on Nook Tablet but your guide looks great too. I'm now running CM10 and everything looks great so far with a few minor exceptions (youtube crashes for me and netflix won't play video but audio comes through)
cartisdm said:
Ended up going with Installing CM10 Internally on Nook Tablet but your guide looks great too. I'm now running CM10 and everything looks great so far with a few minor exceptions (youtube crashes for me and netflix won't play video but audio comes through)
Click to expand...
Click to collapse
YouTube crashes a lot with all the cm10+ versions. You can get better playback using the browser instead of the app though.
datallboy said:
YouTube crashes a lot with all the cm10+ versions. You can get better playback using the browser instead of the app though.
Click to expand...
Click to collapse
Interesting, that may be a problem. 99.99% of my tablet browsing consists of reading e-books, chatting on GroupMe, browsing reddit, and watching youtube videos. If YouTube is going to be a problem maybe I should find the best CM7 version out there and flashh
What ROM did you go with? I'm running Succulent's CM10 from Dec 31, from Iamafanof website. I haven't had any Youtube issues.
Not that I run Youtube much, so maybe I shouldn't say too much, but my little 8,5 year old buddy does a lot of Youtubing on her NT running the same setup and she hasn'r complained in the couple of months she has had it.
asawi said:
What ROM did you go with? I'm running Succulent's CM10 from Dec 31, from Iamafanof website. I haven't had any Youtube issues.
Not that I run Youtube much, so maybe I shouldn't say too much, but my little 8,5 year old buddy does a lot of Youtubing on her NT running the same setup and she hasn'r complained in the couple of months she has had it.
Click to expand...
Click to collapse
CM10.0 from Iamafanof:
http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/
CM10.0 Jellybean for Nook Tablet w/ 10-Touchs Driver (12/31) FINAL
cm-10-20121104-UNOFFICIAL-acclaim.zip
cartisdm said:
Interesting, that may be a problem. 99.99% of my tablet browsing consists of reading e-books, chatting on GroupMe, browsing reddit, and watching youtube videos. If YouTube is going to be a problem maybe I should find the best CM7 version out there and flashh
Click to expand...
Click to collapse
I'd suggest you first try un-install and re-install YouTube.
cartisdm said:
CM10.0 from Iamafanof:
http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/
CM10.0 Jellybean for Nook Tablet w/ 10-Touchs Driver (12/31) FINAL
cm-10-20121104-UNOFFICIAL-acclaim.zip
Click to expand...
Click to collapse
Good page, but don't use the build! Go with the newest one, 20121231!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
* Your warranty is now void.
Untested build. I don't have the device. Someone with some balls please make a back up and give this a try and get back to me.
Any root issues http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip
ROM: pulled
GAPPS: http://goo.im/devs/BaNkS/GApps%204.3
Thanks to the guys over at cyanogen, google, and uXylon.
Will have to give it a shot tonight
Sent from my SGH-I777 using Tapatalk 2
I flashed it, it booted into android fine but every time I selected start on the first setup screen it would reboot. Now I can't get into recovery, however I have a broken power button which might be causing complications. I'm working on getting back into recovery but this is an old phone so if I don't get it working, its no big deal.
s33d1ing said:
I flashed it, it booted into android fine but every time I selected start on the first setup screen it would reboot. Now I can't get into recovery, however I have a broken power button which might be causing complications. I'm working on getting back into recovery but this is an old phone so if I don't get it working, its no big deal.
Click to expand...
Click to collapse
Damn that is horrible. Power button doesn't work at all? Have you trye taking it apart and cleaning the contactors? What recovery do you have? Is there only one option? can you op to setup gapps later? You can always try using fastboot to get in there.
RBMacGregor said:
Damn that is horrible. Power button doesn't work at all? Have you trye taking it apart and cleaning the contactors? What recovery do you have? Is there only one option? can you op to setup gapps later? You can always try using fastboot to get in there.
Click to expand...
Click to collapse
I have taken the phone apart but I still couldn't get the power button to work. Anyhow, I just got everything restored and I'm going to try flashing it again. :laugh:
Okay, I just flashed the rom this time. It boots into android but when I try to open any app, the phone reboots.
s33d1ing said:
I have taken the phone apart but I still couldn't get the power button to work. Anyhow, I just got everything restored and I'm going to try flashing it again. :laugh:
Okay, I just flashed the rom this time. It boots into android but when I try to open any app, the phone reboots.
Click to expand...
Click to collapse
haha you have balls Ill give you that! Had me worried hate to brick someones device. Could you possibly logcat it? I think I need to change the tool chain compiling the kernel googles using 4.7 now and I'm not sure cyanogen is ready out of the box for it. Ill try with 4.6 tomorrow.
RBMacGregor said:
haha you have balls Ill give you that! Had me worried hate to brick someones device. Could you possibly logcat it? I think I need to change the tool chain compiling the kernel googles using 4.7 now and I'm not sure cyanogen is ready out of the box for it. Ill try with 4.6 tomorrow.
Click to expand...
Click to collapse
I cant get into settings to turn on usb debugging because the phone restarts every time I open settings. Is there any way to make a logcat in this situation?
s33d1ing said:
I cant get into settings to turn on usb debugging because the phone restarts every time I open settings. Is there any way to make a logcat in this situation?
Click to expand...
Click to collapse
See if you can download catlog and get the log that way for him.
Good luck.
Sent from the i777
I got a soft brick. Good thing I had a Jtag because I could not even get into download by button combination.
You may want to check and see if the i777 repo has even been updated to a useable state, as it had not been a few days ago when I last checked.
The kernel works but the ROM itself doesn't do much.
I have ported the CM 10.2 unofficial build pulled from GT-I9100 forum and I flashed it. All I can say is it worked fine but still is unstable..highly unstable. I used d default kernel and changed the modules and keypad script. It booted well and was fast. But phone heating issue and couple of FC's us what I encountered. And battery life issues.
Sent from my SGH-I777 using xda premium
AJ Newkirk said:
You may want to check and see if the i777 repo has even been updated to a useable state, as it had not been a few days ago when I last checked.
The kernel works but the ROM itself doesn't do much.
Click to expand...
Click to collapse
I had to make some changes to the i777 device tree to get it to build. Im gonna give it another go after work today.
twcobra said:
I got a soft brick. Good thing I had a Jtag because I could not even get into download by button combination.
Click to expand...
Click to collapse
**** soft brick? How the hell did that happen. Boot loader went off without a hitch.
RBMacGregor said:
**** soft brick? How the hell did that happen. Boot loader went off without a hitch.
Click to expand...
Click to collapse
Not sure what caused it. I had installed GAPPS with all the extras. Next time I try I will just install the ROM and the GAPPS core. Then the extra stuff one at a time. Believe me I started getting nervious when I could not get into download by button combo. I started breathing easy when I found my Jtag pluged it in and went rite to download on power up.
Anyone know why the rom was pulled?
Spinergy02 said:
Anyone know why the rom was pulled?
Click to expand...
Click to collapse
4.3.3 versions have TRIM Implementation ....and our devices aren't design for SSD overwrite deleted blocks
Sent from my SGH-M919 using xda premium
samprocat said:
4.3.3 versions have TRIM Implementation ....and our devices aren't design for SSD overwrite deleted blocks
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
TRIM would not be implemented on anything for our device. The SII version of CM10.2 and anything based off of CM10.2 trees would not contain TRIM.
I haven't made any calls but I sure hope I'm not having mic issues on 4.0 because voltage control is a really big deal to me and I don't want to upgrade.
Could someone explain why TRIM wouldn't be good for our devices?
RBMacGregor said:
**** soft brick? How the hell did that happen. Boot loader went off without a hitch.
Click to expand...
Click to collapse
I've had the same thing, doing pretty much nothing!
Fresh install, wiped everything, from system to memory card, plugged into USB transferring some files and BOOM, brick. Wipe again, reinstall, continue copying some files and brick again.
Needless to say I am sticking to 10.1 for a while longer.
Hi, I hope someone here has the know-how to help me out of the mess I've made for myself.
Okay, here's what I did:
1.) Accepted the KitKat upgrade.
2.) Ran qbking's autoroot thing. (It worked, thanks.)
3.) Flashed TWRP (I forget which version)
4.) Flashed Sac23's rom.
After the rom flash I was trapped in the 'boot-loop of death' where all powering my pone on
achieved was getting the "Samsung Galaxy Note 3" splash page & then rebooting, endlessly.
In a panic I flashed the "NAB Engineering bootloader tar file" I grabbed off ofhttp://forum.xda-developers.com/showthread.php?p=51165389 .
Now every time I power on I get the "Samsung Galaxy Note 3" splash page (again) a forced reboot and now get the message;
"Kernel Panic!
wait...
Done!
UDC START
KERNEL PANIC
UPLOAD MODE"
At which point it just plain freezes.
Is there anyone out there who tell me how (or IF it's even possible now) I can just get back to stock??
ANY help/opinion/advice would be seriously appreciated.
Flumpy said:
Hi, I hope someone here has the know-how to help me out of the mess I've made for myself.
Okay, here's what I did:
1.) Accepted the KitKat upgrade.
2.) Ran qbking's autoroot thing. (It worked, thanks.)
3.) Flashed TWRP (I forget which version)
4.) Flashed Sac23's rom.
After the rom flash I was trapped in the 'boot-loop of death' where all powering my pone on
achieved was getting the "Samsung Galaxy Note 3" splash page & then rebooting, endlessly.
In a panic I flashed the "NAB Engineering bootloader tar file" I grabbed off ofhttp://forum.xda-developers.com/showthread.php?p=51165389 .
Now every time I power on I get the "Samsung Galaxy Note 3" splash page (again) a forced reboot and now get the message;
"Kernel Panic!
wait...
Done!
UDC START
KERNEL PANIC
UPLOAD MODE"
At which point it just plain freezes.
Is there anyone out there who tell me how (or IF it's even possible now) I can just get back to stock??
ANY help/opinion/advice would be seriously appreciated.
Click to expand...
Click to collapse
You should check sacs rom for instructions on this issue, as the engineering bootloader isn't a fallback option to correct your inability to boot.
Please indicate the version of TWRP you're using, as knowing that will help. There's a chance that you are on the wrong version of TWRP, which could solve your issue.
You can always reflash stock NAB, flash TWRP, then the rom, which is pre-rooted.
Sent from my SM-N900P using Xparent BlueTapatalk 2
I've been in a similar situation. Pull the battery on the Galaxy Note 3 page. Then hold the necessary buttons to get into recovery before putting the battery back in. Keep them held while putting the battery in. If that doesn't help break the cycle then do the same thing (battery pull and hold necessary buttons down for Odin mode/download mode and keep them down while placing battery back in) till it hits the correct screen. Then reboot to recovery from there.
@micmars: Tnx for the speedy reply (guess all that ostuff I've seen people writing about you here @ XDA are true, you really ARE a benignly omnipotent kinda dood. )
I ended up flashing the stock NAB firmware (with TWRP 2.7.0.0). It was nice not being mocked by the 'Boot-Loop of Doom'. [for a heartbeat @ least. =\ =D ]
BUT THEN
I started the root process thing again;
1.) Ran "CF-Auto-Root..." (sorry for my earlier snafu [see first post] Chainfire/QbKing77.)
2.) Flashed TWRP 2.7.0
3.) And then reflashed sac23's rom.
& I'll be uh, darned, if it didn't launch back into the same *#&$! boot-loop again. (Just to be certain I was getting a good d/l, I RE-downloaded it to both my phone AND computer this time.) And still kept getting stuck in the same "Samsung Gal..." splash screen loop. =\
For grins & giggles I downloaded a different ROM (Toxic Swamp v1.0.2), ran through the root process, all was good until I flashed the rom and the SAME bootloop started up again.
Can anyone please tell me if I'm doing something screwy in my process or if maybe I pissed of a diety somewhere or something?
ANY advice/comment/good guess would be greatly appreciated.
Always remember, ->Pobody's nerfect.<-
Sent from my Sprint-flavored SM-900P (using the XDA app.)
Make sure your flashing roms that are 4.4.2 you can't use 4.3 roms toxic Swamp 1.0.3 is 4.3 .... There is no going back to 4.3 now
Sent from my SM-N900P using Xparent BlueTapatalk 2
Oh, and Tw1sted247, I tried the technique you mentioned (appreciate it) but it's not that I can't get into either Odin/recovery, it's that anytime I try to start my phone with anything other than stock it immediately starts in w/the merry-go-round from hell (boot-loop) thang.
->Pobody's nerfect.<-
Sent from my Sprint-flavored SM-900P (using the XDA app.)
OK, I'm Confused...
Flumpy said:
Oh, and Tw1sted247, I tried the technique you mentioned (appreciate it) but it's not that I can't get into either Odin/recovery, it's that anytime I try to start my phone with anything other than stock it immediately starts in w/the merry-go-round from hell (boot-loop) thang.
->Pobody's nerfect.<-
Sent from my Sprint-flavored SM-900P (using the XDA app.)
Click to expand...
Click to collapse
OK, I'm confused..which is my favorite stage of enlightenment, so thank you.
So, as has been asked by others, why would you flash a TouchWiz Jellybean 4.3 ROM (Toxic Swamp) built on MJ4 onto a TouchWiz KitKat rom built on NAB(D)? You really shouldn't do that, as it is inviting trouble across the phone's OS.
I would kindly ask that you boot your phone and show us the "About Device" page (not the one that has all of your personal info, as no one needs to see your MEID, &c). That will give us a start.
You may be looking at a complete overhaul of your device.
Be thankful that your phone booted up, and then ONLY flash the original NAB(D) tar or One-Click, then TWRP from PC Odin, and then inject root from recovery, using the latest Chainfire Superuser zip found here.
After that, we can block and tackle where you wish to arrive.
Okay, here's the requested screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Sprint-flavored SM-900P (using the XDA app.)
Or better yet:
Flumpy said:
Or better yet:
View attachment 2646244
Click to expand...
Click to collapse
I'm usually loathe to recommend a rom, but to recommend stock DeOdex or Odex, seems harmless enough, and it'll give us a clean slate. Looks like your completely stock.
We're going to take this on two phases, first to get you just recovery and root, then onto one of the stockish roms. It's weird, but so is your situation.
So, grab one of the two stockish NABD (we'll skip the NAB group), put it on your internal memory, but plan to use it later.
TWRP below,
https://www.dropbox.com/s/ptl8dyomprxxn0l/openrecovery-twrp-2.7.0.0-hltespr-4.4.img.tar
We'll get you no ads and some mods if you want, but for now, let's get you flashing something.
Superuser (goes on your phone, try internal storage),
https://www.dropbox.com/s/lbtuggkhqknm2ik/UPDATE-SuperSU-v1.93.zip
1. Flash recovery above from PC Odin, version 3.07 below,
https://www.dropbox.com/s/z2n10tjzmxlhaz4/Odin3 v3.07.zip
Power down phone completely, take off any case, install Odin, leave auto restart checked (why not?), hold power + volume down + home to go into download mode, hit volume up to confirm, then, have your fingers at the ready, you'll be holding home + volume up simultaneously, very soon, load the tar I gave into the PDA slot, once Odin confirms it's ready, click start on the computer, have your fingers ready, once it flashes and starts to power cycle, hit those two keys, and you're in recovery...
2. In recovery, flash the superuser zip I gave you, reboot...
Now stay on this awhile before proceeding to the stockish rom.
Please quote me when responding.
Good luck!
Sent from my SM-N900P using Xparent BlueTapatalk 2
D'oh!
First of all I'd like to thank micmars et al. for lending your knowlege, expertise and namely, PATIENCE as I floundered through a SIMPLE root/flash.
Just to give ya'll the skinny, i FinAllY did manage to install both TWRP 2.7 and Sac23's kk rom onto my Sprint Note 3.
-> To be honest, I'm nearly beyond belief happy/surprised that I didn't manage to kill the $#%@ thing! =] <-
micmars said:
I'm usually loathe to recommend a rom, but to recommend stock DeOdex or Odex, seems harmless enough, and it'll give us a clean slate. Looks like your completely stock.
We're going to take this on two phases, first to get you just recovery and root, then onto one of the stockish roms. It's weird, but so is your situation.
So, grab one of the two stockish NABD (we'll skip the NAB group), put it on your internal memory, but plan to use it later.
TWRP below,
https://www.dropbox.com/s/ptl8dyomprxxn0l/openrecovery-twrp-2.7.0.0-hltespr-4.4.img.tar
We'll get you no ads and some mods if you want, but for now, let's get you flashing something.
Superuser (goes on your phone, try internal storage),
https://www.dropbox.com/s/lbtuggkhqknm2ik/UPDATE-SuperSU-v1.93.zip
1. Flash recovery above from PC Odin, version 3.07 below,
https://www.dropbox.com/s/z2n10tjzmxlhaz4/Odin3 v3.07.zip
Power down phone completely, take off any case, install Odin, leave auto restart checked (why not?), hold power + volume down + home to go into download mode, hit volume up to confirm, then, have your fingers at the ready, you'll be holding home + volume up simultaneously, very soon, load the tar I gave into the PDA slot, once Odin confirms it's ready, click start on the computer, have your fingers ready, once it flashes and starts to power cycle, hit those two keys, and you're in recovery...
2. In recovery, flash the superuser zip I gave you, reboot...
Now stay on this awhile before proceeding to the stockish rom.
Please quote me when responding.
Good luck!
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Flumpy said:
First of all I'd like to thank micmars et al. for lending your knowlege, expertise and namely, PATIENCE as I floundered through a SIMPLE root/flash.
Just to give ya'll the skinny, i FinAllY did manage to install both TWRP 2.7 and Sac23's kk rom onto my Sprint Note 3.
-> To be honest, I'm nearly beyond belief happy/surprised that I didn't manage to kill the $#%@ thing! =] <-
Click to expand...
Click to collapse
You'll likely come to find over time that these devices are pretty much able to withstand almost anything you can throw at them.
You can brick for good if you do something insane like flash a bootloader from the wrong device or build, but that aside, you can create quite the bit of turmoil for yourself.
Either way, terrific news.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Anyone have a pair of these glasses and working on root access? Anyone interested? There are a group of us that would be really interested in finding a solution.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dvegaman said:
Anyone have a pair of these glasses and working on root access? Anyone interested? There are a group of us that would be really interested in finding a solution.
Click to expand...
Click to collapse
I have a pair of the FPV Drone Edition. Have side loaded a few apps. Haven't rooted since Galaxy S3 ( back on iPhone now) am interested to get this going
Hi !
It seems the rooting of intel devices follow the scheme:
-get bootimg
-patch it
-allow oem bootloader (voiding warranty and endangering future updates)
-flash the patched bootimg and pray
Is this correct or did i oversimplify or generalize too much or am i plain wrong, anyone ?
Greetings,
Ender
P.S. Greetings dvegaman
Bump.
Well, BUMP, goddamn
Just came across 2 pairs of these (BT-300s).
If the lack of interest in rooting is due to lack of hardware, reach out to me privately here on XDA; would happily donate one to kickstart some development efforts.
-jd
jdiegmueller said:
Just came across 2 pairs of these (BT-300s).
If the lack of interest in rooting is due to lack of hardware, reach out to me privately here on XDA; would happily donate one to kickstart some development efforts.
-jd
Click to expand...
Click to collapse
Bumping this one up. Have a new pair and looking to root to wake them up some.
Sent from my Moto Z (2) using Tapatalk
This may seem easy to others but I figured out how to do a factory data reset using ADB... something that would've helped when my BT-300 went into a boot loop last weekend...
***DO AT YOUR OWN RISK! NOT RESPONSIBLE FOR BRICKING, ETC..... (but it worked fine for me).
1. Install "minimal_adb_fastboot_v1.4.2_setup.exe" (google it and grab at your own risk) on your Windows PC.
2. Go to the BT-300 and:
a. Under Security allow unknown sources
b. Under Developer Options allow USB debugging and unlock bootloader.
3. Connect same powered up BT-300 to PC via USB cable.
4. Start up that minimal ADB program. It will open in command prompt.
5. Check connection by typing "adb devices"
Should see "EMBT3C device" on PC
6. Now type, "adb reboot recovery" and wait for android with triangle/exclamation point to appear after device reboots. You will notice the physical buttons flash purple too.
7. Press and hold power button. Also press Vol Up, then release Vol Up and finally release Power button.
You should now see the recovery menu including "wipe data/factory reset", cache clear, and so on...
NOW... if I could get recovery.zip image to restore if I "kill" it to reload with ADB... THEN I'd try root. There must be a way. I just want GApps 5.1.1 on the thing for starters.
Still struggling with rooting... No dice so far. I've never rooted any Android... Once rooted can we then save the original factory ROM someplace safe, or do I need that first from another source? Newbie questions . I know just enough to be dangerous! LOL.
I got the factory image
Played around with the "SoftwareUpdate" apk and found the strings it uses to download the 1.4
Ugh just signed up but because I don't have enough posts I had to put a bunch of spaces in the links for them to
show up. Just remove the spaces and they should work? Either his or copy the SoftwareUpdate.apk and pull the strings from that.
ht tps:// download.ebz.epson.net /dsc /du /04 /SecureUpdateInfo ?PRN=BT-300&CTI=80&OSC=ARD&SCD=H756EMBT3C&SID=012345
You download a file called "SecureUpdateInfo" open it in a text editor and it will give you a link to the direct download for the zip. Its about 300megs. I have been playing with the boot options, but keep crashing it on boot and having to restore. I found 4 test pins that may be a serial port, but its 1.8 volt so I need to build something
PS - It might com back without a link but "BUSY" on it. I have been testing it a bunch so thats what happened right now. The fille will look like below
Code:
; secure update information
[BT-300;]
Version=R1.4.0
Size=371659424
Location= ht tps:// download.ebz.epson.net/ dsc/check/ 01/ GetFile. php ?PATH=xxxxxxx/OTA-R1.4.0.zip&KEY=lt1fs0DK
DownloadNumber=11474485
LALocation1=h ttp:// download.ebz.epso n.net/ dsc /hmd_license /EULA.zip
Erodros said:
Played around with the "SoftwareUpdate" apk and found the strings it uses to download the 1.4
Ugh just signed up but because I don't have enough posts I had to put a bunch of spaces in the links for them to
show up. Just remove the spaces and they should work? Either his or copy the SoftwareUpdate.apk and pull the strings from that.
ht tps:// download.ebz.epson.net /dsc /du /04 /SecureUpdateInfo ?PRN=BT-300&CTI=80&OSC=ARD&SCD=H756EMBT3C&SID=012345
You download a file called "SecureUpdateInfo" open it in a text editor and it will give you a link to the direct download for the zip. Its about 300megs. I have been playing with the boot options, but keep crashing it on boot and having to restore. I found 4 test pins that may be a serial port, but its 1.8 volt so I need to build something
PS - It might com back without a link but "BUSY" on it. I have been testing it a bunch so thats what happened right now. The fille will look like below
Code:
; secure update information
[BT-300;]
Version=R1.4.0
Size=371659424
Location= ht tps:// download.ebz.epson.net/ dsc/check/ 01/ GetFile. php ?PATH=xxxxxxx/OTA-R1.4.0.zip&KEY=lt1fs0DK
DownloadNumber=11474485
LALocation1=h ttp:// download.ebz.epso n.net/ dsc /hmd_license /EULA.zip
Click to expand...
Click to collapse
I am both impressed with your progress and baffled why I after I download SecureUpdateInfo I can't get to the zip file. Grrrrrrr.
chuck1026 said:
I am both impressed with your progress and baffled why I after I download SecureUpdateInfo I can't get to the zip file. Grrrrrrr.
Click to expand...
Click to collapse
Is the link in the in the secureupdate? I don't know if the strings encode the serial number in some why or if epson is reading this thread
I can pm you a link for the file if you can't get it
Erodros said:
Is the link in the in the secureupdate? I don't know if the strings encode the serial number in some why or if epson is reading this thread
I can pm you a link for the file if you can't get it
Click to expand...
Click to collapse
Yes, pm me the link. Thanks
Sent from my Moto Z (2) using Tapatalk
chuck1026 said:
Yes, pm me the link. Thanks
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
Ok sending now.
I also managed to root my epson! I discovered the twrp.img here:
https://forum.xda-developers.com/android/development/root-tutorial-intel-atom-cherry-trail-t3468330
If you get into bootloader mode and fastboot flash it into the recovery partition, you can adb root it and then install supersu from there. I just trashed my device though so be sure to do a full image backup first haha.
Erodros said:
Ok sending now.
I also managed to root my epson! I discovered the twrp.img here:
https://forum.xda-developers.com/android/development/root-tutorial-intel-atom-cherry-trail-t3468330
If you get into bootloader mode and fastboot flash it into the recovery partition, you can adb root it and then install supersu from there. I just trashed my device though so be sure to do a full image backup first haha.
Click to expand...
Click to collapse
You trashed it? What did ya load after root to crash it?
chuck1026 said:
You trashed it? What did ya load after root to crash it?
Click to expand...
Click to collapse
Tried to load up opengapps, then every time I rebooted it would be "optimizing apps" I tried to side-load the OTA again and poof, it killed the system partition.
The ota apparently doesn't have the full image. Right now I am trying to hack together something from another cherry rom and side load it, but I need a DD of someones system Glad twrp still works or I wouldn't have shell root access to fix.
Erodros said:
Tried to load up opengapps, then every time I rebooted it would be "optimizing apps" I tried to side-load the OTA again and poof, it killed the system partition.
The ota apparently doesn't have the full image. Right now I am trying to hack together something from another cherry rom and side load it, but I need a DD of someones system Glad twrp still works or I wouldn't have shell root access to fix.
Click to expand...
Click to collapse
You tell me how to share a pure factory image of mine (I'll gladly do an FDR for the cause)... and I'll share with ya!
chuck1026 said:
You tell me how to share a pure factory image of mine (I'll gladly do an FDR for the cause)... and I'll share with ya!
Click to expand...
Click to collapse
Ok I am retarded. I didn't configure twp correctly so all the folders it had were wrong. So when I went to use the install tool it screwed up majorly.
Just glad I didn't overwrite the bootloader
PS - Ok, I figured out how to restore the original recovery loader and it recovered fine. It must be something in this hacked version of twip that isn't applying the ota correctly. Going to try to build a version of twip just for this
Erodros said:
Ok I am retarded. I didn't configure twp correctly so all the folders it had were wrong. So when I went to use the install tool it screwed up majorly.
Just glad I didn't overwrite the bootloader
Click to expand...
Click to collapse
You are not. I am the noob trying to figure out the whole root process and I don't even know how to backup the existing bootloader and ROM so I can restore it with ADB if I screw it all up in root..... I feel clueless and know just enough to be dangerous... yet for some reason, I'm not afraid, just need to learn.
chuck1026 said:
I am both impressed with your progress and baffled why I after I download SecureUpdateInfo I can't get to the zip file. Grrrrrrr.
Click to expand...
Click to collapse
Whew! I did it. First I took the instructions from here as a start:
https://forum.xda-developers.com/android/development/root-tutorial-intel-atom-cherry-trail-t3468330
In fact, if you can "almost" follow the instructions verbatim. The problem is that the data drive is encrypted and the default android password didn't work so I had to modify the boot.img to not encrypt the data partition then do a wipe. supersu installed fine then.
As for gapps, that was tricky. You have to manually install google webview apk as the built in one is garbage.
Still working on the vr settings. Camera has issues with scaling as I think good believes it to be a widescreen when its a 4.3.
Once I get it down, I will make a boot.img and recovery.img that should just work.