Related
Source rom: RUU_PRIMO_DS_ICS_40A_HTC_Europe_1.59.401.1_Radio_ 1.05.34D.25_20.20.30.22U_release_263747_signed.exe
!!I LIMITED LIABILITY IF YOU BRICK YOUR PHONE !!!
1. Unblock bootloader officially
2. Flash CMW recovery by command: fastboot flash recovery recovery.img
3. Download rom.
4. Unpack zip and place on your SD card to the directory \clockworkmod\backup\
You should get path clockworkmod\backup\Russian-1.59.401.1\
and list of files:
boot.img
cache.ext4.tar
data.ext4.tar
nandroid.md5
recovery.img
system.ext4.tar
5. Boot to recovert
6. Choose Backup/Restore
7. Choose Restore
8. Point out my backup and start restoring
9. Reboot to fastboot and flash original kernel fastboot flash boot boot_signed.imghttps://docs.google.com/open?id=0B5l6hlK799AFZjQxSWNpai12MUE
10. Turn on mobile, pass wizard and Enjoy!!!
Firmware, is clean, without root, not deodexed, without mods or anything else.
Includes all European languages, Google apps, Facebook, Dropbox and other cool things.
This will not flash radio cause you have S-OFF, and do not forget to make backup if you have something important on your phone, before doing something, cause all user data will be cleared.
Flashing original kernel in step 9 is mandatory, otherwise no WiFi and Bluetooth.
wrong list of providers
Hi,
First of all, thanks. I was able to change the rom of my t328w without any problems.
However, the list of the local mobile GSM providers is totally wrong. It is connected on "France Telecom" (in place of Mobistar) which is not possible because I live in Belgium. I tried to put an apns-conf.xml in the /etc folder but no success so far.
Any idea where I have to look ?
Thanks
Checksum error
6. Choose Backup/Restore
7. Choose Restore
8. Point out my backup and start restoring
Thanks for posting this. I have a Chinese T328W (bought in Beijing). I have followed all the steps to here but when I try to restore it says:
Checking MD5 sums ....
MD5 mismatch!
and then it fails. Any thoughts?
Many thanks in advance
Alex
alexshepherd said:
6. Choose Backup/Restore
7. Choose Restore
8. Point out my backup and start restoring
Thanks for posting this. I have a Chinese T328W (bought in Beijing). I have followed all the steps to here but when I try to restore it says:
Checking MD5 sums ....
MD5 mismatch!
and then it fails. Any thoughts?
Many thanks in advance
Alex
Click to expand...
Click to collapse
its possibly because of a different recovery from that of which the back up is taken, get the same recovery flashed!!
I mean same version of recovery!
happened the same wit my Karbonn a9 when I had a custom built cwm based non touch recovery, had taken the back up and tried to restore on my friends same phone wit touch recovery, so flash the right recovery 1st.
recovery.img
Quote:
its possibly because of a different recovery from that of which the back up is taken, get the same recovery flashed!!
I mean same version of recovery!
Unquote
The downloaded recovery.img from step 2 is not working AND the recovery.img in the downloaded files from step 4 is not working.
Both the same error
Checking MD5 sums ....
MD5 mismatch!
Where of how to get the recovery.img ?
htc vc
thainks bro .....
rooting htcc vc succsss.............
thank's for this very good job
you said that russian rom support all european language, but there's no french language
can I flash another european rom now ? and which one if it's possible ?
Thank you very much
Thanks
links gone
Hi to all, The links (google) in this thread do not exist any more. Please send me the sources of the links. Thx
If I'm creating a duplicate post, I apologize. However, I am trying to find a zip of CWM Touch 6.0.2.3.
As I am creating this post, I see that there may be a recovery in other forums. Is the recovery the same across all devices? I just want to make sure I get the right one for my S3.
Thank you,
The one and only GBP.
Just made these .zips...
CWM 6.0.2.3 (SGS3 T-Mobile)
CWM 6.0.2.3 Touch (SGS3 T-Mobile)
Flash either of them in Recovery Mode.
CWM SITE
Thank you, I really appreciate your help.
So I know how to do that the next time, how did you create the zip file? When I was at the CWM site, all I could download was an IMG file.
Try using twrp its nice and user friendly if you want an alternative touch based recovery just download goo manager from the play store and give it a try can't hurt
Sent from my SGH-T999 using xda premium
HOW to create a .zip (flashable rom when new version comes out)
1. Started with older CWM .zip ROM that I knew worked in past...
2. Download Newest CWM Recovery .img file from CWM SITE...
3. Extract older CWM .zip and rename to newest Version number... example "Recovery_CWM_v6.0.2.3"
4. rename newest CWM recovery .img to "recovery.img" and copy to your extracted folder. (Write over older version)
5. Re-compress with WinRAR or 7-Zip and make sure it's .ZIP format, not .RAR or another type.
6. All done
*** All your doing is taking recovery image and updateing into newly created .zip
*** in flash mode, the Recovery option to INSTALL (or flash any zip) always reads META-INF\com\google\android\"updater-script"
the script it reads for this example is...
ui_print("Please Wait");
ui_print("Flashing recovery");
show_progress(0.200000, 10);
package_extract_file("recovery.img", "/dev/block/mmcblk0p18");
show_progress(0.100000, 0);
ui_print("Success!!!");
so you can see it 's just gonna put "recovery.img" in your "mmcblk0p18" Partition which we can see is the recovery partition.
there are many partitions like System, Data, Flexrom, Cache, Dvalk Cache, SD Card, etc...they all have same start with different ending numbers mmcblk0p18
I agree with dscott973, that TWRP v2.3.3.1 is the best RECOVERY ! I'd change to that one (my opinion)
You can do the same thing by puting TWRP image renamed to "recovery.img" in the same format as this thread example (and rename folder accordingly),
but very important, always make sure your using the same type. Make sure your using for Samsung Galaxy S3 (TMobile type).
Example : Don't mix Verizon or AT&T type (just know what your doing and label it correctly)
ktmdave7 said:
1. Started with older CWM .zip ROM that I knew worked in past...
2. Download Newest CWM Recovery .img file from
3. Extract older CWM .zip and rename to newest Version number... example "Recovery_CWM_v6.0.2.3"
4. rename newest CWM recovery .img to "recovery.img" and copy to your extracted folder. (Write over older version)
5. Re-compress with WinRAR or 7-Zip and make sure it's .ZIP format, not .RAR or another type.
6. All done
*** All your doing is taking recovery image and updateing into newly created .zip
*** in flash mode, the Recovery option to INSTALL (or flash any zip) always reads META-INF\com\google\android\"updater-script"
the script it reads for this example is...
ui_print("Please Wait");
ui_print("Flashing recovery");
show_progress(0.200000, 10);
package_extract_file("recovery.img", "/dev/block/mmcblk0p18");
show_progress(0.100000, 0);
ui_print("Success!!!");
so you can see it 's just gonna put "recovery.img" in your "mmcblk0p18" Partition which we can see is the recovery partition.
there are many partitions like System, Data, Flexrom, Cache, Dvalk Cache, SD Card, etc...they all have same start with different ending numbers mmcblk0p18
I agree with dscott973, that TWRP v2.3.3.1 is the best RECOVERY ! I'd change to that one (my opinion)
You can do the same thing by puting TWRP image renamed to "recovery.img" in the same format as this thread example (and rename folder accordingly),
but very important, always make sure your using the same type. Make sure your using for Samsung Galaxy S3 (TMobile type).
Example : Don't mix Verizon or AT&T type (just know what your doing and label it correctly)
Click to expand...
Click to collapse
Thank you for your help. I'll take a look at TWRP. I just wanted the latest recovery because I'm considering upgrading to 4.2.1. I've read that the older recoveries struggle with the new file system, due to multiple users.
Merry Christmas
GBP85 said:
Thank you for your help. I'll take a look at TWRP. I just wanted the latest recovery because I'm considering upgrading to 4.2.1. I've read that the older recoveries struggle with the new file system, due to multiple users.
Merry Christmas
Click to expand...
Click to collapse
^So true, found that out the hard way... :silly:
ok. new noob here. so i have downloaded the file to root and install cwm on my gs3 from rootgalaxys3.com. the cwm in it won't allow me to flash a new rom. 'assert failed' is the only thing that keeps showing up. i looked into it and i think i have to upgrade my cwm version. so i found this link to the touch version for the galaxy s3. after i download it and i go to throw it in to the PDA slot in odin. its not there. so i extract it and i find 'meta-inf' file and a "recover.img" i can end up putting that in to the pda slot. BUT it ends in .img... is this ok or does the file have to end in .tar to flash properly and work?
PLEASE HELP ME!!!!
justinjrdawson said:
ok. new noob here. so i have downloaded the file to root and install cwm on my gs3 from rootgalaxys3.com. the cwm in it won't allow me to flash a new rom. 'assert failed' is the only thing that keeps showing up. i looked into it and i think i have to upgrade my cwm version. so i found this link to the touch version for the galaxy s3. after i download it and i go to throw it in to the PDA slot in odin. its not there. so i extract it and i find 'meta-inf' file and a "recover.img" i can end up putting that in to the pda slot. BUT it ends in .img... is this ok or does the file have to end in .tar to flash properly and work?
PLEASE HELP ME!!!!
Click to expand...
Click to collapse
Download ROM manager for cwm or goo manager for twrp and flash recovery from app in goo manager hit the menu button and flash recovery script. I dont know how to do it off hand in ROM manager but it is in there
Sent from my SGH-T999 using xda premium
The 2 files I posted earlier here are for FLASHING in RECOVERY only, not made for ODIN install.
another separate way to install Recovery is...
A) Download app from Market called "Terminal Emulator" (it's like using ADB commands on cell phone instead of PC).
B) use the same "recovery.img" from either of my 2 Zips earlier posted and then copied it to External SDCard (name of .img file has to match same name as in text below)
C) Run Terminal Emulator and enter these 2 command lines (Cell has to be ROOTED for su permissions to work)
su
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
D) Check to make sure you have Recovery.
-with cell being off, Use {Volume Down, Home, Power} to load up recovery and check it.
To directly answer the question, you can only flash .tar files with Odin.
ktmdave7 said:
CWM 6.0.2.3 (SGS3 T-Mobile)
CWM 6.0.2.3 Touch (SGS3 T-Mobile)
Flash either of them in Recovery Mode.
CWM SITE
Click to expand...
Click to collapse
Seriuosly... just attach things like this.. They are small enough. Especially since you chose to use a stupid file hosting site that tells you to register for a free account but doesnt even give that option.
ktmdave7 said:
CWM 6.0.2.3 (SGS3 T-Mobile)
CWM 6.0.2.3 Touch (SGS3 T-Mobile)
Flash either of them in Recovery Mode.
CWM SITE
Click to expand...
Click to collapse
/
Useless, i cant even create a free basic account, could you unload it somewhere else please?
Here you go: http://db.tt/okfh9vzU
ktmdave7 said:
The 2 files I posted earlier here are for FLASHING in RECOVERY only, not made for ODIN install.
another separate way to install Recovery is...
A) Download app from Market called "Terminal Emulator" (it's like using ADB commands on cell phone instead of PC).
B) use the same "recovery.img" from either of my 2 Zips earlier posted and then copied it to External SDCard (name of .img file has to match same name as in text below)
C) Run Terminal Emulator and enter these 2 command lines (Cell has to be ROOTED for su permissions to work)
su
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
D) Check to make sure you have Recovery.
-with cell being off, Use {Volume Down, Home, Power} to load up recovery and check it.
Click to expand...
Click to collapse
Don't you mean Volume Up, Home, Power for Recovery?
Can someone reload these links? I need them badly thanks
Verizon RUU 6.22.605.6 PN07IMG Signed
PN07IMG_M7_WL_L50_SENSE60_MR_VERIZON_WWE_6.22.605.6_HSM_Radio_1.13.41.1209_NV_VZW_4.64_002_release_460480_signed_1
Disclaimer:
Flash at your own risk!
This will wipe your entire phone, including internal sdcard. Back up your files to your pc first.
This will not effect s-off status.
How To Flash:
Check MD5 sum and make sure it is correct
Rename file to exactly PN07IMG.zip (PN[ZERO]7IMG.zip)
Place file on fat32 formated sd card or usb drive in no folders
Connect the sd card or usb drive to your phone using a usb-otg cable.
Boot to hboot (power off phone, hold volume down and power at the same time)
Once in hboot it should automaticly find the file, and prompt you to press volume up to flash it.
Phone will reboot several times. Once its done, the phone will try to boot but will bootloop.
Boot back to hboot ( hold vol down and power untill hboot comes up), and select factory reset.
The phone will rboot several times, once its done it will boot up to stock 6.22.605.6
DOWNLOAD
PN07IMG_M7_WL_L50_SENSE60_MR_VERIZON_WWE_6.22.605.6_HSM_Radio_1.13.41.1209_NV_VZW_4.64_002_release_460480_signed_1 zip
MD5:574ed7acdcf77263ac60943e2f001d2a - 1.4gb
.
Other M7 6.22.605.6 Files:
https://androidfilehost.com/?w=files&flid=46152
Reserved Too
Merry Christmas!
cmlusco said:
Verizon RUU 6.22.605.6 PN07IMG Signed
Quoted material removed......
Click to expand...
Click to collapse
I don't think this is exactly what you think it is.. it's only 419 megs large
What is it then? I have successfully flashed the phone with it after being wiped in twrp. It has also been downloaded more than 40 times, and no one has said anything about any issues. If its not i dont want to misrepresent it, especially if it will mess up someones phone. I think i know quite a bit about htc phones, but i am definitley no expert. All i know is it worked for me more than once, on two different m7's.
cmlusco said:
What is it then? I have successfully flashed the phone with it after being wiped in twrp. It has also been downloaded more than 40 times, and no one has said anything about any issues. If its not i dont want to misrepresent it, especially if it will mess up someones phone. I think i know quite a bit about htc phones, but i am definitley no expert. All i know is it worked for me more than once, on two different m7's.
Click to expand...
Click to collapse
I will tear it open tomorrow and take a look but the previous signed ruu were almost 1.4gb. Double check the size of the file you uploaded to make sure too. Just the system partition alone dd'd and trimmed and zipped would be larger than 419megs.
Sent from my SM-T810 using Tapatalk
dottat said:
I will tear it open tomorrow and take a look but the previous signed ruu were almost 1.4gb. Double check the size of the file you uploaded to make sure too. Just the system partition alone dd'd and trimmed and zipped would be larger than 419megs.
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
The file sizes and md5's match on my pc and on afh. This is a link to the original file as i got it. https://www.androidfilehost.com/
cmlusco said:
The file sizes and md5's match on my pc and on afh. This is a link to the original file as i got it. https://www.androidfilehost.com/?fid=24352994023707485
Click to expand...
Click to collapse
So I opened it today and it's not an RUU.
One is 1.4gb and one is 419Meg. I believe the file posted in the OP is the sync version of "update"... not an actual RUU. You should straighten up the OP to reflect this file link you posted (and is quoted in my post) here because it's the actual 1.4gb RUU. Unlike a rom, a bad RUU on a the wrong phone will lead to a brick so be very careful in what you post RUU wise.
Also, I believe you cut copied and pasted your RUU from the m9 thread you posted... the line below needs a little tweaking from the RUU.
The phone will rboot several times, once its done it will boot up to stock 3.10.605.7
Sent from my SM-T810 using Tapatalk
dottat said:
So I opened it today and it's not an RUU.
One is 1.4gb and one is 419Meg. I believe the file posted in the OP is the sync version of "update"... not an actual RUU. You should straighten up the OP to reflect this file link you posted (and is quoted in my post) here because it's the actual 1.4gb RUU. Unlike a rom, a bad RUU on a the wrong phone will lead to a brick so be very careful in what you post RUU wise.
Also, I believe you cut copied and pasted your RUU from the m9 thread you posted... the line below needs a little tweaking from the RUU.
The phone will rboot several times, once its done it will boot up to stock 3.10.605.7
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
So you are saying that the whole file is the ruu? Will that flash with zip's inside of a zip? Thanks for looking at it, learn something new every day.
cmlusco said:
So you are saying that the whole file is the ruu? Will that flash with zip's inside of a zip? Thanks for looking at it, learn something new every day.
Click to expand...
Click to collapse
The [email protected] zip format HTC uses has always contained multiple zips. Usually one or two contain firmware and a half dozen or so contain system broken into pieces.
Sent from my Nexus 6 using Tapatalk
dottat said:
The [email protected] zip format HTC uses has always contained multiple zips. Usually one or two contain firmware and a half dozen or so contain system broken into pieces.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I tried flashing the whole file both with fastboot flash, as a PN07IMG.zip, and as an update.zip from stock recovery, and all failed with errors. Fastboot flash gave error "read zipped android-info fail", PN07IMG.zip hboot said "no img wrong img", and recovery just said "installation aborted" after about 30 seconds. Any ideas, i have pulled the links for now.
cmlusco said:
I tried flashing the whole file both with fastboot flash, as a PN07IMG.zip, and as an update.zip from stock recovery, and all failed with errors. Fastboot flash gave error "read zipped android-info fail", PN07IMG.zip hboot said "no img wrong img", and recovery just said "installation aborted" after about 30 seconds. Any ideas, i have pulled the links for now.
Click to expand...
Click to collapse
How did you extract the smaller zip from the larger might I ask?
Sent from my Nexus 6 using Tapatalk
dottat said:
How did you extract the smaller zip from the larger might I ask?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
With a program called universal extractor. Think thats my problem, what program should i use?
cmlusco said:
With a program called universal extractor. Think thats my problem, what program should i use?
Click to expand...
Click to collapse
Ok... so the larger zip simply gets extracted.. that gives you two things. 1) the bootloader in a flashable zip and 2) the RUU itself (which is 1.4gb).
I am uploading a copy of the correct RUU file shortly. I believe that app you used only extracted one system chunk/zip. There are a couple tools i use to extract the RUU file down into separate zips. See the screenshot i attached.... original RUU/signed zip at the top and the resulting RUU below... first one is the firmare, 2,3 and 4th are system split up and the 5th is boot and tp zipped.
Here's the firmware only zip
https://www.androidfilehost.com/?fid=24367857647223006
Full flashable signed RUU zip (1.4gb)
https://www.androidfilehost.com/?fid=24367857647223007
dottat said:
Ok... so the larger zip simply gets extracted.. that gives you two things. 1) the bootloader in a flashable zip and 2) the RUU itself (which is 1.4gb).
I am uploading a copy of the correct RUU file shortly. I believe that app you used only extracted one system chunk/zip. There are a couple tools i use to extract the RUU file down into separate zips. See the screenshot i attached.... original RUU/signed zip at the top and the resulting RUU below... first one is the firmare, 2,3 and 4th are system split up and the 5th is boot and tp zipped.
Here's the firmware only zip
https://www.androidfilehost.com/?fid=24367857647223006
Full flashable signed RUU zip (1.4gb)
https://www.androidfilehost.com/?fid=24367857647223007
Click to expand...
Click to collapse
Thank you, i will update the op.
cmlusco said:
verizon ruu 6.22.605.6 pn07img signed
pn07img_m7_wl_l50_sense60_mr_verizon_wwe_6.22.605.6_hsm_radio_1.13.41.1209_nv_vzw_4.64_002_release_460480_signed_1
disclaimer:
flash at your own risk!
This will wipe your entire phone, including internal sdcard. Back up your files to your pc first.
This will not effect s-off status.
how to flash:
check md5 sum and make sure it is correct
rename file to exactly pn07img.zip (pn[zero]7img.zip)
place file on fat32 formated sd card or usb drive in no folders
connect the sd card or usb drive to your phone using a usb-otg cable.
Boot to hboot (power off phone, hold volume down and power at the same time)
once in hboot it should automaticly find the file, and prompt you to press volume up to flash it.
Phone will reboot several times. Once its done, the phone will try to boot but will bootloop.
Boot back to hboot ( hold vol down and power untill hboot comes up), and select factory reset.
The phone will rboot several times, once its done it will boot up to stock 6.22.605.6
download
pn07img_m7_wl_l50_sense60_mr_verizon_wwe_6.22.605.6_hsm_radio_1.13.41.1209_nv_vzw_4.64_002_release_460480_signed_1 zip
md5:574ed7acdcf77263ac60943e2f001d2a - 1.4gb
.
Click to expand...
Click to collapse
the process didnt work on my phone . Sohould i use adb fastboot tools??
Hi, I flashed TWRP to be able to install magisk on my friend's Honor 7x (BND-L21 C432) and now that magisk is flashed and configured I want to go back to the stock recovery. I've downloaded the update.zip with the Firmware Finder app, and I've extracted the recovery_ramdisk.img from the UPDATE.APP file.
But once flashed (with fastboot) I can't access it, it gives me ERROR MODE, like if the img was invalid.
Any help?
Thanks!
Did you download and flashed the correct build file? Which recovery you flashed?
shashank1320 said:
Did you download and flashed the correct build file? Which recovery you flashed?
Click to expand...
Click to collapse
I was using correct version, but I wasn't using HuaweiUpdateExtractor. After using it to get the img it worked well.
Thanks!
eXtremeDevil said:
Hi, I flashed TWRP to be able to install magisk on my friend's Honor 7x (BND-L21 C432) and now that magisk is flashed and configured I want to go back to the stock recovery. I've downloaded the update.zip with the Firmware Finder app, and I've extracted the recovery_ramdisk.img from the UPDATE.APP file.
But once flashed (with fastboot) I can't access it, it gives me ERROR MODE, like if the img was invalid.
Any help?
Thanks!
Click to expand...
Click to collapse
this install zip, should restore the recovery-from-boot.p file, the file that causes stock recovery to be replaced. I have not confirmed on this device but it is a generic solution that should work.
mrmazak said:
this install zip, should restore the recovery-from-boot.p file, the file that causes stock recovery to be replaced. I have not confirmed on this device but it is a generic solution that should work.
Click to expand...
Click to collapse
Thanks anyway, I was able to *correctly* extract the img file
What does that file exactly? Is there a backup of the recovery on the phone?? I assuming we're talking about normal recovery, not the second eRecovery thing, right?
eXtremeDevil said:
Thanks anyway, I was able to *correctly* extract the img file
What does that file exactly? Is there a backup of the recovery on the phone?? I assuming we're talking about normal recovery, not the second eRecovery thing, right?
Click to expand...
Click to collapse
Stock Android has a feature to make a recovery image from the boot.img. By checking the contents of the recovery partition and comparing a checksum. When the sum does not match, the file "recovery_from_boot.p" takes over and builds it's own recovery image.
When you install twrp and "swipe to allow system modification" that file gets renamed to end with ".bak"
This zip file verifies the recovery script is on the phone e, and if it is, it will remove the .bak extension . That makes the system .restore (make) stock recovery on the next boot up
Thanks for the info!
I root my devices with magisk and make chmod 555 to NVD_IMEI. because of magisk bug. Then I use few week(maybe 2 week?) with no problem. but I trid mount ext4 sdcard(because I want easy to recover with TWRP(but I did not install yet) but AP file is to big so can't use fat32) and it's successful. At next morning(January 28th), I saw signal was dead.(but, wifi is alive. ; I can't remember about Bluetooth, IMEI and is only signal dead or can't attach sim card.) So I reboot my phone( because I just think something crash it) but can't boot and get stuck. so I flash stock rom but can't boot. but only recovery(Normal and TWRP all) work well. So I do re-partition but also not work. I do NAND Erase with magisk patched AP and it booted. but IMEI disappear(of course because I do NAND Erase) and wifi did not work. I flash stock rom again but boot fail... when flash magisk patched AP it boot. I don't know why only magisk patched AP only boot, but I will use patched AP so not important yet.(I don't know what will happen future.) I think wifi error because I NAND Erase so vender partition broke. So I will flash vender image first. but sadly I have IMEI backup but I don't have vender partition backup... So I search internet but couldn't find vender image. Where can I get image? Is because of other problem? Then what and how can I fix it?
vendor.zip is vender folder(partition) backup after I NAND Erase it. TWRP backups of Vender partitions are also fine. If there's anything that needs to be changed for each device, please let me know as well.(ex.S/N, IMEI)
Broken partition after NAND erase? Sounds unlikely if flashing went successful. You cannot break NAND memory itself using software, and flashing with the "re-partition" option using external PIT file will re-partition everything unconditionally, so no broken partition may remain after that. Sounds more like you flashed wrong or incompatible stock firmware. And did you do Factory Reset after flashing?
P.S.: And I still don't understand why so many people need Magisk so badly. Root is needed only for a few quite low-level apps.
uluruman said:
Broken partition after NAND erase? Sounds unlikely if flashing went successful. You cannot break NAND memory itself using software, and flashing with the "re-partition" option using external PIT file will re-partition everything unconditionally, so no broken partition may remain after that. Sounds more like you flashed wrong or incompatible stock firmware. And did you do Factory Reset after flashing?
P.S.: And I still don't understand why so many people need Magisk so badly. Root is needed only for a few quite low-level apps.
Click to expand...
Click to collapse
NAND Erase is at odin option.
I do root for use "few quite low-level apps" and view and fix or backup app data.
I use "SM-A325N_2_20230113085551_pl06359zs5_fac.zip". It's compatible stock from samsung server. I use this stock to recover once, and I recover it.
Ok ) I have extracted vendor.img from your firmware: https://easyupload.io/vgzftz (if that's what you needed, I cannot understand your language clearly enough). Only I am not sure how you're going to flash it, because it's a dynamic partition inside the physical "super" partition and cannot be flashed directly besides (reportedly) using dd from the shell or using fastboot.
I still think you somehow mixed parts from different firmware versions. I never seen a situation when flashing a complete stock firmware with re-partition and NAND erase and then Factory Reset would not fix the booting. Try going into Recovery and do Factory Reset right after flashing, without allowing the system to try booting.
uluruman said:
Ok ) 귀하의 펌웨어에서 vendor.img를 추출했습니다: https://easyupload.io/vgzftz (필요한 경우 귀하의 언어를 충분히 이해할 수 없습니다). 물리적 "슈퍼" 파티션 내부의 동적 파티션이고 셸에서 dd를 사용하거나 fastboot를 사용하는 것 외에는 직접 플래시할 수 없기 때문에 어떻게 플래시할지 확신할 수 없습니다.
Click to expand...
Click to collapse
삼성에는 패스트부트가 없습니다. 그러나 다운로드 모드가 있습니다. 다운로드 모드에서 odin을 사용하여 펌웨어를 업로드하십시오. 또한 TWRP에서 img를 플래시할 수 있습니다.
uluruman said:
Ok ) I have extracted vendor.img from your firmware: https://easyupload.io/vgzftz (if that's what you needed, I cannot understand your language clearly enough). Only I am not sure how you're going to flash it, because it's a dynamic partition inside the physical "super" partition and cannot be flashed directly besides (reportedly) using dd from the shell or using fastboot.
Click to expand...
Click to collapse
At samsung, there is no fastboot. but, there is download mode. Use odin to flash at download mode. Also can flash img and zip at TWRP.
If you still need help please be a bit clearer what exactly is your problem, what you cannot achieve. I think a Korean-speaking person would be of much help here but it seems there is none