Related
EDIT: I managed to flash stockrom via flashtool, I didn't do anything different so I can't really help others with the same problems, I just kept trying.
But I can tell you the root of all the mess I did: Neowave ROM requires unlocked bootloader, which I didn't had. I'm still curious why it messes up everything and not only /boot
and /system, but I'm glad that everything works again.
So I managed to (hopefully soft)brick my phone again when flashing new rom. (from Omega to Neowave)
What I did:
-flashed new recovery (Philz Touch recovery)
-wiped /system
-flashed new rom, gapps minimal, aosp calendar sync addon and supersu update (all without rebooting)
-then I rebooted the phone, screen was black, no LED, only a vibrate at the beginning.
-PC detects it as SEMC flash drive, the phone automatically disconnects and then reconnects again after ~1min
-Repair with Sony Companion didn't work, it just said that there is no software for my phone
-adb devices said there are no devices
-I can't enter recovery or fastboot, only fastboot worked twice but I disconnected the phone because the Sony Companion said so
Additional info:
-rooted
-locked bootloader
What should I do now?
I wanted a new clean rom because the old one was so damn laggy and had many problems and high battery drain, and I'm going on a vacation
in 2 day so I'm in a hurry. I don't have a 2nd phone because this is already my 2nd (lost my LG G2 2 weeks ago..)
I hope u understand my struggle and take your time to help me, thanks in advance)
NO surrender
Tazmaniiac said:
EDIT: I managed to flash stockrom via flashtool, I didn't do anything different so I can't really help others with the same problems, I just kept trying.
But I can tell you the root of all the mess I did: Neowave ROM requires unlocked bootloader, which I didn't had. I'm still curious why it messes up everything and not only /boot
and /system, but I'm glad that everything works again.
So I managed to (hopefully soft)brick my phone again when flashing new rom. (from Omega to Neowave)
What I did:
-flashed new recovery (Philz Touch recovery)
-wiped /system
-flashed new rom, gapps minimal, aosp calendar sync addon and supersu update (all without rebooting)
-then I rebooted the phone, screen was black, no LED, only a vibrate at the beginning.
-PC detects it as SEMC flash drive, the phone automatically disconnects and then reconnects again after ~1min
-Repair with Sony Companion didn't work, it just said that there is no software for my phone
-adb devices said there are no devices
-I can't enter recovery or fastboot, only fastboot worked twice but I disconnected the phone because the Sony Companion said so
Additional info:
-rooted
-locked bootloader
What should I do now?
I wanted a new clean rom because the old one was so damn laggy and had many problems and high battery drain, and I'm going on a vacation
in 2 day so I'm in a hurry. I don't have a 2nd phone because this is already my 2nd (lost my LG G2 2 weeks ago..)
I hope u understand my struggle and take your time to help me, thanks in advance)
Click to expand...
Click to collapse
When a mistake is always better to return to the " factory " ROM before trying again . I recommend using flashtool . through fastboot , put his boot.img and then a flash the stock rom
I have a TX, roms and testing step that you like . but if the PC recognizes there is hope.
I'm using the google translator . : P
Tazmaniiac said:
EDIT: I managed to flash stockrom via flashtool, I didn't do anything different so I can't really help others with the same problems, I just kept trying.
But I can tell you the root of all the mess I did: Neowave ROM requires unlocked bootloader, which I didn't had. I'm still curious why it messes up everything and not only /boot
and /system, but I'm glad that everything works again.
Click to expand...
Click to collapse
You need to flash a stock ftf.
Keep us updated on how far.
sublinker said:
You need to flash a stock ftf.
Keep us updated on how far.
Click to expand...
Click to collapse
With flashing stockrom I meant flashing stock ftf, sorry for that.
So the case was I reset my device, and later after i flashed a ROM into my device, it does not boot. Instead, it goes into TWRP recovery. And it goes to TWRP every time i boot my device.
I have done this for so many times and I cannot even know what is going wrong this time. I am quite frustrated and I did googled a lot but it did not solve my problem. So, I want to know if anyone else encounter similar problem and solution towards it.
I tried:
1. Wipe the dalvik cache.
2. Remove the battery for half an hour
3. Reflash the twrp
Any efforts and reply is much appreciated.
Thank you.
Mine's exactly the same, I factory reset so I could pass the phone on; and now it will not install custom roms, I've tried about 7 or 8, and it will only boot into twrp 3.0.2-5. Soft brick, but I'm unable to find any solution.
Here's hoping someone will come and help.
I think I'll have to reinstall twrp by connecting the phone to the computer, but I've no idea how to do this.
slifer225 said:
So the case was I reset my device, and later after i flashed a ROM into my device, it does not boot. Instead, it goes into TWRP recovery. And it goes to TWRP every time i boot my device.
I have done this for so many times and I cannot even know what is going wrong this time. I am quite frustrated and I did googled a lot but it did not solve my problem. So, I want to know if anyone else encounter similar problem and solution towards it.
I tried:
1. Wipe the dalvik cache.
2. Remove the battery for half an hour
3. Reflash the twrp
Any efforts and reply is much appreciated.
Thank you.
Click to expand...
Click to collapse
Exactly the same issue here too, installed lineage 14.1, was working great, I was selling to a friend, did a factory reset, now stuck at twrp, roms install etc, but after a reset, every time straight back to TWRP.
Looks like I might need to flash back to stock somehow.
But I did find this, but not yet tried.
https://www.reddit.com/r/LineageOS/comments/5riech/how_fix_twrp_recovery_boot_loop_after_lineageos/
andydgg said:
Mine's exactly the same, I factory reset so I could pass the phone on; and now it will not install custom roms, I've tried about 7 or 8, and it will only boot into twrp 3.0.2-5. Soft brick, but I'm unable to find any solution.
Here's hoping someone will come and help.
I think I'll have to reinstall twrp by connecting the phone to the computer, but I've no idea how to do this.
Click to expand...
Click to collapse
Well i have took the ultimate solution. Back to stock firmware fix everything. Well, i guess not much to mention on stock firmware=)
I think you should do the same thing too. Good luck.
slifer225 said:
Well i have took the ultimate solution. Back to stock firmware fix everything. Well, i guess not much to mention on stock firmware=)
I think you should do the same thing too. Good luck.
Click to expand...
Click to collapse
That is good to know, I shall attempt to do the same, did you later install a custom rom and everything was fine afterwards?
Yes, i flashed custom recovery and ROM afterward. Even several attempt on wipe and flash the new ROM. So i guess it should be fixed
Thank you.
andydgg said:
Mine's exactly the same, I factory reset so I could pass the phone on; and now it will not install custom roms, I've tried about 7 or 8, and it will only boot into twrp 3.0.2-5. Soft brick, but I'm unable to find any solution.
Here's hoping someone will come and help.
I think I'll have to reinstall twrp by connecting the phone to the computer, but I've no idea how to do this.
Click to expand...
Click to collapse
As slifer225 mentioned you can downgrade to stock firmware by installing the stock MM rom s433 version using spftools.
Download and Install stock MM rom using spftools.
Here is the link- https://cloud.mail.ru/public/Cco5/JYk3ytrW1
For further info follow this post- https://forum.xda-developers.com/k3-...3#post71749243
Follow this step by step guide to go back to unrooted stock rom. If you want to root after that then try installing custom recovery(twrp) again using spftools and flash supersu.zip using recovery. Do take a backup though before rooting your device.
---------- Post added at 10:11 AM ---------- Previous post was at 10:04 AM ----------
justwondering said:
That is good to know, I shall attempt to do the same, did you later install a custom rom and everything was fine afterwards?
Click to expand...
Click to collapse
Everything is working perfectly as I myself had gone through the same issue and did everything to fix the problem until I downgraded back to stock. Did root on my device again and installed lineage 7.1.1 and it works like a charm. One thing I love about this rom is the efficient ram management, lag free but battery management is not upto the mark but I guess we can work it out.
Whatever you do never forget taking a backup of functional rom.
Yes, I can confirm the solution worked for me, I left it with stock rom for my friend, I tried lineage 14.1 and did a factory reset, but ended once again with softbrick , lineage will install and work perfectly, but as soon as you do a factory reset, soft brick
Now I've hard bricked it. I loaded up a 'looprecovery' when it rebooted there's nothing, no charge light no vibrations PC doesn't see it, land fill?
Wondering...
justwondering said:
Exactly the same issue here too, installed lineage 14.1, was working great, I was selling to a friend, did a factory reset, now stuck at twrp, roms install etc, but after a reset, every time straight back to TWRP.
Looks like I might need to flash back to stock somehow.
But I did find this, but not yet tried.
https://www.reddit.com/r/LineageOS/comments/5riech/how_fix_twrp_recovery_boot_loop_after_lineageos/
Click to expand...
Click to collapse
I think that solution only works on Snapdragons. It didn't for me. Is there a solution for MTK devices?
the solution for this(FIX)
all we need to do is reinstall a stock recovery and the again reinstall the TWRP
https://forum.xda-developers.com/k3-note/general/ufficial-thread-lenovo-k3-note-t3102997
follow this link..my phone just got fixed
My phone TWRP-looped many times. The solution is actually easy.
1. Reflash using SPFlashtool ONLY the stock recovery
2. boot into stock recovery
3. choose english > press reboot phone
4. phone will reboot into rom without problemos
5. reflash TWRP
cheers
or
1. Copy stock recovery.img into sdcard
2. In twrp, select Install and navigate to where you put stock recovery.img
3. Press install image. Then, Select recovery.img. Slide to install
4. boot into stock recovery
5. choose english > press reboot phone
6. phone will reboot into rom without problemos
7. reflash TWRP
DONE
Infinity loop recovery
andydgg said:
Now I've hard bricked it. I loaded up a 'looprecovery' when it rebooted there's nothing, no charge light no vibrations PC doesn't see it, land fill?
Click to expand...
Click to collapse
hI MY FRIEND , you have been able to fix your K3 note, I have the same problem, I made twrp flash and went into infinite loop. Can you help? thank you
I smashed it and put it in the bin. I think once you can't get a charge light after tyring for a couple of week, it's dead.
Not working for Lenovo K3 Note.
My K3 note stuck in the twrp recovery after factory reset from the RR. I tried this solution but it didn't work.
Please help.
Whichever flashing method I use (TWRP, fastboot) Whichever rom I use (I tried clean stock, pre rooted, MM, LP, backups), I can't get past the animation screen. Even restoring a backup through TWRP gets stuck at the same spot. The only ROM that works is LineageOS (based on Android 7.1). I tried wiping various combinations of dalvik cache, data, cache, system, internal storage - still always stuck on boot animation. I tried leaving it for a long time always, the longest was over 2 hours. I feel like I'm missing wiping something since it seems like the issue is going from a 7.1 rom down maybe?
More info: I was using SLiM ROM (MM 6.0.1) for a while but it got extremely slow and poor battery life after a while. I flashed LineageOS for Z3C and it worked fine, but wasn't my cup of tea, so I wanted to go back to stock-based. I figured I'd try eXistenZ (MM 6.0.1). The instructions said to be on 23.5.A.1.291 first, then root it, and then flash the existenz zip. I didn't downgrade to .291 the first time and it didn't work. Second time I flashed a stock D5803_23.5.A.1.291 (which booted up normally). Went through the rooting process (as seen here), and that worked fine. But the next step of flashing eXistenz didn't work. I tried again from the start, but this time I couldn't boot into after flashing 23.5.A.1.291 again. This is where the problem started. I tried Slim and various roms using fastboot, various versions of twrp, and even a 6.0.1 backup through twrp. Always regardless of ROM, it gets stuck on boot animation. Except for LineageOS.
Hi, I'm in the exact same situation, I have Lineage OS 7.1 installed and I can't go back to any custom ROM based on Android 6.0 stock, all I get is always a bootloop. The only other ROM I can install is Sony stock via Flashtool. I really don't know what the problem is, please let me know if you manage to solve this weird problem.
Install old twrp, wipe /apps_log.
Or use emma to get a clean device again.
I solved the issue installing stock Android 6.0 with Flashtool, twrp 3.0.2 and then flashing ROM. :good:
Hello all,
Firstly I would like to thank all the great people here, I've been struggling for hours with my dead Xperia Z and the amount of dedication and support I've found so far across all the members here is really impressing.
Let me first illustrate my case.
Firstly, I came here to root my phone and install a custom rom ships with Android N 7.1.2 (Resurrection Remix), I did went through all the newbies/how to threads and I did successfully ended up with Android N on my phone
Unfortunately, the device was not working probably in case of incoming or outgoing calls. No ringtone (already selected from Settings >Sound - played and heared), while in call it keeps ending the call unexpectedly, sometimes it feels very laggy that I couldn't even tap on anything. So I decided to give up until I found another rom that ships with Android N (XOSP), after successfully installing the rom, it starts out very smooth and I tested everything and it was ok, until yesterday the same issue still persists plus my device mic is not working no one can hear me while I'm talking neither from a headset mic nor the device mic. Finally I gave up and decided to rollback to the old lolipop stock rom.
Here's comes the current problem:-
1- I did flash 10.7.A.0.222 Customized MEA using flash tool and it's flashed successfully.
2- I'm now stuck with a dead black screen after sony logo.
I tried everything, changed the flashtool version, downloaded other ftf kernel file, used Xperia Companion and non of them worked for me. I did also tried what's listed in here https://forum.xda-developers.com/xperia-z/general/disaster-recovery-getting-z1-zu-z-zl-to-t2229250
I only can boot into fastboot or flashboot mode
I cannot copy files to my phone as it never appears as a storage media in my computer.
Any help will be much appreciated
Sorry for the long post
I never had this problem before, but have you try other ftf with lower android version like KK?
I see this problem on someone, everyone of them had this problem when they try to revert back to stock LP from N. Then someone suggest to flash KK ftf. You should try this if you haven't try this.
Sorry if my English is bad.
UPDATE:
when the first 7.0 nougat custom rom came, I'm on 5.1.1 rom with XZDual recovery. I made a backup for this rom and flash the 7.0 N rom only for trial then revert back to stock 5.1.1 that I backup before. Chippa's rom always came with latest built-in recovery so when I upgrade to nougat rom the XZDual recovery also lost (I don't have FOTA recovery, lol).
The step I made to revert back to stock is to do a FULL wipe of the phone (cache, davlik cache, data, system, AND internal storage), not a regular full wipe (without internal storage).
I put my backup stock rom file to my external sdcard (because the internal storage got wiped) and begin to flash, BUT NOT reboot into system, I reboot the phone to recovery instead (because I think the 5.1.1 rom works better with old TWRP so I reboot the phone to recovery first to get the old XZDual recovery).
After phone enter the old TWRP, I do a FULL wipe (cache, davlik, data, system, internal storage) once again to make sure everything OK, then flash the stock rom once again.
aand... it works. I did it 3-4 times to test new build of 7.0 n rom and never have any problem of reverting back.
But, I never test this method on newest 7.1.1 rom or 7.1.2 rom.
since you can't boot on LP rom, then try to flash KK rom.
Just install phone driver, flashtool, and download the KK ftf.
I'm sorry I can't provide you the full instruction because I never had this problem before, but you can search for this on N rom thread (the rom developed by Chippa). There is a guide made by someone on that thread.
Zerikwan said:
I never had this problem before, but have you try other ftf with lower android version like KK?
I see this problem on someone, everyone of them had this problem when they try to revert back to stock LP from N. Then someone suggest to flash KK ftf. You should try this if you haven't try this.
Sorry if my English is bad.
UPDATE:
when the first 7.0 nougat custom rom came, I'm on 5.1.1 rom with XZDual recovery. I made a backup for this rom and flash the 7.0 N rom only for trial then revert back to stock 5.1.1 that I backup before. Chippa's rom always came with latest built-in recovery so when I upgrade to nougat rom the XZDual recovery also lost (I don't have FOTA recovery, lol).
The step I made to revert back to stock is to do a FULL wipe of the phone (cache, davlik cache, data, system, AND internal storage), not a regular full wipe (without internal storage).
I put my backup stock rom file to my external sdcard (because the internal storage got wiped) and begin to flash, BUT NOT reboot into system, I reboot the phone to recovery instead (because I think the 5.1.1 rom works better with old TWRP so I reboot the phone to recovery first to get the old XZDual recovery).
After phone enter the old TWRP, I do a FULL wipe (cache, davlik, data, system, internal storage) once again to make sure everything OK, then flash the stock rom once again.
aand... it works. I did it 3-4 times to test new build of 7.0 n rom and never have any problem of reverting back.
But, I never test this method on newest 7.1.1 rom or 7.1.2 rom.
since you can't boot on LP rom, then try to flash KK rom.
Just install phone driver, flashtool, and download the KK ftf.
I'm sorry I can't provide you the full instruction because I never had this problem before, but you can search for this on N rom thread (the rom developed by Chippa). There is a guide made by someone on that thread.
Click to expand...
Click to collapse
Thank you so much for your reply. I will try it out. I really appreciate your contribution and I will keep you updated
Hello everyone, I'm here to share with you guys a solution that saved my life last night.
Well, as a good user, I tried to root my phone and I got it, but the screenlock wasn't working as you guys should know, then I tried to go back to stock and wait 'til someone fix that problem, but when I flashed Stock through Odin, my phone began to bootlooping after Samsung's logo and apperently there was no reason for it to do that, but I got a lot of erros, like:
No data access (Argument invalid);
Modem error (auth), etc.
Well, what I did was just flash TWRP through odin, formatted /data and then I flashed the official recovery and firmware again.
Hope that helps!
iRomulls said:
Hello everyone, I'm here to share with you guys a solution that saved my life last night.
Well, as a good user, I tried to root my phone and I got it, but the screenlock wasn't working as you guys should know, then I tried to go back to stock and wait 'til someone fix that problem, but when I flashed Stock through Odin, my phone began to bootlooping after Samsung's logo and apperently there was no reason for it to do that, but I got a lot of erros, like:
No data access (Argument invalid);
Modem error (auth), etc.
Well, what I did was just flash TWRP through odin, formatted /data and then I flashed the official recovery and firmware again.
Hope that helps!
Click to expand...
Click to collapse
probably during flash with odin you chose Home_csc_omc..... and all phone's data still intact/untouch. that's why need to wipe data in TWRP.
if since the first place you chose csc_omc without HOME label... thats mean you do the clean flash and all will fine no need format data in TWRP.
just my thought..