Related
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!
*** I HAVE SOLD MY M8 BUT I WILL TRY AND KEEP THIS UP-TO-DATE WHEN NEW RUUs COME OUT ***
*** NEW GUIDE AS WE NOW HAVE AN RUU!!! ***
This guide is for Windows-only. The reason for this is because the htc_fastboot file used is a Windows binary and there doesn't appear to be a version for Mac/Linux
This guide will allow you to return your EU, unbranded M8_UL device to 100% stock (inc. locking the bootloader and removing the tampered flag) for resale purposes or to return to HTC. It does not cover carrier-branded handsets and does require you to be S-OFF but Step 3 can be done on an S-ON EU M8 so long as your bootloader is relocked and you match one of the CIDs listed below. A lot of this can be used to restore a US carrier M8 as the RUUs are available, though, but you'd have to get the relevant RUU.zip from the EXE (which is very easy)
This process applies to the following CIDs:
HTC__001
HTC__102
HTC__203
HTC__E11
HTC__405
HTC__Y13
HTC__304
HTC__A07
HTC__032
HTC__J15
HTC__016
HTC__M27
HTC__K18
HTC__A48
HTC__002
You need the following files stored in your fastboot folder:
4.16.401.10 RUU ZIP - https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view (renamed to ruu.zip - not ruu.zip.zip!)
md5:4e03845aeab375746b4553e610047680
htc_fastboot.exe - *** REMOVED DUE TO HUGE AMMOUNTS OF SPAM REQUESTS ***
md5: 7343C5BCEC64373F83D69BD074954759
TWRP - http://techerrata.com/file/twrp2/m8/openrecovery-twrp-2.8.4.0-m8.img (renamed to recovery.img) md5:
e51c6ce8db0b7318ef31e1e7bd03c96e
And you'll also need HTC Sync Manager - http://www.htc.com/uk/support/software/htc-sync-manager.aspx (install it for the drivers and then uninstall it but leave the drivers on your PC)
All commands in bold are to be done in a command prompt window in your fastboot folder
1. 'Lock' the bootloader and reset the tamper flag
We know we can relock the bootloader by using the command 'fastboot oem lock', but it will show 'RELOCKED' on the bootloader and still show the phone has been unlocked in the past. With S-OFF we can set it back to 'LOCKED' . To do this, we need to use TWRP and adb shell
Flash TWRP in the usual manner by connecting the phone to the PC whilst in the bootloader and flash by using the command fastboot flash recovery recovery.img. Once flashed, boot the phone into TWRP and connect to your PC and make sure the drivers are successfully installed. To confirm it's working type adb devices and it should be listed with your devices serial number. Assuming you can see the device, we can now use adb shell to change the flag from 'UNLOCKED' to 'LOCKED' by using the following commands:
adb shell
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
Once the command has finished, we can continue using adb shell to reset the tamper flag by using the following command:
echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
Once this has finished, we can exit out of adb shell by simply typing exit. Then reboot the phone into the bootloader through the menu in TWRP so we can confirm the flags are set back to stock.
2. Change the CID (if required)
Now we're in the bootloader and are 'LOCKED' and not listed as modified (but still S-OFF) it's best we reset the CID so moving forward things are easy. To do this, you just need to use fastboot oem writecid HTC__001, or whichever CID your device originally came with from the list at the beginning of this guide. Once you've reset the CID, reboot the bootloader to confirm the changes using fastboot reboot-bootloader
3. Flash the RUU
We are now at the point where we can flash the RUU and restore the phone to 100% stock. To do this, we first need to boot the phone into RUU mode using the command fastboot oem rebootRUU. Once in RUU mode, you'll see a silver HTC logo on the phone and that's it. At this point, we now use the HTC fastboot package to flash their RUU.zip file using the command htc_fastboot flash zip ruu.zip. This process will take a few minutes, and the phone will reboot a few times but once done it'll say complete. At this point, reboot the phone back to the bootloader using fastboot reboot-bootloader
4. Factory reset the device *** OPTIONAL ***
Having flashed the RUU, I always prefer to do a factory reset to make sure everything is in order. To do this, boot into the stock recovery and once at the black screen hold volume up and press power to get into the menu and then select 'wipe data/factory reset' using the volume buttons and use power to select the option.
5. Reboot the phone
Pretty obvious this - just select 'reboot system now' and you should be good to go!
Reserved in case I need it
To adapt this for every single m8 would be incredibly simple, I'm not sure why you would target such a small group? Nice guide never the less.
Also you always need to flash firmware files twice.
Sent from my HTC One_M8 using xda app-developers app
exad said:
To adapt this for every single m8 would be incredibly simple, I'm not sure why you would target such a small group? Nice guide never the less.
Also you always need to flash firmware files twice.
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
Because there aren't any pre-packaged ZIPs for any other build - only Nandroids. Now, I'm sure someone could make a flashable ZIP out of a Nandroid but I don't have the time for that! Plus, you've then got to make sure the right FW package is available as well as the stock recovery. I also DIDN'T have to flash the FW package twice, it worked doing it once only but it does mention to do it again as a precaution
As I have an unbranded EU handset I did this guide - if anyone wants to use it as a template then please feel free to do so!
EddyOS said:
I also DIDN'T have to flash the FW package twice, it worked doing it once only but it does mention to do it again as a precaution
Click to expand...
Click to collapse
Any time hboot is flashed, you have to flash it twice for it to actually complete the full flash. There are no exceptions to the rule so if you did it once, you effectively didn't finish your firmware flash and run the risk of bricking your device instantly if you go S-ON to return it if the firmware was modified in any way over how it was stock. Please fix your guide before someone has modified their hboot to remove the red text and bricks their phone when they find the separate guide to go S-ON.
EtherealRemnant said:
Any time hboot is flashed, you have to flash it twice for it to actually complete the full flash. There are no exceptions to the rule so if you did it once, you effectively didn't finish your firmware flash and run the risk of bricking your device instantly if you go S-ON to return it if the firmware was modified in any way over how it was stock. Please fix your guide before someone has modified their hboot to remove the red text and bricks their phone when they find the separate guide to go S-ON.
Click to expand...
Click to collapse
It says it already!! I didn't flash it twice as I was already on the correct FW. I've made it bold so people will notice it
EddyOS said:
e. Type: fastboot flash zip firmware.zip and wait for process to complete. Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Click to expand...
Click to collapse
EddyOS said:
It says it already!! I didn't flash it twice as I was already on the correct FW
Click to expand...
Click to collapse
You're on the correct firmware but not everyone will be. Currently your guide sets people up for a brick should they follow it and then follow the procedure to go S-ON afterwards as many actually get rid of the red text. Its not optional to flash it twice like you make it sound, its mandatory. If you won't change the text, I'll report the thread because this will result in bricks, end of story.
EtherealRemnant said:
You're on the correct firmware but not everyone will be. Currently your guide sets people up for a brick should they follow it and then follow the procedure to go S-ON afterwards as many actually get rid of the red text. Its not optional to flash it twice like you make it sound, its mandatory. If you won't change the text, I'll report the thread because this will result in bricks, end of story.
Click to expand...
Click to collapse
In which case blame @mike1986. as it was taken from his firmware thread. I'll 'correct' it to please you but I don't agree with it as EU users will already be on the right FW. Nowhere does this mention that you have to go back to S-ON as that's nothing to do with this guide. All this is for is going back to stock
Text changed to make it a bit more obvious to do it twice, although this is different to flashing an RUU ZIP (where you HAVE to flash it twice as that's how the RUU ZIP works). Surely if it needed flashing twice it'd tell you to do it (as an RUU ZIP does)?
EddyOS said:
In which case blame @mike1986. as it was taken from his firmware thread. I'll 'correct' it to please you but I don't agree with it as EU users will already be on the right FW. Nowhere does this mention that you have to go back to S-ON as that's nothing to do with this guide. All this is for is going back to stock
Click to expand...
Click to collapse
I can't believe mike doesn't have it right either but I checked his thread and sure enough, there it is. Hopefully he'll change it since you tagged him here.
Even if you are on EU firmware, if you modify hboot to get rid of the red text and you have an incomplete firmware flash, you will brick if you turn the secure flag back on to return the device for warranty/exchange. Most people who return to stock are doing so in order to return the device so it is just smart to assume that they may have changed their hboot at some point.
EddyOS said:
Text changed to make it a bit more obvious to do it twice
Click to expand...
Click to collapse
Thank you.
EDIT: Noticed your edit to your post. It doesn't say something like this:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
After you do the first command? I suppose its possible HTC changed it. I don't have a firmware zip for me to go back to my T-Mobile firmware or I would try it myself to see but every HTC I've ever had before, if you are flashing an image with the hboot in it you had to do it twice. I wonder if the hboot is actually removed from mike's image.
EtherealRemnant said:
I can't believe mike doesn't have it right either but I checked his thread and sure enough, there it is. Hopefully he'll change it since you tagged him here.
Even if you are on EU firmware, if you modify hboot to get rid of the red text and you have an incomplete firmware flash, you will brick if you turn the secure flag back on to return the device for warranty/exchange. Most people who return to stock are doing so in order to return the device so it is just smart to assume that they may have changed their hboot at some point.
Thank you.
EDIT: Noticed your edit to your post. It doesn't say something like this:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
After you do the first command? I suppose its possible HTC changed it. I don't have a firmware zip for me to go back to my T-Mobile firmware or I would try it myself to see but every HTC I've ever had before, if you are flashing an image with the hboot in it you had to do it twice. I wonder if the hboot is actually removed from mike's image.
Click to expand...
Click to collapse
That's correct, it's not there any more. And the HBOOT is in the FW ZIP (see attached). That's why I didn't make it 'mandatory' as I assumed it wasn't needed as that warning didn't come up
EddyOS said:
That's correct, it's not there any more. And the HBOOT is in the FW ZIP (see attached). That's why I didn't make it 'mandatory' as I assumed it wasn't needed as that warning didn't come up
Click to expand...
Click to collapse
I still don't trust it and would continue to flash it twice to make sure. I don't remember the exact reason why the hboot caused it to fail all the time, something to do with the signature checking I believe.
The only way to really verify if it is actually flashing or not is to flash a different hboot this way and see if it actually works. I don't have the time to mess with it right now so I'd still suggest the old way. You know what they say about things that aren't broke...
EtherealRemnant said:
I still don't trust it and would continue to flash it twice to make sure. I don't remember the exact reason why the hboot caused it to fail all the time, something to do with the signature checking I believe.
The only way to really verify if it is actually flashing or not is to flash a different hboot this way and see if it actually works.
Click to expand...
Click to collapse
You're probably right, I just did what I did but then again I never flashed a custom HBOOT so it wasn't gonna be an issue (and I'd never go back to S-ON anyway)
EddyOS said:
You're probably right, I just did what I did but then again I never flashed a custom HBOOT so it wasn't gonna be an issue (and I'd never go back to S-ON anyway)
Click to expand...
Click to collapse
The only time I ever bother returning to stock is if I have to return the phone under warranty, sorry I was so mean about it, its just a serious issue when you have the potential to brick someone's device. I've never been unfortunate enough to brick but I've seen it posted before and what it came down to was something that wasn't explained clearly and could have been totally avoided. Thanks for the guide, I'm sure it will help many people. :good:
EtherealRemnant said:
The only time I ever bother returning to stock is if I have to return the phone under warranty, sorry I was so mean about it, its just a serious issue when you have the potential to brick someone's device. I've never been unfortunate enough to brick but I've seen it posted before and what it came down to was something that wasn't explained clearly and could have been totally avoided. Thanks for the guide, I'm sure it will help many people. :good:
Click to expand...
Click to collapse
It's all good! I've made one last change to that point to highlight that although it's not strictly required it's strongly recommended to do it twice as a precaution
Not sure what else you can out as no doubt someone will get it wrong at some point...
EddyOS said:
Not sure what else you can out as no doubt someone will get it wrong at some point...
Click to expand...
Click to collapse
It wouldn't be XDA if they didn't! :highfive:
Is it possible on my phone with CID HTC__J15 and S-on??
sari94 said:
Is it possible on my phone with CID HTC__J15 and S-on??
Click to expand...
Click to collapse
You can use parts of the guide but not the parts with (REQUIRES S-OFF) next to it (basically 1 and 5 are what you need, so long as you have an unbranded handset)
Added CIDs that will work with this guide to help users - if it's not listed then it won't work
Im guessing that once your back at stock you'll get OTA updates?
Ok, I am completely flummoxed. I have a Kindle Fire HD 2013 7" that is stuck in fastboot mode. Whether the factory cable is plugged in or not, it still goes to fastboot when turned on, Changing the bootmode via fastboot does not affect it. Heres the interesting part-
An lsusb in Ubuntu lists it as an Amazon Kindle Fire HD 8.9", it definitely isn't.
getvar product lists it as a "Bowser-Dummy-00" - I have no idea what this is although the motherboard says "Soho" on it when opened up
Trying to flash boot, bootloader, recovery, system etc etc via fastboot gives a "partition doesn't exist" error.
Trying the flashall command on fastboot informs me that the update file I have is for Soho but my product is this damn Bowser-Dummy-00
I have tried eMMC access but get nothing from that, Ubuntu does not even register it is connected.
When connected normally in fastboot mode I am informed that the MTP device could not be accessed.
I have been trying for hours to try and sort this out and find something on the "Bowser-Dummy" thing but I am coming up a blank
Any help would be so appreciated, I cannot seem to find any update file that is suitable for this product
Did you purchase the product like this? If so, it seems you got an engineering unit...
r3pwn said:
Did you purchase the product like this? If so, it seems you got an engineering unit...
Click to expand...
Click to collapse
Bought it off of eBay as a "boot loop" problem.
I have never seen this name of board before
overlode said:
Bought it off of eBay as a "boot loop" problem.
I have never seen this name of board before
Click to expand...
Click to collapse
The Kindle Fire HDs use a "Bowser" platform (unique to Amazon only, I believe) and the original Fires use a "Blaze" platform (Again, unique to Amazon, I believe). Yeah, looks like you definitely got an engineering device, unless production models use a "dummy" platform (very weird if they did.) Considering it's not even flashing the updates and giving it's the errors makes it even weirder... Too bad @Hashcode went to work at Linaro. He may have found this interesting.
r3pwn said:
The Kindle Fire HDs use a "Bowser" platform (unique to Amazon only, I believe) and the original Fires use a "Blaze" platform (Again, unique to Amazon, I believe). Yeah, looks like you definitely got an engineering device, unless production models use a "dummy" platform (very weird if they did.) Considering it's not even flashing the updates and giving it's the errors makes it even weirder... Too bad @Hashcode went to work at Linaro. He may have found this interesting.
Click to expand...
Click to collapse
Yeah I know was gutted when I found out.
The closest I have gotten to getting it to work was trying to flash a full dd I did of a working Soho model but it reports that the image is too big. I have messaged stunts about it as he was working on a sparse system file.
The fact that all the partitions are missing is a bit strange and that in Ubuntu an "lsusb" command lists it as a Kindle Fire HD 8.9". I suspect someone else before me has tried flashing it with incorrect software and partly bricked the device.
I tried to flash an official update I downloaded from Amazon but it reports that amazon-info.txt is missing from the archive. I put the file in the same folder I was trying to flash from and it attempted to write but then reported that the update is for a "Soho" not this stupid Bowser model.
I am at a loss for what to do with it, I have tried pretty much everything, the "unable to access MTP device" error in Ubuntu is also weird.
I even soldered a card reader to the eMMC, something I have done many times before but not even that is recognised.
I also tried fastbooting into an unsupported TWRP file, risky I know but due to the fact that I was not flashing it, it should be safe to do. But alas it always returns to the fastboot screen after the grey "Kindle Fire" splash screen.
For the minute I will keep playing with it but I doubt I will find an easy solution unless I can get hold of a "Bowser" official update
overlode said:
Yeah I know was gutted when I found out.
The closest I have gotten to getting it to work was trying to flash a full dd I did of a working Soho model but it reports that the image is too big. I have messaged stunts about it as he was working on a sparse system file.
The fact that all the partitions are missing is a bit strange and that in Ubuntu an "lsusb" command lists it as a Kindle Fire HD 8.9". I suspect someone else before me has tried flashing it with incorrect software and partly bricked the device.
I tried to flash an official update I downloaded from Amazon but it reports that amazon-info.txt is missing from the archive. I put the file in the same folder I was trying to flash from and it attempted to write but then reported that the update is for a "Soho" not this stupid Bowser model.
I am at a loss for what to do with it, I have tried pretty much everything, the "unable to access MTP device" error in Ubuntu is also weird.
I even soldered a card reader to the eMMC, something I have done many times before but not even that is recognised.
I also tried fastbooting into an unsupported TWRP file, risky I know but due to the fact that I was not flashing it, it should be safe to do. But alas it always returns to the fastboot screen after the grey "Kindle Fire" splash screen.
For the minute I will keep playing with it but I doubt I will find an easy solution unless I can get hold of a "Bowser" official update
Click to expand...
Click to collapse
You could try modifying the amazon-info.txt file and change all instances of "Soho" to Bowser-Dummy-00.
r3pwn said:
You could try modifying the amazon-info.txt file and change all instances of "Soho" to Bowser-Dummy-00.
Click to expand...
Click to collapse
I will just try and explain a little better what I have done so far as I think I have got myself a little confused.
I cant seem to find a file in any amazon archive named amazon-info.txt.
I tried updating using fastboot -i 0x1949 update update.zip - this returned the error of -
"archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt"
I then just created a new text file using notepad and simply entered "board=Bowser-Dummy-00" and saved it into the directory where my files were and where I was running fastboot. Unfortunately I still get the same message
I then tried again with fastboot -i 0x1949 update update.zip and I still get the same error
I then tried fastboot -i 0x1949 flashall and this returns an error of -
"error: neither -p product specified nor ANDROID_PRODUCT_OUT set"
I then tried fastboot -i 0x1949 -p Bowser-Dummy-00 flashall and I get -
"error: could not load android-info.txt: No error"
I have tried set ANDROID_PRODUCT_OUT=C:\Users\Kev\Desktop\Kindle Fire HD 7 SOHO but still it returns the same error.
I am running out of ideas...
Edit - I tried running fastboot -i 0x1949 flashall again and now it gives this -
"Bootloader Version...:
Baseband Version.....:
Serial Number........: ************************
------------------------------
checking product...
OKAY [ 0.001s]
sending 'boot' (8192 KB)...
OKAY [ 0.438s]
writing 'boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.455s"
The only thing that changes on the Kindle is in the top left hand side of the screen I get the message "Start downloading" every time I send the command
overlode said:
I will just try and explain a little better what I have done so far as I think I have got myself a little confused.
I cant seem to find a file in any amazon archive named amazon-info.txt.
I tried updating using fastboot -i 0x1949 update update.zip - this returned the error of -
"archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt"
I then just created a new text file using notepad and simply entered "board=Bowser-Dummy-00" and saved it into the directory where my files were and where I was running fastboot. Unfortunately I still get the same message
I then tried again with fastboot -i 0x1949 update update.zip and I still get the same error
I then tried fastboot -i 0x1949 flashall and this returns an error of -
"error: neither -p product specified nor ANDROID_PRODUCT_OUT set"
I then tried fastboot -i 0x1949 -p Bowser-Dummy-00 flashall and I get -
"error: could not load android-info.txt: No error"
I have tried set ANDROID_PRODUCT_OUT=C:\Users\Kev\Desktop\Kindle Fire HD 7 SOHO but still it returns the same error.
I am running out of ideas...
Edit - I tried running fastboot -i 0x1949 flashall again and now it gives this -
"Bootloader Version...:
Baseband Version.....:
Serial Number........: ************************
------------------------------
checking product...
OKAY [ 0.001s]
sending 'boot' (8192 KB)...
OKAY [ 0.438s]
writing 'boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.455s"
The only thing that changes on the Kindle is in the top left hand side of the screen I get the message "Start downloading" every time I send the command
Click to expand...
Click to collapse
So it seems that your partitions are completely messed up. I don't think there is any way to fix that, but I'll look into it and keep you posted.
r3pwn said:
So it seems that your partitions are completely messed up. I don't think there is any way to fix that, but I'll look into it and keep you posted.
Click to expand...
Click to collapse
I would appreciate that, personally I think this is a lost cause and only Amazon would be able to sort it out. My experience of linux is not enough to give me a chance of getting round the mounting as MTP device problem either
r3pwn said:
So it seems that your partitions are completely messed up. I don't think there is any way to fix that, but I'll look into it and keep you posted.
Click to expand...
Click to collapse
Hey man. What's up here? Seems that the dude has another board entirely.
overlode said:
I would appreciate that, personally I think this is a lost cause and only Amazon would be able to sort it out. My experience of linux is not enough to give me a chance of getting round the mounting as MTP device problem either
Click to expand...
Click to collapse
Mounting as MTP in fastboot isn't possible on any device AFAIK.
SafinWasi said:
Hey man. What's up here? Seems that the dude has another board entirely.
Click to expand...
Click to collapse
Actually, to me, it looks like he got an engineering unit, but can't flash any images because, well, Bowser-Dummy-00 != Soho.
And the partitioning seems to be messed up. If we somehow magically fix the partitions, he might be able to get it up and running, but it's doubtful.
---------- Post added at 03:31 PM ---------- Previous post was at 03:27 PM ----------
When you get the chance, try running
Code:
fastboot oem ?
and tell me what the output is. If it's more convenient for you, we could have this conversation via Hangouts or some other quick messaging service...
r3pwn said:
Mounting as MTP in fastboot isn't possible on any device AFAIK.
Actually, to me, it looks like he got an engineering unit, but can't flash any images because, well, Bowser-Dummy-00 != Soho.
And the partitioning seems to be messed up. If we somehow magically fix the partitions, he might be able to get it up and running, but it's doubtful.
---------- Post added at 03:31 PM ---------- Previous post was at 03:27 PM ----------
When you get the chance, try running
Code:
fastboot oem ?
and tell me what the output is. If it's more convenient for you, we could have this conversation via Hangouts or some other quick messaging service...
Click to expand...
Click to collapse
Lol,partitioning wizard of Oz.
And Hangouts or Line or Kik would be good for me.
Sent from my device running CyanogenMod 11
SafinWasi said:
Lol,partitioning wizard of Oz.
And Hangouts or Line or Kik would be good for me.
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
I was actually talking to him. You have my Kik already.
r3pwn said:
Mounting as MTP in fastboot isn't possible on any device AFAIK.
Actually, to me, it looks like he got an engineering unit, but can't flash any images because, well, Bowser-Dummy-00 != Soho.
And the partitioning seems to be messed up. If we somehow magically fix the partitions, he might be able to get it up and running, but it's doubtful.
---------- Post added at 03:31 PM ---------- Previous post was at 03:27 PM ----------
When you get the chance, try running
Code:
fastboot oem ?
and tell me what the output is. If it's more convenient for you, we could have this conversation via Hangouts or some other quick messaging service...
Click to expand...
Click to collapse
Ok
C:\Users\Kev>fastboot -i 0x1949 oem ?
...
FAILED (remote failure)
finished. total time: 0.005s
Not sure what that means to you guys
Also, have never used hangouts before, tried to find xda irc but couldn't
r3pwn said:
I was actually talking to him. You have my Kik already.
Click to expand...
Click to collapse
I was talking to him as well. And look below,oem doesn't work as well. Too bad we can't use adb in fastboot
Sent from my device running CyanogenMod 11
SafinWasi said:
I was talking to him as well. And look below,oem doesn't work as well. Too bad we can't use adb in fastboot
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
I think I may have helped him to get it working. I sent him a few commands and he will try them once he gets up.
Sent from my iPod touch using Tapatalk
Have you tried asking in the kfsowi modding community?
https://plus.google.com/communities/115612726860884592519
r3pwn said:
The Kindle Fire HDs use a "Bowser" platform (unique to Amazon only, I believe) and the original Fires use a "Blaze" platform (Again, unique to Amazon, I believe). Yeah, looks like you definitely got an engineering device, unless production models use a "dummy" platform (very weird if they did.) Considering it's not even flashing the updates and giving it's the errors makes it even weirder... Too bad @Hashcode went to work at Linaro. He may have found this interesting.
Click to expand...
Click to collapse
idk about the engineering unit, im no dev or linux whiz, just a guy looking for help, but im getting same error when trying to flash my recovery partition back with stock img "partition not found" i pulled before i started modding it., also stuck on fastboot screen....mine is KFHD 8.9 and store bought, i can flash boot par and system par but no go on recovery par, maybe because i used Hashcodes 2nd bootloader and TWRP recovery install tut? did you guys ever figure this out? thanks in advance
Mike
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.