Related
I have an M2, I did, something to it which involved flashing something and unlocking the bootloader, It got bricked, and the only way i could recover it is with the tiny off button next to the Sim-Slot (Lifesaver, Thanks Sony) and putting it into that flash mode thing where the light goes blue, and Flashing a stock firmware, Or so I thought, It was customised, Also in the whole process I somehow Downgraded to Jelly Bean, and the Updater says that I have custom firmware, I have clockworkmod, But it didnt work properly and now i have no recovery menu at all also Miracast is broken, HSDP (Some sort of DRM thing) failed probably caused by one of these issues
So yeah does anyone have a Firmware for my device so that the Sony Updater will accept it? Don't care which android version, as long as It can be updated back up to KitKat and is UK GENERIC no customisations
All i wanted was to root my phone to get a WiFi password that I lost
Thanks
bigglescat5 said:
I have an M2, I did, something to it which involved flashing something and unlocking the bootloader, It got bricked, and the only way i could recover it is with the tiny off button next to the Sim-Slot (Lifesaver, Thanks Sony) and putting it into that flash mode thing where the light goes blue, and Flashing a stock firmware, Or so I thought, It was customised, Also in the whole process I somehow Downgraded to Jelly Bean, and the Updater says that I have custom firmware, I have clockworkmod, But it didnt work properly and now i have no recovery menu at all also Miracast is broken, HSDP (Some sort of DRM thing) failed probably caused by one of these issues
So yeah does anyone have a Firmware for my device so that the Sony Updater will accept it? Don't care which android version, as long as It can be updated back up to KitKat and is UK GENERIC no customisations
All i wanted was to root my phone to get a WiFi password that I lost
Thanks
Click to expand...
Click to collapse
I guess XperiFirm is what you need:
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
quake73 said:
I guess XperiFirm is what you need:
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
Click to expand...
Click to collapse
Will Version "Customised UK" allow me to Update using the Sony Updater?
bigglescat5 said:
Will Version "Customised UK" allow me to Update using the Sony Updater?
Click to expand...
Click to collapse
No the sony software picks up any device if the bootloader is unlocked. it will only re-flash the firmware if the bootloader is locked.
However you can use flash tool http://www.flashtool.net/index.php and it will do it for unlocked bootloaders.
HatchetEgg said:
No the sony software picks up any device if the bootloader is unlocked. it will only re-flash the firmware if the bootloader is locked.
However you can use flash tool and it will do it for unlocked bootloaders.
Click to expand...
Click to collapse
Can I Re-Lock the bootloader? And how can Flashtool update my phone?
bigglescat5 said:
Can I Re-Lock the bootloader? And how can Flashtool update my phone?
Click to expand...
Click to collapse
Make sure the drivers are installed for your phone on you laptop/PC first.
once you have downloaded a Firmware for the M2 you put the firmware in the firmware folder of the flashtool directory then you select the thunderbolt icon. select flash mode and follow the instructions. Also it will say press the back button in the instructions instead you need to press vol down for flash mode or up for fastboot mode.
Once done you get a little window that shows and just select the firmware you want to flash and the way you go.
you can unlock and re-lock bootloaders with flashtool but I think you need to have unlocked it with flash tool to do that.
Try these links:
Device: Xperia M2 (D2303)
CDA: 1281-1548
Customization : CE
Release: 18.0.C.1.13 / R1B
https://drive.google.com/file/d/0BxfA3HIG47hxLXFjQV92UC0zNTg/edit?pli=1
Device: Xperia M2 (D2303)
CDA: 1281-1548
Customized CE1
Release: 18.3.1.C.1.13 / R1B
https://docs.google.com/file/d/0BxfA3HIG47hxMElLNzFhQUFXOTg/edit?pli=1
bigglescat5 said:
Will Version "Customised UK" allow me to Update using the Sony Updater?
Click to expand...
Click to collapse
If you only need a functional KK 4.4.4 phone then choose Customized UK 18.3.1.C.1.13 in xperifirm, download it, wait for it to unpack the files.
Then you need to use flashtool, got to Tools->Bundles->Create to create a flashable .ftf file. Select all the files in the folder where you downloaded the rom, fill in the fields for version/branding/device and click create.
Lastly, you click the Lightning button in flashtool, select flashmode, select your newly created ftf.
When it asks to connect your phone, power off the phone, press&hold the VolDown button when inserting the usb cable, the led should blink briefly green once. The flashing should begin at that moment.
quake73 said:
If you only need a functional KK 4.4.4 phone then choose Customized UK 18.3.1.C.1.13 in xperifirm, download it, wait for it to unpack the files.
Then you need to use flashtool, got to Tools->Bundles->Create to create a flashable .ftf file. Select all the files in the folder where you downloaded the rom, fill in the fields for version/branding/device and click create.
Lastly, you click the Lightning button in flashtool, select flashmode, select your newly created ftf.
When it asks to connect your phone, you press&hold the VolDown button when inserting the usb cable. The flashing should begin at that moment.
Click to expand...
Click to collapse
XperiFirm just throws a error, wants me to reinstall JRE, I have, and I have uninstalled JDK and stuff too with the latest version
WHY DO ALL MY DEVICES HATE ME!
bigglescat5 said:
XperiFirm just throws a error, wants me to reinstall JRE, I have, and I have uninstalled JDK and stuff too with the latest version
WHY DO ALL MY DEVICES HATE ME!
Click to expand...
Click to collapse
from the xperifirm page:
** If you have Flashtool installed, Java Runtime is bundled with it and doesn't have to be installed separately. Just extract XperiFirm's files to Flashtool's folder and run XperiFirm.exe from there.**
quake73 said:
from the xperifirm page:
** If you have Flashtool installed, Java Runtime is bundled with it and doesn't have to be installed separately. Just extract XperiFirm's files to Flashtool's folder and run XperiFirm.exe from there.**
Click to expand...
Click to collapse
Its downloading now , Is there any way to make it so when I flash it later it will not wipe my phone, Not essential, but i hate reinstalling and reconfiguring everything
bigglescat5 said:
Its downloading now , Is there any way to make it so when I flash it later it will not wipe my phone, Not essential, but i hate reinstalling and reconfiguring everything
Click to expand...
Click to collapse
At the ftf selection window, under [Wipe:], uncheck [DATA]. That way, your data will not get erased and It might save you from reinstalling everything.... In theory
Try with DATA unchecked first, see if all is fine. If not then reflash the clean way, with DATA checked. Tell us here how it went.
quake73 said:
At the ftf selection window, under [Wipe:], uncheck [DATA]. That way, your data will not get erased and It might save you from reinstalling everything.... In theory
Try with DATA unchecked first, see if all is fine. If not then reflash the clean way, with DATA checked. Tell us here how it went.
Click to expand...
Click to collapse
Flashed without data, It seemed to flash everything but When I booted the phone, It was still JellyBean where did all the flashes go?
bigglescat5 said:
Flashed without data, It seemed to flash everything but When I booted the phone, It was still JellyBean where did all the flashes go?
Click to expand...
Click to collapse
Then, 2 possibilities come to mind, you either didnt download the latest version (18.3.1.C.1.13) or didnt select it correctly in flashtool. I hope you only unchecked DATA, not checked everything under Exclude
How much time did the flashing process take, it should be, maybe more than 5 minutes
I downloaded Kitkat for sure, The only other thing i deselected was TA, because I heard that TA is bad and kills your phone
bigglescat5 said:
I downloaded Kitkat for sure, The only other thing i deselected was TA, because I heard that TA is bad and kills your phone
Click to expand...
Click to collapse
Then i'm out of ideas. as for that TA, i honestly am not sure what that exactly is or wheteher it is lost during unlocking. i leave it unckecked, have heard that flashtool decides if it needs to be flashed.
here is how i would flash 4.4.4:
(do you have all those parts? the ones in red? maybe not all but system.sin is THE android, kernel is important, too)
quake73 said:
Then i'm out of ideas. as for that TA, i honestly am not sure what that exactly is or wheteher it is lost during unlocking. i leave it unckecked, have heard that flashtool decides if it needs to be flashed.
here is how i would flash 4.4.4:
Click to expand...
Click to collapse
I will try flashing TA
bigglescat5 said:
I will try flashing TA
Click to expand...
Click to collapse
ok, now i saw...seems you downloaded 18.0.C.1.13
the lates android version for m2 in xperifirm is 18.3.1.C.1.13, i guess you got the wrong version.
Oh wait, I must be flashing the wrong rom lol
Ok i figured it out i somehow made the bundle thing wrong and Flashtool didnt pick it up, i am a total idiot , I flashed the rom i orginally used to un-brick my phone
Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks
Same problem here
Ulverinho said:
Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks
Click to expand...
Click to collapse
Have to install stock ROM again then update it via ota. Could also try flashing an ota update file via the official recovery of your phone.
A_Bunny said:
Have to install stock ROM again then update it via ota. Could also try flashing an ota update file via the official recovery of your phone.
Click to expand...
Click to collapse
Yep, my guess was the same. As per official recovery - I'll try adb sideload, but first time it couldn't find phone (all drivers installed and up-to-date).
http://forum.xda-developers.com/moto-g/help/driver-fastboot-falcon-s-t2820848
This error pops up - I can't find solution also...
Ulverinho said:
Yep, my guess was the same. As per official recovery - I'll try adb sideload, but first time it couldn't find phone (all drivers installed and up-to-date).
http://forum.xda-developers.com/moto-g/help/driver-fastboot-falcon-s-t2820848
This error pops up - I can't find solution also...
Click to expand...
Click to collapse
Install the recovery with fastboot not adb.
A_Bunny said:
Install the recovery with fastboot not adb.
Click to expand...
Click to collapse
Well, I might misunderstood, but:
I have official recovery (fastboot is mode of it, I guess, when U press Power+volume key?)
I've read about adb sideload zip_name_of_OTA.zip
I don't know any other way to install OTA apart from let phone handle it OR adb sideload.
Ulverinho said:
Well, I might misunderstood, but:
I have official recovery (fastboot is mode of it, I guess, when U press Power+volume key?)
I've read about adb sideload zip_name_of_OTA.zip
I don't know any other way to install OTA apart from let phone handle it OR adb sideload.
Click to expand...
Click to collapse
Just load it onto your phone before you flash it. Your ROM does work.
A_Bunny said:
Just load it onto your phone before you flash it. Your ROM does work.
Click to expand...
Click to collapse
Load ZIP of OTA on SD Card and install it from Recovery? Will it work?
Ulverinho said:
Load ZIP of OTA on SD Card and install it from Recovery? Will it work?
Click to expand...
Click to collapse
It may work if it is the stock recovery.
A_Bunny said:
It may work if it is the stock recovery.
Click to expand...
Click to collapse
Got this, screenshot in attachment.
Fingerprints are wrong. In build.prop - I can see it's fine, fingerprint of current 4.4.4. - matches expected.
But as soon as update starts - it says that 4.4.2 is fingerprint of my OS. Bollocks.
Edited OTA zip, edited some metadata file...
Why it won't install on pretty clean phone - I can't understand...Previous installs of OTA went fine with root etc.
Ulverinho said:
Got this, screenshot in attachment.
Fingerprints are wrong. In build.prop - I can see it's fine, fingerprint of current 4.4.4. - matches expected.
But as soon as update starts - it says that 4.4.2 is fingerprint of my OS. Bollocks.
Edited OTA zip, edited some metadata file...
Why it won't install on pretty clean phone - I can't understand...Previous installs of OTA went fine with root etc.
Click to expand...
Click to collapse
Well the only thing I would recommend would be to install the stock system though fastboot manualy.
Ulverinho said:
Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks
Click to expand...
Click to collapse
i feel ya same thing here, than i tryed installing a stock lollipop from here via twrp witch ended up messing my phone with failing the procedure wondered around couldnt revert to stock since im a noob and didnt even backed up the rom,but at the and of the day thank god for the cm12.1 finally menaged to make my phone running again at least
Greetings, I have the same problem, it is the last screen that appears when you install the update, and then restarts it goes off the screen update error ...
To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.
fusionice said:
To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.
Click to expand...
Click to collapse
Yeah, that's the better way.
But I guess, I can install Stock 5.* straight away after wiping? Why bother about OTA, if there is ROM available?
fusionice said:
To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.
Click to expand...
Click to collapse
Yep.
The solution is backup data, restore stock last firmware using fastboot guide posted in this forum and not even update apps (cancel gmail registration and everything it asks when it first starts) ONLY update motorola update services so you can get the ota again an install it. If you have the ota downloaded you can flash it through recovery but using the last recovery version (.61) and of course last firmware version. If you guys flash it all through fastboot, it should install w/o any problems.
Dear members
I want to update my rooted E6633 running 32.2.A.0.376 to 32.4.A.0.160 through the OTA, of course, because my device is already rooted the downloaded update couldn't be installed, the reason behind seeking for this update that I'm not able to make phone call and the phone is not able to detect the SIM cards and showing pop up error message android.phone.com has stopped repeatedly whenever I press ok and phone app crashes.
what I have done so far is through superus app I chose full unroot and the phone rebooted successfully and I have checked it with the root checker showing that the root is not installed properly
I launched the flashtool and booted the device on flashmood and selected the bootloader relock option
flashtool said that bootloader finished relocking the device, but the device is not able to boot to the normal mood whenever I push the power on button the device only vibrate or boots to flashmood when the cable is connected but when unlocking the bootloader, the device boots normally.
How to update my device without losing my current data and to fix phone application and SIMs recognition?
Do I have to fastboot the original Sony kernel and where can I find it? because I didn't make any backup
I don't mind losing root I just want to make the OTA update installed without flashing my phone and starting from the beginning.
Thank you
Notes: when the device is rooted again and when opening luckyputcher the error messages disappear and SIMs cards work fine and phone app opens normally
I will assume the reason you are not going for this is because of limited bandwidth or something along those lines.
You can either wait for someone to post a stock kernel of it but if you have a the .376 ftf you can extract the kernel using this guide (at step 3 you can flash the kernel using adb/fastboot)
Dna10 said:
I will assume the reason you are not going for this is because of limited bandwidth or something along those lines.
You can either wait for someone to post a stock kernel of it but if you have a the .376 ftf you can extract the kernel using this guide (at step 3 you can flash the kernel using adb/fastboot)
Click to expand...
Click to collapse
Thanks for your reply, not limited bandwidth but slow connection that one of the reasons, if I could extract the kernel from the firmware and flashing it without losing the data and allowing ota to be installed this will be great. Hopefully this way fixes the system errors and keeping the data and settings as it is.
Thanks again I will start following these guidelines if something went wrong surely I will sue you :laugh:
Ok I downloaded the ftf file, extracted kernel.sin
opened flashtool
I coudn't found the Dump Data option but I clicked on extract data inisted
I renamed the extracted kernel from elf to boot.img
I flashed the kernel using this command
fastboot boot boot.img
I got this error message : FAILED (remote: dtb not found)
so I relocked the bootloader and I got diffrent message : FAILED (status read failed (Too many links))
I went to flashtool and flasehd the kernel with no errors but the mobile did'nt boot, it's stuck on sony logo
what is the problem !?
kingskull said:
Ok I downloaded the ftf file, extracted kernel.sin
opened flashtool
I coudn't found the Dump Data option but I clicked on extract data inisted
I renamed the extracted kernel from elf to boot.img
I flashed the kernel using this command
fastboot boot boot.img
I got this error message : FAILED (remote: dtb not found)
so I relocked the bootloader and I got diffrent message : FAILED (status read failed (Too many links))
I went to flashtool and flasehd the kernel with no errors but the mobile did'nt boot, it's stuck on sony logo
what is the problem !?
Click to expand...
Click to collapse
Ok First Things First you should have used the command :
fastboot flash boot boot.img
Secondly to remedy to the problem flash the ftf BUT don't select anything in the wipe section, keep them all unchecked. Then you will have a stock and unrooted ROM without having lost your data.
Edit: If you were able to download that big of a file why didn't you go directly with the .106 fw? You would have had the same initial result you wanted! ::facepalm::
Dna10 said:
Ok First Things First you should have used the command :
fastboot flash boot boot.img
Secondly to remedy to the problem flash the ftf BUT don't select anything in the wipe section, keep them all unchecked. Then you will have a stock and unrooted ROM without having lost your data.
Edit: If you were able to download that big of a file why didn't you go directly with the .106 fw? You would have had the same initial result you wanted! ::facepalm::
Click to expand...
Click to collapse
I was not sure about flashing the whole ftf, I was worried if I flashed the the new 160 would cause the system to break down, so I decided to unroot and to keep my self on the safe side by unrooting, relocking bootloader and installing the stock kernel so that I will be able to update to the .160 fw through OTA
I will follow your instruction about flashing the .367 fw. I was thinking about it but I wasn't sure which options that should I select without losing the data. Should I select the whole options except the wipe section?
Thanks for your help
Don't select anything! It should look like in the screenshot I uploaded
Dna10 said:
Don't select anything! It should look like in the screenshot I uploaded
Click to expand...
Click to collapse
Hmmm yesterday before posting my last reply I flashed the firmware I only selected the kernel and nothing happened, no changes happened to the firmware except the ota size was reduced from 485mb to 187mb !?
Oh dear according to the screenshot you uploaded the ftf I downloaded is for middle east and I'm from Saudi Arabia never thought there is custom firmware for Saudi Arabia do you think that the reasone behind this boot failure is because of the difference between the installed firmware and the downloaded one?
It shouldn't pose any problems at all. Any problem arising might be of your doing. What you could do is make a Titanium Backup of your user apps and go for clean install if your problems persist.
Dna10 said:
Don't select anything! It should look like in the screenshot I uploaded
Click to expand...
Click to collapse
Ok that's great, after flashing the ftf the device boot normally but the bloody ass error still persist I can't make or receive phone calls the phone app is crashing, of course, since the root is not available luckypatcher will not solve the problem and to be honest I don't know what is the relation between this error and luckypatcher.
The funny thing after the process succeed the phone showing that the software is up to date man !!
more than that when checking software update settings app crashes
I really want to thank you for helping me, I really appreciate it :good:
my last option is downloading 160 fw and flashing it
Have you tried a different dialier app?
First Lock Bootloader Then Flash FTF File.
The stock ROM has a feature called verity, which ensures that the system partition is not modified. It uses a cryptographic signature to verify each sector on the partition. If any sector is modified, it is treated as corrupt.
In other words, any changes to the system partition will render it unbootable. This includes mounting /system read-write in recovery, even once.
In order to modify your system partition or recover from accidentally mounting your system partition read-write, you must download and flash the correct boot image using tuliptool.
You can find stock boot images with verity removed here:
US model, version 7.1.1 b12
md5=71428e4957763858f47bc9540e848d5e
US model, version 7.1.1 b14
md5=c6a67411e81f27d798eea035ddf4261e
EU model, version 7.1.1 b09
md5=ba210d332d3527b81f652dd0d2ce962e
i tried to see what would happen if i adb sideload supersu and my results came out that the went to zte screen and went into a bootloop didnt boot up but i have root priv in twrp....hmm. so i re-edl boot to after that i was able to boot back in to my android without root or supersu and twrp went back to normal aswell i was in the mood to test thankfully i was able to fix what ever had any issues
What would we need to provide for you to make one for v1.0.0B06?
I can make one for any firmware version. I just need the following:
* any relevant regional or model info.
* firmware version (including android version).
* the backup boot image, eg. from tuliptool.
parawizard said:
What would we need to provide for you to make one for v1.0.0B06?
Click to expand...
Click to collapse
So if I were to want to stay on the current ZTE rom (for now) would I need to flash this in order to root or currently root is only supported on the incomplete rom you are working on?
Depends how you root. I don't run stock so someone else should answer with details.
fallen00sniper said:
So if I were to want to stay on the current ZTE rom (for now) would I need to flash this in order to root or currently root is only supported on the incomplete rom you are working on?
Click to expand...
Click to collapse
tdm said:
Depends how you root. I don't run stock so someone else should answer with details.
Click to expand...
Click to collapse
i'm not a fan of the stock image, i do like to keep features which the stock seems devoid other than atmos which used to be hit or miss lol
i am sure someone out there likes the stock look, i used nova launcher and made things smaller, neater and tried to make it look a little better.
Done some experiments with SuperSU 2.82 (unsuccessfully, got bootloop).
In other words, any changes to the system partition will render it unbootable. This includes mounting /system read-write in recovery, even once.
Click to expand...
Click to collapse
And was able restore phone to work only with this EU boot.
Thanks, for making and publishing it!
Hi tdm, my 7 mini is USA hardware version but with European 6.0.1 firmware (build number ZTE B2017G V1.0.0B12). I tried to go back to USA Nougat firmware but unsuccessfully. Basically my phone was turned into P852A11 from P852A12. Do I need a new boot image with verity removed so that I can flash USA firmware? If I have to use Tuliptool, can you build a Windows32 version? Thanks in advance.
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
bao_gg said:
Hi tdm, my 7 mini is USA hardware version but with European 6.0.1 firmware (build number ZTE B2017G V1.0.0B12). I tried to go back to USA Nougat firmware but unsuccessfully. Basically my phone was turned into P852A11 from P852A12. Do I need a new boot image with verity removed so that I can flash USA firmware? If I have to use Tuliptool, can you build a Windows32 version? Thanks in advance.
Click to expand...
Click to collapse
tdm said:
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
Click to expand...
Click to collapse
Thank you tdm. You are awsome. I will provide you the checksums tomorrow.
Hey @tdm
Wanted to ask if you just removed the "verify" option in the fstab file to strip the dm verity checks? I might have read something like this before
Yes that's exactly it.
TheSSJ said:
Hey @tdm
Wanted to ask if you just removed the "verify" option in the fstab file to strip the dm verity checks? I might have read something like this before
Click to expand...
Click to collapse
I had finally gotten around to unlocking the bootloader and flashing TWRP.
Would flashing one of your custom ROMs without flashing the verity-free boot images affect anything?
I would suggest flashing the no verity boot just to avoid the headache
The stock boot images are only for running stock. Custom ROMs all include their own boot images.
JoeGatto said:
I had finally gotten around to unlocking the bootloader and flashing TWRP.
Would flashing one of your custom ROMs without flashing the verity-free boot images affect anything?
Click to expand...
Click to collapse
tdm said:
The stock boot images are only for running stock. Custom ROMs all include their own boot images.
Click to expand...
Click to collapse
Great. Looks like I'll be trying AOKP soon.
JoeGatto said:
Great. Looks like I'll be trying AOKP soon.
Click to expand...
Click to collapse
I've been running it for a couple of days and so far its great. No issues here
MrWhite0429 said:
I've been running it for a couple of days and so far its great. No issues here
Click to expand...
Click to collapse
You weren't kidding. Feels much faster than ZTE's ROM, and so refreshing as long as I've been looking at that MiFavor UI.
EDIT: Battery drain during standby.
tdm said:
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
Click to expand...
Click to collapse
Hi tdm, my adb can not recognize the mini. And in order to get the partition info, I need to "boot into twrp" as the instruction says. But my recovery is STOCK not TWRP.
Anyway, if you can make a win32 Tuliptool, I can unlock the bootloader and flash the TWRP in. After that, I can flash any firmware that I want. Is it correct?
Hey all,
I love stock android! So when i read about OpenKirin I was excited. Did anyone use this to install LineageOS on our mate9 successful? What are your experiences?
I have another question as well: I changed my model to the MHA-L29, rooted with a custom recovery.
OpenKirin says it needs to have the stock one. Does anyone have a link to the stock MHA-L29 recovery and a guide on how to install it?
dekraan said:
Hey all,
I love stock android! So when i read about OpenKirin I was excited. Did anyone use this to install LineageOS on our mate9 successful? What are your experiences?
I have another question as well: I changed my model to the MHA-L29, rooted with a custom recovery.
OpenKirin says it needs to have the stock one. Does anyone have a link to the stock MHA-L29 recovery and a guide on how to install it?
Click to expand...
Click to collapse
First off, this thread probably belongs in Q/A.
Moving on:
I've run all 3 provided ROMs, Carbon as my daily driver and Lineage and RR for testing various things. They all work pretty well.
For stock recovery & ramdisk, download your current firmware (or if you've run other Treble ROMs as well, the version that corresponds to your current build number in Settings / System / About Phone) using Firmware Finder - you only need the main update.zip for this. You'll also need one of the utilities for extracting them. There's Huawei Update Extractor (I think that's what it's called anyway) for Windows, or https://github.com/marcominetti/split_updata.pl for Linux / Mac. Extract the ramdisk and recovery ramdisk images and there you go.
Installing those is a matter of rebooting into the bootloader and running:
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash ramdisk ramdisk.img
(The name for recovery_ramdisk.img may vary a bit - the windows app will extract it as RECOVERY_RAMDIS.img.)
From there, just follow their instructions. If you have any problems, hit up the Telegram chat linked off the site, someone will be willing to help.
@irony_delerium, thank you very much. That sounds like something even I can do without too much problems
How do you like it, being on LineageOS?
dekraan said:
@irony_delerium, thank you very much. That sounds like something even I can do without too much problems
How do you like it, being on LineageOS?
Click to expand...
Click to collapse
Like I said in my original reply, my daily driver is Carbon; the Lineage builds I've only run briefly because NFC wasn't enabled, but the CarbonROM builds there have it. I use Google Pay every day, so it's kind of a requirement for me.
With that said, the only thing that's got issues for me is the camera app, and most of the blame for that is with Huawei. It generally works, but it'll close & restart often when switching modes or trying to start a recording.
I know there are various other minor issues with recording video in all 3, again because Huawei. (They put together bum codecs, and then patched the system side of the EMUI media stack to deal with the bum codecs, instead of fixing the codecs.)
Also worthy of mention (especially because I see people asking about this all the time): there is no VoLTE support. The devs are aware of it. Unless you're on a network that is pure LTE, it's mostly a non-issue. If you are, it's probably a deal breaker.
Getting on from there, they're all clean Android experiences, without the overbearing weight of EMUI. They don't try to pull some of the things EMUI did - the final breaking point for me was when it insisted on terminating apps in the background regardless of how much you might actually be using them. (In my case, AdGuard as a VPN service.)
Dear Sir
How Can I Revert to Stock Emui?
I am on Lineage baeta 4 ROM.
With Stock Recovery.
Tried Update and Hwota Methods but no Success.
I have Searched Everywhere.
Please Do A Step By Step Guide for Newbies.
Regards
talpur1 said:
Dear Sir
How Can I Revert to Stock Emui?
I am on Lineage baeta 4 ROM.
With Stock Recovery.
Tried Update and Hwota Methods but no Success.
I have Searched Everywhere.
Please Do A Step By Step Guide for Newbies.
Regards
Click to expand...
Click to collapse
Some comments before, Huawei Firmware Extractor. Extract system.img from the stock rom you used before flash Lineage.
Flash stock system.img in fastboot.
I have downloaded and tried to extract 4 roms but The Extractor tool is Giving error.
Its Giving invalid Hearder crc error.
talpur1 said:
I have downloaded and tried to extract 4 roms but The Extractor tool is Giving error.
Its Giving invalid Hearder crc error.
Click to expand...
Click to collapse
Go to settings in the app and disable CRC checking. (Bug in the app.)
I was on OldDroid's OpenKirin, but today switched to Carbon Beta 2 from https://openkirin.net/download/. This installed without problems and I did a hard reset as part of installation. The earlier version worked very well, except there were a few bugs. I haven't found any bugs in this ROM yet.
Random question: Does anyone know if it's safe to go from one build to another directly? I'm trying Lineage but would like to give Resurrection Remix a go. The instructions say that you should be coming from EMUI...
Thanks
jellmoo said:
Random question: Does anyone know if it's safe to go from one build to another directly? I'm trying Lineage but would like to give Resurrection Remix a go. The instructions say that you should be coming from EMUI...
Thanks
Click to expand...
Click to collapse
It's fine to go between them, provided you reload the stock ramdisk (if you installed Magisk) & factory reset before booting into the new ROM.
irony_delerium said:
It's fine to go between them, provided you reload the stock ramdisk (if you installed Magisk) & factory reset before booting into the new ROM.
Click to expand...
Click to collapse
You can switch between the Custom Roms. I always do. Backup your data on the data partition via USB to PC, go to TWRP do a factory reset and then install the new image via fastboot. Reboot and rejoice
mcc2005 said:
You can switch between the Custom Roms. I always do. Backup your data on the data partition via USB to PC, go to TWRP do a factory reset and then install the new image via fastboot. Reboot and rejoice
Click to expand...
Click to collapse
TWRP only works right on a Huawei device if you're either decrypted or running EMUI. (On a custom ROM, with an encrypted device, TWRP doesn't even start up - it locks up at the splash screen.)
Factory reset using stock recovery. Only using stock recovery. The OpenKirin team will not support any other configuration.
yes you are right. but there is still the possibility to do these things with a patched TWRP. I use this for my Mate 9 https://drive.google.com/file/d/1h50RJ6LNNSEVW9CS16C0NjeP7ZZNTECE/view?usp=sharing
mcc2005 said:
yes you are right. but there is still the possibility to do these things with a patched TWRP. I use this for my Mate 9 https://drive.google.com/file/d/1h50RJ6LNNSEVW9CS16C0NjeP7ZZNTECE/view?usp=sharing
Click to expand...
Click to collapse
And the reason why I say anything is because the 2 most common problems I see are:
1) "I'm on Jio, where's my VoLTE?"
2) "I used TWRP and (it's not working | I screwed up | it's broken)".
The response to the first is universally, go back to stock.
The second, restore your entire stock firmware and then follow the instructions exactly as they are written.
With root, you can back up your apps with Titanium. I haven't had good luck with backing up settings with Titanium and after attempting to restore settings, I usually wind up wasting an hour or two and then factory-resetting and just reinstalling the apps. Now I don't even bother backing up settings, but just back up my apps. Even then two or three seem to be botched but uninstalling/reinstalling those will fix that problem. (It isn't always the same ones, either; not sure what causes this). This approach avoids the pain of configuring apps, e.g. travel app usernames and passwords, as well as preserving messages and the like. The biggest nuisance for me is that I carry around 40 unread Amazon books, which have to be sent to the phone (and I'm not so good at remembering which ones I've already read out of the more than 500 in my account), and I carry a bunch of google offline maps, which have to be manually recreated. Lastpass helps with login information too.
In my most recent (Carbon B2) install, I didn't bother with the backup but installed everything fresh and I had a fully functioning phone with 99% of the configuration I like within 2 hours, since I'd been pretty careful to put all the passwords and so on for my roughly 80 apps into a secured text file, as well as backing up my Nova launcher settings.
Hi guy's I got a question if anyone can help me out
I'm on MHA-L29 8.0.0.360 (c567)
No custom rom but I got root with supersu
How can I install this carbon rom I try allready but twrp ask me on what partition I want to install the .img file and It shows bunch of it
I'm running twrp latest by pretoriano
Thank you very much guys
Caguayote said:
Hi guy's I got a question if anyone can help me out
I'm on MHA-L29 8.0.0.360 (c567)
No custom rom but I got root with supersu
How can I install this carbon rom I try allready but twrp ask me on what partition I want to install the .img file and It shows bunch of it
I'm running twrp latest by pretoriano
Thank you very much guys
Click to expand...
Click to collapse
Restore your stock ramdisk and recovery partitions. (I'd actually start with a full restore to stock firmware first: get your vendor patches in order. 8.0.0.369 is available for most phones on c567, 370 might be available.)
Factory reset using stock recovery. Flash with fastboot. Magisk for root & SafetyNet.
irony_delerium said:
Restore your stock ramdisk and recovery partitions. (I'd actually start with a full restore to stock firmware first: get your vendor patches in order. 8.0.0.369 is available for most phones on c567, 370 might be available.)
Factory reset using stock recovery. Flash with fastboot. Magisk for root & SafetyNet.
Click to expand...
Click to collapse
do you know where can i download the stock ramdisk and recovery partition for mate 9 i was running 8.0.0.369 sorry i put 360
im stuck on twrp splash screen and i cant go to access my backup file to restore and i only access fastboot mode
but my phone says unlocked then frp says lock thanks for all your help
Now i'm using android 7.0. based rom aur 2.3, if i want to install that stock android rom, do i have to flash android 8 based twrp?