Develop Bugs

Galaxy Nexus Bricked

My nexus is from everyway shape or form bricked. I tried all forms of fixing it:
-Tried flashing stock image from fastboot
-tried flashing stock through odin
-tried flashing through recovery
-tried locking and unlocking the bootloader
What I noticed: I can flash different kernels and mods. But as soon as I try to flash a ROM that I already had saved on the SD it cancels the install and shows "(bad)". I also cannot mount /system to format it.
Also, when I try to flash anything thru odin or fastboot, everything works according to ODIN and I get the blue "PASS" sign, but when it reboots nothing sticks. I was able to use the Toolkit v7.8 to boot into TWRP recorvery, and it still doesnt work. NOTE: I can only boot into it with the Toolkit, I cant actually flash the recovery permanently.
I guess the system files became Read-Only.
I have no ROM currently loaded so I can only boot into Download mode/Fastboot and CWM recovery.

Things to try
acesofbelkan said:
My nexus is from everyway shape or form bricked. I tried all forms of fixing it:
-Tried flashing stock image from fastboot
-tried flashing stock through odin
-tried flashing through recovery
-tried locking and unlocking the bootloader
What I noticed: I can flash different kernels and mods. But as soon as I try to flash a ROM that I already had saved on the SD it cancels the install and shows "(bad)". I also cannot mount /system to format it.
Also, when I try to flash anything thru odin or fastboot, everything works according to ODIN and I get the blue "PASS" sign, but when it reboots nothing sticks. I was able to use the Toolkit v7.8 to boot into TWRP recorvery, and it still doesnt work. NOTE: I can only boot into it with the Toolkit, I cant actually flash the recovery permanently.
I guess the system files became Read-Only.
I have no ROM currently loaded so I can only boot into Download mode/Fastboot and CWM recovery.
Click to expand...
Click to collapse
It looks like you've tried just about everything and you are very capable of getting it done. My only suggestion is that when I thought I was bricked, I kept wiping all the data I could find. From CWM I started with a wipe data/factory reset and that had the best results for me. After that, wipe dalvik, wipe battery stats, and I tried loading a new ROM from sdcard. I wouldn't try to install a new kernel or any other mod until you successfully boot into your new(or old) ROM.
Like I said, you probably already knew all of this but I wanted to make sure all the bases were covered. If it doesn't help you, I hope it at least helps someone else. Good luck, and please post your progress!

try using fastboot to erase the system and other partition.
fastboot erase system
fastboot erase userdata
faseboot erase boot
fastboot erase recovery
Then flash stock from fastboot

Ok, I try the fast boot method today after work. I have a feeling it wont work until I can mount the system folder which is the sole problem if Im not mistaken. I wiped absolutely everything I could in CWM to no avail. So fastboot looks like the only choice

acesofbelkan said:
Ok, I try the fast boot method today after work. I have a feeling it wont work until I can mount the system folder which is the sole problem if Im not mistaken. I wiped absolutely everything I could in CWM to no avail. So fastboot looks like the only choice
Click to expand...
Click to collapse
Fastboot does not require mounting of anything -- it writes to the entire partition.

efrant said:
Fastboot does not require mounting of anything -- it writes to the entire partition.
Click to expand...
Click to collapse
I don't have the best knowledge when it comes to this. But if this is true then perhaps I lost root? When I was flashing a Rom my phone shut off and that's when these problems started. Would losing root be the cause of this?

acesofbelkan said:
I don't have the best knowledge when it comes to this. But if this is true then perhaps I lost root? When I was flashing a Rom my phone shut off and that's when these problems started. Would losing root be the cause of this?
Click to expand...
Click to collapse
No. Root has nothing to do with fastboot. Root has nothing to do with your device. Root has to do with the Android build that you are running.
When you are booted into the bootloader (i.e., fastboot mode), there is no Android OS running, so how can there be root?
The fastboot executable on your PC interacts directly with the bootloader, and it will wipe an entire partition, or write an image to a partition.

first off you need to download wugfresh's Gnex toolkit:
http://forum.xda-developers.com/show....php?t=1766475
second you need to install all the drivers if you haven't already.
then you need to choose your model type
after you will need to click on back to stock what it does is it resets everything, assuming your phone cant boot up choose not booting
once that is done you can choose the factory image which can be downloaded from Googles factory images or you can use the options provided
after that you follow all the steps provided in the tool kit. the tool kit is mostly automatic so it wont take allot of time.
once that is done you are back in stock and have lost everything but don't fret because you can root it again using the same tool kit.
quick point your phone still has an unlocked boot loader so don't worry about that.
once youve completed the above steps you should be back to your good old galaxy nexus home screen

NoorGnex said:
[snip]
first off you need to download wugfresh's Gnex toolkit
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1469909

efrant said:
http://forum.xda-developers.com/showthread.php?t=1469909
Click to expand...
Click to collapse
I've personally never had problems with tool kits and have found them very helpful, because of my busy schedule I don't have the time to do it myself even with my amateur coding skills, and have found only people who dont understand what there getting themselves into get bricked, thats not to say you cant brick your phone if your smart but if your smart you would have done a nandroid before flashing anything.
thanks again for that enlightening post

NoorGnex said:
first off you need to download wugfresh's Gnex toolkit:
http://forum.xda-developers.com/show....php?t=1766475
Click to expand...
Click to collapse
Link is bringing up a 404 error. Did the toolkit move locations?

JackG058 said:
Link is bringing up a 404 error. Did the toolkit move locations?
Click to expand...
Click to collapse
sorry
http://forum.xda-developers.com/showthread.php?t=1766475

NoorGnex said:
sorry
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
Thanks. I'm prepping for doing a ROM tomorrow night so trying to do my due diligence now.

JackG058 said:
Thanks. I'm prepping for doing a ROM tomorrow night so trying to do my due diligence now.
Click to expand...
Click to collapse
This is what you should be reading for due diligence...

efrant said:
This is what you should be reading for due diligence...
Click to expand...
Click to collapse
I will add this to my reading list, and send you my kind thanks.
edit: And bookmarking, of course.

I tried WugFresh's toolkit, everything was flashed(at least thats what the program said). But when the phone reboots, nothing, just logo screen

acesofbelkan said:
I tried WugFresh's toolkit, everything was flashed(at least thats what the program said). But when the phone reboots, nothing, just logo screen
Click to expand...
Click to collapse
That's what I was trying to get across earlier...
Use this: http://forum.xda-developers.com/showthread.php?t=1626895 That way, you can see where you are having issues.
And in case you missed it earlier: http://forum.xda-developers.com/showpost.php?p=30015315&postcount=9

NoorGnex said:
first off you need to download wugfresh's Gnex toolkit:
http://forum.xda-developers.com/show....php?t=1766475
second you need to install all the drivers if you haven't already.
then you need to choose your model type
after you will need to click on back to stock what it does is it resets everything, assuming your phone cant boot up choose not booting
once that is done you can choose the factory image which can be downloaded from Googles factory images or you can use the options provided
after that you follow all the steps provided in the tool kit. the tool kit is mostly automatic so it wont take allot of time.
once that is done you are back in stock and have lost everything but don't fret because you can root it again using the same tool kit.
quick point your phone still has an unlocked boot loader so don't worry about that.
once youve completed the above steps you should be back to your good old galaxy nexus home screen
Click to expand...
Click to collapse
Only after you learn what is going on in the background.
I think i'm going to stop trying to help people using toolkits if it seem that they did not even bordered to read up on fastboot and adb..

efrant said:
http://forum.xda-developers.com/showthread.php?t=1469909
Click to expand...
Click to collapse
+1

acesofbelkan said:
I tried WugFresh's toolkit, everything was flashed(at least thats what the program said). But when the phone reboots, nothing, just logo screen
Click to expand...
Click to collapse
This quote pretty much defines why people hate toolkits.

[Q] S-Off Recovery problem

Hello! Hi, I'm kinda new to all of this, and I downloaded all of this today. I've been reading a lot and watching a lot of videos, yet I nothing really seems to fix my devices problem.
I have a HTC One on the Verizon carrier and I have just recently S-Off'd it using Rumrunner (I used the Rom checker to make sure it was unlocked and it even says it is whenever i enter bootloader). Although I was successfully able to unlock my device, I seem to have trouble with entering into recovery mode. Whenever I try to go into Recovery mode, my device reads "Entering Recovery mode" in pink at the top for about 10-20 seconds. Then all of a sudden it just goes black and it reboots as if I had never even chosen to go into recovery mode. I don't know if this holds any significance, but I've noticed that my boot up logo only has "HTC ONE" on it, the writing "simply beautiful" is now removed.
I have tried using cmd and ADB to clear the cache, I've tried using ClockManager from Rom Manager, and I've tried multiple times on regular mode. None of them really seem to work and I don't really understand why. Can anyone please offer me some suggestions? Thank you.
Seriously I only want a transparent theme for my HTC One that's all LOL

@Cinestra hey so I'm also kind of new to this but I can try to help. So what custom recovery did you flash?

Chilidog said:
@Cinestra hey so I'm also kind of new to this but I can try to help. So what custom recovery did you flash?
Click to expand...
Click to collapse
I think the person didn't flash one. Flash twrp through fastboot. Don't use ROM manager cwm is getting old
Sent from my HTC6500LVW using xda app-developers app

cstrife999 said:
I think the person didn't flash one. Flash twrp through fastboot. Don't use ROM manager cwm is getting old
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Hello, thank you i very much appreciate your advice. I did not try flashing yet.
I just tried to flash TWRP by using Fastboot and the CMD. However I still get no luck. I entered everything in the command prompt fine and it responded nicely. However, whenever I try to go to Recovery mode, the screen just says "entering recovery mode...." and then just turns black 15 seconds later and reboots again :S

Cinestra said:
Hello, thank you i very much appreciate your advice. I did not try flashing yet.
I just tried to flash TWRP by using Fastboot and the CMD. However I still get no luck. I entered everything in the command prompt fine and it responded nicely. However, whenever I try to go to Recovery mode, the screen just says "entering recovery mode...." and then just turns black 15 seconds later and reboots again :S
Click to expand...
Click to collapse
Hmm... That is strange indeed...
Sent from my HTC6500LVW using xda app-developers app

I had the same problem and discovered that when i enter stock recovery, when the black screen appears, i had to press power+vol up to get it to show up. You may have to press them several times to get the timing right. Hope that helps!

cstrife999 said:
I think the person didn't flash one. Flash twrp through fastboot. Don't use ROM manager cwm is getting old
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
when I got my phone back from sonic, twrp wouldn't install for me so I had to use CWM.
OP should probably try both and make sure he's following the instructions here:
http://forum.xda-developers.com/showpost.php?p=45513789&postcount=2

I'm quite new to rooting as well. Seems we are having the same problem. I was able to get beaups' s-off exploit to work without any problems. When I load into HBoot it says the phone is unlocked and I've also used a Root Checker to determine the phone is rooted.
My next step was to try and install TWRP using fastboot. I ran a command prompt window using administrator rights during the whole process. Everything seemed to install just as it should. The problem is when I try to boot into recovery I'm having the same problem as Cinestra. I simply get the HTC logo screen with "Entering Recovery..." in pink letters at the top of the screen for around 15 seconds, then it reboots as if it would normally and restart the phone as usual. I have tried to reinstall the custom recovery step by step, using 'fastboot erase cache' before and after as well as using an older version of TWRP just in case that would help. Again, everything seems to install just fine but I still can not boot into recovery. I've also tried to see if the GooManager app would be of some help, but that is also not working for me.
I've since also tried flashing CWM but the same situation occurs. Install seems fine but no luck booting into recovery. ROM Manager was a no go as well.
I just can't figure this out. I've tried different cables, deleted and reinstalled HTC drivers/adb/fastboot, and multiple recovery images. I just gave beasleyj62's suggestion of holding down the power/volume down buttons after it goes to black when it starts to restart but that just put me into a bootloop sadly. Had to hold down the power button a few times to get it to boot correctly again. Any help on this would be greatly appreciated. Cheers.
I would also just like to add a little more info on my device in case this will help troubleshoot this. I'm using a Verizon HTC One with Software Number 1.10.605.10.

Same problem here. Tried flashing from fastboot, using goomanager, using rom manager, and from within the terminal emulator (can't find the command now but i think it was on the TWRP site).
Fastboot gives every indication it works, goomanager and rom manager give an error, and the emulator method appeared to work.
Tried to fastboot both TWRP and clockworkmod but neither worked.
At work right now but still investigating...
*edit: goomanager error states 'no recoveries found for your device.'

carassius-one said:
Same problem here. Tried flashing from fastboot, using goomanager, using rom manager, and from within the terminal emulator (can't find the command now but i think it was on the TWRP site).
Fastboot gives every indication it works, goomanager and rom manager give an error, and the emulator method appeared to work.
Tried to fastboot both TWRP and clockworkmod but neither worked.
At work right now but still investigating...
*edit: goomanager error states 'no recoveries found for your device.'
Click to expand...
Click to collapse
ROM manager and goomanager are not supported you have to flash Twrp or CWM via fastboot
Sent from my HTC6500LVW using XDA Premium 4 mobile app
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
I wonder if you guys are having problems because you tried to use rom manager or goomanager and it messed something up...
Sent from my HTC6500LVW using XDA Premium 4 mobile app

Chilidog said:
ROM manager and goomanager are not supported you have to flash Twrp or CWM via fastboot
Click to expand...
Click to collapse
Thanks. That answers that part of the question.

Chilidog said:
ROM manager and goomanager are not supported you have to flash Twrp or CWM via fastboot
Sent from my HTC6500LVW using XDA Premium 4 mobile app
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
I wonder if you guys are having problems because you tried to use rom manager or goomanager and it messed something up...
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Didn't realize they weren't supported. Sadly, I don't think they are the culprit here. I tried to flash using fastboot first. I attempted it with 'openrecovery-twrp-2.6.3.0-m7.img' first then with the older version 'openrecovery-twrp-2.6.1.0-m7.img' next. It was the same issue with both. I didn't attempt using GooManager until after I had used fastboot, though GooManager just failed to initialize the install. I mean it didn't even run or change anything as far as I can tell, and simply gave an error back saying "No recoveries were found for your advice".
Did the same thing with CWM and ROM Manager. I installed CWM from fastboot. Only after seeing the same thing happen when I tried to install TWRP did I give ROM Manager a shot. This also just gave an error message without initializing any install. Thanks for the input though.

Prizm432 said:
Didn't realize they weren't supported. Sadly, I don't think they are the culprit here. I tried to flash using fastboot first. I attempted it with 'openrecovery-twrp-2.6.3.0-m7.img' first then with the older version 'openrecovery-twrp-2.6.1.0-m7.img' next. It was the same issue with both. I didn't attempt using GooManager until after I had used fastboot, though GooManager just failed to initialize the install. I mean it didn't even run or change anything as far as I can tell, and simply gave an error back saying "No recoveries were found for your advice".
Did the same thing with CWM and ROM Manager. I installed CWM from fastboot. Only after seeing the same thing happen when I tried to install TWRP did I give ROM Manager a shot. This also just gave an error message without initializing any install. Thanks for the input though.
Click to expand...
Click to collapse
Yeah...I tried the fastboot method first too, for both TWRP and CWM. I really doubt that is the problem.

Two thoughts:
1. Did you have any issues during the S-OFF? How many pours did it take? My thoughts here are that the S-OFF wasn't, for whatever reason, fully clean, which may suggest that you relock and S-ON your phone, and reapply Rumrunner.
2. Did you flash with the decrypted RUU? I would flash the phone with that (the link is somewhere in this subforum) and then try to flash a recovery image.
carassius-one said:
Yeah...I tried the fastboot method first too, for both TWRP and CWM. I really doubt that is the problem.
Click to expand...
Click to collapse

godhamba said:
Two thoughts:
1. Did you have any issues during the S-OFF? How many pours did it take? My thoughts here are that the S-OFF wasn't, for whatever reason, fully clean, which may suggest that you relock and S-ON your phone, and reapply Rumrunner.
2. Did you flash with the decrypted RUU? I would flash the phone with that (the link is somewhere in this subforum) and then try to flash a recovery image.
Click to expand...
Click to collapse
1. I think it was 3 or 4 pours. Seemed to work flawlessly.
2. Still trying to learn which includes learning what an ruu is. Maybe that is my problem. I ran rumrunner and then have been trying to flash a recovery ever since...with no other steps.

godhamba said:
Two thoughts:
1. Did you have any issues during the S-OFF? How many pours did it take? My thoughts here are that the S-OFF wasn't, for whatever reason, fully clean, which may suggest that you relock and S-ON your phone, and reapply Rumrunner.
2. Did you flash with the decrypted RUU? I would flash the phone with that (the link is somewhere in this subforum) and then try to flash a recovery image.
Click to expand...
Click to collapse
1. Nope, I had no issues while doing the S-Off. It took 3 pours for me.
2. I haven't used any RUU for this. So you suggest going back to S-On and locked, then using the RUU? Sorry, still new to the whole process so just want to be clear on procedure. Yeah, I've been considering going back to complete stock and starting from scratch again. I'll give that a go later tonight if I can't come up with anything else.
Thanks.

No, no. The only RUU available is a decrypted one, which can only be flashed while S-OFF. So the ideas I put down were distinct, and not steps. My thought is that either (i) you return yourself to full stock and non-root as is explained in a thread in this subforum, or alternatively, (ii) flash the RUU to get a fully untouched setup (the RUU contains the factory "rom", bootloader and recovery and will return it to being fresh from the factory) on the device and then flash the recovery.
Prizm432 said:
1. Nope, I had no issues while doing the S-Off. It took 3 pours for me.
2. I haven't used any RUU for this. So you suggest going back to S-On and locked, then using the RUU? Sorry, still new to the whole process so just want to be clear on procedure. Yeah, I've been considering going back to complete stock and starting from scratch again. I'll give that a go later tonight if I can't come up with anything else.
Thanks.
Click to expand...
Click to collapse

Cinestra said:
I just tried to flash TWRP by using Fastboot and the CMD. However I still get no luck. I entered everything in the command prompt fine and it responded nicely. However, whenever I try to go to Recovery mode, the screen just says "entering recovery mode...." and then just turns black 15 seconds later and reboots again :S
Click to expand...
Click to collapse
I had the same problem and yesterday I posted my fix in this Forum's TWRP thread.
I had been using
openrecovery-twrp-2.6.3.0-m7.img
What I really needed was
openrecovery-twrp-2.6.3.0-m7vzw.img
Go here: http://goo.im/devs/Flyhalf205/M7VZW/openrecovery-twrp-2.6.3.0-m7vzw.img

beasleyj62 said:
I had the same problem and discovered that when i enter stock recovery, when the black screen appears, i had to press power+vol up to get it to show up. You may have to press them several times to get the timing right. Hope that helps!
Click to expand...
Click to collapse
Thanks for your solution, unfortunately though, it doesn't seem to work.
jpradley said:
I had the same problem and yesterday I posted my fix in this Forum's TWRP thread.
I had been using
openrecovery-twrp-2.6.3.0-m7.img
What I really needed was
openrecovery-twrp-2.6.3.0-m7vzw.img
Click to expand...
Click to collapse
Hmm alright so you suggest flash this other version of TWRP instead? That would make sense because the link looks like it's specialized for Verizon. I will try that out today!
godhamba said:
Two thoughts:
1. Did you have any issues during the S-OFF? How many pours did it take? My thoughts here are that the S-OFF wasn't, for whatever reason, fully clean, which may suggest that you relock and S-ON your phone, and reapply Rumrunner.
2. Did you flash with the decrypted RUU? I would flash the phone with that (the link is somewhere in this subforum) and then try to flash a recovery image.
Click to expand...
Click to collapse
1. It took me about 3 pours. That is an interesting thought and I think it may very well be valid, but I would prefer not to reset or relock my device though.
2. I have not decrypted RUU yet because I was unfamiliar with the term. I may try this if the new TWRP code does not work

@Prizm432 it looks like you are flashing the wrong Twrp zip. It has to end in m7vzw.zip
Sent from my HTC6500LVW using XDA Premium 4 mobile app

I just screwed my phone and can't figure it out.

HTC M8 AT&T
I have been dealing with this all morning and I am about to blow my brains out.
I thought i was running twrp but was instead running CWM.
Previously had Cyanogen Mod working fine on the phone no issue. Just wanted android instead
Tried to install Android Revolution from zip. Boom done. Reboot
Encryption. Try all 10 passwords i EVER use a couple hundred times it seems.
Fail. So i go back to CWM and try to reset phone to factoy. Gives me error "unknown volume for path /sd-ext/
error mounting /sdcard/.android_secure!
Skipping Format
Data Wipe Complete
Boot up still asks for password try a hundred times again. Still nothing
Boot into fastboot to attempt to put TWRP on it. and no computer sees my phone in fastboot.
Any ideas how to save my phone?

Do you a nandroid backup? You can restore your phone and try one more time.
Tapatalked with my "refrigerator look" HTC one M8

Go me the noob. No nandroid.
Any other idea..

Do you get the ding when connecting the phone and are running a command prompt from the folder with fastboot binary and required files?
What response does 'fastboot devices' give?

ashyx said:
Do you get the ding when connecting the phone and are running a command prompt from the folder with fastboot binary and required files?
Click to expand...
Click to collapse
No and when i run adb devices i get nothing

xagesz said:
No and when i run adb devices i get nothing
Click to expand...
Click to collapse
Adb won't respond unless you sideload or boot Into os.
Check your usb cable, make sure it's the original cable and you have fastboot drivers installed.

ashyx said:
Adb won't respond unless you sideload or boot Into os.
Check your usb cable, make sure it's the originals cable and you have fastboot drivers installed.
Click to expand...
Click to collapse
I tried sideloading a rom. but still encryption screen. and Fastboot has worked before because i used it to install cwm. BOot into it how?

xagesz said:
I tried sideloading a rom. but still encryption screen. and Fastboot has worked before because i used it to install cwm. BOot into it how?
Click to expand...
Click to collapse
If you don't hear the ding then you either have a cable problem or a driver problem. Just re-install the drivers and check the cable
http://forum.xda-developers.com/showthread.php?t=2588979

ashyx said:
Adb won't respond unless you sideload or boot Into os.
Check your usb cable, make sure it's the original cable and you have fastboot drivers installed.
Click to expand...
Click to collapse
ashyx said:
If you don't hear the ding then you either have a cable problem or a driver problem. Just re-install the drivers and check the cable
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
I am working this angle now but even so what do I need to do to save my phone

xagesz said:
I am working this angle now but even so what do I need to do to save my phone
Click to expand...
Click to collapse
From what I seen you going to need to format the sd. You can see if twrp will format it but if that don't work try stock recovery and do a factory reset in bootloader.

Darknites said:
From what I seen you going to need to format the sd. You can see if twrp will format it but if that don't work try stock recovery and do a factory reset in bootloader.
Click to expand...
Click to collapse
DARKNITES YOU ARE THE MAN. I send you a case a beer. Anyway... CWM menu down at the bottom is format data and media. never spotted this before and did that and the phone finally went around the darn encryption menu. THank you.

xagesz said:
I am working this angle now but even so what do I need to do to save my phone
Click to expand...
Click to collapse
As said if you get fastboot working you can flash a custom recovery or stock. You can then download a stock nandroid back up from the stock backups thread then flash the required backup from custom recovery.
All explained in that thread.

ashyx said:
As said if you get fastboot working you can flash a custom recovery or stock. You can then download a stock nandroid back up from the stock backups thread then flash the required backup from custom recovery.
All explained in that thread.
Click to expand...
Click to collapse
Yeah. Fastboot was not working AT ALL. I tried and tried. But the issue is now resolved. Thanks.

xagesz said:
DARKNITES YOU ARE THE MAN. I send you a case a beer. Anyway... CWM menu down at the bottom is format data and media. never spotted this before and did that and the phone finally went around the darn encryption menu. THank you.
Click to expand...
Click to collapse
Don't drink beer but thanks away and no problem dude.

[Q] no root, no os, stuck on logo. big mess

hi folks. my stupidity has brought me a week full of sleepless nights.
i rooted my m8 a few months back and all was well untill i realised i couldnt get the otas . so i unrooted my device via supersu. then i tried to flash a stock rom but the file could not be found in twrp. i did wipe and ever since im stuck on d logo. i have tried a lot of things but nothing seems to work. im dieing for help.

rshbh said:
hi folks. my stupidity has brought me a week full of sleepless nights.
i rooted my m8 a few months back and all was well untill i realised i couldnt get the otas . so i unrooted my device via supersu. then i tried to flash a stock rom but the file could not be found in twrp. i did wipe and ever since im stuck on d logo. i have tried a lot of things but nothing seems to work. im dieing for help.
Click to expand...
Click to collapse
Are you s-off? Unlocked boot loader?

rshbh said:
hi folks. my stupidity has brought me a week full of sleepless nights.
i rooted my m8 a few months back and all was well untill i realised i couldnt get the otas . so i unrooted my device via supersu. then i tried to flash a stock rom but the file could not be found in twrp. i did wipe and ever since im stuck on d logo. i have tried a lot of things but nothing seems to work. im dieing for help.
Click to expand...
Click to collapse
If you can enter fastboot, flash latest twrp recovery, nuke everything and sideload a rom/put a rom in external sd and flash from there... Should work...

jsaxon2 said:
Are you s-off? Unlocked boot loader?
Click to expand...
Click to collapse
i am s-on and yes my bootloader is unlocked.

lukes91 said:
If you can enter fastboot, flash latest twrp recovery, nuke everything and sideload a rom/put a rom in external sd and flash from there... Should work...
Click to expand...
Click to collapse
thanks!! i'm a noob,. tell me, can i update and flash an updated twrp and rom without root and with my phone stuck on d logo screen??

rshbh said:
thanks!! i'm a noob,. tell me, can i update and flash an updated twrp and rom without root and with my phone stuck on d logo screen??
Click to expand...
Click to collapse
Hold down the power button and the vol. up button for 20 seconds or so.
As soon as it goes dead, switch from vol. up to vol. down.
Fastboot is where you are now.

xunholyx said:
Hold down the power button and the vol. up button for 20 seconds or so.
As soon as it goes dead, switch from vol. up to vol. down.
Fastboot is where you are now.
Click to expand...
Click to collapse
ok.. and then?

rshbh said:
ok.. and then?
Click to expand...
Click to collapse
And then the post above my last one.
Do what @lukes91 said and use ADB to fix it.

lukes91 said:
If you can enter fastboot, flash latest twrp recovery, nuke everything and sideload a rom/put a rom in external sd and flash from there... Should work...
Click to expand...
Click to collapse
could you pls elaborate? im finding this very technical and difficult. can u suggest a video or a step by step guide?

rshbh said:
could you pls elaborate? im finding this very technical and difficult. can u suggest a video or a step by step guide?
Click to expand...
Click to collapse
hi! well, to flash recovery it's plenty of tutorial around, and you can look on twrp official site too... to delete everything, just select full wipe in recovery and to sideload follow this guide http://teamw.in/ADBSideload

rshbh said:
could you pls elaborate? im finding this very technical and difficult. can u suggest a video or a step by step guide?
Click to expand...
Click to collapse
can you post the results for fastboot getvar all
(minus your Serial no and IMEI)
this is the basic instructions
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.8.1.0
http://techerrata.com/browse/twrp2/m8
fastboot flash recovery openrecovery-twrp-2.8.1.0-m8.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.renovaterom.co.uk/OneM8/ROMs/Renovate_4.5.0.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload Renovate_4.5.0.zip
make sure the rom is in the same folder as adb / fastboot

Cant enter recovery mode

I cant format,update,or enter revovery mode.Ive tried to turn off the phone and do that power button and volume up.Then i go press recovery,then the phone restarts and go to the same screen.Theres no error thingy showing.

Hi,
Reflash your recovery via fastboot command:
Code:
fastboot flash recovery [color="red"]recovery.img[/color]
Replace recovery.img with your prefered recovery's filename.
Sent from my GT-I9500

krasCGQ said:
Hi,
Reflash your recovery via fastboot command:
Code:
fastboot flash recovery [color="red"]recovery.img[/color]
Replace recovery.img with your prefered recovery's filename.
Sent from my GT-I9500
Click to expand...
Click to collapse
Fastboot undetected

haridzk said:
Fastboot undetected
Click to expand...
Click to collapse
Have you installed the USB driver?
Sent from my GT-I9500

krasCGQ said:
Have you installed the USB driver?
Sent from my GT-I9500
Click to expand...
Click to collapse
You mean using conputer?

New Z00A ZE551ML 3.15 firmware can't upgrade OTA manually
I have the same problem, although it is not likely the drivers.
When attempting to sideload the full firmware image, it errors out after a few seconds, stating that it cannot detect the device. I reboot the phone manually, then reboot bootloader from command prompt. try again and the same thing happens. First, I tried placing the file on an sd card, renaming it to MOFD_SDUPDATE but it failed after 25% and left me with the screen showing the "unplugged" icon. Now I cannot enter recovery at all. Attempted root, tethered, untethered, and no luck with any. I used an app before trying any of this to make sure it was not rooted or unlocked already. I'm running out of ideas. When I get home, I will try flashing just the droidboot.img as suggested in this thread: http://forum.xda-developers.com/zenfone2/help/unlock-bootloader-read-fix-t3138837.
Any other advice would be greatly appreciated. As I said my phone has
VERSION: WW-ASUS_Z00A-2.15.40.13 and failed to manually upgrade to 2.19.40

haridzk said:
You mean using conputer?
Click to expand...
Click to collapse
No, I mean USB Driver, for real. You can't do anything related to debugging without having the related drivers installed.
Sent from my GT-I9500

Quadro1972 said:
I have the same problem, although it is not likely the drivers.
When attempting to sideload the full firmware image, it errors out after a few seconds, stating that it cannot detect the device. I reboot the phone manually, then reboot bootloader from command prompt. try again and the same thing happens. First, I tried placing the file on an sd card, renaming it to MOFD_SDUPDATE but it failed after 25% and left me with the screen showing the "unplugged" icon. Now I cannot enter recovery at all. Attempted root, tethered, untethered, and no luck with any. I used an app before trying any of this to make sure it was not rooted or unlocked already. I'm running out of ideas. When I get home, I will try flashing just the droidboot.img as suggested in this thread: http://forum.xda-developers.com/zenfone2/help/unlock-bootloader-read-fix-t3138837.
Any other advice would be greatly appreciated. As I said my phone has
VERSION: WW-ASUS_Z00A-2.15.40.13 and failed to manually upgrade to 2.19.40
Click to expand...
Click to collapse
If you are getting the USB logo on your screen you're sh!t out of luck as it is a hard brick... You'll need to send back to ASUS to get rom put back on phone...

ultramag69 said:
If you are getting the USB logo on your screen you're sh!t out of luck as it is a hard brick... You'll need to send back to ASUS to get rom put back on phone...
Click to expand...
Click to collapse
I was very fortunate that it would still boot into the bootloader. As a result I was able to fix using these instructions and pre-rooted images, including an Asus recovery image:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
---------- Post added at 04:37 AM ---------- Previous post was at 04:33 AM ----------
Quadro1972 said:
I was very fortunate that it would still boot into the bootloader. As a result I was able to fix using these instructions and pre-rooted images, including an Asus recovery image:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Click to expand...
Click to collapse
Also, if anyone else attempts this fix, download the images using Google Chrome or it will error out, fail checksum