Hello (hopefully) Black Shark Owner,
Unfortunately, it seems that rooting the Black Shark prevents the ability to use OTA on the phone.
What i need, is your help:
if you have a Black Shark on G66X1901082OS00MPX, Please reply to this thread.
I will give you instruction to help me fix my phone, and if that works, i should be able to create an Image that can be flashed to Black Shark Global phones, to restore them to Stock condition (and allow OTA again)
Thanks to @leipnacht, i was able to fix my phone, update from pre-2019 version, to the latest security update at june 2019.
I will post instructions later for everyone with broken OTA.
gilbert32 said:
Hello (hopefully) Black Shark Owner,
Unfortunately, it seems that rooting the Black Shark prevents the ability to use OTA on the phone.
What i need, is your help:
if you have a Black Shark on G66X1901082OS00MPX, Please reply to this thread.
I will give you instruction to help me fix my phone, and if that works, i should be able to create an Image that can be flashed to Black Shark Global phones, to restore them to Stock condition (and allow OTA again)
Click to expand...
Click to collapse
Just an FYI for the link I posted on your JoyUI thread, I have here the dsp files for G66X1901140OS00MPX version.
G66X1901140OS00MPX dsp images
leipnacht said:
Just an FYI for the link I posted on your JoyUI thread, I have here the dsp files for G66X1901140OS00MPX version.
G66X1901140OS00MPX dsp images
Click to expand...
Click to collapse
Your dsp files worked!
unfortunately, now my bluetooth partition is also changed (possibly others too).
Can you share bluetooth_a.img? (turns out your slot a is on the system version i have, so i only need slot a files).
Hopefully bluetooth is the only other broken partition
BTW, you can zip them, so that upload goes much faster.
gilbert32 said:
Your dsp files worked!
unfortunately, now my bluetooth partition is also changed (possibly others too).
Can you share bluetooth_a.img? (turns out your slot a is on the system version i have, so i only need slot a files).
Hopefully bluetooth is the only other broken partition
BTW, you can zip them, so that upload goes much faster.
Click to expand...
Click to collapse
These are the bluetooth images. Here you go. For other files. I'll upload it if there's free time here at work
bluetooth images SKR-H0 (G66X1901140OS00MPX)/
leipnacht said:
These are the bluetooth images. Here you go. For other files. I'll upload it if there's free time here at work
bluetooth images SKR-H0 (G66X1901140OS00MPX)/
Click to expand...
Click to collapse
Bluetooth works now
The next partition i need is modem. :fingers-crossed:
@leipnacht did you have a chance to upload the backups?
I only need slot a backups, and right now my OTA fails on the modem partition.
gilbert32 said:
@leipnacht did you have a chance to upload the backups?
I only need slot a backups, and right now my OTA fails on the modem partition.
Click to expand...
Click to collapse
Just go on this link
G66X1901140OS00MPX Backups
This is a shared folder. I'll just upload all the stuffs there. Just check it time to time
leipnacht said:
Just go on this link
G66X1901140OS00MPX Backups
This is a shared folder. I'll just upload all the stuffs there. Just check it time to time
Click to expand...
Click to collapse
Awesome, Thanks!
The backups from @leipnacht seem to be working for me. Once i test it completely, if my phone resumes OTA, i will try to make a backup and package it into a flashable zip.
That way, anyone should be able to restore his phone completely.
gilbert32 said:
The backups from @leipnacht seem to be working for me. Once i test it completely, if my phone resumes OTA, i will try to make a backup and package it into a flashable zip.
That way, anyone should be able to restore his phone completely.
Click to expand...
Click to collapse
have you done with the ota ? thx
kanded said:
have you done with the ota ? thx
Click to expand...
Click to collapse
Yes. I used ota and got 2 updates. After updating, i rerooted and got magisk back.
Edit: did you mean the flashable zip? No i didn't, but i uploaded a full backup in another thread.
gilbert32 said:
Yes. I used ota and got 2 updates. After updating, i rerooted and got magisk back.
Edit: did you mean the flashable zip? No i didn't, but i uploaded a full backup in another thread.
Click to expand...
Click to collapse
hi gilbert i have black shark 1 china how to i get ota update? can you help me? (my phone unlocked, twrp and magisk installed)
Can Somebody Know How To Fix Null Imei, I Converted My Black Shark 1 CN To Global
I have a blackshark global after dead recovery got null imei and unknown baseband . QCN cannot be restored on the device . I have used many programs and boxes to restore qcn but i get unknown response from phone . any help ?
Related
Hi all, I have a TS 1/8/2100, firmware 20140513.
TWRP and Bluetooth tether ROM are available for firmware 20140328 only. Past conversations make me think there won't be any update soon.
A solution would be to install previous firmware, then TWRP, then update firmware. But partitions changed in between.
According to this SP Flash Tool can also physically format a partition if you can get a partition management table (PMT). The scatter file describes logical partitions, but it seems you can also add PMT. (After backup with MTKDroidTool, click "prepare Blocks for FlashTool")
Knowing this, provided that hardware is relatively unchanged, it could be possible for newest TS to enjoy TWRP happiness.
I would like to try, if someone could be kind enough to give me a stock backup for TS 1-8-2100 firmware 20140328 with PMT. (there sould be a file called MT6572_Android_scatter_emmc_PMT.txt)
I need you to help me help you to help me help you.
thx.
MrTip said:
Hi all, I have a TS 1/8/2100, firmware 20140513.
TWRP and Bluetooth tether ROM are available for firmware 20140328 only. Past conversations make me think there won't be any update soon.
A solution would be to install previous firmware, then TWRP, then update firmware. But partitions changed in between.
According to this SP Flash Tool can also physically format a partition if you can get a partition management table (PMT). The scatter file describes logical partitions, but it seems you can also add PMT. (After backup with MTKDroidTool, click "prepare Blocks for FlashTool")
Knowing this, provided that hardware is relatively unchanged, it could be possible for newest TS to enjoy TWRP happiness.
I would like to try, if someone could be kind enough to give me a stock backup for TS 1-8-2100 firmware 20140328 with PMT. (there sould be a file called MT6572_Android_scatter_emmc_PMT.txt)
I need you to help me help you to help me help you.
thx.
Click to expand...
Click to collapse
Here you go - hope it's what you're looking for..
Tigerite said:
Here you go - hope it's what you're looking for..
Click to expand...
Click to collapse
No, it's not. The key element of my message is
with PMT. (there sould be a file called MT6572_Android_scatter_emmc_PMT.txt)
Click to expand...
Click to collapse
Thank you anyway.
That's all that was generated by the tool I'm afraid, I followed the steps from the link you provided too, but still no joy. It only produces the standard one, no PMT suffix.
Tigerite said:
That's all that was generated by the tool I'm afraid, I followed the steps from the link you provided too, but still no joy. It only produces the standard one, no PMT suffix.
Click to expand...
Click to collapse
That's unfortunate. Did you click on "prepare Blocks for FlashTool" after backup ? I'll try myself asap to confirm the procedure.
Yes I did, but no PMT text file in the relevant folder..
Tigerite said:
Yes I did, but no PMT text file in the relevant folder..
Click to expand...
Click to collapse
Well, the procedure is correct. It appears that PMT can be (or not) in scatter file without any difference in the filename. So you have to check by yourself, as I did, if you want to format. (look for many lines per partition, like 'physical_start_addr' and 'linear_start_addr')
You have to select "format+download" in "sp flash tools" to format everything (including preloader, so be carefull).
Take all precautions: Backup everything, including userdata and cache partition, because sp flash tools will ask for it if you have to format. Do not forget to backup nvram.
Doing this, I successfully formatted the TS and installed previous firmware, 20140328.
Sadly, the TS won't boot. Here lies my hope to get TWRP and bt tether ROM working without update from its creator...
So, back to firmware 20140513.
After the new format+backup, TS boot normally, but I had a "IMEI invalid" error. So, I used MTKdroidtools to restore nvram the same way I previously backed it up.
Complete 'format+download' is to be used if you messed up with partitions or if partitions changed.
Could be usefull, this was to let you know how.
MrTip said:
Well, the procedure is correct. It appears that PMT can be (or not) in scatter file without any difference in the filename. So you have to check by yourself, as I did, if you want to format. (look for many lines per partition, like 'physical_start_addr' and 'linear_start_addr')
You have to select "format+download" in "sp flash tools" to format everything (including preloader, so be carefull).
Take all precautions: Backup everything, including userdata and cache partition, because sp flash tools will ask for it if you have to format. Do not forget to backup nvram.
Doing this, I successfully formatted the TS and installed previous firmware, 20140328.
Sadly, the TS won't boot. Here lies my hope to get TWRP and bt tether ROM working without update from its creator...
So, back to firmware 20140513.
After the new format+backup, TS boot normally, but I had a "IMEI invalid" error. So, I used MTKdroidtools to restore nvram the same way I previously backed it up.
Complete 'format+download' is to be used if you messed up with partitions or if partitions changed.
Could be usefull, this was to let you know how.
Click to expand...
Click to collapse
What exactly are you trying to do?
kuronosan said:
What exactly are you trying to do?
Click to expand...
Click to collapse
Install last firmware known to be working with twrp.
Did that.
The device doesn't boot anymore.
Revert to previous backup.
Did that.
I like to see things by myself.
It's not your firmware that's the problem. I'm running twrp on the latest firmware without issue.
kuronosan said:
It's not your firmware that's the problem. I'm running twrp on 20140513 firmware without issue.
Click to expand...
Click to collapse
I can only rely on testimonies on this very forum, but I have not seen a single person succesfully installed twrp on firmware 20140513.
I have seen successfull install on previous firmware, and then OTA upgrade.
What is it for you ?
It is exactly what I told you. It's up to you to believe me or not.
kuronosan said:
It is exactly what I told you. It's up to you to believe me or not.
Click to expand...
Click to collapse
You didn't told me if its an install on 20140513 firmware or if it's an upgrade from previous firmware.
kuronosan said:
EU 1/8 users who have the new aluminum watch or who received their units after May 13th need to click here and also need to remember that recovery may not work (although it probably won't work before this anyway).
Click to expand...
Click to collapse
I understand you agree there is a problem with twrp 2.7.1.0 on newer devices.
You'll notice I did say new devices. Not new firmware.
kuronosan said:
You'll notice I did say new devices. Not new firmware.
Click to expand...
Click to collapse
Ok then, you win by default. Look at me asking a simple question while you obviously rather going back an forth playing fallacy pong. Please forgive me if I cut this short. I'll click on Thank You anyway.
Anyway to get back to the thread.. I've tried everything, booting in recovery, running MTK Droid Tools as Administrator, installing busybox again - but still no PMT file. I'm all out of ideas now..
Tigerite said:
Anyway to get back to the thread.. I've tried everything, booting in recovery, running MTK Droid Tools as Administrator, installing busybox again - but still no PMT file. I'm all out of ideas now..
Click to expand...
Click to collapse
That's OK. It appears that PMT can be (or not) in scatter file without any difference in the filename. (If you look in the file and see many lines per partition, like 'physical_start_addr' and 'linear_start_addr', you have PMT)
So I found what I was looking for, thank you.
MrTip said:
Ok then, you win by default. Look at me asking a simple question while you obviously rather going back an forth playing fallacy pong. Please forgive me if I cut this short. I'll click on Thank You anyway.
Click to expand...
Click to collapse
No one is trying to win. I have a good deal of experience with MTK devices based on my researching various methods of backup/restore/flash/etc and I was offering a hand.
You can play one-person pong with yourself and claim fallacy all you want or you can get off your high horse.
Up to you. I have work to do.
TWRP Install on newest firmware + OTA
got watch on 7/26. did OTA. firmware date 5/27/2014. unable to install TWRP via any method including shell DD command. well it installs but on entry I just get on the old andy with red ! showing. It seems like a watchdog timers reboots it after a few minutes and all is back to the way it was.
Which TWRP did you use?
Hello,
It seems that many of HAM2 users have the consumer cellular variant and are irked by several modifications done on the stock ROM that one gets when he buys the phone unlocked. Many of us, including myself, would like to flash the stock ROM if possible but maybe are not brave enough to try .
Someone uploaded several versions of different ROMS on https://drive.google.com/folderview?...0&usp=sharing. So, the question is can we flash any of these ROMS on our consumer cellular variant and if so, how ? I used to have a samsung galaxy young and flash different countries ROM using ODIN so many times that I can't remember how much. I tried that because it was confirmed to work. So, can the same be done on our HAM2 ?
Thanks.
The problem with flashing oem firmware
medwatt said:
Hello,
It seems that many of HAM2 users have the consumer cellular variant and are irked by several modifications done on the stock ROM that one gets when he buys the phone unlocked. Many of us, including myself, would like to flash the stock ROM if possible but maybe are not brave enough to try .
Someone uploaded several versions of different ROMS on https://drive.google.com/folderview?...0&usp=sharing. So, the question is can we flash any of these ROMS on our consumer cellular variant and if so, how ? I used to have a samsung galaxy young and flash different countries ROM using ODIN so many times that I can't remember how much. I tried that because it was confirmed to work. So, can the same be done on our HAM2 ?
Thanks.
Click to expand...
Click to collapse
The 126 firmware in that folder is the original firmware that came on the consumer cellular version. The problem with flashing the complete 148 firmware is inside udate.app file there is a file named oem_verlist.img. The is a partition in the root directory of the phone for that img file to be flashed. when you go to update with the 148 firmware that img file realizes that it does not match the phone that you are trying to flash to and bring up a error and fails. I have tried to fastboot that img file to its partition but it will not go. Maybe I am using the wrong parition name but with out updating that partition before trying to flash it will fail.
mtyler7807 said:
The 126 firmware in that folder is the original firmware that came on the consumer cellular version. The problem with flashing the complete 148 firmware is inside udate.app file there is a file named oem_verlist.img. The is a partition in the root directory of the phone for that img file to be flashed. when you go to update with the 148 firmware that img file realizes that it does not match the phone that you are trying to flash to and bring up a error and fails. I have tried to fastboot that img file to its partition but it will not go. Maybe I am using the wrong parition name but with out updating that partition before trying to flash it will fail.
Click to expand...
Click to collapse
When you say "update", do you mean clearing the OS and installing a new one from scratch ? Does that mean after the update all the consumer cellular additions will go away and there will be no trace of it ?
If updating seems difficult now for the consumer cellular versions, what will we do when they release Lollipop ?
If they do not release a cc version then I would have to extract the OEM update.app file from the huawei site to all the IMG files and fastboot flash one at a time(force flash if you want to call it). Inside the update file there will be a system.IMG, data.IMG, cache.IMG,etc
Sent from my MT2L03 using XDA Premium 4 mobile app
mtyler7807 said:
If they do not release a cc version then I would have to extract the OEM update.app file from the huawei site to all the IMG files and fastboot flash one at a time(force flash if you want to call it). Inside the update file there will be a system.IMG, data.IMG, cache.IMG,etc
Sent from my MT2L03 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Assuming they release the CC version of lollipop, will there be any problem if some of the system files have been changed? For example, I've deleted some system apps that I never use and changed the boot- and flash-screen files. Will the update fail because of that ? I'm asking this because I saw a video made by one of the forum members here when he was trying to install the v148 update. He had to uninstall everything and return the system to default before updating. If that is so, then I guess no Lollipop crying::crying for me !!
Given that Lollipop is still some months away and the lack of any meaningful activity on the HAM2, why don't we prepare our HAM2 for who-knows-what. I'd like to get a grip on a my phone now instead of getting swamped by error messages when Lollipop gets released or we get custom firmware.
There's this thread [http://forum.xda-developers.com/showthread.php?t=2315547] which explains how to extract the individual image files from the huawei update app.
Do you have the CC version of HAM2 ? If so, will you be trying to flash the image files because extracting the image files seem straight-forward ? I'm actually a bit nervous doing it myself because I've always flashed my other devices when it has been confirmed to work. What I'm wary of is I'm not sure that the device software in the v148 update app is 100% compatible with the CC variant that I own ! How can one be sure of that ?
I've downloaded v148 update file and extracted the files you mentioned. Instead of taking screenshots of the contents of the image files, I've recorded a small video. I can see the boot.img and system.img but no recovery.img. There are also other files. Take a look at the video. The question now is what to do with these files and more importantly what are my chances of unbricking the phone if it bricks !!
It will not fail because of boot animation and splash screen change. It will fail because of missing system apps. You would need to reinstall those if the package comes as a upgrade but if it is a full download then your OK.
Dealing with extracting the files from the update.app just search for my post, I have a complete instruction guide.
Sent from my MT2L03 using XDA Premium 4 mobile app
mtyler7807 said:
It will not fail because of boot animation and splash screen change. It will fail because of missing system apps. You would need to reinstall those if the package comes as a upgrade but if it is a full download then your OK.
Dealing with extracting the files from the update.app just search for my post, I have a complete instruction guide.
Sent from my MT2L03 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Have you seen the video I uploaded ? Is it the "full download"? Can I flash it ? Will the phone brick ?
I read your posts on the subject. But it seems you have changed some system apps and the camera is not working as it should. I have already downloaded the 148 file and extracted the system.img and boot.img files. Can I flash these or do I have to use the files you uploaded on google drive ?
The question is why didn't you use the v148 stock ? I already have the v148 stock. Will it brick my phone if I flash the image files ? If not, why did you have to add extra files there such that the camera is 8MP instead of 13MP. Also, why is the hotspot always enabled ? Is that the case with people with the original stock ?
Man, I'm still waiting for your reply !
medwatt said:
Man, I'm still waiting for your reply !
Click to expand...
Click to collapse
My understanding is it is possible to flash to stock if your bootloader is unlocked and have TWRP installed. Then its as simple as flashing a backup from a matching model with stock frimware. For whatever reason mtyler7807 is trying to reinvent the wheel.
290 said:
My understanding is it is possible to flash to stock if your bootloader is unlocked and have TWRP installed. Then its as simple as flashing a backup from a matching model with stock frimware. For whatever reason mtyler7807 is trying to reinvent the wheel.
Click to expand...
Click to collapse
"For whatever reason mtyler7807 is trying to reinvent the wheel", Ha Ha. I spent about 2 weeks working on this phone when I first got it. With this phone it has more partitions than what is included in the backup with TWRP. TWRP is made for backup and restoring the files that get changed, the other partitions don't change. So when I first started experimenting with this phone I got a full 148 backup with no data and installed it. I had problems, the custom.bin points to a different cust/us/ folder (because it is for a different carrier) , I had to rename that folder and found I have no more 4glte only H/H+, So I had to get the original cust folder from the guy and copy it to the phone. Still and only H/H+. It was okay for then because I testing. Next Viewed my system specs and saw that pretty much half half phone was 148 and the other half was 132.
I have Redone my complete back since I posted the last one with google camera with 13mp support( rather have border transparency). I made a post asking people summit backups. You have to do a little research, did my research and got help from the forum guys. If you want 148 on your CC version you will have to extract the update and fastboot img files (ex.fastboot flash system system.img). The name of the file is the partition name.
From my understanding twrp does a nand backup. Which is more like an image of nand. So restoring an image from a stock phone would also give you the stock partition table no?
It has been a while since ive played with android on such a low level. When it came time to update my HP Touchpad to JB i had to manually create the partition table manually to make it fit. Eventually a script was created that automatically made the changes to the file system. Perhaps a solution along those lines could be useful in getting the stuck firmware on the CC phones? The file system would only need to be created on initial flash to the stock firmware.
mtyler7807, I've been trying to get an answer since I first created this thread. The only reason I want to install the original huawei stock instead of the cc version is because I want to be able to download and install updates just like regular stock huawei HAM2 users instead of waiting for the CC version. So, please can you answer these questions :
1. If I follow your steps and use the image files you uploaded, will I get rid of CC completely meaning will my phone be just like a stock HAM2 phone from Huawei ?
2. Can I install Huawei updates directly, instead of having to do what you did (extracting the image files and the rest of the process).
3. If the answers to the above questions is no and no, then whats the point of installing your images files (apart from getting the hotspot which I don't use) ?
Please answer these questions unambiguously so that I and others will get a clear understanding of the reasons to flash the image files you uploaded. In doing so, people will stop creating these threads asking boundless questions.
Thanks.
medwatt said:
mtyler7807, I've been trying to get an answer since I first created this thread. The only reason I want to install the original huawei stock instead of the cc version is because I want to be able to download and install updates just like regular stock huawei HAM2 users instead of waiting for the CC version. So, please can you answer these questions :
1. If I follow your steps and use the image files you uploaded, will I get rid of CC completely meaning will my phone be just like a stock HAM2 phone from Huawei ?
2. Can I install Huawei updates directly, instead of having to do what you did (extracting the image files and the rest of the process).
3. If the answers to the above questions is no and no, then whats the point of installing your images files (apart from getting the hotspot which I don't use) ?
Please answer these questions unambiguously so that I and others will get a clear understanding of the reasons to flash the image files you uploaded. In doing so, people will stop creating these threads asking boundless questions.
Thanks.
Click to expand...
Click to collapse
Here is what k2thejx5 said after flashing a backup from a stock phone.
k2thejx5 said:
What's weird is when I flashed the stock file and tried to upgrade, it wouldn't work. The kernels were different so I had to go back to stock consumer rom. Also, while using the rom you posted.. I lost my toggles and had to use a different app. What also was very weird, after flashing back to the stock consumer rom, I had tethering! Don't get it lol.
Click to expand...
Click to collapse
-Do what I did makes your phone a complete oem, All that is need to be done is to flash a splash screen.
-How would I know if updates will work since 148 is the latest version for oem, can't test that tell lollipop.
-I'm not pushing anyone to install my image, I got about 30 pm's to post my recovery to enable hotspot and to get those toggles backup at the top. Alot of people messed up and lost them flashing that original twrp recovery under developer. Alot of others wanted the hotspot without the head ache of going through the research.
And for the people with problems with there phone that want 148 and updates with no problems, You should have brought a OEM and stayed away from sears or target or took it back to the store if you were not ready to take on the challenge of fabbing up your phone. Or just deal with the factory image and hope for lollipop.
---------- Post added at 02:14 PM ---------- Previous post was at 02:06 PM ----------
Me and k2thejx5 was trying to fix the problem with the twrp recovery originally posted on this site. That one is not mine. Read the post. That firmware took our toogles away. You have to read this forum a little more.
Ok man, thanks for the reply. Two last question:
-For as long as you've been using your phone with your image files, have you been noticing problems like "unexpected crashes", trying to launch something and its unresponsive lie APN
-Is this the latest file you recommend : [https://drive.google.com/file/d/0BwnSk8BOQp3wV0JMWnJGc3RBTzQ/view]
Thanks.
I have to make another one. I created a new one with epic browser and 360 deg rotation. And I added Camera JB+. Thats the best camera add out there to me, looks just like google 5 camera. I can post image of this new one. I'll Back up my phone and clear the cache and restore it with no data so none of my info will be saved that belongs to me. then i'll setup up the phone and back it up and post.
mtyler7807 said:
I have to make another one. I created a new one with epic browser and 360 deg rotation. And I added Camera JB+. Thats the best camera add out there to me, looks just like google 5 camera. I can post image of this new one. I'll Back up my phone and clear the cache and restore it with no data so none of my info will be saved that belongs to me. then i'll setup up the phone and back it up and post.
Click to expand...
Click to collapse
All right then. Upload it when you're ready !
Hey guys.
I'm trying to update my F1 but since it's rooted, OTA is not happening (it caused my phone to TWRP bootloop) and other's have reported that they had a better working version flashing the update via the SP Flash Tool. So last time I tried using the Flash Tool was a mess getting it to work (because drives and all) so I was hoping someone might have an image of this update that I could flash via TWRP or is there's a way to convert the extracted RAR folder. Thanks for any help.
David C.
mantarkus said:
Hey guys.
I'm trying to update my F1 but since it's rooted, OTA is not happening (it caused my phone to TWRP bootloop) and other's have reported that they had a better working version flashing the update via the SP Flash Tool. So last time I tried using the Flash Tool was a mess getting it to work (because drives and all) so I was hoping someone might have an image of this update that I could flash via TWRP or is there's a way to convert the extracted RAR folder. Thanks for any help.
David C.
Click to expand...
Click to collapse
The OTA update may be used in Twrp, with some edits, depending on what all has been changed on phone .
I do not have time this weekend to look at it. But can in few days
***UPDATE***
This can update from version 20190316 only
If you open the update.zip you have from the OTA and replace the 'updater-script' with the one attached here. It should perform the update. Remove the ".txt" from the file name first
I say should , because if you have done significant modifications then that may effect its effectiveness.
@mantarkus
I put together an OTA style zip, that has the same images as sp flash install, with only exception being the preloader. The preloader from stock OTA update is different format to the preloader used in flash tool. ( Assume it has to do with the way it gets intalled ) So I have the preloader from OTA in the zip.
I have not uploaded the zip, or tested it out. Before i use the data to upload it. Let me know if you are interested.
mrmazak said:
@mantarkus
I put together an OTA style zip, that has the same images as sp flash install, with only exception being the preloader. The preloader from stock OTA update is different format to the preloader used in flash tool. ( Assume it has to do with the way it gets intalled ) So I have the preloader from OTA in the zip.
I have not uploaded the zip, or tested it out. Before i use the data to upload it. Let me know if you are interested.
Click to expand...
Click to collapse
Hey, thanks a lot. Yes, I am interested. Is this flashable via TWRP?
David C.
mantarkus said:
Hey, thanks a lot. Yes, I am interested. Is this flashable via TWRP?
David C.
Click to expand...
Click to collapse
It should be. Have not tested it. So busy lately.
Best option is to use the flash tool, but after I test this, I will uploaded it. But who knows , rumor us, there had been updated every 2 months so far. Maybe new update is out soon anyway
Anyone know if this is working on the normal F1 (Non-play) version? With the minimal differences including same SoC shouldnt it work? Anyone tested?
wtf rip, i refreshed and i landed here somehow (by my own fault probably). Mean't for: https://forum.xda-developers.com/android/development/twrp-twrp-3-3-0-0-umidigi-f1-play-t3933829
flashing this recovery on my non-play if anyone knows. Soz '
Nexus Radical said:
Anyone know if this is working on the normal F1 (Non-play) version? With the minimal differences including same SoC shouldnt it work? Anyone tested?
wtf rip, i refreshed and i landed here somehow (by my own fault probably). Mean't for: https://forum.xda-developers.com/android/development/twrp-twrp-3-3-0-0-umidigi-f1-play-t3933829
flashing this recovery on my non-play if anyone knows. Soz '
Click to expand...
Click to collapse
Yes, I have been told it does work for both play and not play. I am using the ported version of that official build , done by "ghost"
Oh right. I did a bit of searching before asking for a link but I did find this
ghost45 said:
New Umidigi f1 recovery 3.3.1 test2 is pubblished.
Test this one if all is corrected...
http://www.mediafire.com/file/1emy4tk1gvnkj96/recovery-twrp-3.3.1_Umidigi_F1_test_2.rar/file
Click to expand...
Click to collapse
Will this work fine? I know it's a test version. As long as flashing works properly, decryption and mtp works I guess that's all I need?
Otherwise what would you say is the best available twrp version right now? ?
My phone had been rooted via Magisk, some system update box kept coming up, but I kept tapping cancel as I didn't think it would work anyway. Yesterday, I'm not sure if it was forced or it tapped something in my pocket, but now it has installed the update, and *boom* I'm on Android 10. Build number V11.0.5.0.QFQEUXM. Root lost, everything else seems to work though. I have a notification from Magisk Manager that says update available! press to download and install.
Should I do that to regain root? Is that the safest way to do that? I have backups, but I'd rather not have to go through that faff. Thanks so much for your help! And this super useful forum! Thanks will be given also :fingers-crossed:
FR Ray said:
My phone had been rooted via Magisk, some system update box kept coming up, but I kept tapping cancel as I didn't think it would work anyway. Yesterday, I'm not sure if it was forced or it tapped something in my pocket, but now it has installed the update, and *boom* I'm on Android 10. Build number V11.0.5.0.QFQEUXM. Root lost, everything else seems to work though. I have a notification from Magisk Manager that says update available! press to download and install.
Should I do that to regain root? Is that the safest way to do that? I have backups, but I'd rather not have to go through that faff. Thanks so much for your help! And this super useful forum! Thanks will be given also :fingers-crossed:
Click to expand...
Click to collapse
The easiest way to re-root your phone is to follow the steps on this post here. However, there are no .img files for the last versions.
I need the fastboot for 11.0.19 Global
lbsilva said:
The easiest way to re-root your phone is to follow the steps on this post here. However, there are no .img files for the last versions.
I need the fastboot for 11.0.19 Global
Click to expand...
Click to collapse
The guide you mentioned in your post also contains a link in which you can extract your own boot image and use that image to patch via Magisk to obtain root.
Here is the link: DUMP stock boot.img
pkdon123 said:
The guide you mentioned in your post also contains a link in which you can extract your own boot image and use that image to patch via Magisk to obtain root.
Here is the link: DUMP stock boot.img
Click to expand...
Click to collapse
Hi thanks for the link! It looks like I will use the TWRP and Magisk method, as there is less to go wrong. But the links on that post are from 2019, so I'm guessing they are not compatible with A10. I've found this post: https://forum.xda-developers.com/showpost.php?p=82372895&postcount=139 to try to find some updated links, but the mirrors cannot be found
FR Ray said:
Hi thanks for the link! It looks like I will use the TWRP and Magisk method, as there is less to go wrong. But the links on that post are from 2019, so I'm guessing they are not compatible with A10. I've found this post: https://forum.xda-developers.com/showpost.php?p=82372895&postcount=139 to try to find some updated links, but the mirrors cannot be found
Click to expand...
Click to collapse
I used the steps from the same post for obtaining root on my stock Android 10 V11.0.14.0.QFQMIXM i.e. global version. Now I don't know whether it will work on V11.0.19 Global or not, but it should. I cannot test it now because I'm using EvolutionX Custom ROM now.
Hello,
I found a firmware file for the Nord N20 5g. However, it is CPH2459_11_A.06, while my phone says it is GN2200_11_A.06. Would it still be possible to do a local update to pull the boot image, or must the CPH and GN match? I have the T-Mobile version, bootloader unlocked, and network unlocked , along with the July security patch.
Thanks!
Take a full-backup of your firmware and find out.. lol.
DrScrad said:
Take a full-backup of your firmware and find out.. lol
Click to expand...
Click to collapse
I'm unfortunately not that brave
Rogo00 said:
I'm unfortunately not that brave
Click to expand...
Click to collapse
Want me to give it a go?
DrScrad said:
Want me to give it a go?
Click to expand...
Click to collapse
It would be awesome just to see if it works, but I don't know if it would harm your phone or not, and I would feel terrible if it did.
i would try flashing to inactive slot then switch over and maintain your functional system
PsYk0n4uT said:
i would try flashing to inactive slot then switch over and maintain your functional system
Click to expand...
Click to collapse
I'm still too new to rooting to do this successfully, I'm afraid
cph2459 is the unlocked version of the N20 5G correct? could you link the firmware please?
It is the unlocked version. I have the TMO version but it is network unlocked. The firmware can be found here: https://mega.nz/file/MXckFawK#IZ1ypD5Ftqw5Oz3oaeHLahqfUeaD6DlTzHCjeR3oseg
Also, this one is GN2200, but it is 11_A.05. Would it downgrade with the current patch? https://mega.nz/file/lX1H3Z5C#hUVmdbWUFI0bt0WQZVfaenTfVwoOqlfn2oexY5uC-Hs
If the OTA contains patches for all the required images then it SHOULD. But don't take my word on that.
What exactly are you trying to accomplish? Do you simply need a backup? It would probably be best to load a prerooter gsi with DSU sideloader and just use Partitions Backup and Restore app from playstore and backup all your partitions then just add them all to a single archive to make it easier to manage. You can select in options to save as raw (.img) and then just compress them all into a single archive and that would make it even easier to retrieve the needed partition images if you happen to need to restore anything.
PsYk0n4uT said:
If the OTA contains patches for all the required images then it SHOULD. But don't take my word on that.
What exactly are you trying to accomplish? Do you simply need a backup? It would probably be best to load a prerooter gsi with DSU sideloader and just use Partitions Backup and Restore app from playstore and backup all your partitions then just add them all to a single archive to make it easier to manage. You can select in options to save as raw (.img) and then just compress them all into a single archive and that would make it even easier to retrieve the needed partition images if you happen to need to restore anything.
Click to expand...
Click to collapse
I see. Basically I'm just trying to obtain root access. You mentioned prerooted gsi? I will need to read up more on this. Man this would be a lot easier with TWRP lol
waiting to hear from someone about a twrp that has been in the works. we tried one yesterday that didnt work. a different device tree is needed from the one that was used.
using DSU loader you can temporarily load a prerooted gsi and back everything up and move it to your pc and then move the boot.img to your internal storage where you can easily find it with the magisk app. install and load the magisk app and patch the boot.img then move the patched boot image to your pc and flash it in fastboot. that will give you a permanent root unless you prefer to stick with the gsi you sideloaded. but keep in mind any gsi you load with DSU Sideloader will be gone when you reboot the phone and your back to your regular system. you can use the sticky command if you want to keep the gsi installed but be sure to allocate plenty of space for your gsi if you plan on using it long term
if your on the may or july security patch you should be able to just download the patched boot.img from my other thread. i posted the stock images too in case you need to go back to stock or have issues booting. that being said. its best to just make your own backups. the july patch is GN2200_11_A.06
PsYk0n4uT said:
if your on the may or july security patch you should be able to just download the patched boot.img from my other thread. i posted the stock images too in case you need to go back to stock or have issues booting. that being said. its best to just make your own backups. the july patch is GN2200_11_A.06
Click to expand...
Click to collapse
I didn't know you did the July patch as well. I will check it out now
Also if and when you do flash the magisk patched boot images, do this command before and/or after flashing the boot.img:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Someone else has tried this and lost radios..... Can maybe get everything working again by reflashing the FULL BACKUP you took before cross flashing.... This would be an experiment though so don't attempt if your not ready to spend some time researching and unbricking your device should it be necessary
I tried it. I'm bootlooped
bricklife4me said:
I tried it. I'm bootlooped
Click to expand...
Click to collapse
I was just about to ask if you had two different devices because remember me telling you to be careful and not get your flashes mixed up?
DrScrad said:
I was just about to ask if you had two different devices because remember me telling you to be careful and not get your flashes mixed up?
Click to expand...
Click to collapse
I have a samsung a02, pixel 7 pro, moto g 5 g , oneplus n20 , iphone 12, iphone 6 , 4 tablets, and two LG