Related
Hey Guys, could sure use your help... i updated my 10.1 le yesterday and that went thru fine. Later on i was playing and watching youtube and it sent my tablet into a boot loop and i cant seem to fix it. any help would be appreciated thanks in advance.
Mine did the same thing when i was streaming music. Not even Odin brought it back. I used adb to reboot into stock 3e recovery and wipe data/factory reset it, then used Odin to grt back to 3.0.1. Then i just redownloaded the 3.1 update. Hope that helps
LovellKid said:
Mine did the same thing when i was streaming music. Not even Odin brought it back. I used adb to reboot into stock 3e recovery and wipe data/factory reset it, then used Odin to grt back to 3.0.1. Then i just redownloaded the 3.1 update. Hope that helps
Click to expand...
Click to collapse
right now im having problems with adb listing the devices. adb is installed. it keeps saying that i need some APX drivers???
Drivers are here:
http://www.samsung.com/us/support/owners/product/GT-P7510UWYXAR
I had the same problem. This is what i did. Since I had already rooted my tablet, I already had in my laptop ADB and the driver for the tablet. If you don't have these 2 things, I suggest you go to the development section of this forum, look for the insrltructions on how to root, and download what you need.
I connected my tablet then went into cmd mode (DOS MODE), then typed adb reboot recovery. From there the tablet rebooted into recovery. I then wiped data and cache. Then I rebooted and it went fine, no more bootloop. In settings I noticed that it had reverted back to 3.0.1 so I just did update again. Since then my tablet has been smooth as butter.
Sent from my GT-P7510 using XDA Premium App
For those not too comfortable with ADB, I just installed PDAnet (for the fastboot drivers) and after booting to fastboot (holding power and the volume down button and selecting the USB symbol) I used the "fastboot -w" command in CMD.exe to wipe the device.
Its rather strange that a lot of people are having problems. Mine started after getting an error turning on the WIFI chip. Thank god for Titanium Backup's option to sync with Dropbox. Hope this helps.
kdietze3 said:
For those not too comfortable with ADB, I just installed PDAnet (for the fastboot drivers) and after booting to fastboot (holding power and the volume down button and selecting the USB symbol) I used the "fastboot -w" command in CMD.exe to wipe the device.
Its rather strange that a lot of people are having problems. Mine started after getting an error turning on the WIFI chip. Thank god for Titanium Backup's option to sync with Dropbox. Hope this helps.
Click to expand...
Click to collapse
THANK YOU!! Your suggestion of installing PDAnet saved me! I was having a hell of a time trying to get the right drivers so my computer would recognize the tablet has an adb device. After installing PDAnet, it was a cinch. Then I reflashed everything, wiped userdata and cache, and rebooted (I followed the instructions found here: http://forum.xda-developers.com/showpost.php?p=14600617&postcount=111) Now my tab is working again and I was getting ready to ship it off to Samsung so they could re-flash it for me.
Follow this steps
The steps are this:
http://forum.xda-developers.com/showpost.php?p=15084897&postcount=123
Obviously I have installed adroid-sdk and download fastboot from HTC page.
I'm one of the lucky ones who has had their I/O tab stuck in a boot loop on 3.1, and after trying the steps below, I am not getting it to work. I know I must be making a stupid mistake somewhere along the line, but essentially,
I downloaded the new image, boot, and recovery files into a directory on my hard drive;
I installed PDAnet;
I entered into fastboot on my GTab and plugged it into my PC;
I can tell that fastboot is now listed as a device (I suspect this means that the drivers are installed correctly and that it is recognizing a fastboot device);
Now when I try to run the fastboot commands suggested, I get 'fastboot' is not recognized as an internal or external command...
Stupid question, but I am supposed to run this command from cmd.exe, right? Any ideas what I am doing wrong so that the fastboot commands are not recognizable? I may need a dumbed down instruction set if there are steps I am missing somewhere...
engljeff said:
I'm one of the lucky ones who has had their I/O tab stuck in a boot loop on 3.1, and after trying the steps below, I am not getting it to work. I know I must be making a stupid mistake somewhere along the line, but essentially,
I downloaded the new image, boot, and recovery files into a directory on my hard drive;
I installed PDAnet;
I entered into fastboot on my GTab and plugged it into my PC;
I can tell that fastboot is now listed as a device (I suspect this means that the drivers are installed correctly and that it is recognizing a fastboot device);
Now when I try to run the fastboot commands suggested, I get 'fastboot' is not recognized as an internal or external command...
Stupid question, but I am supposed to run this command from cmd.exe, right? Any ideas what I am doing wrong so that the fastboot commands are not recognizable? I may need a dumbed down instruction set if there are steps I am missing somewhere...
Click to expand...
Click to collapse
Edit:
After trying just about everything, I have concluded there are two hurdles I still cannot pass. First, if I fastboot my device, and select the USB icon, my device is appearing in my windows device list. However, I cannot run any fastboot commands in cmd.exe window. Not sure why or what else is needed. Second, I successfully installed SDK and tried to enter recovery mode through ADB, but I cannot find the magic trick to have my device appear in ADB. ODINing back to stock did not make a difference. If I can get past either of these hurdles I am confident I can progress, so any suggestions are appreciated.
fastboot commands never seem to work for me. Always says waiting for device.
ericc191 said:
fastboot commands never seem to work for me. Always says waiting for device.
Click to expand...
Click to collapse
Which makes me wonder if I am doing something wrong. I can't even get fastbook command to be recognized. It's as if there is some fastboot software needed so that my pc knows what to do when I type fastboot. I hoped SDK was enough, took a stab with a fastboot.exe from htc I found on another forum, neither worked. How did you get your pc to look for your device from fastboot in the first place?
Sent from my SGH-T959 using XDA App
Hi .. I have the same problems before
I found out that the new ADB has moved the directory to "platform-tools"
This renders the fastboot useless "winapiadb.dll"(or something) file not found pop up window
I got that ridiculous bootloop issue right in the middle of the flight! thought I bought a $$$ junk lol
use the fastboot -w option to recover .. but it resets the whole tablet back to OE (original everything)
Hey guys,
So I have one of the Limited Edition Google IO Galaxy Tab 10.1's and I can't find a more updated thread than this. It seems this problem is isolated or mostly isolated to the Limited Edition tabs?
Anyways, I've read through the thread (as well as many other resources) and I just don't understand what I'm supposed to do to defeat the boot loop problem.
For me, pressing the Power and Volume up button (or Power and Volume down button) doesn't do a thing. The tablet does not respond at all. The only thing other than the boot loop is that I can get it into "upload mode" whatever that is.
This thread doesn't mention upload mode, so I don't know how to proceed. I can't seem to find anything in the manual about this sort of hard reset, nor can I find any information anywhere else.
Also, I've read this thread, and I do not have any familiarity with what the following software projects are: Odin, PDAnet, and APX Drivers. I also have not used the android SDK.
Also, in the third post chris eckman posted a link to some sort of Galaxy Tab drivers on samsung's site, which is now a broken link.
Anyways, while I'm a noob to the XDA community, I am a computer engineer, and I'm confident I won't have any trouble recovering this device. There's just so much conflicting information and alternatives methods that I'm not sure how to proceed.
It seems like a tutorial might exist out there that I have not yet found?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Clyde_Frog said:
Hey guys,
So I have one of the Limited Edition Google IO Galaxy Tab 10.1's and I can't find a more updated thread than this. It seems this problem is isolated or mostly isolated to the Limited Edition tabs?
Anyways, I've read through the thread (as well as many other resources) and I just don't understand what I'm supposed to do to defeat the boot loop problem.
For me, pressing the Power and Volume up button (or Power and Volume down button) doesn't do a thing. The tablet does not respond at all. The only thing other than the boot loop is that I can get it into "upload mode" whatever that is.
This thread doesn't mention upload mode, so I don't know how to proceed. I can't seem to find anything in the manual about this sort of hard reset, nor can I find any information anywhere else.
Also, I've read this thread, and I do not have any familiarity with what the following software projects are: Odin, PDAnet, and APX Drivers. I also have not used the android SDK.
Also, in the third post chris eckman posted a link to some sort of Galaxy Tab drivers on samsung's site, which is now a broken link.
Anyways, while I'm a noob to the XDA community, I am a computer engineer, and I'm confident I won't have any trouble recovering this device. There's just so much conflicting information and alternatives methods that I'm not sure how to proceed.
It seems like a tutorial might exist out there that I have not yet found?
Click to expand...
Click to collapse
Ok, well if you are running a "stock" IO bootloader, then you should have fastboot and download modes accessible to you by using the volume down and power button combo.
Have you ever gotten to this menu before? If not, then you just aren't doing it right. Let go of the power button part of this combo once the samsung logo appears, and then you should see two icons appear. If you have an IO bootloader, then you are going to go into fastboot mode, and then use fastboot to get your recovery booted. Once you get CWM booted, you can flash a stock ROM, load up stock recovery and wipe this sucker back to factory, and then fastboot your CWM recovery and install Task650's latest rom and be bootloop free. Let me know if you need further help.
Alright, first things first. Yes, this tablet is 100% stock, and I've done one major Android update, but it was not the one that broke everyone's wireless.
----------
So going step by step:
you should have fastboot and download modes accessible to you by using the volume down and power button combo. Have you ever gotten to this menu before?
So, I did once get to what I believe was the "fastboot" menu. I had four options available to me, the first one was something like "repair boot process" which I selected, because I was having a boot problem. It did nothing, and now I cannot get back to that menu.
I did get to the USB upload screen once by accident, when I was trying to get back to the boot menu, but not knowing what to do at that point. I had to shut it off.
Let go of the power button part of this combo once the samsung logo appears, and then you should see two icons appear.
Which Samsung logo? If I press both the power button and volume up or down, I get nothing. Nothing happens. If I press the power button first and then two seconds later start holding down the volume button, then eventually I get the blue swirly samsung screen. At the end of that, the samsung logo is clear. But waiting a bit longer, after about 30 seconds of blank screen, a pulsing white Samsung logo comes up, and I've never known which samsung logo to stop holding the power button. I believe I've tried every combination imaginable, and none of them work.
If you have an IO bootloader Do you mean Google I/O Stock bootloader? If not, I have no idea what this is in reference to.
Once you get CWM booted No idea what that is.
you can flash a stock ROM Where do I get that?
-------------
My bootloop might be different from everyone else's. Everyone else says "shut off the device, and then turn it on with the volume down/up held down. The problem with mine is that it NEVER shuts off! So, I can only do about 2 tests per day, because the only way I can shut it off is to let the battery run dead.
Mine switches from boot loop, and if I force that off, by holding down the power button for 10-15 seconds, then it immediately boots back up into "going into upload mode, cause unknown" If I force that screen off, it boots into the boot loop, so I can never boot from a "powered off" mode, again, unless I let the battery run dead.
I've tried every button pressing boot sequence I can think of with no luck. Can't I just upload something to the device in "upload mode" ? I don't need any data off this device, I just want it to be reset back to day 1, so that I can turn it on and use it.
Thanks so much for your help. As you might imagine, this is a very frustrating problem.
bootloop
can someone please help me ,i have a samsung galaxy tab 2 10.1 ,and its on boot loop ,always showing smsung galaxy tab 2 logo,i've tried restoring factory settings ,,didn't work ,i tried to install receovery from internal sd card says not found ,some one pleeaaase send me the steps of what to do
Hi there guys, first of all thank you all so much for the support here.
I have a problem with my atrix, i googled a lot before posting, but i still can't find a solution:
I have a atrix 4G, unlocked, was running successfully neutrino 2,8 version.
After 2 months of being (almost) fully functional, the phone crashed(i didn't do anything particular at that time, i think that i was browsing google maps) suddenly and now i have continuous boot loop, i get only the classic red dual core logo, with the "unlocked" notification over it, and then after 10-15 sec it reboots.
I try to open it with holding volume down, to enter recovery, nothing happens. It reboots again. The computer doesn't see it, in this case.
I reboot it with holding volume up, says "starting RSD protocol suppport", and pc sees it and i get the cling-clong sound of usb.
I would do the recovery using rsd, but i read that it is not for unlocked devices, is this so? What can i do in this case? Thanks a lot!!!
ergotelis said:
Hi there guys, first of all thank you all so much for the support here.
I have a problem with my atrix, i googled a lot before posting, but i still can't find a solution:
I have a atrix 4G, unlocked, was running successfully neutrino 2,8 version.
After 2 months of being (almost) fully functional, the phone crashed(i didn't do anything particular at that time, i think that i was browsing google maps) suddenly and now i have continuous boot loop, i get only the classic red dual core logo, with the "unlocked" notification over it, and then after 10-15 sec it reboots.
I try to open it with holding volume down, to enter recovery, nothing happens. It reboots again. The computer doesn't see it, in this case.
I reboot it with holding volume up, says "starting RSD protocol suppport", and pc sees it and i get the cling-clong sound of usb.
I would do the recovery using rsd, but i read that it is not for unlocked devices, is this so? What can i do in this case? Thanks a lot!!!
Click to expand...
Click to collapse
You'll probably need to flash a new recovery partition. Check out this thread:
http://forum.xda-developers.com/showthread.php?t=1950307
RaiderDuck said:
You'll probably need to flash a new recovery partition. Check out this thread:
http://forum.xda-developers.com/showthread.php?t=1950307
Click to expand...
Click to collapse
Thanks, but the problem is that this guy can get into the recovery with powering up+holding volume down button, if i understood well.but I can't!
ergotelis said:
Thanks, but the problem is that this guy can get into the recovery with powering up+holding volume down button, if i understood well.but I can't!
Click to expand...
Click to collapse
flasing a recovery is done via fastboot so you don't have to enter recovery but fastboot (hold power and volume down till it shows fastboot, then press up) .
look at this post: http://forum.xda-developers.com/showpost.php?p=33137046&postcount=10
Fix
ergotelis said:
Hi there guys, first of all thank you all so much for the support here.
I have a problem with my atrix, i googled a lot before posting, but i still can't find a solution:
I have a atrix 4G, unlocked, was running successfully neutrino 2,8 version.
After 2 months of being (almost) fully functional, the phone crashed(i didn't do anything particular at that time, i think that i was browsing google maps) suddenly and now i have continuous boot loop, i get only the classic red dual core logo, with the "unlocked" notification over it, and then after 10-15 sec it reboots.
I try to open it with holding volume down, to enter recovery, nothing happens. It reboots again. The computer doesn't see it, in this case.
I reboot it with holding volume up, says "starting RSD protocol suppport", and pc sees it and i get the cling-clong sound of usb.
I would do the recovery using rsd, but i read that it is not for unlocked devices, is this so? What can i do in this case? Thanks a lot!!!
Click to expand...
Click to collapse
hello i had this problem yesterday, it happens in neutrino rom to alot of people!
and btw i could not open recovery either
ill explain what i had to do
i had to use moto-fastboot and install a new recovery, basically your recovery is dead and your rom is unbootable
heres the steps
download the moto drivers and install
http://forum.xda-developers.com/attachment.php?attachmentid=1381183&d=1349549067
then download the motofastboot zip http://forum.xda-developers.com/attachment.php?attachmentid=1381414&d=1349555102
and create a new folder in C: (computer) called Android and then drag the files from the moto zip into android
Then download a new recovery http://www.mediafire.com/?6ww8wrjrdqq9m97
place the recovery.img into the android folder
now you have all the files needed to reflash your new recovery and fix your phone the whole idea is to reinstall recovery so you can access it and wipe and install the rom fresh again
now you need to do these steps
1) Attach your phone to the PC via USB (use a port closest to the power supply)
2) Reboot phone while holding volume down until you see "fastboot"
3) Press volume up to initiate fastboot
4) On your PC click the Start menu, then in the search box type "cmd"
5) In the command prompt type the following commands (no quotes, hit enter after each command)
6a) "cd c:/android"
6b) "moto-fastboot devices"
your CMD promt should show something like this
C:\Users\Me>cd c:/android
c:\Android>fastboot devices
TA20703SX9 fastboot
c:\Android>
now if that has all worked type the following phrases
moto-fastboot erase recovery
moto-fastboot flash recovery recovery-clockwork-6.0.1.4-maguro.img
moto-fastboot reboot
now the phone should reboot, unplug the usb and pull battery out.
put battery back in and then try to boot into recovery like you normally would (power button + Vol Down)
and your new recovery should load!
from here you can wipe your whole system which i would reccomended as your current one is corrupt and install a new rom or reflash your current on onto a clean wipe. if you dont understand how to clean wipe do all of these steps, factory reset, clear cache, clean dalvik cache then go to mounts > storage and format data + format cache + format system
now install new rom and let it boot up, should bootloop a couple of times then start! if not unplug battery from phone and ask for further assitance
Pixelguy said:
1) Attach your phone to the PC via USB (use a port closest to the power supply)
2) Reboot phone while holding volume down until you see "fastboot"
3) Press volume up to initiate fastboot
Click to expand...
Click to collapse
Thank you for your help, the problem is exactly here, i put on the usb, i power up the phone by pressing the volume down, and the phone does nothing,doesn't show the fastboot,and after 10-15 secs starts rebooting again. This is my problem!
The only response from my phone is when powering up, and pressing the volume up, it says "starting rsd protocol support"
Is there any case that my volume down is dead?
ergotelis said:
Thank you for your help, the problem is exactly here, i put on the usb, i power up the phone by pressing the volume down, and the phone does nothing,doesn't show the fastboot,and after 10-15 secs starts rebooting again. This is my problem!
The only response from my phone is when powering up, and pressing the volume up, it says "starting rsd protocol support"
Is there any case that my volume down is dead?
Click to expand...
Click to collapse
unplug usb
remove battery, then put battery back in make sure phone off (no green light)
then hold power button and vol down at the same time for a few seconds
Fastboot should appear in white writing then press up volume and it should say starting rsd protocal or something similiar
then plug in usb and follow the steps i have written above
i do exactly what you said, but doesn't show fastboot. from switched off, if i press volume up with power button, i see the message "starting rsd protocol support" .but no fastboot option!
Is there any chance that you can access adb after bootscreen? than you can use "adb reboot recovery" to get there...
jorno88 said:
Is there any chance that you can access adb after bootscreen? than you can use "adb reboot recovery" to get there...
Click to expand...
Click to collapse
When i start up phone, the only combination possible to stop restarting is by pressing power+vol up to show that with RSD. There is no other option then selectable. Power + volume down does not work, doesn't show anything, has anyone of you experienced this thing?
If the only working option you have is RSD, then I'm afraid you're stuck with having to flash a stock SBF. I hope you know/remember exactly what stock version you had installed before any modding or flashing, because the SBF has to match exactly. Choose wisely and read up as much as you can before flashing.
I have over a year now with custom roms, and i can't remember which version i had. Why do i have to find exactly the version that i had? The latest stock version won't work with rsd? It will make it hard brick?If i manage at least to recover the fastboot menus etc it would be great!
I will later also try to open it, to see if the side button "volume down" is not working,.
I have another question, in your moto atrix, if you press on startup power+vol up, are you also seeing the "starting RSD" etc option??
ergotelis said:
I have over a year now with custom roms, and i can't remember which version i had. Why do i have to find exactly the version that i had? The latest stock version won't work with rsd? It will make it hard brick?If i manage at least to recover the fastboot menus etc it would be great!
Click to expand...
Click to collapse
Yes, flashing a wrong SBF will most likely hardbrick your device.
ergotelis said:
I have another question, in your moto atrix, if you press on startup power+vol up, are you also seeing the "starting RSD" etc option??
Click to expand...
Click to collapse
Can't try right now, but as far as I know, yes, that is a standard way to enter RSD mode.
thank you, so, i know that at least my phone responds to some instructions.
Is there anyone else to suggest me to do anything else?
IN rsd mode, (other than flashing a stock random rom with chance of hardbricking,)the phone can be read by usb, can i do anything there?
ergotelis said:
IN rsd mode, (other than flashing a stock random rom with chance of hardbricking,)the phone can be read by usb, can i do anything there?
Click to expand...
Click to collapse
Sadly no. The RSD mode can only ever be used to flash SBFs. That's it. Nothing less, nothing more.
I will now try to open it to see if vol down is not working well. If it does work, i will select a stock rom 1 year old and i will flash it using rsd, and whatever happens....:good:
I disassembled the phone, the button seems to operate fine(?).
I flashed with RSDlite the 2.3.6 version, the RSD stuck to waiting for phone to restart.
The phone restarted, the "unlocked" logo disappeared.
Starts normally, passes the red motorola logo, shows the graphic of AT&T, and after ~10sec starts restarting again. Bootloop again!
At boot, pressing power+vol up, i can still get the RSD support. Pressing power+vol down does nothing, I don't see any error messages, like the ones in hard brick.
What can i do now, any ideas please!!!
try this
ergotelis said:
I disassembled the phone, the button seems to operate fine(?).
I flashed with RSDlite the 2.3.6 version, the RSD stuck to waiting for phone to restart.
The phone restarted, the "unlocked" logo disappeared.
Starts normally, passes the red motorola logo, shows the graphic of AT&T, and after ~10sec starts restarting again. Bootloop again!
At boot, pressing power+vol up, i can still get the RSD support. Pressing power+vol down does nothing, I don't see any error messages, like the ones in hard brick.
What can i do now, any ideas please!!!
Click to expand...
Click to collapse
Yesterday I had a hard time getting my phone into fastboot mode, after loading a bad SV kernel,it only wanted to start the RSD protocol mode. I eventually got into fastboot by plugging into the wall charger, then removing and installing the battery while holding the vol button. When fastboot appears, unplug the charger to allow sd access.
Thanks for the suggestion, i tried even this,it didn't work. The funny thing is that it shows the battery charging level full screen if i connect the charger, as it starts.
I noticed also that when i press vol down now, it takes longer to start and continue to the moving red logo, it stays for a while stable red,feels like it is thinking whether to start or not lol (if i don't press vol down, on the power up the red moto logo immediately starts the classic "waving" effects)
Anyone having any kind of suggestion?I guess you don't, right?
Hello,
I Was trying to install cyanogenmod on my LG Optimusl5 and I was quite succesfull. I saw the screen working like a charm and the phone seems to be running ok. But, after something about 1 minute, the phone boots. This happens all the time when the system starts.
Another information is that this started after I unblocked the phone and BEFORE I installed the cyanogenmod (in other words, this boot occurs even in official room).
So, I tried to recover my bootloader typing really fast the command described in this post (http://forum.xda-developers.com/showpost.php?p=38053729&postcount=1159): dd if=/sdcard/bootloader_backup.bin of=/dev/block/mmcblk0p5. But I made this after installed cyanogenmod.
When it restarted, the smartphone shows the following message:
"
Secure booting error!
Cause: boot certification verify
"
I tried some recovery options like volume down, power and (after) home button, volume up, power and home button, volume up and down, power and home button. Everyone of this actions redirected me for this screen.
I tried to use KDZ but it does not found my phone.
The question is: have I bricked my phoje? Can I recover it? Without jtag?
Thanks in advance.
Anyone?
I saw that my windows loaded a adb driver when I plug my e612 into usb: fastboot interface (Google USB ID).
But I`ve tried to use the lg recovery tool and adb and neither of them found the device.
Does anyone have any (any!!) ideia??
Well, I can acess fastboot, but don`t know what to do.
How do I flash the original room on my e612?
Thanks
Ok, I just want to know if my phone is hard bricked, or if I still have a chance...
I tried to install an update (121 to 170 for plk-l01) on my rooted phone, with local update. It didn't worked, twrp show errors everywhere, and after turning off know i can't access the recovery. when I press on vol+/- and power for 10-15 second, it vibrate but nothing else.
Is there anything I can do ? my phone isn't recognized by my computer, by the way...
Why you did that? You can't update rooted phone
Idiocrate said:
Ok, I just want to know if my phone is hard bricked, or if I still have a chance...
I tried to install an update (121 to 170 for plk-l01) on my rooted phone, with local update. It didn't worked, twrp show errors everywhere, and after turning off know i can't access the recovery. when I press on vol+/- and power for 10-15 second, it vibrate but nothing else.
Is there anything I can do ? my phone isn't recognized by my computer, by the way...
Click to expand...
Click to collapse
Try to boot into fastboot (phone turned off - connect with data usb to the computer - vol down + power on). Extract rom which is currently installed or higher (for your respective model) and flash from it:
fastboot.exe flash boot BOOT.img
fastboot.exe flash recovery RECOVERY.img
fastboot.exe flash cust CUST.img
fastboot.exe flash system SYSTEM.img
Reboot.
piskr said:
Try to boot into fastboot (phone turned off - connect with data usb to the computer - vol down + power on). Extract rom which is currently installed or higher (for your respective model) and flash from it:
fastboot.exe flash boot BOOT.img
fastboot.exe flash recovery RECOVERY.img
fastboot.exe flash cust CUST.img
fastboot.exe flash system SYSTEM.img
Reboot.
Click to expand...
Click to collapse
Thanks, but unfortunately, it just 'boot' as others reboots. it vibrates, doesn't get recognize and doesn't turn on...
If anyone have any clue on how to force recognizing the phone storage, it might really help ^^
That is what my phone is doing, I tried to upgrade to marshmallow though with no root!! I put the zip in the dload folder and went through the upgrade process everything went through the phone rebooted and now its dead. Blank screen and if you hold power after a few seconds it will vibrate but that is it. I presume its hard bricked? no matter what combo of buttons I press I cannot get it in to fastboot.
james194zt said:
That is what my phone is doing, I tried to upgrade to marshmallow though with no root!! I put the zip in the dload folder and went through the upgrade process everything went through the phone rebooted and now its dead. Blank screen and if you hold power after a few seconds it will vibrate but that is it. I presume its hard bricked? no matter what combo of buttons I press I cannot get it in to fastboot.
Click to expand...
Click to collapse
ok I'm looking for a solution for hours now... so I just lokked how works our phone and I think the trouble must be in the preloader, because I can't even make my phone being recognized by any computer and I can't access to recovery.
I found this :
http://www.droidgyan.com/soft-brick-vs-hard-bricked-vs-broken/
Which could help. I'll leave that topic on for some days (if it could help someone) and I'll open a new one to know if there is any easier solution ! thanks and good luck.
I sorted mine, it was only 2 days old so I got it replaced by the shop I bought it on. I would say it was something like a pre loader from what I saw. I have never bricked an Android phone and I must have had 15-20 of them since my first HTC Magic and before that Windows Mobile which again I messed with tons reloading with all sorts of ROM's!! These phones are wayyyy too sensitive to being messed with, I always remember though that you never mess with the boot loaders, but it looks like these updates do to get it bricked to that point.
Idiocrate said:
Thanks, but unfortunately, it just 'boot' as others reboots. it vibrates, doesn't get recognize and doesn't turn on...
If anyone have any clue on how to force recognizing the phone storage, it might really help ^^
Click to expand...
Click to collapse
Do you have adb debugging activated on the phone? Did you try to hold phone buttons long enough?
piskr said:
Do you have adb debugging activated on the phone? Did you try to hold phone buttons long enough?
Click to expand...
Click to collapse
Euuum..... maybe yes ? I used fastboot but I don't think it really matters now, there's nothing working on it. And I've sometimes hold the buttons for 30-40 second while praying lol
korenisko said:
Why you did that? You can't update rooted phone
Click to expand...
Click to collapse
local update
I just hard bricked my Honor 7 the same way. Is there really no solution? Other China-Phones are pretty much unbrickable, since you can always fix it via the preloader. No such luck here? Back to the shop and hope they actually replace it? While I admit it was stupid to just hastily start the OTA while having twrp and not stock recovery (no root, though), this is a terrible design flaw on Huaweis side.
Anyway... any hope or no chance?
i just hard bricked my honor 7 PLK-L01
it the same thing it is doing . not recognized by the computer
tried all the combination of buttons. but no hope
and it only vibrates when tried to turn on
Need urgent help please
@Idiocrate try to boot into bootloader mode just by pressing Vol DOWN button and simultaneously connecting it to a PC, don't press Power button, if it boots into it, then follow the method given by @piskr in third post.
Hey,
I installed TWRP as I have done many times before using the links from here and Odin, now all that happens is TeamWin flashes up every few seconds if I get into recovery, if I do adb reboot download, it just goes to the samsung splash screen and sits there forever. All I have access to is adb recovery, so I can open a adb shell, but from there I can do nothing.
I feel it is bricked, unless anyone knows what I can do from adb, any help would be greatly appreciated. It's not so much the issue twrp I need help with, I assume I did something wrong and that's caused the brick, but more the possible things I can do to fix.
Thanks in advance if anyone can help
Phrive said:
Hey,
I installed TWRP as I have done many times before using the links from here and Odin, now all that happens is TeamWin flashes up every few seconds if I get into recovery, if I do adb reboot download, it just goes to the samsung splash screen and sits there forever. All I have access to is adb recovery, so I can open a adb shell, but from there I can do nothing.
I feel it is bricked, unless anyone knows what I can do from adb, any help would be greatly appreciated. It's not so much the issue twrp I need help with, I assume I did something wrong and that's caused the brick, but more the possible things I can do to fix.
Thanks in advance if anyone can help
Click to expand...
Click to collapse
So did you backup the original boot partition? If not, maybe just use odin and flash your rom back. The term 'bricked' means the device is completely unresponsive, that's not your case. It's not 'bricked'.
AsItLies said:
So did you backup the original boot partition? If not, maybe just use odin and flash your rom back. The term 'bricked' means the device is completely unresponsive, that's not your case. It's not 'bricked'.
Click to expand...
Click to collapse
I have the original boot partition but I can't get into download so can't use Odin
Phrive said:
I have the original boot partition but I can't get into download so can't use Odin
Click to expand...
Click to collapse
Use the combo keys for Odin?
AsItLies said:
Use the combo keys for Odin?
Click to expand...
Click to collapse
Tried all the key combos for download and none of them work, I figured if abd reboot download didn't work the keys wouldn't either but still tried
i can help go to adb recovery remove usb cable hold power+volume up+down all three together once the device vibrates only remove power button keep holding volume up+down and plug in the usb cable(connected to computer) immediately otherwise it may go to Samsung screen then in odin mode just download firmware from samfw website and flash ap file done
if it shows Samsung logo its not a hard brick its a soft brick i had my tab hard bricked actually no response to charger screen doesn't turn on nothing i gave it to repair guy he just removed battery put it back and it started lol
zenitsu man said:
i can help go to adb recovery remove usb cable hold power+volume up+down all three together once the device vibrates only remove power button keep holding volume up+down and plug in the usb cable(connected to computer) immediately otherwise it may go to Samsung screen then in odin mode just download firmware from samfw website and flash ap file done
Click to expand...
Click to collapse
I 'think' I've sorted it, turning the device of in this state just don't seem to do anything or is too quick not sure.
If I get it into 'recovery' I can then do adb reboot and as soon as I hit enter hold both volume buttons and it makes it into download.
Currently reflashing the stock rom so thank you