Related
Anytime I try to do anything through Rom Manager (flash a ROM, nandroid backup, etc.) upon rebooting into recovery, I get a white triangle with an yellow exclamation point. After pressing the power button, the following text is revealed along with the Clockwork Recovery Menu.
Finding update package...
Opening update package...
Verifying update package...
E:failed to seek in /cache/update.zip (Invalid argument)
E:signature verification failed
Installation aborted.
If I select advanced->Reboot Recovery after receiving the error, the device reboots. After this second reboot, the process continues as it should have after the first reboot. I've tried downgrading the version of my Clockwork Recovery, but it seems to have no effect.
Any ideas?
...
I believe the standard array of initial questions would be:
1) Did you flash S-OFF?
2) Is your card FAT32 formatted
3) Try redownloading the file using a different browser (to ensure a cache doesn't deliver the same update.zip without trying)
jdmba said:
I believe the standard array of initial questions would be:
1) Did you flash S-OFF?
Click to expand...
Click to collapse
Yes.
jdmba said:
2) Is your card FAT32 formatted
Click to expand...
Click to collapse
Yes.
jdmba said:
3) Try redownloading the file using a different browser (to ensure a cache doesn't deliver the same update.zip without trying)
Click to expand...
Click to collapse
This failure isn't specific to any one file. Besides, I don't think it's a corruption of the file since it works when I select "reboot recovery" from the first failed attempt. In fact, this even happens when choosing "Backup ROM" from ROM Manager.
On a side note, I've tried wiping cache in ROM Manager as well.
Toggle Signature Verification and/or is d/l corrupt?
In CWM, have you tried toggling the on or off setting for the signature verification, as well as the other toggle?
Also, I read some superb advice here:http://http://forum.xda-developers.com/showthread.php?t=765930
check out the advice in post # 285 and see if that fixes you up.
Everyone seems to think my downloads are corrupt. That is definitely not the problem. If they were corrupt, they wouldn't function after the first reboot. They would continue to fail. Let me try explain my problem another way...
Here's my device setup...
Radio - 2.15.00.07.28
Kernel - King's BFS #4
ROM - SR Vanilla RC 2
CWM Version - 2.5.0.5
ROM Manager Version - 2.0.2.6
Here's a process I'm following...
1. Open ROM Manager
2. Clear Download Cache (Just to be sure!)
3. Select Backup Current ROM which causes reboot into recovery.
4. Receive the error which I outlined in my first post. *NOTE* I have not downloaded nor chosen to flash ANY update.zip files. *NOTE*
5. Open the advanced menu in CMW and choose "Reboot recovery" which causes the phone to reboot into recovery.
6. The backup progresses like it should have after the first reboot.
Again, the process above does not involve the use of any downloaded update.zip files. No ROMS, no Kernels, etc.
Does ROM Manager create it's own update.zip file stored in /cache to execute whatever function it needs to after reboot? It appears that might be the case.
I've attempted to reinstall ROM Manager and downgrade to an early version of CWM in ROM Manager. Neither seem to have helped.
I had the same problem trying to flash the latest leedroid
I entered recovery, de-selected signature verification and then flashed the rom through recovery mode.
Flashed normally and up to now it looks like it worked (waiting for first boot)
Hope this helped
Both signature verification and script asserts are toggled off. This is why the update.zip will flash after the second reboot into recovery and manually.
In recovery, is cache, data, or system mounted? If so, can you unmount any/ all, and reboot?
Sent from my ADR6300 using XDA App
I just started having this problem today, at least i noticed it today. It acts as if the signature verification is enabled the first try and disabled the second time. I can't find ANY way to fix this but reboot recovery and it works... If anyone finds a solution, please post.
*edit* I also noticed the "Fix Permissions" utility doesn't work in ROM Manager. Dont know if this is related or not.
PIYIRIO said:
I just started having this problem today, at least i noticed it today. It acts as if the signature verification is enabled the first try and disabled the second time. I can't find ANY way to fix this but reboot recovery and it works... If anyone finds a solution, please post.
Click to expand...
Click to collapse
Did you change anything today? I found someone in the SR ROM thread today that started having the same problem.
No, only an app and removed it. I dont know how long it has been broke since I haven't used it since SR 3.0rc1.. got tired of the reminder for rc3 and it wouldn't automagically run the install.zip.
Interesting.... Please post as this shakes out.
Sent from my ADR6300 using XDA App
I have this same issue, I think it's an issue with Rom Manager. No matter what I try to do from there (Reboot to Recovery, make backup, flash zip, etc.) I get that string of messages.
If I download a file from ROM manager to be flashed, I have to move the file to the root of the sd card before booting to recovery for it to flash correctly. I have just gotten used to doing it this way.
srt4mn said:
I have this same issue, I think it's an issue with Rom Manager. No matter what I try to do from there (Reboot to Recovery, make backup, flash zip, etc.) I get that string of messages.
If I download a file from ROM manager to be flashed, I have to move the file to the root of the sd card before booting to recovery for it to flash correctly. I have just gotten used to doing it this way.
Click to expand...
Click to collapse
Me as well
PIYIRIO said:
*edit* I also noticed the "Fix Permissions" utility doesn't work in ROM Manager. Dont know if this is related or not.
Click to expand...
Click to collapse
If you look in the OP for the SR ROMS, you'll see that a known issue. He includes a fix_permissions binary instead.
I've reached out to the developer. Hopefully we will hear from him soon.
Can you guys try clearing your download cache, and then reflashing recovery?
Possible workaround
Koush said:
Can you guys try clearing your download cache, and then reflashing recovery?
Click to expand...
Click to collapse
Cache wipe have been tried, see post #3.
I have some info that may be valuable:
This evening I rooted my Desire (SLCD) using Unrevoked 3.14 and recovery-clockwork-2.5.0.7-bravo.img I realize this is the incredible forum but hold on.. hear me out
I observed the _exact_ same behavior:
- Yellow eclamation + second reboot to recovery would run backup, also happened when selecting "Reboot Into recovery" in RomManager (RM)
- Tried DL cache wipe in RomManager,
- Tried reflash of recovery
This fixed it for me:
- Re-root via Unrevoked 3.14 using recovery-clockwork-2.5.0.1-bravo-slcd.img
- Re-flash CM (this may be optional, I don't know)
- Boot ROM and start RM just to have it tell me I need to install recovery (obviosly didn't detect my 2.5.0.1-bravo-slcd)
- Allow RM to flash 2.5.0.7-bravo via download
- Now "Backup ROM" and "Reboot to recovery" works as intended
- RM reports 2.5.0.7-bravo installed, recovery booted (via RM) is 2.5.0.7-bravo BUT recovery booted using HBOOT (back+power on Desire) is 2.5.0.1-bravo-slcd (!)
Note: Incredible users should _not_ use -bravo recovery images(!) just outlining how I made it work to help you find a solution
Koush said:
Can you guys try clearing your download cache, and then reflashing recovery?
Click to expand...
Click to collapse
Worked for me. Thanks Koush!
Sent from my ADR6300 using XDA App
Didn't work for me.. I've tried everything that I can think of. Different SD cards, i've formated /data/ /cache/ and reinstalled..
i'm using virtuous 2.7
Stuck in a bootloop. Here's my story.
Updated to 4.4.2 earlier today.
Tried to root my Nexus 7 later after the update. Here's what I did:
rebooted into bootloader with adb (adb reboot-bootloader)
unlocked the bootloader with fastboot (fastboot oem unlock)
flashed clockworkmod using fastboot (this is the file i downloaded and flashed: -http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.3-flo.img)
rebooted into recovery
selected "install zip>choose zip from sdcard" (trying to install supersu.zip file that I had loaded onto the internal memory)
Here's where I ran into trouble. After selecting "choose zip" nothing happens, and a message shows up on botton of the screen that says "E: Can't mount /sdcard"
So I can't install anything from clockworkmod.
I rebooted into bootloader, tried to re-flash using fastboot - "device not found"
I tried to reboot the device into android - bootloop animation
I tried wiping data, cache, factory reset, dalvik chache, etc from recovery - still getting bootloop animation
Any ideas?
Ok, I wiped/deleted sdcard data from clockworkmod and I managed to get it to boot.
That's deadly but I still don't have root, which was the point of this in the first place. Anyone know where I went wrong?
Strange. I did pretty much the exact same procedure and it worked for me.
Sent from my Nexus 10 using xda app-developers app
So, I flashed TWRP.
Tried installing SuperSu from there. This worked slightly better than Clockworkmod Recovery, it at least could read the internal storage, and allowed me to select the supersu.zip file. But I get the following error when I try to install it:
E: Unable to open zip file
Error flashing zip 'sdcard/Download/UPDATE-SuperSU-v1.80.zip
Not sure what's happening here.... May have to do with the 4.4.2 update? Maybe I'll try flashing the 4.4.2 factory image and then retrying the above steps.
I also did pretty much the same. I had a new Nexus 7 2013. The very first thing I did was to update to 4.4.2 through OTA before I went to rooting procedures:
Unlock bootloader (data was wiped because of it)
Flash TWRP
Flash superuser.zip file through TWRP
Everything worked fine.
First of all, I want to tell that I am a beginner and do not know much about rooting and custom ROM installation.
Few days back, I became very keen to know what is custom ROM and is there any custom ROM available for my HTC One X. I searched through internet and found one, downloaded it. Rooted my phone, Unlocked bootloader. After that I installed CWM touch recovery. Everything was going great. Then, I first flashed the kernel given along with that custom ROM. it Flashed. Then, I flashed that Custom ROM. I Showed an error. I flashed it twice or thrice but it stucked on that error. Also in a Hurry, or Excitement, I forgot to take a backup of my previous ROM. After that, I switched on my phone it does nothing and stucked at HTC Bootscreen. I factory reset my phone, it wiped all data from phone. I Thought, a RUU would work, but it also doesn't worked.
I went to HTC Service Center, they are saying that motherboard will be replaced, which is almost of same cost of phone. I cannot spend so much.
I tried so many ways, but nothing worked.
So, I am Finally here seeking help from Experts. Any help will be highly appreciable.
Sorry for my bad English.
Details :
HBoot: 1.73
S-ON
Endevouru
Try this, flash this recovery :
https://www.dropbox.com/s/qp21ubo10xetcvn/Philz recovery 5.15.9.img
Make a full wipe and install the rom.zip. and flash the boot.img from the rom.zip
What rom were you trying to flash ?
If its a kitkat ROM you can't use cwm recovery to flash that rom.. you either use philz recovery given by mr hofs or latest twrp recovery from the twrp thread or indexed listing thread..
a.broken.star said:
If its a kitkat ROM you can't use cwm recovery to flash that rom.. you either use philz recovery given by mr hofs or latest twrp recovery from the twrp thread or indexed listing thread..
Click to expand...
Click to collapse
You mean this one
https://www.dropbox.com/s/14c1ikgsp38axwv/twrp-recovery2.img
Righto...:thumbup:
i was trying to flash MaximusHD rom.
and Philz recovery i have tried already. The problem is I do not have access to storage. All i have is Bootloader access. and nothing on my phone
Charge the battery, unlock the bootloader, flash the custom recovery and install a new rom
Mr Hofs said:
Charge the battery, unlock the bootloader, flash the custom recovery and install a new rom
Click to expand...
Click to collapse
i have tried this too.. no ROM is being flashed. everytime it ends with some error(s)
What error ??? Be more specific otherwise we cant get 1 step ahead
1: Is your bootloader unlocked ?
2: flashes the custom recovery ?
3: what rom ?
4: did you also flashed the boot.img ?
Please answer specifically !
Mr Hofs said:
What error ??? Be more specific otherwise we cant get 1 step ahead
1: Is your bootloader unlocked ?
2: flashes the custom recovery ?
3: what rom ?
4: did you also flashed the boot.img ?
Please answer specifically !
Click to expand...
Click to collapse
1. Bootloader was unlocked, i have relocked it. I'll unlock it. no Issues.
2. I have tried CWM philz touch custom recovery. I'll install it again
3. It do not have any ROM at present. Earlier it had 4.2.2 JB Stock ROM
4. Yes, I flashed boot.img. Nothing worked
1. Unlock the bootloader again
2. Flash the Philz-Recovery
3. Boot the Recovery
4. Install the Rom via ADB-Sideload
5. Reboot to bootloader
6. Flash the Kernel (boot.img)
7. Reboot into system
If you get an error, then post the Code here , so we can find out what's wrong with your phone.
Sent from my HTC One using XDA mobile app
HD2Bastler said:
1. Unlock the bootloader again
2. Flash the Philz-Recovery
3. Boot the Recovery
4. Install the Rom via ADB-Sideload
5. Reboot to bootloader
6. Flash the Kernel (boot.img)
7. Reboot into system
If you get an error, then post the Code here , so we can find out what's wrong with your phone.
Sent from my HTC One using XDA mobile app
Click to expand...
Click to collapse
sorry for this stupid question. But how to use ADB Sideload..??
Just mount the sdcard in the mounts and storage menu ! No need for adb sideload
And don't just install the rom, you must perform a full wipe before that !
Factory reset
Wipe cache partition
Wipe dalvik cache
Format system
Format data
Format cache
Then install the rom !
Mr Hofs said:
Just mount the sdcard in the mounts and storage menu ! No need for adb sideload
And don't just install the rom, you must perform a full wipe before that !
Factory reset
Wipe cache partition
Wipe dalvik cache
Format system
Format data
Format cache
Then install the rom !
Click to expand...
Click to collapse
ok i will try this and will be back with whatevr result comes out....
I bricked mine too , this is what I did
mohitsinghl said:
ok i will try this and will be back with whatevr result comes out....
Click to expand...
Click to collapse
If that doesn't work try this , this is what I did when I bricked my HTC One X:
1. Download Fastboot
2. Download adb
3. Download cm-10.2.1-endeavoru.zip (https://download.cyanogenmod.org/?device=endeavoru)
(I used this one , it's justs so you get your SD Card Working again and you can
put ROMS and everything on it again)
4. Download openrecovery-twrp-2.4.0.0-endeavoru-JB (http://techerrata.com/browse/twrp2/endeavoru)
(This one will be used because it has touch ability's and you can install ROMS with it )
4.1 Or you can download recovery-clockwork-touch-6.0.4.7-endeavoru.img (a.k.a Philz recovery)
(This one will be used because it has touch ability's and you can install ROMS with it )
( I used Philz recovery 5.15.9.img (provided by Mr Hofs -> who is a great guy btw)
5. Download openrecovery-twrp-endeavoru-2.1.7 (http://techerrata.com/browse/twrp2/endeavoru
(This one will be used for adb push commands, openrecovery-twrp-endeavoru-2.1.7 has a built
in ability for your sd-Card , adb can recoginze it but the problem is your touch will not work.)
6. Go into bootloader -> fastboot and do this:
6.1 fastboot flash recovery openrecovery-twrp-endeavoru-2.1.7.img
7. Go into recovery (Hboot -> recovery)
7.1 just open the recovery, your touch will probably not work. DONT LOCK IT JUST LEAVE IT OPEN
(ADB sideload didn't work for me so that's why we are going to do this)
IF YOUR TOUCH WORKS YOU CAN SKIP STEP 8
7.2 do this command: adb devices
If you don't find your devices in this then the next steps will not work.
YOU HAVE TO SEE YOUR DEVICE
7.3 do this command: adb push cm-10.2.1-endeavoru.zip /sdcard/
You can only do cm-10.2.1-endeavoru.zip if the zip file is located in the same folder your using
with command. I'm not sure about /sdcard/ . I cant remember anymore But this will put the
but this will put the zip Directly on your SDcard.
8. Go to bootloader -> fastboot
8.1 do this command: fastboot flash recovery openrecovery-twrp-2.4.0.0-endeavoru-JB.img
8.2 or do this command: fastboot flash recovery Philz recovery 5.15.9.img
Your touch wasn't working but it will work now.
9. Go to booloader -> fastboot
9.1 extract the boot.img from the Download cm-10.2.1-endeavoru.zip into the fastboot folder
9.2 do this command fastboot flash boot boot.img
9.3 fastboot erase cache
10. Go back to recovery
10.1 Wipe User Data
10.2 Wipe data cache
10.3 Go to advanced -> wipe Dalvik Cache
11. Install zip from sdcard
11.1 Choose cm-10.2.1-endeavoru.img
11.2 Install the zip WITH full wipe
12. After the install, reboot. You should have a full functional HTC ONE X now
13. Now but your ROM's(ZIP FILES)/Recovery(ZIP FILES)/Kernels and everything you want on your HTC because
You can see your HTC on your PC again!
I tried adb push.. But i cant find the pushed zip on sd card in recovery.. Moreover i tried flashing using fastboot command i.e. fastboot flash zip rom.zip it ended with an error <remote not allowed>
Sent from my Titanium S5 using XDA Free mobile app
For maximus hd do this :
Flash Philz 5.15 and mount the sdcard and wait literally minutes to let the sdcard pop up, copy the rom, do a full wipe and install it then also flash the boot.img from the maximus rom in the bootloader and reboot the phone
Don't make this so hard on yourself !
Philz 5.15 recovery is not flashed. And ended with an error 0xa . any other way??
Sent from my Titanium S5 using XDA Free mobile app
Uhm really.....second time : post the error/your taken steps ! I'm not playing a game of sharades here ......
If it's not flashed you are doing something wrong
Please don't get angry on me.. M a beginner.
Okey now i have managed to flash philz recovery version 6 i.e. philz touch 6 but still cant get storage popup on my pc. I waited 30 mins after clicking mount /storage/sdcard0
Sent from my Titanium S5 using XDA Free mobile app
Requirements:
HTC ONE X (mine was international but you are free to try anyways )
UNLOCKED BOOTLOADER
PATIENCE.
1. Download Fastboot
If you have adb and fastboot already you can skip STEP 1 and STEP 2
2. Download adb
3. Download cm-10.2.1-endeavoru.zip (https://download.cyanogenmod.org/?device=endeavoru)
(I used this one , it's justs so you get your SD Card Working again and you can
put ROMS and everything on it again)
4. Download openrecovery-twrp-2.4.0.0-endeavoru-JB (http://techerrata.com/browse/twrp2/endeavoru)
(This one will be used because it has touch ability's and you can install ROMS with it )
4.1 Or you can download recovery-clockwork-touch-6.0.4.7-endeavoru.img (a.k.a Philz recovery)
(This one will be used because it has touch ability's and you can install ROMS with it )
( I used Philz recovery 5.15.9.img (provided by Mr Hofs -> who is a great guy btw)
5. Download openrecovery-twrp-endeavoru-2.1.7 (http://techerrata.com/browse/twrp2/endeavoru
(This one will be used for adb push commands, openrecovery-twrp-endeavoru-2.1.7 has a built
in ability for your sd-Card , adb can recoginze it but the problem is your touch will not work.)
6. Go into bootloader -> fastboot and do this:
6.1 fastboot flash recovery openrecovery-twrp-endeavoru-2.1.7.img
7. Go into recovery (Hboot -> recovery)
7.1 just open the recovery, your touch will probably not work. DONT LOCK IT JUST LEAVE IT OPEN
(ADB sideload didn't work for me so that's why we are going to do this)
IF YOUR TOUCH WORKS YOU CAN SKIP STEP 8
7.2 do this command: adb devices
If you don't find your devices in this then the next steps will not work.
YOU HAVE TO SEE YOUR DEVICE
7.3 do this command: adb push cm-10.2.1-endeavoru.zip /sdcard/
You can only do cm-10.2.1-endeavoru.zip if the zip file is located in the same folder your using
with command. I'm not sure about /sdcard/ . I cant remember anymore But this will put the
but this will put the zip Directly on your SDcard.
8. Go to bootloader -> fastboot
8.1 do this command: fastboot flash recovery openrecovery-twrp-2.4.0.0-endeavoru-JB.img
8.2 or do this command: fastboot flash recovery Philz recovery 5.15.9.img
Your touch wasn't working but it will work now.
9. Go to booloader -> fastboot
9.1 extract the boot.img from the Download cm-10.2.1-endeavoru.zip into the fastboot folder
9.2 do this command fastboot flash boot boot.img
9.3 fastboot erase cache
10. Go back to recovery
10.1 Wipe User Data
10.2 Wipe data cache
10.3 Go to advanced -> wipe Dalvik Cache
11. Install zip from sdcard
11.1 Choose cm-10.2.1-endeavoru.img
11.2 Install the zip WITH full wipe
12. After the install, reboot. You should have a full functional HTC ONE X now
13. Now but your ROM's(ZIP FILES)/Recovery(ZIP FILES)/Kernels and everything you want on your HTC because
You can see your HTC on your PC again!
Why are you flashing so many recoveries ?
Just flash Philz 5.15 for non kitkat roms or twrp2 for use with all roms. On those 2 recoveries all features work including touch on all hboot numbers. You don't need 2.4 at all !
And both recoveries support UMS inside the recovery. I think you only made it a bit hard on yourself this way. The rom (CM) didn't make your sdcard work again btw.....any rom does but it has to be installed all in the correct way
Sorry to say but your steps are a bit of a mess
I would have explained it like this....taking in mind that knowing fastboot is mandatory and common :
1: flash either Twrp2 or Philz 5.1.5 (for non kitkat roms)
2: enter the recovery and mount the sdcard in the mount menu, wait literally minutes to let the sdcard pop up
3: copy the desired rom
4: unmount and perform a full wipe (that means to wipe ALL except sdcard)
5: install the rom.zip
6: reboot to the bootloader and flash the boot.img from the desired rom
7: reboot
Done !
Mr Hofs said:
Why are you flashing so many recoveries ?
Just flash Philz 5.15 for non kitkat roms or twrp2 for use with all roms. On those 2 recoveries all features work including touch on all hboot numbers. You don't need 2.4 at all !
And both recoveries support UMS inside the recovery. I think you only made it a bit hard on yourself this way. The rom (CM) didn't make your sdcard work again btw.....any rom does but it has to be installed all in the correct way
Sorry to say but your steps are a bit of a mess
I would have explained it like this....taking in mind that knowing fastboot is mandatory and common :
1: flash either Twrp2 or Philz 5.1.5 (for non kitkat roms)
2: enter the recovery and mount the sdcard in the mount menu, wait literally minutes to let the sdcard pop up
3: copy the desired rom
4: unmount and perform a full wipe (that means to wipe ALL except sdcard)
5: install the rom.zip
6: reboot to the bootloader and flash the boot.img from the desired rom
7: reboot
Done !
Click to expand...
Click to collapse
The problem with this was that when I mounted my sdcard nothing popped up. (I litterly waited 30 minutes) I explain it this way because when following other threads explaining how to "unbrick" your phone. I got a lot of issues during the proces. Like SD-card not mounting, fastboot not working, adb not working, touch screen not working, promises of recovery's that your device wil be recognized for usb sideload, ... I ran into a lot of problems and I had to figure it out myself how I had to unbrick my HTC because I forgot to take a back-up. And these were the steps I did.I know your explanation is more 'ideal" but sometimes people can't follow the ideal path because of issues/bugs/problems and that's where my thread comes in
If it doesn't pop up its a pc driver issue
Mr Hofs said:
If it doesn't pop up its a pc driver issue
Click to expand...
Click to collapse
For me it wasn't I had properly installed all drivers. it just said endeavoru on my devices. And i couldn't connect. But once I installed the TWRP recovery it showed HTC ONE X and it worked
The twrp did nothing, as i said .... it was a driver issue. Once you booted to the bootloader it got picked up and drivers were added/modified correctly. If the drivers were installed properly it should say MYHTC .....
@vsp33ddyv MAAAAAAAAAN you saved me!!! I soft bricked my dad's phone by accidentally flashing the recovery to the boot partition as well as the recovery partition so the stock ROM was overwritten by the recovery. I wasn't planning on flashing any ROMs so there was no rom zip on my sdcard. I downloaded CM11, tried sideloading it through adb but it kept saying it didn't recognize the device. I tried USB storage mounting but that didn't work either (no matter how long I waited). I would have NEVER guessed that all I needed to do was download that broken (I say broken because touch doesn't work so basically nothing works) TWRP recovery img!!!! @Mr Hofs, sir, you were wrong. It wasn't the drivers. ADB didn't recognize my device, I changed my recovery and BAM it's suddenly there. I had already rebooted the device a million times so it's not like the drivers suddenly decided to get installed (there were no notifications either).
So thank you thank you thank you SO DAMN MUCH!
Thank you very much.
If it hadn't been for your tutorial i would've had to throw the phone.
Many thanks.
Hello everybody,
Here my problem :
I tried to install a custom rom, I failed. Now, my smartphone stay on the Asus logo screen. I tried to follow this - http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835 - to fix the problem, but when I connect phone and laptop, adb doesn't find the device.
If I continue and go in recovery mode (using TWRP), laptop can access the phone (I can see internal memory but not external).
And if I try the ADB sideload, there is no device again...
It's the first step, I don't see any other way to unbrick the phone...
Thanks in advance
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 be lucky your phone is recognized
Hello,
Frist, thank you for your answer. I had already tried this way but nothing. Finally, I fixed the problems (detect phone and unbrick phone).
1-In TWRP, I loaded recovery.img, boot.img and droidboot.img. Reboot in recovery mod, but I had the dead droid... so I pushed on power and volume up till I have a new screen.
2-In this part, I did a Wipe/Factory reset (useless I think), reboot in recovery mode (still dead droid). This time I selected the line "update with adb" (with an ASUS firmware). Then I had a message who told me update adb sideload. I did it and it installed the firmware. The smartphone reboot correctly.
Now, I have the same problem I had yesterday. In TWRP, my external storage isn't detected...
you use stock recovery or custom recovery, if you use stock recovery external-storage won't detected
Hello,
Thank you Bar4, I explained above how I fixed my problems. Now I'm searching a way to make TWRP (TWRP 3.0) detect my external storage to install Cyanogenmod 13.0. If it's really not possible, I would try with CWM (I have seen it in your screen).
Edit : I guess custom, TWRP. It's why I don't understand why it doesn't allow me to mount SD card or doesn't detect this same SD Card.
Mara Udé said:
Hello,
Thank you Bar4, I explained above how I fixed my problems. Now I'm searching a way to make TWRP (TWRP 3.0) detect my external storage to install Cyanogenmod 13.0. If it's really not possible, I would try with CWM (I have seen it in your screen).
Click to expand...
Click to collapse
i use twrp 3.0 too, but external sd detected. no need to put on external storage, you can flash Cm 13 through internal storage
if you want to install custom rom it's better if you make a backup first, so if happen you failed when installing new rom or maybe you don't like it (new rom) you can go back to stock rom through TWRP restore
Ok, failed again...
Try a different rom or redownload the rom it might have been a bad download.
The error message says there is no updater script in the zip meaning it can't install anything as the updater script tells what directories to install the files if I seen it correctly that is.
Sent from my ASUS_Z00AD using Tapatalk
Mara Udé said:
Ok, failed again...
Click to expand...
Click to collapse
maybe the CM 13 zip file you have download corrupted, try to re-download and re-flash it again. if still failed try another rom
( i'm using AICP Rom "based on CM 13 too") try it, it's awesome Rom ---> do clean install wipe all except internal storage and external storage
http://forum.xda-developers.com/zenfone2/development/rom-c-p-t3285951/post64645756#post64645756
http://opengapps.org/ ( select x86-6.0-nano )
Hi,
Sorry for this late answer. As I failed to install those roms (CM13, Bliss), I'm going to stop here and wait for the Marsmallow update. But I'm happy my phone isn't brik anymore.
Thank you all.