I recently flashed my A51 using Odin latest version because it wouldnt move past the logo the other day when i turned it on. At first I got the circle with the bolt si9gn indicating it was or needed charging and when i pulled the charging cable away it filled the outer circle with green inidicating it was at 97%. The unit turns on but gets stuck at the logo from that point forward. I tried going into recovery mode and wiping the cache and resetting to factory with no results. from the guide here, I went to the website recommended and downloaded the appropriate firmware, using odin latest ver. I had no problems with it and it inidcated passing. Is there anything beyond that? I havent read anywhere that there was a solution , ive only seen a comment about someone saying the motherboard was probably bad. That sounded like a "best guess" to me and I wanted to know if anyone knows for sure or can suggest something for me to do. I really wanted this phone to work. Thanks and sorry if I missed any threads on here or this is posted in wrong section.
Related
ok I tried to sbf back to 2.2.......everything looked normal but at the end of the flash the phone tried to boot several times and then said reboot phone manually. The only way I knew to do that was to pull the battery which I did. I booted back to the rsd lite and then the program said complete and success.
The problem with that was the phone was in bootloop. I unplugged the phone from the computer and did another battery pull and went into android recovery. It goes to fastboot and I choose android recovery. Instead it goes to a screen of the little android with an exclamation. I have tried this over and over with the same results...... I plugged into the wall charger and tried to get it to boot from there but it goes to the battery charge sign instead of bootstrap recovery. I tried the several times also with and without the battery to no avail.
So now I have run out of things to try and I see no other info on the forums that is different than what I have done. Can someone please help me or have I ruined this phone?
the sbf file I flashed was named VRZ_MB870_DTN-14.8_1FF_01.sbf.
Which phone?
whew!!!! I figured it out and just thought I would post the solution here in case someone else runs into it.
When the x2 goes into the green android with the exclamation mark you press the up and down volume button at the same time and this will carry you to an android recovery screen I had never seen before. Then do a data wipe and cache clear hit reboot and it will come right up. I got this from the internet somewhere although it was not not clear as to whether it would work in this situation but it did and I am sooooooo glad!!!!!!!
I think I am 5 years older now.....bummer
the_scotsman said:
Which phone?
Click to expand...
Click to collapse
Droid x2.....I think the thread got moved
Please use the Q&A Forum for questions Thanks
Moving to Q&A
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!
Just for reference I have a p5113 model.
A while back I put Cyanogen on my tablet. A few months ago I cracked the screen, only a bit on the corner, of course I can't stand cracked screens so I ordered a replacement. When I installed the screen everything connected fine and dandy so I tried to start it up, but when I did the touch function didn't work. I thought maybe it was just a bad screen that I had ordered, so I got another. When I got the second screen in I replaced it, but this time it was doing the same thing as before where the touch wasn't working! I made sure everything was connected okay and also checked for anything damaged, but everything seemed fine. For some reason I thought maybe hard resetting it would help, but it didn't. At this point I was just trying to get the stock 4.2.2 firmware back on it. I downloaded the firmware, used ODIN to get it onto the tablet. When it restarted after the firmware was loaded on, it was stuck in a bootloop. I heard that it may just need to be factory reset again so I tried to get into recovery mode, but only goes into ODIN/Download mode, which is what my final problem is here.
TL;DR Tablet will not go into recovery mode. Only ODIN/download mode.
I haven't been able to find ANYONE else that has had this problem before. So if anyone knows the source of my problem, I would be very appreciative of your help.
Well you could have fried the capacitive touch circuit with a static charge I have no idea what your skill level is also you could have a bad image or you could have bonked the hardware and it doesn't detect critical boot hardware I'm not that well versed in firmware related boot issues but hopefully some helpful nerd can give you a hand you could also just try again aster you download a new IMG
Sent from my toaster
Samwise13 said:
Just for reference I have a p5113 model.
A while back I put Cyanogen on my tablet. A few months ago I cracked the screen, only a bit on the corner, of course I can't stand cracked screens so I ordered a replacement. When I installed the screen everything connected fine and dandy so I tried to start it up, but when I did the touch function didn't work. I thought maybe it was just a bad screen that I had ordered, so I got another. When I got the second screen in I replaced it, but this time it was doing the same thing as before where the touch wasn't working! I made sure everything was connected okay and also checked for anything damaged, but everything seemed fine. For some reason I thought maybe hard resetting it would help, but it didn't. At this point I was just trying to get the stock 4.2.2 firmware back on it. I downloaded the firmware, used ODIN to get it onto the tablet. When it restarted after the firmware was loaded on, it was stuck in a bootloop. I heard that it may just need to be factory reset again so I tried to get into recovery mode, but only goes into ODIN/Download mode, which is what my final problem is here.
TL;DR Tablet will not go into recovery mode. Only ODIN/download mode.
I haven't been able to find ANYONE else that has had this problem before. So if anyone knows the source of my problem, I would be very appreciative of your help.
Click to expand...
Click to collapse
sounds like a damaged digitizer to me.
may as well get a new tablet as digitizers tend to cost almost the same as a new device...
now... recovery...
this may sound redundant but try flashing the firmware again. when it flashes make sure it says "recovery.img" or similar at some point in the Odin log.
be sure to use the correct pit file and the repartition check box when flashing.
there are usually two or more firmwares per tablet so if one fails to boot recovery try the other.
the site I find that has reliable files is samsung-updates.com but be prepared for slow downloads averaging am hour and a half.
Sent from my SGH-T999 using Tapatalk
Hi all..or anyone out there
I have had the seemingly strange bootloop problem on my stock note N8010...which stuck on the dreaded "samsung galaxy note 10.1" and only has odin feature working. (and no factory reset options because I think the poor old tab is crammed to bursting with apps, files and cache and so had a meltdown) poor thing.
so anyway I check these sites of techie wonder and wisdom and followed every logical option..starting with the simple ones
first ran power down and tried to boot up (x3) with no joy, then take apart the tablet to disconnect / reconnect the battery and boot up (x3) still no change.
So went and got the firmware from samwares (both jelly bean and kitkat) to then flash through odin....tried and failed first because of dodgy cable, but the then got a new one...and joy of joys (at first) odin recognised my tab and the firmware flashed across with pass..but then auto rebooted straight back into the dreaded samsung 10.1 again....so tried different versions of odins... and tried other global n8010 firmware...but funnily and frustratingly then all fully download and pass in odin (and the andoid logo and green download status bar on the tablet seems to shown that downloading is and has fully taken place.... but the darn thing still wont boot up past the samsung galaxy note 10.1
Sadly coming to the ends of my tether (of so many nearly there false hopes, high and lows) and very little cash to send it to the Sami tech bods doesnt help matter....I then read and tried the (supposed) last resort pit file/firmware option...first with kitkat (as apparently that worked for someone somewhere) and then tried with jelly bean..again each time itAlways passes in odin.... but auto reboots into the dreaded bootloop logo .... to haunt and torment me.. Aaaaagh!!!!.....I would not mind if it said action failed (for once) like some others seem to experiencet...but it always passes in ODIN????
So.....have come to the semi ignorant conclusion it is either the bootloader section of the tablet or the original software that is messed up or some internal hardware component has a fault.
but was wondering if there is anthing left to try...or would it potentially be possible or worth trying to root a tablet in this condition?
As although I have not ventured into the wild worlds of rooting.....I am now pretty confident of messing with this tablets mind..and have little to lose...so any further ideas and help would be great.
Exact same here. Never flashed, totally stock N8010. My wife hadn't used it for a couple of weeks. So she grabs it again and it was off. booted to nothing but the boot logo. Nothing worked except Download mode.
Flashing stock roms has Odin reporting success, but it still won't boot up. Trying re-Partition does give a fail as soon as I press start.
And we aren't alone. It appears there are quite a few of these cases. I have no idea how to solve this.
I have done a bit of rom flashing on my old galaxy S (the first one) and bootloaders and such usually were included in a ROM. Rooting was done with Recovery or an app and I think it was also possible with adb, IIRC (it's been a while).
It's my wife's Note and she's starting to scope out mini iPads...
Same problem with GT-N8010
I am also having the same problem.
I tried to upload a new ROM via ODIN. All was successful from the ODIN app (PASSED). but stuck on the boot screen. Power and Vol up does not work (it appears to but then crashes out to the boot screen again) so no way to do a hard factory reset.
Volume down/power does work and allows you to get to Odin mode. but as above, uploading a new ROM does not seem to work.
This is an un-rooted GT-N8010 with the stock ROM when I purchased it back in 2013 I believe.
Come on guys, give us some ideas.
Thanks
Gene
Sounds like wrong model firmware flashed as that's the usual bootloop problem .
Try Odin firmware flash wait to passed then remove battery for a short while and replace and try recovery mode .
In my case there is no incompatible firmware issue... The tablet just stopped working one morning and that was that.
Can't comment on the other posters though.
Sent from my GT-I9305 using XDA Free mobile app
Gene_uk said:
In my case there is no incompatible firmware issue... The tablet just stopped working one morning and that was that.
Can't comment on the other posters though.
Sent from my GT-I9305 using XDA Free mobile app
Click to expand...
Click to collapse
My wife's the same. Never done anything to it. No idea how to remove the battery. I let the battery run down once, then recharged it, made no difference.
That was before trying to flash the new firmware. My Note says N8010 on the back, it says so in the download mode. I got a firmware from SamMobile for the N8010. Don't know what else I can do.
Widdly said:
My wife's the same. Never done anything to it. No idea how to remove the battery. I let the battery run down once, then recharged it, made no difference.
That was before trying to flash the new firmware. My Note says N8010 on the back, it says so in the download mode. I got a firmware from SamMobile for the N8010. Don't know what else I can do.
Click to expand...
Click to collapse
Having same problem here ... tried flashing different firmwares along with PIT file - still no luck ..
stuck on samsung galaxy note screen .. cannot get recovery mode
Any help guys?
Tried 3 different versions of Odin, it always fails after boot.img ("complete write operation failed")
My phone model is G920I.
I'm stuck in the exclamation mark screen. Only thing I can do pressing buttons is reach the download screen. Can't access recovery.
Can I flash TWRP through odin and try installing a firmware stored in my ssd? Or that wouldn't even work seeing as I can't get pass the ! blue (green?) screen anyway?
Worst part is, I don't even know how this all started. I got a notification that a new update was released, but my battery was low, the phone died, I left ir charging and it wouldn't turn on the other day. I probably ****ed something up in the recovery screen (it was accessible in the beginning) and now I can only access the !/download screen.
Does anyone have any idea what I can do? Thanks in advance.
rifek4 said:
Charge you battery a bit anyway, to be sure there is minimum 30%. Then flash latest 7.0 firmware correctly for your model via Odin3 with latest drivers: https://forum.xda-developers.com/ga...official-stock-firmware-t3086387/post73935393 here you found all.
Click to expand...
Click to collapse
Made a new thread because my problem seems slightly different and I explain about it. Don't see how it could be prejudicial to the forum but thanks for the hint.
My phone is only on when connected with cable, either to the computer or charger, When I still had access to recovery mode, it said 99% battery. Now I don't even think I can check the battery? All I know is when the phone is not connected, it stays off.
I've tried using a couple of supposedly stock firmware from my model but the error is always the same. Gonna try downloading one from where you linked me to, but do you really thing it could make a difference, considering everything I've said?
Thanks in advance.