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.
Related
Hi guys, sorry if this is in the wrong section.
My brother has a Huawey y300-0100 (u8833 I believe), I rooted it for him with no issues,and installed TWRP via the app in the google playstore, but forgot I needed to unlock the bootloader, and now because of that everytime I power it on I get this error:
Image signature verify fail
Your boot/recovery image may have an incorrect signature.
Please update your image to a signature official one
Click to expand...
Click to collapse
I have no idea how to fix this, I have read some forums but was unable to understand anything other than the access to the pink screen.. any ideas anyone? Thanks in advance.
update: I fixed it, I downloaded the official rom from the Huawei website and put it on the external sdcard, then held down V- V+ and Power while it was off, it installed the stock rom back onto the device and everything works perfectly, close the thread as you wish
how to restore “image signature verify fail”
Sparkles SP said:
update: I fixed it, I downloaded the official rom from the Huawei website and put it on the external sdcard, then held down V- V+ and Power while it was off, it installed the stock rom back onto the device and everything works perfectly, close the thread as you wish
Click to expand...
Click to collapse
I have the same problem ... i have downloaded the rom from huawei, but after i push V- + V+ Power.. it still loads to the pink menu.. Now, i have no idea how to repair it ..
sorry for the bad english
problem not solved. please recommend any other solutions
Sparkles SP said:
Hi guys, sorry if this is in the wrong section.
My brother has a Huawey y300-0100 (u8833 I believe), I rooted it for him with no issues,and installed TWRP via the app in the google playstore, but forgot I needed to unlock the bootloader, and now because of that everytime I power it on I get this error:
I have no idea how to fix this, I have read some forums but was unable to understand anything other than the access to the pink screen.. any ideas anyone? Thanks in advance.
Click to expand...
Click to collapse
How did it worked on your device, mine says falure while installing rom download from huawei official website. What is the solution to it.
Do anybody have any idea, please help. I have also not unlocked bootloader.
Get the official ROM from Huawei website. Unzip, and copy the contained folder 'dload' (with the UPDATE.APP file in it) to a microSD-card. Pull your phones battery, insert the SD-card. Put battery back in.
Hold down both Volume buttons (+ and -), and hold down Power to turn on the device.
It should start updating, stock reflashing the phone. If not, the problem is most likely your SD-card.
I also ended up in 'brick-lite' mode by trying to replace the bootloader without unlocking. Above worked for me, and by calling Huawei I got the right unlock code, unlocked, and has the bootloader replaced and the system SU'ed so far.
Tips to others with issues:
Vol + and power on == bootloader
Vol - and power on == locked in logoscreen, turns on ADB fastboot mode (for unlocking bootloader etc)
Both Vol and power on, SD card in reader == factory reflash (file must be on SDcard)
Both Vol and power on, no SD card == Pink mode
Almost there and then it failed...
{
"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, I don't know what to do next.
My device Mi3 is running on CyanogenMod 13 and latest TWRP recovery. Unable to install weekly updates of CyanogenMod. Recently, got an update cm-13.0-20160516-NIGHTLY when i tried to install that there is an dialog box of "Apply Update" You are about to update bla bla bla... Note: This feature requires a compatible Recovery or updates will need to be installed manually. I didn't get what it means and i thought TWRP is a valid recovery so proceeded from that. After few minutes it rebooted the device top recovery and nothing happened from that. So i rebooted the system again searched over Internet about the issue haven't found any perfect solution (within what i found) but i tried by copying the update file to /sdcard (i mean root directory) and tried to install the update manually by using TWRP recovery but it is showing an error "Updater process ended with ERROR: 7 Error installing zip file '/sdcard/cm-13.0-20160516-NIGHTLY-cancro.zip' Updating partition details......done"
Can you help me out how to install the update and also tell me what I've done wrong so that i will not do that again.
Thanks in advance.
Dude, the answer to your question is in the first post of CM13 FAQ.
Go in here and follow the guide.
https://jrizzoli.github.io/dotfiles/
Hi @diongdyh
sorry for late reply, please help me with a step that is mentioned in the link you've given.
"Run flash_all.bat (on windows) or flash_all.sh (on OS x and Linux - it's suggested to open it from a terminal in these systems)"
Does it mean to run in cmd or what. Please help me out. If you can please elaborate that step.
manideeproyal said:
Hi @diongdyh
sorry for late reply, please help me with a step that is mentioned in the link you've given.
"Run flash_all.bat (on windows) or flash_all.sh (on OS x and Linux - it's suggested to open it from a terminal in these systems)"
Does it mean to run in cmd or what. Please help me out. If you can please elaborate that step.
Click to expand...
Click to collapse
Just connect your device and double click on "flash_all.bat"(I'm assuming you to be on Windows) and it'll do the rest
Well I encountered the same problem a while ago.. I just flashed miui 8 through twrp.. and booted and again flashed latest cm13 and it worked.. No problems so far..
Sent from my MI 3W using XDA-Developers mobile app
@ssasin.monish said:
Just connect your device and double click on "flash_all.bat"(I'm assuming you to be on Windows) and it'll do the rest
Click to expand...
Click to collapse
ok i'll do the same. I doubt whether the device needs to be in fastboot mode or normal system. If you can clear this i'll proceed because previously i tried the same but in fastboot and the device is recognized i checked by 'fastboot devices'.
manideeproyal said:
ok i'll do the same. I doubt whether the device needs to be in fastboot mode or normal system. If you can clear this i'll proceed because previously i tried the same but in fastboot and the device is recognized i checked by 'fastboot devices'.
Click to expand...
Click to collapse
{
"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"
}
It is literally written in the second step. Bootloader=Fastboot mode.
diongdyh said:
It is literally written in the second step. Bootloader=Fastboot mode.
Click to expand...
Click to collapse
i've done the same @diongdyh, after selecting run something went in a flash on the desktop screen and nothing happened on my device and its still in fastboot mode. i think booting to miui 8 and then installing cm13 will be a better option as suggested by @sidhg for me as i'm not getting exactly what to do
even I am having the same problem, I nothing happpens on clicking on flash all file.........
manideeproyal said:
i've done the same @diongdyh, after selecting run something went in a flash on the desktop screen and nothing happened on my device and its still in fastboot mode. i think booting to miui 8 and then installing cm13 will be a better option as suggested by @sidhg for me as i'm not getting exactly what to do
Click to expand...
Click to collapse
Yes it'd be best that you flash miui 8 with fastboot/bootloader
http://bigota.d.miui.com/6.6.1/cancro_alpha_images_6.6.1_20160516.0000.22_6.0_cn_2231b4fcb7.tgz
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"
My fellows and friends,
One of these days, I received an update from LineageOS and when installing it from OTA ( using TWRP ), the first lines ( about 10 to 15 ) from the istallation sequence activities were all red, showing that something went wrong. Immediately I removed the batery to stop the process and installed the first version of the custom rom, using the TWRP. It worked fine and I received some notifications about the new revisions of the rom. I skipped the one that caused problems and accepetd the download the one on the Nov, 17, 2018 of the rom, and had installed. It appeared to me that everything was ok but, one day I turned the phone off during thje night. The next morning, I tryed to boot the phone without success. It started an infinite loop situation..... So, I tryed to repeat the same procedure to install the very first version of the rom using TWRP at the recovery mode. When I was using the TWRP to perform the advanced wipe, the dalvik cache, data and system could not be wiped. The answer about the problem was shown as : failed to mount /efes ( inavlid argument ).
I got the information that, in cases like that, the stock rom should be installed. I downloaded it from www.stockrom.net and had it istalled with the use of Odin. Unfortunately, the boot loop was there again.
What was worse now was that no TWRP was installed and Odin could not recognize the phone, although I had installed the newest set of drivers from Samsung, applicable to any devices from them.
Please I need your help to see if there is a possible solution to solve this case. Phone Model: GT-i9300 SSN -I9300GSMH - in Brazil
The message I got from the phone: E: failed to mount /efes ( inavlid argument )
{
"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 thank you in advance any help from you guys,
Gilberto Leite
Flashing a stock ROM will always replace TWRP with the stock recovery.
Are you trying to flash the latest stock ROM?
Do you have a backup of the EFS directory? It's an important directory as that is where a lot of information, including the IMEI is stored.
Hi Audit 13, thnaks for replying.
No I don't have the back up for the folder you mentioned. I was trying to install the last stock rom downloaded from www.stockrom.net, which I suppose was the last one. The worst part is that to computer does not recognize the phone since then.... I do not know what to do. I suppose that there is not a way to back up the folder you mentioned. I think that I have to install something from the very begining, as if the phone was to receive the installation of the very first program, as if it was just coming from the factory, totaly clean. Is that so? Am I right? And, how to do it? I tryed to download the stock rom from Samsung, but I think it was difficult and could not have it accomplished.
Thanks a lot and I'm still waiting instructions of how to solve this problem.
You should try using different USB cables and different USB ports to recognize the phone.
I assume you are using Windows since you mentioned Odin. When you connect the phone, do you see any new devices appear under Device Manager?
What is the phone's model # in download mode?
Is the the ROM you used: https://www.stockrom.net/2015/11/stock-rom-original-de-fabrica-samsung_19.html ?
Did you try using Odin 3.07?
Hi Audit13!
Thanks a lot for your help! I've already got hte files you mentioned and am preparing for trying to do the procedure you taught me.
Thanks again and soon, I hope, to be back to confirm whether it succeded.
Bie....
Hi Audit13,
Unfortunately the computer is not recognizing the SGS device.
I was ready to install the sock rom you suggested, had downloaded the Odin 3.07. I use Windows 10 and the latest drivers have been installed. The phone was in the download mode and tryed all available USB port. I've waited some minutes in each USB port for recognition with no success.
I thank you for your help. Is there any other method we could try? If you could please indicate, I thank you again.
Is there a method available using ADB procedures?
Hope there is.
Thanks, anyway for the help.
Hi Audit13
I think that the situation got a little worse. I tryed to do some recovery on the emergency recovery mode, but none of them succeeded. Now, what I get when tryng to get to the recovery mode is an android robot with an open belly with a red triangle coming out of it.... It gets to thedownload mode, but no recognition from the computer. This happened after trying to ionstall the stock rom obtained from the site you mentioned. The only thing that I could do was through the Universal-Android-Diag-Enabler-V2, what made the qualcomm start. Is there a way to make a comand to the phone that could star the USB debbuging? I tryed the various ODIN versions but with no success.
There is another problem - I'm using Windows 10 and the PowerShell uses different command lines not recognized by adb. I tipped devices and the program indicated that there was an mistake.
Is ther an Instructions Booklet for Odin?
What is your opinion? Do you think that there still exists a solution for my phone's case? If so, what to do?
Please, I ask you to help me on solving this problem.
Thanks in advance...
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