Related
Hello, I am in need of a little help. I am a complete noob to android and have no idea really how the system works. I have a Samsung Galaxy S and have decided to root my phone for 2 reasons.. ap2sd and so I can install the lag fix. I have done a bit of reading and chosen the path I wish to take but would like some assurance and pointers. I am also unsure of: If I root my phone does this automatically mean that with a properly partitioned sd card that I can store apps 2 sd or do I still need to flash the handset with a new ROM and if so there I am stuck... I do not know where to begin with searching for the best ROM for me. Also I would like to know if after i've done this will the handset still be able to receive the official updates or will I just need to keep updating it myself!
Here is the rundown as far as i have got so far...
Samsung Galaxy S I9000/XXJF3 Updated!
All the programs for XP i need are downloaded (eg.net3.5/4, samsung drivers)
The root method I thought was best for me was that of TGA_Gunman
The lag fix I had chosen is by Chainfire
I have still to back up the original ROM with ClockWorkMod (Is this easy to do and if I need to use it will it bring me completely back to my original settings for warranty purposes, or is there other things I would need to do?)
Also could someone provide me with a link to the best noob proof SD partitioning method!!
Is there anything I'm missing here, or anything that could be done a better way!! Any and all pointers will be much appreciated....
P.s. I would be wanting to update to the official froyo update when it's available will this cause me problems and if so what must I do!
Thanks in advance
ANDROID NOOB
rooting the phone is safe, and it will not cause any damage to the phone.
but stuff that you install after you root your phone, or modifications and customization changes that you do, might brick the phone, is not done properly (that's the worse case scenario), normally it will just get stuck in a black screen, or endless loop.
All that can be easily fixed using the 3 button Recovery Mode, or 3 button Download mode as posted in the Wiki
I'll suggest you to try the phone rooted but stock with whatever firmware you choose to run.
use the "Lag Fix" only if you really feel the phone sloppy.
I've been using my phone from day one to now without the "Lag Fix" because i've not experience any lag at all.
However I do install Apps to the external SD card, as i want to keep my internal SD as free as possible.
the best link for the Lag Fix & SD card partitioning is the sticky here
http://forum.xda-developers.com/showthread.php?t=724251
AllGamer said:
rooting the phone is safe, and it will not cause any damage to the phone.
but stuff that you install after you root your phone, or modifications and customization changes that you do, might brick the phone, is not done properly (that's the worse case scenario), normally it will just get stuck in a black screen, or endless loop.
All that can be easily fixed using the 3 button Recovery Mode, or 3 button Download mode as posted in the Wiki
I'll suggest you to try the phone rooted but stock with whatever firmware you choose to run.
use the "Lag Fix" only if you really feel the phone sloppy.
I've been using my phone from day one to now without the "Lag Fix" because i've not experience any lag at all.
However I do install Apps to the external SD card, as i want to keep my internal SD as free as possible.
the best link for the Lag Fix & SD card partitioning is the sticky here
Thanks... I understand the risks. Bricked my windows omnia twice before I successfully managed to de-brand and update it!! lol... As to what you said about rooting it and staying with whatever firmware I choose? I wouldn't know which one to use. Normally I wouldnt bother with it all but the lag on my phone now is silly, 5sec pauses on black screens. I end up having to kill my inactive apps once or twice a day just to get some usability from it (which I'm not supposed to need to do)..... So with that in mind is there a firmware that is running better that XXJF3.... Also if flashing a new ROM will be more advantageous and easier I am willing to take that route. I had a look at the link you gave for the lag fix... but being honest I feel that is a bit much for me at this moment... there are many one click lag fixes out there that don't intimidate me so much, is there not a reliable one?... The reason the lag fix you posted scares me is that I dont really understand half of whats being said and am not to sure of the process (if i'm honest it's not explained simple enough for idiots like me) Also dont even know what a busybox is let alone have one, The one click options have them in the package. Sorry, I am so dumb and need the easy route!! LOL.... A Step by step dummies guide would be much appreciated.. LOL! But honestly The more I read the more it all confuses me.....
Anxiously waiting any help possible!!... if it's possible!
Click to expand...
Click to collapse
hmm.. then i'll suggest the "one click lag fix v2" in the developers forum.
that's the easiest way to get it going.
for the I9000 version JM1 seems to be the most stable ROM
I ma be following this thread as I am a noob as well
Thanks to the patient experts here!!!
Cheers!
AllGamer said:
hmm.. then i'll suggest the "one click lag fix v2" in the developers forum.
that's the easiest way to get it going.
for the I9000 version JM1 seems to be the most stable ROM
Click to expand...
Click to collapse
Read some more into the problems with the lag fixes and now see why you were trying to steer me away.... Still way to many bugs for my liking!! I think for now its best like you said to just root and flash a better firmware... But how do I do this, correct me if im wrong:
1. Root phone via TGA_Gunman method
2. Back up phone using clockworkmod
3. download new firmware from samsung firmwares
4. put downloaded firmware onto root folder of internal SD
5. shut down phone then put the phone into download mode (Using the 3 buttons)
6. select the update.... then wait it out!!
Am I missing anything ???
As I side point I called the european samsung office today to ask if there was going to be a fix for the lag in the next month, or is it just the GPS it's concerned with... Samsungs response.... "There wasnt a problem with lag on the phone as far as we knew... You're the first person to complain of it... It has to be a problem with your handset"... Needless to say the conversation went no futrther, or I'd have lost the plot! LOL...
damdeviousduck said:
As I side point I called the european samsung office today to ask if there was going to be a fix for the lag in the next month, or is it just the GPS it's concerned with... Samsungs response.... "There wasnt a problem with lag on the phone as far as we knew... You're the first person to complain of it... It has to be a problem with your handset"... Needless to say the conversation went no further, or I'd have lost the plot! LOL...
Click to expand...
Click to collapse
Holy stitch, what BS is that? FOR ME, THERE IS DEFINITELY LAGGING THE MOMENT I BROUGHT THIS PHONE (from music player to video player to switching between apps or even opening some apps though most of the times its just minimal).
spandsbab said:
Holy stitch, what BS is that? FOR ME, THERE IS DEFINITELY LAGGING THE MOMENT I BROUGHT THIS PHONE (from music player to video player to switching between apps or even opening some apps though most of the times its just minimal).
Click to expand...
Click to collapse
Yeah I've had the same... The longer the phone is in use the slower mine gets... I'm not leaving apps in the background either... It seems as if it just piles and piles inactive apps into the memory then goes slow!! I cancel the inactive ones and It's fast for a while then BOOM!.. slow again, 5/10 screen lag! unreal they're sayin they know nothing! Just hoping that a new firmware will make it better as the lag fixes look way too buggy still! Good luck with yours.. let me know if you find out any better roots/routes to fix the dam thing!
i'll disagree with the lag
i'm still using the stock ROM on mine, and i don't experience the lags some people are having.
i can browse fast, switch apps fast, play audio/video fast, launch GPS app fast, and get a lock fast even when the car is moving on the road already
i do leave stuff like Fring running in the backgroup for my IM and video calls, meanwhile the music player plays via Bluetooth to the car Deck or BT headphones, and using GPS to check my route for speed, traffic jam, etc.
email is constantly syncing, set to auto sync every hour
if i want to check the weather it loads up instantly
using stock JH2 ROM
damdeviousduck said:
1. Root phone via TGA_Gunman method
2. Back up phone using clockworkmod
3. download new firmware from samsung firmwares
4. put downloaded firmware onto root folder of internal SD
5. shut down phone then put the phone into download mode (Using the 3 buttons)
6. select the update.... then wait it out!!
Click to expand...
Click to collapse
As far as im aware you cant install a firmware using the update.zip method? this is more for custom roms and other modifications over the top of an already installed firmware?
you want to open up Odin3 and connect your phone ones in download mode, use this to flash the PDA file in your firmware pack
Using JG4. No lag. None zilch wham. I have seen the lag first hand at a local store.
I will not be installing a lag fix until I understand what they are doing so I don't be a tard (brick my phone).
AllGamer said:
i'll disagree with the lag
i'm still using the stock ROM on mine, and i don't experience the lags some people are having.
i can browse fast, switch apps fast, play audio/video fast, launch GPS app fast, and get a lock fast even when the car is moving on the road already
i do leave stuff like Fring running in the backgroup for my IM and video calls, meanwhile the music player plays via Bluetooth to the car Deck or BT headphones, and using GPS to check my route for speed, traffic jam, etc.
email is constantly syncing, set to auto sync every hour
if i want to check the weather it loads up instantly
using stock JH2 ROM
Click to expand...
Click to collapse
Dont quite understand what you mean... "I'll disagree with the lag" you can't disagree with it it's there... whether you have problems with it or not MANY people do!!
sensi_ said:
As far as im aware you cant install a firmware using the update.zip method? this is more for custom roms and other modifications over the top of an already installed firmware?
you want to open up Odin3 and connect your phone ones in download mode, use this to flash the PDA file in your firmware pack
Click to expand...
Click to collapse
I'm fine up to the point of flashing the formware could you or someone please explain in a bit more detail what ODIN3 is, how it works and what i'm gonna need and what I need to do!! Sorry to be asking so much, but better I ask and get it right than ask for more help on how to unbrick my phone ...LOL
Is it an android program or somethin I put on my PC... also is there anything I would need to do to the phone other than the root!!
EDIT: Why o why do I need to use odin3... From what i'e read all that does is send it back to original settings and firmware... WHICH I HAVE!! I have not even rooted the phone yet, I am gathering enough info before I even begin!!
So back to the point in hand.... I will root my phone back up the ROM with clockworkmod!!
After this I am stuck as to how I flash it with a different firmware one that is more stable and maybe not having issues with lag!!
Which firmware should I pick and how do I get it flashed onto the device!
PLEASE HELP! I need to try something to get rid of this lag it's unbearable! I'm now wondering if there maybe is something wrong with the handset as the lag is really not to be expected 10secs to switch an app... and i've only added bout 15 apps so its not as if I'm expecting alot from the thing!
before you go all the way and do all those Mod to make the phone faster
lets try something more simple and safer to get rid of that LAG problem (10 sec is definitely too much)
go to the phone dial pad
and dial this number
*2767*3855#
Then give us an update if the phone goes back to normal speed.
AllGamer said:
before you go all the way and do all those Mod to make the phone faster
lets try something more simple and safer to get rid of that LAG problem (10 sec is definitely too much)
go to the phone dial pad
and dial this number
*2767*3855#
Then give us an update if the phone goes back to normal speed.
Click to expand...
Click to collapse
did that played with the phone a little a began to see the lag creep up on me again (I am beginning to think this is a problem with memory more than anything, it just keeps loading inactive apps into the memory till it's full) .... Ran quadrant and had a score of 856 although this means not alot to me... what is the norm... and why does that seem slow.... it is after all a 1ghz processor.....
awaiting any ideas/responses.... maybe I am just being too fussy!!!
While i'm still thinking bout what to do... Anybody got any thoughts on the APK ryanZA has released on the market place.. one click root and lagfix!! some comments that it does nothing and some sayin its runnin quadrant scores over 2k....
IS IT ONLY FOR CAPTIVATE/VIBRANT or will it work with european models???????
if it's slow like 10 sec lag even on stock.... i'll definitely return the phone to exchange for another unit.
it should respond immediately, like in 1 sec
AllGamer said:
if it's slow like 10 sec lag even on stock.... i'll definitely return the phone to exchange for another unit.
it should respond immediately, like in 1 sec
Click to expand...
Click to collapse
As I say it doesnt start laggy... it just gets that way after a while of using it!! 'is it then to do with the apps i'm using but them the system manager says its all inactive programs using the space... why does it load so many in!
I have just decided to root and lag fix using Ryans' oneclick apk from the market place... Has worked a treat... Am just waiting for the official JM1 update for mine... Kies wont update my version for now.. Anyway wait and see, got a feeling froyo will be out before they sort out the kies update here! If all else fails wait for the official froyo release and apply it myself with odin!...
thanks for the help!
question for you.
did you install any software that will log your activities?
i just recently installed a network logging app, to see how much 3G /2G/GPRS data i'm using, and i noticed the seldom lags
as soon as i uninstalled that particular software, the stock JH2 ROM runs fast as usual again.
i still have all kind of other apps running in the background like IM, fring, and many other online stuff running continously without any lag
AllGamer said:
question for you.
did you install any software that will log your activities?
i just recently installed a network logging app, to see how much 3G /2G/GPRS data i'm using, and i noticed the seldom lags
as soon as i uninstalled that particular software, the stock JH2 ROM runs fast as usual again.
i still have all kind of other apps running in the background like IM, fring, and many other online stuff running continously without any lag
Click to expand...
Click to collapse
Nope I was getting lag sometimes on a virtually clean handset with only 4 apps installed and the weren't apps that logging any activities at all... think maybe was bad firmware... had re-installation of system today at a samsung repair centre.. see how things go for now!! thanks though...
First of all running stock Droid 3 Rooted Flashed to cricket
with all the fixin's, Bootstrap, CMW, ... etc....
:edit ... Now with safestrap.
_________________________________________
I noticed after taking my phone out of my pocket while trying to turn it on from normal off screen while on that it wouldn't show up the light still indicated it was working I can even turn off the phone.
Taking the battery out and back in semi fixed this but only to the extent where when the phone is turned on the moto logo doesn't appear but the droid eye does.
whence at the booted screen if I were to let it go black it has a chance to not stay on unless I RIGHT after it boots unlock it and keep it lit,
(but)
the main problem I noticed was it really only did this after lets say I was typing or doing anything with the qwerty board open and perhaps I let the screen turn off after a minute,
when I try to wake it up it stays black. EVERY TIME like most of the time,
it has to do with the keyboard being open when the screen goes to sleep.
WHAT IS WRONG *pulls hair out*
_________________________________
I can't say when but I've looked everywhere
tried uninstalling every app but the essentials,
then restoring to my first restore which was after my first initial root.
Tried factory reset,
Tried flashing back to stock,
yeah I think this counts for as much as I've gone insane looking for an answer for.
I have been told this sounded like a software issue so all I'd need to do is re install like I did when flashing back to stock THIS MORNING.
____________________________________________________
I need help to identify somehow if this IS or IS NOT a software/hardware problem.
and an answer to help me fix this would be nice as well thank you.
I know I am supposed to be brief but putting in all that into google and into every forum I have delved just isn't going to put it the way it needs to be said.
______________________________________________________
______________________________________________________
Edit:
Ok so far since no one has said anything I have also reinstalled my old newest state, still giving me crap.
Then just did the newest update 5.7 blah and still it's happening.
I hypothesize it might be the flex ribbon cable maybe (but it really might not) I read from another phone it might be a capacitor but it might not.
Whatever is wrong the phone still is able to at times now 40/60% of the time work properly and wake normal but then again not.
__________________________________________
Right as of now I have put isc to see if this helps .......... .... to be continued or helped.
I'm back, well ics installed fine after the second time made it boot loop over and over.
-----------------------------------------------------------------------
I can receive calls now
but
no sms, mms, or internet.
(even though the network status settings are blank it's weird I can still receive calls, and send calls.)
since you can't restore the apn's with 3rd party I now have this NEW issue.
the phone goes unresponsive within cdma workshop and ##Program does not work.
I'd like some help in finding out now how to if it is possible yet to properly flash to cricket and or just change my apns and get into cdma as well as QPST.
__________________________________________
PLEASE I NEED HELP thank you
-3nJo1
Yeah, it does sound like a hardware problem. If nobody else can help you fix it, you'll need to reflash the latest OTA update (or revert to your safestrap nandroid), unroot it and restore all the system apps that you may have frozen/deleted, and hope that Verizon will replace it.
Thanks
necromanteion said:
Yeah, it does sound like a hardware problem. If nobody else can help you fix it, you'll need to reflash the latest OTA update (or revert to your safestrap nandroid), unroot it and restore all the system apps that you may have frozen/deleted, and hope that Verizon will replace it.
Click to expand...
Click to collapse
Thanks for your input.
(verizon wouldn't replace it since I baught it from someone else (legit) and I don't have verizon.
UNLESS you think if I had the previous owner take it into the store could they replace it? what steps would they take to see if it was rooted?
_______________________
I never unrooted it when I did allll of this
Do you think rerooting is soumething that I should have done before doing this?
Or most likely is this a flex ribbon cable thing ....
I just tried the diagnostic (leave keyboard open then turn the screen off and on thing)
it came on at least 3 times normal then it didn't either right after the 3rd try or upon closing the qwerty board ...
also do you have an answer at all for the ics portion of my problem?
THANK YOU
___________________________________________________________
EDIT!!!!!!!! Actually realized I did reroot after the sbf ota flash .....
so all things aside yehs I also did that any other solutions inquiries ...
ANYONE ELSE PLEASE HELP!
Another path to try down is Motorola - depending on the age of the phone, I believe there's a warranty through them.
stud beefpile said:
Another path to try down is Motorola - depending on the age of the phone, I believe there's a warranty through them.
Click to expand...
Click to collapse
Thanks,
well it is less than a year old I think, could I be able to get motorola to replace it when all I have is the phone no receipt or box ???
MORE HELP FROM ANYONE ELSE PLEASE
I bought my d3 off craigslist and the power button and n key weren't always working. I took it in to Verizon and had a new one in the mail 3 days later!
Sent from my XT862 using XDA App
Sorry didn't read the part about you being on cricket. Maybe you could make friends with someone that has d3 on verizon have them activate it and take it in for you.
3nJo1 said:
Thanks,
well it is less than a year old I think, could I be able to get motorola to replace it when all I have is the phone no receipt or box ???
MORE HELP FROM ANYONE ELSE PLEASE
Click to expand...
Click to collapse
I believe there is another apn type tool that the Cricket Android tools are using for their specific settings. You may have to search XDA a bit to see if anything shows up for othere phones on Cricket.
Sent from my DROID3 using XDA App
At a certain point on my screen, the phone thinks I am touching it.
I dont know how else to explain it but a 'phantom touch'.
Its repetitive and very annoying.
It seemed to start after I flashed some custom ROMS.
I flashed back to stock (2.3.5) in the hopes of it being fixed but it seemed to follow me.
Has anyone had this issue/knows how to fix it?
Thanks
It was completely fine before flashing the custom roms? try re-flashing stock rom, don't root, do factory data wipe from the settings. If its still following you, it might be a hardware issue. and if that's the case, you might need to send it in. It should be covered from the 1 year samsung warranty. make sure you don't have the triangle
dr. xp55 said:
It was completely fine before flashing the custom roms? try re-flashing stock rom, don't root, do factory data wipe from the settings. If its still following you, it might be a hardware issue. and if that's the case, you might need to send it in. It should be covered from the 1 year samsung warranty. make sure you don't have the triangle
Click to expand...
Click to collapse
It seems to have just gone away on its own. Cheers for the help anyway, would have done this if I still had the problem.
It seems to come back when I flash a ROM.
I flashed the German ICS official ROM (which is great btw), and it seems to have come back.
Hopefully, someone can provide me with a solution, perhaps its a corrupt system file?
Still, it goes away when the phone is charging.
Any ideas at all?
I'm not sure if this is helpful, but I faced the same issue when I flashed ParanoidAndroid yesterday. In Settings>Device settings, there is an option of "screen sensitivity". I set that to 10 (the minimum, ie, the most sensitive). It was then that these phantom touches started. I set it to 100(max, least sensitive) and I couldn't get the touchscreen to register any touches at all. The Spen worked in both cases, so I just used that to reset it.
Anyhow, I believe that this menu is accessible via a key code on stock roms. I'm not sure of it, but it should be. Look around in the tips and tricks thread, all secret codes for the Note are listed over there. Then just change sensitivity to 20.
Hi, I think this seems to be the trick.
I was unable to find the code to access the settings menu you described.
However, I installed TouchScreenTune, and that seems to be working for the moment.
Will post my results in a few hours or so.
Thanks
bloodyhippo said:
In Settings>Device settings, there is an option of "screen sensitivity". I set that to 10 (the minimum, ie, the most sensitive)....
Anyhow, I believe that this menu is accessible via a key code on stock roms. I'm not sure of it, but it should be. Look around in the tips and tricks thread, all secret codes for the Note are listed over there. Then just change sensitivity to 20.
Click to expand...
Click to collapse
Also, If you are able to remember/get the code that would be great.
I found a list of the codes but none look like they'll be what you mentioned.
Thanks again
novastorm17 said:
Also, If you are able to remember/get the code that would be great.
I found a list of the codes but none look like they'll be what you mentioned.
Thanks again
Click to expand...
Click to collapse
You're right, I couldn't find one that'd help either. Hmm.
Do you still have the problem?
It hasn't gone away, but I think the frequency at which it occurs has reduced
Any other ideas/any other way to do your previous method?
Cheers
Okay so here is all the information I have.
No matter which ROM I flash, the issue of the random touching continues.
Ive tried without root, and tried a complete reinstall (by formatting all data and storage)
I found a CWM restore I made 6 months ago (long before the issue started). That didnt work either.
Things that DO work:
TouchScreenTune seems to greatly reduce the frequency at which at occurs by decreasing the sensitivity of the screen, however, it makes it harder to use the phone.
Plugging in USB stops it completely, but when its removed, the issue comes back.
I thought since it is following me through different ROMs it is a hardware issue.
Does ANYONE know a fix/heard of this before?
At the moment Ive resorted to using my old IDEOS (oh god) and have begun working towards a warranty rectification.
Thanks anyone who can help
Update from Samsung:
Issue due to motherboard/touchscreen
Cheers for your help
Like the title says, I will paypal $15 (or more if you give me extra help) to whoever can help me root and upgrade my Galaxy Tab SCH-i800. I need it rooted and an upgrade to 4.0 or higher would be nice. I've tried one click roots and none worked. I've tried following youtube videos and they never turn out to work. Seems like cyanogenmod would be the best route, but I just can't seem to get it right.
Now, I've done my fair share of computing: I'm familiar with torrents, keygens, cracks, I've also accomplished several circuit board repairs for my car stereo, car window switches, and my macbook. But when it comes to software I'm more of an apple person, windows and android frustrate me.
I should also mention I made another attempt to root my tab last night. I was following a youtube video on how to use heimdall and I got pretty far and everything seemed to be working, but after the part where heimdall automatically reboots the tab it booted up like normal, but the touchscreen doesn't work. it senses my finger but the directions are off, like up is right, and down is left, and vice versa. Now I need to figure out how to fix this.
I'm exhausted after spending hour after hour googling all these problems and trying to understand all this android and root lingo. I figure I should just have an expert completely walk me through it so I can stop wasting my time sitting in front of my computer and so I don't mess up anymore.
Thanks!
You can try
http://forum.xda-developers.com/showthread.php?t=1585619
it is for Sprint tab, but will work on Verizon tab.
priyana said:
You can try
http://forum.xda-developers.com/showthread.php?t=1585619
it is for Sprint tab, but will work on Verizon tab.
Click to expand...
Click to collapse
I'm sure this is helpful, but the problem is I don't understand what all of this means, I've tried figuring it out but I screw up everytime.
Firstly, do you have access to a windows or Linux machine ... Aka not a mac
jim80b said:
Firstly, do you have access to a windows or Linux machine ... Aka not a mac
Click to expand...
Click to collapse
Yeah I have a pc with windows 7. I've tried several attempts with heimdall and I finally got it to work after watching a few youtube videos, and it rebooted my tab and I thought I finally got it, but when it turned on things were very messed up. the screen digitizer is Waaayy off, up is right, left is down, and vice versa. I don't think its communicating with the battery correctly since it says it been 100% for 3 days straight. also a big problem is it won't turn off.
I must have loaded the wrong file for something in the process and got something screwed up. Should I download all the stock firmware or software and reload it on my tablet?
Also back to rooting, I was talking to someone and they suggested I use odin instead of heimdall, they think I will have better success.
Also since I have your attention, I want to upgrade to 4.0 or higher. Do I root before I upgrade or after?
Thanks!
There are many resources on these websites... Www.xda-developers.com and www.rootzwiki.com. check out the forums for the galaxy tab. Both have step by step instructions on doing this. When looking for Roms, make sure you download the p1c ROM. Cyanogenmod and other roms use that designation. That is for the CDMA tab (Verizon and sprint). I've used heimdall and Odin. IMO they are both equally as useful and user friendly.
If your tab doesn't shut down, hold the power button down for about 8 seconds. It will shut down.
Which ROM did you flash when you started seeing the touchscreen problems?
Hang in there. I remember when I started tinkering with rooting and flashing Roms. It takes some time to understand and get it right. Hang in there.
Sent from my SCH-I545 using Tapatalk
Carson-TL said:
Yeah I have a pc with windows 7. I've tried several attempts with heimdall and I finally got it to work after watching a few youtube videos, and it rebooted my tab and I thought I finally got it, but when it turned on things were very messed up. the screen digitizer is Waaayy off, up is right, left is down, and vice versa. I don't think its communicating with the battery correctly since it says it been 100% for 3 days straight. also a big problem is it won't turn off.
I must have loaded the wrong file for something in the process and got something screwed up. Should I download all the stock firmware or software and reload it on my tablet?
Also back to rooting, I was talking to someone and they suggested I use odin instead of heimdall, they think I will have better success.
Also since I have your attention, I want to upgrade to 4.0 or higher. Do I root before I upgrade or after?
Thanks!
Click to expand...
Click to collapse
Can you boot into recovery by pressing power-on and volume-up keys together?
If you can and you have installed a correct CDMA kernel via Heimdahl everything can be worked out and you can get to 4.0, not latest 4.4.2 though at this point.
However, the behavior of your screen suggests you installed a wrong kernel...
Hm
I've recently rooted/flashed my newly acquired sch-i800 to all kinds of roms. if you want me to zip up the heimdall files i've used, let me know.
alternatively, this is the guide i used:
well due to being a new member it wont let me link, pm me for a link to the guide i used.
the first rom i successfully flashed was the p1c download cm9.1 and corresponding gapps
Soooooo, I installed a new layer and the phone borked, hooked it up to the unbrick restore tool kit, it flashed the whole rom and failed after 100%, Now when I connect it it gives me this. Any help?
Try this: http://onlinejobwithoutanyinvestment.com/sp-flash-tool-errors-fix-brom-error/
Can you get into recovery and reformat?
Maybe as of now, try to follow this post.
http://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
I assume you have tried the restore method posted by tomsgt. And on that thread there are a few other posts same error as you
Hello, the recent bricks appear to have something to do with a guide posted by a user recently. If you have bricked your phone, please join the hangout below where we will cooperate with you to investigate the cause of your brick and attempt to find a fix.
Join the conversation on Hangouts: https://hangouts.google.com/group/Q5wGs6508l1rqGng2
Sent from my LG G4 using XDA Labs
Various from errors
It looks like the hangout stated above is closed, but I looked at the other link and I'm hoping someone might be able to clarify. Under the brom 4032 it states:
download preloader and move it to target_bin folder and rename or move checksum.ini from target_bin.
Do they mean the preloader driver? Or the preloader file that would be in the firmware or somewhere. And it goes into the sp flash tools folder somewhere? Or the firmware I'm flashing? I have the 16/2 Amazon version, and I actually have another I'm using that has been successfully rooted and bootloader unlocked. Is there something I could extract from the working phone to help jumpstart the bricked one?
Persuasion89 said:
It looks like the hangout stated above is closed, but I looked at the other link and I'm hoping someone might be able to clarify. Under the brom 4032 it states:
download preloader and move it to target_bin folder and rename or move checksum.ini from target_bin.
Do they mean the preloader driver? Or the preloader file that would be in the firmware or somewhere. And it goes into the sp flash tools folder somewhere? Or the firmware I'm flashing? I have the 16/2 Amazon version, and I actually have another I'm using that has been successfully rooted and bootloader unlocked. Is there something I could extract from the working phone to help jumpstart the bricked one?
Click to expand...
Click to collapse
This is what i reed from the error list. None of the fixes that i see say to touch the preloader.
"7. Error 5054 – BROM ERROR S_DL_GET_DRAM_SETTINGS_FAIL (5054)
Fix : Need to Check load matches your target which is to be downloaded. For more info, that the file you’re trying to flash do not belong or not compatible with your phone. Verify that you are using the right version of files for your device. If so, try to formatting before flashing again."
and just to show what i read about 4032 (not the error the op has)
14. Error 4032: Operation Skill Problems
Fix : Press the volume down button (key to reduce volume), then it can trigger the yellow bar progress continue. You’d better install batteries in your mobile during flash process.
edit 1:
sorry rereading page it get confussing. there multiple error 4032 messages.
6. Error 4032 – BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032) [EMI] Enable DRAM fail
Fix : Ensure that the files you are trying to flash are exact version of your phone model. If so, now try to formatting your phone but do not format the boot loader before flashing it. Sometimes, device that produce in 2014 also result this error code, solution is download preloader and move it to target_bin folder and rename or move checksum.ini from target_bin.
This would be the best solution for BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032) [EMI] Enable DRAM fail, SP Flash Tool is unable to enable DRAM or communicate effectively with your device issue.
but still this error does not have same text as the op
mrmazak said:
This is what i reed from the error list. None of the fixes that i see say to touch the preloader.
"7. Error 5054 – BROM ERROR S_DL_GET_DRAM_SETTINGS_FAIL (5054)
Fix : Need to Check load matches your target which is to be downloaded. For more info, that the file you’re trying to flash do not belong or not compatible with your phone. Verify that you are using the right version of files for your device. If so, try to formatting before flashing again."
and just to show what i read about 4032 (not the error the op has)
14. Error 4032: Operation Skill Problems
Fix : Press the volume down button (key to reduce volume), then it can trigger the yellow bar progress continue. You’d better install batteries in your mobile during flash process.
edit 1:
sorry rereading page it get confussing. there multiple error 4032 messages.
6. Error 4032 – BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032) [EMI] Enable DRAM fail
Fix : Ensure that the files you are trying to flash are exact version of your phone model. If so, now try to formatting your phone but do not format the boot loader before flashing it. Sometimes, device that produce in 2014 also result this error code, solution is download preloader and move it to target_bin folder and rename or move checksum.ini from target_bin.
This would be the best solution for BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032) [EMI] Enable DRAM fail, SP Flash Tool is unable to enable DRAM or communicate effectively with your device issue.
but still this error does not have same text as the op
Click to expand...
Click to collapse
Well to clarify I also receive the 0x13be or whichever is in the op attached picture. I'm pretty sure this is what I get if I plug in my phone while completely powered down after hitting download. Red bar loads like in picture, and then error. However I've tried various button techniques as advised by other posts and sources, which yield various other errors including the 4032 and 5034. It seems like it just depends on how the setup is feeling. I'd verify which methods yield which results, but I'm having boot issues with my laptop now. My basic logic though is they're all hanging at the same spot, immediately after da load but prior to injection. Maybe this is noobish but I think it's one issue causing all of the errors, and I'm hoping that a solution for either op or I would benefit us both. I'm not very experienced but I have a feeling the preloader.bin isn't doing its thing. Will I be able to get this file with a read back of a working r1 16/2? That's a little long, and sorry if these answers are out there but I've looked around over the last week and I get pointed in a direction, but I can't find a solid answer. I'd really just like to be informed as I don't want to break anything else.
Persuasion89 said:
Well to clarify I also receive the 0x13be or whichever is in the op attached picture. I'm pretty sure this is what I get if I plug in my phone while completely powered down after hitting download. Red bar loads like in picture, and then error. However I've tried various button techniques as advised by other posts and sources, which yield various other errors including the 4032 and 5034. It seems like it just depends on how the setup is feeling. I'd verify which methods yield which results, but I'm having boot issues with my laptop now. My basic logic though is they're all hanging at the same spot, immediately after da load but prior to injection. Maybe this is noobish but I think it's one issue causing all of the errors, and I'm hoping that a solution for either op or I would benefit us both. I'm not very experienced but I have a feeling the preloader.bin isn't doing its thing. Will I be able to get this file with a read back of a working r1 16/2? That's a little long, and sorry if these answers are out there but I've looked around over the last week and I get pointed in a direction, but I can't find a solid answer. I'd really just like to be informed as I don't want to break anything else.
Click to expand...
Click to collapse
Well your attention to detail is vital. As you are one of the first to have come across this issue on this phone so when we do have a solution if will most likely become a stiky guide so to prevent further issues. Hopefully you are not past your Amazon return point. As far as I know there is not an answer on what you will need to do. So if we have time to keep troubleshooting that will be good but if you need to do a return that is understandable.
mrmazak said:
Well your attention to detail is vital. As you are one of the first to have come across this issue on this phone so when we do have a solution if will most likely become a stiky guide so to prevent further issues. Hopefully you are not past your Amazon return point. As far as I know there is not an answer on what you will need to do. So if we have time to keep troubleshooting that will be good but if you need to do a return that is understandable.
Click to expand...
Click to collapse
I have two, the other one is just going to be a backup so I'll report back if I find a silver bullet. It's recognized by PC and still trying to come back, so if I totally brick it I'll call the 60$ cost of education.
Persuasion89 said:
I have two, the other one is just going to be a backup so I'll report back if I find a silver bullet. It's recognized by PC and still trying to come back, so if I totally brick it I'll call the 60$ cost of education.
Click to expand...
Click to collapse
I feel the same way, legit bought two of these to just play around with. The mistake I made was somehow enabling format all + Download. This completely borked my phone.
I am using a S7 Edge, and i'm also on Verizon, my girlfriend is on Tmobile however and when her case comes tomorrow she will be retiring her G3 for this phone. Her phone is fine though.
Mine does the fancy download mode of just showing red at the bottom of the tool when you plug it in and the only sign of life is through the LED on the phone, like the eye of the terminator. Just a red led, constantly on.
Phone will connect instantly, but after being connected to the PC for at least 30 seconds it'll randomly make the disconnect noise and the tool will no longer recognize it, but interesting enough the LED is still on and if you hit download after the "disconnect" then actually REMOVE the cable, you'll get an error even though no download mode is present at least not visably.
If you open device manager under windows 10 for me, and then connect the phone it'll show the MediaTek under com/Ports, but after it makes the disconnect sound it's no longer there {No duh, right} Just an observation...but after a minute or so it'll automatically pop back up.
This made Colton and Mr. Mazak think that the preloader is still in tact, just everything else is out of whack.
We are currently in the process/thinking of a way to create a scatter for the entire backup of the phone (The first boot into TWRP) and seeing if there is a way to completely restore the phone from the SPFT via the new scatter/backup.
I do not know how to do this, so I am waiting on the R1 HD gods to bestow upon me their methods of wisdom and hopefully fix the brick! Colton told me it'll be a couple days, i'm in no hurry, but it's always exciting to think there's a possible fix, and considering this is an ugly problem, if it gets fixed they're going to save many phones.
etc, etc.
Yeah exactly what I'm dealing with, well first I was getting a flashy home screen after boot. Re flash didn't work so I took the bad advice of format+DL. The thing I don't get though is if it's not the preloader then why won't ANYTHING flash.
Have you tried a read back? Because every option on my end is just a brick wall right after initialization. I figured if preloader is intact then it would at least attempt to read the memory blocks, or let me attempt a format, or anything. My phone's picked up properly by two PCs, and really the red bar is the da handshaking the preloader to lock the phone in that state during the flash right? Or Chinese to English translation is more difficult to understand than I expected.
Regardless I'm just a noob with too much free time. I'm Trying to make a bootable drive for my laptop so I can put in work, but latest Ill be at it here in a couple hours once I'm free. I'm convinced this is fixable so I'm going to pull everything I can from the working phone and see what I can figure out. Ill be back to consult the thread before I do anything big though. Hopefully I can contribute some to this. I have a vision of how this is going to work, but I couldn't explain it for the life of me.
Gytole said:
I feel the same way, legit bought two of these to just play around with. The mistake I made was somehow enabling format all + Download. This completely borked my phone.
I am using a S7 Edge, and i'm also on Verizon, my girlfriend is on Tmobile however and when her case comes tomorrow she will be retiring her G3 for this phone. Her phone is fine though.
Mine does the fancy download mode of just showing red at the bottom of the tool when you plug it in and the only sign of life is through the LED on the phone, like the eye of the terminator. Just a red led, constantly on.
Phone will connect instantly, but after being connected to the PC for at least 30 seconds it'll randomly make the disconnect noise and the tool will no longer recognize it, but interesting enough the LED is still on and if you hit download after the "disconnect" then actually REMOVE the cable, you'll get an error even though no download mode is present at least not visably.
If you open device manager under windows 10 for me, and then connect the phone it'll show the MediaTek under com/Ports, but after it makes the disconnect sound it's no longer there {No duh, right} Just an observation...but after a minute or so it'll automatically pop back up.
This made Colton and Mr. Mazak think that the preloader is still in tact, just everything else is out of whack.
We are currently in the process/thinking of a way to create a scatter for the entire backup of the phone (The first boot into TWRP) and seeing if there is a way to completely restore the phone from the SPFT via the new scatter/backup.
I do not know how to do this, so I am waiting on the R1 HD gods to bestow upon me their methods of wisdom and hopefully fix the brick! Colton told me it'll be a couple days, i'm in no hurry, but it's always exciting to think there's a possible fix, and considering this is an ugly problem, if it gets fixed they're going to save many phones.
etc, etc.
Click to expand...
Click to collapse
So just a quick question here. Something clicked for a second. In this description you said Windows shows connected then lost , during the spft process?
If this is case means phone is not realy off.
But if I misunderstand the order nvm.
Maybe disconnecting battery is needed for your situation.
mrmazak said:
So just a quick question here. Something clicked for a second. In this description you said Windows shows connected then lost , during the spft process?
If this is case means phone is not realy off.
But if I misunderstand the order nvm.
Maybe disconnecting battery is needed for your situation.
Click to expand...
Click to collapse
Disconnected the battery, ran the return to stock, red download and red led light only. Same boat.
So just a quick question here. Something clicked for a second. In this description you said Windows shows connected then lost , during the spft process?
If this is case means phone is not realy off.
But if I misunderstand the order nvm.
Maybe disconnecting battery is needed for your situation.
Click to expand...
Click to collapse
I thought the same as well but I was a little afraid to try and get in there to do it. New laptop is coming weds so I haven't had a way to work on this but it's worth a try. I kinda thought the same.
Disconnected the battery, ran the return to stock, red download and red led light only. Same boat.
Click to expand...
Click to collapse
How difficult is it to remove? I'm assuming there's some soldering involved?
Persuasion89 said:
I thought the same as well but I was a little afraid to try and get in there to do it. New laptop is coming weds so I haven't had a way to work on this but it's worth a try. I kinda thought the same.
How difficult is it to remove? I'm assuming there's some soldering involved?
Click to expand...
Click to collapse
Nope. Just remove all the screws underneath the removable cover then the backplate is held in by snaps, I used a guitar pick to pry the edges from the rest of the frame and it popped right out. Do note its rather stiff and flimsy so pry with care.
Gytole said:
Nope. Just remove all the screws underneath the removable cover then the backplate is held in by snaps, I used a guitar pick to pry the edges from the rest of the frame and it popped right out. Do note its rather stiff and flimsy so pry with care.
Click to expand...
Click to collapse
I might give this a shot. also I've read about the test point flashing by grounding one of the pins, Apparently that's how they do it in the factories. If it doesn't work and I'll have it apart anyway I might give it a shot.
Persuasion89 said:
I might give this a shot. also I've read about the test point flashing by grounding one of the pins, Apparently that's how they do it in the factories. If it doesn't work and I'll have it apart anyway I might give it a shot.
Click to expand...
Click to collapse
If you do try to find the "meta" mode. Still can't flash anything yet. Unless you made your own backup before original flash. Because the files in the convert and unbrick section are not the complete ROM. Since you are stuck from doing a format all, I don't think those will do it.
But I do think it is a good idea to find a stable way to get phone connected to PC so it can be flashed though
just see something about vcom drivers. and the op screenshot shows usb driver(lower right corner of photo). it should be a vcom driver(lower right corner of photo)
mrmazak said:
If you do try to find the "meta" mode. Still can't flash anything yet. Unless you made your own backup before original flash. Because the files in the convert and unbrick section are not the complete ROM. Since you are stuck from doing a format all, I don't think those will do it.
But I do think it is a good idea to find a stable way to get phone connected to PC so it can be flashed though
Click to expand...
Click to collapse
so i have a full rom backup. or at least it should be. I also have a full TWRP backup i cant use on my SD card. MT Droid tools doesnt support this chipset though, so I dont know how else to get this readback i did chopped into partitions.
Just wondering, how many phones are bricked? Of these bricked phones how many were caused from flashing witha VM? And how many used the format function to try and recover?