Related
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
gvazquez82 said:
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
Click to expand...
Click to collapse
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
MrHaPpY66 said:
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
Click to expand...
Click to collapse
First of all thank you for trying to help me, I hope you are having a good Thanks Giving.
I used the thread you linked to, and downloaded the version with out knox. I followed the instructions
transferred ROM and flashed kernel file to SD card
used odin to flash TWRP,
used twrp to flash rom and kernel file.
and it takes the file thankfully, there's only one issue. My phone can't make or receive calls/texts. Is yours able to?
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Next Update
the bootloader I flashed apparently flashed to the external sd card? I flashed another one and it is booting from the internal sd. I had to flash a different modem the one in the bootloader/modem file I flashed from the link above didnt take? I got most everything sorted out, but im getting tired, it has been an all night adventure. its 08:23 est now
sorry for the delay in updating this I had to get some rest.
theramsey3 said:
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Click to expand...
Click to collapse
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
spongdangly said:
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
Click to expand...
Click to collapse
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I will give that a shot, but what's an APN, sorry. And how do I create one, and is it needed for me to do so?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
It should be, I'm working right now so I don't have time to fine the guide on how to inject your IMEI. If I remember correctly it involves using QPST. If you have an old (or any) working Nandroid backup that should fix the problem.
FYI, make sure you don't use the guide for the international S3 as it has different hardware and folder structure/contents.
As for the APN, it should automatically fill itself in since it reads it off the SIM Card (I might be wrong).
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I tried it and it work!!!!!!!!!!!!!!!!!
67 texts just came in. Sir, I thank you oh so kindly. You have made this gloomy rainy day oh so joyous.
No problem. Glad I could help you.
The real credit should go to -Mr.X-, loserskater and anyone else(no disrespect there were alot of files) whose stuff I tried to flash lastnight thank you all in the dev community who contribute.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
gvazquez82 said:
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
Click to expand...
Click to collapse
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
flexfulton said:
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
Click to expand...
Click to collapse
do you know of a good stable kit kat like ROM I could use for the s3? And any speculation as to why the ROMs werent taking for me?
Like many other sprint users, I experienced serious problems with 5.1.1. This resulted in battery pulls and even a downloading boot. I starting looking into a fix. After flashing about every ROM for sprint N910P on this website, I either result in bootloop or the same problems persist. The problems are as follows:
-Can't boot, so I have to wait ~5 minutes to try again
-Boots straight to downloading, mmc read fail
-Boots fine
-Crashes to black screen around 80-90% battery (back to problem 1)
I cannot figure how to use odin anymore because it fails on nearly every rom I attempt. My reactivation lock is OFF.
I'll try to provide as much detail as I can, but I'm at my wits end with this phone.
Thanks!
If you can Odin OK1 stock tar, there is another root alternative: root stock with Chainfire Auto Root. CFAR has been updated for Android 5.1.1 Note 4
http://forum.xda-developers.com/showpost.php?p=55865442&postcount=3
Custom ROMs will take longer than 5 minutes to boot initially after flash. TWRP has been known to fail to flash or not properly flash after trying repeatedly to flash wrong tar with Odin or flash with reactivation locked. Which, if any, apply to you? I hope it's not hardware failure...
Sent from my SM-N910P using Tapatalk
Chainfire was going to be my next option. I think the first time I attempted using chainfire through odin, it ended in a bootloop. I haven't tried the update version though. I'll give that a shot.
Is there any way to fix this problem with TWRP (delete it and reflash)?
I'm starting to think its a hardware failure, which would suck because knox is tripped and warranty expired a few days ago anyway I believe.
I downloaded the updated CFAR last night to verify it was updated. It's bundled with Odin 3.10.6 Use the defaults with that for stock OK1 tar.
You should know that CFAR is primarily for rooted stock.
If you want a custom ROM, you may have to use Philz CWM touch recovery for Note 4. TWRP just gets inoperative for some time for some users when tars fail in repeated attempts. Philz' seems to flash where TWRP doesn't if that's the case.
http://downloadandroidrom.com/file/GalaxyNote4/CWM/philz_touch_6.59.0-trlte.tar
Sent from my SM-N910P using Tapatalk
Sorry to be the bearer of bad news, but this is most likely a hardware problem. I've had two Note 4's do exactly this. Flashed the stock rom on both with Odin, problems still persisted. It would just get random restarts and sometimes boot into "panic mode", whatever that is. The quality control on these phones is terrible. I baby them and never rooted any of them, yet two of them messed up like that, and all 3 of course have GPS issues. If it worked like it's supposed to it would be amazing, my friend has had one since my first Note with 0 issues, super jealous.
I hope its ok for me to post this here i couldnt find any threads on this issue and i didnt want to make new one just for this one problem so i figure i post it here since the post doesnt really point out to nothing specific and its on note 4 thread so i know ill get faster response than if i posted it in help thread ,but if i'm in wrong please feel free to delete this post at once . With that out of the way heres my issue and i hope theres an easy fix for it i was on latest pl1 build of 6.0.1 stock rooted i got tired of playing pokemon so i decided i want my themed look back so i restored my backup of 5.1.1 cog5 build ,everything works fine but my wifi ,its grayed out and when i try to turn it on it stays in "turning on " possition but it never does come on it eventualy goes back to " to see the list of networks turn on the wifi" .Now my question is is there any way to fix this wifi without flashing srock 5.1.1 i know there used to be fix for it back when i was on note 3 but this was yeaaaaars ago and i dont have that file any more thanks a million.
bigbabo said:
I hope its ok for me to post this here i couldnt find any threads on this issue and i didnt want to make new one just for this one problem so i figure i post it here since the post doesnt really point out to nothing specific and its on note 4 thread so i know ill get faster response than if i posted it in help thread ,but if i'm in wrong please feel free to delete this post at once . With that out of the way heres my issue and i hope theres an easy fix for it i was on latest pl1 build of 6.0.1 stock rooted i got tired of playing pokemon so i decided i want my themed look back so i restored my backup of 5.1.1 cog5 build ,everything works fine but my wifi ,its grayed out and when i try to turn it on it stays in "turning on " possition but it never does come on it eventualy goes back to " to see the list of networks turn on the wifi" .Now my question is is there any way to fix this wifi without flashing srock 5.1.1 i know there used to be fix for it back when i was on note 3 but this was yeaaaaars ago and i dont have that file any more thanks a million.
Click to expand...
Click to collapse
To fix the WiFi and camera focus, get the bootloader for OG5 from OP in this thread and flash it in Odin.
https://forum.xda-developers.com/showthread.php?p=66352412
The ones labeled firmware are bootloaders. You don't have to flash the whole OG5 stock tar but you still could. Just make sure the flash restores that bootloader and you should be set.
Likewise, you could still restore a MM backup and restore its bootloader.
I think you should backup your keepsakes in internal memory and wipe internal memory before restoring a backup that crosses Android versions. With backups on extSdCard, you could wipe everything but that but I'd think you could factory reset, wipe internal memory plus the Android folder on extSdCard and have a good transition with the bootloader flash. Otherwise, a factory reset would be the minimum step but may leave some residual information you may not need cluttering your memory along with what you want to keep. Seems I recall some having issues coming back to lollipop from MM without wiping internal memory?
Just curious, do you recall what you wiped going back to lollipop?
Sent from my SM-N920P using Tapatalk
Nothing i just go back n forth between lp and mm depending on lvl of interest in pokemon lol i have backups of 6.0.1 and 5.1.1 i just restore backups without wiping it restores fine aside from wifi not turning on i have no other issues
Edit: sorry meant to quote the post above me
bigbabo said:
Nothing i just go back n forth between lp and mm depending on lvl of interest in pokemon lol i have backups of 6.0.1 and 5.1.1 i just restore backups without wiping it restores fine aside from wifi not turning on i have no other issues
Edit: sorry meant to quote the post above me
Click to expand...
Click to collapse
Gotcha. Just an old question in the back of my mind from early days of MM. I researched the TWRP thread, the developers recommended a factory reset.
If you've ever noticed internal memory available seemingly smaller than usual, it could be the extraneous folders.
Thanks.
Sent from my SM-N920P using Tapatalk
USE THIS IF YOU WANT TO USE DR.KETAN COMPLETELY ON SPRINT NETWORK
I got the rom working on my N910P here are the EXACT steps and links to files i used.
1) Make sure you are on OK1 bootloader: I flashed BOTH the baseband and the Firmware.tar with ODIN
Failure to flash both could lead to WIFI not turning on and Camera not focusing
provided here: http://forum.xda-developers.com/note-4-sprint/development/basebandsbootloaders-ok1-pc1-pb5-t3358357 BIG THANKS TO @freeza
2) Flash the M5 rom
Provided here: http://forum.xda-developers.com/note-4/snapdragon-dev/n910g-dr-ketan-custom-rom-t2928568 another big thanks to @dr.ketan for the great rom!
3)Flash just the H-Vitamin Kernel alone not the MM5 fix or anything just the kernel
Provided Here: http://galaxynote4root.com/t-mobile-note-4-roms/how-to-convert-galaxy-note-4-into-galaxy-s7-edge/2/
Special Thanks to @zedomax! He also has a good video on this if you want to follow there, just use the files I give you rather than the ones he does!
3) Flash the Verizon data fix V2 ( located in attached files under first paragraph). I know you want the phone to work on sprint but for some reason this lead to me getting the rom to work.
provided here: http://forum.xda-developers.com/note-4/snapdragon-dev/marshmallow-6-0-1-ports-data-fixes-t3379978 Thank you @louforgiveno
4) Flash SuperUser I used beta 2.74
provided here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
@chainfire thank you!
5) Boot the phone and set up APN. You don't have to speed through set up, I went ahead and did a full restore before doing all of this.
Name-Whatever you want
APN-n.ispsn
MMSC-http://mms.sprintpcs.com
Multimedia message proxy- 68.28.31.7
Multimedia message port- 80
MCC-310
MNC-120
everything else leave as is go ahead and save.
6)Set Network Mode to LTE/CDMA then go ahead and try to test SMS and MMS
if it doesn't work boot to recovery and go to next step. It didn't work for me but hey you guys might get lucky.
*Note that stock messages app may not work, in my case if i went to attach a file the app crashed so every time so i continued on with Google Messenger*
7)Flash this fix: http://forum.xda-developers.com/note-4-sprint/development/steps-to-install-dr-ketans-rom-g-t3379659/post67086423#post67086423
Thank you @KLPFL
I'm not sure if this fix overwrites what the Verizon V2 fix does, or if its the same thing but like i said these are the steps and files that worked for me!
8)Reboot phone go to settings make sure network is LTE/CDMA, check and make sure APN is set right, now try texting if nothing happens turn off mobile data for a minute. Turn it back on and you should be good to go with sending SMS and MMS (calling and receiving and data work)
Took me a week to figure out all the files and all the fixes to use! I don't take credit for any of the files or fixes or rom I simply got things to work!
@redxblood85 Check your Inbox.
redxblood85 said:
USE THIS IF YOU WANT TO USE DR.KETAN COMPLETELY ON SPRINT NETWORK
I got the rom working on my N910P here are the EXACT steps and links to files i used.
1) Make sure you are on OK1 bootloader: I flashed BOTH the baseband and the Firmware.tar with ODIN
Failure to flash both could lead to WIFI not turning on and Camera not focusing
provided here: http://forum.xda-developers.com/note-4-sprint/development/basebandsbootloaders-ok1-pc1-pb5-t3358357 BIG THANKS TO @freeza
2) Flash the M5 rom
Provided here: http://forum.xda-developers.com/note-4/snapdragon-dev/n910g-dr-ketan-custom-rom-t2928568 another big thanks to @dr.ketan for the great rom!
3)Flash just the H-Vitamin Kernel alone not the MM5 fix or anything just the kernel
Provided Here: http://galaxynote4root.com/t-mobile-note-4-roms/how-to-convert-galaxy-note-4-into-galaxy-s7-edge/2/
Special Thanks to @zedomax! He also has a good video on this if you want to follow there, just use the files I give you rather than the ones he does!
3) Flash the Verizon data fix V2 ( located in attached files under first paragraph). I know you want the phone to work on sprint but for some reason this lead to me getting the rom to work.
provided here: http://forum.xda-developers.com/note-4/snapdragon-dev/marshmallow-6-0-1-ports-data-fixes-t3379978 Thank you @louforgiveno
4) Flash SuperUser I used beta 2.74
provided here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
@chainfire thank you!
5) Boot the phone and set up APN. You don't have to speed through set up, I went ahead and did a full restore before doing all of this.
Name-Whatever you want
APN-n.ispsn
MMSC-http://mms.sprintpcs.com
Multimedia message proxy- 68.28.31.7
Multimedia message port- 80
MCC-310
MNC-120
everything else leave as is go ahead and save.
6)Set Network Mode to LTE/CDMA then go ahead and try to test SMS and MMS
if it doesn't work boot to recovery and go to next step. It didn't work for me but hey you guys might get lucky.
*Note that stock messages app may not work, in my case if i went to attach a file the app crashed so every time so i continued on with Google Messenger*
7)Flash this fix: http://forum.xda-developers.com/note-4-sprint/development/steps-to-install-dr-ketans-rom-g-t3379659/post67086423#post67086423
Thank you @KLPFL
I'm not sure if this fix overwrites what the Verizon V2 fix does, or if its the same thing but like i said these are the steps and files that worked for me!
8)Reboot phone go to settings make sure network is LTE/CDMA, check and make sure APN is set right, now try texting if nothing happens turn off mobile data for a minute. Turn it back on and you should be good to go with sending SMS and MMS (calling and receiving and data work)
Took me a week to figure out all the files and all the fixes to use! I don't take credit for any of the files or fixes or rom I simply got things to work!
Click to expand...
Click to collapse
i m already on stock PE1 .... is it necessary to go back to lollipop OK1 and then again move upwards?
n70shan said:
i m already on stock PE1 .... is it necessary to go back to lollipop OK1 and then again move upwards?
Click to expand...
Click to collapse
Yeah you gotta be on OK1, any marshmallow bootloader will cause the phone to not boot. Once it's set you can try flashing back to PE1. I ran the rom with Beast mode kernel, and PC1 and it worked once it was set up. But yeah for initial set up you need to be on OK1
hey red, I did the install the way you have it set, but after I installed everything and let it boot, I cant access the settings portion? It just says unfortunately settings has stopped? and there is no way to access through the apps launcher because its not there? Where did I go wrong? I started from fresh OK1 as well.
divineazn716 said:
hey red, I did the install the way you have it set, but after I installed everything and let it boot, I cant access the settings portion? It just says unfortunately settings has stopped? and there is no way to access through the apps launcher because its not there? Where did I go wrong? I started from fresh OK1 as well.
Click to expand...
Click to collapse
I've never heard of that happening. I would try reflashing the rom and kernel then letting that boot alone. If that boots then go back and flash the fix. Also just to make sure, wipe your data, cache, system, and dalvik before flashing everything
Hey red, sorry for the late reply, I just got out of work, but to update you on my issue, I went to ok1 stock it I didn't wipe data and cache stuff etc. I finally received did it and I have phone calls and data. When I sms it takes forever to send, like 7 minutes to be exact, I know this by texting my wife and seeing how long it takes. It does eventually send the text, but also I tried to send mms and that does NOT send? I'm not sure why? I did the mobile setup the way you said in the beginning. Then I had to flash the mod afterwards because I was not able to send sms. Afterwards I decided to turn off mobile data for a minute to see if it helped but it was the same. I also tried turning mobile data off and rebooting and turned it back on but still no luck. Is there anything else you suggest I try? I greatly appreciate your work!
divineazn716 said:
Hey red, sorry for the late reply, I just got out of work, but to update you on my issue, I went to ok1 stock it I didn't wipe data and cache stuff etc. I finally received did it and I have phone calls and data. When I sms it takes forever to send, like 7 minutes to be exact, I know this by texting my wife and seeing how long it takes. It does eventually send the text, but also I tried to send mms and that does NOT send? I'm not sure why? I did the mobile setup the way you said in the beginning. Then I had to flash the mod afterwards because I was not able to send sms. Afterwards I decided to turn off mobile data for a minute to see if it helped but it was the same. I also tried turning mobile data off and rebooting and turned it back on but still no luck. Is there anything else you suggest I try? I greatly appreciate your work!
Click to expand...
Click to collapse
are you using the stock messaging app? If so then try a third party like google messenger. For OK1 did you flash both baseband and firmware? Also are you using KLPFL data fix for the second fix flash?
Yes I tried the stock and then I downloaded the Google messenger app. Was Dr kreton rom suppose to already have the Google messenger? Yes I flashed ok1 full. I didn't do it separately, I have a tar file from back then to flash it full. Should all this information be correct?
redxblood85 said:
Yeah you gotta be on OK1, any marshmallow bootloader will cause the phone to not boot. Once it's set you can try flashing back to PE1. I ran the rom with Beast mode kernel, and PC1 and it worked once it was set up. But yeah for initial set up you need to be on OK1
Click to expand...
Click to collapse
ok i was on 6.0.1 PE1 and then i turned off my phone and flashed OK1 baseband and firmware then i flashed twrp recovery and then this rom etc but my phone is not booting up it is stuck at samsung logo... now what?
n70shan said:
ok i wan on 6.0.1 PE1 and then i turned off my phone and flashed OK1 baseband and firmware then i flashed twrp recovery and then this rom etc but my phone is not booting up it is stuck at samsung logo... now what?
Click to expand...
Click to collapse
Hey I ran into that problem too, after you went back to the OK1, did you wipe as stated before you flashed the rom? make sure you wipe first or else you'll have problems.
divineazn716 said:
Hey I ran into that problem too, after you went back to the OK1, did you wipe as stated before you flashed the rom? make sure you wipe first or else you'll have problems.
Click to expand...
Click to collapse
yes when i installed twrp i first wiped system, data, cache etc and then installed rom but my phone is stuck at samsung... now what should i do? i have to odin back PE1 to make my phone alive for now
n70shan said:
yes when i installed twrp i first wiped system, data, cache etc and then installed rom but my phone is stuck at samsung... now what should i do? i have to odin back PE1 to make my phone alive for now
Click to expand...
Click to collapse
Did you try to ODIN OK1 again? after you ODIN OK1 again let it run and see if it boots up with stock OK1. If it doesnt and it keeps bootlooping try going to wipe the usual and THEN ODIN OK1. I had to try so many things to figure it out, isnt it fun? lol even though it takes up hours of your day.... =/
n70shan said:
yes when i installed twrp i first wiped system, data, cache etc and then installed rom but my phone is stuck at samsung... now what should i do? i have to odin back PE1 to make my phone alive for now
Click to expand...
Click to collapse
i think this is issue with downgrading from PE1 to OK1 but on contrary they are saying this is how it works... i m confused now... @dr.ketan can confirm
---------- Post added at 05:51 PM ---------- Previous post was at 05:25 PM ----------
divineazn716 said:
Did you try to ODIN OK1 again? after you ODIN OK1 again let it run and see if it boots up with stock OK1. If it doesnt and it keeps bootlooping try going to wipe the usual and THEN ODIN OK1. I had to try so many things to figure it out, isnt it fun? lol even though it takes up hours of your day.... =/
Click to expand...
Click to collapse
ok i tried again to wipe everything then flash rom , kernel , fixes and then powered off my phone and flashed OK1 baseband and firmware but still stuck at samsung logo, nothing is working
FYI.... Sprint N4 User(s): You need to be in OK1 or older BL/FW (LP). You can't be on MM BL/FW it will give you bootloop. You can Odin the BL/FW (getting from Freeza in Dev Thread).
1. Wipe everything Except Internal & External SD
2. Flash Rom
3. Flash Data Fix ( Verizon V2 - One I posted which I edited the APN - (All credit go LouForgiveNo)) Don't ask me but that is the only thing I found to work perfectly for our Sprint Phone
4. Flash Kernel ( Vitamin-H, AEL 10.3 (somehow is not really stable), Nameless MM (in N4 Snapdragon thread under the rom, 2 post), Freeza Beasmode (lost Wifi))
5. Do you Normal Setup
6. After complete go to Setting -> Mobile Network -> Network Mode ( Select LTE/CMDA (MUST). Then Access Point Names and select LTE - SPRINT test IPS (last one on the list)
7. Reboot.. Test mms and sms by sending it to yourself. It will take a little bit to go but once it go, it will work find afterward
8. Option - The network has as Roaming Indicator Off... If you want to say Sprint, You would need to flash eri.xml file ( I found this on the web, I only edit to match Sprint. I'm not taking any credit on this.. don't remember who credit too).. User @JWnSC is the one who found the fix.
n70shan said:
yes when i installed twrp i first wiped system, data, cache etc and then installed rom but my phone is stuck at samsung... now what should i do? i have to odin back PE1 to make my phone alive for now
Click to expand...
Click to collapse
Okay try flashing stock OK1, let it get to initial set up screen. Then flash twrp, wipe dalvik, system, data, and cache, then flash the rom, kernel, verizon v2 fix. See if it boots.
Ok I got it all working. These are the steps I took.
Odin ok1 if you haven't and let it boot up so you know it's working
Next after you have twrp installed,
Wipe everything except internal and external so
I wiped 3 times and then factory reset 3 times. Sorry just a habit.
Next I installed the Dr kreton rom
Next I installed the @KLPFL mod data fix he adjusted.
Next I installed vitamin h
Then I rebooted.
I didn't install supersu yet like @KLPFL directed.
I let it boot and put in the information.
When the Dr kreton window fix popped up I just ignored it for now and went to do what @KLPFL said and made sure his access points that he created at the bottom was clicked.
Then made sure to change from global to the Lte/CDMA.
Then I rebooted after the searching lte/CDMA popped up briefly.
After it rebooted I tested everything and it worked fine. Thank you guys for us support!
Oh yea I installed supersu after I made sure everything was connected and then installed Dr kreton fix.
divineazn716 said:
Ok I got it all working. These are the steps I took.
Odin ok1 if you haven't and let it boot up so you know it's working
Next after you have twrp installed,
Wipe everything except internal and external so
I wiped 3 times and then factory reset 3 times. Sorry just a habit.
Next I installed the Dr kreton rom
Next I installed the @KLPFL mod data fix he adjusted.
Next I installed vitamin h
Then I rebooted.
I didn't install supersu yet like @KLPFL directed.
I let it boot and put in the information.
When the Dr kreton window fix popped up I just ignored it for now and went to do what @KLPFL said and made sure his access points that he created at the bottom was clicked.
Then made sure to change from global to the Lte/CDMA.
Then I rebooted after the searching lte/CDMA popped up briefly.
After it rebooted I tested everything and it worked fine. Thank you guys for us support!
Oh yea I installed supersu after I made sure everything was connected and then installed Dr kreton fix.
Click to expand...
Click to collapse
Glad you got it to work.. The only reason I said flash supersu is because sometime you don't get root and you can't apply the fix on your initial bootup.
Hello, anyone using this rom on sprint?
http://forum.xda-developers.com/showthread.php?t=3374171
Sent from my SM-N920P using XDA-Developers mobile app
KLPFL said:
FYI.... Sprint N4 User(s): ...
6. After complete go to Setting -> Mobile Network -> Network Mode ( Select LTE/CMDA (MUST). Then Access Point Names and select LTE - SPRINT test IPS (last one on the list)
Click to expand...
Click to collapse
I followed the instructions in the OP and reference your procedure here. Everything seems to be working, except I cannot get mobile data. I don't see the APN "LTE - SPRINT test IPS".
I do see the APN I configured from Step 5 in the OP.
Could I have missed something obvious? On OK1 bl and fw.
Thanks!
mike
Ok I am having some serious issues as of late, I am far from an Android expert but have been using and rooting them since Android started, and I am also a Linux user. So as stated in the subject I have been getting these issues (not always together).
Recovery will disappear after a normal reboot.
Root will disappear after a normal reboot.
WiFi is "broken" after a normal reboot (is disabled, and can't be enabled).
My status bar disappears.
This has happened across a few different roms, but my main is Team OctOs Oct-N. This is making no sense to me at all. These things will happen after a ROM has already been setup and working for a time, that is what has me scratching my head. The only thing I can think of is some system has changed in the Pixel XL ROMs that I don't know about or something. I always start from a fresh phone, flashing google images, installing the rom the proper way, I always follow the devs install procedure for the most part (depending on the ROM) it is flash rom, flash vendor, flash twrp, reboot into twrp, flash gapps. Everything goes good it runs fine, and then some time after, sometimes a few days later, sometimes a few hours later, one or a combo of the issues listed above happen. I though maybe there was an issue with the actual rom. So i decided to try 1 or 2 other roms but some issue still arrives. Also when twrp wont boot (because it apparently disappeared) I reinstall it properly, and one would think I would be able to boot back into the existing system, but it don't, it always boots right back into twrp.
I am at a complete loss and the only thing I can think of is something has changed with the Pixel system that I am unaware of. Any info would be great I know that this is not a good description on what is actually happening but that's it I have no idea at all. Have a great day and thanks.
I have found that to get TWRP to stick I have to flash the zip and whatever else I'm flashing, then boot into my rom, then boot back into fastboot TWRP and flash the TWRP zip again, then boot back into the rom.
Root is tricky on this phone. Nobody can really answer what's going on there without knowing what month bootloader you are using, what app and what version of the app you are trying to use to root.
The other problems really sound Rom related. If you want to go from a truly fresh start with no chance of any corruption on either partition you might want to run flash-all.bat of the Google factory image separately to partition a and then to partition b. That cleared up problems for me in the past but I'm not sure why.
You might also consider running stock and seeing if the WiFi or status bar problems persist.
xxxtncxxx said:
Ok I am having some serious issues as of late, I am far from an Android expert but have been using and rooting them since Android started, and I am also a Linux user. So as stated in the subject I have been getting these issues (not always together).
Recovery will disappear after a normal reboot.
Root will disappear after a normal reboot.
WiFi is "broken" after a normal reboot (is disabled, and can't be enabled).
My status bar disappears.
This has happened across a few different roms, but my main is Team OctOs Oct-N. This is making no sense to me at all. These things will happen after a ROM has already been setup and working for a time, that is what has me scratching my head. The only thing I can think of is some system has changed in the Pixel XL ROMs that I don't know about or something. I always start from a fresh phone, flashing google images, installing the rom the proper way, I always follow the devs install procedure for the most part (depending on the ROM) it is flash rom, flash vendor, flash twrp, reboot into twrp, flash gapps. Everything goes good it runs fine, and then some time after, sometimes a few days later, sometimes a few hours later, one or a combo of the issues listed above happen. I though maybe there was an issue with the actual rom. So i decided to try 1 or 2 other roms but some issue still arrives. Also when twrp wont boot (because it apparently disappeared) I reinstall it properly, and one would think I would be able to boot back into the existing system, but it don't, it always boots right back into twrp.
I am at a complete loss and the only thing I can think of is something has changed with the Pixel system that I am unaware of. Any info would be great I know that this is not a good description on what is actually happening but that's it I have no idea at all. Have a great day and thanks.
Click to expand...
Click to collapse
This has been a real challenge with this phone (but I'm enjoying it). Anyway, the way I got a good stable set up is flashing the factory image to both slots (a/b), then adb/fastboot to twrp.img and flash ROM, then boot up. Then again the twrp.img and flash the twrp.zip and boot up. Then do the root and boot up , then go back and do the kernel (since it's EX and I want the gestures, I boot it up rooted before I flash EX). This works for me although I'm using Pure Nexus ROM. Hope this helps you, looks similar to what was posted by jhs39.
Hi,
I flashed TWRP on my unlocked Redmi Note 8T with MIUI Global 12.5.5. Everything was great until I rebooted it and saw Bluetooth error which pops every time I try to turn Bluetooth on or just randomly during usage of the device. I also tried to re-flas TWRP with Orange fox but it unfortunatelly did not help. Now I have no idea what to do but there are also some other people with this problem (for example:
https://www.reddit.com/r/Xiaomi/comments/y9zsak
).
Does anybody know any solution? Thanks!
Btw Orange fox is for ginko devices, I did not find version for willow
I had the exact same problem when I tried to root my stock rom in ginkgo. I was getting a lot of "app keeps stopping" pop ups, and that also included bt. My bt was completely broken until I changed rom. Also I'm guessing this had happened when I had rooted my phone with magisk, not by flashing recovery itself. Perhaps you could try to uninstall magsik, and see it it resolves the issue for you. If that would be the case, then you would have found your problem, and maybe you can flash a custom rom to safely root your phone.
Thanks for reply, but i did not have magisk flashed on my phone. I only had installed the app, prepared apk file and did nothing in TWRP (Orange fox) , just flashed a recovery with my PC, checked that it is working and rebooted device. Anyway I tried to do it only because of acces to NFC and Gpay which is now blocked.
As you also said, I would like to try custom rom (like LineageOS) because it seems like bad idea to have a stock room on an unlocked phone. Only the problem is how to backup data like data from apps, games etc.
So now it tried one of my ideas, which was to install Magisk (root) and uninstall it but it also did not help (I expected that)
vasik006 said:
Thanks for reply, but i did not have magisk flashed on my phone. I only had installed the app, prepared apk file and did nothing in TWRP (Orange fox) , just flashed a recovery with my PC, checked that it is working and rebooted device. Anyway I tried to do it only because of acces to NFC and Gpay which is now blocked.
As you also said, I would like to try custom rom (like LineageOS) because it seems like bad idea to have a stock room on an unlocked phone. Only the problem is how to backup data like data from apps, games etc.
Click to expand...
Click to collapse
To backup data simply copy your personal files in pc or sdcard. And to backup data in apps, take back-up of only those apps and where you need to backup. Don't take a complete backup using some app. That consumes a lot of space and make the newly rom feel "not so new". Most apps don't require you to take back-up offline these days. I usually backup only my personal files before flashing rom.
Yeah, that's true. But don't you know how to backup data from these "offline" apps? I was trying to solve this also before unpocking bootloader like a year ago but unsuccessfuly.
Also, which rom should I choose? I'm deciding between LineageOS and Pixel experience.
So I have LOS installed but I can´t install other zip files (like Google apps). Im only getting error: signature verification failed while. Im using LOS recovery so where is the problem?
Solved it!
Hey @vasik006 ! I know this is very late and you might have found the solution yourself, but I found the solution to this problem. Since yesterday I was trying to root my ginkgo with twrp, using magisk delta and had exact same issue. Joyose and bluetooth keeps stopping, and don't work. Simply factory reset ( I also formatted data) in twrp, and in next boot bluetooth should work. Then you can simply install the magisk apk and let it do its thing. No need to flash again since it has already made changes to boot file that can't be overriden by resetting phone.
Thanks, this might help someone else with this problem. I have already formatted my phone, installed Lineage OS and everything is ok
For me, the problem with BT and Joyose occurs only with TWRP v3.7.x. I went back to TWRP v3.6.1_9-0 but now backups are not working.
Jatin Verma x821 said:
Hey @vasik006 ! I know this is very late and you might have found the solution yourself, but I found the solution to this problem. Since yesterday I was trying to root my ginkgo with twrp, using magisk delta and had exact same issue. Joyose and bluetooth keeps stopping, and don't work. Simply factory reset ( I also formatted data) in twrp, and in next boot bluetooth should work. Then you can simply install the magisk apk and let it do its thing. No need to flash again since it has already made changes to boot file that can't be overriden by resetting phone.
Click to expand...
Click to collapse
I have the same problem with the Redmi note 8. Did you unroot first or did the factory reset directly? Tks
ennev said:
I have the same problem with the Redmi note 8. Did you unroot first or did the factory reset directly?
Click to expand...
Click to collapse
no need to unroot. simple factory reset the device and you're done.
Jatin Verma x821 said:
To backup data simply copy your personal files in pc or sdcard. And to backup data in apps, take back-up of only those apps and where you need to backup. Don't take a complete backup using some app. That consumes a lot of space and make the newly rom feel "not so new". Most apps don't require you to take back-up offline these days. I usually backup only my personal files before flashing rom.
Click to expand...
Click to collapse
TWRP is invaluable for backing up the system before making changes like theming etc. and I can take a TWRP backup to any of my (all the same) devices and restore the whole thing in just a few minutes. So convenient! I really couldn't imagine life without TWRP. TWRP enables me to clone my device in case of hardware failure. All my settings and all my apps and all my custom configurations which would otherwise take hours/days to setup - BAM! Presto! on the new device and running perfectly.
TWRP + NeoBackup are essential. TWRP as described, and NeoBackup to roll back breaking updates to apps when devs butcher them, break them, and/or just remove really useful features. I also disconnect apps that get ruined by an update from the Play Store so they don't keep coming up when I check for updates.
Alpha_Geek1 said:
TWRP is invaluable for backing up the system before making changes like theming etc. and I can take a TWRP backup to any of my (all the same) devices and restore the whole thing in just a few minutes. So convenient! I really couldn't imagine life without TWRP. TWRP enables me to clone my device in case of hardware failure. All my settings and all my apps and all my custom configurations which would otherwise take hours/days to setup - BAM! Presto! on the new device and running perfectly.
TWRP + NeoBackup are essential. TWRP as described, and NeoBackup to roll back breaking updates to apps when devs butcher them, break them, and/or just remove really useful features. I also disconnect apps that get ruined by an update from the Play Store so they don't keep coming up when I check for updates.
Click to expand...
Click to collapse
I would advise you to read the posts again. They were asking about how to take backup of "personal apps" which twrp can't do, and if they are changing ROM then twrp backup won't be of any use to them. Therefore, whatever you're trying to tell here doesn't really help the discussion.
Jatin Verma x821 said:
I would advise you to read the posts again. They were asking about how to take backup of "personal apps" which twrp can't do, and if they are changing ROM then twrp backup won't be of any use to them. Therefore, whatever you're trying to tell here doesn't really help the discussion.
Click to expand...
Click to collapse
TWRP does backup personal apps and their settings. Once you restore a TWRP backup, you have everything back except media files - images, videos, documents, etc. The launcher icons, the apps, the system settings - everything is a perfect clone which you can restore on a new device (same model, of course).
I actually came across this thread searching to see if others had a problem where merely flashing TWRP caused Bluetooth to crash (and Atmos).
Use OrangeFox
is there anyone use BT-fix-for-PE-20190618.zip to fix this problem ?
I'm on an ROG Phone II with the same issue.
The "fix" is to wipe in TWRP and install Magisk BEFORE you leave for your first boot and NEVER come back to TWRP as the issue will return the second recovery is booted.
s3rv said:
For me, the problem with BT and Joyose occurs only with TWRP v3.7.x. I went back to TWRP v3.6.1_9-0 but now backups are not working.
Click to expand...
Click to collapse
From what I can tell, this is correct. 3.6_XX-X allows me to come and go from TWRP as much as I please without incurring the bug, however, I haven't tested backup though I can't see a reason why they wouldn't work.
Are these existing backups that aren't working or the whole backup function in general?
starkshadow said:
is there anyone use BT-fix-for-PE-20190618.zip to fix this problem ?
Click to expand...
Click to collapse
It looks like this guy didn't have any luck with it either. It may be divice specific
Dredead said:
I'm on an ROG Phone II with the same issue.
The "fix" is to wipe in TWRP and install Magisk BEFORE you leave for your first boot and NEVER come back to TWRP as the issue will return the second recovery is booted.
From what I can tell, this is correct. 3.6_XX-X allows me to come and go from TWRP as much as I please without incurring the bug, however, I haven't tested backup though I can't see a reason why they wouldn't work.
Are these existing backups that aren't working or the whole backup function in general?
It looks like this guy didn't have any luck with it either. It may be divice specific
Click to expand...
Click to collapse
amazing, I have do nothing, just reboot my device, and yesterday the bluetooth also has problem, but today I open bluetooth, it is no problem. I'm still confused about that.
starkshadow said:
amazing, I have do nothing, just reboot my device, and yesterday the bluetooth also has problem, but today I open bluetooth, it is no problem. I'm still confused about that.
Click to expand...
Click to collapse
It seems to be a twrp issue. What version do you have? And what version of magisk do you have?
I have recently flashed miui 12 (android 10) after bricking the phone using qtel. I noticed the Bluetooth problem last week and didn't find a fix. I have twrp 3.6.2 and magisk 25.1. I had twrp 3.7.1 but if failed to decrypt data using pattern so I rolled back to 3.6.2. And I thought that magisk had to do with the Bluetooth problem so I rolled back to 25.1 from 26.
I still can't use the Bluetooth, and I don't have time to reset the phone, I just finished restoring everything
I CAN CONFIRM
go back to the previous twrp 3.6.2 version + wipe factory reset or simply format data solve sucesfuly solve installation issue of Magisk 26.1 or Magisk Delta 25210
Olfason said:
I CAN CONFIRM
go back to the previous twrp 3.6.2 version + wipe factory reset or simply format data solve sucesfuly solve installation issue of Magisk 26.1 or Magisk Delta 25210
Click to expand...
Click to collapse
I can't afford resetting my phone right now , don't have enough time. I'll let it like that for some months.
Edit : I have miui 12.0.6 installed (android 10) and I'm not planning to upgrade since I have much better battery life (even better than every mod I tried). I wander if I flash miui rom from recovery can fix it?
Edit 2: flashing the rom from recovery didn't fix it