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.
Related
I have been trying for hours to install both TWRP and CWM recoveries, and my phone will not accept them.
It goes through the process, yet upon the reboot into recovery, it just starts normally.
the message on the phone is: Mismathched partition size (recovery)
I have a Canadian version of 4.4.2 stock rom on my Moto G.
It is boolader unlocked and rooted.
Any ideas how to install the recovery?
My ultimate goal is to install a rom that supports russian language.
retfeg said:
I have been trying for hours to install both TWRP and CWM recoveries, and my phone will not accept them.
It goes through the process, yet upon the reboot into recovery, it just starts normally.
the message on the phone is: Mismathched partition size (recovery)
I have a Canadian version of 4.4.2 stock rom on my Moto G.
It is boolader unlocked and rooted.
Any ideas how to install the recovery?
My ultimate goal is to install a rom that supports russian language.
Click to expand...
Click to collapse
same problem here! brand new phone, 4.4.2 o2 UK.
the mismatched partition size error is not important i know that.
have tried Philz (got it to work once, but after rebooting, had gone again. ever after letting it fix the rom rewrite on exit!). also tried stock CWM 6046 and 6047.
have tried entering recover immediately after flashing.
have tried flashing multiple times.
have tried different usb ports.
ideas please?
i've never had this much trouble with any phone (have experience over 3 years with Blade, G300, Xperia range etc.)
edit: tried using fastboot -S 0 parameter also, seems to make no difference. phone won't boot into recovery. this is slightly different to the problem i had with old phone, that one would boot Philz but not boot any ROMs. this one is booting stock ROM. if i can get Philz to "take" again i could try flashing CM, but i wanted to stay on stock, and just root it..
edit2: just started working! bizarre.. hope this doesn't jinx it. i wrote two recovery images with -S 0 and it works, not sure if because of that or something else. btw Philz won't backup the stock rom, odd - it just errors out, CWM standard works though.
hurrah! i rebooted normally, went back to fastboot and recovery still there. this is with recovery-clockwork-6.0.4.7-falcon.img
now i can hopefully root it..
wonder if my 3rd moto g will get any easier! this is a huge PITA of random non-workiness so far.
FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Original post:
SHORT VERSION:
My god this has been one crazy root journey.
I have done absolutely EVERYTHING I could pull up on google to fix my phone, and what seemed to be the final piece to the puzzle, still has not fixed anything.
My phone is bricked, and i would really appreciate help at this point.
The current problem:
When I turn on my phone, it vibrates, and displays the WARNING BOOT LOADER UNLOCKED screen, and stays there forever.
I can access my boot loader, and recovery, but I dont know what to do at this point.
I tried a quick flash stock recovery kit kat with moto tool AIO, and it didnt help.
Any ideas?
LONG VERSION (backround info may help to understand the current issue)
Now, if you want to know what began all of this, continue reading, otherwise the above is my current issue.
After successfully unlocking and rooting my phone
I downloaded SWITCHME, an app that lets you create multible users on the phone. the instructions say that you can use a sub account to test and mess around with anything because you can simply go back to the admin account that has everything untouched.
That was a lie.
1.I deleted .setup, along with a few other things THAT WHERE NOT FLAGGED AS IMPORTANT, assuming the phone would still work. and my phone went bonkers, displaying this infinite message: UNFORTUNATELY, SETUP HAS STOPPED. It was impossible to use the phone, and I could only access bootloader.
2.After endless googling, driver downloading, xda mod installing, I managed to set up my boot loader to do the guide restore stock firmware:http://forum.xda-developers.com/showthread.php?t=2542219
Sadly, I flashed the wrong model number package, I was flashing x35, when I later discovered that my phone is x45.
Flashing the x35 firmware bricked my phone further, to where it would "fail to boot up" and would only display bootloader over and over after attempting to turn the phone on.
3. Simple, I realized I flashed the wrong thing, so I downloaded the x45 firmware from the firmware teem on this website, flashed all of the commands, and bam, the phone starts up with the boot loader warning, and DOES NOT get stuck in the previous boot loader issue I had.
But now the phone wont get past that warning screen so... now im pissed.
Please, if anyone can help me I would greatly appreciate it, Im so close to getting my phone back...
EDIT 2: Looks like the phone wont stay shut down, I realized that if I dont open up boot loader, it will turn itself on and display the warning message.
EDIT:
The stuffs I have, ready to try anything:
CWM touch mod
Moto Tool AIO
Minimal ADB and Fast boot
RETUS x1045 factory firmware
All directories, folders, cmd commands are set up and working properly between all of the programs.
The phone appears to be responding to all cmd commands properly.
I also have the windows one touch super boot root method. (he superboot-windows.bat )
Im afraid to try anything major after freshly flashing the x45 firmware that seemed to bring me one step closer without the help of someone else.
I restored stock to my phone using this link yesturday http://www.ibtimes.co.uk/how-restore-motorola-moto-g-stock-firmware-1447290
it may work for you
I have almost the same problem as if the fastboot not install anything despite not display errors
great that you got it done.
maybe my few cents about my "bricking" story. (xt1032 moto g)
yesterday i wanted to change the rom from cm11 nightly to another custom rom like ehndroix/carbonrom...
first i thought that will be done in a few mins, after having already flashed a custom rom.
then the story began, getting adb work, but, 2weeks ago everything was setup and went fine. dunno why my laptop lost the "drivers".
thats the link which solved that problem: tinyurl . com / kgffjh4 [sorry cant post links outside of xda yet, spam protection]
so after a few hours of getting that fixed i, i began flashing.
suddently i got stuck in bootscreen (ehndroix logo for example)...
then i wanted to go back with my previous backup made internaly of clockworkmod. though i couldnt restore my backup because there was an error message while restoring /data of my backup
also when restoring to factory/wipe in cwm there was that error message about clouldnt "touch" /data, i dont remember the message exactly.
after thinking i bricked everything, i though lets wipe my internal sdcard, maybe that causes the /data error.
then i restarted the device and went for a shower... after 15min i came back and my device was "started".
now i dont know that exactly helped, maybe wiping all data on my phone, or just letting my device boot for a "long" time...
so, thats my yesterdays brick story.
do a factory reset if the bootloader has that option.. otherwise install or run/boot a custom revovery, then either
try the factory reset option there and reboot or..
wipe everything and install a rom
Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!
ngr.hd said:
Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!
Click to expand...
Click to collapse
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors
angelgzg said:
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors
Click to expand...
Click to collapse
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.
ngr.hd said:
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.
Click to expand...
Click to collapse
I flash the recovery but rebooted into recovery, the android keeps popping up (no commands)
FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Sorry I'm traveling a d couldnt update thread fast enough.
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
Kinda new to this, so I apologize for any incorrect terminology. This is the second phone I've tinkered with, the first having been a LG Optimus Q which I only rooted.
So, I started off with flashing TWRP recovery and rooting my phone. Everything was fine. Decided I wanted to tinker with the status bar and other parts of the display and found CyanogenMod.
Flashed CM recovery, then installed CM from CM recovery. Booted into device to find I had lost root, and somewhere in the process of re-rooting my phone stopped booting past the "boot-loader unlocked" warning screen, but I can access recovery etc. It also boot-loops when I don't power it down from recovery.
Have attempted flashing stock, re-flashing TWRP/CM recovery, then attempted to install CM again from CM recovery only to have it fail. Could a corrupt mod cause a soft-brick?
I'm re-downloading CM now, hoping that a non-corrupt file will fix this.
Anyone have any other suggestions in case that doesn't work?
::EDIT:: It worked. Phone boots past "bootloader unlocked" warning screen, past the CM boot logo and into the phone.
Wrong place
This is Moto g3 forum!
Yousvel said:
This is Moto g3 forum!
Click to expand...
Click to collapse
This was referencing my Moto G 3, actually.
About a year ago, a friend gave me his Moto G so that I rooted it for him. On the system settings it showed as "falcon", XT1032. Everything was working fine. Then, he got a Moto G3, and gave his old Moto G to his young brother. After about two months, my friend told me that the old Moto G was in a bootloop, so I fixed it. Two weeks later, he told me the phone was no longer booting (it could barely boot into fastboot) and gave it to me again. Obviously, his young brother did something, but I don't know what, oh and also both times the battery was completely discharged when I received it.
So, I thought "Easy, just flash stock image and it will boot again". So I downloaded XT1032's stock image (5.1, as that was the version installed) and tried to flash it. Got many errors, both on PC fastboot/mfastboot and phone's fastboot. Also I couldn't boot or flash TWRP recovery, everything was broken. So I checked the model number on the battery, and it said it was XT1039, the 4G, peregrine version. So I downloaded peregrine's stock, and tried to flash it. Still got lots of errors (image size is too large, boot hab failed or something like that, I can't remember it clearly) but at least now I was able to boot TWRP recovery, but I still couldn't permanently flash it. There I checked the partitions, and they were corrupted, so I fixed them. Tried to flash again with no luck. Booted TWRP, tried to flash LineageOS, and got an error saying that the phone is the Falcon version! So, downloaded Falcon's Lineage, flashed it successfully, but the system won't boot, instead it will default to stock recovery (which was previously not working). AGAIN tried to flash Falcon's stock, now I'm back to the begining...
A solution I thought was intentionally bricking the phone completely and blank flash it, but I'm unsure how to do it, and I don't think is the best option...
BTW if someone could tell me how every partition is originally formatted so I can be sure all of them are fine, thanks.