I tried to upgrade my brothers samsung galaxy gio with a leaked version of it's 2.3.4 upgrade via "Odin".It kinda got stuck in the process and following the guide for it I removed the battery (it said to remove the battery if it stuck at a process for more than 10 minutes). After that when I tried to power it up it got stuck with an image of a phone and a pc connected with dots and a caution mark in between. For extra info recovery mode doesn't open but the download mode does. And I have tried to upgrade it a few times but gets stuck at the process named "ididb download"or something like that.
Is the phone bricked?????? Plz reply quick.
Hi,
Don't worry: as long as you can turn the phone on you should be OK, it's only a soft brick . Have you tried going in download mode again, and reflashed another ROM or even the one you attempted? Got evering right? OPS? Evering you must tick? Re-read the whole tutorial cause generally people mess up because they don't pay enough attention ^^
P.S. At least a million threads exist for this, you obviously haven't looked far before posting..
I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
hechoen said:
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
Click to expand...
Click to collapse
I didn't feel like i really hard bricked it until i saw the USB computer connection error "device pluged in malfunctioned" in more than one PC.
Then i really felt like its a hardware BIOS chipset level problem now but man...
That story cracked me up. That is exactly why I spend days reading before I even root my phone. I made the mistake one time on my old G1 and it could not be revived.
Congrats on getting it working. (especially without flooding the q&a with redundant questions that have been described in detail several places )
hani1400 said:
I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Click to expand...
Click to collapse
Wheooooooooowwww,..you just UNBRICKED mine, I know of the Battery pull etc...but the post you referenced
is MAGIC
This was not my first Rom nor Root on this phone, it weirdly happened while doing the GB starter....via ODIN, which i also used before..no clue what went wrong, oh well...
Thank you, thank you "i did"....Yohoooo
Yup i agree i like to read, reread then read as i do. This way i got a pretty good understanding of what I'm doing. Btw i have just started using one click and it is sooooo simple. I love it.
Sent from my SGH-T959V using XDA App
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
diavel said:
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=881162
Im still carrying this phone, stupid baseband unlock for iphone won't come out now I am carrying 2 phones, one as an ipod touch and the galaxy s! Good story, hope it can help others, but I am prepared to jump off of this bandwagon anytime now!
I inherited a Galaxy S7 from my brother after he recently passed away. He was with T-Mobile, so it's a G930T (I have the original box, too, which has come in handy). I brought it back home with me... to France. I figured I'd have it unlocked and replace my old smartphone with this newer one.
Since I didn't know what his pin was, I did a factory reset... and found myself stuck in FRP!
At that point I called T-Mobile and was able to have myself added as an authorized user on my brother's account. They gave me the pin (too late! gah!) and unlocked the phone on their end, as it had been fully paid for. But as far as the FRP thing they were unable to help.
After a lot of googling, I found a bunch of how-to videos explaining how to bypass FRP, I thought I was in luck... except none of them worked for me. Then I came across a comment stating that flashing the device might do the trick. So I decided to try that... but now I'm locked in a boot loop (on the Samsung Galaxy S7 screen that keeps flashing on and off).
Here's what I did, step by step:
1) I installed Odin 3.13.1 from samsungodin.com
2) I downloaded & unpacked a stock ROM from sammobile.com, more specifically this one:
G930TUVS8CRJ1 - GALAXY S7 SM-G930T TMB USA (T-MOBILE)
3) I connected the phone to the laptop
4) I ran Odin and selected (with the AP button) the AP_GS30T* file & hit "start"
Odin said PASS! and I thought all was good... except it wasn't.
So I went googling some more and found a great page... which I am not allowed to link to yet, apparently, but it's on thedroidguy's website.
Only problem is that I can NOT get into the Recovery Menu. When I try the procedure (Home+Volume Up+Power) all I get is "recovery booting" in a bright blue font and THAT starts flashing on and off instead of the Galaxy S7 screen. If I redo the same button sequence, it just switches back to the other screen.
The ONLY other screen I can get to (unless there's another trick I haven't heard of yet) is the blue 'Warning' screen from which you can install ROM's (Home+Volume Down+Power).
So I tried to reinstall that same ROM two other times. First because I wasn't sure if I'd ran Odin as an administrator the first time around, figured that might be the issue, but that didn't change anything. Then I gave it another shot, this time using the phone's original USB cable (I had initially used mine), hoping that would make a difference... but of course, it did not.
So... is there anything I can do at this stage? Did I maybe go for the wrong ROM? Is there another one I can try?
I just hope it's not permanently bricked :-o
So I managed to unbrick my device, yay me! It took me some time to figure it out, but the solution was quite simple. Up until that point I had only been flashing the AP file alone. What fixed my problem was to also flash the bootloader (BL) file. This got me out of that boot loop.
I still haven't managed to bypass that annoying FRP lock, though. Every technique I've tried has failed.
On the plus side, I'm becoming an expert at flashing :-o
I just came across a method that, I think, could work: flash the factory combination file, enable usb debugging, then flash the regular firmware (with all files except CP).
My problem is that I can only find ONE combination file for the G930T but it doesn't match ANY of the firmwares available on sammobile... is this a problem?
The filename is similar to the v6 firmwares, only the last 4 characters don't match.
The other issue is that none of the v6 firmwares will flash on my device (they all fail pretty quickly while going through the AP file)... will using the combination file fix this?
Any thoughts or suggestions would be greatly appreciated.
After the most recent update my phone got put into a bootloop that wouldnt stop for some reason, it would boot and then after I wanna say less than 20 seconds it would reboot itself, and just kept going on in this cycle unless I powered it off when it was booted. Anyway I've been trying everything I can to get the damn thing working again so I can at the very least get my pictures off of it without factory resetting it and nothing is working, and I sorta feel like I've made things worse. I tried flashing with Odin but after that the thing just stopped booting alltogether so that kinda limited my options a lot. Now I'm trying to sideload an update from an sd card which might work if i can find the right thing to sideload onto it but before it gets anywhere it tells me error in /sideload/package.zip (status 7) so either I just need a different thing to sideload or something's broken. Either way I don't know how to get it working cause I have no idea what I'm doing here so now I need help.
My phone is SM-G970U SPR
Sounds like you are in a bad spot. If your pictures are on internal storage then flashing anything in Odin will wipe that.
I think you need to accept that they may be lost.
not so fast, i've used home_csc in all my flashes and when I finally got one working all my stuff was still intact. Now i just need to figure out how to get it to stop bootlooping.
Hello friends, I am currently crying in the same boat!
So, similar to Oske829 my phone ( Samsung Galaxy S10e ) has entered into a bootloop after a recent update that occurred roughly on February 06, 2021.
I am also experiencing the same symptoms as well:
My phone starts to boot up, then fails and Approximately 20 seconds after, it repeats that cycle. The phone continues to bootloop until drained of its battery then repeats this cycle again once if it is charged. **this is the current situation**
After playing around with the buttons, the only progress I've made is reaching the Download Mode. Ive yet to try odin or anything else and would like to ask for some help please! I really want to be able to save the data on there (pictures, music, apps, etc..)
Any help is appreciated, Thanks!
AlphaFeedback said:
Hello friends, I am currently crying in the same boat!
So, similar to Oske829 my phone ( Samsung Galaxy S10e ) has entered into a bootloop after a recent update that occurred roughly on February 06, 2021.
I am also experiencing the same symptoms as well:
My phone starts to boot up, then fails and Approximately 20 seconds after, it repeats that cycle. The phone continues to bootloop until drained of its battery then repeats this cycle again once if it is charged. **this is the current situation**
After playing around with the buttons, the only progress I've made is reaching the Download Mode. Ive yet to try odin or anything else and would like to ask for some help please! I really want to be able to save the data on there (pictures, music, apps, etc..)
Any help is appreciated, Thanks!
Click to expand...
Click to collapse
Download the latest official firmware with Frija tool (no download caps unlike websites like Sammobile etc). Just be aware that if you download and use Android 11 you wont be able to downgrade to Android 10.
After you have downloaded it unpack the zip and run Odin. In order to preserve your data flash the HOME_CSC file not the regular CSC... file. Once you unpack the files you will see.
The phone needs to be in download mode for flashing and battery is suggested to be at 40% or more.
Btw a good way to get out of bootloop and get the phone to shut down is to connect the USB cable (could be from charger or PC) and then press Volume Down+Power buttons to force a restart. It may be nessesary to do this a few times.
At one point you will not see the boot screen but instead it will show the lightning bolt charging logo and the percentage. After that you can simply unplug the cable and the phone will turn off.
In order to enter Download mode the best way is to start with phone turned off. Hold Bixby+Volume Down buttons and connect the USB cable from PC. Once you see the confirmation screen you can release the buttons and press Volume Up to continue.
AlphaFeedback said:
Hello friends, I am currently crying in the same boat!
So, similar to Oske829 my phone ( Samsung Galaxy S10e ) has entered into a bootloop after a recent update that occurred roughly on February 06, 2021.
I am also experiencing the same symptoms as well:
My phone starts to boot up, then fails and Approximately 20 seconds after, it repeats that cycle. The phone continues to bootloop until drained of its battery then repeats this cycle again once if it is charged. **this is the current situation**
After playing around with the buttons, the only progress I've made is reaching the Download Mode. Ive yet to try odin or anything else and would like to ask for some help please! I really want to be able to save the data on there (pictures, music, apps, etc..)
Any help is appreciated, Thanks!
Click to expand...
Click to collapse
So incredibly glad to hear I'm not a lone soul dealing with this issue. I've tried a whole bunch of things to fix this issue but nothing is getting me anywhere. I tried flashing android 10 but as that other lad said you can't flash older versions of android.
At this point I think my only chance of saving the phone is to wait for a new system update to release and flash that in case it somehow magically fixes the phone for some reason. I wouldn't recommend trying to flash atm because it doesn't seem to help currently and if you donk it up you'll lose your data which is not something either of us want to do.
I'll let you know what happens if I try flashing a future update.
Well i had an even bigger problem initially. Not only was my S10e bootlooping. My EFS partition was missing files (dont know how that happened). That meant that IMEI was blank and there was not network connectivity aside from Wi-Fi.
Unfortunately even the stock firmware flash does not fix EFS. Thankfully i had a backup (multiple actually) stored away including EFS. So with some fiddiling around in custom recovery file manager (TWRP) i manged to get that restored. I did lose bunch of pictures in intrernal storage tho. Thankfully it was nothing important. Now i keep everything on SD card and SD Cards backup in PC.
Now im trying to get the phone rooted with Magisk but the damn thing is not working.
This underscores the importance of regular (i had weekly TWRP) backups. I had backups of all partitions except internal data like pictures etc. Lesson learned i guess.
Hey RaXelliX thanks for lending a hand! Unfortunately I'm using a Mac Pro and Frija is a Windows exclusive *tears*
it seems that my next best alternative is to use Samloader instead of Frija, and JOdin3 instead of Odin. After some research ive realized that I am way out of my depth , but shall continue nonetheless. I'm gonna try your method with these alternatives and hope for the best, that sounds good in theory I was just curious to the thoughts of others more experienced.
And Oske829 your definitely not alone, stay strong and best of luck
Thanks!
There was a new firmware on Sammobile that I just tried flashing, didn't fix the problem, still bootlooping. I am officially out of ideas on how to fix this. I think there's something funky at the hardware/software level that's throwing a fit about having to run android 11 that's causing this, but I have no clue what it could be or how to resolve it. Not sure if there's anything i can do at this point to save my data.
Oske829 said:
There was a new firmware on Sammobile that I just tried flashing, didn't fix the problem, still bootlooping. I am officially out of ideas on how to fix this. I think there's something funky at the hardware/software level that's throwing a fit about having to run android 11 that's causing this, but I have no clue what it could be or how to resolve it. Not sure if there's anything i can do at this point to save my data.
Click to expand...
Click to collapse
You could try flashing a custom recovery (i suggest TWRP: https://eu.dl.twrp.me/beyond0lte/ S10e Exynos version) and the once in recovery connect USB cable to move the data off. If you succeed then you could wipe the phone and get out of bootloop.
When flashing recovery via Odin use the AP field and select the twrp-3.5.0_9-4-beyond0lte.img.tar file and make sure NAND Erase and Re-Partition are OFF. Auto-Reboot could be on or off.
This would touch only the recovery partition and will not wipe data unless you do it yourself inside TWRP.
There are a few caveats with this. The phone may complain about missing VBMETA header. If that's the case i will share a modified TAR file that includes that and TWRP itself. Or the phone could fail flashing custom recovery due to Vaultkeeper that prevents flashing unofficial binaries. This usually happens a day or two after flashing firmware. After that Vaultkeeper disengages.
Obviously your bootloader should be unlocked. You can do that by pressing Bixby+Vol Down before connecting the cable (with phone off) and then long press Vol Up to enter bootloader unlock mode. Bootloader can later be relocked again.
RaXelliX said:
You could try flashing a custom recovery (i suggest TWRP: https://eu.dl.twrp.me/beyond0lte/ S10e Exynos version) and the once in recovery connect USB cable to move the data off. If you succeed then you could wipe the phone and get out of bootloop.
When flashing recovery via Odin use the AP field and select the twrp-3.5.0_9-4-beyond0lte.img.tar file and make sure NAND Erase and Re-Partition are OFF. Auto-Reboot could be on or off.
This would touch only the recovery partition and will not wipe data unless you do it yourself inside TWRP.
There are a few caveats with this. The phone may complain about missing VBMETA header. If that's the case i will share a modified TAR file that includes that and TWRP itself. Or the phone could fail flashing custom recovery due to Vaultkeeper that prevents flashing unofficial binaries. This usually happens a day or two after flashing firmware. After that Vaultkeeper disengages.
Obviously your bootloader should be unlocked. You can do that by pressing Bixby+Vol Down before connecting the cable (with phone off) and then long press Vol Up to enter bootloader unlock mode. Bootloader can later be relocked again.
Click to expand...
Click to collapse
Is this exclusively for exynos phones or can I run twrp on a qualcomm device?
nevermind i found the snapdragon version of twrp
I'm trying to unlock the bootloader the way you described but that doesn't seem to be doing anything, and any guides I'm seeing on how to unlock it all involve doing something that resets the phone which isn't what I'm going for.
Oske829 said:
I'm trying to unlock the bootloader the way you described but that doesn't seem to be doing anything, and any guides I'm seeing on how to unlock it all involve doing something that resets the phone which isn't what I'm going for.
Click to expand...
Click to collapse
You might be out of luck as Snapdragon versions do not allow bootloader unlocks. At least as far as i know. I wrongly assumed you had Exynos version. If the data is important the last resort might be to contact some data recovery company. Im sure they have tools to access the internal memory even if the phone bootloops or flat out refuses to boot.
Flash 4 file firmware
Use Home_csc
If you want keep your data
Hucin44 said:
Flash 4 file firmware
Use Home_csc
If you want keep your data
Click to expand...
Click to collapse
I believe he already tried that and the phone is still bootlooping. Im betting that whatever causes the bootloop is in the data, the data he needs to access.
A bad situation all around because if he wipes the data it will likely fix the bootloop but he will lose the data. If he keeps the data the phone will keep bootlooping and he wont be able to access it. Although i would argue that the data you cant access is effectively lost anyway and that the proper functioning of the phone is more important.
I've heard that theres tools you can use to recover deleted data after resets and stuff since data doesnt get wiped when its deleted its just marked as stuff that can be written over. So I would think there would be a way for me to reset my phone to get it working and then recover the data with one of those programs, but the problem is from what I've heard you need a rooted device to do any of that and since I can't unlock my bootloader I don't think that can happen.
The one last thing I'm going to try before I seek out help from data recovery people is to try pushing the smartswitch apk onto the phone with adb and then hoping I have enough uptime to install it before the phone reboots cause I've heard you can use smartswitch in download mode to backup data, but I haven't found any guides anywhere about how this is done so I don't know if its actually doable.
Oske829 said:
I've heard that theres tools you can use to recover deleted data after resets and stuff since data doesnt get wiped when its deleted its just marked as stuff that can be written over. So I would think there would be a way for me to reset my phone to get it working and then recover the data with one of those programs, but the problem is from what I've heard you need a rooted device to do any of that and since I can't unlock my bootloader I don't think that can happen.
The one last thing I'm going to try before I seek out help from data recovery people is to try pushing the smartswitch apk onto the phone with adb and then hoping I have enough uptime to install it before the phone reboots cause I've heard you can use smartswitch in download mode to backup data, but I haven't found any guides anywhere about how this is done so I don't know if its actually doable.
Click to expand...
Click to collapse
Well I find myself here after 48 hours of s10e hell, with an almost identical issue. After a couple attempts and a trip to our local cell phone repair place, we ended up doing a factory reset, with the same hopes -- that the files were still there but the space marked as "free" and a 3rd party data recovery program could bring them back from the dead.
But they all require your phone to be rooted first - and this being my first venture into phone rooting I'm not really sure which route to go, or if it'll even be worth the effort. Does rooting the phone mean flashing it with a new OS, or simply unlocking superuser access so the recovery software can do its bit? (bear in mind, a lot of these products try to root the phones themselves, but none of them seem to work - I've tried about 4 different products thus far).
I'm convinced that if I can root this phone, the recovery software WILL find those lost sectors and recover the lost data, even after a factory reset -- there's plenty of youtube videos out there that say you can do this, but the rooting bit is what's got me tied up in knots!
huh.. jeah, latest update bricked my s10e too.
but my case, when power on phone, nothing happens, just black.. when conect cable to pc , then i can enter recovery and download mode..
till now nothing helped..
oem locked, frp locked, cant flash custom binaries!
hope next update will fix this madnes..
or need to find same firmware as update.zip what we can flash using stock recovery option (sadly saamsung dont give any update.zip files, i gues its money thing)
so, odin dont help, chimera tools dont help, and enginering combination file give some approval error to flash factory binaries!
houdini987 said:
I'm convinced that if I can root this phone, the recovery software WILL find those lost sectors and recover the lost data, even after a factory reset -- there's plenty of youtube videos out there that say you can do this, but the rooting bit is what's got me tied up in knots!
Click to expand...
Click to collapse
well ,as far as i know, thease all recovery lost data works with HDD type disks, flash memory are out of luck..
because, i easy restored deleted data from my HDD, if it wasnt multiple times formated or writed full hdd , deleted, writed full etc.. but with SSD that software isnt working, due flash memory.. but, maybe im just to old, and there are new softs who can do that, just, i have not seen any jet!