[Q] Help Unrooting! - Sprint LG G2

Please don't refer me to any more threads or forums........
I'm sure this has been done and done and talked about but I've been reading the **** out of forums and comments for a few hours now and trying to unroot my Sprint LG G2.
I had it running stock like a champ. rooted it. worked great. then I was attempting to flash lollipop and it required a recovery update (No Problem) I downloaded the correct files and bam! it says your phone is not rooted this requires a root (or something like that) I was already rooted SuperSU installed and root checker said I was fine. so what the hell I swipe to root while inside recovery and it goes to some black screen with tiny text saying fastboot: processing commands and won't leave the screen. I tried booting into recovery and same thing happens. Tried to reboot normal and I'm stuck on the LG logo with my led flashing between blue and green slowly. I CAN boot into download mode and I'm following this
http://pastebin.com/WTm1xFXz
and this
http://forum.xda-developers.com/showthread.php?t=2687929
to unbrick but having this error "Failed PreviousLoad()
Did I not get the right .dll file? I doubt it cause I only saw one...or is it the wrong .tot file? there was 3 or so
http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware
Please help!
When i'm in download mode the phone does say I am rooted. is there a way to just re-flash recovery and restore from my backups I did before all this? if I have to wipe this thing clean and start over I don't really mind I just need to get my phone back haha this is the first time this has ever happened to me and I consider myself tech savvy so idk what I did here (except re rooting in recovery like an idiot) thanks so much!

First question, is the download mode you see with a small status bar or the big one?
If you have the big one, download mode should work. The f flash software will verify the tot file. If that goes through you should be golden.
When it asked you in TWRP to root, that is a message telling you system or ROM file did not take.
If you want cm12, use zv8 tot. Root, auto-rec, update TWRP with blastgator bumped TWRP 2.5.1. Flash cm ROM or aosp, then gapps. And go

Related

CM10.1 crashed and softbricked itself, can't access the file system

I have Cyanogenmod 10.1 (stable) installed; the other day it crashed while I was on Instagram, rebooted itself, and wouldn't go past the spinning circle screen. Tried rebooting it, now it won't go past the screen before that, with the blue Cyanogenmod man and the Samsung logo.
I have TWRP 2.5.0.0 installed with it, which I don't know how is possible being that the file systems are incompatible, so unless I used Odin to install CM10.1, I don't know how I did it without installing Clockworkmod Recovery over TWRP.
I've been trying to fix it for a couple days now (I'm kicking myself for not getting around to posting here sooner). When I go into TWRP it asks me for a password (which I've never set, I assume it's asking me because that's all it knows to do when the file system is incompatible), which I click cancel at every time, and when I try to do just about anything (including installing new ROMs or recoveries from within TWRP) it gets errors when trying to mount any partitions on the device, so I can't change anything on the phone at all.
I've tried re-installing TWRP AND Clockworkmod Recovery with Odin, and they succeed, but when the phone tries to reboot, the screen just turns off and nothing happens, and I have to take the battery out to do anything else.
So right now I'm totally screwed unless I can fix this thing. I'd like to not have to drop 200 on a Nexus 4 after only a year or having this phone I bought brand new, especially with the Nexus 5 already coming out later this year...can somebody help me???
EDIT: I should clarify that I can access recovery and download mode
If you can get into download mode you can flash a stock image to your phone and restart from scratch. Download the proper stock image from here http://forum.xda-developers.com/showthread.php?t=1968625 and flash it in odin.
FoxTrotz said:
If you can get into download mode you can flash a stock image to your phone and restart from scratch. Download the proper stock image from here http://forum.xda-developers.com/showthread.php?t=1968625 and flash it in odin.
Click to expand...
Click to collapse
I should've clarified that I've tried this with a bunch of roms, and it just shows SBA2 in the status box forever. I left it for a full hour before and it never changed.
According to this page http://www.alliance-rom.com/community/wiki/bricked-android/ reformating your external sd card may help. It also links to something I personally have never heard of but apparently this: http://forum.xda-developers.com/showthread.php?p=15330252 can help unbrick any samsung phone that's flashable with odin.

[Q] Unique Situation ATT Galaxy Note 2 Help

Ok, this is my first post so forgive if this is in the wrong section...
I have a friend's Galaxy Note 2 ATT that was stuck on the Galaxy Note 2 Boot screen, and it wouldn't go any further.
Because I work for Samsung at the Samsung Experience Shop, I tried running it through our smart reflash tool
-----> This didn't work because it would fully download it onto the phone, but when it got to the Android with the thing spinning in its chest, it would stop and ALWAYS freeze halfway.
Next step I tried doing was going through Samsung Kies and downloading the stock OS and load that, but the same Android with the spinning thing in its chest would show up and it would freeze.
Due to this guy being my friend I told him I would try anything to get his phone to work again (root, to custom recovery, to custom rom)
My steps so far:
1. I have successfully rooted my device via ODIN 1.85 by using CF-Auto-Root
2. Afterwards, I loaded on a custom recovery via ODIN 1.85 which now is philz_touch_6.07.9
Here is my problem now, I've tried searching everywhere and I can't really find the answer...
Whenever I try to side load a rom through ADB through Android tools (its in the right directory and everything because it transfers over), I keep getting an error message "E: Error in /tmp/update.zip (status 7) Installation Aborted."
Now before I get that error I get stuff like getprop("ro.product.device")==t0lte" ||getprop("ro.build.product").... etc. and it goes on and on.
So far the ROMs that I have tried were Cyanogenmod 10.1 and the Pacman Rom, and yes, both are for the correct device like the model name/number match up. And now how I said I thought I rooted the device, whenever I try to reboot into recovery via Philztouch, it says at the top Root Access is missing. Root device, and I click yes. When it reboots into recovery and I want to turn the phone off again, it still says Root Access is missing.
I am open for anything really. My friend just wants his phone to work again. and I've literally exhausted all of my ideas as I keep running into the same issue.
What am I doing wrong? and is something like this possible to fix? Or is my friend SOL?
Thanks for all the help. It's much appreciated.
Your recovery is outdated. Status 7 error.
I use TWRP from the original development section.
rangercaptain said:
Your recovery is outdated. Status 7 error.
I use TWRP from the original development section.
Click to expand...
Click to collapse
+1 to this^^^^^
Look here»»» http://forum.xda-developers.com/showthread.php?t=1981198
And why not give him something stock instead of a CM Rom??[emoji37]
Plenty of stock 4.3 Rom's in the development section...
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Good advice ^^^^ for your friend.
Ok, thanks for the direct response. I've downloaded the latest TWRP recovery and when I try to push it through ODIN, I still have PhilZ Touch 6..? Sorry, I feel like I'm skipping something simple...
according to a guide, I have to make sure when I'm pushing a custom recovery through ODIN I have to leave Auto Reboot and F. Reset Time UNCHECKED. I made sure they were, and for some reason after it says PASS and thread successful 1 failed 0. When I disconnect the phone and turn it back on into recovery mode, I still has PhilZ Touch...
Use your recovery to flash TWRP. There's a zip version and an odin version.
Ok, I got stock recovery on there just by redoing the CF-Auto Root package through ODIN.
I figured well I can apply the ROM the adb through the stock recovery...
It was going well until I got this error. The last line before the error stated:
"Veryfying update package..."
Error:
E: failed to verify whole-file signature
E: signature verification failed
is that due to the fact that i'm using stock recovery?
In the mean time since that didn't work I'm going to flash TWRP and hopefully that fixes the issue.
I'm kinda just documenting my steps here in case anyone wants to follow and chime in if i'm doing something wrong.
Thanks for the help guys!
************3AM EDIT*****************
Ok so I managed to get TWRP 2.7 on the device as I needed the ability to adb sideload the update.zip to the phone since I can't boot into the phone's OS whatsoever.
This is the error I'm receiving now:
Checking for MD5 file...
Skipping Md5 check: no MD5 file found.
then it restarts and I'm stuck at the Samsung GALAXY Note II screen... what's my next step..? Find a different ROM?
**********Another Edit**************
It has just come to me, I shouldn't have to adb sideload the update.zip or the custom rom... even though I can't get into the phones OS and can't copy and paste to the root of the device. Can't I just copy and paste it to a micro SD card and mount that, and then apply the update from there? And as far as those errors I had earlier, I'm still not sure why I received them...
Again, thanks for all the help
Adb won't work if USB debugging wasn't enabled.
In TWRP you can disable md5 checking.
And you don't unzip the zip file.
Thanks for the reply. ADB didn't work because, in fact, since I haven't been able to turn the phone on, I know USB debugging isn't turned on.
And as far as having the MD5 check, it is unchecked.
I received a success message. However, when I try to boot the phone it still gets stuck at the Samsung Galaxy Note II screen.
******Edit******
Ok ended up using a different ROM, I think PacMan rom? It seemed to work until it got to extracting system files and then the phone sits for a couple minutes, screen turns black. And when I try to wake the screen, only the back and menu buttons come up...
Another thing, even though I've already rooted my device using CF-Auto-Root, When I reboot my device with TWRP I go to reboot and then recovery. Then it warns me saying no OS bla bla bla, and then it says it notices that my phone isn't rooted? And that SuperSU isn't on the device. It asks to install it by swiping. I swipe it starts to install, phone reboots. When I reboot it again, it still tells me that the phone isn't rooted. And with the phone not being rooted, I'm coming to the conclusion why I'm having trouble trying to flash Roms.. Is this a possibility?
Why are you using ADB? just drop the .zip for the ROM you wish to flash onto a micro SD card, and flash from within the TWRP. Don't try to extract the .zip whatsoever.

[Q] e980 rooted + TWRP recovery, flashing rom issues

I rooted my LG Optimus G Pro 4.4.2 via TowelRoot, installed SphinX, FreeGee, and installed TWRP recovery. I then flashed Cyanogenmod 10.2, and it (seemingly) worked well. However, I seem to have lost the ability to call others and recieve calls, but texting works, and I am disappointed with the battery life. It seems to not support reading the tilt of the phone, which I use with some of my paid for games.
So I flashed Beanstalk, and the installation seemed to work well, but on the reboot (after I had wiped before install and after, before rebooting) it gave error messages saying google services closed, and wizard closed. It gave me the option to report on both issues, but each time I closed one error window, the other would pop up, like in an endless loop. So, thankfully, reboot into recovery was a power button option in that rom (wish they all did that) and I then flashed back to CyanogenMod10.2. So I then decided to update Cyanogen to 12 via the built-in upgrade, and it also did the same thing, giving the same error messages in a continuous loop. So I finally was able to power up into recovery (for some reason, it seems to not work every time after shutting the phone off).
I am wondering if I can just flash back to the stock, and then debloat, or, better yet, can I just flash 4.1.2 to this device (I don't know if it ever had that OS) then root and debloat, as I do wish to use my wiimote. I have looked at the various methods to return to stock, but they seem to be quite confusing, as I don't read text-type very well, and most of the descriptions are typed this way. I would appreciate any assistance with getting these issues taken care of.
supersu unroot
Sorry for the double post, but I read that using supersu to unroot would brick the phone. Will this method simply return the phone to stock, or will it damage it?
Ok, so if I am understanding this correctly, to return an e390 to stock, you:
1. download and unzip the lg flashtool
2. download and install current lg drivers
3. download the dll and stock image
4. put phone into download mode and then plug into computer
5. run flashtool + make sure device manager port is com41
6. select dll and firmware, and finish
7. flash the modem-can this only be done with root?
What is step 7? Flash what modem?

HELP! Fully wiped. Only Recovery mode is possible. Help me flash a stable ROM.

What I've done:
1. Tried LGNPST method but phone never showed up in the software
2. Tried flashing with LG official tool. That always resulted phone disconnected.[I did put my phone into download mode]
3.Tried almost all KDZ_FW_UPDATE methods they always stopped either in not responding-> close program OR extraction error
4. Tried sideloading using adb but they also resulted in "bad file" even push didn't work saying no permission to write(I think)
for adb I tried converted .zip of kdz using some guide in xda.
My phone is totally clean now. I can boot to Recovery or Download Mode. There's no file that's flashable right now. I'm in Philz touch recovery
This actually happened while I was flashing to unlock bootloader and charge went low.
I desperately want it to function properly. Please anyone with any new or updated methods, help me.
When normally trying to boot up, Google logo comes and phone switches off.
I was in F180L converted to E975.
I've INDIAN(20a) version kdz also european(10h) and korean(30e).

V410 7.0 LTE bricked

Ok guys I am pretty sure I fubar'd my tablet.
I am stuck in a recovery loop. When I start the tablet it just goes back into recovery. Which if I still had TWRP I think I could still do something, but I flashed cyanogen recovery trying to flash cm13 since I cold not get anything else to work. I cannot boot into download/firmware update screen. The screen just flickers a little and goes dark.
A little background:
Started when tablet forced install of 5.0 update and I was in a recovery loop. I flashed 410 test build, rooted, flashed twrp, installed stock rooted ROM. Everything was fine. Then tablet did it again, this time I just flashed rooted ROM and factory reset. Even took the steps to fix the white lines and storage issues. Was working fine. Got home a few days ago and I was in a recovery loop again. But now I don't have the bootloader screen/download mode/firmware update screen (whatever you want to call it) so last night i tried to download cm13, Gapps and cyanogen recovery with no avail.
I can access adb on my PC while in recovery, but when I try to access ADB shell I get unauthorized something or other. Because I cannot authorize USB debugging, because ROM won't boot. I tried to flash stock rooted ROM from cyanogen recovery and it says not signed or something like that.
Does anyone have any ideas? I really think I have screwed the pooch here.
sent from a device using an app
title
if you have a stock recovery image flashing it is easy, i had a LOT of troubles with my v410 and still am working with it. i have mine rooted, just with TWRP though, i cant use xposed framework, which negates why i rooted this in the first place. anyway, through much grit and determination flash your stock image after wiping what needs to be wiped and doing all other necessary things. Then, you must download kingo root, supersu, superuser. flashify would help with the flashing i hear, but it has troubles with the v410. kingo root was an apk i managed to find buried under a million viruses on the 34th page of google..or something. rooted mine in one click, from stock to reboot to twrp root.. many glitches.
I need help myself, deleted my "Phone" system app, causing me to lose connectivity with my data plan. cant seem to restore it, and flashify nor twrp has been able to flash a custom recovery, or a backup, im at a loss.
Help? We seek the same thing.
Ok but how do I flash the stock recovery image. I can't use fastboot. ADB says I am unauthorized.
sent from a device using an app
Anyone have any other ideas?
I am at a complete loss. I am by no means a developer, but I do know my way around. I really think I have FUBAR'd this one.
Kind of stinks, I give up. Anyone want a bricked v410?
Sent from my Galaxy Tab 2 using Tapatalk

Categories

Resources