Recently I completely wiped my phone to get rid of root. I know. Bad decision. Here's the deal though. After installing (flashing) countless stock roms, custom roms, and other solutions, I cannot get it to unbrick. The furthest I've come is getting stuck on the "untrusted" screen. Am I doing something wrong? I've tried flashing System, Recovery, and Boot for every rom that I have found. I've spent a bunch of time getting nowhere. It seems hopeless. Can someone help?
Hello,
If you pay 15€ you can do this :
https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775
I've unbricked my phone with this tuto.
Yeah, definitely worked for me, too. Absolutely worth the 15 bucks! :good:
Here's how I did it, step by step (no guarantees): https://forum.xda-developers.com/showpost.php?p=72794604&postcount=6
Related
im very inexperienced.... VERY!...lol well i rooted using the v8 all in one method. fooling around with rom manager, i hit back up current rom while i was downloading one. went to reboot and not past lg screen. tried the power/ vol down recovery and deleting.... would still stop at lg screen. is there any hope? stupid question...... im have a capped plan, so i got stuck while downloading, could it still be downloading? basically pertaining to overages
Reflash Kernel!
Yeah, happened to me once, too!
The problem could be, that you are using a wrong kernel.
Try to reflash the original kernel and the standard rom of your phone and start over again!
And for the next time:
Read the threads CAREFULLY before flashing! This prevents errors and bricking.
Good Luck
The_Mighty_Muffin
the thing is i didnt't "flash" a rom. i just downloaded something within rom manager and it happened while backing up current rom. now how do i go about fixing it. im not really sure how. thanks in advance
please help
All I can tell you is...as long as you can see something, a blinking screen, a logo, anything, there is still hope. Where you using the phone or some PC based software?
i was using the rom manager. i just need help getting this thing stock. dont care about deleting anything. just want it to work, thank you in advance
i think my only problem is getting the vs910.dll to work... dont know what version. i had latest ota update
Someone please please help me. I am in desperate need of a solution. And before I lay out the issue I am having, I would like to thank everyone for taking their time to read through my post and give their input. I truly appreciate it everybody. Much much thanks.
Just as a disclaimer, I've looked all over the internet, everywhere I can possibly find for days on end, and none of what I found worked for me. It feels like I tried everything there could be, and that is why I am coming here. Again, thank you.
So here's a little background information: I have a Verizon Samsung Galaxy S4 (SCH-I545). I got the phone over the summer, and as soon as I received the phone I was updated to the apparently dreadful VRUMAE7 update. There afterwards, I tried rooting the phone. I've had rooting experience before with decent success, and never ran into problems like I did. It took awhile for me root my S4, but after awhile I was able to successfully root it. Although, I'm pretty sure I may have done something wrong. You will see why shortly.
So a week or two back, my S4 prompted me to update to the next update. I believe it was Android 4.3 (VRUEMJ7). I was very excited for the update and tried running it. But every time I accepted the update and tried updating, my phone went into Recovery to download the new update and stalled out with an error. Thereafter I would have to reboot the phone to get it working again. After failing to update multiple times, I realized that it is probably because I messed up my root. So without doing much research, I simply tried flashing the stock firmware that came with my phone thinking it should work pretty flawlessly.
I have a Mac OS, so using VmWare Fusion with Windows 7, I downloaded Odin and booted up my phone on Recovery mode, downloaded the stock VRUMAE7 firmware I found online, and began flashing. But Odin threw me a error, so I tried rebooting my phone thinking it would go back to normal. BUT this time, it kept going into recovery mode with a yellow Triangle saying firmware was installed incorrectly, etc. I was so frustrated at this point, thinking that I truly may have bricked my phone.
I began on this long journey of going through all the sources I could find online possible, downloading every type of Verizon S4 firmware I can find, trying every Odin method possible, and spending long long hours of the night biting my fingers at my dreadful fate. I even tried flashing the stock PIT File along with my stock firmware, to see if that would fix it. But no luck. I also tried using a standard windows machine rather than VMware, still with no luck.
I ask you all to please suggest any ideas, thoughts, or inputs you possibly can. I am willing to try anything and everything at this point. Please do help. I appreciate you guys reading through my lengthy question, sorry for that. Just wanted to lay everything out.
Thank you very very much.
muazra said:
Someone please please help me. I am in desperate need of a solution. And before I lay out the issue I am having, I would like to thank everyone for taking their time to read through my post and give their input. I truly appreciate it everybody. Much much thanks.
Just as a disclaimer, I've looked all over the internet, everywhere I can possibly find for days on end, and none of what I found worked for me. It feels like I tried everything there could be, and that is why I am coming here. Again, thank you.
So here's a little background information: I have a Verizon Samsung Galaxy S4 (SCH-I545). I got the phone over the summer, and as soon as I received the phone I was updated to the apparently dreadful VRUMAE7 update. There afterwards, I tried rooting the phone. I've had rooting experience before with decent success, and never ran into problems like I did. It took awhile for me root my S4, but after awhile I was able to successfully root it. Although, I'm pretty sure I may have done something wrong. You will see why shortly.
So a week or two back, my S4 prompted me to update to the next update. I believe it was Android 4.3 (VRUEMJ7). I was very excited for the update and tried running it. But every time I accepted the update and tried updating, my phone went into Recovery to download the new update and stalled out with an error. Thereafter I would have to reboot the phone to get it working again. After failing to update multiple times, I realized that it is probably because I messed up my root. So without doing much research, I simply tried flashing the stock firmware that came with my phone thinking it should work pretty flawlessly.
I have a Mac OS, so using VmWare Fusion with Windows 7, I downloaded Odin and booted up my phone on Recovery mode, downloaded the stock VRUMAE7 firmware I found online, and began flashing. But Odin threw me a error, so I tried rebooting my phone thinking it would go back to normal. BUT this time, it kept going into recovery mode with a yellow Triangle saying firmware was installed incorrectly, etc. I was so frustrated at this point, thinking that I truly may have bricked my phone.
I began on this long journey of going through all the sources I could find online possible, downloading every type of Verizon S4 firmware I can find, trying every Odin method possible, and spending long long hours of the night biting my fingers at my dreadful fate. I even tried flashing the stock PIT File along with my stock firmware, to see if that would fix it. But no luck. I also tried using a standard windows machine rather than VMware, still with no luck.
I ask you all to please suggest any ideas, thoughts, or inputs you possibly can. I am willing to try anything and everything at this point. Please do help. I appreciate you guys reading through my lengthy question, sorry for that. Just wanted to lay everything out.
Thank you very very much.
Click to expand...
Click to collapse
Hi there,
it seems an easy problem but do it at your own risk I don't take responsibility of bricked device,etc
so lets go with what you need:
A- Odin [I believe you already have it]
B- stock rom go to this site:
androidayos.com/samsung-galaxy-s4-odin-stock-firmware/
and choose the suitable stock rom based on your Baseband version
C- Drivers installed for your device [if your mac/laptop recognizes your device then skip this step if not google it,download the drivers and install them]
IMPORTANT:Make sure you have 80% or more on battery
after you get these stuff install the device drivers as mentions in C then turn your device off and power it while holding volume up it should take you to download.now open odin and navigate it to the rom which you downloaded from B and flash it .wait for green color to appear and your back to your stock now it should open normally hope that I helped
Hello there!
Im new to this forum, thou ive used some stuff from it before.
So, i got tired of my ICS o3d.. Too many problems with apps and other stuff.
And now ive tried to flash JB 4.2.2 to it.
Worked fine throu the flash, but stucks in bootloop on first boot.
And now i cant even do sh*t with my phone. Cant even get into recovery.
So, im not noob on flashing/rooting and all that. Been doing it for some years now.
But never got a bootloop like this one before.
How do i fix this?
EDIT:
Sometimes when i try to get into recovery (by pressing vol - button) it asks me if i wanna do a hard factory reset. And ive done that now two times. Still stucks on bootloop.
solved
Sorry for doubleposting.
But, i managed to save the phone.
OMAPflash + LGflashtool = unbrick
thanks to the man who invented them things.
Sulotion here:
[GUIDE] [P920/5] [SU760] Resurrection Guide (Lets get those brick's fixed...)
Friggin' awesome.
Now i only need to flash for JB again hope for not brick it again.
So..
the rom itself runs fine. No 3D anyhow.
But, my IMEI got lost.
And i cant fix it. Help needed!
Feels like im flooding the **** out of this thread. Sry for that.
BUT..
i managed to get my IMEI back.
I did a recovery with LGmobile Support Tool. And then i got bootloop from hell.
So i go back to the whole unbricking procedure.
And thank god it worked.
Too bad im back on 2.3.5 now. Want 4+.
Maby its for the best to stay on 2.3..
Thread can be closed.
Hi all,
I've been ROM'ing since 2013 on multiple devices so I am somewhat familiar with adb/fastboot flashing and commands, what to do, what not to do, etc.... I just picked up a used pixel and first thing I did was unlock the bootloader - no problem. Next I go to root, so I began following this tutorial https://android.gadgethacks.com/how-to/root-your-google-pixel-pixel-xl-0174670/ , as instructed I DL the required drivers, image files, patch file etc...and follow this tutorial for installing TWRP https://android.gadgethacks.com/how-to/install-twrp-custom-recovery-your-pixel-pixel-xl-0175163/ , I get to step 8 and instruct via the command window to fastboot boot twrp.img, just as instructed. Everything appeared to be going the way it should as it started to boot to TWRP but almost as quickly the phone just died. I mean dead as a door nail. It won't do a thing. It won't even charge now. I have never had a phone just die like this. I fear I have met my first true full on brick.
I mean, yeah, I have soft bricked phones many a times but always had a backup to restore or was able to dig my way out one way or another but that was explainable by messing with questionable ROM's or something similar. Here I was just booting to the phone specific most recent version of TWRP by a solid well known tutorial with solid links, no indication that these could be the wrong images or zip's at all....but I'll be damned if this phone is dead as hell. I'm hoping someone can shed some light as to what happened or even miraculously tell me that it can be fixed.
Guys, is this a worst case scenario full on brick with no hope or getting it back to life? If so, why? Where did I go wrong? If this is going to be what I fear it is I hope to at least understand how it happened so I can avoid it in the future. This was a very expensive F-up on my part. I am beside myself with grief and disbelief that I could have done this with as many times as I have unlocked bootloaders, rooted, installed TWRP, flashed ROM's, etc.. I mean I 'm not the best but I am not a noob by any means. I feel like such a dumb ass right now!
Appreciate any help or explanation anyone can offer. Thanks.
We don't flash avb or any other patches anymore and haven't for like an android version and a half. For future reference look for more current information when modding a phone and for simple things like root guides go to xda don't just ask Google.
@kerryh420,
Those are some pretty old tutorials!
After plugging in the charger and wait for say 10seconds, can you boot into bootloader with button combo?
(Power + volume down or power + volume up for recovery as alternative)
Cheers
Sent from my Galaxy Tab S2 8.0 using XDA Labs
No offense, if you've been ROM'ing since 2013 you'd know not to go to other websites for tutorials! XDA is your best friend to follow instructions on Rooting, Flashing a recovery, and etc! Sorry that happened to ya. If it's literally dead you're probably out of luck and I know that's not what you want to hear. My best advice is to not follow tutorials on other websites. Good luck on your next device!
I was following the instructions here: https://forum.xda-developers.com/xperia-xz/help/sony-xperia-xz-dual-f8332-unlock-t3640302. I unlocked the bootloader just fine. But when I flashed the andro plus kernal, the phone now just sits on the sony logo. I thought I flashed the right one. I am still able to fastboot and can enter recovery, but I don't know where to go from here. I have spent the day reading up on different fixes, but with broken links, broken images, and acronyms galore, the learning curve is steep and I haven't been able to figure anything out. What is the next step to try and recover the phone? Any help would be greatly appreciated.
Ok, I figured it out. I don't know if the problem was caused by the wrong andro plus kernal version, but I had to reflash the 6.x.x version and repeat the steps. Took some time, but I am learning quite a bit.