Decided to create a new thread, since it covers a different topic. I'm trying to create TWRP for the MOQI I7S which has a Qualcomm Snapdragon 710. I've tried various tutorials on porting TWRP, but it ends up with the MOQI being stuck at the boot logo. Is there any way someone can help me, or someone can just port TWRP for me? I have an older firmware which should suffice for making TWRP.
Firmware: https://drive.google.com/file/d/1Hne3x3LY1LnKgurlNYK8trr-wHPD1fCD/view
Sorry for the double post but I need a favor from any user with a MOQI I7S. I need to extract files boot_a.bin and boot_b.bin using QFIL, but they need to be as clean as possible, so I can't use mine. It could help me with rooting the device without issues and eventually install TWRP for everyone. PM me if you need help with extracting those files.
Hello. I hope its not too late and you still can do this ? I've got mine i7s near a month ago and before doing anything else I dumped backup from it. Too bad, that for this phone there are no firmwares, so this was my first action for it. I uploaded files you asked as attachments
All this time I use mine device with magisk root without any problems, so, I guess, root through boota is quite safe and stable. I also have uploaded magisk-modified boot, if you'll need it
One thing I want to add: I hadn't succeeded to use QFIL version you'd uploaded. Had succeeded with tool QPST_2.7.496
I hope this will help!
SmashMan4 said:
Decided to create a new thread, since it covers a different topic. I'm trying to create TWRP for the MOQI I7S which has a Qualcomm Snapdragon 710. I've tried various tutorials on porting TWRP, but it ends up with the MOQI being stuck at the boot logo. Is there any way someone can help me, or someone can just port TWRP for me? I have an older firmware which should suffice for making TWRP.
Firmware: https://drive.google.com/file/d/1Hne3x3LY1LnKgurlNYK8trr-wHPD1fCD/view
Click to expand...
Click to collapse
Hi, I'm looking for the firmware for moqi i7s.
Can you share the file again?It's unavaliable now.
Thanks!
0jmaster0 said:
Hello. I hope its not too late and you still can do this ? I've got mine i7s near a month ago and before doing anything else I dumped backup from it. Too bad, that for this phone there are no firmwares, so this was my first action for it. I uploaded files you asked as attachments
All this time I use mine device with magisk root without any problems, so, I guess, root through boota is quite safe and stable. I also have uploaded magisk-modified boot, if you'll need it
One thing I want to add: I hadn't succeeded to use QFIL version you'd uploaded. Had succeeded with tool QPST_2.7.496
I hope this will help!
Click to expand...
Click to collapse
Hi, I'm looking for the firmware for moqi i7s.
Can you share the firmware for this device?
Thanks!
Kasct said:
Hi, I'm looking for the firmware for moqi i7s.
Can you share the firmware for this device?
Thanks!
Click to expand...
Click to collapse
Hi. I have uploaded dump of my phone here: https://drive.google.com/file/d/1h0_6qW3eE5OacfqXazsBHuxPUP7v73az/view?usp=sharing
This archive have all files dumped from phone after buying, except userdata file for now. Despite this file is almost empty, its size is ~60Gb so I can't upload it anywhere.
Also, archive containts png with partitions addresses.
WARNING: as I understand, simple flashing of these files can replace your phone IDs and other serial numbers! In that case phone can not boot at all. If I'm wrong, correct me, please. Hope it'll help
PS: Better try asking manufacturer for the correct firmware files
Hello there anyone abe to upload the firmware files, can't find them anywhere......my i7s is currently a nice paperweight!
Related
Hi all, I have a TS 1/8/2100, firmware 20140513.
TWRP and Bluetooth tether ROM are available for firmware 20140328 only. Past conversations make me think there won't be any update soon.
A solution would be to install previous firmware, then TWRP, then update firmware. But partitions changed in between.
According to this SP Flash Tool can also physically format a partition if you can get a partition management table (PMT). The scatter file describes logical partitions, but it seems you can also add PMT. (After backup with MTKDroidTool, click "prepare Blocks for FlashTool")
Knowing this, provided that hardware is relatively unchanged, it could be possible for newest TS to enjoy TWRP happiness.
I would like to try, if someone could be kind enough to give me a stock backup for TS 1-8-2100 firmware 20140328 with PMT. (there sould be a file called MT6572_Android_scatter_emmc_PMT.txt)
I need you to help me help you to help me help you.
thx.
MrTip said:
Hi all, I have a TS 1/8/2100, firmware 20140513.
TWRP and Bluetooth tether ROM are available for firmware 20140328 only. Past conversations make me think there won't be any update soon.
A solution would be to install previous firmware, then TWRP, then update firmware. But partitions changed in between.
According to this SP Flash Tool can also physically format a partition if you can get a partition management table (PMT). The scatter file describes logical partitions, but it seems you can also add PMT. (After backup with MTKDroidTool, click "prepare Blocks for FlashTool")
Knowing this, provided that hardware is relatively unchanged, it could be possible for newest TS to enjoy TWRP happiness.
I would like to try, if someone could be kind enough to give me a stock backup for TS 1-8-2100 firmware 20140328 with PMT. (there sould be a file called MT6572_Android_scatter_emmc_PMT.txt)
I need you to help me help you to help me help you.
thx.
Click to expand...
Click to collapse
Here you go - hope it's what you're looking for..
Tigerite said:
Here you go - hope it's what you're looking for..
Click to expand...
Click to collapse
No, it's not. The key element of my message is
with PMT. (there sould be a file called MT6572_Android_scatter_emmc_PMT.txt)
Click to expand...
Click to collapse
Thank you anyway.
That's all that was generated by the tool I'm afraid, I followed the steps from the link you provided too, but still no joy. It only produces the standard one, no PMT suffix.
Tigerite said:
That's all that was generated by the tool I'm afraid, I followed the steps from the link you provided too, but still no joy. It only produces the standard one, no PMT suffix.
Click to expand...
Click to collapse
That's unfortunate. Did you click on "prepare Blocks for FlashTool" after backup ? I'll try myself asap to confirm the procedure.
Yes I did, but no PMT text file in the relevant folder..
Tigerite said:
Yes I did, but no PMT text file in the relevant folder..
Click to expand...
Click to collapse
Well, the procedure is correct. It appears that PMT can be (or not) in scatter file without any difference in the filename. So you have to check by yourself, as I did, if you want to format. (look for many lines per partition, like 'physical_start_addr' and 'linear_start_addr')
You have to select "format+download" in "sp flash tools" to format everything (including preloader, so be carefull).
Take all precautions: Backup everything, including userdata and cache partition, because sp flash tools will ask for it if you have to format. Do not forget to backup nvram.
Doing this, I successfully formatted the TS and installed previous firmware, 20140328.
Sadly, the TS won't boot. Here lies my hope to get TWRP and bt tether ROM working without update from its creator...
So, back to firmware 20140513.
After the new format+backup, TS boot normally, but I had a "IMEI invalid" error. So, I used MTKdroidtools to restore nvram the same way I previously backed it up.
Complete 'format+download' is to be used if you messed up with partitions or if partitions changed.
Could be usefull, this was to let you know how.
MrTip said:
Well, the procedure is correct. It appears that PMT can be (or not) in scatter file without any difference in the filename. So you have to check by yourself, as I did, if you want to format. (look for many lines per partition, like 'physical_start_addr' and 'linear_start_addr')
You have to select "format+download" in "sp flash tools" to format everything (including preloader, so be carefull).
Take all precautions: Backup everything, including userdata and cache partition, because sp flash tools will ask for it if you have to format. Do not forget to backup nvram.
Doing this, I successfully formatted the TS and installed previous firmware, 20140328.
Sadly, the TS won't boot. Here lies my hope to get TWRP and bt tether ROM working without update from its creator...
So, back to firmware 20140513.
After the new format+backup, TS boot normally, but I had a "IMEI invalid" error. So, I used MTKdroidtools to restore nvram the same way I previously backed it up.
Complete 'format+download' is to be used if you messed up with partitions or if partitions changed.
Could be usefull, this was to let you know how.
Click to expand...
Click to collapse
What exactly are you trying to do?
kuronosan said:
What exactly are you trying to do?
Click to expand...
Click to collapse
Install last firmware known to be working with twrp.
Did that.
The device doesn't boot anymore.
Revert to previous backup.
Did that.
I like to see things by myself.
It's not your firmware that's the problem. I'm running twrp on the latest firmware without issue.
kuronosan said:
It's not your firmware that's the problem. I'm running twrp on 20140513 firmware without issue.
Click to expand...
Click to collapse
I can only rely on testimonies on this very forum, but I have not seen a single person succesfully installed twrp on firmware 20140513.
I have seen successfull install on previous firmware, and then OTA upgrade.
What is it for you ?
It is exactly what I told you. It's up to you to believe me or not.
kuronosan said:
It is exactly what I told you. It's up to you to believe me or not.
Click to expand...
Click to collapse
You didn't told me if its an install on 20140513 firmware or if it's an upgrade from previous firmware.
kuronosan said:
EU 1/8 users who have the new aluminum watch or who received their units after May 13th need to click here and also need to remember that recovery may not work (although it probably won't work before this anyway).
Click to expand...
Click to collapse
I understand you agree there is a problem with twrp 2.7.1.0 on newer devices.
You'll notice I did say new devices. Not new firmware.
kuronosan said:
You'll notice I did say new devices. Not new firmware.
Click to expand...
Click to collapse
Ok then, you win by default. Look at me asking a simple question while you obviously rather going back an forth playing fallacy pong. Please forgive me if I cut this short. I'll click on Thank You anyway.
Anyway to get back to the thread.. I've tried everything, booting in recovery, running MTK Droid Tools as Administrator, installing busybox again - but still no PMT file. I'm all out of ideas now..
Tigerite said:
Anyway to get back to the thread.. I've tried everything, booting in recovery, running MTK Droid Tools as Administrator, installing busybox again - but still no PMT file. I'm all out of ideas now..
Click to expand...
Click to collapse
That's OK. It appears that PMT can be (or not) in scatter file without any difference in the filename. (If you look in the file and see many lines per partition, like 'physical_start_addr' and 'linear_start_addr', you have PMT)
So I found what I was looking for, thank you.
MrTip said:
Ok then, you win by default. Look at me asking a simple question while you obviously rather going back an forth playing fallacy pong. Please forgive me if I cut this short. I'll click on Thank You anyway.
Click to expand...
Click to collapse
No one is trying to win. I have a good deal of experience with MTK devices based on my researching various methods of backup/restore/flash/etc and I was offering a hand.
You can play one-person pong with yourself and claim fallacy all you want or you can get off your high horse.
Up to you. I have work to do.
TWRP Install on newest firmware + OTA
got watch on 7/26. did OTA. firmware date 5/27/2014. unable to install TWRP via any method including shell DD command. well it installs but on entry I just get on the old andy with red ! showing. It seems like a watchdog timers reboots it after a few minutes and all is back to the way it was.
Which TWRP did you use?
Hello,
It seems that many of HAM2 users have the consumer cellular variant and are irked by several modifications done on the stock ROM that one gets when he buys the phone unlocked. Many of us, including myself, would like to flash the stock ROM if possible but maybe are not brave enough to try .
Someone uploaded several versions of different ROMS on https://drive.google.com/folderview?...0&usp=sharing. So, the question is can we flash any of these ROMS on our consumer cellular variant and if so, how ? I used to have a samsung galaxy young and flash different countries ROM using ODIN so many times that I can't remember how much. I tried that because it was confirmed to work. So, can the same be done on our HAM2 ?
Thanks.
The problem with flashing oem firmware
medwatt said:
Hello,
It seems that many of HAM2 users have the consumer cellular variant and are irked by several modifications done on the stock ROM that one gets when he buys the phone unlocked. Many of us, including myself, would like to flash the stock ROM if possible but maybe are not brave enough to try .
Someone uploaded several versions of different ROMS on https://drive.google.com/folderview?...0&usp=sharing. So, the question is can we flash any of these ROMS on our consumer cellular variant and if so, how ? I used to have a samsung galaxy young and flash different countries ROM using ODIN so many times that I can't remember how much. I tried that because it was confirmed to work. So, can the same be done on our HAM2 ?
Thanks.
Click to expand...
Click to collapse
The 126 firmware in that folder is the original firmware that came on the consumer cellular version. The problem with flashing the complete 148 firmware is inside udate.app file there is a file named oem_verlist.img. The is a partition in the root directory of the phone for that img file to be flashed. when you go to update with the 148 firmware that img file realizes that it does not match the phone that you are trying to flash to and bring up a error and fails. I have tried to fastboot that img file to its partition but it will not go. Maybe I am using the wrong parition name but with out updating that partition before trying to flash it will fail.
mtyler7807 said:
The 126 firmware in that folder is the original firmware that came on the consumer cellular version. The problem with flashing the complete 148 firmware is inside udate.app file there is a file named oem_verlist.img. The is a partition in the root directory of the phone for that img file to be flashed. when you go to update with the 148 firmware that img file realizes that it does not match the phone that you are trying to flash to and bring up a error and fails. I have tried to fastboot that img file to its partition but it will not go. Maybe I am using the wrong parition name but with out updating that partition before trying to flash it will fail.
Click to expand...
Click to collapse
When you say "update", do you mean clearing the OS and installing a new one from scratch ? Does that mean after the update all the consumer cellular additions will go away and there will be no trace of it ?
If updating seems difficult now for the consumer cellular versions, what will we do when they release Lollipop ?
If they do not release a cc version then I would have to extract the OEM update.app file from the huawei site to all the IMG files and fastboot flash one at a time(force flash if you want to call it). Inside the update file there will be a system.IMG, data.IMG, cache.IMG,etc
Sent from my MT2L03 using XDA Premium 4 mobile app
mtyler7807 said:
If they do not release a cc version then I would have to extract the OEM update.app file from the huawei site to all the IMG files and fastboot flash one at a time(force flash if you want to call it). Inside the update file there will be a system.IMG, data.IMG, cache.IMG,etc
Sent from my MT2L03 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Assuming they release the CC version of lollipop, will there be any problem if some of the system files have been changed? For example, I've deleted some system apps that I never use and changed the boot- and flash-screen files. Will the update fail because of that ? I'm asking this because I saw a video made by one of the forum members here when he was trying to install the v148 update. He had to uninstall everything and return the system to default before updating. If that is so, then I guess no Lollipop crying::crying for me !!
Given that Lollipop is still some months away and the lack of any meaningful activity on the HAM2, why don't we prepare our HAM2 for who-knows-what. I'd like to get a grip on a my phone now instead of getting swamped by error messages when Lollipop gets released or we get custom firmware.
There's this thread [http://forum.xda-developers.com/showthread.php?t=2315547] which explains how to extract the individual image files from the huawei update app.
Do you have the CC version of HAM2 ? If so, will you be trying to flash the image files because extracting the image files seem straight-forward ? I'm actually a bit nervous doing it myself because I've always flashed my other devices when it has been confirmed to work. What I'm wary of is I'm not sure that the device software in the v148 update app is 100% compatible with the CC variant that I own ! How can one be sure of that ?
I've downloaded v148 update file and extracted the files you mentioned. Instead of taking screenshots of the contents of the image files, I've recorded a small video. I can see the boot.img and system.img but no recovery.img. There are also other files. Take a look at the video. The question now is what to do with these files and more importantly what are my chances of unbricking the phone if it bricks !!
It will not fail because of boot animation and splash screen change. It will fail because of missing system apps. You would need to reinstall those if the package comes as a upgrade but if it is a full download then your OK.
Dealing with extracting the files from the update.app just search for my post, I have a complete instruction guide.
Sent from my MT2L03 using XDA Premium 4 mobile app
mtyler7807 said:
It will not fail because of boot animation and splash screen change. It will fail because of missing system apps. You would need to reinstall those if the package comes as a upgrade but if it is a full download then your OK.
Dealing with extracting the files from the update.app just search for my post, I have a complete instruction guide.
Sent from my MT2L03 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Have you seen the video I uploaded ? Is it the "full download"? Can I flash it ? Will the phone brick ?
I read your posts on the subject. But it seems you have changed some system apps and the camera is not working as it should. I have already downloaded the 148 file and extracted the system.img and boot.img files. Can I flash these or do I have to use the files you uploaded on google drive ?
The question is why didn't you use the v148 stock ? I already have the v148 stock. Will it brick my phone if I flash the image files ? If not, why did you have to add extra files there such that the camera is 8MP instead of 13MP. Also, why is the hotspot always enabled ? Is that the case with people with the original stock ?
Man, I'm still waiting for your reply !
medwatt said:
Man, I'm still waiting for your reply !
Click to expand...
Click to collapse
My understanding is it is possible to flash to stock if your bootloader is unlocked and have TWRP installed. Then its as simple as flashing a backup from a matching model with stock frimware. For whatever reason mtyler7807 is trying to reinvent the wheel.
290 said:
My understanding is it is possible to flash to stock if your bootloader is unlocked and have TWRP installed. Then its as simple as flashing a backup from a matching model with stock frimware. For whatever reason mtyler7807 is trying to reinvent the wheel.
Click to expand...
Click to collapse
"For whatever reason mtyler7807 is trying to reinvent the wheel", Ha Ha. I spent about 2 weeks working on this phone when I first got it. With this phone it has more partitions than what is included in the backup with TWRP. TWRP is made for backup and restoring the files that get changed, the other partitions don't change. So when I first started experimenting with this phone I got a full 148 backup with no data and installed it. I had problems, the custom.bin points to a different cust/us/ folder (because it is for a different carrier) , I had to rename that folder and found I have no more 4glte only H/H+, So I had to get the original cust folder from the guy and copy it to the phone. Still and only H/H+. It was okay for then because I testing. Next Viewed my system specs and saw that pretty much half half phone was 148 and the other half was 132.
I have Redone my complete back since I posted the last one with google camera with 13mp support( rather have border transparency). I made a post asking people summit backups. You have to do a little research, did my research and got help from the forum guys. If you want 148 on your CC version you will have to extract the update and fastboot img files (ex.fastboot flash system system.img). The name of the file is the partition name.
From my understanding twrp does a nand backup. Which is more like an image of nand. So restoring an image from a stock phone would also give you the stock partition table no?
It has been a while since ive played with android on such a low level. When it came time to update my HP Touchpad to JB i had to manually create the partition table manually to make it fit. Eventually a script was created that automatically made the changes to the file system. Perhaps a solution along those lines could be useful in getting the stuck firmware on the CC phones? The file system would only need to be created on initial flash to the stock firmware.
mtyler7807, I've been trying to get an answer since I first created this thread. The only reason I want to install the original huawei stock instead of the cc version is because I want to be able to download and install updates just like regular stock huawei HAM2 users instead of waiting for the CC version. So, please can you answer these questions :
1. If I follow your steps and use the image files you uploaded, will I get rid of CC completely meaning will my phone be just like a stock HAM2 phone from Huawei ?
2. Can I install Huawei updates directly, instead of having to do what you did (extracting the image files and the rest of the process).
3. If the answers to the above questions is no and no, then whats the point of installing your images files (apart from getting the hotspot which I don't use) ?
Please answer these questions unambiguously so that I and others will get a clear understanding of the reasons to flash the image files you uploaded. In doing so, people will stop creating these threads asking boundless questions.
Thanks.
medwatt said:
mtyler7807, I've been trying to get an answer since I first created this thread. The only reason I want to install the original huawei stock instead of the cc version is because I want to be able to download and install updates just like regular stock huawei HAM2 users instead of waiting for the CC version. So, please can you answer these questions :
1. If I follow your steps and use the image files you uploaded, will I get rid of CC completely meaning will my phone be just like a stock HAM2 phone from Huawei ?
2. Can I install Huawei updates directly, instead of having to do what you did (extracting the image files and the rest of the process).
3. If the answers to the above questions is no and no, then whats the point of installing your images files (apart from getting the hotspot which I don't use) ?
Please answer these questions unambiguously so that I and others will get a clear understanding of the reasons to flash the image files you uploaded. In doing so, people will stop creating these threads asking boundless questions.
Thanks.
Click to expand...
Click to collapse
Here is what k2thejx5 said after flashing a backup from a stock phone.
k2thejx5 said:
What's weird is when I flashed the stock file and tried to upgrade, it wouldn't work. The kernels were different so I had to go back to stock consumer rom. Also, while using the rom you posted.. I lost my toggles and had to use a different app. What also was very weird, after flashing back to the stock consumer rom, I had tethering! Don't get it lol.
Click to expand...
Click to collapse
-Do what I did makes your phone a complete oem, All that is need to be done is to flash a splash screen.
-How would I know if updates will work since 148 is the latest version for oem, can't test that tell lollipop.
-I'm not pushing anyone to install my image, I got about 30 pm's to post my recovery to enable hotspot and to get those toggles backup at the top. Alot of people messed up and lost them flashing that original twrp recovery under developer. Alot of others wanted the hotspot without the head ache of going through the research.
And for the people with problems with there phone that want 148 and updates with no problems, You should have brought a OEM and stayed away from sears or target or took it back to the store if you were not ready to take on the challenge of fabbing up your phone. Or just deal with the factory image and hope for lollipop.
---------- Post added at 02:14 PM ---------- Previous post was at 02:06 PM ----------
Me and k2thejx5 was trying to fix the problem with the twrp recovery originally posted on this site. That one is not mine. Read the post. That firmware took our toogles away. You have to read this forum a little more.
Ok man, thanks for the reply. Two last question:
-For as long as you've been using your phone with your image files, have you been noticing problems like "unexpected crashes", trying to launch something and its unresponsive lie APN
-Is this the latest file you recommend : [https://drive.google.com/file/d/0BwnSk8BOQp3wV0JMWnJGc3RBTzQ/view]
Thanks.
I have to make another one. I created a new one with epic browser and 360 deg rotation. And I added Camera JB+. Thats the best camera add out there to me, looks just like google 5 camera. I can post image of this new one. I'll Back up my phone and clear the cache and restore it with no data so none of my info will be saved that belongs to me. then i'll setup up the phone and back it up and post.
mtyler7807 said:
I have to make another one. I created a new one with epic browser and 360 deg rotation. And I added Camera JB+. Thats the best camera add out there to me, looks just like google 5 camera. I can post image of this new one. I'll Back up my phone and clear the cache and restore it with no data so none of my info will be saved that belongs to me. then i'll setup up the phone and back it up and post.
Click to expand...
Click to collapse
All right then. Upload it when you're ready !
Firstly I want to tell you that I am very close to unbRick Moto e.
So, as u all know that android operating system is made on Linux.
So android development is possible using Linux as I am using Kali Linux
And I would like to tell you that we hard-bricked Moto e by updating it to New firmware which contains the update of bootloader
In android operating system bootloader is the thing which tells the kernel to boot or to start the phone
And by upgrading our bootloader is corrupted so it is not booting nor in fastboot mode or in system
So the problem is bootloader is deleted and we have to reinstall it using kali Linux by deleting and then recreating the bootloader and .gpt partions.
And I am facing some problem using Kali Linux
So is there anyone who have good knowledge of Linux
It will be really appreciated..
U can contact me on my whatsapp no.8233361455
Divesh ahuja said:
Firstly I want to tell you that I am very close to unbRick Moto e.
So, as u all know that android operating system is made on Linux.
So android development is possible using Linux as I am using Kali Linux
And I would like to tell you that we hard-bricked Moto e by updating it to New firmware which contains the update of bootloader
In android operating system bootloader is the thing which tells the kernel to boot or to start the phone
And by upgrading our bootloader is corrupted so it is not booting nor in fastboot mode or in system
So the problem is bootloader is deleted and we have to reinstall it using kali Linux by deleting and then recreating the bootloader and .gpt partions.
And I am facing some problem using Kali Linux
So is there anyone who have good knowledge of Linux
It will be really appreciated..
U can contact me on my whatsapp no.8233361488
Click to expand...
Click to collapse
Where did you get this information? Is only Kali Linux or any Linux Distro required? I have some knowledge, so I might be able to help if you give me more information
Actually I am doing software engineering
So I have a little knowledge
And Kali Linux is best to do so because it is an advance linux
Divesh ahuja said:
Actually I am doing software engineering
So I have a little knowledge
And Kali Linux is best to do so because it is an advance linux
Click to expand...
Click to collapse
I see... Okay, we can proceed... PM me the details
Just hope for solution for my hard bricked Moto E.. Or i will bring it to Service Center
Dear Rohitagni , plz contact me
What happend?
Divesh ahuja said:
Firstly I want to tell you that I am very close to unbRick Moto e.
So, as u all know that android operating system is made on Linux.
So android development is possible using Linux as I am using Kali Linux
And I would like to tell you that we hard-bricked Moto e by updating it to New firmware which contains the update of bootloader
In android operating system bootloader is the thing which tells the kernel to boot or to start the phone
And by upgrading our bootloader is corrupted so it is not booting nor in fastboot mode or in system
So the problem is bootloader is deleted and we have to reinstall it using kali Linux by deleting and then recreating the bootloader and .gpt partions.
And I am facing some problem using Kali Linux
So is there anyone who have good knowledge of Linux
It will be really appreciated..
U can contact me on my whatsapp no.8233361488
Click to expand...
Click to collapse
what happend...?...any progress??
Divesh ahuja said:
Dear Rohitagni , plz contact me on whatsapp
8233361488
Click to expand...
Click to collapse
Sorry bro, I missed out this post... I'll contact you by this evening.
did you solved the problem cuz i also kind of having this problem
did you solved the problem cuz i also kind of having this problem
How about using Mi flash?
I too have a hard bricked Moto e. And I've been looking for unbrick solutions, but no luck so far. However, I came across a few methods that might work like using Mi flash or QPST eMMC download (I don't think QFill will work). Miflash seems to be a good option as it is used to unbrick any Xiomi phones. Unfortunately, there is no Xiomi phones with Snapdragon 200. Now, all we need is correct files for Moto e:
1. MPRG8x10.hex (It is the eMMC programmer file to help download the bootloader into eMMC, and I guess it can be used with all Snapdragon 200 MSM8x10 processor. And I've already got this file somehow).
2. 8x10_msimage.mbn (It is the bootloader image file and specific to the phone. In case of Moto e, it is the motoboot.img. Renaming the file might just work. I've got this file too.)
3. Raw XML and Patch XML files (These XML files contain the partition details of Moto e. And I don't have these two. We need someone with a working Moto e to create a system dump file. From that we may be able to create these XML files.)
4. Fastboot Script file (It is a batch file. I'm downloading few Xiomi fastboot roms to see the contents of this batch file)
Some useful links:
forum.xda-developers.com/showthread.php?t=2086142
forum.xda-developers.com/showthread.php?t=2450045
P.S: I'm new to XDA and certainly not an expert. If you find anything wrong with the above information, you're more than welcome to correct me. I'm not allowed to post links. Please put (http://) in the beginning of those links.
206bone said:
I too have a hard bricked Moto e. And I've been looking for unbrick solutions, but no luck so far. However, I came across a few methods that might work like using Mi flash or QPST eMMC download (I don't think QFill will work). Miflash seems to be a good option as it is used to unbrick any Xiomi phones. Unfortunately, there is no Xiomi phones with Snapdragon 200. Now, all we need is correct files for Moto e:
1. MPRG8x10.hex (It is the eMMC programmer file to help download the bootloader into eMMC, and I guess it can be used with all Snapdragon 200 MSM8x10 processor. And I've already got this file somehow).
2. 8x10_msimage.mbn (It is the bootloader image file and specific to the phone. In case of Moto e, it is the motoboot.img. Renaming the file might just work. I've got this file too.)
3. Raw XML and Patch XML files (These XML files contain the partition details of Moto e. And I don't have these two. We need someone with a working Moto e to create a system dump file. From that we may be able to create these XML files.)
4. Fastboot Script file (It is a batch file. I'm downloading few Xiomi fastboot roms to see the contents of this batch file)
Some useful links:
forum.xda-developers.com/showthread.php?t=2086142
forum.xda-developers.com/showthread.php?t=2450045
P.S: I'm new to XDA and certainly not an expert. If you find anything wrong with the above information, you're more than welcome to correct me. I'm not allowed to post links. Please put (http://) in the beginning of those links.
Click to expand...
Click to collapse
First of all, the OP has sold his phone, so don't expect any further development from this thread.
Second, you are most welcome to implement your knowledge about unbricking as many fellow members are in need of a solution.
And last but not the least, welcome to XDA
Thanks for the reply..
Rohitagni said:
First of all, the OP has sold his phone, so don't expect any further development from this thread.
Second, you are most welcome to implement your knowledge about unbricking as many fellow members are in need of a solution.
And last but not the least, welcome to XDA
Click to expand...
Click to collapse
Thanks Rohitagni for the reply. It's good for him that he has sold his phone. Hope somebody is out there to create the dump file. Anyway, I'll keep looking around and will post a thread if I find any solution. :good:
Can we use like different bootloader in this case
I got one moto e bricked
yesterday i just updated OTA 4.4.4 and my phone is bricked i.e. nothing happens with my phone.
Please can some one tell me step by step solution. this will help other as well.
I tried blankflash but couldn't open the port.
can you explain the procedure
206bone said:
Thanks Rohitagni for the reply. It's good for him that he has sold his phone. Hope somebody is out there to create the dump file. Anyway, I'll keep looking around and will post a thread if I find any solution. :good:
Click to expand...
Click to collapse
I unfortunately hardbricked my Moto E today. Everything was going fine when I decided to go to Advanced->Recovery in the TWRP recovery after wiping everything. Only the LED light blinks now when connecting and disconnecting the charger. I also happen to have access to a working Moto e. I might be able to help you here in finding the required files. Let me know what you want and how. Thanks,
---------- Post added at 07:41 PM ---------- Previous post was at 07:41 PM ----------
206bone said:
Thanks Rohitagni for the reply. It's good for him that he has sold his phone. Hope somebody is out there to create the dump file. Anyway, I'll keep looking around and will post a thread if I find any solution. :good:
Click to expand...
Click to collapse
I unfortunately hardbricked my Moto E today. Everything was going fine when I decided to go to Advanced->Recovery in the TWRP recovery after wiping everything. Only the LED light blinks now when connecting and disconnecting the charger. I also happen to have access to a working Moto e. I might be able to help you here in finding the required files. Let me know what you want and how. Thanks.
Rohitagni said:
First of all, the OP has sold his phone, so don't expect any further development from this thread.
Second, you are most welcome to implement your knowledge about unbricking as many fellow members are in need of a solution.
And last but not the least, welcome to XDA
Click to expand...
Click to collapse
I have system dump can anyone help me
moto e hard bricked
hi dude!
iam Shaik Rabbani
u know i hav hard bricked my moto e...i hav tried many ways to solve the issue on the internet but failed however...so if possible please help!
hope to hear from u soon
I might be able to help
206bone said:
I too have a hard bricked Moto e. And I've been looking for unbrick solutions, but no luck so far. However, I came across a few methods that might work like using Mi flash or QPST eMMC download (I don't think QFill will work). Miflash seems to be a good option as it is used to unbrick any Xiomi phones. Unfortunately, there is no Xiomi phones with Snapdragon 200. Now, all we need is correct files for Moto e:
1. MPRG8x10.hex (It is the eMMC programmer file to help download the bootloader into eMMC, and I guess it can be used with all Snapdragon 200 MSM8x10 processor. And I've already got this file somehow).
2. 8x10_msimage.mbn (It is the bootloader image file and specific to the phone. In case of Moto e, it is the motoboot.img. Renaming the file might just work. I've got this file too.)
3. Raw XML and Patch XML files (These XML files contain the partition details of Moto e. And I don't have these two. We need someone with a working Moto e to create a system dump file. From that we may be able to create these XML files.)
4. Fastboot Script file (It is a batch file. I'm downloading few Xiomi fastboot roms to see the contents of this batch file)
Some useful links:
forum.xda-developers.com/showthread.php?t=2086142
forum.xda-developers.com/showthread.php?t=2450045
P.S: I'm new to XDA and certainly not an expert. If you find anything wrong with the above information, you're more than welcome to correct me. I'm not allowed to post links. Please put (http://) in the beginning of those links.
Click to expand...
Click to collapse
I have a hard-bricked moto e xt1021 and one that still running but is not unlocked or rooted, i would like to help so if there is a way to make the dump file just let me know.
help !
email me bro
[email protected] this is my email address
Mt6761 chi p set****
I am in need of some assistance. I just got this phone and i had unlocked the boot loader and was trying to install twrp but have done something wrong. Now i am stuck with bootloop. I contacted wiko for the stock recovo[ery but they said they will not be releasing it for this model. If someone could be so kind as assist me in either pulling nessisary files from a new stock wiko ride or pulling the needed files from a device they own and be so kind as share. The bootloader wasnt hard to unlock at all.. I just couldnt find a twrp or any other files on google for this device and must have made a mistake when trying to create my own twrp. Any help would be so grately appreciated
Reply
WesHTCB said:
Mt6761 chi p set****
I am in need of some assistance. I just got this phone and i had unlocked the boot loader and was trying to install twrp but have done something wrong. Now i am stuck with bootloop. I contacted wiko for the stock recovo[ery but they said they will not be releasing it for this model. If someone could be so kind as assist me in either pulling nessisary files from a new stock wiko ride or pulling the needed files from a device they own and be so kind as share. The bootloader wasnt hard to unlock at all.. I just couldnt find a twrp or any other files on google for this device and must have made a mistake when trying to create my own twrp. Any help would be so grately appreciated
Click to expand...
Click to collapse
Did you get the needed files yet?
Not exactly.. I had tried to make a backup of a new ride device but couldnt get them to work properly without breaking varity...i used mtk-su to do the backup. If you have any advise, files, or even questions i could use or help you with... Let me know...
What files u need? I found a way to read and copy files from boot and system partitions
Idk if anyone is using this thread anymore but I have a full backup of the wiko ride stock image I believe. If needed let me know.
KaosKreationz said:
Idk if anyone is using this thread anymore but I have a full backup of the wiko ride stock image I believe. If needed let me know.
Click to expand...
Click to collapse
i have a wiko ride that i recently soft bricked just messing around and i can not find the right files to flash to it anywhere. yes, please, i could use the backup if you are still in possession of it.
Hi, i tried to install a custom rom in my device (y6 2018 ATU L21) and an error ocurred due to my ****ty usb cable, so now im in a big trouble because the phone is bricked.
I backup some partitions before the accident such as kernel, ramdisk but guess what, the most important (system.img) is corrupted and i can't do anything.
The phone boots and shows huawei logo and then black screen forever, i can't access TWRP nor Erecovery, im completly stuck.
I searched on "Huawei Firmware Finder" but any of the ROMs for ATUL21 works (some of them have missing partitions) so now i only depend on the community, if there is any good person that has this phone and wants to help me by sharing the partitions to me i will appreciate such act of generosity, if you want to help me you can follow those steps (Need to be root):
https://forum.xda-developers.com/t/guide-twrp-backup-current-partitions.3853831/
If you have any stock rom that works for this model im glad to accept it .
Have a good day.
I think I have this for you:
ATU-L21 BACKUP
Good luck!
mro92 said:
I think I have this for you:
ATU-L21 BACKUP
Good luck!
Click to expand...
Click to collapse
For people like you i never lose hope on the community and i always try to help others, thank you so much my brother. Bless you and your family.
Mimoun.
which tool do i use to write this file
Hello, it's been a while since the post but I still need your help. I have the same problem as describe. I downloaded the file from the nice man. Tried to flash it with fastboot but the phone still has the same problem. maybe you can solve your problem and can help me.
I only have access to fastboot because the rest doesn't work. maybe you also have a custom ROM that works on the device, which doesn't necessarily have to be original software.
Thanks in advance
Jannikoks06 said:
Hello, it's been a while since the post but I still need your help. I have the same problem as describe. I downloaded the file from the nice man. Tried to flash it with fastboot but the phone still has the same problem. maybe you can solve your problem and can help me.
I only have access to fastboot because the rest doesn't work. maybe you also have a custom ROM that works on the device, which doesn't necessarily have to be original software.
Thanks in advance
Click to expand...
Click to collapse
Hi, this is what i have done to recover the phone. First, there is one mistake that i made and it was trying to flash the files from fastboot, you can't do that because the phone is bricked, instead you need to download the firmware from "Huawei Firmware Finder" and then you need to dissasemble your phone to press the test point. look at this video for reference huawei test point once your PC is going to recognize your device as 'COM' on the device manager, and then you need to use a tool to flash the firmware, i can't share with you the tool since i have switched to Linux distro and i don't use Windows anymore. But if you were smart enough to flash your phone i think with a little bit of search you are gonna find.
Good Luck and have a good day.
Hello thanks for the answer, I have already downloaded stock roms from 2 different sites, both are the same.There are many subfolders in the file but after a long search you can find some .app files right? What should I do with the file exactly? Flash this directly? If so, do you happen to remember the name? Or did you extract the various files from this file, such as "Boot" or something else?