So, I flashed to 3.1 today.
Modified the framework-res to try to theme it and f'ed it all up, stuck in bootloops.
Got in fastboot and reflashed stock system.img and I cant get past the dual core screen.
do I need the 3.1 system.img and now the 3.0 one to flash?
Can someone please provide this?
nevermind, I flashed system.img and boot.img and im back in, although android.process.acore keeps force closing
did you use the boot.img from 3.0 or from the new 3.1 release? have the boot.img from the 3.1 handy?
Related
hi i m trying to update my gt540 from cyanogenmod (swiftdroid v2.0 M4) to cyanogenmod (swiftdroid v2.0 M5).this shows error assert failed: write_raw_image("temp/boot.img","boot") .please help .i m wondering what to do???
This is a known bug with M5. The update has installed, but the boot.img hasn't been flashed. Here is what you need to do.
Extract boot.img from the update .zip file. If you can boot into swiftdroid, use YaffsExpert to flash the boot.img.
Hope it helps,
Jack
JackG256 said:
This is a known bug with M5. The update has installed, but the boot.img hasn't been flashed. Here is what you need to do.
Extract boot.img from the update .zip file. If you can boot into swiftdroid, use YaffsExpert to flash the boot.img.
Hope it helps,
Jack
Click to expand...
Click to collapse
is there a version that already has the fix applied? i tried the one on the main thread that was supposed to be fixed, but it still gave this error msg.
Same problem for me.
I don't think the installation completes since the installation seems to abort before system.img is flashed.
I could always try fastboot but I'd wait for a fix.
No it works fine, it aborted at the boot.img. so just reboot and uses the terminal to complete the update.
are you 100% sure? have you tried it? i don't think the phone will boot if the boot.img is corrupt.
nibras_reeza said:
are you 100% sure? have you tried it? i don't think the phone will boot if the boot.img is corrupt.
Click to expand...
Click to collapse
If you were to look at the updater-script file in the update.zip file, the system partition is modified first. Also, the boot.img isn't corrupt, the update script has an error in it which aborts the boot.img flash. But if you flash the boot.img via fastboot or YaffsExpert, it works perfectly.
Jack
For reference's sake, the issue has been fixed I guess.
SwiftDroid v2.0 M5 Fixed
Recovery:http://swift.kulkoff.com/SwiftDroid_v2.0_recovery_M5.zip
Fastboot:http://swift.kulkoff.com/SwiftDroid_v2.0_fastboot_M5.zip
Guys, I need some help. I need to flash the stock kernel and recovery in order to update OTA to b381 (when I try to install it it goes into Revolution Recovery and the installation fails), but I can't find it anywhere... I tried to flash the ones in the b381 update but I had problems unlocking the phone since the code was not recognised, and had to bypass it with adb. Now I'm back to Revolution Recovery and Elite Kernel V4, what could have been the problem? The kernel or the recovery? Anyway, could anyone give me a link to the b371 stock boot.img and recovery.img? My internet connection sucks and I can't dowload the whole firmware to extract the images (I probably deleted the backups I had made before changing recovery and kernel, yes, I'm dumb).
I newbed up my phone (soft bricked) and am trying to flash back to stock, but didn't think to save the stock recovery image before I flashed TWRP. Does anyone happen to have it for the ZE553KL? Or perhaps the stock firmware can be flashed through TWRP? I tried to flash via adb sideload, and it appeared to work, but that could be the totally wrong way.
Thanks!
Check the ROM somewhere here "convert CN to WW". There's a stock image in there with instructions how to sideload through ADB.
Thanks @magicmanfk!
The recovery.img is indeed in the ROM file attached to that thread. I extracted it and ran
Code:
fastboot flash recovery recovery.img
and it brought back the stock recovery. Then I was able to flash one of the older firmware files via
Code:
adb sideload UL-Z01H-WW-11.41.87.2-user-1.zip
and I'm back to stock. Now going to try to upgrade to N.
lirpa said:
Thanks @magicmanfk!
The recovery.img is indeed in the ROM file attached to that thread. I extracted it and ran
Code:
fastboot flash recovery recovery.img
and it brought back the stock recovery. Then I was able to flash one of the older firmware files via
Code:
adb sideload UL-Z01H-WW-11.41.87.2-user-1.zip
and I'm back to stock. Now going to try to upgrade to N.
Click to expand...
Click to collapse
Did you use that image for a US phone or other?
The image you used looks like the firmware on the Asus site dated 6/6/2017 so I guess the firmware there are full images and not patches like someone suggested???
I'm asking because I feel like I may want to go back to US version stock at some point and don't have a backup so if the above is the case then I probably don't need to ask someone for a backup...
Did you have any luck upgrading to N? When I try using the phone's normal procedure I get an error saying I can't upgrade to N from a firmware less current than 11.41.87.2 even though that's the one I'm running. After flaking back to stock recovery I was able to update to that one normally... I wonder if there was something subtle that went wrong.
Would anyone here have it? I overlooked the "7.1.1" message and used TWRP anyways, THEN used the 7.1.1 boot img which threw me into a bootloop, I can boot into EDL just fine, sideload doesn't work with me, so I see obtaining my original B2017G US boot.img and reflashing it with tulip as the best option to get back on track! Hope someone is able to help
Though, would there be any other methods of flashing the boot.img and removing the bootloop, like updating my firmware to 7.1.1 or something?
https://forum.xda-developers.com/showpost.php?p=73257562&postcount=13
I see something here, downloaded "Axon7mini_Android7(SD card software).zip" but unfortunately I don't know what to do with that update.zip file.
I wanted to relock my Mi A1 but forgot to backup the stock boot image. Searched the monthly ROM update thread but it's not there yet.
Anyone got it?
Thanks!
Edit:
My bad, it was June patch (OPM1.171019.019.V9.6.3.0.ODHMIFE)
https://forum.xda-developers.com/mi-a1/how-to/ota-xiaomi-mi-a1-ota-links-t3718542
i need stock boot image for july patch to
I want to update to August but I have already rooted Magisk and I uninstalled it first which happened to be uncommand, because it might boot. img patch has overwritten boot.img default.
for the link above I do not understand why it is so large in size even though the img boot that has been patched is less than 5MB.
please help
nirvanarahadian said:
I want to update to August but I have already rooted Magisk and I uninstalled it first which happened to be uncommand, because it might boot. img patch has overwritten boot.img default.
for the link above I do not understand why it is so large in size even though the img boot that has been patched is less than 5MB.
please help
Click to expand...
Click to collapse
it's the entire rom, not only the boot image, that's why it is so large in size
Done
smsporto said:
it's the entire rom, not only the boot image, that's why it is so large in size
Click to expand...
Click to collapse
Done i downloaded fastboot in here https://forum.xda-developers.com/mi...-ota-links-t3718542/post74828108#post74828108, i download Android 8.1.0 [OPM1.171019.026.V9.6.4.0.ODHMIFE] (fastboot image) and i do flash with cmd boot.img. its work , not uncommand anymore, and i did an experiment with restarting my phone and stock boot img is only temporary and returns uncommand. how to fix it?,is it safe if i immediately update to the latest patch from OTA, the thing that is feared if booting will return like that and i'm confused looking for boot.img for august patch
nirvanarahadian said:
Done i downloaded fastboot in here https://forum.xda-developers.com/mi...ota-links-t3718542/post74828108#post74828108, i download Android 8.1.0 [OPM1.171019.026.V9.6.4.0.ODHMIFE] (fastboot image) and i do flash with cmd boot.img. its work , not uncommand anymore, and i did an experiment with restarting my phone and stock boot img is only temporary and returns uncommand. how to fix it?,is it safe if i immediately update to the latest patch from OTA, the thing that is feared if booting will return like that and i'm confused looking for boot.img for august patch
Click to expand...
Click to collapse
If u are sure that u haven't touched the system partition then u can try to update via OTA. Make sure u flashed and not only booted the downloaded boot.img from V9.6.4.0 ROM. I guess it's better to download the latest version from here:
https://drive.google.com/drive/mobile/folders/1dw87qgRNGxfj7UZduHK91LE6X1Xs7CWL
Then do a clean flash and install the entire ROM with fastboot.
"'*"*"
I've done flashing while on the way and I'm waiting. My cellphone suddenly turns on and it looks like it's doing a factory format. and I just updated it to August. all my data is lost even though the user data has been secured and the flashing process has not finished