Related
Hi All,
i have unlocked bootloader, Rooted ICS
now i installed the latest JB update via the SD card method (renaming it to E201_768_SDUPDATE).
did the power+vol down method. intstalled it and reboot.
now all i get is this message coming up.
"The Device is UnLocked.
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Booting recovery kernel image"
and it gets stuck there at the ASUS screen.
i have tried to install the APX driver from universal driver 0.7 TF700, and all i get is unknown device in win7 device manager.
hence i cant get into NVflash or Fastboot.
is there anything else that i can do to unbrick this tablet.
are there any other drivers that i need to install in win7 x64 or it to recognize that it is an asus tablet.??
Looks like the JB update didn't write everything properly - you still have the old bootloader. You should really have created backups for nvflash before trying to upgrade to JB.
But it's still not too late. Can you switch yout device to fastboot mode? If yes, then it's just a matter of getting your PC configuration right.
Then the next thing I would do: re-flash some custom recovery via fastboot, make sure it works and you have adb root access, check if /sdcard is ok, then install the AndroidRoot bootloader to create your blobs for nvflash, reboot into recovery, pull the blobs to your PC via adb, and only then try to upgrade to JB again.
_that said:
Looks like the JB update didn't write everything properly - you still have the old bootloader. You should really have created backups for nvflash before trying to upgrade to JB.
But it's still not too late. Can you switch yout device to fastboot mode? If yes, then it's just a matter of getting your PC configuration right.
Then the next thing I would do: re-flash some custom recovery via fastboot, make sure it works and you have adb root access, check if /sdcard is ok, then install the AndroidRoot bootloader to create your blobs for nvflash, reboot into recovery, pull the blobs to your PC via adb, and only then try to upgrade to JB again.
Click to expand...
Click to collapse
Hi, no unfortunately i cant access fastboot, i have tried using the TWRP method of and all i get it a message saying waiting for device. when i try to push the TWRP.blob file.
i think my problem is that the usb device drivers are not working hence win7 x64 cant recognize the tablet when it is turned off (APX mode i believe)
dazzyd said:
Hi, no unfortunately i cant access fastboot, i have tried using the TWRP method of and all i get it a message saying waiting for device. when i try to push the TWRP.blob file.
Click to expand...
Click to collapse
Let's check it step by step:
- On the device, can you still activate the fastboot mode (USB icon)?
- On your PC, you should see a USB device with vendor ID 0b05 and product ID 4daf. Should be visible somewhere in Device Manager under Windows, maybe someone else can give you details (under Linux everything is much simpler with lsusb).
- On the PC, "fastboot devices" should give you more than no output at all (some question marks, AFAIR).
_that said:
Let's check it step by step:
- On the device, can you still activate the fastboot mode (USB icon)?
- On your PC, you should see a USB device with vendor ID 0b05 and product ID 4daf. Should be visible somewhere in Device Manager under Windows, maybe someone else can give you details (under Linux everything is much simpler with lsusb).
- On the PC, "fastboot devices" should give you more than no output at all (some question marks, AFAIR).
Click to expand...
Click to collapse
Hi again, no i cant see the usb icon,
i am only getting this Asus screen
the Device is UnLocked.
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Booting recovery kernel image"
and it gets stuck there at the ASUS screen.
dazzyd said:
and it gets stuck there at the ASUS screen.
Click to expand...
Click to collapse
And if you hold down Volume-down while powering on, it's the same? In that case, 3 icons should appear before it tries to start the recovery kernel.
_that said:
And if you hold down Volume-down while powering on, it's the same? In that case, 3 icons should appear before it tries to start the recovery kernel.
Click to expand...
Click to collapse
yes i have tried holding down the volume-down while power on and still nothing. no icons appear.
dazzyd said:
yes i have tried holding down the volume-down while power on and still nothing. no icons appear.
Click to expand...
Click to collapse
Sorry, then I am out of ideas.
dazzyd said:
Hi All,
i have unlocked bootloader, Rooted ICS
now i installed the latest JB update via the SD card method (renaming it to E201_768_SDUPDATE).
did the power+vol down method. intstalled it and reboot.
now all i get is this message coming up.
"The Device is UnLocked.
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Booting recovery kernel image"
and it gets stuck there at the ASUS screen.
i have tried to install the APX driver from universal driver 0.7 TF700, and all i get is unknown device in win7 device manager.
hence i cant get into NVflash or Fastboot.
is there anything else that i can do to unbrick this tablet.
are there any other drivers that i need to install in win7 x64 or it to recognize that it is an asus tablet.??
Click to expand...
Click to collapse
You're done. You need to send out for repair. Sorry, but I haven't see any one here able to recover the device with the above message.
buhohitr said:
You're done. You need to send out for repair. Sorry, but I haven't see any one here able to recover the device with the above message.
Click to expand...
Click to collapse
hmm bummer.. no other way to force install a device driver to detect the tablet on my win7 pc.? all i need is a glimmer of hope that i can still talk to the tablet at the lowest level interface. ie APX mode.
dazzyd said:
hmm bummer.. no other way to force install a device driver to detect the tablet on my win7 pc.? all i need is a glimmer of hope that i can still talk to the tablet at the lowest level interface. ie APX mode.
Click to expand...
Click to collapse
The driver on your PC is not the problem. For using nvflash in APX mode you'd need the Secure Boot Key, which is unique for each device and which Asus does not give us, or the blob for the wheelie tool that can be created with the AndroidBoot hacked bootloader, which is also unique for each device. But for creating this blob, you need working fastboot access.
I've spent lots of time looking through forums trying to answer/solve my issue so I hope it's not something stupid I've missed. Sorry for the trouble if it is though.
So, my issue is that I simply cannot unlock the bootloader of my Nexus S (i9020T). The phone's connecting to my computer via Samsung Android ADB Interface as seen under the Device Manager. I see the proper device ID when I type "fastboot devices" into the adb command prompt w/ phone in fastboot mode. Then, when I type "fastboot oem unlock" the phone starts the unlock verification process -- I select yes, the phone restarts, but it goes back to the stuck Google screen. Then, if I pull the battery and go into fastboot mode directly, bootloader's still locked. I've tried this quite a few times and same result -- same result trying to unlock w/ some of the toolkits here (WugFresh's NRT, m.sabra's root tool). Haven't tried Odin but from what I've read it would also require an unlocked bootloader to do anything. I've even tried a few other things like pushing recovery and bootloader images onto the phone via adb, but these also failed due to the locked bootloader.
I also cannot enable USB debugging under phone settings either b/c I now can't get past the Google logo/fastboot mode menu. Didn't think this was required to unlock bootloader though.
Background: Phone had the latest auto updated version of Android when the phone all of a sudden turned off in the middle of the night recently. Weird b/c the battery was basically full. It now always gets stuck on the Google logo upon normal restart. It goes into fastboot mode OK if I remove the battery and press power/vol. buttons -- I then first tried the restore and recovery functions there, etc, but no effect.
Any ideas? Or is the phone just dead now?
Thanks! :fingers-crossed:
Edit:
I've now tried what's described as a possible solution here: http://forum.xda-developers.com/showthread.php?p=44753413#post44753413. It didn't work since that also needs bootloader to be unlocked.
I've also tried to solve it w/ all versions of Odin. None of them detect my phone even after installing Kies w/ drivers. I think I have the required drivers though since I can command the phone fine through adb. And Odin should need bootloader unlocked to work anyway...
Edit 2:
To add, one of the first things I tried was to do a manual factory data reset in the recovery menu (selecting 'yes' to erase all data).
And I tried adb sideload of the OTA .zip file. But installation was aborted. The following appeared immediately under the regular adb sideload instruction in the system recovery menu (under "Now send the package you want to apply to the device..."):
Finding update package...
Opening update package...
Verifying update package...
Installing update...
file_getprop: failed to stat "/system/build.prop": No such file or directory
Installation aborted.
Bump w/ more info.
I tried GOOMANAGER but wasn't rooted and I think that might have screwed up my Fastboot possibly....when I try to do boot into recovery now and select the RCK option I get the dead / sick droid and it says error every time. I don't know what to do now! Any ideas? I also tried to downgrade from 10.6.1.14.10 to 10.6.1.14.8 so I can root and install TWRP and ROMS, but need to get into recovery to do that. I cannot get into Fastboot / recovery to load stuff!!! HELP!!!!!!!!
TerrorTodd said:
I tried GOOMANAGER but wasn't rooted and I think that might have screwed up my Fastboot possibly....when I try to do boot into recovery now and select the RCK option I get the dead / sick droid and it says error every time. I don't know what to do now! Any ideas? I also tried to downgrade from 10.6.1.14.10 to 10.6.1.14.8 so I can root and install TWRP and ROMS, but need to get into recovery to do that. I cannot get into Fastboot / recovery to load stuff!!! HELP!!!!!!!!
Click to expand...
Click to collapse
You are aready in the fastboot mode when you are in the bootloader menu. Look on the upper left corner, you will see the fastboot is active...
LetMeKnow said:
You are aready in the fastboot mode when you are in the bootloader menu. Look on the upper left corner, you will see the fastboot is active...
Click to expand...
Click to collapse
Ok, but I can't do anything from there can I? Don't I have to select one of the three options? RDK Android or Wipe? RDK is what allows you to load zips right? I can not load that it gives me the dead android...
TerrorTodd said:
Ok, but I can't do anything from there can I? Don't I have to select one of the three options? RDK Android or Wipe? RDK is what allows you to load zips right? I can not load that it gives me the dead android...
Click to expand...
Click to collapse
Yes, you can fastboot your custom recovery. Can you tell me what you intend to do with your device? Your rom, kernel, and version?
LetMeKnow said:
Yes, you can fastboot your custom recovery. Can you tell me what you intend to do with your device? Your rom, kernel, and version?
Click to expand...
Click to collapse
I've unlocked the bootloader and I wanted to root it. I'd like to put a custom recovery TWRP and custom ROM probably CM 10.1 or something like that. Currently I'm running stock ROM build JOP40D.US_epad- 10.6.1.14.10-2-13-8-1. (I understand this build is not rootable so I was going to either downgrade or try to load a custom ROM) Kernel version 3.1.10-gb1a9af5 [email protected] #1
When I get to the fastboot menu there are the three options to chose from and when I select the RCK I get the dead droid with error underneath every time. So I have been unable to load anything.
TerrorTodd said:
I've unlocked the bootloader and I wanted to root it. I'd like to put a custom recovery TWRP and custom ROM probably CM 10.1 or something like that. Currently I'm running stock ROM build JOP40D.US_epad- 10.6.1.14.10-2-13-8-1. (I understand this build is not rootable so I was going to either downgrade or try to load a custom ROM) Kernel version 3.1.10-gb1a9af5 [email protected] #1
When I get to the fastboot menu there are the three options to chose from and when I select the RCK I get the dead droid with error underneath every time. So I have been unable to load anything.
Click to expand...
Click to collapse
The dead adroid is the stock recovery. There are two option for you to install the custome recovery.
1. Downgrade your firmware version and use motochopper to get root before using goo
2. Use fastboot to install your custome recovery
Read this thread: http://forum.xda-developers.com/showthread.php?t=2252563
The last few pages have an instruction and link to use fastboot.... Good luck..
and itightu
LetMeKnow said:
The dead adroid is the stock recovery. There are two option for you to install the custome recovery.
1. Downgrade your firmware version and use motochopper to get root before using goo
2. Use fastboot to install your custome recovery
Read this thread: http://forum.xda-developers.com/showthread.php?t=2252563
The last few pages have an instruction and link to use fastboot.... Good luck..
Click to expand...
Click to collapse
Thanks. I'll have to find that. I think that is the main problem for me. I don't think I'm doing the Fastboot thing correctly. Thanks I'll check it out tonight for sure!!
TerrorTodd said:
Thanks. I'll have to find that. I think that is the main problem for me. I don't think I'm doing the Fastboot thing correctly. Thanks I'll check it out tonight for sure!!
Click to expand...
Click to collapse
Ok Scott's too rebooted the machine into Fastboot and the USB Driver is not recognized. I have downloaded the USB drivers from ASUS Sync program and unstalled Sync.
In the top corner it says:
Key driver not found...Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801" A03
Starting Fastboot USB download protocol
The options at the boot menu are RCK ANDROID WIPE DATA
Not sure how to get the drivers to recognize....without that I'm dead in the water...any thoughts?? I thought for sure that the ones from ASUS would do the trick....
Should I have other menu options at Fastboot?
TerrorTodd said:
Ok Scott's too rebooted the machine into Fastboot and the USB Driver is not recognized. I have downloaded the USB drivers from ASUS Sync program and unstalled Sync.
In the top corner it says:
Key driver not found...Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801" A03
Starting Fastboot USB download protocol
The options at the boot menu are RCK ANDROID WIPE DATA
Not sure how to get the drivers to recognize....without that I'm dead in the water...any thoughts?? I thought for sure that the ones from ASUS would do the trick....
Should I have other menu options at Fastboot?
Click to expand...
Click to collapse
You are already in the fastboot mode. If you have downloaded scott recovery, you can start using it.
LetMeKnow said:
You are already in the fastboot mode. If you have downloaded scott recovery, you can start using it.
Click to expand...
Click to collapse
But I cannot as the USB does not recognize the device when it goes into fastboot. Works fine when in normal operation I can access the tablet through the USB, but in fastboot it does not recognize it. Can't seem to find a solution all USB drivers I have loaded do not work. Updating the drivers from the window on PC that opens does not work. UGH!!!!!!
TerrorTodd said:
But I cannot as the USB does not recognize the device when it goes into fastboot. Works fine when in normal operation I can access the tablet through the USB, but in fastboot it does not recognize it. Can't seem to find a solution all USB drivers I have loaded do not work. Updating the drivers from the window on PC that opens does not work. UGH!!!!!!
Click to expand...
Click to collapse
Can you explain how you do it? You may miss a step or something..
LetMeKnow said:
Can you explain how you do it? You may miss a step or something..
Click to expand...
Click to collapse
I followed this to the "T"
This is the summary from the Scott post:
1. Download the "install recovery.zip" from the above link
2. Extract it some where on your computer, prefer in the document folder
3. Check and make sure that the "USB debugging" is ticked on your device under the developer option menu
4. Download the TWRP 2.6.1.0.blob file from here: http://techerrata.com/browse/twrp2/tf700t
5. Rename it to "recovery.blob" and put it in same folder with all the fastboot files so that you can use Scott's script
6. Double click on the Scott's script or bat file and follow the instructions on the screen until you see the phrase says "write is okay or completed"
7. When it is finished, you can now reboot your device, done..
When it reboots it will not load drivers and I cannot access the tablet / fastboot.
It shows this at fastboot and I cannot do anything. Happens with script and if I manually do it. I can't use fastboot no matter what I try the USB drivers do not recognize the tablet.
Key driver not found...Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801" A03
Starting Fastboot USB download protocol
The options at the boot menu are RCK ANDROID WIPE DATA
TerrorTodd said:
I followed this to the "T"
This is the summary from the Scott post:
1. Download the "install recovery.zip" from the above link
2. Extract it some where on your computer, prefer in the document folder
3. Check and make sure that the "USB debugging" is ticked on your device under the developer option menu
4. Download the TWRP 2.6.1.0.blob file from here: http://techerrata.com/browse/twrp2/tf700t
5. Rename it to "recovery.blob" and put it in same folder with all the fastboot files so that you can use Scott's script
6. Double click on the Scott's script or bat file and follow the instructions on the screen until you see the phrase says "write is okay or completed"
7. When it is finished, you can now reboot your device, done..
When it reboots it will not load drivers and I cannot access the tablet / fastboot.
It shows this at fastboot and I cannot do anything. Happens with script and if I manually do it. I can't use fastboot no matter what I try the USB drivers do not recognize the tablet.
Key driver not found...Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.10-20130801" A03
Starting Fastboot USB download protocol
The options at the boot menu are RCK ANDROID WIPE DATA
Click to expand...
Click to collapse
You can try to use the window prompt to change the directory to the fastboot.exe folder and type this command to see if you can get to your recovery: fastboot reboot-recovery or fastboot reboot recovery
LetMeKnow said:
You can try to use the window prompt to change the directory to the fastboot.exe folder and type this command to see if you can get to your recovery: fastboot reboot-recovery or fastboot reboot recovery
Click to expand...
Click to collapse
I don't think that will help as the Recovery gives me the dead droid every time. I was trying to replace the recovery in this exercise. This is more of a pain that its worth I think. Phones are so much easier to do this with. UGH!
TerrorTodd said:
I don't think that will help as the Recovery gives me the dead droid every time. I was trying to replace the recovery in this exercise. This is more of a pain that its worth I think. Phones are so much easier to do this with. UGH!
Click to expand...
Click to collapse
Follow this post - - > http://forum.xda-developers.com/showthread.php?p=30260444 <-- if you want to install the drivers.
Also make sure that you have a working fastboot environment and run the command prompt from the folder where fastboot.exe is located. The dead android you are seeing when accessing the recovery it's normal with Stock Recovery, nothing is wrong with your device.
BTW, i suppose that your device is already unlocked because otherwise Fastboot won't work.
Pretoriano80 said:
Follow this post - - > http://forum.xda-developers.com/showthread.php?p=30260444 <-- if you want to install the drivers.
Also make sure that you have a working fastboot environment and run the command prompt from the folder where fastboot.exe is located. The dead android you are seeing when accessing the recovery it's normal with Stock Recovery, nothing is wrong with your device.
BTW, i suppose that your device is already unlocked because otherwise Fastboot won't work.
Click to expand...
Click to collapse
Dead Droid with the word "Error" underneath it is normal?
Yes the device is unlocked. I cannot get into recovery and cannot get Fastboot to work because the stupid USB drivers don't recognize the tablet. Works fine when not in Fastboot mode, but when goes into fastboot no USB. It's maddening!!!!
Yes dead android it's ok.As for the driver just follow the link i posted and install the driver manually,that will solve the driver issue.
Pretoriano80 said:
Yes dead android it's ok.As for the driver just follow the link i posted and install the driver manually,that will solve the driver issue.
Click to expand...
Click to collapse
Will do this tonight when I get home from work and will report back!
TerrorTodd said:
Will do this tonight when I get home from work and will report back!
Click to expand...
Click to collapse
Ok so the problem was that I had the damn keyboard connected and was trying to connect through that. I took that off and UBS recognized immediately!! Going to try and root now etc. I will report back again!
Keyboard connected = BAD
TerrorTodd said:
Ok so the problem was that I had the damn keyboard connected and was trying to connect through that. I took that off and UBS recognized immediately!! Going to try and root now etc. I will report back again!
Keyboard connected = BAD
Click to expand...
Click to collapse
What Windows version are you running? Win 8 doesn't seem to recognize the fastboot drivers, or maybe it was that you have to change the option of Windows only using Microsoft signed drivers?? Can't quite remember. But lots of people were unsuccessful getting fastboot to work in Win8.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Hi,
I am trying to restore my TF300T to stock ROM and when accessing fastboot I get the <device not found message>
I have ADB/FASTBOOT installed on my laptop (running Win7 64bit)
My tablet details are below:
Device = Unlocked
Key driver not found..Booting OS
Android cardhu-user bootloader <1.00e> released by "TW_epad-10.6.1.15.3-20130416" A03
Starting Fastboot USB download protocol
I have the RCK / Android and Wipe Data icons but no USB icon (I believe this is correct as I am automatically in fastboot mode, based upon the information above)
I have read a lot of posts but an unable to resolve this matter. Any help is greatly appreciated.
Thanks in advance.
Hi!
That is correct. The "starting fastboot USB download protocol" tells you that you are in fastboot mode. Now comes the tricky part: Finding a fastboot package that works with your computer and your Transformer. F.e. I have three different ADB/Fastboot installations and only one works. I've installed this one here: http://forum.xda-developers.com/showthread.php?t=2588979
Note: The programm installs itself into C:\adb\ so you have to copy your recovery there...
You have to check first if your Transformer is connected. If "fastboot devices" is retuning a serial number than it's all fine... :good:
Hello everyone,
I need some help with the following situation:
Using Odin I successfully flashed my Galaxy A32 5G with Android 13 (as indicated by the green PASS in Odin).
When the phone tries to reboot, I get the dreaded error message, "Can't load Android system. Your data may be corrupt....."
On my PC I issued the command, >adb devices, but no devices were found.
This is probably because I did not enable USB debugging, when the phone was still working.
I'm trying to avoid doing a factory reset, because I don't want all my data wiped.
According to the following article, you can flash an OTA file using "adb sideload" command, even without enabling USB debugging.
However, everything else I've read says that adb commands work only when USB debugging is enabled.
Fix “Can’t Load Android System Your Data May Be Corrupt” Without Resethttps://www.droidwin.com/fix-cant-load-android-system-your-data-may-be-corrupt-without-reset/
Can someone perhaps clarify whether or not USB debugging is required for using adb commands?
Thank you very much,
Peter
plee12 said:
Hello everyone,
I need some help with the following situation:
Using Odin I successfully flashed my Galaxy A32 5G with Android 13 (as indicated by the green PASS in Odin).
When the phone tries to reboot, I get the dreaded error message, "Can't load Android system. Your data may be corrupt....."
On my PC I issued the command, >adb devices, but no devices were found.
This is probably because I did not enable USB debugging, when the phone was still working.
I'm trying to avoid doing a factory reset, because I don't want all my data wiped.
According to the following article, you can flash an OTA file using "adb sideload" command, even without enabling USB debugging.
However, everything else I've read says that adb commands work only when USB debugging is enabled.
Fix “Can’t Load Android System Your Data May Be Corrupt” Without Resethttps://www.droidwin.com/fix-cant-load-android-system-your-data-may-be-corrupt-without-reset/
Can someone perhaps clarify whether or not USB debugging is required for using adb commands?
Thank you very much,
Peter
Click to expand...
Click to collapse
I think, In stock recovery only the adb sideload command works so it don't need USB Debugging to be turned ON.
aiSanaul said:
I think, In stock recovery only the adb sideload command works so it don't need USB Debugging to be turned ON.
Click to expand...
Click to collapse
Thanks for your input. Encouraged by your input, I read the article again and realized that I have to put the phone in sideload mode first.
So, I went back to the stock recovery mode and selected the menu item, "Apply update from ADB". Then I see the message on the phone, "Now send the package you want to apply....with adb sideload <filename>". Now that I thought the phone was in sideload mode, on the PC I entered ">adb devices". This time it recognized the device and displayed the device name. However, it also displayed the word, "unauthorized", after the device name. According to the article, if sideload is properly entered, it should display the word, "sideload".
Anyway I tried entering ">adb sideload update.zip", and I got the error message, "device unauthorized".
So, any idea how to get the phone to be authorized?
If this is not possible, I was thinking of replacing the stock recovery with a custom recovery like TWRP. This way I can at least back up all my data first before doing a factory reset. However, I believe installing TWRP requires the bootloader to be unlocked, which automatically wipes all data. So, this defeats the purpose of installing TWRP in the first place
Is there some trick to install TWRP without unlocking the bootloader?
Thank you
plee12 said:
Thanks for your input. Encouraged by your input, I read the article again and realized that I have to put the phone in sideload mode first.
So, I went back to the stock recovery mode and selected the menu item, "Apply update from ADB". Then I see the message on the phone, "Now send the package you want to apply....with adb sideload <filename>". Now that I thought the phone was in sideload mode, on the PC I entered ">adb devices". This time it recognized the device and displayed the device name. However, it also displayed the word, "unauthorized", after the device name. According to the article, if sideload is properly entered, it should display the word, "sideload".
Anyway I tried entering ">adb sideload update.zip", and I got the error message, "device unauthorized".
So, any idea how to get the phone to be authorized?
If this is not possible, I was thinking of replacing the stock recovery with a custom recovery like TWRP. This way I can at least back up all my data first before doing a factory reset. However, I believe installing TWRP requires the bootloader to be unlocked, which automatically wipes all data. So, this defeats the purpose of installing TWRP in the first place
Is there some trick to install TWRP without unlocking the bootloader?
Thank you
Click to expand...
Click to collapse
As you already know this is not possible without unlocking bootloader, I will explain further more to make it easy to understand.
If you don't unlock your bootloader and try flashing TWRP on your phone using ODIN Flash Tool then maybe your phone get into an veification error and your phone will end up in a softbrick. You can repair your phone by flashing your phone's stock firmware using ODIN Flash Tool, eventually you will wnd up loosing all your data.
Also unlocking bootloader in Samsung devices is so easy by turning OEM Unlocking in Developer options, but you don't seem to have access to your phone.
An Unlocked Bootloader is the PASS, which allows you to do custom thing to your phone. So without it, this won't work, maybe that is why you got that error “Can’t Load Android System Your Data May Be Corrupt”.
ALTERNATIVELY you can try flashing your phone's OLD original Stock Firmware using ODIN Flash Tool and see what happens. You can also try flashing TWRP through ODIN Flash Tool. Only flash OFFICIAL TWRP made for your device (if any), otherwise you don't have options I guess.
also Why didn't you Unlocked Bootloader before flashing a custom rom? because of warranty?
aiSanaul said:
As you already know this is not possible without unlocking bootloader, I will explain further more to make it easy to understand.
If you don't unlock your bootloader and try flashing TWRP on your phone using ODIN Flash Tool then maybe your phone get into an veification error and your phone will end up in a softbrick. You can repair your phone by flashing your phone's stock firmware using ODIN Flash Tool, eventually you will wnd up loosing all your data.
Also unlocking bootloader in Samsung devices is so easy by turning OEM Unlocking in Developer options, but you don't seem to have access to your phone.
An Unlocked Bootloader is the PASS, which allows you to do custom thing to your phone. So without it, this won't work, maybe that is why you got that error “Can’t Load Android System Your Data May Be Corrupt”.
ALTERNATIVELY you can try flashing your phone's OLD original Stock Firmware using ODIN Flash Tool and see what happens. You can also try flashing TWRP through ODIN Flash Tool. Only flash OFFICIAL TWRP made for your device (if any), otherwise you don't have options I guess.
also Why didn't you Unlocked Bootloader before flashing a custom rom? because of warranty?
Click to expand...
Click to collapse
Thanks very much for your detailed explanations and for your continued support.
Let me answer your question first about why I didn't unlock the bootloader before flashing a custom ROM. Let me backtrack and explain how this problem came about in the first place. My phone was doing an automatic system update two weeks ago (Android 13). After downloading and installing, it tried to boot up. That's when it got stuck in an infinite rebooting loop. At that point, I had no way to change any settings on the phone.
Also, to clear up any confusion, I was not trying to flash a custom ROM. I was simply trying to flash the stock ROM (Android 13), supposedly the same firmware version as the OTA that broke my phone after the automatic system update. I was thinking that perhaps there was an internet glitch during the automatic system update process, which corrupted the OS. So, I was just trying to re-install the same version as the OTA to see if that would solve the problem.
I had also thought about flashing the original version that came with the device (Android 11). But, I think I read somewhere that either Samsung phones do not allow the user to downgrade, or even if it does allow you do so, the downgrading process will wipe out the existing data on the phone. Perhaps you can confirm that or not?
In the meantime, as you suggested, I will look into how to flash TWRP.
Thank you