Hi
I have ascend g7 and I have rooted it by kingroot. but, I decided to unroot my phone. I have tried many ways but didn't worked.
- "uninstall kingRoot" -> failed
-SuperSu "Full Unroot" ->failed
- tried to flash custom recovery-> failed
please help me!
I would appreciate any ideas which could help me to solve my problem
p.s.: I'd like to flash CM13 custom ROM but no custom Recovery could be installed. dont know why!!!
This may be a silly question, but have you unlocked your bootloader?
If not, that is the first thing you need to do before you are able to install a custom recovery.
Secondly, the only way to unroot will be to reinstall an update.app of the current firmware you have, or a later version.
miz_pimp said:
This may be a silly question, but have you unlocked your bootloader?
If not, that is the first thing you need to do before you are able to install a custom recovery.
Secondly, the only way to unroot will be to reinstall an update.app of the current firmware you have, or a later version.
Click to expand...
Click to collapse
hi
firstly, thank you for reply. secondly, I tried to unlock bootloader but I'm gonna try it again. thirdly, what is "update.app"? after reinstalling update.app or newer version of ROM, what am I supposed to do to unroot my phone?
thanks agian
hmdkshvrz said:
hi
firstly, thank you for reply. secondly, I tried to unlock bootloader but I'm gonna try it again. thirdly, what is "update.app"? after reinstalling update.app or newer version of ROM, what am I supposed to do to unroot my phone?
thanks agian
Click to expand...
Click to collapse
An update.app is the full firmware file for Huawei devices.
After updating your device, it will be completely stock, so everything will be like it was out of the box. So you will no longer be rooted.
Please look at my post for unlocking bootlader works 100 percent for the g7 L01 not sure for any other variant try at own risk hope this works for you
Related
Hi
I am new to the OnePlus 2. When I bought it, stock 5.1.1 installed, I downloaded and installed the latest Marshmallow stock build via an OTA update. I then followed the official OnePlus video guide on unlocking the bootloader and rooting the device. I successfully unlocked the bootloader, flashed TWRP and then went on to flash SuperSU. Unfortunately, then device did not reboot - and I was soft-bricked, stuck on the boot animation. I am not sure what went wrong here.
In order to un-brick and recover my device, I downloaded the latest Marshmallow OxygenOS 3.0.2 zip from OnePlus. I was able to get this onto my device and I flashed it successfully in TWRP, and all is well.
My questions are:
1) Having flashed the latest stock, Marshmallow OxygenOS 3.0.2, will my bootloader still be unlocked?
2) Will I still have TWRP recovery, or stock recovery?
3) How can I successfully root?
Thank you in advance
I already forget what it is looks like when I change from stock to custom ROM.
But hey, here is the guide to help you:
1. use Fastboot command -> fastboot oem device-info
If "Device unlocked: ture" than your bootloader is unlocked. Normally, if you have not yet touch anything, oem is locked. But if you do unlock it, it will STAY unlock unless you use fastboot command line to change back to locked.
2. OP website only show is optional to use official recovery, so I think it is depend on you. Just go and check on it
3. For OnePlus Brand is easy. Just go and download SuperSU 2.74, place into your "sdcard", and flash it.
qingmui said:
I already forget what it is looks like when I change from stock to custom ROM.
But hey, here is the guide to help you:
1. use Fastboot command -> fastboot oem device-info
If "Device unlocked: ture" than your bootloader is unlocked. Normally, if you have not yet touch anything, oem is locked. But if you do unlock it, it will STAY unlock unless you use fastboot command line to change back to locked.
2. OP website only show is optional to use official recovery, so I think it is depend on you. Just go and check on it
3. For OnePlus Brand is easy. Just go and download SuperSU 2.74, place into your "sdcard", and flash it.
Click to expand...
Click to collapse
Hi - many thanks for the reply and information
Just to confirm, question 2: I flashed the latest stock from TWRP to recover from a soft brick. Would that process have flashed stock recovery also? Do I need to check this out by pressing Vol. down and Power buttons on boot?
Thanks again
pretty pixel said:
Hi - many thanks for the reply and information
Just to confirm, question 2: I flashed the latest stock from TWRP to recover from a soft brick. Would that process have flashed stock recovery also? Do I need to check this out by pressing Vol. down and Power buttons on boot?
Thanks again
Click to expand...
Click to collapse
TWRP will ask you, if you want to disable stock recovery flash, after you flash official firmware.
Rooting the newest stock firmware with the latest supersu from chainfire's website will turn your device into a bootloop.
Here you can find the right supersu for your firmware:
http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
Greetings LordHelmchen
LordHelmchen89 said:
TWRP will ask you, if you want to disable stock recovery flash, after you flash official firmware.
Rooting the newest stock firmware with the latest supersu from chainfire's website will turn your device into a bootloop.
Here you can find the right supersu for your firmware:
http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
Greetings LordHelmchen
Click to expand...
Click to collapse
Hello and thank you for sending me the information and links. Flashing the modified supersu worked and I am now rooted
Just a final question please...Before I received your reply I had flashed stock several times and tried different supersu versions. And ended up in bootloops as a result of this. Is this likely to have damaged my device in any way?
pretty pixel said:
Hello and thank you for sending me the information and links. Flashing the modified supersu worked and I am now rooted
Just a final question please...Before I received your reply I had flashed stock several times and tried different supersu versions. And ended up in bootloops as a result of this. Is this likely to have damaged my device in any way?
Click to expand...
Click to collapse
No, this will not damage your phone. I can not say too much about it, but the device shouldn't be damaged, it's a software-thing
PS: Hope my english is okay...and if I helped you, I would be very grateful if you click the Thanks-Button ...thank you
LordHelmchen89 said:
No, this will not damage your phone. I can not say too much about it, but the device shouldn't be damaged, it's a software-thing
PS: Hope my english is okay...and if I helped you, I would be very grateful if you click the Thanks-Button ...thank you
Click to expand...
Click to collapse
Thank you for the reassurance
Hello,
i'm a new user and i have a question for you guys. I have my P8Lite with:
- unlocket bootloader TWRP 3.0.2-0
- rooted
- firmware 5.0.1
(i used to write little scripts for school project that used my phone so i had to access root-locked functionalities)
my friends recently recived and update for their phone but i tried to do it (OTA and local) and didnt work.
Could please someone explain to me why i cant update my firmware? What's keeping me from doing so?
If i need to give up on root/custom recovery i can do that. I just want to know how to get the last stock firmware on my phone.
Thanks a lot.
SuperAntani said:
Hello,
i'm a new user and i have a question for you guys. I have my P8Lite with:
- unlocket bootloader TWRP 3.0.2-0
- rooted
- firmware 5.0.1
(i used to write little scripts for school project that used my phone so i had to access root-locked functionalities)
my friends recently recived and update for their phone but i tried to do it (OTA and local) and didnt work.
Could please someone explain to me why i cant update my firmware? What's keeping me from doing so?
If i need to give up on root/custom recovery i can do that. I just want to know how to get the last stock firmware on my phone.
Thanks a lot.
Click to expand...
Click to collapse
You need to give up twrp. Also make sure you download correct region/model firmware otherwise it may fail or give you many bugs. Especially balong bug. After updating your phone will automatically unroot and probably your data will be erased. So backup your data to avoid any loss.
Suleiman01 said:
You need to give up twrp. Also make sure you download correct region/model firmware otherwise it may fail or give you many bugs. Especially balong bug. After updating your phone will automatically unroot and probably your data will be erased. So backup your data to avoid any loss.
Click to expand...
Click to collapse
Ok, let's say i install the original recovery, i then should be able to update to the latest version.
At that point will i still be able to re-install twrp and re-root?
(I think bootloader should remain unlocked)
SuperAntani said:
Ok, let's say i install the original recovery, i then should be able to update to the latest version.
At that point will i still be able to re-install twrp and re-root?
(I think bootloader should remain unlocked)
Click to expand...
Click to collapse
After you successfully updated your phone to Android 6.0 you may root it again or install twrp.
Bootloader should remain unlocked. There is no need to lock it.
Suleiman01 said:
After you successfully updated your phone to Android 6.0 you may root it again or install twrp.
Bootloader should remain unlocked. There is no need to lock it.
Click to expand...
Click to collapse
That's marvelous. I'll do that as soon as i can and i'll post the outcome
It all worked properly, i installed stock recover > OTA update > re-installed custom recovery.
Now i have the lastest update with custom recovery.
I had some troubles with root tho, i made a backup then installed the latest version of SuperSU through TWRP but it soft bricked my phone so i had to restore the backup.
I gave up on root because i dont need it but it would be nice to know what went wrong there.
Anyway it all works fine and i kept my files and apps.
Thanks a lot buddy
Hi friends.
Not work Recovery,
Not work Fastboot.
There are tutorials for repair?
Thank you very much.
lnadeb said:
Hi friends.
Not work Recovery,
Not work Fastboot.
There are tutorials for repair?
Thank you very much.
Click to expand...
Click to collapse
What did you do to get there?
I wanted to execute a locked bootloader. After restarting only ERROR MODE.
I need help.
Hi there, I have bricked my Mate 9 and am having the same message. Did you get your Mate back to work? If so, please kindly share the method. Thank you very much!
Grimmlocks said:
Hi there, I have bricked my Mate 9 and am having the same message. Did you get your Mate back to work? If so, please kindly share the method. Thank you very much!
Click to expand...
Click to collapse
Same question... What did you do to get there?
---------- Post added at 10:59 ---------- Previous post was at 10:57 ----------
Maybe you made like here!
franzyroy said:
Same question... What did you do to get there?
Click to expand...
Click to collapse
I was on twrp and shield Rom, but wanted to test if flashing an official rom through Fastboot and restoring oeminfo could get official updates back. After flashing official recovery through twrp, I can't go back to fastboot o erecovery mode, only this screen.
I will have to take to technical support eventually, but was wondering if there is any solution to this...
Grimmlocks said:
I was on twrp and shield Rom, but wanted to test if flashing an official rom through Fastboot and restoring oeminfo could get official updates back. After flashing official recovery through twrp, I can't go back to fastboot o erecovery mode, only this screen.
I will have to take to technical support eventually, but was wondering if there is any solution to this...
Click to expand...
Click to collapse
What erecovery have you flashed?
Are you sure it's corresponding with your current EMUI?
Can you acceed to the bootloader mod? Apparently NO
Have you tried to re-install the TWRP from adb?
I don't understand why you installed the erecovery to install an official. It was unecessary. After, I didn't try to put a custom on this phone model. I'll take a look how to come back on official from a custom for this phone.
franzyroy said:
What erecovery have you flashed?
Are you sure it's corresponding with your current EMUI?
Can you acceed to the bootloader mod? Apparently NO
Have you tried to re-install the TWRP from adb?
I don't understand why you installed the erecovery to install an official. It was unecessary. After, I didn't try to put a custom on this phone model. I'll take a look how to come back on official from a custom for this phone.
Click to expand...
Click to collapse
I actually flashed the official recovery because with twrp it cannot be updated. I can neither enter bootloader, so cannot flash twrp back.
All the img files have been extracted from an official rom, so I am quite sure. Thank you very much for the help!
franzyroy said:
What erecovery have you flashed?
Are you sure it's corresponding with your current EMUI?
Can you acceed to the bootloader mod? Apparently NO
Have you tried to re-install the TWRP from adb?
I don't understand why you installed the erecovery to install an official. It was unecessary. After, I didn't try to put a custom on this phone model. I'll take a look how to come back on official from a custom for this phone.
Click to expand...
Click to collapse
Finally I had to take it to official technical support. And even they couln't fix it, because they just sent me a new one...I am gladly surprised by Huawei customer services.
Thank you for your interest in helping! It is much appreciated!! :good:
Glad for you!
Hi, I recently tried to downgrade back to stock firmware from Lineage OS using the Dload method.
However now its on a bootloop, the versions of CAN-01 and CAN-11 all give me a bootloop, after waiting on it a while it will boot into recovery mode.
Usually this is a simple problem to fix however it reset my bootloader to locked as well as my twrp recovery, I'm not sure how I can recover from this other than sending to repairs.
Any suggested solutions!
It could just be I have the wrong update.zip but I want some more views on this.
Noctyk said:
Hi, I recently tried to downgrade back to stock firmware from Lineage OS using the Dload method.
However now its on a bootloop, the versions of CAN-01 and CAN-11 all give me a bootloop, after waiting on it a while it will boot into recovery mode.
Usually this is a simple problem to fix however it reset my bootloader to locked as well as my twrp recovery, I'm not sure how I can recover from this other than sending to repairs.
Any suggested solutions!
It could just be I have the wrong update.zip but I want some more views on this.
Click to expand...
Click to collapse
Hello!
Check this post.
#Henkate said:
Hello!
Check this post.
Click to expand...
Click to collapse
Hi! Thank you for the fast reply, I remember that I've tried method 1 already and since it reset my bootloader, it's no longer unlocked. The first thing I did when I realised it was a bootloop I tried to reflash my TWRP as I have a backup but it fails everytime I try to flash anything through fastboot as my bootloader is locked.
I was slightly naive and didn't think it would wipe my TWRP and bootloader back to locked.
What do you recommend I try?
Well, Unlock your Bootloader again.. ^^
Bad2hold said:
Well, Unlock your Bootloader again.. ^^
Click to expand...
Click to collapse
I've fixed the issue now thanks, I forgot to wipe the cache and extra bits after the Dload update thats why it was stuck on the bootloop :silly:
My problem before was I couldnt get the IDs needed for my bootloader unlock code since I couldn't actually check the IDs through settings.
Hi there,
I have a problem in downgrading my moto g4 play. I have stuck with this problem when I was flashing Android 7.1.1 (HARPIA_NPI26.48-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) via RSD lite 6.2.4. RSD lite failed during flashing boot.img. After that I tried to downgrade to 6.0.1 with this stock rom (XT1607_HARPIA_AMAZON_USA_MPI24.241-2.35-1_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml).
I would like to mention that I have tried same steps with ADB + Fastboot and I was getting the same answer from the phone "version downgraded for boot. Failed to validate boot image"
As I know, the official stock ROMs work without any problem with a locked bootloader.
But I would like to ask is there any other methods for flashing android nougat or downgrade?
Thanks
genadik said:
Hi there,
I have a problem in downgrading my moto g4 play. I have stuck with this problem when I was flashing Android 7.1.1 (HARPIA_NPI26.48-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) via RSD lite 6.2.4. RSD lite failed during flashing boot.img. After that I tried to downgrade to 6.0.1 with this stock rom (XT1607_HARPIA_AMAZON_USA_MPI24.241-2.35-1_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml).
I would like to mention that I have tried same steps with ADB + Fastboot and I was getting the same answer from the phone "version downgraded for boot. Failed to validate boot image"
As I know, the official stock ROMs work without any problem with a locked bootloader.
But I would like to ask is there any other methods for flashing android nougat or downgrade?
Thanks
Click to expand...
Click to collapse
You can't manually downgrade/upgrade the Amazon variant of this device.
Can I use Blank Flash tools for restoring my device?
genadik said:
Can I use Blank Flash tools for restoring my device?
Click to expand...
Click to collapse
Bootloader locked Amazon varient? Not likely.
Sorry that my question will look a bit stupid...But if it's not hard for you, can you explain why??
Thanks
genadik said:
Sorry that my question will look a bit stupid...But if it's not hard for you, can you explain why??
Thanks
Click to expand...
Click to collapse
Commands needed to access essential partitions/files (eg: aboot) are blocked on most devices with a locked bootloader. You can certainly try - me thinks the possibility of yielding an unrecoverable brick outweighs any possible benefit.
Best case it simply fails.
So, in this case, the only solution s service center?
genadik said:
So, in this case, the only solution s service center?
Click to expand...
Click to collapse
Yep (the only reasonable solution IMHO).