i have new recovery twrp(decryption support) installed and also patched boot.img with root, now i want to flash update_data_hw_full package and an ota update.zip package, which is stock firmware. can i flash it with patched boot? or do i need to flash stock boot.img first? and will flashing this firmware with twrp work? bcz it is an OTA package
No, TWRP can't flash stock Huawei packages, you'll need the stock recovery.
You may also need stock boot.img, not sure, I don't use it.
Once i flashed those nougat files with twrp and its all working good. But thats an old ver of MM twrp..
Haven't tried the new one.
SolarisSixth said:
No, TWRP can't flash stock Huawei packages, you'll need the stock recovery.
You may also need stock boot.img, not sure, I don't use it.
Click to expand...
Click to collapse
with stock recovery how can i flash an update.zip package?? bcz in dload it uses update.app
faizalotai said:
Once i flashed those nougat files with twrp and its all working good. But thats an old ver of MM twrp..
Haven't tried the new one.
Click to expand...
Click to collapse
i will try and post what ever i get, but really dnt wanna go back to MM and then come downloading to nougat its a hell long process.
Related
i have custom ROM with unlocked bootloader and rooted , how i can revert back to stock motorola ?
i have global version XT1032 .
Flash stock rom by lost101, http://forum.xda-developers.com/showthread.php?t=2854688 then flash stock recovery so you can get OTA
eddydc1 said:
Flash stock rom by lost101, http://forum.xda-developers.com/showthread.php?t=2854688 then flash stock recovery so you can get OTA
Click to expand...
Click to collapse
would that work? not necessary to flash original firmware via fastboot?
arya5 said:
would that work? not necessary to flash original firmware via fastboot?
Click to expand...
Click to collapse
Well, OP says "All of these ROMs will get future OTA updates as released by Motorola."
I have 210.12.40.falcon_umts.EURetail.en.EU ROM installed on my XT1032.
I also have TWRP recovery. I want to install Lollipop OTA so I have to get back to stock recovery.
I tried to flash recovery.img from https://mega.co.nz/#!HRpRTR4Q!GNPL3a1Syc8vwholky1wNNfX4rQ-24swytFM6cUVowM via fastboot but it's not working (red triangle). How to do that?
You need to flash back to stock 4.4.4 with no root and stock recovey, update Motorola Services app in the play store, then check for OTA updates..
audit13 said:
You need to flash back to stock 4.4.4 with no root and stock recovey, update Motorola Services app in the play store, then check for OTA updates..
Click to expand...
Click to collapse
Please read before answering.
I have stock 4.4.4 and I have OTA avaliable. But I can't install it with custom recovery.
My problem is only that I can't install stock recovery.
Did you unzip the file and try to flash the stock recovery using fastboot?
You did not mention whether your ROM was rooted, had any apps removed, etc,. and this is why I suggest re-flashing to make sure you have a completely stock ROM.
You have the EU retail ROM on your phone and the link is for the Retail GB. Not sure if both ROMs use the same recovery and partition layout.
I've just finished flashing stock recovery, this is the guide I used:
http://forum.xda-developers.com/moto-g/general/gpe-ota-lrx21z-5-0-1-xt1033-xt1032-t2969847
You're going to have to download mfastbootv2, Minimal ADB and Fastboot and the batch files, then mfastboot flash recovery recovery.img and I guess you're done.
Though I've did the whole tutorial, so I'm not sure if that one command is enough if you only want to flash recovery, but I think that's all you need.
Need 5.0.1 stock recovery to update to 5.1 ota
Hello, does anyone have the stock recovery image for 5.0.1/LRX21Z.M002? I have been searching google for hours to try and find this image. Any help would be appreciated.
Pr3no said:
I've just finished flashing stock recovery, this is the guide I used:
http://forum.xda-developers.com/moto-g/general/gpe-ota-lrx21z-5-0-1-xt1033-xt1032-t2969847
You're going to have to download mfastbootv2, Minimal ADB and Fastboot and the batch files, then mfastboot flash recovery recovery.img and I guess you're done.
Though I've did the whole tutorial, so I'm not sure if that one command is enough if you only want to flash recovery, but I think that's all you need.
Click to expand...
Click to collapse
audit13 said:
Did you unzip the file and try to flash the stock recovery using fastboot?
You did not mention whether your ROM was rooted, had any apps removed, etc,. and this is why I suggest re-flashing to make sure you have a completely stock ROM.
You have the EU retail ROM on your phone and the link is for the Retail GB. Not sure if both ROMs use the same recovery and partition layout.
Click to expand...
Click to collapse
So, for last 2 hours I was trying to flash stock recovery. I tried to flash different ROMs, wiped data and system several times. Nothing seemed to work. After flashing recovery.img from any stock firmware package there always was red triangle and it didn't work. All custom recoveries works.
So since I've already had my data wiped, I just flashed Lollipop with fastboot and it works well. But still doesn't have stock recovery.
Anyone can suggest what upgrade I should choose and which one is more stable? I want to root my phone as well so if anyone with the official Marshmallow update can give me a good reason to upgrade from 5.0.2 I'd really appreciate it.
Besides sense 7 is there anything else to look forward to in Marshmallow for HTC?
Also anyone with the Marshmallow GPE Rom or Viper M8 please share your experiences with the roms.
For the first time I'm having trouble deciding what to flash on my E8 thanks to all the devs!
I tried everything, and - offical 6.0.1 is better choise. There is best camera. They really updated drivers or libs, i don't know. Stock ROM + custom kernel it's always good. All custom ROM's here is based on older firmwares.
Jestercore said:
I tried everything, and - offical 6.0.1 is better choise. There is best camera. They really updated drivers or libs, i don't know. Stock ROM + custom kernel it's always good. All custom ROM's here is based on older firmwares.
Click to expand...
Click to collapse
How did you Root and get the custom kernel (without the system write protection) on Marshmallow? Same as how you'd do it on 5.0.x?
Yes, my 6.0.1 rooted, but custom kernel not exist this time. We waiting.
Jestercore said:
Yes, my 6.0.1 rooted, but custom kernel not exist this time. We waiting.
Click to expand...
Click to collapse
Would you please explain how to root your E8 6.0.1? I prefer to get just root without installing custom recovery, so I can backup stock recovery using flashify just in case for future OTA.
i dont know about way like this. In future u can extract stock recovery from OTA package, that u gonna receive. This always works.
I've flashed supersu 2.67 via recovery.
Jestercore said:
i dont know about way like this. In future u can extract stock recovery from OTA package, that u gonna receive. This always works.
I've flashed supersu 2.67 via recovery.
Click to expand...
Click to collapse
I received OTA and installed it directly. I forgot to backup the OTA file first so I don't have a chance anymore to extract the stock recovery. I tried to downgrade to 5.02 but always failed.
wildanw2 said:
I received OTA and installed it directly. I forgot to backup the OTA file first so I don't have a chance anymore to extract the stock recovery. I tried to downgrade to 5.02 but always failed.
Click to expand...
Click to collapse
don't worry, u can use future OTA's recovery to install the same OTA
Downgrading is easy. You need to flash TWRP recovery via fastboot. Do not need full root. ERASE everying. The flash lollipop RUU via external SD.
parthasd said:
Downgrading is easy. You need to flash TWRP recovery via fastboot. Do not need full root. ERASE everying. The flash lollipop RUU via external SD.
Click to expand...
Click to collapse
I have M8SW and it is S-ON, it currently running BinDroid ONE V1.3.0 Android 4.4.4. I'm thinking about trying marshmallow ROM but I've read that is hard to downgrade to Kitkat once the firmware has been upgraded to higher version. But you said above it is easy to downgrade, can you please provide me with the steps to downgrade from marshmallow to kitkat rom. Thanks
Also, how can I tell what were the previous versions of Android that my phone had (STOCK)?
For example: there were several 5.1.1 versions or 5.0. versions - how do I know which one do I need?
Thanks.
The easiest way to have a routed rom would be to flash a stock rom from Google, flash twrp, and flash supersu from twrp.
audit13 said:
The easiest way to have a routed rom would be to flash a stock rom from Google, flash twrp, and flash supersu from twrp.
Click to expand...
Click to collapse
Sorry if I didn't explain myself - my phone is rooted and I have a custom ROM. What I want to do is to go back to stock ROM but keep it rooted.
Thanks.
Flash a stock rom, then just root the stock rom. There is no other way unless you flash a stock pre-rooted rom.
audit13 said:
Flash a stock rom, then just root the stock rom. There is no other way unless you flash a stock pre-rooted rom.
Click to expand...
Click to collapse
So you can't keep it rooted while flashing stock?
And how do you know which versions are for your phone (if I don't want to go back to the latest Marshmallow for example)?
You can only keep root when flashing stock if you find a prerooted stock image.
Google search for nexus factory images.
audit13 said:
You can only keep root when flashing stock if you find a prerooted stock image.
Google search for nexus factory images.
Click to expand...
Click to collapse
Yes, I know that I need to Google for factory image, but there are several images with the same release. For example, there are three 5.1.1. (LMY48B, LMY48I and LMY48M). Same with 6.0.0. and 4 X 6.0.1 version. How do you know which one is for my device?
Thanks.
Any stock image for hammerhead will work on a hammerhead device. The reason it will delete root is you will have to flash system, and unless the system image you flash is prerooted, no more root.
wangdaning said:
Any stock image for hammerhead will work on a hammerhead device. The reason it will delete root is you will have to flash system, and unless the system image you flash is prerooted, no more root.
Click to expand...
Click to collapse
Thanks!
Just trying to understand that difference between the different versions, or are these simply system updates, from XXX29K to XXX29S for example?
Changes in the android version 5.0->5.1->6.0 are fairly large system updates. Within 5.1.1 they are security patches.
If you have a rooted phone and talk about flashing, you should know this. Else you are a menace to your phone...
Root is a system modification - if you delete or reinstall the System partition, you'll lose root. But re-root is easy.
I recommend to read tutorials and get some knowledge before trying to root, flash or before asking those questions, where Senior xda-members just shake their heads.
The simple way to do what you seem to want is to back up all your important stuff (photos, etc.), install MMB29V (the latest March 1st 6.0.1 security version), install TWRP 3.0.0.0, and from TWRP flash SuperSU v2.70. It will take slightly longer than it's taken me to type this, but not much...
After that, when a new monthly security version comes out, flash system.img, boot.img & radio.img, and repeat the TWRP & SuperSU steps. No data loss.
Just the stock kernel that I can flash in twrp because white pug kernel currently has issues with as cards.
colliflower1107 said:
Just the stock kernel that I can flash in twrp because white pug kernel currently has issues with as cards.
Click to expand...
Click to collapse
Flashing stock boot.img should do the job.
Ok, where can I find this for B389?
colliflower1107 said:
Ok, where can I find this for B389?
Click to expand...
Click to collapse
Download the firmware finder and search for b389 and download update.zip and extract it using huawei update extractor and extract boot.img and flash the image using twrp.
Or ask some one give the boot backup
i did flash the stock boot.img but it gets into bootloop