Hey all. I have reached a defect in my research and I could use some help.
I have a Wifi Xoom that I fried the mother board on. Not sure how, just woke up one morn and it wouldn't turn on anymore.
So I replaced that MOBO with another that was listed as soft bricked (It was cheep so I figured why not try).
Anyway with the new board installed I can boot to the Motorola Logo, I can load fastboot, recovery and RSD. The device appears as it should on my pc and I can fastboot flash.
I replaced the system image, the recovery image, The userdata image and the boot image. using fastboot. I also cleared cache, from fastboot and recovery as well as deleting all user data from recovery (Factory Reset).
I also re-installed the whole system using an RSD Image which went successfully as well.
Now I know its actual flashing because I flashed a different recovery to test and that worked, but for some reason im stuck in a boot loop at the Motorola Logo. I can still access all features (fastboot, recovery and RSD) but it will not boot past the Moto Logo.
I have tried installing the 4.1.1 and 4.1.2 updates through recovery which both installed their updated boot loaders and for a moment I thought I had success when I saw the xoom boot image with the flashing squares, but then that froze and it rebooted never to be seen again.
So my question is, is this a hard brick and I should just stop trying or does anyone have any other suggestions?
Also I am not using a Moto cable, but it tells me that I am successfully flashing, and as I stated I am seeing the recovery flash correctly, Does this make a difference being that I have successful flashes for other partitions? Is the Boot partition special? It tells me I'm flashing, but is it lying to me?
Everything I read thus far indicates that if you can access fastboot and recovery that its not hard bricked, but what exactly does a hard brick look like?
Thanks All any insight is appreciated.
Hey all, i made my own Motorola usb cable and tried to reflash again with no success. I'm still boot looping.
Sent from my SCH-I535 using xda premium
I have and tried with an official Motorola cable now as well without success. ideas?
Sent from my SCH-I535 using xda premium
Try reflashing the official imgs (provided from motodev site) with fastboot and after locking your bootloader. Try booting up, if nothing changes, sorry but I doesn't know how to fix then. Hope it works...
Sent from my MZ601 using XDA HD Premium using 1/8of my brain, the other 7/8 is thinking in my love Isadora
Yea I tried that, no worries, but do you know what does a hard brick look like? I have searched and found no real description, all anyone says is if you can get to fast boot is more than likely not.
Sent from my SCH-I535 using xda premium
OK , I know its been a while but I just started playing with this again.
OK so I got the idea that it might be a permissions issue. so I wiped everything again and re-installed again. Following this I tried to fix permissions in TWRP which failed. I installed CWM and ran fix permission which was successful. after that I was able to boot the tablet to android and install an account.
However now it is rebooting with some frequency and periodically it will get stuck at the moto screen again.
At this point if I perform a data wipe and clear cache I can get the tablet to boot again but I still have this issue.
Also If I fix permissions again from either recovery or rom manager it sends me back to the being stuck at the moto screen and I have to start again.
Thoughts?
Related
So I was cruising around the Nexus S forums and found a rom I liked after I unlocked and rooted my phone.
I flashed Paranoid Android and then flashed the Matr1x kernel. Thus putting me in a neverending bootloop.
No ability to go back to CWM so I can't restore. And I can't put it in download mode so no ODIN.
What the heck do I do?
Can anyone help?
BTW if this is actually called a soft brick I'm sorry my terminology might be off.
Also I did this because the last phone I did extensive flashing with was an HTC Inspire 4G and it was easy to flash stuff just clear everything and flash what you wanted no bootloops. Sadly this phone not so much.
Hmm... No recovery...I've been stuck in a bootloop but I had recovery!
Sorry for the useless post, I cant help you..
Are you able to get into bootloader?
Usually when a bootloop occurs you should still be able to go in recovery.
When you say "no ability to access CWM" do you mean ROM Manager? Or the recovery mode?
What happens when you try to access the recovery mode?
same issue like urs
http://forum.xda-developers.com/showthread.php?t=1775933
try clean install;
flash Rom-Wiper.zip
flash Dalvik-Wiper.zip
then;
factory reset,
Format the system, data, cache, boot & partitions of your device.
I mean no access to recovery. CWM is Clock Work Mod Recovery. I have no access to fastboot either. The only thing my phone can do is bootloop.
You have to be mistaken.
Press power and volume up to get into fastboot ( bootloader). Then pick recovery....
That rom or kernel will not erase recovery. If your phone is in a bootloop it is making it past the bootloader
So it appears it as if I was mistaken. I got into fastboot and booted into CWM I'm still confused as to what I did, but I think I corrupted the Kernel.
It was the weirdest thing though. I tried it at least a dozen times, then I tried to run down the battery and try it again afterwards, and it didn't work so I gave up. Then I tried it again about 5 minutes ago and it worked. I'm sorry I cause you guys so much confusion. I've been doing this for so long I guess I just didn't doubt I was doing it right.
Hey guys,
I've been using this website as reference for years but never had an issue I hadn't already seen asked.
I've been looking for weeks for a solution to this and haven't found anything.
I tried to flash cm10.1 over my stock 4.1.2 and corrupted the system.
It was booting directly to AP Fastboot and showing an error about not calling the ROM properly.
I tried reflashing using RSD Light 5.7 but every time it tried to flash the system it said the phone returned failed.
So I upgraded RSD to v6.1 and tried again. This time the phone says it flashed properly but it freezes during the droid boot logo.
I've tried using the utility and it gives me the same results.
I can get into factory recovery and I've performed several hard resets. But the phone still freezes whenever it tries to load the system.
I'm using a Motorola Factory Cable on a high speed USB port.
Any ideas why I'm stuck in a soft brick that I can't flash out of?
ShiningRaven said:
Hey guys,
I've been using this website as reference for years but never had an issue I hadn't already seen asked.
I've been looking for weeks for a solution to this and haven't found anything.
I tried to flash cm10.1 over my stock 4.1.2 and corrupted the system.
It was booting directly to AP Fastboot and showing an error about not calling the ROM properly.
I tried reflashing using RSD Light 5.7 but every time it tried to flash the system it said the phone returned failed.
So I upgraded RSD to v6.1 and tried again. This time the phone says it flashed properly but it freezes during the droid boot logo.
I've tried using the utility and it gives me the same results.
I can get into factory recovery and I've performed several hard resets. But the phone still freezes whenever it tries to load the system.
I'm using a Motorola Factory Cable on a high speed USB port.
Any ideas why I'm stuck in a soft brick that I can't flash out of?
Click to expand...
Click to collapse
Format system via any of the custom recoveries before flashing your new ROM - this will wipe out any leftover problems completely & should let you start 100% fresh with a new ROM.
tzlot said:
Format system via any of the custom recoveries before flashing your new ROM - this will wipe out any leftover problems completely & should let you start 100% fresh with a new ROM.
Click to expand...
Click to collapse
I lost my root when I originally got stuck in fastboot. And I can't boot up the phone until I can get it fixed.
ShiningRaven said:
I lost my root when I originally got stuck in fastboot. And I can't boot up the phone until I can get it fixed.
Click to expand...
Click to collapse
Can you get back into fastboot now? If so
Use fastboot to flash a custom recovery (CWM, TWRP or OUDHS)
use the recovery to factory reset, wipe cache/dalvic, AND format system (sometimes in the advanced menu)
then flash rom of your choice.
If you can't get fastboot working you'll need smarter help than I can give you... but the format system step clears out all kinds of gremlins.
I can get into fast boot but I don't have an unlocked boot loader to flash anything custom.
ShiningRaven said:
I can get into fast boot but I don't have an unlocked boot loader to flash anything custom.[/QUOTE
If you can get into fastboot then you should be able to unlock b/l with this toolkit I used it and it worked for me you can also flash rom with it its in the orginial development thread
http://forum.xda-developers.com/showthread.php?t=2154995
Click to expand...
Click to collapse
ShiningRaven said:
So I upgraded RSD to v6.1 and tried again. This time the phone says it flashed properly but it freezes during the droid boot logo.
I've tried using the utility and it gives me the same results.
I can get into factory recovery and I've performed several hard resets. But the phone still freezes whenever it tries to load the system.
I'm using a Motorola Factory Cable on a high speed USB port.
Any ideas why I'm stuck in a soft brick that I can't flash out of?
Click to expand...
Click to collapse
Had the same problem after a fastboot via the utility. Try powering your phone down completely and leaving it off for about 5-10 min. This can be tricky with the hardware buttons so if you have access to TWRP that will help as it has a power off option. You might also try flashing again via the utility. I believe that's what I had to do, but the power down method is what a friend suggested based of his experience with the same exact problem you documented.
FIXED!!!
OK first I want to thank everybody who responded. I got tied up with work and kind of forgot about this project for a few days.
Repeated uses of the Utility and RSD both left me stuck with the phone freezing every time it tried to load the system into memory.
I had checked out the toolbox before but I didn't think I could do much from a locked bootloader.
After your suggestion jmcdonald I tried it again. It says my device isn't available to be unlocked so I tried downgrading back to ICS.
The toolbox says that it failed but it must have fixed something because the phone booted back up to android 4.1.2 stock!
So far I have bricked a lot of phones and learned a lot about ADB in the process of fixing them but I've never had one I was so certain was bricked permanently. But now it seems to be working fine, I'm scared to try rebooting in now.
Definatly going to unlock the bootloader pronto.
Thanks again jmcdonald!
I haven't seen this written anywhere yet but I've found something weird with the TWRP loop, months back I used the asus system wipe and got stuck in the TWRP loop because I supposedly erased all the data and file structures on my system but every now and then I keep checking for fixes and playing around with the tablet, today I charged it up again and went into TWRP, on the PC (win 7) ran the cmd "ADB reboot bootloader", for the hell of it I chose the middle option, the android, is said cold booting linux, the chrome asus logo came up with the spinning dot animation and I just waited and then it began updating my app's and my system loaded right up, everything was there. There's no sd-card in the external slot so it's pulling straight from the tablet, wifi connected, all my apps began updating from the marketplace, I can download, TWRP just says the tablet is blank. It seems to have no root access anymore though, hopefully this can be helpful. Also if I reboot it goes right back to TWRP but if I run the reboot bootloader cmd and choose the android it starts right back up without having to update everything again.
pariahcomplex said:
I haven't seen this written anywhere yet but I've found something weird with the TWRP loop, months back I used the asus system wipe and got stuck in the TWRP loop because I supposedly erased all the data and file structures on my system but every now and then I keep checking for fixes and playing around with the tablet, today I charged it up again and went into TWRP, on the PC (win 7) ran the cmd "ADB reboot bootloader", for the hell of it I chose the middle option, the android, is said cold booting linux, the chrome asus logo came up with the spinning dot animation and I just waited and then it began updating my app's and my system loaded right up, everything was there. There's no sd-card in the external slot so it's pulling straight from the tablet, wifi connected, all my apps began updating from the marketplace, I can download, TWRP just says the tablet is blank. It seems to have no root access anymore though, hopefully this can be helpful. Also if I reboot it goes right back to TWRP but if I run the reboot bootloader cmd and choose the android it starts right back up without having to update everything again.
Click to expand...
Click to collapse
so if you can get to bootloader. why dont you fastboot flash the blob file for the latest update? this would install system and new bootloader and stock recovery. from there regaining control of tablet. then just fastboot flash twrp and flash a custom rom....just a thought but if your getting into bootloader you should be able to flash blob.
I tried that right when I saw fast boot coming up, nothing would go through, I did fix it by using the method posted by Buster by using fast boot to systematically erase everything one by one then flash new firmware, just thought this info might be helpful, it's almost like twrp becomes a separate partition when you use asus wipe since everything is still there and bootable
kaos420 said:
so if you can get to bootloader. why dont you fastboot flash the blob file for the latest update? this would install system and new bootloader and stock recovery. from there regaining control of tablet. then just fastboot flash twrp and flash a custom rom....just a thought but if your getting into bootloader you should be able to flash blob.
Click to expand...
Click to collapse
I'm having issues and this won't help me. I flashed the JB version of twrp 2.5 instead of the 4.2 one and am getting a bootloop on the Asus screen. I reflash the update blob and it just doesn't boot
It IS Lupus said:
I'm having issues and this won't help me. I flashed the JB version of twrp 2.5 instead of the 4.2 one and am getting a bootloop on the Asus screen. I reflash the update blob and it just doesn't boot
Click to expand...
Click to collapse
search i have seen a guide for your specific issue on how to correct. it i was under q&a.
kaos420 said:
search i have seen a guide for your specific issue on how to correct. it i was under q&a.
Click to expand...
Click to collapse
I figured it out. I downgraded my bootloader back to 4.1(I know it went because I had the fastboot USB icon back) flashed the correct recovery and wiped everything. My data partition got corrupted. Got back into a working environment and flashed 4.2.1 again, with the proper recovery.
Sent from my HTC6435LVW using xda app-developers app
It IS Lupus said:
I figured it out. I downgraded my bootloader back to 4.1(I know it went because I had the fastboot USB icon back) flashed the correct recovery and wiped everything. My data partition got corrupted. Got back into a working environment and flashed 4.2.1 again, with the proper recovery.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
alternativly this should work as well for latest fw
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
(just for reference)
cheers
-Buster
Buster99 said:
alternativly this should work as well for latest fw
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
(just for reference)
cheers
-Buster
Click to expand...
Click to collapse
This is how I ended up fixing mine, can't thank you enough Buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Help please :crying: I just bricked my phone and I am not able to unbrick it . First , it requires you to install adb driver but I didn't not enable usb debugging before the brick . And I cannot flash the factory image . Any ideas how to unbrick without enabling usb debugging ?
ice051138 said:
Help please :crying: I just bricked my phone and I am not able to unbrick it . First , it requires you to install adb driver but I didn't not enable usb debugging before the brick . And I cannot flash the factory image . Any ideas how to unbrick without enabling usb debugging ?
Click to expand...
Click to collapse
What exactly did you do with the phone?
you don't need USB debugging to flash stock images. Your phone just need to be able to boot into fastboot and have the bootloader unlocked.
What happens when you press/hold power button for 20 seconds?
USB debugging is an ANDROID setting therefore only works or applicable when you are booted into Android
Sent from my Nexus 5 using Tapatalk
My phone is stuck at boot animation
I am in a dire need to your help. i just got my phone to stuck in the boot animation. This is what happened
i had a nexus 5 for 6 months, it was rooted and had xpose framework installed. Yesterday i updated my xpose app to the latest and installed an xpose module "Call blocker". but after one day use, i realized that it was making my nexus slow and i was suffering from low performance. So today i decided to uninstall this app, by going into settings>apps>call blocker and uninstalled it from there. Just after that i rebooted by phone, but it got into the boot loop (reboot after finishing the boot animation).
This is what is already tried:
I downloaded the nexus 5 image from google and extracted it. I flashed all the stock images (from bootloader) but now my phone is stuck at boot animation. i also installed CWM recovery and formatted system, data, cache and all options that were available, after that i flashed it again with stock images, but still stuck in the boot animation (circles keep on spinning forever).
Please guide me... I can't think of any more ways
rao_hamza said:
I am in a dire need to your help. i just got my phone to stuck in the boot animation. This is what happened
i had a nexus 5 for 6 months, it was rooted and had xpose framework installed. Yesterday i updated my xpose app to the latest and installed an xpose module "Call blocker". but after one day use, i realized that it was making my nexus slow and i was suffering from low performance. So today i decided to uninstall this app, by going into settings>apps>call blocker and uninstalled it from there. Just after that i rebooted by phone, but it got into the boot loop (reboot after finishing the boot animation).
This is what is already tried:
I downloaded the nexus 5 image from google and extracted it. I flashed all the stock images (from bootloader) but now my phone is stuck at boot animation. i also installed CWM recovery and formatted system, data, cache and all options that were available, after that i flashed it again with stock images, but still stuck in the boot animation (circles keep on spinning forever).
Please guide me... I can't think of any more ways
Click to expand...
Click to collapse
did you wipe data and cache with stock recovery after flashing?
rao_hamza said:
I am in a dire need to your help. i just got my phone to stuck in the boot animation. This is what happened
i had a nexus 5 for 6 months, it was rooted and had xpose framework installed. Yesterday i updated my xpose app to the latest and installed an xpose module "Call blocker". but after one day use, i realized that it was making my nexus slow and i was suffering from low performance. So today i decided to uninstall this app, by going into settings>apps>call blocker and uninstalled it from there. Just after that i rebooted by phone, but it got into the boot loop (reboot after finishing the boot animation).
This is what is already tried:
I downloaded the nexus 5 image from google and extracted it. I flashed all the stock images (from bootloader) but now my phone is stuck at boot animation. i also installed CWM recovery and formatted system, data, cache and all options that were available, after that i flashed it again with stock images, but still stuck in the boot animation (circles keep on spinning forever).
Please guide me... I can't think of any more ways
Click to expand...
Click to collapse
Are you sure you have flashed all the stock images? If so, then head to the stock recovery and perform a factory reset and then reboot. It should boot up.
- Sent from an IceCold Hammerhead!
rao_hamza said:
I am in a dire need to your help. i just got my phone to stuck in the boot animation. t(
Click to expand...
Click to collapse
I had this same issue the other day. First time was stuck at boot animation, second flashing of factory image saved my phone
Sent from my Nexus 5 using Tapatalk
Another newb that doesn't know the difference between fastboot and ADB, two of the MANY things you should be well-versed in before tinkering. Please head over the general forum and read the stickies.
samersh72 said:
did you wipe data and cache with stock recovery after flashing?
Click to expand...
Click to collapse
Thank you for all your support. I was able to restore my phone back to normal. What i did, after flashing the stock images, and I rebooted my phone to recovery and wiped the user data and cache. Although i tried if previously but i don't know why i didn't work than. May be, it only works just after the flashing of new/stock rom. Anyjow its good now. thank you for the support
Thumbs up XDA :good::laugh:
Hello, everyone.
So basically this is my issue. One day at work my Moto G restarted randomly and has been stuck in a bootloop ( boot animation cycles infinitely ).
I can access fastboot, booting to recovery freezes on TWRP logo.
My phone is rooted, unlocked and etc. I have tried flashing stock firmware, no changes, not even my custom boot logo and animation don't change.
I have tried using fastboot to erase everything and format but formatting fails saying this filesystem cannot be formatted.
I can access my files by booting into another recovery using fastboot boot recovery.img ( tried with PhilZ ) although it shows everything as it was before this all this ( all files gone, only directories left ).
I noticed that I could use ADB while stuck at TWRP logo. I tried pushing roms and using booted PhilZ to find them but they never appear, I can only push to /tmp, anything else doesn't exists although is shown through booted PhilZ.
I have tried using mkfs.ext4 to format my filesystem, everything went as it should but nothing changed.
TL;DR Bootloop, recovery does not open, fastboot flashing does nothing, adb push doesn't push anything
What the hell is going on with my phone? Any ideas people?
Somehow, your file system can't be accessed....was your phone encrypted?
itouchables said:
Somehow, your file system can't be accessed....was your phone encrypted?
Click to expand...
Click to collapse
It wasn't, I never encrypted it.
Also fastboot getvar all shows that my partition type is RAW.
Shouldn't it be F2FS or EXT4?
Maybe anyone has a proper partition mount point list for the Moto G?
I would try mkfs.ext4 formatting every possible mount point (cache,data,system and etc)
For example dev/block/mmcblk0p38
I found a Moto X mount point list but I have no clue if it's the same or not
Aequus.Mihi said:
Hello, everyone.
So basically this is my issue. One day at work my Moto G restarted randomly and has been stuck in a bootloop ( boot animation cycles infinitely ).
I can access fastboot, booting to recovery freezes on TWRP logo.
My phone is rooted, unlocked and etc. I have tried flashing stock firmware, no changes, not even my custom boot logo and animation don't change.
I have tried using fastboot to erase everything and format but formatting fails saying this filesystem cannot be formatted.
I can access my files by booting into another recovery using fastboot boot recovery.img ( tried with PhilZ ) although it shows everything as it was before this all this ( all files gone, only directories left ).
I noticed that I could use ADB while stuck at TWRP logo. I tried pushing roms and using booted PhilZ to find them but they never appear, I can only push to /tmp, anything else doesn't exists although is shown through booted PhilZ.
I have tried using mkfs.ext4 to format my filesystem, everything went as it should but nothing changed.
TL;DR Bootloop, recovery does not open, fastboot flashing does nothing, adb push doesn't push anything
What the hell is going on with my phone? Any ideas people?
Click to expand...
Click to collapse
Hi! did you find a solution?!
Oliverrlh said:
Hi! did you find a solution?!
Click to expand...
Click to collapse
No. Turns out my phone memory chip was corrupted due to flashing
Aequus.Mihi said:
No. Turns out my phone memory chip was corrupted due to flashing
Click to expand...
Click to collapse
I think I might have a similar situation. Can you give me an advice on how to confirm this?
The only difference in the circumstances is that my fiance's moto g has a custom recovery on it then she tired to install the 5.1 update. Then it would boot into the OS and after while would shut down then go to the recovery. I thought I had solved the issue by doing a factory reset. Everything was going fine until I turn it off. Now I get the boot animation and then a black screen. I can get the load screen on the custom recovery but that is it The computer can still recognize the phone.
Does this sound like your situation?
Icon000 said:
I think I might have a similar situation. Can you give me an advice on how to confirm this?
The only difference in the circumstances is that my fiance's moto g has a custom recovery on it then she tired to install the 5.1 update. Then it would boot into the OS and after while would shut down then go to the recovery. I thought I had solved the issue by doing a factory reset. Everything was going fine until I turn it off. Now I get the boot animation and then a black screen. I can get the load screen on the custom recovery but that is it The computer can still recognize the phone.
Does this sound like your situation?
Click to expand...
Click to collapse
That's the same situation I was in.
Even if you try to flash another ROM, it will never install.
You can't modify any files because the memory is ****ed.
I sold the phone for parts and bought a S4