Related
Okay, I was able to get into pink screen by erasing the dload folder, removing the battery, and connecting to my PC via the USB cable. I then copied CWM 5.0.2.7 over and then flashed Stallion-51-ICS onto the phone. I now have a very fast, rooted and customized U8800-51, BUT no mobile service. IMEI and APN info is correct but it won't access the mobile service that our other phones access, SIM is the same one that I use in my current phone.
I know you are supposed to back up the IMEI partition and APN before flashing a custom ROM, but since my phone got broke trying to restore a full backup done with CWM I was caught off guard.
Still looking for any suggestions you all might have.
Seriously???
pastorbob62 said:
Okay, I was able to get into pink screen by erasing the dload folder, removing the battery, and connecting to my PC via the USB cable. I then copied CWM 5.0.2.7 over and then flashed Stallion-51-ICS onto the phone. I now have a very fast, rooted and customized U8800-51, BUT no mobile service. IMEI and APN info is correct but it won't access the mobile service that our other phones access, SIM is the same one that I use in my current phone.
I know you are supposed to back up the IMEI partition and APN before flashing a custom ROM, but since my phone got broke trying to restore a full backup done with CWM I was caught off guard.
Still looking for any suggestions you all might have.
Click to expand...
Click to collapse
Not to be negative or anything but I think this is the least responsive forum on this site. I have spent hours searching for possible solutions to various problems I've encountered over the past several months, asked several questions and received little if any help. I was only able to get back from a bricked phone to where I am now by using information found on other websites. Pretty sad if you ask me.
In contrast, whenever I have asked a question on my tablet's forum I've received fast workable solutions/answers to my problems/queries. The threads are informative, well organized and contain answers to any situation I have encountered.
Granted, my current problem with my phone is my own fault for trying to customize it. And I suspect part of the problem is due to the age of this phone thus most of the "experts" have moved on to other ventures. It is also hindered by the lack of information available from Huawei and the service providers.
All of that said, if anybody has any suggestions for how I can repair the ESF partition or whatever is causing this lack of mobile service issue I would be extremely grateful. It isn't the end of the world since i have a new phone (Consumer Cellular) that I am currently using but it would be great to get this one working since it's much faster and more streamlined than my stock Consumer Cellular version.
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Blefish said:
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Click to expand...
Click to collapse
Thank you very much for your reply. It seems that you have found the answer to my problem. But unfortunately, I don't have a copy of the original stock ROM. My phone is the -51 version and any links I have found to the stock ROM are broken. There is a version I found but it is for Venezuela and I don't think it will work. I am leery to try it and totally brick my phone. My backup is apparently corrupted. I backed up my new working phone with Disk Image and attempted to restore it to the broken phone but all that did was cause it to come up to the ATT logo screen for a few seconds and then shut down. It wouldn't do anymore than that. So I restored the Stallion 3.5 image I made and am back to a great fast tablet with no phone service. I also tried backing up my IMEI on the working phone and restoring it to the broken phone but that had no effect.
It is my understanding that the -Pro version of the ROM will work, but I don't have the stock image of that either. I suspect it work might since I was able to use the -Pro version of GB on it. All of my internet searches have only turned up custom ROMs and other desperate people looking for fixes for similar problems or worse. I agree 100% with your assessment of Huawei's lack of meaningful support. It really is a shame, because these phones aren't half bad when they have been customized and OC'ed a little.
I have just about given up on it and resigned myself to using it as an MP3 player for my car system. I have learned my lesson and am leaving the working phone stock. It is rooted and I have cleaned off all of the bloatware, and set it up so most apps run from my SD card, so it really isn't half bad. At least it works.
Again, thank you for your reply and advice.
Blefish said:
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Click to expand...
Click to collapse
@Blefish
hi there, can you please give me the exact steps do to so, because im experience the exact same problem.
I've lost the imei in the upgrade process, and them flashed the 4GB image from a user, and then when i try to update to gingerbread, i can't have 3G signal, only 2G.
in the past, i had made a backup of the imei after flashing that .img file, and i think that after update to gingerbread had restored the imei and the 3g was working nice. But this time i cannot acomplish the same, don't remember very well the exact steps that i've made.
I already tried with the B517 and B518, and can't get it to work...
Can you give me some help please?
Thanks in advance
ggunzio said:
@Blefish
hi there, can you please give me the exact steps do to so, because im experience the exact same problem.
I've lost the imei in the upgrade process, and them flashed the 4GB image from a user, and then when i try to update to gingerbread, i can't have 3G signal, only 2G.
in the past, i had made a backup of the imei after flashing that .img file, and i think that after update to gingerbread had restored the imei and the 3g was working nice. But this time i cannot acomplish the same, don't remember very well the exact steps that i've made.
I already tried with the B517 and B518, and can't get it to work...
Can you give me some help please?
Thanks in advance
Click to expand...
Click to collapse
In my case, I restored the full 4GB from some russian community's provided image (it was named Huawei_U8800_FullFlash.bin), which returned my device to stock 2.2. From there I installed 2.3, and everything still worked. The problem in my case was that I could not restore my own IMEI, it never gave me connection & failed to register to a network. The only solution was to use the "wrong" IMEI that came with the 4GB image.
Huawei has some sort of backup mechanism if they think the "data" is corrupted. I can't tell how it works, but it likes to break things that were working before.
Blefish said:
In my case, I restored the full 4GB from some russian community's provided image (it was named Huawei_U8800_FullFlash.bin), which returned my device to stock 2.2. From there I installed 2.3, and everything still worked. The problem in my case was that I could not restore my own IMEI, it never gave me connection & failed to register to a network. The only solution was to use the "wrong" IMEI that came with the 4GB image.
Huawei has some sort of backup mechanism if they think the "data" is corrupted. I can't tell how it works, but it likes to break things that were working before.
Click to expand...
Click to collapse
i have exactly the same phone than you, because i installed that backup too. After installed it, the IMEI SV is 36, after installing B518 it says it is 18, but before it was 17, and i had 3g signal, but not now.
My question is, wich SV is your phone reporting?
Thank you
I also have a problem like this, but I think it's a bit more severe. My phone got stuck while charging. Couldn't reboot. Was getting stuck on the aurora loading screen(using DZO 5u20). Than reinstalled whole rom. But now I don't any signal and the phone doesn't even see a SIM card. Showing 'baseband unknown' and the IMEI and IMEI SV are also unknown. Not 0's but just unknown. Is this is a similar problem? And can something be done to fix it.
I had some backups on my sd card, untill the sd-card got fried in the phone a couple of months ago.
Here's the story
1. this phone wouldn't boot up after the OTA update, the screen read "firmware upgrade encountered an issue.
please use software repair assistant & try again."
2. used odin 3.09 to reflash pit and the latest nc4 official firmware (I know it can't be rooted, but that's the only choice I have).
3. phone came back alive, worked for t-mobile and verizon sim cards.
Problem:
after a few hours or maybe a day, or maybe a restart, phone won't detect sim card, baseband version shows unkwown, hardware
version is empty, imei, network, MIN, PRL version, ERI version, imeisv, iccid are all "unknown".
What I have done:
phone will be back to normal if I flash the firmware again, I've use odin 3.09 and kies 3 many times.
I also tried flashing different modems, for ex, MI9, MJE, NC2 even NC4. But phone will keep restarting, sometimes the phone is working after
a few restarts. But eventually I will have the same problem again.
I was wondering if someone could point me to the right direction?
nicedog said:
Here's the story
1. this phone wouldn't boot up after the OTA update, the screen read "firmware upgrade encountered an issue.
please use software repair assistant & try again."
2. used odin 3.09 to reflash pit and the latest nc4 official firmware (I know it can't be rooted, but that's the only choice I have).
3. phone came back alive, worked for t-mobile and verizon sim cards.
Problem:
after a few hours or maybe a day, or maybe a restart, phone won't detect sim card, baseband version shows unkwown, hardware
version is empty, imei, network, MIN, PRL version, ERI version, imeisv, iccid are all "unknown".
What I have done:
phone will be back to normal if I flash the firmware again, I've use odin 3.09 and kies 3 many times.
I also tried flashing different modems, for ex, MI9, MJE, NC2 even NC4. But phone will keep restarting, sometimes the phone is working after
a few restarts. But eventually I will have the same problem again.
I was wondering if someone could point me to the right direction?
Click to expand...
Click to collapse
When you flashed the different modems, did you check settings/about the phone to verify that the modem flash " took"? Recommend entering Odin from power off, especially when flashing modems. FWIW, I'm not at all sure this will fix your problem, but it's worth a shot.
cam30era said:
When you flashed the different modems, did you check settings/about the phone to verify that the modem flash " took"? Recommend entering Odin from power off, especially when flashing modems. FWIW, I'm not at all sure this will fix your problem, but it's worth a shot.
Click to expand...
Click to collapse
Yes I did. The baseband version showed MI9 when my phone was still working properly.
nicedog said:
Yes I did. The baseband version showed MI9 when my phone was still working properly.
Click to expand...
Click to collapse
OK. Hopefully someone else will chime in with some suggestions.
one more thing I've done many times so far is, sometimes a full reset will bring it back to normal too.
settings -> backup and reset -> factory data reset.
I don't mind bricking my phone, but maybe someone knows other possible way, say, flashing EFS? I don't even know what that is.
I've been searching for the right solution but I haven't found one yet.
Never ever give up!
I'm the OP and I finally got it working. I simply ran EFS Professional v2.1.73, did a backup and restore of the EFS. That's it!
Did you figure out what efs is?
Sent from my SM-N900V using XDA Premium 4 mobile app
It didn't last long, and using EFS profession for EFS backup/restore never worked again.
I then saw this page the other day,
http://forum.xda-developers.com/showthread.php?t=2610757
So I used odin to flash
pit
official kitkat rom
I also checked these two,
erase nand
erase EFS
the phone booted up fine, I then turned it off and entered recovery mode, did a data and cache wipe, then booted up the phone again, that brought back my imei, my sim card worked again.
Unfortunately I'll lose it again once I flash a custom rom, or perhaps even a reboot.
I'm still searching for a permanent solution. But at least now I can use my sim card with a stock rom
Rom based on which region?
nicedog said:
It didn't last long, and using EFS profession for EFS backup/restore never worked again.
I then saw this page the other day,
http://forum.xda-developers.com/showthread.php?t=2610757
So I used odin to flash
pit
official kitkat rom
I also checked these two,
erase nand
erase EFS
the phone booted up fine, I then turned it off and entered recovery mode, did a data and cache wipe, then booted up the phone again, that brought back my imei, my sim card worked again.
Unfortunately I'll lose it again once I flash a custom rom, or perhaps even a reboot.
I'm still searching for a permanent solution. But at least now I can use my sim card with a stock rom
Click to expand...
Click to collapse
Can you please tell the stock rom based on which CSC ? or country ?
I'm having the same issue. Lost baseband and imei, but never got it recovered. even with stock.
I use this one,
ALL_VZW_N900VVRUCNC4_N900VVZWCNC4_1487472_REV03_user_low_ship_MULTI_CERT.tar.md5
http://www.trueandroid.com/2014/05/n900vvrucnc4-android-442-kitkat.html
Same boat brother, this is what I've posted. So far I'm a week in this situation, battery pull brings it back, any mod like Xposed with module where you have to reboot looses the baseband, IMEI etc. I have backup of the EFS and restored it multiple time with no joy.
Need some advice guys for Verizon my Note 3, I'm currently stock NC4 ready to. flash this bad boy ROM, after root access with TowelRoot, installation of BusyBox and Supersu no SafeTrap yet. Once I reboot in this state, I have the Baseband unknown under Settings-About Phone status all unknown info on IME etc etc. Off course I loose 4G signal all together. I may reboot again and it comes back. I know about EFS partition corruption and have multiple backup of My note 3 EFs partition. Even with restore it would still happen. I have exhausted all my knowledge learned throughout the years from you guys. But, I'm asking some help again. I am very familiar with all the terms about flashing/rooting so please feel free to throw some genius on how I can fix this thing.
Sent from my SM-N900V using Tapatalk
Hey guys. I know for sure there is another thread about a similar problem but the biggest problem I'm having is figuring out what to do next, or better yet, what did I even mess up?
I made a thread a couple days ago here asking about the LTE option on my phone and how there was none. It's an Intl' phone and therefore I guess doesn't work on Canadian LTE networks.
Before we start, I'm using TWRP 2.7.0.0 . My phone is the UAE version of the D802, which is the D80220C. My current custom rom is Liquidsmooth MS3.2 .
So I found a list of modems and flashed the one for Bell. It was for the D803, but the thread I was looking at said it was cross-compatible so I assumed that meant it's okay for me to flash it on my phone.
Even so, I backed up my EFS partitions just to be 100% sure. I even used the .zip file that automatically backs up the current modem files. So I thought there was definitely a way out if it didn't work.
I will give you the full story of what was done and maybe I can get some guidance on maybe something I did wrong.
1) I flashed the D803 Bell modem.
2) Reboot to system, LS3.2 hangs on start up. Tried a hard restart to see if it wasn't a fluke. Nothing. Still hanging.
3) Figured the EFS files were toast, so I ran the restore .zip for my EFS. Reboot, and still hanging.
4) Said WTF? and restored my first stable rooted stock rom. It booted into the rom fine, but when it got to the lock screen I saw the "Service Disabled" and the phone quickly crashed.
5) Didn't even attempt to restart on that rom. So I tried a couple terminal commands to copy the modems1.img and modemst2.img files to corresponding partitions. Copied both just fine, but no change. Still screwing up.
So, this is where I am so far. I am in the process of downloading the D80220C UAE .kdz file so I can try to flash that one first. If that doesn't work, I'm really at a loss.
When I read into this some more, all I see is people who have totally wiped their EFS files and having to spend a whole bunch of time using a bunch of different programs to get in an recover the IMEI number.
What do you guys think?
Some good news right off the bat. I found a KK baseband for D802 and flashed it. So now I was able to restore my LS3.2 rom and boot into it fine. I see my IMEI and MAC address and can get WiFi at last!
Mods, you can delete this thread if you wish.
Tuesday
306sh activated with MVNO, SA300 firmware, rooted, with TWRP recovery,
working fine for past 2 months.
For unknown reasons, it decided last friday (at home, none to low signal) to do a system update
(from SA300 to S7232). Phone - on the desk- just "dinged" and msg came up "updating
system software". I attempted to cancel, but it didn't respond. Less than a minute later, "Update Successful" msg. Didn't reboot, anything, settings showed S7232 firmware. (SA300 before,
i had done my weekly backup earlier that morning).
Since then, phone constantly reboots at the "Aquos" screen; after an average 8 hours of rebooting, it will boot to setup, the talking setup screen. Works perfect for about an hour then rebooting starts again. Let battery die last nite, tried again this am - same thing rebooting.
TWRP backups don't fix problem- weekly backup, i have 6 i've tried, factory reset doesn't fix, if i try to Software Update, it checks, tells me, "up to date".
I turn on wi-fi to use the phone from home, , guessing it did a ? hit & miss ? ota update since the
wi-fi was off when it attempted the update. Home is a very minimal signal area.
Any way to force it to take the S7232 update again?
(I could update over wi-fi if i had wanted, only i didn't want the update anyhow).
thanks, rik
I can give you a link for a backup with latest firmware, you will have to wipe data tho
https://mega.nz/#!fkommKgJ!fkiaT_p8ZFOBzyJpUdNAqOZlTWpt-5hNuQ-2vvA5tSQ
This is a full backup from newest firmware but you need to wipe data before boot
sent from rooted 306sh
Stick firmware updates are not compatible with custom recoveries
sent from rooted 306sh
Just home, thanks
Hi,
Thanks for the help, just home from work (rough), so i will plug the
Aquos in tonite and hopefully be able to try the file tomorrow,
(that 8 hour boot thing), just downloaded your file, i'm ready.
This is my take-to-work personal phone, sprint zone, and i missed it today.
Your help is really appreciated.
rik
Final note
thought i'd just post to let you know the phone obviously had big problems
-- it failed to start today -- just buzz on buzz off -- even after 4 hours charging,
all i could get was the battery dead screen, wouldn't come on at all.
Guess the real problem was with hardware, i laid it away in the junk phone box
in the attic, end of Aquos Crystal.
rik
I downloaded this backup and yesterday to restore the firmware, works great, huge thank you , you saved me. :хорошо:
can you help me?
badbadri said:
I downloaded this backup and yesterday to restore the firmware, works great, huge thank you , you saved me. :хорошо:
Click to expand...
Click to collapse
can you help me dude? :crying:
im already download this firmware and confuse how to restore it
im looking for how to root my phone but always confuse
and finally i installed supersu on playstore and reboot
im waiting for 5 minutes and not booting, and im plug my phone to pc and the computer request for formating all my storage
and my phone can enter the recovery mode and i go to wipe data & factory reset, and still not work
can you send to my email?
my email is [email protected]
thx ..
Question: My 306SH would not update (still at S8216). Could use your back up to update my firmaware?
After 306SH ph was acting weird, did a hard reset & saw system Software updtd to S7232, & unk file in Misc (.eCtcQjbu1dgnvtFnvnr6yepTp1M=) I then installed Malwarebytes & scan detects this S7232 software update as malicious malware Android/PUP.RiskyTool.Agent.ay (dm.redbend) "/system/priv-app/fotaClient.apk". When going to System to do an manual update, Malwarebytes popups w/same msg every scan "Software App", even aft reboot 2days ago 7/12/2017. And phone wont let me create new google acct. An error that "google account mgr not working" popup & I see that same unk file reappears. Ph not rooted -XDA says "there's no root for 306SH that works">see XDA blog 'Root for Aquos Crystal 306SH ONLY'.
Go to the Sharp USA website for the 306SH firmware, and see what firmware you are on.
Download the firmware from the versions higher than yours, and if there is a repeat, notably "kernel.img", download the most latest version of it.
Then, plug your device into your computer, make sure you have the proper drivers installed for the Sharp Aquos Crystal installed on your computer. Boot your device into bootloader. Go to a terminal, cd to the directory where you downloaded your .img's from the website, and do
fastboot flash kernel kernel.img
Ex.
fastboot flash foo foo.img
And you can flash all the latest updates. When done, exit the terminal, make sure the device is unmounted, unplug from computer, and reboot your Crystal.
Hooray, it should be updated!
turkbot said:
I can give you a link for a backup with latest firmware, you will have to wipe data tho
(Mega-nz link expired)
This is a full backup from newest firmware but you need to wipe data before boot
sent from rooted 306sh
Click to expand...
Click to collapse
Turkbot, I hate to beg on my first XDA post, but is there any chance that you still have that ROM and is there any chhance that it's not TextNow loaded? I've got TWRP, Busybox, SuperSU, Xposed, and I've tried every which way to edit the prop, tweak it with modules, unlock etc (it even works with my Sprint MSL, but crashes when I try to manually set my MDN and MSID) It just says no SIM/no service and refused to give me any signal except for GPS and WIFI without one. Countless 'techs' over the phone and 3 different Sprint repair stores claim they don't have the stock firmware and Sharp actually claims that the reason they can't help me with the firmware is their contract with Sprint forbids it.. If you still have the file or a TWRP / Titanium etc backup you would be my savior.
So, I'm having a particularly strange issue here. I recently got this Sprint Note 4 and activated it. However, there appears to be a missing option under settings. Tethering and Hotspot is straight up gone. To clarify, I have pictures attached showing the item listing, and one without it.
Clarifications of troubleshooting I've tried so far:
I have attempted a factory reset of the device
I have attempted to do a reset with ##72786#
I have tried updating Profile, PRL,
I am using a DeOdexed PH4 6.0.1 ROM. I have tried reflashing per instruction (triple wiping Cache, Dalvik, Internal, System, etc)
I have tried flashing a STOCK OTA PH4 ROM to see if it would show up there. It does not.
I called Sprint technical support to reprovision my phone. They pushed out a a reprovisioning that I accepted. No change.
At one point, Wanam/Xposed was attempted to be installed. I checked for system/csc/features.xml. It was not there
http://forum.xda-developers.com/note-4-sprint/development/rom-stock-ph4-bloated-deodexed-t3473610/ is the custom ROM i'm using. However, it doesn't seem like a ROM specific issue.
If I use Activity Launcher or itools, i can access the actual wifi hotspot MENU (the toggle off and on, LAN settings, etc). I can enable it and the system will broadcast the SSID. However, if I try connecting to it, no devices are able to successfully connect.
here is the Activity Launcher referenced, for other readers:
http://forum.xda-developers.com/showpost.php?p=66713935&postcount=7
but anyways, regarding devices not being able to connect, sometimes the data connectivity (through hotspot only, not for the entire phone) will go dead if you don't start using it immediately after first unlocking and activating tether.
in my experiences, if you keep data alive by immediately connecting a device after your first time turning tether on (after unlock) by downloading a large file or somewhat frequently reloading web pages (on the connected device!) -- anything that will keep data sending and receiving -- it will stick, and the data service to connected device issues will stop.
it's not foolproof, it's not a silver bullet, but this is the method to the madness I have learned and worked for me many times when changing roms and even getting new phones.
it's been a couple months since I had to fiddle with it last, so I can't remember if it was necessary to re-unlock after a failed attempt at keeping data alive. you might only have to toggle data off then back on for another attempt.
when I had the problem of connected devices losing internet access, it would only happen after having worked for a few seconds to a few minutes. it'd work then abruptly stop, and this is my "fix"
My issue seems more in line with the devuces failing to validate to begin with. Not losing connection.
I had something like this before, I vaguely recall it having to do with using Odin vs. OTA stock. So did you try wiping your phone completely then Odin the stock PH4 tar, or did you OTA to PH4?
beezar said:
I had something like this before, I vaguely recall it having to do with using Odin vs. OTA stock. So did you try wiping your phone completely then Odin the stock PH4 tar, or did you OTA to PH4?
Click to expand...
Click to collapse
The very very very first time, I OTA'd to PH4. The next two tries were wiping completely and using the PH4 tar file. So both methods have been attempted.
I was referring to loss of internet connection, not signal related. I thought that was clear, sorry
Sterist said:
I was referring to loss of internet connection, not signal related. I thought that was clear, sorry
Click to expand...
Click to collapse
I thought you meant loss of internet connection in the sense of anti-tether provisioning from Sprint. My phone's LTE never goes down (and I am able to still browse the internet from the mobile device while tethering).
The connected devices never successfully "connect". They aren't listed as connected devices under the mobile hotspot. My other Android phone (without mobile data) is forever connecting. My macbook claims it has an assigned IP but is "unable to access the internet". So I'm not sure what the hell is going on with that.
At this point, I have restored my Note 3 as my active device until I get this resolved. I'm willing to re-write everything down to the barest metal I can.
Somebody in another topic mentioned something about PIT. I don't know anything about that sort of thing. My knowledge extends about as far as installing recovery and flashing ROMs.
I'm confident I could follow procedure, but could use a guiding hand on where to go from here.
sounds like the tether unlock method you used was not done correctly, whether by whoever made it or yourself
method 2 in Galaxy Tools should work just fine. there are several threads in the Sprint note 4 seconds that contain the apk or ppl that will pm it to you. the author discontinued the public/free version of the app and now chargers $35+ per person for a 1 time use lol once you get a copy of the free one, make copies and store on multiple devices forever.
it's primarily for Sprint Sammy devices, so you prob won't see much if anything about it here in the collective note 4 forum.
may work on some boost or even tmo, but yeah.
edit:
you'll want either 3.1.5, easy install n msl read broken on MM and less features
or 3.1.8, troublesome install with msl read working but unreliably, more features.
Sterist said:
sounds like the tether unlock method you used was not done correctly, whether by whoever made it or yourself
method 2 in Galaxy Tools should work just fine. there are several threads in the Sprint note 4 seconds that contain the apk or ppl that will pm it to you. the author discontinued the public/free version of the app and now chargers $35+ per person for a 1 time use lol once you get a copy of the free one, make copies and store on multiple devices forever.
it's primarily for Sprint Sammy devices, so you prob won't see much if anything about it here in the collective note 4 forum.
may work on some boost or even tmo, but yeah.
edit:
you'll want either 3.1.5, easy install n msl read broken on MM and less features
or 3.1.8, troublesome install with msl read working but unreliably, more features.
Click to expand...
Click to collapse
Came back around to this, as I am running a multi-rom and am still encountering this issue. I never attempted any hotspot unlockers. The hotspot was missing from the get-go.
Gamemaster1379 said:
Came back around to this, as I am running a multi-rom and am still encountering this issue. I never attempted any hotspot unlockers. The hotspot was missing from the get-go.
Click to expand...
Click to collapse
Just a thought and question: when you Odin stock tar to recover from this condition, are you using the rooted extended power menu to boot to download mode? Or, do you prevent the auto reboot of stock tar flash with Odin options?
A noted developer, @idone from Galaxy Tool app, once shared with me that rooted shortcut or preventing auto reboot can prevent the normal flash of Odin booting to recovery momentarily to set csc options. csc options flashed may not restore on any boots if you skip that initial auto boot.
The suggested method is to power down and pull battery for 30 seconds our more before reinserting battery and manually booting to downloaded mode. And do not uncheck auto reboot or pull battery but use Odin defaults and let phone auto boot. Doing this allows the phone to boot into recovery to do its thing briefly before booting system. I usually just let it perform the setup wizard and didn't activation just in case.
I rarely do the the data profile update or PRL because if letting the phone setup this way and phone prompts to reboot later, I believe this all done. But since this may allow ItsOn to bootstrap initialize, after flashing TWRP and backing up, I wipe internal memory and factory reset before flashing a custom ROM. Data format is optional; I don't always do that.
But if you do all that and don't see hotspot in Settings of stock, that's a problem. Maybe from dead stock, try KIES or Smart Switch to restore latest stock and check again?
Sent from my SM-N920P using Tapatalk