Database Develop

How to recover brick after fail update to CM10? GT-P7300

Hi all.
I've used standart OS for a long time and I decided to install CM10 (JB) using Clockwork Recovery 6.0.1.8.
First of all, have installed Clockwork and put CM10 and Gapps in sdcard.
After that, i start tablet in recovery mode and 've installed CM10 via Clockwork. Without rebooting, i have installed Gapps also via Clockwork.
But i forgot to wipe device before that
So after rebooting i got animated video with triangles. Waiting for 20 minutes... nothing. After 30, i switched off device pressing power button.
After switching it on, there is that triangles...
I have entered to recovery and wipe all data, but device freezed on cleaning cache. I had no choice and reboot it.
But he kept silence, lol. Nothing happened, black screen. Recovery also didn't work.
Connecting to PC... Found XPA device (or not XPA, i forgot). So i googled about it and download and install special driver.
Now device defines as NVIDIA USB Boot-recovery driver for Mobile devices.
Odin cant see the device, ofc. Recovery isn't working.
nvflash --sync:
Code:
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
(After this comand, device autounplugged)
I don't know what to do, please help me to recover my brick.

kudos on the full and clear report.
but too many parallel threads for same issue
http://forum.xda-developers.com/showthread.php?p=31177035

eskimono said:
Hi all.
I've used standart OS for a long time and I decided to install CM10 (JB) using Clockwork Recovery 6.0.1.8.
First of all, have installed Clockwork and put CM10 and Gapps in sdcard.
After that, i start tablet in recovery mode and 've installed CM10 via Clockwork. Without rebooting, i have installed Gapps also via Clockwork.
But i forgot to wipe device before that
So after rebooting i got animated video with triangles. Waiting for 20 minutes... nothing. After 30, i switched off device pressing power button.
After switching it on, there is that triangles...
I have entered to recovery and wipe all data, but device freezed on cleaning cache. I had no choice and reboot it.
But he kept silence, lol. Nothing happened, black screen. Recovery also didn't work.
Connecting to PC... Found XPA device (or not XPA, i forgot). So i googled about it and download and install special driver.
Now device defines as NVIDIA USB Boot-recovery driver for Mobile devices.
Odin cant see the device, ofc. Recovery isn't working.
Could you tell us what kernel are you using? Apparently, from what i read in this forum cm10 with old HC kernel will not brick while wipe. Thanks.
nvflash --sync:
Code:
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
(After this comand, device autounplugged)
I don't know what to do, please help me to recover my brick.
Click to expand...
Click to collapse
Could you tell us what kernel are you using? Apparently, from what i read in this forum cm10 with old HC kernel will not brick while wipe. Thanks.

[Q] Device does not boot after twrp 2.8.5.0 update - Stuck at CM Logo

Hello everybody,
I am having severe trouble with my HTC one mini 2: After an update to TWRP 2.8.5.0 the phone gets stuck at the CM12 logo.
After I got the phone, I installed CM 12 with TWRP 2.7.1.0. Everything was working fine, besides the well known problem that TWRP freezes from time to time.
Yesterday I wanted to update to TWRP 2.8.5.0. I performed the recovery flash and everything seemed to work fine. Also I erased the cache. I used the following commands:
fastboot erase cache
fastboot flash recovery recovery-twrp-2.8.5.0.img
After that, I wanted to reboot my phone. Unfortunately, this did not work out at all. My phone does neither boot to CM12 nor to recovery. It does not react to the Power button. I can restart it by holding POWER + VOL UP but the phone gets stuck at the CM logo and will not move further. Also, I can not boot to recovery.
Also, the phone is not available via adb/fastboot. adb/fastboot does not show any attached devices. Adb/fastboot can only detect the phone, when the phone was running out of battery and is attached to the PC but not yet turned on. In this case, adb/fastboot detect the device, but mark it as "unauthorized" so that i can not connect to it.
I am kind of desperate. I hope somebody con help me with this issue.
Thanks in advance.
Cheers,
braumeister

hey guys,
does anybody have an idea what to do about this problem?
Is there any way, I can flash a new stock rom to the device via the SD-card?
Cheers,
braumeister

braumeister84 said:
hey guys,
does anybody have an idea what to do about this problem?
Is there any way, I can flash a new stock rom to the device via the SD-card?
Cheers,
braumeister
Click to expand...
Click to collapse
CM its very buggy and it sucks.
install previous version of TWRP and revert to stock.
Stock
TWRP
fastboot only works in bootloader mode
abd only works with system connected to PC

kativiti said:
CM its very buggy and it sucks.
install previous version of TWRP and revert to stock.
fastboot only works in bootloader mode
abd only works with system connected to PC
Click to expand...
Click to collapse
THX for your help.
Unfortunately I can not install another TWRP version as I can access my phone neither via adb nor via fastboot.
Both, "adb devices" as well as "fastboot devices" do not recognize my phone. Also I can not access recovery. I tried "POWER+VOL UP/DOWN" but it did not work.

Same problem
HEy guys,
like braumeister said... I have exactly the same problem.
Is anyone here able to help us? That would be great!

@fleischball
You are probably on a bootloop. A soft brick. It happens when you dirty flash ROMs.
The simplest solution is
- wipe dalvic cache/cache via your recovery
If this doesn't work
- wipe cache + dalvic cache + data + android secure.
- reflash your ROM
- again wipe dalvic cache + cache
- reboot
This method is called clean flash.
Hope this would be helpful for you.

hitman-xda said:
@fleischball
You are probably on a bootloop. A soft brick. It happens when you dirty flash ROMs.
The simplest solution is
- wipe dalvic cache/cache via your recovery
If this doesn't work
- wipe cache + dalvic cache + data + android secure.
- reflash your ROM
- again wipe dalvic cache + cache
- reboot
This method is called clean flash.
Hope this would be helpful for you.
Click to expand...
Click to collapse
Thanks, Hitman. But this wont work at first try because - like braumeister already described - we are not able to get into recovery or bootloader:
After I got the phone, I installed CM 12 with TWRP 2.7.1.0. Everything was working fine, besides the well known problem that TWRP freezes from time to time.
Yesterday I wanted to update to TWRP 2.8.5.0. I performed the recovery flash and everything seemed to work fine. Also I erased the cache. I used the following commands:
fastboot erase cache
fastboot flash recovery recovery-twrp-2.8.5.0.img
After that, I wanted to reboot my phone. Unfortunately, this did not work out at all. My phone does neither boot to CM12 nor to recovery. It does not react to the Power button. I can restart it by holding POWER + VOL UP but the phone gets stuck at the CM logo and will not move further. Also, I can not boot to recovery.
Also, the phone is not available via adb/fastboot. adb/fastboot does not show any attached devices. Adb/fastboot can only detect the phone, when the phone was running out of battery and is attached to the PC but not yet turned on. In this case, adb/fastboot detect the device, but mark it as "unauthorized" so that i can not connect to it.
Click to expand...
Click to collapse

After you reboot with pwr+vol up you have to hold pwr+vol down exactly when the phone reboots to enter bootloader.

doiutzu said:
After you reboot with pwr+vol up you have to hold pwr+vol down exactly when the phone reboots to enter bootloader.
Click to expand...
Click to collapse
THATS IT!!!! Thanks!!!!!!

Please Help KFHD7 (2012) Tate is not going past Kindle Fire Orange Logo

Hi,
I used KFHD SRT 1.3.5 to recover KFHD 7 (2012) from "Red Screen Of Death" successfully and it even updated itself to 7.5.1.
But it again developed RED screen falt within a day. Now even if I use different KFHD SRT versions right from 1.2 to 1.3.5 it is not recovering.
I also tried using bootloader, boot, recovery from Amazon 7.5.1 update.zip However it went till your Kindle cannot boot Reset or Reboot option screen.
Can I get system.img for 7.5.1 ? or is it due to some other fault.
Kindle Android Gurus, Please help

Using fastboot directly or KFHD SRT scripts, I can oem format, erase, flash xloader, bootloader, (Amazon/SRT) boot.img, (Amazon/SRT)recovery.img, (SRT) system.image successfully. but still the device does not boot up. Can expert throw light on this behavior.
How should I go about Is it hardware fault?

Now it has progressed upto TWRP but still no luck
Now I can go into TWRP after using MLO-pvt and u-boot-prod from Stock ROM 7.2.3 and then flashing 2nd Bootloader, TWRP recovery and freedom boot.img
However in mount menu, I am not able to mount data, cache, system partitions. Sometimes if I repair/format these partitions they can be mounted.
However it always say storage cannot be mounted....
Still struggling to get it back working. As stated earlier SRT worked only once and system got upgarded to 7.5.1 but now no version of SRT works.

I might be able to help
In TWRP project Hold down your power button and it should asy slide to unlock slide it then reboot back into recovery and it should work. if not click on wipe in twrp then advanced select everything then wipe then factory wipe then go back to advanced and wipe dalvik cache and cache then hold power button and slide to unlock then reboot back into recovery and try to flash something.

Kindle Fire HD 7" Stuck flashing the teamwin screen.

So after trying to install the cyanogenmod nightly, my device started displaying repeated errors about different processes stopping. This would not stop, so I tried to reboot the device. Now the device is attempting to load into the recovery section, but it has just reached the teamwin screen and just keeps going black then flashing back to the screen. Any way I can recover it, or should I finally retire it?

I'm having the same exact issue. Mine started after doing a factory reset from the system settings to try to alleviate some Play Store issues.
I'm just replying in the hope that someone will see this and help us out.

I got the same issue, I tried to factory reset the system and now mine keep flash at the teamwin screen. I cannot connect to the PC neither. Please help.

nicarasu said:
So after trying to install the cyanogenmod nightly, my device started displaying repeated errors about different processes stopping. This would not stop, so I tried to reboot the device. Now the device is attempting to load into the recovery section, but it has just reached the teamwin screen and just keeps going black then flashing back to the screen. Any way I can recover it, or should I finally retire it?
Click to expand...
Click to collapse
You probably didn't factory reset, wipe cache and wipe dalvik cache when you flashed the ROM.
usn.mustanger said:
I'm having the same exact issue. Mine started after doing a factory reset from the system settings to try to alleviate some Play Store issues.
I'm just replying in the hope that someone will see this and help us out.
Click to expand...
Click to collapse
Both of you, you can't factory reset a rooted device from the system settings, this usually wipes out the whole OS because with root the device has access to system partition, when you reset it wipes everything it has permission to remove(with root it has permission to everything).
Factory reset from settings on a nonrooted device doesn't wipe the OS because it doesn't have permission to alter system. That's why it doesn't harm the device and only wipes the data you've put on the phone.
Try flashing TWRP and see if your devices will boot to recovery then. If not, you may have to use fastboot to flash the stock firmware.
boy201 said:
I got the same issue, I tried to factory reset the system and now mine keep flash at the teamwin screen. I cannot connect to the PC neither. Please help.
Click to expand...
Click to collapse

nicarasu said:
So after trying to install the cyanogenmod nightly, my device started displaying repeated errors about different processes stopping. This would not stop, so I tried to reboot the device. Now the device is attempting to load into the recovery section, but it has just reached the teamwin screen and just keeps going black then flashing back to the screen. Any way I can recover it, or should I finally retire it?
Click to expand...
Click to collapse
Strange... is your tablet at least recognized by a computer?
Make sure you connect it to a USB 2.0 port

After factory wipe, won't load past boot screen

I just got the phone today.
I was trying to follow this guide to install lineageOS https://wiki.lineageos.org/devices/s2/install
Flashed twrp and got up to the 3rd part. I was about to start flashing the rom but the recovery mode was asking me for a password I didn't have. I never set a password on it.
So I tried doing a factory reset and now when I try to reboot it, it gets stuck on the boot screen with the LeEco logo and powered by android etc.
I can still boot into recovery. I tried wiping the cache and dalvik cache and factory reset it again but it didn't help. I didn't try wiping anything else yet since I'm afraid to break it.
I did get twrp on but I did not install any roms yet.
All I did was the factory wipe and now I'm stuck.
I have no important data on it, so I don't care if I have to reset everything.
If I can just get it back to factory default so I can start over, I'd be fine.
What's the recommended course of action?
Sorry I'm kind of a noob at this so detailed instructions would be appreciated.

I figured it out.
In recovery mode, mounted the phone to computer
Computer didn't recognize it at first so had to go to device manager and change the driver to read it as composite usb
Moved over the rom I wanted to flash and just installed it like I was planning to

Another possibility would have been an OTG adapter. You don't have any problem with windows drivers that way

motaku96 said:
I figured it out.
In recovery mode, mounted the phone to computer
Computer didn't recognize it at first so had to go to device manager and change the driver to read it as composite usb
Moved over the rom I wanted to flash and just installed it like I was planning to
Click to expand...
Click to collapse
So you flashed it with ADB?, cuz i have the same problem aswell.

somzkiller said:
So you flashed it with ADB?, cuz i have the same problem aswell.
Click to expand...
Click to collapse
Yes, I found it easier to flash through ADB.