Database Users

[Q] Help 11/2013Tmobile mytouch 4g may be bricked? Unresponsive past Clockwork screen

I know this topic is not popular and most people may skip over it but please read. I am NO expert when it comes to this so if anybody can help out it would be most appreciated. I have a T-mobile My touch 4g( NOT the slide version) running ginger bread 2.3.4. I wanted to play a game called "Clash of clans" but it says i need firmware 4.1 or higher. I was bummed because T mobile stopped making upgrades for this phone a long time ago. I saw online from different threads and videos that I need to downgrade the firmware and go back to fre3vo 2.2. OK i'm fine with that. I had no Idea how adb worked so I saw a post on xda this site how to use it for dummies. I now know how to. I followed ALL steps from http://forum.xda-developers.com/showthread.php?t=1178912 on how I should go about this process. Everything went smooth up until the "Downgrading steps." I finally learned how to place the zip file named "PD15IMG.zip" in the root of sd card. Ok i had it. I also followed the manual downgrade routine. The phone went into boot-loader mode. The phone scanned the file and that took maybe 2 min before it asked me to update. I hit yes to update. I waited for the phone to update then it shut off. I guess the phone restarted to a black screen. The only thing I could see was the top portion bar where the battery and time info is. The rest of the screen was completely black. I took the battery out thinking that maybe the phone just needed to be restarted and this was the worst thing to happen. I turned the phone on and now the screen will NOT boot past the "t mobile mytouch 4g logo screen. I have no idea what to do from here. I went to go back to clockworkmod to see if i could repeat the process. The package scans like before then it asks me to update then I said yes. This is where the phone says its "updating" in pink letter on the side but NO progress is being made. Nothing happens and the phone seems unresponsive. I took the battery out and went back to clockworkmod. I tried to hit 'Factory Reset' but it just stays highlighted on factory reset and it wont move up and down. Nothing works. I took the battery out and re tried clockworkmod. I tried hitting recovery and then a "phone with a "green arrow" below shows up then the screen goes black and the phone vibrates 7 times then nothing else happens. I can no longer access the phone on my computer. Normally when I plugged it in the F: drive folder came up indicating I could change contents in the Sd card. I heard that you can change the setting using terminal and when i try typing "adb shell" it said it cannot find my phone and that my phone inst connected although it is connected to my computer. I have windows 7 Toshiba satellite so nothing is bad on the PC. Battery, cable, everything is fine no defects with the phone.
Also
A little information when ClockWorkMod is up. This is exactly what it says and this is exactly the color as it shows.
GLACIER PUT SHIP S-ON
HBOOT-0.89.0005
MICROP-0429
RADIO-26.11.04.03_M
eMMC-boot
Apr 14 2011, 13;18;22
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Since I can no longer access the phone on my pc I took the micro sim sd out and placed it in my samsung galaxy player 3.6 From there I can at least change what goes into the Sd card. I have searched countless hours and nothing else comes up. I CANNOT go back to the normal mode my phone used to be. I just freezes past mytouch4g screen. Please help anybody. I want to downgrade ginger bread 2.3.4 to fre3vo 2.2 so i can root and upgrade to jelly bean or something higher to play clash of clans since this phone wasn't compatable. Please somebody help. Can I ever use my phone again? Does this mean it's bricked? I'm an apple user so I have little experience with android. Somebody anybody help me out?
Here are a few links i used in the process
http://lifehacker.com/5853519/how-do-i-fix-my-bricked-android-phone
http://forum.xda-developers.com/showthread.php?t=863899
help me please

Bolt34 said:
I know this topic is not popular and most people may skip over it but please read. I am NO expert when it comes to this so if anybody can help out it would be most appreciated. I have a T-mobile My touch 4g( NOT the slide version) running ginger bread 2.3.4. I wanted to play a game called "Clash of clans" but it says i need firmware 4.1 or higher. I was bummed because T mobile stopped making upgrades for this phone a long time ago. I saw online from different threads and videos that I need to downgrade the firmware and go back to fre3vo 2.2. OK i'm fine with that. I had no Idea how adb worked so I saw a post on xda this site how to use it for dummies. I now know how to. I followed ALL steps from http://forum.xda-developers.com/showthread.php?t=1178912 on how I should go about this process. Everything went smooth up until the "Downgrading steps." I finally learned how to place the zip file named "PD15IMG.zip" in the root of sd card. Ok i had it. I also followed the manual downgrade routine. The phone went into boot-loader mode. The phone scanned the file and that took maybe 2 min before it asked me to update. I hit yes to update. I waited for the phone to update then it shut off. I guess the phone restarted to a black screen. The only thing I could see was the top portion bar where the battery and time info is. The rest of the screen was completely black. I took the battery out thinking that maybe the phone just needed to be restarted and this was the worst thing to happen. I turned the phone on and now the screen will NOT boot past the "t mobile mytouch 4g logo screen. I have no idea what to do from here. I went to go back to clockworkmod to see if i could repeat the process. The package scans like before then it asks me to update then I said yes. This is where the phone says its "updating" in pink letter on the side but NO progress is being made. Nothing happens and the phone seems unresponsive. I took the battery out and went back to clockworkmod. I tried to hit 'Factory Reset' but it just stays highlighted on factory reset and it wont move up and down. Nothing works. I took the battery out and re tried clockworkmod. I tried hitting recovery and then a "phone with a "green arrow" below shows up then the screen goes black and the phone vibrates 7 times then nothing else happens. I can no longer access the phone on my computer. Normally when I plugged it in the F: drive folder came up indicating I could change contents in the Sd card. I heard that you can change the setting using terminal and when i try typing "adb shell" it said it cannot find my phone and that my phone inst connected although it is connected to my computer. I have windows 7 Toshiba satellite so nothing is bad on the PC. Battery, cable, everything is fine no defects with the phone.
Also
A little information when ClockWorkMod is up. This is exactly what it says and this is exactly the color as it shows.
GLACIER PUT SHIP S-ON
HBOOT-0.89.0005
MICROP-0429
RADIO-26.11.04.03_M
eMMC-boot
Apr 14 2011, 13;18;22
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Since I can no longer access the phone on my pc I took the micro sim sd out and placed it in my samsung galaxy player 3.6 From there I can at least change what goes into the Sd card. I have searched countless hours and nothing else comes up. I CANNOT go back to the normal mode my phone used to be. I just freezes past mytouch4g screen. Please help anybody. I want to downgrade ginger bread 2.3.4 to fre3vo 2.2 so i can root and upgrade to jelly bean or something higher to play clash of clans since this phone wasn't compatable. Please somebody help. Can I ever use my phone again? Does this mean it's bricked? I'm an apple user so I have little experience with android. Somebody anybody help me out?
Here are a few links i used in the process
http://lifehacker.com/5853519/how-do-i-fix-my-bricked-android-phone
http://forum.xda-developers.com/showthread.php?t=863899
help me please
Click to expand...
Click to collapse
Bro calm down. I've been though panic attacks like this too lol
Open clockworkmod
To select or scroll use the TRACKPAD
Put a rom on your sdcard, find any in the resource bible in the development section
Do a factory reset and flash that rom
And yay,

N_otori0us_ said:
Bro calm down. I've been though panic attacks like this too lol
Open clockworkmod
To select or scroll use the TRACKPAD
Put a rom on your sdcard, find any in the resource bible in the development section
Do a factory reset and flash that rom
And yay,
Click to expand...
Click to collapse
-It won't allow me to use the track pad I can only use the volume up and down buttons to scroll. What rom should I put on my sd card? If you have a link or something that would be great.. Also when I try to factory reset the phone just freezes. I don't know what to do.

any rom
That screen you posted information from is called H-BOOT, it's like the factory boot loader. Clockwork MOD will show up after that but from what I'm gathering you didn't even install that in the first place. In H-BOOT you can only use the volume buttons and the power button to select so that is all normal.
So you downloaded the stock ROM and in the process of downgrading got stuck. If the SD card still works in other devices do you still have PD15IMG.zip on the card?
Also did you make sure to download the proper drivers for ADB and also for your phone? The ADB ones you should be able to find on this forum and the HTC ones you could get directly from you carriers website, and most likely somewhere on this forum. It will be up to you to really read, read, read, but I don't mind point you in the right direction.
You will find links of information with in this post http://forum.xda-developers.com/showthread.php?t=2288189
I would read through s-off / s-on and true rooting. I feel like you're missing drivers and basically just have nothing installed on the phone. So you aren't bricked, you just need to do more research. Bricked is the phone shows no screen at all and won't even turn on. I've done it once, and you are luckily not there. I believe the first time I rooted this phone I had the same problem of "is it installing...did I miss something...eff it, battery pull...oh no!"
Also select the recovery option and let me know what happens, if it advances you to the next screen that is what is actually Clockwork Mod recovery. If you actually have that then we are even better. I'll keep checking back tonight for ya.

tonyMEGAphone said:
That screen you posted information from is called H-BOOT, it's like the factory boot loader. Clockwork MOD will show up after that but from what I'm gathering you didn't even install that in the first place. In H-BOOT you can only use the volume buttons and the power button to select so that is all normal.
So you downloaded the stock ROM and in the process of downgrading got stuck. If the SD card still works in other devices do you still have PD15IMG.zip on the card?
Also did you make sure to download the proper drivers for ADB and also for your phone? The ADB ones you should be able to find on this forum and the HTC ones you could get directly from you carriers website, and most likely somewhere on this forum. It will be up to you to really read, read, read, but I don't mind point you in the right direction.
You will find links of information with in this post http://forum.xda-developers.com/showthread.php?t=2288189
I would read through s-off / s-on and true rooting. I feel like you're missing drivers and basically just have nothing installed on the phone. So you aren't bricked, you just need to do more research. Bricked is the phone shows no screen at all and won't even turn on. I've done it once, and you are luckily not there. I believe the first time I rooted this phone I had the same problem of "is it installing...did I miss something...eff it, battery pull...oh no!"
Also select the recovery option and let me know what happens, if it advances you to the next screen that is what is actually Clockwork Mod recovery. If you actually have that then we are even better. I'll keep checking back tonight for ya.
Click to expand...
Click to collapse
I appreciate the comment and help. Sorry i didn't know that I wasnt in colckworkmod just yet. Im new to android as I am an apple person. Some of the links i've found on this site are outdated or used by sites that are no longer running. If possible could you help direct me to the appropriate link so that I can download the correct rom? thank you so much!

first
First in your Hboot screen scroll with the volume button to "Recovery" and let me know what happens.
---------- Post added at 04:36 PM ---------- Previous post was at 04:29 PM ----------
Also did you go to tmobile and install the HTC drivers under the support menu for your phone?
These are all must I read through your post and also am currently reading the link you said you followed but if you didn't do all these prerequisite work it's no wonder why you froze up.
---------- Post added at 04:52 PM ---------- Previous post was at 04:36 PM ----------
I see, you said the Recovery goes black and vibrates 7 times. Something didn't install right. At this stage of working with your phone you won't see the F: drive pop up until we fully get you downgraded and get the ROM operational.
See what you can do with this link. Follow it and even redownload items from it. It's more updated then the one you used.
http://forum.xda-developers.com/showthread.php?t=928370
And let me know how it goes, and if I helped click the little thanks button~ like i said before I'll have time tonight to go back and forth and try and make this work. You just need to read your face off. HTC's can be tricky but at least it's not MOTOROLA...
---------- Post added at 05:11 PM ---------- Previous post was at 04:52 PM ----------
Found another thread too
http://forum.xda-developers.com/showthread.php?t=1538859&page=6
Page 4 has a link to some PD15IMG.zip files that could work, Page 5 has someone confirming which one works and then Page 6 this guy posts a video on how he fixed his.
Also make sure the phone is charged a low battery can cause boot loops, try and format the SD card and only have PD15IMG.zip be the only file.

lol I missed the fact that he's still in bootloader.
Bro just try flashing that stock img again

tonyMEGAphone said:
First in your Hboot screen scroll with the volume button to "Recovery" and let me know what happens.
---------- Post added at 04:36 PM ---------- Previous post was at 04:29 PM ----------
Also did you go to tmobile and install the HTC drivers under the support menu for your phone?
These are all must I read through your post and also am currently reading the link you said you followed but if you didn't do all these prerequisite work it's no wonder why you froze up.
---------- Post added at 04:52 PM ---------- Previous post was at 04:36 PM ----------
I see, you said the Recovery goes black and vibrates 7 times. Something didn't install right. At this stage of working with your phone you won't see the F: drive pop up until we fully get you downgraded and get the ROM operational.
See what you can do with this link. Follow it and even redownload items from it. It's more updated then the one you used.
http://forum.xda-developers.com/showthread.php?t=928370
And let me know how it goes, and if I helped click the little thanks button~ like i said before I'll have time tonight to go back and forth and try and make this work. You just need to read your face off. HTC's can be tricky but at least it's not MOTOROLA...
---------- Post added at 05:11 PM ---------- Previous post was at 04:52 PM ----------
Found another thread too
http://forum.xda-developers.com/showthread.php?t=1538859&page=6
Page 4 has a link to some PD15IMG.zip files that could work, Page 5 has someone confirming which one works and then Page 6 this guy posts a video on how he fixed his.
Also make sure the phone is charged a low battery can cause boot loops, try and format the SD card and only have PD15IMG.zip be the only file.
Click to expand...
Click to collapse
Ok Im going to try this now. Just hold on in there for me.
Lets see if this works

tonyMEGAphone said:
First in your Hboot screen scroll with the volume button to "Recovery" and let me know what happens.
---------- Post added at 04:36 PM ---------- Previous post was at 04:29 PM ----------
Also did you go to tmobile and install the HTC drivers under the support menu for your phone?
These are all must I read through your post and also am currently reading the link you said you followed but if you didn't do all these prerequisite work it's no wonder why you froze up.
---------- Post added at 04:52 PM ---------- Previous post was at 04:36 PM ----------
I see, you said the Recovery goes black and vibrates 7 times. Something didn't install right. At this stage of working with your phone you won't see the F: drive pop up until we fully get you downgraded and get the ROM operational.
See what you can do with this link. Follow it and even redownload items from it. It's more updated then the one you used.
http://forum.xda-developers.com/showthread.php?t=928370
And let me know how it goes, and if I helped click the little thanks button~ like i said before I'll have time tonight to go back and forth and try and make this work. You just need to read your face off. HTC's can be tricky but at least it's not MOTOROLA...
---------- Post added at 05:11 PM ---------- Previous post was at 04:52 PM ----------
Found another thread too
http://forum.xda-developers.com/showthread.php?t=1538859&page=6
Page 4 has a link to some PD15IMG.zip files that could work, Page 5 has someone confirming which one works and then Page 6 this guy posts a video on how he fixed his.
Also make sure the phone is charged a low battery can cause boot loops, try and format the SD card and only have PD15IMG.zip be the only file.
Click to expand...
Click to collapse
So I found a new img file and the same thing happens. It says it's updating but doesnt make any progess and it looks like its frozen. What should I do?

N_otori0us_ said:
lol I missed the fact that he's still in bootloader.
Bro just try flashing that stock img again
Click to expand...
Click to collapse
tonyMEGAphone said:
First in your Hboot screen scroll with the volume button to "Recovery" and let me know what happens.
---------- Post added at 04:36 PM ---------- Previous post was at 04:29 PM ----------
Also did you go to tmobile and install the HTC drivers under the support menu for your phone?
These are all must I read through your post and also am currently reading the link you said you followed but if you didn't do all these prerequisite work it's no wonder why you froze up.
---------- Post added at 04:52 PM ---------- Previous post was at 04:36 PM ----------
I see, you said the Recovery goes black and vibrates 7 times. Something didn't install right. At this stage of working with your phone you won't see the F: drive pop up until we fully get you downgraded and get the ROM operational.
See what you can do with this link. Follow it and even redownload items from it. It's more updated then the one you used.
http://forum.xda-developers.com/showthread.php?t=928370
And let me know how it goes, and if I helped click the little thanks button~ like i said before I'll have time tonight to go back and forth and try and make this work. You just need to read your face off. HTC's can be tricky but at least it's not MOTOROLA...
---------- Post added at 05:11 PM ---------- Previous post was at 04:52 PM ----------
Found another thread too
http://forum.xda-developers.com/showthread.php?t=1538859&page=6
Page 4 has a link to some PD15IMG.zip files that could work, Page 5 has someone confirming which one works and then Page 6 this guy posts a video on how he fixed his.
Also make sure the phone is charged a low battery can cause boot loops, try and format the SD card and only have PD15IMG.zip be the only file.
Click to expand...
Click to collapse
When I went to recovery mode..it went to a black screen with like a green symbol and box. Then the entire screen went blank and I noticed the phone vibrated "7" times. What should I do?

Bolt34 said:
When I went to recovery mode..it went to a black screen with like a green symbol and box. Then the entire screen went blank and I noticed the phone vibrated "7" times. What should I do?
Click to expand...
Click to collapse
7 vibrates of death.
Dun dun daaaaaa.
That's a brick. I think.
Sent from my HTC Glacier

N_otori0us_ said:
7 vibrates of death.
Dun dun daaaaaa.
That's a brick. I think.
Sent from my HTC Glacier
Click to expand...
Click to collapse
So in other words...I can't fix the phone then?

N_otori0us_ said:
7 vibrates of death.
Dun dun daaaaaa.
That's a brick. I think.
Sent from my HTC Glacier
Click to expand...
Click to collapse
Couldn't that just be due to a low battery also?
---------- Post added at 05:08 PM ---------- Previous post was at 05:00 PM ----------
These people couldn't even get into the Bootloader. That's why I believe there is slightly still hope for you.
http://forum.xda-developers.com/showthread.php?t=2188591

tonyMEGAphone said:
Couldn't that just be due to a low battery also?
---------- Post added at 05:08 PM ---------- Previous post was at 05:00 PM ----------
These people couldn't even get into the Bootloader. That's why I believe there is slightly still hope for you.
http://forum.xda-developers.com/showthread.php?t=2188591
Click to expand...
Click to collapse
I made sure the phone was fully charged and I had it plugged in. That couldn't be it.

last
Bolt34 said:
I made sure the phone was fully charged and I had it plugged in. That couldn't be it.
Click to expand...
Click to collapse
My last thread attempt, and if this doesn't work. I'd say check out Craigslist for a new phone. My Glacier 4G antenna, the actual hardware, I believe is shot. So I'm going to have to down grade and run through a similar process so I can send it back for a replacement. These things can get tricky so I feel your bricked pain. I've bricked a Motorola Atrix before.
http://forum.xda-developers.com/showthread.php?t=2329869
If none of this works. It's time to put it in a shoe box and bury it in the back yard.

[q] such agonizing frustration

Well, here's my story.
Trying to install custom rom for my Note 3. I have version N900V for verizon. I'm assuming whatever I use I can use the N9005 because that's the only one that ever seems to come close to my model number based off the qualcomm chipset? Just a side note I guess. I've currently had success in rooting via one of the "one click" apps called Kingo. Very nice and easy and breezy. The real problem is trying to install a custom recovery via cwm. No matter what I do or try nothing will work. I can gaurantee it.
Also tried looking into twrp but even their app wouldn't install recovery. So I've done many things from using multiple versions of Odin, to many different cwm's, and all making sure I follow the instructions just as outlined to no avail. EVERY single time is a failed attempted with Odin, never passes. I believe I've gotten every different error you could get (all derive from same method anywho so figure they mean the same).
I haven't broken my knox yet so I guess that's good. I'm just not sure why I can't seem to get a recovery installed so i can finally move onto getting the rom installed. Once in download mode with the whole "volume up/home button/ power button" thing I get a few errors in there too such as: Sys rev check fail: no signature, and magiccode check fail: (some error here). Something along those lines. Even when I first started it would say that the signature files couldn't be verified or something. Looked a bit different and I forget how/when I got those messages. Funny thing is when I press volume up and power button with home, I get a recovery that looks just like a cwm one....not sure if there the whole time by default or maybe a feature of the root? Not sure honestly but I tried forgetting the cwm and going to install the rom and of course my luck I wiped data/cache following directions hoping it'd install properly, and I still get errors while trying to do the rom.
So now i'm back at out of box settings(although rooted) and I'm nowhere. If any of you has the slightest idea that could help I can't give up now. Also an interesting tidbit is I don't have the option anywhere for "reactivation lock" being disabled. Not sure why if anyone knows that explanation. Already have USB Debugging enabled so lets get the obvious ruled out too. Also I know my drivers have to be installed correctly since I can get into my phones SD card just fine as well as Odin always recognizes it right away as being added or removed hence the color being either yellow or blue. Tried even ticking everything and nothing and just some. even tried adding the pit file too. probably not necessary. I've had to even try replugging into different USB ports without closing Odin as some have suggested would work, and also closed Odin doing the same thing. No avail. I fear I may not be able to flash cwm for some reason? I would be pretty upset if I couldn't install a custom rom.

ducky06 said:
Well, here's my story.
...
So now i'm back at out of box settings(although rooted) and I'm nowhere. If any of you has the slightest idea that could help I can't give up now.
...
Click to expand...
Click to collapse
Hints - read more, select the right forum:
http://forum.xda-developers.com/verizon-galaxy-note-3

IIRC Verizon uses a locked boot loader. This means you can only load software signed by Verizon onto your device. The error messages seem also to point in that direction.
Someone may correct me if I'm wrong.
---------- Post added at 12:20 PM ---------- Previous post was at 12:04 PM ----------
Another sidenote: You mentioned Kingo. This is suspected to be malware (I didn't follow the corresponding thread, however). Seems to spy IMEIs. Search here at xda for more.
Just a warning for those reading it.

AT&T Samsung Galaxy S7 G930A Root Install Instructions?

If anybody can put up a step-by-step guide, or a video that shows how to properly install it all, I'm sure myself, and much of the community would appreciate it.
Recently, my laptop that I had ADB, and every tool imaginable for Androids, and specifically the Galaxy Series, took a huge dump on me and I lost it all. I installed it so long ago, that embarrassingly I've forgotten how I did it all. If someone could post how they rooted their GS7 (non-edge variant), I would be very appreciative. And I'm sure much of the community would be too. I'm embarrassed to even have to ask as someone who used to formerly develop mods on phones. But it is what it is. It's been so long since I've set it all up, and I've had to do so much since that time that I've simply forgotten how I did it/how to do it. Any help would be GREATLY appreciated. Thank you ahead of time...
I've tried following the instructions in the sticky above. I ran the 930X ROOT.TAR in the special version of ODIN. And every ran OK. It said "Success" and then rebooted. All seemed well, then it froze on the AT&T Boot Logo. What can I do from here? I know from history that this is one of the points that people panic and claimed "brick" (though I've never seen a real brick from rooting). Any help would be greatly appreciated

There's a great guide in the Verizon forum. Root was universal based on FW. Just make sure you flash the correct 930 or 935 with the modded odin. I recommend you follow the steps to "unroot" for the sake of doing an extremely in depth factory reset. Also make sure you get chain fires latest supersu built for the s7qc.
Sent from my SAMSUNG-SM-G930A using Tapatalk

twizt3d said:
There's a great guide in the Verizon forum. Root was universal based on FW. Just make sure you flash the correct 930 or 935 with the modded odin. I recommend you follow the steps to "unroot" for the sake of doing an extremely in depth factory reset. Also make sure you get chain fires latest supersu built for the s7qc.
Sent from my SAMSUNG-SM-G930A using Tapatalk
Click to expand...
Click to collapse
thank you for that. I'll check it out. Hopefully it'll get me past this bootscreen issue
yup. Great instructions. All set rooted now. Now time to play with xposed and V4A and the like. Yay

OK. Followed the instructions on the Verizon page and used the PrinceComsy version. Stuck at the AT&T logo. How did you go past this step? Should I have used the standard version? thanks

thanirs said:
OK. Followed the instructions on the Verizon page and used the PrinceComsy version. Stuck at the AT&T logo. How did you go past this step? Should I have used the standard version? thanks
Click to expand...
Click to collapse
(keep in mind this is only my personal experience...)
but the PrinceComsy version of ODIN was the only one to work for me. How far exactly have you gotten in the process before you got stuck at the logo? You do have ADB installed correctly installed on your PC and turned on on your phone right? and cd-ed the specific "super" folder for the SU adb install, right? FYI: It's not a simple root process, like 1-click roots on previous devices. This is more similar to the in-depth root methods like on the N1 and D1 before super nice devs went out of their way to make it simple. So if you're not familiar with ADB shell and the likes, it'll be difficult for you. But, no matter how high and mighty or condescending people act, we've all had to start somewhere. I'll help you get through the process as much as I can

Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
52brandon said:
(keep in mind this is only my personal experience...)
but the PrinceComsy version of ODIN was the only one to work for me. How far exactly have you gotten in the process before you got stuck at the logo? You do have ADB installed correctly installed on your PC and turned on on your phone right? and cd-ed the specific "super" folder for the SU adb install, right? FYI: It's not a simple root process, like 1-click roots on previous devices. This is more similar to the in-depth root methods like on the N1 and D1 before super nice devs went out of their way to make it simple. So if you're not familiar with ADB shell and the likes, it'll be difficult for you. But, no matter how high and mighty or condescending people act, we've all had to start somewhere. I'll help you get through the process as much as I can
Click to expand...
Click to collapse
---------- Post added at 08:47 PM ---------- Previous post was at 08:21 PM ----------
OK. Proceeding with the recommended steps in the install guide, I ran into this one nagging pop-up:
Security notice: Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes.
Its a rather annoying notice that keeps popping up. What is the fix for this? Quick 'google' suggested some people uninstalling Knox altogether and it seemed fairly drastic. Suggestions?
thanirs said:
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
Click to expand...
Click to collapse
---------- Post added at 09:08 PM ---------- Previous post was at 08:47 PM ----------
OK never mind please and sorry. Found the answer in the Fix/debloat script.

thanirs said:
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
---------- Post added at 08:47 PM ---------- Previous post was at 08:21 PM ----------
OK. Proceeding with the recommended steps in the install guide, I ran into this one nagging pop-up:
Security notice: Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes.
Its a rather annoying notice that keeps popping up. What is the fix for this? Quick 'google' suggested some people uninstalling Knox altogether and it seemed fairly drastic. Suggestions?
---------- Post added at 09:08 PM ---------- Previous post was at 08:47 PM ----------
OK never mind please and sorry. Found the answer in the Fix/debloat script.
Click to expand...
Click to collapse
so you got it all figured out and running great now right? No other issues right?

Just to add to this, I have verified that this still works using PG1.
http://forum.xda-developers.com/showpost.php?p=67970468&postcount=33

twizt3d said:
Just to add to this, I have verified that this still works using PG1.
http://forum.xda-developers.com/showpost.php?p=67970468&postcount=33
Click to expand...
Click to collapse
Can you please try restoring to af2?

Thanks for the ping. I think so. One thing I ran into which I don't know if its related to rooting. When I am in a phone conversation, audio on the other end goes in and out after a few minutes into the call. This happens with bluetooth or not. Still figuring out this issue.
52brandon said:
so you got it all figured out and running great now right? No other issues right?
Click to expand...
Click to collapse
Seeing battery drain. So went back to stock /unroot for now.

I was not trying to root my phone but reflash to an earlier version. I tried the Prince version of Odin and it did not work. The version that ended up working is in this thread
http://forum.xda-developers.com/att-galaxy-s7/how-to/firmware-g930a-edge-variant-afp-stock-t3415344
http://click.xda-developers.com/api...ww.mediafire.com/download/2t...din_3.12.3.rar

Desperately Asking For HELP!!!

Hello, guys! It's now my 2nd post asking the exact same help. I'm very desperate to fix my phone : Asus Zenfone 5.
I have been looking for solutions for a long time, I'm not easily quit on googling. So far, this problem is one that haven't been fixed and very unlikely to be fixed
I have contacted many people including that Taiwan guy who is an expert on Zenfone 5 (forgot the name) and I'm EXTREMELY DESPERATE
I know this problem might be similiar with other case, but this one seems to be rare, because I have not found the solution.
Here is the timeline before my device got soft-bricked :
1. I upgraded to Lolipop with a different version of it's recovery, but still worked.
2. One day, ANR Keeps reporting that SystemUI has stopped. Rebooted and the phone went bootloop.
3. (probably the problem) I flashed wrong version of recovery (I think it was kitkat's recovery) and after then, I'm not able to get into DROIDBOOT.
I have tried several ways :
1. Sending package to my phone over ADB Sideload (It says something like error mounting blabla)
2. Flashing with xFSTK (It says something about driver, and I googled it. Found everyone with the same problem, endless solutions)
3. Downloaded about 1 gig of files (DEBRICK Files) and still, gets stuck somewhere.
So anyone have a solution for me, please?? I'm totally desperate right now, I lost hope. Never had this kind of problem, the thing is that so far, I never had such never-solved case in my life, I will always
find a solution from Google even that would take a long time. I have been searching passively for about 8 months, and I got none of those works
I will be very thankful if anyone would try to help this problem, I will bring detailed information you want, because I don't have solutions left.
Sorry for bad English
Thank You so much!

From what I know (even though I am far from being an expert, just tried and researched a lot), there is no way to fix it.
The bottom line of the problem is that you can't repartition internal storage of zenfone 5 because of x86 architecture, there is no proper Linux partition tools for it. And the oem partitioning via bootloader just fails (gpt command failed).
this type of problem has raised extremely in last month because of some reason.
I just don't understand why but, perhaps, some error in the recent twrp version/s or flash scripts.
My zf5 is a full brick now with no chance for salvation, service can't fix it as well, says impossible to repartition because of the mentioned above.
Hope, I'm wrong

Try @dgadelha "unbrick" package what contain system in .raw format

It will not help. Because any unbrick method involves repartition, which is impossible in this case.
---------- Post added at 09:58 PM ---------- Previous post was at 09:55 PM ----------
But, @kihope12, that would be great if you post a link to that package or thread. Thanks!

Normaly i know link only for zenfone assist, what dont work anymore, so.. just try search on XDA

Well.. I'm done then.. I had so much hope with that phone after recovering it from bootloop.. Now there is no chance to get it back..
Anyway, thanks a lot for letting me know about this, otherwise I would keep looking for something impossible to fix.. And, you seem to know much about this.
Thanks again!!

Stuck on twerp read only ...with lock

Bought a secondary essent, figuring if I was going to brick up something, better to brick up a 20$ cracked up POS than my day to day user.
Everything was going as planned, didnt use the 15 second loader used the platform tools...
unlocked her, added BMG's twerp file....there's my mistake...I didnt rename the file.
As I wrote that I realized that.
Cannot get the device to reconize thru adb tools but windows see's her as Meta(or something) tried the different commands but adb doesnt see it.
Cannot turn phone off, tried volume up down power every which way,,,,
Big white lock on the 'keep system on read only screen" and cannot move....in any fashion.
Help me if ya can please,,,phone is at 84%....maybe just letting her die off?

back to bootloader and
I am not sure what sequence of buttons did it, but it was not a rename problem, its a unresponsive twerp problem. Using the original twerp has not accounted for the updates this phone has gone thru....I think BMG got one that a bit more "user friendly"....so I will keep trying with this 20$ phone....also in any of the "tutorials there is mention of an A/B partition but no instruction on it...learning on the fly...

pen101 said:
Bought a secondary essent, figuring if I was going to brick up something, better to brick up a 20$ cracked up POS than my day to day user.
Everything was going as planned, didnt use the 15 second loader used the platform tools...
unlocked her, added BMG's twerp file....there's my mistake...I didnt rename the file.
As I wrote that I realized that.
Cannot get the device to reconize thru adb tools but windows see's her as Meta(or something) tried the different commands but adb doesnt see it.
Cannot turn phone off, tried volume up down power every which way,,,,
Big white lock on the 'keep system on read only screen" and cannot move....in any fashion.
Help me if ya can please,,,phone is at 84%....maybe just letting her die off?
Click to expand...
Click to collapse
Hold power longer than 10 seconds (hard reboot) then volume down and it'll boot bootloader. From there flash a working boot image with working TWRP patched for the Rom you are on.
Sent from my PH-1 using Tapatalk
---------- Post added at 05:34 PM ---------- Previous post was at 05:32 PM ----------
pen101 said:
I am not sure what sequence of buttons did it, but it was not a rename problem, its a unresponsive twerp problem. Using the original twerp has not accounted for the updates this phone has gone thru....I think BMG got one that a bit more "user friendly"....so I will keep trying with this 20$ phone....also in any of the "tutorials there is mention of an A/B partition but no instruction on it...learning on the fly...
Click to expand...
Click to collapse
https://www.youtube.com/channel/UCucUjVNJshybBA8JWftayVA check out my channel where I provide tutorials, reviews and files in links to complete pretty much any task for essential.
Sent from my PH-1 using Tapatalk

First and foremost,,,,
THANKS FOR THE REPLIES AND ADVISE.
Got up, drank a cup, dragged a brush across me head...booted up bootloader, hit on recovery mode and now back to square one with the latest pie flavor.
Sometimes you "over work" the problem.
As a mechanic I sometime got "stuck" and instead of getting frustrated, I simply walked away and came back to it, only to find (as with this) a simple solution.
I am expecting a tv box (PIE, 4 and 64)....should be a head scratcher.
Great forum, good peeps...MANY THANKS!