Related
MotoFlasher Bootloader Tool!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Why use MotoFlasher?
When Motorola Make the firsts android phones, RDSLite flash all the stuff that make your phone work but now, RDSLite only works like fastboot or directly dont work on some devices.
So, if you want to flash your bootloader, you can use MotoFlasher, that simplifies the process.
Disclaimer
Bootloader Flashing is ONLY for phones that don't boot or don't pass the fastboot, don't use if your phone works.
Features
Easy Flashing With binary files included that simplifies the process.
Support Multiples Devices.
Automatic Process, With Minimal User Interaction.
Over 1K of LineCodes that protect your phone from malfunction/ bad use of qboot/qflash tool.
You Will Find Update Info, New Things and Download on my website
MotoFlasher Website
Issue Tracker (Support)
HOW TO/ FAQ/ Request
How To: Repairing a Moto Bootloader
First, Install the Special Driver (See Below).
Check your phone (on Device Manager), it shows like "Qualcomm HS-USB QDloader 9***".
Open MotoFlasher, select your device and your last android version, detect and Flash...
You Will see the fastboot screen on your device (if everything works great).
Flash the Partition Table, and Full Bootloader Again (See Below).
How to: See if I can use MotoFlasher for repair my phone:
If your device don't turn on, follow this steps:
Plug in your device and check Device Manager:
If the driver isn't installed, the device show like "qusb_bulk" or any that start like "qusb_...."
If the driver is installed, the device show like "Qualcomm HS-USB QDloader 9***".
Install the Driver
Now from 1.7.1.1 the driver is installed automatically, and you can manage on "Driver Installer" app. You didn't need to override signing anymore
TroubleShooting:
a. It hangs on:
Code:
greeting device for command mode
or
Code:
opening device: \\.\COM**
Just mantain power button until the program start working...
b. Error:
Code:
FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)
or:
Code:
FAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet)
your MBM-CI dont match with your bootloader version, use another MBM-CI version.
c. Cant flash GPT / Motoboot:
Use another firmware, try for another android versions.
d. Fastboot Error:
Code:
preflash validation failed
Try your original (or last flashed) firmware
Reserved ??
Sent from my XT1053 using XDA Premium 4 mobile app
Boss442 said:
Reserved for FAQ and step by step guide
Click to expand...
Click to collapse
What is this tool for exactly??
Gundabolu SC said:
What is this tool for exactly??
Click to expand...
Click to collapse
If your phone Die and wont turn on again, you will need this tool.
This Reflash the whole bootloader
I hope I never need this tool. However, thank you very much for this! I am sure this tool will save some users if they get into big trouble.
This tool works even whit the mismatch partition error???
conquesoextra said:
This tool works even whit the mismatch partition error???
Click to expand...
Click to collapse
This tool won't work if the bootloader is working, you will need to flash something that break it (on moto g aboot or tz partitions)
I will be the first to ask what is probably an insanely stupid question... Would this work for flashing back to previous android versions on an updated phone?
Fadelight said:
I will be the first to ask what is probably an insanely stupid question... Would this work for flashing back to previous android versions on an updated phone?
Click to expand...
Click to collapse
No, only works if "emergency flashing" is running, and only run if the bootloader is broken
Even if the bootloader is broken intentionally, it is still not possible to downgrade from what I've read. 4.4.4 is locked tight, well done Google.
Sent from my iPad using Tapatalk
Johnny Wong said:
Even if the bootloader is broken intentionally, it is still not possible to downgrade from what I've read. 4.4.4 is locked tight, well done Google.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
I think that is issue of motorola, google don't do the bootloaders and afaik, if you flash only system & boot, you can downgrade without downgrading the bootloader
Boss442 said:
I think that is issue of motorola, google don't do the bootloaders and afaik, if you flash only system & boot, you can downgrade without downgrading the bootloader
Click to expand...
Click to collapse
I meant Google locked down 4.4.4 so tight that nobody has been able to root it. If we could root 4.4.4, we would all have unlocked bootloaders thanks to Sunshine. I would expect a phone running 4.4.4 to bootloop in the best case scenario if you flash 4.4.2 system and boot files only, most likely soft brick. Which is why everyone is saying it is impossible to downgrade.
Johnny Wong said:
I meant Google locked down 4.4.4 so tight that nobody has been able to root it. If we could root 4.4.4, we would all have unlocked bootloaders thanks to Sunshine. I would expect a phone running 4.4.4 to bootloop in the best case scenario if you flash 4.4.2 system and boot files only, most likely soft brick. Which is why everyone is saying it is impossible to downgrade.
Click to expand...
Click to collapse
So, google is bad for repair an insecure issue? if you want to root, unlock the bootloader, if you can't unlock the bootloader, buy a phone capable of unlock the bootloader, or found a exploit.
Moto G with 4.4.4: Unlocked BL & Root.
PS: This tool is for people that had a bad downgrading, you can downgrade from 5.0 but only if you know how to downgrade
How did I imply that Google was bad for patching up security issues? "Well done" means good job. The only reason I posted is to save people the trouble of trying to downgrade in order to achieve root so they can unlock boot loader. Not going to happen. I'm typing this post on a Moto X Developer Edition so spare me the lecture about buying a phone that can unlock boot loader. Lol
P.s. what is the boot loader version on 5.0? Most custom Roms out now doesn't even touch the boot loader partition so not sure what you are talking about when you said you can downgrade from 5.0 back down to 4.4.4. Of course you can if you didn't flash motoboot and gpt. I used to run 4.4.4 on my Droid Maxx with 4.4 boot loader (30.B4 I think) and with that setup I could downgrade back down to 4.4. But if I flash the motoboot and gpt from 4.4.4 then I can only downgrade to 4.4.4. Make sense?
Boss442 said:
So, google is bad for repair an insecure issue? if you want to root, unlock the bootloader, if you can't unlock the bootloader, buy a phone capable of unlock the bootloader, or found a exploit.
Moto G with 4.4.4: Unlocked BL & Root.
PS: This tool is for people that had a bad downgrading, you can downgrade from 5.0 but only if you know how to downgrade
Click to expand...
Click to collapse
Johnny Wong said:
How did I imply that Google was bad for patching up security issues? "Well done" means good job. The only reason I posted is to save people the trouble of trying to downgrade in order to achieve root so they can unlock boot loader. Not going to happen. I'm typing this post on a Moto X Developer Edition so spare me the lecture about buying a phone that can unlock boot loader. Lol
P.s. what is the boot loader version on 5.0? Most custom Roms out now doesn't even touch the boot loader partition so not sure what you are talking about when you said you can downgrade from 5.0 back down to 4.4.4. Of course you can if you didn't flash motoboot and gpt. I used to run 4.4.4 on my Droid Maxx with 4.4 boot loader (30.B4 I think) and with that setup I could downgrade back down to 4.4. But if I flash the motoboot and gpt from 4.4.4 then I can only downgrade to 4.4.4. Make sense?
Click to expand...
Click to collapse
If you flash 4.4.4, you can downgrade to 4.4.3 or 4.4 flashing all exept the bootloader.
The thread isn't about downgrading, so, please, stop offtopic here
PS: the custom roms don't touch the bootloader, the only problem in 5.0 is when you flash the OTA, the zip updates the bootloader, and you can't go back the bootloader.
Boss442 said:
If you flash 4.4.4, you can downgrade to 4.4.3 or 4.4 flashing all exept the bootloader.
The thread isn't about downgrading, so, please, stop offtopic here
PS: the custom roms don't touch the bootloader, the only problem in 5.0 is when you flash the OTA, the zip updates the bootloader, and you can't go back the bootloader.
Click to expand...
Click to collapse
My original reply was to Fadelight when he asked if he could downgrade with this tool. The answer is still, NO!
I didn't realize that the lollipop OTA is out for the xt1060, oh wait, its not. So only custom Roms are available and relevant to the discussion. It would be a bad idea to take an ota without undoing all the modified stuff first. Using your example, if the boot loader is mismatched with the system, 4.4.4 boot loader and 4.4 system and you try to take an ota, it would end in failure. If you are lucky, the ota will not install, if you're not, it'll install and on reboot you have a nice brick.
The point is, most doesn't have this info and I'm trying to save them from having to do the research or the time they spend using this tool to undo their mess.
Your reply with the lecture summed it up best. Get a DE or Pure or Nexus if you want to have UBL & root. Or else, just wait till somebody comes out with an exploit. But as of now, don't waste your time. You'll know when an exploit is available long before it is released due to the amount of traffic it will receive. Sunshine for example.
Johnny Wong said:
My original reply was to Fadelight when he asked if he could downgrade with this tool. The answer is still, NO!
I didn't realize that the lollipop OTA is out for the xt1060, oh wait, its not. So only custom Roms are available and relevant to the discussion. It would be a bad idea to take an ota without undoing all the modified stuff first. Using your example, if the boot loader is mismatched with the system, 4.4.4 boot loader and 4.4 system and you try to take an ota, it would end in failure. If you are lucky, the ota will not install, if you're not, it'll install and on reboot you have a nice brick.
The point is, most doesn't have this info and I'm trying to save them from having to do the research or the time they spend using this tool to undo their mess.
Your reply with the lecture summed it up best. Get a DE or Pure or Nexus if you want to have UBL & root. Or else, just wait till somebody comes out with an exploit. But as of now, don't waste your time. You'll know when an exploit is available long before it is released due to the amount of traffic it will receive. Sunshine for example.
Click to expand...
Click to collapse
Yes, this tool don't work for downgrade, and tell him to the Moto G users, that flashed 5.0 OTA and he tried to go back bootloader to 4.4.4 and we brick their phones, only a few that only downgrade system get your phone working. The others will have to wait until a 5.0 release to add on my tool
Any idea what this error is?
OUTPUT*: C:\Python27\python.exe: can't open file 'C:\Program': [Errno 2] No such file or directory
OUTPUT*:
OUTPUT:
mjwill97 said:
Any idea what this error is?
OUTPUT*: C:\Python27\python.exe: can't open file 'C:\Program': [Errno 2] No such file or directory
OUTPUT*:
OUTPUT:
Click to expand...
Click to collapse
Install phyton, on the following route: C:\Python27\
I have update my H60-L04 (asia) to emui4.0 but bricked... i need the full rom of H60-L04C470B805 to unbrick it.. i have try the india version,B803, but it wont work... any idea for this? Thanks
roythen said:
I have update my H60-L04 (asia) to emui4.0 but bricked... i need the full rom of H60-L04C470B805 to unbrick it.. i have try the india version,B803, but it wont work... any idea for this? Thanks
Click to expand...
Click to collapse
Put the phone in fastboot mode, install CWM or TWRP, copy the backup to SD/clockworkmod/backup or SD/TWRP/backup and restore it
Choose a backup
Backup B803
https://mega.nz/#!adYwhRKI!2cSUEQYOJu_BVIFwKpA30TV3ptfsDEyx6iARlfzLhZg
Backup B805
https://yadi.sk/d/aQ2ess6WnUW3C
Backup B807
https://mega.nz/#!6dIzhTza!Zz9nPJpCZwSJ9yiLTsuI3x1tu0K6BE2HNYjX5gCxXiI
Backup B810
https://mega.nz/#!PEpQgaQZ!472a_bzdP4pACHvk77wsuDw53KmViDGWVhw-PRiZD_Q
Junior Member
12 posts
Thanks: 3
i just Downgraded from B810 to B550
1- We need to use a clean B810 (or i think any of this H60-L04C675B8007
H60-L04C675B8006
H60-L04C675B8010
H60-L04C675B8004
H60-L04C675B8003
H60-L04C151B8002
H60-L04C151B8001) it is in VERLIST.img inside UPDATE.APP
2- We need to use boot.IMG B803 - Recovery.IMG B803
3- Use the downgraded package https://drive.google.com/file/d/0ByJ...w?pref=2&pli=1
4- Use full room B550
(and may be this done because i Change location to (hw/normal) first) this link https://www.youtube.com/watch?v=36L-...ature=youtu.be
adhamamar said:
Junior Member
12 posts
Thanks: 3
i just Downgraded from B810 to B550
1- We need to use a clean B810 (or i think any of this H60-L04C675B8007
H60-L04C675B8006
H60-L04C675B8010
H60-L04C675B8004
H60-L04C675B8003
H60-L04C151B8002
H60-L04C151B8001) it is in VERLIST.img inside UPDATE.APP
2- We need to use boot.IMG B803 - Recovery.IMG B803
3- Use the downgraded package https://drive.google.com/file/d/0ByJ...w?pref=2&pli=1
4- Use full room B550
(and may be this done because i Change location to (hw/normal) first) this link https://www.youtube.com/watch?v=36L-...ature=youtu.be
Click to expand...
Click to collapse
link downgrade package not work
Steve Giordano
which build num you use?is the rom is clean?what is your location?
Billion Thanks to you guys.. my phone works again.... but dunno how to root it.... any idea.... i already a week finding solution.. and i almost plan to buy a new phone....
adhamamar said:
Steve Giordano
which build num you use?is the rom is clean?what is your location?
Click to expand...
Click to collapse
My location is Italy, My last rom is L04-C432B805 .
the rom isn't clean..
Please help! :crying:
@Steve Giordano, i try that already. and my phone got back to kitkat... you better flash to twrp recovery then flash twrp back up 803 full stock. in that senario i do wipe cache and factory reset before proceed to rollback. it really work. just make more perservance
Jessie17 said:
@Steve Giordano, i try that already. and my phone got back to kitkat... you better flash to twrp recovery then flash twrp back up 803 full stock. in that senario i do wipe cache and factory reset before proceed to rollback. it really work. just make more perservance
Click to expand...
Click to collapse
After flash twrp recovery with fastboot i can't acces on it... (button vol + and poweroff) :crying:
sorry for my bad english!
Steve Giordano said:
After flash twrp recovery with fastboot i can't acces on it... (button vol + and poweroff) :crying:
sorry for my bad english!
Click to expand...
Click to collapse
You can help users if they give the correct information!
You have unlocked the bootloader? If you have unlocked the bootloader when you put the devices into fastboot mode you get a message in red phone unlocked
If the phone not unlocked it is useless to flash the recovery or twrp
If the phone is unlocked cwm and twrp work to 100%
panamera2011 said:
You can help users if they give the correct information!
You have unlocked the bootloader? If you have unlocked the bootloader when you put the devices into fastboot mode you get a message in red phone unlocked
If the phone not unlocked it is useless to flash the recovery or twrp
If the phone is unlocked cwm and twrp work to 100%
Click to expand...
Click to collapse
My phone have Unlocked bootloader.
this is when flash TWRP recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Steve Giordano said:
link downgrade package not work
Click to expand...
Click to collapse
https://drive.google.com/file/d/0ByJkSOohdNz_NWtGclJmVTYtZUk/view?pref=2&pli=1
Steve Giordano said:
My phone have Unlocked bootloader.
this is when flash TWRP recovery.
Click to expand...
Click to collapse
Try the latest version of TWRP v4
TWRP_2.8.7.0_EN_EMUI_4.0_v4.img
https://drive.google.com/folderview...sharing&tid=0By4NGNfKPDLBQTZ2S0licGhjNmc#list
Download adb here
http://www.mediafire.com/download/o5ruw752ked884u/adb+H60.zip
Copy TWRP_2.8.7.0_EN_EMUI_4.0_v4.img in the adb folder
turn off the device and boot into fastboot mode
in adb folder run cmd.exe as administrator and type these commands:
fastboot devices
If the device is recognized correctly displaying a series of numbers
Then type
fastboot flash recovery TWRP_2.8.7.0_EN_EMUI_4.0_v4.img
fastboot reboot
Disconnect the USB cable and press volume up + power (press 8 - 10 seconds) to enter into recovery
If it works to restore a backup
panamera2011 said:
Try the latest version of TWRP v4
TWRP_2.8.7.0_EN_EMUI_4.0_v4.img
https://drive.google.com/folderview...sharing&tid=0By4NGNfKPDLBQTZ2S0licGhjNmc#list
Download adb here
http://www.mediafire.com/download/o5ruw752ked884u/adb+H60.zip
Copy TWRP_2.8.7.0_EN_EMUI_4.0_v4.img in the adb folder
turn off the device and boot into fastboot mode
in adb folder run cmd.exe as administrator and type these commands:
fastboot devices
If the device is recognized correctly displaying a series of numbers
Then type
fastboot flash recovery TWRP_2.8.7.0_EN_EMUI_4.0_v4.img
fastboot reboot
Disconnect the USB cable and press volume up + power (press 8 - 10 seconds) to enter into recovery
If it works to restore a backup
Click to expand...
Click to collapse
Ora funzionaaa va in recovery!!!!
Now work! go in recovery!
Very Thanks @panamera2011
panamera2011 said:
Put the phone in fastboot mode, install CWM or TWRP, copy the backup to SD/clockworkmod/backup or SD/TWRP/backup and restore it
Choose a backup
Backup B803
https://mega.nz/#!adYwhRKI!2cSUEQYOJu_BVIFwKpA30TV3ptfsDEyx6iARlfzLhZg
Backup B805
https://yadi.sk/d/aQ2ess6WnUW3C
Backup B807
https://mega.nz/#!6dIzhTza!Zz9nPJpCZwSJ9yiLTsuI3x1tu0K6BE2HNYjX5gCxXiI
Backup B810
https://mega.nz/#!PEpQgaQZ!472a_bzdP4pACHvk77wsuDw53KmViDGWVhw-PRiZD_Q
Click to expand...
Click to collapse
can i use any of these backups to downgrade from B805 or i have to use the b805 backup?? plz note that my phone isn't bricked, i just want to downgrade from b805 eu version and all downgrade packages are indian..
will this work??
monmon20077 said:
can i use any of these backups to downgrade from B805 or i have to use the b805 backup?? plz note that my phone isn't bricked, i just want to downgrade from b805 eu version and all downgrade packages are indian..
will this work??
Click to expand...
Click to collapse
I do not know, these backups found them on Honor 6 4pda
With google, search Honor 6 4pda, use the translator, and look if are suitable for you.
I'm sorry, but my phone is L02
monmon20077 said:
can i use any of these backups to downgrade from B805 or i have to use the b805 backup?? plz note that my phone isn't bricked, i just want to downgrade from b805 eu version and all downgrade packages are indian..
will this work??
Click to expand...
Click to collapse
it's not possible.... I'm in your situation
luis_20_p7 said:
it's not possible.... I'm in your situation
Click to expand...
Click to collapse
is there any solution for us.. when i try to upgrade to any version b806 or above it fails at 5% and when i try to downgrade using any downgrade package it fails at 36% coz all downgrade packages are indian version and my b805 is eu... i'm afraid i won't be able to upgrade my phone to the stable version of android M.. and the battery draining in b805 is very annoying... what can we do??
Hi guys, you have look here?
http://pantomath.xyz/how-to-unbrick-honor-6-from-android-m/
Sent from my H60-L02 using Tapatalk
panamera2011 said:
Hi guys, you have look here?
http://pantomath.xyz/how-to-unbrick-honor-6-from-android-m/
Sent from my H60-L02 using Tapatalk
Click to expand...
Click to collapse
i tried this methode many times.. never worked for me coz all downgrade packs in that thread are indian and my b805 version is eu... is there any other source for downgrade packs other than this site??
Hiya People,
Just wanted to share my journey and my TWRP backups with you all.
I have a M8sw (dual-SIM) mec_dugl which many thanks and :highfive: and respect to DutchDanny, I converted it to a M8sw Europe/UK version running near stock Lollipop 5.0.2 Sense 6 RUU 2.33.401.6.
When I saw the Marshmallow update, I was over the moon and decided to download it straightaway but as I had TWRP as recovery, the phone was rooted and had xposed installed, I knew I didn't have much of a chance.
So guess what? The Marshmallow update downloaded OK and then tried to go into recovery but since it was TWRP, it failed. So I took the OTA zip file from the phone's downloaded folder and extracted out the recovery.img from the firmware.zip and replaced TWRP. I then uninstalled xposed and turned off SuperSU. This time round, I go a similar message as http://forum.xda-developers.com/one-e8/help/help-htc-e8sd-mm-update-install-error-t3345406
So I decided to follow a mixture of DutchDanny's [REMODEL][S-OFF NEEDED] M8SW China Remodel to M8SW EU and yourmate's guide get OTA updates.
To cut the already long story short, I went back to L5 Stock 2.33.401.3 then use OTA updates to L5 Stock 2.33.401.6 and then finally to the part 1 of the Marshmallow update L5 Stock 2.33.401.8 and at each stage, I reflash TWRP, wipe and then backup and then reflash the OTA recovery.img in readiness for the next OTA
So I have the last Lollipop 5.0.2 Stock HTC Sense 6 Europe 2.33.401.8 factory reset TWRP backup AND Marshmallow 6.0.1 Stock HTC Sense 7 Europe 3.07.401.1 factory reset TWRP backup in all its glory with bloatware and all.
Enjoy!
I have remodeled my phone following the DutchDanny guide. I rooted the phone and installed xpose. BUT to install marshmallow I first install the lolipop RUU from hboot. then enter to system update to marshmallow without any problem. finally I flash TWRP and then flash supersu and that all for me.
bro help
i have same porblem and i kinda even forgot how to i rooted phone.. man i have rooted it before and i hate twrk recovry.. i also had super user.. and bootloader minu says s on.. i clocked super user and chose unroot and it did.. then i cant find twrk any more.. and i wanna install andriod 6 s bad please tell me how to do it
generalugh28 said:
Lollipop 5.0.2 Stock HTC Sense 6 Europe 2.33.401.8 factory reset TWRP backupAND https://drive.google.com/open?id=0B1qf0eVpKmagUENyOXFxdWgtTEU"]Marshmallow 6.0.1 Stock HTC Sense 7 Europe 3.07.401.1 factory reset TWRP backup in all its glory with bloatware and all.
Enjoy!
Click to expand...
Click to collapse
both no wifi, driver is missing, any fix? everything else works just fine.
good day sir, that is a Marshmallow TWRP backup right? if i restore the file with my M8sw (dual-SIM) mec_dugl, will it work and give me an MM firmware? coz mine just got recovery loop after i updated with MM and is it converted to EU version already? Thanks!
I have downloaded your "Marshmallow 6.0.1 Stock HTC Sense 7 Europe 3.07.401.1 factory reset TWRP backup" and recover it in twrp but after the recovery it just stuck in bootloop. What must I do to make it working?
smiter said:
both no wifi, driver is missing, any fix? everything else works just fine.
Click to expand...
Click to collapse
I also had the same problem after upgrading to MM.... my guess is that it's the kernel module for wifi which need to be updated.... seems like HTC isn't putting much effort to implement the new update...
I went back to lollipop with a twrp backup.
sanijsnj said:
I also had the same problem after upgrading to MM.... my guess is that it's the kernel module for wifi which need to be updated.... seems like HTC isn't putting much effort to implement the new update...
I went back to lollipop with a twrp backup.
Click to expand...
Click to collapse
how to install his file? I have downloaded his "Marshmallow 6.0.1 Stock HTC Sense 7 Europe 3.07.401.1 factory reset TWRP backup" and recover it in twrp but after the recovery it just stuck in bootloop. What must I do to make it working?
I actually has stock rom with no modification that will cause bootloop when upgrading.. I only had to unroot.. Flash stock boot and recovery and let OTA do the rest
I haven't tried the twrp backup on this thread.
sanijsnj said:
I actually has stock rom with no modification that will cause bootloop when upgrading.. I only had to unroot.. Flash stock boot and recovery and let OTA do the rest
I haven't tried the twrp backup on this thread.
Click to expand...
Click to collapse
thanks, I guess I just need to download OTA. also for safer update. though its the chinese version, really having a hard time with its store.
Jon_Nel said:
thanks, I guess I just need to download OTA. also for safer update. though its the chinese version, really having a hard time with its store.
Click to expand...
Click to collapse
Keep in mind that you'll need an unmodified stock ROM for OTA to be a success... Being rooted or having xposed framework causes bootloops.
As for the Chinese store.. You can easily replace it with Google apps.... Just follow the direction in this video.. You can skip it to 1:50mins....
http://https://youtu.be/doyMXI2AFM8
sanijsnj said:
Keep in mind that you'll need an unmodified stock ROM for OTA to be a success... Being rooted or having xposed framework causes bootloops.
As for the Chinese store.. You can easily replace it with Google apps.... Just follow the direction in this video.. You can skip it to 1:50mins....
http://https://youtu.be/doyMXI2AFM8
Click to expand...
Click to collapse
Thank you so much for your reply. I tried to update(OTA) my kitkat[1.21.1402.11] rom to lollipop last night but when I woke up there's this error saying that I should have unmodified rom in order to download the OTA. this ROM that im using is the stock RUU from this link. I dont know why it says that it is modified. does it something to do with my location? because im in the Philippines and this is phone is from China. Hmm, really having a problem updating to MM. Sorry I'm new in HTC's because I'm a Samsung user from the past.
Jon_Nel said:
Thank you so much for your reply. I tried to update(OTA) my kitkat[1.21.1402.11] rom to lollipop last night but when I woke up there's this error saying that I should have unmodified rom in order to download the OTA. this ROM that im using is the stock RUU from this link. I dont know why it says that it is modified. does it something to do with my location? because im in the Philippines and this is phone is from China. Hmm, really having a problem updating to MM. Sorry I'm new in HTC's because I'm a Samsung user from the past.
Click to expand...
Click to collapse
I'm not sure what might be causing this error...but it's definitely not because of your location...you should ask from the other thread, they might be able to assist you.
Fail to load wifi driver on marshmallow twrp rom
Hello
My device is a HTC e8 Chinese version that is remodeled to EU version.
After upgrading to Marshmallow with twrp, everything seemed to be OK but Wi-Fi persists to be in OFF situation and it couldn't be ON.
And then I put the phone on Airplane mode and then I start Wi-Fi again, when I did it, a notification appeared that it told me:
"Fail to load driver, reason: Module is not compatible (8)."
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does anyone have any idea about fixing e8 Wi-Fi driver?
.
chatrood said:
Hello
My device is a HTC e8 Chinese version that is remodeled to EU version.
After upgrading to Marshmallow with twrp, everything seemed to be OK but Wi-Fi persists to be in OFF situation and it couldn't be ON.
And then I put the phone on Airplane mode and then I start Wi-Fi again, when I did it, a notification appeared that it told me:
"Fail to load driver, reason: Module is not compatible (8)."
Does anyone have any idea about fixing e8 Wi-Fi driver?
.
Click to expand...
Click to collapse
It seems that mostly everyone with the china unicom is facing this issue... It has something to do with the kernel or kernel module for WiFi... Unless a developer is able solve this problem... We're gonna have to wait for HTC to fix this via an OTA update.
Hello all,
I have a rooted (with CWM) Mate7 TL10 EMUI 3.0 (4.4.2) B131, (Middle East) and need to update it to Marshmallow, can I do it directly? or do I have to update to Lollipop first? either way, please guide me on how to do it, I have been looking online for days for B131, but couldn't find anything for it.
thank you in advanced
M.Maany said:
Hello all,
I have a rooted (with CWM) Mate7 TL10 EMUI 3.0 (4.4.2) B131, (Middle East) and need to update it to Marshmallow, can I do it directly? or do I have to update to Lollipop first? either way, please guide me on how to do it, I have been looking online for days for B131, but couldn't find anything for it.
thank you in advanced
Click to expand...
Click to collapse
I just had this problem a month ago, same build number and barely any help. But, I was able to find helpful posts in the end. So I'm here to help... and yes. First Lollipop then Marshmallow update.
As you probably know, BACKUP what you need before proceeding.
Then you need to:
1- Unroot your phone if you have root.
2- Have EMUI's stock recovery. You can reinstall it in case you've installed a custom recovery on the phone.
3- Factory reset your device (HIGHLY ADVICE to do but not mandatory).
4- Download Lollipop update (to B326) from here: http://ministryofsolutions.com/2016/02/huawei-mate-7-lollipop-511-upgrade-for.html
5- After you finish the download, extract the "UPDATE.APP" file from it (no need to extract anything else from the archive), create a folder called "dload", and put "UPDATE.APP" in that folder.
6- Once you've done that, you should go to updater in your settings, select "local update". This time, the phone should detect the file "UPDATE.APP".
7- Next, attempt to update. The device should restart and attempt to install the update.
From my experience, the update took about 30 minutes to install, since I didn't factory reset before update. So, I don't know if it'll take less time with a clean device.
To update to marshmallow AFTER you've installed lollipop, simply find the OTA update online, download it, and repeat steps 5 to 7.
If anything of what I said was unclear, missing files to download, or you have any questions, feel free to post again here and I'll try to reply back.
Hopefully everything goes well with you, and have a good day.
Credit goes mostly to Mutahhar Bashir for posting the above site of the update.
EDIT:
P.S.: For bootloader re-lock, I personally don't think it's a must, since it worked updating ota with unlocked bootloader for me.
Highly appreciated my friend
Thank you so much for the help, quick question though, where from can I get the correct stock recovery for my device? Is there a chance I would brick it if I try to install an incompatible recovery?
Again, thank you so much for the help.
M.Maany said:
Thank you so much for the help, quick question though, where from can I get the correct stock recovery for my device? Is there a chance I would brick it if I try to install an incompatible recovery?
Again, thank you so much for the help.
Click to expand...
Click to collapse
Found it on another site. This should be it: http://forum.android.com.pl/topic/2...recovery-sterowniki-mt7-l09-mt7-tl10/?page=27
Sorry I took long, had difficulty finding the file. Install the recovery version that you are CURRENTLY in. The file is called "Recovery mate7 mobopx v2.2". You'll find it on a specific reply on that page.
Keep me up-to-date with your progress for me to see if I can help.
Thanks mate, I really appreciate this, however, you kinda lost me when you said "Install the recovery version that you are CURRENTLY in", I'm not sure I get what you meant, u mean reinstall the same recovert I already have? Or check what version of CWM I have and install the same version of the TWRP recovery?
M.Maany said:
Thanks mate, I really appreciate this, however, you kinda lost me when you said "Install the recovery version that you are CURRENTLY in", I'm not sure I get what you meant u mean reinstall the same recovert I already have? Or check what version of CWM I have and install the same version of the TWRP recovery?
Click to expand...
Click to collapse
Oh I was unclear. Sorry.
What I meant is, that the stock recovery you want to install should be the same as the android version of your phone currently. As in you are currently on Kitkat, then choose to install the kitkat stock recovery from the application.
I hope it's clear right now.
unable to install stock recovery
hey bro, sorry for being away, I keep getting this error when trying to install stock recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
cscl.6te.net/Capture.JPG
any idea how to fix it?
by the way, i used kingroot to root my device, don't know if that's related.
Uhm... Just a few suggestions.
M.Maany said:
hey bro, sorry for being away, I keep getting this error when trying to install stock recovery
any idea how to fix it?
Click to expand...
Click to collapse
Uhm... just a few suggestions:
-Install adb drivers
-Install hisuite (It contains drivers for the mate 7)
-Enable usb debugging (which I'm pretty confident you've enabled)
Universal ADB drivers can be found on the official Clockworkmod website. Hisuite should be available on Huawei's site. Also bootloader must be unlocked (which I'm also confident you have already) if it's not.
Other than what I said above, I still can't think of any other way to try and fix it... Sorry if I couldn't help.
iDoFatalities said:
Uhm... just a few suggestions:
-Install adb drivers
-Install hisuite (It contains drivers for the mate 7)
-Enable usb debugging (which I'm pretty confident you've enabled)
Universal ADB drivers can be found on the official Clockworkmod website. Hisuite should be available on Huawei's site. Also bootloader must be unlocked (which I'm also confident you have already) if it's not.
Other than what I said above, I still can't think of any other way to try and fix it... Sorry if I couldn't help.
Click to expand...
Click to collapse
I may have forgotten to mention that it's still rooted , still trying to figure out how to unroot
M.Maany said:
I may have forgotten to mention that it's still rooted , still trying to figure out how to unroot
Click to expand...
Click to collapse
Stock recovery with root installed is no problem. You can do that after installation. When you get to the OTA update part, uninstall root before so. So, you're not forced to as long as you are still at this step.
ugggg
iDoFatalities said:
Stock recovery with root installed is no problem. You can do that after installation. When you get to the OTA update part, uninstall root before so. So, you're not forced to as long as you are still at this step.
Click to expand...
Click to collapse
i uninstalled kingroot and this unrooted my device, installed adb drivers from clockworkmod site, installed hisuite from huawei site, already have usb debuggine enabled, but still getting same error
any alternative way to restore stock recovery?
can do the update.app manual update without restoring stock recovery?
uggggg
uninstalled kingroot, this unrooted my device, BUT still getting same error, installed adb from clockworkmod , installed hisuite from huawei site, still same error.
can I do the UPDATE.APP manually without restoring the stock recovery??
any alternative method to restore stock recovery?
M.Maany said:
uninstalled kingroot, this unrooted my device, BUT still getting same error, installed adb from clockworkmod , installed hisuite from huawei site, still same error.
can I do the UPDATE.APP manually without restoring the stock recovery??
any alternative method to restore stock recovery?
Click to expand...
Click to collapse
if I lock the bootloader then unlock it again, would that help? if yes, how do i re-lock it
M.Maany said:
uninstalled kingroot, this unrooted my device, BUT still getting same error, installed adb from clockworkmod , installed hisuite from huawei site, still same error.
can I do the UPDATE.APP manually without restoring the stock recovery??
any alternative method to restore stock recovery?
Click to expand...
Click to collapse
You MUST have stock recovery for OTA updates. Sorry.
You can try relock then unlock. But i specifically dont know how to. I think there is an app you can find on the tools/utilities tab of this device for utilities for the Mate7, which i think has a relock bootloader option, and many more utilities.
Other than that, I don't know yet how to help you man. For the meantime, surf the internet if you can find anything that can help.
I apologize.
EDIT: Doesn't your phone reboot into bootloader when trying to install? And have you made sure if the recovery has changed?
thanks man for all the help, yes my device reboots into bootloader and it says device unlocked in red on that screen, and yes i'm still on CWM recovery.i even tried
-adb reboot recovery
-fastboot flash recovery d:\recovery.img
but still get the same error, i think the bootloader lock might be the problem, will look around for that utility you've mentioned and let you know how it goes.
M.Maany said:
thanks man for all the help, yes my device reboots into bootloader and it says device unlocked in red on that screen, and yes i'm still on CWM recovery.i even tried
-adb reboot recovery
-fastboot flash recovery d:\recovery.img
but still get the same error, i think the bootloader lock might be the problem, will look around for that utility you've mentioned and let you know how it goes.
Click to expand...
Click to collapse
Unlock your bootloader again and it might fix the problem. Also you can check out DC Unlocker.
If there is a TWRP for KitKat you can use the terminal to flash your stock recovery or you can use Flashify with root.
YAYYYY !!!!
erayrafet said:
Unlock your bootloader again and it might fix the problem. Also you can check out DC Unlocker.
If there is a TWRP for KitKat you can use the terminal to flash your stock recovery or you can use Flashify with root.
Click to expand...
Click to collapse
FINALLY !!!, tried unlocking bootloader again and it worked, although it took forever to get the unlock code.
anyway, now I have stock EMUI recovery, will remove root and do the OTA and let you know how it goes.
ON lollipop
Alright, thanks to your help and thorough instructions, I am now on lollipop, next step please on the way to Marshmallow?
oh oh, one question though, will i still be able to root after updating to marshmallow?
M.Maany said:
Alright, thanks to your help and thorough instructions, I am now on lollipop, next step please on the way to Marshmallow?
oh oh, one question though, will i still be able to root after updating to marshmallow?
Click to expand...
Click to collapse
Yes.
AWESOME
Awesome !! now do you have a link for me to download the UPDATE.APP for Marshmallow?
or does it need to be updated in some other way?
This thread going to guide you on how you can root Realme GT NEO 2 Device with RUI 3.0 installed.
This boot image is fresh, and it's patched for root access.
Caution: Before flashing, you need to have your bootloader unlocked, for bootloader unlocking, go to this link and follow the procedure to get approval and unlock your device bootloader.
Link: https://forum.xda-developers.com/t/bootloader-unlock-realme-gt-neo-2-rmx3370-all-variants.4391679/
After you get approval, you are ready to root your device!
For this tutorial, I gonna use a windows device.
WARNING!
I am not responsible for anything. proceed at your own risk. Rooting or Unlocking the Bootloader voids the device warranty, keep it in your mind.
STEP - ONE
Only follow this step, if you get approval for the bootloader, and you didn't unlock this device or your flashing environment needs to be configured. You need to visit the following link to set up your environment for flashing a custom boot image.
Link: https://njpsmultimedia.blogspot.com/2022/04/realme-gt-neo-2-bootloader-unlock.html you just need to follow the video tutorial on this website.
STEP - TWOIt's assumed that your environment is properly configured. Let's flash this boot image to root your device.
Download this zip file from here https://drive.google.com/file/d/1Xk1yBp5EDCZbl3i3jMtOhjfaVtTCQqYB/view?usp=sharing and copy the boot.img file to platform-tools folder.
Then open the terminal and cd to the platform-tools folder.
Then, shut down your device and hold the vol up + vol down + power button together to boot this device into fastboot mode.
First, you need to run
Code:
fastboot devices
to check if your device is properly connected to the bootloader interface. If it shows something then your device is properly connected, If not, try to install the device driver, change the cable, or boot into the bootloader mode again.
If your device is connected properly, then you will see a screen like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And then run this command:
Code:
fastboot flash boot boot.img
Then,
Code:
fastboot reboot
You are done! Congratulation.
Note: This method was tested with Realme UI 3.0 android 12 on GT NEO 2. Do not try this method on RUI 2.0 or on other devices.
SCREENSHOTS
Note
If you face NO WIFI, Sound issue on the C04 version, you are advised to flash this alternate version from here: https://forum.xda-developers.com/t/...uide-on-gt-neo-2.4435919/page-2#post-86985433
Do you lose all data ? On the root part the bootloader is already unlocked
theogr91 said:
Do you lose all data ? On the root part the bootlocker is already unlocked
Click to expand...
Click to collapse
- it is necessary to have the bootloader unlocked before flash (instructions on how to unlock the bootloader can be found in the video in the post above or here on the forum)
- after flash just install Magisk manager
no data loss, tested and functional
theogr91 said:
Do you lose all data ? On the root part the bootlocker is already unlocked
Click to expand...
Click to collapse
If your bootloader is already unlocked, no data loss. but If your device bootloader is not unlocked, then unlocking your device data will be erased.
Do we flash magisk or other way of root ?
theogr91 said:
Do we flash magisk or other way of root ?
Click to expand...
Click to collapse
You need not flash anything extra than flashing customized boot.img. Just simply follow this step and your device will be rooted.
Worked like charm thanks. Will the phone be ok after an OTA update ?
Help...After flashing boot image and rebooted , Wifi is not scanning the networks and I am unable to take calls but 4g(internet) is working fine. Please reply me for any fix. I followed the exact steps you mentioned. My Device Realme Gt neo 2 UI 3.0
mahesh.pujala said:
Help...After flashing boot image and rebooted , Wifi is not scanning the networks and I am unable to take calls but 4g(internet) is working fine. Please reply me for any fix. I followed the exact steps you mentioned. My Device Realme Gt neo 2 UI 3.0
Click to expand...
Click to collapse
In my case, all is fine.
You can try backup data and then reset your device through recovery.
theogr91 said:
Worked like charm thanks. Will the phone be ok after an OTA update ?
Click to expand...
Click to collapse
After the OTA update, you may need to flash this boot image again.
Help...After flashing boot image and rebooted , Wifi is not scanning the networks and I am unable to take calls but 4g(internet) is working fine. Please reply me for any fix. I followed the exact steps you mentioned. My Device Realme Gt neo 2 UI 3.0
Nurujjamanpollob said:
In my case, all is fine.
You can try backup data and then reset your device through recovery.
Click to expand...
Click to collapse
Thanks for the reply . Any way I reverted back to previous state by flashing stock boot image and firmeware. Now everthing works fine. I will think about rooting later..
Removed root and updated to RMX3370_11_C.04 is it safe to reflash root image on this version?
theogr91 said:
Removed root and updated to RMX3370_11_C.04 is it safe to reflash root image on this version?
Click to expand...
Click to collapse
I just tried this and it worked for me...
Meanwhile I realised that my wifi and my phone don't work anymore... I have no idea if this boot image is the cause.
Grobie13 said:
Meanwhile I realised that my wifi and my phone don't work anymore... I have no idea if this boot image is the cause.
Click to expand...
Click to collapse
I have no wifi after the flash and i have no twp on RMX3370_11_C.04 any way to fix it ?
theogr91 said:
I have no wifi after the flash and i have no twp on RMX3370_11_C.04 any way to fix it ?
Click to expand...
Click to collapse
No solution so far. I think first everything was fine, after flashing the magisk boot image it's gone worse... But I'm not sure.
I do not recommend updating on RMX3370_11_C.0. After flashing boot image (without Magisk) wifi no longer working.
I flashed clean firmware and lock bl i am done moding this device only adb debloat.. And after clean flash netflix still wont open login screen...
Grobie13 said:
No solution so far. I think first everything was fine, after flashing the magisk boot image it's gone worse... But I'm not sure.
Click to expand...
Click to collapse
What device variant you use? India or global?
Probably I gonna update this boot image today with latest update.
Nurujjamanpollob said:
What device variant you use? India or global?
Probably I gonna update this boot image today with latest update.
Click to expand...
Click to collapse
It's global respectively EU. But I start from scratch yesterday. I flashed twrp, format data and flashed magisk. But other people need your patched boot image. Thanks for providing.