I have an original Onn 10.1 (no keyboard) that's bricked. I didn't mess around with anything. Tried to use it one day and it was bricked.
When I plug in the battery charge animation runs on the screen (screen isn't dead) and the battery does charge. Hitting the power button does nothing. Various combinations of power + volume do nothing.
I followed the guide here (thanks CaffeinePizza) and was able to successfully format then flash the stock ROM from this post (thanks NFSP G35). Both operations ran fine and gave the success check mark in SP Flash Tools.
The tablet is just as bricked as before. It behaves the same. Is there anything else to try?
Related
One day my defy (which used MIUI Pikachu) didn't boot up properly. It showed me a MIUI splash screen. What I did was to go to bootloader mode and installed the CEE Nordic fixed SBF I found on the net. After flashing, the phone only gave me a motorola logo. I patiently waited for 15 minutes or so but nothing happened.
I took a research on the net and found out that I had to put my phone into stock recovery mode. But when I turned off my phone (Had to do it by a battery pull), pushed the volume down button and pushed the power button afterwards, the screen was still black.
So, what mistakes did I made, are there any ways to fix my phone without bringing it to service center. I think the problem lies in the sbf files, it's only 37mb while a "normal" sbf from droid-developers is about 200mb.
By the way, if my phone is a korean one, can I use a nordic version ?
yes you can fix it. take the battery out then put it back in after a while to make sure its off.
hold down volume up and push the power on. This will get you into bootloader, It may not show anything on the screen but if you hook up the USB cable and open RSD lite it should say its connected.
Now from here you just have to find the right SBF file to flash. This may take 1 go or 10 goes (took me about 10) till I found one that works and it booted straight away.
I must warn you, Your phone WONT! charge in this state so take the battery out when your downloading the files or not flashing it or using it as it will run the battery out fast.
If the battery runs out then you will have to search and do the macqyver method
idecaf said:
One day my defy (which used MIUI Pikachu) didn't boot up properly. It showed me a MIUI splash screen. What I did was to go to bootloader mode and installed the CEE Nordic fixed SBF I found on the net. After flashing, the phone only gave me a motorola logo. I patiently waited for 15 minutes or so but nothing happened.
I took a research on the net and found out that I had to put my phone into stock recovery mode. But when I turned off my phone (Had to do it by a battery pull), pushed the volume down button and pushed the power button afterwards, the screen was still black.
So, what mistakes did I made, are there any ways to fix my phone without bringing it to service center. I think the problem lies in the sbf files, it's only 37mb while a "normal" sbf from droid-developers is about 200mb.
By the way, if my phone is a korean one, can I use a nordic version ?
Click to expand...
Click to collapse
after flashing stock rom you have to get into stock recovery & do factory reset ^^ ph should boot up after that...
if your battery is flat/dead you need to become McGyver -=or=- get extra charged battery & repeat process
After flashing CEE nordic, T-Mobile US and UK roms, I couldn't even go to bootloader mode nor recovery mode. so this is impossible to clear date.
bootloader will not show but RSD lite will say its connected, Unless the battery is flat as it wont charge in this state.
If you hook up the macqyver method and turn the phone on holding the up button and connect the USB cable. RSD lite should say that its connected if you have done it right. It took me 3 goes to get it working but once I did it worked.
It took me 10 roms before I found one that worked. So dont give up
kelbygreen said:
bootloader will not show but RSD lite will say its connected, Unless the battery is flat as it wont charge in this state.
If you hook up the macqyver method and turn the phone on holding the up button and connect the USB cable. RSD lite should say that its connected if you have done it right. It took me 3 goes to get it working but once I did it worked.
It took me 10 roms before I found one that worked. So dont give up
Click to expand...
Click to collapse
same here. macgyver worked on about the 3rd attempt (not sure why, the wires looked connected each time), and my 3rd SBF worked... then i couldn't root, flashed another sbf, and the 5th method worked...z4root, superoneclick, doroot, droid2root, and DOOMLORD worked
but now my sdcard wont load, so i got more problems... sigh... if you have warranty just get a new phone!!!
Hello everyone.
I searched the whole forum and found similar threads with kinda the same problem - but no solution worked for me (or aswell none was stated).
My problem is that my Xoom 2 ME (MZ608-16) (Android 4.0.4) won't turn back on, doesn't light up the LED when charging and seems to be fully bricked.
I also tried to do those button-combo tricks but it had no use. I held those combos several times for a longer period.
But what I can tell is that the screen does a small short flash as if it would boot after holding the buttons POWER/LOCK + SOUND UP for a short time.
Holding those buttons even longer after the first not-easy-to-notice flash it rapidly happens again and again.
What caused this trouble was that I tried to flash the firmware after rooting.
First I stocked at a screen showed that some flash didn't worked out well (looks like fastboot mode).. that happend after trying to flash the recovery to do a proper backup before to do the-stuff-i-wished-to-do. It showes up every boot. Normal boot could be inizialized even though after entering the "control menu" via pressing VOL UP + VOL DOWN + POWER/LOCK on the same time and releae it.
After that I wished to fix it via flashing the whole firmware in hope the message would go away.. troublesome was that I used the wrong firmware for another Model than the MZ608.
And now I'm stocked.
You all helped me already a few times without me registering.
Now I hope you can help me ones again.
Thank you very much in advance.
Greetings
Zeitwaechter
Edit 2013-05-08: Still no changes.
I request further help
You can put phone back into fastboot using factory cable method - see here http://forum.xda-developers.com/showthread.php?t=1077414
If the phone is bricked then you need to use omapflash to flash fastboot and then the image - see here http://forum.xda-developers.com/showthread.php?t=1242330
Hi all,
Yesterday my Jiayu S3 crashed and rebooted, after setting an alarm clock and using the Spotify app. However, it did not reboot into the OS as usual. It did not even show the Jiayu logo, but the phone vibrated (sign that it's booting), screen turned on, phone turned off again, repeating this cycle over and over (not the traditional bootloop as I know it). I was running a rom based on the original rom, with some slight modifications. This rom was running stable for more than a week. I know my way around Android, and am used to switching roms, flashing etc.
Right away, I checked the following things:
- Battery removal didn't help (I did not forget to put it in again ofcourse )
- Phone doesn't go into it's charging cycle when charger is connected
- I do NOT have access to recovery
- I can, however, access the boot menu (Volume up + power key, options: Normal boot, recovery, fastboot)
- I can get into fastboot mode (haven't tested ADB yet), that's the only thing that's still working
I tried to flash the original firmware using SP flashtool, and I am still able to upload firmware on the phone! I am sure that I'm using the correct ROM, and tried different PC's and drivers. Got a few succesful flashes, but still bootlooping.
I also had the idea that my battery was empty (didn't charge it overnight), and measured the battery at 3.52 V. So it was pretty empty but not that empty that it doesn't boot. In an effort to charge the phone, I left it bootlooping for an hour or so, and later on it turned out that it only drained the battery further, 2.99 V.
I didn't want to kill this battery so I did use 2 other batteries from an old Jiayu G4, which appear to work if you turn them around and hold them against the pins (note: I knew what I was doing here ). After a lot of Googling, and seeing a lot of generic "how to fix any brick" stuff I was not able to revive my phone again.
I still believe (and hope) that the error is on the software side of the phone. All the partitions should be ok and in working order according to SP flashtool.
Now this is where my knowledge stops and where (hopefully) your help comes in. What can be corrupted that I haven't checked yet? Do you guys have any suggestions to revive this "high-end" phone again? Once again, it did not happen because of bad flashing or something like that, it happened randomly when I was using the phone normally. I tried to be as accurate as possible (long story), but if there are any questions I'm happy to answer them.
Any suggestion is welcome!
Thanks in advance.
Bump..
Anyone?
bump
Unlocked Bootloader using fastboot, messed with random roms, then wiped everything , then installed stock rom again . Seemed normal. set to update while it was charging @ 30% battery juice. Came back after some hours, to find it dead.
I have set to charge for 6+ hours. Pressed various combinations of volume buttons and power for minutes. Pressed power button for minutes. Nothing on the screen.
Only indication of life is when connected to PC via usb - "Uknown USB device (Device Descriptor request failed)"
Any hope?
Edit: The exact stock ROM installed : (WARNING: A**holes have coinhive script on that page)https://firmware.center/firmware/Mo...HS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip
aakthoo said:
Unlocked Bootloader using fastboot, messed with random roms, then wiped everything , then installed stock rom again . Seemed normal. set to update while it was charging @ 30% battery juice. Came back after some hours, to find it dead.
I have set to charge for 6+ hours. Pressed various combinations of volume buttons and power for minutes. Pressed power button for minutes. Nothing on the screen.
Only indication of life is when connected to PC via usb - "Uknown USB device (Device Descriptor request failed)"
Any hope?
Edit: The exact stock ROM installed : https://firmware.center/firmware/Mo...HS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Sounds like its hard bricked to me, ive had basically the same thing happen in the past with ZTE phones and i never managed to recover them.
If you cant get it into recovery or have it recognized your pretty stuck, i would try a different cord and/or computer and hopefully you can get it recognized.
https://forum.xda-developers.com/moto-x-style/help/computer-unknown-usb-device-t3748055
BEWARE:
Please note that going to that link my antivirus blocks a virus, it could be false but i rarely have anything blocked from websites like that.
Hey, the phone 'was' indeed hard bricked. So I googled for "moto x style hard brick" and found a thread right here: https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860
It has detailed instructions to unbrick. Working perfectly . Phone saved, when I had lost almost all hope.
System dump
aakthoo said:
Unlocked Bootloader using fastboot, messed with random roms, then wiped everything , then installed stock rom again . Seemed normal. set to update while it was charging @ 30% battery juice. Came back after some hours, to find it dead.
I have set to charge for 6+ hours. Pressed various combinations of volume buttons and power for minutes. Pressed power button for minutes. Nothing on the screen.
Only indication of life is when connected to PC via usb - "Uknown USB device (Device Descriptor request failed)"
Any hope?
Edit: The exact stock ROM installed : (WARNING: A**holes have coinhive script on that page)https://firmware.center/firmware/Mo...HS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
If it's hard bricked then get a system dump of the first 200mb of your stock rom, download win32 disk imager, take the system dump and burn it to a SD card through win32 disk imager, put the SD card in your phone and boot it up, once powered on go to fastboot and flash your stock rom again. Hardbrick solved
I am at a loss here. After almost 2 years of working flawlessly, my s5e won't boot.
The screen got frozen while using anydesk, and had to force a restart (power button + up and fown volume buttons).
I can see the Samsung logo for less than a second, and then it switches off. Without touching anything, after some seconds the same thing happens.
I tried charching it and similar behaviour: i see charging circle for less than a second, and off again.
I AM AT A LOSS.
I managed to boot it pressing power+volume_up buttons and this is what i see (attached). It can stay like that for a long time so I guess battery and it's connection to the tablet are fine.
PLEASE ANY HELP WOULD BE VERY WELCOME
UPDATE:
I have tried MANY things in the 6 hours since I wrote this post. I am able to put the tablet in download mode and ODIN (and my PC) recognizes it. I am able to flash VBMETA but now TWRP (fail).
At some point the tablet rebooted in normal mode (why?) but got frozen again and had to reboot it.
Anyone can point me to how to recover it? I don't mind right now to loose what is in the internal memory.
Did you try to hard reboot (power_button + volume_down ) for more than 9 seconds.
If did not work then you may have to charge the phone? If its fully charged try to flash stock rom using Odin. When your device does not boot that means the stock firmware is corrupted and needs to be flashed again. That happened to me before and now my phone is working fine. Wanna know how to flash it? Look it up online!
Abd El-Rahman El-Batal said:
Did you try to hard reboot (power_button + volume_down ) for more than 9 seconds.
If did not work then you may have to charge the phone? If its fully charged try to flash stock rom using Odin. When your device does not boot that means the stock firmware is corrupted and needs to be flashed again. That happened to me before and now my phone is working fine. Wanna know how to flash it? Look it up online!
Click to expand...
Click to collapse
I did try a hard reboot. Same result. I already rooted and installed a custom rom on it (first thing i did).
Twrp is installed but I'm unable to boot to it.
Any more ideas?
iruiz2 said:
I did try a hard reboot. Same result. I already rooted and installed a custom rom on it (first thing i did).
Twrp is installed but I'm unable to boot to it.
Any more ideas?
Click to expand...
Click to collapse
Listen up carefully. There is a truck to boot into recovery. When you hard reboot screen will turn black then show logo. While screen is
Black quick hold vol up button and power.
Worked on my galaxy a10. Tell meh the results bro
Abd El-Rahman El-Batal said:
Listen up carefully. There is a truck to boot into recovery. When you hard reboot screen will turn black then show logo. While screen is
Black quick hold vol up button and power.
Worked on my galaxy a10. Tell meh the results bro
Click to expand...
Click to collapse
It just loads the screen attached in my first post.
Try flash via Odin, it still in download mode with this warning.
The tablet was still covered by warranty so I called the seller and they took it to a Samsung repair store. They replaced the motherboard, so I guess it was not recoverable.
The bad news is that they updated to android 11, I was quite happy with old 9.0 because I had TWRP and Magisk working.
Thank you for all that tried to help.