Related
Hi,
I have a Motorola atrix 4g. The phone will not boot up. It turns on and the Motorola logo come then the red light stars blinking. after a minute or so the phone restarts and repeats the process. I tryed factory hard reset but no luck.
i fount this on the web http://forum.xda-developers.com/showthread.php?t=966405 but has no idea how to do this.
Pleas help me
thank you
Pgeorge
It happens if there is somthing wrong when you install a rom
try to find another rom and flash it if you unlocked the bootloader
or flash ATT 4.5.91 Rom via RSD Lite ONLY IF YOU HAVE LOCKED BOOTLOADER
Jack Krauser said:
It happens if there is somthing wrong when you install a rom
try to find another rom and flash it if you unlocked the bootloader
or flash ATT 4.5.91 Rom via RSD Lite ONLY IF YOU HAVE LOCKED BOOTLOADER
Click to expand...
Click to collapse
hi,
thank you for the fast replay. I have rsd installed, but where can i find this rom
Softbrick
Is bootloader unlocked? Says on m logo?
Sent from my MB860 using xda premium
stevendeb25 said:
Softbrick
Is bootloader unlocked? Says on m logo?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
It is not unlocked. There is nothing on the logo. Only the m
help
kinggeorge3287 said:
It is not unlocked. There is nothing on the logo. Only the m
Click to expand...
Click to collapse
help please
go here to download any atrix related files
visit that site, it contains everything for the atrix and the best place to get roms, tools, utilities, mods, tweaks, and so forth....
but first download the zip file below this message. I uploaded the zip file for you that has adb, fastboot & moto-fastboot(lets you install .img over 100mb), the necessary dll files & atrix recovery image & command.bat which just opens the command prompt window for you and puts you into the folder so you dont have to navigate anywhere in command prompt to located folders.
first try this, download the zip file, extract to any folder like c:\fastboot
then run the command.bat file to quickly bring up a command prompt and type these commands
Code:
fastboot -w
fastboot flash recovery recovery.img
fastboot reboot
that may solve your issue if your kernel installed properly and the boot.img file was properly written to the boot partition. If it doesn't solve your problem, go to that link above to find the kernel for whatever rom you're on, att, cm7 or cm9. Get the correct kernel thats compatible, pull out the boot.img from that zip file and also place it into your fastboot folder, then go to fastboot mode again and type "fastboot flash boot boot.img" and then fastboot reboot.
android-DEP said:
go here to download any atrix related files
visit that site, it contains everything for the atrix and the best place to get roms, tools, utilities, mods, tweaks, and so forth....
but first download the zip file below this message. I uploaded the zip file for you that has adb, fastboot & moto-fastboot(lets you install .img over 100mb), the necessary dll files & atrix recovery image & command.bat which just opens the command prompt window for you and puts you into the folder so you dont have to navigate anywhere in command prompt to located folders.
first try this, download the zip file, extract to any folder like c:\fastboot
then run the command.bat file to quickly bring up a command prompt and type these commands
Code:
fastboot -w
fastboot flash recovery recovery.img
fastboot reboot
that may solve your issue if your kernel installed properly and the boot.img file was properly written to the boot partition. If it doesn't solve your problem, go to that link above to find the kernel for whatever rom you're on, att, cm7 or cm9. Get the correct kernel thats compatible, pull out the boot.img from that zip file and also place it into your fastboot folder, then go to fastboot mode again and type "fastboot flash boot boot.img" and then fastboot reboot.
Click to expand...
Click to collapse
Hi,
I tryed doing this, but i get a error " Failed to process command flash: recovery error (0x180002)
I think when i tried to flash rom with RSD LIght may have done something to the files. and it was no help. I dont get a flashing red light now. only the phone stops booting at M logo.
Now How do i flash new rome ? Do i use RSD Light or something else. I know that RSB Requires .sbf file but all the files i see in the site you gave me are .zip.
i also tryed the fastboot flash boot boot.img and no luck, it gvies me the error "Failed to process command flash: recovery error (0x180002)"
thank you for the replay
Pgeorge
do you have clockworkmod recovery installed or any custom recovery installed? if not, then thats why it wont flash, your bootloader is locked.
the whole idea behind using clockworkmod recovery is to avoid using RSD to flash sbf files which can brick the phone easily. Its best to avoid using RSD to flash sbf files on your phone at all costs and leave only as a last resort method if you just cannot recover the phone.
Flashing a new rom would normally be done by already having your phone rooted and unlocked with clockworkmod recovery or some other custom recovery installed so you can boot into recovery and choose "install from zip" and point to the zip file that has the rom. The custom recovery does the flashing for you and its a safer method of flashing roms on the phone than RSD.
If you got no other choice and I know what thats like, i been there too. Download RSD Lite v5.6, should be a free download online somewhere, and then search online for "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", then use RSD to flash that sbf onto phone.
Before trying that, goto http://samcripp.com/files/ and in the folder OTA Updates, download the first file named Blur_Version_91.4.5.141.MB860.ATT.en.US.zip and put it into the fastboot folder, boot into fastboot again and try "fastboot update Blur_Version_91.4.5.141.MB860.ATT.en.US.zip" and you may be able to get away with just using fastboot to flash that update onto the phone to restore corrupt files. I would try this before using RSD to flash the phone
android-DEP said:
do you have clockworkmod recovery installed or any custom recovery installed? if not, then thats why it wont flash, your bootloader is locked.
the whole idea behind using clockworkmod recovery is to avoid using RSD to flash sbf files which can brick the phone easily. Its best to avoid using RSD to flash sbf files on your phone at all costs and leave only as a last resort method if you just cannot recover the phone.
Flashing a new rom would normally be done by already having your phone rooted and unlocked with clockworkmod recovery or some other custom recovery installed so you can boot into recovery and choose "install from zip" and point to the zip file that has the rom. The custom recovery does the flashing for you and its a safer method of flashing roms on the phone than RSD.
If you got no other choice and I know what thats like, i been there too. Download RSD Lite v5.6, should be a free download online somewhere, and then search online for "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", then use RSD to flash that sbf onto phone.
Before trying that, goto http://samcripp.com/files/ and in the folder OTA Updates, download the first file named Blur_Version_91.4.5.141.MB860.ATT.en.US.zip and put it into the fastboot folder, boot into fastboot again and try "fastboot update Blur_Version_91.4.5.141.MB860.ATT.en.US.zip" and you may be able to get away with just using fastboot to flash that update onto the phone to restore corrupt files. I would try this before using RSD to flash the phone
Click to expand...
Click to collapse
Well i tryed everything you provided, but no luck. I tryed the RSD but it dont go past the M logo after flash. any other way you know?
thnak you
pgeorge
http://forum.xda-developers.com/showthread.php?t=1163342
you said that site doesnt have any SBF files to download, this is a good example of why the owner decided against posting the sbf files online. A lot of people from what I heard, were either soft bricking their phones into temporary hat weights or going full out hard into brick city on a one way ticket joy ride. Flashing sbf files is very risky and RSD tool isn't really meant for the public to be downloading to use at home and flash full roms over their devices. Thats a Motorola utility and it's not exactly a risk-free method of flashing the rom inside these phones. Plus getting SBF files online, you rarely know 100% if its compatible with your model phone or where came from exactly and that it's integrity can be checked for 100% consistency that nothing half-way through the file is missing any chunks of code or is corrupt. Try sticking to only using fastboot & adb & get clockworkmod recovery to make FULL and complete devices backups.
Now that I learned my lesson a few times, no matter what, first thing I always do in recovery is make a backup before I flash anything at all, just in case of just in case, its better to measure twice and cut once.
try that link above and restore stock gingerbread 2.3.4, phone doesnt need to be unlocked or root, and make sure to use "moto-fastboot.exe" it lets you push\pull & install files larger than 200MB onto phone through fastboot, the regular fastboot has some limit on file sizes
Hi,
to give you a update noting worked. The link you provided dont have any working lnks to download. I tryed some other once and no luck. It gave me "failed to boot 1". so i flashed this file "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf" it went away, but no boot after the logo. I don't know what i am doing wrong. Any other ideas?
Thank you
Pgeorge
android-DEP said:
http://forum.xda-developers.com/showthread.php?t=1163342
you said that site doesnt have any SBF files to download, this is a good example of why the owner decided against posting the sbf files online. A lot of people from what I heard, were either soft bricking their phones into temporary hat weights or going full out hard into brick city on a one way ticket joy ride. Flashing sbf files is very risky and RSD tool isn't really meant for the public to be downloading to use at home and flash full roms over their devices. Thats a Motorola utility and it's not exactly a risk-free method of flashing the rom inside these phones. Plus getting SBF files online, you rarely know 100% if its compatible with your model phone or where came from exactly and that it's integrity can be checked for 100% consistency that nothing half-way through the file is missing any chunks of code or is corrupt. Try sticking to only using fastboot & adb & get clockworkmod recovery to make FULL and complete devices backups.
Now that I learned my lesson a few times, no matter what, first thing I always do in recovery is make a backup before I flash anything at all, just in case of just in case, its better to measure twice and cut once.
try that link above and restore stock gingerbread 2.3.4, phone doesnt need to be unlocked or root, and make sure to use "moto-fastboot.exe" it lets you push\pull & install files larger than 200MB onto phone through fastboot, the regular fastboot has some limit on file sizes
Click to expand...
Click to collapse
kinggeorge3287 said:
Hi,
to give you a update noting worked. The link you provided dont have any working lnks to download. I tryed some other once and no luck. It gave me "failed to boot 1". so i flashed this file "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf" it went away, but no boot after the logo. I don't know what i am doing wrong. Any other ideas?
Thank you
Pgeorge
Click to expand...
Click to collapse
when rds end flashing the sbf the phone gets a bootlop or failed to boot error again?
lucamibel said:
when rds end flashing the sbf the phone gets a bootlop or failed to boot error again?
Click to expand...
Click to collapse
it starts up, the M logo comes and it freezes there. To turn the phone off i have to pull the battery.
thank you
Pgeorge
Restore Your Motorola Atrix 4G Back to 4.5.91 Stock Firmware
it helps to remove any problem related to rom..
With so many Android phones literally flooding the market these days, it’s no wonder that there are also so many firmware upgrades and custom firmware being developed and released every now and then. A superior device with great stuff neatly packed into it, the Motorola Atrix 4G is one of the devices for whom developers have devoted significant firmware love.
One reason for the attention that devs give to the Atrix 4G is that it is a fantastic device with a dual-core Nvidia Tegra 2 processor and robust ability for handling impressive graphics and video without choking. Together with its powerful processor and 1 GB of RAM, the Atrix 4G is a mean powerhouse that can be further exploited with the use of third-party applications and custom ROMs.
In an age where technology is constantly changing at an alarming pace it is important to always have a trusted source to get your updates in a timely fashion. Custom ROMs and factory firmware updates have played a crucial role in the development in many of our devices.
For those of you who have rooted your Atrix 4G and already have installed custom ROMs, then you might already have some bad experiences with regards to unofficial firmware sources. Unofficial firmware such as custom ROMs are literally filled with many bugs and disabled features. In many cases, these ROMs are not stable for daily use.
Luckily for owners of the Motorola Atrix 4G, there’s an escape hatch for reverting to stock, functioning firmware and return the phone to its factory state.
In this tutorial, you will learn how to roll back your Motorola Atrix 4G to the official firmware version 4.5.91, regardless of your current firmware
HERE IS THE LINK FOR YOUR PROBLEM....BEST OF LUCK
kinggeorge3287 said:
it starts up, the M logo comes and it freezes there. To turn the phone off i have to pull the battery.
thank you
Pgeorge
Click to expand...
Click to collapse
then you can now try unlocking and flashing cwm recovery and flash a custom rom to avoid using rds again
sikkijazz said:
Restore Your Motorola Atrix 4G Back to 4.5.91 Stock Firmware
it helps to remove any problem related to rom..
With so many Android phones literally flooding the market these days, it’s no wonder that there are also so many firmware upgrades and custom firmware being developed and released every now and then. A superior device with great stuff neatly packed into it, the Motorola Atrix 4G is one of the devices for whom developers have devoted significant firmware love.
One reason for the attention that devs give to the Atrix 4G is that it is a fantastic device with a dual-core Nvidia Tegra 2 processor and robust ability for handling impressive graphics and video without choking. Together with its powerful processor and 1 GB of RAM, the Atrix 4G is a mean powerhouse that can be further exploited with the use of third-party applications and custom ROMs.
In an age where technology is constantly changing at an alarming pace it is important to always have a trusted source to get your updates in a timely fashion. Custom ROMs and factory firmware updates have played a crucial role in the development in many of our devices.
For those of you who have rooted your Atrix 4G and already have installed custom ROMs, then you might already have some bad experiences with regards to unofficial firmware sources. Unofficial firmware such as custom ROMs are literally filled with many bugs and disabled features. In many cases, these ROMs are not stable for daily use.
Luckily for owners of the Motorola Atrix 4G, there’s an escape hatch for reverting to stock, functioning firmware and return the phone to its factory state.
In this tutorial, you will learn how to roll back your Motorola Atrix 4G to the official firmware version 4.5.91, regardless of your current firmware
HERE IS THE LINK FOR YOUR PROBLEM....BEST OF LUCK
Click to expand...
Click to collapse
Hi,
doing this gave me SVF:108:1:2
fail to boot 3
starting rsd mode
lucamibel said:
then you can now try unlocking and flashing cwm recovery and flash a custom rom to avoid using rds again
Click to expand...
Click to collapse
So how do i go about doing this? is there a link i can use?
thank you
Pgeorge
kinggeorge3287 said:
So how do i go about doing this? is there a link i can use?
thank you
Pgeorge
Click to expand...
Click to collapse
help please
kinggeorge3287 said:
help please
Click to expand...
Click to collapse
I am able to get into android recovery. It has a option to update from sdcard. Can i do something with this?
Pleas help
Pgeorge
Had the phone for 2 weeks. without being rooted it is so boring! Please any devs come up with a custom recovery soon
htcmusic said:
Had the phone for 2 weeks. without being rooted it is so boring! Please any devs come up with a custom recovery soon
Click to expand...
Click to collapse
that's why i gave mine to my wife, she doesn't like root. not positive this device will really get alot of development.
fix-this! said:
that's why i gave mine to my wife, she doesn't like root. not positive this device will really get alot of development.
Click to expand...
Click to collapse
Guys the device was just launched. Right now I'm working on teaming up with Brinly Taylor so we can develop for this.
Moto e 3g Variant boot.img and recovery.img
give me the following and i will try to compile a custom recovery
- boot.img(from 3g variant)
-recovery.img(from 3g variant)
Saumitra Yadav said:
give me the following and i will try to compile a custom recovery
- boot.img(from 3g variant)
-recovery.img(from 3g variant)
Click to expand...
Click to collapse
I have this model. But when i try to extract boot.img from adb shell. it says access denied, and when i type su the it says not found . any idea how this can be resolved.
We seem to have a chicken and egg problem here. We need a custom recovery to get root, but we need root to get the bits to make a custom recovery. I'll try to make something when I have time, but I don't have a device to test with, so I'll need the community's help to test.
squid2 said:
We seem to have a chicken and egg problem here. We need a custom recovery to get root, but we need root to get the bits to make a custom recovery. I'll try to make something when I have time, but I don't have a device to test with, so I'll need the community's help to test.
Click to expand...
Click to collapse
Well i have this 3g variant of moto e 2015. I am ready to help but i am new to all this stuff. Yesterday i pulled system.img but can't pull boot image.
Ravx said:
Well i have this 3g variant of moto e 2015. I am ready to help but i am new to all this stuff. Yesterday i pulled system.img but can't pull boot image.
Click to expand...
Click to collapse
I made something. I have no clue if it will work. Things usually don't work on the first try, but we have to start somewhere. Try this at your own risk. I'm not responsible for bricking your phone. I don't have a Moto E 3G to test with.
As a good first test with this recovery, try flashing SuperSU: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
TWRP for 3G Model only! Flash at your own risk! Completely untested first attempt!
Download link for my test recovery: http://www.mediafire.com/download/uple1nxzzpg1cb5/otus_twrp-2.8.6-untested.img
To install:
Code:
fastboot flash recovery otus_twrp-2.8.6-untested.img
EDIT: Don't use this image, it's too big and I've identified other issues.
Ravx said:
I have this model. But when i try to extract boot.img from adb shell. it says access denied, and when i type su the it says not found . any idea how this can be resolved.
Click to expand...
Click to collapse
This will be possible only when moto release sources,
squid2 said:
I made something. I have no clue if it will work. Things usually don't work on the first try, but we have to start somewhere. Try this at your own risk. I'm not responsible for bricking your phone. I don't have a Moto E 3G to test with.
As a good first test with this recovery, try flashing SuperSU: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
TWRP for 3G Model only! Flash at your own risk! Completely untested first attempt!
Download link for my test recovery: http://www.mediafire.com/download/uple1nxzzpg1cb5/otus_twrp-2.8.6-untested.img
To install:
Code:
fastboot flash recovery otus_twrp-2.8.6-untested.img
Click to expand...
Click to collapse
I had someone try it and found out that the image is too big. I will post a smaller one that should fit when I find time. I'll need to create a stripped down kernel and device tree for otus. To do that, I'd probably need my own device to test on. The 3G model is unavailable in Canada, but for the sake of the community, I've ordered a 3G model from abroad, at a cost much greater than what it is worth, so that I have a unit to test on. My test unit won't arrive for another week I'd expect.
squid2 said:
I had someone try it and found out that the image is too big. I will post a smaller one that should fit when I find time. I'll need to create a stripped down kernel and device tree for otus. To do that, I'd probably need my own device to test on. The 3G model is unavailable in Canada, but for the sake of the community, I've ordered a 3G model from abroad, at a cost much greater than what it is worth, so that I have a unit to test on. My test unit won't arrive for another week I'd expect.
Click to expand...
Click to collapse
Thankyou so much squid bro, you are great . Please make a new thread for moto e 3g 2015 version in which all the development and testing work will be carried out. I thought that i have made wrong descision by buying Moto E 3g version because of no dev support. You are a life saver bro.....
As far as testing goes , I am in.....:good:
Ravx said:
Thankyou so much squid bro, you are great . Please make a new thread for moto e 3g 2015 version in which all the development and testing work will be carried out. I thought that i have made wrong descision by buying Moto E 3g version because of no dev support. You are a life saver bro.....
As far as testing goes , I am in.....:good:
Click to expand...
Click to collapse
Here goes my second attempt. I've tried to backport my Linux 3.10.74 based "Squid Kernel" to the 3G Moto E. This is a rather crazy idea, and I don't think anyone has ever done this for the MSM8x10 family. I've managed to create a kernel binary that is half the size of the stock kernel. I don't expect this recovery to boot at all. If it does boot, I would be quite pleased.
Download link for the adventurous: https://www.mediafire.com/?j5wgj035ml7nng9
I'd suggest first trying fastboot boot twrp-otus-2.8.6-test2.img before you flash it, since it is experimental and probably won't work. If it does boot, check the file manager to see if it is able to view all your data. If it boots and is able to see your data, then we have a miracle, so go ahead and flash it if you'd like.
If this recovery doesn't boot, don't worry, I will make a recovery that works, just be patient. I'm waiting for my test unit to arrive. It's been crawling along through the USPS. Hopefully, I'll have it by this time next week.
REMINDER: This is totally untested, and probably won't work. Try at your own risk. Make sure to try booting it with "fastboot boot" before flashing it. This might brick your device. Be careful. Even if it appears to work, I don't recommend flashing anything with this recovery until I receive my test device and properly verify it.
P.S. I'll make a new thread once I have something that works.
squid2 said:
Here goes my second attempt. I've tried to backport my Linux 3.10.74 based "Squid Kernel" to the 3G Moto E. This is a rather crazy idea, and I don't think anyone has ever done this for the MSM8x10 family. I've managed to create a kernel binary that is half the size of the stock kernel. I don't expect this recovery to boot at all. If it does boot, I would be quite pleased.
Download link for the adventurous: https://www.mediafire.com/?j5wgj035ml7nng9
I'd suggest first trying fastboot boot twrp-otus-2.8.6-test2.img before you flash it, since it is experimental and probably won't work. If it does boot, check the file manager to see if it is able to view all your data. If it boots and is able to see your data, then we have a miracle, so go ahead and flash it if you'd like.
If this recovery doesn't boot, don't worry, I will make a recovery that works, just be patient. I'm waiting for my test unit to arrive. It's been crawling along through the USPS. Hopefully, I'll have it by this time next week.
REMINDER: This is totally untested, and probably won't work. Try at your own risk. Make sure to try booting it with "fastboot boot" before flashing it. This might brick your device. Be careful. Even if it appears to work, I don't recommend flashing anything with this recovery until I receive my test device and properly verify it.
P.S. I'll make a new thread once I have something that works.
Click to expand...
Click to collapse
Ok probably a noob qiestion. But does booting recovery from adb makes any changes to my device. Is there a probabilty of soft bricking the device by this method.
And should the boot loader be unlocked before trying this.
Ravx said:
Ok probably a noob qiestion. But does booting recovery from adb makes any changes to my device. Is there a probabilty of soft bricking the device by this method.
And should the boot loader be unlocked before trying this.
Click to expand...
Click to collapse
You need an unlocked bootloader. First boot your device into bootloader mode (turn phone off, press and hold PWR and VOL- together for 3 seconds, then let go). You will see a bootloader menu. Then use fastboot on your computer to boot the recovery.
Running "fastboot boot xyz.img" will not make any changes to your device. As long as you don't flash anything with the recovery, it's fairly safe to try. Booting it up and browsing with the file manager shouldn't hurt anything. Note that when you try to leave recovery, TWRP will ask you if you want to root your device with SuperSU. If you want to be safe, read the screen carefully and make sure you say no for now.
The risky operation would be to flash the recovery (fastboot flash xyz.img) and then use the recovery to flash other ROMs or customizations. I would not recommend doing this if you don't have enough experience or are worried about messing up your phone.
squid2 said:
You need an unlocked bootloader. First boot your device into bootloader mode (turn phone off, press and hold PWR and VOL- together for 3 seconds, then let go). You will see a bootloader menu. Then use fastboot on your computer to boot the recovery.
Running "fastboot boot xyz.img" will not make any changes to your device. As long as you don't flash anything with the recovery, it's fairly safe to try. Booting it up and browsing with the file manager shouldn't hurt anything. Note that when you try to leave recovery, TWRP will ask you if you want to root your device with SuperSU. If you want to be safe, read the screen carefully and make sure you say no for now.
The risky operation would be to flash the recovery (fastboot flash xyz.img) and then use the recovery to flash other ROMs or customizations. I would not recommend doing this if you don't have enough experience or are worried about messing up your phone.
Click to expand...
Click to collapse
Sorry bro but it is not booting. The steps i followed
1.) unlocked bootloader ( Success ...getting unlock msg when booting
2.) got to bootloader.
3.)booted the recovery ( i changed the name of recovery to "recovery" for convinience)
4.) cmd showed msg booting but the phone shows android logo and does not act from there.
5. I had to reboot the phone by pressing power button for 10 secs.
Have i done anything wrong????
Ravx said:
Sorry bro but it is not booting. The steps i followed
1.) unlocked bootloader ( Success ...getting unlock msg when booting
2.) got to bootloader.
3.)booted the recovery ( i changed the name of recovery to "recovery" for convinience)
4.) cmd showed msg booting but the phone shows android logo and does not act from there.
5. I had to reboot the phone by pressing power button for 10 secs.
Have i done anything wrong????
Click to expand...
Click to collapse
It might just be that it doesn't work, but your comment about it showing the Android logo doesn't sound right. Does it show a "dead" android logo laying on its back with a door open on its body? If you see that, you booted up the stock recovery. The stock recovery will show that logo forever until you use a certain button combo to bring up a menu.
How did you boot the recovery? I assume you downloaded my file, renamed it to "recovery.img", and then ran this command from the folder that contains my recovery image:
Code:
fastboot boot recovery.img
squid2 said:
It might just be that it doesn't work, but your comment about it showing the Android logo doesn't sound right. Does it show a "dead" android logo laying on its back with a door open on its body? If you see that, you booted up the stock recovery. The stock recovery will show that logo forever until you use a certain button combo to bring up a menu.
How did you boot the recovery? I assume you downloaded my file, renamed it to "recovery.img", and then ran this command from the folder that contains my recovery image:
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
No it showed the logo of moto powered by android and yes i renamed the file and entered the same command you typed.
As soon as i typed it. It showed that logo and got hanged. And then i rebooted. And it booted normally.
Ravx said:
No it showed the logo of moto powered by android and yes i renamed the file and entered the same command you typed.
As soon as i typed it. It showed that logo and got hanged. And then i rebooted. And it booted normally.
Click to expand...
Click to collapse
I had someone else try it too, with the same result as you. No big surprise to me, didn't expect it to work. I'll make one with a more conventional 3.4.x kernel when I get time.
Otus TWRP Attempt 3
@Ravx
Alright everyone, I've made a third attempt at creating a recovery for the Moto E 3G. I still don't have the device, so you have to test yourself. I made this one with a more conventional 3.4.x kernel. I would guess that this recovery is more likely to work than the the previous one. As before, try fastboot boot xyz.img before flashing. I suspect that this recovery might boot sometimes and fail other times. If it fails to be boot the first time, try a couple more times before giving up.
Download Link: http://www.mediafire.com/download/1he2ys1832441s7/twrp-otus-2.8.6-test3.img
If it boots, try using the file manager. Check that it is able to see all your files. I don't recommended using this recovery to flash things until I'm able to verify it myself.
Try at your own risk. I'm not responsible for messing up your device. This recovery has not been tested.
squid2 said:
@Ravx
Alright everyone, I've made a third attempt at creating a recovery for the Moto E 3G. I still don't have the device, so you have to test yourself. I made this one with a more conventional 3.4.x kernel. I would guess that this recovery is more likely to work than the the previous one. As before, try fastboot boot xyz.img before flashing. I suspect that this recovery might boot sometimes and fail other times. If it fails to be boot the first time, try a couple more times before giving up.
Download Link: http://www.mediafire.com/download/1he2ys1832441s7/twrp-otus-2.8.6-test3.img
If it boots, try using the file manager. Check that it is able to see all your files. I don't recommended using this recovery to flash things until I'm able to verify it myself.
Try at your own risk. I'm not responsible for messing up your device. This recovery has not been tested.
Click to expand...
Click to collapse
Bro you have done it. the recovery booted and i moved a file from one folder to another by using file manager. :good::good::laugh:
EDIT: For now i the recovery's file manager isnt showing "build.prop" and other folders in /system
only the "bin" folder is visible. Is it ok beacaause we havent flashed the recovery or its the other way around.
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
AndriyEtch said:
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
Click to expand...
Click to collapse
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
cva_kabil said:
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
Click to expand...
Click to collapse
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
AndriyEtch said:
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
Click to expand...
Click to collapse
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
cva_kabil said:
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
Click to expand...
Click to collapse
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
I dont think so... I hv not tried... But as of i know if u edit it wrongly, u will not be able to flash that file. . Try others methods first... Hope it works
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
Hi OP, sorry for joining late to the party
So the thing is the OnePlus X is at opposites now since the official MM release on 29th September. The thing is if you are running the old bootloader (OxygenOS 2.x.x) or any ROM based on it, then the New TWRP will not boot, neither will the Stock Recovery that is hosted on the OnePlus download section for the X, which is where i assume you download the stock recovery from, right ? Also note that the official recovery hosted on the TWRP website is also yet to be updated, we're working on that.
So you are on the old Bootloader. Simple stuff. I have posted my guide a lot of time around the forums, its gained a lot of merit. You could follow it for your update process. I'll leave a link below. In case you wanna verify that the old bootloader is causing the issue my Index Thread pinned in the general section has a link for the Stock recovery for Old bootloader, try flashing that via fastboot, if it successfully boots then you're set.
Comprehensive guide to Update to Marshmallow Bootloader
The above guide is centered to the thread i have posted it on but the process is 99% the same. In the end, you could just stay with Oxygen OS 3.1.3, or flash any custom ROM based on the new Bootloader.
Now regarding your query about editing the META of the ROM, well Yes to an extent it IS risky if you ain't careful because my guide guides you to delete the one single line that removes the device check, so as long as you use the modified zip on OnePlus X only, there will be no issues.
Let me know for any further clarifications, also you're welcome to join our support group on Telegram, all of our developers are active there. Ping me (@ mellogang_unite) for an invite
Hi, good evening to the community!
(EDIT: Anyway, I want to apologize if I'm doing something wrong. I recently joined).
I believe I made the biggest mess of my life, and now I'm desperate. I downloaded the latest version of TWRP, to update the one I already used; the problem is that. Now he is no longer in Recovery Mode. And worst of all? I had already deleted my OS. So, there's no way I can authorize OEM unlocking. So I can not use ADB & Fastboot. And I think I have to throw my device away as it is unusable. What should I do? I'm desperate and there are no solutions.
-Thanks
Lord_Miraak said:
Hi, good evening to the community!
(EDIT: Anyway, I want to apologize if I'm doing something wrong. I recently joined).
I believe I made the biggest mess of my life, and now I'm desperate. I downloaded the latest version of TWRP, to update the one I already used; the problem is that. Now he is no longer in Recovery Mode. And worst of all? I had already deleted my OS. So, there's no way I can authorize OEM unlocking. So I can not use ADB & Fastboot. And I think I have to throw my device away as it is unusable. What should I do? I'm desperate and there are no solutions.
-Thanks
Click to expand...
Click to collapse
There is no need to worry if you corrupt you recover, just enter into bootloader mode then flash the recovery.
code:-fastboot flash recovery moto.img
Note:- Moto should be replaced with the recovery name
If you want to return to stock ROM then here is the procedure:-
Firmware:-https://mirrors.lolinet.com/firmware/moto/surnia/official/
Procedure:-https://www.google.com/amp/s/forum....tore-moto-e-2015-stock-firmware-t3044936/amp/
Done now you are now stock ROM .
riyan65 said:
There is no need to worry if you corrupt you recover, just enter into bootloader mode then flash the recovery.
code:-fastboot flash recovery moto.img
Note:- Moto should be replaced with the recovery name
If you want to return to stock ROM then here is the procedure:-
Firmware:-https://mirrors.lolinet.com/firmware/moto/surnia/official/
Procedure:-https://www.google.com/amp/s/forum....tore-moto-e-2015-stock-firmware-t3044936/amp/
Done now you are now stock ROM .
Click to expand...
Click to collapse
Yes thanks! I did it yesterday, watching a Brazilian video. I had to download 3 different ROMs to be able to do such a process; so I did the process through Fastboot. Thank God I did not have to buy another device, hehe. And I'm already using another Custom Rom at the moment (RR, but I plan to change it as soon as I find another great new one that does not bug WhatsApp). Thank you again!
I bricked my phone by flashing a patched boot image from 11.0.2 to a phone with 11.0.0 and I can't get to fastboot mode - etc. I think MSM is my only way back?
I got it to fastboot mode, but there's no boot image for 11.0.0 available, right? Please help
Is it T-Mobile version or unlocked?
There's MSM tool for T-Mobile version and you can download full ROM for unlocked
If yours is unlocked and you can access recovery, use sideload
Code:
adb sideload
Press spacebar once and drag and drop the ROM onto command window and press enter
This can fix boot as well as making version update
bouyakasha said:
I bricked my phone by flashing a patched boot image from 11.0.2 to a phone with 11.0.0 and I can't get to fastboot mode - etc. I think MSM is my only way back?
Click to expand...
Click to collapse
there is no msm tool for the full paid version from OP store .. only for T-Mobile .. but if you phone is still under waranty please get a hold of tech support and tell them you request a remote session and that your phone is seen by your computer . they will have you fill up some forms via email and send you the link to download the tools .. if you do please share them here .. when i had my issue they didnt have the tools available and chose not to send my phone back so i am like you with a briked phone
T-Mobile Variant MSM Tools:
[OPN2005G] [OOS TMO DE18CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: I hope you don't break your phone, but if you do, it's not my fault. Since you are choosing to modify your phone, you accept full responsibility for whatever happens to it, including any damage that may have occurred as a result of...
forum.xda-developers.com
Do not use this on any other variant.
I have no idea how to send it, but I have a boot.img from my factory unlocked N200 (Model DE2117) on firmware Oxygen OS 11.0.0.0.DE17AA. I also have a magisk patched copy of that boot.img. Let me know how to send it and you can give it a shot.
I have found fastboot flashing method for 8T to flash unlocked ROM on T-Mobile version (unlocked bootloader required).
Since T-Mobile version MSM is available, I can use it if anything goes wrong
Stay tuned
amboyscout said:
I have no idea how to send it, but I have a boot.img from my factory unlocked N200 (Model DE2117) on firmware Oxygen OS 11.0.0.0.DE17AA. I also have a magisk patched copy of that boot.img. Let me know how to send it and you can give it a shot.
Click to expand...
Click to collapse
wow .. please upload it to google drive or mega (dot) nz and post the link here .... honestly this gets me very excited ...
mingkee said:
I have found fastboot flashing method for 8T to flash unlocked ROM on T-Mobile version (unlocked bootloader required).
Since T-Mobile version MSM is available, I can use it if anything goes wrong
Stay tuned
Click to expand...
Click to collapse
my bootloader is locked .. thats why MSMDownload tool is a must
edale1 said:
T-Mobile Variant MSM Tools:
[OPN2005G] [OOS TMO DE18CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: I hope you don't break your phone, but if you do, it's not my fault. Since you are choosing to modify your phone, you accept full responsibility for whatever happens to it, including any damage that may have occurred as a result of...
forum.xda-developers.com
Do not use this on any other variant.
Click to expand...
Click to collapse
I tried that on my full paid one from oneplus.com and it dont work ... so yes its a waste to download it for nothing
[GUIDE] Convert TMO to EU via MSM Tool, no SIM Unlock or Bootloader Unlock needed!
*** Use this at your very own risk. *** You will lose all data *** Backup your working modem and persist, just in case *** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took...
forum.xda-developers.com
There's a maual method.
If you're familiar with fastboot flash with Moto phone, yes, similar commands.
Download full ROM and unpack with payload dumper, and flash every .img one by one
Dimitrimem said:
I tried that on my full paid one from oneplus.com and it dont work ... so yes its a waste to download it for nothing
Click to expand...
Click to collapse
If you use the "+ Quote" button, rather than the reply button, it'll create a multiquote, letting you quote and reply to multiple posts all at once (it'll add a "insert quotes" button to the reply box). This eliminates double-posts, which most forums frown upon.
@Dimitrimem here ya go https://drive.google.com/drive/folders/1DzR0uEdyFeBeID4sVaT96z0Y88sMaomL?usp=sharing
Dimitrimem said:
there is no msm tool for the full paid version from OP store .. only for T-Mobile .. but if you phone is still under waranty please get a hold of tech support and tell them you request a remote session and that your phone is seen by your computer . they will have you fill up some forms via email and send you the link to download the tools .. if you do please share them here .. when i had my issue they didnt have the tools available and chose not to send my phone back so i am like you with a briked phone
Click to expand...
Click to collapse
Tried this today. Now waiting on OnePlus to respond.
bouyakasha said:
Tried this today. Now waiting on OnePlus to respond.
Click to expand...
Click to collapse
Don't wait to long for their reply .. if they don't answer call them on the phone.. it takes less than a minute to have them speak with you ... I dragged it for too long with them waiting 7 days to send me a shipping label than another 5 for another try at it .. another 4 to get the link for download ..after all that they said they don't have it... but this was a while back ... I'd be on that phone fast.. tell them you need your phone as it's the only one ... honestly if you can get the msm tool it would be amazing
mingkee said:
[GUIDE] Convert TMO to EU via MSM Tool, no SIM Unlock or Bootloader Unlock needed!
*** Use this at your very own risk. *** You will lose all data *** Backup your working modem and persist, just in case *** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took...
forum.xda-developers.com
There's a manual method.
If you're familiar with fastboot flash with Moto phone, yes, similar commands.
Download full ROM and unpack with payload dumper, and flash every .img one by one
Click to expand...
Click to collapse
I am familiar with this from Moto, and some previous manual flashes with my OEM OP5. However, after extracting the partition .imgs from the OOS OTA via this tool when I try to `fastboot flash logo logo.img` (among others), I get hit with `FAILED remote: flashing is not allowed for critical partitions`, even after having unlocked with `fastboot flashing unlock_critical`. How were you able to get everything to work?
I also tried flashing the OTA zip via the TWRP, but it seems like the current dev version of TWRP in that thread is completely borked for N200 as far as ROM flashing goes ://
darkghost568 said:
I am familiar with this from Moto, and some previous manual flashes with my OEM OP5. However, after extracting the partition .imgs from the OOS OTA via this tool when I try to `fastboot flash logo logo.img` (among others), I get hit with `FAILED remote: flashing is not allowed for critical partitions`, even after having unlocked with `fastboot flashing unlock_critical`. How were you able to get everything to work?
I also tried flashing the OTA zip via the TWRP, but it seems like the current dev version of TWRP in that thread is completely borked for N200 as far as ROM flashing goes ://
Click to expand...
Click to collapse
You have to flash in fastbootd (... reboot fastboot) as instructed in 8T forum
mingkee said:
You have to flash in fastbootd (... reboot fastboot) as instructed in 8T forum
Click to expand...
Click to collapse
Ok so now I'm stuck here as well (saw your comment in the other thread):
mingkee said:
I attempted to flash unlocked ROM on bootloader unlocked T-Mobile version phone
It stuck on products.img. The error stated "not enough space for the partition"
What happened?
Click to expand...
Click to collapse
Any luck getting past this?
darkghost568 said:
Ok so now I'm stuck here as well (saw your comment in the other thread):
Any luck getting past this?
Click to expand...
Click to collapse
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
Towards the bottom of that post it talks about getting past that error.