Related
Please help I unlocked and loaded twrp. Then I flashed the latest Bad Boys Rom 4.4.3 and now I am stuck at the HTC screen. I can't get it to do anything. I have read and tried for hours to RUU or find some way to get a ROM to boot. I am lost...any help much appreciated!
kpahl1973 said:
Please help I unlocked and loaded twrp. Then I flashed the latest Bad Boys Rom 4.4.3 and now I am stuck at the HTC screen. I can't get it to do anything. I have read and tried for hours to RUU or find some way to get a ROM to boot. I am lost...any help much appreciated!
Click to expand...
Click to collapse
Did you fastboot flash the boot image?
What firmware are you on?
Which version of TWRP did you flash?
Captain_Throwback said:
Did you fastboot flash the boot image?
What firmware are you on?
Which version of TWRP did you flash?
Click to expand...
Click to collapse
I used the One_M8_ALL-in -One-Kit_v to get root and to flash trwp 2.7.0.2. I didn't mess with the firmware but I know I was on 4.4.2 and it wanted to take the update but I didn't allow it. I flashed Bad Boyz 4.4.3 latest version...And I do feel dumb for doing that. Wasnt thinking. NOw I am stuck on the white htc screen and cant even get it off by holding the power down button.
kpahl1973 said:
I used the One_M8_ALL-in -One-Kit_v to get root and to flash trwp 2.7.0.2. I didn't mess with the firmware but I know I was on 4.4.2 and it wanted to take the update but I didn't allow it. I flashed Bad Boyz 4.4.3 latest version...And I do feel dumb for doing that. Wasnt thinking. NOw I am stuck on the white htc screen and cant even get it off by holding the power down button.
Click to expand...
Click to collapse
Ok I was just able to get it back to the bootloader and recovery. Thats a positive step. So what do I need to run? I am not S OFF and dont have a rom loaded at the moment. Any help appreciated. I dont want to mess it up any more than I have.
kpahl1973 said:
Ok I was just able to get it back to the bootloader and recovery. Thats a positive step. So what do I need to run? I am not S OFF and dont have a rom loaded at the moment. Any help appreciated. I dont want to mess it up any more than I have.
Click to expand...
Click to collapse
Does anyone have an old 4.4.2 rom I can load to get me going? I know I need to s off and right now I need to get my phone up and running for work and need an older rom that works with current firmware. Thanks so much for any help. I am dead in the water at the moment.
kpahl1973 said:
Does anyone have an old 4.4.2 rom I can load to get me going? I know I need to s off and right now I need to get my phone up and running for work and need an older rom that works with current firmware. Thanks so much for any help. I am dead in the water at the moment.
Click to expand...
Click to collapse
http://themikmik.com/showthread.php...L-Stock-Rooted-Base-2-16-651-4-(Android-4-4-3)
Don't forget to fastboot flash the boot image, and you'll need to download SuperSU and flash the zip after you flash the ROM for it to boot up completely.
Captain_Throwback said:
http://themikmik.com/showthread.php...L-Stock-Rooted-Base-2-16-651-4-(Android-4-4-3)
Don't forget to fastboot flash the boot image, and you'll need to download SuperSU and flash the zip after you flash the ROM for it to boot up completely.
Click to expand...
Click to collapse
Thanks Captain...how do you fastboot flash a .zip file? never done that before...I have flashed a image file but not a zip. I have downloaded your rom and waiting to make sure I flash your 0P6BIMG_m8whl_2.16.651.4_boot_kexec-hardboot_patched.zip correctly before moving forward. Also will any SuperSU zip file work on the phone?
kpahl1973 said:
Thanks Captain...how do you fastboot flash a .zip file? never done that before...I have flashed a image file but not a zip. I have downloaded your rom and waiting to make sure I flash your 0P6BIMG_m8whl_2.16.651.4_boot_kexec-hardboot_patched.zip correctly before moving forward. Also will any SuperSU zip file work on the phone?
Click to expand...
Click to collapse
Click the second link in my sig & scroll down to the section on S-on kernel flashing.
As far as SuperSU, you'll find it in the link below.
http://forum.xda-developers.com/showthread.php?t=1538053
kpahl1973 said:
Thanks Captain...how do you fastboot flash a .zip file? never done that before...I have flashed a image file but not a zip. I have downloaded your rom and waiting to make sure I flash your 0P6BIMG_m8whl_2.16.651.4_boot_kexec-hardboot_patched.zip correctly before moving forward. Also will any SuperSU zip file work on the phone?
Click to expand...
Click to collapse
You don't need that zip file. Just extract to boot.img from the ROM zip. The zip file is specifically for MultiROM support.
Captain_Throwback said:
You don't need that zip file. Just extract to boot.img from the ROM zip. The zip file is specifically for MultiROM support.
Click to expand...
Click to collapse
Ok I flashed the boot.img from the rom I downloaded which was M8WHL 2.16.651.4 Stock Rooted - Deodex and then I flashed the rom. I then flashed the latest SuperSU and rebooted and I am still stuck at the htc screen...did I do something wrong? I was careful to follow step by step with the instructions.
kpahl1973 said:
Ok I flashed the boot.img from the rom I downloaded which was M8WHL 2.16.651.4 Stock Rooted - Deodex and then I flashed the rom. I then flashed the latest SuperSU and rebooted and I am still stuck at the htc screen...did I do something wrong? I was careful to follow step by step with the instructions.
Click to expand...
Click to collapse
I thought you wanted to flash an older base ROM? If so, you wanted to choose a 1.xx base ROM from the thread. Perhaps that's your issue.
Captain_Throwback said:
I thought you wanted to flash an older base ROM? If so, you wanted to choose a 1.xx base ROM from the thread. Perhaps that's your issue.
Click to expand...
Click to collapse
Yes I did to get it going. What would I have to do to get the 2.xx rom going? Or do I need to just get it running first on the old version? I really do appreciate all the help! I really just want my phone to work and its so frustrating. I am downloading the older version now and will try that with the boot.img and supersu as well.
kpahl1973 said:
Yes I did to get it going. What would I have to do to get the 2.xx rom going? Or do I need to just get it running first on the old version? I really do appreciate all the help! I really just want my phone to work and its so frustrating. I am downloading the older version now and will try that with the boot.img and supersu as well.
Click to expand...
Click to collapse
Flashing the 2.xx base ROM requires updating your firmware. You needed an older stock ROM so you could S-OFF and do update it, correct? I thought that was the original issue?
Captain_Throwback said:
Flashing the 2.xx base ROM requires updating your firmware. You needed an older stock ROM so you could S-OFF and do update it, correct? I thought that was the original issue?
Click to expand...
Click to collapse
Yes you are correct. I got ahead of myself. I am downloading the older stock now and hopefully can get that running and then will attempt to s off and put this behind me. Believe it or not I have rooted the evo, lte, one7 and now first time messed up with the m8. You would think I would know a little more and not have made these mistakes. Oh well...with luck this will work and I appreciate all the help!
kpahl1973 said:
Yes you are correct. I got ahead of myself. I am downloading the older stock now and hopefully can get that running and then will attempt to s off and put this behind me. Believe it or not I have rooted the evo, lte, one7 and now first time messed up with the m8. You would think I would know a little more and not have made these mistakes. Oh well...with luck this will work and I appreciate all the help!
Click to expand...
Click to collapse
Thanks for all the help! I am back up and running. I will S off and update.
This is an annoying one. I got a review unit Nexus 6 from a friend, and it is running Android 5.0 build LRX21I. This means that I can't use the manual upgrade package to get to Android 5.1, because for that you need to be running either LRX21O or LRX22C. Even worse, I have tried flashing the LRX22C factory image both manually through fastboot commandline and via Wugfresh, and that hasn't worked either.
Does anyone out there have any ideas on this? I know that worst case, I can just wait until it real OTA comes, but I'm a bit worried on that, because I never even got the Android 5.0.1 OTA.
mikeydangerous said:
This is an annoying one. I got a review unit Nexus 6 from a friend, and it is running Android 5.0 build LRX21I. This means that I can't use the manual upgrade package to get to Android 5.1, because for that you need to be running either LRX21O or LRX22C. Even worse, I have tried flashing the LRX22C factory image both manually with ADB and via Wugfresh, and that hasn't worked either.
Does anyone out there have any ideas on this? I know that worst case, I can just wait until it real OTA comes, but I'm a bit worried on that, because I never even got the Android 5.0.1 OTA.
Click to expand...
Click to collapse
Is everything 100% stock? Not rooted? Stock recovery? Stock encrypted kernel?
mikeydangerous said:
I have tried flashing the LRX22C factory image both manually with ADB
Click to expand...
Click to collapse
You cannot flash factory images with adb. It uses fastboot.
Instead of using the flash-all script, just try manually flashing the system.img, boot.img, radio.img initially.
rootSU said:
You cannot flash factory images with adb. It uses fastboot.
Instead of using the flash-all script, just try manually flashing the system.img, boot.img, radio.img initially.
Click to expand...
Click to collapse
My mistake, definitely meant to type fastboot, not adb, editing the original post now, and I'll try manually flashing after work.
cam30era said:
Is everything 100% stock? Not rooted? Stock recovery? Stock encrypted kernel?
Click to expand...
Click to collapse
Not rooted, stock everything. I unlocked the bootloader when trying to flash, but relocked it when everything failed. I have no interest in rooting.
rootSU said:
You cannot flash factory images with adb. It uses fastboot.
Instead of using the flash-all script, just try manually flashing the system.img, boot.img, radio.img initially.
Click to expand...
Click to collapse
Manually flashing each one did work. Not sure why it failed on flash-all, but thanks!
mikeydangerous said:
Manually flashing each one did work. Not sure why it failed on flash-all, but thanks!
Click to expand...
Click to collapse
I've never liked those flash-all and it doesn't take much time to flash each individually anyway. It's pretty simple and you have more control, quicker IMHO
Is there any method to unlock the bootloader without activating the system developer option? I'm stuck on the boot screen and I can't unlock. ANDROID 5.1
Christian Correia said:
Is there any method to unlock the bootloader without activating the system developer option? I'm stuck on the boot screen and I can't unlock. ANDROID 5.1
Click to expand...
Click to collapse
Can you get into bootloader mode? And if not, what have you tried to get into bootloader mode?
JulesJam said:
Can you get into bootloader mode? And if not, what have you tried to get into bootloader mode?
Click to expand...
Click to collapse
Yes. Enter the RECOVERY and FASTBOOT normally. Actually I don't know what is bootloader mode, more goes into recovery and fastboot
Christian Correia said:
Yes. Enter the RECOVERY and FASTBOOT normally. Actually I don't know what is bootloader mode, more goes into recovery and fastboot
Click to expand...
Click to collapse
bootloader mode = fastboot
If a full system.img of 5.1 is not available for your device, I would get into bootloader mode and try to flash the 5.0 stock system using fastboot or mfastboot. Then see if you can unlock the bootloader. It may not work if you have upgraded your bootloader to 5.1 and please note - you cannot safely downgrade either the bootloader or partition table so don't even try.
What model device do you have? I am assuming that there is no 5.1 system.img available.
JulesJam said:
bootloader mode = fastboot
If a full system.img of 5.1 is not available for your device, I would get into bootloader mode and try to flash the 5.0 stock system using fastboot or mfastboot. Then see if you can unlock the bootloader. It may not work if you have upgraded your bootloader to 5.1 and please note - you cannot safely downgrade either the bootloader or partition table so don't even try.
What model device do you have? I am assuming that there is no 5.1 system.img available.
Click to expand...
Click to collapse
Unfortunately I can't downgrade. And the BOOTLOADER has been updated to version 60.16. The way it's going to be wait the full image (XT1097 5.1 23.11.14 current)
Christian Correia said:
Unfortunately I can't downgrade.
Click to expand...
Click to collapse
Why can't you downgrade just the system partition? If you get the official copy or the fxz, it is a signed image and so you can flash it using fastboot or mfastboot even with a locked bootloader. You may need to flash the 5.0 boot.img too.
What model do you have?
JulesJam said:
Why can't you downgrade just the system partition? If you get the official copy or the fxz, it is a signed image and so you can flash it using fastboot or mfastboot even with a locked bootloader. You may need to flash the 5.0 boot.img too.
What model do you have?
Click to expand...
Click to collapse
I tried to pass the 5.0 system image, plus the error. I do not know what to do. Precise image 5.1 23.32-14 which is what I was before the brick
Christian Correia said:
I tried to pass the 5.0 system image, plus the error. I do not know what to do. Precise image 5.1 23.32-14 which is what I was before the brick
Click to expand...
Click to collapse
What model phone do you have? Brazilian XT1097?
JulesJam said:
What model phone do you have? Brazilian XT1097?
Click to expand...
Click to collapse
Yes
Christian Correia said:
Yes
Click to expand...
Click to collapse
I think this is the official 5.0 firmware for it.
http://forum.xda-developers.com/moto-x-2014/development/rom-retail-br-firmware-t2995818
I would download it, then extract the system file(s). I don't know if they will be in sparsechunks or a single file, but if they are in sparsechunks, you can use regular fastboot to flash them. If the system is a single file system.img, you will have to use mfastboot version 2 to flash it.
I would try just flashing the system partition and then see if it boots. If not, then I would flash the 5.0 boot.img.
You also could try downgrading to 4.4.4 system, I know others have done it successfully.
Just do NOT take any OTAs - people are bricking when they downgrade and then take an OTA. You must wait for the 5.1 firmware to be released to flash it. Don't take an OTA.
JulesJam said:
I think this is the official 5.0 firmware for it.
http://forum.xda-developers.com/moto-x-2014/development/rom-retail-br-firmware-t2995818
I would download it, then extract the system file(s). I don't know if they will be in sparsechunks or a single file, but if they are in sparsechunks, you can use regular fastboot to flash them. If the system is a single file system.img, you will have to use mfastboot version 2 to flash it.
I would try just flashing the system partition and then see if it boots. If not, then I would flash the 5.0 boot.img.
You also could try downgrading to 4.4.4 system, I know others have done it successfully.
Just do NOT take any OTAs - people are bricking when they downgrade and then take an OTA. You must wait for the 5.1 firmware to be released to flash it. Don't take an OTA.
Click to expand...
Click to collapse
Friend didn't work. Gave Error DOWNGRADED VERSION SYSTEM
Christian Correia said:
Friend didn't work. Gave Error DOWNGRADED VERSION SYSTEM
Click to expand...
Click to collapse
The only other thing you could do and I don't know if the dev would agree to this, is use a software tool we have called MoFo - it allows you to flash unsigned files as long as they are in the ext4 format.
The developer is @maiko1 and I will ask on the MoFo thread if he would consider opening up the tool for this purpose. It costs $20 USD for the software. It would allow you bypass the bootloader signature check and force flash any unsigned file you want to the system partition.
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404
JulesJam said:
The only other thing you could do and I don't know if the dev would agree to this, is use a software tool we have called MoFo - it allows you to flash unsigned files as long as they are in the ext4 format.
The developer is @maiko1 and I will ask on the MoFo thread if he would consider opening up the tool for this purpose. It costs $20 USD for the software. It would allow you bypass the bootloader signature check and force flash any unsigned file you want to the system partition.
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404
Click to expand...
Click to collapse
Works even with the locked bootloader? I am not spending money for nothing? Sure it works? Where can I get these images ext4?
Christian Correia said:
Works even with the locked bootloader? I am not spending money for nothing? Sure it works? Where can I get these images ext4?
Click to expand...
Click to collapse
Let me download the 5.0 image for your device and see if I can flash it to my XT1096 first using mofo.exe. I have a locked bootloader.
Since your bootloaders are unlockable, there is the possibility that maiko1 would discount it for you, idk, but you could ask since really it would just be a one time repair tool.
Also, do you know if someone who is still on the 5.1 soak can pull the 5.1 image from their device and make it flashable by mfastboot? Or would it fail the signature check? I don't know enough about that to know.
The other potential issue is that your boot.img is now 5.1 and maybe that would not boot with the 5.0 system.img. It should but you would need someone with an unlocked bootloader to try it and see if the 5.1 boot.img can run with the 5.0 system.
JulesJam said:
Let me download the 5.0 image for your device and see if I can flash it to my XT1096 first using mofo.exe. I have a locked bootloader.
Since your bootloaders are unlockable, there is the possibility that maiko1 would discount it for you, idk, but you could ask since really it would just be a one time repair tool.
Also, do you know if someone who is still on the 5.1 soak can pull the 5.1 image from their device and make it flashable by mfastboot? Or would it fail the signature check? I don't know enough about that to know.
Click to expand...
Click to collapse
I'm going to be standing by then. If it works I will buy
Christian Correia said:
I'm going to be standing by then. If it works I will buy
Click to expand...
Click to collapse
The dev has to agree to open it up for your model and I added this to my last post:
The other potential issue is that your boot.img is now 5.1 and maybe that would not boot with the 5.0 system.img. It should but you would need someone with an unlocked bootloader to try it and see if the 5.1 boot.img can run with the 5.0 system.
You would need to get someone with an unlocked bootloader XT1097 to see if the 5.1 boot.img will boot the 5.0 system.img. I think it should but it would be better to have someone test it.
JulesJam said:
The dev has to agree to open it up for your model and I added this to my last post:
The other potential issue is that your boot.img is now 5.1 and maybe that would not boot with the 5.0 system.img. It should but you would need someone with an unlocked bootloader to try it and see if the 5.1 boot.img can run with the 5.0 system.
You would need to get someone with an unlocked bootloader XT1097 to see if the 5.1 boot.img will boot the 5.0 system.img. I think it should but it would be better to have someone test it.
Click to expand...
Click to collapse
Thank you. I'm awaiting any news
Christian Correia said:
Thank you. I'm awaiting any news
Click to expand...
Click to collapse
And I guess the other potential issue is whether the 5.1 bootloader will unlock when running the 5.0 system.img - it may not. But at least your phone would work until the 5.1 firmware is released.
I am downloading the Brazilian XT1097 5.0 firmware file now and will flash it if it is flashable by mofo.exe - it will take me about an hour or so if everything goes smoothly.
---------- Post added at 04:42 AM ---------- Previous post was at 03:55 AM ----------
Christian Correia said:
Thank you. I'm awaiting any news
Click to expand...
Click to collapse
Ok, the image is broken down into sparse chunks like the AT&T XT1097. I will enlist the help of someone who was able to make the AT&T image into a single file ext4 file that could be flashed by mofo.exe but it is late my time so it won't be until tomorrow. It takes linux to do that and I don't use linux.
Also, there is the possibility that the exploit that mofo.exe relies on is patched in the 5.1 bootloader. I doubt it since 5.1 was out before mofo.exe was released. Maybe maiko1 would let you test it for free since we only know for sure that it works on the 5.0 and 5.0.2 bootloaders.
Christian Correia said:
Thank you. I'm awaiting any news
Click to expand...
Click to collapse
I have made the single file image but now I need another poster here to remove the footer and the header using a hex editor. Once that is done I can flash it to my device using mofo.exe to see if it flashes.
JulesJam said:
I have made the single file image but now I need another poster here to remove the footer and the header using a hex editor. Once that is done I can flash it to my device using mofo.exe to see if it flashes.
Click to expand...
Click to collapse
I'm waiting eagerly. Because it's been more than 1 week without my dear appliance. And I've tried everything to resuscitate him. And from what I've seen, the only way is to have a system image :fingers-crossed:
Fixed
XDAcube said:
Ok guys so i flashed the custom android m rom (JDx 1.0) sometime ago and i want lollipop back and flash benzo rom. how do i do that i upgraded my bootloader to m and im encrypted. do i just download the nexus 6 lollipop 5.1.1 factory image and flash the bootloader and radio?
Click to expand...
Click to collapse
Yes. It is OK to "downgrade" the bootloader from M Preview back to Lollipop.
cam30era said:
Yes. It is OK to "downgrade" the bootloader from M Preview back to Lollipop.
Click to expand...
Click to collapse
But how? do i just download the factory image and fastboot flash it? how about radio?
XDAcube said:
But how? do i just download the factory image and fastboot flash it? how about radio?
Click to expand...
Click to collapse
Download the factory image. Extract the .img files. Then fastboot flash them.
Here for tutorial > http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Use "Method 2: (long....)"
cam30era said:
Download the factory image. Extract the .img files. Then fastboot flash them.
Here for tutorial > http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Use "Method 2: (long....)"
Click to expand...
Click to collapse
The 5.1.1 images are all for us carriers and im from denmark? BTW i know how to flash,
XDAcube said:
The 5.1.1 images are all for us carriers and im from denmark? BTW i know how to flash,
Click to expand...
Click to collapse
LMY47Z has been "mislabeled" by Google. It is also for international devices. Being used successfully by many international users on this forum.
cam30era said:
LMY47Z has been "mislabeled" by Google. It is also for international devices. Being used successfully by many international users on this forum.
Click to expand...
Click to collapse
Just downloading 5.1.0 [emoji14]
Hvid nexus 6 @ Android M!
XDAcube said:
Fixed
Click to expand...
Click to collapse
If you refrain from editing out your question once fixed, it may help others looking for the same solution in the future.
danarama said:
If you refrain from editing out your question once fixed, it may help others looking for the same solution in the future.
Click to expand...
Click to collapse
True but it tapatalk broke the text so i just typed fixed
Has anyone been able to capture OTA OPW28.2 with security patch in May for manual installation?
I would have if the previous update hadn't broken ADB so I couldn't use logcat.
nykola5 said:
Has anyone been able to capture OTA OPW28.2 with security patch in May for manual installation?
Click to expand...
Click to collapse
You can download it here.
[EDIT] This is for the stock Retail version only.
AvenidaDelGato said:
You can download it here.
Click to expand...
Click to collapse
Can I dirty flash this with TWRP?
AvenidaDelGato said:
You can download it here.
Click to expand...
Click to collapse
Thank you so much! I’ve been looking for a ZIP file of this OTA for weeks. Do I flash the files inside with fastboot like the stock images, or is there some other way to install it? I have an unlocked bootloader and TWRP.
lucasbitencourt said:
Can I dirty flash this with TWRP?
Click to expand...
Click to collapse
Did not work on stock recovery...
failed at 40%..
maybe because i am on project fi rom and this seems a retail variant upadte.
You can give it a try on TWRP
aditya30.pawar said:
Did not work on stock recovery...
failed at 40%..
maybe because i am on project fi rom and this seems a retail variant upadte.
You can give it a try on TWRP
Click to expand...
Click to collapse
Not work on TWRP, I'm on stock
AvenidaDelGato said:
You can download it here.
Click to expand...
Click to collapse
It could not install it from the recovery stock, it remains as "package is for source build 12 but expected" and from there it aborts the update, help
nykola5 said:
It could not install it from the recovery stock, it remains as "package is for source build 12 but expected" and from there it aborts the update, help
Click to expand...
Click to collapse
Same here. Variant -6