Downoad: https://android.googleapis.com/pack.../ba01b724176da9aaaf8c58c30f502a2c665a530e.zip
How to extract payload.bin :https://github.com/cyxx/extract_android_ota_payload
patched boot.img : https://mega.nz/#!5tgHCKrY!-rMlD4X2ShS1QTM4TK0g9SW2uJ6QTvwqeJrgC7EscZI
Please can you give me a personal message once the patched boot image upload is complete?
My email address is [email protected]
Thank you
Nanayaw1 said:
Please can you give me a personal message once the patched boot image upload is complete?
My email address is [email protected]
Thank you
Click to expand...
Click to collapse
i found this, and its work
ps: im not in beta tester
https://forum.xda-developers.com/showpost.php?p=78900186&postcount=8
Delta updates aren't extractable.
thorin0815 said:
Delta updates aren't extractable.
Click to expand...
Click to collapse
Don't know exactly what you mean but i managed to extract all images from this payload.bin
My phone is already updated with magisk installed.
So i tried to boot with fastboot command the boot.img extracted and it failed.
-edit
thorin0815 said:
Delta updates aren't extractable.
Click to expand...
Click to collapse
Yes, sad but true... payload dumper says "can´t open image file"
---------- Post added at 08:02 PM ---------- Previous post was at 08:01 PM ----------
k4sh44 said:
Don't know exactly what you mean but i managed to extract all images from this payload.bin
My phone is already updated with magisk installed.
So i tried to boot with fastboot command the boot.img extracted and it failed.
Click to expand...
Click to collapse
Can you share your extracted images?
Here is the zip file with all images.
All images 1.0.4.0 update
But as i told already, i wasn't able to boot with fastboot command the boot.img i extracted.
k4sh44 said:
Here is the zip file with all images.
All images 1.0.4.0 update
But as i told already, i wasn't able to boot with fastboot command the boot.img i extracted.
Click to expand...
Click to collapse
These system/boot images are completely useless, because they are taken from a Delta update and therefore they contain only the code that has changed, not the whole image.
No wonder you couldn't boot up your extracted boot.img, it's only 50% of the file.
Some infos about Delta updates: https://en.wikipedia.org/wiki/Delta_update
So, the patched boot.img of the first post is not valid?
thorin0815 said:
These system/boot images are completely useless, because they are taken from a Delta update and therefore they contain only the code that has changed, not the whole image.
No wonder you couldn't boot up your extracted boot.img, it's only 50% of the file.
Some infos about Delta updates: https://en.wikipedia.org/wiki/Delta_update
Click to expand...
Click to collapse
Ok, good to know.
Thnx
---------- Post added at 09:17 AM ---------- Previous post was at 09:16 AM ----------
jespaper said:
So, the patched boot.img of the first post is not valid?
Click to expand...
Click to collapse
It may be good.
The one i extracted is only 14MB while the one provided in OP is 26
patched boot
Here's a working patched boot, created by applying the OTA and then dumping the partition.
https://mega.nz/#!bUAF1Sba!MPoux619Ti2t90_7qg4oFuwul_OvAwRDI7F7-ZMnwHk
And this is a dump of all the original images in case anyone is interested.
https://mega.nz/#F!CZJBhC6D!ymSe9X-xOnMmnTilNwz8xg
foo9001 said:
Here's a working patched boot, created by applying the OTA and then dumping the partition.
https://mega.nz/#!bUAF1Sba!MPoux619Ti2t90_7qg4oFuwul_OvAwRDI7F7-ZMnwHk
And this is a dump of all the original images in case anyone is interested.
https://mega.nz/#F!CZJBhC6D!ymSe9X-xOnMmnTilNwz8xg
Click to expand...
Click to collapse
Thanks very much for posting the link to OTA dump. The ONLY way of updating my phone is by flashing these files, everything else fails, so good to get them so soon after the ota came out.
the version 10.0.4.0 has drain of battery?
patched boot 10.0.4.0
Hello, this is ori boot.img And patched boot 10.0.4.0 beta tester
---------- Post added at 04:42 AM ---------- Previous post was at 04:31 AM ----------
professor.gold said:
Hello, this is ori boot.img And patched boot 10.0.4.0 beta tester
Click to expand...
Click to collapse
/file/d/1VtrcbUC7yl2kX3KgM0Fmeuxsa4Drw5gW/view
Add a title drive at the start of the download because I am a new member
Vitor00 said:
the version 10.0.4.0 has drain of battery?
Click to expand...
Click to collapse
Not on my side, same battery performance like on 10.0.3.0.
the v10.0.3.0 patched boot img still works on the latest update v10.0.4.0. i tried to reflash it and it worked ! i guess the latest security patched didn't change the boot.img
viking777 said:
Thanks very much for posting the link to OTA dump. The ONLY way of updating my phone is by flashing these files, everything else fails, so good to get them so soon after the ota came out.
Click to expand...
Click to collapse
If it's rooted it might be one of the apps is altering the system partition, I kept getting failed OTA installs as well. What you can try is flashing the current version again and then try to do the update.
My case I'm suspecting it was AdAway because I didn't have the Magisk systemless hosts module installed.
did anyone have original system.img from 10.0.4? i have problem with update i think i forgot have changed something on my system.
Update:
work with this system, Thanks
foo9001 said:
Here's a working patched boot, created by applying the OTA and then dumping the partition.
https://mega.nz/#!bUAF1Sba!MPoux619Ti2t90_7qg4oFuwul_OvAwRDI7F7-ZMnwHk
And this is a dump of all the original images in case anyone is interested.
https://mega.nz/#F!CZJBhC6D!ymSe9X-xOnMmnTilNwz8xg
Click to expand...
Click to collapse
Patched boot v10.0.7.0
Can I have the March patched boot v10.0.7.0 ?? I was unable to find it anywhere. A reply with a link to the patched boot will be appreciated.
Thanks
Related
Here it is for those who need it. I needed it to flash my phone back to stock. The update that was pushed out recently would not work on my rooted phone because I was using a UK rom when I rooted it so I need a stock ('merica) AT&T Status rom that no one seemed to have for any reason. I found the latest update on the HTC website and downloaded their installer, and that failed too. It wouldn't authorize... So into the trash InstallShield exe I went a digging and riped this out of the .cab
I used fastboot to flash the userdata.img, system.img, boot.img and recovery.img to my Status. Rebooted and did a factory reset. SUCCESS. :good:
Download Here:
http://www.mediafire.com/download.php?ncwqh41qa4ry7hi
Lucky-Casper said:
Here it is for those who need it. I needed it to flash my phone back to stock. The update that was pushed out recently would not work on my rooted phone because I was using a UK rom when I rooted it so I need a stock ('merica) AT&T Status rom that no one seemed to have for any reason. I found the latest update on the HTC website and downloaded their installer, and that failed too. It wouldn't authorize... So into the trash InstallShield exe I went a digging and riped this out of the .cab
I used fastboot to flash the userdata.img, system.img, boot.img and recovery.img to my Status. Rebooted and did a factory reset. SUCCESS. :good:
***Going to have to message me to get the download link because this wont let me post it yet.***
Click to expand...
Click to collapse
Have you found something new with this update?
bungphe said:
Have you found something new with this update?
Click to expand...
Click to collapse
Haven't seen anything new yet.
Just pulled this from HTC's website:
"HTC Status™ for AT&T ROM Update | 05.3.2012
Starting May 3rd 2012, HTC will be rolling out a system update for the HTC Status.
This update will only be available for AT&T HTC Status customers and will be sent to the device over the air. Once the release is ready, users will receive a notification on their device advising them of this update and provide instructions to receive and install it. Users can proactively check for this update by going to Home > Menu> Settings > AT&T Software Update > Check for updates.
As an alternative solution, the system update can be downloaded to a PC and manually applied to the device. See the section at the bottom of these instructions for more information.
This system update includes:
Memory allocation fixes to improve low memory issues
Data throttling fix"
So the device is unrooted again?
Did they really solve the low memory issue?
---------- Post added at 09:17 PM ---------- Previous post was at 09:12 PM ----------
Please tell me how to download and flash the rom, thanks.
slow_kknd said:
So the device is unrooted again?
Did they really solve the low memory issue?
---------- Post added at 09:17 PM ---------- Previous post was at 09:12 PM ----------
Please tell me how to download and flash the rom, thanks.
Click to expand...
Click to collapse
My device is now unrooted and I don't really see a reason to root it again. I also never ran into the low memory issue so I can not answer that question. I'll pm you the link...
thanks
Lucky-Casper said:
Here it is for those who need it. I needed it to flash my phone back to stock. The update that was pushed out recently would not work on my rooted phone because I was using a UK rom when I rooted it so I need a stock ('merica) AT&T Status rom that no one seemed to have for any reason. I found the latest update on the HTC website and downloaded their installer, and that failed too. It wouldn't authorize... So into the trash InstallShield exe I went a digging and riped this out of the .cab
I used fastboot to flash the userdata.img, system.img, boot.img and recovery.img to my Status. Rebooted and did a factory reset. SUCCESS. :good:
***Going to have to message me to get the download link because this wont let me post it yet.***
Click to expand...
Click to collapse
nice, i need to fix one, the one you downloaded is htc_status_mr_update_2.14.502.2_us.exe? and when i 7unzip, i only see:
.rsrc - folder
.data
.rdata.text
certificate and
a [0] file of 161,869 kb
so how did you got userdata, system and boot from this file?
thank you very much indeed
atv
atv said:
nice, i need to fix one, the one you downloaded is htc_status_mr_update_2.14.502.2_us.exe? and when i 7unzip, i only see:
.rsrc - folder
.data
.rdata.text
certificate and
a [0] file of 161,869 kb
so how did you got userdata, system and boot from this file?
thank you very much indeed
atv
Click to expand...
Click to collapse
First I used Universal Extractor to extract the files properly from htc_status_mr_update_2.14.502.2_us.exe, because of it being an Install Shield installer. Once it extracted the files in the correct structure I then had to use ZIP Scan on the data1.cab file because Install Shield uses its cab format and very few programs can export them correctly. Once you extract data1.cab you will have all that you need.
hi again
i really want to thank you for your help, the phone was stuck at cmw (s-on) and now its back, but i think that as your post, i should have flashed, userdata.img before, and i did it boot.img then system.img and then i could not flash the userdata.img but the phone turned on finally.
see attached
take care
wilston
atv
atv said:
i really want to thank you for your help, the phone was stuck at cmw (s-on) and now its back, but i think that as your post, i should have flashed, userdata.img before, and i did it boot.img then system.img and then i could not flash the userdata.img but the phone turned on finally.
see attached
take care
wilston
atv
Click to expand...
Click to collapse
Glad I could help my friend!
this is not ICS?
stayfidz said:
this is not ICS?
Click to expand...
Click to collapse
Of course it is! This is the official ICS from HTC, you can read it here: http://www.htc.com/www/help/android4faq/?cid=android4blog
stayfidz said:
this is not ICS?
Click to expand...
Click to collapse
Still GB.
stayfidz said:
Alex C.
1.You confused me, saying it was just a kernel!
2. I've a uk phone, can i install this US on mine?
3. CM9 is way Tard right now?
Re
Click to expand...
Click to collapse
You can install any one your phone. I have had the Asian and UK roms installed before but I would still suggest staying with your region.
i've been trying to unbrick this thing for hours after failed root attempt....i'm trying to use rsd lite to flash back to stock.....i now have access to fastboot and recovery and whatnot.... i cant seem to find the firmware i need to unbrick it. the latest i can find is su6-7.2! if someone found su6-7.3 i feel like that would fix it and id be so happy!!!!!!!rsd fails with 7.2
Su6-7.3 is just the security update.
Just use fastboot to flash the partitions with su6-7.2, you will get the update notification after you're up and running.
I had issues with rsdlite and my ultra when I had it.
Look for Minimal adb and fastboot, you will also need mfastboot to flash the system partition, as its too big for fastboot to handle. If you need instructions on how to manually flash the device, a quick search will reveal easy to follow directions.
Shovales said:
Just use fastboot to flash the partitions. I had issues with rsdlite and my ultra when I had it.
Look for Minimal adb and fastboot, you will also need mfastboot to flash the system partition, as its too big for fastboot to handle. If you need instructions on how to manually flash the device, a quick search will reveal easy to follow directions.
Click to expand...
Click to collapse
but were do i get the stuff im flashing back onto the phone...im pritty sure its system is blank right now
Minimal adb and fastboot:
http://forum.xda-developers.com/showthread.php?t=2317790
Mfastboot:
https://www.androidfilehost.com/?fid=95916177934532795
Firmware:
http://motofirmware.center/files/file/208-cfc-obake_verizon-user-444-su6-72-release-keysxmlzip/
Instructions:
http://forum.xda-developers.com/showthread.php?t=2580060
Shovales said:
Sorry see the my edited post above
Click to expand...
Click to collapse
ok cool im going to try mfastboot now fyi my bootloader is locked still
You're flashing a stock firmware which is signed for the device, so the bootloader being locked isnt problem.
Also mfastboot is used for the system.img to the system partition, you can use fastboot for the other img's.
Shovales said:
Minimal adb and fastboot:
http://forum.xda-developers.com/showthread.php?t=2317790
Mfastboot:
https://www.androidfilehost.com/?fid=95916177934532795
Firmware:
http://motofirmware.center/files/file/208-cfc-obake_verizon-user-444-su6-72-release-keysxmlzip/
Instructions:
http://forum.xda-developers.com/showthread.php?t=2580060
Click to expand...
Click to collapse
i downloaded that firmware already and when i go to extract it its corrupted... i downloaded 3 from the website and still all were corrupted wile unzipping the system image... i redownloaded just to make sure....any other places i can get the firmware?
What are you using to extract the files with?
Shovales said:
What are you using to extract the files with?
Click to expand...
Click to collapse
i tried windows native extract and 7-zip
Winrar I've never had an issue with any file from motofirmware
---------- Post added at 06:06 AM ---------- Previous post was at 06:05 AM ----------
Wait, you said the system image? Do you mean the actual system.img file?
Shovales said:
Winrar I've never had an issue with any file from motofirmware
---------- Post added at 06:06 AM ---------- Previous post was at 06:05 AM ----------
Wait, you said the system image? Do you mean the actual system.img file?
Click to expand...
Click to collapse
i downloaded the zips off of that website already and i was wondering if i can just get links to flash everything individually through fastboot
logan71f100 said:
i downloaded the zips off of that website already and i was wondering if i can just get links to flash everything individually through fastboot
Click to expand...
Click to collapse
Unless you can find the individual files somewhere the firmware zip file that you have is all you got. I downloaded and extracted that same file no more than 2 weeks ago, and nev
er had one bit of trouble with it..
Shovales said:
Unless you can find the individual files somewhere the firmware zip file that you have is all you got. I downloaded and extracted that same file no more than 2 weeks ago, and nev
er had one bit of trouble with it..
Click to expand...
Click to collapse
well im downloading the file again and i installed winrar...would you by chance be able to upload that old file you have to google drive i can give you a link to my drive so you can upload it if you have it
logan71f100 said:
well im downloading the file again and i installed winrar...would you by chance be able to upload that old file you have to google drive i can give you a link to my drive so you can upload it if you have it
Click to expand...
Click to collapse
i just downloaded it again this is the winrar error im getting
C:\Users\Logan\Downloads\CFC-obake_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip: Checksum error in C:\Users\Logan\Downloads\system.img. The file is corrupt
C:\Users\Logan\Downloads\CFC-obake_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip: The archive is corrupt
both om my pcs get the same error wile extracting
logan71f100 said:
i just downloaded it again this is the winrar error im getting
C:\Users\Logan\Downloads\CFC-obake_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip: Checksum error in C:\Users\Logan\Downloads\system.img. The file is corrupt
C:\Users\Logan\Downloads\CFC-obake_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip: The archive is corrupt
both om my pcs get the same error wile extracting
Click to expand...
Click to collapse
I'm having the same problem. I actually need SU6-7 but at this point I'd take SU6-7.2 just to get my phone working again
arcaios26 said:
I'm having the same problem. I actually need SU6-7 but at this point I'd take SU6-7.2 just to get my phone working again
Click to expand...
Click to collapse
do you need the firmware i used to unbrick mine?....btw i got SU6-7.2 to unbrick my SU6-7.3 device.... it is fixed and rooted successfully!
that would work, I bricked mine on 6-7.3
what root method did you use? I'm having a hard time finding one that doesn't require files I can't seem to get downloaded fully
I can try and make a tutorial for you to follow with all files you need in a Google drive for easy access how's that sound?
logan71f100 said:
I can try and make a tutorial for you to follow with all files you need in a Google drive for easy access how's that sound?
Click to expand...
Click to collapse
sounds perfect actually. This phone has given me so many more problems doing this than my old HTC incredible 4g but the phone is far better than that old one.
he only ****ty part us the bootloader is locked and I can't find a way to unlock it. One day there will be a way and I will find it
In case anyone of u ever needs to flash stock boot.img's to restore things,
The twrp telegram group kindly provided me with those backups, i just sorted them and made them available for download...
Currently I have all patches after 4.88 base so may to october security patch...
You can find all stock images here:
https://cloud.vault81.de/s/fnoizKwi8kNF3Rg
and Magisk(v17.2) prerooted patched myself here:
https://cloud.vault81.de/s/AeHiE5HR2qonb3N
Mirror: (All Images)
https://mega.nz/#F!QQp1jQQZ!k5ejlU2NJyic0HusCa_IAQ
Nice job, i have been waiting for this for a long time. Thank you so much ??.
Trissi said:
In case anyone of u ever needs to flash stock boot.img's to restore things,
The twrp telegram group kindly provided me with those backups, i just sorted them and made them available for download...
You can find all stock images here:
https://cloud.vault81.de/s/fnoizKwi8kNF3Rg
Magisk Prepatched Images will be added later...
Click to expand...
Click to collapse
Thanks sir
Greatttttt
Thank you for the img files. Unfortunately i have a problem. When i try to boot the October image with fastboot on A slot where my phone is updated to the october patch - it stucks on android logo. When i switch to B slot which is September patched and use the september img u provided - again the same thing. Any idea?
Mo4o293 said:
Thank you for the img files. Unfortunately i have a problem. When i try to boot the October image with fastboot on A slot where my phone is updated to the october patch - it stucks on android logo. When i switch to B slot which is September patched and use the september img u provided - again the same thing. Any idea?
Click to expand...
Click to collapse
Thats weird... what model do you have? , I thought they work on all Models...
On my device (TA-1012)[Single sim 128gb/6gb], I have exactly the same patches on a and b and both work like a charm with their specific images... Just redownloaded and tested it again...
To narrow down your problem further:
Did you flash anything else? Is your device booting normally when just rebooting? Root? Twrp?
Mo4o293 said:
Thank you for the img files. Unfortunately i have a problem. When i try to boot the October image with fastboot on A slot where my phone is updated to the october patch - it stucks on android logo. When i switch to B slot which is September patched and use the september img u provided - again the same thing. Any idea?
Click to expand...
Click to collapse
If you have another model and some time leftover I would greatly appreciate if you(and everyone else reading this with Another model):
1. could reflash the 4.88 Stock Image
2. Turn off automatic update
3.follow this Upgrade guide over and over again
https://forum.xda-developers.com/no...root-nokia-8-ability-to-t3848390/post77751877
4. Afterwards send me the stock_boot_(randomstuff).gz Magisk generates as Backups in the folder /data or (only viewable with root explorer) AND a screensho of the file creation dates so I know which is which...
I would then upload them and add them to the thread to help others with your model...
No worry's if you don't have time...
Trissi said:
Thats weird... what model do you have? , I thought they work on all Models...
On my device (TA-1012)[Single sim 128gb/6gb], I have exactly the same patches on a and b and both work like a charm with their specific images... Just redownloaded and tested it again...
To narrow down your problem further:
Did you flash anything else? Is your device booting normally when just rebooting? Root? Twrp?
Click to expand...
Click to collapse
Thanks for the replay! My device is TA-1012 [4/64]. I haven't flashed anything. I neither have TWRP or root. When rebooting it is showing the warning that my bootloader is unlocked (offical method). But i noticed something strange. Maybe you will laugh at me :laugh: but the thing is when i boot the phone and the warning pops up it says to press the power button to continue but that doesn't work. I have to wait to boot itself. In the other hand when i boot the stock images you provided the power button works and when i press it, the warning disappears and the android logo pops up. I dont know if this was helpful in some way but i wanted to mention it. Also i will post the backed up img soon that you wanted up there.
Ok so i came up with another idea. I forgot to mention that all these steps i did on Linux so i have Windows also and switched to see if the things are the same. When i enter in cmd, adb recognizes the device without problem. When i write adb reboot bootloader everything is fine. BUT when i write fastboot devices when my phone is in download mode , nothing happens. When i try something like fastboot reboot or fastboot boot xyz.img it says <Waiting for device>. I tried adb and fastboot installer but again nothing. I cannot find nokia drivers, but in OST LA there are 3, i installed them and again nothing. So what should i do?
Edit: It worked when i downloaded new version of adb and fastboot CLI but again - booting the oct img even in Windows cmd makes the phone stuck on android logo
Mo4o293 said:
Thanks for the replay! My device is TA-1012 [4/64]. I haven't flashed anything. I neither have TWRP or root. When rebooting it is showing the warning that my bootloader is unlocked (offical method). But i noticed something strange. Maybe you will laugh at me :laugh: but the thing is when i boot the phone and the warning pops up it says to press the power button to continue but that doesn't work. I have to wait to boot itself. In the other hand when i boot the stock images you provided the power button works and when i press it, the warning disappears and the android logo pops up. I dont know if this was helpful in some way but i wanted to mention it. Also i will post the backed up img soon that you wanted up there.
Click to expand...
Click to collapse
The Power Button stuff is exactly the same for me... Don't think thats the issue...
Really weird, would love to debug further but really have not much other ideas...
Did you try newest fastboot/adb binaries on windows too?
Do you have access to another pc to try it on?
Switched out cables/ports used?
Trissi said:
The Power Button stuff is exactly the same for me... Don't think thats the issue...
Really weird, would love to debug further but really have not much other ideas...
Did you try newest fastboot/adb binaries on windows too?
Do you have access to another pc to try it on?
Switched out cables/ports used?
Click to expand...
Click to collapse
I've switched ports, tried another pc even with different OS (win7). Downloaded the newest adb and fastboot binaries from Android Developers site - nothing. Also i ran a test in fastboot and its says:
bootloader unlocked: true
critical unlocked: false. But i dont think critical is necessary, isnt it?
Mo4o293 said:
I've switched ports, tried another pc even with different OS (win7). Downloaded the newest adb and fastboot binaries from Android Developers site - nothing. Also i ran a test in fastboot and its says:
bootloader unlocked: true
critical unlocked: false. But i dont think critical is necessary, isnt it?
Click to expand...
Click to collapse
If critical was never unlocked it can't have been modified(I think)
Really outta ideas here sorry mate...
Have you tryed booting the prerooted imgs?
Trissi said:
If critical was never unlocked it can't have been modified(I think)
Really outta ideas here sorry mate...
Have you tryed booting the prerooted imgs?
Click to expand...
Click to collapse
Yep the same thing
---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------
I think i should try to flash the stock firmware provided in the forum i think it was the June one. Maybe that will make my device able to flash your images
I have similar issues. I have ta-1012 4/64. When it was of september patch, no september image worked (modified or not), it stucks at "android powered" logo. This is the volatile booting which is performed by "fastboot boot" command.
I use a linux desktop. I tried the latest fastboot executable which came with android-studio and also the one on archlinux android-tools package. (they are a bit different) Results are same.
Now it has october patch. No success with october boot images, too
---------- Post added at 21:59 ---------- Previous post was at 21:53 ----------
Mo4o293 said:
Yep the same thing
---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------
I think i should try to flash the stock firmware provided in the forum i think it was the June one. Maybe that will make my device able to flash your images
Click to expand...
Click to collapse
I think you should wait for TWRP.
Dr. Slump said:
I have similar issues. I have ta-1012 4/64. When it was of september patch, no september image worked (modified or not), it stucks at "android powered" logo. This is the volatile booting which is performed by "fastboot boot" command.
I use a linux desktop. I tried the latest fastboot executable which came with android-studio and also the one on archlinux android-tools package. (they are a bit different) Results are same.
Now it has october patch. No success with october boot images, too
---------- Post added at 21:59 ---------- Previous post was at 21:53 ----------
I think you should wait for TWRP.
Click to expand...
Click to collapse
Yep. We are the black sheeps. Anyway i will definitely wait for TWRP because the other things are risky and thats my daily driver. BTW Im on Manjaro which is based on Arch.
Mo4o293 said:
think i should try to flash the stock firmware provided in the forum i think it was the June one. Maybe that will make my device able to flash your images
.
Click to expand...
Click to collapse
If you do happen to do that please remember this if you have Time....
If you have another model and some time leftover I would greatly appreciate if you(and everyone else reading this with Another model):
1. could reflash the 4.88 Stock Image
2. Turn off automatic update
3.follow this Upgrade guide over and over again
https://forum.xda-developers.com/no...root-nokia-8-ability-to-t3848390/post77751877
4. Afterwards send me the stock_boot_(randomstuff).gz Magisk generates as Backups in the folder /data or (only viewable with root explorer) AND a screensho of the file creation dates so I know which is which...
Click to expand...
Click to collapse
Trissi said:
In case anyone of u ever needs to flash stock boot.img's to restore things,
The twrp telegram group kindly provided me with those backups, i just sorted them and made them available for download...
Currently I have all patches after 4.88 base so may to october security patch...
You can find all stock images here:
https://cloud.vault81.de/s/fnoizKwi8kNF3Rg
and Magisk(v17.2) prerooted patched myself here:
https://cloud.vault81.de/s/AeHiE5HR2qonb3N
Click to expand...
Click to collapse
You can download it on GoogleDrive? links do not open
Anatoly64RUS said:
You can download it on GoogleDrive? links do not open
Click to expand...
Click to collapse
Problem seems on your side
Anatoly64RUS said:
You can download it on GoogleDrive? links do not open
Click to expand...
Click to collapse
Works fine for me too...
I have A pretty restrictive https configuration on that server...
Do you use A massively outdated browser? If Not it should work...
Trissi said:
Works fine for me too...
I have A pretty restrictive https configuration on that server...
Do you use A massively outdated browser? If Not it should work...
Click to expand...
Click to collapse
Browsers are all updated, I'm just from Russia, so a big request to anyone is easy, upload to google drive
Does anyone happen to have the stock ColorOS recovery.img for this device?
Thanks!
Jaernyx said:
Does anyone happen to have the stock ColorOS recovery.img for this device?
Thanks!
Click to expand...
Click to collapse
I've been looking for it also. I couldn't find it in the ozip OTA files.
I have the Chinese variant and want to test the Chinese TWRP, but need the stock recovery just in case...
it's all inside the file system.new.dat.br I'm also trying with the global version
Kratong said:
it's all inside the file system.new.dat.br I'm also trying with the global version
Click to expand...
Click to collapse
I extracted that file. There are a lot of folders. Not sure where to look. Any idea?
with which program? I can't do it I need a fastboot rom
I'll take a look in the system file as well when I get off work.
Smart of you to back your stuff up before diving in. I was trying to see if I could create a rom for my device but I believe I borked my partitions up.
The twrp from wzsx150 in the other thread doesn't boot on my device so I'm hoping the stock recovery image will get me on the right path. I was able to make a bootable twrp but the system partition doesn't mount correctly so I can't flash with it.
I'm pretty new to this stuff but learning more every time I work on it, haha. Should have taken correct precautions though.
Jaernyx said:
I'll take a look in the system file as well when I get off work.
Smart of you to back your stuff up before diving in. I was trying to see if I could create a rom for my device but I believe I borked my partitions up.
The twrp from wzsx150 in the other thread doesn't boot on my device so I'm hoping the stock recovery image will get me on the right path. I was able to make a bootable twrp but the system partition doesn't mount correctly so I can't flash with it.
I'm pretty new to this stuff but learning more every time I work on it, haha. Should have taken correct precautions though.
Click to expand...
Click to collapse
I can't fastboot boot that recovery either and I have the Chinese variant.
Did you do the disable verity etc before trying to boot until your TWRP? Or it could be encryption that's preventing you from viewing the system partition? Might need to format data?
None of these things I'm willing to try without a backup stock recovery though
anandlal said:
I can't fastboot boot that recovery either and I have the Chinese variant.
Did you do the disable verity etc before trying to boot until your TWRP? Or it could be encryption that's preventing you from viewing the system partition? Might need to format data?
None of these things I'm willing to try without a backup stock recovery though
Click to expand...
Click to collapse
I poked around all the dat.br files in the OTA update except the numbered version files and wasn't able to find any recovery.
Unfortunately, I've already fully wiped and it still wont' mount. It kind of seems like my system partition got completely nuked, although tbh I'm not entirely sure how I did that
That being said, I tried directly mounting /system, but I get the error that a block device is required. I checked the fstab files on what I have available and it seems to point to a file that isn't on my device. RIP, haha.
I'll continue to see what I can figure out though. Happy to know it doesn't boot for you actually, as I thought it not booting was due to me gunking up something. Oh yeah, I have a Chinese variant too.
Jaernyx said:
I poked around all the dat.br files in the OTA update except the numbered version files and wasn't able to find any recovery.
Unfortunately, I've already fully wiped and it still wont' mount. It kind of seems like my system partition got completely nuked, although tbh I'm not entirely sure how I did that
That being said, I tried directly mounting /system, but I get the error that a block device is required. I checked the fstab files on what I have available and it seems to point to a file that isn't on my device. RIP, haha.
I'll continue to see what I can figure out though. Happy to know it doesn't boot for you actually, as I thought it not booting was due to me gunking up something. Oh yeah, I have a Chinese variant too.
Click to expand...
Click to collapse
Damn... That's insane! So I guess you have to wait for the stock recovery to be available before you can go back to the stock rom.
What I do like about the stock recovery is that your have the option to go online and install the stock rom.
Kratong said:
with which program? I can't do it I need a fastboot rom
Click to expand...
Click to collapse
Convert system.dat.br to system.dat (brotli)
Convert system.dat to RAW system.img (sdat2img)
Extract system.img (imgextractor)
I installed the twrp chinese version on the global version now i am rom china I wanted to go back but I can't go back to global
Kratong said:
I installed the twrp chinese version on the global version now i am rom china I wanted to go back but I can't go back to global
Click to expand...
Click to collapse
You were actually able to install the CN ROM in the Global variant?!
Yes
---------- Post added at 11:35 AM ---------- Previous post was at 11:25 AM ----------
I need a specific twrp for my model or a fastboot rom to go back to global
Kratong said:
Yes
---------- Post added at 11:35 AM ---------- Previous post was at 11:25 AM ----------
I need a specific twrp for my model or a fastboot rom to go back to global
Click to expand...
Click to collapse
What was the steps you took to go from EU to CN?
I was actually considering going from CN to EU but thought I'd was not possible due to the different partition sizes for system etc..
I can't convert system.img to raw system.img for flash with fastboot can someone post it already converted? for rmx2076.thanks
Kratong said:
I can't convert system.img to raw system.img for flash with fastboot can someone post it already converted? for rmx2076.thanks
Click to expand...
Click to collapse
this link system.img for rmx2076
https://bit.ly/2Yse5ue
i flashed system.img with fastboot reports this error invalid sparse file at header magi. what should i do?
Kratong said:
Yes
---------- Post added at 11:35 AM ---------- Previous post was at 11:25 AM ----------
I need a specific twrp for my model or a fastboot rom to go back to global
Click to expand...
Click to collapse
They just released a flash tool. Let me know if this works for you.
https://www.realmebbs.com/post-deta...subForumId=1156882636577189888&language=zh-CN
thanks later I look at it but is it ok for the global version too? my situation is now this I managed to install the Chinese rom on rmx 2076 involuntarily but the modem part doesn't work everything else works
Kratong said:
thanks later I look at it but is it ok for the global version too? my situation is now this I managed to install the Chinese rom on rmx 2076 involuntarily but the modem part doesn't work everything else works
Click to expand...
Click to collapse
From the looks of it. You just need to have your phone in fastboot mode and select the file you want to flash. So you can try selecting the Global ozip and see if that would bring you back to stock.
Android 11 has been released. Anyone upgraded yet on a rooted device?
Subscribing for root results.
I will try later in a bit and let you know the results.
I need food and drink and the files. Note anyone from India - Please dont download the A11 Files as it isnt for your device.
fkofilee said:
I will try later in a bit and let you know the results.
I need food and drink and the files. Note anyone from India - Please dont download the A11 Files as it isnt for your device.
Click to expand...
Click to collapse
I'm curious to know too!
We gots Root!
So far so good root is working
XMayhem2099 said:
So far so good root is working
Click to expand...
Click to collapse
how did you root? same steps as before with the monthly Android 10 releases? which Magisk are you using?
dimm0k said:
how did you root? same steps as before with the monthly Android 10 releases? which Magisk are you using?
Click to expand...
Click to collapse
I'm guessing, take the OTA, install magisk to inactive slot, reboot and done?
antiochasylum said:
I'm guessing, take the OTA, install magisk to inactive slot, reboot and done?
Click to expand...
Click to collapse
oops, I was hoping to do it via full image rather than OTA
dimm0k said:
oops, I was hoping to do it via full image rather than OTA
Click to expand...
Click to collapse
Probably better to do that lol. My ota is sitting at 1.72gb so it would seem to be a full image.
Did the 1st flash... Didnt boot - Unlocked BL - Looks like nothing flashed to Partition A / Boot A.
Flashing again now ^^
I can't get it to root. I do a fastboot flash boot magisk_patched.img and it fails every time. Anyone had any luck rooting this way?
gettinwicked said:
I can't get it to root. I do a fastboot flash boot magisk_patched.img and it fails every time. Anyone had any luck rooting this way?
Click to expand...
Click to collapse
Do you use the canary build of Magisk or the stable release?
Anyone got a replacement for overscan?
matekaneve said:
Do you use the canary build of Magisk or the stable release?
Click to expand...
Click to collapse
Canary
Well after redownloading the Core Files and updating ADB - Looks like we are alive...
Checking root now.
gettinwicked said:
I can't get it to root. I do a fastboot flash boot magisk_patched.img and it fails every time. Anyone had any luck rooting this way?
Click to expand...
Click to collapse
Not working here either, we need to wait for Magisk update, most probably.
gettinwicked said:
I can't get it to root. I do a fastboot flash boot magisk_patched.img and it fails every time. Anyone had any luck rooting this way?
Click to expand...
Click to collapse
Yes, successfully rooted this way. I didn't play around with any of the betas so this was my first time to just dirty flash right over 10. I patched my own boot.img like usual and transferred it over to my adb folder before flashing. Since you're using MM Canary already, I don't know what to tell you. Maybe your patched boot.img is corrupt? Did you flash the full image or OTA? Next step for me (after creating a new patched boot.img) would be to clean flash the full image. Best of luck.
do you have a link to the canary apk?
I tried going to the canary page, but the download link is dead. TIA
v12xke said:
Yes, successfully rooted this way. I didn't play around with any of the betas so this was my first time to just dirty flash right over 10. I patched my own boot.img like usual and transferred it over to my adb folder before flashing. Since you're using MM Canary already, I don't know what to tell you. Maybe your patched boot.img is corrupt?
Click to expand...
Click to collapse
Further down the page youll see it
https://github.com/topjohnwu/Magisk
---------- Post added at 20:29 ---------- Previous post was at 20:27 ----------
Also to add - Magisk Canary outputted a 4MB Boot Image which was wrong - Correctly patched it should be 32.55 MB roughly.
Make sure you pay attention that the boot.img has been patched properly.
I had trouble rooting but eventually got it to work. I deleted all previous boot images and patched images from phone and pc. Reinstalled platform tools. Grabbed fresh boot img from the factory image, patched it then flashed it. And we're in biz