Need desperate help with a MediaTek clone of S4
Hi everyone,
I will try and keep it short but last night I was badly scammed by a wonderful specimen of the human race, who wanted to sell his old Samsung S4. Turns out:
1. Its a mediatek clone
2. It has more issues than anticipated but all buttons work.
3. Seem to be soft bricked
Now I am facing nothing but patience to try and fix it. What works:
1. All buttons seem functional.
2. The phone boots into normal mode where I have only empty screen with a Phone app. The Phone app opens I can enter digits but cannot dial.
3. I can reboot into Factory mode - I performed all the tests of the device and all were a PASS. I heard the sounds, checked the cam, everything seems to be perfectly working. Touch scree, camera, sound etc. Even noticed it had FM.
I tried booting in Download Mode - no success. I get the dead Android image and it just hangs there. I can easy reboot though.
My PC recognizes the device and opens a media (empty) device folder.
I tried thus far to use SP Flash but....I dont know how to. Nothing is happening.
Of course I spent 6 hours waiting on different stock ROMs for S4 before realizing its a MediaTek device.
And now, here I am desperately asking if anyone could help me, if there is a chance to remedy that situation of mine. I dont need the phone to do anything special. The closer it is to a Samsung Android ROM - awesome. If its other, I dont mind at all. So long as it works and has access to Google Play Store.
Thank you geniuses and wonderful people for any hint you might have.
Hi
I had a similar issue couple of yrs ago with an S3 clone.
First thing u need to knw is the mtk version, memory details (RAM & ROM) and screen resolution to find a suitable OS version.
If ur lucky, ull get the stock ROM from the manufacturer on Google or else ull hafta search on xda, needrom, or the Chinese forums. Most of such devices don't have a lot of development so ull hafta port ROMs so a custom recovery will b helpful
Hope these points help
Sent from my YU5510 using Tapatalk
Ok.
So I need:
Device RAM
Device ROM
Mtk Version
I think I can extract these from the Factory Mode. Will check.
Then I need to get the stock ROM (hopefully) or search for a custom ROM. (Manufacturer I suppose we talk about MediaTek and not Samsung?)
Custom Recovery - yeah, usually this is the first thing I install but how do I do this on a cloned mtk? I suppose ODIN wont work. Can you lastly point me to a link or name of software to use instead of ODIN? (or will it work with ODIN?)
Related
Hey guys,
I really need to find at least the stock ROM for the new-ish Blu Advance 4.0L (model A010U), because the most recent OTA update unforgivingly bricked mine. Now I want to try to re-flash the stock ROM, but I am also open to custom ROMs, if there are any available. Please help me out! Thanks in advance
I am really surprised no one has replied yet, but again I am facing the same problem and I've been searching the Internet for one month now and I found absolutely nothing for this phone (specifically for version A010U).
So I am going to post a different question in the hopes that someone will read it and help us out:
I have two Blu Advance 4.0 L A010U phones, which are identical except for the color (white and green). They were manufactured a month apart one in 10/2015 and one in 9/2015.
Unfortunately after only a couple of months of light use and for no apparent reason (did not drop it, or wet it, etc) it started going through a boot loop. It will start, show the "bold like us" logo then restart again without making it to the operating system at all. Like I said I've been looking for over a month to find a ROM (stock or modded) to reflash but with no luck. Then I had an idea. Since I have the other identical phone that's working fine, is there a trick I can do using the working phone to create a ROM that I can use in my broken one. By the way, the non working phone will allow me to get into the recovery menu, but unfortunately nothing happens if I wipe the cache or even if I reset to factory defaults.
Anyone knows what's causing that "boot loop", how to fix it and where to find a ROM or even "extract" or "create" one using a working Advance 4.0 L ???
Thank you very much!
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Deuler93 said:
Hey guys,
I really need to find at least the stock ROM for the new-ish Blu Advance 4.0L (model A010U), because the most recent OTA update unforgivingly bricked mine. Now I want to try to re-flash the stock ROM, but I am also open to custom ROMs, if there are any available. Please help me out! Thanks in advance
Click to expand...
Click to collapse
I just got ahold of a couple of these devices myself and am in the process of going through all the in's and out's of them....I'm a Samsung nerd so I haven't messed with something like these in a while but I got one (that was supposedly dead bricked per the lady friend of mine I got them from) at least able to boot into factory mode and recovery via ADB and just as I'm posting this I'm in adb shell going through the device's internal memory.....so we'll see what all I find and can pull out of this one and possibly know enough to post an intelligible reply with solutions next time
The boot looping sounds like a common problem with these and when I get to that point I'm going to get rid of the stock bootanimation.zip ASAP and try something else. I get the idea that these things aren't exactly power houses built for much so the littlest thing or small bug in their coding could lead to this kind of crap happening.
Hopefully you figure yours out before I toss these out the window! lol
Cheers y salud!
---------- Post added at 02:27 AM ---------- Previous post was at 02:20 AM ----------
good.m. said:
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Click to expand...
Click to collapse
Forgot to add a couple things about your post, sorry! I beleive (and I just started digging into this phone) that the no command part is the locked bootloader these phones appear to have. I think it was a combo of holding both volume buttons down from a powered off state then pressing power button on that came up with the option for factory mode or recovery (which led to the sad 'no command' droid), i went into factory mode and theres an option for Tp Upgrade which Im assuming is F/W or something similar but I just hooked up to the PC and in that mode it's reading the internal and external memory of the phone and that's about where I'm at so far.
Wow! I'm surprised this thread is still going.
Anywho, I found a repository that is storing the default ROM for the 4.0L. The files were just added recently. I would have liked to have seen a custom Lollipop ROM made by now, but this device is far too irrelevant to get any attention, unfortunately. Just root and forget, I guess.
I can't wait to try it, thank you! And btw, were you able to get root successfully and if so, how?
Deuler93 said:
Wow! I'm surprised this thread is still going.
Anywho, I found a repository that is storing the default ROM for the 4.0L. The files were just added recently. I would have liked to have seen a custom Lollipop ROM made by now, but this device is far too irrelevant to get any attention, unfortunately. Just root and forget, I guess.
Click to expand...
Click to collapse
Hey Deuler93 -
You have my respect for digging out that BLU ROMs link and sharing with the rest of us. I downloaded the one for my Advance and used SP flash tool to flash the phone that was stuck on a boot-loop. Of course first I had to download and install the MediaTeK drivers for USB connectivity with my PC. Everything worked flawlessly, no glitches what so ever. All these links are easily found and widely available online if anyone is interested I can share here too. I just hope that this boot-loop was due to some software glitch and not hardware failure. Everything seems to work fine for now, keepint my fingers crossed it will NOT happen again.
Well, one less headache to worry about. By the way we're not that far, if you're ever in the Chicago area, I owe you a beer or something. Thank you!
Hi guys !
Thank you very much for the Advance 4.0L Roms.
I have successfuly recovered my phone, but the IMEI got lost.
So, I need to root it in order to recover the IMEI, but I just can´t get success on any method :
Kingroot
Framaroot
Towelroot
is there another way to root it ?
Thank you very much.
I got temporary root using the kingroot apk. But it messed things up and I don't trust it anymore. None of the other mentioned methods worked for me either, maybe try the PC kingroot method
well this helps one thing
good.m. said:
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Click to expand...
Click to collapse
umm. . . when the no command option comes up just press the power button and the rest of options will appear. doesnt exactly solve your problem however unless you have the ZIP file to install, which is what I'm looking for.
What might happen if a ROM is used for another blu phone. ??
A similar phone as well.
Plz advise.
Damn! This thread just keeps going!
I haven't even looked here in a while, so I will bunch my commentary here. I'm also salaried now, so I bought into a OnePlus X (onyx), a more expensive cheapo device, so I do not use the 4.0L anymore.
As for rooting tools, I used the Kingroot APK successfully in the stock environment. I never tried flashing something SuperSU myself, but it could work. Is flashing a SU app possible from the fastboot interface?
And to Steve's question - it is technically possible to flash a ROM for a different device onto your own device, but is considered a bad idea due to the possibility of introducing incompatibilities and missing proprietary requirements. I feel like this would hold especially true to stock ROMs because the manufacturer probably has no interest in supporting anything more than the device that they are manufacturing for. Doing so removes many possible "compatibility" issues from even having to be considered, but I digress. In short, try to find a ROM made for your device and your device only.
Did you find the zip file for the recovery
Marya Wynter said:
umm. . . when the no command option comes up just press the power button and the rest of options will appear. doesnt exactly solve your problem however unless you have the ZIP file to install, which is what I'm looking for.
Click to expand...
Click to collapse
i root my blu advance 4.0l a010u with the kingoroot PC apk, but i got some issues with the lock screen and some apps, so, i need some advice..
i was looking for a zip to use it via recovery but i can't find any..
Recover IMEI
srspinho said:
Hi guys !
Thank you very much for the Advance 4.0L Roms.
I have successfuly recovered my phone, but the IMEI got lost.
So, I need to root it in order to recover the IMEI, but I just can´t get success on any method :
Kingroot
Framaroot
Towelroot
is there another way to root it ?
Thank you very much.
Click to expand...
Click to collapse
You dont need root to recover imei all you have to do is type *#*#84666364#*#* in your dialer and you will be entered in EngineerMode then go into connectivity ,CDS information and radio information phone 1 or 2 then you will see AT+ type something eg.A then backspace and select the first thing you see. Put a space after AT+ and then put you imei code here "IMEI" between these "" You can find your imei by removing your battery it willl be there. After sending command reboot and imei is back.
links are down....check this instead
Hey guys, links here seems to be down .
Maybe this link would be useful for you all... stock firmware can be downloaded and useful help on videos is available too... Enjoy
Good day my friends. This is my first post but i read these forums very often. I own a Digicel Dl750 (alcatel 4037a) which i would really appreciate some help with. I tried to flash my phone some time ago using a tutorial i found online since i couldn't find anything useful here (my go to source for these things). However, after trying to flash the rom and failing, i am stuck with a phone that won't respond to any input. COnnecting it with a usb simply gives me a white light on the phone, and device manager reads a "MTK usb port" device. it won't boot or anything else. Been trying to install some kind of recovery but i've had no luck so far. Is anyone here able to provide me with a backup of a working phone so i can fix mine please.
Edit Note1: After a bit more testing, I have pretty much confirmed that it is a problem with the preloader as the phone seems to completely skip the preloader when you connect it to the pc, and after a few seconds goes to the bootrom(?) instead. I am making this call based on the hardware ids show in device manager.
#BUMP I also need a stock firmware for the DL750 4037A
kingofkrunck said:
#BUMP I also need a stock firmware for the DL750 4037A
Click to expand...
Click to collapse
Well i was able to get an OSP dump which solved my problem. Not sure it would be of use to you though
Where can I get this dump at Denis?
Hey guys,
sorry if my english isn't right but I am so tired so now and so frustrated that I don't know what I could do.
The story is simple: I have a android head unit, running allwinner t3 (aka R40) with stock rom and stock recovery.
So far, there isn't any custom recovery available (I would like to create/compile CWM but CWM-Builder have some 502 Bad Gateways...) and the only way to root on 4.4.2 is with 360Root (On 6.0.1 for the newer Models only with Kingroot).
So far not bad but it takes a lot of patience sometimes and sometimes you can try over 1 week every day many hours and it still don't work!
So where do I need help? I want to add Root/SuperSU/... manually but I have many limitation.
First one is that I can only modify the system.img without any chmod and else (Maybe because I am using windows? Maybe because the Firmware has to be flashed while the Head Unit is powered off aka "Dead flash")
Secondly, ADB is not working, to be honest, the head unit act only as a receiver! It accepts any devices like Keyboard, UMTS/WCDMA Stick, USB Stick, ... but MTP fom HeadUnit or ADB, ... don't work. The only way for ADB is ADB over Wifi but I don't know whether it's good or bad. I saw that the USB is plugged into a slot which seems to be bend out, maybe they plugged it in wrong? I don't know how I can test that but I heard that connecting two devices with wrong polarity will break at least one of them!
Thirdly is, that I can't notice a difference between a rooted stock rom and a unrooted stock rom.
According to WinMerge, the rooted ROM have two new files (/etc/install-recovery.sh and /bin/su) but that's it!
If I transfer those files to my custom ROM with the same rooting app, it wont recognize them! I can try and try until I die.
And last, maybe worst, I can't just update something over. Every change outside the Android OS is mainly done by flashing the whole firmware! They changed that policy a little bit after Android 6.0.1 but this Android have the worst stability, worst GPS Modules and completely bricked Bluetooth! Also the stock recovery on 4.4.2 is useless, touch isn't working and the touch-buttons are also not working. I also tried to use a usb keyboard but also useless. Only the 6.0.1 stock recovery recognizes the touch screen and the touch-buttons but as I said, the Android 6 is terribly made...
I know what it sound like a noob and I didn't provided much information but I want to know whether someone can help me or want to help me... maybe someone say that I have to provide information xyz so yeah, feel free to ask
Best regards
Pascal
At what point did you install the ADB device drivers (kinda important) for your device, so that when you plugged it into anything, the thing could register you were plugging in the HeadUnit......
I've been trying to figure this out for a while, and I have made some headway but I think I need to make custom build. If anyone could point me in a direction, it would be super helpful. I have a few ELO ESY15i1 android computers. They are EOL now, and only supported up to kitkat. ELO does not release their kernel source, but I do have their peripherals.
This is how far I have got with this thing, and what I was able to do/determine.
After a bunch of digging, I'm pretty sure that this thing is just a modified S4 i9505. Hardware specs seem to match, outside of the CPU only being 1.7 instead of 1.9ghz. I'm *assuming* that they have down clocked it maybe? The first unit I was working with, apparently had a bricked recovery (had bough it 2nd hand). I was able to boot it into TWRP using the jfltexx image, but I would get no picture. I know it was booted because I could access TWRP via cmd, and it was giving me responses back.
I was able to root it in a very round about way. Since I do not have any volume buttons, I'm limited to adb etc. I was able to root it with iRoot, convert that to supersu, and eventually get flashfire to install. I could finally access almost everything I needed. At some point, I got it stuck in a mode where "QHUSB_DLOAD" was shown to me, with a folder called "image" which I took a copy of. Any google results with that, was just people who had bricked their device, I was able to boot in and out of this, so I'm not sure what was going on or broken.
Here is what the device props listed out: hXXps://pastebin.XXX/FtgQ0DUE
This is the mobilodin report: hXXps://pastebin.XXX/BZrDAFg4
Finally, the "image" I copied: hXXps://anonfiles.XXX/lcQ7RfJ8o0/ESY15i1-image_rar
(sorry can't post links)
The first unit I was working on, I gave to a buddy to mess around with. The 2nd one I have, I have now bricked and it is officially stuck in the "QHUSB_DLOAD" mode. I made a poor choice, and modified the i9505 "updater-script" in lineage-17.1-20200723-nightly-jfltexx-signed to include my "msm8960" device. I flashed it via FlashFire which did go through, just bricked me in the process.
I had a samsung download jig, but I can't find it anywhere, so I have a new one on order. I'm too lazy to cut up a micro usb plug and make one. I have yet to get odin to recognize it at all, or get it into download mode. When I try over adb, it will reboot, try to go in some mode, then reboot again back to the rom.
Any input / help would be greatly appreciated. These machines are super cheap on ebay, the only problem is being stuck on kitkat. I can think of loads of things to use these for, doesn't look like anyone has tried to do anything with them. From all my searching I just found one guy who was trying to root one, and that was about it.
Hi,
I have one 22 inch unit, which I'd like to use with monitoring system and some else, but I need android version with multi windows support, so I'd like to ask you if you succeed with installing new ROM ?
Thanks in advance for reply
Maciek
Well, I've been dinking around with it again, I think I have the HW figured out. I'm pretty sure it's an LG Optimus G, LGE970 is what I'm trying.
I was able to take the stock "ATT-Stock-E97020j" non KDZ zip, pull the boot.img off of it, and flash that.
Now when I connect to my computer, I'm getting LGE Androidnet for Diagnostics, and LGE Androidnet USB serial, as 2 devices.
Just keeps hanging right away when I try and flash the KDZ.
Didn't know where to post this exactly, to be honest. This will be a long post
I was flashing AOSP roms in the phone. Tried to go back to One UI for the VoLTE thing
In one of the AOSP roms I couldn't install it in Lineage Recovery (older version of the rom thing). I saw i one post that doing an ADB Sideload in TWRP could solve the flashing problem. Did that. No issues
Wanted to test another AOSP rom but didn't boot (bootloop), so then I tried to go back to One UI. Don't remember if I did a format data in that moment.
After installing the rom and reboot to system, the phone doesn't even show the splash screen.
But tried to go to download mode and it went there, so the phone is still alive
Tried also going to recovery and it boots there (just to recovery and download mode)
I tried everything I could:
Flashed another custom ROM without success
Flashed other AOSP roms again
Changed the recovery (Lineage, TWRP and Stock tested)
Flashed the stock firmware through Odin several times
Tried to do a re-partition in Odin
Did several factory resets
Nothing seems to work. The weird thing is that, with any rom that I try to install, it tells that is installed, but when I go to the file manager in TWRP, it doesn't install anything. The free space before the installation is the same as after it. I don't know what else I can do. I just have the hope because the phone starts in BL and recovery
Anyone have any idea of what can I do to solve this? Or if there is a way to install the OS outside Odin or recovery (or ADB)
Tried with fastboot (Lineage Recovery) with several commands, and I think I found the issue. The system partition got corrupted. Need to know how to repair it (tried already with the repair option in TWRP)
Any help with this?
https://forum.xda-developers.com/t/...sh-stock-firmware-in-samsung-devices.4452839/
Read it carefully ( retrieve the original PIT file part)
Let me test it and will give feedback
lngl said:
https://forum.xda-developers.com/t/...sh-stock-firmware-in-samsung-devices.4452839/
Read it carefully ( retrieve the original PIT file part)
Click to expand...
Click to collapse
Didn't work out. Same issue
It's so stressful because it boots to the other things, but not to the system
Good afternoon faithful and unfaithful
Unfaithful Redspikejr
The barbarian from Pakonan has no idea about this but in your case he would do the following since I have had your problems and it was resolved positively.
I'm going to try to help you, I don't know English and I use a translator, I hope it's good to understand each other. Luck
First option
1 I want you to put through odin in AP twrp-3.6.0_9-2-d2s_official_jan22.tar unchecking auto reboot
2 in twrp delete data and say YES restart in twrp again and try to install PixelExperience_d2s-12.1-20220522-1749-OFFICIAL. I understand you will have it on the SD, if not, put the ROM on a USB key and try to install it in TWRP.
If you manage to install it, then install magisk apk and restart the system.
3 once started install magisk apk and ready.
Second option
1 I want you to put through odin in AP twrp-3.6.0_9-2-d2s_official_jan22.tar unchecking auto reboot
2 in twrp delete data and say YES reboot in twrp again and install the Recovery lineage.img and reboot in Recovery lineage and Factory reset & reset system partitions
3 Install the PixelExperience_d2s-12.1-20220522-1749-OFFICIAL. I understand you will have it on the SD, if not, put the ROM on a USB key and install from there. turn off the phone and
4 in download mode odin AP twrp-3.6.0_9-2-d2s_official_jan22.tar unchecking auto reboot reboot into TWRP
5 Install Magisk apk and reboot system.
once started install magisk apk and ready.
remember to have the cable plugged in to enter TWRP and download while you are following the steps. Good luck, you will say.
Salu2 of your most faithful infidel Pako
To update the situation
The battery of the phone in inflated like a balloon. I don't know for sure if that was caused by something physical, but will update when have some news
i still have the same problem and still hunger for a solution because i just bought it .. Been running quite a few firmwares now. and bootloaders and kernels and recoverys so far... but whats funny is in pixel recovery it said i had a "d2x" model which is SM-N976 model with 5G... But every elsewhere it says d2s which is note10+. Odin also says SM-N975F model... But anyways... I really really hope someone finds a solution. Because im stuck as hell...
I also made a thread my self
Partly bricked... SM-N975F
Hey guys.. Ive been a visitor in XDA forums for quite a while... And i been running root and custom FW with more or less every samsung from S2 and up... But i just got my self a note10+ (atleast thats what ive been told) and i wanted to root it...
forum.xda-developers.com
And i think its VBMETA problem. BUT i dont have any experience on that term...
Crossing fingers still...
I might have found a solution
Holy Hell, Im am so glad im not the only one that this is happened to. I will be more happy when we find a solution. I have put myself (device) in some questionable states but this has been a first and strange one for me . Its like being so close to booting into system then nothing.
AmercianPM said:
Holy Hell, Im am so glad im not the only one that this is happened to. I will be more happy when we find a solution. I have put myself (device) in some questionable states but this has been a first and strange one for me . Its like being so close to booting into system then nothing.
Click to expand...
Click to collapse
Android Verified Boot 2.0
I found this link this morning. Im sure this is the culprit.
I experienced today something like you. It did not let me flash even stock firmware. But I succeeded to get out. I flased via ODIN BL slot from Dr.Ketan and in AP slot TWRP and nothing else. And I managed to enter the TWRP recovery and from there I restored previous backup.
I will try to do a multipost due to more threads and problems which are the same...
But this is the solution...
In my folder on the picture you will see 2 files i marked with green color...
Use the file and burn it according to your current setup. Odin or custom recovery.
And the problem will be solved. Used 14 days and countless of hours to get out of this boot loop!
So im finally happy to see the boot up screen without pressing into download mode or recovery mode...
The folder on the picture is to be found on this forum... Just cant remember from which thread exackly
GL
Titanity said:
View attachment 5656047
I will try to do a multipost due to more threads and problems which are the same...
But this is the solution...
In my folder on the picture you will see 2 files i marked with green color...
Use the file and burn it according to your current setup. Odin or custom recovery.
And the problem will be solved. Used 14 days and countless of hours to get out of this boot loop!
So im finally happy to see the boot up screen without pressing into download mode or recovery mode...
The folder on the picture is to be found on this forum... Just cant remember from which thread exackly
GL
Click to expand...
Click to collapse
Bless you. My poor phone was down since 6-20. I was just kicking myself in the ass the other day saying if I got my phone to boot again i would never flash **** it on it ever again... @Titanity thank you so much for making me look like a liar. Now lets see what else we can do lol.
So you got it to work? And whats up next?
Titanity said:
So you got it to work? And whats up next?
Click to expand...
Click to collapse
Yes it did. I have gotten myself in some pretty bleak spots in the past and have been able to resolve all my issues on my own research, troubleshooting, trial and error etc. but I had never had a device that was actually able to power on, flash twrp, stockfirmware pass in odin, tried all type of pit file patches, adb and fastboot commands and still not be able to get into OS completely stumped me and I had exhausted so much time on it that i came to the conclusion that one of the talented members of XDA would for sure come up with a solution and I was right.
Sorry for the blabber, Ive been just a watcher of this site for many years and have never had to engage so my apologies for my forum etiquette.
I main focus now is to find a good rom to run with nethunter. I was running Dr. ketan Rom with nethunter while installing every LSposed Module that sounded cool and was beyond impressed by how stable my device still performed (one of my largest TWRP backups was 49Gb btw.) So yea, look for something with a strong kernal, light rom to see what I like. I have yet to try the new roms out due to unfamiliar processes of installing outside of Odin. Its been a while since I had some free time tinker in this space again.
Yea im just a watcher my self... it took me a few days until i decided to make this solution. Because i do think it was a important solution i found. But yes im just a watcher my self...
Now im stuck again though because i have a faulty usb-c, so its claming theres water inthe entrance which there isnt. And i been looking all over the forums for a solution like 3 times now. And people are just trying to trick the fault or acturally have a solution... But thats only IF they have water inside and the stupid alarm goes off...
Instead i need a solution to disable it now that its rooted. So need to know exackly what to look for and theres no help to get here. So kinda stuck... Irritating because i just wanna use it for dex... And not dex wiesless because its lagging on the mouse and what not... So my adapter need the recharge entrance and ... doh! Long journey so far... And its far from ended...
But im very happy it worked out for you... Keep in touch if you need another silly question. Then i might have silly questions for you aswell Good day my friend
@Titanity Bless your heart, I need your help . I broke my friends phone which is a note 10 plus, and all that you guys mentioned about trying everything I did as well.. I read your solution but I dont know where to find the files you marked and how to go about them exactly... the phone is currently on stock recovery and is stuck there.
Okay do you have a option to use a mic and the software discord? i do belive its easier for both of us if we can do this with direct communication. If you dont want to use / have a mic. Then its also fine. Discord got a chat aswell so dont be shy I have my own discord which is:
Join the thetitanity @ twitch.tv Discord Server!
Check out the thetitanity @ twitch.tv community on Discord - hang outwith 17 other members and enjoy free voice and text chat.
discord.gg
Ill pop op now and then, but im not a streamer anymore on twitch. So dont be mistaken by the server info...
Look forward to see you on there. And ill make sure to have the files ready for you
Until then haha
EDIT: I just uploaded a package filled with "i help you in case of emergency" files. Make sure to download it before entering discord. Get it at...
https://easyupload.io/xwlk0w - and the PW is: titanity (30 days avalible)
Also have info ready like: is the model a 975F or? what firmware is on it at the moment. Is the bootloader unlocked. But also things like do you ever used TWRP before and know how to use it etc?
Its a package filled with files of my choice, but made by people from the forum. So no credit goes to me but them...
Have in mind that all the time i been on the forum i always just read the forum and downloaded when needed, so its the first time im trying to help others... But im optimistic!
Titanity said:
Okay do you have a option to use a mic and the software discord? i do belive its easier for both of us if we can do this with direct communication. If you dont want to use / have a mic. Then its also fine. Discord got a chat aswell so dont be shy I have my own discord which is:
Join the thetitanity @ twitch.tv Discord Server!
Check out the thetitanity @ twitch.tv community on Discord - hang outwith 17 other members and enjoy free voice and text chat.
discord.gg
Ill pop op now and then, but im not a streamer anymore on twitch. So dont be mistaken by the server info...
Look forward to see you on there. And ill make sure to have the files ready for you
Until then haha
EDIT: I just uploaded a package filled with "i help you in case of emergency" files. Make sure to download it before entering discord. Get it at...
https://easyupload.io/xwlk0w - and the PW is: titanity (30 days avalible)
Also have info ready like: is the model a 975F or? what firmware is on it at the moment. Is the bootloader unlocked. But also things like do you ever used TWRP before and know how to use it etc?
Its a package filled with files of my choice, but made by people from the forum. So no credit goes to me but them...
Have in mind that all the time i been on the forum i always just read the forum and downloaded when needed, so its the first time im trying to help others... But im optimistic!
Click to expand...
Click to collapse
@Titanity bro that's so generous of you, alright.. downloading and will join discord then , Thanks dude