Database Users

[Q] Need to unbrick Defy+ - Strange problems

Edit: All happy now, a change of pc solved the problem of not detecting the device!
Hi all! I have another challenge for you!
Right, I've got myself in a tizz with my Defy +. While updating between CM10.1 versions I found myself in a situation where I couldn't get past the boot animation. So I loaded the TWRP restore I had made prior to updating...
Except it wouldn't, instead it came up with 'Failed' each time I tried any of the TWRP backups I had created. So the next step was to wipe partitions and start flashing various ROMs until I found one what worked. Except they didn't work either. Eventually I thought the best idea would be to just turn the phone off and see where I was with booting.
So power on, boot logo, blue light, red light then... nothing. Just the boot logo static. Went into the custom bootloader to go into recovery again, nothing. Pressing Custom recovery simply loops back to the top bootloader screen.
Ok next step, flash .sbf and start from scratch. So into the Moto bootloader it is to plug in and flash except... it's no longer detected by my computer.
"Ok" I think, "We'll just flash files from the SD card after I use an external SD card reader.
Except now when I enter Moto recovery to flash the TWRP recovery I get:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verifiaion failed
Installation aborted
So to recap:
1) Tried to flash and update, failed
2) Tried to recover, recoveries wouldn't write (I think this is becaue I'd changed to EXT4 on /data and /cache and had forgotten to go back to EXT3 before trying to recover)
3) Tried to boot, epicly failed
4) Tried to flash .sbf, Defy+ won't appear in RSDLite 5.7 with latest driver
5) Tried to flash from SD card, sig verification failed
6) Googletastic for the last four days
Notes:
a) I CAN charge the Defy+ using the wall charger but I get '?' for the battery level indicator but...
b) In Cmod bootloader 2.1 (Which I can use a little) it shows the correct battery level
c) I /was/ getting some errors with not being able to mount /cache from the moto recovery but I've since used the cmod bootmenu 2.1 to set it back to ext3 and it's all happy now, those errors aren't appearing
d) Plugging in my Defy red lens I get W8 x64 detecting the correct portal drivers and such but when I go to moto bootloader this device also doesn't appear in RSDLite
e) Both devices prompt windows to install a Motorola Flash Interface driver in Device Manager when plugged in in moto bootloader mode and neither device appears in RSDLite despite the fact the program is running in Admin mode
f) Looking at the logs in bootloader, it appears that I might not have formatted anything from ext4 to 3, everything I select in the cmod bootmenu returns .E:Error in /system/... , (Result: Invalid arguement) , Done..
So at the moment I think I need to acheive one of the following:
1) Find a file that allows me to write any useful data to /system like a recovery or some of those bootmenu files that passes the signature verification
2) Find a way to troubleshoot RSDLite so I can actually flash .sbf and get out of this hellhole
Many regards!
Alexis

If your custom recovery is not working, then you cannot do anything other than flash an sbf(nothing except data and cache wipe can be done via stock recovery): this is due to the locked boot loader(recoveries cannot be simply flashed from the stock recovery as you're trying to do)
Sent from my MB526 using Tapatalk 2

Success (ish)!
Yes I swapped to a different machine and then upgraded the version of RSD Lite installed on it from 4.7 to 6.1.5
[URL="http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239"]http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239
And flashed the 'lower' of the two .sbf's from the links on this forum for the British variant. After a DEA1 error (Phone is dead, code corrupt and all the bad things) I managed to flash the file.
As of yet I've not managed to get out of the bootloop but I've not carried out the requisite steps as mentioned in the "So you think you've bricked your Defy/Defy+" thread.
Lessons learned:
1) Motorola drivers and RSD Lite are pennickety, you will probably need to mix them up in order to get them to behave properly
2) If all else fails, use a different computer
3) You will probably need to flash over and over, while making every effort to not muck them up. Be aware the efuse system only has limited uses before it's useless though...
My saga continues, from no USB support hopefully to a fully working device again
In the end switching PC then doing the factory reset from moto recovery let the phone boot, all standard but the dodgy USB stuff at the first post is what sent me away from the right track.

Help with rooting G906S Marshmallow 6.0.1 (tried CFire, TWRP and kingroot)

Hi, I've just recently switched over from iphone to android so I'm still new to the whole system. Anyway I've been trying to root my phone for the past 2 days to no avail so I'm at my wits end here. Before I start my phone is from korea which I don't know if whether or not impacts its ability to be rooted, I've done all the basics like enable USB debugging from dev mode, install samsung usb drivers, open ODIN in admin mode and allow MTP to computer. My Device details are below:
>Baseband version : G906SKSU1CPF1
>KERNEL : 3.10.40-8533426
>BUILD NUMBER : MMB29M.G906SKSU1CPF3
So anyway I first tried flashing using CF autoroot for sm-G906S with odin which while it said it was passed and was successful on pc it would be stuck on the samsung logo with a message at the top left that said :
>Recovery booting
>Recovery is not seandroid enforcing
>set warranty bit recovery
So then I tried flashing TWRP custom recovery and putting Super user zip in the internal storage which although got my phone back to working order still wouldnt let me root as the process required me to go to recovery mode from the fastboot mode after it was done flashing (I tried both with and without autoreboot), however once the flashing was done on fastboot I couldn't get to recovery mode no matter how long I held the Vol up/power/home button combination and when i tried it after rebooting it would show normal recovery mode hence there was no way to install the Super User. (Also attempted this with phils recovery)
I then tried to do the TWRP method using adb with command prompt however it would get stuck saying waiting for device when i tried to flash and needless to say kingroot also failed.
At this point as far I've gone through all the methods I could find for my particular device. Would greatly appreciate any insight or advice regarding this problem.
Thanks

start reading from here http://forum.xda-developers.com/gal...ner-thread-t2807639/post68725608#post68725608

Bootlooping to Factory reset status

Hello,
I'll try to detail as much as I can to explain how i ended up Bootlooping :
I tried today to root my LG H870. (imported from Germany, according to the seller).
I followed the tutorial on xda to unlock the Bootloader on the device.
After flashing it, it launched Android the 1st time without difficulties.
I rebooted into TWRP, flashed supersu, then rebooted into Android. Problems started there, the system told me my partition was encrypted, and asked if i wanted to reinitialize it. After doing so, it's been stuck, bootlooping to TWRP, the internal partition empty.
I followed numerous tutorial on how to flash a stock ROM through TWRP, Fastboot, ADB Sideload, without any success.
With TWRP, it was always ending up saying the flash wasdone, without writing a single file in the partition.
I also tried installing stock ROM with LGUP, but once again, didn't seem to work. While in download mode, it was either telling me the phone was an unknown model, on port COM3, or that there was no handset connected.
I then followed another guide, using LG Firmware Extract and LG Flash Tool. It didn't work as expected, but, I don't really know how, it made LGUP seeing my phone correctly. I was then able to flash a stock ROM (H87010f). No error during the process.
After the LG Logo, i get now a blue screen, saying for some seconds "Encryption Progress", and after that "Factory Reset Status", with a big red "2", and it gets stucks there.
Once again, if I get into download mode and into LGUP, i get now the "no handset connected" message.
Is someone on here able to help me?
If more infos are needed, tell me, i'll try to answer!
Thank you all!

zenfone 5LTE (A500KL) self brick

moms zenfone 5 lte decided to brick itself during an update, it will just stay on the asus logo loading forever.
I tried re-flashing the boot and reovery images worked but didn't do anything towards fixing the boot process.
it will still boot into fastboot flash mode and sd card recovery modes.
attempting todo anything in sd recovery mode spits out multiple errors about not being able to mount the /cache partition (wiping cache, flashing from external card etc)
can't really do much in fastboot mode because the device is not "unlocked" (need to boot OS enable usb debugging and pair with the PC to do anything for "security" hate whoever came up with that)
seems unlocking the bootloader for TWRP and wipe/format the cache via comamnds are not options because of above?
found an unbrick thread but says it dosn't work un zenfone 5 LTE
been trying a few hours kind of stuck and looking for solutions.
any suggestions please ?
Thanks
ps:sorry meant to post this thread in the help section

seems it may be fixable using asus flash tool and flashing a raw image but I am unable to find a raw image for the A500KL model

(Help needed) Soft bricked Tmobile Note 4 with way way WAY too many error messages.

So, I have here a great old Note 4.
It has the generic mmc errors that cause it issues when booting and sleeping so I decided to give it a new rom. I bumped it into developer options, enabled usb debugging and fastboot and turned it off. I opened up odin, found the right twrp file to flash as well as a stock rom. I loaded it up and fired. The issue then was that the PIT partition had issues. Pit partition failed on odin's side, and flash read failure as well as a pit error of some sort on the phone's side. So I did my homework. I then tried to flash a new .pit file, I made sure the boxes were filled out correctly, had the right pit file as well as a correct stock rom, and the right drivers. It failed again with exactly the same errors. I don't know how you can manage saying that you can't flash the file your trying to fix but whatever. So I did more research and continued to change the usb cable to the original one that came with the phone, change the usb port, change versions of odin, use administrator privileges, find another .pit file, and change the pc. None of these worked, they all gave the same errors no matter what I did. So I moved on to see what else I could do, there was only one more issue though, the phone wouldn't boot up to an OS, if I tried to boot up normally it would boot into recovery, and if I booted into recovery it would boot into download mode with a message saying that the mme error caused it to. SO I couldn't do anything like flashfire or rom manager nor could I do something like root the device! So I did more homework, I turned to adb, because I saw something about an alternative to odin. Unfortunately, the phone has to boot up so you can connect it properly before you boot into download mode. So I did more homework and can't get anywhere, I am completely lost as to what to do because I can't flash odin or adb and sd card can only flash .zip files. I have no idea where to find a .zip for cwm or twrp that will work for my phone and the 2 files that I thought would work only gave me errors. I definitely am drowning in error messages and hope someone who knows what in the world is going on can help me get out of this mess.
Sincerely,
TiffPiff