Helppp plzzz!!!! - Galaxy S I9000 General

I was unable to get root access for my Galaxy S for about 1 week, and today I finally could do it. Unfortunately, I rushed to try all of the apps I downloaded before that need root access, one of which was supposed to change the battery icon's (that in the upper tray) appearance. When I clicked on that, the mobile rebooted and kept giving again and again the (Samsung GT-I9000 Galaxy S) screen without proceeding to operation. What made it worse, as I think, is that because I was afraid and very concerned, I tried to do anything and so I entered into recovery mode and kept pressing on things I don't remember exactly but what I do is that I think I unmounted the SD. It's urgent; any1 plz try to help me as soon as possible.

Romino0 said:
I was unable to get root access for my Galaxy S for about 1 week, and today I finally could do it. Unfortunately, I rushed to try all of the apps I downloaded before that need root access, one of which was supposed to change the battery icon's (that in the upper tray) appearance. When I clicked on that, the mobile rebooted and kept giving again and again the (Samsung GT-I9000 Galaxy S) screen without proceeding to operation. What made it worse, as I think, is that because I was afraid and very concerned, I tried to do anything and so I entered into recovery mode and kept pressing on things I don't remember exactly but what I do is that I think I unmounted the SD. It's urgent; any1 plz try to help me as soon as possible.
Click to expand...
Click to collapse
Simply put the phone in download mode and flash the same firmware. The app you used probably caused the bootloop, likely because it wasn't made for your phone/firmware.
Next time, read and learn about it before you do it. And also, just some advice, before you do ANYTHING that will potentially cause your phone to bootloop or no longer work, ALWAYS ALWAYS ALWAYS do a nandroid backup (which can be done in recovery mode). That way, if it messes up your phone, you can simply restore the backup and be right back where you left off.
Good luck!

Thnx for ur concern and advices. I already did that the day after I posted; I discovered another thread on the forum and followed the instructions, and yeah sure I won't rush in these things again .

This kind of this happens all the time when we began in the flash world ajajaj
Don't worry this is the way everyone learns.

Related

[Q] Got me some boot loops after using a specific font with Type Fresh.

Alright, so last night I was fooling around with "Type Fresh," which you guys have probably heard of. It was released here... It's a font changer...
Anyway, things were going good until I tried a font named, "Joystix," which replaced quite a few of my fonts. That caused my phone to go into a crazy bootloop.
So, at this point, I do not have Clockwork Recovery. I actually have the Stock Recovery. For some strange reason, my stock recovery just takes me to a screen with a red triangle, and factory reset just shows this hard drive and a loading bar that never goes anywhere before rebooting my phone into a boot loop.
I've checked to see if ADB will work in my stock recovery, and it does, except for the fact that my phone is, "offline," which is probably not good.
Is there anyway I can get my phone to work again? I remember when I was getting bootloops and I somehow got the phone to reinstall all the correct stuff after going into the stock Volume Down+Power thing a few days ago. I don't know or remember how. Like, it was going into the whole process of giving me the choices and said, "Do you want to update?" I said yes and voila, everything is back to normal. Sadly, this isn't the case atm. :|
halp
wauterboi said:
I've checked to see if ADB will work in my stock recovery, and it does, except for the fact that my phone is, "offline," which is probably not good.
Is there anyway I can get my phone to work again? I remember when I was getting bootloops and I somehow got the phone to reinstall all the correct stuff after going into the stock Volume Down+Power thing a few days ago. I don't know or remember how. Like, it was going into the whole process of giving me the choices and said, "Do you want to update?" I said yes and voila, everything is back to normal. Sadly, this isn't the case atm. :|
halp
Click to expand...
Click to collapse
Well I've never personally used type fresh to change fonts, I've done it in other ways. Just a thought for ya, but I would recommend that if you can get adb to recognize your device (cmd: adb devices) try booting into hboot(volume down + power), and see if it recognizes it regularly that way, from there I recommend trying a program called Droid. It's a windows program that I used when I messed up re-rooting my replacement mt4g (tip: Don't try rooting when having been awake for 26 hours for no apparent reason ). It has a feature called Debug Console which fixed a bootloop, and constant force close that I somehow managed. I also suggest pulling your sdcard, getting a usb scard reader, and installing the stock recovery zip (Pdimg or something like that, I forget off hand).
That's all I can think of, hope it helps
...I finally looked at my SDCard via my brother's phone.
Every thing in my SD Card pretty much has "Font" in front of it in regards to the name.
I mean... Yahoo became FontsYahoo.
wat
Solved.
For those who were wondering, I found out that I had to rename the recovery file to the PBNASFASodhwhatever it was.

[Q] stuck at shut down screen after interrupting update

tl;dr: Interrupted update. cant do jack. tried acer tech support. failed
I grew bored with waiting the two minutes for my tablet to install the new update. so i stood up and hit the power button to put it to sleep like a boss. then i cam back later, the lock screen was unresponsive
i figured out be double tapping the pwr button i was able to unlock the tablet to see the powering down screen (see attachment). I can get to the setting menu, but evrytime i try to mess around in it, the window closes itself.
an interesting note is that the time is wrong, and the battery suddenly went from 100% to 15%
I called acer tech support, and with ther guidance...
pressed the reset button to no effect
powered on holding the pwr & vol- buttons down to get an error (see attachment). then the tablet turns off.
Ive dled some "update.zip" files i found online that are supposedly used to unbrick the tab... but i just got the same error picture(see attachment)
one other thing i tried was to hold the power and vol+ buttons. this cleared a chache, but had no other effect.
I am a noob at droid, but not to tech. i would like to avoid perma bricking, and im unsure about mailing this in. waiting is gay. I would like to restore it to factory settings w/o rooting it etc. as ive never done that before. but im not opposed to installing a CFW if it somes to that...
Im looking for ideas guys here guys. wtf is wrong with this thing?
Haha
Lmao "hit the power button to put it to sleep like a boss", funny ****.
Can't help you though sorry
ive been around he web, and have seen this exact series of symptoms happen to a handful of other guys... i haven figured out a solution yet, and it is looking more and more like ill be sending it in via warranty
my best guess at this point is i have corrupted a crucial system file. as to why i can do jack in the factorys recovery mode... idk. but then again, idk what the factorys recovery mode should look like or how it would function. youtube only shows CWR... which i dont have
if i believed i could anything reasonably withing my abilities, i would... but voiding the warranty on a long shot seems dumb.
still ANY ideas would be great
I too faced exactly the same problem today.. Dunno why this is happening... I am too worried now... Kindly post the solution as you find them...
Am sure calling tech-support is just waste of time..
Thanks in advance..
IM GOLDEN...
Ive reflashed to the original factory build. the problem was with the "update.zip" files i have been using. i guess they were corrupt.
multiupload<dot>com/WCT2FYLMQC
this is the file i used. I tried several from other guides, etc... a guy on another board told me to use this one. i put it on the root of my SD card, then held the power and vol- buttons until the loader had started. it took awhile, and it looked like it froze during the process...
DONT TOUCH IT
just let it do its thing, and it will reboot itself and run through the setup process like when it was new.
npena said:
IM GOLDEN...
Ive reflashed to the original factory build. the problem was with the "update.zip" files i have been using. i guess they were corrupt.
multiupload<dot>com/WCT2FYLMQC
this is the file i used. I tried several from other guides, etc... a guy on another board told me to use this one. i put it on the root of my SD card, then held the power and vol- buttons until the loader had started. it took awhile, and it looked like it froze during the process...
DONT TOUCH IT
just let it do its thing, and it will reboot itself and run through the setup process like when it was new.
Click to expand...
Click to collapse
How to put this file on the root folder when am not able to switchon the Tablet itself... and how reliable is this file??
stuck on same screen also!
My friend and i who both purchased this Acer Iconia tab are both having the same problem. We both received a message on the tablets to do the update. We both got stuck and have gone thru tech line and there is no remedy. She was able to return hers within the 15 day period; I on the other hand am a week over that so have to mail it to Acer for repair. I'm thinking this is more than a cooincidence and there is a problem more spread... Acer would neither verify or confirm....
buntzmehta said:
How to put this file on the root folder when am not able to switchon the Tablet itself... and how reliable is this file??
Click to expand...
Click to collapse
He said the root of his SDCARD. You can take out the sdcard and put it in a sd cardreader on a computer and copy the file to it then put it back in the tablet. The file worked for him so it might be worth trying. Just have patience while it is loading as some of these updates take a while to load and sometimes you may not see anything happening but it is. The more patches and roms you load on Android the more you'll learn to just leave it alone and let the updates finish. Its pretty rare for updates to be messed up. Its usually people getting anxious and clicking on stuff.
Good luck
Sent from my A501 using Tapatalk
still stuck on shutdown screen any updates?
Anyone had any luck with a fix? If not --sending it to Acer for warranty repair after the hurricane hits..Sure hope this isn't a wide spreasd Acer issue do to the new download. Wish I could just return the thing all together. Worked well while I had it a whole 3 weeks...... Thanks in advance for any information.
npena said:
IM GOLDEN...
Ive reflashed to the original factory build. the problem was with the "update.zip" files i have been using. i guess they were corrupt.
multiupload<dot>com/WCT2FYLMQC
this is the file i used. I tried several from other guides, etc... a guy on another board told me to use this one. i put it on the root of my SD card, then held the power and vol- buttons until the loader had started. it took awhile, and it looked like it froze during the process...
DONT TOUCH IT
just let it do its thing, and it will reboot itself and run through the setup process like when it was new.
Click to expand...
Click to collapse
Thanks a lot dear npena.. you are simply great.. i was very anxious initially to try your method as no other member here who face the same problem thanked or recommended your suggestion...
I tried it and it worked... I am really very thankful to you...
Cheers..
you are my hero indeed.. thank once again..
BuntZ
Friends, who face this problem you must try it... it just takes few mins b4 you can get your acer tab to work again beautifully without loosing any settings or installed apps... they remain intact...
Yay!
Glad you got it running again - had a similar problem when doing a ota update myself, was so worried I bricked the tab, went thru about 7 update.zip files until I found one that magically worked, letting me get back into the system and flash the correct rom for my region
hi! i have the same problem with my a500. I write a guide to solve this problem. Problem in firmware. here is the gude http://forum.xda-developers.com/showthread.php?t=1572622

[Q] Cant Seem to Root EL30. Need help!

Ill start this saying, yes, im a noob. I rarely post or visit unless i have problems.
But i do have experience rooting this specific phone before. But this time around its giving me a LOT of problems...
Ill start with:
Samsung Epic 4g (D700.0.5)
FM 2.3.6 (GB)
BB EL30
K 2.6.35.7
Now i will attempt to explain all the problems as well as what i have done to try to fix them and i will give as many links to the pages that i used for guidance as i can.
As i said, i have experience rooting this specific phone in the past. I ran a stock rooted ROM and everything was fine other then some glitches that i just learned to live with. But about 3 months ago i got a few more problems that have been driving me crazy so i desired to reroot.
When i power down the device, it will not turn back on just by pressing/holding the power button. Removing the battery, reinserting it, and holding the power also dose not work. I finally figured out that i have to remove the battery, replace the battery, then quickly (before the on-screen battery disappears) insert a charging cable thats connected to a power source. Then when the battery turns green (even with minimal power or full power) i can then power it on, but only when the on screen battery shows green. If i wait too long and it disappears it will not work and i have to start over from the beginning. (Removing Battery...) That was the 1st problem.
Soon after this happened (maybe 1-2 weeks) my phone started doing random shutdowns and not powering back on (i assume because it didnt have a power source connected). This would happen at anytime of the day or night, even when it was connected to a charger and actively charging. Yesterday i finally had the last of it and started researching this problem. I found that apparently some/all of the epics have this problem in time. From what i read the micro(or mini im not sure) USB port dosnt fit 100% snugly. So it causes heat. This heat causes corrosion and eventually leads to this problem. (I have never got this phone wet in the 1.5 years i have had it, i take very good care of my electronics.) Around the time this started my phone also would drain its self in about 2-3 hours, this was due to it constantly thinking i was plugging and unplugging it from a computer and requesting that i choose from the 3 options of mass storage.... Eventually the whole screen turning black with the android and the 3 buttons went away but the pop up on the notification bar continued, and as already said, it will drain the battery quickly.
NOW on to the rooting problems.
I dont remember what rom i was running originally, but following a few videos from QBKing77.
I odin'd back to EC05. This went fine no problems. (Useing odin 1.85)
I then tried to use the e4gtauto.zip file and running the "RUNFIRST.bat"
Used option A (install Root not EL13/newer)
Everything went though like it was suppose to. No errors or problems. Phone rebooted into recovery rather then to the lock screen.
Not remembering how to use recovery, i did some research, apparently the camera button is SUPPOSED to be the select button, but this did not work for me at all. After several manual reboots (pulling battery) this was the only thing i could get to (not even download mode to try to flash back to EC05 again). I did some research and found a post that said the "home" button on the front of the screen was his selector for some strange reason. This worked for me. I selected "reboot now" or something like that (the 1st option) and it rebooted into what i was thinking was a rooted rom, checked and there was no SU, or BusyBox (as said would happen in the e4gtauto).
I downloaded an su.zip and figured i would flash it with CWM (last time i installed CWM it was "purple" or 3.1.0.1)
Well it seems that my CWM is gone... i did the ever famous "3 finger salute" of Vol Down + Camera + Power and nothing except that i had to select "reboot phone" again from what i believe is stock recovery. Which booted me back into EC05.
By this time it was late at nite (2am or so) so i went to bed, over night apparently it updated and is now EL30. Thinking this was a good thing (and deff proving im not rooted) so today i tried rooting it as EL30.
Still do not have CWM seemingly.
Also would like to note, inorder for me to get to download mode, i have to take out my SD card, take out my battery, plug in the phone, and hold 1+power when the green power indicator comes on as stated above. This is the only way i can get into DownloadMode (if that helps at all)
If i could get any information on how to root from EL30 i would appreciate it greatly!!!
I will answer any questions as fast as possible, and i will provide as much information as you request when as soon as possible.
Thank you all in advance.
LATE:
Im not able to post links... so i cant give all the steps ive followed so far, I have attempted to take out all infomration already stated related to a link or video... Sorry.
I can do this for you remotely via teamviewer 7 google it and install it pm me the id and password and ill do it all for you
Oh and you used the epic touch one click root... not ours.. and el30 doesn't work on one click root.
Sent from my SPH-D700 using xda premium
As i was writing the above i thought of something. What if i do the same thing i have to do in order to get into download mode to boot into CWM.
No, this dosnt work, it brings me back into the what i believe is stock recovery. I decided to mess with the "install from sdcard" option. I tried the various .zips i have on there and they all fail a signature check.
YourLordAndMaster said:
As i was writing the above i thought of something. What if i do the same thing i have to do in order to get into download mode to boot into CWM.
No, this dosnt work, it brings me back into the what i believe is stock recovery. I decided to mess with the "install from sdcard" option. I tried the various .zips i have on there and they all fail a signature check.
Click to expand...
Click to collapse
You have the wrong recovery installed... you used the epic touch one click root... ... just go get teamviewer and ill fix it for you.
oh but now your on stock recovery because samsung has a script in the kernel to restore the stock recovery upon boot.
The rooting has been fixed.
I didnt install a CWM file apparently
and i also did a lot of bad things
Big thanks to "Big Goron" for the help he provided

Another noob to the slaughter... Softbricked my i9505. Any advice?

Note: Moved thread
Hey guys,
Sorry to be one of those d**ks who registers and first post is asking for help >_<
Take a seat and join me on this epic quest of failure, which has been my life for the last 12 hours.
Had this phone since release, over the years it has got more and more bogged-down with crap, even from the word go it had tonnes of bloatware installed, but I always avoided the temptation to root, just because I didn't want the hassle if something went wrong... lol.
Yesterday decided to finally take the plunge and root it, whatstheworstthatcouldhappen.jpeg
Here's how it went down....
1. Kingoroot via PC (first tried the apk but it wouldn't work).
2. Hated all the additional stuff that had been added to the phone (new wakeup screen with ads etc)
3. Used a guide to remove and replace kingoroot (kinguser, kingroot, kingmaster) with superuser. zidroid dot com/how-to-get-ride-and-replace-kinguser-with-supersu-app/ <<Here's the guide
4. Stuck on "Installing, please wait" (just after step 8 in the guide)... as the guide explains, if this happens then reboot. So I did...
5. Phone now won't get past the samsung logo (I die a little inside).
6. Google crap for a few hours (Boot into recovery mode etc) I clear cache, remove data.
7. Try loading a stock rom I downloaded and opening it from the sd card... no joy
8. Try Kies... no joy
9. Try Odin... no joy
10. During all of this frantic messing around I loose the option of booting into recovery mode, now I can only get to download mode.
11. Basically spent about 6 hours last night and a few hours this morning trying to get this fixed from all info I could find online... STILL NO JOY.
So now I'm biting the bullet and having to own up to the public, that's you guys.
Anyone here got a clue as to what may have gone wrong/what I can do to resolve this?
Not even fussed about keeping the phone stock, just need it running something!
As I'm sure you can tell I'm new to messing around with android, but I'm not entirely tech-naive so hopefully with some help I might be able to get this back to more than just a paperweight?
Cheers!
Altum said:
Note: Moved thread
Hey guys,
Sorry to be one of those d**ks who registers and first post is asking for help >_<
Take a seat and join me on this epic quest of failure, which has been my life for the last 12 hours.
Had this phone since release, over the years it has got more and more bogged-down with crap, even from the word go it had tonnes of bloatware installed, but I always avoided the temptation to root, just because I didn't want the hassle if something went wrong... lol.
Yesterday decided to finally take the plunge and root it, whatstheworstthatcouldhappen.jpeg
Here's how it went down....
1. Kingoroot via PC (first tried the apk but it wouldn't work).
2. Hated all the additional stuff that had been added to the phone (new wakeup screen with ads etc)
3. Used a guide to remove and replace kingoroot (kinguser, kingroot, kingmaster) with superuser. zidroid dot com/how-to-get-ride-and-replace-kinguser-with-supersu-app/ <<Here's the guide
4. Stuck on "Installing, please wait" (just after step 8 in the guide)... as the guide explains, if this happens then reboot. So I did...
5. Phone now won't get past the samsung logo (I die a little inside).
6. Google crap for a few hours (Boot into recovery mode etc) I clear cache, remove data.
7. Try loading a stock rom I downloaded and opening it from the sd card... no joy
8. Try Kies... no joy
9. Try Odin... no joy
10. During all of this frantic messing around I loose the option of booting into recovery mode, now I can only get to download mode.
11. Basically spent about 6 hours last night and a few hours this morning trying to get this fixed from all info I could find online... STILL NO JOY.
So now I'm biting the bullet and having to own up to the public, that's you guys.
Anyone here got a clue as to what may have gone wrong/what I can do to resolve this?
Not even fussed about keeping the phone stock, just need it running something!
As I'm sure you can tell I'm new to messing around with android, but I'm not entirely tech-naive so hopefully with some help I might be able to get this back to more than just a paperweight?
Cheers!
Click to expand...
Click to collapse
Your mistake was using Kingroot.
Use CF-Auto-Root next time.
And what does "Try Odin... No joy" mean?
Did it fail or did it successfully flash and still didn't boot?
The procedure to flash with Odin is something like:
Download a stock ROM (should have the .tar extension)
Get a good USB cable (preferably the original one) and connect it to a back USB port (any other ports can cause problems) and to the phone.
If flashing fails, try a gain.
You could have avoided this had you just downloaded the correct cf-auto root file and flashed it via Odin..

Reset Resolution back to 1440p (ADB Fails)

Hi, Today like an idiot I've used this app to push the screen up to 4K, happy with the result I've gone too far and set the 5K preset, rebooted the device and... stuck in a launcher/app/logo loop...
The phone is Rooted and running Android 6.0.1, I Have ADB access thru the TWRP. Issue here is that no matter what all the commands like: WM, AM, PM result in this error:
CANNOT LINK EXECUTABLE: cannot locate symbol "context_lookup" referenced by "/system/lib64/libandroid_runtime.so"...
page record for 0x7fae83c010 was not found (block_size=64)
Of course I could flash new the phone but the ammount of data and how is configurated right now is worth the effort.
Most likely you will need to reflash.. that's why devs says that you have to do a nandroid backup just in case... Maybe try safemode?(Vol Down after the logo appears)
Hi , do you fix it ?
I have the same problem on my s6
CRY123 said:
Hi, Today like an idiot I've used this app to push the screen up to 4K, happy with the result I've gone too far and set the 5K preset, rebooted the device and... stuck in a launcher/app/logo loop...
The phone is Rooted and running Android 6.0.1, I Have ADB access thru the TWRP. Issue here is that no matter what all the commands like: WM, AM, PM result in this error:
CANNOT LINK EXECUTABLE: cannot locate symbol "context_lookup" referenced by "/system/lib64/libandroid_runtime.so"...
page record for 0x7fae83c010 was not found (block_size=64)
Of course I could flash new the phone but the ammount of data and how is configurated right now is worth the effort.
Click to expand...
Click to collapse
silver_ch said:
Hi , do you fix it ?
I have the same problem on my s6
Click to expand...
Click to collapse
Unfortunately not, as CH1N3S3_N00B said gotta do backups when messing with these things!
I needed the phone the next day so hoping google held all my contacts I ended up getting all my data thru adb and then flashing on the new 7.0.1 ROM, TWRP, root and in the end loading up superkernel which allows me to set clock, voltages and governors (just in case is not risky enough that someone might grab the phone and send 2+v to your core )
A side note, if you're gonna flash Nougat watch out that the Xposed thing is not yet avaible, I'm a filthy guy and use modules to hide my status on whatsapp while seeing others and didn't expected that.
Best of luck, keep on breaking stuff up, that's the way to learn, although expensive sometimes!
CH1N3S3_N00B said:
Most likely you will need to reflash.. that's why devs says that you have to do a nandroid backup just in case... Maybe try safemode?(Vol Down after the logo appears)
Click to expand...
Click to collapse
I'm sorry didn't received any notification! anyway if you read my answer below you'll see how it ended :crying: (the safe mode didn't work, it was still trying to boot at 5k)

Categories

Resources