Hello I really hope someone has a good solution for my problem (FIXED NOW - read whole post if interested), I have attempted quite a few supposed solutions that i found and always seem to run into the same problems, so I will try and explain as much as possible about my device and problem.
Firstly I have Samsung Galaxy SIII mini, I bought this from a carphone warehouse store in the UK under a o2 network contract but I believe it to not be network locked.
I then successfully rooted my phone with this image file ( https://mega.co.nz/#!qIsiEZIZ!L7rPSSTJ89-N3WrKs-i5vjYoW0lCIXMnkC5fGcnCg3o ) the other day using odin and by following this thread - http://forum.xda-developers.com/showthread.php?t=2030282
Everything worked PERFECTLY and was extremely happy with the results I had now acquired super user control allowing me to use apps that require this privilege apps such as LCD Density changer (should be renamed "Samsung Bricker")
I stupidly used a LCD Density changer app, which i believe changed the density from 240 to 190.
Since this change the phone would not get past the very first load screen, meaning not the animated samsung logo but the simple galaxy s3 mini splash that is shown before. It still charged and I could still get to recovery mode, I dont think safe mode worked though. I could also still access it via adb on my PC.
So I followed a number of threads on how to use adb and shell to to edit the build.prop file to reset the density but even following numerous methods to make the /system folder and its contents rw (read writable) as opposed to ro (read only) and same goes for build.prop
I was never able to to push the build.prop file back into /system. Even when it seemed it had done it i would pull the build.prop file back again to check to see that there was no change whatsoever.
I also did not have anything like busybox installed to the best of my knowledge and seemed like a much more complex solution to any other thread.
I then wondered would the rom I previously installed contain the correct build.prop file in its system.img, I attempted to unpack these images to check but was unable to with numerous supposed tools available for windows ( I think ubuntu systems are the best for this ).
Just out of pure random stabbing in the dark I hit volume down + power + home once again. I suddenly saw the odin screen on my phone. "Hell to the Yeah" I thought to myself.
So I attempted to follow the thread (mentioned earlier) for the custom the rom using odin again (this was like the 3rd time i had tried to get the odin screen back, as you some times find the connection to the PC and phone to be very unstable at times, so due to this I had just assumed this wasn't going to work)
Now I see the odin screen perhaps, just perhaps the rom does include the build.prop file. So I started the process again and now even though I have wiped all my data as part of my trials to get the phone working again I now no longer have a brick rather than a phone! This process actually took place whilst I was in the middle or writing this post as I was at my wits end and desperately seeking help.
So I am posting this anyway with the hope it may at some point help some other unfortunate soul! MY PHONE NOW WORKS AGAIN! a few hours of my life gone but hopefully it'll save someone else these hours!
(word to the wise dont screw with the LCD Density unless you have a confirmed list of working density's)
Thanks for reading!
Best Wishes Rhys
This sounds great but it's for a different device. You posted in the Verizon Galaxy SIII section (SCH-I535). I'll get a mod to move this for you.
Sent from my SCH-I535 using Tapatalk 4 Beta
SlimSnoopOS said:
This sounds great but it's for a different device. You posted in the Verizon Galaxy SIII section (SCH-I535). I'll get a mod to move this for you.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yeah sorry about that, I did search for a S3 mini forum just had trouble finding it! Thanks to Naddict + SlimSnoopOS for moving to correct thread! :highfive:
Good news.
Related
**Resolved.
Hey all,
This could be a quick answer or hopefully something more. First off, I appreciate you reading this - and all XDA does. It's really nice to see development for the Android system.. so thanks for sure.
Deal is, is that I have a Galaxy Tab with build something like gjj7 - I didnt write it down before the flash.. ugh. Anyway, the post i was reading was installing Clockwork Mod, and recommended the forum below (on XDA)
http://forum.xda-developers.com/showthread.php?t=788108
I used the CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.15.3 because the thread talked about using the JPy file if your ‘Build Number’ wasnt listed.
Odin3 looked great - no errors, all green. Tab did not reboot itself though, just hung. I rebooted, and now it doesn't look to start. If i keep hammering away though, it will show the Galaxy Tab intro screen, but then stop again.
I've seen the battery logo come up a few times too - looked grey - though it was a full charge before the flash.
I did check a Google search and went through all the posts I could on XDA, but just didn't see what I'm looking for. Is it indeed bricked, or because it 'kinda works sometimes not really" is it gonna be ok?
THanks for any replies,
** Edit - I put it in the box to put it away for a while - and when I opened it - the Tab turned on with the Android dude holding a sign. Anyone know why thiswould have turned on after being in the box for a while? I have not tested to see if the computer recognized it - but would like to know if you have a stock Galaxy Tab firmware i can reload.
Hey thanks again for any help -
-Kenny
Hi, I'm no expert, but what I think you may have done is load a kernel only, and you'll need to load a ROM on top in order to get the Tab working again.
I say that because I loaded a .tar file onto my Tab and it hung on the Samsung Galaxy Tab screen. Only when I loaded the JJ4 'full flash' (as I saw it referred to) was I successful in getting my Tab back online. The JJ4 has three .tar files included, one for each slot (Modem, PDA, and CSC).
It's pure guesswork on my part, I am still very new at this, but that might be your issue.
In your shoes I would look for threads about combining kernels and ROMs...?
Hope this helps. And I hope someone will correct me if I'm completely off-track.
k3nnynapalm said:
** Edit - I put it in the box to put it away for a while - and when I opened it - the Tab turned on with the Android dude holding a sign. Anyone know why thiswould have turned on after being in the box for a while? I have not tested to see if the computer recognized it - but would like to know if you have a stock Galaxy Tab firmware i can reload.
Hey thanks again for any help -
-Kenny
Click to expand...
Click to collapse
I'm no expert and havn't done any ROMs for my Tab yet, but I am planning to and thus am reading heavily on the subject.
If I'm not mistaken, the "Android dude holding a sign" is an icon for download mode. This means, you havn't done any ROMs yet, just the kernel part. (Same as above reply)
I suggest that you look at this post ---> http://forum.xda-developers.com/showthread.php?t=932082
It's the one I'm planning to follow. Alterbridge86 has done an excellent job on this post. It has a downloadable step-by-step instruction, as well as the necessary links to files you will need. I suggest you print the instructions so your PC can concentrate on the ROM part.
I hope this helps, and if it does, please click on the thanks below..
Treb71, and SelfP - thank you for the replies guys, I really appreciate that. I finally got a chance to sit down with it again, and recharged it.
I got it into that download mode (power and both volume buttons - seems different everywhere i look, but it worked) and have it being recognized as a Samsung USB Composite Device in device manager. Good to see it can still be found eh?
When you mention Kernal only, - that sounds familiar. What is the difference behind this and ROM? Just the ROM is more of the O/S it uses? Is there a benefit to loading a Kernal thats not the default one that I missed? :S
I'm going to load up those links - that puts me on a great start. I don't normally feel like a total n00b around technology (I'm sure most people on XDA know their stuff) but this experience has humbled me hah.
THanks for the replies!
Hot dog -
It worked.
Basically, reading the PDF he gives here -
http://forum.xda-developers.com/attachment.php?attachmentid=578831&d=1303832984
The first 7 pages talk about backing up, i didn't need to worry about that part and went straight to the Odin3 flash.
Here it hung for a bit. Didnt skip past the "setupconnection" after hitting start (after loading the files of course - as stated) but then i realized the dude holding the sign image I was looking at was not the same as the "Download Mode" sign. The one I was referring to was holding up a sign in the top right corner. Didn't think of 2 versions of it come to think of it.
Anyway, rebooting the tab, reloading the files in Odin, and making sure I was indeed in Download mode - went through.
It was in Netherlands though hahah. Upon boot up I just needed to change some Language settings.
We're good!
I'll continue on with the flash tomorrow (it's late here now) and let you know how the custom firmware is - I figure why not, it's all pretty smooth so far.
You've both been a help, if I could hit thanks a couple more times on your posts you know I would. Let me know if you decide to flash, and if you have any questions or thoughts based on my experiences, and I'll do what I can.
Thanks again XDA - bad ass thread you got going on here the more I learn about it.
-Kenny
Hi all experts,
Yesterday my GT started force closing ALL apps all of sudden. So I tried to reboot the GT and it was stuck at the SAMSUNG logo screen.
When it finally boot(occassionally) to home screen, icons and widgets ALL GONE back to default, apps still force close. Showed setup screens (put in sim...etc). Lookout app shows installed on Market but cannot run. Some apps previously installed showed "free" in Market seems like never installed. Popouts showing force close still.
Open Recovery it shows (see picture). Anyone please HELP!
Well your tab is screwed up lol (for a reason I dunno due to lack of details). Flashing a stock firmware should fix it right away. Charge your tab to the 100%. Go to overcome website and follow the instructions (READ THE GUIDE, then REREAD IT AGAIN) to flash a stock ROM of your choice (or you can flash our stock safe v5 as well. The choice is up to you) once you are done you will be on a pure unrooted stock rom. Feel free to stay on stock or flash w/e custom ROM you desire
I think my GT has always been on stock Rom. I z4rooted it at 2.2 after awhile had all kinds of problems. Then I updated it to gingerbread thru. Kies and it went fine for 2 weeks.
Do you know how to find out which original Rom it is supposed to be with? (I bought it second hand, unbranded international GT-P1000, when I got it it had TGY rom) Let me know what info/detail you need I will post them...
BTW, 1 out of 5/6 times I went to Recovey, it showed something like 'checksum (0)' 'no need to check' but still shows the 'cant access to system/csc/TGY/system' (see picture) When boot it still stucked at logo screen...
anyone expert can help?
DarkPal said:
Flashing a stock firmware should fix it right away. Charge your tab to the 100%. Go to overcome website and follow the instructions (READ THE GUIDE, then REREAD IT AGAIN) to flash a stock ROM of your choice (or you can flash our stock safe v5 as well. The choice is up to you) once you are done you will be on a pure unrooted stock rom. Feel free to stay on stock or flash w/e custom ROM you desire
Click to expand...
Click to collapse
Your question has been answered... We can't help people who DON'T read their responses...
Yeesh....
I did read the responses and brought TAB to local cellphone repair store with Darkpal's solution. I tried 3 of them and none of them were able to solve the problem having tried to flash different roms, and none of them were confident about finding the "original stock rom".
I was suspecting hardware issues, because this TAB I have was second handed therefore I have little idea what "stock rom" it was with, and the larger than usual gap between case and screen on SIM/sd side of the TAB suggested it had been opened.
All in all, I sent my TAB to Connexion2005 who said will JTAG my TAB. Let's wait to hear from him and I will post the result here.
hhc said:
I did read the responses and brought TAB to local cellphone repair store with Darkpal's solution. I tried 3 of them and none of them were able to solve the problem having tried to flash different roms, and none of them were confident about finding the "original stock rom".
I was suspecting hardware issues, because this TAB I have was second handed therefore I have little idea what "stock rom" it was with, and the larger than usual gap between case and screen on SIM/sd side of the TAB suggested it had been opened.
All in all, I sent my TAB to Connexion2005 who said will JTAG my TAB. Let's wait to hear from him and I will post the result here.
Click to expand...
Click to collapse
I am here to report the outcome as promised. Sent the Tab to Connexion2005 for JTAG and got it back after 1 week. It has been over a month and everything works fine. I have to give Connexion2005 the credit to revive my $400 investment. THANK YOU!
Also thanks to all attempted to help in this post. Thread closed!
I have tried installing EA24 stock (http://forum.xda-developers.com/showthread.php?t=1133053) but still Freeze when booting. The error message shown on the picture. I am clueless and need your help.
gtabspring said:
I have tried installing EA24 stock (http://forum.xda-developers.com/showthread.php?t=1133053) but still Freeze when booting. The error message shown on the picture. I am clueless and need your help.
Click to expand...
Click to collapse
I had a more complicated version of this. couldn't format, couldn't mount, nothing. My tab showed this, I tried flashing several different kernels/roms/cwm, everything, nothing. Actually made it worse. It got to a point where when I powered on, I only got the backlit softkeys. A few times I got a weird image I've never seen before. Something about bad or unknown upload mode (with a little droid in teh corner....should have taken a picture). And finally I would get nothing; HOWEVER, if I plugged my tab into my laptop and gave it a few seconds, ODIN would see it. I could try flashing a kernel, but it would never process, just hang at the first step so....
with the tab plugged into the laptop and ODIN showing a connection, I would hold VOL DOWN + POWER until I see it disconnect (this is evident of a power down since I have no lights to indicate that). Once it disconnects (yellow box disappears) you can let go of POWER but do NOT release VOL DOWN. It will reconnect shortly thereafter. You are now in Download mode (whether or not you actually see anything on the tablet. You can test this theory by flashing something. What fixed it for me? I downloaded firmware from samfirmware.com. Specifically I downloaded JJ7 v2.2 (full file name I used was P1000XWJJ7.rar) I think what made the difference was using all 3 files. I did not use a PIT file, I put P1000XWJJ7-REV03-ALL-CL669843.tar.md5 in the PDA box, MODEM_P1000XXJK5_REV_00_CL690077.tar.md5 for Phone, and GT-P1000-CSC-MULTI-OXXJK2.tar.md5 in CSC. I did NOT check repartition. Now, this was after I had tried several things like flashing PIT by itself, different stock kernels, full ROMs, etc.... This was the final step I took. Now I'm back to normal.
I'd be interested to see if this solves anyone else's problem. I am so thrilled that I just fixed my "bricked" tab (no power, no response, no apparent charging even) that I'm hoping my time and effort can help someone else.
Let us know what happens. I am actually scouring the forums now because I know at least 2 others were having similar problems as I and maybe this will help them as well.
BTW, I did lose EVERYTHING on the internal SD, including all my backups. Thankfully I always made backups to External
P.S. I should mention it is an AT&T (GSM) Tab.
swedishcancerboi said:
I had a more complicated version of this. couldn't format, couldn't mount, nothing. My tab showed this, I tried flashing several different kernels/roms/cwm, everything, nothing. Actually made it worse. It got to a point where when I powered on, I only got the backlit softkeys. A few times I got a weird image I've never seen before. Something about bad or unknown upload mode (with a little droid in teh corner....should have taken a picture). And finally I would get nothing; HOWEVER, if I plugged my tab into my laptop and gave it a few seconds, ODIN would see it. I could try flashing a kernel, but it would never process, just hang at the first step so....
with the tab plugged into the laptop and ODIN showing a connection, I would hold VOL DOWN + POWER until I see it disconnect (this is evident of a power down since I have no lights to indicate that). Once it disconnects (yellow box disappears) you can let go of POWER but do NOT release VOL DOWN. It will reconnect shortly thereafter. You are now in Download mode (whether or not you actually see anything on the tablet. You can test this theory by flashing something. What fixed it for me? I downloaded firmware from samfirmware.com. Specifically I downloaded JJ7 v2.2 (full file name I used was P1000XWJJ7.rar) I think what made the difference was using all 3 files. I did not use a PIT file, I put P1000XWJJ7-REV03-ALL-CL669843.tar.md5 in the PDA box, MODEM_P1000XXJK5_REV_00_CL690077.tar.md5 for Phone, and GT-P1000-CSC-MULTI-OXXJK2.tar.md5 in CSC. I did NOT check repartition. Now, this was after I had tried several things like flashing PIT by itself, different stock kernels, full ROMs, etc.... This was the final step I took. Now I'm back to normal.
I'd be interested to see if this solves anyone else's problem. I am so thrilled that I just fixed my "bricked" tab (no power, no response, no apparent charging even) that I'm hoping my time and effort can help someone else.
Let us know what happens. I am actually scouring the forums now because I know at least 2 others were having similar problems as I and maybe this will help them as well.
BTW, I did lose EVERYTHING on the internal SD, including all my backups. Thankfully I always made backups to External
P.S. I should mention it is an AT&T (GSM) Tab.
Click to expand...
Click to collapse
Thanks for the suggestion. I think your version of galaxy tab is different with mine and I am not sure that it will work. I am really desparate for solution. This disaster started when the tab's battery is low and suddenly off and when it's charged and turned on it bricked
Point being, tabs are tabs. You will need to use the same procedure, but a different ROM that is designed for your tablet. Go there and find a ROM. There is a thread about unbricking your tablet, I think in the Android Development section that should have a link to samfirmware.com and may provide you with a ROM version that should work. something that may help: plug your tab into the charger at least overnight. I used the stock charger and cable and charged it for 12 hours or so. I did not get any indication that it was charging since the screen and softkeys would not respond, but it did charge.
Of course, I look back and I think you have an indicator, but still a good idea. Try it anyway. Can't make it worse, eh? Mine seemed hardbricked, but it wasn't. I was real close to taking it apart before I found something that works. I believe, IMO, what really fixed it is flashing ROM (PDA), Modem, and CSC files all at once. It could have been something else, but that was the last thing I did before it finally booted.
Go to samfirmware.com, create a free account, and sign in. Then go here (I think your tab is a P1010, correct?) http://www.samfirmware.com/WEBPROTECT-p1010.htm
and Download this:
1010XWKC1 ## MULTI - CSC - OXXKC1 P1WIFI 2.2.1 2011 March DOWNLOAD
(click on DOWNLOAD)
Unzip that file you just downloaded
Start ODIN
Hold VOL DOWN and plug in tab to computer
I believe 3 files should be in the .rar (you can use 7-zip to open, Google it)
the MODEM file goes in Phone.
the CSC file goes in, you guessed it, CSC
last one is PDA.
I think I just rewrote instructions that can be found in the Galaxy Tab Bible. lol. This is what I would do. It worked for me.
Password for P1000XWJJ7.rar
Gentlemen,
I've downloaded both P1000XWJJ7.rar and P1010XWKC1_OXXKC1 to fix my bricked tab, but both require a password to extract the archives. Does anyone know the password? Has anyone had the same issue? I doubt it, otherwise i think it would have been addressed. Any help is appreciated.
I'm having the same problem were you able to fix it?
jairo_pena said:
Gentlemen,
I've downloaded both P1000XWJJ7.rar and P1010XWKC1_OXXKC1 to fix my bricked tab, but both require a password to extract the archives. Does anyone know the password? Has anyone had the same issue? I doubt it, otherwise i think it would have been addressed. Any help is appreciated.
Click to expand...
Click to collapse
try sampro.pl
see if that works.
I too require the passwords to be able to extract these files if someone would be so kind.
Copied straight from SamFirmware.com. It is right at the top of the download page.
try both of these... seems it could be either one of them
## Password is samfirmware.com
# Password is samsung-firmwares.com
Click to expand...
Click to collapse
where can i get these files for the sprint version of the tab i believe the model is p100 I don't see it listed on the recommended website
oxbeast1210 said:
where can i get these files for the sprint version of the tab i believe the model is p100 I don't see it listed on the recommended website
Click to expand...
Click to collapse
do a quick search of the dev thread for EA24 and you should be able to find the original SPH-P100 files. then you can find the EB28 and EF17 updates as well to get all the way to the official GB release.
tried the suggested file still get the error that the OP got in the first screen
oxbeast1210 said:
tried the suggested file still get the error that the OP got in the first screen
Click to expand...
Click to collapse
ok, no one likes a bricked device so let's see what we can do to help you. tell us where you are with your problem. by that i mean what model do you have, what rom were you running, what did you do or try to do that bricked your phone. i'll keep an eye on this thread looking for your response and we'll go from there.
I have the sprint p100 model room was stock rooted gingerbread.
I mailed the Tab to my brother when he got it tab battery was
completely dead and after he charged it and turned it on
he had that error
---------- Post added at 01:30 AM ---------- Previous post was at 01:29 AM ----------
thank you very much for helping me!!
can anyone help?
I have the T-Mobile version of this, but here's a guide and download files to recover your stock ROM. You can follow the entire guide if you want the Overcome ROM as well:
Guide:
http://www.teamovercome.net/p1000/?page_id=17
Downloads:
http://www.teamovercome.net/p1000/?page_id=21
Good luck!
NOTE:
Sprint modem is not listed, but you can fix that later. If you can get it to work with this guide & using the last modem file, we can go from there.
gtabspring said:
I have tried installing EA24 stock (http://forum.xda-developers.com/showthread.php?t=1133053) but still Freeze when booting. The error message shown on the picture. I am clueless and need your help.
Click to expand...
Click to collapse
try the one on teamovercome . net I have soft bricked mine but it worked after i followed their instructions there..
Has anyone EVER confirmed that overcome work for non GSM tab, for unbricking and CwM functions?
Sent from my GT-P1000 using XDA
Hey there guys, I have myself a galaxy mini, I wanted to put a fresh Rom onto it and so I did a little research. First I had to root it, afrter a few failed attempts of my phone being unable to find or unpack I changed the name of the file to Update.zip. Boom root succesful, Thinks he can program hah. Next step was install clockworkmod, not so simple for me as Im running a mac 10.5 and the copy of odin I got dosent seem to connect to my phone, so I tried change the name, no joy, then I got a different recovery, still no joy, the phone would think it was installing but it was a dead end.
The fool I am, It looked to good to be true and it was, Rom Manager shut me down, if I push all the buttons kies will attempt to connect but my screen is still black. I went to town to get a jig but couldnt find one so I made one but I still cant boot to download.
So now I have a few questions,
1) Is mac term the same as terminal? Terminal got lost somewhere along the way
2) Do I need specific files on micro sd when attempting the jig?
3)Are the points to far on my homemade jig? Lead about 7 inches
4) Is there a specific mac program that can flash the phone?
Any tips or ideas would be greatly apprieceted. Thanks
Nope! Nothing!!!... There's nothing u can do now except giving it 2 care center.
Sent Via XDA™ Premium
Ah well first attempt and at least it can be saved. Thanks for the reply
Don't ever, ever use ROM Manager with (low end) Galaxy devices; it kills them instantly.
Sent from my Nexus 4 using xda app-developers app
Hah im jealous now as ill have to wait for repair Im scared of Rom Manager now, Is there anything like it for the likes of galaxy mini?
So I have done a ton of research on the subject since last night when I made the mistake of editing my build.prop file in the system directory to try and get Milk Music installed and working on my N6.
steps I took pre soft brick
made a copy of build.prop and placed it in my nexus 6 home directory
then went in to edit the file in the system folder
Changed the following
ro.product.model=Galaxy S4 (from Nexus 6)
ro.product.brand=Samsung (from Motorola)
ro.product.manufacturer=Samsung (from Motorola)
Saved the changes using ES file explorer with root access of course and went on to DL the milk music app from http://forum.xda-developers.com/showthread.php?t=2676662 which is the tutorial page to get this all working.
dl'ed the app got it open and got an error saying milk music is only supported on samsung devices so I didnt think much of it and went to copy the backup build.prop over to replace the faulty edited one currently in the system folder. did this, or so I thought and rebooted.
now I am welcomed with just the Google while letters and the unlock symbol at the bottom of the screen and it will not move on.
I can boot into stock recovery but I only have the stock.
I do have adb installed and it worked to unlock N6 bootloader but haven't used it since and I am currently out of the house till prob a little later in the day.
steps I have taken to attempt the (known fixes) have all been shot down by the fact that I can't get ADB working from my friends computer and I am not sure if it is the phone or lack of drivers (which does not seem to be the case) or me just being very noob when it comes to adk and android sdk anything. I have only used it once and that was about a week ago to unlock bootloader.
I wont be able to check this forum till I get home a little later but will update on the situation when I get there and can try to connect phone to my PC where everything has already worked before.
thank you all in advance for all the help
I got home to test some things and I have ADB access and have tested fastboot.
I tried a fresh flash with the guide located here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
had to do the long way like everyone else in comments was describing. everything went smooth no hiccups but still stuck on black screen with Google in white letters with the white unlock at bottom.
any input would be highly appreciated.
Just did the exact same thing I did in second post and went for yet another fresh flash and IT WORKED. got the spinning dots and after a bit ANDROID popped up and the initial welcome screen popped up.
Thank you guys so much for all your help. not sarcastic at all i promise. the guys who lead me to this fix are in so many different forums and threads and have no idea i was piecing it all together to get to this outcome, so to all of them and all of you who participate here on XDA thank you so very much.
I flashed one of the first ver of Android N. It was OK but I could not updated it go back or do anything. It also took root away and unlike M there were no setting to turn it on and I could not get it back. I tried every cmd and attempted to flash forward and back and root again. I finally got pissed and software bricked it. Again I tried everything I could find but when I ran NRT_v2.1.5.sfx.exe to my surprise on the first try it fixed it and I am at 6.01. <