Ok, so I have flashed a ton of ROMs, very successfully I might add. This last ROM I flashed worked just fine. After a day or so it started having some issues, so I tried to restart it. It started booting back up, and never left the HTC Innovation screen with the red text in the lower right hand corner.
I have hard reset it several times, and still I get the same thing. I can get to the boot loader screen and get it to change from serial to usb when plugging it into the computer, but this is as far as I get. Can someone please help me, thanks in advance!
Mark
PS I have also searched the forums, but unfortunately don't know quite what to search for. Thanks again!
Enter in the Bootloader mode (VolDown when reseting), plug the USB cable and install an older ROM via CustomRUU you know is working..
enter bootloader , use MTTY - http://forum.xda-developers.com/showthread.php?t=540290 to format rom memory .
Then flash it with a stock rom from www.HTC.com
Thanks
Thank you both for the help, trying now...IT WORKED!! Thank you guys so much!
Enter bootloader successfully means your phone is not bricked yet.
1) Use MTTY do delete old ROM
the command is "task 29"
Search the forum "MTTY" to learn how to use and where to download
2) Flash new ROM. Done
satus said:
Enter bootloader successfully means your phone is not bricked yet........
Click to expand...
Click to collapse
May not always be true !?
Here's output of 'TASK 29' (end section)
Flash NAND DM internal transfer failed: dmov_transfer()bad=0x7FF
R:NO bad block reversed for block ID 0x7FF
Read sector fail!!!
Can someone enlighten and lead ....
task 28!!! NOT 29!!
more precisley "task 28 55aa"
Dont typo the MTTY commands as it can completly screw up your phone...
please help after flashing a couple of roms i started having some problems
like everytime i reset it does a hard reset and now it doesn't seem to leave the boot image with TOUCH DIAMOND
i cant understand what steps i must follow for MTTY on xp
MTTY didn't work for me
I bricked my phone a few weeks ago and tried everything i could find on MTTY and nothing worked, error after error, i got really lucky and entered bootloader and plugged my USB in immediately after windows 7 boot up and got away with it through CustomRUU. 6 hours to fix and 25 minutes sleep before work. But hey, fixed the diamond and thats all that mattered.
MTTY + Latest HardSPL should solve any problems if you still have access to the bootloader
Related
Please help!
I just upgraded my ROM to Ivan's latest AKU3.5 from bootloader
This completed successfully (100% successful, disconnect and restart etc)
I disconnected and reset, except it was stuck in bootloader mode
I tried the Mtty method (for the first time ever) and followed the step by step instructions...
...after a few seconds a few command lines appeared with "USB>" on the last line
I took this to mean the process had finished (?), disconnected the device from USB and tried a soft reset
the device just stayed stuck in bootloader
next, i downloaded uni_exitbootloader and ran it (as this has worked for me many times in the past). it didn't work the first few times, but i disconnected and reconnected and this time it worked. It said "data sent, you can now reset your device"
This maybe where i went wrong?
I foolishly reset the device before disconnecting it from the USB. The PC immediately said "USB device not recognised" and the screen of my Universal went blank
Now, if i soft reset, it does nothing, i cannot even put it back into bootloader using the camera, on, reset button combination.
HOWEVER, if i press the two soft keys (as if i was going to do a hard reset) i get the white screen with the black text saying "Press 0 to restore etc"
If i press 0, it says "clearing" but the screen just goes blank
If i press x, the screen just goes blank
Now i am completely unable to try and use either mtty or exitbootloader as my PC just says "USB device not recognised" and neither applications run as they should
QUESTION: Have i totally bricked my Universal?!
If not, what can i possibly do...???
As usual, i will be extremely greatful for any advice or assistance to resurrect my favourite Pocket PC!
Thanks in advance for your help.
Aaagh! I think i just realised what i did...
1. I didn't read the posting "For all those stuck in the bootscreen, try the Mamaich method" carefully enough. I didn't realise that the Mamaich method totally erased the ROM!!!
2. By not flashing a new ROM to the device immediately and instead using exitbootloader to exit the bootloader screen i now have a device that has no ROM and probably has no way of knowing how to get into bootloader mode.
Can someone confirm this?
For one, i feel like an idiot for not reading the posting carefully, but having admitted to being stupid,...
... is there anything at all i can do???
Please help...
cancel that, you already said what i was going to ask above
have you try to flash it again with original ROM? sometimes it helps!
Once in bootloader mode, try plugging it into a different USB port, one directly on the PC.
I have had this where one port says not recognised, even after having been plugged in and used for ages, then I go to flash it and it won't work.
Another port has worked for me.
Since you ereased the DOC, all you've got to do now is to reflash the default ROM.
Thanks everyone...
Only problem is, i cannot get it into bootloader mode. And every port i plug it into (so far) says "device not recognised"...
Nevertheless, i did try to reflash the device, but it just gave me the "Error 150" message. It just doesn't know the device is connected i guess?
I think if i hadn't done the Exitbootloader step then i would have been able to reflash it. However, now that i have... i'm a bit stuck... any ideas of other ways to get the device into Bootloader mode?
try
you already know there is a file called EXITBOOTLOADER but did you know that here is a file called ENTERBL ?
try it .....
Thanks dhob187!
Where might i find this file though? Did you mean to attach it?
Just one other question...
How does ENTERBL work if the PC doesn't recognise my device i.e. "USB device not recognised"? Will the application override this and push commands to my pocket pc anyway?
Or is there a way i can get my PC to stop rejecting the device when i plug the USB in?
Thanks in advance,
I believe this is the file u needed
i don't know how this utility works, but just yesterday i stuck in the bootloader after upgrading my uni to AKU 3,5 and solved with ExitBootloader.exe. CMIIW it works the same way, just plug the USB cable then execute the utility (just simple as that).....
but have u tried my earlier suggestion? my friend got the exact problem like you (blank LCD not even bootloader), he was downloaded the original EXEC ROM and try to flash with it (with original upgrade utility also). and the thing start to blink, enter the bootloader and flashing!.....after he manage to wake the device up, then he tried to flash it again with the newest ROM and succeded........
sorry for my english.....
Please don't apologise for your English, thank you for your suggestions!
I didn't quite understand your initial post... but i do now.
Does it have to be the first ROM that it was shipped with or just an original i-mate JasJar ROM?
I can't try it now, but i'm excited to go home and give it a go later tonight... what's more i'm excited at the prospect that there may be some hope for my currently rather expensive paperweight!!!
If the aforementioned doesn't work, i'll try using your attachment.
Cheers again!
it doesn't have to be the first rom that shipped with your imate, just an original one. try your luck then! never give up, keep the faith!!!
sorry, forgot one thing, just ignore the USB error (not recognized) and go for the upgrade (execute the original upgradeUt.exe)
Hi Rudy173.
Thanks for your help, but unfortunately nothing has worked
I have tried running two official JasJar Roms without success... i always get the connection error message (this is surely because the PC always says "device not recognised" when i plug it in).
Also, when i run ENTERBL.exe i just get a failure saying that ...ENTERBL.exe is not a valid WIN32 application... etc...
So unfortunately, i'm still stuck... any further suggestions anyone?
Can the i-mate service centre help me? Is it likely to be expensive?
Back in business )
Wow, not entirely sure what i did... but my Universal is ALIVE!!!
As per the previous post, nothing seemed to be working so i removed Activesync 4.5 beta and reverted to 4.1. I then tried to reflash to an original ROM and the same "connection error" problem happened.
However, next time i tried to enter bootloader, by pressing light, on/off and reset, it went straight into bootloader and i was able to reflash from there
I didn't even need to reflash with an original i-mate ROM. I went straight for Ivan's latest.
This experience has taught me a few things:
1. I have become seriously attached to my Universal!
2. You should never give up hope of retrieval!!
3. This forum is full of very nice helpful people!!!
Thanks everyone.
wow! glad to hear that!
Happy ending....................
I have done a lot of reading about the bootloader being stuck..... But what fix is there when after following the directions of entering Bootloader(ie.pressing the light, power, and pressing the soft reset)
My device will not enter bootloader mode.
does this help?
PLEASE HELP ME, I transfered the file to my device and ran it, but it went black and there is no response. Is my device dead ????
fishboy420
check the screen very closely, it will be in bootloader mode, there is no backlight in bootloader but small writing saying SERIAL (or USB if plugged in) and a version
It won't do anything. And I am familiar with the Bootloader screen. But it won't do anything. Nothing. I even tried to reset it.
I am reallyt scared now. IO hope I didn't fry it???
fishboy
><}}">
just ran the exe on mine 3 times to make sure, works a treat!
it's what the RUU uses to put your device it bootloader!
no idea why your phone has gone bad?
I think I may have screweed it up. I tried to run it and it said not a win32 program or somjething to that effect. So I trqansfered it to my device and opened it up and my device went dead.
Is there a fix for this?
It is a brick now. No Bootloader or nothing
thats what you are meant to do :S
I guess I will have to send it in to repair station. Thank you for your help though. I am just stumped as to why it isn't working
Any suggestions?
Thank you for trying to assist me.
fishboy
I have tried to unlock the ext rom by changing the registry asdescribed in the forum, the result was a white screen tried a hard reset but the result became worser, a dead ppc with a black screen, only when I keep puching on the power button a red green light start flashing. I have tried every possible issue hard, soft reset. Tried to bootload from the sd card without a possible solution, can anybody help me out here, thanks
i guess there is only one option left, flash your device again
I have tried to flash again without succes, the flashing can happen only when there is a usb connection, the driver was not found and the ppc still dead.
bootloader mode!
Beny said:
I have tried to flash again without succes, the flashing can happen only when there is a usb connection, the driver was not found and the ppc still dead.
Click to expand...
Click to collapse
You need to put your fone into bootloader...try the wiki...
I have a nordic HTC Touch Pro 2
This unit started acting up after I installed the Energy ROM from the 20th of December. It used to fail in booting occationally(fixed by attaching USB-power), but now it is thouroughly stuck in the bootloader.
This is what I see when I reboot:
RHOD100 32M SS-BC
SPL-0.85.OliNex
MicroP(LED) 0x0A
MicroLED(KEY) 0x04
TURBO HW/TURBO SW
TP MFG DATA
509,521 792,844
795,200 221,198
226,843 Calibrated
Serial (changes to USB when connected)
There is a quick flash of 2 previous screens, one tri-color and one saying something about no image to load.
I belive, but would be thrilled to be proven wrong, that I have tried all tricks.
Running Windows 7 I first disabled device driver signing and loaded the HTC USB driver. Downloaded mtty 1.42, connected to the phone via USB and ran "boot" command.
The only problem listed was one bad block in CE.
Tried reboot again with same error.
"info 8" revealed that the bad block is 370.
Ran "task 29" but it gave an error trying to delete block 370.
Rebooted and tried to flash latest 29007 Energy ROM. No errors reported during the flash, still when it rebooted after reaching 100% it stopped in bootloader again.
I have also tried this procedure and replaced the Energy ROM with the latest original nordic ROM. When I use "boot" command from mtty I get the HTC screen (white background with htc in green letters) but the phone apparantly is stuck there. A soft restart brings me bach to the bootloader again.
Is my phone bricked? I'm not sure what to do or try next and as I have seen others report my battery is draining and will not charge(no light) when plugged in to computer or charger.
Thanks in advance, I love what you all do for this community and wouldn't have still used tha TP2 if it wasn't for all the great ROMs presented here!
NVM, re-read and see you already tried my suggestion.
Additional info
I ahould add that I also can't do a hard reset. Pressing and holding send and end and then power button only result in getting the bootloader menu. I borrowed a freshly charged battery and tried loading a new ROM, but no change, it still only restarts to the bootloader after completion.
If you can get into bootloader and the usb shows when plugged in, you should be able to flash back to stock via RUU.
Try this;
Open your downloaded ROM with unzipper. You should see two files, the RUU and the RHODIMG.nbh. Copy the .nbh onto the root of your SD card. Powerup the device holding the volume down. It should boot to bootloader and immediatly look for and find the .nhb and install it.
Hope that helps.
Hi!
Thanks for your answers! Sorry about the late reply!
I tested with RHODIMG.nbh file(29007 Energy) on the SD-card. The installation started and ran as expected. When done the screen showed the following info:
"RHODIMG.nbh - OK
OS - OK
Update Complete
UPDATE SUCCESS"
There were no button to press on the screen, and pressing the power-button didn't do anything. I eventually removed the battery, reinstalled the battery and pressed the power button. Unfortunately for me I was once again presented with the bootloader screen.
Any ideas to a new approach? I really don't want to write off the phone as bricked, it should have about a year left in it before I consider replacing it.
Try this:
When powered off, attach headset to the phone. Then press power button.
My Touch Pro2 ran into the same situation recently, showing nothing but a 3-color screen with the same information as you listed. I haven't tried mtty but I found if I plug in the headset, it boots normally. No idea why...
It sounds like an error in the instruction set for the bootloader. Maybe cmonex can help you with a bootloader-friendly version of Hard SPL to re-flash.
cajunflavoredbob said:
It sounds like an error in the instruction set for the bootloader. Maybe cmonex can help you with a bootloader-friendly version of Hard SPL to re-flash.
Click to expand...
Click to collapse
he already has Hard-SPL so he could just reflash it with the Hard-SPL exe in manual mode, but as the version number is the same, the device may skip the updating of the SPL. if the OP wants to try this, I can make one with a different version number. though I seriously doubt that the issue would be fixed that way...
Headset trick
Hi,
Again, thanks to all that try to help me!
I tried the headset trick just now and look and behold, it actually worked! My limited brain can't come up with any plausible explenation but I'm happy anyway
I do remember reading about this trick at some point, but I couldn't locate a headset until today. Thanks lilei105!
Now I will reboot the unit several times to ensure this wasn't just a coincident.
Edit: Booted 4 times, still no problem. Have booted both with and without USB-cable connected to PC.
Yeah my advice would be re-flash it or install/download a different ROM.
i may be way off here, but could it be a problem with the volume down button on the unit? maybe the headset bypasses the standard volume button?
Hello all,
I'm stuck in different guides on what to do next.
Problem: Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13.
Also had charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
Tried:
- Factory reset in TWRP -> didn't work (the occasion I did get into CM13 it showed the setup again, so the reset actually went through, but loops still exist).
- When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
- When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
- Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC.
-> Problem: Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
- Another problem: When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.
So now im a bit stuck on what to try next to solve everything and get myself back into CM13. CM13 has ran since Feb '16 and have been a happy user since then until now.
Thanks for reading!
The simplest solution may be to flash back to stock and start over. If the phone doesn't behave properly on a stock ROM, there could be a hardware problem.
Hi there , in TWRP select reboot then power off .
Enter bootloader via buttons after 10 seconds being off !
Enter bootloader - power and vol + , when in bootloader if on LP -- flash raw with AFT (asus flash tool )
If any probs with above , you might have to fastboot flash stock recovery and boot to recovery if/and a , try raw if on LP with AFT or b, sideload stock firmware you flashed stock recovery for.
audit13 said:
The simplest solution may be to flash back to stock and start over. If the phone doesn't behave properly on a stock ROM, there could be a hardware problem.
Click to expand...
Click to collapse
timbernot said:
Hi there , in TWRP select reboot then power off .
Enter bootloader via buttons after 10 seconds being off !
Enter bootloader - power and vol + , when in bootloader if on LP -- flash raw with AFT (asus flash tool )
If any probs with above , you might have to fastboot flash stock recovery and boot to recovery if/and a , try raw if on LP with AFT or b, sideload stock firmware you flashed stock recovery for.
Click to expand...
Click to collapse
Thank you for your answers! Last hours been trying to flash the stock ROM back. However, when getting into bootloader, adb devices and fastboot devices don't show the device. Or it even freezes and gets into reboot loops again. So this is why I'm stuck, nothing seems to be working from all the guides and things I'm reading.
So precisely:
- Power off bootlooping device by holding power button
- Power on by holding PWR + VOL UP
- When vibrating: release PWR keep holding VOL UP
- Now i'm in bootloader?
- Connect USB cable to computer
- type adb devices, shows nothing.
So what can I try to make connection?
- Now i'm in bootloader?
- Connect USB cable to computer
- type adb devices, shows nothing.
@j4y_ha .................in bootloader
Type >
................................................. fastboot devices
What ifwi version number in bootloader ?
timbernot said:
- Now i'm in bootloader?
- Connect USB cable to computer
- type adb devices, shows nothing.
@j4y_ha .................in bootloader
Type >
................................................. fastboot devices
What ifwi version number in bootloader ?
Click to expand...
Click to collapse
The bootloader in shows the following:
IFWI version: 0094.0173
SERIAL_NUMBER = F8AZFG0152** (couldn't read the last 2 digits as the device rebooted again). Also sometimes the SN shows 012345689ABCDEF.
I've much trouble keeping the device in bootloader. Last tryings it keeps shutting down after couple of seconds in the menu.
EDIT:
So far the device seems to stay in bootloader mode now. I can cycle through the options normal boot, recovery etc. Below the screen it shows Continue the fastboot process in blue text. I've inserted the USB cable but have been unable to get "fastboot devices" to show any device. ASUS Flashtool also doesn't do anything.
I'm going to try to find a micro SD adapter so I can try flashing stock rom in TWRP from the phone itself (would that be something that could work or is this phone fubar?)
@j4y_ha
Do not attempt to flash stock rom in TWRP ! You will brick !
Flash a custom rom in TWRP only- not one with a mm bl version
You have LP
PLEASE
Follow my first reply to you
timbernot said:
@j4y_ha
Do not attempt to flash stock rom in TWRP ! You will brick !
Flash a custom rom in TWRP only- not one with a mm bl version
You have LP
PLEASE
Follow my first reply to you
Click to expand...
Click to collapse
Thank you for your support! Will try again.
I have MM not LP.
I don't understand your reply correctly I think so here is what I think you say?:
I should obtain LP rom for ZE551ML
Next, enter bootloader via buttons PWR & VOL UP after 10 seconds being off !
When in the bootloader, - power and vol + (short press or long?) , when in bootloader ->
I connect USB to computer, flash the file using AFT if I make connection. -- flash raw (raw = LP ROM from ASUS) with AFT (asus flash tool )
Thanks again for your help
j4y_ha said:
Thank you for your support! Will try again.
I have MM not LP.
Thanks again for your help
Click to expand...
Click to collapse
IFWI version: 0094.0173 is LP, NOT M
follow my first reply:good:
---------- Post added at 06:39 PM ---------- Previous post was at 06:37 PM ----------
No1
Hi there , in TWRP select reboot then power off .
---------- Post added at 06:40 PM ---------- Previous post was at 06:39 PM ----------
no2
Enter bootloader via buttons after 10 seconds being off !
no3
When in bootloader you are on LP -- flash raw with AFT (asus flash tool )
@timbernot I'm unable to make connection. Fastboot also most of the times freezes and goes to black screen. What could I possibly try now?
Sorry I thought CM13 was MM but then I'm on LP still haha :good:
j4y_ha said:
@timbernot I'm unable to make connection. Fastboot also most of the times freezes and goes to black screen. What could I possibly try now?
Sorry I thought CM13 was MM but then I'm on LP still haha :good:
Click to expand...
Click to collapse
I'm taking wild guess here that you got wrong TWRP recovery installed somehow or something from M causing all these problems , when you get into bootloader again..Scroll to and select reboot bootloader and fastboot flash stock recovery for LP version you was on .
Then , I guess your problems will be over , where you will be able to flash raw in bootloader or in stock recovery , adb side load the firmware
Thanks for your quick anwer. Will try to get through it haha :good:
DUDEE
that's not a problem.. THAT's like 20 different problems... I bricked the living crap out of my zen the day I bought it (because me = smartypants did not know that the MM boot unlocker is nonexistent so I just tried to root and update from my head using older techniques) and... the XTS tool thingy fixed it..
Don't get me wrong, i want to help but this is the problem that I feel little frustrated with..
Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13. ## (but it boots sometimes and goes into TWRP, so you have an easy fix to just revert to stock lollipop... why haven't you done that? You sound like you know what most of this stuff does...
Charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
## how do you connect this battery issue to your occasional bootloop? Check hardware or firmware and definitely use different threads.. there's no way these are all part of the "same problem"...
When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
## Same answer as above - this is unrelated to #2 and unrelated to #1 - is your TWRP the correct one? I mean... did you just maybe flash TWRP version 4000 Modified Alpha for Google Glass??? LOL
When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
## Is D2W there? "DoubleTap2Wake" ? Are you sure you have a good touch? (this maybe 20% sounds related to your TWRP touch going crazy..)
Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
## There's this awesome invention called DRIVERS... and we're lucky in this case (cuz I bricked an hour after I bought it) because Intel PC + Intel Phone = Yay... There is even.... a very specific "INTEL ASUS WINDOWS DRIVER" file... from the INTEL AND ASUS WEBSITE... or maybe your USB CABLE is f**? My point is... another unrelated issue where it sounds like you've not even tried it properly before complaining.. I like helping people. I don't like when people refuse to try or they skip the actual study-notes to do it... I used the EXACT same guide to unbrick and it worked in 2 mins... I'm on a 2007 Laptop which overheats if I use 4 tabs... how am I able to follow the exact same guide on a brand new "FULLY BRICKED" phone... it literally would vibrate after trying power button for 5 mins and be stuck in a "blank black screen" for hours and hours... No twrp no nothing.. and I did it - why didn't you? Same guide man...
When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.)
## Try again. Sometimes people accidentally hit power to early.. or whatever.. It's not a MK2 Fatality.. don't force yourself to get it exact.. Let the menu pop up... just wait a second and scroll up/down just to see if that works... then scroll to Boot-Recov and gently hit power+vUp.. should be fine.. otherwise just .. literally try 10 times.. it WILL work.
Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC
## Nope.. TWRP is like Bret Hart. It isn't unstable. Not for LP not MM not for N. Not for Stock Not for CM Not for AOSP. You *wanted* to do what you should have done right at the beginning but you didn't get that done properly (see below)
Essentially you have 8 different unrelated issues (and the biggest one is not reading guides, not trying hard enough and just thinking that people like me sit around and get paid for this)... and want ans in one place w/o just doing the simple thing of going back to everything stock...?? *it's just annoying cuz people who want to help will feel like.... others don't even try simply because we exist and have desire to help...* - I am not trying to offend you but I hope you get my pov.
Do This EXACTLY
#Buy a cable. Borrow a cable. Whatever you do be 1000000% sure the USB Cable is fine
#Install Intel Asus Android drivers from official EXE (google it... don't add new post for that link)
AND THEN
Follow the same Unbrick guide word for word *but* just pay close attention to these:-
IntelSeC Driver + device detected even if OFF (start>devman>showall>intelsec
In the official unbrick utility make sure you're on the second tab at the bottom
In settings check that your device flag is 0x08..... whatever instead of the default 0x000
Back in the *second tab at the bottom* (i don't remember exact name but it's in the guide) -- put the right files (mentioned in guide) in the right boxes.. (mentioned in guide) and remember you ONLY need the DVFWthingy... + TOKENthingy + IFWthingy
Plug the Zen in... hear the "da-dumm" sound... keep looking at the Unbrick tool.. and the moment you see Device Detected = 1 you hit install/start...
AFTER that is fully done *(and if you fail don't post just repeat from scratch)... I don't personally recommend Asus Flash tool it was acting dodgy for me but instead grab the RAW Stock... Rename it to zip.. open it and grab the img files and fastboot flash the fastboot droidboot.img + splashscreen splash.img + boot boot.img + recovery recovery.img
If you've followed all that from the guide and double checked what I've put up there.. you should be fine if you just fastboot reboot bootloader... and go into stock recovery... install zip/update and put your stock OS in there..
Done.
Just please take my advice and don't skim through guides, don't think you don't need to read something, don't click stuff without double checking every line from guide, print it out on PAPER if you need to.... but please don't post like this... and don't use different guides or you will be stuck (as your heading stated..)
Forget everything you knew. Close all other tabs and use this guide thoroughly for Reference:-
https://forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840
j4y_ha said:
Hello all,
I'm stuck in different guides on what to do next.
Problem: Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13.
Also had charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
Tried:
- Factory reset in TWRP -> didn't work (the occasion I did get into CM13 it showed the setup again, so the reset actually went through, but loops still exist).
- When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
- When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
- Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC.
-> Problem: Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
- Another problem: When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.
So now im a bit stuck on what to try next to solve everything and get myself back into CM13. CM13 has ran since Feb '16 and have been a happy user since then until now.
Thanks for reading!
Click to expand...
Click to collapse
Wow @ryankabir
one step at a time hey
xFSTK is used to bring temp bootloader to hard bricked devices .
He has stock LP bootloader and all avenues to repair should be explored first
If anyone needs to unbrick , there is a thread in my signature below ,shows how to go from complete brick , to restoring serial number and into system within 15mins
Thank you for your thourough answer Ryankabir! Much appreciated. My answers are below. I will try your suggestions soon.
ryankabir said:
DUDEE
that's not a problem.. THAT's like 20 different problems... I bricked the living crap out of my zen the day I bought it (because me = smartypants did not know that the MM boot unlocker is nonexistent so I just tried to root and update from my head using older techniques) and... the XTS tool thingy fixed it..
Don't get me wrong, i want to help but this is the problem that I feel little frustrated with..
Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13. ## (but it boots sometimes and goes into TWRP, so you have an easy fix to just revert to stock lollipop... why haven't you done that? You sound like you know what most of this stuff does...
Click to expand...
Click to collapse
Yes I do know what I can do with it, but it just so complicating as there are different factors like the loops, not being able to get connections with USB. I mean, it is not totally bricked since sometimes I can get into TWRP or bootloader.
ryankabir said:
Charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
## how do you connect this battery issue to your occasional bootloop? Check hardware or firmware and definitely use different threads.. there's no way these are all part of the "same problem"...
Click to expand...
Click to collapse
Well, since the phone worked fine before the battery issue, there is some sort of link between the issues I would think. Maybe I've broken some hardware during the battery removal or did the booting into charging mode and on/off continously corrupt some memory leaving me with weird crashes & loops.
ryankabir said:
When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
## Same answer as above - this is unrelated to #2 and unrelated to #1 - is your TWRP the correct one? I mean... did you just maybe flash TWRP version 4000 Modified Alpha for Google Glass??? LOL
Click to expand...
Click to collapse
Although I'm not sure if I have the correct TWRP, it did flash CM13 correctly back in FEB 2016 and haven't found a need to update it ever since as it worked fine during the occasional update...
ryankabir said:
When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
## Is D2W there? "DoubleTap2Wake" ? Are you sure you have a good touch? (this maybe 20% sounds related to your TWRP touch going crazy..)
Click to expand...
Click to collapse
No, D2W is not there. The phone is totally unresponsive to the power button as well as D2W. When in TWRP the touchscreen functions fine until it freezes at some random moment.
ryankabir said:
Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
## There's this awesome invention called DRIVERS... and we're lucky in this case (cuz I bricked an hour after I bought it) because Intel PC + Intel Phone = Yay... There is even.... a very specific "INTEL ASUS WINDOWS DRIVER" file... from the INTEL AND ASUS WEBSITE... or maybe your USB CABLE is f**? My point is... another unrelated issue where it sounds like you've not even tried it properly before complaining.. I like helping people. I don't like when people refuse to try or they skip the actual study-notes to do it... I used the EXACT same guide to unbrick and it worked in 2 mins... I'm on a 2007 Laptop which overheats if I use 4 tabs... how am I able to follow the exact same guide on a brand new "FULLY BRICKED" phone... it literally would vibrate after trying power button for 5 mins and be stuck in a "blank black screen" for hours and hours... No twrp no nothing.. and I did it - why didn't you? Same guide man...
Click to expand...
Click to collapse
Yes I know what drivers are :good: - I've tried IntelSoc, Intel ASUS etc... all drivers that are somewhere mentioned I have installed. Before the charging problem I was able to connect the phone and access files fine as well.
ryankabir said:
When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.)
## Try again. Sometimes people accidentally hit power to early.. or whatever.. It's not a MK2 Fatality.. don't force yourself to get it exact.. Let the menu pop up... just wait a second and scroll up/down just to see if that works... then scroll to Boot-Recov and gently hit power+vUp.. should be fine.. otherwise just .. literally try 10 times.. it WILL work.
Click to expand...
Click to collapse
Thanks, will try more!
ryankabir said:
Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC
## Nope.. TWRP is like Bret Hart. It isn't unstable. Not for LP not MM not for N. Not for Stock Not for CM Not for AOSP. You *wanted* to do what you should have done right at the beginning but you didn't get that done properly (see below)
Click to expand...
Click to collapse
TWRP is indeed fine and stable! However, it freezes and reboots my phone so in my particular situation it is currently not stable. Therefore the need to completely wipe the phone and start from fresh.
ryankabir said:
Essentially you have 8 different unrelated issues (and the biggest one is not reading guides, not trying hard enough and just thinking that people like me sit around and get paid for this)... and want ans in one place w/o just doing the simple thing of going back to everything stock...?? *it's just annoying cuz people who want to help will feel like.... others don't even try simply because we exist and have desire to help...* - I am not trying to offend you but I hope you get my pov.
Click to expand...
Click to collapse
Appreciate your POV. I know how it feels like if people ask for help for something they could have read easily somewhere. I'm thankfull for all the guides that people have written on here! I'm asking for help because in my situation the guides are not working and would like to have a full clean wipe of my phone and fix all possible software issues before trowing away the phone because of hardware fault.
ryankabir said:
Do This EXACTLY
#Buy a cable. Borrow a cable. Whatever you do be 1000000% sure the USB Cable is fine
#Install Intel Asus Android drivers from official EXE (google it... don't add new post for that link)
AND THEN
Follow the same Unbrick guide word for word *but* just pay close attention to these:-
IntelSeC Driver + device detected even if OFF (start>devman>showall>intelsec
In the official unbrick utility make sure you're on the second tab at the bottom
In settings check that your device flag is 0x08..... whatever instead of the default 0x000
Back in the *second tab at the bottom* (i don't remember exact name but it's in the guide) -- put the right files (mentioned in guide) in the right boxes.. (mentioned in guide) and remember you ONLY need the DVFWthingy... + TOKENthingy + IFWthingy
Plug the Zen in... hear the "da-dumm" sound... keep looking at the Unbrick tool.. and the moment you see Device Detected = 1 you hit install/start...
AFTER that is fully done *(and if you fail don't post just repeat from scratch)... I don't personally recommend Asus Flash tool it was acting dodgy for me but instead grab the RAW Stock... Rename it to zip.. open it and grab the img files and fastboot flash the fastboot droidboot.img + splashscreen splash.img + boot boot.img + recovery recovery.img
If you've followed all that from the guide and double checked what I've put up there.. you should be fine if you just fastboot reboot bootloader... and go into stock recovery... install zip/update and put your stock OS in there..
Done.
Just please take my advice and don't skim through guides, don't think you don't need to read something, don't click stuff without double checking every line from guide, print it out on PAPER if you need to.... but please don't post like this... and don't use different guides or you will be stuck (as your heading stated..)
Forget everything you knew. Close all other tabs and use this guide thoroughly for Reference:-
https://forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840
Click to expand...
Click to collapse
Thanks for the suggestion and will try this!
timbernot said:
Wow @ryankabir
one step at a time hey
xFSTK is used to bring temp bootloader to hard bricked devices .
He has stock LP bootloader and all avenues to repair should be explored first
If anyone needs to unbrick , there is a thread in my signature below ,shows how to go from complete brick , to restoring serial number and into system within 15mins
Click to expand...
Click to collapse
I've tried your guide but I still have been unable to get a connection with ASUS Flashtool. The phone does keep itself relatively stable in bootloader (don't know what fixed it) - I am able to cycle through normalboot, recovery options etc without it crashing. The bootloader shows "Continue the fastboot process". I have tried different drivers, while rebooting between install/uninstall of drivers.
Thanks again all for the help
@j4y_ha
Goodluck
timbernot said:
@j4y_ha
Goodluck
Click to expand...
Click to collapse
Right m8 , we gonna fix your phone .
Do not stray from this guide.
Stick to it and you will be more the wiser when you have finished .
1 boot to boot loader ...scroll to 'power off ' and select it.
2 Connect your phone to wall charger ...let it charge till full.
When that's done , we ready for next step
timbernot said:
Wow @ryankabir
one step at a time hey
xFSTK is used to bring temp bootloader to hard bricked devices .
He has stock LP bootloader and all avenues to repair should be explored first
If anyone needs to unbrick , there is a thread in my signature below ,shows how to go from complete brick , to restoring serial number and into system within 15mins
Click to expand...
Click to collapse
Just a bit curious what the smileys in line 1 and 2 actually meant.. any hidden snarkasm these?
As for the LP stock BL he has.. after reading through the various (and really insane bugs)... I do not agree with your suggestion to explore all avenues to repair... - and my reasoning for that is... because he got stuck and paralleled different guides... i can understand the urge to have one full fix instead of going all from empty... but i'm basically thinking that if he has put in CM13 then that guide has one Unblock BL (via MMBL) - we can't be sure which one he used (downgrade to LP, unlock then upgrade etc)... + tinkering with TWRP again was it the same twrp thats with CM13.. no way to be certain
So essentially he could be fixing it al but we often totally overlook TX " RR... becausee his type has ben Mania
Cons:
Cant really tell what v BL he has.. and maybe you can try all fixes menrion
£ not a nassuve breakast
I'll try a pros/cons thing...
Pro
Th XT tool as we both said phenoenal (including prerequisites), I am assuming your footer contains the same line I pasted?
Also with his touch screen and semi-sleep state etc - could cause someone to get a permanent bootloop
There could be other mods / zips which simply outwrite each other ldurng etcs.. Now the way you're suggesting... lets say I do that.. how which one touches which sys etc would just
Con
There is defin
Mmbl came about around July 16, he run cm 13 Feb 16.
.173 or .177 is unlocked or locked LP Boot loader.
xFSTK is to gain temp Boot loader.
He gets recognised in fastboot.
He can flash stock recovery .
He can sideload .
.
.
But
Can he ?
That's not sn ide btw
Well I'm not gonna dig too deep into the twrp touch issues (there could be conflicting drivers or even something weird i noticed in twrp302 anything below 20% batt (or if batstats corrupt) then the touch goes craycray.. so lets ignore that..
this thread is getting too heavy i won't have time - so - you can always backup ur data partition so no worries there.. nothing to lose..
one problem at a time.. as I said in first post my phone was bricked much worse i had mismatched fastdroidboot and bootimg and after pressing power on maybe 4-5 times.. it would only turn on once.. sometimes on and immediately off... sometimes on stuck on logo.. sometimes on and no logo but screen is black (corrupt splash)..
so lets just try to go baaaaaack to the futureeeeeee ... Ok I found the script I made (after 8 hours of trying EVERY combination from different guides I just took individual components and made my own.. ) -
I'm writing this in a hurry so please use my first reply to get the XFTS Ubrick Guide for the Files + get the LOLLIPOP One Click BL Unlock + Lollipop Raw image... Their Guide wants you to use Asus Flash but that program failed me every time... so I have got a differnt way to do it..
I'm copying this directly from my own script (so you can change if any paths/names different)... but do not change the order or sequence
Using OneClick (keep the unlock1234 files saved separately for later use)...
If you have these unlocked I just say do it again anyway - no harm...
Unlock Bootloader for LP Stock (even if you have MM you must downgrade by this same method)
Code:
#flash old droidboot for LP stock Bootloader
fastboot flash fastboot droidboot_2_20_40_197.img
fastboot reboot-bootloader
# must run reboot bootloader once with this droidboot before continuing - dn't skip this
# unlock bootloader (use files provided inside oneclick tool but instead of using their script, manually do it - more reliable)
fastboot oem start_partitioning
fastboot flash /tmp/start.sh tools/unlock1
fastboot flash /tmp/recovery.launcher tools/unlock2
fastboot flash /system/bin/logcat tools/unlock3
fastboot flash /tmp/unlock tools/unlock4
fastboot oem stop_partitioning
#if you get failed/error at oem stop - reboot to Bootloader (VOLUP+Power long press -
Release power at Asus Logo or long vibration) and re-do the last step
#if all done so far
fastboot reboot-bootloader
#white Asus logo means unlocked loader
fastboot flash recovery twrp3.img
reboot-bootloader
#toggle Up to choose Recovery - quick tap VOLUP+Power
#twrp will start
install Custom_MM_Rom.zip
#likely it will fail giving IFW 7 error - (intentionally did NOT put MM BL here), so
install Asus_MM_WW_420_184.zip (stock on stock only)
#let it be fully done, verify working MM stock OS
#check if it works - *sign* test your touch screen quickly and in dev tools Keep Debugging ENabled
#then power off - or if you have more options directly choose reboot
#during reboot vibration hit VOLUP+P to Fastboot
####RE-DO Entire first half again
fastboot flash fastboot droidboot_2_20_40_184.img
fastboot reboot-bootloader
# must run once with this droidboot before continuing
# unlock bootloader
fastboot oem start_partitioning
fastboot flash /tmp/start.sh tools/unlock1
fastboot flash /tmp/recovery.launcher tools/unlock2
fastboot flash /system/bin/logcat tools/unlock3
fastboot flash /tmp/unlock tools/unlock4
fastboot oem stop_partitioning
fastboot reboot-bootloader
#now only flash certain MM files (the rest should already be there from stock upgrade) - if you have different MM Img (if they release new one in future - all readers just need to ensure the TOKEN DNX IfW matching)
${FASTBOOTBINARY} flash splashscreen tools/splashscreen_551.img
fastboot flash token tools/bom-token_ze551ml_4_21_40_134.bin
fastboot flash dnx dnx_ze551ml_4_21_40_134.bin
fastboot flash ifwi ifwi_ze551ml_4_21_40_134.bin
fastboot flash fastboot droidboot_4_21_40_134.img
fastboot reboot-bootloader
#should now see black splashscreen + little red error msg for 2 seconds
#entering twrp again by toggling Recovery-> VOLUP+P
install superuser.zip
wipe cache + data
install yourcustomROM.zip
ryankabir said:
Just a bit curious what the smileys in line 1 and 2 actually meant.. any hidden snarkasm these?
As for the LP stock BL he has.. after reading through the various (and really insane bugs)... I do not agree with your suggestion to explore all avenues to repair... - and my reasoning for that is... because he got stuck and paralleled different guides... i can understand the urge to have one full fix instead of going all from empty... but i'm basically thinking that if he has put in CM13 then that guide has one Unblock BL (via MMBL) - we can't be sure which one he used (downgrade to LP, unlock then upgrade etc)... + tinkering with TWRP again was it the same twrp thats with CM13.. no way to be certain
So essentially he could be fixing it al but we often totally overlook TX " RR... becausee his type has ben Mania
Cons:
Cant really tell what v BL he has.. and maybe you can try all fixes menrion
£ not a nassuve breakast
I'll try a pros/cons thing...
Pro
Th XT tool as we both said phenoenal (including prerequisites), I am assuming your footer contains the same line I pasted?
Also with his touch screen and semi-sleep state etc - could cause someone to get a permanent bootloop
There could be other mods / zips which simply outwrite each other ldurng etcs.. Now the way you're suggesting... lets say I do that.. how which one touches which sys etc would just
Con
There is defin
Click to expand...
Click to collapse