Some help with ROM stuff (De-Bloating and some other things) - HTC Droid DNA

So what I am trying to do is get my feet wet with doing some dev work and basically I'm trying to figure out how to (without flashing anything, i want to remove the stuff myself):
De-bloat the stock sense rom and/or just remove all of the HTC garbage and use a different launcher all together without if affecting the system (Im not too sure what is acceptable to remove and what needs to stay in the /system/app/ dir)
Remove the annoying WiFi in the status bar
any and all help is much appreciated and even just pointing me in the right direction

Well you are going to have to flash something.
Sent from my HTC6435LVW using xda app-developers app

Bigandrewgold said:
Well you are going to have to flash something.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I guess what I was trying to say was I wanted to be able to do the work myself rather than flashing a zip someone else made to get rid of like lets say the wifi in status bar

.torrented said:
I guess what I was trying to say was I wanted to be able to do the work myself rather than flashing a zip someone else made to get rid of like lets say the wifi in status bar
Click to expand...
Click to collapse
Here's state of the art for today:
1. Hack DNA to make it look like non-Verizon to the htcdev.com site. Here's a new painless method: http://forum.xda-developers.com/showthread.php?t=2109862
2. Go to htcdev.com and follow link to unlock bootloader. Note that this will WIPE YOUR "SD CARD". It's the only thing that does that. No problem with ROMs, etc. Not even a "factory reset" wipes the "SD", but the bootloader unlock does. You can do a backup before rooting if you install ADB on your PC. See 3a.
3. Install ADB on your PC http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/ and test the connection with "adb devices" command.
a. Consider backup of DNA before unlocking http://forum.xda-developers.com/showthread.php?t=1420351
4. Install a recovery.
a. Dowload a recovery to your PC, either Clockworkmod http://forum.xda-developers.com/showthread.php?t=2051547 or TWRP http://forum.xda-developers.com/showthread.php?t=1994662. Extract the recovery.img file to a folder on your desktop,
b. Connect your DNA to your PC. Open a command prompt in the folder with the recovery by shift-right clicking in that folder and selecting "open command prompt here".
c. Type "adb reboot bootloader" without quotes and enter. DNA will reboot into bootloader. enter "fastboot flash recovery recovery.img" and you're there. You're done with the PC.
5. Install superuser and busybox.
a. Download superuser http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip to your "SD card".
b. Reboot to recovery. You can start recovery during a boot by holding down the volume down button during power up of phone.
c. Use the install zip function to install the above zip. Find links to wipe cach partition and Dalvik cache. Reboot and you're rooted.
d. Install busybox from market.
6. Change to a kernel that can write to system. Most reliable is LK 0.9.5. This will also save you considerable battery life. http://forum.xda-developers.com/showthread.php?t=2106178
a. Download the zip to your DNA and unzip it. There is a boot.img file and another zip file with "kernel modules".
b. Download flash image GUI from market. Use it to find the boot.img file and flash, ignoring the warning about modules. (hard way is use ADB and fastboot flash boot boot.img)
c. Use recovery to install the modules zip package with the install zip function. Wipe cache and Dalvik cache
and reboot.
7. Install Titanium Backup. With this, you can simply freeze or uninstall any app, system/bloat or otherwise, but it requires the system write kernel to change system files.
6. Stronly consider switching ROMs to Viper. All the good of stock but better in so many ways.

yearn2burn said:
Here's state of the art for today:
1. Hack DNA to make it look like non-Verizon to the htcdev.com site. Here's a new painless method: http://forum.xda-developers.com/showthread.php?t=2109862
2. Go to htcdev.com and follow link to unlock bootloader. Note that this will WIPE YOUR "SD CARD". It's the only thing that does that. No problem with ROMs, etc. Not even a "factory reset" wipes the "SD", but the bootloader unlock does. You can do a backup before rooting if you install ADB on your PC. See 3a.
3. Install ADB on your PC http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/ and test the connection with "adb devices" command.
a. Consider backup of DNA before unlocking http://forum.xda-developers.com/showthread.php?t=1420351
4. Install a recovery.
a. Dowload a recovery to your PC, either Clockworkmod http://forum.xda-developers.com/showthread.php?t=2051547 or TWRP http://forum.xda-developers.com/showthread.php?t=1994662. Extract the recovery.img file to a folder on your desktop,
b. Connect your DNA to your PC. Open a command prompt in the folder with the recovery by shift-right clicking in that folder and selecting "open command prompt here".
c. Type "adb reboot bootloader" without quotes and enter. DNA will reboot into bootloader. enter "fastboot flash recovery recovery.img" and you're there. You're done with the PC.
5. Install superuser and busybox.
a. Download superuser http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip to your "SD card".
b. Reboot to recovery. You can start recovery during a boot by holding down the volume down button during power up of phone.
c. Use the install zip function to install the above zip. Find links to wipe cach partition and Dalvik cache. Reboot and you're rooted.
d. Install busybox from market.
6. Change to a kernel that can write to system. Most reliable is LK 0.9.5. This will also save you considerable battery life. http://forum.xda-developers.com/showthread.php?t=2106178
a. Download the zip to your DNA and unzip it. There is a boot.img file and another zip file with "kernel modules".
b. Download flash image GUI from market. Use it to find the boot.img file and flash, ignoring the warning about modules. (hard way is use ADB and fastboot flash boot boot.img)
c. Use recovery to install the modules zip package with the install zip function. Wipe cache and Dalvik cache
and reboot.
7. Install Titanium Backup. With this, you can simply freeze or uninstall any app, system/bloat or otherwise, but it requires the system write kernel to change system files.
6. Stronly consider switching ROMs to Viper. All the good of stock but better in so many ways.
Click to expand...
Click to collapse
While all of this is very very helpful, I failed to mention that this isn't my first rodeo, While I have firm understanding of ADB and rooting and flashing, my approach was more of the "behind the scenes" kind of stuff like what goes on inside of the ROM (tweaking files and what not) I'm at the stage where im trying to learn how to cook a rom(i guess some would say). I've already done so with CM10.1 for my Nexus 7(compiled from sauce), im farily comfortable with linux and my way around the OS. I've got the kitchen setup as well as apktool and what Im trying to learn is how to use these tools to their full extent.
like to make the boot.img unsecure, create a "flashable signed zip", remove non essential apps, the starter stuff
A little bit of background about me: I love computers, im going to school for a Computer Science degree, this kind of work has always interested me and I cant seem to get enough of it, ever since ive discovered this site i cant keep away and i love this communty, I've always wanted to just do more than flash someone else's work, i want to give back and start being able to do things.
Like i said before thanks to everyone for any information its all much appreciated!

Related

[Q] Help with bootloop

Heu guys,
So after using cyanogenmod9, i felt like reverting tp stock.
Sp i got my kernel (xwkk2) and flashed it with odin. Now im in a bootloop. How the bejesus do i fix this?
Thanks
When I got in a boot loop two days ago all I did was wipe data, wipe cache, wipe dalvik cache and install a new ROM instead. If you don't have a removable microSD to put the ROM I suggest you look for the ADB Push tutorial. After your phone boots up try to install a stock Rom.
I don't if this helped but it worked for me.
Sent from my GT-I9100 using XDA
did you just flash a stock kernel? If so, you would get a bootloop as samsung kernels arent compatible with CM9.
Flash the entire rom instead of just the kernel.
ADB PUSH TUTORIAL (quoted from @brewtaz)
Requirements:
Unlocked Bootloader/Rooted Device
CWM Recovery flashed from fastboot.
Basic knowledge of adb/fastboot commands
Steps:
- Download your ROM of choice (referred to as ROM.zip) and place it wherever your ADB is on computer's harddrive (referred to as c:\AndroidSDK\tools)
- Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)
- Once this has completed, unplug your phone from your computer and close the Command Prompt window
- Back in Recovery, go to Recovery's main screen and Do a "Factory Reset", "Wipe Cache Partition", and "Wipe Dalvik Cache [which is in the Advanced menu of Recovery]"
- When these are all done, from Recovery's main screen, select "Install ZIP from SD Card" and then "Choose file from SD Card" and select the ROM.zip file you just pushed from your computer to the SD Card. If you do not see the file, go back to Mounts and Storage and toggle them to say "Mount /sdcard/" and "Mount /system/" and then go back and try to fine the ROM.zip file. If you still do not see it, it was not pushed correctly...go back and ensure you were letter for letter with the name and the file path.
- Once the screen in Recovery says "Install from SD Card Complete.", go back to Recovery's main screen yet again and select "Reboot system now" - If your device fails to Install the ROM.zip, I had this happen to me. You must push the CWM SuperSU ZIP (the .zip file is found at the end of this thread)file as outlined before and Install THAT .zip file in Recovery, then reboot Recovery and Install the ROM.zip from SD Card.
- Let your phone have some time to boot up...initial boot from installing a new ROM have histories of taking a couple minutes.
- You should now be on a working SGS2 running whatever ROM you decided to flash.
I hope this HELPED.
Thanks for this information goes out to doktortaru, strker45, and torxx.
Sent from my GT-I9100 using XDA
All that or simply using cwm format system
Thanks to @brwetz for the above quoted info...!
Sent from my GT-I9100 using XDA
sweet thanks guys!
haaha it ws actually all coz didnt format /data... GAH
Thanx for tutorial...

Crap did I brick this?

Please help. I just want to reset to anything that will work. I have access to CWM. I have deleted all backups (I know...) I have WSG Rom and Wooky (which doesnt like CWM) on the internal SD card. I can't stop getting bootloader loops. I have made some mistakes trying to fix this. I just want anything (ADB or whatever) that will get me to a working tablet. I know this is vauge, please help. WHen I flash WSG it goes to the ASUS screen with the circle that keeps flashing as it rotate- not the image below. I have tried reading about fastboot, which I can enter, but I am unsure how to use it.
...
No this is an easy fix after you do a bit of reading! You need to fastboot flash TWRP and then WIPE and then push a rom to your device through adb.
You'll find TWRP in the development section, I'm guessing your on the stock bootloader (not androidroot), if so read back a couple of pages in the thread and you'll find a link to their older versions. On the first post you'll find a link to their website where you'll find instructions to fastboot flash their recovery.
Also in development section you'll find a thread called How To Un-Brick Your Prime. In there you'll find downloads and instructions for both ADB and Fastboot.
Reading a bit through these post you will learn alot and easily unbrick your device now, and the next time your in trouble.
Hope this helps....
I suggest you go here first http://forum.xda-developers.com/show....php?t=1426502 download and install naked drivers
Then go here http://forum.xda-developers.com/show....php?t=1774352 download and unzip nvflash
Then go here http://forum.xda-developers.com/show....php?t=1615990 download twrp and place it inside the nvflashpack directory where you see adb.exe
Then go here http://forum.xda-developers.com/show....php?t=1782413 download EOS 3
or
Go here http://rootzwiki.com/topic/32357-rom...ckbean-2-8-15/ and download bakedbean 3
Put either one in the nvflashpack directory where adb.exe is or if you have an external sdcard, load a rom onto it (preferred method)
I am not a fan of cm10 though it has some nice features I wouldn't start with it...
Now the hard part....
Go here and follow the instructions http://androidroot.mobi/t3_nvflash/
As per the instructions put your prime in fastboot mode...
to you start a command prompt, open the nvflashpack directory where adb.exe is. Press and hold shift while right clicking in the window, select open command prompt here
When the instructions say to enter a command, highlight it on the webpage and copy then in your command window right click and paste (control V does not work here)
Work your way all the way to the end until you see coming soon...
In the end you will have the modified bootloader required for the latest version of twrp (cwm doesn't work as well as twrp on the prime)
Now follow the instructions to install twrp this can be done through fastboot or through goo manager (download from market if you want to go the goo manager route)
Once that is complete with the prime still plugged into the pc, boot into twrp, now depending on if you have put the rom on an external sd card or not... if on sdcard, have it inserted before going into twrp, and install the rom from the card otherwise you can adb push the rom to the prime it will be adb push /name of rom.zip/ sdcard Note that the rom has to be in the same directory as adb.exe for this to work otherwise you need to type the path....for the name of the rom I suggest right clicking the file, go to properties and copy the name, then right click and paste in the command window... this eliminates mistakes.. and don't forget the.zip part.. the push will take about 5 minutes...
Then install the rom from twrp.....

Install 4.4 ROM on VZW G2: ALL STEPS?

I am very new to the android world, seeing as I am a recent iOS convert. However, I am still struggling with all the terminology and technicalities of android and require assistance (perhaps a lot! :cyclops.
I have managed to root my G2 (VERIZON MODEL) but am stuck there. I do not know how to install CWM or TWRP, nor install any custom ROMs like CM or Gummy.
So will anyone be kind enough to guide me through the process? Thank you.
P.S.
I have searched through the threads in this forum regarding installing custom ROMs and am still confused.
from this thread here
http://forum.xda-developers.com/showthread.php?t=2449670
first download twrp for your device, http://techerrata.com/file/twrp2/g2vzw/openrecovery-twrp-2.6.3.3-g2vzw.zip
plug the phone to the computer, make sure u have usb debugging on in developer settings of phone
since you are already rooted, place that file recovery img to the IOROOT folder.
once done, rename the recovery file to recovery.img
one done, CONTROL + SHIFT + RIGHT CLICK, OPEN COMMAND PROMPT HERE
then type this
adb push recovery.img /data/local/tmp/recovery.img
adb shell
(IF YOU DONT SEE A # prompt on your phone, type su in the command prompt to get it then allow it on phone. once thats done then contine onto next step blow.)
cd /data/local/tmp
dd if=/data/local/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
adb reboot recovery
once its complet just reboot the phone and you should have twrp installed!
once twrp is installed, you can dl the verizon version of paranoid android here
http://downloads.codefi.re/houstonn/kitkat/G2/PA/vs980/pa_g2-4.0-ALPHA-20131205-vs980.zip
and
http://www.androidfilehost.com/?fid=23252070760973599
dl the file, drag the files to the phone, dont place into any folder though.
to install, go to the ioroot folder again, control shift right click open prompt again, type adb reboot recovery
phone should reboot to recovery, go to settings, then select USE RM-F instead of formatting, then go to wipe, advance, select dalvik cache, system, data, and cache. IMPORTANT DO NOT SELECT INTERNAL STORAGE!!!
then swipe to wipe
then go to install then install the paranoid android download first, once its installed, hit the back button on the botom right, then install the GAPPS, then reboot the device your done.
Or you could just download the recovery.img that u choose, and flash it using the app called "Flashify". Easiest way by far and works perfectly for me everytime, using both TWRP and CWM whenever I need.
Once you have that done, installing a ROM such as GUMMY is fairly simple since it usually has the instructions right there in the OP of the thread. Pretty straightforward.
expertzero1 said:
from this thread here
http://forum.xda-developers.com/showthread.php?t=2449670
first download twrp for your device, http://techerrata.com/file/twrp2/g2vzw/openrecovery-twrp-2.6.3.3-g2vzw.zip
plug the phone to the computer, make sure u have usb debugging on in developer settings of phone
since you are already rooted, place that file recovery img to the IOROOT folder.
once done, rename the recovery file to recovery.img
one done, CONTROL + SHIFT + RIGHT CLICK, OPEN COMMAND PROMPT HERE
then type this
adb push recovery.img /data/local/tmp/recovery.img
adb shell
(IF YOU DONT SEE A # prompt on your phone, type su in the command prompt to get it then allow it on phone. once thats done then contine onto next step blow.)
cd /data/local/tmp
dd if=/data/local/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
adb reboot recovery
once its complet just reboot the phone and you should have twrp installed!
once twrp is installed, you can dl the verizon version of paranoid android here
http://downloads.codefi.re/houstonn/kitkat/G2/PA/vs980/pa_g2-4.0-ALPHA-20131205-vs980.zip
and
http://www.androidfilehost.com/?fid=23252070760973599
dl the file, drag the files to the phone, dont place into any folder though.
to install, go to the ioroot folder again, control shift right click open prompt again, type adb reboot recovery
phone should reboot to recovery, go to settings, then select USE RM-F instead of formatting, then go to wipe, advance, select dalvik cache, system, data, and cache. IMPORTANT DO NOT SELECT INTERNAL STORAGE!!!
then swipe to wipe
then go to install then install the paranoid android download first, once its installed, hit the back button on the botom right, then install the GAPPS, then reboot the device your done.
Click to expand...
Click to collapse
So I take it that I put the "ioroot10" file into my phone over the USB, then extract the files of the TWRP file, then place the extracted TWRP file inside of the ioroot10 file? Also, I did the control+shift+right click, but there is not OPEN COMMAND PROMPT option. Sorry for all the questions..
dlee96 said:
So I take it that I put the "ioroot10" file into my phone over the USB, then extract the files of the TWRP file, then place the extracted TWRP file inside of the ioroot10 file? Also, I did the control+shift+right click, but there is not OPEN COMMAND PROMPT option. Sorry for all the questions..
Click to expand...
Click to collapse
no, you place the recovery.img to the ioroot10 folder, ioroot10 stays on your computer.
control + shift + right click = open command window here
Just use flashify its free n so much easier
the definition of open: “mkdir android ; cd android ; repo init -u git:// android.git.kernel.org/platform/manifest.git ; repo sync ; make" gansta mic drop

WI502Q, how i unbricked my watch! (TWRP Backup included)

Alright, so I screwed up my watch a few days ago and it ended up not getting past the splash screen and going straight to recovery. Thanks to @z0mghii, I was able to get a TWRP backup of the system, boot, and data. I replaced this backup with my own so none of his data (if possible) could be taken advantage of. However, after flashing it, I was still unable to boot up. Here are the steps I took in order to get everything back to working order. Keep in mind this is for WREN, the small version. Some steps may be unnecessary.
1. Boot to TWRP
2. Go to advanced wipe
3. Wipe everything
4. Go to the link below and download the TWRP Backup
5. Create a backup of a small partition (like boot) on your watch to create the folder.
6. Plug watch into PC while in TWRP
7. Go to the watch's internal storage
8. Go to the TWRP folder
9. Go to the subfolder
10. Paste the downloaded backup folder into this folder, this should be with the one you created earlier
11. Restore this backup on your watch, be sure to check all the boxes
12. Reboot to the bootloader
13. Install ADB if you haven't already, I recommend the 15 second one
14. While the watch is in the bootloader and it is plugged in, type the following commands
fastboot erase cache
fastboot erase misc
fastboot reboot
https://drive.google.com/drive/folders/0B_HUnwYIrFskUW10UDZ0dXdHQzg (You might have to download each item and put them in a folder instead, unless I'm oblivious to something, sorry )
After this, your watch should boot up, then power back down, then boot back up again. This will be followed up by the boot animation and go to the welcome screen.
If any of you guys could provide me with the latest stock rom version TWRP backup or a stock recovery.img, it would be greatly appreciated. (Unless June patch is the latest). The recovery would be great no matter what. Getting the stock recovery can be done by typing the following commands into the command prompt on a PC. Hopefully they work. It should be copied onto the /sdcard.
Via adb shell (make sure ADB debugging is on in developer options, then type adb shell in CMD on PC) type: cat/proc/mtd and press enter
You will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
I hope I helped somebody with this. Again, huge thanks to @z0mghii for making this possible. I'm sorry for bad formatting.
I'm really new to this. I'm also by no means a developer/hardcore android person. These commands were all taken from google. I take 0 responsibility for your device being ruined. This is just what worked for me.
Reserved
HOLY CRAP IT WORKED!! You just don't know how much this means to me, words can't express!
cland216 said:
HOLY CRAP IT WORKED!! You just don't know how much this means to me, words can't express!
Click to expand...
Click to collapse
Hell yeah. Glad I could help somebody! I've been wanting to give back to the wonderful XDA community for a while as a long time lurker. Also, I'm hoping to get a newer version of the stock rom and a stock recovery.img so you can go back to 100% factory stock for an OTA. I'm pretty proud of myself (being noobish) figuring this out.
Thanks a lot!! My watch was kept in a drawer because it was useless and it has now returned to life, I just have a problem restoring the recovery, the command to locate the recovery folder do not work me, have any idea how located the recovery folder?
klaudio_tv said:
Thanks a lot!! My watch was kept in a drawer because it was useless and it has now returned to life, I just have a problem restoring the recovery, the command to locate the recovery folder do not work me, have any idea how located the recovery folder?
Click to expand...
Click to collapse
Are you referring to "extracting" the recovery img? You only need to do it if you're running the stock recovery.
If so, I think I have screwed the command. Make sure you're in adb shell (in recovery on the watch) and then type "cat /proc/mtd" (with the space in front of cat) without the quotes in order to locate the recovery partition.
You will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
Hopefully this works
Hi, my watch now works well, but I was not able to install updates, when I try to install updates from the watch, watch reboots and go to TWRP recovery. Anyone knows how install the updates?
klaudio_tv said:
Hi, my watch now works well, but I was not able to install updates, when I try to install updates from the watch, watch reboots and go to TWRP recovery. Anyone knows how install the updates?
Click to expand...
Click to collapse
Since the OP helped me, here's my chance to give back..
By no means do I know what hell I'm doing, but I know enough to be dangerous. If you're ready to live dangerously, follow these steps (which worked for me):
1. Go into TWRP on the watch and connect it usb to your computer. Using TWRP file manager, copy the update.zip from CACHE to sdcard\Download.
2. On the computer, browse to Zenwatch internal memory Downloads folder and copy the update.zip file to your computer.
3. Unzip the file on your computer using 7zip.
4. Navigate to \META-INF\com\google\android\ and look for updater-script.
5. Edit updater-script in Notepad++.
6. Delete the lines starting with getprop. This turned out to be lines 2 thru 5.
7. Delete the lines starting with apply_patch_check. This turned out to be lines 10 thru 176
8. Save changes to updater-script then in Windows Explorer highlight all of the files and folders that you unzipped, right-click them and click on 7zip --> Add to update.zip
9. Copy the new update.zip to the Zenwatch internal memory, Downloads folder, overwriting the original update.zip
10. Flash the update.zip file with TWRP.
11. Reboot TWRP to Bootloader.
12. On your computer, goto adb folder where you have fastboot files, and using command prompt type:
fastboot erase cache
fastboot erase misc
fastboot reboot
These steps worked as I was stuck on the June 1, 2016 Android security patch on my Wren Zenwatch. These steps helped me get to the September 1, 2016 security patch.
I managed to update my watch to the September 1 security patch using Cland216's method. But I am unable to update further using the method above. Does anyone have any info on how to update further? Or has any zip files to flash?
If we could get someone to upload the watches stock recovery that would solve all issues.....Why has noone done this for this model yet?
Sent from my OnePlus X using XDA Labs
I'm unable to create a backup file
5. Create a backup of a small partition (like boot) on your watch to create the folder.
6. Plug watch into PC while in TWRP
TWRP :
Could not mount /data
When I try to mount /data , I unable to /data
HOLY ****
Dude.. Let me just say...
YOU ARE THE ****ING ABSOLUTE BEST.
I am now going to make a backup, and save it to my computer, google drive, dropbox, icloud, and every other ****in place I can to make sure this never happens again. Thank you!!!!
Nicholas6706 said:
Alright, so I screwed up my watch a few days ago and it ended up not getting past the splash screen and going straight to recovery. Thanks to @z0mghii, I was able to get a TWRP backup of the system, boot, and data. I replaced this backup with my own so none of his data (if possible) could be taken advantage of. However, after flashing it, I was still unable to boot up. Here are the steps I took in order to get everything back to working order. Keep in mind this is for WREN, the small version. Some steps may be unnecessary.
1. Boot to TWRP
2. Go to advanced wipe
3. Wipe everything
4. Go to the link below and download the TWRP Backup
5. Create a backup of a small partition (like boot) on your watch to create the folder.
6. Plug watch into PC while in TWRP
7. Go to the watch's internal storage
8. Go to the TWRP folder
9. Go to the subfolder
10. Paste the downloaded backup folder into this folder, this should be with the one you created earlier
11. Restore this backup on your watch, be sure to check all the boxes
12. Reboot to the bootloader
13. Install ADB if you haven't already, I recommend the 15 second one
14. While the watch is in the bootloader and it is plugged in, type the following commands
fastboot erase cache
fastboot erase misc
fastboot reboot
https://drive.google.com/drive/folders/0B_HUnwYIrFskUW10UDZ0dXdHQzg (You might have to download each item and put them in a folder instead, unless I'm oblivious to something, sorry )
After this, your watch should boot up, then power back down, then boot back up again. This will be followed up by the boot animation and go to the welcome screen.
If any of you guys could provide me with the latest stock rom version TWRP backup or a stock recovery.img, it would be greatly appreciated. (Unless June patch is the latest). The recovery would be great no matter what. Getting the stock recovery can be done by typing the following commands into the command prompt on a PC. Hopefully they work. It should be copied onto the /sdcard.
Via adb shell (make sure ADB debugging is on in developer options, then type adb shell in CMD on PC) type: cat/proc/mtd and press enter
You will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
I hope I helped somebody with this. Again, huge thanks to @z0mghii for making this possible. I'm sorry for bad formatting.
I'm really new to this. I'm also by no means a developer/hardcore android person. These commands were all taken from google. I take 0 responsibility for your device being ruined. This is just what worked for me.
Click to expand...
Click to collapse
I spoke just a bit too soon, now it is hanging on that animation with the 4 dots. Any suggestions?
NEVERMIND, I AM UP AND RUNNING!! WOOHOOOO

[RECOVERY][UNOFFICIAL] TWRP 3.2.1-0 for Mate 20 X aka Everest (EVR-AL00/EVR-L29)

Below you'll find an unofficial semi-bootleg version of TWRP for the Mate 20 X. I say bootleg because I took @Pretoriano80's P10 lite build and modified it for our devices.
Credits: teamwin, @Pretoriano80, @ante0
Testers: @cflynt
Download: Download TWRP for Mate 20 X
Installation guide:
Welcome to the TWRP installation guide for the Mate 20 X. Keep in mind that installing this REQUIRES you to format your data and remove encryption in order for TWRP to read your /data partition and be able to create backups, so backing up your internal storage is recommended if you want to keep anything from it. This will factory reset your device as well.
Flashing TWRP to the eRecovery ramdisk partition is recommended as it allows you to have both Magisk root and TWRP simultaneously. Otherwise, you can flash between Magisk and TWRP when you need it by flashing this image to recovery_ramdisk. This guide will focus on eRecovery installation.
Magisk root and ADB/a terminal app is REQUIRED for the installation of TWRP as fastboot does not allow flashing of erecovery_ramdisk partition.
Backing up your original eRecovery:
The easiest way to accomplish this is to download "partitions backup & restore" from the google play store, and using that app to back up "erecovery_ramdisk." However, you can also accomplish this with adb by running the command "dd if=/dev/block/bootdevice/by-name/erecovery_ramdisk of=/sdcard/erecovery_ramdisk_stock.img" with your device hooked up to a computer. If you are backing up your internal storage, do it after creating this backup. Otherwise, copy this backup to a safe location on your computer.
Booting to TWRP: Booting into TWRP requires a different button combination.
-Booting to TWRP is as simple as getting to the standard boot splash "corruption" screen. When you see this, it will be followed by instructions to hold volume UP for three seconds. Doing this will boot you into TWRP or eRecovery, depending on which one you have installed. With the phone connected to a power source, USB or AC, reboot/boot the phone holding volume UP. Once the standard corruption screen is displayed, release and hold the volume UP key again.
Booting to Magisk root:
-Booting to Magisk root requires the same volume UP key combination, but the phone must NOT be connected to a power source (USB or AC), OR you must use the "adb reboot recovery" command. Reboot/boot the device holding volume UP. This will display the standart boot splash "corruption" screen but will NOT show the standard instructions for booting into eRecovery. It will simply show a "your device is booting" message under the "corruption" message.
Booting to Magisk root from TWRP: the Reboot>Recovery option in TWRP does NOT reboot the device back into TWRP. This is used to boot Magisk root.
-From TWRP, tap the Reboot button followed by Recovery. Normally, the device would boot back into TWRP, but since TWRP is installed to the eRecovery partition and Magisk is installed to the normal recovery partition, it reboots to Magisk root instead.
Booting back into TWRP from TWRP: Using the Reboot>System option in TWRP will get you back to the standard corruption boot splash screen where you can use the "Booting into TWRP" instructions above to get back into TWRP.
-From TWRP, tap the Reboot button followed by System. This will reboot the device normally, giving you the standard corruption screen followed by a normal boot WITHOUT Magisk root. Use this option only if you plan on rebooting back into TWRP with the "Booting into TWRP" instructions above. Otherwise, use the Reboot>Recovery option to get you back into a rooted system.
Modifying system from TWRP: This device uses "System as root" file structure, so it's a bit different to modify system from TWRP.
-Go to the mount option in twrp and mount "System_root" From here, you'll need to browse /system_root NOT /system in order to make changes to system.
*******************INSTALLING TWRP TO ERECOVERY*******************
Flashing TWRP to eRecovery ramdisk:
-Hook your phone up to a PC.
Step 1.
Start by copying the TWRP image to your internal storage OR nm card. Rename it to "twrp.img" to make typing the next command easier.
Step 2.
Using ADB or a terminal app, gain SU access and run the following command: "dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/erecovery_ramdisk"
Step 3.
Reboot your phone into TWRP by following the "Booting to TWRP" instructions above.
Step 4.
Once you are in TWRP, you will need to format data, as TWRP cannot read encrypted storage on this device yet. Do this in the "wipe" "Format Data" section of TWRP.
Step 5.
Once data is formatted, copy the fstab.kirin980 file from this package to your internal storage or nm card.
Step 6.
Go to "mount" in twrp, and mount Vendor.
Step 7.
Use TWRP file manager in the "advanced" section of TWRP to copy fstab.kirin980 from your internal storage or nm card to /vendor/etc. This will overwrite the original fstab.kirin980 file and replace it with our modified one removing forced encryption so that the system won't try and re-encrypt your device on boot.
Step 8.
Reboot>Recovery to get back into a rooted system, which is now factory resetted.
DO NOT USE ANY OF THE TWRP SUGGESTIONS TO INSTALL ROOT TO YOUR SYSTEM. Disable the notice to install root by going into TWRP settings and unchecking the relevant box.
Great work! @freeza
Can you expand on step 2...
"Using ADB or a terminal app, gain SU access..."
How does one "gain" SU access? Opening a terminal app on the phone and entering SU in command prompt comes back with permission denied even though I am booted under the previous root method.
n1tro said:
Can you expand on step 2...
"Using ADB or a terminal app, gain SU access..."
How does one "gain" SU access? Opening a terminal app on the phone and entering SU in command prompt comes back with permission denied even though I am booted under the previous root method.
Click to expand...
Click to collapse
Are you sure you're booted with magisk root? If so, open the magisk manager and go to > superuser and make sure shell is allowed for root. If you're using a terminal app, then make sure that's allowed.
Sent from my EVR-AL00 using Tapatalk
freeza said:
Are you sure you're booted with magisk root? If so, open the magisk manager and go to > superuser and make sure shell is allowed for root. If you're using a terminal app, then make sure that's allowed.
Sent from my EVR-AL00 using Tapatalk
Click to expand...
Click to collapse
Took a few tries typing in SU before it triggered the Magisk Grant Permission prompt to come up. I granted permission. But entering in the command gives me a permission denied.
Attached screenshot
Magisk permission
n1tro said:
Attached screenshot
Click to expand...
Click to collapse
You want to use app launcher in phone manager or battery settings to turn off emui optimization of magisk manager so it'll be allowed to run in the background to prompt for su. Also try entering just su in the terminal first to get the # prompt instead of $, then enter the dd command
Sent from my EVR-AL00 using Tapatalk
freeza said:
You want to use app launcher in phone manager or battery settings to turn off emui optimization of magisk manager so it'll be allowed to run in the background to prompt for su. Also try entering just su in the terminal first to get the # prompt instead of $, then enter the dd command
Sent from my EVR-AL00 using Tapatalk
Click to expand...
Click to collapse
Seems not all terminal apps are created equal. Even with permissions enabled, issuing the SU command did bring it to a # prompt but kept it at $.
Downloaded and installed Material Terminal from the playstore and it works.
n1tro said:
Seems not all terminal apps are created equal. Even with permissions enabled, issuing the SU command did bring it to a # prompt but kept it at $.
Downloaded and installed Material Terminal from the playstore and it works.
Click to expand...
Click to collapse
Glad you got it sorted [emoji16]
Sent from my EVR-AL00 using Tapatalk
freeza said:
Glad you got it sorted [emoji16]
Sent from my EVR-AL00 using Tapatalk
Click to expand...
Click to collapse
1 problem cleared, another one starts.
I followed the instructions wiping the data and copying the 1 file over under the vendor directory. Phone boots up in setup menu. I go through everything (skipping setting up wifi) and when I finish selecting to use gestures or nav buttons, the phone goes back to the beginning of the setup screen.
Guess, I will try to wipe everything and load the custom rom you guys made
n1tro said:
1 problem cleared, another one starts.
I followed the instructions wiping the data and copying the 1 file over under the vendor directory. Phone boots up in setup menu. I go through everything (skipping setting up wifi) and when I finish selecting to use gestures or nav buttons, the phone goes back to the beginning of the setup screen.
Guess, I will try to wipe everything and load the custom rom you guys made
Click to expand...
Click to collapse
When you wiped data, did you do it from the WIPE screen in TWRP and select Format Data? Should prompt you to type in YES when you do so. Otherwise if you are doing an ADVANCED WIPE it is only formatting data without the Media part. YOU MUST get this part right and then copy over that new fstab.kirin980 file using the TWRP File Manager. If you didn't get this right then your Data Partition will still be encrypted.
Hope that helps.
Chad
cflynt said:
When you wiped data, did you do it from the WIPE screen in TWRP and select Format Data? Should prompt you to type in YES when you do so. Otherwise if you are doing an ADVANCED WIPE it is only formatting data without the Media part. YOU MUST get this part right and then copy over that new fstab.kirin980 file using the TWRP File Manager. If you didn't get this right then your Data Partition will still be encrypted.
Hope that helps.
Chad
Click to expand...
Click to collapse
I wiped the data from the main screen and got a prompt to type YES to continue. I think the setup screen loop issue is coming from all the Huawei stuff I got rid of using the adb procedure in the other thread. Maybe I got rid of some 1st time setup file. In any rate, I got the custom ROM you guys made and installed it and everything works again.
O
n1tro said:
Attached screenshot
Click to expand...
Click to collapse
What is your dpi?? lmao
antiochasylum said:
O
What is your dpi?? lmao
Click to expand...
Click to collapse
340.
I normally have it at 320 but noticed I was making more mistakes on the shrunken keyboard.
n1tro said:
340.
I normally have it at 320 but noticed I was making more mistakes on the shrunken keyboard.
Click to expand...
Click to collapse
How did your set it? The typical lcd_density didn't trigger anything for me.
antiochasylum said:
How did your set it? The typical lcd_density didn't trigger anything for me.
Click to expand...
Click to collapse
It's in a messed up location. Go and edit the local.prop file located in /product/etc/prop pathway. That's the only thing that needs to be set. All the other files and locations are red herrings.
Guys, maybe this is a dumb question... but can i Flash SuperSU directly from the TWRP ?
filip_pine said:
Guys, maybe this is a dumb question... but can i Flash SuperSU directly from the TWRP ?
Click to expand...
Click to collapse
SuperSU is more suited for older phones and no longer being worked on so no more updates/support? https://www.androidpolice.com/2018/0...p-development/ it's also been removed from Play Store.
Magisk is used for root now https://www.xda-developers.com/magisk-vs-supersu/ and there is a thread how to install here
How can I update software?
Now 185, but 195 comming.

Categories

Resources