Related
Uh, so I've been having a few problems trying to unlock the bootloader on my X10 and I came to some problems:
1. When I first connected my phone with the USB cable, the FlashTool showed that my phone had debugging mode off even though I checked it and it was on!
2. I ignored this problem and decided to try unlocking the BL anyways. When I shut down my phone, held the back button and plugged the USB cable to put the phone into Flashmode, after 10-20 seconds it would automatically reboot itself and get my phone out of Flashmode, making me unable to flash Kernel Downgrade!
3. This time I trained my fingers and tried to flash Kernel Downgrade before my phone started to reboot itself and I succeeded. But now that I flashed it, the next step for unlocking says
"disconnect usb cable, press power button until phone vibrates shortly and immidiatly connect the usb cable again (it is supposed to be stuck at SE logo)"
but the problem is that my phone won't go anywhere after the Sony Ericsson text (not the logo with the circle and stuff where it's supposed to)
I am using (or at least was using until I flashed Kernel Downgrade) DoomLord's Kernel v6 and ViolentOS ROM. I have also tried restoring the xRecovery backup I made exactly before starting the flashing, but it still won't work, the phone always gets stuck on the Sony Ericsson text. What am I supposed to do?!
What logo with the circle?? That's the boot animation, loaded when system is already running. It is supposed to be stuck at the first screen, that's when system starts loading kernel and can't with "wrong" baseband.
Sony Ericsson text is WHERE it has to be stuck.
Also, at least for me, I couldn't do unlock without 2.1 rooted system installed, had to flash baseband and system, then unlock and then restore my 2.3 backup.
New Problem
kalte said:
What logo with the circle?? That's the boot animation, loaded when system is already running. It is supposed to be stuck at the first screen, that's when system starts loading kernel and can't with "wrong" baseband.
Sony Ericsson text is WHERE it has to be stuck.
Also, at least for me, I couldn't do unlock without 2.1 rooted system installed, had to flash baseband and system, then unlock and then restore my 2.3 backup.
Click to expand...
Click to collapse
@kalte The logo with the circle is the animation that comes after the text.
But forget what I said. I'm trying to boot the phone and it's not working. I disconnected the USB and took off the battery then put the battery back in to see if it could boot. It's stuck at the text even though I restored everything with an xRecovery backup. Is this because of the Kernel Downgrade?
FIXED IT!
I'm such an awesome person! Just had to flash the Generic Kernel Upgrade. Everything is working, with my previous settings and all.
Tried Unlocking X10i .. getting stuck at the SE logo
I used the following method to unlock my phone bootloader:
http://forum.xda-developers.com/showthread.php?t=1254087
I successfully unlocked the bootloader. But now its taking forever to load. Its getting stuck at the SE logo.
Please help !!!
thejassk said:
I used the following method to unlock my phone bootloader:
http://forum.xda-developers.com/showthread.php?t=1254087
I successfully unlocked the bootloader. But now its taking forever to load. Its getting stuck at the SE logo.
Please help !!!
Click to expand...
Click to collapse
Flash Stock Firmware of your region using flashtool, to get you phone back to life. & try unlocking your bootloader using Flashtool.
PS- Flashtool never disappoints me.
Hey folks, last night I followed this guide http://forum.xda-developers.com/showthread.php?t=2708194 to get a custom bootloader installed on my tablet. Unlocking the bootloader was a bit strange, but worked. I downloaded the bootloader for the SGP511 wifi-only model and installed it without issues. After that, I rebooted and was stuck in a boot loop. The device starts by displaying the logo, then turns black and vibrates periodically a couple of times, then reboots and does the same over and over again. I had the device plugged in allowed to run for at least 45 minutes to see if it would help, but to no avail.
I can access the custom recovery included in the bootloader just fine, but the OS doesn't seem to like the new bootloader. Anyone know of a solution?
serazaziel said:
Hey folks, last night I followed this guide http://forum.xda-developers.com/showthread.php?t=2708194 to get a custom bootloader installed on my tablet. Unlocking the bootloader was a bit strange, but worked. I downloaded the bootloader for the SGP511 wifi-only model and installed it without issues. After that, I rebooted and was stuck in a boot loop. The device starts by displaying the logo, then turns black and vibrates periodically a couple of times, then reboots and does the same over and over again. I had the device plugged in allowed to run for at least 45 minutes to see if it would help, but to no avail.
I can access the custom recovery included in the bootloader just fine, but the OS doesn't seem to like the new bootloader. Anyone know of a solution?
Click to expand...
Click to collapse
You didn't read properly.
You have the new .402 firmware on your device, and the custom kernel / recovery is only compatible with .36 and .55 firmwares. (Doomlord is working on a new version, so just wait a few days.)
Press Volume-Up + Power for a few seconds (device will vibrate 3 times or so) to hard-reset the device.
Then flash a FTF of the .402 firmware with the xda Flashtool (not the Sony Flashtool) to restore functionality.
That worked like a charm, thanks a million and sorry for not reading the instructions properly!
hasenbein1966 said:
You didn't read properly.
You have the new .402 firmware on your device, and the custom kernel / recovery is only compatible with .36 and .55 firmwares. (Doomlord is working on a new version, so just wait a few days.)
Press Volume-Up + Power for a few seconds (device will vibrate 3 times or so) to hard-reset the device.
Then flash a FTF of the .402 firmware with the xda Flashtool (not the Sony Flashtool) to restore functionality.
Click to expand...
Click to collapse
Okay, I'm not sure exactly what you'll need to know to help, so I'll just tell you what I think is important....
Current situation:
- If I boot the phone normally it freezes at the SONY screen and goes no further.
- If I attempt to boot into recovery mode, it loads the CWM screen (logo in the middle with instructions at bottom), but no actual menu or options. After about 5 seconds, this screen disappears, the phone reboots and then gets stuck on the SONY screen.
- If I connect the phone to the computer in Flashmode Flashtool recognizes it as being connected, but regardless of what I do, after about 2mins the phone reboots, loses connection with the computer, and freezes on the SONY screen as before mentioned.
- If I connect the phone to the computer normally while stuck on the SONY screen, the PC recognizes it though doesn't allow me to do anything to it, and Flashtool says I need to install drivers (I have installed every driver that comes with Flashtool).
How I got here:
- I've rooted the phone
- I've flashed Z2_DooMLoRD_AdvStkKernel_FW-438-v05
- I've unlocked the bootloader (via Flashtool)
- I've installed [Rom][Unofficial]Slim Rom 4.4.4 based on CM11.0, ROM for the Sony Xperia Z2
The phone was okay up until this point, however I wasn't happy with the ROM so I tried to reboot into recovery mode to wipe and install Carbon. This is when the trouble began.
Now it seems I can't do anything :/
Please help. This phone is literally 3 days and it looks like I've completely screwed it >.<
Thanks!
How to recover your device from almost any kind of brick
Requirements
Check the pinned sites
Flashtool
FTF of choice for your device
2 Rubber bands (I am serious but only if your device has no response)
Step1
unplug your device from anything
open flashtool on your pc
plug your cable into your PC
do not plug the cable into your device
Step2
Hold your power button and your volume up button at the same time
your device should buzz 3 times
(this should take a few secconds)
if it does not take a few seconds then you need to put a rubber band around your device holding your power button and your volume up button, DO NOT LEAVE MORE THAN IT NEEDS TO BE LEFT, wait patiently for your device to buzz 3 times
Step 3
once your device has buzzed 3 times you are free to flash a FTF as your device is powered off
step4
if you dont know how to flash a FTF but have gotten as far as installing flashtool,Z2 drivers and downloading a FTF FOR YOUR DEVICE... then folow this step
within your flashtool window click on the lightning icon at the top left
select flashmode
navigate to where you downloaded your FTF (OR put your FTF in your /flashtool/firmwares folder)
select your FTF
Flashtool should give you a prompt to plug in your device
hold volume down and plug in your device
step5
wait for it to finish flashing
step6
your device is now recovered, enjoy...
Sent from my D6503 using XDA Premium 4 mobile app
I bricked my phone doing this:
- root with eazyroot
- installed dual recovery
- full wipe
- install carbon + gapps
bum... bricked
i cant even see the Sony logo
Then i use the method mentioned by Envious_Data and my phone returned from hell
Good luck dude... hope u can fix that
carloscarvalho said:
I bricked my phone doing this:
- root with eazyroot
- installed dual recovery
- full wipe
- install carbon + gapps
bum... bricked
i cant even see the Sony logo
Then i use the method mentioned by Envious_Data and my phone returned from hell
Good luck dude... hope u can fix that
Click to expand...
Click to collapse
You didn't unlock your bootloader?
Isn't Carbon ROM AOSP?
If it is, it needs an unlocked bootloader or it will get bricked
Unbalanced said:
Okay, I'm not sure exactly what you'll need to know to help, so I'll just tell you what I think is important....
Current situation:
- If I boot the phone normally it freezes at the SONY screen and goes no further.
- If I attempt to boot into recovery mode, it loads the CWM screen (logo in the middle with instructions at bottom), but no actual menu or options. After about 5 seconds, this screen disappears, the phone reboots and then gets stuck on the SONY screen.
- If I connect the phone to the computer in Flashmode Flashtool recognizes it as being connected, but regardless of what I do, after about 2mins the phone reboots, loses connection with the computer, and freezes on the SONY screen as before mentioned.
- If I connect the phone to the computer normally while stuck on the SONY screen, the PC recognizes it though doesn't allow me to do anything to it, and Flashtool says I need to install drivers (I have installed every driver that comes with Flashtool).
How I got here:
- I've rooted the phone
- I've flashed Z2_DooMLoRD_AdvStkKernel_FW-438-v05
- I've unlocked the bootloader (via Flashtool)
- I've installed [Rom][Unofficial]Slim Rom 4.4.4 based on CM11.0, ROM for the Sony Xperia Z2
The phone was okay up until this point, however I wasn't happy with the ROM so I tried to reboot into recovery mode to wipe and install Carbon. This is when the trouble began.
Now it seems I can't do anything :/
Please help. This phone is literally 3 days and it looks like I've completely screwed it >.<
Thanks!
Click to expand...
Click to collapse
Okay I used to get into this kind of situation when I used HTC One, and what I did is try to flash recovery and unlocked bootloader again "using command".
And problem has solved. I think it is pretty much same for Xperia Z2, (ftf flashing method is not useful in this situation.)
I hope you know how to flash custom recovery using command. If not I think there is some thread that explains how to flash recovery and unlock the bootloader using command, if you can't find it plz let me know. Hope you have recovered phone next time I check this thread. Good luck mate :good:
HussainQ said:
You didn't unlock your bootloader?
Isn't Carbon ROM AOSP?
If it is, it needs an unlocked bootloader or it will get bricked
Click to expand...
Click to collapse
Yeah... I know... A newbie mistake...
I Just follow the instruction available in the site. And there is just "root and recovery"
No bootloader mentioned
But u r right... Thats the reason
Sent from my awesome Xperia Z2 using XDA Premium
@Envious_Data: Bro, thank you so much for that. I my z2 have only 1 day, and i god damn it bricket, that even screen wasn't working. So for other people who had bad luck: first I rooted using Community Rootkit, then unlocked bootloader, and at the end I flashed via fastboot boot.img which one i extracted from zip file from this thread - http://forum.xda-developers.com/showthread.php?t=2702001. Command prompt showed that it works. I rebooted phone sony logo showed up, but then disappeared, and then was crying and sorrow. Three years of rooting,flashing without any problem, and now that. Thank you one more time, that's a great lesson
I do have some advice for people
1. Try to find help threads for your device, i have one for Z2 that gives some useful info, ill be adding more soon
2. Once you have got the jist of flashing then try to expand on that, i do recomend roms first because its harder to brick from a rom than a kernel or a non stock based rom such as CM11 or AOSP
3. Always keep a stock flashable rom (kernel too if you have a unlocked bootloader) on your device
Sent from my D6503 using XDA Premium 4 mobile app
I too hard brick my Z2, only solution is the same as for Z1 http://forum.xda-developers.com/showthread.php?t=2646405
Sorry friend :`
discipuloosho said:
I too hard brick my Z2, only solution is the same as for Z1 http://forum.xda-developers.com/showthread.php?t=2646405
Sorry friend :`
Click to expand...
Click to collapse
A hard brick is by definition not recoverable by the user, requiring either special equipment ie jtag or RMA to fix.
I am quite surprised, and intrigued, at people flashing cm or AOSP on a two day old phone, was Sony experience that awful? You'd maybe be better served with a nexus device.
ghostofcain said:
A hard brick is by definition not recoverable by the user, requiring either special equipment ie jtag or RMA to fix.
I am quite surprised, and intrigued, at people flashing cm or AOSP on a two day old phone, was Sony experience that awful? You'd maybe be better served with a nexus device.
Click to expand...
Click to collapse
True friend, but I had an Xperia MT11i (Neo V) and all (fastboot, flashtool, CM, etc) was always no problem.
I've taken today for service (with CM11 (and cm kernel)) and see what happens ...
@Unbalanced I don't think your Z2 Hardbricked, if it were not ignite. Luck
Hi all, if it helps I did the same thing last night. Flashed CM11 without a recovery and wanted to revert back to my nandroid backup. I flashed doomloards kernal via fastboot. CWM started with no menu and just bootlooped. I then thought it may be a CWM issue, maybe no file structure or something. I flashed XZDuelKernal via fastboot and booted into CWM again and experienced the same issue. As this is a duel recovery, I then booted into TWRP. Recovery started and I was able to flash another zip then recover my nandroid backup. If you get this menu issue with CWM,try and flash a TWRP recovery and boot into that.
Also, as mentioned before, this is not a hard brick. It's just incompatible software and is easily fixed if you know what you are doing and prepared (nandroid backup, knowledge about fastboot and flashmode, ftf, recovery, unlocked bootloader).
Sent from my D6503 using Tapatalk
Stuck
Hi.
I believe (although I'm not sure) that I have bricked my Xperia Z2 in some way. When I press the 'power' button, the phone vibrates once and does nothing. I have tried to hold the 'power on' and 'volume up' buttons for a long time (half an hour with rubber bands), and nothing happens (as explained earlier in the thread).
I believe I am able to access the fastboot though, through 'Terminal' app on OSX. From there I can " ./fastboot devices " and get confirmation that they have loaded. I am also able to perform other tasks from here, such as flashing a recovery and " fastboot erase system -w " (which I believe may have got me to where I am now). I've been following things on this thread: http://forum.xda-developers.com/showthread.php?t=2277112
I have no experience in rooting or flashing, but attempted to flash a custom ROM because there were step by step instructions.
Anyway, I firstly used Sony's rooting procedure whereby an unlock code is generated etc. Eventually I gained access to the Recovery mode (via clockwork), and wiped the phone, installed the ROMAur zip and GApps zip. However, when I booted, it kept giving me warnings saying the apps were crashing. I've since gotten lost completely and need someone to help bail me out.
I'm hoping I can sort things out via the fastboot.
Thanks in advance for your help.
scoobard said:
Hi.
I believe (although I'm not sure) that I have bricked my Xperia Z2 in some way. When I press the 'power' button, the phone vibrates once and does nothing. I have tried to hold the 'power on' and 'volume up' buttons for a long time (half an hour with rubber bands), and nothing happens (as explained earlier in the thread).
I believe I am able to access the fastboot though, through 'Terminal' app on OSX. From there I can " ./fastboot devices " and get confirmation that they have loaded. I am also able to perform other tasks from here, such as flashing a recovery and " fastboot erase system -w " (which I believe may have got me to where I am now). I've been following things on this thread: http://forum.xda-developers.com/showthread.php?t=2277112
I have no experience in rooting or flashing, but attempted to flash a custom ROM because there were step by step instructions.
Anyway, I firstly used Sony's rooting procedure whereby an unlock code is generated etc. Eventually I gained access to the Recovery mode (via clockwork), and wiped the phone, installed the ROMAur zip and GApps zip. However, when I booted, it kept giving me warnings saying the apps were crashing. I've since gotten lost completely and need someone to help bail me out.
I'm hoping I can sort things out via the fastboot.
Thanks in advance for your help.
Click to expand...
Click to collapse
Download ftf file for your device and flash via flashtool.
mariosraptor said:
Download ftf file for your device and flash via flashtool.
Click to expand...
Click to collapse
Thanks for the quick reply Mario. I did just that (using Kuwait FFT for the D6503), and everything appears to be back to normal. Unfortunately I still have not got root access and can't remove the bloatware. As for the bricking issue however, it's solved. Thanks.
Hi guys. So I have been going through xda and Google for hours and hours trying solutions, to no avail. I almost never post on forums for help because I can usually find the solution. Not this time. This is my last resort next to throwing my phone out a window or praying for death's sweet release.
The facts: I have a rooted Xperia Z3v. I tried to upgrade TWRP in order to follow some directions on upgrading to Nougat. I flashed TWRP from 2.8.X.X to 3.X.X.X. I rebooted and it never made it to the Sony logo. Now, if I plug the phone in to either a wall socket or PC it vibrates, endlessly at three second intervals, each time with red LED. If I try to enter flash mode, then its the same but with a brief green led after the red. I can enter fastboot (the only way to stop it vibrating while plugged in) and my PC sees it, including Flashtool, but since my bootloader is locked permanently, I can't really do much with it.
When plugged into the wall-charger, I noticed that the charger's LED changes from "Active" to "Inactive" with every vibration. I'm pretty sure I'm in a reboot loop. The screen is totally dead and there's no logo, but every three seconds it kills it self and comes back.
I have tried everything I could think of.
What I have:
I have the stock firmware ready to go
I have TWRP backups on SD card and PC
I have Flashtool
I think my drivers are good, but not 100% sure
I can fastboot
I'm at my wit's end and losing hope.
Please, I'm open to any suggestions at all.
R3 Pro (3GB/32GB, 2015817 version) came with some chinese/sellers custom ROM (and locked bootloader). It was heavy and bloated, so I decided to update it. Tried latest global stable (fastboot) ROM via miflash, flash was successful but that's was a lie - it stuck on mi logo...
Then I tried various other ROMs, global and developers, latest and older, some xiaomi.eu, manhit, etc. (for locked bootloader) and all I've got was either just a mi logo or mi logo with "powered by android" animation beneth. I left it for hours after flash and still nothing.
Then I found some ways to flash twrp, did that successfully, booted into it, wonder around in terminal and file manager, tried some recovery ROMs - but the result is the same - just logo or logo + animation.
I can get into fastboot (but it doesn't realy matters since bootloader is locked), download (EDL) mode, that Xiaomi menu (with Power and Vol+, with "shortcuts" to all the modes, hardware tests - btw. everything works there, etc.), twrp, charge battery (with some ROMs phone just gets warm and I know it's charging, there are no LED and/or animation, but in some everything works just like it should), but just can't boot into OS.
And I'm going nuts!
Here are some logs from the last ROM (i don't even know anymore which one is it) - pastebin.com/qaKVzxue and pastebin.com/dM3nEVj0
I'm not so experienced in looking at that but seems like every other thing in there, like cpu, i2c (touch/sensor), sound, battery, etc. is broken/faulty which is not true - everything was fine before update, and everything IS still fine according to inbuilt (xiaomi) hardware tests.
So somehow it seems that all the ido ROMs I tried are wrong for this device? Or am I missing something (quite possibly, I'm tired and pissed off)
Last night I did a backup of efs/nvram and then wiped internal memory/partitions, flashed latest global ROM, restored efs/nvram - phone stuck, but this time not on MI logo but freakin' penguin logo (like here en.miui.com/thread-377870-1-1.html). Same logo is for fastboot mode, no more bunny. Then flashed twrp and phone now shows mi logo with "powered by android" animation beneath, like before...
I don't know how this works with Xiaomi phones, but looks like it worked with some factory/seller special combination of ROM and bootloader. Then I did update and something stuck, maybe differences between ROM and bootloader, or some inside/hidden security mechanism that stops boot process? And because I can't find original firmware and/or bootloader is locked (maybe even updated?) it's now stuck...
Either that or some HW fault, but it would be insane that official ROM update with official tools and in factory download mode with full battery can cause such problem!
Can you go to twrp recovery?
Yes, like I said in the first post. I can do anything but boot android/MIUI. It's either because of locked bootloader or somehow official ROM installed officialy (via MiFlash in EDL mode) bricked phone, which is catastrophic bug i.e. epic design/implementation fail by Xiaomi.
Try this
https://forum.xda-developers.com/redmi-3/help/bootloop-bootloader-locked-options-t3331139
Sorry to intrude, I have pretty much the same problem.
Phone is stuck in bootloop and I can only access fastboot mode and EDL mode (but in EDL the phone does not connect to pc) and when I try to flash a stock ROM (since I know it is a software issue due to an unfortunate update) it says "locked device". So I tried to unlock it via MiUnlock... but phone cannot be verified 'cause "account not bound to this device" and obviously I cannot change any options since I cannot use my phone.
Please, help
it was happened to me about 3 days ago when i play around with the twrp & rooting thingy... tried everything from youtube to various forum solutions... just one link really works when you only have fastboot options and your phone bootloader is still unlocked. just follow the steps in the OP... key things here is downloading the tool to read your phone as mentioned in the OP i.e [TOOL]Minimal ADB and Fastboot [1-6-17]
1) Download Tool -> https://forum.xda-developers.com/showthread.php?t=2317790
2) Follow all the steps in the OP -> http://en.miui.com/thread-277276-1-1.html
3) Enjoy your phone from back from the dead.. LOL!
4) Remember here, the key is NEVER GIVE UP and PATIENT!
NOTE : The Device will start, wait till completion , it can take up to 10 Minutes. -> for me around 15-20 minutes for I have flashed the current beta rom of MIUI8 7.6.8
cheers, guys!
blx-
I had a similar situation.
Officially unlocked boot loader. Flashed TWRP using fastboot. Only got the mi logo and a boot loop on start up.
Could not turn on. Could not boot into TWRP.
When the phone was boot looping I could still get into fastboot mode by holding power+volume down.
I booted from fastboot mode into TWRP by opening the command prompts and using
"fastboot boot twrp2.img"
That got the phone available from windows explorer. I was able to move a new ROM image to the SD card and install from TWRP.
Currently running lineage 14.1 -20190112.
I lost a bunch of **** but my phone seems to turn on for the moment.
Note, I still cannot boot into TWRP using the phone only. I can only boot in from fast boot as above.