Alright, so I know what went wrong. I messed up, I know I did, so please try not to mention it.
I accidentally deleted my lib folder in the /system directory using root explorer. What I was trying to do is replace it with the one found in a different thread (as I was missing some files that I needed to receive the BELL OTA update)
So now the phone will not boot past the above mentioned logo (thread title)
I have tried going into android recovery and wiping and restoring all data but that did not help, my phone is not unlocked and I have never installed a different ROM.
What should I do?
I may be wrong, but if you are not unlocked, you may have to do a full SBF flash to get back up and running. If you were unlocked you could just flash a system.img via fastboot.
Alright, I will look into that, right now I am at school so if you could give me a link to a guide for the Bell Motorola Atrix I would appreciate it, if not I will search through the forums for it later.
Thanks for the help!
what did you make on your case.
I have the same problem.
Please help me
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
I have the LG v10 from T-Mobile. I bought the phone a few weeks ago and it had Marshmallow installed. Somehow I managed to install TWRP/SuperSU, but then had issues and flashed the official/stock MM image with LGUP. Afterwards I discovered that MM for this device is not currently rootable, and TWRP cant be flashed via fastboot because MM blocks it. So I returned the device to T-Mo store, lied and said it force-upgrade to MM and had began freezing up. They did an in-store trade for an identical model that had 5.1.1 Lollipop.
The device is currently still in factory condition in every way, with the exceptions that I unlocked the bootloader via fastboot and installed TWRP. Nothing else is modified yet and no custom ROMs have been flashed.
I recently became aware that there is no stock LP image for the T-Mo v10, only MM images are available. After all the issues I've had, I'm now paranoid and want to have a complete dump of the phone's entire contents (partitions, bootloader, system, etc) that is in KDZ or TOT format, and can be reflashed with the standard tools available. Since there is nothing official then I would have to do this myself. This would be useful in the event that I run into lots of issues and need to do a emergency stock restore.
I found a thread by XDA user @tungkick, in which he created a modified dump of the device while it was running LP. However, because it was unofficial and he didn't disclose this upfront, his thread was shut down. His file bricked multiple MM users. I assume it would work if one was still on LP and hadn't upgraded to MM. Not to mention that I cant seem to find his file anywhere. So I figure the safest way is to do this myself. I would be willing to make this file available to the community when finished, with full disclosure that it is unofficial. But the problem is, I don't know how.
I know that the Linux dd command can be used to dump images of various things, and I have read that this can be done on PC by connecting to the device via ADB or fastboot. This would hopefully result in an image file that contained the contents of all the device's partitions.
But another issue would be converting it to KDZ or TOT. And it would have to be done in such a way that it would be flashable with the standard tools.
Can someone please give me a technical understanding of the tools and knowledge I would need to undertake this? Would it be too complicated for someone like myself that has little Android/Linux experience (but is generally competent with computers/technology)?
Thanks for any advice!
Noone can help me with this?
To the mods/admins: I think maybe I posted this in an area where it is unlikely to get any useful answers. Can someone move the thread to the Help& Troubleshooting area of the general LG v10 forum (not here in the T-Mobile subforum)? Thanks!
I think it's just that if that could. have been done someone would have done it already. Even tungkick didn't make one for tmobile for some reason. I think because he made his root injected files from official lg files and lg has not released a kdz or tot for tmobile LP.
Just my observation... I could be wrong.
Sent from my pretty nifty brand new LG V10
@ planetbeen: I don't see why it wouldn't be possible. Linux's dd program can dump almost any connected device that it can see. But then it needs to be converted into a standard TOT/KDZ that can be flashed with any standard software. Which is why I want to create an unofficial backup of the entire phone before modifying it further, so I can do an emergency restore if necessary. I just need the right instructions from people who have the technical expertise.
I had trouble with my old LG v10, I had used LG's LGUP program to flash it to Marshmallow from my PC, only to realize that it couldn't be rooted or have a custom recovery. And I also discovered that I couldn't downgrade to Lollipop. So I returned the phone to the store and exchanged it for an identical model that still had LP. I just told them it had auto-upgraded to MM and started crashing. They exchanged, no questions. Before this I had various issues, like GPS crashing randomly when turning it on, Bluetooth also doing the same thing, and the Settings app also crashed sometimes when accessing the Security menu. I had flashed multiple ROMs, but stock-based and CM/AOSP-based, but kept running into issues, oftentimes the same ones. So I figured that something in the phone had become corrupt and figured that flashing stock MM would fix everything. Big mistake. I'll never let this phone upgrade again until MM is solidly hacked, which from what I've read may be a long time away. I paid enough for this phone and I really value hackability. I'm not the average Joe that just uses my phone for Facebook, etc. To me, if a phone cant be hacked, then buying/owning it is a waste of time/money. Same thing with every computer/electronics device I've ever owned.
Thanks again!
It looks like I'm going to have problems getting answers from knowledgable people, so instead of waiting, I'm going to take a little initiative and at least try to do the dump with dd. I found a post by @tungkick that says to enable USB debugging and make a backup file via dd with the 'adb shell' and 'su' commands. Is the following syntax correct?
dd if=/dev/block/mmcblk0 of=/sdcard/H901.bin bs=1024 count=6291456
Do I run these commands from a PC via command line while connected via USB? Or directly on the device in a terminal emulator? Or do I need to run the command while in fastboot/bootloader mode, while Android is powered down?
Thanks again!
Stock use tool extract kdz then choose file dz (use lgup)
remember can not flash if phone update 6.0
Never downgrade because phone brick now.
version 5.1.1
https://drive.google.com/file/d/0B_Hol5T47S-bQkJVemgzMDV0Nzg/view?usp=sharing
@ tungkick: Thanks for the info. I had used the dd command to dump my phone to external SD before, but the file was 6GB! I was unable to use Tool KDZ Extract to extract the *.dz from the *.kdz file you provided. I was able to flash your KDZ with LGUP, but it boots me into TWRP recovery near the end.
Do you mind if I publicly distribute a mirror copy of your file on my Dropbox, so that it will be available to others that need the stock LP firmware for this device?
Thanks again!
I just wanted to say that flashing your KDZ has possibly screwed up my device permanently. Your image has TWRP, not the stock recovery, and is pre-rooted with SuperSU. Normally this would be good but...............
Near the end of LGUP, the device boots into TWRP. System and MicroSD are mounted, but nothing else (data, cache, dalvik, etc). I was able to obtain a stock recovery *.img, then copied it over to my MicroSD while in recovery. Then I flashed it, booted the phone into stock recovery, and performed a factory reset. Afterwards I booted into system, and all looked good, until it got to the "Checking connection" screen, then a lot of apps started force-closing repeatedly. Because of this I can't get to the Home screen, and no amount of factory reset is working. It just keeps happening over and over again.
How to get out of this mess, anyone?
Help please!!!
Still looking for a solution and would really appreciate any help!
My theory is that the /cache and /data partitions somehow got corrupted during the flash. So I tried booting into FastBoot mode and issueing the commands:
fastboot erase cache
fastboot format cache
fastboot erase userdata
fastboot format userdata
It just says something something along the lines of "remote: cant format/erase in an unlocked state". If I relock the bootloader, it says that it cant erase/format in a locked state.
TWRP still cant read those partitions (they won't mount and cant be mounted), and the apps still start force-closing almost immediately after rebooting into system, before I can complete the setup, preventing me from getting to the home screen.
@ tungkick: Is there any possibility we can arrange a TeamViewer meeting to fix this?
Thanks!