Related
Hi Folks.
Ok here is my situation, I have a rooted and unlocked TF700.
I flashed Zeus 4 and all worked well, then flashed (after full wipe) PARANOIDANDROID 2.15 and again everything was great,
Yesterday I flashed Baked Bean 4 (again after a full wipe) and apart from some SD issues all seemed ok,
I then decided to restore my TWRP backup of Zeus as I needed to use my 64gig msd card.
After a full wipe and restore Zeus started up but the dpi was messed up (160) I think (way small)
I was seeing loads of FC's and file manager showed my internal SD as being empty. Rebooted to recovery and tried the "Format Data" option
It failed right away with this message "E: Unable to format data."
I have tried flashing the stock .26 rom via TWRP and I have the same issue, dpi set to 160 and internal sd not mounted.
It seems my Internal sd is corrupt
What is the procedure to reformat it via ADB or fastboot? (I have searched but the results I found relate to other devices and I dont want to simply follow instructions that might cause further harm to my TF700)
I have followed the NVflash brick proof procedure and have all relevant files backed up (I did this before flashing the last 2 roms)
Please can some one point me in the right direction
Thanks a lot
Jules
I always wipe cache, system, internal, davic and then do a factory reset.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right? What rom you have on your device right now?
Pretoriano80 said:
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right. What rom you have on your device right now?
Click to expand...
Click to collapse
Yip extracted the zip from the zip file and copied it to my ext sd and flashed it via TWRP
I have an unusable Zeus4,
Im about to try a full wipe again and then flash .26 again
EDIT
After flashing .26 and selecting reboot I get the "No OS installed! Are you sure you wish to reboot?" message
Looks like the system partition is corrupted, but i'm not sure. I think you should come here on IRC and maybe someone with more experience will help you - - http://webchat.freenode.net/?channels=asus-transformer
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
ZaJules said:
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
Click to expand...
Click to collapse
This same thing happened to me with my Prime when I was getting ready to send it off for RMA because of a broken HDMI port. Since I was unlocked I was advised to restore to stock before sending it in. However, before I got the chance to do that I started getting the "E: Unable to format data." error that you were. I ended up erasing all partitions from fastboot and putting a note in the box that it wouldn't boot after an OTA. I managed to get away with it and wasn't charged for fixing it
For future reference it would be really helpful to know how you fixed this. Did you do something like what is in this thread: http://forum.xda-developers.com/showthread.php?t=1803343.
Did you ever figure out how CM10 messed up your Infinity? I was running CM9 on my Prime when I got this error. Thanks!
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Pretoriano80 said:
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Click to expand...
Click to collapse
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
paddycr said:
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
Click to expand...
Click to collapse
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Pretoriano80 said:
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Click to expand...
Click to collapse
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
okantomi said:
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
Click to expand...
Click to collapse
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Pretoriano80 said:
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Click to expand...
Click to collapse
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
okantomi said:
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
Click to expand...
Click to collapse
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Pretoriano80 said:
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Click to expand...
Click to collapse
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
okantomi said:
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
Click to expand...
Click to collapse
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Pretoriano80 said:
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Click to expand...
Click to collapse
I'm using TWRP 2.2.2.1, I back up boot, system and data only, and I don't use compression.
I tried to install a new rom so i back uped my phone first and I double checked to see if it was recovered and it was so I did a full wipe on aroma installer and i didn't like the rom so i went to restore and my backup wasnt there!!!!! PLEASE HELP!!!!!!
(Note:I was originally on miui and tried to switch to viperoneS)
itsKenneh said:
I tried to install a new rom so i back uped my phone first and I double checked to see if it was recovered and it was so I did a full wipe on aroma installer and i didn't like the rom so i went to restore and my backup wasnt there!!!!! PLEASE HELP!!!!!!
(Note:I was originally on miui and tried to switch to viperoneS)
Click to expand...
Click to collapse
I have to ask but have you mounted the sdcard and checked on a PC if the file is there to verify? If you have/do and it's not there then as you have rebooted trying to recover files will be very hard to do and even then to get it back clean would be a mini miracle.
shadowch31 said:
I have to ask but have you mounted the sdcard and checked on a PC if the file is there to verify? If you have/do and it's not there then as you have rebooted trying to recover files will be very hard to do and even then to get it back clean would be a mini miracle.
Click to expand...
Click to collapse
I had a similar issue. In case the SD card gets locked while getting a ROM to work, how will i access my backup? Is there no way to force mount the sd card partition using adb somehow?
Hey, I use a GT-n8010 tablet, and I wanted to flash the HyperDrive ROM. So I went ahead, and did all the necessary things only to find that AROMA installer froze every single time, trust me when I say I tried over 10 times. So then I tried to mount my internal SD to try out another ROM, only to find that CWM doesn't mount my internal SD to my PC. Then, I tried copying it over to an external SD and then chucking it into my tablet, but CWM is not able to read my external SD card. I had wiped all my data and cache and dalvik cache. But then accidentally, I formatted my internal SD as well, so I don't have the ROM file on it.
Now, I tried to flash TWRP using download mode, but then it says USB debugging has not been enabled. I'm not able to go back to my stock ROM since I wiped all my data, I'm not able to flash back my nandroid since it's in my computer and I can't transfer it over to my tablet. I can't flash a new ROM since none of the SD cards are mountable.
Some help would greatly be appreciated! Please help out a noob here, I don't have any idea as to what I should do next.
Thank you so much
No one? Someone please help me out! I'm completely lost!
Rules say dont bump.
Suggest you flash a stock rom via Odin and get your phone working .
JJEgan said:
Rules say dont bump.
Suggest you flash a stock rom via Odin and get your phone working .
Click to expand...
Click to collapse
I did do that, but for some reason, it's stuck in the Samsung logo. And I tried resetting from stock recovery, but still got the same result.
I think you should flash stock with odin or flash a different recovery. I think it is called high on android.
http://forum.xda-developers.com/showthread.php?t=1831173
Sent from my SGH-T889 using XDA Premium App
Hello!
I am sorry if this is the incorrect place to post, but I have a very annoying issue with my OnePlus One!
A few days ago I took the OTA update from Android 4.4.4 all the way to 5.1.1. However, there are quite a few bugs with this version, and the "Material UI" is seriously getting on my nerves so I would like to revert back to my previous version. This should be doable because I performed a Nandroid backup with TWRP before updating the phone. My backup is saved on a USB stick which I connect to the phone via a USB OTG cable, which is perfectly mountable in the Recovery.
My phone is rooted and WAS running TWRP Recovery before I upgraded to Lollipop, this replaced TWRP with Cyanogens stock. When I re-rooted my phone I had to reinstall a custom recovery. For some reason, ADB installing TWRP was just not working (No errors, it just didnt install no matter what) so I opted to try a CWM recovery which did the trick.
Now my issue is that my recovery is unable to mount /sdcard which prevents it from performing backups or restores.
I could really use some help here.
Did you update your backup (TWRP?) as well? What version of it are you on?
JeffDC said:
Did you update your backup (TWRP?) as well? What version of it are you on?
Click to expand...
Click to collapse
I am not sure what you mean by updating the backup. The backup is backed up and left in the state it was when I took it, that is to say Android 4.4.4 and the version of TWRP (The date I installed TWRP the first time) is mid February 2015.
The phones recovery right now is PhilzRecovery which as far as I understand is CWM. Latest version.
Try installing twrp from the CWM recovery.. And before restoring the phone from nandroid try installing the clean stock rom at 4.4.4 and then do the nandroid restore.
Sent from OPO using Tapatalk
Press on thanks if I helped you
ashuthosh.heda said:
Try installing twrp from the CWM recovery.. And before restoring the phone from nandroid try installing the clean stock rom at 4.4.4 and then do the nandroid restore.
Sent from OPO using Tapatalk
Press on thanks if I helped you
Click to expand...
Click to collapse
And to do this, I would just drop the .img for TWRP into my phones storage and chose it from inside the recovery? Would this really work? It might be my inexperience, but it sounds somewhat risky.
NodCom said:
And to do this, I would just drop the .img for TWRP into my phones storage and chose it from inside the recovery? Would this really work? It might be my inexperience, but it sounds somewhat risky.
Click to expand...
Click to collapse
Don't know if CWM recovery supports installing img. Twrp supports img flashing. Check the features of CWM recovery and proceed.
Sent from my A0001 using Tapatalk
ashuthosh.heda said:
Don't know if CWM recovery supports installing img. Twrp supports img flashing. Check the features of CWM recovery and proceed.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Well... I am not sure how I just managed this, but I was tinkering about inside my TWRP application and tried the "Install TWRP recovery" setting a second time (I tried it before making this thread, the first time it failed), it actually was successful because it booted into TWRP. From here I selected the TWRP-backup I kept and it installed it successfully (With one note, that it during the installation said something among the lines of "Restoring backup without deleting /data/media" or something like that. The phone rebooted itself after it finished updating, and the old Cyanogen/OPO bootanimation plays. But at login (My device is encrypted since long) it tells me my password is incorrect?!
How could this to happen? I've only ever used a single password (numbers only) for my phone encryption. This is very odd.
NodCom said:
Well... I am not sure how I just managed this, but I was tinkering about inside my TWRP application and tried the "Install TWRP recovery" setting a second time (I tried it before making this thread, the first time it failed), it actually was successful because it booted into TWRP. From here I selected the TWRP-backup I kept and it installed it successfully (With one note, that it during the installation said something among the lines of "Restoring backup without deleting /data/media" or something like that. The phone rebooted itself after it finished updating, and the old Cyanogen/OPO bootanimation plays. But at login (My device is encrypted since long) it tells me my password is incorrect?!
How could this to happen? I've only ever used a single password (numbers only) for my phone encryption. This is very odd.
Click to expand...
Click to collapse
I guess it's a side effect of restoring up a backup of 4.4.4 on lollipop. Try factory reset from twrp and then flash the backup. I would still suggest to first install the stock firmware of 4.4.4 and flash it and then do a restore of 4.4.4.
Sent from OPO using Tapatalk
Currently on Resurrection Remix
Thank me if I helped you.
Also make sure you are using the most recent version of TWRP, as it provides better 'outs' and reliability for newer OP OS versions.
Good evening, I saw some questions similar to this one in the forum, but none had my kind of doubt.
When a new ROM comes out for both S7 and S8, I install via ODIN using the CSC HOME option, so as not to lose the data.
The problem is in the installation of TWRP whenever I install the same by ODIN, when entering the app and trying to install example no-verity ja start I get the message that the DATA folder has been corrupted and can not be mounted.
This way it only works once again doing WIPE DATA, but then I lose my data and I have to start from scratch.
Is there a way this does not happen or will it always be like this when updating a ROM?
Thank you.
costafabiof said:
Good evening, I saw some questions similar to this one in the forum, but none had my kind of doubt.
When a new ROM comes out for both S7 and S8, I install via ODIN using the CSC HOME option, so as not to lose the data.
The problem is in the installation of TWRP whenever I install the same by ODIN, when entering the app and trying to install example no-verity ja start I get the message that the DATA folder has been corrupted and can not be mounted.
This way it only works once again doing WIPE DATA, but then I lose my data and I have to start from scratch.
Is there a way this does not happen or will it always be like this when updating a ROM?
Thank you.
Click to expand...
Click to collapse
Have you tried backing up data with twrp before you wipe and copying it to your pc so you can do a full wipe then put the backup onto the phone and flash It? You can back up data folder only
godkingofcanada said:
Have you tried backing up data with twrp before you wipe and copying it to your pc so you can do a full wipe then put the backup onto the phone and flash It? You can back up data folder only
Click to expand...
Click to collapse
Good afternoon,
Thanks for the reply.
So from what I mentioned above, I do a full backup as I normally do, and I also do a separate from the DATA folder.
Then I install the ROM and TWRP, will it corrupt the DATA folder so I restore only it? Would it be this?
If so, will it work out, in relation to being a ROM different from the other?
costafabiof said:
Good afternoon,
Thanks for the reply.
So from what I mentioned above, I do a full backup as I normally do, and I also do a separate from the DATA folder.
Then I install the ROM and TWRP, will it corrupt the DATA folder so I restore only it? Would it be this?
If so, will it work out, in relation to being a ROM different from the other?
Click to expand...
Click to collapse
The main rom info needed is contained in the system folder. The data folder is application data and whatnot. Reboot into twrp and use the backup option, then copy to pc. Do a full wipe of all, pit backup of data folder and new rom on internal or sd. Go into terp and flash the rom and data folder. Do not flaah system or it will overwrite the new rom. u will restore everything even if you don't have the APK installed in your system. It will return the data, you may need to reinstall the APK. Gmail for example will return will email addresses and messages, contacts and texts will come back to what they were at backup. You should back up modem and efs and boot as well and keep them safe. What I do is I get my phone set up fully, all apps I need and any games and data and then back it up again so any issues and I restore it to a fully functional state and don't need to install tons of things
godkingofcanada said:
The main rom info needed is contained in the system folder. The data folder is application data and whatnot. Reboot into twrp and use the backup option, then copy to pc. Do a full wipe of all, pit backup of data folder and new rom on internal or sd. Go into terp and flash the rom and data folder. Do not flaah system or it will overwrite the new rom. u will restore everything even if you don't have the APK installed in your system. It will return the data, you may need to reinstall the APK. Gmail for example will return will email addresses and messages, contacts and texts will come back to what they were at backup. You should back up modem and efs and boot as well and keep them safe. What I do is I get my phone set up fully, all apps I need and any games and data and then back it up again so any issues and I restore it to a fully functional state and don't need to install tons of things
Click to expand...
Click to collapse
Good afternoon,
I'm sorry for the text I'm using Google Translate.
I believe that I did not understand correctly, because the error happens in the following way, I install a ROM, reinstall the TWRP, yes yes it corrupts the folder DATA!
If I understood mistake, I apologize.
costafabiof said:
Good afternoon,
I'm sorry for the text I'm using Google Translate.
I believe that I did not understand correctly, because the error happens in the following way, I install a ROM, reinstall the TWRP, yes yes it corrupts the folder DATA!
If I understood mistake, I apologize.
Click to expand...
Click to collapse
Is it a custom Rom or a stock rom? Also you can backup via ADB
https://forum.xda-developers.com/an...oid-sdk-adb-backup-apps-t3467560#edit68829721
godkingofcanada said:
Is it a custom Rom or a stock rom? Also you can backup via ADB
https://forum.xda-developers.com/an...oid-sdk-adb-backup-apps-t3467560#edit68829721
Click to expand...
Click to collapse
The ROM I use is provided by Samsung, with no modifications, when I install it I use the CSC option the HOME file, in order not to lose the data, and of course, I do not lose anything I only update the ROM.
The problem is that I need to reinstall TWRP after installing ROM, and when I access TWRP it has corrupted the DATA folder.
costafabiof said:
The ROM I use is provided by Samsung, with no modifications, when I install it I use the CSC option the HOME file, in order not to lose the data, and of course, I do not lose anything I only update the ROM.
The problem is that I need to reinstall TWRP after installing ROM, and when I access TWRP it has corrupted the DATA folder.
Click to expand...
Click to collapse
You can extract the samsung md5 and repack it as a zip with superrs kitchen and then flash it from twrp. Just remove the recovery.img from the extracted files before zipping it up. Then you can simply flash twrp. Then the rom and not have to worry about the fact that you are stuck in a loop of being locked out because you don't need odin for the rom and it won't overwrite your recovery. If that's too much work try using a custom Rom from xda
godkingofcanada said:
You can extract the samsung md5 and repack it as a zip with superrs kitchen and then flash it from twrp. Just remove the recovery.img from the extracted files before zipping it up. Then you can simply flash twrp. Then the rom and not have to worry about the fact that you are stuck in a loop of being locked out because you don't need odin for the rom and it won't overwrite your recovery. If that's too much work try using a custom Rom from xda
Click to expand...
Click to collapse
Thank you very much for your patience. But I'm not clear, or you do not understand.
The problem is not in the ROM, but in the TWRP installation. If I install the ROM with the option CSC HOME I do not lose anything, everything is working correctly.
When I install TWRP it corrupts the DATA folder. The problem is there!
costafabiof said:
Thank you very much for your patience. But I'm not clear, or you do not understand.
The problem is not in the ROM, but in the TWRP installation. If I install the ROM with the option CSC HOME I do not lose anything, everything is working correctly.
When I install TWRP it corrupts the DATA folder. The problem is there!
Click to expand...
Click to collapse
I was saying to use a zip rom because then you can reflash the rom without reflashing twrp. So you flash twrp, it says data error and then you flash rom from zip, which reinstall system and data but will not copy stock recovery over twrp. So you will not have to reinstall it and be stuck. Or try a different version of twrp might also help. Stock firmware overwrites recovery and the rom. You need to modify it to remove recovery from the firmware, or use a custom Rom to stop it from erasing twrp
godkingofcanada said:
I was saying to use a zip rom because then you can reflash the rom without reflashing twrp. So you flash twrp, it says data error and then you flash rom from zip, which reinstall system and data but will not copy stock recovery over twrp. So you will not have to reinstall it and be stuck. Or try a different version of twrp might also help. Stock firmware overwrites recovery and the rom. You need to modify it to remove recovery from the firmware, or use a custom Rom to stop it from erasing twrp
Click to expand...
Click to collapse
I think I understood, more or less, since I translate for Google.
But assuming I want to use normal ROM, you have to back up the DATA folder before installing the ROM and after installing the new ROM and TWRP, restore only the DATA?
Thank you again.
Yes a new rom will overwrite data, you need a backup before. You should be able to connect your phone to a linux operating system and use adb to connect and back it up, if twrp will not let you take a back up.
godkingofcanada said:
Yes a new rom will overwrite data, you need a backup before. You should be able to connect your phone to a linux operating system and use adb to connect and back it up, if twrp will not let you take a back up.
Click to expand...
Click to collapse
In my case I can back up the DATA folder by TWRP. Is there doubt, if I back up the DATA folder in one version of Android and then restore in another version, will it be compatible?
costafabiof said:
In my case I can back up the DATA folder by TWRP. Is there doubt, if I back up the DATA folder in one version of Android and then restore in another version, will it be compatible?
Click to expand...
Click to collapse
Yes it will be, marshmallow and nougat are completely compatible from the boot loader up. You can also turn your stock samsung md5 into a zip file so you do not need odin to install it. You will be able to flash it from twrp
godkingofcanada said:
Yes it will be, marshmallow and nougat are completely compatible from the boot loader up. You can also turn your stock samsung md5 into a zip file so you do not need odin to install it. You will be able to flash it from twrp
Click to expand...
Click to collapse
Again thank you very much.
I'll test it and put it here.
Note: The Thank you button is not working.
costafabiof said:
Again thank you very much.
I'll test it and put it here.
Note: The Thank you button is not working.
Click to expand...
Click to collapse
You are welcome. If you want to have a stock zip file instead of the md5 use this link.
https://forum.xda-developers.com/showthread.php?t=2387941
...
costafabiof said:
...
Click to expand...
Click to collapse
Can you not read the website?
I know what you mean. Twrp can't access the data folder because it's encrypted. But you do have to format it to gain proper access. You have to copy the files out or back them up
godkingofcanada said:
Can you not read the website?
Click to expand...
Click to collapse
I believe that because I am a new user I can not exclude publications, I already tested in CHROME and IE. In the same way I can not give THANK YOU.