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?
Related
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
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.
I had this problem with every ROM, when you load the boot animation to give his first vibration when you start to put your information, freezes and restarts. restarted like 5 times. download all the 4.3 Roms to the forum t989 but all feel the same.
Wipe the internal and external memory. so try and nothing. I went back to Stock Rom 2.3.6, I redid the Root. everything perfect. UVMC6 also install radio perfect, but still, still doing the same. I have a backup copy of AOKP 4.2.2 and as I have been much with it, I want to upgrade to 4.3 or 4.3.1 any help would really really bothers me and trying everything to update and no fun.
josue276 said:
I had this problem with every ROM, when you load the boot animation to give his first vibration when you start to put your information, freezes and restarts. restarted like 5 times. download all the 4.3 Roms to the forum t989 but all feel the same.
Wipe the internal and external memory. so try and nothing. I went back to Stock Rom 2.3.6, I redid the Root. everything perfect. UVMC6 also install radio perfect, but still, still doing the same. I have a backup copy of AOKP 4.2.2 and as I have been much with it, I want to upgrade to 4.3 or 4.3.1 any help would really really bothers me and trying everything to update and no fun.
Click to expand...
Click to collapse
What version and recovery are you using? What's your flashing process?
Still_living714 said:
What version and recovery are you using? What's your flashing process?
Click to expand...
Click to collapse
All Wipe ( Wipe Factory Reset, System, Data, Cache)
And Version Recovery TWRP 2.6.1.0 and CWM and nothing.
josue276 said:
All Wipe ( Wipe Factory Reset, System, Data, Cache)
And Version Recovery TWRP 2.6.1.0 and CWM and nothing.
Click to expand...
Click to collapse
I had a issue sorta like yours and I think had bad download of recovery I was using. I went through everything like you did and even used ODIN to back to stock reflashed and same problems. I switch versions of Recovery and retried and everything is smooth since.
msg1285 said:
I had a issue sorta like yours and I think had bad download of recovery I was using. I went through everything like you did and even used ODIN to back to stock reflashed and same problems. I switch versions of Recovery and retried and everything is smooth since.
Click to expand...
Click to collapse
that version installed to see if I will? and use TWRP and several CWM 2.6.1.0. which you worked for you?
Here a picture with TWRP 2.6.1.0 and I think a clean install
{
"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"
}
and here another after the boot animation that is where it freezes and reboots.
Hmmm this is weird. Flash your recovery thru Odin again and try it then
JesusWazBlack said:
Hmmm this is weird. Flash your recovery thru Odin again and try it then
Click to expand...
Click to collapse
I am on TWRP 2.6.1.0 as well.
I install the rom only no gapps or anything extra and let it boot and see what happens.
I know it may not be poss now but you could try taking out your ext-sd card and simm card and boot just from the internal drive.
I don't know that it would help but it can't hurt and it reduces variables.
msg1285 said:
I am on TWRP 2.6.1.0 as well.
I install the rom only no gapps or anything extra and let it boot and see what happens.
I know it may not be poss now but you could try taking out your ext-sd card and simm card and boot just from the internal drive.
I don't know that it would help but it can't hurt and it reduces variables.
Click to expand...
Click to collapse
now just try and pass the same freezes and gives reboot. : (
I feel stupid with this!
josue276 said:
now just try and pass the same freezes and gives reboot. : (
I feel stupid with this!
Click to expand...
Click to collapse
If you have tried a differnt version of TWRP and differnt 4.3 roms all on a clean install, I don't know what else to recommend.
msg1285 said:
If you have tried a differnt version of TWRP and differnt 4.3 roms all on a clean install, I don't know what else to recommend.
Click to expand...
Click to collapse
I can not wipe preload! believe they have to with this error?
and repair as to wipe Preload!. but still! boot freezes and reboots!! ANNOYING!!!!
josue276 said:
and repair as to wipe Preload!. but still! boot freezes and reboots!! ANNOYING!!!!
Click to expand...
Click to collapse
Hey i have the exact same problem! idk what happened, it's fine on 4.1.2 but right when i update to 4.2.2, not even 4.3 it does the exact same thing! any devs have any ideas? idk if a logcat will help in this case
why not just use another recovery like cwm and see if it works with that one.
Still_living714 said:
why not just use another recovery like cwm and see if it works with that one.
Click to expand...
Click to collapse
I use CWM. is the same.
You need completely wipe everything in order to flash a 4.3 ROM for the first time some times.
Sent from my SGH-M919 using xda premium
'Murica said:
You need completely wipe everything in order to flash a 4.3 ROM for the first time some times.
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
I did a full wipe. but nothing. Even now install the rom Cyanogenmod11
and only get to change language but then freezes and reboots. I was very excited because I thought that had already been arranged until he gave me the error. dont know what else to do to upgrade my phone!
msg1285 said:
I had a issue sorta like yours and I think had bad download of recovery I was using. I went through everything like you did and even used ODIN to back to stock reflashed and same problems. I switch versions of Recovery and retried and everything is smooth since.
Click to expand...
Click to collapse
JesusWazBlack said:
Hmmm this is weird. Flash your recovery thru Odin again and try it then
Click to expand...
Click to collapse
Still_living714 said:
What version and recovery are you using? What's your flashing process?
Click to expand...
Click to collapse
try another board that had saved because it has the USB damaged. try to set you up for the 4.2, 4.3 and 4.4 and also gave me freeze and reboot. and wipe everything very well. I can not be!. but a problem has to see. do not know if I can be my navigation buttons are damaged (broken wire). believe you can be what makes my phone restart?
I had this issue i just updated my twrp. Maybe you should download TWRP from a different source? Maybe the one you have is corrupted or something . IDK try everything.
this doesn't help any, just wanted to confirm the same issue. Anytime I flash ROM above 4.1.2 on this phone it crashes in some way. any custom ROM
Sent from my SGH-T989 using xda app-developers app
i'm sure people post stuff about this all the time, but as of right now i'm stuck in TWRP with no OS, and none of the ROMs i'm trying to use are working at all. i've tried cyanogen, and a couple other random ones i found here, and absolutely nothing is working. could anyone maybe PM me or something and help me through this i have no idea where i went wrong.
dokibot said:
i'm sure people post stuff about this all the time, but as of right now i'm stuck in TWRP with no OS, and none of the ROMs i'm trying to use are working at all. i've tried cyanogen, and a couple other random ones i found here, and absolutely nothing is working. could anyone maybe PM me or something and help me through this i have no idea where i went wrong.
Click to expand...
Click to collapse
I have to ask a preliminary question. What is your boot loader (is it the lastest (4.3))? If your bootloader IS not the latest then there are many ways to "start fresh" by flashing the Stock Rom in ODIN. Ill wait for your reply and guide you further.
imcol said:
I have to ask a preliminary question. What is your boot loader (is it the lastest (4.3))? If your bootloader IS not the latest then there are many ways to "start fresh" by flashing the Stock Rom in ODIN. Ill wait for your reply and guide you further.
Click to expand...
Click to collapse
how can i check my bootloader version?
dokibot said:
how can i check my bootloader version?
Click to expand...
Click to collapse
Quite honestly I dont know how to check from the recovery but which version of stock were you on? 4.3? 4.1.2?
---------- Post added at 07:17 PM ---------- Previous post was at 07:16 PM ----------
I also feel that you can wipe you data, internal data, system, cache and dalvik (which will delete everything) and then push the correct roms and gaaps thorough ABD so you wouldnt need to go back to stock
imcol said:
Quite honestly I dont know how to check from the recovery but which version of stock were you on? 4.3? 4.1.2?
Click to expand...
Click to collapse
i'm probably on 4.1.2 but honestly i'm not 100% sure because it was given to me and i didn't think to check. wow i made a big mistake.
dokibot said:
i'm probably on 4.1.2 but honestly i'm not 100% sure because it was given to me and i didn't think to check. wow i made a big mistake.
Click to expand...
Click to collapse
Alright... If we knew what version your on (for sure) then it would have been quite easy. What model phone do you have? i747 or i747m?
imcol said:
Alright... If we knew what version your on (for sure) then it would have been quite easy. What model phone do you have? i747 or i747m?
Click to expand...
Click to collapse
says on the back it's a SGH-1747. thought i'm almost 90% positive the phone was mostly unused when the update was released
dokibot said:
says on the back it's a SGH-1747. thought i'm almost 90% positive the phone was mostly unused when the update was released
Click to expand...
Click to collapse
okay... I have an easy solution for you on how to get your phone back to working condition but thats only if you have the older boot loader. If you flash the stock rom and you have the updated boot loader (that comes with 4.3) your phone will hard brick. If your willing to take the risk I can guide you further.
imcol said:
okay... I have an easy solution for you on how to get your phone back to working condition but thats only if you have the older boot loader. If you flash the stock rom and you have the updated boot loader (that comes with 4.3) your phone will hard brick. If your willing to take the risk I can guide you further.
Click to expand...
Click to collapse
is there any way i'd able to tell the difference with like a screenshot or something? i'd recognize it if there was a difference in the homescreen. then i'd be able to tell which one i had?
dokibot said:
is there any way i'd able to tell the difference with like a screenshot or something? i'd recognize it if there was a difference in the homescreen. then i'd be able to tell which one i had?
Click to expand...
Click to collapse
!This is 4.3!
{
"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"
}
!This is 4.1.1!
imcol said:
!This is 4.3!
!This is 4.1.1!
Click to expand...
Click to collapse
okay i'm gonna go with 4.3 then. i think that's the one!
dokibot said:
okay i'm gonna go with 4.3 then. i think that's the one!
Click to expand...
Click to collapse
Lol okay, I'm curious as to how you rooted your phone?
imcol said:
Lol okay, I'm curious as to how you rooted your phone?
Click to expand...
Click to collapse
i used Odin3 to root it.
dokibot said:
how can i check my bootloader version?
Click to expand...
Click to collapse
There is a difference that could be seen when you are in download mode due to Knox on the 4.3 update. Upload a picture of your download mode and we can advise you from there.
Sent from my awesome phone.
dokibot said:
i used Odin3 to root it.
Click to expand...
Click to collapse
Okay, from everything you've said here is the best solution that has the least percent of messing up.
Follow everything carefully and you should be good as new!
Boot into TWRP
Wipe DATA/FACTORY RESET
Wipe CACHE
Wipe DALVIK
Format SYSTEM
MOUNT your internal storage to the computer
***TAKE BACKUP OF PICTURES, ETC. from internal storage***
DELETE everything in the internal storage once you take backup, if needed
*** Based on your phone model and everything else I did most of the work and found the correct links, if you dont trust them search CM and 4.3 Gaaps and download them ***
COPY Stable rom to internal storage - here is cyanogenmod 10.2.1 stable for ATT i747: https://download.cyanogenmod.org/get/jenkins/57775/cm-10.2.1-d2att.zip
COPY Gaaps zip to internal storage - here is PA gaaps 4.3: http://www.mediafire.com/download/n2a7nta3jrj1ltk/pa_gapps-modular-mini-4.3-20131024-signed.zip
UNMOUNT internal storage
Flash CM
Flash Gaaps
Clear CACHE
Clear DALVIK
Reboot! You should be good to go
imcol said:
Okay, from everything you've said here is the best solution that has the least percent of messing up.
Follow everything carefully and you should be good as new!
Boot into TWRP
Wipe DATA/FACTORY RESET
Wipe CACHE
Wipe DALVIK
Format SYSTEM
MOUNT your internal storage to the computer
***TAKE BACKUP OF PICTURES, ETC. from internal storage***
DELETE everything in the internal storage once you take backup, if needed
*** Based on your phone model and everything else I did most of the work and found the correct links, if you dont trust them search CM and 4.3 Gaaps and download them ***
COPY Stable rom to internal storage - here is cyanogenmod 10.2.1 stable for ATT i747: https://download.cyanogenmod.org/get/jenkins/57775/cm-10.2.1-d2att.zip
COPY Gaaps zip to internal storage - here is PA gaaps 4.3: http://www.mediafire.com/download/n2a7nta3jrj1ltk/pa_gapps-modular-mini-4.3-20131024-signed.zip
UNMOUNT internal storage
Flash CM
Flash Gaaps
Clear CACHE
Clear DALVIK
Reboot! You should be good to go
Click to expand...
Click to collapse
does it have to be internal storage?
dokibot said:
does it have to be internal storage?
Click to expand...
Click to collapse
I said internal storage cause then you can also clear it and delete any junk files left behind. Once again I am not too familiar with TWRP and if you are able to flash zips straight from external storage, thats also fine.
ALSO look at other person posting a few replies ahead of mine, He has a way to check if you have 4.3 or not. If you didn't have 4.3 then you can flash back to stock easily and start from there instead of flashing a CUSTOM rom.
aybarrap1 said:
There is a difference that could be seen when you are in download mode due to Knox on the 4.3 update. Upload a picture of your download mode and we can advise you from there.
Sent from my awesome phone.
Click to expand...
Click to collapse
[/IMG]
[/IMG]
i'm new to forums in general, not sure if these links will work :T
aybarrap1 said:
There is a difference that could be seen when you are in download mode due to Knox on the 4.3 update. Upload a picture of your download mode and we can advise you from there.
Sent from my awesome phone.
Click to expand...
Click to collapse
i posted the pictures of my download mode o:
dokibot said:
i posted the pictures of my download mode o:
Click to expand...
Click to collapse
I dont know about the download mode thing so you have to wait for the other guy to come online
Have you tried doing what I posted?
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.