OK...I have/had an stock nexus 7 running 4.4.2....until it decided to stop working last night. It was stuck on boot loop. So I decided to try a few things. I tried skipsoft toolkit and I followed a few instructions that other people said worked for them. To make a long story short, things went wrong. Im not sure how but they did. I'm not super knowledgeable about all this but I'd say I know a good amount. I rooted my OG Droid and have my GS3 rooted so I'm not completely in the dark about this but I feel like a idiot at this point. In the skipsoft menu/"command prompt", i was able to get TWRP working through skipsoft but it says I dont have a OS loaded. So apparently I erased everything and Im not sure how to get it back. I've been trying to load a boot img on it but its not letting me. Im lost and would love some help. Here is the screen on my next and also what Im getting on the step of "writing radio" in skipsoft. Anybody know anything about this? Where do I need to go from here? Thanks so much!
Topdroid01 said:
OK...I have/had an stock nexus 7 running 4.4.2....until it decided to stop working last night. It was stuck on boot loop. So I decided to try a few things. I tried skipsoft toolkit and I followed a few instructions that other people said worked for them. To make a long story short, things went wrong. Im not sure how but they did. I'm not super knowledgeable about all this but I'd say I know a good amount. I rooted my OG Droid and have my GS3 rooted so I'm not completely in the dark about this but I feel like a idiot at this point. In the skipsoft menu/"command prompt", i was able to get TWRP working through skipsoft but it says I dont have a OS loaded. So apparently I erased everything and Im not sure how to get it back. I've been trying to load a boot img on it but its not letting me. Im lost and would love some help. Here is the screen on my next and also what Im getting on the step of "writing radio" in skipsoft. Anybody know anything about this? Where do I need to go from here? Thanks so much!
Click to expand...
Click to collapse
Hi, Topdroid01...
Looking at your first screenshot, where it says (amongst other things)....
Code:
.....
BASEBAND VERSION = N/A
.....
Or in other words, your Nexus 7 is WiFi only, and has no 'radio' 3G/GSM component.
...which may explain this 'FAILED' error message, in your second screenshot...
Code:
sending 'radio' (16384 KB )...
OKAY [ 1.983s]
writing 'radio'...
FAILED (remote: (BadParameter))
finished. total time: 2.005s
You can not flash a 'radio' baseband component to a device that doesn't support it.
Without more details, I suspect your skipsoft toolkit is attempting to flash the 'Nakasig' (WiFi/3G/GSM/mobile) factory image... instead of the correct 'Nakasi' factory image, for a WiFi only device.
You can download either from here.
So I strongly suspect, given the 'BASEBAND VERSION = N/A' reference in your first screenshot, that you have a WiFi only 'grouper' Nexus 7, and accordingly you need the 'Nakasi' factory image.
Hope this makes sense.
Rgrds,
Ged.
GedBlake said:
Hi, Topdroid01...
Looking at your first screenshot, where it says (amongst other things)....
Code:
.....
BASEBAND VERSION = N/A
.....
Or in other words, your Nexus 7 is WiFi only, and has no 'radio' 3G/GSM component.
...which may explain this 'FAILED' error message, in your second screenshot...
Code:
sending 'radio' (16384 KB )...
OKAY [ 1.983s]
writing 'radio'...
FAILED (remote: (BadParameter))
finished. total time: 2.005s
You can not flash a 'radio' baseband component to a device that doesn't support it.
Without more details, I suspect your skipsoft toolkit is attempting to flash the 'Nakasig' (WiFi/3G/GSM/mobile) factory image... instead of the correct 'Nakasi' factory image, for a WiFi only device.
You can download either from here.
So I strongly suspect, given the 'BASEBAND VERSION = N/A' reference in your first screenshot, that you have a WiFi only 'grouper' Nexus 7, and accordingly you need the 'Nakasi' factory image.
Hope this makes sense.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks for getting back to me so quick! As for the skipsoft toolkit, I think Im using the correct version. Ive went back and checked a few times but Ill triple check when I get home. I do have a wifi only version btw...so Ill go home and give your advice a try. It makes a lot of sense. Ill get back to you and let you know. Thank you so much!
Hey all! My Nexus 6P that has been on N Preview since day 2 is now stuck in a boot loop. It will usually just display the Google logo and then reboot. Sometimes it will get to the very beginning of the Android boot animation, but rarely.
Unfortunately, I didn't even know about the OEM Unucking setting until I've been trying to get my phone to boot again. I've tried using clearing cache, factory restore, adb sideload, and the flashing instructions Google provides. I've also tried using SkipSoft Android ToolKit with no avail as well. At this point I don't care if I end up with Marshmallow or back on N. I just want my phone working again xP
Does anyone have any ideas on how to restore my phone back to a working state? Thanks!
It also might be good to mention is I'm not all that well versed in a lot of the android development tools. I'm not afraid to get my hands dirty though.
UPDATE (Thanks @NeoAcheron)
While this didn't work for me, this seems to work for some.
NeoAcheron shared the OTA update Google sends out to go from N to Marshmallow. YMMV, so best of luck to you!
If anyone has any other idea's to try, I'd be eternally grateful!
And remember kids, always enable OEM Unlocking like good boys and girls. (Settings -> Developer Options -> OEM Unlocking)
JPT62089 said:
Hey all! My Nexus 6P that has been on N Preview since day 2 is now stuck in a boot loop. It will usually just display the Google logo and then reboot. Sometimes it will get to the very beginning of the Android boot animation, but rarely.
Unfortunately, I didn't even know about the OEM Unucking setting until I've been trying to get my phone to boot again. I've tried using clearing cache, factory restore, adb sideload, and the flashing instructions Google provides. I've also tried using SkipSoft Android ToolKit with no avail as well. At this point I don't care if I end up with Marshmallow or back on N. I just want my phone working again xP
Does anyone have any ideas on how to restore my phone back to a working state? Thanks!
It also might be good to mention is I'm not all that well versed in a lot of the android development tools. I'm not afraid to get my hands dirty though.
Click to expand...
Click to collapse
If you can use fastboot fastboot system that should work out wipe userdata
jaythenut said:
If you can use fastboot fastboot system that should work out wipe userdata
Click to expand...
Click to collapse
Unfortunately, that didn't seem to work
Code:
> fastboot format userdata
Creating filesystem with parameters:
Size: 58688266240
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14328190
Block groups: 438
Reserved block group size: 1024
Created filesystem with 11/3588096 inodes and 271280/14328190 blocks
target reported max download size of 494927872 bytes
erasing 'userdata'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.013s
From the bootloader page on the phone...
Code:
Console: NULL
Battery OK
Device is LOCKED
Qfuse Status: ENABLED
Off-mode-charge: ENABLED
Download Mode: DISABLED.
Also worth a note...
Code:
> fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.005s
format from stock recovery ?
@JPT62089 You are not alone. My Nexus 6P is experiencing the same problem now. Signed up for the Dev Preview, phone behaved strangely today, reboot the device as per usual, and now its stuck on the boot screen...
I have tried applying the preview OTA update, and the Factory firmware reset, with the same results as you.
This is awesome considering I didn't unlock the bootloader, because I would have thought installing stock firmware would be possible.
This sucks... Lets hope Google releases a fix soon.
---------- Post added at 03:02 PM ---------- Previous post was at 03:01 PM ----------
csjneek said:
format from stock recovery ?
Click to expand...
Click to collapse
Unfortunately telling the device to reset to factory doesn't help either. Seems like the latest update broke the OS completely.
Wooohooo! Glad I'm not the only one It's unfortunate to have such a major issue as Preview 3 has been extremely stable for me up until yesterday...
NeoAcheron said:
@JPT62089 You are not alone. My Nexus 6P is experiencing the same problem now. Signed up for the Dev Preview, phone behaved strangely today, reboot the device as per usual, and now its stuck on the boot screen...
I have tried applying the preview OTA update, and the Factory firmware reset, with the same results as you.
This is awesome considering I didn't unlock the bootloader, because I would have thought installing stock firmware would be possible.
This sucks... Lets hope Google releases a fix soon.
---------- Post added at 03:02 PM ---------- Previous post was at 03:01 PM ----------
Unfortunately telling the device to reset to factory doesn't help either. Seems like the latest update broke the OS completely.
Click to expand...
Click to collapse
JPT62089 said:
Wooohooo! Glad I'm not the only one It's unfortunate to have such a major issue as Preview 3 has been extremely stable for me up until yesterday...
Click to expand...
Click to collapse
The Developer Preview was never meant to be signed up by any average user without prior knowledge on Android Development. If you sign up for the beta program, then it's always imperative that you have the bootloader previously unlocked, in case this exact situation happen. Did you actually think that you can just sign up for the Beta program and hope that it will not cause any problems?
ttminh1997 said:
The Developer Preview was never meant to be signed up by any average user without prior knowledge on Android Development. If you sign up for the beta program, then it's always imperative that you have the bootloader previously unlocked, in case this exact situation happen. Did you actually think that you can just sign up for the Beta program and hope that it will not cause any problems?
Click to expand...
Click to collapse
I am a software technical lead, knowing full well what the implications might be of running beta software on any piece of computing equipment. However, not at any point when I signed up was there a statement that I need to unlock the bootloader. Booloader unlocking in my mind (and on previous devices, like the HTC One) was only required when you wanted to deviate from the Stock firmware on the device. This is stock firmware, from Google.
I'm generally quite excited to test new things and I report my findings often with details about my experience and how the software behaved upto that point. But this has left a bad experience and I am not participating in the program anymore due to this.
Coming back now to say "oh you shoulda known" is not constructive. I am interested in a solution, because Google pretty much bricked my device without me touching it. The update (and the beta version since the announcement) applied seamlessly, and was working fine until I rebooted the device today.
---------- Post added at 04:18 PM ---------- Previous post was at 04:09 PM ----------
Found this: https://www.reddit.com/r/Nexus6P/comments/4jzp1o/soft_bricked_nexus_6p_with_locked_bootloader_need/
Might be possible to reproduce the special ZIP file to create a "special" downgrade OTA zip file to unbrick it, just to unlock the bootloader (at the very least).
I will have to look into it later, as I am still at work, and need to tend to some other tasks before getting back to this.
Will keep everyone updated...
NeoAcheron said:
I am a software technical lead, knowing full well what the implications might be of running beta software on any piece of computing equipment. However, not at any point when I signed up was there a statement that I need to unlock the bootloader. Booloader unlocking in my mind (and on previous devices, like the HTC One) was only required when you wanted to deviate from the Stock firmware on the device. This is stock firmware, from Google.
I'm generally quite excited to test new things and I report my findings often with details about my experience and how the software behaved upto that point. But this has left a bad experience and I am not participating in the program anymore due to this.
Coming back now to say "oh you shoulda known" is not constructive. I am interested in a solution, because Google pretty much bricked my device without me touching it. The update (and the beta version since the announcement) applied seamlessly, and was working fine until I rebooted the device today.
Click to expand...
Click to collapse
Bootloader unlocks are extremely important if you want to do any system-level mods (rooting, flashing custom recoveries, rom). Not only does it allow you to deviate from stock firmwares, like you said, but it also opens a gateway in which you can just flash a factory image and resolve any potential problems that may arise from otherwise stock Android or any custom roms you have. And stock firmwares, whether from Google, Samsung or even Apple, don't always mean good, or even stable. They may be stable 99% of the time, but eventually bugs and glitches are bound to happen; that's why they are continually updated, and that's why the 2011 Samsung ICS brick fiasco happened.
I did not mean to insult you or anything in the reply. That being said, yes, you really should have known before venturing into flashing firmwares without unlocking the bootloader and creating a backup first. As for solution, have you recently installed any apps that may not be compatible with N? Can you boot into safemode and disable some apps? If you can actually go into safemode, check allow oem unlock, unlock the bootloader and reflash factory image.
ttminh1997 said:
Bootloader unlocks are extremely important if you want to do any system-level mods (rooting, flashing custom recoveries, rom). Not only does it allow you to deviate from stock firmwares, like you said, but it also opens a gateway in which you can just flash a factory image and resolve any potential problems that may arise from otherwise stock Android or any custom roms you have. And stock firmwares, whether from Google, Samsung or even Apple, don't always mean good, or even stable. They may be stable 99% of the time, but eventually bugs and glitches are bound to happen; that's why they are continually updated, and that's why the 2011 Samsung ICS brick fiasco happened.
I did not mean to insult you or anything in the reply. That being said, yes, you really should have known before venturing into flashing firmwares without unlocking the bootloader and creating a backup first. As for solution, have you recently installed any apps that may not be compatible with N? Can you boot into safemode and disable some apps? If you can actually go into safemode, check allow oem unlock, unlock the bootloader and reflash factory image.
Click to expand...
Click to collapse
No offence taken, but I will make sure to unlock the device once I get it back up. Unfortunately the device doesn't boot at all, I cannot get it into safemode either (using the volume keys during boot).
What I do have though is the thread that is mentioned in the reddit post, I will need to check if this works before unleashing it here...
Will update when any developments made.
---------- Post added at 05:08 PM ---------- Previous post was at 04:46 PM ----------
HEY HEY! It worked!
So you need to get this file: https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
NeoAcheron said:
No offence taken, but I will make sure to unlock the device once I get it back up. Unfortunately the device doesn't boot at all, I cannot get it into safemode either (using the volume keys during boot).
What I do have though is the thread that is mentioned in the reddit post, I will need to check if this works before unleashing it here...
Will update when any developments made.
---------- Post added at 05:08 PM ---------- Previous post was at 04:46 PM ----------
HEY HEY! It worked!
So you need to get this file: https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Click to expand...
Click to collapse
Glad you could make your phone work again. Make sure that you unlock your bootloader before unlocking or testing any new roms.
NeoAcheron said:
No offence taken, but I will make sure to unlock the device once I get it back up. Unfortunately the device doesn't boot at all, I cannot get it into safemode either (using the volume keys during boot).
What I do have though is the thread that is mentioned in the reddit post, I will need to check if this works before unleashing it here...
Will update when any developments made.
---------- Post added at 05:08 PM ---------- Previous post was at 04:46 PM ----------
HEY HEY! It worked!
So you need to get this file: https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Click to expand...
Click to collapse
Did you just flash every .img file? There does not appear to be any other way.
NeoAcheron said:
HEY HEY! It worked!
So you need to get this file: https://android.googleapis.com/pack.../53bd5f816ce0706903d1a69d50bca6cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Click to expand...
Click to collapse
Thanks for posting this NeoAcheron, I sideloaded this yesterday and was actually able to perform an adb sideload this time (found a handy tip... Once the phone is waiting for adb commands, unplug and plug it back into the computer as it may not already see it)
It didn't seem to immediately help, unfortunately. I let it bootloop for a while before giving up and then tried again last night. I had left it on my desk bootlooping for a while and then all of a sudden it was booted and waiting for me to set it up. I quickly did so and immediate went to settings to enable the OEM Flashing setting and just as I did so it went to the red warning screen and then proceeded to bootloop again... I tried to run fastboot flashing unlock again in hopes that my changing the setting took before it bootlooped, but still got the FAILED message. I've since tried every which way of factory resetting, sideloading again, leaving it for hours in bootloop, and still nothing
Anyone have any more ideas?
Maybe a dumb question...but
ttminh1997 said:
Glad you could make your phone work again. Make sure that you unlock your bootloader before unlocking or testing any new roms.
Click to expand...
Click to collapse
Deleted
---------- Post added at 10:19 PM ---------- Previous post was at 09:59 PM ----------
So you need to get this file: https://android.googleapis.com/packa...cd4f52b800.zip
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Can I flash this ( https://android.googleapis.com/packa...cd4f52b800.zip) in TWRP ? I am running N5...I wanted to go back to Marshmallow to be able to flash some roms.
Thanks
NeoAcheron said:
No offence taken, but I will make sure to unlock the device once I get it back up. Unfortunately the device doesn't boot at all, I cannot get it into safemode either (using the volume keys during boot).
What I do have though is the thread that is mentioned in the reddit post, I will need to check if this works before unleashing it here...
Will update when any developments made.
---------- Post added at 05:08 PM ---------- Previous post was at 04:46 PM ----------
HEY HEY! It worked!
So you need to get this file:
Get into the recovery mode of the device to do ADB sideload and update using that zip file. That zip file is the file Google will send to your device when you opt out of the Beta program, to effectively downgrade you back to Marshmallow.
Once you reboot, the device will reboot itself twice and come back as a stock Marshmallow device.
Please note that all your stuff will still be gone... The device will be fully factory reset after this.
I hope this helps you too!
Happy flashing, and happy testing!
Click to expand...
Click to collapse
Hey NeoAcheron. I'm having a similar issue. After years of flashing custom ROMs, I joined the Beta programme so I could do things 'properly' on my Nexus 6P. Been working fine for a fortnight, until today when it randomly froze, crashed, and is now stuck in a bootloop on the 'Google' screen. I can get into the bootloader menu, but every option I select takes me back to the 'Google' bootloop screen. I can't even get my PC to recognise it as a device so I can't sideload a workaround.
Any ideas, or is it basically useless? Google have offered me a replacement phone, but I'd like to try and rescue this one first
Thanks in advance
kristianj79 said:
Hey NeoAcheron. I'm having a similar issue. After years of flashing custom ROMs, I joined the Beta programme so I could do things 'properly' on my Nexus 6P. Been working fine for a fortnight, until today when it randomly froze, crashed, and is now stuck in a bootloop on the 'Google' screen. I can get into the bootloader menu, but every option I select takes me back to the 'Google' bootloop screen. I can't even get my PC to recognise it as a device so I can't sideload a workaround.
Any ideas, or is it basically useless? Google have offered me a replacement phone, but I'd like to try and rescue this one first
Thanks in advance
Click to expand...
Click to collapse
The first thing you could try wiping cache from the stock recovery, and see if it works. Do you have any data on the device that you desperately wanna save, and can't loose?
DJBhardwaj said:
The first thing you could try wiping cache from the stock recovery, and see if it works. Do you have any data on the device that you desperately wanna save, and can't loose?
Click to expand...
Click to collapse
Thanks DJBhardwaj - I'm all backed up. I just wanted to see if I could fix it myself because I'd rather not be without a decent phone for a week. I'm no expert and I usually need my hand holding, but I've managed to get out of a few scrapes in the past with custom ROMs and bootloops!
My issue is that I can't even access stock recovery. I can get into the fastboot menu using the hardware keys but selecting any ption from there throws the device into a bootloop again. I also can't get my PC to see the device and wrestle beck control using adb commands, so I'm a bit stuck :/
kristianj79 said:
Thanks DJBhardwaj - I'm all backed up. I just wanted to see if I could fix it myself because I'd rather not be without a decent phone for a week. I'm no expert and I usually need my hand holding, but I've managed to get out of a few scrapes in the past with custom ROMs and bootloops!
My issue is that I can't even access stock recovery. I can get into the fastboot menu using the hardware keys but selecting any ption from there throws the device into a bootloop again. I also can't get my PC to see the device and wrestle beck control using adb commands, so I'm a bit stuck :/
Click to expand...
Click to collapse
Have you tried on any other Windows or Mac PC? If you can get it to detect, then the problem would be pretty easily solved. To confirm if your device is being recognized, type in the following command in CMD/Terminal:
Code:
fastboot devices
Make: Motorola
Model: Moto X Pure Edition (Style) XT1575
OS: 6.0 Marshmallow
Rooted: yes
Bootloader: you'd better believe it
Hello,
I am having a little trouble with the calling function on my moto x pure edition XT1575.
Problem:
The first time i loaded the os, my phone couldnt boot. it was stuck on the bootloader screen for days until i found a file that i ran in my recovery called SR3 SuperSU v2.78 it helped my phone get out of the bootloader page and i was finally able to use my phone and everything was great! until somebody called.
The phone is connected to my cell network and the phone will ring and i can call out. But, when i hit the phone but it does not display the call window. sometimes i dont realize i am calling somebody until i hear a small "Hello?". while i am on the call with the other person I am on the home screen and can not hang up the call. When others call me my phone rings but it only displays the home screen and it will not allow me to answer the call. All i can do is wait for the phone to stop ringing and hit the call button to call them back. I cannot call my voicemail as there is no keypad. only the home screen and yes i tend to pull up apps with my face.
The only solution i have to this problem is to connect a bluetooth device to it. I have been wearing my Gear S2 3G around so i could make and answer calls minus the use of the voice functionality. Voice commands do not work on my smartwatch anymore for some reason. I have to manually turn the dial to select the contact i would like to call. I can still add phone numbers on the phone (this function didnt work before until i installed another os then reinstalled it). but quite frankly, there is a time i would like to be able to pick up my phone and just answer an incoming call rather then fiddling around with this watch all the time. trying to keep it charged.
What I have tried:
I have tried a number of things. installing a new boot img, new recovery, downloading a new kernel. loading all new img folders into the command prompt. Then my laptop was acting up and i had to reinstall windows to fix it. A friend of mine suggested I should work on getting back my original os and reload some working folders . Ok, so i followed the steps and noticed my command prompt now will not read my phone to load the new img's and i noticed the drivers are not installed. ok, im working with a new computer basically and it doesnt quite recognize my phone. so i installed motorola device manager. adb, usb and the other driver has installed correctly, cool. I tried the casual test on the command prompt "adb devices" it didnt recognize it...ok? so i tried to type in the recovery img like before. nothing. tried to boot up the bootloader. nothing. what is going on here? i have all the drivers and the files waiting to go into the phone. I even restarted the computer to finalize the changes i made to the computer. nothing i have tried works.
what am i going to try next?
clockworkmod... if this doesnt work then i dont know what will.
If there are any suggestions out there any anyone that can help me with the problems that i am having with my phone please reply to this post. Thank you for any help that is posted up here. I will try to comment on what method has worked for me so that whoever has this problem will be able to fix this very simple functionality for a phone. I mean what is the point of carrying around a phone that cannot make or receive phone calls? sure its rooted and thats all cool and fancy. but its laughable that my phone cannot handle what a phone is supposed to do. At this point i might be carrying around 2 phones with me. its ridiculous lol. A phone that cannot call people. I have a small tablet. its not even a phone anymore lol. its a fancy tablet. please comment below, thank you guys!
(update)
I just followed the instructions on this link (http://forum.xda-developers.com/moto-x-style/general/xt1572-mm-twrp-root-xposed-t3276792) from another member of this site. I restored my phone to the way it was when i bought it. but i dont have any connection through my data nor can i connect to wifi. will update again when i find a fix.
Tacoman64 said:
Make: Motorola
Model: Moto X Pure Edition (Style) XT1575
OS: 6.0 Marshmallow
Rooted: yes
Bootloader: you'd better believe it
Hello,
I am having a little trouble with the calling function on my moto x pure edition XT1575.
Problem:
The first time i loaded the os, my phone couldnt boot. it was stuck on the bootloader screen for days until i found a file that i ran in my recovery called SR3 SuperSU v2.78 it helped my phone get out of the bootloader page and i was finally able to use my phone and everything was great! until somebody called.
The phone is connected to my cell network and the phone will ring and i can call out. But, when i hit the phone but it does not display the call window. sometimes i dont realize i am calling somebody until i hear a small "Hello?". while i am on the call with the other person I am on the home screen and can not hang up the call. When others call me my phone rings but it only displays the home screen and it will not allow me to answer the call. All i can do is wait for the phone to stop ringing and hit the call button to call them back. I cannot call my voicemail as there is no keypad. only the home screen and yes i tend to pull up apps with my face.
The only solution i have to this problem is to connect a bluetooth device to it. I have been wearing my Gear S2 3G around so i could make and answer calls minus the use of the voice functionality. Voice commands do not work on my smartwatch anymore for some reason. I have to manually turn the dial to select the contact i would like to call. I can still add phone numbers on the phone (this function didnt work before until i installed another os then reinstalled it). but quite frankly, there is a time i would like to be able to pick up my phone and just answer an incoming call rather then fiddling around with this watch all the time. trying to keep it charged.
What I have tried:
I have tried a number of things. installing a new boot img, new recovery, downloading a new kernel. loading all new img folders into the command prompt. Then my laptop was acting up and i had to reinstall windows to fix it. A friend of mine suggested I should work on getting back my original os and reload some working folders . Ok, so i followed the steps and noticed my command prompt now will not read my phone to load the new img's and i noticed the drivers are not installed. ok, im working with a new computer basically and it doesnt quite recognize my phone. so i installed motorola device manager. adb, usb and the other driver has installed correctly, cool. I tried the casual test on the command prompt "adb devices" it didnt recognize it...ok? so i tried to type in the recovery img like before. nothing. tried to boot up the bootloader. nothing. what is going on here? i have all the drivers and the files waiting to go into the phone. I even restarted the computer to finalize the changes i made to the computer. nothing i have tried works.
what am i going to try next?
clockworkmod... if this doesnt work then i dont know what will.
If there are any suggestions out there any anyone that can help me with the problems that i am having with my phone please reply to this post. Thank you for any help that is posted up here. I will try to comment on what method has worked for me so that whoever has this problem will be able to fix this very simple functionality for a phone. I mean what is the point of carrying around a phone that cannot make or receive phone calls? sure its rooted and thats all cool and fancy. but its laughable that my phone cannot handle what a phone is supposed to do. At this point i might be carrying around 2 phones with me. its ridiculous lol. A phone that cannot call people. I have a small tablet. its not even a phone anymore lol. its a fancy tablet. please comment below, thank you guys!
Click to expand...
Click to collapse
The problem here is we don't know your phones state and what files you have used and what you have done...
To be honest, at this point I would do a full reflash back to pure stock. The instruction link is in my signature (you don't have to lock, that is optional). Once you are in a known good state, then maybe you can root the right way.
Found the problem (no solution yet)
it seems all of my files are running fine when i enter them into the command prompt but the only one that is not working is the gpt.bin.
(fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.369s)
I didnt just copy and paste the name. i manually typed it but it just doesnt work for some reason. hope this information helps.
Tacoman64 said:
it seems all of my files are running fine when i enter them into the command prompt but the only one that is not working is the gpt.bin.
(fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.369s)
I didnt just copy and paste the name. i manually typed it but it just doesnt work for some reason. hope this information helps.
Click to expand...
Click to collapse
Yup... As I suspected... "Preflash validation failed" means you are attempting to flash an older Android version than you have already installed. You need to use a newer/newest firmware version.
(update)
I have successfully unrooted my device. I have typed all the file commands in the command prompt and the only error i got was a preflash validation failed error. I read a few forums to make sure that this was not going to brick my device and found out. Because i am not upgrading my os. the gpt.bin file really isnt necessary. I suppose it would be good to try to code it in anyways but if it fails then it should be fine.
THE PROBLEM:
Was another file wasnt installing correctly. I think the first time i typed in Flash modem NON-HLOS.bin It must have failed before but i didnt see it. It failed again on me but i sent the command again and it successfully installed (huh... weird).
In Conclusion:
So it goes to show you.
Rule 1: OPEN command prompt in the same folder you have your files extracted on by holding shift+right click. It should have an option to open command prompt. (if you've tried it multiple times then put the files in a new folder)
Rule 2: CHECK YOUR COMMANDS! see if they have installed correctly. gpt.bin file doesnt mean anything if you're not upgrading your original os.
Rule 3reverts to rule 2) CHECK your NON-HLOS.bin file in your commands list to see if it downloads correctly to you command prompt.
Rule 4:NO FAILURES. NONE of these other files should say failed and if they do. RE-TYPE them in. If that doesnt work. then download another file. you might just either have a broken file, it didnt download correctly or it might just be the wrong one. find the right file for your model number of phone!
This is to all those who dont know much about computers.
Rule 5: MISSING FILES. If there are any missing files then check your files. the failures could be due to not extracting your files, not downloading the proper files, and simply typing them incorrectly. ex. fastboot flash logo "logo.bin". if your logo name is not "logo.bin" and you just copy pasted it. the file will fail. your file could say something different like "XT1575-logo-new-9-14-15.bin". So instead, type in "fastboot flash logo XT1575-logo-new-9-14-15.bin" it should successfully download. If it doesnt. revert back to the previous rules.
NOW: On to Re-Rooting my device.
Tacoman64 said:
I have successfully unrooted my device. I have typed all the file commands in the command prompt and the only error i got was a preflash validation failed error. I read a few forums to make sure that this was not going to brick my device and found out. Because i am not upgrading my os. the gpt.bin file really isnt necessary. I suppose it would be good to try to code it in anyways but if it fails then it should be fine.
THE PROBLEM:
Was another file wasnt installing correctly. I think the first time i typed in Flash modem NON-HLOS.bin It must have failed before but i didnt see it. It failed again on me but i sent the command again and it successfully installed (huh... weird).
In Conclusion:
So it goes to show you.
Rule 1: OPEN command prompt in the same folder you have your files extracted on by holding shift+right click. It should have an option to open command prompt. (if you've tried it multiple times then put the files in a new folder)
Rule 2: CHECK YOUR COMMANDS! see if they have installed correctly. gpt.bin file doesnt mean anything if you're not upgrading your original os.
Rule 3reverts to rule 2) CHECK your NON-HLOS.bin file in your commands list to see if it downloads correctly to you command prompt.
Rule 4:NO FAILURES. NONE of these other files should say failed and if they do. RE-TYPE them in. If that doesnt work. then download another file. you might just either have a broken file, it didnt download correctly or it might just be the wrong one. find the right file for your model number of phone!
This is to all those who dont know much about computers.
Rule 5: MISSING FILES. If there are any missing files then check your files. the failures could be due to not extracting your files, not downloading the proper files, and simply typing them incorrectly. ex. fastboot flash logo "logo.bin". if your logo name is not "logo.bin" and you just copy pasted it. the file will fail. your file could say something different like "XT1575-logo-new-9-14-15.bin". So instead, type in "fastboot flash logo XT1575-logo-new-9-14-15.bin" it should successfully download. If it doesnt. revert back to the previous rules.
NOW: On to Re-Rooting my device.
Click to expand...
Click to collapse
Actually, your experience is not weird... it is not uncommon for NON-HLOS to fail the first time, subsequent attempts usually work... no idea why, some people say to use the erase modemst# commends first, others don't...
You are still in a mixed environment, the fact your are getting a preflash validation error means your partition table is newer than the one you are attempting to flash, this your device is out of sync (all your partitions don't match version wise). Although this condition itself will not result in bricking, taking an OTA later could cause that (we don't know, it could potentially). Something is definitely amiss, otherwise the gpt.bin would flash and go fine, but the phone KNOWS the partition table you are attempting to flash is older than the one on the device, that should tell you something. If you are going to flash a custom ROM, oh well, but if you are going to stay stock you should flash the latest 18-4 firmware image completely.
my intentions are to root my phone. I was just repairing my call functionality so i could receive phone calls. my phone works now. i can call people and i think receive calls because the call page pulls up when i call out. i dont know if i could receive calls because my phone is currently not activated. (not a phone issue, just didnt pay the bill) when my phone was activated with the root. the phone would ring but no call came up and when i called out the phone page would not be there. so i couldnt hang up a call or access the number pad while in a call for automated systems. now i can so i think that part of it is fixed. I am currently following one of your how to pages but it doesnt explain how to install twrp on the phone. it only says to go to advanced mode of what i believe to be the advanced mode on the recovery menu and put in that command before installing supersu. im still looking for command prompts on how to reinstall my recovery and trying to better understand what advanced setting you are trying to point out.
ITS ALIVE!!!
My phone is now FIXED and ROOTED! thanks to all of you wonderful people out there who helped me! posting up the wonderful posts that include all of the files, data and commands i needed to make this possible. Thank you all again! You guys are the best. now all there is to do is to put some mods on here and have fun with my new toy
acejavelin said:
Actually, your experience is not weird... it is not uncommon for NON-HLOS to fail the first time, subsequent attempts usually work... no idea why, some people say to use the erase modemst# commends first, others don't...
You are still in a mixed environment, the fact your are getting a preflash validation error means your partition table is newer than the one you are attempting to flash, this your device is out of sync (all your partitions don't match version wise). Although this condition itself will not result in bricking, taking an OTA later could cause that (we don't know, it could potentially). Something is definitely amiss, otherwise the gpt.bin would flash and go fine, but the phone KNOWS the partition table you are attempting to flash is older than the one on the device, that should tell you something. If you are going to flash a custom ROM, oh well, but if you are going to stay stock you should flash the latest 18-4 firmware image completely.
Click to expand...
Click to collapse
I made a how to explaining step by step. how to properly root the moto x pure and or all 6.0 motorola's If you would like to check out, make corrections to my post feel free, and or if you have any suggestions on how to make it better please let me know. http://forum.xda-developers.com/moto-x-style/general/how-to-unlock-root-moto-x-pure-style-t3504263
Tacoman64 said:
I made a how to explaining step by step. how to properly root the moto x pure and or all 6.0 motorola's If you would like to check out, make corrections to my post feel free, and or if you have any suggestions on how to make it better please let me know. http://forum.xda-developers.com/moto-x-style/general/how-to-unlock-root-moto-x-pure-style-t3504263
Click to expand...
Click to collapse
It's funny because my guide went live the other day, just haven't added it to my sig yet... http://forum.xda-developers.com/moto-x-style/general/guide-how-to-root-pure-style-t3503958
acejavelin said:
It's funny because my guide went live the other day, just haven't added it to my sig yet... http://forum.xda-developers.com/moto-x-style/general/guide-how-to-root-pure-style-t3503958
Click to expand...
Click to collapse
I seen that that's where I got the code I was missing the first time around. I am about to create another post and attach that link to it on here too. So if someone were to mess up their phone by skipping or not checking the command prompt then they have a plan B. I'll be the simple 1 stop post for every issue on Motorola like Walmart lol. I think it will get cluttered though.
Hi,
Before I start to flash things on my OnePlus 5 I was wondering what the method is to get it back to stock with my previous phone being a Samsung S6 not sure about the process used with phones outside of the Samsung ecosystem. Any help is appreciated.
Thank You
dasbiz said:
Hi,
Before I start to flash things on my OnePlus 5 I was wondering what the method is to get it back to stock with my previous phone being a Samsung S6 not sure about the process used with phones outside of the Samsung ecosystem. Any help is appreciated.
Thank You
Click to expand...
Click to collapse
Try the same on YouTube
hariharansriram said:
Try the same on YouTube
Click to expand...
Click to collapse
Helpful. I would love to watch EpicPhonesHD with jumpcuts everywhere instead of textual instruction from someone who has been modding this specific phone and has experienced any problems specific to this phone for returning to stock that the youtubers don't mention (Think Samsung hidden.img failures) /s
https://youtu.be/SPwHxSZ281o
Watch this I've made this and if you have any problems just comment it
dasbiz said:
Hi,
Before I start to flash things on my OnePlus 5 I was wondering what the method is to get it back to stock with my previous phone being a Samsung S6 not sure about the process used with phones outside of the Samsung ecosystem. Any help is appreciated.
Thank You
Click to expand...
Click to collapse
Download the latest oos software. Flash via whatever recovery you have installed. After flash, you could be back to stock rom with stock recovery. At this point you could also choose to relock bootloader.
I'm not sure if the same procedure works on multi-rom
n0013z said:
Download the latest oos software. Flash via whatever recovery you have installed. After flash, you could be back to stock rom with stock recovery. At this point you could also choose to relock bootloader.
I'm not sure if the same procedure works on multi-rom
Click to expand...
Click to collapse
I reflashed recovery, reinstalled all software and still get this error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
...
FAILED (remote: Flashing Lock is not allowed
)
finished. total time: 0.016s