Related
So I have the Razr M Retail, and I was rooted with Safestrap and running Hashcode0f's CM10, completely stable. Yesterday I decided to move to TWRP with the bootloader unlock, so I backed up my ROM to an external SD, and also separately used TiBu to backup my apps, and then used mattlgroff's Razr M Utility to unlock the BL and flash TWRP, which all went fine. Then I wiped internal storage and restored my backup from TWRP. It restored and booted fine, but the Wi-Fi and camera didn't work. The Wi-Fi is stuck to a toggled off position in the settings, and it's greyed out so I can't change it. If I click to see networks, it gets stuck in "Turning Wi-Fi on..." and I never see anything. The camera force closes with "Can't connect to camera." Since I hadn't been sure from the start that a restore would work, I was expecting trouble at this point, so I flashed a fresh version of CM10 from Hashcode's goo.im with the intention of restoring my apps with TiBu. It booted, but it seemed like it was running slow and the Wi-Fi didn't work, with the same issue as before. I didn't try the camera. I messed around with a few things trying to get it to work, and although nothing worked, I tried doing all of these separately and then reflashing:
a) Flash stock Moto 4.1.2 with the utility
b) Restore my stock rooted Moto 4.1.1 with safestrap (Just sayin, this gets weird, I end up with both TWRP and Safestrap)
c) Restore to b) and then restore my CM10 backup as a Safestrap ROM-slot 1
d) Dial *#*#526#*#* to reset Wi-Fi driver (did nothing afaik)
ALSO, I charged the phone last night and this morning at 8:30 it was at 100% battery. 3 hours later, with wi-fi, data, and GPS all off, and using the phone very very lightly, it was at 46%, so there is significant battery drain coming from somewhere.
Any help or suggestions would be greatly appreciated.
First off, you need to fastboot back to stock and start over. TWRP didn't break your phone, restoring a backup from SS did. If you flash a fresh CM10 build, not a backup, you should be okay and you should only get the bugs that are associated with CM10.
Ok, now you're going to ask why the backup didn't work. SS is designed to work on top of the stock boot.img, but CM10 has its own boot.img and that's the reason that CM10 builds were so buggy when used with SS. When you saved CM10 with SS, it probably saved the stock boot.img with it and the stock boot.img is not going to make CM10 happy. If you had saved a stock based ROM and tried to restore it, you probably would have been okay.
Now, with all that being said, if you fastboot back to 4.1.2, then you'll need to use a 4.1.2 based ROM or a CM build. If you want to use a 4.1.1 based ROM, you'll need to flash the 4.1.1 boot.img, prior to flashing the ROM. You battery is probably dying so quickly because CM10 is trying to fight with the stock kernel. You need to fastboot and flash clean.
Tmfle from
Thanks for the info, but it didn't work
I used the utility to fastboot flash stock Recovery and System, then root with Motochopper, and flash TWRP. I then used TWRP to wipe system and flash a fresh version of CM10, and when it booted there was noticeable graphics lag, and Wi-Fi and Camera didn't work.
I'll flash back to stock for tonight, hope you have another idea =\
VoraciousGhost said:
Thanks for the info, but it didn't work
I used the utility to fastboot flash stock Recovery and System, then root with Motochopper, and flash TWRP. I then used TWRP to wipe system and flash a fresh version of CM10, and when it booted there was noticeable graphics lag, and Wi-Fi and Camera didn't work.
I'll flash back to stock for tonight, hope you have another idea =\
Click to expand...
Click to collapse
Yeah, stop using CM builds. The camera and WiFi are known issues on those builds. What I told you solved the issue with your backed up CM build. This is the reason I don't use CM, they are all buggy right now. There was new one released with a different camera. See how that works for you.
What were your steps for install?
-Boot into recovery
-Wipe cache/dalvik, FDR
-Reboot recovery
-Mount system
-Flash ROM
-Wipe cache/dalvik
-Reboot system
FYI, I never wipe system, only cache/dalvik and FDR. Some people swear by wiping system, I don't do it.
RikRong said:
Yeah, stop using CM builds. The camera and WiFi are known issues on those builds. What I told you solved the issue with your backed up CM build. This is the reason I don't use CM, they are all buggy right now. There was new one released with a different camera. See how that works for you.
What were your steps for install?
-Boot into recovery
-Wipe cache/dalvik, FDR
-Reboot recovery
-Mount system
-Flash ROM
-Wipe cache/dalvik
-Reboot system
FYI, I never wipe system, only cache/dalvik and FDR. Some people swear by wiping system, I don't do it.
Click to expand...
Click to collapse
Hmm, I think I figured it out, or at least part of it, I'll make sure in the morning. Back in December-ish, before the bootloader unlock, Hashcode was releasing new CM10 builds every few days. Only the latest, dated 12/05, had working Wi-Fi, and that's what my backup should be. Now that I look at goo.im again, the only build on there is dated 11/14, and that's the one that I thought was 'fresh' but it never had working Wi-Fi or camera to begin with. Now I read through the CM10 thread here on XDA and I see that mic213 is building more current CM10 releases with more features working, and Hashcode has removed all of his builds except one (no idea why it's this particular one instead of the latest).
As for my install steps, they were actually:
-Boot into recovery
-Format Data (I said wipe system earlier, but I meant format data, as system gets wiped as part of it)
-I didn't reboot recovery, usually do but I got lazy
-Flash ROM (system was already mounted for me? )
-Wipe caches
-Reboot
So yeah, in the morning I'll download and flash mic213's build from here and I'm pretty sure that should work.
VoraciousGhost said:
Hmm, I think I figured it out, or at least part of it, I'll make sure in the morning. Back in December-ish, before the bootloader unlock, Hashcode was releasing new CM10 builds every few days. Only the latest, dated 12/05, had working Wi-Fi, and that's what my backup should be. Now that I look at goo.im again, the only build on there is dated 11/14, and that's the one that I thought was 'fresh' but it never had working Wi-Fi or camera to begin with. Now I read through the CM10 thread here on XDA and I see that mic213 is building more current CM10 releases with more features working, and Hashcode has removed all of his builds except one (no idea why it's this particular one instead of the latest).
As for my install steps, they were actually:
-Boot into recovery
-Format Data (I said wipe system earlier, but I meant format data, as system gets wiped as part of it)
-I didn't reboot recovery, usually do but I got lazy
-Flash ROM (system was already mounted for me? )
-Wipe caches
-Reboot
So yeah, in the morning I'll download and flash mic213's build from here and I'm pretty sure that should work.
Click to expand...
Click to collapse
Yeah, definitely use Mic's builds, they are more current. TWRP shows that the sytem is mounted, but it is fact not. That's why you need to reboot recovery. When you reboot, you'll see that it's not mounted.
Mic's CM10 is very, very stable. Very good build.
10.1 is a little more buggy but still a good build.
Sounds like you're either using one of Hash's old builds or new, buggy ones. Mic is the way to go for now
Sent from my Nexus 7 using Tapatalk HD
I bought this phone used and the person who had it before me it rooted and installed some of different ROMs on it. After getting my used moto x pure 2015 running android 6.0. I booted it up and tested all the functions (including downloading a few apps) Wi-Fi, camera, audio/charging jacks ext. Everything worked fine. So did normal factory reset (not using TWRP) just to make sure everything was clean before using it as my daily. Then, (BUM BUM BUM!) when I tried to start downloading all my apps. None of them would download even though the Wi-Fi was working. Error 492 I think.
I started trying custom ROMs because I was having two big issues (apps not downloading and incoming call not bringing up accept/decline screen) with my stock rom. and wanted to fix those issues with a fresh stock image.
This is all new to me and has not been as easy as anticipated. If anyone knows a clean factory image I could flash or a fail proof fix to error 492 that would be helpful. I really just want to return to fully working Motorola stock android, but the files I have used haven’t fixed the issue. I have searched for a factory image without finding one…
Is there a way to flash the Motorola image through TRWP?
Otherwise, maybe you can help me with my flashing method, and maybe tell me what I am doing wrong. I tried to flash multiple stock images all with the same issue. I have also tried to flash Resurrection Remix, and Brocken OS, both having resulted in a bootloop. I am starting to think I have done something wrong. The steps I have taken so far have been these:
My bootloader is unlocked status code 3.
My phone is not rooted. Do I need root?
First I downloaded adb and fastboot.
Then I flashed TWRP (3.0.2).
I never installed the official Motorola stock image because flashing it from fast boot wouldn’t work and it couldn’t be flashed with TWRP because it is a .gz not a .zip. (I knew a .gz needs to be flashed with fastboot but I knew TWRP was easer so I didn’t fuss with it)
After flashing TWRP to my phone, I downloaded (yes, I checked the md5) the various ROMs to my computer then transfered them to my phone via micro SD card.
Here are the file’s names if that matters:
moto_x_pure_edition_stock_x1575_mphs24.49-18-3_v1-odexed
(booted and Wi-Fi but play store won’t download apps)
moto_x_pure_edition_stock_x1575_mph24.49-18_v1-odexed
(booted but no Wi-Fi)
Broken-v4.9.1-clark-6.0.1-OFFICIAL-20160824 (with Broken_gapps_lp5.1.x_09172015)
(Brocken was the only non-stock that got past boot, but I still couldn’t get past set up without an error and never made it to the system.)
ResurrectionRemix-N-v5.8.0-20161220-clark (7.1 gapps failed to flash but I booted it anyway.)
(boot loop after both of my tries)
I got Wi-Fi working on one of the above stock ROMs (so I KNOW it works) but couldn’t even turn Wi-Fi on in all the others.
The method I used to flash all of the above files in TWRP was:
Wipe
Full wipe (davlik cache, data, system, cache)
(used for RR and Brocken)
Factory reset (using TWRP) (davlik cache, data , cache)
Used for the stock ROMs or even after flashing .zip file I got the error: no OS installed.
Install
Select file of ROM flash (gapps if needed) and flash
I can’t remember which ones but on some of them after flashing I again did a factory reset.
Then I rebooted
Thanks for reading. Sorry it was so long. I tried to add as much useful information as possible. Hopefully someone smarter than me will see my error(s) and help me get my phone into fully working order.
cont.
I really just want to return to fully working Motorola stock android, but the files I have used haven’t fixed the issue. I have searched for a factory image without finding one…
Is there a way to flash the Motorola image through TRWP?
Otherwise maybe you can help me out with my flashing method and maybe tell me what I am doing wrong. I tried to flash multiple stock images all with the same issue. I have also tried to flash Resurrection Remix, and Brocken OS, both having resulted in a bootloop. I am starting to think I have done something wrong. The steps I have taken so far have been these:
My bootloader is unlocked status code 3.
My phone is not rooted. Do I need root?
First I downloaded adb and fastboot.
Then I flashed TWRP (3.0.2).
I never installed the official Motorola stock image because flashing it from fast boot wouldn’t work and it couldn’t be flashed with TWRP because it is a .gz not a .zip. (I knew a .gz needs to be flashed with fastboot but I knew TWRP was easer so I didn’t fuss with it)
After flashing TWRP to my phone, I downloaded (yes, I checked the md5) the various ROMs to my computer then transfered them to my phone via micro SD card.
Here are the file’s names if that matters:
moto_x_pure_edition_stock_x1575_mphs24.49-18-3_v1-odexed
(booted and Wi-Fi but play store won’t download apps)
moto_x_pure_edition_stock_x1575_mph24.49-18_v1-odexed
(booted but no Wi-Fi)
Broken-v4.9.1-clark-6.0.1-OFFICIAL-20160824 (with Broken_gapps_lp5.1.x_09172015)
(Brocken was the only non-stock that got past boot, but I still couldn’t get past set up without an error and never made it to the system.)
ResurrectionRemix-N-v5.8.0-20161220-clark (7.1 gapps failed to flash but I booted it anyway.)
(boot loop after both of my tries)
I got Wi-Fi working on one of the above stock ROMs (so I KNOW it works) but couldn’t even turn Wi-Fi on in all the others.
The method I used to flash all of the above files in TWRP was:
Wipe
Full wipe (davlik cache, data, system, cache)
(used for RR and Brocken)
Factory reset (using TWRP) (davlik cache, data , cache)
Used for the stock ROMs or even after flashing .zip file I got the error: no OS installed.
Install
Select file of ROM flash (gapps if needed) and flash
I can’t remember which ones but on some of them after flashing I again did a factory reset.
Then I rebooted
Thanks for reading. Sorry it was so long. I tried to add as much useful information as possible. Hopefully someone smarter than me will see my error(s) and help me get my phone into fully working order.
I think this thread will help you: https://forum.xda-developers.com/showthread.php?t=3489110
Sent from my XT1572 using Tapatalk
Install stock firmware via fastboot... if that dont fix the issue, install TWRP make a full wipe, FULL, and install the stock firmware again, eventualy that sould fix the issue.
RK2116 said:
Install stock firmware via fastboot... if that dont fix the issue, install TWRP make a full wipe, FULL, and install the stock firmware again, eventualy that sould fix the issue.
Click to expand...
Click to collapse
I'm having a similar issue. Tried the TruPure rom but I want to switch back to stock. If I do a full wipe, would I be able to use the files that Motorola provides on their website and flash those throught fastboot? Or through TWRP? Any chance you have a link to a guide on how to do the latter option (installing through TWRP)? I'm just trying to get my device back to 100% stock so that I can receive OTA.
cdiaz8 said:
I'm having a similar issue. Tried the TruPure rom but I want to switch back to stock. If I do a full wipe, would I be able to use the files that Motorola provides on their website and flash those throught fastboot? Or through TWRP? Any chance you have a link to a guide on how to do the latter option (installing through TWRP)? I'm just trying to get my device back to 100% stock so that I can receive OTA.
Click to expand...
Click to collapse
Odexed one, install with TWRP, full wipe before doing that, no GApps, just ROM, them, install stock recovery vía fastboot. After that you Will be stock with OTAs.
https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120
RK2116 said:
Odexed one, install with TWRP, full wipe before doing that, no GApps, just ROM, them, install stock recovery vía fastboot. After that you Will be stock with OTAs.
https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120
Click to expand...
Click to collapse
Thank you for sharing that link. I think I get it but it seems too easy considering what I've tried so far. Just to make sure I get it:
I should download the odexed rom, go to twrp and wipe data, cache and dalvik then flash the odexed rom through the install function? And thats it? I've literally tried a ton of stuff so if this takes care of it, this is great!
cdiaz8 said:
Thank you for sharing that link. I think I get it but it seems too easy considering what I've tried so far. Just to make sure I get it:
I should download the odexed rom, go to twrp and wipe data, cache and dalvik then flash the odexed rom through the install function? And thats it? I've literally tried a ton of stuff so if this takes care of it, this is great!
Click to expand...
Click to collapse
Yes, also wipe system, make a backup before If you want, but remember, for the OTAs support you need yo flash the stock recovery via fastboot. Good luck.
RK2116 said:
Yes, also wipe system, make a backup before If you want, but remember, for the OTAs support you need yo flash the stock recovery via fastboot. Good luck.
Click to expand...
Click to collapse
This got me back to stock! You are the real MVP.
So I remember seeing a recovery.img file in the factory image that motorola posted on its site. Does it have to be a specific stock recovery or do I need a specific one to match with the file I just installed?
thanks again
cdiaz8 said:
This got me back to stock! You are the real MVP.
So I remember seeing a recovery.img file in the factory image that motorola posted on its site. Does it have to be a specific stock recovery or do I need a specific one to match with the file I just installed?
thanks again
Click to expand...
Click to collapse
Just a stock one, if Motorola have one use that.
RK2116 said:
Just a stock one, if Motorola have one use that.
Click to expand...
Click to collapse
So I'm on stock build 49-18-8 and flashed the recovery from 49-18-3. I went into fastboot and selected recovery. I got the android character with an !
I then did the power button and volume up and got into stock android recovery. Am I supposed to see the android character with ! each time I try to reach the recovery menu? Just wondering if I did this correctly.
Thanks again for pointing me to these resources!
cdiaz8 said:
So I'm on stock build 49-18-8 and flashed the recovery from 49-18-3. I went into fastboot and selected recovery. I got the android character with an !
I then did the power button and volume up and got into stock android recovery. Am I supposed to see the android character with ! each time I try to reach the recovery menu? Just wondering if I did this correctly.
Thanks again for pointing me to these resources!
Click to expand...
Click to collapse
Yes.
I'm having a very difficult time getting this phone setup. I can get very, very close... but then it starts boot looping into recovery.
So starting at the beginning, here is what I did:
- Booted up phone, make sure it works and connects to wifi (I find out later that it got encrypted, even though I didn't set a PIN).
- Inside the OS on first boot, I install and use the official bootloader unlock APK from Asus.
- Rebooted into the bootloader and fastboot flashed TWRP.
- Rebooted into TWRP and flashed the Oreo modem, current unofficial Carbon OS 6.1, nano gapps, and magisk 16.6.
- Rebooted and the Carbon ROM logo comes up. It works for about 2-3 minutes, then reboots.
- After many attempts to decrypt (and a lot of help from the forum), I successfully restore the phone to "WW_ZE552KL_14.2020.1712.85_M3.10.47.15_Phone-user.raw.zip" with the Asus tool.
- Phone is fixed and booting again to the OS, but I'm back to square one.
Second attempt:
- Thinking I need to flash the raw Oreo ROM (instead of just the Oreo modem), I use the Asus tool to flash "WW_ZE552KL_15.0410.1803.55_M3.10.47.19_Phone-user.raw.zip"
- The phone works fine and is now an Oreo ROM with an Oreo modem
- It's still unlocked, so I rebooted into the bootloader and fastboot flashed TWRP.
- Rebooted into TWRP and flashed the current unofficial Carbon OS 6.1, nano gapps, and magisk 16.6.
- Rebooted and the Carbon ROM logo comes up. It works for about 2-3 minutes, then reboots.
- After the reboot, it goes to TWRP... whether I just let it boot on its own, or press power when it says: Start - Continue to boot >
What am I doing wrong?
You're having a rough go at this one eh.
I know we talked about this before, but did you try a factory reset and wiping cache/dalvik before rebooting?
Yes. As we discussed before, you can't wipe cache from TWRP. So I'd wipe dalvik from TWRP, then reboot to the bootloader to do a "fastboot format cache".
I'm going to try a different ROM later this afternoon. Maybe that will make a difference.
Flapjack said:
I'm going to try a different ROM later this afternoon. Maybe that will make a difference.
Click to expand...
Click to collapse
Hello! I've been able to boot any ROM by:
1. flashing TWRP
2. rebooting to recovery
3. installing the ROM zip
4. rebooting to bootloader
5. fastboot continue
But when I restart the phone, it always boots to recovery(TWRP), so I have to repeat steps 4 and 5 to boot the ROM, which is
Could you try and tell me if it works for you too?
I'm gonna take a moment to read about the boot process in depth, as it seems there is no straightforward solution to this out there.
junglesnake said:
Hello! I've been able to boot any ROM by:
1. flashing TWRP
2. rebooting to recovery
3. installing the ROM zip
4. rebooting to bootloader
5. fastboot continue
But when I restart the phone, it always boots to recovery(TWRP), so I have to repeat steps 4 and 5 to boot the ROM, which is
Could you try and tell me if it works for you too?
I'm gonna take a moment to read about the boot process in depth, as it seems there is no straightforward solution to this out there.
Click to expand...
Click to collapse
1) Flash Oreo RAW (can be downloaded from @Saktis_STi' s unlocking thread.
2) Boot till system
3) Flash TWRP
4) Flash ROM, Magisk, GApps
5) Reboot
The reason why it reboots to TWRP is because of 'encryption' thingy.
BootloaderBoi said:
1) Flash Oreo RAW (can be downloaded from @Saktis_STi' s unlocking thread.
2) Boot till system
3) Flash TWRP
4) Flash ROM, Magisk, GApps
5) Reboot
The reason why it reboots to TWRP is because of 'encryption' thingy.
Click to expand...
Click to collapse
many many thanks! I was able to get Ressurection Remix working by now
your steps were right, and I will detail them better to tell how I made it work for others reading this thread:
1) Flash Oreo RAW
1.1 - @Saktis_STi's thread is a bit outdated. I downloaded the newest firmware from Asus website.
1.2 - I also had to find a recent recovery.img, which I think I got it from here https://forum.xda-developers.com/zenfone-3/how-to/original-recovery-img-boot-img-zenfone-t3572188
1.3 - I used the stock recovery's adb sideload to flash the stock ROM
2) Flash TWRP - all good here
3) Flash ROM, Magisk, GApps
3.1 - I wiped system, data, cache and dalvik.
3.2 - I flashed RR ROM, GApps and Magisk (EDIT 2: install all three before the first custom ROM boot, or GApps won't work)
3.3 - Performed a Factory Reset
4) REBOOTED TO GLORY!
For what it seems, the stock ROM encryption that is performed on the stock's first boot was the enemy.
Now one last thing... In Security -> Encription, my device is NOT encrypted.
Do I run the risk of ruining everything if I encrypt it?
EDIT: No, it didn't break, working fine
junglesnake said:
1) Flash Oreo RAW
1.1 - @Saktis_STi's thread is a bit outdated. I downloaded the newest firmware from Asus website
Click to expand...
Click to collapse
lmao. His RAW firmware version is the latest version though
https://forum.xda-developers.com/zenfone-3/development/updated-unlock-relock-bootloader-t3749456
Anyways, enjoy your phone running on custom ROM :good:
Hey guys,
I recently flashed Omnirom and after doing so, noticed I had no signal. After flash, reboot, or resetting Network/Data settings, I'll have data for about 20-30 seconds. I can browse the web, but I can't send or receive calls or messages. Then it goes away completely. It sporadically returns, but drops again quickly.
Carrier is Verizon. My Sim card is still being read so the issue doesn't seem to be there. I've put it back in my Pixel 2 and it's working fine.
At a high level, this is what I've done over the past 12 hours:
1. My bootloader is unlocked. I flashed a new ROM and then it wouldn't boot.
2. I did a Factory reset through Recovery and then it booted into the ROM, where I noticed I had no signal
--Possibly an issue here? This factory reset wasn't done thru TWRP, but the stock(?) recovery. I noticed that after doing this, it wiped everything on my phone, including my Nandroid backups
3. I did another factory reset, still no service
4. I moved sim card from Sim Slot 2 to Sim slot 1, temporarily restored service. Then dropped.
5. I flashed OOS 9.0.12 back, service came back temporarily, then dropped
6. I did a network reset, restored service temporarily, then dropped
7. I reflashed modem, system, and vendor images
Anyone have any thoughts or suggestions? Otherwise, I'm probably going to send my phone back to OnePlus for repair.
Try restoring through the msm tool.
TheRemyx said:
Hey guys,
I recently flashed Omnirom and after doing so, noticed I had no signal. After flash, reboot, or resetting Network/Data settings, I'll have data for about 20-30 seconds. I can browse the web, but I can't send or receive calls or messages. Then it goes away completely. It sporadically returns, but drops again quickly.
Carrier is Verizon. My Sim card is still being read so the issue doesn't seem to be there. I've put it back in my Pixel 2 and it's working fine.
At a high level, this is what I've done over the past 12 hours:
1. My bootloader is unlocked. I flashed a new ROM and then it wouldn't boot.
2. I did a Factory reset through Recovery and then it booted into the ROM, where I noticed I had no signal
--Possibly an issue here? This factory reset wasn't done thru TWRP, but the stock(?) recovery. I noticed that after doing this, it wiped everything on my phone, including my Nandroid backups
3. I did another factory reset, still no service
4. I moved sim card from Sim Slot 2 to Sim slot 1, temporarily restored service. Then dropped.
5. I flashed OOS 9.0.12 back, service came back temporarily, then dropped
6. I did a network reset, restored service temporarily, then dropped
7. I reflashed modem, system, and vendor images
Anyone have any thoughts or suggestions? Otherwise, I'm probably going to send my phone back to OnePlus for repair.
Click to expand...
Click to collapse
Have you wiped the cache?
It's not a hardware issue.
rickysidhu_ said:
Try restoring through the msm tool.
Click to expand...
Click to collapse
I would also try the MSM tool to restore back to stock. Then reflash what you want for a ROM.
rickysidhu_ said:
Try restoring through the msm tool.
Click to expand...
Click to collapse
Scott said:
I would also try the MSM tool to restore back to stock. Then reflash what you want for a ROM.
Click to expand...
Click to collapse
Thanks guys. Using MSM worked.
For those who may have the same issue, I used MSM to go back to 9.0.11 since a few people said they had issues with 9.0.12 such as not being able to unlock it. I restored 9.0.11, unlocked my device, then flashed the 9.0.12 OTA. Issue stayed resolved.
I did try to flash Omnirom again and the issue came back, so I'm curious as to what's happening. I'm going to try another Rom.
Just an update, this seems to happen with any rom I flash now. I tried Omnirom, Pixel Experience, and Syberia OS. They boot up but with no 4g connection. When I use MSM to go back to 9.0.11 or 9.0.12 everything works properly. Not sure what I may be missing?
Out of curiosity, how are you installing your custom ROMs. I have installed quite a few custom ROMs in the last week or so and have not encountered any issues. I use a USB pendrive with an OTG adapter to install my stuff as the phone normally ends up in an encrypted state so the internal storage will not be accessible when booting into TWRP. Here are the steps I use when installing a custom ROM:
01. Boot into TWRP
02. Wipe, then swipe. You can choose to Format Data if you want, but this will erase your internal storage so you will lose your recent pictures and other media.
03. Install full OOS 9.0.11/9.0.12 depending on which version is required for the custom ROM and install TWRP also.
04. Reboot recovery.
05. Install full OOS 9.0.11/9.0.12 and TWRP again to ensure both slots have OOS install on it. Use the same version you installed in step 3.
06. Reboot recovery.
07. Install your custom ROM and TWRP.
08. Reboot recovery.
09. Wipe, then swipe (Do not format; unsure if this makes a difference).
10. Install GApps if needed (ROM dependent) and optionally install Magisk and a custom kernel.
11. Reboot system and then wait to setup the phone.
As stated, this has worked flawlessly for me and I have not run into any issues. Admittedly, I have not tried Omnirom directly, but I have tried Omnirom Treskmod (not available on XDA) and SkyDragon which are both based on Omnirom and did not have issues with either. I have tried maybe 10 different custom ROMs in the last week on so and have not had any problems. Still trying to find the best ROM for me. You could say that I'm a flashaholic.
I hope this helps.
Ooms
dj_ooms said:
Out of curiosity, how are you installing your custom ROMs. I have installed quite a few custom ROMs in the last week or so and have not encountered any issues. I use a USB pendrive with an OTG adapter to install my stuff as the phone normally ends up in an encrypted state so the internal storage will not be accessible when booting into TWRP. Here are the steps I use when installing a custom ROM:
01. Boot into TWRP
02. Wipe, then swipe. You can choose to Format Data if you want, but this will erase your internal storage so you will lose your recent pictures and other media.
03. Install full OOS 9.0.11/9.0.12 depending on which version is required for the custom ROM and install TWRP also.
04. Reboot recovery.
05. Install full OOS 9.0.11/9.0.12 and TWRP again to ensure both slots have OOS install on it. Use the same version you installed in step 3.
06. Reboot recovery.
07. Install your custom ROM and TWRP.
08. Reboot recovery.
09. Wipe, then swipe (Do not format; unsure if this makes a difference).
10. Install GApps if needed (ROM dependent) and optionally install Magisk and a custom kernel.
11. Reboot system and then wait to setup the phone.
As stated, this has worked flawlessly for me and I have not run into any issues. Admittedly, I have not tried Omnirom directly, but I have tried Omnirom Treskmod (not available on XDA) and SkyDragon which are both based on Omnirom and did not have issues with either. I have tried maybe 10 different custom ROMs in the last week on so and have not had any problems. Still trying to find the best ROM for me. You could say that I'm a flashaholic.
I hope this helps.
Ooms
Click to expand...
Click to collapse
Because I had erased all data on my phone, I was doing mostly everything from Fastboot or ADB Sideload in TWRP. So my previous steps were something like this:
1. Use MSM to restore OOS 9.0.11
2. Unlock Bootloader
3. Fastboot to TWRP 3.3.0.2
4. Install TWRP on both slots (ADB Sideload)
5. Reboot Recovery
6. Install 9.0.12 on both slots (ADB Sideload)
7. Install TWRP (ADB Sideload)
8. Reboot System to verify I have signal
9. Reboot Recovery
10. Install custom ROM and TWRP (ADB Sideload)
11. Format Data through TWRP
12. Reboot System (No signal)
I had also noticed that there was some system app or process that was repeatedly crashing, but I couldn't tell what it was because the popup notification would disappear so quickly.
TheRemyx said:
Because I had erased all data on my phone, I was doing mostly everything from Fastboot or ADB Sideload in TWRP. So my previous steps were something like this:
1. Use MSM to restore OOS 9.0.11
2. Unlock Bootloader
3. Fastboot to TWRP 3.3.0.2
4. Install TWRP on both slots (ADB Sideload)
5. Reboot Recovery
6. Install 9.0.12 on both slots (ADB Sideload)
7. Install TWRP (ADB Sideload)
8. Reboot System to verify I have signal
9. Reboot Recovery
10. Install custom ROM and TWRP (ADB Sideload)
11. Format Data through TWRP
12. Reboot System (No signal)
I had also noticed that there was some system app or process that was repeatedly crashing, but I couldn't tell what it was because the popup notification would disappear so quickly.
Click to expand...
Click to collapse
I didn't notice any popups when setting up my device. The only thing I can say is that VoLTE never used to work properly for me on OOS. I had to edit a setting in serial mode to get VoLTE working on my network in the UK. Not sure if it is related at all. I highly doubt it. I noticed in your steps, you have not flashed GApps. I believe most custom ROMs don't contain GApps, only a select few. Is there a reason you are not flashing GApps? I know there are individuals who want to stay away from Google and use Micro-G as an alternative. I believe the minimum is to flash Pico or Nano GApps. I am not sure if there is possibly something in GApps that is related to data and telephony. The notification popup you are getting may also be related to not having GApps. I install the Nano GApps so I can get face unlock working. Maybe try that and then try installing Magisk after if you still have the same issues. You are rebooting the system in your Step 12. Maybe try and reboot recovery first, then reboot system to keep TWRP intact. You could try the steps that I posted. I use a USB pendrive but if you Format Data to clear your internal storage, it should not be encrypted after unless you reboot into OOS beforehand. You should be able to push files directly to internal storage through ADB in TWRP or you can maybe mount the phone on the computer and copy the files across. These are only suggestions. I haven't had the issues you are having but the steps I listed seem to have worked consistently for my. As a note, I have never had to use the MSMTool to get my phone back up and running again. I have used fastboot mode before though.
I hope this helps.
Ooms
TheRemyx said:
Because I had erased all data on my phone, I was doing mostly everything from Fastboot or ADB Sideload in TWRP. So my previous steps were something like this:
1. Use MSM to restore OOS 9.0.11
2. Unlock Bootloader
3. Fastboot to TWRP 3.3.0.2
4. Install TWRP on both slots (ADB Sideload)
5. Reboot Recovery
6. Install 9.0.12 on both slots (ADB Sideload)
7. Install TWRP (ADB Sideload)
8. Reboot System to verify I have signal
9. Reboot Recovery
10. Install custom ROM and TWRP (ADB Sideload)
11. Format Data through TWRP
12. Reboot System (No signal)
I had also noticed that there was some system app or process that was repeatedly crashing, but I couldn't tell what it was because the popup notification would disappear so quickly.
Click to expand...
Click to collapse
Not sure if it helps, but you are doing too many repeated steps. Skip 4 & 5, Format Data before installing 9.0.12. Skip 11. Why are you installing TWRP so many times?
dj_ooms said:
I didn't notice any popups when setting up my device. The only thing I can say is that VoLTE never used to work properly for me on OOS. I had to edit a setting in serial mode to get VoLTE working on my network in the UK. Not sure if it is related at all. I highly doubt it. I noticed in your steps, you have not flashed GApps. I believe most custom ROMs don't contain GApps, only a select few. Is there a reason you are not flashing GApps? I know there are individuals who want to stay away from Google and use Micro-G as an alternative. I believe the minimum is to flash Pico or Nano GApps. I am not sure if there is possibly something in GApps that is related to data and telephony. The notification popup you are getting may also be related to not having GApps. I install the Nano GApps so I can get face unlock working. Maybe try that and then try installing Magisk after if you still have the same issues. You are rebooting the system in your Step 12. Maybe try and reboot recovery first, then reboot system to keep TWRP intact. You could try the steps that I posted. I use a USB pendrive but if you Format Data to clear your internal storage, it should not be encrypted after unless you reboot into OOS beforehand. You should be able to push files directly to internal storage through ADB in TWRP or you can maybe mount the phone on the computer and copy the files across. These are only suggestions. I haven't had the issues you are having but the steps I listed seem to have worked consistently for my. As a note, I have never had to use the MSMTool to get my phone back up and running again. I have used fastboot mode before though.
I hope this helps.
Ooms
Click to expand...
Click to collapse
I had tried flashing GAPPs (ARM64-Nano) and it didn't seem to make a difference. I was skipping that and flashing Magisk just to confirm if I had service first. But would service/signal be dependent on something in GAPPs? I may try your way. I hadn't run into any issues with encrypted storage lately. The last few times I was able to get around it by booting to system first, then rebooting back to recovery.
schmeggy929 said:
Not sure if it helps, but you are doing too many repeated steps. Skip 4 & 5, Format Data before installing 9.0.12. Skip 11. Why are you installing TWRP so many times?
Click to expand...
Click to collapse
I was installing TWRP because every time I restored or flashed, I was losing my custom recovery.
Hi,
I'm sure someone else will have had my problem but I can't seem to find a straight forward solution.
I am wanting to upgrade my Samsung S7 Edge, SM-G935F Exynos, to the latest Lineage OS with Android 10 as Samsung are no longer supporting my phone. The phone is unlocked as supplied from Samsung.
I downloaded Odin v3.14 and successfully flashed TWRP 3.4.0.0 hero.2lte.img.tar. I activated Developer Options and OEM unlock before flashing.
I can enter TWRP but am unsure what I do regarding the Unmodified System Partition options on the 1st TWRP screen so I hit 'Keep Read Only' and then 'Reboot' only to find that the phone attempts to restart, I see the Samsung Galaxy S7 Edge splash screen which then goes off and restarts again repeatedly, so I can't check if all my data etc. is ok on the phone. I did back up Whatsapp and made s Smart Switch backup too but forgot to do Samsung & Google account backups before the flashing.
I'm assuming I've missed something out in the flashing procedure but am not sure of exactly what. I have previously flashed and upgraded Galaxy S3, S3 Mini & a Tab2 10.1 using earlier TWRP versions so it's not that I'm a total beginner. I also tried to do a rom backup via TWRP but that failed and also a wipe Dalvik cache but that also failed.
Please advise:
1. what I've done wrong if anything?
2. Best way to restore the phone without losing existing data if possible perhaps with stock rom flashing? I could try the Smart Switch Emergency Software recovery & Initialisation but I understand that resets the phone to Factory settings loosing all data.
3. Procedure to flash Lineage rom that's 'idiot proofed'?
Thanks in advance.
rebgershon said:
Hi,
I'm sure someone else will have had my problem but I can't seem to find a straight forward solution.
I am wanting to upgrade my Samsung S7 Edge, SM-G935F Exynos, to the latest Lineage OS with Android 10 as Samsung are no longer supporting my phone. The phone is unlocked as supplied from Samsung.
I downloaded Odin v3.14 and successfully flashed TWRP 3.4.0.0 hero.2lte.img.tar. I activated Developer Options and OEM unlock before flashing.
I can enter TWRP but am unsure what I do regarding the Unmodified System Partition options on the 1st TWRP screen so I hit 'Keep Read Only' and then 'Reboot' only to find that the phone attempts to restart, I see the Samsung Galaxy S7 Edge splash screen which then goes off and restarts again repeatedly, so I can't check if all my data etc. is ok on the phone. I did back up Whatsapp and made s Smart Switch backup too but forgot to do Samsung & Google account backups before the flashing.
I'm assuming I've missed something out in the flashing procedure but am not sure of exactly what. I have previously flashed and upgraded Galaxy S3, S3 Mini & a Tab2 10.1 using earlier TWRP versions so it's not that I'm a total beginner. I also tried to do a rom backup via TWRP but that failed and also a wipe Dalvik cache but that also failed.
Please advise:
1. what I've done wrong if anything?
2. Best way to restore the phone without losing existing data if possible perhaps with stock rom flashing? I could try the Smart Switch Emergency Software recovery & Initialisation but I understand that resets the phone to Factory settings loosing all data.
3. Procedure to flash Lineage rom that's 'idiot proofed'?
Thanks in advance.
Click to expand...
Click to collapse
1] You didn't formatted /data and/or flashed magisk or supersu after booting into twrp first time.
Note that you need to format /data under wipe in twrp and type yes and then again reboot in twrp. This is necessary step to disable encryption. And after that flash magisk without any reboot or flash your required rom by following your respective rom thread.
Please note that keeping system read only will cause you to flash in systemless root mode like magisk or super su in systemless mode. There is no difference between normal root mode and systemless root mode except that you will need to allow system modifications in twrp in normal root which will in turn trigger dm verity check and you will need to flash no verity zip to make phone bootable when system modification method (normal root) is selected. Plus system modification will cause certain apps to detect root easily plus increasing complications like I said above. So just keep read only and flash magisk and you will get root in systemless mode without any cons !
Here, you said you're getting a verification screen after rebooting twrp..
This can be caused either by.
1. Not formatting /data after booting twrp for first time
2. Not flashing magisk after formatting /data
3. Enabling system modifications and not flashing no verity zips/magisk
4. Oem unlock is not enabled..
2] You cannot restore data if you didn't back it up before messing with it, or you made a titanium backup/twrp backup.
Smart switch cannot flash phone anymore ..
Yes, flashing stock firmware using home_csc in odin, will not delete data and may restore your phone, but no guarantee that it will work, you can try though. Thats why its strictly advised to do backup before messing your phone in anyway..
3. Pls refer or ask in your respective rom thread.
Sent from my hero2lte using XDA Labs
shah22 said:
1] You didn't formatted /data and/or flashed magisk or supersu after booting into twrp first time.
Note that you need to format /data under wipe in twrp and type yes and then again reboot in twrp. This is necessary step to disable encryption. And after that flash magisk without any reboot or flash your required rom by following your respective rom thread.
Please note that keeping system read only will cause you to flash in systemless root mode like magisk or super su in systemless mode. There is no difference between normal root mode and systemless root mode except that you will need to allow system modifications in twrp in normal root which will in turn trigger dm verity check and you will need to flash no verity zip to make phone bootable when system modification method (normal root) is selected. Plus system modification will cause certain apps to detect root easily plus increasing complications like I said above. So just keep read only and flash magisk and you will get root in systemless mode without any cons !
Here, you said you're getting a verification screen after rebooting twrp..
This can be caused either by.
1. Not formatting /data after booting twrp for first time
2. Not flashing magisk after formatting /data
3. Enabling system modifications and not flashing no verity zips/magisk
4. Oem unlock is not enabled..
2] You cannot restore data if you didn't back it up before messing with it, or you made a titanium backup/twrp backup.
Smart switch cannot flash phone anymore ..
Yes, flashing stock firmware using home_csc in odin, will not delete data and may restore your phone, but no guarantee that it will work, you can try though. Thats why its strictly advised to do backup before messing your phone in anyway..
3. Pls refer or ask in your respective rom thread.
Thanks for your reply Shah though I'm still a bit confused by it.
UnIock OEM was enabled as was USB debugging.
Fortunately, I was able to reflash the stock rom and phone is working again but what sort of backup are you indicating in part 2. above), NAND, Smartswitch or just back up to google, Samsung & Whatsapp accounts?
In 1). of your reply you say 'You didn't formatted /data and/or flashed magisk or supersu after booting into twrp first time.
Note that you need to format /data under wipe in twrp and type yes and then again reboot in twrp. This is necessary step to disable encryption. And after that flash magisk without any reboot or flash your required rom by following your respective rom thread.'
I thought that if I do format /data my data would be lost and I want to make a NAND backup of the existing rom and data before flashing/modifying but if that doesn't loose the data, I assume then the steps are as follows:
1. Flash TWRP with Odin
2. Boot into Recovery-TWRP
3. Tap on the Read Only button on the 1st TWRP screen
4. Format /data under wipe in TWRP and tap yes and then reboot in TWRP. - Do you mean reboot the phone into TWRP of just go back into the TWRP main menu & when do I make the NAND backup?
5. Flash magisk or supersu from SD card no reboot
6. Flash Lineage OS rom from SD card.
7. Reboot.
Please correct any errors above as I've now tried 3 times since my original post without success but always managed to reflash the stock rom to get me going again.
Click to expand...
Click to collapse
rebgershon said:
Thanks for your reply Shah though I'm still a bit confused by it.
Click to expand...
Click to collapse
Thats why you read forums again and again and unless you are sure and know what you're doing, don't proceed with these things and read again.
rebgershon said:
UnIock OEM was enabled as was USB debugging.
Fortunately, I was able to reflash the stock rom and phone is working again but what sort of backup are you indicating in part 2. above), NAND, Smartswitch or just back up to google, Samsung & Whatsapp accounts?
Click to expand...
Click to collapse
Upto you which backup you prefer, saving data on separate storage is the main goal as rooting and flashing custom rom would erase all your data from phone.
rebgershon said:
I thought that if I do format /data my data would be lost and I want to make a NAND backup of the existing rom and data before flashing/modifying but if that doesn't loose the data, I assume then the steps are as follows
Click to expand...
Click to collapse
What you mean exactly ? What doesn't loose the data ? Flashing custom rom first time/rooting always erases your data and yes you need to backup before flashing/modifying.
rebgershon said:
1. Flash TWRP with Odin
2. Boot into Recovery-TWRP
3. Tap on the Read Only button on the 1st TWRP screen
4. Format /data under wipe in TWRP and tap yes and then reboot in TWRP. - Do you mean reboot the phone into TWRP of just go back into the TWRP main menu & when do I make the NAND backup?
5. Flash magisk or supersu from SD card no reboot
6. Flash Lineage OS rom from SD card.
7. Reboot.
Click to expand...
Click to collapse
In step 4. Reboot again in twrp after formatting /data.
When do you make nand backup?? Lol, at this point your phone would have nothing to backup, you should have made a backup the first time you tried modifying your phone. Because flashing stock rom like you said you did many times, already formats the phone.
If you mean you want to backup your phone again, then you can't backup in twrp in this stage. Backup before flashing twrp through any means.
Step 5 is correct, I don't know about step 6. I never flashed lineage and have no experience about it. Pls refer lineage's respective rom thread for exact steps. Good luck
Sent from my hero2lte using XDA Labs
shah22 said:
Thats why you read forums again and again and unless you are sure and know what you're doing, don't proceed with these things and read again.
Upto you which backup you prefer, saving data on separate storage is the main goal as rooting and flashing custom rom would erase all your data from phone.
What you mean exactly ? What doesn't loose the data ? Flashing custom rom first time/rooting always erases your data and yes you need to backup before flashing/modifying.
In step 4. Reboot again in twrp after formatting /data.
When do you make nand backup?? Lol, at this point your phone would have nothing to backup, you should have made a backup the first time you tried modifying your phone. Because flashing stock rom like you said you did many times, already formats the phone.
If you mean you want to backup your phone again, then you can't backup in twrp in this stage. Backup before flashing twrp through any means.
Step 5 is correct, I don't know about step 6. I never flashed lineage and have no experience about it. Pls refer lineage's respective rom thread for exact steps. Good luck
Sent from my hero2lte using XDA Labs
Click to expand...
Click to collapse
Thanks again Shah for your reply/help.
I followed the instructions and got the lineage rom installed and Gapps but I don't think Gapps installed properly as I wasn't able to restore any of the saved data from my google account and it wouldn't allow me to add any other accounts except email so for now I've restored the stock rom and my data.
Is there another Android 10 rom you can recommend besides lineage that will have a similar appearance to Samsung?
rebgershon said:
Thanks again Shah for your reply/help.
I followed the instructions and got the lineage rom installed and Gapps but I don't think Gapps installed properly as I wasn't able to restore any of the saved data from my google account and it wouldn't allow me to add any other accounts except email so for now I've restored the stock rom and my data.
Is there another Android 10 rom you can recommend besides lineage that will have a similar appearance to Samsung?
Click to expand...
Click to collapse
I don't recommend any rom except a stock rooted debloated one.. (like Alexndr's devbase)
Reason : because full custom roms have a high chance to mess up your phone's efs and permanent soft brick issues.
But, I'm in love with infinity wallpapers, dark mode and android 10 in general like all others these days.. so if you really want samsung android 10 for S7 edge, then Floyd V4 is your best bet.. see on rom and software developer section of s7 edge to find floyd v4. Its a s9 android 10 one ui 2 port...
Personally, I'm using latest alexndr's devbase rom. Because I'm still paranoid about fully custom or ported roms
Alexndr's devbase is a full stock oreo - debloated rom. Which has option to root during flashing in twrp too. Its perfect for my needs.
But maybe soon, I will change to Floyd v4 to experience the future.. who knows
Sent from my Legendary Hero2LTE using Tapatalk
shah22 said:
I don't recommend any rom except a stock rooted debloated one.. (like Alexndr's devbase)
Reason : because full custom roms have a high chance to mess up your phone's efs and permanent soft brick issues.
But, I'm in love with infinity wallpapers, dark mode and android 10 in general like all others these days.. so if you really want samsung android 10 for S7 edge, then Floyd V4 is your best bet.. see on rom and software developer section of s7 edge to find floyd v4. Its a s9 android 10 one ui 2 port...
Personally, I'm using latest alexndr's devbase rom. Because I'm still paranoid about fully custom or ported roms
Alexndr's devbase is a full stock oreo - debloated rom. Which has option to root during flashing in twrp too. Its perfect for my needs.
But maybe soon, I will change to Floyd v4 to experience the future.. who knows
Shah,
Many thanks for the recommendation of the FloydQ rom.
I installed it yesterday after making all backups inc. Smartswitch.
Very easy to install both from flashing and Aroma installation viewpoints. Ran 1st time without a glitch and phone now thinks its an S9+ running Android 10 a la Samsung. I even managed to transfer my Smartswitch backup to my wife's old S7 Edge and then used Smartswitch to transfer from that phone to the 'S9+'.
Only glitch was logging into my Samsung account but sorted that as well so all in all very happy so far.:good:
Click to expand...
Click to collapse