Hi all,
I have been hammering away at this one, and putting it on the back-burner, but now, it is really getting to me. Samsung Galaxy Tab Pro 10.1 SM-T520
It has been rooted with ODIN, and shows no problem, (things seem much easier now, as I have re-jigged lots of my old phones using so many more tools, I am not an expert, but can read and search without too much problems) I was very careful to choose the correct file, CF-Auto-Root-picassowifi-picassowifixx-smt520.zip, I have rechecked this step several times, as most of the instructions I found ODIN device ID:COM box should become yellow, when on newer versions it is blue I think, I wondered if I was going mad,
Root Checker Root access granted, all fine. I have Root access. n.
Installed CWM ,latest recovery for a Pro 10.1 wifi, recovery 6.0.3.1 Titanium backup-ed, all ready to go and Reboot and flash a new ROM.. No joy. .. Installed TWRP , same.
When it re-starts it ,shows the galaxy logo, flashes off, then back on, and then fails. Android dead with a red warning , standard recovery KOT49H.T520XXUANAE, all I can do is the usual options:apply update. The only thing I haven't tried is to just wipe all the data. I have a backup of my apps with Titanium Backup on the SD card,I am not that bothered really about much other data if its a pain. I just want control of my device and to try a new ,cleaner ROM(SMT520_GraveD_V3.0)
This has been bothering me for ages, I have read so many posts so am now getting really frustrated I have bought triangle away app. today although I think I sorted that issue early on anyway , but just in case...
Super SU seemed to have vanished so that is back installed
I think I searched and found the Mount/system issue and looked into an issue that lead me to the .system folder, but it is hidden, so I could not find the file it related to. I dont have the specifics to hand as I checked it out at work. I wondered if it is because I have ES file manager, not ASTRO as it said in some of the posts I found.but sure this is a red herring.
I have tried everything..I have a Mac at home and PC at work, I have tried ADB and can see &restart the device etc... so I am connected, first I got the error that it didn't recognise the sideload command. Read up on ADB , looked at the help etc. sideload isn't there as a command, very confusing. But I think I got there one I figured out paths, as of course they are different on a Mac, and possibly more so as I have 2 drives in it, which often confuses me ..grr.
I can of course get into the bootloader, with ON+VOL -, it tells me so far the system is : Official and Knox Warranty Void: 1 which I think is fine, but a chap at work suspected this, but after lots of threads I gather this is normal..
Sorry if long, just thought I should be as clear as possible. I have not really come across such an awkward issue as this , my HTC One was a breeze:crying:
*edit* Just worked out through trial and error, that to use the sideboot command I had to select send via ADB and now with the path /Desktop/SMT520_GraveD_V3.0.zip I was able to send the file but with the following messgae : E:footer is wrong and E:signature verification failed, twice.. So some progress
Thanks !
Just to say after being up waay too long on this, I discovered there is a newer firmware T520XXUANI1_T520BTUANI1_BTU which I may aswell upgrade to first, but of course I cannot do this OTA now As it recognises the device is 'tampered with' *sigh* so gun and games with Odin for Mac tonight, or JODIN3 , just to get the firmware upgrade(which seems to be a jungle of fake download links). before a Rom without bloatware..
I am also not completely clear why, as from another thread about KNOX, as I am basically running stock , without custom recovery.. According to this thread , but I am getting a bit confused now
http://forum.xda-developers.com/gal...neral/knox-warranty-void1-otas-t2996067/page2
Click to expand...
Click to collapse
however this is another story from the ROM install. Apologies
Well. No replies, but I did eventually solve this. Hopefully this can help someone. I am a tinkerer, but I really nearly gave up on this..But this was a cheap second hand tablet ( my first) and I want to see what it can do before I test drive one on my mother who is having nightmares with every Windows laptop I give her!
Once I got to a PC , I had access to Odin3, although it is not available online (apparently to Mac) I could not get it to work due to Java issues (JOdin3 online - brilliant idea but no joy for me so far)
I had the Rom I wanted ( GraveDigger- SMT520_GraveD_V3.0.zip ), the firmware update (T520XXUAOD2_T520BTUAOB1_BTU.zip(i think)) and the unlock file (CF-Auto-Root-picassowifi-picassowifixx-smt520.zip) , non of which I could install in any way , due to being locked out of using a custom Rom bootloader!
At this point I factory reset and cleared the cache( as that is the only options in the basic bootloader!) I also has ADB on the PC so attempted to install the files this way (after messing about using some software to produce the .tar and .md5 files needed for Odin. I tried everything to get this into proper 'bootloader mode' all from scrach again, including trying the adb oem unlockbootloader command, which I would never get to work as I could not get there!
With Odin, I was also again able to flash the firmware update, eventually, and of course had to unlock again. I was curious if I could now use the OTA update, and could not. At some point, in repeating this process( as I think it hung up several times and needed a hard reboot) I had at this point fully wiped the device as I know that is another reason to have glitches and an unstable ROM later.
I think I then tried to check and although T520XXUAOD2 seems to still be the firmware, at some point I managed to get online ( I think some superuser app which I have had to try several may have notified me that KNOX was reset:laugh:When I go to About>Software update it said I had the latest update! Good news!
At this point I had installed both CWM and TWRP again , and thought I would try TWRP.I had tried CWM and the same problem, like a double flash of the Samsung Logo , so I know it had reset !!
THIS TIME I used TWRP ( I thought of trying CWM touch, but its either paid, or I would have to find and ABD the file over I guess) , I managed to re-apply the Root file, Root checker confirmed this , as it had throughout this ordeal!, although apart from ACCESS GRANTED I dont really know what the rest means..Anyway although picassowifi , was still in Device name on TWRP I chose an earlier recovery version to install.- twp-2.7.0.0-picassowifi.img. When I re-booted, I was able to get the TWRP recover image, and install the ROM, I cannot remember if I re-rooted as I was so elated.
I had a few , freezing moments, reinstalling most of my apps through Titanium Backup, I think I just tried to reinstall everything which of was unnecessary, after a hard reset, all seems fine. I checked and the TWRP recovery seems to have stuck. I am not entirely sure how to check about the firmware , but for now I feel this is progress.
Good Luck if anyone found this any use.
Just to add, when you search this ( and probably many other models) you seem to get so many sites, offering exactly the same unlock information, in exactly the same way, many of the downloads seem to take you to many weird and wonderful places. So I tended to look here for downloads if possible. But I had to join SamMobile (which seems a useful site for the firmware upgrade) and trawl all over and assume similarities between other Samsung devices to fully check I was not being an idiot. But this was very odd and I could not find any posts or other workarounds that I did not try. But this new ROM feels lovely and smooth so far, and I now want to look into this tablet further
Related
Hi guys, thanks for the forum and i hope to become a part of it. I've been under so much stress since yesterday, my galaxy s3 (on EE in the UK) for the first time decided it's data was corrupted yesterday after my battery died, never done this or anything like it before, and it wouldn't let me access the phone itself unless the data was reset.
I had a lot of very precious pictures in my gallery from the weekend, which unfortunately chose not to backup to google+ for the last few days, even though it always has up until recently. All night/day i've been trying to figure out and get software to recover these photos, which i think is possible as i did it a long time ago on a blackberry, but not android yet. I'm just hoping it can be done so the photos aren't forever lost, the other stuff gone doesn't bother me so much.
The guide i'm following (here: http://forum.xda-developers.com/gal...de-internal-memory-data-recovery-yes-t1994705) says it needs to be rooted first, and i can't even get past step 1. I've only ever rooted my old galaxy S1 (which worked back then) but i can't seem to get the S3 to do it. And now my phone also believes there's no sim card in and i get no signal now.
this is the guide i followed: http://www.ibtimes.com/how-root-sam...-jelly-bean-official-firmware-tutorial-975812
though i think i need a newer PDA file to flash my i9305 with. I'm on the EE network running 4.3 jelly. It installed Super SU but root checker says it still isn't rooted.
So have i messed this up? And is there any hope for me getting these pictures back?
Thanks in advance for any help, it's much appreciated.
if you are running on 4.3 then you are not following the right guide to root...
use THIS ONE instead... if it fails to root use the workaround part, i used it and worked....used the workaround to install custom recovery and then flashed chainfire zip from his website and updated SU and worked.
are you still able to boot the phone?
Thanks for the response, tried that guide and still getting no signal on my phone (no mobile connection at all, sim card isn't recognised as being there) and i don't think it's rooted right. Still saying SuperSU has stopped working when i try to open it.
I put the Root_SuperSU.1.02-Busybox.1.21.0.zip on the internal SD and tried that too.
Which is the chainfire zip you're talking about, could you possibly link it? I don't really get what you mean by custom recovery, do you mean it's the same as flashing the Busybox thing from recovery mode?
And yeah it still boots up normally...
use that tutorial to install a custom recovery...then install this SuperSU - http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip?retrieve_file=1 - flash it in custom recovery....after that update app with playstore and should work.
but i suggest you get it to a specialized shop to get your photos back...
I tried to unlock my bootloader, following various guides, and kept getting stuck on the "Download Mode !!!" part. I just want to install the latest stable version of Cyanogenmod on my phone since the stock ROM is being a real pain for me (very slow and unresponsive).
I have:
Android 4.1.2
Build Number: JZ054K
Software Version: AME-XXX
I read online that you need the Euro firmware to unlock the bootloader, can I flash the euro firmware and will it mess with my service? I'm confused as to how the firmware affects things since I've read conflicting information. I didn't flash my firmware a few hours before trying to unlock, so maybe that's the problem?
Seriously?
There aren't enough threads and guides for you to read already? Everything you need is already out there on this forum so why start another thread just because you are too lazy to search and read for yourself?
I have read around and have tried a number of guides a number of times. They haven't worked for me and I'm just wondering what i'm doing wrong. Even though all the information is out there, I don't have the experience to understand it apparently. I've spent hours trying to figure things out but i keep reading conflicting info and half-explained steps and now I'm just confused and would like a clear point in the right direction.
So, do i need to reflash the latest firmware, wait a few hours, then try again on a full charge? Or do i need a euro firmware? Which guide should i follow?
I've downloaded a few applications and driver packages and whatnot but if those could possibly conflict with each other and cause problems i could work with a fresh OS. I'm running OS X but i have linux VMs and friends with clean windows installs (mine is all sorts of messed up)
eatfoodnow said:
I tried to unlock my bootloader, following various guides, and kept getting stuck on the "Download Mode !!!" part. I just want to install the latest stable version of Cyanogenmod on my phone since the stock ROM is being a real pain for me (very slow and unresponsive).
I have:
Android 4.1.2
Build Number: JZ054K
Software Version: AME-XXX
I read online that you need the Euro firmware to unlock the bootloader, can I flash the euro firmware and will it mess with my service? I'm confused as to how the firmware affects things since I've read conflicting information. I didn't flash my firmware a few hours before trying to unlock, so maybe that's the problem?
Click to expand...
Click to collapse
It isn't a question of firmware, the phone needs to have an unlockable bootloader to be able to be, well, unlocked. Here is a list http://forum.xda-developers.com/showthread.php?t=2181581 of P880 bootloader versions. Follow the guide to check which BL your phone has.
Thats obsolete, all versions can be unlocked afaik, either with official method or by fuse editing. No need to keep sim card in,you just need proper drivers
Oh, OK, I didn't know that. But, even better, OP should not have any trouble, provided he follows the BL unlock guide here http://forum.xda-developers.com/showthread.php?t=2224020
Maybe his BL is already unlocked OR is relocked (meaning can't be unlocked anymore).
Its more likely that his drivers are messed up imo.
The fuse editing method should work for everyone, i recommend you give it a try
So the fuse method would be the "BL-unlock.bat" method on that bootloader unlock forum post? I've tried it before, but I'll try it again. The directions only say to run it, is there anything else I need? Now, since it's a .bat file I absolutely have to run it on Windows, right? Because if so I'll use a friend's computer instead of my windows installation.
What are the necessary installations before I run the file? How should I configure settings on my phone? (like what type of usb connection should it be)
There are a lot of things that people expect readers to know but I'm really not very knowledgeable about standard practices for phone stuff so I really need every step. Thanks for helping!
Since its.bat file, you can open it in text editor to see which commands it executes. I'd still recommend to do it on windows machine, other OSs may work but aren't tested.
You need abd & fastboot drivers, plus drivers for our device. It's been a while since I've done it, but afaik you can get proper device drivers via lg support tool.
Flying_Bear said:
Since its.bat file, you can open it in text editor to see which commands it executes. I'd still recommend to do it on windows machine, other OSs may work but aren't tested.
You need abd & fastboot drivers, plus drivers for our device. It's been a while since I've done it, but afaik you can get proper device drivers via lg support tool.
Click to expand...
Click to collapse
Also, correct me if i'm wrong I only had stock for 2hours, but also stock needs usb debugging to be enabled or adb won't work?
Yep, afaik usb debugging needs to be enabled
When you are fast enough, it is possible in charging mode wihle the carger animation is shown. But you have install adb driver very fast...
So I'm pretty sure I got the bootloader unlocked, I ran the .bat file and it went through everything until the part where it checks to see if my bootloader is unlocked, it just froze forever, so I closed it.
How should I go about checking?
Also, what would be my next step now for installing CM10.1.3? I tried to follow the guide on the cyanogenmod wiki (install_CM_for_p880) (I can't post links yet)
...but ran into problems with pushing it into root with adb. It said I didn't have permissions, so I googled some stuff, but just got myself confused.
Thanks for all the help btw!
eatfoodnow said:
So I'm pretty sure I got the bootloader unlocked, I ran the .bat file and it went through everything until the part where it checks to see if my bootloader is unlocked, it just froze forever, so I closed it.
How should I go about checking?
Also, what would be my next step now for installing CM10.1.3? I tried to follow the guide on the cyanogenmod wiki (install_CM_for_p880) (I can't post links yet)
...but ran into problems with pushing it into root with adb. It said I didn't have permissions, so I googled some stuff, but just got myself confused.
Thanks for all the help btw!
Click to expand...
Click to collapse
you can check your bl status by entering sw mode (phone off, hold vol+ and insert charger) or reeboting into bl (adb reboot oem-unlock)
to install cm steps are:
-install recovery (you can choose either cwm or twrp, it's more about looks than functions)
-download rom zip onto sd card
-install said zip from said recovery, there's no adb involved
Now my personal opinion, I really don't see the point in flashing 10.1, i would go staright for cm11 if i were you
Ok well I think I got things together more or less, eventually I tried to install CM10.1 with the ROM manager app. I forgot to select the options to wipe my data partitions and now I'm stuck in an endless boot loop every time I turn the phone on. I tried to boot from my backup using CWM which I made with the app prior to trying to install, and it gave me an error about an MD5 checksum failing, no matter what I tried. Should I do the factory reset/wipe option with CWM now? What's my best option.
Also why would you recommend CM11 over CM10.1? I don't want to have to deal with a nightly, all this phone stuff is a supreme headache to me.
eatfoodnow said:
Ok well I think I got things together more or less, eventually I tried to install CM10.1 with the ROM manager app. I forgot to select the options to wipe my data partitions and now I'm stuck in an endless boot loop every time I turn the phone on. I tried to boot from my backup using CWM which I made with the app prior to trying to install, and it gave me an error about an MD5 checksum failing, no matter what I tried. Should I do the factory reset/wipe option with CWM now? What's my best option.
Also why would you recommend CM11 over CM10.1? I don't want to have to deal with a nightly, all this phone stuff is a supreme headache to me.
Click to expand...
Click to collapse
Factory reset then get nandroid manager app and see if you can restore your stuff with that
CM11 is bugless atm and performance (imo) is way superior
So after a factory reset/data wipe, my phone just booted into CM10.1 and now that's working. And it looks like all of my stuff on the phone is still there (though of course apps aren't installed and whatnot, that wouldn't make sense). Thanks for all the help!
I tried to find a feature list or something to see what exactly is better about CM11, and found out that "stable" doesn't exactly mean stable for CM, and that it looks like a good idea to update, so I think I will try to update to that. Do you know anywhere that has an actual feature list to show me what CM11 does that CM10.1 doesn't?
Good evening and sorry if post a thread of which I see two similar oness
However, I could not find a solution in the other ones and have questions which go a little further and really hit my privacy.
I have two XZ3 and both could go into recovery node when I bought them and after a while could not.
I used the reset to factory seting fo wiping cache etc. quite regularly as I had/have reasons to belive that I was/am spied on.
Sice the recovery mode possibility is gone I feel totally unsafe with both phones.
I tried all possibilities I can find of this website or any other in internet, and all were without success.
As described by others, after pushing the power button, there is no led light and it boots suoer-quicklyto the blue stripe view in which we wait till the boot is complete.
Till two days ago I thought ok, the phone just needs a flash, wipe everything away once and all would be resolved.
Well, two days ago I flashed my phone the first time from lollipop to kitkat, which worked without problems and then rooted it with gifroot and then put back lollipop.
Everything ran smoothly and after the whole process I had a rooted lollipop version with a working recovery. I tried the apps which confirm if the root works abd everything was great.
Tthe morning after, however the recovery possibility was gone. The phone was still rooted for everything, but for recvery mode.
I tried several apps, which I gave superuser access with SuperSu, but even from the apps the boot goes always just the NORMAL way without recovery.
To give it another try today I flashed that xz3 again, then rooted it with Kingo root, which in Kitkat firmware worked lalso super easy, the checked with other apps whihchconfirmed that the root works, but still no recovery possibility, no matter with which app..
I really need a specialist who can explain that to me, as I am going mad to think that someone else has total control over my phones.
How realistic is that some spyware does not allow the recovery as of course it knows that it would be eliminated then.
Please give me your thuoghts or knowledge. Everything helps. And if you know a method with which I can be sure that nothing is keft on the phone, I would appreciate.
Thanks and Regards
iFran72 said:
Good evening and sorry if post a thread of which I see two similar oness
However, I could not find a solution in the other ones and have questions which go a little further and really hit my privacy.
I have two XZ3 and both could go into recovery node when I bought them and after a while could not.
I used the reset to factory seting fo wiping cache etc. quite regularly as I had/have reasons to belive that I was/am spied on.
Sice the recovery mode possibility is gone I feel totally unsafe with both phones.
I tried all possibilities I can find of this website or any other in internet, and all were without success.
As described by others, after pushing the power button, there is no led light and it boots suoer-quicklyto the blue stripe view in which we wait till the boot is complete.
Till two days ago I thought ok, the phone just needs a flash, wipe everything away once and all would be resolved.
Well, two days ago I flashed my phone the first time from lollipop to kitkat, which worked without problems and then rooted it with gifroot and then put back lollipop.
Everything ran smoothly and after the whole process I had a rooted lollipop version with a working recovery. I tried the apps which confirm if the root works abd everything was great.
Tthe morning after, however the recovery possibility was gone. The phone was still rooted for everything, but for recvery mode.
I tried several apps, which I gave superuser access with SuperSu, but even from the apps the boot goes always just the NORMAL way without recovery.
To give it another try today I flashed that xz3 again, then rooted it with Kingo root, which in Kitkat firmware worked lalso super easy, the checked with other apps whihchconfirmed that the root works, but still no recovery possibility, no matter with which app..
I really need a specialist who can explain that to me, as I am going mad to think that someone else has total control over my phones.
How realistic is that some spyware does not allow the recovery as of course it knows that it would be eliminated then.
Please give me your thuoghts or knowledge. Everything helps. And if you know a method with which I can be sure that nothing is keft on the phone, I would appreciate.
Thanks and Regards
Click to expand...
Click to collapse
Spyware cannot affect Recovery unless it is granted root permissions and is embedded on system.
Also do not use KingoRoot, a thread in the SG note 3 forums reported Spyware installed after using it, source. For now steer clear of that application until all claims have been proven false
At any rate, ( assuming you have Unlocked Bootloader ) just flash another kernel with recovery, do a full wipe including formating the system partition and restore your system via flashing a rom
9
Revontheus said:
Spyware cannot affect Recovery unless it is granted root permissions and is embedded on system.
Also do not use KingoRoot, a thread in the SG note 3 forums reported Spyware installed after using it, source. For now steer clear of that application until all claims have been proven false
At any rate, ( assuming you have Unlocked Bootloader ) just flash another kernel with recovery, do a full wipe including formating the system partition and restore your system via flashing a rom
Click to expand...
Click to collapse
i got that problem i cant hard reset my phone i forgott my posswords and the key combo dosent work and i have never rooted before, can you give me a step by step for dummie (me)
petterssonjohan said:
9
i got that problem i cant hard reset my phone i forgott my posswords and the key combo dosent work and i have never rooted before, can you give me a step by step for dummie (me)
Click to expand...
Click to collapse
If you can enter flash mode, flash the latest firmware and software for your device using flash tool.
What is flash mode? I can get the phone in a mode where the indicator lamp turns blue is it that?
get Flashtool @ https://xperiafirmware.com/flashtool/
it includes Xperiafirm so you can download a stock ROM for your device and build an .ftf file
when you have the ftf file, drag it into the main Flashtool window
follow prompts
Hopefully someone has some input on this.
My phone is a 626s, a32eul on T-Mobile. I've had this phone since it came out and really grew to liking it, but lately it's been nothing but a headache. I had it rooted with Kingroot (was the only root at the time that worked) since I got it, but never went any further because there wasn't any ROMs available at the time. Recently I started messing around again and decided to reset and try to upgrade to Marshmallow, but I seem to have caused more problems with it than I anticipated.
I've lost the stock recovery completely, currently have TWRP installed. I've tried to remove Kingroot but no matter what I try it won't go away. I followed a replacement procedure from Supersu, but Kingroot is still present. None of the uninstalls seem to work, tried deleting all related files that I could find with root explorer but it still comes back. Factory reset and wiped everything several times, still there . .
My main reason for all this is to load a de-bloated ROM ( I only have 8G of storage, less than 1G after all the useless BS apps update themselves ) I've turned off all the auto-update stuff on the phone and Google, but it still manages to loop back and download everything anyhow.
Would anybody have some input on this? I'd like to get it back to when I took it out of the box for the first time so I can start over, or at very least get rid of King for good so SU can take over? I've found a couple image files for the stock recovery, but all seem to be corrupted or not correct for this phone.
Thanks in advance for any help you can provide . .
And now I think I've done it. Was messing around in TWRP, I think I fat-fingered the system option when wiping, have no operating system now . . I think my frustration has gotten the better of me on this one.
I might have this thing finally figured out. Seems when I upgraded my laptop to Win10, I never re-installed C++ to keep the RUU file running. I must have sobered up enough because its downloading the file right now after 8 hours of smashing my face on 2 keyboards . .
Yes.
re flash with the original RUU then flash twrp recovery.
With twrp recovery install supersu.
Then you will be rooted.
Best way to flash the RUU.
#1 rename the RUU to 0PM9IMG.zip
#2 Copy it to the sd card.
#3 Put sd card in the phone.
#4 Boot to download mode.
Vol DWN plus Power.
#5 it should ask and say hit vol up to flash the ruu when you boot to download mode.
#6 Hit volume up.
No messing around with windows this way and it works alot better off the sd card.
Download one of the RUU's that we have uploaded to here.
If you need the RUU zip rile let me know.
I have uninstalled a system app that I shouldn't have (something to do with network conectivity according to the recovery log) and everything was fine until I updated my device. I hadn't restarted it since removing the system app but after tyhe update it will no longer go past the Samsung galaxy logo. I remember doing something similar to either this device or another and I remember that I was abler to get into the system enough to be able to reinstall the neccessary app and fix the problem. However, this time I cannot get into adb at all. adb won't show any devices when in recovery, download mode, or at any of the three stages of the boot screen. I have tried wiping the cache and everything but factory resetting it as I have data that I can't lose. Any help would be appreciated whether getting adb install-existing to work or to pull important files off of the device before a reset. The device runs android 12 not rooted.
(...)
Go back via odin to the original firmware including the correct BIT.
(...)
Flash in Odin using home CSC file, simple
You only need to run ADB in Windows PC terminal or DOS mode in order to Odin flash firmware. No need to run ADB commands in the phone.
Just be sure that you install the "Samsung ADB Driver" into your PC before
you try Odin flashing firmware.
Just be sure you download the proper firmware for your phone.
Good luck, have a great day and have fun!
Thank you to all the help, but eventually I got into the phone. For anyone who may encounter a similar problem in the future:
After the phone reboots enough, it resets all preinstalled apps and removes any user installed ones and goes into safe mode. From here, the phone goes through the initial setup screens but all data is still intact, just not apps. Concerningly, it doesn't ask for you to enter your password, it just puts you on the homescreen, which seems bad from a privacy perspective as any samsung repair tech can easily cause the phone to boot loop. From here, you can back up anything important and factory reset. There is no way to exit safe mode once you've gotten this far.
I don't remember why odin didn't work, it may have been that I couldn't get the firmware to download as Samsung likes to change that stuff all the time or it may not have reinstalled the system app neccessary.
I should've been more clear in the original post but I have not flashed any unofficial firmware just the U1 firmware to remove carrier bloat, but that was way before this occurred. In case it wasn't clear, the problem happened because through
Code:
adb shell uninstall --user 0 package.name
an important system app was removed (something network related) which caused android to crash when trying to start the service. In short: be careful what you remove when using adb and, for all you forum members: read the whole post instead of jumping to conclusions about the user's mistake and if it isn't clear, ask for more details. Again, thank you to all the helpful comments even if they didn't end up working.
ZenDeveloper said:
Thank you to all the help, but eventually I got into the phone. For anyone who may encounter a similar problem in the future:
After the phone reboots enough, it resets all preinstalled apps and removes any user installed ones and goes into safe mode.
Click to expand...
Click to collapse
May I ask how long it took to "reboot enough"? I'm having issue updating to Android 13. It got into boot loop (the 2nd time actually. I mentioned about it in another thread a few weeks ago. Today I decided to try again). Anyway I am wondering if there's anyway I don't need to reset the whole thing. What you described interested me.
Thanks
hatoxda said:
May I ask how long it took to "reboot enough"? I'm having issue updating to Android 13. It got into boot loop (the 2nd time actually. I mentioned about it in another thread a few weeks ago. Today I decided to try again). Anyway I am wondering if there's anyway I don't need to reset the whole thing. What you described interested me.
Thanks
Click to expand...
Click to collapse
Sorry for the late reply,
I don't know how many times it needs to reboot to go into safe mode but it seemed like quite a bit maybe 20-30 times possibly like 100. But once it does it'll go through the initial setup screens and let you in without a password. It's very important to backup everything on your device before you mess with any system apps or update especially if you've previously messed with system apps. I however don't use google hence I didn't have a backup of anything and needed to get it off before hand.
It could also be possible that Samsung removed this back door in android 13 and just the act of trying to update it gets rid of it. I don't know I'm just throwing around ideas.
Rule #1 - if a OS is fast, stable and fulfilling its mission, let it be! Firmware upgrades/updates can and do break Samsung's.