Serious Problem of this Doogee X5 MAX S - Doogee X5 Questions & Answers

Hello Gents,
a serious problem of this Doogee X5 MAX S.
one day the phone stack on Doogee LOGO and won't to start. so i decide to take a risk and flash it.
first flash the logo disappear but still no starting.
a second flash with same thing nothing happen, and for the recovery mode always can access without any problem.
So after that i decide to flash it with FORMAT + Download , and then i think here i committed my big mistake; the bootloader and recovery Menu no more exist , nothing showing up on the screen ....nothing just the screen stay black
After that i started to looking on the net for ROMs support for Doogee X5 MAX S with MTK6737 Processor. I tried more than 8 ROMs.
what is a positive sign is that The ALL ROMs passed without any problem. i flashed too with TWRP recovery but always the screen still black.
please any suggestions how to return back the bootloader tiny font Menu ; or any other solution

Related

[Q] [9001] Stuck on Splashscreen and more

Hello guys, I have a big problem with my GT-I9001,
I have installed the clockworkmod and cyanogenmod by ivendor, (Alpha 7) http://forum.xda-developers.com/showthread.php?t=2000828
If I try to start my Galaxy it stuck's on the Splashscreen where I can see the Galaxy S Plus and the Cyanogenmod logo. After a few Minutes the screen goes of but you have to take the batterie out of the Handy to start it again.
If I try to boot into recoverymode, after the samsung logo the screen goes off, and again I have to take the batterie out.
At both Situations, if i touch the menu or return button it lights up, but not off anymore. At Situation 2 after a few Minutes.
The Download mode still works but if I try to Flash, for example with a Stock Firmware, it seems to go through with no problem, but instead of rebooting it only gets a blackscreen.
When i have flashed it and I start it the Splashscreen still has the Cyanogenmod logo on it, also if i flashed it with a Stockfirmware.
Another thing is, that if i try to charge my Smartphone, the normal shown batterie is stuck too.
Some people already mentioned the BroodRom, but on the download mode appears the Sentence: MMC boot: MBR read failed, and at Booting normaly is no change.
I tried to connect with adb to the Handy while it is on that black screen. It works, but if i try to enter: recovery --wipe_data, but in the cmd it only says: "/sbin/postrecoveryboot.sh not found" and nothing changed.
So this is the List of things that don't work or i already tried. I hope you guys will find a solution. If not i want to ask what Smartphone you would buy.
Problem found
I searched the whole net and i think i found the problem, It seems to be the memory controller.
I came to this because if i pushed something onto my Handy via adb it was there only till a restart. And some communities tell me, that the problem can be solved by exchanging the memory controller. But i don't think i can do that.

honor 3c (h30-u10) stuck at boot logo (restarting at boot logo)

Hello guys ,
out of the blue my phone just stuck at boot logo and just keeps restarting .
it either stays at boot screen or nothing at all.
power+vol up(down) isnt working as well
can anyone please help me resolve this
i went to a service center and they said it is a hardware issue and parts for this model are not available any more so they cant do anything this about it.
TIA
regards
umerashraf said:
Hello guys ,
out of the blue my phone just stuck at boot logo and just keeps restarting .
it either stays at boot screen or nothing at all.
power+vol up(down) isnt working as well
can anyone please help me resolve this
i went to a service center and they said it is a hardware issue and parts for this model are not available any more so they cant do anything this about it.
TIA
regards
Click to expand...
Click to collapse
Do adb recognize your phone?!
Fixed it?
flash stock rom.
If your phone is showing you BOOT (huawei/honor logo or image) then this not hardware issue. It can occur if you have flashed a custom recovery while its bootloader is locked or Chinese local update available on carbon tesla. Code [email protected] has given very precise details and solution about it. Solution= Download Sp flash tools. Download drivers. Download signed and unsigned official roms B108 or 115. and start experimenting.
what I have done : I flashed Chinese version Rom and then Same issue occurred sent it to claim my warranty. after sometime I did the same mistake but I started searching for this issue and found a complete huawei honor 3c guide on xda. Do not believe shop owner they can be mistaken or experienced.
Fixed
My huawei honor 3c was stuck on logo. I copied dload file to mmc and through stock recovery flashed it. Phone is now ok.

Doogee X5 MAX S MTK6737 -bootloader and recovery + ROM troubles-

Hello Gents,
a serious problem of this Doogee X5 MAX S.
one day the phone stack on Doogee LOGO and won't to start. so i decide to take a risk and flash it.
first flash the logo disappear but still no starting.
a second flash with same thing nothing happen, and for the recovery mode always can access without any problem.
So after that i decide to flash it with FORMAT + Download , and then i think here i committed my big mistake; the bootloader and recovery Menu no more exist , nothing showing up on the screen ....nothing just the screen stay black :crying:
After that i started to looking on the net for ROMs support for Doogee X5 MAX S with MTK6737 Processor. I tried more than 8 ROMs.
what is a positive sign is that The ALL ROMs passed without any problem. i flashed too with TWRP recovery but always the screen still black.
please any suggestions how to return back the bootloader tiny font Menu ; or any other solution
I Have the same exact phone with the same problem
I even ported the firmware from a new one because I have a few of them in my store using InfinityBox
and flashed without any problem but no life
a lot of this phone owners have the same problem . the phone is stupid garbage

Xperia Z3+ E6553 - strange issues, i wanna help

If you dont want to see all my story, go down 2 see the base of my problem and second question.
Hello, i recently bought this phone in last week, used, for fifty euros and it had 32.3.A.2.33 firmware, and please remember WHITE boot screen.
It havent bootloader unlocked.
For some hours of using, it runs fine, except display, seems to be changed by amateur person, sometimes bad touch sensitivity, but i turned on glove mode and no problem. No lags, camera working, every thing - no problem so far.
And then problem began - after restart for sim change, phone boot animation was very slow, and some display flickering. When it booted, system was very slow, display had very slow reactions, i thinked it was GPU or software problem. After some minutes it itself rebooted, 2 red blinks and then booted very fast.
I tried some restarts, 2 of 5 was this problem.
I tried unlock bootloader, and install TWRP, because i think this isnt GPU problem, if 3 times booted and works flawlessly for HOURS !
Okay, bootloader unlocked, twrp installed, i searching for some roms, but phone have very bad community on XDA, i downloaded 3 roms:
AOSCP 3.5.1 - works flawlessly, no display flickering or something, some bugs like camera with bad quality photos, but after restarts, no display flickering or lag and this is important. But no boot screen (pure black boot screen)
Ressurection Remix 5.8.5 - Android 7.1 - after restart it HAD flickering and lag, something similar like first stock rom, 2 of 5 boots... Not very bad but yes. Very good rom.
LineageOS 14.1 - EVERY BOOT HAD THIS PROBLEM. LAGS, DISPLAY FLICKERING, RESTART AND 2 RED BLINKS.
So i installed again AOSCP 3.5.1 and no problem, only camera.
My not intelligent head was a plan - i prove a downgrade. To 28.0.A.4.8 - stock android 5.0.2. Phone gets black boot screen, and EVERY boot had this problem. Lags, scuttering, flickering... But it booted. I try restart, but no difference. 5 of 5 boots had this problem.
I have installed again nougat rom but not like first, but 32.4.A.1.54. After start flashing with flashtool - report an error with boot_delivery.xml - so i checked exclude bootbundle - no problem with flash. Restarted.
Phone had a BLACK BOOT SCREEN - i looking, because nougat sony roms has a white boot screen.
First boot without Sim card - no lags anytime. It has restarted itself, because i wanted to add sim card.
After reboot, every reboot had this problem.
I tried flash with fastboot twrp like first - https://forum.xda-developers.com/xperia-z4/development/twrp-twrp-3-1-1-z3-z4-t3862684
After fastboot reboot - phone has 2 red blinks and not turning on. I put cable out and i trying to turn on it, but it only vibrates 3 times and nothing. Boot or something, i thinked it is dead, but FOR TODAY im able to get into flash mode and bootloader.
I skip some 5 days with trying with flashtool LP, MM and NOUGAT roms, FLASHING TWRP, Sony companion is unusable, because i unlocked bootloader... My phone (or fifty euros) is in holy phucking s+++ in 2 days of using.
Okay, only twrp what i can boot normally is 2.8.7.0 recovery by old 5.0.2 android Z-ROM https://forum.xda-developers.com/xperia-z4/development/zrom-custom-rom-z3-e6553-28-0-8-251-t3206005
For questions, i tried both this stock firmware and custom rom, rare thing is boot normally, but after restart, no difference.
I tried flash again first stock rom 32.3.A.2.33, no difference, but BLACK BOOT SCREEN aside of white.
One but only one different 3.0.0.0 twrp what im able to flash, only into FOTAKernel or RECOVERY not boot partition, because RED blinks and nothing, but this twrp is from sumire (z5):
https://forum.xda-developers.com/crossdevice-dev/sony/twrp-3-1-0-z5-z5c-z5p-t3571050.
I founded this argument by flashing and aoscp rom and error: This is for (ivy), your device is sumire.
I think i can change update_script - there i changed every ivy to sumire.
Installed with this twrp flawlessly, flashed magisk, reboot.
Again Red blinks...
Now what im able FUNCTIONAL only - flash 2.8.7.0 (too with display flickering and , but this twrp is ONLY for install Z-ROM, other roms like aoscp and RR i cant install because error E1004: cannot install system boot image.
And other twrps i can flash only to boot (kernel) partition, but red blinks or boot again into this 2.8.7.0 recovery.
I am making with Sony, and i had in the hands SO MANY phones , so many from them for repair, from different brands for 7 years, no problem with flashing so far (i thinked i am unstoppable :victory: ), and this is my 2nd phuckedup phone for whole 7 years (first was LG G6) and i wanna help, because i have working flash and bootloader, but i havent an idea what next, because some (80 percent) threads havent functional download links for NO SUPPORT or something, but this is absurd. Like my issue, but this is real. For example: i have Xperia SP for 6 years, with stable recently updated (30.9) LOS 15.1 and Xperia S (recent nAOSP 8.1) for 7 years, flashed anything, anything, anything... Downgraded, upgraded... And no problem for today. Reliable phones as... SP is my primary phone (for 6 years) and S for testing. I wanted something from sony but more performance - functional for 2 days. And karma is here - in xda.
Recently i put it into wall charger, it booted into that 2.8.7.0 recovery and it had 94° and it still breaths ! And really it was very hot ! Normally it had less than 60°.
If i flash through fastboot mentioned newer twrp 3.1.1, 3.0.2, 3.2.3 or other mentioned, what non-functioning there, after that red led blinks, it will go to (green) flash mode.
The main problem is: I am able to go into flashmode and fastboot, i can boot system, but (now) i am able to flash only one old recovery, where i CANT install and boot for example aoscp rom or other rom without problems (black screen, then red blinks, then green flash mode). Original software - lags, display scuttering, graphic artifacts but rare thing is going flawlessly, so i think isnt gpu problem. I need real help. I need this phone and i think it can be recovered. I can send anything from this phone (logs or videos), what would be helpful.
After factory reset + system format, in that old recovery, i have in internal storage (sdcard) folder with name 0. Everything cleaned, but this folder remains.
So there is second question, someone experienced with this issue ?
Problem with aoscp fixed. Very luckely, but no problem now !
I had an version of flashtool, 0.9.18.6, maybe i havent problems, because i had older phones from sony (my fault) and newer versions i have experience, cant found .ftf with older firmware.
An error, what i had in older flashtool when i trying to flash both nougat and marshmallow roms - entry (0000084F)parsing error boot_delivery, which means an program for boot.
I doing an very bad thing - check exclude bootbundle and flash was without errors, but this is reason, why i havent an white screen in nougat and marshmallow and amount of recoveries i cant flash so i cant flash an rom.
What i do is install an 0.9.23.1 version of flashtool (because i have an x86 notebook and today versions dont support x86, only x64)
Downloaded orange PL 32.2.a.5.11 (marshmallow official stock rom) from XperiFirm and it flashed bootbundle without problems !
I restarted it - WHITE BOOT SCREEN and HOORAY ! But lags, display scuttering and things, what i writed here, was here, also after itself restart - 3 red blinks. So after 3rd reboot i take cable, plugged in with volume +, fastboot flash boot 3.1.1.0 recovery and it worked.
Flashed AOSCP, magisk and booted without problems, no lags, no display scuttering and etc.
I am very glad i fix my problem, but an question still, why in official firmware or some custom roms (except AOSCP) i had this problems with lags, graphic artifacts, scuttering and reboot in random time with 3 red blinks ? On EVERY official firmware
Hint for you
If you have problem like me, every custom rom making problems, use boot image from aoscp https://androidfilehost.com/?w=files&flid=143620
I am not maintainer of this rom, i want only help others, if your device lags or graphic issues.
Maybe you get bootloop, but with this boot image i havent experienced after every reboot any problem with mentioned lags or again flashing twrp.
Still question for E6553
I tried almost all roms for this device and every other roms have problem with mentioned.
After flash and restart, every boot have problem with display flickering, lags and very, very slow reactions.
Even with every official firmware.
AOSCP is ONLY FUNCTIONAL SYSTEM FOR MY DEVICE ! But it have some bugs, like automatic brightness, bluetooth turning off, nfc not working, accelerometer or little bit heat and idle battery drain (it is fixed by GlassCanon LXT magisk mod) or screen does not turn off when i call, but never this boot problem.
One thing what i see, aoscp havent boot logo from sony and when i get out boot.img from this rom and put it into other custom roms (like LineageOS 14.1, crDroid or RR) and reboot it, no lags, no display flickering, pretty fast boot animation, but bootloop, so this boot.img is proprietary.
I tried from androidfilehost download aosp ota, but error 7 in twrp and when i change this in updater-script, then error 6.
Next what i tried from aosp - fastboot flash system.img - and i cant install it, because this file is big - around 1.2gb.
I am in corner with this phone and i wanna help, what more i should do for stable system or fix bugs in this rom.
Thanks

Question Phone Turns Loops

Hello there, I`ve got a problem with my Xiaomi Redmi Note 10 5G.
After I`ve flashed TWRP, when I turn on my Phone, it doesn`t boot.
The first time it did llike this the accu was next to empty.
So thought, when I would buy a new accu, I would be able to flash it again, but now I've put a new accu in but It's also not possible to flash it again.
I've got a broken Display on this phone, too.
Yesterday I've ordered a new Display.
Today I've tried to boot into Fastboot Mode, so I would have known that it's booted into Fastboot Mode, if there is shown a device in the CMD.
Before I get the new Display, please help me to "Unbrick", I think it's bricked, this phone.
I don't know what I can do.
Bootloader is opened and I think I bricked it by flashing TWRP. And the accu could has been a problem, because it was next to empty.
JonnyBoy84
i dont understand if your phone can enter into fastboot. your message is not clear

Categories

Resources