i flashed the boot.img provided inside the cm7.2 zip file using fastboot and wiped/factory reset my device and wiped cache using CWM and while attempting to flash cm-7.2.0-smultron.zip through CWM i get this:
assert failed: getprop("ro.build.product.device") == "ST15i" || getprop("ro.build.product") == "ST15i" || getprop("ro.product.board") == "ST15i" || getprop("ro.product.device") == "ST15a" || getprop("ro.build.product") == "ST15a" || getprop ("ro.product.bE: error in /sdcard/cm-7.2.0-smultron.zip
(status 7)
installation aborted.
please help friends!
my device is normal but i'm not able to flash cm7.2 . i'm new to android.
thanks.
device:
st15i
unlocked bootloader (official)
rooted (zergrush)
ICS 4.0.4(flashtool)
Download a version from here:
http://download.cyanogenmod.com/?type=RC&device=smultron
If it doesn't resolve, do the following:
Open zip file, go to meta-inf> com> google> android> extract updater-script
Open updater-script with notepad++ (has to be notepad++).
Remove following lining:
Code:
assert(getprop("ro.product.device") == "ST15i" || getprop("ro.build.product") == "ST15i" || getprop("ro.product.board") == "ST15i" ||
getprop("ro.product.device") == "ST15a" || getprop("ro.build.product") == "ST15a" || getprop("ro.product.board") == "ST15a" ||
getprop("ro.product.device") == "smultron" || getprop("ro.build.product") == "smultron" || getprop("ro.product.board") == "smultron");
Do not wipe /system.
Install stock ROM with Flashtool(kernel is not needed) and try installing again.
Wipe cache, dalvik cache and make factory reset, but, once again, do not wipe /system.
CyanogenMod ROM checks the build.prop file, if you are installing the correct ROM. This prevents problems, like installing wrong ROM on your phone.
download link not working
iONEx said:
Download a version from here:
http://download.cyanogenmod.com/?type=RC&device=smultron
If it doesn't resolve, do the following:
Open zip file, go to meta-inf> com> google> android> extract updater-script
Open updater-script with notepad++ (has to be notepad++).
Remove following lining:
Code:
assert(getprop("ro.product.device") == "ST15i" || getprop("ro.build.product") == "ST15i" || getprop("ro.product.board") == "ST15i" ||
getprop("ro.product.device") == "ST15a" || getprop("ro.build.product") == "ST15a" || getprop("ro.product.board") == "ST15a" ||
getprop("ro.product.device") == "smultron" || getprop("ro.build.product") == "smultron" || getprop("ro.product.board") == "smultron");
Click to expand...
Click to collapse
download link not working
how to do it?
Someguyfromhell said:
Do not wipe /system.
Install stock ROM with Flashtool(kernel is not needed) and try installing again.
Wipe cache, dalvik cache and make factory reset, but, once again, do not wipe /system.
CyanogenMod ROM checks the build.prop file, if you are installing the correct ROM. This prevents problems, like installing wrong ROM on your phone.
Click to expand...
Click to collapse
how to flash just the rom?
how not to wipe /system?
thanks for helping
gouthamthemostwanted said:
how to flash just the rom?
how not to wipe /system?
thanks for helping
Click to expand...
Click to collapse
You can look into someguyfromhell's, or my signature. There you'll find how to flash a ROM (and more) explained with greater detail.
Anyway, copy the ROM zip onto your SDcard.
boot into recovery, select factory reset, wipe cache, then choose install custom zip> choose zip and select your ROM.
gouthamthemostwanted said:
how to flash just the rom?
how not to wipe /system?
Click to expand...
Click to collapse
Just had to put it...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Install the same like you did, but do not use the wipe /system option.
it worked the other way!
Someguyfromhell said:
Just had to put it...
Install the same like you did, but do not use the wipe /system option.
Click to expand...
Click to collapse
hey! flashed cyan! guess what i did? i flashed my stock firmware then flashed boot.img from cyan, booted into recovery but this time i wiped /system and flashed cyan rom and it worked like a charm! but this time it was with cyanogenmod9! without /system wipe it didnt work but after wiping out system it worked anyways thanks for helping me out! :highfive:
Hi guys ! Have same problem as original poster. I'll try removing first 3 lines with note++ and will report back. BTW why is this happening I mean it looks like it's saying that this device is not ST15a ....we it's not It's ST15i and according to CM this build is made for ST15i ... unless both are same thing just different regions called it different letter .....
u are posting in the wrong section my friend. reported
Dude look at the date of OP. At that time we didn't had Q/A forum at that time...
Press THANKS if I helped,
Best Regards,
AJ
alokbina said:
Dude look at the date of OP. At that time we didn't had Q/A forum at that time...
Press THANKS if I helped,
Best Regards,
AJ
Click to expand...
Click to collapse
sorry! I didn't knew it. however now it's in the correct section
Related
Myself and my team are bringing you guys native 3minit and Infamous! I need someone to connect your phone to a computer and have working adb then do the following commands. Then upload the file to dropbox or even copy and paste the whole thing to pastebin.com. This way I can bring my kernel and ROM to you! Thanks, Also will need testers ASAP!!!
Code:
adb pull /proc/config.gz
Code:
here
gunzip config.gz
Now send the file to me. PM or post here. Thanks!
Beta 1 is reading for testing. Please make comments in this thread only! Logcat's if your getting fc's please.
There will be a Kernel for this rom built by @Jamison904 This is why we need the info above.
Also there will be themes by @blacknight1114
As per the Developer's request we can't include the app in the rom. So see below!
The free app is here
Play Store App is here well worth it...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
:good:
and one more
Mr Impossible said:
and one more
Click to expand...
Click to collapse
Mine
I'll be a tester, I freed up some time at night recently.
Orical said:
I'll be a tester, I freedom up some time at night recently.
Click to expand...
Click to collapse
Verizon too
Thanks
This is sounding good I must say
Sent from my Beastly powered S4 using Tapatalk 4
i may try!
Added a few thing and fix a few others...
Beta 2
Verizon S4 here how can I help / test ?
Also is this based off the new ME7 and not the MDK ?
Can't believe I barely saw this! Will definitely be trying this out :good:
Sent from my GS4
ahoslc said:
Verizon S4 here how can I help / test ?
Also is this based off the new ME7 and not the MDK ?
Click to expand...
Click to collapse
It's MGA based
I couldn't get it to flash in recovery looked like it was going through it then failed at the end.
ahoslc said:
I couldn't get it to flash in recovery looked like it was going through it then failed at the end.
Click to expand...
Click to collapse
It fails when flashing the kernel. I swapped out the kernels and it flashed fine. However, upon booting I was greeted with a SystemUI fc and had no signal/network access. Not sure if this can be attributed to the kernel I switched or something else.
Edit: Sent the OP a pm for the config.gz. If you need it to be from a fully stock S4 I can probably get one tomorrow.
I had to restore my backup since I'm going out and getting a logcat didn't cross my mind till now :/
Pr1meSuspect said:
It fails when flashing the kernel. I swapped out the kernels and it flashed fine. However, upon booting I was greeted with a SystemUI fc and had no signal/network access. Not sure if this can be attributed to the kernel I switched or something else.
Edit: Sent the OP a pm for the config.gz. If you need it to be from a fully stock S4 I can probably get one tomorrow.
I had to restore my backup since I'm going out and getting a logcat didn't cross my mind till now :/
Click to expand...
Click to collapse
No that should be fine no need to be stock. I sent the info to @Jamison904 Thanks!
Ok the SystemUI and no signal/network I should be able to fix Sprint had similar issues.
I'll probably get 1 more test build out today then it's off to XDA DevCon for the weekend so I would say no updating till Monday...
What kernel did you use? and a logcat would be great help!
ok changed the kernel and a few other things
Beta 3
I think there is a problem with your updater-script. After pulling a log from twrp I noticed why the rom would not flash.
Code:
Flashing kernel
package_extract_file: no boot.img in package
script aborted: assert failed: package_extract_file("boot.img", "/tmp/boot.img")
assert failed: package_extract_file("boot.img", "/tmp/boot.img")
E:Error executing updater binary in zip '/external_sd/Downloads/Alpha_VZW_S4_5.0_Beta3.zip'
Error flashing zip '/external_sd/Downloads/Alpha_VZW_S4_5.0_Beta3.zip'
So I changed it to "boot.lok" in the updater-script and it flashed fine. However, after booting up there's no signal or network access. I'm heading off to work within the half hour so I can't do any troubleshooting atm.
il buono said:
Flashing kernel
package_extract_file: no boot.img in package
script aborted: assert failed: package_extract_file("boot.img", "/tmp/boot.img")
assert failed: package_extract_file("boot.img", "/tmp/boot.img")
E:Error executing updater binary in zip '/external_sd/Downloads/Alpha_VZW_S4_5.0_Beta3.zip'
Error flashing zip '/external_sd/Downloads/Alpha_VZW_S4_5.0_Beta3.zip'
Click to expand...
Click to collapse
Now it makes sense why the kernel I swapped it for worked perfectly. The kernel was still loki'd but it was named "boot.img".
il buono said:
I think there is a problem with your updater-script. After pulling a log from twrp I noticed why the rom would not flash.
Code:
Flashing kernel
package_extract_file: no boot.img in package
script aborted: assert failed: package_extract_file("boot.img", "/tmp/boot.img")
assert failed: package_extract_file("boot.img", "/tmp/boot.img")
E:Error executing updater binary in zip '/external_sd/Downloads/Alpha_VZW_S4_5.0_Beta3.zip'
Error flashing zip '/external_sd/Downloads/Alpha_VZW_S4_5.0_Beta3.zip'
So I changed it to "boot.lok" in the updater-script and it flashed fine. However, after booting up there's no signal or network access. I'm heading off to work within the half hour so I can't do any troubleshooting atm.
Click to expand...
Click to collapse
Thanks man forgot all about that! Was rushing to ge to DevCon...
Sent from my SGH-M919 using Tapatalk 4
Ok fixed the updater script and now the kernel will load and rom should boot.
Beta 4
Here is Beta 5 with added VZW apps... Not sure if any of these will break the rom...
Beta 5
Would test anything you need! Just tell me when!
Been trying for hours to get my GS3 (i9305N) working again.
I am running CWM recovery 5.5.0.4. I had a rooted Stock ROM.
I wanted the latest nightly build of Cyanogenmod, which I've downloaded from their site get.cm.
I also bought Mobile Odin from the playstore after reading how easy it is to use... The load bar got stuck at 20% when flashing the new ROM in mobile odin, after an hour I decided to reboot the phone because it was probably never going to finish.
Now I can only get into CWM and download mode.
I've also tried to update CWM to latest, but it seems impossible to do so with only an .img and not .tar.md5 unless u can access mobile odin... which imo ruined my phone.
In CWM, when trying to install CM 10.2.zip I get an error message saying.
From what I've read the CM for i9305 should be compatible with i9305N aswell, is this true?
yada yada ...
Installing update...
assert failed: getprop("ro.product.device") == "m3" || getprop("ro.build.product") == "m3" || getprop("ro.product.device") == "m3xx" || getprop("ro.build.product") == "m3xx" ||
getprop("ro.product.devide") == "i9305" || getprop("ro.build.product") == "GT-I9305" || getprop("ro.build.product") == "GT-I9305"
E: Error in /sdcard/cm-10.2-20130820-NIGHTLY-i9305.zip
(Status 7)
Installation aborted.
I've also tried to flash several other recoveries with Odin v3.07 for PC.
Which gets stuck at "Get PIT for mapping..." and then says "Complete(write) operation failed."
I am somewhat of a n00b when it comes to flashing ROMs and managing my phone on this level.
I hope someone can help me get my phone to work again.
Do I need to get latest CWM recovery in order to flash the latest cm ROM?
or how do I get passed that error message when trying to flash the ROM?
Ducken said:
Do I need to get latest CWM recovery in order to flash the latest cm ROM?
or how do I get passed that error message when trying to flash the ROM?
Click to expand...
Click to collapse
Here..
Ducken said:
Been trying for hours to get my GS3 (i9305N) working again.
I am running CWM recovery 5.5.0.4. I had a rooted Stock ROM.
Wrong forum this is I9300 have you been flashing the wrong stuff on your phone ???.
Click to expand...
Click to collapse
MoonBlade said:
Here..
Click to expand...
Click to collapse
Now I feel a little dumb. But thanks!!
I'll try to solve this now
JJEgan said:
Wrong forum this is I9300 have you been flashing the wrong stuff on your phone ???.
Click to expand...
Click to collapse
O'RLY!!!
Because from what I can see the subforum is named "Samsung Galaxy S III I9300, I9305"
Glad to see I'm not the only dumb person here.
Edit: Link by MoonBlade worked perfectly
Front Page
Galaxy S III General
Discussion about the Samsung Galaxy S III (general chat, tips & tricks, etc)
Threads: 2,876
Posts: 230,803
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Galaxy S III Q&A, Help & Troubleshooting
For all of your questions relating to the Samsung Galaxy S III
Threads: 22,973
Posts: 155,582
Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & Troubleshooting
For all of your questions relating to the Galaxy S III I9305 (4G LTE + 2GB
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is first rom (type backup) for LG F70
Whats you need:
Unlock bootloader and TWRP recovery http://forum.xda-developers.com/showthread.php?t=3278742
#Debloated
#G3 apps (dialer, system ui, file menaget ...)
#AOSP apps (clock...)
#Pre rooted
#Init.d and bussy box support
#New gpu drivers
#Nova launcher
#Viper FX
#Some extra UI stuff
#Bulid.prop tweaks
#Xposed
#Add block (optional, to enalbe go to adaway and download host file)
#android marshmallow bootanimation
and more...
Instal
1. Download
2. Unpack and paste into TWRP\BACKUPS\LGD3158b50563c\
3. Restore backup
4. Enjoy
HTML:
v1.0 (beta)First relise
If you like my work, You can donate me via paypal:
Need help to install TWRP recovery first before the ROM
Hi Vangreen,
Thanks for making this ROM. I really want to try it. However, I couldn't install the TWRP recovery. Appreciate any help on that front.
1. I went to KuroHaki's post.
2. I followed his instructions step by step
3. In the second step to "set zero the download mode" I received an error message. It said "write error: No space left on device".
3a. After rooting the device with Kingo Root, I have not downloaded many root apps. I have only allowed the pre-installed apps to update.
3b. Pls advice how much memory space is required to run this recovery installation. I will try to delete as many apps as I can and re-run the recovery installation process.
4. In the terminal, after the "No space left on device" message, the terminal prompt changed from "[email protected]:/ #" to "1 | [email protected]:/ #". and when I inserted the command "adb reboot" there's an error msg - "device not found".
Appreciate any advice you may have.
Thank you
Andrew
Try that method to unlock bootloader http://forum.android.com.pl/index.php?/topic/221353-Odblokowywanie-bootloadera
After that download flashify from Play Store and Flash recovery img
TT || LG F70
Hi, is this Rom working? I need to try this Rom.
I do not have much knowledge about android so I am asking
Thanks in advance
Daroor skanda said:
Hi, is this Rom working? I need to try this Rom.
I do not have much knowledge about android so I am asking
Thanks in advance
Click to expand...
Click to collapse
Hi
Worka Perfect , here you have New recovery and unlock bootloader http://forum.xda-developers.com/showthread.php?t=3278742
TT || LG F70
Yup, i tried the rom its working :good:,Thanks for the rom
Please continue the development on F70.
When would you provide cm12.1?
Daroor skanda said:
Yup, i tried the rom its working :good:,Thanks for the rom
Please continue the development on F70.
When would you provide cm12.1?
Click to expand...
Click to collapse
I start compile cm but it is a lot of work to do with kernel and not much time :/
I think month or two and will be ready
Source
https://github.com/CM-LG-F70N
New recovery
http://forum.xda-developers.com/showthread.php?t=3278742
TT || LG F70
The bugs in this rom are:-
1. Display settings are not working.
2. Edit button in notification bar is not working.
3. After performing factory reset, settings force closes.
Is there any solutions for this bugs?
Thanks in advance.
Daroor skanda said:
The bugs in this rom are:-
1. Display settings are not working.
2. Edit button in notification bar is not working.
3. After performing factory reset, settings force closes.
Is there any solutions for this bugs?
Thanks in advance.
Click to expand...
Click to collapse
v1.1 I forgot to paste it on xda
https://drive.google.com/file/d/0BzdzcTIkHtbcQzBJQVJrLWpFWEk/view
Fiew changes
TT || LG F70
In v1.1 i cannot connect my phone in MTP mode to pc.It stays in charging mode only.
What to do?
Thanks in advance.
Daroor skanda said:
In v1.1 i cannot connect my phone in MTP mode to pc.It stays in charging mode only.
What to do?
Thanks in advance.
Click to expand...
Click to collapse
I use Linux, there is no problem
TT || LG F70
Please try and slove the MTP bug in windows.
I am using windows8.1pro, this is the only bug in v1.1.
Thanks in advance.
Daroor skanda said:
Please try and slove the MTP bug in windows.
I am using windows8.1pro, this is the only bug in v1.1.
Thanks in advance.
Click to expand...
Click to collapse
In v1.0 should be ok, i 1.1 i change setting app with g3 ui
TT || LG F70
when i install the rom everything is correct, but after installing all the apps the camera screen is drifting.
like this
How's CM12.1 rom development going on?
Daroor skanda said:
How's CM12.1 rom development going on?
Click to expand...
Click to collapse
A lot of errors, and no Time.
Daroor skanda said:
when i install the rom everything is correct, but after installing all the apps the camera screen is drifting.
like this
Click to expand...
Click to collapse
Change dpi for kamera app in xposed module appsettings
TT || LG F70
When would you release CM12.1 rom?
Daroor skanda said:
When would you release CM12.1 rom?
Click to expand...
Click to collapse
I have a lot od problem with compilation. I think maybe for month, maybe never. I stil work but Hits to hard for me
Cross your fingers
TT || LG F70
Take a look at this guide i think may help you
http://forum.xda-developers.com/chef-central/android/guide-how-to-port-lollipop-marshmallow-t3283452
Daroor skanda said:
Take a look at this guide i think may help you
http://forum.xda-developers.com/chef-central/android/guide-how-to-port-lollipop-marshmallow-t3283452
Click to expand...
Click to collapse
Port is always a worst idea. I compile from Source.
I can make something like in this tutorial, but i not going to try myself. If you want test write to me.
TT || LG F70
I was disappointed to find that the HTC One M9 Sprint (himawhl) wasn't on the supported device list for LineageOS. So I figured I would try my luck and install lineageos for the Verizon version of the phone. I got an error saying that my device was a himawhl not a himawl. So I opened the ZIP file and navigated to \META-INF\com\google\android and opened the updater-script file and changed himawl to himawhl. I then sent the ZIP to my phone and it worked!
Everything seems to be working minus GPS and 60 FPS recording.
Hope this helped someone out If you have any questions feel free to ask them
https://download.lineageos.org/himawl
Here's what my updater-script looks like:
assert(getprop("ro.product.device") == "htc_himawhl" || getprop("ro.build.product") == "htc_himawhl" || getprop("ro.product.device") == "himawhl" || getprop("ro.build.product") == "himawhl" || abort("E3004: This package is for device: htc_himawhl,himawhl; this device is " + getprop("ro.product.device") + ".");
assert(hima.verify_sbl1("1.2.50.1.36","1.2.50.1.37","1.2.50.1.38") == "1");
ui_print("Target: htc/HTCOneM9vzw/htc_himawhl:6.0/MRA58K/669662.7:user/release-keys");
ifelse(is_mounted("/system"), unmount("/system"));
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup");
unmount("/system");
if is_mounted("/data") then
package_extract_file("META-INF/org/lineageos/releasekey", "/tmp/releasekey");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
else
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/userdata", "/data", "");
package_extract_file("META-INF/org/lineageos/releasekey", "/tmp/releasekey");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
unmount("/data");
endif;
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore");
unmount("/system");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.200000, 10);
set_progress(1.000000);
Edit: fixed a typo
Thank you for this - it seems to be working so far.
How would I go about installing LineageOS updates? Can I install it directly from the notification, or do I need to download it each time, make the same edit to himawhl, and reflash?
Thanks!
DoubleJump said:
Thank you for this - it seems to be working so far.
How would I go about installing LineageOS updates? Can I install it directly from the notification, or do I need to download it each time, make the same edit to himawhl, and reflash?
Thanks!
Click to expand...
Click to collapse
You will need to do this every time you want to update.
Yw!
So, GPS is not working with Himawl? have you tried the latest update?
I want to install Lineage Os in my Sprint htc one m9 but i need the GPS working.
Ulix980 said:
So, GPS is not working with Himawl? have you tried the latest update?
I want to install Lineage Os in my Sprint htc one m9 but i need the GPS working.
Click to expand...
Click to collapse
I haven't tried the latest update. Some people have reported the GPS works. It might not work for me because I have xposed installed.
Ulix980 said:
So, GPS is not working with Himawl? have you tried the latest update?
I want to install Lineage Os in my Sprint htc one m9 but i need the GPS working.
Click to expand...
Click to collapse
I'm using this method on my Sprint one m9 (Himawhl), and GPS works fine for me.
Are there any Oreo roms available?
Sent from my Redmi Note 4 using Tapatalk
hey man the last update zip can't be extracted ,I even tried changing my model number to himawl but update stuck in about one third
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bishoy ashraf said:
hey man the last update zip can't be extracted ,I even tried changing my model number to himawl but update stuck in about one third
Click to expand...
Click to collapse
TWRP can't extract it?
Poebat said:
TWRP can't extract it?
Click to expand...
Click to collapse
no I can't extract it to edit it "with WinRAR or es file explorer ,I even tried in my PC with no luck "?
---------- Post added at 11:21 PM ---------- Previous post was at 11:18 PM ----------
this is the link to the screenshot:
https://drive.google.com/file/d/1XW9sZq77t_2ETL3R6v6hzZ2NMA4tdkhd/view?usp=drivesdk
bishoy ashraf said:
no I can't extract it to edit it "with WinRAR or es file explorer ,I even tried in my PC with no luck "
Try redownloading
Click to expand...
Click to collapse
Poebat said:
bishoy ashraf said:
no I can't extract it to edit it "with WinRAR or es file explorer ,I even tried in my PC with no luck "
Click to expand...
Click to collapse
I found the problem,the download zip was corrupted
Click to expand...
Click to collapse
Hello everybody,
I'm wondering about the possibility of flashing TWRP not just in the recovery partition, but also to the recovery backup partition. As sometimes (like when dm verity is enabled) the phone may overwrite TWRP with stock recovery, there's an high risk of erasing the whole memory when you try to boot TWRP. I think it could be useful to have TWRP in both partitions. Even in the case something in TWRP doesn't work (never happened to me, but it's a possibility), and we don't have the original recovery, we could still use fastboot to flash the stock recovery.
Does it make sense or am I somehow wrong? If it's possible, can it be done by just making a TWRP flashable zip, editing the updater-script file to make it flash the recovery in the backup partition?
tremalnaik said:
Hello everybody,
I'm wondering about the possibility of flashing TWRP not just in the recovery partition, but also to the recovery backup partition. As sometimes (like when dm verity is enabled) the phone may overwrite TWRP with stock recovery, with the high risk of erasing the whole memory, I think it could be useful to have TWRP in both partitions. Even in the case something in TWRP doesn't work (never happened to me, but it's a possibility), and we don't have the original recovery, we could still use fastboot to flash the stock recovery.
Does it make sense or am I somehow wrong? If it's possible, can it be done by just using the TWRP flashable zip, editing the update-script file to make it flash the recovery in the backup partition?
Click to expand...
Click to collapse
I don't think there is a recovery backup partition.
Here it is:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If it wasn't there, how could the phone be able to restore the stock recovery by itself?
tremalnaik said:
Here it is:
If it wasn't there, how could the phone be able to restore the stock recovery by itself?
Click to expand...
Click to collapse
Well, if that was a backup recovery, then it should work to dd TWRP there.
I was always under the impression that the stock recovery was stored in the boot image somewhere.
I've prepared this script for flashing: considering it's the first time I mess up the updater-script for such an essential part of the system, can you confirm if it is correct, considering I'd put the TWRP image in the zip as recovery/recoverybak.img ?
Code:
ui_print("Flashing TWRP to recovery backup H850");
package_extract_dir("recovery", "/tmp");
set_perm_recursive(0, 0, 0777, 0777, "/tmp");
ui_print("Verifying ZIP contents...");
ui_print(" ");
apply_patch_check("/tmp/recoverybak.img", "9edc062fc9483652a9c57d185447a92a36d0f603") || abort("\"/tmp/recoverybak.img\" has failed verification.");
ui_print("Flashing. this might take a bit...");
ui_print(" ");
package_extract_file("recovery/recoverybak.img", "/dev/block/bootdevice/by-name/recoverybak");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" Finished... ");
ui_print(" ");
ui_print("Zip by Tremal Naik");
ui_print("Template by autoprime - thx");
ui_print(" ");
i've also checked that both recovery partition and recoverybak partition are the same size, about 41MB, so twrp should fit.
Flashing with dd, according to the TWRP website can be done with
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/soc/624000.ufshc/by-name/recovery
so replacing "recovery" with "recoverybak" should do the job.
tremalnaik said:
I've prepared this script for flashing: considering it's the first time I mess up the updater-script for such an essential part of the system, can you confirm if it is correct, considering I'd put the TWRP image in the zip as recovery/recoverybak.img ?
i've also checked that both recovery partition and recoverybak partition are the same size, about 41MB, so twrp should fit.
Flashing with dd, according to the TWRP website can be done with
so replacing "recovery" with "recoverybak" should do the job.
Click to expand...
Click to collapse
Sorry, looks like you are more knowledgeable on the subject as I don't even know what all that code means. :crying: Any other people know?
The bottom one should work as far as I can tell. If it doesn't, it should throw an error.