Hi all iv have issues with my moto g I cant get any ROM or firmware to boot up then noticed this error in the pic below, how can I fix it and is this why I can't flash roms etc I was on rooted stock UK now I'm stuck with just recovery mode etc
Sent from my Nexus 4 using xda app-developers app
brewy said:
Hi all iv have issues with my moto g I cant get any ROM or firmware to boot up then noticed this error in the pic below, how can I fix it and is this why I can't flash roms etc I was on rooted stock UK now I'm stuck with just recovery mode etc
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Well, I can't see your posted pic but I recommend you to flash a stock UK firmware on your phone through fastboot. You can try any other option too but fastboot would be the best one to resolve your problem without much hassle.
forgotter said:
Well, I can't see your posted pic but I recommend you to flash a stock UK firmware on your phone through fastboot. You can try any other option too but fastboot would be the best one to resolve your problem without much hassle.
Click to expand...
Click to collapse
The error says fail to find path (sd-ext) I'll try fastboot later on I'm just curious as how this error came up after doing the normal wipes I don't no if its recovery related or not but it won't boot any rom or stock roms
Sent from my Nexus 4 using xda app-developers app
@brewy : As long you as you are on moto g, you'll never be able to mount /sd-ext (as moto g only has /data).Since moto g doesn't has a sdcard, there can't be a sd-ext partition. So here ends your curiosity. Lol.
I guess you have CWM as recovery. I recommend you to install TWRP.2.7.0.0.falcon by dhacker.(It had no issue).
And what about your phone. Is it working fine now?
@brewy : As long you as you are on moto g, you'll never be able to mount /sd-ext (as moto g only has /data).Since moto g doesn't has a sdcard, there can't be a sd-ext partition. So here ends your curiosity. Lol.
I guess you have CWM as recovery. I recommend you to install TWRP.2.7.0.0.falcon by dhacker.(It had no issue).
And what about your phone. Is it working fine now?
Click to expand...
Click to collapse
Phew I thought my phone had an error stopping it boot, yep I'm using philz cwm because iv found out twrp changes my F2fs to ext4 after doing the three wipes which I don't want period I have to mfastboot my G later today when I get some time I could of did it early but my laptop was missing some dll files which is now solved
Sent from my Nexus 4 using xda app-developers app
Nope, TWRP doesn't changes your partition from f2fs to ext4. I made a backup of my phone a day earlier and have data.f2fs.win as one of backup files and system will always be ext4 irrespective of which recovery you are on.
I encountered some problems with philz cwm so I moved on to TWRP. It's your choice to choose what you would like to have. Nevertheless, I'd still say to give a try to latest TWRP.
My good wishes for your phone. Hope it will get alive by today.:good:
forgotter said:
Nope, TWRP doesn't changes your partition from f2fs to ext4. I made a backup of my phone a day earlier and have data.f2fs.win as one of backup files and system will always be ext4 irrespective of which recovery you are on.
I encountered some problems with philz cwm so I moved on to TWRP. It's your choice to choose what you would like to have. Nevertheless, I'd still say to give a try to latest TWRP.
My good wishes for your phone. Hope it will get alive by today.:good:
Click to expand...
Click to collapse
Well fixed my G as you can see I'm using with mfastboot now back to rooted stock with twrp none of cwm would stick but at least I got my pride and joy back that's all that matters for now
Sent from my XT1032 using xda premium
Related
Hey guys..
I just today rooted my lovely Nexus S, 9023 or what its called (non branded or nothing)
But i cant load recovery.. went fine when i rooted it, but now that i want to load an custom rom it fails.. i followed this guide to root: http://forum.xda-developers.com/showthread.php?t=883032
Anyone have some ideas??
I just get a android logo and triangle + ! in it.. as error.. (
Best regrads
n0ta
Just tested with ROM Mananger, it can backup just fine.. as soon i choose a ROM to install it loads recovery and fails, just like when you do it manually.
n0ta said:
Just tested with ROM Mananger, it can backup just fine.. as soon i choose a ROM to install it loads recovery and fails, just like when you do it manually.
Click to expand...
Click to collapse
Sounds like stock recovery installed itself. If you are rooted remove/rename /etc/install-recovery.sh then reflash cwm manually or through rom manager.
Sent from my Nexus S 4G using XDA Premium App
I have had this happen on my NS4G. I know they are a little different, but it seems like you are having the same thing happen that I did and to solve it, I open Windows command prompt(or terminal depending on you OS) and fastboot flash recovery (insert recovery.img name here) and reflashed the recovery partition with clockwork. Very easy fix. Just make sure you boot straight into recovery after flashing and flash the Rom you want to flash before booting back into stock(also make a nandroid before that). After that you shouldn't have any more problems unless you unroot. There must be a small glitch somewhere when flashing the clockwork doesn't fully erase stock recovery partition.
krohnjw said:
Sounds like stock recovery installed itself. If you are rooted remove/rename /etc/install-recovery.sh then reflash cwm manually or through rom manager.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
Works now thanks all to both of you.
n0ta said:
Works now thanks all to both of you.
Click to expand...
Click to collapse
Pretty common lately...Android for Nexus S recovers its recovery if it is changes...
"You dawg, we heard you like recovering your recoveries, so we made recovery recover in recovery." and all that...
bender_123 said:
Pretty common lately...Android for Nexus S recovers its recovery if it is changes...
"You dawg, we heard you like recovering your recoveries, so we made recovery recover in recovery." and all that...
Click to expand...
Click to collapse
The Nexus one did the same thing. Most OTAs verify / replace this file. It's easy enough to deal with if you're unlocked and rooted.
Sent from my Nexus S 4G using XDA Premium App
This is about the third or fourth time this question has come up over the past week...
bender_123 said:
This is about the third or fourth time this question has come up over the past week...
Click to expand...
Click to collapse
I assure you it won't be the last.
Sent from my Nexus S 4G using XDA Premium App
[Recovery][Unofficial]TWRP 2.7.0.0 & Clockwork Recovery Touch 6.0.4.4 W/loki (D800)
Clockwork recovery touch with Loki for AT&T LG G2 (D800) Only.
TWRP recovery touch with Loki for AT&T LG G2 (D800) Only.
The only difference between official recoveries and this version is that Loki is built in to recovery.
THIS IS ONLY FOR 10d FIRMWARE. IF YOU ARE ON 10o THEN DO NOT USE!!!
You may want to flash 10d firmware. It can be found HERE with instructions. If you plan on using ROMs it is best to flash 10d firmware first.
Install Methods
Flashable Zip - Must have TWRP or whatever custom recovery already installed.
Boot into recovery and flash Recovery Zip file.
Manual Method - With no custom recovery already installed.
Must have Root first. Check HERE for root
Download the zip file to which recovery you want
Extract zip file to C:\
Open command prompt in root of C drive
You will need adb installed and properly setup in your environment variables. If not place the recovery.img wherever your adb file is located.
Type the following commands:
Code:
adb push recovery.img /data/local/tmp/recovery.img
adb shell
su
cd /data/local/tmp
dd if=/data/local/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
exit
adb reboot recovery
Now you should be in recovery.
Downloads
TWRP 2.7.0.0 with Loki
File Name openrecovery-twrp-2.7.0.0-d800-loki.zip
MD5 f640c221e4a6c575b375094f765d63ba
Clockwork Recovery Touch 6.0.4.4 with Loki
File Name recovery-clockwork-touch-6.0.4.4-d800-loki.zip
MD5 d50fbe2e026463e5df698f0b8b0a4d91
Download HERE
Mirror - Goo.im
Enjoy!
Web Presence:
Twitter
Google+
Credits
TWRP team for great recovery
Koush for original clockwork recovery
djrbliss for Loki
manojsuper said:
Does everything worked.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Everything I have tested so far.
Can I flash using flashify?
Sent from my LG-D802 using XDA Premium 4 mobile app
holeshot77 said:
Can I flash using flashify?
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have not tested that way but I am sure you can. If you just need the img file than extract from zip file.
If you try then let us know how it worked out
Using flashify works like a charm. Just extract img file and flash using flashify. As a third alternative.
Sent from my LG-D802 using XDA Premium 4 mobile app
I haven't used cwm since the days of the vibrant but ,my question is does this recovery speed up flashing a rom? It takes me less then a minute to flash a rom on the nexus 4 so I was just curious. Thanks.
Sent from my Nexus 7 2013 using XDA Premium 4 mobile app
ManOnTheMoon said:
I haven't used cwm since the days of the vibrant but ,my question is does this recovery speed up flashing a rom? It takes me less then a minute to flash a rom on the nexus 4 so I was just curious. Thanks.
Sent from my Nexus 7 2013 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you been flashing OEM modified ROMs on G2 the speed may have been due to the size of the ROMs.
AndroidUser00110001 said:
If you been flashing OEM modified ROMs on G2 the speed may have been due to the size of the ROMs.
Click to expand...
Click to collapse
Sorry I meant to include CM/AOSP based roms. The days of flashing 250mb+ roms are over :good:
I also havent used CWM in a long time now, are there any real differences between this and TWRP besides layout? Any special features unique to CWM?
EniGmA1987 said:
I also havent used CWM in a long time now, are there any real differences between this and TWRP besides layout? Any special features unique to CWM?
Click to expand...
Click to collapse
They all do the same so people will use what they prefer...
Will I lose my twrp backups if I flash this clockwork recovery?
If not, then would I be able to restore twrp backups with cwm? May be a silly question but I never tried this and worried about losing backups.
You will not lose them until you delete them but I am not sure if you can restore twrp backups with clockwork.
SysAdmNj said:
Will I lose my twrp backups if I flash this clockwork recovery?
If not, then would I be able to restore twrp backups with cwm? May be a silly question but I never tried this and worried about losing backups.
Click to expand...
Click to collapse
Sent from my LG-D800 using XDA Premium 4 mobile app
Thanks for this! Always good to see people doing stuff on this phone : )
Flashing was a breeze. Thanks.
Does this mount usb-otg? When I try "Mount USB Storage" nothing happens. I am pretty sure TWRP also does not yet support usb-otg. My hopes were CWM did.
Thanks
Adb side load is an alternative for Mount usb. Install Zip --> Install from adb sideload. Unfortunately this didn't work for me either. If it works for any of you guys please let me know the steps you followed. Sideload doesn't work in TWRP also.
In case of a soft brick either Mount usb or adb side load should help. Otherwise you have to go back to stock using Lg tools and start all over again.
varunkumars said:
Adb side load is an alternative for Mount usb. Install Zip --> Install from adb sideload. Unfortunately this didn't work for me either. If it works for any of you guys please let me know the steps you followed. Sideload doesn't work in TWRP also.
In case of a soft brick either Mount usb or adb side load should help. Otherwise you have to go back to stock using Lg tools and start all over again.
Click to expand...
Click to collapse
Thanks for the reply. I will be a happy camper when we get real usb-otg support from both recoveries
Format Cache is not working
Hey guys,
I flashed this and seem to have a problem with formatting the cache- it just stops so I cannot wipe becuase it stops at formatting cache. Anybody else experienced this before? I flashed again with same results.
thanks,
AC
aaronc_98 said:
Hey guys,
I flashed this and seem to have a problem with formatting the cache- it just stops so I cannot wipe becuase it stops at formatting cache. Anybody else experienced this before? I flashed again with same results.
thanks,
AC
Click to expand...
Click to collapse
Just let it finish, it takes a long time. I thought the same and then it finished up.
Worked like a charm. Thanks!
Sent from my LG-D800 using Tapatalk
Is wiping always going to take this long?
Sent from my LG-D800 using Tapatalk
I've flashed "CWM-based Recovery v6.0.4.6" which was in the rooting guide.
I'm not very happy with it though:
- backups are placed in /data/media/clockworkmod instead of /sdcard/clockworkmod , even though it says "Backup to /sdcard"
- tgz backup does not work, backups are still tars
- after choosing "Reboot" the recovery asks to fix root access, even though it's perfectly fine. Minor annoyance, but still ..
So, which is the best custom recovery at this point for the Moto G?
I really want compressed backups (bz2 if possible) AND I want the backups stored on the virtual sdcard for easy copying.
You can try twrp
Sent from my XT1033 using Tapatalk
Try them all, to see which you prefer, they only take a second to flash,
Personally I use phillz touch recovery,
Sent from my Moto G using xda app-developers app
i use trwp because cwrm philz is bugged in motorola moto g, htc desire 500 and many other phones. who says this is not true, try to restore defaults from settings menu and will try this problem!!!!
plewis1981 said:
Try them all, to see which you prefer, they only take a second to flash,
Personally I use phillz touch recovery,
Sent from my Moto G using xda app-developers app
Click to expand...
Click to collapse
I've installed Philz. Everything I tried works fine, backing up and saving settings.
What exactly are the known bugs for Philz for Moto G?
Can it flash zips and restore backups? If so, it's alright for me.
Sent from my XT1032 using xda app-developers app
I prefer twrp since it's the only one I'm familar with.
phil GUI looks the best
Hello,
I just rooted my Moto G (CWM on it), but when I flashed a rom, is got stuck on the bootlogo.
I installed a newer version of CWM, and flashed a rom again, still stuck, and the newer version of CWM can't see my backup..
What now? please help me...
FearsomeStatue0 said:
Hello,
I just rooted my Moto G (CWM on it), but when I flashed a rom, is got stuck on the bootlogo.
I installed a newer version of CWM, and flashed a rom again, still stuck, and the newer version of CWM can't see my backup..
What now? please help me...
Click to expand...
Click to collapse
Question 1: before you flashed the rom, what wipe options did you select?
Question 2: can u get into the bootloader?
I wiped cache and dalvik. (and I did factory reset to)
and yes, I can even start CWM, but I can't find my backup
FearsomeStatue0 said:
I wiped cache and dalvik. (and I did factory reset to)
and yes, I can even start CWM, but I can't find my backup
Click to expand...
Click to collapse
So it's not in a bootloop anymore? I use TWRP not CWM but I wouldn't think that updating versions would change the source destination path of the backup. Sidenote: after I rooted and backedup my G for the first time, the auto generated name (which was that time/date stamp) had a weird date of sometime in the 1970's and I wasn't able to use that backup because it didn't backup the /system data for some reason. I could still see the backup tho, just not use it
3RAN7ON said:
So it's not in a bootloop anymore? I use TWRP not CWM but I wouldn't think that updating versions would change the source destination path of the backup.
Click to expand...
Click to collapse
Nope, no bootloop, I hold the powerbutton for 5 seconds. But that I can't find my backups is the real problem, I really can't find my backup anywhere (I can use a filemanager in CWM)
FearsomeStatue0 said:
Nope, no bootloop, I hold the powerbutton for 5 seconds. But that I can't find my backups is the real problem, I really can't find my backup anywhere (I can use a filemanager in CWM)
Click to expand...
Click to collapse
I can't say where the backup went but if u freshly unlocked and rooted it before backing up, there can't be that much data lost! You would need to just reflash the stock firmware and backup if that is your intent; to have a stock backup :laugh: and I'm happy it's no longer in a bootloop. I would suggest going forward to save nandroid backups to usb-otg storage device so it can't be wiped from the phone.
I flashed the stock rom with this guide (http://forum.xda-developers.com/showthread.php?t=2542219) but I am still stuck in bootscreen..
So flashing roms doesn't go well.. What now? (thanks for helping!)
And now my phone can't even see my internal storage anymore...
FearsomeStatue0 said:
And now my phone can't even see my internal storage anymore...
Click to expand...
Click to collapse
Search mfastboot on here it will fix your phone
http://forum.xda-developers.com/showpost.php?p=47820707
Sent from my Moto G using xda premium
factory reset will format /sdcard or not?
Sent from my XT1033 using XDA Free mobile app
thestory101 said:
factory reset will format /sdcard or not?
Sent from my XT1033 using XDA Free mobile app
Click to expand...
Click to collapse
Mfastboot wipes everything
Sent from my Moto G using xda premium
brewy said:
Mfastboot wipes everything
Sent from my Moto G using xda premium
Click to expand...
Click to collapse
I faced a similar issue and i have found a answer another user gave me after countless "did you wipe this/ DID YOU WIPE THAT? responses"
what i did was i downgraded to JB 4.3 img ad once i flashed that and it booted up and flashed the philz edition cwm and then i was able to insatll a custom rom.
before this i was on stck 4.4.2 and NO custom rom booted past bootlogo until this solution.
btw i donwgraded to 4.3 in fastboot and flashed custom rom in cmw.
chairsz said:
I faced a similar issue and i have found a answer another user gave me after countless "did you wipe this/ DID YOU WIPE THAT? responses"
what i did was i downgraded to JB 4.3 img ad once i flashed that and it booted up and flashed the philz edition cwm and then i was able to insatll a custom rom.
before this i was on stck 4.4.2 and NO custom rom booted past bootlogo until this solution.
btw i donwgraded to 4.3 in fastboot and flashed custom rom in cmw.
Click to expand...
Click to collapse
When you downgraded to JB did you also wipe the internal SD or did you just flash system and kernel via fastboot?
Inviato dal mio Moto G utilizzando Tapatalk
Bert98 said:
When you downgraded to JB did you also wipe the internal SD or did you just flash system and kernel via fastboot?
Inviato dal mio Moto G utilizzando Tapatalk
Click to expand...
Click to collapse
i erased everything
chairsz said:
i erased everything
Click to expand...
Click to collapse
Aw crap thanks
Inviato dal mio Moto G utilizzando Tapatalk
I'm making this thread so we can all put our heads together to figure out what we can do, what ways there are to get back to stock.. Just things people have done to restore back to stock.
Everyone having this issue people post here please as it will keep the Q&A thread clean.
At the moment I am encounter the issue, although I am not in a bootloop. I had a Official Firmware 4.4.2 installed that had been updated to 4.4.4.
Everything was working properly, but I flashed the latest CM11 Nightly. I had forgotten to backup my stock.
When I try to restore a stock firmware it Fails on partition so I didn't Want to chance flashing anything else in case I bricked my phone
At the moment my phones living off a CM11 TWRP backup which isn't ideal :/
Sent from my Moto G using XDA Free mobile app
I can share a 4.4.2 cmw backup but my net is slow as fk. I successfully downgraded using cmw backup.I think there is some problem with the mount points of the stock . I had this prob of not able to format or write using recovery and fastboot in my Chinese s4 clone but I formatted all partitions using the flash tool that I had and than I was able to flash ROM. It occurred because I had given wrong mount points in the update script of the ROM that I had previously flashed
Sent from my XT1033 using Tapatalk
xXx~~~SHLOK~~~xXx said:
I can share a 4.4.2 cmw backup but my net is slow as fk. I successfully downgraded using cmw backup.I think there is some problem with the mount points of the stock . I had this prob of not able to format or write using recovery and fastboot in my Chinese s4 clone but I formatted all partitions using the flash tool that I had and than I was able to flash ROM. It occurred because I had given wrong mount points in the update script of the ROM that I had previously flashed
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Would a twrp backup work the same?
Sent from my Moto G using XDA Free mobile app
Clarkiieh said:
Would a twrp backup work the same?
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
It should