Related
November, 29 2011
Honeycomb-Beta-v3.5 for P1000L/N
Download
Instructions (use P1000LVJJM9 Froyo downgrade)
You can download JM9 ROM here .
__________________________________________
November, 03 2011
New kernel for stock Gingerbread.
Really, It is my first stable release.
Odin/Heimdall or CwM Recovery -> HumberOS
Sources at http://code.google.com/u/humberos/
__________________________________________
August, 21 2011
New ROM version HumberOS-v2.1
Based: JP2 - P1000L
Features
APK e Framework Fully Deodexed e Zipaligned
Root e Busybox
Reboot/Recovery/Download [options on power button]
New battery icons
New Pop-ups
New bootanimation (thanks to Alberto Maciel)
New wallpaper
New kernel version 20111027
Download Here
__________________________________________
August, 21 2011
New ROM version HumberOS-v2.0
Based: JP2 - P1000L
Features
Download Here
__________________________________________
August, 21 2011
I created a place for discussion about P1000L/N in Portuguese language.
[Construí um espaço para discussão sobre os modelos P1000L/N em português]
http://www.humberos.com.br
Kernel Changelog
KERNEL - ChangelogCM7 P1000N KernelJune, 21 2011
CM7 Beta with P1000N gingerbread stock kernel.
Stock P1000N KernelJune, 14 2011
Added CF-Root by binary procedure.
June, 24 2011
Added Ext4 support.
June, 27 2011
New version with Voodoo Lagfix
July, 18 2011
New version with Overcome CwM Recovery v4.1.0.9 + Voodoo Lagfix
Overcome CwM Recovery Updated to v4.1.0.9 (Based off ClockworkMod Recovery v4.0.0.9)
Option under Tweaks to enable/disable shortened backlight fix
Nandroid restore no longer borks the kernel
No more annoying "back button disabled" (Hooray!)
Shortened Yes/No confirmation menus
Make /dbdata wipe when executing "factory reset/data wipe"
Make /emmc/.android_secure wipe when executing "factory reset/data wipe"
Complete restructuring of menus
Streamlining of commands and elimination of some never used features that were cluttering the interface
August, 21 2011
New version with Overcome CwM Recovery v4.1.1.4 + Voodoo Lagfix
Overcome CwM Recovery Updated to v4.1.1.4 (Based off ClockworkMod Recovery v4.0.0.9)
more space
Reserved!
For Changelogs...
....
Instructions and References
CM7 - Cyanogenmod 7
Official Thread
Author: @Technomancer
Reference: Cyanogenmod WebsiteCF-Root
Official Thread
Author: @ChainfireHeimdall - Open-Source Cross-Platform Flashing Suite
Official Thread
Author: Benjamin DobellOVERCOME
Official Thread
Author: @alterbridge86Install/Recovery MethodsTroubleshootingIf you have a Froyo stock ROM then you should check if your bootloader is signed/secured.
JM9 P1000L version have a protected bootloader.
You can download app and get more informations about bootloaders here.
Some ROMs dont have a dbdata.rfs file.
dbdata.rfs is necessary for flash NEW roms.
dbdata.rfs link for Gingerbread
Before flash, open .tar file (rom) and drag dbdata.rfs into package.
After flash if your 3G dont work, you should install modem of the previous rom.
You can do this replacing modem.bin (JM9) file into .tar package before flash.Recovery - Black ScreenMany P1000L/N users are trying to install the new android version (Gingerbread).
If your device shows a black screen you will need press on power button some time for power off it.
Now, for download mode you will press this buttons: Home + (Vol -) + Power
You can test download mode with Odin. When it shows COM Port (yellow) enabled.
You need learn about Heimdall.
What is Heimdall?
Heimdall is a cross-platform open-source tool suite used to flash firmware (aka ROMs) onto Samsung Galaxy S devices. More information.
Now, you should download P1000L stock ROM (Password is "samfirmware.com"):
P1000L
Uncompress .rar
Uncompress .tar
You will see:
boot.bin
cache.rfs
factoryfs.rfs
gt-p1000_mr.pit
hidden.rfs
modem.bin
param.lfs
Sbl.bin
zImage
Now, using Heimdall command line, you will flash boot files.
Be careful!
Its very IMPORTANT...
Its works ONLY on P1000N or P1000L devices.
Command for recover:
Code:
heimdall flash --primary-boot boot.bin --secondary-boot Sbl.bin
REMEMBER - The boot files is signed.
Read this topic for solve this.
Voce é o caraaaa!!
Can i use this with...?
overcome 2.0.x will work with this kernel?
and the bootloader?
Wait, this is the official binary kernel + cf-root?
Can I install this with BJP3?
No CwM yet, right?
THANKS!
rslee said:
Wait, this is the official binary kernel + cf-root?
Can I install this with BJP3?
No CwM yet, right?
THANKS!
Click to expand...
Click to collapse
AFAIK, CF-root does have CwM inside already.
This should be ok to use with Overcome too, since Overcome only asks for a GB kernel.
Thanks you very much Humberto, spared me of the work of understanding kernels
Greetings Santroph.
humberos said:
June, 14 2011
I've just ported CF-Root to new Gingerbread Kernel.
Thread about CF-Root
Kernel Download
Flashed by Heimdall 1.0.2b
Uncompress file and write follow command:
Code:
heimdall flash --kernel zImage
Click to expand...
Click to collapse
Humberto, coule you please make a tar/odin version of the kernel? For some reason my heimdall don't connect to my device, no matter what I do.
I can only get a -12 error (cannot connect)
I have installed the drivers and everything else.
Greetings, Santroph.
santroph said:
Humberto, coule you please make a tar/odin version of the kernel? For some reason my heimdall don't connect to my device, no matter what I do.
I can only get a -12 error (cannot connect)
I have installed the drivers and everything else.
Greetings, Santroph.
Click to expand...
Click to collapse
The kernel is a .tar file.
Regards,
Humberto
Sent from my GT-P1000N using XDA Premium App
Hi Humberto,
I'm planning to flash Gingerbread using Heimdall.
I have three questions:
1º) I'll decompress the ROM file and substitute dbdata.rfs and modem.bin with the files you said in the other thread and flash everything with Heimdall (repartition enabled). Is it right?
2º) The bootloaders at the Gingerbread P1000N ROM is fully compatible with P1000L device right?
3º) Is it possible to post here the md5sum of each file that I will need to flash using heimdall? I'll be much more calm if I can compare the md5sum of the files you have flashed and we know that work with the ones I'm suppose to flash.
Thanks,
Ronan
humberos said:
The kernel is a .tar file.
Regards,
Humberto
Sent from my GT-P1000N using XDA Premium App
Click to expand...
Click to collapse
I'm sorry, the old kernel tar files I had had a lot os scripts inside too, so I thought this one wouldn't be accepted by Odin, it worked fine and now I have root
Thank you very much.
Our bootloaders are signed and apparently locked with this rom, do you think it is safe to use the apk to unlock them and than use Overcome?
Greetings, Santroph.
Hello HumberOS
Hi Humberos, I have a galaxy P1000N tab to which you installed your rom and I am as P1000L, then install the Kernel ltn_20110612.tar all very well without complaints with the bootloader unlocked with root enabled ..!
My question is: If I install this new kernel ltn_cfroot_r1 Gingerbread can install without problems ..?
Could you tell me the procedure I followed and the files I need to get this q Gingerbread once flashed with your new kernel ..?
As I said originally my Tab is a P1000N your Rom and you have used Odin 20110612 kernel 1.7 for all procedures
Sorry for the length of my questions but understand I need to do to not ruin my tab and I am very new to this and I would greatly appreciate a clear and comprehensive response to achieve what I ask you as well as a detailed been generous with other users ..
Thank you very much Greetings from Ecuador
scalamusical said:
Hi Humberos, I have a galaxy P1000N tab to which you installed your rom and I am as P1000L, then install the Kernel ltn_20110612.tar all very well without complaints with the bootloader unlocked with root enabled ..!
My question is: If I install this new kernel ltn_cfroot_r1 Gingerbread can install without problems ..?
Could you tell me the procedure I followed and the files I need to get this q Gingerbread once flashed with your new kernel ..?
As I said originally my Tab is a P1000N your Rom and you have used Odin 20110612 kernel 1.7 for all procedures
Sorry for the length of my questions but understand I need to do to not ruin my tab and I am very new to this and I would greatly appreciate a clear and comprehensive response to achieve what I ask you as well as a detailed been generous with other users ..
Thank you very much Greetings from Ecuador
Click to expand...
Click to collapse
I don't think you can flash a Gingerbread kernel on a Froyo ROM, can you?
Hello alroger
So I must first pass a Gingerbread Froyo ...?
I can do it directly from the ROM HumberOs or need to return to the Rom of bone stock original Samsung firmware ...?
Thank you very much for your time and help
Greetings from Ecuador
Ronis_BR said:
1º) I'll decompress the ROM file and substitute dbdata.rfs and modem.bin with the files you said in the other thread and flash everything with Heimdall (repartition enabled). Is it right?
Click to expand...
Click to collapse
You will uncompress .tar and PASTE dbdata.rfs, because this rom dont have it.
Ronis_BR said:
2º) The bootloaders at the Gingerbread P1000N ROM is fully compatible with P1000L device right?
Click to expand...
Click to collapse
Yes, I am using them.
Ronis_BR said:
3º) Is it possible to post here the md5sum of each file that I will need to flash using heimdall? I'll be much more calm if I can compare the md5sum of the files you have flashed and we know that work with the ones I'm suppose to flash.
Click to expand...
Click to collapse
SHA1SUM
Code:
34f374d5be752ebfba3d3846a66727429b63c948 boot.bin
3e6a3d1e6ce91189de1a5776fd91e5a267ee0543 cache.rfs
4c836791da2af319a82d85e8d7af4dce36f60e7c factoryfs.rfs
88497436de86d8b29eccbe7bb34a1422d23867b6 gt-p1000_mr.pit
a20ac1413882718f2c607e7f775dd74920d4a66d hidden.rfs
d7ede0664ff1ba6cdd0f7e9e80e1eba478c63521 modem.bin
cc8888883068c827347f769a9ce395b3290bc3aa param.lfs
45f9cd331a07cb6e6b4468267421c874ef76ddf0 Sbl.bin
7ab6bbf12e5d362c121a09dc500d15b886214838 zImage
Regards,
Humberto.
Maikeu Locatelli said:
Can i use this with...?
Click to expand...
Click to collapse
P1000N or P1000L (without Tv tuner)
Maikeu Locatelli said:
overcome 2.0.x will work with this kernel?
Click to expand...
Click to collapse
I think yes, but I dont tested yet.
Maikeu Locatelli said:
and the bootloader?
Click to expand...
Click to collapse
The bootloaders ARE signed, but NOT secured.
I think that custom kernels and firmwares will can still be flashed.
Regards,
Humberto.
rslee said:
Wait, this is the official binary kernel + cf-root?
Click to expand...
Click to collapse
Yes! Official "binary" P1000N kernel with CF-Root.
rslee said:
Can I install this with BJP3?
Click to expand...
Click to collapse
I advise you flash it with Heimdall.
rslee said:
No CwM yet, right?
Click to expand...
Click to collapse
We have CwM 3.0.0.5 !
Regards,
Humberto.
Hello
HumberOs
Friend looks Gingerbread need to install on my Tab P1000N
I have installed your rom and your zImage_ltn_20110612 Kernel Could you please help me
I need to return to stock Froyo to install Gigerbread ...?
My Tools Froyo stock return are: dbdata.rfs, P1000NUBJM2_P1000NUBJM2_P1000NUUBJM2_HOME.tar, and Odin P1_add_hidden.pit 1.7.
Gingerbread and ascend to the tools and files are the same except that the rom is the P1000NUBJP7_P1000NUBJP3_P1000NUUBJP7_HOME.tar and then would use your kernel ltn_cfroot_r1.tar Flashing
Please I need help with this could you tell me if I'm missing something about this or change something in the procedure ..?
HumberOs you do not have much time to explain everything and there are probably many more like me asking you for help but you'd be infinitely grateful if you give me a hand to have gingerbread on my tab
Thank you very much
Greetings from Ecuador
PS: I'm using Google translator for my language is Spanish
santroph said:
Our bootloaders are signed and apparently locked with this rom, do you think it is safe to use the apk to unlock them and than use Overcome?
Click to expand...
Click to collapse
The bootloaders are signed, but not secured.
Custom kernels and firmwares can still be flashed.
Do you flashed a custom Gingerbread kernel? So I think if you replace Overcome kernel...
Regards,
Humberto.
scalamusical said:
Hello alroger
So I must first pass a Gingerbread Froyo ...?
I can do it directly from the ROM HumberOs or need to return to the Rom of bone stock original Samsung firmware ...?
Thank you very much for your time and help
Greetings from Ecuador
Click to expand...
Click to collapse
I suggest you read and understand the other thread from HumberOS and follow post 314 with Humberto's little procedure for flashing Gingerbread and a few tips on postes following that one.
That means, return to stock Froyo ROM (2.2), wiping everything, before flashing stock Gingerbread ROM (2.3).
imgRePacker
LiveSuit's & PhoenixSuit's (Allwinner) firmware images (*.img) unpacker/packer
Version 2.07 Windows & Linux
Supported firmware images (known):
- Sochip SC8600/SC9800 (LiveSuit/zdisk);
- Boxchip F10/F15/F16/F20 (LiveSuit/zdisk);
- Teclast T7200/T8100 (LiveSuit/zdisk);
- Allwinner F10/F13/F18 (LiveSuit/zdisk);
- Allwinner F1C100/F1E200 (LiveSuit);
- Allwinner A10/A13/A10s (LiveSuit);
- Allwinner A20/A31/A31s (PhoenixSuit);
- Allwinner A80 (PhoenixSuit).
Supported second layer file formats:
- Android boot image;
- gzip/cpio archive file;
- cpio_ascii_new archive file;
- sparse image (unpacking).
Old versions:
View attachment 1389477 (19942)
View attachment imgRePacker_202.zip (7443)
View attachment imgRePacker_203.zip (4553)
View attachment imgRePacker_204.zip (18205)
View attachment imgRePacker_205.zip (39619)
View attachment imgRePacker_206.zip
Hi RedScorpio
Unfortunately with this version I can't obtain a proper ext4 iso file.
With an extract of ICS img rom (G18N from yinlips) (mirror here: http://dl.dropbox.com/u/67207175/ROMS/YDPG18.rar)
just a "data" type:
Code:
system.fex.iso: data
instead of:
Code:
system.fex.iso: Linux rev 1.0 ext4 filesystem data, UUID=630e3cc6-b026-4f2a-9f62-50b32a9f2ec8 (extents) (huge files)
Do you have idea of what happened ?
cis.snakeman said:
Code:
system.fex.iso: data
instead of:
Code:
system.fex.iso: Linux rev 1.0 ext4 filesystem data, UUID=630e3cc6-b026-4f2a-9f62-50b32a9f2ec8 (extents) (huge files)
Click to expand...
Click to collapse
These two strings are not the result of the work of any version of the program. Please describe the problem more precisely.
--
RedScorpioXDA said:
These two strings are not the result of the work of any version of the program. Please describe the problem more precisely.
Click to expand...
Click to collapse
Sorry for late answer, it was the "file" command on the iso files generated by imgRepacker. (especially system one)
In fact the iso files are not ext4 filesystem, in fact there is no filesystem defined :/
I'll try with the latest version this afternoon.
cis.snakeman said:
Sorry for late answer, it was the "file" command on the iso files generated by imgRepacker. (especially system one)
In fact the iso files are not ext4 filesystem, in fact there is no filesystem defined .
Click to expand...
Click to collapse
Actually, the program does not modify files in the firmware (saves them as-is). So inform me, in which case you got
Code:
system.fex.iso: Linux rev 1.0 ext4 filesystem data, UUID=630e3cc6-b026-4f2a-9f62-50b32a9f2ec8 (extents) (huge files)
RedScorpioXDA said:
Actually, the program does not modify files in the firmware (saves them as-is). So inform me, in which case you got
Code:
system.fex.iso: Linux rev 1.0 ext4 filesystem data, UUID=630e3cc6-b026-4f2a-9f62-50b32a9f2ec8 (extents) (huge files)
Click to expand...
Click to collapse
I have it with an iso extracted from an older version of the img I used. (one of Android 2.3)
The one wich causing these issue is an Android 4.0 one
This is the files from "YDPG18 Upgrade" android game handled console
http://www.yinlips.com/en/services/downs.aspx
cis.snakeman said:
I have it with an iso extracted from an older version of the img I used. (one of Android 2.3)
The one wich causing these issue is an Android 4.0 one
Click to expand...
Click to collapse
I think, this is a root case. Try to use simg2img for Android 4.0
RedScorpioXDA said:
imgRePacker
LiveSuit's firmware image (*.img) unpacker/packer
Version 2.01 Windows
Version 1.00 Linux
Click to expand...
Click to collapse
Hi
The IMG file for the ProTabXXLV2 here gives a corruption error when trying to unpack with imgRePacker. I know the file works in LiveSuit as I have flashed it a number of times.
Peter
ImgRepacker builds incorrect image
Help me please.
I use ImgRepacker 2.1 with Allwinner A10 ROM for chinese "noname" tablet with Android 4.0.3 ICS.
ImgRepacker unpacks ROM correctly but then repack ROM incorrectly.
I made an experiment.
I unpacked ROM and then repacked it without any changes.
Tablet doesn't boot with the re-assembled ROM.
I compared the old and the new ROMs. Both files are the same size but they contain 81 differences. These differences are:
1) One big block from offset 0050 to 03FF (944 bytes)
2) 40 blocks of 48 bytes. The 1st of these blocks begins at offset 0430 and the others repeated every 1024 bytes.
3) 40 blocks of 720 bytes. The 1st of these blocks begins at offset 0530 and the others repeated every 1024 bytes.
Is there *english* doc to this tool? And what do I do with all these .fex files? Or the .fex.iso ones?
whiskerp said:
The IMG file for the ProTabXXLV2 here gives a corruption error when trying to unpack with imgRePacker. I know the file works in LiveSuit as I have flashed it a number of times.
Click to expand...
Click to collapse
This is the result of improper packaging firmware. In the next versions of the program will be key to disable the checking size of the firmware. The new version is being tested and will be published in the near future.
booroondook said:
I compared the old and the new ROMs. Both files are the same size but they contain 81 differences. These differences are:
1) One big block from offset 0050 to 03FF (944 bytes)
2) 40 blocks of 48 bytes. The 1st of these blocks begins at offset 0430 and the others repeated every 1024 bytes.
3) 40 blocks of 720 bytes. The 1st of these blocks begins at offset 0530 and the others repeated every 1024 bytes.
Click to expand...
Click to collapse
These blocks belong to the titles of files and is unlikely to affect the flashing crash. If the new firmware can unpack, look for the problem in a different place.
booroondook said:
I use ImgRepacker 2.1 with Allwinner A10 ROM for chinese "noname" tablet with Android 4.0.3 ICS.
ImgRepacker unpacks ROM correctly but then repack ROM incorrectly.
I made an experiment.
I unpacked ROM and then repacked it without any changes.
Tablet doesn't boot with the re-assembled ROM.
Click to expand...
Click to collapse
Please provide links to both firmware images
RedScorpioXDA said:
I think, this is a root case. Try to use simg2img for Android 4.0
Click to expand...
Click to collapse
Thanks for the tip, I'll try with it. I think I can find it on xda isn 't it?
Envoyé depuis mon Legend avec Tapatalk
imgRePacker
LiveSuit's firmware image (*.img) unpacker/packer
New version (2.02 Windows & Linux) ready
RedScorpioXDA said:
imgRePacker
LiveSuit's firmware image (*.img) unpacker/packer
New version (2.02 Windows & Linux) ready
Click to expand...
Click to collapse
hi i am trying to unpack the latest firmware image for my Sanei N10 and when i select the .img file it gives me a ''cant open file''
let me know if you need anymore info...
ataxy said:
i select the .img file
Click to expand...
Click to collapse
What you mean? It is a command-line tool and doesn't need actions to select
Unknown format of image
Hi from Spain, RedScorpio.
The last img file of a Onda V972 (new Allwinner a31 chipset) say: Unknown format of image.
What can I do, please?
Thks.
Link of a img file
Here the img file:
https://docs.google.com/file/d/0ByYBry_nzDODbzJOY1EyR0JGSHc/edit
Hi guys! My great mate and friend @edzamber has made a collection of all KitKat Stock Kernel and has made them available for all us! So, all credits go to him!
The Kernel is a computer program that manages input/output requests from software and translates them into data processing instructions for the central processing unit known also as CPU. The Kernel acts as an intermediary between the software and the hardware.
Neither @edzamber nor I are responsible of any damages caused by your mistakes. Perform the procedure at your own risk!
No mirrors please
Requirements:
- A PC using Windows.
- Samsung driver --> HERE.
- Odin 3.07 or Odin 3.09 or Odin 3.10.
You have always to flash a Kernel matched to your ROM version. For example, if your ROM is GNG8, you have to flash the Kernel_Stock_GNG8.tar.md5 file. Otherwise your Wi-Fi will not work. If you flash a Stock Kernel on a Custom ROM, your Wi-Fi will not work because there aren't the stock modules in /system partition. You will need to download the firmware matched to the Kernel version, extract stock modules from system.img.ext4 using the kitchen and then put them in /system partition setting right permissions. Some stock modules are available HERE.
Let's start!
1) Download Stock Kernel from HERE.
2) Run Odin on your PC.
3) Reboot your device into download mode.
4) Put the Kernel in PDA/AP.
5) Put the tick only on "Autoreboot" and "F. Reset Time".
6) Click on "Start" to flash the Kernel.
7) Flash Stock Modules via recovery custom if you have one. Otherwise put manually them in /system partition using a file manager.
8) Reboot and enjoy!
Contributors:
@peppe130
@edzamber
Original thread: Phonandroid.com
Reserved..
Reserved..
Thanks my friend
Posté via Pyrana v44 by Alan-B
http://forum.xda-developers.com/showthread.php?p=53646684
Kernel GNH7 Updated
http://www.mediafire.com/?613y0yvomsvghuo
Posté via Pyrana v44 by Alan-B
http://forum.xda-developers.com/showthread.php?p=53646684
Kernel Stock GNH8 Updated
http://www.mediafire.com/?fi3r2i9ad6c77zc
Posté via Pyrana v46 by Alan-B
http://forum.xda-developers.com/showthread.php?p=53646684
GNH7 & GNH8 Kernels uploaded on Google Drive. A special thanks to @edzamber !
Thanks peppe, you're welcome my friend
Posté via Pyrana v46 by Alan-B
http://forum.xda-developers.com/showthread.php?p=53646684
Added GNH7 stock modules
Added GNH8 stock modules
Added GNH2 Stock Kernel.
Added GNH2 Stock Modules.
Thanks for your Support..
The Stock kernel download link is not working. please provide me other link???
harrisnehal said:
Thanks for your Support..
The Stock kernel download link is not working. please provide me other link???
Click to expand...
Click to collapse
Link works for me.. Try again
Added GNH6 Stock Kernel.
Thanks to @edzamber
Here is XXUGNI2 kernel
http://www.mediafire.com/?me9siwmennjd599
Here are XXUGNI2 Modem and BL :
http://www.mediafire.com/?ssu97teh42taeke
http://www.mediafire.com/?1nv77y9m6hhln96
Enjoy
Added XXUGNI2 Stock Kernel.
Thanks to @edzamber
edzamber said:
Here is XXUGNI2 kernel
http://www.mediafire.com/?me9siwmennjd599
Enjoy
Click to expand...
Click to collapse
Could you - by any chance - also provide the wifi modules?
/system/lib/modules
dhd.ko
scsi_wait_scan.ko
Downloading the image would me 15 hours
daniello8 said:
Could you - by any chance - also provide the wifi modules?
/system/lib/modules
dhd.ko
scsi_wait_scan.ko
Downloading the image would me 15 hours
Click to expand...
Click to collapse
Ok don't worry.. Just the time to download the firmware and upload modules
peppe130 said:
Ok don't worry.. Just the time to download the firmware and upload modules
Click to expand...
Click to collapse
Thanks .. I believe edzamber already has the image .. thought it would only take him a minute.
But any help is appreciated
Greetings guys!
This is another firmware for Xperia Z1 (C6903), and so far is been released in just few countries. I make it pre rooted as by my side once you have a pre rooted firmware you can be able to manage and delete apps what you don`t need to free space in your mobile.
P.S. So far i see same threads but for Z1 Compact and Z Ultra. (if mods believe is not good this thread to exist i don`t mind if it will be deleted)
What do you need:
- Flashable zip
- Mobile phone Xperia Z1 (C6903) - with CWM/TWRP to can flash the zip
- USB Cable (make sure your battery is over 75%)
- Attention and patience
The procedure to flash the zip is the same like in other threads (copy the zip to your external SD Card and from there reboot your phone to CWM/TWRP and select - install zip)
The content of zip is
- firmware C6903_14.5.A.0.238_Greece-Cosmote.ftf (i found with XperiFirm on thread wrote by @IaguCool so of course credits go to him)
- UPDATE-SuperSU-v2.46 credits go to @Chainfire
- Z1-lockeddualrecovery2.8.21-RELEASE.flashable credits to @[NUT]
I used PRF Creator to make this zip flashable, credits go to @zxz0O0
The steps i follow to reach a Lollipop 5.0.2 Pre Rooted firmware i found them here http://techbeasts.com/2015/04/14/root-xperia-z1-c6902c6903-14-5-a-0-242-5-0-2-lollipop-with-dual-recovery/
If you have done before flash with dual recovery you may skip the last link, but if it is your first time when you try to do this i highly recommend you to read before each thread including the one on last link.
Disclaimer
- i am not responsible if you run into a bootloop or you damage your mobile. Do it if you know what you do, if not just give up!
Download file
https://mega.nz/#!KY5ilDrY!F_GyaK2tWmZ8GXKRT_ChRvakkT22kCWhGGDc-ZOOpic
lastest release is 14.6.A.0.368, android 5.1.1. Did you choose wrong firmware to creat or wrong tittle of this thread?
hxq88 said:
lastest release is 14.6.A.0.368, android 5.1.1. Did you choose wrong firmware to creat or wrong tittle of this thread?
Click to expand...
Click to collapse
you have right, i check it now and is there also for few countries, i will download it and i will try to make pre rootabe, if i succeed i will upload here, but for now i want to upload as well 238 as i don`t see a thread about it, and so far i was happy with it! Thanks for let me know is out new firmware!
I'm using .270 now. Should I install this(14.5.A.0.283 ) first before I install 14.6.A.0.368 ?
ferbuffer said:
I'm using .270 now. Should I install this(14.5.A.0.283 ) first before I install 14.6.A.0.368 ?
Click to expand...
Click to collapse
No need, you could flash right away 368, just make sure you backup your actual ROM and update your dualrecovery
Sent from my C6903 using XDA Free mobile app
[STOCK][RMX1971EX][RMX1971]Firmware, Boot, Recovery, VBmeta & TWRP[RMX1971EX][STOCK]
Hai guys.
Here I collect and share Stock Firmware, Boot, Recovery, Vbmeta and TWRP. If you have other versions and links, just let me know, so I can update the list below.
#FIRMWARE
Realme 5 Pro - All Global Region ID, IN, EU, RU, etc it's same EXCEPT Realme Q
RUI Firmware (Android 10)
RMX1971EX_RealmeUI-11_C.11 - Official Firmware (Stock Recovery & TWRP) = Link
Update Log
**Security**:
● Updated Android security patch: December, 2020, January, 2021
**Settings**:
● Added short-press the power button to turn off flashlight feature while screen-off
**Apps**:
● Fixed the issue that two cancel buttons appear when the input box is clicked multiple times in the weather
● Fixed the issue of abnormal system permission acquisition when the radio is turned on
**Bluetooth**:
● Fixed the probabilistic issue of failure to open Bluetooth scanning
**Photos**:
● Fixed the probabilistic issue that Photos cannot play HDR videos
**Alarm**:
● Fixed the probabilistic issue of crashing when entering the alarm details
**Networks**:
● Fixed the probabilistic issue that VOLTE be registered
Click to expand...
Click to collapse
RMX1971EX_RealmeUI-11_C.08 - Official Firmware (Stock Recovery & TWRP) = Link & Custom Firmware C.08 (TWRP Only) = Link
Update Log
Security
● Android Security Patch: November, 2020
Bluetooth
● Added a new icon for phone calls with Bluetooth earphone
Screenshot
● Added Scrolling screenshot feature in horizontal mode
● Added a toggle for physical button screenshot in screenshot settings
Settings
● Added Super power saving mode
● Added a toggle for displaying keyboard when entering app drawer
● Added Icon pull-down gesture
● Added From Sunset to Sunrise option of eye comfort
● Added shortcuts at the bottom of Battery settings
● Added shortcuts at the bottom of Security settings
● Fixed the probabilistic issue of unable to adjust the color temperature after turning off eye comfort
Album
● Fixed the probabilistic screen flicker when entering the album
● Fixed the probabilistic crash issue when browsing in the album
System
● Fixed the probabilistic freezing issue of Clone Phone
Click to expand...
Click to collapse
RMX1971EX_RealmeUI-11_C.07 - Official Firmware (Stock Recovery & TWRP) = Link
RMX1971EX_RealmeUI-11_C.07 - Custom Firmware (TWRP Only) = Link
Update Log
https://otafsg.realmemobile.com/htm...C.07_1070_202009181810/en-US_6fdf42c_5_0.html
Click to expand...
Click to collapse
RMX1971EX_RealmeUI-11_C.06 - Custom Firmware (TWRP Only) = Link
Update Log
https://otafsg.realmemobile.com/htm..._1060_202008061205/en-US_e5421126f2f_6_0.html
Click to expand...
Click to collapse
RMX1971EX_RealmeUI-11_C.05 - Official Firmware (Stock Recovery & TWRP) = Link
RMX1971EX_RealmeUI-11_C.05 - Custom Firmware (TWRP Only) = Link
Update Log
https://otafsg.realmemobile.com/htm...1.C.05_1050_202007271919/en-US_8292f_5_0.html
Click to expand...
Click to collapse
RMX1971EX_RealmeUI-11_C.04 - Official Firmware (Stock Recovery & TWRP) = Link
RMX1971EX_RealmeUI-11_C.04 - Custom Firmware (TWRP Only) = Link
RMX1971EX_RealmeUI-11_C.03 - Official Firmware (Stock Recovery & TWRP) = Link
RMX1971EX_RealmeUI-11_C.03 - Custom Firmware (TWRP Only) = Link
RMX1971EX_RealmeUI-11_C.02 - Official Firmware (Stock Recovery & TWRP Support) = Link
RMX1971EX_RealmeUI-C.02 - Custom Firmware (TWRP Only) = Link
RMX1971EX_RealmeUI-11_C.01 - Official Firmware (Stock Recovery & TWRP Support) = Link
RMX1971EX_RealmeUI-11_C.01 - Custom Firmware (TWRP Only) = Link
COS Firmware (Android 9)
RMX1971EX_11_A.17 = Link
RMX1971EX_11_A.16 = Link
RMX1971EX_11_A.15 = Link
RMX1971EX_11_A.13 = Link
RMX1971EX_11_A.11 = Link
RMX1971EX_11_A.09 - OTA = Link
Realme Q (Cina)
RMX1971_C.11-Realme-UI (Stock Recovery & TWRP) = Link
Update Log
https://otaafs-cost.coloros.com/RMX...1110_202012252020/en-US_062897d50278_5_0.html
Click to expand...
Click to collapse
RMX1971_C.10-Realme-UI (Custom Firmware - TWRP Only) = Link
Update Log
https://otaafs-cost.coloros.com/RMX...100_202012141234/en-US_4afe06912eb4e_5_0.html
Click to expand...
Click to collapse
RMX1971_C.08-Realme-UI (Stock Recovery & TWRP) = Link & Customer Firmware C.08 (TWRP Only) = Link
Update Log
Screenshot
● Added the function of horizontal and long screenshots
● Added physical key switch on the screenshot setting page
Set up
● Added super power saving mode to improve system endurance
● Added a switch to enter the drawer pop-up input method
● Added icon sinking function
● Added a switch to enable eye protection mode from sunset to sunrise
● Added quick guide function at the bottom of the battery
● Added a quick guide function at the bottom of Do Not Disturb
● Added safe bottom shortcut guide function
● Fix the problem of low probability of failure of color temperature adjustment after removing the eye protection mode
Photo album
● New album creation function, you can jump to the recording APP editing creation
● Fix the issue of extremely low probability of splash screen when entering the album
● Fix the problem of low probability of crash when browsing albums
system
● Fix the problem of low probability of mobile phone being stuck during multiple moves
Safety
● Update Android security patch (2020#10)
Click to expand...
Click to collapse
RMX1971_C.07-Realme-UI = Link
Update Log
https://otafs.coloros.com/html/CHN/RMX1971/RMX1971_11.C.07_1070_202009101846/en-US_ded75cb_5_0.html
Click to expand...
Click to collapse
RMX1971_C.06-Realme-UI = Link
Update Log
https://forum.xda-developers.com/showpost.php?p=83142357&postcount=291
Click to expand...
Click to collapse
RMX1971_C.05-Realme-UI = Link
RMX1971_C.04-Realme-UI = Link
RMX1971_C.03-Realme-UI = Link
RMX1971_C.02-Realme-UI = Link
RMX1971_C.01-Realme-UI-Beta = Link
RMX1971_11.A.12 = Link
RMX1971_11.A.11 = Link
RMX1971_11.A.10 = Link
RMX1971_11.A.09 = Link
Realme 5 Pro RMX1971EX NOT Recommended for Realme Q
#Stock Boot
RMX1971EX_11_C.08-RUI = Link or Flashable Zip Link
RMX1971EX_11_C.04-RUI = Link or Flashable Zip Link
RMX1971EX_11_C.03-RUI = Link or Flashable Zip Link
RMX1971EX_11_C.02-RUI = Link
RMX1971EX_11_C.01-RUI = Link
RMX1971EX_11_A.17 = Link or Flashable Zip Link
RMX1971EX_11_A.16 = Link
RMX1971EX_11_A.15 = Link
RMX1971EX_11_A.13 = Link
RMX1971EX_11_A.11 = Link
#Stock Recovery
RMX1971EX_11_C.08-RUI = LINK
RMX1971EX_11_C.04-RUI = LINK
RMX1971EX_11_C.03-RUI = LINK
RMX1971EX_11_C.02-RUI = Link
RMX1971EX_11_C.01-RUI = Link
RMX1971EX_11_A.17 = Link
RMX1971EX_11_A.16 = Link
RMX1971EX_11_A.15 = Link
RMX1971EX_11_A.13 = Link
RMX1971EX_11_A.11 = Link
#Stock Vendor
Stock VENDOR - RUI - C.04 = Link
Stock VENDOR - RUI - C.03 = Link
Stock VENDOR - RUI - C.02 = Link
Stock VENDOR - COS - A.17 = Link
How to Install : Just Flash File Stock Vendor on TWRP.
#Downgrade Firmware
● New Method (Official - Only support versions after C.04 and Lock Bootloader)
Downgrade Firmware RUI to COS A.20 = Link
● Old Method (UnOfficial - Support All RUI Firmware versions and Only Unlock Bootloader)
This file is only used to downgrade the device firmware from RUI to COS before installing the Custom Kernel / Custom Rom base Android 9 (PIE).
This file not Include System Image, so after flash it you can't boot to home screen COS A.17. You need full .Ozip Firmware to booting COS.
Downgrade Firmware RUI to COS A.17 = Link
File Downgrade Include :
- Stock Vendor A.17.
- Vbmeta with Disable Verifycation & Dm Verity.
- Orange Fox TWRP.
How to Install :
- Wipe Dalvik, Cache, Data, System (Recommended Clean Flash).
- Flash File Stock Vendor on TWRP.
- Reboot Recovery / TWRP again before Flash Something or Custom Rom.
#Vbmeta - All Global Region Firmware its same
Vbmeta - Disable Boot Verification & DM-Verity (TWRP) = Link
Vbmeta Stock - C.04 - RUI = Link
Vbmeta Stock - C.03 - RUI = Link
Vbmeta Stock - C.02 - RUI = Link
Vbmeta Stock - C.01 - RUI = Link
Vbmeta Stock - A.17 = Link
#TWRP
TWRP OrangeFox Official R11 by @pjgowtham 2020-07-30 - STABLE = Link
TWRP 3.3.2B Realme Q (China) Link
TWRP PitchBack Recovery v2.9.1 - Beta by @BabluS 2020-07-02 Link
TWRP OrangeFox by @yog12 2020-03-16- BETA = Link
TWRP SHRP 2.2 (Skyhawk) by @yog12 2020-03-20 = Link
TWRP by @BabluS 2020-02-28 = Link
TWRP by @sprinter 2019-11-21 = Link
#Indeep Test Apk - UBL COS & RUI
InDeep Test APK - Color OS 7 (RUI) = Link
InDeep Test APK - Color OS 6 (COS) = Link
Guide UBL
● Color OS 7 - RUI
● Color OS 6 - COS
Click to expand...
Click to collapse
Note : Someone user Confirm Device Region EU NOW support UBL on RUI.
Note: I assume everyone already knows how to Install Stock Firmware or Flash Stock Boot, Recovery & Vbmeta...Don't try Flashing Cross Region / Country unless someone has confirmed it.
If Help you, Don't forget Click Thank's :good:
@credit : Group Telegram R5P_indonesia
@Thanks to Tmv_Josue for Corrections about Firmware and Vbmeta
@Thanks to telco2016 for New Method Downgrade
Requesting Steps to flash
Can u please post steps to flash them?
Thanks
Or any link that guides
Thanks
BhalaBadra said:
Can u please post steps to flash them?
Thanks
Or any link that guides
Thanks
Click to expand...
Click to collapse
Firmware you need stock recovery, Download File Firmware and save file on Internal Storage, just TAP the File on Stock File Manager, follow instruction and wait progress finish or boot to stock recovery from bootloader chose Install from storage devices anda browse file firmware .ozip anda wait to finish progress.
Stock Boot, Recovery & Vbmeta just Boot Handphone to Bootloader and Flash via Fastboot with command
Code:
fastboot.exe flash boot [Path File]/Stock-Boot-RMX1971EX_11_A.13.img
fastboot.exe flash recovery [Path File]/Stock-RecoveryRMX1971EX_11_A.13.img
fastboot.exe flash vbmeta [Path File]/Stock-vbmeta-RMX1971EX_11_A.13.img
@faisalxp.
The Vbmetas from all Realme 5 pro and Q's ColorOS OZIPS are the same, them don't change, so you could link only one VBmeta for all of them, see attachment.
Something that I don't know is how obtain the recovery.img and the system.img, do you know how?
Tmv_Josue said:
@faisalxp.
The Vbmetas from all Realme 5 pro and Q's ColorOS OZIPS are the same, them don't change, so you could link only one VBmeta for all of them, see attachment.
Something that I don't know is how obtain the recovery.img and the system.img, do you know how?
Click to expand...
Click to collapse
Stock Boot, Recovery and Vbmeta just for Realme 5 Pro and i don't know if the MD5 and SHA1 Hash test results are the same, maybe the contents are different. I just took it from My Phone after Install Update Firmware.
recovery.img and system.img u can take from backup twrp just rename it from recovery.emmc.win to recovery.img same system_image.emmc.win to system_image.img
NEW:
The Realme EU support page now list the Realme 5 Pro, it is the same FW than the IN support page since it also has the same MD5:
https://www.realme.com/eu/support/software-update
faisalxp said:
recovery.img and system.img u can take from backup twrp just rename it from recovery.emmc.win to recovery.img same system_image.emmc.win to system_image.img
Click to expand...
Click to collapse
I did not know that the emmc.win files that TWRP backup are an IMGs, thanks for the info.
faisalxp said:
Stock Boot, Recovery and Vbmeta just for Realme 5 Pro and i don't know if the MD5 and SHA1 Hash test results are the same, maybe the contents are different. I just took it from My Phone after Install Update Firmware.
Click to expand...
Click to collapse
Ok, you are right, my mistake was looking in the directly extracted VBmetas from stock Ozips, now, having read you I understand that the VBmetas 7zip extracts from the Ozips are maybe the base for them, not the complete ones. I need to make more analysis but seems to be that the VBmetas from the different Realme Q FW versions are the same and the ones from the R5pro are the same for it too. So, maybe are the same for variant versions but diferent between Q and R5pro.
One thing is sure, the two VBmetas that you linked in OP are exactly the same, bit-identical, so it is not necessary to link both.
Another thing is that the FW for the Indonesian, India, Europe, and Rusia's Realme 5 Pros you linked are the same so maybe it would be a best practice to mention all of them with only one download link to not give users a false idea that they are different.
I bought my phone in India so I presume that it is indian variant. First installed TWRP and LOS and everything was ok. Then tried with magisk but got ERROR 1 cannot mount system. So I taught that maybe flashing the latest firmware will change something. So I flashed firmware. And brick. I attach photos. Please kindly help me
https://www.photobox.co.uk/my/photo?photo_id=502381335672&album_id=5753911027
https://www.photobox.co.uk/my/photo?album_id=5753911027&photo_id=502381334149
https://www.photobox.co.uk/my/photo?photo_id=502381334736&album_id=5753911027
Tmv_Josue said:
I did not know that the emmc.win files that TWRP backup are an IMGs, thanks for the info.
Ok, you are right, my mistake was looking in the directly extracted VBmetas from stock Ozips, now, having read you I understand that the VBmetas 7zip extracts from the Ozips are maybe the base for them, not the complete ones. I need to make more analysis but seems to be that the VBmetas from the different Realme Q FW versions are the same and the ones from the R5pro are the same for it too. So, maybe are the same between variant versions but diferent between Q and R5pro.
One thing is sure, the two VBmetas that you linked in OP are exactly the same, bit-identical, so it is not necessary to link both.
Another thing is that the FW for the Indonesian, India, Europe, and Rusia's Realme 5 Pros you linked are the same so maybe it would be a best practice to mention all of them with only one download link to not give users a false idea that they are different.
Click to expand...
Click to collapse
If fw is the same for all of rm5p devices by region then why is that only Europe version supports B3, B7 and B20 lte bands? It means either vendor or vendor + modem.img differ somehow from other rm5p regional firmware like India or Indonesia.
Madhuvrata said:
I bought my phone in India so I presume that it is indian variant. First installed TWRP and LOS and everything was ok. Then tried with magisk but got ERROR 1 cannot mount system. So I taught that maybe flashing the latest firmware will change something. So I flashed firmware. And brick. I attach photos. Please kindly help me
https://www.photobox.co.uk/my/photo?photo_id=502381335672&album_id=5753911027
https://www.photobox.co.uk/my/photo?album_id=5753911027&photo_id=502381334149
https://www.photobox.co.uk/my/photo?photo_id=502381334736&album_id=5753911027
Click to expand...
Click to collapse
Sory for late replay. Maybe your phone now is Fine.
About your attachment i cant view it, must register so i answer you question base on explaination.
About Error on Flash Magisk because Partition System On Tick in Menu Mount, so you need to make sure untick it before Install Magisk.
About Brick, make sure you flash vbmeta before flash TWRP or Before install Magisk. if not doing it you cant get info Bootdestroy after reboot.
Command Flash
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you now on Brick, try flash Stock Recovery and install Stock Firmware on it or you can flash Latest TWRP with support Flash .OZIP (File Stock Firmware). If not Work try Factory Reset / WIPE DATA.
greenys' said:
If fw is the same for all of rm5p devices by region then why is that only Europe version supports B3, B7 and B20 lte bands? It means either vendor or vendor + modem.img differ somehow from other rm5p regional firmware like India or Indonesia.
Click to expand...
Click to collapse
Thanks for help Explaination
Tmv_Josue said:
I did not know that the emmc.win files that TWRP backup are an IMGs, thanks for the info.
Ok, you are right, my mistake was looking in the directly extracted VBmetas from stock Ozips, now, having read you I understand that the VBmetas 7zip extracts from the Ozips are maybe the base for them, not the complete ones. I need to make more analysis but seems to be that the VBmetas from the different Realme Q FW versions are the same and the ones from the R5pro are the same for it too. So, maybe are the same for variant versions but diferent between Q and R5pro.
One thing is sure, the two VBmetas that you linked in OP are exactly the same, bit-identical, so it is not necessary to link both.
Another thing is that the FW for the Indonesian, India, Europe, and Rusia's Realme 5 Pros you linked are the same so maybe it would be a best practice to mention all of them with only one download link to not give users a false idea that they are different.
Click to expand...
Click to collapse
Sory for late Replay.
About Vbmeta, thanks for info coz idk if that same version, i thinks different build firmware will make different vbmeta to because i just backup it after upgrade firmware, so thanks for suggestion but i still make different link and version, maybe can usefully for some member.
About Same Firmware on different Region, i thinks thats not true, because different country / region have different driver and config hardware and same with software to. So i think better performace and experience on realme 5 pro must install firmware each country / region.
Is it necessary to wipe data (include system, vendor, cache, data in twrp) before flashing ozip in twrp and flashing an .img file (system, boot, recovery, vbmeta) separately on the bootloader?
Because now I'm in custom rom, and i don't want to brick my device if i want go back to stock.
If you just need not brick and want to backup data / app just flash it but maybe its not clean and probably can brick or unstable system. I Recommend and for best result you must wipe all system, vendor, cache, boot and recovery before flash it.
Why file ozip not appear on stock recovery?
try use latest recovery Unofficial-TWRP-20191121.img
Is there any global version stock rom that can support realme Q and flash through the recovery itself? I really want to get rid of this Chinese rom [Noobie]
If my Rm5P's bootloader is unlocked and TWRP is installed,can I flash ROMs and other zips using this TWRP instead of Fastboot?
Nikhilesh23 said:
Is there any global version stock rom that can support realme Q and flash through the recovery itself? I really want to get rid of this Chinese rom [Noobie]
Click to expand...
Click to collapse
.
No, because the partition size is different and there may be different hardware and software configurations that don't support Realme Q ... I suggest you use Custom ROM, although there are still some bugs.
pnsdhrn said:
If my Rm5P's bootloader is unlocked and TWRP is installed,can I flash ROMs and other zips using this TWRP instead of Fastboot?
Click to expand...
Click to collapse
Yes of course, i recomended backup first before try install something.
Yes of course said:
Thank you very much,faisalxp.
Click to expand...
Click to collapse