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?
Related
Hi guys, i have a big problem. I tried to update my girlfriend's phone (huawei g play mini chc-u01). I read some guides and i downloaded all firmwares from huawei site, unlock bootloader and tried to install updates. But at some point, phone won't boot up ! I made a mistake ! Now the situation is that when i turn on the phone, it shows the honor logo. I tried to flash via fastboot the system, recovery and boot image that i extracted from UPDATE.APP of the firmware taken from huawei site. Also tried to flash twrp recovery and find out a way to unbrick phone, but nothing. I can't find anything that works. An other thing is that in fastboot mode, when i type some erase command, output is remote command not allowed, but flash command seems to work.
How can i restore phone ? Is not there a way to restore it, I can make a aspo or cm based rom from system.img and other stock stuff ? Just split image to see files inside.
The last thing and maybe the core of mistake. I flash via twrp an oem file and then honor logo is appeared.
Thanks at all guys !
Edit: I finally restored phone. it works again flashing its lollipop version firmware.
bob1791 said:
Hi guys, i have a big problem. I tried to update my girlfriend's phone (huawei g play mini chc-u01). I read some guides and i downloaded all firmwares from huawei site, unlock bootloader and tried to install updates. But at some point, phone won't boot up ! I made a mistake ! Now the situation is that when i turn on the phone, it shows the honor logo. I tried to flash via fastboot the system, recovery and boot image that i extracted from UPDATE.APP of the firmware taken from huawei site. Also tried to flash twrp recovery and find out a way to unbrick phone, but nothing. I can't find anything that works. An other thing is that in fastboot mode, when i type some erase command, output is remote command not allowed, but flash command seems to work.
How can i restore phone ? Is not there a way to restore it, I can make a aspo or cm based rom from system.img and other stock stuff ? Just split image to see files inside.
The last thing and maybe the core of mistake. I flash via twrp an oem file and then honor logo is appeared.
Thanks at all guys !
Edit: I finally restored phone. it works again flashing its lollipop version firmware.
Click to expand...
Click to collapse
how did you restore your phone ?
I have a g play mini chc-u01 and I upgraded it directly from android 4.4.2 (c185b067 ) to 6.0 (c185b560 ) but this build has many issues. now I want to downgrade to lollipop but I can't get into the recovery mode. whenever I try to enter the recovery mode, the bootloop happens. I tried to flash the system recovery extracted from UPDATE.APP but it didn't work neither did twrp. so can you show me the steps you made to restore your phone ??
Same Problem here. can you share how you fixed it?
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?
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.
Sorry if this is posted in the wrong place but I could not find anywhere to post it by following Help threads I just went round and round in circles. Hi I am fairly new to phone modding. I updated my moto e XT1524 to LineageOS 16.1 some months ago. Yesterday I decided to update to 17.1. I followed the instruction to install. I have wiped phone and ran fastboot adb as instructed. I keep gettting -This packeage is for XT1514,XT1524,XT1526......... ect and error7. I have ammended the updater-script as detailed in the "How to fix error 7 " document but the rom will still not load. same error message. I have now noticed that * Required * firmware version must be based on Marshmallow on the Installation section on the main forum page. Can someone help me get the phone back to stock rom or any other rom for that matter. I can get the phone into recovery mode and I have TWRP installed i aslo have SDK tools installed on PC.
@rddxda
TWRP can't be used to flash Stock ROMs. In your case you need QFIL ( read: Qualcomm Flash Image Loader ) to flash a Stock ROM, and also the Motorola USB driver installed on PC.
jwoegerbauer said:
@rddxda
TWRP can't be used to flash Stock ROMs. In your case you need QFIL ( read: Qualcomm Flash Image Loader ) to flash a Stock ROM, and also the Motorola USB driver installed on PC.
Click to expand...
Click to collapse
Thanks for your help, could you please help a little further as I cannot find a stock rom. I have been on the motorola site and followed a few links on the internet but only to find the file is no longer available. Any idea where I can get a stock rom from or can I use QFIL to load a non stock rom?
I have found a stock rom XT1524_SURNIA_RETEUALL_5.0.2_LXI22.50-13_cid7_subsidy-DEFAULT_CFC.xml.zip this is not an mbn file, however if I open the zip folder there is a fsg.mbn file in there along with boot, bootloader gpt.bin etc. Is this the file to use with QFIL. Sorry to be a pain but I don't want to make the situation worse.
Also can you tell me if restoring to stock rom will this re-lock the bootloader?
UPDATE: First of all thank-you for all your help - I have learned a lot over the past 6 days (that's how long I have been trying to fix it). I flashed lineage-17.1-20200814-recovery-surnia and then sideloaded adb sideload lineage-17.1surnia.zip. Phone now rebooted in normal mode and showing on PC now OK. So old Moto E XT1524 on Lineage OS 17.1.