Related
I was thinking.
When ICS is released here in New Zealand....
Would it be possible for someone to change their region to New Zealand (providing it is added to AIO region changer (Great work BTW Condi)) recieve the OTA update and decrypt and add Root etc to it....
Then share that file to me or anyone with NZ region tablet.. and i would be able to gain root from this????
If this is possible we could start a sort of pay-it-forward system. Where someone would do it for me and then I would do it for someone else etc etc.
Just thinking of ways to get around this kernel 10 bastard : ). That some of us are stuck with ATM.
Any ideas if this could work, have been trying to get my head around it all day .
Kernel 10 will resist
Without root, we can only flash official updates signed by Sony... And of course, we don't have Sony's private key to sign any customized / rooted update (well, it's private)
Condi has find a way to flash test-signed updates within his tool but we already need to have root in order to run it.
Our tablet's bootloader is locked, we don't actually know how to run it in fastboot mode so no ClockWorkMod recovery for us.
The only way now is to wait for a kernel exploit like GingerBreak, ZergRush or Mempodroid that will root our tablet or expect another device specific exploit (like Dan Rosenberg's for HoneyComb tablet S not in kernel #10).
So be patient, again and again...
Ok.... Is the root etc added to the tablet before/during the image flashing, or is it added to the zip file???
If it is added to the zip could we not use that zip on other consoles providing the were in the same region i.e nbx03_033 (NZ)?
We (Condi! ) can open an official zip update file and add root in it.
By doing this, we modify the archive's checksums and invalidate the original signature. We can't rebuild it because it needs secrets from Sony. So we sign the zip with a test key, I think taken from the Android Software Development Kit.
This modded zip can be only flashed to a rooted device because root is needed to disable Sony's signature check and temporary replace it by the test signature check in the Android update mechanism.
That's why we can't flash a modded update to our not rooted HoneyComb devices...
Nesquick95 said:
We (Condi! ) can open an official zip update file and add root in it.
By doing this, we modify the archive's checksums and invalidate the original signature. We can't rebuild it because it needs secrets from Sony. So we sign the zip with a test key, I think taken from the Android Software Development Kit.
This modded zip can be only flashed to a rooted device because root is needed to disable Sony's signature check and temporary replace it by the test signature check in the Android update mechanism.
That's why we can't flash a modded update to our not rooted HoneyComb devices...
Click to expand...
Click to collapse
Ahhh gotcha, damn.
So we must find a so called "local root" in order to gain root from the inside :
- Linux kernel exploit, searched by many but very hard to find and immediatly patched (well, our banks have Linux on their backoffice servers too) ;
- Device specific exploit, searched by few but a little easier to find (they have some easy methods on Acer devices, for example) and patched only by the device's provider when he has time for that.
That's what the rooting thing looks like for kernel #10 / not pre-rooted ICS users...
I know that its a stupid idea, but some softwares like quick boot can get you into the bootloader. would that help for checking fastboot? I'm not an expert, just suggesting.
What I know about this :
- no buttons combination (power + volume up/down) to enter fastboot mode ;
- command "adb reboot bootloader" leads to a normal boot.
Some people here have once reported entering a kind of "download" mode by testing things on their tablet but neither know how nor how to go back in it.
Well... Even if someone finds a way, I guess that command "fastboot oem unlock" won't work so we won't be able to flash anything. But as I was saying in another post, Sony techs must have an easy way to flash bricked tablets... Maybe a low-level tool like Samsung's Odin.
Hi, this rom is no longer on navifirm can someone upload it somewhere I've been searching it everywhere.
Rom's name
RM-820_Rogers_Canada_VAR240202_v2_Black
RM-820 Rogers Rom
Yes please , if someone has this rom could they give us a link to download it. As it no longer shows up on navifirm and I rather not flash the ATT version.
it doesnt work anyway...
What doesn't work?
You can't install it on your rogers
I bricked my Developer Lumia 920 , since developer firmware is not available. I was hoping to flash it with Rogers rom.
yeah mine too is a dev
Looks like the links on navifirm are still active, even though they don't show up in the program anymore.
I tried posting the direct links, but it wouldn't let me. I've instead attached a txt file with the links.
To be able to flash them/use them after downloading you might need to rename each file removing the checksum from the file name.
985F2CE8_RM820_1232.2109.1242.1002_RETAIL_nam_canada_200_02_100347_prd_signed.ffu
would be renamed to
RM820_1232.2109.1242.1002_RETAIL_nam_canada_200_02_100347_prd_signed.ffu
etc
If anyone can find links to the RM-820 dev firmware, or even evn just a dump(or produce a dump), it would be much appreciated.
Chilly2112 said:
Looks like the links on navifirm are still active, even though they don't show up in the program anymore.
I tried posting the direct links, but it wouldn't let me. I've instead attached a txt file with the links.
To be able to flash them/use them after downloading you might need to rename each file removing the checksum from the file name.
985F2CE8_RM820_1232.2109.1242.1002_RETAIL_nam_canada_200_02_100347_prd_signed.ffu
would be renamed to
RM820_1232.2109.1242.1002_RETAIL_nam_canada_200_02_100347_prd_signed.ffu
etc
If anyone can find links to the RM-820 dev firmware, or even evn just a dump(or produce a dump), it would be much appreciated.
Click to expand...
Click to collapse
Thanks for the links , I'll keep a lookout for the RM-820 dev firmware. Thanks once again !
I have a problem when I try to flash it it says recovery failed because it says that the FUU is not meant for that product... (and I changed the name of the files)
Error:
0xFA001304: Platform ID check fails. Reason(s): The FFU file is not meant for this product. The platform ID of image does not match with platform ID of the device.
Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.MurzimProgrammingException: 0xFA001304: Platform ID check fails. Reason(s): The FFU file is not meant for this product. The platform ID of image does not match with platform ID of the device.
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariantPackageCompleted>b__8(Object state)
and it's not the first time I flash it with the rogers rom
lolo2007 said:
I have a problem when I try to flash it it says recovery failed because it says that the FUU is not meant for that product... (and I changed the name of the files)
Error:
0xFA001304: Platform ID check fails. Reason(s): The FFU file is not meant for this product. The platform ID of image does not match with platform ID of the device.
Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.MurzimProgrammingException: 0xFA001304: Platform ID check fails. Reason(s): The FFU file is not meant for this product. The platform ID of image does not match with platform ID of the device.
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariantPackageCompleted>b__8(Object state)
and it's not the first time I flash it with the rogers rom
Click to expand...
Click to collapse
This is a known issue with the Rogers Portico ROM, and I assume the reason it was removed. I was the first person to bring this to light on this forum, and fixed it on my phone by installing the pre-Portico ROM and doing an on device upgrade. I do not have the original ROM files anymore, but just be aware you will need the old ROM to make this work.
Does anyone have the Apollo version of the rogers Nokia 920 then ?
Update: I think this guy uploaded it I am gonna try it I'll keep you all updated
update2: it works
http://forum.xda-developers.com/showthread.php?t=2098562
lolo2007 said:
yeah mine too is a dev
Click to expand...
Click to collapse
mine, too. been looking around for the dev fw
I did succesfully flashed my phone with a rom but i dont have it anymore
i ll try to find it again
. Is it in there or the nokia suite. Maybe I can help.
Sent from my GT-N7100 using xda premium
Chilly2112 said:
Looks like the links on navifirm are still active, even though they don't show up in the program anymore.
I tried posting the direct links, but it wouldn't let me. I've instead attached a txt file with the links.
To be able to flash them/use them after downloading you might need to rename each file removing the checksum from the file name.
985F2CE8_RM820_1232.2109.1242.1002_RETAIL_nam_canada_200_02_100347_prd_signed.ffu
would be renamed to
RM820_1232.2109.1242.1002_RETAIL_nam_canada_200_02_100347_prd_signed.ffu
etc
If anyone can find links to the RM-820 dev firmware, or even evn just a dump(or produce a dump), it would be much appreciated.
Click to expand...
Click to collapse
i downloaded the firmware but everytime i try to flash it i get an error regarding the signature; invalid signature any help??
ka24 said:
I bricked my Developer Lumia 920 , since developer firmware is not available. I was hoping to flash it with Rogers rom.
Click to expand...
Click to collapse
I recommend you don't flash the rogers firmware unless you plan on using the phone on Rogers/Fido/Chatr
It has a lot of issues with other carriers (despite being unlocked).
I bought a lumia from rogers without knowledge of these issues and now im stuck with a brand new, opened lumia that I cant use on Telus, and cant sell because WP8 isnt popular.
It would be nice if someone could get a hold of the dev ROM for the Lumia 920.
guys what do you mean by this
0xFA001106: Signature check of FFU file fails. Reason(s): The FFU file is not correctly signed
or not signed for this device.
Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.MurzimProgrammingException: 0xFA001106:
Signature check of FFU file fails. Reason(s): The FFU file is not correctly signed or not signed
for this device.
at Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at
Nokia.CareSuite.PlugIns.MurzimRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariant
PackageCompleted>b__8(Object state)
Good afternoon, XDA community, I've been searching the heck out of Google for an answer to what I'm trying to do, and haven't gotten anywhere.
I have a Motorola Backflip running the latest AT&T firmware, and I'd like to downgrade it back to Android 1.5.
Now, I learned early on the Radio/Bootloader cannot be downgraded. After some digging I've found a thread on ModMyMobile that instructs you on loading the Radio image from the newer firmware into an SBF containing the older Android version. This can then be flashed from RSD Lite, and it'll keep the new radio and bootloader while loading the system partition of old.
However, an update released after that was post was made put the kibosh on that approach. It now refuses anything that isn't an official, signed SBF.
Here's three ideas I think might work, and I'd like your feedback on them:
1.) I have the MBN files extracted from the Android 1.5 SBF sitting on my hard drive. Is it possible to extract the contents of the systemsec.mbn file, load it into a flash-able ZIP; and then flash it via the custom recovery I have on the phone?
2.) If someone out there were to provide me with a backup of the old firmware, created with jr00ds recovery, could it then be modified to remove everything but the system partition, and then simply restore the modified backup to my device?
3.) This is one I know will do the trick: if someone on these forums has an old, battered Backflip that still has Android 1.5 sitting on its ROM, I could just transplant the motherboard to my pristine unit. If any of you have one you're willing to sell cheaply, please let me know!
Before anyone asks the obvious "Why so much effort for an outdated device/version of Android?", it's purely for nostalgia. This was my first Android device, and part of me would like to relive it. Because, frankly, the 2.1 update was just plain terrible.
in this thread i am going to outline the method i used to restore my device to may security patch after completely botching my current install after trying to root, on august security patch.
a major hand to PsYk0n4uT for the suggestions he's posted in response to my problems, giving me the ability to figure out what's really going on here amongst other things.
(this is compatible with metropcs branded devices, therefore is compatible with t-mobile branded devices and so on)
anyways.
download this may OTA i discovered somewhere online. (hint: if download quota is exceeded. make a copy to your gdrive, then put it in a folder. download the folder and you will bypass the quota)
the OTA will contain msmdownloadtool, but it is unusable in it's current form because it's an internal tool. you're gonna want to download this tool off github to help assist in decrypting the .ofp file and flashing it's complete contents over automatically.
extract the OTA zip, and place the tool from github in the same folder. if using linux, install the python requirements and if you're on windows, i would suggest replacing the adb/fastboot executables with current versions. probably shouldn't matter, but i did in this case.
put your phone into fastboot and run the tool. further instructions depending on OS, are on the repository's page.
after flashing i had to switch my active slot over to the prior inactive slot before i could boot.
now that you've got your device downgraded, get through the initial setup, set it up offline, and put your phone into power saving mode so it can't automatically update (just in case)
instead of using DSU sideloader to extract the files we need, we can use the same .ofp file that our images came from and extract its contents with this tool
install magisk, copy your boot image over, patch the boot image, return it back to your computer, and enter fastboot mode.
proceed to flash the boot image, and all 3 vbmeta images. (important: be sure to disable verification and disable verity when flashing your vbmetas)
???
profit
i hope this can help anyone that's got a paperweight for a device at the moment, and help anyone who wants to root their device without a bunch of possible nonsense. in turn, hoping this can accelerate any possible development with this device.
protip: after getting everything installed and set up, install the systemless debloater module in magisk and download de-bloater from f-droid. "remove" the update service application (com.oplus.romupdate) and the software update tab in settings will now think you're on the latest security patch and will prevent your device from accidentally being updated. unless you want that to happen.
mirrors:
[vngsm.vn] GN2200export_11_A.05_2022050718170202.zip | VietNam GSM Services
vngsmservices.com
OnePlus Nord N20 5G Flash File (Official Firmware) GSMMAFIA
OnePlus Nord N20 5G Qualcomm Snapdragon 695 5G Flash File available here with MSM download tool to download via Direct link.
www.gsmmafia.com
And no problem man. Im glad others are sharing their knowledge and experience here. I've been focused on other things trying to make some progress on the device but still having to learn a lot along the way.
Hopefully we will have custom recovery soon. Looking promising so far and the real devs have given more time than I could possibly ever expect towards a device they don't even own.
For anyone wanting to know more about the people that are doing the leg work check out the team at https://t.me/Android_General_Chat The devs work hard to make these things happen so if you wanna help the cause consider making a contribution to them.
dmtec said:
in this thread i am going to outline the method i used to restore my device to may security patch after completely botching my current install after trying to root, on august security patch.
a major hand to PsYk0n4uT for the suggestions he's posted in response to my problems, giving me the ability to figure out what's really going on here amongst other things.
oneplus seems to be weakly supporting this device because i tried to ask them again for the OTA (i mean, it's pulling from somewhere, right) and they told me that i'd need to send it into a service center for repair. what's the point of unlockable bootloaders if user error can't be corrected in some way.
(this is compatible with metropcs branded devices, therefore is compatible with t-mobile branded devices and so on)
anyways.
download this may OTA i discovered somewhere online. (hint: if download quota is exceeded. make a copy to your gdrive, then put it in a folder. download the folder and you will bypass the quota)
the OTA will contain msmdownloadtool, but it is unusable in it's current form because it's an internal tool. you're gonna want to download this tool off github to help assist in decrypting the .ofp file and flashing it's complete contents over automatically.
extract the OTA zip, and place the tool from github in the same folder. if using linux, install the python requirements and if you're on windows, i would suggest replacing the adb/fastboot executables with current versions. probably shouldn't matter, but i did in this case.
put your phone into fastboot and run the tool. further instructions depending on OS, are on the repository's page.
after flashing i had to switch my active slot over to the prior inactive slot before i could boot.
now that you've got your device downgraded, get through the initial setup, set it up offline, and put your phone into power saving mode so it can't automatically update (just in case)
instead of using DSU sideloader to extract the files we need, we can use the same .ofp file that our images came from and extract its contents with this tool
install magisk, copy your boot image over, patch the boot image, return it back to your computer, and enter fastboot mode.
proceed to flash the boot image, and all 3 vbmeta images. (important: be sure to disable verification and disable verity when flashing your vbmetas)
???
profit
i hope this can help anyone that's got a paperweight for a device at the moment, and help anyone who wants to root their device without a bunch of possible nonsense. in turn, hoping this can accelerate any possible development with this device.
protip: after getting everything installed and set up, install the systemless debloater module in magisk and download de-bloater from f-droid. "remove" the update service application (com.oplus.romupdate) and the software update tab in settings will now think you're on the latest security patch and will prevent your device from accidentally being updated. unless you want that to happen.
Click to expand...
Click to collapse
BROOOO you are EFFING AWESOME! MUCH LOVE!
bumping my own thread because people are being real extra after "bricking" their phones trying to get them working again
Really glad people are still working on this device. I've been away for a while and no longer have access to mine right now so just wanted to say thanks to those of you continuing the efforts
Careful with this. Windows Defender flagged a virus when I tried to download it.
Hi, I wanted to root my Mi 11 Lite 5G NE, but without any success (as described in this thread https://forum.xda-developers.com/t/fastboot-is-not-detected-in-device-manager.4499655/), however, I came with the idea of downgrading the MIUI, so fastboot would also be downgraded. I tried doing it via EDL mode, but Xiaomi likes to make things harder, and I need an authorized Xiaomi account or a patched prog_firehouse_ddr.elf file. Does any of you know where I could possibly get that file? If you know any trusted source, I can even pay for it, send me source via DM
fibur said:
Hi, I wanted to root my Mi 11 Lite 5G NE, but without any success (as described in this thread https://forum.xda-developers.com/t/fastboot-is-not-detected-in-device-manager.4499655/), however, I came with the idea of downgrading the MIUI, so fastboot would also be downgraded. I tried doing it via EDL mode, but Xiaomi likes to make things harder, and I need an authorized Xiaomi account or a patched prog_firehouse_ddr.elf file. Does any of you know where I could possibly get that file? If you know any trusted source, I can even pay for it, send me source via DM
Click to expand...
Click to collapse
Downgrading will result in an anti rollback lock due to the formation of ente top code in the init. So an auth authorized account is required to make changes.
Aitra said:
Downgrading will result in an anti rollback lock due to the formation of ente top code in the init. So an auth authorized account is required to make changes.
Click to expand...
Click to collapse
There should be no problem with downgrading. Other users did as well
But you must not use Mi Flash - just use Fastboot, 7-Zip and Notepad:
- download Fastboot ROM, best use
MIUI Downloader - Apps on Google Play
MIUI upgrade app for Mi users.
play.google.com
Choose Stable, Global or EEA, Older versions
- On the PC, un-gzip and un-tar, you will find couple of bat files
- Take the batch file whose name suggests that Factory Reset will be included, but WITHOUT RELOCKING BL
- Open by Notepad, and take a look.
First 1-2 lines inspect if the phone is Lisa - leave them
Then come 5-6 lines inspecting about roll-back.
You should REMOVE those lines and save the bat file (you can rename and keep the original)
- Run the modified batch file through Fastboot, it will flash the corresponding MIUI stock ROM, without checking for roll-back, and without relocking BL (once you successfully reboot to the System and make sure everything is ok, you can later relock BL)
Similar instructions and guides can be found on Internet and YT - maybe for some other Xiaomi phones, but about the same method