hey , i just installed wrong rom in my moto G , i suppose to install xt1032 but i installed xt1033 and now my phone isn't booting , it's constantly showing me android logo for very long time. When i try to go back to recovery to install another rom , its just flashed teamwin recovey starting wallpaper and without entering in , it reboots into system.Since my system is not loading i am stucked between this. Please help me mymodel no is xt1032 motorola 8 GB
Hi,
Power down your phone and power up by pressing power and volume down buttons, you'll enter bootloader mode.
Connect the phone to your computer and flash again recovery with fastboot commands...
Let us know
You may need to use the following fastboot command:
fastboot erase userdata
Note: Internal storage will be wiped; photos, music etc get erased.
Related
Hello
I have a XT920 with root and this night I received an update for my XT920. After update my phone becames in loop while booting. I found a lot of threads about this problem because the phone was rooted. And to solve this problem the solution was flash another rom to the phone. I started the procedure below:
Fastboot flash boot boot-sign.img
Fastboot flash system system-sign.img
Fastboot flash recovery recovery-sign.img
Fastboot flash flex flex.img
When I executed the second command, I noticed that the first activity was erasing the partition. I wait about 20 minutes in this activity, but it doesn't finish. So I disconect the phone from the USB cable.
Now when I enter in the boot menu, no action works and the phone reboot. So I can't enter in recovery mode, fastboot mode and can't do a factory reset on the phone. All other the procedures (with fastboot, RSD NetConnected, RSD Lite) that I find in the forum needs the fastboot mode to recover thhe phone and flash the ROM again.
There is another way to save my phone? Can somebody help me?
Tks!
ps: sorry for my poor english.
Same Problem
I have the same problem,
The other day my WiFi Xoom stopped getting past the "Motorola Dual Core" screen.
I have removed the SD card.
Android recovery mode gives me the error android with the "!"
It does this plugged in or on battery.
Not rooted.
What else should I try?
neoka said:
The other day my WiFi Xoom stopped getting past the "Motorola Dual Core" screen.
I have removed the SD card.
Android recovery mode gives me the error android with the "!"
It does this plugged in or on battery.
Not rooted.
What else should I try?
Click to expand...
Click to collapse
What were you trying to do before this hapened? Need more info to be able to help.
24348542 26
DavilaDarkness said:
What were you trying to do before this hapened? Need more info to be able to help.
Click to expand...
Click to collapse
Hadn't really done anything. Just normal use. No out of the ordinary installs. Turned it off. Next day I tried turning it on and it won't boot.
Did you ever resolve this ?? I was give one to repair for a child and it too is stuck on the red boot screen. The good thing is the person who sold it to them was a hacker and put TWRP on it of all things. I was floored when I tried to enter recovery and found teamwin.
but the problem is its still stuck on the boot screen, i did flash it 3-4 times with M604 M602 flashes and some other customs but nothing works, it completes flashing and wiping caches but always goes back to stuck on boot screen..
perhaps I have to unclock the bootloader or something for the flash to be succesfull ?
Just wanted to say I fixed it with these commands and firmware if anyone is interested. I tried everything else including flashing with twrp and wiping all caches and it didn't work, getting the stock firmware and doing it like this worked to clear boot screen endless stuck
download fastboot and adb and xoom drivers 6.4 (about 5mb) and the appropriate stock firmware. for me it was ZM604
at the command type
adb reboot bootloader
you may need to unplug and replug cable after it goes in fastboot mode.
fastboot devices
.. should return something "02a439cj0skjdke fastboot" to proceed.
fastboot oem unlock
.. look at your tablet and follow the instructions, for me it was down twice and up once to accept unlock conditions, then it reboots
on reboot press vol down 2 seconds after you see moto logo, it will enter fastboot
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot erase userdata
fastboot reboot
no need to relock after, you will see android logo and first boot pop up after 2-3 mins
My problem:
I had a temporary CWM installed on my Asus Zenfone 2 ZE551ML 4gb/32GB and without thinking, installed an OTA update form 2.20.40.63 to 2.20.40.90.
My phone booted to the Asus logo with the loading circle and got no further.
Sadly I did not have USB debugging enabled at the time so I cant detect it in ADB in recovery mode to sideload.
I have tried to copy firmware to my Micro sd and load from there but my phone has never recognised or mounted SD cards so that is out of the question.
As a last resort I tried flashing the Boot.img, Recovery.img, droidboot.img and system.img, now it wont even get to the asus logo without coming up with and android logo with a red triangle above it, the same logo that comes up when I now try to enter recovery mode.
I have recorded a video of the process I followed to flash the zfone, but cant post it here as this is my first post, but I think I can send it to someone through messages
What am I doing wrong and how do I get my phone back?
Any help would be hugely appreciated, and keep in mind Im a bit of a noob so set by step instructions would be awesome, Thanks guys
Update: the original .img files i used were apparently already rooted, so I am now extracting the 2.20.40.90 firmware from the official Asus site and I will try to flash with those.
but I cant find the system.img inside the UL-Z00A-WW-2.20.40.90-user.zip and was wondering, do I need to take out the Boot.img. droidboot.img and recovery.img then turn all the existing files into a system.img?
Hi, thank you for using XDA Assist. Try asking in your device's specific forum here, http://forum.xda-developers.com/zenfone2 They are the experts on your device. I would start by posting in this thread, http://forum.xda-developers.com/zenfone2/help/help-post-questions-instead-making-t2997779
jd1639 said:
Hi, thank you for using XDA Assist. Try asking in your device's specific forum here, http://forum.xda-developers.com/zenfone2 They are the experts on your device. I would start by posting in this thread, http://forum.xda-developers.com/zenfone2/help/help-post-questions-instead-making-t2997779
Click to expand...
Click to collapse
Ahh thank you, sorry I didnt really know where to post the question
Fixed my phone!!
Ok guys, so I figured out what I was doing wrong.
I preformed the flash correctly with pre-rooted system.img, but I didnt wipe the cache, as soon as I did, my phone booted to a normal rooted device!!
If you want to do this yourself, download pre rooted versins of these files (easy to find with a quick google search)
Recovery.img
Boot.img
Droidboot.img
System.img
ADB tethered launcher (not needed if your phone can enter recovery mode)
and place them all in a new folder (lets call it zenUnbrick)
Boot your zenfone 2 into fast boot mode, then connect it to your pc
(Hold volume up button and power button, when your phone vibrates let go of the power button and continue to hold the volume + button until you see the fastboot screen)
Now hold down shift + right click inside the zenunbrick folder and select 'open command window here'
When that opens, run these commands in this order. Wait till each one finishes and be aware that the (fastboot flash system system.img) command takes quite a while to work its magic, so be patient and dont turn off your phone
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
when your phone reboots, it will most likely still seem bricked, but do not despair!! this is where you open up the ADB tethered launcher, although if your phone can enter recovery mode then you dont need this program
Option 1 - If your phone can enter recovery mode
Boot your phone into fastboot mode
use volume up and down to select recovery mode and use power button to select
wait for your phone to reboot
when you see the broken android symbol, press volume up button and power button simultaneously
select wipe cache and wait (it takes a while)
select reboot now
Your phone is now unbricked and rooted!!
Option 2 - If your phone cant enter recovery mode
Boot your phone into fastboot mode and connect it to your pc
open ADB tethered launcher
type 'ACCEPT'
when it loads type 'T4'
wait for your phone to reboot
select wipe cache and wait (it takes a while)
Select reboot now
Your phone is now unbricked and rooted!!
Hello Everyone
I use YU Yuphoria 5010 since more than a year with original cyanogenmod updated via updater to 12.1 without root and locked bootloader.
Since a month i have been facing force closure in many apps so i downloaded the cyanogenmod 12.1 reovery rom and did dirty flash via recovery solved settings app force closure but not all FC. Then I decided to clean flash a custom rom since cyanogenmod is closed now and also lineage and Yuos have no Volte support.
For this i read many posts forum properly unlocked my Yuphoria with Doomlord's method then rooted it and then flashed TWRP 3.0.0.0 on it and then did clean install of MIUI by Gaggu,and then Rohan successfully and used them but volte was not working. Then flashed stock rom by Yukick and everything (volte + vilte) was working fine exceptfor phone shutting down at 40% of battery.
Then decided for resurrection remix (5.8.1) and flashed it successfully. Tested it for three days some force closure were there also Vilte (not Volte) also not woking. Then saw a RR update (5.8.2) on resurrection remix download page for Yuphoria downloaded it and first time done a dirty flash (every previous flash was a clean flash this time I thought i am already on RR so no problem should be there).
There starts my problem the phone stuck at YU logo then tried to enter the Twrp recovery but could not. So flashed twrp via fastboot again and then wiped cache, delvik cache but no use could not start the phone. so tried to clean flash original cyanogenmod 12.1 rom ( that i used as for dirty flash many times to rectify some fc before) but could not.
Then read many threads on Yu forum and XDA forum and tried many things but no use.
Now the present condition is i can enter Fastboot mode by pressing vol up + power button with
cyanogen fastboot written on screen and can execute various fastoot commands but cannot flash rom as
Fastboot -i 0x2a96 flash system system.img
fail to write system.
I can't enter recovery with vol down + power button (after i entered the command Fastboot erase recovery previously i can enter the recovery by pressing vol down + power button, I did so to replace the TWRP with CWM recovery but no success) Phone starts YU logo appears for some time and then Blank screen.
But i can enter recovery via Fastboot with command
Fastboot -i 0x2a96 boot twrp_3.0.0.0_lettuce.img
but in twrp cannot mount system, data and cache partition tried various things like full wipe and repair file system change file system but no use. Twrp shows intenal storage 0 mb. also cannot flash other custom recovery if i try to flash other custom recovery via fastboot it says ok but cannot boot into recovery but when tried to enter via fastboot command phone enters in cyanogenmod recovery. it can also boot in recovery of Fastboot stock rom via fastboot command.
Fastboot -i 0x2a96 oem device-info
shows
device tampered false,
device unlocked true,
Charger screen enabled true.
I can lock the bootloader also by command
Fastbbot -i 0x2a96 oem lock
then device-info shows
device unlocked false
(without bootloader restart if restarted it shows device
unlocked true).
when enetered in TWRP 3.0.0.0 via fastboot command the phone is also shown as MTP device in Windows but only memory card is shown as storage no internal storage.
if i try to start the phone by pressing power button it stucks at YU logo.
if i connect the phone to computer while it is poweroff it is shown as Android Phone (Android
bootloader interface) in Device manager on my windows 7 laptop.
any other information or screen shot if needed I will provide.
Thanks in advance
For me also same error, possibly because of Flash memory life cycle end.
Hi There!
I'm exeriencing a wierd problem:
On my rooted Doogee S60, i was able to enter the built in recovery mode (and from there the fastboot mode) with Vol+ and Power.
Since i've installed a twrp recovery.img, pressing Vol+ and Power will launch the TWRP UI (wich i cant use, because my touchscreen is disabled).
Normal boot won't work eighter - i flashed a corrupted system.img file as it looks like (ooops). There is also the message at the Boot Screen saying:
"Orange State - Your device has been unlocked and can't be trusted. Your device will boot in 5 seconds"
... although these 5 seconds won't countdown and the device won't boot.
If i enter the TWRP, i can still access the ADB mode. So i can sideload stuff on the device, even the sd card is shown on pc. But the command
adb reboot fastloader
will reboot the phone, but not load the fastloader/fastboot - as it stucks at boot screen (orange state).
Any other ideas to access fastboot, due to flash the recovery.img again with the original to fix?
... or simple question: did i brick it?
thx in advance
Command
Code:
adb reboot fastloader
doesn't exist.
Look inside here:
How to Reboot Android Device into Fastboot or Recovery Mode via ADB « My Digital Life
If you’re using Android phones, tablets or devices, which is proliferating across all markets, prices and channels nowadays, then you may want to familiar yourself with fastboot or recovery mode, which is useful when you need to troubleshoot your beloved phone from the like of Samsung, HTC...
www.mydigitallife.net
introjoe said:
Hi There!
I'm exeriencing a wierd problem:
On my rooted Doogee S60, i was able to enter the built in recovery mode (and from there the fastboot mode) with Vol+ and Power.
Since i've installed a twrp recovery.img, pressing Vol+ and Power will launch the TWRP UI (wich i cant use, because my touchscreen is disabled).
Normal boot won't work eighter - i flashed a corrupted system.img file as it looks like (ooops). There is also the message at the Boot Screen saying:
"Orange State - Your device has been unlocked and can't be trusted. Your device will boot in 5 seconds"
... although these 5 seconds won't countdown and the device won't boot.
If i enter the TWRP, i can still access the ADB mode. So i can sideload stuff on the device, even the sd card is shown on pc. But the command
adb reboot fastloader
will reboot the phone, but not load the fastloader/fastboot - as it stucks at boot screen (orange state).
Any other ideas to access fastboot, due to flash the recovery.img again with the original to fix?
... or simple question: did i brick it?
thx in advance
Click to expand...
Click to collapse
Hi introjoe,
Are you doing? i have the doogee s60 but i just cant root it :'( can you tell me please how did you do it, or the files you use for it? i allready tried but, when i reset and enter fastboot mode, my pc simply dont recognize it.
I want to upgrade the android system to 9 or 10, thats why im doing all o this.
Thanks in advance.
@doryan666
i wasnt able to root the device in the end unfortunately.
i tried using an unofficial twrp, but i was stuck at the main boot screen
i t seems to need some bootloader-activation-code to enter the bootloader to install a new os.
the command line would look like
adb reboot bootloader "CODE"
the activation code has not been released yet by doogee ... and most probably never will be.
sorry to say but i dont think android upgrad will be possible with this device