Hey guys, hopefully someone can help!
Im trying to reflash the stock ROM to my P8 Lite device as I rooted with KingRoot and dont like it, and to be honest dont trust it.
I have downloaded what I believe to be the stock ROM from the NZ Huawei website, im in New Zealand. I have copied the DLOAD folder to a empty microSD and have tried a local update. Throught the update app, and by pushing and holding down the volume up and down keys with power button. Each time the install fails instantly at 0% and just says upload failed.
My understanding is that no root can damage the device, surely the device can be completely wiped and the new ROM installed? Im a little worried that maybe kingroot has actually %&$^% my device? But then im sure doing a stock install of the ROM will fix that.
So, can anyone help with this issue? I got my bootloader unlock code, but got into fastboot and it said my bootloader was already unlocked? So my bootloader is unlocked and im still getting this error.
Im trying to reinstall as I think ive damage DPKG quite badly and am not able to install busybox. Pretty much just want a stock install to start from scratch!
Any help please, much appreciated!
Thanks
Related
when JB came out I upgraded, wasn't happy when playing games screen to slow & lagged, so I renamed ICS retail from asus site & reflashed without issues, worked fine now, but im not sure but maybe bootloader is upgraded to the JB version now? not sure if that is how it works or not. but how i used to do root no longer works at all. when i used DebugfsRoot_Generic_v2.3 it now says it failed & system partition not found when trying to hack to root. I can view & transfer files to the TF700 fine. but I did reinstall ADB drivers again, didn't help, but found no su binary installed, when trying to update Superuser update failed, busybox wont install it fails, & SU app cant find the install path. seems all this is to do with not having the su binary files dir, or what ever is needed to get these apps to install & use the expolit. should I try to wipe the cashe & reflash tablet to ICS again? I really have no clue how to get root back, im really suck here & really need alot of help in steps to repair this so I have a stock ICS & then get root back, boot loader is locked I would like to keep the bootloader locked, but if i must unlock to fix this issue & regain ICS & root it then so be it. But need the steps to take so I dont brick this unit, so im asking please for help from someone that really knows what they are doing & can show me the steps to take. I would also like to know if the bootloader is unlocked is it possible to downgrade tablet to have navflash working? so I wont brick the system down the road? or is it to late as tablets bootloader cant be downgraded after updated to JB once already? I Thank you very much. for answering these questions & helping me to get root back.
Have you tried flashing the root.zip from this thread?
http://forum.xda-developers.com/showthread.php?t=1929712
Or this:
http://forum.xda-developers.com/showthread.php?t=1916762
Had the same problem -
Most likely the update erased the \system\bin\su and system\xbin\su files and didn't replace them.
This may solve it . . .
http://forum.xda-developers.com/showthread.php?t=1985699
waltnich said:
Most likely the update erased the \system\bin\su and system\xbin\su files and didn't replace them.
This may solve it . . .
http://forum.xda-developers.com/showthread.php?t=1985699
Click to expand...
Click to collapse
This instruction is for unlocked device only.
Had the same problem -
If all else fails, unlock.
I personally feel that once we know our device is not defective out of the box -
and have all the tools to get under the hood, and the resource community here at XDA (and otherwise) -
that the mfg warranty won't matter much anyway.
It's a mfg warranty not like it's an all out warranty you pay for.
I unlocked in a heartbeat (thanx 4the tool Asus) - but I am careful as hell when I am under the hood.
waltnich said:
If all else fails, unlock.
I personally feel that once we know our device is not defective out of the box -
and have all the tools to get under the hood, and the resource community here at XDA (and otherwise) -
that the mfg warranty won't matter much anyway.
It's a mfg warranty not like it's an all out warranty you pay for.
I unlocked in a heartbeat (thanx 4the tool Asus) - but I am careful as hell when I am under the hood.
Click to expand...
Click to collapse
Agreed, with the above, my unit is working great. how do i flash if it's not rooted or unlocked, right now? to get the su binary installed in unit again, if missing or removed. thx guys for all the help & I looked at all links & found the su binary zip but have no clue how to flash it or install it, without having root or a unlocked unit having clockworkmod installed
waltnich said:
Most likely the update erased the \system\bin\su and system\xbin\su files and didn't replace them.
This may solve it . . .
http://forum.xda-developers.com/showthread.php?t=1985699
Click to expand...
Click to collapse
Thank you - I unlocked bootloader & then tried this & worked its now rooted again.
- how can i tell what bootloader is installed, even if I updated to JB then downgraded to ICS again. would like to know what ROM's I can use with current bootloader, as now everything i do can brick my unit,
NeoGodSpeed said:
Thank you - I unlocked bootloader & then tried this & worked its now rooted again.
- how can i tell what bootloader is installed, even if I updated to JB then downgraded to ICS again. would like to know what ROM's I can use with current bootloader, as now everything i do can brick my unit,
Click to expand...
Click to collapse
If you plan to use any JB custom rom, It's recommended that you should upgrade to Asus full package latest version of JB, since all custom roms are not included everthing like the Asus rom (custom rom only included rom and kernel, not bootloader, firmware etc..). Then re install recovery twrp, then use twrp to flash custom rom.
I'm kind of new to the whole rooting thing. However, I managed to root the Unlock the bootloader, install the recovery and then root it. However when I tried to install a ROM the phone when off after I had wiped the old OS. So at the moment I am stuck in limbo, all the phone does is flash, any ideas? Thanks.
Waggy2014 said:
I'm kind of new to the whole rooting thing. However, I managed to root the Unlock the bootloader, install the recovery and then root it. However when I tried to install a ROM the phone when off after I had wiped the old OS. So at the moment I am stuck in limbo, all the phone does is flash, any ideas? Thanks.
Click to expand...
Click to collapse
You might want to post in the emergency thread for this.
Someone will chime in I am sure. From what little I know, I would try using the RUU (ROM update utility) to restore the phone.
Before you do that, wait a little while and maybe someone else will post with some other method. The RUU will hopefully restore your phone to stock.
I'm trying to do that now buy it just wont boot up so I can't run the program
Hello everyone i am new to the forums and i am asking a question regarding updating the su binaries on my phone. I got my g2 back in november because they were out of one m7s and this was the second best phone. So i went home and figured id root it. I didnt really want a rom i just like being able to record my screen and mess with the clocks. So none of the ways to root this phone worked so i tired this one in chinese. I succesfully rooted my phon. And it installed supersu. It said i needed to update the binaries so i hit ok. It said it failed. I tried updateing them by moving the .su directly to the folder, but sense i dont even have root permissions because i dint have a .su, it was unsuccessful. So what are my options? Im only 14 and kinda new at rooting, i have done it on two phones before, so please keep it simple. I dont care about keeping my data so i can i flash a stock rom? I. Tried it before but the method was for the 16 gig version which used a kdz file and sense i have a 32 gig version i needed a different file for some reason. In my phone settings it says im rooted and in recovery mode it o whatever pressing vol down and power with a usb connected do does, it says so to. I do NOT have access and i cant figure out how to update the .su and i could really use some help. Could you give me a link or something showing me how to flash a stock rom, or cyanogenmod? Or just getting a way to update the .su would be fine. Sorry for the long description i just want it to be easy for you to diagnose my problem.
Thanks,
Riley
XDA Visitor said:
Hello everyone i am new to the forums and i am asking a question regarding updating the su binaries on my phone. I got my g2 back in november because they were out of one m7s and this was the second best phone. So i went home and figured id root it. I didnt really want a rom i just like being able to record my screen and mess with the clocks. So none of the ways to root this phone worked so i tired this one in chinese. I succesfully rooted my phon. And it installed supersu. It said i needed to update the binaries so i hit ok. It said it failed. I tried updateing them by moving the .su directly to the folder, but sense i dont even have root permissions because i dint have a .su, it was unsuccessful. So what are my options? Im only 14 and kinda new at rooting, i have done it on two phones before, so please keep it simple. I dont care about keeping my data so i can i flash a stock rom? I. Tried it before but the method was for the 16 gig version which used a kdz file and sense i have a 32 gig version i needed a different file for some reason. In my phone settings it says im rooted and in recovery mode it o whatever pressing vol down and power with a usb connected do does, it says so to. I do NOT have access and i cant figure out how to update the .su and i could really use some help. Could you give me a link or something showing me how to flash a stock rom, or cyanogenmod? Or just getting a way to update the .su would be fine. Sorry for the long description i just want it to be easy for you to diagnose my problem.
Thanks,
Riley
Click to expand...
Click to collapse
You can check this thread about root on your device: [Root] Stump Root for LG Devices (2012 - 2014) Big update 1.2.0.
And here is the SuperSu app thread: [STABLE][2015.01.20] SuperSU v2.45.
In the first post there is also a zip file for flashing in custom recovery. If you use this, you won't need the binaries updating process like after updating via Play store.
For registered users, there is more help in the root Q&A thread for your device, and for the SuperSU app update in the SuperSU support thread.
Thread closed. Thank you.
I rooted my stylo last month and shortly after I flashed a twrp recovery in which I thought it was for my ls770. Well after I did that I got that error 1003 thing when I try to boot into recovery. So I now can't boot into recovery So I found a factory recovery file and flashed it also and I still can't boot into recovery. Can someone help please and thanks..
What version of Android? I did the same thing and luckily I had backed up a recovery with Flashify. I can see if I still have the backup. The recovery was for 5.1.1 ZV5
The one I found I think was for 5.0 but I'm on 5.1.1. That would be great @mabry
mabry said:
What version of Android? I did the same thing and luckily I had backed up a recovery with Flashify. I can see if I still have the backup. The recovery was for 5.1.1 ZV5
Click to expand...
Click to collapse
Do you have the stock recovery or what cause I need it asap
My bad bro. When I updated to Marshmallow I formatted my external SD in hope of the new storage feature. I lost it. I am sure 6th Hokage, or Dominick might have one laying around. They the main devs on the Boost Stylo.
did you ever get the stock recovery, I have the same problem...
ShonPu said:
did you ever get the stock recovery, I have the same problem...
Click to expand...
Click to collapse
No I have been trying like a mad man to get the recovery back but nothing is working. And I can't find anyone that can help me. It is driving me insane...
ShonPu said:
did you ever get the stock recovery, I have the same problem...
Click to expand...
Click to collapse
Add me to the list. I can't get anything but secure boot error 1003.
Me too..
Add me as well....
Rooted and went to install twrp..secure boot error 1003.
Anybody get any news on this?
The TWRP that is available out there right now with all the tutorials isnt for our devices (LS770). Theres not much going on with our devices because of the locked bootloader that lg seems to know nothing about; let alone any support for this devices alongside marshmallow. My goal is to port TWRP to our phones and find a backdoor in but im caught up in a bunch of different projects right now and juggling it with work. Plus ive gotta learn how to build these things. If anybody could tell me anything about our phone that i cant figure out thatd be wonderful. Ill try to get the recovery image posted on my drive when i go on my computer next.
Lg lls770
So I've read even just using King root it will lock up your phone, i had done that with my other lg ls770 and tried installing the twrp recovery. Any ideas if i will run into the same problem just using King root? And how would i go about making a back up of my stock recovery?
The ls770 has a locked bootloader. You can't just put any twrp recovery on it. You may be able to use kingroot temp, but I bricked twice using it, and can't offer any advice. If you have read enough of the ls770 brick stories including mine, you'll see there is no real pattern to bricking with kingroot. I successfully used it and restarted and re temp rooted for days, changing build.prop uninstalling google apps, then WHAM, brick out of thin air. Some were bricking straight away after kingroot with only restarting. If you do use kingroot to temp root I hope you'll report back and tell us how it is going, Thanks
So any idea if checking the oem unlock box in developer options and then going to fastboot/download mode would unlock the bootloader? I'm not very advanced with tinkering with android but i can go about the basics i guess
Finallyrooted said:
So any idea if checking the oem unlock box in developer options and then going to fastboot/download mode would unlock the bootloader? I'm not very advanced with tinkering with android but i can go about the basics i guess
Click to expand...
Click to collapse
The oem unlock will not unlock the bootloader.The bootloader is locked by Boost/sprint/virgin. It's probably not going to be unlocked. The only LG's I know that have unlocked bootloader are Tmobile/metropcs. I hope kingroot gets this worked out as we know they have no future without being able to root phones. I made a post on the kingroot page here at XDA asking about what they might do now with marshmallow. I haven't heard from the main @Kingxteam but I keep hearing they are working on it
I thought everything was fixable with flashtool as long as the bootloader is unlocked.. never been so wrong in my life.
Bought a used xperia z3 6166 t mobile version without knowing its support for custom roms (smh).. steps i did:
1)installed recovery.
2) rooted the device
3) unlocked the bootloader (successfully)
4) i thought i was ready to install custom roms like niaboc79's existenz which consequently I did, the phone did boot after that but was connecting in fastboot and flashboot so
5)using flashtool flash stock latest d6616 firmware and was back to step 1.
read somewhere that I could flash d6603 firmware because both phones have same specs so
6)flash d6603 firmware in order to get existenz working
7)flashtool gave some errors and failed
8)used fastboot to flash kernel
the device stops responding all of a sudden..
9) kept on charge for hours, still got nothing , no vibration, no lights , no hard rest via combination of buttons , nothing by pressing the yellow button inside the flap..
10) pc shows usb not recongnized after a couple of seconds of connecting ..
its been beyond frustrating going through the internet, scrolling through threads after thread but no avail.. people say at least the phone should be recognized by pc in any form other than usb not recongnized .. so I went to a local smartphone repair shop and gave it to him but he isnt too hopeful either.. I already have xperia z1c which i messed with so many times but it always responds to the flashtool.. but buying xperia z3 is literally the worst smartphone experience of my life!
is there any way to make this dead brick work again.. any unorthodox means to rewrite boot to make it jump start? any help is appreciated!
hash054 said:
I thought everything was fixable with flashtool as long as the bootloader is unlocked.. never been so wrong in my life.
Bought a used xperia z3 6166 t mobile version without knowing its support for custom roms (smh).. steps i did:
1)installed recovery.
2) rooted the device
3) unlocked the bootloader (successfully)
4) i thought i was ready to install custom roms like niaboc79's existenz which consequently I did, the phone did boot after that but was connecting in fastboot and flashboot so
5)using flashtool flash stock latest d6616 firmware and was back to step 1.
read somewhere that I could flash d6603 firmware because both phones have same specs so
6)flash d6603 firmware in order to get existenz working
7)flashtool gave some errors and failed
8)used fastboot to flash kernel
the device stops responding all of a sudden..
9) kept on charge for hours, still got nothing , no vibration, no lights , no hard rest via combination of buttons , nothing by pressing the yellow button inside the flap..
10) pc shows usb not recongnized after a couple of seconds of connecting ..
its been beyond frustrating going through the internet, scrolling through threads after thread but no avail.. people say at least the phone should be recognized by pc in any form other than usb not recongnized .. so I went to a local smartphone repair shop and gave it to him but he isnt too hopeful either.. I already have xperia z1c which i messed with so many times but it always responds to the flashtool.. but buying xperia z3 is literally the worst smartphone experience of my life!
is there any way to make this dead brick work again.. any unorthodox means to rewrite boot to make it jump start? any help is appreciated!
Click to expand...
Click to collapse
My sincerest apologize for your misfortune. I have not yet encountered this degree of issues. I am going to keep my bootloader locked I do believe. Just got this phone myself and I really wish I could help you. The TMO version of this phone is definitely the worst one I think given the lack of software support.
However I was wondering what method you followed to install recovery and if you attempted to install exposed.
arikdahn said:
My sincerest apologize for your misfortune. I have not yet encountered this degree of issues. I am going to keep my bootloader locked I do believe. Just got this phone myself and I really wish I could help you. The TMO version of this phone is definitely the worst one I think given the lack of software support.
However I was wondering what method you followed to install recovery and if you attempted to install exposed.
Click to expand...
Click to collapse
used the XZdualrecovery zip for locked bootloader.. it was fairly simple , did it twice without any problems! then used recovery to install superuser and update it binaries and the phone was rooted.. I didnt installed xposed because i want to upgrade from lollipop.. that I couldnt do! :crying:
May this thread be a warning to people who themselves arent developers but have a little knowledge about custom roms to do their homework before diving into things they cant get out of..
hash054 said:
used the XZdualrecovery zip for locked bootloader.. it was fairly simple , did it twice without any problems! then used recovery to install superuser and update it binaries and the phone was rooted.. I didnt installed xposed because i want to upgrade from lollipop.. that I couldnt do! :crying:
May this thread be a warning to people who themselves arent developers but have a little knowledge about custom roms to do their homework before diving into things they cant get out of..
Click to expand...
Click to collapse
I will second the f*** out of this, but I will also add that recovery TYPICALLY protects you from a ton of heartache. Not this time huh? Well, I cannot get Kingroot off my frickin' phone. I think it may have been commandeered by China. The uninstall always fails. So I may be in the same boat as you. Not sure if I can install recovery with it on there or not, but I do know it and SuperSU do not play nicely. I am debating which would be more risky, factory resetting a rooted phone to get rid of kingroot, or attempting to install recovery with this scary AF root manager. What a pain in the ass.
So this is the procedure you followed?
https://forum.xda-developers.com/showpost.php?p=60507399&postcount=171
arikdahn said:
I will second the f*** out of this, but I will also add that recovery TYPICALLY protects you from a ton of heartache. Not this time huh? Well, I cannot get Kingroot off my frickin' phone. I think it may have been commandeered by China. The uninstall always fails. So I may be in the same boat as you. Not sure if I can install recovery with it on there or not, but I do know it and SuperSU do not play nicely. I am debating which would be more risky, factory resetting a rooted phone to get rid of kingroot, or attempting to install recovery with this scary AF root manager. What a pain in the ass.
So this is the procedure you followed?
https://forum.xda-developers.com/showpost.php?p=60507399&postcount=171
Click to expand...
Click to collapse
No thats the rooting method.. I just simply flashed the recovery from http://nut.xperia-files.com/path/XZDualRecovery/XZDualRecovery_2.8.26 and just installed superuser and updated the binaries..
I did also have a problem with kingroot.. you can download the official ftf firmware for d6616 and just flash it in flashboot through flashtool.. its the only way to get rid of kingroot in my experience .. but I would give you caution to flash nothing else except official firmware through flashtool.. and do it only if you know how to handle it.. as far my experience is concerned, I did get rid of the kingroot this way not once but twice without problem .. its the stuff that followed bricked the phone.. also my bootloader was unlockable so it might have made a difference..maybe
hash054 said:
No thats the rooting method.. I just simply flashed the recovery from http://nut.xperia-files.com/path/XZDualRecovery/XZDualRecovery_2.8.26 and just installed superuser and updated the binaries..
I did also have a problem with kingroot.. you can download the official ftf firmware for d6616 and just flash it in flashboot through flashtool.. its the only way to get rid of kingroot in my experience .. but I would give you caution to flash nothing else except official firmware through flashtool.. and do it only if you know how to handle it.. as far my experience is concerned, I did get rid of the kingroot this way not once but twice without problem .. its the stuff that followed bricked the phone.. also my bootloader was unlockable so it might have made a difference..maybe
Click to expand...
Click to collapse
Well I guess I'll be doing that then. Thanks. So how do you flash that file without a recovery?
I do not know how to handle flash tool since I have only heard of it and never used it. It appears I'll be using it to get rid of kingroot. How does one learn how to handle it so's one doesn't go and mess anything up?
My bootloader is also unlockable but I don't wanna screw with all the things that unlocking it does to the phone so I'm leaving it alone. I like those features
Also did you ever try to remove bloat on the stock ROM? Everything I remove via titanium backup just reinstalls immediately after removal.
Sorry for all the questions instead of answers for you. You are one of the few still messing with this device and I appreciate all your help very much. All of the info on this forum is mostly applicable to when the phone came out. This means almost all of it only applies to android 4.4 or it doesn't apply to the T-Mobile variant b/c T-Mobile was less popular when this phone was a flagship and uses Wifi text/calling which requires special planning. That and the fact that the threads are several hundred pages long makes following along impossible and makes this site all but useless for these phones now.