Hello everyone i am new here..
my moto g stuck in bootloop
fastboot -recovery and facatory reset also not working..
how can i fix this ?
moto g single sim 8gb
4.4.2 kitkat version
please reply me soon... waiting....
What you did and why you got the boot loop?
Sent from my XT1032 using XDA Premium 4 mobile app
padhu1989 said:
What you did and why you got the boot loop?
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
may be after moto g update to kitkat version... i dont remember.....
last night my mobile switched off and morning i just put on charging... and bootloop starting......
my moto g is from UK tesco mobile. comes with jeally bean..
and i update OTA in india kitkat version...
I can't seem to get into the recovery menu!
When I boot into fastboot I can select ‘Recovery’.
so i have unlocked bootloader...
now...
It displays 'bootloader unlocked' warning, then screen goes blank for a few seconds.
Then 'bootloader unlocked warning' displays again and again.....
jayrocky11 said:
I can't seem to get into the recovery menu!
When I boot into fastboot I can select ‘Recovery’.
so i have unlocked bootloader...
now...
It displays 'bootloader unlocked' warning, then screen goes blank for a few seconds.
Then 'bootloader unlocked warning' displays again and again.....
Click to expand...
Click to collapse
same in here :crying:
jayrocky11 said:
I can't seem to get into the recovery menu!
When I boot into fastboot I can select ‘Recovery’.
so i have unlocked bootloader...
now...
It displays 'bootloader unlocked' warning, then screen goes blank for a few seconds.
Then 'bootloader unlocked warning' displays again and again.....
Click to expand...
Click to collapse
Are you sure you are using volume up button to select a choice.
Pressing power button just reboots, volume down navigates and volume up selects
I made that mistae quite a number of times!
---------- Post added at 10:22 PM ---------- Previous post was at 09:35 PM ----------
jayrocky11 said:
may be after moto g update to kitkat version... i dont remember.....
last night my mobile switched off and morning i just put on charging... and bootloop starting......
my moto g is from UK tesco mobile. comes with jeally bean..
and i update OTA in india kitkat version...
Click to expand...
Click to collapse
Did you try flashing your phone back to Stock from fastboot?
http://forum.xda-developers.com/showthread.php?t=2542219
deej_roamer said:
Are you sure you are using volume up button to select a choice.
Pressing power button just reboots, volume down navigates and volume up selects
I made that mistae quite a number of times!
---------- Post added at 10:22 PM ---------- Previous post was at 09:35 PM ----------
Did you try flashing your phone back to Stock from fastboot?
http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
yes i am using volume up to select.. but not working any factory - recovery.. same bootloop comming again....
now i am goin to flash phone..... downloading stock.....
For you to be able to update the firmware (-> Android) there must not be root or a custom recovery on the phone. Remove both, flash again. Otherwise the updater throws an error and the phone will always reboot.
cyrus_ae said:
For you to be able to update the firmware (-> Android) there must not be root or a custom recovery on the phone. Remove both, flash again. Otherwise the updater throws an error and the phone will always reboot.
Click to expand...
Click to collapse
hmmmm..okk
thanks
Related
I got my official OTA 5.0.2 Indian Version today. I updated it via OTA and now it's stuck at "No command." screen after the "Unlocked Bootloader" screen! Please help! -XT1033
skr975 said:
I got my official OTA 5.0.2 Indian Version today. I updated it via OTA and now it's stuck at "No command." screen after the "Unlocked Bootloader" screen! Please help! -XT1033
Click to expand...
Click to collapse
go to recovery and wipe and factory reset
woozie.2007 said:
go to recovery and wipe and factory reset
Click to expand...
Click to collapse
I am unable to access recovery.
skr975 said:
I am unable to access recovery.
Click to expand...
Click to collapse
when you are in fastboot mode, press recovery, then hold 3 sec the power button, then short press vol+
woozie.2007 said:
when you are in fastboot mode, press recovery, then hold 3 sec the power button, then short press vol+
Click to expand...
Click to collapse
It still says "No command." I am unable to access recovery and also cannot boot.
skr975 said:
It still says "No command." I am unable to access recovery and also cannot boot.
Click to expand...
Click to collapse
in fastboot mode can you go?
woozie.2007 said:
in fastboot mode can you go?
Click to expand...
Click to collapse
Yes
skr975 said:
Yes
Click to expand...
Click to collapse
ok, go to recovery now, when appear no command and the android is down, hold power button 2-3 sec, then press volume+
woozie.2007 said:
ok, go to recovery now, when appear no command and the android is down, hold power button 2-3 sec, then press volume+
Click to expand...
Click to collapse
It is stuck at the same screen. And when I hold the power button for 5-6 secs and then press vol+, it reboots and is stuck at the same screen again.
skr975 said:
It is stuck at the same screen. And when I hold the power button for 5-6 secs and then press vol+, it reboots and is stuck at the same screen again.
Click to expand...
Click to collapse
then try to flash the stock recovery again via fastboot, only recovery.img
woozie.2007 said:
then try to flash the stock recovery again via fastboot, only recovery.img
Click to expand...
Click to collapse
How do I do that? I have the OTA file too. I captured it after receiving the OTA.
skr975 said:
How do I do that? I have the OTA file too. I captured it after receiving the OTA.
Click to expand...
Click to collapse
you are in stock 4.4.4 with stock recovery? or custom recovery?
woozie.2007 said:
when you are in fastboot mode, press recovery, then hold 3 sec the power button, then short press vol+
Click to expand...
Click to collapse
Where do I find recovery.img?
woozie.2007 said:
you are in stock 4.4.4 with stock recovery? or custom recovery?
Click to expand...
Click to collapse
I was in 4.4.4 with custom recovery but I updated to 5.0.2 OTA. It got updated too
skr975 said:
Where do I find recovery.img?
Click to expand...
Click to collapse
in the stock firmware for your phone, download it and unzipped, then flash via fastboot only recovery
---------- Post added at 01:07 PM ---------- Previous post was at 01:06 PM ----------
skr975 said:
I was in 4.4.4 with custom recovery but I updated to 5.0.2 OTA. It got updated too
Click to expand...
Click to collapse
all threads here says the procedure, the ota update works only on stock rom, unrooted, and stock recovery
---------- Post added at 01:10 PM ---------- Previous post was at 01:07 PM ----------
look here for your firmware and folow the steps http://forum.xda-developers.com/showthread.php?t=2542219
Hi guys! Im on 4.4.4 with unlocked bootloader, the only way to root this device that i found on the internet is to use locked bootloader tutorials.
Is there any easy way to root unlocked bootloader D2303 on 4.4.4 18.3.1.C.1.15? I tried flashtool but when it installs towel root and i press make it rain! it says this device is not supported. Thanks in advance!
Here is one easiest way, but its over chinese app called KingRoot.
1. Download latest KingRoot.
2. Press Root button
3. Allow USB debug in Developer settings(Tap 10 times in Phone info on Build number to get Dev. settings)
4. Install Philz Recovery
5. Flash SuperSU V.249 BETA! Important!
6. Flash RICDefeat.zip
Same way is described here
http://forum.xda-developers.com/xperia-m2/general/how-to-permanently-root-xperia-m2-t3106534
But dont forget to flash SuperSU V2.49 BETA and RICDefeat & remove KingRoot apps.
Lothgar said:
Hi guys! Im on 4.4.4 with unlocked bootloader, the only way to root this device that i found on the internet is to use locked bootloader tutorials.
Is there any easy way to root unlocked bootloader D2303 on 4.4.4 18.3.1.C.1.15? I tried flashtool but when it installs towel root and i press make it rain! it says this device is not supported. Thanks in advance!
Click to expand...
Click to collapse
Update your bootloader using emma, then flash a recovery like CM12.1 Recovery from here: http://www.mediafire.com/download/lfub133wy5833bx/recovery.img and flash with it SuperSU zip and RICdefeat. Then you're done.
---------- Post added at 12:06 ---------- Previous post was at 12:05 ----------
Enycz11 said:
Here is one easiest way, but its over chinese app called KingRoot.
1. Download latest KingRoot.
2. Press Root button
3. Allow USB debug in Developer settings(Tap 10 times in Phone info on Build number to get Dev. settings)
4. Install Philz Recovery
5. Flash SuperSU V.249 BETA! Important!
6. Flash RICDefeat.zip
Same way is described here
http://forum.xda-developers.com/xperia-m2/general/how-to-permanently-root-xperia-m2-t3106534
But dont forget to flash SuperSU V.249 BETA and RICDefeat & remove KingRoot apps.
Click to expand...
Click to collapse
Actually that's a locked bootloader method.
And Kingroot also sends your IMEI info to chinese unknown servers...
linuxct said:
Update your bootloader using emma, then flash a recovery like CM12.1 Recovery from here: http://www.mediafire.com/download/lfub133wy5833bx/recovery.img and flash with it SuperSU zip and RICdefeat. Then you're done.
---------- Post added at 12:06 ---------- Previous post was at 12:05 ----------
Actually that's a locked bootloader method.
And Kingroot also sends your IMEI info to chinese unknown servers...
Click to expand...
Click to collapse
Thanks! Trying right now!
linuxct said:
Update your bootloader using emma, then flash a recovery like CM12.1 Recovery from here: http://www.mediafire.com/download/lfub133wy5833bx/recovery.img and flash with it SuperSU zip and RICdefeat. Then you're done.
---------- Post added at 12:06 ---------- Previous post was at 12:05 ----------
Actually that's a locked bootloader method.
And Kingroot also sends your IMEI info to chinese unknown servers...
Click to expand...
Click to collapse
Wait! How to flash recovery? Via flashtool by androxyde or emma?
EDIT: Tryed via fastboot the cm12 recovery, all what i got is grey screen with blue lines yey.
Lothgar said:
Wait! How to flash recovery? Via flashtool by androxyde or emma?
EDIT: Tryed via fastboot the cm12 recovery, all what i got is grey screen with blue lines yey.
Click to expand...
Click to collapse
But you have to do a fastboot flash recovery recovery.img . Did you do that ?
linuxct said:
But you have to do a fastboot flash recovery recovery.img . Did you do that ?
Click to expand...
Click to collapse
Yep.
Lothgar said:
Yep.
Click to expand...
Click to collapse
Then there's no reason to happen that. The lines appear when you boot it normally or when you try to enter recovery by keep holding the Vol- button?
In my D2303 is fine working...
linuxct said:
Then there's no reason to happen that. The lines appear when you boot it normally or when you try to enter recovery by keep holding the Vol- button?
In my D2303 is fine working...
Click to expand...
Click to collapse
The phone is off. I press the power button it vibrates, then for 5-6 second the screen is black. Then the lines shows up and no boot. Vol- pressed or not is the same.
EDIT: Reflashed now only if i try to enter recovery the lines shows up!
Lothgar said:
The phone is off. I press the power button it vibrates, then for 5-6 second the screen is black. Then the lines shows up and no boot. Vol- pressed or not is the same.
Click to expand...
Click to collapse
Go in fastboot mode and run fastboot erase recovery .
Again, I see no reason why this could be happening as this recovery runs in it's partition, isolated, so if you don't run it (Vol- button from the beggining) then it should not interfere with device boot up. Try flashing the latest kernel from the .15 ftf also.
linuxct said:
Go in fastboot mode and run fastboot erase recovery .
Again, I see no reason why this could be happening as this recovery runs in it's partition, isolated, so if you don't run it (Vol- button from the beggining) then it should not interfere with device boot up. Try flashing the latest kernel from the .15 ftf also.
Click to expand...
Click to collapse
I reflashed the recovery trough fastboot and now only if i try to boot recovery the blue lines shows up. I think that is a problem of the recovery.
Lothgar said:
I reflashed the recovery trough fastboot and now only if i try to boot recovery the blue lines shows up. I think that is a problem of the recovery.
Click to expand...
Click to collapse
Maybe is a screen driver problem, but on a D2303?? For me it's working
linuxct said:
Maybe is a screen driver problem, but on a D2303?? For me it's working
Click to expand...
Click to collapse
I remember that you gave me and alternative recovery for the locked bootloader becouse the standard doesn't working. Maybe the same issue?
Lothgar said:
I remember that you gave me and alternative recovery for the locked bootloader becouse the standard doesn't working. Maybe the same issue?
Click to expand...
Click to collapse
No, it shouldn't as the problem only was the GPIO Keys... Not screen driver problem... But yes, looks like you can't use the CM Recovery.
Format your fastboot partition with fastboot erase recovery and use the locked bootloader procedure... What a pity.
linuxct said:
No, it shouldn't as the problem only was the GPIO Keys... Not screen driver problem... But yes, looks like you can't use the CM Recovery.
Format your fastboot partition with fastboot erase recovery and use the locked bootloader procedure... What a pity.
Click to expand...
Click to collapse
I'll try but i dont know how to get the root because the procedure of downgrading the kernel doesn't work i tryed several times!
Here what i got:
Lothgar said:
I'll try but i dont know how to get the root because the procedure of downgrading the kernel doesn't work i tryed several times!
Here what i got:
Click to expand...
Click to collapse
But that pic is from CM recovery or from kernel downgrade?
And in what step you get stuck in the kernel downgrade root method?...
linuxct said:
But that pic is from CM recovery or from kernel downgrade?
And in what step you get stuck in the kernel downgrade root method?...
Click to expand...
Click to collapse
CM recovery. If i downgrade the kernel the adb doesn't start! And yes is enabled in the settings.
EDIT: Solved trying now for the locked bootloader method!
Installed philz recovery with locked bootloader method but i cant flash omnirom! (status 7)
Hi,
I want to install TWRP so I tried rebooting to bootloader by using adb, which didn't work, and I tried rebooting to the bootloader by rebooting to bootloader from recovery mode, which didn't work either, whenever I try it boots normally and just goes to my sim code screen. It's a G920F with stock firmware, my phone notified me of a software update is this the problem?
There's no "bootloader mode" on Samsung devices.
Hi,
There's no bootloader mode on Samsung, instead you get the Download screen. To get to it, just turn off your device, then turn it on using volume down+home+power buttons. You can then proceed to install TWRP using Odin through it.
All the best,
~Lord
Sent from my SM-G935F using Tapatalk Pro
WRONG
forumber2 said:
There's no "bootloader mode" on Samsung devices.
Click to expand...
Click to collapse
I have the same problem.. Cant root my phone because there is no bootloader to turn off... And yes when you go into original recoverymode there is a bootloader option... But it just don't work..
---------- Post added at 02:35 AM ---------- Previous post was at 02:33 AM ----------
There is a bootloader option in samsung recovery so you are wrong.. And yes it does not work....
I have the same problem..
i had the problem, when the cell, automatic restarted and it stuck on this screens, but it never came back, i already tried flashing the cellphone, and i already tried adding a custom bootloader, but no luck, it gave me the information that it mismatch, and attempts to enter the bootloader, without luck, i also already tried to only boot with fastboot, and no luck, it stucks on the twrp or m screen or shows different issues like screen fading or rumbling without reason, attempted to enter the recovery and only got to normal recovery from android, attempted to sideload the zip, and got a verification error, and it fails, again, i cant install a custom recovery, it always fails, and i dont know what to do... i really need help, any suggestion?? i already searched and didnt found any tools, flasher tool v.2 not found, and other tools are not able to help as well, help!!
edit, forgot to add, its an moto g. 2013 , xt1032 ANDROID LOLLIPOP
x-fighter said:
i had the problem, when the cell, automatic restarted and it stuck on this screens, but it never came back, i already tried flashing the cellphone, and i already tried adding a custom bootloader, but no luck, it gave me the information that it mismatch, and attempts to enter the bootloader, without luck, i also already tried to only boot with fastboot, and no luck, it stucks on the twrp or m screen or shows different issues like screen fading or rumbling without reason, attempted to enter the recovery and only got to normal recovery from android, attempted to sideload the zip, and got a verification error, and it fails, again, i cant install a custom recovery, it always fails, and i dont know what to do... i really need help, any suggestion?? i already searched and didnt found any tools, flasher tool v.2 not found, and other tools are not able to help as well, help!!
edit, forgot to add, its an moto g. 2013 , xt1032 ANDROID LOLLIPOP
Click to expand...
Click to collapse
which bootloader?
locked?
which firmware?
flashed how?
Sent from my PH-1 using XDA Labs
sd_shadow said:
which bootloader?
locked?
which firmware?
flashed how?
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
i am unable to use other than the normal bootloader, htt p://cdn.droidviews.com/wp-content/uploads/2014/02/moto-g-bootloader-mode.jpg but mine says unlocked code 3, i used fastboot to attempted to flash the phone, and nothing changed. it has the stock firmware lollipop 5.0.2, codename falcon, i flashed it with fastboot, but no luck, attempted to added by sideload on the android recovery default, and it gives me the errorhttp s://i.imgur.com/nSFMea9.jpg and i am unable to add any file, it doesnt has external sd
x-fighter said:
i am unable to use other than the normal bootloader, htt p://cdn.droidviews.com/wp-content/uploads/2014/02/moto-g-bootloader-mode.jpg but mine says unlocked code 3, i used fastboot to attempted to flash the phone, and nothing changed. it has the stock firmware lollipop 5.0.2, codename falcon, i flashed it with fastboot, but no luck, attempted to added by sideload on the android recovery default, and it gives me the errorhttp s://i.imgur.com/nSFMea9.jpg and i am unable to add any file, it doesnt has external sd
Click to expand...
Click to collapse
https://m.imgur.com/nSFMea9
http://cdn.droidviews.com/wp-content/uploads/2014/02/moto-g-bootloader-mode.jpg
Sent from my PH-1 using XDA Labs
---------- Post added at 01:48 PM ---------- Previous post was at 01:47 PM ----------
neither one of those says what files you are trying to flash
Sent from my PH-1 using XDA Labs
attached
Sent from my PH-1 using XDA Labs
x-fighter said:
i am unable to use other than the normal bootloader, htt p://cdn.droidviews.com/wp-content/uploads/2014/02/moto-g-bootloader-mode.jpg but mine says unlocked code 3, i used fastboot to attempted to flash the phone, and nothing changed. it has the stock firmware lollipop 5.0.2, codename falcon, i flashed it with fastboot, but no luck, attempted to added by sideload on the android recovery default, and it gives me the errorhttp s://i.imgur.com/nSFMea9.jpg and i am unable to add any file, it doesnt has external sd
Click to expand...
Click to collapse
From the picture you uploaded, says that your bootloader is locked, so that is why you can't flash any custom recovery. First you need to unlock your bootloader first but BACKUP FIRST, cause it will erase your internal storage when you unlock your bootloader. After unlocked, then you can flash custom recovery. Hope that helps.
Edit: but if your bootloader is really already unlocked, than try this, flashed twrp, then power down your phone by pressing the power button, then boot to twrp by press power button + volume down buttom. Don't reboot to twrp using the option im bootloader mode or using adb.
tepar said:
From the picture you uploaded, says that your bootloader is locked, so that is why you can't flash any custom recovery. First you need to unlock your bootloader first but BACKUP FIRST, cause it will erase your internal storage when you unlock your bootloader. After unlocked, then you can flash custom recovery. Hope that helps.
Edit: but if your bootloader is really already unlocked, than try this, flashed twrp, then power down your phone by pressing the power button, then boot to twrp by press power button + volume down buttom. Don't reboot to twrp using the option im bootloader mode or using adb.
Click to expand...
Click to collapse
i will upload a more reccent one, where i already unlocked it, but i will try whaat you edited, thank you!! let me try and post results
I was trying to flash a new LinageOS rom, but it didn't work properly. In one of my attempts to switch from the stock to the custom I formatted data in TWRP and seemingly destroyed the partition table. Now my phone is booted into the bootloader, but this bootloader is different from that one I had used to see earlier. More than that, it shows the "oem_locked" state, hovewer the bootloader was unlocked by me a month ago.
I downloaded the latest firmware for the RU region (RETRU), extracted the gpt file, but it can't be flashed due to the error, provided on the screenshot. The same error is actual for all firmware versions, available in the official firmware folder.
In such a way I can't flash gpt and the bootloader seems to be locked and non-unlockable. As far as I understand, the blankflash is a way out, but it is not available at the moment. Are there any other methods to restore the phone fucntionality?
I've seen this before let battery die and then it might come Back normal it's how others have fixed it
As far, as I have understood, I need a signed gpt.bin file. However, Motorola publishes non-signed firmware packages on its site(
I have no opportunity to bring phone back to service, maybe there is a way to get signed firmware files somehow?
kry52 said:
As far, as I have understood, I need a signed gpt.bin file. However, Motorola publishes non-signed firmware packages on its site(
I have no opportunity to bring phone back to service, maybe there is a way to get signed firmware files somehow?
Click to expand...
Click to collapse
Try the rescue option in
Moto Smart Assistant
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my perry_f using XDA Labs
sd_shadow said:
Try the rescue option in
Moto Smart Assistant
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my perry_f using XDA Labs
Click to expand...
Click to collapse
It doesn't detect the phone correctly, since the partition table is bricked. Followed advice from similar topics for other Moto phones and understood, that the inly way out is to wait for newer firmware versions (maybe, they will allow something new), or to wait for clean flash methods via EDL analogues...
Fix
If you anybody bump into the same problem, try to put the phone in blank mode:
Fastboot oem blankflash
Then use blankflash to fix the bootloader. After that, pick your stock firmware and reflash it.
whats a blank flash ans how is this used ot fix a soft brik.
mrk2815 said:
whats a blank flash ans how is this used ot fix a soft brik.
Click to expand...
Click to collapse
A Blankflash is special firmware used to boot device into bootloader so stock firmware can be flashed.
Sent from my mata using XDA Labs
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
See
https://forum.xda-developers.com/g7-power/how-to/guide-recovering-hard-brick-t3989753
Sent from my mata using XDA Labs
---------- Post added at 03:27 PM ---------- Previous post was at 03:17 PM ----------
If the bootloader is corrupted on a Qualcomm based device it may boot into
Emergency download mode (EDM)
Usually the device screen will be completely black
And when connected to a PC will show a
QHSUSB_Bulk or qloader
In device manager
To recover the device a
Blank Flash or
mmcblk0.img/loader.img
Is needed
Sent from my mata using XDA Labs
Haven't read all this so may not be helpful. Just saw "Soft Brick"
To restore to factory. Boot into Bootloader -
Then
Restore
If selecting Recovery Mode from within Bootloader (volume keys to move between, power button to select) returns
No Command
You have to press and hold the power button. Now press and release the volume up button but continue to hold power button
After this, you can see a list with option of Wipe data/ factory reset
bardell3600 said:
Haven't read all this so may not be helpful. Just saw "Soft Brick"
To restore to factory. Boot into Bootloader -
Then
Restore
If selecting Recovery Mode from within Bootloader (volume keys to move between, power button to select) returns
No Command
You have to press and hold the power button. Now press and release the volume up button but continue to hold power button
After this, you can see a list with option of Wipe data/ factory reset
Click to expand...
Click to collapse
It's a possible fix for stock nonroot device,
With stock recovery
But not helpful for custom rom issue s
Like this
Sent from my perry_f using XDA Labs
Thanks you
llskankzll said:
If you anybody bump into the same problem, try to put the phone in blank mode:
Fastboot oem blankflash
Then use blankflash to fix the bootloader. After that, pick your stock firmware and reflash it.
Click to expand...
Click to collapse
thank you very much thanks to what you sent I was able to repair my cel