Help with bricked phone - ASUS ROG Phone II Questions & Answers

Hello, I wanted to root my phone following this tutorial.
After installing the twrp .zip file y rebooted my phone and I got the message "Slot _b is unbootable".
After searching around for a bit, I read in this thread and noticed that is says that if you install twrp, you must also install magisk or your phone won't boot.
Now, my phone can't boot, but I can still go to the bootloader and use fastboot.
I searched around for other people having this issue and found some threads saying to just flash the factory image.
However, I'm not too knowledgeable when it comes to rooting Android phones, so I was a bit confused. Where do I get this image? How do I flash it?
The only thing I could find with detailed instructions was this thread. However, I can't follow the instructions there because my phone is only detected by fastboot when I'm on Linux.
When I'm on Windows fastboot won't detect my phone and the thread I just mentioned requires executing a .exe file, which won't work on Linux.
Does anyone know how I can fix my phone? If possible, please try to be detailed with the instructions (where to download the files, what commands to run, etc.) because of my inexperience with these topics.
Thanks in advance!
Edit: I was finally able to un-brick my phone! I followed steps 1 and 2 from this thread and it worked. I had already tried it before and it didn't work, but trying more than once worked for some reason.

Related

Rooting Problem

Hello today I attempted something that I thought was going to be a quick video tutorial fix. I tried Rooting my HTC one. I followed several guides and read many posts I easily managed to unlock my phone. The problem started when trying to flash the recovery onto my phone, first I tried through commands: fastboot flash recovery and I received the error (FAILED data transfer failure unknown error) I've searched for 7 hours looking for a fix. Since I cant root reverting back to a fresh install is impossible, I cant find a RUU for telus, (I live in canada). I just don't know what to do, when I try to flash anything my bootloader freeze, drivers are up to date, tried restarting computer. Used One_M7_All-In-One_Kit_v1.0 doesn't work. This is a nightmare come save me before I jump off a cliff.
EDIT: What I did from beginning was followed this video "How to Root the HTC One-FlamingArio"to the point where you try and flash the recovery fastboot. That didnt work so after trying to fix that I tried How To Root HTC One & Unlock Bootloader - Easiest & User Friendly- The smoking Android ( super boot a 1 click install) that made my bootloader screen turn to tampered. after that I tried One_M7_All-In-One_Kit_v1.
Note in all in one kit I did erase cache and standard recovery works fine, I've re-installed it may times.
Cant post links yet but I gave video names.
EDIT: when I do the cmd fastboot devices my device shows up when I do adb devices nothing shows up could this be part of the problem?
Thank you all for your help, I re-installed all the programs on my laptop and redid all the steps and it worked. Bye!
Try this in ABD fastboot erase cache then flash the recovery again i hope this helps:fingers-crossed:
What did you do from the beginning? Could you post a step by step traceback of what got you to this point? Let's see if you missed any steps
Tonberry23 said:
Hello today I attempted something that I thought was going to be a quick video tutorial fix. I tried Rooting my HTC one. I followed several guides and read many posts I easily managed to unlock my phone. The problem started when trying to flash the recovery onto my phone, first I tried through commands: fastboot flash recovery and I received the error (FAILED data transfer failure unknown error) I've searched for 7 hours looking for a fix. Since I cant root reverting back to a fresh install is impossible, I cant find a RUU for telus, (I live in canada). I just don't know what to do, when I try to flash anything my bootloader freeze, drivers are up to date, tried restarting computer. Used One_M7_All-In-One_Kit_v1.0 doesn't work. This is a nightmare come save me before I jump off a cliff.
Click to expand...
Click to collapse
Keep an eye on this thread http://forum.xda-developers.com/showthread.php?t=2302870
Many people are looking for the Telus RUU.
Can you still access standard recovery? If so try reverting to factory settings (all data will be lost) and try to boot.
If you can get it to boot you should have more luck in trying to root your device.
I know that I had some issue's trying to get root on my device. But once I got S-off with revone, I was able to install root no problem.
ArmedandDangerous said:
What did you do from the beginning? Could you post a step by step traceback of what got you to this point? Let's see if you missed any steps
Click to expand...
Click to collapse
But I would agree, if you can post the steps you have taken so we know where the bottleneck is.
Hope this helps you out bud
Still need help
Tonberry23 said:
Still need help
Click to expand...
Click to collapse
Nice to see you sorted it
Assuming you have actually flashed a recovery image to your device, you will then need to push a ROM to your sd card so that you can flash it in recovery.
Just do the following:
1. I am guessing you have the HTC drivers installed on your PC.
2. Download the attached adb.zip and unzip it to a folder on your C drive and call the folder whatever you like.
3. Boot your device into recovery and plug it in to a powered USB port on your PC.
4. Navigate to the folder that you just created on your PC and copy your ROM zip into it. rename the ROM zip to 'rom.zip' to make life easy.
5. Inside the folder, press and hold the shift key and right click in a blank part of the window and select 'Open command window here' (screenshot attached).
6. Type 'adb push rom.zip /sdcard' (don't use the quote marks)
7. Press 'enter'
8. Once the zip has finished being pushed to your sdcard, you can reboot into recovery and then flash it as normal.
EDIT: That will teach me not to read to the very end of a post. I'll leave this here for someone else.

[Q] No OS, Stuck in BootLoop/Fastboot, with TWRP, No Download Mode, ADB don't work

I've had my Verizon LG G2 for almost a year and mistakenly upgraded to Lollipop. I researched downgrading to KitKat and it looked safe; I had dual booted my HP Touchpad with a similar process.
I tried rooting with ADB, but it was giving me fits. I used the LG One Click Root Tool. It worked fine. (Running on Windows 7.)
I installed TWRP v2.8.5.1, and downloaded a stock version of KitKat 4.4.4. (I'll admit, at this point, I had looked at multiple guides. Many had missing links or dead ends, but they were all about the same, and always stock.) I followed instructions on clearing and wiping caches, etc. I believe the exact ROM I tried to install was VS98011A_01.zip. It didn't work. It gave the error:
"assert failed: run_program("/tmp/loki.sh") ==0
E: Error executing updater binary in zip"
I looked for more ROMs and tried ParanoidAndroid "pa_g2-4.0-ALPHA-20131203-vs980.zip". At this point, I started to worry and tried installing the Gapps file I downloaded with the stock ROM, and it installed with no problems.
I then tried to install a newer version of TWRP "twrp-2.8.6.0-vs980.zip". (Again, I hadn't really found any great guides at this point, especially to fix my problem, so I was assuming there was something wrong with my ROMs.) It didn't work, and I tried to install Cyanogen Recovery because I ran across it and remembered it from my HP Touchpad. "cm-10.2-vs98012b.zip" did not work, and gave the error above.
I looked for Loki issues and tried downloading a fresh Loki (sorry, I don't have the link) folder and replaced all the files in the original KK .zip I tried. Same loki error. (Sometimes I'll get a "sysMapFile" error, but not often. At this point, I'd dragged a lot of things over to try to install and get anything to work.)
At this point, I tried the following:
http://forum.xda-developers.com/showthread.php?t=2448960
http://forum.xda-developers.com/showthread.php?t=2451696 (as well as a similar one by downloading a laf.img)
http://forum.xda-developers.com/showthread.php?t=2797190
http://forum.xda-developers.com/showthread.php?t=2432476
http://hackerspace.lifehacker.com/how-to-install-a-rom-via-sideload-1505153925
http://forum.xda-developers.com/showthread.php?t=2318497
http://www.androidayos.com/2014/10/06/fix-bricked-lg-g2-stuck-logo-twrp-bootloops-download-mode/
http://forum.xda-developers.com/showthread.php?t=2448960
There were definitely some more links I used but these were the most promising and the ones I still have open.
Several of the LGFlashTools were very close to working, but there were several issues:
1. I can't get it into Download Mode, as it gives a boot certification error.
2. There were some problems with the phone not showing up in Device Manager under "Ports" with COM41, and I thought I had largely resolved that issue. (Depending on the article I was looking at.)
3. Drivers, I'm not sure if they're an issue; I've downloaded several, and installed them, including 2.0 and a 3.1.
ADB does not recognize my device, as I've tried sideloading, although I can still drag and drop files. (I believe I pushed a file into the device early on and it worked though.)
4. Fastboot recognizes there's a device and can boot it via CMD but will not give a number when I use "fastboot devices". I've researched some flashing via Fastboot, and tried flashing the original KK .zip with it, but it said there wasn't enough space. I have about 14GB left on a 32GB device, however.
I hope I've provided enough information, because I've researched and tried so many ways to unbrick it, short of physically opening the phone as suggested here: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Any advice or suggestions would be greatly appreciated. I would love to know what I did wrong, because I know custom ROMs would be a great alternative to dealing with Lollipop until I can upgrade over a year from now.

I appear to be stuck, help me return to stock, please!

Hello XDA,
(TLDR - I've mucked things up and would like some help returning to stock, please! I can't enter download mode and am unsure how to work around this. I have access to TWRP and the phone shows up under adb devices. Phone does not show up under fastboot devices.)
Long version:
So I'm new to all of this and was trying to flash Cyanogenmod to my g2. I was following the instructions found on the cyanogen wiki (can't post links). I got to the bit where I was trying to sideload/push and install cyanogen when TWRP started to give me errors (error executing updater binary in zip cm 11, or something like that).
I did a bunch of googling, and after about an hour of not being able to find a solution, I decided to just return to stock for now. That proved problematic as well, unfortunately. I was following a guide found on droidviews (how to return lg g2 to stock firmware. can't post the link.) using the kdz method. I reached step 17 before I encountered a problem. When I enter download mode, I end up stuck on an updating firmware screen. I am unable to get past this and actually enter download mode. I'm unsure how to proceed at this point.
I have access to TWRP. The phone shows up under adb devices. The phone does NOT show up under fastboot devices. I can boot into download mode but not actually get past that updating firmware screen. I'm hoping there is an easy fix and I'm just being a bit of a derp, but I've been looking around for a while and am not sure how to proceed. Please advise!
Finally got everything to work by flashing a lollipop based rom. Just that i lost my contacts and sms.

Deleted the whole os

I recently formatted everything on my nexus 6 and I mean everything, the OS too. And I can't fix it, there was nothing on the forums or threads about this and how to fix it. Could you please help me?
Boot into the boatloader and flash the fastboot image.
Sent from my DROID Turbo 2
I have Ben an apple guy for 5 years just bought the nexus, I know how to get in to the boot loader but how do I flash the image? I tried downloading the image from the Google developers website but it said it failed ins
talling it!
Big-Blunt said:
I have Ben an apple guy for 5 years just bought the nexus, I know how to get in to the boot loader but how do I flash the image? I tried downloading the image from the Google developers website but it said it failed ins
talling it!
Click to expand...
Click to collapse
you cant use the flash-all, you need to flash each part separately. ynzip the file, then flash each .img file sepately. btw, ive deleted the whole os before. if you already have twrp installed, it wouls be a much easier fix using twrp instead.
How do I unzip the file in the boot loader?
Big-Blunt said:
How do I unzip the file in the boot loader?
Click to expand...
Click to collapse
i dont remember the program i used on my laptop, maybe 7zip.
The file downloaded from Google has a second zip inside. Unzip twice with 7 zip. The system image is inside the embedded zip file.
I assume you have the SDK from Google... Place all image files in the platform tools folder. I rename the images boot, radio, system, etc. to simplify typing the commands when actually flashing the images. DO NOT add the, " .IMG" when renaming.
Then:
Fastboot flash bootloader bootloader.IMG
Fastboot reboot-boitloader
Then same for system, radio, data and cache with out the reboot line.
When all files are flashed then fastboot reboot and enjoy
My brains are exploding rn, idk what or how to do anything, maybe u will think I'm dumb but I don't know what u guys are saying, could anyone post full instructions on how I would do it
The ONLY thing that you need to revive your device is alive bootloader. Every OS has its bootloader, and it determines what to load before system loaded.
I guess you did that foolish things on recovery. Then it won't kill itself of bootloader for sure.
Then there's always a chance. Try to boot into bootloader and switch it to fastboot mode.
Just flash stock rom image provided by google as described above.
You need to do some googling about fastboot and/or look for the beginners guide posted in the forums. You could use wugsfresh toolkit as well. I'm not being a douche not linking them,I'm to stoned
Google anything you don't understand
Sent from my Nexus 6 using Tapatalk
Do you know if your bootloader is unlocked?
You say you're an Apple guy - are you using a Mac? If you have access to a Windows machine I suggest you install Wugfresh's Nexus Root Toolkit and use the "Install & test drivers" button to set up the required drivers to connect your Nexus 6 to the computer. The walkthrough is comprehensive and extraordinarily simple - brilliant piece of programming. There is no Mac version.
Download the factory image (https://developers.google.com/android/nexus/images?hl=en#shamu image MMB29K).
Find the Fastboot/ADB programs on the web (I may have used the Minimal ADB & Fastboot tool, I can't remember exactly) and create a directory containing both programs plus their associated bits and pieces. I recommend making the path as simple as possible - e.g. C:\ADB for ease of navigation ( see below).
(While reading up on this, I came across this, which you may find useful - http://www.android.gs/install-set-up-adb-mac-os-x-linux/).
Unzip everything in the factory image, including the zip inside the zip as Larzzzz82 said, then copy the unzipped *.img files into the ADB Fastboot directory.
Boot your N6 into bootloader.
Open a CMD window and navigate to the ADB directory.
To check that you're connected, type (you don't need caps, this is just to make it clearer) FASTBOOT DEVICES. You should see something like "djdgkdjhgkdfj device" in response; if it's blank you're not connected - go through the driver setup again to see what you've missed.
Once you're successfully connected, you can install your new image following the instructions in this thread:
http://forum.xda-developers.com/google-nexus-5/help/stuck-launching-flashstock-bat-t3244470
I did ask for an expert to run a more experienced eye over them to correct any errors or to remove any pointless reboot commands, but nobody did either, so I guess they're ok. It's what I did and it worked for me. I've just noticed that it includes a line "fastboot flash recovery twrp.img" which you can ignore for the moment - though you may want to do this later when you have a working device.
Come back if you want any clarifications.
Happy new year (and, I hope, device...)
I tried I guess flashing the image through the recovery mode in the mount section but it said it failed,
Big-Blunt said:
I tried I guess flashing the image through the recovery mode in the mount section but it said it failed,
Click to expand...
Click to collapse
No no no you do not flash images through the recovery
Use Wugfresh's Nexus root and toolkit to restore it. Pretty easy.
@wolfen69 - duck and take cover...
I was going to suggest exactly that, since I'm a big fan of Wugfresh's NRT, but recommending it doesn't half bring down the flak... that's why I recommended using it initially at least to get the PC set up properly to connect and then get on with learning how to do it manually.
Personally in this situation using the NRT is exactly what I'd do myself. But now I'm retiring to my bunker for a while.
dahawthorne said:
@wolfen69 - duck and take cover...
I was going to suggest exactly that, since I'm a big fan of Wugfresh's NRT, but recommending it doesn't half bring down the flak... that's why I recommended using it initially at least to get the PC set up properly to connect and then get on with learning how to do it manually.
Personally in this situation using the NRT is exactly what I'd do myself. But now I'm retiring to my bunker for a while.
Click to expand...
Click to collapse
That's OK if people disagree with my recommendation. People are entitled to their opinions.
I tried for hours to do it the manual way and could never get it to work. And I'm a person who is VERY tech savvy. I had a computer repair business and have written advanced linux tutorials. I gave up and started using wugfresh. Has worked great for me. Others are free to do what works for them.
If you dont flash the images through the recovery mode then how do you flash it? I cant flash through command because the phone dosent have usb debugging enabled and its not in developer mode. I tried the nexus root toolkit as well and that didnt work either. Plz i need help!
So how much of my instruction did you follow? What exactly have you tried? Step by step. If you're vague then we can't help you. Error messages?
How did you delete the OS if your phone isn't unlocked?
Sent from my DROID Turbo 2
So i put it in recovery mode and when i tried resetting to factory i accidentally clicked advanced wipe and deleted everything so now its stuck in the boot loop. What i have tried was i downloaded the img file 6.0 shamu from googles site and drag and dropped on internal memory with my pc. Then in recovery mode i went mount and selected the img and it said error.

I simply cannot flash recovery

I nearly bricked my Razr i XT when downgrading from a Kitkat update to JB 4.1.2 but thanks to the great work here I am making some progress but cannot get Recovery or Root. the unlocking of bootloader via the Motorola website went fine and thanks to this post
http://forum.xda-developers.com/showthread.php?t=2239706 I got the rom I wanted, and it's fine.
I have read many other tutorials on installing a recovery and have downloaded and tried 6 or 7 CWM and TWRP images
but it never completes - fastboot says it has, but the phone stubbornly hangs at the flashing.
I have no problems getting into fastboot, but failed many times, and in desperation have tried with USB debugging on and off
and with and without sim and sdcard inserted.
attached are some photos to show where I am stuck at, and I would greatly appreciate some help
carkev said:
I nearly bricked my Razr i XT when downgrading from a Kitkat update to JB 4.1.2 but thanks to the great work here I am making some progress but cannot get Recovery or Root. the unlocking of bootloader via the Motorola website went fine and thanks to this post
http://forum.xda-developers.com/showthread.php?t=2239706 I got the rom I wanted, and it's fine.
I have read many other tutorials on installing a recovery and have downloaded and tried 6 or 7 CWM and TWRP images
but it never completes - fastboot says it has, but the phone stubbornly hangs at the flashing.
I have no problems getting into fastboot, but failed many times, and in desperation have tried with USB debugging on and off
and with and without sim and sdcard inserted.
attached are some photos to show where I am stuck at, and I would greatly appreciate some help
Click to expand...
Click to collapse
U said fastboot hangs at flashing the recovery, but on the command lines on your PC it says finished. Have u tried booting into recovery?
What recovery did u use and where did u get it?
USB debugging, simcard and sdcard don't have anything to do with fastboot. But it is likely that u didn't know that
thanks for looking at this.
I did try booting into recovery from my PC by after rebooting it and then taking the recovery option, but the phone hung at the Motorola bootloader unlocked warning screen.
this link was typical of the various tutorials I used: http://androidteen.com/motorola-razr-i-how-to-root-and-install-clockworkmod-cwm-recovery-on-android-4-1-2-jelly-bean-firmware/
to be fair I cannot recall where I got all the recovery images from - I have that many, and had to rename them recovery.img, so cannot remember the original download names
update:
I have just tried an app from the google play named Root Android, which advised trying other apps - Kingroot, Framaroot & Towelroot,
but they all failed .
what did catch my eye yesterday was the yellow text when in fastboot that says 'dismatched partition entry'
I ignored it as the img files I was trying to flash are all much smaller than the 100mb stated,
but today I am beginning to think that perhaps my recovery partition is corrupt and look for ways to repair it.
does that make any sense?
carkev said:
update:
I have just tried an app from the google play named Root Android, which advised trying other apps - Kingroot, Framaroot & Towelroot,
but they all failed .
what did catch my eye yesterday was the yellow text when in fastboot that says 'dismatched partition entry'
I ignored it as the img files I was trying to flash are all much smaller than the 100mb stated,
but today I am beginning to think that perhaps my recovery partition is corrupt and look for ways to repair it.
does that make any sense?
Click to expand...
Click to collapse
That could be it. Try flashing a rsd lite package from JB. Than go to the recovery and see if u have stock back.
Hazou said:
That could be it. Try flashing a rsd lite package from JB. Than go to the recovery and see if u have stock back.
Click to expand...
Click to collapse
thanks HazouPH, I'll give that a go
I have solved my problem with CWM:victory:
whilst I am not 100% certain I am pretty much sure it was a driver problem - for those who this may benefit, here is what I did.
1. I did not reflash my phone, but stayed with the one in my original post.
2. remember that the main problem was that Fastboot said I had succeeded in flashing a Recovery image, but that the phone 'hung'
at flash as in my photo. and then from my phone I could not get to recovery from the fastboot menu .
3. I stumbled across a posting (on XDA, but I cannot remember where) that said the Motorola drivers were not as good as they should be and that the Motohelper one's would be fine - so I downloaded them, and have attached the zip below.
4. I then decided to tidy up my PC and uninstalled all mobile phone drivers, plus any redundant USB Device drivers
5 for the USB tidying up I tend to use USBdview, which is superb and can be found here
6 when all this was done I simply tried the reflash of CWM - and got the same situation I had been having all along
but amazingly, when I selected 'recovery' it went in CWM - I nearly fainted with surprise!
from all this I can only assume it was a driver problem as I had changed nothing else.
perhaps it was Motohelper drivers- perhaps it was USBdview that did it for me - I will never really know, nor care!
I now have CWM v6.0.1.9 - it is touchscreen and permanent, plus I use the cute Reboot by app by Petrus to control my phone.
happy days!

Categories

Resources