I've been examining CSC's with a hex editor an they seem to be some kind of *.nb0 imagefile containing a RAW filesystem with a *.CAB inside that contains a *.rgu and an a *.reg with the custom settings fot the zone/operator code (XEN, XEC, etc.). I tried to hexedit it but I can't calcule the md5 checksum, it seems to be located at the bottom header of the file but doesn't match with any of file's sections or the whole rest of the binary before the checksum code. Anyone could upload AnDim's new HTCRIE (the one with OMNIA 7 support) to see if it helps editing this kind of *.nb0 ??
Edit: HCTRIE has a fixed method for *.nb0 reading that is only compatible with *.nb0 files containing typical partitions (ULDR, SLDR ,etc) and also is not capable of writting changes so there is no way to create custom csc's for now. I will be investigating for more ways to calculate the image checksum.
Only for development purposes:
Download Hashcheck-less* firmware flasher
*The actual checking is done but it allways says that the firmware's md5 matches the binary header and allows you to flash. I still have to change the code so it shows the error message but allows you to continue.
MD5 chechsum is not the main problem
I uploaded Andim's tools here: http://forum.xda-developers.com/showthread.php?t=1117513.
Any information on the flash-tool is very welcome. But, as xbores already stated, the MD5 is not the main problem. If you manage to create a file that will be accepted by the flash-tool, then there is another problem. The rom-files are signed as "WP7_PRODUCT". The bootloader checks this. If the signature is not valid (which happens when the file is tampered with), the bootloader will probably refuse to boot. So you would also need a patched bootloader. I have no idea how difficult that is. I would assume it isn't to hard to do. But if that were true, then probably other people would already have done it already.
If we have a patched bootloader that accepts cooked roms, and a patched flash-tool or correct checksum calculation, so we can actually flash the cooked rom, that would open up a lot of possibilities. I don't have time to spend to on this, but maybe in the future I will have a look at it. Any info is very appreciated.
Patching the tool would be so easy as I have located the code section where it decides to show md5 hash error or continue with the flash process. It would just require to replace a "jz" instruction by "jmp" one in the code with a hex editor.
It would be thankful that those who downloaded the Hascheck-less flasher reported if it was useful for something...
The absolute hash that checks the flash tool is simple MD5, just depends on from where to where (probably from beginning to the last few bytes except the WP_PRODUCT and the md5 hash itself?).
The main problem is the data between 64h and 8000h - they are signature. I am trying to figure out how is it signed, but it is all weird.
In case of CSC, it seems like it is 1byte per ~512B.
In case of eboot, it is 1byte per ~1024B.
In case of PDA, it is 1byte per ~25kB.
Anyone knows anything about Ra000FF and signing it?
I'm not so sure that it is a signature, if you compare different csc's you find repeating parts in it. And that is IMHO not very typical for signatures.
Is there a thread anywhere describing Ra000FF? I already found file size(without MD5 at the end), size of signature what ever thingy and size of eboot image + entry point.
I did a bit of research and I think I have most (pretty much all?) parts of it. When I get home, I will post my findings.
Code:
Ra000FF container
HEADER:
Offset Length [B] Encoding Description
00 8 Big Endian Ra000FF\x0B
08 2 ?? -- "imagestart" (D000FF)
0C 2 ?? -- "imageend" (D000FF)
11 1 Always 24
15 1 Always 01
18 2 Always 04 80
1D 2 Little Endian Sector size (IMGFS, imageupdate = 808; CSC, eboot = 80)
1F 4 Little Endian File content size in sectors: content size = (value*sector size - (8000 + 13F)) (beginning and ending headers)
The content starts at offset 8000
FOOTER (last 13F bytes)
00 1 Always 7E
04 1 Content type (CSC = A9, EBOOT=C7, IMAGEUPDATE=B8, PDA (IMGFS)=B8, PHONE (Radio)=D6)
05 - 11B In case of PHONE -- some unknown data (another hashes? Some XORs?), in other cases always filled with 00s
11C - 127 Target device type (WP7_PRODUCT or WP7_ENGINEER)
12C - 13B 10 Hash of (whole?) file - probably MD5 (10 bytes)
13C 1 Always 7D
13D - 13F 3 Filled with 00s
ALL NUMBERS ARE IN HEX!
OndraSter said:
The absolute hash that checks the flash tool is simple MD5, just depends on from where to where (probably from beginning to the last few bytes except the WP_PRODUCT and the md5 hash itself?).
Click to expand...
Click to collapse
I have tried the md5 from diferent sections and it doesn't work anyway the goal here is to edit the *.cab.pkg as the md5 checksum check can be bypassed with my patched tool (tested changing random bits inside the imgfs). The *.cab.pkg with header MSCF and ending with an FF heap till the end of the IMGFS is signed with the same certificate as the *.dsm inside it (both can be extracted). As the *.cab.pkg is loaded by the the kernel and not by the bootloader the signature could be meaningless here if the *.cab.pkg inside the IMGFS is properly edited. Considering the FF heap as remaining space we could even add more registry tweaks that would also be loaded at first boot.
Also this is the full set of image signature types:
WP7_ENGINEER_4K
WP7_ENGINEER
WP7_PRODUCT_4K
WP7_PRODUCT
ROISSY_ENGI_4K
ROISSY_ENGI
ROISSY_PROD_4K
ROISSY_PROD
Isn't the CSC file checked when uploading to phone for the certificate signature (RSA MD5, RSA SHA1? Who knows - I don't) in the beginning of the file (from offet 0x64) too?
OndraSter said:
Isn't the CSC file checked when uploading to phone for the certificate signature (RSA MD5, RSA SHA1? Who knows - I don't) in the beginning of the file (from offet 0x64) too?
Click to expand...
Click to collapse
My patched tool ignores md5. It was as simple as changing a jz instruction by a jmp and now no matter if the md5 checksum is correct or not it allways says it's ok (even trough the checking routine is done md5 ok => md5 ok and md5 wrong => md5 ok). About the top header binary sections I don't know but for sure my patched tool allows you to flash images with incorrect md5 checksum.
Yes, but try really flashing some device with not proper signature at offset $64 and down.
I talked with Olipro and this should be similar to R000FF - these data are signed with RSA MD5, every block in file. When data block is sent to phone, it is checked against that ^ and if it is okay, the data is written to NAND. I am not talking about the bottom, I am talking about the top.
This is my first android, and would like to make a safety net before I delve heavily into this. I am trying to use Flash Tool (v0.9.13.0) to bundle my blob_fs files that I had recently collected from Sony PC Companion to make a stock ROM, once I finish the decryption process it prompts me as usual to input Build, Brand, add .sin files, and so on. I wait for about 30 mins, the logs remains the same (did this x3, even after re-installed and restarted comp. Please see below for reference).
29/027/2013 18:27:22 - INFO - Decrypting FILE_279914849
29/027/2013 18:27:22 - INFO - Decrypting FILE_280274462
29/027/2013 18:27:25 - INFO - Decrypting FILE_280274482
29/031/2013 18:31:54 - INFO - Decryption finished
=This is the end of my log=
I know it should inform me once the bundle has completed, but doesn't; I look in my C:\Flashtool\firmwares folder and I see that I have a X10_V1_BLRelock.ftf which is 3.3mb, compared to my blob_FS 885mb. Is this correct? Please point me to the right direction.
My Device:
Xperia Z1 - (aU/KDDI - Black)
Model No.: SOL23
Android Version: 4.2.2
Baseband Version: 8974-AAAAANAQZ-10270011-02
Kernel Version: 3.4.0-perf-g66807d4-024510-g22b4297
Build No: 14.1.C.0.467
[RECOVERY] TWRP 2.8.0.3 Touch Recovery
The most up to date TWRP available for the M7SPR, with enhancements others are now migrating to their repos / phones (battery feedback, performance, etc.).
--------------------------
With permission graciously granted by the venerable @Dees_Troy I am opening this thread for further developing and maintaining the TeamWin Recovery Project (TWRP or TWRP2) for the Sprint HTC One (m7wls) device.
Want to Donate to me?
Cool! Not required, but I certainly appreciate all donations. I do risk my phone with every build I test, so some backup bucks for a dev phone (or even a dev phone if you have one to send) would be great. To donate, click my Donate button or just Go Here.
** General Description and Use **
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel. For more details, look to @Dees_Troy's original description.
Why the new thread? Because TWRP2 is now as up to date for Sprint HTC Ones (m7wls) as any other device. Indeed the issues so many have complained about regarding the first release of the recovery for our phone are all fixed. @Dees_Troy once wrote, quite accurately, that anyone could compile and fix the issues if they wanted because TWRP2 is fully open source. Well, that's the point -- it's done now, and I plan to keep updating, regularly, this recovery.
What Works (see also Change Logs and Issues List):
It appears everything, including OTG Support, off-line charging with notifications (LED and UI), screen-blank, and much more. Alas, bugs happen so if you find one, please post the relevant information about the bug here and create an issue on the github project for TWRP2 Sources given below. Devs, please use the updater-binary provided in this thread. Please read the "TWRP2 Things to Watch Out For" section in Change Logs and Issues List for details on why.
Reported Issues, Recent Updates and Things To Watch Out For: Read the Change Logs and Issues List.
To save you some headaches -- seriously -- read the Change Logs and Issues List -- particularly dealing with backups on newer versions like this and older versions, e.g., 2.6.3 or below.
FIRST AND FOREMOST NOTICE:
*** Use this custom recovery at your own risk. It is possible that use of this software may violate your carrier's Terms of Use/Terms of Service. Read the DISCLAIMER before committing to the use of this application.***
SECOND (AND JUST AS 'FOREMOST'), We all should recognize and give generous thanks to @Dees_Troy and the contributors to Team-Win-Recovery-Project ("TWRP"). Further, the same recognition and thanks should go to Steve Kondik And Koushik Dutta and team for creating CyanogenMod. Both of those projects are the basis of all TWRP builds you download here. Between these giants we get to reap huge benefits and just add that which we need. In short, any work I do here is merely standing on the shoulders of those mentioned above. To see the history of TWRP on our Sprint HTC Ones, look to this thread. Finally, give thanks to @kushdeck for his initial work on the device tree for m7wls devices.
** PREREQUISITES **
1) A rooted, Sprint HTC One (m7wls) Android phone;
2) The phone has an unlocked bootloader.
If you don't know what the above means, don't try to install this recovery by yourself -- that's why we have the Sprint HTC One Q&A, Help & Troubleshooting thread.
** INSTALLING **
Install through fastboot. If you don't know how to do that, you should not yet try to do so or even download this recovery. This is not a support thread for installing recoveries, it is a development thread for developing and enhancing the TWRP2 recovery for m7wls devices. To learn about installing recoveries, please post to the Sprint HTC One Q&A, Help & Troubleshooting thread.
Source Code:
The sources for the entire recovery are open source and you can build your own if you like. To do so, read How to compile TWRP touch recovery. For the specific sources necessary for the Sprint HTC One (m7wls) I keep sources up to date here:
TWRP2 Sources
HTC Common Device Tree
M7WLS Device Tree
Kernel
Offline Battery Charging
Feel free to fork those and send pull requests as you see fit.
Disclaimer
*** Legal Disclaimer -- READ ALL OF THE FOLLOWING ***
If you use the software, or convey it to someone else, you and all subsequent
conveyees are bound by the following:
# LEGAL DISCLAIMERS AND ASSUMPTION OF THE RISK BY THE USER OF THIS PROGRAM
# Assumption of the Risk of Use
# YOU ASSUME, AND AGREE TO ASSUME, ALL THE RISK OF HARM BY USING THIS
# PROGRAM. THIS PROGRAM MAY VOID YOUR WARRANTY WITH A THIRD PARTY,
# IT MAY IMPROPERLY OPERATE AND DAMAGE YOUR DEVICE, IT MAY CAUSE ANY
# MYRIAD OF HARMFUL OUTCOMES REGARDING YOUR DEVICE OR THE USE OF THE DEVICE
# ON WHICH IT GETS INSTALLED. YOU ACKNOWLEDGE THAT YOU ARE AWARE OF THOSE
# RISKS, UNDERSTAND THOSE RISKS, AND VOLUNTARILY AND INTELLIGENTLY ELECT
# TO ENGAGE THOSE RISKS BY USING THE PROGRAM.
#Disclaimer of Warranty.
# THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
# LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
# OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND,
# EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
# WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
# THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH
# YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME ALL LIABILITY AND
# AGREE THAT IN NO EVENT WILL YOU SEEK ANY FORM OF RECOMPENSE, WHETHER LEGAL OR
# EQUITABLE, INCLUDING BUT NOT LIMITED TO NECESSARY SERVICING, REPAIR,
# CORRECTION OR OTHERWISE.
#Limitation of Liability.
# IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL
# ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE
# PROGRAM, PERMITTED OR NOT, BE LIABLE TO YOU FOR LEGAL DAMAGES OR EQUITABLE
# RELIEF, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES
# ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT
# LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED
# BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
# PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
# POSSIBILITY OF SUCH DAMAGES.
Downloads
Current Releases:
TWRP2 Recovery 2.8.0.3
MD5: 4967f4139e6a89ec38fdcdf3363fa183
IMPORTANT!!!: If you are upgrading from a version less than 2.7.1.3, please run a nandroid backup of your ROM before loading the new TWRP. A latent command to wipe your data partition may be lurking in your /misc partition from a prior factory reset request if you ever requested that at the bootloader menu. This TWRP will honor that (as will all TWRP versions containing the new code).
Updater Binary (updater-binary for flashable zips) 2.7.1.2-06-18.2014
MD5 Hash: 32f38d458c380300e8606d7994c7d49e
Devs -- This updater-binary is for use in your flashable zips if your users are having problems with 'asserts on getprops.' This is fully TWRP2 compatible (in effect, Android 4.3 and Android 4.4 compatible). For documentation and supported updater-script functionality, see this post.
Prior Releases:
TWRP2 Recovery 2.8.0.2
MD5: aebcb0eb2fa171e77bdd7e005c45f8ba
IMPORTANT!!!: Before loading the new TWRP, please run a nandroid. A latent command to wipe your data partition may be lurking in your /misc partition from a prior factory reset request if you ever requested that at the bootloader menu. This TWRP will honor that (as will all TWRP versions containing the new code).
TWRP2 Recovery 2.7.1.3
MD5: 9b62f4fc94fa2fc2c9c834e8602773cd
IMPORTANT!!!: Before loading the new TWRP, please run a nandroid. A latent command to wipe your data partition may be lurking in your /misc partition from a prior factory reset request if you ever requested that at the bootloader menu. This TWRP will honor that (as will all TWRP versions containing the new code -- official or not).
TWRP2 Recovery 2.7.1.2
MD5: 0078cafec08e3dae169191a31ca94571
Updater Binary 2.6.3.4a (updater-binary for flashable zips)
MD5 Hash: ac14398cc826e8932d1e007a5b476c12
TWRP2 Recovery 2.7.1.1
MD5: 0078cafec08e3dae169191a31ca94571
TWRP2 Recovery 2.7.0.9
MD5: c8c24a041802492543d533d8b3d3f853
TWRP2 Recovery 2.7.0.4b
MD5: 84f2c210b0cf4dcc5e00d6e7becec636
TWRP2 Recovery 2.7.0.4
MD5: d49f435e1d6ad1880ad0d938bd6fb38b
TWRP2 Recovery 2.7.0.3
MD5: 2cbeb54429a96063898578160720b4c1
TWRP2 Recovery 2.7.0.2
MD5: 8dd6520d18668f92c8daa29128ad07a7
TWRP2 Recovery 2.6.3.4a
MD5: 6c10577b5b587e7f44b2b1d7f0659216
TWRP2 Recovery 2.6.3.4
MD5: 107d81dcabacc777f14f42656847ec5c[/INDENT]
Change Logs and Current Issues
Current Release:
Version 2.8.0.3 (09-18-2014)
Includes all prior features from 2.7.x.x, 2.8.0.1 and 2.8.0.2;
Increased SELINUX and POSIX compliance for a bit more future-proofing;
Supports for older (Jelly Bean) crypto;
Battery LED support for charging (as always from this TWRP);
Updated off-mode charging battery graphics (now from latest (standard) CM 11.0 sources, which are quite nice);
Performance mode for long operations (as always from this TWRP);
Synced with Android 4.4.4 / CM-11.0 sources as of date of build (and don't worry -- still supports prior versions);
Synced with OmniRom TWRP2 underlying sources as of date of build;
Updated exFAT support.
Updater-binary Version 2.7.1.2-06-18-2014 Change Logs:
Android 4.4 source tree compatible -- particularly alleviates assert(getprop ...) errors on which old updater-binaries fail;
Built with CM11 with up to date TWRP2 sources as of date of the build.
Prior Releases:
Version 2.8.0.2 (09-14-2014)
Includes all features of 2.8.0.1 -- Note MTP support is very cool;
Battery LED support for charging (as always from this TWRP);
Performance mode for long operations (as always from this TWRP);
Synced with Android 4.4.4 / CM-11.0 sources as of date of build (and don't worry -- still supports prior versions);
Synced with TWRP2 underlying sources as of date of build;
Ext4 file system synced with HTC version (instead of CM-11, as that has bugs);
Updated exFAT support.
Version 2.7.1.3 (07-19-2014)
Fixes /misc partition overwrites to incorrect area (a long standing bug in the official TWRP);
Now using by-name partitioning scheme for all mounts;
More feedback while doing operations;
Added /devlog as a mountable partition (great for devs and those wanting to erase the files and/or look into the logs;
Synced with CM-11 underlying sources as of date of build;
Synced with TWRP2 underlying sources as of date of build;
Updated off-line battery charger application with latest android code and blue text.
Version 2.7.1.2 (06-18-2014)
General maintenance release includes kernel bug fixes/updates;
Synced with CM-11 underlying sources as of date of build;
Sycned with TWRP2 underlying sources as of date of build;
Updated off-line battery charger application with latest android code and blue text.
Version 2.7.1.1 (06-05-2014)
General maintenance release includes kernel bug fixes/updates;
Synced with CM-11 underlying sources as of date of build;
Sycned with TWRP2 underlying sources as of date of build.
Updater-binary Version 2.6.3.4-02-22-2014 Change Logs:
Android 4.4 source tree compatible -- particularly alleviates assert(getprop ...) errors on which old updater-binaries fail;
Built with CM11 with up to date TWRP2 sources as of date of the build.
Version 2.7.0.9 (05-01-2014)
Upgraded kernel to support (arguably inappropriately forced) CM-11 ROM updater-script changes;
Support for CM-11 based builds using only ".md5sum" as opposed to ".md5" as the suffix to md5 hash files;
Synced with CM-11 underlying sources as of date of build.
Sycned with TWRP2 underlying sources as of date of build.
Version bump to cover the fact that CM-11 team put out some TWRP builds with (seemingly) randomly picked version numbers to try to cover on the (forced) updater-script changes.
Many other fixes.
Version 2.7.0.4b (04-06-2014)
Fixes 'set_metadata_recursive some files failed" message, which caused install failure of some Sense 6 ROMs.
Version 2.7.0.4 (03-31-2014)
Minor change to /etc/fstab to help some troublesome USB sticks;
FITRIM support for ext4 (fstrim works in recovery);
New offmode battery charging app -- new graphics and real-time battery charge percentage reporting;
Synced with CM-11 underlying sources to date of the 03-29-2014.
Version 2.7.0.3 (03-25-2014) Change Logs:
Slipstreamed in fix for slow formats on zip flashables -- if you have a prior build of this (look at the date on your flash .img file), redownload this and reflash;
Upgraded all underlying bits to current CyanogenMod build (cm-11.0 as opposed to older Nov. 2013 snapshot of stable/cm-11.0) -- source code synced with CM repo commits as of the date of the build;
All new kernel - using the standard (supported) msm8960 cm11.0 Sprint kernel as opposed to m7 basis -- decreases recovery size by roughly 500Kbytes;
All TeamWin committed bug fixes up to the date of the build (see https://github.com/omnirom/android_bootable_recovery);
Fairly aggressive thermal CPU throttling when in performance mode -- tweaks will be forthcoming based on user feedback for allowing higher temps before throttling.
Note: the TeamWin splash page comes up later than before so don't let that confuse.
TWRP2 Version 2.7.0.2 Change Logs:
All changelogs consistent with official TWRP2 2.7.0.1 release
Includes backward compatibility with old update-binaries (@Dees_Troy's patch after 2.7.0.1 release)
All other tdhite's enhancements from prior builds
Modified Performance mode to run with OnDemand kernel governor as opposed to Performance (runs CPUs a little cooler)
Still based on CM11 -- I am debating whether, given the patch release above, that CM10.2 is worth it in the end.
TWRP2 Version 2.6.3.4a Change Logs:
Added multi-core support for flash and nandroid long running operations -- message notifies you when performance mode is on or off;
Added screen dim settings;
Enhanced file searching for openrecovery scripts;
@elvisypi's off-line charging graphics, now committed until another cool set arrives.
TWRP2 Version 2.6.3.4 Change Logs:
All known issues fixed (OTG support, Screen Blank/Revive, off-line charging animation and screen blank, and much more);
Battery Charging LED support (mimics standard booted ROM LED indicators).
TWRP2 Things to Watch Out for:
Users have reported incompatibility of backups from the (long ago) release 2.6.3.0, though no problems with backup/restore done with the current release. To work around, restore ROM in prior release then flash new TWRP2 release and backup again.
IMPORTANT: A number of flashable zips include old (only Android 4.3 or below compatible) updater-binary executables. Those may cause "getprop" assertion errors (though generally should not as TWRP2 2.7.0.2 and above detect that and provide internal mappings for the old updater-binaries).
There are some themes in use that prevent folks from seeing the Vibration settings. IF YOU ARE USING A THEME -- PLEASE RUN IT WITHOUT THE THEME BEFORE REPORTING BUGS -- TWRP DOES NOT PROMISE THEMES ARE BACKWARD COMPATIBLE
Some folks execute a "fastboot erase cache" after flashing a recovery. Do not do that! Instead, either "fastboot format cache" or leave it alone. The fastboot erase cache command just blows the file system away and leaves you with an unmountable /cache partition until it's formatted (wipe will do that if you end up with errors about 'cannot mount /cache').
Nicely done sir
BTW first
@tdhite if you need a Dev-Host or AFH mirrors let me know I'll post here
AFH Mirror
Dev-Host Mirror
BD619 said:
Nicely done sir
BTW first
Click to expand...
Click to collapse
Let me know how it goes
Sent from my HTCONE using xda app-developers app
Cant wait to try this... :good::good:
BD619 said:
Nicely done sir
BTW first
@tdhite if you need a Dev-Host or AFH mirrors let me know I'll post here
Click to expand...
Click to collapse
Yea -- I do. My mirrors are fine too, but I'd really like this in the mirrors most folks have familiarity with. Thanks so much. If you upload somewhere like that, lemme know and I'll update the download links.
Thanks for your contribution man!
Sent from my HTCONE using Tapatalk
Sweet well done!!. Thank you much sir. One request, can we get the option to turn off vibration please
Superb job. Finally a recovery without bugs!
Sent from my HTC One using Tapatalk
benny3 said:
Sweet well done!!. Thank you much sir. One request, can we get the option to turn off vibration please
Click to expand...
Click to collapse
Yes please disable vibration if possible
Update tried Advance wipe/wipe
cache/dalvik cache/system/data
Failed
Tried using superwipe
Failed
Was getting unable to mount cache error.
Flashed back to 2.6.3.0
Should have gotten a recovery log darn it
Awesome!! Thank you for all your hard work this is amazing
benny3 said:
Sweet well done!!. Thank you much sir. One request, can we get the option to turn off vibration please
Click to expand...
Click to collapse
BD619 said:
Yes please disable vibration if possible
Update tried Advance wipe/wipe
cache/dalvik cache/system/data
Failed
Tried using superwipe
Failed
Was getting unable to mount cache error.
Flashed back to 2.6.3.0
Should have gotten a recovery log darn it
Click to expand...
Click to collapse
If u have a custom theme delete it reboot into stock recovery and the option for vibration shows.
sent from my-beanstalk-one
bearw815 said:
If u have a custom theme delete it reboot into stock recovery and the option for vibration shows.
sent from my-beanstalk-one
Click to expand...
Click to collapse
No theme here
BD619 said:
No theme here
Click to expand...
Click to collapse
Mine shows option to change vibration.
The error stated for the super wipe script is a get prop error failure.
Edit: getprop (ro.product.device)==
sent from my-beanstalk-one
bearw815 said:
Mine shows option to change vibration.
The error for the super wipe script is a get prop error failure.
sent from my-beanstalk-one
Click to expand...
Click to collapse
I have the vibration change as well
Sent from my One using Tapatalk 2
benny3 said:
Sweet well done!!. Thank you much sir. One request, can we get the option to turn off vibration please
Click to expand...
Click to collapse
Vibrations are all there -- just to go to "Settings" and "Vibration Duration" -- turn them all down to your liking. If anything is missing, look to your theme -- others had the same issue during early testing.
BD619 said:
Yes please disable vibration if possible
Should have gotten a recovery log darn it
Click to expand...
Click to collapse
But what will you use then?
Sent from my GT-N5110 using Tapatalk
FrozenRiff said:
But what will you use then?
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
Good point...
Hello I have a razer phone 2 a long time ago I wanted to install a specific rom was the lineageOs but the problem is that I also install the recovery by removing the twrp, personally I like it better that is why I tried to change it again but I do not know what It could have passed the recovery if I change but the system is no longer there, I had seen that using the repair or change file system could help to repair the corrupt partitions but it tells me that there is nothing present and when trying to install any file it always gives an error.
A solution that I can think of is to install a backup copy but unfortunately I did not take any and I could not find one online that is why I ask for help to see if someone can provide me with a backup copy of the entire phone since that can possibly revive it.
Thank you
Go HERE: https://developer.razer.com/razer-phone-dev-tools/factory-images/ and download the appropriate image for your device. Follow all the directions for installing ADB/Fastboot drivers and flash the phone from your PC. You'll be up and running in no time. See the forums for installing root and TWRP using arter97-Rxx kernel and additionally look into Magisk V23 for root and customization.
Magisk - The Magic Mask for Android
Welcome to the Magisk Release / Announcement thread! For all up-to-date info and links, please directly check Magisk's GitHub Page Installation Download count of previously XDA hosted files: 25,490,945 v1: 8746 v2: 2251 v3: 3790 v4...
forum.xda-developers.com
****Moderator Notice****
This project has been taken down due to violation of the XDA GPL Policy.
I did not post this thread by stealing it from someone. I posted this because the original thread and the google drive links to the latest TWRP for the A328 were no where to be seen.
CAUTION: I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR DEVICE, IF YOU BLAME IT ON ME I WILL LAUGH AT IT. MAKE SURE ALL YOUR DATA IS BACKED UP TO SOMEWHERE. (If anyone has warranty for this phone now, it is void once you are doing this.) --WARNING
TWRP 3.2.1 Recovery for Lenovo A328 is the latest version I found for this phone.
G drive: ***Link removed by moderator***
When reposting this thread please credit me and the whoever made TWRP 3.2.1 For Lenovo A328.
INSTRUCTIONS:
Please do not try to flash the scatter file provided in the folder in SP Flash tool. Some error messages will come and That will brick your phone.
_________________________________________________________________________________________________
The easiest method is to root your phone by Magisk: **Link removed by moderator**
Then use an app called Flashify to flash the TWRP image to your phone. ( Search YouTube for more information)
WARNINGS:
Please copy the image to your internal storage and then flash it using Flashify.
DO NOT FLASH IT ON YOUR SD CARD OR EXTERNAL STORAGE.
Do not wipe internal storage when installing a rom or anything, because this will also delete the TWRP recovery from your storage. (From experience)
Only wipe Data, Dalvik Cache, Cache and System.
Features:
Flashing Images and Zips (LOL)
Date and time customization
Brightness customization
File explorer
Improved ADB Sideload
Faster MTP file transfer
Quicker flashing
More useless settings options
____________________________________________
To boot: Hold power button. Once Phone vibrates leave power button and hold Volume UP and Volume DOWN together until Teamwin logo shows.
As you know I don't really know about the TWRP information so if anything I mention is wrong in this thread please mention it.
Credits to Parrot403 on 4PDA for the recovery.
Credits to me for improving bugs and other issues.
Happy Flashing
Hello @Acidanthera
Please be aware that since this is not your own project, you must provide credit to who built this. An easy way to do this is by linking to the original thread.
If there is no original thread, you must link the source that was used to build this recovery.
Lastly, we do not recommend Kingoroot because it is a known source of malware. Magisk is by far the best option for root.
V0latyle said:
Hello @Acidanthera
Please be aware that since this is not your own project, you must provide credit to who built this. An easy way to do this is by linking to the original thread.
If there is no original thread, you must link the source that was used to build this recovery.
Lastly, we do not recommend Kingoroot because it is a known source of malware. Magisk is by far the best option for root.
Click to expand...
Click to collapse
Okay, i made some improvements and fixes to the recovery so i did not give credit to the person who ported it to this phone. Done as instructed
Acidanthera said:
Okay, i made some improvements and fixes to the recovery so i did not give credit to the person who ported it to this phone. Done as instructed
Click to expand...
Click to collapse
Okay so this is your own project. Please publish the source you built it from. For more details see the GPL Policy linked in my signature.
@Acidanthera As you have failed to publish the source you used to build this, I have taken this down. For more information, please read the XDA GPL Policy.
Further, the only offical and safe Magisk source is @topjohnwu 's Github:
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Please do not post any other source as they might be infected with malware.