HARD BRICKED AFTER INSTALLING 4.4.4 UPDATE IN MOTO E 1st gen


Question

When I updated my mobile, it power offed then it gone to bootloader mode then I pressed on normal power, but it didn't, so I press on recover, it gone to TWRP mode and I pressed on recover, there some codes happened, and then it gone off. till then nothing working.



not even charging, and not opening bootloader too.



pls I need your suggestion. THANK YOU



This video on Youtube (published March 2015) is showing same problem that I have. You can see in the comments that still this problem is going on.



see article about Easy JTAG on internet. you can understand how this begin and end.


Answer

There are really only 4 viable solutions for a hard bricked Moto "letter" device, assuming this is truly hard bricked and not a battery or charging issue. Being hard bricked on one of these devices means that the bootloader is inaccessible and the device doesn't boot, if the bootloader is inaccessible we have few options remaining for self-repair.



Qualcomm HS-USB Qloader 9008 - All Qualcomm devices have the ability to be hard flashed with the proper files. Although this is an option for many devices, it is not for these devices because Moto/Lenovo will not release the necessary files. Thus this is not a valid option for these devices, I only bring this up because searching the internet will return many references to this tool, but we cannot use it thanks to Moto/Lenovo policy on these devices. - Source



JTAG programming - Requires an external device and ROM files, assuming the partitioning is still intact this is a viable option although for lower end or older devices, the price of the programmer is often significantly more than the value or replacement cost of the device, with modest units costing around $200USD (source) without the necessary cables which sometimes need to be purchased separately or fabricated, and the initial cost of this device when new was $100USD and it's current value is around $30USD, most likely makes this option undesirable.



Authorized Service Center - Have the device repaired by an authorized Moto service center. Due to the age of this device, it is likely out of warranty and the cost will likely be more than the device's value or replacement cost. I have no reference for this information, so it might be worth your time to investigate it yourself, if this was the result of an official OTA update, it may be possible to find a sympathetic ear at a local authorized repair center.



So this brings us to the Final Option... As noted in some of my previous options, the cost/value of the device needs to be considered here. The Moto E is a low-end, low cost device and was released in May 2014, just over 3 years ago. This device has very little value and a replacement unit would likely cost less than any valid repair option, so it may just be time to discard/recycle the device and purchase a new or used replacement device.



Like many things in life, not everything can be feasibly or economically repaired, sometimes you just have to accept that and move on.


Topics


2D Engines   3D Engines   9-Patch   Action Bars   Activities   ADB   Advertisements   Analytics   Animations   ANR   AOP   API   APK   APT   Architecture   Audio   Autocomplete   Background Processing   Backward Compatibility   Badges   Bar Codes   Benchmarking   Bitmaps   Bluetooth   Blur Effects   Bread Crumbs   BRMS   Browser Extensions   Build Systems   Bundles   Buttons   Caching   Camera   Canvas   Cards   Carousels   Changelog   Checkboxes   Cloud Storages   Color Analysis   Color Pickers   Colors   Comet/Push   Compass Sensors   Conferences   Content Providers   Continuous Integration   Crash Reports   Credit Cards   Credits   CSV   Curl/Flip   Data Binding   Data Generators   Data Structures   Database   Database Browsers   Date &   Debugging   Decompilers   Deep Links   Dependency Injections   Design   Design Patterns   Dex   Dialogs   Distributed Computing   Distribution Platforms   Download Managers   Drawables   Emoji   Emulators   EPUB   Equalizers &   Event Buses   Exception Handling   Face Recognition   Feedback &   File System   File/Directory   Fingerprint   Floating Action   Fonts   Forms   Fragments   FRP   FSM   Functional Programming   Gamepads   Games   Geocaching   Gestures   GIF   Glow Pad   Gradle Plugins   Graphics   Grid Views   Highlighting   HTML   HTTP Mocking   Icons   IDE   IDE Plugins   Image Croppers   Image Loaders   Image Pickers   Image Processing   Image Views   Instrumentation   Intents   Job Schedulers   JSON   Keyboard   Kotlin   Layouts   Library Demos   List View   List Views   Localization   Location   Lock Patterns   Logcat   Logging   Mails   Maps   Markdown   Mathematics   Maven Plugins   MBaaS   Media   Menus   Messaging   MIME   Mobile Web   Native Image   Navigation   NDK   Networking   NFC   NoSQL   Number Pickers   OAuth   Object Mocking   OCR Engines   OpenGL   ORM   Other Pickers   Parallax List   Parcelables   Particle Systems   Password Inputs   PDF   Permissions   Physics Engines   Platforms   Plugin Frameworks   Preferences   Progress Indicators   ProGuard   Properties   Protocol Buffer   Pull To   Purchases   Push/Pull   QR Codes   Quick Return   Radio Buttons   Range Bars   Ratings   Recycler Views   Resources   REST   Ripple Effects   RSS   Screenshots   Scripting   Scroll Views   SDK   Search Inputs   Security   Sensors   Services   Showcase Views   Signatures   Sliding Panels   Snackbars   SOAP   Social Networks   Spannable   Spinners   Splash Screens   SSH   Static Analysis   Status Bars   Styling   SVG   System   Tags   Task Managers   TDD &   Template Engines   Testing   Testing Tools   Text Formatting   Text Views   Text Watchers   Text-to   Toasts   Toolkits For   Tools   Tooltips   Trainings   TV   Twitter   Updaters   USB   User Stories   Utils   Validation   Video   View Adapters   View Pagers   Views   Watch Face   Wearable Data   Wearables   Weather   Web Tools   Web Views   WebRTC   WebSockets   Wheel Widgets   Wi-Fi   Widgets   Windows   Wizards   XML   XMPP   YAML   ZIP Codes