Phone does not boot to ROM but only recovery. Must boot bootloader, "Normal Powerup" - Moto G Q&A, Help & Troubleshooting

Phone does not boot to ROM but only recovery. Must boot bootloader, "Normal Powerup"
My Moto G (2003) has TWRP. When I switch on the phone, it only boots into recovery TWRP 3.0.2.0, no matter what ROM I install.
However, when I boot the phone into bootloader mode and then select to do "Normal Powerup", the phone boots the installed ROM.
It is really strange.
Any hints on how to figure out what is happening? And how to fix?

Boot into TWRP. Then via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22​

lost101 said:
Boot into TWRP. Then via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22​
Click to expand...
Click to collapse
Thanks, this solved the problem.
Before, this partition had the strings
Code:
$ adb shell strings /dev/block/mmcblk0p30
boot-recovery
recovery
qe 1/1
Once the partition was cleared up (and stayed zeroed out), the phone would boot to the ROM.

lost101 said:
Boot into TWRP. Then via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22​
Click to expand...
Click to collapse
I have the same problem, but I got the error message:
Code:
dd: writing '/dev/block/platform/msm_sdcc.1/by-name/misc': No space left on device
When I tried to run the suggested soultion.
Any idea how to solve this?

rrd108 said:
I have the same problem, but I got the error message:
Code:
dd: writing '/dev/block/platform/msm_sdcc.1/by-name/misc': No space left on device
When I tried to run the suggested soultion.
Any idea how to solve this?
Click to expand...
Click to collapse
Yes, ignore the error message. The infinite number of zeroes from /dev/zero doesn't fit into the limited space of a partition, but when you get the message the partition is already filled.

Related

[Q] Can't install TWRP over CWM

Specs:
Tablet:
Asus TF300T running currently nothing previously CM10.2
Recovery: CWM 6.0.2.3
Computer
MacBook Pro running 10.9.1
I currently have CWM installed into the recovery portion and it is proving rather difficult to remove. I had TWRP flashed into recovery and had it working. I decided to get greedy and flash CM11 onto my tablet and TWRP kept coming back with error status 7. All the guides I had seen said to use CWM so I decided to give it a try. After finally sifting through the internet and finding the CWM that works on my tablet, CWM came back with errors saying "E: Can't mount /cache/recovery/command" along with a couple other commands. I am also unable to mount the /sdcard/ portion of my internal memory. I am now able to boot into the bootloader and use ADB to flash the recovery and it says it's successful but the tablet totally freezes up after the install and I have to hold the power button down just to shut it off. After rebooting the tablet and choosing recovery it boots into CWM. My final goal is just to get CM10.2 back onto my tablet along with TWRP.
Anyone have any ideas as to how to accomplish this?
harend said:
Specs:
Tablet:
Asus TF300T running currently nothing previously CM10.2
Recovery: CWM 6.0.2.3
Computer
MacBook Pro running 10.9.1
I currently have CWM installed into the recovery portion and it is proving rather difficult to remove. I had TWRP flashed into recovery and had it working. I decided to get greedy and flash CM11 onto my tablet and TWRP kept coming back with error status 7. All the guides I had seen said to use CWM so I decided to give it a try. After finally sifting through the internet and finding the CWM that works on my tablet, CWM came back with errors saying "E: Can't mount /cache/recovery/command" along with a couple other commands. I am also unable to mount the /sdcard/ portion of my internal memory. I am now able to boot into the bootloader and use ADB to flash the recovery and it says it's successful but the tablet totally freezes up after the install and I have to hold the power button down just to shut it off. After rebooting the tablet and choosing recovery it boots into CWM. My final goal is just to get CM10.2 back onto my tablet along with TWRP.
Anyone have any ideas as to how to accomplish this?
Click to expand...
Click to collapse
What bootloader are you on? CM11 requires either the touch CWM or TWRP 2.6.3.1 and both of those require a 4.2 bootloader that is not 10.6.1.8. You may have to upgrade by flashing the stock ROM first.
cmendonc2 said:
What bootloader are you on? CM11 requires either the touch CWM or TWRP 2.6.3.1 and both of those require a 4.2 bootloader that is not 10.6.1.8. You may have to upgrade by flashing the stock ROM first.
Click to expand...
Click to collapse
I had the stock 4.2 Asus ROM installed before I rooted my tablet. Right now I can't get cwm to even see the internal storage /sdcard/ along with many of the other spaces
harend said:
I had the stock 4.2 Asus ROM installed before I rooted my tablet. Right now I can't get cwm to even see the internal storage /sdcard/ along with many of the other spaces
Click to expand...
Click to collapse
When you start up the tablet and press Volume down to enter the fastboot menu, what is the version on the top left corner of the screen?
cmendonc2 said:
When you start up the tablet and press Volume down to enter the fastboot menu, what is the version on the top left corner of the screen?
Click to expand...
Click to collapse
Well for starters it says
Code:
Key driver not found.. Booting OS
but the next line says
Code:
Android cardhu-user bootloader <1.00e> released by "US_epad-10.6.1.27.5-20130902" A-03
So I would assume that I could install CM11 but I'm not exactly sure. Also from the bootloader menu I chose to boot android instead of recovery and it booted into CM10.2 so i guess that part of the problem is fixed but I would still like to be able to install CM11 on my device.
Thanks so far!
harend said:
Well for starters it says
Code:
Key driver not found.. Booting OS
but the next line says
Code:
Android cardhu-user bootloader <1.00e> released by "US_epad-10.6.1.27.5-20130902" A-03
So I would assume that I could install CM11 but I'm not exactly sure. Also from the bootloader menu I chose to boot android instead of recovery and it booted into CM10.2 so i guess that part of the problem is fixed but I would still like to be able to install CM11 on my device.
Thanks so far!
Click to expand...
Click to collapse
OK So you need to install TWRP 2.6.3.1
Follow this guide:
http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
After that CM11 should be working fine.
cmendonc2 said:
OK So you need to install TWRP 2.6.3.1
Follow this guide:
http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
After that CM11 should be working fine.
Click to expand...
Click to collapse
I still can't get TWRP to install. Here are the commands that I ran and the computer output
Code:
$./adb reboot bootloader
$./fastboot -i 0x0B05 flash recovery /Users/henry/Desktop/TWRP/TF300T_TWRP_2-6-3-1.zip
sending 'recovery' (7053 KB)...
OKAY [ 2.387s]
writing 'recovery'...
OKAY [ 2.436s]
finished. total time: 4.823s
$./fastboot reboot
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
rebooting...
ERROR: usb_write failed with status e00002ed
The terminal only threw the usb_write error after I manually restarted the tablet but it will just hang if I don't manually reboot it. It also automatically starts up in the CWM. Is there such a thing as blessing start up drives such as with Linux/Mac? Or did I flash the CWM to the boot partition by accident?
harend said:
I still can't get TWRP to install. Here are the commands that I ran and the computer output
Code:
$./adb reboot bootloader
$./fastboot -i 0x0B05 flash recovery /Users/henry/Desktop/TWRP/TF300T_TWRP_2-6-3-1.zip
sending 'recovery' (7053 KB)...
OKAY [ 2.387s]
writing 'recovery'...
OKAY [ 2.436s]
finished. total time: 4.823s
$./fastboot reboot
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
rebooting...
ERROR: usb_write failed with status e00002ed
The terminal only threw the usb_write error after I manually restarted the tablet but it will just hang if I don't manually reboot it. It also automatically starts up in the CWM. Is there such a thing as blessing start up drives such as with Linux/Mac? Or did I flash the CWM to the boot partition by accident?
Click to expand...
Click to collapse
Pretty sure you just flashed the wrong file?
Take the TWRP zip and extract the .img file. Then do:
Code:
$./fastboot -i 0x0B05 flash recovery /Users/henry/Desktop/TWRP/recovery.img
I hope you hadn't flashed a 4.1 recovery earlier....
cmendonc2 said:
Pretty sure you just flashed the wrong file?
Take the TWRP zip and extract the .img file. Then do:
Code:
$./fastboot -i 0x0B05 flash recovery /Users/henry/Desktop/TWRP/recovery.img
I hope you hadn't flashed a 4.1 recovery earlier....
Click to expand...
Click to collapse
I'm usually pretty careful to make sure that i'm only flashing recoveries for 4.2 or 4.3 specifically. I'm still stuck with CWM automatically booting and if I send the reboot to recovery command it is still going to CWM. Also I keep getting the could not clear input/output pipe errors.
harend said:
I'm usually pretty careful to make sure that i'm only flashing recoveries for 4.2 or 4.3 specifically. I'm still stuck with CWM automatically booting and if I send the reboot to recovery command it is still going to CWM. Also I keep getting the could not clear input/output pipe errors.
Click to expand...
Click to collapse
So when the tablet starts up, it goes directly to CWM or will it go to the fastboot menu after holding down VOL Down? Try running
Code:
fastboot devices
as soon as it gets into CWM
cmendonc2 said:
So when the tablet starts up, it goes directly to CWM or will it go to the fastboot menu after holding down VOL Down? Try running
Code:
fastboot devices
as soon as it gets into CWM
Click to expand...
Click to collapse
It will automatically go into CWM. the only way into the bootloader menu is if I send the command
Code:
./adb reboot bootloader
if I type the fastboot devices command nothing shows up and it just goes to the next line.
PC OS
harend said:
It will automatically go into CWM. the only way into the bootloader menu is if I send the command
Code:
./adb reboot bootloader
if I type the fastboot devices command nothing shows up and it just goes to the next line.
Click to expand...
Click to collapse
What is the OS of your PC????
lj50036 said:
What is the OS of your PC????
Click to expand...
Click to collapse
i'm on a mac running OSX 10.9.1

Moto G bricked?

Hey guys this is my first thread, I hope it's in the right section
Here's my problem:
Yesterday my Moto G 2013 with CM12.1 just froze (I could turn the screen on and off but that was it)
I tried opening the reboot menu, which worked, but it got stuck on "rebooting", so I just holded the power key until it turned off.
After that I got to the boot logo, but nothing happened from there, not even the boot animation showing up.
Next I tried to boot into TWRP, but it only got to the TWRP boot logo and nothing happened after that, so I flashed CWM, which I could access, but when trying to flash something it just doesn't progress. When I press "reboot to bootloader" on CWM it just freezes there aswell.
In another thread I read that flashing the gpt.bin should fix everything but it didn't help.
I don't really want to perform a factory reset, because of the data loss, but I think this would be my only option.
My question is:
How can I fix my phone (preferably without a factory reset), for example by getting TWRP to work again, because I have a Backup of my system and a zip of CM12.1 on it?
Btw another thing to mention is that when being in Recovery/System USB doesn't really work, but if my phone is turned off or in bootloader it works just fine.
Try "fastboot boot twrp.img" (or whatever the exact name of your TWRP image is). If it gets at least to the curtain screen, run "adb pull /tmp/recovery.log".
_that said:
Try "fastboot boot twrp.img" (or whatever the exact name of your TWRP image is). If it gets at least to the curtain screen, run "adb pull /tmp/recovery.log".
Click to expand...
Click to collapse
When I try "fastboot boot twrp.img" it reboots and get's stuck at the boot logo of android (Motorola logo) and I can hear the "Device disconnected" sound of windows.
But I flashed TWRP into recovery and it get's to the curtain screen. But it doesn't recognize my phone which might have to do with that as soon as it boots into a system USB just won't work
The following command will get TWRP working: fastboot erase userdata
lost101 said:
The following command will get TWRP working: fastboot erase userdata
Click to expand...
Click to collapse
But this will delete everything like my pictures folder, right? Isn't there a way to backup these files ?
@Ju43
adb pull /sdcard/ c:/motog_backup/​
lost101 said:
@Ju43
adb pull /sdcard/ c:/motog_backup/​
Click to expand...
Click to collapse
But adb only works in recovery mode in android, which I can't access right now without deleting everything, right ? And if I delete userdata, will my TWRP backup be deleted, too ? (It's just a backup of my system)
(sorry for asking so many questions, but I really don't wan't to lose all my photos and stuff)
Ju43 said:
But adb only works in recovery mode in android, which I can't access right now without deleting everything, right ? And if I delete userdata, will my TWRP backup be deleted, too ? (It's just a backup of my system)
(sorry for asking so many questions, but I really don't wan't to lose all my photos and stuff)
Click to expand...
Click to collapse
Yes, you do need at least access to recovery mode for adb to work. Try testing TWRP even if it is only partially loading. Also try CWM.
Everything will get erased on internal storage, photos, TWRP backup etc. Unfortunately, you may be left with no alternative.
lost101 said:
Yes, you do need at least access to recovery mode for adb to work. Try testing TWRP even if it is only partially loading. Also try CWM.
Everything will get erased on internal storage, photos, TWRP backup etc. Unfortunately, you may be left with no alternative.
Click to expand...
Click to collapse
Okay, thanks for your answer, but as I mentioned before, as soon as I boot into something like recovery or android, USB doesn't really work anymore (though it seemed to work again in android). Will erasing user data fix this (as it seems to be a software problem) or even better fixing it before erasing userdata, so I can backup my files? And if I erase user data and TWRP/CWM/whatever works, but USB won't then I can't really put a system on it, can I ?
Ju43 said:
Okay, thanks for your answer, but as I mentioned before, as soon as I boot into something like recovery or android, USB doesn't really work anymore (though it seemed to work again in android). Will erasing user data fix this (as it seems to be a software problem) or even better fixing it before erasing userdata, so I can backup my files? And if I erase user data and TWRP/CWM/whatever works, but USB won't then I can't really put a system on it, can I ?
Click to expand...
Click to collapse
Recovery mode ADB can take some effort to make work depending on the version of Windows. Since you obviously want to backup your files, you can try booting into Linux (a livecd will work) and installing adb. Linux adb works without the need for drivers so it may give you access.
If using Ubuntu, the command to install adb/fastboot is:
sudo apt-get install android-tools-adb android-tools-fastboot​
lost101 said:
Recovery mode ADB can take some effort to make work depending on the version of Windows. Since you obviously want to backup your files, you can try booting into Linux (a livecd will work) and installing adb. Linux adb works without the need for drivers so it may give you access.
If using Ubuntu, the command to install adb/fastboot is:
sudo apt-get install android-tools-adb android-tools-fastboot​
Click to expand...
Click to collapse
I see what you mean but I got adb to work most times when android was still working (just not in recovery) but I also had problems with charging when the phone was turned on, so I assume it's a problem with android, but I'll search for a Ubuntu Live CD that should be layng around somewhere here (lol) and I'll try it
@lost101
Ok, I installed adb and fastboot, but now it doesn't even find my phone in bootloader...
Ju43 said:
@lost101
Ok, I installed adb and fastboot, but now it doesn't even find my phone in bootloader...
Click to expand...
Click to collapse
Use: sudo fastboot devices
lost101 said:
Use: sudo fastboot devices
Click to expand...
Click to collapse
Thanks, I didn't think abut that :highfive: fastboot works now, but adb doesn't (again when using fastboot boot TWRP.img the terminal shows that it worked but the phone just reboots and is stuck on the Motorola logo and if I flash TWRP it doesn't work either). Maybe I should mention, that I have that screen flickering and like scanline thingy going on when I boot into recovery.
Ju43 said:
Thanks, I didn't think abut that :highfive: fastboot works now, but adb doesn't (again when using fastboot boot TWRP.img the terminal shows that it worked but the phone just reboots and is stuck on the Motorola logo and if I flash TWRP it doesn't work either). Maybe I should mention, that I have that screen flickering and like scanline thingy going on when I boot into recovery.
Click to expand...
Click to collapse
Can you fastboot boot TWRP.img, then adb pull /sdcard/ ?
lost101 said:
Can you fastboot boot TWRP.img, then adb pull /sdcard/ ?
Click to expand...
Click to collapse
Nope, because as I mentioned it doesn't get to the TWRP logo at all
Ju43 said:
Nope, because as I mentioned it doesn't get to the TWRP logo at all
Click to expand...
Click to collapse
Try CWM.
lost101 said:
Try CWM.
Click to expand...
Click to collapse
Same thing except it started vibratng and didn't stop until restarting after a few seconds 0.o
Ju43 said:
Same thing except it started vibratng and didn't stop until restarting after a few seconds 0.o
Click to expand...
Click to collapse
Maybe you can get the phone booting into Android by fastboot flashing the system.sparsechunks from the Factory Firmware Image for your phone.
lost101 said:
Maybe you can get the phone booting into Android by fastboot flashing the system.sparsechunks from the Factory Firmware Image for your phone.
Click to expand...
Click to collapse
Downloading it right now, could you please exactly tell me what to flash with which command ?

nexus 5 softbrick

Hey,
Hopefully you guys can give me some help with the problem ive been having,
My nexus 5 is stuck in bootloop, i can get into the bootloader and the lockstate is unlocked but no custom recovery is appearing like it used to. I tried flashing using ADB but my phone doesn't show up as a device on my pc.
i have tried to wipe the cache ect and it comes up with "E:failed to mount /cache (invalid argument)
I only really know the basics of this stuff (only ever used the basic stuff to root and flash my phone)
You must use fastboot commands while being into the bootloader, not adb.
mworley1991 said:
Hey,
Hopefully you guys can give me some help with the problem ive been having,
My nexus 5 is stuck in bootloop, i can get into the bootloader and the lockstate is unlocked but no custom recovery is appearing like it used to. I tried flashing using ADB but my phone doesn't show up as a device on my pc.
i have tried to wipe the cache ect and it comes up with "E:failed to mount /cache (invalid argument)
I only really know the basics of this stuff (only ever used the basic stuff to root and flash my phone)
Click to expand...
Click to collapse
Yeah, exactly what primokorn says...
Primokorn said:
You must use fastboot commands while being into the bootloader, not adb.
Click to expand...
Click to collapse
If you use the command "fastboot devices" and your phone with a code appears in the command prompt then there's no problem with your drivers.
Just reflash the factory image, you can use the automatic process if you run "flash all". You can also flash the images manually but if you go for that option make sure you don't forget to flash the cache image, that will fix your problem with mounting the cache partition.
ADB commands are used when the phone is booted into the ROM.
Flash the latest stock ROM from here to see if it solves the issue: https://developers.google.com/android/nexus/images
If the phone still bootloops, flash the userdata.img in fastboot. After flashing the userdata.img file in fastboot, boot directly into stock recovery using the power/volume buttons, perform a factory wipe, and reboot.

Internal storage 0 mb twrp (Nexus 5 softbricked)?

So I totally messed up my phone. When booting it, CM logo will take forever to disappear. Hopefully I can go to bootloader. I have installed latest version of TWRP. TWRP logo stays up for about 5 minutes then it loads the main menu.
It shows internal storage o mb. If I flash custom rom or firmware, it shows unable to mount /data, /persist, /cache. Even I couldn't unmount the partition through ADB Shell as it shows error "device or resource is busy". What is the solution for this? I badly want my phone back. Even I think I lost all my important data. Please help me to solve this. What could be the actual solution? And I am a noob. So if you instruct me with a solution, be descriptive. Thank you.
Can you get in fastboot mode? If so install the latest factory image.
rdmunn said:
Can you get in fastboot mode? If so install the latest factory image.
Click to expand...
Click to collapse
I tried but device will not mount /data. So flashing fails
hiren43 said:
I tried but device will not mount /data. So flashing fails
Click to expand...
Click to collapse
Try this fastboot command:
Code:
fastboot erase data
fastboot erase cache

No OS, internal storage 0 Mb

Sorry for my English... I have a problem with my moto g XT1032 with bootloader unlocked and version recovery latest TWRP, I rooted and was running CM13, until I began to present faults so I decided to restart the phone, from that the phone turned on in recovery mode and when I check if everything is fine, says I have no OS installed, I review the status of the internal storage (all this is from the recovery TWRP) it says it is 0mb,i tried to flash from the bootloader the original firmware and all commands says FAILED when it's gonna write it (failed to erase partition). Anyone who has had this problem before and have fixed or knows how to fix it?
Try this tool: http://forum.xda-developers.com/moto-g/general/gpe-lollipop-5-1-1click-installer-t3075522 .
Via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22​
lost101 said:
Via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22​
Click to expand...
Click to collapse
I try to do it but it says
dd: writing '/dev/block/platform/msm_sdcc.1/by-name/misc': No space left on device
:crying::crying::crying:
Maybe try:
adb shell
cd /dev/block/platform/msm_sdcc.1/by-name
dd if=/dev/zero of=./misc​
lost101 said:
Maybe try:
adb shell
cd /dev/block/platform/msm_sdcc.1/by-name
dd if=/dev/zero of=./misc​
Click to expand...
Click to collapse
Sorry for hijacking the thread but i am afraid that I am with similar problem, when using my G its just rebooted and after that the battery drop to 20% (previous 76%) and a lot of files disappear, like amnesia any idea why?
BryanByteZ said:
Sorry for hijacking the thread but i am afraid that I am with similar problem, when using my G its just rebooted and after that the battery drop to 20% (previous 76%) and a lot of files disappear, like amnesia any idea why?
Click to expand...
Click to collapse
Sounds like classic 'emmc corruption' symptomatology. Fastboot flash the latest factory firmware image for your model. However it may well be game over for your handset.
lost101 said:
Sounds like classic 'emmc corruption' symptomatology. Fastboot flash the latest factory firmware image for your model. However it may well be game over for your handset.
Click to expand...
Click to collapse
Oh sh**, okay thanks for the info!
when I flashed falcon_502_partitions_nomodem.zip on my moto g XT1028 and then I reboot to bootloader nothing is there and when I tried to restart my devices the screen is black and the fastboot mode is also not visible and I'm not able to flash anything to make my device work.
Aditya2512 said:
when I flashed falcon_502_partitions_nomodem.zip on my moto g XT1028 and then I reboot to bootloader nothing is there and when I tried to restart my devices the screen is black and the fastboot mode is also not visible and I'm not able to flash anything to make my device work.
Click to expand...
Click to collapse
Post here and only here: http://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788
If your model is not supported, then you may never be able to resolve the situation.
Solved
I faced the sane problem with my moto g3. actually after booting it into recovery it went to loop of recovery and off.
Then downgraded twrp to 3.0.2 using fastboot from pc.
Then it booted into recovery but was showing 0mb internal storage.Lastly i used format data under wipe in twrp then it got back to normal.

Categories

Resources