Please please please help!!! Lg G3 model sv985 running lollipop 5.1.1
So one day I wanted to connect my ps3 controller to my ps4. I found out how to do it but it requested my phone to be rooted. So after a couple of days trying to root my phone I finally found a solutions. I used the kind root method. After getting root access you are required to put your phone into recover mode. The problem I am having is when I go into recovery mode all I get is an error message stating "secure boot loading error 1003" then proceeds to go to a black screen with the notifications lights blinking red and blue. Then I have to take my battery out and reboot my phone that way. It starts up normal but twrp does the same process as do other rebooting apps. Today I got the update to install marshmallow 6.0 and it also needs to go into recovery mode. When I try to reboot the same black screen appears. I finally came to agreements with myself to just get rid of root and go back to kitkat then upload 6.0. My problem here is the program you need to download to switch back requires a password and user name. Which according to the steps, you just download a file then switch it to the program and shouldn't need a password or username anymore. Every time it fails. Sorry kinda spaced what it's called. (it's the program needed to downgrade sorry I forgot the name) I've been at this for about a month and now my phone won't even get notifications. The root totally messed it up. I wouldn't mind if I could get super su to work. Basically my question is, how can I get around the secure boot error 1003 to get into recovery mode. Even if I just take my root loses and uprgrade to 6.0. All I need is to reboot, it shouldn't be so hard. All the YouTube videos I have found are all in Spanish that get good reviews but I can't understand most of the conversations. Thank you to the XDA for everything you guys do. Your awesome!
Related
long story short. I tried to flash a newer updated copy of SuperSU or whatever to get root back after updating to 4.0.4 earlier this week.
Once I did that I was able to get back into the operating system and run Root Checker. Everything passed. I then tried WiFi tether and it kind of locked up on me for a bit. then I was able to stop it and exit out of it. I Force closed the programs. Life was good.
For whatever reason I restarted the tablet. once I did that I was stuck on the Samsung screen for at least 15 minutes.
I then tried to re-run root file and then the new updated SuperSU. Then everything went all to hell.
Then I get a message that says
"Firmware upgrade encountered an issue. Please select recovery mode from Kies & try again."
Now I can not boot into anything but recovery...
I am able to with that message on the screen, connect to Odin and proceed to run the "factory" restore. However it has been sitting at what I would assume is about 5% or so for a long time. at least 20-30 minutes. Should this take this long?
And is there anything else I can do to do a restore? I am fairly new to this tablet and I use it for work and of course I have a super full day of work tomorrow and really got to get this thing back up and going.
So I just wanted a simple root to get root access on my NOTE3 to stop some apps from auto starting.
I was at KK and went with one of popular youtube channel vids as I have done many times before. The only difference this time, is that I have my work email tied in and I am required to encrypt the phone. I assume that this is the problem here.
My phone asks me for my encryption password, and then the green android guy comes on the screen for a second, then disappears, then fade to black.
Nothing else happens, the phone then powers off.
I tried to revert back.
I quickly found out that I cant go back to MJ4 (at least not easily, I tried already, this fails with error basically stating that I cant go back).
I am able to apply (N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 - KK), but this is giving me the same results as the root (phone boots, asks for ecryption p/w, takes p/w, then powers off).
Is there anything I can do to get my phone back to a working state?
Any and all help is and will be greatly appreciated.
dd2fourteen said:
I am able to apply (N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 - KK), but this is giving me the same results as the root (phone boots, asks for ecryption p/w, takes p/w, then powers off).
Is there anything I can do to get my phone back to a working state?
Any and all help is and will be greatly appreciated.
Click to expand...
Click to collapse
I am unfamiliar with encrypting phones, but I believe you should try to use the full-restore from rwilco12.
I hope this works for you.
Pls help me root my zte obsidian running android 5.1 Model NO. Z820
I need help too
I also have ZTE obsidian tmobile and really want to root it i cant do much because it only comes with 4gb of space and i cant move apps to the SD card till i root Please help find a root
yeah same issue here all say that it cant after like 10-15 mins its just like nope sry
have you used this
http://forum.xda-developers.com/cro...oolbox-android-one-toolkit-one-click-t3030165
Yes, I tried. Its not working.
Is there any other way. I am desperate. It doesnt allow to move the Apps to SD card. There is no way. Locked in 4GB
I have a z820 in need of root as well. I've tried everything, including the link up there, and so far.....nope. Nothing. No apps to SD for me either.
Zte can't root for ****!!!!
I'm so mad because I really tried everything even a computer won't let me tried everything there to like why would the make a zte that can't even move your games or pictures or music to your SD card knowing danm well everybody gone need like we only got 4g that's nothing so what are we so posted to do delete stuff that we like.to trade for the other that we really don't need **** I'm pissed right now I know y'all are to but if anybody finds something please send me the info or con me by [email protected] thank you:good:
Needs update
This Phone really needs an update, it reboots and sucks, we can't even get into fastboot or anything to try to unlock the bootloader someone needs to make this possible because who in the hell uses only 4gb of storage, apps are so big and you can only download like 3 apps then you have to get rid of something if you want another app and its dumb so please someone..HELP US :crying:
Throwing my post up here so I can follow. Need root bad on this thing. I am using lite versions of every app. Lol
Same problem w/ ZTE obsidian..tCan't move to SD card. Anybody figure somethcing out yet?
I've gotten Kingroot to attempt to root it once and the results varied. Usually got 16% but the highest was almost 30% but I can't even get kingroot to even root it anymore.
The phone is not going into fastboot at all. I think the bootloader is locked. The phone will never be rooted.
I might of found a way, but it's untested so, proceed at your own risk, I am not responsible if your phone becomes bricked.
Enable developer mode and tick "OEM Unlocking" in the developer menu
Download SuperSU update zip from Chainfire's site and put it on your sdcard (internal won't work)
Power off your phone and hold power and volume up
Select recovery, wait for the android with the lid open to show up
Hold power and volume up for a couple seconds and let go
A menu should pop up, if not try again until it does
Select "update from sdcard"
Select the SuperSU zip
Let it flash the zip (shouldn't take long)
Choose reboot
See if SuperSU is installed and test that it works
Again, this is untested and would need a couple of people testing it to make sure it works flawlessly, so if this worked, please post that it did.
Nope. Thank you though.
picsles said:
Nope. Thank you though.
Click to expand...
Click to collapse
Any type of error happen or did it not allow it to flash at all?
I can't even get to recovery. Gives me the choice then goes to dead android guy.
Sent from my LGL21G using Tapatalk
Musicmanmike said:
I can't even get to recovery. Gives me the choice then goes to dead android guy.
Sent from my LGL21G using Tapatalk
Click to expand...
Click to collapse
You have to hold down power and vol up for like 2 seconds when you get to the dead android, then you'll get the recovery menu.
When I try to install the update package, I get 'opening update package' followed after less than a second by 'installation aborted'.
I powered down from the Developer Options screen with OEM unlock turned on when trying to update - it appears to turn off during boot as it is off again on restart.
Any suggestions? I looked at the logs that are visible from the recovery screen but they did not seem to have anything useful. Are there logs I can retrieve via ADB to see what the issue is?
My phone has build B18.
Kurrelgyre said:
When I try to install the update package, I get 'opening update package' followed after less than a second by 'installation aborted'.
I powered down from the Developer Options screen with OEM unlock turned on when trying to update - it appears to turn off during boot as it is off again on restart.
Any suggestions? I looked at the logs that are visible from the recovery screen but they did not seem to have anything useful. Are there logs I can retrieve via ADB to see what the issue is?
My phone has build B18.
Click to expand...
Click to collapse
OEM Unlocking is always on for me even after restarts but I haven't tried to flash SuperSU yet. You might wanna get a logcat while doing it and post it here to see if anyone knows what the problem is. I have an older build of the phone (B03) but I dunno if it matters or not.
EDIT: Also every new Kingroot build allows you to attempt to root it for like 2 days and then it just can't for some reason but the thing with 18% still happens.
LUModder said:
You might wanna get a logcat while doing it and post it here to see if anyone knows what the problem is. I have an older build of the phone (B03) but I dunno if it matters or not.
Click to expand...
Click to collapse
The logcat I am familiar with is in ADB. The only way I can find to access the phone from recovery with ADB is to select the flash from ADB option, which puts the phone in sideload mode where you can't pull data off. I was unsure if trying to load the ZIP that way would brick the phone so I haven't tried it.
I also tried using Fastboot and it doesn't recognize the phone at any time.
Is there another way to capture what is happening with the update?
I tried selecting restart in bootloader from the recovery menu with the phone connected to the PC. It stayed at the ZTE splash screen for over 10 minutes but neither fastboot nor ADB was able to communicate with it. I tried various key combinations without effect and finally ended up pulling the battery. Maybe it just froze up during boot for some reason.
I have tried every one-touch root I can find, none of them work. All the manual guides start with unlocking the bootloader - which I can't find any info on for this model. Based on the partition info, it's definitely locked: it has 27 (!) partitions including names like seccfg and oemkeystore. Is this normal for a lollipop device?
Well, I just got this phone this week. It was actually a gift in fact since I broke my last phone a week before this.
As soon as I got used to the new phone. I started playing with it's guts. I rooted it with Kingroot, since it has never failed me before. Installed Xposed Framework, and flashed the 5.1.1 stuff for it to run. I had to flash TWRP to flash the Xposed Framework stuff (for some reason I couldn't get the sideload to work). Got a few modules for it. Got all my usual apps such as Facebook, ES FM, Instagram, etc. Got a few games. Spent some hours playing the games. You know, all the stuff you do when you get a new phone.
Then, I decided it was time to switch from Kingroot to SuperSU, as I do with every phone I root with Kingroot (and there were a few). I did it the same way as I have before, using w0lfdroid's method (I can't post links yet). The Kingroot app didn't automatically uninstall, but SuperSU was working. So, I uninstalled Kingroot manually with ES FM. That caused a lot of "unfortunately, com.kingroot.kinguser has stopped" dialogs that never stopped coming, and I decided a reboot might fix it.
I was wrong, the reboot did NOT fix it. It turns on, goes to the LG logo screen, goes to the Metro PCS screen, dims the background, [all of that within a minute and then] vibrates once, and then no sign of anything else. However, the phone does seem to be alive. When I plug it into USB the MTP starts working. It's also listed in adb's devices list. I can even use adb. I used adb to boot it into bootloader/fastboot, and it's even listed in fastboot's devices. It does still charge.
That damned Kingroot, I'll never use it again to shortcut through rooting. It has always worked, and I've been able to swap it with SuperSU everytime before this one. I just don't want to risk this happening again.
I'm lost on what I should do about this. What would you fella's do?
_____________________
I do have a warranty on it, but I've obviously voided that above. I could lock the bootloader back with fastboot (using "fastboot oem lock") so they don't see anything significant right away, but they could always dig in to see that I've done a lot of changing. Hell, all they would have to do is boot into recovery and see TWRP... xD
Well, I just locked it back ("fastboot oem lock" ) and I think my phone is actually coming back on, it's currently on the "Android is starting" screen optimizing app 12 of 151.
I'm just hoping the lock command doesn't reset my device like the unlock command obviously does... I guess I'll edit this with my results in like an hour when this is done (not literally an hour)!
EDIT 1: 10 minutes later, it seems to be stuck on "Starting apps." after it finished optimizing.
EDIT 2: 10 more minutes later, I'm pretty sure it was indeed frozen on "Starting apps.", so I took the battery out. I turned it back on only to see it still freezing on the Metro PCS screen... Well damn.
EDIT 3: Yet another 10 minutes later, still stuck on the Metro PCS screen...
EDIT 4: I no longer have USB debugging access, since I re locked the bootloader (which seems to have reset it, again). So now I also do not have access to fastboot. I think I screwed myself...
unbricking
@ goatitalone can help you unbrick your device. I still have the files if he is OK with it I can help you too or if he can write a tutorial on here that would be great. @ goatitalone?
I have same exact problem howisit fixed?
Magik1 said:
I have same exact problem howisit fixed?
Click to expand...
Click to collapse
do you still have adb? if you do i can send a twrp backup
its been listed kingroot will brick you, currently the oneclick is compatible with our devices. you should have done some searchign before tinkering with your device in my opinion, if youre smart enough to unlock your bootloader .. you should be smarter in researching root methods.
youll have to reflash your device, contact goitalone - as noone that he's helped will help you with getting those files.
as for it being an ms3302 device.. i havent seen that device under our series.
Use this to unbrick http://forum.xda-developers.com/android/development/stock-firmware-rom-unbrick-lg-k7-k330-t-t3432878
Hi im hoping someone can help me, in an attempt to root my swift 2 i flashed twrp ensuring to use the correct version from the website. after not being able to find the Supersu zip file properly i attempted to restart the phone to locate it on the memory card, it was at this point i got the first warning of 'your device software cant be checked for corruption, please lock the boot loader' after that i get the dm-verity error and then the first wileyfox powered by android screen pops up and freezes there indefinitely. occasionally the second orange wileyfox logo will load but then that will freeze too!
please help its a brand new phone and im nearly crying over this!!!
https://forum.xda-developers.com/swift-2/how-to/marmite-wileyfox-ota-nougat-android-7-1-t3654999
Have a look at the first post Section 3 on that post should help you
mostly the part related to
adb reboot "dm-verity enforcing"
Flash stock recovery and only boot TWRP don't flash it
Thanks for the reply. Almost straight after posting I found a download for nougat 7.1.1 and flashed that, then updated it to the latest via OTA. I still get the verity warning occasionally and the phone seems laggier than before plus it reboots itself occasionally but at least it still works! No root but I may have another go at a later date.