Related
This is a TWRP Backup of the Middle East Marshmallow OTA (B511) for TL 10 International Version:
Link:https://mega.nz/#F!i1QkjLrI
Decription key:!Rj6Iw_--xg8vABPi76NxeQ
Place the file within TWRP>BACKUPS folder in your SD card.
I did a factory reset via TWRP pior to backing-up and did not notice some of the apps (Most Google Apps and some stock Huawei apps like Compass, Mirror, etc.) went missing. So after restoring the back-up, you may restore those missing apps by doing the following:
1.) Download the Stock MM recovery
2.) Boot to fastboot mode then flash the stock recovery.
3.) After rebooting phone boot to stock recovery mode.
4.) On stock recovery choose "Wipe Data/Factory Reset". Once back on the phone will regain all lost apps/icons
Hi! Link mega crashed! ?
Enviado desde mi JAZZ
link not working please check before post
Link works.It must enter the decryption key: !Rj6Iw_--xg8vABPi76NxeQ
Hi is only for TL10?
tried to roll back from Marshmallow B511 but you fail, try my method here
http://forum.xda-developers.com/mate-7/general/tried-to-roll-b511-to-b326-fail-try-t3302479
blitzkriegger said:
This is a TWRP Backup of the Middle East Marshmallow OTA (B511) for TL 10 International Version:
Link:https://mega.nz/#F!i1QkjLrI
Decription key:!Rj6Iw_--xg8vABPi76NxeQ
Place the file within TWRP>BACKUPS folder in your SD card.
I did a factory reset via TWRP pior to backing-up and did not notice some of the apps (Most Google Apps and some stock Huawei apps like Compass, Mirror, etc.) went missing. So after restoring the back-up, you may restore those missing apps by doing the following:
1.) Download the Stock MM recovery
2.) Boot to fastboot mode then flash the stock recovery.
3.) After rebooting phone boot to stock recovery mode.
4.) On stock recovery choose "Wipe Data/Factory Reset". Once back on the phone will regain all lost apps/icons
Click to expand...
Click to collapse
Work very fine TL09
I tried several times on TL10 international version, but when rebooting system always got stucked on huawei logo screen. Even waited long periods with no effect.
Any hint?
pasil.pt said:
I tried several times on TL10 international version, but when rebooting system always got stucked on huawei logo screen. Even waited long periods with no effect.
Any hint?
Click to expand...
Click to collapse
did it work for you, because i tried it and had the same results, if it didn't, would you mind telling me what you did to make your phone work again please
---------- Post added at 02:34 PM ---------- Previous post was at 02:18 PM ----------
pasil.pt said:
I tried several times on TL10 international version, but when rebooting system always got stucked on huawei logo screen. Even waited long periods with no effect.
Any hint?
Click to expand...
Click to collapse
did it work for you, because i tried it and had the same results, if it didn't, would you mind telling me what you did to make your phone work again please
nozeback said:
did it work for you, because i tried it and had the same results, if it didn't, would you mind telling me what you did to make your phone work again please
---------- Post added at 02:34 PM ---------- Previous post was at 02:18 PM ----------
did it work for you, because i tried it and had the same results, if it didn't, would you mind telling me what you did to make your phone work again please
Click to expand...
Click to collapse
I can't remember well but i think I went into recovery (TWRP) to restore a backup
If you cannot go into twrp recovery either to restore a bckp or to flash another rom you need to go into the fastboot procedure, flashing img files from PC. But yoy can see this procedures on other threads
urgently need Stock MM recovery,plz
hi,thanks for the guide,I urgently need Stock MM recovery and I cant Find it,unfortunately my device has no recovery and most unfortunately it was on MM,After boot loader unlock, I flashed another recovery which seems to be incompatible and now device has no recovery,tried more than 10 recovery but none leave me a chance,please upload a stock MM recovery if possible.
Here
https://mega.nz/#!w15xjZxL!0-alMyU4RgsxQ6K6FjOPZna-piQLXODLE0QarKtdVCg
Send from ?
Looking for the stock browser apk from b331. Any chance someone has a link
ogre del said:
Looking for the stock browser apk from b331. Any chance someone has a link
Click to expand...
Click to collapse
Here https://mega.nz/#!Z9gjRJpR!iJmlBWIFRLhhDRIFu3--FoxkAj6Pc6wZCuajDZ7WKZw
Send from ?
New link thanks to @Blue.Ember
https://mega.nz/#!e1BmGBKY!xoGZ2s-AbUyg2khj98e-veul95_KU0esstyK4SmqtiM
Send from ?
Owners of the factory-unlocked, dual SIM Snapdragon variant labelled as 'a5_dug' in the bootloader mode, will be pleased to know that the update is now available from your stock Lollipop ROM.
Before you begin
Preparation
If you are not using the official update tool, and wish to use OTA files uploaded here, reboot your phone in to its bootloader, and ensure that a5_dug is displayed. This update may not apply to other models, regardless of whether they are dual SIM or not. It most certainly will not apply to the 816G model which uses a MediaTek chipset.
You must ensure that you have 2GB free on the internal eMMC storage before continuing if you wish to update using the stock update tool. The update tool does not download to the microSD card.
The update does not update, unfortunately, the HTC Sense user interface. It uses the same Sense version as Lollipop did, with some minor changes.
Update contents, simplified
Android 6.0.0
HTC Sense 6.0
Additional Google features
Installation
For phones running a stock ROM earlier than Lollipop 5.0.2
Please update your phone to 5.0.2 and proceed to follow the instructions below if you wish to update through the official update tool.
For phones running stock Lollipop 5.0.2
The update is in two parts for phones running stock Lollipop 5.0.2. The first part is less than 60MB (typically), and prepares the phone for the installation of the second, main part, which is around 1.1GB.
Open the 'Settings' app.
Scroll down and select 'About'.
Tap 'System update'
Agree to download the update by pressing 'OK'.
Once downloaded, 'System update downloaded' appears in the notification tray.
Tap this, and tap 'Install'.
Then repeat for the second part.
For phones running custom software
(investigating)
I just got HTC Mail update only!!!
The update could be available around 01 - 02 week, hope so
@gwhite5 seriously!??? No Sense 7 ?!!!
Its great news but plz provide me with the marshmallow ROM for dual sim models with root capabilities! ? thanks in advance
Any news about the a5_dwg models ?
I have A5 Dug (816w).
After OTA update I have Android 6 with Sense 7, not Sense 6...
For devices on custom recovery
I am running official ROM but on custom recovery TWRP and rooted. My question is will this update will be installable on this setup?( Haven't tried yet)
Also I tried rolling back to stock recovery but I have removed few system app in past without backup is there any way to get the apks for them . I got error for HTC Car app . Also will need help on how to install it as a system app, cuz its not avaialble on "/system/priv-app/Automotive_Home/Automotive_Home.apk" .
Any help is appriciated.
TIA
I finally managed to reinstall the automotive_home.apk as system app, i moved back to stock recovery and then tried the OTA update once again still getting the same error " unexpected content" on that path.
could someone please make a twrp backup of the android 6 on the a5_dug ?
@mshtob its already done bro check updates we are still waiting for a5_dwg
pratik14994 said:
@mshtob its already done bro check updates we are still waiting for a5_dwg
Click to expand...
Click to collapse
No sorry I meant a twrp backup because I have twrp and cyanogen mod I was hoping someone could have a twrp backup of stock marshmallow rom so I can restore it
I have A5_DUG (CID: HTC__622 / Asia_HK) and I didn't get the update yet...
Is it because it's rooted with many changes? I didn't have this problem with the previous update so is it just not released yet for my CID?
EDIT: I noticed that version-main is blank in the bootloader
Hi guys
I have desire 816 a5 dug..and i have an update to marshmallow in tow step.
I change my custom recovery to stock and i done full unroot.
When i tap to first step(54mg) after setup and reastart, my phone wait on white screen with htc logo for to long..i reastart again my phone but nothing will happen.
And i have to return my twrp back up to be true.
What should i do?
Thanks
THE_MOJTABA said:
Hi guys
I have desire 816 a5 dug..and i have an update to marshmallow in tow step.
I change my custom recovery to stock and i done full unroot.
When i tap to first step(54mg) after setup and reastart, my phone wait on white screen with htc logo for to long..i reastart again my phone but nothing will happen.
And i have to return my twrp back up to be true.
What should i do?
Thanks
Click to expand...
Click to collapse
you can use this MM backup
http://forum.xda-developers.com/desire-816/general/twrp-backup-htc-desire-816-a5dug-dual-t3336060
Extract recovery from the OTA file.
It happened to me and I extracted the recovery image from the downloaded OTA update.
copied the OTA zip file to computer. unzipped and extracted the firmware.zip file from it. Flashed recovery again to this new recovery (basically both are stock). This worked for me and i can go till the recovery screen.
---------- Post added at 08:05 PM ---------- Previous post was at 08:04 PM ----------
THE_MOJTABA said:
Hi guys
I have desire 816 a5 dug..and i have an update to marshmallow in tow step.
I change my custom recovery to stock and i done full unroot.
When i tap to first step(54mg) after setup and reastart, my phone wait on white screen with htc logo for to long..i reastart again my phone but nothing will happen.
And i have to return my twrp back up to be true.
What should i do?
Thanks
Click to expand...
Click to collapse
It happened to me and I extracted the recovery image from the downloaded OTA update.
copied the OTA zip file to computer. unzipped and extracted the firmware.zip file from it. Flashed recovery again to this new recovery (basically both are stock). This worked for me and i can go till the recovery screen.
need lolipop recovery guys
Tnx for your help
kyyubikiller said:
It happened to me and I extracted the recovery image from the downloaded OTA update.
copied the OTA zip file to computer. unzipped and extracted the firmware.zip file from it. Flashed recovery again to this new recovery (basically both are stock). This worked for me and i can go till the recovery screen.
---------- Post added at 08:05 PM ---------- Previous post was at 08:04 PM ----------
It happened to me and I extracted the recovery image from the downloaded OTA update.
copied the OTA zip file to computer. unzipped and extracted the firmware.zip file from it. Flashed recovery again to this new recovery (basically both are stock). This worked for me and i can go till the recovery screen.
Click to expand...
Click to collapse
I used recovery from "firmware.zip" file but did'nt work..after setup and reastart, my phone stoped on whit screen whit htc logo...i dont now what can i do anymore.
---------- Post added at 02:11 AM ---------- Previous post was at 02:06 AM ----------
Roberto Nigel said:
you can use this MM backup
http://forum.xda-developers.com/desire-816/general/twrp-backup-htc-desire-816-a5dug-dual-t3336060
Click to expand...
Click to collapse
Tnx but this backup did'nt work too
THE_MOJTABA said:
I used recovery from "firmware.zip" file but did'nt work..after setup and reastart, my phone stoped on whit screen whit htc logo...i dont now what can i do anymore.
---------- Post added at 02:11 AM ---------- Previous post was at 02:06 AM ----------
Tnx but this backup did'nt work too
Click to expand...
Click to collapse
How so? .. If you'r a5_dug it should work
tell me what have you done with it?
Roberto Nigel said:
How so? .. If you'r a5_dug it should work
tell me what have you done with it?
Click to expand...
Click to collapse
yes im sure my phone is a5_dug.
when i want to extract this back up, i see an error in end of extract process (99%). but the files will be extract correctly,apparently
i copied files to sd card and done full wipe, i restore this back up..but the process was ok until 60%, but suddenly the process will be 100% and writes successful and done. but after restart my phone stop in white screen with htc logo!
i repair the .zip back up but it dose not change.
i think the .zip file is broken-down.. i downloaded it with download manager.
Roberto Nigel said:
How so? .. If you'r a5_dug it should work
tell me what have you done with it?
Click to expand...
Click to collapse
fixed.. tnx a lot
the downloaded file was destroyed.
Be cautious with the latest N910TUVS2EPG2.
You might not be able to downgrade the bootloader once its updated.
If you look back at the history of builds for the N910T you will see the following:
N910TUV U2 EPE3 = 6.0.1
N910TUV U2 DOK2 = 5.1.1
N910TUV U1 COG2 = 5.0.2
Pay attention to the U1 & U2 numbers.
Notice that you can upgrade and downgrade between 6.0.1 and 5.1.1 but cannot downgrade to 5.0.1
Both 6.0.1 and 5.1.1 have U2 in their build. In the past (at least on some devices) once these numbers change is when you cannot downgrade to a different number.
So whats my point? Look at the latest build. N910TUV S2 EPG2.
"S2" This very well could mean you can not downgrade to 5.1.1 and or PE3 6.0.1.
It also could mean that there have been some other bootloader changes.
There have been some reports that some on the latest N910TUVS2EPG2 have had trouble flashing TWRP.
Disclaimer: This info is not to be taken as golden fact. I'm just providing it so people can look out and be aware this has been the case in the past.
Since a lot of this information has not been confirmed and will not be confirmed by Samsung we can only go by past situations.
This has been indeed the case on both the Note 4 and the Galaxy Tab S2
To everyone that has indeed updated to this new Firmware version (N910TUVS2EPG2) please post any experiences from it.
Any problems? Any confirmed known changes. Anything.
Thanks!
I updated, and I was able to install twrp, root, and xposed. However, I have heard reports that twrp doesn't work for some people.
I updated yesterday. Took a couple of tries, but I got it to install twrp & supersu. Currently rooted on epg2
Can anyone point me in the direction of installing xposed on 6.0.1?
N910T here. Updated to EPG2 and I was able flash twrp, supersu v2.76 and custom ROM. I haven't tried rolling back to 5.1.1 bootloader yet.
Sent from my SM-N910T3 using Tapatalk
ayeitschris said:
N910T here. Updated to EPG2 and I was able flash twrp, supersu v2.76 and custom ROM. I haven't tried rolling back to 5.1.1 bootloader yet.
Sent from my SM-N910T3 using Tapatalk
Click to expand...
Click to collapse
Chocu1a said:
I updated yesterday. Took a couple of tries, but I got it to install twrp & supersu. Currently rooted on epg2
Can anyone point me in the direction of installing xposed on 6.0.1?
Click to expand...
Click to collapse
Any chance one of you could try rolling back to 5.1.1 or even PE3?
Regarding Xposed it should be the same one as PE3.
http://forum.xda-developers.com/note-4-tmobile/general/pe3-xposed-n910t-t3-marshmallow-t3406950
Also, How is PG2 running for you both? Anything worth mentioning?
DeeXii said:
Any chance one of you could try rolling back to 5.1.1 or even PE3?
Regarding Xposed it should be the same one as PE3.
http://forum.xda-developers.com/note-4-tmobile/general/pe3-xposed-n910t-t3-marshmallow-t3406950
Also, How is PG2 running for you both? Anything worth mentioning?
Click to expand...
Click to collapse
I upgraded to the new MM and everything its ok, twrp, (your root systemless) is ok and all is ok! let me rolling back to LP now, gime a 20 or 30 min...:good:
wilsonmd said:
I upgraded to the new MM and everything its ok, twrp, (your root systemless) is ok and all is ok! let me rolling back to LP now, gime a 20 or 30 min...:good:
Click to expand...
Click to collapse
Any update to this?
DeeXii said:
Any update to this?
Click to expand...
Click to collapse
Odined stock EPG2 tar, SuperSu systemmode, Xposed alt 86 wanam, TWRP 3.0.2-0, no issues. Great battery, runs smoother, no hiccups. :good:
DeeXii said:
Any update to this?
Click to expand...
Click to collapse
via Odin and i could not let me try flashing the LP bootloader and flash any room ......
How Downgrade your T-Mobile Note 4 (N910t) from MM (any version) to DOK2 Lollipop!
DeeXii said:
Any update to this?
Click to expand...
Click to collapse
IM NOT RESPONSABLE IF A HEART ATTACK OCCUR OR YOUR PHONE BLOW UP WITH ALL THE ROOF :silly:
IF YOU HAVE YOUR PHONE IN MM PG2 STOCK rooted with super SU systemless and last TWRP instaled (like me) YOU CAN DOWNGRADE TO D0K2 LOLLIPOP :
******REMEMBER Disable Reactivation lock (see picture below) and activate USB debuggin, Before DO this procedure!!*******
1-Download the DOK2 BOOTLOADER HERE https://www.androidfilehost.com/?fid=24269982087008410 and the D0K2 modem here: https://www.androidfilehost.com/?fid=24269982087008409 ( i did use 3.0.9 Odin) >>>>>>>>>thanks to @xoxo_xdagirl91 for post the links!
2- Download The 5.1.1 rom here: http://forum.xda-developers.com/note-4-tmobile/development/rom-maximum-ovrdrive-v15-1-1-t3196653 its an awsome rom by @OvrDriVE and so Thanks for that!
3-Put the ovrDrive 5.1.1 rom into the external sd card together with the upgrade. (because need erase all in the internal memory, remember, make a back up of your data in the phone or in the internal memory if you want).
4-now GO to your TWRP and wipe cache-dalvik-system-data-INTERNALmemory x3 ..........DONT TOUCH YOUR EXTERNAL SD, REMEMBER THE OVRDRIVE 5.1.1 ROM IS THERE!
******REMEMBER WHEN YOU ERASE YOUR INTERNAL MEMORY JUST REBOOT AGAIN IN RECOVERY, each time you erase yor internal memory, when reboot in TWRP you see the warning and said that you need to click in "never show this screen during boot again" just click there and swipe to allow Modifications or the stock recovery will rewrite again. TURN OF YOUR PHONE!
5-GO TO DOWNLOAD MODE TO USE Odin and flash the 5.1.1 bootloader FIRST, WHEN FINISH, Flash the modem ..... REMEMBER: put the bootloader in the BL section FIRST AND FLASH & FOLLOWING THE modem in the CP section of odin
6- When finish the step 5, go to your recovery TWRP>install>go to ext sd>flash the ROM first, when finish, wipe dalvik, cache and reboot again in TWRP
7- Just flash the othe part of the rom........the upgrade zip file, when finish just reboot the system aaaaaaaand
WALAAAAAHHHHHH!!!!!!
I DID IT EXACTLY AS DIRECTED AND I HAVE A CLEAN OVRdrive
rooted rom in 5.1.1. Now you can flash via ODIN the original firmware on 5.1.1:good::good:
Just wanted to share my experience for posterity. Here's what I did (and promptly undid). I don't know much about anything, so feel free to laugh and/or point out where I went wrong:
1. Installed the stock N910TUVS2EPG2 from Odin on my 910T.
2. Flashed SuperSU System Mode (which is wrong, I think...should have done systemless, right?)
3. Got the scary yellow "set warranty bit kernel" message and nothing else on the screen.
4. After a couple of attempted reboots, I got the message saying something to the effect of unauthorized software being installed and I'd have to send it in to get it repaired.
5. After a couple of reboots (pulled the battery and tried turning it on again a couple of time), it went through a full boot. After the boot was complete, I got another message within the OS about unauthorized software.
6. Opened SuperSU, unrooted and restored stock recovery.
Everything seems fine now, like nothing ever happened. Calls, data, wifi, and all that are working. I'll wait for the experts to chime in before I attempt this again. I'm just happy it works...at least as far as I can tell.
mykos said:
Just wanted to share my experience for posterity. Here's what I did (and promptly undid). I don't know much about anything, so feel free to laugh and/or point out where I went wrong:
1. Installed the stock N910TUVS2EPG2 from Odin on my 910T.
2. Flashed SuperSU System Mode (which is wrong, I think...should have done systemless, right?)
3. Got the scary yellow "set warranty bit kernel" message and nothing else on the screen.
4. After a couple of attempted reboots, I got the message saying something to the effect of unauthorized software being installed and I'd have to send it in to get it repaired.
5. After a couple of reboots (pulled the battery and tried turning it on again a couple of time), it went through a full boot. After the boot was complete, I got another message within the OS about unauthorized software.
6. Opened SuperSU, unrooted and restored stock recovery.
Everything seems fine now, like nothing ever happened. Calls, data, wifi, and all that are working. I'll wait for the experts to chime in before I attempt this again. I'm just happy it works...at least as far as I can tell.
Click to expand...
Click to collapse
Those scary red and yellow warnings are standard. Just lets you know the phone has been modified, nothing to worry about. To keep it simple, you can use either systemmode or systemless. And of course you will get a message saying the phone is using an unauthorized software, because you just flashed a custom ROM. Haha. That only pops up when you check for system updates.
xdapowerapps said:
Those scary red and yellow warnings are standard. Just lets you know the phone has been modified, nothing to worry about. To keep it simple, you can use either systemmode or systemless. And of course you will get a message saying the phone is using an unauthorized software, because you just flashed a custom ROM. Haha. That only pops up when you check for system updates.
Click to expand...
Click to collapse
Thanks for the response! I gave it another shot this morning.
Used CF Auto Root, installed TWRP, no issues. I was having random restarts on non-stock roms, but none on this one even with rigorous testing.
xdapowerapps said:
Those scary red and yellow warnings are standard. Just lets you know the phone has been modified, nothing to worry about. To keep it simple, you can use either systemmode or systemless. And of course you will get a message saying the phone is using an unauthorized software, because you just flashed a custom ROM. Haha. That only pops up when you check for system updates.
Click to expand...
Click to collapse
They say that this compilation can not Downgrade "N910TUVS2EPG2" to 5.1.1 o another 6.0.1 compilation
IS TRUE..!!
mykos said:
Thanks for the response! I gave it another shot this morning.
Used CF Auto Root, installed TWRP, no issues. I was having random restarts on non-stock roms, but none on this one even with rigorous testing.
Click to expand...
Click to collapse
Glad that everything is running smooth for you! I normally like to run stock, install TWRP, root, and then tweak whatever I don't like. Right now I'm running an S7E Port located HERE. Process requires a little work; 1st) flash the ROM, 2) flash kernel, 3) flash data fix, 4) ??? , 5) profit. :laugh:
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
kiikez said:
They say that this compilation can not Downgrade "N910TUVS2EPG2" to 5.1.1 o another 6.0.1 compilation
IS TRUE..!!
Click to expand...
Click to collapse
That is correct; presently you cannot downgrade from EPG2 to a lower version due to security policy changes. Maybe there will be a workaround soon; however, I have 0 issues on EPG2. :good:
xdapowerapps said:
Glad that everything is running smooth for you! I normally like to run stock, install TWRP, root, and then tweak whatever I don't like. Right now I'm running an S7E Port located HERE. Process requires a little work; 1st) flash the ROM, 2) flash kernel, 3) flash data fix, 4) ??? , 5) profit. :laugh:
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
That is correct; presently you cannot downgrade from EPG2 to a lower version due to security policy changes. Maybe there will be a workaround soon; however, I have 0 issues on EPG2. :good:
Click to expand...
Click to collapse
Conflicting reports on here. I haven't tried this myself yet but THIS post states a successful downgrade. YMMV.
mykos said:
Just wanted to share my experience for posterity. Here's what I did (and promptly undid). I don't know much about anything, so feel free to laugh and/or point out where I went wrong:
1. Installed the stock N910TUVS2EPG2 from Odin on my 910T.
2. Flashed SuperSU System Mode (which is wrong, I think...should have done systemless, right?)
3. Got the scary yellow "set warranty bit kernel" message and nothing else on the screen.
4. After a couple of attempted reboots, I got the message saying something to the effect of unauthorized software being installed and I'd have to send it in to get it repaired.
5. After a couple of reboots (pulled the battery and tried turning it on again a couple of time), it went through a full boot. After the boot was complete, I got another message within the OS about unauthorized software.
6. Opened SuperSU, unrooted and restored stock recovery.
Everything seems fine now, like nothing ever happened. Calls, data, wifi, and all that are working. I'll wait for the experts to chime in before I attempt this again. I'm just happy it works...at least as far as I can tell.
Click to expand...
Click to collapse
how did you flashed the super su systemless?
Cannot root or odin twrp after latest (pg2) update. Odin to pe2 and everything is back to normal.
xdapowerapps said:
Glad that everything is running smooth for you! I normally like to run stock, install TWRP, root, and then tweak whatever I don't like. Right now I'm running an S7E Port located HERE. Process requires a little work; 1st) flash the ROM, 2) flash kernel, 3) flash data fix, 4) ??? , 5) profit. :laugh:
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
That is correct; presently you cannot downgrade from EPG2 to a lower version due to security policy changes. Maybe there will be a workaround soon; however, I have 0 issues on EPG2. :good:
Click to expand...
Click to collapse
Could you list the exact steps. I would like to try that ROM as well, considering we don't have any MM ports for our T-Mo Note 4. How is it working so far?
Thanks
krishelnino said:
Could you list the exact steps. I would like to try that ROM as well, considering we don't have any MM ports for our T-Mo Note 4. How is it working so far?
Thanks
Click to expand...
Click to collapse
Sure bud.
1) Download the M6 ROM from Dev-Host or from MediaFire.
Put this file in your external SD card.
2) Download the BeastMode kernel.
Put this file in your external SD card.
3) Download the Data Fix - MM_DataFixs7rebootmenu.zip.
Put this file in your external SD card.
4) Boot into recovery. Make a backup of your current ROM just in case. :fingers-crossed:
5) Go into Advanced Wipe (if you're using TWRP) and wipe dalvik, system, data, cache, internal storage (or whichever options are available in the recovery you are using).
6) Flash M6 Rom from Step 1. Do not restart.
7) Flash kernel from Step 2. Do not restart.
8) Flash data fix from Step 3.
9) Now wipe cache and dalvik cahe. Restart.
Once you restart, it will look like your phone crashed or is stuck in a bootloop, it's not. Let it sit there for about 10-15 minutes and it will boot into the setup screen. Good luck. :good:
Hello,
I need your help because I did an error while rooting my U Play.
I've successfully unlocked my bootloader, and then I flashed the twrp recovery, installed the supersu zip, and I was pretty much tired and now I'm not sure of what I've done but I'm left with a phone with access to download mode, bootloader mode and custom recovery, but no rom on the phone.
I am on a single sim europe, with Orange 1.30.89.6
I've tried to flash an europe rom but I got this message "cid mismatched", because it was a non orange rom I assume.
Now, I've no rom to flash, no backup. And no idea how to get a rom.
Can you please help me to find a rom and a guide to finish to root my phone then please ?
My girlfriend have exactly the same phone than me, stock everythning. I don't know if it is possible to "extract" her stock rom...
Strepherd said:
Hello,
I need your help because I did an error while rooting my U Play.
I've successfully unlocked my bootloader, and then I flashed the twrp recovery, installed the supersu zip, and I was pretty much tired and now I'm not sure of what I've done but I'm left with a phone with access to download mode, bootloader mode and custom recovery, but no rom on the phone.
I am on a single sim europe, with Orange 1.30.89.6
I've tried to flash an europe rom but I got this message "cid mismatched", because it was a non orange rom I assume.
Now, I've no rom to flash, no backup. And no idea how to get a rom.
Can you please help me to find a rom and a guide to finish to root my phone then please ?
My girlfriend have exactly the same phone than me, stock everythning. I don't know if it is possible to "extract" her stock rom...
Click to expand...
Click to collapse
First of all, you should do backup before flashing any third-party zip, rom etc, it is a common sense.
I'll upload a stock image backup [Orange, 1.30.89.6] for you, please flash separate .img file through TWRP recovery, you can follow this guide.
https://htcfz.wordpress.com/2018/01/22/htc-flash-rom-twrp-img/
In last, I suggest that use Magisk to get root access for HTC U Play.
---------- Post added at 07:00 PM ---------- Previous post was at 06:05 PM ----------
https://drive.google.com/open?id=1ysz6VSuYSBjKJnk9mHQSv4luBZcxpWpx
Thx, that gives me some hope that at least one can root the device.
Bought my phone in Fry's, had stock nougat. Order of events that led to my current predicament:
1. Wanted to root.
2. Installed TWRP, tried pushing supersu without a new kernel, didnt do so systemless.
3. Tried again systemless.
4. ended up in bootloader loop.
5. realized i didnt back up, so i installed this: https://forum.xda-developers.com/general/rooting-roms/real-official-stock-rom-xt1625-xt1642-t3575895
6. Driver on pc no longer recognizes phone to the point of being able to see system storage, and also cannot open TWRP anymore.
7. The link above is MM. I wanted at least Nougat, since, i got used to some features.... like being able to freaking use hands free calling via bluetooth in my cars.
8. I just want to be able to see internal storage again, and access TWRP, so i can install Lineage and get past this horrible nightmare.
You guys are awesome, I am years behind most of you when it comes to these processes, I have to read line by line what to do in these tutorials, I dont even understand half of the acronyms, or understand half of the terms.
Thanks in advance.
P.S. Just to clarify, marshmellow is working.
Wolamute said:
P.S. Just to clarify, marshmellow is working.
Click to expand...
Click to collapse
Yours really doesn't ask you to upgrade to Nougat like 10 times a day? Mine just must be pushy.
First try: Settings > About phone > system updates
If that doesn't work post what build version of MM you are now on. (also on the about phone page)
Wolamute said:
Bought my phone in Fry's, had stock nougat. Order of events that led to my current predicament:
1. Wanted to root.
2. Installed TWRP, tried pushing supersu without a new kernel, didnt do so systemless.
3. Tried again systemless.
4. ended up in bootloader loop.
5. realized i didnt back up, so i installed this: https://forum.xda-developers.com/general/rooting-roms/real-official-stock-rom-xt1625-xt1642-t3575895
6. Driver on pc no longer recognizes phone to the point of being able to see system storage, and also cannot open TWRP anymore.
7. The link above is MM. I wanted at least Nougat, since, i got used to some features.... like being able to freaking use hands free calling via bluetooth in my cars.
8. I just want to be able to see internal storage again, and access TWRP, so i can install Lineage and get past this horrible nightmare.
You guys are awesome, I am years behind most of you when it comes to these processes, I have to read line by line what to do in these tutorials, I dont even understand half of the acronyms, or understand half of the terms.
Thanks in advance.
P.S. Just to clarify, marshmellow is working.
Click to expand...
Click to collapse
Off-topic, kind of, but I'm trying to flash ANY recent version of TWRP on my XT1625. I unlocked the bootloader, but try to flashing twrp in fastboot mode always returns an error: "(bootloader) Image not signed or corrupt"
What twrp version did you use and where can I get it, please.
What twrp version did you use and where can I get it, please.
Click to expand...
Click to collapse
twrp-3.2.1-0-athene.img
from https://twrp.me/motorola/motorolamotogplus2016.html
Did you unlock your bootloader?
fastboot flashing unlock
---------- Post added at 08:16 PM ---------- Previous post was at 07:57 PM ----------
Wolamute said:
P.S. Just to clarify, marshmellow is working.
Click to expand...
Click to collapse
So I went through and fastboot flashed all those files from your link to Motorola support.
It wouldn't let me relock the bootloader with fastboot oem lock
it did lock with fastboot flashing lock
I was able to reboot, now of course with a verification error boot msg
Connected to wifi and it auto-prompted the Nougat ota update.
Just completed the Nougat install currently on build NPJ25.93-14
Maybe you just need to reflash those files from the Motorola site, and connect to wifi for the 700+MB download?
there's another security update to NPJ25.93-14-4 available after you get back to nougat. Good luck
superceege said:
twrp-3.2.1-0-athene.img
from https://twrp.me/motorola/motorolamotogplus2016.html
Did you unlock your bootloader?
---------- Post added at 08:16 PM ---------- Previous post was at 07:57 PM ----------
Click to expand...
Click to collapse
My xt1625 was boot-unlocked, and I was try the same twrp version you mentioned. I continued researching, and found that, despite the error msg, twrp was flashed correctly. I just needed to go to recovery directly from the bootloader screen. Thanks for your help.
superceege said:
Yours really doesn't ask you to upgrade to Nougat like 10 times a day? Mine just must be pushy.
First try: Settings > About phone > system updates
If that doesn't work post what build version of MM you are now on. (also on the about phone page)
Click to expand...
Click to collapse
EDIT : Ok guys i figured out what to do, the phone wasnt being detected with MTP unless i switched it to charge only, then back to MTP, now i have TWRP back on, and will be trying out lineage. Thanks for the input, it helped!
It's like i said, the one in the link, its 6.0.1. , the kernel is 3.10.84-g061c37c
No, it never pushes notifications about updates with this stock rom posted on xdad, and no, i cannot use the menus to prompt a manual update.
Like i said, i can no longer even access TWRP, my recovery screen says no command, which i can bypass by holding power and clicking volume up, then releasing power, but its not TWRP, and i cannot access internal storage to put anything on it anymore.
Wolamute said:
EDIT : Ok guys i figured out what to do, the phone wasnt being detected with MTP unless i switched it to charge only, then back to MTP, now i have TWRP back on, and will be trying out lineage. Thanks for the input, it helped!
It's like i said, the one in the link, its 6.0.1. , the kernel is 3.10.84-g061c37c
No, it never pushes notifications about updates with this stock rom posted on xdad, and no, i cannot use the menus to prompt a manual update.
Like i said, i can no longer even access TWRP, my recovery screen says no command, which i can bypass by holding power and clicking volume up, then releasing power, but its not TWRP, and i cannot access internal storage to put anything on it anymore.
Click to expand...
Click to collapse
Hmm, what 6.0.1. build do you have (if you scroll down to the bottom of Settings>About Phone, there should be an entry for Build Number)? I recall that for US devices you need to be on MPJ24.139-48/49 or MPJ24.139-64 to be eligible for the OTA update to Nougat. Any other different firmware build may not give you an update as the build's not recognised by the update server for your region/software channel.
However, as you flashed the MM firmware onto your device when you previously had Nougat, I would advise against taking the OTA update route. Depending on what version of Nougat you had before you tried to root, you may hard brick your device if you try to flash the OTA, since flashing MM firmware may not downgrade your bootloader, as such you'd be flashing an old OTA onto a newer Nougat bootloader, which is a really bad idea. If you can remember what stock firmware you had (or at least what security patch it was), we can try to locate the correct firmware for you to flash and safely get you back onto the update path.
As for the recovery, that sounds like the stock recovery you have on your device, which if you re-flashed the stock ROM, will replace TWRP. You may have to re-flash TWRP.
On a related note, on Marshmallow, you do not need to flash a custom kernel - you could flash TWRP and your choice of root manager. On stock Nougat (on the G4/Plus devices), you must flash a custom kernel, else you will likely bootloop as you experienced. Here's a rooting guide for G4/Plus Nougat devices: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
---------- Post added at 04:28 AM ---------- Previous post was at 04:23 AM ----------
Baboon_Red said:
Off-topic, kind of, but I'm trying to flash ANY recent version of TWRP on my XT1625. I unlocked the bootloader, but try to flashing twrp in fastboot mode always returns an error: "(bootloader) Image not signed or corrupt"
What twrp version did you use and where can I get it, please.
Click to expand...
Click to collapse
That error is normal, as far as I know - the TWRP image is not cryptographically signed by Motorola, so that message seems to be mainly informational and alerting you that you are flashing unsigned images in fastboot (which you are), since fastboot is mainly used to flash signed images. Once you've flashed TWRP, reboot straight to recovery to ensure the TWRP is not overwritten by the stock recovery. Afterwards, you can boot as normal.
Be careful to flash the TWRP version/architecture for what you want to do - e.g. if you wish to flash 64 bit custom ROMs, you must use a 64 bit TWRP version. Attempting to flash 64 bit custom ROMs via 32 bit TWRP may give you an error 255 otherwise.