ads

Affichage des articles dont le libellé est Softbrick. Afficher tous les articles
Affichage des articles dont le libellé est Softbrick. Afficher tous les articles

dimanche 20 septembre 2015

Weird Soft-Brick, Need Help!!!



Hi all,
I started out on TWRP version 2.7.1.0, and I wanted to flash the latest TWRP recovery (2.8.7.0), so I used the app that was linked by the TWRP site (TWRP Manager). So I tried to flash the latest update, and then a message pops up telling me to check if this was the right partition. I was careless and I didn't check it, and went ahead and installed it. It said it failed, but next thing I know, every time I tried to reboot(into the system/OS) I just boot right into TWRP (version 2.8.7.0). Then from TWRP (2.8.7.0) I tried to reboot into recovery, and it rebooted into TWRP, except that it was version 2.7.1.0, where I started.
So, when I hit boot into system, I got TWRP (2.8.7.0), and when I hit boot into recovery, I got TWRP 2.7.1.0. I was completely confused, so I wiped the OS, and then booted into fastboot to fastboot flash TWRP(2.8.7.0) in my recovery (It worked). Right now, I'm soft-bricked so I don't have an OS, but I have TWRP(2.8.7.0) as my recovery. Except now, I still get TWRP when I try to boot into system, and fastboot flashing, adb sideloading, and regular TWRP flashing is not working...:confused::confused::confused:
Any help is very appreciated, I need my phone to just be working!!! Except, if anyone can help me update it to 5.1 while they're at it, that would be awesome!



vendredi 28 août 2015

[Q] possible permanent soft-brick tf700t



So, I just managed to get the Bootloader unlocked, flashed CWRM and then accidentally hit the factory reset button from the system settings menu, and am now stuck in the reset recovery screen.

I have access to adb but not fastboot. I have not done anything with NVFLASH

Am I permanently screwed for this motherboard or can I still be recovered?



Nexus 4 OTA soft-brick help



I was updating my Mom's Nexus 4 to 4.4 (with the intention of bringing it to the current version to address various security issues -- like stagefright), but it appears to have "soft-bricked" as some people are calling it.
- locked bootloader
- not rooted.
- stock firmware

It goes into a "bootloop"? Where the Google logo displays forever (at least 30 minutes) w/o doing anything.

Normally I'd have spent more time doing this (e.g. backing it up, etc). But due to various personal mishaps in the past year, my tech environment is incomplete and a mess. I've never had problems w/ OTA updates so I foolishly went ahead w/o an adb backup -- which would have at least given me most files (even if I have to redo the entire setup). Also, due to poor timing, I was in a rush to get this done so she'd have a week or so before her trip to get used to the small changes (yes, she freaks out over small changes like the camera UI being different). So, whenever you're doing 2 things at once, you never pay attention to one thing fully. And this is also what happened to the OTA update -- so if there were ANY error messages or anything during the update, I did not notice. =(

Unfortunately I also don't have the device in front of me (things like work get in the way of personal masochism -- aka playing with tech).

Anyhow... I'm not exactly certain if it was going to 4.4. When I downloaded the OTA images for the Nexus 4 for 4.4 and tried to flash using the flash-all tool, it complained that the bootloader was not the right one. When I pulled down 4.3 and tried to flash, it did not complain about that bootloader version. So perhaps it didn't properly flash the bootloader? In any case, is there any chance of getting at the files now before a wipe?

What confuses me, is why I cannot flash w/ a STOCK image. Aren't they signed? Even with a locked bootloader, couldn't it in theory let the right images in?

Also, I'm normally in a windows environment, but due to my machines all being down, I'm on the work MacBook Pro instead. So unfortunately I can't try WugFresh's rootkit -- although I'm not sure it would help w/ a locked boot loader.

So... the questions are:
1) Is there a way to flash to a stock OTA image w/o losing data?
2) Or if that's not possible, is it possible to get the data from the phone?
3) Or I'm out of luck and I shouldn't waste any more time trying to recover what's lost?

(Btw, I didn't lose everything -- e.g. I have photos, sms and call logs backed up. WhatsApp used to be backed up, but it seems like both the 3rd party solution and WhatsApp themselves have stopped supporting some sort of offline backup. So mainly just concerned about files in Downloads or Documents or something -- everything else I've made sure was "on the cloud".)



jeudi 27 août 2015

Softbrick on my galaxy note 10.1 2014 p605



Hello everyone!
Yesterday I wanted to flash my tablet with an updated firmware as in the country I'm in we don't get updates automatically. Also I wanted to clear the tablet of junk so I used TWRP to clear everything: Note: I had been rooted before, using towelroot.
  • Dalvik Cache

  • System

  • Data

  • Internal Storage

  • Cache

Then I downloaded the 2015 Kit Kat 4.4.2 version from Sammobile. The day after I used ODIN to flash it but I believe the USB cable might have gotten disconnected, as it has sort of worn out, during the process. Also: From the very beginning Odin didn't show the model name, which I found strange. I tried flashing it again with a different cable but now it failed at hidden.img.ext4.
Afterwards I (probably stupidly) tried to flash it again with the NAND ERASE ALL option -derpface- enabled - obviously it still didn't work. Then I couldn't boot into recovery anymore. I am not certain it was at that point that recovery stopped working, could've been earlier. Pressing the usual combination for recovery (power + Volume Up) instead boots into Download where it says:
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SM-P605
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 0X1 (4)
QUALCOMM SECURE BOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A2, P2
UDC START
Normal booting just gets you stuck at the SAMSUNG Logo.
Pls help