Related
Hi guys, I've had my Desire rooted for around 2 months and have used loads of
ROMs/Mods etc. It's fair to say I know the procedure. At the moment though I'm
puzzled and worried because I have lost my previous ROM and can't get a new one
on!
I was flashing a new version of Pinky Desire over the previous one (without wiping)
and it never got to the reboot screen. So I took out the battery and put it back in
to reboot it. It got to the custom boot screen and no further so I then booted into
recovery and wiped data and cache and re-flashed the ROM, but the result was
the same...
So I tried this a couple more times until suddenly the recovery-windows.bat file
would no longer put me into a recovery menu. I've tried everything I can think of
(using my original Goldcard etc) but nothing is fixing it- it's like I've lost root access.
How can I make my phone useable again? PLEASE HELP!!!
EDIT: In case it makes a difference I did delete what I thought were some old .zips from my SD shortly before this.
Install an official RUU, then re-root it? I guess some of the pro's got some better answers though
Download the ClockworkMod recovery, rename it in update.zip, put it in the sd, enter recovery, when you get the red triangle press vol up+power, select to flash update.zip.
Yep, flash an ruu, then re-root, only this time use unrEVOked and for future when flashing roms use the newer recoveries like clockworkmod or amonra.
The old recoverywindows.bat file leaves you at risk of the usb brick. You may well already have that now if you pulled the battery mid flash.
Thanks all. Haven't had a chance to do this yet but will. I did manage to flash an update.zip but it won't detect the sd. will try with clockwork mod.
DomFel said:
Download the ClockworkMod recovery, rename it in update.zip, put it in the sd, enter recovery, when you get the red triangle press vol up+power, select to flash update.zip.
Click to expand...
Click to collapse
Tried this but all I'm getting is cannot find directory. It retries about 12 times then
reboots. Just won't work.
When trying to flash an RUU it comes up with 'Error 170: USB connection error'.
This is weird because the device's bootloader recognises that there's a usb
connection. Any ideas?
EDIT: Seems like the phone in it's current state simply can't mount an sd card.
Gotta try some alternative methods for getting the RUU to run...
Doogleman said:
When trying to flash an RUU it comes up with 'Error 170: USB connection error'.
This is weird because the device's bootloader recognises that there's a usb
connection. Any ideas?
EDIT: Seems like the phone in it's current state simply can't mount an sd card.
Gotta try some alternative methods for getting the RUU to run...
Click to expand...
Click to collapse
Check out the USB brick thread.
prove said:
Check out the USB brick thread.
Click to expand...
Click to collapse
I will. That's so sh*t though
Thanks guys
Had almost same problem.
I even couldn't flash update.zip
the problem was in SD. it was working OK in windows, but phone couldn't mount it. soved problem with reformating using SDFormater, when formated with clockworkmod.
mendozinas said:
Had almost same problem.
I even couldn't flash update.zip
the problem was in SD. it was working OK in windows, but phone couldn't mount it. soved problem with reformating using SDFormater, when formated with clockworkmod.
Click to expand...
Click to collapse
I've two SDs and neither is working though so...
two things
the windows unlockerthing.bat was only supposed to be run one time, after that you could access the menu pressing vol up and power...
Why would you pull the batt on a Flash??
Pulled the battery because the device said flash completed but didn't do anything for over 5 mins. Won't make that mistake again. I've actually bricked the USB so this thread is a little pointless now
Oh and I did fix the SD issue
Hi there!
Got kind of a strange Problem with my Nexus:
I had big troubles last weak after i fully the battery by accident. I was stuck in a bootloop, so first thing i tried was a factory reset and restoring a nandroid backup. Didn't work, it randomly rebooted while restoring the backup. Same with a aokp rom i still had on my sd card.
Fastboot flashing didn't work either, i always got a "too many links" error.
It wasn't the usb cable, because i tried three, and it wasn't the pc, the drivers or the usb ports, cause i tried 3 different pcs, too.
At first i thought maybe the internal sd was corrupted somehow, but that didnt really make sense.
As a last resort i switched too odin, always hated it, didn't use it since the galaxy s first came out.
Guess what: It didn't work! It just got stuck at "sending data" or something like that while trying to flash a stock 4.2 rom.
What finally did the trick was:
After i ****ed up the whole device with odin and got the "phone exclamation mark pc" screen after turning it on, i tried flashing the attached zip with odin to get at least my recovery back, which worked after some tries.
After that i flash the slim rom via adb sideload and my nexus came to life again. Which didn't make sense at all, but i was happy.
UNTIL NOW:
I wanted to re calibrate my battery so i fully discharged the phone. And guess what: Same **** all over again.
I just can't get my head around it. It doesn't make sense at all, for me at least. It has to be some kind of hardware failure, but what?
Is there something like the bios battery on pc motherboards which is broken on my device? But flash storage doesn't need any current to save data, so....
I'm no Linux programmer but i'm no rookie either, so i don't think i commited any severe mistakes while trying to fix it. (well, despite odin being a failure in itself )
So, any ideas? I searched the forums a bit, but i didn't find anything similar, just the usual bootloop stuff.
You should never fully deplete a battery. Batteries have their own OS, which allows them to recalibrate themselves. When the system asks you for juice, give it to him.
a maguro wrote this.
I didn't do a full discharged, sorry for being unclear. I just used it until it turned off (5%), nothing more.
Edit:
Ok, i guess it is a real brick now. When i try flashing a rom via sideload, it gets stuck at "formatting data" and reboots after a while. flashing with odin doesn't work either.
Guess i got a bit closer to the core of the problem.
it seems like i have no /data partition on the sd card.
Rom flashing always gets stuck at formatting data. when i try to adb push a file to /data or data/media, it says "no such file or directory found".
When i try to unmount /data in cwm, nothing happens.
Any ideas?
Try adb pushing to /mnt/sdcard/ or /sdcard/ directly.. I remember an issue when i could not use adb with the data folder at all, unless i ran insecure adb from the android os.
or even /mnt/shell/emulated/0/
bodh said:
Try adb pushing to /mnt/sdcard/
Click to expand...
Click to collapse
Thanks, that worked. But still, i can't access the sd card via cwm, so that didn't really help. it says "couldnt open directory"
flashing with sideload still crashes at "Format and Mount System, Mount Data"
Why doesn't it create /system and /data?
Edit:
CWM Log says:
Can't partition non-vfat: datamedia
Why aren't you using fastboot?
bodh said:
Why aren't you using fastboot?
Click to expand...
Click to collapse
HansBaer2000 said:
Fastboot flashing didn't work either, i always got a "too many links" error.
Click to expand...
Click to collapse
That happens when i try to flash system
Seems that just my /data/media folder is gone, at least thats what TWRP tells me
Any way to bring it back? Or are my partitions corrupted?
I guess I missed that. Too bad there's not a manual of common fast boot errors and their causes. I read that the 'too many links error' often relates to bad drivers. I'd try universal naked drivers. Uninstall your current ones, then install. Make sure you're running fast boot as admin. Fast boot erase cache and fast boot format..also, perhaps your data/media got nested by subsequent flashes?
I don't think a low battery should cause any problems to the storage, however if you really have problems with partitions, perhaps try to flash odin with PIT file? (http://forum.xda-developers.com/showthread.php?t=1405327)
bodh said:
I guess I missed that. Too bad there's not a manual of common fast boot errors and their causes. I read that the 'too many links error' often relates to bad drivers. I'd try universal naked drivers. Uninstall your current ones, then install. Make sure you're running fast boot as admin. Fast boot erase cache and fast boot format..also, perhaps your data/media got nested by subsequent flashes?
Click to expand...
Click to collapse
Have tried both, the Samsung usb and the naked drivers before. Maybe i'll try a 4th PC and a 4th cable.
My Gnexi said:
I don't think a low battery should cause any problems to the storage, however if you really have problems with partitions, perhaps try to flash odin with PIT file? (http://forum.xda-developers.com/showthread.php?t=1405327)
Click to expand...
Click to collapse
Tried that multiple times. Flashing a PIT file only works, it repartitions just fine. Flashing a stock rom however always stops at "write NAND"
Are you using USB 2 ports? Try USB 3?
a maguro wrote this.
i would try, but my usb 3 doesn't recognize the phone in fastboot or adb mode, can't say why
After a update for better compatibility for 3rd party app, my Zenfone wont get past the ASUS screen at all.
Im also stuck at the asus load screen. I played around with the permissions of the sd card, after rebooting its stuck. Guys how to unbrick?
bratski said:
Im also stuck at the asus load screen. I played around with the permissions of the sd card, after rebooting its stuck. Guys how to unbrick?
Click to expand...
Click to collapse
you may want to flash your phone back. so this consist of
1) read up how to access to Temp CWM
2) download and transfer the full rom to your SD card
3) do a wipe all partition and go to advanced setting, wipe cache
4) install zip and choose from external SD, point to that .zip file for the full rom and apply.
5) installation may take 10min or so do not switch it off. after installation you are good as new.
I believe this should solve your problem, normal if things get bricked is due to config file error could be [syntax, corrupted, missing, setting].
Flashing should solve mostly of it unless the file that you previously accessed require root and cwm does not give permission to the file. that is a permanent bricking.
As always, newbie should not try tweaking permission required files, you end up having bricking the device as there might be no solution to recover it due to access rights. ALWAYS have a back up file so you can at least copy the file back and chmod it.
jerk48 said:
After a update for better compatibility for 3rd party app, my Zenfone wont get past the ASUS screen at all.
Click to expand...
Click to collapse
by asus screen, did you mean the ASUS Setup Wizard?
sooty84 said:
you may want to flash your phone back. so this consist of
1) read up how to access to Temp CWM
2) download and transfer the full rom to your SD card
3) do a wipe all partition and go to advanced setting, wipe cache
4) install zip and choose from external SD, point to that .zip file for the full rom and apply.
5) installation may take 10min or so do not switch it off. after installation you are good as new.
I believe this should solve your problem, normal if things get bricked is due to config file error could be [syntax, corrupted, missing, setting].
Flashing should solve mostly of it unless the file that you previously accessed require root and cwm does not give permission to the file. that is a permanent bricking.
As always, newbie should not try tweaking permission required files, you end up having bricking the device as there might be no solution to recover it due to access rights. ALWAYS have a back up file so you can at least copy the file back and chmod it.
Click to expand...
Click to collapse
my problem right now is my pc wont detect my phone. Ive already installed the drivers.
Same thing happened to me when I tried flashing the OTA update with my phone being rooted. You have get into recovery mode on the phone and then use ADB to put the original image back to the device to get it back to stock so it will reboot. It worked for me
sooty84 said:
you may want to flash your phone back. so this consist of
1) read up how to access to Temp CWM
2) download and transfer the full rom to your SD card
3) do a wipe all partition and go to advanced setting, wipe cache
4) install zip and choose from external SD, point to that .zip file for the full rom and apply.
5) installation may take 10min or so do not switch it off. after installation you are good as new.
I believe this should solve your problem, normal if things get bricked is due to config file error could be [syntax, corrupted, missing, setting].
Flashing should solve mostly of it unless the file that you previously accessed require root and cwm does not give permission to the file. that is a permanent bricking.
As always, newbie should not try tweaking permission required files, you end up having bricking the device as there might be no solution to recover it due to access rights. ALWAYS have a back up file so you can at least copy the file back and chmod it.
Click to expand...
Click to collapse
downshift00 said:
Same thing happened to me when I tried flashing the OTA update with my phone being rooted. You have get into recovery mode on the phone and then use ADB to put the original image back to the device to get it back to stock so it will reboot. It worked for me
Click to expand...
Click to collapse
where do i get the stock image?
bratski said:
where do i get the stock image?
Click to expand...
Click to collapse
here is the stock firmware.
https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
its fine if your phone does not talk to your PC now. copy the firmware to your SD card via other means. [card reader etc]
then try my method of flashing it back to original state, you stated that adb dont work, have you tried the temp CWM method yet?
the main goal is to wipe dalvik cache under advanced menu in CWM, and cache partition and all hard reset.
then you flash back your original file.
hope it works for you.
sooty84 said:
here is the stock firmware.
https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
its fine if your phone does not talk to your PC now. copy the firmware to your SD card via other means. [card reader etc]
then try my method of flashing it back to original state, you stated that adb dont work, have you tried the temp CWM method yet?
the main goal is to wipe dalvik cache under advanced menu in CWM, and cache partition and all hard reset.
then you flash back your original file.
hope it works for you.
Click to expand...
Click to collapse
ive read about the temp cmw method and i cant figure out how to go about it. it says on the instruction that you need to turn on phone before running the cai_dat_CWM. how am i going to do this as my phone will only boot to the asus logo? thanks
just figured it out. I need to boot in fastboot so the phone will get recognized. However, the latest build available on the asus website is still 2.17.40.12. I already have the 2.18.40.12 version. The 2.17 firmware can't overwrite the newer build in temp CWM recovery. Anybody knows where i can download the full rom? Z00A-WW-2.18.40.12?
bratski said:
just figured it out. I need to boot in fastboot so the phone will get recognized. However, the latest build available on the asus website is still 2.17.40.12. I already have the 2.18.40.12 version. The 2.17 firmware can't overwrite the newer build in temp CWM recovery. Anybody knows where i can download the full rom? Z00A-WW-2.18.40.12?
Click to expand...
Click to collapse
I GOT THE SAME PROBLEM.
dunno what to do anymore.
sigh...
help me please
Ninjakura said:
I GOT THE SAME PROBLEM.
dunno what to do anymore.
sigh...
help me please
Click to expand...
Click to collapse
here is the link for stock but pre-rooted img for latest 2.18.40.12 firmware,,make sure to download Z00A firmware if you have ZE551ML device.. and if I was not mistaken, you may choose to FULL UNROOT in SuperSU apps to go back to stock rom..
cangcan said:
here is the link for stock but pre-rooted img for latest 2.18.40.12 firmware,,make sure to download Z00A firmware if you have ZE551ML device.. and if I was not mistaken, you may choose to FULL UNROOT in SuperSU apps to go back to stock rom..
Click to expand...
Click to collapse
thanks. problem solved after i followed instructions from this thread, http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
bratski said:
my problem right now is my pc wont detect my phone. Ive already installed the drivers.
Click to expand...
Click to collapse
me too, any idea on how to fix it?
sooty84 said:
you may want to flash your phone back. so this consist of
1) read up how to access to Temp CWM
2) download and transfer the full rom to your SD card
3) do a wipe all partition and go to advanced setting, wipe cache
4) install zip and choose from external SD, point to that .zip file for the full rom and apply.
5) installation may take 10min or so do not switch it off. after installation you are good as new.
I believe this should solve your problem, normal if things get bricked is due to config file error could be [syntax, corrupted, missing, setting].
Flashing should solve mostly of it unless the file that you previously accessed require root and cwm does not give permission to the file. that is a permanent bricking.
As always, newbie should not try tweaking permission required files, you end up having bricking the device as there might be no solution to recover it due to access rights. ALWAYS have a back up file so you can at least copy the file back and chmod it.
Click to expand...
Click to collapse
I have same prolem as OP's got.
I've got stuck on Asus Loading screen after install OTA update on rooted device.
I'm gonna try your method.
Thanks
downshift00 said:
Same thing happened to me when I tried flashing the OTA update with my phone being rooted. You have get into recovery mode on the phone and then use ADB to put the original image back to the device to get it back to stock so it will reboot. It worked for me
Click to expand...
Click to collapse
how did u do that? can u give me step by step instruction please?
ty
Did anyone able to fix this problem (stuck at Asus logo and not able to get to recovery mode or connect to the computer)? Thanks!
SAN_MARINO said:
Did anyone able to fix this problem (stuck at Asus logo and not able to get to recovery mode or connect to the computer)? Thanks!
Click to expand...
Click to collapse
Press Power+Volume Up key, After vibration leave Power Button then choose Recovery Mode using Volume keys, if sleeping Android screen appear at Recovery with Error message, Press Volume Up and Power and leave immediately Power Key, it will show you the Recovery Menu, then Reset your device, it will solve your problem.
If I am helped you, Press Thanks button.
k576 said:
Press Power+Volume Up key, After vibration leave Power Button then choose Recovery Mode using Volume keys, if sleeping Android screen appear at Recovery with Error message, Press Volume Up and Power and leave immediately Power Key, it will show you the Recovery Menu, then Reset your device, it will solve your problem.
If I am helped you, Press Thanks button.
Click to expand...
Click to collapse
Thanks!
I already tried it like 20 or more times. The ASUS logo still shown for like 10 seconds and died and came back again (ASUS logo). When I tried to connect it with my laptop, the computer won't recognize the device.
SAN_MARINO said:
Thanks!
I already tried it like 20 or more times. The ASUS logo still shown for like 10 seconds and died and came back again (ASUS logo). When I tried to connect it with my laptop, the computer won't recognize the device.
Click to expand...
Click to collapse
I will try to tell you step by step:
1. Press Power Button + Volume Button
You enter into Recovery Fastboot Option, then Choose Recovery menu using Volume Key (3 Option mostly shown)
then press Power Button (From Recovery Mode), it restart.
2. Then after Restart it shows you (Mostly) Sleeping Android Screen with Error text, then Press First Volume Up Button, and Press Power Button (Power button for a second or two then leave it, IF YOU PRESS MORE TIME, IT WILL RESTART THE PHONE).
3. You can now see the Recovery Menu with Normally appear in other phones also - Reset, Restart, Etc Option.
Hope you will now able to reset your phone...
----------------------------------------------------------
PRESS THANKS BUTTON IF I AM HELPED YOU
----------------------------------------------------------
IS the android recovery menu stored in the bootloader?
Does the bootloader corresponds to the file boot.img on SP FLASH TOOL?
I have an alcatel 7047 xpop c9 (with MT6582M processor) . It power on and automatically goes to android recovery menu and there is no way to let it exit from this mode or to power off because the battery is not removable.
It seems that the problem appeared during an upgrade, because the battery discharged during the process.
Today i tried to use SP FLASH TOOL version 5 in order to write the flash, included preloader, boot, recovery etc., by using a backup for this phone found on internet. After flashing everything i tried to reboot the phone but each time the same menu is shown.
Question: does the boot.img file overwrites the bootloader? How could I understand what is the problem? Could I enable some print or log, even remote logging, in order to better understand what is going wrong?
Yesterday i also tried the upgrade tool from alcatel website (it reloads all the original files but the result is the same).
EDIT: i was able to open the case, remove the battery and replug it, but the problem is still the same: Reconnecting the battery and powering the phone, it automatically goes in the recovery menu.
Wow
Wow, no reply. Is it there someone hereeeeeeeee?
gaucho1978 said:
IS the android recovery menu stored in the bootloader?
Does the bootloader corresponds to the file boot.img on SP FLASH TOOL?
I have an alcatel 7047 xpop c9 (with MT6582M processor) . It power on and automatically goes to android recovery menu and there is no way to let it exit from this mode or to power off because the battery is not removable.
It seems that the problem appeared during an upgrade, because the battery discharged during the process.
Today i tried to use SP FLASH TOOL version 5 in order to write the flash, included preloader, boot, recovery etc., by using a backup for this phone found on internet. After flashing everything i tried to reboot the phone but each time the same menu is shown.
Question: does the boot.img file overwrites the bootloader? How could I understand what is the problem? Could I enable some print or log, even remote logging, in order to better understand what is going wrong?
Yesterday i also tried the upgrade tool from alcatel website (it reloads all the original files but the result is the same).
EDIT: i was able to open the case, remove the battery and replug it, but the problem is still the same: Reconnecting the battery and powering the phone, it automatically goes in the recovery menu.
Click to expand...
Click to collapse
Just discovered your post. Have you solved the issue?
First of all, the recovery image is not stored in the bootloader...whatever you meant by that. It is stored in the recovery partition. The boot.img is NOT the bootloader. It is the kernel. And it is stored in the boot partition. Those questions simply sound like you are trying to figure out why your phone is booting into recovery. Even after you have restored the STOCK ROM using Alcatel's Mobile Upgrade S.
My first thought was that you have no system image or that your custpack partition is corrupted. But those issues would lead to a boot loop or you would just hang on the boot logo and not move forward. Plus you restored the stock ROM. So that's really strange that you're booting only into recovery each time.
However what is more likely is that you are not starting your phone correctly. I once had a lady with the exact same issue. Her phone developed this strange problem where it would only boot into recovery. Her phone was completely stock. She never did anything with her phone except use it like a non-techie would use their phone. She didn't even know what recovery meant. All she knew was this strange menu always appeared when she started her phone.
BUT, when I booted her phone...guess what? It booted up just fine! But with her, her phone would always boot into recovery. You know why? I watched her boot her phone. She had developed a new habit every time she started her phone of inadvertently applying pressure on the Volume UP button while she was turning on her phone...because it was on the opposite side of the phone from the power button.
It's really weird that the problem persists even after you flashed back to stock. If that's the case, my only other guess is that your motherboard is damaged, or perhaps it's not you who is holding down the vol+ button...maybe it's just stuck.
So, a little background. Full stock recovery, latest Telus 4.4.2 firmware.
Phone may have suffered a drop and/or some water damage during an episode of blackout drunkenness. Yes, I know, I'm an idiot.
Worked fine for a day or two, then began randomly shutting off, seemingly at times when the phone's CPU was under stress. Keeping it in airplane mode seemed to help avoid the reboots somewhat but not completely.
This began right before I was leaving for vacation, and had no time to go replace it. Then, after successfully taking a bunch of awesome pictures while on vacation, the phone decides to go into a boot loop. Can only boot into download mode.
I've got another phone now, but would REALLY like to get the data off the phone if at all possible. I'm assuming there must be some hardware issue at this point causing the boot loop, so I'm guessing that restoring the phone to 100% original working order is probably out of the question.
Any suggestions? I'm guessing something got corrupted, but I'm wondering if maybe I can flash a new recovery or re flash the stock rom via odin and hope it boots up long enough to get the data off? Will it wipe all my data if i try to flash via Odin? Should I take it in for a JTAG? are there other options like getting someone to dump the data off the memory chip somehow?
Thanks in advance.
Since the phone will enter download mode, I suggest flashing twrp 2.87 onto the phone, boot into recovery, mount the data partition, connect the phone to a computer, and try to copy the data to the computer.
Okay, where is a reputable source to download Odin, and what version should I use?
Also, can you provide a link to the exact instructions for flashing TWRP? I looked at the info available on their website and it's not that clear...
And so once I've booted into recovery and mounted the data partition, I leave the phone on, correct? Dont do anything, just connect it to the PC, and it should show up there?
Thanks so much for your help
audit13 said:
Since the phone will enter download mode, I suggest flashing twrp 2.87 onto the phone, boot into recovery, mount the data partition, connect the phone to a computer, and try to copy the data to the computer.
Click to expand...
Click to collapse
Okay, I was able to flash TWRP successfully and boot into it.
However, when I attempt to mount the data partition, it won't let me. When I go into the log files, it says unable to mount /data, unable to mount /system, unable to mount /cache, etc......
Also says Internal Storage 0mb ....
So.... i'm guessing this is really not good
Any further suggestions??
If it can't mount the partition and the size is 0, looks like the internal memory is shot.
The only other thing you could try would be to re-flash the stock ROM without wiping anything to see if it will boot. If it fails to flash via Odin, I don't there is much you can do.