Hi guys, I'm pretty new to rooting so tell me if i need to give more info etc cause I know i can be a bit vague.
So I rooted my phone no problem via the all in one kit thing and installed cyanogen, but this was right before the big android update so I wanted to switch back and update to that, but somewhere along the line i got rid of all the Roms (I think)
The stage it's at now: I can boot normally but the startup wizard fails, I assume this is because the stock operating system isnt hooked up to run, regardless I can't find a copy or figure out how to run it. (before my TWRP seemed to stop running on startup)
Bootloader: I don't know how it ended up relocked after I'd unlocked it but am guessing that is why i cant access the custom recovery at the moment (twrp)
If anyone is able could you walk me through, or point me to a guide to show:
How to unlock a relocked phone,
How to get a Stock version of Android (anything after 4.0 I guess because it will auto update?) running on there
Tell me if I'm being dumb in any part of this (apart from pissing about with things I don't understand, haha)
OK, So i'm unlocked and back onto TWRP, that was easy though, What I do need help with is working out how to install the factory Operating system again, last time I tried that is what caused the relocking etc so any help would be amazing.
Thanks, Simon
Redijedeye said:
OK, So i'm unlocked and back onto TWRP, that was easy though, What I do need help with is working out how to install the factory Operating system again, last time I tried that is what caused the relocking etc so any help would be amazing.
Thanks, Simon
Click to expand...
Click to collapse
Is this the same device as the one you are asking about in? [Q] How do I know what RUU to use, and more by Redijedeye
sd_shadow said:
Is this the same device as the one you are asking about in? [Q] How do I know what RUU to use, and more by Redijedeye
Click to expand...
Click to collapse
Sorry yes, meant to close this post now that this particular problem was kinda sorted but didnt get round to it last night. Unless you know a way to get the correct firmware for the wifi? Just seems strange it'd update wrong.
Redijedeye said:
Sorry yes, meant to close this post now that this particular problem was kinda sorted but didnt get round to it last night. Unless you know a way to get the correct firmware for the wifi? Just seems strange it'd update wrong.
Click to expand...
Click to collapse
No, I don't.
I consider this [Completed] and have thread closed.
Related
Anyone know of, or or have a link to a factory rom (hell any rom would do at this point) that I would be able to flash with the stock S3 recovery? Just trying to unbrick my phone. Story of what happened below:
I'm running stock 4.1.1 rooted touchwiz. I wake up this morning to a notification saying I had an update on my phone. Should have definitely waited but without thinking I went ahead and updated, which of course soft bricks? The phone. (boots up, and but hangs at the 4Glte, flash screen)normally this would be an easy fix, I could Odin back to stock or something but I'm down in Mississippi till Monday for training and do not have access to my pc.
I can access the factory recovery on the phone but that's it, have no clue where CWM is. I've tried flashing some backups but the factory recovery says that it's not a signed package or whatever. Anyone have any idea how I can get this sucker booted up and running using just an android tablet?
What about reflashing CWM so I can access my backups? Could I somehow flash CWM with factory recovery?:
Dr. Light said:
Anyone know of, or or have a link to a factory rom (hell any rom would do at this point) that I would be able to flash with the stock S3 recovery? Just trying to unbrick my phone. Story of what happened below:
I'm running stock 4.1.1 rooted touchwiz. I wake up this morning to a notification saying I had an update on my phone. Should have definitely waited but without thinking I went ahead and updated, which of course soft bricks? The phone. (boots up, and but hangs at the 4Glte, flash screen)normally this would be an easy fix, I could Odin back to stock or something but I'm down in Mississippi till Monday for training and do not have access to my pc.
I can access the factory recovery on the phone but that's it, have no clue where CWM is. I've tried flashing some backups but the factory recovery says that it's not a signed package or whatever. Anyone have any idea how I can get this sucker booted up and running using just an android tablet?
What about reflashing CWM so I can access my backups? Could I somehow flash CWM with factory recovery?:
Click to expand...
Click to collapse
first of all you can't flash anything on a stock recovery hence the need of a custom recovery. Second you don't accept the OTA when rooted as it can cause the exact issue that you have. Last there isn't a way to fix your problem via another android device that I know of.
U are going to need a pc and then u will need to download Odin http://forum.xda-developers.com/attachment.php?attachmentid=1165122&d=1340993443 and u can get the official software from here on XDA http://hotfile.com/dl/182822657/9f6...WBLK3_381038_REV09_user_low_ship.tar.md5.html this is the 4.1.1 software. Here is a link to some official pre rooted software http://forum.xda-developers.com/showthread.php?t=1984436 all of these software's you can install though Odin just look up here on XDA on how to use Odin and you will be fine once your phone is up and running again then you will need to get you a custom recovery. Then you can access your backups.
Always_Jonezen said:
U will need to download Odin http://forum.xda-developers.com/attachment.php?attachmentid=1165122&d=1340993443 and u can get the official software from here on XDA http://hotfile.com/dl/182822657/9f6...WBLK3_381038_REV09_user_low_ship.tar.md5.html this is the 4.1.1 software. Here is a link to some official pre rooted software http://forum.xda-developers.com/showthread.php?t=1984436 all of these software's you can install though Odin just look up here on XDA on how to use Odin and you will be fine once your phone is up and running again then you will need to get you a custom recovery.
Click to expand...
Click to collapse
He doesn't have access to his PC PLUS he already knows what to do on that end.
jmxc23 said:
He doesn't have access to his PC PLUS he already knows what to do on that end.
Click to expand...
Click to collapse
Just trying to help out but of course someone always has to criticize. I don't see you giving him any advice.
Thanks for all of advice guys. I'll prob just wait it out till Monday. Thanks again.
Always_Jonezen said:
Just trying to help out but of course someone always has to criticize. I don't see you giving him any advice.
Click to expand...
Click to collapse
He was asking if he can use an android tablet to fix his phone. He doesn't have access to PC at least until Monday it says so in his post. I wasn't even criticizing you at all. Unless he knows someone with a PC in Mississippi or someone here knows how to use one android device to flash something on another android device he sadly will have to wait until he gets home to fix his phone. You didn't do anything to be criticized for trying to help all I did was point out the info that you missed without personally attacking you making it a critique.
jmxc23 said:
He was asking if he can use an android tablet to fix his phone. He doesn't have access to PC at least until Monday it says so in his post. I wasn't even criticizing you at all. Unless he knows someone with a PC in Mississippi or someone here knows how to use one android device to flash something on another android device he sadly will have to wait until he gets home to fix his phone. You didn't do anything to be criticized for trying to help all I did was point out the info that you missed without personally attacking you making it a critique.
Click to expand...
Click to collapse
hey all, I've been reading , downloading etc for hours trying to get back into my GS3.. i was as usual roaming around and saw a post that said something to this effect "do ya need to get back to stock?" and figured yes i need to so i jumped in with both feet ..i had my boot loader unlocked and for some reason locked the darned thing remembering it was locked before i rooted and then i get the screen that says ie: "System software not authorized ~~~~~~~~~~~~" with a yellow triangle over it with an "!" mark in it..
all would have been ok except the line up of the way to do things was kinda outta line.. after i had locked bootloader "which is the way the GS3 came" i thought. at any rate i am now where i said i was and if i can be helped it would be appreciated.. and no repeated.. next time i'll read their whole line up first.. so help me if ya can and i am game right now for about anything ..
All right i'll explain my situation, so my phone is a HTC One SV cricket version, I got Twrp v2.6.3.2, my phone was working perfectly fine until it started lagging a little so i took out battery restarted and the phone restarted on its own every 10 seconds from there on out. So i booted into recovery keep in mind (this was probably pretty stupid but i did it anyways) i wiped the phone, and did advanced wipe thinking the problem would go away but now when i turn it on the screen goes white and says HTC one and freezes. I can still access recovery and fastboot, if there's anyway to fix this please help me.
I understand your problem, you've wiped your Os (System partition).
But unless someone provides you a backup or a rom for cricket, you can't really solve this.
There is not all hope gone, but i am not the one to make this:
Here you find a RUU for cricket.
This is for using from a working OS usually. As you can't boot to your OS, this don't work in this way for you.
There is a way, if somebody with the knowledge and running Linux extracts the rom.zip from the RUU for you. This you should be able to flash from fastboot.
But i can't do this, cause i'm not running Linux on my PC and the Tool to do that is ONLY for Linux.
old.splatterhand said:
I understand your problem, you've wiped your Os (System partition).
But unless someone provides you a backup or a rom for cricket, you can't really solve this.
There is not all hope gone, but i am not the one to make this:
Here you find a RUU for cricket.
This is for using from a working OS usually. As you can't boot to your OS, this don't work in this way for you.
There is a way, if somebody with the knowledge and running Linux extracts the rom.zip from the RUU for you. This you should be able to flash from fastboot.
But i can't do this, cause i'm not running Linux on my PC and the Tool to do that is ONLY for Linux.
Click to expand...
Click to collapse
I use windows 7, so that means i can't do it? would there be anything else that would work even un-rooting the phone?
You don't have root anymore, if you've wiped your Os.
You have no System files anymore.
You need a backup from someone else or the RUU with this:
- http://forum.xda-developers.com/showthread.php?t=2264316
- http://forum.xda-developers.com/showthread.php?t=2264238
- http://forum.xda-developers.com/showthread.php?t=2084470
old.splatterhand said:
You don't have root anymore, if you've wiped your Os.
You have no System files anymore.
You need a backup from someone else or the RUU with this:
- http://forum.xda-developers.com/showthread.php?t=2264316
- http://forum.xda-developers.com/showthread.php?t=2264238
- http://forum.xda-developers.com/showthread.php?t=2084470
Click to expand...
Click to collapse
it looks like those arn't for cricket version of HTC One SV, i'm assuming it wouldnt be a good idea to try them out on my phone. so basically the only hope of my phone working is Linux?
Easiest way is, if some is uploading a cricket TWRP backup for you.
old.splatterhand said:
Easiest way is, if some is uploading a cricket TWRP backup for you.
Click to expand...
Click to collapse
Alright so i gotta find someone to give me a cricket TWRP backup, so i should probably make another post to see if anyone has one then.
old.splatterhand said:
You don't have root anymore, if you've wiped your Os.
You have no System files anymore.
You need a backup from someone else or the RUU with this:
- http://forum.xda-developers.com/showthread.php?t=2264316
- http://forum.xda-developers.com/showthread.php?t=2264238
- http://forum.xda-developers.com/showthread.php?t=2084470
Click to expand...
Click to collapse
i just realized when i looked at my HTC in fastboot it says K2_PLC_Cl which is under the supported devices however i'm totally suck on the process and confused on exactly how i do this. basically i got no idea.
still don't have it fixed
Up
Hey! I don't know if this is the right place, but I'll try to explain my problem.
Yesterday I got a notification of an update(think it's 6.0.0 (MRA58N)). Today, when I tried to install it I just got an "Error!" message.
I tried to reboot the phone, but nothing happened. It doesn't turn on. However, I can get it into that fastboot screen or what it's called.
Haven't had any problems before, and Im kind of a beginner on these technical issues regarding phones.
So could someone please explain what I should do(hopefully nothing to complicated).
Thanks!
That sounds like a rooted phone. Is it? Have you owned the phone from new, or is it second-hand?
dahawthorne said:
That sounds like a rooted phone. Is it? Have you owned the phone from new, or is it second-hand?
Click to expand...
Click to collapse
It was new when I bought it (april 2014). I have only installed updates when getting a notification on the phone. I got a notification to do an update yesterday. Did it today. But while updating it just stopped and said "Error!". Turn the phone off, tried to turn it on but nothing happened.
What's the easiest way to make the phone work again?
Have in mind that Im not experienced at all with these stuff . Never had had any problems before
Thanks
Were you already on a version of Marshmallow? They are both version 6.0.0 regardless of the name (MRA58K/N).
Was there any message apart from just "Error"? Do you remember what it looked like?
I take it that you have enough battery?
I have no idea of the answer, just trying to get some clues.
(Oh, and at worst you can probably flash a new ROM. Don't get too worried just yet... )
dahawthorne said:
Were you already on a version of Marshmallow? They are both version 6.0.0 regardless of the name (MRA58K/N).
Was there any message apart from just "Error"? Do you remember what it looked like?
I take it that you have enough battery?
I have no idea of the answer, just trying to get some clues.
Click to expand...
Click to collapse
Yes, I updated to marshmallow a couple of weeks ago.
Yes, I was on about 75% battery when trying to update.
As far as I recall it was just the android guy and a red text saying Error! (well it said Fel! because it's in swedish.)
It started to install the updates, but just stopped halfway(rough estimate).
Hmm :/
EDIT: Yes, I've asked on other forums, and they have been saying to flash(it's called taht right?) But since I'm new to this stuff, I want to check all possible alternatives first. And if I decide to do this, I'll have to feel fully prepared on what to do, don't want to screw up things even more
To give you at least some hope have a look at this thread:
http://forum.xda-developers.com/google-nexus-5/help/stuck-launching-flashstock-bat-t3244470
If you've never done any flashing before, I recommend that you install Wugfresh's Nexus Root Toolkit. It can be used to flash a new ROM, but I'm becoming more convinced that the people in these forums are right in saying that it's good to try things manually rather than relying on a toolkit. I suggest that you use the toolkit's tutorial to set up your PC with all the right drivers & programs (ADB/Fastboot) so that you're prepared for typing in the commands.
dahawthorne said:
To give you at least some hope have a look at this thread:
http://forum.xda-developers.com/google-nexus-5/help/stuck-launching-flashstock-bat-t3244470
If you've never done any flashing before, I recommend that you install Wugfresh's Nexus Root Toolkit. It can be used to flash a new ROM, but I'm becoming more convinced that the people in these forums are right in saying that it's good to try things manually rather than relying on a toolkit. I suggest that you use the toolkit's tutorial to set up your PC with all the right drivers & programs (ADB/Fastboot) so that you're prepared for typing in the commands.
Click to expand...
Click to collapse
Thanks, I'll have a look at it.
Just to be sure. A factory reset wont work, right?
I don't know - I suppose it's worth trying. But if the phone doesn't turn on, you'll have to go through the PC setup anyway so that you can work on the phone. Besides, it will come in very useful when you need to do any maintenance on the phone in future (if that's what you want).
Or is there a factory reset in stock recovery? I don't use it myself, so I don't know.
CoJonees said:
Thanks, I'll have a look at it.
Just to be sure. A factory reset wont work, right?
Click to expand...
Click to collapse
Wug's toolkit needs a fix. It will not load the new Mashmellow either
Want to learn something instead of using a toolkit to do stuff for you?
1) http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
2) http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Both these threads are unavailable, possibly deleted.
Sent from my Nexus 5 using Tapatalk
beekay201 said:
Want to learn something instead of using a toolkit to do stuff for you?
1) http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
2) http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
@beekay
"Want to learn something instead of using a toolkit to do stuff for you?"
You convinced me, but I think that the NRT has a lot of great help in setting up a PC so that you can actually start learning about ADB/Fastboot manual commands.
Although I'd done some minor fastboot stuff before, I'd never done the full Monty and installed a ROM, but I found the experience strangely pleasurable...
@op found help yet :what::what::what::what:
I've been using Gnabo v_7 version for quite a long time, and a very simple and beautiful day when I woke up my Samsung GT-N8000 was stuck on bootscreen. I wasn't able to do much so I got this "Brazil stock rom" that I found in a website, and it flashed all right, except for the detail that there is something at the screen that I haven't got a bloody clue how to remove. hahaha
And still, whenever I try to install another room, I got stuck at bootlogo and so on. I'm kinda lost here, mind a little help?
I traveled around the forum but well, I'm a little dumb so I couldn't find any proper information about, how to solve this. I would like to know if there is a way to remove this thing from the main screen, and post here the image for you guys to see it please.
I tried to post the image here to make it easier understanding, but since I got this login recently I can't =\
Thanks
Install custom recovery (if you haven't already. If you already have it installed, make sure to update to latest version), root device, wipe everything and flash custom ROM.
DroidTwe4kz said:
Install custom recovery (if you haven't already. If you already have it installed, make sure to update to latest version), root device, wipe everything and flash custom ROM.
Click to expand...
Click to collapse
So far I've tried the rom = N8000XXUDNE4 [still bootloop], then another 4.1 android version of other German rom XXALGA and nothing. Downloaded 3 Brazilian versions, and nothing. [I am from Brazil]. The only one that worked flashing using Odin was one called "KIES_HOME_N8000UBALGA_N8000ZTOALG3_N8000UBLG5.tar". And still, not recognizing my cellphone chip, and with some big watermark at the middle of the screen showing some information about the ROM and the version is 4.0. Even though this one worked fine, I was able to root and when I tried to flash another room, BANG! Bootloop again! =\
I was looking at the forum topics and I read some about ADB or something like that can fix this and "break" this bootloop making the device work normally again with the roms. But i haven't got a clue how to use it. Please help me! =\
vitortakeda said:
So far I've tried the rom = N8000XXUDNE4 [still bootloop], then another 4.1 android version of other German rom XXALGA and nothing. Downloaded 3 Brazilian versions, and nothing. [I am from Brazil]. The only one that worked flashing using Odin was one called "KIES_HOME_N8000UBALGA_N8000ZTOALG3_N8000UBLG5.tar". And still, not recognizing my cellphone chip, and with some big watermark at the middle of the screen showing some information about the ROM and the version is 4.0. Even though this one worked fine, I was able to root and when I tried to flash another room, BANG! Bootloop again! =\
I was looking at the forum topics and I read some about ADB or something like that can fix this and "break" this bootloop making the device work normally again with the roms. But i haven't got a clue how to use it. Please help me! =\
Click to expand...
Click to collapse
You can use ADB to push/pull files to Android. I don't know if you can use it to fix bootloop. With it, you can also reboot to recovery and sideload zip
DroidTwe4kz said:
You can use ADB to push/pull files to Android. I don't know if you can use it to fix bootloop. With it, you can also reboot to recovery and sideload zip
Click to expand...
Click to collapse
Well, after 2 days of research and paying attention on things here, I found out that my problem is "/EFS error". Meaning to use ADB to recover or fix it? But I don't know how to use this. I've downloaded 3GB of it but I was lost about using, and uninstalled. Is is there any short or better version and some good tutorial about using to retrieve my EFS so I can install another roms? I'm using original stock rom now, Brazilian android 4.0 and that's the only only the device is working fine but of course missing things as my cellphone card and the yellow message at the top of the screen. Please guide me through ADB.
P.s Is there a way to create /efs or something like so the device work properly? Cause I've deleted when I installed some rom, and I have no backup here. =\
Thanks!
vitortakeda said:
Well, after 2 days of research and paying attention on things here, I found out that my problem is "/EFS error". Meaning to use ADB to recover or fix it? But I don't know how to use this. I've downloaded 3GB of it but I was lost about using, and uninstalled. Is is there any short or better version and some good tutorial about using to retrieve my EFS so I can install another roms? I'm using original stock rom now, Brazilian android 4.0 and that's the only only the device is working fine but of course missing things as my cellphone card and the yellow message at the top of the screen. Please guide me through ADB.
P.s Is there a way to create /efs or something like so the device work properly? Cause I've deleted when I installed some rom, and I have no backup here. =\
Thanks!
Click to expand...
Click to collapse
Here is tutorial about how to install ADB and Fastboot drivers and use them. Unfortunately, I don't know how to use it to restore efs. Sorry.
Not sure if my phone is a lost cause and only good as a door stop. My phone at one stage would only display a screen asking me to plug into smart switch to recover the phone so I tried that but smart switch wasn't happening. I downloaded the latest stock rom and installed it successfully via ODIN but now my phone will not get past the boot logo. I can only get into download mode, Any advise on if I can get my phone working again?
Thanks
Andrew
andrew88 said:
Not sure if my phone is a lost cause and only good as a door stop. My phone at one stage would only display a screen asking me to plug into smart switch to recover the phone so I tried that but smart switch wasn't happening. I downloaded the latest stock rom and installed it successfully via ODIN but now my phone will not get past the boot logo. I can only get into download mode, Any advise on if I can get my phone working again?
Thanks
Andrew
Click to expand...
Click to collapse
Bro, I've been there and this is why I made an account on xda to see if my s6 (G-920F) can be fixed in any way. Yesterday I had the same thing as you when I tried to re-flash the phone with its proper, latest stock-ROM (UK/EE Nougat 7.0). Given how it hadn't worked, the update attempt through Odin screaming a big "FAIL!" at me, I was afraid I had bricked it completely, so I proceeded to re-install TWRP with Odin by putting the phone in download mode. I wiped the phone again with TWRP and now I'm not sure what I have to do as I am stuck with the UK Nougat bootloader and nothing else on it.
Before this whole ordeal I had rooted the phone and unlocked the bootloader following some instructions from a Youtube video and successfully installed a nighty build of LineageOS, which was buggy as **** (couldn't answer calls, use data, use the camera and a ****ton of apps were just not working). Dumbly enough, I thought I could just remove it through a wipe and put something else back on it but oh was I wrong.
Right now I'd just want to get my phone back to working (like you), as I am out of a job and need to be able to take phone calls with a normal, working phone.
Sorry I couldn't be of much help, but yeah maybe a first step towards fixing it would be to flash TWRP recovery on it and through the terminal, see what bootloader version you have with the command "getprop ro.bootloader". At least you will know the version of the broken bootloader you're experiencing difficulties with and *hopefully* an actual dev from the forums will entertain themselves in trying to solve this noobish puzzle we've created for ourselves.
Seriously, if there is a dev ready to board this crazy adventure with us, please help.
My namesake or username is pretty much a clue to what got me into this position.
I wish it was that simple for me mate, I cant access the recovery menu, I've tried flashing various recovery options but cant boot into any of them. I'm certain I could fix the phone if I could get to recovery. I'm now leaning towards it being a hardware fault with my phone. As you have access to recovery I think you may have more luck with your phone.
TerribleChoices said:
Bro, I've been there and this is why I made an account on xda to see if my s6 (G-920F) can be fixed in any way. Yesterday I had the same thing as you when I tried to re-flash the phone with its proper, latest stock-ROM (UK/EE Nougat 7.0). Given how it hadn't worked, the update attempt through Odin screaming a big "FAIL!" at me, I was afraid I had bricked it completely, so I proceeded to re-install TWRP with Odin by putting the phone in download mode. I wiped the phone again with TWRP and now I'm not sure what I have to do as I am stuck with the UK Nougat bootloader and nothing else on it.
Before this whole ordeal I had rooted the phone and unlocked the bootloader following some instructions from a Youtube video and successfully installed a nighty build of LineageOS, which was buggy as **** (couldn't answer calls, use data, use the camera and a ****ton of apps were just not working). Dumbly enough, I thought I could just remove it through a wipe and put something else back on it but oh was I wrong.
Right now I'd just want to get my phone back to working (like you), as I am out of a job and need to be able to take phone calls with a normal, working phone.
Sorry I couldn't be of much help, but yeah maybe a first step towards fixing it would be to flash TWRP recovery on it and through the terminal, see what bootloader version you have with the command "getprop ro.bootloader". At least you will know the version of the broken bootloader you're experiencing difficulties with and *hopefully* an actual dev from the forums will entertain themselves in trying to solve this noobish puzzle we've created for ourselves.
Seriously, if there is a dev ready to board this crazy adventure with us, please help.
My namesake or username is pretty much a clue to what got me into this position.
Click to expand...
Click to collapse
andrew88 said:
I wish it was that simple for me mate, I cant access the recovery menu, I've tried flashing various recovery options but cant boot into any of them. I'm certain I could fix the phone if I could get to recovery. I'm now leaning towards it being a hardware fault with my phone. As you have access to recovery I think you may have more luck with your phone.
Click to expand...
Click to collapse
Oh dear.
Yeah it does sound like something got deeply ****ed up in this case. I had the luck to somehow get past the smart switch error when the phone died of low battery. As I attached it to the charger I quickly boot it into download mode before the screen would become a bootloop again and that's where I was able to reinstall the latest version of TWRP recovery. After that, I was able to flash a stock ROM of Nougat that didn't have a ****ed up bootloader like I had. Specifically the one from this thread: https://forum.xda-developers.com/galaxy-s6/help/device-5-binary-3-s6-sm-g920f-t3706025
by forumber2.
It's the Netherlands stock-ROM. Not sure if you're from the US and the carrier would be wrong with that CSC, but it was a good bet for me. I got my phone back to working normally now.
Worst case scenario I'd say see if you have a phone repair shop nearby and ask them an opinion on what could be wrong. I'm just an amateur like you.
Still, I wish you the best of luck with it. Maybe there's still some hope. :/