Develop Bugs

[Q] (Q) accidentally wiped OS ,Need help getting OS back on sgh-i747

To start I bought this phone from a friend was working fine. It seemed to be rooted after going to recovery mode and realizing it was a custom recovery that I got into. I've had plenty on iPhones and androids , so far this is the first time after hours of research and trying everything that I've had to make a post asking for help. I have a sgh-i747 pebble blue ATT phone. It had 4.3 OS on it and was rooted before I acidentally wiped the OS off of it. I've tried the past few days to use Odin to get the stock firmware back on, I've tried 4.0.1 - 4.3 , no luck. Odin recognizes phone after I click start after choosing the md5 tar file it either says fail or stays at setupconnection. I've tried many times over and over unistalling and re installing drivers , kies, and downloading different firmware and every version of Odin. I need help guys please , thanks alot

k4krisbrah said:
To start I bought this phone from a friend was working fine. It seemed to be rooted after going to recovery mode and realizing it was a custom recovery that I got into. I've had plenty on iPhones and androids , so far this is the first time after hours of research and trying everything that I've had to make a post asking for help. I have a sgh-i747 pebble blue ATT phone. It had 4.3 OS on it and was rooted before I acidentally wiped the OS off of it. I've tried the past few days to use Odin to get the stock firmware back on, I've tried 4.0.1 - 4.3 , no luck. Odin recognizes phone after I click start after choosing the md5 tar file it either says fail or stays at setupconnection. I've tried many times over and over unistalling and re installing drivers , kies, and downloading different firmware and every version of Odin. I need help guys please , thanks alot
Click to expand...
Click to collapse
I can get into recovery mode but it's a custom one , and I can get into download mode. Someone please help I'm sire it's somethig small I'm missing like the correct downloads for the firmware and odin

k4krisbrah said:
I can get into recovery mode but it's a custom one , and I can get into download mode. Someone please help I'm sire it's somethig small I'm missing like the correct downloads for the firmware and odin
Click to expand...
Click to collapse
it was rooted with a custom recovery on it before i wiped the OS off , it was on 4.3 , working okay. ive tried so many firmwares , so many threads on how to , so many downloads of odin and the firmware and tried uninstalling and re installing everything from drivers to kies to everything. someone please help or forward me to a thread that WILL work. ive even tried 2 different cords and 3 different usb ports and am not using a usb hub. the pc im using recognizes my phone in odin but always either freezes after i select firmware and click start or it goes thru and comes up with fail, or failed auth. someone please help thanks.

k4krisbrah said:
it was rooted with a custom recovery on it before i wiped the OS off , it was on 4.3 , working okay. ive tried so many firmwares , so many threads on how to , so many downloads of odin and the firmware and tried uninstalling and re installing everything from drivers to kies to everything. someone please help or forward me to a thread that WILL work. ive even tried 2 different cords and 3 different usb ports and am not using a usb hub. the pc im using recognizes my phone in odin but always either freezes after i select firmware and click start or it goes thru and comes up with fail, or failed auth. someone please help thanks.
Click to expand...
Click to collapse
Since your phone was on 4.3, the only thing you can do now would be a stock restore to 4.3. Please see the thread below for the stock restore zip as well as instructions. You may use another device to copy the stock restore zip to an external SD card and then place this card in your phone, then flash from (custom) recovery. Odin cant help you now except to flash custom recovery if you need to redo this.
http://forum.xda-developers.com/showthread.php?t=2658486

Larry2999 said:
Since your phone was on 4.3, the only thing you can do now would be a stock restore to 4.3. Please see the thread below for the stock restore zip as well as instructions. You may use another device to copy the stock restore zip to an external SD card and then place this card in your phone, then flash from (custom) recovery. Odin cant help you now except to flash custom recovery if you need to redo this.
http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
the only option i have is a s3 with a lcd thats not working it will boot and go on but i cant see anything. how would i go upon sticking my sd card inside there and getting that 4.3 download on there.

k4krisbrah said:
the only option i have is a s3 with a lcd thats not working it will boot and go on but i cant see anything. how would i go upon sticking my sd card inside there and getting that 4.3 download on there.
Click to expand...
Click to collapse
i found out i have twrp custom recovery that i can access and download mode. its twrp v2.6.3.1

k4krisbrah said:
i found out i have twrp custom recovery that i can access and download mode. its twrp v2.6.3.1
Click to expand...
Click to collapse
Good you have TWRP already. You can try to see if you can save the zip to your phone's internal memory as the PC may be able to recognize it in download or recovery mode. Otherwise, you may try using any other device at all that accepts (micro) SDHC card e.g. camera, card adapter etc. You may also be able to flash the zip directly from your PC using the desktop flasher. See thread with instructions below ...
http://forum.xda-developers.com/showthread.php?t=2383148
Let me know if this works for you.
---------- Post added at 09:02 PM ---------- Previous post was at 09:00 PM ----------
Larry2999 said:
Good you have TWRP already. You can try to see if you can save the zip to your phone's internal memory as the PC may be able to recognize it in download or recovery mode. Otherwise, you may try using any other device at all that accepts (micro) SDHC card e.g. camera, card adapter etc. You may also be able to flash the zip directly from your PC using the desktop flasher. See thread with instructions below ...
http://forum.xda-developers.com/showthread.php?t=2383148
Let me know if this works for you.
Click to expand...
Click to collapse
Of course, you need to first download the stock recovery zip for TWRP to your PC.

Larry2999 said:
Good you have TWRP already. You can try to see if you can save the zip to your phone's internal memory as the PC may be able to recognize it in download or recovery mode. Otherwise, you may try using any other device at all that accepts (micro) SDHC card e.g. camera, card adapter etc. You may also be able to flash the zip directly from your PC using the desktop flasher. See thread with instructions below ...
http://forum.xda-developers.com/showthread.php?t=2383148
Let me know if this works for you.
---------- Post added at 09:02 PM ---------- Previous post was at 09:00 PM ----------
Of course, you need to first download the stock recovery zip for TWRP to your PC.
Click to expand...
Click to collapse
thanks so much for your help. i took my s3 that had a bad lcd and put my sd in that and moved the zip file i downloaded here http://forum.xda-developers.com/showthread.php?t=2658486 then i flashed it from twrp and wiped cache and all that good stuff everything was fine after that. only question i have for you now is to root or not to root , i forget the pros and cons of it , its been a while. i know i rooted my s2 and note 2 a while back but i havent had a android in a while. thanks so much for your help , thumbs up :good:

k4krisbrah said:
thanks so much for your help. i took my s3 that had a bad lcd and put my sd in that and moved the zip file i downloaded here http://forum.xda-developers.com/showthread.php?t=2658486 then i flashed it from twrp and wiped cache and all that good stuff everything was fine after that. only question i have for you now is to root or not to root , i forget the pros and cons of it , its been a while. i know i rooted my s2 and note 2 a while back but i havent had a android in a while. thanks so much for your help , thumbs up :good:
Click to expand...
Click to collapse
Glad to know your phone is now working fine. To root or not is a choice you'll have to make depending on how much control you want over your phone. The pros are that you literally have control over your phone in terms of installing apps or making modifications to the operating system. You can install custom ROMs and/or apps that you would otherwise not be able to install. The con, of course, is security and integrity of your phone. There is always a risk that you may end up bricking your phone or creating access for malware. Rooting should, therefore, be something you do only if you have need for it.

... Just Odin stock ROM and work from there or if twrp isn't latest... Odin latest recovery and then USB files into phone using recovery and then flash... Or again just use odin to flash and then do whatever you want afterward
Sent from my d2lte using Tapatalk

[Q] Problems with AT&T update from 4.1.1

I'm sure I'm not the only one that has had this problem. I've never been able to do the update to 4.2 from 4.1.1. After the download and reboot, the phone gives me an error message. AT&T was no help. I rooted my phone last year but I can't remember how I rooted it. Anyway, I want to update to a new stable ROM. My questions are, do I need to update from 4.1 to 4.2, then 4.3 and then 4.4? Or can I go from 4.1 to 4.4? And if someone could direct me to an easy problem-free stable ROM, I would be most grateful!
Jennifer

southernblonde said:
I'm sure I'm not the only one that has had this problem. I've never been able to do the update to 4.2 from 4.1.1. After the download and reboot, the phone gives me an error message. AT&T was no help. I rooted my phone last year but I can't remember how I rooted it. Anyway, I want to update to a new stable ROM. My questions are, do I need to update from 4.1 to 4.2, then 4.3 and then 4.4? Or can I go from 4.1 to 4.4? And if someone could direct me to an easy problem-free stable ROM, I would be most grateful!
Jennifer
Click to expand...
Click to collapse
If your phone is rooted, you could have difficulties getting an OTA update. You could either unroot your phone from the SuperSU app or you could manually do a 2-step update to 4.1.2 and then 4.3. Unrooting should allow your phone take an OTA update if you are currently on a stock ROM. For manual update process, please follow the instructions below ....
1) Go to the first page in the thread below ...
http://forum.xda-developers.com/show....php?t=2387423
2) Download the 2 zip files under update412.zip and update43.zip respectively to your computer
3) Copy the zip files to a good quality (micro) SD card
4) Place the card in your phone and boot to recovery mode by simultaneously holding down the Volume Up, Home and Power buttons
5) Hold the buttons until you see a blue message flash across the screen. Then release the Power button but continue to hold the Volume Up and Home button until you see the Android image appear. Then release the buttons
6) Use the volume up/down key to scroll to <mount from external storage> and the power button to select
7) Navigate to the first zip file (update412.zip) and install. Wait for installation to finish and your phone to reboot.
8) Complete set up. Check your phone settings. Then power off and reboot to recovery again.
9) Repeat the process for the second update file.
The latest (official) Android version available for the i747 is 4.3 Jelly Bean. Android 4.4 (Kit-Kat) has not been rolled out yet for this phone so if you want the latest stock (official) system, that would be 4.3. If you are looking at a custom ROM, there are quite a few Kit-Kat based ROMs out there.

Larry2999 said:
If your phone is rooted, you could have difficulties getting an OTA update. You could either unroot your phone from the SuperSU app or you could manually do a 2-step update to 4.1.2 and then 4.3. Unrooting should allow your phone take an OTA update if you are currently on a stock ROM. For manual update process, please follow the instructions below ....
1) Go to the first page in the thread below ...
http://forum.xda-developers.com/show....php?t=2387423
2) Download the 2 zip files under update412.zip and update43.zip respectively to your computer
3) Copy the zip files to a good quality (micro) SD card
4) Place the card in your phone and boot to recovery mode by simultaneously holding down the Volume Up, Home and Power buttons
5) Hold the buttons until you see a blue message flash across the screen. Then release the Power button but continue to hold the Volume Up and Home button until you see the Android image appear. Then release the buttons
6) Use the volume up/down key to scroll to <mount from external storage> and the power button to select
7) Navigate to the first zip file (update412.zip) and install. Wait for installation to finish and your phone to reboot.
8) Complete set up. Check your phone settings. Then power off and reboot to recovery again.
9) Repeat the process for the second update file.
The latest (official) Android version available for the i747 is 4.3 Jelly Bean. Android 4.4 (Kit-Kat) has not been rolled out yet for this phone so if you want the latest stock (official) system, that would be 4.3. If you are looking at a custom ROM, there are quite a few Kit-Kat based ROMs out there.
Click to expand...
Click to collapse
Thanks for replying so quickly. When installing 412.zip, I get the following error message after Verifying Current System:
E:Error in tmp/sideload/package.zip (Status 7)

southernblonde said:
Thanks for replying so quickly. When installing 412.zip, I get the following error message after Verifying Current System:
E:Error in tmp/sideload/package.zip (Status 7)
Click to expand...
Click to collapse
Usually, you get a status 7 error message when your recovery mode is out of date. Are you using stock recovery or custom recovery? If custom, would you know what version it is?

Larry2999 said:
Usually, you get a status 7 error message when your recovery mode is out of date. Are you using stock recovery or custom recovery? If custom, would you know what version it is?
Click to expand...
Click to collapse
It looked to be stock recovery. It said Android System Recovery

southernblonde said:
It looked to be stock recovery. It said Android System Recovery
Click to expand...
Click to collapse
You shouldn't have any difficulties flashing the zip if you are on stock recovery. Did you verify the MD5 of the zip you downloaded to be sure it downloaded correctly?

Larry2999 said:
You shouldn't have any difficulties flashing the zip if you are on stock recovery. Did you verify the MD5 of the zip you downloaded to be sure it downloaded correctly?
Click to expand...
Click to collapse
What does MD5 stand for?
Earlier today I tried unrooting and downloading OTA but same problem as before....it cuts out early during installation, reboots and I'm left with 4.1.1

southernblonde said:
What does MD5 stand for?
Earlier today I tried unrooting and downloading OTA but same problem as before....it cuts out early during installation, reboots and I'm left with 4.1.1
Click to expand...
Click to collapse
The MD5 (or checksum verifier) is an algorithm used to verify the authenticity and integrity of digital files. It is statistically improbable for 2 separately created files to have the same MD5 so verifying the MD5 ascertains that the file downloaded correctly and/or has not altered in any way from the original prior to your download. The download source for the files shows the MD5 of the original files so you can use the MD5 checker tool to verify the ones you downloaded. If the MD5 matches, then the file is OK. Otherwise, it didn't download correctly or may have been altered in some way.
http://winmd5.com/
However, the fact that you are unable to get the OTA update after unrooting suggests there may be a different problem with your device. Possible some security encryptions are preventing updates to the system. I'll suggest you back up your files and try doing a factory reset to return the phone to original settings then try the upgrade process again. Prior to upgrading your firmware, however, I would suggest you take the opportunity to free unlock your phone (if not already done). This can only be done on 4.1.1

Larry2999 said:
The MD5 (or checksum verifier) is an algorithm used to verify the authenticity and integrity of digital files. It is statistically improbable for 2 separately created files to have the same MD5 so verifying the MD5 ascertains that the file downloaded correctly and/or has not altered in any way from the original prior to your download. The download source for the files shows the MD5 of the original files so you can use the MD5 checker tool to verify the ones you downloaded. If the MD5 matches, then the file is OK. Otherwise, it didn't download correctly or may have been altered in some way.
http://winmd5.com/
However, the fact that you are unable to get the OTA update after unrooting suggests there may be a different problem with your device. Possible some security encryptions are preventing updates to the system. I'll suggest you back up your files and try doing a factory reset to return the phone to original settings then try the upgrade process again. Prior to upgrading your firmware, however, I would suggest you take the opportunity to free unlock your phone (if not already done). This can only be done on 4.1.1
Click to expand...
Click to collapse
Thanks for all your help, I really appreciate it. I've been working on this phone all day. I'm still having issues with the phone after doing a factory reset and a hard reset. I unlocked it also. The MD5s matched. It downloads the update, then when it goes to install, it gets to 25% then bypasses the rest. The phone still says its 4.1.1. After I did the factory reset only, when I went to update, it was saying there were no updates available...thats what led me to do the hard reset. I'm ready to throw this thing in the ocean. I thought the hard reset would put it back to just out of the box fresh but I still see old apps in there like SuperSU and Mobile Odin Pro. Perhaps those apps are messing it up? This really has me stumped. When I USB it to my laptop and boot up Kies, it says there are no updates available.
I just wiped the cache partition and did a hard reset again. This time I downloaded the update412.zip from the sdcard and I got the same original error: E:Error in tmp/sideload/package.zip (Status 7)

southernblonde said:
Thanks for all your help, I really appreciate it. I've been working on this phone all day. I'm still having issues with the phone after doing a factory reset and a hard reset. I unlocked it also. The MD5s matched. It downloads the update, then when it goes to install, it gets to 25% then bypasses the rest. The phone still says its 4.1.1. After I did the factory reset only, when I went to update, it was saying there were no updates available...thats what led me to do the hard reset. I'm ready to throw this thing in the ocean. I thought the hard reset would put it back to just out of the box fresh but I still see old apps in there like SuperSU and Mobile Odin Pro. Perhaps those apps are messing it up? This really has me stumped. When I USB it to my laptop and boot up Kies, it says there are no updates available.
I just wiped the cache partition and did a hard reset again. This time I downloaded the update412.zip from the sdcard and I got the same original error: E:Error in tmp/sideload/package.zip (Status 7)
Click to expand...
Click to collapse
Please don't give up on your phone yet. It isn't that bad yet. The dreaded error message you are getting means that your recovery system is compromised. Also, once rooted, your phone stays that until specifically unrooted. Even a factory reset will not remove SuperSU and Mobile Odin and the definitive solution to un-rooting is to flash a complete stock image. However, you may be able to fix the recovery issue and get updates in a number of ways. First, you could reflash a complete stock 4.1.1 image via Odin. This will update all system partitions including recovery and should deliver a new and working recovery partition. It will also remove root and make it possible to get an OTA update to 4.3JB. You can download the Odin flashable file from Sammobile.com or from the following link ... http://www.4shared.com/get/zAmWJ54J/I747UCDLK3_I747ATTDLK3_ATT.html
Unzip and extract the *.tar file and flash via Odin.
The second solution would be to use Mobile Odin or Desktop Odin v3.09 to flash a new recovery partition. You'll need the same *.tar file for UCDLK3 but you'd only need to load the recovery partition. If this is successful, you can try the manual update process again.
The final solution would be to flash custom recovery via Odin and then flash the 4.3JB stock restore image via (custom) recovery. You could do the same 2-step manual update via custom recovery. However, a complete stock restore image is available for 4.3 which can be flashed via custom recovery. Please see the first page of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2658486
You can find the TWRP custom recovery Odin flashable file for your device via the link below ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
Hope this finally solves it.

Larry2999 said:
Please don't give up on your phone yet. It isn't that bad yet. The dreaded error message you are getting means that your recovery system is compromised. Also, once rooted, your phone stays that until specifically unrooted. Even a factory reset will not remove SuperSU and Mobile Odin and the definitive solution to un-rooting is to flash a complete stock image. However, you may be able to fix the recovery issue and get updates in a number of ways. First, you could reflash a complete stock 4.1.1 image via Odin. This will update all system partitions including recovery and should deliver a new and working recovery partition. It will also remove root and make it possible to get an OTA update to 4.3JB. You can download the Odin flashable file from Sammobile.com or from the following link ... http://www.4shared.com/get/zAmWJ54J/I747UCDLK3_I747ATTDLK3_ATT.html
Unzip and extract the *.tar file and flash via Odin.
The second solution would be to use Mobile Odin or Desktop Odin v3.09 to flash a new recovery partition. You'll need the same *.tar file for UCDLK3 but you'd only need to load the recovery partition. If this is successful, you can try the manual update process again.
The final solution would be to flash custom recovery via Odin and then flash the 4.3JB stock restore image via (custom) recovery. You could do the same 2-step manual update via custom recovery. However, a complete stock restore image is available for 4.3 which can be flashed via custom recovery. Please see the first page of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2658486
You can find the TWRP custom recovery Odin flashable file for your device via the link below ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
Hope this finally solves it.
Click to expand...
Click to collapse
I finally did get it fixed last night, actually by one of your solutions there. I had googled the error message (status 7) and I found a thread here on XDA where someone said that because I had used Titanium to delete bloatware when I got the phone, I wouldn't be able to update until it looked right out of the box so I downloaded Odin and flashed 4.1.1. again. Thank God I didn't brick the phone with everything I did to it yesterday. LOL It was finally able to flash 4.1.2 then 4.3. Its disturbing all the threads I see going back to 4.1.1 from 4.3. Is there a huge issue? I'm going to try to find a stable KitKat to flash to. Thanks again for your help!

southernblonde said:
I finally did get it fixed last night, actually by one of your solutions there. I had googled the error message (status 7) and I found a thread here on XDA where someone said that because I had used Titanium to delete bloatware when I got the phone, I wouldn't be able to update until it looked right out of the box so I downloaded Odin and flashed 4.1.1. again. Thank God I didn't brick the phone with everything I did to it yesterday. LOL It was finally able to flash 4.1.2 then 4.3. Its disturbing all the threads I see going back to 4.1.1 from 4.3. Is there a huge issue? I'm going to try to find a stable KitKat to flash to. Thanks again for your help!
Click to expand...
Click to collapse
Glad to know it's now working. I think there's more fuss than fact to the 4.3 question. As far as performance and functionality goes, Touchwiz 4.3 is a major improvement on the older Jelly Bean versions. The main problem, of course, is that the bootloader can not be safely downgraded once you are on 4.3. This is only a problem if you need to free unlock your phone which is only possible on 4.1.1. Otherwise, you can safely flash a KitKat based custom ROM. I would only advise you stick with a stable like you've said and be sure it's one that won't try to mess with your bootloader. Most custom ROMs don't but it wouldn't hurt to make sure.

Larry2999 said:
Glad to know it's now working. I think there's more fuss than fact to the 4.3 question. As far as performance and functionality goes, Touchwiz 4.3 is a major improvement on the older Jelly Bean versions. The main problem, of course, is that the bootloader can not be safely downgraded once you are on 4.3. This is only a problem if you need to free unlock your phone which is only possible on 4.1.1. Otherwise, you can safely flash a KitKat based custom ROM. I would only advise you stick with a stable like you've said and be sure it's one that won't try to mess with your bootloader. Most custom ROMs don't but it wouldn't hurt to make sure.
Click to expand...
Click to collapse
Do you have a recommendation for a stable Kit Kat rom?

I am trying to upgrade to 4.3 on an unlocked, rooted SGH-I747 that I am using internationally (in New Zealand now); however, when I tried to flash a clean 4.1.1 so I could update to 4.3, doing a factory reset and cache wipe, I successfully load the firmware with Odin but then it won't boot past the blue pulsing samsung logo I think I need to flash a new recovery partition, as you suggest below, but I don't know how to do that.
Can anyone help?
Larry2999 said:
Please don't give up on your phone yet. It isn't that bad yet. The dreaded error message you are getting means that your recovery system is compromised. Also, once rooted, your phone stays that until specifically unrooted. Even a factory reset will not remove SuperSU and Mobile Odin and the definitive solution to un-rooting is to flash a complete stock image. However, you may be able to fix the recovery issue and get updates in a number of ways. First, you could reflash a complete stock 4.1.1 image via Odin. This will update all system partitions including recovery and should deliver a new and working recovery partition. It will also remove root and make it possible to get an OTA update to 4.3JB. You can download the Odin flashable file from Sammobile.com or from the following link ... http://www.4shared.com/get/zAmWJ54J/I747UCDLK3_I747ATTDLK3_ATT.html
Unzip and extract the *.tar file and flash via Odin.
The second solution would be to use Mobile Odin or Desktop Odin v3.09 to flash a new recovery partition. You'll need the same *.tar file for UCDLK3 but you'd only need to load the recovery partition. If this is successful, you can try the manual update process again.
The final solution would be to flash custom recovery via Odin and then flash the 4.3JB stock restore image via (custom) recovery. You could do the same 2-step manual update via custom recovery. However, a complete stock restore image is available for 4.3 which can be flashed via custom recovery. Please see the first page of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2658486
You can find the TWRP custom recovery Odin flashable file for your device via the link below ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
Hope this finally solves it.
Click to expand...
Click to collapse

southernblonde said:
Do you have a recommendation for a stable Kit Kat rom?
Click to expand...
Click to collapse
I'm not too much into customs. You could, however, take a loot at the new AOSP ROMS or CM 10x...
---------- Post added at 10:34 AM ---------- Previous post was at 10:30 AM ----------
Pfhyde said:
I am trying to upgrade to 4.3 on an unlocked, rooted SGH-I747 that I am using internationally (in New Zealand now); however, when I tried to flash a clean 4.1.1 so I could update to 4.3, doing a factory reset and cache wipe, I successfully load the firmware with Odin but then it won't boot past the blue pulsing samsung logo I think I need to flash a new recovery partition, as you suggest below, but I don't know how to do that.
Can anyone help?
Click to expand...
Click to collapse
You could have installed directly from recovery without first trying to flash a fresh 4.1.1. This would have only been necessary if your 4.1.1 wasn't working right in some way. Try booting into recovery and then doing a wipe/reset. If your phone boots successfully after this, then try the 2-step update -first to 4.1.2 and then to 4.3 via the instructions posted earlier in this thread. Please let me know if this works.

Larry2999 said:
I'm not too much into customs. You could, however, take a loot at the new AOSP ROMS or CM 10x...
---------- Post added at 10:34 AM ---------- Previous post was at 10:30 AM ----------
You could have installed directly from recovery without first trying to flash a fresh 4.1.1. This would have only been necessary if your 4.1.1 wasn't working right in some way. Try booting into recovery and then doing a wipe/reset. If your phone boots successfully after this, then try the 2-step update -first to 4.1.2 and then to 4.3 via the instructions posted earlier in this thread. Please let me know if this works.
Click to expand...
Click to collapse
Thanks for the suggestion. I've tried wiping again from recovery but I get errors (see this thread I started for the details).
-pf

Pfhyde said:
Thanks for the suggestion. I've tried wiping again from recovery but I get errors (see this thread I started for the details).
-pf
Click to expand...
Click to collapse
Since you are apparently successful with Odin, can you try flashing an original stock image rather than the modified (pre-rooted) version you are using. You may download the original version from sammobile.com or do an internet search for it. The zip should be close to 1Gb in size but please make sure to verify the MD5 prior to flashing.

Larry2999 said:
I'm not too much into customs. You could, however, take a loot at the new AOSP ROMS or CM 10x...
---------- Post added at 10:34 AM ---------- Previous post was at 10:30 AM ----------
You could have installed directly from recovery without first trying to flash a fresh 4.1.1. This would have only been necessary if your 4.1.1 wasn't working right in some way. Try booting into recovery and then doing a wipe/reset. If your phone boots successfully after this, then try the 2-step update -first to 4.1.2 and then to 4.3 via the instructions posted earlier in this thread. Please let me know if this works.
Click to expand...
Click to collapse
Larry2999 said:
Since you are apparently successful with Odin, can you try flashing an original stock image rather than the modified (pre-rooted) version you are using. You may download the original version from sammobile.com or do an internet search for it. The zip should be close to 1Gb in size but please make sure to verify the MD5 prior to flashing.
Click to expand...
Click to collapse
I did try an original stock, originally. I only tried the rooted stock after the original didn't work (got stuck with pulsing blue samsung logo). I'll try the one from sammobile.com (but I think that's where I got it the first time) and report back after I get off work late tonight.
-p

[Q] 4G LTE issue

Hi guys. I got new N900T phone with stock rom. Latest updated was 4.4.2
Few days before Lollipo come up, I rooted my phone and when Lollipop 5.0 was published I installed 4.4.2 stock via Odin to update rom to 5.0 official. and I done that. All worked fine and as u all know, we couldnt write to SD card. My GPS worked fast, but I wanted SD card write. I rooted my phone to install SD fix, but I couldnt do that somehow (i got some errors) and I flashed official 5.0 Lollipop again via Odin. After that my GPS doesnt want to lock and I reset nv_build (something like that), now my GSP working but still I need 5-10 mins to lock. I have 4G issue now, even if I switch it to LTE, I dont get 4G LTE signal. When I put my SIM card to other 4G phone, 4G working, but on my phone doesnt want to work. ANy suggestion? solution? idea? to somehow reset 4G network, idk. 3G working. Ty
Samusng Galaxy Note 3 N900T
Lollipop 5.0 latest firmware stock official

Anyone?

Anyone?

Boot into twrp recovery, wipe data, system, internal storage, cache, dalvik cache. Pull battery for the 30 seconds. Insert battery. Enter download mode. Flash full stock 5.0 lollipop tar found on this thread. Maybe you already have the tar. Your phone should be good to go after that clean install.
http://forum.xda-developers.com/showthread.php?t=3047672

srod562 said:
Boot into twrp recovery, wipe data, system, internal storage, cache, dalvik cache. Pull battery for the 30 seconds. Insert battery. Enter download mode. Flash full stock 5.0 lollipop tar found on this thread. Maybe you already have the tar. Your phone should be good to go after that clean install.
http://forum.xda-developers.com/showthread.php?t=3047672
Click to expand...
Click to collapse
HI. Thank you on your time and help. I dont have twrp recowery. How to install it? Im on 5.0 lollipop stock.

srod562 said:
Boot into twrp recovery, wipe data, system, internal storage, cache, dalvik cache. Pull battery for the 30 seconds. Insert battery. Enter download mode. Flash full stock 5.0 lollipop tar found on this thread. Maybe you already have the tar. Your phone should be good to go after that clean install.
http://forum.xda-developers.com/showthread.php?t=3047672
Click to expand...
Click to collapse
It wont install TWRP recovery at all on my N900T Lollipop.

markokrstic said:
It wont install TWRP recovery at all on my N900T Lollipop.
Click to expand...
Click to collapse
Are you rooted? You have to root first using cf-auto root and then you install twrp recovery using odin. Do you need help on rooting phone or do you already know how to do that?
---------- Post added at 10:16 AM ---------- Previous post was at 10:10 AM ----------
I saw in your post that you have already rooted your device so after your stick rooted, boot into DL mode and flash this file in Odin on your pc and it will install twrp recovery. https://dl.twrp.me/hltetmo/twrp-2.8.6.0-hltetmo-4.4.img.tar.html

srod562 said:
Are you rooted? You have to root first using cf-auto root and then you install twrp recovery using odin. Do you need help on rooting phone or do you already know how to do that?
---------- Post added at 10:16 AM ---------- Previous post was at 10:10 AM ----------
I saw in your post that you have already rooted your device so after your stick rooted, boot into DL mode and flash this file in Odin on your pc and it will install twrp recovery. https://dl.twrp.me/hltetmo/twrp-2.8.6.0-hltetmo-4.4.img.tar.html
Click to expand...
Click to collapse
Hi. Thx again for your time. There was a issue with TWRP file from twrp website. I found another one here on XDA and worked great. I wiped all what u wrote in your post, installed again 5.0 stock via Odin and still 4G/LTE doesnt work.

Screwed up trying to root, stuck in bootloop

So, I've got a 64gb black sprint Galaxy S6, non-edge. This morning, it had stock 5.11 on it, but I decided I wanted to root it, and ... I screwed up. I got Odin 3.10.6 and installed CF-Auto-Root-zerofltespr-zerofltespr-smg920p.tar.md5 which I now know does not work with 5.11. Since then, bootloop. Reboots every minute or so. I've tried everything I can find, wiping everything, flashing what purport to be stock ROMs, putting TWRP on there, and still within a minute of booting it reboots. I tried installing Smart Switch, but it can't get a connection because the phone just won't stay booted.
Rooting would be nice, but I just want my phone to work again. What can I do here? I don't have insurance and KNOX is flipped.

if you're sure you are on 5.1.1, flash any kernel (unikernel v8, etc.) that would fix your issue.

I should mention this is a SM-G920P, if that's significant.
I flashed the stock package through Odin, then TWRP, then installed Hacker Kernel through that. It's still rebooting repeatedly while i try to go through the initial setup process, and dumping me at the language select each time.
I tried unikernel too, didn't work either.

Okay, here's my current process, which is not working.
Boot to ODIN/Download mode, by holding power+volume down+home.
Open Odin 3.10.6, as administrator. Auto-Reboot is unchecked.
Flash what's supposed to be the latest stock rom, obtained here.
Wait until it says PASS, then reboot into ODIN mode again.
Flash the TWRP 2.8.7.0 tar, obtained here.
Wait until it says PASS, then reboot into recovery, by holding power+volume down+home until it reboots and then power+volume up+home to enter recovery.
Wipe Data/Cache/Darvik.
Transfer Hacker Kernel and SuperSU .zips, obtained here, to storage on phone.
Use TWRP to install Hacker Kernel, as instructed on that page.
Reboot into recovery.
Use TWRP to install Super SU. Note: In the section of the log reading Boot Image Patcher, I get Extracting ramdisk, Decompressing ramdisk, Failure, aborting. Important?
Reboot.
Now it's sitting on the Samsung Galaxy S6 screen, and not going any farther than that.

I tried flashing nothing but the stock 5.1.1 package, but that's not working either. It still keeps rebooting, and it won't ever get past the screen that says "Preparing your device for first-time use... This may take 3 or 4 minutes." Is there anything I can do? I can't afford to not have a phone and I can't afford to replace this one. Please, help me.

I've redownloaded everything, checking md5 sums, and those are all correct. Flashing the BOL1 stock gets me rebooting, flashing it and then Unikernel v8 gets me rebooting, flashing it and then Unikernel v9 gets me rebooting, flashing it and then Unikernel v9 and then TWRP has me rebooting.
It boots up and stays up for a minute or two, enough to get a little ways into the setup. The first boot, it stays on the Sprint screen for a while, then reboots after about a second on the language select screen. When it gets back there, I can select language, connect to wifi, accept the EULA, and then wait on the "Preparing your device for first-time use" screen for a little while before it reboots. Sometimes it'll get as far as asking me if I want to let Google collect diagnostic data.

Hardware issue...i had the same issue with similar process. I had to get a replacement phone

Is it possible that trying to install the Chainfire root package on a 5.11 phone just broke something permanently? Could it be something partition-related, maybe? I'm at a total loss here.

This should help
kafziel83 said:
Is it possible that trying to install the Chainfire root package on a 5.11 phone just broke something permanently? Could it be something partition-related, maybe? I'm at a total loss here.
Click to expand...
Click to collapse
I had the same issue also with the SM-G920P.
Problems:
*unikernal > v6 (v7 and above == bootloop)
*hackerkernal on non-teamsprint rom == bootloop
*cf auto root was not required for root
What fixed it for me:
1. Odin back to stock 5.1.1
2. Flash TWRP
3. Boot into recovery
4. Reboot (it should tell you that root is not installed or something like that, so if it asks to install root let it)
5. Once booted into os SuperSU will tell you to update the su binary, update then reboot
6. Congratulations you have root.

lodbldbol said:
I had the same issue also with the SM-G920P.
Problems:
*unikernal > v6 (v7 and above == bootloop)
*hackerkernal on non-teamsprint rom == bootloop
*cf auto root was not required for root
What fixed it for me:
1. Odin back to stock 5.1.1
2. Flash TWRP
3. Boot into recovery
4. Reboot (it should tell you that root is not installed or something like that, so if it asks to install root let it)
5. Once booted into os SuperSU will tell you to update the su binary, update then reboot
6. Congratulations you have root.
Click to expand...
Click to collapse
Did 1, did 2, did 3, did 4 but it didn't give any message like that, and now it's just repeating the "Samsung Galaxy S6 Powered By Android" screen over and over.
Unless when you say "Odin back to stock 5.1.1" you mean flashing 5.1.1 and then going through the setup to a functioning OS, because I have never been able to do that since I started.

kafziel83 said:
Did 1, did 2, did 3, did 4 but it didn't give any message like that, and now it's just repeating the "Samsung Galaxy S6 Powered By Android" screen over and over.
Unless when you say "Odin back to stock 5.1.1" you mean flashing 5.1.1 and then going through the setup to a functioning OS, because I have never been able to do that since I started.
Click to expand...
Click to collapse
To Odin back to stock 5.1.1 properly follow the steps on this page exactly with the files it tells you to use http://www.androidrootz.com/2015/05/how-to-unroot-galaxy-s6-and-s6-edge.html
Then you'll need a ROM, i recommend this http://forum.xda-developers.com/spr...ment/ram9200-ofe-rom-thread-v3-5-1-1-t3173417
Once in recovery flash it (skip to step 7 in the link) then boot up, if that doesn't work I don't know what will.

Tried that, now it boots as far as the Sprint screen but hangs there and then reboots.

kafziel83 said:
Tried that, now it boots as far as the Sprint screen but hangs there and then reboots.
Click to expand...
Click to collapse
Hardware issue

Any advice on getting a replacement? I still have about $500 left on the monthly installments for this phone, and I don't have insurance. The Sprint stores I went to said to go to Samsung for a replacement for a malfunctioning phone, since I've had it for less than a year, since KNOX is flipped I'm guessing Samsung won't give me a thing.

I uploaded a file to Mediafire called 2016-03-20--04-15-35_G920P_Renegade_OJ7_v1.zip
This is a TWRP backup of my phone's system/radio/boot/efs, it should replace anything that doesn't work. I don't know if it'll work but it's worth a try.
Copy the zipped folder to TWRP/BACKUPS and restore your phone

Okay. Can you link to the mediafire page to download it?

kafziel83 said:
Okay. Can you link to the mediafire page to download it?
Click to expand...
Click to collapse
No, XDA won't let me put links to outside websites until I have 10 posts.

Same Problem
kafziel83 said:
Okay. Can you link to the mediafire page to download it?
Click to expand...
Click to collapse
Hi,
Same problem here,
Did you find a solution for your problem?

lodbldbol said:
I uploaded a file to Mediafire called 2016-03-20--04-15-35_G920P_Renegade_OJ7_v1.zip
This is a TWRP backup of my phone's system/radio/boot/efs, it should replace anything that doesn't work. I don't know if it'll work but it's worth a try.
Copy the zipped folder to TWRP/BACKUPS and restore your phone
Click to expand...
Click to collapse
If ever the EFS is cleared, deleted whatever. It re-builds from block 12, so there's no need to worry too much.
Sent from my SM-G925P using XDA Labs
---------- Post added at 10:12 AM ---------- Previous post was at 10:09 AM ----------
kbashiri said:
Hi,
Same problem here,
Did you find a solution for your problem?
Click to expand...
Click to collapse
I would do a quick repartition, nand erase all, flash stock ROM boot it, and flash from there. Hope it goes well.
Sent from my SM-G925P using XDA Labs

Please Help
ChubbbySquish said:
If ever the EFS is cleared, deleted whatever. It re-builds from block 12, so there's no need to worry too much.
Sent from my SM-G925P using XDA Labs
---------- Post added at 10:12 AM ---------- Previous post was at 10:09 AM ----------
I would do a quick repartition, nand erase all, flash stock ROM boot it, and flash from there. Hope it goes well.
Sent from my SM-G925P using XDA Labs
Click to expand...
Click to collapse
Should I do re-partition then nand erase all and then flash rom or should I do them altogether?

No data for MTK Device

Hi there guys!:fingers-crossed:
I've tried to install a couple of Project Treble roms, however it seems that all of them have the same issue, they don't connect to the mobile connection ( by Vodafone RO, if it's relevant in any way).
I've configured the APN and contacted the carrier and they took a shot at it as well, but to no avail.
I've also noticed that i can send messages however but I'm not receiving any.
The phone is a Umidigi One with MTK6763.
Thanks in advance!

CSI.ISC said:
Hi there guys!:fingers-crossed:
I've tried to install a couple of Project Treble roms, however it seems that all of them have the same issue, they don't connect to the mobile connection ( by Vodafone RO, if it's relevant in any way).
I've configured the APN and contacted the carrier and they took a shot at it as well, but to no avail.
I've also noticed that i can send messages however but I'm not receiving any.
The phone is a Umidigi One with MTK6763.
Thanks in advance!
Click to expand...
Click to collapse
Hey there! I am in the same boat. I have Poptel P60 which also has MT6763. All the symptoms match. Also tried a couple of rooms to no avail including 8.1 and 9.0 ones. Octopus ROM's recent change log mentioned something about Mtk RIL but also cannot get mobile data to work.
I'm noticing that after some time (and maybe some combination of reinserting sim and other things) I see some activity on the mobile connection indicator but still no working data. Double checked and tried different sets of APNs. Nothing
I'm hoping somebody has some suggestions... please let me know if you learn anything and I will, too. Manufacturers GUI is horrid and punishes you for rooting...
Maybe we could submit a bug ticket.

Does data work on any 8.1 treble ROM this phone will be worth it if I can get 9.0 data working but I'll settle for omni ROM or rr remix

No data, unable calls, incorrect network name (KDDI and SoftBank SIM)
Hello.
I'm facing this issue too.
I flashed many GSI ROM to Umidigi One (MT6763), SIM card detected but no data and unable calls.
Network state is always showing "No service - Emergency calls only".
I'm using KDDI SIM 4G VoLTE type.
When I'm using stock ROM, data and VoLTE calling are fully working after apn settings.:good:
I entered *#*#4636#*#* command network testing screen. in stock ROM, current network shown carrier name "KDDI" but I after flashed other ROM, it showing up weird number "44051". is this normally?
I tried friend's SoftBank SIM, it showing up correctly "SoftBank" but still no data and unable calls.
How can I make a mobile connection in other roms??
Sorry my poor English... I using Google Translate and post from Japan.
Thanks.

I am also facing this issue bro i have mt6739 chipset

I have mt6762 (helio p22)
Isee similar problem. Aosp 9.0 flashed and booted without any cell signal.
In order for my device to have working twrp, I needed to pay dm_verity. And I also removed forceencrtpt. I have read a comment that this encrypt change could be the cause of not connecting to cell signal.
I tested this a little. I flashed gsi with encryption still set to force. I was then able to have cell signal. But!!!!!!!!, There was many many apps and system force closeing.
Keyboard
Bluetooth
Settings,
Gallery
Camera
Etc , all repeated crash.

Can anyone tested gsi without encryption ?

facing the same issue here on mt6763 chipset. if i only flash the treble roms (i dont have twrp which mounts system and vendor so i only flash treble roms 9.0 versions via fastboot), after flashing call and mobile data including LTE works fine. I ported twrp for my phone with twrp porter windows app.. anytime i flash it... networks and data doesnt work anymore. i guess it is so because the twrp only boots to DECRYPTION UNSUCCESSFUL page so i cant use the phone with the twrp flashed... i have to restore stock recovery to boot pass the decrytion error page,, which ofcourse also encrypts the phone again. So now, i think the problem is my twrp, does anyone have a better working twrp for 6763 and 4.4.95+ kernel. Why does flashing twrp breaks the network connection??

puflynx said:
facing the same issue here on mt6763 chipset. if i only flash the treble roms (i dont have twrp which mounts system and vendor so i only flash treble roms 9.0 versions via fastboot), after flashing call and mobile data including LTE works fine. I ported twrp for my phone with twrp porter windows app.. anytime i flash it... networks and data doesnt work anymore. i guess it is so because the twrp only boots to DECRYPTION UNSUCCESSFUL page so i cant use the phone with the twrp flashed... i have to restore stock recovery to boot pass the decrytion error page,, which ofcourse also encrypts the phone again. So now, i think the problem is my twrp, does anyone have a better working twrp for 6763 and 4.4.95+ kernel. Why does flashing twrp breaks the network connection??
Click to expand...
Click to collapse
Just reboot to recovery mode when you see dycryption unsuccessful and perform normal factory reset and then reboot

chandan2000 said:
Just reboot to recovery mode when you see dycryption unsuccessful and perform normal factory reset and then reboot
Click to expand...
Click to collapse
it doesnt change anything. decryption unsuccessful still shows. i flashed the ported twrp on my stock an hour ago and realized sim cards dont work anymore. by the way, right after installing twrp i wipe data and install no verity opt encrypt zip but still. My boot and recovery images are all secured in the stock OS. could the secured img be the cause??

puflynx said:
it doesnt change anything. decryption unsuccessful still shows. i flashed the ported twrp on my stock an hour ago and realized sim cards dont work anymore. by the way, right after installing twrp i wipe data and install no verity opt encrypt zip but still. My boot and recovery images are all secured in the stock OS. could the secured img be the cause??
Click to expand...
Click to collapse
Flash this file after that reboot to recovery and format data and reboot if you see dycryption unsuccessful then reboot to recovery on the screen which you are perform normal factory reset

chandan2000 said:
Flash this file after that reboot to recovery and format data and reboot if you see dycryption unsuccessful then reboot to recovery on the screen which you are perform normal factory reset
Click to expand...
Click to collapse
Right but if i successfully get passed the decryption unsuccessful page...sim cards dont work on the phone anymore. does that mean any attempt to decrypt my stock boot/kernel/recovery brings up connectivity issues.?? thinking out loud. and how do i properly get rid of encryption from my stock rom?

puflynx said:
Right but if i successfully get passed the decryption unsuccessful page...sim cards dont work on the phone anymore. does that mean any attempt to decrypt my stock boot/kernel/recovery brings up connectivity issues.?? thinking out loud. and how do i properly get rid of encryption from my stock rom?
Click to expand...
Click to collapse
Flash this file while in recovery mode https://drive.google.com/file/d/1VCgNLByeUQRkX_amZg1u8eypQL3osd3C/view?usp=drivesdk and then format data also select rm-rf instead of formatting option in twrp setting

ok thank you for the file but i have seen vendor in the files.. So before i flash i have to let you know.. my twrp fails to mount vendor... i remember flashing magisk 16.4 for treble roms but i got an error.... unable to mount/system/vendor...... due to this i couldnt root my treble rom.
ok it flashed successfully but please tell me exactly how the process is because i still get decryption unsuccessful. At which point should i select rm-rfs instead of formatting in twrp setting... is it before or after flashing the file.......

puflynx said:
ok thank you for the file but i have seen vendor in the files.. So before i flash i have to let you know.. my twrp fails to mount vendor... i remember flashing magisk 16.4 for treble roms but i got an error.... unable to mount/system/vendor...... due to this i couldnt root my treble rom.
ok it flashed successfully but please tell me exactly how the process is because i still get decryption unsuccessful. At which point should i select rm-rfs instead of formatting in twrp setting... is it before or after flashing the file.......
Click to expand...
Click to collapse
First flash the file after that select rm-rf instead of formatting option in twrp then go to wipe section and format data then reboot after that if you seen decryption unsuccessful then shutdown your phone and reboot to twrp and do a normal factory reset
---------- Post added at 05:00 AM ---------- Previous post was at 04:59 AM ----------
puflynx said:
ok thank you for the file but i have seen vendor in the files.. So before i flash i have to let you know.. my twrp fails to mount vendor... i remember flashing magisk 16.4 for treble roms but i got an error.... unable to mount/system/vendor...... due to this i couldnt root my treble rom.
ok it flashed successfully but please tell me exactly how the process is because i still get decryption unsuccessful. At which point should i select rm-rfs instead of formatting in twrp setting... is it before or after flashing the file.......
Click to expand...
Click to collapse
R u rooted or not ?
---------- Post added at 05:03 AM ---------- Previous post was at 05:00 AM ----------
Use carlive image kitchen from pc and unpack twrp then edit fstab file

chandan2000 said:
First flash the file after that select rm-rf instead of formatting option in twrp then go to wipe section and format data then reboot after that if you seen decryption unsuccessful then shutdown your phone and reboot to twrp and do a normal factory reset
---------- Post added at 05:00 AM ---------- Previous post was at 04:59 AM ----------
R u rooted or not ?
---------- Post added at 05:03 AM ---------- Previous post was at 05:00 AM ----------
Use carlive image kitchen from pc and unpack twrp then edit fstab file
Click to expand...
Click to collapse
i am rooted please. so to go over the decryption error, do i allow twrp system modification or i should keep it read only before i flash the file??
secondly, i am happy you brought the unpacking twrp up... i dont know how my stock imgs were coded because i dont find fstab in both my recovery and boot img. Please check attachment for unpacking files

puflynx said:
i am rooted please. so to go over the decryption error, do i allow twrp system modification or i should keep it read only before i flash the file??
secondly, i am happy you brought the unpacking twrp up... i dont know how my stock imgs were coded because i dont find fstab in both my recovery and boot img. Please check attachment for unpacking files
Click to expand...
Click to collapse
Send me your twrp recovery img file and also stock recovery img file bro i will try to help you
---------- Post added at 09:30 AM ---------- Previous post was at 09:28 AM ----------
puflynx said:
i am rooted please. so to go over the decryption error, do i allow twrp system modification or i should keep it read only before i flash the file??
secondly, i am happy you brought the unpacking twrp up... i dont know how my stock imgs were coded because i dont find fstab in both my recovery and boot img. Please check attachment for unpacking files
Click to expand...
Click to collapse
If you'r twrp not working properly you cant be able to decrypt your phone
---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------
You can also edit it yourself just go to ramdisk folder then etc you will find recovery.fstab file edit it according to your stock recovery img recovery.fstab file

chandan2000 said:
Send me your twrp recovery img file and also stock recovery img file bro i will try to help you
---------- Post added at 09:30 AM ---------- Previous post was at 09:28 AM ----------
If you'r twrp not working properly you cant be able to decrypt your phone
---------- Post added at 09:32 AM ---------- Previous post was at 09:30 AM ----------
You can also edit it yourself just go to ramdisk folder then etc you will find recovery.fstab file edit it according to your stock recovery img recovery.fstab file
Click to expand...
Click to collapse
i appreciate your help so very much but i would rather forward you the files, i believe you know best. however, i have also attached a picture fo files in stock rom... because i can also see ramdisk-recovery.img files in there as well
here is a personal link to the files.
https://drive.google.com/drive/folders/1Hdyh3ZtysayWl1qAHFHjgDzzoEJjVdMv?usp=sharing

Get the file bro
https://drive.google.com/file/d/1k2UhVhtFFIkv8eVrP-kI9_GrlQcpCC-S/view?usp=drivesdk

chandan2000 said:
Get the file bro
https://drive.google.com/file/d/1k2UhVhtFFIkv8eVrP-kI9_GrlQcpCC-S/view?usp=drivesdk
Click to expand...
Click to collapse
wow that was fast but i flash twrp,,,whether or not i swipe to allow modification,,, i flash the file (patch_uncryptable.zip), i select rm-rf instead of formatting, go to wipe, select format data, type yes and boom..... failed to mount /data (invalid argument) , unable to format to remove encryption, updating partition details........, failed to mount /data (invalid argument)..... done.
this is what happens bro