Related
I have a stock 2.1 defy with the 2.51 rom (i think). all the mod i did was root the phone using super one click, the phone ran fine for a few months until i experimented with titanium backup and deleted google talk etc. i found out that (too late)doing this would cause the android market to stop downloading and updating my apps. To remedy my situation i tried installing google talk service.apk back to system apps. first by copying the file to my sd card and pushing it to the system file using terminal emulator. after rebooting my phone is now bootlooping. i tried removing the battery and just after i insert it it would go immediately into the bootloop phase. tried using recovery (volume down+power) and wipe cache and reset, still no go. last resort i tried is after wiping i tried installing cm7 but the installation was immediately aborted. please help, right now im close to tears, i didn't know that it was this hard to mod a defy. my previous phone was a wildfire and modding it was pretty easy.
What happens when you turn the phone on? Does it start in the bootloader? Is it stuck in Motorola Logo?
Try to wipe data/cache again and see what happens.
As well you might want to go ahead and download all tools needed to flash an sbf. Because if worst comes to worst your going to have to flash one
Sent from my Life Proof Defy on CM7
juanplopes said:
What happens when you turn the phone on? Does it start in the bootloader? Is it stuck in Motorola Logo?
Click to expand...
Click to collapse
the phone turns itslef on automatically when i insert the battery, white moto logo first then bootloops in motoblur animation.i can go into bootloader mode by pressing up and power before inserting the battery. i just wished i hadn't played around with titanium backup. i already downloaded the necessary files to flash a new firmware. hope i learn to do it properly.
javi422 said:
Try to wipe data/cache again and see what happens.
As well you might want to go ahead and download all tools needed to flash an sbf. Because if worst comes to worst your going to have to flash one
Sent from my Life Proof Defy on CM7
Click to expand...
Click to collapse
i tried wiping the cache/data numerous times under recovery mode to no avail. now im crossing my fingers that my battery isn't that drained for me to flash a new firmware.
Try to wipe data/cache again and see what happens.
As well you might want to go ahead and download all tools needed to flash an sbf. Because if worst comes to worst your going to have to flash one
You can also do the battery hack/trick
Sent from my Life Proof Defy on CM7
Click to expand...
Click to collapse
i tried wiping the cache/data numerous times under recovery mode to no avail. now im crossing my fingers that my battery isn't that drained for me to flash a new firmware.
Click to expand...
Click to collapse
Sent from my Life Proof Defy on CM7
Hi I have the same problem,I just tried to flash the Barebone 1.5 ROM.
My Defy was stock,I just root it and made a backup with clockmod before I did as discribed here:
Installing (Rom wipes data/cache partitions)
1. Copy Barbones to sdcard: Barebones_15-signed.zip.
2. Boot into recovery (make a backup ?) and restore nandroid: 3.4.2_177-Nand.NORDIC_DEBLUR.zip.
3. Still in recovery, select install zip from sdcard -> choose zip from sdcard -> Barebones_15-signed.zip.
4. Reboot system, first boot will take time as it builds the dalvik cache; wait for the background to load, and enjoy Barebones.
- Use Easy Installer to install any apk's you feel are missing.
- Removed.Stock.Apps.zip
-- Removed Apps Must Be Copied To /system/app Manually - Remember To Set Permissions & Reboot
To downgrade back to Eclair; just flash the Eclair sbf you where using beforehand; thats it.
Click to expand...
Click to collapse
after Reboot it just shows Motorola,I can access Recovery Menu stock one and custom,tried wipe restore factory settings and wipe cache but nothing helped!
What version where you coming from ? Eclair or Froyo ?
Btw factory reset and wiping the cache doesnt do anything in these situations.
Did you restore the Nandroid provided ?
Also cant lie only thing I did not test was coming straight from an Eclair build.
I used the Korean Froyo sbf as a starting point; but I'm testing it now.
Got it alive again with this steps.
No wonder why u're stuck on motorola logo.
Let me break it down for you.
Make sure you have motodrivers installed or install them here.
And install the RSD Lite too Here
Turn off your phone, hit the power+volume up together.
Wait till u're in the bootloader.
Open the RSD Lite, u phone should be detected so u click on "..." select the .sbf u downloaded from here
And flash it.
Wait till is over, and your phone should be good again.
Click to expand...
Click to collapse
I used this .sbf
But I still don't know what went wrong,I did exactly as discribed in the TUT I postetd above!?
Well if you flashed that sbf you wont be able to downgrade back to Eclair anymore.
However; yes doing that will fix it.
Is it not good that I flashed this .sbf? I got the phone just 2 days ago I think it already had the newest firmware etc.!?
EDIT: But something is wrong with my Wlan connection it is very slow and always loses connection
I doubt it came with Froyo seeing as they are all leaked builds.
http://forum.xda-developers.com/showthread.php?t=966537 <- Read up
Just means you cant go back to Eclair.
Ok so you wifi is slow ? Are you even using my rom now; because you flashed 3.4.2_155-Stock.CEE_DEBLUR.sbf.
I cant see your phone so you have to tell me what your using.
Yes I just flashed the sbf nothing else,and before I just did what I read in the instructions from the Barebone 1.5 Thread.
1. Copy Barbones to sdcard: Barebones_15-signed.zip.
2. Boot into recovery (make a backup ?) and restore nandroid: 3.4.2_177-Nand.NORDIC_DEBLUR.zip.
3. Still in recovery, select install zip from sdcard -> choose zip from sdcard -> Barebones_15-signed.zip.
4. Reboot system, first boot will take time as it builds the dalvik cache; wait for the background to load, and enjoy Barebones.
- Use Easy Installer to install any apk's you feel are missing.
- Removed.Stock.Apps.zip
-- Removed Apps Must Be Copied To /system/app Manually - Remember To Set Permissions & Reboot
Click to expand...
Click to collapse
I tried this sbf before 3.4.3_11-Stock.UKTmobile_BLUR but it always failed thats why I tried the other one
So your not using my rom now - the sbf overwrites everything.
Ok sorry Im a noob^^ I just wanted to have all this blur stuff removed etc and your rom seems just perfect for me.
I have problems now with the phone and I really wished I would never had tried this.
I cant boot into recovery mode anymore with clockworkmod, I rooted my phone again installed clockwork but the screen stays black after the Motorola Screen came up when I try to make a recovery boot with clockwork.
cause I wanted to restore the backup I did with clockworkmod before I messed it all up,would that make my phone like it was before or not!?
I doubt you will be able to get back to your backup simply cause I dont think its Froyo.
So do this:
1. Boot into bootloader (power + volume up).
2. Flash 3.4.2_155-Stock.CEE_DEBLUR.sbf again.
3. While its rebooting after flashing hold volume down to goto stock recovery.
4. Do a factory reset.
5. Root your device using superoneclick http://forum.xda-developers.com/showthread.php?t=913709
6. Reboot.
7. Install 2nd Init Recovery http://forum.xda-developers.com/showthread.php?t=1032212
8. Reboot twice (to finish installing recovery).
9. Reboot into recovery - wait for blue led then hit volume down.
10. At this point you can try to restore your backup or flash a rom of your choice.
If you try your backup and it does not work you will need to start this process over.
Ok thank you so much fritolays for your help! I will try this tomorrow and post back if I had success or not!
greetz!
EDIT: Couldn't wait to try it and it worked! I took the risk and tried to install your rom again (restoring my backup didn't worked anyways 'cause clockworkmod didn't find the backup but it was still in the same folder it got stored before) works like charm as far as I could test it. But now I really have to go to sleep!
Big thanks again fritolays without your quick help I would still try to get my Defy to work without any success! and THANKS! for this great rom!!!
EDIT2: I don't know why but I have problems with the phone since yesterday when I first flashed another ROM,I always have Network Connection Problems now! I can't download anything from the market if I get to the market! 'cause normally it says no network connection! It worked fine for like 20minutes after I got it to work with ur method u told me above then it suddenly took very very long to download an app. Never had these Problems before,I also have very bad Phone Signal and most of the Time I can just make Emergency Calls and I turned Internet Connection OFF for mobile network (like I did before when it was stock) but sometimes I still can go online with Wlan turned off so this is really ****ed up 'cause I have no internet plan with my mobile phone!
But with your ROM the phone is really flying,I did a Benchmark Test before and got 1100 Score and by just putting your ROM on my Defy without any overclocking or something like that I got 1275 Score!
EDIT3 I found the direction it was clockworkmod/backup/ now
I did a wipe factory reset and a cache wipe and now restoring it I really hope everything is like it was before all this!
Ok this got me to the Bootloop Problem again so I did again all the steps u told me and instead of restoring ur ROM I restored my backup wich was now in the right direction,but it is also ended up in Bootloop!
EDIT4 If I try all this with ur ROM it works,is it because of the Froyo .sbf I flashed that I can't get my backup working!?
I get this Error Message after my phone booted with ur ROM maybe that is one of the Problems I have? "Sorry,the process android.process.media got suddenly closed try it again" I had to translate it so maybe the message is a bit different in english but thats what it says generally.
So everything worked great again,I go into Market to download TitaniumBackup (like I always did) then as always I apply the new Busybox Install TitaniumBackup suggests everytime I start it and the Wifi gets slow already by downloading Busybox. Then I tried to go to the Market again and Network Error, I get the feeling it has something to do with this app or the Busybox installation TitaniumBackup is doing!?
I don't know what it is but it alwys messes something in my phone up and I get Wifi Probs!??
EDIT5 I tried another ROM now "xd1 ** new ** ver 1.2" and everything worked fine! I downloaded Quadrant and a Antivirus App just to test it and everything was alright so I tried TitaniumBackup again (the Free Version as always) and guess what the download got fast till 42% then stuck and now I can't download anything again from Market it is very slow and then the downloads got canceled! wtf is wrong with this app!? I need it for all my Apps 'cause I did a backup with this app but since I flash custom ROMS it always does this bull**** when I download it from market!?
update..got my defy unbricked by following Higgsy's step by step method. installed a 2.51 SEA sbf in the process. love the phone without blur. now im thinking of upgrading to a froyo rom, which do you guys think is the best? based from reading the posts here i'm more confused than ever. sbf's here and 2nd init that??? not to mention a fixed sbf?? i really can't understand these terms and the more i read the more i got confused. Could you guys help me in laymans terms the proper process for upgrading to froyo and which rom is you think is best??
my galaxy grand continue to reboot, i even flash the stock 4.1.2 and 4.2.2 firmware but still the phone reboots, it only reaches the wifi setup, then it restarts, please help.
chrowley said:
my galaxy grand continue to reboot, i even flash the stock 4.1.2 and 4.2.2 firmware but still the phone reboots, it only reaches the wifi setup, then it restarts, please help.
Click to expand...
Click to collapse
The information provided by you is not sufficient.There are some points i would like to know about.
Have u rooted your device?
Are you flashing through ODIN?
ROM version?
Did you make data wipe/ cache wipe before flashing over a previous firmware?
There are many threads associated with this.So please take a look over that.If you don't find answer then we are here to help you
ashwin77sgg said:
The information provided by you is not sufficient.There are some points i would like to know about.
Have u rooted your device?
Are you flashing through ODIN?
ROM version?
Did you make data wipe/ cache wipe before flashing over a previous firmware?
There are many threads associated with this.So please take a look over that.If you don't find answer then we are here to help you
Click to expand...
Click to collapse
yes sir rooted, i flash the firmware through odin, then i figured out that i have a backup so i restore it and its a yes it starts, , but the problem is sometimes it reboots and the screen is blinking sometimes, any solution for this sir? thanks in advance
chrowley said:
yes sir rooted, i flash the firmware through odin, then i figured out that i have a backup so i restore it and its a yes it starts, , but the problem is sometimes it reboots and the screen is blinking sometimes, any solution for this sir? thanks in advance
Click to expand...
Click to collapse
Thanks for Calling me "Sir". But seriously no need to say it. Say it to real developers.
Now coming to the topic,
For your information,keep in mind that when u flash the Official firmware through ODIN, You loose the root access.
Don't restore any backup. Just flash through ODIN. After flashing Wipe Cache and Data wipe is recommended too.
To gain the root access again you need to flash recovery from ODIN.
Other members looking at this this thread please correct me if i am wrong .I still not getting which backup the guy is talking about.
ashwin77sgg said:
Thanks for Calling me "Sir". But seriously no need to say it. Say it to real developers.
Now coming to the topic,
For your information,keep in mind that when u flash the Official firmware through ODIN, You loose the root access.
Don't restore any backup. Just flash through ODIN. After flashing Wipe Cache and Data wipe is recommended too.
To gain the root access again you need to flash recovery from ODIN.
Other members looking at this this thread please correct me if i am wrong .I still not getting which backup the guy is talking about.
Click to expand...
Click to collapse
oh sorry sir, i'll make it clear, my last firmware is 4.2.2 and my rom is GENNEXT, but when i encounter the problem, i tried to go back and flash the 4.1.2 stock firmware, then later i discovered that i have a backup from my previous rom(GENNEXT running 4.2.2 firmware) so i flash again the 4.2.2 stock firmware and flash the philz touch recovery, wipe data/factory reset, wipe cache and wipe dalvik cache then restore the back up, then my phone is restored but theres another problem sometimes the screen blinks and the phone reboots in a few minutes after the startup.
chrowley said:
oh sorry sir, i'll make it clear, my last firmware is 4.2.2 and my rom is GENNEXT, but when i encounter the problem, i tried to go back and flash the 4.1.2 stock firmware, then later i discovered that i have a backup from my previous rom(GENNEXT running 4.2.2 firmware) so i flash again the 4.2.2 stock firmware and flash the philz touch recovery, wipe data/factory reset, wipe cache and wipe dalvik cache then restore the back up, then my phone is restored but theres another problem sometimes the screen blinks and the phone reboots in a few minutes after the startup.
Click to expand...
Click to collapse
OK. Then it may be the problem with your GENNXT ROM cause the problem occured after restoring Backup.Try the fresh install of latest build of GENNXT rom.
ashwin77sgg said:
OK. Then it may be the problem with your GENNXT ROM cause the problem occured after restoring Backup.Try the fresh install of latest build of GENNXT rom.
Click to expand...
Click to collapse
i already tried it sir but it didnt solve the problem, it passes the setup but after a few minutes the phone reboots.
You might want to try one of the AOSP-based ROMs (CM11/Slimkat/Carbon/Omni/ProBAM) and see if it fixes the issue. If it still reboots even after installing one of those ROMs, then you probably has a faulty hardware. If it stops rebooting,then you probably has a corrupted installation of stock firmware...
Faulty hardware = get it to a service center, but be prepared to pay some bucks because you have already lost your warranty...
Corrupted stock firmware = try to flash the firmware again via Odin but DON'T RESTORE ANY BACKUP. If it still reboots, redownload the firmware package and reflash.
I'm not an expert, but I figured that your phone is already unusable by constant rebooting... let's just solve it by trial and error.
naufalhadyan said:
You might want to try one of the AOSP-based ROMs (CM11/Slimkat/Carbon/Omni/ProBAM) and see if it fixes the issue. If it still reboots even after installing one of those ROMs, then you probably has a faulty hardware. If it stops rebooting,then you probably has a corrupted installation of stock firmware...
Faulty hardware = get it to a service center, but be prepared to pay some bucks because you have already lost your warranty...
Corrupted stock firmware = try to flash the firmware again via Odin but DON'T RESTORE ANY BACKUP. If it still reboots, redownload the firmware package and reflash.
I'm not an expert, but I figured that your phone is already unusable by constant rebooting... let's just solve it by trial and error.
Click to expand...
Click to collapse
This is probably the best explained and most direct definition of what to do and what may be happening with our ever-rebooting Grands.... Thank you!!!
Had to create an account to thanks naufalhadyan
I was running on LineAgeOS 13.0 for a while until yesterday, when I went to install some random play store app and it crashed then went on a infinite rollercoaster with absolutely no fun making loops every time it got of the boot animation, did a factory reset, on the 2nd or 3rd app it crashed and looped, flashed another .zip with the rom, same, installed an RRemix on the same version (I like the 6) and when installing another random playstore it crashed the same way, now i'm on a AOSP 6.0 flashed from the recovery and so far i've been downloading the entire play store (just for kicks) and its smooth.
I don't use come to this troubleshooting section but on the last 24 hours there were some major bugs regarding endless loops, maybe a play store update came bugging our grand duos'? Is that even possible?
victorsmarotta said:
Had to create an account to thanks naufalhadyan
I was running on LineAgeOS 13.0 for a while until yesterday, when I went to install some random play store app and it crashed then went on a infinite rollercoaster with absolutely no fun making loops every time it got of the boot animation, did a factory reset, on the 2nd or 3rd app it crashed and looped, flashed another .zip with the rom, same, installed an RRemix on the same version (I like the 6) and when installing another random playstore it crashed the same way, now i'm on a AOSP 6.0 flashed from the recovery and so far i've been downloading the entire play store (just for kicks) and its smooth.
I don't use come to this troubleshooting section but on the last 24 hours there were some major bugs regarding endless loops, maybe a play store update came bugging our grand duos'? Is that even possible?
Click to expand...
Click to collapse
Even iam facing the same issue
phone reboots automatically and doesnt even start... infinite bootloop. Was working fine and suddenly this issue came up from nowhere(past 2 weeks) ..
Iam using Resurrection rom 5.7.4 (Marshmallow)
Damn I was on AICP 11, when this exact strange bootloop problem occurred for no rhyme and reason. I know the hardware is fine, the issue arises from installing apps from playstore, the moment it goes beyond a certain app limit in the device, it will start endless bootloop, I am sure this is Google's doing. Anyways this is not a hardware issue and I know more people will be coming here looking for answer to this issue. I have tried both the opengapps and deltagapps, same behaved this way, it never happened before and lately google have introduced one other app which is google's android instant app that will sit in your device, even though you need it not not. very well google for using our precious internal data to around 500Mb to 1Gb.
formating data partition solves this issue, temporarily but you lose your apps and data.
I had successfully avoided this issue when I stopped installing more apps on my device, It took me 2 tries and I found a perfect balance of 4-5 apps, it came crashing again when I tried installing the 7th app.
I don't know if other ROMs will be able to handle this bug, but I know it's time for me to look for another ROM, I was happy with AICP 11, for more than a year. Sad.
Reading about this issue, I came to know this is prevalent on all CM marshmallow based ROMs. So, going to flash Nougat or kitkat or the stock ROM should probably fix this.
Try a new battery.
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
So...
Last week, my wife's Tab S went into a bootloop. She runs complete stock, we haven't rooted, or anything. There had been a notification about an update, but she hadn't touched it. She'd updated to Lollipop at some point last year, but hadn't applied the absolute latest update. One day last week, she just turned it on, and it started bootlooping.
Because it was so stock, there were no backups, no nandroids, or anything like that. No Custom Recovery. I told her "well, we can just do a factory reset. You'll lose everything, but once we get you back up and running, it'll just re-download everything from the Goog." So we factory reset it. Looked good for a minute, booted into the first screen, enter in your Wi-Fi password, all that. As soon as we got the Wi-Fi password entered, however, it re-booted. And keep rebooting. Bootloop city. No problem. I walked her through (over the phone) using Odin to flash the latest Lollipop firmware. No dice. It appeared to flash successfully, but still bootlooped.
Over the weekend, I tried using Kies to flash the most official firmware I could find. Everything was successful -computer recognized the device, was able to download "direct from the source," as it were, but it got stuck at 69% twice before failing. I read somewhere that one had to run Kies in administrator mode to get it to successfully complete. So I did, and it got past 69%, successfully completing the flash. STILL NO LUCK. STILL WITH THE BOOTLOOPS.
Last night, I realized that I hadn't flashed in Odin using Administrator Mode. Tried it, using latest 5.0.2 (XAR-Cellular South). Flashed successfully, all appeared well. Still bootlooped.
So, I'm stuck. I can get into recovery, I can get into Download Mode, I can successfully flash. I just can't get the darn thing booted.
Thoughts, anyone? Should I try flashing a Custom ROM? How hard is that using Odin? Thanks in advance.
Ok this will take a few tries but here is my method of dealing with this situation
1) Flash stock using Odin
2) AS SOON AS the screen goes blank, start holding Power+Volume Up+Home
3) When recovery boots, release the buttons
4) Use the volume buttons to select "Wipe data/factory reset"
5) Press power to confirm
6) Reboot
If that doesn't work, you may either:
1) (more likely) Installing a ROM will fix the problem
2) (unlikely but possible) You might have worn NAND pages, which I doubt but could cause this behavior.
Nandr0idC0nsumer said:
Ok this will take a few tries but here is my method of dealing with this situation
1) Flash stock using Odin
2) AS SOON AS the screen goes blank, start holding Power+Volume Up+Home
3) When recovery boots, release the buttons
4) Use the volume buttons to select "Wipe data/factory reset"
5) Press power to confirm
6) Reboot
If that doesn't work, you may either:
1) (more likely) Installing a ROM will fix the problem
2) (unlikely but possible) You might have worn NAND pages, which I doubt but could cause this behavior.
Click to expand...
Click to collapse
Thanks, I'll try these steps tonight when I get home, and report back!
All right, here's something interesting. Before I tried your first step, I remembered that the other night, I left it stuck at the Samsung logo -it was just kind of stuck there, and since the behavior was a little different than I'd seen before (not continuous bootlooping), I thought I'd boot into recovery and wipe. I did, I wiped (factory reset), and rebooted. The tablet booted into the first screen, Accessibility/Wi-Fi, blahblah. This was where it usually rebooted. On a hunch, I bypassed entering in my WiFi key. I then bypassed almost everything else (Samsung account, Google account, etc.), expecting that the tablet would reboot at any moment. But I made it to the front apps page, where it shows you the side-launcher, the Magazine-Flipboard thingie, and whatnot. Wi-Fi still not connected, though. I opened up the app drawer, and scrolled around. Looked really good for a moment. I even took a picture with the camera, and viewed it in Gallery! Feeling brave, I thought, "well, maybe it just needed a couple of minutes before firing up the radio." So I went into settings, and inputted my WiFi key. It connected. And rebooted into its bootloop. (getting so tired of that boot-sound).
Went ahead and flashed the most original stock firmware I could find. As always, flashed successfully. As soon as it booted, I made my way to recovery, and wiped, per your instructions. No luck. Bootloop again.
It's something in the WiFi is what I've come to think as a result of the above. Which I don't entirely understand, as I thought the radio got re-flashed with the firmware.
I'm ready to try flashing a Custom Rom. Can I do that through Odin, or should I try and flash TWRP, and do it through there? Will TWRP flash without a working (bootable) OS?
All right. Thanks for your response!
Try this as a test.
First make a full backup of every partition with twrp including the EFS <<IMPORTANT!
Get it booting again without wifi then root the device and delete the EFS folder or delete it in recovery.
Reboot the device and try and enable wifi.
ashyx said:
Try this as a test.
First make a full backup of every partition with twrp including the EFS <<IMPORTANT!
Get it booting again without wifi then root the device and delete the EFS folder or delete it in recovery.
Reboot the device and try and enable wifi.
Click to expand...
Click to collapse
Got TWRP installed. Won't backup. Fails at 16% (system partition, I think). Just powers down to battery indicator in the middle of the backup. Looks like it backs up the EFS, though, since it's the first one. And when I go into TWRP's Restore option, there's a backup there (though I don't dare try and restore it).
Now I have to figure out a way to get the Custom ROM and GAPPS I downloaded onto the tablet without a reliable boot... It's gotten to the front screen a time or two tonight, but starts looping even when I bypass the WiFi setup.
Entered adb/TWRP interface. Tried to push two files, a Custom ROM file, and a GAPPS file. The ROM failed, with some sort of "Error 7," incompatible data, blahblah... Just out of curiosity, I tried to push the GAPPS file, and that failed after about 6%, and the tablet powered off.
I'm running out of ideas.
copied a custom rom to a USB/OTG stick (thumbdrive), and plugged it in. Fired up TWRP, tried to install. Wouldn't. Wouldn't install GAPPS, either. Looks like the only way it wants to flash anything is through ODIN or KIES.
The Latest...
All right...
I remembered that sometimes the TWRP version mattered. When I installed TRWP last night, I installed the latest and greatest, 3.0.2. Last night after I gave up, I remembered that sometimes, the latest and greatest TWRP doesn't install things perfectly. So, this morning, I downloaded TWRP 2.8.6-ish onto the USB/OTG device, and re-flashed the recovery partition. To be honest, I was surprised that TWRP was even able to flash that (but the TWRP image is only like 9.8 MB, so...)...
Got TWRP 2.8.6.0 flashed, and rebooted into TWRP. Immediately decided to try and re-flash the custom ROM that I'd tried unsuccessfully to flash last night, since the thumbdrive was still plugged in. Resurrection Remix Lollipop. Lined up GAPPS in the queue, as well. The ROM *appeared* to flash better than it had in TWRP 3.0.2, but it was sort of hard to see... GAPPS failed, and I was prepared to watch another round of bootloops. It did bootloop, sort of. The RR splash screen appeared, said that it was installing (or preparing) xx out of XX apps. Then, it rebooted. I figured it was doing its bootloop thing. However, it got to the same screen, "installing xx out of XX apps. Except that XX number had gone down, and the xx number had gone up. It repeated this action about 4 times --the last time I saw it reboot, it was "installing 1 out of 2 apps." And then...?
It booted into the RR lockscreen.
Of course, there were no GAPPS. In fact, there are something like only 20 apps total on the tablet. But it appears somewhat stable at the moment. (See picture).
Afraid to try and connect WiFi, afraid that it'll just bootloop.
Speaking of bootloop. At one point, once we got it booted, my wife hit an option in the Settings. LCD Density, I believe. As soon as she hit it (she literally just placed her finger over the 320 default option), the tablet rebooted. No loop, though. Rebooted straight back to the RR lockscreen.
So I appear to have a somewhat stable OS flashed onto the tablet at the moment. No GAPPS, though. No WiFi.
Anybody have a suggestion on where to go from here? I have my doubts as to whether or not I can even back up this configuration.
Sorry about all the updates. I kind of figured that if *anyone* else ever goes through what I'm going through, they'll have some sense of all the different things that can be tried in resurrecting a bricked/bootlooping device. I appreciate everyone's efforts to date -thank you so much, @Lightn1ng and @ashyx.
All right, because I can't leave well enough alone....
I got WiFi up and working. Tablet still stable and working. Wheeeee.... No GAPPS, though.
Downloaded GAPPS, second-smallest package from opengapps- only 128M (5.1 ARM package). Downloaded it in Android, from the tablet! Tried to flash it in TWRP. Failed, tablet rebooted halfway (not even) through. Now it's bootlooping again...
I should've left well enough alone, and waited for someone. Have tried re-installing Resurrection Remix, but tablet keeps failing to flash. Might have to try and flash a different TWRP. I don't know...
Have you tried another Gapps? Also, is this the WiFi only model or the LTE model we're talking about?
Lightn1ng said:
Have you tried another Gapps? Also, is this the WiFi only model or the LTE model we're talking about?
Click to expand...
Click to collapse
It's the WiFi-only model - SM-T800.
It's kind of weird. I thought it might be some sort of internal memory problem (like the worn Nand pages you mentioned), since almost anything I try to do in TWRP fails (although I was able to flash an entire Custom ROM the one time AND get it booted) -but backing up isn't working, whether it's to internal/external SD. And the fact that I can flash perfectly (subjective term there) well using Odin or Kies tells me that whatever problems the tablet is having, something's getting through.
I'll try a different GAPPS package. Right now, though, TWRP isn't letting me flash hardly anything, and moving files back and forth on this thing is just awful.
AGH - I was so close!
daina said:
It's the WiFi-only model - SM-T800.
It's kind of weird. I thought it might be some sort of internal memory problem (like the worn Nand pages you mentioned), since almost anything I try to do in TWRP fails (although I was able to flash an entire Custom ROM the one time AND get it booted) -but backing up isn't working, whether it's to internal/external SD. And the fact that I can flash perfectly (subjective term there) well using Odin or Kies tells me that whatever problems the tablet is having, something's getting through.
I'll try a different GAPPS package. Right now, though, TWRP isn't letting me flash hardly anything, and moving files back and forth on this thing is just awful.
AGH - I was so close!
Click to expand...
Click to collapse
I'm running out of ideas!
Maybe somebody else with a T800 could backup their entire EMMC using
Code:
dd if=/dev/mmcblk0 of=/sdcard/full_nand_dump.bin
And you take the file on your tablet and do
Code:
dd if=/sdcard/full_nand_dump.bin of=/dev/mmcblk0
And restore YOUR efs folder using TWRP.
THIS IS A DANGEROUS OPERATION AND I AM NOT RESPONSIBLE FOR ANYTHING THAT GOES WRONG!
---------- Post added at 08:01 PM ---------- Previous post was at 07:57 PM ----------
@ashyx Any more ideas before I go ahead with my evil world domination plan to recover this device?
I wouldnt carry out any risky operations until a full backup can be made with twrp or you may end up with an unrecoverable device.
If twrp cannot backup the system partition then there is an issue with the partition.
Try backup again and post the recovery log, it may contain some relative information.
I have the same issues and have tried eveything. I was rooted and running the latest Pheonix rom on my sm-t800. Last Wednesday (8-10) I starting getting boot loops out of nowhere, no new apps nothing just a daily driver. I've been through everything on here and have gone back to bone stock but to no avail, the boot loops just keep coming. I can connect to wifi and get things set up but if I try to use anything more than 'light usage' the tab starts its boot loops again and rows fits for about 10 minutes and always different timing on the boot. Sometimes it will make it to the Samsung logo, sometime only to Tab S and sometimes about 10 seconds of usage.. I know this isn't helping much but wanted to let you know there are more of us with the same problem. Will be blab to try anything to help said issue.
Exactly the same issue on my LTE version.
Samsung support just asked me 230€ for a new motherboard.
I refused to repair. I think it is related to nand memory..
Hello I have both the 8.4" and 10.5" I updated the 8.4" to Android 5.02 nothing but boot loops my other is still on 442 and I wont be updating it as its working fine. I have been reading a few posts and the problem was right in front of me all the time I have 2 internet connections 2.4 GHZ and 5.0 GHZ if I connect to the 5.0 GHZ I get boot loops but if I stay on 2.4 GHZ no problems what so ever so I may just install a custom rom and my 10.5 tab and stay clear of the faster internet.
srfairhurst said:
Hello I have both the 8.4" and 10.5" I updated the 8.4" to Android 5.02 nothing but boot loops my other is still on 442 and I wont be updating it as its working fine. I have been reading a few posts and the problem was right in front of me all the time I have 2 internet connections 2.4 GHZ and 5.0 GHZ if I connect to the 5.0 GHZ I get boot loops but if I stay on 2.4 GHZ no problems what so ever so I may just install a custom rom and my 10.5 tab and stay clear of the faster internet.
Click to expand...
Click to collapse
Why not just update to Marshmallow? Absolutely no issues for me.
ashyx said:
Why not just update to Marshmallow? Absolutely no issues for me.
Click to expand...
Click to collapse
Now i figured out its the wifi thats causing the problem i will update to android 6.01 or if i can find a good custom rom il risk that.
daina said:
It's the WiFi-only model - SM-T800.
It's kind of weird. I thought it might be some sort of internal memory problem (like the worn Nand pages you mentioned), since almost anything I try to do in TWRP fails (although I was able to flash an entire Custom ROM the one time AND get it booted) -but backing up isn't working, whether it's to internal/external SD. And the fact that I can flash perfectly (subjective term there) well using Odin or Kies tells me that whatever problems the tablet is having, something's getting through.
I'll try a different GAPPS package. Right now, though, TWRP isn't letting me flash hardly anything, and moving files back and forth on this thing is just awful.
AGH - I was so close!
Click to expand...
Click to collapse
DrinkSlinger said:
I have the same issues and have tried eveything. I was rooted and running the latest Pheonix rom on my sm-t800. Last Wednesday (8-10) I starting getting boot loops out of nowhere, no new apps nothing just a daily driver. I've been through everything on here and have gone back to bone stock but to no avail, the boot loops just keep coming. I can connect to wifi and get things set up but if I try to use anything more than 'light usage' the tab starts its boot loops again and rows fits for about 10 minutes and always different timing on the boot. Sometimes it will make it to the Samsung logo, sometime only to Tab S and sometimes about 10 seconds of usage.. I know this isn't helping much but wanted to let you know there are more of us with the same problem. Will be blab to try anything to help said issue.
Click to expand...
Click to collapse
Hello,
and the rest of story??
i can flash TWRP in download mode, and i can intall zip by TWRP , the lineage rom,
but, cant odin flash official md5 file, it stucks on logo.
Hello guys!
I've buyed 910P, which was camuflated to 910F (i checked under battery - sticker there says SM-N910F, but in Odin download I see 910P). There was Lineage OS, celluar part works good, but there was some freezes (with camera/gallery), and pulse/UV sensor on back panel of phone isn't work. So after couple of days I've decided to return it to stock firmware - I wanted that sensor, and fast camera.
So. I maded backup with TWRP, found stock FW with 6.0.1 (N910PVPS4DQH1 if I remember correctly), loaded it with Odin - it works, but only english language (not a big problem), and no celluar networks at all. While I was on stock 6.0.1, it pulls update through OTA, and phone was updated. Nothing seems changed after OTA, celluar part don't works, all other good... I've decided to restore backup from my initial Lineage OS - and I don't maked backup of stock FW - I thinked like "I have firmware for Odin, I can re-flash it, if I'll need it...". But this seems to be critical mistake...
I've recovered Lineage OS backup, but phone don't see celluar network, all other was like before. I've tried several custom ROMs - and there was similar picture everywhere - all good, but no network. I decided that this probably caused by "bad" modem, and I just need to load some other modem firmware... I loaded it - and I've found that any custom ROM rebooting after 35-45 seconds from powering phone up. It can be on load animation on that moment, of If I install fresh lineage OS - it can ever show me a desktop - but it WILL vibrate and reboot after some time from powering up. Looks like watchdog...
I've tried to re-load stock ROM - but Odin fails - aboot in my phone has version 5, and in stock rom there is version 4. So I can't go back to stock state, and every ROM that I tried rebooting shortly after powering phone on.
Today I tried to load all parts of that stock rom, just without aboot - I unpacked tar, and maded tar without aboot (I changed system.ext4 with winhex, altered there version from 0004 to 0003 - there was same version mismatch like with aboot) - but it not helps, phone still reboots...
I think, this is because "new" aboot wants "new" modem...
So, I stuck here. Can't go back to stock, can't make phone just work without reboots...
Did somebody tries to load aboot from stock tar with TWRP? I mean copy aboot to SD, go to TWRP->terminal and try something like dd if=/sdcard/aboot.img of=/dev/block/... ?
I tried KIES, but it don't recognize phone - so I can't do "emergency recovery" there...
Did somebody have phone in stock after last OTA update? If yes - can you please share modem image for TWRP?
Sorry for really long post... I just need an advice, because I totally stucked now...
Dmitry_Sysoletin said:
Hello guys!
I've buyed 910P, which was camuflated to 910F (i checked under battery - sticker there says SM-N910F, but in Odin download I see 910P). There was Lineage OS, celluar part works good, but there was some freezes (with camera/gallery), and pulse/UV sensor on back panel of phone isn't work. So after couple of days I've decided to return it to stock firmware - I wanted that sensor, and fast camera.
So. I maded backup with TWRP, found stock FW with 6.0.1 (N910PVPS4DQH1 if I remember correctly), loaded it with Odin - it works, but only english language (not a big problem), and no celluar networks at all. While I was on stock 6.0.1, it pulls update through OTA, and phone was updated. Nothing seems changed after OTA, celluar part don't works, all other good... I've decided to restore backup from my initial Lineage OS - and I don't maked backup of stock FW - I thinked like "I have firmware for Odin, I can re-flash it, if I'll need it...". But this seems to be critical mistake...
I've recovered Lineage OS backup, but phone don't see celluar network, all other was like before. I've tried several custom ROMs - and there was similar picture everywhere - all good, but no network. I decided that this probably caused by "bad" modem, and I just need to load some other modem firmware... I loaded it - and I've found that any custom ROM rebooting after 35-45 seconds from powering phone up. It can be on load animation on that moment, of If I install fresh lineage OS - it can ever show me a desktop - but it WILL vibrate and reboot after some time from powering up. Looks like watchdog...
I've tried to re-load stock ROM - but Odin fails - aboot in my phone has version 5, and in stock rom there is version 4. So I can't go back to stock state, and every ROM that I tried rebooting shortly after powering phone on.
Today I tried to load all parts of that stock rom, just without aboot - I unpacked tar, and maded tar without aboot (I changed system.ext4 with winhex, altered there version from 0004 to 0003 - there was same version mismatch like with aboot) - but it not helps, phone still reboots...
I think, this is because "new" aboot wants "new" modem...
So, I stuck here. Can't go back to stock, can't make phone just work without reboots...
Did somebody tries to load aboot from stock tar with TWRP? I mean copy aboot to SD, go to TWRP->terminal and try something like dd if=/sdcard/aboot.img of=/dev/block/... ?
I tried KIES, but it don't recognize phone - so I can't do "emergency recovery" there...
Did somebody have phone in stock after last OTA update? If yes - can you please share modem image for TWRP?
Sorry for really long post... I just need an advice, because I totally stucked now...
Click to expand...
Click to collapse
Check this post, at the end you'll find link for the latest QI5 build, try to flash your phone by using odin, it may fix it.
https://drive.google.com/open?...d=0B1blPsoKK5taRk5SZ3NwdmUtTzA
Sent from my SM-N910P using Tapatalk
jam97 said:
Check this post, at the end you'll find link for the latest QI5 build, try to flash your phone by using odin, it may fix it.
https://drive.google.com/open?...d=0B1blPsoKK5taRk5SZ3NwdmUtTzA
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Actually, that post is mine too
But thanks anyway!