OK the thing is I got my S3 which rocks by the way, but I went crazy when I switch the WiFi toggle to ON and never see a sole WiFi connection. I've tried with routers, APs, even turn my Dell Studio 1555 laptop into an AP using Connectify... and got the same problem. The phone seems to be scanning the area, but I think is not.
So this is what I've been trying so far. Reading this thread I called *#0011#, entered into Service Mode, pressing Menu I entered into WiFi and turned off WiFi powersaving mode, fixing absolutely nothing.
Then I tried to open an adb shell, then su and then:
Code:
wpa_supplicant -dd -i wlan0 -f /sdcard/wifi.log -c /etc/wifi/wpa_supplicant.conf
And I don't know if the code is wrong or something, but what I get is this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I tried to run "wpa_cli", like an user in that post points, but adb just wont recognize that command.
After that I use the command logcat and when I switch the WiFi ON, this is what I get:
As you can see I'm getting an error
Code:
wpa_supplicant ( 5068): wlan0: Failed to initiated AP scan
So my first questions are, does this happens frecuently? Someone here has been with this problem? It's fixeable?
Thanks in advance.
There is no standard for command-line applications. In this case, it seems to be looking for:
wpa_supplicant -dd -iwlan0 -f/sdcard/wifi.log -c/etc/wifi/wpa_supplicant.conf
instead of this:
wpa_supplicant -dd -i wlan0 -f /sdcard/wifi.log -c /etc/wifi/wpa_supplicant.conf
I don't use ADB, so I cannot test. However, usually if the usage doesn't show spaces, don't use them. It shows you this in the example at the bottom
Aerowinder said:
There is no standard for command-line applications. In this case, it seems to be looking for:
wpa_supplicant -dd -iwlan0 -f/sdcard/wifi.log -c/etc/wifi/wpa_supplicant.conf
instead of this:
wpa_supplicant -dd -i wlan0 -f /sdcard/wifi.log -c /etc/wifi/wpa_supplicant.conf
I don't use ADB, so I cannot test. However, usually if the usage doesn't show spaces, don't use them. It shows you this in the example at the bottom
Click to expand...
Click to collapse
I tried it and get EXACTLY the same.
However you can see the log in the logcat command I put.
It's fixeable?
If your bone stock, try using Odin and reflashing stock again. Maybe you have a corrupted driver. If your not stock, did you flash a kernel? Some have modified wifi drivers.
stevessvt said:
If your bone stock, try using Odin and reflashing stock again. Maybe you have a corrupted driver. If your not stock, did you flash a kernel? Some have modified wifi drivers.
Click to expand...
Click to collapse
I'm in stock. I'll try to reflash it again. And then tell you.
However if I install a custom ROM, which kernel you recomend me?
I'm worried about this, I just need to know if it's a hardware of software problem.
Thanks.
I think they all do, but its easy to make a back up of your stock ROM first. This usually works, but sometimes it needs to be Odined back.
Are you rooted?
What build are you on?
Have you ever flashed, modded or updated anything on the phone?
Did you restore any backups from a previous rom or device?
Anything else you have done, such as installing any wifi management apps or anything like that could be useful info.
Boot into recovery, wipe cache and dalvik then reboot. If still not working try a factory reset from the settings menu. (This will wipe all data including internal sdcard)
If this doesnt work try using odin to flash MrRobinsons root66 version of UVALH2. (This way you will have root if you dont already and will have more ability to troubleshoot than without in case it still doesnt work.) (Or if you are just set against rooting flash the regular UVALH2 fw)
If you are on build UVALEM or UVALG1, while in the wifi scan screen press menu, advanced (i think), and make sure your wifi band is set to auto. Try 2.4ghz and 5ghz only as well.
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Are you rooted?
What build are you on?
Have you ever flashed, modded or updated anything on the phone?
Did you restore any backups from a previous rom or device?
Anything else you have done, such as installing any wifi management apps or anything like that could be useful info.
Boot into recovery, wipe cache and dalvik then reboot. If still not working try a factory reset from the settings menu. (This will wipe all data including internal sdcard)
If this doesnt work try using odin to flash MrRobinsons root66 version of UVALH2. (This way you will have root if you dont already and will have more ability to troubleshoot than without in case it still doesnt work.) (Or if you are just set against rooting flash the regular UVALH2 fw)
If you are on build UVALEM or UVALG1, while in the wifi scan screen press menu, advanced (i think), and make sure your wifi band is set to auto. Try 2.4ghz and 5ghz only as well.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I'm rooted. My build is IMM76D.T999UVALEM. I've never flashed, modded or update anything on the phone... except, well, the root procedure with the toolkit. I didn't make a backup of a previous rom. Also I never installed anything WiFi-related.
I booted into Recovery, wiped cache and dalvik and still doesn't work. I tried 2.4ghz and 5ghz wifi bands and nothing.
I will try to reflash the stock rom and see what happens, in the meantime I'll download MrRobinsons root66 version of UVALH2 and if the stock doesn't work, I install MrRobinson's and I'll tell you.
Thanks for you answer.
I hopw what I tell you so far serves you to help me... in the meantime I'll do the ROMs flashing.
Just fyi, MrRobinsons root66 version is the stock build only it is pre-rooted.
He has both UVALEM and UVALH2 versions.
UVALEM is the original out of the box build.
UVALH2 is the official updated build.
I would recommend updating regardless, and in your case it may be your best bet. I leave it up to you if you want to try root66 or not, but ive used it quite a few times and its always worked well for me.
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Just fyi, MrRobinsons root66 version is the stock build only it is pre-rooted.
He has both UVALEM and UVALH2 versions.
UVALEM is the original out of the box build.
UVALH2 is the official updated build.
I would recommend updating regardless, and in your case it may be your best bet. I leave it up to you if you want to try root66 or not, but ive used it quite a few times and its always worked well for me.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Sorry man, I'm looking MrRobinsons root66 and I can't find it. Can you give me the direct link? Man I'm not a noob and still I can't find it :laugh:
EDIT:
--------------------
I found this one, but it's for the AT&T version.
http://forum.xda-developers.com/showthread.php?t=1771687
stevessvt said:
http://forum.xda-developers.com/showthread.php?t=1771687
Click to expand...
Click to collapse
LFMAO... you gave me the link in the exact moment I found it.
THANKS.
I'll tell you when I flash this one.
I flashed the UVALEM stock rom founded in this thread and Odin shows me this error:
Code:
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> amss
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Also the phone show me this error: Unsupport dev_type
I have no idea why... let's hope with this everything goes fine.
Your in download mode, correct? Vol down, home and power, until it vibrates, then let power go but hold vol down and home.
stevessvt said:
Your in download mode, correct? Vol down, home and power, until it vibrates, then let power go but hold vol down and home.
Click to expand...
Click to collapse
Yep, in download mode.
Did you unzip the file? The file you flash is inside the zip file
stevessvt said:
Did you unzip the file? The file you flash is inside the zip file
Click to expand...
Click to collapse
If I don't unzip it Odin won't see it
Well hmmmm....m
I'd factory reset, or wipe. Then flash a custom Rom.
Also, I'd put my router back the way it was.
Reboot both systems, etc
Sent from my SGH-T999 using xda premium
---------- Post added at 08:28 PM ---------- Previous post was at 08:18 PM ----------
have you tried flashing using Rom manager?
Sent from my SGH-T999 using xda premium
Well guys I installed MrRobinson's root66 ROM and didn't fix the wifi since, like a while ago, the phone can't see any wifi network. BUT I pass a logcat and my surprise was the shell showed me the same error of before, but with more things:
I hope this "new" things on the shell should indicate anyone some good fixer answer for me.
Please help... I'm literally sh*ted on my pants here.
Thanks in advance.
Maybe you got a defective phone? Can you take it back and exchange for another?
Sent from my SGH-T999 using xda app-developers app
Related
I've read and read many threads in this subject. Now im just soo confused. Please help me understand the steps required to update my rooted GB to ICS.
This is what i'm on.. rogue ET recovery 1.1.2 (CWM v5.0.2.7)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I would like to update to go to [ROM][TeaM VeNuM]◣◢)BOA(now Blue Too)v0.2 -FF18-Updated 07-02-12 De-Odexed TW/LG/ICS
In order for me to update to this ICS rom, i need to update my CWM recovery correct..? AGAT recovery is what most recommend.
here..
http://forum.xda-developers.com/showthread.php?t=1687354
So i boot my phone into recovery and install the AGAT.zip to update my recovery then i should be free to install venum rom correct?
Or do i need to be already in a ICS stock rom to flash the AGAT recovery to update to the Venum rom...???
please help me understand..!!!! thanks in advance
Your model number shows SPH-D710 which is the Sprint Epic Touch 4G. This forum is for the SGH-i777 AT&T Galaxy S II. Completely different phone.
Ill bounce this to the ET4G forum for you...
Red5 said:
Your model number shows SPH-D710 which is the Sprint Epic Touch 4G. This forum is for the SGH-i777 AT&T Galaxy S II. Completely different phone.
Ill bounce this to the ET4G forum for you...
Click to expand...
Click to collapse
Wow... ok.. I feel really stupid now thanks... I'm starting out well.. lol
anyone..??
If you have mobile Odin install the stock el26 kernel from there if not use Odin boot into recovery and use calks wipe all then flash rom should work with no problems its the safest way to flash here's a link to el26 from my drive save ya some time looking. make sure you nandroid backup and titanium backup before hand and also make sure you have the rom on your sdcard.
El26
https://docs.google.com/file/d/0B7aReWYt54fKUGxBNXEwXzNPaHM/edit
Calks wipe all
https://docs.google.com/file/d/0B7aReWYt54fKMTlzN2p0YXFqUXM/edit
Sent from my SPH-D710 using Tapatalk 2
Sry forgot to set the share settings should be ok now
Sent from my SPH-D710 using Tapatalk 2
Its alright, ya got it now =)
I was attempting to flash to the newest AOKP rom(7-13), well preparing to flash to it anyhow. I flashed the latest AGATS recovery as per QBKing's video posted on the...14th I'm sure.
Anyhow, I flashed the recovery and now I am unable to get past the samsung splash. After having done this, I imagine I did it wrong, but I can still get to the recovery, which is AGATS now. You say that the way you just posted was the safest way to flash? I believe you, being that it looks the simplest.
orr
Would i be able to flash the AOKP rom now? QBK said this is the safest recovery, if something on my prior setup isn't savy with this recovery, if I flash this new ICS rom, then it should all work itself out?
So for anyone wondering, I went ahead and flashed the rom, and it worked. I went ahead and installed AOKP rom, and it booted up. I re-installed agats recovery FF18 (<-- this is right right? I need to learn, teach me! lol) then booted back into the rom to make sure that it worked, and it did. rebooted into recovery, mounted usb, copied gapps, unmounted.
I just flashed gapps, and am rebooting ......and am now stuck in a boot loop to the recovery? What happened??
Alright lol, I somehow was stuck in a loop, but I did a battery pull whilst in agat, then hit the power button, it rebooted into agat but straight into the reboot menu, and then I clicked reboot to system and I'm back to the rom now.
I'm not getting any Wifi or 4g, and low signal. but I do have play store. jumped feet first into it, now I gotta deal with it ....
Agats recovery is a TouchWiz based recovery. That's probably why you are having issues with wifi and possible many other issues. I suggest you start again and flash EL26 using mobile Odin , factory reset+ wipe cache+dalvik cache, install aokp rom and gapps right after and then reboot. The included recovery in the latest AOKP, TWRP, has been modified and be labeled as safe. There is no need to flash another recovery. But as you may know, there is always a risk when flashing ICS, so take things slow and double check things
Sent from my SPH-D710 using xda app-developers app
Well it would seem that another one of my problems is that I can't access my storage menu under settings, leading me to believe that I don't have any access to my SDcard. I'm just going to use regular odin to flash down to EL26. then follow btaylor545 instructions below. Unless I ca figure out installing this mobile_odin .apk to my phone somehow. I'd prefer that, don't wanna raise the y_triangle.
mosez.315 said:
Well it would seem that another one of my problems is that I can't access my storage menu under settings, leading me to believe that I don't have any access to my SDcard. I'm just going to use regular odin to flash down to EL26. then follow btaylor545 instructions below. Unless I ca figure out installing this mobile_odin .apk to my phone somehow. I'd prefer that, don't wanna raise the y_triangle.
Click to expand...
Click to collapse
You can't go into the market and download it? You could also just download a file explorer from the market and install it that way. And there now an app called Triangle away and will take away the triangle as long as you are on ICS. It's made by the same person who made Mobile Odin, Chainfire.
Yeah, I have the store, but I don't have access to it because I need to be connected to my data, can't via 3/4G, or my wifi, so I can't download anything via market. I'm reading to figure something out now...
---------- Post added at 11:23 PM ---------- Previous post was at 11:00 PM ----------
Alright!
So through all my fruitful searching (it actually turns up great results here!!) I got Mobile Odin Lite pushed to my device via APKPush. I need to instal an addon because its Odin Lite, but its only for flashing FW's, so I oughta be all right to flash the el26 kernel with Mobile Odin.
So now I have all of the tools available to me, I just need the route. I oughta be fine doing all of this, ICS to ICS, because it's the released ICS, not the leaked correct?
:highfive: i just wanted to give everyone a big thanks... I'm officially on ICS..! :victory:
I basically did as stated by btaylor545 and SkippyDogg...
- Used stock el26 kernel .TAR version
- flashed stock EL26 kernel using ODIN mobile purchased from the market.
- Phone will reboot after flash. Hold vol up and power button to go into recovery.
- use Calks wipe all .zip multiple times..
- then flashed my ICS rom...
Rom used:
http://forum.xda-developers.com/showthread.php?t=1694483
One last question... If i wanted to try another ICS rom, is it best practice to flash back to GB rom and EL26 kernel then go to another ICS rom or just using EL26 stock kernel be sufficient to jump to another ICS rom.. Thanks again..
mclain1 said:
:highfive: i just wanted to give everyone a big thanks... I'm officially on ICS..! :victory:
I basically did as stated by btaylor545 and SkippyDogg...
- Used stock el26 kernel .TAR version
- flashed stock EL26 kernel using ODIN mobile purchased from the market.
- Phone will reboot after flash. Hold vol up and power button to go into recovery.
- use Calks wipe all .zip multiple times..
- then flashed my ICS rom...
Rom used:
http://forum.xda-developers.com/showthread.php?t=1694483
One last question... If i wanted to try another ICS rom, is it best practice to flash back to GB rom and EL26 kernel then go to another ICS rom or just using EL26 stock kernel be sufficient to jump to another ICS rom.. Thanks again..
Click to expand...
Click to collapse
Welcome to ICS! :victory:
To Answer your question, just flashing the kernal though Mobile Odin and repeat the steps I mentioned and you're good to goo.
I've managed to get to ICS successfully too! AOKP Fri da 13th build. I'm having problems with service still, can't find where to connect to my wifi, and no 4g. Is that where a different modem kernel would come in?
SkippyDogg said:
Welcome to ICS! :victory:
To Answer your question, just flashing the kernal though Mobile Odin and repeat the steps I mentioned and you're good to goo.
Click to expand...
Click to collapse
That is awsome skippyDogg..! Thanks again.. . Awesome community..!
mosez.315 said:
I've managed to get to ICS successfully too! AOKP Fri da 13th build. I'm having problems with service still, can't find where to connect to my wifi, and no 4g. Is that where a different modem kernel would come in?
Click to expand...
Click to collapse
Mosez, i'm still a noob, but i usually resolve reception issues by flashing a different modem. I'm on FC14 now with this new rom and so far no connectivity issues, i'll give it a couple more days..
I think I'm still on a GB kernel for some reason...when I go to system settings>about phone> it tells me I still have an EL29 baseband version. Whats up with that? Is that the problem causer?
Your base band version is your modem. Flash a rom does not upgrade your modem. There is a section with all the different modems available. You can flash thru recovery or mobile Odin.
Sent from my SPH-D710 using xda app-developers app
Lol, I know now. The delay of any responses to my inquiries is making me search these things out on my own, but the directional assistance of just getting it out of my head and down on the forum helps immensely.
I found the Modem/kernel repository, and am going to flash the FF18 modem to see if it turns out some better results. My question now is that all of the guide are telling me to flash CWM recovery kernel, like a whole new rom, you know. I was curious if I could just flash this zip with the TWRP recovery, and just be the end of it, or do I wipe catch/factory restore/dalvik too?
mosez.315 said:
Lol, I know now. The delay of any responses to my inquiries is making me search these things out on my own, but the directional assistance of just getting it out of my head and down on the forum helps immensely.
I found the Modem/kernel repository, and am going to flash the FF18 modem to see if it turns out some better results. My question now is that all of the guide are telling me to flash CWM recovery kernel, like a whole new rom, you know. I was curious if I could just flash this zip with the TWRP recovery, and just be the end of it, or do I wipe catch/factory restore/dalvik too?
Click to expand...
Click to collapse
I believe the newest TWRP allows you to flash modems now, so it should be as easy and downloading the FF18 Modem.zip and placing it on your internal storage, rebooting into TWRP recovery and flashing it. Just as a note, different modems work best on different phones.
So for example your phone might get fast 3G speeds on FF18 but get really slow 3G at FF02. 4G is also affected when flashing a new modem. So you have test out each modem if you want the best possible speed for your phone.
And sadly, AOKP at the moment does not allow you to update the phones Profile and PRL. Both of those actions together can fix signal and and speed issues from time to time.
Sent from my SPH-D710 using xda app-developers app
I have created this thread for all you SG-NOTEII Noobs & Senior Members!
The purpose of this thread is to limit the number of (sometimes useless) threads, that are created over a simple problem that can easily be solved by READING OR SEARCHING.
This is the Emergency thread!
*Did you run into a problem and need quick assistance?
*Do you have a question or concern about your SG-NOTEII device?
Don't panic just ask here and I or WE THE SG-NOTEII COMMUNITY will gladly help!
In case of Emergency!
Hey, I just installed the T889UVALL4 update, which fixes the Exynos exploit. I had my phone rooted before the update but then I had to UNroot it to even install or to see the update. So I wanted to know if I can still root with the same method as I did before using Odin and install CWM recovery with out bricking my device.
Unless there's a new root.
Sent from my SGH-T889 using xda app-developers app
No your safe to re-root. Same method.
Sent from my HTC One S using Tapatalk 2
Thanks. Came from iOS. Still new to the Android Eco System as far as Rooting/ Roms/Hacks/ etc. Didn't have to waste a thread :thumbup:
Sent from my SGH-T889 using xda app-developers app
this thread is................... awesome?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was notified there was an update available. I was rooted using CF auto root and after unrooting Super SU, I cannot get the update. It just says checking for updates... I try connecting to Kies but that wont connect. I am a noob in need of an expert. Right when I was starting to think I had a grasp of Android, I'm stuck. I'm on stock everything 4.1.1 and T889UVALK8
HELP!!
MarDog said:
I was notified there was an update available. I was rooted using CF auto root and after unrooting Super SU, I cannot get the update. It just says checking for updates... I try connecting to Kies but that wont connect. I am a noob in need of an expert. Right when I was starting to think I had a grasp of Android, I'm stuck. I'm on stock everything 4.1.1 and T889UVALK8
HELP!!
Click to expand...
Click to collapse
You Should Download and Flash A Custom Recovery For Your Note 2, Like CWM Or TWRP Through Odin. Then You Should Be Able To Flash A Newer Radio Or ROM.
Are You Looking For An OTA Update From Tmo?
MarDog said:
I was notified there was an update available. I was rooted using CF auto root and after unrooting Super SU, I cannot get the update. It just says checking for updates... I try connecting to Kies but that wont connect. I am a noob in need of an expert. Right when I was starting to think I had a grasp of Android, I'm stuck. I'm on stock everything 4.1.1 and T889UVALK8
HELP!!
Click to expand...
Click to collapse
update : Kies worked finally somehow. Not sure why it wasn't working the 10 other times I tried. Problem solved!
MarDog said:
update : Kies worked finally somehow. Not sure why it wasn't working the 10 other times I tried. Problem solved!
Click to expand...
Click to collapse
Probably Wasn't Properly Connecting To Kies. Glad It's Ok Now.
I'm sure this is a stupid question, but why can't I roam over to ATT? I have a Tmo value plan (post-paid unlimited) and when I'm in my companies datacenter, my Tmo connection is very poor- to the point where I miss calls and texts sometimes don't come through. I try manually choosing ATT from the provider list but it reports "not registered".
Am I doing something wrong? I should be able to roam over to ATT, right??
phdeez said:
I'm sure this is a stupid question, but why can't I roam over to ATT? I have a Tmo value plan (post-paid unlimited) and when I'm in my companies datacenter, my Tmo connection is very poor- to the point where I miss calls and texts sometimes don't come through. I try manually choosing ATT from the provider list but it reports "not registered".
Am I doing something wrong? I should be able to roam over to ATT, right??
Click to expand...
Click to collapse
Settings-More Settings-Mobile Settings-Data Roaming (check).
Sent from my SGH-T889 using xda premium
This is weird... i flashed CWM using ODIN and everything was fine... flashed a few roms and made backups just fine! This morning i went to flash the new MYROM- revolution and i boot in to CWM and press the "wipe data/factory reset" option and it would RESTART the recovery! i went to restore my current settings and it fell in to a boot loop. i flashed the CWM again via TOOLBOX/ODIN and still the same!!! i restored my original rom ( factory with root) and it booted but now i'm nervous to try anything im using the 6.0.2.7 version (the one that comes with the ROM manager app ). has anyone run into this kind of trouble??? any help would be appreciated!!!
jeibosquez said:
This is weird... i flashed CWM using ODIN and everything was fine... flashed a few roms and made backups just fine! This morning i went to flash the new MYROM- revolution and i boot in to CWM and press the "wipe data/factory reset" option and it would RESTART the recovery! i went to restore my current settings and it fell in to a boot loop. i flashed the CWM again via TOOLBOX/ODIN and still the same!!! i restored my original rom ( factory with root) and it booted but now i'm nervous to try anything im using the 6.0.2.7 version (the one that comes with the ROM manager app ). has anyone run into this kind of trouble??? any help would be appreciated!!!
Click to expand...
Click to collapse
Change your recovery to TWRP. Forget that "old" CWM....Too many problems with it.
premiatul said:
Change your recovery to TWRP. Forget that "old" CWM....Too many problems with it.
Click to expand...
Click to collapse
+1000000
Sent from my HTC One S using Tapatalk 2
premiatul said:
Change your recovery to TWRP. Forget that "old" CWM....Too many problems with it.
Click to expand...
Click to collapse
Belive me I tried to install TWRP and it wont get pass the team win "splash screen"... I've tried it more than once to no avail....
jeibosquez said:
Belive me I tried to install TWRP and it wont get pass the team win "splash screen"... I've tried it more than once to no avail....
Click to expand...
Click to collapse
Did you try to install it with GALAXY NOTE2 TOOLKIT?
http://forum.xda-developers.com/showthread.php?t=1957720
Never had any problems with that, so give it a go....
Quasi-bricked GN2 ... help please.
Hello -
I'm rooted and I was trying to install a different system font using Font Installer * Root * .
I followed the apps instructions and wound up with a bunch of Korean instead of where I thought the new font should be.
I then tried to re-boot and got stuck at the Samsung screen.
I have since tried to wipe / factory reset and flash the stock rom to no avail.
I have a Nandroid backup I created with Galaxy Note 2 Tool Kit but I don't know hot to re-install it.
Everything stops at the Samsung screen.
Help!
Thanks.
UPDATE: It's official -- I'm bricked. After hours of searching these fora it appears I need a Samsung signed stock 4.1.2 rom as I'm getting the "E:Signature verification failed" error and teshxx's ROM doesn't appear to be signed (is that correct?)
I'm stuck with the stock recovery and I really can't see any way out.
HELP please!
whatllitbenext said:
Hello -
I'm rooted and I was trying to install a different system font using Font Installer * Root * .
I followed the apps instructions and wound up with a bunch of Korean instead of where I thought the new font should be.
I then tried to re-boot and got stuck at the Samsung screen.
I have since tried to wipe / factory reset and flash the stock rom to no avail.
I have a Nandroid backup I created with Galaxy Note 2 Tool Kit but I don't know hot to re-install it.
Everything stops at the Samsung screen.
Help!
Thanks.
UPDATE: It's official -- I'm bricked. After hours of searching these fora it appears I need a Samsung signed stock 4.1.2 rom as I'm getting the "E:Signature verification failed" error and teshxx's ROM doesn't appear to be signed (is that correct?)
I'm stuck with the stock recovery and I really can't see any way out.
HELP please!
Click to expand...
Click to collapse
You are correct I hope you have insurance on your phone.
Sent from my HTC One S using Tapatalk 2
Question
If I have a tmobile note2 unlocked to use on AT&T and want to root and install Roms will it break the unlock? Where I have to have it unlocked again? I have searched everywhere and can't seem to find an answer except on really old phones.
AT&T Galaxy s3. I have no Internet. Everything else good. Can someone give the order of flashing. Does the update bootloader go on before the cm nighty and don't you wipe before doing both. I feel like I am doing something wrong.
tepeee said:
AT&T Galaxy s3. I have no Internet. Everything else good. Can someone give the order of flashing. Does the update bootloader go on before the cm nighty and don't you wipe before doing both. I feel like I am doing something wrong.
Click to expand...
Click to collapse
Can you post a screenshot of your "About device" settings? And by Internet do you mean your data doesn't work? If so that generally points to a modem issue. As for the order of flashing, it generally goes like this:
1. Wipe Data/Factory Reset
2. Install .zip
3. Wipe Cache/Dalvik Cache
4. Reboot
I me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
an data.
Terminal emulator says I have mi747ucdlk3 bootloader
tepeee said:
I meView attachment 2961324an data.
Click to expand...
Click to collapse
What bootloader is on your phone? The LK3 baseband is 4.1.1.
Does the bootloader go on after cm11 room and don't you need to wipe before or after flashing it? How can you tell what bootloader is on your phone? Thanks
check post #s 7-9-10 from here
http://forum.xda-developers.com/showthread.php?t=2893182
err on the side of kindness
---------- Post added at 11:49 AM ---------- Previous post was at 11:45 AM ----------
@audit13 :As for the order of flashing, it generally goes like this:
1. Wipe Data/Factory Reset
2. Install .zip
3. Wipe Cache/Dalvik Cache
4. Reboot
Someone tell me, does the bootloader go on first or after the cm11 rom?
The bootloader must always be loaded first. Without a bootloader, the ROM would not boot.
Wiping cache, dalvik, data, and system does not touch the bootloader or modem.
Audit, take a look up a few posts where I have a pic of my About phone. As far as I see I have the right bootloader. Remember I formatted everything, not wipe.
That screen shows your modem, not the bootloader.
If you have terminal emulator on your phone, open the app and type this in and let us know what it says:
su and press enter.
getprop ro.bootloader and press enter.
Try this if you don't have terminal emulator: boot into download mode and tell me what it says on the screen.
It's important to know which bootloader you have because that will determine what can be safely flashed to the phone.
Maybe this will help. I get this message after applying the rom right after applying the network name and password, (INSERT SIM CARD, You need to refer to your sim card instructions that came with your phone and there is a red android with on eye closed) . I have my bootloader listed in couple posts up.
Try flashing a more recent modem with this guide: http://forum.xda-developers.com/showthread.php?t=1831898
If no dice, update the bootloader with this guide: http://forum.xda-developers.com/showthread.php?t=2321310
That screen shot is not your bootloader, it is your modem. I don't recommend flashing any modem or bootloader related until your find out what it is.
I also have a Nexus 4 and when I got to the "About" screen, it tells me my modem is 1.0.3 but I know my bootloader not 1.0.3.
audit13 said:
That screen shot is not your bootloader, it is your modem. I don't recommend flashing any modem or bootloader related until your find out what it is.
I also have a Nexus 4 and when I got to the "About" screen, it tells me my modem is 1.0.3 but I know my bootloader not 1.0.3.
Click to expand...
Click to collapse
He updated one of his posts. "Terminal emulator says I have mi747ucdlk3 bootloader"
NikoZBK said:
He updated one of his posts. "Terminal emulator says I have mi747ucdlk3 bootloader"
Click to expand...
Click to collapse
OMG. I am so embarrassed. Thank you NikoZBK for pointing this out.
Teepee, my apologies for not thoroughly reading your post
It is possible that CM11 is not completely compatible with the 4.1.1 modem. Try installing CM10.2 to see if you can get internet access over your data connection. If you can, try updating the modem and bootloader as NikoZBK suggested.
If you want, you could also flash back to unroot stock 4.1.1 and run OTA updates to get all the way to stock 4.4.2.
audit13 said:
OMG. I am so embarrassed. Thank you NikoZBK for pointing this out.
Teepee, my apologies for not thoroughly reading your post
It is possible that CM11 is not completely compatible with the 4.1.1 modem. Try installing CM10.2 to see if you can get internet access over your data connection. If you can, try updating the modem and bootloader as NikoZBK suggested.
If you want, you could also flash back to unroot stock 4.1.1 and run OTA updates to get all the way to stock 4.4.2.
Click to expand...
Click to collapse
Seconded. And no problem. :good: I almost missed it myself.
First off let me thank the two of you for all your help. If you haven't noticed, you are dealing with someone with very little knowledge lol. If you go back to post #11 I updated the exact message I am getting. Are there any links you can give me on running OTA updates and how to flash back to unroot stock 4.11.
tepeee said:
First off let me thank the two of you for all your help. If you haven't noticed, you are dealing with someone with very little knowledge lol. If you go back to post #11 I updated the exact message I am getting. Are there any links you can give me on running OTA updates and how to flash back to unroot stock 4.11.
Click to expand...
Click to collapse
The easiest way to get back to stock and run OTA updates is this:
1) download the stock ATT 4.1.1 ROM from sammobile.com. Just search for the sgh-i747.
2) put your phone into download mode but don't connect it to your computer;
2) launch Odin and click on the PDA box and browse for the ROM file. The ROM file should now appear in the PDA box.
3) don't check anything in Odin except F.Reset Time;
4) connect your phone to the computer and flash the ROM in Odin by clicking on the start button;
5) when you see the word "Reset" in the Odin status window, disconnect the usb cable, pull the battery, replace the battery, boot into recovery, wipe cache and data, boot the phone.
The phone should now be running a completely stock 4.1.1 ROM. At this point, I would test out your data connection to make sure everything is working. If everything is working and you want to update via OTA, just connect to wifi and check for software updates directly from your phone.
Be aware of the fact that rooting on stock 4.3 and stock 4.4.2 can be trickier because Knox will be loaded onto your phone after running the OTA update to 4.3.
Just a quick FYI, if I may... as I understand it, the latest cm releases will have to be run on the 4.4.2 bootloader and modem. They apparently updated the radio/ril files and they don't play well with our older modems.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Would anything bad happen if I tried to format the boot folder? Thinking of formatting everything I can if it won't hurt my phone?
I was running rooted stock version of kit kat. Yesterday afternoon I had Google Music running while doing housework when suddenly the music stopped. I checked the phone and the screen was black and would not turn on. Pulled the battery and then it stuck at the AT&T logo for 30+ minutes. I booted into CWM to perform a factory reset and potentially reinstall the ROM from the external sd card. The factory reset produced the following error.
Code:
--Wiping Data ...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache
Formatting /sdcard/.android_secure...
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete
Fiddled around more with CWM to reset and try to fix. Now, upon reboot, it hands at the Samsung Galaxy Note II screen.
Any help on fixing this so it can at least limp along until my Nexus 6 gets here would be greatly appreciated.
Use Phil touch recovery, and use wipe\clean to install new ROM. Should fix your problem. Also if you are going to a Nexus 6 you should try CM11 when u flash a new ROM.
If you want to use CWM then just format the system and flash a new ROM.
Sent from my GT-N7105 using XDA Free mobile app
I'm unfamilair with Phil Touch recovery.
Can I flash it using JOding on OSX?
ShrekOpher said:
Use Phil touch recovery, and use wipe\clean to install new ROM. Should fix your problem. Also if you are going to a Nexus 6 you should try CM11 when u flash a new ROM.
If you want to use CWM then just format the system and flash a new ROM.
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
John.T.Erskine said:
I'm unfamilair with Phil Touch recovery.
Can I flash it using JOding on OSX?
Click to expand...
Click to collapse
You can check here
http://forum.xda-developers.com/showthread.php?t=2201860
Sent from my SHIELD Tablet using XDA Free mobile app
Odin doesn't recognize the device. It could be the browser version running on an old macbook pro, but I believe it is the fact that the phone's internal sd card is corrupted somehow.
John.T.Erskine said:
Odin doesn't recognize the device. It could be the browser version running on an old macbook pro, but I believe it is the fact that the phone's internal sd card is corrupted somehow.
Click to expand...
Click to collapse
Have you tried formating the data and system from cwm?
Go into recovery and go to "advanced" and select format system and/or format data.
Sent from my GT-N7105 using XDA Free mobile app
Tried that and received the same error as the OP. Can not mount SD card.
ShrekOpher said:
Have you tried formating the data and system from cwm?
Go into recovery and go to "advanced" and select format system and/or format data.
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
Same issue
I'm having the same issue as OP. The phone won't get back to recovery. Won't even go into download mode.......Please help!
Edit: I was so used to working on my wife's phone (Note 1) that I was using the wrong button combination for download mode. I still can't get back to recovery, but I'll be ok once I get home.
Try to flash stock rom in Odin. That should fix any errors but if you're still getting errors there's other stuff to try
absinthesummer said:
Try to flash stock rom in Odin. That should fix any errors but if you're still getting errors there's other stuff to try
Click to expand...
Click to collapse
Not the OP but I just tried this with KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar and it did not help.
Here's what I have done thus far:
1. Reflash the stock ROM from sammobile via ODIN
2. Ends in a FAIL on sboot.img
3. Phone says unsupported version (I believe this is due to the Knox locking. I can't downgrade)
4. Reflash recovery-clockwork-touch-6.0.4.3-t0lteatt.img using Heimdall
5. Wipe data, cache, and Dalvik cache (noting the errors regarding the /data partition still occur)
5. Sideload cm-11-20141008-SNAPSHOT-M11-t0lte.zip
6. Sideload gapps-kk-20140606-signed.zip
7. Reboot the phone
8. Stuck in a boot loop on the cyanogenmod logo
Thoughts on where to go from here? Tearing my hair out.
ProjektTHOR said:
Not the OP but I just tried this with KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar and it did not help.
Here's what I have done thus far:
1. Reflash the stock ROM from sammobile via ODIN
2. Ends in a FAIL on sboot.img
3. Phone says unsupported version (I believe this is due to the Knox locking. I can't downgrade)
4. Reflash recovery-clockwork-touch-6.0.4.3-t0lteatt.img using Heimdall
5. Wipe data, cache, and Dalvik cache (noting the errors regarding the /data partition still occur)
5. Sideload cm-11-20141008-SNAPSHOT-M11-t0lte.zip
6. Sideload gapps-kk-20140606-signed.zip
7. Reboot the phone
8. Stuck in a boot loop on the cyanogenmod logo
Thoughts on where to go from here? Tearing my hair out.
Click to expand...
Click to collapse
Yes that's definitely KNOX bootloader kicking back your flash attempts in odin. MA4 is pretty old firmware. You need MK6 or NE5. Here's where you can get the latest 4.3-4.4.2 firmwares: http://forum.xda-developers.com/galaxy-note-2-att/development/rom-att-i317-ucucne5-mj4-stock-odex-t2802189
This should correct the data issue, if not, you may need to grab a pit file, but usually flashing the latest stock fixes it without requiring all that.
Flash that, re-root, flash new recovery (note: use a newer recovery, cwm sometimes has issues with our device, but twrp has been updated to work with 4.3+ same with philz, if you prefer that UI. Once 4.4.4 comes out, it doesn't play well with cwm, philz, OR older versions of twrp- I had a fight with a note 3 and recoveries yesterday, finally got it going with the latest twrp).
Boot up the device, flash/update your supersu. If you want to install a different rom now, go ahead. Once you have a new recovery installed, format (manually) /system /data /internal storage /cache /dalvik. The internal storage is important b/c it's usually what causes the /data corruption. Always wipe internal storage when switching between roms (or even between an update, I do). I don't usually wipe everything 3 times like some people do, but it is important to wipe the essentials. In twrp, internal storage is an option when wiping. In cwm & philz, you have to go under mounts & storage & it's second up from the bottom (format /data including /data/media> sdcard). Then back out to the main recovery menu and flash your rom, if you have any issues reboot recovery (not system) and re-flash it.
One more thing, make sure you have enough system storage for the gapps. I've run into issues where the rom flashed fine but gapps was too big for the system and didn't flash correctly. Try a slim gapps
Hope this helps, if you have any other questions I'm happy to try to help. We'll get it fixed for ya
Not able to flash other ROMS besides Stock now.......
In my previous post, I was able to get to download mode and flashed back to stock. I thought I was flashing At&t Stock 4.3, but was really flashing At&t 4.1.2 Stock.
I guess it would help to state what happened and the order of things. I'm at work so I don't have the exact versions for each file used, but I'll try my best. I was running DN3 v3.1.1. Something was happening where there was very little space left on my internal storage and I felt like it was time to try a different Rom since I had been on this for a few months as a daily.
1. I flashed BlissStalk with no issues, just didn't care much for the Rom (no hate, just not my cup of tea!)
2. Next I flashed CyanideMod and didn't care for that either. No issues, just wasn't my cup of tea.
3. I then attempted to flash the DS NE5 Rom, using CWM, and it would come on and show the Samsung Galaxy Note II screen and then go black. I had to do a battery pull to get anywhere and then it would come back on and get back to the Galaxy Note II screen and freeze there, or cut off completely again. This is what brought me here to this thread.
I was able to go back to stock 4.1.2, then stock 4.3, and even now on stock 4.4.2. But now I can't flash any Rom at all without getting stuck. I tried to flash DN3's latest and keep getting stuck at the second Samung Screen. I have tried to reboot and tried to reflash as the help says. I am reading through various topics and FAQ pages, but I figured this may be more than any particular Rom issue (I've tried flashing other Roms and I'm getting stuck on those too-either stuck at logos or turning off completely). I have to keep flashing back to stock.
I am researching this, even while at work, but does anyone have any idea what could be wrong?
PS Even though I don't state it above, I followed all flashing directions to a T!
dirtyalphaman said:
In my previous post, I was able to get to download mode and flashed back to stock. I thought I was flashing At&t Stock 4.3, but was really flashing At&t 4.1.2 Stock.
I guess it would help to state what happened and the order of things. I'm at work so I don't have the exact versions for each file used, but I'll try my best. I was running DN3 v3.1.1. Something was happening where there was very little space left on my internal storage and I felt like it was time to try a different Rom since I had been on this for a few months as a daily.
1. I flashed BlissStalk with no issues, just didn't care much for the Rom (no hate, just not my cup of tea!)
2. Next I flashed CyanideMod and didn't care for that either. No issues, just wasn't my cup of tea.
3. I then attempted to flash the DS NE5 Rom, using CWM, and it would come on and show the Samsung Galaxy Note II screen and then go black. I had to do a battery pull to get anywhere and then it would come back on and get back to the Galaxy Note II screen and freeze there, or cut off completely again. This is what brought me here to this thread.
I was able to go back to stock 4.1.2, then stock 4.3, and even now on stock 4.4.2. But now I can't flash any Rom at all without getting stuck. I tried to flash DN3's latest and keep getting stuck at the second Samung Screen. I have tried to reboot and tried to reflash as the help says. I am reading through various topics and FAQ pages, but I figured this may be more than any particular Rom issue (I've tried flashing other Roms and I'm getting stuck on those too-either stuck at logos or turning off completely). I have to keep flashing back to stock.
I am researching this, even while at work, but does anyone have any idea what could be wrong?
PS Even though I don't state it above, I followed all flashing directions to a T!
Click to expand...
Click to collapse
Ok so you've got the ne5 bootloader, so any time you flash stock you'll have to flash that version or above. Stock rom works, but custom ones don't, correct?
What's weird is that the latest dn3 is a modified stock rom so that shouldn't be an issue.
When you flashed stock, you re-rooted and did you update super su? I'm sure you already know but you should update super su's binaries & let it disable Knox, which will set your seLinux from enforcing to permissive. That could potentially be a reason why you can't flash new roms, Knox & selinux interfering with the kernel flash part of the rom(s) you're trying. If you haven't done this you may want to try and then try flashing a custom rom again. If you still encounter issues I'll try to help.
---------- Post added at 12:32 PM ---------- Previous post was at 12:21 PM ----------
John.T.Erskine said:
I'm unfamilair with Phil Touch recovery.
Can I flash it using JOding on OSX?
Click to expand...
Click to collapse
Also, cwm is pretty old and prone to bugs on our devices. However philz is based on cwm and very similar in terms of user interface. It's not as different as twrp is. It has the same style and setup just a few additional tools that cwm doesn't have. It's also more compatible with our devices. If I had to choose one I wouldn't choose cwm, I'd go with philz or twrp for the sake of compatibility.
Thanks. I'll try this when I get home. Yea, once I flashed stock I kept getting Security Notices. I saw this was due to Knox and disabled it but that was a few flash attempts ago. I will follow you steps and let you know how it goes. Once again, thanks.
absinthesummer said:
Yes that's definitely KNOX bootloader kicking back your flash attempts in odin. MA4 is pretty old firmware. You need MK6 or NE5. Here's where you can get the latest 4.3-4.4.2 firmwares: http://forum.xda-developers.com/galaxy-note-2-att/development/rom-att-i317-ucucne5-mj4-stock-odex-t2802189
This should correct the data issue, if not, you may need to grab a pit file, but usually flashing the latest stock fixes it without requiring all that.
Click to expand...
Click to collapse
You are a saint. I'm not sure why I was struggling to find stock 4.4-series firmwares that could be flashed. I was so focused on getting them from sammobile or samware-firmware that I didn't even think to look here. I am going to try this process today and let you know if it works out!
absinthesummer said:
When you flashed stock, you re-rooted and did you update super su? I'm sure you already know but you should update super su's binaries & let it disable Knox, which will set your seLinux from enforcing to permissive. That could potentially be a reason why you can't flash new roms, Knox & selinux interfering with the kernel flash part of the rom(s) you're trying. If you haven't done this you may want to try and then try flashing a custom rom again. If you still encounter issues I'll try to help.
Click to expand...
Click to collapse
I really think this is my issue. I tried updating Super SU by flashing 1.75, but I think that's old. It doesn't show up and when I download it from the PLAY store, it says there is no SU Binary. It's too late to fiddle with this now, but I will mess around with it tomorrow. I think I lost my root and it's not trying to let me get it back. But I don't give up that easy. I was looking through the sticky thread to get the most up to date SU flash, but because it's late and I had a lot going on, this project will have to wait until tomorrow. Thanks for your help and I will let you know what happens tomorrow.
dirtyalphaman said:
I really think this is my issue. I tried updating Super SU by flashing 1.75, but I think that's old. It doesn't show up and when I download it from the PLAY store, it says there is no SU Binary. It's too late to fiddle with this now, but I will mess around with it tomorrow. I think I lost my root and it's not trying to let me get it back. But I don't give up that easy. I was looking through the sticky thread to get the most up to date SU flash, but because it's late and I had a lot going on, this project will have to wait until tomorrow. Thanks for your help and I will let you know what happens tomorrow.
Click to expand...
Click to collapse
Sounds like you've figured it out. 1.75 is very old. Latest (stable) is 2.16. There are also beta versions out. I can link you to the latest flashable in the morning.
You may want to re-root via cf auto root if you can't get it to flash, but if you've got access to recovery a flash to the latest supersu should take... it's just not with 1.75 because those binaries are so outdated, it likely can't overpower enforcing selinux. That has been resolved in newer versions. I'm almost positive you'll be fine with a newer supersu/root.
Edit:
here's the link to 2.16 zip download: http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip
And here's a link to chainfire's thread so you can bookmark it & always have access to the latest:
http://forum.xda-developers.com/showthread.php?t=1538053
absinthesummer said:
Sounds like you've figured it out. 1.75 is very old. Latest (stable) is 2.16. There are also beta versions out. I can link you to the latest flashable in the morning.
You may want to re-root via cf auto root if you can't get it to flash, but if you've got access to recovery a flash to the latest supersu should take... it's just not with 1.75 because those binaries are so outdated, it likely can't overpower enforcing selinux. That has been resolved in newer versions. I'm almost positive you'll be fine with a newer supersu/root.
Edit:
here's the link to 2.16 zip download: http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip
And here's a link to chainfire's thread so you can bookmark it & always have access to the latest:
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
Hey, this worked for my root. I installed and updated the SU Binary. It got stuck trying to disable Knox, but I rebooted and went right back to it--Knox was disabled in a few seconds! Thanks again. I will wait until I get home to try to flash again because I would hate to end up stuck at work without my phone working and also because..........my name.......my name is Ken. And I.......I'm a flashaholic...........
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dirtyalphaman said:
Hey, this worked for my root. I installed and updated the SU Binary. It got stuck trying to disable Knox, but I rebooted and went right back to it--Knox was disabled in a few seconds! Thanks again. I will wait until I get home to try to flash again because I would hate to end up stuck at work without my phone working and also because..........my name.......my name is Ken. And I.......I'm a flashaholic...........
Click to expand...
Click to collapse
Awesome! Good luck (and I think we're all flash-aholics)
Thank you for all of your help!!! Flashed the latest DN5 rom and it's working great. I found an issue that might have been preventing me from flashing earlier besides the botched root. My external sd card is having a few issues. A week or so ago it changed to read only and wouldn't let me move any files to or from it. Tonight it wouldn't let me flash the rom, but it worked when moved the rom to the internal storage. So I'm good to go! Can't thank you enough!
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
I'm currently stucked and don't know what to do. I have installed odin and several stock firmware. I odin ob7 and it tell me that message. I'm fustrated and thinking about buying iphone 5.
Chubby19865 said:
I'm currently stucked and don't know what to do. I have installed odin and several stock firmware. I odin ob7 and it tell me that message. I'm fustrated and thinking about buying iphone 5.
Click to expand...
Click to collapse
Please, get the iPhone 5......
Chubby19865 said:
I'm currently stucked and don't know what to do. I have installed odin and several stock firmware. I odin ob7 and it tell me that message. I'm fustrated and thinking about buying iphone 5.
Click to expand...
Click to collapse
Did you start in OE1 build? If you wiped system and don't have a nandroid backup, look in development section for Noterized Stable 2 and flash that in recovery. If you don't have custom recovery or root, you can still use Odin for root and recovery tars.
If you haven't rooted or flashed stock recovery, a battery pull or factory reset may get you going again on stock. I'd wait for the next OTA if that is the case. Can't say when OTA is coming but since the last update wasn't supported with a tar, it should be forthcoming.
If no, Odin should give a failure. Did it complete with a success message? A tell here is a message stating something to the effect of aboot not authorized; shortened in parenthesis.
Sent from my SM-N910P using Tapatalk
xxSTARBUCKSxx said:
Please, get the iPhone 5......
Click to expand...
Click to collapse
really ?? LOLL.
Chubby19865 said:
really ?? LOLL.
Click to expand...
Click to collapse
Mmhmm. Giving the title to your post that you did and the fact that the frustration alone with Android wants you to venture to Apple, it seems that an iPhone would be your best option. Id go with the 6 Plus, personally(on my deathbed of course), but you mentioned the iPhone 5, so I stuck with the 5 also in my reply.
I got alliance rom running. I am done messing with my note 4.
I unrooted oe1 easily
I am having the same issue. I was on stock rooted with TWRP recovery. I tried switching over to stock deodexed and have got nothing but boot loops it doesn't even go past the note 4 screen. I've since tried using odin to put the stock rom on and everything fails. I can not flash zips either I've been doing all clean installs. Any ideas as to how I can get my phone working again?
xda Zed said:
I am having the same issue. I was on stock rooted with TWRP recovery. I tried switching over to stock deodexed and have got nothing but boot loops it doesn't even go past the note 4 screen. I've since tried using odin to put the stock rom on and everything fails. I can not flash zips either I've been doing all clean installs. Any ideas as to how I can get my phone working again?
Click to expand...
Click to collapse
@Chubby19865 got Alliance working. I believe its either that or Noterized youll have to flash until either another OTA or .tar comes out.
You have the same issue I did. What i did was i flashed the ob7 modem via odin. I also install philz cwm, since i couldn't transfer files with twrp. I also made a backup with cwm before i did everything. For you, you should flashed bob7 modem and wipe and install alliance rom. That's what i did.
@xda Zed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I get nothing but fails this is OB7 from sammobile
http://imgur.com/IvD7JaG
xda Zed said:
I get nothing but fails this is OB7 from sammobile
http://imgur.com/IvD7JaG
Click to expand...
Click to collapse
You cant go down that route in the situation youre in. Flash just the Modem, not the entire firmware, then flash the Alliance rom.
Im happily on NK2 after not being impressed with Lollipop(well-named IMO, it does suck indeed), so i cant speak on the TWRPvsCWM for recovery and file transfer chubby mentioned.
I flashed the modem it went through but I am still getting boot loops.
---------- Post added at 02:31 AM ---------- Previous post was at 02:22 AM ----------
xda Zed said:
I flashed the modem it went through but I am still getting boot loops.
Click to expand...
Click to collapse
I can flash zips in recovery but nothing happens..
xda Zed said:
I flashed the modem it went through but I am still getting boot loops.
---------- Post added at 02:31 AM ---------- Previous post was at 02:22 AM ----------
I can flash zips in recovery but nothing happens..
Click to expand...
Click to collapse
Are you waiting long enough? If i remember correctly, the lollipop roms can take anywhere from 10-15 on first boot.
Only thing i can suggest is a Battery Pull, Wipe, Flash Modem, Wipe, Flash Alliance.
xda Zed said:
I flashed the modem it went through but I am still getting boot loops.
---------- Post added at 02:31 AM ---------- Previous post was at 02:22 AM ----------
I can flash zips in recovery but nothing happens..
Click to expand...
Click to collapse
Maybe that's what @Chubby19865 was referring to when he used Philz recovery?
That project is no longer updated but apparently still works. I think it was gotten from this link but use at your own risk. A confirmation would be nice.
http://forum.xda-developers.com/showpost.php?p=39433458&postcount=1
Ditto on the wait reply. What do you see with TWRP flash and initial boot?
Uncharted waters for us trying to help not on the OE1 blues but the custom lollipop ROMs have to optimize and start the dalvik-cache directory with art dex files.
Sent from my SM-N910P using Tapatalk
xxSTARBUCKSxx said:
Are you waiting long enough? If i remember correctly, the lollipop roms can take anywhere from 10-15 on first boot.
Only thing i can suggest is a Battery Pull, Wipe, Flash Modem, Wipe, Flash Alliance.
Click to expand...
Click to collapse
I tried that I can feel it vibrate and see the screen reset I am getting nowhere...
xda Zed said:
I tried that I can feel it vibrate and see the screen reset I am getting nowhere...
Click to expand...
Click to collapse
Lemme go through some of the OE1 threads and see what I can find.
http://forum.xda-developers.com/showpost.php?p=61026642&postcount=17
Apparently this needs to be placed on your SD and flash that? Still searching for a more defined "process of steps"
FYI... TWRP was mentioned, so if youre using philz(cwm) id use TWRP for that process. Lemme pilfer some more.
http://forum.xda-developers.com/showpost.php?p=61642915&postcount=75
xda Zed said:
This was OB7 from OB7
Click to expand...
Click to collapse
what did you just call me?
And as samep just suggested, last but not least...
Chubby19865 said:
For you, you should flashed bob7 modem and wipe and install alliance rom. That's what i did.
@xda Zed
Click to expand...
Click to collapse
This was OB7 from OB7 I just tried to flash a deodexed version of stock (Clean) and have not been able to get anything but a bootloop since. =(
xxSTARBUCKSxx said:
Lemme go through some of the OE1 threads and see what I can find.
Click to expand...
Click to collapse
You've already covered half of what @Chubby19865 suggested.
What's left? Odin Philz CWM Recovery, CWM nandroid backup (if system wasn't already wiped). Wipe and flash Alliance.
http://forum.xda-developers.com/showpost.php?p=61667056&postcount=10
To my recollection, there's only two users that posted success in flashing anything but Noterized.
@DreamingWolf was the other I recall. He primarily used an old OB7 nandroid to get back. But from all reading and recollection, Odin stock tars remain broken for OE1 OTA update. Without a tar to fall back on, that's a sad place to be.
Sent from my SM-N910P using Tapatalk
Ok.. i need to go on a beer run, this is most annoying not being able to assess the situation from your side of things or id be able to give you step by step instructions. Try flashing Noterized in the meantime though instead of deodexed stock. Ill be back shortly.