Related
Friend of mine flashed wrong rom. Now phone won't turn on at all. Any solutions?
sent from your moms house
A little more details then that.
GINGERVOLTED!
nap286 said:
Friend of mine flashed wrong rom. Now phone won't turn on at all. Any solutions?
sent from your moms house
Click to expand...
Click to collapse
A few questions first:
What ROM did he try to flash?
Did he try to flash it through Clockwork Recovery or ROM Manager?
When you try to turn the phone on, does the backlight come on the screen or anything? Or does it just sit there without even making an attempt to turn on?
Flashing the wrong ROM would not hard brick your phone. The install of the ROM would simply fail. If anything, it sounds like your friend tried to flash a ROM and the battery either died or was taken out during flashing. Please post back so we can all try to help.
He is talking about me
I flashed it through CWM and went to restart and now the phone is dead
No lights nothing no vibrate it simply will not turn on
flashed it with
O2X FLAIR GB v4 REVOLUTION FINAL (based on LG v20L)
for optimus
From what I am thinking The power button is no longer assigned?
I am guessing
JVT said:
He is talking about me
I flashed it through CWM and went to restart and now the phone is dead
No lights nothing no vibrate it simply will not turn on
flashed it with
O2X FLAIR GB v4 REVOLUTION FINAL (based on LG v20L)
for optimus
Click to expand...
Click to collapse
Could you give me a link?
Sent from my Transformer Prime TF201 using xda premium
JVT said:
He is talking about me
I flashed it through CWM and went to restart and now the phone is dead
No lights nothing no vibrate it simply will not turn on
flashed it with
O2X FLAIR GB v4 REVOLUTION FINAL (based on LG v20L)
for optimus
Click to expand...
Click to collapse
So the ROM flashed but when you went to reboot, that's when the phone froze up?
Are you 100% sure there was enough battery life when you flashed it? You really might have hard-bricked it. I figured the ROM would just simply fail installing because that's usually what happens.
spc_hicks09 said:
So the ROM flashed but when you went to reboot, that's when the phone froze up?
Are you 100% sure there was enough battery life when you flashed it? You really might have hard-bricked it. I figured the ROM would just simply fail installing because that's usually what happens.
Click to expand...
Click to collapse
I think it might be something with the splash screen.
Sent from my Transformer Prime TF201 using xda premium
The battery was low, but it went to reboot after the install and never restarted
JVT said:
The battery was low, but it went to reboot after the install and never restarted
Click to expand...
Click to collapse
The phone shouldn't automatically reboot after an install...
Sent from my Transformer Prime TF201 using xda premium
JVT said:
The battery was low, but it went to reboot after the install and never restarted
Click to expand...
Click to collapse
Were you doing this through ROM Manager or just flashing through Recovery?
Sent from my GingerFusion Revo using Tapatalk.
http://forum.xda-developers.com/showthread.php?p=20747850&posted=1#post20747850
I have to wait 5 mins between posts
I selected the reboot phone option.
I had successfully flashed gingervolt but thought this was another option.
---------- Post added at 09:14 PM ---------- Previous post was at 09:05 PM ----------
through recovery, Did the necessasary data wipes and then flashed from zip
JVT said:
http://forum.xda-developers.com/showthread.php?p=20747850&posted=1#post20747850
I have to wait 5 mins between posts
I selected the reboot phone option.
I had successfully flashed gingervolt but thought this was another option.
Click to expand...
Click to collapse
I honestly don't know what to say. If the phone is completely unresponsive then it very well could be a hard-brick. The only thing you can do then is call Verizon, tell them that you had a software update for your Revolution and the phone shut off in the middle of the update and now will not come on at all. They'll probably send you a free one (hopefully). That's really about the only thing I can think of. Have you tried just plugging it in to see if it charges at all? Plug it in and see if either the screen will come on or you at least get the LED light to come on. If not then do what I said a second ago and call Verizon.
Yeah I get nothing, they are going to send me a new one. Thanks anyway.
JVT said:
Yeah I get nothing, they are going to send me a new one. Thanks anyway.
Click to expand...
Click to collapse
Ok cool, sorry I couldn't help more man!
I was more curious why it happened more than anything, Being phoneless for 2 days sucks too though. I feel naked
JVT said:
I was more curious why it happened more than anything, Being phoneless for 2 days sucks too though. I feel naked
Click to expand...
Click to collapse
Yeah I've been there, it sucks really bad. The reason why it happened other than the fact that the ROM is for a different phone, is because the ROM has a boot.img that is not compatible with the Revolution. So once you changed the boot.img the phone was no longer able to boot up. At least that's what I think about it.
Sent from my GingerFusion Revo using Tapatalk.
Hi Developers,
I need your help i have been a fan of this site for some time now and have found very useful information here. now i need your help once again.
I tried to unlock the Bootloader and flashed TWRP and CWM but when i try to bring the device back up SU is not granted Root access. i tried over and ocer again.
When i try to reboot the phone Fastboot/Flash recovery/TWRP or CWM the device hands adn never comes back up.
I even tried to do a Facotry reset and start over. This also did not work.
Can you guys please guide me on truly doing a factory reset so that i can try this again?
Thank you very much for your help.
Rgrds,
Robert1c
If you want to reset to out of the box stock, run the ruu.
Sent from my HTCONE using Tapatalk 4 Beta
Robert1c said:
Hi Developers,
I need your help i have been a fan of this site for some time now and have found very useful information here. now i need your help once again.
I tried to unlock the Bootloader and flashed TWRP and CWM but when i try to bring the device back up SU is not granted Root access. i tried over and ocer again.
When i try to reboot the phone Fastboot/Flash recovery/TWRP or CWM the device hands adn never comes back up.
I even tried to do a Facotry reset and start over. This also did not work.
Can you guys please guide me on truly doing a factory reset so that i can try this again?
Thank you very much for your help.
Rgrds,
Robert1c
Click to expand...
Click to collapse
coal686 said:
If you want to reset to out of the box stock, run the ruu.
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
Hi Coal-
I tried that earlier. the 1st time through it saw my device but then blued screened my PC. then once rebooted i tried again and its not seeing my device anymore. any advice?
Robert1c said:
Hi Coal-
I tried that earlier. the 1st time through it saw my device but then blued screened my PC. then once rebooted i tried again and its not seeing my device anymore. any advice?
Click to expand...
Click to collapse
Hi Guys just an update. i was able to get TWRP installed but now it never actually launches the phone. when i reboot the phone it goes right into TWRP.
What am i doing wrong?
Robert1c said:
Hi Guys just an update. i was able to get TWRP installed but now it never actually launches the phone. when i reboot the phone it goes right into TWRP.
What am i doing wrong?
Click to expand...
Click to collapse
If you can get into recovery, just restore nandroid. Or flash a fresh rom.
Sent from my lair.
volk9029 said:
If you can get into recovery, just restore nandroid. Or flash a fresh rom.
Sent from my lair.
Click to expand...
Click to collapse
I tried running the RUU.zip but i get the attached error
Robert1c said:
I tried running the RUU.zip but i get the attached error
Click to expand...
Click to collapse
Make sure you are in the boot loader when running ruu and you have all the proper HTC drivers. If that's not it you can try searching Google for the error.
Dude. Just boot into recovery then on phone press mount usb. On your computer in your drives you should see your phones memory. Download a rom from the sprint htc one. Use this. http://www.androidfilehost.com/?fid=22962010882834713 Once downloaded drag zip to storage. Once done press unmount usb. Then on recovery press install from storage. Click on your rom zip. Let it install. Reboot your htc one. Your good. You should have no more issues.
Sent from my HTCONE using xda premium
eric00716 said:
Make sure you are in the boot loader when running ruu and you have all the proper HTC drivers. If that's not it you can try searching Google for the error.
Click to expand...
Click to collapse
he also has to relock his bootloader to run the RUU
Fyi, because I see it misused a lot, "Bricking" man's it won't even power on, be recognized by any device, etc. If it just won't go into its ROM then that isn't a brick.
Sent from my HTCONE using Tapatalk 4 Beta
Mine fits the description of bricked better... All stock, no root, just using it as a GPS, left it plugged into the car charger when I went into the store but turned the screen off (that thing gets HOT). When I came back, no led, no power, nothing. Have tried connecting to the wall charger that came with it, to USB 2 and 3 on computers, left it charging all night. Not so much as a flicker... The computers didn't recognize anything connecting to them either.
Long hold of power (with and without either/both volume buttons) has done nothing.
What is left to try? I would rather not lose all the pictures from my vacation, but need my phone back for work.
If its not rooted go to sprint and get urself a new one
Sent from my HTCONE using xda premium
HTC_M7 said:
If its not rooted go to sprint and get urself a new one
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
Thanks! thats what im thinking about doing. the screen says:
*** TAMPERED ***
*** RELOCKED ***
will they take it back adn give me a new one in this state?
THanks again!
Well it says it was tampered
Sent from my HTCONE using Tapatalk 4 Beta
Dang... Not good news, but I never played with it at all, so I should be OK. Really too bad about those pictures.
HTC_M7 said:
Well it says it was tampered
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
I think that will be an issue as well. i did find a few posts that talk about the RUU to take it back to stock where the two messages would go away but the mirrors where this is located (http://www.androidfilehost.com/?fid=22979706399752930) are all down.
I have the HTC One from Sprint. does anyone know where else i can find the RUU?
http://www.androidfilehost.com/?fid=22979706399752930
Sent from my HTCONE using Tapatalk 4 Beta
---------- Post added at 05:06 PM ---------- Previous post was at 05:06 PM ----------
Try again
Sent from my HTCONE using Tapatalk 4 Beta
HTC_M7 said:
http://www.androidfilehost.com/?fid=22979706399752930
Sent from my HTCONE using Tapatalk 4 Beta
---------- Post added at 05:06 PM ---------- Previous post was at 05:06 PM ----------
Try again
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
Looks like it may have been my machine. downloading now. thanks ill post an update in a minute.
I purchased the AT&T version of the Galaxy Note 3 a little less than a week ago and, to be honest, I'm not really keen on it. There are a number of reasons, but what it boils down to is that I just don't think I like it all that much. I've already sold my Galaxy Note 2, so I'll have to figure out what I'm going to do about a cell phone, but that's something beyond the scope of this particular posting. What I need help with is how to unroot this device. I used the Root De La Vega procedure very shortly after it came out and it worked like a charm. I noted that when the phone boots up, there is the word "Custom" and an unlocked padlock. How do I get this AT&T model of the Galaxy Note 3 back to the condition, more or less, of when I bought it about a week ago so that I won't have any issues getting the refund processed? I've heard some people requesting help with unrooting and they've been told to use the unroot in SuperUser. Will this get rid of the "Custom" wording on boot-up AND the unlocked padlock? If not, is there a way to get this back to the way it was or am I just out of luck since I only have about another week to return this device. Obviously, if I'm stuck, I'm stuck and I'll find a way to live with it. Who knows...I might actually get to liking it down the road when some of the quirks have been worked out. However, if there's a way to sort all of this out in a timely manner where there's no muss or fuss, that would be the ideal solution. Any help would be greatly appreciated.
KennyXL said:
I purchased the AT&T version of the Galaxy Note 3 a little less than a week ago and, to be honest, I'm not really keen on it. There are a number of reasons, but what it boils down to is that I just don't think I like it all that much. I've already sold my Galaxy Note 2, so I'll have to figure out what I'm going to do about a cell phone, but that's something beyond the scope of this particular posting. What I need help with is how to unroot this device. I used the Root De La Vega procedure very shortly after it came out and it worked like a charm. I noted that when the phone boots up, there is the word "Custom" and an unlocked padlock. How do I get this AT&T model of the Galaxy Note 3 back to the condition, more or less, of when I bought it about a week ago so that I won't have any issues getting the refund processed? I've heard some people requesting help with unrooting and they've been told to use the unroot in SuperUser. Will this get rid of the "Custom" wording on boot-up AND the unlocked padlock? If not, is there a way to get this back to the way it was or am I just out of luck since I only have about another week to return this device. Obviously, if I'm stuck, I'm stuck and I'll find a way to live with it. Who knows...I might actually get to liking it down the road when some of the quirks have been worked out. However, if there's a way to sort all of this out in a timely manner where there's no muss or fuss, that would be the ideal solution. Any help would be greatly appreciated.
Click to expand...
Click to collapse
I'm not super familiar with the unrooting process, but try to unroot using SuperSU and reboot a couple of times to see if it goes away. If that doesn't work then flash the original firmware with odin and that should do it. Pretty easy to do from what I understand.
agent929 said:
I'm not super familiar with the unrooting process, but try to unroot using SuperSU and reboot a couple of times to see if it goes away. If that doesn't work then flash the original firmware with odin and that should do it. Pretty easy to do from what I understand.
Click to expand...
Click to collapse
Perhaps this is showing my ignorance, but since the AT&T Galaxy Note 3 has a locked bootloader (which, as of yet, has not been unlocked), would that prevent Odin from flashing a new image? If I don't need an unlocked bootloader to flash with Odin, do you know where I might find the original image that came with my phone from AT&T in a format that Odin can flash? I haven't tried the SuperSU yet since I want all my options readily available so that if one fails, I can move on to the next one.
KennyXL said:
Perhaps this is showing my ignorance, but since the AT&T Galaxy Note 3 has a locked bootloader (which, as of yet, has not been unlocked), would that prevent Odin from flashing a new image? If I don't need an unlocked bootloader to flash with Odin, do you know where I might find the original image that came with my phone from AT&T in a format that Odin can flash? I haven't tried the SuperSU yet since I want all my options readily available so that if one fails, I can move on to the next one.
Click to expand...
Click to collapse
To my understanding you can flash anything with Odin on a locked bootloader phone that is "signed". If you give me a few minutes I'll help you look for the original odin file to flash.
agent929 said:
I'm not super familiar with the unrooting process, but try to unroot using SuperSU and reboot a couple of times to see if it goes away. If that doesn't work then flash the original firmware with odin and that should do it. Pretty easy to do from what I understand.
Click to expand...
Click to collapse
agent929 said:
To my understanding you can flash anything with Odin on a locked bootloader phone that is "signed". If you give me a few minutes I'll help you look for the original odin file to flash.
Click to expand...
Click to collapse
I really appreciate your help. Every time I've used Odin in the past has involved a phone with a non-locked bootloader (as far as I know) so this is new territory for me.
KennyXL said:
I really appreciate your help. Every time I've used Odin in the past has involved a phone with a non-locked bootloader (as far as I know) so this is new territory for me.
Click to expand...
Click to collapse
Not a problem. I've been looking for that odin file with no luck. I would PM designgears and ask him if he can provide a link for it because you couldn't find it.
agent929 said:
Not a problem. I've been looking for that odin file with no luck. I would PM designgears and ask him if he can provide a link for it because you couldn't find it.
Click to expand...
Click to collapse
Thanks. I'll give that a try.
Use the same file that u used to root. The one with the one click. After it pass, you're back to stock. i just did it yesterday.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
If you looked at the root thread you'd see directions to unroot right there.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
panday74 said:
Use the same file that u used to root. The one with the one click. After it pass, you're back to stock. i just did it yesterday.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Zach Alt said:
If you looked at the root thread you'd see directions to unroot right there.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
What they said
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4
panday74 said:
Use the same file that u used to root. The one with the one click. After it pass, you're back to stock. i just did it yesterday.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried the SuperSU full unroot method - didn't remove the padlock, flashed the one click - didn't remove it, and just flashed the second (for funsies) and that didn't help (probably shouldn't have expected it to).
I'm returning my note and can't get rid of the lock. Will PM Designgears I guess
Did you restart it a few times? Also a factory reset?
Sent from my SAMSUNG-SM-N900A using Tapatalk 5
seanu13 said:
I tried the SuperSU full unroot method - didn't remove the padlock, flashed the one click - didn't remove it, and just flashed the second (for funsies) and that didn't help (probably shouldn't have expected it to).
I'm returning my note and can't get rid of the lock. Will PM Designgears I guess
Click to expand...
Click to collapse
I was kinda wondering how to remove the padlock also. I have read that some people that haven't even rooted have the padlock on boot up also??? I read somewhere about triangle away working, have you tried that?
agent929 said:
Did you restart it a few times? Also a factory reset?
Sent from my SAMSUNG-SM-N900A using Tapatalk 5
Click to expand...
Click to collapse
yes to both (restarted 5 times). since i was already so far into the root process, I added the files to the sdcards that are in the root steps, and the lock went away. Then I finished rooting.
went back and did one click again and still had the lock after rebooting 5 times. Thought about how it went away after adding the files so I skipped through the phone setup, enabled USB debugging again and added a dummy file to the sd card (a .csv I had on my desktop) and then removed it. Rebooted, and the lock was gone.
I'd use the padlock hack in Wanum and hide the root apps via Nova Launcher just to stick it to ATT and return it rooted.
Sent from my SAMSUNG-SM-N900A using xda premium
Omg, just reflash the stock rom from the package. Says so in the instructions.
READ!
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Jammol said:
Omg, just reflash the stock rom from the package. Says so in the instructions.
READ!
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you READ, you will see he already did that.
agent929 said:
If you READ, you will see he already did that.
Click to expand...
Click to collapse
The last post that was here when I posted was yours. That's why I posted for him to Read the instructions.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Ok well here's what I did and the padlock is gone.
Factory reset on the phone
Phone rebooted and I removed the super su app using the setting in the su app.
Then flashed the one click 9 tar
phone reboots on its own after flashing, icon was still there
rebooted the phone twice and the padlock was gone
Not sure if I just got lucky or what lol
Jammol said:
The last post that was here when I posted was yours. That's why I posted for him to Read the instructions.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Got ya..tapatalk has been mean to me too lol
---------- Post added at 10:26 AM ---------- Previous post was at 10:25 AM ----------
Quickvic30 said:
Ok well here's what I did and the padlock is gone.
Factory reset on the phone
Phone rebooted and I removed the super su app using the setting in the su app.
Then flashed the one click 9 tar
phone reboots on its own after flashing, icon was still there
rebooted the phone twice and the padlock was gone
Not sure if I just got lucky or what lol
Click to expand...
Click to collapse
I know you have to reboot a few times to set the status somehow, iB4STiD explained it in one of his post before.
Ok, so I got my hands on a new g2 that came with Verizon's VS98012B. Rooted it successfully in a snap with ioroot24. Then installed FreeGee and attempted to install TWRP 2.3.3.3.
Then things went wrong. FreeGee hung for a while, then it seemed to crash, opened it again, and 2.3.3.3 supposedly installed successfully immediately. Chose reboot to recovery, it turned off, and that's it.
It won't turn on. It's not boot looping. The LG screen never comes up. I can't get to any recovery. Power and Vol Down, don't do anything. I've tried every combo of power and the volume buttons but the most it'll do is a quick vibrate, again nothing on the screen though. It won't connect to the PC or charge.
Freegee F'd me hard. Anybody got any ideas? I literally had the phone for less than an hour... UGH
I went through the EXACT same process and i'm now in the same situation as you. I have a lg g2 vs980 on 12b with jellybean 4.2.2 (just got it yesterday). I rooted with ioroot22, then clicked twrp 2.6.3.3 in freegee which seemed to be stuck at the processing screen. I exited and went back in, and then freegee said complete or something. So i clicked reboot recovery, and bricked phone resulted. Completely black screen with no response at all. The only thing it does is vibrates a couple times if i hold power, but nothing more than that.
Another weird thing, if it's plugged into the wall or pc with a charger and i hold power down....a red led flashes 8 times and then the phone vibrates and then the red led flashes 8 times and this just repeats endlessly until i let go of the power button. Seems like the batterys dead but it was at 67% when i clicked reboot recovery so that wouldn't make sense. I'm currently charging the phone because there's really nothing left to do...i'm pretty sure it's a hard brick and i have no idea what caused it.
Freegee doesn't touch anything but recovery for 12b people. How did you reboot to recovery? The freegee app? When it hung was it stuck downloading? The zips it downloads are signed so it's not possible to get a bad download and it still try to flash it.
I'd really like to get the logs from freegee once you get it restored. Have you tried download mode?
No matter what you should be fine to still boot normally although I know you say you can't.
Sent from my LG-LS970 using xda app-developers app
I have this same problem. Just tried to make a back up with TWRP 2.6.3.3 and it bricked. I've used TWRP to install a ROM before, and it worked fine. I recently went back to using Clockwork, but then needed TWRP to install Malladus and i tried making a back up and this happened. The only response I get from the phone is a single vibration while holding down the power button.
---------- Post added at 07:42 PM ---------- Previous post was at 07:36 PM ----------
Shelnutt2 said:
Freegee doesn't touch anything but recovery for 12b people. How did you reboot to recovery? The freegee app? When it hung was it stuck downloading? The zips it downloads are signed so it's not possible to get a bad download and it still try to flash it.
I'd really like to get the logs from freegee once you get it restored. Have you tried download mode?
No matter what you should be fine to still boot normally although I know you say you can't.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
FreeGee does though, I used it to install ClockWork and TWRP recoveries before. I already had the file on my phone, so FreeGee just "installed" it and now it doesn't work. I've used it to backup and install before so it's weird that it would do this now. :-\ And what's this download mode you speak of.
Same thing happened to me. I rooted Verizon LG G2 used FreeGee and when first trying to go into recovery I got nothing. Same thing just vibrates when i hold down. Can't boot to recovery and can't boot into download mode. Need help......
ya i get the endless red led flash vibrate cycle thing with power button and when plugged in.
i took it apart and unplugged the battery for a while, replugged, reassembled and still the same thing. didnt help but figured i'd give it a shot.
i dont know what it was doing when it was hung. i believe it said 'installing twrp 2.3.3.3' or something like that. cant do download mode. cant connect to pc to do the lgtool restore thing. pretty much it seems like its hard bricked to me but i dont have much experience with this. btw, i think i may have had the phone hooked up the computer still in ethernet mode from rooting it moments before. i really cant remember for certain though.
man do i wish i just pushed this manually and skipped freegee. was my first time trying it.
Same deal here, and I usually flash recoveries through ADB. My fault for being lazy about it I guess. Would love to return the thing but I've already taken quite a few pictures with it.
Shelnutt2 said:
Freegee doesn't touch anything but recovery for 12b people. How did you reboot to recovery? The freegee app? When it hung was it stuck downloading? The zips it downloads are signed so it's not possible to get a bad download and it still try to flash it.
I'd really like to get the logs from freegee once you get it restored. Have you tried download mode?
No matter what you should be fine to still boot normally although I know you say you can't.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
I had the same thing happen to me today.Can't get into download mode. The phone won't respond to anything as stated before. I used quick boot.
---------- Post added at 08:31 PM ---------- Previous post was at 08:28 PM ----------
blue26 said:
Same deal here, and I usually flash recoveries through ADB. My fault for being lazy about it I guess. Would love to return the thing but I've already taken quite a few pictures with it.
Click to expand...
Click to collapse
I normally install recovery manually too. Except if I update through goo.
All these reports of bricking peoples devices can't be by chance I think I will stay away from freegee any reports with other models other than vs980 don't know what happened I installed twrp with freegee about a month ago and I had 12b don't know what happened between then and know
Sent from my LG-VS980 using Tapatalk
spinninbsod said:
All these reports of bricking peoples devices can't be by chance I think I will stay away from freegee any reports with other models other than vs980 don't know what happened I installed twrp with freegee about a month ago and I had 12b don't know what happened between then and know
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
How long did it take for the app to complete the install?
45 seconds to 1 minute
Sent from my LG-VS980 using Tapatalk
Mine was stuck on the processing twrp screen for at least 10 minutes.
Clicking back did nothing, but home button took me out. Then when i went back in, it was normal no problem. If i tried clicking back though, it would get stuck at the processing screen again even though i didnt tell it to do anything (i just clicked back). Then it quickly said complete or something, so i did reboot recovery and game over.
It looks like everyone here thats bricked just got their phone quite recently (like me)...something's definitely going on
Sent from my DROID Pro using xda app-developers app
Is it possible that the freegee app download is corrupt and is not Installing recovery properly that redlight almost seems like its a hard brick this sounds a lot worse than a softbrick
Sent from my LG-VS980 using Tapatalk
spinninbsod said:
Is it possible that the freegee app download is corrupt and is not Installing recovery properly that redlight almost seems like its a hard brick this sounds a lot worse than a softbrick
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Maybe that's possible, i have no idea. Definitely a lot worse than a soft brick. I'm really hoping shelnutt can figure something out. If it's truly hard bricked, what options would there be verizon wise? Like take it back or exchange or something
Sent from my DROID Pro using xda app-developers app
That's really the only option I am going to look in the user guide to see if it says anything about a redlight plug them in for awhile and if they get hot it is most ddefinately a hardbrick do not go to sleep with these plugged in that is very dangerous check tommorow try to charge it but keep a close eye on it and if still nothing take it to verizon and hope for the best I any developers wanting to get in contact with shellnut I'm by no means a developer
Sent from my LG-VS980 using Tapatalk
---------- Post added at 09:11 PM ---------- Previous post was at 09:03 PM ----------
Everybody having this problem only with the vs980 right anybody with other variants please post here we need shellnut to see this so he might be able to figure out what's going wrong
Sent from my LG-VS980 using Tapatalk
Same Here
Worst part is I used freegee a while ago and it worked PERFECTLY. Not a single problem to be found then when I flashed mine back to stock and went through the whole process again. It fails no logo, no downloader mode, no recovery mode. Just a blank screen and it vibrates. -_- I also don't get the red flashing light.
spinninbsod said:
That's really the only option I am going to look in the user guide to see if it says anything about a redlight plug them in for awhile and if they get hot it is most ddefinately a hardbrick do not go to sleep with these plugged in that is very dangerous check tommorow try to charge it but keep a close eye on it and if still nothing take it to verizon and hope for the best I any developers wanting to get in contact with shellnut I'm by no means a developer
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Dangerous how? And is there any risk in taking it to verizon, considering we're rooted?
Sent from my DROID Pro using xda app-developers app
---------- Post added at 11:19 PM ---------- Previous post was at 11:14 PM ----------
Worst part is I used freegee a while ago and it worked PERFECTLY. Not a single problem to be found then when I flashed mine back to stock and went through the whole process again. It fails no logo, no downloader mode, no recovery mode. Just a blank screen and it vibrates. -_- I also don't get the red flashing light.
Click to expand...
Click to collapse
Plug the phone into your computer, them hold the power button for a long time. Red light starts flashing on mine
Sent from my DROID Pro using xda app-developers app
The battery might overheat and I dought there is any danger taking it to Verizon it sounds like it is hardbricked if they can't get it to turn on it should be fine if I were you guys i would stay away from freegee until this issue is fixed
Sent from my LG-VS980 using Tapatalk
spinninbsod said:
The battery might overheat and I dought there is any danger taking it to Verizon it sounds like it is hardbricked if they can't get it to turn on it should be fine if I were you guys i would stay away from freegee until this issue is fixed
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Yea i doubt verizon will be able to fix it anyways. Maybe ill take it to them later this week and see what they say.
If there's a next time, i'm pushing twrp.lok manually with adb which is what i should have done in the first place
Sent from my DROID Pro using xda app-developers app
spinninbsod said:
Is it possible that the freegee app download is corrupt and is not Installing recovery properly that redlight almost seems like its a hard brick this sounds a lot worse than a softbrick
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
No, the zips it downloads are signed, so if it's a corrupt download it won't pass sig check of the zip file, and it won't process it.
TheOriginalKyle said:
Worst part is I used freegee a while ago and it worked PERFECTLY. Not a single problem to be found then when I flashed mine back to stock and went through the whole process again. It fails no logo, no downloader mode, no recovery mode. Just a blank screen and it vibrates. -_- I also don't get the red flashing light.
Click to expand...
Click to collapse
People have used freegee on 12b for months with no issues. I'm baffled why all of sudden in the last 24hours it seems several people have run into issues with twrp. I've disabled twrp for now until we figure out what the actual issue is.
Freegee itself does not alter anything except the recovery partition when installing a recovery on Verizon 12b. And it wipes and flashes the recovery partition in the same action. The boot stack is not touch, nor is any part of the system/boot partitions touched.
The fact that no one's device shows up in qhusb mode in windows means no one is bricked. No one's device is in bulk mode either, so the devices should be able to boot normal, or boot into download mode.
Nothing has changed with freegee in the last 24 hours, besides a beta build I pushed to the beta channel of the playstore. No one is running the beta currently according to google though.
Were you guys running anything else besides a pure stock rom? How did everyone root?
UPDATE2: This only seems to happen if you uninstall the Launcher system app. Mine does not seem to be affected by Xposed or other mods, and works 100% fine now in U Power Saving.
Just decided to try Ultra Power Saving mode after rooting and modding my phone yesterday. I'm not sure what exactly caused it (xposed, root, w.e) but my phone will not boot past the ATT Globe now. Just thought everyone might appreciate a heads up that they may have to factory reset after enabling this setting.
I'll update if my phone decides to boot up (letting it sit now)
UPDATE: It seems that after rooting, U power saving does have the potential to BRICK your phone. DO NOT ENABLE FOR ANY REASON AFTER ROOTING.
My gut says the culprit was uninstalling Launcher.apk (thought it was the google launcher >_>) gonna have to factory reset now.
More info dude
You might have just freaked out a noob here. Root was just achieved yesterday for the Verizon and ATT platform. Please post your hardware software state so we don't get confused here.
chronicaust said:
Just decided to try Ultra Power Saving mode after rooting and modding my phone yesterday. I'm not sure what exactly caused it (xposed, root, w.e) but my phone will not boot past the ATT Globe now. Just thought everyone might appreciate a heads up that they may have to factory reset after enabling this setting.
I'll update if my phone decides to boot up (letting it sit now)
Click to expand...
Click to collapse
Same here cant get past the logo did a factory reset in recovery and still a no go. I tried to Odin back but still a no go as the files we have to return to stock are older I guess than the version I had on my phone. I am not 100% sure what caused it on my phone. Ive let mine sit for 20minutes or so and no go. took out the battery for a few hours etc no go. So now I am looking for Firmware KOT 49.G900AUCU2AND3.
pcidiot said:
Same here cant get past the logo did a factory reset in recovery and still a no go. I tried to Odin back but still a no go as the files we have to return to stock are older I guess than the version I had on my phone. I am not 100% sure what caused it on my phone. Ive let mine sit for 20minutes or so and no go. took out the battery for a few hours etc no go. So now I am looking for Firmware KOT 49.G900AUCU2AND3.
Click to expand...
Click to collapse
Are you sure that your didn't remove or freeze the launcher? If you don't have a third party launcher installed, freezing/removing the launcher.apk will cause the phone to not boot past the logo screen.
cjranucci said:
Are you sure that your didn't remove or freeze the launcher? If you don't have a third party launcher installed, freezing/removing the launcher.apk will cause the phone to not boot past the logo screen.
Click to expand...
Click to collapse
Nope I didn't delete any launchers. I left both in tacked stock and the Google launcher I was using before Root.
yup, enabling ultra power saving blows up the phone confirmed here also.. All i removed was the AT&T crap, shealth, drive mode, anda few other items.,. now phone is stuck at the black and white at&t logo wont do anything else..
---------- Post added at 03:54 PM ---------- Previous post was at 03:53 PM ----------
cjranucci said:
Are you sure that your didn't remove or freeze the launcher? If you don't have a third party launcher installed, freezing/removing the launcher.apk will cause the phone to not boot past the logo screen.
Click to expand...
Click to collapse
had apex launcher running and as default in my case. phone is frozen on (white/black like its in power saving mode AT&T logo)
Never. Delete. Stock. Apps. Just freeze them
Sent from my SAMSUNG-SM-G900A using Tapatalk
robstunner said:
Never. Delete. Stock. Apps. Just freeze them
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
I disagree. There are serious disk space concerns with this phone. If I am not going to use an app,and I have root, I am deleting it to recover the space it takes plus any associated files. If that breaks something, then that sucks. You can always reinstall through factory reset.
I'm fairly confident your wrong. Factory reset won't make uninstalled system apps reappear. That's why they don't let you delete them normally.
Just Odin back to stock after Odin flashes reboot into recovery and wipe all data reboot and all should be well
Sent from my SM-G900F using Tapatalk
cjranucci said:
I disagree. There are serious disk space concerns with this phone. If I am not going to use an app,and I have root, I am deleting it to recover the space it takes plus any associated files. If that breaks something, then that sucks. You can always reinstall through factory reset.
Click to expand...
Click to collapse
except where they said they tried to odin back in and no luck so try again
Suggest that someone change the title to include AFTER TOWELROOT in there. For someone like me who had the files on the phone but just didn't pull the trigger yet, it will better keep them informed.
cyberace1985 said:
except where they said they tried to odin back in and no luck so try again
Click to expand...
Click to collapse
willing to bet there's some user error involved...Odin back to stock should fix any issues.
Sent from my SM-G900F using Tapatalk
djkinetic said:
willing to bet there's some user error involved...Odin back to stock should fix any issues.
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
How much you willing to bet..
You wrong if you have lock bootloader and you took update and bootloader is updated you can't odin back to previous version. We don't have current (updated) odin file for AT&T S5 yet.
Swiping from dark side of Galaxy S5.
Can anyone confirm that after unrooting with superuser it Will be safe to use ultra power saving mode?
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
vxkillswitchxv37 said:
Can anyone confirm that after unrooting with superuser it Will be safe to use ultra power saving mode?
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I confirm it.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Same with Samsung keyboard too. That's the only keyboard that works in UPS mode.
norbarb said:
How much you willing to bet..
You wrong if you have lock bootloader and you took update and bootloader is updated you can't odin back to previous version. We don't have current (updated) odin file for AT&T S5 yet.
Swiping from dark side of Galaxy S5.
Click to expand...
Click to collapse
try flashing the file without the boot loader.
Sent from my One M8 using Tapatalk
djkinetic said:
try flashing the file without the boot loader.
Sent from my One M8 using Tapatalk
Click to expand...
Click to collapse
Worked for me, and so far at least one other person in my thread.