I have the OST software up and running, but cannot find a stock ROM on the internets for the TA-1085. Where can I find it? Must be a .nb0 file, apparently, to work. I'm stuck on the download mode screen, and fastboot/adb methods have all failed to restore or reset to factory.
drewski429 said:
I have the OST software up and running, but cannot find a stock ROM on the internets for the TA-1085. Where can I find it? Must be a .nb0 file, apparently, to work. I'm stuck on the download mode screen, and fastboot/adb methods have all failed to restore or reset to factory.
Click to expand...
Click to collapse
First are you bootloader unlocked?
If so, you can use NOST using the CTL-256A-0-00WW-B07 - September '18 firmware (Android 8.1). From here https://androidfilehost.com/?w=files&flid=299213.
The other firmware CTL-345A-0-00WW-B01 - December '18 (Android 9.0) and CTL-351F-0-00WW-B04 - March '19 has a new sparse so you can't use NOST to flash. You have to use Hikari's new sparse script to flash to a more recent rom. You can find the thread here: https://forum.xda-developers.com/nokia-7-plus/how-to/guide-workaround-flashing-sparse-t3906070
A friend also got his 7.1 bricked, by the update v3.54h
Can he skip the update? Or he's never gonna recieve another update (android 10 for example) till he install that one?
Related
So i got my Honor 5x yesterday and thought i would install a custom rom on it since people are recommending it.
Its my first time so i followed guids. I installed adb and fastboot and managed to get TWRP 3.1.1-0- on it.
Btw, i have a Honor 5x
Model KIW-L21
I am able to get into the recovery TWRP. I made a backup and saved the folder "BACKUPS" on my PC.
I then downloaded LineageOS from their Homepage: download (DOT) lineageos (DOT) org/kiwi
I downloaded the latest version. I also downloaded Gapps from Opengapps.org. I downloaded ARM64 version 7.1
I wiped my phone completely and copied the two zip files on the phone. I went to "install", selected LineageOS zip and added Gapps. i swiped right to install and the installation stopped with ERROR 7
I tried to download older versions of LineageOS but the same thing happens. ERROR 7
I then downloaded an olderversion of CM13 with GAPPS 6.0. Again, Error 7
I downloaded XENON HD ZIP from here: mirrors (DOT) c0urier (DOT) net/android/teamhorizon/N/Official/kiwi/
Error 7
I downloaded ASOP from here: downloads (DOT) aospextended (DOT) com/kiwi/
Error 7
I looked up Error 7 and its says it is a security check that figures out, that the ROM is not compatible with the Phone. Some guy told me that this happens a lot and that i should use another rom.
I looked for a solution on youtube and found a guy who said that i can do the following:
Unzip the ROM on your pc, go into \META-INF\com\google\android and open the updater script with Notepad++. Delete the first two lines that says asserts, save, close it again and zip the whole package again.
I copied the new, modifiled rom on the phone with the GAPPS and installed it. This time ERROR 7 didnt appear. GAPPS were also installed. When i boot my device i get in the loading screen from Lineage for about 5-10 minutes. After that, it just restarts and restarts and restarts. I can't get out of the boot loop since I can't remove my battery. when I press VOL UP I come back the TWRP and can wipe the phone again.
I tried that with 3 different LineageOS ROMS and one XENON HD ROM.
I also get into a boot loop where my phone just restarts and restarts and restarts.
I tried to get my backup working so I copied the folder "BACKUPS" on my phone and went to restore in TWRP. but... i found nothing there?
I am super frustrated since my phone is basically dead and I have no idea what I can do.
BTW, every site calls my phone "KIWI" but my model number is "KIW-L21"
As mentioned in Los 14.1 thread (& should be mentioned in all threads), "ROM Firmware Required: No VoLTE firmware! (B360, B370, ...)". You must downgrade your stock rom to B350 at least, before try playing with custom roms (only for kiwi, of course).
Non VoLTE Marshmallow firmware is required. As said by @mauam get in there and have the same process repeated
Thank you for your replies.
The only thing i could find was this thread: https://forum.xda-developers.com/ho...-lineageos-14-1-pre-official-kiw-l24-t3528488
It said there:
Important note:
Stock Firmware B360 and B370 are known to cause bootloops!
(Generally: if your stock ROM supports VoLTE it is likely that it is also affected!)
All others might work, please do not ask in here how to up- or downgrade!
It doesnt mentioned what that mean and even said "dont ask in here how to downgrade"
I have no idea what all that means. I dont know what stock firmware is, what version i have or how i could downgrade it. I can access TWRP, but still have no OS on it.
edit: this is the full log:
Updateing partition details...
... done
Full SElinux support is present.
MTP Enabled
Installing zip file '/sdcard/lineage-14.1-20170816-nightly-kiwi-signed.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Comparing TZ version TZ.BF.3.0.C3-00025 to TZ.BF.3.0.C3-00022") =="1"
assert failed: kiwi.verify_trustzone("TZ.BF.3.0.C3-00025") == "1"
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/lineage-14.1-20170816-nightly-kiwi-signed.zip'
Updating parition details...
...done
Click to expand...
Click to collapse
When i edit the zip file and delete the first two line of the updater scripter with notepad++ as i mentioned above, i can install these ROMS, but they wont boot / are in an infinite Bootloop
So on which firmware you were before flashing Los
PalakMi said:
So on which firmware you were before flashing Los
Click to expand...
Click to collapse
how do i check that?
I was able to get the backup running. So I am back to EMUI 3.1 / Android 5.1.1. Here is a screenshot from my phones status: i.imgur (DOT) com/rCnuOpX.png
Activehannes said:
how do i check that?
I was able to get the backup running. So I am back to EMUI 3.1 / Android 5.1.1. Here is a screenshot from my phones status: i.imgur (DOT) com/rCnuOpX.png
Click to expand...
Click to collapse
Just go to about phone
PalakMi said:
Just go to about phone
Click to expand...
Click to collapse
I did and posted a screenshot above
is it Build number "KIW-L21C432B160"
so... B160?
update:
I just downloaded this:
NEW KIW-L21 C432B350 - D003
from this thread: https://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288
I was going to unzip it, copy the "dload" folder on my device, go the the updater and run the "local update package".
And then my phone will be on android 6.0 with b350, right?
The next step would be to start the phone in the recovery TWRP, go to wipe --> advance wipe and select everything (system, data, cache etc). after that i copy the latest Kiwi lineage OS zip rom on my device with the GAPPS 7.1 and try to install them again via TWRP 3.1.1?
Is this right?
I just wanna ask because my phone doesnt work for 2 days now and i dont want to brick it completely. cant afford a new one
Update to marshmallow first (any update before b360, like b320)
Update to marshmallow first (any update before b360, like b320)
Click to expand...
Click to collapse
when i go to the "updater" and and search for a new update it says that there is none. My phone is still on EMUI 3.1/android 5.1.1/b160. Do i need to manually download another firmware? so a B320 patch first (with the dload folder and local upgrade package) and after that the B350 upgrade?
Try manual ota here or search here. If no luck use XDA search bar &/or Google. Good luck.
Activehannes said:
when i go to the "updater" and and search for a new update it says that there is none. My phone is still on EMUI 3.1/android 5.1.1/b160. Do i need to manually download another firmware? so a B320 patch first (with the dload folder and local upgrade package) and after that the B350 upgrade?
Click to expand...
Click to collapse
Try any marshmallow update before b360.
If it didn't work, try the above post.
so i followed this guide: https://forum.xda-developers.com/honor-5x/how-to/manual-ota-update-guide-update-app-t3445976
he describes 2 methods.
I wasnt able to find a B320 update for KIW L21, only for KIW L22 which is the Indian device I think. so I downloaded KIW L21 B330 Denmark. I unzipped the file and copied the dload folder on my device,
i went to update --> menu --> local update --> UPDATE.APP
my phone restarts into TWRP and does nothing. I know that I need the EMUI stock recovery, not TWRP, but no matter how many times I do this, it always restarts into TWRP.
i also tried the other method.
I shut down my phone, press VOLUP and VOLDOWN and Power. The phone goes into the the "honor" loading screen and restats after a few seconds. and restart again and again. If i release the power button before it restarts, it just boots into the system. If I shut it down and hold VOLUP and Power it boots into TWRP. I tried so many different compinations, but i cant get my phone into the EMUI Stock recovery. I read in the other XDA thread, that i need to unlock my phone. So i tried that. i went adb reboot bootloader --> fastboot oem relock CODE. the console did its magic but my phone is still unlocked. And now i cant repeat that command. when i go again into the bootloader and type fastboot oem relock it says:
PS C:\adb> adb devices
List of devices attached
W6HDU17610003396 device
PS C:\adb> adb reboot bootloader
PS C:\adb> fastboot oem relock 1524319619165116
...
FAILED (remote: Image verify failed,relock fail)
finished. total time: 1.810s
PS C:\adb> adb devices
List of devices attached
PS C:\adb>
Click to expand...
Click to collapse
So, i still have b160 / android 5.1 on my phone :/ can anyone figure out what went wrong?
Activehannes said:
so i followed this guide: https://forum.xda-developers.com/honor-5x/how-to/manual-ota-update-guide-update-app-t3445976
he describes 2 methods.
I wasnt able to find a B320 update for KIW L21, only for KIW L22 which is the Indian device I think. so I downloaded KIW L21 B330 Denmark. I unzipped the file and copied the dload folder on my device,
i went to update --> menu --> local update --> UPDATE.APP
my phone restarts into TWRP and does nothing. I know that I need the EMUI stock recovery, not TWRP, but no matter how many times I do this, it always restarts into TWRP.
i also tried the other method.
I shut down my phone, press VOLUP and VOLDOWN and Power. The phone goes into the the "honor" loading screen and restats after a few seconds. and restart again and again. If i release the power button before it restarts, it just boots into the system. If I shut it down and hold VOLUP and Power it boots into TWRP. I tried so many different compinations, but i cant get my phone into the EMUI Stock recovery. I read in the other XDA thread, that i need to unlock my phone. So i tried that. i went adb reboot bootloader --> fastboot oem relock CODE. the console did its magic but my phone is still unlocked. And now i cant repeat that command. when i go again into the bootloader and type fastboot oem relock it says:
So, i still have b160 / android 5.1 on my phone :/ can anyone figure out what went wrong?
Click to expand...
Click to collapse
May be i can help u with this .
Hi there
I am struggeling with the root process of my XA Ultra F3211 (running 7.0 Nougat) and I just don't find a solution for my problem on the internet.
I hope y'all can help me with this one..
I read several guides how I can manage to root my phone, I think the basic points are the following:
- USB debugging has to be enabled - there's no problem with that one
- bootloader has to be unlocked (if possible) - it is possible for my phone and I did it
- USB drivers have to be installed - i installed the whole Android Studio including the SDK manager where I could choose to install the Google USB drivers
- you need the flashtool (I installed v. 0.9.23.1), a boot.img, a custom recovery.img and magisk or SuperSU
1. then you should flash only the boot_delivery.xml from the Marshmallow firmware in flash mode (I guess you need to do that because it's not possible to root Nougat without this step)
2. afterwards you should flash the boot.img and recovery.img in fastboot mode using a command line and the fastboot commands (fastboot flash boot boot.img / fastboot flash recovery recovery.img)
3. after you have done this the custom recovery should be installed and you should be able to boot into it to wipe the phone and flash magisk / SuperSU
That's the road so far.
I've tried these steps but I am not able to boot my Xperia into recovery mode. I think the problem is the boot_delivery.xml because when I tried to flash it from a 36.0.A.2.109 (Marshmallow) firmware (it's named customized_UK, I'm from Germany but I did not find a MM FW for Germany) the flashtool gave me the following information:
- Parsing boot delivery
- No flash script found.
- Flash script is mandatory. Closing session
- Ending flash session
- Flashing finished
I found those lines in some posts on the internet but I did not find any information. Someone said that he copied the default.fsc from the C:\Users\YourUser\.flashTool\devices\F31XX to the F32XX directory and renamed it into device and firmware versions. I did not find any default.fsc in this directory so I copied the one from the F33XX directory and named it "F3211_36.0.A.2.109.fsc" and guess what? I started flashtool and the fsc file was deleted. Even if I created it again while the flashtool was already running the tool never asked me if it should use a script - it just tries to flash and gives me the lines I listed above.
I'm not sure if this is the problem, but flash mode seems to work (the Xperia's LED is glowing green) - so does fastboot mode (blue LED) and for both: no unknown devices in Windows' devicemanager.
Maybe it did already work and I just can't manage to boot into recovery but I tried everything (vol down + powerbutton, vol up + powerbutton, powerbutton and repeatedly vol down or vol up when the screen turns on, hold all three buttons at once) - I think vol down + powerbutton should work, the phone vibrates and shows the Sony logo, I let off the buttons, the screen turns off again, then the Sony logo appears again and the phone starts normally into Android.
Does anyone have an idea what I can try to get my Xperia rooted?
Am I wrong in any point?
Looking forward to reading your answeres and thanks in advance
@dionarap, if the guide explains that you have to use Flashtool v0.9.23.2 why are you using v0.9.23.1 ?? Update it, download firmwares again from included Xperifirm, use FSC script when asked and all should be fine
rrvuhpg said:
@dionarap, if the guide explains that you have to use Flashtool v0.9.23.2 why are you using v0.9.23.1 ?? Update it, download firmwares again from included Xperifirm, use FSC script when asked and all should be fine
Click to expand...
Click to collapse
Thank you very much for your fast response
Well, you got me there. I forgot to exchange the x10flasher.jar in the flashtool directory.. *facepalm*
I'll try it when I'm at home again - but I have one more question before I'll do that.
When I start XperiFirm (through flashtool) and choose my device (F3211) the only entry for the Market "Germany" is build nr. 36.1.A.1.86 / R1B - according to another post that's also Nougat.
So which firmware do I need and could I choose a firmware for any Market if I only need to flash the boot_delivery.xml? Or can I use a downloaded ftf-file from another source? I found the 36.0.A.2.109 firmware (which seems to be MM 6.0.1) but it's named "...Customized_UK" and the at the download source the region was entitled "Russia" so I'm not really sure if I should use this ftf-file. I can find a firmware 36.0.A.2.109 / R6A for the Market "Costa Rica" in the XperiFirm - should I rather use this one?
Is it basically possible to tell which Android version a build nr. like 36.1.A.1.86 (Nougat) or 36.0.A.2.109 (MM) has or did I get something wrong?
Edit: I tried the "Costa Rica" firmware and it worked for me - rooting done
Thanks for the assistance!
dionarap said:
Thank you very much for your fast response
Well, you got me there. I forgot to exchange the x10flasher.jar in the flashtool directory.. *facepalm*
I'll try it when I'm at home again - but I have one more question before I'll do that.
When I start XperiFirm (through flashtool) and choose my device (F3211) the only entry for the Market "Germany" is build nr. 36.1.A.1.86 / R1B - according to another post that's also Nougat.
So which firmware do I need and could I choose a firmware for any Market if I only need to flash the boot_delivery.xml? Or can I use a downloaded ftf-file from another source? I found the 36.0.A.2.109 firmware (which seems to be MM 6.0.1) but it's named "...Customized_UK" and the at the download source the region was entitled "Russia" so I'm not really sure if I should use this ftf-file. I can find a firmware 36.0.A.2.109 / R6A for the Market "Costa Rica" in the XperiFirm - should I rather use this one?
Is it basically possible to tell which Android version a build nr. like 36.1.A.1.86 (Nougat) or 36.0.A.2.109 (MM) has or did I get something wrong?
Click to expand...
Click to collapse
You are on the right way
Yes you can know the Android version with the firmware build numbers.
For the MM firmware, you can download it with any customization/build it's not important we only need boot_delivery.xml
For the N firmware, you have to use the same as flashed in the device. You can download (and flash) it with an other customization too, the differences are small like LTE/4G icon, some apps are different like Spotify, Gameloft, AVG and the APN settings can be missing for your network provider (easy to add).
I don't recommend to download firmwares from the web because you will not have the FSC file who is very important to avoid hard brick. There is a way to manually add it but I will not explain how to do because I really dislike this way.
Thanks again! rooting is complete I think I just was too blind to notice this mistake after googling, reading and trying different things for several hours.. Again thanks for the assistance
@rrvuhpg Please Help buddy..
i've followed all your step but ending with white Sony logo
i can't enter recovery or else. where did i go wrong and what todo?
Please Help... Please
Edit: If I Re-Flash with different regional firmware, will it brick?
anybody please provide link for official N firmware..
Thanks in advance
Hi there
How far did you go? Did you already flash recovery and did you already enter it once? What was your last step before you got the sony screen? I'm not sure if reflashing can harm your phone but I think you should use a firmware downloaded via XperiFirm (it's integrated in Flash Tool). To get a Nougat firmware for Xperia XA Ultra look for build nr. 36.1.A.0.182.
Hope this helps - good luck mate!
Hello,
i got today a Chinese XT1605-05. I flashed the firmware and gapps with twrp from this thread.
The firmware and gapps were installed successfully. But after reboot only the boot animation stucked for around 5 minutes than the smartphone restarts into twrp. Gladly i can copy firmware files to system folder and flash again. So the smartphone isn’t bricked.
Than i tried an older lineage 16.0 firmware => same problem.
And a firmware [URL="https://forum.xda-developers.com/moto-z/development/rom-omnirom-t3881462“] from here[/URL] => same problem.
Now i have nothing running. I have no idea where i could get the right firmware file for this Chinese Version.
And the original (stock image from lenovo) firmware is only available from sources which could be infected. Not a good idea to flash this garbage.
Best regards
TUKF98
Edit:
Ok, here ist the default firmware:
https://forum.xda-developers.com/moto-z/development/moto-z-official-firmware-downloads-t3449837
But it would be better to get android 9.0 working.
Sorry, for double post. It was created by a mistake.
Edit 2:
This stock firmware does not work. Wrong zip file.
Edit 3:
It works now, the lineage version .
I watched this video. And did all steps.
Edit 4:
Now its not working anymore. Its a joke. I installed a new version of lineageOS with the same procedure it worked first.
And now it wont work. The old firmware doesnt work also. WTF. I dont know what is wrong with this thing. Its now again stucking in boot sequence with the "ball moving on the line".
Edit:
Have flashed stock firmware back via fastboot commands. What a crap phone . 100 Euros are cheap, but not as cheap that i would take this ..... .
Now i have installed the original China firmware with trojans.
You cant block this **** from recording every input. But the european firmware does not run on my phone. After flash its hanging in bootloop.
Hello,
first of all i want to mention that i have a special skill when it comes to choosing smartphones to buy. I like em small and cheap so i always had trouble installing custom roms when buying new phones. Just like this time, when i decidied that replacing my Galaxy S5 Mini screen for the fourth time is just not worth it anymore. I ran to the next store, checked the offers, found the Galaxy A20e, did a quick google "A20e lineage" saw there were a few install threads and decided to buy the phone.
That was on Thursday i have since then continuously tried to either root the stock firmware or flash TWRP to install Lineage GSI.
Whatever i try, when rooting with Magisk and afterwards booting the rooted OS using the recovery key combo, the touchscreen won´t work.
I can boot to the unrooted OS and use the touchscreen.
When installing TWRP using XDADEV guide, i can boot to TWRP right after install, wipe and flash required zip file but after the next reboot i can only boot into stock recovery.
Here´s what i did so far:
Software Used:
- Odin 3.14
- Magisk Manager App 7.5.1
- SamFirm 0.3.6
- downloaded the newest Stock firmware "A202FXXU3BTD1"
- unlocked bootloader / SamsungVault
- Flashed newest Firmware "A202FXXU3BTD1" using Odin.
- Installed Magisk Manager
- Patched extracted file "AP_A202....tar" from "A202FXXU3BTD1"
- Moved the patched AP file back to computer
- Flashed modified AP + stock BL, CP and Home_CSC again
- Wipe/Factory reset
- Start Phone with Power+Volume Up until Logo flashes, then release for rooted OS
- Touchscreen not working
- Boot Phone without root (just press Power Button)
- Touchscreen works fine
II then repeated the complete procedure with an Andoid 9 based FW "A202FXXU3ASL4" which ended with the same result.
Then i wanted to move on, since i always thought that Installing TWRP normally does not require root permissions.
I found several guides, some required root, some not. So i decided to try that. I Found two different testing versions, one from xda and flashed them regarding to the HowTo.
With the Android 10 stock firmware, odin was not able to install them at all.
The Android 9 Stock firmware was able to install TWRP and i was able to wipe and flash additional required zip file but after the next boot, i was only able to boot to stock recovery.
I will continue trying different Firmware versions, for now i want to go back to the newest stock FW since i have tried this one in the beginning of my research, maybe now, 15 hours of work later, i will manage to get it running =D
I am willing to provide further details, just let me know. Hope someone has an idea.
best regards,
Hannes
correcting
after frther testing, there is no way to boot into unrooted OS with working touch once magisk patched firmware is installed
GG
looks like reading and testing for 2 days built the right knowledge so after flashing the most recent firmware and only flashing the modified boot.img again (this was one of my first steps ever) this time it seemed to work.
Magisk is officially installed and the system is rooted. on to the next step, i´ll keep reporting.
on to the next one
I was finally able to get TWRP running after flashing Pie based Stock FW.
Now i am stuck installing Q based GSI, they just wont boot.
Pie based GSI work fine, is flashing Q based Stock FW required to install Q based GSI using TWRP?
SOLVED
hannes22 said:
looks like reading and testing for 2 days built the right knowledge so after flashing the most recent firmware and only flashing the modified boot.img again (this was one of my first steps ever) this time it seemed to work.
Magisk is officially installed and the system is rooted. on to the next step, i´ll keep reporting.
Click to expand...
Click to collapse
Could you be more specific on how you managed to root your A20e SM-202F? I've got the exact same issue with an unresponsive touch screen. My bootloader is unlocked, no problem there. I've tried three different firmwares (one of them being the exact same as stock, and the others are newer versions), and several different (but similar) methods. I've tried patching the firmware with both latest Magisk Manager and the canary version. I use latest Odin. I've also tried to patch both the full AP-file and the only the boot.img (boot.tar). But every time that I reboot into android after I've done the rooting I get a touch screen that's not working. I just can't get past that point...
The phone I'm trying to root has Android 10 and U3 bootloader, NEE version.
EDIT - The solution was to first download and flash the newest firmware _without_ using a patched Boot.img or AP.tar-file. I.e, patching the same firmware the phone had out of the box did NOT work. After the firmware update I could successfully flash the patched Boot.img file and root the phone.
Hi there,
My Nokia 7.1 has been stuck on android one screen since last week. I tried several solutions which include:
1. Changing active slot
2. factory reset
3. flashing firmware
When I tried to flash firmware I was not able to do it because bootloader is not unlocked and the flash file that I got was older than my device's. I wanted the flash file for this build number: nokia/crystal_00ww/ctl_sprout 10/QKQ1.190828.002/00WW_4_15X. I searched on internet but did not get it. Can someone help on this?