306SH logo screen freeze on boot - Sharp Aquos Crystal

Hi all,
I have just recently rooted my 306SH, the rooting process was fine. The problem started when I flashed an incompatible twrp image. Now I can't boot into anything it seems, no recovery, no fastboot and the power button will show only the logo screen. If connected to a power source the red led light will stay on even if unplugged. The device can be completely shut down and the red light off if I hold the down+volume and power down for few seconds.
I can connect it to my computer via usb by holding up+volume and power (green led light) . I installed google usb driver onto the android device and it stays connected for about 30 seconds to 1 minute. I tried using command prompt and SDK by typing "adb reboot recovery" but get an error message "error: device '(null)' not found.
Things I have installed on my computer:
(ADB, fast boot and drivers) https://forum.xda-developers.com/showthread.php?p=48915118#post48915118
SDK Platform-tools
306SH:
Google USB driver
Is there anything I can do from my computer? I was thinking maybe I can flash in an image to replace it. And also my sim card pops out and can't be set back in, is this due to the incorrect flashing?
Any help or input is greatly appreciated, I've been working on this for a while and is getting no where.

Related

[Q] Hard Brick fastboot issues

Ok so here's what happened.
Couple days ago I mistakenly selected "install now" while attempting to postpone the OTA on my VS980. Phone was rooted on stock ROM via stump root and I had not installed a custom recovery yet.
Phone then would only show the LG screen and display an error. No download mode or recovery.
So I utilized a VM running Ubuntu and pushed the sdl1, aboot, rpm, tz and TWRP 2.7 to the phone.
upon restart of the phone It would only start up into fastboot mode. The only other thing it would do is bring up the hardware key mode ( done by pressing vol-, pwr, vol+ at the same time)
Phone would report two errors upon being plugged into the computer and the computer only recognizes the phone as an adb device in device manager
"EP1/out FAIL nfo=40pg0=f910700"
"usb_read() transaction failed"
So I installed the adb on windows and in terminal on Ubuntu. I also installed the unified LG drivers, SDK and the google USB drivers. I now get the same error messages but the fastboot mode now constantly resets.
here is what it goes through
"fastboot mode started"
"reset"
"portcharge"
"fastboot: processing commands"
"reset"
"EP1/out FAIL nfo=40pg0=f910700"
"portcharge"
"usb_read() transaction failed"
"fastboot: oops!"
"fastboot: processing commands"
"reset"
"EP1/out FAIL nfo=40pg0=f910700"
"portcharge"
"usb_read() transaction failed"
"fastboot: oops!"
"fastboot: processing commands"
this goes on and on....
any ideas on where to go from here?
You could try pushing fal.img like you've pushed those other files, rather than using the fastboot.
Id love too, but my comp isn't recognizing the phone when plugged in
Were you in bulk mode originally when you wrote the partitions to the phone? If so, i'm surprised you can't enter twrp. Just to rule out and error, be sure you're holding down power for no less than 15 seconds to power off the phone all the way. Then press and hold both volume down and power simultaneusly until the lg logo comes up. Then quickly release both buttons and immediatly press and hold them both again until the factory reset screen comes up. Accept factory reset to enter twrp.
If that is all a rehash, so be it. Just want to make sure you're using the correct method. Many people fail to hold down power long enough on the initlal shutdown making all the steps after that a moot point. Also you don't want to be connected to usb when doing the above procedure.

Nexus 7 - cannot enter fastboot mode

Hi,
a friend gave me a "broken" Nexus7 which is in a boot loop since she tried to flash Ubuntu on it. But I got stuck because I cannot enter fastboot mode.
When I start the Nexus 7, it shows the Google logo (with closed lock symbol). After approximately 15 seconds the Ubuntu start screen logo appears. After another 15 seconds it reboots.
I already tried the following:
1.) Entering fastboot mode by starting with power button & volume down -> boot loop
2.) Make sure it's really a fresh start by opening the tablet, removing the battery cable, connecting the battery cable, trying to enter fastboot mode
3.) Connecting it with my PC (running on Linux) and trying to issue commands to the tablet:
lsusb shows vendor and product id, so it kind of recognizes the tablet
adb devices shows a serial id + "recovery" during the time in which the Ubuntu logo is displayed
I cannot enter any adb commands -> error: protocol fault (no status)
fastboot devices shows no device in any of the stages of boot loop
Interesting thing is that in Ubuntu the only possibility to power off the device is pressing the volume up key for a few seconds.... the power key doesn't do anything anymore if the device is during its boot loop...
There must be a bootloader, otherwise it would not try to load Ubuntu. Maybe the recovery bootloader (fastboot) got somehow overwritten?
Can I do anything else in software, or do I have to replace some hardware to make it work again?

Bootloop and red light on recovery

Hi,
I have a nexus 4 that is stuck on opening animation and won't go to fastboot\recovery.
(a weight fell on it a long time ago. Worked for the next 3 days then died.)
Situation now is that it is stuck on the opening animation (lollipop) when turned on.
When trying to go to fastboot using volume up+down+power I get a blinking red light (volume up\down only with power button only resets the device or turns it off.)
Computer recognizes the device and I can see it in ADB devices while stuck on opening animation, but it says "unauthorized" so I can't use "adb reboot recovery" command.
Trying to press up+down+power while connected to computer gives solid red light and repetitive "device connected" sound from the computer every 1 sec.
Phone was never rooted or flashed in any way.
Any idea what I can do? I don't mind restoring factory image or factory reset.
Thanks to anyone who tries to help in advance

Hard brick of Z5C ... can I save it?

Well, I did it this time.
In a valiant attempt to install a custom ROM, I erased every partition using fastboot,
Code:
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot erase recovery
fastboot erase cache
Now what I meant to do here was flash a recovery, using
Code:
//fastboot flash recovery TWRP.img
but repeating this so many times over the last 48 hours, I did not do above and instead went quickly right into below,
Code:
fastboot reboot
The system rebooted as I told it to ... right into a black void of nothing. Now their is no 'recovery' image and no 'bootloader' image ... the phone is hard bricked, won't turn on at all, dead. I was so close to getting to the custom ROM! Is there any chance to get it back into recovery mode? or have I learned a $350 lesson?
Edit: Further research indicates it may be possible to force the system into fastboot using a USB jig. Has anyone tried this method?
apsommer said:
Well, I did it this time.
In a valiant attempt to install a custom ROM, I erased every partition using fastboot,
Code:
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot erase recovery
fastboot erase cache
Now what I meant to do here was flash a recovery, using
Code:
//fastboot flash recovery TWRP.img
but repeating this so many times over the last 48 hours, I did not do above and instead went quickly right into below,
Code:
fastboot reboot
The system rebooted as I told it to ... right into a black void of nothing. Now their is no 'recovery' image and no 'bootloader' image ... the phone is hard bricked, won't turn on at all, dead. I was so close to getting to the custom ROM! Is there any chance to get it back into recovery mode? or have I learned a $350 lesson?
Edit: Further research indicates it may be possible to force the system into fastboot using a USB jig. Has anyone tried this method?
Click to expand...
Click to collapse
When you plug it in while holding volume up what happens?
TheVan28 said:
When you plug it in while holding volume up what happens?
Click to expand...
Click to collapse
Nothing. LED flashes red every few seconds. The same response if plugging it in without holding volume up. Along these same lines, holding the power button on for a few seconds causes the small vibration haptic feedback to occur as if it is turning on normally ... but nothing happens the phone remains dead. Similarly, holding volume down and the power key causes a small vibration haptic feedback as it was booting into recovery ... but nothing happens the phone remains dead. I haven't seen anything on the screen appear, or the phone turn on it any way, since executing the fastboot sequence previously described.
Whatever you did, you should still be able to enter in flash mode and flash a stock firmware. And by this I mean full stock firmware, not a ROM.
Sent from my E5823 using Tapatalk
Ilko said:
Whatever you did, you should still be able to enter in flash mode and flash a stock firmware. And by this I mean full stock firmware, not a ROM.
Sent from my E5823 using Tapatalk
Click to expand...
Click to collapse
Ok, that would be great. I would be thrilled to get the stock ROM back, at this point getting the phone to turn on at all would be a victory! Would you please describe precisely how to do enter flash mode with the phone in the current state? To reiterate, the phone will not turn on in any way (normally, or volume down + power to boot into recovery). The only life in the device is a slow blinking red LED when it's plugged in, and a quick vibration after holding the power button. The screen has not turned on in any way, or the LED shown any color other than red, since executing the fastboot sequence previously described.
hold power button + volume up and to force shutdown
and then hold volume up (or down, i don't quite remember) while connecting it to a pc (hold the button while connecting the usb cable).
If the led turns green or blue, congrats
The power key has nothing to do in this context. It is used only to boot into recovery or force OFF.
While holding VOL ↑, plug the USB cable to your PC to enter into fastboot mode (blue light)
While holding VOL ↓, plug the USB cable to your PC to enter into flash mode (green light, or maybe nothing)
TheVan28 said:
hold power button + volume up and to force shutdown
and then hold volume up (or down, i don't quite remember) while connecting it to a pc (hold the button while connecting the usb cable).
If the led turns green or blue, congrats
Click to expand...
Click to collapse
Nothing. Device still unresponsive as described.
does your PC detect the device ? (new device sound notification)
Ilko said:
does your PC detect the device ? (new device sound notification)
Click to expand...
Click to collapse
No, the PC does not currently detect the device. All drivers are correctly installed as the phone was recognized accurately prior to the described fastboot sequence.
This is weird. I already erased everyting via fastboot too a while ago, and I could still flash it.
Just to be sure.... unplug all other "smart device" before anything (drivers can't handle more than one device at a time when it comes to FB or flash mode). Open the device manager and let it to the foreground. While you hold the vol down key, plug it and keep holding it until the device is detected. Don't expect any reaction on phone's screen, it remains OFF in both fastboot and flash mode. So, if the device manager reacts, you win.
Ilko said:
This is weird. I already erased everyting via fastboot too a while ago, and I could still flash it.
Just to be sure.... unplug all other "smart device" before anything (drivers can't handle more than one device at a time when it comes to FB or flash mode). Open the device manager and let it to the foreground. While you hold the vol down key, plug it and keep holding it until the device is detected. Don't expect any reaction on phone's screen, it remains OFF in both fastboot and flash mode. So, if the device manager reacts, you win.
Click to expand...
Click to collapse
I'm getting something here which is very encouraging! Executing your sequence causes the device manager to blink (refresh) as if it sees something, however no new devices are recognized in the tree. The phone LED goes to a solid green, reminiscent of a fully charged battery, stays on for about 30 seconds, briefly blinks red and then back to green, etc. The device manager is certainly reacting here it just doesn't recognize the device.
So here we are, you win. Because you have the "two", detection and green led. And if this state goes off after a certain time, it is normal. There is a kind of countdown and the device quits that mode if nothing is sent to it. You should be able to flash a firmware now with flashtool software.
Just ensure you have proper drivers installed properly (WinUSB drivers need to turn signature verification OFF before or Windows will block the installation)
Ilko said:
So here we are, you win. Because you have the "two", detection and green led. And if this state goes off after a certain time, it is normal. There is a kind of countdown and the device quits that mode if nothing is sent to it. You should be able to flash a firmware now with flashtool software.
Just ensure you have proper drivers installed properly (WinUSB drivers need to turn signature verification OFF before or Windows will block the installation)
Click to expand...
Click to collapse
Unbelievable! You saved me! I'm back up with the stock ROM and peace of mind to attempt the custom ROM process again. Saved me $350 ... thank you!!
That's great : )
It is almost impossible to hard brick a Xperia. If something goes wrong, remember flashtool ^^

I only can reach the Bootmenu. Bricked? What can I do?

Hi,
I'm not very experienced with those root things and followed a tutorial to do so.
I unlocked the bootloader, had TWRP installed and root. This worked. Now I wanted to remove Root and TWRP and go back to the original state. I couldn't find the stock recovery file, so I installed the P996A04V1.3.0B13_MR2_sd_ssl.zip via TWRP from the SD Card. Till here it worked. I could enter the stock recover and boot the phone.
Then Android wanted to install a security update. I allowed it and this is where the problem started.
The install process stood still on 25% for minutes. I thought it stuck and pressed and hold the power button to reboot that I can wipe the memory. But nothing happened. But the installation Process continued suddenly. I had the feeling that this power key worked like a skip key. So maybe it didn't install a file where it was stuck.
After the installation reached 100% the screen switched to black and nothing worked anymore. I couldn't restart the phone or anything but I think the phone was doing something cause it consumed electricity. When I checked the phone hours later I noticed it was empty.
I can reach the unlocked bootloader now, but none of the selections works. Doing nothing to boot or select Recovery lead to black screen and stuck. Then I have to wait until the battery is empty again. Fastboot, Power Off just restart the phone and I end in the Bootmenu again. I can't even fully charge the phone. As soon as it has enough power to start the Bootmenu appears. So I don't see the display of the charging process.
I don't understand how this could happen. I tried different key combinations when the phone had enough electricty to start. The phone always restarts and end in the bootmenu. Only when I press all three keys it's standing still on the ZTE Logo screen but as soon as I release the keys I end again in the bootmenu.
How can I force another Update?
regards
Let' start with the basic questions:
Do you have proper backup of your data?
Which Android Version did your Axon had before it went unusable?
You could try to reflash TWRP.
Boot your phone into bootmode.
Download a proper TWRP Image on your PC (https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547)
Open a cmd shell (press the windows key and type 'cmd' -> press enter)
Navigate to the folder where the TWRP Image is stored ('
Code:
cd C:\Users\[I]YOUR_USER_NAME[/I]\Downloads\
')
Type: '
HTML:
fastboot flash recovery [I]TWRP_IMG_NAME.img[/I]
'
Afterwards you could try to reboot into recovery mode.
I don't have a backup. But there isn't something imortant on the phone that I want to keep. I can do a full reset and reinstall, too.
Android must have been the latest offical availabe what's in the file. Was it Android 8? V1.3.0B13
The fastboot mode doesn't work. The screen turns black and the LED blinks red but only for a moment. Then the phone restarts and I'm in the bootmenu again. Windows doesn't recognize it as device.
Is there a way to force it to do an update from my SDCard without it needed to be connected to a PC?
Stevie123 said:
I don't have a backup. But there isn't something imortant on the phone that I want to keep. I can do a full reset and reinstall, too.
Android must have been the latest offical availabe what's in the file. Was it Android 8? V1.3.0B13
The fastboot mode doesn't work. The screen turns black and the LED blinks red but only for a moment. Then the phone restarts and I'm in the bootmenu again. Windows doesn't recognize it as device.
Is there a way to force it to do an update from my SDCard without it needed to be connected to a PC?
Click to expand...
Click to collapse
I don't know of any.
But you could boot into EDL Mode (Press and hold Both Volume button and then press the power button) and flash a Stock EDL rom from the Download Center i have linkd before.
It's not visible for the PC. The only thing I see is the charging screen when its total empty and you can't even boot as. As soon as it has enough power to switch to the normal screen the bootloader appears and when I do nothing the screen turns black and nothing happens. I don't even know if it is charging. The LED is off.
Follow this guide to unbrick it and then use MiFlash and flash an EDL ROM
https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229

Categories

Resources