Related
Does anyone have this problem? I`ve searched and cant find a solution.
I had sense rom on my phone then decided to go back to jboogie rom. I booted into stock recovery(power+vol down) and when i tried to tap bottom right of screen the screen wouldn`t respond so I couldn`t do a factory reset. I then tried volume up=power button to flash sbf through RSDlite. Nothing came on my phone screen telling me to attach usb, it juat stayed blank, although rsdlite said phone was connected so i started to flash sbf anyway. Then on the phone screen it said software update in progress, once it finished flashing, instead of saying rebooting phone on RSDlite it came up with "pass" and the phone wont boot or do anything at all now.
Sorry for long message, but hope someone can help.
Thanks
Mark
try to flash a stock rom sbf with rsdlite and after that, do a wipe in recovery mod. to enter recovery press power+ vol down, after the droid apears, push vol up+vol down. You have to see then the stock recovery menu. I did in the same way and is working. I think is now so easy to really brick this phone.
Thanks for your reply, unfortunately when I try to get into stock recovery by pressing power+volume down I dont get anything on the screen at all anymore, nothing happens. Its the same when I press power+volume up to try to flash it too.
not even white led?
maybe your battery is 2low?
if u see the white led u can still go into bootloader and flash .sbf with rsd lite
Hi there,
I can't believe its dead!!
I have tried every rom available and tried out all the .sbf's too. A couple of times i thought i have bricked it but it was always done to user error (or a lack of understanding at times on my part). These Defy's seem to be almost bullet proof!
I had the "pass message" from RSDLite and all i had to do was flash the "2.2 bootonly" sbf to get past it. I have had corrupted boot loader messages and more but it just keeps coming back for more once things the right things are done in the right sequence.
Assuming your battery is ok, I would try installing one of the latest froyo .sbf's with RSDLite 3.9 only completion do a wipe from the stock recovery (hold pwr + vol down). Press vol up and vol down to activate the menu, select wipe with volume up or down, press power to go. The after rooting apply one of the excellent roms from Jboogie & Pays.
Good luck... sure it will be fine.
Andy
qpzmaluk said:
Thanks for your reply, unfortunately when I try to get into stock recovery by pressing power+volume down I dont get anything on the screen at all anymore, nothing happens. Its the same when I press power+volume up to try to flash it too.
Click to expand...
Click to collapse
If you have only black screen, you have to flash the latest undowngradable rom you flashed, then you you finally get to moto logo, you will be able to go to recovery and wipe. After it it will boot just fine.
I had the exact same problems, i tried to reflash. It ended up not showing anything on the screen in any of the button combinations. It did however show in RSD Lite and after i tried to flash the chinese rom it said "pass" after that i only got a white led and it no longer was detectable through usb. I tried to recharge the battery so i left it on white light with charger plugged over the night... No success. It's now in service and hope they fix it.
I would like to point out to anyone trying to help me that bootloader no longer shows up, neither recovery menu.
astearon said:
I had the exact same problems, i tried to reflash. It ended up not showing anything on the screen in any of the button combinations. It did however show in RSD Lite and after i tried to flash the chinese rom it said "pass" after that i only got a white led and it no longer was detectable through usb. I tried to recharge the battery so i left it on white light with charger plugged over the night... No success. It's now in service and hope they fix it.
I would like to point out to anyone trying to help me that bootloader no longer shows up, neither recovery menu.
Click to expand...
Click to collapse
I had a similar thing when i flattened my battery half way through flashing an .sbf. I borrowed a friends battery, flashed the boot only and all was fine. There is a couple of pointers on the forum on how to charge your battery if you dont have a working rom (it wont charge without one! You have to get the motorola logo followed by the battery animation to charge your battery).
In your case im pretty certain you could have saved yourself the hassle of sending it off for service.
Andy
Thanks for all the replys, I have already had the dead battery a couple of weeks ago and "revived" it by putting the + and _ wires of usb cable into the battery of the defy, but this seems different, I cant get anything to work on it, no roms will flash and all I get is black screen. I do get the white led but only sometimes. It is very change indeed, I will try some of the solutions you guys said tomorrow and let yous know how I got on.
Thanks again
Mark
I did not want to risk charging out of wires, i have unlimited warranty on it after all so i gave it to service hoping a fix will be made by guys who know what they where doing (i hope).
In any case i see -qpzmaluk- tried off of wires and nothing happened.
I tried to flash again this morning using all the techniques above but I cant get rsdlite to recognise my phone either now. All i get is when connected to usb is the white led, nothing else happens when i try to go into recovery etc.
Mark
Huge thanks to EDITION I got my phone working again.
I did what he said about flashing last undowngradeable rom and surprisingly it came back to life. Brilliant mate, i cant thank you enough.
Mark
how did u do that? if u said your rsd lite cant recognize your phone?
I kept trying to connect to pc with usb and rsdlite eventually found it so I took the chance of flashing froyo 3.4.3-the one I last had on the phone, and surprisingly this time it went throughht to the end of booting the phone and now I have everything working again including stock recovery etc.
One thing to mention was that I couldn`t get into pwer+vol up or down before I flashed this time I flashed my phone. I just connected it to pc and luckily rsdlite recognised it this time and I just pressed flash button, then eventually phone booted up. So something was wrong and it didn`t flash it the normal way by going into stock recovery on phone but it worked
So, been running CM10 for a long time on tab. Decided to go back to stock, and downloaded the JB stock rom. Flashed via ODIN. Everything seemed to go OK, except that after the flash the screen went black for ages, and didn't reboot. So I hard powered it off. Probably what did it, but it wasn't going anywhere for about 15 minutes, so figured it was the next step.
Now, I get the battery charging icon. The system goes through the Galaxy Tab 2 7.0 white logo, the swirling then glowing Samsung logo, and then loops through that forever.
It wouldn't be such a problem if I could back into ODIN and do another flash, but I can't get into download mode (normally I do it via adb but that isn't working since there is no USB connection at all). Tried all combinations, power/up, power/down etc. It just boot loops as above. I'm pretty sure I bricked it, but just wanted some confirmation.
Been doing this on and off for a long time, and it's the first time I've ever got stuck like this.
Thanks in advance.
Plug USB charger, your device will boot into charge mode. From charge mode you can boot into recovery by keep holding VOLUME UP button and than press POWER button. Clear data and cache in recovery, reboot.
ketut.kumajaya said:
Plug USB charger, your device will boot into charge mode. From charge mode you can boot into recovery by keep holding VOLUME UP button and than press POWER button. Clear data and cache in recovery, reboot.
Click to expand...
Click to collapse
Thanks, but I tried all combinations of Power/Volume UP and Power/Volume DOWN, it just goes through a normal boot cycle until it starts looping.
I guess it's possible I'm not using the right timing. I'm assuming that you hold Volume UP or DOWN and then press and hold Power until the screen goes black, and then release? I've done it like that many times, and also continued to hold everything down as the logo appears, and then system goes back to the battery charging icon as if it powers off again. I sound like such a noob when I type stuff like that!
I saw ODIN successfully write system.img, boot.img, and recovery.img, so I'm thinking any CWM recovery I had on there is toast.
sl0ttedpig said:
Thanks, but I tried all combinations of Power/Volume UP and Power/Volume DOWN, it just goes through a normal boot cycle until it starts looping.
I guess it's possible I'm not using the right timing. I'm assuming that you hold Volume UP or DOWN and then press and hold Power until the screen goes black, and then release? I've done it like that many times, and also continued to hold everything down as the logo appears, and then system goes back to the battery charging icon as if it powers off again. I sound like such a noob when I type stuff like that!
I saw ODIN successfully write system.img, boot.img, and recovery.img, so I'm thinking any CWM recovery I had on there is toast.
Click to expand...
Click to collapse
You must pull usb cable before start.
You can try to re-flash.
tuxafgmur said:
You must pull usb cable before start.
You can try to re-flash.
Click to expand...
Click to collapse
Well, don't I feel like the idiot!
How did I not think to disconnect the USB before trying this? tuxafgmur, your first "Thanks" has been registered, I've got it from here!
P.S. Welcome to the forum!
it sounds strange. never heard of such a strange boot problem. anyway it could be that while transferring boot.img it became damaged due to some error. i know you probably tryed but you may try and connect it to linux or mac os x in order to check if you could retrive more data about the tab. for example the mac could find if it is totally corrupted. normally when i plug my samsung devices it ask me to add the samsung-modem also if they are turned off. meybe if it happens the same to you you can try to adb fastboot it also if i doubt myself about it working, but give it a shot
i hope my bad english is not preventing you to understand what i'm saying!
give us new feedback!
The power button on my N5 started acting up, like if i even press it once it will show me the power off option. After that it started to randomly reboot. Now its reboots every 2 sec showing the google logo. When it try to put it in recovery mode, it again reboots. Randomly like 20 in 1 trys it stops in the recovery mode.
1. I tried to factory data reset. I got an error msg something like " Cant mount cache ".
2. Called both Lg and goole for a replacement, but my warranty got over.
3. I unlocked the bootloader using fastboot and tried to flash stock rom, but after the first reboot bootloader command the bootloader again comes to locked status. Still after all process the phone reboots and gets to the booting animation, but it does not move past that( even after an hour).
Device was in full stock condition when this happened. Someone please help me out!!
shaveender said:
The power button on my N5 started acting up, like if i even press it once it will show me the power off option. After that it started to randomly reboot. Now its reboots every 2 sec showing the google logo. When it try to put it in recovery mode, it again reboots. Randomly like 20 in 1 trys it stops in the recovery mode.
1. I tried to factory data reset. I got an error msg something like " Cant mount cache ".
2. Called both Lg and goole for a replacement, but my warranty got over.
3. I unlocked the bootloader using fastboot and tried to flash stock rom, but after the first reboot bootloader command the bootloader again comes to locked status. Still after all process the phone reboots and gets to the booting animation, but it does not move past that( even after an hour).
Device was in full stock condition when this happened. Someone please help me out!!
Click to expand...
Click to collapse
You should ask questions in the Q&A forum. However i think that it cant be a software problem at all, its the power button, you shold take it to repairs and replace it.
shaveender said:
The power button on my N5 started acting up, like if i even press it once it will show me the power off option. After that it started to randomly reboot. Now its reboots every 2 sec showing the google logo. When it try to put it in recovery mode, it again reboots. Randomly like 20 in 1 trys it stops in the recovery mode.
1. I tried to factory data reset. I got an error msg something like " Cant mount cache ".
2. Called both Lg and goole for a replacement, but my warranty got over.
3. I unlocked the bootloader using fastboot and tried to flash stock rom, but after the first reboot bootloader command the bootloader again comes to locked status. Still after all process the phone reboots and gets to the booting animation, but it does not move past that( even after an hour).
Device was in full stock condition when this happened. Someone please help me out!!
Click to expand...
Click to collapse
Yeah, definitely sounds like a hardware power button issue. You can still contact LG to repair it for a fee even though the warranty is expired. If you don't want to do that, you (or a tech-savvy friend) can try tearing it apart to see if it's stuck or if there's residue or something like that. This article also has some suggestions, but I don't think they'll be very useful as your power button appears to be stuck down.
I'm going to try to keep this as simple as possible as I don't really know what I did wrong or how I ended up where I am now.
I have a Samsung Galaxy 8+ and I decided to root it. I decided to follow this guy's instructions on how to do it: youtube.com/watch?v=eh-I4uxAmUY.
I follow his steps and am bought to the "Unmodified System Partition" menu after having gone through the process of factory resetting, wiping my data and using Odin to flash twrp-3.1.0-r1_dreamlteks.
The problem is that now the touch screen is unresponsive. It does literally nothing.
I am stuck at the screen that says "Keep System Read only?" where I have to "Swipe to Unlock Modifications", but find myself unable to do so because my touch screen doesn't let me swipe!
So now I'm panicking:
Firstly, I can't get the phone to shut down. Holding the power button does nothing, even if I hold it for a full minute.
Secondly, I can't boot the phone into anything except this unresponsive TWRP thing.
Thirdly, my computer no longer recognizes my phone when I try to connect it via USB (might be unrelated?).
How ****ed am I?
Is my phone just bricked now?
Can I save this rooting attempt in any way, or at least revert to the stock?
Will bringing the phone to a retailer help me in any way, or have I already broken the warranty?
Please guys I am desperate for some assistance here.
ViRALiC said:
I'm going to try to keep this as simple as possible as I don't really know what I did wrong or how I ended up where I am now.
I have a Samsung Galaxy 8+ and I decided to root it. I decided to follow this guy's instructions on how to do it: youtube.com/watch?v=eh-I4uxAmUY.
I follow his steps and am bought to the "Unmodified System Partition" menu after having gone through the process of factory resetting, wiping my data and using Odin to flash twrp-3.1.0-r1_dreamlteks.
The problem is that now the touch screen is unresponsive. It does literally nothing.
I am stuck at the screen that says "Keep System Read only?" where I have to "Swipe to Unlock Modifications", but find myself unable to do so because my touch screen doesn't let me swipe!
So now I'm panicking:
Firstly, I can't get the phone to shut down. Holding the power button does nothing, even if I hold it for a full minute.
Secondly, I can't boot the phone into anything except this unresponsive TWRP thing.
Thirdly, my computer no longer recognizes my phone when I try to connect it via USB (might be unrelated?).
How ****ed am I?
Is my phone just bricked now?
Can I save this rooting attempt in any way, or at least revert to the stock?
Will bringing the phone to a retailer help me in any way, or have I already broken the warranty?
Please guys I am desperate for some assistance here.
Click to expand...
Click to collapse
You have voided your warranty so you can't take it down to the shop and get it replaced.
It isn't fully bricked because you can still boot into an "os" that isn't fully functional. It ain't recognised because you have to swipe past this and hop into the ADB sideload interface. Btw, try holding your home button, power button and volume up (or down) and report results.
If I was you, I would wait till the battery drains and shuts off and then let it be off for the rest of the night or something and then try again.
RAZERZDAHACKER said:
You have voided your warranty so you can't take it down to the shop and get it replaced.
It isn't fully bricked because you can still boot into an "os" that isn't fully functional. It ain't recognised because you have to swipe past this and hop into the ADB sideload interface. Btw, try holding your home button, power button and volume up (or down) and report results.
If I was you, I would wait till the battery drains and shuts off and then let it be off for the rest of the night or something and then try again.
Click to expand...
Click to collapse
Alright, I'll give it until it passes out from battery loss and then get back on when things change. Thanks for the reply!
Ok Guys So I Shouldn't Have Done This But I Used Fastboot To Flash Recovery And I think I Did It Wrong. It Said "ok" And Finished And I Rebooted Phone It Resetted And Then Stuck On The Orange State Bootloader Message. I Do The Recovery Mode And Goes Black And Nothing Is Responsive For a While, Sometimes Longer Than Others. This Happens If I Start Phone Normal Or Try Fastboot Or Download.
Because Of My Mistake I Cannot Connect To Pc Software And Im Not Sure Of What I Can Do. I Feel Like Im Not Going To Like The Answer For This But I Got To Take The Blame For This.
Btw i Have A Samsung galaxy Note 20 Ultra Sm-N986u
I think your phone is hard bricked
so you can't get fastboot using volume up+power or via adb?
rescue from manufacturer site pos or just device not being recognised?
It isn't hard bricked it's just way of Samsung trying to make life of simple people more difficult, people who paid for Samsung phones lots of money.
To sort that screen issues what you can surely do is,
Simply press volup + voldown buttons at the same time, no matter if you're on that orange screen or whatever just press those those two buttons at the same time and keep pressing them while you connect your phone to pc. you will boot into download mode. Then flash stock firmware for your phone. After stock of flashed Reboot and start your phone, go to developer options see if oem unlock option is there if it is then oem unlock it if it is not then go back to settings manually change date to year ago, then go to updates disable auto update, connect to WiFi, and press on update several times untill window shows up saying no updates, then go to developer options you should see oem unlock, unlock it.
Then boot into download mode and make sure you have working copy of recovery.
And make sure you follow instructions of whoever recovery you installed on how to boot into recovery. I have S20 plus and too had troubles with it, and the only working recovery for my phone is twrp customised. To boot into it after flashing recovery from odin auto reboot disabled I pressed voldown and power, USB cable connected, then after screen goes off I changed from voldown to volup while kept pressing power button and cable connected. Orange screen with warning showed up for 5 sec I kept pressing and it bottled to twrp and then I was able to install custom rom beyond rom and while installing in aroma I was able ti choose option to remove orange screen.
That's it.
I ran into the same error. I mistakenly loaded twrp's recovery into userdata instead of ap section. The phone was stuck at the orange screen and nothing was happening whatever i pressed. I waited till the battery to dry out and with 0% battery, i directly connected to pc and was able to get into download mode. Then i flashed stock and everything is now back to normal.
Carl Johnson (Cj) said:
I think your phone is hard bricked
Click to expand...
Click to collapse
Absolutely not