Related
Hello XDA!
I opened a new thread hopefully to open a discussion about improvements I think are beneficial, my experience over the last 24 hours that a couple sticky edits would have saved me (and others) time.
My Story:
Yesterday (5/3) I saw I had around a 250 mb OTA. Excited (hoping for 4.2, assuming was the 4.1.2 that VZW released recently) I kick on WiFi, download and watch as it reboots and appears to install successfully. Time for work to end, grabbed phone off charger as it appeared to be rebooting after successful install, and ran out to catch train home.
Downstairs, at train stop, take a look at phone and heart sinks as it is in a fast splash screen loop, blinking the VZW Galaxy Note 2 screen for about 1 second in endless loop. As I had never seen before was thinking firmware update bricked it and I was looking at least until Tuesday before I'd have a working phone. Luckily, I was able to quickly see that I could still get into download mode, so knew I was (likely) going to be ok.
Get home and a Quick Robin, to the Internetz! later I'm browsing XDA and following the t=t=2024207 walkthu to restore stock. FYI, my device prior to the failed OTA was unrooted stock. At this point I'm not sure if it's going to restore, so I'm trying to do the true stock, no unlocked bootloader in case it has to be RMA'd. I've downloaded all my files, waited patiently for the slow hosting service for the FXZ(?) to download and am grinding through it and of course it fails at the system.img. Luckily, blessedly the awesome community here had released the image that included the unlocked bootloader which I was (after waiting to download, etc etc again) able to successfully get installed via Odin, booted up and working successfully.
So, while the first post section regarding restore to stock does indicate users with latest firmware "L4 OTA Only" shouldn't be attempting to use the Official VRAL I didn't think it applied to me. I would say that a fair amount of individuals looking to take the drastic step of a full restore to stock might be in a scenario like mine, where something significant has happened and likely confirming what OS/firmware/etc you are on might not be feasible. In my case, I assumed never rooted/unlocked vanilla device should be about as receptacle to an "official" restore as any. In this scenario, where a 100% for all devices stock recovery ("alternative") works, 'I feel that it should have been pushed harder than the official or at least blurbed with if you don't know what you are on, use this' While I understand that it is the "official" image, it has requirements for it to work. A co-worker had an ASUS TF300T that tried pushing a recovery image for ICS after he had upgraded to JB and it hard bricked his tablet, with ASUS wanting to charge him about 60% cost of the tablet to replace motherboard. That's heartbreaking, and I am sure since a hard brick wasn't a likely scenario here, why it wasn't mentioned.
Also: The download link for the Alternate Restore lists the file as: I605_VRALJB_Restore.tar.md5.xz which requires that it be unpacked using 7zip AND also that once extracted, it needs to be renamed to kick of the extra extension md5 in order for ODIN to see it properly as a PDA image file. (I605_VRALJB_Restore.tar.md5 ) Neither step is mentioned in the original post, and I had to read through to I believe the 11th page or so before realizing that was the problem. I'm sure with most of the people that are daily users of this forum knew automatically that these steps were required, but I would counter that a thread explaining how to restore Stock is one of the few threads that is likely to reach a larger, inexperienced demographic who would need to know such details.
Lastly, since (I thought) I had an unlocked bootloader, but otherwsie working phone again (Thank you, thank you thank you!) might as well get it rooted, and grab a ODEX'd stripped ROM with the OS release because getting the Software Update nag and not being able to complete or even brick my phone makes my OCD gland flex mightily. Was delighted to see an on-device APK root option which threw me back to the ease of z4root a few years ago with my Droid X. APK installs, and it roots so easily, like it had the functionality out of the box. I grab goo.im manager and install TWRP. Go to boot into custom recovery so I can install my sexy updated OS ROM and enjoy my fun device without all the yucky bloatware I've just ignored/dealt with for the last 2 months and I get the dreaded and in my opinion illegal "VZW unauthorized software" software brick.
Back to the forums, see I need another stock 'alternative' restore to fix AND a little confused, but believe I need to run a "jailbreak" bootloader unlock (CASUAL ?t=2118348) Which I haven't done yet. I have all files downloaded, just paused to post my experiences here.
So, this was main reason for my post, as I can understand some of why walkthru is laid out the way it is above, but why not have this included as part of the stickied root walkthru? It's mentioned thusly:
section 1a is a old method and no longer needs to be used unless the end user wants root only. proceed to Adam Outler's "JAILBREAK" thread linked at the bottom of this section for rooting and unlocking bootloader so custom roms can be flashed!!!
Click to expand...
Click to collapse
I couldn't find the link it refers to at bottom of section? I ended up googling to find guide. ((t=202420)
if this is still a requirement for root, custom ROM/Recovery, I would have made this steps 1-x of the root guide. is it because another person authored it? It would be nice to be able to credit and quote, I know alot of what drives contributors is the 'Thanks" and Donations, be great if XDA admins could round table and find a solution that allows for a consolidated guide for each device and still give each contributor a way to get their +1's and plug donation/web/twitter handle url's
So, is my understanding incorrect of what is needed or do folks agree with me that current setup is not the most efficient way XDA community could be offering instructive guides on Root/Mods? It would be wonderful if XDA Mods upon announcement of devices, when creating the forum threads for device (Development, OG Development, General, etc etc) created a blank thread for the how to root et.al and then allowed it to be edited by the community as a Wiki. Or even if an individual created, allow that person to allow x amount of other community members to edit, add and adjust.
I see droidstyle created a thread about questions for softbrick, and I might have to look at the original sticky thread about how to stock restore, but it seems he/she might have better saturation if this info was included in the original post. The stickied How To recover stock is direct accessible from a google search. I doubt his Q&A thread is or definitely not going to be one of the highest page-ranked sites.
So, please let me know if I'm just out of my mind, off the mark. I will give myself a small escape clause based on the fact that I probably scored about 2 hours of sleep last night messing around trying to get the note running again. I am actually concerned that the instructions for Return to Stock/Root/Etc for the VZW i605 doesn't have the link to unlock bootloader via casual and am hoping that following that process before rooting/customrecovery/ROM is correct, and not going to be another BrickGate for me. I know as OS versions are updated and/or Big Red and Big Blue constantly push patches trying to lock people out of their phones that instructions change and methods break. As new directions are implemented it's easy to lose steps as edits occur on the fly.
Most importanly! I hope this thread comes across as constructive criticism/suggestions, I have nothing but the highest respect for this community and it's contributors. Even skewed, outdated and conflicting information is better than no information and I SUPER appreciate the hard work required to get it out to us. I am most definitely not expressing displeasure with my experience or the content, only using the threads I mentioned as examples of what I personally see as opportunity for improvements XDA could implement that would allow for easier dissemination of the information the community is sharing so unselfishly. I only open it for discussion, so that others like me can access the information quicker with less confusion. I read comments of disgust and exasperation as people are directed to search, rather than post, and they are right, the information is invariably there, and most often or not within the first 5 posts of a thread. But sometimes when a developer talks to another developer, the tiny and considered minor details are not mentioned because it's considered common knowledge, and thats where the noobs, soccer moms and Grandmas can get left scratching their heads trying to puzzle how you got from point a to b. (Stereotypes used for comedic effect, please take no offense) I believe it would save alot of people having to answer the same questions over and over again time and frustration and freeing them to focus their talents on making us the next epic ROM/Kernel/App
thanks for reading! Also, I'm not just drive-by b*tching, if anyone is interested, I would love to show a mock-up of the i605 guide these great contributors have created as I would compile it. I'm passionate about mobile technology and customization, sadly my talents don't lie in the creation of such, only the enjoyment of it. But I'm a hell of a document admin. I create wiki's and KB's/sharepoint admin for a living, and would love to contribute what I know in that way
Being newly interested in rooting and tweaking my devices (started with my S3) there are a lot of terms that are mentioned in customizing threads that I do not understand, and a lot of those threads don't have detailed instructions for someone that's new to tweaking. Is there one post somewhere on xda that lists terms, methods, etc for newcomers like me?
I don't trust any forum other than xda because I simply think its the best forum for tweaking, etc so I don't really trust links outside xda. I also know that the way some things need to be done is device specific.
I'm confused about how to "flash" something in "recovery' (such as removing the wifi notification thread), flashing a custom recovery, using Goomanager to flash, etc. Don't get me wrong; I can follow detailed instructions as long as they are there......but if they aren't, that leaves me and a great deal of newcomers in the dark.
Some of these things are done via the phone and some have to be done via PC....and many times there aren't detailed instructions so I'm unsure what I an supposed to do and don't want to brick a $700 device.
So....is this information contained in all separate posts throughout the forum? Or is there one thread per device that details it? Being as some of these things are device specific, I'm hesitant to even look in other device forums.
Thanks for reading, and any assistance is appreciated.
wolfgrrl said:
Being newly interested in rooting and tweaking my devices (started with my S3) there are a lot of terms that are mentioned in customizing threads that I do not understand, and a lot of those threads don't have detailed instructions for someone that's new to tweaking. Is there one post somewhere on xda that lists terms, methods, etc for newcomers like me?
I don't trust any forum other than xda because I simply think its the best forum for tweaking, etc so I don't really trust links outside xda. I also know that the way some things need to be done is device specific.
I'm confused about how to "flash" something in "recovery' (such as removing the wifi notification thread), flashing a custom recovery, using Goomanager to flash, etc. Don't get me wrong; I can follow detailed instructions as long as they are there......but if they aren't, that leaves me and a great deal of newcomers in the dark.
Some of these things are done via the phone and some have to be done via PC....and many times there aren't detailed instructions so I'm unsure what I an supposed to do and don't want to brick a $700 device.
So....is this information contained in all separate posts throughout the forum? Or is there one thread per device that details it? Being as some of these things are device specific, I'm hesitant to even look in other device forums.
Thanks for reading, and any assistance is appreciated.
Click to expand...
Click to collapse
Well, this can be a complex arena to play in. For the S4, you'll want to download Odin v3.07 and a copy of the stock ROM just in case you break something.
> http://forum.xda-developers.com/showthread.php?t=2289325
> http://forum.xda-developers.com/showthread.php?t=2189539
ROM = read-only memory - this is the part of your phone's internal storage you're not really supposed to be able to play with (like /system, or the phone's radio for example)
The act of "flashing" is writing data to ROM
Recovery just means that you should always be able to boot your device into this mode to RECOVER from a software problem; IE: flashing a bad ROM (IE: one that doesn't work and you can't start your phone anymore).
I don't really know a whole lot more than that, I just poke around and pretend like I do =)
OverkillSD said:
Well, this can be a complex arena to play in. For the S4, you'll want to download Odin v3.07 and a copy of the stock ROM just in case you break something.
> http://forum.xda-developers.com/showthread.php?t=2289325
> http://forum.xda-developers.com/showthread.php?t=2189539
ROM = read-only memory - this is the part of your phone's internal storage you're not really supposed to be able to play with (like /system, or the phone's radio for example)
The act of "flashing" is writing data to ROM
Recovery just means that you should always be able to boot your device into this mode to RECOVER from a software problem; IE: flashing a bad ROM (IE: one that doesn't work and you can't start your phone anymore).
I don't really know a whole lot more than that, I just poke around and pretend like I do =)
Click to expand...
Click to collapse
Thanks As I learn more, I think I'm going to make a post that contains everything I learn, so others have it all in one place.
Well, there's a LOT to learn...like I said; complex arena. So much so that there's no way to make a single post take you from newbie to knowledgeable newbie in one read.
Then there's Google;
"what is rom"
"what is flashing rom"
"what is recovery mode android"
Eliminates the need for said post
Plus, by the time you get it all written, it will have all changed ^_^
I just recieved a replacement Unit for my malfunktioning HDX 9.8. Current version on this thing is 14.3.0.2_user_302075320. I have just started it up to check the version and have not yet registered it or even connected it to a network. This time around I would like to be in control of things! What would be the appropriate thing to do with this version, if I want to :
1. Root it and keep it from auto-updating.
2. getting it safestrapped to be able to...
3. ...flash custom roms safely in the future,
Ive been looking around these forums to find out myself but information is scrambled and depending on version numbers and other things. The learning curve sure is steep here
/sebastian
My humble suggestion is to install TWRP (here) followed by the ROM of your choice. Each has pros/cons....stock is also an option. You will need to do some reading, plan carefully and be prepared for the unexpected. Keep that pup in 'airplane' mode to prevent debilitating OTA updates until you identify and apply an appropriate blocker. I think you will find the community quite willing to help with specific questions but you probably won't get a start-to-finish recipe. Lots of reading ahead but the rewards are worth it IMO. Good luck!
Thanks for the reply! Good to hear that airplane mode can be a temporary update blocker! I'll do some more reading up on TWRP to begin with then.
Device Manager said:
Thanks for the reply! Good to hear that airplane mode can be a temporary update blocker! I'll do some more reading up on TWRP to begin with then.
Click to expand...
Click to collapse
Be carefull and dont use airplane mode to block updates while in stock! At least one user reported that amazon can update your kindle even with airplane mode on! If you setup your wifi already, just turn-off / forget your wifi while in stock, or use OTA blocker ...
Forgetting all WiFi networks is good advise indeed! I have seen Kindle readers pop out of airplane mode on occasion; suppose the same could happen on Fire/HDX tablets although I have not personally experienced this. OTA blocker is great (what I use) but obviously requires root.
OK, thanks everyone!
I'm good so far! I first rooted with towelroot then went for the toolkit. Installed the ADB drivers, then SU, then OTA blocker. After that I Installed safestrap, made a backup and a new rom-slot, to which I restored the recovery. So now I should be OTA blocked and have a stock ROM recovery option. I hope I haven't made any terrible mistakes yet
I'm a happy camper! (as of yet
Now I will do som reading up on HDXposed and custom roms I guess. Does anyone have any suggestions? Is the Nexus rom a good option?
Thanks again!
Ok Iplayed around some and read up some more. Now I can definitely see the benefits of going for the custom recovery! I have a few remaining questions about the specifics about flashing TWRP that I cant seem to find the answer to. Hope somewone would be kind enough to help or point me in the right direction.
Do I need to uninstall safestrap before (or after) flashing TWRP?
Is "Copy image to SD-card root" the same as copying it to the device file system root? As in draging and dropping in windows perhaps?
What is the tool for issuing the commands mentioned in the TWRP install guide? (I have used ADB but only via the Toolkit aplication and I havent seen a command prompt for this around).
Sorry for lacking in some fundamentals on this... (being a noob on android stuff)
Never mind the above. All sorted. Up and running HDX Nexus 2.0.5. Great stuff!
Hi there,
I've been cruising these forums for a while and have managed to root my device, get adb setup, and TWRP installed. An unfortunate bit seems to be that you cannot leave TWRP installed and actually boot the device. I managed to get stuck in a boot loop having not restored the 5.4.1 bootloaders. I turned the device off and rebooted into TWRP, flashed the 5.4.1 bootloaders, rebooted, and I'm golden. However, this doesn't really get me anywhere.
So my goal here is to just wipe all this FireOS crap and turn this tablet into a normal android tablet. I've seen plenty of posts about it but cannot seem to find any single post that would achieve this for my specific device and software version. So I'm coming here for help.
Mostly, what I have done so far has come from this thread: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Unfortunately, from what I can tell, this process does not remove FireOS and replace it with stock Lollipop, it just updates you to 5.1.2 (which I'm already at) and installs GAPPS. It does not really have a "pure" Android install and it somehow retains the FireOS as the primary OS.
Now, please correct me if I am wrong here with any of the above (this is not a hobby of mine) but since I've rooted a few devices before I figured I could handle it. It seemed like a bargain getting this Fire HD 7 used for like $64... if only I can get it onto stock Android. I'm basically trying to make it a Nexus 7.
Since I CAN get into TWRP, I figure I should just be able to flash a custom ROM right? I've just been having a really hard time finding a stock Lollipop ROM specifically for my device. From what I've heard, flashing the new ROM is the most error-prone part of this type of stuff and can totally brick the device if it were not meant for it. If that did happen, I would need to be able to boot the device back up, get an adb connection, run the scripts that flash the correct bootloaders (post #2, section 101, from the link above) so I can reboot into TWRP and fix it. Perhaps understandably so, I've been very hesitant to just go trying things willy-nilly that I don't fully understand.
Could anyone offer any assistance? Perhaps just point me in the right direction? I've probably read most of the threads you'll likely link, so a short bit of context to how something pertains to my specific device as well as the link could help me significantly. The guides that people write usually contain updates and are quite difficult to follow to the "T" and half the time I'm not even sure something I'm doing actually pertains to my device.
[EDIT] I found this video (https://www.youtube.com/watch?v=_c5hHSCO_o8) but it looks like he's doing that on a previous generation Fire so, again, I'm not sure it will work and don't want to try and then brick it.
nedwards said:
Hi there,
I've been cruising these forums for a while and have managed to root my device, get adb setup, and TWRP installed. An unfortunate bit seems to be that you cannot leave TWRP installed and actually boot the device. I managed to get stuck in a boot loop having not restored the 5.4.1 bootloaders. I turned the device off and rebooted into TWRP, flashed the 5.4.1 bootloaders, rebooted, and I'm golden. However, this doesn't really get me anywhere.
So my goal here is to just wipe all this FireOS crap and turn this tablet into a normal android tablet. I've seen plenty of posts about it but cannot seem to find any single post that would achieve this for my specific device and software version. So I'm coming here for help.
Mostly, what I have done so far has come from this thread: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Unfortunately, from what I can tell, this process does not remove FireOS and replace it with stock Lollipop, it just updates you to 5.1.2 (which I'm already at) and installs GAPPS. It does not really have a "pure" Android install and it somehow retains the FireOS as the primary OS.
Now, please correct me if I am wrong here with any of the above (this is not a hobby of mine) but since I've rooted a few devices before I figured I could handle it. It seemed like a bargain getting this Fire HD 7 used for like $64... if only I can get it onto stock Android. I'm basically trying to make it a Nexus 7.
Since I CAN get into TWRP, I figure I should just be able to flash a custom ROM right? I've just been having a really hard time finding a stock Lollipop ROM specifically for my device. From what I've heard, flashing the new ROM is the most error-prone part of this type of stuff and can totally brick the device if it were not meant for it. If that did happen, I would need to be able to boot the device back up, get an adb connection, run the scripts that flash the correct bootloaders (post #2, section 101, from the link above) so I can reboot into TWRP and fix it. Perhaps understandably so, I've been very hesitant to just go trying things willy-nilly that I don't fully understand.
Could anyone offer any assistance? Perhaps just point me in the right direction? I've probably read most of the threads you'll likely link, so a short bit of context to how something pertains to my specific device as well as the link could help me significantly. The guides that people write usually contain updates and are quite difficult to follow to the "T" and half the time I'm not even sure something I'm doing actually pertains to my device.
[EDIT] I found this video (https://www.youtube.com/watch?v=_c5hHSCO_o8) but it looks like he's doing that on a previous generation Fire so, again, I'm not sure it will work and don't want to try and then brick it.
Click to expand...
Click to collapse
You seem to have the gist of it, which is that what you want to do can't be done. There is only one ROM for this device--CM11, here: http://forum.xda-developers.com/fire-hd/orig-development/rom-cm-11-kindle-hd6-t3270138 --and it is not fully working. No one's ever posted here about successfully installing a ROM for a different device, only about bricks as a result of trying.
@xSentinel has been disabling all possible apps, while still keeping the device running. His goal may be the same as yours(?). He started a thread here, but has since got a lot more disabled: http://forum.xda-developers.com/fire-hd/help/5-1-2-bloatware-safe-to-remove-apps-2014-t3355167. Might want to post there and see what he's up to.
DoLooper said:
You seem to have the gist of it, which is that what you want to do can't be done. There is only one ROM for this device--CM11, here: http://forum.xda-developers.com/fire-hd/orig-development/rom-cm-11-kindle-hd6-t3270138 --and it is not fully working. No one's ever posted here about successfully installing a ROM for a different device, only about bricks as a result of trying.
@xSentinel has been disabling all possible apps, while still keeping the device running. His goal may be the same as yours(?). He started a thread here, but has since got a lot more disabled: http://forum.xda-developers.com/fire-hd/help/5-1-2-bloatware-safe-to-remove-apps-2014-t3355167. Might want to post there and see what he's up to.
Click to expand...
Click to collapse
Ah, that is unfortunate. At least you've helped me to understand that my goal cannot be fully realized. I probably should have done a bit more research before purchasing the Fire tablet. I'm really just looking to set up an in-car tablet to handle Torque guages, navigation, and music. Perhaps I should just return the Kindle and shell out the extra cash for a Nexus 7. I think I could probably get a refurbished one for a price similar to what I paid for the Fire. I'll poke around xSentinel's thread a bit and see what I'm up against first though. If it comes down to it, the headache of dealing with Amazon's locked down devices might just outweigh the extra money/hassle of a Nexus 7 and a return.
nedwards said:
Ah, that is unfortunate. At least you've helped me to understand that my goal cannot be fully realized. I probably should have done a bit more research before purchasing the Fire tablet. I'm really just looking to set up an in-car tablet to handle Torque guages, navigation, and music. Perhaps I should just return the Kindle and shell out the extra cash for a Nexus 7. I think I could probably get a refurbished one for a price similar to what I paid for the Fire. I'll poke around xSentinel's thread a bit and see what I'm up against first though. If it comes down to it, the headache of dealing with Amazon's locked down devices might just outweigh the extra money/hassle of a Nexus 7 and a return.
Click to expand...
Click to collapse
You also might check out the Fire forums. (I got a refurb for $30.) They have a few ROMs and are doing interesting things. Also, lots of activity over there.
Some people may strive to be "purists", but remaining pragmatic is a recipe for relatively happy life
Because the bootloaders are locked, there are very limited options on what to boot. There was some lucky bug in the earlier bootloaders that gifted us with the ability to boot an unsigned TWRP using 4.5.3 bootloaders. But boot.img always had to be signed, or it would not boot.
To create a custom OS, one needs to match the custom ROM to the existing boot.img from a given version of FireOS. Kind of pain in the @ss, don't you agree ?
Instead, however, one can just keep FireOS 5, and tweak it to behave like almost a pure Android. And it's not hard ! So why chase the unicorns when all you want is right in front of you !
I'm currently working on completing a CM11 port - as someone else mentioned it needs to use the stock boot.img though, so I have to heavily modify CM code in order to get it to work with full functionality. CM11 does run very well on the device though, and it's much snappier than Fire OS imo.
In theory this device could use something like safestrap to boot unsigned boot images, however I probably won't bother writing something like that until I have CM11 at 100% functionality (currently my build is at about 60% if I were to estimate).
I think the guy who posted the first CM11 port is now working on porting CM12, although it's a massive pain to test.
nedwards said:
Ah, that is unfortunate. At least you've helped me to understand that my goal cannot be fully realized. I probably should have done a bit more research before purchasing the Fire tablet. I'm really just looking to set up an in-car tablet to handle Torque guages, navigation, and music. Perhaps I should just return the Kindle and shell out the extra cash for a Nexus 7. I think I could probably get a refurbished one for a price similar to what I paid for the Fire. I'll poke around xSentinel's thread a bit and see what I'm up against first though. If it comes down to it, the headache of dealing with Amazon's locked down devices might just outweigh the extra money/hassle of a Nexus 7 and a return.
Click to expand...
Click to collapse
Just so you know it can be done, I am running Torque on a Fire HD 6 and still running thr Fire O.S. There is also a similar app to Torque Pro in the Amazon app store - search for OBD and it should see it (sorry I can't give the name, soft bricked the device and won't be near a computer for another 4 days) It is similar in capabilities to Torque Pro, and runs around the same price.
Hi, I am new here, but have recently gotten into rooting phones etc, but my knowledge base is still Novice at best. I have an AT&T Optimus G that was rooted and had CWM, Free G and Kitkat. Long story short, a co-worker who claimed to know what they were doing has reset my phone, wiped my external sd card and totally factory reset my phone. When I turn it on now ClockworkMod Recovery comes on, but all of my back ups etc have been wiped. I am assuming that it is now just a machine with no info on it. What do I do now? I'm sure that the answer to this will be very involved so if anyone could possibly suggest a thread to read or somewhere to start I would greatly appreciate it. I'm sorry for the inconvenience guys...
The google account that this was linked to is my current one so no issues with reset protection once it gets running or what not. Any info I can provide on my end if need be feel free to let me know. I know one of the specifics to the device was: geefhd???
Here is the current update: Android 4.4.2 KitKat
The details
Release date: September 29, 2015
Android version: 4.4.2
Baseband version: APQ8064/MDM9x15M
Kernel version: 3.4.0
Build number: KOT49I.E98020i
File size: 9.47MB
Software version: E98020i
EMT803 said:
Hi, I am new here, but have recently gotten into rooting phones etc, but my knowledge base is still Novice at best. I have an AT&T Optimus G that was rooted and had CWM, Free G and Kitkat. Long story short, a co-worker who claimed to know what they were doing has reset my phone, wiped my external sd card and totally factory reset my phone. When I turn it on now ClockworkMod Recovery comes on, but all of my back ups etc have been wiped. I am assuming that it is now just a machine with no info on it. What do I do now? I'm sure that the answer to this will be very involved so if anyone could possibly suggest a thread to read or somewhere to start I would greatly appreciate it. I'm sorry for the inconvenience guys...
The google account that this was linked to is my current one so no issues with reset protection once it gets running or what not. Any info I can provide on my end if need be feel free to let me know. I know one of the specifics to the device was: geefhd???
Click to expand...
Click to collapse
Since your phone has been wiped, you are going to have to re-install your ROM either via LGNPST, which will return your phone to stock, or you will need to install your favorite custom ROM via adb sideload.
If going back to stock via LGNPST refer to FAQ Number 3 here http://forum.xda-developers.com/showthread.php?t=2006946
If installing custom rom via ADB Sideload refer here http://www.droidviews.com/sideload-roms-mods-using-adb-sideload/
Kilogrm said:
Since your phone has been wiped, you are going to have to re-install your ROM either via LGNPST, which will return your phone to stock, or you will need to install your favorite custom ROM via adb sideload.
If going back to stock via LGNPST refer to FAQ Number 3 here http://forum.xda-developers.com/showthread.php?t=2006946
If installing custom rom via ADB Sideload refer here http://www.droidviews.com/sideload-roms-mods-using-adb-sideload/
Click to expand...
Click to collapse
I was able to fix the problem late the night of this post, but I REALLY DO APPRECIATE the advice.
I had to reinstall the firmware ultimately. I did learn the commands and process for the sideload, so that was cool, and the program zips did show as downloading from 0-100% and attempted to install, but the 4g part of "this device is geef4g" was an error that I was unable to surmount. I attempted to install the madmack version of TWRP to no avail. I am lucky I figured out the tool ONLY by accidentally stumbling over the advice referencing turning back the clock on the pc.
Moving Forward...
Ok... Had to at least stop in and say thank you for the response and post the conclusion to the handful of people that stopped and looked at the thread and at the least not be one of the members that pops on to fix their device and lurks around until they need help to post again. I wouldn't be back to stock with my Optimus if others did that. I do apologize that I was able to find onsite and unable to do it at the time of the threads origin. I wont re-post links, FlashTool the fix was figuring out the right order to go in with the drivers and eventually flashing the stock AT&T firmware with the LG FlashTool. I kept on getting an error when placing the dll file and the tot in to the Tool and it was total mental error on my part when "organizing" everything beforehand. It did require me to wipe my pc back down to Windows 8.1 simply because this is all new to me and I had files EVERYWHERE from rooting every thing I can get my hands on recently. I'm having fun, but this Optimus is my heart for some reason. Originally I had her rooted with Towelroot (I believe), it could of been the LG one click flash thing that I grabbed from here, and I remember Freegee and KitKat recovery being part of the process, but I attempted to install TWRP (personal preference for me from messing with a Kindle Fire for weeks installing CM) but during reboot always went back to CWM 6.0.2.1 (or similiar). Ultimately CM was the goal on this device but was never possible, for me at least, due to my device being "geef4g" yada yada. I think I have read the fix for this in another post, so I will re study up on all that again if need by, but I wanted to pose this question simply because the "Mystique" of successfully installing CM has passed, and while I love the interface and style of that ROM, I kinda liked AndroidArea51 Rom and another ROM whose name escapes me at the moment that I put on some OLD LG phones that I practiced on in the beginning. So this is my goal. I would love it if one or two of you guys would take the time to look at what I want to accomplish and point me in the right direction as far as the procedure and order I should install these modifications to this device and if you have preferences I would love to hear them. I will look up the threads on how to do everything, so I'm not asking for an easy way out of hitting the search box, but I am WAY behind you guys as far as skill set and knowledge base is concerned and trial and error is not the method I wanted to use on this particular machine. If I need to begin a new thread or if a MOD wants/requires me to rename this thread or move it I understand. Stand by for what my goal is ultimately......
OBJECTIVE
AT&T Optimus Pro G (will HOPEFULLY be accepted by StraightTalk and used on their network or whatnot)
I ran the IMEI through their BYOD tool and it was accepted initially a week or so ago while "rooted", so I am assuming that since it is mine from another network they wont sweat me. HOWEVER, if they are going to send any code or require me to allow them modifications during the activation process that is going to in anyway alter my device down to the castrated ST standard they sell, I will have to weigh finances and options again. I realize that Tethering will be frowned upon, traceable, and grounds for termination in either case, but the subject of Mobile Hotspots is what brought me to you guys here in the first place. It irks me.
In my original "build" of this phone I attempted to dabble in "Over-Clocking" with Kernel Booster and Kernel Auditor. I didn't have a f******* clue what any of that $hiT meant. If the app's pretty much optimized it I did so for SPEED rather than battery. I don't know why, I want this thing to FLY in a noticeable fashion for performance and so that I can whip it out and show my family and friends just what the hell it is that I am accomplishing.
1. Optimize it for speed, but I would like the eventual permanent ROM to be stable PERIOD. Whether I customize the Kernel and then place the ROM, or build the ROM and then mess with the Kernel is a hurdle that I don't understand how to approach really, so when you guys talk about it I just think it sounds cool. I am assuming that "Xposed" is something I should maybe begin studying? Build props through ES File Explorer has peaked my interest as well. Long story short, if CM is what you guys suggest I install, I dont want to Optimize the hell out of the stock only to have all of it be replaced when the custom ROM is flashed. I hope that makes sense.
2. I want to optimize the range on my WIFI and every other manner of device communication without losing security. I have numerous friends that are very generous with their personal accounts that allow me to randomly log in to strangers spots (EX. Xfinity accouts), in order to truly connect to it, I have to sit outside in the yard like a weirdo at 3am with my phone in my backyard, much to the disgust of every dog in the neighborhood. I dont want to be that guy. Honestly, I am really curious in learning how to access the internet and/or any other data networks that are out there with out using these major carriers at all. I feel like there is a lot more out there than the average person is aware of. Maybe they are super low key because they are owned by the upper rich 1% or the military etc etc, but if other networks exist that facilitate the same communications that us peasants pay $100/month to access I want in on it.
3. Optimize the picture, color and clarity of the screen for any and everything being shown on it, optimize the Audio with a good "Music Player"(currently what I use) which I generally heard through head phones and when in the car pushed to that system via FM signal. I currently have over 1000 tracks, discovering a cost efficient way of adding to that Library would be wonderful (ie: spend $0), but I have been out of the music file sharing game for a while so I dont know if this is realistic. Optimizing my camera to take the best shots possible on this phone. I generally shoot nature shots, sunsets, sunrises.... unsuspecting women in doggy, the usual... I will not be loading movies and super large files. I am a NAZI with my storage. If I could expand upon the internal or external factory specs that would be great. In other words, real life applications... I haven't been a gamer for decades so nothing crazy, but this device's beautiful picture is what I fell in love with.
4. A kick ass ROM UI that is eye catching and user friendly... sorry so long winded. Got to go run calls at work now....