Related
Hi all.
My wife hqs a I9003. She was running rooted stock 2.2.1 KB1FW on it. Everything was fine untill about 4 days ago. Thay's when without reason the whole Android system started to fail. Clock, Maps, Messaging, TW Launcher, etc all gave error and forced closed. She only had about 10 or 15 apps installed and all on phone memory. So I did a Factory Restore thinkg it would help but it was all still the same.
So I flashed KPE (all 4 files) and a new error started: after 1 or 2 after the factory restore on new FW, phone crashes and goes in to a boot loop (Samsung logo and intro screen). Once I manage to get back to Android, it's reset to factory settings (install wizzard). I've flashed KPH, KB1, KB3 etc and it's the same problem all the time. Was flashing the APBOOT file from KPE a mistake?? How can I fix this?? I don't have a backup and even if I did, I can enter download mode but not restore mode (Vol Up + Home + Power).
Please, I need help urgently
Thanks
Sent from my GT-I9000 using XDA App
Before this all started did she install some unknown kinda software/app from the market?
Also while flashing did you use Latona.pit file?
Sent from my GT-I9003 using Tapatalk
Nope. Thay's the weird thing. On mine, I'm constantly installing/deleting from the market, blackmarket and other sources and have no problems. All the apps she had, I installed myself and were all "safe".
As far as the pit file, I used it first joint with the other 4 files (like I did for my I9000) and after I used it on it's own. I've tried first the pit file, then the FW files, just the FW files and the pit + FW files with and without re-partition checked... I'm running out of ideas and getting desperate...
Sent from my GT-I9000 using XDA App
Sounds to me like the phone has developed a hardware fault.
Things do just up and die sometimes..
Could it be the battery??? She hasn't dropped or banged it at all. Mine had a slight swim.and is still perfect. If I flash it back to a European KB1, would the warranty still cover me??
Sent from my GT-I9000 using XDA App
Try to do the following:
Select only latona (.pit) and repartition in odin. Put the phone in download mode and flash.
Next reset all. Select pda, modem, csc file from XXKB3 firmware. Dont choose repartition and flash.
hope it works
Sent from my GT-I9003 using Tapatalk
Tell me teh method what you followed to flash? Like first, the pit file with re-partion,auto-reboot and F.reset time checked. And, then, the other 4 file of the SAME Fw with the auto-reset unchecked. Also, Did you click on the reset button after flashing the pit file?
Try to do the following:
Select only latona (.pit) and repartition in odin. Put the phone in download mode and flash.
Next reset all. Select pda, modem, csc file from XXKB3 firmware. Dont choose repartition and flash.
hope it works
Sent from my GT-I9003 using Tapatalk
Click to expand...
Click to collapse
Had done that before but just did it again. So far it has crashed once but didn't revert back to factory default this time and I now have the recovery mode again.
Tell me teh method what you followed to flash? Like first, the pit file with re-partion,auto-reboot and F.reset time checked. And, then, the other 4 file of the SAME Fw with the auto-reset unchecked. Also, Did you click on the reset button after flashing the pit file?
Click to expand...
Click to collapse
I've done it various ways as I explained in the first post. With and without re-partition, with and without the pit file, etc.
But I had a minor brainwave this morning after the first crash on XXKB3. The microSD she had in her phone was an 8GB she got with her old Xperia. It was used under Symbian and when I put it in her Galaxy, I think I had formatted it with the PC but not with the phone. Can't remember (she has it since May). In any case, she didn't have apps stored on the SD but she did have all wallpapers, photos, music, ringtones, etc. I've now removed the SD and see how it goes. Just thinking that maybe the SD is f****d and could be creating a shortcut or inestability with the phone... Worth a try as I'm all out of ideas.
Thatnks to everyone for the help you're providing me with this issue. I suppose it's weird that after flashing many different ROMs the problem persists and is still the same. If all else fails and I re-flash the XXKB1, do yo guys think Samsung will take responasability for the problem?? I have it unlocked with the app thats on the market, but AFAIK I have the EFS folder backup stored somewhere.
Well phone still switching off with the XXKB3 FW. It's only switching off now tho... No boot loop. And at least now I know it's not the SD at fault. I'll try re-flashing XXKB3 tomorrow as I only flashed it once today. Then I'll do a factory format and reset battery stats once I flash the CWM. If after that it's still the same, I gues I'll have to restore the EFS folder, flash the XXKB1 FW and send it off to Samsung and hope for the best... Unless anyone has any other idea I can try???
Sent from my GT-I9000 using XDA App
i am not sure bout this but if you flash xxkph it shouldnt void varanty since its official rom? right o.o
xGiox said:
i am not sure bout this but if you flash xxkph it shouldnt void varanty since its official rom? right o.o
Click to expand...
Click to collapse
No. Anything that is done using Odin voids your warranty so when visiting service centre just flash to the firmware that your phone came out of the box then tell the service centre staff the phone just went crazy or anything like that just dont talk about Odin to them. And try this out.
1. Download an app called Rom manager from the market.
2. Make sure you are rooted.
3. Go into rom manager and hit fix permissions.
4. Reboot.
That should do it. Or else its the service centre.
Sent from my GT-I9003
crazbanditz said:
No. Anything that is done using Odin voids your warranty so when visiting service centre just flash to the firmware that your phone came out of the box then tell the service centre staff the phone just went crazy or anything like that just dont talk about Odin to them. And try this out.
1. Download an app called Rom manager from the market.
2. Make sure you are rooted.
3. Go into rom manager and hit fix permissions.
4. Reboot.
That should do it. Or else its the service centre.
Sent from my GT-I9003
Click to expand...
Click to collapse
i mean they wont know if he used kies or odin.
xGiox said:
i mean they wont know if he used kies or odin.
Click to expand...
Click to collapse
But if you dont come from russia which the csc says ser which is russia then they will know its definite you used Odin as there is no other ways you could get to a firmware of another region where you don't even come from using Kies unless you hacked Kies which also voids the warranty.
Sent from my GT-I9003
crazbanditz said:
But if you dont come from russia which the csc says ser which is russia then they will know its definite you used Odin as there is no other ways you could get to a firmware of another region where you don't even come from using Kies unless you hacked Kies which also voids the warranty.
Sent from my GT-I9003
Click to expand...
Click to collapse
LOL., you can say you travel to RUSSIAN..
madi3d8 said:
LOL., you can say you travel to RUSSIAN..
Click to expand...
Click to collapse
Then the warranty will be voided didnt you see they said warranty will be voided if not bought within the country or something like that.??
Sent from my GT-I9003
That is complex! In, India, You just go into the service center and tell him your problem! He will check the FW version and tell that you void warranty. Just SHOUT at him and tell him you are a developer ..VOILA! He will service it! He will take a hell lot of time for a small problem though!
And if I'm willing to pay for the repair?? Or maybe load a europe CSC file on it... Had a bit of a bright idea today: switch batteries. She's using my I9000's battery at the moment. Let's see if it doesn't turn off. My I9000 fell yesterday, had a rubber cover on it so the bang wasn't bad BUT my loud speaker has blown out seems easy enough to replace and I do laptop repairs so shouldn't be too much hastle to sort it myself. But so much for the Galaxy S being the iPhone 4 killer... Sem to be quite delicate phones...
Bit of off topic: anyone know anything about the Galaxy S 3??? If and when it's coming out and some type of details.. Galaxy S 2 was a big failure with more problems than the one I have according to what I've read on the internet...
Sent from my GT-I9000 using XDA App
DigiRay said:
And if I'm willing to pay for the repair?? Or maybe load a europe CSC file on it... Had a bit of a bright idea today: switch batteries. She's using my I9000's battery at the moment. Let's see if it doesn't turn off. My I9000 fell yesterday, had a rubber cover on it so the bang wasn't bad BUT my loud speaker has blown out seems easy enough to replace and I do laptop repairs so shouldn't be too much hastle to sort it myself. But so much for the Galaxy S being the iPhone 4 killer... Sem to be quite delicate phones...
Bit of off topic: anyone know anything about the Galaxy S 3??? If and when it's coming out and some type of details.. Galaxy S 2 was a big failure with more problems than the one I have according to what I've read on the internet...
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
1) Galaxy S3 will be launched once Nexus Prime is out (also being made out by Samsung)
2) Nexus Prime will be released some time in October so S3 will probably be released late October or sometime in November (more or less - to compete with iPhone5)
3) Galaxy S2 is one of the hottest selling item in the WORLD right now - i guess you have read some biased reports about its performance issues.
Just thought I'd give you all a quick update on what's happened with my wife's I9003.
After trying everything possible to fix it via flashing, the whole internal memory collapsed. It wasn't even able to finish installing the last firmware I flashed on it.
I took it to the shop, told them what happened and the sent it off to the technical repair service. That was on the 5th of this month.
Got it back today fully working!!!
They changed the main board as a faulty part, so even though it was unlocked with no EFS backup and was flashed numerous times, the guarantee took care of the repair
Tomorrow I'll root it and install ROM Manager and do a backup of the firmware before I flash it to Gingerbread, as they've returned it with Froyo and carrier boot screen. And this time I'll keep a backup of the EFS folder too LOL
I wonder is there anyway to force a main board to break via software, would be interesting for those that have voided their warranty by unlocking or flashing, if the board is broke, any changes become untraceable.
While I'm here, just a quick question: When I do the backup via ROM Manager, will it backup only the PHONE part of the firmware or will the MODEM & CSC be included too?? If it's only the PHONE file, how can I backup the others???
Thanks to all of you that responded to my original post and tried to help me with the phone.
Sent from my GT-I9000 using XDA App
Had some issues with my galaxy tab.
Long story short I went to nandroid restore and **** got worse. The tablet was repartitioned before creating nandroid and I thought it would restore okay.. NO.
I used factory reset package and tried to get it back to factory, no dice. NO matter what i try IT BOOTS, BUT old apps are there. I can manually uninstall them, restart the tablet and they are back and Force Closing like crazy. I tried a factory reset from the device and same. I don't know what to do I need some sort of superwipe.
I have tried about everything I can think of. Anyone else have any ideas here? A superwipe zip etc?
Fix permissions in CWM.
Sent from my SCH-I510 using xda premium
kvswim said:
Fix permissions in CWM.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Tried but no cigar. Don't think there is a whole lot i haven't tried at this point seems like the card may be going bad.
Repartition?
Sent from my SCH-I510 using xda premium
I would say if wipe doesn't work, flash back to stock using odin/heimdall then flash what you have right now... repartition doing so...
However Factory reset not working is kinda strange...
Waiting for more details or info
I'm reaching a bit, but one problem you *could* be having is that since you've added new roms you've updated your filesystems from RFS to EXT4. I'd have to look at the ROM package you are using to determine how it's moving data onto your filesystems, but if it's true stock then it may not know anything about EXT4 and be trying to mount the filesystems as RFS (which would fail if you've converted to EXT4).
I've found in playing around with flashing a lot of different kernels and builds to my phone that a flashing "everything" using Heimdall is the most thorough approach. What you want is a build that will replace the cache, data, system, root and kernel "/dev/block" devices, as well as the primary and secondary bootloaders. This link:
http://forum.xda-developers.com/showthread.php?t=1275031
Has the stock rom (it's a TAR file, like you would use with ODIN, but un-tar it and you can use with Heimdall) for a Sprint Tab. I don't know if that's what you have, but I'm sure you can find an appropriate stock for your tab. If all you get is a big TAR file, what you want to do is un-tar it and the contents should be something like:
zImage
recovery.bin
factoryfs.rfs
params.lfs
cache.lfs
dbdata.rfs
boot.bin
Sbl.bin
...and there will probably be a modem.bin. I would avoid flashing that if you can. I've just had some very bad experiences flashing the wrong modem.bin by mistake (had to take the tab apart, solder a JTAG to it, and use the JTAG ressurect to bring the tab back to life).
While all this "should" work that same with ODIN, my experiences have been more reliable after reflashing with Heimdall. By reflashing something like "factoryfs.rfs" you will not only be flashing the files, but also in effect be reformating the filesystem for the "factory" system files you need.
Keep in mind doing this kind of reflash will return your filesystems to a "pristine" RFS state... but it should get you back to a place where you can then restore your nandroid backup with Heimdall.
I have been having the same problem with my cdma tab, no matter what rom I install or the method (heimdall,Odin,or cwm) I have apps that will not delete and non stop force closes. These apps will come back after data wipes, and from rom to rom they are automatically reinstalled.
Miui is the only gingerbread rom that I had limited success with, but with miui I get non-stop keyboard fc's. And the unwanted apps still come back.
I have tried everything suggested in this thread, and the only thing that has semi worked was flashing an ice cream rom to the tab. But of the two ics roms I found, one has no wifi, and the other says encryption unsuccessful on boot.
Any help would be greatly appreciated.
Sent from my Inspire 4g using ICS
I have the same problem with my tab few montsh ago.Nothing help.I took tab to samsung service.It was damage mainboard.In service they replace mainboard and after that it works like charm.I think that you should do the same. Sorry for my bad english.
Thanks for your input jdiem. I tried what you suggested on heimdall as well. Didn't work.
Sent from my PG86100 using Tapatalk
xena0709 said:
I have the same problem with my tab few montsh ago.Nothing help.I took tab to samsung service.It was damage mainboard.In service they replace mainboard and after that it works like charm.I think that you should do the same. Sorry for my bad english.
Click to expand...
Click to collapse
Thanks, my tablet is currently at Samsung repair awaiting repair parts. Meaning that as you mention here, if you have this problem it appears to be a hardware issue. Mine was around 1 month old so still in warranty. Sucks to have to live without it though.
Sent from my PG86100 using Tapatalk
Follow up, they changed the PCB. All was well initially, however, after a couple weeks the tablet began having the same issue all over again
Really weird.
Hi everyone,
I finally might have figured out how to fix the ghost call issues and the reorginizing internal process problem... it has been 10 days that I have had no ghost calls and no RIP.
After many hours arguing with LG (who after all 12 calls still said they never heard of this problem before). The only advice they could offer me was to send my phone to repairs.
I decided to do a final attempt and if it didn't work I would have sent my phone in 3 times to get a different phone and end this nightmare.
So I did a factory reset on my phone.
The problem was still there.
I heard about keeping the CPU above 600mhz all the time and while that temporarily worked it came back.
I loaded the recovery mode and factory reset from there and I also cleared the cache. that didn't work.
After more research I found that putting the phone in 2g will help. While this was true it was still happening but a lot less.
I decided to explore the world of Roms and that's where the fix came in.
My phone is rooted. Big thank you to Dan 
I am running V20c 2.3.5
I Formatted my internal SD and my external.
I installed clockwork mod and backed up my stock rom... I then booted into recovery mode and cleared every cache option (2 on first screen and dalvik in advanced. The only exception was battery stats with CWM.
After doing all that, I had to leave so I figured I would look for a new rom another time. That was 15 days ago. After a week I realized that I haven't been getting the RIP or the GC problem... seeing as how it was hard to check I forwarded all my calls from my home office line to my cell phone so that if the call was not answered it would go to my cell after the 2nd ring. To this day (10 days later)... every call on that phone has been registered on my cell... therefore I believe that CWM IS THE KEY TO OUR PROBLEMS
*JUST NOTE THAT I SAVED MY SD CARD TO MY PC SO I HAD A EXTRA BACKUP SHOULD NEED BE.*
**WHEN I DID IT, I FORMATTED WITH CWM**
so after all that here's the process...
*WORKS ON V20C 2.3.5 ROGERS*
1. ROOT
2. FORMAT EVERYTHING (SETTINGS/STORAGE...)
3. VERIFY THAT YOU STILL HAVE ROOT (YOU SHOULD)
4. INSTALL CWM
5. BACKUP YOUR DEFAULT ROM (NEVER KNOW)
6. ENTER CLOCKWORK RECOVERY
7. CLEAR ALL CACHE EXCEPT BATTERY STATS (I DID NOT TOUCH ANY PARTITIONS OPTIONS)
8. GO BACK IN YOUR PHONE
9. DO NOT PUT BACK YOUR BACKUP ROM
***Remember this is working for me on Rogers V20c 2.3.5***
I made a titanium backup of all my Apps but I am not restoring them I am redownloading from scratch. I do not know if it will cause issues with the GC/RIP issues.
Good luck to all of you and I hope that you finally get to enjoy our cursed phones. I had RIP messages easily every 2 hours and for 15 days I haven't seen a single one and all my calls are working.
Thank you to Dan for Root and the Creator of CWM for saving us.
Sent from my LG-P925g using XDA
Nitedriver said:
Hi everyone,
I finally might have figured out how to fix the ghost call issues and the reorginizing internal process problem... it has been 10 days that I have had no ghost calls and no RIP.
After many hours arguing with LG (who after all 12 calls still said they never heard of this problem before). The only advice they could offer me was to send my phone to repairs.
I decided to do a final attempt and if it didn't work I would have sent my phone in 3 times to get a different phone and end this nightmare.
So I did a factory reset on my phone.
The problem was still there.
I heard about keeping the CPU above 600mhz all the time and while that temporarily worked it came back.
I loaded the recovery mode and factory restored from there and I also cleared the cache. that didn't work.
After more research I found that putting the phone in 2g will help. While this was true it was still happening but a lot less.
I decided to explore the world of Roms and that's where the fix came in.
My phone is rooted. Big thank you to Dan 
I am running V20c 2.3.5
I installed clockwork mod and backed up my stock rom... I then booted into recovery mode and cleared every cache option with CWM. Formatted my internal SD and my external.
After doing all that, I had to leave so I figured I would look for a new rom another time. That was 15 days ago. After a week I realized that I haven't been getting the RIP or the GC problem... seeing as how it was hard to check I forwarded all my calls from my home office line to my cell phone so that if the call was not answered it would go to my cell after the 2nd ring. To this day 10 days later... every call on that phone has been registered on my cell... therefore I believe that CWM IS THE KEY TO OUR PROBLEMS
so after all that here's the process...
1. ROOT
2. FORMAT EVERYTHING (SETTINGS/STORAGE...)
3. VERIFY THAT YOU STILL HAVE ROOT (YOU SHOULD)
4. INSTALL CWM
5. BACKUP YOUR DEFAULT ROM (NEVER KNOW)
6. ENTER CLOCKWORK RECOVERY
7. CLEAR ALL CACHE AND FORMAT (I DID NOT TOUCH ANY PARTITIONS OPTIONS)
8. GO BACK IN YOUR PHONE
9. DO NOT PUT BACK YOUR BACKUP ROM
***Remember this is working for me on Rogers V20c 2.3.5***
I made a titanium backup of all my Apps but I am not restoring them I am redownloading from scratch. I do not know if it will cause issues with the GC/RIP issues.
Good luck to all of you and I hope that you finally get to enjoy our cursed phones. I had RIP messages easily every 2 hours and for 15 days I haven't seen a single one and all my calls are working.
Thank you to Dan for Root and the Creator of CWM for saving us.
Sent from my LG-P925g using XDA
Click to expand...
Click to collapse
CWM isn't the issue. It's the baseband.
CWM is on a different partition than the baseband and is not active until it is called. Ghost calls still exist because 2.3.5 in general has this issue. 2.3.6 fixed ghost calls.
Sent from my Samsung Galaxy S II w/ CM9
Never said that CWM was a problem I said CWM helped fix this issue
I posted this to help others who were looking for a solution it is still working for me so I'm happy and I figured id share my findings in hopes of helping others who got nothing to lose and everything to gain with this phone.
Have a good one.
I believe that CWM FIXED my phone
Sent from my LG-P925g using XDA
[Removed comment after being confirmed safe to format SDCARD in CWM]
johnw230873 said:
Hi Guys, be aware that people have fully bricked their phone formating there sdcard using CWM.
Click to expand...
Click to collapse
Ooo I wasn't aware... well guess I was lucky.... I think just formatting the SD card regularly (not with CWM) and then using CWM to clear caches would be enough...going to modify original post thanks John
Sent from my LG-P925g using XDA
146 views and no confirmations or experiences... there is a 0% chance of bricking your phone.... come on guys try it and post... if it doesn't work for everyone else then at least people know. Help eachother out you got nothing to lose (if u back up) if ur scared for ur backups remove the external SD during testing or backup to ur PC.
Sent from my LG-P925g using XDA
Wait. You should remove the notices for BRICKING.
Reason being as it is only applicable to CyanogenMod. It has an option to use the sdcard for data instead. Stock doesn't.
Formatting sdcard and emmc in ClockworkMod will not and can not brick your device on a LG Firmware.
This, again, does not include CyanogenMod.
Now. As for fixing the problem, I've done this method and still have ghost calls.
You will ALMOST always get ghost calls with 2.3.5.
Sent from my Samsung Galaxy S II w/ CM9
Hi Guys I was going off other information in other posts for example http://forum.xda-developers.com/showthread.php?t=1529836&page=2 talking about CWM and CyanogenMod.
I'm not an expert in this area and after reading this didn't want a lot of bricked phone so thought I'll better say something, have edited my post and removed the comment.
I have also tried this, worked for 3 days then a GC
The Dark Lestat said:
Wait. You should remove the notices for BRICKING.
Reason being as it is only applicable to CyanogenMod. It has an option to use the sdcard for data instead. Stock doesn't.
Formatting sdcard and emmc in ClockworkMod will not and can not brick your device on a LG Firmware.
This, again, does not include CyanogenMod.
Now. As for fixing the problem, I've done this method and still have ghost calls.
You will ALMOST always get ghost calls with 2.3.5.
Sent from my Samsung Galaxy S II w/ CM9
Click to expand...
Click to collapse
Done thanks
Sent from my LG-P925g using XDA
Its been mentioned that 2.3.6 fixes the ghost call issue, however i am having dificulties finding this. Can someone post a direct link to the thread or download spot gor it?
Sent from my LG-P925 using XDA
cmeducknow702 said:
Its been mentioned that 2.3.6 fixes the ghost call issue, however i am having dificulties finding this. Can someone post a direct link to the thread or download spot gor it?
Sent from my LG-P925 using XDA
Click to expand...
Click to collapse
I assume this because all devices friends have ranging from Nexus to Samsung to HTC with 2.3.5 had ghost calls and when they updated to 2.3.6, ghost calls disappeared. They were on stock as well.
Sent from my Samsung Galaxy S II w/ CM9
Ok, i've only been worried about my thrill... never paid attention any others. Thanks
Sent from my LG-P925 using XDA
NOOOOOOOOOOOOO!!! Scrap this thread guys....I just got my first. R.I.P I HATE THIS PHONE!
it was going so well....
Does anyone know any stable 3D working roms that fix this issue??? Let me know thanks...
Sent from my Rooted ANTI GC/RIP LG-P925g using XDA
Hello,
When I got my Note, I must have installed every app going on it, the phone got clogged up and just kept crashing out and being generally rubbish so I thought Id do a hard reset and start over. I booted into the stock recovery menu and just did a factory reset, it worked fine and the handsets fine but Im interested to know if on a stock rom, locked bootloader with no rooting could that affect my handset and mess with the storage capacity?
With me looking at rooting and roms Ive seen a lot of posts where people have rooted and done wipes on their phone and its corrupted the storage, loosing part of it, so I was just interested if the same risks apply to a stock handset?
mozza54 said:
Hello,
When I got my Note, I must have installed every app going on it, the phone got clogged up and just kept crashing out and being generally rubbish so I thought Id do a hard reset and start over. I booted into the stock recovery menu and just did a factory reset, it worked fine and the handsets fine but Im interested to know if on a stock rom, locked bootloader with no rooting could that affect my handset and mess with the storage capacity?
With me looking at rooting and roms Ive seen a lot of posts where people have rooted and done wipes on their phone and its corrupted the storage, loosing part of it, so I was just interested if the same risks apply to a stock handset?
Click to expand...
Click to collapse
See your post, I believe you are in GB rom / or on a safe ICS kernel.
Otherwise, I can only say you are damn lucky.
Rooting is not a problem in note. But wiping is a problem if u r on stock ICS kernel.
A lot of thread regarding this one alrd. If you're handphone is fine now, and you don't need root / etc... Just use it as per normal.
But if you want to do more with your handphone, read carefully on all thread that you wish to try to experiment on your handset.
I don't quite understand with what you want. Perhaps you could give your about screenshot, to know more on what stock rom you are now, and which kernel you are now. Then you list out what you need to do.
Sent from the corner of this rounded earth.
No it can't mess with storage capacity, you are on stock recovery and that is safe
Sent from my GT-N7000 using xda premium
Im just interested in finding out if me resetting my handset could have corrupted the phones storage. Not including my SD card, my note says Ive got 1.97gb of internal storage and then 11gb of USB storage which considering its a 16gb phone means theres about 3gb less. Even my external card (which is 16gb) registers 14.3gb. so I was just interested to find out if this is correct or if it sounds like the reboot has caused an issue?
I've only had the handset a couple of weeks and obviously its all still under warranty so I've got the option to send it back, which is easier the newer the handset.
mozza54 said:
Im just interested in finding out if me resetting my handset could have corrupted the phones storage. Not including my SD card, my note says Ive got 1.97gb of internal storage and then 11gb of USB storage which considering its a 16gb phone means theres about 3gb less. Even my external card (which is 16gb) registers 14.3gb. so I was just interested to find out if this is correct or if it sounds like the reboot has caused an issue?
I've only had the handset a couple of weeks and obviously its all still under warranty so I've got the option to send it back, which is easier the newer the handset.
Click to expand...
Click to collapse
Those figures are correct, the rest of the memory is allocated to system. If you'd damaged the emmc you'd know about it cos the phone wouldn't boot. There's an app you can install to check for emmc damage in the play store
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
You need to be rooted to do a full scan.
Sent from my GT-N7000 using xda premium
SpyderTracks said:
Those figures are correct, the rest of the memory is allocated to system. If you'd damaged the emmc you'd know about it cos the phone wouldn't boot. There's an app you can install to check for emmc damage in the play store
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
You need to be rooted to do a full scan.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Yeah I saw that,.. thanks for the help, I think Im gonna has to stop being a giant wus now and get this sucker rooted
mozza54 said:
Yeah I saw that,.. thanks for the help, I think Im gonna has to stop being a giant wus now and get this sucker rooted
Click to expand...
Click to collapse
It's worth it and nowadays fairly straight forward using pc odin or mobile odin. Look for links in the forum.
Sent from my GT-N7000 using xda premium
Hi peeps.
I was rooted a while back. Had problems with phone freezing mostly when using camera.
Sooo i unrooted, relocked bootloader and then used the Sony update to repair. So ive been on .757 pure stock and i got more problems with that, touchscreen was weird from time to time. It rebooted once a day and it didnt matter wich task i was doing it seems (when rooted it only happened during use of camera and mostly AR effects). So now i became random reboots.
Well i rerooted now and now i can use the AOSP brower again(thank god for that) and most things i wanna have working are working. Havent tested it for that long yet when rerooted but keeping fingers crossed that it will work like it should. Possibly some random reboots wich i dunno whats causing them.
But isnt it strange.
I was wondering about something though. Scrolling seems not so smooth when rooted, but that might be placebo kicking in.
/Jonas
I was wrong It worked just as bad with rootaccess now. So I repaired the phone again with Sony update.
I just wanna get rid if this phone now, it gives me me a headache!!!
Sent from my C6903 using XDA Free mobile app
if you get reboots on Custom Roms with Custom Kernels, well, it's not strange to me, it happen many time, BUT if you get random reboots on Stock, then I will should be worry about it. For all the other reasons you have to have them less on stock, if you really still have all this issues then I will replace it via warranty. I heard some Xperias was not fixed with any Firmware.
Well that's just it. I have reboots on stock rom with stock kernel. Usually once every day. I can't get rid of it. I've repaired and repaired and it is still the same.
Here is the funny part, the warranty of the phone expired one month before I even bought it when I was in touch with Sony. I have abit of an argue with my retailer atm since he says it's software related. And im saying I wanna return it. And get either money back or a new working phone.
Sent from my C6903 using XDA Free mobile app
Reflash stock rom via flashtool. It sounds like your just repairing the device. Do factory reset and flash stock rom.do a back up first.
Sent from my C6906 using XDA Free mobile app
I am on .136 stock (4.3), no root, no unlocked bootloader... all works fine...I have read so many people complaining about newer updates to .681 or .757 .... I do not see any point updating to newer versions, as I am not missing anything major with .136
Jonas740 said:
Hi peeps.
I was rooted a while back. Had problems with phone freezing mostly when using camera.
Sooo i unrooted, relocked bootloader and then used the Sony update to repair. So ive been on .757 pure stock and i got more problems with that, touchscreen was weird from time to time. It rebooted once a day and it didnt matter wich task i was doing it seems (when rooted it only happened during use of camera and mostly AR effects). So now i became random reboots.
/Jonas
Click to expand...
Click to collapse
That isn't anything to do with rooting m8, how you flash your phone and what you flash onto your phone, the apps you use or don't use and your actual habits you have, these are some of the things which cause random reboots and problems for the most part, the other is bad luck and hardware issues.
Particular devices did have some rebooting issues, I myself haven't had one in a long time so i don't get them at all, whether i'm on a custom rom or an AOSP rom, I do get the occasional slow down but there isn't a phone out there or PC for that matter that never slows down at any time.
What I would say to do is to clean up your internal and external memory and download a tried and tested rom, lets say monxified 6.0.3
Go back to 534 and re-root, install a custom recovery and flash that bad boy (don't forget to perform a full wipe, factory, cache and dalvic) use a full FTF to fill in the blanks using flashtool (avoid flashing system and TA , exlude wiping with flashtool) Do not restore using recovery either.
Don't flash a custom kernel either, just let the system boot and see how it runs, install one or two apps (not a massive restoration using titanium) Avoid xposed for now and reboot the phone.
See if you can leave it like that for a while and see if you get any random reboots.
Do it by the numbers methodically and you should be fine
Good luck
How do I wipe everything with flashtool.
Last time I rooted I flashed 681 with flashtool. Had strange reboots then aswell.
Let me say this, I have unlocked the bootloader and I do not have backup on my TA. Wouldn't older roms then 681 mess up my phone? Bootloader is relocked with flashtool and I ain't rooted and I don't have CWM installed anymore.
So easiest way to clear the phone would then be? And I want to use Stable Sony rom.
Guide me step by step like if was a complete idiot
Sent from my C6903 using XDA Free mobile app
Jonas740 said:
Let me say this, I have unlocked the bootloader and I do not have backup on my TA. Wouldn't older roms then 681 mess up my phone? Bootloader is relocked with flashtool and I ain't rooted and I don't have CWM installed anymore.
Click to expand...
Click to collapse
If you don't have TA then I don't understand why you relocked your bootloader with Flashtool, it not make sense to me.
Jonas740 said:
So easiest way to clear the phone would then be? And I want to use Stable Sony rom.
Click to expand...
Click to collapse
Unlock Booltloader, Flash a Stock FTF and wipe everything, then proceed with the steps to gain Root.
Jonas740 said:
Guide me step by step like if was a complete idiot
Click to expand...
Click to collapse
You know the steps. ..LOL..
I locked just for camera tests.
But when you say "wipe". Doesn't flashtool already wipe all if I flash a stock rom?
Sent from my C6903 using XDA Free mobile app
Jonas740 said:
I locked just for camera tests.
Click to expand...
Click to collapse
Without DRM Keys the test is useless, but maybe you know now from fact that it not change.
Jonas740 said:
But when you say "wipe". Doesn't flashtool already wipe all if I flash a stock rom?
Click to expand...
Click to collapse
Yes, this is what I meant, just click on Wipe Data, Appslog and Cache. Still not a full format of your system partition but this is what it do to make a clean installation.
Well I did that a few days after I received my phone. I had the same problems back then. I actually did just that one hour before making this post aswell. Hoping it would work good, which it didn't.
If the phone would have been in my possession a little longer I would run it over with my car. Now it's quite new so I won't do that but I'm really tired of it and it's so boring have to send it to my retailer for repairs and w8 forever. Then when I get it back. I BET that they only will flash new software and test it for five min and ship it back and it will still have the same problem.
Been there done that alot of times with other things
Sent from my C6903 using XDA Free mobile app
(Comment removed. Made a stupid derp)
I was thinking rolling back to 4.3 though to see if that would be more stable. Noticed that, if the phone don't reboot in a day wich it normally does then the touch is acting weird instead.
And last night I stopped it from rebooting, I pressed the power button to turn of screen when it frooze and that cancelled the reboot. But after that I noticed some apps with camera didn't work.
Sent from my C6903 using XDA Free mobile app
I think something like a Tool to format the entire system partition will be useful but in your case I think it will not help much.
Mega wipe Google it. Back up first as it'll nuke your memory.
Sent from my C6903 using XDA Premium 4 mobile app
Well now I have wiped the phone using cvm. And I flashed 4.3 instead hoping the phone will be stable. If it ain't it's going in the bin
I do miss the emoji keyboard, but that's about it. Know if it's possible to get that on 4.3?
Phone feels alot faster on 4.3, the camera reacts faster and tbh the pictures look better. No problems so far, hoping it will work. Battery time is also ALOT better!
Sent from my C6903 using XDA Free mobile app