Develop Bugs

[Q] Advanced Ace Hack Kit issue

Earlier today, I ran the updated 15/10/11 version of the ace hack kit. Like it was suggested, I read through the manual then I re-read it and re-read it again. As suggested, I disabled / uninstalled all security software on my pc and the other superfluous services. Ran the executable drivers file then I set the phone to charge only and usb debugging was ticked.
I then ran the hack-ace.cmd file as administrator and let the program do it's thing.
It appeared to have completed without any glitches in the suggested 6 minutes.
However, on the phone, all was not well. Since running this, the screen remains blank. When I power on, I get the HTC logo and then it disappears / disintegrates into a blank screen and nothing happens.
The only reason I ran this was to get rid of the irritating apps that I never use but have to Kill every day.
Can anyone help to overcome this problem? This was a replacement handset that I had to fight with my insurance company to get only for this to happen.
I am literaly at my wits end.
Thanks

anomander0108 said:
Earlier today, I ran the updated 15/10/11 version of the ace hack kit. Like it was suggested, I read through the manual then I re-read it and re-read it again. As suggested, I disabled / uninstalled all security software on my pc and the other superfluous services. Ran the executable drivers file then I set the phone to charge only and usb debugging was ticked.
I then ran the hack-ace.cmd file as administrator and let the program do it's thing.
It appeared to have completed without any glitches in the suggested 6 minutes.
However, on the phone, all was not well. Since running this, the screen remains blank. When I power on, I get the HTC logo and then it disappears / disintegrates into a blank screen and nothing happens.
The only reason I ran this was to get rid of the irritating apps that I never use but have to Kill every day.
Can anyone help to overcome this problem? This was a replacement handset that I had to fight with my insurance company to get only for this to happen.
I am literaly at my wits end.
Thanks
Click to expand...
Click to collapse
i think you need to install custom rom and flash it in recovery follow the steps in instruction in ace hack kit because it happen to me also when I ran the ace hack kit..

avnr said:
i think you need to install custom rom and flash it in recovery follow the steps in instruction in ace hack kit because it happen to me also when I ran the ace hack kit..
Click to expand...
Click to collapse
Yes this is the best thing to do. Something must have corrupted your stock ROM. If AAHK completed properly, then you should have ClockworkMod recovery installed.
The first thing I did was install 4EXT recovery but thats not necessary, that was just a personal choice.
So these are the steps you should take:
1: Download a new ROM and put it on your SD card in a convenient place (I recommend the RCMIX32 Runny 3.1 ROM)
2: Remove the battery and reinsert the battery
3: Hold down the volume down button and then hold down the power button. You will get to a white screen with some green robots on the bottom. This is the bootloader screen. You will have to wait a bit for it to finish scanning the SD card. It will tell you when it is finished
4: Use the volume buttons to select recovery and press the power button to select it
5: After a few seconds the recovery environment will appear
6: Go to the wipe menu. Wipe data, cache and dalvik cache (and system if you have the option. I havent used Clockworkmod in a while so I cant really remember what options you have there)
7: Go a few menu's back and select Install zip from SD card
8: Select the zip file
9: Press yes on the confirmation screen
10: When it is finished, click reboot now. It might be on the menu back
This will install a new ROM and it should work properly. If you have any problems along the way just say and we will help to the best of our ability

Thanks for the responses.
I don't think ClockworkMod is installed as there are no options available when I select recovery. It just reboots the device back to the HTC splash screen which as mentioned then fades / deteriorates to a black screen. I had tried the Android HD Revolution rom but no difference.
One thing I did yesterday in my panic was to select 'Factory reset'. Will this have usb debugging setting?
Finally, when I connect to a pc, it doesn't see it. Is this because it's still set on charge only mode?
I'm probably my own worst enemy

If you finally press "Factory reset" you will reset USB debugging, then you can't root your phone using this tools kit. Try to reinstall the stock rom.
If you didn't root your DHD. Phone may still under warranty.

Hi Guys
I've managed to get this back up and running again.
After a lot of playing about with various file downloads last night, I finally managed to get my pc to see the phone. After that, I just downloaded a stock rom and installed it.
After this fright, I am reluctantly going to stick with this and not bother with rooting / custom roms.
Anyway, many thanks for all your responses, I really appreciate the time you took to helpo me out.
This forum absolutely rocks.

Hi,
I've just downloaded, I read the 'effen' manual and then ran ace-hack, it seems to have worked except I can't see clockwork mod recovery?
I can see superuser and ROMmanager, is it still ok to try and download and flash a custom ROM?
---------- Post added at 09:46 PM ---------- Previous post was at 09:03 PM ----------
Well to confirm my noob status I have now found that clockwork mod recovery is indeed installed (I assume you're not meant to be able to see it as an app as it sits at a lower level).
I downloaded the CM7 ROM, so have booted up into recovery mode, have wiped/formatted as instructed but when I choose the zip file from SD card it appears to start then aborts installation...help!!!!

Hi juicyp
juicyp said:
Hi,
I've just downloaded, I read the 'effen' manual and then ran ace-hack, it seems to have worked except I can't see clockwork mod recovery?
I can see superuser and ROMmanager, is it still ok to try and download and flash a custom ROM?
---------- Post added at 09:46 PM ---------- Previous post was at 09:03 PM ----------
Well to confirm my noob status I have now found that clockwork mod recovery is indeed installed (I assume you're not meant to be able to see it as an app as it sits at a lower level).
I downloaded the CM7 ROM, so have booted up into recovery mode, have wiped/formatted as instructed but when I choose the zip file from SD card it appears to start then aborts installation...help!!!!
Click to expand...
Click to collapse
Did you check the MD5 Checksum of the .zip before you copied it to your SD Card? as it might is some way have got corrupted.
Here is a link to what I always use before I copy anything to my SD Card or install on my OS System:- MD5 Check 2.1.
Take Care
TheQuest

Thanks!
I'm all sorted (I think, fingers crossed).
It was principally because of the mac unzipping (Safari preferences not checked), this was the original and prime fault.
That caused me to doubt my partitions on the SD card (google is sometimes your enemy) which I altered.
So what then happened was CM7 installed but upon reboot looped continuously on the android skateboarding screen.
I finally resorted to formatting the SD Card, reapplying the CM7 zip and the google zips and so far it looks good.
Of course I (me and me alone) has stuffed up all the user data I had on the SD card. I might try to recover some photos but stuff like contacts I can regenerate no major loss there.
Thanks for replying!!

CM7 - the experience thus far
Well its 72 hours since I took the plunge!
Initially it looked odd and felt flakey, the Market refused to download 80% of the apps I tried. I resolved this (not sure if it was the right way) by going into recovery and clearing the cache 2-3 times and eventually downloaded all of my old apps.
Some apps cause frequent force-closes, I assume because they've not been updated for Gingerbread? Thats a very minor irritant, I can easily live without these apps anyway.
Battery life hasn't noticeably altered yet but I suppose I have been constantly been tinkering, playing with settings, trying wifi (seems a little less sensitive to signals) and gauging how the radio is working - I seem to get HSPDA a lot less and resort to 3G more than I previously did?
So, done it, like it despite some minor reservations - now what, is there anything else I can do to improve the experience?
I must add one thing this has shown me - I really really know very little about what goes on under the hood. Despite 20+ years experience in CIS this is a very different world and all credit to those who have developed CM7!!

Please help if you can.. please
Hello!!
I am desperately seeking some guidance. Please.
So, I used to have a HTC Inspire 4G and in June I rooted it successfully.. then installed Cyanogenmod 7 etc.. everything worked great. I unfortunately lost the phone and because of insurance got a new one.
When I rooted the first time I used the old school method that was in the XDA forum.. ADB..etc.. but today... with the new replacement..
I downloaded Advance ace hack kit 29102011 (ahhk 29102011.zip) which after reading all the stuff I thought would be just a quicker way to get rooted. I used the same PC that I used before.
This time, unfortunately I am getting a black screen, right after the HTC splash screen shows up.. it fades to black.
I can get to the "Hboot" screen but removing the battery, then restarting by holding the power and the down vol button.
Tried Factory reset.. still fades to back
Tried Recovery .. still fades to back
The device will not be recognized on my laptop when connected to USB..
Am I stuck? Do I have any options?
I should have done what I did before.. but am at a loss right now.. will you please help me.
Please.
Thanks a million in advance for your responses.
Please help.

ravennyc said:
Hello!!
I am desperately seeking some guidance. Please.
So, I used to have a HTC Inspire 4G and in June I rooted it successfully.. then installed Cyanogenmod 7 etc.. everything worked great. I unfortunately lost the phone and because of insurance got a new one.
When I rooted the first time I used the old school method that was in the XDA forum.. ADB..etc.. but today... with the new replacement..
I downloaded Advance ace hack kit 29102011 (ahhk 29102011.zip) which after reading all the stuff I thought would be just a quicker way to get rooted. I used the same PC that I used before.
This time, unfortunately I am getting a black screen, right after the HTC splash screen shows up.. it fades to black.
I can get to the "Hboot" screen but removing the battery, then restarting by holding the power and the down vol button.
Tried Factory reset.. still fades to back
Tried Recovery .. still fades to back
The device will not be recognized on my laptop when connected to USB..
Am I stuck? Do I have any options?
I should have done what I did before.. but am at a loss right now.. will you please help me.
Please.
Thanks a million in advance for your responses.
Please help.
Click to expand...
Click to collapse
Try to run the latest RUU.

Similar Issue
Hi all,
Similar issue as the thread, during AAHK had a "file not found" issue and now, only get HTC screen fading to black. Getting into HBOOT works fine.
I do have S-OFF but;
Have tried recovery, nothing.
Any RUU nothing
ADB shows device is offline
running any other option in AAHK device offline
Any help would be greatly appreciated.
Cheers!

[GUIDE]How to unbrick your Defy and solve other bugs

So your Defy is bricked. It's really hard to brick a Defy or a Defy+ due to locked bootloader, so you can't really brick it but you can get it in state of not booting. In this simple guide i will show you how to unbrick Defy and fix some common errors!
Lets get started!
How to unbrick your Defy
What do you need!
You need the following:
Motorola Defy
RSD Lite (download here: http://goo.gl/KRSRp
SBF (i reccomend 2.2 CEE Froyo) (download here: http://goo.gl/Jhz84) (for other SBFs use this link: http://goo.gl/dYQTl )
USB Cable
Charged battery (at least 50%)
Motorola USB Drivers (download here: http://goo.gl/bWg1M )
Download and install USB Drivers
Download and install RSD Lite
Turn off your phone
Go into bootloader by pressing Power button and Vol+ button
Connect your phone to your PC via USB cable
Make sure everything is OK
Locate downloaded SBF. In popup dialog press Uncompress and start flashing
If you get " Please manually power up this phone " in RSD Lite pull battery out > put your battery back > reboot into stock recovery by holding Power button and Vol- button > Choose Wipe data/cache > Choose Reboot system now
That's it, you unbricked your Defy!
How to repair damaged Dalvik or cache
Use the same method for unbricking your Defy. If you still have problems...do the same procedure again.
How to fix empty battery
If your battery is so empty that you can't even charge it, there are 2 options
Option 1. (McGyver method)
Get a USB cable, cut the off the B plug (the one that plugs into the device) and strip away the shielding, revealing the 4 individual wires inside: White, Green, Red and Black. Red is +5V DC and Black is ground. strip a few (1-2) mm's off each and gently push them into the + and - slots on the battery. Apply some tape to keep them in place, but don't cover the other connectors. Now plug the battery back in, a tight fit, but possible if you've peeled back the shielding and the white and green wires so that only Black and Red are actually being crammed in there with the battery
It should look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Red goes to the + terminal,Black goes to the - terminal
Plug the business end of the newly modded usb cable into your computer.
That's it, your Defy should be alive now
McGyver method found at this thread:http://forum.xda-developers.com/showthread.php?t=892026
I was lazy to write the method by my words...so i just copied from that thread....because he wrote it so well
If original author has problems with copyrights, he can PM me and we will sort it out.
Option 2.
Connect Defy to PC via USB cable. Make sure that your PC is powered on. LED in the top left-hand corner should be white coloured. Leave the Defy overnight to charge. In the morning it should be charged a little bit to charge it via normal method
I have not tested McGyver method, but option 2 worked for me (happened to me once)
This is the end of this tutorial. I hope i helped!
Froyo nandroid backup here
Guys I created a prerooted and with cwm installed froyo nandroid backup. Make full restore
Link: http://d-h.st/RxH
IF YOU DO MAKE ANY DAMAGE TO YOUR PHONE DURING THE PROCESS I AM NOT RESPONSIBLE!

is cee froyo recommended for india defy with stock froyo 2.2.2 and green lens?
my stock was retail taiwanese JRDNEM_U3_3.4.3-36-1.7_CHINESE_SIGN_SIGNED_UCAJRDNEMARAB1B50AA03A.0R_PDS03C_USAJRDNFRYORTINT15_P002_A014_HWp3_Service1FF.sbf.gz
reply please.

prax31 said:
is cee froyo recommended for india defy with stock froyo 2.2.2 and green lens?
my stock was retail taiwanese JRDNEM_U3_3.4.3-36-1.7_CHINESE_SIGN_SIGNED_UCAJRDNEMARAB1B50AA03A.0R_PDS03C_USAJRDNFRYORTINT15_P002_A014_HWp3_Service1FF.sbf.gz
reply please.
Click to expand...
Click to collapse
Well try it...you can always go back by flashing another SBF
IF YOU DO MAKE ANY DAMAGE TO YOUR PHONE , I AM NOT RESPONSIBLE!

bricked/not booting defy
basically downloaded & flashed a wrong sbf file after i rooted it from rsd lite. now its stuck at M screen, will not connect to rsd lite and i have searched relentlessly to figure out another way to flash to it, even in recovery mode will not unzip any files. is there a way to fix it? i have wiped cache and data and rebooted. nothing works...pls help :'(

melowed said:
basically downloaded & flashed a wrong sbf file after i rooted it from rsd lite. now its stuck at M screen, will not connect to rsd lite and i have searched relentlessly to figure out another way to flash to it, even in recovery mode will not unzip any files. is there a way to fix it? i have wiped cache and data and rebooted. nothing works...pls help :'(
Click to expand...
Click to collapse
Pull battery out and wait 5 minutes and reinsert it.
Sent from my house via interwebs to You!

bricked/not booting defy
ppero196 said:
Pull battery out and wait 5 minutes and reinsert it.
Sent from my house via interwebs to You!
Click to expand...
Click to collapse
tried that, still not working

melowed said:
tried that, still not working
Click to expand...
Click to collapse
Go manually to bootmenu (stock) and then connect phone with RSD Lite and flash another SBF
Sent from my house via interwebs to You!

bricked/not booting defy
ppero196 said:
Go manually to bootmenu (stock) and then connect phone with RSD Lite and flash another SBF
Sent from my house via interwebs to You!
Click to expand...
Click to collapse
i can get it to go to boot menu but it wont connect to rsd lite for me to flash another sbf. is there some other way im not aware of?

I can send you my froyo nandroid backup. You can restore it via CWM
No apps installed...it comes pre rooted. OK?
Sent from my house via interwebs to You!

bricked/not booting defy
ppero196 said:
I can send you my froyo nandroid backup. You can restore it via CWM
No apps installed...it comes pre rooted. OK?
Sent from my house via interwebs to You!
Click to expand...
Click to collapse
Awesome thx see if that works
FINALLY got it back to stock after upgrading to the the 5.9v of rsd lite and reinstalling the drivers but i had to flash the same sbf file about 4 times...lol i knew i had the right one but thanks for trying to help me anyway!

i need help asap
melowed said:
Awesome thx see if that works
FINALLY got it back to stock after upgrading to the the 5.9v of rsd lite and reinstalling the drivers but i had to flash the same sbf file about 4 times...lol i knew i had the right one but thanks for trying to help me anyway!
Click to expand...
Click to collapse
Can you send me also the froyo back up? this is what happened to me:
i cleared the cache in the bootloader menu
then i restore factory settings
then i had a zip file of a rom , i changed its name to update so that the bootloader can detect the update.. the update installed completely but when i started rebooting its just stuck at the "Motorola" logo.. what can i do to fix this sir?

drakefrancis said:
Can you send me also the froyo back up? this is what happened to me:
i cleared the cache in the bootloader menu
then i restore factory settings
then i had a zip file of a rom , i changed its name to update so that the bootloader can detect the update.. the update installed completely but when i started rebooting its just stuck at the "Motorola" logo.. what can i do to fix this sir?
Click to expand...
Click to collapse
OK..I'll send you...
It comes with 2ndinit and prerooted
Sent from my MB526 using xda app-developers app

ppero196 said:
OK..I'll send you...
It comes with 2ndinit and prerooted
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
Hey ppero, Thanks for the guide.
Some random Chinese build finally worked for my phone, phone was bough used: http://forum.xda-developers.com/showpost.php?p=14762402&postcount=143

Froyo nandroid backup
Extract in the root of SD card and restore using cwm
Make full restore
http://d-h.st/RxH
Sent from my iPhone 5 using Tapatalk 2

bricked MB526 BL7 no recovery available
Hello, I try to give as much information as possible so please bear with me.
MB526 with BL7 was working perfectly with the quarx nightly 20121018+update v3 but of course I installed the v4 update. What a friend and I figured is that there is a problem when flashing the 2ndboot updates with your power plug still plugged in, this is what I totally forgot about on the v4 update. I wiped the cache and dalvik before AND after the update but was stuck the bootloop. Now I had just made a CWM backup two weeks ago but when restoring I got an error message concerning the system folder. Still in bootloop on the splah M logo. I remember there was something about an older custom ROM and the recovery I used that didnt work so I figured I should start from the SBF.
Using RSDlite 5.7 on a winXP machine, I tried to flash the way I am used to flash brand new MB526 with BL7: (did that for a few friends and the girl)
1. DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
2. DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.sbf
but the plan was overthrown by my phone. It flashed through the whole process but was stuck at the the "please manually power up this phone"-screen in RSDlite, the phone was connected but at the splash screen. Battery out, the PASS would only appear in RSD if I boot directly into bootloader again. Otherwise this splash screen makes my mad. It doesnt boot.
I tried to flash the alternative, chinese, root ROM for BL7; samesame, but different.
Downloaded RSDlite 6.14, Mdriver 5.9 on a win7 machine, used about all the BL7 ROMs I could find on the site: sbf.droid-developers.org/umts_jordanplus/ The last one being the [Retail British] sbf.droid-developers.org/umts_jordanplus/DEFYPLUS_U3_4.5.1-134_DFP-231_BLUR_SIGN_USADEFYEMARAB1B8RTGB005.0R_PDS03C_USAJRDNGIBRRTGB_P023_A025_M002_Service1FF.sbf.gz
samesame
:crying:
Now I cannot boot into the motorola recovery. Theres just the background picture but no menu. As far as I know, flashing an SBF is all that I can do. Anyone has got an idea, which ROM to try or what else to do ?
Thanks in advance

butcherr said:
Hello, I try to give as much information as possible so please bear with me.
MB526 with BL7 was working perfectly with the quarx nightly 20121018+update v3 but of course I installed the v4 update. What a friend and I figured is that there is a problem when flashing the 2ndboot updates with your power plug still plugged in, this is what I totally forgot about on the v4 update. I wiped the cache and dalvik before AND after the update but was stuck the bootloop. Now I had just made a CWM backup two weeks ago but when restoring I got an error message concerning the system folder. Still in bootloop on the splah M logo. I remember there was something about an older custom ROM and the recovery I used that didnt work so I figured I should start from the SBF.
Using RSDlite 5.7 on a winXP machine, I tried to flash the way I am used to flash brand new MB526 with BL7: (did that for a few friends and the girl)
1. DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
2. DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.sbf
but the plan was overthrown by my phone. It flashed through the whole process but was stuck at the the "please manually power up this phone"-screen in RSDlite, the phone was connected but at the splash screen. Battery out, the PASS would only appear in RSD if I boot directly into bootloader again. Otherwise this splash screen makes my mad. It doesnt boot.
I tried to flash the alternative, chinese, root ROM for BL7; samesame, but different.
Downloaded RSDlite 6.14, Mdriver 5.9 on a win7 machine, used about all the BL7 ROMs I could find on the site: sbf.droid-developers.org/umts_jordanplus/ The last one being the [Retail British] sbf.droid-developers.org/umts_jordanplus/DEFYPLUS_U3_4.5.1-134_DFP-231_BLUR_SIGN_USADEFYEMARAB1B8RTGB005.0R_PDS03C_USAJRDNGIBRRTGB_P023_A025_M002_Service1FF.sbf.gz
samesame
:crying:
Now I cannot boot into the motorola recovery. Theres just the background picture but no menu. As far as I know, flashing an SBF is all that I can do. Anyone has got an idea, which ROM to try or what else to do ?
Thanks in advance
Click to expand...
Click to collapse
Flash the sbf again.
If you encounter please manually power up the phone unplug the device from PC, reboot into stock recovery and wipe data/factory reset. After that reboot
Trolls, trolls everywhere

ppero196 said:
Flash the sbf again.
If you encounter please manually power up the phone unplug the device from PC, reboot into stock recovery and wipe data/factory reset. After that reboot
Trolls, trolls everywhere
Click to expand...
Click to collapse
thank you. stock recovery. there is no stock recovery. MB526. BL7. Just the droid and a triangle with the "!" inside the triangle if I try to boot into stock recovery. I remember having this problem with my hannspad and there was a flashable ROM with just the stock recovery. Is there something comparable for the defy? only the recovery or is the BL7 the problem here?

butcherr said:
thank you. stock recovery. there is no stock recovery. MB526. BL7. Just the droid and a triangle with the "!" inside the triangle if I try to boot into stock recovery. I remember having this problem with my hannspad and there was a flashable ROM with just the stock recovery. Is there something comparable for the defy? only the recovery or is the BL7 the problem here?
Click to expand...
Click to collapse
That is Stock recovery (droid and yellow triangle) .Try pressing Vol Up and Vol Down simultaneously to get the menu. If that doesn't work TAP in the lower right hand corner of the screen to get the menu. Tap around a bit to get the right spot.
The newer stock recovery works off touch screen instead of the rocker buttons.

_ossie_ said:
That is Stock recovery (droid and yellow triangle) .Try pressing Vol Up and Vol Down simultaneously to get the menu. If that doesn't work TAP in the lower right hand corner of the screen to get the menu. Tap around a bit to get the right spot.
The newer stock recovery works off touch screen instead of the rocker buttons.
Click to expand...
Click to collapse
Thank you VERY much. I spent too much time with CWM it appears. I dont remember having used the stock recovery once. I thought BL7 was my enemy with that screen. My phone must feel like its been gangbangraped now with all the different ROMS I have flash upon it. Thanks again, quarx build 20121018+v4 running. Am creating a backup right now.

When I connect to pc (battery empty) it charges white led then boots up hangs on motorola logo for sometime then shutsdown to white led again, is that normal?

Help! I Think I Soft Bricked my M8 GPE..?

So my M8 GPE is S-Offed, bootloader unlocked, and rooted. The new 4.4.3 update came out today, and I wanted to upgrade to that. I downloaded the OTA on my device from one of the threads for the GPE OTA here, and when I went in CWM to flash it, it said something about the build.prop being unable to verify/find.
I read somewhere (I think on Android Central) that someone else was trying to do a very similar thing (with a different phone though). Their build.prop was edited, and it needed to be stock to accept the update. Some people advised him to just get the stock build.prop, put it in the folder, and make a backup of the one he had for it to update (and then he could put the other back).
After reading that, I went to the thread on here with the M8 GPE dumps, downloaded the one for 4.4.2, and extracted the build.prop and did what I explained above.
After that, I went to the recovery, and tried to flash the OTA. Still didn't work, and had the same error. I went to reboot, and after pressing that the screen went black. I wasn't able to get to the splash screen after that, just the screen that says Google with the unlocked padlock at the bottom.
I can't get anything now, and would really like to fix this ASAP. It's not my main phone (my main number is in my iPhone), so it's not as bad as it could have been, but it's really annoying.
I'm starting to think that maybe build.props are device specific? It really didn't make sense that it didn't work the first time, because there were plenty of articles saying that rooted Nexus 5s with custom recoveries could just flash OTAs like I initially tried to (because the GPE phones are so similar, and there's nothing out there about the M8 GPE, I figured everything should be similar).
Anyone have any ideas? I realized I was probably a little quick to go messing around, but I really didn't think installing an OTA could cause this much trouble
Thanks!

To be more clear:
The only thing I can get is this. And that's by holding power+volume up or power+volume up and down for 10 seconds. Nothing happens when I hold power+down or just power (even for a minute):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my iPhone 5s using Tapatalk

Can you get in to recovery or in the bootloader? Sorry can't see your picture seems broken
Sent from my HTC One_M8 using XDA Premium 4 mobile app

Hawkysoft said:
Can you get in to recovery or in the bootloader? Sorry can't see your picture seems broken
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
+1
Why the heck will you edit build.prop when it was not modified.
Time to flash custom recovery and restore a GPE nandroid
Don't lock the bootloader in any case
---------- Post added at 12:04 AM ---------- Previous post was at 12:03 AM ----------
Need stock recovery to flash ota on most phones

Hawkysoft said:
Can you get in to recovery or in the bootloader? Sorry can't see your picture seems broken
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It says Google with an unlocked padlock on the bottom. The background is totally black. No combination of buttons can get me anywhere else.
Sent from my iPhone 5s using Tapatalk

SaHiLzZ said:
+1
Why the heck will you edit build.prop when it was not modified.
Time to flash custom recovery and restore a GPE nandroid
Don't lock the bootloader in any case
---------- Post added at 12:04 AM ---------- Previous post was at 12:03 AM ----------
Need stock recovery to flash ota on most phones
Click to expand...
Click to collapse
I wasn't sure if it was edited by S-Off, AdAway, or rooting.
I now remember reading somewhere that if you reflagged stock recovery and did the update that would work... Now I understand why I have the stock recovery on my PC
I totally forgot about that while I was doing this. I didn't remember until now for some reason. If power+down doesn't do anything, what can I do?
Sent from my iPhone 5s using Tapatalk

SolarTrans said:
I wasn't sure if it was edited by S-Off, AdAway, or rooting.
I now remember reading somewhere that if you reflagged stock recovery and did the update that would work... Now I understand why I have the stock recovery on my PC
I totally forgot about that while I was doing this. I didn't remember until now for some reason. If power+down doesn't do anything, what can I do?
Sent from my iPhone 5s using Tapatalk
Click to expand...
Click to collapse
Can you at the very least pick up the phone when connecting to a PC? If so you could send command from there to boot into bootloader and work from there?

SolarTrans said:
I wasn't sure if it was edited by S-Off, AdAway, or rooting.
I now remember reading somewhere that if you reflagged stock recovery and did the update that would work... Now I understand why I have the stock recovery on my PC
I totally forgot about that while I was doing this. I didn't remember until now for some reason. If power+down doesn't do anything, what can I do?
Sent from my iPhone 5s using Tapatalk
Click to expand...
Click to collapse
It will HAVE to work.
Press and hold Volume Down + Power.. and it will get you in bootloader mode.

BerndM14 said:
Can you at the very least pick up the phone when connecting to a PC? If so you could send command from there to boot into bootloader and work from there?
Click to expand...
Click to collapse
No nothing... When the Google logo shows up, it shows up as a DVD drive with no disk in it until the logo disappears a couple seconds later.
Sent from my iPhone 5s using Tapatalk

SaHiLzZ said:
It will HAVE to work.
Press and hold Volume Down + Power.. and it will get you in bootloader mode.
Click to expand...
Click to collapse
I just did that for 5 minutes straight. Nothing happened D:
Sent from my iPhone 5s using Tapatalk

SolarTrans said:
No nothing... When the Google logo shows up, it shows up as a DVD drive with no disk in it until the logo disappears a couple seconds later.
Sent from my iPhone 5s using Tapatalk
Click to expand...
Click to collapse
Odd then, when the phone usually boots while connected to PC it already gets picked up by the PC, though it won't load most things for sure. When I tried to install an app and it wanted to reboot it got hung up on the splash screen too, none of the hardware buttons worked(Like you're experiencing now, though I know your problem is more than just an app). When I plugged it into PC it gave the notification sound on PC that it was loading drivers, I just opened the command prompt, adb devices and it showed the device connected, could reboot into bootloader form there.

BerndM14 said:
Odd then, when the phone usually boots while connected to PC it already gets picked up by the PC, though it won't load most things for sure. When I tried to install an app and it wanted to reboot it got hung up on the splash screen too, none of the hardware buttons worked(Like you're experiencing now, though I know your problem is more than just an app). When I plugged it into PC it gave the notification sound on PC that it was loading drivers, I just opened the command prompt, adb devices and it showed the device connected, could reboot into bootloader form there.
Click to expand...
Click to collapse
See it isn't doing that on the PC though. I have the drivers, but it doesn't notice it while it's off
Sent from my iPhone 5s using Tapatalk

SolarTrans said:
See it isn't doing that on the PC though. I have the drivers, but it doesn't notice it while it's off
Sent from my iPhone 5s using Tapatalk
Click to expand...
Click to collapse
Of course.
I mean though, the necessary drivers already load up as soon as the phone starts up, hence why you can use command prompt in fastboot mode even though the phone itself didn't fully start up, but if adb doesn't pick up your phone then I guess it won't be much help then to get you into fastboot mode or even send a command to reboot the device into fastboot.
So no hardware and software method to do this

BerndM14 said:
Of course.
I mean though, the necessary drivers already load up as soon as the phone starts up, hence why you can use command prompt in fastboot mode even though the phone itself didn't fully start up, but if adb doesn't pick up your phone then I guess it won't be much help then to get you into fastboot mode or even send a command to reboot the device into fastboot.
So no hardware and software method to do this
Click to expand...
Click to collapse
Yeah... You can see the unlocked padlock on the bottom when you can get it to show something, so I'm afraid to send it to Google.
I've looked around on the internet, and I haven't seen anyone who's been unable to boot anything because they changed the .prop...

If there's some way to maybe drain the battery completely so they can't even turn it on a little bit, that may help

What about holding the power button for a minute?

SaHiLzZ said:
What about holding the power button for a minute?
Click to expand...
Click to collapse
Don't think it'll work. I had it happen to me as well, like I said in my one post up there. Tried to install the Root Companion for GSAM Battery Monitor, it wanted a reboot to complete, pushed the button to do reboot and it got hung up right after device turned "off" to reboot, it didn't even show HTC logo or nothing. Tried pushing button combinations, holding power in etc it didn't do anything, none of the hardware reboot methods worked.
Plugged in USB cable and hooked it up to computer, opened my command prompt in adb folder and checked to see if it picked up the device. It did and I rebooted the device from the command prompt, no problem. So I don't know the hardware combinations hardly ever works, but what I find odd is that the 'software' (Through command prompt) doesn't work either. He said that it picks up the device as DVD drive with no disk, so surely the computer picked it up, so adb should as well Strange that it doesn't, I would have thought it could pick up the device as soon as it gets powered on, hence why we can just connect it in fastboot when we boot directly into it(Hardware method). Does it load seperate drivers(For PC) for a fastboot boot and a normal one?
Oh well... Use it for BBQ fire, buy a new one

I checked adb devices, and nothing showed up... Damn shame. How about this? Break screen>send to HTC advantage>get free replacement?
Sent from my iPhone 5s using Tapatalk

To reboot the phone you have to hold volume UP and power for about 20 seconds. Do this and as soon as the Google logo goes away hold volume DOWN only. It should then boot into the boot loader and you can then carry on from there...don't connect it to your PC until you're in the bootloader

Update: so for whatever reason, the phone was draining battery the entire time while it was "off" now, after totally draining the battery, I'm able to get it to show it's charging and access recovery mode.
Can I manually change by prop file from there, or should I just restore the OS?
Sent from my iPhone 5s using Tapatalk

FTV 2015, sloane-5.2.4.0-rooted_r1 rom, bricked flashing Magisk 12 in drunken stupor

Hi All,
I managed to brick my Fire TV 2 by flashing Magisk 12 whilst under the influence.
The unit now boots to the white Amazon logo, the power light goes from white to orange and then it restarts (bootloop).
I have tried various fixes covered on the AFTV site to get back in to recovery but to no avail.
Attempted to re-root the unit which fails with the message "error: source file is larger than target file!"
During the re-root process, It does load the preloader and the power light pulses white until I remove the power lead. Is there anything I can do from here?
Details: sloane-5.2.4.0-rooted_r1 rom with TWRP recovery v3.0.0-5
Thanks.

Reflash the pre rooted rom from recovery

m1steron said:
Hi All,
I managed to brick my Fire TV 2 by flashing Magisk 12 whilst under the influence.
The unit now boots to the white Amazon logo, the power light goes from white to orange and then it restarts (bootloop).
I have tried various fixes covered on the AFTV site to get back in to recovery but to no avail.
Attempted to re-root the unit which fails with the message "error: source file is larger than target file!"
During the re-root process, It does load the preloader and the power light pulses white until I remove the power lead. Is there anything I can do from here?
Details: sloane-5.2.4.0-rooted_r1 rom with TWRP recovery v3.0.0-5
Thanks.
Click to expand...
Click to collapse
The 2nd main requisite for Magisk is a fully unlocked bootloader. And only a small % of FTV1's have this done. If you can still go into TWRP. Then just flash the same PreRooted ROM you had installed before.

Y314K said:
The 2nd main requisite for Magisk is a fully unlocked bootloader. And only a small % of FTV1's have this done. If you can still go into TWRP. Then just flash the same PreRooted ROM you had installed before.
Click to expand...
Click to collapse
Sorry but it's a Fire TV 2 and the problem is that I can't get in to the TWRP recovery. I have tried multiple methods including the remote button presses and keyboard combinations.
The device isn't recognised over a network or USB adb. Before I bricked it, both USB and ADB debugging were enabled.

Have you tried the unbrick method?.
https://forum.xda-developers.com/newreply.php?do=newreply&p=65281865
I unbricked mine this morning

CFKod said:
Have you tried the unbrick method?.
https://forum.xda-developers.com/newreply.php?do=newreply&p=65281865
I unbricked mine this morning
Click to expand...
Click to collapse
Yes I have tried this but receive the following error:
error: source file is larger than target file!
I have tried using different versions of recovery and installer.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: Your links didn't work properly. Wasn't until I looked at it again that I saw the bit about an unbrick image. Trying it now, fingers crossed...

OK, I have tried using both unbrick methods (unbrick.img and unbrick+ramdisk.img) they completed successfully but didn't resolve the issue (white Amazon logo, pulsing orange light bootloop).
Presently I am trying to inject the prerooted rom's boot.img using the "mediatek_inject firetv2 COM4 boot.img /boot -" command. At 4% so far...

Success! It took about 5 hours to flash the boot.img. Upon restarting the device it loaded to the white Amazon logo with the glowing white power led but this time it didn't reboot (no yellow light). It seemed stuck at this point so I started pressing the keyboard recovery buttons and viola, it opened TWRP. Flashed the latest pre-rooted rom, cleared caches and rebooted. Happily, all my data and apps were unaffected.
A lesson learnt. Don't mess about with technical things when you are drunk!
Thanks for all your help.

m1steron said:
Success! It took about 5 hours to flash the boot.img. Upon restarting the device it loaded to the white Amazon logo with the glowing white power led but this time it didn't reboot (no yellow light). It seemed stuck at this point so I started pressing the keyboard recovery buttons and viola, it opened TWRP. Flashed the latest pre-rooted rom, cleared caches and rebooted. Happily, all my data and apps were unaffected.
A lesson learnt. Don't mess about with technical things when you are drunk!
Thanks for all your help.
Click to expand...
Click to collapse
Thanks have wondered about magisk as more apps check root. Obviously a no no
Sent from my SM-G955F using Tapatalk

m1steron said:
Success! It took about 5 hours to flash the boot.img. Upon restarting the device it loaded to the white Amazon logo with the glowing white power led but this time it didn't reboot (no yellow light). It seemed stuck at this point so I started pressing the keyboard recovery buttons and viola, it opened TWRP. Flashed the latest pre-rooted rom, cleared caches and rebooted. Happily, all my data and apps were unaffected.
A lesson learnt. Don't mess about with technical things when you are drunk!
Thanks for all your help.
Click to expand...
Click to collapse
Just think you did some Magisk v12 on non-Unlocked Bootloader FTV test. I am just glad you at least got your device back to a normal state. Took one for the modding scene. Thanks drunken M1steron. I know sober M1steron would not have approved.

Hello m1steron,
Thxs for sharing your experience.
Krgds

m1steron said:
Success! It took about 5 hours to flash the boot.img. Upon restarting the device it loaded to the white Amazon logo with the glowing white power led but this time it didn't reboot (no yellow light). It seemed stuck at this point so I started pressing the keyboard recovery buttons and viola, it opened TWRP. Flashed the latest pre-rooted rom, cleared caches and rebooted. Happily, all my data and apps were unaffected.
A lesson learnt. Don't mess about with technical things when you are drunk!
Thanks for all your help.
Click to expand...
Click to collapse
Trying to flash boot.img the forth time using mediatek inject command... It stucks at around 50% each time. Should i try it again and again or leave it?

Servet83 said:
Trying to flash boot.img the forth time using mediatek inject command... It stucks at around 50% each time. Should i try it again and again or leave it?
Click to expand...
Click to collapse
Did it finish? I left mine flashing for most of the day so I don't know if it paused at 50% or not.

m1steron said:
Did it finish? I left mine flashing for most of the day so I don't know if it paused at 50% or not.
Click to expand...
Click to collapse
No, it didn't finish. Yesterday it stopped at 67%. Don't know what to do alternatively...is it cause im using a windows pc?

Servet83 said:
No, it didn't finish. Yesterday it stopped at 67%. Don't know what to do alternatively...is it cause im using a windows pc?
Click to expand...
Click to collapse
I used Windows 10 on an old works laptop. Could you describe all the steps you are taking?

m1steron said:
I used Windows 10 on an old works laptop. Could you describe all the steps you are taking?
Click to expand...
Click to collapse
1. Connect to FTV using a2a usb cable
2. start handshake
3. Power on Box (handshake complete)
4. Start mediatek inject command (continue with 'y')
5. Wait writing filesystem...
Here are 2 Screenshots. One for the install_firetv2_recovery process and the other dor mediatek inject process.

Servet83 said:
1. Connect to FTV using a2a usb cable
2. start handshake
3. Power on Box (handshake complete)
4. Start mediatek inject command (continue with 'y')
5. Wait writing filesystem...
Here are 2 Screenshots. One for the install_firetv2_recovery process and the other dor mediatek inject process.
Click to expand...
Click to collapse
Thanks, are you using the extracted boot.img from the same pre-rooted rom that is installed on your device?
Also, this is where I got the information from: https://forum.xda-developers.com/fire-tv/development/firetv-2-unbrick-image-t3313349/page3
rbox should be able to help.

m1steron said:
Thanks, are you using the extracted boot.img from the same pre-rooted rom that is installed on your device?
Also, this is where I got the information from: https://forum.xda-developers.com/fire-tv/development/firetv-2-unbrick-image-t3313349/page3
rbox should be able to help.
Click to expand...
Click to collapse
Yes, i am using the same boot.img (5.2.1.1).
How did u solve the error "source file larger target file" while running the install recovery batch?
Trying to get in touch with rbox. Thank u so far!

Servet83 said:
Yes, i am using the same boot.img (5.2.1.1).
How did u solve the error "source file larger target file" while running the install recovery batch?
Trying to get in touch with rbox. Thank u so far!
Click to expand...
Click to collapse
I didn't so I tried the below:
m1steron said:
OK, I have tried using both unbrick methods (unbrick.img and unbrick+ramdisk.img) they completed successfully but didn't resolve the issue (white Amazon logo, pulsing orange light bootloop).
Presently I am trying to inject the prerooted rom's boot.img using the "mediatek_inject firetv2 COM4 boot.img /boot -" command. At 4% so far...
Click to expand...
Click to collapse

m1steron said:
I didn't so I tried the below:
Click to expand...
Click to collapse
Didn't work for me i remember that usb debugging was turned of before bricking the device and maybe thats the issue now...

Requesting urgent help

Hello everyone
I was trying to do an OTA update for AOSP Extended custom rom on a Lenovo ZUK Z2 Plus phone from its then v6.2 to v6.6 and along the way encountered many problems and now my phone is now in an unusable state.
I'll state the issues I encountered in order:
-Do above mentioned OTA update for AOSP Extended. It downloads and shows it installed successfully but upon restart it refuses to boot the OS
-Stuck on that black screen with options for recovery. I think it is called fastboot screen? or perhaps bootloader screen. The one where you use volume keys to navigate.
-I chose Recovery option and it opened up TWRP. I clicked Install and selected my ROM manually but then was unable to install a newly downloaded AOSP due to an error #7
-I figure maybe updating TWRP to the latest version will help. I flash TWRP img and reboot.
-Upon reboot I find myself unable to even get back into recovery!.. the option to enter recovery exists but whenever I pick it it just restarts and throws me back to the fastload/bootloader black screen.
-I was stuck here for several hours before deciding to flash stock firmware via QFIL since fastboot was still working fine.
-I successfully flash stock firmware through QFIL using my computer. I reboot the phone and now a new issue:
I press the power button to turn my phone on but my phone screen briefly flashes a dimly lit black screen and then goes off, again flashes the black screen and goes off again. It keeps repeating this in a continuous unending loop.
I am literally out of ideas. I don't even want to get the stock rom anymore just want a usable phone again : (
I would greatly appreciate any help please.
Thank you for your time.

I wanted to post an update.
I was able to get out of this strange loop by holding power button and pressing volume up as soon as the led lit once and before the ZUK logo popped up.
Afterwards I did the Power+ Volume UP + Plug USB cable to get the qualcomm port thing and re-try flashing Stock firmware. Unfortunately the same problem after flashing, no errors in log, with the black screen being lit and then off again in loop. Could anyone tell me how to get to custom rom or even stock firmware from this position please.

The only thing you can do is QFIL stock rom. That should solve the problem. Try doing it correctly one more time and report with any type of errors.
Don't worry it'll be fine. Any type of software related problems can be solved just have to keep trying, who knows what solution may work!

the_harsh said:
The only thing you can do is QFIL stock rom. That should solve the problem. Try doing it correctly one more time and report with any type of errors.
Don't worry it'll be fine. Any type of software related problems can be solved just have to keep trying, who knows what solution may work!
Click to expand...
Click to collapse
Could you guide me to a specific stock rom I can use with QFIL method please?
I used a ' Lenovo_Zuk_Z2_Z2132_EN_OPEN_USER_Q01080.2_N_ZUI_2.5.104_ST_170418_QPST ' however now whenever I power my phone it takes me to this screen always:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Maky-313 said:
Could you guide me to a specific stock rom I can use with QFIL method please?
I used a ' Lenovo_Zuk_Z2_Z2132_EN_OPEN_USER_Q01080.2_N_ZUI_2.5.104_ST_170418_QPST ' however now whenever I power my phone it takes me to this screen always:
Click to expand...
Click to collapse
Flashing this ROM should solve the issue however flash again to confirm. I was in the same situation before but I don't remember exactly what I did.
Try pressing all three buttons (+- and power).

Maky-313 said:
Could you guide me to a specific stock rom I can use with QFIL method please?
I used a ' Lenovo_Zuk_Z2_Z2132_EN_OPEN_USER_Q01080.2_N_ZUI_2.5.104_ST_170418_QPST ' however now whenever I power my phone it takes me to this screen always:
Click to expand...
Click to collapse
okay this is strange....never encountered this screen before. Can you put your phone to EDL mode? If yes then try doing a QFIL any 3.5+ ZUI. It should solve the problem!
Although I've once successfully flashed ZUI 4.0.199, you can follow this guide for 3.5:
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/oreo-zuio3-5-099dev-z2-t3719682

the_harsh said:
okay this is strange....never encountered this screen before. Can you put your phone to EDL mode? If yes then try doing a QFIL any 3.5+ ZUI. It should solve the problem!
Although I've once successfully flashed ZUI 4.0.199, you can follow this guide for 3.5:
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/oreo-zuio3-5-099dev-z2-t3719682
Click to expand...
Click to collapse
I am currently downloading a Z2131_CN_OPEN_USER_Q00030.1_O_ZUI_3.5.389_ST_180525_qpst.zip for another thread. Is this the same as one of the ones in the thread linked by you? If not I'll abort.
Also, I previously had AOSP 6.2 which iirc was based on Android 9.0, do you feel perhaps me trying to flash older stock roms such as the earlier oreo(I think) based ones are causing issues? or is that not a problem flashing older android version based firmware/roms.

Maky-313 said:
I am currently downloading a Z2131_CN_OPEN_USER_Q00030.1_O_ZUI_3.5.389_ST_180525_qpst.zip for another thread. Is this the same as one of the ones in the thread linked by you? If not I'll abort.
Also, I previously had AOSP 6.2 which iirc was based on Android 9.0, do you feel perhaps me trying to flash older stock roms such as the earlier oreo(I think) based ones are causing issues? or is that not a problem flashing older android version based firmware/roms.
Click to expand...
Click to collapse
well, i guess you've downloaded and tried it as it's been more than an hour now. also if you had AEX (not AOSP I presume) 6.2 then you must have flashed 3.5 to update the firmware, so flashing older one can be a problem. Is the new one working?

the_harsh said:
well, i guess you've downloaded and tried it as it's been more than an hour now. also if you had AEX (not AOSP I presume) 6.2 then you must have flashed 3.5 to update the firmware, so flashing older one can be a problem. Is the new one working?
Click to expand...
Click to collapse
I went ahead and downloaded the Zui.3.5.389.qpst from your earlier linked thread. I used QFIL just now to flash it, unfortunately the phone still won't boot.
When I press the power button the white LED turns on for a second and then goes off after which is just a Solid black screen throughout. Doesn't make difference if I press the power button and let go or hold the power button down the same behaviour each time.
This was also the behaviour on earlier flashes of 1_M_ZUI_2.0.093_ST_160811_qpst & 2_N_ZUI_2.5.104_ST_170418_QPST : (

Maky-313 said:
I went ahead and downloaded the Zui.3.5.389.qpst from your earlier linked thread. I used QFIL just now to flash it, unfortunately the phone still won't boot.
When I press the power button the white LED turns on for a second and then goes off after which is just a Solid black screen throughout. Doesn't make difference if I press the power button and let go or hold the power button down the same behaviour each time.
This was also the behaviour on earlier flashes of 1_M_ZUI_2.0.093_ST_160811_qpst & 2_N_ZUI_2.5.104_ST_170418_QPST : (
Click to expand...
Click to collapse
are you sure your phone is being recognized in PC correctly and the flashing stock ROM don't endup in any error?

the_harsh said:
are you sure your phone is being recognized in PC correctly and the flashing stock ROM don't endup in any error?
Click to expand...
Click to collapse
I think its recognised as the correct qualcomm device under ports in device manager but I will take a screenshot for you so you can have a look.
and later today I'll reflash and save a log this time for the same 3.5 ROM and share that as well.

Samirmathakiya said:
Flashing this ROM should solve the issue however flash again to confirm. I was in the same situation before but I don't remember exactly what I did.
Try pressing all three buttons (+- and power).
Click to expand...
Click to collapse
the_harsh said:
are you sure your phone is being recognized in PC correctly and the flashing stock ROM don't endup in any error?
Click to expand...
Click to collapse
guys it worked! I just decided to leave it plugged into the charger for a while and left.
After coming back I long-pressed the power button to make sure it was powered off before attempting to use the key combination to put it in EDL mode and I guess I pressed it too short or let go of the power perhaps but it booted right into the OS : )
I feel now that earlier perhaps the phone didn't have enough charge to go past the initial zuk booting logo perhaps? I did not charge it since yesterday and would only be plugged into the usb for edl attempts, perhaps that was just enough to get flashing but not enough to boot the phone. I now wonder if previous flashing attempts were indeed successful and I just didn't have the battery to get it past the initial boot logo screen : S...
One last request please : )
I would like you guys to advise a custom rom for me please. I am looking for a stock android experience wherein the UI is very smooth and slick, I would also like to have a long battery life please if possible. I don't play games etc. so 3d performance or processing power is not a priority.
Thank you.

Maky-313 said:
guys it worked! I just decided to leave it plugged into the charger for a while and left.
After coming back I long-pressed the power button to make sure it was powered off before attempting to use the key combination to put it in EDL mode and I guess I pressed it too short or let go of the power perhaps but it booted right into the OS : )
I feel now that earlier perhaps the phone didn't have enough charge to go past the initial zuk booting logo perhaps? I did not charge it since yesterday and would only be plugged into the usb for edl attempts, perhaps that was just enough to get flashing but not enough to boot the phone. I now wonder if previous flashing attempts were indeed successful and I just didn't have the battery to get it past the initial boot logo screen : S...
One last request please : )
I would like you guys to advise a custom rom for me please. I am looking for a stock android experience wherein the UI is very smooth and slick, I would also like to have a long battery life please if possible. I don't play games etc. so 3d performance or processing power is not a priority.
Thank you.
Click to expand...
Click to collapse
Stick with official lineage os now
https://download.lineageos.org/z2_plus

Maky-313 said:
guys it worked! I just decided to leave it plugged into the charger for a while and left.
After coming back I long-pressed the power button to make sure it was powered off before attempting to use the key combination to put it in EDL mode and I guess I pressed it too short or let go of the power perhaps but it booted right into the OS : )
I feel now that earlier perhaps the phone didn't have enough charge to go past the initial zuk booting logo perhaps? I did not charge it since yesterday and would only be plugged into the usb for edl attempts, perhaps that was just enough to get flashing but not enough to boot the phone. I now wonder if previous flashing attempts were indeed successful and I just didn't have the battery to get it past the initial boot logo screen : S...
One last request please : )
I would like you guys to advise a custom rom for me please. I am looking for a stock android experience wherein the UI is very smooth and slick, I would also like to have a long battery life please if possible. I don't play games etc. so 3d performance or processing power is not a priority.
Thank you.
Click to expand...
Click to collapse
Derp caf pie is also very good..
On it for 3 days now and quite stable rom.. definitely recommend

congratulations on getting it done! as a thankyou gesture you can give me party in Starbucks ? (JK).
For Custom ROM
If you want something with customizations I'd say go with AOSiP pie. The best and latest I've used.
But if you want to stick more to the stock Android side you should go with Lineage pie. It's the best in business.

the_harsh said:
congratulations on getting it done! as a thankyou gesture you can give me party in Starbucks (JK).
For Custom ROM
If you want something with customizations I'd say go with AOSiP pie. The best and latest I've used.
But if you want to stick more to the stock Android side you should go with Lineage pie. It's the best in business.
Click to expand...
Click to collapse
yup yup I went ahead with the Lineage OS 16 as it seemed to be very popular. So far so good.
Thank you and everyone else for your help. God bless : )