Hi everyone,
My galaxy S recently had the "System UID Inconsistent" problem. As solution, everyone says to wipe data, or reinstall the rom. I've did it a lot of times, and this still continues. I've now installed the clockwork recovery mod to try to wipe the data and fix permissions.
The strange thing is that I mount the USB Storage, delete ALL FILES ON THE PHONE, and go back to the recovery ALL FILES ARE BACK THERE. I don't have any clue on what is happening, why all files get back to the phone, and why i can't delete the files on it. Can someone help me?
Hi Mate,
Follow the link posted below and hopefully your problem will be fixed.
http://www.theandroidsoul.com/ezbase-ezrom-for-android-2-2-install-revert-back/
Cheers
Tryed it, FAILED
With the "Repartition" ticked, it give an error that can't do the repartition... Without it checked, it completes the proccess, but he doesn't finish to boot.
I think that the data partition is really ****ed up... when it finish to install the official rom when it comes to the recovery mode, it gave me some errors on dbdata (he can't write it) and some errors to wipe the data partition.
here are some errors that usually occurs.
Flash errors said:
E:failed to mount /dbdata (File Exists)
E:delete_data_files:Can't mount /dbdata
your storage not prepared yet, please use UI menu for format and reboot actions.
Media File copy Error
-- Deleting files...
E:failed to mount /dbdata (File Exists)
E:delete_data_files:Can't mount /dbdata
your storage not prepared yet, please use UI menu for format and reboot actions.
-- Updateing filesystem...
E:failed to mount /dbdata (File exists)
E:discard_filesystem_for_rfs:Can't mount /dbdata
-- Wiping cache
Formating /cache...
Cache wipe failed.
--Applying Multi-CSC...
(here all goes ok)
Click to expand...
Click to collapse
Nobody? No one knows why files can't be Deleted? It's really bricked?
an idea..
hi dark,
you have a re-partition problem which means probably you made lagfix and you just install a new firmware wout taking lagfix back
you should install a firmware which has an ability to repart your phone. Your best alternative is I9000XXJPU 2.2 Froyo Rom which has a future with it. download it. from samfirmware and install it.
and then upgrade as u want to girgerbread etc..
i hope this helps
Ok. I'll try soon... but, I've never made a lagfix on my phone
hello,
i have the same problem. Have you found a solution?
thanks
Try what everyone said befora... but still don't get any clue about the problem
Do you have the I9000 M << by any chance ? These are know for SD card failures, resulting in strange behaviour like you have mentioned..
Also what firmwares have you tried to flash with odin ?
something waaaaay back always works for me, Something like Eclair with all 3 files and 512PIT... No matter whats issues i have encountered, That firmware always makes my phone better
Good luck, Hope you get it sorted
Mine is T ... I have read about the M problems and tryed the same with T ... but nothing worked... I've flashed 2.1 2.2 and 2.3 official roms but doesn't worked... I still have the "Undeletable partition" issue... I think that it'll be a Time Capsule, frozen files in time to record later.
undeletable partition sdcard and "System UID Inconsistent"
Hi Dark FlameS,
have you found a solution to your problem, I also have the same?
The only ROM that don't give me at the beginning the "System UID Inconsistent" is probably the last one I installed 2.3.5 i9000XXXJVS before the partition /sdcard became undeletable.
With that ROM I can use at least the phone to make phone call and navigate, but I can't install or delete any program on /sdcard.
This is very frustrating!
Please someone help us thank you very much in advance!
This is the log of ODIN and it seems there are no error but the /sdcard (internal sd) are always there!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_XFJVA_Sbl.tar.md5 is valid.
<OSM> PHONE_XXJVT.tar.md5 is valid.
<OSM> CSC_OXFJV1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> param.lfs
<ID:0/004> NAND Write Start!!
<ID:0/004> zImage
<ID:0/004> boot.bin
<ID:0/004> Sbl.bin
<ID:0/004> factoryfs.rfs
<ID:0/004> dbdata.rfs
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response form LOKE
<ID:0/004> cache.rfs
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
No, Haven't found any solution
I'm from Brazil, and this phone was bought over the internet and it's not from Brazil. I'm not sure if it is from New Zealand or Mexico...
I had seen some people telling that this occurs only with I9000T Early versions, and people who had this problem had changed their phone on the warranty... But, samsung Brazil says that they can't do nothing for me 'cause they don't have the software for my phone, just for the Brazillian version of the phone (I9000B)...
If your phone is not an I9000T, search a bit more for a solution, it may be just corrupted files. My case is that the filesystem won't write nothing more, so the phone can't delete the files there and neither write files.
I've seen that some Galaxy phones crash sometimes with files that has large names and lightbox photo app sometimes write files with these large names and the system file goes crazy, if you handle to delete these files, maybe your phone could work, if you're lucky.
Lightbox might have been the sparkle to this occurs to me, as it has occured in the day that I have instaled it. Or maybe it was changing the sd card that i had in there, that I've done in the same day...
I just could say to you know that I have no solution, the only solution will be buy a new phone. Hope that you're luckyer than me...
Thank you for the reply, mine it's a I9000 but I installed superuser.apk and for the same reason (undeletable file, apk, and partition) I can't delete it, so I don't think they will accept the warranty!
But you still could try the payed fix... they can't refuse... The problem with me is that samsung brazil only fix brazillian phones
Related
I am so hosed. I have been fighting with my Sprint Tab for the last few days and would really appreciate someone's help. I have had the phone ! computer error, stuck on the Samsung screen issue and now have finally successfully got back into CWM, and keep getting the following error. I can't get the system to reboot.
E:failed to mount /system (invalid argument)
/system may be rfs. Checking...
Checking /data...
Checking /datadata...
E:failed to moun /datadata (invalid argument)
/datadata may be rfs. Checking...
Checking /cache...
Done!
I successfully flashed a rom but when I reboot system it comes right back to CWM with this error. Tried to install the update.zip on page one for Gingerbread and get the following error:
Installing update...
file_getprop: failed to stat "/system/build.prop": no such file or directory
e:Error in /sdcard/update.zip
(status 7)
Installing aborted.
the dbdata is corrupt
its mean you have to re-flash back with PIT and pit file
basically follow the guide here : http://forum.xda-developers.com/showthread.php?t=1133590
k0sh said:
the dbdata is corrupt
its mean you have to re-flash back with PIT and pit file
basically follow the guide here : http://forum.xda-developers.com/showthread.php?t=1133590
Click to expand...
Click to collapse
Thanks for the info. I have been on this page and tried the link for Sprint, I will try again and see if I have any success.
tallen said:
Thanks for the info. I have been on this page and tried the link for Sprint, I will try again and see if I have any success.
Click to expand...
Click to collapse
try to put the pit file and flash it 1st , and then flash your rom . separate
k0sh said:
try to put the pit file and flash it 1st , and then flash your rom . separate
Click to expand...
Click to collapse
I had done this before with Odin but kept having issues with the EA24 update, it would fail. I am going to try again.
Result from running P1_20100909.pit
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
Tried to run the Odin EA24 update but received error Odin3 Communicator has stopped working...ugh!!!!!!
what odin are you using ? ?
you can't update odin ? ? there is no options to file\tools etc ?
use odin 1.7
k0sh said:
what odin are you using ? ?
you can't update odin ? ? there is no options to file\tools etc ?
use odin 1.7
Click to expand...
Click to collapse
Mine says Odin3 v1.7, I believe I got it off the Sprint forum. My freaking system is all shanked up. I think I am going to delete all of the files I have downloaded and start over because nothing is working for me. I have used Odin and Heimdall to no success.
This may be the last chance to get back the needed important data (please don't ask the awkward question: why not back up the data first) .....
Tried the official SAMSUNG repair office, they said no way!!! Tried search the net and not much available either!
Any expert here can help?
Problem:
Galaxy Note 1 GT-N7000, possibly still in unrooted Ginger Bread, suddenly stuck at boot logo. Press+hold Power/Vol Up/Home brings the machine into recovery mode showing:
1. the green Android robot and yellow arrow out from a file box logo,
2. messages displayed:
<in red>
E: failed to mount /sdcard (I/O error)
E:copy_cache_media:Can’t mount /sdcard
Your storage not prepared yet, please use UI menu for format and rebootactions.
<in Red>
<in yellow>
Media files copy failed.
# MANUAL MODE #
-- Updating application …
<in yellow>
..<in red>
E: failed to mount /sdcard (I/O error)
E:copy_cache_media:Can’t mount /sdcard
Your storage not prepared yet, please use UI menu for format and rebootactions.
Copy application failed.
<in Red>
..<in yellow>
-- Applying Multi-CSC…
Installing Multi-CSC
Can’t access to ‘/system/csc/TGY/system/’.
Successfully applied Multi-CSC
<in yellow>
Then, the usual Android system recovery message <in blue> for reboot, apply update, wipe data/factory reset, wipe cache, test redbend fota displayed at the top part of the screen.
3. Tried wiping cache partition and reboot, no luck with the same situation after reboot.
4. The SAMSUNG repair office said it’s not the battery problem. All data will be gone for rebooting the machine.
The data are more important than the machine, ie, saving the data is more important than saving the machine.
Any suggestions and directions for a workable solution will be highly appreciated.
there is a possible way ... do at your on risk..
1. boot into dwonload mode and connect the phone to PC.. open odin and check if connecting fine
2. download philz kernel for for ICS/JB (tar version) and flash it using the PDA tab in odin. (This will not boot the GB rom but should give you access to CWM)
3.Once flash is completed, remove the cabe and battery.. put the battery back in and boot into recovery mode, (vol up+home+power) .. You should see CWM recovery
4. Contacts can be backuped up by doing a nandroid backup of your rom. for the data in InternalSD, go to mounts and storage and choose mount USB storage.
conect phone to pc and wait for the drivers to appear.
5. copy what ever data you need.
It is possible.
Flash CF Root Gingerbread kernel using PC Odin.
Drop into recovery and connect your phone to PC.
From ADB you'll be able to copy (backup) ANY file you need.
DO NOT perform factory reset / wipe data or you'll lose the data.
---------- Post added at 05:56 PM ---------- Previous post was at 05:54 PM ----------
Ohh yes nandroid backup too will work.
Easier way. Do a nandroid backup on recovery. Flash the same rom you were using. Advanced restore of data partition of the nandroid.
Thank you very much guys for all of your quick and valuable replies.:good::good:
Please excuse my ignorance as I’m only a dummy, actually the worst, an old dummy!!
In order not to make the suitation worse, I’d like to know/clarify the following details before proceeding to the suggested ways:
@nokiamodeln91:
1. Connected to PC with the N7000 in SAMSUNG logo display, opened Odin3 v1.85, ID:COM column shows <in yellow>0:[COM4] and Message column shows<ID:0/004>Added!!
Is download mode=press&hold [power+vol up+home] keys?
2. In the thread: http://forum.xda-developers.com/showthread.php?t=1901191
Trying to download philz-cwm6-n7000, found the following 5 tar files:
PhilZ-cwm6-XXLT5-OXX-5.03.0.tar.md5
PhilZ-cwm6-ZSLO2-OZS-5.03.0.tar.md5
PhilZ-cwm6-DDLSC-ODD-5.03.0.tar.md5
PhilZ-cwm6-DXLSE-OLB-5.03.0.tar.md5
PhilZ-cwm6-JPLSB-UAE-5.03.0.tar.md5
Which one is suitable for an UNROOTED GingerBread N7000 with csc/TGY/system?
Will try to follow the other steps after clarifying the suitable tar file.
@Boy124:
1. What is CF Root Gingerbread kernel? Where can I download a copy for an UNROOTED N7000?
2. Please elaborate on or direct me to detailed ADB procedures, preferably a step-by-step guide if not asking too much. I’ve downloaded adt-bundle-windows-x86-20130219. How to copy (backup) the contacts data?
3. Thanks for reminding not to wipe data and perform factory reset.
@projeto56 and Boy124:
Search a bit on nandroid. But how to add nandroid in the machine as it is (stuck in boot logo)?
The machine has not been flashed with any ROM since purchase. No modifications, flashing or anything, no rooting, just add apps (as said, I’m an old dummy!). When booting in recovery mode, cannot see any backup or restoring options
Hope you guys have enough patience to bear with me and answer the questions.
Thanks again.
@liway
CF Root is not necessary.
As nokiamodeln91 said flash PhilZ kernel with PC Odin - any version will do the job.
After flashing with PC Odin, drop into recovery. (home key + volume up + power)
Then back up your current ROM.
Flash Gingerbread firmware with PC Odin again.
Root it. If you have Titanium Backup Pro, you can directly restore data from a nand backup. Or restore data only after rooting your ROM.
Lemme know if you need further assistance.
liway said:
Search a bit on nandroid. But how to add nandroid in the machine as it is (stuck in boot logo)?
The machine has not been flashed with any ROM since purchase. No modifications, flashing or anything, no rooting, just add apps (as said, I’m an old dummy!). When booting in recovery mode, cannot see any backup or restoring options
Click to expand...
Click to collapse
Do this:
Boy124 said:
As nokiamodeln91 said flash PhilZ kernel with PC Odin - any version will do the job.
After flashing with PC Odin, drop into recovery. (home key + volume up + power)
Then back up your current ROM.
Click to expand...
Click to collapse
But afterwards, i recommend you to flash a JB stock ROM directly from your new recovery. And after you've set it up, you either restore your data from your nandroid, or you use titanium backup pro to restore only what you need (recommended).
Anyway, if you've set up your google account previously, probably your contacts are already saved in the cloud.
You need to connect the phone in download mode (vol down + home + power). Then volume up to continue. The screen should show downloading.
Now connect the phone to pc and use odin to flash any tar version of the kernel. (like ddlsc). Select on pda tab.
None of these kernels are suitable as it will not boot on GB. This is just for you to get into an advanced recovery to backup your data before you wipe and get your phone working.
Following the suggested procedures, set the machine in downloading mode to download PhilZ-cwm6-DDLSC-ODD-5.03.0.tar, the bar below KERNEL square in Odin becomes completely green with the Message displayed:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-DDLSC-ODD-5.03.0.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
It stayed at this stage for hours and seems stopped there.
Tried to boot it in recovery mode [vol up+home+power], this time only the boot logo with an exclamation mark (!) in yellow triangle. Odin message:
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Put back in downloading mode again, and the machine now is exactly at the same stage with the above message displayed and apparently halted at "NAND Write Start!!". The machine's screen remains in the downloading mode.
What should I do next?
Make sure kies process is not running in task manager. Use the main usb ports. Use samsung usb cable only. Reboot the phone in download mode and try again. The tar file should be in pda.
kies process is not running in task manager.
using one of the main usb ports.
Cannot locate the original samsung usb cable, using ordinary USB 2.0 cable. Will try to find the original samsung usb cable and try again later.
The tar file is in pda.
Thanks.
maybe a pciture of where file should be added in odin will help him/her. flashing kernel takes only seconds. as i can see drivers were properly installed from the descriptions above.
In Odin, I've ticked the box for PDA, then put the file with the whole path name for the folder in the column after PDA.
Tried again with
1. sure that all kies process is not running in task manager.
2. using one of the main usb ports at the back plate of a desktop PC.
3. Using an original samsung usb cable from Note 2 (should be the same as for this Note 1?),
4. The tar file is in pda, and path/location stated in the box after ticked PDA in Odin.
....
Still halted at the stage of NAND Write Start!!:crying:
did you reboot into download mode? you should not continue from a failed flash. reboot
restart the pc and run odin as admin.
disable any AV and Firewall softwares.
if still a no go then try on a different pc
Disconnected the machine. Taken away and put back the battery. Rebooted in download mode [vol dn+home+power].
Restarted the pc and run under a user with administrator right.
Disabled all norton internet security protections. Turned off modem/router connection.
Connect to Odin, still no go. Same situation, halted at NAND Write Start.
Will try to arrange another pc next day or so.
In the meantime, any other alternatives worth trying?
Even a bricked phone in download mode should be able to flash a kernel.
What you could try is unintall kies and usb drivers. And then download samsung usb drivers from developer. Samsung.com and install it again. Then try.
- deleted Kie and SAMSUNG USB driver. Restart the PC.
- reinstall samsung usb driver.
- restart in download mode and connect PC.
still no go!
to recap: using Odin3-v1.85 and PhilZ-cwm6-DDLSC-ODD-5.03.0.tar
diff PC seems to be the last option
though you could try this. download http://d-h.st/FVh. its the PIT file. Select the PIT file in PIT Tab.. and kernel in PDA tab..
make sure repartition is checked.. then flash again and see..
flash wit PIT and kernel.
In Odin, Set Partition shows up in the 1st square and message:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-DDLSC-ODD-5.03.0.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
seems halted there!
How long will I have to wait?
Hi Guys,
I have a Galaxy S3 (i9305) Rooted on Stock 4.4, Knox disabled, w Xposed. Running Philz Recovery.
Anyways, I woke Saturday morning to my phone stuck on the Samsung Boot Logo.
I tried rebooting several times to no avail, so tried a recovery via Philz. (I can get into Odin Mode / Recovery no problems)
However when I try to do a restore, it fails. When I initially boot up Philz I get this;
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
And when I try to wipe caches / system etc I get an error message;
E: format_volume: make_ext4fs failed on /dev/block/mmcblk0p12
Tried flashing stock FW via Odin and that fails.
So not sure what I can do? From my research it looks like the eMMC (internal SD) has croaked, but how can I be
absolutely sure? Has anyone had a similar situation and been able to recover?
Thanks in Advance!
BrikHaus said:
Hi Guys,
I have a Galaxy S3 (i9305) Rooted on Stock 4.4, Knox disabled, w Xposed. Running Philz Recovery.
Anyways, I woke Saturday morning to my phone stuck on the Samsung Boot Logo.
I tried rebooting several times to no avail, so tried a recovery via Philz. (I can get into Odin Mode / Recovery no problems)
However when I try to do a restore, it fails. When I initially boot up Philz I get this;
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
And when I try to wipe caches / system etc I get an error message;
(will enter exact info when an home and can see phone)
Can't format /system/ doesn't exist?
Tried flashing stock FW via Odin and that fails.
So not sure what I can do? From my research it looks like the eMMC (internal SD) has croaked, but how can I be
absolutely sure? Has anyone had a similar situation and been able to recover?
Thanks in Advance!
Click to expand...
Click to collapse
Try TWRP.
Flash: http://d-h.st/users/psndna88/?fld_id=34039#files (all files). But attention, when you format 'data' partition, you lost all files from internal (you can skip format data, or if you not have important files, format)
After this, flash a new rom with Odin (or if you have custom rom, flash again)
il3gal said:
Try TWRP.
Flash: http://d-h.st/users/psndna88/?fld_id=34039#files (all files). But attention, when you format 'data' partition, you lost all files from internal (you can skip format data, or if you not have important files, format)
After this, flash a new rom with Odin (or if you have custom rom, flash again)
Click to expand...
Click to collapse
Thanks il3gal.
When I try to flash TWRP (Which I had before I installed Philz) I get the following from Odin;
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can you provide a bit more info about how I flash those 4 files? If I can?
BrikHaus said:
Thanks il3gal.
When I try to flash TWRP (Which I had before I installed Philz) I get the following from Odin;
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can you provide a bit more info about how I flash those 4 files? If I can?
Click to expand...
Click to collapse
This 4 files is for format your partition in ext4. (if you try to modify partitions with f2fs or others)
Try 2/3 times with Odin and TWRP. If not work, download stock rom from http://www.sammobile.com/firmwares/database/GT-I9305/ and install with Odin
What Odin are you use to flash TWRP? Reinstall usb drivers or change usb port
il3gal said:
This 4 files is for format your partition in ext4. (if you try to modify partitions with f2fs or others)
Try 2/3 times with Odin and TWRP. If not work, download stock rom from http://www.sammobile.com/firmwares/database/GT-I9305/ and install with Odin
What Odin are you use to flash TWRP? Reinstall usb drivers or change usb port
Click to expand...
Click to collapse
Do you use Odin to flash those 4 files? If so what are they 'AP'?
I've tried to flash on 2 different computers using (5) different cables. Still no luck at all..
Using Odin 3.10.6
I think I'm screwed..
BrikHaus said:
Do you use Odin to flash those 4 files? If so what are they 'AP'?
I've tried to flash on 2 different computers using (5) different cables. Still no luck at all..
Using Odin 3.10.6
I think I'm screwed..
Click to expand...
Click to collapse
For .zip files you need flash with recovery (cwm/twrp/philz)...but if you try with Odin and is not work..i dont now if my method is work for you..
download odin 3.09.....i tried odin 3.10 and it did not recognized my phone and download the usb drivers from the recovery thread on the developing section.
http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
Thanks il3gal, tried to flash those zips and get an error message;
E: Failed to setup expected mounts for install; Aborting
hexisg said:
download odin 3.09.....i tried odin 3.10 and it did not recognized my phone and download the usb drivers from the recovery thread on the developing section.
http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
Click to expand...
Click to collapse
Thanks hexisg. Tried 3.09 and same issue. No Luck.
Greetings! I've managed to brick my Samsung S2 T817 (5.1.1). I'm stuck in one of two bootloops.
1) Your device didn't update successfully use the Verizon Software Repair Assistant...
2) ODIN Mode
Download Speed: FAST
Product Name: SM-T817V
Current Binary: Samsung Official
Downloading....
Short story, I (foolishly) tried to root using ODIN an a T810.tar and I bricked the device. Can someone send me a URL for the Verizon Assistant Recovery software OR provide steps direction on how to un-brick my device? Any help you can provide would be awesome!
Just flash the stock Firmware with Odin.
http://easy-firmware.com/index.php?a=browse&b=category&id=6552
Thanks for the help Ashyx but when I download/extract the MD5 file I cannot flash the package.
I was sure to run Odin as Admin. My tablet displays the following:
SW REV. CHECK FAIL. DEVICE: 2. BINARY: 1
Odin Odin presents the following error:
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> param.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any idea what I'm missing? Thanks for the help!
Try flashing just the recovery. Convert it to a tar archive first.
Still Bricked
ashyx said:
Try flashing just the recovery. Convert it to a tar archive first.
Click to expand...
Click to collapse
Thanks for the tip but no luck. I used 7-zip to create a tar file. I can load this to Odin3 but as soon as I select Start the program crashes. Uggh. Is it possible to get the Verizon Software Repair tool?
Thanks!
NewYork2Cali said:
Thanks for the tip but no luck. I used 7-zip to create a tar file. I can load this to Odin3 but as soon as I select Start the program crashes. Uggh. Is it possible to get the Verizon Software Repair tool?
Thanks!
Click to expand...
Click to collapse
It shouldn't crash, how did you create it and which version of 7zip?
I used 7 zip 64 bit for Win 10.
I successfully created the tar file from the (MD5 file) located in the T817VVRU1AOG9_T817VVZW1AOG9_5.1.1_USA_Verizon_ALL.zip file. Odin3 crashes as soon as I select Start. Thanks!
NewYork2Cali said:
I used 7 zip 64 bit for Win 10.
I successfully created the tar file from the (MD5 file) located in the T817VVRU1AOG9_T817VVZW1AOG9_5.1.1_USA_Verizon_ALL.zip file. Odin3 crashes as soon as I select Start. Thanks!
Click to expand...
Click to collapse
You need to pull the recovery.img out of the md5 and tar that up not the md5 itself.
I believe I did that. I extracted the zip and pulled out this file
ALL_VZW_T817VVRU1AOG9_T817VVZW1AOG9_CL5500403_QB5862896_REV02_user_low_ship.tar.md5
I used 7 zip to create this file
ALL_VZW_T817VVRU1AOG9_T817VVZW1AOG9_CL5500403_QB5862896_REV02_user_low_ship.tar
I loaded the tar file to Odin and it crashed. Am I missing a step? Thanks!
NewYork2Cali said:
I believe I did that. I extracted the zip and pulled out this file
ALL_VZW_T817VVRU1AOG9_T817VVZW1AOG9_CL5500403_QB5862896_REV02_user_low_ship.tar.md5
I used 7 zip to create this file
ALL_VZW_T817VVRU1AOG9_T817VVZW1AOG9_CL5500403_QB5862896_REV02_user_low_ship.tar
I loaded the tar file to Odin and it crashed. Am I missing a step? Thanks!
Click to expand...
Click to collapse
You're not paying attention.
You need the file called RECOVERY.IMG that is inside the tar.md5.
Right click the md5, select open archive in 7zip.
Pull the recovery.img out then using 7-zip right click it, select create archive. Select TAR and STORE as the only options. Flash with Odin.
Will flashing this have any negative affects on Knox or void my warranty? Id like to try and reset my tablet back to a new setup beyond what a factory reset does.
{
"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"
}
Code:
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
FEATURES
MTP and ADB support
EXT4 support
F2FS support
EXFAT support
KNOWN ISSUES
Data decryption unsupported
adb sideload does not work
DOWNLOAD
Not available anymore
Contributors
Linux4
Source Code: https://github.com/TeamWin
FAQ
How to boot into Download mode
Turn off the tablet
Press and hold volume down and volume up
Connect the tablet to a computer via USB cable
How to boot in recovery mode
Turn off the tablet
Press and hold volume up and power until bootloader logo appears
How to flash TWRP
Unlock the tablet's bootloader
Backup all your data as unlocking will factory reset your tablet!
Enable developer options and enable OEM unlock option there
Boot into download mode (you have to do it like described above, with adb reboot download the unlock option won't be available!)
Long press volume up to unlock your device
Go through initial setup again after unlock. You must connect to WiFi but can skip everything else.
Confirm that bootloader is actually unlocked (OEM unlock option grayed out and telling you it's already unlocked in developer options)
Boot into download mode
Flash twrp.img.tar (or twrp.img if you use heimdall) from TWRP download page using Odin/Heimdall.
CHANGELOG
2020-11-02
Fix mounting and naming of usb-otg and external_sd
2020-11-01
Fix mounting issues present in latest TWRP build (also fixes settings not saving/loading)
2020-10-29
Sync kernel source with lineage (fixes screen bugs when booting up on newer firmware)
2020-09-23
Initial release
Reserved
Linux4 said:
FAQ
How to flash twrp
Unlock the tablet's bootloader
Flash disabled vbmeta images (only required if you're not going to flash my LineageOS)
Boot into download mode
Flash recovery.img using Odin or Heimdall
Click to expand...
Click to collapse
Thanks for making this possible.
I assume you have to rename the twrp.img to recovery.tar using 7zip, and flash it with the AP option in Odin, right?
Flashing failed, i get this log in Odin:
<ID:0/008> Added!!
<ID:0/008> Odin engine v(ID:3.1401)..
<ID:0/008> File analysis..
<ID:0/008> Total Binary size: 67 M
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> twrp-3.4.0-0-gta4xlwifi.img
<ID:0/008> Unassigned file
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Iceman66 said:
Thanks for making this possible.
I assume you have to rename the twrp.img to recovery.tar using 7zip, and flash it with the AP option in Odin, right?
Flashing failed, i get this log in Odin:
<ID:0/008> Added!!
<ID:0/008> Odin engine v(ID:3.1401)..
<ID:0/008> File analysis..
<ID:0/008> Total Binary size: 67 M
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> twrp-3.4.0-0-gta4xlwifi.img
<ID:0/008> Unassigned file
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You have to rename the twrp.img to recovery.img and add it to a .tar archive using e.g 7zip, I'll also add that to the FAQ
Thx, working now.
Has anyone verified MTP actually working with this build?
Yes MTP works very well for me
So do change the name form twrp.img to recovery.img then using 7zip press add to archive and use .tar format, then flash using odin on the ap section
mu1989 said:
Yes MTP works very well for me
Click to expand...
Click to collapse
Just to be totally clear, you mean in TWRP, not Lineage itself, correct?
ianmacd said:
Just to be totally clear, you mean in TWRP, not Lineage itself, correct?
Click to expand...
Click to collapse
Yes, I mean that. It works in twrp as well as in lineage OS
Has anyone gotten this working in an August or later revision of the stock firmware (v2 in place of v1 binary)? I get the blurred screen upon entry into TWRP. Don't know if it's flashing custom ROMs correctly, either. I rather doubt it.
@Linux4, are you planning to add support for data encryption in future releases?
tejasjadhav said:
@Linux4, are you planning to add support for data encryption in future releases?
Click to expand...
Click to collapse
I'd like to add that (though only for AOSP FBE, not Samsung's encryption on stock) and already experimented a bit with it but it's still not working correctly.
So I got it installed by following the more detailed step by step process. I lost the ability to play Netflix and Prime but I was expecting that.
First question, while doing a backup I am not able to backup the partition data, is this normal?
Second, TWRP is not retaining the settings that I change, did I do something wrong while installing?
Did you use twrp to install lineage or just to flash magisk?
Twrp doesn't really get along with the super partition.
If you want to use netflix you have to but magisk liboemcrypto modul
mu1989 said:
Did you use twrp to install lineage or just to flash magisk?
Twrp doesn't really get along with the super partition.
If you want to use netflix you have to but magisk liboemcrypto modul
Click to expand...
Click to collapse
Just installed magisk as part of the unlocking guide, have used los for a long time but just
didnt feel like messing with it now, is there a flashable file for magisk for the tab s6 lite?
In the Lineage forum we had already discussed the topic
i have issue flashing the twrp img
i have confirmed that the OEM unlock is present under developer options, and i get the unlocked bootloader prompt
so my changelog is this under Odin 3.1.3
<ID:0/009> Added!!
<ID:0/009> Odin engine v(ID:3.1301)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 67 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> NAND Write Start!!
<ID:0/009> SingleDownload.
<ID:0/009> recovery.img
<ID:0/009> RQT_CLOSE !!
<ID:0/009> RES OK !!
<ID:0/009> Removed!!
<ID:0/009> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
but when i press Vol Up + Power, the recovery boots into the Samsung default. did i miss something?