Related
Wow! I need some help. I've acquired a Samsung Galaxy Note (i717, I believe) that shows all the signs of being healthy (appearance, touch screen, etc.) but persistently slows down at the ATT opening splash screen, begins to load Android, dies and reboots. Whatever variant rooted ROM I received it with (sluggish and unreliable) I have written over and now I can't get any farther than the Android settings screen. Therefore I do not know the exact version nor can I begin to set it up (wifi, etc.).
That's the 'presenting problem', so let me explain what I've done to this point (about 25 hrs. worth!). I have reloaded latest version of CWM (runs great) and then Padawan JB . . . same symptoms. I have loaded the ATT JB and ICS via the latest Odin successfully . . . with same symptoms. I have loaded TWRP (touch screen is snappy and works as it should) and Padawan JB again . . . with same symptoms. I have wiped caches before, after, and in between till I'm blue in the face, each time with the same symptoms. Most recently I have done a hard reset to native/factory settings . . . with no change! I've tried to scour the XDA (and any other sites) trouble shooting articles and seem to have come to a dead end.
Here's a couple things that I'm wondering: because I can't get deep enough into Android to check out the model number, could the phone be something other than an ATT model? At the top of the front face it simply says 'Samsung', not ATT at top and Samsung at bottom like my previous ATT Note. Right after boot I persistently get an ATT splash screen which would lead me to believe that it is ATT. Is there some other way to find model, say in TWRP? Do I need a phone specific version of Android? Second, everything seems to be working fine physically (i.e., no hardware problems). Could this thing have gotten a virus in an earlier life that's preventing the ROM from working right? I've not been able to get far enough to register it with my cell provider (second party, not ATT). Must you be up and running with the cell service to correctly load and use the ROM (wouldn't think so)? And if so, how without Android working? I've been using and playing with computers for 25 years, but I'm fairly new to the Android system (but learning fast!) Any help would sure be appreciated. I'd really like to resurrect this baby. I loved my first Note (till it fell off the car and disappeared).
pstrulm said:
Wow! I need some help. I've acquired a Samsung Galaxy Note (i717, I believe) that shows all the signs of being healthy (appearance, touch screen, etc.) but persistently slows down at the ATT opening splash screen, begins to load Android, dies and reboots. Whatever variant rooted ROM I received it with (sluggish and unreliable) I have written over and now I can't get any farther than the Android settings screen. Therefore I do not know the exact version nor can I begin to set it up (wifi, etc.).
That's the 'presenting problem', so let me explain what I've done to this point (about 25 hrs. worth!). I have reloaded latest version of CWM (runs great) and then Padawan JB . . . same symptoms. I have loaded the ATT JB and ICS via the latest Odin successfully . . . with same symptoms. I have loaded TWRP (touch screen is snappy and works as it should) and Padawan JB again . . . with same symptoms. I have wiped caches before, after, and in between till I'm blue in the face, each time with the same symptoms. Most recently I have done a hard reset to native/factory settings . . . with no change! I've tried to scour the XDA (and any other sites) trouble shooting articles and seem to have come to a dead end.
Here's a couple things that I'm wondering: because I can't get deep enough into Android to check out the model number, could the phone be something other than an ATT model? At the top of the front face it simply says 'Samsung', not ATT at top and Samsung at bottom like my previous ATT Note. Right after boot I persistently get an ATT splash screen which would lead me to believe that it is ATT. Is there some other way to find model, say in TWRP? Do I need a phone specific version of Android? Second, everything seems to be working fine physically (i.e., no hardware problems). Could this thing have gotten a virus in an earlier life that's preventing the ROM from working right? I've not been able to get far enough to register it with my cell provider (second party, not ATT). Must you be up and running with the cell service to correctly load and use the ROM (wouldn't think so)? And if so, how without Android working? I've been using and playing with computers for 25 years, but I'm fairly new to the Android system (but learning fast!) Any help would sure be appreciated. I'd really like to resurrect this baby. I loved my first Note (till it fell off the car and disappeared).
Click to expand...
Click to collapse
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory reset in between.
fbauto1 said:
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory
I would reflash cwm thru odin after that I would flash the latest TWRP 2.5. Then you can flash whatever. If padawan is givin u problems try something else like AOSP or AOKP. Padawan is TW based. JaimeD builds are pretty sweet.
sent from my GalaxySuperNote running OC Padawan JB
Click to expand...
Click to collapse
androidmechanic said:
fbauto1 said:
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory
I would reflash cwm thru odin after that I would flash the latest TWRP 2.5. Then you can flash whatever. If padawan is givin u problems try something else like AOSP or AOKP. Padawan is TW based. JaimeD builds are pretty sweet.
sent from my GalaxySuperNote running OC Padawan JB
Click to expand...
Click to collapse
If you want TWRP, flash TWRP. No need to flash CWM
Click to expand...
Click to collapse
AT&T Phones have a [logo}AT&T] on the top-center!!
But if you are in doubt, use kies to do a full recovery-restore [WILL ERASE EVERYTHING ON YOUR DEVICE].
See post #4 on this thread.
fbauto1 said:
androidmechanic said:
If you want TWRP, flash TWRP. No need to flash CWM
Click to expand...
Click to collapse
If you go thru Odin you would have cwm first. With the problems talked about, I would go back factory stock then re-root with Odin. Then thru cwm, flash twrp or whatever floats your boat.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
androidmechanic said:
If you go thru Odin you would have cwm first. With the problems talked about, I would go back factory stock then re-root with Odin. Then thru cwm, flash twrp or whatever floats your boat.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
fbauto1 said:
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
Click to expand...
Click to collapse
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
fbauto1 said:
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
Click to expand...
Click to collapse
androidmechanic said:
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
you are both actually correct, however, I am looking at PSTRULM's stats. if he is anything like me when I started, the more simple and less complication involved in the process, the more he may understand.
ANDROIDMECHANIC is stating the most basic and beginner way to do this and understand simply. after doing this a few times as I did, the basic mechanics of the process will become more fluent.
then he can make his own decisions as to methods which might be easier for him, without confusing.
I am sure you both are a huge help to everyone and I thank members such as yourself for your efforts. ME, I prefer baby steps, cause I know I can really EFF things up if I get confused
androidmechanic said:
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Just a reminder.. when flashing through Odin, make sure it's an ODIN-flashable tarball, i.e., you can't flash a recovery-type zip through Odin and vice versa.
This will help anyone who keeps having flashing issues.
More detailed instructions in my GUIDE!
http://forum.xda-developers.com/showthread.php?t=2295557
THIS IS ONE QUICK/SIMPLE ERROR FREE ROM FLASHING PROCEDURE
This should eliminate a few posts saying, stuck in download mode, stuck at logo. just vibrates and them MANY other issues that somehow, everyone seems to find.
Here is my quick rom flashing process I use ALWAYS (yes always)
THINGS YOU NEED ON extSDCARD
1. Extra kernels (2 or 3 you know works for your device)
2. Optional: 2 recoveries that can be flashed (I use CWM & TWRP)
3. Optional: apps.zip (a zip created from Titantium BU, containing Root Explorer, TU Backup, Quickpic, ES File Explorer and Terminal Emulator)
Flashing the rom: TOUCHWIZ/AOSP ROMS
1. Backup current rom (to the extsdcard)
2. Complete wipe, (I do complete, some people do not) Complete = No Issues [FACTORY RESET + CLEAR CACHE + CLEAR DALVIK CACHE + CLEAR DATA]
3. Flash the rom
4. Flash the kernel (your device kernel) (I know some roms have their own kernel) this is where your problems start.
AGAIN: FLASH YOUR KERNEL, you KNOW it works. 1 more time FLASH YOUR KERNEL. (you can experiment with other kernels after you boot)
AOSP ROMS - require you to flash gapps before you boot. [This is not required for TouchWiz roms]
5. Boot the rom.
FINISHED!!!! SUCCESS!!!
Total time to flash a rom:
7-10min
Errors - NONE
This goes for every rom in my guide.
TIPS:
This flash procedure is for Touchwiz Roms, if you are flashing AOSP roms, you must flash the gapps package associated with the rom you are flashing.
**** SGH-I337M Users: Often requires flashing a different kernel than the one included in most ATT ROMS. Any GT-i9505 kernel will work and Adam kernel and Faux kernel are both confirmed working for us Canadian users.
Note: Flash KERNEL directly after ROM then reboot device.
[Special thanks to blyndfyre for this helpful tip].
The extra recovery I flash if a rom does not like the recovery I am using.
Yes, you can flash recoveries back and forth.
Apps.zip I flash after the rom is up & running. This I use to get the rom setup (like root explorer and others needed)
I am in no way responsible for anything that may do damage to any device - Use these tips at your own risk - period!
If you found this useful in any way, please hit the THANKS button for my effort.
RESERVED
TheAxman said:
Any questions? Anyone.
Click to expand...
Click to collapse
I've been running into a lot of issues when trying to flash different ROMs. For instance, right now I'm on CleanROM 1.6 - I just tried to install PureGv2.
Steps I took:
Have Goo and ROM Manager installed after clean install of CleanROM 1.6
Flash CWM from ROM Manager
Install Recovery Script from Goo
Reboot into recover from Goo
TWRP loads
Wipe data, cache, dalvik, etc
Install PureGv2
I forget the error off the top of my head but it doesn't install
In a nutshell I'm asking what am I doing wrong? Do I need to flash another kernel?
Flash your verizon kernel. Correct. I know it is a vzn rom, but do it anyway.
TheAxman said:
Flash your verizon kernel. Correct. I know it is a vzn rom, but do it anyway.
Click to expand...
Click to collapse
Was looking through Tomsgt's Youtube channel and stumbled across a video of his that showed his "About Phone". Everything was identical to mine, so I'm still a little lost as to why I can flash certain ROMs but not others. Sac/Gru's ROM soft bricked my phone, Hyperdrive5.7 didn't install, CleanROM does. It's just funky...maybe I'll just Odin back to stock, flash the MDK and start fresh.
Could the downloads be a problem? I downloaded 2 of the ROMs from work today on a 50meg pipe and they didn't work.
Do you download the ROMs to your phone or to your computer and then move them to your SD card?
If you download to your phone, do you move them to the SD card or leave them in the download folder on the internal storage?
If you do the latter, do you use a micro SD adapter or plug the phone in and move them that way?
harrytery said:
Was looking through Tomsgt's Youtube channel and stumbled across a video of his that showed his "About Phone". Everything was identical to mine, so I'm still a little lost as to why I can flash certain ROMs but not others. Sac/Gru's ROM soft bricked my phone, Hyperdrive5.7 didn't install, CleanROM does. It's just funky...maybe I'll just Odin back to stock, flash the MDK and start fresh.
Could the downloads be a problem? I downloaded 2 of the ROMs from work today on a 50meg pipe and they didn't work.
Do you download the ROMs to your phone or to your computer and then move them to your SD card?
If you download to your phone, do you move them to the SD card or leave them in the download folder on the internal storage?
If you do the latter, do you use a micro SD adapter or plug the phone in and move them that way?
Click to expand...
Click to collapse
Download to the computer,then copy to the phones extsdcard, should be ok, make sure you do a md5 check on the files to make sure they are the correct size.
TheAxman said:
Download to the computer,then copy to the phones extsdcard, should be ok, make sure you do a md5 check on the files to make sure they are the correct size.
Click to expand...
Click to collapse
Alright sounds good. Flashing back to stock later today then re-rooting
thanks for the help
Remember always do a BACKUP before you do anything.
First off, big thanks for this thread.
Now I'm running Cleanrom 1.5. If I wanted to install a new rom can someone please explain exactly what I do to go about it? As jargon free as possible would be awesome.
Sent from my SCH-I545
I certainly scared the carp outta me the other night. I'm using the Carbon ROM and while I do like it, I miss a couple of the S4s features. I picked what looked like a good modified stock ROM and proceeded to flash it.
I'm using Goo and TWRP for the job. I checked of all 3 boxes for clearing cache, davik and factory reset.
Then I chose the file and started it.
The first result, it acted like if was doing everything but nothing changed. Phone still worked fine.
On the next try, I waited for TWERP to start and I reselected the ROM I wanted and flashed it.
When it booted up, I was very happy to see the original screens come up. Then it stopped on the one with the Verizon check mark. The blue LED slowly pulsing and nothing else for about 30 min. I removed battery to try and start over. Same thing again.
Time to goto my backup and restore my phone back to Carbon.
IT FAILED.
Now my phone is stuck in a weird looking boot up loop. After a few tries I was able to get into recovery
mode. TWRP started loading, froze and crashed! Even though I am a total noob at this, I still did not panic.
I'd restart my phone by removing the battery, going into recovery mode and then wildly press every button on my phone hoping to break the loop. It worked! I chose a different save and tried it all over again. FAIL.
ON the next I wiped every bit of old data off. Chose Factory restore crossed my fiingers....it work! My phone is fine now.
Thanks to that ordeal and this thread I think I know what I did wrong even though this never happened to me. before.
1) WIPE THE DATA
2)INSTALL A COMPATABLE KERNAL FIRST
V^^^^V
Vampyre111 said:
I certainly scared the carp outta me the other night. I'm using the Carbon ROM and while I do like it, I miss a couple of the S4s features. I picked what looked like a good modified stock ROM and proceeded to flash it.
I'm using Goo and TWRP for the job. I checked of all 3 boxes for clearing cache, davik and factory reset.
Then I chose the file and started it.
The first result, it acted like if was doing everything but nothing changed. Phone still worked fine.
On the next try, I waited for TWERP to start and I reselected the ROM I wanted and flashed it.
When it booted up, I was very happy to see the original screens come up. Then it stopped on the one with the Verizon check mark. The blue LED slowly pulsing and nothing else for about 30 min. I removed battery to try and start over. Same thing again.
Time to goto my backup and restore my phone back to Carbon.
IT FAILED.
Now my phone is stuck in a weird looking boot up loop. After a few tries I was able to get into recovery
mode. TWRP started loading, froze and crashed! Even though I am a total noob at this, I still did not panic.
I'd restart my phone by removing the battery, going into recovery mode and then wildly press every button on my phone hoping to break the loop. It worked! I chose a different save and tried it all over again. FAIL.
ON the next I wiped every bit of old data off. Chose Factory restore crossed my fiingers....it work! My phone is fine now.
Thanks to that ordeal and this thread I think I know what I did wrong even though this never happened to me. before.
1) WIPE THE DATA
2)INSTALL A COMPATABLE KERNAL FIRST
V^^^^V
Click to expand...
Click to collapse
I can not stress enough HOW IMPORTANT THE KERNEL IS!
Hmm so everyone is a now a Oriental Flash Master from the far East now huh?
What recovery is everyone using?
[updated: 07-12-2013]
Flashing Questions
So, if you just need to add something, like different Kernerl, do you have to wipe and start from scratch?
Should you.
If so, and you backup apps and data in Titanium, then what you do a full wipe, flash entire rom, and reinstall the apps and data associated therewith?
Last, I have asked this but cannot seem to get an answer.
Installed Hyperdrive 7 (also had 5.7 and 6). Rom is super smooth and fast, working like a charm. but I want Verizon Visual Voice Mail.
I tried to copy the apk file to the devices system/app directory but get permission denied message....tried to install, and get failed message....
xander45 said:
So, if you just need to add something, like different Kernerl, do you have to wipe and start from scratch?
Should you.
If so, and you backup apps and data in Titanium, then what you do a full wipe, flash entire rom, and reinstall the apps and data associated therewith?
Last, I have asked this but cannot seem to get an answer.
Installed Hyperdrive 7 (also had 5.7 and 6). Rom is super smooth and fast, working like a charm. but I want Verizon Visual Voice Mail.
I tried to copy the apk file to the devices system/app directory but get permission denied message....tried to install, and get failed message....
Click to expand...
Click to collapse
did you set the permissions for the app? That should work actually. Look at one of the apps in that directory, and set the permissions the same for the voice app. Reboot and see what happens.
Good luck.
May want to post this question also in my guide thread.
http://forum.xda-developers.com/showthread.php?t=2295557
Sorry if this is dumb, but how do I know what kernels for sure work with my device and how do I get them to my external sd card? I suppose the one that is currently on my device(how to get that to sd?), but what others?
Thanks.
Painterface said:
Sorry if this is dumb, but how do I know what kernels for sure work with my device and how do I get them to my external sd card? I suppose the one that is currently on my device(how to get that to sd?), but what others?
Thanks.
Click to expand...
Click to collapse
Please bring the question over to my thread up above. It shows also what kernels to use. We will help there.
Another noob question: so you still advise flashing a kernel even if the ROM creator says that the ROM comes with the appropriate kernel and that no extra flashing is required? I've got the Verizon Galaxy S4 variant and specifically am thinking of Dubbsy's Google Play Edition ROM.
Sent from my SCH-I545 using Tapatalk 2
theoneknownasbob said:
Another noob question: so you still advise flashing a kernel even if the ROM creator says that the ROM comes with the appropriate kernel and that no extra flashing is required? I've got the Verizon Galaxy S4 variant and specifically am thinking of Dubbsy's Google Play Edition ROM.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
You would flash the rom, and after, flash your verizon kernel, simple as that.
Here's the story in short,
I bought a new LGOG a week ago.
Rooted it.
Running on stock 4.1.2 Jellybean , AT&T(unlocked for use with any operator).
Now , today I installed freegee and updated it. Took a backup of my EFS , and copied it in my external MMC.
Apart from that also attached the freegee with my dropbox account.
Now , I tried to install CWM recovery , but it seems that there was some sort of problem with download of CWM , as it was taking eternity. I waited for few minutes but then I rebooted the phone.
The phone actually didn't booted up fine. It's now stuck at LG logo , followed by a Google logo afterwards at the beginning with padlock symbol.
The logo stays there for a second and then the phone shuts down.
I panicked when I saw this , realizing that this may be a hard brick. Now I tried combination of volume keys , and it seems that it brought up a menu on the screen , with couple of options and information.
The options available are :
Start-
PowerOff-
Recovery Mode-
Restart boot loader-
The info available below are :
Fastboot mode
product_name : mako
variant -mako 16gb
hw version : rev_10 (88)
bootloader version : makoz10f
baseband version : n/a
carrier info : none.
serial number : 05959*******98de7**
signing- production
secure boot- enabled
lock state - unlocked
When I select reboot recovery , it reboots and then same as stated above. Seems as if the recovery is either not installed properly or is not working.
I was wondering that whether this is a complete brick or is there any chances of this being fixed ??
PS There's no warranty , it's an imported set from USA . SO cant avail it here .
A help would be really appreciated , willing to donate few bucks , if things work.
http://forum.xda-developers.com/showthread.php?t=2230994
Read carefully before attempting to use it.
You can also read this thread, I just helped another person: http://forum.xda-developers.com/showthread.php?t=2556006
Let me know if you have questions.
aedren said:
You can also read this thread, I just helped another person: http://forum.xda-developers.com/showthread.php?t=2556006
Let me know if you have questions.
Click to expand...
Click to collapse
Thanks for your immediate reply Guys. That sounds really helpful.
It seems zombiegeek was able to fix the phone , and seems mine phone is in similar state.
I am going to go through the LGPNST and will see if that works. Searching for the tutorial thread on it.
optimusv45 said:
http://forum.xda-developers.com/showthread.php?t=2230994
Read carefully before attempting to use it.
Click to expand...
Click to collapse
I am going to go through it. Thanks for sharing.
EDIT : Successfully booted into Download mode By holding both the volume keys ( when device was completely switched off) and then plugging it into the PC using data cable.
It went straight to download mode.
Started LGNPST. Made sure that it detected my device. Registered LS970.dll file use rgsvr32.
Selected the DLL and BIN , and it went to 67% progress after start .
Rebooted , and went into boot loop.
I tried the same procedure again , but this tie with ATLBin instead of original Bin.
It rebooted and went into TWRP mode.
Finally a sigh of relief , as It booted into recovery.
Followed the steps as mentioned in the thread above. It worked!!
--------------
Haven't installed any ROMS yet.
optimusv45 said:
http://forum.xda-developers.com/showthread.php?t=2230994
Read carefully before attempting to use it.
Click to expand...
Click to collapse
same thing happened to my phone. Use freeGee to unlock and download cwm
but cwm download failed and have the same google logo and options.
just do the lgnst to stock.
Now I root my phone again. and not sure what should I do next.
so should I use the E970 Original TeenyBin to unlock bootloader and install cwm?
thanks
laofan said:
same thing happened to my phone. Use freeGee to unlock and download cwm
but cwm download failed and have the same google logo and options.
just do the lgnst to stock.
Now I root my phone again. and not sure what should I do next.
so should I use the E970 Original TeenyBin to unlock bootloader and install cwm?
thanks
Click to expand...
Click to collapse
Try the original teenybin, I think it includes twrp recovery. Don't worry about cwm. After flashing the bin boot into recovery and flash a rom. Again read the teenybin thread carefully and make sure you understand first.
PS. Original bin didn't work for me I had to use the other one. So if the same happens don't freak out.
optimusv45 said:
Try the original teenybin, I think it includes twrp recovery. Don't worry about cwm. After flashing the bin boot into recovery and flash a rom. Again read the teenybin thread carefully and make sure you understand first.
PS. Original bin didn't work for me I had to use the other one. So if the same happens don't freak out.
Click to expand...
Click to collapse
Yeah , I also want to stay away from CWM as long as TWRP is there.
What I am confused about is that if we flash the original JB bins from AT&T , will it leave the bootloader unlocked with TWRP recovery ??
All I need is Stock JB , with unlocked bootloader and TWRP recovery.
You said that original bins , didn't worked . DId you mean you used the ALTBin or something else ?
Rishi. said:
Yeah , I also want to stay away from CWM as long as TWRP is there.
What I am confused about is that if we flash the original JB bins from AT&T , will it leave the bootloader unlocked with TWRP recovery ??
All I need is Stock JB , with unlocked bootloader and TWRP recovery.
You said that original bins , didn't worked . DId you mean you used the ALTBin or something else ?
Click to expand...
Click to collapse
Yes, your bootloader will be unlocked and you will have twrp. Teenybin will not give you a working rom, it updates your phone to the newest software and give you a recovery. I think there is a bin that will recovery your phone to stock jb, you will have to look for it on the teenybin thread. Btw stock jb battery life is quite bad and there are quite a few stable 4.3 roms to choose from. Yes, I used altbin but that's just my phone. Original bin may work for you.
@Rishi.
here is the bin I use to go back to stock using LGNPST
http://forum.xda-developers.com/showthread.php?t=2219953
optimusv45 said:
Yes, your bootloader will be unlocked and you will have twrp. Teenybin will not give you a working rom, it updates your phone to the newest software and give you a recovery. I think there is a bin that will recovery your phone to stock jb, you will have to look for it on the teenybin thread. Btw stock jb battery life is quite bad and there are quite a few stable 4.3 roms to choose from. Yes, I used altbin but that's just my phone. Original bin may work for you.
Click to expand...
Click to collapse
Actually original TeenyBin , didn't worked in my case either.I had to flash the ALternative bins to make the TWRP work.It went into bootloop with original teeny bin , alt one worked though.
Good that the recovery is working now.
As you mentioned that the battery on stock Jb is bad , so I am going to leave that. But Can you confirm any 4.3/4.1 stable rom that has no issues whatsoever. ??
Rishi. said:
Actually original TeenyBin , didn't worked in my case either.I had to flash the ALternative bins to make the TWRP work.It went into bootloop with original teeny bin , alt one worked though.
Good that the recovery is working now.
As you mentioned that the battery on stock Jb is bad , so I am going to leave that. But Can you confirm any 4.3/4.1 stable rom that has no issues whatsoever. ??
Click to expand...
Click to collapse
The issues I encounter is insignificant comparing to how much benefit I gain. I run houstonns PA 3.99 RC 2 Adreno build . battery a lot better, less heat, deep sleep great, always wake up, fast and smooth, theme enabled too. Link for it http://forum.xda-developers.com/showthread.php?t=2228880 cm10.2 stable is also out. Bear in mind no one is gonna promise you you won't run into some issues and the stock rom isn't trouble-free either. If you are worried then you can just stick with stock for now. I honestly do like the stock rom, I think it looks great. Maybe eventually your curiosity will drive you to try custom roms.
PS: you can get stock running, make a backup, and then try some roms. Also now you know you have teenybins on your side, you should feel quite safe trying roms. Go with big name first , houstonns work is very good.
optimusv45 said:
The issues I encounter is insignificant comparing to how much benefit I gain. I run houstonns PA 3.99 RC 2 Adreno build . battery a lot better, less heat, deep sleep great, always wake up, fast and smooth, theme enabled too. Link for it http://forum.xda-developers.com/showthread.php?t=2228880 cm10.2 stable is also out. Bear in mind no one is gonna promise you you won't run into some issues and the stock rom isn't trouble-free either. If you are worried then you can just stick with stock for now. I honestly do like the stock rom, I think it looks great. Maybe eventually your curiosity will drive you to try custom roms.
PS: you can get stock running, make a backup, and then try some roms. Also now you know you have teenybins on your side, you should feel quite safe trying roms. Go with big name first , houstonns work is very good.
Click to expand...
Click to collapse
I have had experiences with lots of custom roms , MROm , Beanstalk , MIUI , CM7 , CM10 , etc, when I was an Atrix 4g user. The Roms have excellent performance difference . MIUI was best though as it had the appeal in terms of layout.
Anyways , unless I don't try one on LGOG , I am sure I won't be able to tell the difference.
BTW , I am going to try the Official Cyanogen 10.2 first.
If you flash the 11c or 20j bin you will be back to locked bootloader and no recovery. That is why I linked to flashable zip for 20j, it should work with twrp. Sorry for not being able to reply sooner.
Rishi. said:
I have had experiences with lots of custom roms , MROm , Beanstalk , MIUI , CM7 , CM10 , etc, when I was an Atrix 4g user. The Roms have excellent performance difference . MIUI was best though as it had the appeal in terms of layout.
Anyways , unless I don't try one on LGOG , I am sure I won't be able to tell the difference.
BTW , I am going to try the Official Cyanogen 10.2 first.
Click to expand...
Click to collapse
People are reporting issue with turning off NFC. They recommend either rebooting right away after booting into the rom or flash the rom again, So keep these in mind.
optimusv45 said:
People are reporting issue with turning off NFC. They recommend either rebooting right away after booting into the rom or flash the rom again, So keep these in mind.
Click to expand...
Click to collapse
installed cm10.2 , working good . seems stable with no issues , at least none with nfc yet.
will take a backup of this and will flash the stock bin with twrp.
adfurgerson said:
If you flash the 11c or 20j bin you will be back to locked bootloader and no recovery. That is why I linked to flashable zip for 20j, it should work with twrp. Sorry for not being able to reply sooner.
Click to expand...
Click to collapse
Thanks. It seems the Flashable zip you posted is better to use , since I went through the Flashable bins(.tot) thread and realized that rooting it back after LGNPSTing was kinda of doubtful.
Have taken CM10.2 backup. Will flash the TWRP/CWM flashable stock.
hi I am having trouble registering my dll files is there anyone that can help me?
nicklefloss said:
hi I am having trouble registering my dll files is there anyone that can help me?
Click to expand...
Click to collapse
Registering ?
I can't write to the internal SD card anymore after doing a factory reset / full wipe and reflash (http://forum.xda-developers.com/tmo...ent/testing-debloated-dob1-rom-t3077507/page1).
The phone was working fine, the ROM is super fast and was perfect. Of course I had to flash the update to the "stable" version, right? No offense to the OP, I am sure it is just a random android glitch on my phone. Love the ROM.
Anyway, on a Mac and on the road traveling... In terminal I get the following error:
127|[email protected]:/ # fsck_msdos /storage/emulated/0
** /storage/emulated/0 (NO WRITE)
Invalid signature in boot block: 00002|[email protected]:/ #
Any ideas how I can fix this? The phone is running just fine less the write access to /emulated/0. I have tried SD fix from the market and various adb commands as well as the same or similar commands from the android terminal emulator.
In the process I was able to reformat my internal SD by mistake and therefore have no data backup (smart, I know). I am fine with starting from a factory baseline and reinstalling everything, I just need to know how to get there (eg. do something that will ensure remove the error above).
Any help would be appreciated as I have to get everything working 100% since the phone is my lifeline on the road (I know, which is why I flashed it on the road, right?).
Mordred said:
I can't write to the internal SD card anymore after doing a factory reset / full wipe and reflash (http://forum.xda-developers.com/tmo...ent/testing-debloated-dob1-rom-t3077507/page1).
The phone was working fine, the ROM is super fast and was perfect. Of course I had to flash the update to the "stable" version, right? No offense to the OP, I am sure it is just a random android glitch on my phone. Love the ROM.
Anyway, on a Mac and on the road traveling... In terminal I get the following error:
127|[email protected]:/ # fsck_msdos /storage/emulated/0
** /storage/emulated/0 (NO WRITE)
Invalid signature in boot block: 00002|[email protected]:/ #
Any ideas how I can fix this? The phone is running just fine less the write access to /emulated/0. I have tried SD fix from the market and various adb commands as well as the same or similar commands from the android terminal emulator.
In the process I was able to reformat my internal SD by mistake and therefore have no data backup (smart, I know). I am fine with starting from a factory baseline and reinstalling everything, I just need to know how to get there (eg. do something that will ensure remove the error above).
Any help would be appreciated as I have to get everything working 100% since the phone is my lifeline on the road (I know, which is why I flashed it on the road, right?).
Click to expand...
Click to collapse
Without wiping try reflashing the rom. If you have to flash an update to the rom to get the stable version you might just try reflashing that. If that doesn't work I hate to say it but go back into recovery and do a full wipe, system, data, and cache. Then reinstall rom again. Sometimes it's just as simple as a bad flash.
@Corwinder - thanks for that. I think I have tried variations of what you describe but tonight when I get back to the hotel I will have another go at it. What I can't figure is why when I re-flash or flash a backup it seems to write just fine. The error only seems to manifest after I boot into the OS.
Altamont - that is way south in the state isn't it?
Thanks again.
Mordred said:
@Corwinder - thanks for that. I think I have tried variations of what you describe but tonight when I get back to the hotel I will have another go at it. What I can't figure is why when I re-flash or flash a backup it seems to write just fine. The error only seems to manifest after I boot into the OS.
Altamont - that is way south in the state isn't it?
Thanks again.
Click to expand...
Click to collapse
Yeah, about 10 miles or so from the Oklahoma border. When people ask I normally tell them I'm about an hour west of Joplin, Mo. Just one more thing. Not sure if this would affect it but I assume your bootloader and modem are both OB1 versions. Did you have stock Lollipop on your phone at one time in other words? If so then the answer would be yes. I'm no developer but I see a lot of times when you need to have either the bootloader or the modem on the latest stock version.
Corwinder said:
Yeah, about 10 miles or so from the Oklahoma border. When people ask I normally tell them I'm about an hour west of Joplin, Mo. Just one more thing. Not sure if this would affect it but I assume your bootloader and modem are both OB1 versions. Did you have stock Lollipop on your phone at one time in other words? If so then the answer would be yes. I'm no developer but I see a lot of times when you need to have either the bootloader or the modem on the latest stock version.
Click to expand...
Click to collapse
I came from stock, yes, but I don't remember if I had to flash a new BL and modem to get to root (I was reflashing my wife's mega at about the same time). For arguments sake, say I am still stock (BL, modem)... what is your answer of yes to?
What is the logical next step?
Thanks again.
Mordred said:
I came from stock, yes, but I don't remember if I had to flash a new BL and modem to get to root (I was reflashing my wife's mega at about the same time). For arguments sake, say I am still stock (BL, modem)... what is your answer of yes to?
What is the logical next step?
Thanks again.
Click to expand...
Click to collapse
Was stock 4.4.2 or was it 5.0 Lollipop. The S5 does not come with Lollipop preinstalled or at least they weren't. The bootloader and modem you'd need would be in the stock Lollipop. So to be safe if you don't know if you were on stock Lollipop or KitKat then I would go here http://www.sammobile.com/firmwares/database/SM-G900T/ and download the version 5 listed. You would need to use Oden to flash that and then root. Then you could install your recovery and flash the rom.
Corwinder said:
Was stock 4.4.2 or was it 5.0 Lollipop. The S5 does not come with Lollipop preinstalled or at least they weren't. The bootloader and modem you'd need would be in the stock Lollipop. So to be safe if you don't know if you were on stock Lollipop or KitKat then I would go here http://www.sammobile.com/firmwares/database/SM-G900T/ and download the version 5 listed. You would need to use Oden to flash that and then root. Then you could install your recovery and flash the rom.
Click to expand...
Click to collapse
Thanks. 5.0 was pre-installed. Just bought it last month. It will have to wait for a few weeks until I get home (only travel with a Mac) unless you know a way to run odin on Mac.
Mordred said:
Thanks. 5.0 was pre-installed. Just bought it last month. It will have to wait for a few weeks until I get home (only travel with a Mac) unless you know a way to run odin on Mac.
Click to expand...
Click to collapse
Well since 5.0 was preinstalled you shouldn't need to restore a stock copy. But if you ever wanted to you can get Odin for a Mac here http://mac.softpedia.com/get/Developer-Tools/ODIN.shtml
Since it was preinstalled you have the current bootloader and modem. Just go into Recovery and do a full wipe. Not a factory reset. Wipe System, Data, cache, and Dalvik cache. After this you can reinstall that rom.
Re-occurance... NOT SOLVED
Corwinder said:
Well since 5.0 was preinstalled you shouldn't need to restore a stock copy. But if you ever wanted to you can get Odin for a Mac here http://mac.softpedia.com/get/Developer-Tools/ODIN.shtml
Since it was preinstalled you have the current bootloader and modem. Just go into Recovery and do a full wipe. Not a factory reset. Wipe System, Data, cache, and Dalvik cache. After this you can reinstall that rom.
Click to expand...
Click to collapse
Just wanted to say thanks for the responses. Back up and running and going through the fun task of reconfiguring everything. I did a clean wipe, all partitions, etc then flashed once and flashed again (first did not seem to take - hung at boot screen with notification light pulsing).
OK, back to square one. This time I figured I would "fix" the partition and managed to damage/change/corrupt the EFS partition. Now I am stuck with a fully functioning phone that nags about being in factory mode on every boot. Went to the efs folder and it did not have the two files to change, so I created them, still the same thing.
Thoughts? Should I flash back to stock and take it in for warranty?
Still on the road so anmy immediate help woould be appreciated.
Hi guys,
I'm new here. I didn't root my S3 yet, but I want to do it and install new rom. But first I would need your help with Rom choosing, as I'm completely blind in this matter
The thing is, I would prefer a ROM which let me choose which application I want to install on my phone and which not - check/uncheck option. This rom should be FAST and stable.
As I have no experience at all, I would like to ask you which ROM will be the best for me? Btw, it would be great if I can choose language (Polish).
Hope you will help me
Regards,
Karol
edit: sorry for typo in the topic, impossible to change it now
Hi, I am in the same boat. Stock standard international S3, but extremely slow. Ram usage on startup is 700mb.
Which rom would you guys suggest that is both stable (no bugs), and fast (using much less ram).
This is my everyday phone, I take a lot of photos, especially the camera should be functioning perfectly.
Any help would be much appreciated.
Edit: Last time I rooted and played around with these things were about 3-4 years ago with my Sony X10 mini. I am slowly getting back into it, reading up on the latest rooting apps etc.
@errolpl: Search in development subforum for 'aroma installer'. Usually these ROMs offer only system apps to choose. 3rd party user apps you'll have to install by your own. You can edit the header with edit-function.
@demozzracy: If you want full camera suport, I recommend NCS-ROM: based on last JB-firmware, but brilliant debloated. So slim, fast, battery friendly and all hardware working. I'm testing many LP-ROMs, but they are primarily newer, hardly better (for S3).
@rp158: Thank you!
I was extremely new just a few weeks back as well. I must say that my attempts on finding a solution for my slow S3 has been a rather hard and bumpy road.
To help you save some time, here is what I've gathered so far:
Last time I flashed phone firmware, a couple of years ago, it required a PC, a cable and some funky software.
Then when I flashed my S3 for the first time, about a year ago, I started out with Cyanogenmod and used their app+cable installer. I think this is still the easiest way to root the phone, and get started with custom roms. Even if you plan to use some other rom than Cyanogenmod.
When the phone is rooted you can install TWRP, simply done via an app on the appstore. TWRP is recovery firmware that can stay on the phone, even though you flash new roms. (The phone is divided into several separate sections, bootloader, recovery, actual system, and data area.... I don't even know much about it yet.) The important part is that it is extremely easy to flash new roms using this tool, and a micro SD-card.
Simply drop the rom zip file onto the card and flash them. (For some roms you need to flash some "GAPPS" as well. These are the google apps, like the play store etc. If you don't flash them you can't really use the phone for much.)
This is where the real problems start. Finding the right ROM.
The S3 is old, and only supported up to Jelly Bean for my 1GB international version, or Kitkat if you have one of the 2gb versions.
This has not stopped developers in providing both Kitkat and Lollipop to any version of the S3. However... as eager they are to provide the newest coolest features, just as lazy do they seem to be with their testing. (Sorry guys, but someone has to say it.)
So I've gone through some roms now... none of them really good.
The first Official Cyanogenmod I flashed half a year ago. I used this for almost a year.. but the camera would crash constantly, and the phone was not able to display video. For example movieclips on facebook.
Second ROM: Cyanogenmod has also stopped developing for the S3, so a few weeks back I switched to some unofficial version. It seemed to work... camera and video was ok, and everything had the nice Lollipop feel to it.
However MMS did not work. I could receive one and send one, next ones would require a reboot for them to work. The problem was brought up in the ROM Q/A tread, but the answer from the developer was: Sorry I don't use MMS so I don't really see a problem.
Third: Onto some next rom. This one was tagged STABLE. It was far from it. In fact it was even easier to discover that this rom had the same MMS problem. Because the message app would crash immediately when trying to send one.
4th attemt was the same rom, but a different kernel... still the same problem.
5th rom was Blisspop... Wau, this was beautiful! Cool webpage, Cool animations.... it was just too bad that the site is dead, and that the rom can't even run for 24 hours without the android keyboard crashing 25 times or so. Also Blisspop has OTA updates... the only problem is that it constantly says that there is a new version for the S3.. but the download fails. Apparently some bad change to the website caused this, and apparently this problem has been going on for 3 months without anyone bothering to fix it.
6th was Archidroid. The second to top ROM for the S3. It looks cool, and has many features... but just as other Lollipop ROMs, sending MMS's without error is not one of them....
I've really tried everything. People always says that the MMS problems are due to APN's not being set up correctly, doing some reboots etc.... but trust me... I've set them up so many times you wouldn't belive it.
7th. After reading this thread and rp158's recommendation of NCS-ROM I'm now running that one. Without a single thing being set up, I was able to send and receive MMS's right away.
However... now I'm stuck back at the ugly kitkat look, and Touch wiz.
tl;dr;
So what do I want to say with all this?
Get root and TWRP and start playing around with ROMs
Lollipop does not look like an option for the S3, at least not right now
Don't let yourself be fooled by nice webpages or [STABLE]-tags, or comments that say: "I've been running this since yesterday.. it's 100% stable!"
Timusius thanks a lot for that post.
Puts things in perspective.
As I said in my post, I am ok with the KitKat look, as long as it is stable, I am always on call at work, and cant afford constant phone crashes.
I am going to try the root/twrp to NCS rom in the next couple of days
@Timusius thank you for your post. You help me a lot!
S5 Sensation
errolpl said:
Hi guys,
I'm new here. I didn't root my S3 yet, but I want to do it and install new rom. But first I would need your help with Rom choosing, as I'm completely blind in this matter
The thing is, I would prefer a ROM which let me choose which application I want to install on my phone and which not - check/uncheck option. This rom should be FAST and stable.
As I have no experience at all, I would like to ask you which ROM will be the best for me? Btw, it would be great if I can choose language (Polish).
Hope you will help me
Regards,
Karol
edit: sorry for typo in the topic, impossible to change it now
Click to expand...
Click to collapse
It's 5 months already that im using S5 Sensation rom for i9300/9305 ( 4.4.4 kitkat). This rom has S5/Note4 features and works great im satisfied. No problems so far, no bugs, etc ^^
It comes with AROMA installer and lets you to choose which apps you want to install and which not.
Cooldato said:
It's 5 months already that im using S5 Sensation rom for i9300/9305 ( 4.4.4 kitkat). This rom has S5/Note4 features and works great im satisfied. No problems so far, no bugs, etc ^^
It comes with AROMA installer and lets you to choose which apps you want to install and which not.
Click to expand...
Click to collapse
How you install those rom?
Pixelzack said:
How you install those rom?
Click to expand...
Click to collapse
Device must be rooted + newest cwm recovery installed. After that you just download custom rom, move it to ur phone memory/sdcard and flash it throught recovery mode
Cooldato said:
Device must be rooted + newest cwm recovery installed. After that you just download custom rom, move it to ur phone memory/sdcard and flash it throught recovery mode
Click to expand...
Click to collapse
My phone already rooted without cwm,can i just install cwm like i did to root my phone?
Pixelzack said:
My phone already rooted without cwm,can i just install cwm like i did to root my phone?
Click to expand...
Click to collapse
https://www.clockworkmod.com/rommanager here is the latest CWM versions for smartphones, but its .img file and u cannt flash it directly from Odin. U need to make .img into .tar.md5 odin flash-able file by some tools, or flash it via adb shell, etc.
Anyway here is Odin rdy .tar file , go to this link http://forum.xda-developers.com/gal...covery-clockworkmod-touch-6-0-3-2-gt-t1719744 download recovery-cwmtouch-6.0.3.2-GTI9300.tar and flash it via Odin / Download mode.
Cooldato said:
https://www.clockworkmod.com/rommanager here is the latest CWM versions for smartphones, but its .img file and u cannt flash it directly from Odin. U need to make .img into .tar.md5 odin flash-able file by some tools, or flash it via adb shell, etc.
Anyway here is Odin rdy .tar file , go to this link http://forum.xda-developers.com/gal...covery-clockworkmod-touch-6-0-3-2-gt-t1719744 download recovery-cwmtouch-6.0.3.2-GTI9300.tar and flash it via Odin / Download mode.
Click to expand...
Click to collapse
Can I use this one?
http://forum.xda-developers.com/gal...covery-clockworkmod-touch-6-0-3-2-gt-t1719744
Pixelzack said:
Can I use this one?
http://forum.xda-developers.com/gal...covery-clockworkmod-touch-6-0-3-2-gt-t1719744
Click to expand...
Click to collapse
Sure, thats what i linked you above.
Cooldato said:
Sure, thats what i linked you above.
Click to expand...
Click to collapse
Hahaha Thanks dude for helping noob like me
Pixelzack said:
Hahaha Thanks dude for helping noob like me
Click to expand...
Click to collapse
No problem Feel free to poke me if u meet some troubles ^^
Cooldato said:
No problem Feel free to poke me if u meet some troubles ^^
Click to expand...
Click to collapse
How to install this?
http://forum.xda-developers.com/galaxy-s3/development/i9300-to-n00t-bring-lte-fun-to-3g-t2886574
just need some detailed guide xD
Pixelzack said:
How to install this?
http://forum.xda-developers.com/galaxy-s3/development/i9300-to-n00t-bring-lte-fun-to-3g-t2886574
just need some detailed guide xD
Click to expand...
Click to collapse
1. Install ClockworkMod(or PhilZ) recovery
2. Put ROM on your SD card
3. Enter recovery mode
4. Perform a full data wipe(except you're running previous versions of back-to-n00t)
5. Flash ROM
6. Flash SuperSU
Cooldato said:
1. Install ClockworkMod(or PhilZ) recovery
2. Put ROM on your SD card
3. Enter recovery mode
4. Perform a full data wipe(except you're running previous versions of back-to-n00t)
5. Flash ROM
6. Flash SuperSU
Click to expand...
Click to collapse
perform a full data wipe means "Factory reset"?
How to flash rom? It's included in the recovery mode?
How to flash SuperSU?
Pixelzack said:
perform a full data wipe means "Factory reset"?
How to flash rom? It's included in the recovery mode?
How to flash SuperSU?
Click to expand...
Click to collapse
yeah this means doing a "Factory reset", must be done throught Recovery mode, wipe data, wipe cache, wipe dalvik cache.
Put ROM on your SD card, then enter Recovery Mode by pressing Home + Volume UP + Power buttons and ull have smth like:
Install Zip -> Choose Zip from /Storage/Sdcard (External SDcard) , Search for ur ROM file and start flashing :X
Flash the SuperSu .zip file same way as flashing ROM.