I have a problem with my 16GB Galaxy Tab 10.1 in that for some reason, while trying to pick up a WiFi signal from my Sky Broadband router (which none of my other WiFi devices has any problems picking up a signal from), the WiFi option seems to be stuck on the "Turning On" message and I don't know how to get it unstuck so that I can pick up a WiFi signal again from any device.
If anybody has any suggestions (I'm already looking at trading it in for a Asus Transformer Pad Infinity) to fix it, I'd be very grateful for them.
I had a similar problem. It occurred after using rom manager to install cwm on stock rooted rom and a factory reset fixed the problem for me, did you try it?
Sent from my amazing 10.1 galaxy tab
Panos_dm said:
I had a similar problem. It occurred after using rom manager to install cwm on stock rooted rom and a factory reset fixed the problem for me, did you try it?
Sent from my amazing 10.1 galaxy tab
Click to expand...
Click to collapse
Sorry for the late reply.
I haven't tried it because I didn't know how to back up everything on my Galaxy Tab 10.1 to do so.
My problem occured weeks after I installed CWM on my Galaxy Tab 10.1
Also, does anybody else know if there's an alternate way to fix this problem without needing a factory reset?
Try to flash a different kernel. Odin or cwm doesn't matter. And you won't lose data!
Sent from my amazing 10.1 galaxy tab
Panos_dm said:
Try to flash a different kernel. Odin or cwm doesn't matter. And you won't lose data!
Sent from my amazing 10.1 galaxy tab
Click to expand...
Click to collapse
Thanks for the advice! What's the best kernel to use as I don't have a custom ROM on my Tab 10.1 because all I did was just root it, nothing more.
Here: http://droidbasement.com/db-blog/
But sorry to say it but I don't think you will avoid wipe data. I could be wrong but wiping fixes almost all problems...
Sent from my amazing 10.1 galaxy tab
Panos_dm said:
Here: http://droidbasement.com/db-blog/
But sorry to say it but I don't think you will avoid wipe data. I could be wrong but wiping fixes almost all problems...
Sent from my amazing 10.1 galaxy tab
Click to expand...
Click to collapse
I just hope I don't have to do a wipe as it would be a pain in the ass to have to do so (It's stuff like this plus the fact that I'm on my third Galaxy Tab 10.1 due to all the constant problems I've had with them that's making me switch to the Transformer Pad Infinity when it comes out!).
What's the best way of doing a kernel installation with this as I've never done one before? Also, how do I do a complete backup of the device?
I've installed the kernel via CWM after doing a wipe (and I did a backup in ROM Manager as well as via Titanium Backup AND backed up everything possible to my hard drive) and now my device is stuck on the Galaxy Tab 10.1 boot screen! (The one which says "Samsung GALAXY Tab 10.1" on it)
Does anybody have any suggestions on how to fix it?
UPDATE: I also can't switch it off using the Power button as well!
Did you flash the correct kernel? There are different kernels for ics and hc and they are different for every device as well. Get into recovery and wipe dalvik cache and cache.
Since you wiped the data, the best solution is still to go here:
http://www.sammobile.com/firmware/?page=3&t=3&o=1#osa.
Download your stock firmware, flash it via odin, root again and restore everything with titanium!
Sent from my amazing 10.1 galaxy tab
Panos_dm said:
Did you flash the correct kernel? There are different kernels for ics and hc and they are different for every device as well. Get into recovery and wipe dalvik cache and cache.
Since you wiped the data, the best solution is still to go here:
http://www.sammobile.com/firmware/?page=3&t=3&o=1#osa.
Download your stock firmware, flash it via odin, root again and restore everything with titanium!
Sent from my amazing 10.1 galaxy tab
Click to expand...
Click to collapse
It looks like I used the ICS kernel for the 3G version (which is the version of the Galaxy Tab 10.1 that I have) instead of the HC version by mistake!
In the meantime, should I wait until the battery drains completely and try to recharge it to see if your advice works?
With the backup that I made with Titanium, I take it that's still safe on the device if I can get back into it?
You can flash without draining the tab. Also, everything in your /sdcard (music, videos, cwm backups, etc) don't get wiped. What you loose is only the apps you have installed. Just if you use odin flash only the Rom and not a pit file, as it will COMPLETELY wipe the tab, including sdcard.
Sent from my amazing 10.1 galaxy tab
Panos_dm said:
You can flash without draining the tab. Also, everything in your /sdcard (music, videos, cwm backups, etc) don't get wiped. What you loose is only the apps you have installed. Just if you use odin flash only the Rom and not a pit file, as it will COMPLETELY wipe the tab, including sdcard.
Sent from my amazing 10.1 galaxy tab
Click to expand...
Click to collapse
I'm just downloading the firmware right now and I was wondering which option in the Files section on Odin do I use to flash the firmware. (Sorry for being such a noob, but it's been quite a while since I've used it to flash a ROM and I can't remember what the option was to do so)
In the meantime, thank you for answering my questions (I'm still going to get me a Asus Transformer Pad Infinity in any case) and showing patience to someone who's had nothing but problems with the device since he got his first one a few months back.
UPDATE: I drained the battery and recharged it, but from the looks of things it's still stuck on the same screen and still won't let me switch it off! It's a shame that I've been having so much with the Galaxy Tab 10.1 even though I've forgiven it for its lack of microSD slot.
Hey no prob. That's the best way I can contribute here for the moment. I am glad that my advices are somewhat useful to you.
Here is a complete guide to restock the tab:
http://www.teamovercome.net/p7500/?page_id=5
You don't have to use the provided stock rom, since you are downloading your own! Just skip the pit part, unless you have backed up everything in your hard drive. I don't know the exact options, since I have never used odin for the tab, but it explains it all with screenshots.
I have a small favor to ask. Can you check whether the binary counter will increase after that? In theory it shouldn't be affected, because you flash a stock rom but I would be grateful if you could tell me what happens.
Yeah, the only thing which bothers me too is the lack of the microsd but ok, I decided I can live with that!
Sent from my amazing 10.1 galaxy tab
Panos_dm said:
Hey no prob. That's the best way I can contribute here for the moment. I am glad that my advices are somewhat useful to you.
Here is a complete guide to restock the tab:
http://www.teamovercome.net/p7500/?page_id=5
You don't have to use the provided stock rom, since you are downloading your own! Just skip the pit part, unless you have backed up everything in your hard drive. I don't know the exact options, since I have never used odin for the tab, but it explains it all with screenshots.
I have a small favor to ask. Can you check whether the binary counter will increase after that? In theory it shouldn't be affected, because you flash a stock rom but I would be grateful if you could tell me what happens.
Yeah, the only thing which bothers me too is the lack of the microsd but ok, I decided I can live with that!
Sent from my amazing 10.1 galaxy tab
Click to expand...
Click to collapse
The device is still stuck on the screen with the Galaxy Tab logo on it and won't switch off at all! Does that mean it's unfixable or is it one of those boot loop problems that I've read about here?
I'm seriously looking at sending it off for repair or replacement if it can't be fixed.
This happened after odin? Just wait a little bit. It usually takes a while for the first boot.
Sent from my Nokia 3210
I haven't used it with Odin yet. Should I wait for it to drain fully and recharge fully before trying again?
Also, it's good to know that my data is safe and all I need to do is to root it again and reinstall my apps using Titanium Backup.
It's best to be full before you flash. If the battery is drained before the process is finished then you have a brick!! Just please check your binary counter before and after you flash the stock firmware. I really need to know this... You can see this number in the downloading mode screen. Your tab will be fine...good luck!
Sent from my amazing 10.1 galaxy tab
I've fully charged it up to 100% so hopefully it should be safe to try and fix the problem.
Also, I've downloaded what seems to be the latest Vodafone UK stock ROM and I take it that's the one I should be definitely using to return the device to stock?
Yes, that is correct, although it does't matter which rom you choose as long as it is for p7500. I am waiting for an update with good news!
Sent from my amazing 10.1 galaxy tab
Sorry I haven't updated in a while, been kept busy.
I've plugged it into the laptop after charging it up to 100% but it's not being recognised by the laptop at all even after reinstalling the USB drivers.
I've managed to get into the screen with the Android Downloading icon on the right and the folder logo on the left. What should I do next?
Related
I'm not sure if this is the right place to ask this so sorry if it isn't.
A few weeks ago my little brother decided to install clockworkmod on my phone for some reason. He however though I had a Samsug galaxy S but I have a Samsug galaxy S advance. So he decided to install clockworkmod for samsung galaxy s on my pone. Ever since he did that my phone has been crashig every 10 minutes and has just been slower in performance.
I don't know anythig about how rooting and all this work and I just can't figure out how to remove it.
Can anyone help me?
manananana said:
I'm not sure if this is the right place to ask this so sorry if it isn't.
A few weeks ago my little brother decided to install clockworkmod on my phone for some reason. He however though I had a Samsug galaxy S but I have a Samsug galaxy S advance. So he decided to install clockworkmod for samsung galaxy s on my pone. Ever since he did that my phone has been crashig every 10 minutes and has just been slower in performance.
I don't know anythig about how rooting and all this work and I just can't figure out how to remove it.
Can anyone help me?
Click to expand...
Click to collapse
The right place would be the device spcific forum for the sgs+.
But anyway.. Backup all your files, download the firmware for your phone (on sammobile for example) and flash it via odin. (You can get odin on many websites, just google.)
There are many tutorials how to use odin, so view one of them.
Then your phone should work correctly again. But it's completly wiped, so all your files would be deleted, except the ones located on your sd. So again, backup everything like sms, contacts etc.
Good luck.
Sent from my GT-I9100 using xda app-developers app
use this link http://forum.xda-developers.com/showthread.php?t=1945806
If anyone has the time i would like some help on how to flash my Note without bricking the phone. Reason i ask, is because i have already bricked it!! Sent it off to mobiletechvideos.com who unbricked it so now i'm back! I love the phone alot just hate stock rom and how slow it is. I would like to use a rom that is able to overclock? I've read about the sauron rom but i can't tell if it's out dated or if there is something better now?
I'm not a noob when it comes to rom's, Htc aria, samsung captivate, inspire, then the htc one x - i've all rom'd them but now i'm stump'd. The first go around, i flashed the rom and everything went thru fine. When i booted up the phone - Nothing changed!? so i find another rom, flashed it and the phone bricked. Tried jig everything else and to no avail. So 65$ later i'm back with the stock rom and it's rooted. Anyhow, here is the info i'm sure you guys are wanting to give me a hand!
Model Number
SAMSUNG-SGH-I717
Andriod Version
2.3.6
Baseband Version
I717UCLF6
Kernel Version
2.6.35.11
Build Number
GINGERBREAD.UCLA1
Cliff Notes -- Hard bricked trying to flash rom, Main goal want to overclock, battery life not issue. Please help flashing :angel:
do you have a custom recovery ? like cwm or the other one ( ive only had my note a week)
i would start with that..
If I were you (and I fully understand that I am not nor anyone else on here...) I would:
1. Install Samsung Kies and drivers to my laptop.
2. Start Samsung Kies and plug in the phone via USB cable.
3. Update the phone's OS via Kies to ICS. You won't brick it that way.
4. Give stock ICS a chance and if you still feel it's too slow for you (rolling eyes), flash a custom ROM/kernel.
nutpants said:
do you have a custom recovery ? like cwm or the other one ( ive only had my note a week)
i would start with that..
Click to expand...
Click to collapse
Yep, already have clockwork mod, That's no big deal.
BlackZenith said:
If I were you (and I fully understand that I am not nor anyone else on here...) I would:
1. Install Samsung Kies and drivers to my laptop.
2. Start Samsung Kies and plug in the phone via USB cable.
3. Update the phone's OS via Kies to ICS. You won't brick it that way.
4. Give stock ICS a chance and if you still feel it's too slow for you (rolling eyes), flash a custom ROM/kernel.
Click to expand...
Click to collapse
Sounds good sir i will give it a try - Meanwhile Anyone want to take a stab at walking me thru a rom that would work on my phone?
not that i have any idea what i am doing...
0 MAKE VERY SURE THE ROM YOU ARE FLASHING IS FOR YOUR PHONE... FORGET THE WORDS "note" or "galaxy" or anything else..
its the i717d or i 7100 or i 7000 that matters.. if in doubt dont do it..
1 download your cwm compatible rom (like blackstar or others) ( try to pick a recent rom no older than 2 months unless all the developers have jumped ship for the new phone)
( usually ends with a .zip) to your sd card)
2 use "android file verifier " ( from the market) to make sure your md5 hash of the download is prefect
( there SHOULD be a md5 someplace to verify the file download)
then by following info like whats found here.... http://forum.xda-developers.com/showthread.php?t=1584250 ( and that i copied and pasted)
boot into recovery by pressing volume up down,and power button at same time ( when your phone is turned off)
Select wipe data/factory reset and confirm
Select wipe cache partition and confirm
Select advanced - wipe dalvik cache and confirm
Select install zip from SD card
Select from internal SD card or wherever you placed it.
Select the ROM file and confirm.
rom will install
then AGAIN
Select wipe data/factory reset and confirm
Select wipe cache partition and confirm
Select advanced - wipe dalvik cache and confirm
boot up wait 5mins for it to boot.. dont touch it for 10 minutes after it boots
then
have fun..
dont forget to wonder if you bricked it during the first boot... that one takes the longest..
i have followed these directions drunk and sober when flashing over 20 times my new note i717d i got last week and im not bricked yet.
its the same system i used with my sgs2 i9100 for over a year and it still works..
but then dont think anything i have said here is right.
i could just be stupid and very lucky that i dont brick everything i touch but will not admit it.
READ A LOT, then READ more.. then ONE MORE TIME READ.. then flash.
BlackZenith said:
If I were you (and I fully understand that I am not nor anyone else on here...) I would:
1. Install Samsung Kies and drivers to my laptop.
2. Start Samsung Kies and plug in the phone via USB cable.
3. Update the phone's OS via Kies to ICS. You won't brick it that way.
4. Give stock ICS a chance and if you still feel it's too slow for you (rolling eyes), flash a custom ROM/kernel.
Click to expand...
Click to collapse
So after about 2 hours off and on, using different cables and google. No avail, UGH!
Samsung kies
Your device is not supported to update via samsung kies. Walked thru a few xda threads and they are saying update thru odin. Hell if i'm jumping ship to odin again, mine as well do a rom. I'm giving this 1 more shot, if it bricks i'll sell it lol!!
Mobiletechvideos most have had to do something extreme to repair your device, or they gave you one that.... never mind. Well, looks like you need to flash CWM and find a zip aligned ROM on here.
BlackZenith said:
Mobiletechvideos most have had to do something extreme to repair your device, or they gave you one that.... never mind. Well, looks like you need to flash CWM and find a zip aligned ROM on here.
Click to expand...
Click to collapse
LOL, no they did exactly what was promised. Even people who haven't bricked their device have ran into this issue!
Okay - After reading up and then watching a video on how to flash roms. Which looked exactly like what i had done before time and time again. I'm proud to say i'm ROM'D! I'm now running the blackstar rom and it's very zippy love it to death. Would like to have tried ICS 4.0.4 but took the plunge and happy with the turn out.
I've always came to this site for help but never made an account and you guys are too nice! Hopefully i can/could help someone else out down the road. Until then i'm going to enjoy not being so slow! Thanks!:good:
Its because you have a LF6 modem. Its not the modem that GB had. The Kies upgrade only works if your phone is stock.
You can use the kies emergancy firmware upgrade option.
Is not black star 4.04?
nutpants said:
Is not black star 4.04?
Click to expand...
Click to collapse
1st post says GB.
rangercaptain said:
1st post says GB.
Click to expand...
Click to collapse
First post here or first post of black star ?
written in your mud with my stick
Your first post.
The latest black star is based on the ics 4.0.4 firmware from Singapore
studacris said:
Your first post.
The latest black star is based on the ics 4.0.4 firmware from Singapore
Click to expand...
Click to collapse
The original Tom I started with was 2.3.6 since lies wouldn't let me update to ice 4.0.4 I jumped the gun and flashed blackstar. While it is a great rom. I'm thinking of trying more while I got my feet wet.
1Note said:
The original Tom I started with was 2.3.6 since lies wouldn't let me update to ice 4.0.4 I jumped the gun and flashed blackstar. While it is a great rom. I'm thinking of trying more while I got my feet wet.
Click to expand...
Click to collapse
I've been flashing two roms a day looking for something that supports total recall and underclocking, with a network mode menu that has lte on it.
I think I am out of luck.and I have forgotten some roms so I may flash everything again and keep notes...
It's research not an addiction.
written in your mud with my stick
Stage 1 of acceptance is denial
studacris said:
Stage 1 of acceptance is denial
Click to expand...
Click to collapse
LOL ...
And of course my favorite ....
"Trying is the first step toward failure ".....(Homer Simpson )...(grin )
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.
(I also posted this in general Q&A)
Hi.
I made an account just to post this because I honestly don't know where else to go. I'm new at rooting so please explain everything in simple terms.
I rooted my Verizon Galaxy S4 a few days ago and everything was great. I did a few soft mods with Xposed and Wanam and everything was still great. I thought I would wait until the weekend to do some custom ROM flashing and whatnot since I knew it was a time consuming process.... MAN was it a time consuming process. Mainly because I messed up my whole phone.
I installed Safestrap v3.71 (CWM Recovery wasn't compatible with my phone or something...?) and flashed Hyperdrive RLS13 to my MK2 build Verizon Galaxy S4 on ROM Slot 1. It worked great but I saw that all my free space in my internal memory was taken up because of my Stock ROM being too large. So I proceed to wipe data from the Stock ROM slot after backing it up and putting the backup on my computer. I factory reset the Stock ROM and hit reboot. I think the error occurred because I forgot to reselect the ROM Slot 1. Or maybe factory resetting like that isn't supposed to happen... I don't know.
But now my phone won't boot up all the way. It's stuck on the Samsung Galaxy S4 screen. I tried booting into recovery but it just takes me to the stock recovery. Apparently Safestrap is unable to be booted into directly or something... so i tried to factory reset from there and it did.
Now my phone won't even go into recovery mode. If I try it will say "Recovery Booting" but the screen will go black and reboot again and get stuck on the Samsung Galaxy S4 screen.
I HAVE LOOKED EVERYWHERE ON THE INTERNET and nothing directly applies to me or is simple enough for me to understand... I am currently downloading the NO-WIPE method stock ROM or something for what I think applies to me from http://forum.xda-developers.com/show....php?t=2578209 so I can put that into Odin which I downloaded (but don't really know how to use) and it says it will take 3 hours to download. GREAT. More waiting. I would like something quicker if possible.
SO MY QUESTION IS:
WHAT THE HELL DO I DO???
Specs of my phone again:
Verizon Galaxy S4 SCH-1545
Android 4.3
Build MK2
Kernel Mk2
(I'm not even sure what all that means but there it is)
ALL HELP WILL BE GREATLY APPRECIATED BECAUSE I DON"T KNOW WHAT TO DO!
Thank you. So. Very. Much.
the immunity said:
(I also posted this in general Q&A)
Click to expand...
Click to collapse
Why? It belongs here.. Oh well.
the immunity;49967773
I installed Safestrap v3.71 (CWM Recovery wasn't compatible with my phone or something...?) and flashed Hyperdrive RLS13 to my MK2 build Verizon Galaxy S4 on ROM Slot 1. It worked great but I saw that all my free space in my internal memory was taken up because of my Stock ROM being too large. So I proceed to wipe data from the Stock ROM slot after backing it up and putting the backup on my computer. I factory reset the Stock ROM and hit reboot. I think the error occurred because I forgot to reselect the ROM Slot 1. Or maybe factory resetting like that isn't supposed to happen... I don't know.
But now my phone won't boot up all the way. It's stuck on the Samsung Galaxy S4 screen. I tried booting into recovery but it just takes me to the stock recovery. Apparently Safestrap is unable to be booted into directly or something... so i tried to factory reset from there and it did.
Now my phone won't even go into recovery mode. If I try it will say "Recovery Booting" but the screen will go black and reboot again and get stuck on the Samsung Galaxy S4 screen.
I HAVE LOOKED EVERYWHERE ON THE INTERNET and nothing directly applies to me or is simple enough for me to understand... I am currently downloading the NO-WIPE method stock ROM or something for what I think applies to me from [url said:
http://forum.xda-developers.com/show....php?t=2578209[/url] so I can put that into Odin which I downloaded (but don't really know how to use) and it says it will take 3 hours to download. GREAT. More waiting. I would like something quicker if possible.
SO MY QUESTION IS:
WHAT THE HELL DO I DO???
Specs of my phone again:
Verizon Galaxy S4 SCH-1545
Android 4.3
Build MK2
Kernel Mk2
(I'm not even sure what all that means but there it is)
ALL HELP WILL BE GREATLY APPRECIATED BECAUSE I DON"T KNOW WHAT TO DO!
Thank you. So. Very. Much.
Click to expand...
Click to collapse
You're going to have to wait for the no-wipe ROM to load. Sorry, but there's not much else you can do.
Given that you're a newbie, I'd start with installing Samsung Kies and using that to recover, but that'll take hours as well.
k1mu said:
Why? It belongs here.. Oh well.
You're going to have to wait for the no-wipe ROM to load. Sorry, but there's not much else you can do.
Given that you're a newbie, I'd start with installing Samsung Kies and using that to recover, but that'll take hours as well.
Click to expand...
Click to collapse
Thanks man. I actually just got it to work. Do you know why this problem happened in the first place so I can avoid it next time?
the immunity said:
(I also posted this in general Q&A)
Hi.
I made an account just to post this because I honestly don't know where else to go. I'm new at rooting so please explain everything in simple terms.
I rooted my Verizon Galaxy S4 a few days ago and everything was great. I did a few soft mods with Xposed and Wanam and everything was still great. I thought I would wait until the weekend to do some custom ROM flashing and whatnot since I knew it was a time consuming process.... MAN was it a time consuming process. Mainly because I messed up my whole phone.
I installed Safestrap v3.71 (CWM Recovery wasn't compatible with my phone or something...?) and flashed Hyperdrive RLS13 to my MK2 build Verizon Galaxy S4 on ROM Slot 1. It worked great but I saw that all my free space in my internal memory was taken up because of my Stock ROM being too large. So I proceed to wipe data from the Stock ROM slot after backing it up and putting the backup on my computer. I factory reset the Stock ROM and hit reboot. I think the error occurred because I forgot to reselect the ROM Slot 1. Or maybe factory resetting like that isn't supposed to happen... I don't know.
But now my phone won't boot up all the way. It's stuck on the Samsung Galaxy S4 screen. I tried booting into recovery but it just takes me to the stock recovery. Apparently Safestrap is unable to be booted into directly or something... so i tried to factory reset from there and it did.
Now my phone won't even go into recovery mode. If I try it will say "Recovery Booting" but the screen will go black and reboot again and get stuck on the Samsung Galaxy S4 screen.
I HAVE LOOKED EVERYWHERE ON THE INTERNET and nothing directly applies to me or is simple enough for me to understand... I am currently downloading the NO-WIPE method stock ROM or something for what I think applies to me from http://forum.xda-developers.com/show....php?t=2578209 so I can put that into Odin which I downloaded (but don't really know how to use) and it says it will take 3 hours to download. GREAT. More waiting. I would like something quicker if possible.
SO MY QUESTION IS:
WHAT THE HELL DO I DO???
Specs of my phone again:
Verizon Galaxy S4 SCH-1545
Android 4.3
Build MK2
Kernel Mk2
(I'm not even sure what all that means but there it is)
ALL HELP WILL BE GREATLY APPRECIATED BECAUSE I DON"T KNOW WHAT TO DO!
Thank you. So. Very. Much.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2606501
hey I have a similar problem, but when I go to download mode it shutdowns
codyh said:
hey I have a similar problem, but when I go to download mode it shutdowns
Click to expand...
Click to collapse
Does it go into download mode before turning off? Others have had issues like this where their power button for stuck
Hi
I have bricked my samsung galaxy tab 7 v2.2
I followed some stes found here
I rooted the phone , I noticed I had superuser icon
with odin selected pda & file CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS
Everything seemed to go alright but now the phone is in a constant loop with funny coloured lines all over the screen.
Please can some one help
Cheeers
Des
beags64 said:
Hi
I have bricked my samsung galaxy tab 7 v2.2
I followed some stes found here
I rooted the phone , I noticed I had superuser icon
with odin selected pda & file CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS
Everything seemed to go alright but now the phone is in a constant loop with funny coloured lines all over the screen.
Please can some one help
Cheeers
Des
Click to expand...
Click to collapse
Do you have a Custom Recovery? Ex: CWM,TWRP, etc
If he used the CF Autoroot, then not likely he has recovery. Best bet will be to reload the stock OS via Odin to get back to normal. You need to make sure you get the right version of the firmware though because there are different variants of the tab.
es0tericcha0s said:
If he used the CF Autoroot, then not likely he has recovery. Best bet will be to reload the stock OS via Odin to get back to normal. You need to make sure you get the right version of the firmware though because there are different variants of the tab.
Click to expand...
Click to collapse
Thanks Guys.
I don't have any recovery unfortunately. I have tried the 2 optus versions of 2.2 that i found here
but both of them just put the phone / Tab in a loop at the Samsung start up screen.
Any idea where I could find some more to try
GT-p1000 originally optus in australia firmware around 2011 I think cant be sure
Appreciate all the effort
thanks
Des
Did both versions cause lines on the screen, or just not being able to boot? It's not uncommon to need to do a factory reset after restocking with Odin, but if the screen was having issues too then that is most likely something to do with the bootloaders. Try doing a factory reset, then pull the battery, then boot into download and install the latest 2.3.6 for your tablet: http://www.sammobile.com/firmwares/3/?download=8303 . You might have to sign up, sorry, but it's the official version specifically for what you need and if your screen flickering issue IS bootloader related, then this will cure that as well.
Both rom caused the lines & I was unable to read anything in order to do the reset.
I had afriend work on this over Easter & he managed to get it working & installed kit kat my problem now is the resolution is to high
thanks for your assistance
Cheers
Beags
beags64 said:
Both rom caused the lines & I was unable to read anything in order to do the reset.
I had afriend work on this over Easter & he managed to get it working & installed kit kat my problem now is the resolution is to high
thanks for your assistance
Cheers
Beags
Click to expand...
Click to collapse
I just tried to change "ro.sf.lcd_density=160" to 240 as the screen did not look to good with tasker widgets.
It could not save so I followed he instruction to give full root access.
after changing the value it went to save for awhile then said failed.
After that the "Build.prop" was empty.
Now the phone is stuck on the Cyanogen mod front screen.
Is there a way to get back the "Build.prop" or how can I restore it?
Cheers
Beags
Easiest way is just going to be to reinstall the rom, if it is still on your storage. If you just wipe the cache and dalvik cache then reflash rom and Gapps, you should be back to normal without needing to factory reset. There are build prop editor apps in the Play Store. Would probably be a bit easier and make sure to save it correctly for you.
Out of curiousity - the lines on the screen was a bootloader issue, I'm assuming?
help and sorry!!
sorry beags64 for posting this in yours but i need a help!i have a bricked mT6573 Chang jiang G22 (one SIM) and i didn't found any compatible stock ROM for it,i can download (micromax A50,A75 into it) 100% but nothing else than black screen and vibrating!so do you know where can i find a rom for it?!thanks
techlie said:
sorry beags64 for posting this in yours but i need a help!i have a bricked mT6573 Chang jiang G22 (one SIM) and i didn't found any compatible stock ROM for it,i can download (micromax A50,A75 into it) 100% but nothing else than black screen and vibrating!so do you know where can i find a rom for it?!thanks
Click to expand...
Click to collapse
You need to start your own thread.
Yes the rom was still in storage so I reinstalled as suggested & everything back as I left it.
Thanks heaps
beags64 said:
Yes the rom was still in storage so I reinstalled as suggested & everything back as I left it.
Thanks heaps
Click to expand...
Click to collapse
Welcome! Glad all is well.