please help me I have been trying solutions for 2 months but nothing works. I also tried to do
1 go to wipe
2 go to advanced wipe
3 select date
4 repair or change flie system
5 change flile system ext 2
6 then replace ext 4
but it does not work. when i try to boot in to the system it goes into an infinite loading screen. please HELP (I used google translator because my english sucks)
@Boyko99
Either boot-loader broken or Android system corrupted. Re-flash Stock ROM.
I don't know if my answer came to you so I'll rewrite it
jwoegerbauer said:
@Boyko99
Either boot-loader broken or Android system corrupted. Re-flash Stock ROM.
Click to expand...
Click to collapse
could you tell me how to find the Stock ROM. I need help because I'm not very practical in modding
Boyko99 said:
could you tell me how to find the Stock ROM.
Click to expand...
Click to collapse
GIYF ...
i downloaded this now what should i do? and with what program?
jwoegerbauer said:
GIYF ...
Click to expand...
Click to collapse
i downloaded this now what should i do? and with what program?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@Boyko99
Because you avoided to name phone's brand/model in this thread's title you can't really get advised.
Anyway:
Assumed these requirements
got fulfilled, the USB-driver suitable to your phone is installed on PC,
then the basic steps to perform are
1) Unlock phone's boot-loader, if not done yet
2) flash the ROM
@jwoegerbauer
I can't start the phone so I don't know how to do it I'm stuck in twrp because if I try to turn it on it goes into a loop
@Boyko99
My POV:
This is the price that people who think they must improve (?) phone's Android, will say put up a better (?) ROM / Recovery than that what gets pre-installed by OEM/Carrier ( in their R&D department there are certainly no idiots sitting around ), pay.
@jwoegerbauer
i have a note 3 its the worts rom of all
Related
please anybody help me i need the firmware files for a hard bricked iphone 5s clone with MT6571 chipset.
unfortunately i got the phone in such a condition that it was not booting up but i could still open the factory mode and from there i found that the chipset is MT6571 but could not get much info. as the factory mode was in chinees language. I got a snap of the factory mode and here's the dropbox link of snap:
https://www.dropbox.com/s/hm5b8zdup9emuf3/IMG_5s-Clone.jpg?dl=0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
please help me with the flash files..
thank you
plz help me if anybody can
plz give me a link to the above mentioned flash files
sujeet27yadav said:
plz help me if anybody can
plz give me a link to the above mentioned flash files
Click to expand...
Click to collapse
If you have not had any replies, then I'm afraid its for several reasons.
You can't get "flash" files for mediatek chips set phones, they simply do not exist anywhere.
You can only "flash" something on a device that has the architecture to allow flashing (ie a Qualcomm) I'm pretty sure you need to build your own twrp/clockwork mod recovery yourself for your pacific device.
Mediatek chipset devices are notoriously difficult to mod in anyway, and always the easiest to brick.
I'm no expert but you really need to have someone explain this to you, your phone is bricked and there is no way to recover it.
Its the very reason after having two of these very cheap Chinese clone phones that both went wrong after only a few months I will never purchase such a device again, even after one came to me pre rooted and with CWM installed, that did not stop it going horribly wrong after 6 weeks usage.
My only advice to you is to google the make/brand along with the model number firmware(for example this is how I did it)
Example-Epade S90 (NEO N002) 4.5 firmware
But its doubtful you would be able to flash anything as you won't have any working recovery, and most of the website for these firmwares will be in Chinese.
This is my own experience, not something I have read, someone with a lot more knowledge than me needs to explain this to you in a way you may understand more than I can explain.
Sent from my XT1524 using XDA-Developers mobile app
Hey,
I recently got a cheap, slightly used chinese version Nokia N1. But because without the Google Services its pretty much useless to me, I want to root it and install a custom ROM.
I followed 2 tutorials:
https://forum.xda-developers.com/nokia-n1/help/nokia-n1-root-t3125771
and
https://forum.xda-developers.com/nokia-n1/general/play-store-howto-t3118965
But I always get stuck on the part with the Recovery Launcher.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To give some background, here are the steps I did:
Because fastboot and the launcher won't see my device if its in MTP or PTP, I disabled both. That seems to work fine.
I "unlocked" oem in the developer settings and also allowed USB debugging.
I started the Recovery Launcher with admin privileges and used option T4.
It boots into recovery mode, but I just get errors all over the place bacause the device is still locked. So i just typed "fastboot oem unlock". Then T4 again.
Thats where this error occurs. From what I read, this should put me into a CWM recovery session. But it doesn't. It just stays in the fastboot mode window.
I'm pretty new to this android modding thing, so don't expect to much knowledge from me.
with much thanks
~David
Bump
I really hope bumps are allowed here
its seems from ur bootloader, try to re unlock with fastboot unlock oem. if you done try different recovery developed for ur devices.
nuzzydev said:
its seems from ur bootloader, try to re unlock with fastboot unlock oem. if you done try different recovery developed for ur devices.
Click to expand...
Click to collapse
The thing is, there are no other solutions out there I really know about. I searched google up and down and got no real result.
I think my problem is that my android version isn't 5.0.x, like almost every english tutorial suggests. It is 5.1.1.
oh God... my fault sorry
Hello
I am complete new to the "custom ROM for mobile phones" business.
But i am familiar with Linux based Satellite Receivers where you
also can flash custom ROMS to enhance the functionality.
Or in other words - i know what bricked means.
Anyway what i have done so far:
I have an unlocked Bootloader on my Mi A3.
1st time (non permanent) flash of TWRP-3.3.1-2 into recovery for
a full backup of my phone to Sd-Card.
An encounter with Bootloop made
Now i want to make TWRP permament on both partitions.
But, after flashing TWRP into recovery again, i recognizing that
the "Unmodified System Partition" screen is not apearing anymore.
After my 1st twrp flash, twrp showed me a screen where something
about "Keep System Read only" was explained.
With a slider "Swipe to Allow Modifications".
This screen is not more apearing anymore.
Is this mandatory to go on ?
My goal is to have twrp, magisk and lineageos on my phone.
Last but not least i want to say:
A fantastic source of informations here but overwhelming btw. *g*
* Edit *
32 Views but no answers this could mean that my concern is not clear ?
After entering to twrp on my phone for the first time i saw this screen here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As i explained above, i only wanted to make a backup from my phone
as a fallback if something goes wrong afterwards.
Due to this i pressed ´Keep Read Only´
Don´t know if the ´Never show this...´ was flaged
My thoughts was:
Keep Read Only is okay for now/backup.
And if necessary i can Swipe for modification next time.
My concern is the screen will not showing again.
In case of i HAVE to swipe to make modifications for the next steps,
what i have to do now that this screen will show up again
that i can make the f*ckn swipe ? :angel:
Thank you
Open twrp, goto mount, there's an option for mount read-only system.
m.h.mahadi said:
Open twrp, goto mount, there's an option for mount read-only system.
Click to expand...
Click to collapse
Thank you.
Hi everyone, I have the Ulefone Armor X5 2020 version (android 10)with the mt6762 mediatek processor ( description of the seller, the ticket on the box and Ulefone description) this is very confuse why the stock rom for this device is for mt6765 and I read mt6765 with sp flash software.
My problem is what this was bricked from factory, its work unstable and rebooting ramdomly.
I try many things like factory reset, wipe the cache, (when wipe the cache the display show E: Fota installation aborted, E:: No such file or diretory) reflash the stock firmware, reflash preloader and recovery separately, but the problem persist.
And one of the first messages i read was system corrupted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Help me please!!!
Aha! Same fone as mine... Now here's your problem, same as mine, quite simply, android 9 says mt6762, but an upgrade to android 10_q shows mt6765, I now have mine on 10 pro, and it shows mt6762. Now to get out of where you are, you need to grab the firmware for your fone, have adb/fastboot setup, and get ready to restore fone, the fact you can see recovery means it aint that bad... did you fix it?
Pachacouti said:
Aha! Same fone as mine... Now here's your problem, same as mine, quite simply, android 9 says mt6762, but an upgrade to android 10_q shows mt6765, I now have mine on 10 pro, and it shows mt6762. Now to get out of where you are, you need to grab the firmware for your fone, have adb/fastboot setup, and get ready to restore fone, the fact you can see recovery means it aint that bad... did you fix it?
Click to expand...
Click to collapse
Hello, thanks for answering, could you tell me the download link of the firmware that you used to be able to test and see if my phone revives please.
So I have this phone Xiaomi Redmi 10X, and I wanted to put Pixel Experience 11.0 in it, after seeing this thread on GitHub.
To my surprise, following steps on that link was not that easy!
I flashed MIUI 22.1.19 manually (not in the correct way), and I ended up with a hard bricked phone.
Yesterday, while Googling about that, I managed to run into a tool called MTKClient v2.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and it solved my problem, by flashing original firmware and got it correctly working with the default MIUI 13 system.
BUT, that wasnt enough for me, because I still wanted to put Pixel Experience in it since I like it so much and think it is so sexy!!! So I, without knowing what I was doing, erased all the partitions in my phone with that tool.
Now, I cant get it to connect to that tool to work or connect with my device. On the cmd behind though, I do get some hope after seeing that device is still recognized in some way, but that's all there is to it, it doesnt go further, only "Phone detected: Reading model info".
I've tried to wait and keep both volume buttons pressed at the same time, but to no avail.
Since this, I've tried several tools but none is working to reset my partition table to original state, since I think that's my problem.
Any idea how to fix it?
Jjflick said:
Did you try cross-patching it with a razor cable?
Click to expand...
Click to collapse
No. What is that?
Jjflick said:
Did you try cross-patching it with a razor cable?
Click to expand...
Click to collapse
Even if it connects, it shows no partitions to write over.
What it needs, is to first restore the erased partitions, I think, and then writing (flashing) the firmware into it.