Bootloader erased??? ASUS Zenfone 2 - Android Q&A, Help & Troubleshooting

A few months ago, I moved from stock Asus ROM to CyanogenMod 13 ( Phone rooted, bootloader unlocked and TWRP installed), although recently I wanted to move back to original ZenUI due to battery drain and a couple of minute bugs, I decided to flash the ROM through TWRP (biggest mistake of my life) this is the stuff I did :
1. Downloaded Stock ROM for my Zenfone 2 Z008
2. Copied it to SD Card along with CM13 and GApps Super package as backup
3. Went into recovery mode (TWRP) to flash the ROM
4. Erased everything except SD Card
5. Attempted to install stock ROM, after a few minutes it failed [ it was stuck on something "mounting...."] (I know I'm a noob)
6. Thanks to the CM backup I flashed it along with the GApps
7. Rebooted phone
AND BAM!
No booting screen , no booting animation just an illuminated black screen, after a while it showed the welcome screen of CM 13 asking me to enter details - Language , Google account blah blah blah...
Till date whenever I switch on my phone there's no booting animation (not even the ASUS logo which comes before the booting animation!) And somehow after a while of black screen my phone displays my lockscreen and I am able to use it.... Now the best part, I can't access my bootloader! Everytime I try to open it (be it from pressing the buttons to using an app to easily access it) bootloader won't open. Upon using the Volume down + Power button combination the phone vibrates a little and nothing happens while it's supposed to give two long vibrations , though it does give the long vibrations upon normally booting the phone or while putting it for charging while it's switched off (Yes the charging animation is there)...
So yeah, I need your help guys...

Related

Galaxy Tab 10.1 Wifi P7510 stuck on battery screen

Hi
I used the factory reset function on my tab a couple days ago to delete all apps and such and upon reboot it was stuck at the slowly flashing Samsung logo and would proceed no further. I left it for a good hour and a half in that state before I tried hard resetting it but no dice. I've had it do this before when I first rooted it, but unlike that time it doesn't replay the whole boot animation, just the logo part at the end of the animation. I managed to get it in clockwork mod or bootloader whatever that function is and cleared all the caches and did a reboot recovery (i believe thats what it was called) but upon reboot it did the same exact thing. So after that I gave up and went to bed, but the next day when I went back at it again it wouldn't even turn on. After messing around with the power button and volume button trying to get into recovery mode it finally turned on but went to the battery screen with no other actions. I've tried several times to get it into recovery mode but it either wont turn on or it just goes to the battery screen. I have it plugged into my pc at the moment and apparently it is in recovery mode or something because Odin recognizes it. Says [0:COM3] and the box is yellow, but the screen never turns on though when holding the power button and volume button while it's plugged into a pc, the pc recognizes something plugged into the USB slot. My pc is only recognizing it as a modem and will do nothing else with it.
I have the Starburst rom and the overclocked kernel installed and would like to either revert it to stock rom or perhaps the AOKP rom, milestone 6. Is there any way to do this if I can't boot it into a state where I can access the SD card on my pc? All the guides I've found always require I put files on the sd card to flash in clockwork recovery mod. Thanks for any assistance
Edit: Solved it myself, feel free to delete this post. Thanks!

[Q] Lenovo A830 Boot Loop No Recovery

I have a problem with one of my Lenovo A830 phones.
I bought it from Etotalk, so it came rooted, and with their custom version of the Lenovo Stock ROM and their custom version of CWM 5.5 installed.
I tried formatting my SD card and then doing a factory data reset from within the operating system. (I was intending to install MIUI V5 after rebooting into recovery).
However, on rebooting, the device is now caught in an infinite boot loop, and I am not able to boot into recovery mode (by holding down power and both volume keys). It loads the initial splash screen, then shows a few seconds of the Android character and some whirring cogs before rebooting.
I am able to boot into Factory mode (power and volume up) or Meta mode (power and volume down). Factory mode has a number of options, but they are all in Chinese characters, which I am unfortunately not able to read.
I did notice that my SD card seemed to be write protected when I tried to format it in my computer and to copy on the new ROM - I solved this by putting it in a different phone and reformatting it. I wonder whether the factory reset process has write protected something it shouldn't have?
Does anyone know how I might best proceed? I've been digging around on the forums, and tried a few things, but there's nothing which seems to provide a coherent solution for this problem.
I've got the latest Android SDK Tools, MTK Droid Tools 2.4.8, SP Flash Tool 3.1312, some additional ADB drivers (120827 v3.7) that I'm not sure how to install, the latest MIUI V5 ROM (3.8.16), and the latest stock Lenovo ROM (S118 from Need A ROM, just in case I need it).
Maybe different SP Flash Tools version?
I had trouble using SP Flash Tools v3.1312 with A830. Once I switched to v3.1304.0.119 I was able to flash both the original ROM and the custom MIUI one without serious issues. I'm unable to post the download link but google it.
One other thing is that when connecting the phone, it usually loads the something something Preloader driver, which is no good (even if it gives you Download OK). When attempting to flash either ROM, try pressing both the power and volume up buttons while connecting the phone (after pressing Download), only way it worked for me.
Good luck!
I managed to sort this out quite simply in the end!
On the Lenovo A830 (and presumably other Lenovo Android phones?), you enter recovery by pressing power and then pressing volume up / down together after a short pause. The short 1 - 2 second pause is important, because if you try and press them at the same time or in quick succession it doesn't seem to work.
I then installed MIUI V5 from the SD card followed by Google Apps after a reboot. In order to get MIUI to install, I had to remove the assert check at the top of the update script, because this seems to erroneously check for the A820 (even though there isn't currently a port for this device?). It's working excellently with two exceptions - I am unable to select the SD card as a storage device, and Google Play store is not searchable (it causes a Force Close).
tominglis said:
I managed to sort this out quite simply in the end!
On the Lenovo A830 (and presumably other Lenovo Android phones?), you enter recovery by pressing power and then pressing volume up / down together after a short pause. The short 1 - 2 second pause is important, because if you try and press them at the same time or in quick succession it doesn't seem to work.
I then installed MIUI V5 from the SD card followed by Google Apps after a reboot. In order to get MIUI to install, I had to remove the assert check at the top of the update script, because this seems to erroneously check for the A820 (even though there isn't currently a port for this device?). It's working excellently with two exceptions - I am unable to select the SD card as a storage device, and Google Play store is not searchable (it causes a Force Close).
Click to expand...
Click to collapse
Hello,
How did you manage to fix the reboot loop?I have the same problem,after a factory reset the phone just reboot like you said in first post...please help me fix it...
claudiuionel said:
Hello,
How did you manage to fix the reboot loop?I have the same problem,after a factory reset the phone just reboot like you said in first post...please help me fix it...
Click to expand...
Click to collapse
Hi I had similar "reboot loop" problem this morning after a phone factory reset.
I have no idea how I solved that but the following was the steps I tried:
1. Install the MTK6589_PdaNET_ADB_VCOM_Drivers. Skip the USB connection during setup. Start the PdaNET after setup finished.
2. Insert battery inside the phone and connect the phone with the computer by USB
In my case, the phone reboot loop once, and the lenovo screen appeared in the second restart. The phone hanged. I unplugged the cable, took out the battery, insert the battery again and start the phone normally again and it is working now.
I recommend installing the recovery rom after you have fixed the phone.
Goodluck

Pepsi P1S corrupted eMMC?

Hello
Yesterday i have recieved the Pepsi (Koobee) P1S. it was full of bloatware so i decided to flash a modded rom. After i realized that this custom rom is only in english and chinese (Im German) i wanted to switch back to the original. But then i made the biggest mistake: I have flashed the false rom (CM for Mt6592 CPU but false Smartphone). After that i have flashed the right original rom again. but a strange Error appears: the Phone boot up normaly and then freeze and reboot by itself..over and over again. But not at the same step. Sometimes it freeze during the Bootanimation..sometimes it boot up completly and i can swipe through the Screens (for about 10 sec). When i push the standby button (Display went off) the Phone stays in this mode and dont freeze.
the i flashed TWRP and try to wipe the phone. Even in TWRP it freeze, but not during the wipes or in the Boot Mode slelect screen.
I Have a friend with the same phone. Is it possible to copy a complete backup (eMMC etc) to my phone? Or someone had a Idea what i can try next? I have flashed different roms (for this phone) so many times, but the error is still there.
Please help me.. It should be a present for my GF birthday today
SOLUTION
I downloaded the flashtool that flashes MTK Devices then searched google for Pepsi p1s needrom and downloaded the original firmware scatter file, turn off the P1S unplug it from USB,...Start the flashtool, and search the firmware will be second search bar select search and browse your computer for the firmware you downloaded from needrom, then you will see it load all the files.....there is a button bar that has an arrow open the arrow and select firmware update, then hit the green go button after you hit the green go button plug in your powered off PEPSI P1S ....it will give you a red bar on the flashtool at bottom first, then it will format your device properly, then install all the necissary files, its real quick about 3 minutes, after a box will pop up on the screen and say OK with a big check mark, at this point you can unplug your phone, power it up and wait about 3 minutes, everything will be normal again. So sorry I would post the links however I forgot my password and username that I was using for many years and forgot my recovery email as well.....so if you google it you can find the stuff, just hope I helped with the proper method of flashing......good luck, let me know how it goes.
Thanks but i know how to flash the firmware with SP Flash Tool. i have flashed the P1S with 3 different roms..but always the same error (freeze and reboot at different points)
Are you using download mode? Or firmware update? The reason I ask is download mode always gave me a bootloop, but when switched to firmware update mode it formats the device correctly and fixes the file structure, try firmware update mode.
Im using "Format All + Download"
Try using firmware update mode, let me know what happens.
same problem...freeze (at different points) ans reboot.
here you can see what happen:
https://www.youtube.com/watch?v=J1oFkgUwtOo
try this! P1
power off
then hold power button + volume down
the boot mode will appear
select recovery
it will show you no command
then pres power button first and the press volume up
now you device is on recovery
then select
wipe data/factory reset.
Blueray88 said:
Hello
Yesterday i have recieved the Pepsi (Koobee) P1S. it was full of bloatware so i decided to flash a modded rom. After i realized that this custom rom is only in english and chinese (Im German) i wanted to switch back to the original. But then i made the biggest mistake: I have flashed the false rom (CM for Mt6592 CPU but false Smartphone). After that i have flashed the right original rom again. but a strange Error appears: the Phone boot up normaly and then freeze and reboot by itself..over and over again. But not at the same step. Sometimes it freeze during the Bootanimation..sometimes it boot up completly and i can swipe through the Screens (for about 10 sec). When i push the standby button (Display went off) the Phone stays in this mode and dont freeze.
the i flashed TWRP and try to wipe the phone. Even in TWRP it freeze, but not during the wipes or in the Boot Mode slelect screen.
I Have a friend with the same phone. Is it possible to copy a complete backup (eMMC etc) to my phone? Or someone had a Idea what i can try next? I have flashed different roms (for this phone) so many times, but the error is still there.
Please help me.. It should be a present for my GF birthday today
Click to expand...
Click to collapse
I have noted one thing.
when I update supersu to play store and reboot it goes in bootloop.
so I recommend not to upgrade or even to make unroot just after removing apps with viruses

Bricked Umidigi Crystal

I have a Umidigi Crystal (2/16) and it´s not booting anymore.
How that came is a long story.:crying:
I got the phone, wanted to root it and while I was enabling usb debugging in developer options, I noticed you can root it from there as well.
I have no idea whether thats a Umidigi special or if that was seen on other phones too, basically I had a slider option to enable root access.
After a reboot, SuperSU was installed automatically, root checker, file explorer and rom toolbox worked fine with it but I actually rooted to get Xposed Installer.
That worked very well too, only did I want to have a custom recovery to prepare my phone in case of a bootloop.
So I followed these instructions.
I hadn´t unlocked the bootloader by the time and since the instructions said I would have to unlock it I did that first using these instructions.
Everything worked as expected but from this point on, on the pre-bootanimation picture my screen would say
Code:
Orange State
Your device has been unlocked and can't be trusted
Booting in 5 sec...
As everything else was the same as before, I just ignored it.
Then I moved on to installing TWRP by, again, these instructions.
The process seemed to work but after finishing, I was unable to boot into recovery mode, my phone would just boot into the normal OS(which still worked by the time).
I wanted to get around that by using this app but because of the unlocked bootloader my phone was factory reset
and I had to root again.
I was going for the same way I already did it beforehands and I was asked to reboot again.
After that point, my phone was stuck in the pre-bootanimation screen saying it´s orange state thingy again and would just stay there forever.
I tried installing the stock rom from here ((2/16 - V1.0_20171026)) to get rid of the root setting I enabled.
Now I get the pre-bootanimation screen with the orange state text again and after 5 seconds it keeps the background image but the text disappears.
Thats where it´s stuck for like 3 hours now.
When I press the power key a couple of seconds, that loop starts again, I can´t turn the phone off.
Things I can still do:
•Reboot (holding the power button, still get stuck the same way though)
•Access a PC, the internet, an SD Card and electricity
•Charge the phone
•I still have all the drivers on my PC properly installed
Things I can´t do
•Keep the phone turned completely off
•Boot into fastboot, recovery or normal OS
•Get the PC to recognize my phone (not even the adb)
What I want (if possible in that order):
•Boot into literally any OS
•Use the current OS or any custom rom
•Have root access without the developer option method
•Have TWRP
•Unlocked Bootloader
I know, I ask for a lot but this is the only phone I have right now and I badly need it.
Getting it to boot again is really the primary goal here.
Thanks so much to everyone who tries to help me, it really means a lot

Switched ROMS (Evolution X -> Nusantara) -> NOW Bootloop

Hi Community,
I read some posts how to fix my Problem, but i cant go to a service Point.
So I was using the Evolution X for a long Time (Installed with TWRP 3.1.0).
And now i wanted to change to the Nusantara Project (Vanilla), I did a clean Flash, everything worked i could access the System.
Than i had problems installing Play Store, so i rebooted into Recovery via the System. But now im Stuck in the Loop.
Can i Somehow connect my Phone to the PC and Reset?
Can someone tell me if i Hard/soft bricked my phone ?
Just a little advice, would be really appreciated.
Thanks a lot
Go to TWRP, wipe system, cache, data and dalvik. Now flash nusantra and whichever GApps are recommended for it (if there are no recommendations then use OpenGApps, make sure the architecture is correct). Now wipe dalvik and restart. Sometimes, certain roms begin to bootloop if you boot into the rom first, then try to install gapps later.
If you still have issues, just reflash the stock rom.
I cant access the TWRP anymore, im just stuck on the Bootloader, no matter how i turn on The Phone (Volume Up + Power ON ), (Volume Down + Power), (All 3 Buttons)
Nothing works anymore i dont understand ....
Im searching the net but i cant go to fastboot or something else, its just keeps on rebooting ...
So it's bootlooping, but you cant access recovery?
When the screen turns off, press the key combo and it should go to recovery.
Your best bet is to take it to a service centre, but if that really isn't possible for you, then wait for its battery to drain completely, then when you plug in the charger, instead of turning the phone on, press the key combo to enter the recovery. From there, wipe and flash some other OS.
I've also heard that certain versions of TWRP don't support some roms, leading to a bootloop. In that case, you'll have to use orangefox recovery to flash the rom (orangefox is flashable via twrp)
Yes its Bootlooping.
When i turn it on, on the Left Corner "Recovery Mode" blinks for one second. Than the usual Text appears:
"Orange State
Your Device has been unlocked and cant be trusted
Your Device will boot in 5 Seconds".
So after a couple of seconds (around 10-20 sec)
It turns off and immediately on again. I Just can turn it OFF when i hold all 3 Buttons.
Than i try starting it with Volume up + Power / Volume down + Power, But i cant access Recovery or TWRP.
So i should wait til the battery gets low and try it again ?
Like i said, my custom Rom (Evolutionx) and TWRP just worked fine. I dont know man ...
Well since your bootloader is unlocked, try flashing the stock rom again. Look for a tutorial and follow it.
Hi I managed to unbrick my device with this guide, and im back on a stock rom
Unbrick
i ran following commands to get to my custom rom:
I run adb reboot bootloader,
add executed following commands.
(Pitch Black recovery 3.1)
- adb reboot bootloader
- fastboot flash recovery recovery.img
-fasboot reboot recovery
It just hang up and booted after a while into the normal system.
But im not able to get to the recovery menu ?
When I restart and hold Volume up + Power, i go in a loop and the phone keeps restarting over and over again.
what have i Fu**ed up ?
Do i need another recovery tool ?
sorry guys, i appreciate your help a lot tho !
EDIT: Is my bootloader unlocked ?
I can access via "adb reboot bootloader" the phone
and on the blackscreen on the phone it is written:
oppo verfiy pass
fastboot_unlock_verify ok
Update:
So i tried some Stuff and i got Red State. No Problem i Unbricked it once again and now im on Stock Android 10.
Now im Trying to enable the bootloader again.
I downloaded the In Depth Test_Realme_6.apk but i keep getting the Error that i should update the system.
So should i update the system ?
I cant find a CURRENT Tutorial to make this work, please help...
If you cant find a tutorial for your version, why not downgrade back to a previous one if possible.

Categories

Resources