I have the S7270, I try to flash my device using the default firmware "S7270XXUANA2_S7270OLBANA2_S7270XXUANA2_HOME.tar" using Odin, but my device still can not be used and still bootlop. when entering cwm appear warning "did not match size '/system/csc/common/system/csc/others.xml". then when i use menu wipe cache, appear warning "error".
I do not understand why this happened, because I was given these devices by my friend. does anyone know a solution?
bfalcon said:
I have the S7270, I try to flash my device using the default firmware "S7270XXUANA2_S7270OLBANA2_S7270XXUANA2_HOME.tar" using Odin, but my device still can not be used and still bootlop. when entering cwm appear warning "did not match size '/system/csc/common/system/csc/others.xml". then when i use menu wipe cache, appear warning "error".
I do not understand why this happened, because I was given these devices by my friend. does anyone know a solution?
Click to expand...
Click to collapse
Have exactly the same problem with a S7270L, it seems to be a hardware problem rather than a software problem from what I've read. And I haven't found a solution yet, but if I do, I'll let you know!.
Related
Hi, I am new to this, but I am learning fast. I have a RCA tablet (rct6378w2) that will not boot. It powers on, but hangs on the RCA splashscreen. I am able to access the recovery system. Wiping the cache and factory reset doesnt seem to fix the problem. Because the tablet powers on and the screen works okay, I feel like there is still hope for the device. I was wondering if someone could list all of the common reasons why a tablet will power on, but not boot into android. Extra credit if you can tell me which possible problems are fixable and which ones are not. Thanks!
jeremyb234 said:
Hi, I am new to this, but I am learning fast. I have a RCA tablet (rct6378w2) that will not boot. It powers on, but hangs on the RCA splashscreen. I am able to access the recovery system. Wiping the cache and factory reset doesnt seem to fix the problem. Because the tablet powers on and the screen works okay, I feel like there is still hope for the device. I was wondering if someone could list all of the common reasons why a tablet will power on, but not boot into android. Extra credit if you can tell me which possible problems are fixable and which ones are not. Thanks!
Click to expand...
Click to collapse
1. ROM is wrong for the tablet
2. Tablet has no ROM installed
These are the issues possible for you as you say you wiped and factory reset the tablet but did you re-install the ROM afterwards ?
TechMinerUK said:
1. ROM is wrong for the tablet
2. Tablet has no ROM installed
These are the issues possible for you as you say you wiped and factory reset the tablet but did you re-install the ROM afterwards ?
Click to expand...
Click to collapse
Thanks for the response. Well, to give clarity as to when the problem began, this is what happened. I was doing normal things on my tablet, and it seemed to lag really bad. As I tried to press the home button once or twice, I saw some strange lines on the screen as it faded (kind of like when a battery dies). Then the device restarted and hung on boot. After rebooting a few times, I then tried to wipe the cache with no success. After this, I did the factory reset. I know that it cannot be the wrong ROM, but I wonder if somehow the files were corrupted or if the storage unit could have failed. Anyways, according to various instructions I have seen online, I thought that doing the factory reset would restore the original factory rom image? Am I incorrect?
jeremyb234 said:
Thanks for the response. Well, to give clarity as to when the problem began, this is what happened. I was doing normal things on my tablet, and it seemed to lag really bad. As I tried to press the home button once or twice, I saw some strange lines on the screen as it faded (kind of like when a battery dies). Then the device restarted and hung on boot. After rebooting a few times, I then tried to wipe the cache with no success. After this, I did the factory reset. I know that it cannot be the wrong ROM, but I wonder if somehow the files were corrupted or if the storage unit could have failed. Anyways, according to various instructions I have seen online, I thought that doing the factory reset would restore the original factory rom image? Am I incorrect?
Click to expand...
Click to collapse
Depends, if it's a custom recovery it could wipe everything
TechMinerUK said:
Depends, if it's a custom recovery it could wipe everything
Click to expand...
Click to collapse
Thanks for the response. I have only used the regular stock recovery that is preloaded on the device (I think it's called Android System Recovery 3e. To my knowledge, I don't believe there are any working custom recoveries for this device. It seems that doing the factory reset is normally the way to go to fix OS issues on this device. However, when the factory reset process is successful (as far as going through the process is concerned), but it does not fix the issue, it makes me wonder if the factory recovery image is corrupt or something. Any ideas? Also, if the device turns on and I can navigate through the recovery options and even use ADB, do you think the hardware is still good? If so, then it would be a software/firmware problem... right?
I would simply like to get the device working. I don't care whether its a stock recovery or custom recovery, stock rom or custom Rom. I just want to use the device again and not have to throw it in the garbage. Do you have any ideas how I can get it going?
One other thing, I just don't understand why it's so difficult to restore a tablet. A PC is ultra easy to fix by using a self-booting recovery disk or a live linux iso. Perhaps someone can explain to me why it seems to be impossible to find a working rom anywhere for this device.
jeremyb234 said:
Thanks for the response. I have only used the regular stock recovery that is preloaded on the device (I think it's called Android System Recovery 3e. To my knowledge, I don't believe there are any working custom recoveries for this device. It seems that doing the factory reset is normally the way to go to fix OS issues on this device. However, when the factory reset process is successful (as far as going through the process is concerned), but it does not fix the issue, it makes me wonder if the factory recovery image is corrupt or something. Any ideas? Also, if the device turns on and I can navigate through the recovery options and even use ADB, do you think the hardware is still good? If so, then it would be a software/firmware problem... right?
I would simply like to get the device working. I don't care whether its a stock recovery or custom recovery, stock rom or custom Rom. I just want to use the device again and not have to throw it in the garbage. Do you have any ideas how I can get it going?
One other thing, I just don't understand why it's so difficult to restore a tablet. A PC is ultra easy to fix by using a self-booting recovery disk or a live linux iso. Perhaps someone can explain to me why it seems to be impossible to find a working rom anywhere for this device.
Click to expand...
Click to collapse
Unfortunatley because it's not a common brand of tablet not many developers are working on creating ROMs for it
Hello. So yeaah, i installed twrp to my phone and tried to install custom rom to my SM-930F. installed custom rom rebooted my phone and when it boots it says confirmation failed or something and has only one option is to factory reset my phone. i press that button and nothing happens, my phone reboots and same screen is back. i could restore it with kies, but i dont know my serial number, and on my box there is none written. how to fix my problem? or atleast is it possible to get my serial number using twrp terminal or something? thank you for your answers
Aironasioo said:
Hello. So yeaah, i installed twrp to my phone and tried to install custom rom to my SM-930F. installed custom rom rebooted my phone and when it boots it says confirmation failed or something and has only one option is to factory reset my phone. i press that button and nothing happens, my phone reboots and same screen is back. i could restore it with kies, but i dont know my serial number, and on my box there is none written. how to fix my problem? or atleast is it possible to get my serial number using twrp terminal or something? thank you for your answers
Click to expand...
Click to collapse
The number is "hidden" on the back not easy to read with the black version
https://techloverhd.com/wp-content/...upside-down-IMEI-and-serial-number-musked.jpg
Hi, my S7 started acting strange a few days ago so I decided to reboot it. Ever since, it would turn on, let me use the screen for about 15 seconds before becoming unresponsive and rebooting itself.
I decided to use the "Emergency Recovery Software and Initialization" feature on Smart Switch. The whole process completed, but the phone keeps booting up to a screen that says "Device Storage Corrupt". Theres a Reset Device button at the bottom but it does not do anything.
The next thing I did was boot into Recovery and selected "Wipe data/factory reset" but it always says "Data wipe failed".
The full error message:
E: format_volume: make ext4 failed on /dev/block/platform/155a0000.ufs/by-name/USERDATA with 1(I/O error)
-- Set Factory Reset done...
Data wipe failed.
Click to expand...
Click to collapse
Could anyone please suggest what else I can do?
Thank you in advance.
Tried flashing stock with ODIN (3.12.3 minimum version)?
Add all 4 parts of the ROM into ODIN, use CSC instead of HOME_CSC to ensure it resets after the flash
Put the phone into Download mode (Volume Down & Home & Power)
Ensure the COM port is highlighted at the top of ODIN to show it sees the phone (Connect to PC via USB)
Hit start and wait for the flash to complete
You can download the ROM / Firmware from updato.com or search for samfirm tool here on XDA
So I followed your instructions and It flashed successfully, but on the phone a blue screen appears with the android and "Erase" written below it. It stays like this for a while before saying "Error!" and then booting into recovery and displaying the same message as I mentioned in my original post.
E: format_volume: make ext4 failed on /dev/block/platform/155a0000.ufs/by-name/USERDATA with 1(I/O error)
-- Set Factory Reset done...
Data wipe failed.
Click to expand...
Click to collapse
I do not understand why it does not let me wipe data/factory reset my phone.
EDIT: I tried again using the steps you told me, except I checked "Re-Partition" this time. The exact same problem still persists.
Unfortunately it sounds like hardware failure, probably not much more you can do other than send it in for repair
Hi all, i have s7 edge G935T which stucked on boot loop and not starting after screen of T mobile, i have tried all the firmware possible and i have tried to put original PIT file but still it is not booting up, dear please help me out from here.
Thanks
RQ14 said:
So I followed your instructions and It flashed successfully, but on the phone a blue screen appears with the android and "Erase" written below it. It stays like this for a while before saying "Error!" and then booting into recovery and displaying the same message as I mentioned in my original post.
I do not understand why it does not let me wipe data/factory reset my phone.
EDIT: I tried again using the steps you told me, except I checked "Re-Partition" this time. The exact same problem still persists.
Click to expand...
Click to collapse
did you fix it?
Hey, unfortunately I had to buy a new phone. I sent that one back and got a refund. I think it was a hardware failure
click "wipe" and then click "format data"
i have a very strange problem with this device i have tried everything imaginable to get it working but no luck, when it boots up everything is normal until when you try to use it you get all these annoying pop ups telling you there no free space and google play services has stopped or some other app has stopped basically you cant really use anything, when i tried to perform a hard rest everything goes without an error the reset sais its successfull but when you boot up again after reset nothing is changed like you didnt even do it, same goes with trying to flash the device the flash passes without errors but nothing changes i tried to flash with usb firmware using research tool and using an SD card update but same exact problem, can anyone help me plz
seif113 said:
i have a very strange problem with this device i have tried everything imaginable to get it working but no luck, when it boots up everything is normal until when you try to use it you get all these annoying pop ups telling you there no free space and google play services has stopped or some other app has stopped basically you cant really use anything, when i tried to perform a hard rest everything goes without an error the reset sais its successfull but when you boot up again after reset nothing is changed like you didnt even do it, same goes with trying to flash the device the flash passes without errors but nothing changes i tried to flash with usb firmware using research tool and using an SD card update but same exact problem, can anyone help me plz
Click to expand...
Click to collapse
You can find a older version of firmware for this device
This will fix it
I have tried older versions but still no luck
seif113 said:
I have tried older versions but still no luck
Click to expand...
Click to collapse
Then you can try fastboot
I have tried flashing with fastboot still the same, basically every possible way i wonder if the phone memory is faulty
Hallo,
at first: I tryed to post my problem in the CAT s61 section. But i got the Message that i do not have enough posts/points to do so. It was suggested by the forum to post my thread in Q&A.
I updated my CAT S61 via OTA, same way as the last updates. I am not sure to what version the update was. I had no problems or issues with the phone before.
Very shortly after booting up my phone crashes. I have to boot it up again and get that message every time:
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!......
okay
drive google com file d 1zQHeQOlk2qlXDCSm8zx7s_c7s3UMOwTm view (questionmark) usp=sharing
Message on my phone on boot: "Android Recovery
CAT/CatS61/CatS619/PKQ1.190118.001/LTE_s0201121.0_S61S1.022.01user/release-keys
use volume up/down and power.
can't load Android system. Your data may be corrupted. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device
"
I shared a picture of the phone via GDrive. There is no option to upload pictures.
I can't find any useful help on the CAT-Phones site. The FAQ on the Site is mostly stuff for Android beginners. No PC tools or anything.
I don't want to lose my data and wipe my phone as suggested on the phone Message....
What can i do?
Sorry english is not my main language.
Same problem here, CAT S61, no idea if I had an update but today keeps rebooting to Android Recovery Screen,
If I power off and on I can get back into the phone with an annoying "Toolbox has stopped" error, CAT FAQ says to force stop but before I can get that far it reboots again.
Phone is charged.
Did you fix the problem?
Regards, Simon
ToolBox App Cache
Hey Simon, yes i got an email response from the cat support. I was on a buisness-trip, sorry for my late reply. I fixed it.
You have to open the app details of the toolbox app. force stoo the app, and under a sub-option in the apo info delete its cache and reboot.
If your cat s61 is in the restart-loop you can force stop ist by pressing power and vol down simultanously for dunno 8-13 seconds.
You have to be real quick. i needed like six attemps. but it worked for me.
No dataloss at all.
Thanks Dominus, I did find those instructions before your reply and tried it multiple times, but always before I could complete the instructions the phone would restart again.
I ended up doing a hard reset, not a pleasant experience, lost everything of course, photos were all in the cloud fortunately.
Phone is now operating normally again, I hope this isn't going to be a regular thing, I will certainly persevere with your instructions if it does.
Regards, Simon
Hello!! A friend of mine have a CAT S61 that after update won't boot and displays this error "Your deviced is corrupt. It cant be trusted and will not boot" but he didn't tried to root it or something like that.
And when I told him to get into recovery and wipe data he got this error of "no such file or directory.."
Do you know how to solve this error or do yo know where I can get the Stock Rom or OTA to flash and try? Ty
AugusTroll said:
Hello!! A friend of mine have a CAT S61 that after update won't boot and displays this error "Your deviced is corrupt. It cant be trusted and will not boot" but he didn't tried to root it or something like that.
And when I told him to get into recovery and wipe data he got this error of "no such file or directory.."
Do you know how to solve this error or do yo know where I can get the Stock Rom or OTA to flash and try? Ty
Click to expand...
Click to collapse
It seems they tried flashing something that was not meant for their device and now it has corrupted the system partition or somehow wiped out the operating system.
You will need to flash the full stock firmware to solve this. Can you boot the device into its flash mode? Download mode, fastboot mode or some similar flashing mode.
Do a Google search for:
"Return to stock (your model number)"
Sent from my SM-S767VL using Tapatalk
Droidriven said:
It seems they tried flashing something that was not meant for their device and now it has corrupted the system partition or somehow wiped out the operating system.
You will need to flash the full stock firmware to solve this. Can you boot the device into its flash mode? Download mode, fastboot mode or some similar flashing mode.
Do a Google search for:
"Return to stock (your model number)"
Click to expand...
Click to collapse
Ty for your response.
He says he didn't tried to flash anything. But I think the only way to solve this will be flash the stock Rom. The problem is that we didn't found the stock Rom and CAT didn't answered our emails.
Thanks again for your help!