I was trying to root my device (Xperia Z3 Compact) as instructed here:
DooMLoRD's CWM-Based Recovery Console
Somewhere in between, a mistake was made and being the novice that I am, I can't seem to undo it.
I also have no idea what happened, but if what I understood online is right, I screwed up the bootloader which made the recovery console unavailable.
Here is screenshot on Emma:
Here are the steps I made on the console:
Also, the phone makes some sort of nice sound, not a beep, although I can't identify it and the screen is always black.
I would pretty much appreciate all the help, with the things I've done, I've pretty much voided the warranty (I think) so I hope you guys can help me out.
We advise users to check supported devices at Developer World.
The D5833 is now added as a supported device, and I hope it will appear as an available service next time you connect your Z3 compact.
Best regards
Carl
Sony developer support
Indeed, by rooting device you've lost warranty.
I've faced with fact it's not to easy run Recovery Console while booting device. Sometimes I had to push to volume control buttons very long and fast for achieving result.
Please check is device seen by fastboot now.
I believe if bootloader is really broken you have to take your device to the service. Guys from service should be able to recover it by JTAG.
It seems that you've already flashed a custom kernel.
Key sequence for entering recovery program may change depending on the kernel being flashed. So for my Xperia P I've had to press the power button repeatedly until I get into CWM recovery.
To switch into fastboot : press and hold the volume Up button, and plug in the USB cable; the notification LED will light up Blue
flash mode: press and hold the volume Down button, and plug in the USB cable
Related
I really hope somebody can help me with this.
I have xperia z5 premium, power button stopped working a month ago or something, but the phone was working perfectly fine. Of course, I made a mistake and did not charge it in time and it turned off. Now I can't get it to turn back on because the button is not working.
I explored all my options and I realized I can do fastboot reboot through fastboot and adb. However, I can't seem to get my phone to go into fastboot mode.
I hold volume up button (which I know for a fact is working), I plugin usb, and instead of getting that blue led light everybody keeps talking about, I just get a red led and then a green one after the sony logo that signals the phone is charging.
I installed ADB and xperia z5 premium drivers and I still can't get it to work. When I type fastboot reboot it says when I try adb reboot or adb reboot bootloader it says "error: device not found".
I've also installed xperia companion app and when I plugin my phone it shows a screen where it says: "Your device is locked
Unlock require
Unlock the device using password or fingerpint if needed
Allow data access
On your device, select the option to allow data access"
I've tried doing the same thing with adb on two different pcs, always get the same result. Phone just gets to charging screen and keeps charging instead of going into any mode.
I also tried holding volume down button and plugging in usb which is supposed to be recovery mode or something, but that doesnt work either, I also get charging screen. And I'm 100% sure both my volume up and volume down buttons are working.
What am I doing wrong?
P.S - Debugging mode is not on, im 100% sure since i never turned it on.
Somebody please help!
Thanks!
try downloading the sony xperia flashtool and boot your device in fastboot mode by holding down the volume down button and inserting the usb cable a blue light should appear, open up the flash tool and wait for the device to be detected if not detected, goto c drive then inside the flashtool folder there should be a folder named drivers, open it up then install the drivers for your device. back to the flashtool... when your device is detected, click on the lightning bolt icon and select fast boot mode, then you should see a window pop up and click reboot device into system.
hope this solves your problem
My goal is to get my Moto G6 phone in Root Mode. I bought a blank phone for this purpose, so no data is at risk. After following the steps on the XDA guide, I only got so before things did not work as they described. If I reboot my phone, I get this blue Moto G6 bootscreen and the phone never boots. I can get TWRP running on the phone though. Right now, my phone is not being recognized by either adb or fastboot. The guide I've been following is at
https://forum.xda-developers.com/moto-g6/how-to/guide-twrp-root-magisk-installation-t3816569
c:\Software\MotoG6>adb shell
error: no devices/emulators found
c:\Software\MotoG6>fastboot devices
c:\Software\MotoG6>
I have the latest Moto G6 drivers installed, but I don't think they apply anymore. If I unplug and replug in the USB cable into my Windows machine, it says it does not recognize the device.
The firmware I saw on the device when it did boot was OPSS27.82-87
* I do not know how to go back to stock because it won't recognize the device enough for me to push the stock image to it. *
*** FWIW, even on step 3 of that guide, it would say the boot image was not signed or corrupt. This happened when I tried to do
fastboot flash boot <insert-boot-image-name-here>.img
someone else had that problem and the recommendation was to ignore the message and reboot to recovery.
(https://forum.xda-developers.com/moto-g4-plus/development/wip-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586/page2)
For those who would say, "Read the **** manual", bear in mind that I did read the manual. No manual said where to get the firmware information they asked for. Also, many of the image links were bad. They did not say how to handle the case where the image did not install as they said it would. Somehow these manufacturers make each phone just enough different, and each firmware is different that it's impossible to predict what a phone will say ahead of time with certainty.
When it shows no commands, press and hold the power button then tap volume up button once. Then release the power button.
If this doesn't work mostly likely needs to be sent back to the manufacturer.
I had rooted my Yu Yureka plus by unlocking the bootloader using adb fastboot method, then flashing the TWRP recovery V2.8.7.0, and then flashing superSU v2.46.
After rebooting my yureka plus, and going to recovery it started cynogen recovery only, even though update cynogen recovery option was disabled.
So I flashed TWRP again and without rebooting again, just flashed crDroidAndroid-6.0.1-20160827-tomato.zip and GApps zip file from internal memory. The phone rebooted and worked fine after that.
But while playing a game the phone automatically rebooted and ever since have been stuck on "Preparing to start.. Starting apps.."
I had disabled the developer options because I thought it was working fine.
The phone is working behind the preparing to start screen.. I can hear the message notification and caller ringtone when someone messages or calls, but can't access anything
Any suggestions what I should do now?
I have tried doing a factory reset from recovery but the problem persists and none of the hardware buttons are working, had to remove battery to access the recovery (still cyanogen recovery is opening).
Please HELP!
you can us this tutorial to get back to stock rom
http://www.thetechnotriad.com/393/how-to-unbrick-yu-yureka/
So the title pretty much says it all and it's a pretty weird problem. Every time I connect my cyanogenmod via USB to my computer it reboots and wants a firmware update. As far as I can tell, this started happening while I was developing an app. I was using android-studio to run it on my phone when gnome started having problems mounting it.
It shouldn't have been mounting it to begin with because the phone was only connected for usb-debugging. However, because gnome was having problems, it kept trying to mount the phone and I was getting mount notifications every couple of seconds. Because this was so annoying, I disabled auto-mount in the dconf-editor in gnome. The notifications stopped, but at that point, android-studio was also not able to install the app on the phone anymore. Then at some point, the phone "crashed" and restarted, asking me for a firmware update.
I can restart the phone into normal mode by disconnecting the USB cord and holding the power button. Then everything works fine, but still every time I connect the phone to USB, it reboots, wanting a firmware update. I've tried doing adb devices while the phone is in the firmware screen, but adb doesn't find my phone, so I can't even debug like that.
Is there a way to debug or fix this? Or is there a way cancel the firmware update from the firmware screen, so that it won't interpret a usb-connection as a signal to do a firmware update? BTW, the phone is an LG G2, in case that makes a difference.
So I've researched this a little further and found the answer here. This seems to have been a side effect of not having enough space left on the device. It would be cooler if they had said something to that effect, but at least the problem is solved
I just installed android sdk. And trying to follow these steps to detect my device. Because my phone was disconnected & dead during an unfortunate/accidental/unwelcome software upgrade.
It's frozen on Samsung start up screen. I was able to use volume + power + home buttons to get into another black screen with now send the package you want to apply to the device with adb sideload <file name>. But not sure how to sideload from adb when I can't even detect my device. All I want is to retrieve my data & start up my device as normal.
Within the Command Prompt under platform tools, I typed adb devices. But no device listed. I am currently installing the Samsung Galaxy Note MTB device driver.
Can someone please guide me to the correct steps? There has to be a way to retrieve the data from the internal memory right?
Edit 1:
According to this article, I am not sure if my phone is bricked or trap in a bootloop...First of all, lets get something straight. Most people use the term "bricked" improperly. A bricked phone means one thing: your phone won't turn on in any way, shape or form, and there's nothing you can do to fix it. It is, for all intents and purposes, as useful as a brick. A phone stuck in a boot loop is not bricked, nor is a phone that boots straight into recovery mode. These are things you can usually fix, and they're a lot more common than a truly bricked phone. If your phone is actually bricked, you won't be able to fix it yourself (but there are things you can do—see the end of this article)
Edit 2:
PC specs : Win Vista, 32-bit
After installing MTP drivers I am at this point. However within adb devices command I only see <aserial number> recovery. It doesn't say <serial number> device
Do I still have a hope to get to my data?
Your phone may be stuck in a BootLoop It wont get detected using adb try using FastBoot if not you should contact your samsung service center to reload software . Your data is lost in this case.
UPDATE
try downloading sp flash tool check your phone is detected if so you can have some hope in data recovery