Hi everybody,
I messed up a little my system.
One week ago I installed a B704 firmware, and today I tried to get back to B226.
The result is that now my phone won't boot, and I can't install any rom!
That's the story:
Following olav's guide (http://forum.xda-developers.com/showthread.php?t=2132043) I got back to B123 (IntermediatePack): At first I modified the file build.prop with the alternative method described in the FAQ. B123 installed successfully and booted.
Then, i copied B226's UPDATE.APP to sdcard and booted into recovery. I got a lot of errors "Unable to mount /cust"...
I didn't know what to do, I tried a couple of times, and then... I wiped a lot of things using TWRP! (good idea, isn't it? :/ )
As a result, now I cannot install anything.
When I flash the IntermediatePack and try to install B123, I get into "Android System Recovery 3e) and nothing happens!
Can anyone help me?
My phone is useless right now....:crying:
Another detail (I don't know if it's useful):
The phone was not rooted, I couldn't root it or even install Gapps.
Related
Hello all,
I'm sorry if this is the wrong place to post, but I thought I'd give it a try.
I own a Desire myself and the rooting / flashing a new ROM process was pretty easy so I thought I can help a friend out and put a custom ROM on his new Motorola Defy. Turns out I sucked at it. *ahem*
Right, the problem is as follows:
I got the brand new device, used SuperOneClick to root it, tried ROM Manager to install ClockworkMod CWM and it said Defy isnt supported in ROM Manager. So I google'd and it came up with this [german] (not allowed to post links), which basically gave me CWM.zip with an apk in it, which installed "System Recovery" and gave me the option to "Install System Recovery" and Reboot into Recovery - successfully bootet into CWM 2.5.1.8 , alright.
I did a nandroid backup and then wiped everything, selected the ROM on the sdcard to install MIUI 1.9.9 ROM, which worked fine. After it finished installing, I chose reboot system now.
Now what happens is:
I try to boot normally: I Only get the Motorola logo on screen and nothing ever happens
I boot into recovery like I used to know (Power + VolDown), I get a screen with a yellow exclamation mark and the android robot on it. Figured out that both volume keys take me to Android System Recovery Utility. I wiped everything again, that didn't help. I tried giving it the CWM.zip as an update.zip but it refuses that because it's apparently not properly signed. I can't do anything else in there. It also gives me a couple of errors "E: Can't moint CACHE:recovery/command" (/caller, /log)
Please, can anybody help me out? It seems I can't boot any ROM from it right now, nor do I know how to get CWM back in to at least even restore the nandroid backup (which I still have).
I would love to, at the end of the day, have a rooted device with CWM running and MIUI 1.9.9. If that doesn't work, at least can I restore the CWM backup somehow to have to stock ROM running?
I would really appreciate any help very much and realize I may be in over my head, it just seemed too easy on the Desire I previously used. Thanks a lot!
Hello! Im using HTC M8, yesterday i decided to root it so I used this guide to do bootloader activation, flashing recovery and rooting it (h t t p :/ / theunlockr.com/2014/04/19/root-htc-one-m8-all-in-one-toolkit-method-video/).
Everything was fine till i done everything and started my phone. I tried to run Supersu, and i got message that Supersu binary is not installed, i tryed to update it from googleplay, but nothing. Than i decided to flash updated version found on internet, now i get strange things like, x application failed to run , report this to HTC, my phone storage is not recognized or shown in any file menager or when i connect it to pc, i cant download anything from chrome, to my phone... Help please. What to do?
I tryed factory reset, reflashing recovery, but nothing happend. I have plan to instal newest version of super su but i cant put it in phone root to instal it from recovery boot...
Somebody?! Anything?
Hello everybody,
I have a serious problem. I did the update to lollipop, installed CWM und tried to root the system. Obviously, I did something wrong and now the system does not boot anymore. Booting delivers the Sony string on the screen, for ever and ever. At the moment, I can only use fastboot. Since I never had such a situation, I do not know how I can come to a booting system from this state. Could perhaps somebody give me a hint how to proceed? I tried Google, but problem is, that "recover fastboot" means I always come to sites telling me to install CWM, but they do not work at my bricked device..
In the hope for a helping advise,
Wumba
Support
which your model of compact Z1?
where d5503 download stock firmware sorry i not permission post link search google
install Flash Tools sorry i not permission post link search google
Paste "D5503_14.5.A.0.242_RU.ftf" in directory : C:/Flashtools/Firmware and rename paste firmware.old
open flash tools click lightning icon, select flash mode, copy and paste "D5503_14.5.A.0.242_RU.ftf" in desktop and select directory c:\desktop/"D5503_14.5.A.0.242_RU.ftf".. and flash ..... wait finish instalation :good:
WumbaHammerstein said:
Hello everybody,
I have a serious problem. I did the update to lollipop, installed CWM und tried to root the system. Obviously, I did something wrong and now the system does not boot anymore. Booting delivers the Sony string on the screen, for ever and ever. At the moment, I can only use fastboot. Since I never had such a situation, I do not know how I can come to a booting system from this state. Could perhaps somebody give me a hint how to proceed? I tried Google, but problem is, that "recover fastboot" means I always come to sites telling me to install CWM, but they do not work at my bricked device..
In the hope for a helping advise,
Wumba
Click to expand...
Click to collapse
yes I encountered same problem after installing 242 prerooted with prf method. Then I installed xposed and probably xprivacy module (not compatible still now with lollipop) caused the bootloop. I couldn't enter recovery, so no zip flash, only fastboot.
I had to start again from sratch . I flashed 108 kitkat firmware (easy to root), then with root I installed dual recovery. Then wipe all and flashed prerooted zip.
Hi XDA, many threads here have helped me in the past so time to ask another (probably stupid) question. It's a bit of a long story so I apologise in advance.
I've been running CM (one of the nightly builds from about 3 weeks back, don't have the file so I can't say which) on my phone for a while with no issues until a couple of nights ago when it was overheating (charging while playing a game, stupid I know) so I decided to turn it off so it could cool down without taking it off charge.
The following morning I turn it back on to find that it's getting to the blue android head logo of CM and getting stuck there. First thing I do is reboot into TWRP and flash my backup from right after I installed CM. Reboot and... same result. Okay, no biggie right? Time to reinstall CM (the latest nightly build from yesterday) and Google Apps (nano package) via TWRP and reboot again. Still stuck at the blue android head logo. The reinstall was handled after using the Wipe-Factory Reset function of TWRP, as the guide here explains.
At this point I decide to do a bit of research and learn that it's called a softbrick or bootloop and apparently flashing the stock rom can fix it. The LG software suite won't even recognise the device but a friend of mine found this guide so I attempted to run through it. All goes well until it comes time for the software to connect to the phone - I pop it in download mode while putting the USB cable in, the program says waiting for connection, runs for 14 seconds and says it's trying to put the phone into download mode, at this point it fails saying the phone can't be put into download mode.
Some of the comments beneath the article offer fixes like using USB 2.0 instead of 3.0, putting the program into compatability mode for Win7 and running in administrator mode. To be thorough I tried every USB port on my machine (both 2.0 and 3.0) and run the program in compatability mode (with and without admin mode) for several versions of windows. Same result every time.
Another friend then suggests that somehow permissions got borked and it might be worth reflashing SuperSU to the system but at this point I'm at a loss for how to do that. I have the one click root script that I got from god knows where (not this one because that didn't work for me) that has a SuperSU zip in it, presumably it flashes that to the phone when it runs (found this out the hard way because I've been a moron in the past and tried installing SuperSU through TWRP and broke the boot previously, fixed by re-running the one click root script - this was ages ago before even installing CM.)
So right now I can put the phone into download mode manually, get into TWRP and use all its functions as well as connect to my PC and use ADB functions while the phone's in TWRP but can't boot into CM or flash a stock rom. Any help would be appreciated, I've spent a whole day reading guides, asking friends and clumsily trying to fix this only to get nowhere.
Have u tried installing the stock via TWRP? Via zip ... Wipe cache delvik also..
jinderation said:
Have u tried installing the stock via TWRP? Via zip ... Wipe cache delvik also..
Click to expand...
Click to collapse
I haven't tried that, I didn't even know it was possible. Could you give me some more detailed pointers on how to do this? I noticed that the stock ROM I have cames as a .TOT file but CM is several files and folders in the zip. Will it install fine from that zipped up TOT file?
Thank you so much for your time.
When the rom is uploaded by the dev its also uploaded in .zip file place it ur system rom just go into twrp recovery flash the the zip file before flashing wipe cache n delvik too its easy as 1,2,3 search here on xda for ur compatible model
jinderation said:
When the rom is uploaded by the dev its also uploaded in .zip file place it ur system rom just go into twrp recovery flash the the zip file before flashing wipe cache n delvik too its easy as 1,2,3 search here on xda for ur compatible model
Click to expand...
Click to collapse
Thank you so much. I got it sorted. I really appreciate you taking the time to help me out with my stupidity.
My Zenfone 2 (ZE551ML 4GB) dilemma:
*•*I unlocked the bootloader with the official bootloader app
*•*I flashed the latest TWRP via adb. In the recovery screen, I saw an android showing error. That's when the panic started.
*•*I Then I rooted my phone with the one click Zenfone root application (available in XDA)
*•*I installed the official TWRP manager from the playstore and flashed with it. That also didn't solve my problem. Actually, a new problem set in. The phone started bootlooping IN RECOVERY.
*•*I rebooted the phone and then flashed an old version of TWRP for my phone. That solved the problem.
*•*Now, I wanted to flash Lineage OS in my phone. According to a YouTube tutorial, I copied my required files (the custom ROM and OpenGAPPS) to my Micro SD and then from twrp's advanced wipe, deleted everything except for Micro SD. I know that was an extremely stupid move but please bear with me.
*•*Deleting everything made things hundred times worse. It seemed impossible to get the phone into recovery mode again. But after a long time, I did.
*•*Now onto flashing the new ROM. I did a factory reset with twrp and then flashed the ROM and immediately got Error 7. By googling a bit, I found that the only way to solve this problem was by deleting the assert lines from the updater-script in meta/com/google/android inside the ROM.
*•* When I reflashed it, the process completed but it showed an error: (E:unknown command [log])
*•* Then I overlooked it again as a quick google said it didn't matter. Then I successfully flashed OpenGAPPS. I rebooted my phone and it kept bootlooping until it was back in the recovery screen. Weird right?
*•*I didn't seem to find any workaround so I decided to restore stock ROM. I downloaded it and flashed it. It succeeded. I rebooted my phone. And. .
*•*My phone now vibrates when I power on the phone and then it shows a black screen. It reboots automatically. I know it does as the phone vibrated periodically after the reboot
*•* I also can't go into the bootloader menu. My phone seems dead but I really need to revive it. I can't afford a new phone. Could you guys help me out please?
LethalHoe said:
My Zenfone 2 (ZE551ML 4GB) dilemma:
*•*I unlocked the bootloader with the official bootloader app
*•*I flashed the latest TWRP via adb. In the recovery screen, I saw an android showing error. That's when the panic started.
*•*I Then I rooted my phone with the one click Zenfone root application (available in XDA)
*•*I installed the official TWRP manager from the playstore and flashed with it. That also didn't solve my problem. Actually, a new problem set in. The phone started bootlooping IN RECOVERY.
*•*I rebooted the phone and then flashed an old version of TWRP for my phone. That solved the problem.
*•*Now, I wanted to flash Lineage OS in my phone. According to a YouTube tutorial, I copied my required files (the custom ROM and OpenGAPPS) to my Micro SD and then from twrp's advanced wipe, deleted everything except for Micro SD. I know that was an extremely stupid move but please bear with me.
*•*Deleting everything made things hundred times worse. It seemed impossible to get the phone into recovery mode again. But after a long time, I did.
*•*Now onto flashing the new ROM. I did a factory reset with twrp and then flashed the ROM and immediately got Error 7. By googling a bit, I found that the only way to solve this problem was by deleting the assert lines from the updater-script in meta/com/google/android inside the ROM.
*•* When I reflashed it, the process completed but it showed an error: (E:unknown command [log])
*•* Then I overlooked it again as a quick google said it didn't matter. Then I successfully flashed OpenGAPPS. I rebooted my phone and it kept bootlooping until it was back in the recovery screen. Weird right?
*•*I didn't seem to find any workaround so I decided to restore stock ROM. I downloaded it and flashed it. It succeeded. I rebooted my phone. And. .
*•*My phone now vibrates when I power on the phone and then it shows a black screen. It reboots automatically. I know it does as the phone vibrated periodically after the reboot
*•* I also can't go into the bootloader menu. My phone seems dead but I really need to revive it. I can't afford a new phone. Could you guys help me out please?
Click to expand...
Click to collapse
Did you flash the MM bootloader compatible TWRP mentioned in the OP for LineageOS? That solves error 7.
Ragarianok said:
Did you flash the MM bootloader compatible TWRP mentioned in the OP for LineageOS? That solves error 7.
Click to expand...
Click to collapse
I did not do that. I remembered all the steps but forgot that. That is the primary cause of my problem. Anyway to solve it?
LethalHoe said:
My Zenfone 2 (ZE551ML 4GB) dilemma:
*•*I unlocked the bootloader with the official bootloader app
*•*I flashed the latest TWRP via adb. In the recovery screen, I saw an android showing error. That's when the panic started.
*•*I Then I rooted my phone with the one click Zenfone root application (available in XDA)
*•*I installed the official TWRP manager from the playstore and flashed with it. That also didn't solve my problem. Actually, a new problem set in. The phone started bootlooping IN RECOVERY.
*•*I rebooted the phone and then flashed an old version of TWRP for my phone. That solved the problem.
*•*Now, I wanted to flash Lineage OS in my phone. According to a YouTube tutorial, I copied my required files (the custom ROM and OpenGAPPS) to my Micro SD and then from twrp's advanced wipe, deleted everything except for Micro SD. I know that was an extremely stupid move but please bear with me.
*•*Deleting everything made things hundred times worse. It seemed impossible to get the phone into recovery mode again. But after a long time, I did.
*•*Now onto flashing the new ROM. I did a factory reset with twrp and then flashed the ROM and immediately got Error 7. By googling a bit, I found that the only way to solve this problem was by deleting the assert lines from the updater-script in meta/com/google/android inside the ROM.
*•* When I reflashed it, the process completed but it showed an error: (E:unknown command [log])
*•* Then I overlooked it again as a quick google said it didn't matter. Then I successfully flashed OpenGAPPS. I rebooted my phone and it kept bootlooping until it was back in the recovery screen. Weird right?
*•*I didn't seem to find any workaround so I decided to restore stock ROM. I downloaded it and flashed it. It succeeded. I rebooted my phone. And. .
*•*My phone now vibrates when I power on the phone and then it shows a black screen. It reboots automatically. I know it does as the phone vibrated periodically after the reboot
*•* I also can't go into the bootloader menu. My phone seems dead but I really need to revive it. I can't afford a new phone. Could you guys help me out please?
Click to expand...
Click to collapse
xfstk is the only way. go to following thread and do as suggested. one advice when you get into bootloader. flash raw without AFT. that is best.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785