Related
Please help!!! Ok, let me start by saying that I've successfully rooted, soft bricked, and unbricked my previous S2 & Note 2. I just got an S4 about a month ago and decided to root today. While I was setting it up a month ago I updated to mf3 and had completely forgotten.
I did the new root via terminal and was successful. Installed SU just fine. I gave root to xplorer and switched out my build.prop for the sprint sg4 to install google wallet (the one I could actually use nfc with). Installed fine, then got an error about not having sufficient permission inside gw. I rebooted and somehow su lost binary. I've tried everything I could look up. I can't uninstall su without root, and I can't open it without the binaries. I can't replace the build.prop, or edit it. I can pull via adb but can't push. Can't do it through adb shell either. Can't use odin (cuz mf3), can't use mobile odin, can't use goo either. I'm lost.
It hasn't caused any serious problems but I'd like to have my at&t build.prop back. (Fyi, I did back it up before I did it. So I have it, I just can't replace it.)
Can this be fixed? Am I f'ed? Do I have to live with it til someone gets around the bootloader? Or do I have to take it back to bestbuy to replace it? (And if I do, Will they replace it?)
Update: BestBuy will not replace it.
Go to a best buy that has the Samsung experience. They won't replace the phone but they can flash the mf3 firmware and get you back to like new again. You'll have to sweet talk them.
You can also try visiting an att store to have them flash mf3.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Thanks for the posts guys. Really appreciate it! I ended up trying to do an emergency flash via Kies. After a couple of dozen times of it failing to download (too slow) my phone ended up with the yellow triangle and said the firmware upgrade failed and to connect it to Kies. Luckily that showed that I wasn't rooted so I took it to a Samsung experience kiosk and they had me up and running in 10 minutes. Needless to say I'm not rooting again til there's a recovery for MF3!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Jd1639, the girl I spoke to yesterday wouldn't reflash it for me. She could tell it wasn't stock because of the 4G signal.
I got lucky today with Kies failing! The hubs would've killed me!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
silrosriv said:
Jd1639, the girl I spoke to yesterday wouldn't reflash it for me. She could tell it wasn't stock because of the 4G signal.
I got lucky today with Kies failing! The hubs would've killed me!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I had the exact same experience with Best buy. The lady, as friendly as she was, was unhelpful in my situation. She kept saying they do not want to flash something that has been altered in any way just in case it gets bricked... it is to prevent liability on their part (which I can kind of understand). I even told her I'd be glad to sign a waiver to assume full liability if something goes wrong. She didn't go for it... Unfortunately, I'm stuck at the moment, I'm searching out ways to restore my build.prop from either adb sideload via the stock recovery or through ODIN somehow... There was a thread discussing a fix for the yellow triangle that required ODIN to flash some files (5 or so)... So, I was thinking if I can get the same type of thing setup for build.prop, I'd be in good shape... I just have 0 experience with doing this stuff, so I'm still reading/learning how it all works.
Dusty, I think if you're on MF3 nothing is going to work. You can try an emergency firmware flash through Kies. If you're at the yellow triangle and it's telling you to connect it to Kies then look at the top and see if it says that you're running Samsung official with write block enabled. If it does then take it back to the Samsung experience kiosk and tell them your PC froze during an update and that's what broke your phone.
Hope it helps. That's what worked for me.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
dustyhughes said:
I had the exact same experience with Best buy. The lady, as friendly as she was, was unhelpful in my situation. She kept saying they do not want to flash something that has been altered in any way just in case it gets bricked... it is to prevent liability on their part (which I can kind of understand). I even told her I'd be glad to sign a waiver to assume full liability if something goes wrong. She didn't go for it... Unfortunately, I'm stuck at the moment, I'm searching out ways to restore my build.prop from either adb sideload via the stock recovery or through ODIN somehow... There was a thread discussing a fix for the yellow triangle that required ODIN to flash some files (5 or so)... So, I was thinking if I can get the same type of thing setup for build.prop, I'd be in good shape... I just have 0 experience with doing this stuff, so I'm still reading/learning how it all works.
Click to expand...
Click to collapse
Wait so you lost root, too?
What exactly is your problem?
Because you can replace your build.prop with adb easily.
Exel said:
Wait so you lost root, too?
What exactly is your problem?
Because you can replace your build.prop with adb easily.
Click to expand...
Click to collapse
Sorry, I was a bit vague... I modded the build.prop to enable lockscreen rotation, which was basically adding one line to the end of the file. I realize how dumb this was, it was late and I wasn't thinking clearly :silly:....
Well, since I modded the build.prop, I cannot boot to the OS, in fact after the Samsung boot logo it doesn't even make it to the AT&T boot screen. It remains black after Samsung boot logo. The LED does turn blue after a bit, and if I have the phone plugged into the laptop the USB drivers will install, but I never make it to the OS no matter how long I leave the phone.
So I'm stuck not being able to boot to the OS. I can get to stock recovery and have the ADB sideload option, but it seems to be different that full blown ADB (from what I've gathered).
My biggest problem now is trying to take a copy of the clean build.prop and replace the one that is messed up in /system/
I can't determine exactly what I need (update script with build.prop etc) to load over sideload to get it to work.
---------- Post added at 12:07 PM ---------- Previous post was at 12:03 PM ----------
silrosriv said:
Dusty, I think if you're on MF3 nothing is going to work. You can try an emergency firmware flash through Kies. If you're at the yellow triangle and it's telling you to connect it to Kies then look at the top and see if it says that you're running Samsung official with write block enabled. If it does then take it back to the Samsung experience kiosk and tell them your PC froze during an update and that's what broke your phone.
Hope it helps. That's what worked for me.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I can get my phone to the yellow triangle, but mine actually says custom in the top left instead of official... Because of that, I couldn't convince the lady at the kiosk to flash my phone. Granted, it wasn't on the yellow triangle yesterday when i took it. I did convince her to plug it in while I had it in download mode. It recognized my phone, but I couldn't get her to proceed with flashing it.
dustyhughes said:
Sorry, I was a bit vague... I modded the build.prop to enable lockscreen rotation, which was basically adding one line to the end of the file. I realize how dumb this was, it was late and I wasn't thinking clearly :silly:....
Well, since I modded the build.prop, I cannot boot to the OS, in fact after the Samsung boot logo it doesn't even make it to the AT&T boot screen. It remains black after Samsung boot logo. The LED does turn blue after a bit, and if I have the phone plugged into the laptop the USB drivers will install, but I never make it to the OS no matter how long I leave the phone.
So I'm stuck not being able to boot to the OS. I can get to stock recovery and have the ADB sideload option, but it seems to be different that full blown ADB (from what I've gathered).
My biggest problem now is trying to take a copy of the clean build.prop and replace the one that is messed up in /system/
I can't determine exactly what I need (update script with build.prop etc) to load over sideload to get it to work.
---------- Post added at 12:07 PM ---------- Previous post was at 12:03 PM ----------
I can get my phone to the yellow triangle, but mine actually says custom in the top left instead of official... Because of that, I couldn't convince the lady at the kiosk to flash my phone. Granted, it wasn't on the yellow triangle yesterday when i took it. I did convince her to plug it in while I had it in download mode. It recognized my phone, but I couldn't get her to proceed with flashing it.
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=1236732
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
dustyhughes said:
Sorry, I was a bit vague... I modded the build.prop to enable lockscreen rotation, which was basically adding one line to the end of the file. I realize how dumb this was, it was late and I wasn't thinking clearly :silly:....
Well, since I modded the build.prop, I cannot boot to the OS, in fact after the Samsung boot logo it doesn't even make it to the AT&T boot screen. It remains black after Samsung boot logo. The LED does turn blue after a bit, and if I have the phone plugged into the laptop the USB drivers will install, but I never make it to the OS no matter how long I leave the phone.
So I'm stuck not being able to boot to the OS. I can get to stock recovery and have the ADB sideload option, but it seems to be different that full blown ADB (from what I've gathered).
My biggest problem now is trying to take a copy of the clean build.prop and replace the one that is messed up in /system/
I can't determine exactly what I need (update script with build.prop etc) to load over sideload to get it to work.
---------- Post added at 12:07 PM ---------- Previous post was at 12:03 PM ----------
I can get my phone to the yellow triangle, but mine actually says custom in the top left instead of official... Because of that, I couldn't convince the lady at the kiosk to flash my phone. Granted, it wasn't on the yellow triangle yesterday when i took it. I did convince her to plug it in while I had it in download mode. It recognized my phone, but I couldn't get her to proceed with flashing it.
Click to expand...
Click to collapse
Then I would try Kies. Leave your phone unplugged, then go to tools, upgrade and initialization, in all caps enter your device (mine is SGH-I337), click ok, enter your serial number, click ok, then plug in your phone in Odin mode. If that doesn't work you may have to wait for someone to figure out MF3 with Odin.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
silrosriv said:
Try this
http://forum.xda-developers.com/showthread.php?t=1236732
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Thanks much, I really appreciate the help. I have tried to push/pull files from my device without luck. The only option i have for ADB on my phone at the moment is the stock recovery "install over adb". It looks like the only commands I can run are "adb devices" (which lists my phone as "sideload") and "adb sideload"... I've used the sideload command to try and flash an OTA mf3 cfg file I found in another thread. the file was successfully pushed to the phone, and the update began but failed with an erro code of 7 (which is supposed to mean wrong device or something).
I was thinking if I could encapsulate the build.prop with a script into one of these update files to be pushed over sideload, I may be able to get my build.prop replaced and my phone running again. But i'm not sure how to build that file, or whether or not it would even have access to replace a file in the "/system" folder.
I'm still searching, and will update when/if I find an answer.
dustyhughes said:
Thanks much, I really appreciate the help. I have tried to push/pull files from my device without luck. The only option i have for ADB on my phone at the moment is the stock recovery "install over adb". It looks like the only commands I can run are "adb devices" (which lists my phone as "sideload") and "adb sideload"... I've used the sideload command to try and flash an OTA mf3 cfg file I found in another thread. the file was successfully pushed to the phone, and the update began but failed with an erro code of 7 (which is supposed to mean wrong device or something).
I was thinking if I could encapsulate the build.prop with a script into one of these update files to be pushed over sideload, I may be able to get my build.prop replaced and my phone running again. But i'm not sure how to build that file, or whether or not it would even have access to replace a file in the "/system" folder.
I'm still searching, and will update when/if I find an answer.
Click to expand...
Click to collapse
Not sure, correct me if I'm wrong, but I think you're in recovery (blue DOS looking menu list). Power button & volume up? That is how you get to sideload. To do regular adb you need to run an app for terminal emulator while the phone is actually on.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
silrosriv said:
Then I would try Kies. Leave your phone unplugged, then go to tools, upgrade and initialization, in all caps enter your device (mine is SGH-I337), click ok, enter your serial number, click ok, then plug in your phone in Odin mode. If that doesn't work you may have to wait for someone to figure out MF3 with Odin.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I'm afraid you are right... If MF3 were available through Kies (since I was unfortunate enough to get a phone with mf3) i'd be ok... but i think i may just be waiting a while.... My wife has the same phone, so if i could image hers, I could go that route... but again, out of my area of expertise.
---------- Post added at 12:29 PM ---------- Previous post was at 12:28 PM ----------
silrosriv said:
Not sure, correct me if I'm wrong, but I think you're in recovery (blue DOS looking menu list). Power button & volume up? That is how you get to sideload. To do regular adb you need to run an app for terminal emulator while the phone is actually on.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
you are correct, I cannot get to the phone's os for full blown adb...
dustyhughes said:
I'm afraid you are right... If MF3 were available through Kies (since I was unfortunate enough to get a phone with mf3) i'd be ok... but i think i may just be waiting a while.... My wife has the same phone, so if i could image hers, I could go that route... but again, out of my area of expertise.
---------- Post added at 12:29 PM ---------- Previous post was at 12:28 PM ----------
you are correct, I cannot get to the phone's os for full blown adb...
Click to expand...
Click to collapse
I kind of want to try for you..
You have TeamViewer? It's a remote access app for your PC so I can run some commands on your PC (adb)
dustyhughes said:
I'm afraid you are right... If MF3 were available through Kies (since I was unfortunate enough to get a phone with mf3) i'd be ok... but i think i may just be waiting a while.... My wife has the same phone, so if i could image hers, I could go that route... but again, out of my area of expertise.
---------- Post added at 12:29 PM ---------- Previous post was at 12:28 PM ----------
you are correct, I cannot get to the phone's os for full blown adb...
Click to expand...
Click to collapse
Have you tried to boot in safe mode? I don't think it will let you change anything though.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Exel said:
I kind of want to try for you..
You have TeamViewer? It's a remote access app for your PC so I can run some commands on your PC (adb)
Click to expand...
Click to collapse
I do not have teamviewer currently installed. I've been using LogMeIn since it was completely free and kind of just stuck with it. I've also used join.me for the one off remote assistance situations.
i would be willing to allow you to try. I currently have ADB installed and have updated the windows path environment to use ADB universally, so there's no need to be in any certain directory.
I would be willing to allow you to attempt something... I'm almost desperate at this point
Sorry for the delay, I'm still at work, and something came up.
You guys can also try Join.me totally free.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
silrosriv said:
Have you tried to boot in safe mode? I don't think it will let you change anything though.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
i'm not sure what you mean about safe mode, is there a hardware key combination required for it?
---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------
silrosriv said:
You guys can also try Join.me totally free.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Yes, I love Join.me... I liked it more before it started "suggesting" you to buy it all the time though
dustyhughes said:
i'm not sure what you mean about safe mode, is there a hardware key combination required for it?
---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------
Yes, I love Join.me... I liked it more before it started "suggesting" you to buy it all the time though
Click to expand...
Click to collapse
Feel free to PM me the info and whatnot and I'll see what I can do for you.
Ok, i got my G2 today and have spent hours upon hours trying to get this to work.
This is where im at so far,
I have the international version of the G2-d802
I have used the ioroot10 file to root the phone.
Downloaded ROM manager from the play store and attempted to flash clockwork recovery mod.
It says it is complete, but then when I select reboot to recovery I just receive the dead android with the red exclamation mark, with the words " No Command " written underneath.
What am I doing wrong?
It all seemed straight forwards until I tried to attempt it myself, I've looked everywhere for answers and have come up with nothing.
P.S: I am a complete noob when it comes to this. I have seen some methods involving adb or something, seemed too complex, and I figured using some apps and a simple batch file would be enough to get this to work, apparently I was wrong.
Try the recovery images in the dev. section. I don't think the ROM Manager version is loki-fied.
download Flashify from Play Store to push custom recovery ... i've done it that way ... fast n efficient
your_m0m said:
Try the recovery images in the dev. section. I don't think the ROM Manager version is loki-fied.
Click to expand...
Click to collapse
No offence, but. I have no idea what you just told me to do or how to even go about doing it. Could you please elaborate?
Download flashify From play store
Find twrp or cwm recovery from the developer section of xda.
Use flashify to flash this recovery
Sent from my VS980 4G using Tapatalk
CKsquid said:
No offence, but. I have no idea what you just told me to do or how to even go about doing it. Could you please elaborate?
Click to expand...
Click to collapse
Sorry, you can use flashify like the other guy said or follow the instructions on this thread.
http://forum.xda-developers.com/showthread.php?t=2468858
---------- Post added at 02:08 AM ---------- Previous post was at 02:04 AM ----------
your_m0m said:
Sorry, you can use flashify like the other guy said or follow the instructions on this thread.
http://forum.xda-developers.com/showthread.php?t=2468858
Click to expand...
Click to collapse
This one might be better.
http://forum.xda-developers.com/showthread.php?t=2500441
I thank you guys for trying to help me, but literally all the stuff you are linking and the things you are saying dont make any sense to me.
I need a step by step, simplified guide on what I am supposed to be doing,
I downloaded flashify, downloaded some sort of recovery-clockwork.img file and used flashify on it, rebooted then just got some small text in the top left corner :/
please help me, because I honestly think the lg's varient of andoid is utter ****e.
I haven't used flashify so I can't help you there, but the second link I posted is an auto installer for recovery.
Could someone please offer some advice, i really am stumped on this one. I have a nexus 4 which is rooted has an unlocked bootloader and is running on the stock version of kitkat. Last week i changed network and as bizarre as it sounds when i got disconnected from three my phone bricked and got stuck on the boot logo.
Since then i went home and got the skipsoft toolkit up and running to essentially put a fresh rom on. Unfortunately no luck, i have gone into the bootloader and recovery,factory/wipe reset -- still no luck it's stuck on the boot logo. Now i realised that adb isn't working only fastboot which has also limited my options. i have tried multiple version of roms/recoverys etc.. they install which confirmed by the change of boot logo but that's it just hangs again.
Is there something else i can try? I would really appreciate some direction on it. Thanks very much in advanced.
airrunner said:
Could someone please offer some advice, i really am stumped on this one. I have a nexus 4 which is rooted has an unlocked bootloader and is running on the stock version of kitkat. Last week i changed network and as bizarre as it sounds when i got disconnected from three my phone bricked and got stuck on the boot logo.
Since then i went home and got the skipsoft toolkit up and running to essentially put a fresh rom on. Unfortunately no luck, i have gone into the bootloader and recovery,factory/wipe reset -- still no luck it's stuck on the boot logo. Now i realised that adb isn't working only fastboot which has also limited my options. i have tried multiple version of roms/recoverys etc.. they install which confirmed by the change of boot logo but that's it just hangs again.
Is there something else i can try? I would really appreciate some direction on it. Thanks very much in advanced.
Click to expand...
Click to collapse
What do you mean you changed network? What recovery are you using twrp or cwm hope it's twrp I think you need to search forums for wugfresh tool kit and start fresh which means going back to stock rom, recovery etc.. Wugfresh toolkit is the easiest method for you and even has videos on YouTube for step by step instructions you can't go wrong be patient and pay attention and you will be OK..www.wugfresh.com/youtube
---------- Post added at 09:58 PM ---------- Previous post was at 09:56 PM ----------
WelfareBaby said:
What do you mean you changed network? What recovery are you using twrp or cwm hope it's twrp I think you need to search forums for wugfresh tool kit and start fresh which means going back to stock rom, recovery etc.. Wugfresh toolkit is the easiest method for you and even has videos on YouTube for step by step instructions you can't go wrong be patient and pay attention and you will be OK..www.wugfresh.com/
Click to expand...
Click to collapse
[/COLOR]
WelfareBaby said:
What do you mean you changed network? What recovery are you using twrp or cwm hope it's twrp I think you need to search forums for wugfresh tool kit and start fresh which means going back to stock rom, recovery etc.. Wugfresh toolkit is the easiest method for you and even has videos on YouTube for step by step instructions you can't go wrong be patient and pay attention and you will be OK
Click to expand...
Click to collapse
I meant literally that i changed network from three to ee, which i also brought my original number over with it. The day my number transfered to ee my phone bricked and it's been stuck on boot loop since.
I have never used wugfresh before but i followed your instructions and spent sometime with it this morning. It's a very simple piece of software and i must admit i was feeling hopeful it might have fixed my boot-loop issue, but it hasn't. I have done factorywipes/wiped cache, flashed multiple version roms. As far as recovery i had TWRP running on my device, but for some reason i am no longer able to go into it only the bootloader. When i do click on recovery i got the android on its back with the exclamation mark, which obviously gives me the wipe options which i have done.
If there is anything else you can think of i would be greatly appreciative.
airrunner said:
[/COLOR]
I meant literally that i changed network from three to ee, which i also brought my original number over with it. The day my number transfered to ee my phone bricked and it's been stuck on boot loop since.
I have never used wugfresh before but i followed your instructions and spent sometime with it this morning. It's a very simple piece of software and i must admit i was feeling hopeful it might have fixed my boot-loop issue, but it hasn't. I have done factorywipes/wiped cache, flashed multiple version roms. As far as recovery i had TWRP running on my device, but for some reason i am no longer able to go into it only the bootloader. When i do click on recovery i got the android on its back with the exclamation mark, which obviously gives me the wipe options which i have done.
If there is anything else you can think of i would be greatly appreciative.
Click to expand...
Click to collapse
.
I really have no clue what changing network to ee is did you not create a backup if so you could restore it but since you can't once you get in bootloader and scroll to recovery you get dead android use to toolkit I told you and flash stock+unroot option it should work
---------- Post added at 12:57 AM ---------- Previous post was at 12:56 AM ----------
WelfareBaby said:
.
I really have no clue what changing network to ee is did you not create a backup if so you could restore it but since you can't once you get in bootloader and scroll to recovery you get dead android use to toolkit I told you and flash stock+unroot option it should work
Click to expand...
Click to collapse
If not pm me try to help you figure it out
I am very grateful you taking the time to help me with the boot issue. But i have actually just managed to sort it, finally!
It came down to me changing to an older radio version for 4.4.4., then i installed a 4.3 rom which it worked! I then upgraded to 5.01 and hey presto it's back to normal.
Thanks again nexus root tool-kit is definitely an essential
airrunner said:
I am very grateful you taking the time to help me with the boot issue. But i have actually just managed to sort it, finally!
It came down to me changing to an older radio version for 4.4.4., then i installed a 4.3 rom which it worked! I then upgraded to 5.01 and hey presto it's back to normal.
Thanks again nexus root tool-kit is definitely an essential
Click to expand...
Click to collapse
Your welcome glad I could help we all been in some situation before since you back up and running don't forget to make a backup of current rom always good idea to have that handy in case.. Cheers...
I left my phone charging and came back to get it. It was stuck on the google logo, I am able to boot into recovery but it says No Installed.
Is their anything else I can do other than flash it again.
I was thinking maybe the wrong partititon was checked, but everything looks fine.
Krooked22 said:
I left my phone charging and came back to get it. It was stuck on the google logo, I am able to boot into recovery but it says No Installed.
Is their anything else I can do other than flash it again.
I was thinking maybe the wrong partititon was checked, but everything looks fine.
Click to expand...
Click to collapse
Assuming that the ROM is still there, you can dirty flash the ROM zip over it, and see if it works. There's no harm in trying that.
But "No OS Installed" simply means that your /system or /boot parition are not detected (means, they are empty). Now of course, the last resort is to flash the ROM all over again.
Krooked22 said:
I left my phone charging and came back to get it. It was stuck on the google logo, I am able to boot into recovery but it says No Installed.
Is their anything else I can do other than flash it again.
I was thinking maybe the wrong partititon was checked, but everything looks fine.
Click to expand...
Click to collapse
You need to provide more information. Are you on the stock ROM or a custom ROM? Stock recovery or TWRP? Had you made any changes to the device recently?
Someone please help. I just rooted my 6P. Did a little bit of doing. Phone would never boot just the round circles. So went into TWRP and tried to wipe to start fresh, not it says no OS installed. I have no ROMS's on the phone. No boot images. Been a while since I've done this. Really need help on this one. Thanks.
Download the dp3 , boot into bootloader, connect to PC run installer script after you unzip the factory image " flash all" sit back and wait for phone to reboot.
---------- Post added at 10:30 PM ---------- Previous post was at 10:29 PM ----------
It's that simple.
Hey thanks a lot. Couple things, and I apologize in advance for not knowing this already.
1) what's dp3
2) how do I run installer script?
I know I shift right click and open a cmd window within fastest - where I'll unzip the file - and I know how to get the phone into Bootloader.
Again, sorry for asking for simple explanations.
StormCell said:
Someone please help. I just rooted my 6P. Did a little bit of doing. Phone would never boot just the round circles. So went into TWRP and tried to wipe to start fresh, not it says no OS installed. I have no ROMS's on the phone. No boot images. Been a while since I've done this. Really need help on this one. Thanks.
Click to expand...
Click to collapse
Download any ROM ( like pure Nexus) and gapps
You can use USB otg to flash the ROM using twrp or transfer the ROM file from your PC to your phone in twrp (it supports mtp)
Simply flash ROM and gapps and viola
Sent from my Nexus 6P using XDA Labs
Ok, I'm gonna tackle this tomorrow. Any recommendations on a good ROM and Kernel (Verizon). I made nice donations long ago to Franco and ROM Manager.
Thank again, everyone!
StormCell said:
Someone please help. I just rooted my 6P. Did a little bit of doing. Phone would never boot just the round circles. So went into TWRP and tried to wipe to start fresh, not it says no OS installed. I have no ROMS's on the phone. No boot images. Been a while since I've done this. Really need help on this one. Thanks.
Click to expand...
Click to collapse
Download the required ROM and gapps, connect your phone to pc , type in google, Mini adb and fastboot, a page on XDA itself will come, download it, its small and install.
Then copy the ROM and gapps package to the location of the installation of the application.
Now open your recovery and tap on adb sideload, and swipe(twrp)
Go to your PC, open adb application a cmd will appear, type adb devices, it will start a daemon then will give you your device number, a number should appear. Then type
Adb sideload """"name of your ROM package""".zip
It will start installing, wait for few minutes.
Do the same for gapps
Adb sideload " name of gapps package ".zip
Then reboot
Its fixed
NOT Sent from my GT-N7100 using the XDA-developers mobile app
i42o said:
Download the dp3 , boot into bootloader, connect to PC run installer script after you unzip the factory image " flash all" sit back and wait for phone to reboot.
---------- Post added at 10:30 PM ---------- Previous post was at 10:29 PM ----------
It's that simple.
Click to expand...
Click to collapse
Why are you telling him to install the Developer Preview? He wouldn't want that unless he's actually asking for it, which he isn't.
StormCell said:
Ok, I'm gonna tackle this tomorrow. Any recommendations on a good ROM and Kernel (Verizon). I made nice donations long ago to Franco and ROM Manager.
Thank again, everyone!
Click to expand...
Click to collapse
Please continue the discussion in the other thread that you posted this question in, as I said, let's not create duplicate discussions.
StormCell said:
Hey thanks a lot. Couple things, and I apologize in advance for not knowing this already.
1) what's dp3
2) how do I run installer script?
I know I shift right click and open a cmd window within fastest - where I'll unzip the file - and I know how to get the phone into Bootloader.
Again, sorry for asking for simple explanations.
Click to expand...
Click to collapse
Developer preview 3 is a Android N preview and it is very fluid, battery life is good on stock and reason I recommend this because it is simple to do, gives you good options within the ROM and is good overall but that's just my opinion.
---------- Post added at 12:35 PM ---------- Previous post was at 12:32 PM ----------
Heisenberg said:
Why are you telling him to install the Developer Preview? He wouldn't want that unless he's actually asking for it, which he isn't.
Click to expand...
Click to collapse
Dude, I'm trying to help. Beats what you said, you going detective mode on him while I'm just giving him an easy solution. Read a book or something
i42o said:
Dude, I'm trying to help. Beats what you said, you going detective mode on him while I'm just giving him an easy solution. Read a book or something
Click to expand...
Click to collapse
Lol. Maybe you missed the title under my name.
The dev preview isn't what he asked for, it isn't an easy solution, it isn't easy to come back from if he doesn't like it, it isn't even remotely what he needs. What he's looking for is a simple way to get his phone booted up and working again (a very simple request), and what you're suggesting is he install a beta OS (a complicated "solution").
If you really have a problem with a moderator requesting that a member posts in one place at a time (as per our rules), then I'm gobsmacked. If you'd care to look at the advice I gave him in the guide thread where he also posted you'd notice that I gave two solutions that:
A) Actually address the simplicity of his problem.
B) Give two simple, easy to execute, solutions that are the most common solutions you'll ever see anyone give a member in his situation. Solutions that don't involve having to install a developer preview that he never asked for.
I get that you're trying to help him, but the "solution" you provided him isn't right for his situation at all. There was no need to become defensive and aggressive when this was pointed out.
Vishal Vignesh said:
Download the required ROM and gapps, connect your phone to pc , type in google, Mini adb and fastboot, a page on XDA itself will come, download it, its small and install.
Then copy the ROM and gapps package to the location of the installation of the application.
Now open your recovery and tap on adb sideload, and swipe(twrp)
Go to your PC, open adb application a cmd will appear, type adb devices, it will start a daemon then will give you your device number, a number should appear. Then type
Adb sideload """"name of your ROM package""".zip
It will start installing, wait for few minutes.
Do the same for gapps
Adb sideload " name of gapps package ".zip
Then reboot
Its fixed
NOT Sent from my GT-N7100 using the XDA-developers mobile app
Click to expand...
Click to collapse
I'm copying files over to my Nexus now using MTP from TWRP. Can't I just copy evrything over and flash that way? Man, this seems so much more complicated than back in the day. Thanks.
Crap, wrong thread! Sorry! Got confused.
StormCell said:
I'm copying files over to my Nexus now using MTP from TWRP. Can't I just copy evrything over and flash that way? Man, this seems so much more complicated than back in the day. Thanks.
Crap, wrong thread! Sorry! Got confused.
Click to expand...
Click to collapse
Sure, this method is for those who do not wanna copy the zip package to the PC/don't have it
Sent from my GT-N7100 using XDA-Developers mobile app
If anybody can put up a step-by-step guide, or a video that shows how to properly install it all, I'm sure myself, and much of the community would appreciate it.
Recently, my laptop that I had ADB, and every tool imaginable for Androids, and specifically the Galaxy Series, took a huge dump on me and I lost it all. I installed it so long ago, that embarrassingly I've forgotten how I did it all. If someone could post how they rooted their GS7 (non-edge variant), I would be very appreciative. And I'm sure much of the community would be too. I'm embarrassed to even have to ask as someone who used to formerly develop mods on phones. But it is what it is. It's been so long since I've set it all up, and I've had to do so much since that time that I've simply forgotten how I did it/how to do it. Any help would be GREATLY appreciated. Thank you ahead of time...
I've tried following the instructions in the sticky above. I ran the 930X ROOT.TAR in the special version of ODIN. And every ran OK. It said "Success" and then rebooted. All seemed well, then it froze on the AT&T Boot Logo. What can I do from here? I know from history that this is one of the points that people panic and claimed "brick" (though I've never seen a real brick from rooting). Any help would be greatly appreciated
There's a great guide in the Verizon forum. Root was universal based on FW. Just make sure you flash the correct 930 or 935 with the modded odin. I recommend you follow the steps to "unroot" for the sake of doing an extremely in depth factory reset. Also make sure you get chain fires latest supersu built for the s7qc.
Sent from my SAMSUNG-SM-G930A using Tapatalk
twizt3d said:
There's a great guide in the Verizon forum. Root was universal based on FW. Just make sure you flash the correct 930 or 935 with the modded odin. I recommend you follow the steps to "unroot" for the sake of doing an extremely in depth factory reset. Also make sure you get chain fires latest supersu built for the s7qc.
Sent from my SAMSUNG-SM-G930A using Tapatalk
Click to expand...
Click to collapse
thank you for that. I'll check it out. Hopefully it'll get me past this bootscreen issue
yup. Great instructions. All set rooted now. Now time to play with xposed and V4A and the like. Yay
OK. Followed the instructions on the Verizon page and used the PrinceComsy version. Stuck at the AT&T logo. How did you go past this step? Should I have used the standard version? thanks
thanirs said:
OK. Followed the instructions on the Verizon page and used the PrinceComsy version. Stuck at the AT&T logo. How did you go past this step? Should I have used the standard version? thanks
Click to expand...
Click to collapse
(keep in mind this is only my personal experience...)
but the PrinceComsy version of ODIN was the only one to work for me. How far exactly have you gotten in the process before you got stuck at the logo? You do have ADB installed correctly installed on your PC and turned on on your phone right? and cd-ed the specific "super" folder for the SU adb install, right? FYI: It's not a simple root process, like 1-click roots on previous devices. This is more similar to the in-depth root methods like on the N1 and D1 before super nice devs went out of their way to make it simple. So if you're not familiar with ADB shell and the likes, it'll be difficult for you. But, no matter how high and mighty or condescending people act, we've all had to start somewhere. I'll help you get through the process as much as I can
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
52brandon said:
(keep in mind this is only my personal experience...)
but the PrinceComsy version of ODIN was the only one to work for me. How far exactly have you gotten in the process before you got stuck at the logo? You do have ADB installed correctly installed on your PC and turned on on your phone right? and cd-ed the specific "super" folder for the SU adb install, right? FYI: It's not a simple root process, like 1-click roots on previous devices. This is more similar to the in-depth root methods like on the N1 and D1 before super nice devs went out of their way to make it simple. So if you're not familiar with ADB shell and the likes, it'll be difficult for you. But, no matter how high and mighty or condescending people act, we've all had to start somewhere. I'll help you get through the process as much as I can
Click to expand...
Click to collapse
---------- Post added at 08:47 PM ---------- Previous post was at 08:21 PM ----------
OK. Proceeding with the recommended steps in the install guide, I ran into this one nagging pop-up:
Security notice: Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes.
Its a rather annoying notice that keeps popping up. What is the fix for this? Quick 'google' suggested some people uninstalling Knox altogether and it seemed fairly drastic. Suggestions?
thanirs said:
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
Click to expand...
Click to collapse
---------- Post added at 09:08 PM ---------- Previous post was at 08:47 PM ----------
OK never mind please and sorry. Found the answer in the Fix/debloat script.
thanirs said:
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
---------- Post added at 08:47 PM ---------- Previous post was at 08:21 PM ----------
OK. Proceeding with the recommended steps in the install guide, I ran into this one nagging pop-up:
Security notice: Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes.
Its a rather annoying notice that keeps popping up. What is the fix for this? Quick 'google' suggested some people uninstalling Knox altogether and it seemed fairly drastic. Suggestions?
---------- Post added at 09:08 PM ---------- Previous post was at 08:47 PM ----------
OK never mind please and sorry. Found the answer in the Fix/debloat script.
Click to expand...
Click to collapse
so you got it all figured out and running great now right? No other issues right?
Just to add to this, I have verified that this still works using PG1.
http://forum.xda-developers.com/showpost.php?p=67970468&postcount=33
twizt3d said:
Just to add to this, I have verified that this still works using PG1.
http://forum.xda-developers.com/showpost.php?p=67970468&postcount=33
Click to expand...
Click to collapse
Can you please try restoring to af2?
Thanks for the ping. I think so. One thing I ran into which I don't know if its related to rooting. When I am in a phone conversation, audio on the other end goes in and out after a few minutes into the call. This happens with bluetooth or not. Still figuring out this issue.
52brandon said:
so you got it all figured out and running great now right? No other issues right?
Click to expand...
Click to collapse
Seeing battery drain. So went back to stock /unroot for now.
I was not trying to root my phone but reflash to an earlier version. I tried the Prince version of Odin and it did not work. The version that ended up working is in this thread
http://forum.xda-developers.com/att-galaxy-s7/how-to/firmware-g930a-edge-variant-afp-stock-t3415344
http://click.xda-developers.com/api...ww.mediafire.com/download/2t...din_3.12.3.rar