Related
I searched all yesterday and today and cannot re-root after upgrading from 4.1.2 to 4.3. I always do a ton of searchs no matter what forum I'm on because I don't want to seem lazy like some others out there but this is beyond me. I registered so I could make a thread and this is what I have and the situation:
Samsung Galaxy S3 SCH-R530U
US Cellular
upgraded from 4.1.2 to 4.3
kernel 3.031-2025306 [email protected] #1
baseband version R30UVXUBMJA
build number JSS15J.R530UVXUBMJA
SE for Android status Enforcing SEPF_SCH-530U_4.3_0010
hardware version R530U.01
Previously rooted using Odin, SuperSU, Titanium Backup Pro, ODIN_CWM6.tar.md5
I took the phone back to stock using unroot through SuperSU and upgraded from 4.1.2 to 4.3 OTA with no problems. I've been trying to re-root using numerous combinations (ODIN3 v3.07) and no matter what I do the Samsung Security notice blocks rights to SuperSU (beta v1.76) and Titanium Backup Pro so it won't root. This is the message I get:
"Security notice - unauthorized access to a secured area has been blocked. Tap to learn more."
The most recent md5 file I've tried is CF-Auto-Root-d2usc-d2usc-schr530u.tar.md5 but nothing else has worked either. I'm at my wits end and my brain is about ready to explode. I just need to be able to access Titanium Backup Pro so I can shut off a few programs and processes. Any help is VERY VERY much appreciated. Thanks!!!!!
TTT for some help please.
jguenther said:
I searched all yesterday and today and cannot re-root after upgrading from 4.1.2 to 4.3. I always do a ton of searchs no matter what forum I'm on because I don't want to seem lazy like some others out there but this is beyond me. I registered so I could make a thread and this is what I have and the situation:
Samsung Galaxy S3 SCH-R530U
US Cellular
upgraded from 4.1.2 to 4.3
kernel 3.031-2025306 [email protected] #1
baseband version R30UVXUBMJA
build number JSS15J.R530UVXUBMJA
SE for Android status Enforcing SEPF_SCH-530U_4.3_0010
hardware version R530U.01
Previously rooted using Odin, SuperSU, Titanium Backup Pro, ODIN_CWM6.tar.md5
I took the phone back to stock using unroot through SuperSU and upgraded from 4.1.2 to 4.3 OTA with no problems. I've been trying to re-root using numerous combinations (ODIN3 v3.07) and no matter what I do the Samsung Security notice blocks rights to SuperSU (beta v1.76) and Titanium Backup Pro so it won't root. This is the message I get:
"Security notice - unauthorized access to a secured area has been blocked. Tap to learn more."
The most recent md5 file I've tried is CF-Auto-Root-d2usc-d2usc-schr530u.tar.md5 but nothing else has worked either. I'm at my wits end and my brain is about ready to explode. I just need to be able to access Titanium Backup Pro so I can shut off a few programs and processes. Any help is VERY VERY much appreciated. Thanks!!!!!
Click to expand...
Click to collapse
I have same phone. Recently went to Slimbean (4.3.1). I have Triangle Away and it couldn't access root. I also used CF-Auto-Root. Used a root check app, it says I am rooted. Odin also said device passed. Super User says I am missing a binary and I need to root manually. Trying to find that info
If you find anything out please let me know. A root checker says I'm rooted but I can't access SuperSU or Titanium backup as the S3 is blocking it.
Did you get the Slimbean 4.3.1 for USCC and if so where?
There was just a new SuperSU update and it granted me access to everything. I asked if I wanted it to disable KNOX and I said yes. Titanium Backup works and so does Triangle Away. I think I'm good to go.
How did you update?
jguenther said:
There was just a new SuperSU update and it granted me access to everything. I asked if I wanted it to disable KNOX and I said yes. Titanium Backup works and so does Triangle Away. I think I'm good to go.
Click to expand...
Click to collapse
How did you update to 4.3? Did you use the simple update you can download to computer, or did you use Kies? I'm not having any luck with either. I chatted twice with a Samsung Tech person, but neither one had any help for me. Just thought I'd check to see if you could help me. It's not easy finding someone else on here with US Cellular. Any help would be appreciated. Thank you.
smithar said:
How did you update to 4.3? Did you use the simple update you can download to computer, or did you use Kies? I'm not having any luck with either. I chatted twice with a Samsung Tech person, but neither one had any help for me. Just thought I'd check to see if you could help me. It's not easy finding someone else on here with US Cellular. Any help would be appreciated. Thank you.
Click to expand...
Click to collapse
I tried to download the simple update but my phone wouldn't update to the 4.3 so I did it over the air. You probably know but the OTA software update is in "about device." We have four S3s in our home and only one of them hasn't been able to get the download OTA yet. The only bug that I've found is when you start the phone it will show numerous downloads in the notifications and they will come back even if you clear them. The way to get rid of them is to go to the download icon (green arrow) and clear all the downloads and restart. Hope this helps.
jguenther said:
I tried to download the simple update but my phone wouldn't update to the 4.3 so I did it over the air. You probably know but the OTA software update is in "about device." We have four S3s in our home and only one of them hasn't been able to get the download OTA yet. The only bug that I've found is when you start the phone it will show numerous downloads in the notifications and they will come back even if you clear them. The way to get rid of them is to go to the download icon (green arrow) and clear all the downloads and restart. Hope this helps.
Click to expand...
Click to collapse
I have downloaded the simple update, but get an error msg while trying to install to computer. (1152: error extracting) whatever that means. I uninstalled all Samsung anything from my computer, restarted, shut off firewall & Norton, downloaded again, but same thing while trying to install to computer. I updated to 4.1.2 this way, but keep getting an error on 4.3 update.
I tried to go through Kies. It updated Kies to 2.6, it said Kies3 was for 4.3. When I tried to hook into Kies, it refuses to accept my IMEI #. Says its incorrect. wth. The Samsung Chat Tech told me USCellular 4.3 update wasn't available yet through Kies OTA.
When I tried to get the 4.1.2 update through the phone, it would never give it to me. Even though I unrooted and used Triangle Away, it still knew my sg3 was modified. Maybe I'm doing something wrong. Do you have any suggestions ? I'm not very tech savvy when it comes to these phones.
I'm sorry to bother you with this, but it's rare to find someone with USCellular on here. Thank you so much for your time.
I got the error message too so something is wrong with the download from Samsung/USCC. Just keep trying to do the OTA update and maybe it will go through. My GUESS is that Samsung and USCC stopped doing the update because of a couple bugs or issues. The reason I say that is I updated mine one day (worked), my wife's the next (worked), my son's the next days later (worked) and tried my other son's a couple days later and no update for him. I unrooted mine before the update without doing triangle away so I don't know if that really has anything to do with it at all. However, it does have to be unrooted if you do the OTA. Good luck!
I used Triangle Away, then unrooted. My phone still says 'modified' even though counter no longer says 2. When I try OTA through the phone, it constantly sticks on 'checking for updates'. I'm sure it's because it still says modified. I tried using Kies, my phone will not connect. Keeps saying my s/n is incorrect. I understand my IMEI has been corrupted.
I have started a thread on here for some help in how to get the 4.3 update.
Thank you so much for trying to help me. I will be eligible for an upgrade soon. I just may have to wait to have anything more than 4.1.2.
Again, thank you.
Samsung
jguenther said:
I searched all yesterday and today and cannot re-root after upgrading from 4.1.2 to 4.3. I always do a ton of searchs no matter what forum I'm on because I don't want to seem lazy like some others out there but this is beyond me. I registered so I could make a thread and this is what I have and the situation:
Samsung Galaxy S3 SCH-R530U
US Cellular
upgraded from 4.1.2 to 4.3
kernel 3.031-2025306 [email protected] #1
baseband version R30UVXUBMJA
build number JSS15J.R530UVXUBMJA
SE for Android status Enforcing SEPF_SCH-530U_4.3_0010
hardware version R530U.01
Previously rooted using Odin, SuperSU, Titanium Backup Pro, ODIN_CWM6.tar.md5
I took the phone back to stock using unroot through SuperSU and upgraded from 4.1.2 to 4.3 OTA with no problems. I've been trying to re-root using numerous combinations (ODIN3 v3.07) and no matter what I do the Samsung Security notice blocks rights to SuperSU (beta v1.76) and Titanium Backup Pro so it won't root. This is the message I get:
"Security notice - unauthorized access to a secured area has been blocked. Tap to learn more."
The most recent md5 file I've tried is CF-Auto-Root-d2usc-d2usc-schr530u.tar.md5 but nothing else has worked either. I'm at my wits end and my brain is about ready to explode. I just need to be able to access Titanium Backup Pro so I can shut off a few programs and processes. Any help is VERY VERY much appreciated. Thanks!!!!!
Click to expand...
Click to collapse
it looks to me like samsung are finally making a stand against rooting although i do not agree with this as i use an app called freedom and when i open it i get a security issue from Samsung
The only reason i left iphone for samsung was because i felt like they had something other apple with hardware and i was happy to do this as i could get root access but for now i see that this might not be possible for a while.
i recommend installing a normal superuser.apk and that might work but i cannot check this right now as i am out
i hope this little bit of information did help in anyway
Hi,
This is my first post here on the XDA forum so if I make any mistakes, please do tell.
So, I got a Galaxy Ace 2 (I8160) which was running unrooted and stock at Android 2.3.6 (if I recall correctly).
I decided I wanted the phone to run at a newer Android version (KitKat preferred), so I decided to look into Cyanogenmod 11.0.
I succesfully installed the Clockworkmod Recovery after soms attempts and after that I was able to install Cyanogenmod 11.0 running on Android 4.4.4.
My first impression was positive, until I noticed I regularly got some error messages about com.android.phone which stopped working.
On top of this, the phone had no service and I was unable to make any calls (also selecting a service provider made com.android.phone crash).
After a lot of looking around on the internet, I found out this could be caused because I flashed Cyanogenmod 11.0 directly from Android 2.3.6.
On another tutorial I read I should've flashed Cyanogenmod 11.0 from any Jellybean version but as I stated earlier, I flashed it from a Gingerbread version.
On another forum I found someone who used to have the same issue and stated that he made the same mistake as I did (flashing from a non-Jellybean version).
He said he flashed a stock Jellybean ROM to his phone, installed Clockworkmod Recovery and at last flashed Cyanogenmod again and everything seemed to be working just fine.
I decided to do the same and flashed a stock Jellybean ROM for the I8160 using Odin v3.07.
After Odin told me the flash process passed, the phone rebooted but was stuck at the Samsung Galaxy Ace 2 logo.
When trying to get into the recovery, I got the same problem and the only thing I saw was the startup logo.
If I'd turn off the phone and plug in to my computer (which normally shows the battery percentage) it'd be stuck at the loading icon (normally this loading icon is visible for about 5 seconds and after that the battery percentage is visible).
I'm still able to get into download mode, so I tried reflashing the same ROM but unfortunately without success.
I used the following stock ROM: samsung-updates.com/details/28857/Galaxy_Ace_2/GT-I8160/XEN/I8160XXNB1.html.
I've been using the Cyanogenmod 11.0 and GApps files from: maclaw.pl/downloads/.
Does anybody have any idea about how I coud fix this?
Thanks in advance.
EDIT: Just tried flashing a stock ROM with Android 2.3.6, problem is still there: samsung-updates.com/details/18868/Galaxy_Ace_2/GT-I8160/H3G/I8160NELG2.html
In my opinion, You should flash 3-parted Firmware
http://forum.xda-developers.com/showpost.php?p=53921158&postcount=8
PS. Sorry for my bad English.
ChuckMichael said:
In my opinion, You should flash 3-parted Firmware
http://forum.xda-developers.com/showpost.php?p=53921158&postcount=8
PS. Sorry for my bad English.
Click to expand...
Click to collapse
Thanks for you reply.
I came across this 3-parted firmware flash a few hours ago.
I'm trying it right now. I'll let you know what the results are.
Alright, another update. (My problem seems to be fixed!)
At first I tried downloading the 3 files neccessary for the new flash method, but for some reason it'd take me hours to download them.
I started looking on the internet for the same files and found a torrent link on another forum leading to a torrent file uploaded here, on the XDA forums: http://forum.xda-developers.com/attachment.php?attachmentid=1757643&d=1361735404.
I downloaded the files in the torrent and used them properly in Odin.
The flashing process started and at about 80% Odin gave me a nasty error message saying the flash failed...
At that moment I was seriously hopeless and pretty sure I've just succesfully hard-bricked my phone.
I tried to start it and I got a weird message saying a firmware update went wrong and that I should fix it using Samsung Kies.
As it stated, I tried using Samsung Kies but was unable to get my phone to work.
I was out of options so I decided to give the 3-way flashing method a second chance.
Oding started flashing and for some reason finished succesfully this time.
The phone reboots, and shows the 'Samsung Galaxy Ace 2 GT-I8160' message for a few minutes.
After that the Samsung logo pops up and I've waited for another few minutes until a new screen pops up.
I see the Android guy and a blue progress bar underneath and patiently waits untill it's done.
After this I see the Samsung logo again and the phone finally boots to Android! Great Success!
Conclusion in my case: The 3-parted firmware seemed to do the trick for me.
As I stated above, the first flash failed but the second one was totally succesfully and revived my phone.
kolsthoorn said:
Alright, another update. (My problem seems to be fixed!)
At first I tried downloading the 3 files neccessary for the new flash method, but for some reason it'd take me hours to download them.
I started looking on the internet for the same files and found a torrent link on another forum leading to a torrent file uploaded here, on the XDA forums: http://forum.xda-developers.com/attachment.php?attachmentid=1757643&d=1361735404.
Click to expand...
Click to collapse
Yeb - you can use also the 3-parted MB4 (which was an very early JB FW).
But as the MB4 is not 100% complete - I still recommend only to use the 3-parted FWs linked by me (which ChuckMichael shows you)
But anyway - If your Phone booted you are done - You do not need to to it again. Just flash afterwards the newst original FW available.
My phone is running the BOG5 5.0.1 software and it is a retail edition.
I recieved a notification on my device prompting me that a new update is available (finally! 5.1.1!) I tap "download now", the download eventually finishes and it proceeds to install.
My phone boots into recovery, "installing update" and very shortly after I see the droid triage error and below it says "error!" and then my phone reboots. When I unlock my phone it says, "Sorry, there was a problem updating your SAMSUNG SM-N910V. No changes were made."
I looked under software update in settings and it says "software not updated to N910VVRU2BOK3" and the error code is 410.
I also notice that when I go into recovery it says "dm-verity verification failed...."
I looked in Kies to see if the update was available there, and of course it wasn't. And I can't find the ROM anywhere as of yet to flash with ODIN.
I would appreciate all of the help I can get.
Thank you.
traceestarr said:
My phone is running the BOG5 5.0.1 software and it is a retail edition.
I recieved a notification on my device prompting me that a new update is available (finally! 5.1.1!) I tap "download now", the download eventually finishes and it proceeds to install.
My phone boots into recovery, "installing update" and very shortly after I see the droid triage error and below it says "error!" and then my phone reboots. When I unlock my phone it says, "Sorry, there was a problem updating your SAMSUNG SM-N910V. No changes were made."
I looked under software update in settings and it says "software not updated to N910VVRU2BOK3" and the error code is 410.
I also notice that when I go into recovery it says "dm-verity verification failed...."
I looked in Kies to see if the update was available there, and of course it wasn't. And I can't find the ROM anywhere as of yet to flash with ODIN.
I would appreciate all of the help I can get.
Thank you.
Click to expand...
Click to collapse
I'm having the exact same issue and symptoms, have you made any progress with this? If I find a solution I'll share here too. I've tried Kies and VZW Software Upgrade Assistant, neither finds the update, but I can get it on my retail VZ Note 4, just won't successfully install.
Keiller said:
I'm having the exact same issue and symptoms, have you made any progress with this? If I find a solution I'll share here too. I've tried Kies and VZW Software Upgrade Assistant, neither finds the update, but I can get it on my retail VZ Note 4, just won't successfully install.
Click to expand...
Click to collapse
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
traceestarr said:
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
Click to expand...
Click to collapse
I have similar issue ,i don't have a update yet showing on my device so i await for it to show up. Please let us know if flashing it makes the difference.
traceestarr said:
Thank you for your feedback. I wonder if it has to do with a corrupt software build on our devices. I ordered my phone in November of last year and it came with BOG5 on it. I'm going to see about flashing stock BOG5 completely fresh on the phone and see if that corrects the issue.
Click to expand...
Click to collapse
Sounds like something worth trying, I'll watch for an update on how it goes for you. Thanks!
I have found a solution (albeit requires a full wipe, which is worth having 5.1.1 for me)
Firstly, I attempted flashing the "stock restore" file in odin and resulted in an error, I then tried the full firmware instead (mind you for BOG5, if you're having problems on your current version I'd suggest using your current build) with success, proceed with a data wipe in recovery and noticed that the "dm-verity verification failed...." message is now gone and now that bottom area of the screen has information about applying Multi-CSC.
Restart the phone, set up as normal and go straight for the software update. My phone downloaded and installed the update perfectly! For safety just boot into recovery and do a full wipe again, and there you have it!
The stock firmwares for RETAIL SM-N910V are here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
traceestarr said:
I have found a solution (albeit requires a full wipe, which is worth having 5.1.1 for me)
Firstly, I attempted flashing the "stock restore" file in odin and resulted in an error, I then tried the full firmware instead (mind you for BOG5, if you're having problems on your current version I'd suggest using your current build) with success, proceed with a data wipe in recovery and noticed that the "dm-verity verification failed...." message is now gone and now that bottom area of the screen has information about applying Multi-CSC.
Restart the phone, set up as normal and go straight for the software update. My phone downloaded and installed the update perfectly! For safety just boot into recovery and do a full wipe again, and there you have it!
The stock firmwares for RETAIL SM-N910V are here: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
Click to expand...
Click to collapse
Thank you for reporting back with what worked for you. I've tried following the same steps you took, but after flashing the full BOG5 firmware and doing a data wipe and then doing basic setup on my phone, the OTA is still failing, Error Code: 404. I'll try again, but so far no success. Still stuck on the buggy 5.0.1, the version where you can't flash back to 4.4.4....
Keiller said:
Thank you for reporting back with what worked for you. I've tried following the same steps you took, but after flashing the full BOG5 firmware and doing a data wipe and then doing basic setup on my phone, the OTA is still failing, Error Code: 404. I'll try again, but so far no success. Still stuck on the buggy 5.0.1, the version where you can't flash back to 4.4.4....
Click to expand...
Click to collapse
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
traceestarr said:
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
Click to expand...
Click to collapse
You're right, I thought I had seen that message earlier in the week while trying to get the OTA for 5.1.1 to work, but I didn't write it down. Your description of symptoms matched mine so well I figured it had to be the same issue or something so similar that running through the same process would work for me too.
I may take the phone into Verizon to show them the update fail and see if they are willing to do anything for me....
Glad you got yours up and running, but I am just a little bit jealous
Keiller said:
You're right, I thought I had seen that message earlier in the week while trying to get the OTA for 5.1.1 to work, but I didn't write it down. Your description of symptoms matched mine so well I figured it had to be the same issue or something so similar that running through the same process would work for me too.
I may take the phone into Verizon to show them the update fail and see if they are willing to do anything for me....
Glad you got yours up and running, but I am just a little bit jealous
Click to expand...
Click to collapse
I've found that most times the OTA update fails prior to rebooting to install the update and I get the 404 error I reported earlier. However, when it does make it to the point of doing the OTA update after reboot, after that fails, I get the same 410 error you reported, see attached, and I also the dm-verity fail message in recovery. Then after using Odin to install BOG5, the verity fail disappears, replaced by a Multi-CSC message, I do a complete data wipe/factory reset, set up my basic google account and try the OTA, which fails every time. But once the dm-verity fail is gone, I can try doing an update from external storage, which I've tried with the BOK3 5.1.1 zip file posted here: http://forum.xda-developers.com/not...id-5-1-1-according-to-website-t3290683/page20 However, this still fails to load.
At this point I'm pretty convinced that I some other issue with my phone. I found elsewhere that someone was able to take their phone into Best Buy and have them flash the 5.1.1 update for them via Kies. That is probably my next step.
But I wanted to share what I've tried in case anyone else is experiencing the same dead end or in the off chance that someone has found a solution.
Sure would love to see the full 5.1.1 BOK3 tar.md5 sometime before Marshmallow hits, pretty sure using Odin to install the update that way would work....
traceestarr said:
I am sorry to hear that this didn't work for you. But it appears we're both getting different error codes. Does your recovery display issues with dm-verity failing? I think this was part of my problem in the first place.
Click to expand...
Click to collapse
The full OTA for 5.1.1 was posted and I was able to update using Odin, following the instructions on this post: http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
Just wanted to update this post with the solution which finally worked for me.
Hello everybody, I'm in way over my head here. A few months ago, I rooted my device using odin. I felt that this was fairly simple and I had no issues. Today, I tried updating the software and got a message that said something like "can not update as you have unauthorized software installed". I thought I had better unroot and that's where my problems begin.
I unrooted using supersu, , but it still would not let me download the software update. I thought that the recovery must be the issue, so I tried flashing back to the stock image using odin and now the thing won't even turn on. It goes through the samsung startup screens and then goes into a sequence of 3 or 4 error messages that all read something like "Unfortunately, dialer storage has stopped"
I don't think I've done irrepairable damage but I'm not sure where to go now. It doesn't want to boot into recovery but I can get into download mode. Any help is greatly appreciated!
Flash the stock firmware in Odin to go back to 100% stock. You'll have to find the stock firmware (kitkat or lollipop) in one of these forum threads or download it from sammobile.
Edit: You didn't mention which device you have (8.4 or 10.5; wifi or cellular). Below are stock firmwares for 8.4 and 10.5.
http://forum.xda-developers.com/galaxy-tab-s/general/official-firmware-selection-sm-t700-sm-t2960225
HKSpeed said:
Flash the stock firmware in Odin to go back to 100% stock. You'll have to find the stock firmware (kitkat or lollipop) in one of these forum threads or download it from sammobile.
Edit: You didn't mention which device you have (8.4 or 10.5; wifi or cellular). Below are stock firmwares for 8.4 and 10.5.
http://forum.xda-developers.com/galaxy-tab-s/general/official-firmware-selection-sm-t700-sm-t2960225
Click to expand...
Click to collapse
Thank you! I have the sm-t805w. I have downloaded the firmware from sammobile and will attempt to install it this evening. Do I need to install gapps as with nexus devices or is that included in the firmware files?
Hey guys,
With the whole stay at home situation I stumbled upon my old Note 4 (sprint variant SM-N910p). I haven't touched it in several years, and have no clue what rom/firmware was on it, but it won'T boot. I can get into recovery but it fails to wipe anything, I was able to flash twrp (twrp-3.0.2-0-trltespr.img) through Odin, and i have tried various firmwares, but odin always fails. I have tried different cables, and even another computer. Not sure where to go from here. I only want the phone restored to factory, i do not need root. I have tried stock firmwares from sammobile aslo to no avail.
Any suggestions and help would be great!!
Thanks
Purell and be well!!!!!
If your on the latest update 5DQ15 then your locked on a fused 5, binary 4 and will be prevented from downgrading. Odin will show "sw rev check fail" when attempting to flashing a lower aboot. The firmware is at the top of the link
https://forum.xda-developers.com/no.../rom-15nov2017-stock-ish-plustidbits-t3705395
Mr. JAVI said:
If your on the latest update 5DQ15 then your locked on a fused 5, binary 4 and will be prevented from downgrading. Odin will show "sw rev check fail" when attempting to flashing a lower aboot. The firmware is at the top of the link
https://forum.xda-developers.com/no.../rom-15nov2017-stock-ish-plustidbits-t3705395
Click to expand...
Click to collapse
The main file download is not available from androidfilehost anymore.
if you do get it to pop through, it just doesn't download.
Do you know of an alternate source for this file??
I'm messing around with one of my old note 4's to check out the new roms without flashing my daily driver note 4. I done borked this one up long time ago, so it's wipe wiped.
Might have been a bad battery long time ago when this thing started messing up on me. doh!
sarinhighwind said:
The main file download is not available from androidfilehost anymore.
if you do get it to pop through, it just doesn't download.
Do you know of an alternate source for this file??
I'm messing around with one of my old note 4's to check out the new roms without flashing my daily driver note 4. I done borked this one up long time ago, so it's wipe wiped.
Might have been a bad battery long time ago when this thing started messing up on me. doh!
Click to expand...
Click to collapse
Looks like it works randomly. Decided to try again.