Related
As the title says I'm getting stuck on:
sending 'bootloader' (2100 KB)
when trying to flash a stock image to return the tablet to stock. the tablet is basically dead, i can get into the bootloader, which freezes anytime i try to flash the stock image, and i can't boot into recovery or android itself.
i am desperate for help right now. was trying to sell this today and now i feel like an asshole since i now soft bricked it on the day he was suppose to buy it. I've done factory restores on 2 GNex, a G4 and the 2013 N7 and NEVER had any issues like this. hell never had any issues of any kind with those devices.
*edit* well i finally got it to flash, only took 20 tries. don't know wtf that was all about but glad i'm getting rid of this thing.
neok44 said:
As the title says I'm getting stuck on:
sending 'bootloader' (2100 KB)
when trying to flash a stock image to return the tablet to stock. the tablet is basically dead, i can get into the bootloader, which freezes anytime i try to flash the stock image, and i can't boot into recovery or android itself.
i am desperate for help right now. was trying to sell this today and now i feel like an asshole since i now soft bricked it on the day he was suppose to buy it. I've done factory restores on 2 GNex, a G4 and the 2013 N7 and NEVER had any issues like this. hell never had any issues of any kind with those devices.
*edit* well i finally got it to flash, only took 20 tries. don't know wtf that was all about but glad i'm getting rid of this thing.
Click to expand...
Click to collapse
Well, it just happened to me too and while in fastboot, well mine was in fastboot while this was happening, I just used to volumn button to get to boot to recovery. Once in recovery I had it reboot to the bootloader. After I was back in fastboot and started the install again, it worked.
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!
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.
I could really use some help. I'm at the edge of my patience and have tried pretty much everything I can think of. I say near brick cause a phone without WiFi and BT is kinda useless.
Here's the back story. I had my previous xt1575 stolen. I purchased a used one off ebay. I received it, only to find it was bootloader unlocked, rooted. Not an issue in theory but I wasn't told that. Ok, upon trying the phone it worked but the battery would last 3 hours, it would have random reboots and would run so hot i could hardly hold the phone. I figured it was a faulty kernel. I flashed a new kernel and stock rom. Battery life went back to almost perfect but was off by about 20%. The random reboots were still an issue, but everything else seemed to work. A randomly rebooting phone is far from ideal. I figured I'd keep trying. Maybe it was a software issue. I would get random results with different roms. And the rebooting really seemed to occur when I had all my apps downloaded. So, I decided to run to flash again and run lean and see if with just the default apps whether it would reboot. After the flash, I waited a few hours, then BT and WiFi just stopped working. No go. The actual toggles revert to off position essentially immediately and neither turn on. I've since tried FDRs, different roms, different kernels, no luck. No idea what to do at this point. It could be hardware, obviously. It could be that the wifi chip was faulty and causing the overheating/battery drain from before, and finally after running so hot that one day before I flashed, it just did final damage to the chip that came to pass 3 days later. I don't know. It's possible but i somehow feel like it's a SW issue. I could send it back but it's complicated and i would really prefer to see if I can get this resolved. I've reflashed the modem bin files of stock roms, etc. Another issue i get often is when i try flashing, I get the writing 'boot'... (bootloader) Preflash validation failed FAILED (remote failure) and other such failures. Additionally, TWRP often just disappears. Aside from that, the OS, usually runs fine. I can't download apps obviously due to no WiFi, but everything else seems fine and I haven't had any reboots since the wifi/bt stopped working. I don't know if it's a partition issue, or hardware or what. I could use some advice. I'm at the limit of my patience and my knowledge here.
Let me know what you guys need and thanks ahead of time for your help.
vijn said:
I could really use some help. I'm at the edge of my patience and have tried pretty much everything I can think of. I say near brick cause a phone without WiFi and BT is kinda useless.
Here's the back story. I had my previous xt1575 stolen. I purchased a used one off ebay. I received it, only to find it was bootloader unlocked, rooted. Not an issue in theory but I wasn't told that. Ok, upon trying the phone it worked but the battery would last 3 hours, it would have random reboots and would run so hot i could hardly hold the phone. I figured it was a faulty kernel. I flashed a new kernel and stock rom. Battery life went back to almost perfect but was off by about 20%. The random reboots were still an issue, but everything else seemed to work. A randomly rebooting phone is far from ideal. I figured I'd keep trying. Maybe it was a software issue. I would get random results with different roms. And the rebooting really seemed to occur when I had all my apps downloaded. So, I decided to run to flash again and run lean and see if with just the default apps whether it would reboot. After the flash, I waited a few hours, then BT and WiFi just stopped working. No go. The actual toggles revert to off position essentially immediately and neither turn on. I've since tried FDRs, different roms, different kernels, no luck. No idea what to do at this point. It could be hardware, obviously. It could be that the wifi chip was faulty and causing the overheating/battery drain from before, and finally after running so hot that one day before I flashed, it just did final damage to the chip that came to pass 3 days later. I don't know. It's possible but i somehow feel like it's a SW issue. I could send it back but it's complicated and i would really prefer to see if I can get this resolved. I've reflashed the modem bin files of stock roms, etc. Another issue i get often is when i try flashing, I get the writing 'boot'... (bootloader) Preflash validation failed FAILED (remote failure) and other such failures. Additionally, TWRP often just disappears. Aside from that, the OS, usually runs fine. I can't download apps obviously due to no WiFi, but everything else seems fine and I haven't had any reboots since the wifi/bt stopped working. I don't know if it's a partition issue, or hardware or what. I could use some advice. I'm at the limit of my patience and my knowledge here.
Let me know what you guys need and thanks ahead of time for your help.
Click to expand...
Click to collapse
What image are you using? Make sure you are using MPH24.49-18-4 (the -4 is important and newer than the one that ends in 18-18 on Moto's site) with the May 1, 2016, security update from here and flashing each step manually using this post's instructions.
I could explain most of the issues individually you are seeing, unless you are already using the specific version I referenced, since they all seem to relate to improper or old version flashing, but it doesn't really matter because the answer to all of them is the same... Reflash the proper version making sure each steps results in an OKAY.
If I am way off base, then it is likely a hardware problem.
acejavelin said:
What image are you using? Make sure you are using MPH24.49-18-4 (the -4 is important and newer than the one that ends in 18-18 on Moto's site) with the May 1, 2016, security update from here and flashing each step manually using this post's instructions.
I could explain most of the issues individually you are seeing, unless you are already using the specific version I referenced, since they all seem to relate to improper or old version flashing, but it doesn't really matter because the answer to all of them is the same... Reflash the proper version making sure each steps results in an OKAY.
If I am way off base, then it is likely a hardware problem.
Click to expand...
Click to collapse
Well, first off thanks a lot for your help. I had installed that particular version, though it wasn't the one currently installed. But I followed all the instructions and steps and got success writes for all and it booted up but didn't recognize any wifi networks and i tried to toggle on the wifi and same as before. Nothing happens. Wifi simply won't turn on. Same for bluetooth. Looking more like a HW problem isn't it?
vijn said:
Well, first off thanks a lot for your help. I had installed that particular version, though it wasn't the one currently installed. But I followed all the instructions and steps and got success writes for all and it booted up but didn't recognize any wifi networks and i tried to toggle on the wifi and same as before. Nothing happens. Wifi simply won't turn on. Same for bluetooth. Looking more like a HW problem isn't it?
Click to expand...
Click to collapse
I mean I know HW can die at any time, and maybe it was already dying from before which caused the initial issues when I got the phone, but I just have this sneaking suspicion that it's not HW related. I can't shake that feeling. But every SW based solution I try doesn't seem to do the trick.
acejavelin said:
I could explain most of the issues individually you are seeing, unless you are already using the specific version I referenced, since they all seem to relate to improper or old version flashing, but it doesn't really matter because the answer to all of them is the same... Reflash the proper version making sure each steps results in an OKAY.
Click to expand...
Click to collapse
Actually when u have a chance, I'd love this. Been rooting, modding my phones for years but I've never gone past a certain level of understanding. I'm not by nature a code guy though I have enjoyed playing around with custom roms and stuff. Anyway, ya, no pressure and my priority is to see if I can get this fixed or should just send it back, but if you do have time afterwards, would love to know what the deal is.
Still hoping someone can help me out with this. Any ideas? I'd really appreciate it.
vijn said:
Still hoping someone can help me out with this. Any ideas? I'd really appreciate it.
Click to expand...
Click to collapse
us the restore to stock tool, then install twrp and flash trupure and without booting flash the updated modem
unitz0mbie said:
us the restore to stock tool, then install twrp and flash trupure and without booting flash the updated modem
Click to expand...
Click to collapse
Hmm. Definitely willing to try that. You wouldn't happen to have links to Trupure and the updated modem would you? And the Restore to stock tool is this I assume: CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162. Not sure what Trupure is. It's a custom ROM?
vijn said:
Hmm. Definitely willing to try that. You wouldn't happen to have links to Trupure and the updated modem would you? And the Restore to stock tool is this I assume: CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162. Not sure what Trupure is. It's a custom ROM?
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155
scroll down u will find a link for a modem, and u just flash it aswell
trick is to to flash the rom and modem without booting. if u only boot rom u will no wifi/bt etc
unitz0mbie said:
https://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155
scroll down u will find a link for a modem, and u just flash it aswell
trick is to to flash the rom and modem without booting. if u only boot rom u will no wifi/bt etc
Click to expand...
Click to collapse
That's so weird. Never heard of that before but will definitely try it. Thanks a lot.
unitz0mbie said:
https://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155
scroll down u will find a link for a modem, and u just flash it aswell
trick is to to flash the rom and modem without booting. if u only boot rom u will no wifi/bt etc
Click to expand...
Click to collapse
And Trupure? That's a ROM I assume. Know where I can find that? I could research it obviously, but figured there's likely a couple different versions of it. Would rather get the one you recommend. - nevermind. I see that the link you provided was for trupure. Thanks a lot. Will let you know how it goes.
unitz0mbie said:
https://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155
scroll down u will find a link for a modem, and u just flash it aswell
trick is to to flash the rom and modem without booting. if u only boot rom u will no wifi/bt etc
Click to expand...
Click to collapse
The thing is, I'm on 6.0. Secondly my TWRP keeps getting deleted. And I just tried flashing twrp again and now I'm getting this: sending 'recovery' (34434 KB)...
OKAY [ 0.753s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.773s
Not sure how to proceed. Not much I can do without a working recovery. Any ideas?
vijn said:
That's so weird. Never heard of that before but will definitely try it. Thanks a lot.
Click to expand...
Click to collapse
no problem, if u still have no bt u can find the specific files u need to flash
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
vijn said:
The thing is, I'm on 6.0. Secondly my TWRP keeps getting deleted. And I just tried flashing twrp again and now I'm getting this: sending 'recovery' (34434 KB)...
OKAY [ 0.753s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.773s
Not sure how to proceed. Not much I can do without a working recovery. Any ideas?
Click to expand...
Click to collapse
what version of twrp are u using
---------- Post added at 11:43 PM ---------- Previous post was at 11:41 PM ----------
vijn said:
The thing is, I'm on 6.0. Secondly my TWRP keeps getting deleted. And I just tried flashing twrp again and now I'm getting this: sending 'recovery' (34434 KB)...
OKAY [ 0.753s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.773s
Not sure how to proceed. Not much I can do without a working recovery. Any ideas?
Click to expand...
Click to collapse
try using the restore to stock tool, it will remove twrp
and then u can reflash twrp
unitz0mbie said:
no problem, if u still have no bt u can find the specific files u need to flash
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
what version of twrp are u using
Click to expand...
Click to collapse
3.0.2 i think. can't really check but i think that's what i remember from the last time i loaded it
Here's the thing, there seems to be a consistent issue writing to the boot partition and TWRP never lasts. I don't know all that much about this but I feel as though there's a part of the software that is constantly being deleted/overwritten and that may explain why the modem never stays and twrp never stays. Does that make any sense?
The return to stock tool gives the following 2 errors:
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.378s
and
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 149.569s
Obviously the second error is the end of the process. Can't go any further if it can't write the system. Super confused. Every time I install a new ROM another issue pops up.
unitz0mbie said:
no problem, if u still have no bt u can find the specific files u need to flash
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
what version of twrp are u using
---------- Post added at 11:43 PM ---------- Previous post was at 11:41 PM ----------
try using the restore to stock tool, it will remove twrp
and then u can reflash twrp
Click to expand...
Click to collapse
Managed to get the restore to stock working. Restarted bootloader. Tried to flash twrp, and same error: writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.779s
vijn said:
Managed to get the restore to stock working. Restarted bootloader. Tried to flash twrp, and same error: writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.779s
Click to expand...
Click to collapse
is your bootloader locked?
unitz0mbie said:
is your bootloader locked?
Click to expand...
Click to collapse
to be honest, I don't even know any more. I've locked and unlocked it a bunch of times. Some tools I've used automatically lock or unlock it. At this point i just tried to unlock is using my key and got the following error: error: Command length (142) exceeds maximum size (64). So, ya, i have no idea what's going on. The bootloader page says device:locked, but the prebootloader page says bootloader unlocked.
unitz0mbie said:
is your bootloader locked?
Click to expand...
Click to collapse
I have to step away for a couple hours. I will be back. But regardless of how this goes, I just wanted to say thanks for trying to help with this stuff. I've never had so many issues with a phone before. My previous ones would occasionally give me some headaches, but not to this extent. Anyway, hopefully you'll still be around when i get back or will have some other recommendations.
sounds like your BL is locked man.
TWRP thread here
https://forum.xda-developers.com/u11/development/recovery-twrp-touch-recovery-t3617028
I clone the repo from @Captain_Throwback and built TWRP recovery for U11 (ocndugl).
It can work well but have some issue with OTG function and touch not work while boot into TWRP (press power button and unlock lockscreen could get touch back to work).
#built with ocndugl kernel, it may not boot on ocnuhl or ocndtwl variant
#version 1
twrp-3.1.1-0-ocn_TEST.img
https://www.androidfilehost.com/?fid=817550096634770756
#version 2
I fix the external_sd and otg issues but USB function still not work.
twrp-3.1.1-0-ocn_TEST_2.img
https://www.androidfilehost.com/?fid=817550096634772885
Well, when you create device files without a device and can't test what you build, you end up with a TWRP that isn't fully functional...
If I'm able to get one, I will certainly do my best to work out any of the issues and make sure the device gets official TWRP support. Thanks for testing my device tree.
Captain_Throwback said:
Well, when you create device files without a device and can't test what you build, you end up with a TWRP that isn't fully functional...
If I'm able to get one, I will certainly do my best to work out any of the issues and make sure the device gets official TWRP support. Thanks for testing my device tree.
Click to expand...
Click to collapse
Plz read the thread carefully. He lives in Taiwan and U11 is selling there for a couple of days, there are many user reviews on TW forums already. Next place comes to Hong Kong around 5/6th June and I pre-ordered an U11 6+128GB. Finger crossed.
TheEndHK said:
Plz read the thread carefully. He lives in Taiwan and U11 is selling there for a couple of days, there are many user reviews on TW forums already. Next place comes to Hong Kong around 5/6th June and I pre-ordered an U11 6+128GB. Finger crossed.
Click to expand...
Click to collapse
well, there is no information about that he lives in taiwan or not. so no need to read it carefully
Captain_Throwback said:
Well, when you create device files without a device and can't test what you build, you end up with a TWRP that isn't fully functional...
If I'm able to get one, I will certainly do my best to work out any of the issues and make sure the device gets official TWRP support. Thanks for testing my device tree.
Click to expand...
Click to collapse
Hope you could get one and maintain this device.
I'm still a noob with this :laugh:
Sent from my HTC One M9 using XDA Labs
DeeZZ_NuuZZ said:
well, there is no information about that he lives in taiwan or not. so no need to read it carefully
Click to expand...
Click to collapse
His home country stated Taiwan
Sent from my LG-D855 using XDA Free mobile app
TheEndHK said:
His home country stated Taiwan
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
yea saw that now, because it wasn't visible cause he's OP. didn't even knew taiwan sells it earlier, just remembered in EU it solds from first june I think
DeeZZ_NuuZZ said:
yea saw that now, because it wasn't visible cause he's OP. didn't even knew taiwan sells it earlier, just remembered in EU it solds from first june I think
Click to expand...
Click to collapse
No offense indeed and thanks Captain_Throwback for his hard working on HTC. In my experiences, HTC guys on xda board are usually nice and helpful, mostly better than those who I met on sony, samsung, lg xda board.
I've sent a pull request to https://github.com/CaptainThrowback/android_device_htc_ocn that fixes the sd card and screen not responding at first boot issues. The usb one I'll look at later, need to do some real life stuff for a bit
I expect the problem is in init.recovery.usb.rc as it sets mtp,adb
One thing though... whilst I can fastboot boot recovery.img I can't flash recovery with an unlocked bootloader but S-ON.
$ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (34772 KB)...
OKAY [ 0.778s]
writing 'recovery'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 0.778s
Flinny said:
I've sent a pull request to https://github.com/CaptainThrowback/android_device_htc_ocn that fixes the sd card and screen not responding at first boot issues. The usb one I'll look at later, need to do some real life stuff for a bit
I expect the problem is in init.recovery.usb.rc as it sets mtp,adb
One thing though... whilst I can fastboot boot recovery.img I can't flash recovery with an unlocked bootloader but S-ON.
$ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (34772 KB)...
OKAY [ 0.778s]
writing 'recovery'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 0.778s
Click to expand...
Click to collapse
interesting...looks like we'll need s-off sooner than later... when u fastboot boot it, is twrp still functional?
OMJ said:
interesting...looks like we'll need s-off sooner than later... when u fastboot boot it, is twrp still functional?
Click to expand...
Click to collapse
Yeah, backups to internal and sdcard is as far as I've gone. I might give flashing my SlimRoms build a go later.. or maybe I'll see if my built ramdisk with a few bootclass path alterations for stock boots first
I also got TWRP compiled and running, stuck at MTP and USB Mass storage too.
BTW, I rooted my device before flashing any custom recovery... using something about to be released in the Magisk forum
Guess I should open a TWRP thread with my mostly working version now that we have a working kernel . We can continue working on MTP/UMS, though I suspect MTP will require a patch or two in TWRP upstream to add support for configfs. I think fixing UMS will require kernel source.
Haha guys, I figured out the way to fix both UMS and MTP. Yay!
I provided the info to Captain, and him, nkk71 and I are working on it now
topjohnwu said:
Haha guys, I figured out the way to fix both UMS and MTP. Yay!
I provided the info to Captain, and him, nkk71 and I are working on it now
Click to expand...
Click to collapse
nice!
topjohnwu said:
Haha guys, I figured out the way to fix both UMS and MTP. Yay!
I provided the info to Captain, and him, nkk71 and I are working on it now
Click to expand...
Click to collapse
That's awesome!!
Flinny said:
I've sent a pull request to https://github.com/CaptainThrowback/android_device_htc_ocn that fixes the sd card and screen not responding at first boot issues. The usb one I'll look at later, need to do some real life stuff for a bit
I expect the problem is in init.recovery.usb.rc as it sets mtp,adb
One thing though... whilst I can fastboot boot recovery.img I can't flash recovery with an unlocked bootloader but S-ON.
$ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (34772 KB)...
OKAY [ 0.778s]
writing 'recovery'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 0.778s
Click to expand...
Click to collapse
BTW, I figured out that you must be flashing recovery in fastboot mode.
Boot into download mode, then you can flash the recovery without an issue
(reboot with power button down, or adb reboot download)
Interesting, that's new my last phone was a m9 :/
TWRP thread is up. Thanks @Flinny and @topjohnwu for helping work out the issues with TWRP!
Still hoping to be able to get my hands on one so I can maintain for it properly .
Captain_Throwback said:
TWRP thread is up. Thanks @Flinny and @topjohnwu for helping work out the issues with TWRP!
Still hoping to be able to get my hands on one so I can maintain for it properly .
Click to expand...
Click to collapse
I missed the m10.. after getting the m7/m8/m9 but I have to say I'm REALLY enjoying the u11 everything is just INSTANT.