Develop Bugs

[Q] Problem with Odin / can't flash Bootloader

Hi guys,
hope you can help me with a nasty little problem ..
I got a Chinese Note 2 (GT-N7100_CHN_CHN) from my father in law - he bought a Note 4 just recently. The phone is virtually not usable in Europe, as no Google support is implemented (mail, G+, Maps) and there is no access to the regular Playstore. Also, the only Android available is 4.1.
So I tried to flash a new Firmware (and yes, I'm a noob), and that's were the problems began. I've downloaded this ROM: N7100XXUFNE1_N7100DBTFNE1_N7100XXUFND3_HOME.tar.md5 which is - as far as I could figure out - a more or less "factory" version of a German Android 4.4 ROM. For whatever reason, I was unable to flash it using Odin (I tried several drivers, cables, computers (all Win7/64), disabled virus scan .. no way to get Odin 3.09 to work. It recognizes the phone, but aborts the flash process immediately with just a "1 processes failed" error.
After reading a bit here, I tried to root the phone using Saferoot (worked perfectly), loaded MobileOdin and this ROM to the phone and did the flashing there. This works fine, the phone starts, it has a German interface, is running KitKat .. great. Only issue: The WiFi does not work. As I figured out from this forum, I need to install either a WiFi patch or a new Bootloader (I've downloaded BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.tar.md5 - hope that's the right one).
The problem now is:
Saferoot fails to root the Android 4.4 version - so no root access
MobileOdin does not work without root (and I don't know whether it would be able to flash a bootloader)
Odin 3.09 still does not work with the device
I tried Heimdall, but it does not accept the .md5 files for Odin and I could not find any ROMs in the right format
So I'm running out of ideas what else to try. Could you give me a hint what to to do?
Many thanks,
Scooby

You are saying the phone is chinese and doesn't have support from Google so there is clearly not original phone.
Samsung has not produced that phone so it means the hardware parts are not from samsung and the ROM you are flashing can't be installed.
I read you want to root but I think it is already rooted(try with the app "root checker")
You can't do much with that phone.
Sorry

manuel1992 said:
You are saying the phone is chinese and doesn't have support from Google so there is clearly not original phone.
Samsung has not produced that phone so it means the hardware parts are not from samsung and the ROM you are flashing can't be installed.
I read you want to root but I think it is already rooted(try with the app "root checker")
You can't do much with that phone.
Sorry
Click to expand...
Click to collapse
Hi Manuel,
it's definitely a original Samsung device. Google is simply (virtually) not available in China, so they install a slightly modified Android that points to a local Samsung store instead of playstore, G+ and Maps is not pre-installed ..
As written above, I was able to root it as long as the original Android 4.1.x was installed and I have successfully flashed the new german Kitkat ROM. "Only" Problem right now is that I can't get Odin to work and due to that I can not install the Wifi fix or new Bootloader. And ideas on that?
Thanks
Scooby

ZE551ML not receiving OTA or detecting update file

My phone's stuck on the firmware from April 1st (specifically LRX21V.WW-ASUS-Z00A-2.13.40.13_20150401_8390_user044030427_201501601090010000500001). I have the TW 4GB/32GB/1.8GHz version of the phone and I have not ever unlocked the bootloader or rooted.
I can check for a OTA but it doesn't come up with anything. I was told to download the firmware from ASUS's support site and flash it from there. I downloaded the WW zip (my phone is currently running the WW version) and made sure it was *-user.zip and put it in the Internal Storage but my phone doesn't detect it. I've rebooted, recopied it, tried with a different version of firmware (still newer than my version) and no matter what I do I don't get the notification to update. I've also since factory reset my phone, which hasn't helped.
ASUS told me to try downloading the WW_2.14.40.19 zip and trying to update with that, but I don't get the notification to update either. My friend who also has the same model as me has exactly the same problem and we both have Android OS swallowing up ~60% of the battery per charge by using up the CPU, which is very annoying.

I have exactly the same problem. I can't update my phone.
The systemupdate.apk also crashes at start.

mikbob said:
My phone's stuck on the firmware from April 1st (specifically LRX21V.WW-ASUS-Z00A-2.13.40.13_20150401_8390_user044030427_201501601090010000500001). I have the TW 4GB/32GB/1.8GHz version of the phone and I have not ever unlocked the bootloader or rooted.
I can check for a OTA but it doesn't come up with anything. I was told to download the firmware from ASUS's support site and flash it from there. I downloaded the WW zip (my phone is currently running the WW version) and made sure it was *-user.zip and put it in the Internal Storage but my phone doesn't detect it. I've rebooted, recopied it, tried with a different version of firmware (still newer than my version) and no matter what I do I don't get the notification to update. I've also since factory reset my phone, which hasn't helped.
ASUS told me to try downloading the WW_2.14.40.19 zip and trying to update with that, but I don't get the notification to update either. My friend who also has the same model as me has exactly the same problem and we both have Android OS swallowing up ~60% of the battery per charge by using up the CPU, which is very annoying.
Click to expand...
Click to collapse
I am having this issue as well. Anyone figure out how to fix it?

I think I fixed it.
First I flashed a pre-rooted ROM (Like in this tutorial: asus-zenfone.com/2015/04/asus-zenfone-2-pre-root-systemimg.html)
After that, my phone detected the update files.
I hope this will help

I have same problem

That most likely indicates that you have CN device with WW rom slapped on top of it. The only way for OTA is unlocked bootloader and TWRP install, or ADB sideload full update each time new firmware released. If you still can return the device - do it.

Try:
1. Copy the downloaded firmware file to MicroSD
2. Rename it to MOFD_SDUPDATE.zip
3. Go to recovery mode
And the file should be detected and the update process should start immediately.
Edit: Okay, looks like your guys got it fixed.
Edit2: And oh no, this was actually a one year old thread :-|

Thanks dude!
:good::good::good::good::good::good:

[Q] how to install htc devcenter roms

hi friends
--- i have htc 816w. After unlocking and rooting two months, my touch started not work well. it sometimes doest work, sometimes writes by itself, and sometimes open windows by itself. Because of this problem;
---- i installed some custom roms like "cm-12-20150505-NIGHTLY-a5.zip" and "mokee" and on my mobile. i didnt like them. there were some problems. i want to restore old rom but, i tried reset and everything but i couldnt go back to android 4.4.4.
*my mobile is now "cm-12-20150505-NIGHTLY-a5"
*and android is 5.0.2 .
----????my question: how can i install roms in page
"http://www.htcdev.com/devcenter/downloads"
i want to install this rom. it is 4.4.4
a51dtul-3.10.28-g090104e.zip
can i do it with fastboot or flashing commands on pc ???????
please step bye step

osmanoca said:
hi friends
--- i have htc 816w. After unlocking and rooting two months, my touch started not work well. it sometimes doest work, sometimes writes by itself, and sometimes open windows by itself. Because of this problem;
---- i installed some custom roms like "cm-12-20150505-NIGHTLY-a5.zip" and "mokee" and on my mobile. i didnt like them. there were some problems. i want to restore old rom but, i tried reset and everything but i couldnt go back to android 4.4.4.
*my mobile is now "cm-12-20150505-NIGHTLY-a5"
*and android is 5.0.2 .
----????my question: how can i install roms in page
"http://www.htcdev.com/devcenter/downloads"
i want to install this rom. it is 4.4.4
a51dtul-3.10.28-g090104e.zip
can i do it with fastboot or flashing commands on pc ???????
please step bye step
Click to expand...
Click to collapse
That is not rom but source code and You can't install that. Also watch out for models as You was represent that Your model is 816 (A5) and You was anyway look at sources of A51DTUL!

Can't install Recovery or Downgrade from Stock MM 6.0

Hi,
I have a temprooted LG G3 (D855) with Official Marshmallow Stock ROM. I have tried to bump it using this thread, but the moment I have rebooted my device to recovery, I had no recovery at all and it has factory reset my device (don't worry, I had a backup). So I've decided to downgrade it to Lollipop or even to KitKat. I've tried to use LG Flashtool 2014. It had thrown an error on both versions (connection failed). I've read about it and found LGUP and even LGUP thrown an error. I've tried to do it agian from LG Flashtool (the old one) and it thrown this error: "CrossDL [] to [d855].SWversion()" and I've searched for this problem, and found a tutorial to remove this error (using Hex Workshop to delete the model) but Hex Workshop had stopped working when I've tried to save it. And I have a good computer (Intel Core i7 Skylake, 8GB RAM). Even before all that stuff, I had a temproot, which means every time I reboot the phone, the root just vanishing. And I've used KingRoot (which is a good root app) to root it.
Please help me. I want to install CM13 very soon.

MGSTUDIOs0mE0Ne said:
Hi,
I have a temprooted LG G3 (D855) with Official Marshmallow Stock ROM. I have tried to bump it using this thread, but the moment I have rebooted my device to recovery, I had no recovery at all and it has factory reset my device (don't worry, I had a backup). So I've decided to downgrade it to Lollipop or even to KitKat. I've tried to use LG Flashtool 2014. It had thrown an error on both versions (connection failed). I've read about it and found LGUP and even LGUP thrown an error. I've tried to do it agian from LG Flashtool (the old one) and it thrown this error: "CrossDL [] to [d855].SWversion()" and I've searched for this problem, and found a tutorial to remove this error (using Hex Workshop to delete the model) but Hex Workshop had stopped working when I've tried to save it. And I have a good computer (Intel Core i7 Skylake, 8GB RAM). Even before all that stuff, I had a temproot, which means every time I reboot the phone, the root just vanishing. And I've used KingRoot (which is a good root app) to root it.
Please help me. I want to install CM13 very soon.
Click to expand...
Click to collapse
Download a twrp bumped recovery img from the twrp site(https://dl.twrp.me/d855/), and Rashr or flashify app. Then use kingroot for your temporary root, then use Rashr or the flashify app to install recovery img, reboot into recovery, and then flash cm13 or whatever you want.
*I'm not sure about obtaining permanent root for MM on your SW version or your model(I have a vs985), but since you are flashing cm13 and not staying on stock you shouldn't have to worry about any of that mess.

You can repeat the whole process on a Windows 7 (32-bit) pc. I had the same problem while i was trying to restore my lg g3 to stock kitkat using flash tool (tot method) on my Windows 10 (64-bit) laptop. I am still unable to restore to stock on my laptop but this process works smooth on my brother's computer with Windows 7 (32-bit).
I am pretty sure changing to a Windows 7 32-bit pc will solve your problem.

startswithPendswithOOH said:
Download a twrp bumped recovery img from the twrp site(*removed because I am a new user*), and Rashr or flashify app. Then use kingroot for your temporary root, then use Rashr or the flashify app to install recovery img, reboot into recovery, and then flash cm13 or whatever you want.
*I'm not sure about obtaining permanent root for MM on your SW version or your model(I have a vs985), but since you are flashing cm13 and not staying on stock you shouldn't have to worry about any of that mess.
Click to expand...
Click to collapse
That's exactly what I did. And it just removed the recovery. I've also tried to do it through adb and it also failed. I've noticed that there is some missing information in my build.prop file, and I've tried to fill it, but it had no effect.

dksoni411 said:
You can repeat the whole process on a Windows 7 (32-bit) pc. I had the same problem while i was trying to restore my lg g3 to stock kitkat using flash tool (tot method) on my Windows 10 (64-bit) laptop. I am still unable to restore to stock on my laptop but this process works smooth on my brother's computer with Windows 7 (32-bit).
I am pretty sure changing to a Windows 7 32-bit pc will solve your problem.
Click to expand...
Click to collapse
Will it work in Virtual Machine? I have only 64-bit Windows 7 laptops... But I'll look for one. I'll try it.

dksoni411 said:
You can repeat the whole process on a Windows 7 (32-bit) pc. I had the same problem while i was trying to restore my lg g3 to stock kitkat using flash tool (tot method) on my Windows 10 (64-bit) laptop. I am still unable to restore to stock on my laptop but this process works smooth on my brother's computer with Windows 7 (32-bit).
I am pretty sure changing to a Windows 7 32-bit pc will solve your problem.
Click to expand...
Click to collapse
OK, so I've tried it and it still won't work. I was using Windows 7 Ultimate 32-bit now.

I've solved the problem with a little help from CODEFIRE team: I've flashed the tot with the G3-CODEFIRE dll which worked perfectly.
I can't post link because I'm still a new member.
Anyone knows how to close a thread or add the [SOLVED] tag? I'm quiet new here...
Sorry about my bad english.

[ROM] [STOCK] Official manual updates on the M2 tablet M2-A01L

Official manual updates for
the M2 tablet M2-A01L​
- Disclaimer
Well, whatever you do with this guide is all up to you and in your own responsibility. You
should have basic knowledge about Android. Remember, I have only one M2-A01L and this
guide worked this way on my device. There is no guarantee, it will work on your M2-A01L,
too.
- Issue
Well, some guys just do not get an automated update in their EMUI apps, still hanging dry
on B006 or B007.
- Solution
So, you can manually update the tablet with one of the original update files, which I saved at
my two automatic updates.
- Guide
1. First, it is important to know, if you have installed a different recovery and/or any root stuff.
If no, go to 3.!
2. So, with a different recovery like TWRP and not the official Huawei one, you cannot get the
official updates. Also, I absolutely do not recommend Kingroot. You may rather use Magisk for
systemless root rights - way less problems. For a guide I recommend my other thread, but you
can do it your own way:
https://forum.xda-developers.com/mediapad-m2/how-to/guide-official-updates-m2-tablet-root-t3589363
Basically, you cannot update with a non-original recovery like TWRP.
3. If you are on B006, you should first update to B007 and afterwards to B010. I did it that way.
I would not recommend going directly to B010. If you are on B007 you can update to B010.
You might update to B010, if you are on B009, but I never tested this with this file.
4. So, we have two ways to go - you have to decide one:
a) You have to download the file (see below), rename it to "update.zip" and place it into the
directory "HwOUC" on your tablet. That is the very official way, just like it usually goes.
OR
b) You have to download the file (see below), unpack the included "update.app" and place it
into the directory "dload" on your tablet. That should be working, too, BUT I never checked this
and I only read somewhere on the internet about this method. I definitely do NOT recommend
it. The first method is the easier one.
5. Well, now you have to reboot your tablet and it will reboot directly into the recovery, because
it "sees" the update in the update directory ... et voila, you are getting your awaited update.
6. After the update is done and your device has rebooted, you can go back to your own recovery
like I did with this guide:
https://forum.xda-developers.com/mediapad-m2/how-to/guide-unlock-bootlader-twrp-root-huawei-t3322340
- Root:
If you want to have root rights, I strongly recommend flashing Magisk within TWRP, because it is
just a nice and more modern approach to having root. It works very fine on my M2 10 tablet. The
link for the files and guide is here:
https://goo.gl/UXYk4d
It is very easy. You just flash Magisk 12 in TWRP and then install the Magisk Manager app from the
Play store.
- Files for M2-A01L:
File-Upload:
B007 (from B006): M2-A01LV100R001C100B007.zip (European version)
B010 (from B007): OTA-M2-A01LV100R001C100B010.zip (European version)
DepositFiles:
B007 (from B006): M2-A01LV100R001C100B007.zip (European version)
B010 (from B007): OTA-M2-A01LV100R001C100B010.zip (European version)
Have fun with your updated tablet. ... and I am happy, if I could help you - any coffee/juice appreciated.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=ESYCULGT8ZU3A
...
..
.

*** save ***

Hi xsycox, I'm not able to update mine with your technique Mine is a M2-A01L with 006.
I load the file M2-A01LV100R001C100B007.zip in HwOUC and rename it to update.zip but restarting the tablet it is not installed automatically.
So the only way I've is to go in "manual update" of the tablet, select the file and it will reboot. But after 2% I got error.
I also tried the "dload" unpack method without results..
Help please..

Shocker580 said:
Hi xsycox, I'm not able to update mine with your technique Mine is a M2-A01L with 006.
I load the file M2-A01LV100R001C100B007.zip in HwOUC and rename it to update.zip but restarting the tablet it is not installed automatically.
So the only way I've is to go in "manual update" of the tablet, select the file and it will reboot. But after 2% I got error.
I also tried the "dload" unpack method without results..
Help please..
Click to expand...
Click to collapse
Same issue here. I'm on 007.

vahtmestar said:
Same issue here. I'm on 007.
Click to expand...
Click to collapse
Shocker580 said:
Hi xsycox, I'm not able to update mine with your technique Mine is a M2-A01L with 006.
I load the file M2-A01LV100R001C100B007.zip in HwOUC and rename it to update.zip but restarting the tablet it is not installed automatically.
So the only way I've is to go in "manual update" of the tablet, select the file and it will reboot. But after 2% I got error.
I also tried the "dload" unpack method without results..
Help please..
Click to expand...
Click to collapse
Had the same issue as well. Luckily I've been able to find a full Stock ROM of the latest version B010. It is designed for the 10.0 LTE Premium Edition of the M2 A01L. Shared it in a separate threat over here. Maybe it'll be of any help to you. Only problem when using it, is a full factory reset happening by doing so.

Hi,
just curious to know. I have Media pad M2-A01W (not A01L) which I bought in China (using in EU). I have currently M2-A01WV100R001C233B020 build number, which was an update from September 1, 2016. Is this A01L (EU/Western version) is different than A01W update? Is it possible to manually replace A01W to A01L ? I tried once but wasn't succeed.
Thanks in advance for your reply.
-KK

5m4r7ph0n36uru said:
Had the same issue as well. Luckily I've been able to find a full Stock ROM of the latest version B010. It is designed for the 10.0 LTE Premium Edition of the M2 A01L. Shared it in a separate threat over here. Maybe it'll be of any help to you. Only problem when using it, is a full factory reset happening by doing so.
Click to expand...
Click to collapse
You just saved my tablet. Thanks.

Hi, is it work for Dtab D-01H (Docomo), I dont find any rom for it

More custom roms for Mediapad M2 10 !
Hi,
I don't understand why we don't have more custom roms for the Mediapad M2 10....