Database Develop

I ^%%* it up

Guys, I don't have the original image and the only image I have on my SDcard is eclair 2.0-1.2
I am just upset with the OP for providing insufficient instructions and I am very unaware of the previous setup required before doing it so.
I am in recovery mode and my G1 keeps rebooting over and over since I wipe the factory default.
I apologize for not using the search button because I don't see any answers, or maybe I just want direct answer.
Sorry, I have to ask this, how do I recover the image on my G1? I have it connected to my PC but it's currently in recovery mode right now.
Please provide me detailed step to step what I need to do. Thank you for your time and effort, this is upsetting me big time.

misdirection said:
I am just upset with the OP for providing insufficient instructions
I am in recovery mode and my G1 keeps rebooting over and over since I wipe the factory default.
I apologize for not using the search button because I don't see any answers, or maybe I just want direct answer.
Sorry, I have to ask this, how do I recover the image on my G1? I have it connected to my PC but it's currently in recovery mode right now.
Please provide me detailed step to step what I need to do. Thank you for your time and effort, this is upsetting me big time.
Click to expand...
Click to collapse
LMAO dude this is pure richness right here, you are posting in wrong section you know. And that title of yours isnt following forum rules. Were you rasied under rock or something? There are tons of guides that will tell you what to do, plus even vid guides. All directions are all here for your use.
-Best Regards Ace
Ps. if your in rec mode then your not bricked
Brick=cant turn on G1 pr G1 is stuck @ Splash screen

Gotta give props for the thread title ... is very attracting ... lol

Stop blaming the guys making the ROMS for your own F-up.
Learn to read the instructions.
ALL of them.
Don't blame them for the fact you didn't read THIS :
first you will need these things haykuro spl,ext3/linux-swap if you dont have it and if you do wipe them clean

The please provide links for those kinds of software.
I am really upset that no one will help me

Oh lordy!
Havent laughed this hard in aaaaages!
If nothing else you make for some great entertainment value

misdirection said:
Guys, I don't have the original image and the only image I have on my SDcard is eclair 2.0-1.2
I am just upset with the OP for providing insufficient instructions and I am very unaware of the previous setup required before doing it so.
Click to expand...
Click to collapse
You should be upset at yourself for not reading the clear instructions that are inherent in nearly every ROM update procedure. READ the instructions.
I am in recovery mode and my G1 keeps rebooting over and over since I wipe the factory default.
I apologize for not using the search button because I don't see any answers, or maybe I just want direct answer.
Click to expand...
Click to collapse
Searching forums before diving blindly into processes like these will certainly save you frustration and a bricked device. Again, blaming someone else for your laziness isn't exactly the route you should take.
Sorry, I have to ask this, how do I recover the image on my G1? I have it connected to my PC but it's currently in recovery mode right now.
Please provide me detailed step to step what I need to do. Thank you for your time and effort, this is upsetting me big time.
Click to expand...
Click to collapse
Search the forums.

shadowch31 said:
Oh lordy!
Havent laughed this hard in aaaaages!
If nothing else you make for some great entertainment value
Click to expand...
Click to collapse
I know this place is ***** great, this guy got me laughin here

just return the phone and get an apple iphone

Okay..
How do I put the files into SD card even when my phone is in boot mode?

misdirection said:
Guys, I don't have the original image and the only image I have on my SDcard is eclair 2.0-1.2
I am just upset with the OP for providing insufficient instructions and I am very unaware of the previous setup required before doing it so.
I am in recovery mode and my G1 keeps rebooting over and over since I wipe the factory default.
I apologize for not using the search button because I don't see any answers, or maybe I just want direct answer.
Sorry, I have to ask this, how do I recover the image on my G1? I have it connected to my PC but it's currently in recovery mode right now.
Please provide me detailed step to step what I need to do. Thank you for your time and effort, this is upsetting me big time.
Click to expand...
Click to collapse
1. Read the rules
2. Read the Forum
3. Search on the Forum
4. Post in good place

ums_enable in console
or on amon_ra usb toggle on the main screen

quit hating ppl help noob out, which version of recovery r u using ? or is it stock recovery? Which rom r u trying to flash? If u r using stock recovery u should b serching for something like Fastboot or adb, if u using cyan's or RA's recovery that just find different room to flash.It would b nice to know Phones specs...SPL, Radio, REcovery etc. just like what i got in my sig.
For future references post in Q&A thread or where is the ROM u flashed is, Provide some info if u need help.

I am using standard recovery. I tried Droid Explorer and no luck.

misdirection said:
How do I put the files into SD card even when my phone is in boot mode?
Click to expand...
Click to collapse
Since you're too cocky and too ignorant to do most of the things on here, I suggest you put your phone back to stock as soon as you figure out how to flash images. Get the "recovery image" from here http://developer.htc.com/google-io-device.html, then go ahead and get a card reader, drop the file on the reader, rename it update.zip, boot into recovery, alt+s to flash it, alt+w to wipe, then reboot.

misdirection said:
I am using standard recovery. I tried Droid Explorer and no luck.
Click to expand...
Click to collapse
ok then go here and set up adb after u done follow the link in my sig to flash RA 1.5.2 recovery. After u get RA recovery find the rom u need to flash id suggest Cyans rom or WG and make sure ur SPL and RAdio is uptodate.
Good luck.

Can you atleast change the title?
Such language on a sunday.

HAHA too bad this dump won't allow the wrecking crew to 'assist' this here fella...

Ace42 said:
Can you atleast change the title?
Such language on a sunday.
Click to expand...
Click to collapse
I know right! but hey give him a break i bet almost every1 of u ****ed something up eh ;-) .... personally i so "bricked" my phone twice.....lost root at least 5 times fing around with the roms and scripts....

Brutal,
Me and Ace42 spent around 2 pages in manups thread trying to help only to be told '**** You' we have given him all the links to help him yet still he does not listen and proceeds to be rude and obvoxious.
I think he is looking more for someone to do it all for him rather than using the information already given out to help himself.
All I can say is good luck, your gonna need it!

[Q] URGENT Device boot loop I need urgent help please

I am on my. Way to return the phone to best buy. I was rooted and with an unlocked bootloader and had TWRP. I used the Nexus Toolkit and relocked the phone before flashing stock and now it won't boot. It just shows the team win logo flashing over and over. Please please help as they close in 30 minutes. Also it isn't detected in adb or fast boot.
EDIT: fixed it!

I am at this same point. How did you fix it?

chris23445 said:
I am on my. Way to return the phone to best buy. I was rooted and with an unlocked bootloader and had TWRP. I used the Nexus Toolkit and relocked the phone before flashing stock and now it won't boot. It just shows the team win logo flashing over and over. Please please help as they close in 30 minutes. Also it isn't detected in adb or fast boot.
EDIT: fixed it!
Click to expand...
Click to collapse
TheAnarchist1 said:
I am at this same point. How did you fix it?
Click to expand...
Click to collapse
Going to assume he managed to Re-flash factory images.
Moral of this story is don't use toolkits and learn how to recover from bootloops and read about potential problems that could arise.

ADB is your friend!

TheAnarchist1 said:
I am at this same point. How did you fix it?
Click to expand...
Click to collapse
Hold the power and volume down button until it boots into recovery. Then plug the phone into your computer. Download the stock 5.0.1 zip (luckily I already had it downloaded). Use the toolkit and unlock the bootloader. It will say its successful but the phone will boot loop again. Boot into recovery and should say the bootloader is unlocked. Then flash the stock zip file and it should work! I had to figure it all out as I went because I couldn't figure it out online lol.
radicalisto said:
Moral of this story is don't use toolkits and learn how to recover from bootloops and read about potential problems that could arise.
Click to expand...
Click to collapse
To be fair, I was in a huge rush and relocked the bootloader before flashing stock. Totally a user error and not a toolkit error.

Boot loops

radicalisto said:
Going to assume he managed to Re-flash factory images.
Moral of this story is don't use toolkits and learn how to recover from bootloops and read about potential problems that could arise.
Click to expand...
Click to collapse
Or, the moral is follow the toolkit developer's directions.......

aiiee said:
Or, the moral is follow the toolkit developer's directions.......
Click to expand...
Click to collapse
Yep. That/don't rush when resetting the phone and do it in the wrong order.

aiiee said:
Or, the moral is follow the toolkit developer's directions.......
Click to expand...
Click to collapse
No, it isn't because...
chris23445 said:
I had to figure it all out as I went because I couldn't figure it out online lol.
Click to expand...
Click to collapse
but if a toolkit had never been used in the first place, there would be nothing to figure out as it would all have been learned in the rooting process.

rootSU said:
No, it isn't because...
but if a toolkit had never been used in the first place, there would be nothing to figure out as it would all have been learned in the rooting process.
Click to expand...
Click to collapse
No lol I would have completely been screwed without the toolkit. All that happened was I did the steps wrong and I have no idea how to unlock the bootloader and relock it and root with adb and the toolkit was easier for me. I could have googled the adb thing but it would have been much more of a hassle.

chris23445 said:
No lol I would have completely been screwed without the toolkit. All that happened was I did the steps wrong and I have no idea how to unlock the bootloader and relock it and root with adb and the toolkit was easier for me. I could have googled the adb thing but it would have been much more of a hassle.
Click to expand...
Click to collapse
Thus proving my point.

radicalisto said:
Going to assume he managed to Re-flash factory images.
Moral of this story is don't use toolkits and learn how to recover from bootloops and read about potential problems that could arise.
Click to expand...
Click to collapse
rootSU said:
Thus proving my point.
Click to expand...
Click to collapse
Not in the slightest . Your analysis is flawed. You assume this problem was caused by not understanding the underlying structure but it wasn't. It was caused by failing to follow directions. Which would have caused him problems had he used ADB or not.

aiiee said:
Not in the slightest . Your logic is skewed. Good luck with that.
Click to expand...
Click to collapse
How is it skewed? If, when he first got his phone, he unlocked and rooted in the normal way and not used a toolkit. He would have known how to use fastboot, including how to flash stock and lock the boot loader. He would not have used a toolkit today and wouldn't have used the wrong order and this thread wouldn't exist.
If you're an advocate for the cheat way and the way that makes it harder for us to help people, so be it. But 95%.of us prefer users to learn things properly and not become a burden to the forum. But you can help them all. Good luck with that.

chris23445 said:
No lol I would have completely been screwed without the toolkit. All that happened was I did the steps wrong and I have no idea how to unlock the bootloader and relock it and root with adb and the toolkit was easier for me. I could have googled the adb thing but it would have been much more of a hassle.
Click to expand...
Click to collapse
how to properly root.
1. run the command "fastboot oem unlock" in fastboot. this unlocks your bootloader.
2. flash a custom recovery via fastboot.
3. flash the latest supersu in your new recovery.
4. reboot with root.
5. woohoo!
this takes about 3-5 minutes.

aiiee said:
Which would have caused him problems had he used ADB or not.
Click to expand...
Click to collapse
Adb is absolutely nothing to do with any of this. Another misconception of toolkit users. Which again, proves my point.

aiiee said:
Not in the slightest . Your analysis is flawed. You assume this problem was caused by not understanding the underlying structure but it wasn't. It was caused by failing to follow directions. Which would have caused him problems had he used ADB or not.
Click to expand...
Click to collapse
you dont use adb to root. nor will adb work while you are in the bootloader. fastboot is what you use

simms22 said:
you dont use adb to root. nor will adb work while you are in the bootloader. fastboot is what you use
Click to expand...
Click to collapse
You can use adb. Fastboot is used for the oem i lock and recovery flash. If you want to put the supersu file on the phone without downloading it on the phone you can just adb push and flash in recovery. Done.

Thanks
chris23445 said:
Hold the power and volume down button until it boots into recovery. Then plug the phone into your computer. Download the stock 5.0.1 zip (luckily I already had it downloaded). Use the toolkit and unlock the bootloader. It will say its successful but the phone will boot loop again. Boot into recovery and should say the bootloader is unlocked. Then flash the stock zip file and it should work! I had to figure it all out as I went because I couldn't figure it out online lol.
To be fair, I was in a huge rush and relocked the bootloader before flashing stock. Totally a user error and not a toolkit error.
Click to expand...
Click to collapse
Thanks for the clear explanation.:good:

@rootSU
For those curious. I figured I would check back in with this thread. I did not use a toolkit to begin with. I have the sdk properly set up and know my fastboot and adb commands and the difference between both. What I did:
1. Fastboot oem unlock
2. Fastboot flash recovery recovery.img (it was twrp)
3. Booted into recovery and it would not let me access the recovery, just kept flashing the TWRP splash over and over and over.
The issue I think for me, was that I did not wait until the Nexus had wiped itself and booted back into Android to rebuild the file system. Hence TWRP farting out. I simply started from scratch again, flashed all the proper stuff that was needed and followed steps, and I was alright after that.
I have since returned the device though and exchanged it with a new Nexus 6, because my back cover had started to pop up in the top right corner above the power and volume buttons....but THAT is another story for another thread : p
Cheers all!
PS: It has been a while since I have owned a Nexus device, hence my own failure to follow the rules. Things have changed a bit with this Nexus it seems, and it was my fault. I am all good now though (or I will be after I set up this new Nexus 6)
PSS: No toolkits were used, or will ever be used in the creation and resolution of this debacle. My life is hard enough without blindly wandering through the forest of Android customization with my hand held by a complete stranger.
: p

TheAnarchist1 said:
@rootSU
For those curious. I figured I would check back in with this thread. I did not use a toolkit to begin with. I have the sdk properly set up and know my fastboot and adb commands and the difference between both. What I did:
1. Fastboot oem unlock
2. Fastboot flash recovery recovery.img (it was twrp)
3. Booted into recovery and it would not let me access the recovery, just kept flashing the TWRP splash over and over and over.
The issue I think for me, was that I did not wait until the Nexus had wiped itself and booted back into Android to rebuild the file system. Hence TWRP farting out. I simply started from scratch again, flashed all the proper stuff that was needed and followed steps, and I was alright after that.
I have since returned the device though and exchanged it with a new Nexus 6, because my back cover had started to pop up in the top right corner above the power and volume buttons....but THAT is another story for another thread : p
Cheers all!
PS: It has been a while since I have owned a Nexus device, hence my own failure to follow the rules. Things have changed a bit with this Nexus it seems, and it was my fault. I am all good now though (or I will be after I set up this new Nexus 6)
PSS: No toolkits were used, or will ever be used in the creation and resolution of this debacle. My life is hard enough without blindly wandering through the forest of Android customization with my hand held by a complete stranger.
: p
Click to expand...
Click to collapse
after fastboot oem unlock, you have to reboot once before flashing the recovery. rarely it doesnt stick, so you just flash it again if nothing appears

Accidentally flashed a file to root that was for KitKat (Im on Lollipop)

So I accidentaly flashed the wrong root file thus making my systemui continuously crash. Any suggestions as to what I can do?

shahrukhraza said:
So I accidentaly flashed the wrong root file thus making my systemui continuously crash. Any suggestions as to what I can do?
Click to expand...
Click to collapse
Stock recovery or TWRP?
Are you looking to undo what you did without having to do a complete wipe, or are you open to more drastic solutions? Because you can always run the toolkit to reset to complete stock by flashing the stock images over your current system. But that would of course perform a complete wipe.

Paddington said:
Stock recovery or TWRP?
Are you looking to undo what you did without having to do a complete wipe, or are you open to more drastic solutions? Because you can always run the toolkit to reset to complete stock by flashing the stock images over your current system. But that would of course perform a complete wipe.
Click to expand...
Click to collapse
I dont really mind a complete wipe. And are you referring to this toolkit? http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3048099
if not could you please tell me which one?
And to clarify, I followed this tutorial: https://www.youtube.com/watch?v=_fPIYhzWlnw . The file that I flashed to attempt to root is in the description of that.

shahrukhraza said:
I dont really mind a complete wipe. And are you referring to this toolkit? http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3048099
if not could you please tell me which one?
And to clarify, I followed this tutorial: https://www.youtube.com/watch?v=_fPIYhzWlnw . The file that I flashed to attempt to root is in the description of that.
Click to expand...
Click to collapse
I actually used this one: http://forum.xda-developers.com/moto-x-2014/development/tool-moto-x-pure-edition-recovery-t2897819 when I was messed around, but I would imagine either would work. When I needed to return to unrooted stock, I believe that toolkit returned me to 4.4.4 unrooted stock, then I just ran the 5.0 OTA once the phone booted up.
The toolkit you referenced is the one I used to unlock the bootloader, flash TWRP, and root my phone. As long as you can get to recovery or fastboot, either toolkit should work to return you to stock. BUT I caution you, I have a pure edition, and these toolkits were made for the pure edition. If you do not have a pure edition, you'll want to read the disclaimers/instructions/other posts to make sure it will work on your phone.

Okay so this escalated quickly.
So here I am being my dumb self , I try to flash TWRP. That goes fine and then I try to wipe my data. After that I reboot it and as its turning on it foes black on the boot animation. and now I cant even get into freaking recovery mode. I dont know what I did but im pretty sure I messed up bad. I need some serious help now and anything is appreciated.

Paddington said:
I actually used this one: http://forum.xda-developers.com/moto-x-2014/development/tool-moto-x-pure-edition-recovery-t2897819 when I was messed around, but I would imagine either would work. When I needed to return to unrooted stock, I believe that toolkit returned me to 4.4.4 unrooted stock, then I just ran the 5.0 OTA once the phone booted up.
The toolkit you referenced is the one I used to unlock the bootloader, flash TWRP, and root my phone. As long as you can get to recovery or fastboot, either toolkit should work to return you to stock. BUT I caution you, I have a pure edition, and these toolkits were made for the pure edition. If you do not have a pure edition, you'll want to read the disclaimers/instructions/other posts to make sure it will work on your phone.
Click to expand...
Click to collapse
Yessir thanks for replying. However I now have a whole new problem. Do you have any suggestions for that? It is the post above^

shahrukhraza said:
Okay so this escalated quickly.
So here I am being my dumb self , I try to flash TWRP. That goes fine and then I try to wipe my data. After that I reboot it and as its turning on it foes black on the boot animation. and now I cant even get into freaking recovery mode. I dont know what I did but im pretty sure I messed up bad. I need some serious help now and anything is appreciated.
Click to expand...
Click to collapse
Hey thats an easy fix just load into the boatloader and reflash the rom through mfastboot
edit: you should be able to get all the files you need from his website http://forum.xda-developers.com/moto-x-2014/general/ota-pure-edition-lollipop-5-0-t2932625

ewalk4866 said:
Hey thats an easy fix just load into the boatloader and reflash the rom through mfastboot
edit: you should be able to get all the files you need from his website http://forum.xda-developers.com/moto-x-2014/general/ota-pure-edition-lollipop-5-0-t2932625
Click to expand...
Click to collapse
Bootloader as in vol. down + power button right? Thats not working too. I also tried other combinations to no luck. And before it was turning on but now its not even booting to the boot animation. Thanks for the link though, if it does magically boot into the bootloader then i'll know what to do at least.
Edit: Okay so theres the charging animation, so thats a start, I guess. Still no luck on the bootloader tho.

Okay got it into bootloader mode!
Now before I do any other stupid thing can somebody just confirm one thing for me? On Graffix's website, this is the img I should flash through mfastboot right
Lollipop 5.0 22.21.11 FULL IMAGE PACKAGE Zip
Just a confirmation because I dont really trust my judgement. Thanks again everybody

shahrukhraza said:
Okay got it into bootloader mode!
Now before I do any other stupid thing can somebody just confirm one thing for me? On Graffix's website, this is the img I should flash through mfastboot right
Lollipop 5.0 22.21.11 FULL IMAGE PACKAGE Zip
Just a confirmation because I dont really trust my judgement. Thanks again everybody
Click to expand...
Click to collapse
Yes that's right remember you only have to flash system

Sorry that my Toolkit suggestion messed you up. I really thought that solution would work, not make it worse.

Paddington said:
Sorry that my Toolkit suggestion messed you up. I really thought that solution would work, not make it worse.
Click to expand...
Click to collapse
Toolkit are never really a good idea it just makes people lazy and not learn how to flash or fix problems on there own.

Paddington said:
Sorry that my Toolkit suggestion messed you up. I really thought that solution would work, not make it worse.
Click to expand...
Click to collapse
Nah man that didnt mess it up, some other stupid thing did it lol. Nothing on you, rather thanks for the help.

ewalk4866 said:
Toolkit are never really a good idea it just makes people lazy and not learn how to flash or fix problems on there own.
Click to expand...
Click to collapse
I agree that Toolkits can make you lazy and not learn how to fix things on your own, but when you need a quick fix and don't have time to figure out what is going wrong, it's always nice to just boot your phone into fastboot or recovery and fix things with a few keystrokes on your computer.

I got it to work guys! Thanks for all the help. It was much appreciated.

I need some help. I'm bricked.

Okay. so after hours of searching and reading about unbricking my nexus 6. I am lost, and very desperate.
So, I unlocked my bootloader, and rooted my phone today using chainfire cf auto root. and all went well. The primary reason I did this was to edit the build.prop file to enable wifi tethering, and this is where my problems started. Using root explorer I added
HTML:
net.tethering.noprovisioning=true
to the end of the build.prop file. I rebooted and now I'm stuck in a bootloop on the google screen.
I did not have a custom recovery installed, so flashing a new rom isn't that easy. I have looked into flashing twrp or cwm from the stock recovery adb sideload feature, but I haven't gotten this figured out either.
So that brings me to where I am at now. I still have an unlocked bootloader, which I guess is leaving me some options, but I just don't know where to go to find information which isn't going to further muck this situation up.
Help, please. I don't have a backup phone. And I am getting desperate.
Thanks in advance

Reboot to the bootloader, flash stock system.img
Sent from my Nexus 6 using Tapatalk

very first off.. http://forum.xda-developers.com/nexus-6/general/attention-questions-t3228454
meaning, you wont get help if tou do ont post it in the right place.
secondly, you have two choices, flash twrp then flash a rom, or flash the factory image(just system.img). what your pro lem is tgat you used a toolkit, instead of learning thd very easy proper way. now you dont know how to do things. its rwally easy to flash twrp via fastboot, and its very easy to flash a factory image using fastboot as well. now ill ask a mod to move your thread into the correct area..

thanks
simms22 said:
very first off.. http://forum.xda-developers.com/nexus-6/general/attention-questions-t3228454
meaning, you wont get help if tou do ont post it in the right place.
secondly, you have two choices, flash twrp then flash a rom, or flash the factory image(just system.img). what your pro lem is tgat you used a toolkit, instead of learning thd very easy proper way. now you dont know how to do things. its rwally easy to flash twrp via fastboot, and its very easy to flash a factory image using fastboot as well. now ill ask a mod to move your thread into the correct area..
Click to expand...
Click to collapse
I am mainly a reader here and don't normally post as I can figure things out on my own normally. So, sorry for posting in the wrong forum.
Help is appreciated..
Thanks.

acscot2 said:
I am mainly a reader here and don't normally post as I can figure things out on my own normally. So, sorry for posting in the wrong forum.
Help is appreciated..
Thanks.
Click to expand...
Click to collapse
i just saw, it was your first post. i didnt mean to sound rude, for that im sorry.
but you have your answer(s). your phone isnt bricked, its just without os. and the os can be flashed, even using a toolkit.

my phone bricks after 5 mins into starting it

please help i have a s10+ when i start it after 5 mins it stops reponding i can try to restart it but it will do the same thing can i unroot it or somthing

qomzt said:
please help i have a s10+ when i start it after 5 mins it stops reponding i can try to restart it but it will do the same thing can i unroot it or somthing
Click to expand...
Click to collapse
Expensive phone and you go mess with it.... Do you have twrp install if you do reflash your boot img it should clear magisk
([emoji813]9/[emoji725]/9[emoji813])

PoochyX said:
Expensive phone and you go mess with it.... Do you have twrp install if you do reflash your boot img it should clear magisk
([emoji813]9/[emoji725]/9[emoji813])
Click to expand...
Click to collapse
no man plsease help i dont know these things i watched a video to do it help

qomzt said:
no man plsease help i dont know these things i watched a video to do it help
Click to expand...
Click to collapse
How you rooted without twrp you patched your img and ADB pushed it?
([emoji813]9/[emoji725]/9[emoji813])

PoochyX said:
How you rooted without twrp you patched your img and ADB pushed it?
([emoji813]9/[emoji725]/9[emoji813])
Click to expand...
Click to collapse
i dont know i have not don the twp thing

qomzt said:
i dont know i have not don the twp thing
Click to expand...
Click to collapse
How did you achieve root on your device then... [emoji52]
([emoji813]9/[emoji725]/9[emoji813])

qomzt said:
please help i have a s10+ when i start it after 5 mins it stops reponding i can try to restart it but it will do the same thing can i unroot it or somthing
Click to expand...
Click to collapse
Sounds like you've jumped into the deep end a bit too early... The best option for you is likely to go to your device's forum, here: https://forum.xda-developers.com/s10-plus
There you can probably find information and guidance on how to root, flash and install stuff to your device. And you'll be able to ask for assistance from other users that have the same device as you (not every device works the same, and that is especially true for Samsung).
A couple of tips for you, going forward:
Do your homework. Read as much as you can about the modifications you're trying to do, and Android modification in general (but remember that things can change fast and a guide you find might be very outdated by the time you read it. The forums are usually the best place for up-to-date info).
Make backups! Always make sure that you have a backup of any important data, and don't store it on the device.
Know how to go back to a working state when you mess up, because mess up you will (everyone does at some point). This tip is of course tied to the first one...
Don't follow some guide or video blindly. Make sure you understand what every step of the process does. That way you won't get stuck like this next time.
Good luck.