Related
Hi,
So i just got a new nexus one, unlocked and it had Android version 2.3.3, it has cyanogen Mod 7.0 installed and the kernel Version is 2.6.37cyanogenmod... and the baseband version is 32.41.00.32U....
I was wondering if it is possible to update to the 2.3.4? If possible than how?
Thanks inadvace
yes, install the newest nightly
Nightly 61 and any nightly after that is 2.3.4
Go here and download the ROM you want http://download.cyanogenmod.com/?type=nightly&device=passion
Go here for latest GAPPS file (20110507) http://forum.xda-developers.com/showpost.php?p=13551248&postcount=1972
1-Save files to your SD card
2-boot into recovery
3-chose "flash zip from sd card"
4-navigate to where you have the file save and chose the file to flash
5-repeat step 3 if you want to flash the latest GAPPS file
6- reboot
Also what is the # after 32.41.00.32U_ for your baseband? The number indicate your radio version
Note: With this zip file you can flash s219 build directly with SP flash tool no need to flash lollipop rom
Flashing Procedure :
Download the file given at the bottom of the post.
Extract the zip file with any software.
Install all drivers,If u already installed before then leave this step.
Go To MTK_Koleos_flashtool_v5.1536.00.000 Folder and open flash_tool.
Now you will be asked for the scatter file.
Browse the folder to which you have extracted the downloaded zip.
And then go to SW folder and open target_bin folder.
You will find a text file named MT6753_Android_scatter click on it.
Then it takes some time for loading the scatter file.
After that click on download button and connect your device to pc after shutting it down.
The Process will be started and after flashing you will be directly in the S219 Marshmallow Build.
DOWNLOAD LINKS HERE :fingers-crossed::fingers-crossed:
Video Tutorial : https://www.youtube.com/watch?v=0qIU863_PaU
Visit the site : www.atozhacks.blogspot.com
Vijay chandra said:
Note: With this zip file you can flash s219 build directly with SP flash tool no need to flash lollipop rom
Flashing Procedure :
Download the file given at the bottom of the post.
Extract the zip file with any software.
Install all drivers,If u already installed before then leave this step.
Go To MTK_Koleos_flashtool_v5.1536.00.000 Folder and open flash_tool.
Now you will be asked for the scatter file.
Browse the folder to which you have extracted the downloaded zip.
And then go to SW folder and open target_bin folder.
You will find a text file named MT6753_Android_scatter click on it.
Then it takes some time for loading the scatter file.
After that click on download button and connect your device to pc after shutting it down.
The Process will be started and after flashing you will be directly in the S219 Marshmallow Build.
DOWNLOAD LINKS HERE :fingers-crossed::fingers-crossed:
Visit the site : www.atozhacks.blogspot.com
Click to expand...
Click to collapse
this will be very helpfull ..Thankyou
hirencj said:
this will be very helpfull ..Thankyou
Click to expand...
Click to collapse
if u support my work click some adds on my site
Vijay chandra said:
if u support my work click some adds on my site
Click to expand...
Click to collapse
Yeah sure bro..
@Vijay chandra Could you tell me how to retain my personal data n app data while flashing your ROW s219 update. Currently I am on s219 with TWRP 3.0.2 rooted with SuperSU PseudoPro version 2.78 systemless.
Kessang said:
@Vijay chandra Could you tell me how to retain my personal data n app data while flashing your ROW s219 update. Currently I am on s219 with TWRP 3.0.2 rooted with SuperSU PseudoPro version 2.78 systemless.
Click to expand...
Click to collapse
backup data in TWRP ,after flashing this restore that
I was given a link. cronociclope Senior Member
I tested it. 100 for 100 on :cyclops:
It is necessary to return or to be emu 4. (MM).
Have the unlock code. (Bootloader).
Have downloaded the full firmware (2 files) Full-ota-mf-pv that twrp can install.
And have downloaded the firmware update, full full-ota-mf (no pv). (3 files).
pc+ winzip+ twrp (chinois), carteSD,
regard
https://www.youtube.com/watch?v=oTBvz71l4s0&t=1s
So on the pc, with winzip. Because with winrar for me it does not want to transfer large volumes. :
_ Downloaded a firmware emui 5. Full-ota-mf-pv for your device (it's a firmware in two files, which twrp for MM can install).
_______ update.zip and datafull hw-eu.zip
Uploaded emui update 5. Full-ota-mf not written pv and that does not share ota. But we want it. : (this is a firmware in three files).
________update.zip, public file and data hw-eu.zip
_ Open the update file of the pv version and delete the update.app, then open the update of the no pv version, and transfer update.app in the pv version.
Do the same thing with the datafull file hw-eu and data hw-eu.
In the public zip, there is a data folder with the product and system files.
In the zip data hw-eu, there is a data folder with the cust and version.
We can also transfer them.
In the zip data full hw-eu to data / hw_init :cyclops:
_copy your two new .zip files onto the SD card.
_start the phone in recovery twrp MM.
_ Go to wipe, advanced wipe, check all except well-sure sd card, and wipe to wipe.
_allez to install, installed both zip, it will show you two errors ignore them.
_allez to reboot, reboot system.
Hello
in the public zip, there is a data folder with the product and system files.
In the zip data hw-eu, there is a data folder with the cust and version.
We can also transfer them.
In the zip data full hw-eu to data / hw_init
regard
2017.09.20 VNS-L21C432B382 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97161/f1/full/update.zip
filelist http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97161/f1/full/filelist.xml
B383 was released on Firmware Finder.
Install the OTA one (mb version).
Johnny TDN said:
B383 was released on Firmware Finder.
Install the OTA one (mb version).
Click to expand...
Click to collapse
yes, full-ota-mf
2017.09.21 VNS-L21C432B383 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97303/f1/full/update.zip
filelist http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97303/f1/full/filelist.xml
and
your pkg install full-ota-mf-pv vns-l21c432b371
2017.03.21 VNS-L21C432B371 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v89798/f2/full/update.zip
filelist http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v89798/f2/full/filelist.xml
got an ota update b383.
failed at 32%
gg huawei
Johnny TDN said:
got an ota update b383.
failed at 32%
gg huawei
Click to expand...
Click to collapse
strange 32%
with this method, I can even install p10 lite.
can be checked, the update.app that is the good you place in the update.zip
go to wipe before installing update.zip edit this seems important.
2017.08.30 VNS-L31C432B390 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97199/f1/full/update.zip
filelist http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97199/f1/full/update.zip
If I am rooted and I have TWRP, can I install the update?
I installed update without come back in mm and without reset phone by this steps:
1)flash Hassan twrp recovery
2)download the 3 update file
3)extract update.app from update.zip and from update_full_VNS-L11_hw_eu.zip.
4)With Huawei update extractor extract the image file (system boot vendor cust version misc) from the two update.app and flash It with recovery. The product Image is not falshable, you have to extract this with ext4imageview
5)do a wipe cache and davilk and flash magisk zip to root. Install magisk manager (with the new update b391 i have some problem with supersu)
6)copy the file extract from product Image and data file extract from update_full_VNS-L11_hw_eu.zip and data_full_pubblic.zip in /data and in /product partition with solid Explorer with root permission.
Reboot
It's ok
http://oi63.tinypic.com/29cncx4.jpg
Paolo83 said:
I installed update without come back in mm and without reset phone by this steps:
1)flash Hassan twrp recovery
2)download the 3 update file
3)extract update.app from update.zip and from update_full_VNS-L11_hw_eu.zip.
4)With Huawei update extractor extract the image file (system boot vendor cust version) from the two update.app and flash It with recovery. The product Image is not falshable, you have to extract this with ext4imageview
5)do a wipe cache and davilk and flash magisk zip to root. Install magisk manager (with the new update b391 i have some problem with supersu)
6)copy the file extract from product Image and data file extract from update_full_VNS-L11_hw_eu.zip and data_full_pubblic.zip in /data and in /product partition with solid Explorer with root permission.
It's ok
Click to expand...
Click to collapse
Hello
Hello
ALSO Product.img of update.zip?
Because, he does not want, that's why, I always go to MM.
bad reading sorry,
Chisetdel31260 said:
Hello
ALSO Product?
Click to expand...
Click to collapse
We are not able ti flash product with this recovery, we can try to ask information to Hassan. The solution is to extract product.img with Android ICS JB EXT4 imagefile unpacker and copy the folder in /product with solid Explorer and root permission. It replace the file with the correct attribute. You have to use this metod to copy data folder
Paolo83 said:
We are not able ti flash product with this recovery, we can try to ask information to Hassan. The solution is to extract product.img with Android ICS JB EXT4 imagefile unpacker and copy the folder in /product with solid Explorer and root permission. It replace the file with the correct attribute. You have to use this metod to copy data folder
Click to expand...
Click to collapse
I've already asked him to hassan and he added to install twrp product image, but its not working.
I tried to copy pasted already with a file explorer, but every time, things break. (either with force close parameters, or force close camera, or boot-animation disappears and becomes android).
there is always something wrong.
Yes, we leave from MM everything is ok, clean.
You have to use solid Explorer It works!! With this procedure In five minutes I upgrade to last version
Managed to update to b382.
Seems stable and somehow, the battery is much better o^o
go
time to download, c432b390.
And to transfer everything in the b370 zip, then to go back to c432b160, I installed it correctly.
so this version is emu 5.0.1, patch September 1, version kernel 25 aug and baseband 286.
as you can see.
Updated to b382 vns-l21.
Problem : No notifications on Hangouts. I must go to my friend's chat in order to see the notification.
I have a question for @Chisetdel31260 or @Paolo83 or for whom I can answer it.
Is it still unclear if it is necessary or not the data_full public, which contains this .zip? And how can I add it without errors? Thanks to whoever can guide me :angel:
Doble_f said:
I have a question for @Chisetdel31260 or @Paolo83 or for whom I can answer it.
Is it still unclear if it is necessary or not the data_full public, which contains this .zip? And how can I add it without errors? Thanks to whoever can guide me :angel:
Click to expand...
Click to collapse
Hello
yes, I add it.
you just have to open the folder data / hw_init /
sorry,
for my bad English.
yet I do a great deal of effort.
for that google translator, does not blow up the planet.
Hi Chisetdel, I share this video, which includes the files OEMinfo.zip, Update.zip and Update_data_full.zip modified and ready to install via TWRP directly from EMUI 4.1 for the L21 (C432B382/EMUI 5.0.1) and L23 (C605B372/EMUI 5.0.1): here
Greetings
I recently bricked my EVA-AL00 from installing Magisk and I'm using Tecalote's post (https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389) to resolve it.
I downloaded the update zip file (first result on https://pro-teammt.ru/firmware-database/?firmware_model=eva-al00&firmware_page=0), extracted, then used the Extractor software to extract UPDATE.APP. However, the Extractor tool did not show either ramdisk.img or boot.img. Only files are: CURVER.img, EFI.img, PACKAGE_TYPE.img, SHA256RSA.img, VERLIST.img, VERSION.img, crc.img and cust.img.
Could someone please help me find the right file?
george.tian said:
I recently bricked my EVA-AL00 from installing Magisk and I'm using Tecalote's post (https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389) to resolve it.
I downloaded the update zip file (first result on https://pro-teammt.ru/firmware-database/?firmware_model=eva-al00&firmware_page=0), extracted, then used the Extractor software to extract UPDATE.APP. However, the Extractor tool did not show either ramdisk.img or boot.img. Only files are: CURVER.img, EFI.img, PACKAGE_TYPE.img, SHA256RSA.img, VERLIST.img, VERSION.img, crc.img and cust.img.
Could someone please help me find the right file?
Click to expand...
Click to collapse
It must be FullOTA-MF, not OTA-MF, you must first unzip update.zip and then open update.app by Huawei Update Extractor.
You can also download b540 FullOTA from Firmware Finder, see eg
https://forum.xda-developers.com/showpost.php?p=78511904&postcount=1261
IMO, would be better to obtain support if you asked through HWOTA7 thread
Anyway, on my Mega, there are various stock kernels, ramdisks, etc from b535, b539 and b540, including b540 ramdisk patched for Magisk v18.
I've been using it and several other users and it worked fine
https://mega.nz/#F!JwkVyRya!Rb7OUE0z3PEpXBRxGOM-vQ
However, if you recived OTA Patch02 for b540, you will need to patch/install Magisk by checking both Preserving Encryption and Preserving AVB - for b535, b539 and b540 before Patch02, Preserving AVB was not needed. (only Preserve Encryption)
I'm currently back on b535, but with OTA Patch02, you can find on my Mega also its patched ramdisk, but again, because of Patch02, it was needed now to check also Preserve AVB.
If you are already on b540 with Patch02, I"m not sure if its stock ramdisk is the same as for b540 before Patch02 (probably yes, because OTA Patch02 was only few MB)
You can also extract ramdisk from your currently installed firmware directly from Oreo TWRP, go to Advanced, Terminal and use the command
Code:
dd if=/dev/block/bootdevice/by-name/ramdisk of=/external_sd/ramdisk.img
Extracted ramdisk.img will be saved to external SD card.
You can do the same from TWRP also for kernel and system - however, not for data partition (since TWRP lacks support to read encrypted data partition)
Hey please I'm looking for boot _recovery_crc.img
Eteon x said:
Hey please I'm looking for boot _recovery_crc.img
Click to expand...
Click to collapse
Hi there,
Without information about which device you have (model number, Android version, build number, custom version) it is not possible to give you a suitable tip.
It would also be helpful to know why you need a specific image.
Up to Android 7 there was a boot.img and a recovery.img, as well as a recovery2.img.
From Android 8 on there was no longer a boot.img, but instead the ramdisk.img. And for the recovery the so-called recovery_ramdisk.img.
Both images are different for each firmware, which is why precise information is necessary. The images can be extracted from the Update.App.
To do this, the firmware suitable for the device must be downloaded.
A xxx.crc.img is meaningless because it's just a checksum and not an image to flash!
Tecalote said:
Hi there,
Without information about which device you have (model number, Android version, build number, custom version) it is not possible to give you a suitable tip.
It would also be helpful to know why you need a specific image.
Up to Android 7 there was a boot.img and a recovery.img, as well as a recovery2.img.
From Android 8 on there was no longer a boot.img, but instead the ramdisk.img. And for the recovery the so-called recovery_ramdisk.img.
Both images are different for each firmware, which is why precise information is necessary. The images can be extracted from the Update.App.
To do this, the firmware suitable for the device must be downloaded.
A xxx.crc.img is meaningless because it's just a checksum and not an image to flash!
Click to expand...
Click to collapse
I was trying to flash an XML file from a board firmware using IDT and it's showing me that
Eteon x said:
I was trying to flash an XML file from a board firmware using IDT and it's showing me that
Click to expand...
Click to collapse
Your Screenshot shows a Huawei p10 VTR Board firmware.
But this Thread is for P9, not for P10.
Is your device a Huawei P10?
Please ask in the Huawei P10 Forum.
I can't help you with IDT flashing method.
I worked for such cases only with ChimeraTool and sometimes with DC Phoenix. (Both are paid Services)
hi, as i mentioned in the title: i am in that twrp recovery, I am not able to check the files of realme ui OS zip file. i am able to copy the OS zip file to internal storage but i am not able see those files in twrp recovery. currenlty no OS is installled in my X2pro. need suggestions. should i download and flash another twrp file of lower version to check the same?