Wat steps to root and install Viper (international HTC One X+) - HTC One X+

Hope somebody can help me with this. I want to root my HTC One X + (with the all in one root kit 2.3) and put the rom ViperX+ 1.0.3 on it. Can somebody confrim that the steps below are the right ones.
With all in one root kit V2.3.
1.install HTC Drivers
2.register at HTCdev
3.Get Token ID
4. Submit Token ID
5.Unlock bootloader
So far everything goes oke. But for the below steps I need help.
- Is this the moment to make a backup by creating a CWM image?
After that
- Do i need to Flash recovery TWRP International with the all in one root kit v2.3 or is it better to flash Venom mod of TWRP recovery with Venom Flasher?
- flash Elite kernel repacked (boot.img) for Viper with Venom Flasher (or is it better to flash it with the all in one tool kit)
- Boot in recovery (vol down + power)
- Full wipe
- Install Viper rom (zipfile)
-Reboot phone
Hope you guys can help me with this. Thanks!

a bit searching would have led you to this thread: http://forum.xda-developers.com/showthread.php?t=2066390
at all, your steps are nearly fine: but at first you need a custom Recovery for creating any Backup (CWM Backup does just work with CWM recovery - at all those backups are generally referred as "nandroid"-Backups. But backups created with CWM are not compatible with TWRP and TWRP-Backups are not compatible with CWM)
For Viper ROM, the Viper modded TWRP is recommended, and the VenomFlasher tool is more easy than AIO-Toolkit for flashing Recovery (Venom modded TWRP 2.4.1.0) and Kernel
So do:
6. put ViperROM on your sdcard
7. flash recovery with Venom Flasher (in fastboot mode*)
8. boot into recovery, make backup (system, data and kernel, so you have your original kernel in case of ... you need to go back to stock)
9. flash kernel (in fastboot mode*)
10. go into recovery, do full wipe, and flash your ROM
Done.
* if you aren't in fastboot mode, Venom Flasher will take you there, so you just need your device switched on and connected to your computer with USB debugging activated in the developer options.

Related

[P769] [UL BL] [CWM] [TWRP] [Philz] Recoveries for P769 - No More Mirror Issues

UNLOCKED BOOTLOADER REQUIRED FOR BELOW RECOVERIES
ClockworkMod​
Downloads:
6.0.4.5
CWM 6.0.4.5 Touch for P769
6.0.4.8
CWM 6.0.4.8 No-Touch for P769
Philz Advanced CWM​
Downloads:
6.40.0
Philz CWM 6.40.0 - Based on CWM 6.0.4.8 for P769
TWRP​
Downloads:
2.7.1.1
TWRP 2.7.1.1 for P769
Information
Questions:
- What is the difference between normal recovery and these recoveries?
If you install a normal CWM/TWRP/Philz release on an unlocked P769, you will notice that the screen is inverted/mirrored and/or the the touch is also wonky. The above uploaded recoveries have been especially adapted to work correctly, so there is no-more mirror issue and the touch works fine as well. After flashing the below fix too, the touch should work while on your ROM as well.
Please note, you may have to also flash this fix (cwm_ts_fix_p769) for the wonky touchscreen after flashing the recovery. Get it here
- How to install recovery?
Option 1:
a. Go to recovery and flash the zip
Option 2:
a. Extract the recovery.img file from the zip and copy to your internal/external SD card on phone
b. Install Rashr from here
c. Flash the recovery from within the application by browsing for it
Option 3:
a. Extract the recovery.img file from the zip and copy to your computer
b. Use fastboot to install recovery, see here
c. Use the command "fastboot flash recovery recovery.img"
Option 4:
a. Via flash_image, use this guide.
- Are these recoveries bug-free?
I have tested all the recoveries on my device (T-Mobile P769) and it does boot into them and you can flash zip files, I can't comment on functionality more than that, however if there is an issue with these recoveries then it is most likely an issue with the original recovery as well.
- How are these recoveries created?
These recoveries are created simply by using kuma82's method, described here, which is replacing the kernel (zimage) from the original recoveries and replacing with the kernal from bobZhome's CWM recovery .
- Will you keep updating the recoveries?
I will try my best, I do not compile the recoveries from the original sources, because I don't have the time or know how to, however if there is a new recovery release and required by the users, I will gladly mod it and upload it.
Thanks to:
- @artit for his TWRP
- @artas182x for his CWM 6.0.3.7 and 2nd-init
- @dhiru1602 for his device tree
- @Polloos for his compiled recoveries
- @kuma82 for his guidance on unlocking and making these recoveries
- @BobZhome for creating the CWM recovery, from which the kernel(zimage) was extracted
- Philz, TWRP, CWM for their excellent work and awesome recoveries.
Please inform people that their bootloader must be unlocked to flash these and thanks for 2.7 twrp.
Thanks, I forgot to add that. Done.

Issues with no working recovery.

Ok long story short i'm confused as to what's up with this device. I just picked it up and started messing with it. Looks like it has mako bootloader unlock and cwm 6x recovery installed. The only roms it can flash is cm12.1 and the factory ATT images correctly. I tried to update to the newer version of CWM or TWRP via fastboot and the flash takes but no recovery is present. Things i've tried =
Full factory reset via LGE970AT-01-V20j-310-410-MAR-08-2013 (this leaves me with no bootloader/fastboot/recovery) It boots but black screen on bootanimation.
tinybin (both options) only the altern will boot but. (have fastboot but no recovery.)
So long story... In stock firmware I can install freegee and unlock via mako but there will be no recovery if I choose TWRP and CWM won't install anything bt CM... I'm attempting to install Blisspop btw.
Any help would be great. Thank you

Sony Z2 Help

Im new into rooting so i succesfully unlocked my bootloader and installed the twrp recovery via flash now i have the problem that my phone always boots into the recovery mode no matter what, i have a sonyz2 D6503 andriod 6.0.1 i follow a tutorial on youtube . now i have read a few threads that it is wrong to install twrp with fastboot flash boot C/:whaterver.img i should have done it with fastboot flash recovery C/:whatever.img . Im kinda stuck now and i have no idea what to do moreover im kinda scared to do something, because it can cause more damage that i already have.
im kinda sorry for my horrible english i hope you can understanf this trouble
If you want to proceed back to stock ROM, flash stock FTF using flashtool (download link and instructions can be found inside my signature), with KERNEL and SYSTEM checked, other leave other options intact.
If you want to flash another non-stock ROM, flash an advanced kernel via fastboot toolbox inside the flashtool I mentioned above, then you can flash the ROM using the TWRP inscribed with the advanced kernel.
If you want to proceed to stock ROM but rooted and with other MODs installed, there are two ways to do so:
Easier method:
Flash an advanced kernel then use the pre-installed TWRP to flash the SuperSU.zip or whatever MOD zips.
Complex method:
Restore stock kernel using flashtool mentioned above, then flash the TWRP (recovery) image (you can get one HERE) using a cmd on PC or Laptop with ADB and flastboot drivers installed, typein:
Code:
fastboot flash recovery <recovery>.IMG
then you can boot into the TWRP to flash whatever MODs you want.
--------------------
As always, do more research before entering into tweaking things, noobness can be fatal!

Clockwork Mod or TWRP which one EASY ?

I dont want MIUI and useless extra app so i have to install custom rom.
First step is unlock bootlader with mi unlock app okay. But my question is how can i install custom rom ?
TWRP or Clockwork Mod ???
Using TWRP i have to install it first after that i have to install recovery.img and lazyflasher unless my phone gonna brick and its too complicated.
What about Clockwork Mod ?? is it different method ?
I guess i found my path.
1)Installing ROM MANAGER from Play Store of course with rooted device.
2)Install inside of app Clockwork Mod
3)Select custom rom from SD Card and select Gapps,backup,wipe data...
and device gonna reboot do everything automatic is that true and simple ?
My question is using rom manager and install custom rom like that or i have to something extra.
Sorry about my english...
I don't have the phone yet, but i had redmi note 3 before and installing twrp was simply putting it in fastboot mode and using adb command "Flash recovery xxxxx.img" and you are set, considering you have an unlocked bootloader that is. then you follow the installing instructions given by the developer, usually (flash rom.zip followed by gapps.zip). But ofcourse i don't have the phone so take what i said as a refernce only and wait for someone else' reply. as of clockwork recovery, i think twrp is easier to use but there is generally no major diffrence.
Forgot Clockworkmod even existed. Have been using TWRP for ages.
cwm has reached end of support.
https://forum.xda-developers.com/showthread.php?t=2201860
use twrp
CWM is dead, twrp is one and only option otherwise there is also Red wolf recovery available.
Steps to install a custom Rom.
Unlock bootloader
Flash TWRP
Flash lazyflasher.zip, reboot
Now DL any Rom.zip and desired Gapps package
Boot into TWRP again
Backup (just incase)
wipe > advanced wipe > wipe everything except internal / SD card
Flash firmware.zip, if you're coming from marshmallow based Miui
Flash Rom.zip followed by Gapps
?? ¿
Profit

*Urgent* Need clarifications regarding the flashing of TWRP recovery & custom ROMs

*Urgent* Need clarifications regarding the flashing of TWRP recovery & custom ROMs
I want to flash a custom ROM (Pixel Experience Plus) on my Poco/Pocophone F1.
It would be of great help if I get clarifications regarding the following:
1. After unlocking the bootloader, is it necessary to flash TWRP recovery using 'fastboot flash recovery' cmd command, to flash a custom ROM? Or can TWRP recovery just be booted by using the 'fastboot boot' cmd command & then flash the ROM? (This is because I'd prefer to flash a custom ROM without permanently flashing TWRP recovery, I want TWRP temporarily)
2. In case if it's necessary to flash TWRP using 'fastboot flash recovery' cmd command, then do I have to flash DFE (Disable Force Encryption). Can I skip flashing DFE? (Because I don't want to flash DFE & want TWRP temporarily)
3. I want a clean install of the custom ROM. So, can I wipe Dalvilk/ART cache, Data, System, Cache, Internal Storage, SDCard? i.e. everything except, USBOTG (Because, the custom ROM & firmware ZIP files are stored in it & I'll flash them from USB OTG device).
Would this type of wiping affect the TWRP recovery?
4. After wiping everything except USBOTG, can the custom ROM & firmware ZIP files be transferred into the phone's internal storage by connecting it to the PC, while in TWRP recovery?
5. Is it safe to flash the ZIP files from a USB OTG device?
6. As I already mentioned that I want TWRP temporarily (If it's possible). After flashing the firmware & custom ROM. If the recovery is still a stock Mi recovery. Would it affect the functioning of the custom ROM in any way?
If all of the above can be done, is this one of the proper way to flash/boot TWRP recovery & flash a custom ROM? If not, please guide me accordingly.
imegsp said:
I want to flash a custom ROM (Pixel Experience Plus) on my Poco/Pocophone F1.
It would be of great help if I get clarifications regarding the following:.
Click to expand...
Click to collapse
i'm no expert and i'm fairly new to flashing if you're kind enough to read it here's my 2cents.
1) I believe it is necessary to flash with that command & have TWRP as your custom recovery , it is packed with powerful tools. so i don't see a problem not wanting it permanently and it saves you the hassle of flashing it again when changing roms , fixes,etc..
2) Yes , you need to flash the DFE so you won't encounter any errors in TWRP later.
3) " Dalvilk/ART cache, Data, System, Cache " this should be okay , no need to flash everything. for best practices do a factory wipe in TWRP and in advanced mode wipe those 4. make sure to create a backup in-case something goes wrong.
4) I haven't tried this yet , but it seems not doable as you need permission in the phone for the default USB connection toggle if it's in data transfer mode , usb debuggin , charging etc. best is boot your phone then do the transfer in file manager.
5) Yes it is safe since OTG is another form of External Data devices such as SD Card , etc.
6) No it wouldn't affect the rom functionality since rom and recovery is two different thing.. but still , to avoide future mishaps stick with TWRP
you can check this helpful link by madsponge26 : https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
imegsp said:
I want to flash a custom ROM (Pixel Experience Plus) on my Poco/Pocophone F1.
It would be of great help if I get clarifications regarding the following:
1. After unlocking the bootloader, is it necessary to flash TWRP recovery using 'fastboot flash recovery' cmd command, to flash a custom ROM? Or can TWRP recovery just be booted by using the 'fastboot boot' cmd command & then flash the ROM? (This is because I'd prefer to flash a custom ROM without permanently flashing TWRP recovery, I want TWRP temporarily)
2. In case if it's necessary to flash TWRP using 'fastboot flash recovery' cmd command, then do I have to flash DFE (Disable Force Encryption). Can I skip flashing DFE? (Because I don't want to flash DFE & want TWRP temporarily)
3. I want a clean install of the custom ROM. So, can I wipe Dalvilk/ART cache, Data, System, Cache, Internal Storage, SDCard? i.e. everything except, USBOTG (Because, the custom ROM & firmware ZIP files are stored in it & I'll flash them from USB OTG device).
Would this type of wiping affect the TWRP recovery?
4. After wiping everything except USBOTG, can the custom ROM & firmware ZIP files be transferred into the phone's internal storage by connecting it to the PC, while in TWRP recovery?
5. Is it safe to flash the ZIP files from a USB OTG device?
6. As I already mentioned that I want TWRP temporarily (If it's possible). After flashing the firmware & custom ROM. If the recovery is still a stock Mi recovery. Would it affect the functioning of the custom ROM in any way?
If all of the above can be done, is this one of the proper way to flash/boot TWRP recovery & flash a custom ROM? If not, please guide me accordingly.
Click to expand...
Click to collapse
1. if you always want to depend on PC to trigger your Poco in to recovery then use command "fastboot boot recovery.img", otherwise lets say you are on the move and got pixel update! you can simply download it , and flash it in 15 mins on the go , so mainly its upto you . from security point of view, yes its not good to have twrp flashedi n your /recovery , anyone can boot and do harm! , so its a judgement call for you...
2. again upto you, DFE wont interfere/confilt with either rom or twrp
3. android device have various paritition wiping "/system" & "/data" (user setting and apps & appdata) is ENOUGH and called CLEAN FLASHING in various threads of custom roms. you don't have to wipe internal storage!!! you will lose you data... BUT YES if you get encryption error then you must click "FORMAT DATA" button on twrp in order to make storage usable/accessable to twrp. this FORMAT DATA will format your /data /system and /internalStorage partitions and you will delete all your data! then you can flash custom rom of your choice from scratch
4. you don't get access of TWRP FILEMANAGER via fastboot commands from pc, BUT you can do similar by enableing TWRP SIDELOAD option under settings, this adb sideload is a mode listening for new incoming file to flash! if you side load pixelrom.zip from fastboot command while your twrp has active sideload waiting, fastboot will start sending the file and twrp will wait and as soon as the transmit is completed! the file will automatically be flashed!. ,
however you can put files in usbotg drive or combo drive and using file manager in twrp move files from HERE to THERE!
5. I always do it!, but make sure the connection is not faulty!!! otherwise high chances of incomplete flashing and I lost my redmi3i due to impcomplete flashing of stable rom! (bricked)
6. no it wont affect! infact you can even keep the /recovery partition blank! ( fastboot erase recovery).
for MIUI FLASHING/ROOTING / Disabling force encryption etc , this post is king
https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
I am on HAVOC2.8 and this is how i did it
1. flashed TWRP 3.3.1 unofficial (download it from HERE ) ref Reference - as official twrp has TOUCH driver issues. this one worked with me very well
2. I wiped /data, /system then
3. flashed VENDOR.zip from HERE
4. FLASHED CUSTOM ROM (i use HAVOC2.8)
5. FLASHED DFE HERE - REFERENCE
6. FLASHED GOOGLE APPS ( GAPPS.ORG) ( ARM64>9.0MicroPackage)
7. Flash Optimus Drunk Kernel ( OPTIONAL- havoc uses shadow kernel , i feel OD kernel is better, battery and 4g connectivity)
8. FLASHING MAGISK19.3
9. when i was on havoc2.7, by using MIGRATE, it made flashable zip of my APPS+DATA, stored in internalStorage, and now I will FLASH that file., Mine size goes to 2gb you can get it from HERE
10. WIPE CACHE/DELVIK
11. REBOOT
fire reboot may go in to bootloop and then second reboot may take a while and finally you should see Pixel Setup asking google accounts and info etc
once after you finish setup! don't RESTORE APPS from PLAYSTORE, (download only license apk, in my case I have purchases many apps from playstore and saperate license info is always appear in intial setup! SELECT THOSE ONLY)
ONCE playstore is DONE downloading all your selected (fewer) apps, and MAGISK ROOT is working...... put device on AIRPLANE MODE
FROM DROP DOWN Notification panel, CLICK MIGRATE, and it will prompt you what do you wana restore from your previouce ROM to newly flashed HAVOC ..APPS+SETTINGS+PERMISSION+DATA etc - migrate restoration may take upto 30 mins,
once done, uninstall from system and reboot device!
REMEMBER I DONOT RECOMEND MIGRATE TRICK FOR WHATSAPP, it doesn't work properly and NOTIFICATION ISSUES with BLANK DP observed by me whenever I forcely re-instated whatsapp by migrate!

Categories

Resources