Related
Hi,
After changing my phone's date into the future, my G2 Touch told me there was an update available, so I told it to go ahead and apply it. When the phone rebooted it came up with this message:
E:No signature (218 files)
E:Verification failed
Installation aborted
I have nandroid installed on the phone. At least I think that's what's installed - I haven't played with any ROM stuff since November I think, when I changed the bootloader (I think - if that's what's giving me the option to do a nandroid backup now) and installed the newest T-Mobile G2 ROM.
Should the phone be able to install the OTA update, or will I have to replace the bootloader in order to get the OTA update on there? If I do have to replace the bootloader, will that require a full wipe?
James
Completely the same problem with HTC Hero after European OTA update. It has been rooted while ago (by following instructions from this forum) and now after setting up date in the future and confirming update, phone reboot and I get "Android System recovery" screen with menu and this message bellow it:
Build: CyaanogenMod v1.4 + JF
Finding update package ...
Opening update package ...
Veryfing update package ...
E: No signature (218 files)
E: Verification failed
Installation aborted.
Click to expand...
Click to collapse
I have the same problem (I did not write down the message, so I'm not sure which "Build:" was listed) .
The update fails, the phone reboots and then works under the old build. Under "settings/about phone" there is also no info about the update. Can one force the phone to download the update a second time? Would this help?
Bye
Nick
P.S. I'm running the phone in Germany over e-plus as network provider. The updates was done over a WiFi connection. The phone is not branded - was from the free market and not from a provider.
Hey,
got the same problem. At least I could extract the official OTA-update-zip to publish it here (see attachment)
There also is a "recovery.img" in the update zip, so I guess usually the OTA update will kill custom recovery bootloaders. We could replace the "recovery.img" in the zip with a hacked one before applying the update.
However first we should fix the verification error...
P.S.: Also Germany, not branded, Vodafone Network
Does anyone know if I will lose all my data if I reflash the original recovery.img onto my phone?
As I used flashrec to flash ra-recovery.img I keept all my data. So I don't belive you will lost any of your data except of your actual recovery image.
At last, we can try to flash origianl RUU, but with this we lost all our personal data.
----
I tried it. I installed flasrec.apk using ASTRO and used this app to flash the recovery.img from here mentioned/linked OTA update zip. Afterwards I changed date again and was able to install OTA Update without errors and loosing personal data. Now I'm without nandroid because of changing recovery image. Keep cool at this procedure installing these flashes takes long time in boot process - I was really near an hard reset ...
Flashing the original recovery.img should not be a problem.
However, I don't want to lose root access, and thus I will wait for the official HTC 2.1-update (hoping someone publishes it online) and then flash it by myself..
I don't mind losing root access at this moment (the reason I rooted my phone was to get wifi tethering but never got it working with a mac).
Since I am total noob with android stuff, I would highly appreciate some step by step instructions or link where I can find what to do. Thanks guys.
Hi, I've been trying to install the recovery.img from the update but I get this message with flashrec 1.1.3:
Code:
"Flash FAILED: Could not run command."
I'm using WWE 405.66 flashed with ra-recovery img 1.6.2... and the rom is rooted.
What am I doing wrong?
I can't even install ra-recovery with flashrec now and I have installed ra-recovery 1.6.2 this morning (I was using 1.5)
And yes, I know I'm going to lose ra-recovery.
rseffner said:
As I used flashrec to flash ra-recovery.img I keept all my data. So I don't belive you will lost any of your data except of your actual recovery image.
At last, we can try to flash origianl RUU, but with this we lost all our personal data.
----
I tried it. I installed flasrec.apk using ASTRO and used this app to flash the recovery.img from here mentioned/linked OTA update zip. Afterwards I changed date again and was able to install OTA Update without errors and loosing personal data. Now I'm without nandroid because of changing recovery image. Keep cool at this procedure installing these flashes takes long time in boot process - I was really near an hard reset ...
Click to expand...
Click to collapse
What was the rom you were using when you flashed the official recovery?
alvaritolalala said:
Hi, I've been trying to install the recovery.img from the update but I get this message with flashrec 1.1.3:
Code:
"Flash FAILED: Could not run command."
I'm using WWE 405.66 flashed with ra-recovery img 1.6.2... and the rom is rooted.
What am I doing wrong?
I can't even install ra-recovery with flashrec now and I have installed ra-recovery 1.6.2 this morning (I was using 1.5)
And yes, I know I'm going to lose ra-recovery.
Click to expand...
Click to collapse
Try the following:
- Copy the recovery.img to your SD card
- Turn off the phone, turn it on with Buttons "HOME"+"ONOFF" pressed such that the ra-recovery which you already have starts
- connect to your phone by cable using "adb shell"
- Then with root access you can flash the image by typing "flash_image recovery /sdcard/recovery.img"
This should do it
jamesots said:
Hi,
After changing my phone's date into the future, my G2 Touch told me there was an update available, so I told it to go ahead and apply it. When the phone rebooted it came up with this message:
E:No signature (218 files)
E:Verification failed
Installation aborted
I have nandroid installed on the phone. At least I think that's what's installed - I haven't played with any ROM stuff since November I think, when I changed the bootloader (I think - if that's what's giving me the option to do a nandroid backup now) and installed the newest T-Mobile G2 ROM.
Should the phone be able to install the OTA update, or will I have to replace the bootloader in order to get the OTA update on there? If I do have to replace the bootloader, will that require a full wipe?
James
Click to expand...
Click to collapse
hey,
I had same problem
go to All programs--> Recovery Flasher--> Restore backup
then restart and update OTA
Greetings from Zagreb, Croatia
Hey guys.
So, for those of you, who do NOT care about root for now, here's what worked for me:
1.: Download the zip-file with the OTA Update, mentioned on the first page and extract it.
2.: Connect your Hero to your PC and copy the recovery.img from the OTA onto your sdcard. Disconnect from computer.
3.: Boot your phone into the bootloader (Home + PWR).
EDIT: Now connect the phone to the pc again!
4.: open the command prompt of your pc, navigate to your Android SDK folder. (If it is not installed, download it and make sure you've got the needed drivers. Otherwise: Download them, using the Setup.exe from Android SDK)
5.: Here are the needed commands:
Code:
adb shell
$su
mount -a
flash_image recovery /sdcard/recovery.img
6.: reboot your phone after exitting the command prompt.
7.: Factory reset, reboot again
8.: And well, wait for the update-window again and be happy, now it should work
EDIT 2:
Any questions? Just leave a reply
@Revoluzifer
OK I did exactly as you explained, but having problem with su command:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
I know I know, you're going to say my phone is not rooted at all But believe me it was and some apps that require root access are there (screenshot, wifi tether etc.).
I even tried to find su cmd with find:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
But got nothing as you can see.
Ideas?
@dinke:
Which bootloader / recovery console is installed?
Means, what do you see, after booting with Home + PWR?
Also try to input $su instead of just su.
But first tell me your "hack" if any
@Revoluzifer
Thanks for quick reply
I see Android system recovery screen, not sure if this is nandroid or what but have this text on the screen with following options:
Android system recovery <2>
Use trackball to highlight;
click to select.
[Home+Back] reboot system now
[Alt+S] apply sdcard:update.zip
[Alt+W] wipe data/factory reset
[Alt+B] nandroid v2.2 backup
[Alt+R] restore latest backup
[Alt+F] repair ext filesystems
-------------------------------
Click to expand...
Click to collapse
And bellow menu there is build ID:
Build: CyanogenMod v1.4 + JF
I don't remember exact procedure that I applied for rooting hero, but I followed instructions from this forum (I can try by searching for exact thread if that may help you).
Edit: I applied root procedure by following instructions on these two links:
http://forum.xda-developers.com/showpost.php?p=4257045
http://forum.xda-developers.com/showthread.php?t=559613
That sounds just perfect
CyanogenMod 1.4 is exactly the same recovery console i have had before.
(Btw, Hero is not officially supported by CM anymore, had a nice discussion yesterday in cyanogen IRC )
So, try to use $su instead of su, that's what I typed and it all worked just great.
But you definitely first booted into bootload and then connected the phone to your pc again?
Tell me if this worked for you, please...
Greetz,
Sven
dinke said:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
Click to expand...
Click to collapse
Forget about the "su". You are already root.
(You can see this, as there's a '#' in front)
Just do the mounting and flashing
Oh... You're right, nerdture... didn't see the #
I *think* I've tried mount no matter of missing 'su' cmd and it didn't work either but will try again as soon as I manage to find some cable to connect hero with macbook (no longer nearby windows machine but have sdk installed on mac so should be working as well)
Revoluzifer said:
But you definitely first booted into bootload and then connected the phone to your pc again?
Click to expand...
Click to collapse
Yes
No clockworkmod recovery needed. And this won't break root on system updates you will just have to update su binary after each system update.
(1) Download developer ROM from here http://en.miui.com/download-101.html#164
(2) Copy file to root folder on phone storage and rename the file to update.zip.
(3) Power off the phone then hold volume up and power key till mi logo pops to boot into recovery mod.
(4) Select language, click volume down to navigate to 'Install update,zip to System One' and hit power button to select.
(5) Wait for Install to complete (usually progress stops at 98% for while but do not panic and wait for it to complete).
(6) Now hit Reboot then Reboot to System One after update and reboot go to security enable root permission install Super SU from playstore, open the app and update Su binary.
(7) Now phone is rooted, Super Su is installed, Su binary is updated so you can go and disable root permission from security app and let Super Su manage root permissions instead.
Note- when ever you install an update from phone it will install update to system two
and when you update from recovery it will install update to system one
I am not a DEV, just sharing what I know.
Which method is recommended? Rooting with package through recovery or through system settings menu within MiUi?
i download the developer rom when i went to flash it, it says its for pieces your device is cancro . so whats the problem /
mandarpalshikar said:
Which method is recommended? Rooting with package through recovery or through system settings menu within MiUi?
Click to expand...
Click to collapse
You can use any method, just use same method every time so one of the two system stays stock.
Babu-Ji said:
i download the developer rom when i went to flash it, it says its for pieces your device is cancro . so whats the problem /
Click to expand...
Click to collapse
Try flashing it from recovery. And make sure you downloaded developer ROM for 'WCDMA/CDMA China' and not 'TD'.
vikie said:
No clockworkmod recovery needed. And this won't break root on system updates you will just have to update su binary after each system update. Also from what I know this method does not void your warranty.
(1) Download developer ROM from here http://en.miui.com/download-101.html#164
(2) Copy file to root folder on phone storage and rename the file to update.zip.
(3) Power off the phone then hold volume up and power key till mi logo pops to boot into recovery mod.
(4) Select language, click volume down to navigate to 'Install update,zip to System One' and hit power button to select.
(5) Wait for Install to complete (usually progress stops at 98% for while but do not panic and wait for it to complete).
(6) Now hit Reboot then Reboot to System One after update and reboot go to security enable root permission install Super SU from playstore, open the app and update Su binary.
(7) Now phone is rooted, Super Su is installed, Su binary is updated so you can go and disable root permission from security app and let Super Su manage root permissions instead.
Note- when ever you install an update from phone it will install update to system two
and when you update from recovery it will install update to system one
I am not a DEV, just sharing what I know.
Click to expand...
Click to collapse
Its not available for any snapdragon 800 variant. Its just for TD and CHINESE version of MI3. And even if somehow works on other MI3. If you flash this you will still void warranty as it's not officially given by xiaomi.
Now you will say how will they know. Its the same phone. They will known when you will go to claim the warranty in your country. I don't think you will go to china to claim the warranty of your phone and even if you do go to china for that
a. Your phone should have international warranty.
b. And that person giving you warranty should be stupid enough to ignore the country mentioned in your bill and also ignore the fact that no developer version is available for your country.
Lots if if's and buts and travelling just to claim warranty.
Okay, I was not sure about warranty thing any way. Will edit that. Also you could have just replied, didn't had to quote the whole thing. I am pretty sure buying new phone would be cheaper than going to china for warranty. Also I am sure people who use xda and flash custom roms would not cry for warranty. And this is no twitter so won't argue on this further.
I have the LG Power (aka LG Leon) from Tracfone, which has a protected bootloader. KingRoot roots it, but its su binary is not fully compatible with all root apps. Fooling around with KingRoot, I found a way to ultimately root the phone with SuperSU, using KingRoot as a "mule" app to do it.
Warning: As always, you can make your device unusable by attempting to root it. You follow these instructions at your own risk.
Download KingRoot from kingroot.net, install it, and let it do its thing. You may have to try a couple or three times before it gains root.
Install SuperSU from Google Play. Open it and "Cancel" the prompt to update the su binary (it won't work, yet). Configure SuperSU to your preferences, and grant it root permission when KingUser asks.
Install a root browser such as ES File Explorer from Google Play, open it, and enable root access. KingUser should prompt to allow it root.
You will need a copy of the SuperSU su binary. It is not yet in the /system/xbin folder, as KingRoot has control over that. You can get it through ChainFire's site, or from the "root.zip" file attached to this thread: http://forum.xda-developers.com/fir...ne-supersu-t3105546/post60669196#post60669196
Load the mule with the payload. Browse to /data/data/com.kingroot.kinguser using the root browser and REPLACE all instances of "su" with the SuperSU version of the su binary. You will find at least two deeply embedded in the directory tree.
Now wait, possibly for several minutes. KingRoot will eventually check its integrity and find that the installed su binary is different than the one it its data directory. It will reinstall automatically and test its access. If successful, you will see a SuperSU prompt to grant KingRoot superuser access! :victory: Deny it.
Now open SuperSU again and allow it to upgrade the su binary through the "Normal" method. It should succeed.
Restart the device.
Open SuperSU again to test root access. Open a few root apps such as the root explorer. SuperSU should prompt to grant root access.
You can uninstall KingRoot (and Purify, if you want).
Some issues that I ran into that may or may not be of concern to you:
After rooting, my device became unstable and would freeze a few minutes after restarting. I had to take out the battery to restart it. I was messing around a lot with it, so most likely it's something else I did. However, if this happens to you, go into "Safe Mode" by powering it on, waiting for the LG Logo to appear, then holding the "volume down" button until you see the default launcher screen with "Safe Mode" in the lower left corner. Give it many minutes to settle in, then restart normally. This restores a few things to default (such as your widgets, which you will have to re-configure).
SuperSU asked me a second time to update the su binary. I allowed it, and it never asked me again.
If all else fails and you can't get a stable root, install KingRoot again and have it re-root the phone.
FlashFire works on this phone after rooting as above. I was able to successfully flash Xposed to the device.
Don't try to flash TWRP, however. The bootloader is locked and you will lose recovery if you do this. (Yes, I did it.)
this not work on H340n with android 6.0
gsearle5 said:
FlashFire works on this phone after rooting as above. I was able to successfully flash Xposed to the device.
Don't try to flash TWRP, however. The bootloader is locked and you will lose recovery if you do this. (Yes, I did it.)
Click to expand...
Click to collapse
Hey, quick question because I'm still not getting the framework to successfully flash. Which version of the framework did you use specifically?
Corbow6 said:
Hey, quick question because I'm still not getting the framework to successfully flash. Which version of the framework did you use specifically?
Click to expand...
Click to collapse
I flashed version 81. It's working great, so I haven't attempted to upgrade yet.
gsearle5 said:
FlashFire works on this phone after rooting as above. I was able to successfully flash Xposed to the device.
Don't try to flash TWRP, however. The bootloader is locked and you will lose recovery if you do this. (Yes, I did it.)
Click to expand...
Click to collapse
I had the same issue... So after lots of searching I found a stock 5.0.1 recovery for a LG G3 that works. The zip file is NOT flashable but just unzip the recovery.img and flash that with FlashFire. You can then turn off the phone, press & hold vol- & power till the phone vibrates the continue to hold vol- and release then press and hold power again to enter stock recovery.
voluptuary said:
I had the same issue... So after lots of searching I found a stock 5.0.1 recovery for a LG G3 that works. The zip file is NOT flashable but just unzip the recovery.img and flash that with FlashFire. You can then turn off the phone, press & hold vol- & power till the phone vibrates the continue to hold vol- and release then press and hold power again to enter stock recovery.
Click to expand...
Click to collapse
Thank you! I'll try it out. What do I have to lose, recovery?
gsearle5 said:
I flashed version 81. It's working great, so I haven't attempted to upgrade yet.
Click to expand...
Click to collapse
I just updated to version 86 without a hitch.
Looks like I celebrated too soon, while you can enter recovery with the IMG I posted above it won't actually do anything... except make you have to pull the battery out. Least you don't get an error in the top left corner anymore so there's that.
Just installed the new Xposed Framework self-installer for Lollipop on this device (LG Power). It worked flawlessly.
http://forum.xda-developers.com/showthread.php?t=3034811
Hello,
I have the device HTC Desire 825 with the pre-installed 6.0.1. I have tried loads to root my device, I have tried all the one-click root ways from Kingo etc but they all fail.
I tried to find a way to flash the device but on the list of devices, the HTC Desire 825 is not on the list. Not sure if there is a way to root it or not, I done it before on previous devices but never been stuck like this. If someone knows a way, please tell me how, it would be much appreciated
Thank you,
zemauk said:
Hello,
I have the device HTC Desire 825 with the pre-installed 6.0.1. I have tried loads to root my device, I have tried all the one-click root ways from Kingo etc but they all fail.
I tried to find a way to flash the device but on the list of devices, the HTC Desire 825 is not on the list. Not sure if there is a way to root it or not, I done it before on previous devices but never been stuck like this. If someone knows a way, please tell me how, it would be much appreciated
Thank you,
Click to expand...
Click to collapse
Why not you try goes to HTC dev..might be they knew it much better..I mean rooting your devuces
HTC dev - all other devices.
Twrp found in a discussion here in one of the threads.
Latest Superuser Beta zip or img.
brunkonjaa said:
HTC dev - all other devices.
Twrp found in a discussion here in one of the threads.
Latest Superuser Beta zip or img.
Click to expand...
Click to collapse
And how I can install TWRP to use for root my device?
Xxshark888xX said:
And how I can install TWRP to use for root my device?
Click to expand...
Click to collapse
Go to HTC dev site. Register. Log in. Look for "unlock bootloader" option. Click on it. Follow instructions. Great, you have now unlocked your bootloader !
Now, in order to unlock bootloader you had to download HTC fastbooot . Open the folder where that HTC fast boot has been extracted.....
Now, previously downloaded Superuser and Twrp files......
Place them in that folder where you extracted your HTC fastboot files.
Right click on empty space anywhere inside that folder while holding "shift", and you will get an option to "open cmd window here". Click on it. Type "adb devices". Your phone should show as some numbers followed by the word device ( "1234567 device").
Your device should be recognized and you can continue to the next step. If it isn’t recognised then you should re-install all the USB Drivers for your device.
Next, enter the following command line in CMD in order to flash the TWRP Recovery files:?*fastboot flash recovery "name of downloaded recovery".img.
When the TWRP Recovery file is successfully installed, CMD will display a confirmation message. Disconnect the device from computer now.Use the Volume buttons to select ‘HBOOT’ option on your smartphone and select it by pressing Power. Test to see if the RECOVERY mode works by selecting the ‘RECOVERY’ option. Your phone should boot into TWRP Recovery mode now and this means that the install has been successfully completed.
To install Superuser, repeat above steps BUT instead of typing "Twrp xxxxxx.img" type "name of superuser file". Once you have confirmation of the file being sent, disconnect from PC, enter recovery, choose install, and click on the superuser file.
Little tip: I spent hours trying to send both Twrp and superuser files to the phone with all kinds error messages showing inside cmd screen. File too big, can't read file, destination unreachable...... then I found simple solution:
Inside the fastboot folder I created new empty folder.
I copy/pasted Twrp and superuser files inside of it.
Opened cmd folder inside of that new folder and tried sending files again, one at the time. It worked flawlessly straight away.
Little tip 2: if you have trouble writing the names of your Twrp and superuser files in your cmd window, you can do the following:
Type "fastboot flash recovery", press space bar once, now left click on the required file in you fastboot folder (Twrp or superuser) and drag it across into your cmd window.
If you need anything else, feel free to ask. When dealing with this kind of fiddling with your device, no question is stupid or irrelevant.
brunkonjaa said:
Go to HTC dev site. Register. Log in. Look for "unlock bootloader" option. Click on it. Follow instructions. Great, you have now unlocked your bootloader !
Now, in order to unlock bootloader you had to download HTC fastbooot . Open the folder where that HTC fast boot has been extracted.....
Now, previously downloaded Superuser and Twrp files......
Place them in that folder where you extracted your HTC fastboot files.
Right click on empty space anywhere inside that folder while holding "shift", and you will get an option to "open cmd window here". Click on it. Type "adb devices". Your phone should show as some numbers followed by the word device ( "1234567 device").
Your device should be recognized and you can continue to the next step. If it isn’t recognised then you should re-install all the USB Drivers for your device.
Next, enter the following command line in CMD in order to flash the TWRP Recovery files:?*fastboot flash recovery "name of downloaded recovery".img.
When the TWRP Recovery file is successfully installed, CMD will display a confirmation message. Disconnect the device from computer now.Use the Volume buttons to select ‘HBOOT’ option on your smartphone and select it by pressing Power. Test to see if the RECOVERY mode works by selecting the ‘RECOVERY’ option. Your phone should boot into TWRP Recovery mode now and this means that the install has been successfully completed.
To install Superuser, repeat above steps BUT instead of typing "Twrp xxxxxx.img" type "name of superuser file". Once you have confirmation of the file being sent, disconnect from PC, enter recovery, choose install, and click on the superuser file.
Little tip: I spent hours trying to send both Twrp and superuser files to the phone with all kinds error messages showing inside cmd screen. File too big, can't read file, destination unreachable...... then I found simple solution:
Inside the fastboot folder I created new empty folder.
I copy/pasted Twrp and superuser files inside of it.
Opened cmd folder inside of that new folder and tried sending files again, one at the time. It worked flawlessly straight away.
Little tip 2: if you have trouble writing the names of your Twrp and superuser files in your cmd window, you can do the following:
Type "fastboot flash recovery", press space bar once, now left click on the required file in you fastboot folder (Twrp or superuser) and drag it across into your cmd window.
If you need anything else, feel free to ask. When dealing with this kind of fiddling with your device, no question is stupid or irrelevant.
Click to expand...
Click to collapse
Thanks for the help. I successful rooted my HTC Desire 825. But I have another question. I downloaded Titanium Backup to uninstall bloatware apps. the problem is that after uninstalling the apps still remain in the memory of the device, why?
Xxshark888xX said:
Thanks for the help. I successful rooted my HTC Desire 825. But I have another question. I downloaded Titanium Backup to uninstall bloatware apps. the problem is that after uninstalling the apps still remain in the memory of the device, why?
Click to expand...
Click to collapse
Oh the joys of bloatware!!!!!!!
Here's what I did: after trying to remove it, and soft bricking ????, I installed xposed, lucky patched and Greenify. In this forum I am not allowed to explain how I got specific version of Greenify that works with lucky patcher patch in order to gain pro version, so I won't explain it ????.
I simply greenified most of bloatware, so it's out if the way.
I know it doesn't really answer your question but at least it allows to keep the beast at bay.
brunkonjaa said:
Oh the joys of bloatware!!!!!!!
Here's what I did: after trying to remove it, and soft bricking ????, I installed xposed, lucky patched and Greenify. In this forum I am not allowed to explain how I got specific version of Greenify that works with lucky patcher patch in order to gain pro version, so I won't explain it ????.
I simply greenified most of bloatware, so it's out if the way.
I know it doesn't really answer your question but at least it allows to keep the beast at bay.
Click to expand...
Click to collapse
I already have Lucky Patcher. Later I will search Greenify and try to uninstall all the bloatware. Thanks again ?
Xxshark888xX said:
I already have Lucky Patcher. Later I will search Greenify and try to uninstall all the bloatware. Thanks again ?
Click to expand...
Click to collapse
Unlike stock Android, manufacturer skins like TouchWiz, Sense etc. come with a plethora of pre-loaded apps that you can’t uninstall. Be careful.
Xxshark888xX said:
I already have Lucky Patcher. Later I will search Greenify and try to uninstall all the bloatware. Thanks again ?
Click to expand...
Click to collapse
Hi! Did you manage to uninstall any of the bloatware?
Xxshark888xX said:
Thanks for the help. I successful rooted my HTC Desire 825. But I have another question. I downloaded Titanium Backup to uninstall bloatware apps. the problem is that after uninstalling the apps still remain in the memory of the device, why?
Click to expand...
Click to collapse
The uninstalled Apps will crawl back after reboot because the device is still S-ON. There are couple ways to handle this. One is to S-OFF the device using Sunshine or similar app. Method 2 is using TWRP. Use the TWRP built-in file explorer, mount system, head to where the apps are and delete the ones you wouldn't need.
Hello guys. Does someone have a back up of the htc 825 stock recovery.img? Maybe someone can extract the stock recovery and share it here please ?
stenlibi said:
Hello guys. Does someone have a back up of the htc 825 stock recovery.img? Maybe someone can extract the stock recovery and share it here please ?
Click to expand...
Click to collapse
Hi, did you manage to find the recovery img?
I need to flash it instead of buggy twrp, searched for hours and nowhere to be found
Ok, i've managed to find it This is the stock recovery IMG, working fine, extracted from original firmware.
https://mega.nz/#!yYd30a7A!hK7RoQjhWkG8S2nS3__B8xbnwAssN4QI59rXJyQ1y9o
Credits go to nkk71 https://forum.xda-developers.com/member.php?u=2605798 for the great tool to exctract the firmware image,
without it i wouldn't accomplish the task.
If the link will die, PM me, i'll reupload.
Notes:
Updated Android security patch to August 2020
Colors look super bleached after update... Anyone else??
EDIT: Nevermind... Toggled themes and it went away.
Anyone have it rooted that can share magisk patched boot img from .37?
Holy crap. It actually came thru right away. Not even having to wait a day or two. Giant improvement over 10.0.36. Now if they'd only start giving us the new features available for the global 7t pro.
kirschdog1 said:
Anyone have it rooted that can share magisk patched boot img from .37?
Click to expand...
Click to collapse
Here's the one I pulled from the phone as part of the root process.
starcms said:
Holy crap. It actually came thru right away. Not even having to wait a day or two. Giant improvement over 10.0.36. Now if they'd only start giving us the new features available for the global 7t pro.
Click to expand...
Click to collapse
Giant improvement? I thought it was just a security update?
kirschdog1 said:
Giant improvement? I thought it was just a security update?
Click to expand...
Click to collapse
Giant improvement in OTAs actually showing up/being able to download. The vast vast majority of people had never gotten the update from 10.0.35 to 10.0.36.
---------- Post added at 11:07 ---------- Previous post was at 10:43 ----------
Btw, how to best update OTA and keep root:
It literally takes 30 seconds to install/accept/download OTA and keep root.
A) Use Magisk Manager app to uninstall (click uninstall and click restore images -- don't do a complete uninstall). Don't reboot yet.
B) Accept, download, and install OTA -- do NOT reboot yet!
C) After OTA update is successfully completed and it's asking to reboot, open Magisk Manager, and choose to "install via inactive slot (after OTA)"
D) Reboot, and you'll be upgraded and rooted.
starcms said:
Giant improvement in OTAs actually showing up/being able to download. The vast vast majority of people had never gotten the update from 10.0.35 to 10.0.36.
---------- Post added at 11:07 ---------- Previous post was at 10:43 ----------
Btw, how to best update OTA and keep root:
It literally takes 30 seconds to install/accept/download OTA and keep root.
A) Use Magisk Manager app to uninstall (click uninstall and click restore images -- don't do a complete uninstall). Don't reboot yet.
B) Accept, download, and install OTA -- do NOT reboot yet!
C) After OTA update is successfully completed and it's asking to reboot, open Magisk Manager, and choose to "install via inactive slot (after OTA)"
D) Reboot, and you'll be upgraded and rooted.
Click to expand...
Click to collapse
So you're saying I don't have to do that whole resever.img thing anymore? I can now just unroot and get the ota? I always had issue getting OTAs.
lilaznboi5582 said:
So you're saying I don't have to do that whole resever.img thing anymore? I can now just unroot and get the ota? I always had issue getting OTAs.
Click to expand...
Click to collapse
Yep, that is correct, super easy now.
I was rooted on like version 27, didn't run the OTA fixer and I just got this installed and my phone rebooted. I kept getting notifications that there was an update, and I was like: "lEt Me sEe iF tHiS wIlL wOrK".
Magisk says not installed, I don't have an uninstall option.
I downloaded the .img file in this thread, do I still need to use Magisk to patch this file, or it's already patched: use fastboot on your PC running ADB to install Magisk again?
I was shocked to receive a full download of an OTA and even get it installed / update my phone. I almost passed out cause it was taking forever to boot and I thought I bricked it.
I just need to make sure all I gotta do is use the file in this thread for fastboot or if I have to patch it first then fastboot install
starcms said:
Giant improvement in OTAs actually showing up/being able to download. The vast vast majority of people had never gotten the update from 10.0.35 to 10.0.36.
---------- Post added at 11:07 ---------- Previous post was at 10:43 ----------
Btw, how to best update OTA and keep root:
It literally takes 30 seconds to install/accept/download OTA and keep root.
A) Use Magisk Manager app to uninstall (click uninstall and click restore images -- don't do a complete uninstall). Don't reboot yet.
B) Accept, download, and install OTA -- do NOT reboot yet!
C) After OTA update is successfully completed and it's asking to reboot, open Magisk Manager, and choose to "install via inactive slot (after OTA)"
D) Reboot, and you'll be upgraded and rooted.
Click to expand...
Click to collapse
I tried doing this method and it says "stock backup does not exist!" What did I do wrong? :silly:
Naruyasha said:
I tried doing this method and it says "stock backup does not exist!" What did I do wrong? :silly:
Click to expand...
Click to collapse
You most likely used Magisk Manager to patch the boot image and then got root by flashing "fastboot flash boot magisk_boot.img". This doesn't give Magisk Manager a chance to back up your stock boot image.
To root properly:
A) Flash your stock boot image.
"fastboot flash boot stock_boot.img"
B) Boot, NOT flash, boot image with Magisk installed (generated by Magisk Manager)
"fastboot boot magisk_boot.img"
C) Then go into Magisk Manager, choose install, direct install. And reboot.
Now you are rooted and Magisk Manager will have made a backup copy of your stock boot image so it can be very easily restored in the future.
I downloaded ADB from here:
Source Article & Directions - https://www.xda-developers.com/install-adb-windows-macos-linux
Direct Download Link - https://dl.google.com/android/repository/platform-tools-latest-darwin.zip
I extracted the folder to a place I will re-use later, opened up an administrator command prompt, downloaded the magisk_patched file from this thread, and typed this into my CMD:
D:
cd D:\Rype's Stuff\ADB {this is the folder I extracted ADB to & also where I placed the .img file}
fastboot boot magisk_patched.img
It's already patched with Magisk and is ready to boot your phone into a root state !
So I guess we don't need to run the OTA fixer any more, we just need a patched magisk every time?
After you fastboot boot magisk_patched, then your Root privileges will be enabled.
This will add a few more install options within Magisk Manager.
Tap on Install and then choose Install to Inactive Slot (after OTA).
{ONLY choose Direct Install if this was your first time installing Magisk onto your device.}
After the console says it's finished and there is a Reboot button: tap on it to reboot your device.
After the unlocked bootloader message, you should be permanently rooted everytime you boot, after an OTA.
starcms said:
You most likely used Magisk Manager to patch the boot image and then got root by flashing "fastboot flash boot magisk_boot.img". This doesn't give Magisk Manager a chance to back up your stock boot image.
To root properly:
A) Flash your stock boot image.
"fastboot flash boot stock_boot.img"
B) Boot, NOT flash, boot image with Magisk installed (generated by Magisk Manager)
"fastboot boot magisk_boot.img"
C) Then go into Magisk Manager, choose install, direct install. And reboot.
Now you are rooted and Magisk Manager will have made a backup copy of your stock boot image so it can be very easily restored in the future.
Click to expand...
Click to collapse
Direct install or inactive slot???
I thought Direct Install was for the literal 1st time installing Magisk
Then Install to Inactive Slot was for after OTA's.
I chose inactive slot and I've been on the T-Mobile boot image pink background screen for like 5 minutes now.
---------- Post added at 10:10 AM ---------- Previous post was at 09:36 AM ----------
starcms said:
Giant improvement in OTAs actually showing up/being able to download. The vast vast majority of people had never gotten the update from 10.0.35 to 10.0.36.
---------- Post added at 11:07 ---------- Previous post was at 10:43 ----------
Btw, how to best update OTA and keep root:
It literally takes 30 seconds to install/accept/download OTA and keep root.
A) Use Magisk Manager app to uninstall (click uninstall and click restore images -- don't do a complete uninstall). Don't reboot yet.
B) Accept, download, and install OTA -- do NOT reboot yet!
C) After OTA update is successfully completed and it's asking to reboot, open Magisk Manager, and choose to "install via inactive slot (after OTA)"
D) Reboot, and you'll be upgraded and rooted.
Click to expand...
Click to collapse
I choose install via inactive slot (after OTA) and now I'm stuck at the tmobile logo / screen.........
I was softbricked / boot looped.
I just needed to reboot into fastboot, then run:
fastboot --set-active=b
Now I'm able to reboot properly.
After testing the booting, I fastbooted again, this time into the patched magisk, and now I'm going to choose direct install.
-----------------------------------------------------
If you choose Install to Inactive Slot on accident, then you need to:
fastboot --set-active=b
fastboot boot magisk_patched_10.0.37.img
Open Magisk --> Install --> Direct Install
RypeDub said:
I was softbricked / boot looped.
I just needed to reboot into fastboot, then run:
fastboot --set-active=b
Now I'm able to reboot properly.
After testing the booting, I fastbooted again, this time into the patched magisk, and now I'm going to choose direct install.
-----------------------------------------------------
If you choose Install to Inactive Slot on accident, then you need to:
fastboot --set-active=b
fastboot boot magisk_patched_10.0.37.img
Open Magisk --> Install --> Direct Install
Click to expand...
Click to collapse
You only use install to inactive slot after downloading and installing but before rebooting an OTA update in order to keep from losing root. This is because the OTA is installed to the inactive slot. But once the phone reboots to finish installing OTA, it switches the slot with the OTA to be active and the slot with the older version of Android to be inactive.
"Direct Install" installs Magisk to the boot image of the Active Slot while "Install to Inactive Slot" installs Magisk to the boot image of the Inactive Slot.
starcms said:
You only use install to inactive slot after downloading and installing but before rebooting an OTA update in order to keep from losing root. This is because the OTA is installed to the inactive slot. But once the phone reboots to finish installing OTA, it switches the slot with the OTA to be active and the slot with the older version of Android to be inactive.
Click to expand...
Click to collapse
So what's the most effective method for having a working setup, taking the OTA and immediately reboot?
RypeDub said:
So what's the most effective method for having a working setup, taking the OTA and immediately reboot?
Click to expand...
Click to collapse
You already quoted my instructions...
To root properly:
A) Flash your stock boot image (if it's not stock).
"fastboot flash boot stock_boot.img"
B) Boot, NOT flash, boot image with Magisk installed (generated by Magisk Manager)
"fastboot boot magisk_boot.img"
C) Then go into Magisk Manager, choose install, direct install. And reboot
To update OTA and keep root:
A) Use Magisk Manager app to uninstall (click uninstall and click restore images -- don't do a complete uninstall). Don't reboot yet.
B) Accept, download, and install OTA -- do NOT reboot yet!
C) After OTA update is successfully completed and it's asking to reboot, open Magisk Manager, and choose to "install via inactive slot (after OTA)"
D) Reboot, and you'll be upgraded and rooted.
starcms said:
You already quoted my instructions...
To root properly:
A) Flash your stock boot image (if it's not stock).
"fastboot flash boot stock_boot.img"
B) Boot, NOT flash, boot image with Magisk installed (generated by Magisk Manager)
"fastboot boot magisk_boot.img"
C) Then go into Magisk Manager, choose install, direct install. And reboot
To update OTA and keep root:
A) Use Magisk Manager app to uninstall (click uninstall and click restore images -- don't do a complete uninstall). Don't reboot yet.
B) Accept, download, and install OTA -- do NOT reboot yet!
C) After OTA update is successfully completed and it's asking to reboot, open Magisk Manager, and choose to "install via inactive slot (after OTA)"
D) Reboot, and you'll be upgraded and rooted.
Click to expand...
Click to collapse
You read what I asked wrong.
I wasn't asking what is the CORRECT steps, I was asking what should / could I do if I messed up / did things in the wrong order.
But it's all good. Anyone who MESSED UP doing the proper way, can just look at all my posts and find out how I recovered.