Hi, as said in the title, my Motorola XT910 is stuck on the logo, and will not boot, even after charging, and letting it do its thing overnight. I tried everything I could, including trying to wipe the cache via recovery mode, and I do not have access to it via adb in any ways. The only communication I can establish between it and my computer is via fastboot. The RSD Software doesn't recognize it either, though it appears on the computer as "ADB Device". Biggest problem is, I have seen threads from years ago on other forums, all over the internet with people having this issue, some had it fixed via a factory reset, some had to send it back. Obviously, I cannot send it back to motorola, as for the factory reset, I really cannot do it, since my whole objective of making this phone function again was to recover old very important videos and photos on it, which is rendered impossible due to android not starting.
I really hope someone has a solution (does anyone still even come by these threads ?).
Thanks in Advance,
Dylan.
LaMontreBelge said:
Hi, as said in the title, my Motorola XT910 is stuck on the logo, and will not boot, even after charging, and letting it do its thing overnight. I tried everything I could, including trying to wipe the cache via recovery mode, and I do not have access to it via adb in any ways. The only communication I can establish between it and my computer is via fastboot. The RSD Software doesn't recognize it either, though it appears on the computer as "ADB Device". Biggest problem is, I have seen threads from years ago on other forums, all over the internet with people having this issue, some had it fixed via a factory reset, some had to send it back. Obviously, I cannot send it back to motorola, as for the factory reset, I really cannot do it, since my whole objective of making this phone function again was to recover old very important videos and photos on it, which is rendered impossible due to android not starting.
I really hope someone has a solution (does anyone still even come by these threads ?).
Thanks in Advance,
Dylan.
Click to expand...
Click to collapse
RSD lite doesn't work with most Windows 10 machines, use Windows 7. http://forum.xda-developers.com/showpost.php?p=59348530&postcount=6
If you want to save data you need to modify the .XML file if using RSD Lite
Lots of issues can cause a boot loop, bad battery, bad app, bad hardware... even a bad charger or USB cable.
Try [Utility] - = MotoFlashPro =
Hi, thanks for replying, I took note of the software not functionning with windows 10, do you think it will work if I run 7 in VmWare and pass the phone through or do I absolutely have to use a physical 7 machine ?
Also, I really cannot make a factory cable like the one pictured in the post you linked, since none of my cables permit such a modification (the fifth pin does not have a spot to solder onto).
About the bootloop, well I'm not sure it really is one, since it doesn't loop at all, it just stays on the starting screen.
It shouldn't be a battery problem since even when giving power straight to the battery terminals, it does not boot, though the fastboot thing says "battery ok".
It shouldn't be a bad app either since last time I used the phone, like 3 years ago before I broke the screen which I replaced recently, it worked perfectly fine, and obviously I could not install an app in the meantime. The battery just ran down to 0 volts but I managed to make it work again. And what do you mean by bad charger ? Something like not powerful enough perhaps ?
LaMontreBelge said:
Hi, thanks for replying, I took note of the software not functionning with windows 10, do you think it will work if I run 7 in VmWare and pass the phone through or do I absolutely have to use a physical 7 machine ?
Also, I really cannot make a factory cable like the one pictured in the post you linked, since none of my cables permit such a modification (the fifth pin does not have a spot to solder onto).
About the bootloop, well I'm not sure it really is one, since it doesn't loop at all, it just stays on the starting screen.
It shouldn't be a battery problem since even when giving power straight to the battery terminals, it does not boot, though the fastboot thing says "battery ok".
It shouldn't be a bad app either since last time I used the phone, like 3 years ago before I broke the screen which I replaced recently, it worked perfectly fine, and obviously I could not install an app in the meantime. The battery just ran down to 0 volts but I managed to make it work again. And what do you mean by bad charger ? Something like not powerful enough perhaps ?
Click to expand...
Click to collapse
Hi again, quick update, I plugged it into my Windows Xp machine as I do not have a windows 7 computer, and it appeared. Also, could you please tell me what to change in the xml file in order to keep the data ?
Please, are you there ? I really need this help with the XML file, what do I need to edit ? I got the phone to be recognized in windows, even in rsd lite, i just need to know what to edit in the file
LaMontreBelge said:
Please, are you there ? I really need this help with the XML file, what do I need to edit ? I got the phone to be recognized in windows, even in rsd lite, i just need to know what to edit in the file
Click to expand...
Click to collapse
I've never had to use RSD Lite, and you might be better off waiting for him to respond incase I'm wrong (haven't touched this phone in a while). But I've done some digging and heard you can remove the line near the end of that XML file that goes something like
Code:
<step operation="erase" partition="userdata"/>
and it should skip the data wipe. I don't think it's necessary to remove the ones for cache and stuff. It might be a bad idea.
Smu1zel said:
I've never had to use RSD Lite, and you might be better off waiting for him to respond incase I'm wrong (haven't touched this phone in a while). But I've done some digging and heard you can remove the line near the end of that XML file that goes something like
Code:
<step operation="erase" partition="userdata"/>
and it should skip the data wipe. I don't think it's necessary to remove the ones for cache and stuff. It might be a bad idea.
Click to expand...
Click to collapse
Thanks for the info, I will indeed wait for him to reply, but i just checked in the XML file, and I do not have that line anywhere in the file. Does that mean it is incomplete or does this one just default to not erasing ? Also, this is the only file I could find that is a perfect match for my french market xt910.
LaMontreBelge said:
Thanks for the info, I will indeed wait for him to reply, but i just checked in the XML file, and I do not have that line anywhere in the file. Does that mean it is incomplete or does this one just default to not erasing ? Also, this is the only file I could find that is a perfect match for my french market xt910.
Click to expand...
Click to collapse
Also, I just checked in the other file I found, for an english-languaged model this time, it does have these lines, but is only 560mb instead of the 800 something of my french file
LaMontreBelge said:
Thanks for the info, I will indeed wait for him to reply, but i just checked in the XML file, and I do not have that line anywhere in the file. Does that mean it is incomplete or does this one just default to not erasing ? Also, this is the only file I could find that is a perfect match for my french market xt910.
Click to expand...
Click to collapse
Huh, yeah I don't really know then. The model I have is the XT912 (Verizon). I just got this info from a thread for a newer Moto. It could very well just simply not wipe, but I wouldn't go ahead and try incase you end up actually wiping it permanently. I'm not an expert at all, so I'd just wait until he gives you advice. Does this French firmware have similar lines like that for cache or other partitions? It might be in a completely different format then what I'm looking at. But I doubt it's corrupt.
Smu1zel said:
Huh, yeah I don't really know then. The model I have is the XT912 (Verizon). I just got this info from a thread for a newer Moto. It could very well just simply not wipe, but I wouldn't go ahead and try incase you end up actually wiping it permanently. I'm not an expert at all, so I'd just wait until he gives you advice. Does this French firmware have similar lines like that for cache or other partitions? It might be in a completely different format then what I'm looking at.
Click to expand...
Click to collapse
Actually I think the xt912 is pretty much identical unless I'm mistaking something. But either way, I do appreciate your cautiousness about the subject. Yes exactly I really cannot afford to lose the data that remains on the phone. Actually yes it does seem to have fairly similar lines, here have a look, on the left is the french firmware and the right the international. Now, I do not know what the files you're used to working with look like, but they may very well have similar if not identical lines.
Edit: I just re-read your question and realized I completely misunderstood what you asked. No, the french version doesn't have formatting lines at all. Deeply sorry for this misunderstanding.
LaMontreBelge said:
Actually I think the xt912 is pretty much identical unless I'm mistaking something. But either way, I do appreciate your cautiousness about the subject. Yes exactly I really cannot afford to lose the data that remains on the phone. Actually yes it does seem to have fairly similar lines, here have a look, on the left is the french firmware and the right the international. Now, I do not know what the files you're used to working with look like, but they may very well have similar if not identical lines.
Edit: I just re-read your question and realized I completely misunderstood what you asked. No, the french version doesn't have formatting lines at all. Deeply sorry for this misunderstanding.
Click to expand...
Click to collapse
I've noticed the left one is a "1FF" firmware. Which from what I've looked up, is supposed to not have the erasing lines. While the "CFC" ones are. Which is why the right one has those. But I've noticed the left firmware has what seems to be Gingerbread. I don't know if dirty flashing an older firmware will cause issues, if it's even possible. I've found an old thread on droidforums where someone tried to go back to ICS from that JB leak and ended up bricking. I don't think I can post links because I haven't posted 10 times unless they changed something.
Smu1zel said:
I've noticed the left one is a "1FF" firmware. Which from what I've looked up, is supposed to not have the erasing lines. While the "CFC" ones are. Which is why the right one has those. But I've noticed the left firmware has what seems to be Gingerbread. I don't know if dirty flashing an older firmware will cause issues, if it's even possible. I've found an old thread on droidforums where someone tried to go back to ICS from that JB leak and ended up bricking. I don't think I can post links because I haven't posted 10 times unless they changed something.
Click to expand...
Click to collapse
Actually, the phone is still on gingerbread (2.3.5) as I never found updates when it still worked, so this shouldn't be an issue (hopefully) and okay, thanks for the info, so it means my file is sound, right?
LaMontreBelge said:
Actually, the phone is still on gingerbread (2.3.5) as I never found updates when it still worked, so this shouldn't be an issue (hopefully) and okay, thanks for the info, so it means my file is sound, right?
Click to expand...
Click to collapse
I believe the file should be good unless you somehow got a bad download or something. But it seems 2.3.5 and 2.3.6 have different bootloader versions, and it looks like the firmware on the left doesn't have the "mbm" stuff. The last thing you need is a hard brick, so I'd be pretty hesitant to flash unless someone who has more knowledge tells you it's okay. I'm guessing you'd have to find a French CFC firmware and edit out that userdata wipe line (if that even works) or find a 1FF 2.3.5 firmware with an identical bootloader.
Smu1zel said:
I believe the file should be good unless you somehow got a bad download or something. But it seems 2.3.5 and 2.3.6 have different bootloader versions, and it looks like the firmware on the left doesn't have the "mbm" stuff. The last thing you need is a hard brick, so I'd be pretty hesitant to flash unless someone who has more knowledge tells you it's okay. I'm guessing you'd have to find a French CFC firmware and edit out that userdata wipe line (if that even works) or find a 1FF 2.3.5 firmware with an identical bootloader.
Click to expand...
Click to collapse
Alright, then I won't flash it, just in case. Also, do you have any way to check if the bootloader version is different ? If yes, I could check it. And alright, I'll try finding another file that happens to be on 2.3.5. Thanks again for the info sir.
LaMontreBelge said:
Alright, then I won't flash it, just in case. Also, do you have any way to check if the bootloader version is different ? If yes, I could check it. And alright, I'll try finding another file that happens to be on 2.3.5. Thanks again for the info sir.
Click to expand...
Click to collapse
I hyperlinked a link I found with some info on that. I just looked at the build number of the versions listed in that doc, looked at the bootloader version next to it, and looked at the firmware's filename. In your case, "6.5.1-167" has bootloader version "0A.6C" while 2.3.5 with the build number "6.5.1_73" has bootloader version "0A.66". My source was this Doc https://docs.google.com/document/d/1CWZU-4i7jWO26RXJ7YFJV-Ze-mJrDaTuCuVI-ZwxDBE/. I honestly don't know if the bootloader matters, but I wouldn't want to risk it in case it makes the situation worse. Hopefully shadow can help you out.
https://forum.xda-developers.com/t/index-motorola-droid-razr-2012.3023837/post-58684547
Here's a pinned thread with some firmwares if it helps any.
Smu1zel said:
I hyperlinked a link I found with some info on that. I just looked at the build number of the versions listed in that doc, looked at the bootloader version next to it, and looked at the firmware's filename. In your case, "6.5.1-167" has bootloader version "0A.6C" while 2.3.5 with the build number "6.5.1_73" has bootloader version "0A.66". My source was this Doc https://docs.google.com/document/d/1CWZU-4i7jWO26RXJ7YFJV-Ze-mJrDaTuCuVI-ZwxDBE/. I honestly don't know if the bootloader matters, but I wouldn't want to risk it in case it makes the situation worse. Hopefully shadow can help you out.
Click to expand...
Click to collapse
Okay, i just took a look at the doc linked, and I have no idea how you found it, but it is mind boggling. All the roms, listed, just like that. Thank you so much. And yes indeed the bootloader is different, and I wouldn't risk it. I'll keep looking for the 2.3.5 ROM, but for now it seems like a lost cause. Perhaps they have it over on the Motorola forums. I'll make a thread later today.
Smu1zel said:
I hyperlinked a link I found with some info on that. I just looked at the build number of the versions listed in that doc, looked at the bootloader version next to it, and looked at the firmware's filename. In your case, "6.5.1-167" has bootloader version "0A.6C" while 2.3.5 with the build number "6.5.1_73" has bootloader version "0A.66". My source was this Doc https://docs.google.com/document/d/1CWZU-4i7jWO26RXJ7YFJV-Ze-mJrDaTuCuVI-ZwxDBE/. I honestly don't know if the bootloader matters, but I wouldn't want to risk it in case it makes the situation worse. Hopefully shadow can help you out.
Click to expand...
Click to collapse
Also, in the document there is a link that leads to an archive, but no files are downloadable, do you happen to have any of them by chance ?
Smu1zel said:
https://forum.xda-developers.com/t/index-motorola-droid-razr-2012.3023837/post-58684547
Here's a pinned thread with some firmwares if it helps any.
Click to expand...
Click to collapse
This thread does indeed help a little bit, but the firmware center link does not, as it is where i got my 2.3.6 ROM from, and as far as I know, is the only french one. Honestly I do not care if it's an English one, I just want to make sure that it won't mess up the phone
LaMontreBelge said:
Also, in the document there is a link that leads to an archive, but no files are downloadable, do you happen to have any of them by chance ?
Click to expand...
Click to collapse
Yeah I think those links might be out of date. Go under "XT910" and look at some of the links. Also I found that doc under that section.
https://forum.xda-developers.com/t/index-motorola-droid-razr-2012.3023837/post-58684547
I hope I'm not leading you down a wrong path, hopefully he responds soon. Maybe the bootloader doesn't matter, I don't know.
Related
I bought a Razr Maxx from Amazon, it came from Hong Kong with AsiaRetail ROM, it works fine with except the encoding of music tags. I want to switch to the same Motorola's Android version but from another region (For example: US). I was reading a few procedures, but all they explains migratations from GB to ICS and I am already on ICS (673.94.328.XT910.AsiaRetail.en.03). Does anybody knows any procedure to download and install Motorola's Android stock ROM?
Thanks in advance.
You can use RSDLite to install any european ICS version. I did it in mine too, from an Asian ROM to Retail.eu (Rtail British)
http://forum.xda-developers.com/showthread.php?t=1850683
http://sbf.droid-developers.org/umts_spyder/list.php
EDIT: also this one I posted a while ago: http://forum.xda-developers.com/showthread.php?p=31477142#post31477142
davizera said:
You can use RSDLite to install any european ICS version. I did it in mine too, from an Asian ROM to Retail.eu (Rtail British)
http://forum.xda-developers.com/showthread.php?t=1850683
http://sbf.droid-developers.org/umts_spyder/list.php
EDIT: also this one I posted a while ago: http://forum.xda-developers.com/showthread.php?p=31477142#post31477142
Click to expand...
Click to collapse
Thank you so much. It worked just fine, I had issues on the first boot but I applied a factory reset and it solved.
I have 2 questions:
- Is it totally secure the sbf files from droid-developers? (I had never hear it before)
- I can't share my data conection, i don't have Internet on my computer through the phone
rcdeoliveira said:
Thank you so much. It worked just fine, I had issues on the first boot but I applied a factory reset and it solved.
I have 2 questions:
- Is it totally secure the sbf files from droid-developers? (I had never hear it before)
- I can't share my data conection, i don't have Internet on my computer through the phone
Click to expand...
Click to collapse
I really think that the sbf files are safe, there's no reason to think differently. It's not like they would put a worm on it, but I think they are pretty safe, coming from a leak.
About the data connection, did you try changing from open to WEP to WPA and so on?
davizera said:
I really think that the sbf files are safe, there's no reason to think differently. It's not like they would put a worm on it, but I think they are pretty safe, coming from a leak.
About the data connection, did you try changing from open to WEP to WPA and so on?
Click to expand...
Click to collapse
Ummmm, i didn't try that, but i have connection to the gateway IP (ping), but i can't go beyond it.
I have another issue, encryption for applications and disk doesn't work, I always get a black screen and never finish the process.
davizera said:
I really think that the sbf files are safe, there's no reason to think differently. It's not like they would put a worm on it, but I think they are pretty safe, coming from a leak.
Click to expand...
Click to collapse
Various components of the firmware need to be signed by Motorola in order to be flashable via fastboot. That's one of few pros of a locked bootloader.
rcdeoliveira said:
Ummmm, i didn't try that, but i have connection to the gateway IP (ping), but i can't go beyond it.
I have another issue, encryption for applications and disk doesn't work, I always get a black screen and never finish the process.
Click to expand...
Click to collapse
Try a different set if sbf files. You may have gotten a corrupt down load. Or possibly a modded set.
Sent from my DROID RAZR using xda app-developers app
sttierney said:
Try a different set if sbf files. You may have gotten a corrupt down load. Or possibly a modded set.
Click to expand...
Click to collapse
Mate, you clearly don't know what are you talking about - please stop giving wrong advice. There are checksums and digital signatures in place, which are verified by RSD Lite and phone prior to flashing, thus modified/damaged file won't be accepted by the device. Only genuine files, which were signed by Motorola, can be flashed to the phone in the fastboot mode.
@rcdeoliveira: With regard to your network issue, please debug your upstream connection - e.g. TTL. This feature definitely works for me. Regarding the whole device encryption, initial run may take up a lot of time, so be sure to leave the device at the "black screen" overnight attached to a charger.
I need help. I just bought used droid razr maxx. Then When I got home, i realize it cant be rooted,something bout the su binary cant be pushed?Then I did some research,and I realize,since my razr maxx is from china,it somehow is different? Anybody know how to change this? For god sake,I cant even install some simple apps such ass foursquare?? Can I just place Any region update files in the MicroSD n update?My firmware is GAS_ASIA_SPYDERICS_P008 n System version 67.213.906.XT910.ChinaRetail.en.CN . I read about flashing using fastboot but my pc cant detect my fone when in flashboot,why is that? All the drivers are already installed. Now I cant root or use custom ROM. T_T
[update 2] I just summarized a way to backup and restore (all based on other great DEV's work, just put in one place) your TS before your play with your TS here: http://forum.xda-developers.com/showthread.php?p=52820278#post52820278
Go check it if you plan to root your TS!
[update] With the help of cheahcl, I got the latest F/W for 4th List 1/8/2100. With the MTK SP_Flash_Tool, I was able to upload a corrected F/W for my TS and everything goes back to normal!
Thanks for cheahcl for his dump and Lokifish Marz for his All in one tools! You guys really saved my day! (and my TS).
A Quick summary: Do NOT use any method on XDA yet to root or change TWRP recovery! It seems the TS of 4th list is different in some way than the ones before which render most of stuffs here invalid. However, fear not to play around since now we have a way to go back to stock!
In my experience, I found that it's really difficult to truly brick a MTK based system. The system will just reject flashing at slightest sign that a F/W is not compatible. The only cache is you need to have the "correct" F/W specifically for your TS!
In my observation, OMate made changes between each delivery. For Example, the 4th list of 1/8/2100 is different in (At least F/W configuration) of the 3rd or earlier 1/8/2100.
------------------------below is my original story of what I tried and failed--------------------------
Just got mine (1/8/2100) 5 hrs ago! I am on the 4th list. The delivery in FAST!
The watch starts normally. I played with it for a while, than decided to root it, install TWRP and apply the security hack made by +Lokifish Marz
Now I have a brick! Just after 30 min I receive the watch!
<<Can anyone help me here?>>
First of all, in respecting to all great DEVs, I have NO intention to blame anyone else but myself. (I did this to my own watch!)
Second, I have been rooting Android since Cupcake day, so I am not a Noob... (or so I think...) I am very familiar with ADB/fastboot... and use almost daily.
So here is the guide to brick. If Anyone have any idea please help me out!
--------------------------------------------------------------------------------------------------
1st, I tried to use this tool to root+TWRP+scurity patch http://forum.xda-developers.com/showthread.php?t=2713183&page=2 knowing it's NOT tested against 1/8/2100. I just tried anyway... The script went with a lot of errors, it seems the script cannot locate correct files but still push the security patched files into the /system/app (and other places).
I turn on the watch, but it just stuck at boot logo (the orange "Truesmart" logo without animation)
Also, the Recovery is still stock, TWRP is no where to be seen.
Since ADB still works, I adb reboot couple times, pull the battery, let the watch run for 2hrs, etc... Nothing works. The watch just stuck at the boot logo.
Than I follow this thread http://forum.xda-developers.com/showthread.php?t=2641261 and http://forum.xda-developers.com/showthread.php?t=2641261 with Stock firmware downloaded from http://d-h.st/users/Lokifish Marz/?fld_id=30814#files (Omate_1-8_2100_TrueSmart_20140328.zip)
I installed all drivers, restarts my Win 7 (x86) pc (several times), and after several attempts the Flashtool just flash in the Firmware.
The Tools flash with a green Check mark, indicating everything is ok!
However the watch just become a brick after this....
Than this completed the brick process! Now the watch won't even turn on, when I try to use Flash tool again, it always say S_FT_ENABLE_DRAM_FAIL. Google this and you find it's due to flashing wrong F/W, but I don't know where went wrong!
Anyone else have same problem or it's just me? Anyone have solution?
You said everything...
You made mistake but that shouldn't be problem.
You soft brick it using wrong recovery image and root tool but as you said, you had adb and fastboot on - so if you know what are you doing and I see you know (except of that pary of flashing something that's not for your device .) you should be able to flash stock firmware back.
If you can flash another firmware, try with other firmware...
Don't know what else to say....
Omate build piece of sh*t and we'll all have problems with it...
It's very hard to differentiate devices.
All of them has same nr on mother boards and, as I said, we will all have problems with Omate and their TrueSh*t...
Sent from my C6903 using Tapatalk
funky0308 said:
You said everything...
You made mistake but that shouldn't be problem.
You soft brick it using wrong recovery image and root tool but as you said, you had adb and fastboot on - so if you know what are you doing and I see you know (except of that pary of flashing something that's not for your device .) you should be able to flash stock firmware back.
If you can flash another firmware, try with other firmware...
Don't know what else to say....
Omate build piece of sh*t and we'll all have problems with it...
It's very hard to differentiate devices.
All of them has same nr on mother boards and, as I said, we will all have problems with Omate and their TrueSh*t...
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Ha! Very true! I think you are right! I believe Omate have many segmentation on their HW/SW, even with same model number.... A lot of things changes between versions which makes the "factory image" not compatible....
Anyone has the latest (4th list) 1/8/2100 TS who could dump their whole image for me would be helpful...
I would like to help you but mine is 2nd list and it's still on customs office...
Omate shipment experts, you just gotta love them....
Sent from my C6903 using Tapatalk
Not sure what to tell you on this. A board revision change is possible as the Omate_1-8_2100_TrueSmart_20140328.zip was from a 1/8 2100. I can't even test stuff anymore as I gave one to a tech student that's studying network and system security and the other four were stripped down, reworked into data gathering modules and then donated to near space projects.
Lokifish Marz said:
Not sure what to tell you on this. A board revision change is possible as the Omate_1-8_2100_TrueSmart_20140328.zip was from a 1/8 2100. I can't even test stuff anymore as I gave one to a tech student that's studying network and system security and the other four were stripped down, reworked into data gathering modules and then donated to near space projects.
Click to expand...
Click to collapse
Thanks Lokifish for your comment... Is there anyway to get a latest F/W? If you know anyone I could contact, please PM me... Thanks!
Anyone have yet received a 1/8/2100 on 4th list could PM me a Factory F/W dump?
I tried another XP PC with all steps checked and rechecked but still... No luck...
Teach me how to do a dump and I'll dump it for you. I was also looking how to backup my stock firmware before playing around, seeing as no one has our version of firmware uploaded for restore yet.
Also received mine yesterday and firmware version is 20140513, pretty damn recent.
You guys are going to have to help each other out on this one. I've already deleted 90% of any and all Android dev stuff from my personal file server and computer. This includes tools, guides and work going as far back as the original HTC Evo.
cheahcl said:
Teach me how to do a dump and I'll dump it for you. I was also looking how to backup my stock firmware before playing around, seeing as no one has our version of firmware uploaded for restore yet.
Also received mine yesterday and firmware version is 20140513, pretty damn recent.
Click to expand...
Click to collapse
Thanks a lot! First of all, Currently don't do anything posted on XDA yet since most of them will not work with this version of TS... (This is where I am now...)
First of all, please get all necessary tools directly from this post "All Tools" http://forum.xda-developers.com/showthread.php?t=2734687 (Do NOT download or install any other things there!)
Follow those steps: (modified from link above)
1. Download "All Tools"
2. Install Universal ADB Drivers (included in All Tools) <--If you already have ADB up and running, it's not necessarily, then.
3. Enable USB Debugging on watch
4. Launch MTKDroid Tools
5. Connect watch to PC
6. Please follow the instruction from here: http://www.chinaphonearena.com/foru...up-MTK6592-MTK6589-MTK6577-and-all-MTK-Phones
a. Skip everything above and just starts from "B) Open ADB prompt to begin communication with the phone" .
b. Don't worry about the recovery thing... TS comes with a recovery which is not locked and you can do everything this article said with only stock recovery. (also no busy box is needed, nor su since TS run everything in root!)
c. You could also refer to the video guide below for details
7. it's okay to just provide the file you got after finishing the step "C) Read back the ROM with MTK Droid Tools" I should be able to do the Step D) and after myself.
Thanks a lot for your help!
Lokifish Marz said:
You guys are going to have to help each other out on this one. I've already deleted 90% of any and all Android dev stuff from my personal file server and computer. This includes tools, guides and work going as far back as the original HTC Evo.
Click to expand...
Click to collapse
Dear Lokifish,
Could you please still keep those tools on the host servers so people can still access them? (Like "All tools", etc.) Please...... (I need a emoticon of a small kitten with big eyes here...)
Thanks!
ok will get it to tonight. about 6 hours time. cheers
lssong99 said:
Dear Lokifish,
Could you please still keep those tools on the host servers so people can still access them? (Like "All tools", etc.) Please...... (I need a emoticon of a small kitten with big eyes here...)
Thanks!
Click to expand...
Click to collapse
The space was given to me for free as a recognized developer and contributor. Seeing that I have left development completely, it is not right that I continue to use the services. So at the end of the week the files will be purged and I will ask the xda remove my developer and contributor status.
Lokifish Marz said:
The space was given to me for free as a recognized developer and contributor. Seeing that I have left development completely, it is not right that I continue to use the services. So at the end of the week the files will be purged and I will ask the xda remove my developer and contributor status.
Click to expand...
Click to collapse
Oh! I see the situation... In this case, may I have your permission to host those files somewhere (maybe by XDA moderator, or ...me?) so they could still be accessible?
I could feel your feeling on this fiasco. Must be quite frustrate experiences for you...
lssong99 said:
Oh! I see the situation... In this case, may I have your permission to host those files somewhere (maybe by XDA moderator, or ...me?) so they could still be accessible?
I could feel your feeling on this fiasco. Must be quite frustrate experiences for you...
Click to expand...
Click to collapse
https://dl.dropboxusercontent.com/u/25414599/!Files_to_FlashTool.rar
I've done step D as well, good to just flash it I guess.
Let me know if it worked, before I start messing about. I'm not good in all these stuff. Been flashing since HD2 days but still, just a tutorial follower, can probably count Linux commands I know with 1 hand.
cheahcl said:
https://dl.dropboxusercontent.com/u/25414599/!Files_to_FlashTool.rar
I've done step D as well, good to just flash it I guess.
Let me know if it worked, before I start messing about. I'm not good in all these stuff. Been flashing since HD2 days but still, just a tutorial follower, can probably count Linux commands I know with 1 hand.
Click to expand...
Click to collapse
Dear cheahcl,
Thank you soooo much for the image! I successfully restored my TS and now EVERYTHING GOES BACK TO NORMAL!
If you want to play around, please don't forge to back up your IMEI! since the MTK SP_Flash_Tool will wipe your IMEI!
Please follow this guide here: http://forum.xda-developers.com/showthread.php?t=2631953 under "IMEI Backup Procedure" before proceed anything dangerous!
After this, you are good to go! MTK is non-brickable (from what I learned for the past day... All you need is a corrected factory F/W!)
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!!
lssong99 said:
Dear cheahcl,
Thank you soooo much for the image! I successfully restored my TS and now EVERYTHING GOES BACK TO NORMAL!
If you want to play around, please don't forge to back up your IMEI! since the MTK SP_Flash_Tool will wipe your IMEI!
Please follow this guide here: http://forum.xda-developers.com/showthread.php?t=2631953 under "IMEI Backup Procedure" before proceed anything dangerous!
After this, you are good to go! MTK is non-brickable (from what I learned for the past day... All you need is a corrected factory F/W!)
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!!
Click to expand...
Click to collapse
don't sweat it, haha i needed to backup my original firmware as well anyways, seeing how scarce it is around here and all the weird discrepancies in HW/SW versions. good to know i can always fall back on this file. haha yeah i've also backed up my imei. time to play around and see.
cheers
Ive managed to get my brand new watch stuck in a bootloop after using framaRoot to root it. (I know, I know)
Now, I am able to boot into recovery mode or factory, and tried a factory reset. No luck, so i'm pretty sure the issue is in the /system partition.
Does anyone know if there are zip files somewhere that i can flash from recovery, to restore the system partition?
Device:
- 1GB / 8GB / 2100MHz Version
- Originally unrooted
- OUI 2.1
- Modem Ver: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
- No other modifications besides the rooting (which did work already before I rebooted)
Spoetnicus said:
Ive managed to get my brand new watch stuck in a bootloop after using framaRoot to root it. (I know, I know)
Now, I am able to boot into recovery mode or factory, and tried a factory reset. No luck, so i'm pretty sure the issue is in the /system partition.
Does anyone know if there are zip files somewhere that i can flash from recovery, to restore the system partition?
Device:
- 1GB / 8GB / 2100MHz Version
- Originally unrooted
- OUI 2.1
- Modem Ver: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
- No other modifications besides the rooting (which did work already before I rebooted)
Click to expand...
Click to collapse
The TS (or any MTK based system) does not use the usually "recovery backup/restore" way we familiar of, instead it goes the "special tool on PC backup/restore" method. You need ask people who receive their watch in around the same time as yours with same configuration to backup their watch FW with MTK tools than restore with said FW.
Basically what I had done in this thread!
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Sent from my HTC_One_max using XDA Premium HD app
lssong99 said:
The TS (or any MTK based system) does not use the usually "recovery backup/restore" way we familiar of, instead it goes the "special tool on PC backup/restore" method. You need ask people who receive their watch in around the same time as yours with same configuration to backup their watch FW with MTK tools than restore with said FW.
Basically what I had done in this thread!
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Sent from my HTC_One_max using XDA Premium HD app
Click to expand...
Click to collapse
Thanks!
Im pretty sure that I was on 'Omate_TrueSmart_20140513.103530_V2.0' before I bricked it, so that gives hope
I dont have it with me right now, but Ill try it as soon as I get back home on monday
Thanks again for the tutorials and reply
lssong99 said:
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Click to expand...
Click to collapse
HEY! It worked
I'm back at a functional Truesmart
Thank you soo much
And in case three smiley's aren't enough:
Also, quick note for other people bricking their phone, my issue (after I bricked it again), was that I used an app to change the density property, which broke the boot of the watch.
The app that broke my watch was: https://play.google.com/store/apps/details?id=com.birdapi.android.dpi
Ok so I got the samsung galaxy light from metro running 4.4.2 and I decided to root my phone got myself rooted but I used some**** that changdd my phone from metro to tmobile and I guess my pho j e is locked now and its on 4.2.2 and im a iphone guy and dont really understandwhat I did but any help with gettjng my phone back would really be awesome
themilkboy08 said:
Ok so I got the samsung galaxy light from metro running 4.4.2 and I decided to root my phone got myself rooted but I used some**** that changdd my phone from metro to tmobile and I guess my pho j e is locked now and its on 4.2.2 and im a iphone guy and dont really understandwhat I did but any help with gettjng my phone back would really be awesome
Click to expand...
Click to collapse
What?
I have a Galaxy Light, and I'm fairly knowledgeable about the device. But I don't understand gibberish. You need to tell us exactly what you did, and try to speak in English without typos.
Ok
Lol sorry, I rooted my phone, well I put twrp on my phone the flashed it with I guess a flash for tmobile and on jellybean instead of kitkat. I tried to flash the radio but dont think it did anything. And now I reboot my phone and its asking for the sim pin
themilkboy08 said:
Lol sorry, I rooted my phone, well I put twrp on my phone the flashed it with I guess a flash for tmobile and on jellybean instead of kitkat. I tried to flash the radio but dont think it did anything. And now I reboot my phone and its asking for the sim pin
Click to expand...
Click to collapse
Which TWRP did you flash? Did you flash T-Mobile firmware? I need to know EXACTLY what you did.
Ok
I used twrp 2.7.0.0-gardaltetmo.tar. The flashed a supers u update -v 1.94.zip, then I wanted to know how to unroot incase I needed to know and used SGH-t399-stock-MJA.ZIP
themilkboy08 said:
I used twrp 2.7.0.0-gardaltetmo.tar. The flashed a supers u update -v 1.94.zip, then I wanted to know how to unroot incase I needed to know and used SGH-t399-stock-MJA.ZIP
Click to expand...
Click to collapse
Don't use T-Mobiles firmware on your MetroPCS phone.
This is what you need to do.
And for the love of all that is good in this world, next time DO A BACKUP before flashing things. You installed TWRP, which gives you the ability to make a complete backup of your system exactly as it is at that point in time. If you had done a back-up before you screwed up your phone, it would have taken you but a few minutes to unscrew it.
I apologize for being harsh, but it seems to me like you really need to read and research a lot more. I always (well, usually...almost bricked my tablet the other day) read everything I can find about something potentially risky before doing it. Let this be a learning experience for you. Read as much as you can, understand what it is you are actually doing rather than just following some guide, and if you don't understand, just ask. I and most of us here would rather you asked a noobish question instead of going blindly ahead and screwing your phone up. Playing around with root and recovery and flashing without understanding it is like thinking you can perform open heart surgery with a meat cleaver because you've seen every episode of ER, Scrubs, and Grey's Anatomy.
thanks
ok thanks alot btw. just now got the files downloaded but im in twrp and the files are on my pc how could i get them to my phone? and i dont have a sd card either
themilkboy08 said:
ok thanks alot btw. just now got the files downloaded but im in twrp and the files are on my pc how could i get them to my phone? and i dont have a sd card either
Click to expand...
Click to collapse
Hm. I didn't think about that. I think you might need to get an SD card. Go on Amazon or eBay and pick one up. An 8GB one can be had for literally a few bucks, but a 64GB class 10 one for $35 is an awesome thing too.
Ok
Ok, and with the back up download how do I get the in twrp. Should I put it in a zip file or leave it how it is
ok im a retard
Planterz said:
Hm. I didn't think about that. I think you might need to get an SD card. Go on Amazon or eBay and pick one up. An 8GB one can be had for literally a few bucks, but a 64GB class 10 one for $35 is an awesome thing too.
Click to expand...
Click to collapse
ok so i cannot figure out how to do this.
i have the sgh-t399n galaxy light- with no os installed, i have twrp on my phone. and i have a backup a sd card. but when i go to restore in twrp the backup isnt there, and ive tried going threw the file options to move it to where is it suposed to go but no such luck. i thought maybe a terminal command would work but i have no clue what command to use. if you could help one more time that would be awesome
You can always use Samsung Kies 3 to flash your phone back to stock. You need your serial number though, and for some reason it is not printed on the back of the device(at least for me). A call to tech support should get that sorted anyway.
Alternatively, you can do this with Odin to a very similar effect. Search Google for something like "T399NUVUANK3 tar" to get the file you need, my personal backup is corrupt so I can't share.
fddm said:
You can always use Samsung Kies 3 to flash your phone back to stock. You need your serial number though, and for some reason it is not printed on the back of the device(at least for me). A call to tech support should get that sorted anyway.
Alternatively, you can do this with Odin to a very similar effect. Search Google for something like "T399NUVUANK3 tar" to get the file you need, my personal backup is corrupt so I can't share.
Click to expand...
Click to collapse
Ugh... I own a t399n and I'm doing some real development on it. . I've made a stock odex and deodexed rooted zip files for the t399n and haven't posted them yet. . If you're in a bad way still hit me up and I'll have you up and running in no time. Fun things coming for metro users. Who says you have to pay for a high end device to have a high end device? He he he....
Do you have a backup I bicked my samsung galaxy light metropcs then I unbricked it by restoring a backup for the samsung galaxy light that I found online. Search fresh backup for samsung galaxy light sgh t399n.
Planterz said:
Which TWRP did you flash? Did you flash T-Mobile firmware? I need to know EXACTLY what you did.
Click to expand...
Click to collapse
You're quite uppity, aren't you? I had no trouble understanding exactly what he did.
reholli said:
You're quite uppity, aren't you? I had no trouble understanding exactly what he did.
Click to expand...
Click to collapse
Are you seriously giving me crap about a post from over a year ago? Nice contribution to the discussion.:good: I have no idea if the OP ever fixed his phone, but at least I tried to help.
Planterz said:
Are you seriously giving me crap about a post from over a year ago? Nice contribution to the discussion.:good: I have no idea if the OP ever fixed his phone, but at least I tried to help.
Click to expand...
Click to collapse
And the age of the post, with respect to your attitude, is relevant how?
reholli said:
And the age of the post, with respect to your attitude, is relevant how?
Click to expand...
Click to collapse
I just love getting an email alert at 4am because someone quoted me to post absolutely nothing of substance.
It's relevant because IT WAS A YEAR AGO! I don't remember why I was so cranky that day. I did apologize to him for it. Did you notice that I also still did my best to help him? Do you have a solution to his problem? Does he even still have this phone, given that it was a year ago? If you want to fixate on my posts, fixate on the hundreds of times I've been thanked for helping others, especially going above and beyond helping people find the perfect device for them. I'm not here to be grumpy, I'm here to help people, and get help when needed. Why are you here? To pester me? Look, I respect my elders, and you're clearly older, but at the same time don't presume to talk down to me. Try reflecting on yourself and your motive in making a useless post, bumping a thread dead for several months (a severe breach of netiquette), purely to insult another member.
Come to think of it, my email alert wasn't because I was quoted (I have that feature turned off). I got the alert because I'm still subscribed to this thread, having done so in case there were new posts that might enable me to help the OP. I suppose I should unsubscribe, giving the fact that nobody has posted anything of use or substance in 7 months or so.
Hi
I read most of the threads here before about the internal memory can't be mounted issue, but nothing seems to work for me. I can't even figure out which ruu I should download, bacause i bought my phone used and unlocked. I saw it somewhere in android that it was telus, but I downloaded tons of ruu-s and nothing works.
The issue started like 2 years ago and I tried everything I could find online and now my other phone broke I pulled the amaze out again to try to bring it back to life. I took a photo when the battery died and I believe it was using the internal memory that time.
All the info I can get is what it says in the bootloader because I relocked it.
I tried ADB, Linux, and the RUU way and maybe I do something wrong... thats why I ask for help here
The device is S-On hboot is 1.93.0002 so its ICS
I used it on Wind Mobile (Canada) network, but I believe it came from Bell
Also I have some more info from Image CRC, but thats hexa decimal that doesn't mean me anything
So something must be wrong with the partitions, but there's no way I can reach it and partition it again at the second.
If anyone can help me than please do it.
Also I'm not really a pro in Adb and linux and stuff like that. The adb commands don't seem to work, but the fastboot ones do. adb devices doesn't print any connected devices.
kiskisboki said:
Hi
I read most of the threads
If anyone can help me than please do it.
Click to expand...
Click to collapse
Start here:
http://forum.xda-developers.com/amaze-4g/help/qa-htc-unbricking-project-t2966472
pbergonzi said:
Start here:
http://forum.xda-developers.com/amaze-4g/help/qa-htc-unbricking-project-t2966472
Click to expand...
Click to collapse
Thanks. I read that page before, but didn't see the link to the actual thread, so the whole thing didn't make sense... now it does.
Anyways, I believe I have the Linux live cd that they suggested not to use so I stuck at the brickdetect part. Im trying tho
Yes hi, I just got a new Huawei Mediapad M5, and I tried to purchase a code to unlock the bootloader, but they said the firmware on my tablet is too new, and that I would need to downgrade to a firmware from before July 2018 first. But I don't know how to do that, nor where to find the firmware.
I'm good with tablets so I'll be able to do it, but I need to know how to first. Thank you
Okay so quick update, my m5 is the CMR-W09. I downloaded the c432 version of it and unzipped everything, put in in the sd card root folder, and did the power/vol up/vol down button combo and it failed without even starting.
So I tried several other versions of the firmware that I found elsewhere. Trying things several different ways of doing with each one, and no matter what I tried, which was pretty much every version of the way to do this mentioned in the past two months on the bootloader guide thread, and every single one of them got the same failure message, so I seriously do not know what to do. Please help. What am I doing wrong?
Okay so thank you everyone for all the help you've provided, they said sarcastically. But after three days of trying about a hundred different methods, I have officially given up on trying to downgrade the firmware on my tablet.
I've tried so many different methods listed in the guide on this forum, and other methods I found elsewhere.
I tried multiple firmware versions, of both sht and cmr, and none of them have worked.
I've put the dload folder with everything unzipped inside it and that didn't work, I tried with the zips still zipped inside, nope. I tried the dload folder with nothing in it but the update.app file. That is the only time anything happened by the way. It gets to five percent, and then immediately fails, no matter how many times I try, or how many different firmware's I do said method with, it always fails at five percent.
I even spent 17 dollars to join Easy Firmware so I could get one of the firmware versions they had that I couldn't find anywhere else. And same thing.
So I don't know what it is, maybe the firmware that came preinstalled on my tablet is a newer version that doesn't allow downgrading anymore, that's the most likely thing I can think of anyway. But yeah, it ain't happening for me.
So unless anyone has any words of advice, or an idea on what might be going on, please close this thread for me, it's existence is now pointless.
ElsaReyes said:
Okay so thank you everyone for all the help you've provided, they said sarcastically. But after three days of trying about a hundred different methods, I have officially given up on trying to downgrade the firmware on my tablet.
I've tried so many different methods listed in the guide on this forum, and other methods I found elsewhere.
I tried multiple firmware versions, of both sht and cmr, and none of them have worked.
I've put the dload folder with everything unzipped inside it and that didn't work, I tried with the zips still zipped inside, nope. I tried the dload folder with nothing in it but the update.app file. That is the only time anything happened by the way. It gets to five percent, and then immediately fails, no matter how many times I try, or how many different firmware's I do said method with, it always fails at five percent.
I even spent 17 dollars to join Easy Firmware so I could get one of the firmware versions they had that I couldn't find anywhere else. And same thing.
So I don't know what it is, maybe the firmware that came preinstalled on my tablet is a newer version that doesn't allow downgrading anymore, that's the most likely thing I can think of anyway. But yeah, it ain't happening for me.
So unless anyone has any words of advice, or an idea on what might be going on, please close this thread for me, it's existence is now pointless.
Click to expand...
Click to collapse
Ive downgraded using the comments on this thread https://forum.xda-developers.com/mediapad-m5/how-to/bootloader-unlock-guide-t3781275 and then ive unlocked the bootloader using dc unlocker, to know exacly how to downgrade, read all the comments especially the new of them, do not give it up
Seek and you will be found
THE MAXIMUM POWER said:
Ive downgraded using the comments on this thread https://forum.xda-developers.com/mediapad-m5/how-to/bootloader-unlock-guide-t3781275 and then ive unlocked the bootloader using dc unlocker, to know exacly how to downgrade, read all the comments especially the new of them, do not give it up
Seek and you will be found
Click to expand...
Click to collapse
That's the thing though. I have read through every comment in that thread, and tried every single method listed and not a single one works for me.
The furthest it ever gets is 5 percent and then it fails. So I really don't know what's going on with my tablet. I just won't let me downgrade it.
Do you think you can give me a quick play by play on how you did it?
ElsaReyes said:
That's the thing though. I have read through every comment in that thread, and tried every single method listed and not a single one works for me.
The furthest it ever gets is 5 percent and then it fails. So I really don't know what's going on with my tablet. I just won't let me downgrade it.
Do you think you can give me a quick play by play on how you did it?
Click to expand...
Click to collapse
Keep in mind that you need to downgrade to the last version of yours(e. G. You are in the. 196 then you should downgrade to the. 195 and then.. 193 and not directly from. 196 to. 193
My device is CMR-W09C432 Which is MediaPad M5 10.8inch Only wifi EU version, ive downloaded the same firmware of my device (only full otas) which is called update.zip,
I unzipped it
Put it in the root of your sdcard in dload folder (first create a folder in your sdcard called dload, then put ONLY update.app inside dload folder)
It is going to be like this dload/Update.app
Reboot and press and hold volume buttons and power button at the same time
Thats it
Plz write to me if you need any further assistance, i will be glad to help you as i was at the same position as yours
THE MAXIMUM POWER said:
Keep in mind that you need to downgrade to the last version of yours(e. G. You are in the. 196 then you should downgrade to the. 195 and then.. 193 and not directly from. 196 to. 193
My device is CMR-W09C432 Which is MediaPad M5 10.8inch Only wifi EU version, ive downloaded the same firmware of my device (only full otas) which is called update.zip,
I unzipped it
Put it in the root of your sdcard in dload folder (first create a folder in your sdcard called dload, then put ONLY update.app inside dload folder)
It is going to be like this dload/Update.app
Reboot and press and hold volume buttons and power button at the same time
Thats it
Plz write to me if you need any further assistance, i will be glad to help you as i was at the same position as yours
Click to expand...
Click to collapse
Okay thank you thank you thank you. I haven't yet tried this method as I just saw this message, but it's one I haven't seen before so I'm going to try it and hopefully it'll work. But just have one small question.
My M5 is the CMR-W09C567.
I'm in 190 right now, that's what my tab came as. But using Firmware Finder, the only ones I see before it are 175, 167, and 156. Are those the only ones that came before? Or should I actually be looking for versions like 189, 188 and so on? Just making sure I'm not misunderstanding anything.
ElsaReyes said:
Okay thank you thank you thank you. I haven't yet tried this method as I just saw this message, but it's one I haven't seen before so I'm going to try it and hopefully it'll work. But just have one small question.
My M5 is the CMR-W09C567.
I'm in 190 right now, that's what my tab came as. But using Firmware Finder, the only ones I see before it are 175, 167, and 156. Are those the only ones that came before? Or should I actually be looking for versions like 189, 188 and so on? Just making sure I'm not misunderstanding anything.
Click to expand...
Click to collapse
Sorry for my late answer
First download the full ota mf version 175 as the first attachment shows
Second step is to download the update.zip (2 attachment)
Then unzip the update.zip file and copy paste the update.app inside dload folder at the root of your sdcard
hopefully this step is going to work, BUT BE AWARE THAT IF DOWNGRADE WAS SUCCESSFUL, YOU ARE GOING TO LOSE ALL YOUR DATAS SO MAKE A BACKUP BEFORE DOING IT
Then try to use dc unlocker after putting the usb settings to manufacture mode
THE MAXIMUM POWER said:
Sorry for my late answer
First download the full ota mf version 175 as the first attachment shows
Second step is to download the update.zip (2 attachment)
Then unzip the update.zip file and copy paste the update.app inside dload folder at the root of your sdcard
hopefully this step is going to work, BUT BE AWARE THAT IF DOWNGRADE WAS SUCCESSFUL, YOU ARE GOING TO LOSE ALL YOUR DATAS SO MAKE A BACKUP BEFORE DOING IT
Then try to use dc unlocker after putting the usb settings to manufacture mode
Click to expand...
Click to collapse
Nah see, it still won't downgrade for me, it doesn't make any sense like I said.
I clicked the full ota version of 175 like you said, and on the page that came up, I clicked the word download, and of the three files that showed up, I choose to download just the update.zip
I unzipped the update.zip file and moved the update.app file into the dload folder on the root of my sd card.
And then I turned off my tablet, and held down the vol up, vol down, and power button all at the same time until the device booted into a screen that just had the EMUI logo.
Several phrases flashed by beneath it, before it said it was installing the update, but the update sticks at 5 percent, and after being stuck like that for several seconds, it just gives up and I'm left with the Software Install Failed screen once again.
I just don't get it. Do I need to have the SD Card formatted a certain way? Can there be no other files on it besides the dload folder and update file? Is there a setting I don't have turned on that I need on??
Small update, I just tried flashing an actual update instead of a downgrade, and the same exact thing happened.
I'm starting to think that I'm doing nothing wrong and in actuality it's a problem with my tablet.
ElsaReyes said:
Small update, I just tried flashing an actual update instead of a downgrade, and the same exact thing happened.
I'm starting to think that I'm doing nothing wrong and in actuality it's a problem with my tablet.
Click to expand...
Click to collapse
There is another way to flash, which is should work, download all the 3 files (as the 2 attachment shows) and without unzipping any folder, put them instead of Update.app.
It is going to be like the first attachment (yours should read usa instead of eu)
This method should work
THE MAXIMUM POWER said:
There is another way to flash, which is should work, download all the 3 files (as the 2 attachment shows) and without unzipping any folder, put them instead of Update.app.
It is going to be like the first attachment (yours should read usa instead of eu)
This method should work
Click to expand...
Click to collapse
Nope. Now it doesn't even start to install. It just immediately goes Software install failed the second the EMUI logo shows up.
I really think there just might be something very wrong with my tablet, cause something should have worked by now.
ElsaReyes said:
Nope. Now it doesn't even start to install. It just immediately goes Software install failed the second the EMUI logo shows up.
I really think there just might be something very wrong with my tablet, cause something should have worked by now.
Click to expand...
Click to collapse
Ive heard about a method from TeamMT which allows you to downgrade even with a locked bootloader, keep in mind that you need to install ONLY the version of hisuite that is in the videos description
Take a look here https://youtu.be/xFCLpgGZEJM
If it did not work, try the dns method which is in FirmwareFinder app, you need to change your router dns in order to get the firmware through eRecovery
THE MAXIMUM POWER said:
Ive heard about a method from TeamMT which allows you to downgrade even with a locked bootloader, keep in mind that you need to install ONLY the version of hisuite that is in the videos description
Take a look here https://youtu.be/xFCLpgGZEJM
If it did not work, try the dns method which is in FirmwareFinder app, you need to change your router dns in order to get the firmware through eRecovery
Click to expand...
Click to collapse
Okay I don't know what's going on here, but I downloaded that version of hisuite that it lists. And I followed the instructions on how to connect to it. And it connects, but then immediately disconnects. And then connects again and so on and so on. It just keeps connecting then disconnecting.
I really really really appreciate all the hell your giving me, it means more then you can know, but I'm really starting to believe that there is something wrong with my tablet. One of these methods should have worked by now right?
ElsaReyes said:
Okay I don't know what's going on here, but I downloaded that version of hisuite that it lists. And I followed the instructions on how to connect to it. And it connects, but then immediately disconnects. And then connects again and so on and so on. It just keeps connecting then disconnecting.
I really really really appreciate all the hell your giving me, it means more then you can know, but I'm really starting to believe that there is something wrong with my tablet. One of these methods should have worked by now right?
Click to expand...
Click to collapse
I believe that there is not any kind of problems with your device, it is just you might missed something as all m5s are equals except the vendor which has nothing to do with failing downgrade operations.
Try the DNS method from Firmware finder and this should work as it send the choosed firmware to the eRecovery, for more infos choose (Get and update via eRecovery), this method is supposed to work with all EMUIs (3,4,5 and 8)
Write to me if it worked out
THE MAXIMUM POWER said:
I believe that there is not any kind of problems with your device, it is just you might missed something as all m5s are equals except the vendor which has nothing to do with failing downgrade operations.
Try the DNS method from Firmware finder and this should work as it send the choosed firmware to the eRecovery, for more infos choose (Get and update via eRecovery), this method is supposed to work with all EMUIs (3,4,5 and 8)
Write to me if it worked out
Click to expand...
Click to collapse
Sorry but nope...
I changed the DNS number in the wifi settings to the one it gives. And still when I start into eRecovery, the only update it offers is the latest and not the one I choose...
ElsaReyes said:
Sorry but nope...
I changed the DNS number in the wifi settings to the one it gives. And still when I start into eRecovery, the only update it offers is the latest and not the one I choose...
Click to expand...
Click to collapse
Sorry, i do not have any more infos about this specific situation all i can do is to advice you to reread through the unlock bootloader thread (the one ive sent you before) as i used some advices in the comments section which helped me to do a successful downgrade in order to unlock the bootloader
Try again and again and do not give it up?
THE MAXIMUM POWER said:
Sorry, i do not have any more infos about this specific situation all i can do is to advice you to reread through the unlock bootloader thread (the one ive sent you before) as i used some advices in the comments section which helped me to do a successful downgrade in order to unlock the bootloader
Try again and again and do not give it up
Click to expand...
Click to collapse
Thanks for all your help. But honestly I think it'd be best if I just gave up. I don't want to, but clearly the universe does not want me downgrading this stupid thing.. lol
And as I said, already read through that entire thread and followed every bit of advice in it.
ElsaReyes said:
Thanks for all your help. But honestly I think it'd be best if I just gave up. I don't want to, but clearly the universe does not want me downgrading this stupid thing.. lol
And as I said, already read through that entire thread and followed every bit of advice in it.
Click to expand...
Click to collapse
Through trial and errors you should be able to do it, try rebranding your device to the European version through funkyhuawei
THE MAXIMUM POWER said:
Through trial and errors you should be able to do it, try rebranding your device to the European version through funkyhuawei
Click to expand...
Click to collapse
Just wasted 44 dollars on a pass for the funkyhuawei site and it won't let me rebrand without first being unlocked.
Unlocking my tablet is why I want to downgrade.
Yeah I'm done. I really appreciate all your help, I really do, But I've now spent over 60 dollars trying to get this thing downgraded only to fail every single time, so I'm done.