Hi guys, I have an issue with my Zenfone 2 (ZE551ML).
I flashed CyanogenMod 12.1 and everything was working fine. That is, until I decided I wanted to go back to stock ROM. That's when everything went wrong.
1) I went into recovery mode (using Power + Volume UP).
2) I wiped cache partition (probably my first mistake)
3) I restored to factory settings (possibly my second mistake)
4) After this I tried to flash the "recovery1.img" of the stock ROM I had.
5 ) That didn't work so I tried using ADB to flash different ".zip" files (all firmware downloaded from Asus website)
When that didn't work either, I abandoned and rebooted the phone. But it doesn't boot anymore.
It is stuck on the Asus screen and nothing happens.
Does anyone know if and how I can get out of this situation?
I must insist on the fact that I am only a novice. Until now I've only ever known iOS and have no knowledge whatsoever of how Android works.
I already posted my question here ("http://forum.xda-developers.com/general/xda-assist/possibly-softbricked-zenfone-2-t3248318") and was told I might want to try posting it here as well. I hope one of you can help me repair my mess !
Related
[FIXED]
Got some help on the forum;
downloaded asus firmware, unpacked blob, fastboot flash staging blob; fastboot reboot
Prime is now back to fully operational!
Many thanks to @kkdm
[/FIXED]
Hello,
I have looked around the various threads (including the 'how to unbrick your prime' one) but have not seen this issue mentioned.
I have a strange issue where if I factory reset (i.e. to Asus) the device will simply keep looping at the ASUS EEE logo, with device is unlocked in the top left hand corner. If however I install CM10 or another MOD, it seems to work as normal and boot into the homescren.
Having read around, there was an issue with an Asus update where it appeared to do something similar to this, is it perhaps that I am on that version and thus am getting the same error? Would a simple download and copy of the latest ASUS ROM fix that? I am unsure on how to do this exactly, but have read this was an issue, but I find it unlikely as everything was fine before I unlocked etc.
Is it perhaps the bootloader has become corrupt in some way with the ICS/JB difference? This is just a guess on my limit knowledge...
The reason for putting back the ASUS stock ROM is selling the device, having upgraded to the Infinity, and do not particularly want to send it with CM10 on.
Any help would be greatly appreciated,
What do you mean factory reset back to asus ?
You cannot just hit factory reset and it will go back to stock rom as you have overwritten it with cm10, or do you mean you have tried to install the stock version of the rom?
DO NOT use the official software from the Asus site, this can brick it.
There is a stock rom somewhere in the development section. You need to flash that to the tablet and you will be good to go.
edit... this is what you want .. http://forum.xda-developers.com/showthread.php?t=1708613
It turns out there is no ROM on the internal storage anymore (I must have selected the format option on my last attempt at installing Androwookie), as a result I cannot access the sdcard by plugging the thing into my PC.
Is there a way of installing this via the micro SD card slot?
flumpster said:
What do you mean factory reset back to asus ?
You cannot just hit factory reset and it will go back to stock rom as you have overwritten it with cm10, or do you mean you have tried to install the stock version of the rom?
DO NOT use the official software from the Asus site, this can brick it.
There is a stock rom somewhere in the development section. You need to flash that to the tablet and you will be good to go.
edit... this is what you want .. http://forum.xda-developers.com/showthread.php?t=1708613
Click to expand...
Click to collapse
Hello,
Just to clarify, I can get into recovery without issue, it just won't boot after factory reset and now hangs at ASUS logo.
Is there a way around this at all? :--(
Hello,
Latest problem is having ASUS Transformer Prime ADB Interface listed in Device Manager, but not being able to use the adb shell.
I get either 'device not found' or occasionally something about /system/sh not being found, in either case this is obviously not good.
I can still get into TWRP 2.1.3 though, surely there must be a way round this?
Now fixed, see first post
Hey guys,
I am really hoping someone can please help me out with this, as I am travelling and relying on my transformer to get me around. This is what I’ve done: basically I didn’t like the stock software, so I updated from ICS to JB, downloaded the unlock tool, unlocked the bootloader and rooted my tablet and installed TWRP recovery
From there I installed some version of Paranoid Android which kept freezing up and being jittery, so I figured I’d play it safe with a stable cm10 build, tried to flash it with TWRP and it just got stuck on the ASUS splashscreen, which I later realised was due to TWRP not being at the latest version (did I mention I am clearly a total rookie).
So I flashed paranoid back, and tried to update TWRP which I couldn’t get my head around (GooManager wouldn’t allow me to update it) so I decided to try ClockworkMod Recovery, which I downloaded this .zip and just flashed it over the top, which I thought you could do… Now my tablet won’t boot past the Asus splashscreen, nor will it boot into recovery. I could access the bootloader screen before but now I can’t.
The only thing I can think to do that worked for someone somewhere on the internet was to just let the battery run dead and then try holding down the Vol Down + Power.
Can anyone recommend anything? Or at least tell me what I’ve done?
thanks all
Twinning92 said:
Hey guys,
I am really hoping someone can please help me out with this, as I am travelling and relying on my transformer to get me around. This is what I’ve done: basically I didn’t like the stock software, so I updated from ICS to JB, downloaded the unlock tool, unlocked the bootloader and rooted my tablet and installed TWRP recovery
From there I installed some version of Paranoid Android which kept freezing up and being jittery, so I figured I’d play it safe with a stable cm10 build, tried to flash it with TWRP and it just got stuck on the ASUS splashscreen, which I later realised was due to TWRP not being at the latest version (did I mention I am clearly a total rookie).
So I flashed paranoid back, and tried to update TWRP which I couldn’t get my head around (GooManager wouldn’t allow me to update it) so I decided to try ClockworkMod Recovery, which I downloaded this .zip and just flashed it over the top, which I thought you could do… Now my tablet won’t boot past the Asus splashscreen, nor will it boot into recovery. I could access the bootloader screen before but now I can’t.
The only thing I can think to do that worked for someone somewhere on the internet was to just let the battery run dead and then try holding down the Vol Down + Power.
Can anyone recommend anything? Or at least tell me what I’ve done?
thanks all
Click to expand...
Click to collapse
CWM is not compatible with Jellybean. Unfortunately you are hard bricked.
Why didn't you make a backup with NvFlash? If you did that you could restore your tablet.
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
dar101978 said:
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
Click to expand...
Click to collapse
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
CalcProgrammer1 said:
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
Click to expand...
Click to collapse
Thanks thats what i did, I just basically had to use KIES to use the emergency recovery, then root my phone again. My question is what version of TWRP causes this? cause i used the newest version i could find off GOO. My other concerne is, will it accept or be safe to use a custom ROM? Well i gues ill find out :laugh: THANKS AGAIN!
Everyone with the sgh-i717 is having problems with the latest TWRP and the most stable version is 2.5.0.0. Go with that one or you'll be starting all over again I imagine. And don't just stop at the download link in the OP's, read the thread and find out what's going on. The problems with TWRP have been going on for a while and the development threads have a lot of comments about the latest build causing problems. Good luck! :good:
Hello people!
First of all - Happy New Year!
Okay, my problem is this:
I gave my phone to a person who knows what he's doing, to change my ROM (switched from stock ROM to CM10).I wasn't there and didn't know what he did but I was glad that he did it. The ROM was still a beta (not sure how is it called for the ROMs) version and I had some problems with the camera, chrome and messanger were closing even if I didn't want them and many other problems which i dont remember now. This was the reason I wanted to change this CM10 to another ROM , but I had some problems with changing it. Took me like 4 hours (eventho my phone was unlocked) and i almost gave up when I tried for last time to install CM again and it worked! I don't know what I did because It was long ago. Anyways to my main problem:
Before 2 days I told myself ok now is the time to change the ROM (New Year - new ROM ). I started doing everything that the post I found says ( I can't give you link, but it's for dummies). All I did wrong was not downloading the whole folder with the boot.img (which I still don't have) ,but only the file boot.img from 2shared. I had to do the last step, because the device entered a Bootloop. Since then I Power ON my phone ,but all it does is to show the "HTC quitely brilliant logo. I tried to reinstall the Viper ROM , but nothing changed. I panicked. I had Trickdroid 6.0 on my device so I tried to install it too, but still the ending result was the same... The last choice I had was to install the CM ROM again, so I did it. Still nothing. I think it all came from the boot.img file i downloaded , but I'm not sure. I started to search forums for this kind of issue but I didn't find anything similar to this, or atleast I didn't search for the right thing. Anyways, I thought of doing a factory reset from the Fastboot mode, and after 2 hours of searching the forums I did a factory reset. The phone restarted and entered in the Recovery menu again. I didn't know what was I supposed to do there + I had NOTHING in the phone (which I knew it was going to happened) but I didnt think that the ROMs will be deleted too. So I tried to connect my phone with the USB ,but as usual it needs a full boot up to connect with the USB, so I can upload some files to it. Now all I can do is enter in the Recovery/Fastboot menu. Can anyone help me or does anyone have an idea what should I do?
P.S. Sorry for the long post. I'm desperate.
Can you sideload a zip through recovery? Because boot.img files are only a kernel, so you're going to need a complete kernel.
Sent from my Nexus 4 using Tapatalk
SMillerNL said:
Can you sideload a zip through recovery? Because boot.img files are only a kernel, so you're going to need a complete kernel.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I cannot connect to the computer. I don't have anything on my phone and I can't upload anything to the device. Except if there is a option to 'allow" something via fastboot from the computer. Since that is the only connection I have with the phone.
I'd like to start this thread in establishing that I am not familiar with how all this works, nor do I have any idea how to fix it, which is why I'm here. I only know the system info, such as version, firmware, etc.
In attempting to add cyanogen mod on my already previously rooted Samsung Galaxy Tab 2 7.0 gt-p3113, I watched a video that directed me to install clockwork recovery and root in a single bundle using Odin, (which I successfully did). I then proceeded to install cyanogen mod while in clockwork recovery, which it then told me to factory reset wipe all data before doing so. After going to the "main page" of CWM and resetting the device like it told me, I then went back to install cyanogen mod, only to have it tell me that CWM is out of date. I tried rebooting the device, but it would take me back to CWM, which im assuming means I deleted to OS on accident.
After all that, I finally concluded I'm stuck on an old version of Clockwork Recovery with no OS installed. I can access download mode, however when I'm not in download mode the device automatically boots up to the old version of clockwork mod, and I'm stuck there.
As I have no idea how all this stuff works and did pretty much everything from a YouTube video, I'm hoping a more experienced developer can help fix the problem and somehow help me regain use of my tablet. At this point I don't care whether I can get cyanogen mod installed or not, and I would appreciate all the help I can get.
Thanks
EvilPenguin42 said:
I'd like to start this thread in establishing that I am not familiar with how all this works, nor do I have any idea how to fix it, which is why I'm here. I only know the system info, such as version, firmware, etc.
In attempting to add cyanogen mod on my already previously rooted Samsung Galaxy Tab 2 7.0 gt-p3113, I watched a video that directed me to install clockwork recovery and root in a single bundle using Odin, (which I successfully did). I then proceeded to install cyanogen mod while in clockwork recovery, which it then told me to factory reset wipe all data before doing so. After going to the "main page" of CWM and resetting the device like it told me, I then went back to install cyanogen mod, only to have it tell me that CWM is out of date. I tried rebooting the device, but it would take me back to CWM, which im assuming means I deleted to OS on accident.
After all that, I finally concluded I'm stuck on an old version of Clockwork Recovery with no OS installed. I can access download mode, however when I'm not in download mode the device automatically boots up to the old version of clockwork mod, and I'm stuck there.
As I have no idea how all this stuff works and did pretty much everything from a YouTube video, I'm hoping a more experienced developer can help fix the problem and somehow help me regain use of my tablet. At this point I don't care whether I can get cyanogen mod installed or not, and I would appreciate all the help I can get.
Thanks
Click to expand...
Click to collapse
Well, I would say that may be a bigger problem ! Now what I think better for you would be trying to flash the stock ROM over to the device again I am sure you have your hands over the flashing. So head over to the sammobile/firmware section and try getting the stock ROM downloaded and flash it over your device.