Database Info

[Q] Bricked TF700 when trying to install TWRP

Current Status of my TF700:
-Boot looping with Asus "Inspiring Innovation - Persisten Perfection" logo. Approximately 5 seconds between reboots, with a vibrate every time it reboots.
-It says "Device is Unlocked" in the top left.
-Holding power for a long time (over 20s) will shut it off, and vibrate, but then it immediately vibrates again and resumes the bootloop.
-I cannot get it into the bootloader with Power + Vol Down. That combination does nothing.
-If I use the pinhole button, as long as I hold it, the screen remains blank. As soon as I release it again, the bootloop resumes immediately.
-It does not get to the second "shiny" Asus logo.
-It doesn't get far enough to recognize a new firmware file on the microSD card.
How I got to this point:
Stock ever since I bought it up until a few days ago. I decided it was time to root, unlock, install TWRP, and install CWM. I never got that far.
1. I unlocked first. I believe it was successful because it has said "Device is Unlocked" ever since.
2. I tried to root with the debugfs method. It reported it was successful, but despite several attempts, it was unsuccessful.
3. I tried using GooManager to install TWRP. It never worked.
4. I discovered that I wasn't running the latest Asus firmware. I then upgraded it. It ran successfully. (V10.6.1.14.10)
5. I tried rooting with Motochopper. It reported success. But it didn't work. I then discovered it wouldn't work with V10.6.1.14.10.
6. I then tried installing TWRP via fastboot. It reported success, but Power+VolDown didn't get me into TWRP. Nothing seemed to load TWRP. In case it's relevant, I was having trouble where Windows was saying there was a problem with the Bootloader Interface Driver, and after several reboots, I was able to get fastboot to reportedly load TWRP. It reported success, but I never saw TWRP.
7. I booted into Recovery, the latest version that said something to the effect of, "USB recovery loaded" or something, with 3 icons: RCK, Android, and Wipe Data. This is the only recovery I was ever able to see, by the way. I then selected "Wipe Data" hoping it would give me a new starting point.
Once it rebooted, it has been stuck in this bootloop. Have I royally screwed myself, or is there a way to recover?
Please ask any questions, I will answer them to the best of my ability. In the meantime, I will hope to run the power down on the tablet in the hopes it will make a difference.

blauciel said:
6. I then tried installing TWRP via fastboot. It reported success, but Power+VolDown didn't get me into TWRP.
....
7. I booted into Recovery, the latest version that said something to the effect of, "USB recovery loaded" or something, with 3 icons: RCK, Android, and Wipe Data. This is the only recovery I was ever able to see, by the way.
Click to expand...
Click to collapse
Power+VolDown activates the bootloader menu - this is the screen with the 3 icons, where you can use fastboot. Since you needed to go there to install TWRP via fastboot, you should have known that Power+VolDown doesn't get you into TWRP - you'd have to press VolUp in the bootloader menu, to activate RCK.
blauciel said:
I then selected "Wipe Data" hoping it would give me a new starting point.
Once it rebooted, it has been stuck in this bootloop. Have I royally screwed myself, or is there a way to recover?
Click to expand...
Click to collapse
Selecting "Wipe data" from the bootloader menu with a broken recovery is the best known way to brick a TF700. This can only be recovered via nvflash, which you can't use since you never got far enough to extract the required files from your tablet while it still worked. Your only option now is a new mainboard.

Well, crap. RCK never did anything except show a loading bar then reboot.
Thanks for the reply.
...from my phone...

Anyone know of a place that sells 64gb mainboards? Not finding anything thus far...
...from my phone...

in case anyone cares, I swapped the motherboard out with one from ebay, and it booted right up.

A handful of problems after performing a factory reset

Hi.
I installed some dodgy app which required root access to operate (but it didn't even though I allowed it in SuperSu) and this is where my problems started.
First of all, I noticed each and every app I tried to run would immediately crash. That included system apps, such as the Settings app. At that stage I was left with only the launcher working and attempts to uninstall apps would also cause a crash. Even the shutdown menu was broken and the phone hung up so I was forced to reboot it by holding the power button for 10 seconds.
After that, the phone would no longer be able to boot, it was stuck in a boot loop, but recovery still worked (TWRP for that matter) so firstly I wiped the cache partitions (including dalvik cache) but that didn't help, as the phone still wouldn't boot. In this case there was only one thing left for me to try and that was the factory reset capability of TWRP which claimed to not even touch internal storage so I was fine with that and did the wipe.
Thankfully, the phone booted afterwards and it welcomed me with the first startup guide (the language selection dialog was really buggy but that's Huawei's fault) and the phone was seemingly ok, except that the whole internal storage had been wiped out but not only that - the external microsd card was empty as well! Could you believe that? I couldn't. TWRP promised not to touch internal storage and the external memory card wasn't even mentioned but why would it wipe it anyway?
That's for the story behind it, now for the actual problems I'm facing right now:
The stock remote app is gone
The boot animation has changed to a different one (now it's a silver "android" logo instead of the "honor" logo)
Battery usage stats are not available (see: http://i.cubeupload.com/BXCknW.png)
Sound quality from the built-in speaker seems noticeably worse
Hereby, I'm asking you guys to help me out with all of this.
The "remote app missing" problem could be solved by someone sharing their apk file with me, that's probably the simplest one to fix.
As for the boot animation, I have no clue as I don't even know what files are responsible for that.
The same for the battery stats problem, I'm already through a couple of full-charge-to-discharge cycles as well as wiping the cache partition, but the problem remains.
The sound quality probably has to do with the DTS sound enhancer. The config file for that is either "/cust/unicom/cn/xml/dolby_config.xml" or "/cust/unicomelectric/cn/xml/dolby_config.xml" and I'm asking you to upload these files somewhere so I can compare them with mine to see if anything is different.
The device I'm using is the H60-L02 variant running the B532 ROM.

Does the 3 buttons method erase internal storage as well? I've already set up quite some apps and having to do it again wouldn't be the most pleasant surprise. But at least in this case I could make some backups and whatnot...
Also, would it work if I flashed B535 straight away or does the 3 buttons method expect the same version which is already installed, in this case B532?

pudup said:
It will wipe internal storage. You can flash any *full* ROM as long as you're not moving up or down from kitkat-lolipop/marshmallow.
Click to expand...
Click to collapse
Okay, so I decided I'd do the whole thing today. I downloaded the full B535 ROM on my PC, backed up all the stuff I care about from the phone to the PC as well, and also I downloaded the MultiTool.
Though the MultiTool thread says this in bold red:
VirusPlus said:
EMUI 3.1 WARNING! Update over rooted or system modded in EMUI 3.1 gives a BRICK.
You have to restore system and REMOVE root before every update in EMUI 3.1 for now.
Click to expand...
Click to collapse
So I also fired up Titanium Backup in order to defrost all the frozen apps, which went fine, and then I wanted to unroot the phone but I've been unable to do so so far.
To unroot, I launch the SuperSU app, navigate to the "Settings" tab and select "Full unroot". The problem being, it just gets stuck on the screen saying "Uninstalling, please wait...". I don't know how long it usually takes to complete, so far I've waited for maybe 10 minutes and nothing seems to change. Should I care about that? Is that warning about updating rooted/modified EMUI 3.1 resulting in a brick still true?
Can I skip this step and just flash the stock recovery followed by the 3 buttons method?
EDIT:
After some trial and error with the multi tool and different recoveries, I was able to finally unroot. Next, I flashed the stock recovery for B532 and attempted to do the 3 buttons method, but it would say "Install failed. The update package does not exist" (could be because I'm doing the update from a USB flash drive as I don't have an micro sd card big enough to fit the package). So I rebooted the phone into system and used the Updater to perfrom a local update where it would let me pick the USB drive. It completed without errors and then rebooted into some kind of updater (black background and some bluish emui colors) where it also took some time to finish thankfully successfully. I can right now see the phone booting and for what it's worth, the boot animation is once again the good old "honor" logo and not that ugly silvery "android" one
And now it's "Optimizing system...". I really hope it finsishes successfully as it's already a bit late here and I wouldn't like the phone to be unusable tomorrow :laugh:
36% ready...
46% it's kind of fun to watch this, and now 49%
I'd like to thank @pudup once more for helping out, I'm not really that much into flashing recoveries, roms and all that myself. Without your help I would probably be too scared to try doing something on my own :crying:
86%, 89%, 95% and 100%. Aww, what a relief Good old stock lock screen and wallpaper.

[Solved] Sometimes stuck on bootscreen can't even powerdown! LOS 14.1

Hi,
since my old M7 is having more and more annoying issues, I tried to move to a One A9.
The problem:
The phone gets stcuk on LOS boot screen. Looks like it's loading but it never finishes and I can't even turn it off by holding power button pressed for 10s, 1m or even 10m!
BUT this happens only sometimes! Last night I just left it in this state to get the battery empty and this morning it was turned off. "On the way" to recovery (TWRP 3.1.1) I pressed the wrong button and it rebooted. Without any issues! Used it all day until I wanted to reboot it to insert a microSD-card. Since then: stuck on bootscreen! Can't get out...
Any ideas?
What I did:
Unlocked the phone
Factory reset
Installed TWRP
Flashed LOS 14.1
Flashed Magisk 14.0
Help appreciated

Somehow I'd consider this thread as solved:
I went back into TWRP and:
- formatted DATA
- made a full wipe
- made another full wipe
Now suddenly I don't get neither bootloops nor "Can't mount" errors in recovery (which I forgot to mention in the opening post :silly
I write "somehow" since I have formatted DATA before, as well as made a full wipe, because I couldn't even install LOS before that

Lost WiFi and other features after switching from Slot B to Slot A

I am running stock ROM and have bootloader unlocked and TWRP already installed. The phone was rooted without problems. I was getting an error from Super SU, so I looked up how to fix it online and the suggestion was to install an older version and then try to upgrade it. It was hard to find a zip from a legitimate source but once I found it, TWRP did not show the directory I was looking for (this was previously available when I rooted it). This is where I did something stupid and looked around in the settings and found the Slot A / Slot B option. I switched from B to A and the phone got stuck on the boot animation for several minutes after rebooting. I decided to reboot into TWRP and switched the slot back to B. This brought the phone back but WiFi is off by default and whenever I try to turn it on, it doesn't change.
I have seen a couple of other people mention similar issues about losing wifi after a root or changing the slot. What's the fix? I am wondering if there is anything else "broken" after the slot change and if I should do a factory reset (I would hate to do that as I was almost finished setting up this device). I have also received the error message saying "Process System isn't responding" in the settings menu a few times. It also seems like the finger print scanner isn't recognizing fingerprints any more and face unlock isn't working

One possibility is, that SuperSU isn't that compatible anymore. Magisk does a wonderful job and no problems so far. Maybe you should give it a try and switch from using SuperSU to Magisk.

shagexpert said:
I am running stock ROM and have bootloader unlocked and TWRP already installed. The phone was rooted without problems. I was getting an error from Super SU, so I looked up how to fix it online and the suggestion was to install an older version and then try to upgrade it. It was hard to find a zip from a legitimate source but once I found it, TWRP did not show the directory I was looking for (this was previously available when I rooted it). This is where I did something stupid and looked around in the settings and found the Slot A / Slot B option. I switched from B to A and the phone got stuck on the boot animation for several minutes after rebooting. I decided to reboot into TWRP and switched the slot back to B. This brought the phone back but WiFi is off by default and whenever I try to turn it on, it doesn't change.
I have seen a couple of other people mention similar issues about losing wifi after a root or changing the slot. What's the fix? I am wondering if there is anything else "broken" after the slot change and if I should do a factory reset (I would hate to do that as I was almost finished setting up this device). I have also received the error message saying "Process System isn't responding" in the settings menu a few times. It also seems like the finger print scanner isn't recognizing fingerprints any more and face unlock isn't working
Click to expand...
Click to collapse
I had the same issue when I first got my 6 when I was playing around with the slots. Also my original TWRP install for some reason would crash and reboot whenever I plugged in the data cable while in TWRP. I ended up flashing back to stock OOS 5.1.5 through fastboot (used the flash-all command) and then reinstalled TWRP and everything has been working great since then.

MickyFoley said:
One possibility is, that SuperSU isn't that compatible anymore. Magisk does a wonderful job and no problems so far. Maybe you should give it a try and switch from using SuperSU to Magisk.
Click to expand...
Click to collapse
The instructions I followed already installed Magisk to the phone. I wanted Super SU because some of the other chainfire apps like Liveboot and rooted apps like Titanium backup said Super SU is needed (Titanium said Magisk will work but may not be reliable for some newer versions of the ROM). I can live without liveboot but really need Titanium to reliably transfer data from my older phone.
To be honest I didn't know they did the same thing (magisk and Super SU). I am curious now, what if I factory reset my phone and attempted to install Super SU instead of Magisk this time?
If I do a factory reset (let's say I want it just like it was out of the box and I format the data partition as well), will I need to root the phone again? I am asking because I don't know which part of the instructions I should ignore. I am sure TWRP will already be installed after the reset so I would only need to install the extra apps...

You don't have to format data. Just factory reset it. Then use "fastboot boot twrp.img", don't allow modifications, flash a kernel you want (if you want one - I really recommend ElementalX) and then the latest version of Magisk (16.4 BETA currently). Did so - all fine. And yes: Even Titanium Backup works without any issue with Magisk.

We had similar problems with TWRP on the Razer Phone when it was new. We solved the problem by using the TWRP boot image to flash the stock boot image and then flashing a TWRP zip. I just got the OnePlus 6 yesterday and haven't really messed with it yet but everything sounds the same to me so far.

I read more about TWRP and realized what I was doing wrong when the directory with zip files wasn't showing up. When TWRP showed up I was supposed type in my regular unlock password to decrypt storage. When I did that the folder I was looking for showed up. I made a backup through recovery (which took like an hour, may be because the external flash drive I attached was really slow - and the size of the backup was about 12GB). After that I installed the zip file for Super SU, just to see if it worked - it showed the installation was successful but the app was still missing from the app drawer. Now I wanted to factory reset the device and start over.
I went into wipe and there was nothing listed under the wipe screen. I went into Advanced wipe and wiped whatever was selected by default. The selected items were Dalvik / ART Cache, System, Data. There was also "Internal Storage and USB Storage" that wasn't selected.
I swiped to wipe, it wiped everything. Then asked reboot, I rebooted, got a blank screen with white LED for a long time. When I plugged it into the computer it recognized the device as Qualcomm HS-USB Diagnostics 900E (COM4). I rebooted it by holding Power + Volume Up + Volume Down. I tried to boot into boot loader next. This brought me to another blank screen. The computer still makes a noise when it reboots but screen stays black. The only message that shows up is the one saying boot loader is unlocked. Did I brick my phone? This keeps getting progressively worse.

shagexpert said:
I read more about TWRP and realized what I was doing wrong when the directory with zip files wasn't showing up. When TWRP showed up I was supposed type in my regular unlock password to decrypt storage. When I did that the folder I was looking for showed up. I made a backup through recovery (which took like an hour, may be because the external flash drive I attached was really slow - and the size of the backup was about 12GB). After that I installed the zip file for Super SU, just to see if it worked - it showed the installation was successful but the app was still missing from the app drawer. Now I wanted to factory reset the device and start over.
I went into wipe and there was nothing listed under the wipe screen. I went into Advanced wipe and wiped whatever was selected by default. The selected items were Dalvik / ART Cache, System, Data. There was also "Internal Storage and USB Storage" that wasn't selected.
I swiped to wipe, it wiped everything. Then asked reboot, I rebooted, got a blank screen with white LED for a long time. When I plugged it into the computer it recognized the device as Qualcomm HS-USB Diagnostics 900E (COM4). I rebooted it by holding Power + Volume Up + Volume Down. I tried to boot into boot loader next. This brought me to another blank screen. The computer still makes a noise when it reboots but screen stays black. The only message that shows up is the one saying boot loader is unlocked. Did I brick my phone? This keeps getting progressively worse.
Click to expand...
Click to collapse
OK good news! I tried one more time and fast boot showed up. I was able to get into recovery. I have the backup so I will try to restore that. I don't know what to do after that. I am thinking wiping without getting into advanced mode.

shagexpert said:
OK good news! I tried one more time and fast boot showed up. I was able to get into recovery. I have the backup so I will try to restore that. I don't know what to do after that. I am thinking wiping without getting into advanced mode.
Click to expand...
Click to collapse
When your phone booted straight into that mode with black screen and the led, then you bricked it. Same happened to me 2 days ago. The solution was to use the Msmtool from another thread and it worked great. Just follow the guide. But it will wipe your device. And you have to install oxygenos manually via "local upgrade". If you have a question, just ask

What I ended up doing was restoring from the backup I had. This was the "bad backup" without WiFi and broken finger print and facial recognition. After the restore, I did a normal wipe (not advanced). This reset the phone to factory settings. Once I configured WiFi and signed into my Google account, Google offered to recover from a cloud backup of my One Plus - I didn't know Google made these backups. It downloaded all the apps automatically. I don't know yet if I have sign into all of them all over again.
The bad back up saved my ass, I wasn't even planning on making it. I was just testing the backup feature. That's why you should always do a backup, even if the device isn't in ideal configuration.

shagexpert said:
The instructions I followed already installed Magisk to the phone. I wanted Super SU because some of the other chainfire apps like Liveboot and rooted apps like Titanium backup said Super SU is needed (Titanium said Magisk will work but may not be reliable for some newer versions of the ROM). I can live without liveboot but really need Titanium to reliably transfer data from my older phone.
Click to expand...
Click to collapse
I rooted my phone with Magisk and installed the 5.1.6 via OTA (and reroot via installed Magisk Manager). So no need to install TWRP so far.
Titanium Backup runs flawlessly with Magisk (already on my OP 3T and my OP 5).
So give Magisk a try, I never had such an easy and reliable update as the one from 5.1.5 to 5.1.6

Helium is a great alternative to titanium.

Oppo R7S - ROM installation crashed, cannot get back to recovery mode, keeps crashing

Hi there,
I am a newbie and hoping that someone could help to give me some clear pointers about options that i could take to rescue my phone - I hope its not bricked.
I was attempting to install LineageOS 16 on my Oppo R7s. This is my second attempt at installing a ROM - I did it a couple of weeks ago with Project Spectrum, and it worked, but Project Spectrum didn't impress me, so i wanted to try lineage OS instead).
I entered developer mode and enabled USB debugging
I downloaded the LineageOS zip to my SD card, as well as a Google Apps zip.
I downloaded the TWRP app on my phone just in case it was needed, however I've never used that app and not 100% sure how to use it.
I rebooted in recovery mode, and tried to install from the LineageOS zip file. It didn't start installing, I got some error message which I cannot recall... so I tried wiping the application data first, to see if that would help (maybe that was my mistake??)
I then went back to the install menu, and tried to install the Google Apps package first.... it started downloading, but then crashed and black screened.
Now, when I try to power on the phone, I get the oppo logo, and then it briefly goes back to the install screen for a second, with a message on the screen saying: "updating please wait, do not remove battery, do not co other operations" - but this only lasts for a second, then it crashes.
When I try to reboot into recovery mode (Power key +volume down), it does the same thing. I cannot get back to the white recovery menu.
Is there any way that I can rescue the situation and get back into recovery mode to try again? Or get back to a functioning USB connection so I can load a new ROM zip to try that instead?
When I plug it into the power, I get no indication that the phone is charging.
I'm worried the battery will go flat.
I have ADB installed on my computer, but I dont really know how to use it - the only command I know is "adb push" to load the roms onto the SD Card
Any advice on how to get access again would be greatly appreciated!