>>Be me.
>>Verified root and unlocked the bootloader. Wanted to put Cyanogen on my new phone. Since it's an older phone, it looks like the only way I can do that is through recovery mode (http://wiki.cyanogenmod.org/w/Install_CM_for_xt907).
So, I need to install a recovery image and whatnot. Cool. So I get going on that. Get the correct image, check the md5, get fastboot and adb working in my command prompt. Put the recovery img into the same directory as fastboot.exe. Fastboot devices, there it is, great. Attempt to flash image; variable not supported.
Google. Apparently on some phones there's a file that installs stock recovery on boot (http://forum.xda-developers.com/showthread.php?t=2017748). Okay, just have to rename it, I guess. Won't let me rename. Something to do with SU, possibly. Check SU, binary is out of date. Try to update. Failed. WiFi is fine. Nothing will make it update the binary file.
Get rid of SU. Try SuperSU. Update binary without a hitch. Still can't change file name. NFC what to do now. Might have to try a completely different recovery. Would like to get this to work, since I'd prefer to have CW Recovery, so I can use the CW Rom Manager, although I guess you can use CW Rom Manager as long as you have some type of recovery. Any help would be greatly appreciated. Getting frustrated and out of ideas.
You did grab your recovery from here correct... I've heard of to many issues with cwm you're better off using TWRP IMO but those are the recoveries for our device... Try Flashing with flashify or Rashr...
Sent from my XT907 using XDA Premium 4 mobile app
No, I got it from the CWM Rom Manager website. I'll try flashing with one of those apps. Failing that, I'll try TWRP. I'll keep you posted. Thanks for the fast reply.
Used Flashify to flash TWRP image, worked flawlessly. Thanks so much, buddy, you're awesome. I first rooted my Droid Inc like 2 yrs ago before there were really a lot of apps for flashing, so I'm totally floored at how easy it was to root and unlock this phone. Excited to flash more stuff!! XD
cm10.1.3 stable, miui roms, colorOS rom, avatar rom. not working import contacts from sim card. droid razr m
xt907. i live in georgia. (tbilisi). please
help me. sorry my bed english.
Still having some issues...
Got my TWRP recovery working, so I went ahead and tried to flash Cyanogen. I'm confused abt the builds. What's the difference between nightlies (unstable, I guess?), and snapshots? Also, why is there a build download for my phone, but also one for my phone's processor? People on the Razr M dev forum were saying they were using the nightly for the processor. So, anyway, I tried to flash a snapshot for cwm11 4.4.2 for my phone model, and I got this image. Went ahead and restored, but not sure how to proceed from here. Pls, advise.
Inb4 my phone is running 4.4.2, and I did do a factory reset before flash.
Machostar, I'm not sure if this is the right thread for that type of question.
machostar said:
cm10.1.3 stable, miui roms, colorOS rom, avatar rom. not working import contacts from sim card. droid razr m
xt907. i live in georgia. (tbilisi). please
help me. sorry my bed english.
Click to expand...
Click to collapse
Just sync contacts with your google account or use Titanium Backup. Quicker and easier... and works.
---------- Post added at 02:02 PM ---------- Previous post was at 02:01 PM ----------
Zamkat said:
Got my TWRP recovery working, so I went ahead and tried to flash Cyanogen. I'm confused abt the builds. What's the difference between nightlies (unstable, I guess?), and snapshots? Also, why is there a build download for my phone, but also one for my phone's processor? People on the Razr M dev forum were saying they were using the nightly for the processor. So, anyway, I tried to flash a snapshot for cwm11 4.4.2 for my phone model, and I got this image. Went ahead and restored, but not sure how to proceed from here. Pls, advise.
Inb4 my phone is running 4.4.2, and I did do a factory reset before flash.
Machostar, I'm not sure if this is the right thread for that type of question.
Click to expand...
Click to collapse
Nightlies are going to be on the KK bootloader (your 4.4.2 firmware). Use them, or downgrade back to JB and use a snapshot (or _jbbl nightlies).
xKroniK13x said:
Just sync contacts with your google account or use Titanium Backup. Quicker and easier... and works.
---------- Post added at 02:02 PM ---------- Previous post was at 02:01 PM ----------
Nightlies are going to be on the KK bootloader (your 4.4.2 firmware). Use them, or downgrade back to JB and use a snapshot (or _jbbl nightlies).
Click to expand...
Click to collapse
Thank you! I'll try a nightly; I'm still confused abt why the snapshot didn't work. It was supposed to be for 4.4.2. What am I missing?
Tried to flash the first image on the list of CM nightlies for xt907, with gapps KK and it just did the same thing again. Failed. I don't understand why this isn't working. I checked the md5, copy to SD card via USB cable, boot into recovery, factory reset, flash. What am I doing wrong? What does that mean: "Error executing updater binary"?
Zamkat said:
Tried to flash the first image on the list of CM nightlies for xt907, with gapps KK and it just did the same thing again. Failed. I don't understand why this isn't working. I checked the md5, copy to SD card via USB cable, boot into recovery, factory reset, flash. What am I doing wrong?
Click to expand...
Click to collapse
Format and go to advanced format and wipe everything except external SD card. Yes this means wiping all internal memory. I had to do it before CM would boot, as did a few others on here.
Sent from my RAZR M (CM Nightlies) from Tapatalk Pro.
Booted into recovery, Advanced Wipe, checked every box but Micro SD card. Still failed.
Zamkat said:
Thank you! I'll try a nightly; I'm still confused abt why the snapshot didn't work. It was supposed to be for 4.4.2. What am I missing?
Click to expand...
Click to collapse
There are NO snapshot builds for the KK bootloader.
Zamkat said:
Tried to flash the first image on the list of CM nightlies for xt907, with gapps KK and it just did the same thing again. Failed. I don't understand why this isn't working. I checked the md5, copy to SD card via USB cable, boot into recovery, factory reset, flash. What am I doing wrong? What does that mean: "Error executing updater binary"?
Click to expand...
Click to collapse
Zamkat said:
Booted into recovery, Advanced Wipe, checked every box but Micro SD card. Still failed.
Click to expand...
Click to collapse
There are no more individual builds. All moto_msm8960 devices have been unified. Go here and download the proper version.
ATTACK said:
There are NO snapshot builds for the KK bootloader.
There are no more individual builds. All moto_msm8960 devices have been unified. Go here and download the proper version.
Click to expand...
Click to collapse
Oh! I didn't know that. Why are those other builds still available for download if they don't work? :\ Okay, I'll try the unified nightly, thank you, again!!
Alright. Got the nightly for msm8960. Seems to be working great. One issue is that the wifi seems to be having more trouble connecting than before. I looked at the bug reports, but couldn't really find anything helpful.
Zamkat said:
Alright. Got the nightly for msm8960. Seems to be working great. One issue is that the wifi seems to be having more trouble connecting than before. I looked at the bug reports, but couldn't really find anything helpful.
Click to expand...
Click to collapse
Yup, that's the biggest issue ATM.
Sent from my RAZR M (CM Nightlies) from Tapatalk Pro.
Related
It is what it says on the box....
I accidentally flashed an updated 4.2.2 rom onto my rooted Nexus 4 that was only running 4.2.1
Now, I can't get by the repeated error messages.
In recovery mode have tried to wipe the cache, the dalvik... even tried a full new install of the SU binary.... but can't seem to recover from this error.
Any insight?
I'm only asking this because it's on the script us tech support people have to follow. Did you make a backup?
wipe data(factory reset), then reflash your 4.2.2 nexus 4 rom(and gapps if needed). just flashing the su binaries does nothing for you. i do stuff like this for fun sometimes, its neat seeing all those errors
benderunit9000 said:
I'm only asking this because it's on the script us tech support people have to follow. Did you make a backup?
Click to expand...
Click to collapse
Fair question -
I backed up all my data, yes.
And I had just done a fresh unlocking so I didn't think I needed to - I still had the SU binary in the root directory.
I tried to reflash, still won't boot up in a way I can get at the root directory to put new .zip ROMs on the root, etc.
simms22 said:
wipe data(factory reset), then reflash your 4.2.2 nexus 4 rom(and gapps if needed). just flashing the su binaries does nothing for you. i do stuff like this for fun sometimes, its neat seeing all those errors
Click to expand...
Click to collapse
Did the factory reset. But I don't know how to re-flash with 4.2.2 since it was 4.2.1 originally.
I've downloaded the binary... do I use a similar command ./fastboot .... etc. like I used for flashing the other things?
Robworldwide said:
Fair question -
I backed up all my data, yes.
And I had just done a fresh unlocking so I didn't think I needed to - I still had the SU binary in the root directory.
I tried to reflash, still won't boot up in a way I can get at the root directory to put new .zip ROMs on the root, etc.
Click to expand...
Click to collapse
there should be an adb sideload option in your custom recovery, you can push a rom to your phone from your computer using adb. you can also reflash the stock image via fastboot. then youll just have to reflash a recovery, then your su binaries or custom rom.
---------- Post added at 09:46 PM ---------- Previous post was at 09:42 PM ----------
Robworldwide said:
Did the factory reset. But I don't know how to re-flash with 4.2.2 since it was 4.2.1 originally.
I've downloaded the binary... do I use a similar command ./fastboot .... etc. like I used for flashing the other things?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2010312
simms22 said:
there should be an adb sideload option in your custom recovery, you can push a rom to your phone from your computer using adb. you can also reflash the stock image via fastboot. then youll just have to reflash a recovery, then your su binaries or custom rom.
Click to expand...
Click to collapse
Hmmm.
Okay. I'm using clockworkMod Recov 5.8.3.1
I don't see the sideload option, but I'll keep looking.
Robworldwide said:
Hmmm.
Okay. I'm using clockworkMod Recov 5.8.3.1
I don't see the sideload option, but I'll keep looking.
Click to expand...
Click to collapse
cwm should have it, twrp has it for sure.
simms22 said:
there should be an adb sideload option in your custom recovery, you can push a rom to your phone from your computer using adb. you can also reflash the stock image via fastboot. then youll just have to reflash a recovery, then your su binaries or custom rom.
---------- Post added at 09:46 PM ---------- Previous post was at 09:42 PM ----------
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
I've been trying for hours. NO IDEA how to do any of this with a MAC computer.
I at least get to my CDW recovery screen, but I don't have a clue what to do next.
1. Go back to 100% stock using efrant's guide on here
2. Read up on everything so you know what you're doing
3. Try again
EddyOS said:
1. Go back to 100% stock using efrant's guide on here
2. Read up on everything so you know what you're doing
3. Try again
Click to expand...
Click to collapse
For the benefit of those coming after me, who may run into the same problem I did:
I can attest to the wisdom of the above 3 simple steps. It took me several hours to *finally* get this right, but the ABSOLUTE SLAM-DUNK I'VE FINALLY GOT THIS SUSSED PROCESS happened start-to-finish in 20 minutes.
The key step: METICULOUS FOLLOWING EFRANT'S GUIDE.
Do not get sidetracked by other boards or 'short-cuts'.
Just do this... it works, and obviously I learned a lot along the way.
I'm now back to stock, and happily unlocking and rooting, installing custom ROMs just being cognizant of the difficulty if I flash a 4.2.2 ROM on a device that is currently 4.2.1 (which, I believe, is the stock Sprint even now as of April 23).
Thank you to EddyOS and Simms.
what you actually have to do when flashing a ROM with a higher android version than the one you are running? for example I am now on CM10.1, and when Android 5.0 comes out, I need to flash new bootloader and baseband to update to a 5.0 ROM and it will work? Or what?
Thanks in advance!
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
what you actually have to do when flashing a ROM with a higher android version than the one you are running? for example I am now on CM10.1, and when Android 5.0 comes out, I need to flash new bootloader and baseband to update to a 5.0 ROM and it will work? Or what?
Thanks in advance!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
The key for me was that in addition to flashing the new ROM (I was running 4.2.1 and wanted to put on a custom 4.2.2 ROM) I had to sequentially install the custom ROM then the gapps file while in the same session in recovery mode. Do NOT install just the ROM and then exit recovery mode and reboot! That is how mine got hung up and I had to do a full stock re-install (see Efrant's guide).
As I understand it, this was an issue due to the a change in directory structure or something, so YMMV - this may not apply to future versions of Android.
Robworldwide said:
The key for me was that in addition to flashing the new ROM (I was running 4.2.1 and wanted to put on a custom 4.2.2 ROM) I had to sequentially install the custom ROM then the gapps file while in the same session in recovery mode. Do NOT install just the ROM and then exit recovery mode and reboot! That is how mine got hung up and I had to do a full stock re-install (see Efrant's guide).
As I understand it, this was an issue due to the a change in directory structure or something, so YMMV - this may not apply to future versions of Android.
Click to expand...
Click to collapse
So you didnt actually have to do something special cause I always flash gapps in same session.
And baseband and bootloader, how did you do that? Just flash before installing ROM?
Sent from my Nexus 4 using xda app-developers app
When KLP finally comes out the first thing I will be doing is flashing the complete factory image when released from Google. This will update everything and then using a custom KLP ROM will be a sinch. This is my personal opinion and others may say otherwise but for me it works
EddyOS said:
When KLP finally comes out the first thing I will be doing is flashing the complete factory image when released from Google. This will update everything and then using a custom KLP ROM will be a sinch. This is my personal opinion and others may say otherwise but for me it works
Click to expand...
Click to collapse
Yeah but cant you just install new bootloader and baseband, and then flash a ROM? Much easier imo
Sent from my Nexus 4 using xda app-developers app
I, personally, prefer to flash everything first and then go custom. Dunno why, just do!
EddyOS said:
I, personally, prefer to flash everything first and then go custom. Dunno why, just do!
Click to expand...
Click to collapse
Meh, easier if you just flash stock ROM in CWM first if you want to...
But could someone please answer my question?
Sent from my Nexus 4 using xda app-developers app
Ok so I'm first going to attempt to list the process I've gone thru to describe the problem I'm having:
1. Received phone and took OTA(12B) when I got it
2. Rooted with IORoot15
3. Pushed TWRP via add... Thought I did it wrong so I reflashed it using Freegee
4. Couldn't flash any ROMs (status 7 error) so I thought I was soft bricked
5. figured out that I could flash a stock ROM so did that
6. thought problem would be solved by using CWM instead of TWRP
7. still can't flash any ROMs other than stock...
Any assistance would be greatly appreciated!
Oh and tried to use the Status 7 fix by removing the "assert" lines but then I just kept getting Status 6 errors.
sydtrakked said:
Ok so I'm first going to attempt to list the process I've gone thru to describe the problem I'm having:
1. Received phone and took OTA(12B) when I got it
2. Rooted with IORoot15
3. Pushed TWRP via add... Thought I did it wrong so I reflashed it using Freegee
4. Couldn't flash any ROMs (status 7 error) so I thought I was soft bricked
5. figured out that I could flash a stock ROM so did that
6. thought problem would be solved by using CWM instead of TWRP
7. still can't flash any ROMs other than stock...
Any assistance would be greatly appreciated!
Oh and tried to use the Status 7 fix by removing the "assert" lines but then I just kept getting Status 6 errors.
Click to expand...
Click to collapse
I'm stuck too, how did you flash the stock file?
sydtrakked said:
Ok so I'm first going to attempt to list the process I've gone thru to describe the problem I'm having:
1. Received phone and took OTA(12B) when I got it
2. Rooted with IORoot15
3. Pushed TWRP via add... Thought I did it wrong so I reflashed it using Freegee
4. Couldn't flash any ROMs (status 7 error) so I thought I was soft bricked
5. figured out that I could flash a stock ROM so did that
6. thought problem would be solved by using CWM instead of TWRP
7. still can't flash any ROMs other than stock...
Any assistance would be greatly appreciated!
Oh and tried to use the Status 7 fix by removing the "assert" lines but then I just kept getting Status 6 errors.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2587296
here for 12b recoveries
and search through the thread for edited roms
I have the TMO verison but plenty of my friend have successfully flashed trwp using flashify also what kernals and roms are you trying to flash over? are you clean or dirty flashing?
try latest version of twrp..
but i'm relying on twrp 2.6.3.3.. been working since i rooted the phone 2months ago
zekurosu said:
try latest version of twrp..
but i'm relying on twrp 2.6.3.3.. been working since i rooted the phone 2months ago
Click to expand...
Click to collapse
Can you post a link to the latest twrp recovery for tmo? ive been looking but couldn't find one.
I have the vzw g2 and i took the 12b update and rooted it finally today. i have the same issue and your saying i need the newer cwm? extract the .lok and flash? Can you please help me and give me step by step instructions because im stuck in the bad cwm and only have cm 10.2 on my sdcard. ive tried going back to stock but none of those methods are working for me even though i have all drivers and follow everything. i tried the method where i use the kdz files and also the tot files. kdz fails at 49% with no explanation and the tot method never starts after the instructions say unplug then replug back in. Im completely baffled, i havent messed around in awhile.
---------- Post added at 02:31 AM ---------- Previous post was at 02:29 AM ----------
He mentiones flashing a .lok file, i have downloaded the proper one, just a little guidance for how to since im stuck in recovery already...
---------- Post added at 02:32 AM ---------- Previous post was at 02:31 AM ----------
He mentiones flashing a .lok file, i have downloaded the proper one, just a little guidance for how to since im stuck in recovery already...
ceredics said:
I have the vzw g2 and i took the 12b update and rooted it finally today. i have the same issue and your saying i need the newer cwm? extract the .lok and flash? Can you please help me and give me step by step instructions because im stuck in the bad cwm and only have cm 10.2 on my sdcard. ive tried going back to stock but none of those methods are working for me even though i have all drivers and follow everything. i tried the method where i use the kdz files and also the tot files. kdz fails at 49% with no explanation and the tot method never starts after the instructions say unplug then replug back in. Im completely baffled, i havent messed around in awhile.
---------- Post added at 02:31 AM ---------- Previous post was at 02:29 AM ----------
He mentiones flashing a .lok file, i have downloaded the proper one, just a little guidance for how to since im stuck in recovery already...
---------- Post added at 02:32 AM ---------- Previous post was at 02:31 AM ----------
He mentiones flashing a .lok file, i have downloaded the proper one, just a little guidance for how to since im stuck in recovery already...
Click to expand...
Click to collapse
Have you tried to flash back to the 12A and not use the 12b
tbishop91 said:
Have you tried to flash back to the 12A and not use the 12b
Click to expand...
Click to collapse
Nope, the one i was using i believe was the 10. Also, when it boots it was secure boot unsuccessful. Im seeing a handful of people stuck with this with no solution thread.
You used ioroot did you open a cmd prompt and push a loki file using a adb command
tbishop91 said:
You used ioroot did you open a cmd prompt and push a loki file using a adb command
Click to expand...
Click to collapse
I used ioroot res i did. But no i dont recall EVER using adb....
ceredics said:
I used ioroot res i did. But no i dont recall EVER using adb....
Click to expand...
Click to collapse
How did you install your custom recovery did you do it thro the computer or thro your phone itself sorry for the question but im just trying to help and im a little confused
tbishop91 said:
How did you install your custom recovery did you do it thro the computer or thro your phone itself sorry for the question but im just trying to help and im a little confused
Click to expand...
Click to collapse
No i dont mind i appreciate it. i used the FreeGee app in the play store to install the CWM. It was the 60445 or whatever but with a 5 at the end.
ceredics said:
No i dont mind i appreciate it. i used the FreeGee app in the play store to install the CWM. It was the 60445 or whatever but with a 5 at the end.
Click to expand...
Click to collapse
so you flashed A ZIP thro you phone and you flashed it twice and not it wont boot? so you might have to use this method.
http://forum.xda-developers.com/showthread.php?t=2471370
tbishop91 said:
so you flashed A ZIP thro you phone and you flashed it twice and not it wont boot? so you might have to use this method.
http://forum.xda-developers.com/showthread.php?t=2471370
Click to expand...
Click to collapse
It boots and everything, I get into CWM. Just cant flash anything because I get abortion error status 7 every time. I see that method works for the TMO one, i have VZW.
Trying the method you posted now
ceredics said:
It boots and everything, I get into CWM. Just cant flash anything because I get abortion error status 7 every time. I see that method works for the TMO one, i have VZW.
Trying the method you posted now
Click to expand...
Click to collapse
have you tried to use twrp instead of clockwork, I think that's what cwm stands for make sure whatever you do you double check that method does not harm your device.
It didnt work... Fckkkkk. So to make it clearer
VZW
Lg G2
Rooted with io
Rom when rooted was stock latest ota
currently stuck in CWM with nothing to boot into because of consistent abortion then status 7.
can you sideload aboot.img from adb
Id need step by step instructions on how to sideload something because ive never messed with adb. It seems if i adb a different recovery or a specific file it may start to work. Can i sideload TWRP?
let me consult my know it all friend lol
I bought a phone pre rooted and everything. It was nice, but the problem is I am having trouble changing the recovery on the phone.
For a long time I had TWRP 2.6.3.4. I could not flash any recovery over it. I was finally able to flash TWRP 2.6.3.1 using the same method to get TWRP. At that point I'm still not able to flash a recovery over TWRP.
I just discovered "flashify" tonight where I had flashed the CWR image for the d800. Now I can't even boot into recovery. It acts like I have non. I can boot into android no-problem though.
When I use "flashify" or "Recovery Tools" they claim I still have TWRP 2.6.3.1.
______________________________________________________________________________________________________________________
Can someone please help me.
I too tried flashing CWM over TWRP using Flashify, but it didn't work, it still said I had TWRP. However, Flashify did work to revert back to Stock Recovery.
I still have the backup file of the Stock Recovery, I can upload it somewhere if you want to, then maybe you can install CWM.
I have a D802 myself, not sure if my backup would work with your D800 though. but if you're adventurous...
Hid3rs said:
I too tried flashing CMW over TWRP using Flashify, but it didn't work, it still said I had TWRP. However, Flashify did work to revert back to Stock Recovery.
I still have the backup file of the Stock Recovery, I can upload it somewhere if you want to, then maybe you can install CMW.
I have a D802 myself, not sure if my backup would work with your D800 though. but if you're adventurous...
Click to expand...
Click to collapse
I was able to get back a version of TWRP following this: http://theunlockr.com/2013/11/03/flash-custom-recovery-lg-g2-versions-video/
Still don't know why I can't get other recoveries like CWR or why almost all versions of CM will fail to flash using TWRP
EDIT
I miss read you post. I thought you had a copy of TWRP. Go ahead and send the the stock recovery as that's one thing I have yet to try..
Traceguy said:
I was able to get back a version of TWRP following this: http://theunlockr.com/2013/11/03/flash-custom-recovery-lg-g2-versions-video/
Still don't know why I can't get other recoveries like CWR or why almost all versions of CM will fail to flash using TWRP
EDIT
I miss read you post. I thought you had a copy of TWRP. Go ahead and send the the stock recovery as that's one thing I have yet to try..
Click to expand...
Click to collapse
Well now I'm not sure if it's a good idea. Even for custom recoveries there are different files to download for D800 and D802. I don't think my backup would be compatible with your variant.
If you want CM, try flashing Official Nightlies. I've heard they are stable. I flashed CM11 Nightly with TWRP 2.6.3.4 just fine. You can grab it for D800 here.
Hid3rs said:
Well now I'm not sure if it's a good idea. Even for custom recoveries there are different files to download for D800 and D802. I don't think my backup would be compatible with your variant.
If you want CM, try flashing Official Nightlies. I've heard they are stable. I flashed CM11 Nightly with TWRP 2.6.3.4 just fine. You can grab it for D800 here.
Click to expand...
Click to collapse
Mine never works. I think its a MD5 error or something. I can only get one version of CM running and I think it's 10.2, I assume my whole phone is just messed up. Not being able to flash CM or recoveries.
Try going back to stock and starting over? Did you by chance take the 10o ota? That seems to be causing issues for others.
Sent from my LG-D800
btm fdr said:
Try going back to stock and starting over? Did you by chance take the 10o ota? That seems to be causing issues for others.
Sent from my LG-D800
Click to expand...
Click to collapse
I'm not sure.
Is there a windows software out there that can bring me to stock sort of like the NexusToolkit for Nexus devices.
Traceguy said:
I'm not sure.
Is there a windows software out there that can bring me to stock sort of like the NexusToolkit for Nexus devices.
Click to expand...
Click to collapse
Settings - about phone - software information
See what software version you have.
Sent from my LG-D800
btm fdr said:
Settings - about phone - software information
See what software version you have.
Sent from my LG-D800
Click to expand...
Click to collapse
I'm currently running CyanogenMod "10.2.0-d800", there is no "Software Information" or "Version"
Recovered back to Clean ROM 2.0
Software version: d80210b
EDIT:
Using this guide here: http://forum.xda-developers.com/showthread.php?t=2468858
I was able to get CWM.
So far I've come to the conclusion. The only way to change recoveries is through the PC and not from the phone it's self
Found it, nevermind
Sent from a PollutedG2 using the xda premo app
Hello everyone!
So i installed the CM12 rom for Moto X Play xt1562 version. Everything went fine until i did a factory reset. I first had a bootloop and could go inside the rom again. Then i did a factory reset and now i cant get pass TWRP..
I have been searching on the forum for clues why and how to solve my problem but cannot find anything.
Just to describe what message i get is :
" failed to mount /dev/block/bootdevice/by-name/system at/system: No such file or directory."
I have the "stock" rom aswell but the same message appear when i do this
I'm very happy if someone have the answare to my million dollar question!
Thanks in advance!
I'm confused. You flashed cm12, then it booted fine. You went back into twrp and did a factory reset? At this point you couldn't boot anymore. You then tried to flash your stock ROM with twrp?
I know there may be a language barrier, but I'm having trouble following. Are you trying to go back to stock to sell?
dictionary said:
I'm confused. You flashed cm12, then it booted fine. You went back into twrp and did a factory reset? At this point you couldn't boot anymore. You then tried to flash your stock ROM with twrp?
I know there may be a language barrier, but I'm having trouble following. Are you trying to go back to stock to sell?
Click to expand...
Click to collapse
Had a hard time explaining this problem.
I worked it out and got it fixed by installing the newest version of TWRP but when i'm trying to install the latest "stock" version of Moto X (found in this forum, EU-Version) it just fails. So i have to install CM12 and dont have ny choice.
Thanks for the answare dictionary!
Off topic, is it possible to install another camera then stock Cm12?
Fozec said:
Had a hard time explaining this problem.
I worked it out and got it fixed by installing the newest version of TWRP but when i'm trying to install the latest "stock" version of Moto X (found in this forum, EU-Version) it just fails. So i have to install CM12 and dont have ny choice.
Thanks for the answare dictionary!
Off topic, is it possible to install another camera then stock Cm12?
Click to expand...
Click to collapse
You can't install the stock ROM by recovery. You have to extract the contents of the zip and use fastboot from your computer to flash. Glad you're at least up and running though.
Yes you can install Alternate cameras.
dictionary said:
You can't install the stock ROM by recovery. You have to extract the contents of the zip and use fastboot from your computer to flash. Glad you're at least up and running though.
Yes you can install Alternate cameras.
Click to expand...
Click to collapse
Awesome! I downloaded the stock version for XT1562 but it cannot be installed through fastboot or sideload, i dont know why? :S Always get "FAILED"
Fozec said:
Awesome! I downloaded the stock version for XT1562 but it cannot be installed through fastboot or sideload, i dont know why? :S Always get "FAILED"
Click to expand...
Click to collapse
Just how are you trying to flash it? Are you unzipping the zip, and flashing each step individually, like posted in the linked thread?
Flash stock recovery I imagine it's checking the signature and failing when it sees twrp.
Oh and I've installed moto camera app and gallery they work great. Available as a flashable zip in the camera thread I posted. A user shared the link.
Sent from my XT1562 using Tapatalk
I flashed stock while I didn't flash the stock recovery over my twrp. Granted, on reboot I had the android lying down, but it flashed no problem. Just went and flashed twrp again and all was well.
Hi,
I just unlocked the bootloader of my Moto G Plus 4 via adb, and after that I switched it on, it worked fine and I transferred SuperUser.zip into my phone's internal memory, and then tried to flash it through recovery, (following the sleps I read somewhere), since then my phone is not rebooting - it is rebooting into bootloader and I can enter recovery as well, but Im not able to reboot my phone. The device is being detected via adb when it is in recovery mode, but not in bootloader. Is this issue fixable? Please help me fix this.
EDIT: I forgot to mention, I'm not getting the boot animation as well. I press the power key and nothing at all happens.
d1nesh said:
Hi,
I just unlocked the bootloader of my Moto G Plus 4 via adb, and after that I switched it on, it worked fine and I transferred SuperUser.zip into my phone's internal memory, and then tried to flash it through recovery, (following the sleps I read somewhere), since then my phone is not rebooting - it is rebooting into bootloader and I can enter recovery as well, but Im not able to reboot my phone. The device is being detected via adb when it is in recovery mode, but not in bootloader. Is this issue fixable? Please help me fix this.
Click to expand...
Click to collapse
You got into bootloop, just download the stock ROM and then flash it again, follow any guide over XDA or see YouTube for more help. Flash ROM without locking bootloader will be good.
Sent from my Moto G4 Plus using Tapatalk
avirk said:
You got into bootloop, just download the stock ROM and then flash it again, follow any guide over XDA or see YouTube for more help. Flash ROM without locking bootloader will be good.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I forgot to mention, I'm not getting the bootanimation as well, I press the power button and nothing at all happens.
d1nesh said:
I forgot to mention, I'm not getting the bootanimation as well, I press the power button and nothing at all happens.
Click to expand...
Click to collapse
Yes that is what happen after unlocking Boot loader, just flash the stock ROM using any tutorial over XDA without locking the boot loader and then follow the proper instructions to root your mobile. Rooting is very easy on Android N. So I will say flash android N and then proceed.
Sent from my Moto G4 Plus using Tapatalk
avirk said:
Yes that is what happen after unlocking Boot loader, just flash the stock ROM using any tutorial over XDA without locking the boot loader and then follow the proper instructions to root your mobile. Rooting is very easy on Android N. So I will say flash android N and then proceed.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
d1nesh said:
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
Click to expand...
Click to collapse
First thing, your query doesn't belong to the development thread. It should had been created in "Questions and Answers"
Second thing, if you flash supersu on stock rom it won't boot due some security measures of Moto. Instead flash ElementalX kernel first and then flash supersu.
d1nesh said:
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
Click to expand...
Click to collapse
All information that you will need can be found here. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
For the latest stock nougat firmware for XT1643 check this link https://mega.nz/#!ystC2ZSL!ql6cyC5v5RgLQfo7G44mhi7Ng-AQBvtsouKxKinbHi8
If you have some confusion about flashing, be sure to check it out before going on. I believe you have some knowledge about fastboot and using it.
==vj== said:
First thing, your query doesn't belong to the development thread. It should had been created in "Questions and Answers"
Second thing, if you flash supersu on stock rom it won't boot due some security measures of Moto. Instead flash ElementalX kernel first and then flash supersu.
Click to expand...
Click to collapse
i'm really sorry about posting in wrong thread.
While trying to flash ElementalX kernel through memory card, I'm getting error: Zip signature verification failed, (in red).
nazim7 said:
All information that you will need can be found here. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
For the latest stock nougat firmware for XT1643 check this link https://mega.nz/#!ystC2ZSL!ql6cyC5v5RgLQfo7G44mhi7Ng-AQBvtsouKxKinbHi8
If you have some confusion about flashing, be sure to check it out before going on. I believe you have some knowledge about fastboot and using it.
Click to expand...
Click to collapse
Last time I used fastboot was more than one year ago. Also, my device is not being detected by adb when in bootloader.
d1nesh said:
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
Click to expand...
Click to collapse
You can try one thing if you have twrp and your phone is booting into recovery then do this.
Download any custom rom based on Android N, don't go with RR for now as it is not for newbie cause new build has some issue while flashing.
Download the gapps recommend the opengapps Nano package from the opengapps.org.
Place both zip on your sd card and boot into recovery and then wipe everything like, system, dalvik cache, cache, system and then install the both zip, first rom and then install gapps. Then reboot. I hope it will fix the bootloop issue.
d1nesh said:
Last time I used fastboot was more than one year ago. Also, my device is not being detected by adb when in bootloader.
Click to expand...
Click to collapse
What did you mean by your device not being detected in bootloader mode. Did you install the right drivers. Did you install minimal adb and fastboot. Can you do the below steps and tell me the result.
1. Download the drivers from here.
For Windows: http://www.devfiles.co/download/5eEx...ager_2.5.4.exe
2. Download the Minimal ADB and Fastboot = https://www.androidfilehost.com/?fid=745425885120698566
3. Install Minimal ADB and Fastboot = https://forum.xda-developers.com/sho....php?t=2317790
4. Restart the Moto G4 in fastboot mode. (Bootloader mode)
5. Connect the Phone to the computer.
6. In adb fastboot folder shift+right click and then in the pop up click "open command window here"
7. In the command line type: "fastboot devices"
Seeing your serial number means we know all is good and your phone is connected and you can go on flash the stock firmware. If the serial number is not showing, the drivers are not properly installed.
---------- Post added at 01:33 PM ---------- Previous post was at 01:25 PM ----------
avirk said:
You can try one thing if you have twrp and your phone is booting into recovery then do this.
Download any custom rom based on Android N, don't go with RR for now as it is not for newbie cause new build has some issue while flashing.
Download the gapps recommend the opengapps Nano package from the opengapps.org.
Place both zip on your sd card and boot into recovery and then wipe everything like, system, dalvik cache, cache, system and then install the both zip, first rom and then install gapps. Then reboot. I hope it will fix the bootloop issue.
Click to expand...
Click to collapse
I thought he don't have TWRP installed. If TWRP is installed, then go on with what he said. That is the best solution for you. :good:
avirk said:
You can try one thing if you have twrp and your phone is booting into recovery then do this.
Download any custom rom based on Android N, don't go with RR for now as it is not for newbie cause new build has some issue while flashing.
Download the gapps recommend the opengapps Nano package from the opengapps.org.
Place both zip on your sd card and boot into recovery and then wipe everything like, system, dalvik cache, cache, system and then install the both zip, first rom and then install gapps. Then reboot. I hope it will fix the bootloop issue.
Click to expand...
Click to collapse
I tried the same, but the flashing process is stuck on "Patching system image unconditionally..." I tried two different ROMs, and in both cases, it is stuck in the same step
d1nesh said:
I tried the same, but the flashing process is stuck on "Patching system image unconditionally..." I tried two different ROMs, and in both cases, it is stuck in the same step
Click to expand...
Click to collapse
Try with wiping everything, wipe system and internal storage as well, I know your important data will be gone but it will be worth a try. If anything comes up let us know, also what have you tried so far tell us in details so we don't repeat it over and over, also in above post some links are provided try them.
avirk said:
Try with wiping everything, wipe system and internal storage as well, I know your important data will be gone but it will be worth a try. If anything comes up let us know, also what have you tried so far tell us in details so we don't repeat it over and over, also in above post some links are provided try them.
Click to expand...
Click to collapse
I had tried wiping everything already, still I'm getting this error.
Also i'm getting one more error: Unable to load "/system".
d1nesh said:
I had tried wiping everything already, still I'm getting this error.
Also i'm getting one more error: Unable to load "/system".
Click to expand...
Click to collapse
Try with other pc or change the port for data cable. It seems your system partition got corrupted, also you can mount system partition under twrp and then try to format it.
d1nesh said:
I had tried wiping everything already, still I'm getting this error.
Also i'm getting one more error: Unable to load "/system".
Click to expand...
Click to collapse
When in TWRP, go to Mount and see if system is ticked or not. If not, mount the system and wipe it. Then flash the rom again. BTW which TWRP version are you using. From where you get it.
nazim7 said:
When in TWRP, go to Mount and see if system is ticked or not. If not, mount the system and wipe it. Then flash the rom again. BTW which TWRP version are you using. From where you get it.
Click to expand...
Click to collapse
System is not ticked when i go to Mount, neither am I able to tick it. BTW, I have twrp-3.0.2-0-athene.img.
d1nesh said:
System is not ticked when i go to Mount, neither am I able to tick it. BTW, I have twrp-3.0.2-0-athene.img.
Click to expand...
Click to collapse
So that is the problem. You have to install TWRP latest version. Version 3.0.2 r4 or higher by shreps will work for you. You can find it here. https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
The latest version is 3.0.3 n4. Flash it, mount the system and everything will be good for you
d1nesh said:
System is not ticked when i go to Mount, neither am I able to tick it. BTW, I have twrp-3.0.2-0-athene.img.
Click to expand...
Click to collapse
As @nazim7 suggested you to flash the latest TWRP and then try to flash the rom again, also you can try to resize the partition and try to format it from twrp from the option in twrp. Just let us know what the result come back.
nazim7 said:
So that is the problem. You have to install TWRP latest version. Version 3.0.2 r4 or higher by shreps will work for you. You can find it here. https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
The latest version is 3.0.3 n4. Flash it, mount the system and everything will be good for you
Click to expand...
Click to collapse
There's one more problem like I've mentioned previously. I have the latest drivers even then the device is not being detected via adb when in bootloader, but as soon as I boot into recovery, the device shows up on adb after command. How do I flash the recovery if the device doesn't show up in bootloader on adb?