Related
I would like to get everyone's opinion, I'm looking at a couple options of how to get rid of Sprint / HTC Junk that runs at startup and continues to startup - Sprint Nav, Sprint Zone, Nascar, all those things. I'd love to hear alternate suggestions as well.
1. Startup Auditor - Seems to do a decent job of keeping things from starting, definitely reduced boot time, but I'm unsure of how it actually operates - is it just another task killer? Or does it actually take things out of a startup list without running in the background? I've been playing with it for close to a day and am still undecided, at times it seems to help, but other times I don't think it really did anything. It seems like having root would make it completely pointless, since you could edit things yourself.
2. Wait for Root - I already did the OTA update so root is not possible, from what I understand. With root access, I'm sure it would be much easier to remove the actual applications, and furthermore install custom roms without the bloat.
3. ?? You tell me please
Thanks guys!
If you're comfortable using adb, you can root here: http://forum.xda-developers.com/showthread.php?t=718889
I rooted my yesterday after the OTA and flashed Fresh 0.5.3. It doesn't have most of the crapware.
gx1400 said:
If you're comfortable using adb, you can root here: http://forum.xda-developers.com/showthread.php?t=718889
I rooted my yesterday after the OTA and flashed Fresh 0.5.3. It doesn't have most of the crapware.
Click to expand...
Click to collapse
Funny I was just reading that. I have zero experience with ADB, but perhaps that is the best route. Can't be too hard to learn, right?
Thanks for posting that. If you have root, it mostly eliminates the need for a program like startup auditor, right?
berardi said:
Funny I was just reading that. I have zero experience with ADB, but perhaps that is the best route. Can't be too hard to learn, right?
Thanks for posting that. If you have root, it mostly eliminates the need for a program like startup auditor, right?
Click to expand...
Click to collapse
Correct. Most ROMs already have the crapware removed, however, once rooted you'll also have the ability to remove and do anything else you want.
If you are uncomfortable with adb, don't be. There are enough tutorials and videos around to walk you through the process. Not only was I a complete noob when I moved to Andriod from the iPhone but I am also using a Mac which means the commands are slightly different. However, with a little trial and error I was able to root via adb the very weekend the phone was released when only adb instructions existed.
And, going forward you'll never have to wait for "Idiot Guides" again. Whenever something new and great comes along you'll have the skills to implement it right away.
okolowicz said:
Correct. Most ROMs already have the crapware removed, however, once rooted you'll also have the ability to remove and do anything else you want.
If you are uncomfortable with adb, don't be. There are enough tutorials and videos around to walk you through the process. Not only was I a complete noob when I moved to Andriod from the iPhone but I am also using a Mac which means the commands are slightly different. However, with a little trial and error I was able to root via adb the very weekend the phone was released when only adb instructions existed.
And, going forward you'll never have to wait for "Idiot Guides" again. Whenever something new and great comes along you'll have the skills to implement it right away.
Click to expand...
Click to collapse
I'm trying to setup ADB right now but I'm stuck here:
http://forum.xda-developers.com/showthread.php?t=694250
3. Enabling ADB support on EVO
If using completely stock EVO, adb will be disabled in recovery and can't be enabled.
Click to expand...
Click to collapse
So if you can't enable ADB on stock EVO, but you need ADB to root - what to do?
EDIT : Nm I think I got it
I want to say that if you plug your phone into your computer and select sync option, that it will install the necessary drivers. Just make sure to turn on usb debugging in your settings menu: menu,settings, applications, development, usb debugging- check the box.
elegantai said:
I want to say that if you plug your phone into your computer and select sync option, that it will install the necessary drivers. Just make sure to turn on usb debugging in your settings menu: menu,settings, applications, development, usb debugging- check the box.
Click to expand...
Click to collapse
Thanks got it..
I'm following these instructions, they seem the most complete. I followed every step successfully and refreshed the pages, and it told me to reboot and run part2. However when I hit
adb reboot
it returns
adb: permission denied
What did I do wrong here?
EDIT: Missed hitting exit. That step wasn't there in original, it is in the recompiled though.
go read up on that thread, do a search for 'permission denied' or the like and I am sure something will come.I saw it a few times while reading that thread
err... Are you sure it didnt just mean reboot your phone?
elegantai said:
go read up on that thread, do a search for 'permission denied' or the like and I am sure something will come.I saw it a few times while reading that thread
err... Are you sure it didnt just mean reboot your phone?
Click to expand...
Click to collapse
haha thanks I was messed up because the original instructions didn't say to exit the adb shell (I probably should have known though) but now I'm past that, now to reboot and hit adb shell /data/local/part2 in time lol this is fun :-D
All done!!! :-D now to flash rom... good times!
Thanks all
As I wrote the guide I realized the files, scripts, and images are scattered through multiple threads, which makes finding what you need difficult, even from a main thread (the guide for example). This was compounded even more when I was writing the CM9 Install Guide for the CyanogenMod Wiki and listed the commands themselves, it became huge, intimidating, and looks extremely daunting, I can only imagine what a new flasher must think seeing it! And and so I decided perhaps I can fix this, and with that I present to you...
The A100 Flashing Toolkit!
What is it?
A single zip file that, when unzipped, contains EVERYTHING you need, ADB, fastboot, scripts, CWM recovery image, everything you need to take your stock ICS A100 through rooting, unlocking the bootloader, and flashing CWM recovery (twrp coming soon)!
How is it used?
Its a set of 6 PC scripts, 3 for windows users (.bat) and 3 for linux users (.sh). Run in order from the same folder, and you can just click and run, reboot, click and run, reboot, click and run, install custom rom, done!
You MUST already be on ICS! This is not for HC, if you are on HC update to ICS FIRST!
Instructions
Make sure you are on ICS! Read the bold red letters above! You have been warned! You should already have installed the Acer USB drivers for ADB to work.
Ok, now you're on ICS....right?
Download and unzip the file to whatever folder you can remember, for example c:\acer or ~/acer.
Open your file manager of choice and browse on over to where you unzipped the files, and get ready.
Windows
Right click on A100-root-win.bat and select Run as Adminitrator.
Once that is finished, let your tablet reboot.
Once it's rebooted, right click on A100-unlock-win.bat and select Run as Administrator.
Once this finishes, let the tablet reboot again (the script will tell you what's happening)
Once it's rebooted, right click on A100-recovery-win.bat and select Run as Administrator.
Allow it to finish, it'll reboot a couple times.
Half the time it reboots into recovery, other reboots into system, not sure why it happens.
If it boots into recovery, go ahead and make a full backup, might as well.
If it boots into system, reboot into recovery and make a full backup, might as well.
At this point, you can now wipe and install a custom ROM, see the A100 Guide in General for ROMs and instructions on this.
Linux
Execute A100-root-linux.sh and allow it to run.
Once that is finished, allow tablet to reboot.
Exectute A100-unlock-linux.sh and allow it to run.
Let the tablet reboot
Execute A100-recovery-linux.sh and allow it to run.
It'll either reboot into recovery, or system, it does one or the other for some reason.
If rebooted into recovery, make a full backup.
If rebooted into system, reboot into recovery and make a full backup.
Wipe and install a new custom ROM, see the A100 Guide in General for ROMs and instructions on this.
How to boot into recovery
There's a few ways, 1 way is an app like quick boot, you can use adb by typing adb reboot recovery or you can do it manually.
Power off the tablet.
Press and hold the volume - button, closest to power and lock switch.
Holding volume - press and hold Power.
Hold until the screen says Booting recovery kernel then let go.
You should be in recovery, either CWM, TWRP, or stock, whatever you have installed.
As always I am open to suggestions, advice, or reports! Feel free to post up or PM me with any issues, questions, bugs, or ideas!
Download
A100 Flash Toolkit 1.1 7-16-12
Now featuring the correct bootloader!
Thanks to smokku for pointing this out.
Who do we thank for this package?
ZeroNull: Alot of the scripting is based on his work, and borrows his ADB and fastboot executables.
ptesmoke: Uses his CWM recovery.img file
CyanogenMod Iconia Team: For allowing me the chance to write for the Wiki, and realizing this NEEDED to be done.
Anyone else I'm forgetting, I'm sorry I will add you as soon as I remember (feel free to drop me a note!)
Sounds great, many thanks.
Thanks for all you hard work and patience.
a100 flash program
After several hours trying, having trouble with some of the batch files. Appears some file names called in .bat different than actual file names, also had to invoke adb from Command prompt window, wouldn't work from windows file manager. Followed instructions but process is breaking down in second batch file. After correcting file names, batch file runs but recovery.img is failing. Need help figuring this out.
Esat
Birbey said:
After several hours trying, having trouble with some of the batch files. Appears some file names called in .bat different than actual file names, also had to invoke adb from Command prompt window, wouldn't work from windows file manager. Followed instructions but process is breaking down in second batch file. After correcting file names, batch file runs but recovery.img is failing. Need help figuring this out.
Esat
Click to expand...
Click to collapse
Oh wow OK I'll take a look I must have mixed everything up. My desktop is littered with files from all these projects. I'm sorry about that I should have double checked everything before I uploaded it. If the called files are different then the scripts it must be the old version mixed with new scripts or something. I should have it squared away sometime tonight/tomorrow morning.
Edit: I'm assuming by saying command prompt you use windows, the a100-root-win.bat file looks fine, was this one giving any issues?
I'm checking the second and third now for whatever is going on.
Tapatalked from my Galaxy S II.
Fixed.
I'm not able to unlock my a100, when it enters boot loader and I press volume - and + nothing happens, any advice? Thanks a lot.
Sent from my A100 using XDA
diegof18 said:
I'm not able to unlock my a100, when it enters boot loader and I press volume - and + nothing happens, any advice? Thanks a lot.
Sent from my A100 using XDA
Click to expand...
Click to collapse
You have to be FAST when it gets there, it times out in like half a second it seems.
When you run it, have the tab in your hand, fingers on volume - and volume + (volume - is next to the lock switch). As soon as you see the screen change, hit volume - then volume +. It takes a few tries usually. It'll just sit there until you reboot afterwards.
Hi, I was wondering, since I just rooted yesterday (got this tab last friday) should I skip the script for rooting and simply run the other two or do I have to run the root script anyways? by the way Im having some real weak reception from this tablet, like 2 bars only and thats when standing about 5 feet from the router, Im willing to follow this procedure in order to try one of the custom roms to see if the wifi weak signal goes away (Ive tried most of the things there are to attemp to fix this, including messing around with my router) do you know if any one has successfully fixed this with a custom rom? if so which one? thanks in advance and sorry for (kinda) hiijacking the thread.
elander said:
Hi, I was wondering, since I just rooted yesterday (got this tab last friday) should I skip the script for rooting and simply run the other two or do I have to run the root script anyways? by the way Im having some real weak reception from this tablet, like 2 bars only and thats when standing about 5 feet from the router, Im willing to follow this procedure in order to try one of the custom roms to see if the wifi weak signal goes away (Ive tried most of the things there are to attemp to fix this, including messing around with my router) do you know if any one has successfully fixed this with a custom rom? if so which one? thanks in advance and sorry for (kinda) hiijacking the thread.
Click to expand...
Click to collapse
Congrats on the purchase and welcome! You can skip over rooting if you already have rooted ICS. Not HC.
The weak wifi is pretty common, mine is weaker then any other devices I have, usually by a bar or 2. Custom roms won't fix it, I think they just have the power turned down on it. Its also possible there is a bad connection to the antenna internally. If you're very unhappy stop Modding now and return to stock and exchange for another unit or brand.
Any other questions feel free to ask.
Tapatalked from my Galaxy S II.
thanks for the info.
pio_masaki said:
Congrats on the purchase and welcome! You can skip over rooting if you already have rooted ICS. Not HC.
The weak wifi is pretty common, mine is weaker then any other devices I have, usually by a bar or 2. Custom roms won't fix it, I think they just have the power turned down on it. Its also possible there is a bad connection to the antenna internally. If you're very unhappy stop Modding now and return to stock and exchange for another unit or brand.
Any other questions feel free to ask.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
thanks for your fast reply, I was contemplating the idea of flashing some custom rom as a last resort before either opening up the tab's case to check for myself that everything was "wired right" as Im not too happy with the idea of sending this off to acer's as I live in the Dominican Republic and I'd hate to pay the overpriced shipping fee if it is something that I can fix by myself, but on the other hand I might as well break something new instead of fixing the wifi anthena, so I guess I'll have to claim the warranty and hope the wont send me another faulty unit (I've read somewhere some people had issues with the replacement units). Such a great little device cursed with bad QA. anyways, if I hard reset the tab it'll be back to stock right? (as of now the tab is running stock os with root access and the modified wpa_wifi apliance to gain access to adhoc networks) Thanks
elander said:
thanks for your fast reply, I was contemplating the idea of flashing some custom rom as a last resort before either opening up the tab's case to check for myself that everything was "wired right" as Im not too happy with the idea of sending this off to acer's as I live in the Dominican Republic and I'd hate to pay the overpriced shipping fee if it is something that I can fix by myself, but on the other hand I might as well break something new instead of fixing the wifi anthena, so I guess I'll have to claim the warranty and hope the wont send me another faulty unit (I've read somewhere some people had issues with the replacement units). Such a great little device cursed with bad QA. anyways, if I hard reset the tab it'll be back to stock right? (as of now the tab is running stock os with root access and the modified wpa_wifi apliance to gain access to adhoc networks) Thanks
Click to expand...
Click to collapse
I'm not sure, but I don't think resetting these puts them back to 100% if rooted, the root stays since it sits in /system. You'll have to manually remove SU then reset to get rid of the root, I think. Other option is restore through the update.zip method which should wipe /system. You could try a hard reset and see if it removes SU or not, it might.
Does the unlock script only works with the pre-release of ICS?
I cant get to the unlock mode... allways saying "xxxx .11 ics fast boot xxxxxxx"
NeO_CooL said:
Does the unlock script only works with the pre-release of ICS?
I cant get to the unlock mode... allways saying "xxxx .11 ics fast boot xxxxxxx"
Click to expand...
Click to collapse
Not quite clear on what you're asking, but as far as I know it should work on any version bootloader unless they changed it on some update, which wouldn't surprise me.
What is the whole message, and when is it occuring?
I have the latest ICS version availble thru OTA.
Or i´m not being fast enough?
Already tried a million times the Volume - and Volume +.
Guetting this message:
"Bootloader V0.03.11-ICS Starting fastboot usb download protocol"
Should get the unlocked mode right?
NeO_CooL said:
I have the latest ICS version availble thru OTA.
Or i´m not being fast enough?
Already tried a million times the Volume - and Volume +.
Guetting this message:
"Bootloader V0.03.11-ICS Starting fastboot usb download protocol"
Should get the unlocked mode right?
Click to expand...
Click to collapse
Ok if you don't get the new screen with two icons, then it isn't unlocking yet. It seems the script is hanging before passing the next step.
When it gets to that screen again, type
fastboot oem unlock
as soon as you hit enter, get ready for that volume down then up, so maybe have it in your lap with your fingers on the volume rocker.
I'll look at the script again to see why it's hanging, or if it isn't hanging, why it's shooting past that point without waiting.
Forgot to say i´m using the windows version.
Thanks
pio_masaki said:
Ok if you don't get the new screen with two icons, then it isn't unlocking yet. It seems the script is hanging before passing the next step.
When it gets to that screen again, type
fastboot oem unlock
as soon as you hit enter, get ready for that volume down then up, so maybe have it in your lap with your fingers on the volume rocker.
I'll look at the script again to see why it's hanging, or if it isn't hanging, why it's shooting past that point without waiting.
Click to expand...
Click to collapse
The issue is that you included the A100 bootloader in the archive with a script to write it.
A100 bootloader (version 0.03.11-ICS) is not unlockable.
You need to write A200 bootloader (version 0.03.06-ICS) to your device, to have the unlocking option.
You know you have unlockable bootloader when you see green ACER logo in the bottom-right side of the screen instead white one in the center.
The script and blob you included is used to restore the original A100 (not unlockable) bootloader.
For the ones looking for the unlockable bootloader, it's here: http://forum.xda-developers.com/showthread.php?t=1557445
smokku said:
The issue is that you included the A100 bootloader in the archive with a script to write it.
A100 bootloader (version 0.03.11-ICS) is not unlockable.
You need to write A200 bootloader (version 0.03.06-ICS) to your device, to have the unlocking option.
You know you have unlockable bootloader when you see green ACER logo in the bottom-right side of the screen instead white one in the center.
The script and blob you included is used to restore the original A100 not unlockable bootloader.
For the ones looking for the unlockable bootloader, it's here: http://forum.xda-developers.com/showthread.php?t=1557445
Click to expand...
Click to collapse
It's just labeled a100, it isn't the actual a100 blob. But go ahead and use that link until I get the chance to go back through it, I'm obviously messing it all up somewhere, I may have used the a100 blob and gotten it mixed up with the a200 blob when I was renaming and shifting things around. I'll pull the download for now until I get the chance to get it all sorted out, sorry guys.
Edit OK its back up with the proper boot loader for unlocking. I can't believe I did that. Huge thanks to smokku for pointing that out!
No worries.
And yeah, you have to be quick when it asks to toggle unlock, like half a second quick.
I attempted a root on Samsung Note 2 Sprint version (in white). Followed all steps, however phone got stuck in a reboot loop right after I put the option 2 (root only) Odin step in. Sprint ver LPH889 (I believe that is what Odin is calling it, option 72). Toolkit used was ADB 4.1.0.
Original symptoms were that the Android updater was looping trying to load everything; being new I made it worse and tried recoveries and reloads which also failed. Now it boots, goes to splash, circling blue oval image and...it stays there.
Good news: I have access to download mode and recovery reset mode (including sideloading).
Bad news: every thread I've followed has given me an issue.
I have recovery access but I need some idea of where to go from here and searches have shown near but not exact symptoms. I have unplugged it from the pc, removed the battery, done a factory reset, attempted to reflash via Odin (root) attempted to reflash stock via Odin and so far I am still stuck in a reboot loop. Windows detects the phone but shows a problem in device manager because possibly it won't stop rebooting. Any help you can provide is appreciated and if at all possible I need to recover some form of working phone here, and soon. My girl needs it for work and Sprint's network in my area barely works from day to day (which they admit but don't credit my account for). This phone has problems sending/receiving calls, they claim it's fine, and I was forced to try a root to get some form of working device. That failed too.
I'm a newb at this...it's been years since I flashed a phone (Razor v3), so...any help would be appreciated, otherwise I have to crawl to sprint/samsung and get it replaced, which I don't want to do. Thanks.
doesitwork? said:
I attempted a root on Samsung Note 2 Sprint version (in white). Followed all steps, however phone got stuck in a reboot loop right after I put the option 2 (root only) Odin step in. Sprint ver LPH889 (I believe that is what Odin is calling it, option 72). Toolkit used was ADB 4.1.0.
Original symptoms were that the Android updater was looping trying to load everything; being new I made it worse and tried recoveries and reloads which also failed. Now it boots, goes to splash, circling blue oval image and...it stays there.
Good news: I have access to download mode and recovery reset mode (including sideloading).
Bad news: every thread I've followed has given me an issue.
I have recovery access but I need some idea of where to go from here and searches have shown near but not exact symptoms. I have unplugged it from the pc, removed the battery, done a factory reset, attempted to reflash via Odin (root) attempted to reflash stock via Odin and so far I am still stuck in a reboot loop. Windows detects the phone but shows a problem in device manager because possibly it won't stop rebooting. Any help you can provide is appreciated and if at all possible I need to recover some form of working phone here, and soon. My girl needs it for work and Sprint's network in my area barely works from day to day (which they admit but don't credit my account for). This phone has problems sending/receiving calls, they claim it's fine, and I was forced to try a root to get some form of working device. That failed too.
I'm a newb at this...it's been years since I flashed a phone (Razor v3), so...any help would be appreciated, otherwise I have to crawl to sprint/samsung and get it replaced, which I don't want to do. Thanks.
Click to expand...
Click to collapse
What method are you using to root.....I used the "toolkit" and had no problems at all.
http://forum.xda-developers.com/showthread.php?t=1957155....try this if you haven't already
vel7wil said:
What method are you using to root.....I used the "toolkit" and had no problems at all.
http://forum.xda-developers.com/showthread.php?t=1957155....try this if you haven't already
Click to expand...
Click to collapse
I thought it would to but I did not want to dig through 70+ pages of the thread when searching failed...unless I really needed to. Most of it is old and doesn't apply.
I was directed by the referenced Youtube vid. I used the options referenced for the phone in this thread with that toolkit. I backed up existing files (not as one unit, but internal files and I think OS), went for the option 2, followed the instructions and things went great through odin...until android went to update and started looping with the 'updating files' percentages. At that point I tried to restore to basic and started clearing caches and such and that is how I got to where I am.
When that failed I started looking at the leaked stock flash and that failed on shoot.ini which that guy never addressed because he thought his international version was all versions (that's why I choose 'doesitwork?' as screen name ). So i'm down to sideloading or something. I really need guidance, and I emailed the toolkit author but I'm still waiting on a reply.
Any thoughts?
doesitwork? said:
I thought it would to but I did not want to dig through 70+ pages of the thread when searching failed...unless I really needed to. Most of it is old and doesn't apply.
I was directed by the referenced Youtube vid. I used the options referenced for the phone in this thread with that toolkit. I backed up existing files (not as one unit, but internal files and I think OS), went for the option 2, followed the instructions and things went great through odin...until android went to update and started looping with the 'updating files' percentages. At that point I tried to restore to basic and started clearing caches and such and that is how I got to where I am.
When that failed I started looking at the leaked stock flash and that failed on shoot.ini which that guy never addressed because he thought his international version was all versions (that's why I choose 'doesitwork?' as screen name ). So i'm down to sideloading or something. I really need guidance, and I emailed the toolkit author but I'm still waiting on a reply.
Any thoughts?
Click to expand...
Click to collapse
When used the toolkit a year ago, I found that I had to turned off all firewalls and antivirus apps for it to work properly. Once I did that it worked fine....give it a shot...can't hurt......might even be able to repair what you've done so far.....Good Luck!!!
I'll give this my best shot...download a rooted rom from the development section and place it on your SD card.
Download toolkit from here (I take no credit for this) http://d-h.st/iu0
Put phone in download mode.
Open ODIN and uncheck "auto reboot". Then click "PDA" and add the .tar file (recovery).
Plug phone into PC (make sure to have samsung drivers installed).
Once ODIN sees the phone you can click "start".
When the recovery flash is complete, pull your battery to ensure power down.
Boot into recovery : volume up, home, power all at the same time.
Flash rooted rom.
Toolkit is an extra and unnecessary step.
http://rwilco12.com/downloads.php?d...ung Galaxy Note II (SPH-L900)/Stock ROMs/MC2/
Grab the one click flavor of choice. Use the one with 1090526 in the name as that's the full version.
Open in windows, put phone in download mode and flash. Easy Peasy.
Let me know if you have any issues with this.
Sorry for the late reply, I had some issues with the "catchpa".
The one click fix worked like a charm, thank you! I will soon be making a contrib to the site. It's a shame I couldn't root as easily :laugh: .
I know the level of work that goes into this stuff and the desire to keep on top of new gear while maintaining support for the old and I appreciate the community coming to my aid, so again, thank you!
---------- Post added at 08:14 AM ---------- Previous post was at 07:36 AM ----------
[/COLOR]
doesitwork? said:
Sorry for the late reply, I had some issues with the "catchpa".
The one click fix worked like a charm, thank you! I will soon be making a contrib to the site. It's a shame I couldn't root as easily :laugh: .
I know the level of work that goes into this stuff and the desire to keep on top of new gear while maintaining support for the old and I appreciate the community coming to my aid, so again, thank you!
Click to expand...
Click to collapse
It is usually a pretty common courtesy to hit the "thanks button" when someone helps you out.
I am not at all trying to be mean, just letting you know.
garwynn said:
Toolkit is an extra and unnecessary step.
http://rwilco12.com/downloads.php?d...ung Galaxy Note II (SPH-L900)/Stock ROMs/MC2/
Grab the one click flavor of choice. Use the one with 1090526 in the name as that's the full version.
Open in windows, put phone in download mode and flash. Easy Peasy.
Let me know if you have any issues with this.
Click to expand...
Click to collapse
hello @garwynn im trying to do this same thing.. its been so long since ive odin'd, how would i put TWRP on this now after these steps? i tried goomanager and that didnt work. (couldnt find recovery) and i tried flashing in stock recovery and got a fail . im kind of lost right now and am wondering if there is another way or do i have to do the toolkit? thanks
edit: for some reason, the tool kit links have been pulled by a mod. ..but this video helped me get twrp back. phew. zedomax to the rescue.. http://www.youtube.com/watch?v=7leb9OznhqY
so yesterday i installed the new optimus de rom and it started up fine and everything was okay, then today i realized my 3g wasnt working and usually thats no big deal because all i have to do is restore my efs in the app FreeG (I think thats what its called, I might be wrong). Well right after i did that, i hit restart phone and it turned off then wouldnt come back on. Then i finally got to the LG symbol but it will turn off then the screen will be on but will just show black. I cant boot in to recovery nor can i do anything on it at all, when i plug it in the charger it says "battery.png is missing, battery: 75%". I took my phone in to sprint and they did a reset although that didnt do anything so there sending me a new one. Now my question is, is there any way I can open up my phones folder so i can get my pictures and everything that was on it? My pics were very important to me and i dont want to lose them, thats all i need so if some could help me get them that would be much appreciated, thanks.
Penley94 said:
so yesterday i installed the new optimus de rom and it started up fine and everything was okay, then today i realized my 3g wasnt working and usually thats no big deal because all i have to do is restore my efs in the app FreeG (I think thats what its called, I might be wrong). Well right after i did that, i hit restart phone and it turned off then wouldnt come back on. Then i finally got to the LG symbol but it will turn off then the screen will be on but will just show black. I cant boot in to recovery nor can i do anything on it at all, when i plug it in the charger it says "battery.png is missing, battery: 75%". I took my phone in to sprint and they did a reset although that didnt do anything so there sending me a new one. Now my question is, is there any way I can open up my phones folder so i can get my pictures and everything that was on it? My pics were very important to me and i dont want to lose them, thats all i need so if some could help me get them that would be much appreciated, thanks.
Click to expand...
Click to collapse
The key here is going to be getting back into recovery. Have you tried getting into Download Mode? If you saw the LG logo then you SHOULD be able to get into download mode. Make sure the phone is completely powered off. Connect the USB to your pc but before you connect the other end to your phone, hold volume up then connect it. You should see "Download Mode" on the screen. You will see other directions for download mode but for me this always works, usb to pc, hold volume up then plug the phone in while still holding the volume up. If you can get into Download Mode you can flash a teenybin to get back into recovery following the guide in this thread here.
Currently even if you can get into Download Mode adb might not recognize your phone(at least it never did for me). Once you flash a teenybin using LGNPST, you should be able to get into Recovery. Once in Recovery you can use adb to pull your files off of the phone and onto your computer. I use it from a linux terminal but there are guides available for Windows if that's what you use. The adb guide should be easy to find on xda(just search) so I haven't linked to it. Once adb is set up on your computer AND you can get into Recovery you can use the command 'adb pull /data/media' without quotations and it will copy the contents of your internal storage to your pc. However if you can get into recovery you do have other options for just getting the phone back up and running. This guide here should also help.
If you are familiar with irc(internet relay chat) you can hop onto freenode and enter the #lg-optimus-g channel. As soon as you enter the channel you will see "Need Help? You won't read this but..." followed by a link. All the files for LGNPST, teenybins, and in depth tutorials on fixing a soft brick will be found there. I hope this helps you and hooray for me because this is my 200th post!
PS - If you can't get into Download Mode then your secondary bootloader is gone and there isn't anything you can do(to my knowledge). However, like I said, if you saw the LG logo at all, Download mode should still be an option. Also keep in mind these instructions are for the Sprint(ls970) lg optimis g. I believe the keys are flipped on AT&T/International models(Volume Down when you plug it in to get to Download Mode).
HPTesla said:
The key here is going to be getting back into recovery. Have you tried getting into Download Mode? If you saw the LG logo then you SHOULD be able to get into download mode. Make sure the phone is completely powered off. Connect the USB to your pc but before you connect the other end to your phone, hold volume up then connect it. You should see "Download Mode" on the screen. You will see other directions for download mode but for me this always works, usb to pc, hold volume up then plug the phone in while still holding the volume up. If you can get into Download Mode you can flash a teenybin to get back into recovery following the guide in this thread here.
Currently even if you can get into Download Mode adb might not recognize your phone(at least it never did for me). Once you flash a teenybin using LGNPST, you should be able to get into Recovery. Once in Recovery you can use adb to pull your files off of the phone and onto your computer. I use it from a linux terminal but there are guides available for Windows if that's what you use. The adb guide should be easy to find on xda(just search) so I haven't linked to it. Once adb is set up on your computer AND you can get into Recovery you can use the command 'adb pull /data/media' without quotations and it will copy the contents of your internal storage to your pc. However if you can get into recovery you do have other options for just getting the phone back up and running. This guide here should also help.
If you are familiar with irc(internet relay chat) you can hop onto freenode and enter the #lg-optimus-g channel. As soon as you enter the channel you will see "Need Help? You won't read this but..." followed by a link. All the files for LGNPST, teenybins, and in depth tutorials on fixing a soft brick will be found there. I hope this helps you and hooray for me because this is my 200th post!
PS - If you can't get into Download Mode then your secondary bootloader is gone and there isn't anything you can do(to my knowledge). However, like I said, if you saw the LG logo at all, Download mode should still be an option. Also keep in mind these instructions are for the Sprint(ls970) lg optimis g. I believe the keys are flipped on AT&T/International models(Volume Down when you plug it in to get to Download Mode).
Click to expand...
Click to collapse
Thank you for the response, i just tryed to get in to download mode and it went in to it fine. I would try to do all that to repair it but I dont want sprint to see that its rooted and it I cant have it be fixed when the new phone comes in, the only thing that i want is to get my files from it. Is there any way that I can just do that but leave the phone the way it is? (Not booting up passed the lg logo) I want the new phone because my current Optimus G's battery is going pretty bad I think and I would like a new one.
Penley94 said:
Thank you for the response, i just tryed to get in to download mode and it went in to it fine. I would try to do all that to repair it but I dont want sprint to see that its rooted and it I cant have it be fixed when the new phone comes in, the only thing that i want is to get my files from it. Is there any way that I can just do that but leave the phone the way it is? (Not booting up passed the lg logo) I want the new phone because my current Optimus G's battery is going pretty bad I think and I would like a new one.
Click to expand...
Click to collapse
There are plenty of ways to get it stuck at the lg logo, sometimes it happens just from dirty flashing a rom, sometimes because you install a rom without wiping dalvik/cache. But you should know if you are on Sprint, one of the reasons I stick with them(even though their coverage is horrible in my area) is because rooting DOES NOT void your warranty with Sprint. They will warn you against it but they are the only carrier that allows rooting and will still fix your phone. Here is some info on that here. They won't advertise it but it's the truth. But bricking your phone intentionally is pretty easy I think. After getting back your data, just go into recovery and start deleting stuff you normally wouldn't. It's similar to opening up your car's hood and saying "This looks important" and ripping it out, lol. At this point that's what I would do, fixing your rooted phone is within their warranty, replacing it(which is what you want) I'm not 100% on. Although the post I linked to, says even ordering a replacement on a rooted phone is covered. Its in a reply on that page, you'll see another link. So you could get your info, use a different LGNPST file to set your phone back to factory(which will relock the bootloader and lose root) and then you can do what you did to get there in the first place or root it and start deleting important files with a root explorer to get it back to being stuck. Hope this helps.
HPTesla said:
There are plenty of ways to get it stuck at the lg logo, sometimes it happens just from dirty flashing a rom, sometimes because you install a rom without wiping dalvik/cache. But you should know if you are on Sprint, one of the reasons I stick with them(even though their coverage is horrible in my area) is because rooting DOES NOT void your warranty with Sprint. They will warn you against it but they are the only carrier that allows rooting and will still fix your phone. Here is some info on that here. They won't advertise it but it's the truth. But bricking your phone intentionally is pretty easy I think. After getting back your data, just go into recovery and start deleting stuff you normally wouldn't. It's similar to opening up your car's hood and saying "This looks important" and ripping it out, lol. At this point that's what I would do, fixing your rooted phone is within their warranty, replacing it(which is what you want) I'm not 100% on. Although the post I linked to, says even ordering a replacement on a rooted phone is covered. Its in a reply on that page, you'll see another link. So you could get your info, use a different LGNPST file to set your phone back to factory(which will relock the bootloader and lose root) and then you can do what you did to get there in the first place or root it and start deleting important files with a root explorer to get it back to being stuck. Hope this helps.
Click to expand...
Click to collapse
Oh wow I never knew that but that helps a lot thanks for the help, the sprint guy said theydid a master reset or hard reset or soemthing like that, does that mean it deleted all my pictures and everything? And i understand what you mean to rebrick it that's pretty simple. When i get my new optimus is there a new root out for the update? And what roms do you prefer?
Penley94 said:
Oh wow I never knew that but that helps a lot thanks for the help, the sprint guy said theydid a master reset or hard reset or soemthing like that, does that mean it deleted all my pictures and everything? And i understand what you mean to rebrick it that's pretty simple. When i get my new optimus is there a new root out for the update? And what roms do you prefer?
Click to expand...
Click to collapse
If they did a hard reset it is possible that it wiped everything but not a definite. I purchased my phone from Best Buy and was on zvb. When the zvc update came through it messed my phone up(which is why you don't take OTA's once rooted without further knowledge/modifications) so I took it to Best Buy and they said they did a hard reset to fix it. It worked, my phone booted back up and my internal was fine. However, that's Best Buy and they barely know what they are doing so it may have been a soft reset, I am not 100% sure. As for a new root for the update, I received another phone shortly after because the glass back on mine broke and Best Buy replaced it with a whole new phone. It was on zvc and I used an app named Framaroot with the Gandalf exploit option and it worked fine for me. I have heard of others having issues with that method but for me, it worked and has stuck.
Fiddy619's universal root method seems to be the preferred way for our phone, look in the general section here for a thread by engine95 to see what I mean. After I rooted with Framaroot I then used FreeGee and unlocked the bootloader then made a total nandroid backup of my stock in TWRP before going further. I also copied the backup to my PC just in case.
As for my preferred roms, if we are talking about Android 4.4 both Vanir and PSX are my personal favorites. However as you can tell from my signature I am still using stock zvc android 4.1.2. I have flashed just about every rom available for our phone but my daily driver is stock that I have modified manually(different kernel, removed bloat ware, minor modifications and tweaks, etc). For android 4.3 I have had the best experience with CM10.2 and cfxe. I have not tried CM11(based on 4.4) for awhile but it seems to have overwhelming support - Cyanogenmod usually does.
Really when it comes to roms it's personal preference. They are all very similar with different tweaks/additions. As for which one is the most stable that is also a tricky question. Even though we have the same model of phone, I have seen how picky they can be from one to the other. My roommates have the EXACT same phone, installing CM10.2 worked fine for two of us, but one lost GPS and I had to fix it.
My best advice for when you get your new phone is to backup your working stock and then have fun flashing different things making sure you follow the instructions per rom exactly. It's always a good idea after making your backup(if planning to install another rom) to wipe everything except your internal storage and do a clean install of the rom and gapps. Then, test it for a day or so because sometimes it takes time to settle in. It's a shame that Optimus DE gave you issues, it was rock solid for me, again, these phones are picky! But one of the main reasons I stayed with stock is because the AOSP based cameras leave much to be desired when compared to the LG camera. Again it's just personal preference because some don't like the lg camera.
If you have any other issues or questions I will be glad to help if I can. A lot of the people you see who are active on the forums are very knowledgeable, as long as you ask politely most will be glad to help.
HPTesla said:
If they did a hard reset it is possible that it wiped everything but not a definite. I purchased my phone from Best Buy and was on zvb. When the zvc update came through it messed my phone up(which is why you don't take OTA's once rooted without further knowledge/modifications) so I took it to Best Buy and they said they did a hard reset to fix it. It worked, my phone booted back up and my internal was fine. However, that's Best Buy and they barely know what they are doing so it may have been a soft reset, I am not 100% sure. As for a new root for the update, I received another phone shortly after because the glass back on mine broke and Best Buy replaced it with a whole new phone. It was on zvc and I used an app named Framaroot with the Gandalf exploit option and it worked fine for me. I have heard of others having issues with that method but for me, it worked and has stuck.
Fiddy619's universal root method seems to be the preferred way for our phone, look in the general section here for a thread by engine95 to see what I mean. After I rooted with Framaroot I then used FreeGee and unlocked the bootloader then made a total nandroid backup of my stock in TWRP before going further. I also copied the backup to my PC just in case.
As for my preferred roms, if we are talking about Android 4.4 both Vanir and PSX are my personal favorites. However as you can tell from my signature I am still using stock zvc android 4.1.2. I have flashed just about every rom available for our phone but my daily driver is stock that I have modified manually(different kernel, removed bloat ware, minor modifications and tweaks, etc). For android 4.3 I have had the best experience with CM10.2 and cfxe. I have not tried CM11(based on 4.4) for awhile but it seems to have overwhelming support - Cyanogenmod usually does.
Really when it comes to roms it's personal preference. They are all very similar with different tweaks/additions. As for which one is the most stable that is also a tricky question. Even though we have the same model of phone, I have seen how picky they can be from one to the other. My roommates have the EXACT same phone, installing CM10.2 worked fine for two of us, but one lost GPS and I had to fix it.
My best advice for when you get your new phone is to backup your working stock and then have fun flashing different things making sure you follow the instructions per rom exactly. It's always a good idea after making your backup(if planning to install another rom) to wipe everything except your internal storage and do a clean install of the rom and gapps. Then, test it for a day or so because sometimes it takes time to settle in. It's a shame that Optimus DE gave you issues, it was rock solid for me, again, these phones are picky! But one of the main reasons I stayed with stock is because the AOSP based cameras leave much to be desired when compared to the LG camera. Again it's just personal preference because some don't like the lg camera.
If you have any other issues or questions I will be glad to help if I can. A lot of the people you see who are active on the forums are very knowledgeable, as long as you ask politely most will be glad to help.
Click to expand...
Click to collapse
Okay Im going to try some new roms out when I get my new phone, I would like to try out an AOSP Kitkat Rom but I couldnt get one to flash last time I tryed but I will figure that out later when I get it. Now back to my Bricked Optimus, I want to try the teenybin method although I dont understand the directions... the second step tells me to flash but how can I do that without recovery? and it doesnt say anything about entering in download mode which is the only thing I can do, am I forgetting something? And thank you for the help Tesla I really appreciate it, Ive had more assistance from you than anyone else.
Penley94 said:
Okay Im going to try some new roms out when I get my new phone, I would like to try out an AOSP Kitkat Rom but I couldnt get one to flash last time I tryed but I will figure that out later when I get it. Now back to my Bricked Optimus, I want to try the teenybin method although I dont understand the directions... the second step tells me to flash but how can I do that without recovery? and it doesnt say anything about entering in download mode which is the only thing I can do, am I forgetting something? And thank you for the help Tesla I really appreciate it, Ive had more assistance from you than anyone else.
Click to expand...
Click to collapse
Are you a windows user? The teenybin isn't flashed from recovery it is flashed from a tool called LGNPST which is a Windows program. I am going to private message you a link. It will have links for downloading and installing LGNPST on your PC. It says that you will lose all your data but if you are using the teenybin you shouldn't. It's LG's tool for flashing firmware and gives that warning regardless of what you flash. And you're welcome, coming from an EVO 4G this phone is very different and plenty of people have helped me - just paying it forward.
HPTesla said:
Are you a windows user? The teenybin isn't flashed from recovery it is flashed from a tool called LGNPST which is a Windows program. I am going to private message you a link. It will have links for downloading and installing LGNPST on your PC. It says that you will lose all your data but if you are using the teenybin you shouldn't. It's LG's tool for flashing firmware and gives that warning regardless of what you flash. And you're welcome, coming from an EVO 4G this phone is very different and plenty of people have helped me - just paying it forward.
Click to expand...
Click to collapse
Hey I got in to recovery through the Teenybin although the reset that they did deleted all of my stuff so Im kinda bummed:/ but its okay cause I got my new Optimus today and its brand new so Im happy with it. Thanks again for all of the help. Thats funny that you used to have an EVO 4G because I had it for so long and thats the phone I switched back to when my LG got bricked, but let me tell you Im glad to be back to the Optimus haha the EVO 4G is just way to slow anymore. Now that I have this new Optimus which root method should I go with? Its currently runnning ZVB (4.1.2) should I update the software? It says theres a software update available but I know that sometimes they dont have roots out for those updates so how should I start with this process again with the new phone in your opinion? I havnt done this in forever (going on a year) so I cant really remember everything that I had to do.
Penley94 said:
Hey I got in to recovery through the Teenybin although the reset that they did deleted all of my stuff so Im kinda bummed:/ but its okay cause I got my new Optimus today and its brand new so Im happy with it. Thanks again for all of the help. Thats funny that you used to have an EVO 4G because I had it for so long and thats the phone I switched back to when my LG got bricked, but let me tell you Im glad to be back to the Optimus haha the EVO 4G is just way to slow anymore. Now that I have this new Optimus which root method should I go with? Its currently runnning ZVB (4.1.2) should I update the software? It says theres a software update available but I know that sometimes they dont have roots out for those updates so how should I start with this process again with the new phone in your opinion? I havnt done this in forever (going on a year) so I cant really remember everything that I had to do.
Click to expand...
Click to collapse
Let your phone update before rooting and unlocking. You should end up with ZVC.
Then, you have a choice on rooting. @HPTesla will say Framaroot. I'd say use fiddy Universal root.
Then DL FreeGee from the Playstore, use the"mako" version of TWRP/CWM, your choice, I'd do with TWRP and you'll be unlocked.
Back it up in recovery and you'll be good to go.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
Let your phone update before rooting and unlocking. You should end up with ZVC.
Then, you have a choice on rooting. @HPTesla will say Framaroot. I'd say use fiddy Universal root.
Then DL FreeGee from the Playstore, use the"mako" version of TWRP/CWM, your choice, I'd do with TWRP and you'll be unlocked.
Back it up in recovery and you'll be good to go.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The fiddy universal looks easier to me so I will probably use that although its not very Important which ever one is better I will use, and what recovery do you think is better? I used TWRP before but is the other one any better? I will probably go with that anyways Im just trying to get some opinions in. And what ROM do you use? I think Im gonna start out with the stock rooted ROM but theres still some stuff I want from the DE ROM like the G2 keyboard and other features from the G2, is there any way I can get those? And have you had any experience with the KitKat ROMs? Those interest me too
engine95 said:
Let your phone update before rooting and unlocking. You should end up with ZVC.
Then, you have a choice on rooting. @HPTesla will say Framaroot. I'd say use fiddy Universal root.
Then DL FreeGee from the Playstore, use the"mako" version of TWRP/CWM, your choice, I'd do with TWRP and you'll be unlocked.
Back it up in recovery and you'll be good to go.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Exactly what he said, framaroot was quick and easy for me, but the lgog is so damn picky and fiddy seems to be the preferred method so use it just to be safe. I had zero issues with framaroot but I think I've just been lucky. And definitely update to zvc before doing either. I'd also update prl and profile for good measure.
That sucks that you lost all of your data, they must have actually did a hard reset where as BestBuy told me they did a hard reset and actually did a soft reset. But it's BestBuy so I never expect much. I softbricked my lgog the day after I got it using the GAIO tool(before finding out about FreeGee) and they fixed it with a soft reset. The guy called the manager over and the manager asked me if I tried unlocking the bootloader and I played dumb. My exact words were "What the hell is a bootloader?" and he immediately fixed it. But I was shocked anyone at BestBuy would even know that. Lmao.
As for my EVO, the micro usb port broke so I was charging it for two months like MacGyver, literally stipped the usb charging wire and hooked it straight into the positive/negative terminals in the battery while turned off! It was a fire hazard but it did the trick, lol. And luckily it had external sd(my one big gripe about the lgog) so I could still get my stuff off of it even without usb. I did love that phone, but you're right, it's incredibly slow now compared to the wonderful lgog.
And as always you are quite welcome!
---------- Post added at 07:39 PM ---------- Previous post was at 07:30 PM ----------
Penley94 said:
The fiddy universal looks easier to me so I will probably use that although its not very Important which ever one is better I will use, and what recovery do you think is better? I used TWRP before but is the other one any better? I will probably go with that anyways Im just trying to get some opinions in. And what ROM do you use? I think Im gonna start out with the stock rooted ROM but theres still some stuff I want from the DE ROM like the G2 keyboard and other features from the G2, is there any way I can get those? And have you had any experience with the KitKat ROMs? Those interest me too
Click to expand...
Click to collapse
I think the reason I say framaroot is bc its also super easy, install the app, pick gandalf exploit and it will do it's thing - done without ever connecting to a pc. But @engine95 is right, fiddy is more stable so use that. As for TWRP, I love 2.5.0.0 but for KK roms you have to use the one that comes with updated FreeGee, TWRP 2.6.3.x because of the SELinux changes Google made with 4.4. TWRP 2.6 was unstable originally but has since become just as stable as 2.5 according to most. OpTimuS DE was rock solid for me, as for getting some of the G2 apps, I'm not certain. It's doable but I don't know how difficult it would be because I've never tried to install them elsewhere. And I already gave you my choice of best current KK roms but today I found out a few guys are trying to get OMNI official for us. When that happens I think I will be switching to OMNI because they have been producing some impressive commits/tweaks that you won't find elsewhere. Just look through xda news to see what I mean, OMNI is on a roll!
Penley94 said:
The fiddy universal looks easier to me so I will probably use that although its not very Important which ever one is better I will use, and what recovery do you think is better? I used TWRP before but is the other one any better? I will probably go with that anyways Im just trying to get some opinions in. And what ROM do you use? I think Im gonna start out with the stock rooted ROM but theres still some stuff I want from the DE ROM like the G2 keyboard and other features from the G2, is there any way I can get those? And have you had any experience with the KitKat ROMs? Those interest me too
Click to expand...
Click to collapse
I prefer TWRP just because that has always been our best one since the beginning. Now that all the versions of the OG are coming together though both are fine.
I like stock, but Lrod's OpTimuS 5.0 is my daily. The G2 adds he made got me hooked.
If your gonna try to pull some stuff from DE, check with Lrod. He's made alot of changes to a lot of files making it difficult. For me at least.
I've ran all the KK Roms and I liked them all. PSX is probably my favorite though. I liked Liquid in its early days, pre KK. I'm not sure it's up to KK yet.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
I prefer TWRP just because that has always been our best one since the beginning. Now that all the versions of the OG are coming together though both are fine.
I like stock, but Lrod's OpTimuS 5.0 is my daily. The G2 adds he made got me hooked.
If your gonna try to pull some stuff from DE, check with Lrod. He's made alot of changes to a lot of files making it difficult. For me at least.
I've ran all the KK Roms and I liked them all. PSX is probably my favorite though. I liked Liquid in its early days, pre KK. I'm not sure it's up to KK yet.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Again, I think you're right on all fronts. Liquid was smooth(heh) but it hasn't been long since we received an official 4.3 so I don't think they're up to 4.4. And same goes for the G2 apps, sometimes it's as simple as pulling an apk out of a zip and pushing it to system/apps and changing permissions but I think Lrod did a lot of work to get the G2 apps working on our phone because they required certain dependencies/modified frameworks.
engine95 said:
Let your phone update before rooting and unlocking. You should end up with ZVC.
Then, you have a choice on rooting. @HPTesla will say Framaroot. I'd say use fiddy Universal root.
Then DL FreeGee from the Playstore, use the"mako" version of TWRP/CWM, your choice, I'd do with TWRP and you'll be unlocked.
Back it up in recovery and you'll be good to go.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Okay so I rooted it through fiddys universal root but when I try to go on to FreeGee it just doesnt want to open for me? Ive tryed a lot of times and I get nothing it will either send me to the playstore to an app called busy box or will sometimes restart my phone, Im confised I have no clue what to do? I tryed to uninstall and reinstall and nothing I installed the busybox app but it said I didnt have root permission or there was a problem getting the root or something like that.
Penley94 said:
Okay so I rooted it through fiddys universal root but when I try to go on to FreeGee it just doesnt want to open for me? Ive tryed a lot of times and I get nothing it will either send me to the playstore to an app called busy box or will sometimes restart my phone, Im confised I have no clue what to do? I tryed to uninstall and reinstall and nothing I installed the busybox app but it said I didnt have root permission or there was a problem getting the root or something like that.
Click to expand...
Click to collapse
You have to root before unlocking.
Make sure your phone has at least 70 percent charge or more!!
Go to Settings: Settings>Security>Unknown sources checked: Settings>Developer Options>USB Debugging checked, Settings> Display>Screen Timeout - at least 5 min
from fiddy thread.
Directions
1. Unzip the zip file
2. Make sure USB Debugging is on, and you are in Charge only Mode
3. Run the CurrentRoot.bat, wait for the prompt. (Can now be run as admin if you wish, Still works running as regular user tho. Thanks robisodd)
4. Change to MTP Mode
5. Just ignore when your computer asks how to view files on your device.
6. Press enter in the CMD prompt to continue.
7. Done.
You shouldn't have any issues.
If you do, then try Framaroot. http://forum.xda-developers.com/showthread.php?t=2130276 and follow those directions.
Follow this. http://forum.xda-developers.com/showthread.php?t=2050582 It has all the info on rooting and unlocking
Edit. You may have to root as admin/not admin, try both.
Edit #2 Also, do not use USB 3.0 ports. They are iffy for this stuff. LGNPST included
engine95 said:
You have to root before unlocking.
Make sure your phone has at least 70 percent charge or more!!
Go to Settings: Settings>Security>Unknown sources checked: Settings>Developer Options>USB Debugging checked, Settings> Display>Screen Timeout - at least 5 min
from fiddy thread.
Directions
1. Unzip the zip file
2. Make sure USB Debugging is on, and you are in Charge only Mode
3. Run the CurrentRoot.bat, wait for the prompt. (Can now be run as admin if you wish, Still works running as regular user tho. Thanks robisodd)
4. Change to MTP Mode
5. Just ignore when your computer asks how to view files on your device.
6. Press enter in the CMD prompt to continue.
7. Done.
You shouldn't have any issues.
If you do, then try Framaroot. http://forum.xda-developers.com/showthread.php?t=2130276 and follow those directions.
Follow this. http://forum.xda-developers.com/showthread.php?t=2050582 It has all the info on rooting and unlocking
Edit. You may have to root as admin/not admin, try both.
Edit #2 Also, do not use USB 3.0 ports. They are iffy for this stuff. LGNPST included
Click to expand...
Click to collapse
Okay i will try this later when i have access to a computer, but the last root i tryed told me it was successful although it didnt restart my phone or anything it just said it was in the command prompt. I will try again cause i dont think it did anything. But i have a question about roms, i am most likely going to flash the DE 5.0 again because i like it with the g2 keyboard and i kind of like the lg feel to it but the only problem is google play music always gives me an error when im playing songs and it always has. I heard aosp roms dont have that problen so in your opinion what is the most stable aosp rom with all features working like gps and everything??
Penley94 said:
Okay i will try this later when i have access to a computer, but the last root i tryed told me it was successful although it didnt restart my phone or anything it just said it was in the command prompt. I will try again cause i dont think it did anything. But i have a question about roms, i am most likely going to flash the DE 5.0 again because i like it with the g2 keyboard and i kind of like the lg feel to it but the only problem is google play music always gives me an error when im playing songs and it always has. I heard aosp roms dont have that problen so in your opinion what is the most stable aosp rom with all features working like gps and everything??
Click to expand...
Click to collapse
AOSP SuperNexus has been getting good reviews here in the forums but I haven't tried it yet. I would give that one a shot though. I'd flash GAPPS standard with it instead of GAPPS core as well. This is just generally speaking with any of the AOSP roms.
The directions @engine95 gave you for fiddy are spot on(as usual ), specifically having the phone in charge only mode instead of mtp. I think a lot of people have missed that step and it won't work in mtp. Using usb 2.0 is another good tip.
And if your phone didn't reboot, you probably arent rooted. Easiest way to check that you are rooted is by going into the app drawer and seeing either Superuser or SuperSu app. If it's there, you're rooted, if not, it didnt work. If it said it worked but didnt reboot, Im assuming you rebooted manually? It sounds silly but sometimes it's as simple as that. But again, after rebooting if one of those apps arent there, you are not rooted.
EDIT: I've never tried rooting with fiddy without being in charge only mode, Im wondering if being in mtp may install supersu/superuser app but not the binary? Probably not but I could be wrong. Just wondering if there is any possible way that the app could be there but you still wouldn't have root privileges. For me, if the app is there, I'm rooted but I don't pretend to know everything(far from it, lol).
EDIT#2: Once you are rooted and recovery is installed, here is the link to SuperNexus.
EDIT#3: And I can't stress this one enough....after rooting and unlocking the bootloader, before flashing ANYTHING, make a full backup of your stock AND copy the TWRP folder(with your backup in it) to a computer, JUST IN CASE! That way you will always have a backup elsewhere, even if something goes wrong with your phone's internal storage. Better safe than sorry!!! And it's also best to copy the entire TWRP folder.
@HPTesla You're on a roll!
Go with everything he's said.
I don't use Google music ,so I'm of little help there.
Almost every ROM has its quirks, and it's just a matter of finding the one that does what you need/want.
Our devs have given us a lot of options. And I know, I sure appreciate them.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Penley94 said:
so yesterday i installed the new optimus de rom and it started up fine and everything was okay, then today i realized my 3g wasnt working and usually thats no big deal because all i have to do is restore my efs in the app FreeG (I think thats what its called, I might be wrong). Well right after i did that, i hit restart phone and it turned off then wouldnt come back on. Then i finally got to the LG symbol but it will turn off then the screen will be on but will just show black. I cant boot in to recovery nor can i do anything on it at all, when i plug it in the charger it says "battery.png is missing, battery: 75%". I took my phone in to sprint and they did a reset although that didnt do anything so there sending me a new one. Now my question is, is there any way I can open up my phones folder so i can get my pictures and everything that was on it? My pics were very important to me and i dont want to lose them, thats all i need so if some could help me get them that would be much appreciated, thanks.
Click to expand...
Click to collapse
I ran OpTiMuS for a long time and every time I would try new roms, decide I didn't like or whatever and go back, I'd always have to 1. Dial ##72786# 2. Let it self activate sometimes twice, but usually just once before I would pick up 3g/4g. May have just been my phone but you may try that out if you go back to optimus De. Over all, my favorite stock like rom though.
Sent from my Optimus G using XDA Premium 4 mobile app
Hi all i know someone will not be happy i have asked this question that is probs one of the most asked on here from Nubs like me lol.... Basicly i recently got my rooted htc one m8 S-on back, i was planning to sell it so tried to remove the Root from the phone i have somehow managed to Brick it, its under HTC_001 it didnt have a main fw number so i did what others have and read it from the about software section on my phone wich give me 1.54.401.10....... Well i ended up download that one something went wrong either way now im left with a phone that only goes into Hboot and i can access the recovery what is TWRP i can connect the usb and get onto my Sd card using mount but ive tried and tried to get no joy.... Sorry for the nub questions i did go abit out of my knowledge people say ADB on other forums, im not very clued up with it other than changing the recoverys ive watched youtube vids ect no joy Please can someone give me a Simple Tut or link to help me ive tried following threads and still got no joy http://forum.xda-developers.com/showthread.php?t=2701376 So now i ask the PRO'S please help lol
mikem2273 said:
Basicly i recently got my rooted htc one m8 S-on back
Click to expand...
Click to collapse
Got it back from where???
mikem2273 said:
Sorry for the nub questions
Click to expand...
Click to collapse
No need to apologize for the n00b questions. However, the huge run-on sentences are another story. Take some time to type a post with proper punctuation and sentence structure. It will make it easier for you to get you point across and for us to help.
mikem2273 said:
now im left with a phone that only goes into Hboot and i can access the recovery what is TWRP i can connect the usb and get onto my Sd card using mount but ive tried and tried to get no joy....
Click to expand...
Click to collapse
Tried and tried what? If you aren't specific in what you have done, what are we supposed to do, guess? Be detailed and be specific when asking for help.
You aren't in bad shape at all if you have recovery and can mount SD. Just put a software 1.x based ROM on the SD and flash it in TWRP.
---------- Post added at 01:48 PM ---------- Previous post was at 01:42 PM ----------
mikem2273 said:
people say ADB on other forums, im not very clued up with it other than changing the recoverys
Click to expand...
Click to collapse
Just use the XDA search function, and search "adb beginner" to find a number of good adb/fastboot tutorials aimed at just that, beginners.
But if you've used fastboot to install recovery, the other commands aren't any harder. Its just a matter of just knowing what commands to use for a given situation.
If you can mount SD, I don't even think you need adb. But its a very valuable tool to know, and can help in a lot of situations.
Thanks for the response, well i tried a stock rom im not sure where i went wrong tbh i put it on the internal sd and the file would not show up inTWRP i then had a back up and copied and pasted the files from the Stock rom into the back up and tried to install it and thats where it messed up i am crap at this kind of thing i rooted it no problem i thought unrooting would be easier, adb is a bit confusing with me if there was a way i could put a file onto my sd card in zip format and open it i just tried the original one i downloaded to get loads of red commmads saying
E;unable to stat '/and-sec/;555?.??/m?? and so on a load more random numbers
Sorry i am not very on ball with this should of just left it how it was lol
Right update time...... so i have got the phone back working by flashing a new rom but my phone massively lags on boot up, i think my firmware files are corrupt i cant get wifi either ive red about fixes but all need S-off yet i dont want to pay 25 dollars is this the only way to do this ?? i cant put firmware files on my hone without the s-off such hard work and effort would rather pay someone to fix it lol
unable 2 load my one m8 to fasboot
pls, i av bein unable to access fastboot on my device; i cant unlock bootloader,s-off e.t.c......what can i do; i really need help...
d screen displays black with fastboot mode @ d lower left corner
nnamathy said:
pls, i av bein unable to access fastboot on my device; i cant unlock bootloader,s-off e.t.c......what can i do; i really need help...
d screen displays black with fastboot mode @ d lower left corner
Click to expand...
Click to collapse
Dude ..who are you talking too ?? your post is useless and makes no sense.
Start your own thread ... post an exact description of what you did and whats wrong along with pictures / bootloader / anything that might be of some help
mikem2273 said:
Thanks for the response, well i tried a stock rom im not sure where i went wrong tbh i put it on the internal sd and the file would not show up inTWRP i then had a back up and copied and pasted the files from the Stock rom into the back up and tried to install it and thats where it messed up i am crap at this kind of thing i rooted it no problem i thought unrooting would be easier, adb is a bit confusing with me if there was a way i could put a file onto my sd card in zip format and open it i just tried the original one i downloaded to get loads of red commmads saying
E;unable to stat '/and-sec/;555?.??/m?? and so on a load more random numbers
Sorry i am not very on ball with this should of just left it how it was lol
Click to expand...
Click to collapse
You sentence structure (or lack of it) is still making it hard to understand what you are trying to tell us. If you can't even be bothered to type a proper sentence; how do you expect us to take the time to help you? Honestly, most other requests for help on this forum get much more response. I think many folks are just walking away from this thread without helping, because they can't understand you due to your writing style.
Your lack of specificity also makes it crippling to try to help. What stock ROM, and where did you get it from?
If you got a stock nandroid, you then need to extract the files from the zip and place them in exactly the right folder, otherwise TWRP won't see it. And you do not use the TWRP "INSTALL" function with a stock nandroid, you use the "RESTORE" function.
A flashable ROM zip, in contrast to a nandroid, can be placed anywhere on internal storage or removable SD, and TWRP will see it and flash it using the INSTALL function.
Its very easy to push a ROM zip to the phone with adb. I already told you how to find BEGINNER tutorials on how to use adb. Don't expect to be spoonfed information that is already readily available on XDA. If you have a specific question regarding adb, ask it. Otherwise just saying "adb is confusing" is not going to help you.
---------- Post added at 11:05 AM ---------- Previous post was at 11:03 AM ----------
mikem2273 said:
Right update time...... so i have got the phone back working by flashing a new rom but my phone massively lags on boot up, i think my firmware files are corrupt i cant get wifi either ive red about fixes but all need S-off yet i dont want to pay 25 dollars is this the only way to do this ?? i cant put firmware files on my hone without the s-off such hard work and effort would rather pay someone to fix it lol
Click to expand...
Click to collapse
Your firmware files aren't "corrupt". They are just outdated, and don't match the ROM your flashed.
OTAs are available for your version. An option if you don't want to s-off, is to return to stock ROM and recovery, and OTA to update the firmware. It seems you are having problems installing the stock nandroids, but I think you just need to properly follow the instructions from the stock nandroid collection thread.
Otherwise, you are stuck running ROMs that are based on 1.x software. Running anything more recent will result in long boot times and broken WiFI, as you've experienced.
Dammit i know excatly where i went wrong and what you meant by you have to open the file up and adb the right files to the right places............ $%$% i have now fully ruined the phone i think i turn it on i get a White screen the phone then goes full black screen and does nothing...... i have connected the phone via usb to the laptop, the laptop notices the phone and usb i click on the phone in my computer nothing is there when it opens i have also gone onto adb and done the "adb devices" and it does not show on the list, is there anything i can do with this now, i am very gratefull for the help even though i haven't been specific and guessed my way through alot of it like a nob,
adb only works when booted into OS or in recovery.
Alternately, if you have an SD card reader, use it to load a ROM zip onto the SD from your computer. Then place SD in the phone, boot TWRP, and flash the ROM.
redpoint73 said:
You sentence structure (or lack of it) is still making it hard to understand what you are trying to tell us. If you can't even be bothered to type a proper sentence; how do you expect us to take the time to help you? Honestly, most other requests for help on this forum get much more response. I think many folks are just walking away from this thread without helping, because they can't understand you due to your writing style.
Click to expand...
Click to collapse
At this point I have to assume it's an inability to communicate clearly, not an unwillingness. You have a lot more patience than most for even trying.
redpoint73 said:
adb only works when booted into OS or in recovery.
Alternately, if you have an SD card reader, use it to load a ROM zip onto the SD from your computer. Then place SD in the phone, boot TWRP, and flash the ROM.
Click to expand...
Click to collapse
@redpoint73: I'm in his exact same position...hopefully, I can communicate this a little better...at least I'll try. LOL
Background: Rooted, S-Off (via Sunshine), , TWRP 2.8.1.0, was running CleanROM (on the 444 firmware) and tried installing Vanir 444. I did a factory reset and I'm pretty sure I might have went into Advanced and wiped System as well (from the reading I've done, I shouldn't have done that) ROM installed no problem, Gapps installed no problem, installed SuperSU 2.40 at the end and rebooted. When the phone went to reboot, it went to the usual white HTC screen, then went black and never moved past that point.
As you advised in an earlier post, I held down Power/Vol up until the white HTC screen appears. I waited until the screen went black then held Vol down for several minutes but bootloader never came up.
My computer recognizes the phone when I plug it in, Windows explorer shows both "Internal" and "SD card", with Internal basically empty and SD card showing all my files. Since I can't get into bootloader, "adb devices" doesn't bring anything back.
Any suggestions you might have would be hugely appreciated - hoping to avoid having to head to a local Verizon store and see what they can do! If I missed any background or details, let me know and I'll elaborate.
TIA!
sigmaxaa said:
@redpoint73: I'm in his exact same position...hopefully, I can communicate this a little better...at least I'll try. LOL
Click to expand...
Click to collapse
I can't imagine it being any worse than the previous guy!
Seriously though, your post would have been better served in its own thread, or almost any other relevant thread. Couple reasons for this:
1) My experience, when folks say they are "in the exact same position", "I have the same problem", etc. they are in fact virtually never the exact same condition. There are far too many variables (M8 variant, hboot version, software/firmware version, how you got to the current condition, and many more) for your condition to be "exactly the same". And for that matter, when folks say they have the "same problem" it in fact is most often a completely different cause, and different fix. Do yourself a favor, and don't say "me too" when posting a problem.
2) The OP basically chased everyone away with his horrible diction. Help threads in this section normally get considerable traffic and assistance. I'm the only one helping this guy, because apparently I'm the only one patient enough to try to decipher his ramblings. By attaching your post to his, you've pretty much cursed your issue to obscurity as well.
sigmaxaa said:
As you advised in an earlier post, I held down Power/Vol up until the white HTC screen appears. I waited until the screen went black then held Vol down for several minutes but bootloader never came up.
Click to expand...
Click to collapse
If you got this from a post of mine in another thread, its (normally) accompanied with the statement that failure to get into bootloader is virtually always a matter of user error (not getting the timing right). Simply stated, if the screen still comes on, you can get into bootloader. So just repeat the steps until the bootloader screen comes up. You either didn't start pressing vol down fast enough; or let go of it too early (don't let go until the bootloader screen appears).
sigmaxaa said:
My computer recognizes the phone when I plug it in, Windows explorer shows both "Internal" and "SD card", with Internal basically empty and SD card showing all my files. Since I can't get into bootloader, "adb devices" doesn't bring anything back.
Click to expand...
Click to collapse
Once you get the timing right to get into bootloader, and from there recovery, we should be in good shape.
You can likely recover by transferring a known good ROM to the SD card, and just flashing from custom recovery. Or just restore your nandroid.
sigmaxaa said:
Any suggestions you might have would be hugely appreciated - hoping to avoid having to head to a local Verizon store and see what they can do!
Click to expand...
Click to collapse
I doubt Verizon can help. And since the phone was put into this situation by your own actions (mods you performed) its really your responsibility to fix it, not theirs.
redpoint73 said:
I can't imagine it being any worse than the previous guy!
Seriously though, your post would have been better served in its own thread, or almost any other relevant thread. Couple reasons for this:
1) My experience, when folks say they are "in the exact same position", "I have the same problem", etc. they are in fact virtually never the exact same condition. There are far too many variables (M8 variant, hboot version, software/firmware version, how you got to the current condition, and many more) for your condition to be "exactly the same". And for that matter, when folks say they have the "same problem" it in fact is most often a completely different cause, and different fix. Do yourself a favor, and don't say "me too" when posting a problem.
2) The OP basically chased everyone away with his horrible diction. Help threads in this section normally get considerable traffic and assistance. I'm the only one helping this guy, because apparently I'm the only one patient enough to try to decipher his ramblings. By attaching your post to his, you've pretty much cursed your issue to obscurity as well.
If you got this from a post of mine in another thread, its (normally) accompanied with the statement that failure to get into bootloader is virtually always a matter of user error (not getting the timing right). Simply stated, if the screen still comes on, you can get into bootloader. So just repeat the steps until the bootloader screen comes up. You either didn't start pressing vol down fast enough; or let go of it too early (don't let go until the bootloader screen appears).
Once you get the timing right to get into bootloader, and from there recovery, we should be in good shape.
You can likely recover by transferring a known good ROM to the SD card, and just flashing from custom recovery. Or just restore your nandroid.
I doubt Verizon can help. And since the phone was put into this situation by your own actions (mods you performed) its really your responsibility to fix it, not theirs.
Click to expand...
Click to collapse
Thanks for the reply, I do appreciate it. I was able to get it working (after dozens of attempts) and you're absolutely correct...it's all in the timing.