Hi, Guest! Login / Register




Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

[Please help] TECNO R7 INTERNAL SD CARD DAMAGED

#31

(06-10-2016, 01:24 PM)mensa Wrote:
(06-10-2016, 12:13 AM)Kingsident Wrote:
(06-09-2016, 07:44 PM)mensa Wrote:
(06-08-2016, 11:36 PM)Kingsident Wrote:
(06-08-2016, 01:38 PM)mensa Wrote: Yea try a new ROM download and flash again.

I flashed a fresh rom, it started rrom the beginning as normal the size flashed was increasing accordingly till 2.03gb was flashed, but as soon as it hit 100% the size flashed went down to 163mb and it was a success. The green tick came up then i tried to power it on but nothing, just the same dead phone but it gets warm after sometime. This flashing was done after formatting.

I got another rom from androidvillaz, it was very small in size about 92mb, the extracted system.img was 140 something mb, i flashed the rom and all of it was flashed, a total of 170 something mb. Tried powering it up but the same story; dead yet warm

Any remedy for this? This all started because i recieved an 'SD card is damaged' notification from internal sdcard

Dont flash the whole ROM. Flash only preloader, boot, uboot and recovery partitions; Then use adb to boot into recovery. But format before flash. Format whole except bootloader.
Can you please give me step by step instructions on how to boot into recovery with adb along with how to install it's drivers? I will greatly appreciate it. When I boot into recovery, what do I do next?
You can get the step by step info here; 
https://forum.hovatek.com/thread-588.html

I tried all I could but adb can't detect the phone even after installing the drivers


Reply
#32
(This post was last modified: 06-10-2016, 07:52 PM by mensa. )
Is windows detecting the phone?
Reply
#33
(06-10-2016, 06:21 PM)Kingsident Wrote:
(06-10-2016, 01:24 PM)mensa Wrote:
(06-10-2016, 12:13 AM)Kingsident Wrote:
(06-09-2016, 07:44 PM)mensa Wrote:
(06-08-2016, 11:36 PM)Kingsident Wrote: I flashed a fresh rom, it started rrom the beginning as normal the size flashed was increasing accordingly till 2.03gb was flashed, but as soon as it hit 100% the size flashed went down to 163mb and it was a success. The green tick came up then i tried to power it on but nothing, just the same dead phone but it gets warm after sometime. This flashing was done after formatting.

I got another rom from androidvillaz, it was very small in size about 92mb, the extracted system.img was 140 something mb, i flashed the rom and all of it was flashed, a total of 170 something mb. Tried powering it up but the same story; dead yet warm

Any remedy for this? This all started because i recieved an 'SD card is damaged' notification from internal sdcard

Dont flash the whole ROM. Flash only preloader, boot, uboot and recovery partitions; Then use adb to boot into recovery. But format before flash. Format whole except bootloader.
Can you please give me step by step instructions on how to boot into recovery with adb along with how to install it's drivers? I will greatly appreciate it. When I boot into recovery, what do I do next?
You can get the step by step info here; 
https://forum.hovatek.com/thread-588.html

I tried all I could but adb can't detect the phone even after installing the drivers

Can windows detect the phone?
Reply
#34
(06-10-2016, 07:28 PM)mensa Wrote: Is windows detecting the phone?

I preeed shift yen right clicked selected open command window here, when it started it was supposed to show the list if devices connected but it didn't so I typed in adb devices and the list comes up empty
Reply
#35
(06-10-2016, 07:59 PM)Kingsident Wrote:
(06-10-2016, 07:28 PM)mensa Wrote: Is windows detecting the phone?

I preeed shift yen right clicked selected open command window here, when it started it was supposed to show the list if devices connected but it didn't so I typed in adb devices and the list comes up empty
Okay when you connect the phone without adb opened. Do you see windows detecting the phone?
Reply
#36
(06-10-2016, 08:10 PM)mensa Wrote:
(06-10-2016, 07:59 PM)Kingsident Wrote:
(06-10-2016, 07:28 PM)mensa Wrote: Is windows detecting the phone?

I preeed shift yen right clicked selected open command window here, when it started it was supposed to show the list if devices connected but it didn't so I typed in adb devices and the list comes up empty
Okay when you connect the phone without adb opened. Do you see windows detecting the phone?

Wimdows does, though it trips, the sound for a connected device goes off amd on repeatedly. I connected another functional phone but adb could still not still detect it.
Reply
#37
(06-10-2016, 10:08 PM)Kingsident Wrote:
(06-10-2016, 08:10 PM)mensa Wrote:
(06-10-2016, 07:59 PM)Kingsident Wrote:
(06-10-2016, 07:28 PM)mensa Wrote: Is windows detecting the phone?

I preeed shift yen right clicked selected open command window here, when it started it was supposed to show the list if devices connected but it didn't so I typed in adb devices and the list comes up empty
Okay when you connect the phone without adb opened. Do you see windows detecting the phone?

Wimdows does, though it trips, the sound for a connected device goes off amd on repeatedly. I connected another functional  phone but adb could still not still detect it.

That means you did not configure adb properly. Uninstall everything. Every mtk driver and adb as well. Then restart the machine and after reboot; install adb. Enter yes hroughout the adb setup installatuon
Reply
#38
(06-11-2016, 12:44 PM)mensa Wrote:
(06-10-2016, 10:08 PM)Kingsident Wrote:
(06-10-2016, 08:10 PM)mensa Wrote:
(06-10-2016, 07:59 PM)Kingsident Wrote:
(06-10-2016, 07:28 PM)mensa Wrote: Is windows detecting the phone?

I preeed shift yen right clicked selected open command window here, when it started it was supposed to show the list if devices connected but it didn't so I typed in adb devices and the list comes up empty
Okay when you connect the phone without adb opened. Do you see windows detecting the phone?

Wimdows does, though it trips, the sound for a connected device goes off amd on repeatedly. I connected another functional  phone but adb could still not still detect it.

That means you did not configure adb properly. Uninstall everything. Every mtk driver and adb as well. Then restart the machine and after reboot; install adb. Enter yes hroughout the adb setup installatuon

The thing is I can't find the adb driver that was installed to uninstall it

Sent from my Tecno H5 using Hovatek mobile
Reply
#39
(This post was last modified: 06-11-2016, 06:56 PM by mensa. )
(06-11-2016, 06:16 PM)Kingsident Wrote:
(06-11-2016, 12:44 PM)mensa Wrote:
(06-10-2016, 10:08 PM)Kingsident Wrote:
(06-10-2016, 08:10 PM)mensa Wrote:
(06-10-2016, 07:59 PM)Kingsident Wrote: I preeed shift yen right clicked selected open command window here, when it started it was supposed to show the list if devices connected but it didn't so I typed in adb devices and the list comes up empty
Okay when you connect the phone without adb opened. Do you see windows detecting the phone?

Wimdows does, though it trips, the sound for a connected device goes off amd on repeatedly. I connected another functional  phone but adb could still not still detect it.

That means you did not configure adb properly. Uninstall everything. Every mtk driver and adb as well. Then restart the machine and after reboot; install adb. Enter yes hroughout the adb setup installatuon

The thing is I can't find the adb driver that was installed to uninstall it

Sent from my Tecno H5 using Hovatek mobile

I don't know if USB debugging is tune on; if tune on and still the same problem, connect the phone and navigate to device manager. You will see android phone. 
Click on it to open the dialogue google adb drivers and you can right click on it to uninstall the drivers.
When done, reboot the pc, then connect the phone whiles installing the adb
Reply
#40
(06-11-2016, 06:55 PM)mensa Wrote:
(06-11-2016, 06:16 PM)Kingsident Wrote:
(06-11-2016, 12:44 PM)mensa Wrote:
(06-10-2016, 10:08 PM)Kingsident Wrote:
(06-10-2016, 08:10 PM)mensa Wrote: Okay when you connect the phone without adb opened. Do you see windows detecting the phone?

Wimdows does, though it trips, the sound for a connected device goes off amd on repeatedly. I connected another functional  phone but adb could still not still detect it.

That means you did not configure adb properly. Uninstall everything. Every mtk driver and adb as well. Then restart the machine and after reboot; install adb. Enter yes hroughout the adb setup installatuon

The thing is I can't find the adb driver that was installed to uninstall it

Sent from my Tecno H5 using Hovatek mobile

I don't know if USB debugging is tune on; if tune on and still the same problem, connect the phone and navigate to device manager. You will see android phone. 
Click on it to open the dialogue google adb drivers and you can right click on it to uninstall the drivers.
When done, reboot the pc, then connect the phone whiles installing the adb

As at the time the phone was working USB debugging was on.
Adb can detect another phone when the phone is on but can't when it's off, isn't it possible for a adb to detect a phone while it's off


Sent from my Tecno H5 using Hovatek mobile
Reply










Users browsing this thread:
1 Guest(s)