Wifi Tether (any fixes)? - Hero CDMA Themes and Apps

I'm obviously new to this so bare with me.
I just rooted my Sprint HTC Hero and the first thing I would like to do is use it to tether. I've tried both versions of Android_wifi_tether (1.52, 1.6) but have had no luck in getting it functional. Basically; It broadcasts the signal (I'm at work so the only way to test it was with a Macbook) just fine. The Macbook even connects to it and my phone shows "3KB down 7.8KB up" meaning it detected something has connected. Once that happens nothing else works. The Macbook indicates it has no internet connection.
I was wondering if anyone has been able to get this to work? I'm a little hesitant on installing a custom ROM because it seems like a lot of work and I'm not too knowledgeable when it comes to Linux.
Also, can my phone still be updated or is that still unkown? If I install a root app and the update kills root does that mean I lose it entirely or just for anything I try to install post update?
As a side note: Someone should make a post with step by step guides to follow. What I mean by this is put the guides in chronological order.
1) Root your phone (guide link)
2) Run Nandroid backup (guide link)
3) etc.
Anyway, really appreciate the work! This is exciting.

fatkitty420 said:
I'm obviously new to this so bare with me.
I just rooted my Sprint HTC Hero and the first thing I would like to do is use it to tether. I've tried both versions of Android_wifi_tether (1.52, 1.6) but have had no luck in getting it functional. Basically; It broadcasts the signal (I'm at work so the only way to test it was with a Macbook) just fine. The Macbook even connects to it and my phone shows "3KB down 7.8KB up" meaning it detected something has connected. Once that happens nothing else works. The Macbook indicates it has no internet connection.
I was wondering if anyone has been able to get this to work? I'm a little hesitant on installing a custom ROM because it seems like a lot of work and I'm not too knowledgeable when it comes to Linux.
Also, can my phone still be updated or is that still unkown? If I install a root app and the update kills root does that mean I lose it entirely or just for anything I try to install post update?
As a side note: Someone should make a post with step by step guides to follow. What I mean by this is put the guides in chronological order.
1) Root your phone (guide link)
2) Run Nandroid backup (guide link)
3) etc.
Anyway, really appreciate the work! This is exciting.
Click to expand...
Click to collapse
Currently the only phones that have wifi tethering working are the ones who installed MoDaCo's ROM...something in there is configured differently to allow it to work.

thecodemonk said:
Currently the only phones that have wifi tethering working are the ones who installed MoDaCo's ROM...something in there is configured differently to allow it to work.
Click to expand...
Click to collapse
How functional is the ROM?
The one thing I'm scared of is that if I install a ROM I'll be dependent on this community to make future things work?
I mean, can you still access the Market? What about future updates? Will applications I purchased already still be available?
Like I said, I'm still fairly noobish.

fatkitty420 said:
How functional is the ROM?
The one thing I'm scared of is that if I install a ROM I'll be dependent on this community to make future things work?
I mean, can you still access the Market? What about future updates? Will applications I purchased already still be available?
Like I said, I'm still fairly noobish.
Click to expand...
Click to collapse
No sweat! If you look at my join date and postcount, you can see I'm not exactly the veteran around here either.
The MoDaCo ROM doesn't modify very much yet...just adds functionality (it's not the heavily optimized kernel that the GSM users have for example). I'm finding it fairly stable...there's a few quirks but those have fixes pretty easily found so far.
I can still purchase from the market...the stuff you purchased already is tied to your google account, not your phone. I bought Docs2Go before I rooted and flashed and I was able to redownload and install without any hassle or added cost.
On a custom ROM, future updates do depend on the person who is building the ROM. However, MoDaCo has proven pretty reliable thus far in keeping up with releases so it's a bit of a trust thing, do you trust MoDaCo to continue that trend or would you rather place your trust in the manufacturer? (It's a preference thing and willingness to risk either way).
The upside is that once you root to a recovery image (Not even changing your OS), you can take a Nandroid backup of your phone, which is an image you can drop back on there to get back to stock/manufacturer spec (as if you never left).
Any changes to your phone since the backup will not show up but that's kindof the risk.

thecodemonk said:
k on there to get back to stock/manufacturer spec (as if you never left).
Any changes to your phone since the backup will not show up but that's kindof the risk.
Click to expand...
Click to collapse
This is somewhat confusing for me. My phone is currently rooted. If I restore it factory default will it still be rooted?
If not,
Then should I restore to factory default first, take a Nandroid back up (this looks difficult), then root my phone?
The recovery image is basically replacing the "Factory reset" image, right?

fatkitty420 said:
This is somewhat confusing for me. My phone is currently rooted. If I restore it factory default will it still be rooted?
If not,
Then should I restore to factory default first, take a Nandroid back up (this looks difficult), then root my phone?
The recovery image is basically replacing the "Factory reset" image, right?
Click to expand...
Click to collapse
Ah ok...the recovery image is like a second mini OS you are booting into that has menu options and specializes in updating your phone with a custom ROM, running Nandroid for backups, and enabling you to mount your SDCard to your computer, so installing that doesn't actually do anything to your phone's running OS.
Nandoid takes a backup of the phone's OS (the one you use every day) as it is right now. It places the backup onto your sdcard under a folder called "nandroid" (where you can take a copy of it and put it on your computer to be safe). So whenever you Nandroid your phone, it's taking a snapshot of how your phone is currently configured (the whole thing) and if you restore from that three weeks from now after doing a bunch of things...it restores to the phone as if you hadn't done anything to it in those three weeks.
So to make an example: if you take a backup of your phone right now (rooted, right?) and then you do a bunch of things to it...then restore from that backup, it's as if you didn't do any of those things you did since the backup (but it will still be rooted since you backed up a rooted phone).
Second Example: If you nandroid your phone when it's running MoDaCo's ROM...when you restore it, it will be running MoDaCo's rom and configured however it was configured then.
I wouldn't worry about trying to get to factory default first...HTC has an official utility that can get you back to the state your phone was in when you first openned it out of the box. (http://forum.xda-developers.com/showthread.php?t=559622)

thecodemonk said:
Ah ok...the recovery image is like a second mini OS you are booting into that has menu options and specializes in updating your phone with a custom ROM, running Nandroid for backups, and enabling you to mount your SDCard to your computer, so installing that doesn't actually do anything to your phone's running OS.
Nandoid takes a backup of the phone's OS (the one you use every day) as it is right now. It places the backup onto your sdcard under a folder called "nandroid" (where you can take a copy of it and put it on your computer to be safe). So whenever you Nandroid your phone, it's taking a snapshot of how your phone is currently configured (the whole thing) and if you restore from that three weeks from now after doing a bunch of things...it restores to the phone as if you hadn't done anything to it in those three weeks.
So to make an example: if you take a backup of your phone right now (rooted, right?) and then you do a bunch of things to it...then restore from that backup, it's as if you didn't do any of those things you did since the backup (but it will still be rooted since you backed up a rooted phone).
Second Example: If you nandroid your phone when it's running MoDaCo's ROM...when you restore it, it will be running MoDaCo's rom and configured however it was configured then.
I wouldn't worry about trying to get to factory default first...HTC has an official utility that can get you back to the state your phone was in when you first openned it out of the box. (http://forum.xda-developers.com/showthread.php?t=559622)
Click to expand...
Click to collapse
Great, this really clarified things.
I love technology but, like most of these things, it's very overwhelming at first.

Related

[Q] Backing up my backups

So right now I'm using CWM to do my nandroid backups. I make one after I make any major updates or changes - call me a worry wort. I also use Titanium Backup.
With doing this, obviously it takes up a bit of room so I offload them to my computer. The issue here is if I do something detrimental and need to restore, I don't know of a way to get the backup files back onto the internal memory since you can't access them via CWM, if that makes sense.
I guess I can simply keep just the latest backup saved on the phone itself but I'm wondering if there's another method that I'm not aware of. Is there a way to get files copied to the internal memory if you can't fully boot into the OS?
Oh and one other question: Does a nandroid backup include every single item? Basically is it a 100% clone of the device or are some thing left out? Basically if I tried a completely different rom and then decided to go back to an entirely different rom, would I simply be able to restore it and be up and running? The last restore I did seems to indicate it does but that was going from different versions of the same rom.
nandroid is a clone of ur system.
diablo009 said:
nandroid is a clone of ur system.
Click to expand...
Click to collapse
Ok that's what I figured; read something a bit ago which seemed to say something else.
So if I want to test a few completely different rom setups and make a nandroid backup of each one, I could essentially swap between them whenever I want by simply restoring them and I'll get back to the exact state as I was at the time they were made? Menus and all?
So apparently a kernel change will not get reverted via nandroid. Anything else? Just tried Entropy's daily driver and apparently it's a no go for me. Restored via nandroid and still freezes during 'X' boot animation.
I was running Infusion 1.1 and made sure to reset the VC O/C back to stock and reboot before updating...

[Q] Comprehensive Tutorial on switching to GB / CM7

I am overjoyed to see that there is finally an official gingerbread update that I can flash, and then a CM7 for this kernel, that doesn't have any bugs that are too annoying. However, it's been a while since I became an expert on flashing my old LG Eve. Is there a thread somewhere that outlines exactly how to do this for this exact phone and mod?
I've got a D2G, with Fission ROM. the phone is unlocked and rooted. I have an original ROM saved to flash to the phone if need be. Everything I would ever need is backed up using Titanium Backup. I've downloaded the GB update and CM7. I think I'm ready to go.
Questions:
- Is there a thread that answers all this already?
- Am I going to run into any problems being unlocked or rooted?
- Does the phone revert back to being locked once the new GB is installed? That would not be good considering I'm in Canada, not on Verizon. I bought my phone unlocked so I don't know how to just unlock it again.
- I remember using nandroid before to make a complete backup of the contents of my phone so that if I screwed up I could just go back to it seamlessly. Same thing this time around?
- I'm not completely illiterate here though, so I'm going to give it a go and you can just correct me where I am wrong. First, put the CM7 and GB files on the SD card. then do a nandroid backup of the phone. Clear data, clear cache. Then use clockworkmod to flash the GB update. then use clockworkmod again to flash CM7. then use clockworkmod again to flash gapps. Start up phone, do a complete restore with Titanium and I'll have all my apps and settings, call history and texts back. I'm probably wrong somewhere in all this, but where?
If there's not already a comprehensive thread on this, let this be it!
You will need to SBF to stock to be able to install the update.
Refer to the following for some instructions:
http://droid.koumakan.jp/wiki/SBF
http://droid.koumakan.jp/wiki/4.5.607_Firmware
http://droid.koumakan.jp/wiki/CyanogenMod
Ok, I read these all over about 5 times. So in a nutshell, these are the steps:
- use rsdlite to put your phone back to the stock firmware 2.4.330
- unroot and remove cwm
- use android recovery to install gingerbread 4.5.607
- root again and install cwm again
- use cwm to install cyanogen and gapps.
Correct?
Also, I am running fission. According to my system info it is firmware 2.4.3. I would rather skip step 1 and just install gingerbread. I am guessing I can't, but please confirm.
Sent from my DROID2 GLOBAL using XDA App
You don't need to unroot and remove CWM after flashing the SBF.
Otherwise everything's correct.
You cannot install the official Gingerbread firmware update onto a phone that is not running stock unrooted 2.4.330 without CWM and with all bundled software intact.
Note: if you need to backup your applications and configuration data, you can do so with CWM. Make a backup under Fission, then perform all those steps above, and once you're running CM7 on 4.5.607, use CWM's advanced restore feature to only restore /data.
So here I am in Gingerbread on my D2G (already further than I thought I'd get!) and you would think it would be smooth sailing from here... except I can't root it now! Is there a different technique for rooting in Gingerbread? I used Z4 before, and it worked in seconds.
OK, I figured out how to root using another thread. and when i am in adb shell I get "#" and not "$" after entering a string of commands.
But, apps think that I'm not rooted. All I need is to install CWM, but it runs into errors, presumably because I am not rooted.
The phone is in some sort of weird half-rooted state.
really weird experience with rooting. I realized that I hadn't done the additional steps where you push superuser to the phone and a couple other commands. So I did that, and then root check said i was rooted. I rebooted, and adb shell was acting like I wasn't rooted! yet root check still said I was. I was able to flash CWM and reboot, and then install CM7. Everything seems great!
except, right from the start I was getting repeated FCs for com.android.phone.
I remember that there's an issue with needing to reboot after switching to GSM... so I'm trying that now. Let's hope that stops the FCs.
So what ended up happening was, I rebooted and stopped getting the FCs for the phone after switching to GSM. So that is good. However, aside from the two minor bugs that I was prepared to live with, this is happening now:
- I have phone and SMS service, just no data. Wireless works fine, and so do GPS and Bluetooth to my knowledge.
- When attempting to select a network to register on, I get the dreaded “Your SIM card does not allow connection to this network” message. I have tried doing this with data/roaming enabled/disabled and with “only 2G” selected. I have also tried a couple of tips I found online such as removing the battery for 15 minutes and also getting a new SIM card.
- At first I was able to enter new APNs, but they wouldn’t save. I hit menu, then save, but it goes back to the APN screen and none are listed. Now, what happens is, if I hit menu, then “add new apn”, nothing happens.
I went into the telephony.db file to manually enter my APNs, and it seems that they are already there, which is good. I re-entered them all manually using sqlite anyway. This did not work. I also noticed that Verizon was listed with a “1” in current, which probably means that Verizon is my current APN. So I removed that 1 and placed it on all my rogers APN entries. Still, nothing is saved at the APN screen in settings, and I can’t enter them through that screen, either. And no data.
Suppose it turns out that this is just a bug with CM7 right now and it’s unusable for me. Obviously I don’t want to go all the way back to Fission on Froyo when I can use gingerbread. How far back into this process do I have to go? Can I just flash GB and it will overwrite CM7?
Did you make a CWM backup of your freshly installed Gingerbread? If so, just restore.
If not, I don't see how you're going to “just flash Gingerbread” without SBF'ing to 2.4.x.
Well, I have done a lot of testing and troubleshooting. I went back to the start of this whole process, and I backed up my APNs and fully tested the phone at every turn, and my conclusion is that CM7 is not friendly to APNs. There was no problem with stock Froyo or stock Gingerbread. With the working APNs that I had, I was able to use data on both. Once CM7 was installed, it was a no go.
I used a couple of apps to backup my APNs both in Froyo and Gingerbread prior to installing CM7, and when CM7 inevitably didn't allow me to use data, I tried to restore my APNs using these programs as well. They say that they worked, and it's true that if you go into root explorer the APNs are there as you entered them or restored them using a program. But it seems these APNs are not going to work unless you actually see them at the APN page in settings. And nothing I have tried up to this point has been able to make any APN show up at that screen.
I think the “Your SIM card does not allow connection to this network” message at the network operators screen, as well as my inability to enter APNs, are 100% related. I also bet there is a simple solution to it!
If anyone has any ideas about how to make an APN stick, and how to force a phone to start using it, please let me know. I'll also post this at the CM7 forum.

[Q] Post-flash data Loss

Hi, i've been a noob-lurker at this forum since joining the android community in december, but this is my first post so i'd like to start off by saying hello to everyone. As i mentioned before, my knowledge of this OS is fairly limited, so i may occasionally need for things to be a little dumbed down for me to understand.
That all being said, i recently decided to try flashing the Eagle Blood ROM (a T-Mobile based ROM) on my ATT skyrocket using CWM. The process was completed without my phone being connected to my computer, as i decided to flash a ROM available through CWM itself.
Before i flashed the ROM, the phone was rooted, had superuser, Titanium backup, etc. I believe CWM had a fairly recent backup of all my stuff as well. Once the phone booted into the new ROM, i noticed that i had none of my apps present, none of my data (contacts, messages, pictures, etc), was no longer rooted, and could no longer connect to the data network (my internet will not run without wifi). I do remember that at some point in the reboot process the log showed that it had not recognized my external SD card. I'm not sure but it might be that all my apps were on the card and none of the info loaded because of that. Additionally, because i am running on a mac and have not yet been able to reliably connect my phone to the computer, i do not have any of the more valuable data stored there either.
Essentially i'd like to know if i can recover any or all of the data (either through finding some backup buried in the system) or through pulling the contacts, etc. from the google cloud i assume they are in, and then lastly if someone could point to what exactly i did wrong in the process -- it would be nice to continue flashing ROMs and what not. If i left out any important pieces of information, please let me know.
Thank you so much!
Restore your backup. And ya, you either wiped data before flash or the rom did it for you. You can backup apps+data in tibu but you have to restore them after flash. That will restore app data. Not att data. Chances are your T-Mobile rom had T-Mobile apn's...ect. try the T-Mobile conversion zip. Its in the skyrocket dev section.
Sent from my SAMSUNG-SGH-I727 using xda premium
I'm not sure where i would find those backups -- they were all on the apps themselves and (unless titanium or CWM automatically pushes the backups to another server). Both of those are not on the phone any more (or at least not in the application folder).
I will look into the T mobile conversion, that should be a good first step.
And, a quick update, all my pictures are still on the phone. Contacts, etc. are still missing.
Did youake a cwm backup before flashing?
Sent from my SAMSUNG-SGH-I727 using xda premium
Yes and no. I downloaded CWM a while back and decided to make a backup right off the bat. Functionally speaking it would have all my stuff on it, but i also did not understand flashing recovery mode at that point, so i'm not sure it would have worked.
But no, not right before i flashed the ROM
Boot into recovery, go to backup and restore, go to restore. See if there is a file available. I'm kinda confused. Did you or didn't you make a cwm backup?
Sent from my SAMSUNG-SGH-I727 using xda premium
am.rawr said:
Hi, i've been a noob-lurker at this forum since joining the android community in december, but this is my first post so i'd like to start off by saying hello to everyone. As i mentioned before, my knowledge of this OS is fairly limited, so i may occasionally need for things to be a little dumbed down for me to understand.
That all being said, i recently decided to try flashing the Eagle Blood ROM (a T-Mobile based ROM) on my ATT skyrocket using CWM. The process was completed without my phone being connected to my computer, as i decided to flash a ROM available through CWM itself.
Before i flashed the ROM, the phone was rooted, had superuser, Titanium backup, etc. I believe CWM had a fairly recent backup of all my stuff as well. Once the phone booted into the new ROM, i noticed that i had none of my apps present, none of my data (contacts, messages, pictures, etc), was no longer rooted, and could no longer connect to the data network (my internet will not run without wifi). I do remember that at some point in the reboot process the log showed that it had not recognized my external SD card. I'm not sure but it might be that all my apps were on the card and none of the info loaded because of that. Additionally, because i am running on a mac and have not yet been able to reliably connect my phone to the computer, i do not have any of the more valuable data stored there either.
Essentially i'd like to know if i can recover any or all of the data (either through finding some backup buried in the system) or through pulling the contacts, etc. from the google cloud i assume they are in, and then lastly if someone could point to what exactly i did wrong in the process -- it would be nice to continue flashing ROMs and what not. If i left out any important pieces of information, please let me know.
Thank you so much!
Click to expand...
Click to collapse
When flashing any TMobile t989 ROM, you must also flash the conversion package as well. It contains the kernel and other files that are required. You can find that conversion package from the t989 dev thread. I strongly recommend performing a full wipe, flash the rom again, then flash conversion package BEFORE you reboot.
You may also need to manually input the correct APN settings.
Sent from my SAMSUNG-SGH-I727 using XDA Premium App
I just tried booting into recovery: the phone powers down and then just buzzes in 3 second intervals until i let go.
The only thing about performing a full wipe and working from there is that it would need a computer, which i am still currently unable to connect the phone with...
am.rawr said:
I just tried booting into recovery: the phone powers down and then just buzzes in 3 second intervals until i let go.
The only thing about performing a full wipe and working from there is that it would need a computer, which i am still currently unable to connect the phone with...
Click to expand...
Click to collapse
With the Skyrocket, press and hold volume +&- and power, once you see the Samsung splash, then release the power button (continue holding volume) m, wait a few seconds and it should load recovery. You don't need a computer to perform a full wipe. Ypu can download Darkside Super Wipe Script. That will completly wipe your phone (won't wipe sd or emmc memory).
Sent from my SAMSUNG-SGH-I727 using XDA Premium App
Okay, i was able to boot into recovery (sorry about the confusion, for a second i forgot that it was possible to get into recovery outside of the app).
I found the backup i had made a while back (accidentally made another, current backup while doing this) and have tried loading it twice, but it throws up "Error while formatting /system!"
sorry, a closer yields the full text as...
"E:format_volume: no MTD partition "/dev/block/mmcblk0p24"
Error while formatting /systems!"
Just tried to boot back into the system and now i have a message saying
"warning
A custom OS can cause critical problems in phone and installed applications"
i can either boot into the custom anyways or "restart phone".
Restart? Or would that mean i would have to get it reactivated?

Bootloader won't unlock (4.1.2, getting ready for custom ROM)

Afternoon, y'all. Let me cut to the chase:
My objective: To install the custom ROM located at this link (http://forum.xda-developers.com/showthread.php?t=2591895). I don't want to lose my root functionality/benefits by taking the OTA 4.3 update (Titanium, Greenify, etc), but I want to be able to use apps like DashClock which don't work with 4.1.2.
My phone specs:
Model SCH-i535
Android Version 4.1.2
Baseband Version i535VRBMF1
Kernel Version 3.0.31-1152558 ([email protected] #1)
Build Number JZO54K.i535VRBMF1
Hardware version 1535.10
Phone IS ROOTED, and I used the Casual root tool located here: http://forum.xda-developers.com/showthread.php?t=2332825
[*]Apps I am using during this process (specific to root, backup, etc): Titanium Backup Pro (full backup made, including update.zip), ROM Manager, Root Checker, SuperSU
[*]Although I had a ton of frozen bloatware/system apps (all safe, I checked thoroughly before I did this a few months ago), I have unfrozen everything.
Previous experience: Before this S3, I had an HTC Thunderbolt which I successfully rooted and installed a custom ROM onto. So I have *some* experience, but I am no zen master.
Problems I've run into this time around:
Phone is rooted, but I am pretty sure the bootloader is NOT unlocked. Rootchecker confirms that the phone is rooted, and apps that require root access work just fine.
Related to the above point, when I run Casual (as I did just a few minutes ago), this is the log that appears in the window:
-Waiting for device...
Waiting for ADB device connection. When your OS recognizes the device, we will continue. Don't touch anything.
-Device found.
-Pushing exploit...
4298 KB/s (1283460 bytes in 0.291s)
-Pushing root tools...
2990 KB/s (96260 bytes in 0.031s)
4692 KB/s (1867568 bytes in 0.388s)
5424 KB/s (1872015 bytes in 0.336s)
-Rooting phone...
-This may take a few minutes.
Failure.
-installing superuser to system partition
-once root is confirmed you can flash the Insecure aboot
done
-Script Complete
This "FAILURE" is what catches my eye. I can't tell if the phone is "half-rooted" (no unlocked bootloader), or if it's just that Casual sees that my phone is already rooted so it doesn't bother trying to do it again (which is fine, I can understand that point, if it is true).
ClockworkRecovery Mod fails when trying to backup my current ROM (unlocked TouchWiz, no custom ROM installed yet). When I push "Backup Current ROM" in ROM Manager, it reboots the phone (crashes) and puts it into recovery mode, but there's nothing to recover. So my screen goes to the Yellow Triangle of Death screen and gives me a red error message in the top-left corner saying "secure kernel: fail". I had to reboot the phone using Volume Down+Home+Power, and it goes right back to a normal startup. This is what leads me to believe my bootloader is still locked, and I can't find a way to overcome that. I NEVER see the CWM menu to wipe cache, data, etc.
Titanium Backup failed to backup my SMS messages (everything else went fine). It gives me an XML error right away. I used a different app to back them up, which gave me no problems. Not sure if this is related to the larger problem, but I figured it was worth mentioning.
What I'm asking: I'm wanting to make sure that I've got all my bases covered. I know I've done my backups through Titanium Backup correctly, but I do remember that with my Thunderbolt I had to copy down some ID numbers related to the phone so I could sync it after installing a custom ROM (I haven't read any mention of this with the S3, so I'm a bit worried that I'm missing something).
CWM not working correctly is what's throwing me off- I don't want to get my phone stuck in bootloops like before. I want to backup my current setup, clean the cache/data/etc, install the ROM and then restore my apps and data.
I want to avoid resorting to ODIN and putting my phone back to stock (and risk getting the OTA 4.3 update, which I refuse to do) to be able to load this ROM, but if that's what I need to do, then so be it.
Any help, insights, etc would be immensely appreciated! I've read countless threads over the last few months (and especially in the last week), and the fact that there isn't much documentation regarding MF1 when it comes to installing bootchains and ODIN makes me feel like I'm groping in a dark a bit.
Many thanks!
Wow, long post.
Sounds like you're rooted, so download ez unlock v 1.2 to flash the insecure aboot. Then flash the rom after.
You should be good to go after that.
Edit : additionally, I wouldn't restore any apps or data from tibu in this case, going from 4.1.2 to 4.3 changes quite a bit of file structuring and could cause problems.
Sent from my SCH-I535 using Tapatalk 2
Thanks for the reply! And yes, sorry for the long post- I opted to be thorough and give all the relevant information up front instead of playing a cat-and-mouse game of having to post repeatedly with information I could've posted at the beginning.
I heard about EZ Unlock but wasn't sure if it was still appropriate to use in this case. Per your instructions, I will sideload the APK and make magic happen from there.
I DID encounter something new just about an hour ago- I used Casual but I got no errors this time. Hopefully that is a sign of good things to come.
And thanks for the heads up about TiBu backups not working well- that right there saved me a LOT of headaches, I'm sure.
This being the case, however, how would I link my device to Verizon/Google if no data is restored at all from the backup, like account information and such? And would I still be able to restore my SMS/call log (they're in an XML file, not in app data)?
Again, many thanks!
DuoDSG said:
Thanks for the reply! And yes, sorry for the long post- I opted to be thorough and give all the relevant information up front instead of playing a cat-and-mouse game of having to post repeatedly with information I could've posted at the beginning.
I heard about EZ Unlock but wasn't sure if it was still appropriate to use in this case. Per your instructions, I will sideload the APK and make magic happen from there.
I DID encounter something new just about an hour ago- I used Casual but I got no errors this time. Hopefully that is a sign of good things to come.
And thanks for the heads up about TiBu backups not working well- that right there saved me a LOT of headaches, I'm sure.
This being the case, however, how would I link my device to Verizon/Google if no data is restored at all from the backup, like account information and such? And would I still be able to restore my SMS/call log (they're in an XML file, not in app data)?
Again, many thanks!
Click to expand...
Click to collapse
Don't be sorry for the long post, much better to be detailed and explain as much as you can. Shows you did some research before asking. I wish everyone researched that much before posting.
Ez unlock is great to use in this case, it will brick your phone if you're on 4.3.
You can always restore your contacts from googles database, as far as restoring call logs and sms messages you should be OK. But if you encounter any lag or bugs it could have something to do with that.
Sent from my SCH-I535 using Tapatalk 2
All right, so I followed your instructions. I sideloaded EZ Unlock, which did the trick, and then I went into CWM Recovery, wiped the data, cache and dalvik.
Then I went ahead and loaded the ROM zip from the SD card, and VOILA! Without a hitch. The phone is snappier than EVER and it's just a matter of downloading the apps I want to again from the play store. Even the data speeds--whether on WiFi or 4G--are blazing fast, I never encountered speeds like this, even when I first got my phone stock from Verizon.
I was pleasantly surprised that my phone didn't have an identity crisis (as had happened when I rooted and loaded a custom ROM on my HTC Thunderbolt years ago). Right away it knew my phone number, and my Google account sync was flawless.
So far, extremely impressed. And I can breathe a sigh of relief that I OVERprepared for this instead of missing something crucial (so far! fingers crossed). Before, under 4.1.2, I used a combination of Greenify, freezing unwanted bloatware/system apps and Xposed Framework to get my phone to do incredible things, and I look forward to seeing how everything works under 4.3 without Verizon's slimy tentacles all over my phone again.
I will continue to update the thread as I run into issues or curious info that might be useful to anyone considering going through the same process. Surely my experience and effort can allow someone else to have an easier time than I did!
Thank you again for your help- it may have seemed simple, but the direction and reassurance you gave was all the help I needed to make it happen and not blow up my phone

Kernel is not seandroid enforcing - sm-g930f

OK, so on boot I get this warning, "KERNEL IS NOT SEANDROID ENFORCING" after upgrading to latest stock firmware and re installing TWRP. I also note that when I try and do anything in TWRP it tells me that the /data partition can not be mounted and a couple of other errors. I understand that this is because the stock ROM encrypts the /data directory, no reason to doubt this, but it wasn't there before I flashed the stock ROM upgrade - done because I had a new version notification driving me made.
I have seen that I can wait for TWRP to add something to it's tools to fix this, if they are even looking at it. Or I can re-partition data via TWRP.
If I do the latter, if I use TWRP to make a copy of the data partition and restore after, would I be reintroducing the encryption?
If it does fix it and the TWRP restore introduces the encryption back, would Titanium restore everything without encryption?
Is it even a fix?
Advise sort here please....
did u ever solve this i also have it but im on holiday and unable to get access to any stock firmware... files are too big for international downloads. it will cost me like £30 to download the one file i need to flash using odin and it bothers me this could happen again after.
I modified the build.prop file to allow tethering to work something along the lines of tether_required_dun 0 to the bottom as described in many posts but the phone went immediately into boot loo.
TWRP is on and working correctly.
phone was rooted.
oem unlock ticked
i can adb to the phone correctly
i used to get recorevy is not seandroid enforcing. that changed to kernel is not seandroid enforcing. and i can now no longer boot.
bit of a strange one...
twiztednibbz said:
did u ever solve this i also have it but im on holiday and unable to get access to any stock firmware... files are too big for international downloads. it will cost me like £30 to download the one file i need to flash using odin and it bothers me this could happen again after.
I modified the build.prop file to allow tethering to work something along the lines of tether_required_dun 0 to the bottom as described in many posts but the phone went immediately into boot loo.
TWRP is on and working correctly.
phone was rooted.
oem unlock ticked
i can adb to the phone correctly
i used to get recorevy is not seandroid enforcing. that changed to kernel is not seandroid enforcing. and i can now no longer boot.
bit of a strange one...
Click to expand...
Click to collapse
I did but I am not happy about the fix.
I had to wipe the data partition in the advance mode and reformat it. I always do things three times to make sure. SO effectively has to start from scratch with the phone set up. I didn't use the back up as it may have reintroduced the problem, so after I wiped the old backup and created a new, and then built the phone and created another new backup in TWRP.....
I still find certain apps don't work, like Cerberus - hidden, Cool Tool, APM+........
Hope it helps you.
jonners59 said:
I did but I am not happy about the fix.
I had to wipe the data partition in the advance mode and reformat it. I always do things three times to make sure. SO effectively has to start from scratch with the phone set up. I didn't use the back up as it may have reintroduced the problem, so after I wiped the old backup and created a new, and then built the phone and created another new backup in TWRP.....
I still find certain apps don't work, like Cerberus - hidden, Cool Tool, APM+........
Hope it helps you.
Click to expand...
Click to collapse
Hi mate.
Yes unfortunately same boat here... ended up putting superman on but i lost all the last 2 weeks worth of holiday photos ive just taken and i leave in 3 days ffs. The rest i had pretty much backed up before i left. Just not often u get the chance to film a live octopus feeding in rock pools on a beach among the 3000 photos ive taken.
Ah well theae things happen. It is weird because everywhere i read people have great success doing what i did even on a stock rom non rooted so dont know why mine went pair shaped.
I spose the benefits are this rom is far superior to stock. Everything seems to work so far. Superman 1.17. Dont know of youve tried it but since your in same boat on a fresh install its really worth a look. Sorry to hear of ya loss.
twiztednibbz said:
Hi mate.
Yes unfortunately same boat here... ended up putting superman on but i lost all the last 2 weeks worth of holiday photos ive just taken and i leave in 3 days ffs. The rest i had pretty much backed up before i left. Just not often u get the chance to film a live octopus feeding in rock pools on a beach among the 3000 photos ive taken.
Ah well theae things happen. It is weird because everywhere i read people have great success doing what i did even on a stock rom non rooted so dont know why mine went pair shaped.
I spose the benefits are this rom is far superior to stock. Everything seems to work so far. Superman 1.17. Dont know of youve tried it but since your in same boat on a fresh install its really worth a look. Sorry to hear of ya loss.
Click to expand...
Click to collapse
Do you not put pics on external SD or have sync to google or OneDrive etc.... I was lucky in that respect as I keep nothing of any note on the internal storage and docs/etc are all sync'd It's the days of re doing settings that p me off. And Titanium never puts it back as you want really.
I think the prob is encryption. I believe that the stock ROM encrypts the data drive.
I am on stock, rooted. I am not happy with the stock and can't wait for a non stock build to come out - I don't think there are any yet, that are not built on the stock. Superman is modified stock, yes? How do you find it and what are the differences?
jonners59 said:
Do you not put pics on external SD or have sync to google or OneDrive etc.... I was lucky in that respect as I keep nothing of any note on the internal storage and docs/etc are all sync'd It's the days of re doing settings that p me off. And Titanium never puts it back as you want really.
I think the prob is encryption. I believe that the stock ROM encrypts the data drive.
I am on stock, rooted. I am not happy with the stock and can't wait for a non stock build to come out - I don't think there are any yet, that are not built on the stock. Superman is modified stock, yes? How do you find it and what are the differences?
Click to expand...
Click to collapse
Same as you really but I moved everything before i left for my vacation. ive never actually worked out how to get the camera to save direct to the sd card if thats even poasible upto now so i just move them all every two weeks onto the sandisk extreme.
I cant use the auto sync in this country because the file sizes are so large of the photos that it would cost me more then buying a brand new dslr camera to upload one holiday on the fly. Lol
Yeah that totally grates me too tbh but these pictures really got my goat your right about titanium too. All the other ones are the same. The only backup program thats ever worked properly for me is the lg g4 h815 built in one its brilliant.
You are correct about the encryption i didnt think using that command would soft brick the phone or i wouldnt have done it before backing up. You have to format the data partition to remove the encryption which in turns wipes all your data.
I was on stock h3g uk rooted software but it was so locked down even with root it made life difficult. I dont like to stray too far away from the stock experience these days most are quite adept.
Superman is modified stock a lot of it is based on the nougat rom that is due out after MM. It also has the edge features and swipe bar etc.
Its slick fast and totally brilliant. Android pay doesnt work i dont believe but there is very little else.
No bugs to my knowledge
There are audio and volume enhancements as well. Camera enhancements. Kustom kernels.
It uses aroma inataller so you can choose what you want to install as well.
Definately the best rom ive tried for many years. Turned my boring galaxy into a sharp snappy customisable device that i am over the moon with. If only samsung employed some of these people...
Honestly if you can live with the one or two things that dont work its so much better.
You mention things don't work. what does not work?

Categories

Resources