Related
I have a TF300, recent OTA Jellybean, unlocked, TWRP installed... but for the life of me I can't figure out how to root or if it is possible.
Most google searches date back to pre-Jellybean. I have tried flashing the hydroponic and stock ROMs but I end up with "signature verification fails" after trying to install via TWRP.
I assume this means I need root access... but I can't install root access without root access?!?
Please help, I know I am probably missing something obvious.
Thanks.
hormiga0 said:
I have a TF300, recent OTA Jellybean, unlocked, TWRP installed... but for the life of me I can't figure out how to root or if it is possible.
Most google searches date back to pre-Jellybean. I have tried flashing the hydroponic and stock ROMs but I end up with "signature verification fails" after trying to install via TWRP.
I assume this means I need root access... but I can't install root access without root access?!?
Please help, I know I am probably missing something obvious.
Thanks.
Click to expand...
Click to collapse
First there are two hydro roms, one JB and one ICS. When you get signature verification error you are most likely flashing an ICS rom, recovery, etc on a JB bootloader.
Try this link http://forum.xda-developers.com/showthread.php?t=1697227. It includes most of what you need on XDA for TF300.
There are recovery flashable roots available also.
Good Luck!
hormiga0 said:
I have a TF300, recent OTA Jellybean, unlocked, TWRP installed... but for the life of me I can't figure out how to root or if it is possible.
Most google searches date back to pre-Jellybean. I have tried flashing the hydroponic and stock ROMs but I end up with "signature verification fails" after trying to install via TWRP.
I assume this means I need root access... but I can't install root access without root access?!?
Please help, I know I am probably missing something obvious..
Click to expand...
Click to collapse
You must use this part:
== Part 3 - Install recovery and rooting ==
Let's start with installing the recovery
1) Download these 2 files:
- Jellybean recovery with fastboot files: Fastboot files + JB recovery
- Root files => Root files
- You can also download the new CWM Touch recovery if you don't like TWRP: CWM Touch recovery thread or TWRP recovery and download this file : openrecovery-twrp-2.3.1.0-tf300t-JB.blob
2) Extract the recovery with fastboot files zip and open a command prompt in the same folder of the adb and fastboot files (Shift + Right mouse)
3) Reboot into the bootloader of your tablet, type: adb reboot bootloader
4) When your tablet has reached the bootloader navigate with volume down to the usb icon and press volume up to confirm.
5) To flash the recovery type:
- TWRP: fastboot -i 0x0b05 flash recovery twrp.blob
- CWM: fastboot -i 0x0b05 flash recovery CWM-Touch.blob
6) A blue bar will appear and the recovery will be installed, when the blue bar is filled press volume up + power button to reboot into the tablet.
Now we will root the tablet
7) Copy Superuser-3.2-RC3-arm-signed to the internal storage of your tablet. then reboot into the bootloader again.
8) This time you need to select the RCK icon with volume up to enter the recovery image.
9) In recovery flash Superuser-3.2-RC3-arm-signed and reboot into the system
10) Install Supersu from Google Play
11) Open up Supersu, it will ask you to update the binary, choose yes.
12) Now your tablet should be rooted
Click to expand...
Click to collapse
This part works well
So I bought a Chinese OnePlus One, and it came pre-installed with CM 11 version 11.0-XNPH33r.
Connected to wifi, and got the system update for 11.0-XNPH38r Incremental, so I click download and install.
It reboots phone, then it loads ColorOS recovery looking screen with Chinese written on it and a green loading bar, then The CM splash icons comes back and loads. (alien looking guy with an arrow circling around his head)
After all that, I go to check the version and I'm still stuck at 11.0-XNPH33r!
I tried manually doing it from ColorOS recovery with 11.0-XNPH38r Incremental zip file, it installs about 3/4 of the way and then fails.
My Kernel Version is : 3.4.0-cyanogenmod-g0ad30e5
My ColorOS Recovery Version is : 1.2 (Rooted)
I've been looking around the forums, and I see people manually updating using TWRP which I don't have.
Can someone please help me, and if you have a solution can you please give me a step by step direction since I'm new to flashing/rooting and this phone.
I have a guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
It contains instructions on how to unlock your bootloader and install TWRP recovery (sections 1 and 2). Before doing anything though you should check the status of your bootloader because it might already be unlocked. You'll need to follow the instructions at the top of the guide to install your phone drivers and also adb/fastboot via the Android SDK. Once you have done that you can boot your phone into fastboot mode (hold power + volume up), connect your phone to your PC via usb cable, open a command prompt from your fastboot folder (shift + right click anywhere within the foler, then select open command prompt here), and issue this command:
Code:
fastboot oem device-info
Please post the results here.
Thanks man, I'll try that out.
timmaaa said:
I have a guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
It contains instructions on how to unlock your bootloader and install TWRP recovery (sections 1 and 2). Before doing anything though you should check the status of your bootloader because it might already be unlocked. You'll need to follow the instructions at the top of the guide to install your phone drivers and also adb/fastboot via the Android SDK. Once you have done that you can boot your phone into fastboot mode (hold power + volume up), connect your phone to your PC via usb cable, open a command prompt from your fastboot folder (shift + right click anywhere within the foler, then select open command prompt here), and issue this command:
Code:
fastboot oem device-info
Please post the results here.
Click to expand...
Click to collapse
TY for you help. I manage to get a custom recovery (TWRP), but I still can't update past 33R, when I update I get "E:Error executing updater binary in zip '/cache/cm-bacon-3628510d76-to-ac1ccf7921-signed.zip
I also have this phone SuperSU fully rooted I think
TheOneinNeed said:
TY for you help. I manage to get a custom recovery (TWRP), but I still can't update past 33R, when I update I get "E:Error executing updater binary in zip '/cache/cm-bacon-3628510d76-to-ac1ccf7921-signed.zip
I also have this phone SuperSU fully rooted I think
Click to expand...
Click to collapse
Go to section 8 of my guide and flash the stock images. Make sure you remove the -w of the last command though or it'll wipe all your user data.
Transmitted via Bacon
timmaaa said:
Go to section 8 of my guide and flash the stock images. Make sure you remove the -w of the last command though or it'll wipe all your user data.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks man. I actually tried the flashing of 44s on the guide you sent me and it worked. Sorry for my last reply. You've been a great help and my phone is up to date.
Two last question if you don't mind. When the new update comes, can I install through Settings> About Phones> System Updates
or do I have to do something similar to the flashing I just did
after flashing my custom recovery is gone (TWRP) and the Cyanogen Mod Recovery took its place. Should I leave it like that or get TWRP and if TWRP is the answer, do I use the same method I did installing the custom recovery?
You should now have no problems receiving automatic updates through the settings menu. You can leave the stock recovery if you want to, or you can flash TWRP again. If you don't intend on flashing any custom ROMs or mods then the stock recovery should suit you just fine. Flashing a recovery is done via fastboot.
Code:
fastboot flash recovery twrp-2.8.4.1.img
(where the recovery filename is twrp-2.8.4.1.img)
timmaaa said:
You should now have no problems receiving automatic updates through the settings menu. You can leave the stock recovery if you want to, or you can flash TWRP again. If you don't intend on flashing any custom ROMs or mods then the stock recovery should suit you just fine. Flashing a recovery is done via fastboot.
Code:
fastboot flash recovery twrp-2.8.4.1.img
(where the recovery filename is twrp-2.8.4.1.img)
Click to expand...
Click to collapse
Thank you for your time and effort to help.
I appreciate it a lot. Thanks again!
i rooted my deviced. Used systemless root. in the hope OTA would work when a update arrived.
Now there is a update but.... it says the update fails. (in dutch).
I used supersu unroot, but it still says update failed.
I tried using the MDM tools as here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/91996
... but that is giving a bogus cannot connect to internet message (I think it just means that there is no server for the g4 phone, internet is fine and fast on phone and pc)
I want the update but Now i am stuck:
-I do not want to re-lock the phone
-I do want the update. (euret -> may to juli security update)
Questions:
-Are there any meaning full error messages.. anywhere?
-are there other ways to flash the OTA?
-I see flashing stock should work. But is my unrooted rom different from stock?
You don't need to relock your bootloader to take the OTA-Update. Maybe the SuperSU "unroot" option was not 100% successful and the boot.img is still modified in anyway. And maybe you had make some other changes to your /system partition, any changes result in an error.
First you have to download the stock-rom for your device -> http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=100
Then flash only boot.img, recovery.img and all system.img_sparsechunk.0-7 files via fastboot.
Edit: With only flashing boot, recovery and system no data should be lost.
Edit: and maybe logo.bin when you had removed the unlocked warning
After that your are able to take the OTA-Update and root it again with this guide -> http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
downloading XT1642_ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip now.
is only option anyway because after trying to flash supersu it won't boot anyway. (but still boots into fastboot mode.. no brick yet)
thx
have you used xposed? or custom kernel?
Bender1987 said:
You don't need to relock your bootloader to take the OTA-Update. Maybe the SuperSU "unroot" option was not 100% successful and the boot.img is still modified in anyway. And maybe you had make some other changes to your /system partition, any changes result in an error.
First you have to download the stock-rom for your device -> http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=100
Then flash only boot.img, recovery.img and all system.img_sparsechunk.0-7 files via fastboot.
Edit: With only flashing boot, recovery and system no data should be lost.
After that your are able to take the OTA-Update and root it again with this guide -> http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
Click to expand...
Click to collapse
Thank you for this information Bender. I was wondering the exact same thing. I am rooted on a Moto G4 and i was wondering if a OTA update, or reflashing stock would wipe my data + all installed apps.
If i do it your way it shouldn't be any concerns?
srgudhka said:
have you used xposed? or custom kernel?
Click to expand...
Click to collapse
no only supersu and modified hosts file with adaway (main reason for root is titanium backup)
flashed boot, recovery and system with
Code:
fastboot oem fb_mode_set
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
system boots now with all user data intact in may 2016 update.
However system update nows says it is up to date. .... maybe they retracted the update temporary? ... patience.... (reteu).
@leuk_he
I have a RETEU version here in germany and download the XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml.zip file, which had the same build no as my g4+.
If you try to flash files from the wrong rom, you get an error while flashing or lost temporary your WiFi and IMEI till you find and flash the right one.
So compare the build no on your phone and the stock rom file.
@Zajbot
As long as you don't wipe cache or data or use fastboot erase userdata, all your data should be there.
I have done the same yesterday and all data is still on my phone
---------- Post added at 13:16 ---------- Previous post was at 13:11 ----------
You don't need the OEM fb_mode_set.
Try it again in few hours or reboot, the update should pop-up again, don't worry.
Wifi and imei info are correct(NL) I checked the XT1642_ATHENE from the bootloader screen (did not know this number)
but... patience is a hard one.... :crying::crying: ... and if people say "don't worry... i worry..." bad habit.
Build number accorindg to phoneinfo is MPJ24.139-48 ... but i think that is what i just flashed. Not sure if that is what was in the phone before.
i added the oemset becuase it cried about wrong signature on boot.img it still did afterwards.
@leuk_he
Then you have maybe the wrong ROM. I flashed boot recovery and system and had no errors. But my build no. matches before the update.
You can download my OTA-update zip from my drive and sideload it manually with stock recovery.
If the update have a wrong build no. you only get an error.
https://drive.google.com/file/d/0B8Pa0dVQxQjHcm8xU2ZfcGk4VUE/view?usp=drivesdk
Bender1987 said:
@leuk_he
You can download my OTA-update zip from my drive and sideload it manually with stock recovery.
If the update have a wrong build no. you only get an error.
https://drive.google.com/file/d/0B8Pa0dVQxQjHcm8xU2ZfcGk4VUE/view?usp=drivesdk
Click to expand...
Click to collapse
How does the sideload works?
Thanks
@Marv42
1. Download the .zip file to SD card.
2. Reboot into Stock Recovery -> Hold "Volume DOWN" while starting your phone.
3. Hold "Power + Volume UP" few seconds, then you get to recovery menu.
4. Choose "Apply update from SD card".
5. Choose .zip file.
6. Wait and watch the log, take +20min, then there is an "error" or "success" msg.
7. "Reboot system now"
Bender1987 said:
@Marv42
1. Download the .zip file to SD card.
2. Reboot into Stock Recovery -> Hold "Volume DOWN" while starting your phone.
3. Hold "Power + Volume UP" few seconds, then you get to recovery menu.
4. Choose "Apply update from SD card".
5. Choose .zip file.
6. Wait and watch the log, take +20min, then there is an "error" or "success" msg.
7. "Reboot system now"
Click to expand...
Click to collapse
Didn't work for me. I get the bootloadermenu and when I switched to RECOVERY I got the ANDROID-Picture with "No Command".
Flashing a new recovery.img don't change anything.
Is a sideload flah with adb possible?
@Marv42
When the dead Android shows up -> Power + Volume UP
Try it few times, then the recovery menu shows up.
Bender1987 said:
@Marv42
When the dead Android shows up -> Power + Volume UP
Try it few times, then the recovery menu shows up.
Click to expand...
Click to collapse
I think there is a problem with my recovery. I flashed the recovery from rom-zip
Edit: get the recovery
Edit 2.: Give up, get with my and yours OTA.zip a sideload mistake (number 7). Now I wait for the next OTA, next days will be hard without ROOT
@Marv42
You can easily root with the method mentioned in post #2, just boot into TWRP and make sure you follow ALL steps in the guide.
Bender1987 said:
@Marv42
You can easily root with the method mentioned in post #2, just boot into TWRP and make sure you follow ALL steps in the guide.
Click to expand...
Click to collapse
thanks for your hint, I start it tomorrow, have a good night
For the root, in the future, don't FLASH the TWRP, just BOOT into it, so you can apply SU for systemless root. Don't skip the step of creating the extra file.
This way you are still having the standard recovery.
SoNic67 said:
For the root, in the future, don't FLASH the TWRP, just BOOT into it, so you can apply SU for systemless root. Don't skip the step of creating the extra file.
This way you are still having the standard recovery.
Click to expand...
Click to collapse
I haven't flash the TWRP, I always boot by mfastboot to TWRP
Bender1987 said:
@leuk_he
You can download my OTA-update zip from my drive and sideload it manually with stock recovery.
If the update have a wrong build no. you only get an error.
https://drive.google.com/file/d/0B8Pa0dVQxQjHcm8xU2ZfcGk4VUE/view?usp=drivesdk
Click to expand...
Click to collapse
Tried sideloading with twrp , but it gave error 7 on build number. "this device has . "
thx anyway for sharing.
I will now try load older system images with older build number.
/edit:
Flashed MJP-..23 like bender and it now says a update is availble.
interesting side note. when using the build-48 it already showed battery indicator on motowake screen but still at may-2016 security update.
Hi,
My Honor 6 (Indian Version) was stuck in boot loop post OTA upgrade from B822 to B831. In order to fix this issue, I went through many forums available online and then decided to use the Multi Tool to downgrade to Android L & EMUI 3.1.
To get this done I have followed the below steps:
1. Unlock bootloader
2. Extract BOOT, CUST, RECOVERY and SYSTEM files from the update package downloaded from Honor.in site. //(Honor 6_Firmware_H60-L04_Android 5.1.1_EMUI 3.1_C675B570_India_Flipkart)//
3. Used Multi Tool to unbrick.
Post this the phone is not able to get into recovery mode; it's stuck at the logo screen. It doesnot recognise the 3 button command to boot into recovery mode.
I have tried using the 'boot to recovery' command in Multi Tool but it throws error "daemon not running starting on port 5037".
I have also tried adb command but for some reason my computer does not recognise my mobile.
i.e. adb devices --> doesnot show my device. (yes, I have updated the abb drivers). So I am not able to use any adb commands.
Then i tried installing/flashing CWM & TWRP recovery. None helped. :crying:
Now I am here, out of options and do not know how to proceed.
Could someone in this forum help me fix the current issue? Please.
In addition, I would like to know a few things:
a. How to install a new OS/ROM on a dead phone? (Healthy hardware with corrupt software)
b. How to format any phone and start a fresh installation?
c. How to read internal memory of a phone which has no ROM or corrupt software?
I am new to all this. Please bear with me.
Thanks,
Sampath
sampathnayak09 said:
Hi,
My Honor 6 (Indian Version) was stuck in boot loop post OTA upgrade from B822 to B831. In order to fix this issue, I went through many forums available online and then decided to use the Multi Tool to downgrade to Android L & EMUI 3.1.
To get this done I have followed the below steps:
1. Unlock bootloader
2. Extract BOOT, CUST, RECOVERY and SYSTEM files from the update package downloaded from Honor.in site. //(Honor 6_Firmware_H60-L04_Android 5.1.1_EMUI 3.1_C675B570_India_Flipkart)//
3. Used Multi Tool to unbrick.
Post this the phone is not able to get into recovery mode; it's stuck at the logo screen. It doesnot recognise the 3 button command to boot into recovery mode.
I have tried using the 'boot to recovery' command in Multi Tool but it throws error "daemon not running starting on port 5037".
I have also tried adb command but for some reason my computer does not recognise my mobile.
i.e. adb devices --> doesnot show my device. (yes, I have updated the abb drivers). So I am not able to use any adb commands.
Then i tried installing/flashing CWM & TWRP recovery. None helped. :crying:
Now I am here, out of options and do not know how to proceed.
Could someone in this forum help me fix the current issue? Please.
In addition, I would like to know a few things:
a. How to install a new OS/ROM on a dead phone? (Healthy hardware with corrupt software)
b. How to format any phone and start a fresh installation?
c. How to read internal memory of a phone which has no ROM or corrupt software?
I am new to all this. Please bear with me.
Thanks,
Sampath
Click to expand...
Click to collapse
First of all hold and press power + vol down to boot into bootloader mode and type
Fastboot devices
After connecting your phone to PC and opening a command window in platform-tools. Your device should be listed.
adb devices works only when your phone is already booted into Android or running twrp.
Copy and paste the four image files to platform-tools folder and fire these commands
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img
Fastboot flash cust cust.img
And then use the 3 button command.
(Platform-tools folder can be downloaded after installing latest Android SDK software)
How to return back to Stock Recovery & Install Stock Rom.
muradulislam said:
First of all hold and press power + vol down to boot into bootloader mode and type
Fastboot devices
After connecting your phone to PC and opening a command window in platform-tools. Your device should be listed.
adb devices works only when your phone is already booted into Android or running twrp.
Copy and paste the four image files to platform-tools folder and fire these commands
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img
Fastboot flash cust cust.img
And then use the 3 button command.
(Platform-tools folder can be downloaded after installing latest Android SDK software)
Click to expand...
Click to collapse
I am in a bit different situation, let me explain.
Till day before yesterday I was on B570 Rom, then I upgraded over OTA to B831, then Unlocked Bootloader, Rooted, Installed Latest TWRP Recovery & Installed Latest Xposed Framework, everything went successfull & My phone is running fine.
But the question that arises to me is that none of the Stock Marshmallow update for Honor 6 - H60-L04 has been stable as compared to Lollipop Version & I found B570 super stable & the possibility of myself reverting back to B570 is more. What would be the procedure to revert back to B570.. I think first of all I would have to revert back to stock recovery & then flash the rom package, but how to do this successfully.
Kindly advice.
muradulislam said:
First of all hold and press power + vol down to boot into bootloader mode and type
Fastboot devices
After connecting your phone to PC and opening a command window in platform-tools. Your device should be listed.
adb devices works only when your phone is already booted into Android or running twrp.
Copy and paste the four image files to platform-tools folder and fire these commands
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img
Fastboot flash cust cust.img
And then use the 3 button command.
(Platform-tools folder can be downloaded after installing latest Android SDK software)
Click to expand...
Click to collapse
Thank you for your response. :good:
I have flashed all the files using the fastboot mode, but my phone does not recognise the 3 button command.
It either displays the Honor logo or restarts with a quick vibration. the only command it recognised is 'Vol Down + USB plugged into a computer' (for fastboot).
When flashed with Honor Custom or CWM recovery the phone does not recognise:
1. Vol up + Vol down + Power - for recovery mode
2. Vol down + Power - for hard reset/clear cache partition
When flashed with TWRP recovery the phone only recognises: Power + Vol Up button which boots into recovery mode; however this works only when connected to a power source, the moment I disconnect the power cable the phone switches off.
I tried to install Honor 6 custom ROM EMUI4.0 using TWRP. Need guidance on the below two scenarios.
1. TWRP only recognises .zip files. HONOR custom ROMs are in .app format. What should I do?
2. As a work around, I have downloaded 'Honor 6_Firmware_H60-L04_Andriod 6.0_EMUI 4.0_C432B820_Channel-Others.zip' from xda forum and tried installing it, but TWRP throws a 'no md5 file found' error.
To address this I tried using WinMD5.exe to get the MD5 code and manually created a .MD5 file, but TWRP did not recognise it. Please guide.
Thanks,
Sampath
sampathnayak09 said:
Thank you for your response. :good:
I have flashed all the files using the fastboot mode, but my phone does not recognise the 3 button command.
It either displays the Honor logo or restarts with a quick vibration. the only command it recognised is 'Vol Down + USB plugged into a computer' (for fastboot).
When flashed with Honor Custom or CWM recovery the phone does not recognise:
1. Vol up + Vol down + Power - for recovery mode
2. Vol down + Power - for hard reset/clear cache partition
When flashed with TWRP recovery the phone only recognises: Power + Vol Up button which boots into recovery mode; however this works only when connected to a power source, the moment I disconnect the power cable the phone switches off.
I tried to install Honor 6 custom ROM EMUI4.0 using TWRP. Need guidance on the below two scenarios.
1. TWRP only recognises .zip files. HONOR custom ROMs are in .app format. What should I do?
2. As a work around, I have downloaded 'Honor 6_Firmware_H60-L04_Andriod 6.0_EMUI 4.0_C432B820_Channel-Others.zip' from xda forum and tried installing it, but TWRP throws a 'no md5 file found' error.
To address this I tried using WinMD5.exe to get the MD5 code and manually created a .MD5 file, but TWRP did not recognise it. Please guide.
Thanks,
Sampath
Click to expand...
Click to collapse
@DigiGoon
@sampathnayak09
You need to flash stock recovery first, by executing this command:
Code:
fastboot flash recovery recovery.img
@sampathnayak09
Make sure your power button is working correctly. If the files can be flashed successfully, you should be able to boot into recovery.
Honor firmware can only be flashed using three button method. You can search online for making .zip from .app but I am not sure that will solve your problem.
---------- Post added at 04:10 AM ---------- Previous post was at 04:06 AM ----------
mahadikrs said:
I am in a bit different situation, let me explain.
Till day before yesterday I was on B570 Rom, then I upgraded over OTA to B831, then Unlocked Bootloader, Rooted, Installed Latest TWRP Recovery & Installed Latest Xposed Framework, everything went successfull & My phone is running fine.
But the question that arises to me is that none of the Stock Marshmallow update for Honor 6 - H60-L04 has been stable as compared to Lollipop Version & I found B570 super stable & the possibility of myself reverting back to B570 is more. What would be the procedure to revert back to B570.. I think first of all I would have to revert back to stock recovery & then flash the rom package, but how to do this successfully.
Kindly advice.
Click to expand...
Click to collapse
There are rollback packages for going back. I have read those threads on XDA but could not find them again. Will look for them and will send you a link as soon as I found one.
muradulislam said:
@sampathnayak09
Make sure your power button is working correctly. If the files can be flashed successfully, you should be able to boot into recovery.
Honor firmware can only be flashed using three button method. You can search online for making .zip from .app but I am not sure that will solve your problem.
---------- Post added at 04:10 AM ---------- Previous post was at 04:06 AM ----------
There are rollback packages for going back. I have read those threads on XDA but could not find them again. Will look for them and will send you a link as soon as I found one.
Click to expand...
Click to collapse
Thanks for the reply.
If I extract the recovery.img from the B831 Rom Package & flash the same using the below command will it give me back my stock recovery.
fastboot flash recovery recovery.img
And if once I am on Stock Recovery I hope I can again Install a full fresh copy of the B831 Package which will be with Stock Recovery i.e NO TWRP Recovery & root free. And after that when I get the rollback package I can revert back to B570. Pls advice am I going right or is there any possibility that I will brick my phone.
sampathnayak09 said:
Thank you for your response. :good:
I have flashed all the files using the fastboot mode, but my phone does not recognise the 3 button command.
It either displays the Honor logo or restarts with a quick vibration. the only command it recognised is 'Vol Down + USB plugged into a computer' (for fastboot).
When flashed with Honor Custom or CWM recovery the phone does not recognise:
1. Vol up + Vol down + Power - for recovery mode
2. Vol down + Power - for hard reset/clear cache partition
When flashed with TWRP recovery the phone only recognises: Power + Vol Up button which boots into recovery mode; however this works only when connected to a power source, the moment I disconnect the power cable the phone switches off.
I tried to install Honor 6 custom ROM EMUI4.0 using TWRP. Need guidance on the below two scenarios.
1. TWRP only recognises .zip files. HONOR custom ROMs are in .app format. What should I do?
2. As a work around, I have downloaded 'Honor 6_Firmware_H60-L04_Andriod 6.0_EMUI 4.0_C432B820_Channel-Others.zip' from xda forum and tried installing it, but TWRP throws a 'no md5 file found' error.
To address this I tried using WinMD5.exe to get the MD5 code and manually created a .MD5 file, but TWRP did not recognise it. Please guide.
Thanks,
Sampath
Click to expand...
Click to collapse
If the phone keeps going off you tried charging for a while? Battery might not be charging due to no OS.
Sent from my H60-L04 using XDA Labs
mahadikrs said:
Thanks for the reply.
If I extract the recovery.img from the B831 Rom Package & flash the same using the below command will it give me back my stock recovery.
fastboot flash recovery recovery.img
And if once I am on Stock Recovery I hope I can again Install a full fresh copy of the B831 Package which will be with Stock Recovery i.e NO TWRP Recovery & root free. And after that when I get the rollback package I can revert back to B570. Pls advice am I going right or is there any possibility that I will brick my phone.
Click to expand...
Click to collapse
Try out this thread...
http://forum.xda-developers.com/hon...wngrade-eu-h60-l04-indian-b810-t3367031/page1
My honor 6 bricked about a month ago so can not verify this method but to get out of bootloop, always keep a nandroid backup of your device somewhere safe.
You can make a nandroid backup using twrp. Save it to SD card and then copy it to your PC to keep it safe.
muradulislam said:
Try out this thread...
http://forum.xda-developers.com/hon...wngrade-eu-h60-l04-indian-b810-t3367031/page1
My honor 6 bricked about a month ago so can not verify this method but to get out of bootloop, always keep a nandroid backup of your device somewhere safe.
You can make a nandroid backup using twrp. Save it to SD card and then copy it to your PC to keep it safe.
Click to expand...
Click to collapse
Thanks for your response.
I was able to do as per the steps I mentioned in my earlier post & now I have successfully Downgraded to B570, With Unlocked Bootloader, Rooted, TWRP & Xposed Installed. So its time for me to change my signature.
P.s : Also Updated TWRP to the Latest Version i.e TWRP 3.0.2-0
DigiGoon said:
@sampathnayak09
You need to flash stock recovery first, by executing this command:
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Hi,
I did flash the stock recovery, but my phone keeps rebooting and doesn't get into recovery mode.
I am sure it has sufficient battery charge. (Close to 90%).
Is there a way to do a clean install on Android phones? Like the way we install Windows OS on computers. Format hard disks, create partitions and then install a fresh OS?
Thanks
mahadikrs said:
Thanks for your response.
I was able to do as per the steps I mentioned in my earlier post & now I have successfully Downgraded to B570, With Unlocked Bootloader, Rooted, TWRP & Xposed Installed. So its time for me to change my signature.
P.s : Also Updated TWRP to the Latest Version i.e TWRP 3.0.2-0
Click to expand...
Click to collapse
Hi,
Could you please provide links to
1. The downgrade transition package.
2. Latest TWRP version.
Also plz help me understand the benifits of TWRP when it cannot be used to install the stock ROM?
sampathnayak09 said:
Hi,
Could you please provide links to
1. The downgrade transition package.
2. Latest TWRP version.
Also plz help me understand the benifits of TWRP when it cannot be used to install the stock ROM?
Click to expand...
Click to collapse
Find attached below the required links for Rollback package & TWRP.
1) https://club.hihonor.com/in/honor6.217/downgrade-link-from-marshmallow-b831-to-lollipop-b570.7935
2) https://twrp.me/devices/huaweihonor6.html
Regarding TWRP, it lets you install custom roms & other apps which cannot be installed thru stock recovery e.g Xposed Framework. Further TWRP is useful for restoring the phone as it allows to restore the phone by using Nandroid backups taken earlier, provided the Nandroid backups are stored in SD Card. There may be more advantages which I am still trying to find out.
mahadikrs said:
Find attached below the required links for Rollback package & TWRP.
1) https://club.hihonor.com/in/honor6.217/downgrade-link-from-marshmallow-b831-to-lollipop-b570.7935
2) https://twrp.me/devices/huaweihonor6.html
Regarding TWRP, it lets you install custom roms & other apps which cannot be installed thru stock recovery e.g Xposed Framework. Further TWRP is useful for restoring the phone as it allows to restore the phone by using Nandroid backups taken earlier, provided the Nandroid backups are stored in SD Card. There may be more advantages which I am still trying to find out.
Click to expand...
Click to collapse
Thank you for providing the links. Let me try installing these.
muradulislam said:
First of all hold and press power + vol down to boot into bootloader mode and type
Fastboot devices
After connecting your phone to PC and opening a command window in platform-tools. Your device should be listed.
adb devices works only when your phone is already booted into Android or running twrp.
Copy and paste the four image files to platform-tools folder and fire these commands
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img
Fastboot flash cust cust.img
And then use the 3 button command.
(Platform-tools folder can be downloaded after installing latest Android SDK software)
Click to expand...
Click to collapse
goldfinv said:
If the phone keeps going off you tried charging for a while? Battery might not be charging due to no OS.
Sent from my H60-L04 using XDA Labs
Click to expand...
Click to collapse
Phone has 75% + charge as shown in TWRP recovery.
sampathnayak09 said:
Phone has 75% + charge as shown in TWRP recovery.
Click to expand...
Click to collapse
Maybe try flashing one of the custom EMUI ROMs via TWRP?
Sent from my H60-L04 using XDA Labs
@mahadikrs @muradulislam @goldfinv
Thank you for your input guys. I am now able to enter stock recovery mode (3 button mode); however, the installation stops at 5%.
Any suggestions?
sampathnayak09 said:
@[email protected]@goldfinv
Thank you for your input guys. I am now able to enter stock recovery mode (3 button mode); however, the installation stops at 5%.
Any suggestions?
Click to expand...
Click to collapse
Give it a couple of tries. Users have suggested that it usually gets stuck somewhere but trying for 2,3 times gets the job done.
Sent from my PLK-L01 using XDA Labs
sampathnayak09 said:
@mahadikrs @muradulislam @goldfinv
Thank you for your input guys. I am now able to enter stock recovery mode (3 button mode); however, the installation stops at 5%.
Any suggestions?
Click to expand...
Click to collapse
Let me know which Rom version is your phone running now & which version you are trying to migrate to.
Also if 3 button Force update is not working then you can try the project menu option.
But first let me know what state your phone is currently in.
As there seems to be no such guide yet and it took me quite a while to get all this information together, I thought of giving back something by putting information together for others to start.
This guide is meant for the CLT-L29 (dual SIM). Rebranding and switching your CLT-L09 (single SIM) to dual is not subject of this guide and is not adviced.
This is for a Huawei P20 Pro CLT-L29 with factory reset. Please bear with me if there really is a step missing as I try to reproduce this for the documentation with an already bootloader unlocked and previously rooted phone (root should be gone after [factory] resetting via eRecovery).
A collection of all tools used can be found here.
As always, you are doing this on your own risk, no one else can be held responsible for this.
Cheat sheet
eRecovery
The recovery sitting in the "recovery" partition. eRecovery is Huawei's recovery that is able to fix your phone by downloading the latest OTA update via WiFi if you got stuck in a boot loop for several reasons.
To boot into eRecovery:
Power down your phone (if you are stuck in a boot loop simply continue with the next step).
Hold volume up until you end up in eRecovery.
Setup your WiFi access and let it recover your phone.
If unsure, "wipe data/factory reset" to get rid of any leftovers you messed up.
Reboot and be happy that you have not fully bricked your phone.
TWRP
The recovery typically flashed to the "recovery_ramdisk" partition. TeamWin Recovery Project is what you typically use to flash ROMs, to root the phone and to install OTA updates.
Do NOT flash TWRP into "recovery" partition or you will lose eRecovery and the ability to easily recover your semi-bricked phone via WiFi!
To boot into TWRP (once flashed):
Power down your phone (if you are stuck in a boot loop simply continue with the next step).
Hold volume up and power until you end up in TWRP.
Unlock your bootloader
Get your bootloader unlock code from here https://emui.huawei.com/en/unlock_detail (available until mid of July I think). Some report to have to wait 24/48h to get their code via mail, I got mine directly.
Register via mail and do not get confused that you can not select USA or Germany or whatever country, simply use location Hong Kong.
Make sure you select "EMUI above 5.0" when entering your phone data (P20 Pro comes with EMUI 8.x).
Connect your phone via ADB. There are tons of HowTos about this, so I will not be covering this here.
Use Tool All In One to check that you can talk to your device via ADB. It will also help you installing the correct ADB USB drivers.
Unlock your bootloader using Tool All In One.
Reboot back into system.
Flash TWRP
Make sure no lock screen or other locking is set:
"Settings > Security": Remove fingerprint, face or password locking, simply set to none.
Enter developer mode, should already been done for unlocking the bootloader.
Setting > System > Developer options: Disable the display lock.
Download latest ADB & Fastboot as I will continue with the rest on command line.
Verify connection to your phone with "adb devices", this should list your phone.
Reboot into fastboot by using "adb reboot bootloader".
Verify connection to your phone with "fastboot devices", this should list your phone.
Flash TWRP by Pretoriano80 with "fastboot flash recovery_ramdisk twrp_clt_0.1.img". This TWRP is able to access the encrypted internal storage! TWRP is flashed to "recovery_ramdisk". This ensures that you can still access eRecovery if something goes wrong.
Remove the USB cable.
Reboot into TWRP. If you do not boot directly into TWRP the Huawei eRecovery might replace TWRP again. Once you booted into TWRP you are fine for future reboots.
Use "Keep Read Only" for the system partition.
Make a backup!!!
Backup your phone to internal storage (USB stick via USB-OTG adapter failed for me):
Select "Backup".
Tick all partitions (scroll down and tick all).
Swipe to Backup.
Select "Reboot System", "Do Not Install".
Back in Android make a copy of your backup located in your internal storage "/TWRP/" to an external location like your PC. Keep the backup on your phone to be able to go back quickly to this point via TWRP.
Root the stock ROM
Place "Magisk-v16.4-Beta.zip" onto the internal storage.
Power off the phone and remove the USB cable.
Boot into TWRP.
Install root and Magisk Manager:
Select "Install".
Select "Magisk-v16.4-Beta.zip"
Tick "Reboot after installation is complete".
Swipe to confirm Flash.
Select "Do Not Install".
Back in Android start "Magisk Manager" and check that it is green and therefore rooted.
Install an OTA (Over The Air) stock update
PC method
Method involving ADB based on this guide.
First make sure no OTA update gets installed automatically as this will end up in booting into TWRP and failing with the update.
Go to "Settings > System > System Update".
Open the three dots menu on the top right and select "Update Settings".
Disable automatic update download via WiFi as once updates are downloaded the phone will bug you to update and maybe tries to update itself during the night!
Start in Android but do not download the OTA update yet.
Verify connection to your phone with "adb devices", this should list your phone.
Reboot into fastboot by using "adb reboot bootloader".
Verify connection to your phone with "fastboot devices", this should list your phone.
Flash "recovery_ramdisk_nocheckP20.img" with "fastboot flash recovery_ramdisk recovery_ramdisk_nocheckP20.img". For official OTA updates that you would regularly get, the "nocheck" feature should not be needed but does not harm. This will remove TWRP and you have to flash it again after the OTA update has finished.
Reboot into Android by using "fastboot reboot".
Remove the USB cable.
Download your OTA update via "Settings > System > System Update".
Let the phone reboot to install the OTA update and follow the update until you are back in Android with your new firmware version.
Install TWRP and root again.
Standalone method
Deprecated/wrong method based on this guide.
Read first!!!
While this method should do no harm it will only ever update to CLT-L29 8.1.0.128a(C432) [hw/eu] as this is what is inside the file "update.zip" that you can currently download and that gets installed by "HuRUpdater_0.3.zip" in the same folder. This was not clearly explained in the source thread, therefore sorry about this wrong information. If you intend to update to this stock ROM continue, otherwise use the "PC method".
I will check about the best way to install OTA updates without PC interaction in the next couple of days (currently waiting for 130+ getting rolled out for me for some investigations regarding the OTA process).
First make sure no OTA update gets installed automatically as this will end up in booting into TWRP and failing with the update.
Go to "Settings > System > System Update".
Open the three dots menu on the top right and select "Update Settings".
Disable automatic update download via WiFi as once updates are downloaded the phone will bug you to update and maybe tries to update itself during the night!
Place the following files into a folder on the internal storage (for sure not all are required but this is part of the little information not clear right now):
"HuRUpdater_0.3.zip"
"recovery.img"
"update.zip"
"update_all_hw.zip"
"update_data_public.zip"
Go to "Settings > System > System Update" and check for an update.
Download the OTA update.
Do not reboot when prompted.
Make sure no lock screen or other locking is set:
"Settings > Security": Remove fingerprint, face or password locking, simply set to none.
Enter developer mode, should already been done for unlocking the bootloader.
Setting > System > Developer options: Disable the display lock.
Power down the phone.
Boot into TWRP.
Install "HuRUpdater_0.3.zip". Do not get irritated if it tells you it is for CLT-L09 instead of CLT-L29, everything is fine.
Wipe dalvik cache before rebooting.
Reboot back into Android.
Check "Magisk Manager" to see if root got removed. TWRP might get removed as well. If TWRP or root got removed, repeat the install for one or both like before.
In my case only root got removed but TWRP was kept functional. If this is the case for you as well, simply flash "Magisk-v16.4-Beta.zip" via TWRP again.
Changelog
2018-06-21
Updated/corrected wrong information collected about installing OTA updates standalone (without PC). Until further notice use the PC method.
Great post. Thank you
Very good post!
Thank you to collect all this important info!
[emoji481]
P20 Pro & Tapatalk
can i use your step above to rebranding from L29c636 to l29c432? Thanks
Barcovn said:
can i use your step above to rebranding from L29c636 to l29c432? Thanks
Click to expand...
Click to collapse
Not sure, not tested and not topic of this thread.
For my understanding, why do you want to rebrand it to C432 which is the region code as far as I understand.
Is there a BIG benefit of getting OTA updates earlier or why do you want to mess around with it ?
Xcelsior said:
Not sure, not tested and not topic of this thread.
For my understanding, why do you want to rebrand it to C432 which is the region code as far as I understand.
Is there a BIG benefit of getting OTA updates earlier or why do you want to mess around with it ?
Click to expand...
Click to collapse
yes, i mean change the region code. as i use the p20 pro since April, newer firmware ususal fix/improve performance for phone or camera. however it seem the c636 update is much slower then C432. currently i have problem with facebook lagging which inhope newer firmware fix it
This is good! I'll sticky it when I get a chance later tonight. I'm mobile atm
Maybe I'm missing something.
https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326
It's been here for some time.
Nothing wrong with your guide it's decent but the info provided is actually already here mate.
Root, twrp, de-brand, OTA, it's all there
dladz said:
Maybe I'm missing something.
https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326
It's been here for some time.
Nothing wrong with your guide it's decent but the info provided is actually already here mate.
Root, twrp, de-brand, OTA, it's all there
Click to expand...
Click to collapse
They're a bit different. The debrand thread is obviously good but much more specific to debranding. This is a more generic for general How-To's
dladz said:
Maybe I'm missing something.
https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326
It's been here for some time.
Nothing wrong with your guide it's decent but the info provided is actually already here mate.
Root, twrp, de-brand, OTA, it's all there
Click to expand...
Click to collapse
I was reading this one as well but like matt4321 already said, it is actually for a different purpose.
And even the "ROOT ONLY" instructions are either widespread over the whole P20 Pro forum, incomplete or even outdated:
Linking to other threads with endless, partly revised instructions (on page n of the thread).
Referring to wrong official TWRP that can not use internal storage.
Hard to understand for beginners on this device (not even talking about someone who is entirely new to all of this).
Missing steps or expecting that you have already successfully flashed your first ROM (talking about advanced things like rebranding).
Don't get me wong, I am used to read a lot when it comes to custom ROMs (if you check the old part of my signature you can see that I am not actually a newbie here and my roots actually reach back to when all of the Android stuff startet at all, back when XDAs flashed HTC HD2 WinMo to Android). However I really missed a guide that actually collects all the basic information for beginners without going off roads too early.
These are more or less the steps I'm used to when I owned my nexus phones.
I have some questions:
If I root my phone and install, let's say adaway, will I be able to receive OTA? Or I will have to flash a new image manually?
If after root I relock bootloader, will I be able to unlock it again later for further modding?
This method implies that I can return to stock anytime and relock bootloader?
Thanks for the guide and answers , great job
mangusZen said:
If I root my phone and install, let's say adaway, will I be able to receive OTA? Or I will have to flash a new image manually?
Click to expand...
Click to collapse
Yes, exactly what I am doing. I need root for some apps and besides that I am happy with the stock OTA ROM, at least for the moment. OTA updates work fine so far.
The only thing as explained in my guide is that OTA updates will fail as they boot into TWRP instead of original fastboot. Therefore you need to explicitly boot into TWRP and install the downloaded OTA update with "HuRUpdater_0.3.zip".
mangusZen said:
If after root I relock bootloader, will I be able to unlock it again later for further modding?
Click to expand...
Click to collapse
From what I have read so far re-locking your bootloader is not advised. You seem to be unable to unlock it again or at least need to request another unlock code from Huawei.
At least this is my understanding of the situation so far.
mangusZen said:
This method implies that I can return to stock anytime and relock bootloader?
Click to expand...
Click to collapse
Returning to stock is even easier if you keep eRecovery working as explained in the guide (flashing TWRP only to recovery_ramdisk partition). With eRecovery you can wipe TWRP and root and let eRecovery download and install the latest official stock ROM.
Regarding the bootloader re-locking, see my answer above.
Xcelsior said:
Yes, exactly what I am doing. I need root for some apps and besides that I am happy with the stock OTA ROM, at least for the moment. OTA updates work fine so far.
The only thing as explained in my guide is that OTA updates will fail as they boot into TWRP instead of original fastboot. Therefore you need to explicitly boot into TWRP and install the downloaded OTA update with "HuRUpdater_0.3.zip".
From what I have read so far re-locking your bootloader is not advised. You seem to be unable to unlock it again or at least need to request another unlock code from Huawei.
At least this is my understanding of the situation so far.
Returning to stock is even easier if you keep eRecovery working as explained in the guide (flashing TWRP only to recovery_ramdisk partition). With eRecovery you can wipe TWRP and root and let eRecovery download and install the latest official stock ROM.
Regarding the bootloader re-locking, see my answer above.
Click to expand...
Click to collapse
Ok, so to install OTA I have to use hurupdater method and flash the OTA package manually.
For what I read and understood, but I may be wrong, the problem with relocking bootloader is encountered by who used the funkyhuawei method, that alters bootloader in some way, especially to achive the mono sim - dual sim switch.
With this you cant for now re unlock the bootloader again.
But I could be wrong and be like that for everyone, will see if someone will come up with some clarifications.
It would be nice to have the ability to return to stock, lock bootloader and use warranty
[emoji14]
Thanks for your work and answers
mangusZen said:
Ok, so to install OTA I have to use hurupdater method and flash the OTA package manually.
Click to expand...
Click to collapse
Yes, that is basically what "HuRUpdater_0.3.zip" will do, it will flash/install an OTA update that has previously been downloaded.
Wipe cache afterwards and be happy with your new up to date stock ROM version.
Xcelsior said:
Yes, that is basically what "HuRUpdater_0.3.zip" will do, it will flash/install an OTA update that has previously been downloaded.
Wipe cache afterwards and be happy with your new up to date stock ROM version.
Click to expand...
Click to collapse
I have to rename the downloaded OTA packages for huru to work, right?
mangusZen said:
I have to rename the downloaded OTA packages for huru to work, right?
Click to expand...
Click to collapse
Not for me. Just downloaded the OTA update via the EMUI system menu in Android, rebooted into TWRP and installed (aka executed) HuRu.
HuRu did the rest for me.
Tested with 120 -> 128 OTA update.
Hi It is late at night and I am not sure if I typed fastboot flash recovery twrp_clt_0.1.img instead off fastboot flash recovery_ramdisk twrp_clt_0.1.img. How can I make sure I still have erecovery? super newbie to android rooting, please help Thank you
Amowiel said:
Hi It is late at night and I am not sure if I typed fastboot flash recovery twrp_clt_0.1.img instead off fastboot flash recovery_ramdisk twrp_clt_0.1.img. How can I make sure I still have erecovery? super newbie to android rooting, please help Thank you
Click to expand...
Click to collapse
Simplest way would be to try to boot into eRocovery:
Power off the phone.
Power on the phone until you see the "you are a baddy because you unlocked your bootloader" screen.
Hold volume up (you can already hold it when powering on the phone) until you end up in eRecovery or TWRP.
If you end up in TWRP it should still be possible to recover your eRecovery with a proper backup of the "recovery" partition from any other P20 Pro.
Xcelsior said:
Simplest way would be to try to boot into eRocovery:
Power off the phone.
Power on the phone until you see the "you are a baddy because you unlocked your bootloader" screen.
Hold volume up (you can already hold it when powering on the phone) until you end up in eRecovery or TWRP.
If you end up in TWRP it should still be possible to recover your eRecovery with a proper backup of the "recovery" partition from any other P20 Pro.
Click to expand...
Click to collapse
thank you so much for such a quick reply, can confirm that my brain was not so fried and I didn't wipe my ercovery
thank you for your amazing guide, everything worked perfectly
mangusZen said:
Ok, so to install OTA I have to use hurupdater method and flash the OTA package manually.
For what I read and understood, but I may be wrong, the problem with relocking bootloader is encountered by who used the funkyhuawei method, that alters bootloader in some way, especially to achive the mono sim - dual sim switch.
With this you cant for now re unlock the bootloader again.
But I could be wrong and be like that for everyone, will see if someone will come up with some clarifications.
It would be nice to have the ability to return to stock, lock bootloader and use warranty
[emoji14]
Thanks for your work and answers
Click to expand...
Click to collapse
Actually you don't in some cases, if your simply rooted with twrp and you want to install an OTA that's been advertised to your device. All you need to do is install the nocheck recovery IMG and then take the update, reinstall twrp and magisk after the update and you're done.
If it's an update that's not advertised to your device yet then hur updater is the way.