Related
As a general FYI, if you think you need to repartition your phone it is also possible that your phone has experienced:
a) A hardware issue, possibly partial or total emmc failure.
b) A mismatch between bootloader (sboot.bin) and trustzone (tz.img) versions. See this post or my MK6 stock thread for some possible options to fix this.
As a step of last resort to recreate the partition table on your phone, a pit file may be what you need. This can be done in either Odin or Heimdall.
Warning - repartitioning your phone may erase all data and might cause other unintended consequences. You assume all risk.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
To use a pit file in Odin, this is typically done as part of a flashing a stock rom package, like the LJ2 or MA4 package for the i317 (or similar package for the i317m). You specify the pit file in the PIT section, make sure the repartition box is checked, and then add the rom package in the PDA section like usual.
If you are running an official 4.3 or later bootloader you will not be able to successfully flash a stock firmware package that contains earlier bootloaders - Odin will hang and you will need to find a different stock package to flash that does not contain a bootloader. (i.e. If you took the the i317 4.3 OTA and are running the MK6 bootloader or a later bootloader, you'll want to avoid UCAMA4)
The attached zip includes pit files for both the i317 and the i317m. The partition mapping is the same for both (see the included analysis files), but the pit files have unique security signatures which are accepted only by the bootloader of the specific model phone for which they are intended. I've tested the file for the i317 and can confirm that it works as intended. The file for the i317m was pulled the same way by an XDA member (thanks @plemen !) with an i317m and I've confirmed it is formatted correctly. It has now been confirmed as working.
If you want to learn a bit more about pit files, check out this thread by Adam Outler:
http://forum.xda-developers.com/showthread.php?t=2540480
Very interested in this, as I need the pit file for my I317. Question about the bootloader, though.... I've never taken an OTA, just flashing CM and OmniROM nightlies (was on 4.4.2 when my phone committed suicide). Should I be safe to use this pit file? And what factory firmware would you recommend to go with it?
pit files should be back in a day or two (I'll be testing over the weekend).
Depending on what happened to your phone it's still highly probable that your pit (partition) data is fine. There's a way to confirm this using Heimdall - when time permits I'll add instructions to post #2. That's a safer first step than attempting a repartition.
As for bootloader and firmware - if you've never taken an OTA, and you're not on a 4.3 bootloader your best bet for stock firmware is UCAMA4. It's a more complete and somewhat newer package than the other option (UCALJ2). You can get this from sammobile, or a mirror copy I have linked in post #2 here:
http://forum.xda-developers.com/showthread.php?t=2589891
that post also has information on a couple apps you can load that will allow you to check which bootloader you have loaded once your phone is operational.
Thanks for doing this! Did you have any luck over the weekend? Looking to re-partition as I'm unable to mount.
anine said:
Thanks for doing this! Did you have any luck over the weekend? Looking to re-partition as I'm unable to mount.
Click to expand...
Click to collapse
I expected a test phone on Saturday that didn't arrive until Tuesday thanks to the USPS getting the day off on Monday. Once I confirm the files work as intended I will repost them.
As for the issue you are having - what partition isn't mounting? Can you provide more detail?
Zen Arcade said:
I expected a test phone on Saturday that didn't arrive until Tuesday thanks to the USPS getting the day off on Monday. Once I confirm the files work as intended I will repost them.
As for the issue you are having - what partition isn't mounting? Can you provide more detail?
Click to expand...
Click to collapse
The Note 2 (ATT) suddenly rebooted and stuck on the "Samsung Galaxy Note 2" screen. A couple reboots and a battery pull did not solve the issue. I even let the phone stay on the screen in the event it needed to do some sort of repair.. but after an hour, nothing changed.
I loaded CWM recovery and got recovery mount errors. Also, I am unable to mount any of the internal file system when attempting from the advanced menu. After a couple of hours of following tutorials I went into download mode and installed the stock ATT rom. It was successful but still did not boot (attempted this twice). I came upon a few suggestions for similar issues that said the PIT file was needed to repartition. I used Beanstalk 4.4.2 before the crash.
Help
anine said:
The Note 2 (ATT) suddenly rebooted and stuck on the "Samsung Galaxy Note 2" screen. A couple reboots and a battery pull did not solve the issue. I even let the phone stay on the screen in the event it needed to do some sort of repair.. but after an hour, nothing changed.
I loaded CWM recovery and got recovery mount errors. Also, I am unable to mount any of the internal file system when attempting from the advanced menu. After a couple of hours of following tutorials I went into download mode and installed the stock ATT rom. It was successful but still did not boot (attempted this twice). I came upon a few suggestions for similar issues that said the PIT file was needed to repartition. I used Beanstalk 4.4.2 before the crash.
Click to expand...
Click to collapse
I desperately need this PIT file as well.. not on 4.3 however..I can get to download mode and into recovery but it spits a bunch of errors about unable to mount /cache etc...
anine said:
The Note 2 (ATT) suddenly rebooted and stuck on the "Samsung Galaxy Note 2" screen. A couple reboots and a battery pull did not solve the issue. I even let the phone stay on the screen in the event it needed to do some sort of repair.. but after an hour, nothing changed.
I loaded CWM recovery and got recovery mount errors. Also, I am unable to mount any of the internal file system when attempting from the advanced menu. After a couple of hours of following tutorials I went into download mode and installed the stock ATT rom. It was successful but still did not boot (attempted this twice). I came upon a few suggestions for similar issues that said the PIT file was needed to repartition. I used Beanstalk 4.4.2 before the crash.
Click to expand...
Click to collapse
The symptoms you describe are similar to those I've seen on the Q&A forum recently. I don't want to be the bearer of bad tidings, but I suspect you have a partial emmc (hardware) failure.
My time during the week is limited so I expect to have testing done this weekend.
terpencar said:
I desperately need this PIT file as well.. not on 4.3 however..I can get to download mode and into recovery but it spits a bunch of errors about unable to mount /cache etc...
Click to expand...
Click to collapse
I had similar issue, and was able to resolve it by following this thread. YOu need to restore factory original by following this thread from XDA.
Please don't forget to Thank
The files provided are only for phone I317 and not I317M
http://www.androidfilehost.com/?fid=23060877490003986
Instructions:
1. Download "back to stock" zip folder I uploaded. It contains all the files needed. No need to search around.
2. Unzip the file and extract the folder to your desktop.
3. Open folder and install Samsung drivers if not already done so.
4. Now make sure you have root and custom recovery on the phone. Turn the phone off. Hold volume up, home and power button at the same time.Wait till u see custom recovery screen and then let go off all the buttons.
5. Once in recovery... delete data, system, cache, dev cache like you want to flash a new rom. Turn the phone off by pulling the battery or see option for power off device under custom recovery.
6. Once the phone is completely off lets get into download mode. Hold volume down, home and power button until you see the screen with an option to press volume up to get into download. Press volume up to enter download mode when asked.
7. Now open odin3.07 I provided in the folder u downloaded. Once open connect your phone via usb. Windows should install device drivers. Once thats done, you should see com## on the Odin software.
8. On odin software you should see button called PDA. Click on it and browse to the file called KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user _low_ship.tar. in the folder provided by me. select it and hit ok. Odin will process the file. It will take max 2 to 3 min.
9. Before you click start on Odin make sure auto reboot and F. reset time is checked only. Everything else unchecked. Click start button. Odin will start flashing the factory firmware. It will take time.
10. Once Odin is done flashing. phone will reboot. Now you can disconnect the usb cable. When phone is fully rebooted, skip all the prompt and get to home screen.
11. Turn the phone off again and get into download mode. Connect usb cable to computer with Odin open. Click Pda and select file called CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar. Let Odin process it and then click start. Once flashing the root file is done. Phone should reboot to home screen. Now you have root. The reason we need root is to get rid of counter # in download more. It should say zero.
12. Connect your phone to computer while on the home screen. Open phone internal storage and go to download folder and copy Triangle away.apk into it.
13. Go into settings and security and check unknown sources.
14. Go to apps and open application "my file". Go to download folder and select triangle away application to install. install it. Open application application and scroll down and select reset counter option. Make sure your are connected to wifi. Confirm you phone is I317 and triangle away will download the file. Your phone should reboot into some type of reset counter recovery screen. follow the instruction on the screen to reset the counter. After that phone should reboot.
15. Once rebooted uninstall triangle away apk. Now open super user application and scrool down and click fully unroot. When done go into stock recovery and clear data and cache. reboot phone. All done. Your counter is set to zero. Your phone should read normal under settings.
You can update your phone under settings from att servers.
Enjoy.
Thanks to chainfire for his triangle away app and root for our device.
rob_z11 said:
I had similar issue, and was able to resolve it by following this thread. YOu need to restore factory original by following this thread from XDA.
Please don't forget to Thank
The files provided are only for phone I317 and not I317M
Instructions:
1. Download "back to stock" zip folder I uploaded. It contains all the files needed. No need to search around.
2. Unzip the file and extract the folder to your desktop.
3. Open folder and install Samsung drivers if not already done so.
4. Now make sure you have root and custom recovery on the phone. Turn the phone off. Hold volume up, home and power button at the same time.Wait till u see custom recovery screen and then let go off all the buttons.
5. Once in recovery... delete data, system, cache, dev cache like you want to flash a new rom. Turn the phone off by pulling the battery or see option for power off device under custom recovery.
6. Once the phone is completely off lets get into download mode. Hold volume down, home and power button until you see the screen with an option to press volume up to get into download. Press volume up to enter download mode when asked.
7. Now open odin3.07 I provided in the folder u downloaded. Once open connect your phone via usb. Windows should install device drivers. Once thats done, you should see com## on the Odin software.
8. On odin software you should see button called PDA. Click on it and browse to the file called KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user _low_ship.tar. in the folder provided by me. select it and hit ok. Odin will process the file. It will take max 2 to 3 min.
9. Before you click start on Odin make sure auto reboot and F. reset time is checked only. Everything else unchecked. Click start button. Odin will start flashing the factory firmware. It will take time.
10. Once Odin is done flashing. phone will reboot. Now you can disconnect the usb cable. When phone is fully rebooted, skip all the prompt and get to home screen.
11. Turn the phone off again and get into download mode. Connect usb cable to computer with Odin open. Click Pda and select file called CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar. Let Odin process it and then click start. Once flashing the root file is done. Phone should reboot to home screen. Now you have root. The reason we need root is to get rid of counter # in download more. It should say zero.
12. Connect your phone to computer while on the home screen. Open phone internal storage and go to download folder and copy Triangle away.apk into it.
13. Go into settings and security and check unknown sources.
14. Go to apps and open application "my file". Go to download folder and select triangle away application to install. install it. Open application application and scroll down and select reset counter option. Make sure your are connected to wifi. Confirm you phone is I317 and triangle away will download the file. Your phone should reboot into some type of reset counter recovery screen. follow the instruction on the screen to reset the counter. After that phone should reboot.
15. Once rebooted uninstall triangle away apk. Now open super user application and scrool down and click fully unroot. When done go into stock recovery and clear data and cache. reboot phone. All done. Your counter is set to zero. Your phone should read normal under settings.
You can update your phone under settings from att servers.
Enjoy.
Thanks to chainfire for his triangle away app and root for our device.
Click to expand...
Click to collapse
Thanks.. It just hangs at system.img in odin
Nice job Zen
Sent from my SGH-I317 using XDA Premium 4 mobile app
Pit files are back up and attached to the OP. The i317 pit file is tested and confirmed working.
The i317m file is identical, except for the security signature. I'm currently looking for someone with a healthy i317m willing to test flash the i317m pit file to confirm it works. (I would do this myself, but I don't have an i317m).
Unfortunately it did not work for me. emmc failure suspected. Strange thing is that in ODIN I can still "Successfully" install a ROM.. and even the PIT file succeeded. I still got a logo screen for several minutes.
Fortunately for me, I have an additional mainboard from a otherwise damaged note 2. I'll be swapping that out.
Thank you anyway. Hope your file helps others!
My phone was not booting and stopped at Samsung logo. After the pit file and stock rom, my phone is live again. I am still having issue with storage but at least I have good starting point.
thanks
Works fine on i317m
anine said:
Unfortunately it did not work for me. emmc failure suspected. Strange thing is that in ODIN I can still "Successfully" install a ROM.. and even the PIT file succeeded. I still got a logo screen for several minutes.
Fortunately for me, I have an additional mainboard from a otherwise damaged note 2. I'll be swapping that out.
Thank you anyway. Hope your file helps others!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2626593
qkster said:
http://forum.xda-developers.com/showthread.php?t=2626593
Click to expand...
Click to collapse
See posts #9 and #13 on the thread above for the specific potential solution to try.
Corrupt pit file it says. for note 2 att help
I have a Att note 2 i flash the mj9 firmware using mobile odin first. Then i formatted storage, data, system, and cache. And now its says i have NO ios Installed with is true but when i try flashing another rom in TWRP it fails iv'e try stock ATT, Jedi Rom, MeanBean Rom. now i tryed to flash stock firmware through J Odin but it always say corrupt pit file...Someone Please Help MEE
kumar_420 said:
I have a Att note 2 i flash the mj9 firmware using mobile odin first. Then i formatted storage, data, system, and cache. And now its says i have NO ios Installed with is true but when i try flashing another rom in TWRP it fails iv'e try stock ATT, Jedi Rom, MeanBean Rom. now i tryed to flash stock firmware through J Odin but it always say corrupt pit file...Someone Please Help MEE
Click to expand...
Click to collapse
Err mj9 is verizon haha
Sent from my lightning fast Note II running MeanBean 2.0 SuperCharged
Is there a way to switch from 5.0 to 4.4 while the phone is unrooted or would I have to root it in order for that to happen? Also if I have to root what would be the best way to do so and put back 4.4?
I am totally interested in this as well any step-by-step information would be highly appreciated
I would have to say no... you can flash back to 4.4... but need root to flash
Sent from my SM-N910P using Tapatalk
kaz007 said:
Is there a way to switch from 5.0 to 4.4 while the phone is unrooted or would I have to root it in order for that to happen? Also if I have to root what would be the best way to do so and put back 4.4?
Click to expand...
Click to collapse
Here's a step by step procedure to downgrade, make sure you backup your internal sd card contents because it requires a data/reset on 4.4. since lollipop encrypts internal storage.
Download these 3 files.
USB (Driver) ver.1.5.45.0 ( Latest as of this post ) from samsung.com/support, search for your device SM-N910P and choose your color, and select manuals and downloads
Odin v3.10.6, from rwilco12's website, HERE
N910PVPU1ANK2 .TAR file, from ViperBoy's thread in generals forum HERE
Save these files to your desktop within a folder called Note4Downgrade makes it easier to find.
Uninstall your previous drivers like old Samsung, Kies of any versions.
open the Odin zip file, drag and drop its contents into the Note4Downgrade folder.
Open the N910PVPU1ANK2 zip file, drag and drop the .tar file into the Note4Downgrade folder.
Install the latest Samsung drivers, no need to reboot your computer.
Open the Odin3.10.6 executable file, select PDA or AP slot and load in the NK2.tar file, it'll take awhile and the Odin program will freeze as the file that its loading is ~1.8 GB's.
In the mean time while this is being loaded, shutdown your Note 4 Device and go into download mode by pressing Volume Down, Home Button, and Power Button Simultaneously.
Hold it down until it starts up into an Android Logo Firmware screen, Next Press Volume Up to continue into the next dialogue.
Once the file is loaded into the Odin program, use the original Samsung USB cable and plug it into a USB 2.0 port ( No, Not 3.0, Sometimes it can cause issues and errors, its do-able, but not recommended. )
Have the Odin Program detect your device and Windows will install the device drivers. Once this is done, a word within a blue box will state this message up top.
[COM:##]
It does not matter on what the "##" is as long as that is reading a number, meaning Odin has recognized and detected your device.
Stop here and recheck your progress.
- Latest Samsung Drivers installed ( SM-N910P )
- Odin 3.10.6 with loaded N910PVPU1ANK2.tar inside the PDA or AP slot
- Device in download mode, plugged into a USB 2.0
- Odin with [COM:##] in a box.
Proceed to clicking the "START" button if you have all of your above progresses done.
This will take around 15-30 minutes of flashing the stock 4.4 firmware, this will not tick the KNOX switch if you haven't rooted your device already as this is stock firmware.
It'll auto reboot once it is done, First time boot up will take longer as it is loading the device for the "First Time".
Once you're done, and you're on the welcome screen of the device, power it off.
Now we need to do 2 sets of resets, data factory within recovery, and an internal SD card wipe through Backup and Reset menu within settings of the device.
Now go into the devices recovery by pressing these 3 buttons. Power UP, Home Button, and Power Button.
Hold it until you see blue text at the top left corner of your devices screen stating "REBOOTING RECOVERY. . . ."
Then you can let go.
LEGEND
- Volume buttons = up or down
- Power Button = Proceed into next dialogue
From here go into the wipe data/factory and reset the device.
Once done, do a cache wipe.
and lastly, reboot the device.
Once your device has been rebooted, skip all the welcome steps and go to home, pull down the notifications bar and select the setting button up top.
scroll down to storage and unmount your Ext SD Card and take it out ( If you have one! ), now back out and go within Back up and Reset under personalizations. checkbox wipe internal Card and factory data reset again.
Once its all done it'll reboot, now you're on the latest firmware of kitkat on the note 4.
I hope this will help you as well as others wanting to stay on kitkat for any reasons they have or if they run into issues on lollipop.
Your guide, simplified!
- Spark91
Awesommmme! Thanks for taking the time Spark!
Glad I've helped out!
Very thorough guide.
bought a note 4 (sm-n910p) from eBay thinking that i can use ssu.apk to sim unlock the device. It was on lollipop.
so i thought i can downgrade to 4.4 . unfortunately while flashing kitkat using odin i got a fail message .After that phone is showing ("firmware upgrade encountered an issue ")
i tried to flash stock lollipop firmware using odin sadly now it show { THERE IS NO PIT PARTITION } error .
the device is on oe1 build
I'm on N910PVPU3BOF5 will that work with my phone ?
zjor2000 said:
I'm on N910PVPU3BOF5 will that work with my phone ?
Click to expand...
Click to collapse
I think of5 has an updated bootloader and cannot be downgraded.
can anyone here tell me how to downgrade from 5.1 lollipop to kitkat? i tried downloading the kitkat firmware from sammobile and flashing it via odin but it fails
Go into recovery, select wipe, advanced wipe and then check cache, dalvik cache, data, internal storage(make a backup) and system. When that's done, power down your device, boot into download mode and flash stock kitkat rom via Odin. I hope this helps
First do a factory reset if you are not rooted
If you have root and twrp installed do as follows : go in twrp (power + vol up + home) select Wipe > advanced wipe and wipe everything except external sd
1. Go to this link http://www.sammobile.com/firmwares/database/SM-N7505/ and select your country then download a firmware 4.1.1 version.
>Note: Create a free account on the samsung page to get full download speed as provided by your ISP. Mine is 100 kpbs
2. Then download odin from here > http://odindownload.com/download/#.VxKXaVRxeFU > Scroll down and click Download now button which is blue color.
3. After you have downloaded your firmware extract it to your desktop, then extract odin
4. Run Odin3 v3.10.7 then click AP then browse where you extracted the firmware and select it and click open.
5. Wait for it as Odin will says not responding but patience.
6. After it fully loads then Switch off your phone,
boot in download mode ( Hold power and vol - and home )
then press vol + to continue
plug usb cable in phone and pc. see msg added in odin
then click start on odin. wait till your phone reboots. do not unplug until its fully booted.
7. Now you have kitkat again.
Hi,
Phone; SM-AF520F
My phone has been restarting on its own from the past month and I ignored it. It showed me occasionally Google services failed or system UI is not responding.
I factory resetted the phone as any noob would do and the restart occurrence went to only at night, which I was unbothered with. A little time passed and the phone went to the downloading sky blue screen.
I'm aware with flashing roms and stuff but I never really tried it. I tried everything;
i) Used Odin, three different versions
ii) Used Stock firmware, three different versions
iii) Used Smart switch
The phone only went in download phase and than in the phase where you press home button, volume and power and it shows fonts in the left hand corner. Odin always giving me errors, sometimes stucking on setting up connection.
Two errors:
i) There is no PIT partition
ii) Write operation failed
There are always these things happening.
When I restarted with volume down and power key, the system showed, there was an error and try smart switch, updated my drivers but when I go in the settings to emergency recover my phone, it does not show my phone.
After restarting the phone couple of time, Im in downloading mode again, in between the screen also turns full sky blue with no text.
I tried installing custom recovery but the image didn't load, ( I dont know what i am doing at this point, even if this was a good idea).
I have scavanged every forum, every post, everything on the internet but I just can't seem to fix it, I tried every possible thing and it just dosent work. I know it can be fixed but I don't know how. I know I'm doing something stupidly wrong but I can't seem to figure it out.
This is an old phone, I'm going to buy another one soon but I just hope it works for another week? Can I wipe the whole system and start from scratch (Which i dont know how to do).
Any type of help would be greatly appreciated, or just tell me to give up hope on it so I can just throw it away and move on.
1-Install 7zip application in windows
Then using 7zip, try to open file (in stock ROM files) -⇾ "CSC_ODD_***"
2-There is your phone pit file for a520f.
Extract that file and keep it between your stock Rom files.
3-Download the Odin from this link and open it:
https://dl2018.sammobile.com/Odin3-v3.14.4.zip
4-Go to download mode (blue screen) in your phone!
Add 4 part of your ROM to Odin.
Then in pit tab of Odin add your phone pit file!
5-In option tab of Odin toggle Re-Partition option.
6-click on start and wait until it shows a green icon and phone restarting!
It must be fixed!
matkali said:
1-Install 7zip application in windows
Then using 7zip, try to open file (in stock ROM files) -⇾ "CSC_ODD_***"
2-There is your phone pit file for a520f.
Extract that file and keep it between your stock Rom files.
3-Download the Odin from this link and open it:
https://dl2018.sammobile.com/Odin3-v3.14.4.zip
4-Go to download mode (blue screen) in your phone!
Add 4 part of your ROM to Odin.
Then in pit tab of Odin add your phone pit file!
5-In option tab of Odin toggle Re-Partition option.
6-click on start and wait until it shows a green icon and phone restarting!
It must be fixed!
Click to expand...
Click to collapse
Thank you for your response.
I did what you exactly said, previously it failed at the instant, now it moved one tab and than failed.
I tried the provided Odin, than tried two roms with, with the pit filed extracted and enabled re partition.
The error occurred: Complete(write) operation failed.
The error occurred every time I tried to flash, it never worked.
Do you think there is anything else to do?
Try this way to go download mode:
Press vol-down + power until phone restart
Then instantly press vol-up + Home + Power to going to download mode!
If it not works for you! You can use (eMMC programmer or easy JTAG) to writing rom on your phone memory (Last Option)!
I gave up on it and asked for professional help. Idk what he did, but he fixed the phone. It was sluggish at first but it works like a charm now.
It took 7 minutes to turn it on, than It said, there was an authorized user who tried to access your phone, use your previous email password to access your phone. I put it on my previous details and the works okay after some updates.
I wonder what he did? And i never knew android has a feature where if somone tries to reset your phone, google account locks it? Wow.
Is flashing a custom os a good idea? I'm afraid I'll brick it or something or just keep running one ui and wait for it to die again.
Thank you for your help btw, made me learn alot.
matkali said:
1-Install 7zip application in windows
Then using 7zip, try to open file (in stock ROM files) -⇾ "CSC_ODD_***"
2-There is your phone pit file for a520f.
Extract that file and keep it between your stock Rom files.
3-Download the Odin from this link and open it:
https://dl2018.sammobile.com/Odin3-v3.14.4.zip
4-Go to download mode (blue screen) in your phone!
Add 4 part of your ROM to Odin.
Then in pit tab of Odin add your phone pit file!
5-In option tab of Odin toggle Re-Partition option.
6-click on start and wait until it shows a green icon and phone restarting!
It must be fixed!
Click to expand...
Click to collapse
im having the exact same problem this guy has, installing a pit file will erase my data? if i use HOME_CSC will the pictures stay? i only care about the photos.
A lot of people rooted are having issues with DEX with either systemUI closing, systemuidex closing or the app only staying open on PC pr TV for a few seconds.
Please can anyone who is rooted please let me know if they can access DEX and if so - is it working for you?
Please show a pic of magisk front screen with version number and state your exact rooting procedure
Hopefully we can then find out what is breaking dex
UNLESS anyone knows what sort of log may diagnose the issue? I have a dumpstate/logcat but not sure what part im looking at
exocetdj said:
A lot of people rooted are having issues with DEX with either systemUI closing, systemuidex closing or the app only staying open on PC pr TV for a few seconds.
Please can anyone who is rooted please let me know if they can access DEX and if so - is it working for you?
Please show a pic of magisk front screen with version number and state your exact rooting procedure
Hopefully we can then find out what is breaking dex
UNLESS anyone knows what sort of log may diagnose the issue? I have a dumpstate/logcat but not sure what part im looking at
Click to expand...
Click to collapse
We're do I get root how to for the u version
The only version that is rooted is the B version. The international, European, and North American versions are not able to be rooted.
We have root on the B variant
I believe the issue is related to having the "Data" folder being decrypted - This "Decrypting" process is on step # 4 under the 2nd process "PROCESS IF COMING FROM STOCK A12"
I have tried the process without the "Formatting the data" step which allows me to boot with root + Dex working. The only issue is that I'm limited to storage, It's fixed to 32gb out of the original size(512gb). Is there a way to resolve the limited storage issue?
Note: If we decrypt the data(Format data via twrp), we are restricted to:
- Cannot share pics in Samsung Gallary
- Dex's system ui constantly crashes
- Cannot install apps such as games that requires external downloads from installing an apk
- GMail cannot download embed files from an email
- ETC anything related to storage within the data, we cannot access/delete/edit when the data is decrypted
lilplanet said:
I believe the issue is related to having the "Data" folder being decrypted - This "Decrypting" process is on step # 4 under the 2nd process "PROCESS IF COMING FROM STOCK A12"
I have tried the process without the "Formatting the data" step which allows me to boot with root + Dex working. The only issue is that I'm limited to storage, It's fixed to 32gb out of the original size(512gb). Is there a way to resolve the limited storage issue?
Note: If we decrypt the data(Format data via twrp), we are restricted to:
- Cannot share pics in Samsung Gallary
- Dex's system ui constantly crashes
- Cannot install apps such as games that requires external downloads from installing an apk
- GMail cannot download embed files from an email
- ETC anything related to storage within the data, we cannot access/delete/edit when the data is decrypted
Click to expand...
Click to collapse
Thats some great info thanks very much
although that would also effect the download and install of Magisk potentially and that works - do you have an example of an app or game doing this so i can test?
i can confirm i cannot share pics directly from gallery but can within apps such as telegram
Downloading docs from Gmail is buggered
Dex is RIP.
@ianmacd do you think there is something we could be missing - we are effectively doing the disabler's job manually on F926B and its not unreasonable to think we may have missed something - could running the multidisabler be useful to see if it picks something up (even if it completely breaks things) so that we can then do the required modification manually?
exocetdj said:
Thats some great info thanks very much
although that would also effect the download and install of Magisk potentially and that works - do you have an example of an app or game doing this so i can test?
i can confirm i cannot share pics directly from gallery but can within apps such as telegram
Downloading docs from Gmail is buggered
Dex is RIP.
@ianmacd do you think there is something we could be missing - we are effectively doing the disabler's job manually on F926B and its not unreasonable to think we may have missed something - could running the multidisabler be useful to see if it picks something up (even if it completely breaks things) so that we can then do the required modification manually?
Click to expand...
Click to collapse
Me again
BVA9 STOCKRooted !
No sharing issues , and 100% working DEX
I used your BL file , extracted recovery from your AP File to make an Odin flashable TWRP.tar to sideload and flash your app-debug.zip
pvillasuso said:
Me again
BVA9 STOCKRooted !
No sharing issues , and 100% working DEX
I used your BL file , extracted recovery from your AP File to make an Odin flashable TWRP.tar to sideload and flash your app-debug.zip
Click to expand...
Click to collapse
whats your internal storage size? and have you reset device since you last managed to get this working?
Yes , I have reseted the phone.
When flashing to stock I used CSC ( the one that wipes data )
Did a stock recovery factory reset and also format data when I used the twrp recovery .
There is something with wrong with your AP file Bro , because I first used that file , and I tried the camera and had the sharing issue . Same happened with your older build , So I think the problem is there.
I Have the 256gb version
pvillasuso said:
Yes , I have reseted the phone.
When flashing to stock I used CSC ( the one that wipes data )
Did a stock recovery factory reset and also format data when I used the twrp recovery .
There is something with wrong with your AP file Bro , because I first used that file , and I tried the camera and had the sharing issue . Same happened with your older build , So I think the problem is there.
I Have the 256gb version
Click to expand...
Click to collapse
Ok sounds promising
Please can you provide a step by step procedure here and if i can replicate it i will amend the first post and files in the rooting thread
looks like formatting in TWRP could be the issue then - and we need to format at a different stage? (please still provide full process)
exocetdj said:
looks like formatting in TWRP could be the issue then - and we need to format at a different stage? (please still provide full process)
Click to expand...
Click to collapse
Yes , do that factory reset from stock recovery .
I also think the twrp format is not working as expected
edit : about the full process...
I ended again in a mess , and did several random stuff (as I got stuck some times in Download mode)
But .. If you ask me what I think that works , it would be like this:
1. Flash odin to stock , NOT using HOME_CSC
2. Do the initial setup (usb debugging and OEM status ( if shown ) checked
3. Flash odin the BL file , and TWRP.tar
4. TWRP , format ( I think nothing happened in this step ), reboot to TWRP , sideload and flash app-debug.zip
5. Reboot to download mode and flash stock recovery , and do the factory reset there ( at this step I tought I woud lose the previously flashed magisk stuff , but that didnt happen, and I got booted & rooted )
******
So I'm sure the BL file helped me to flash TWRP , because I tried it alone (TWRP) and it didn't work ( got bootloops ending in download mode ).
What I didn't try , now that Im reading myself , was to do a factory reset from stock , after doing that initial setup , and tried to flash that TWRP file right after that.
links to files :
AP_twrp_F926B_A12_BVA9
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
AP_stockrecovery_F926B_A12_BVA9
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
pvillasuso said:
Yes , do that factory reset from stock recovery .
I also think the twrp format is not working as expected
edit : about the full process...
I ended again in a mess , and did several random stuff (as I got stuck some times in Download mode)
But .. If you ask me what I think that works , it would be like this:
1. Flash odin to stock , NOT using HOME_CSC
2. Do the initial setup (usb debugging and OEM status ( if shown ) checked
3. Flash odin the BL file , and TWRP.tar
4. TWRP , format ( I think nothing happened in this step ), reboot to TWRP , sideload and flash app-debug.zip
5. Reboot to download mode and flash stock recovery , and do the factory reset there ( at this step I tought I woud lose the previously flashed magisk stuff , but that didnt happen, and I got booted & rooted )
******
So I'm sure the BL file helped me to flash TWRP , because I tried it alone (TWRP) and it didn't work ( got bootloops ending in download mode ).
What I didn't try , now that Im reading myself , was to do a factory reset from stock , after doing that initial setup , and tried to flash that TWRP file right after that.
links to files :
AP_twrp_F926B_A12_BVA9
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
AP_stockrecovery_F926B_A12_BVA9
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
do you have stock recovery or TWRP installed now you have root?
exocetdj said:
do you have stock recovery or TWRP installed now you have root?
Click to expand...
Click to collapse
Stock recovery now
I can try to flash twrp , and can go back to stock recovery if it doesnt work
exocetdj said:
do you have stock recovery or TWRP installed now you have root?
Click to expand...
Click to collapse
the key is that if you install TWRP now and dex and file sharing etc etc is still working then i need to look at these files
As far as im aware = the DEX issues are a result of having TWRP installed
exocetdj said:
the key is that if you install TWRP now and dex and file sharing etc etc is still working then i need to look at these files
As far as im aware = the DEX issues are a result of having TWRP installed
Click to expand...
Click to collapse
Well, then I can try to install twrp , and launch DEX to see how it goes
Be right back and let you know
edit :
Flashed TWRP successfully !
No sharing issues , Dex working fine !
pvillasuso said:
Well, then I can try to install twrp , and launch DEX to see how it goes
Be right back and let you know
edit :
Flashed TWRP successfully !
No sharing issues , Dex working fine !
Click to expand...
Click to collapse
ok so i am now rooted with stock recovery and everything is working - Dex, sharing etc etc
so i am missing TWRP
please can you go into finer detail into what you then did to install TWRP i need to have as much information as possible - please also confirm if you can mount data and flash files in TWRP if not then there is not really much point in having TWRP installed - i am thinking this is unlikely as you have not disabled forcencryption
I have managed to follow this far
1. Flash odin to stock , NOT using HOME_CSC
2. Do the initial setup (usb debugging and OEM status ( if shown ) checked
3. Flash odin the BL file , and TWRP.tar
4. TWRP , format ( I think nothing happened in this step ), reboot to TWRP , sideload and flash app-debug.zip
5. Reboot to download mode and flash stock recovery , and do the factory reset there ( at this step I tought I woud lose the previously flashed magisk stuff , but that didnt happen, and I got booted & rooted )
I am now rooted with stock recovery - i find it hard to see how we can just install TWRP and use it normally and mount /data without having to at least destroy user data each boot as forcencrypt has NOT been disabled
what is making things far too hard is a process that follows things like this:
"
edit : about the full process...
I ended again in a mess , and did several random stuff (as I got stuck some times in Download mode)
But .. If you ask me what I think that works , it would be like this: "
there are just too many variables - for instance, forceencryption could have been disabled without you realizing when doing the random bits - did you reflash my AP files at any point?
exocetdj said:
ok so i am now rooted with stock recovery and everything is working - Dex, sharing etc etc
so i am missing TWRP
please can you go into finer detail into what you then did to install TWRP i need to have as much information as possible - please also confirm if you can mount data and flash files in TWRP if not then there is not really much point in having TWRP installed - i am thinking this is unlikely as you have not disabled forcencryption
I have managed to follow this far
1. Flash odin to stock , NOT using HOME_CSC
2. Do the initial setup (usb debugging and OEM status ( if shown ) checked
3. Flash odin the BL file , and TWRP.tar
4. TWRP , format ( I think nothing happened in this step ), reboot to TWRP , sideload and flash app-debug.zip
5. Reboot to download mode and flash stock recovery , and do the factory reset there ( at this step I tought I woud lose the previously flashed magisk stuff , but that didnt happen, and I got booted & rooted )
I am now rooted with stock recovery - i find it hard to see how we can just install TWRP and use it normally and mount /data without having to at least destroy user data each boot as forcencrypt has NOT been disabled
what is making things far too hard is a process that follows things like this:
"
edit : about the full process...
I ended again in a mess , and did several random stuff (as I got stuck some times in Download mode)
But .. If you ask me what I think that works , it would be like this: "
there are just too many variables - for instance, forceencryption could have been disabled without you realizing when doing the random bits - did you reflash my AP files at any point?
Click to expand...
Click to collapse
I agree with you about the variables
In short
I was rooted with stock BL6 and twrp
So I flashed to this newest stock , and tried to keep my setup and get rooted again
I flashed HOMECSC and after that gave a shot with newest twrp ( to flash newest app-debug.zip )
I ended with a download mode bootloop
So I used your guide with your files , everything went fine .. except for the sharing and dex issues
This is when the forceencryption could have been disabled , exactly !
Then , I did the steps above , back to 100% stock ( steps above ) , without your AP File this time .
TWRP , is useless at this point , it cant mount data , it is the same behaviour as with BL6 version
Edit : Nice that you could replicate it !
"ok so i am now rooted with stock recovery and everything is working - Dex, sharing etc etc "
pvillasuso said:
I agree with you about the variables
In short
I was rooted with stock BL6 and twrp
So I flashed to this newest stock , and tried to keep my setup and get rooted again
I flashed HOMECSC and after that gave a shot with newest twrp ( to flash newest app-debug.zip )
I ended with a download mode bootloop
So I used your guide with your files , everything went fine .. except for the sharing and dex issues
This is when the forceencryption could have been disabled , exactly !
Then , I did the steps above , back to 100% stock ( steps above ) , without your AP File this time .
TWRP , is useless at this point , it cant mount data , it is the same behaviour as with BL6 version
Click to expand...
Click to collapse
Thanks for the info
looks like using TWRP at a starting point is the only way thats going to be of any use - rooted stock is the way forward!!!
exocetdj said:
Thanks for the info
looks like using TWRP at a starting point is the only way thats going to be of any use - rooted stock is the way forward!!!
Click to expand...
Click to collapse
Sure Bro , no problem