Related
Turned on my Wi-Fi
Samsung account asked to make update, and install push service
Play store forced to make updates
Facebook app section expired
Then the phone starts to be super slow, then the screen's touch stopped responding and everything was going crazy and lagging and not working.
I was successfully able to stop the PLAY Store updates and turned off my Wi-Fi
then I removed the battery only to force restart
The phone was stuck at the message of ( SAMSUNG Galaxy Note N7000 ) and nothing, after several seconds the processor area is super HOT
Sometimes I was able to see the BootAnimation with the whole music played.
I can successfully enter the download mode and Recovery mode
A message in red is written in Recovery mode:
E:Error in /data/log/recovery_kernel_log.txt (read-only file system)
I am currently using PhliZ
I don't want any format of any type please, the device contains important information especially the SNote app
any way I can recover my phone back, and if possible without formatting ?
By the way I downloaded Odin, rooted the phone with the right matching version, updated to official German jellybean, then downloaded the UAE version to support Arabic language and the system just went updating and all the information was not erased, then the whole things I mentioned above happened.
One of the apps that was always crashing (Root Toolbox PRO), caused the system to hang for several seconds then a message appear saying it stopped responding
mido_ameer said:
Turned on my Wi-Fi
Samsung account asked to make update, and install push service
Play store forced to make updates
Facebook app section expired
Then the phone starts to be super slow, then the screen's touch stopped responding and everything was going crazy and lagging and not working.
I was successfully able to stop the PLAY Store updates and turned off my Wi-Fi
then I removed the battery only to force restart
The phone was stuck at the message of ( SAMSUNG Galaxy Note N7000 ) and nothing, after several seconds the processor area is super HOT
Sometimes I was able to see the BootAnimation with the whole music played.
I can successfully enter the download mode and Recovery mode
A message in red is written in Recovery mode:
E:Error in /data/log/recovery_kernel_log.txt (read-only file system)
I am currently using PhliZ
I don't want any format of any type please, the device contains important information especially the SNote app
any way I can recover my phone back, and if possible without formatting ?
By the way I downloaded Odin, rooted the phone with the right matching version, updated to official German jellybean, then downloaded the UAE version to support Arabic language and the system just went updating and all the information was not erased, then the whole things I mentioned above happened.
One of the apps that was always crashing (Root Toolbox PRO), caused the system to hang for several seconds then a message appear saying it stopped responding
Click to expand...
Click to collapse
I got that error message too E:Error in /data/log/recovery_kernel_log.txt this morning while trying to reflash JB but it was something odd i was trying and i think i got it due to that, as you can enter recovery you will have to format data in order to fix this or format everything to reflash firmware but before you do that, go to philz recovery and then to mounts/Storage go to last option mount USB (while it is connected to the computer ofcourse) you should see both the internal and external card on computer after that with all your data. Back it up on computer. Unmount once you are done and then do all the wipes and reflash JB.
Cheers!!!
Mounting failed
I am currently working on PhilZ-cwm6-JPLSB-UAE-4.93.6-signed
then I coped recovery CWM-6.0.1.2-n7000.zip to the external sd card
I booted in recovery mode, and installed update
then I followed your instructions but no mobiles where detected by the windows 7, a unknown Samsung android is detected in control panel > printers & devices
every time I restart the phone it returns back to PhilZ
Is there is a windows drivers problem ?
mido_ameer said:
I am currently working on PhilZ-cwm6-JPLSB-UAE-4.93.6-signed
then I coped recovery CWM-6.0.1.2-n7000.zip to the external sd card
I booted in recovery mode, and installed update
then I followed your instructions but no mobiles where detected by the windows 7, a unknown Samsung android is detected in control panel > printers & devices
every time I restart the phone it returns back to PhilZ
Is there is a windows drivers problem ?
Click to expand...
Click to collapse
Download from http://forum.xda-developers.com/showthread.php?t=1901191
this:
Code:
<< 12.05.2013 - PhilZ-cwm6 v5.03.0 with CWM 6.0.3.2 based recovery >>
DDLSC - DXLSE - JPLSB - XXLT5 - ZSLO2 Fixed for bootloop
go to recovery and choose install zip and choose the file i mentioned above (zip file) and go the location where you have saved it (external SD) and reboot into recovery, mount storage.
Go to Dr. Ketan's thread for latest samsung drivers install them and see if it shows up your internal and external storage on computer. Backup and go to dowload mode and flash JB again.
Thanks so much
I installed PhliZ 5.0.3.0 updated and installed succussfully
I was able to mount the sdcard and copied all the folders was there to my PC
Then I downloaded a new LSB jellybean UAE edition and worked like sharm
Now my note is working
Thanks for your support
Noise Cancelling is not working
It seems that the phone noise cancelling feature is not working any more, whatever I do in the options while call in progress
Mobile GT-N7000
Android 4.1.2
Baseband N7000XXLSO
Kernel 3.0.31-906407
Build number JZ054.N7000JPLSB
Hello
I tried to install different Rom from different sites but every time I apply the update from the Recovery menu, the installation hangs for error Error in / tmp / sideload / ... (status 0)
I also tried to format the SD card but the error persists ... I also installed cwm ...
I seem to have tried one of these 2 ROM:
...needrom.com/mobile/galaxy-ace-s5830
...needrom.com/mobile/s5830-galaxy-ace
Currently there is Android 2.3.6 and if I install updates, the cel says it is updated
you must install cwm and then at cwm install zip from sdcard and not aplly update
tethering
graineeg said:
you must install cwm and then at cwm install zip from sdcard and not aplly update
Click to expand...
Click to collapse
Now it's works: Now there's cyanogenmod (ANDROID 4.2.1).
The only thing that doesn't works is tethering (and wifi hotspot).
I have vodafone...
Thanks
Stefano
Ok, I see many of you have tried installing CM11 but with "Status 7" on the installing process
See this thread how to install CM11 http://forum.xda-developers.com/galaxy-ace/s5830i-develop/rom-cyanogenmod-11-0-androidarmv6-t2805309
But I've figured out that many of you have not completely understand this process..
First let's install the Clockwork mod Recovery onto our phones:
1.Download this zip onto your SD card Click!
2.Boot into recovery (hold vol + vol- and power until the screen goes on)
3.In recovery select Apply update from SD card and select the Clowermod_Recovery_MTD.zip file and it will install it
4.Select Reboot system now in your stock recovery, or if you have temporary CWM recovery select advanced and Reboot Recovery...
5.Install the CM11 zip from your SD card through the CWM recovery
Second way for installing the CM11 without the bugs and that you can run your phone with SIM card and some bugs fixed also:
1.Follow this thread Click!
2.Go into Odin and put this file in your phone place without PDA and CSC Click!
3.Hit start and boot into stock ROM with that modem
4.Follow the above instructions
And that it is you phone is now running 4.4.4 Kit Kat
Addon:
If you have any trouble during the process (if you didn't go through the explanation very well, if you did there wont be any problems) do this process from this thread
Click!
I am not responsible for any damage done to your mobile phone!!
If you want you can donate to me for this only by clicking nothing else:
If you want click on this link to donate me 20 points haha wo hoo
http://www.allkeyshop.com/?mref=dobermanGT
Status 7-Error by installing ClockworkMod-Recovery 6.0.8.2 on Samsung Cooperve
Hello,
I want to install CyanogenMod 11 on my Samsung Cooperve.
when I go into Recovery Mode and try to install ClockworkMod-Recovery 6.0.8.2 - as mentioned in flexton´s howto - I get the Error Messages:
Code:
This package is for „cooperve,GT-S5830i,gt-s5830i“ devices; this is a „“.
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
Thats weird because my device IS a cooperve,GT-S5830i. What went wrong here and how can I solve this problem?
I don´t know, If this is important, but my Andorid System does not boot anymore.
foto2000 said:
What went wrong here and how can I solve this problem?
I don´t know, If this is important, but my Andorid System does not boot anymore.
Click to expand...
Click to collapse
I think for the moment you have to restore your system.
Edit
I find it this link for S5830i:
http://forum.xda-developers.com/showthread.php?t=1840645
I wish you success !
rom link dead
the link to the cm11 rom doesnt work. I cannot find the cm11 rom for s5830i anywhere. Please help
Best Tutorial I've found! Works perfect. Thanks.
Windows 7 is the most recommended OS to do almost all work without any problem, So I recommend you to activate your existing OS being purchased its license code from ODosta Store
Which is distributing license for almost all types of Microsoft Products with good customer support. I personally use it and have a good experience.
You can upgrade your windows 7 or windows 8.1 pro to windows 10, But you can face some technical issues, So I recommend you to have clean installation of Windows 7, windows 8 or Windows 10 and activate it using legal license.
Hi everyone,
I am looking for a solution to recover my Samsung Galaxy S7 (SM-G930FD) from a bootloop, without TWRP. I have read through many posts to find a solution, but not have worked for me. Please read the full details before offering a solution.
- I rooted my phone, successfully, using CF Auto Root (via Odin). It was working fine for several days
- I installed Hide My Root from the Google Play Store, which did not work
- I installed XposedInstaller_3.0-alpha4.apk
- I installed TWRP Manager from the Google Play Store
- I installed BusyBox from the Google Play Store
- I downloaded xposed*.zip (xposed-v86-sdk23-arm64.zip) and xposed-uninstaller*.zip (xposed-uninstaller-20150831-arm64.zip)
- I installed TWRP. I did a lot at once, so some steps are a little fuzzy right now.
- I booted into recovery mode (TWRP) and completed a backup for the data, to the SD card.
- In recovery mode, I then selected BOTH zip files for install. Once that completed, the phone restarted and stuck at the Samsung logo.
- I booted into download mode and tried CF Auto Root again, with no success.
- I booted into recovery mode, but TWRP does not seem to appear. It goes to the default Android Recovery with the following options:
> Reboot system now (did not help)
> Reboot to bootloader (did not help)
> Apply update from ADB ("Update from external storage is disabled")
> Apply update from SD card ("Update from external storage is disabled")
> Wipe data/factory reset (did not help)
> Wipe cache partition (did not help)
> Mount /system (did not appear to do anything)
> View recovery logs (lists various logs)
> Power off (turns off phone)
Specifications:
- Samsung Galaxy S7 (SM-G930FD)
- Dual Sim
- International
- Exynos 8890 Octa-Core
- Android 6.0 (Marshmallow)
If you need any additional information that will help you determine a solution, I will attempt to provide to you what I can. I am only looking for possible solutions from the point in which I am at now, not what I did wrong or the correct way to go about doing it. It's a little too late for that now, isn't it?
Thank-you in advanced,
Brandon
SOLUTION
A friend of mine suggested using Smart Switch, which failed, but I was able to come up with a solution from that. Here are the steps I took to bring my phone back to life.
1) Download Samsung Smart Switch and run it
2) From the top right, select "MORE," followed by "Emergency software recovery and initialization
3) Fill in the required information, including the model number and serial number of your device, followed by the OK button
4) Attempt to complete the process vis Smart Switch first
Note: Keep your phone in a cool place, since the screen does stay on the entire time.
If this fails AFTER the download completed (it did for me):
5) Locate the files that were downloaded. On Windows this will be on your system drive under "Users\*user*\AppData\Local\Temp\tmp****", where tmp**** contains random characters. The easiest way to find the name is to sort by date created or modified and look for a large file with a similar name. Now locate the folder starting with the same name. Within this folder there should be 5 files. Copy them all to an alternate location. You will only need the AP file, but you may wish to use the others.
6) Disconnect the phone from your computer
7) Uninstall Smart Switch, Kies, and the Samsung Drivers (if installed)
8) Download the latest version of Odin
9) Restart your computer and reboot the phone into Download mode (Vol Down + Power + Home) => Vol Up on prompt
10) Reinstall Samsung Drivers
11) Run Odin and click the AP button and locate the file you saved, starting with "AP_"
12) Plug in your phone, click Start, and wait for the process to complete.
I hope this helps anyone else looking for a solution, as I have not found this anywhere else online. :good:
First up - Let me say that the complete credit to the method goes to two members here as in the thread https://forum.xda-developers.com/galaxy-tab/help/galaxy-tab-active-2-forum-question-t3712591
BUT BUT BUT what the two experts have missed out is on explaining a clear step by step guide for a complete noob like me . So this is an attempt to explain every step. My tab had root in less than 10 mins .
why i needed the root ?
16gb is not enough for the tab so i wanted to apps and data to be moved to the sd card .
Here are the steps
On the Pc
1. Download the stock firmware (must be the same as in your tab) from samfirmware or any other source.
2. Extract the firmware and the extract archive called AP... . Once extracted you will have a boot.img file in it.
On the TAB
3. Activate developer options by clicking the software version 5 times.
4. In the developer options check OEM unlock and USB debugging
5. Download Magisk Manager v16 from xda and install on the TAB.
Connect the tab to the pc
6. Copy the boot.img file from pc to the tab.
7. Run Magisk Manager and in settings choose the output format as odin compatible tar,
8. Click the INSTALL button in the MAGISK manager and choose 'patch boot image file'
9. After a few minutes a dark screen will appear will read all ok boot image patched...now copy that patched_boot.img.tar file from the tab to the PC and rename it as boot.img.tar
On the Tab
10. Recheck under developer options if check OEM UNLOCK and USB DEBUGG
11. DELETE the GOOGLE account (crucial)
12. Switch of the tab
13. Go to download mode by holding vol down, menu and power together , once asked press vol up to go to the download mode.
14. Connect tab to PC.
On the PC
15. Download ODIN and once downloaded right click and run as administrator.
16. Choose AP and select the previously patched boot.img.tar file.
17. Click START
On the TAB
18. It will run the download and restart , restart will say "VERIFICATION FAILED and aask to RESET and erase .
19. CLICK RESET
20. wait for reset saying ERASING and let the tab restart.
NOW the next step is the most crucial one and it is where i got stuck as none of the members who have rooted their device mention it. I did all of the above procedures repeatedly and failed to get root until i realized there was one FINAL CRUCIAL STEP before enjoying the root.
LAST STEP
ON THE TAB
After the TAB restarts , fill in the initial details (google , samsung account, wifi etc) and before you do anything else INSTALL THE MAGISK MANAGER V16 app you downloaded from XDA .......thats it ....you have root access now . ENJOY!
How did you install Magisk?
When I open Magisk Manager v5.6.4, I get a "Magisk is not installed" and I only have the settings option.
No "install" options.
I have the same tablet. don't know of any twrp that can work with it, therefore leaving me with Magisk Manager only.
Id' be glad to get some help
Thanks,
SOLVED: You must have a functioning network interface in order for the "install" button to appear and you need internet connection to "install the v16 zip".
Magisk is OpenSource though, right? so probably it can be changed to allow offline installation as well.
Rooteed
Well Crap...I just got my Nice, New, Sparkleing Tab Active2 and cant root it yet. I have the New US version SM-T397U Unlocked model. cant find a Stock firmware on Sammobile as of yet...any ideas?
EDIT: Neeeevermind... I did a lil hacking and cracking (for about 26min, lol) to find the files I needed for the SM-T397U. If anyone is looking for em let me know and I'll shoot em' your way. Guessing I'm the first person to root a T397U, hope more will follow. I havent even had this thing 6 hours yet. Thanks for the write up and all those that contributed to the tools and info!
I followed every steps till the end and everything went smoothly. But once I rebooted the tablet, I got the red label on the top left corner: "custom binary blocked by OEM lock". The tablet won't boot properly anymore "OEM unlock" was enabled in the Developers options, I double checked to be sure before flashing.
Edit:
Actually, the "custom binary blocked by OEM lock" appears as soon as I modify the system partition (I wanted to modify the Generic.kl in the keylayout folder on the system partition). If you do not touch anything, everything is fine.
[X-POST from here ]
Worked perfectly, Thank you very much!
WARNING: THIS WILL WIPE EVERYTHING ON YOUR TABLET.
Backup all of your important files before you flash the patched boot.img using odin.
I tried to backup my app data using samsung switch and it worked, but didn't restore most of my device settings and all of my app data.
(Good thing I kept backups for my important apps that had in app backup functionality - like Nova launcher and Squid)
Keep in mind that you probably won't be able to get OTA updates after you perform these steps, it doesn't matter though since this tablet isn't going to be updated that frequently (The 8.0 update is going to come at the end of 2018, source)
Hello.
I tried this but when i using the magisk manager i have an error meassage and the following log:
- Copying image to cache
- Device platform: armeabi-v7a
- Existing zip found
1038+1 records in
1038+1 records out
1063528 bytes transferred in 0.022 secs (48342181 bytes/sec)
- Unpacking boot image
MagiskBoot v18.1(18100) (by topjohnwu)
- Boot Image Modification Tool
mmap failed with 12: Out of memory
! Unable to unpack boot image
! Installation failed
Can you help what i did wrong?
Thank you
oem unlock does not appear
SOLUTION FOUND
how do you oem unlock
I have wasted hours on this, waited weeks, tried the date trick with a legit setup, but the oem unlock never appears, running oldest version of firmware 7.1.1 feb 2018, what gives?
Tried reinstalling firmware via odin, successful flash but no factory reset. Suspect this made no difference. Got the security fail on PIT error, needed a new version of odin and selecting individual AP etc. files fixed this.
apparently you need a samsung or google account
So trying a samsung account... no dice
Now trying adding a sim card as well... success
OK after months of waiting and trying things, this just worked!
Update- I lost the date trick, have to wait 7 days after step 7 on auto date, just appears in developer options no need to press manual update.
https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-skip-rmm-prenormal-install-t3749468
- try downloading UK rom which was released before december '17 (october)
See if it lets the below process work again?
0/ install sim card (was not even the original carrier one in my case although my phone is not carrier locked)
1/ factory reset
2/ on reboot skip all accounts, do not enter a name do not turn on wifi, accept minimal amounts of things
3/ set date to 1/4/19 - turn off automatic date
4/ turn off automatic software updates
5/ enable developer options and turn off auto update system
6/ turn on wifi (date changes)
6b/ change date back
7/ Install samsung account (I went to samsung cloud) (date not changed but software update now triggered despite not touching manual update)
8/ (for interest look at manually check for software updates - it already says 1/4/19 last checked)
9/ reboot
10/ (date is now changed back to today again without my permission)
11/ (it pops up asking to install an update, despite auto updates turned off. - LATER)
12/ (last checked software date is now today (because I left wifi on I think through a reboot) this is 4/5/19 over 1 month later)
13/ go to developer options for the 27868745# time
OEM UNLOCK APPEARED HOLY ****
It is between Bluetooth HCI snoop log and Running services on the dev page, top of the developer options
Since the RMM prenormal thing triggered I had to do this again, so the above instructions do work.
If you stuff up the date just factory reset and start again. Reflash not required
I used a brand new throwaway samsung account for this but thats possibly up to you.
RMM state prenormal
OK now that I've jumped through hoops, installed TWRP
I go to reboot and it's locked recovery again - repeat above OEM unlock reappearing act steps fixes RMM=prenormal. Now it's official again.
Apparently you need to install an RMM patch as well which is not mentioned in this thread.
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
So, odin -> ap -> TWRP download
quickly press power-up-home when it resets!!!
recovery is not seandroid enforcing appears and TWRP starts.
1. back up all partitions to microsd!
2. install
a TWRP -> magisk
b TWRP -> RMM disabler - this writes to /system defeating the purpose of magisk???
wipe cache/dalvik reboot
on boot:
"Verification failed"
"Unable to restart your device the integrity verification has failed.... erase all your data"
Well recovery boots this time not an RMM error thats nice... oh it runs a few commands and automatically restarts again.
"Verification failed..."
I guess that is a boot loop then, thanks TWRP for not stopping at a menu ffs.
Reflash TWRP with odin, now it halts at TWRP menu.
https://forum.xda-developers.com/ga...t/how-to-recover-verification-failed-t3775722
Apparently I should put in download mode and cancel - Result = fail & TWRP bootloop -> reinstall TWRP
unmountable /data partition - yep thats me - could try format to exfat - ext4 - Result = Verification failed ffs
---------- Post added at 01:52 PM ---------- Previous post was at 01:00 PM ----------
Take 3
"Looks like you didnt flash encryption breaker." no-verity-no-encrypt_ashyx.zip or no-verity-opt-encrypt-6.0 zip well duh of course but which one for t395
https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
seems a few up to 6.0
BTW if you don't press reset and instead try and reboot into recovery you don't have to reflash TWRP
Verification FAIL.
https://forum.xda-developers.com/galaxy-note-8/how-to/guide-how-to-root-device-encryption-t3742493
Take 4 - try reinstating boot.img with no mods.
Try flashing stock AP -> twrp -> DMM fix -> magisk in quick succession & booting tablet
Verification Failed! Reset
Goes to recovery - less errors on TWRP (no mount errors like before) but verification failed again.
Because TWRP is installed I don't get the erasing screen as described by OP....? TWRP does something very quickly I think it says formatting cache, it is doing a standard factory reset. Trying manual factory reset with TWRP does not work.
So I think I need TWRP to prevent DMM tripping and install magisk but I need stock recovery to avoid the verification failing constantly.
Or a new version of TWRP that supports encryption? 3230+ I have 3230...?
Try Stock RO system - twrp - dm verity - magisk
Verification failed. Reset - no dmm error thats nice. TWRP did some extra stuff.
Verification failed again.
#&%^&^#%$#[email protected]#%[email protected]#%#$%
Option 556
Install dmverity patch using stock recovery.
Gives error can't find /misc partition - pretty sure these are TWRP zips only.
Magisk website says install TWRP so I can't see how to avoid TWRP and this annoying verification fail. Maybe try an older version of magisk???
Verification bootloop FIX:?
I tried booting stock, it says something like data corrupt on start, looks the same as the verification failed but with the different message. I let it erase/factory reset with stock recovery.
DMM preload did not trigger on this!
As soon as it succeeded I installed TWRP in case DMM triggers.
Now with fixed data partition (presumably) retry TWRP
1. no verity patch (6.0)
2. magisk
cannot install DMM as it alters system partition...?
No cache wipe.
Lets see what happens...... Black screen but this time
'encryption failed' reset. Press reset.... TWRP does a factory reset
'encryption failed'
LOL now I have an encryption failed bootloop.
Reinstall stock and use stock factory reset again - boot to recovery straight away, wipe data & cache
Now install TWRP (not booted once yet)
Install verity patch 6.0
install magisk 19.1
Boot system for the first time. - got a bootloop? no just taking it's sweet time. Fingers crossed!
Android is starting... WELCOME
HOLY **** IT WORKED
DMM patch not installed and it hasn't tripped DMM yet (the old 7 day wait issue)
SUMMARY:
1/ ensure DMM is official and not preload, OEM unlocked etc with above post steps
2/ flash stock AP - do NOT boot system yet
3/ stock recovery - wipe data and cache
4/ download odin mode - install twrp-3.2.3.0-gtactive2lte-7.1.2.tar
5/ twrp - install no-verity-opt-encrypt-6.0.zip
6/ twrp - install magisk 19.1
7/ Boot system for the first time
So I have not installed RMM patch (system untouched) but I did install the no encryption/dm verity patch.
It actually boots now.... will update if further problems
Interestingly OEM unlock has disappeared, so RMM must be prenormal so it will probably die on reboot. Argh. But everything is restoring OK for now. See what happens...
Magisk app auto installed and passes safetynet. Preserve force enctyption and AVB 2.0/dm-verity unchecked.
Annoyingly despite backing up all my messages to samsung they are not restoring past 20 april. Not the end of the world.
Skype keeps stopping.
Reboot and YES only officially released binaries are allowed to be flashed boot loop.
So lets do this again!
SUMMARY:
1/ ensure DMM is official and not preload, OEM unlocked etc with above post steps
8skip 2/ flash stock AP - do NOT boot system yet
8skip 3/ stock recovery - wipe data and cache
4/ download odin mode - install twrp-3.2.3.0-gtactive2lte-7.1.2.tar
5/ twrp - install no-verity-opt-encrypt-6.0.zip
6/ twrp - install magisk 19.1
7/ Boot system for the second time
Pretty sure I already tried this so it won't work. &^%#@&^$#$#%#$%@##%@
Oh great it has managed to install the update and now the date fix doesn't work. &^#%&^#$#@$%@#$
After waiting 7 days
1/ Use stock recovery factory reset, then immediately hold down-home-power download mode
2/ Odin TWRP, then immediately hold up-home-power to enter TWRP
2a/ TWRP swipe to allow modifications (for RMM patch)
3/ TWRP install RMM patch
4/ TWRP install no verity patch
5/ TWRP install latest Magisk
NB Magisk seems to install itself as an app - its just there.
...Safetynet pass despite RMM editing /system phew
Hello,
With the last version of Magisk, we no longer have the setting to choose the output format as odin compatible tar.
How can we deal with this, please ?
Regards,
Driss35 said:
Hello,
With the last version of Magisk, we no longer have the setting to choose the output format as odin compatible tar.
How can we deal with this, please ?
Regards,
Click to expand...
Click to collapse
You don't have to choose any file type. Magisk scans files automatically.
Also, if your file type is ".lz4", you have to change it to ".img". Unless, you can't continue.
@Drnms thanks for this thread. But, some places have to be updated because of new Magisk versions.
Did App data remain after rooting
Drnms said:
First up - Let me say that the complete credit to the method goes to two members here as in the thread https://forum.xda-developers.com/galaxy-tab/help/galaxy-tab-active-2-forum-question-t3712591
BUT BUT BUT what the two experts have missed out is on explaining a clear step by step guide for a complete noob like me . So this is an attempt to explain every step. My tab had root in less than 10 mins .
why i needed the root ?
16gb is not enough for the tab so i wanted to apps and data to be moved to the sd card .
Here are the steps
On the Pc
1. Download the stock firmware (must be the same as in your tab) from samfirmware or any other source.
2. Extract the firmware and the extract archive called AP... . Once extracted you will have a boot.img file in it.
On the TAB
3. Activate developer options by clicking the software version 5 times.
4. In the developer options check OEM unlock and USB debugging
5. Download Magisk Manager v16 from xda and install on the TAB.
Connect the tab to the pc
6. Copy the boot.img file from pc to the tab.
7. Run Magisk Manager and in settings choose the output format as odin compatible tar,
8. Click the INSTALL button in the MAGISK manager and choose 'patch boot image file'
9. After a few minutes a dark screen will appear will read all ok boot image patched...now copy that patched_boot.img.tar file from the tab to the PC and rename it as boot.img.tar
On the Tab
10. Recheck under developer options if check OEM UNLOCK and USB DEBUGG
11. DELETE the GOOGLE account (crucial)
12. Switch of the tab
13. Go to download mode by holding vol down, menu and power together , once asked press vol up to go to the download mode.
14. Connect tab to PC.
On the PC
15. Download ODIN and once downloaded right click and run as administrator.
16. Choose AP and select the previously patched boot.img.tar file.
17. Click START
On the TAB
18. It will run the download and restart , restart will say "VERIFICATION FAILED and aask to RESET and erase .
19. CLICK RESET
20. wait for reset saying ERASING and let the tab restart.
NOW the next step is the most crucial one and it is where i got stuck as none of the members who have rooted their device mention it. I did all of the above procedures repeatedly and failed to get root until i realized there was one FINAL CRUCIAL STEP before enjoying the root.
LAST STEP
ON THE TAB
After the TAB restarts , fill in the initial details (google , samsung account, wifi etc) and before you do anything else INSTALL THE MAGISK MANAGER V16 app you downloaded from XDA .......thats it ....you have root access now . ENJOY!
Click to expand...
Click to collapse
Hi Dmms,
Please confirm if the data remained (i.e. was not erased) after the rooting?
Thanks in advance.
Hi, in case it is still relevant:
- Tab does a factory reset when booting first time after the boot img is flashed, data on the device is lost. Data on the SD card is not affected
- In my case, flashing boot.img with Odin didn't work. Odin said success, but no root. Heimdall worked fine, tab was rooted at first attempt
Does this guide also work for Android 9 ?
Edit: So it works with Android 9 also but I had to unpack the boot.img with 7zip ZS according to this post https://forum.xda-developers.com/t/samsung-a40-how-to-root.3929496/post-79902328
and re-pack it with normal 7zip according to these steps:
Do you have the boot.img.lz4 file to boot.img unpacked?
You have renamed the magisk_patched.img to boot.img?
You used the normal 7zip to package into a .tar file? Not the 7zZs?
You used the normal Odin 3.14?
Hello, did you manage to remove the "format as internal" lock?
Hi guys,
Trying to root this tablet, when I load the patched magisk file in Odin and perform the download. The tablet restarts and loads like normal but the tablet isn't rooted.
Any ideas?
alguma fortma?