Good night everyone.
I have a Nokia 2.2 TA-1188 to which I recently unlocked the bootloader successfully using the method from this guide:
[GUIDE] How to unlock the bootloader for Nokia 2.2
To content farms: DO NOT COPY AND PASTE THE ENTIRE GUIDE! Now the last piece of puzzle of Nokia x.2 series bootloader unlock line has been completed, thanks to the help of a member called Woke_World. After I read his procedure, I decided to...
forum.xda-developers.com
However, when I tried to flash the latest TWRP (v3.6.2) over stock Android 9 (the ROM used to unlock the bootloader from the guide above) following the exact procedure shown on TWRP's site, using both the recovery IMG and the vbmeta linked within the instructions (the vbmeta apparently comes direct from Google), the phone became bricked and totally unresponsive apart from periodic short vibrations whenever I try to boot in any way (system, fastboot, recovery, etc.).
What can I do to try revive it?
kevriveroc said:
Good night everyone.
I have a Nokia 2.2 TA-1188 to which I recently unlocked the bootloader successfully using the method from this guide:
[GUIDE] How to unlock the bootloader for Nokia 2.2
To content farms: DO NOT COPY AND PASTE THE ENTIRE GUIDE! Now the last piece of puzzle of Nokia x.2 series bootloader unlock line has been completed, thanks to the help of a member called Woke_World. After I read his procedure, I decided to...
forum.xda-developers.com
However, when I tried to flash the latest TWRP (v3.6.2) over stock Android 9 (the ROM used to unlock the bootloader from the guide above) following the exact procedure shown on TWRP's site, using both the recovery IMG and the vbmeta linked within the instructions (the vbmeta apparently comes direct from Google), the phone became bricked and totally unresponsive apart from periodic short vibrations whenever I try to boot in any way (system, fastboot, recovery, etc.).
What can I do to try revive it?
Click to expand...
Click to collapse
If you can connect to the phone with SP Flash Tool you should be able to flash it with Android 9 again and start over. Just download though, not format + download, because then you'll need to restore your IMEI and serial numbers.
djinc91 said:
If you can connect to the phone with SP Flash Tool you should be able to flash it with Android 9 again and start over. Just download though, not format + download, because then you'll need to restore your IMEI and serial numbers.
Click to expand...
Click to collapse
I have just tried to do so, but to to no avail. I keep getting the following error message:
STATUS_STOR_LIFE_EXHAUST (0xC003001D)
The storage on your device has reached end of life, please change to use new device to do operations
I used the DA bundled with SP Flash Tool and drivers linked in one of the folders, apparently MTK ones.
Here's a screenshot of the error message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was able to download the firmware again after unchecking the Storage Life Cycle Check box within SP Flash Tool's options, and the phone is now up and running, no troubles up so far.
Thank you very much for your help djinc91!
Uhm Ur phones storage chip is literally dying
Thats emmc for u
areallydumbperson said:
Uhm Ur phones storage chip is literally dying
Thats emmc for u
Click to expand...
Click to collapse
I've had no trouble with my storage during all the years I've owned this phone. Never experienced slowdown, errors, loss of data, etc, not now, not before.
Even so, this is just a backup/2nd device used for nothing important, so it doesn't bother or worry me in the slightest. I'll just keep it using it as is until it dies or I just can't make it usable anymore.
Thank you for your heads up, though.
Related
Marcos and I'm from Peru, excuse my English, unlock the bootloader and flashed twrp and the computer started to restart indefinitely, looking for a backup full twrp copy it in my sd card restore from twrp and restart the phone was left screen black with blue led light on, connect to pc and I get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
the mobile does not respond fastboot nor recovery, it's been almost 2 days that I try to recover via qualcomm qfil but I do not find anywhere "programmer patch" download the full rom (2.22gb) contains update.app and extracted via huawei extractor but I can not find the necessary files:
I was researching and I would like to know if it can be created based on my firmware to use qfile or some other program or method to reset my cell phone. Thanks for your help I will be aware of all help.:good::highfive:
I was researching and I would like to know if it can be created based on my firmware to use qfile or some other program or method to reset my cell phone. Thanks for your help I will be aware of all help.
P.S; My phone buys it on the internet and I have no guarantee. Please, I need all your knowledge.:victory::good::good:
nike1973 said:
Marcos and I'm from Peru, excuse my English, unlock the bootloader and flashed twrp and the computer started to restart indefinitely, looking for a backup full twrp copy it in my sd card restore from twrp and restart the phone was left screen black with blue led light on, connect to pc and I get this:
the mobile does not respond fastboot nor recovery, it's been almost 2 days that I try to recover via qualcomm qfil but I do not find anywhere "programmer patch" download the full rom (2.22gb) contains update.app and extracted via huawei extractor but I can not find the necessary files:
I was researching and I would like to know if it can be created based on my firmware to use qfile or some other program or method to reset my cell phone. Thanks for your help I will be aware of all help.:good::highfive:
I was researching and I would like to know if it can be created based on my firmware to use qfile or some other program or method to reset my cell phone. Thanks for your help I will be aware of all help.
P.S; My phone buys it on the internet and I have no guarantee. Please, I need all your knowledge.:victory::good::good:
Click to expand...
Click to collapse
Take a look in here : https://forum.xda-developers.com/general/general/twrp-huawei-y7-trt-lx1-trt-lx3-t3738002
raystef66 said:
Take a look in here : https://forum.xda-developers.com/general/general/twrp-huawei-y7-trt-lx1-trt-lx3-t3738002
Click to expand...
Click to collapse
thanks for your help but I can not enter the erecovery mode
Hello Marcos, I regret not having any solution but, do you still have the backup of this model?
hello, I have not found any solution
Ardavalar said:
Hello Marcos, I regret not having any solution but, do you still have the backup of this model?
Click to expand...
Click to collapse
hello, I have not found any solution since it does not detect anything, from here take the backup https://forum.xda-developers.com/general/general/twrp-huawei-y7-trt-lx1-trt-lx3-t373800. .. specify for huawei y7 trt lx3.
nike1973 said:
hello, I have not found any solution since it does not detect anything, from here take the backup https://forum.xda-developers.com/general/general/twrp-huawei-y7-trt-lx1-trt-lx3-t373800. .. specify for huawei y7 trt lx3.
Click to expand...
Click to collapse
Thank you very much, but I already tried this supposed backup of the TRT-LX3 and it was in a bootloop (unlike the version of the TRT-LX1 that strangely worked).
Ardavalar said:
Thank you very much, but I already tried this supposed backup of the TRT-LX3 and it was in a bootloop (unlike the version of the TRT-LX1 that strangely worked).
Click to expand...
Click to collapse
hi, in my case my computer is completely dead, does not enter fastboot mode or recovery mode only the pc recognizes qhsusbulk.Actualmente I can not find a solution.
Spoiler: Phone Data:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi Guys,
I'm super new to the whole topic and am only doing this because I have a spare smartphone and wanted to learn something.
The bootloader is unlocked.
The USB drivers are installed on the PC.
USB Debugging is turned on.
Smartphone states "Orange State [...]" while booting.
Then I tried to extract the boot.img via the "MTK Droid Root & Tools v2.5.3" to flash this later with Magisk. But here I got the following error message:
Spoiler: MTK Error
The same messages have been there before I did anything on the smartphone for the first time.
From DE to ENG:
--->>> Connect to device <<<---
--- ERROR: --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!--- unknown ROM structure, backup NOT possible!ATTENTION! a file (/system/recovery-from-boot.p) which restores the stock recovery in case of normal phone startup was found!
So I flashed a stock rom here from
Spoiler: link
Umidigi A7 Pro Stock Firmware ROM (Flash File)
Download Official Umidigi A7 Pro Firmware (original flash file) without any password for Free. We also provide the Stock Rom for other Umidigi devices.
xdafirmware.com
to the phone via the SP Flash Tool (because I did something that enabled the first Boot Loop), the phone restarts in factory state succesfully, I set it up once and then installed Magisk, and using Magisk patched the boot.img of the from I downloaded.
However, when I now want to flash it via the flash tool, this error message appears:
Spoiler: Flash Tool Error
And suddenly I am in boot loop. As soon as I flash the original boot.img, the phone starts as usual.
I have also tried the whole thing via TWRP, and as soon as I install Magisk.zip via the TWRP the boot loop angers me again. Also MTK still shows the same error.
Spoiler: I have followed the following instructions:
Main Guide: https://www.getdroidtips.com/root-umidigi-a7-pro/
Helping Video:
Spoiler: Magisk log
I'm happy about anything that helps me out getting this phone rooted
Sorry my friend that noone has yet to have replied to your inquiry here. Ill do my best to give you some of the knowledge I have when it comes to setting you in the right direction without failure next time. Today and for the last month or so I have been working hard with the Umidigi a7 pro 64gb. To be clear are you making sure to flash the magisk zip file of the boot.img file that you saved from the stock firmware. You shouldn't have to fiddle around with to many of the settings just when you do flash the patched file you have to make sure to uncheck everything other then boot.img patched file. I am very new to this as well and honestly it's a tricky process to get it ever done right on your first attempt. You seem to have and know enough knowledge on this topic. MTK is a finnacky processor. I myself have yet to get this device fully rooted yet. The issue I myself have is my PC is not properly updating the MTK and other drivers to make the magic happen which I think I am just going to have to get my other dell going again to try on a fresh PC that I just set up again for this exact thing. To my most recent knowledge though when it comes to the Umidigi a7 pro you have to follow each and every step closely and to a exact precise t or the whole operation will fail every time you try. Are you using your micro SD card to it's full potential and making sure that you saved the patched file properly. You also have to watch for corrupt files when it comes to this kind of thing. But you know enough to just trust the pages you are downloading your files from and make sure everything is signed and legit. Another thing is what seemed to help me is removing SP flash tool completely from my PC. Then re downloading it and starting from scratch by flashing your stock scatter file and I find when flashing hold the power button when it starts for just a few seconds only some people think to keep holding the power button through the entire flash process but to my knowledge what has worked from a noobs perspective is hold power for just a few seconds until the full load of the red bar comes and then when it goes away you can let go of power button and it will continue on with the rest of the manual installment process. There are a lot of high technical highs and lowes when it comes to what you can do here and from the info I've gotten MTK devices weren't really meant to be able to withstand even being remotely compatible devices for root. Honestly let me know how things are going lately for you as I know this post is a bit old. I myself have came close to periodically throwing this phone as far out of the window as it can reach, I'm not a quitter by any means and still today and even right now m working on that to try to help others in any way i possibly can and today I will get this device into full root accesss.
This restore process is intended for the AT&T V60 (lmv600am) model and will most likely WIPE your data so back it up if you want to keep it!
This process will restore the lmv600am to Pixel P4a a13 dp1. I’ve dumped all the required partitions from my lmv600am which has been running this rom for about a week now. I have yet to find any problem at all. To me it seems smooth and fast. This process uses the Qfil utility and assumes you already have a working knowledge of Qfil and that you have already installed it on your Windows PC. If you don’t have that knowledge start reading. The internet is full of Qfil guides.
You can’t damage or fix your existing imei relevant partitions from this restore because they aren’t included in this download.
You are responsible for backing up your existing phone partitions. I’m not liable for you using my work product and you do so at your own risk. If you’re unsure of what you’re doing then read more about Qfil and what is does. Again, if you are a newby go slow. Taking your time will save you a lot of aggravation.
This process will not fix your erased or damage imei number problem. There are process out there for that but they are usually reserved for people with an expert level of knowledge on the subject.
This guide is for anyone who’s presently wanting to try Google’ new Android a13 dp1 release. I have only this when my phone was already on an Android 11 rom. That’s not to say it won’t work coming from an Android 10 rom but I haven’t tried it.
I strongly suggest that you run the “reset option” option from Settings>System>. This will completely reformat and wipe your userdata when completed. No need to go thru the setup process just put phone in edl (9008) mode.
Steps
Download “Lmv600am a13 dp1 P4a Restore Partitions.7z” file from here and unzip. Remember the unzipped restore directory path.
Plug your phone into PC with USB cable and put you phone in EDL (9008) mode. Again, there are guides on how to do this everywhere.
Start Qfil and select the port of your phone’ connection. (See Windows device manager)
Select the v60 firehose (.elf) which is included in the unzipped directory.
Select storage type = ulf which is located at the bottom right of the Qfil dialog screen. I’m using Qfil 2.0.3.5 version. The correct version of Qfil is important as there have been problems with older versions.
Next click on the “load XML” button and group select “rawprogram0” thru “rawprogram6” which are also in the unzipped directory, then hit OK. Next it will ask for the Patch0.xml file, hit cancel as we’re not patching anything.
Wait a few seconds and then click on the “Download” button. Qfil will now resolve all the names of the partitions to be restore and then start the download process to the phone.
When complete phone reboots as I recall.
If you wish you can Qfil load both the eng alb file to abl_a – abl_b which will give you Flashboot mode and your magisk modified boot.img to boot_a – boot_b to give you root. I have both.
When I click download it just gets stuck. There is no ulf storage type on my qfil. Maybe I have the wrong one? I only get ufs and a few others.
edit I guess I bricked it, my other lg v60 works fine lol
nvm again used my laptop. that fixed it. Nice build
does the qdac works?
I update Android 13.How can I restore to origin lg system? It can't work as update steps.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ck5524209 said:
I update Android 13.How can I restore to origin lg system? It can't work as update steps.
View attachment 5562119
Click to expand...
Click to collapse
If you wish to restore to the original AT&T a11 system for lmv600am go to the guide in this forum which I provided. It is meant for this exact circumstance, to enable those that wish to test what they like when they like and then return to a stock a11 environment when they wish.
Was trying to flash my CN ROM to the WW ROM.
Forgot to turn on USB Debugging in Developer Tools.
Couldn't get it work using HunterTik's guide.
Ran flashall_ATF from windows explorer.
Command prompt flashed on screen then vanished.
Tried running flashall_ATF in an elevated command prompt.
It failed but has apparently wiped the ROM. Device is now stuck in boot loop to fastboot.
Whatever option I choose reboots the device back to fastboot.
Windows can see the device but adb devices returns List of Devices Attached is blank.
How do I recover the phone from here?
Found this thread Rog phone 5 stucked on fastboot
Ran this command: fastboot -v flash all WW_ZS673KS_18.0830.2101.75_M2.13.24.14.1-ASUS_1.1.63_Phone-user.raw
Received these lines of text & now device boots to splash screen, gets stuck there, reboots a few times then sends me back to fastboot.
Still can't access recovery mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Device is now back in a fastboot loop with no access to any options but power off & restart.
Your phone is broken
Buy a new phone and don't try to mess with it next time
Flash back to CN and try again.
or, get a dump of the official firmware, then sent boot / recovery / super over fastboot manually.
[Windows] Asus OTA payload auto extractor
Since nobody is doing it, I thought I'd package it and just put it here to help people This is a packaged version of Vm03's payload dumper make to work with windows without installing python and other stuff I also included a single line script...
forum.xda-developers.com
also, you might want to try 9008 rescue. it seems like whatever you're trying to do wiped / repart the partitions. that's why the BL is confused.
also, if you're on win11, some driver related **** can mess things up causing flashing fail.
yurishouse said:
also, you might want to try 9008 rescue. it seems like whatever you're trying to do wiped / repart the partitions. that's why the BL is confused.
also, if you're on win11, some driver related **** can mess things up causing flashing fail.
Click to expand...
Click to collapse
9008 rescue is the direction I was headed & you're right. Although, on reflection, the partitions were already deleted prior to running the 'fastboot -v flash all xx.raw' command. Not sure how, since that command was the only thing I did which resulted in something happening.
So recently my phone was having minor problems.. like randomly restarting and showing overheating warning when the phone isn't even hot.. so ive decided to update it through RSA but turns out RSA dont have the update my phone needed.. I've tried multiple update but not even the china one works even though the phone was originally from china.. can anyone please help.. I'm so sad right now because i dont want to loose this phone
P.s after installing the update from RSA the phone just stuck in boot up then cuts of after
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You have a Pro not a Duel. You will need this first, extract it and place all the files within it to /ProgramData/RSA/Download/romfiles/L79031(delete whats currently in this folder first, then move all the files you downloaded into this folder). Now run RSA and and flash the correct firmware for your Legion Pro. Upon boot, make sure to run System Update to the latest firmware available (you will have to do this two or three times).
&(*) said:
You have a Pro not a Duel. You will need this first, extract it and place all the files within it to /ProgramData/RSA/Download/romfiles/L79031(delete whats currently in this folder first, then move all the files you downloaded into this folder). Now run RSA and and flash the correct firmware for your Legion Pro. Upon boot, make sure to run System Update to the latest firmware available (you will have to do this two or three times).
Click to expand...
Click to collapse
I think I'm in the same situation- And your link doesn't work. What is 'this'? Can't find any info on it!!!
@xXHotBoxXx420 ,
Pretty sure that link was removed. Here is where you'll find the firmware for your device. Just follow the instructions you quoted by @&(*) after gathering your models firmware.
project_2501 said:
@xXHotBoxXx420 ,
Pretty sure that link was removed. Here is where you'll find the firmware for your device. Just follow the instructions you quoted by @&(*) after gathering your models firmware.
Click to expand...
Click to collapse
Hey thank you, but I actually found a CN ZUI 13.5 ROM that I've never found before and flashed it, and it worked. I have Android 12 now, but my cellular still isn't working, and I want a ROM with Google apps by default- one more like the stock android. I assume that's the global version. Trying to go about unlocking my bootloader and flashing the Legion Duels ROM on my Legion pro, I've heard there is a way. Just need to find a good tutorial.
@xXHotBoxXx420 ,
Here is a guide that will work on this device, make sure you read it carefully and backup what it states. I suggest you read this other guide first so you can recover from any mistakes.
project_2501 said:
@xXHotBoxXx420 ,
Here is a guide that will work on this device, make sure you read it carefully and backup what it states. I suggest you read this other guide first so you can recover from any mistakes.
Click to expand...
Click to collapse
Helpful, but I'm wondering if I can do it the other way around; CN to Global rather than Global to CN. I'm sure it probably works the same way, backup partitions and all that. I just figured you had to unlock the bootloader to be able to flash other ROMs but I have flashed the ROW & EE ROMs and ended up with crashdump/bootloop. Didn't realize flashing partitions could fix that. I think I'll give it a try. Thanks