Hi, i recently entered the Android world and (as expected by my friends) i bricked my phone trying to test custom roms and kernels.
I yet know almost nothing about hardware and software on smart phones. I would really like some guidance to unbrick it.
What i did exactly is flash a custom kernel on +mmcblk0p5 which might be "oemsbl" while i should flash it on +mmcblk0p8 which is my boot as fas as i know. For the flashing i used ClockworkMod.
I tried two usb jigs bought from a different source but the phone does not response to anything. Its dead. No download mode, no CWM, no usb recognision when connected, not responding at power button at all.
Any ideas?
Does my phone support the unbrickable mod?
Related
Hi all,
I've got a Nexus S 4G CDMA Sprint phone running Stock ICS 4.0.4 IMM76D.
My bootloader is unlocked from previous roots and whatnot.
My problem is that my phone is not being recognized by my computer at all. We're talking complete nonrecognition. No yellow triangle in device manager, no pop-ups, nothing. This phone will just not be read by my computer! I've tried different cords, different computers, re-installation of drivers after resetting my computer, installed PDA net, did a factory reset on the phone, I've literally been on Google for hours upon hours upon hours trying to figure this out and can't figure out why the computer is not recognizing the phone and why the phone is not allowing me to put it into usb mounting. It is however, charging via the computer and wall plug. I can get into stock 3e android recovery, fastboot using V-Up and Power and I can get it into download mode. It is NOT recognized in any modes by the computer nor other computers including my Linux box. The phone states that the usb control initializes but then ends a moment later. I am thinking this is a hardware issue but that leaves me with two issues:
If I was to go to Sprint to have it fixed they would realize my bootloader was unlocked thus voiding the warranty and I'd feel like quite an idiot at the store
If it is hardware related why is the charge working on the device.
I have also tried to bend up the usb plate to make it touch the pins better but that did not help at all. I am at my wits end and really need some help here, I've done everything I could find on Google and here plus more. I want to just return it but with the bootloader unlocked this is really not a possibility. I am looking for help to either become able to lock the bootloader without it having to be connected via the computer so I can then get it fixed if it is hardware related or if I can get the darn thing to be read by the computer once more. so yea, this is where I am at and I would appreciate it so much if someone could help me out, thanks guys!!!
Wireless adb in playstore should help.
Sent from my Nexus S 4G using XDA
That would be perfect! Only problem is that it requires root access on the phone which I am unable to obtain because I cannot access the phone. Is there a way to root the phone without having to connect it via the computer? Something like an update.zip with files able to be flashed through android recovery 3e? If I can get root access than wireless adb would be perfect.
*ultimately if I could remove signature checking in Android Recovery 3e that would work so I could in turn try to root the phone and install a different recovery to then try a different rom to see if that in turn fixes the issue.
Ebicoustic said:
That would be perfect! Only problem is that it requires root access on the phone which I am unable to obtain because I cannot access the phone. Is there a way to root the phone without having to connect it via the computer? Something like an update.zip with files able to be flashed through android recovery 3e? If I can get root access than wireless adb would be perfect.
*ultimately if I could remove signature checking in Android Recovery 3e that would work so I could in turn try to root the phone and install a different recovery to then try a different rom to see if that in turn fixes the issue.
Click to expand...
Click to collapse
You might be able to download your rom of choice and rename it update.zip. I'm not sure if it will flash though....someone else chime in if I'm wrong. You can use wireless file transfer if needed.
Sent from my Nexus S 4G using XDA
Yea I've tried that, everything gets shot down by the recovery with a E:Signature Verification Failed. Thank you for your help so far but I don't think this is something that is going to be helped. I've put in a ticket to Samsung for a repair under it's warranty. In the past I've sent in a rooted phone and they've fixed it so I think I'm going to give that a shot. Just don't want to be without a phone for 2+ weeks.
Well good luck...you are running stock unrooted so it shouldn't matter. It is a dev phone for damn sake. Sorry couldn't help.
Sent from my Nexus S 4G using XDA
Well if you want to download a custom rom... Since you are on this forum. Download any rom (preferably CM9 since its quite good from my experience). Flash the stable version and wait till everything is completed. Now when you flash make sure you download a recovery...eg ClockWorkMod Recovery from google market. You should now have a custom rom installed and download wireless adb as chappy said. See if that works
Hello everyone, I bought a brand new IPPO Q78 (Android 4.0.4) via focalprice.com 2 month ago. First day of using it, and by using I mean simply installing a few apps, and after reboot, I got BOOT LOOP problem, so it wasn't able to get to tablets home screen. After lot of reading about similar problems, I was able to successfully unbrick it using (I suggest others with same cheap china tablet that are also soft bricked to use this program, it really was the only one which helped me):
http://forum.gsmhosting.com/vbb/f781/android-tablet-wifi-cpu-a10-a13-wipe-rom-easy-zakir-gsm-1656461
Here is my situation now, you can view it:
http://www.youtube.com/watch?v=cU1KYIrvZWI
Before, when it was soft bricked, at least after this android logo came the android animation that looped forever, but my computer was able to recognize and install the drivers for Android ADB device, now it can't, it won't recognize my tablet no matter what, ONLY when I press volume up and connect it to usb port, then it recognizes and installs vid_1f3a_pid_efe8 driver, which also I cannot use with LiveSuite, why? I really don't know, I've tried every possible solution found on forums (mainly here, but elsewhere also).
Whole this situation is a result of me doing the CWM upgrade/install, I'm a newbie, so I cannot tell for sure what was it, I just know it was from xda--developers forum, more accurately this thread:
http://forum.xda-developers.com/showthread.php?t=2189640
after this, poof. I think it is hard bricked, and my question is, is there a way to flash it (btw, tablet is rooted) by only having access through mentioned driver vid_1f3a_pid_efe8 and without LiveSuit, cause I would have to download and try a 100 ROM's before I pin the one that suits my tablet. It's really a tough program to deal with, but if it's the only one, I would gladly format and reinstall my Windows OS as many times I need to to get it working.
Hi guys.
I have for a few weeks one Xiaomi Mi3 16GB Snapdragon (WCDMA). Because I thought it was too slow, I flashed another rom by Mirecovery, but I think I used a wrong one because the phone is completely dead! I am not able to get access to the recovery mode or fastboot. The keys don’t work anymore.
This is the rom I flashed: xiaomi.eu_multi_NX403A_4.7.11_jb-4.2. downloaded on miuiandroid.com.[later I heard this is a rom for zte z5s mini, so really wrong one ]
After installing of MiPhone2.11.6, the first time when I connected the phone with the pc, the red led kept lighting on and the driver wasn't installed, but the phone was recognized by MiFlash(com20, i think): flashing did't work because there wasn't a communication with the port. After that I tried to reinstall MiPhone and afther some attempts, when I connected the phone with the pc, the red led kept lighting on for a few seconds and the driver was installed. But the phone wasn't anymore recognized by Miphone, so again no possibility to flash it.
I’m really desperate because i used the phone just for 2 weeks.
I would really appreciate if somebody would come with a good solution.
Thank you.
chc2918 said:
Hi guys.
I have for a few weeks one Xiaomi Mi3 16GB Snapdragon (WCDMA). Because I thought it was too slow, I flashed another rom by Mirecovery, but I think I used a wrong one because the phone is completely dead! I am not able to get access to the recovery mode or fastboot. The keys don’t work anymore.
This is the rom I flashed: xiaomi.eu_multi_NX403A_4.7.11_jb-4.2. downloaded on miuiandroid.com.[later I heard this is a rom for zte z5s mini, so really wrong one ]
After installing of MiPhone2.11.6, the first time when I connected the phone with the pc, the red led kept lighting on and the driver wasn't installed, but the phone was recognized by MiFlash(com20, i think): flashing did't work because there wasn't a communication with the port. After that I tried to reinstall MiPhone and afther some attempts, when I connected the phone with the pc, the red led kept lighting on for a few seconds and the driver was installed. But the phone wasn't anymore recognized by Miphone, so again no possibility to flash it.
I’m really desperate because i used the phone just for 2 weeks.
I would really appreciate if somebody would come with a good solution.
Thank you.
Click to expand...
Click to collapse
if you have no access to recovery or fastboot, the phone is finished
one of the worst things you can do to a device is flash the wrong software, as you see.
I've searched for nearly 12 hours and tried several methods, but since this is an older device a lot of threads and links are dead. I was hoping someone could give me advice here, and I did use the search but to no avail.
The situation is I have a Galaxy Tab 2 10.1 (GT-P5113) and it's stuck on the logo and the sound it boots up cuts out half way (wondering if it's a hardware issue). I can boot into Download Mode and I have the drivers for it on my computer. The problem I'm having is USB Debug wasn't enabled. Is there a way I can flash through Odin3 and which version should I use? This device isn't rooted either. Any help or advice would ease my mind.
Moceimo said:
I've searched for nearly 12 hours and tried several methods, but since this is an older device a lot of threads and links are dead. I was hoping someone could give me advice here, and I did use the search but to no avail.
The situation is I have a Galaxy Tab 2 10.1 (GT-P5113) and it's stuck on the logo and the sound it boots up cuts out half way (wondering if it's a hardware issue). I can boot into Download Mode and I have the drivers for it on my computer. The problem I'm having is USB Debug wasn't enabled. Is there a way I can flash through Odin3 and which version should I use? This device isn't rooted either. Any help or advice would ease my mind.
Click to expand...
Click to collapse
download a copy of your device stock firmware, if you already have it, flash it with odin, there is no specific version of odin, it works on all as long as your device gets connected and shows in odin you are fine.
regarding the hardware issue, it might be or it might be not, you can only be sure after successfully flashing a stock firmware file.
it won't need any USB Debug option for flashing stock firmware so you are safe to flash.
If odin does not work you may try going to the recovery and perform a factory reset and delete cache
Sorry to start a thread on this old device and guessing there may not be anyone who can help me.
I flashed the Lenovo VibeUI ROM from needrom which seemed to work well, but I wanted to go back to stock and used the Ulefone 'onekey flashing tool' which usually worked to go back to the stock ROM. This time there was an error message, so I used SP Flashtool to flash the stock rom.
However the phone appears bricked - no screen, no charging indicator when plugged into the charger or USB on PC, whether latest official V1 or V2 ROM flashed. Not identified by PC as plugged in, but with battery removed, it appears I can 'flash' stock ROM using SP FT or Onekey official flashing software, but it is still 'dead' when battery reinserted.
Even though flashing the ROM with SP Flash Tool and the official Onekey flashing tool appear to flash the ROM to the EMMC, the phone won't even boot to the boot logo. Plugging in the charger doesn't show the charging indicator. I think the issue is with the 'ERROR: NAND flash was not detected!' message when I do a memory test. Not quite sure how this happened.
I thought it was difficult to brick MTK devices, but I seem to have achieved the almost impossible! Does anyone have any idea how I can recover from this bricking? The phone is recognised by SP FT so I hope there is a possibility.
Is there an easy way of solving this as I would like to donate this phone to someone who needs it? Tried lots of 'fixes' from XDA and other sites, but nothing working so far.
Any help/advice greatly appreciated.
:fingers-crossed: