Related
Well, I started out with CM7 RC4, and everything was dandy.
But then I decided to try out Virtuous. I did a Titanium Backup, then did a nandroid backup and wiped through ROM Manager. Virtuous was horribly laggy, however, so I decided to switch back to CM.
Upon restoring my nandroid, my G2 froze at the 'data' section, and I was forced to pull the battery. After reboot, it couldn't get past the white HTC screen. When I booted back into CWM, I immediately got the following:
"ClockworkMod Recovery v3.0.0.5
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log"
It reloads those errors every time I go back to the main menu of CWM, as well.
Every ROM I try and flash still gets stuck at the splash screen.
I've wiped everything there is to wipe, and any time I try and restore any of my nandroids, I get:
"Erasing boot before restore...
Error while erasing boot image!"
I've been looking for a solution for the past 4 hours and I can't seem to fix it. I don't even know what ROM is actually loaded on my phone.
Please, if anyone can help, it would be greatly appreciated! I just want to be able to actually use my phone.
pokemontrainer4life said:
Well, I started out with CM7 RC4, and everything was dandy.
But then I decided to try out Virtuous. I did a Titanium Backup, then did a nandroid backup and wiped through ROM Manager. Virtuous was horribly laggy, however, so I decided to switch back to CM.
Upon restoring my nandroid, my G2 froze at the 'data' section, and I was forced to pull the battery. After reboot, it couldn't get past the white HTC screen. When I booted back into CWM, I immediately got the following:
"ClockworkMod Recovery v3.0.0.5
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log"
It reloads those errors every time I go back to the main menu of CWM, as well.
Every ROM I try and flash still gets stuck at the splash screen.
I've wiped everything there is to wipe, and any time I try and restore any of my nandroids, I get:
"Erasing boot before restore...
Error while erasing boot image!"
I've been looking for a solution for the past 4 hours and I can't seem to fix it. I don't even know what ROM is actually loaded on my phone.
Please, if anyone can help, it would be greatly appreciated! I just want to be able to actually use my phone.
Click to expand...
Click to collapse
From the looks of it. It seems that you messed up your recovery , all you have to do is go back into fastboot and then reflash/reinstall the recovery.img and everything should be working fine afterwards
derykisonder said:
From the looks of it. It seems that you messed up your recovery , all you have to do is go back into fastboot and then reflash/reinstall the recovery.img and everything should be working fine afterwards
Click to expand...
Click to collapse
I've read a few places that you need the engineering hboot. Is that true?
And how can I tell if I have it already?
Well it appears I don't have the engineering hboot. When I flashed the recovery via fastboot it came back saying "FAILED (remote: not allowed)".
Is there a way I can install the hboot without using Terminal on the phone?
Wow same for my i dont have Eng hboot i thought i put it in my phone but somehow its gone know D: looking for solution :/
OK, I had this same problem and was able to fix it. I d on't know how many of you this will help but here is what I did. I was able to boot into CWM and choose advanced restore where I manually restored the system and data files. I then reboot my device and I was able to get it to fully boot. So far I have seen no real issues with the phone and it's better than a brick; it will at least get you running again so you can try something different if need be.
pokemontrainer4life said:
Well it appears I don't have the engineering hboot. When I flashed the recovery via fastboot it came back saying "FAILED (remote: not allowed)".
Is there a way I can install the hboot without using Terminal on the phone?
Click to expand...
Click to collapse
Ever heard of adb?
Sent from my T-Mobile G2 using XDA Premium App
flash & restore
I had a workaroudn for something similar - basically phone wouldnt boot past splash screen after losing power. I was able to make a CWM backup, and the only way i could find to get all my things back was to do a fresh os flash and work with some nandroid abckup files to try to extract the data out manually - there is one called Nandroid Manager, but it ahsnt always worked for me, but a great concept. worth a try, if not there appears to be other products on the market now which may help
Well, I have rooted my phone with unrevoked it installed the recovery mod 2.5.0.7 and I'm a bout to flash my phone. Thing is though I've been here for a while.
The story goes like this.. Relatively chronological..
I download HBOOT drivers install them on my Windows 7 64bit. I then download and run unrEVOked3, hook up my phone and choose charge only. unrevoked3 does it's thing and everything seems fine. I partition the SDcard with 6,5gb fat32 and 1gb ext4. Then i go into recovery i then go to wipe data/factory reset and chose it. Then i cant find dalvik data at first but i later find it, so i wipe that. Then I chose to install zip from sdcard which earlier moved. The InsertCoin A2SD+ 1.0.9 mod.
It starts up finds the file and starts flashing or so it seems.
It stops, and I cant remember the error message. So, I go searching cant really find anything except the fact that I should have wiped cache partitions also.. So I go back do a full wipe again and run it.
Then I get this error message: ( i tried again with a Cyanogen mod, and i got assert_failed write_raw_image...)
- assert failed: Package_extract_file("boot.img","/tmp/boot.img")
E: Error in /sdcard/InsertCoin_GB_Sense2.1_A2SD+_1.0.9.zip
(status 7)
Installation aborted..
I then find the baadnwz irc and ask for help there.. repartition my sdcard with gparted, and run through it all again...
Same error..
I then notice that CWMR is saying:
E: Cant fint MISC:
E: Cant mount Cache:recovery/command
E:Cant find misc:
E:Cant mount cache:recovery/log
E: cant fin misc:
I ask if this is normal, NO, is the clear answer i get.. so i test different things, new repartition correct sized and everything..
Still same..
Then I go and download the Froyo RUU and install it reset everything (of course i forgot to sync my contacts..) and i do everything from the top root, cwrm and try flashing but the same errors are still there..
So i then create this thread hoping that this error already isnt here after search.. And hoping someone can help me..?
I'm running the HTC Desire on HBOOT 0.93.0001, radio 5.11.05.27.
Worst thing is no matter how many times i wiped the different things no changes were made on the phone, when i rebooted i still got up my original bckgrnd image and everything...
So, what is going on?
It might be worth watching a few vids and reading a few guides. Here's a start http://forum.xda-developers.com/showthread.php?t=1016084. Also, don't worry. I messed up too when I first started to root and flash.
I can't remember what the status 7 error is and how to fix it. Think it's just to re-download the rom and try again.
If you have PVT4 device, you need to use AmonRA recovery.
I guess you're S-ON? If S-OFF try recovery from my sig.
Ironically I have used the tutorial in the development forum.. Used all the videos i could find, except s-off cause i was told i didnt have to do that when i was just flashing a new ROM..
How do i know if i have a pvt4 device?
edit: i found out.. im a pvt4 device..
Then root again, download recovery from my sig unpack .img and choose "custom recovery" in unrevoked and select it.
You can also use AmonRA recovery.
Or if you don't want to root again, S-OFF and flash new recovery in fastboot.
I don't really understand why they made CWM default recovery in unrevoked, people have so many issues with it. :-(
Sent from my HTC Desire using XDA App
spike0209 said:
Well, I have rooted my phone with unrevoked it installed the recovery mod 2.5.0.7 and I'm a bout to flash my phone. Thing is though I've been here for a while.
The story goes like this.. Relatively chronological..
I download HBOOT drivers install them on my Windows 7 64bit. I then download and run unrEVOked3, hook up my phone and choose charge only. unrevoked3 does it's thing and everything seems fine. I partition the SDcard with 6,5gb fat32 and 1gb ext4. Then i go into recovery i then go to wipe data/factory reset and chose it. Then i cant find dalvik data at first but i later find it, so i wipe that. Then I chose to install zip from sdcard which earlier moved. The InsertCoin A2SD+ 1.0.9 mod.
It starts up finds the file and starts flashing or so it seems.
It stops, and I cant remember the error message. So, I go searching cant really find anything except the fact that I should have wiped cache partitions also.. So I go back do a full wipe again and run it.
Then I get this error message: ( i tried again with a Cyanogen mod, and i got assert_failed write_raw_image...)
- assert failed: Package_extract_file("boot.img","/tmp/boot.img")
E: Error in /sdcard/InsertCoin_GB_Sense2.1_A2SD+_1.0.9.zip
(status 7)
Installation aborted..
I then find the baadnwz irc and ask for help there.. repartition my sdcard with gparted, and run through it all again...
Same error..
I then notice that CWMR is saying:
E: Cant fint MISC:
E: Cant mount Cache:recovery/command
E:Cant find misc:
E:Cant mount cache:recovery/log
E: cant fin misc:
I ask if this is normal, NO, is the clear answer i get.. so i test different things, new repartition correct sized and everything..
Still same..
Then I go and download the Froyo RUU and install it reset everything (of course i forgot to sync my contacts..) and i do everything from the top root, cwrm and try flashing but the same errors are still there..
So i then create this thread hoping that this error already isnt here after search.. And hoping someone can help me..?
I'm running the HTC Desire on HBOOT 0.93.0001, radio 5.11.05.27.
Worst thing is no matter how many times i wiped the different things no changes were made on the phone, when i rebooted i still got up my original bckgrnd image and everything...
So, what is going on?
Click to expand...
Click to collapse
try this, we have same problem... http://forum.xda-developers.com/showthread.php?p=16320099#post16320099
Somehow, installing alpharev and s-offing the phone, and then installing a new recovery helped me. Im now running cyanogen 7 om my phone
I would love your guy's opinions on this issue. I was planning to do a fresh install of Cyanogenmod due to wifi issues when I ran into some trouble. I just updated my Clockworkmod recovery from 3.0.0.8 to 5.0.2.0 this morning, and it has been bringing up errors along the lines of:
Code:
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/log
E: Error in /cache/recovery/log
(Read-only file system)
I read up on these errors, and it seems that attempting to flash ROMs and whatnot with these errors often lead to bricked devices. So far, my device still works fine (minus the WiFi, obviously), and I've successfully flashed the recovery several times, performed a nandroid backup, and reflashed my kernel without error, as far as I can tell. However, given the nature of these errors, I am much too nervous to try reflashing Cyanogenmod. So far I have attempted downgrading CWM, checking my emmc and checked the cache partition for the files CWM supposedly can't open. last_log is present, but log is not. From the results of the emmc test, I think it's working fine, but I'd like you guys to verify that for me. Below is about as detailed a log as I can give of what has happened today. Any assistance in fixing this problem and making sure it is safe to reflash Cyanogenmod would be extermely appereciated.
Phone Info
HTC Droid Incredible (ADR6300)
Cyanogenmod 7.1.0 RC1
Android 2.3.4
Clockworkmod Recovery 3.0.0.8
Incredikernel 2.6.38.8 (8/15/11)
HBOOT 0.92.0000
Radio 2.15.00.07.28
S-OFF
Code:
Events leading up to this:
Flashed CWM 5.0.2.0 through ROM Manager-flash failed
Rebooted into recovery-still running 3.0.0.8
Rebooted phone
Tried again through ROM Manager with "erase recovery" option checked
Rebooted into recovery-still running 3.0.0.8
Rebooted phone
Flashed CWM 5.0.2.0 through Terminal Emulator
Rebooted into recovery-flash was successful
Rebooted phone
Discovered WiFi error issue
Rebooted into CWM 5.0.2.0
Performed a nandroid backup, which appeared to be successful
Errors appeared at some point, can't remember when.
"E: Can't open /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/last_log"
Rebooted phone
Rebooted into CWM 5.0.2.0
Wiped Dalvik cache and reflashed incredikernel, thinking it would fix the WiFi issue
Flash seemed successful, same errors popped up again, can't remember exactly when
Rebooted phone
Researched errors, came to notice that navigating menus and backing out now caused:
"E: Error in /cache/recovery/log
(Read-only file system)
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/last_log"
Further navigation would always produce:
"E: Can't open /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/last_log"
Code:
Steps taken to fix the problem (so far)
Tried flashing CWM 3.0.0.8 through ROM Mangager
Rebooted into recovery-still running 5.0.2.0
Tried flashing CWM 3.0.0.8 through adb
Rebooted into recovery-flash was successful
Errors still persisted
Found a thread suggesting the problem may be with a faulty emmc
Ran "cat /proc/kmsg | grep mmc0" through adb to test the emmc
Results of test
Checked to see if log and last_log files exist
Found last_log, not log
Images of the problem
Results of the emmc test
Errors in CWM 5.0.2.0
Errors in CWM 3.0.0.8
last_log is present in /cache/recovery
Have you wiped the cache partition from recovery and then flash cwm recovery from hboot as a PB31IMG.zip?
How exactly do I go about doing that? I know how to wipe the cache, but do I just rename the CWM zip to PB31IMG.zip and flash it?
Rixanu said:
How exactly do I go about doing that? I know how to wipe the cache, but do I just rename the CWM zip to PB31IMG.zip and flash it?
Click to expand...
Click to collapse
Um not sure what file you have but here is one for you http://dinc.does-it.net/PB31IMG.zip, just place it on the root of your sdcard and boot into hboot. It will find the file after a couple secs and prompt to press vol up to install. This is version 5.0.1.0
Also you may want to run fix permisions from the advanced menu in recovery.
You are quite the lifesaver, it worked like a charm! One more question, though. I would like to upgrade CWM to 5.0.2.0 if possible. Would it be safe to flash it through terminal emulator/adb, or should I just update through hboot from now on? Thanks so much for your help!
Rixanu said:
You are quite the lifesaver, it worked like a charm! One more question, though. I would like to upgrade CWM to 5.0.2.0 if possible. Would it be safe to flash it through terminal emulator/adb, or should I just update through hboot from now on? Thanks so much for your help!
Click to expand...
Click to collapse
No problem. Hboot is the best way to do it. I dont have a 5.0.2.0 file at the moment but if you need one i can get it for you.
Edit: you could also update it thru rom manager and if for some reason it messes something up just flash the one from earlier post again.
That's alright, I found one a few minutes ago, just in case. This also seems to have fixed my wifi issue, so this is about the best case scenario I can picture. Thanks again!
Your welcome.
I guess all is not as it seems. The problem in CWM started popping up again just a few minutes ago. On top of that, when I rebooted, I got caught in a bootloop. I managed to boot up fine after a battery pull, but this is really starting to scare me. Does anyone have any advice?
PS. I'm posting here because I feel this doesn't need a whole new topic. If that would be better, just let me know.
Rixanu said:
I guess all is not as it seems. The problem in CWM started popping up again just a few minutes ago. On top of that, when I rebooted, I got caught in a bootloop. I managed to boot up fine after a battery pull, but this is really starting to scare me. Does anyone have any advice?
PS. I'm posting here because I feel this doesn't need a whole new topic. If that would be better, just let me know.
Click to expand...
Click to collapse
I would revert back to CWM 3.0.0.8 thru rom manager for awile and see if the problem still persists. However once you do make sure to make a new nandroid as i dont believe cwm 5 backups are compatible with version 3.
Rom manager didn't work (again), so I flashed through hboot and it worked fine. Errors are gone, and no more bootloops since last night. I'm gonna wipe and reflash Cyanogen later today because my wifi is all buggy again and I feel as if a clean install may hopefully kill any latent symptoms. Feel free to let me know it that's a bad idea, haha. Thanks again.
need to exchange the phone, so i need to revert the phone back to fully stock. phone currently has cyanogenmod 7. just want to make sure i'm doing this right...
so as i understand it, following the g2\desire z wiki, i can just use clockword mod recovery to install the stock image and flash it with CWM right, via the "flash alternate recovery" option?
and more importantly, the wiki says that to install the stock rom, i need to make sure my main version is not higher than 1.19.531.1, but i was not able to find my version. i booted into hboot, which number is that? and regardless, if i use misc_version to set the main version, does it matter what version i have? also, i used gfree to root before, and still have the original partition 7 saved on my pc, if that matters. thanks
Here follow my guide, it describes how to return to stock. Only change you might want to make is use a proper stock rom to flash instead of my modded ones.
-Nipqer
thanks! how do you flash stock recovery???
i did fastboot recovery recovery.img and it said:
"sending 'recovery' (4652 KB)... OKAY [1.021 S]
writing 'recovery'... FAILED <remote: not allowed>
finished. total time : 1.031s
Fastboot flash recovery only works on eng hboots or htcdev unlocked hboots.
-Nipqer
Sent from my HTC Vision using xda premium
so then what can i do? thanks again
Use the xda wiki to get full root. That will give you recovery in the process
-Nipqer
Sent from my HTC Vision using xda premium
Similar-sounding problem
I've attempted to install ClockworkMod and CM7 on my G2 with Gingerbread 2.3.4, and have wound up putting it in a semi-bricked state. (Whole process went fine on my old G2 last year, but had to return that due to a wifi problem). Here's what I've done so far:
1. Started the root/CW process (http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Rooting). Once I got to the psneuter step, I got "Failed to set prot mask (innappropriate ioctl for device)", which I figured meant I needed to do the downgrade, since that was the only difference I could see between my new G2 and the old one (which had Froyo when I went through this process).
2. Downgraded to Froyo (http://wiki.cyanogenmod.com/wiki/HTC_Desire_Z:_Firmware_Downgrade_(Froyo). That seemed to go just fine.
3. Re-did the root/CW process. That also seemed to go just fine, until I rebooted into CW, at which point I got:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
At this point, attempting to select any of the items in the CW menu just showed the hat-with-ring logo, no text. I figured I must have screwed something up, and decided I'd best roll back to stock (I'd just done that on my old G2, so I could send it in, and that process had also worked fine).
4. Rolled back to the original PC10IMG.zip (http://theunlockr.com/2010/12/01/how-to-unroot-the-t-mobile-g2-htc-vision/ but without the OTA part). When I rebooted, I got the green-on-white "HTC" screen, for at least 10 minutes. Retried several times. Using power-volumedown, I could still get into recovery, which was still Clockwork, but with the same errors as in step 3. I could still connect via ADB (when in Clockwork) and get a root shell with that, at this point.
5. Big goof: I decided I should rollback to stock recovery. Did that using the http://forum.xda-developers.com/showthread.php?t=834545 guide. Rebooted. Phone still sticks at the initial HTC screen, forever. Using power-volumedown, I can get to the screen whose name I do not know, the one that's white with three skateboarding androids at the bottom, and the "Fastboot, Recovery, Factory Reset, Simlock, System Info, Image CRC" menu.
6. Recovery now takes me to what I presume is stock recovery, which has a "E:Can't mount /cache/recovery/command" message at the bottom of the screen. Menu is "Reboot system now, Apply sdcard:update.zip, Wipe data/factory reset, Wipe cache partition." Factory reset and wiping the cache partition, then rebooting, still results in the eternal HTC screen.
7. If I do reboot and do power-volumedown to get back to the three-skateboards screen (someone please tell me the actual name, so that I can sound like less of an idiot), I can select fastboot, and then connect via fastboot-windows. I haven't done anything with that yet, however, as I figured I've gone too far already without stopping to ask for help, and don't want to cut myself from off from fastboot the way I cut myself off from adb.
Right now, I just want to get the phone to a usable state again. Not expecting any hand-holding, but I'd appreciating someone pointing me to the start of the path back.
...the three skateboards screen is called bootloader
is it still s-off and what hboot-number does it show?
At the top of the bootloader (thanks!) screen, I get:
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1010000)
MICROP-0425
RADIO-26.01.00.17_M2
eMMC-boot
Sep 8 2010, 15:56:38
ok, this looks good.
first i would flash a recovery.img through fastboot (you do have eng hboot so it should work)
download the 3.0.2.4 image from here and put it into your platform tool folder:
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
then connect your phone to pc go to your platform tool folder and type:
"fastboot flash recovery recovery.img"
enter recovery and wipe data&cache&dalvik cache afterwards flash a new rom...
if you get the same error as before, have a look here:
http://forum.xda-developers.com/showthread.php?t=1448441
Thanks immensely. Going to try this in the morning (hitting 2am for me). Just one final question: at the "flash a new ROM" step, should that be the stock T-Mobile ROM, or does it matter? My original intent was to install CM, so if it makes no difference I'll go with that, but right now I'd be happy just to have a phone that boots, so if I need to I'll use stock and count my blessings.
emamid said:
Thanks immensely. Going to try this in the morning (hitting 2am for me). Just one final question: at the "flash a new ROM" step, should that be the stock T-Mobile ROM, or does it matter? My original intent was to install CM, so if it makes no difference I'll go with that, but right now I'd be happy just to have a phone that boots, so if I need to I'll use stock and count my blessings.
Click to expand...
Click to collapse
no do not flash a stock rom (you will get in troubles doing this with a rooted phone and s-off)... cm7 is a good way to go
if you don´t mind pls hit the thanks button
damnit... now i can't seem to downgrade the new phone, with the 1.22 firmware. following the cyanogenmod wiki, at the step where you enter:
Code:
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
adb shell
i get a whole bunch of:
Code:
An error occurred while running the exploit (-1) (errno: 25)
Scanning region fffe0000...
An error occurred while running the exploit (-1) (errno: 25)
adb shell
adb: permission denied
$
help, what am i doing wrong?
first of all you do have gingerbread (2.3+)? because you asked this in a different thread...
and you did chmod it as described in the guide?
hoffmas said:
first of all you do have gingerbread (2.3+)? because you asked this in a different thread...
and you did chmod it as described in the guide?
Click to expand...
Click to collapse
nope, it's android version 2.2, but the build number is 1.22.531.8, so that means i have to downgrade it, right?
you need a different guide for a froyo downgrade - try this guide:
http://forum.xda-developers.com/showthread.php?t=905261
i´m not sure if it works... other thing you could do is make a official update to gingerbread and then downgrade with the guide you used before.
hoffmas said:
if you don´t mind pls hit the thanks button
Click to expand...
Click to collapse
Weird, I had to open the page in Firefox rather than Chrome for the "Thanks" button to show up.
---------- Post added at 03:03 PM ---------- Previous post was at 02:43 PM ----------
hoffmas said:
ok, this looks good.
first i would flash a recovery.img through fastboot (you do have eng hboot so it should work)
download the 3.0.2.4 image from here and put it into your platform tool folder:
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
then connect your phone to pc go to your platform tool folder and type:
"fastboot flash recovery recovery.img"
enter recovery and wipe data&cache&dalvik cache afterwards flash a new rom...
if you get the same error as before, have a look here:
http://forum.xda-developers.com/showthread.php?t=1448441
Click to expand...
Click to collapse
Installed clockwork, and can get to it through the bootloader. However, when I try to wipe the cache -- or select any of the other menu items -- I just get the hat-and-ring logo, with nothing else. Power button takes me back to the CW menu again. No error messages at any stage, but nothing happens either.
Should I proceed with the steps in the second link you pointed to? Or does this sound like a different problem?
Hm don't know... Maybe try to find out if your cache is corrupted or your emmc chip. So yes follow the link i posted, but before you do the same as the op there (means using your sdcard instead of emmc) try everything else... (i think nipqer posted a link there related to corrupted cache...)
Sent from my HTC Vision using XDA App
Thankfully, I didn't have to go through hardly any of the contortions CollegeBound had to in that thread. Installing 4EXT was enough -- it was able to get past the "E:Can't mount /cache/..." errors (which started again when I used fastboot to erase the cache), whereas Clockwork was stymied by them. Did an update using a CM ROM, and everything seems fine.
Thanks again for your help. I don't think T-Mobile would have let me RMA two phones in two weeks.
Hello,
i just unlocked bootloader and installed twrp and it all went fine..
until i wanted to fully wipe my device, i did this via twrp.
after 20Minuts, nothing happend, the bar was still white and gray (not even a little bit blue)
and it kept stuck on ''twrp formatting data using make_ext4fs function''.
i knew this wasn't a good idea, but i decided to turn off my phone,
and now, everytime when i turn it on on the normal way it just redirrects me to TeamWin in a bootloop.
even if i want to go to recovery mode i keep stuck in that bootloop, so there is nothing i can do right now, i only can stick at Fastboot Mode but nothing else,
Is there any way to fix this problem?
Using ASUS ZENFONE 2 551ML
I hope you did a backup of your system before? Otherwise just download the latest full image:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.174-user.zip
place it on your internal sdcard (via adb push) and then flash it normally with TWRP. Please note that the procedure can take up to 30 minutes, where the formatting is the procedure taking the longest time...
TheSSJ said:
I hope you did a backup of your system before? Otherwise just download the latest full image:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.20.40.174-user.zip
place it on your internal sdcard (via adb push) and then flash it normally with TWRP. Please note that the procedure can take up to 30 minutes, where the formatting is the procedure taking the longest time...
Click to expand...
Click to collapse
How to he flash stock rom by twrp?
Download and flash this via twrp http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526
Make sure you flash Supersu before you flash the rom.
mr_gourav2000 said:
How to he flash stock rom by twrp?
Click to expand...
Click to collapse
It's all written there...adb push on the phone, flash the zip normally via twrp, wait and done
TheSSJ said:
It's all written there...adb push on the phone, flash the zip normally via twrp, wait and done
Click to expand...
Click to collapse
but i cant use twrp on my phone because its stuck in bootloop, or what do you mean? (english not my main language)
please give me some proper step by step instructions, i would really apreciate that!
thanks anyway your awesome!
Man, I misread your post, sorry...I thought you could boot only into twrp
If you still have fastboot, why not flashing twrp 2.8.x.x?
Code:
Fastboot flash recovery nameofrecovery.img
Fastboot reboot recovery
Otherwise you could flash stock system with this guide: http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
It's a lot to read
wow, that is something really helpfull, there is still hope to revive my phone
i'll let you know how it turnt out xd
thanks alot!!
i fixed recovery mode, so thats already one step further. Oefff @TheSSJ thanks for the help.
But now i get some other problems, when i try to wipe my phone i get the error like ''unable to mount /data'' and ''unable to wipe dalvik''
and all other kinds of these errors, i get the same problem when i was installing rom. isn't there anything or a way to fully wipe all this **** so i can install a fresh rom.
i flashed custom rom and this is error log i get. its all full written down.
E: could not mount /data and unable to find crypto footer.
E: unable to mount /data
E: unable to recreate /data/media folder.
updating partition details...
E: unable to mount /data
... done
E: unable to mount storage.
E: unable to mount /data/media during GUI startup
Full SELinux support is present.
E: unable to mount /data/media/twrp. twrps when trying to read settings file.
E:unable to mount /data
MTP enabled
E: unable to mount /data
E: unable to mount /data
E: unable to mount /data
Installing external_sd/UL-Z00A-WW-2.20.40.174-user.zip ...
Checking for MD5 file...
Skipping MD5 check: no MD5 File found
Device image SKU:
OTA image SKU: WW
assert failed: getprop ("ro.build.asus.sku") == ''WW''
E: Error executing updater binary in zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Error flashing zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Updating Partition Details...
E:unable to mount /data
... done
E: unable to mount storage.
Failed
Seems you don't have a WW image installed, do you have a CN Software? Then you need another Software of course
what do you mean with ww & cn software?
sorry but im new in this.. but im really interested so can you please explain a little bit?
how can i get this other software! thanks!!!
Where did you buy your Phone? what does the packaging state? WW, CN, TW, etc? These 2 letters must be written in uppercase somewhere, then we will know which software to flash, there is a check where your phone's software is compared to the zip you are trying to flash:
assert failed: getprop ("ro.build.asus.sku") == ''WW''
Which TWRP did you flash?
ohhh yes, i do have CN software Probably, as it is buyed from china.
Where can i find this other type software?
thanks!
colldor200 said:
ohhh yes, i do have CN software Probably, as it is buyed from china.
Where can i find this other type software?
thanks!
Click to expand...
Click to collapse
There you go: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-CN-2.20.40.159-user.zip
I think flashing will still fail though...but pls try first,maybe it'll work
i tryed it, i get the same error :/
Update: i changed from CN to WW.
Because of this i reflashed to twrp 3.0 and it works properly and now wiping shows no problem anymore.
I also got the WW ota zip but dont know how to install that.
Anyway, i tryed to install xaosp rom (even if my ota is still CN)
And it showed no problems at all!
BUT when i tryed to startup my phone it sticks with the asus logo and wont go any further, not a bootloop, it just sticks at the asus logo.
We are Always getting more and more steps further into fixing my phone, thanks for that @TheSSJ were almost there ?
colldor200 said:
Update: i changed from CN to WW.
Because of this i reflashed to twrp 3.0 and it works properly and now wiping shows no problem anymore.
I also got the WW ota zip but dont know how to install that.
Anyway, i tryed to install xaosp rom (even if my ota is still CN)
And it showed no problems at all!
BUT when i tryed to startup my phone it sticks with the asus logo and wont go any further, not a bootloop, it just sticks at the asus logo.
We are Always getting more and more steps further into fixing my phone, thanks for that @TheSSJ were almost there
Click to expand...
Click to collapse
You could try flashing cm13 first and then xosp:
First wipe data/cache
Then flash cm13
Boot up and hope that it works
Reboot to recovery
Wipe data/cache
Flash xosp and maybe a kernel that fits (FlareM?)
Boot to system again
You could try flashing cm13 first and then xosp:
First wipe data/cache
Then flash cm13
Boot up and hope that it works
Reboot to recovery
Wipe data/cache
Flash xosp and maybe a kernel that fits (FlareM?)
Boot to system again
Click to expand...
Click to collapse
sorry for the kinda late answer, but yes i followed your instructions, and it works completely, after cm13 i also immediately installed gapps.
i skipped xaosp im fine with cm13
Thanks alot @TheSSJ for all the help my phone is fully fixed now and even working faster then before its like super fast.
thanks again your great!