My $20 hoot huawei p20 pro CLONE (here a link /w info about the phone with false specs full of bugs)https://www.freebrowsinglink.com/hoot-p20-pro/ got bricked a week ago after I left it connected to a Windows computer with internet access.
{
"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"
}
The story starts with when I tried to root the phone with KingoRoot, eventually ads started popping up, facebook, dating or porn sites and malware like that. I uninstalled KingoRoot and installed some anti spam software like avg and avast, but that did not help, ads kept coming. The phone has Android 5.1 Lollipop on it and after I left it connected to a Windows Laptop, like I said before, error messages with 'UI has stopped working' and 'other stuff stopped working' started popping up in a whole sequence of error messages so it rendered the phone unusable.
Next I started messing with it via platform-tools and wanted to flash TWRP on it and eventually a different OS like Lineage, but now the phone is totally shot and I can not use recovery any longer. The only thing that seems to work is fastboot mode, but it doesn't let me install a custom recovery like TWRP. Unlocking the bootloader seems to work, like shown in the attached pix, but other commands like 'fastboot devices' give a funny looking device name: '0123456789abcdef'. Other commands like fastboot erase -w and oem info show failure only; reboot-bootloader works and so on.
Any advice on this one? I'm just trying to learn about phones and android and this seems like a perfect opportunity, unless this cloned smartphone is piece of a worthless brick, which most assuredly is.
Try to flash corect stock firmwares for your device , check which one is yours .
https://hellostockrom.com/huawei-clone-p20-pro/
Yo TeddyLo, I tried already a similar website and after 2 hours of downloading through a slow internet connection the files were encrypted WinRaRs and probably useless anyway...thanks bro.
Hard Bricked Hoot P20 pro Clone
Yo, Teddy Lo, I had been busy last few days and tried to follow your suggestion, but to no avail. The device is now a hard brick, it does not come on at all, no more fastboot mode, or battery status logo when off and loading for that matter. It all happened when I tried to flash this file 'DOOGEE-Shoot_2-Android7.0--20170517' with SP Flash Tool. The device downloaded the files, but is completely dead now.
I am trying to do format and download with different ROMs for whatever is available on the internet for a P20 Pro clone phone, and phone manages to establish connection through USB with SP Flash Tool, but every time I get the following error message:
How can I fix this problem? Thanks.
Clone_Cat said:
Yo, Teddy Lo, I had been busy last few days and tried to follow your suggestion, but to no avail. The device is now a hard brick, it does not come on at all, no more fastboot mode, or battery status logo when off and loading for that matter. It all happened when I tried to flash this file 'DOOGEE-Shoot_2-Android7.0--20170517' with SP Flash Tool. The device downloaded the files, but is completely dead now.
I am trying to do format and download with different ROMs for whatever is available on the internet for a P20 Pro clone phone, and phone manages to establish connection through USB with SP Flash Tool, but every time I get the following error message:
How can I fix this problem? Thanks.
Click to expand...
Click to collapse
hi, i had the same problem, and i found this forum , it solved the issue ....
forum.gsmhosting.com/vbb/f296/clone-welcome-huawei-p20-pro-firmware-2574709/
Regards
Related
Hi, I am trying to root this phone using the guide here: bbs.elephone.hk/thread-9919-1-1.html#.WGr04lzUHIU
However in Windows 10, nothing happens when I hit the download button, and in Linux this error happens when using the files I got from the guide:
{
"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"
}
this is the same PC, with Ubuntu and Windows 10 dual boot
I have tried the fastboot method, but I can't get my bootloader to unlock, the vol up button simply doesn't register on the phone.
So is there any fix? Or am missing something?
Problem solved! Windows 10 doesn't like the drivers provided. However Windows 7 does, so I advise that you keep your Windows 7 install somewhere
Follow this it will explain what you need to do. I had same issue with Windows 10 but rooted my P9000 no problem. I used FlashTools - all the info you need here:
https://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042
I gave up following tutorials on elephone.hk forum & just followed tutorials from here, but whatever your personal preference - hope it helps ;0)
Need my elephone back
Not sure if this is best placed here???
So....tried to flash my Elephone P9000 using the SmartPhone Flash Tool and all the steps provided tutorial at:
https://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042
Using Win10 so it took me a while to disable the driver signature enforcement option to get the drivers installed. Got that done and all..so far so good.
Download all the files as the tutorial says...clicked download and connected the phone which was powered off. Up pops a messages "PMT changed for ROM; it must be downloaded."
Google search for this and came across some pages that informed me to click on the 'Format' section in the Flash Tool
Did this and then went back into 'Download' and hey presto, the flash worked and I got the big green tick.
Lovely stuff...until I tried to power on my phone....dead in the water. Power+Volume Up does nothing, power on its own does nothing. I've downloaded loads of instances of the Flash Tool, tried the elephone stock ROM scatter file, recovery image files etc and still nothing. Read loads of similar pages where it's happened to others but just wont work for me!!!!
Can anyone help?
jfk247 said:
Not sure if this is best placed here???
So....tried to flash my Elephone P9000 using the SmartPhone Flash Tool and all the steps provided tutorial at:
https://forum.xda-developers.com/elephone-p9000/how-to/how-to-guideline-install-mtk-drivers-t3344042
Using Win10 so it took me a while to disable the driver signature enforcement option to get the drivers installed. Got that done and all..so far so good.
Download all the files as the tutorial says...clicked download and connected the phone which was powered off. Up pops a messages "PMT changed for ROM; it must be downloaded."
Google search for this and came across some pages that informed me to click on the 'Format' section in the Flash Tool
Did this and then went back into 'Download' and hey presto, the flash worked and I got the big green tick.
Lovely stuff...until I tried to power on my phone....dead in the water. Power+Volume Up does nothing, power on its own does nothing. I've downloaded loads of instances of the Flash Tool, tried the elephone stock ROM scatter file, recovery image files etc and still nothing. Read loads of similar pages where it's happened to others but just wont work for me!!!!
Can anyone help?
Click to expand...
Click to collapse
this usually happends when your flashing with old preloader... try installing CM13 with updated preloader, it should work.
Thanks Ruben, I managed to get the green tick in the sm flash tools using the 'Elephone P9000 Preloader_Lk_Boot_Recovery update' scatter text file.
Phone still wont power on at all and i can't access the sd card to copy across any ROMS so I'm back to square 1 by the looks of it. I'll keep pluggin away at it.
Hello,
My LG-D280N is bricked... i think... every time it boots it goes on a purple screen called Demigod crash handler, it also does the same thing when i try to factory reset it
So i had no choice but to flash a new room to hopefully fix it, THANKFULLY it does go to download mode without crashes and it does show up on my device manager as "Android bootloader interface" but even so the flashtool says port(USB or Serial) not found, here is what the phone says
{
"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 was writing all that, it actually booted to android!!!! but there are infinite " app stopped" messages, it's impossible to go to settings and try to hard reset or rather it's impossible to go anywhere, looks to me like re-flashing a brand new stock rom is the only choice
i should say that i put this phone in my closet two months ago and it was fine! when i tried to use it today it was like that but anyway, is there anything i can do? I really need to fix that phone
Thanks alot, i really appreciate any help
An update... the phone responds to fastboot commands from ADB tools, it doesn't show up on "adb devices" list though
Wonder if there is a way to use to use fastboot commands to flash a kdz file?
More updates... i used a tool to extract everything from the KDZ file and reflashed the following files like this:
fastboot flash boot boot.bin
fastboot flash factory factory_475136.bin
fastboot flash factory recovery.bin
fastboot flash aboot aboot_144384.bin
fastboot flash aboot abootb_150528.bin
Now i could of have done something either right or extremely stupid BUT ever since i did that factory reset mode actually worked! no more demigod crash handlers and i also stopped seeing those small "boot verification errors" in the corner and the phone actually booted and saw the initial welcome screen, so it actually factory reseted! BUT even though it did I STILL saw the sea of "*instert app here* has stopped" which makes it impossible to navigate the phone
But for whatever reason, it's now stuck on the startup logo after a reset, well even if i screwed up badly, download mode still works like before sooo it's not much different, at the very least i got rid of the stupid demigod crash handler
I've been working on that phone for hours now... been researching on google with little to no information about this at all, most solutions involve the flash tool WHICH doesn't work so i had to come up with my own ideas... and to make matters worse nobody here has gave me clues on how to fix it which is why i give these updates, maybe all this information will help you come up with a solution
Another update... i was wondering why it wouldn't be detected by my flashtool... until it hit me... the download mode itself has problems, thankfully fastboot still worked and i was able to reflash it using one of the files i extracted from the KDZ file
After this, my download mode now works correctly, it displays everything right and is now recognized by the flashtool! finally some real freaking progress, working on this thing is such a pain but finally im getting somewhere, but it's not over yet, right now im waiting for the device to reach 40% of charge before i flash the rom, hopefully no errors will occur as it has already been a HUGE pain and time consuming
Final update... i have successfully flashed the stock rom, after a whole day of trial and error i did it, let me summarize
My problem was mostly that the download mode itself needed to be reflashed, for whatever reason it was broken or not properly configured but whatever the case, it needed to be reflashed using fastboot in order to work correctly and be recognized by the LG Flashtool, after i reflashed it, it was fine and the LG Flashtool FINALLY recognized my device, but the LG Flashtool would CRASH whenever i clicked the "Read Phone Information" button, not sure why but i tried 4 times until it finally worked, not sure what happened there but who cares, it worked out, then it finally started flashing until it said "error connecting to the server", took me sometime and research to realize that it's SUPPOSED to do that and that i should ignore the message and NOT close it because if i do the whole flashtool stops, after this i let it sit in the background and do all the flashing, it was fine until 77%, it gave me an error message and said that i should try to reset my device back into download mode, then it retried doing the whole process all over again AND THANKFULLY this time it successfully did it, the phone now boots to Android as normal, the sea of "app stopped" message is also gone thankfully and so that's pretty much it...
My absolute stupid mistakes and problems with this could help other people avoid those same mistakes and problems so i won't delete the post since as i said, it can prove to be useful to others
Hi all,
think i bricked/ defected my Pace today. The idea was a mod with german language so i began to read here at xda for info. I'm on iOS now but modding on Android is nothing new for me, i modded some mobiles before, everthing workedtill today. I unlocked the bootloader and installed the mod, something went wrong i think, maybe i tried an incorrect image or something else, i don't know. After installing the watch wanted to update via OTA an after that it was shown as a Stratos in the Huami Amazfit Tool, sn was NULL an so on. The watch booted to os but the app was not able to read the QS Code for connection, touch doesn't work...
I can't say which ways i tried the last 6 to 8 hours to repair it and now i'm sure there is no bootloader/ software anymore on the watch. It starts with Amazfit Logo and stops with "No Command" & and the triangle. The only way to connect is in Fastboot, which shows chinese signs at the bottom of the display. There is no connection possible on ADB or otherwise.
Is there any way to get back the software on my watch? Maybe download mode which starts from my pc or something else? I'm on win 10 here, there is no linux machine or something else.
Thanks for reading
If you can get to fastboot and recovery, you have not deleted the bootloader.
Follow this guide: https://forum.xda-developers.com/smartwatch/amazfit/tutorial-unbrick-huami-amazfit-t3547300
Quinny899 said:
If you can get to fastboot and recovery, you have not deleted the bootloader.
Follow this guide: https://forum.xda-developers.com/smartwatch/amazfit/tutorial-unbrick-huami-amazfit-t3547300
Click to expand...
Click to collapse
Hi,
i tried this yesterday for about 10 to 15 attempts, but after step 4 there is no adb connection for step 5 and adb commands doesn't work. Getting the watch in fastboot is no problem anymore for me after last night
You have flashed Stratos firmware on your Pace, that's why touch didn't work. If the unbrick tutorial didn't work for you, then you should check your drivers: both drivers for adb and fastboot (they are different) should be installed and working properly. Sometimes you must re-connect the watch for the computer to detect it when the mode change, I usually keep Device Manager when I am using Windows to check this.
Or try AmazeROM installer, it has an option to start flashing from fastboot and it will guide you through the process.
Hi all,
sorry for my later post but under week i have no time for doing things like this here.
I checked adb and fastboot on the pc, installed system wide and works, fastboot drivers seems to be ok, but i have no idea how to check adb drivers. It's all the same, if i try this guide https://forum.xda-developers.com/sma...azfit-t3547300 or if i install amazeos with installer. The watch is recognized in fastboot but afterwards switching to adb there is no new connection, it's still in fastboot and does not switch to anything, i can restart it when amazeos installer script runs but nothing happens and if i let it run for about three hours the watch is still in fastboot and nothing happens there. In the device manager i see only an ADB Testing Device when in fastboot connected, on adb nothing happens there.
I tried everything on a clean win 7 machine, in this case the watch won't even recognize, so i could't run an installer or try to use the unbrick guide.
Just for information, it was Stratosfied which killed my watch in my mistake, but after that i think i deleted all with Amazfit Tools for doing the worst case for me here an unplugged it before reinstalling something else.
I attached some pics of the watch, first is after starting and directly after Amazfit logo, second is in fastboot with this method https://forum.xda-developers.com/sm...tches/amazfit-boot-fastboot-directly-t3546829, Point two there is not reachable, only point one fastboot, but in it i can't do anything though.
{
"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 for information, every fastboot command will be determind with "The command is not allowed"
Hi,
For a few weeks now, my stratos 3 doesn't work despite all my efforts. The problems started to occur on 4.2.5.0.
When I boot the watch in smart mode, I only see a black screen. But the watch can be linked to the phone in bluetooth and adb commands are working fine.
I can restart the watch in ultra mode using adb reboot mcu and it works fine in that mode.
I tried to wipe data with adb reboot wipe, same
I tried to install the stock firmware (https://forum.xda-developers.com/smartwatch/amazfit/fw-tool-stock-global-international-t4031153), no change (even with older FW)
I tried the PACEficator Custom ROM (https://forum.xda-developers.com/smartwatch/amazfit/paceficator-project-stratos-3-multi-t4033223), it worked for 2 minutes, then the problem reappeared.
I tried to flash the watch with the ingenic tool (https://forum.xda-developers.com/smartwatch/amazfit/tutorial-ingenic-cloner-tool-aamzfit-t3908237), same...
At this point I don't know what to do, except only using the watch in ultra mode.
Is my SD card damage? Or is it another component ?
If you have any lead, idea or insight, I would take it willingly :fingers-crossed:
elimeXCI said:
Hi,
For a few weeks now, my stratos 3 doesn't work despite all my efforts. The problems started to occur on 4.2.5.0.
When I boot the watch in smart mode, I only see a black screen. But the watch can be linked to the phone in bluetooth and adb commands are working fine.
I can restart the watch in ultra mode using adb reboot mcu and it works fine in that mode.
...
Click to expand...
Click to collapse
Hi! I have the same problem that I encountered in the same period ( the 4th May FW 4.2.5.0) but in my case the watch optimizes app for 20 minutes (15% of battery), then gives QR but can not pair the mobile. I skipped QR from adb and the watch boots in Smart mode but it works wery slowly and shows big charge leak. In my case i can pair with earphones but not with the mobile.
I did all to pair but adb shell dumpsys bluetooth_manager says:
enabled: false
state: 10
address: D8:80:3C:3B:71:F3
name: Watch
Bluetooth Service not connected
I upgraded with original OTA update to 4.2.6.0 - useles
I unlocked bootloader and flashed with Saratoga moded FW 4.2.6.0 - useless
Now thinking to downgrade or eraze and unbrick.
Taking into consideration mentioned above I don't think our problem is a hardware one.
Hello,
Little update...
I decided to downgrade to 4.2.2.1 to see what would happen.
But first I started to go into fastboot mode and then I rebooted the watch. A message that I had never seen before appeared :
{
"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"
}
I don't even know what is the launcher , so I closed it.
And then, :angel: :angel: :angel: the watch started to work normally.
I don't know what happened, and if the problems that I had will be coming back. But I'm praying that it won't.
So I'm now in 4.2.6.0 and everything seems to be working fine.
You're right Godfly, That's not a hardware issue.
elimeXCI said:
Hello,
Little update...
I decided to downgrade to 4.2.2.1 to see what would happen.
But first I started to go into fastboot mode and then I rebooted the watch. ....
I don't even know what is the launcher , so I closed it.
And then, :angel: :angel: :angel: the watch started to work normally.
I don't know what happened, and if the problems that I had will be coming back. But I'm praying that it won't.
So I'm now in 4.2.6.0 and everything seems to be working fine.
You're right Godfly, That's not a hardware issue.
Click to expand...
Click to collapse
Congrats! I downgraded to 4.2.2.1 - useless. Now upgrading to 4.2.4.0. I am afraid will have to to flash the watch with the Ingenic Cloner tool and dawngrade like you.
Don't go to 4.2.6.0 it's so bugged 4.2.5.0 is ok
Hi i am newbie this forum i have an problem with an android gingerbread isn't booting and didn't vibrate show samsung logo or anything battery charging now show and when i connect to my windows it sounds device connected / disconnected and when on Device manager is "Unknown Device" It's one of seriously problems because maybe android plays with unmount system / partition 4025 MB or something from clockwork recovery now the system cannot be reinstalled , booting into recovery , download or anything and ODIN Didn't show ID / COM .Does this think happened to you press the button / plug in charger and nothing happened .I Also installed Android ADB Driver upon adb devices command it display error no device found I Try to find a way to repair myself without to take the old device to an repair shop to replace the android piece memory that i don't know where is located.If is an way to fix that i will say thanks.Sorry for bad post but my phone didn't do anything it have problems.What i will do , no one of the youtube tutorials helped much.It does not boot loop anything like a blank screen not flash nothing happened. It does not have bootloader / fastboot / recovery / download mode anyone it's very bricked i cannot undo anything.
Thanks for reading this threat
Bump for help
Sorry if i bump so i need help with this device GT-S5300 for 5 years i must take tomorrow to repair service device so i have 2 pictures of my device that cannot boot into recovery and download mode. :crying:
What i will say not booting into recovery and download and boot is dead without os it cannot vibrate the android and show samsung logo
Here is pictures of android and proof not booting a lot
{
"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"
}
This device must be fixed with all costs so i am Romanian maybe chance to survive or fix is 10
Tommorow i will take it to repair and i explain the situation maybe i replace the motherboard aswell with gingerbread os 2.3.6 I Hope there is a chance to repair so good luck to me
Fixed GT-S5300 Unbricked motherboard
I have good news my motherboard has been changed and had an low price so the repair was successfully
My samsung have the last chance i guess so must avoid forced upgrades and force format because maybe bricking again so i root an flash zip and worked and partition fine
Now that problem has been resolved i must ask someone to end this topic :good:
Carefull gingerbread i warned myself :fingers-crossed::victory:
When I was at Junior High in 9th grade I broke my Samsung GT-S5300 due to improperly install of incorrect custom rom (lollipop) to my phone that's why the device can't read my sd card even the gallery is empty. I broke it on last 2017. And now 2022 I tried to repair it via odin because our school allow us to borrow a laptop (which is I don't have) then repair my phone there and boom! I got my Samsung GT-S5300 back again to normal. It's now 5 years old. I love that phone because it's so hard to break it. I remember I throw my phone and then it's still alive. Until now it's still alive (but the home key don't work) but I can still use it. My favorite phone is this samsung gt-s5300. I'm planning to buy the same phone like this but I can't find it in the market (because it's phased out or not available). By christmas I will buy Samsung GT-S5360 (even if I have much money I don't like luxurious phones).