bricked huawei g730 - General Questions and Answers

bricked huawei g730 - General Questions and Answers

hello there,
I have huawei g730-u10
"MTK6582, quadcore cortex A7, 1GB Ram, 4GB Rom"
last week, I was trying to install a CWM recovery using "mobile uncle" app. after it finished , a prompt for restarting appears and I pressed "yes".
it was the last time seeing my phone alive!!! it restarts to huawei logo for about 20 seconds and restarts again and again and again....
unfortunately my device doesn't have a rom online, even on HUAWEI website, so, I downloaded a similar phone ROM "hdc-s5-gold" to use its preloader, cache, boot , etc
the problem is when I connect the phone to SP flashtools the red bar appears and then it holds for seconds and a message with connection loss appears while the phone is going in its infinite restart.. so the flashtools seems to find the phone for a while but fails to write to it thanks to power loss.
notes:
1. I have tried many flashtool versions
2. I have tried with and without battery connection, and with and without volume up holding.
3. the phone can't access to CWM, download mode or factory reset mode.
4. the drivers are installed shows: "MT65xx preloader" and I think there is no driver problem
5. even when I connect the phone to charger, it keeps restarting and the charging logo doesn't appear
I appreciate any help

SP log files attached
thanks

I have same problem.How to solve it.

same problem, what to do???

elkhopoa said:
hello there,
I have huawei g730-u10
"MTK6582, quadcore cortex A7, 1GB Ram, 4GB Rom"
last week, I was trying to install a CWM recovery using "mobile uncle" app. after it finished , a prompt for restarting appears and I pressed "yes".
it was the last time seeing my phone alive!!! it restarts to huawei logo for about 20 seconds and restarts again and again and again....
unfortunately my device doesn't have a rom online, even on HUAWEI website, so, I downloaded a similar phone ROM "hdc-s5-gold" to use its preloader, cache, boot , etc
the problem is when I connect the phone to SP flashtools the red bar appears and then it holds for seconds and a message with connection loss appears while the phone is going in its infinite restart.. so the flashtools seems to find the phone for a while but fails to write to it thanks to power loss.
notes:
1. I have tried many flashtool versions
2. I have tried with and without battery connection, and with and without volume up holding.
3. the phone can't access to CWM, download mode or factory reset mode.
4. the drivers are installed shows: "MT65xx preloader" and I think there is no driver problem
5. even when I connect the phone to charger, it keeps restarting and the charging logo doesn't appear
I appreciate any help
Click to expand...
Click to collapse
Universal unbrick guide:
Terminology - types of bricks:
Soft brick - often occurs in the shape of a bootloop or any other problems with booting such as always getting to recovery or not getting past the carrier logo. This type of a brick, which shows some signs of life, can in most cases be fixed.
Hard brick - As the name implies, your phone can essentially used as a brick and it shows no signs of life. This kind of a brick is rare and in theory should be unfixable. However there are advanced methods of fixing your phones such as JTAG, but they require extra tools and accessories.
The decision:
Is my phone soft or hard bricked?
If you answer yes to all of the questions below you probably have a hard birck:
Test as said in order!
Nothing happenes when you hold or press the power button
You cannot get the screen to even turn on by pressing or holding any combination of buttons on your phone
Nothing happenes if you do the same as about but with your phone plugged into a charger
Nothing happenes when you plug your phone into a computer
When you plug in your phone into a computer it does not recognize it as a phone, storage or any other media device
Nothing happenes when you try all of the above again, but with removing the battery in between steps for 10 seconds and putting it back in again
Nothing happenes when you try all of the above again, but after leaving the phone plugged into a charger for 2 hours
If all of the questions are a "yes", then you either have a broken charging port and and a discharged battery or you have a hard brick.
The unbricking:
There are many methods of unbricking and they are all different to each phone. Here I will list the most common methods that often succeed.
Samsung users skip to 4. method.
1. If you have access to a stock recovery:
Method 1:
1. Shut down / turn off your phone.
2. Boot into Recovery mode – hold down the volume down button and then hold the power button (the button combination is different for every phone. Look yours up on Google)
3. Use volume keys to navigate the menus, and power button to select the menu items (Again, might be different for every phone)
4. Choose “Wipe Cache Partition”.
5. Choose “Wipe Data / Factory Reset” to delete all your settings and apps, using the correct ROM.
6. Reboot your device.
Method 2:
Download the stock rom for your phone. It should be in ".zip" format. Make sure it's the official version
(Find it by Googling something like "[your phone model] stock rom")
Put the file on your phone's external SD card.
Make sure that the rom is for your exact phone model.
1. Shut down / turn off your phone.
2. Boot into Recovery mode – hold down the volume down button and then hold the power button (the button combination is different for every phone. Look yours up on Google)
3. Use volume keys to navigate the menus, and power button to select the menu items (Again, might be different for every phone)
4. Select "apply update from external storage"
5. Navigate to the zip file you copied to your phone
6. Install it.
If you get Status Error 7 that means you didn't download an official stock rom.
2. If you have access to a custom recovery:
Method 1:
Try stock recovery method 1
Method 2:
1. Find a stable custom rom for your phone or if you want to download the stock rom
Make sure that the rom is for your exact phone model.
2.. Copy the zip file to the phone's external SD.
3. Install the zip
(If you have a custom recovery you probably know the drill)
3. If you have access to fastboot mode:
First install ADB and fastboot drivers (if you haven't already):
To install it on windows there is a handy tool called the 15 Second ADB installer which will install pretty much everything you need.
On Ubuntu install with:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
On Fedora:
Code:
sudo dnf install android-tools
On OS X using Homebrew:
Code:
brew install android-platform-tools
Once you have the drivers installed you have to find a recovery image for your phone to install a custom recovery.
You can try one of the popular recoveries such as CWM or TWRP.
You need to get the recoveryNameHere.img file for your phone.
Find it by Googling:
"[your phone model] TWRP recovery"
or
"[your phone model] CWM recovery"
Make sure that the recovery is for your exact phone model.
Now on your phone enter fastboot mode:
Turn your phone off.
You can try different button combinations. For my phone it's holding power and volume down buttons.
Once you're in fastboot mode plug your phone into a computer and open your terminal/cmd.
Type in:
Code:
fastboot devices
You should see a list of devices. There should be only one device ID number.
If you see the ID it's working. If you don't you didn't install the Google USB driver properly (on Windows) and if it says "'fastboot' is not a recognized command" or "No command 'fastboot' found" then you didn't even install your drivers.
If you have problems with installing Google "how to install adb and fastboot drivers"
Now that you know fastboot is working type in:
Code:
fastboot flash recovery C:\Path\To\Recovery.img
Replace "C:\Path\To\Recovery.img" with an actuall path of the recovery file you downloaded.
It should say success.
If it doesn't try to execute:
Code:
fastboot oem unlock
This will delete all data you had on your phone (games, game progress, apps...).
Now try
Code:
fastboot flash recovery C:\Path\To\Recovery.img
again.
Once you're done type in:
Code:
fastboot reboot
And your phone should still not work. Now what you have to do it try the custom recovery method above (number 2.)
4. If you have a Samsung device:
Try this tutorial of unbricking with Odin: click here

Related

No Recovery Mode - Flashing through Computer

Hi
I have an ASK 748SP tablet, model info "crane-evb v13" with Android 2.3.4 installed.
I have not had success with flashing a recovery mode.
My device is not on the ROM Manager list.
flash_image responds with "Error scanning partitions: No such file or directory."
The device was strangely rooted when I bought it from the retailer. The instruction manual strangely says to boot into recovery mode by holding Vol + and the power button. I called the support company and they said that a recovery needs to be installed first. Using Root Explorer there is no recovery folder. (/recovery) - is there supposed to be?
Sorry if all of that doesn't make sense. I'm a noob around here.
So my question is how can I flash a recovery mode on my device OR how do I flash a ROM via my computer? (and make backups.)
PS: I do not have fastboot and am hopeing to upgrade to ICS.
Any help would much be appreciated. Thanks.

Have you found anything out yet?
I purchased a 5 point capacative screen 7 inch tablet from Ebay (NEW) about 4 weeks ago. The name of this tablet is Tablet PC (LOL). But under About Device and model number I get the same crane-evb-v13, Android 2.3.4, Kernel Version 2.6.36-android. Other than a minor issues with a keyboard, a retarded partioning, and getting Netflix to stay in sync (voices and video out of sync) the unit has been fast, responsive, and over all good considering I paid $128 new for it.
Have you made any head way as to if this unit can be rooted?

My tablet surprisingly came rooted like I said, I have tried rerooting it but didn't succeed. Unfortunetly I have bricked my device but hope to recover it soon.
@I get the same crane-evb-v13, Android 2.3.4, Kernel Version 2.6.36-android
I have Android 2.3.4 too (or should I say I did, ) Kernal Version 2.6.36-android, and I too have minor issues with the keyboard.
Retarded partitioning - I think so too - once again - flash_image failed, I seem to have /mnt/sdcard instead of /sdcard. The sdcard is built in which kind of confuses me.
Thanks for your reply, hope you can get your device rooted. If you find anyway to install recovery mode, please tell me.
__________________
Yharooer

Try the zixoon ROM:
1.- The battery must be charged before making update.
2.- DISCONNECT! device from charger.
3.- Turn "off" and then turn "on" hardware switch on device.
4.- Connect Zixoon v78 USB "OTG" directly to the PC.
5.- Press and hold for some second first "MENU" and than "POWER" buttons together.
(Charger must be unplugged from the device!).
6.- The PC detected a new storage "VDfu" with some letter.
7.- Run the Zixoon Flash Tool.exe (on Windows Vista/Seven must be run with administrator privileges)
8.- Coose "Flash device" button at the left side and press "Start" button to begin the flashing process.
9.- Wait several minutes untill gets "Complete" message.
(Do not disconnect the USB cable during the flashing process!)
10.-Disconnect Zixoon v78 from PC
11.-Turn "off" and then turn "on" hardware hardware switch on device.
12.-Press "Power" button on devise for 3 Second.
I can't post the external link for download (I'm new user) but sure you can find it.

PM me. I may have what you need.

HELP! ROM Manager bricked my O3D - Is it fixable?

NOTE: Before we start, I have now googled it and in hindsight I probably should of left RM alone!
Anyway as the title states my O3D seems totally goosed! I selected the recovery flash in ROM Manager for P920, it rebooted and all it does now is show the logo for a second, vibrate then off. I tried the usual tutorial stuff...
Power button, Vol up battery in - it comes up 'USB Device Unrecognised' and then It also keeps popping up 'Unknown Device' however when I click on properties every entry is 'Unavailable'
Power button, Vol Down, battery in does nothing (tried it a million times)
If I do...
Power button, Vol up then apply the battery - Device Manager finds... 'LG Mobile USB Modem', 'MAP SMS' (Other Devices) and 'LGE Mobile Composite USB Device'
No sign of OMAP44xx so the flash tools don't see it... strangely LG Mobile Support Tool sees the phone and tries to update it however it says it has the latest firmware, when I use the update recover option it gets to 15% but then complains that it can't communicate with the phone.
Is it dead? :crying:
Any help would be much appreciated.

dont worry. its not dead. has happened to my phone a trillion times ..
all you need to is try as below:
1. without connecting phone to usb first hold down 3d button then volume down and keep pressing power untill it starts up and then off again , then release all 3 together as it is off and repeat (remember first 3d then volume down and then power). this time just let the power button go on lg logo but keep pressing the other 2.
2. if this doesnt work, then easiest method - download omap4boot for optimus v1.21 or all in one p920 v1.3 by XDA, remove battery, only press down the volume up button and while pressing connect usb. make sure you hear 1 ding of connect , 1 dong of disconnect then 2 dings of connect. after this the ding dong should end .. if you have all drivers installed , then it will install omap drivers. a window will pop up and everything will have a green check. once it does that you can install a custom recovery twrp or cwm using fastboot . boot into recovery and flash a rom.
still if doesnt work, have patience, post a reply and will tell other steps to proceed with .....

Thanks for your time RVBSD, unfortunately (although I will keep trying!)
In No. 1 - I get the first logo, but when I re-apply the 3D/V and power, I don't get the second logo.
In No.2 - I get the first ding/dong then just 1 ding, no sign of Mr OMAP! - I'll keep trying though.

Once u get the second ding and then this music stops, Open device manager. Look for lg usb modem and disable it. Then look for omap44 something. The device manager may be refreshing quickly. Somehow i had a chance to right click on omap device and chose update driver. Select manual and choose omap.inf from the folder that u have to download as per my previous reply. Restart computer and check again.
Alternatively you can install all inf manually, right click and install, before connecting the device.
Let me know
Sent from my LG-P920 using xda app-developers app

Again, thanks again for your input but I am still no further. I manually clicked the inf and it said it installed fine... but nothing changed in Device Manager. I then attempted to 'force' the driver on the unknown device, however after it installed it returned a 'Code 10' error... unable to start.
Even tried the service software 'LGNPST' but it couldn't even connect to the port! ho-hum...

i tried it again. even on my computer it didnt take the omap drivers this time.... strange .....
but i could install fastboot, then installed cwm recovery . then flashed a rooted rom and its working ...
1. Turn off your Phone, pull out battery.
2. download omap4boot-for_optimus-v1.21 (run "start_fastboot.bat" (it will wait until phone connected)
3. connect phone with USB cable without battery, the usbboot will start
4. insert battery while the usbboot is waiting, it gives 5 secs only
5. unplug USB cable the LG logo will appear with fastboot on top
6. download the attached files to your desktop and extract
7. open cmd and in cmd navigate to fastboot.exe location, where ever downloaded
8. run fastboot.exe from cmd and choose the cwm file to be pushed to your phone
command : fastboot -s flash recovery recovery-clockwork-6.0.1.9-p920.img
9. reboot device into recovery , try to wipe cache and factory reset and try to reboot
if this works it will take you to existing installed rom, then you can reboot to recovery and flash Su_Bbox_1.20.2_gazhead_signed.zip to root it
10. else copy a custom rom to sd card , insert in the mobile , reboot into recovery and flash the cutom rom

PLease help
CAn you tell me how can mount recovery partition

HELP Please; soft brick

Hi everyone.
Ok back in August I purchased an Oppo r7plus "m" version not knowing the difference, from a 3rd party seller. I know I probably should've waited until the phone would go on sale in Canada but I wasn't sure if it ever would. So anyways the phone worked great for a while. I noticed that it came pre loaded with OPPO Tools and Super SU. I thought wow, this phone is rooted right of the box? Great! So I started uninstalling some native apps of which I thought were just "bloatware", everything went fine until I uninstalled the weather app.
When I turned the phone back on after restarting, it now goes into the OS but continuosly flashes on and off and you can only access the dropdown notification screen. Luckily from there I can still access the settings menu. I tried holding the power button and volume down button to go to the factory boot screen. That worked and in there its says the color os version, but in brackets says
(rooted).
I can only assume the phone is still rooted but is stuck in some sort of soft brick. I've been doing alot of reading into how I might be able to fix the phone but I'm having trouble figuring it out. I'm good with computers and all but not to this level and I never rooted an android phone before.
Please somebody HELP.

So I've downloaded the ROM for my phone model, r7 plus m, and I transfered the zip file over to the internal storage of the device. I then held down the volume down and power buttons to boot to color os recovery. Than I cleared cache and install from sd found the zip file and it started to run.
After about a minute or two into the installation it stops and reads "Installation Failed". I'm thinking I need a recovery.img file but I'm not sure. Even if I had that file I don't know what to do next.
Anyone have any ideas?

NALSONSON said:
So I've downloaded the ROM for my phone model, r7 plus m, and I transfered the zip file over to the internal storage of the device. I then held down the volume down and power buttons to boot to color os recovery. Than I cleared cache and install from sd found the zip file and it started to run.
After about a minute or two into the installation it stops and reads "Installation Failed". I'm thinking I need a recovery.img file but I'm not sure. Even if I had that file I don't know what to do next.
Anyone have any ideas?
Click to expand...
Click to collapse
Hi, how did you sort it? Are you still in need of stock recovery? I have one for model F, dont know if it works with M model.

1. Download and extract my RAR files ---> HERE
2. Open your PC device manager
3. Connect an usb cable only to your pc then press and hold the phone volume + button and then connect the usb cable to the phone
3. In the device manager you will see Qhsub_bulk then release the volume+ button
4. Right click on Qhsub_bulk and choose update driver
5. Use one of the driver folders which you alredy extract to install the Qualcomm driver and you will see it like 9008
6. Your phone have to be charged very well for a few hours before you try to flash it.
7. Remove it from the charger then connect an usb cable only to your pc.
8. Try to press and hold the volume + and power buttons at the same time for a few seconds and connect the usb cable to the phone.
9. You have to see the driver in the device manager like 9006 (you can release the buttons) [it wasn't easy for me so keep trying]
10. Open the MSMDownloader and press start
11. If everything is ok you will see a green progress bar flashing. (I was stuck here with the "NON-HLOS.bin" file which you can see in the "Other NON-HLOS File" folder inside the rom which you download)
12. When the process complete in about 10 minutes you can remove the usb cable from your phone.
13. Now you have to do a veeeeeeeery long press and hold on your power button untill you feel the vibration and after that you will see the OPPO logo.
14. Leave it for 5-10 minutes to load the Color OS.
15. Ok you have a working phone but still some apps icons that are missing and the keyboard doesn't appear when you have to write something.
16. Download THIS zipped ROM and put it in the internal storage of your phone.
17. Shut down the phone then press and hold the volume - and the power button at the same time for a while intil you enter into recovery mode.
18. Choose english and then install rom from zip file. After the installation complete reboot the phone and you will get a working keyboard and few more apps like Browser, Chinese market and else....
For me i still need to insert the IMEI's because they are lost... and now i have message: Oppo nv backup. The NV partition is invalid...
Good luck to all! And if you want to give me a beer: paypal: [email protected]

Still stuck
I still can’t detect any qhsub_bulk in device manager. Even I reformat my pc to window 7 64bit it still not detecting. What it detected was only like Android usb.
Oppo r7 plusm suspected soft brick with rooted.
- stuck at oppo logo
- try recovery with stock rom but error * failed to update*
- wipe all but still same failed to update
- try the guild here but can’t detect my device with the tool

Shield Tablet problems: ADB, Recovery Mode, Fastboot... = DEAD?

I can imagine that you all are tired of reading this headline, but seriously, ME TOO.
I have been looking for information about this issue during several weeks and I have not found any solution, so I would extremely thank you if you take your time reading this problem and trying to help me finding a solution.
Some months ago I tried to flash a ROM on my Shield Tablet, I followed all the steps from a topic in this forum: [Complete Guide] SHIELD Tablet K1 Root, Custom Rom and Xposed Framework but I wanted to try a different ROM: CARBON-CR-5.1-MOO-WEEKLY-shieldtablet-20170216-0454 (the name of the file) And now I have a tablet that is stuck on the Carbon launch screen every time I turn it on, when I press volumen down + power it goes into the screen buttt as soon as I press recovery mode the only thing it does is to restart itself and stays stuck in the NVIDIA screen. The Minimal ADB and Fastboot do not recognize the tablet with the adb devices command.
When I turn on the tablet (and stays stuck into the IOS icon as I mentioned before) and connect it to the PC the device manager recognize the tablet as a Portable device with the name: MTP USB device, when I press the power+volumen down the PC recognize the tablet as an Android Device -> Android Bootloader Interface. And this is all the information I have about my problem...
May you help me?
Thank you in advance. I hope your knowledge will help me and other people with the same problem. If you need more information of this problem let me know and I'll answer ASAP. If you have any idea tell me and I'll try it.

Warlain said:
when I press volumen down + power it goes into the screen buttt as soon as I press recovery mode the only thing it does is to restart itself and stays stuck in the NVIDIA screen. The Minimal ADB and Fastboot do not recognize the tablet with the adb devices command.
When I turn on the tablet (and stays stuck into the IOS icon as I mentioned before) and connect it to the PC the device manager recognize the tablet as a Portable device with the name: MTP USB device, when I press the power+volumen down the PC recognize the tablet as an Android Device -> Android Bootloader Interface. And this is all the information I have about my problem...
May you help me?
Click to expand...
Click to collapse
Your device is not, dead, it's only taking some time to reflect
First of all, I understood that you're able to access to the device's bootloader menu, through the button combo (black screen with white text, "continue","restart bootloader","recovery mode"), and you selected "recovery mode".
Now, unless you have flashed a custom recovery, there's nothing to do with the shield's stock recovery, so, just enter in the bootloader menu as you did, without selecting any option.
You are now in "fastboot mode", in order to check your device's connection you have to write in the adb shell
Code:
fastboot devices
If you see your device you can now boot a custom recovery that will help you to fix the problems you caused, I would follow this link: (copy-paste, can't post links)
"nvidiashieldzone.com/shield-tablet/shield-tablet-root/root-shield-tablet-v1-marshmallow/"
And do the 8th step, in "Root procedure"
Fastboot with TWRP
Type “fastboot devices” Copy and make sure your Shield Tablet is visible.
If your Shield Tablet is listed, type “fastboot boot twrp-20151227-EXPERIMENTAL-shieldtablet-m.img” Copy (or whatever you named it) and hit enter. If your TRWP image filename has a space in it, you may have issues.
After 15 seconds or so (be patient), you should see the TWRP Recovery screen. Note: This experimental version has some UI issues, just keep at it.
You may be prompted with something to do with the system being READ ONLY. Accept the default and swipe.
Click to expand...
Click to collapse

Use fastboot to wipe cache (fastboot erase cache) then try to flash TWRP (with fastboot) again. This will often clear up issues with being unable to boot to TWRP (at least on other devices).
If you are able to boot TWRP, restore the TWRP backup (if you made one) or put another ROM on the phone, and flash it.

I also have this kind of problem. After i update twrp by flashing it and restore a backup the sistem doesnt show. Stucks on nvidia logo. I tried even restore my recent backup but nothing also. Any idea ?

'Artemis' said:
Your device is not, dead, it's only taking some time to reflect
First of all, I understood that you're able to access to the device's bootloader menu, through the button combo (black screen with white text, "continue","restart bootloader","recovery mode"), and you selected "recovery mode".
Now, unless you have flashed a custom recovery, there's nothing to do with the shield's stock recovery, so, just enter in the bootloader menu as you did, without selecting any option.
You are now in "fastboot mode", in order to check your device's connection you have to write in the adb shell
Code:
fastboot devices
If you see your device you can now boot a custom recovery that will help you to fix the problems you caused, I would follow this link: (copy-paste, can't post links)
"nvidiashieldzone.com/shield-tablet/shield-tablet-root/root-shield-tablet-v1-marshmallow/"
And do the 8th step, in "Root procedure"
Click to expand...
Click to collapse
Done, Thank you a lot! It starts working again!!!

Neffos X-1 stuck in bootloop

Heya folks,
I have just attempted my first time flashing TWRP on my TP-Link Neffos X-1 following this guide: https://rootmygalaxy.net/twrp-root-...nd_Install_TWRP_Recovery_On_TP-Link_Neffos_X1.
Its looking kinda grim. It starts with the orange state Message and that the device will boot in 5 seconds, however after that it starts with an infinite bootloop. I also cannot access the Recovery (vol up + power), for it simply doesnt work anymore after the guide. When I plug it into my pc, it will automatically start with the bootloop (I can shut the phone off with vol down + power).
Attempting to get into fastboot mode over ADB (adb reboot bootloader), returns with the message error: device '(null)' not found. I think that is due to it not being recognized in the device manager(it doesnt show my phone anymore but unknown device). I tried to install the phone driver for the uknown device, however that keeps failing. I think its due to the phone permanently connecting and reconnecting to the pc.
So I'm wondering of what to do. I guess the biggest issue is that the drivers are not recognized, but as long as the phone keeps on restarting every couple of seconds i doubt i can properly install the driver. You guys got any ideas?

My guess is you haven't installed on Windows PC the appropriate Android USB Driver matching the device

I mean the appropriate USB driver had to be there for me to flash it with the TWRP in the first place, right?

Think I clearly said that the additionally required USB-driver has to be installed on Windows PC.

I have this one installed https://rootmydevice.com/download-neffos-usb-drivers/, is this the additionally required usb driver?

So far, despite what driver I pick for the device, it shows the code 10, device couldnt be started - probably because it never gets past the starting screen but keeps rebooting

slayingduck said:
Heya folks,
I have just attempted my first time flashing TWRP on my TP-Link Neffos X-1 following this guide: https://rootmygalaxy.net/twrp-root-...nd_Install_TWRP_Recovery_On_TP-Link_Neffos_X1.
Its looking kinda grim. It starts with the orange state Message and that the device will boot in 5 seconds, however after that it starts with an infinite bootloop. I also cannot access the Recovery (vol up + power), for it simply doesnt work anymore after the guide. When I plug it into my pc, it will automatically start with the bootloop (I can shut the phone off with vol down + power).
Attempting to get into fastboot mode over ADB (adb reboot bootloader), returns with the message error: device '(null)' not found. I think that is due to it not being recognized in the device manager(it doesnt show my phone anymore but unknown device). I tried to install the phone driver for the uknown device, however that keeps failing. I think its due to the phone permanently connecting and reconnecting to the pc.
So I'm wondering of what to do. I guess the biggest issue is that the drivers are not recognized, but as long as the phone keeps on restarting every couple of seconds i doubt i can properly install the driver. You guys got any ideas?
Click to expand...
Click to collapse
Try this TWRP file: TWRP_3.2.3_NeffosX1_TP902A_by_kiruha_21.img

The thing is, I cannot flash anything due to my phone constantly rebooting while inserted in the pc usb-slot. Neither ADB nor my device manager recognize the device and as mentioned before, I cannot install any drivers

slayingduck said:
The thing is, I cannot flash anything due to my phone constantly rebooting while inserted in the pc usb-slot. Neither ADB nor my device manager recognize the device and as mentioned before, I cannot install any drivers
Click to expand...
Click to collapse
Some MTK devices has this: Press both VOL+ & Power buttons. Only remove 2 buttons when you see Bootloader mode (recovery; fastboot; reboot system) or directly in the Recovery mode. Now you can use fastboot.
With the SPFT you can use same tip above. In the SPFT choose DOWNLOAD and plug USB device. Process to flash stock ROM or stock recovery.img & boot.img start.
If not start pugging USB: choose DOWNLOAD - press VOL- and plug USV device. You can try with buttons like only VOL- or VOL+ or combo buttons VOL+&VOL- or VOL-&VOL+ or other button combination.
You can try FIRMWARE UPGRADE too.
That's depend about LOCKED or Unlocked bootloader process that you made before actions!
If you unlocked bootloader so only need patience. If not so that's no good.

Database Info

welcome