Database Info

Broken CWM

I have flashed the CWM from TF201 by accident. Now the tablet is stuck in that CWM mode. I can't connect to usb using adb mode. Power+volume down does not work anymore. Any way I can reflash the correct CWM?
THanks

If you can boot to OS - you can use fastboot to flash any recovery.. or flash TWRP from goomanager.
upd: sry..don't see about "stuck".

abe_cedar said:
I have flashed the CWM from TF201 by accident. Now the tablet is stuck in that CWM mode. I can't connect to usb using adb mode. Power+volume down does not work anymore. Any way I can reflash the correct CWM?
THanks
Click to expand...
Click to collapse
I have made the same mistake. Although I can get the device to fastboot USB mode. I have tried to use CWM with the restore I made before I put in Cyanogenmod 9, as well as putting on the Cyanogenmod experimental #2 for TF300. No error messages at all and it wipes data and cash without any problems.
But I get locked on the Asus boot screen and it does not continue ie I am stuck as well.
I have as well tried to use the TWRP 2.1.5. I get the Teamwin loggo screen, it wipes all the data and verifies all the filesystems and reboots. Still stuck.
Is the device bricked ?
upd:The TF300 can not be shutoff either. When you hold the power button the screen goes black, but after ~5 s the device is starting again and is still stuck on the Asus bootup screen.

if you reboot it holding vol down and power, can you get back into the boot menu, to reselect fastboot?
if holding the power button doesn't switch it off, what happens if you leave it to run out of batteries then do this?
then you can flash the correct recovery.img

cheedear said:
if you reboot it holding vol down and power, can you get back into the boot menu, to reselect fastboot?
if holding the power button doesn't switch it off, what happens if you leave it to run out of batteries then do this?
then you can flash the correct recovery.img
Click to expand...
Click to collapse
Yes, I can get access to the fastboot and I have already tried to flash with the recovery.img. I have as well let the battery run out and tried it once more with the same result.
Still stuck on the asus bootup screen.

power
Hare,
I have same problem.tab cannot power off. Just reboots into cwm.
I was thinking to drain bat. Thanks for sharing that info.

There are a lot of topics about people who broke their devices with TF201's recovery.
Afaik, no one recovered it. Send to Asus.

So the device is bricked then :'(.
Thanks for clearing it up.
Sent from my GT-I9100 using XDA

RMA..
Guillaume,
Thanks for clarification.
I have read that ASUS wants 700USD for replacing/reflashing the bootloader. That was for the tf201. Any way to nvflash it back to factory? I don't believe that they have to change the MB.
I have no warranty left, but I don't want to be gouged by them either.
Any thoughts, info?

Hi,
I've do the same mistake, but I can use adb.
Do youhave any news about our problem?
Thanks
Midyr

unable to power off
My issue is that I have the CWM for the tf201. I did the update from the CWM app in Android. Bad idea. So now the tab does not power off s.t. I can get into the power+vol down mode. Adb does not work since I cannot ( don't know how) to make it go into the usb debugging mode. I have tried several things none of which have worked. Still stuck.
I wanted some feedback for a RMA from ASUS, posted it here but sor far no answers.

Not sure if it would really work, but on my Evo, I don't have to completely power off the phone to do the recovery sequence. I can do it during a normal reboot. There is a point just before the device starts booting again where it is technically "off", and if I hold volume down (don't even have to hold power on my Evo; volume down seems to be the only necessary button) starting at this point, the phone will boot into the bootloader.
So, next time the device reboots, just start holding volume down (possibly power also, just in case) at the "off" point.

[Help] Bricked my Nexus what's next? :(

Hi, this situation is kind of strange and I hope it's just the battery and not the whole goddamn phone.
What I'm dealing with at the moment is:
The phone doesn't boot
When plugged onto charger or USB cable it boots but stuck at Google logo after a blink and stays there. Also, Home, Back and other buttons are lighten.
When "forcefully" put into fastboot mode, e.g. after plugging it onto USB and instantly pressing Vol Up + Power it stuck there as well, volume rocker no more response neither does the power button. Also, I notice there are no commands at the end like "USB int" etc we see normally.
Fastboot or ADB returns no device found
Please help. I personally believe it could be due to battery, what do you guys think?
Thank you.

As long as you can see the google logo, your device is not bricked. GIve more useful information; like your computer operating system, the last thing you did before this happened, etc.

ej8989 said:
As long as you can see the google logo, your device is not bricked. GIve more useful information; like your computer operating system, the last thing you did before this happened, etc.
Click to expand...
Click to collapse
Thanks. My OS is Windows 8.1 Update 1. The last thing was to install UPDATE-SuperSU to root so that I can install ROM Manager to update Recovery but the installation was aborted so I attempt to flash it via Fastboot with success. Then, wanted to install SlimKat but it couldn't let me mount USB storage so that I can put the .zip file. I, then stupidly click on install via ADB but didn't know how to go back so I pulled the battery and powered up; used ADP push command to transfer said the file, but again for some reason I had to pull the battery and since then I am in above position.
Sent from my XT1032 using Tapatalk

Put the device in bootloader and plug it into the computer, be patient, my phone is rather slow to get detected sometimes.. (Up to 30 min.) Check your drivers on the computer, try rebooting the boot loader from just pressing the power button (while in boot loader mode)..
If all else fails, read up on Wugs NRTK page and about ODIN...
Sent from my Nexus S using XDA Premium 4 mobile app

Setting.Out said:
Put the device in bootloader and plug it into the computer, be patient, my phone is rather slow to get detected sometimes.. (Up to 30 min.) Check your drivers on the computer, try rebooting the boot loader from just pressing the power button (while in boot loader mode)..
If all else fails, read up on Wugs NRTK page and about ODIN...
Sent from my Nexus S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, device doesn't go into bootloader without plugging it to computer (I've to press required buttons BEFORE plugging OTG cable). And when it boots in fastboot mode it doesn't let me press any button either. I kept it plugged in for sometime as well when it when it was at Google logo; will try to do the same while in fastboot mode too and let you know. As for drivers, same computer was used before when it was working and it detected just fine immediately (gave me a pain to find the right drivers though - PDANet was a life saver).
EDIT:
I should mention that I broke the OS before this happened by formatting /system folder and wiping other data from CWM recovery - I think, I also rebooted it without flashing the ROM as well.

BaghiXDA said:
Hi, device doesn't go into bootloader without plugging it to computer (I've to press required buttons BEFORE plugging OTG cable). And when it boots in fastboot mode it doesn't let me press any button either. I kept it plugged in for sometime as well when it when it was at Google logo; will try to do the same while in fastboot mode too and let you know. As for drivers, same computer was used before when it was working and it detected just fine immediately (gave me a pain to find the right drivers though - PDANet was a life saver).
EDIT:
I should mention that I broke the OS before this happened by formatting /system folder and wiping other data from CWM recovery - I think, I also rebooted it without flashing the ROM as well.
Click to expand...
Click to collapse
I recently had to update my drivers on my computer.. after it did an update, my phone wasn't recognized..
Try Wugs Nexus Root Toolkit,.. use the options for "bricked".. do this from the bootloader screen (power/volume +)...
I don't have experience with ODIN, so you'll need to read that forum/threads...

Setting.Out said:
I recently had to update my drivers on my computer.. after it did an update, my phone wasn't recognized..
Try Wugs Nexus Root Toolkit,.. use the options for "bricked".. do this from the bootloader screen (power/volume +)...
I don't have experience with ODIN, so you'll need to read that forum/threads...
Click to expand...
Click to collapse
The problem is, even the Toolkit doesn't recognize the device no matter what. Even the keys for ODIN don't work, aren't they Home+VOL+ and Power?
EDIT1:
Kept plugged in for little longer as suggested but it heats up (it's too hot here) so I plugged out. Going to be running it off of Linux and lets see how it goes. :fingers-crossed:
EDIT2:
Tried Adam's UnBrickable method on Linux and even that couldn't find device. But that was to be expected since Adam clearly mentioned in his post that this tool isn't for those who see anything on their screen.

Whelp! Currently I can only see I:\ drive in device manager and that's all under portable devices and that's all. I see the same even in BIOS boot options, it's listed as "Google".

Guess need to close this thread now.

Problems with my d6633 Z3 Dual

Hallo people,
I have a very big problem with my d6633. I installed tonight TWRP - so fas, so good. After installing TWRP asked me to root the device, I said YES. My bootloader was unlocked. Then I couldn't exit TWRP. After every reboot the device started into TWRP. Now I can not start the device. I tried with Power+ Volume+, reset button - nothing.
Any suggestions?
Thanks for your help.

mazagi said:
Hallo people,
I have a very big problem with my d6633. I installed tonight TWRP - so fas, so good. After installing TWRP asked me to root the device, I said YES. My bootloader was unlocked. Then I couldn't exit TWRP. After every reboot the device started into TWRP. Now I can not start the device. I tried with Power+ Volume+, reset button - nothing.
Any suggestions?
Thanks for your help.
Click to expand...
Click to collapse
Use flashtool go back stock, after flash twrp, flash supersu manually, don't let twrp install for you

yuzhengwen said:
Use flashtool go back stock, after flash twrp, flash supersu manually, don't let twrp install for you
Click to expand...
Click to collapse
How can I do that? There is no power on my device. And I think I cannot charge it...

mazagi said:
How can I do that? There is no power on my device. And I think I cannot charge it...
Click to expand...
Click to collapse
Google using flashtool to flash stock firmware

yuzhengwen said:
Google using flashtool to flash stock firmware
Click to expand...
Click to collapse
No chance. The device will not be detected. I can not charge it.

mazagi said:
No chance. The device will not be detected. I can not charge it.
Click to expand...
Click to collapse
How much % did it have before you started the procedure?
Did you try holding down vol+ and then plugging it into USB?

Hello Jkay7,
Thanks for your support. My solution was to leave the device switched off over the night. Connected via original cable. Today in the morning my dyouzhengwen evice was detected via flash tool and as youzhengwen suggested I could flash the original ftf file.

artusk01 said:
Hello Jkay7,
Thanks for your support. My solution was to leave the device switched off over the night. Connected via original cable. Today in the morning my dyouzhengwen evice was detected via flash tool and as youzhengwen suggested I could flash the original ftf file.
Click to expand...
Click to collapse
Nice to hear that!

Any help would be appreciated
Sony Xperia Z3 Dual D6633
I have tried just about every method seen. My problem with the flashtool or PC companion is that the phone is recognized by the computer but I can only start to turn the device on which I don't believe it actually boots. Broken display and new display does not power on.
Or it connects in fastboot by holding volume up when connecting. This shows a blue led.
But trying to connect in flash mode by holding power down just makes the led flash red then green continuously.
And for the pc companion it always says the connection was unsuccessful once the led turns green on the device.
I got the phone for only $40 in this condition. So I cannot say what entirely was wrong or what it's last working state was.
I bought a new screen and power flex cable. As well as a back plate and tempered glass protectors. I was going to wait until everything works perfect speakers and all before I sealed it tight with water proof adhesive stickers.
Even before I bought the new power flex the computer recognized it and the battery health and charge %. The battery was able to charge. But I couldn't turn the device on.
The computer confirmed that it had been at 29% after some time charging and then 100% after leaving it on charge.
Now with the new screen and power cable the phone still does nothing if not plugged it. The light was red at first, but then yellow, then after some time green when the battery fully charged. This was again even before the new parts.
I have to plug it in to try anything.
It goes red then starts to turn on and turns green.
But I hear no sound, get no vibrations, the computer only sees it as the phone and shows absolutely nothing on the removable disk. Just blank when I click on the drive volume. But it is seen as an Xperia D6633 phone or fastboot Android device.
I've tried the reset button, holding power and volume up, volume down, all three. Tried my factory cable. Different cables, different ports, uninstalling it from service manager and letting the flash tool recognize and install it.
I also tried the new display on the old power flex and the old display on the new power flex.
Nothing changed, no vibrations, no sounds, system never actually fully starts as far as I can tell, and cannot connect in flash mode only fast boot. And the flashable file is only seen in flash mode. Fastboot can only see the folder but it is ready to flash files as far as I can tell.

@xdathekilljoy
That's a lot of money you're putting into an (apparently) broken phone Brave!
Okay so what happens if you hold Vol+ while it's shut down and then connect it to USB, the LED turns blue, right?
So why does flashing it from there on not work?

Jkay7 said:
@xdathekilljoy
That's a lot of money you're putting into an (apparently) broken phone Brave!
Okay so what happens if you hold Vol+ while it's shut down and then connect it to USB, the LED turns blue, right?
So why does flashing it from there on not work?
Click to expand...
Click to collapse
Well it didn't seem that broken at first and both it and the display were only about 37 piece. Power flex was almost 10. Seemed like a rightful price.
Yes the led turns blue and it is in fastboot mode. The flash file seems to only be readable for flashing in flash mode "volume down". I can see the folder of the flash file in fastboot mode " volume up ", but not in a flashable format.
And when connecting " volume down " it fails a connection while the led just flashes green to red to green to red continually

Two updates
1. I thought I should mention that when I do plug the phone in to a charger or computer the top does get a bit warm or hot as well as the led turns on. Different color depending.
2. With much fiddling and trying if holding the volume down button for different lengths of time while connecting up a computer I finally got it to connect in flash mode and flashed a file...... No change.
At this point maybe I should try a new battery for the hell of it even though this one seems to be working.
Or there is a minute hardware damage somewhere. Maybe the power ic? Or s capacitor?

Cannot Enter Bootloader or Use Volume Up.

Hello Guys,
My OnePlus One screen broke, it was in my drawer for more than 15 days without charge, i connected charger for 1 hour it just went from 1% to 5% but i didnt thought much about it as my priority was to change screen, i bought touch+lcd with frame and replaced it myself, but it wasnt powering up then i tried putting the backpanel on, it then booted up to the home screen, but the battery indicator wasnt moving up i powered off the phone after that it never turned on, i researched a bit and found out the after long period of time if you dont charge your phone might have problem charging and there was one suggestion which i followed and that was charge OPO using usb cable attached to PC, i left it for somewhat 7hours and it powered on i thought it might be the problem of ROM i flashed official H2OS (regret selecting this rom) using TWRP, it was a catastrophe my phone wont Enter Bootloader or Recovery, and wont even boot to system, it seemed i hardbricked my device, i used Oneplus one recovery tool 64GB to bring my device to life but after that no matter what i do my device wont enter to bootloader as the volume up button stopped working too : tried advance reboot, powerup+volumeup, opo toolkit.
Help me, i want to root my device and unlock bootloader once again.

Pra7ul said:
Hello Guys,
My OnePlus One screen broke, it was in my drawer for more than 15 days without charge, i connected charger for 1 hour it just went from 1% to 5% but i didnt thought much about it as my priority was to change screen, i bought touch+lcd with frame and replaced it myself, but it wasnt powering up then i tried putting the backpanel on, it then booted up to the home screen, but the battery indicator wasnt moving up i powered off the phone after that it never turned on, i researched a bit and found out the after long period of time if you dont charge your phone might have problem charging and there was one suggestion which i followed and that was charge OPO using usb cable attached to PC, i left it for somewhat 7hours and it powered on i thought it might be the problem of ROM i flashed official H2OS (regret selecting this rom) using TWRP, it was a catastrophe my phone wont Enter Bootloader or Recovery, and wont even boot to system, it seemed i hardbricked my device, i used Oneplus one recovery tool 64GB to bring my device to life but after that no matter what i do my device wont enter to bootloader as the volume up button stopped working too : tried advance reboot, powerup+volumeup, opo toolkit.
Help me, i want to root my device and unlock bootloader once again.
Click to expand...
Click to collapse
adb reboot bootloader

waterdaan said:
adb reboot bootloader
Click to expand...
Click to collapse
That Just Reboots it to system, i have turned adb on and clicked on trust this connection i have checked adb devices, and it shows attached devices too,
it just wont reboot to bootloader, but i can enter recovery. Help Please.

Pra7ul said:
That Just Reboots it to system, i have turned adb on and clicked on trust this connection i have checked adb devices, and it shows attached devices too,
it just wont reboot to bootloader, but i can enter recovery. Help Please.
Click to expand...
Click to collapse
Is your volume up button actually broken or does it still work and can you boot into something? If it still works (hold on, this idea might be a little crazy xD) you could try completely hard bricking (no joke! you cannot get into Qualcomm download mode with a booting device) and restoring it with the msm8974downloadtool from the oneplus one unbricking guide which should theoretically fix everything that is wrong.

noahvt said:
Is your volume up button actually broken or does it still work and can you boot into something? If it still works (hold on, this idea might be a little crazy xD) you could try completely hard bricking (no joke! you cannot get into Qualcomm download mode with a booting device) and restoring it with the msm8974downloadtool from the oneplus one unbricking guide which should theoretically fix everything that is wrong.
Click to expand...
Click to collapse
Even If my volume button dosent work then why wont it enter bootloader via advance reboot it just restarts to system after selecting reboot to bootloader,so i should hard brick my device once again, P.S. i have done that twice before though.

I broke mit Pixel 3 !?

Hello,
I've rooted my Pixel 3 as described here in the forum.
Everything went well and I was booting in TWRP without any problems; Bootloader is still unlocked. I didn't installed a custom ROM or anything else. After I've selcted "restore backup" my backup (which I've made before with TWRP) my phone is now messed up:
It's starting in Bootloader (Warning Screen for unlocked Bootloader) and than is switching on an white screen with Google logo for ca. 3-4 sec. and than it's jumping back into the Bootloader in an endless Loop.
Any idea what I can do to rescue my phone?
Thanks, Mags

MMoes said:
Hello,
I've rooted my Pixel 3 as described here in the forum.
Everything went well and I was booting in TWRP without any problems; Bootloader is still unlocked. I didn't installed a custom ROM or anything else. After I've selcted "restore backup" my backup (which I've made before with TWRP) my phone is now messed up:
It's starting in Bootloader (Warning Screen for unlocked Bootloader) and than is switching on an white screen with Google logo for ca. 3-4 sec. and than it's jumping back into the Bootloader in an endless Loop.
Any idea what I can do to rescue my phone?
Thanks, Mags
Click to expand...
Click to collapse
In bootloader mode can you get your computer to recognize the phone. If so, download the latest update from Google website and install using adb. This will wipe the phone but will get it restored. I've had to do this in my pixel 2 before. I don't have the pixel 3 yet as I just ordered it today.

MMoes said:
Hello,
I've rooted my Pixel 3 as described here in the forum.
Everything went well and I was booting in TWRP without any problems; Bootloader is still unlocked. I didn't installed a custom ROM or anything else. After I've selcted "restore backup" my backup (which I've made before with TWRP) my phone is now messed up:
It's starting in Bootloader (Warning Screen for unlocked Bootloader) and than is switching on an white screen with Google logo for ca. 3-4 sec. and than it's jumping back into the Bootloader in an endless Loop.
Any idea what I can do to rescue my phone?
Thanks, Mags
Click to expand...
Click to collapse
FilthyFord said:
In bootloader mode can you get your computer to recognize the phone. If so, download the latest update from Google website and install using adb. This will wipe the phone but will get it restored. I've had to do this in my pixel 2 before. I don't have the pixel 3 yet as I just ordered it today.
Click to expand...
Click to collapse
You can also edit the flash-all file to remove the -w and not completely wipe your phone. This way, your data will remain and it still resets the important factory stuff.

FilthyFord said:
In bootloader mode can you get your computer to recognize the phone. If so, download the latest update from Google website and install using adb. This will wipe the phone but will get it restored. I've had to do this in my pixel 2 before. I don't have the pixel 3 yet as I just ordered it today.
Click to expand...
Click to collapse
Thanks, I‘ve tried with adb devices & no device found. So obviously my computer doesn‘t recognize the Pixel

sliding_billy said:
You can also edit the flash-all file to remove the -w and not completely wipe your phone. This way, your data will remain and it still resets the important factory stuff.
Click to expand...
Click to collapse
Thanks. Loosing my data isn‘t the Problem. Actually I‘m even not able to connect to the phone and flash anything.

MMoes said:
Thanks. Loosing my data isn‘t the Problem. Actually I‘m even not able to connect to the phone and flash anything.
Click to expand...
Click to collapse
Have you hard powered the device down and then rebooted to BL with key combo to check connectivity?

sliding_billy said:
Have you hard powered the device down and then rebooted to BL with key combo to check connectivity?
Click to expand...
Click to collapse
No, could you please descripe the process what to do exactly. Would love to give it a try. Thank you

MMoes said:
No, could you please descripe the process what to do exactly. Would love to give it a try. Thank you
Click to expand...
Click to collapse
Hold down the power button until the phone completely shuts off. Hold power while holding the volume down button (start by holding the volume down and then immediately start holding the power button - it's is technically holding both at the same time but starting with volume down just a moment before keeps you from pressing power first). That should get you to fastboot.

MMoes said:
Thanks, I‘ve tried with adb devices & no device found. So obviously my computer doesn‘t recognize the Pixel
Click to expand...
Click to collapse
ADB doesn't work when booted to the bootloader. It only works when you're booted to the OS. To see if the computer recognizes the phone when in the bootloader, use fastboot devices instead of adb devices.

sliding_billy said:
Hold down the power button until the phone completely shuts off. Hold power while holding the volume down button (start by holding the volume down and then immediately start holding the power button - it's is technically holding both at the same time but starting with volume down just a moment before keeps you from pressing power first). That should get you to fastboot.
Click to expand...
Click to collapse
Holding the power button didn't had any effect, but holding volume - and holding power button at the same time was starting the bootloader and so I was now able to start TWRP Manager.
So if you could help me from here to fix the OS would be great, e.g. is there any chance to copy the original OS from Google or an custom ROM from my computer (e.g. I wotk on MAC and is there a way to copy via Terminal?) or does TWRP offers any way to reset/ reinstall?

robocuff said:
ADB doesn't work when booted to the bootloader. It only works when you're booted to the OS. To see if the computer recognizes the phone when in the bootloader, use fastboot devices instead of adb devices.
Click to expand...
Click to collapse
Yes, the computer recognizes the phone (via Terminal on my MAC)

MMoes said:
Holding the power button didn't had any effect, but holding volume - and holding power button at the same time was starting the bootloader and so I was now able to start TWRP Manager.
So if you could help me from here to fix the OS would be great, e.g. is there any chance to copy the original OS from Google or an custom ROM from my computer (e.g. I wotk on MAC and is there a way to copy via Terminal?) or does TWRP offers any way to reset/ reinstall?
Click to expand...
Click to collapse
Sorry, but I do not know the Mac commands, but if you are in Fastboot and the device shows/connects it is just a matter of running the flash-all and resetting. If you are not connecting in Fastboot but can get into TWRP, I would start with a reset in TWRP.

sliding_billy said:
Sorry, but I do not know the Mac commands, but if you are in Fastboot and the device shows/connects it is just a matter of running the flash-all and resetting. If you are not connecting in Fastboot but can get into TWRP, I would start with a reset in TWRP.
Click to expand...
Click to collapse
The commands on the MAC are almost the same and with your flash-all (flash.all.sh Mac Command) it worked very well with the factory image from google. Now I'm back in the race and my P3 is running again.
Thank you all guys!

MMoes said:
The commands on the MAC are almost the same and with your flash-all (flash.all.sh Mac Command) it worked very well with the factory image from google. Now I'm back in the race and my P3 is running again.
Thank you all guys!
Click to expand...
Click to collapse
Excellent news. On another note... if all you need from TWRP is to install Magisk to root, you do not need to permanently install TWRP. Just fastboot boot the [twrp].img file, install the Magisk .zip and keep stock recovery.

From messing around, it seems that trying to restore system from twrp is messed up. Data backup works fine. The only other way I got bootlooped was by messing with boot, vbmata, and vendor partitions. Out of those three, I think boot is the most likely to get messed up by normal users. I know this is sorted now, but in the future try to just reflash boot.img and see if it boots.
-The vbmeta and vendor thing is specific because I need to get the radio to work here.