Hi all, this is my last hope at the moment. Any input would be highly thanked.
I own an ASUS Padfone 2 (KOT49H.WW_Padfone-11.8.4.23-20141028), stock firmware, that I managed to get soft-bricked, as I read they call it.
Phone is unrooted, ran KitKat, and I really don't know much more about it, I'm not really an expert unfortunately... No custom ROM or any of those pro stuff.
Scenario:
Every single app crashed upon opening, performed a reboot, phone got stuck into infinite boot-loop, at the company logo in the beginning.
What can the phone do and what I've done so far (all of which have been found through internet):
I can enter into recovery mode.
Did a factory reset and wiped cache partition before the following.
I entered what the phone calls "CSC mode", that other sources call "fastboot mode".
Followed this guide http://forum.xda-developers.com/showthread.php?t=2256977 , installed drivers, entered into the proper directory on CMD, and typed "fastboot boot recovery.img", but CMD says "OKAY" and all, but gets stuck at "booting...", even after like 15 minutes.
Then, for whatever reason I saw on the internet, I tried the command "fastboot oem unlock" that also didn't finish anything either in CMD or (seemingly) on the phone.
Then, I tried following this guide in CSC mode (even though I don't have the invalid kernel error) http://www.modaco.com/forums/topic/365818-padfone-2-invalid-kernel/#comment-2191432 , but also didn't get any further than CMD stuck at "booting..." for forever.
I suspect it could be possible to do some of those booting magic, but I have no clue how it works and how my problem inside the problem could be solved...
Thank you so much in advance.
(Please beware that I don't understand what the words bootloader, fastboot, flash or ROM mean. I'm a mere mortal.)
Related
i have an lg optimus l9 p769.
it was rooted, overclocked to 1240, init.d enabled, various tweaks, and was running 4.1.2
but i wanted more. so i decided to try to unlock my bootloader to try out some roms,
i used "[Guide]Unlock Bootloader for Noobs P769" by "carloswii5" im going to tell you step by step what i did and what happened...
i downloaded the zip that supposedly contained all the files i needed and off i went.
i enabled usb debugging and put the connection to "lg software"
i immediately flashed the v20 kdz, so far so good. it booted with the mirrored image and wonky touchscreen
i rechecked that usb debugging was on and check the connection for "lg software" and all was good.
connected to wifi, i opened the browser, went to facebook and browsed a while, then i let it sit for 35 minutes exactly.
i got to step 5
5) Ok now that the 30 minutes or more have passed you need to go to the downloaded files and move
the "Android" folder to your "C:\" drive "dont worry just has adb files" now open a command prompt and
type the following
"cd c:\Android"
"adb devices" to make sure your phone is connected a list of numbers should appear
"adb reboot oem-unlock" and your phone should then reboot
then the lg logo will appear then a mirrored confirmation to unlock bootloader just press
the "Volume Up" button and it will confirm it then hold the power button until it reboots
Click to expand...
Click to collapse
the zip i downloaded didnt come with "android" folder, so i used an adb from a different folder.
it recognized it under "adb devices" so i typed "adb reboot oem-unlock"
this is where it got weird, it rebooted, but there was no confirmation too unlock the bootloader. it just simply restarted. so i tried again.
nothing.
i thought " well hey, i didnt unlok my bootloader so no harm done, ill just flash v10g back and start back from there."
no precautions, i just flashed the kdz. phone restarted. still had a mirrored image, loaded to the boot screen animation and got stuck,
i read that a hard reset might fix that, so i tried it, but its as if the phone isnt recognizing the buttons at all.
my phone will, however, still go into "software update" but the offline flashing tool says the phone is not connected, but my laptop identifies i
a "omap" device, this is where im stuck.
cant flash any kdz, cant hard reset, cant boot pass animation, will anybody help me with this issue?? pleasee!!!! ive never had problems following directions as far as flashing, rooting, etc. etc. im familiar with basic aspects of android
You shouldn't have flash it back to 10x version that causes bootloop. Maybe try online recovery lg tool or flashing bootloader and uboot, there should be contained instructions how to fix drivers too.
Wysłane przez LG P760 L9 PACMAN 4.3 za pomocą Tapatalk 4
hi, i work helping my classmates when they stuck on their phones... ok, i'm apologize for my bad english but here is the thing, i now have one Huawei G610-U00 and the phone say "Encryption unsuccessful", i notice that him install the twrp recovery so i try flashing a new recovery using fastboot and the fastboot only say "sending 'recovery'" and nothing else happens(i left all the night, the phone only discharge the battery,), make a search on google and find info related and try them, try using sp flash, try installing a new zip, even try a force-update but when press the vol + and - and the power key, the phone go to recovery, also in the bootloader mode it only say "recovery_status:UPDATED" nothing else, the "adb devices" comand shows '0123456789ABCDEF' the "fastboot devices" show "mt6589_phone_720pv2", please need help i use the adb comand and try to format but only receive error messages, this is that i get on the recovery:
https://drive.google.com/file/d/0B_NnURitRMg-ZUZCUC1WaXVIQkdPSGRCaE90NUFUVUZodnBr/view?usp=sharing
https://drive.google.com/file/d/0B_NnURitRMg-RUN5ZjhWbklDUVRNeThFbXRMLUdfUUNoVkFJ/view?usp=sharing
https://drive.google.com/file/d/0B_NnURitRMg-ZGxqYlhMeTBhbVVXbERHWXNoN0xXYlgxTFdV/view?usp=sharing
https://drive.google.com/file/d/0B_NnURitRMg-bVJRODB1N3hXckxNbnhMZFBpajdhekxhaUc4/view?usp=sharing
Click to expand...
Click to collapse
goluisgerardo said:
hi, i work helping my classmates when they stuck on their phones... ok, i'm apologize for my bad english but here is the thing, i now have one Huawei G610-U00 and the phone say "Encryption unsuccessful", i notice that him install the twrp recovery so i try flashing a new recovery using fastboot and the fastboot only say "sending 'recovery'" and nothing else happens(i left all the night, the phone only discharge the battery,), make a search on google and find info related and try them, try using sp flash, try installing a new zip, even try a force-update but when press the vol + and - and the power key, the phone go to recovery, also in the bootloader mode it only say "recovery_status:UPDATED" nothing else, the "adb devices" comand shows '0123456789ABCDEF' the "fastboot devices" show "mt6589_phone_720pv2", please need help i use the adb comand and try to format but only receive error messages, this is that i get on the recovery:
Click to expand...
Click to collapse
I have a similar problem with Huawei Y320-U030, MTK 6572, Android 4.2.2 with many malware infections. Almost all applications keep crashing, Factory Reset from Settings does not work, but I can do it from the recovery and it seems to complete successfully but when the devices boots, all user applications and files are there. I have flashed it with stock ROM and backup ROM from an other working similar phone, the flashing process completed successfully but when the device boots all user files and applications are untouched, even after formatting the whole flash with Sp flashtool, Volcano box and Miracle box! An applications called DU Speed Booster is set as device administrator with a pattern lock which cannot be deactivated. Uninstalling the imo application makes the device reboot and hang on Huawei logo untill the battery is pulled out. I can't install any new apk or root the device even using PC. Music, videos, and photos in the internal memory can be copied with a computer but cannot be deleted. Formatting the internal memory with a PC seems successful but all files on the device are intact. Very interesting case indeed.
Can I do that? My device won't boot into recovery, despite flashing it through fastboot several times. Also tried "fastboot boot twrp.img" and it doesn't boot. Can I flash original OxygenOS or any other rom through fastboot? If so, how?
Also my device cannot be seen @"adb devices", I believe usb debugging is off, any way I can turn it on using fastboot? Googled for a while and couldn't find any information.
Just google "Mega Unbrick Guide" or search here !
Thanks for the suggestion, I did follow that process successfully but the phone is still stuck in a bootloop. The bootloader locked in the process as well and now I cannot flash any recovery through fastboot. The phone will get into recovery though but trying to sideload anything will result in a "protocol fault(no status)" error.
As a sidenote, the internal storage seems "faulty" to say the least now. It is not recognized at any time as MTP device but rather shows 3 unformated partitions of 1.00MBs, 155MBs and 2.5GB respectively. Moreover trying to "Install from Local" @recovery menu renders no response, just a short vibration, sometimes.
Anyone else encountered this problem? Is there any chance it is a hardware problem afterall? I'm really clueless right now.
Sorry to make my first post a request for help. Here's what happened.
I have a model KIW-L24 Honor 5X, with code-name kiwi with TWRP and Lineage OS 15.1 installed. Last night (today?) at around 2 AM PST or so (not sure of the exact time, I would have looked on my phone) my phone suddenly rebooted into recovery. I waited for the menu to pop up or something, but instead it eventually rebooted again. After that, every boot consists of "Boot/Recovery image verify failed!" "Please update to the authorized images." and then brings up the fastboot screen, which proudly displays "PHONE Locked" in green and "FRP unlock" in red. From what I understand, this means that the bootloader is locked (again).
Now, in theory, I can re-unlock the phone (once I find the relevant code again), flash lineage os again, and continue on my merry way. However, I have a password manager on my phone (Keypass2Android) that has not been backed up recently, so it would be preferable if I could recover that, at the very least. I've already tried booting both a custom recovery image and a stock recovery image via
Code:
fastboot boot <image>
but it only came back with
Code:
FAILED (remote: Command not allowed)
so I can only conclude that I cannot boot arbitrary images while the boot-loader is locked.
So, here's my options as I see it:
Unlock the bootloader again, wiping the device.
Flash stock, hope that that doesn't wipe my data. (EDIT: if it doesn't, hope that it doesn't bootloop or something requiring me to wipe)
Find some other method of recovering data from the device.
So, my questions are: how might the bootloader have gotten locked in the first place? Is there anything I can do to recover data, especially my password manager data? Please let me know if there's any other information you need.
Thanks in advance, regardless of the answer.
i managed to delete twrp and when i did then it shows that the system has been destroyed and after restart it is stuck on
fastboot windows. i tried to connect it with my pc so i could install flash rom but it doesnt show up on pc after connecting to usb.
i dont understand what to do next... helppppppppppppppppppppppppp
I have been in this situation before but I'm not sure how exactly i got into it but I was also doing something to do with twrp. Anyway, whenever you encounter such a problem you need to provide as much information as you possibly can to help us help you. This way people are able to narrow down to what causes a particular problem. One question I have is how did you "delete" twrp?
Now for how I got out of that "system has been destroyed" problem. First off, I had already successfully unlocked my bootloader (don't know if you had). Also, the adb drivers were properly installed on my pc. What I did (at the "system has been destroyed" screen) was to let it sit there while connected to the charger for what seemed to be around 10 minutes and kept doing what I was doing and out of the corner of my eye I saw it rebooting and unexpectedly it went into fastboot. I connected it to my pc and it showed up in device manager and "fastboot devices" command detected it. I proceeded to successfully flash recovery with fastboot and then used "fastboot boot recovery.img (or whatever you have renamed your recovery to)" command. It went into recovery mode after which I copied rom via mtp and flashed it and it agreed to boot into system after the flashing was successful.
These may not be the exact steps I took but as close to them as I can recall (because I was bewildered at the thought that my phone was dead). I think the key turning point was to let it sit at the "system has been destroyed" screen for a while.
twistyplain said:
I have been in this situation before but I'm not sure how exactly i got into it but I was also doing something to do with twrp. Anyway, whenever you encounter such a problem you need to provide as much information as you possibly can to help us help you. This way people are able to narrow down to what causes a particular problem. One question I have is how did you "delete" twrp?
Now for how I got out of that "system has been destroyed" problem. First off, I had already successfully unlocked my bootloader (don't know if you had). Also, the adb drivers were properly installed on my pc. What I did (at the "system has been destroyed" screen) was to let it sit there while connected to the charger for what seemed to be around 10 minutes and kept doing what I was doing and out of the corner of my eye I saw it rebooting and unexpectedly it went into fastboot. I connected it to my pc and it showed up in device manager and "fastboot devices" command detected it. I proceeded to successfully flash recovery with fastboot and then used "fastboot boot recovery.img (or whatever you have renamed your recovery to)" command. It went into recovery mode after which I copied rom via mtp and flashed it and it agreed to boot into system after the flashing was successful.
These may not be the exact steps I took but as close to them as I can recall (because I was bewildered at the thought that my phone was dead). I think the key turning point was to let it sit at the "system has been destroyed" screen for a while.
Click to expand...
Click to collapse
Hey thanks for replying to be honest ..i thought people will help but seems like nobody cares here..
The thing is i dont remember actually exact process but i somehow managed to delete the twrp ..
the main problem is you said after ur phone got onto fastboot you connected it to ur pc and flashed official rom but in my case in the device manger or anywhere ... when my phone is in fastboot mode and i connect it to my pc it doesnt show up as connected not in device manager or any other place...this is the main problem....if only my device shows up connected i wouldve flashed rom way before anything...its been 1 week since my phone died ...i need help...i tried everything from youtube ...seems it doesnt work for me
AjTheKiller1 said:
Hey thanks for replying to be honest ..i thought people will help but seems like nobody cares here..
The thing is i dont remember actually exact process but i somehow managed to delete the twrp ..
the main problem is you said after ur phone got onto fastboot you connected it to ur pc and flashed official rom but in my case in the device manger or anywhere ... when my phone is in fastboot mode and i connect it to my pc it doesnt show up as connected not in device manager or any other place...this is the main problem....if only my device shows up connected i wouldve flashed rom way before anything...its been 1 week since my phone died ...i need help...i tried everything from youtube ...seems it doesnt work for me
Click to expand...
Click to collapse
Have you ever had your phone detected by your pc in fastboot mode? And if you connect it to the pc, does the computer play the hardware detected sound?
You need to rule out a driver issue. I'm not the only other person to get the "system has been destroyed" message and people usually get out of it. I don't know why yours is so problematic.
Had you successfully unlocked bootloader?
The Good old "System has been destroyed" Message. Well, This is terrible This should not happen in the first place. I assume it happened Because you wiped data and then deleted twrp. But If you want help you have to specify how exactly did you " Delete TWRP" What steps did you follow to Delete it. None the less the best bet on getting your device back would be to go to the nearest service center. Pretend you did nothing and maybe they will say you got a bad update.