Hi,
is it possible somehow to cleare the partitions "deeper" then it's possible with the build in format command inside CWM?
I tried the fastboot erase (system, data, boot) with the result "permission denied" also.
The problem is the Moto G got messed up during the update to 4.4.
Since that moment the Moto G won't boot up with any stock Rom i flashed and i checked up many, many different stock roms (4.3 and 4.4.2).
It is possible to access recovery. (only CWM-swipe is working, CWM-touch, TWRP or the stock recovery won't boot) (Somehow TWRP booted once, but never again...) Sometimes i even can't access CWM-swipe, than I have to erase userdata and cache inside bootloader.
The other thing is it was possible to boot up the G with the Lego Rom, but it rebooted very often (30secs, 1min, 10secs....)
At this moment even that doesn't work it's getting stuck inside the bootlogo like every other custom rom i tried (Slim, CM11).
This behaviour makes me belief that things must be messed up depper inside.
I like to wipe everything!
Try this to restore your system
http://forum.xda-developers.com/showthread.php?t=2644703
I dont know what happened woth your g , but this delets everything except of the bootloader and then flashes the normal stock Rom, so that your moto g is like new.
It could be that sth. is wrong with your recovery as you cant wipe or flash anything, maybe flashing another recovery via fastboot would make you able to flash roms again and you wont need to restore stock.
Hopefully this works but remember that it doesnt metter what you do, you are responsible for everything and noone else. I dont guarentee that this works.
Hi,
this is what i had done about 40 times with almost 20 different stock roms. They all doesn't boot up
The Lego-Rom is the onlyone which had booted up completly but rebooted automaticly. Now Lego is hanging in bootlogo.
Like i wrote in the first post. CWM-swipe is the only recovery that still works most of the time. And I tried the stock recovery, CWM-touch (philz-touch) and TWRP.
I need to go deeper with the wipe/format if it is possible.
Otherwise i need to dump the G.
Thats really weird. If this all doesnt work then i dont know.
Yep, this is why I'm asking for help! Maybe someone know more.
ikarugaski said:
Yep, this is why I'm asking for help! Maybe someone know more.
Click to expand...
Click to collapse
I WAS IN A SIMilar situation a few days back
i couldnt boot up nor boot to recovery so to make a slong story short, i simply took a system img and a boot img and a cwm recovery img and fasboot flashed all 4 one at a time and somehow it worked fully stock but at least i could reset up all my stuff from there.
kep i mind before this method i i tried the guide "restore stock moto g rom" for 2 days straight with fastboot failing to flash it each time. if ur ok with starting anew apps wise try to flash a stock rom.
Hi all,
So I'm far from a noob at at all of this (doing the custom android thing for years). But I'm not exactly constantly fiddling with my phone all the time anymore either. Basically I get a set-up that works for me, and I stick with it.
I've patiently been waiting to update to Lollipop. And today I did it. I did it by flashing the required factory images with fastboot.
AND IT WORKS. No problem. It boots. I go through the initial set-up. I can let it restore all my apps and passwords from the google servers, etc. So far so good.
My problem is that I cannot root. After I try, it bootloops (stuck at the Google splash, with my unlocked icon).
I tried to root before my first boot. I tried after the initial boot (before set-up and signing in). I tried rooting after setting it all up, and singing in, and letting google restore all of my apps. No matter which sequence I try, it will reboot a couple times at the first Google splash, and then fall back to Recovery.
(So, I'm on back on my rooted 4.4.4 nandroid, I think it's Mahdi Rom-- I forget)
Vital Stats:
Trying to install factory images of 5.0.1, all stock (system, boot (kernel), radio, bootloader)
Factory reset
(the above works fine)
TWRP 2.8.1.0
SuperSU-v2.40 (flashed via recovery)
Any ideas? Thanks for any help.
No, but could you try the previous version of SuperSU? Just to rule out the new version that I haven't tested please?
I updated to 5.0.1 earlier
Flashed all the img files exact userdata and then booted in to Android.
I then flashed TWRP 2.8.1.0 and used that to flash SuperSU 2.37
All that worked fine.. I then did a play update and SuperSU updated to 2.40
All working fine as far as I can tell. Apps needing root are working!
iowabeakster said:
Hi all,
So I'm far from a noob at at all of this (doing the custom android thing for years). But I'm not exactly constantly fiddling with my phone all the time anymore either. Basically I get a set-up that works for me, and I stick with it.
I've patiently been waiting to update to Lollipop. And today I did it. I did it by flashing the required factory images with fastboot.
AND IT WORKS. No problem. It boots. I go through the initial set-up. I can let it restore all my apps and passwords from the google servers, etc. So far so good.
My problem is that I cannot root. After I try, it bootloops (stuck at the Google splash, with my unlocked icon).
I tried to root before my first boot. I tried after the initial boot (before set-up and signing in). I tried rooting after setting it all up, and singing in, and letting google restore all of my apps. No matter which sequence I try, it will reboot a couple times at the first Google splash, and then fall back to Recovery.
(So, I'm on back on my rooted 4.4.4 nandroid, I think it's Mahdi Rom-- I forget)
Vital Stats:
Trying to install factory images of 5.0.1, all stock (system, boot (kernel), radio, bootloader)
Factory reset
(the above works fine)
TWRP 2.8.1.0
SuperSU-v2.40 (flashed via recovery)
Any ideas? Thanks for any help.
Click to expand...
Click to collapse
Try not doing that? When you go through the initial configuration, choose "Set up as a new device". Maybe the restore is somehow corrupting SuperSU?
BirchBarlow said:
Try not doing that? When you go through the initial configuration, choose "Set up as a new device". Maybe the restore is somehow corrupting SuperSU?
Click to expand...
Click to collapse
It happens even if I try to root before setting anything up at all.
albert_htc,
Are you saying: I should also flash the stock recovery first. Then boot for the first time. Then re-flash TWRP. Then flash SuperSU.
I never flashed the stock recovery. TWRP was on already on it.
Thanks guys. I'll give it another rip (doing stock recovery, then flashing back to TWRP) sometime soon.
iowabeakster said:
It happens even if I try to root before setting anything up at all.
albert_htc,
Are you saying: I should also flash the stock recovery first. Then boot for the first time. Then re-flash TWRP. Then flash SuperSU.
I never flashed the stock recovery. TWRP was on already on it.
Thanks guys. I'll give it another rip (doing stock recovery, then flashing back to TWRP) sometime soon.
Click to expand...
Click to collapse
Yes, flash the factory image using the batch file so every partition gets re-flashed. Now I'm thinking maybe your recovery is corrupt.
Run flash-all.bat and when your device reboots, go through all of the initial configuration and download all of the Gapps updates. Once that's all completed, go ahead and route using TWRP. If you find yourself still having the same problem, try live booting TWRP to flash SuperSU.
BirchBarlow said:
Yes, flash the factory image using the batch file so every partition gets re-flashed. Now I'm thinking maybe your recovery is corrupt.
Run flash-all.bat and when your device reboots, go through all of the initial configuration and download all of the Gapps updates. Once that's all completed, go ahead and route using TWRP. If you find yourself still having the same problem, try live booting TWRP to flash SuperSU.
Click to expand...
Click to collapse
I'm not going to flash over my user data, nandroids, app back-ups, etc. I'll stay with kit kat forever on my nexus 5 before I do that. Version numbers aren't that important. Hours wasted getting things set-up again are.
My recovery works fine. Both on kit kat and lollipop. My only problem is a boot loop when I flash SuperSU (via TWRP), on lollipop. I will try flashing stock recovery, though and then reflashing TWRP.
iowabeakster said:
I'm not going to flash over my user data, nandroids, app back-ups, etc. I'll stay with kit kat forever on my nexus 5 before I do that. Version numbers aren't that important. Hours wasted getting things set-up again are.
My recovery works fine. Both on kit kat and lollipop. My only problem is a boot loop when I flash SuperSU (via TWRP), on lollipop. I will try flashing stock recovery, though and then reflashing TWRP.
Click to expand...
Click to collapse
It's a tedious process, but it really isn't all that hard to back everything up to a computer, and you can do it easily with fastboot and a single command line.
Or what I'd recommend doing is just booting up, backing up all folders to a PC and then resetting and restoring later, backup apps with Titanium Backup (what I always do). A lot of us flashed factory images when Lollipop came out, so it isn't that bad once you start on the road.
Have you tried rooting from the bootloader via Chainfire's cf-auto root? I know I've read that sometimes rooting from recovery doesn't work properly, and that only certain zips will work. I've used the auto root each time (from stock fastboot flashing 5.0 & 5.0.1) with lollipop and it works fine. Link
Unzip and run batch file in bootloader. It will wipe everything if you haven't already unlocked bootloader (fastboot oem unlock). If you are already unlocked it won't wipe anything.
snappycg1996 said:
It's a tedious process, but it really isn't all that hard to back everything up to a computer, and you can do it easily with fastboot and a single command line.
Or what I'd recommend doing is just booting up, backing up all folders to a PC and then resetting and restoring later, backup apps with Titanium Backup (what I always do). A lot of us flashed factory images when Lollipop came out, so it isn't that bad once you start on the road.
Click to expand...
Click to collapse
I just backed the /sdcard, to my PC. I just re-ran titanium.
I can deal with "/sdcard issues" from updating to lollipop easy enough. That's a 30 second fix. I can deal with setting up my email accounts to my email client app. I can deal with launcher settings, and all the other apps, widgets, etc. Those are things that I can slowly get back to where I want. They aren't critical. But yeah, very tedious.
I think "starting over" may be much more tedious for me than most people though. I run ssh servers and clients on all PCs, servers, and phones (disabling passwords and using rsa encryption keys for security). It's very nice, once I get it all set up in that I can access everything (from anything) very easily. I do need root for that though also.
But if I can't just hit a "restore" to get it all my ssh addresses, keys, fingerprits, etc back to where it was and then I have to: reverify new fingerprints, generate new keys, re-enable passwords to transmit new keys for everything, then disable passwords (for all machines) ... well... I just get very very grumpy.
anactoraaron said:
Have you tried rooting from the bootloader via Chainfire's cf-auto root? I know I've read that sometimes rooting from recovery doesn't work properly, and that only certain zips will work. I've used the auto root each time (from stock fastboot flashing 5.0 & 5.0.1) with lollipop and it works fine. Link
Unzip and run batch file in bootloader. It will wipe everything if you haven't already unlocked bootloader (fastboot oem unlock). If you are already unlocked it won't wipe anything.
Click to expand...
Click to collapse
I'll check that out. Thanks.
Alright so I have a Moto G original version, currently running 4.4.4. I previously rooted it and stuck TWRP on it, but then when it became available to update to Lollipop on the Moto G I tried to get stock recovery on it. I used "MotoToolAIOV3" to put "Kitkat Stock Recovery" on it. This seemed to work fine, until it came to update, which then it errored every time I tried. I then realised the stock recovery that "MotoToolAIOV3" must be faulty or something, so I tried reputting TWRP on my Moto G by flashing it from an app called "Rashr". This seemed to be successful, HOWEVER I went to reboot my phone to check if it had worked, put it into bootloader, then went into recovery and it still came up with the stock recovery "MotoToolAIOV3" had given me. I was confused, so I tried "normal powerup", which THEN sent me into TWRP, however this time, when the bootloader unlocked warning came up, a weird blurry line went through my screen every so often, and then it went into TWRP, with the line going across the screen in TWRP as well. I've tried to boot into normal powerup through TWRP, Bootloader, normal powerup, holding down power button but every time I try, it goes into TWRP with a dodgy line going across my screen. I'm currently doing exams and I really need my phone as I have revision notes on apps that I can only access on that phone, and things such as exam timetable saved in the actual phone.
Please, somebody help ):
Again my phone is a Moto G Original Gen running 4.4.4 stock android, on a tesco thing (cant remember what its called might be kernel).
Thank you.
bump
bump
bump2
bump2
Arcenum said:
bump2
Click to expand...
Click to collapse
Seems like you have flashed TWRP into the kernel partition. Seem like the "Rashr" app or whatever flashed it there by mistake. I recommend that you install TWRP via a more standard procedure, such as using fastboot(if bootloader unlocked) or using the instructions given where ever you downloaded TWRP. Your situation is not serious as long as you are careful....
1. Install recovery to correct partition
2. Boot to that recovery and wipe/factory reset etc...
3. Install an new ROM.
Weirdest problem, and not one that I've ever encountered after playing around with Android since the G1 days!
My Boost Moto G 2013 will only boot into the recovery, no matter what I do. I've searched and searched through Google and on XDA and found nothing that matches my problems exactly.
I can get into the bootloader (am running version 41.1A) and flash a new recovery. I've got TWRP on there right now, but I've tried CWM as well -- same problem. I've actually installed Android 5.1 from the stock flashable zip, and it says it flashes fine, but still won't boot into it. No matter how I restart the phone, it just goes straight into recovery.
Any ideas?
I'm assuming that you've tried different ROMs? I had a weird problem where I could no longer flash any ROM's without getting an error. Only after I did a complete wipe of everything (including internal storage which was the key) was I able to properly boot up. Not quite the issue you're having but worth a shot, make sure you can access the phone on your PC so that you can copy over the ROM after the wipe.
I have had this problem recently. I believe I had to fastboot flash stock recovery, then an older, smaller CWM to avoid partition mismatch problems. Then flash the TWRP you want with a zip with CWM.
Sent from my XT1031 using Tapatalk
Hello people,
I just tried flashing TWRP to my J7 Prime phone. Odin flash was successful and I could boot into recovery. I followed through normal procedure(data format and no-verity-opt-encrypt flashed). I did not flash any other zips and when i tried to boot back into System my phone didn't get through the Galaxy Prime logo. It wouldn't even show the boot animation. Before this happened, I did root my phone and everything was fine, I accidentally deleted google play once and also wanted to flash stock firmware so I did. After I flashed the stock firmware, when I wanted to root it again it would work after flashing magisk and booting into the system but after some time passes the apps one by one would begin to freeze and at last no app would even load. When i try to reboot at this point, the phone wouldn't boot back into the system anymore. It would get past the Samsung logo but the boot animation wouldn't even play as i was stuck in a black screen. I tried to restore with TWRP then, (Only restoring Boot, System and Data but I didn't wipe anything on the system before restoring. I think that this might be the issue but I just recently got into rooting.) but when i rebooted to use my phone it wouldn't get past the Samsung logo. The Samsung J7 Prime logo would show up, then 1-2 seconds pass and then reboot. This was a loop.
I was able to reflash stock firmware and get it to work normally. Since I can't risk bricking the phone as I can't get a new one after this experience I didn't flash anything again. Because after i restored with TWRP back then and now my phone bricking just because of a TWRP flash I think if I just give it some more tries (even with difference in procedure) it might just get hard bricked. I think flashing firmware so often might brick it. I really don't know but I can't risk bricking this phone.
The phone right now is OK. I just want to learn why this might happen, what would cause this and how to fix this. I will not flash anything because again I can't risk getting this phone bricked.
Just getting some information for me is enough as I am also curious about this problem,
Thank you.