Related
i followed the instructions to the letter and after it was done
i was presented with a picture of an IC microchip and an arrow pointing down.
i restarted the phone and now it wont start.
i cant get into bootloader mode or recovery mode...
Please help me get my phone back!!!!
did you let it finish? the ic microchip and arrow pointing thing? or did you yank out the battery?
i panicked and yanked out the battery...i killed it, didnt i?
I think he didn't let the phone finish and restarted the phone cause it wasa taking too long if that's the case 99.0% the phone is bricked. It happend to somebody else here already. Jy
He just call tmobile and told them the wasn't turning on and they send him a replacement.
I think this is something that needs to be added to the flashing roominstructions.
slyfury said:
i panicked and yanked out the battery...i killed it, didnt i?
Click to expand...
Click to collapse
Im sorry man, you did the one thing you shouldnt have while flashing
Perrosky said:
I think he didn't let the phone finish and restarted the phone cause it wasa taking too long if that's the case 99.0% the phone is bricked. It happend to somebody else here already. Jy
He just call tmobile and told them the wasn't turning on and they send him a replacement.
I think this is something that needs to be added to the flashing roominstructions.
Click to expand...
Click to collapse
i agree 100% please add that to the instruction for noobs like me
oh well, i just hope i get a replacement quickly
that happened to me so i called t-mo and told them that my g1 wont turned on at all and tried the other battery so they send me a replacement. of course i was a noob back then. i learned my lesson in a hard way so i suffer a week without my precious g1 lol.
slyfury said:
i followed the instructions to the letter and after it was done
i was presented with a picture of an IC microchip and an arrow pointing down.
i restarted the phone and now it wont start.
i cant get into bootloader mode or recovery mode...
Please help me get my phone back!!!!
Click to expand...
Click to collapse
also once you called t-mo do not let them know that youre modifying your phone otherwise they will not send you another handset.
slyfury said:
i followed the instructions to the letter and after it was done
i was presented with a picture of an IC microchip and an arrow pointing down.
i restarted the phone and now it wont start.
i cant get into bootloader mode or recovery mode...
Please help me get my phone back!!!!
Click to expand...
Click to collapse
how about take out the sdcard and connect it to the computer, put the jfr33 in it, and flash your phone again. It works
also he could try getting into recovery mode using adb or sumthin...i am not too sure about it...but i think it can be done..!!!
tannyfiles said:
also he could try getting into recovery mode using adb or sumthin...i am not too sure about it...but i think it can be done..!!!
Click to expand...
Click to collapse
If the phone can't reach the bootloader or recovery console I don't think ADB is going to work but I could be wrong.
patience is a virtue
your topic title is misleading and could lead users who haven't tried yet to be too wary about flashing over to Haykuro's builds...
Ultimately...your phone didn't mess up after flashing 4.X..YOU messed up.
if you cant turn on youre g1 then it is dead, even if you connect it to pc or what if it cant be turned be on, it is dead cuz thats what happened to me so just call t-mo and tell them youre phone wont turn on and you tried another battery still wont turn and DO NOT tell them you modify or even saying you attemped to modify your g1's rom.
the best thing for him to do would be flash rc29 nbh and start from scratch...the phone is more than likely not bricked.
korndub said:
the best thing for him to do would be flash rc29 nbh and start from scratch...the phone is more than likely not bricked.
Click to expand...
Click to collapse
To my opinion, i do not think the phone is bricked since there is no hardware issue is involving, it's the software itself, if he can access to the root of the sd card, problem is solved.
but oh well, i would call Tmobile and request a new shinny phone . wait... they will send a refurbished one won't they? oh noo...
I have a similar problem, i was attempting to move apps to the sd card, partitioned it, installed the lucidrem rom and then started using his code and the flashing android loop started, turned it off and back on and still the flashing android, i used the fastboot method to restore my nandroid backup, and the phone is back to working, my problem is that i cant access recovery mode.
everything else is fine, just when i try to load the recovery mode it just stays on the boot screen, can anybody help a newbie out?
the bootloader works, and the phone can load normally, but the recovery mode wont start.
cueballv2 said:
I have a similar problem, i was attempting to move apps to the sd card, partitioned it, installed the lucidrem rom and then started using his code and the flashing android loop started, turned it off and back on and still the flashing android, i used the fastboot method to restore my nandroid backup, and the phone is back to working, my problem is that i cant access recovery mode.
everything else is fine, just when i try to load the recovery mode it just stays on the boot screen, can anybody help a newbie out?
the bootloader works, and the phone can load normally, but the recovery mode wont start.
Click to expand...
Click to collapse
That happened to me also. When I installed lucidrem's rom the recovery would work. What it actually was that when you first rooted your g1 do you rmr installing the recovery img? Well its pretty much the same thing lucidrems rom didn't have a recovery img command line attatched to it. I just installed recovery again from the terminal emulator just like it said in the root your g1 thread.
Atleast that is my side of the story. I don't anything about coding. So I could be wrong but that was just my experience.
bigballa said:
That happened to me also. When I installed lucidrem's rom the recovery would work. What it actually was that when you first rooted your g1 do you rmr installing the recovery img? Well its pretty much the same thing lucidrems rom didn't have a recovery img command line attatched to it. I just installed recovery again from the terminal emulator just like it said in the root your g1 thread.
Atleast that is my side of the story. I don't anything about coding. So I could be wrong but that was just my experience.
Click to expand...
Click to collapse
wow, thanks alot for your help, reflashed the recovery.img and it worked a treat, thought id bricked it good and proper, but your advice worked, thanks again.
Hi everybody, i was updating my rooted lg phone to the latest ota (bad idea, i know). Well, it bricked. i can get into recovery mode and download mode. I used lg flash tools and the results are : "Download Fails" and then " Can't change to DL mode". What is going on! . Am i out of a phone that i got a weeks ago or is their hope? Thanks in advance any advice is welcome!
nty123 said:
Hi everybody, i was updating my rooted lg phone to the latest ota (bad idea, i know). Well, it bricked. i can get into recovery mode and download mode. I used lg flash tools and the results are : "Download Fails" and then " Can't change to DL mode". What is going on! . Am i out of a phone that i got a weeks ago or is their hope? Thanks in advance any advice is welcome!
Click to expand...
Click to collapse
stock recovery or TWRP?
any way here is what i think you're searching for
http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
i was trying again with the flash tool on a different computer and it got significantly farther this time, to 94%. Now when i connect it it goes to the blue screen like it normally should with a number 2 showing and its just frozen there. So i do not know if i have twrp anymore, any advice?
nty123 said:
i was trying again with the flash tool on a different computer and it got significantly farther this time, to 94%. Now when i connect it it goes to the blue screen like it normally should with a number 2 showing and its just frozen there. So i do not know if i have twrp anymore, any advice?
Click to expand...
Click to collapse
you didnt disconnect the phone when it rebooted did you
Got it working, Thanks everybody.
nty123 said:
Got it working, Thanks everybody.
Click to expand...
Click to collapse
Do you mind posting what you did that was able to work? I have to wait to find someone that will let me use a windows computer to run the flash tool I guess as I cant run it on Mac OS X
Stuck on the TWRP screen, and flashing zips doesn't work, every reboot brings it to the TWRP screen and I cant seem to find system.img or boot.img in the file directory from that screen so I am thinking it ALL got wiped
Thanks for any help
Just a little FYI, you named the thread hard bricked, however you were only soft bricked. Hard Brick is a dead phone... No power, no lights, or any response.
j311slx said:
Do you mind posting what you did that was able to work? I have to wait to find someone that will let me use a windows computer to run the flash tool I guess as I cant run it on Mac OS X
Stuck on the TWRP screen, and flashing zips doesn't work, every reboot brings it to the TWRP screen and I cant seem to find system.img or boot.img in the file directory from that screen so I am thinking it ALL got wiped
Thanks for any help
Click to expand...
Click to collapse
Give this thread a try
http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
I have a rooted Note5 that i cant unroot no matter what i do it just wont unroot (Odin always fails).
The phone restarts during call for no reason and i found out that its only when the screen is dark while on a call.
I cant even update my phone because it just wont install any PA no matter what i do.
I think there's something wrong with the Kernel or maybe the whole system is ****ed up because after i rooted everything started happening when my brother messed it all up, so my phone has a security "Device Manager" and after the root it said "threat found", to fix press restart so he did... after that my phone just went to Samsung logo and off again and again. So i went to Odin and tried a bunch of firmware until i got it to turn on. But ever since that i cant unroot and my phone keeps restarting during calls.
Please help with anything I'm willing to pay if necessary.
Also, im sure its just because its rooted but whenever the phone turns on it says in red "Kernel is not seandroid enforcing"
I've tried everything that i know, i wouldn't be posting if i haven't searched everything and everywhere.
Thanks
komoruu said:
I have a rooted Note5 that i cant unroot no matter what i do it just wont unroot (Odin always fails).
The phone restarts during call for no reason and i found out that its only when the screen is dark while on a call.
I cant even update my phone because it just wont install any PA no matter what i do.
I think there's something wrong with the Kernel or maybe the whole system is ****ed up because after i rooted everything started happening when my brother messed it all up, so my phone has a security "Device Manager" and after the root it said "threat found", to fix press restart so he did... after that my phone just went to Samsung logo and off again and again. So i went to Odin and tried a bunch of firmware until i got it to turn on. But ever since that i cant unroot and my phone keeps restarting during calls.
Please help with anything I'm willing to pay if necessary.
Also, im sure its just because its rooted but whenever the phone turns on it says in red "Kernel is not seandroid enforcing"
I've tried everything that i know, i wouldn't be posting if i haven't searched everything and everywhere.
Thanks
Click to expand...
Click to collapse
To fix your issues you are having you need to flash @jovy23 's stock-modified kernel in tarp recovery.
Here is the link to jovy23's stock rooted kernel:
http://forum.xda-developers.com/tmo...ernel-stock-modified-kernel-touchwiz-t3194148
No need to unroot.
Good luck, Have a great day.
Sent from my SM-G928F using Tapatalk
Misterjunky said:
To fix your issues you are having you need to flash @jovy23 's stock-modified kernel in tarp recovery.
Here is the link to jovy23's stock rooted kernel:
http://forum.xda-developers.com/tmo...ernel-stock-modified-kernel-touchwiz-t3194148
No need to unroot.
Good luck, Have a great day.
Sent from my SM-G928F using Tapatalk
Click to expand...
Click to collapse
Ive Seen that before but i dont Know what I'm supposed to download or do. What do i download and also what do i use it with? Odin? Sorry noob here shouldn't have messed with something i don't know :/ lesson learned
re: kernel flashing
komoruu said:
Ive Seen that before but i dont Know what I'm supposed to download or do. What do i download and also what do i use it with? Odin? Sorry noob here shouldn't have messed with something i don't know :/ lesson learned
Click to expand...
Click to collapse
Do you have TWRP installed? You should know this if you are rooted.
The link I gave you (jovy23's) only has only ONE download link.
The download link is for the stock-modified kernel which you
need to copy to your phone's internal sdcard and flash it in twrp.
You don't need to do anything with Odin to fix the problem you
are having. You only need to flash the kernel using TWRP.
The download link is RED with BIG BOLD letters saying "DOWNLOAD". LOL
Misterjunky said:
Do you have TWRP installed? You should know this if you are rooted.
The link I gave you (jovy23's) only has only ONE download link.
The download link is for the stock-modified kernel which you
need to copy to your phone's internal sdcard and flash it in twrp.
You don't need to do anything with Odin to fix the problem you
are having. You only need to flash the kernel using TWRP.
The download link is RED with BIG BOLD letters saying "DOWNLOAD". LOL
Click to expand...
Click to collapse
Ok ive done that before without knowing what i was doing now i know, but it still doesnt work, this is what i did.
Downloaded the kernel and ive tried 3 different TWRP Apps and it reboots my device and it takes to system recovery and i cant do anything from there except reboot, ive Pressed all 3 apply from... and it just gives me an action message that it failed to apply. Also At the bottom of system recovery theres a action message that says "dm-verity verification failed"
Idk what that is or if its normal but just letting you know just in case
komoruu said:
Ok ive done that before without knowing what i was doing now i know, but it still doesnt work, this is what i did.
Downloaded the kernel and ive tried 3 different TWRP Apps and it reboots my device and it takes to system recovery and i cant do anything from there except reboot, ive Pressed all 3 apply from... and it just gives me an action message that it failed to apply. Also At the bottom of system recovery theres a action message that says "dm-verity verification failed"
Idk what that is or if its normal but just letting you know just in case
Click to expand...
Click to collapse
I flashed an kernel img and now my device is stuck on Logo screen in red on top says "kernel not seandroid enforcing" and its stuck on that screen. Im currently trying to install a firmware through odin but its failing IDK what to do at this point.
komoruu said:
I flashed an kernel img and now my device is stuck on Logo screen in red on top says "kernel not seandroid enforcing" and its stuck on that screen. Im currently trying to install a firmware through odin but its failing IDK what to do at this point.
Click to expand...
Click to collapse
I imagine you got it figured out by now but it sounds like you don't have TWRP installed. You do that with Odin, we all start somewhere so I am not going to say you should know this or that but I will say go back to the general section and follow one of the guides to get it set up. I would start over if I were you by following one of said guides.
My root failed, and my phone is stuck in "Downloading". Is my phone screwed?
My version is 7.0, model number: SMG920V
I used this guide and a few other resources for my first root. I am an utter newb, basically. (Can't post links so I'll just say it was Tomsguide on how to root your S6.)
I did everything there, installed Odin, the root, yadayada, then got to the last step. I clicked start, and the bar on Odin 3 filled up just a bit before a big red "FAIL" cropped up. I panicked, and tried running it again. No dice.
If I'm remembering correctly, this error "Complete(Write) operation failed" was also there in the output. Now when I try press start to download the root, it just says "All threads completed. (succeed 0 / failed 0)" I think that's changed. Before it had said 1 for failure.
My phone is in downloading mode. Other threads have said that Samsung Kies is what usually causes this, but I don't have Kies. It's possible that during the install my janky USB cable disconnected from the phone. Would that mean I'm ****ed? On my phone's blue screen, there's a line that says, in red text on a black background, "Secure check FAIL : (recovery)". What does this mean, exactly? if I my phone is wiped, I don't really mind. But if it's bricked, that's frustrating as hell.
This is my first post on XDA. I would appreciate any advice, and if I've left anything out, please tell me and I will add it. Thanks.
Edit: My phone works now, I let it run out of charge then recharge it. No brick today, at least. But I still want to know what went wrong in the root process.
Well for future reference, if your phone is showing anything on the screen, it can probably be saved because it's just a software issue. A soft brick isn't anything to worry about. This is why everyone says to make a backup though, just in case.
The only time to be worried is when the phone wont turn on at all. I cant tell you where you went wrong but hopefully it keeps you from panicking next time.
DirtyDan771 said:
My version is 7.0, model number: SMG920V
I used this guide and a few other resources for my first root. I am an utter newb, basically. (Can't post links so I'll just say it was Tomsguide on how to root your S6.)
I did everything there, installed Odin, the root, yadayada, then got to the last step. I clicked start, and the bar on Odin 3 filled up just a bit before a big red "FAIL" cropped up. I panicked, and tried running it again. No dice.
If I'm remembering correctly, this error "Complete(Write) operation failed" was also there in the output. Now when I try press start to download the root, it just says "All threads completed. (succeed 0 / failed 0)" I think that's changed. Before it had said 1 for failure.
My phone is in downloading mode. Other threads have said that Samsung Kies is what usually causes this, but I don't have Kies. It's possible that during the install my janky USB cable disconnected from the phone. Would that mean I'm ****ed? On my phone's blue screen, there's a line that says, in red text on a black background, "Secure check FAIL : (recovery)". What does this mean, exactly? if I my phone is wiped, I don't really mind. But if it's bricked, that's frustrating as hell.
This is my first post on XDA. I would appreciate any advice, and if I've left anything out, please tell me and I will add it. Thanks.
Edit: My phone works now, I let it run out of charge then recharge it. No brick today, at least. But I still want to know what went wrong in the root process.
Click to expand...
Click to collapse
Not sure of the process you followed but there's one thing I do know, all Verizon handsets come with locked bootloader, you have to unlock the bootloader, think it's oem unlock before you flash anything in odin, I'm guessing that's why you got the fail message.
sofir786 said:
Not sure of the process you followed but there's one thing I do know, all Verizon handsets come with locked bootloader, you have to unlock the bootloader, think it's oem unlock before you flash anything in odin, I'm guessing that's why you got the fail message.
Click to expand...
Click to collapse
Thanks, I got the same tip about the bootloader on Reddit, but I don't see the option to enable OEM unlocking in Dev options. Does that mean I'm screwed?
DirtyDan771 said:
Thanks, I got the same tip about the bootloader on Reddit, but I don't see the option to enable OEM unlocking in Dev options. Does that mean I'm screwed?
Click to expand...
Click to collapse
It's a bit tricky tbh, you are better off looking in the s6 Verizon forums to see what's happening with root as it's a little tricky with the Verizon variants
I had the same problem.
Can you tell when Odin fails?
BaTarrY said:
I had the same problem.
Can you tell when Odin fails?
Click to expand...
Click to collapse
It will say FAIL in the upper left
DirtyDan771 said:
It will say FAIL in the upper left
Click to expand...
Click to collapse
In the buttom left it tells you what Odin is doin,
So I need to know after what file he is failing.
I have an s7 active that is stuck in the reboot loop. I am able to get it to download mode, but when i try to flash anything it won't flash and odin stops responding.
Can someone please help me?
Its an sm-891a
I was trying to find a stock rom to flash?
jrjorin said:
I have an s7 active that is stuck in the reboot loop. I am able to get it to download mode, but when i try to flash anything it won't flash and odin stops responding.
Can someone please help me?
Its an sm-891a
I was trying to find a stock rom to flash?
Click to expand...
Click to collapse
Here is a pic
I have been able to get it to download mode. I have tried flashing it with odin but it fails. I have no clue what the guy before me put on it. After it fails i get the security warning saying use smart start or something like that.
I have tried it and once I type in the info and click ok the program just closes.
All i am trying to do is get it back to stock.
Can anyone please help me?
Update i was able to get it flashed in odin but it still sticks on the recovery booting screen.
Any help is welcome
jrjorin said:
Update i was able to get it flashed in odin but it still sticks on the recovery booting screen.
Any help is welcome
Click to expand...
Click to collapse
Maybe someone can tell me what this means please
More info
I have tried to flash g891aucu2bqb2 7 all
It didn't flash
I was able to flash g891aucs6csg2 att6csg2 but it gets stuck in recovery booting.
I downloaded the newest sw from Samsung and it wont flash.
I was told i might have the wrong build #
Can someone please tell me something? ?
jrjorin said:
More info
I have tried to flash g891aucu2bqb2 7 all
It didn't flash
I was able to flash g891aucs6csg2 att6csg2 but it gets stuck in recovery booting.
I downloaded the newest sw from Samsung and it wont flash.
I was told i might have the wrong build #
Can someone please tell me something? ?
Click to expand...
Click to collapse
This is flash att 8.04
jrjorin said:
This is flash att 8.04
Click to expand...
Click to collapse
Got this on restart now
jrjorin said:
Got this on restart now
Click to expand...
Click to collapse
FYI
i was able to flash it with the Samsung tool, but it still is caught in the loop.
It comes up with android man and says installing system updating then restarts.
What do I try now??
jrjorin said:
FYI
i was able to flash it with the Samsung tool, but it still is caught in the loop.
It comes up with android man and says installing system updating then restarts.
What do I try now??
Click to expand...
Click to collapse
Update
Last night during the endless rebooting it came up with the recovery menu, then went past the first Samsung active logo to a fading Samsung logo and then the blue att logo.
Also the blue power light is now staying on.
And its still doing the boot loop
Another update :
Here is what I can get sometimes
I feel like someone out there can help me.
Please
Another update
Sorry for all the questions but i am still having problems.
Now I get this
Fail to open recovery no such file or directory
I was able to get to the recovery screen and I did the factory reset 2 times and cleared the cache.
It booted to the att logo and restarted.
Now it just shows the start up screen and then restarts.
jrjorin said:
Another update
Sorry for all the questions but i am still having problems.
Now I get this
Fail to open recovery no such file or directory
I was able to get to the recovery screen and I did the factory reset 2 times and cleared the cache.
It booted to the att logo and restarted.
Now it just shows the start up screen and then restarts.
Click to expand...
Click to collapse
Here is the recovery screen that shows its updated to sw ver 8
There is something weird with this phone. Yesterday I let the battery die to make sure it was a fresh boot and it came up with the red charge light for the first time and the correct charge symbol. Before it would charge but no lights and just a circle with lightning bolt.
Now its just doing the reboot loop again and won't go into recovery.
Has anyone else ever seen anything like that?
I am glad someone was able to help me. Apparently what i have been trying to flash is just a security update.
Can someone please send me a link for the latest full rom for s7 active?
I am able to flash this. G891AUCS6CSG2_ATT6CSG2
Is it a full rom?
I have tried every rom i can find. Either they won't flash because they are an older version, or the stick in the reboot loop.
The farthest i have gotten is the blue att ball
Still no luck and no help
Finally I see my problem.
FRP MODE is on.
I need a combination file for binary 6
Please.
Just wondering if this forum is in limbo . My s7 active was working perfectly fine [til 10/22/22] and then it froze and
then it would only go to download mode. So I flash latest Samfw.com_SM-G891A_ATT_G891AUCU6CTB1 ROM and
it goes to updating system, but displays ERASING - I have tried to install only recovery and the same
happens - It deletes everything I flash ? now it only flashed recovery, boot and modem and wont flash the larger BL,CS,CSC AP files ? Just trying to get the phone working again and to use it as a dash cam - LOL
Thanks for any input