Database Users

Moto X No service error

After i flashed Twrp my phone wont get any service and i have checked imei and it is at 00000000. Is there a way to fix this?
I have my original imei number with me
Any help would be appreciated

R0gueThund3r said:
After i flashed Twrp my phone wont get any service and i have checked imei and it is at 00000000. Is there a way to fix this?
I have my original imei number with me
Any help would be appreciated
Click to expand...
Click to collapse
You pure or style? Try pulling sims card and reinsert? Not heard that one just from flashing twrp.
Sent from my XT1575 using Tapatalk 2

milski65 said:
You pure or style? Try pulling sims card and reinsert? Not heard that one just from flashing twrp.
Sent from my XT1575 using Tapatalk 2
Click to expand...
Click to collapse
I am using the pure and i have tried reinserting the sim card , and i checked the sim card in another phone and it works

R0gueThund3r said:
I am using the pure and i have tried reinserting the sim card , and i checked the sim card in another phone and it works
Click to expand...
Click to collapse
You've done nothing else but unlock bootloader and twrp via adb?
Sent from my XT1575 using Tapatalk 2

milski65 said:
You've done nothing else but unlock bootloader and twrp via adb?
Sent from my XT1575 using Tapatalk 2
Click to expand...
Click to collapse
That and adding super Su

R0gueThund3r said:
That and adding super Su
Click to expand...
Click to collapse
I'll keep looking, but I haven't seen that mentioned.
Sent from my XT1575 using Tapatalk 2

I've got the same issue, unlocked the bootloader and flashed TWRP via the command line (as well as SuperSU via TWRP). Rebooted and re-inserted the SIM multiple times to no avail.
Edit: I've tried looking for the APN settings on my device, but that seems to have disappeared as well? here's a screenshot of what my settings screen looks like: https://gyazo.com/90f9ab027357cea8009bdae1a0346690
Edit 2: I checked my IMEI, and it's weird...I see every digit except for the last one when I look for it via the *#06# dialer command (I know because I cross-referenced with the IMEI printed on the box the phone came in).
---------- Post added at 11:46 AM ---------- Previous post was at 11:24 AM ----------
R0gueThund3r said:
That and adding super Su
Click to expand...
Click to collapse
have you had any luck resolving the issue?

Mine did the same thing. Flashed TWRP and SuperSU. Then I copied a few apks and jars from /system for vendor blobs with root explorer. I don't see how anything changed there because system is read only (but it was ril related files).
After some digging I had my IMEI but my phone number was "Unknown". I went to AT&T for a new sim but that didn't fix it. I ended up going back to stock with this thread: http://forum.xda-developers.com/mo...dows-tool-moto-x-style-pure-edition-t3199905 and everything is working again.
TWRP and root again and so far still have network.

rwaterspf1 said:
Mine did the same thing. Flashed TWRP and SuperSU. Then I copied a few apks and jars from /system for vendor blobs with root explorer. I don't see how anything changed there because system is read only (but it was ril related files).
After some digging I had my IMEI but my phone number was "Unknown". I went to AT&T for a new sim but that didn't fix it. I ended up going back to stock with this thread: http://forum.xda-developers.com/mo...dows-tool-moto-x-style-pure-edition-t3199905 and everything is working again.
TWRP and root again and so far still have network.
Click to expand...
Click to collapse
I used that to reset but i still get the problem

R0gueThund3r said:
I used that to reset but i still get the problem
Click to expand...
Click to collapse
Did you solve your problem??
im getting no service after Unlock bootloader and flash TWRP.

rwaterspf1 said:
Mine did the same thing. Flashed TWRP and SuperSU. Then I copied a few apks and jars from /system for vendor blobs with root explorer. I don't see how anything changed there because system is read only (but it was ril related files).
After some digging I had my IMEI but my phone number was "Unknown". I went to AT&T for a new sim but that didn't fix it. I ended up going back to stock with this thread: http://forum.xda-developers.com/mo...dows-tool-moto-x-style-pure-edition-t3199905 and everything is working again.
TWRP and root again and so far still have network.
Click to expand...
Click to collapse
I also have lost service after flashing some ROMS on my VZ MXP. Reinserting the SIM, reflashing other ROMs or reflashing the radio haven't helped. I'll give this a try. Thanks.

What ROM are you using? Did you recently upgrade from lollipop to marshmallow or marshmallow to nougat? Have you ran fastboot erase all (if not DO NOT that causes the imei to be permenantly erased). Have you tried flashing files from the factory image? This is very strange.

thebaconbox said:
What ROM are you using? Did you recently upgrade from lollipop to marshmallow or marshmallow to nougat? Have you ran fastboot erase all (if not DO NOT that causes the imei to be permenantly erased). Have you tried flashing files from the factory image? This is very strange.
Click to expand...
Click to collapse
The loss of service occurred after flashing the 11/11/16 nightly of AICP, which I believe is Nougat. I had already had the 11/09 and 11/10 nightly installed. The 11/10 seemed to perform OK, except battery life was short. The 11/11 version caused a bunch of com.android.phone errors. I then reflashed the stock ROM posted here, but the problem persists. I haven't tried the factory image. Do you have a link to the process to do that?. I'm currently using my GS3 and that phone is way too slow, definitely would like to go back to my MXP.

rwaterspf1 said:
Mine did the same thing. Flashed TWRP and SuperSU. Then I copied a few apks and jars from /system for vendor blobs with root explorer. I don't see how anything changed there because system is read only (but it was ril related files).
After some digging I had my IMEI but my phone number was "Unknown". I went to AT&T for a new sim but that didn't fix it. I ended up going back to stock with this thread: http://forum.xda-developers.com/mo...dows-tool-moto-x-style-pure-edition-t3199905 and everything is working again.
TWRP and root again and so far still have network.
Click to expand...
Click to collapse
OK, I used this tool. It fixed the problem, and have restored service. Had to also do the wifi fix, which is discussed later in that thread. Thank you.

can u please me how you fix that , i have few units same issue no service

Gsm UK said:
can u please me how you fix that , i have few units same issue no service
Click to expand...
Click to collapse
Your units are not the same, they are XT1578 engineering units which were intended for Verizon specific service, but never came to fruition... those units are likely fancy paperweights now, no ROM or radios were ever released for them since they used a special chipset.

This may be a stupid question, but did you clean flash or dirty flash the stock ROM and/or aicp? Make sure you fully wipe/format system, boot, cache, data, and dalvik cache when flashing new ROMs.

I also have problems with the network, no signal, plus my appears the normal imei, Moto X Style Brazil.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Anyone from you guys with no service devices got the solution or not?

[Discussion] Dumb attempt to upgrade to Marshmallow with TWRM in osprey

Hi everyone, posting this as a information about something you should NOT try: upgrade your OTA rom with custom recovery installed, in my case TWRP.
I did this with ignorance of not think that (or search about) the custom rom could interfere at the normal process of OTA upgrade from Lollipop to MarshMallow. Actually I remembered that I was unlocked and rooted the phone but I did not remember I was using custom recovery. AFAIK at this device is impossible to root without unlocking and custom recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are on TWRP don't do this!
For those don't know about TWRP and OTA updates, read this:
https://twrp.me/faq/officialota.html
In short terms: don't try OTA updates (official updates) if you installed custom rom such as TWRP. "Installing official updates from your manufacturer or carrier is not supported by TWRP." "[This] may result in unexpected behavior" "Most of the time the best way to get a new update onto your device is to simply wait a couple of days for ROM makers for your device to come up with ROMs that are based on the new update that you can safely and easily install."
But I did it. And now I'm reporting it for those who are curious. So, what's happened?
Fortunately the device is not bricked as I thought when it reboot to TWRP for flashing the OTA update instead of the stock recovery process! I thought that I messed everything when I see the frozen TWRP for something about 10 minutes or less. After the long 10 minutes of frozen TWRP image I got the recovery working and checked the log:
Of course, errors on the log.
Rebooted and got a frozen background image, after a while a permanent black. When the screen turn off the notification system shows the battery as dead (and it as not). But I could turn it off and gain access to the recovery holding power and volume down buttons.
After two failed reboots to the system with the same result I tried to make a screenshot using the hard buttons and it works (screenshoted the black screen) and suddenly the lock screen shows up. I got into, everything working slow meaning that there was a lot things working in the background. Got some error messages from google service and MMS/SMS communication and minutes later it automatically reboots and booted the TWRP again.
This turned to a loop. I stopped this by going to the system setup - about the device - check for updates. And got a message "the update has failed". Good. After a while the message offering the update shows again... No, thanks...
I rebooted to TWRP and fixed the permissions, maybe this solve some problems.
Right now the phone is working but the rebooting process has unexpected behaviors, some tries result in a normal fast process and other tries result in a long black image and the system/launcher just don't arm up for some minutes, but after a while it works. I'm not confident. Already backed up apps with Titanium backup.
I'm planning to restore everything from the stock using this guide:
http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
And them, maybe, update the OTA to marshmallow. Before doing that, I will search and get to know if it is possible to re-root the phone with marshmallow in osprey (that means re-unlock and install TWRP again). Rooted device it's a need for me.
This is what happened to my device when tried to OTA update with TWRP. I had luck not bricking this.

+1 on the dumb attempt. Early morning, excited for the release, upgrade please! Yeah, no good. Is restoring our only option? Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?

did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery ?
Sent from my Nexus 6 using Tapatalk

Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?
Click to expand...
Click to collapse
Yeah, DON'T proceed with the update! Deleting the downloaded files just break the process... My advise is to make a backup before deleting this.

sgloki77 said:
did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery
Click to expand...
Click to collapse
Ok, sorry about the huge wall of text.

No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.

golgiapp said:
No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.
Click to expand...
Click to collapse
:good:
Good to know that a factory reset could fix the problems caused by the OTA update with TWRP. But after this it should remain with custom recovery and not possible to OTA update. for stock MM

i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Not sure, but take a look at /cache

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
/data/data/com.motorola.ccc.ota/app_download

hp420 said:
/data/data/com.motorola.ccc.ota/app_download
Click to expand...
Click to collapse
found it!!
thanks extracted ok !!
its a zip flashable,can it be converted to install like the oem recovery images using the adb method?

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Thank you for the warning
---------- Post added at 12:58 AM ---------- Previous post was at 12:54 AM ----------
Thank you for the warning

I experience this today, I flashed a stock rom again so I can have the OTA update, but what I can't do is root my device, I flash the custom recovery and then I flash the beta version of SuperSU, and when I reboot my device it bricks in the Motorola Logo, anybody knows how to fix this, or should I wait a little bit longer to root my phone? as the OP I need root too

Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk

nelsonw said:
Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again

VicSanRED said:
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again
Click to expand...
Click to collapse
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.

hp420 said:
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.
Click to expand...
Click to collapse
I tried with the latest version 2.66 and still the same issue. Don't know what to do now.

So its posible to root MM ?? Safe ,stable?
Supersu v 2.62??

Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk

nelsonw said:
Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Can you post a little tutorial?, I wanna be sure I'm doing everything OK.

I messed up badly. Need help in reviving my Phone.

So I was flashing couple of custom ROMs but I didn't knew I would messed up this badly.
So here's what I did. I had older TWRP 3.0.2-0 version which was working fine. So before flashing new ROM, I decided to back up my existing MiUI8 ROM in case something goes wrong and I saved the TWRP back up in my PC.
After that I thought before flashing custom ROM why not just update the TWRP recovery since it was quite old. So I did that through fastboot method and flashed a custom ROM. It was working OK but some Banking official apps were not working so decided to flash back my old MiUi8 ROM. Now here's where I messed up. Now the TWRP asks me to enter my encryption password which I did and decided to restore my older ROM but it gave me the error that "I entered correct password but my data has been corrupted" and prompt to do a Reset. So I did that using Wipe option in TWRP and it did got booted successfully but now its showing me error
"Find device storage corrupted your device is unsafe now"
My WiFi is disabled. Please help me now. Seems I messed up badly.

kernel.debugger said:
So I was flashing couple of custom ROMs but I didn't knew I would messed up this badly.
So here's what I did. I had older TWRP 3.0.2-0 version which was working fine. So before flashing new ROM, I decided to back up my existing MiUI8 ROM in case something goes wrong and I saved the TWRP back up in my PC.
After that I thought before flashing custom ROM why not just update the TWRP recovery since it was quite old. So I did that through fastboot method and flashed a custom ROM. It was working OK but some Banking official apps were not working so decided to flash back my old MiUi8 ROM. Now here's where I messed up. Now the TWRP asks me to enter my encryption password which I did and decided to restore my older ROM but it gave me the error that "I entered correct password but my data has been corrupted" and prompt to do a Reset. So I did that using Wipe option in TWRP and it did got booted successfully but now its showing me error
"Find device storage corrupted your device is unsafe now"
My WiFi is disabled. Please help me now. Seems I messed up badly.
Click to expand...
Click to collapse
Your issue is encryption issue....you need to format data from recovery.....reboot your device to recovery again and then try to restore backup.
---------- Post added at 05:12 AM ---------- Previous post was at 05:05 AM ----------
Not 100 % guarantee but should work..
If recovered.... your good luck....if not...
Then download fastboot rom for your device and flash through mi flash tool.
Good luck....:good:

Ajay kumar 7 said:
Your issue is encryption issue....you need to format data from recovery.....reboot your device to recovery again and then try to restore backup.
---------- Post added at 05:12 AM ---------- Previous post was at 05:05 AM ----------
Not 100 % guarantee but should work..
If recovered.... your good luck....if not...
Then download fastboot rom for your device and flash through mi flash tool.
Good luck....:good:
Click to expand...
Click to collapse
I did flashed fastboot ROM through Mi Flash Tool but it didn't work. My WiFi and Bluetooth are disabled. Can't Login in Mi Account.

kernel.debugger said:
I did flashed fastboot ROM through Mi Flash Tool but it didn't work. My WiFi and Bluetooth are disabled. Can't Login in Mi Account.
Click to expand...
Click to collapse
Do same process by entering your device in edl mode....

Ajay kumar 7 said:
Do same process by entering your device in edl mode....
Click to expand...
Click to collapse
Dude! You are a life saver. I was managed to successfully revive the phone by flashing in EDL mode. Though I had to lock everything but phone is working now. WiFi Bluetooth working. Can Login in Mi Account. No longer getting "corrupted device" popup. I lost my all internal data though. Its okay. Have to manage. Thank you so much.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

kernel.debugger said:
Dude! You are a life saver. I was managed to successfully revive the phone by flashing in EDL mode. Though I had to lock everything but phone is working now. WiFi Bluetooth working. Can Login in Mi Account. No longer getting "corrupted device" popup. I lost my all internal data though. Its okay. Have to manage. Thank you so much.
Click to expand...
Click to collapse
No bro .......
We are here to help each other.....
Enjoy bro....

Ajay kumar 7 said:
No bro .......
We are here to help each other.....
Enjoy bro....
Click to expand...
Click to collapse
Thanks!!! I had same problem and now it's solved! Thanks again!

ivaitsis1974 said:
Thanks!!! I had same problem and now it's solved! Thanks again!
Click to expand...
Click to collapse
:good:

kernel.debugger said:
Dude! You are a life saver. I was managed to successfully revive the phone by flashing in EDL mode. Though I had to lock everything but phone is working now. WiFi Bluetooth working. Can Login in Mi Account. No longer getting "corrupted device" popup. I lost my all internal data though. Its okay. Have to manage. Thank you so much.
Click to expand...
Click to collapse
You could have saved a heck lot by just restoring your persist partition from miui backup.
Always take backup of persist, if anytime you get error with mi account or wifi bt not working, then just restore old persist and it will work like before.
Didn't see this thread first else, i could have saved your time.
Remember that for next time though.
---------- Post added at 05:53 PM ---------- Previous post was at 05:49 PM ----------
santoshk22 said:
You could have saved a heck lot by just restoring your persist partition from miui backup.
Always take backup of persist, if anytime you get error with mi account or wifi bt not working, then just restore old persist and it will work like before.
Didn't see this thread first else, i could have saved your time.
Remember that for next time though.
Click to expand...
Click to collapse
Also, i think that you didn't backup persist while backing up miui. Since ,Your device us working now, just backup that partition, and if something like this happens again just restore it and you're done.

Updating from 10 to 11 with root

Ok, so I'm gonna do the update to android 11 now that it seems to be more stable. My question is, once I do that, and I keep root, is there a way to do a factory data reset and not lose root all together? I like to do a factory reset when doing a major update just to make sure things run as smooth as possible, but I'd like to not lose root in the process. Thanks in advance!

Root (aka Magisk) IMHO resides in the boot image, so a factory reset would not interfere with root itself. Of course you would need to reinstall Magisk manager (Canary) after the factory reset. Oh, and you need to be on Canary Magisk for A11 anyway - so if you do the update from A10 you need to make sure you are on Magisk Canary (Manager and Magisk itself) or it won't work afterwards...

s3axel said:
Root (aka Magisk) IMHO resides in the boot image, so a factory reset would not interfere with root itself. Of course you would need to reinstall Magisk manager (Canary) after the factory reset. Oh, and you need to be on Canary Magisk for A11 anyway - so if you do the update from A10 you need to make sure you are on Magisk Canary (Manager and Magisk itself) or it won't work afterwards...
Click to expand...
Click to collapse
Nope latest beta works great too. Canary isn't needed anymore.

imneveral0ne said:
Ok, so I'm gonna do the update to android 11 now that it seems to be more stable. My question is, once I do that, and I keep root, is there a way to do a factory data reset and not lose root all together? I like to do a factory reset when doing a major update just to make sure things run as smooth as possible, but I'd like to not lose root in the process. Thanks in advance!
Click to expand...
Click to collapse
I have guides for this and for 11-11 they're in the guides section.
Thoroughly tested.

Kollachi said:
Nope latest beta works great too. Canary isn't needed anymore.
Click to expand...
Click to collapse
So I just need beta magisk and the regular app? Cause I just installed the canary magisk manager and it's missing quite a few options like magisk hide and such. And I definitely need those.

dladz said:
I have guides for this and for 11-11 they're in the guides section.
Thoroughly tested.
Click to expand...
Click to collapse
That is a lot more involved than I was expecting this to be. I figured I could just retain root with an update the same way I always do.

imneveral0ne said:
That is a lot more involved than I was expecting this to be. I figured I could just retain root with an update the same way I always do.
Click to expand...
Click to collapse
It's 9 steps?
You need to remove modules, you will need to use the updated boot img and your won't have twrp to fall back on.
If you want to wipe after you'll need to set up then reinstall magisk then obtain your boot img, patch it and boot it then flash it directly.

dladz said:
It's 9 steps?
You need to remove modules, you will need to use the updated boot img and your won't have twrp to fall back on.
If you want to wipe after you'll need to set up then reinstall magisk then obtain your boot img, patch it and boot it then flash it directly.
Click to expand...
Click to collapse
It's not that, it's just that I usually used a pretty simple guide for updates and I didn't need to do anything on the computer for it to work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is it because we're updating from 10 to 11 that these extra steps are needed? Sorry, I'm just curious is all.

imneveral0ne said:
It's not that, it's just that I usually used a pretty simple guide for updates and I didn't need to do anything on the computer for it to work.
Is it because we're updating from 10 to 11 that these extra steps are needed? Sorry, I'm just curious is all.
Click to expand...
Click to collapse
No not at all.
Tbh it's extremely similar.
Just that the way I've written it means you won't have issues, I'd rather cover bases in a guide than answer a 100 questions later.
If you have magisk functional already then you're halfway there.
I've updated the OP in my guide.
Some steps are informational

dladz said:
No not at all.
Tbh it's extremely similar.
Just that the way I've written it means you won't have issues, I'd rather cover bases in a guide than answer a 100 questions later.
If you have magisk functional already then you're halfway there.
I've updated the OP in my guide.
Some steps are informational
Click to expand...
Click to collapse
I installed the canary built of magisk from your thread, but there isn't an install button. ?
Edit: I went back to the beta build and it worked fine with patching.

imneveral0ne said:
I installed the canary built of magisk from your thread, but there isn't an install button. ?
Edit: I went back to the beta build and it worked fine with patching.
Click to expand...
Click to collapse
Good stuff..so what channel did you change it to.? Are you able to provide a version as someone has the exact same issue.

dladz said:
Good stuff..so what channel did you change it to.? Are you able to provide a version as someone has the exact same issue.
Click to expand...
Click to collapse
Just the beta channel. And I can once I get my phone working again lol. You straight up told me I was gonna need to use this to root my phone after a factory reset. And I went ahead and installed twrp anyway. Using the msm tool now to fix it lol.

imneveral0ne said:
Just the beta channel. And I can once I get my phone working again lol. You straight up told me I was gonna need to use this to root my phone after a factory reset. And I went ahead and installed twrp anyway. Using the msm tool now to fix it lol.
Click to expand...
Click to collapse
Lol no worries man. Glad you're up and running.
:good:

Cannot boot to latest version of TWRP on SM-N910G

Hello!
I bought an SM-N910G on ebay recently. The stock rom is a little bit slow and I would like to flash lineage or something else.
When i try to flash the latest version of twrp with odin it passes and shows the splash screen with the logo and version (all normal) but doesnt load and reboots to Android.
Does anyone have any ideas? ive tried most things that i found online but nothing works. the first available version on the twrp website does flash and work but wont flash latest lineage.

del32 said:
Hello!
I bought an SM-N910G on ebay recently. The stock rom is a little bit slow and I would like to flash lineage or something else.
When i try to flash the latest version of twrp with odin it passes and shows the splash screen with the logo and version (all normal) but doesnt load and reboots to Android.
Does anyone have any ideas? ive tried most things that i found online but nothing works. the first available version on the twrp website does flash and work but wont flash latest lineage.
Click to expand...
Click to collapse
Which bootloader is active?
So 3.6.2-9-0 doesn't start?
Tried flashing that .img using old TWRP as well or only .tar with Odin?
What did 3.1.0-0 say when flashing LOS fails?

bmwdroid said:
Which bootloader is active?
So 3.6.2-9-0 doesn't start?
Tried flashing that .img using old TWRP as well or only .tar with Odin?
What did 3.1.0-0 say when flashing LOS fails?
Click to expand...
Click to collapse
sorry i am not sure what you mean by which bootloader is active, is there a way to check this?
Nope, it just loads on the splash screen for a while then boots back to android
I have tried old twrp to flash and odin tar
It said an error about this rom is for *phone* you are using blank or something along those lines.
Afaik 3.5(?) is the only one that can install past oreo roms

del32 said:
sorry i am not sure what you mean by which bootloader is active,
is there a way to check this?
Click to expand...
Click to collapse
That's the one from the stock firmware you came from.
Should be the latest stock possible.
Did you check or can you tell?
del32 said:
Nope, it just loads on the splash screen for a while then boots back to android
I have tried old twrp to flash and odin tar
It said an error about this rom is for *phone* you are using blank or something along those lines.
Click to expand...
Click to collapse
Can you provide a screenshot?
del32 said:
Afaik 3.5(?) is the only one that can install past oreo roms
Click to expand...
Click to collapse
Well mine is on 3.6.1_9-0 and currently on Havoc 4.16 I got from the telegram group.
Has of course the battery drain problem (like all A11 custom versions for this device) when shut down.
With that TWRP I've installed A11 versions of LOS, crDroid and Havoc mulitple times.

bmwdroid said:
That's the one from the stock firmware you came from.
Should be the latest stock possible.
Did you check or can you tell?
Can you provide a screenshot?
Well mine is on 3.6.1_9-0 and currently on Havoc 4.16 I got from the telegram group.
Has of course the battery drain problem (like all A11 custom versions for this device) when shut down.
With that TWRP I've installed A11 versions of LOS, crDroid and Havoc mulitple times.
Click to expand...
Click to collapse
im using the latest 6.0.1 australia optus firmware (im australian and on optus)
there were bootloader files there available there for download but i dont think they worked for me. and also gave me no service in android
I am currently at school, so i will be able to provide a screenshot later
should i try a different stock firmware version/ different country carrier when i get home?

del32 said:
im using the latest 6.0.1 australia optus firmware (im australian and on optus)
Click to expand...
Click to collapse
So that should be ok.
del32 said:
...
should i try a different stock firmware version/ different country carrier when i get home?
Click to expand...
Click to collapse
No idea if that wil do any good or even harm your device.
I know that on some that works but idk about yours.
Perhaps it will help to start from scratch flashing the latest stock if available via samfirm_reborn_3.6.3 (gets it directly from Samsungs servers).

bmwdroid said:
So that should be ok.
No idea if that wil do any good or even harm your device.
I know that on some that works but idk about yours.
Perhaps it will help to start from scratch flashing the latest stock if available via samfirm_reborn_3.6.3 (gets it directly from Samsungs servers).
Click to expand...
Click to collapse
I'll try samfirm_reborn_3.6.3
currently installing the files it needs
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

@del32 which files?
Didn't need any additional ones on my W11 system.
SamFirm_Reborn itself starts directly without installation.
Took it from here:
GitHub - ivanmeler/SamFirm_Reborn
Contribute to ivanmeler/SamFirm_Reborn development by creating an account on GitHub.
github.com

bmwdroid said:
@del32 which files?
Didn't need any additional ones on my W11 system.
SamFirm_Reborn itself starts directly without installation.
Took it from here:
GitHub - ivanmeler/SamFirm_Reborn
Contribute to ivanmeler/SamFirm_Reborn development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
not sure what it needed but i just installed anyways and it all worked
used the same github link
also now in twrp, getting error 1 got a screenshot

del32 said:
not sure what it needed but i just installed anyways and it all worked
used the same github link
also now in twrp, getting error 1 got a screenshot
Click to expand...
Click to collapse
Well your device is trltedt so ROM should fit.
Which TWRP right now?
Did updaing it work?
You did "Format data" after wiping?
Tried with 2nd download of that ROM?
Tried crDroid or Havoc?
Once when I had flashing problems I changed filesystem of several partitions to and fro which helped.
If that all doesn't help I'ld start from scratch.

bmwdroid said:
Well your device is trltedt so ROM should fit.
Which TWRP right now?
Did updaing it work?
You did "Format data" after wiping?
Tried with 2nd download of that ROM?
Tried crDroid or Havoc?
Once when I had flashing problems I changed filesystem of several partitions to and fro which helped.
If that all doesn't help I'ld start from scratch.
Click to expand...
Click to collapse
I am using 3.1.0
I tried a later version and still didnt work, 3.2.2 does not even work!!!
Yes, format data after wiping.
I have tried to redownload
will try havoc right now

@bmwdroid
same issue with havoc, error one and your device is blank
not sure what happened with it

del32 said:
@bmwdroid
same issue with havoc, error one and your device is blank
not sure what happened with it
Click to expand...
Click to collapse
I suppose you definitely need a higher TWRP version but don't understand why you can't flash it.
What does TWRP say when you flash a higher version?

@del32 regarding higher TWRP.
As I understood you you're either flashing 3.5 or higher using Odin and it then TWRP doesn't start afterwards.
Correct?
What happens when you flash high TWRP...img using the older 3.1. TWRP and reboot after that into recovery from TWRP menu?

bmwdroid said:
@del32 regarding higher TWRP.
As I understood you you're either flashing 3.5 or higher using Odin and it then TWRP doesn't start afterwards.
Correct?
What happens when you flash high TWRP...img using the older 3.1. TWRP and reboot after that into recovery from TWRP menu?
Click to expand...
Click to collapse
I just got it to work!!! TWRP 3.5.2 and Havoc are running!!!
i was recording a video to show what i did and how it failed and it just worked
as long as i dont screw around with twrp i should be fine, thank you for your help.
if it wasnt for your response i was just going to give up and not bother.
Your browser is not able to display this video.

@del32 glad I could somewhat help.
May I quote from the film "Galaxy Quest":
Never give up, never surrender
Additional advices: I saw you rebooting after flashing but it's recommended to wipe Cache/Dalvik before the reboot.
It's useful to activate "advanced reboot" so that you can directly reboot to TWRP from the system without button combo.
When you want to get a higher TWRP you can flash it directly within the old one using a .img file.
Worked always for me so it should for you as well.
And you could mark the thread as solved so that others have no need to answer.

bmwdroid said:
@del32 glad I could somewhat help.
May I quote from the film "Galaxy Quest":
Never give up, never surrender
Additional advices: I saw you rebooting after flashing but it's recommended to wipe Cache/Dalvik before the reboot.
It's useful to activate "advanced reboot" so that you can directly reboot to TWRP from the system without button combo.
When you want to get a higher TWRP you can flash it directly within the old one using a .img file.
Worked always for me so it should for you as well.
And you could mark the thread as solved so that others have no need to answer.
Click to expand...
Click to collapse
Thank you very much, also ive never had issue with not wiping after flash but ill keep it in mind and try to remember for later on
I also had advanced reboot on but i didnt have an os on the phone at time of recording
once again, many thanks!!!!!!!
so excited to have Havoc on my phone

del32 said:
Thank you very much, also ive never had issue with not wiping after flash but ill keep it in mind and try to remember for later on
I also had advanced reboot on but i didnt have an os on the phone at time of recording
once again, many thanks!!!!!!!
so excited to have Havoc on my phone
Click to expand...
Click to collapse
Which Havoc version btw?

bmwdroid said:
Which Havoc version btw?
Click to expand...
Click to collapse
4.6, working nicely on android 11
faster than i thought it would be!

@del32 here you find much newer ones: