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.

Soft bricked Nexus 6P, bootloop

EDIT: A lot of Users have the same Issues, read about it here: https://productforums.google.com/forum/#!topic/nexus/iPnYjg322Q8
Edit2: this thread can be closed, thanks.
Hi,
i am stuck in a bootloop. I tried to find a thread with the same issue, but i wasn't succesful.
So here's what i've done and what's my problem.
Problem:
The Phone is stuck after the google logo, restarts .
i CAN get into TWRP/recovery/bootloader
what i did:
I flashed the factory images (even different versions) both via flashall.bat and manually typing.
after that i tried a new install and hard reseting, erasing cache afterwards.
I treid to adb sideload the Full OTA Roms, no luck either.
I tried installing Custom Roms(lineage, DU)/ EX Kernel on top of stock rom.
& the usual stuff like changing pcs, cables and usb ports.
The Flashing works fine everytime.
When i connect my N6P to my pc after flashing, it says 110GB free out of 110Gb.
EDIT: when i open file manager in twrp, i see a lot of folders (root, recovery, system, cache boot etc)
I thought maybe it is a permission problem or a filesystem problem?
Maybe i need to change filesystems in twrp?
please shre any ideas with me, i appreciate your help. My ohone is now bricked for nearly 24hours... I have no backup phone.

madddiiin said:
Hi,
i am stuck in a bootloop. I tried to find a thread with the same issue, but i wasn't succesful.
So here's what i've done and what's my problem.
Problem:
The Phone is stuck after the google logo, restarts .
i CAN get into TWRP/recovery/bootloader
what i did:
I flashed the factory images (even different versions) both via flashall.bat and manually typing.
after that i tried a new install and hard reseting, erasing cache afterwards.
I treid to adb sideload the Full OTA Roms, no luck either.
I tried installing Custom Roms(lineage, DU)/ EX Kernel on top of stock rom.
& the usual stuff like changing pcs, cables and usb ports.
The Flashing works fine everytime.
When i connect my N6P to my pc after flashing, it says 110GB free out of 110Gb.
I thought maybe it is a permission problem or a filesystem problem?
Maybe i need to change filesystems in twrp?
please shre any ideas with me, i appreciate your help. My ohone is now bricked for nearly 24hours... I have no backup phone.
Click to expand...
Click to collapse
So if i go into twrp/wipe/advanced
select system + repair r change filesystem it says:
Size: 2929 MB, Used: 2597 MB, ext4
select data, ".."
Size: 113661 MB, Used:0 MB, ext4
I can Repair System , but not data.
data: it says /sbin/e2fsck -fp /dev/block/mmcblk0p44 process ended with error: 1 unable to repair data.
EDIT:
I tried to format every partition;
chache, userdata and system format fine,
but boot cant be formatted; it report error: "Formatting is not supported for filesystem with type ' '."
is my boot partition broken?

Need help returning to stock, have constant issues, please HELP!!!

Hi,
I initially had G935FXXS3ERHD_G935FXEO3ERG2_XEO installed and flashed Glamour ROM S9+ port some time ago, now i need to return it to stock but no luck...
Using latest odin i flashed:
G935FXXU3ERL3_G935FXEO3ERKF_XEO
and
G935FXXU3ERJE_G935FXEO3ERJF_XEO
(i need to remain on 3 bootloader)
after each flash i receive the NO COMMAND screen, and cannot boot into stock recovery... only way to boot the phone is to install TWRP... I have noticed when i plug the phone is it comes up as GALAXY S9+ so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
i have no idea what else to try

Hi,
Using latest Odin I am trying to return to my phone to stock but cannot 
I have tried 4 different firmware’s already (over 20 times) and each one will PASS the flash process, phone rests, installing system update (stops at around 30%) and during the blue screen the update stops, resets, receive Erasing message for a bit and then NO COMMAND and phone will simply not boot. (with some flashes the stock recovery is not even available, working or present)
... only way to boot the phone is to install TWRP... installing the NO VERITY file seems to help in booting…
I have noticed when i plug the phone is it comes up as another device name (from a previous ROM) so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
Back in DOWLOAD MODE under system status = CUSTOM (after flashing stock firmware)
My guess is that the new firmware I flash simply wont stick, or is half installed, or could be something to do with encryptions,
Some of the logs I see include:
Failed to open recovery
Reboot recovery cause UNKNOWN
E: Failed setting up dirty target
Fail to mount /system as rw
i have no idea what else to try

SM-G350 decided to not work out of nowhere

Hi! I used this phone back in 2014-2015 and then in 2016 I bought an iPhone 7, so I left the phone in his box. 2 years ago I needed to use that phone because I left some important photos that I didn't backup and a red exclamation mark appeared on the up-left part of the screen when I booted it. Couldn't access recovery but only download mode, the phone is a SM-G350 (I live in Italy and it isn't an ITV but a TIM region), I didn't root it or something it was stock firmware. Last year I decided to flash the TIM firmware but a KIES Update failed appeared (ODIN said OK and it went all good), I could access recovery and an EFS error appeared. This year I tried flashing TWRP 3 to install LineageOS 13 (maybe something could change) and transferring the file and flashing worked but the phone won't boot (stuck on LineageOS boot animation). I tried formatting Data etc but the EFS error was still there. I tried flashing ITV and TIM roms from Odin with no success, only an infinite boot. Yesterday I tried flashing another recovery but even with the Odin "OK" text TWRP was still there, so I started to doubt if the internal memory went corrupted when I left it another 2 months. I found a make2fs and mount method for the EFS, it mounts, I can install the LineageOS 13 zip but the progress bar stays at about 70%. When I delete files or transfer new things into memory or trying formatting from TWRP the internal memory clears temporarily and when I reboot into recovery the files go back like I didn't delete them. I had another SM-G350 but it died totally (it booted with the same exclamation mark thing) and back in 2015 I was using it in my hand and rebooted itself in recovery mode showing a file system unknown error.

G900F Restart loops

Hello everybody
I'm having this random issues with my Galaxy S5 G900F (Klte) with custom and stock roms.
Boot loops some times (System or Recovery)
Freezes at Logo or booting system or booting recovery.
Spontaneous reboots on recovery or system, at start or sometime later.
Some times it reach the PIN screen and sometimes not.
Some times it works for hours and some times it is rebooting all the time.
It happens from some days ago when I did a restore from custom rom backup.
It was taking a long time booting to system (more than 1 hour) so I removed the battery.
When I tried to start again the phone was not working well. (Just rebooting all the time)
I tried to solve it by flashing my previous used Stock Roms with Odin v3.09 with the result = <OSM> All threads completed. (succeed 1 / failed 0)
KitKat - G900FXXU1ANE2_G900FOXX1AND3_G900FXXU1ANE2_HOME
Lollipop - G900FXXU1BOJ1_G900FPHE1BOJ1_G900FXXU1BOJ1_HOME.tar
Marshmallow - G900FXXS1CPG9_G900FPHE1CPE3_G900FXXU1CPC9_HOME.tar
I also tried with custom Roms: RR pie, Bliss 12.7, Crdroid...
Sometimes I'm having errors while flashing custom Roms but sometimes everything be correct.
I also tried repairing, wiping and formatting every partition to ext2 and ext4
For some times I'm having problems wiping and formatting some partitions (randomly): unmount partition or no such file or directory...
I also tried with Original recovery and TWRP 2.x, 3.2 and 3.3 with the same results.
And also tried with and without SD and SIM
I don't know what more can i do. Some idea would be nice.
Aditional info:
My battery only have 7 months.

Is there any way to full clean all the phone partitions memory or any else?
Is Odin cleaning the phone during the installation of a new Rom or it is leaving some untouched?
How is posible that after install a Stock Rom with Odin with success end the mobile being unstable?

I'm doing a lot of tests because I don't understand the cause of my phone is unstable, but I'm learning a lot trough internet.
Some of the tests I'm doing are having this unespected results: (I could update this)
Boot loop entering to recovery mode
Cause: Unknow
Solution 1: Some times works better when I maintain pressed Vol+ and home until the TWRP screen si shown. (But not allways)
Solution 2: Some times I need to remove the battery, wait some minutes and try again after before entering in recovery. (Some times I need to repeat the proccess)
Boot loop entering to system
Cause: Partition system can't be repaired and shows "unable to mount partition" error on TWRP (May be the files or the partition is damaged or lost)
Solution: The only way I found is enter in recovery mode and clean system/dalvik/cache then install the Rom again. (Don't need to wipe data if it's the same Rom/Gapps)
Cause: Unknow
Solution: Sometimes the mobile enter to system after some tries

I also want to share some knowledge with the people that are looking for solution of similar problems and they found this post.
Some usefull guides I found: (I could update this)
A nice guide about Odin: https://pakfones.com/what-is-odin-and-how-to-use-full-guide/
What about nand erase on odin?: https://www.droid views.com/nand-erase-odin-samsung-firmware/
A nice program to get 4 part firmwares (SamFirm): https://samfirmtool.com/samfirm-v0-5-0 (The guide in the same site. )
Nothing new but , how to flash 4 parts firmware: https://rootsamsung.com/flash-samsung-stock-firmware-4-files
How to extract PIT from 4 Part firmwares (Easy way): https://www.droid views.com/extract-samsung-pit-file-from-firmware/#Extract_Samsung_PIT_File_from_Samsung_Firmware
Backup EFS/NV_data (Manual): https://forum.xda-developers.com/showthread.php?t=2737448
Something new, What is Combination Firmware?: https://combinationfile.us/what-is-samsung-combination-file-firmware/
Remove the space on URLS between droid and views.com
I don't see any diference between 1 part and 4 part firmware.
I think the Combination Firmware is only a little versión of Android (not much useful to fix nothing)
The same tools inside Combination are also on Development options in every Rom.
All credits of the guides/programs to their creators/maintainers. (I've only collected it here)

I will edit this post to not spaming the forum with the news.
Testing 4 parts Firmware obtained from SamFirm:
AP_G900FXXU1CRA2_CL12884729_QB16534923_REV00_user_low_ship_MULTI_CERT.tar.md5
BL_G900FXXU1CRA2_CL12884729_QB16534923_REV00_user_low_ship_MULTI_CERT.tar.md5
CP_G900FXXU1CQK3_CL12557498_QB15704233_REV00_user_low_ship_MULTI_CERT.tar.md5
CSC_PHE_G900FPHE1CRB1_CL12989714_QB16755881_REV00_user_low_ship_MULTI_CERT.tar.md5
But nothing really special, the phone continues restarting.
Testing 4 parts Firmware + PIT + re-partition + NAND Erase All
Nothing new, same reboot problems booting system.
At this point I have less reboots entering in recovery mode but:
Sometimes i have errors when I install custom Rom (E1001: Failed to update system image. and Error:7)
Stock roms boot loops everytime while booting system. (1 Part Firmware, 4 parts, with or without NAND Erase and PIT)
Custom roms like Bliss 12.7 works some times but without gapps.
I can't install Gapps now because errors / freezes at recovery.
Since the latest Stock Firmware installation I have more problems:
Black screen after Samsung logo.
More dificulties to enter on Recovery
Cannot solved by flashing any Stock Firmware.
Hardware buttons are good, and is not problem of overheats. (Works bad also in a cool state)
Going to SAT next monday.