I was using Odin trying to flash this stock rom to my device, then i felt like its doin nothing so i disconnected it.
Here are the instructions I've followed.
now i see this image, no recovery or download mode avail:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I found this post, but since it targets Galaxy S and not my device (Galaxy S WiFi 5.0 YP-G70 Player - US version), I am not sure about OPS File mentioned there, is it device-independent?
I don't wanna make things worse than they are now.
Update
I've managed to unbrick the phone, now I'm unable to flash a ROM on it, see details.
Thanks for your help.
Been there, done that.
http://forum.xda-developers.com/showthread.php?t=1386669
Go to this guide. Get the bootloaders he provides. You'll use his PIT file and bootloader to get back to the download screen. Then flash that stock rom you were trying to flash previous, but use the PIT file you used from AdamOutlers guide. Should come back perfectly fine.
DeLaVicci said:
http://forum.xda-developers.com/showthread.php?t=1386669
Go to this guide. Get the bootloaders he provides. You'll use his PIT file and bootloader to get back to the download screen. Then flash that stock rom you were trying to flash previous, but use the PIT file you used from AdamOutlers guide. Should come back perfectly fine.
Click to expand...
Click to collapse
It requires an Ubuntu box.
I would do it if I don't have another choice.
I thought about using the Odin Multi Downloader from PC.
Update: Will this work for my particular device so I don't have to install Ubuntu? He talks about a windows version (with a exe extension), but i dont find the download and its not on google code.
Update: Found the exe:
http://code.google.com/p/heimdall-o...mdalloneclick/resources/HeimdallPackage/?r=27
NullUser said:
It requires an Ubuntu box.
I would do it if I don't have another choice.
I thought about using the Odin Multi Downloader from PC.
Update: Will this work for my particular device so I don't have to install Ubuntu? He talks about a windows version (with a exe extension), but i dont find the download and its not on google code.
Update: Found the exe:
http://code.google.com/p/heimdall-o...mdalloneclick/resources/HeimdallPackage/?r=27
Click to expand...
Click to collapse
Notice that I didn't follow the guide, it just led me to trouble.
All I had to do is install Java, run the jar and let it do its thing, didnt have to bother with permissions or extracting the jar at all.
No, ignore the Ubuntu part. Just download his GalaxyPlayer-Bootloader.zip. Skip the instructions for the Resurrector, it's not needed. Just start the guide at step 4, and it should get you into download mode. Then flash the stock ROM you got, but flash without a PIT file. It's the PIT file that made it crash, I've had the same problem.
DeLaVicci said:
No, ignore the Ubuntu part. Just download his GalaxyPlayer-Bootloader.zip. Skip the instructions for the Resurrector, it's not needed. Just start the guide at step 4, and it should get you into download mode. Then flash the stock ROM you got, but flash without a PIT file. It's the PIT file that made it crash, I've had the same problem.
Click to expand...
Click to collapse
Whatever, it's already in download mode (i used that OneClick.jar, ran it and followed it and it unbricked it).
Anyway, now I'm trying to flash the ROM using Odin, I'm starting the process and it goes idle, here is the Odin log:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ueki8_min.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
************Here is where it standing right now and doesn't do anything************
i checked the cpu and its 0%, is the device working? how long can it take?? As soon as I disconnect, it will go soft-bricked, which is what happened last-time, is there any point in being patient and letting it work, i dont see any progress or sign of life anyway.
Update
I looked into Heimdall but have no clue how to flash a stock rom with it, all i got is a pit file and a md5 file.
UPDATE
Case closed, I found the problem, it was the PIT file, I took a PIT from here and everything works like a charm!
Thanks for all of you!
I kept telling you it was the pit file.
Can you help me?
I had the same thing as you. Used oneclick.jar and unbricked, but now when I try to flash Erygits rom Odin says FAIL and something with blablabla pit.
What do I do now?
BTW how did you flash with Heimdall (or didn't you?)?
Thanks in advance.
Rapydax said:
BTW how did you flash with Heimdall (or didn't you?)?
Click to expand...
Click to collapse
I flashed with OnClickUnbrick which is part of Heimdall.
Did you unbrick your device already (and bring it to download mode)?
No - refer to here.
Yes -
You'll have to know if you have the US, International or EU version. FYI, The US version has a capacitive (non-physical) home button.
Install Odin
Make sure the Samsung Driver is installed (check device mgr)
Use a PIT from here
For the US version: Use this (2.3.5) or this (2.3.6), or this ROM (all ROMs are rooted)
For international use one of the ROMs here.
I'm just trying to help, I'm not resp. for any damage etc. etc. etc.
If you have a different device, or u need any other help, buzz me and will provide links, I have some, in just a few ago I didn't have a clue what a ROM means, so don't be shy to ask, and sorry if that's not the case.
And BTW, should u ever hear about a tested ICS ROM for the US ver. please PM or buzz me.
DeLaVicci said:
http://forum.xda-developers.com/showthread.php?t=1386669
Go to this guide. Get the bootloaders he provides. You'll use his PIT file and bootloader to get back to the download screen. Then flash that stock rom you were trying to flash previous, but use the PIT file you used from AdamOutlers guide. Should come back perfectly fine.
Click to expand...
Click to collapse
If you have the Phone-PC screen, you don't need bootloaders. The Phone-PC screen is "forced" download mode - device is saying "you need to flash something in Odin"
Unable to have device boot after following all suggestions
First I want to thank all who have made possible either by developing or recollecting the data required to unbrick the Samsung Galaxy Player 5.0, an excellent effort!
Let me know explain my device situation:
1. I got the Galaxy Player 5.0 US (capacitive buttons) from a friend (original owner) who I think he did try some trick (he couldn't explain) and the device never booted again.
2. I've been researching the different tools, files, kernels, factory ROMs around the Galaxy Player 4.0 and 5.0.
3. I've patiently read gazillion threads in this forum which all of the interconnect at a given time, from there I was able to finally identify and download:
Tools required:
- UnBrickable Resurrector - Adam Outler
- VirtualBox VM with Windows 7
- GalaxyPlayer Bootloader package
- Odin
- Heimdall
I have downloaded the ROM:
- YP-G70_UEKI8_MIN.rar
- Eryigit_Rom_PDA_YP-G70_G70ZCKPA.R.3.0-Defult-USA-Extract-it.rar
which only includes the kernel (zImage) and the filesystem content (factoryfs.rfs) and the pit file (euki8.pit).
I've find the euki8.pit to be useless in the many attempts to try to flash using it (Odin will stall the process of flashing if I use it); instead of it, I've downloaded:
- G70-GalaxyPlayer5.0-8gig.pit
- GB70-GalaxyPlayer70-16gb.pit
I don't know if it is a 8 or 16 gig, since I never used the device.
What is the condition of the device?
- The device will not show a charging icon when charging cable is connected (either to the USB power adaptor or the computer USB port)
- The device will get warm if I connect the charger to the wall outlet
- The device screen does not react to pressing the Power button
- The device screen does not react to pressing Vol Up/Down and Power (Download Mode)
What I've accomplish so far:
- Device is able to go to Download Mode using the UnBrickable Resurrector.
- Use Oding to transfer files to the device while in Download Mode.
Data Transfers Successfully attempted:
- Download Mode only:
- Put device in Download Mode using UnBrickable Ressurector.
- PIT File included in Galaxy Player Bootloader package
- Selected to Re-Partition
- Used the Bootloaders included in the GalaxyPlayer Bootloader package.
Transfer reported by Odin as pass, the device behavior is exactly the same as originally described.
- Partition / Boot
- Put device in Download Mode using UnBrickable Ressurector.
- PIT files (G70-GalaxyPlayer5.0-8gig.pit and GB70-GalaxyPlayer70-16gb.pit)
- BootLoader from GalaxyPlayer Bootloader package.
Transfer reported by Odin as pass, the device behavior is exactly the same as originally described.
- Partition / ROM
- Put device in Download Mode using UnBrickable Ressurector.
- PIT files (G70-GalaxyPlayer5.0-8gig.pit and GB70-GalaxyPlayer70-16gb.pit)
- BootLoader files from GalaxyPlayer Bootloader package.
- ROM file ueki8_min.tar.md5
Transfer reported by Odin as pass, the device behavior is exactly the same as originally described.
- Partition / Boot / ROM
- Put device in Download Mode using UnBrickable Ressurector.
- PIT files (G70-GalaxyPlayer5.0-8gig.pit and GB70-GalaxyPlayer70-16gb.pit)
- BootLoader files from GalaxyPlayer Bootloader package.
- ROM file ueki8_min.tar.md5
Transfer reported by Odin as pass, the device behavior is exactly the same as originally described.
- ROM
- Put device in Download Mode using UnBrickable Ressurector.
- ROM file ueki8_min.tar.md5 and Eryigit_Rom_PDA_YP-G70_G70ZCKPA.R.3.0-Defult-USA.tar
Transfer reported by Odin as pass, the device behavior is exactly the same as originally described.
I've also tried using Heindall without success, most of the time the communication breaks and I see a lots of communication error reported back from libusb. So far the only success I have had is using the combination of UnBricable Resurrector + Odin.
Is there anything that the community might see that I'm missing?
I volunteer to be the ginnea pig for any additional crazy testing since at this point can't do much. If one or more developers want to work with me, we can develop a testing procedure and validate it.
Looking forward to make this Samsung Galaxy Player 5.0 device to work!
Best regards,
Well I tried to do the Odin flashing with a bootloader and pit, yesterday. They didn't work though, Odin said: FAIL, so my only simple option left was to wipe data and cache while in recovery mode. I did that and then rebooted and it worked, strangely enough. It was so simple...
But I had a soft-brick. I had to use oneclick.jar to un-soft-brick the device. Then I could use the power and volume buttons to get into downloading mode or recovery mode.
So maybe you should get into recovery mode and wipe all data and cache?
That's what I did anyway.
Good luck
I am an android noob and can't tell if it matters that much all I can sure say is that the us version isn't available as 16gig,only 8.
Sent from my YP-G70 using XDA
NullUser said:
I flashed with OnClickUnbrick which is part of Heimdall.
Did you unbrick your device already (and bring it to download mode)?
No - refer to here.
Yes -
You'll have to know if you have the US, International or EU version. FYI, The US version has a capacitive (non-physical) home button.
Install Odin
Make sure the Samsung Driver is installed (check device mgr)
Use a PIT from here
For the US version: Use this (2.3.5) or this (2.3.6), or this ROM (all ROMs are rooted)
For international use one of the ROMs here.
I'm just trying to help, I'm not resp. for any damage etc. etc. etc.
If you have a different device, or u need any other help, buzz me and will provide links, I have some, in just a few ago I didn't have a clue what a ROM means, so don't be shy to ask, and sorry if that's not the case.
And BTW, should u ever hear about a tested ICS ROM for the US ver. please PM or buzz me.
Click to expand...
Click to collapse
Have tried all of this, but still getting a black screen after Odin reboots the player. Odin is reporting "PASS!" though. Any ideas or suggestions?
If Odin says it's a Pass but it isn't showing anything on the screen, maybe it's a hardware problem? Do you have the Android SDK installed so you could try running the ADB to explore the device? If USB Debugging was enabled before your friend broke it, it might work. If that's the case, then it's a hardware problem and there probably isn't jack you can do about it. =\
What entropy said
Had this same thing happen to my galaxy player 5.0. just reconnected it then flashed the kernel again.
Will try installing the Android SDK
DeLaVicci said:
If Odin says it's a Pass but it isn't showing anything on the screen, maybe it's a hardware problem? Do you have the Android SDK installed so you could try running the ADB to explore the device? If USB Debugging was enabled before your friend broke it, it might work. If that's the case, then it's a hardware problem and there probably isn't jack you can do about it. =\
Click to expand...
Click to collapse
I'll install the SDK, is there a particular sequence of events or commands to execute once I have it installed?
Regards,
---------- Post added at 10:54 AM ---------- Previous post was at 10:47 AM ----------
Rapydax said:
Well I tried to do the Odin flashing with a bootloader and pit, yesterday. They didn't work though, Odin said: FAIL, so my only simple option left was to wipe data and cache while in recovery mode. I did that and then rebooted and it worked, strangely enough. It was so simple...
But I had a soft-brick. I had to use oneclick.jar to un-soft-brick the device. Then I could use the power and volume buttons to get into downloading mode or recovery mode.
So maybe you should get into recovery mode and wipe all data and cache?
That's what I did anyway.
Good luck
Click to expand...
Click to collapse
Forgot to mention that I also tried the oneClick unbrick software. I set the device in DownloadMode (via UnBrickable Resurrector) then I run the OneClick and click the button, the device then reboots and goes back to a blank screen, no reboot and still did not respond to any key pressing sequence.
Regards,
Forgot to mention that I also tried the oneClick unbrick software. I set the device in DownloadMode (via UnBrickable Resurrector) then I run the OneClick and click the button, the device then reboots and goes back to a blank screen, no reboot and still did not respond to any key pressing sequence.
Regards,[/QUOTE]
No, I meant that I had to use oneclick.jar to get back to downlaod screen, sorry for saying it wrong.
Once you're in download mode or recovery mode you should either restore your back-up files (recovery mode) or flash a new rom/kernel (download mode).
Some news...
I tried multiple combinations of :
- PIT
- Boot
- Kernel
- ROM (Kernel + FileSystem)
and at some point in time the device booted into CWM mode and it was sowing errors about not finding the following partitions:
/cache
/cache/recovery
/efs
/data
and other that couldn't read because they scroll in the screen.
I was able to save a copy of the log into the SDCard:
Starting recovery on Sun Jan 9 18:20:10 2005
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v5.0.2.7
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /efs rfs /dev/block/mmcblk0p10 (null)
2 /system ext4 /dev/block/mmcblk0p13 (null)
3 /datadata ext4 /dev/block/mmcblk0p14 (null)
4 /cache ext4 /dev/block/mmcblk0p15 (null)
5 /data ext4 /dev/block/mmcblk0p16 (null)
6 /emmc vfat /dev/block/mmcblk0p17 (null)
7 /sdcard vfat /dev/block/mmcblk1p1 (null)
8 /boot emmc /dev/block/mmcblk0p11 (null)
9 /recovery emmc /dev/block/mmcblk0p12 (null)
touch: /etc/mtab: No such file or directory
W:Unable to create /etc/fstab!
Irocessing arguments.
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
E:Can't mount /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
W:Can't unlink /cache/recovery/command
Does this look familiar to anyone? Any way to fix this?
Regards,
Orzmud, don't you have back-ups, so you can restore? If so, wipe all data and cache and then go to advanced and click on delete dalvik cache or something. Then restore.
I didn't have a back-up saved, so:
What I did when I got into downloading mode:
- Startup another computer and install Odin, the .pit files and the custom ROMs/kernels.
- Go into recovery mode.
- Wipe all data (3×), cache and dalvik (in advanced menu).
- Go back to downloading mode and connect to the pc.
- Open Odin 3 v1.85 and click on PDA. Select http://www.mediafire.com/?nch3g45zw5qdyhx (INTL). If you have the US version of the player then download the US stock ROM somewhere.
- Click on the "PIT" option and select one of the .pit files that fits your galaxy player version (http://forum.xda-developers.com/showthread.php?t=1389873)
- Then click on Start.
- Voila my player worked again.
I don't know if this will work for you, but it might be worth a try.
Related
I am looking around this thread has anyone seen anything on YP-GB70 or is this the same as YP-G70? It is from Korea. I guess steve's kernal is NOT compatible with this device. What Kernal / ROM is? Any suggestions
Korean YP GB70 root and non root kernels (firmware KPH)
Hello,
you can find root and non root kernels for Korean Samsung Galaxy Player YP GB70. It is flashable only over the last KPH firmware (as of March 2012). As I cannot yet post links to outside pages (new user) try to decode the URL from this:
HTTP doubledot slash slash bvlgarian dot tistory dot com slash 138
You can flash the kernels with Odin.
That's great help you can give us.
We are many from outside to buy this YP-GB70 from korea and we need support to improve our device or rearrange it.
Our "little" problem is to find the right connexion or links to the people having knowledge and tools available.
I tried the link you provide us, if right, have a look of what i got.
What item is it to open?
Anyway don't be shy with your english it is better than mine. (french I am)
Regards
I got it after several Trials (bulgarian versus bvlugarian!)
Now I have to dig in the subject. * we keep in touch.
Thanks again,
Hey
Hi, Im a Korean Galaxy Player user.(YP-GB70.)
This Root Knernel is not rooting kernel. Because, This Kernel flashed Odin, device has bricked. But, Korean Galaxy Player's Rooting Rom is appear.
(In fact, This is my custum Rom.)
I tested the "rooted kernel" it leads my device alive from KPH brick gotten after upgrade (I felt Happy). Only problem is it doesn't reconize any internal mémory as well as external SD. So anybody got that?
Anyway, send us link for any other rooting solution. you are welcome.
Korean YP GB70 root and non root kernels (firmware KPL)
Hi folks,
here are root and non root kernels for Korean Samsung Galaxy Player YP GB70. It is flashable only over the last KPL firmware (as of April 2012):
http://bvlgarian.tistory.com/320
Once you flash root kernel via ODIN and set up SUDO, you can flash back to nonroot kernel (apparently the features of root kernel are not very well implemented/maintained anymore). Even if you flash back to nonroot kernel, the device would remain rooted.
---
If you want to flash complete customized ROM for Korean GB70:
http://greenview.tistory.com/31
The *.egg archives can be decompressed by AllZip.
---
And before you start, you can temporarily flash RJ's Custom Kernel r13 for YP-GB70. This kernel has support for ClockworkMod, so you can backup your original KPL ROM to sdcard. After flashing with ODIN you can call ClockworkdMod via combination "HOME button" + "POWER button" + "Vol. Up".
The kernel is here:
http://greenview.tistory.com/attachment/[email protected]
Once you backup your ROM, you should go back to stock kernel, RJ's kernel probably wouldn't boot, it is usable only for backup/restore.
---
Note: if you don't know what you are doing, ie. if you aren't comfortable with fdisk, adb etc., you should expect some major setbacks ;-).
Many thanks for your support.
I still have the following problem to understand and to solve in order to have my device fully working.
Detail:
-When using no rooted kernel it stay in loop at Galaxy player logo for a while....
-When using rooted kernel it starts 100% but I can't access any Sd memory or USB connexion like the internal memory is not adressed.
Who knows about this issue?
Any help is appreciated.
Korean YP GB70 partition softbrick recovery
lolo9393 said:
Many thanks for your support.
I still have the following problem to understand and to solve in order to have my device fully working.
Detail:
-When using no rooted kernel it stay in loop at Galaxy player logo for a while....
-When using rooted kernel it starts 100% but I can't access any Sd memory or USB connexion like the internal memory is not adressed.
Who knows about this issue?
Any help is appreciated.
Click to expand...
Click to collapse
It looks like one or more of your partitions are damaged. Probably by setting a wrong option in ODIN. I've did that mistake and here's how to fix it with a good chance of not losing your data:
* Install root kernel via ODIN
* Start your device normally (do not put your device in DOWNLOAD mode), it's OK if it hangs.
* On your PC install Android SDK + platform tools and make sure your adb is working.
* "adb shell" to your device
* "sudo su" or "su"
* "mount -t tmpfs tmpfs /tmp"
* "exit"
* "exit"
* Get busybox binary: http://www.4shared.com/file/DffR-A0B/busybox.html
* Untar /unzip the binary
* Push the binary to your device: "adb push busybox /tmp/busybox".
Then get fdisk working:
* "adb shell" to your device
* "sudo su" or "su"
* "cd /tmp"
* "chmod 775 busybox"
* "ln -s busybox fdisk"
* "./fdisk /dev/block/mmcblk0"
* List your partitions by pressing "p".
Here's the listing of CORRECT partition sizes (for 16GB model!):
Disk /dev/block/mmcblk0: 15.9 GB, 15925772288 bytes
1 heads, 16 sectors/track, 1944064 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 5 1944064 15552480 5 Extended
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p5 9 40 256 83 Linux
/dev/block/mmcblk0p6 45 76 256 83 Linux
/dev/block/mmcblk0p7 81 240 1280 83 Linux
/dev/block/mmcblk0p8 245 404 1280 83 Linux
/dev/block/mmcblk0p9 409 1048 5120 83 Linux
/dev/block/mmcblk0p10 1053 2332 10240 83 Linux
/dev/block/mmcblk0p11 2337 3296 7680 83 Linux
/dev/block/mmcblk0p12 3301 4260 7680 83 Linux
/dev/block/mmcblk0p13 4265 38824 276480 83 Linux
/dev/block/mmcblk0p14 38829 55980 137216 83 Linux
/dev/block/mmcblk0p15 55985 64176 65536 83 Linux
/dev/block/mmcblk0p16 64181 313396 1993728 83 Linux
/dev/block/mmcblk0p17 313401 1937720 12994560 83 Linux
If some of them are mismatched (p14 and p15 probably), delete them and create again in fdisk. You don't have to format them, just setup correct type (T 83). Finally write (w) and quit fdisk.
* "sync; sync; sync"
* "reboot"
If the device still hangs:
* Put your device in SYSTEM RECOVERY mode: ("Pwr button" + "Vol up" + "Home button")
* Choose "wipe cache partition"
* Choose "reboot system now"
If the device still hangs:
* Put your device in SYSTEM RECOVERY mode: ("Pwr button" + "Vol up" + "Home button")
* Choose "wipe data/factory reset"
* Choose "reboot system now"
If the device still hangs, then try your service or shop.
Attached what i got with heimdall ytd.
I will start ADB today when free. i must learn about first.
Thanks
Today edit:
I have followed your clear instruction, here attached the result before going forward in another mistake let me have your direction to follow.
I mind this can help many other people like me!
missed attachment
Attachment can't be sent under msg edit sorry.
Partitions
lolo9393 said:
Attachment can't be sent under msg edit sorry.
Click to expand...
Click to collapse
You did a good job! Your model is 32GB by the way, so the size of your partition p17 would be different from my model. Your partition p14 is corrupted and p15-17 are missing. You should delete p14 and create p14-17 as type 83 (Linux). You can make the same sizes, as my example, except for the p17, which you can simply create from block 313401 until the end of the disk . Then try the rest of my instructions.
If the formatting in SYSTEM RECOVERY mode would not help you, you can create tool "mke2fs" the same way you created "fdisk" and you can format the partitions via command:
"./mke2fs -j /dev/block/mmcblk0p14"
That's for partition p14, you should also do that for the rest (p15-17) and then try to format again in SYSTEM RECOVERY.
That should help.
Before correcting the wrong blocks by hand, I innocently accepted the light offer to correct block 14 by typing "w" that's may be not good. but i cann't retur to read dev/block/mmblck0 to see the resulting. What's wrong?
Sorry if bothering for you but that's common problem with beginners!
fdisk
Try: "./fdisk dev/block/mmblck0". What happens?
chongkwan said:
Try: "./fdisk dev/block/mmblck0". What happens?
Click to expand...
Click to collapse
Thanks
Now, You can go to sleep and have a good night.
I'll finish the work with care.
Regards
Great success!
My device restarted after KPL Fw flashing (odin). I have not lost any personal data (photo and music), that's strange after some 20 different flash process and wipes.
Your are top expert guy!
Many THANKS for your help.
I was seeking for solution from end january when I Missrooted my device!
I have in meantime learn so much about Android and also improved my english somehow.
In case I can give you back a service, please ask.
I am sure your problem solving would help many other infortunate guys, why not to make this "sticky".
I can add what is good not to be done to avoid problem then!
Best Regards
Very good! Congratulations Your partitions are correct now. I am sorry you had to wait so long.
trying to fellow the above tutorial with no lcuk , i'm stuck in adb shell error device not found, any clue ?
Hi
In post N°8 You have everything you "must" do.
Rooted kernel is RJ's 14 kernel and nothing else for our device.
You go recovery and adb will connect.
then "shell" et voila.
Forget playing with the PIT file; it si no reason it is wrong at this step, avoid adding a difficulty, please.
Keep informed as you want
now after flashing a Korean kernel the device does boot up normally and everything seems to be fine apart from memory, internal memory and staff is all showing unavailable ?!?! strange situation ?!?! does anybody have an idea about how to fix that ?
Fine,
You mind you are just at a "wipe" step to be done.
Normally full wipe is enough to get the device restarted from home.
OK do it and give me the result reported at the screen after this step.
Hi everyone,
after spending hours with my Galaxy Tab 10.1N 3G (P7501) and searching through XDA and also Google, I finally decided to ask for help...
The tab never was extremly stable, crashing every few days. At some point I upgraded stock 3.2 to a stock 4.0 for the Galaxy Tab 10.1 (P7500), which seemed better but still not satisfactory. So I decided to go for CM 10.1 (as I use on my Galaxy Nexus).
In the progress of the update I figured out some problem with the file systems: Wiping/Flashing over from ClockworkMod 6.0.3.0 seemed not to erase old data, resulting in a unstable system as for instance /data was not wiped correctly.
Already fearing a flash memory problem, I completely blanked the Tab using Odin and a stock firmware 4.0.x image. This actually cleared everything and I restarted the update process, which worked this time flawlessly.
For several weeks I had a nicely running system on CM 10.1 (recently on the 2013-05-13 nightly, which TabletUI und OpenPDroid patch). It still crashed every few days (either becoming very slow or just hanging, sometimes it rebootet by itself). I also switched to TWRP 2.5.0.0 recovery.
A few days ago it crashed during an app install and did not boot up again. It was hanging a few seconds after the CM 10.1 boot animation started. Not even TWRP 2.5.0.0 would boot, the Tab would just reboot after a minute or so.
I then flashed ClockworkMod 6.0.3.0 via Odin, which booted up. I started to regain some hope and did run a e2fsck on all partitions. /system (p4) and /data (p8) showed many file system errors. I cleared the ones on /data which mainly affected files related to the crashed app install.
I then formatted /system from CWM, rebooted recovery and checked /data and /system again. /data was fine, however the now empty /system showed again many file system errors. I created a file system using mke2fs -T ext4 and checked again, this time /system was fine. I then reformatted using CWM and it again had file system errors.
I then made a file system with mke2fs, switched to TWRP (as I mistrust CWM now) and installed CM again (with TWRP). After rebooting into recovery and doing another e2fsck -f on /system (p4), again many file system errors occurred, mainly multiple claimed blocks.
I found emmc_scan from another thread, it did not find problems on my device.
How can this be? Is this a bug in CWM or a problem with my Tab? Or am I doing something wrong here?
I don't know what to do beside reflashing stock and sending the tab in for repair, however, the error description for the service is probably rather difficult, as the problem only becomes visible after a while of use.
Thanks for any advice/help!
I did a few more tests with the following results:
- just flashing a CM 10.1 nightly (namely the one from 2013-05-13, though I doubt it is something special about it) OR using the format option in CWM 10.1 will cause the file system to test later on with many many errors. TWRP does not really format but rather remove all files, therefore it does not cause damage, at least not on an empty file system.
- I checked all file system on my Galaxy Nexus (running the same CM 10.1 nightly and the same TWRP 2.5.0.0 recovery) and all filesystem (tested with e2fsck -f) tested completly ok.
So what can be the cause for the Galaxy Tab's filesystem corrupting all the time?
Thanks again for any ideas!
SheridanJohn said:
Hi everyone,
after spending hours with my Galaxy Tab 10.1N 3G (P7501) and searching through XDA and also Google, I finally decided to ask for help...
The tab never was extremly stable, crashing every few days. At some point I upgraded stock 3.2 to a stock 4.0 for the Galaxy Tab 10.1 (P7500), which seemed better but still not satisfactory. So I decided to go for CM 10.1 (as I use on my Galaxy Nexus).
In the progress of the update I figured out some problem with the file systems: Wiping/Flashing over from ClockworkMod 6.0.3.0 seemed not to erase old data, resulting in a unstable system as for instance /data was not wiped correctly.
Already fearing a flash memory problem, I completely blanked the Tab using Odin and a stock firmware 4.0.x image. This actually cleared everything and I restarted the update process, which worked this time flawlessly.
For several weeks I had a nicely running system on CM 10.1 (recently on the 2013-05-13 nightly, which TabletUI und OpenPDroid patch). It still crashed every few days (either becoming very slow or just hanging, sometimes it rebootet by itself). I also switched to TWRP 2.5.0.0 recovery.
A few days ago it crashed during an app install and did not boot up again. It was hanging a few seconds after the CM 10.1 boot animation started. Not even TWRP 2.5.0.0 would boot, the Tab would just reboot after a minute or so.
I then flashed ClockworkMod 6.0.3.0 via Odin, which booted up. I started to regain some hope and did run a e2fsck on all partitions. /system (p4) and /data (p8) showed many file system errors. I cleared the ones on /data which mainly affected files related to the crashed app install.
I then formatted /system from CWM, rebooted recovery and checked /data and /system again. /data was fine, however the now empty /system showed again many file system errors. I created a file system using mke2fs -T ext4 and checked again, this time /system was fine. I then reformatted using CWM and it again had file system errors.
I then made a file system with mke2fs, switched to TWRP (as I mistrust CWM now) and installed CM again (with TWRP). After rebooting into recovery and doing another e2fsck -f on /system (p4), again many file system errors occurred, mainly multiple claimed blocks.
I found emmc_scan from another thread, it did not find problems on my device.
How can this be? Is this a bug in CWM or a problem with my Tab? Or am I doing something wrong here?
I don't know what to do beside reflashing stock and sending the tab in for repair, however, the error description for the service is probably rather difficult, as the problem only becomes visible after a while of use.
Thanks for any advice/help!
Click to expand...
Click to collapse
Wow what a process. .. Odin back to stock recovery (not ROM only factory recovery e3 which can be found here http://droidbasement.com/galaxy/ ) do a factory reset in stock recovery and flash back cwm and cm10.1 with the right Gapps, let me know what the results are
DefQoN_BE said:
Wow what a process. .. Odin back to stock recovery (not ROM only factory recovery e3 which can be found here http://droidbasement.com/galaxy/ ) do a factory reset in stock recovery and flash back cwm and cm10.1 with the right Gapps, let me know what the results are
Click to expand...
Click to collapse
Hi and thanks for your reply!
I can't find a e3 factory recovery in any of the subdirectories from that link, though. Before I used P7501XXLPC_P7501DBTLPC_DBT.zip from sammobile, I was under the impression that this will kill anything. At least the tar.md5 files contains boot, bootloader, cache, hidden, modem, recovery and system. However, I would be happy to try something else. I also read about repartitioning and also got a "u1_02_20110310_emmc_EXT4.pit" file, I am not sure if I used that in the early process.
SheridanJohn said:
Hi and thanks for your reply!
I can't find a e3 factory recovery in any of the subdirectories from that link, though. Before I used P7501XXLPC_P7501DBTLPC_DBT.zip from sammobile, I was under the impression that this will kill anything. At least the tar.md5 files contains boot, bootloader, cache, hidden, modem, recovery and system. However, I would be happy to try something else. I also read about repartitioning and also got a "u1_02_20110310_emmc_EXT4.pit" file, I am not sure if I used that in the early process.
Click to expand...
Click to collapse
Think it's under retail, recovery stock io or something like that http://droidbasement.com/galaxy/retail/
DefQoN_BE said:
Think it's under retail, recovery stock io or something like that http://droidbasement.com/galaxy/retail/
Click to expand...
Click to collapse
Hi,
it took a while as I made a complete backup.
Anyways, I used ODIN3 v1.85 with checks at Auto Reboot and F. Reset Time (default) and tried via PDA to flash the recorvery io, but it failed:
Code:
<ID:0/018> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery-stock_io.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/018> Odin v.3 engine (ID:18)..
<ID:0/018> File analysis..
<ID:0/018> SetupConnection..
<ID:0/018> Initialzation..
<ID:0/018> Get PIT for mapping..
<ID:0/018> Firmware update start..
<ID:0/018> recovery.bin
<ID:0/018> NAND Write Start!!
<ID:0/018>
<ID:0/018> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Flashing CWM 6.0.3.0 worked however (using the recovery.tar.md5 also from droidbasement)...
I was able to retrieve a recovery.img from the full firmware P7501XXLPC_P7501DBTLPC_DBT and create a tar.md5 just from recovery.img via cygwin:
Code:
>tar -H ustar -c recovery.img > recovery.tar
>md5sum -t recovery.tar >> recovery.tar
>mv recovery.tar recovery.tar.md5
This flashed ok and anounced itself as Android System Recovery 3e. Factory reset/wipe did format /data and format /cache.
I then flashed recovery.tar.md5 from droidbasement with CWM 6.0.3.0 and flashed CM 10.1 nightly 20130513 via sideload and the gapps gapps-jb-20130129-P75xx.zip from droidbasement.
Afterwards I rebooted into recovery and did an e2fsck on all partitions via adb shell. The e2fsck on /system did return immense amounts of errors:
Code:
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 15297 has zero dtime. Fix<y>? n
n
no
Inodes that were part of a corrupted orphan linked list found. Fix<y>? yes
Inode 15329 was part of the orphaned inode list. FIXED.
Deleted inode 15349 has zero dtime. Fix<y>? n
n
no
Deleted inode 15361 has zero dtime. Fix<y>? yes
Deleted inode 15377 has zero dtime. Fix<y>? n
n
no
Inode 15381 is in use, but has dtime set. Fix<y>? yes
Inode 15381 has imagic flag set. Clear<y>? n
n
no
Inode 15381 has a extra size (65535) which is invalid
Fix<y>? yes
Inode 15381 has compression flag set on filesystem without compression support. Clear<y>? n
n
no
Inode 15381 has INDEX_FL flag set but is not a directory.
Clear HTree index<y>? yes
Inode 15381 should not have EOFBLOCKS_FL set (size 18446744073709551615, lblk -1)
Clear<y>? n
n
no
Inode 15381, i_size is 18446744073709551615, should be 0. Fix<y>? yes
Inode 15381, i_blocks is 4294967295, should be 0. Fix<y>? n
n
no
Inode 15382 is in use, but has dtime set. Fix<y>? yes
Inode 15382 has imagic flag set. Clear<y>? n
n
no
Inode 15382 has a extra size (65535) which is invalid
....
The other partitions are fine:
Code:
~ # e2fsck -fn /dev/block/platform/sdhci-tegra.3/by-num/p5
e2fsck -fn /dev/block/platform/sdhci-tegra.3/by-num/p5
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/platform/sdhci-tegra.3/by-num/p5: 15/28672 files (6.7% non-contiguous), 3720/114688 blocks
~ # e2fsck -fn /dev/block/platform/sdhci-tegra.3/by-num/p8
e2fsck -fn /dev/block/platform/sdhci-tegra.3/by-num/p8
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/platform/sdhci-tegra.3/by-num/p8: 14/3825664 files (0.0% non-contiguous), 286204/15275644 blocks
I dd'ed /dev/zero over p4 (system) and checked the other partitions again, they were fine. I then reinstalled CM 10.1 and gapps, rebooted recovery and rechecked the filesystem...
Code:
~ # dd if=/dev/zero of=/dev/block/platform/sdhci-tegra.3/by-num/p4
dd if=/dev/zero of=/dev/block/platform/sdhci-tegra.3/by-num/p4
dd: writing '/dev/block/platform/sdhci-tegra.3/by-num/p4': No space left on device
1183745+0 records in
1183744+0 records out
606076928 bytes (578.0MB) copied, 110.833892 seconds, 5.2MB/s
...
~ # e2fsck -fn /dev/block/platform/sdhci-tegra.3/by-num/p4
e2fsck -fn /dev/block/platform/sdhci-tegra.3/by-num/p4
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/platform/sdhci-tegra.3/by-num/p4: 1544/37040 files (0.3% non-contiguous), 83490/147968 blocks
Now it was clean after installation...!!
What do you think, should I dd all other partitions like /cache, /data as well? How can this be at all? Flash error that was relocated now?
=> addition:
I thought I will try my luck and reflash the nightly. Afterwards, I again had many file system errors on /system...
BTW: Did you ever try to e2fsck your system partition from recovery? Hardly imagine that it is normal to have file system errors, but who know. My Galaxy Nexus has none, though.
make_ext4fs responsible for errors...?
Hi,
I did some more tests and could reproduce a faulty file system with the following steps:
- install something on /system
- run make_ext4fs on partition p4 (/system), either with or without -w (wipe, apparently not doing anything as it is "afraid" of the EMMC bug, that my device does not even have according to the emmc tester app)
- run e2fsck on that partition
et voila => endless file system errors.
This can't be normal (and harmless), can it? Looks however more like a problem with make_ext4fs if the wipe step is omitted.
If I run make_ext4fs with "-t" option (which apparently initialized the unused inodes), the file system is clean afterwards and stays clean during further runs of make_ext4fs and also during installation of CM. However, another installation of CM will then call make_ext4fs without -t and then the errors are back.
In my opinion the problem here is, that wipe is not executed at all and (without the -t option) the inodes contain some data. Not sure, how this affects the file system, though. Maybe it does not matter at all, however it is somewhat confusing that there are errors right after the fs creation...
Hi,
noone any ideas on this issue?
Gesendet von meinem Galaxy Nexus mit Tapatalk 2
Hi,
I'm sorry, I have no error solution, I can only list what I've done.
I flashed my Tab 10.1 N 3G with Odin / P7500XXLQ8_P7500OXALQ8_ITV.
TAB Worked with this Android 4.0.4 perfectly, also G3.
Later: Root; Flash Rom with CM first 5.x meanwhile 6.0.3. TWRP don't work on my device.
For Weeks i use CM 10.1 nightly and meanwhile kernel A1_P4_V1.9 work perfect - min 456MHz max 1600MHz ondemant / row
Antutu from 5000 points to round about 7000points
Franz H. said:
Hi,
I'm sorry, I have no error solution, I can only list what I've done.
I flashed my Tab 10.1 N 3G with Odin / P7500XXLQ8_P7500OXALQ8_ITV.
TAB Worked with this Android 4.0.4 perfectly, also G3.
Later: Root; Flash Rom with CM first 5.x meanwhile 6.0.3. TWRP don't work on my device.
For Weeks i use CM 10.1 nightly and meanwhile kernel A1_P4_V1.9 work perfect - min 456MHz max 1600MHz ondemant / row
Antutu from 5000 points to round about 7000points
Click to expand...
Click to collapse
Thanks for your reply. I can affirm that this combination (CM 10.1, A1 1.9) works very fine and smooth. With latest 1.9 I also get very good batterly life with very long deep sleeps. I reinstalled everything now, making sure I formatted all partitions cleanly and tested them for fs errors. So I hold my thumbs that it will continue working. I also updated not just by flashing new CM over old one, but by manually formatting /system using "make_ext4fs -t" beforehand.
At my first CM 10. installation, it was failed after a crash which needed a hard reboot (long power button). Afterwards, it would hang in the boot animation and I found fs errors on /data and /system. Maybe a glitch, maybe those errors were there before I installed it, who knows.
Hello guys,
I have a Ulefone Be Touch 2 (with a MT6752 cpu) that only boot and stay on the ulefone logo, and I can't install any ROM (official or custom ones)...
In fact, the tools (latest SPFlashTool v5.1628 and the one provided by ulephone I used successfully earlier) do the download process until 100% without error message, but the only thing that seems to be on the phone (and working) is the recovery.
With this two softwares I am able to install the official recovery or TWRP (2.8.7.0 from needrom), and they both are usable.
But when I try to do something in recovery mod, it tells me that cache or system partitions (and others) are not mounted (or found).
In SPFlashTool, I tryed many features without success but I have (NAND and UFS) errors when doing memory tests :
#External RAM:
#
# Type = DRAM
#
# Size = 0x80000000 (2048MB/16384Mb)
#
#NAND Flash:
#
# ERROR: NAND Flash was not detected!
#
#EMMC:
#
# EMMC_PART_BOOT1 Size = 0x0000000000400000(4MB)
# EMMC_PART_BOOT2 Size = 0x0000000000400000(4MB)
# EMMC_PART_RPMB Size = 0x0000000000400000(4MB)
# EMMC_PART_GP1 Size = 0x0000000000000000(0MB)
# EMMC_PART_GP2 Size = 0x0000000000000000(0MB)
# EMMC_PART_GP3 Size = 0x0000000000000000(0MB)
# EMMC_PART_GP4 Size = 0x0000000000000000(0MB)
# EMMC_PART_USER Size = 0x00000003a3e00000(14910MB)
#
#UFS:
#
# ERROR: UFS was not detected!
I don't understand what it meens and how can I change the recovery if the NAND is gone? Are system partitions and recovery stored in different places/memory (types)?
I searched and read on differents thread (the UBT2 review, mtk6755 ERROR: NAND Flash was not detected by split52 , [GUIDE] How to 'unbrick' your Mediatek MT65xx...) and googled and watched related videos but didn't find anything than matches and can really help me.
So, if someone can help me I would really be grateful.
Thank you in advance.
I'm sorry if I post this thread in the wrong section (I think it's the first I creat).
sylkyls
I had a problem like your's when I walked all over my partition layout because of a botched flash. Didn't have UFS errors tho. No info anywhere. Had to verify my scatter file and recovery fstab layout agreed with each other. Ended up modifying my scatter file. Took it one partition at a time using the fstab until the recovery recognized all partitions then backed up my files, reformatted and flashed the stock rom using SPF Tools. Took a while to boot. After that, the original scatter file worked. Still don't make sense why it worked that way but it got me back working.
smith901 said:
I had a problem like your's when I walked all over my partition layout because of a botched flash. Didn't have UFS errors tho. No info anywhere. Had to verify my scatter file and recovery fstab layout agreed with each other. Ended up modifying my scatter file. Took it one partition at a time using the fstab until the recovery recognized all partitions then backed up my files, reformatted and flashed the stock rom using SPF Tools. Took a while to boot. After that, the original scatter file worked. Still don't make sense why it worked that way but it got me back working.
Click to expand...
Click to collapse
Thank you smith901,
I don't know how to do this: I can run a terminal into the recovery but if I do cat /etc/fstab or less /etc/fstab , I only have :
/system ext4 rw
/cache ext4 rw
/data ext4 rw
/external_sd auto rw
I think I'm doing the wrong way.
Could you tell me (or redirect me to) a method please?
Have a nice day
sylkyls
sylkyls said:
Thank you smith901,
I don't know how to do this: I can run a terminal into the recovery but if I do cat /etc/fstab or less /etc/fstab , I only have :
/system ext4 rw
/cache ext4 rw
/data ext4 rw
/external_sd auto rw
I think I'm doing the wrong way.
Could you tell me (or redirect me to) a method please?
sylkyls
Click to expand...
Click to collapse
Seems to be fstab problems.
Use whatever unpacking tool you are comfortable with to unpack the stock recovery and TWRP. Then replace your fstab files in the root and /etc directories after changing what you want, rw to /system or whatever. Modify the twrp.fstab file in /etc using the values from stock fstab. You might have to add in or replace your rc and mt6735 files also. Repack then flash. The log screen in TWRP will let you know what partitions can't be read. Choosing the correct encryption partition took some trial & error.
Once you get it all to read, the modified twrp.fstab, files in the unpacked stock recovery folder plus a device tree, and the TWRP building thread will get a recovery built by yourself as soon as you can sync from git.
smith901 said:
Seems to be fstab problems.
Use whatever unpacking tool you are comfortable with to unpack the stock recovery and TWRP. Then replace your fstab files in the root and /etc directories after changing what you want, rw to /system or whatever. Modify the twrp.fstab file in /etc using the values from stock fstab. You might have to add in or replace your rc and mt6735 files also. Repack then flash. The log screen in TWRP will let you know what partitions can't be read. Choosing the correct encryption partition took some trial & error.
Once you get it all to read, the modified twrp.fstab, files in the unpacked stock recovery folder plus a device tree, and the TWRP building thread will get a recovery built by yourself as soon as you can sync from git.
Click to expand...
Click to collapse
Thank you again, but I'm really sorry that I can't apply your instructions... ( unpacking with 7-zip does not give me any fstab file )
Could you try to do it with the official rom please? ( download link is in the bottom of this page: http://ulefone.com/download/betouch2.html , at the next step my phone needs the "option 2" rar file).
With custom roms (zip files flashable with a custom recovery or rar archive), I can unpack thems and obtain/open a fstab file ( recovery.fstab ) but not with things flashable with SPFlashTool.
sylkyls
sylkyls said:
Thank you again, but I'm really sorry that I can't apply your instructions... ( unpacking with 7-zip does not give me any fstab file )
Could you try to do it with the official rom please? ( download link is in the bottom of this page: http://ulefone.com/download/betouch2.html , at the next step my phone needs the "option 2" rar file).
With custom roms (zip files flashable with a custom recovery or rar archive), I can unpack thems and obtain/open a fstab file ( recovery.fstab ) but not with things flashable with SPFlashTool.
sylkyls
Click to expand...
Click to collapse
I meant an unpacking tool like Carliv Image Kitchen or Android Image Kitchen. I'm rarely this helpful so once I finish cleaning the carpet I'll have a look.
The recovery.fstab file look slim in this recovery but that is what they made.
Download Aindroid Image Kitchen.
Follow the instructions to unpack your stock recovery and TWRP recovery.
Make the changes you want. Copy needed files, /etc/recovery.fstab, fstab.mt6752 and probably the *.rc files from stock to TWRP. Just check everything to be sure.
Repack TWRP then flash.
I don't use Windows so I couldn't use the program provided in the archive.
sylkyls,
did you solve the issue? I have the same problem.
cmarqz said:
sylkyls,
did you solve the issue? I have the same problem.
Click to expand...
Click to collapse
Hello,
Sorry every one but I forgot to follow this thread as I had a lot of work and someone giave me another phone ( a samsung note 4 N910F) that I repared (and am using now) and then I did let my ulefone away from my priorities.
Sorry cmarqz but I didn't try the solution proposed by smith901 on my MTK6752 device.
Maybe I'll try it later.
Did you find a solution for your device?
Best regards XDA users.
I need help to root my Aligator S5065 Duo phone. It ha Andoid 7.0 and the chipset is Mediatek MT6580.
Here is some info from the phone:
BB Chip : mt6580
MS Board. : ALIGATORS5065
Build Time : Tue Jan 23 15:35:41 CST 2018
Krenel Ver. : 3.18.35+ ([email protected]) (gcc version 4.8 (GCC)) #2 SMP PREEMPT Tue Jan 23 16:11:14 CST 2018
Android Ver. : 7.0
SW Ver. : alps-mp-n0.mp2-V1-droi6580.weg.n
Custom Build Verno. : unknown
IMEI1 : XXX
IMEI2 : XXX
Modem Ver. ALIGATOR_S5065_OS_1.1_2018 0123
Bar code : 010901MT000000000000003891_155648
The idea was:
1) make a full backup using MTK Droid Tool
2) flash TWRP using SP Flash Tool
3) boot TWRP and install Magisk
Problems:
1) MTK Droid Tool v2.5.3. doesn't support this chipset and I didn't found a newer version - so no full backup
I've tried to download a stock ROM or a full backup.
I have found MT6580__ALIGATOR__ALIGATOR_S5065__alps-mp-n0.mp2-V1_droi6580.weg.n__Android_7.0.ispff but it seems to need Infinity CM2 Dongle for flashing, which I don't own.
I have also found ALIGATOR S5065 – 7.0_MT6580_WL581M.LG.ALIG.HB.N.F.S12.B18.0927.V3.02_OS_1.1_20170927.zip which seems to be usable but not exactly the same as I have in my phone, at least it contains a scatter file. With the help of this scatter file I have I've read back my phone but the read imgs are considerably bigger, than the original ones in the zip - that doesn't seem right?
2) I have downloaded TWRP_3.2.3-0_20180803_UNOFFICIAL_MT6580_N.zip which should be a TWRP recovery for my chipset and the same kernel version, so I hoped it could work. But when trying to flash it with SP Flash Tool I get "PMT changed for the ROM" error message. The suggested solution for this error seem to be very risky (formating the phone, atc.), so I didn't dare to try ...
Now I'm stuck and I don't know how to proceed.
Any help would be really appreciated
Some progress:
I got a custom TWRP recovery image from Matty1993 <- thank you very much
I flashed it using adb and fastboot:
adb devices - successfully listed my device
adb reboot bootloader
fastboot flash recovery c:\adb\recovery.img - got this error message: "FAILED (remote: 'not allowedin locked state')"
Locked bootloader, unlocking ...
fastboot flashing unlock
- (bootloader) Start unlock flow
- OKAY [ 18.800s]
- Finished. Total time: 18.816s
Flashing the recovery.img
fastboot flash recovery c:\adb\recovery.img
Sending 'recovery' (10226 KB) OKAY [ 0.359s]
Writing 'recovery' OKAY [ 0.640s]
Finished. Total time: 1.030s
Success
fastboot reboot-bootloader
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.016s
fastboot erase cache (I don't know if it was a good idea but it was in the tutorial, I was following)
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' OKAY [ 0.109s]
Finished. Total time: 0.125s
fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.016s
Now when booting the phone complains:
Orange state
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
In 5 second it starts to boot but it stays forever on the "POWERED BY android" logo
I can boot to TWRP recovery (also fastboot), so I did and flashed magisk (because the main goal was to root my phone) and selected to delete cache/dalvik.
I'm not able to switch off the phone, it reboots. I had tu pull the battery (luckily it's removable).
The phone info changed
BB Chip : mt6580
MS Board. : ALIGATORS5065
Build Time : Tue Jan 23 15:35:41 CST 2018
Krenel Ver. : 3.18.35+ ([email protected]) (gcc version 4.8 (GCC)) #2 SMP PREEMPT Tue Jan 23 16:11:14 CST 2018
Android Ver. : 7.0
SW Ver. : alps-mp-n0.mp2-V1-droi6580.weg.n
Custom Build Verno. : unknown
IMEI1 : unknown
IMEI2 : unknown
Modem Ver. ALIGATOR_S5065_OS_1.1_2018 0123
Bar code : unknown
The IMEIs and Bar code are now "uknown".
What did I wrong and what to do, to fix it?
forget MTK Droid Tool it is outdated and does not support scatter for devices > 4 GB. you can use SP Flash Tool for full ROM dump. First thing you should do is backup your nvram partition, hopefully it is not too late...
https://www.getdroidtips.com/backup-restore-imei-nvram-data-mediatek
If you already have backup of stock boot.img:
- copy file to /external_sd/TWRP/BACKUPS folder
- rename it to boot.emmc.win
- create a backup of current boot (just in case)
- restore renamed stock boot.emmc.win from TWRP
regarding boot stuck:
- Format Data and Wipe Cache from TWRP, reboot recovery, wipe again (Wipe -> Format Data -> type yes)
- reboot TWRP, check if /system /data and /cache is mounted/mountable (you should see folders or files inside)
- reboot system and wait 5 minutes, first boot may take a while because the data partition is forced encrypt
- if android is completely booted, check IMEI
Now, if your device is in good condition, reboot recovery and make a full TWRP backup.
Thank you very much for your help.
I did a dump before, using the SP Flash Tool and the scatter from the downloaded ALIGATOR S5065 – 7.0_MT6580_WL581M.LG.ALIG.HB.N.F.S12.B18.0927.V3.0 2_OS_1.1_20170927.zip file.
So I have a sort of a "backup"
Now I'm going to read and I'll report back how it went.
blakegriplingph said:
NVRAM data must have been wiped off somehow, as that's one reason as to why your serial numbers have gone kaput.
Click to expand...
Click to collapse
If this is the case, you can "download" (=flash) your backup files from SP Flash Tool. In scatter file change entries to "is_download: true". Open the edited scatter file with SP Flash Tool. Make sure you uncheck all checkboxes, except nvram, nvdata (and cache, if you still have problems with this partition). Double click on file name and select the file for each partition. Make sure EMMC_USER is selected. The file sizes must fit partition size. Do NEVER flash PRELOADER! Press start, then connect phone, then insert battery.
nvram.bin 5120 KiB (0x00500000)
nvdata.bin 32768 KiB (0x02000000)
cache.img 409600 KiB (0x19000000)
If done, hold Volume Up key while unplug + plug in USB cable, this will boot into recovery. Wipe Cache and Data
My sizes of the backup files:
nvram.bin 5 242 880 seems OK
nvdata.bin 33 554 432 seems OK
cache.img 419 430 400 bigger
Is there a way I can check the integrity of them before flashing?
And what when I get the "PMT changed for the ROM" error message?
I've attached the used scatter file
Should be fine if you use same scatter file used for read back. If you got "PMT changed" (probably wrong scatter file), you must restore all partitions (except preloader) with the exactly same scatter file you have created your backup. Then your phone should be restored to its original state no matter if scatter file was wrong. Once you get your phone in good condition, you can create your own scatter file with current partition layout from WwR MTK v2.30
Matty1993 said:
All good mate yeah orange state is because you unlocked bootloader and didnt factory reset [...]
If you still get dramas with orange state let me know ill manually patch the dm-verity out of your boot.img for you
Click to expand...
Click to collapse
Orange state just mean unlocked bootloader, you can't get rid of. Do not lock the bootloader again, just leave it orange state is fine...
I thought so and it doesn't really bother me
Matty1993 said:
Your device comes with out of the box encryption in your boot.img fstab your system path will be /dev/block/platform/mtk-msdc/******/msdc/by-name/system /system ext4 ro wait, "verify"
Click to expand...
Click to collapse
Zdendav said:
I did all the steps:
- wipe, format
- factory reset
hangs on the "POWERED BY android" logo, when trying to boot
- flashed boot.img in fastboot
- reboot
I was not fast enough to go onto TWRP, it tried to boot, hangs on the "POWERED BY android" logo
-reboot into TWRP
- wipe, format
- factory reset
still hangs on the "POWERED BY android" logo, when trying to boot
I can borrow exactly the same phone from a relative (fully working) - maybe I should do a full backup of it, then I'll have "clean" images of boot, recovery etc.
Meanwhile I did another full backup and this time I used WwR MTK v2.30 to create a correct scatter.
I attach both scatter files.
Click to expand...
Click to collapse
as @Matty1993 already figured out, your phone seems fine, just dm-verity prevents to boot because of recovery checksum mismatch. You have to disable dm-verity.
Install Disable_Dm-Verity_ForceEncrypt.zip from TWRP. This will patch your boot.img and modify fstab entries. Format Data, then use "Copy Log" option and upload recovery.log here
aIecxs said:
Should be fine if you use same scatter file used for read back. If you got "PMT changed" (probably wrong scatter file), you must restore all partitions (except preloader) with the exactly same scatter file you have created your backup. Then your phone should be restored to its original state no matter if scatter file was wrong. Once you get your phone in good condition, you can create your own scatter file with current partition layout from WwR MTK v2.30
Click to expand...
Click to collapse
I did try and I got the "PMT changed" even when I selected all partitons except preloader ..
I did borrow exactly the same phone from a relative and created a full backup and from it a proper scatter file. I compared both scatter files and there are differences (as expected)
I attach both scatter files
I don't know how to proceed.
1) Lock the bootloader?
2) Flash parts from the borrowed phone? Which parts?
PS I have also a backup of userdata taken in factory mode.
don't flash anything with SP flash tool, just see my previous post. boot + recovery + nvram are identical, but tee1 + tee2 + teeinfo missing, and metadata + userdata have different size. keep the backup created with scatter file from WwR_MTK this seems to be the right one
aIecxs said:
Install Disable_Dm-Verity_ForceEncrypt.zip from TWRP. This will patch your boot.img and modify fstab entries. Format Data, then use "Copy Log" option and upload recovery.log here
Click to expand...
Click to collapse
Done. Did it all in one go (without any reboot), then powered off.
Log is attached
aIecxs said:
don't flash anything with SP flash tool, just see my previous post. boot + recovery + nvram are identical, but tee1 + tee2 + teeinfo missing, and metadata + userdata have different size. keep the backup created with scatter file from WwR_MTK this seems to be the right one
Click to expand...
Click to collapse
Sorry I missed your post until I posted mine ...
I'll keep all backups until it's sorted out.
And thank you very much aIecxs and Matty1993 for all your help
thanks for the log. seems there is something wrong, maybe with TWRP or maybe with phone.
Code:
E:Primary block device '/dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/userdata' for mount point '/data' is not present!
Failed to mount '/cache' (Invalid argument)
Error installing zip file '/external_sd/Disable_Dm-Verity_ForceEncrypt_04.03.19.zip'
Flash stock boot.img and stock recovery.img from fastboot. reboot into stock recovery. Wipe Data + Cache. reboot to bootloader. boot into TWRP from fastboot. copy log to sdcard and upload again. reboot your phone and wait 5 minutes.
I flashed the stock recovery and boot in fastboot in one go.
Then rebooted to recovery but there is only "Supported API: 3" in the lower left corner of the display and that's all.
What to do next?
Edit: It's even worse, I'm not able to enter fastboot, recovery etc., the phone doesn't react to the volume button and always show the orange message a boot to the Supported API: 3 screen.
This indicates something is wrong with cache partition. Usually a normal system boot from stock boot.img will fix this. If you can't enter fastboot mode, flash recovery from SP Flash Tool. Try this version it has changed fstab. This should fix the /data mount. Then you should be able to enter fastboot again.
Code:
[strike]/data ext4 /dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/userdata flags=encryptable=/dev/block/platform/mtk-msdc.0/by-name/metadata[/strike]
/data ext4 /dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/userdata flags=encryptable=/dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/metadata
Regarding /cache try following from fastboot:
Code:
fastboot format:ext4 cache
after this wipe cache again from stock recovery (you can boot stock recovery from fastboot without flashing it). if cache still not mounted in TWRP, your only choice left is flash backup of cache partition from your friends phone from SP Flash Tool
edit: attachment deleted
Flashed your recovery, now it always boots into twrp, volume buttons still seem to not work, I'm still not able to enter fastboot.
Edit: I was able to enter fastboot by "adb reboot bootloader" when in TWRP, strangely "adb reboot fastboot" booted into TWRP.
I formatted the cache, rebooted into stock recovery, formatted the cache again.
Rebooted into TWRP, in file manager the cache is empty, in the mount menu I'm not able to tick any of the listed partitions to mount it ...
I'm not able to post the new log, it copies it to /data/media but in the file manager the location is empty ...
i have added some mount points, please download and flash again. you can copy recovery.log from adb
Code:
adb pull /tmp/recovery.log C:\adb\recovery.log
please post output of df and mount
Code:
adb shell
mount
busybox df -aT
/ # mount
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/ # busybox df -aT
Filesystem Type 1K-blocks Used Available Use% Mounted on
tmpfs tmpfs 463204 44 463160 0% /dev
devpts devpts 0 0 0 0% /dev/pts
proc proc 0 0 0 0% /proc
sysfs sysfs 0 0 0 0% /sys
selinuxfs selinuxfs 0 0 0 0% /sys/fs/selinux
tmpfs tmpfs 463204 32 463172 0% /tmp
adb functionfs 0 0 0 0% /dev/usb-ffs/adb
Hello Guys,
like the Title tells i got Problems rooting my Samsung S10
I follow this Guide: https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
and already tried to look up the error i get but i didnt find anything usefull yet
so everything works fine till i have to flash the Magisk Patched AP to my phone then it fails at vendor.img and after a Reboot the System is damaged. After that i just flash the unpatched AP and it works again but no matter how often i retry all steps or just the flashing part it always fails at the Vendor.img now i wanted to ask if anyone could help me or atleast tell me whats the mistake
Spoiler: Other maybe Useful Screens
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Spoiler: Log from Odin
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1401)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 7084 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> param.bin
<ID:0/007> up_param.bin
<ID:0/007> cm.bin
<ID:0/007> keystorage.bin
<ID:0/007> uh.bin
<ID:0/007> vbmeta.img
<ID:0/007> dt.img
<ID:0/007> dtbo.img
<ID:0/007> system.img
<ID:0/007> vendor.img
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Look below.
||||| said:
S10 Root Tutorial - optimized (orange)
S10/e/+ Root & Custom Rom Guide
Credits go to our Hero TopJohnWu & Developers & Contributors!
I attached the original File (see at the bottom)
Change log
• 21/06/2019 – Initial Version
• 03/09/2019 – Correct typo with Download Mode key combo
• 11/09/2019 – Added link to Telegram group in ROM section
• 11/09/2019 – Added change log.
• 12/09/2019 – Add note about TWRP version
• 07/12/2019 – added some more Notes & Nice to Knows |||||
Details
This guide will help you take your virgin S10 phone to a fully rooted phone running a custom rom.
It is highly recommended that you use an external SD card for this process as the steps has you formatting the internal data a couple of times, so having this on an external SD will keep this all intact.
Also note that MTP to your phone via a PC can get varied results, hence why again using an SD card is recommended as with an adaptor you can plug this straight into your PC and into phone when needed.
You must understand - that you always have to handle the Booting Process manually with the key combinations of Buttons after flashing - else you will have reboots and fails(no twrp etc)!
--Download Latest/your Official Firmware Version (PC)--
• On PC Download Samfirm from the following link: Updato& Sammobile (S10-Example) or search on google
• Extract the zip and run samfirm.exe
• Enter your model and Region (I.E Model=G975F, Region=BTU)
• Tick ‘Auto’
• Click Check Update
• It should show you the latest firmware version
• Click Download
• Firmware will download and decrypt (if Decrypt automatically was ticked)
• Default download location (My Documents)
>> • Prepare those Files (Unpack them) and get them on your External SD-Card - you will need them later <<<
--Download ODIN 3.13.1 (PC - FLASHSOFTWARE) --
• Go here and download the latest version of ODIN
>>> • Be sure to uncheck "Auto-Restart" later on - because there is a Twist to this (see Tipps&Tricks) <<<
--Unlock Bootloader--
**WARNING THIS WILL WIPE YOUR DATA**
• Enable developer Settings
(Settings > About Phone > Software Information > Tap build number 7 times (Enter your device pin)
• Go into Developer option and enable ‘OEM Unlocking’ (Enter Device Pin)
>>> THIS WILL ONLY SHOW UP - IF you have Internet activated (WLAN or 3G/LTE) & you must set your Date 7+ Days into the Future! <<<
• WARNING MESSAGE: Click turn on
• Power off your phone
• Hold Bixby + Volume Down and plug in your phone to your PC
>>> Bixby + Volume down + USB-Cable (plug it) = Downloadmode <<<
Download mode should now be shown
• Hold Volume Up, you’ll get a warning message, then press volume up to accept.
• This will now wipe your data and automatically reboot
• Boot the phone
• Go through initial set-up but skip everything for now
• Enable developer mode again and OEM unlocking (or should be enabled and greyed out)
• You are now done, and your bootloader will now allow ‘Unofficial Images’
--Download Latest TWRP (Phone)--
• On your phone Download the latest TWRP image for your model to the phone external SD card from here
• **NOTE – If you are installing Beyond Rom version 5.3 and onwards then you need to download a minimum of TWRP version 3.3.1-7
• We will need this later….
--Patch Firmware & TWRP File--
• On your PC extract the firmware files (AP, BL, CP and HOME_CSC)
• Copy the AP file to your SD card and enter SD card in your phone
• On your phone download the latest Magisk Manager APK from here
• Install the app.
• You may need to allow to “Install Unknow Apps” for chrome
1. Load up Magisk Manager on your phone
2. Next to ‘Magisk is not installed.” Click Install
3. Click Install on the pop up
4. Click ‘Select and Patch a File’
5. Select the AP file you copied across to your external SD
6. Magisk will now patch the AP file
7. A file called magisk_pached.tar will be created
• Repeat steps 2-4 but this time for the TWRP image file you downloaded earlier to your external SD.
• At the end of this process you should have two files
magisk_patched.tar and magisk_patched.img
• One is a Magisk patched version of TWRP (.IMG) and the other is a Magisk patched version of stock rom (.TAR)
--Rename and repackage--
• Remove the SD card from your phone and plug into PC
• Copy the above files from the SD to you PC
magisk_patched.tar & magisk_patched.img
• Rename the file magisk_patched.img to recovery.img
• Open the file magisk_patched.tar using a zip tool (I.E 7Zip) inside the archive remove the existing recovery.img and replace with the new patched recovery.img you made above
--Download Multi-disabler (Phone)--
• On your phone download multi disabler from here
• Ensure this is on your External SD card
--Download Custom Rom (Beyond) (Phone)--
• Head over to the ROM telegram group to download the latest version of Beyond ROM and tips/tricks and notices the telegram group is here
• Download the latest ROM to your phone.
• Ensure this is on your External SD Card
--Flash Patched File--
• Turn off your phone and boot into download mode (Hold BIXBY + VOL DOWN + Plug in USB)
• Press volume up to enter download mode
• On PC load up Odin
• Using the patched file and other files you extracted earlier place the following files in the following location
AP = magisk_patched.tar (Created above with custom patched recovery.img inside)
BL = BL_XXXXXXX (Extracted from original firmware file)
CP = CP_XXXXX (Extracted from original firmware file)
CSC = HOME_CSC_XXXXXX (Extracted for original firmware file)
• Under the options tab ensure ‘AUTO REBOOT’ is not ticked
• Click Start – This should take 5 – 10mins to complete.
--Full Data Wipe--
**DO NOT SKIP THIS STEP**
• Your phone should still be in Download Mode
• Review the next few steps to familiarise yourself with the button combinations
• Press Power + Volume Down for a few seconds to exit download mode
• AS SOON AS THE SCREEN GOES BLACK
HOLD Power + Bixby + Volume Up
KEEP HOLDING THESE KEYS UNTIL YOU SEE THE TWRP LOGO
• If TWRP runs a script and then reboots, immediately hold the same buttons again to get back into TWRP
--Multidisabler and Date Wipe--
• Click Install and select the Multidisabler.zip you downloaded earlier – DO NOT REBOOT
• Back to main menu in TWRP select WIPE>FORMAT DATA and TYPE YES, CLICK TICK BUTTON
**WHEN COMPLETE DO NOT REBOOT**
• Back to menu of TWRP select WIPE and swipe to do a Factory Reset (Data, Cache and Dalvik wipe) **WHEN COMPLETE DO NOT REBOOT**
• Back to main menu, Click Reboot, and Choose Recovery (Don’t hold any Buttons)
• The system will start booting (and will automatically reboot the first time)
• When booted, complete the initial set-up (Internet Connection is required), If you are going to custom rom, then you can skip logging into your account.
• Open Magisk (if it’s not in your app draw then manually install)
• Complete the steps required by Magisk
--Install Custom Rom (Beyond Rom)--
• Power off your phone
• Hold Power + Bixby + Volume Up until you see the TWRP logo
• Click Install
• Select the Beyond custom rom zip you downloaded to your phone earlier
• Follow the Aroma install options (do clean install the first time)
• When flash is complete, use reboot option and select reboot to recovery.
>>> DO NOT JUST REBOOT AFTER FLASHING - ALWAYS GO BACK IN MAIN MENU > REBOOT MENU & BOOT INTO RECOVERY - SO YOU WILL HAVE ROOT - OTHERWISE NOT! <<
• Congratulations you now have Custom rom installed on your S10.
Notes/Tips/Tricks
• Every time you reboot you will need to use the key combo or..
>>> Do this right after the flashing Process - when you it restarts - or better restart manually <<
◦ Hold Power + Bixby + Volume Up to TWRP logo to enter recovery
◦ Hold Power + Bixby + Volume Up until you see the Samsung warning screen for the 2nd time to boot into rooted rom.
When you get Stuck or something doesn't go well - don't worry - you can always flash a patched TWRP by itself!
• Go to Download Mode
• Use a patched TWRP and put it as recovery.img inside a recovery.tar (you create the archive (pack the .img as a .tar instead of .zip) using 7zip or similar)
• After you flashed it successfully and the screen turns dark (your restart)
- you instantly hold VOLup + Bixby + Power Button ( over the first 2 Screens)
- and let go, but hold VOLup down with your finger UNTIL TWRP comes up! - you are safe now! (almost) :silly: :victory:
>>> DO NOT JUST REBOOT AFTER FLASHING - ALWAYS GO BACK & BOOT INTO RECOVERY - SO YOU WILL HAVE ROOT - OTHERWISE NOT! <<
• Edxposed works for Pie and supports some functionality for Samsung phones like:
◦ Removing high volume warning
◦ Removing high brightness warning
◦ Advance power menu (Reboot to recovery, download etc..)
◦ Details can be found here
Here is a Video as well, wich is good to follow
But after you did this all in the Video - you need to flash patched TWRP!
I recommend to do it right after the patched AP File - let it stay in downloadload-mode, plug the usb-cable out and back in and flash the recovery.tar!
And you will have TWRP and now you can flash ROMS & BACKUP etc !
TWRP has also has File Manager - you can move/copy folders & files from internal to external etc
ok, well I added everything in orange what else was needed to be said! Wich I had to find out the hard way... and wich saves lots of Time!!
I still not slept for over 42 and wrote all this the last 2 hours, because I was so excited and wanted to give back! (and the Backup goes from internal to external at the same time
I will may add more to this Thread here... I have many tipps & tricks... wich is not so easy to find out first
I wish you all the best with your Rooted Samsung S10 S10+ etc
God bless you & sleep well
Best regards :victory:
|||||
Click to expand...
Click to collapse
Here.
Kenora_I said:
Look below.
Click to expand...
Click to collapse
so that is basically what i did and what didn't work.
Parelath said:
so that is basically what i did and what didn't work.
Click to expand...
Click to collapse
Did you follow each steps correctly?
Did you install a custom ROM?
I am just trying to install Magisk nothing else and yeah i did the steps multiple times with the same outcome it always fails at the Odin Flash part.
Parelath said:
I am just trying to install Magisk nothing else and yeah i did the steps multiple times with the same outcome it always fails at the Odin Flash part.
Click to expand...
Click to collapse
So you did flash a custom rom successfully and the issue is when you flash the modified AP?
so no i did not flash a custom rom it is not required for Magisk
like i said i just try to flash the Patched Magisk AP and it always fails at the Vendor.img
.
ianmacd said:
The multi-disabler started life on the Exynos S10 range, the first Samsung devices to launch with Android 9 (Pie). Since then, it has grown to support a great many Samsung devices running either Android 9, 10 or 11, and with either an Exynos or a Qualcomm SoC at their core. This includes the S10 and S20 series, the N10 and N20 series, the A10 - A70 series, the Tab A and Tab S series, Z Flip and (Z) Fold devices, and many more.
When flashed onto a compatible device, the multi-disabler will semi-permanently disable a number of device protection features and services that become problematic on a rooted device. Some pose a threat to the rooted state of the device, while others become dysfunctional and generate a flood of log messages. Semi-permanently in this context means that the disablement will persist until re-enabled by the user, for example as a side-effect of flashing new firmware with Odin. You will therefore need to reflash the multi-disabler every time you perform a system-wide firmware update.
The methodology of the multi-disabler is the path of least intervention. This means that for any given device, only those services that must be disabled to ensure the smooth operation of the device will be tackled.
The following is a list of features disabled by the multi-disabler on Samsung devices launched in 2019:
FBE (file-based encryption): Until this is disabled, most versions of TWRP — all for Exynos devices and many for Qualcomm — cannot read files on /data (the userdata partition). You must format /data to actually remove FBE after disabling it. Back up your data first!
Vaultkeeper: Magisk now dynamically disables this during boot, but if you boot outside of Magisk, it will return with a vengeance on some devices.
Process authentication (a.k.a. proca): This service must be disabled on some devices in order to use a custom kernel without problems. Note that all 2019 devices with TWRP utilise a custom kernel for Android, because the same kernel is shared by Magisk to boot the system. This does not apply to devices lauched in 2020 and later.
Stock recovery auto-restoration: In certain circumstances, your device will automatically restore its stock recovery partition, overwriting your custom recovery (TWRP). Magisk now also provides dynamic protection against this, but again, this will not save you if you boot outside of Magisk.
wsm: On Android 10 and 11, this service prevents Samsung smartwatches from connecting to the Galaxy Wearable app.
Extra services are disabled as needed per device.
Furthermore, when the ZIP file is renamed to contain the string _btfix somewhere in the name and the file is then flashed on a supported Android 10 device, the system's libbluetooth.so library will be patched in situ to prevent the loss of Bluetooth pairings across reboots. This is a recurring issue with many rooted Samsung devices manufactured before 2020 and updated to Android 10. Devices launched in 2020 and later do not need this patch.
The multi-disabler's support for this solution is limited to a relatively small number of Samsung devices and is deprecated as of v3.0. It will be removed in a future release.
If you find that patching fails on your device, please refer to Arthur Trouillot's superior libbluetooth patcher, which supports a much wider variety of devices.
The multi-disabler is written in Bourne shell, so you can — and ideally should — audit the code yourself to ensure its safe operation. It's performing open-heart surgery on the software of your device, so you should not simply trust it. Apart from anything else, bugs can creep in from time to time, despite or sometimes even because of my refactoring of the code.
The multi-disabler is idempotent, which means you can safely flash it multiple times without incurring unintended side-effects.
The package is attached to this posting and the code is available on GitHub.
Click to expand...
Click to collapse
Have you also flashed this?
ianmacd said:
If rooting with Magisk alone and in accordance with John Wu's instructions, this disabler isn't needed. If you're going to use a rooted TWRP image instead of stock recovery, however, then you're probably going to want to flash it.
Click to expand...
Click to collapse
no i didnt yet.
do i need it cause here he says its not needed if i only flash magisk
and isnt that a Post Flash process?
Do you have ramdisk when looking in magisk?
it says No
Parelath said:
Hello Guys,
like the Title tells i got Problems rooting my Samsung S10
I follow this Guide: https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
and already tried to look up the error i get but i didnt find anything usefull yet
so everything works fine till i have to flash the Magisk Patched AP to my phone then it fails at vendor.img and after a Reboot the System is damaged. After that i just flash the unpatched AP and it works again but no matter how often i retry all steps or just the flashing part it always fails at the Vendor.img now i wanted to ask if anyone could help me or atleast tell me whats the mistake
Spoiler: Other maybe Useful Screens
View attachment 5365435
View attachment 5365437View attachment 5365439
Spoiler: Log from Odin
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1401)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 7084 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> param.bin
<ID:0/007> up_param.bin
<ID:0/007> cm.bin
<ID:0/007> keystorage.bin
<ID:0/007> uh.bin
<ID:0/007> vbmeta.img
<ID:0/007> dt.img
<ID:0/007> dtbo.img
<ID:0/007> system.img
<ID:0/007> vendor.img
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Magisk in RecoveryIf your device does not have ramdisk in boot images, Magisk has no choice but to hijack the recovery partition. For these devices, you will have to reboot to recovery every time you want Magisk enabled.
Since Magisk now hijacks the recovery, there is a special mechanism for you to actuallyboot into recovery mode. Each device model has its own key combo to boot into recovery, as an example for Galaxy S10 it is (Power + Bixby + Volume Up). A quick search online should easily get you this info. As soon as you press the combo and the device vibrates with a splash screen, release all buttons to boot into Magisk. If you decide to boot into the actual recovery mode, long press volume up until you see the recovery screen.
As a summary, after installing Magisk in recovery (starting from power off):
(Power up normally) → (System with NO Magisk)
(Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
(Recovery Key Combo) → (Splash screen) → (Long press volume up) → (Recovery Mode)
(Note: You CANNOT use custom recoveries to install or upgrade Magisk in this case!!)
So you read the above?
ok so u now just repeat the stuff said in the guide i linked?
i told u i do everything step by step but as soon as i have to flash the AP i cant cause it fails at the vendor.img nothing post flash its WHILE flashing it fails
Yeah i got that before posting, internet sucks right now.
Parelath said:
ok so u now just repeat the stuff said in the guide i linked?
i told u i do everything step by step but as soon as i have to flash the AP i cant cause it fails at the vendor.img nothing post flash its WHILE flashing it fails
Click to expand...
Click to collapse
When patching the AP file did you select recovery mode in magisk?
And im assuming you used adb pull not MTK to transfer the file to the pc
yep i checked Recovery Mode
and used the adb method so the file wont get corrupted
Parelath said:
yep i checked Recovery Mode
and used the adb method so the file wont get corrupted
Click to expand...
Click to collapse
And your sure the vendor.img is the issue. Dosent Odin give a err code?
Oh, and you should be using the latest version and the binary should be the same.