DISCLAMER and WARNING: I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or the current economic crisis. Please do some research if you have any concerns about this app.
Click to expand...
Click to collapse
Story:
Just received Sony Smartwatch 3 and decided to oem unlock for future so once root available I would not need to reset device.
Enabled adb
manually specified correct drivers in device manager
rebooted to bootloader using adb reboot bootloader
entered fastboot oem unlock twice and watch rebooted
but got stuck on boot for whatever reason.
I tried all the methods to get into fastboot (Swiping diagonal as on LG watch, and together with power button as on samsung ) to no avail.
The only other mode I was able to get into - s1 flash device w/o drivers.
Found Sony Emma software to work with unlocked Xperia, and after its installation it said that bootloader is locked and I need to either update from sony site or unlock bootloader first!
Installed Sony PC Companion software, but software update while listing smartwatch 3 said that there is no firmware for it.
After googling random forums on bootlooping sony xperias found that to reset device you need to click "repair my phone/tablet" in Phone/Tablet Software Update section
Click to expand...
Click to collapse
Guide to unbrick bootlooping SWR50 that is able to get into s1 bootloader/flash mode:
1. Power off device by holding power key until it reboots and then switches off with few vibrations
2. Connect to computer and check device manager - you should see unknown device
3. Install Sony PC Companion from this website http://www.sonymobile.com/us/tools/pc-companion/
Check if driver appeared in the Device Manager, e.g. unknown device will disappear and something like SEFLash will appear under usb controllers
If driver is still not found - try to install Emma (http://developer.sonymobile.com/services/flash-tool/) and get this driver to work
4. Go into PC Companion and click on "Support Zone", it will be downloaded
5. Then click on "Accessories software update" and try to update Smartwatch 3 (We might get new versions in the future, so it will be easiest to do so)
UPDATE: Now you can reflash from Accessories page, it will ask if you want to refrlash. Keeping steps bellow for information purposes.
6. If #5 not working:
Click on "Phone/Tablet Software Update" (yes, silly), click on "repair my phone/tablet", click Continue and Agree to all licenses, etc....
7. Once presented by the list of phones - Select anything I guess, but I selected Xperia Z2, it should start downloading and then updating.
8. Once done it will say build number watch was flashed, in my case it was KNX01V
9. Disconnect watch and boot it.
P.S. I guess they show phone selection just to provide instructions how to get into download mode and then flash based on the versions from bootloader.
P.P.S I'm glad I tried this last resort thing after being ready to deal with verizon support and waiting for new watch...
I've found that formatting cache and userdata partition like it says in the link below makes the device boot as expected:
source.android.com -> /source/building-devices.html#unlocking-the-bootloader
(sorry for faulty link, new user)
Good to know, I decided to wait a bit as I was eager to play with new toy.
Will unlock tomorrow if it is still locked after Sony reset.
And looks like I would have to write my own apps to test GPS and sensors performance.
And the good news is fastboot state unlocked after stock reflash.
XorZone said:
manually specified correct drivers in device manager
Click to expand...
Click to collapse
Can you please elaborate on which driver you used to get access to the Smartwatch 3 via ADB? I am trying to use the latest google USB driver, but the device is showing up as offline listed under "adb devices". Just tried the latest ADB v1.0.32 and it seems the watch shows up as "unauthorized". Did you see an ADB notification on the watch that you had to accept, because I am not seeing anything like that.
NVM, it started working after I restarted adb server like 25 times...
Device offline usually is not about driver. But I hit on device and manually picked google-adb composite device
OK, bricked watch today with corrupted /system and boot process hanged with non responsive power button. Had to wait for discharge and it was pita to get into flashmode with enough juice, because after black screen charging it boots instead of going into kernel charging.
Anyway it is up and running and has ROOT now!
Will upload files and create guide as soon as I will be with good internet.
See my sig!
*delete*
*deleted*
Well, there are different levels of bootloaders
At least Sony s1 flash, fastboot, kernel...
To flash with PC companion you need to boot into s1 by powering off and then hold power and connect to USB once sony logo shown (you should see black screen with backlight on). Make sure you sit on PC companion update screen and that watch had enough juice.
With charging there are different levels of charging:
1. Battery dead
2. Boot loader charging (about 4 min from USB port) with black screen
3. Kernel charging either offline (if you powered off before) or boot and operational charging.
When #2 charges it will boot kernel and if kernel or system is broken it might hang and discharge.
But you can force into s1 flash mode before it boots into kernel. Or if you lucky you could power on and power off before it boots and hang.
In my case I had not enough juice to flash it and watch didn't react to button in kernel mode, so I had to wait for discharge, then plugged into USB and start timer, figured it boots after ~3min 55sec. So I opened PC companion update screen, waited 3:53 and disconnected watch, then hold power button and connect to PC after 5 sec and was able to flash.
To power off - just hold power button until it reboots and continue holding until it vibrates 3 times.
Good luck
XorZone said:
Story:
Guide to unbrick bootlooping SWR50 that is able to get into s1 bootloader/flash mode:
1. Power off device by holding power key until it reboots and then switches off with few vibrations
2. Connect to computer and check device manager - you should see unknown device
3. Install Sony PC Companion from this website http://www.sonymobile.com/us/tools/pc-companion/
Check if driver appeared in the Device Manager, e.g. unknown device will disappear and something like SEFLash will appear under usb controllers
If driver is still not found - try to install Emma (http://developer.sonymobile.com/services/flash-tool/) and get this driver to work
4. Go into PC Companion and click on "Support Zone", it will be downloaded
5. Then click on "Accessories software update" and try to update Smartwatch 3 (We might get new versions in the future, so it will be easiest to do so)
UPDATE: Now you can reflash from Accessories page, it will ask if you want to refrlash. Keeping steps bellow for information purposes.
6. If #5 not working:
Click on "Phone/Tablet Software Update" (yes, silly), click on "repair my phone/tablet", click Continue and Agree to all licenses, etc....
7. Once presented by the list of phones - Select anything I guess, but I selected Xperia Z2, it should start downloading and then updating.
8. Once done it will say build number watch was flashed, in my case it was KNX01V
9. Disconnect watch and boot it.
P.S. I guess they show phone selection just to provide instructions how to get into download mode and then flash based on the versions from bootloader.
P.P.S I'm glad I tried this last resort thing after being ready to deal with verizon support and waiting for new watch...
Click to expand...
Click to collapse
This method is windows only. Is there no cross-platform way to do it?
I did the stupid thing.. and ended up with a softbricked phone.
Sony PC Companion did the trick for me!
I tried doing it through VMWare on my macbook, but didn't seem to work at all.
On windows it was plug'n'Pray
Sony companion will not let me restore my SW50. Detects it and tells me that the software is updated. If I try from the menu to repair phone, it makes me accept all agreements and finally tells me the same thing no updates.
Is in bootloop and do not start after open bootloader
My sw3 is in bootloop.I uesd your guide but still can't repair my watch. I tried many time to use pc companion but always got the same wrong message,wrong code(100) which couldn't connect to the Internet.
@swidon @KONG8691
I find myself in the same situation, you have found a solution to the problem?
Thanks for your help
best regards
jerry_italia said:
@swidon @KONG8691
I find myself in the same situation, you have found a solution to the problem?
Thanks for your help
best regards
Click to expand...
Click to collapse
Yes!, follow these instructions and you can enter in fastboot or recovery and flash a new firmware:
Detach any USB cable connected to the watch
Turn it off holding the power button and keep holding the button until the watch vibrates three times and then switches it off
Press the power button and keep holding. A blue screen that prompts to insert an USB cable will display
Double tap the power button
A black menu will display, with on-screen instructions
Move to Fastboot or Recovery Mode pressing the power button, once a time
Select Fastboot (or Recovery) by double pressing the power button
Good luck bro.
swidon said:
Yes!, follow these instructions and you can enter in fastboot or recovery and flash a new firmware:
Detach any USB cable connected to the watch
Turn it off holding the power button and keep holding the button until the watch vibrates three times and then switches it off
Press the power button and keep holding. A blue screen that prompts to insert an USB cable will display
Double tap the power button
A black menu will display, with on-screen instructions
Move to Fastboot or Recovery Mode pressing the power button, once a time
Select Fastboot (or Recovery) by double pressing the power button
Good luck bro.
Click to expand...
Click to collapse
you are my hero... stock recovery flashed and sw3 reboot! thankyou so much bro
jerry_italia said:
you are my hero... stock recovery flashed and sw3 reboot! thankyou so much bro
Click to expand...
Click to collapse
How do you go about getting stock recovery back at the moment I'm on 5.0.1 and I can't ota update to 5.1.1 because it thinks its on 5.1.1 when it's not the only way I can think of updating it is to get stock recovery then sideload the ota zip on stock recovert but I can't do that with TWRP can someone help?
Hi,
My watch boot loops on the marshmelow boot animation after I Got marshmelow
I tried XorZone instractions and it said it re-updated image. but it will boot looped.
I tried to factory reset from the menu (double tap at download screen then go factory reset).... didn't work. still boot loops.
I see I can go to fastboot or recovery, but what do I do there? Any instructions I can follow to try to revive my watch please? thanks.
wonderfull!
XorZone said:
Well, there are different levels of bootloaders
At least Sony s1 flash, fastboot, kernel...
To flash with PC companion you need to boot into s1 by powering off and then hold power and connect to USB once sony logo shown (you should see black screen with backlight on). Make sure you sit on PC companion update screen and that watch had enough juice.
With charging there are different levels of charging:
1. Battery dead
2. Boot loader charging (about 4 min from USB port) with black screen
3. Kernel charging either offline (if you powered off before) or boot and operational charging.
When #2 charges it will boot kernel and if kernel or system is broken it might hang and discharge.
But you can force into s1 flash mode before it boots into kernel. Or if you lucky you could power on and power off before it boots and hang.
In my case I had not enough juice to flash it and watch didn't react to button in kernel mode, so I had to wait for discharge, then plugged into USB and start timer, figured it boots after ~3min 55sec. So I opened PC companion update screen, waited 3:53 and disconnected watch, then hold power button and connect to PC after 5 sec and was able to flash.
To power off - just hold power button until it reboots and continue holding until it vibrates 3 times.
Good luck
Click to expand...
Click to collapse
Related
i got my acro s hard bricked
I used twrp for making a backup for the the stock firmware.
and then i installed the 5.0.1 the lollipop custom firmware
the link :http://forum.xda-developers.com/showthread.php?t=2799765
, but it was not rooted but somehow the recovery was working good .. i decided to restore the stock using the backup version which i made in the beginning coz the ROM was sucks. after finishing the loading it asked for restart and after that i got a blank screen and the following
-no response for charging
-no LED lights at all
-non of any combinations working (volume+ and power on , hard reset or volume+up+power on)
-access to fastboot or flashtool is denied
-no power on no vibrations
but after a day of charging an Orange LED appears but i waited for two more days till the LED disappeared
and tried the flashtool but all i got is "device connected but with debugging off"
i think the problem was using recovery with unrooted device but can't find a solution for that
any suggestions ??!!
Notes:
am too calm
am not panic ..
am not in hurry too
and it's not a big deal
i just want the device back in order to get my stuff from it that's why going to Sony service center is not an option coz they format the whole device
Similar here on st26i
On 4.4 Paranoidandroid I've got after a five days of use in one second a lot of force closes. From every app from the system. It was impossible to stop it, or make normal reboot, so I've hold Power + VolUp and waited till three vibrations. Then turn on the phone, normal vibration and SONY logo.
After that black screen. First with some backlight, after minutes phone backlight turn off.
Now:
- No response for Power button
- No response for Power+VolUp combination
- No charging LED
- System find only SEMC Flash Device
- Flashtool says Device Connected with USB Debugging off
- Combination Power+VolUp make connected device to disconnect and connect again as SEMC Flash Device
- Cant acces fastboot, dwonload mode.
smogf said:
Similar here on st26i
On 4.4 Paranoidandroid I've got after a five days of use in one second a lot of force closes. From every app from the system. It was impossible to stop it, or make normal reboot, so I've hold Power + VolUp and waited till three vibrations. Then turn on the phone, normal vibration and SONY logo.
After that black screen. First with some backlight, after minutes phone backlight turn off.
Now:
- No response for Power button
- No response for Power+VolUp combination
- No charging LED
- System find only SEMC Flash Device
- Flashtool says Device Connected with USB Debugging off
- Combination Power+VolUp make connected device to disconnect and connect again as SEMC Flash Device
- Cant acces fastboot, dwonload mode.
Click to expand...
Click to collapse
it seems like we stuck here
Yup.
Is there any windows/linux software for SONY devices like KDZ for LG phones? Which have an emergency flash option and, etc.???
/EDIT
So... I have read a little and I think (wchich I supposed before witout reading) boot is "dead".
I think it will be possibly to flash new boot with s1boot, but. I cannot find service manual for lt26i. Can anyone have it? Or can say where is the Test Point in this device?
makaom said:
i got my acro s hard bricked
I used twrp for making a backup for the the stock firmware.
and then i installed the 5.0.1 the lollipop custom firmware
the link :http://forum.xda-developers.com/showthread.php?t=2799765
, but it was not rooted but somehow the recovery was working good .. i decided to restore the stock using the backup version which i made in the beginning coz the ROM was sucks. after finishing the loading it asked for restart and after that i got a blank screen and the following
-no response for charging
-no LED lights at all
-non of any combinations working (volume+ and power on , hard reset or volume+up+power on)
-access to fastboot or flashtool is denied
-no power on no vibrations
but after a day of charging an Orange LED appears but i waited for two more days till the LED disappeared
and tried the flashtool but all i got is "device connected but with debugging off"
i think the problem was using recovery with unrooted device but can't find a solution for that
any suggestions ??!!
Notes:
am too calm
am not panic ..
am not in hurry too
and it's not a big deal
i just want the device back in order to get my stuff from it that's why going to Sony service center is not an option coz they format the whole device
Click to expand...
Click to collapse
Same situation, really need help from someone because its my only android phone right now.
Hello,
I think I bricked my phone
I wanted to upgrade from 4.4.2 to Lollipop http://forum.xda-developers.com/sony-xperia-z1-compact/general/stock-14-6-1-236-customized-lollipop-5-t3264557
And before that I did a factory reset and format data (I got some issues on my phone and wanted to get rid of them).
Now I can not enter TWRP, I can not enter any thing. At the time beeing, after many restarts my red button is broken, I switch it off by "Power/Vol+". When I connect USB or push Power it starts and showing "SONY"-Logo, and that's it.
I can not enter flash-mode by swith off, hold Vol- and connect USB :crying:
What can I do to revive my Z1c?
Thanks for advices
BerWatch!
BerWatch said:
Hello,
I think I bricked my phone
I wanted to upgrade from 4.4.2 to Lollipop http://forum.xda-developers.com/sony-xperia-z1-compact/general/stock-14-6-1-236-customized-lollipop-5-t3264557
And before that I did a factory reset and format data (I got some issues on my phone and wanted to get rid of them).
Now I can not enter TWRP, I can not enter any thing. At the time beeing, after many restarts my red button is broken, I switch it off by "Power/Vol+". When I connect USB or push Power it starts and showing "SONY"-Logo, and that's it.
I can not enter flash-mode by swith off, hold Vol- and connect USB :crying:
What can I do to revive my Z1c?
Thanks for advices
BerWatch!
Click to expand...
Click to collapse
Do you have adb / fastboot on your computer?
levone1 said:
Do you have adb / fastboot on your computer?
Click to expand...
Click to collapse
Yes, I have, but can not enter my phone/don't know how to enter.
I tried switch off (by Power and Vol+), holding Vol- (the same with Vol+) and plug in USB - it starts by showing red light for 2 sec than "SONY", and than stps - no vibration, no light, only steady "SONY"
cmd shows: D:\Programme\Android-Tools\ADB>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
D:\Programme\Android-Tools\ADB>adb reboot recovery
error: device not found
D:\Programme\Android-Tools\ADB>adb reboot bootloader
error: device not found
Phhu, hopefully I do something wrong?!
Install these:
http://developer.sonymobile.com/downloads/drivers/xperia-z1-compact-driver/
and try again
BerWatch said:
Yes, I have, but can not enter my phone/don't know how to enter.
I tried switch off (by Power and Vol+), holding Vol- (the same with Vol+) and plug in USB - it starts by showing red light for 2 sec than "SONY", and than stps - no vibration, no light, only steady "SONY"
cmd shows: D:\Programme\Android-Tools\ADB>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
D:\Programme\Android-Tools\ADB>adb reboot recovery
error: device not found
D:\Programme\Android-Tools\ADB>adb reboot bootloader
error: device not found
Phhu, hopefully I do something wrong?!
Click to expand...
Click to collapse
Power off by holding power and volume up, just wait until it turns off. When it's totally shut off, just hold volume up while plugging in cable and don't let go of volume until you see blue led. Then you're in fastboot mode. If you have drivers installed, it's very easy to get into recovery from there. Report back.
If everything fails...
Install Flashtool on your PC, install the necessary drivers (flashtool helps you with that), download the current firmware in .ftf format and apply it with Flashtool to your phone.
No worries, we all were at your point sometime but you can always recover
Thanks for your hints, folks!
I'll try them tomorrow and give feedback than.
Happened to me once.. Accidentally wiped my data..
Only thing I managed to do is reinstall kk via flashtool
Xperia Z1 Compact .386 rooted
...nothing works.
I have almost everything installed: adb.exe (800kb from 25.07.2013), fastboot.exe (157kb from 25.07.2013), Flashtool (Version 0.9.14.0 built on 12-02-2014 22:45:00), Xperia Companion (Vers. 1.1.24.0), Z1 Compact drivers (device manager says: Sony sa0109 ADB Interface Driver Vers. 2.0.10.30018 from 13.05.2013).
Nothing can connect my Win10-PC via USB3.0 to my phone, it always starts (when I connect it to USB by holding wether Vol+ or Vol-) with red (...pink?) light for about 4sec, followed by showing "SONY" - end of anything.
I'm desperate :crying:
Do you get the green led light when connected in flash mode (vol down when connecting)?
Xperia Z1 Compact LP .386 rooted
No, only red light, than "SONY" without any vibration...
May it be, that usb-debugging was off, whenn I did format data?
BerWatch said:
No, only red light, than "SONY" without any vibration...
May it be, that usb-debugging was off, whenn I did format data?
Click to expand...
Click to collapse
I don't think it's related..
Maybe you don't have the right drivers on pc?
Xperia Z1 Compact LP .386 rooted
The fastboot or flashmode mode should always work - regardless of what you did regarding ROMs or setting or wipe etc.
It is there to save your phone if you messed up.
It is strange that you cant enter these modes. Normally its really a driver issue and you PC does not recognize your phone.
But it seems that you have tried installing them already.
Just to make sure... Your phone charges normally when you plug it in right? So it cant be a broken cable or broken micro-USB connection on your phone?
Also make sure your phone is really shut down - try resetting it with the red button next to your SIM-card slot.
Your volume buttons were fine before right?
Schlengge said:
The fastboot or flashmode mode should always work - regardless of what you did regarding ROMs or setting or wipe etc.
It is there to save your phone if you messed up.
It is strange that you cant enter these modes. Normally its really a driver issue and you PC does not recognize your phone.
But it seems that you have tried installing them already.
Just to make sure... Your phone charges normally when you plug it in right? So it cant be a broken cable or broken micro-USB connection on your phone?
Also make sure your phone is really shut down - try resetting it with the red button next to your SIM-card slot.
Your volume buttons were fine before right?
Click to expand...
Click to collapse
BINGO!!! ...the usb-cable, it's a pretty new one, but I know, the Z1c doesn't like every cable
Now I can enter Flashtools flash and fastboot mode.
I think I lost almost everything on my Z1c, even my TWRP, don't I?
What is now for noobs like me the best way to install this? http://forum.xda-developers.com/sony-xperia-z1-compact/general/stock-14-6-1-236-customized-lollipop-5-t3264557
Many Thanks!
Flash kitkat, root with pc, install twrp recovery, and flash lp rom from recovery
Xperia Z1 Compact LP .386 rooted
Oreltub said:
Flash kitkat, root with pc, install twrp recovery, and flash lp rom from recover/QUOTE]
...uuumpf, but thanks!
Does kiktkat mean 14.4.A.0.108 Android 4.4.4?
Click to expand...
Click to collapse
Yes
Xperia Z1 Compact LP .386 rooted
Thank you all for your input!
It was the usb-cable which did load my Z1c and in this case (no other data on the phone) light the purple LED and display the "SONY"-logo - but nothing else!
All the future problems are more on the software-side (my head) than on the hardware (the cable)...
Haha glad you sorted it out. I don't know why but I also have USB cables in my collection that just won't work with my Z1C... But now you know
If you need further help in restoring with flashtool you can also look up this thread for some helpful links : http://forum.xda-developers.com/showthread.php?t=2631291
Try to get your hands on a .108 firmware (I always keep one on my PC in case I f*** up ). They are easy to root with EasyRoot and from there you can flash dualrecovery. With TWRP you are good to access your backups or flash anything you want again.
Sent from my D5503 using XDA-Developers mobile app
Schlengge said:
Haha glad you sorted it out. I don't know why but I also have USB cables in my collection that just won't work with my Z1C... But now you know
If you need further help in restoring with flashtool you can also look up this thread for some helpful links : http://forum.xda-developers.com/showthread.php?t=2631291
Try to get your hands on a .108 firmware (I always keep one on my PC in case I f*** up ). They are easy to root with EasyRoot and from there you can flash dualrecovery. With TWRP you are good to access your backups or flash anything you want again.
Sent from my D5503 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks - I'll give a feedback when i'm through!
Hi there. After (an attempt) to unlock the bootloader of my A50 and installing TWRP Recovery (TWRP_A50_Magisk_Prepatched) i find myself in an orange bootstate. I can't get it into recovery, download or fastboot mode. It seems like a full brick. I can't even power off the device. Only Volume up, Volume down and Power button let's the device reboot but then the same boot problems appear. Is there anything i can do to recover my phone?
Text of first screen when booting up:
"The phone's bootloader is unlocked and it's software integrity can't be verified. Andy data on this phone may be vulnerable to attackers. Don't store any important or sensitive information on this phone". Press power key to continue"
Text of second screen when booting up:
"The phone is not running Samsung's official software. You may have problems with features or security and you won't be able to install software updates"
Any ideas!?
flash stock via odin
nikolas60 said:
flash stock via odin
Click to expand...
Click to collapse
I have the same problem described as above. To use odin you need access to the download menu. Personally, i can not even access the download menu using any cobination of volume up-down & power combination...
RestrictedPower said:
I have the same problem described as above. To use odin you need access to the download menu. Personally, i can not even access the download menu using any cobination of volume up-down & power combination...
Click to expand...
Click to collapse
caztricum said:
Hi there. After (an attempt) to unlock the bootloader of my A50 and installing TWRP Recovery (TWRP_A50_Magisk_Prepatched) i find myself in an orange bootstate. I can't get it into recovery, download or fastboot mode. It seems like a full brick. I can't even power off the device. Only Volume up, Volume down and Power button let's the device reboot but then the same boot problems appear. Is there anything i can do to recover my phone?
Text of first screen when booting up:
"The phone's bootloader is unlocked and it's software integrity can't be verified. Andy data on this phone may be vulnerable to attackers. Don't store any important or sensitive information on this phone". Press power key to continue"
Text of second screen when booting up:
"The phone is not running Samsung's official software. You may have problems with features or security and you won't be able to install software updates"
Any ideas!?
Click to expand...
Click to collapse
Try connecting your phone to your PC with the USB Type C cable, and do VolDown + Power to reboot the phone, and the moment the screen turns black, press VolUp + VolDown. It'll bring you to a different screen where you can press VolUp to go into download mode for flashing the stock firmware via Odin. I got my stock firmware from https://samfrew.com/all/page/2/#t (you'll need to search for your Model Number - SM-A505F/SM-A505FN/SM-A505FM, and select the correct Region. Also, select the correct Modem Version (the last 4 letters/number of the item to download). Then, follow the "Flashing Guide" at the bottom of the Samfrew page where you downloaded your firmware.
jtanhw said:
Try connecting your phone to your PC with the USB Type C cable, and do VolDown + Power to reboot the phone, and the moment the screen turns black, press VolUp + VolDown. It'll bring you to a different screen where you can press VolUp to go into download mode for flashing the stock firmware via Odin. I got my stock firmware from (you'll need to search for your Model Number - SM-A505F/SM-A505FN/SM-A505FM, and select the correct Region. Also, select the correct Modem Version (the last 4 letters/number of the item to download). Then, follow the "Flashing Guide" at the bottom of the Samfrew page where you downloaded your firmware.
Click to expand...
Click to collapse
This did it for me! Many thanks...
jtanhw said:
download mode for flashing the stock firmware via Odin. I got my stock firmware from https://samfrew.com/all/page/2/#t (you'll need to search for your Model Number - SM-A505F/SM-A505FN/SM-A505FM, and select the correct Region. Also, select the correct Modem Version (the last 4 letters/number of the item to download). Then, follow the "Flashing Guide" at the bottom of the Samfrew page where you downloaded your firmware.
Click to expand...
Click to collapse
I had the same problem and managed to get back to the Download Page.
How do I find out what is the correct region of the correct Modem Version of my phone? It's an S10 (intl unlocked) that I bought in the US from Amazon.
TheAsker70 said:
I had the same problem and managed to get back to the Download Page.
How do I find out what is the correct region of the correct Modem Version of my phone? It's an S10 (intl unlocked) that I bought in the US from Amazon.
Click to expand...
Click to collapse
You can find answers in the S10 forum. But I think the steps will be the same (this is A8 device/forum).
Rexton270 said:
You can find answers in the S10 forum. But I think the steps will be the same (this is A8 device/forum).
Click to expand...
Click to collapse
My bad. Apologize. Will head over there. Thanks!
No bother. Hope you are sorted by now.
this is the exact same problem that goes for me with my samsung a505gn, i flashed a twrp 3.3.1-2_zvox and im stuck at this state. i found my stock firmware at the link provided above, but there are multiple types of a505gn stock firmware (XTC, SMA, GLB), question is, how do i know the correct type of stock firmware to reinstall to my phone, hence, having a limited information of the phone because of this problem (which is stuck at orange bootstate).
Same Problem
caztricum said:
This did it for me! Many thanks...
Click to expand...
Click to collapse
for now work on not sir
i have same problem stuk n auto restart
if u work can u help me thanks
jtanhw said:
try connecting your phone to your pc with the usb type c cable, and do voldown + power to reboot the phone, and the moment the screen turns black, press volup + voldown. It'll bring you to a different screen where you can press volup to go into download mode for flashing the stock firmware via odin. I got my stock firmware from https://samfrew.com/all/page/2/#t (you'll need to search for your model number - sm-a505f/sm-a505fn/sm-a505fm, and select the correct region. Also, select the correct modem version (the last 4 letters/number of the item to download). Then, follow the "flashing guide" at the bottom of the samfrew page where you downloaded your firmware.
Click to expand...
Click to collapse
thank you very much
thanks for your comment, its help me. my Samsung A50 hanged on boot-loader and loop turn on/off.
Is there a way to install twrp if the problem is like this every time I try to install the twrp it came to this problem. Please help me
jtanhw said:
Try connecting your phone to your PC with the USB Type C cable, and do VolDown + Power to reboot the phone, and the moment the screen turns black, press VolUp + VolDown. It'll bring you to a different screen where you can press VolUp to go into download mode for flashing the stock firmware via Odin. I got my stock firmware from https://samfrew.com/all/page/2/#t (you'll need to search for your Model Number - SM-A505F/SM-A505FN/SM-A505FM, and select the correct Region. Also, select the correct Modem Version (the last 4 letters/number of the item to download). Then, follow the "Flashing Guide" at the bottom of the Samfrew page where you downloaded your firmware.
Click to expand...
Click to collapse
Hi this helped me many thanks <3
jtanhw said:
Try connecting your phone to your PC with the USB Type C cable, and do VolDown + Power to reboot the phone, and the moment the screen turns black, press VolUp + VolDown. It'll bring you to a different screen where you can press VolUp to go into download mode for flashing the stock firmware via Odin. I got my stock firmware from https://samfrew.com/all/page/2/#t (you'll need to search for your Model Number - SM-A505F/SM-A505FN/SM-A505FM, and select the correct Region. Also, select the correct Modem Version (the last 4 letters/number of the item to download). Then, follow the "Flashing Guide" at the bottom of the Samfrew page where you downloaded your firmware.
Click to expand...
Click to collapse
thank you so much you just helped me save my phone
peace keeper said:
thank you so much you just helped me save my phone
Click to expand...
Click to collapse
Have you got the a21s? As can't root it, as every twrp source I use soft bricks the phone, or just bootloops, or goes into error at boot up and stops half way. Was thinking trying other custom recovery. Any tips m8?
jtanhw said:
Try connecting your phone to your PC with the USB Type C cable, and do VolDown + Power to reboot the phone, and the moment the screen turns black, press VolUp + VolDown. It'll bring you to a different screen where you can press VolUp to go into download mode for flashing the stock firmware via Odin. I got my stock firmware from https://samfrew.com/all/page/2/#t (you'll need to search for your Model Number - SM-A505F/SM-A505FN/SM-A505FM, and select the correct Region. Also, select the correct Modem Version (the last 4 letters/number of the item to download). Then, follow the "Flashing Guide" at the bottom of the Samfrew page where you downloaded your firmware.
Click to expand...
Click to collapse
My phone is Realme 6 it doesnt take me anywhere my laptop only does the plugging in and plugging out sound all the time and when I let go of the volume buttons the bootloop happens again
caztricum said:
Hi there. After (an attempt) to unlock the bootloader of my A50 and installing TWRP Recovery (TWRP_A50_Magisk_Prepatched) i find myself in an orange bootstate. I can't get it into recovery, download or fastboot mode. It seems like a full brick. I can't even power off the device. Only Volume up, Volume down and Power button let's the device reboot but then the same boot problems appear. Is there anything i can do to recover my phone?
Text of first screen when booting up:
"The phone's bootloader is unlocked and it's software integrity can't be verified. Andy data on this phone may be vulnerable to attackers. Don't store any important or sensitive information on this phone". Press power key to continue"
Text of second screen when booting up:
"The phone is not running Samsung's official software. You may have problems with features or security and you won't be able to install software updates"
Any ideas!?
Click to expand...
Click to collapse
caztricum said:
Hi there. After (an attempt) to unlock the bootloader of my A50 and installing TWRP Recovery (TWRP_A50_Magisk_Prepatched) i find myself in an orange bootstate. I can't get it into recovery, download or fastboot mode. It seems like a full brick. I can't even power off the device. Only Volume up, Volume down and Power button let's the device reboot but then the same boot problems appear. Is there anything i can do to recover my phone?
Text of first screen when booting up:
"The phone's bootloader is unlocked and it's software integrity can't be verified. Andy data on this phone may be vulnerable to attackers. Don't store any important or sensitive information on this phone". Press power key to continue"
Text of second screen when booting up:
"The phone is not running Samsung's official software. You may have problems with features or security and you won't be able to install software updates"
Any ideas!?
Click to expand...
Click to collapse
I HAD the same issue an I resolved it.
There are 2 methods to overcome this problem.
I even wrote a PDF and attached here in this post.
Below is SOME content from the PDF so it could be easy for users to find it on Google. I still strongly recommend you to refer to the PDF attached as it has pictures as well.
Samsung Galaxy M31 / Samsung M31 Screen is stuck on the following error message / error screen:
‘This phone’s bootloader is unlocked and the software integrity can’t be verified. Any data on this phone may be vulnerable to attackers. Don’t store any important or sensitive information on the phone.’
‘The phone is not running Samsung’s official software. You may have problems with features or security. And you won’t be able to install software updates.’ (error screen looks like below):
I was using correct TWRP and I was on Android 11 One UI 3.1.
Just to experiment, I flashed wrong TWRP version which was meant for Android 10 while being on Android 11. And so this problem started. Stuck on the error screen. Phone will not power off or on. Could not even enter the bootloader screen. Nothing works whatever keys I press. The same screen comes up. When the phone goes off and the phone will not accept charging that mean even you it whole night connected to charger, phone will not be charged- the same error screen.
So, the battery was not charging (my battery was at 24% just before this tragedy happened. It was late night and I thought of waking up tomorrow and plug in charger for an hour thinking if its battery is quite charged then I will follow Fix Method 2).
I woke up next morning and the phone was off (Battery drained fully). To this I was happy thinking that I can now hold Volume + and Power key and connect USB cable to enter Bootloader. When I did that phone would enter bootloader and gets switched off automatically (remember the battery was drained completely, charger too failed to charge battery and phone is not drawing enough power from USB port to stay on bootloader. On bootloader screen the phone’s display is fully on so more power usage).
Now I knew that the USB port is not proving enough power so that the phone could remain On while in bootloader when I hold Volume + and Power key and connect USB cable to enter Bootloader. I know for sure that Fix Method 2 will fix this for sure but it’s quite tiring.
So I referred to my PC manual to figure out which USB port provides maximum power. I found the right port (refer pic below):
So now I figured out 5 Volts port and plugged the original white Samsung M31 USB cable into one (refer the pic below):
If you don’t know which USB Port is 5 Volts then I recommend you to try all the ports and try getting to bootloader screen.
So when the phone was off, I pressed and hold the Volume up and Volume down key and with other hand I connected USB cable and now the phone went in bootloader and then I quickly flashed the right TWRP. Disconnected the USB cable and put the phone to charge and now it was accepting charge. Phone was back into life.
So I resolved it by Fix Method 1 below:
Fix Method 1: On my PC, I located the 5 Volts USB port and plugged the original white Samsung M31 USB cable into one (refer the pic below):
Entered Bootloader screen.
How to enter bootloader screen:
Assuming your phone is unlocked and the developers options are on and you have enabled USB debugging in Developer options and you have little knowledge of flashing firmware or TWRP via Odin.
Press and hold Volume Up and Volume down keys together with one hand and using other hand, connect USB cable to phone and release all the keys. Now phone will show bootloader screen which looks like below pic:
I quickly flashed the correct TWRP via Odin:
Flashing TWRP:
· Make sure OEM Unlock is ON in developer settings;
· Turn off the phone;
· Press the volume down + volume up button whilst the phone is connected to a pc to boot in download mode;;
· Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
· Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
· Make sure OEM Unlock is ON in developer settings;
· Turn off the phone;
· Use Vol up + Power + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, factory reset data and redo from step 5!
TWRP screen was up. I tapped on Reboot and it did not reboot because the battery was not enough charged however I saw that TWRP Menu this means TWRP was working so the phone will boot up once it is charged.
Now I plugged in charger and was happy to see the correct charging screen (refer below pic):
I would turn power switch Off and On it quicky to know the charging percentage.
When it reached 20% I started phone (obviously by long pressing power key and it booted up just fine).
I loved myself
Fix Method 2:
Remove the phone’s back cover.
Be careful while removing the back case as you could screw the finger print sensor.
Disconnect the battery connector from motherboard and reconnect it.
Do not turn on the phone. As turning On will again get you back to the same error screen.
Put the back cover on.
Connect charger. Do not turn phone On yet. Wait for 5 min.
Do not even touch the phone.
Now you need to know the percentage of charge so do not hit the power button yet instead locate the main switch to which your charger is connected. Quickly turn Off and On and look at phone it shows charging percentage.
Once charging percentage reached around 20% you can touch your phone and power it on and it should boot up fine. It should not take more than 5 min to boot up.
Atharkhan101 said:
I HAD the same issue an I resolved it.
There are 2 methods to overcome this problem.
I even wrote a PDF and attached here in this post.
Below is SOME content from the PDF so it could be easy for users to find it on Google. I still strongly recommend you to refer to the PDF attached as it has pictures as well.
Samsung Galaxy M31 / Samsung M31 Screen is stuck on the following error message / error screen:
‘This phone’s bootloader is unlocked and the software integrity can’t be verified. Any data on this phone may be vulnerable to attackers. Don’t store any important or sensitive information on the phone.’
‘The phone is not running Samsung’s official software. You may have problems with features or security. And you won’t be able to install software updates.’ (error screen looks like below):
I was using correct TWRP and I was on Android 11 One UI 3.1.
Just to experiment, I flashed wrong TWRP version which was meant for Android 10 while being on Android 11. And so this problem started. Stuck on the error screen. Phone will not power off or on. Could not even enter the bootloader screen. Nothing works whatever keys I press. The same screen comes up. When the phone goes off and the phone will not accept charging that mean even you it whole night connected to charger, phone will not be charged- the same error screen.
So, the battery was not charging (my battery was at 24% just before this tragedy happened. It was late night and I thought of waking up tomorrow and plug in charger for an hour thinking if its battery is quite charged then I will follow Fix Method 2).
I woke up next morning and the phone was off (Battery drained fully). To this I was happy thinking that I can now hold Volume + and Power key and connect USB cable to enter Bootloader. When I did that phone would enter bootloader and gets switched off automatically (remember the battery was drained completely, charger too failed to charge battery and phone is not drawing enough power from USB port to stay on bootloader. On bootloader screen the phone’s display is fully on so more power usage).
Now I knew that the USB port is not proving enough power so that the phone could remain On while in bootloader when I hold Volume + and Power key and connect USB cable to enter Bootloader. I know for sure that Fix Method 2 will fix this for sure but it’s quite tiring.
So I referred to my PC manual to figure out which USB port provides maximum power. I found the right port (refer pic below):
So now I figured out 5 Volts port and plugged the original white Samsung M31 USB cable into one (refer the pic below):
If you don’t know which USB Port is 5 Volts then I recommend you to try all the ports and try getting to bootloader screen.
So when the phone was off, I pressed and hold the Volume up and Volume down key and with other hand I connected USB cable and now the phone went in bootloader and then I quickly flashed the right TWRP. Disconnected the USB cable and put the phone to charge and now it was accepting charge. Phone was back into life.
So I resolved it by Fix Method 1 below:
Fix Method 1: On my PC, I located the 5 Volts USB port and plugged the original white Samsung M31 USB cable into one (refer the pic below):
Entered Bootloader screen.
How to enter bootloader screen:
Assuming your phone is unlocked and the developers options are on and you have enabled USB debugging in Developer options and you have little knowledge of flashing firmware or TWRP via Odin.
Press and hold Volume Up and Volume down keys together with one hand and using other hand, connect USB cable to phone and release all the keys. Now phone will show bootloader screen which looks like below pic:
I quickly flashed the correct TWRP via Odin:
Flashing TWRP:
· Make sure OEM Unlock is ON in developer settings;
· Turn off the phone;
· Press the volume down + volume up button whilst the phone is connected to a pc to boot in download mode;;
· Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
· Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
· Make sure OEM Unlock is ON in developer settings;
· Turn off the phone;
· Use Vol up + Power + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, factory reset data and redo from step 5!
TWRP screen was up. I tapped on Reboot and it did not reboot because the battery was not enough charged however I saw that TWRP Menu this means TWRP was working so the phone will boot up once it is charged.
Now I plugged in charger and was happy to see the correct charging screen (refer below pic):
I would turn power switch Off and On it quicky to know the charging percentage.
When it reached 20% I started phone (obviously by long pressing power key and it booted up just fine).
I loved myself
Fix Method 2:
Remove the phone’s back cover.
Be careful while removing the back case as you could screw the finger print sensor.
Disconnect the battery connector from motherboard and reconnect it.
Do not turn on the phone. As turning On will again get you back to the same error screen.
Put the back cover on.
Connect charger. Do not turn phone On yet. Wait for 5 min.
Do not even touch the phone.
Now you need to know the percentage of charge so do not hit the power button yet instead locate the main switch to which your charger is connected. Quickly turn Off and On and look at phone it shows charging percentage.
Once charging percentage reached around 20% you can touch your phone and power it on and it should boot up fine. It should not take more than 5 min to boot up.
Click to expand...
Click to collapse
Atharkhan101 said:
I HAD the same issue an I resolved it.
There are 2 methods to overcome this problem.
I even wrote a PDF and attached here in this post.
Below is SOME content from the PDF so it could be easy for users to find it on Google. I still strongly recommend you to refer to the PDF attached as it has pictures as well.
Samsung Galaxy M31 / Samsung M31 Screen is stuck on the following error message / error screen:
‘This phone’s bootloader is unlocked and the software integrity can’t be verified. Any data on this phone may be vulnerable to attackers. Don’t store any important or sensitive information on the phone.’
‘The phone is not running Samsung’s official software. You may have problems with features or security. And you won’t be able to install software updates.’ (error screen looks like below):
I was using correct TWRP and I was on Android 11 One UI 3.1.
Just to experiment, I flashed wrong TWRP version which was meant for Android 10 while being on Android 11. And so this problem started. Stuck on the error screen. Phone will not power off or on. Could not even enter the bootloader screen. Nothing works whatever keys I press. The same screen comes up. When the phone goes off and the phone will not accept charging that mean even you it whole night connected to charger, phone will not be charged- the same error screen.
So, the battery was not charging (my battery was at 24% just before this tragedy happened. It was late night and I thought of waking up tomorrow and plug in charger for an hour thinking if its battery is quite charged then I will follow Fix Method 2).
I woke up next morning and the phone was off (Battery drained fully). To this I was happy thinking that I can now hold Volume + and Power key and connect USB cable to enter Bootloader. When I did that phone would enter bootloader and gets switched off automatically (remember the battery was drained completely, charger too failed to charge battery and phone is not drawing enough power from USB port to stay on bootloader. On bootloader screen the phone’s display is fully on so more power usage).
Now I knew that the USB port is not proving enough power so that the phone could remain On while in bootloader when I hold Volume + and Power key and connect USB cable to enter Bootloader. I know for sure that Fix Method 2 will fix this for sure but it’s quite tiring.
So I referred to my PC manual to figure out which USB port provides maximum power. I found the right port (refer pic below):
So now I figured out 5 Volts port and plugged the original white Samsung M31 USB cable into one (refer the pic below):
If you don’t know which USB Port is 5 Volts then I recommend you to try all the ports and try getting to bootloader screen.
So when the phone was off, I pressed and hold the Volume up and Volume down key and with other hand I connected USB cable and now the phone went in bootloader and then I quickly flashed the right TWRP. Disconnected the USB cable and put the phone to charge and now it was accepting charge. Phone was back into life.
So I resolved it by Fix Method 1 below:
Fix Method 1: On my PC, I located the 5 Volts USB port and plugged the original white Samsung M31 USB cable into one (refer the pic below):
Entered Bootloader screen.
How to enter bootloader screen:
Assuming your phone is unlocked and the developers options are on and you have enabled USB debugging in Developer options and you have little knowledge of flashing firmware or TWRP via Odin.
Press and hold Volume Up and Volume down keys together with one hand and using other hand, connect USB cable to phone and release all the keys. Now phone will show bootloader screen which looks like below pic:
I quickly flashed the correct TWRP via Odin:
Flashing TWRP:
· Make sure OEM Unlock is ON in developer settings;
· Turn off the phone;
· Press the volume down + volume up button whilst the phone is connected to a pc to boot in download mode;;
· Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
· Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
· Make sure OEM Unlock is ON in developer settings;
· Turn off the phone;
· Use Vol up + Power + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, factory reset data and redo from step 5!
TWRP screen was up. I tapped on Reboot and it did not reboot because the battery was not enough charged however I saw that TWRP Menu this means TWRP was working so the phone will boot up once it is charged.
Now I plugged in charger and was happy to see the correct charging screen (refer below pic):
I would turn power switch Off and On it quicky to know the charging percentage.
When it reached 20% I started phone (obviously by long pressing power key and it booted up just fine).
I loved myself
Fix Method 2:
Remove the phone’s back cover.
Be careful while removing the back case as you could screw the finger print sensor.
Disconnect the battery connector from motherboard and reconnect it.
Do not turn on the phone. As turning On will again get you back to the same error screen.
Put the back cover on.
Connect charger. Do not turn phone On yet. Wait for 5 min.
Do not even touch the phone.
Now you need to know the percentage of charge so do not hit the power button yet instead locate the main switch to which your charger is connected. Quickly turn Off and On and look at phone it shows charging percentage.
Once charging percentage reached around 20% you can touch your phone and power it on and it should boot up fine. It should not take more than 5 min to boot up.
Click to expand...
Click to collapse
Hi, friend. I have the same problem. But I don't even have a bootloader. When I log in, I just get a black screen.
Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks
Call whoever you bought the phone from and do warranty claim.
I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.
Baumhouse said:
I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.
Click to expand...
Click to collapse
rao_hamza said:
Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks
Click to expand...
Click to collapse
rao_hamza said:
Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks
Click to expand...
Click to collapse
Bootloader unlocked?
cultofluna said:
Bootloader unlocked?
Click to expand...
Click to collapse
If I remeber correctly flashing factory images forces you to unlock the device. So yes, the bootloader of rao_hamza's device should be unlocked.
From memory you can revive it through QPST and orher Qualcomm utilities, however hard part is to get the files. the phone is too new and many shops dont have the unlock tools yet.
" While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone. " - this is still good news, as phone is being detected by windows, try to install Qualcomm drivers and see if you can get it to boot into EDL. GOOD LUCK.
Pixel 6 uses Google's own new Tensor chip - so no Qualcomm tools
Like @Baumhouse I went through something similar. Two things for me: it took way longer to hold power and volume down than any other phone I've owned. I was seriously concerned I wasn't going to get there. Two, the factory images all made it to fastbootd and then failed all because I hadn't updated to the latest SDK.
Just throwing this out in hopes you don't have to send it back.
What @ridobe said. Make sure you're using the latest official Google Platform Tools (there's a link in my thread at the top of my signature below if you need it, or just Google for it). If I had a nickel every time someone didn't update the tools when they went to use them...
roirraW edor ehT said:
What @ridobe said. Make sure you're using the latest official Google Platform Tools (there's a link in my thread at the top of my signature below if you need it, or just Google for it). If I had a nickel every time someone didn't update the tools when they went to use them...
Click to expand...
Click to collapse
This and a bad/wrong cable seem to be the most common culprits
ridobe said:
Like @Baumhouse I went through something similar. Two things for me: it took way longer to hold power and volume down than any other phone I've owned. I was seriously concerned I wasn't going to get there. Two, the factory images all made it to fastbootd and then failed all because I hadn't updated to the latest SDK.
Just throwing this out in hopes you don't have to send it back.
Click to expand...
Click to collapse
Any idea how long you had to hold that button combinaiton? I tried longer, maybe 60 sec, but still no response from the phone.
tids2k said:
From memory you can revive it through QPST and orher Qualcomm utilities, however hard part is to get the files. the phone is too new and many shops dont have the unlock tools yet.
" While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone. " - this is still good news, as phone is being detected by windows, try to install Qualcomm drivers and see if you can get it to boot into EDL. GOOD LUCK.
Click to expand...
Click to collapse
What is EDL? and had the Google usb drivers installed, to get the fastboot working.
Baumhouse said:
I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.
Click to expand...
Click to collapse
Yes, I don't know who to get into a bootloader in this situation, if that were working I would have some hope.
If you can get to the bootloader you can use google's flashing website, flash.android.com. I just use that to go back to stock, even with an unlocked bootloader.
pysklona said:
If you can get to the bootloader you can use google's flashing website, flash.android.com. I just use that to go back to stock, even with an unlocked bootloader.
Click to expand...
Click to collapse
Thanks @pysklona. you are right, but the problem is I can't get into the bootloader. This is what I am seeking help for.
rao_hamza said:
Thanks @pysklona. you are right, but the problem is I can't get into the bootloader. This is what I am seeking help for.
Click to expand...
Click to collapse
Sorry, misread the post.
@pysklona came here because I'm in the same boat, hard-bricked my device after running the flash-all script. Was using the most recent version of platform tools and the brand new cable that came with the phone.
Was getting the same result, attaching it to a windows pc makes the attached device chime, but disconnects after a few seconds. It came up first as "Setting up Pixel ROM Recovery". I let it sit overnight and now it doesn't auto-disconnect and I get a serial device under com3 on windows. Attaching it to macos gives me a "Pixel ROM Recovery" device. Despite "recovery" in the name, I think it's actually in EDL mode, not recovery mode. No devices come up for adb or fastboot on windows, linux or macos. Screen is completely blank no matter what.
Not being a Qualcomm chip makes this whole process from here a bit of an unknown, but will assume the process for recovery is more or less the same. Looking into QPST/MsmDownloadTool/OpenPST, although as pointed out, I'm not sure any of those tools will work since this isn't a qualcomm chip. MsmDownloadTool is for oneplus, but maybe something can be modded.
ootri said:
@pysklona came here because I'm in the same boat, hard-bricked my device after running the flash-all script. Was using the most recent version of platform tools and the brand new cable that came with the phone.
Was getting the same result, attaching it to a windows pc makes the attached device chime, but disconnects after a few seconds. It came up first as "Setting up Pixel ROM Recovery". I let it sit overnight and now it doesn't auto-disconnect and I get a serial device under com3 on windows. Attaching it to macos gives me a "Pixel ROM Recovery" device. Despite "recovery" in the name, I think it's actually in EDL mode, not recovery mode. No devices come up for adb or fastboot on windows, linux or macos. Screen is completely blank no matter what.
Not being a Qualcomm chip makes this whole process from here a bit of an unknown, but will assume the process for recovery is more or less the same. Looking into QPST/MsmDownloadTool/OpenPST, although as pointed out, I'm not sure any of those tools will work since this isn't a qualcomm chip. MsmDownloadTool is for oneplus, but maybe something can be modded.
Click to expand...
Click to collapse
Thanks for sharing your experience. I just returned the device and got myself a new one.
anyways, i am not sure what is causing this hard brick. thats is something we all should be careful about it.
same thing here. pixel 6 from google store. magisk installed on the december update and i downgraded to the november one using the flash-all.bat script. phone reboots and am told the software is corrupt
reboot back into fastboot mode, run the script again. and get this software is corrupt message again
this time I cant' even boot into fastboot/bootloader mode. and plugging the phone into windows gives me the "pixel rom recovery" message
phone seems dead (black screen, not responding to hardware buttons)
any other solutions than to get it replaced?
Hmm, maybe plug it in to a PC via USB to supply it with power (maybe the battery is down) and just do a very long press of the power button - at least 30 seconds - until the phone starts up. If it does and isn't in fastboot you could try "Power-VolDown" to get into fastboot...
If it just doesn't react to all of this and waiting a bit (in case the battery was at 0% and needs some minimal charge) I think a replacement is the only way to go....
Enddo said:
same thing here. pixel 6 from google store. magisk installed on the december update and i downgraded to the november one using the flash-all.bat script. phone reboots and am told the software is corrupt
reboot back into fastboot mode, run the script again. and get this software is corrupt message again
this time I cant' even boot into fastboot/bootloader mode. and plugging the phone into windows gives me the "pixel rom recovery" message
phone seems dead (black screen, not responding to hardware buttons)
any other solutions than to get it replaced?
Click to expand...
Click to collapse
You could try Official Google Android Flash Tool. It's merely another method of doing what you effectively tried, but from what I've read, it's helped some folks. Sadly, others have reported that the Official Google Pixel Update and Software Repair hasn't been updated for the P6P yet.
If that doesn't help, hang in there. There are others in here who will likely have even better advice.
roirraW edor ehT said:
You could try Official Google Android Flash Tool. It's merely another method of doing what you effectively tried, but from what I've read, it's helped some folks. Sadly, others have reported that the Official Google Pixel Update and Software Repair hasn't been updated for the P6P yet.
If that doesn't help, hang in there. There are others in here who will likely have even better advice.
Click to expand...
Click to collapse
appreciate the links. right now, I can't even get into fastboot/bootloader mode. so neither of those tools detect the phone.
@s3axel the battery definitely isn't low. I charged it up before all this specifically so that I know it had plenty of juice (was at 93% or something).
I'm thinking maybe after letting the battery die, charging it back up will let me boot into a special boot mode
but any other ideas, please, I'm all ears
[SOLVED see post below]
Hi all,
Just bricked my Phone and can't access MSM. Hope you can help me. I will try to be very clear on the steps I took to get to this point.
Device: EU OnePlus 9 Pro
What is was trying to do: Go from rooted C.47 to Pixel Entended ROM
What I did:
Code:
Unrooted using Magisk uninstall option
Updated to c.48 through OTA
Go to lineageOS page on how to ensure all firmware partitions are consistent
very stupidly did not flash dtbo and vendor boot partition
did adb reboot fastboot in stead of abd reboot bootloader
Download the "lineage-19.1-20220701-recovery-lemonadep.img" and tried to temporaryly flash it by
fastboot flash boot <recovery_filename>.img
This resulted in the device getting stuck on the 1+ boot logo.
I can still force turn it off by holding Volume Up + Power.
When I try to access EDL by turned off and Vol UP + Vol Down + Plug and release, My PC makes a connection sound and the screen stay black for a while. After +- 10 seconds, the PC makes a disconnection sound and the phone boots up and gets stuck again on the 1+ bootup icon.
Also my phone won't stay turned off when plugged in the charger or pc
Yes, but what is it presenting as (i.e. EDL, fastboot, ADB, UMS...) when it connects?
If this is Windows, UsbLog.exe is handy to identify things popping up (as long as they have drivers installed).
For a list of devices that have ever tried to connect, try "enumusb.exe /l".
Both available here: https://www.temblast.com/windows.htm
Renate said:
Yes, but what is it presenting as (i.e. EDL, fastboot, ADB, UMS...) when it connects?
If this is Windows, UsbLog.exe is handy to identify things popping up (as long as they have drivers installed).
For a list of devices that have ever tried to connect, try "enumusb.exe /l".
Both available here: https://www.temblast.com/windows.htm
Click to expand...
Click to collapse
I will try this
I found the issue:
> EDL exits after 10 seconds if it is not captured by the MSM tool.
> The MSM tool only monitored 4 of my 10 USB ports
> So it was not captured because I was plugged in to an unmonitored USB port and rebooted after 10 seconds
> I have successfully used the MSM tool now
Oh! A bit off-topic, but I have never understood why EDL is commonly used over a "serial" port.
The interface that EDL presents is a generic USB bulk interface with two endpoints. You can use it just like that.
But no. They have to use a Qualcomm driver that makes it look like a "serial" port and then you can connect to that.
Me? I use a generic "WinUSB" Zadig driver. I have an EDL client that just connects to that fine.
So does the Python client implementation.
Also, I've never run into that 10 second timeout.
TraktorHenk said:
[SOLVED see post below]
Hi all,
Just bricked my Phone and can't access MSM. Hope you can help me. I will try to be very clear on the steps I took to get to this point.
Device: EU OnePlus 9 Pro
What is was trying to do: Go from rooted C.47 to Pixel Entended ROM
What I did:
Code:
Unrooted using Magisk uninstall option
Updated to c.48 through OTA
Go to lineageOS page on how to ensure all firmware partitions are consistent
very stupidly did not flash dtbo and vendor boot partition
did adb reboot fastboot in stead of abd reboot bootloader
Download the "lineage-19.1-20220701-recovery-lemonadep.img" and tried to temporaryly flash it by
fastboot flash boot <recovery_filename>.img
This resulted in the device getting stuck on the 1+ boot logo.
I can still force turn it off by holding Volume Up + Power.
When I try to access EDL by turned off and Vol UP + Vol Down + Plug and release, My PC makes a connection sound and the screen stay black for a while. After +- 10 seconds, the PC makes a disconnection sound and the phone boots up and gets stuck again on the 1+ bootup icon.
Also my phone won't stay turned off when plugged in the charger or pc
Click to expand...
Click to collapse
Your phone needs to be in OFF state mode when you're using EDL.
So, very simple:
Enter bootloader mode by holding both volume buttons with the power button together till your phone restarts and enters the bootloader.
From the bootloader screen you can use the volume buttons to navigate through the choices and you can select "Switch off".
When you complete this, you need to hold both volume buttons, and while holding them connect the cable (PC).
If you don't have or you don't have the correct Qualcomm EDL drivers installed, your phone will reboot or start to boot, it won't stay in EDL mode for longer than 10 seconds.
I also got the correct drivers for you, but you need to install the drivers manually while your device is in "EDL" mode, so, you need to be a bit "fast".
I have even a video for you, but need to upload it to YouTube so you can watch it.
I'll share you here the drivers just in case if you're familiar with a manual installation of the drivers.
ekin_strops said:
Your phone needs to be in OFF state mode when you're using EDL.
So, very simple:
Enter bootloader mode by holding both volume buttons with the power button together till your phone restarts and enters the bootloader.
From the bootloader screen you can use the volume buttons to navigate through the choices and you can select "Switch off".
When you complete this, you need to hold both volume buttons, and while holding them connect the cable (PC).
If you don't have or you don't have the correct Qualcomm EDL drivers installed, your phone will reboot or start to boot, it won't stay in EDL mode for longer than 10 seconds.
I also got the correct drivers for you, but you need to install the drivers manually while your device is in "EDL" mode, so, you need to be a bit "fast".
I have even a video for you, but need to upload it to YouTube so you can watch it.
I'll share you here the drivers just in case if you're familiar with a manual installation of the drivers.
Click to expand...
Click to collapse
Thanks for the help. The problem ended up to be a bit different than this for me, but this is a good post for anyone to find in the future!