Related
Hi all,
I have a Xoom, running one of the nightlies from Team EOS (#34) and it was running fine until it started to get a lot of force closes. I figured thats fine ... I'm running a nightly, but then I started noticing that when I delete or install apps, then do a reboot, the apps are either not there (if I'd done an install) or still there (if I'd removed).
So then I figured, oh well, high time I got up to the latest nightly or even the stable build, and tried that, but low and behold after flashing the stable version of the Team EOS rom, when I booted back into the OS it was still the nightly #34.
So I tried restoring to the stock Motorola rom via fastboot, same result: booted into the OS on nightly #34. I tried a simple factory reset but when I boot back in all my data is still there.
So this is what I've tried:
- install Team EOS 1.0.0 stable build via CWM
- install Motorola stock rom via fastboot
- wipe data and cache via fastboot
- wipe data and cache via CWM
- factory reset via OS
... all with the same result - it just boots back into the OS with apps still there that I've deleted many times, and apps not there that I've installed many times. One slight point of note is that when I do the factory reset via OS, for some reason it boots into recovery, rather than back into the OS ... not sure if this is significant
Please help? I've searched around and people have mentioned this problem, but the threads always end without an answer
you could try to unlock your xoom again (even if it is not locked!), that should wipe your /data partition. As to why it doesn't through fastboot (assuming you used fastboot erase userdata), no clue... Also, if you're flashing something through fastboot and you don't get an error message and it still didn't work, that sounds like serious trouble...:-\
Thanks for your reply.
I'll try that out (the unlock) and I'll give fastboot another go with that command. I may have used fastboot -w on one occasion, and:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
on another.
I was wondering if I can do anything tricky with mounting/unmounting in CWM, but thats an area I have little of my own knowledge. Any thoughts?
I tried both of those suggestions, with no luck. And no error messages either.
Please continue to help .. I appreciate it!
Must say ive got the same problem - getting spurious erros after updating to the final build (3.0) - even after a hard reset and then going through the startup stuff i still end up with my desktop wallpaper from before....although i must confess i havent done the command line stuff yet...
Sorry buddy, but the bad news is that i put mine in for repair, and they were unable to fix it. They said that some aspect of the hardware had been fried and would need an expensive replacement, which would not be worth the cost. One of the risks of custom ROMs .....
Hey All,
I just got my One XL and I was so excited by the root on 2.20 that I decided to try and flash the custom rom of AOKP on onto it.
After rooting the phone, I did the following:
Flashed TWRP 2.3.1.0 - success
Then I went and saw the thread about the AOKP rom and followed instructions. On that thread, it states that you must flash the boot.img before doing this through fastboot if you are coming forom 2.20 firmware, so I did that. Then I saw that it said on the thread "do not complain about bootlooping if you flashed a custom KERNEL or did not manually flash the stock KERNEL via fastboot" As this was the first custom rom I had attemped with this phone I assumed that I had the stock KERNEL already installed, so I did not flash any kind of kernel.
As soon as I flashed the boot.img from AOKP, I saw that there was red writing on the bootloader about this being for development use only and I noticed that the phone would get past the bootloader to a black screen and then would reboot (boot loop).
I thought that the issue here was that I did not flash the kernel so I went and downloaded the rohan.kernel and flashed that. HOWEVER, I did not realize that I was meant to use recovery to do that and I pushed the boot.img from within the kernel via fastboot instead of using recovery to flash the new kernel (not sure if that matters all that much, but I think that from now on all rom work will be done in the day time after sleeping a little more).
After doing that I see no change in the performance of the phone (it is still boot looping). I am unsure of what to do now. I managed to push the KERNEL zip file and the ROM zip file to the phone via adb but when I try and install them via TWRP I am getting an error because the phone reports that it is unable to mount /sdcard/.
Can one of the far more knowlegable gurus here point me in the right direction? I have wiped the cache and davlik cache numerous times but that has not helped. Should I use TWRP to wipe the system? How can I get the phone back to a place where I can install the new rom?
Thanks!!
ackerchez said:
Hey All,
I just got my One XL and I was so excited by the root on 2.20 that I decided to try and flash the custom rom of AOKP on onto it.
After rooting the phone, I did the following:
Flashed TWRP 2.3.1.0 - success
Then I went and saw the thread about the AOKP rom and followed instructions. On that thread, it states that you must flash the boot.img before doing this through fastboot if you are coming forom 2.20 firmware, so I did that. Then I saw that it said on the thread "do not complain about bootlooping if you flashed a custom KERNEL or did not manually flash the stock KERNEL via fastboot" As this was the first custom rom I had attemped with this phone I assumed that I had the stock KERNEL already installed, so I did not flash any kind of kernel.
As soon as I flashed the boot.img from AOKP, I saw that there was red writing on the bootloader about this being for development use only and I noticed that the phone would get past the bootloader to a black screen and then would reboot (boot loop).
I thought that the issue here was that I did not flash the kernel so I went and downloaded the rohan.kernel and flashed that. HOWEVER, I did not realize that I was meant to use recovery to do that and I pushed the boot.img from within the kernel via fastboot instead of using recovery to flash the new kernel (not sure if that matters all that much, but I think that from now on all rom work will be done in the day time after sleeping a little more).
After doing that I see no change in the performance of the phone (it is still boot looping). I am unsure of what to do now. I managed to push the KERNEL zip file and the ROM zip file to the phone via adb but when I try and install them via TWRP I am getting an error because the phone reports that it is unable to mount /sdcard/.
Can one of the far more knowlegable gurus here point me in the right direction? I have wiped the cache and davlik cache numerous times but that has not helped. Should I use TWRP to wipe the system? How can I get the phone back to a place where I can install the new rom?
Thanks!!
Click to expand...
Click to collapse
First of all I think if you're on 2.2 fw I don't think you can flash kernels through TWRP - I think it has to be through fastboot, I don't know first hand as I'm still on an earlier fw version.
Secondly if you can get into recovery you can flash another rom.
Go to Mount > Mount USB Storage with your phone connected via USB, it should mount as a drive otherwise windows asks you to format format the drive if this happens chances are may have wiped it in bootloader with factory reset or clear storage in either case just format the drive.
You can then drag and drop another rom onto the phone and flash that - remember to extract the boot.img from the rom and flash via fastboot so it will boot.
Goodluck
thejosh86 said:
First of all I think if you're on 2.2 fw I don't think you can flash kernels through TWRP - I think it has to be through fastboot, I don't know first hand as I'm still on an earlier fw version.
Secondly if you can get into recovery you can flash another rom.
Go to Mount > Mount USB Storage with your phone connected via USB, it should mount as a drive otherwise windows asks you to format format the drive if this happens chances are may have wiped it in bootloader with factory reset or clear storage in either case just format the drive.
You can then drag and drop another rom onto the phone and flash that - remember to extract the boot.img from the rom and flash via fastboot so it will boot.
Goodluck
Click to expand...
Click to collapse
Hey!
Thanks a ton for your reply! I managed to get the phone to install a new ROM (AOKP V5) and it seems to boot up. Now when I get into that rom, I see all kinds of things crashing on me. The "Settings" app crashes, the keyboard crashes..any idea?
Did you wipe system, factory reset, davlik and cache from within TWRP before flashing?
Try that otherwise if you're still running into issues post in the thread.
You flashed the 11/10 JB gapps?
Sent from my Nexus 7 using xda premium
ok, i got the phone back up now and have been able to flash stuff properly.
I am working on an issue where after flashing a new rom (AOKP v4) and then a new kernel right after (rohan.kernel V2) the rom seems to hang on the loading splash screen. Has anyone else had this happen? Know how to solve it?
ackerchez said:
ok, i got the phone back up now and have been able to flash stuff properly.
I am working on an issue where after flashing a new rom (AOKP v4) and then a new kernel right after (rohan.kernel V2) the rom seems to hang on the loading splash screen. Has anyone else had this happen? Know how to solve it?
Click to expand...
Click to collapse
Did u wipe everything? (davlik, cache)
Sent from my HTC One XL using xda premium
[SOLVED]
So after having my Transformer for some time now (unlocked, rooted, and running CROMI) it began to get sluggish. I wanted to upgrade to something else, and decided to try PA HALO http://forum.xda-developers.com/showthread.php?t=2376927
I missed something somewhere, prob the fact that I installed TWRP over my CWM that I had from long ago, instead of upgrading to the new CWM, or the fact that I'm still on the 10.4.4.25 bootloader. I rebooted into recovery, flashed the PA zip, rebooted into recovery, flashed the new GAPPS, and wiped the cache and Delvik. When I went to boot it up the "ParanoidAndroid3+" text and neon jellybean/fish thing show up, then nothing.
I (stupidly) did not make a new backup before doing this change (though there is one from my CWM, but TWRP doesn't seem to recognize it).
ADB does not seem to be working. When I select the USB icon, while using the power+volDown, I get the message "starting fastboot usb download protocol" and ADB does not see the device. If I let the device try and boot (when it gets stuck at the neon jb/fish) ADB sees the device, but gives the error <waiting for device> when I try and flash the new CWM. I seem to be able to access the terminal from TWRP, so I know there is a way to load the old CWM restore files, I just don't know how.
Help is needed.
found a way to do it, but I guess it took away my root when I flashed the new rom. Now I get "su is not recognized" from the terminal..... I'm downloading http://forum.xda-developers.com/showthread.php?t=2107271 and will try to get the os to boot. I can always re root the device, but I kinda need the device to boot into something first.
You missed quite a lot to get yourself into that pickle.
The second line of the PA thread reads:
GET THE LATEST BOOTLOADER AND RECOVERY
The link leads you to the CM 11 thread where it says in no uncertain terms that you need to be on the 10.6.1.14.4 or later bootloader. You think a 10.4.4.25 bootloader will run a JB 4.3 rom?
I hope you get it working.... Good luck
berndblb said:
You missed quite a lot to get yourself into that pickle.
The second line of the PA thread reads:
GET THE LATEST BOOTLOADER AND RECOVERY
The link leads you to the CM 11 thread where it says in no uncertain terms that you need to be on the 10.6.1.14.4 or later bootloader. You think a 10.4.4.25 bootloader will run a JB 4.3 rom?
I hope you get it working.... Good luck
Click to expand...
Click to collapse
Thanks for the kind kick to the nuts guy. I flashed the new bootloader (10.6.1.14.4) http://forum.xda-developers.com/showthread.php?t=2223918 that was already on the root of my tablet, downloaded GAPPS (4.2.2-4.3) http://forum.xda-developers.com/showthread.php?t=2405292 and placed it on MicroSD card, and already had the PA rom http://forum.xda-developers.com/showthread.php?t=2039557
Did some searching and came across a thread (can't find it now) that said to wipe before and after installing GAPPS.
It works now. The process went as follows:
1. Flash bootloader and reboot into recovery
2. Wipe cache/Delvik, flash GAPPS, wipe again
3. Flash rom
4. Reboot and wait for the rom to settle
Something is still wrong, or I'm not understanding the layout of PA, because I'm missing some options and buttons for some apps I've downloaded. I've made a back up with TWRP (for just in case), and am going to try getting CM 10.2 on there.
datboyc said:
Thanks for the kind kick to the nuts guy. I flashed the new bootloader (10.6.1.14.4) http://forum.xda-developers.com/showthread.php?t=2223918 that was already on the root of my tablet, downloaded GAPPS (4.2.2-4.3) http://forum.xda-developers.com/showthread.php?t=2405292 and placed it on MicroSD card, and already had the PA rom http://forum.xda-developers.com/showthread.php?t=2039557
Did some searching and came across a thread (can't find it now) that said to wipe before and after installing GAPPS.
It works now. The process went as follows:
1. Flash bootloader and reboot into recovery
2. Wipe cache/Delvik, flash GAPPS, wipe again
3. Flash rom
4. Reboot and wait for the rom to settle
Something is still wrong, or I'm not understanding the layout of PA, because I'm missing some options and buttons for some apps I've downloaded. I've made a back up with TWRP (for just in case), and am going to try getting CM 10.2 on there.
Click to expand...
Click to collapse
The "kick" was really meant as a friendly slap upside your head which was probably unnecessary since I hope you did that yourself already extensively - so I apologize
Glad you got it working :thumbup:
Hello,
My TF700 was on a CleanRom (2.3 i think), for a while, i decided to update.
- I installed the latest CWM (via fastboot) and flashed a Cyanogen 10.2 "stable", but my tablet freezed very quickly after successful boot, i tried some reboots and get same problem.
- I tried to install a stock ODEX root ROM, the tablet freezed at asus logo
- I flashed TWRP instead of CWM, it doesn't helped
- I tried wipe data and cache with TWRP, then my data was not accessible anymore and TWRP was unable to re-create it
- I searched on forums and found on this one that flash a boot.blob file can solve the problem
- It doesn't and now CWM and TWRP refuse to work ....
So i post here before getting my tablet completely brick.
At this point, i get access to fastboot / abd, CWM load but don't work (reboot when trying to do something), TWRP don't load.
Any suggestion to get back to a Stock ODEX rooted rom ?
Excuse my english ...
Asphodele said:
Hello,
My TF700 was on a CleanRom (2.3 i think), for a while, i decided to update.
- I installed the latest CWM (via fastboot) and flashed a Cyanogen 10.2 "stable", but my tablet freezed very quickly after successful boot, i tried some reboots and get same problem.
- I tried to install a stock ODEX root ROM, the tablet freezed at asus logo
- I flashed TWRP instead of CWM, it doesn't helped
- I tried wipe data and cache with TWRP, then my data was not accessible anymore and TWRP was unable to re-create it
- I searched on forums and found on this one that flash a boot.blob file can solve the problem
- It doesn't and now CWM and TWRP refuse to work ....
So i post here before getting my tablet completely brick.
At this point, i get access to fastboot / abd, CWM load but don't work (reboot when trying to do something), TWRP don't load.
Any suggestion to get back to a Stock ODEX rooted rom ?
Excuse my english ...
Click to expand...
Click to collapse
Hey Your in the right place
Shoot me an email, we can review your issues and if we find a solution we can post back here to help
XDA users with there issues....
My email is everywhere talke a look around
Thx Josh
Asphodele said:
Hello,
My TF700 was on a CleanRom (2.3 i think), for a while, i decided to update.
- I installed the latest CWM (via fastboot) and flashed a Cyanogen 10.2 "stable", but my tablet freezed very quickly after successful boot, i tried some reboots and get same problem.
- I tried to install a stock ODEX root ROM, the tablet freezed at asus logo
- I flashed TWRP instead of CWM, it doesn't helped
- I tried wipe data and cache with TWRP, then my data was not accessible anymore and TWRP was unable to re-create it
- I searched on forums and found on this one that flash a boot.blob file can solve the problem
- It doesn't and now CWM and TWRP refuse to work ....
So i post here before getting my tablet completely brick.
At this point, i get access to fastboot / abd, CWM load but don't work (reboot when trying to do something), TWRP don't load.
Any suggestion to get back to a Stock ODEX rooted rom ?
Excuse my english ...
Click to expand...
Click to collapse
Sounds like you are on an old bootloader. Flash the stock rom from asus by unzipping the zip you download from their website and placing in the root folder of your micro sd and then go into rck from the bootloader menu (power + volume down whilst booting)
Or you could just flash it from recovery....
lj50036 helped me to flash a new bootloader, recovery, rom and nvflash to make it unbrickable
Not just helped he spent many times to explain me how it works and what he did.
He is very nice and this was a pleasure to talk with him, i'm happy that there's still person like that on this planet
see you !
Asphodele said:
lj50036 helped me to flash a new bootloader, recovery, rom and nvflash to make it unbrickable
Not just helped he spent many times to explain me how it works and what he did.
He is very nice and this was a pleasure to talk with him, i'm happy that there's still person like that on this planet
see you !
Click to expand...
Click to collapse
I buy a tf700 with cm 11 a few days ago i am really interessted on how this steps works. I really want to make it unbrickeable, But i dont really understand how it works. I can not enter in fastboot. at least i got cwm interface when rebooting with adb into recovery.
Can u explain how you did it?
It invovles flashing a modified bootloader and the flatline recovery and then using Wheelie to generate your nvflash blobs.
Step-by-step instructions (which you need to follow to the letter) are here:
https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Stuck in boot loop, fastboot and recovery accessible
Hello,
I'm having a similar issue and I need help! Initially my tablet was rooted with Cromi-X 5.4. Then I decided to try Crombi-KK.
Here is what happened:
- Updated TWRP recovery
- Did a full wipe as recommended
- Flashing got stuck at the Crombi-KK loading sign
- Tried to reflash but TWRP wasn't detecting data partition anymore
- Instead installed the other recommended recovery CWMR.
- Flashed Crombi-KK, it worked. Played around with it for a few days, it was wonderful, fast and responsive.
- Battery died out and when I turned it back on I got a UIDs system inconsistent error.
- I found online many recommendations to reflash so I tried to do that
- Since then I'm stuck in a boot loop. I see the initial "bios" Asus logo then it restarts over and over.
- I am able to access bootloader and recovery
I've tried reflashing the asus stock blob. I've tried wiping the data through CWMR but it starts working and then it restarts. I don't know what to do anymore, so if anyone can help me, I would really appreciate it!
Thanks
Which recovery and bootloader version do you have now?
A (for KK) outdated bootloader seems the most likely culprit.
You can try save the recovery log when you flash or grab a logcat of the bootloop, but probably it'll only tell you that the recovery cannot mount /data.
Determine that you are on the correct bootloader, if not update it. If you're lucky the tablet will start right up. If it doesn't, formatting /data is the only way I know to get it back. Not just wiping - formatting it. You will loose everything on internal SD, so I hope you have a nandroid you can restore from later.
If you use TWRP 2.7+ be aware that formatting can take more than an hour. Let it finish!
For good measure, download CROMBi-KK again, check the md5 and then flash that file.
I'm on 10.6.1.14.10 bootloader which I think is the latest one
I have 6.0.4.7 CWMR
I'm trying to format data completely but when i do it in CWMR it starts and then the tablet reboots on it's own after a couple of minutes.
How can I retrieve the logs, I never had to do it before.
Thanks for your help
Mhh, getting a little more complicated.
Your BL is ok...
What do you see in CWM when you go into Mounts and Storage? What is mounted?
The recovery logs are under Advanced > show logs.
I'm at work now but from what I remember the only thing mounted was the cache. I'll double check tonight. Do you think there's any hope or I have a brand new paper weight?
yasyas said:
I'm at work now but from what I remember the only thing mounted was the cache. I'll double check tonight. Do you think there's any hope or I have a brand new paper weight?
Click to expand...
Click to collapse
Can you fastboot flash twrp?
It's much much better than CWM, has its own terminal and will be easier to offer the correct format command.
sbdags said:
Can you fastboot flash twrp?
It's much much better than CWM, has its own terminal and will be easier to offer the correct format command.
Click to expand...
Click to collapse
So I flashed TWRP and when I go in mount/storage everything is selected except for system. Should I do a format data from the wipe menu before flashing crombi-kk again?
yasyas said:
So I flashed TWRP and when I go in mount/storage everything is selected except for system. Should I do a format data from the wipe menu before flashing crombi-kk again?
Click to expand...
Click to collapse
To be in the safe side, yes, that is what I would do. TWTRP 2.7.+ takes a long time to format and it may seem the process got stuck. Give it at least 90 minutes to finish.
Then reflash CROMBi
I'm back up and running !!!
This time installing TWRP, everything was mounted (maybe my previous flash before CWMR wasn't good), did a format data, waited until it was done, flashed latest Crombi-KK and going through setup now. Hopefully won't have the same UID issue on next shutdown. I didn't enable fsync or journaling so hopefully it won't happen again.
Thanks both of you for your help!
Good deal! Happy for you!
Rooting google pixel zl
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.