I am relatively new to Android and last night was my first experience with flashing custom ROMs. After a couple months of reading many different articles and threads on xda and other sites, I tried to make sense of what rooting and flashing meant and was all about. I successfully rooted my device and then last night I tried to unlock the bootloader which I think I did correctly. Then, I tried to install CWM on it which I think also worked. The problems started from then: Rebooting into recovery didn't work (it only gave me a black screen) and I tried to find some solutions online. There wasn't much luck but somehow after many attempts, I was able to boot into recovery. From there, I wiped my data and settings (It wasn't factory reset before), wiped the cache, and wiped the dalvik cache which went all well I think. Then, I tried installing the latest CM10 nightly for the L7 and midway through installation, the phone just rebooted itself. And now, it's stuck on bootloop. I tried many different things and even formatted the system which I think made it worse. Please help!!
The Quick Details:
-LG P705G (Canada, Fido) was running stock ROM V10e i think
-was rooted
-i think bootloader was successfully unlocked
-stuck on bootloop
-formatted the system and now only LG logo appears when I boot (no CM logo)
-I really have no clue what to do :crying:
Thanks!
Check this.
Thanks for the reply
RoberGalarga said:
Check this.
Click to expand...
Click to collapse
Thanks for the reply, do you know if the firmwares will work for my Canadian P705G as well? Because it seems they are all for foreign countries
I dunno, dude. The images available are for locked phones, but I dunno if there are major differences between them (plus carrier apps, of course).
RoberGalarga said:
I dunno, dude. The images available are for locked phones, but I dunno if there are major differences between them (plus carrier apps, of course).
Click to expand...
Click to collapse
Alright thanks I'll give it a shot. One more question do you know if I would be able to update my software back to my original carriers if I was to successfully unbrick it with one of these other ones?
Surely yes.
Related
Greetings
As the tittle points outs, I flashed the latest Androwook Rom(2.1) and it always stucks at the Intro Crawl. I re-downloaded it, flashed it again, but had had no success.
The Prime has been unlocked since May, and it was running the Cyanogen Nightly Rom, before I tried the Wook one. I wiped Cache and Delvik, and tried an older build as well with no success. I use the latest TWRP, 2.1.3. I also tried all availlable kernels and options during the installation with no success.
Can anyone give me a hint as to what is the problem? I can always go back to CM Rom, but I would feel like I accepted defeat.
Also, why does the installation always wipe my internal sd card , when no such option is selected?
drsane1984 said:
Greetings
As the tittle points outs, I flashed the latest Androwook Rom(2.1) and it always stucks at the Intro Crawl. I re-downloaded it, flashed it again, but had had no success.
The Prime has been unlocked since May, and it was running the Cyanogen Nightly Rom, before I tried the Wook one. I wiped Cache and Delvik, and tried an older build as well with no success. I use the latest TWRP, 2.1.3. I also tried all availlable kernels and options during the installation with no success.
Can anyone give me a hint as to what is the problem? I can always go back to CM Rom, but I would feel like I accepted defeat.
Also, why does the installation always wipe my internal sd card , when no such option is selected?
Click to expand...
Click to collapse
jumping from one rom to another needs a full wipe i guess... when you said wiping your internal sd card, that's the reason why you're stuck into crawling? so i guess you use adb to push the ROM, then flash again?
in my case, when i had a bootlop, i push fullwipe.zip first, flash it, then push Androwook.zip, then flash it... it all came back alive..
First of all, thank you for your reply!
Now, to adress each step
jumping from one rom to another needs a full wipe i guess.
Click to expand...
Click to collapse
Yup, did one (factory reset+system wipe) before trying to flash AW Rom.
when you said wiping your internal sd card, that's the reason why you're stuck into crawling? so i guess you use adb to push the ROM, then flash again?
Click to expand...
Click to collapse
After the first three unsuccessfull attempt to flash the ROM did I wipe my internal SD, so it isn't the crawling looping intro's problem. And yes, I push ROMs via Adb, and trying flashing.
in my case, when i had a bootlop, i push fullwipe.zip first, flash it, then push Androwook.zip, then flash it... it all came back alive..
Click to expand...
Click to collapse
That was actually the last step I tried before asking for help. Even after I typed this post, I did it again. Flashed it, pushed AW, and flashed again. No success.
*Edit: I have forgotten a primary Troubleshooting technique. Downloading AW2.1 from a different source, will update.
sorry but im not much of a help i can see... hope somebody could. don't lose hope though...
Intentions matter
Thanks for your time anyway!
After two more failed flashes, I got it to boot!
Apparently the starting animation was causing some kind of problem, which I cannot ever imagine. After I checked the option to have the uggly original boot animation, the rom booted normally and I am now using it.
I am quite happy to get it to work, but if anyone has any solution to the boot problem, I would be really glad to hear him!
drsane1984 said:
Intentions matter
Thanks for your time anyway!
After two more failed flashes, I got it to boot!
Apparently the starting animation was causing some kind of problem, which I cannot ever imagine. After I checked the option to have the uggly original boot animation, the rom booted normally and I am now using it.
I am quite happy to get it to work, but if anyone has any solution to the boot problem, I would be really glad to hear him!
Click to expand...
Click to collapse
Hello Everybody! Guys, sorry for my english!!!!!
First of all, I have to present myself, my name is Marco, I'm italian, 25 years old and I'm in the Android world since about 12 Years.
I started whit a Galaxy S2, and after I bought an Asus Transformer Prime.
After just two week, I decided to put in a Custom ROM, on my devices, and I understood how the system work better instead of a Stock ROM!
And after, I understood, how the XDA Developers Forum is important for me, and expecially for all the people who like to learn about the Android World.
So, I just want to Thanks with all of you for the support that i receive EVERY DAY to solve my problems!
One of these was with flashing the Androwook, weeks ago I flashed the Team EOS 2.0, that was really amazing, but after a While, I found some slowdowns in some action on the system, so i decided to try a rom based on the stock rom, but with improvement and tweaks, so what's better then the Androwook?
The problem was, the same explained on this post, after all wipes, the prime was not boot, and stuck in bootanimation!
I solved, checking the box "Install custom ROM" as drsane1984 have done, and now the ROM is booted perfectly!!
Thanks another time! I'am convinced that if you are able to seach, you'll find for sure the solution to your problems! If not, just ask!
Bye!
I got a brand new BELL SGS2HDLTE yesterday model SGH757 and flashed CWM, everything was ok. This morning I decided I wanted to flash a samsung based ICS rom specifically this on here (http://forum.xda-developers.com/showthread.php?t=1569686). I booted into CWM Recovery, wipe/factory reset wiped cache and dalvik cache and installed the ROM. The setup show up and eventually said complete please reboot. I pressed reboot and the phone turned off and refuses to turn on anymore. The battery was at 44% when I was flashing, even if I plug the phone in via usb nothing happens. I've tried taking out the battery for a few second and putting it back in but nothing happens. I can't boot into CWM or DL mode either, its as if the phone is completely dead... Can someone tell me whats going on here??? I never had an issue like this on my old SGS.. Thanks in advance!
I'm guessing the infamous brick bug is responsible.
What was your configuration before flashing the new ROM?
What ROM and kernel?
Sent from a GT-I9100 having a mind of its own
TechnicallyImpaired said:
I got a brand new BELL SGS2HDLTE yesterday model SGH757 and flashed CWM, everything was ok. This morning I decided I wanted to flash a samsung based ICS rom specifically this on here (http://forum.xda-developers.com/showthread.php?t=1569686). I booted into CWM Recovery, wipe/factory reset wiped cache and dalvik cache and installed the ROM. The setup show up and eventually said complete please reboot. I pressed reboot and the phone turned off and refuses to turn on anymore. The battery was at 44% when I was flashing, even if I plug the phone in via usb nothing happens. I've tried taking out the battery for a few second and putting it back in but nothing happens. I can't boot into CWM or DL mode either, its as if the phone is completely dead... Can someone tell me whats going on here??? I never had an issue like this on my old SGS.. Thanks in advance!
Click to expand...
Click to collapse
I'm sorry bro but you might have suffered from the infamous super brick bug and your inability to read.
Solution:
Package the phone and send it to Samsung repair center
Swyped from Samsung Galaxy SII
TechnicallyImpaired said:
I got a brand new BELL SGS2HDLTE yesterday model SGH757 and flashed CWM, everything was ok. This morning I decided I wanted to flash a samsung based ICS rom specifically this on here (http://forum.xda-developers.com/showthread.php?t=1569686). I booted into CWM Recovery, wipe/factory reset wiped cache and dalvik cache and installed the ROM. The setup show up and eventually said complete please reboot. I pressed reboot and the phone turned off and refuses to turn on anymore. The battery was at 44% when I was flashing, even if I plug the phone in via usb nothing happens. I've tried taking out the battery for a few second and putting it back in but nothing happens. I can't boot into CWM or DL mode either, its as if the phone is completely dead... Can someone tell me whats going on here??? I never had an issue like this on my old SGS.. Thanks in advance!
Click to expand...
Click to collapse
No offense to the two responders above me, but you can ignore them.
The problem is that you attempted to flash a firmware not meant for your phone.
You yourself said you have an SGH-I757. Well, that ICS ROM you linked that you tried to flash is for the GT-i9100. The two models have different hardware, so firmwares, kernels, and ROMs are NOT compatible between them.
This probably screwed up the bootloader. Your only course of action at this point will probably be either JTag repair, or sending it to Samsung for repair.
ctomgee said:
No offense to the two responders above me, but you can ignore them.
The problem is that you attempted to flash a firmware not meant for your phone.
You yourself said you have an SGH-I757. Well, that ICS ROM you linked that you tried to flash is for the GT-i9100. The two models have different hardware, so firmwares, kernels, and ROMs are NOT compatible between them.
This probably screwed up the bootloader. Your only course of action at this point will probably be either JTag repair, or sending it to Samsung for repair.
Click to expand...
Click to collapse
Thanks for not being a douche bag in your response, much appreciated. Thanks for the info BTW, I just got myself a new one and I'll be more careful now. My biggest annoyance with native ICS on this phone is one is looks like gingerbread and two it comes with a tonne of bloatware that you can't remove without rooting ect. At this point should I flash CWM again since it installed successfully last time, root, and use that as a method to remove the unwanted bloatware. I'm so hesitant to flash this phone now, it seems it was much ease on my SGS1.
TechnicallyImpaired said:
Thanks for not being a douche bag in your response, much appreciated. Thanks for the info BTW, I just got myself a new one and I'll be more careful now. My biggest annoyance with native ICS on this phone is one is looks like gingerbread and two it comes with a tonne of bloatware that you can't remove without rooting ect. At this point should I flash CWM again since it installed successfully last time, root, and use that as a method to remove the unwanted bloatware. I'm so hesitant to flash this phone now, it seems it was much ease on my SGS1.
Click to expand...
Click to collapse
Just make sure you stick to flashing things meant for your model. Those things compatible with your device will be clearly labeled with the model number.
Problem is the SGH-i757 doesn't have its own forum, so stuff for it gets posted in here.
ctomgee said:
Just make sure you stick to flashing things meant for your model. Those things compatible with your device will be clearly labeled with the model number.
Problem is the SGH-i757 doesn't have its own forum, so stuff for it gets posted in here.
Click to expand...
Click to collapse
Yup, I've found a few but I also have a few questions maybe you can help me with. According to this thread ( http://forum.xda-developers.com/showthread.php?t=1756242) only stock ICS v 4.0.4 is effected by this superbrick. The SGS2 I hardbricked earlier today was updated to this version via keys to 4.0.4 before installing the custom ROM. So provided I stick to ROMS such as lets say the one here (http://forum.xda-developers.com/showthread.php?t=1740188) and avoid upgrading to 4.0.4 I should be able to CWM + Flash + Root correct? I should also be able to do the standard factory reset / wipe cache / wipe dalvik? I also used the eMMC Brickbug Check app in the first post I liked under how to AVOID the superbrick and it came up saying my chip was sane. Thanks in advance and also I pressed the thank you button
TechnicallyImpaired said:
Yup, I've found a few but I also have a few questions maybe you can help me with. According to this thread ( http://forum.xda-developers.com/showthread.php?t=1756242) only stock ICS v 4.0.4 is effected by this superbrick. The SGS2 I hardbricked earlier today was updated to this version via keys to 4.0.4 before installing the custom ROM. So provided I stick to ROMS such as lets say the one here (http://forum.xda-developers.com/showthread.php?t=1740188) and avoid upgrading to 4.0.4 I should be able to CWM + Flash + Root correct? I should also be able to do the standard factory reset / wipe cache / wipe dalvik? I also used the eMMC Brickbug Check app in the first post I liked under how to AVOID the superbrick and it came up saying my chip was sane. Thanks in advance and also I pressed the thank you button
Click to expand...
Click to collapse
The brick bug may not affect you at all. The most common Galaxy S2 affected is the i9100, which we have established is NOT your device. And you already used the app that said your chip is "sane", so it's confirmed you don't have to worry about it.
Again, you bricked the device by flashing a ROM meant for a different device. Had nothing to do with the brick bug.
ctomgee said:
The brick bug may not affect you at all. The most common Galaxy S2 affected is the i9100, which we have established is NOT your device. And you already used the app that said your chip is "sane", so it's confirmed you don't have to worry about it.
Again, you bricked the device by flashing a ROM meant for a different device. Had nothing to do with the brick bug.
Click to expand...
Click to collapse
Thanks, I wasn't aware flashing a rom not meant for your device can cause a hard brick to the point where you cant turn anything on and no buttons are responsive ect. Thanks for the help.
Guys, I need your help!
My friend has a P769 (T-Mobile) and last wednesday we've unlocked the bootloader and installed the CWM and CM10.1, following a video tutorial that we found in this topic: http://forum.xda-developers.com/showthread.php?t=2277639 .
Everything worked perfectly, but according to my friend he tried to install a update from CM10.1 and now the device shows only the LG logo at booting. I've downloaded the ROM again (CM10.1 for P769), wiped all possible options on CWM (data/factory reset, cache and dalvik), installed the ROM many times and we still get stuck at LG logo.
I've searched here but it seems anyone was stupid enough as my friend was, haha =\. Can anyone help me with ideas?
Thank you in advance!
Wrong section that's why you don't get an answer and if you had used search in the same thread you saw the video you would have seen you answer is buried in there.
flash X and U from 20f and reset you should be fine if not watch the video and do a offline KDZ flash to stock and then try again.
Its advisable to take nandroid backup before doing any such work so that your phone cab be restored to default rom in such cases
Sent from my LG-P765 using xda app-developers app
1.) Terribly wrong section. Development is for developing SOFTWARE, not developing questions.
2.) Offline flash KDZ or flash the boots from 20f, as the other chap stated.
3.) Be more careful when tinkering (But not too careful, I "bricked" this thing probably 10-15 times )
I got my Optimus G a few days ago and since then decided to put a custom ROM on so I can get Android 4.3. I've tried two methods, rooting, unlocking, etc. with Stock and then flashing a different rom. As well, I've simply used LGNPST to put TeenyBin on before flashing a custom ROM.
I've tried with several ones, from CyanogenMod to SlimBean to Carbon and a few others. For the majority of them, it boots up correctly after being flashed, but the first time I reboot the phone after this it will never start up. It just freezes at the "Google" screen, or for some ROMs it shows this briefly then turns black. Either way, it never successfully boots up once it's been restarted a single time.
I've tried all the options in the Recovery mode, formatting, wiping, clearing cache/Dalvik cache, etc. But no matter what it still doesn't make it past boot.
I can successfully put back Stock on it with LGNPST, but I want to get 4.3 and I can't find a solution that will continue to work after the phone reboots. Any idea how to solve this?
dabomb18359 said:
I got my Optimus G a few days ago and since then decided to put a custom ROM on so I can get Android 4.3. I've tried two methods, rooting, unlocking, etc. with Stock and then flashing a different rom. As well, I've simply used LGNPST to put TeenyBin on before flashing a custom ROM.
I've tried with several ones, from CyanogenMod to SlimBean to Carbon and a few others. For the majority of them, it boots up correctly after being flashed, but the first time I reboot the phone after this it will never start up. It just freezes at the "Google" screen, or for some ROMs it shows this briefly then turns black. Either way, it never successfully boots up once it's been restarted a single time.
I've tried all the options in the Recovery mode, formatting, wiping, clearing cache/Dalvik cache, etc. But no matter what it still doesn't make it past boot.
I can successfully put back Stock on it with LGNPST, but I want to get 4.3 and I can't find a solution that will continue to work after the phone reboots. Any idea how to solve this?
Click to expand...
Click to collapse
I Had Exactly The Same Problem,I Wiped Internal Storage(I Had Took A Backup First)
Then Flashed Stock 20j Via LGNPST
Then Rooted It And Downloaded FreeGee App And Unlocked Bootloader And Installed Recovery.
And Now I Don't Have That Issue.
Regards,
acervenky,
XPT
acervenky said:
I Had Exactly The Same Problem,I Wiped Internal Storage(I Had Took A Backup First)
Then Flashed Stock 20j Via LGNPST
Then Rooted It And Downloaded FreeGee App And Unlocked Bootloader And Installed Recovery.
And Now I Don't Have That Issue.
Regards,
acervenky,
XPT
Click to expand...
Click to collapse
Thanks for the reply acervenky. I did what you said and got it rooted successfully, but then when I unlocked the Bootloader using FreeGee0.5 it said it worked successfully. However, when I tried rebooting it got stuck on the LG logo and I had no luck getting into the bootloader screen.
Edit: In the past, I followed different guides that would supposedly unlock your phone using the FreeGee app from the Play store, but those didn't work either when I tried them. Generally they would say successful, but even then most of the time it wouldn't work afterwards.
Okay somehow I got it working!
I'm not sure what steps along the way fixed it, but essentially I re-flashed a few times, either 20j stock or TeenyBin [Alt]. Eventually, wiping, formatting, etc. and installing my custom ROM SlimBean worked. The difference was that this time it works now when I reboot, so I don't have a gimp form of 4.3.
Thank you again acervenky, I'm not sure how but installing 20j seems to have done the trick. On the plus side, when I continued to reflash 20j it would always keep my data, allowing me to mess around without having to worry about losing all my settings.
dabomb18359 said:
Okay somehow I got it working!
I'm not sure what steps along the way fixed it, but essentially I re-flashed a few times, either 20j stock or TeenyBin [Alt]. Eventually, wiping, formatting, etc. and installing my custom ROM SlimBean worked. The difference was that this time it works now when I reboot, so I don't have a gimp form of 4.3.
Thank you again acervenky, I'm not sure how but installing 20j seems to have done the trick. On the plus side, when I continued to reflash 20j it would always keep my data, allowing me to mess around without having to worry about losing all my settings.
Click to expand...
Click to collapse
Glad That It Helped,Just Press The Thanks Button Instead Of Replying.
It Means A Lot :highfive:
Regards,
acervenky,
XPT
(I had included all links to the zips and files I used but XDA wouldn't let me include those due to this being my first post.)
I need help. I messed up pretty bad. I have a Galaxy S3 T999N on Metro Pcs. A buddy got me into root about a year ago. It's been slow for me, because I'm scared of bricking my device. (I've read many guides, forum posts and watched many videos but I've never had the courage to flash a custom ROM, even though it looks really fun.)
SPECS
Galaxy S3 T999N 4.2.1 on Metro Pcs
The phone was rooted with Odin 3.07.
Later I used Odin 3.09 to flash custom recovery for TWRP. (Zip: openrecovery-twrp-2.3.1.1-d2mtr)
A couple days ago, I finally got enough courage to flash a custom rom. I Used titanium to back up all my apps, then used twrp to make a restore.
I used TWRP on the nightly I found (cm-11-20140217-NIGHTLY-d2mtr.zip). It failed. I apologize for not doing a log dump... I can't remember exactly what the log said. Something like (ERROR 7 or STATUS 7)
I wiped the cache and dalvik cache and used the recovery I made before the attempt at cyanogen, then I wiped the cache and dalvik cache again. TWRP said it was a successful recovery. When I went to reboot into the stock OS... It just hangs at the "Metro PCS Wireless for all" intro screen.
I started to do research on that symptom. found all kinds of threads on boot loops.
I tried leaving the battery out for 30 seconds, then booting into twrp to wipe the cache several times.
Then I tried the same steps with the dalvik included.
Then I repeated that same process with a factory reset. (several times.) Always the same result.
I even tried that entire process with wiping the entire phone, DATA, cache, dalvik, system, then doing recovery again. Doesn't work.
My recovery isn't working. I don't know what to do. (ALSO, INTERESTING SYMPTOM: I've noticed after doing the recovery, during the boot, the part when the black with white font Galaxy splash screen plays, the sound that it makes when the blue galaxy animation forms... it sounds like that sound starts late and gets cut off, then it sticks at the "Metro PCS Wireless for all" intro screen. It only does this after a factory reset, it doesn't make any sound at all otherwise because I think my phone's sound was turned off when I made the restore.)
I had a tech buddy try to find my stock rom, he wasn't sure which one to use. (confusion between Metro pcs and T-mobile S3s discussed below.) He told me to try another custom rom. If I could get one to work, that means the phone is still good and the custom rom would give me time to possibly find the stock rom for my model. (I just paid my bill, I'm wasting service right now.)
First I tried to find a stock rom for my phone. If I used "metro pcs" as a part of the google search, it came back with mostly results pertaining to Samsung Galaxy S III SCH-R530M (I've owned the SCH-R530M... it was white and the first model variant that Metro PCS had. I think it was only 4G not 4GLTE) All I could find for the T999N is a T-Mobile stock 4.1 but my device is 4.2. and on metro PCS. I was told that when the device updated to 4.2, partitioning and other things changed on the device specific to a 4.2 setup. So if I tried to use a 4.1 stock rom I could brick my device. (In the reading I've done, I've never came across anything that said that on the internet.)
So I moved on and started looking for another custom rom. I had seen a lot of videos on pacman. Looks awesome. After doing some reading, I found pacman on the android forums. (pac_d2mtr-20130510-v22.1.1)
IT WORKED! I was super excited. I got this X-mas-ish feeling in my stomach, like I just opened an awesome gift.
The Wifi Worked, but the camera, DATA and calls did not work. I was still super excited! First I explored Pacman, and ended up in the about phone section. (Model number was SCH-R530M! This probably isn't going to function the way I'd like, I thought to my self.)
The more I played with pac's interface, the more it kept freezing. Had to do a bunch of battery pulls.
On the same thread mentioned above, There was some talk about MMS problems, someone suggested flashing this for 4g and MMS fixes. (AOKP TO METRO FIX.zip) using TWRP, It flashed successfully but didn't fix my calls or DATA.
BY THIS TIME, IT WAS LATE, HAD BEEN READING FOR HOURS AND I WAS FEELING TIRED AND REALLY BUMMED.)
Then I tried to look for my models modem files to flash. (I'll be honest, I'm new to this, I had no idea where to look.) eventually I found a modem repostiory on a thread(Can't find the site in my history, but I found the link) I found this: USC_T999N_GalaxyS3_UVBNC1_Modem. I flashed that, it didn't work either.
At that point, I think I flashed AOKP TO METRO FIX.zip and USC_T999N_GalaxyS3_UVBNC1_Modem.zip out of panic and frustration of not having a phone. Could I have messed up my radios? is it possible that even if I ever get back into my stock, could the radios be messed up now cause I flashed AOKP TO METRO FIX.zip and USC_T999N_GalaxyS3_UVBNC1_Modem.zip?
I'm scared... and burned out. I really need a phone and don't have money for an insurance deductible or a new phone. (I know... what a stupid noob, right?)
I hate my current job and have been on the hunt for about three months, which paid off with a couple interviews. I'm waiting for 2nd interviews to be scheduled. How will they or anyone else interested in
hiring me, reach me?
A lot of the threads I've read, people report that their device can't boot into recovery or boot into download mode. MINE CAN STILL DO BOTH.
I'm not sure what to do. I appreciate anyone who took the time to read all of this.
TO SUM IT ALL UP, I WAS WONDERING:
1. Is there another method how to fix the boot loop problem?
2. I also heard that T-Mobile and Metro PCS merged, which is why I have a T-Mobile model. Would it matter if I used the T Mobile Stock (or custom rom.) When technically I'm on Metro PCS?
2a. Would that effect my ability to make calls?
3. Also, is it true that using a 4.1 stock rom after having taking the 4.2 update, will that brick my Phone?
3a. Is there a place that offers 4.2 stock roms? I could only find 4.1 (not sure where to look.)
3b. My wife has the exact same phone, same model, rooted, only hers is 4.1 and mine is 4.2 - Could there be a method or some useful way to use the firmware from the wife's phone?
4. Is it possible that if I ever get back into my stock, could the radios be
messed up now cause I flashed AOKP TO METRO FIX.zip and USC_T999N_GalaxyS3_UVBNC1_Modem.zip while messing with pacman?
5. My phone can still go into download mode and it still boots into recovery. Is there any hope that I can save this? What else do I need to consider? Is all my network settings stuck on the recovery?
THANK YOU FOR YOUR TIME.