Hello everybody. I recently flashed my phone with the latest Cyanogenmod rom for the HTC one, using the wHil recovery flasher. However after playing with the rom for a bit I decided I want to swap back to stock everything that came with my phone. What is the process to go about doing this?
Thanks!
Did you make a nandroid before flashing the Rom, if yes then just flash it then flash stock tmobile recovery img then relock the bootloader..just do a quick search and you find out how to do it... But it will still say tampered on bootloader... But ota will work cause that only requires stock recovery and stock Rom
Sent from my HTC One using Tapatalk 2
I did not, however I downloaded someone else's stock nandriod dump.
So all I need to do is flash the stock rom, flash the stock recovery, relock the bootloader and I should be able to get OTA updates and all that good stuff again?
GeePM said:
I did not, however I downloaded someone else's stock nandriod dump.
So all I need to do is flash the stock rom, flash the stock recovery, relock the bootloader and I should be able to get OTA updates and all that good stuff again?
Click to expand...
Click to collapse
Yes, that's what I did, and OTA updates work perfert
That's great to hear. So I shouldn't experience any issues when I return to the stock rom like loosing any kind of features and such?
I've been having issues trying to adb push this backup to my phone since 4.2 andriod has things locked down in regards to backups. Been getting the device not found issue, so I'm going to try and push it using a different PC soon hopefully. With where I work I can't live without WiFi calling/texting that Cyanogenmod lacks
So I have the stock backup through clockwork mod and I have it in the proper /clockworkmod/backup folder. Problem is, clockwork mod touch isn't detecting that I have any backups to restore. So I decided to make a fresh backup just to see where it was placed so I could put this other backup I downloaded in there.
Problem. I can't find it anywhere. I don't know where to put it. I don't know where clockworkmod touch wants it to go. Any ideas?
EDIT: Apparently there are two of these folders? *looking more*
EDIT 2: Clearly, If I try to restore from the saved backups, it shows the backup I made, but no amount of searching is finding it through any of my file managers. I'm finding the backup I downloaded, but not the one I made. wtf? Are there hidden folders or something? I have root access.
EDIT 3: There are apparently two clockwork mod folders on my phone. Clockwork mod is saying that it sees the test backup I made on 6-10, but when I check in my file manager for a backup, it shows me the folder with a 4-26 backup which is what I want to restore. The FILE MANAGER sees a folder with 4-26, whereas clockworkmod sees a folder with a backup of 6-10. Both folders are apparently clockworkmod/backup. Does anyone have any idea what's going on here?
So I just flashed the stock rom, reinstalled the stock rescue image, and relocked my bootloader.
How long does it take for me to be able to get the 4.2 update?
change yearThe
GeePM said:
So I just flashed the stock rom, reinstalled the stock rescue image, and relocked my bootloader.
How long does it take for me to be able to get the 4.2 update?
Click to expand...
Click to collapse
Nevermind! Just went to the upgrade section and got it
GeePM said:
Nevermind! Just went to the upgrade section and got it
Click to expand...
Click to collapse
4.2?????
blackangst said:
4.2?????
Click to expand...
Click to collapse
Nevermind, I still don't have it. Was 4.2 pushed out yet?
GeePM said:
Nevermind, I still don't have it. Was 4.2 pushed out yet?
Click to expand...
Click to collapse
No. Not on TMobile.
Related
I have to return my European GSM Hero to HTC because of a problem with the backlight and usb connection so I should restore it to the original ROM.
It's currently running one of the 2.1 ROMs and has the RA-hero-1.6.2 recovery image also.
I have all the nandroid backups I made along the way including the first one which includes boot, cache, data, misc, recovery and system. Although the recovery image in this backup would be the custom one I put on there when I first rooted it.
I also have the original recovery image that was saved when I first rooted the phone using the flashrec app.
So I guess the procedure to restore it would be:
1. First restore the earliest nandroid backup and then,
2a. Boot into the old custom recovery and flash the original recovery image.
2b. Or I could use flashrec again to restore the original recovery image.
Any thoughts? Suggestions? Gotchyas I should know about?
Also is there anything special I have to do with the Radio? Do I need to restore to the original radio too?
Solved:
So I followed this procedure and it worked perfectly to restore my phone to the original ROMs:
1. Boot into recovery and restore earliest nandroid backup (which contained the original ROM but an old version of a custom recovery)
2. Reboot phone
3. Boot into the old recovery and flash an update.zip for the original radio
4. Reboot phone twice
5. Boot up phone and run flashrec, but flash the phone with the backup recovery image I made when I ran flashrec originally.
6. Restore the phone to factory settings before sending it back to HTC.
I didn't need to use the HTC Sync software or the RUUs at all and it all seems to have worked fine.
Thanks everyone for your help.
Orginal rom?
Download and install a orginal RUU rom update, and i belive Radio, rom etc. will be flashed to the stock rom?
Wow, useful first post!
I know you can flash the original HTC rom in update.zip format, but that will keep the custom recovery intact. After this you should restore the original recovery with flashrec.
in contrast to your 26th post chool's first post contains the correct answer to the question...
But it was still more informative than your 1,217th.
Chool is spot-on, though. You can download the HTC Sync software and run the original rom's RUU once it's connected to your phone, and it will set it back to the default original.
rayjt9 said:
But it was still more informative than your 1,217th.
Click to expand...
Click to collapse
are you drunk, dumb or both?
edit: since THIS POST is #1217 for me you are actually right. yet my questions remains...
I should have mentioned that I'm on Linux. I'm pretty sure the HTC Sync software is only for Windows. I can get Windows if I need to, so that's not too much of a problem.
I have heard that running the RUUs once you have changed your Radio can be harmful? Is there any truth to that?
kendong2 said:
are you drunk, dumb or both?
edit: since THIS POST is #1217 for me you are actually right. yet my questions remains...
Click to expand...
Click to collapse
In answer to your question, neither. I was going by the numbers at the top right of your posts, which, this morning, was 1217. Did you perhaps delete something sending it back to 1216?
bonneHero said:
I should have mentioned that I'm on Linux. I'm pretty sure the HTC Sync software is only for Windows. I can get Windows if I need to, so that's not too much of a problem.
I have heard that running the RUUs once you have changed your Radio can be harmful? Is there any truth to that?
Click to expand...
Click to collapse
Hmm, it doesn't look like there's an alternative to HTC Sync which would work for Linux, as far as I'm aware. I haven't heard of any problems with RUUing after a radio change, but if you're concerned, I believe there should be no harm in reflashing your radios with the original versions first.
Hi, stupid question here from a relative noob....
I have a Cincinnati Bell Vibrant, that I recently flashed CM7 on (after using Rom Manager to backup up my stock rom). Liked it, but found it too battery-intensive, so I booted into clockworkmod recovery and attempted to restore the backup of my stock rom. It failed on flashing the boot image, and now my phone is stuck on the Vibrant screen, and won't boot. None of the hardware combinations to get into recovery mode are working, but I can get it into download mode. Before I screw things up further, what is the best way to go from here to get the backup restored, or is it even possible at this point?
Thanks
tabbott01 said:
Hi, stupid question here from a relative noob....
I have a Cincinnati Bell Vibrant, that I recently flashed CM7 on (after using Rom Manager to backup up my stock rom). Liked it, but found it too battery-intensive, so I booted into clockworkmod recovery and attempted to restore the backup of my stock rom. It failed on flashing the boot image, and now my phone is stuck on the Vibrant screen, and won't boot. None of the hardware combinations to get into recovery mode are working, but I can get it into download mode. Before I screw things up further, what is the best way to go from here to get the backup restored, or is it even possible at this point?
Thanks
Click to expand...
Click to collapse
This doesn't sound too bad. Basically you want to Odin back to stock. Then reflash the rom you were on, then you can reboot back into recovery and restore your backup. If voodoo was enabled on your backup make sure voodoo is enabled again before restoring(it might work either way, but I'm not sure). When I've done this, I restore a prerooted 2.2 stock Rom without changing the bootloaders, but almost any official stock rom will also work. I'm on the go, so I don't have a link handy, but post back if needed and I will point you to the odin package I use. Good luck.
I also am having some issues with Clockworld recovery. The problem i am having is that when doing a nandriod backup this is the error i am recieving
"E:cant mount /dev/block/mmcblk1p1 (or @)
Cant mount /mnt/sdcard
any suggestions on whats going on?
phone_noobie said:
I also am having some issues with Clockworld recovery. The problem i am having is that when doing a nandriod backup this is the error i am recieving
"E:cant mount /dev/block/mmcblk1p1 (or @)
Cant mount /mnt/sdcard
any suggestions on whats going on?
Click to expand...
Click to collapse
Are you sure the sdcard is good? If so then I would follow the same steps listed above, that way you know your CWR is good.
mattb3 said:
Are you sure the sdcard is good? If so then I would follow the same steps listed above, that way you know your CWR is good.
Click to expand...
Click to collapse
yes it is good because i can see all the videos, pics i have saved in it. Also i put the new ROM on my internal sd card and its there so sd card is def good. What could be causing the problem?
To the op, I would use Odin, no real worries there.
To the other guy with sdcard issue, try moving all files to your PC, format your sdcard, reboot, move files back, flash cwr in ROM mgr, backup work? Move critical files back from PC.
mattb3 said:
This doesn't sound too bad. Basically you want to Odin back to stock. Then reflash the rom you were on, then you can reboot back into recovery and restore your backup. If voodoo was enabled on your backup make sure voodoo is enabled again before restoring(it might work either way, but I'm not sure). When I've done this, I restore a prerooted 2.2 stock Rom without changing the bootloaders, but almost any official stock rom will also work. I'm on the go, so I don't have a link handy, but post back if needed and I will point you to the odin package I use. Good luck.
Click to expand...
Click to collapse
Thanks...that's exactly what I did, except the backup would never quite "take." It completely loaded and cycled through the boot process, but I ended up on a boot-restore loop. So now I've Odin-ed back to stock with the closest build I could find to my stock (which I don't think is out there yet - FROYO.UVJL6.ULTIMOBILE - do you know anywhere to find it?), rooted, and am searching for a good, stable, battery-friendly mod once again.
s15274n said:
try moving all files to your PC, format your sdcard, reboot, move files back, flash cwr in ROM mgr, backup work? Move critical files back from PC.
Click to expand...
Click to collapse
i did try formatting, then moving all the stuff back and am still getting that same error message
^ what rom are you on, if one?
You could always ODIN, and use my option b cwr in the noob guide. I just tested making a backup using trigger 8/22 and know there are no issues. Not really sure whats up on your end. I will say though, I've emailed koush several times that there is an issue with cwr on the vibrant from rom manager, for some it won't even flash.
phone_noobie said:
i did try formatting, then moving all the stuff back and am still getting that same error message
Click to expand...
Click to collapse
try different sd card..or reinstall CWM...
Alright, so I wiped my phone in TWRP in preparation to flash something and I neglected to make a backup (I know, rookie mistake). The ROM I tried flashing will not go through and now I am stuck. I can boot into recovery fine but I really need a ROM to flash so I have something to boot into. I can't use an RUU (I have tried), probably because I used the bootloader unlock/root work-around. I'd gladly take any advice but I think what I need is just a flashable .zip of the stock ROM or maybe a backup I can restore in TWRP. If some kind soul could help me out, I'd be forever grateful.
are you referring the the stock rom offered by mycomputerdoctor? If so, the flashing does fail, but your phone will still work. From what I understand the only problem is the error in TWRP and you wont have root anymore.
My phone does indeed still work, but I wiped /system before trying to flash so I don't have a ROM installed currently and therefore cannot boot past the splash screen.
http://forum.xda-developers.com/showthread.php?t=1999962
docnok63 said:
http://forum.xda-developers.com/showthread.php?t=1999962
Click to expand...
Click to collapse
Unfortunately, that is an RUU, which does not work for me. Thanks, though.
install the rom, even if it says fails, it should still boot. you could also just adb push the updated rom on to your sd card.
Thrillhouse847 said:
Alright, so I wiped my phone in TWRP in preparation to flash something and I neglected to make a backup (I know, rookie mistake). The ROM I tried flashing will not go through and now I am stuck. I can boot into recovery fine but I really need a ROM to flash so I have something to boot into. I can't use an RUU (I have tried), probably because I used the bootloader unlock/root work-around. I'd gladly take any advice but I think what I need is just a flashable .zip of the stock ROM or maybe a backup I can restore in TWRP. If some kind soul could help me out, I'd be forever grateful.
Click to expand...
Click to collapse
Im in the same boat :/ stuck in recovery and have no rom to flash. going to try to adb the latest version and see how that goes.
I was afraid of something like this. We shouldn't be messing with our phones without a back to factory state.
I'm actually all set now. I flashed the updated stock, debloated ROM and made a back up so I'm good to go.
Sent from my HTC6435LVW using Tapatalk 2
hey guys
I recently decided to opt in to flashing 5.0 rom on my device, but ive read somwhere (http://forum.xda-developers.com/tmobile-galaxy-s5/general/warning-flashing-bootloader-modem-t3037034) that people are having trouble restoring backed up roms and even going back to NK2 with full odin wipe. I have also read that flashing a custom 5.0 kernel will resolve this issue. Is that true, i want to know by someone with expirience. And also can i flash custom roms while on 5.0 bootloader if i load it with a custom kernel.
IAM NOT planning on taking the OTA update but rather ViSiON-X Rom http://forum.xda-developers.com/showthread.php?t=2797336.
My main concern is being able to flash roms/restoring/backing up, specifically custom roms not touchwiz based and Kitkat.
THANKS IN ADVANCE
androidfine16 said:
hey guys
I recently decided to opt in to flashing 5.0 rom on my device, but ive read somwhere (http://forum.xda-developers.com/tmobile-galaxy-s5/general/warning-flashing-bootloader-modem-t3037034) that people are having trouble restoring backed up roms and even going back to NK2 with full odin wipe. I have also read that flashing a custom 5.0 kernel will resolve this issue. Is that true, i want to know by someone with expirience. And also can i flash custom roms while on 5.0 bootloader if i load it with a custom kernel.
IAM NOT planning on taking the OTA update but rather ViSiON-X Rom http://forum.xda-developers.com/showthread.php?t=2797336.
My main concern is being able to flash roms/restoring/backing up, specifically custom roms not touchwiz based and Kitkat.
THANKS IN ADVANCE
Click to expand...
Click to collapse
I downloaded 5.0. Was NOT satisfied and put KitKat back on. No problems doing that at all but I an NOT rooted.
androidfine16 said:
hey guys
I recently decided to opt in to flashing 5.0 rom on my device, but ive read somwhere (http://forum.xda-developers.com/tmobile-galaxy-s5/general/warning-flashing-bootloader-modem-t3037034) that people are having trouble restoring backed up roms and even going back to NK2 with full odin wipe. I have also read that flashing a custom 5.0 kernel will resolve this issue. Is that true, i want to know by someone with expirience. And also can i flash custom roms while on 5.0 bootloader if i load it with a custom kernel.
IAM NOT planning on taking the OTA update but rather ViSiON-X Rom http://forum.xda-developers.com/showthread.php?t=2797336.
My main concern is being able to flash roms/restoring/backing up, specifically custom roms not touchwiz based and Kitkat.
THANKS IN ADVANCE
Click to expand...
Click to collapse
I updated via Odin tar file.
About restoring from a nandroid custom recovery backup:
I think/thought I mentioned this in that first thread you linked, but, you cannot in any way restore an old backup onto a new version of android irregardless the device or recovery. Say the system apk, settings apk uses a file named xyz.dat in KitKat, it saves that file to your /data directory. You now go ahead and flash Lollipop which now that same system apk, the settings apk uses a file named yzx.dat, you go and restore your backup restoring the file xyz.dat. Now the settings apk which is a system apk, cannot find this file and runs into a bootloop because not finding the file should never happen but since you went behind its back to remove that file, you confused it majorly.
I use Titanium Backup to restore my apps, best money ever spent.
I personally went back to KitKat, cause, well, I missed xposed more than i thought i would lol. Everything just worked the way I wanted it to with xposed.
I did have to Odin flash a KitKat based ROM in order for it to work though. After that, I restored my full nandroid backup and everything is working again.
My recommendations to you:
1. Take a FULL backup using TWRP or other custom recovery, this includes backing up your system, data, and boot.
2. Flash the Lollipop update using Odin.
3. DO NOT WIPE DATA
4. Reboot.
You should see "android is upgrading" and have a Lollipop build with all your apps still there. i got a few force closes so I ended up wiping my data, but those apps that forced closed were all root apps that were looking for system files that didn't exist anymore.
elesbb said:
I updated via Odin tar file.
About restoring from a nandroid custom recovery backup:
I think/thought I mentioned this in that first thread you linked, but, you cannot in any way restore an old backup onto a new version of android irregardless the device or recovery. Say the system apk, settings apk uses a file named xyz.dat in KitKat, it saves that file to your /data directory. You now go ahead and flash Lollipop which now that same system apk, the settings apk uses a file named yzx.dat, you go and restore your backup restoring the file xyz.dat. Now the settings apk which is a system apk, cannot find this file and runs into a bootloop because not finding the file should never happen but since you went behind its back to remove that file, you confused it majorly.
I use Titanium Backup to restore my apps, best money ever spent.
I personally went back to KitKat, cause, well, I missed xposed more than i thought i would lol. Everything just worked the way I wanted it to with xposed.
I did have to Odin flash a KitKat based ROM in order for it to work though. After that, I restored my full nandroid backup and everything is working again.
My recommendations to you:
1. Take a FULL backup using TWRP or other custom recovery, this includes backing up your system, data, and boot.
2. Flash the Lollipop update using Odin.
3. DO NOT WIPE DATA
4. Reboot.
You should see "android is upgrading" and have a Lollipop build with all your apps still there. i got a few force closes so I ended up wiping my data, but those apps that forced closed were all root apps that were looking for system files that didn't exist anymore.
Click to expand...
Click to collapse
Yeah I avoided lollipop all together. People seem to be having too many problems with it.I installed NK2 via Odin and now rooted/exposed. Runs smooth and I can flash other Roms.
But I do have this one issue. My auto rotation rodent seem to be working I tried everything I can think of. At first boot it works for 10 minutes or 5 sometimes. Than it shuts down completely. Accelerometer isn't working either. No temple run movement or asphalt 8 (sucks). I did sensor firmwate update and ran samsung diagnostic. The sensor seem to be at 0,0 on x and y axis. At first boot they work fine though. Any help please. I even tried different kernel and software Roms to no Vail. And I don't think it's hardware cause it works for brief moments.
Sent from my SM-G900T using XDA Free mobile app
I let the lollipop update happen.. Used the last day and everything seems fine but I can't use Screen mirroring which I use alot.. anyway I downloaded the stock 4.4.2 md5 and odin completely successfully writes it and after it reboots it is stuck at the Tmobile 4gLTE bootscreen.. I've rebooted it and waited a long time.. as well as rewriting. Guess I'll have to download the stock lollipop tar and hope it boots
tri0xinn said:
I let the lollipop update happen.. Used the last day and everything seems fine but I can't use Screen mirroring which I use alot.. anyway I downloaded the stock 4.4.2 md5 and odin completely successfully writes it and after it reboots it is stuck at the Tmobile 4gLTE bootscreen.. I've rebooted it and waited a long time.. as well as rewriting. Guess I'll have to download the stock lollipop tar and hope it boots
Click to expand...
Click to collapse
The 4.4.2 .tar is a "non-wipe" .tar. You need to go into stock recovery and do a factory data reset after flashing.
Did the trick, thanks!
muniz_ri said:
The 4.4.2 .tar is a "non-wipe" .tar. You need to go into stock recovery and do a factory data reset after flashing.
Click to expand...
Click to collapse
Does downgrading like this trips Knox?
Thanks
chiquito3 said:
Does downgrading like this trips Knox?
Thanks
Click to expand...
Click to collapse
I downgraded my wife's phone using the official 4.4.2 firmware from sammobile, and it did NOT trip knox.
You've probably heard this song and dance before, but my phone only charges if I hold the connector a little to the left of the port of the phone. This is a phone issue, I've tried like 5 cables. I am rooted so I'm worried att will just turn me away if I go to a repair place. I am s-on. I'm hoping maybe this is something I can fix myself. Any ideas?
Secondly, today I noticed that my mobile data only works for browsing google. Only google's web results show up. If I click on a link from there, it won't work. Any other app does not work. I've tried a soft reset and rebooting several times, and no I don't have any proxies enabled. If anyone has the stock lollipop build.prop, I'd really appreciate that. Very strange issue that I've never heard of. Running elementalx kernel and stock rom.
siren_shadows said:
my phone only charges if I hold the connector a little to the left of the port of the phone. This is a phone issue, I've tried like 5 cables. I am rooted so I'm worried att will just turn me away if I go to a repair place. I am s-on. I'm hoping maybe this is something I can fix myself. Any ideas?
Click to expand...
Click to collapse
If you purchased the phone from AT&T, they will not deny warranty due to root, unlocked bootloader, etc. Folks here have had good success with warranty claims on modified phones with AT&T. If you look at AT&T's warranty terms, you will see that they changed a year or 2 ago. Modifying the software is no longer mentioned under the items that void the warranty. Only physical damage and water damage are now listed.
siren_shadows said:
Secondly, today I noticed that my mobile data only works for browsing google. Only google's web results show up. If I click on a link from there, it won't work. Any other app does not work. I've tried a soft reset and rebooting several times, and no I don't have any proxies enabled. If anyone has the stock lollipop build.prop, I'd really appreciate that. Very strange issue that I've never heard of. Running elementalx kernel and stock rom.
Click to expand...
Click to collapse
What happens if you just type in a URL, without going through Google search results?
redpoint73 said:
If you purchased the phone from AT&T, they will not deny warranty due to root, unlocked bootloader, etc. Folks here have had good success with warranty claims on modified phones with AT&T. If you look at AT&T's warranty terms, you will see that they changed a year or 2 ago. Modifying the software is no longer mentioned under the items that void the warranty. Only physical damage and water damage are now listed.
What happens if you just type in a URL, without going through Google search results?
Click to expand...
Click to collapse
ah, thanks. if I type in a URL, I get the same dns lookup error. seems YouTube, Instagram, and Google are the only things that work. play store does not work.
siren_shadows said:
ah, thanks. if I type in a URL, I get the same dns lookup error. seems YouTube, Instagram, and Google are the only things that work. play store does not work.
Click to expand...
Click to collapse
Did you make any recent changes that may have caused this, such as flashing the custom kernel?
redpoint73 said:
Did you make any recent changes that may have caused this, such as flashing the custom kernel?
Click to expand...
Click to collapse
yeah, I reinstalled elementalx. I'd love a stock build.prop and an insecure stock kernel if that's possible.
siren_shadows said:
yeah, I reinstalled elementalx. I'd love a stock build.prop and an insecure stock kernel if that's possible.
Click to expand...
Click to collapse
Did you modify build.prop?
redpoint73 said:
Did you modify build.prop?
Click to expand...
Click to collapse
yeah, but I deleted the values. I'm worried I may have deleted something I wasn't meaning to, though.
siren_shadows said:
yeah, but I deleted the values. I'm worried I may have deleted something I wasn't meaning to, though.
Click to expand...
Click to collapse
WNC just posted the 4.28.502 version of his ROM here: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
I assume the build.prop is stock; and kernel is insecure.
unfortunately, I am s-on.
siren_shadows said:
unfortunately, I am s-on.
Click to expand...
Click to collapse
s-off is only needed to flash firmware (and it sounds like you already have Lollipop firmware).
You can pull boot.img from the ROM.zip without even actually flashing the whole ROM.
build.prop, not sure if there is a similar way to do that (extract without flashing he whole ROM). Otherwise, flash the ROM, and extract/copy the build.prop for use on the fully stock ROM.
Or just flash the ROM and use it, WNC's work is always good. Its basically the stock ROM, just cleaned up.
redpoint73 said:
s-off is only needed to flash firmware (and it sounds like you already have Lollipop firmware).
You can pull boot.img from the ROM.zip without even actually flashing the whole ROM.
build.prop, not sure if there is a similar way to do that (extract without flashing he whole ROM). Otherwise, flash the ROM, and extract/copy the build.prop for use on the fully stock ROM.
Or just flash the ROM and use it, WNC's work is always good. Its basically the stock ROM, just cleaned up.
Click to expand...
Click to collapse
I'm not averse to using the ROM, I just don't want to lose my data or have any long boots/incompatibility issues. I used the latest OTA from the official att update.
siren_shadows said:
I'm not averse to using the ROM, I just don't want to lose my data or have any long boots/incompatibility issues. I used the latest OTA from the official att update.
Click to expand...
Click to collapse
You shouldn't have any long boot or imcompatibility issues. The ROM I linked is based on the same ROM you are on (AT&T Lollipop update) just with bloat removed and some performance enhancements. What you can do, if you want to keep the current stock ROM:
1) Download the ROM I linked
2) Unzip on your computer
3) Find boot.img, copy it to your fastboot folder. This should be the stock, insecure kernel
4) Connect phone to computer in fastboot mode
5) Flash boot.img with command: fastboot flash boot boot.img
Reboot the phone, and see if the data is working again. If not, you can try to restore the build.prop. I don't personally know of a way to pull this from the ROM similar to above for the kernel. So this may be a little convoluted, but just a thought:
6) Make a nandroid of the current setup
7) Flash the ROM by WNC
8) Use a file explorer to copy build.prop file to internal storage or the removable SD
9) Restore your nandroid (back to stock AT&T) that you just made in Step 6 above
10) Copy the build.prop from WNC's ROM to overwrite the one that you modified
11) If it doesn't work, you are no worse off since you have a nandroid snapshot of your current setup (won't lose any user data)
redpoint73 said:
You shouldn't have any long boot or imcompatibility issues. The ROM I linked is based on the same ROM you are on (AT&T Lollipop update) just with bloat removed and some performance enhancements. What you can do, if you want to keep the current stock ROM:
1) Download the ROM I linked
2) Unzip on your computer
3) Find boot.img, copy it to your fastboot folder. This should be the stock, insecure kernel
4) Connect phone to computer in fastboot mode
5) Flash boot.img with command: fastboot flash boot boot.img
Reboot the phone, and see if the data is working again. If not, you can try to restore the build.prop. I don't personally know of a way to pull this from the ROM similar to above for the kernel. So this may be a little convoluted, but just a thought:
6) Make a nandroid of the current setup
7) Flash the ROM by WNC
8) Use a file explorer to copy build.prop file to internal storage or the removable SD
9) Restore your nandroid (back to stock AT&T) that you just made in Step 6 above
10) Copy the build.prop from WNC's ROM to overwrite the one that you modified
11) If it doesn't work, you are no worse off since you have a nandroid snapshot of your current setup (won't lose any user data)
Click to expand...
Click to collapse
I've got some very bad news. I tried replacing the build prop with the one in the zip that you linked, and now my phone won't boot up. at all. can't even get into recovery.
siren_shadows said:
I've got some very bad news. I tried replacing the build prop with the one in the zip that you linked, and now my phone won't boot up. at all. can't even get into recovery.
Click to expand...
Click to collapse
Can you still get into bootloader?
sigh. was able to get into recovery. gonna restore. don't think i had a modified build.prop at that time either... hopefully my cable won't mess up before i copy the backup back onto my phone
redpoint73 said:
Do you mean you can't get into bootloader?
If so, that doesn't actually make any sense, bootloader is write protected with s-on. So there is no way this can be corrupted or over-written.
This seems scary. But just take a breath, as I don't think this is as bad as it looks.
What happened after you copied the file?
Does the screen come on at all?
Click to expand...
Click to collapse
i got a black screen after a reboot. but holding power and volume up did the hard reset and i had to really quickly press volume down. like a split second window
siren_shadows said:
sigh. was able to get into recovery. gonna restore. don't think i had a modified build.prop at that time either... hopefully my cable won't mess up before i copy the backup back onto my phone
Click to expand...
Click to collapse
You didn't need to move the backup off the phone.
Its not a bad idea to make a copy of the backup (in the event the one on internal storage gets wiped) to your computer.
But its also good to keep a backup either on internal storage or on the removable SD.
redpoint73 said:
You didn't need to move the backup off the phone.
Its not a bad idea to make a copy of the backup (in the event the one on internal storage gets wiped) to your computer.
But its also good to keep a backup either on internal storage or on the removable SD.
Click to expand...
Click to collapse
I was a genius and decided I would save space by moving onto my computer. However, I am restoring now. That'll fix my black screen issue, right?
siren_shadows said:
I am restoring now. That'll fix my black screen issue, right?
Click to expand...
Click to collapse
Yes, build.prop is part of the ROM, so the TWRP backup will put you back to where you were before trying to replace the build.prop file.
Odd, I wouldn't think that replacing the build.prop with the one for a nearly stock ROM (and same LP base) would render the phone unbootable into OS.
redpoint73 said:
Yes, build.prop is part of the ROM, so the TWRP backup will put you back to where you were before trying to replace the build.prop file.
Odd, I wouldn't think that replacing the build.prop with the one for a nearly stock ROM (and same LP base) would render the phone unbootable into OS.
Click to expand...
Click to collapse
who knows. My issue isn't fixed regarding mobile data, either. At least I have a usable phone tho!