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 ?
Related
Hi there.
It seems that I can't help myself anymore.
Got a prime with JB bootlader 10.4.2.18 and TWRP 2.4.3.0 on it.
Flashed SuperSU using TWRP and, after that, tried to flash
ParanoidAndroid for my device. (pa_tf201-3.10-07MAR2013-190411.zip)
Right after starting the flashing procedure TWRP seems to crash.
(It immediately shows it's splash screen again and gets laggy.)
I also tried other TF201-JB-ROMs but it happens with any of them!
I can access TWRP and Fastboot! But I got no ROM on the device
and aint able to flash one.
After hours of searching and reading it still looks like a Option 3 brick
to me and I don't know what to do next.
Some ppl tell to write the original blob from Asus' 10.4.2.18 stock rom,
others advise against that because it will get hard-bricked. I'm stuck.
Any ideas?
Seems to be solved.
Instead of using my MicroSD-card to install the new ROM I now just
used ADB to transfer the file directly onto the device.
It worked fine for cm-10.1-20130308-UNOFFICIAL-tf201.
I'll try AndroWook_Hairy_Bean_v1.51_FINAL tomorrow, or shouldn't I?
trust me andro wook HB 1.51 is the best at all !
i tried each and every one of Roms and no one can beat HB !
if u can live without changing themes or multi user features Andro Wook is best choice for u ...
must annoying issue in other none stock based Roms is that no one of them can play movies in HW acceleration mode . ( image quality will be very lower in other modes )
u should wipe system before flashing new Roms (specially after CM Roms ) ...
its a little risky but best results will come from it !
sorry for my terrible english
marleng said:
Seems to be solved.
Instead of using my MicroSD-card to install the new ROM I now just
used ADB to transfer the file directly onto the device.
It worked fine for cm-10.1-20130308-UNOFFICIAL-tf201.
I'll try AndroWook_Hairy_Bean_v1.51_FINAL tomorrow, or shouldn't I?
Click to expand...
Click to collapse
Hello. The problem is with twrp 4.2.3.0 version. Push 4.2.2.0,your problem will end.
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.
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
dar101978 said:
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
Click to expand...
Click to collapse
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
CalcProgrammer1 said:
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
Click to expand...
Click to collapse
Thanks thats what i did, I just basically had to use KIES to use the emergency recovery, then root my phone again. My question is what version of TWRP causes this? cause i used the newest version i could find off GOO. My other concerne is, will it accept or be safe to use a custom ROM? Well i gues ill find out :laugh: THANKS AGAIN!
Everyone with the sgh-i717 is having problems with the latest TWRP and the most stable version is 2.5.0.0. Go with that one or you'll be starting all over again I imagine. And don't just stop at the download link in the OP's, read the thread and find out what's going on. The problems with TWRP have been going on for a while and the development threads have a lot of comments about the latest build causing problems. Good luck! :good:
Ok, so I've rooted and put custom roms on numerous phones. I've been trying to put a custom recovery, twrp or cwm, whatever, on my wife's phone, but have got a wall. I know for sure, 100% that I am rooted. I tired to install twrp and cwm via their respective apps, ends up in either bootloop trying to boot into recovery (and FYI, the screen shows that a custom recovery is installed, just doesn't load into recovery and restarts). And tried both via Odin, but got the same result. Have never ran into this problem before with any of my phone's, all of the galaxy's and Galaxy Note's since the S2. Any help would be greatly appreciated. Thanks homies!
Just to add, yes I made sure double checked, triple checked that I was installing the correct recovery for the phone model. Also, she has done all the ota updates that sprint has pushed as of last week (2/9/15).
Psychotic-Cerebellum said:
Ok, so I've rooted and put custom roms on numerous phones. I've been trying to put a custom recovery, twrp or cwm, whatever, on my wife's phone, but have got a wall. I know for sure, 100% that I am rooted. I tired to install twrp and cwm via their respective apps, ends up in either bootloop trying to boot into recovery (and FYI, the screen shows that a custom recovery is installed, just doesn't load into recovery and restarts). And tried both via Odin, but got the same result. Have never ran into this problem before with any of my phone's, all of the galaxy's and Galaxy Note's since the S2. Any help would be greatly appreciated. Thanks homies!
Just to add, yes I made sure double checked, triple checked that I was installing the correct recovery for the phone model. Also, she has done all the ota updates that sprint has pushed as of last week (2/9/15).
Click to expand...
Click to collapse
OK, from your post it looks like you have done this before. To be sure lets go through the motions one more time.
Your device is updated to 4.4.4 NK4 the latest KitKat version. It's rooted you have supersu icon and run a root checker. First download again ( in case you got a bad download ) a copy of Philz CWM version 6.48.4 here is the link https://goo.im/devs/philz_touch/CWM_Advanced_Edition/hlte/ use "phil'z_touch_6.48.6-hlte.tar.md5" . I like to use odin version v1.85 it's little older but very stable, here is a link https://mega.co.nz/#!oA5xzTAL!LXoVWB...ZlOMSWdRGVX6Uo now flash the .tar file with odin. Make sure you let device boot up on it's own back to the OS, do not pull the cable and boot the device yourself. Then try and boot into recovery.
If it bootloops again, I would backup all your data to the PC desktop, and then do a factory reset get back to bone stock ( that means when your in download mode it says Samsung Official status not custom ) so many times I have seen folks with an unrooted device where the bootloader still says custom and you end up with a dirty flash or worse. It may take a couple factory resets to get back to stock, it doesn't always take the first time. When I flash a custom rom and then decide to go back to stock, I flash the rom two or three times to make sure I'm bone stock.
If the factory reset doesn't work you may have to flash a new stock NK4 OS. Then root again and install the recovery. Here is my thread with all the info you need http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 , Enjoy !!!
Thanks for taking the time to give me a detailed response. Sounds like I'm gonna have to wait till Wednesday or Thursday when im off work and have some time to do this, but yeah, I was thinking maybe just a factory reset, but I'll use your links and try it one more time first. I'll let ya know. Thanks again
Do you have another link to the older Odin (1.85).the link says the file isn't there... Thanks again
Never got to test it out, but she didn't really want a custom rom anyway, just the WiFi hotspot, and I finally found a method that works, big shout out to idone for his awesome app. If anyone else is looking for WiFi hotspot without root that sees this, check out his tread in the apps and themes, for this phone. Worked like a charm. Thanks again jimzweb1. Much appreciate the reply!
Psychotic-Cerebellum said:
Never got to test it out, but she didn't really want a custom rom anyway, just the WiFi hotspot, and I finally found a method that works, big shout out to idone for his awesome app. If anyone else is looking for WiFi hotspot without root that sees this, check out his tread in the apps and themes, for this phone. Worked like a charm. Thanks again jimzweb1. Much appreciate the reply!
Click to expand...
Click to collapse
Awesome, Ya idone is the man when it comes to enabling the mobile hotspot be careful what you click with app. I will correct that link. Thanks
Psychotic-Cerebellum said:
Ok, so I've rooted and put custom roms on numerous phones. I've been trying to put a custom recovery, twrp or cwm, whatever, on my wife's phone, but have got a wall. I know for sure, 100% that I am rooted. I tired to install twrp and cwm via their respective apps, ends up in either bootloop trying to boot into recovery (and FYI, the screen shows that a custom recovery is installed, just doesn't load into recovery and restarts). And tried both via Odin, but got the same result. Have never ran into this problem before with any of my phone's, all of the galaxy's and Galaxy Note's since the S2. Any help would be greatly appreciated. Thanks homies!
Just to add, yes I made sure double checked, triple checked that I was installing the correct recovery for the phone model. Also, she has done all the ota updates that sprint has pushed as of last week (2/9/15).
Click to expand...
Click to collapse
That's the problem Knox security is getting harder flash engineering boot loader again then try rashr in app store to flash philz
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.