Hey guys,
by the way, sorry if grammar is bad. Im German.
This is my first post here, so thanks for reading
I have already flashed some Smartphones with Recoverys, Custom OS an Kernels. So im not new to this.
Some days ago a friend gave me his G900F, because its stuck in bootloop after lollipop update.
I thought, thats no problem. "Just a new recovery with odin, flash kernel, clear cache and install rom".
At least ive tried like 3 kernels and some roms. everytime the same thing: bootloop.
Thats totally weird for me. i cleared all caches, davlik, internal storage etc and its still the same.
Bootloop:
Sometimes it boots up till Roms "settings screen for first boot (language, wlan etc)".
Then after a random time of seconds, i get graphic errors on screen and touch stops working. (parts of screen are flickering or swiched against each other).
Then the reboot follows with 2 short vibrates as confirmation. And sometimes it reboots before it reaches the Rom.
For me it sounds like broken hardware, but in recovery mode it works normal for hours, inclusive graphic gui and touch
The Recovery needs the same hardware parts (like cpu, ram, touch, gpu) to work like the os, doesnt it? im confused. Bricked or not?
Thanks very much for reading my Thread
seems like its emmc got corrupted.
Thanks very much for your reply.
Since there is a risk changing the emmc ( and i also dont have a new one ), is there a way to install android directly to ext sd?
nop. sorry i don't know of any
you have to visit some repair shop and emmc must be replaced
Hi,
I need a stock/factory ROM or any custom ROM that works for this phone : Yezz Andy AZ4.5
The phone can be flashed but i was unable to find a working ROM for it.
I tried to get the current file before flashing it, but nothing was accessible. Nothing except SP Flash Tool was able to access the phone.
It's an MT6572 chipset. I've flashed it with a similar ROM, when holding the home button, the phone vibrate, but the screen doesn't turn on, so i can't tell if it really boots or not.
Probably, nobody has access to this phone, but this is mostly my last chance to restore it with the stock rom. Or if anyone can create any compatible rom
Thanks guys !
Edit : After some research, the rom i'm using might be working, but the lk.bin (i've read that it contains some drivers) file doesn't have the correct lcd driver. So, it might boot, but nothing can prove it.
Edit 2 : With headphones, I can hear the boot sound (I checked on the net, it's the same). I'm flashing different lk.bin (uboot image) files and testing if the phone boots. With some, I get a screen with lines and it boots, with some other, I get a white screen but it crash during the sound and it tries to boot again.
Hello,
I'm not the best at flashing and all that, and I'm sure I'm doing something wrong here:
I have the problem like many, there is a 2cm bar over top of the screen where my touch is not responding, sometimes it works, sometimes not. Some say to zap it with a lighter's spark, tried it, didnt manage to do anything; others said custom ROM solves it.
(if you know a fix I'm not aware of, feel free to post).
From the "LineageOS" topic on the Elephone forums it says I need Android 6.0 (tried with 7.0, just to try -> bootloops),
the problem is I cant manage to get 6.0 working on my phone, I flash it with SPFT and when it says its done, my phone doesnt turn on, doesnt charge and does nothing. The only way to get it up and running is to flash stock ROM while holding VOL+ and plugging it in.
What am I doing wrong? Am I misunderstanding the steps? Am I just plain dumb? (probs)
If you need any more info, please ask.
Thanks fellas.
Update:
If I understood corectly you cant downgrade because the bootloader gets also updated to and doesnt allow downgrading if not unlocked, so I went and tried to unlock OEM.
It all works fine and dandy until I get to the "Press Volume UP to unlock or Volume DOWN to cancel" part, when I press UP nothing happens, and when I press DOWN it just cancels.
TWRP is flashed, and is rooted.
VirusWar said:
Update:
If I understood corectly you cant downgrade because the bootloader gets also updated to and doesnt allow downgrading if not unlocked, so I went and tried to unlock OEM.
It all works fine and dandy until I get to the "Press Volume UP to unlock or Volume DOWN to cancel" part, when I press UP nothing happens, and when I press DOWN it just cancels.
TWRP is flashed, and is rooted.
Click to expand...
Click to collapse
Thats wrong, this device comes unlocked by default, which is why you are able to boot twrp.. The reason the device doesnt boot when you try to downgrade is because the preloader is too old, you need to go to the lineage 13 forum and download the preloader tool provided there and flash it, alongside lineage 13 flash it from twrp, it should be android 6, you can still go to android 6 stock rom if you flash stock rom and then the preloader provided in the lineage (the most resent preloader for the 6.0) u should get android 6 stock booting
Thanks for clearing things up, it worked.
Sadly, it didnt fix the touch screen problem, I guess its faulty or something like that, I'll replace it when I've got the funds.
Thanks for the help.
Hello forum people, I need help to revive my S3 i9300, if you could help me I would really appreciate it.
I tell what I remember about the problem:
The phone was rooteado to be able to use it with any company since it was of movistar. a year ago with the rootking (we sent it to root), the phone was my dad and now has a new one, and it stopped using about 2-3 months.
Then I lent it to a friend who had just broken his cell, so I gave it to him so he has something until he buys one, but he told me that it did not work because he did not load and unload very quickly. He gave it back to me and I stopped using it until about 1 month ago, that I was left without a cell phone and I want to use it to have something.
The same thing happens as it does not load and it is very easy to download, BUT if you use the charger and cable of the Huawei ascend Mate 7 that my dad has, it charges perfectly and the cargo is not cut at all.
Well, seeing that this happened, I restarted it from the factory (I guess the root will be removed with that).
It was still branded and only loaded with the charger and the Huawei cable ...
Well now I tell what happened with what I did.
I install the samsung drivers for the compu, install odin 3.10.6 and under the recovery file that I put up, well I install everything but when I realized instead I read fast and instead of saying PDA said AP in the odin.
Well I try to turn it on and it does not turn on, I try to enter into recovery mode and it does not start.
Then I install another odin, version 1.30 and have a PDA, I do everything as I say start the phone in download mode, home odin, connect the phone to the computer, put the file in pda and give start.
He tells me that everything went well but still does not turn on and without going into recovery mode.
Say that when I do recovery mode (volume up, home and power) I see the logo of samsung and like that desinstegra, then it appears again and blinks in blue but as if it were broken and the logo moves. In short broken.
Then then install another recovery, https://dl.twrp.me/i9300/twrp-3.0.2-...0.img.tar.html
Now I want to enter into recovery mode but this appears and I want to touch some option that appears but nothing, as if the touch was dead.
And after that, it seems to me that I tried to change the Kernel and I put any but the one of my model by mistake.
Current status of the s3:
It lights normally but it takes a long time.
Enter DOWNLOAD mode (vol down, home and Power)
The screen touch does not work but it does show an image.
The buttons work, also the easy button of back and home.
DO NOT enter RECOVER mode (vol up, home and power) is frozen in the Samsung logo.
I want to make it work with any other rom that is functional except the STOCK. And that transforms into unlocekd
It does not matter if when I install a new ROM the files are deleted, I do not have anything in the phone.
Thank you very much to those who respond.
Only to get sure, that I understood you right:
after flashing the wrong kernel, your touch in twrp is not working anymore?
Will say the device is not reacting when you press a button on the screen with your fingers? If so than, I am afraid that your touch is broken. What kernel did you use? Can you post the name of the zip or tar file?
Beside of that, after flashing samsung stock, the reboot will last quite long. Maybe around 15 min till up to 25 or 30. And after flashing and before reboot, go to recovery and make a factory reset. Cross my fingers... :fingers-crossed:
rodman01 said:
Only to get sure, that I understood you right:
after flashing the wrong kernel, your touch in twrp is not working anymore?
Will say the device is not reacting when you press a button on the screen with your fingers? If so than, I am afraid that your touch is broken. What kernel did you use? Can you post the name of the zip or tar file?
Beside of that, after flashing samsung stock, the reboot will last quite long. Maybe around 15 min till up to 25 or 30. And after flashing and before reboot, go to recovery and make a factory reset. Cross my fingers... :fingers-crossed:
Click to expand...
Click to collapse
Hello, if I think that the Kernel had changed I do not remember exactly what it was because I downloaded it on a page written in Asian language by mistake and the Google translator confused the words and he said it was from the s3 but I think it was from the note 3.
The tactile does not respond exactly.
I did not understand him completely, he wants me to enter RECOVERY mode (it takes about 15-20 min to enter) and then do a factory reset?
I almost forgot to clarify that I had tried to do this from the video: https://www.youtube.com/watch?v=fA86_HFGx_w
Everything was installed perfect and I did it as is, except to delete.
Or reinstall the factory rom to see if it worked again.
If you flashed a kernel from note3 that the touch will be most probably minimum damaged and does not work proper anymore. I flashed mistakenly the kernel from the note2 and touch was broken, but maybe you were lucky and your touch is still working. No, passing into recovery should take only a few seconds, but rebooting into system after flashing samsung stock, then in recovery, then wiping and factory reset, could take a rather long time.
rodman01 said:
If you flashed a kernel from note3 that the touch will be most probably minimum damaged and does not work proper anymore. I flashed mistakenly the kernel from the note2 and touch was broken, but maybe you were lucky and your touch is still working. No, passing into recovery should take only a few seconds, but rebooting into system after flashing samsung stock, then in recovery, then wiping and factory reset, could take a rather long time.
Click to expand...
Click to collapse
Could you tell me how to do it please? I'm not an expert at all in changing ROM.
but you wrote that you already flashed something (?) via odin? I understood that you flashed samsung stock rom, beside kernel and twrp to proof, whether phone is working with original sw? If not than please check and search the i9300 forum section, there are a few of howtos and todo threads and posts which explains it even more better, that I could ever do
Edit: for example:
https://forum.xda-developers.com/galaxy-s3/general/samsung-galaxy-s3-sticky-roll-thread-t2344125 and from there for example
https://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
rodman01 said:
but you wrote that you already flashed something (?) via odin? I understood that you flashed samsung stock rom, beside kernel and twrp to proof, whether phone is working with original sw? If not than please check and search the i9300 forum section, there are a few of howtos and todo threads and posts which explains it even more better, that I could ever do
Click to expand...
Click to collapse
I used odin but I forgot how I had done and had followed the steps of a tutorial that I lost the link.
check my edited post above, now with links to guides and one of the best feature here on xda is the search button and that we have many things to read
rodman01 said:
check my edited post above, now with links to guides and one of the best feature here on xda is the search button and that we have many things to read
Click to expand...
Click to collapse
Hello, thank you very much for the links that you have passed me. They will be very useful, excuse me but I do not want to be irritating at all but I am really lost.
My only question is to know how to start reliving it?
I start installing CWN and then change the ROM?
I would recommend to start with flashing the original samsung stock sw via odin. To see that everything is working as it should. If it is so, especially your touch, than you can go ahead with routing, flashing an alternative recovery and testing custom roms, like leo or pie as you posted in the other thread. The time you are spending with writing here and in the second thread you could have already finished the sw flash and reboot to system to check the health of your device. Others than that procedure is a waste of time in my opinion. But thats your decision. On the other hand, we, or better I wouldn't spoon feed you further, because you can find almost everything for that years old device here with search, read read and read.
rodman01 said:
I would recommend to start with flashing the original samsung stock sw via odin. To see that everything is working as it should. If it is so, especially your touch, than you can go ahead with routing, flashing an alternative recovery and testing custom roms, like leo or pie as you posted in the other thread. The time you are spending with writing here and in the second thread you could have already finished the sw flash and reboot to system to check the health of your device. Others than that procedure is a waste of time in my opinion. But thats your decision. On the other hand, we, or better I wouldn't spoon feed you further, because you can find almost everything for that years old device here with search, read read and read.
Click to expand...
Click to collapse
Hello, I did the following, I had tried to re-install the stock stock a few days ago and it did not work, I did it for odin.
So what I did today was, install the recovery mode of ClockWorkMod and probe with the rom of MIUI 8 and that of Linage16, no installation. Then try with this: https://forum.xda-developers.com/galaxy-s3/development/rom-t3442868 And install correctly but it does not work, pass the Samsung logo but then when the ROM logo appears it stays there frozen and restarts ... it seems to me that officially the phone is dead.
Again: the right stock samsung sw should work if flash via odin didn't fail and, what I already mentioned, after flashing you did a factory reset in recovery. After that the reboot into system could take several minutes. Otherwise you can try it with repartition efs backup restore etc etc etc.
btw: newer custom roms, like leo-16, cannot be flashed with the old cwm recovery and cwm touch recovery, as you mentioned in the related thread, would not make much sense, if your touch is broken!?! If you do not want to go via samsung stock sw, then get a newer twrp, search for info which one is suitable, and guides how to flash custom roms, and flash the preferred one of your choice.
Never flashed anything from Gitlab and IDK where I'm at with Flashing TWRP cause I have few tiny hard to read lines of text on the lower left of the unihertz boot logo.
It's detected in ADB and PowerShell Fastboot
https://unofficialtwrp.com/twrp-3-3-1-root-unihertz-titan/
https://www.androidweblog.com/unihertz-titan-root-install-twrp-recovery/
My question about this is do I merge the two folders together. (artifacts folder and unihertz titan master folder. )
https://gitlab.com/ubports/communit...-titan/unihertz-titan/-/blob/master/README.md
I've never even built anything so I'm just going to use it as is, but this type of flashing is new to me. Pulling files off a repo etc, I'm used to the old school download a zip from AFH and putting it on a sd card and flashing it in TWRP, prior to all this I rarely if not ever did very many ADB Cmd's let alone much flashing.
So I'm trying to see what else I need to do and where I went wrong with TWRP
Sidenote if I hold volume up on a fresh boot it just reboots to a black screen then powers back on again, sits at the black screen for 5 to 10 seconds.
I'm used to the old simple single click rooting and custom recovery then apply supersu.
The last device I flashed was a Note 4 Edge
So rooting via KitKat days vs Oreo days are different a few things have changed, not many single click autorooters, not much use of supersu anymore it's mostly all magisk
so I'm a little behind haha when I got the KeyOne and Key2 I became rusty.
TWRP only currently works on EMMC Titan. This is being worked on. There are instructions https://gitlab.com/HengYeDev/unihertz-titan here to get ubuntu touch on a ufs titan. However i have not been able to replicate the results, yet.