hy'all
summed up: bootloop, displays: device corrupted and wont boot after a few tries
longer: fked around and found out. rooted with magisk boot img patch, changed stock launcher app(foolishly didnt make any backups at all) and wont boot at all.
newflasher doesnt work, missing SOMC Flash Device in device manager(looked around couldnt find any working drivers)
tried to flash manually and progressed till the Sony logo but restart there and then corrupted shutdown
twrp does come in but fails to mount basically anything when wiping
any ideas? kinda lost here
edit: lol solved. using the evox griffin zip as a baseline idea for img files, flashed the same ones from stock fw and it booted. gg
Related
Hi all,
Today I wiped all data and cache from my device and installed VillainROM from CWM Recovery Manager. Install looked fine it said that it finished, so I went to reboot.
The device was stuck on the Samsung Galaxy S II logo with the yellow triangle (!) for around 10 minutes. I then turned it off cause I realized it wasn't going to boot.
Anyone have any idea why this happened? I restored a backup of my previous ROM and my phone booted up real fast and it was fine.
Could just be a bad download?
Sent from my GT-I9100 using XDA App
Try flash it again before it boots. IE: Flash from zip, then go back and falsh from zip again.
I've had to do that with CM...
OK will try that, cause the same thing happened to me when I installed Cyanogenmod straight from Rom Manager. Thx
Update: No go, I also made sure Deluxe Settings was uninstalled before I went into recovery. It's stuck at the boot screen.
However, upgrading my previous ROM (WanamLite v4.0) to WanamLite 5.2 worked fine and the device booted. It was exactly the same procedure in recovery mode but a different ZIP file.
Will try another ROM like LiteningRom and see if anything changes. I don't think it's a CRC error because I open up the files before I copy to the device to see if WinRAR pops any CRC errors.
I'd start on the thread a few up from yours.... the one that mentions if you have a boot loop
Sorry, I didn't realize it was a boot loop because it wasn't actually looping, just stuck on the image. Is that considered a boot loop?
So I am in need to reflash the whole system via sdcard through the stock recovery! I am still locked. Now what happend was is i updated from .13 to .14 booted up got a scroll of errors. It only allowed me to use the apps i had moved to my sdcard. Soi checked es eile manger and my whole system file was gone so i rebooted thinking it was a fluke or i was seeing things and now im stuck at the boot screen.
I have tried to use the recovery to flash the firmware update and it ends up with a red exclamation above the androids chest.
If someone could explain mayb im doing it wrong. I have tried renaming the .zip 201_SDUPDATE.ZIP n nothing so nehelp would be great thanks.
hi guys,
my find 5 was having some reboot issues (it was rebooting a few times per day) and that was a bit anoying. I was using an old original FW so i decided to update to a newer one. Heard good stuff about the Omni so i went for that, so i was using TWRP 2.4.1.0 (i think... i'm sure it was 2.4.x) and on the omni page they said we have to use TWRP 2.6 so i went for an update.
here, i think, i've created my problem. I used the new flashify app to install the TWRP but instead of choose recovery img i choosed to flash the boot and i guess i'd flashed the TWRP on the boot.
well anyaway, now i'd installed the TWRP 2.6.3.1 i manage to start the phone in fastboot and recovery all good here, i install every rom nice and easy over TWRP but the phone simply doesn't start, it gets stuck on Touchscreen Firmware Update please wait.... this happens ALWAYS with what version of TWRP or even if i install CWM...
my guess is that i'd messed up some partition or so i don't really know what but i'd tried to format every partition that TWRP let me and still getting the freackin Touchscreen Frim updt screen... so need some Pro help to help me undo the mistake i'd done...
i'd tried to manualy flash the boot with my current firms boot.img and still no go... the damn touchscreen update screen keeps showing on no matter what....
thanks for everything
i change the firmware and start logo changes too so booting it's changing why the hell the touchscreen update keeps appearing... grrrrr i even installed a chinese firmware and a equivalent screen appeared i'm pretty sure it says: "Touchscreen Firmware Update in Progress Please Wait" but in chinese XD really don't know what to do anymore...
some ideas please?
i just don't know what to do anymore... does anyone knows what makes the phone try to update the touchscreen firm? today i installed the CWM in boot not in recovery just to test if the damn thing would go to the touch updt screen again and it just boot to the CMW like it should (normal because i'd flashed the CMW in the boot place). now i flash a new firmware (that will flash the correct boot.img) and the thing keeps holding on the touch update... i'm really out of ideas now
one other thing it's that if i install the TWRP in boot it won't boot in TWRP like it shoul... it stucks on oppo logo.
well i managed to install the same firm i had and have no touchscreen update... but if i install any other firm the message appear...
hello everyone
I would like to permanently hard brick my phone wt19i...... I tried everything from flashing other phone's rom, kernel and recovery. Tried using rom manager too, but nothing worked. As soon as I flash stock gb or stock ics, the phone comes back to life again.
Please if someone could suggest a working method so that even the service centre guys won't be able to fix.
Why would you want to do that
Easiest way would be to physically mess up the chip, shorting something or so.
Sent from my SM-N9005 using Tapatalk
How to short something in hardware.....all I found by searching was flashing improper things.....but each method failed....as soon as to confirm hard brick I tried to flash stock rom it flashed normally and booted too
anikanu said:
How to short something in hardware.....all I found by searching was flashing improper things.....but each method failed....as soon as to confirm hard brick I tried to flash stock rom it flashed normally and booted too
Click to expand...
Click to collapse
have Xperia Mini St15i rooted unlocked bootloader. Running on CM 11.0 very well
but I recent update to latest build 24072015 and I can't boot my phone; after I tried to restore my old backup,tried to install old Rom which is( I installed in past successful)l and tried flash Xperia mini stock rom ftf (various version) but phone doesn't start can say hard brick.
I can install all of them successfully but phone does not start. always displays error of "unfortunately the process com.android.phone has stopped and phone restart on boot logo again and again.
update......
I recently flash BeanStalk-4.4006-20131128-smultron and after many tries I success to start phone but I noticed that in apps only 50 MB memory is free. I didn't have installed any app. in past I have there is about 370 MB free.(xperia mini has 420 mb data partition)
I have try to erase system,data with fastboot but nothing happens
I attached text file of fastboot commands.
I tried to flash sony origional firmware too but it only restarts again and again .
I have tried to erase system and userdata with fastboot but i see that it encountered bad block in erase data, I can't understand why data partition can't be formated ? text document attached
I think my data partition is full. after reboot in recovery there is an error of " no space left in device " phone does not start normally. I can boot in recovery but still can not use phone .
running on CM 11 and this problem is start on flashing cm-11-20150723-UNOFFICIAL-LegacyXperia-smultron. after that my phone doesn't start.
So I recently tried to unroot my device with flashing official ROM on it. Apparently I used the wrong file because my phone got bricked. I tried using XiaoMiTool by Francesco but it didn't help. I spent a lot of time trying to fix it so ill post what worked for me. I downloaded a lot of ROMS but none of them worked for me there was either flash error or device mismatching and I couldn't find right flash official software anywhere. I downloaded another ADB fixing program which worked, I downloaded Szaki/XiaomiADB fastboot tools which worked perfectly. I simply connected my phone searched for my phone code name (tucana) downloaded ROM from there, wiped all data off and finally flashed OS on my device. I also have a question, are there any android software fixing programs for phone repair companies or something similar?
Have good day and stay healthy,
MX8MC8
id suggest to unbrick with mi flash tool.
I did that always when i was stuck on something, it ofcourse removes your data but saves the device so its still the profit probably... After succesfull rom installation you can flash again.
Also you do this in fastboot mode
When I was stuck in the same way the solution I found was to flash whatever rom then when the phone bootloops, go into recovery, and format data. Afterwards it will boot to startup screen and take forever to load up. Anyway that is my solution, before that I would have to flash stock recovery to boot for the first time then flash a custom recovery back.