Hi,
For some weeks i have the Echo Issue on my Z5C. I read that modify the mixer_path could help, and just install TWRP will be enough do modify it.
So this morning I Unlock my bootloader and I Install TWRP by using this thread :
https://forum.xda-developers.com/z5-compact/development/twrp-twrp-3-2-1-z5-compact-t3748952
I Used the 23.02.2018 version with this command :
"fastboot flash recovery recovery-name.img"
Until that no problems, I can restart with the TWRP interface. But, when i just want to restart by using "REBOOT" from TWRP, the phoe stays stuck on the Sony picture.
I can reboot on TWRP but thats all...and i'm stuck here...
I don't know verry much about developement...
my build is 32.4.A.1.54 and i'm on android 7.1.1
Thanks a lot for helping me.
I did that too last nite
I see you got that pesky sony s1 boot driver disable driver signing in windows 10 just to get the phone recognized. that sucks.
I just got this phone after some deliberation. I read good things here on it. I did what you did. Bricked it. Stuck on sony picture and both LED colors light at same time looking funky. I was able to recover the phone. I joined this forum just to tell you. Hope you fix it.
I used flashtool-0.9.25.0-windows software, installed it. Then pulled the US firmware from sony named E5823_32.4.A.1.54_1299-2920_R1E.ftf Flashed that and bam factory image.
I am still afraid to mess with twrp until I am sure. If you found it let me know. Thanks. I am on a newer firmware and perhaps that was the problem with TWRP?
---------- Post added at 08:59 AM ---------- Previous post was at 08:52 AM ----------
so many threads on this phone twrp
I am not wure
https://forum.xda-developers.com/crossdevice-dev/sony/twrp-3-1-0-z5-z5c-z5p-t3571050
---------- Post added at 09:06 AM ---------- Previous post was at 08:59 AM ----------
check this thread over at saw it on reddit comments about :silly: lineage
just google
which twrp build_to_choose_for_xperia_z5_compact
Z5C bricked after TWRP 220218.img- FIXED
I did this again. installed TWRP and was stuck in SONY screen.
Used recovery_suzuran_220218.img
Then just booted into TWRP
Installed lineage-14.1-20181207-nightly-suzuran-signed.zip
Had to drop it on internal storage. TWRP didn't read the SD card right.
After installing that it boots to lineage OS and then just installed
open_gapps-arm64-7.1-full-20190106.zip
Phone is up and running. Hope someone finds this helpful
Related
Hello guys,
This morning I installed kitkat on my lg g2 D802. I am now running it but I want to go back to 4.2.2. However, I lost the root when upgrading, as well as the custom recovery. Right now I can't seem to root it again, and Im unable to flash a stock rom, as when I am on lg flashtool, it says that the device is not recognized. Does anyone have an idea on how to get back to 4.2.2 so that I can root it again. I really need to because I need to flash the baseband again as I don't get any signal right now.
Thanks a lot !
This is not the correct forum for questions, you should read the sticky posts.
However, this might help:
http://forum.xda-developers.com/showthread.php?t=2582142
Edit: this might be the better solution: http://forum.xda-developers.com/showthread.php?t=2672076
Be careful not to brick your device. You do not have a backup of your partitions, do you?
Oh, sorry for that.. The solution proposed is for linux, and I only use windows. I have a nandroid backup on my phone, but I cannot access it because I don't have the recovery anymore. I saw the second link and tried to follow the tutorial but I block when trying to actually flash the tot file, this is why I sent the screen capture.
For the Linux solution you could run a Live-CD/DVD on your windows computer.
If this does not work, look for downgrading guides here on XDA or google. There are a couple, just search for them. I will report back if I find something.
---------- Post added at 09:00 PM ---------- Previous post was at 08:43 PM ----------
Looks like a global solution, although not very simple: http://forum.xda-developers.com/showthread.php?t=2432476
It's the second sticky post here, just bellow "Questions do not go in GENERAL". But since you did not read the first, I presume you did not have a look at the second
Hi there,
I think I may have messed up my tablet. I recently was trying to update it through the fastboot commands but after wiping the internal storage and data, I went back to the bootloader and found out that the device was locked now. I can't fastboot flash anything since I don't have permission to do anything. I have TWRP flashed to the recovery though but when I go into there it asks for a password. I checked to see and it's because the device is locked, so I needed to unlock it. Well unfortunately there isn't an OS on the tablet to go into the settings and unlock it from. I was trying to flash Dirty Unicorns to see if I could just change it there but it fails during flash saying '/umount system failed: no volume exsists' if I try to reboot after that it just goes to the Google screen and does nothing.
So Bootloader Locked, TWRP installed, can't unlock bootloader since no OS installed.
Help!
Edit: I put this in the wrong forum. My bad.
@Verttex,
Let me see if I have understood your situation:
- bootloader is locked
- No ROM (deleted?)
-TWRP recovery installed, but you can't get into it because it requests a password?
---------- Post added at 08:07 PM ---------- Previous post was at 07:37 PM ----------
[/COLOR @Verttex
I think there is a solution for you on the Nexus 6 forum. See post #40 here >http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539/page4
Well I did the third command with the unlock.IMG that they provided, but now the screen doesn't work. It seems I can still get it to go to the bootloader since my computer detects it.
I might be able to get it to TWRP and then run the adb command again but right now, the screen is just blank.
Maybe I accidentally flashed the n6 unlock image instead of the n9 one?
Verttex said:
Well I did the third command with the unlock.IMG that they provided, but now the screen doesn't work. It seems I can still get it to go to the bootloader since my computer detects it.
I might be able to get it to TWRP and then run the adb command again but right now, the screen is just blank.
Maybe I accidentally flashed the n6 unlock image instead of the n9 one?
Click to expand...
Click to collapse
Go to that thread and post your question. They are the experts, and VERY helpful. The OP is actually looking for someone like you to try this.
Discussion moved to http://forum.xda-developers.com/nex...enable-oem-unlock-t3113539/page6#post61042231
Thread closed as per OP request.
I can't seem to get root on my Sm-T337A.
I want acheive root and learn to develop and experiment with custom ROMS. I'm very new to this.
I was able to install Odin and install a boot.tar file but the Tablet kept boot cycling into recovery mode. I tried what I thought was sidebooting files using adb, but apparently I don't understand how that works yet. I restored the tablet by forcing it into install mode (held down power, vol down, and home) then used Odin to install the boot(LP).tar file which restored the tablet. This ROM is indeed the AT& T Rom, but it is not the same one that came with the Tablet when I got it new (it has a different look).
Please help.
Here is the information on my tablet.
Android 5.1.1
Baseband Version - T337AUCU2BOH4
Kernal Version [email protected] #1 Thu Aug 13 17:01:34 KST 2015
Build Number LMY47X.T337AUCU2BOH4
Knox 2.4
You're SOL, bootloader is locked
gonzo6962001 said:
You're SOL, bootloader is locked
Click to expand...
Click to collapse
I was able to root mine with KingRoot but after rebooting it said I had to take mine to the nearest At&t store. Yea...that won't be happening. Through Odin I flashed the LP boot tar. Fixed it. But I really want to gain root. There is no way around this? There has to be a way to unlock bootloader. Thanks in advance.:fingers-crossed:
NITASHA212 said:
I was able to root mine with KingRoot but after rebooting it said I had to take mine to the nearest At&t store. Yea...that won't be happening. Through Odin I flashed the LP boot tar. Fixed it. But I really want to gain root. There is no way around this? There has to be a way to unlock bootloader. Thanks in advance.:fingers-crossed:
Click to expand...
Click to collapse
If you could explain how to get around a locked bootloader you would make a lot of people very happy. Can't be done yet. That is the whole issue
---------- Post added at 03:36 PM ---------- Previous post was at 03:27 PM ----------
Look up t337a temp root in xda. A guy says he figured it out but Noone has tried it. I use mine for work every day so I can't chance it. If you're brave enough to try. If it works put in a reply there and let me know. It says it works on our bootloader
---------- Post added at 03:51 PM ---------- Previous post was at 03:36 PM ----------
Here is the link
http://forum.xda-developers.com/tab-4/general/att-tab-4-8-t337a-temp-root-t3301345
hello,
i have a Samsung tab e sm-t561 , it is a NTTF study tab. i wanted to remove their OS and reload to stock rom. but when i try to update it via odin, it gives me error saying that the MDM MODE, CANT DOWNLOAD
REGARDS
I'm not having problems on my.
I own an SM-T561 and I were flashing many times without problems.
I needed to flash stock rom many times because there was no root and tried almost all methods I found, until we found a Russian site doing the root, and their method worked.
Can you verify the kernel and rom version?
unlock your bootloader
recallrules said:
hello,
i have a Samsung tab e sm-t561 , it is a NTTF study tab. i wanted to remove their OS and reload to stock rom. but when i try to update it via odin, it gives me error saying that the MDM MODE, CANT DOWNLOAD
REGARDS
Click to expand...
Click to collapse
Unlocking your bootloader with adb/SDK would enable you to flash anything you want. Do this and notify me after unlocking your boot loader
---------- Post added at 05:47 PM ---------- Previous post was at 05:42 PM ----------
I got this tab from ohio state university when I was doing my masters.. And I just unlocked the bootloader using Android SDK (Google how to do this). After that, i've flashed my tab with TWRP recovery. Then, I have used Odin to flash custom recovery on my device. Works fine as hell. Just like a normal tab.
dvrz said:
Unlocking your bootloader with adb/SDK would enable you to flash anything you want. Do this and notify me after unlocking your boot loader
---------- Post added at 05:47 PM ---------- Previous post was at 05:42 PM ----------
I got this tab from ohio state university when I was doing my masters.. And I just unlocked the bootloader using Android SDK (Google how to do this). After that, i've flashed my tab with TWRP recovery. Then, I have used Odin to flash custom recovery on my device. Works fine as hell. Just like a normal tab.
Click to expand...
Click to collapse
can u tell me how do the boot loader unlock??? in download mode?
i also have this problem please told to disable secure download in odin
passwaord: MDMPass:8152
dvrz said:
Unlocking your bootloader with adb/SDK would enable you to flash anything you want. Do this and notify me after unlocking your boot loader
---------- Post added at 05:47 PM ---------- Previous post was at 05:42 PM ----------
I got this tab from ohio state university when I was doing my masters.. And I just unlocked the bootloader using Android SDK (Google how to do this). After that, i've flashed my tab with TWRP recovery. Then, I have used Odin to flash custom recovery on my device. Works fine as hell. Just like a normal tab.
Click to expand...
Click to collapse
HEY unlocking bootloader using android sdk,
the mdm agent doesn't allow the connectivity to pc.
i.e in device manager no android device is shown. while other devices get connected easily and android device is shown in device manager.please do something
I just rooted my sm-t561 3g device
Hey I just rooted my Samsung sm-t561 device wanting to upgrade to higher version than Kitkat 4.4.4 but couldn't get any solution.
Hi I need some help please, not really technical but loaded the Android N beta on my Nexus 9 wi-fi, as it was crashing almost hourly I opted to restore it to factory defaults, it is now stuck in a boot loop. Tried to install the current supported factory image using ADB OTA sideload but it fails at 47% saying something like "Error: image is "flounder"; device is "".. as if the device has no identity.
the fastboot can see the device but ADP struggles. the device shows LOCKED at all times. any suggestions greatly appreciated
part fixed
graminou said:
Hi I need some help please, not really technical but loaded the Android N beta on my Nexus 9 wi-fi, as it was crashing almost hourly I opted to restore it to factory defaults, it is now stuck in a boot loop. Tried to install the current supported factory image using ADB OTA sideload but it fails at 47% saying something like "Error: image is "flounder"; device is "".. as if the device has no identity.
the fastboot can see the device but ADP struggles. the device shows LOCKED at all times. any suggestions greatly appreciated
Click to expand...
Click to collapse
I have now got my device working by sideloading Android N image, not achieved my objective of unenrolling but at least I have a device that boots, will wait for a more stable version eventually
What image are you trying to sideload?
Make sure your not using the LTE version.
Try sideloading the Android N OTA again.
Have you previously enabled OEM unlock in developer options? If yes try "fastboot OEM unlock".
---------- Post added at 04:54 PM ---------- Previous post was at 04:51 PM ----------
graminou said:
I have now got my device working by sideloading Android N image, not achieved my objective of unenrolling but at least I have a device that boots, will wait for a more stable version eventually
Click to expand...
Click to collapse
You post the above around the same time as my reply.
You now can enable OEM unlock and flash factory images.
corkiejp said:
What image are you trying to sideload?
Make sure your not using the LTE version.
Try sideloading the Android N OTA[/URL] again.
Have you previously enabled OEM unlock in developer options? If yes try "fastboot OEM unlock".
---------- Post added at 04:54 PM ---------- Previous post was at 04:51 PM ----------
You post the above around the same time as my reply.
You now can enable OEM unlock and flash factory images.
Click to expand...
Click to collapse
Hi corkyejp and thanks, i was aiming to go back to current supported not the beta N release, I officially unenrolled received the OTA image, installed, got stuck in bootloop, tried sideloading MOB30G which i beleive was the correct wifi not LTE version (I saw that version mentioned in my crashlogs too). the device was in developer mode, I think but am not sure, however the HBOOT screens always showed LOCKED. i tried the fastboot flashing unlock (and OEM unlock options) but neither unlocked me. anyway at least I have a device that boots now, will put up with crashes if they occur. thanks again