Hello to all.
I just create my rom, but being new to Nexus, I am faced with a real worry.
My rom is flashable but there is an error during the flash and the boot.img is not taken into account.
Roma pass all the same.
I verified several times my update script and another, there is no problem.
I also took tested for other update script Roma differente, always the same worries.
I changed boot.img, but still the same problems.
So I need for this problem, the help of a renowned developer, who can give me a lesson.
I built a lot of Roma, s3, s4, LG G2 without any worries.
for that, I really do not understand.
need help.
fraternally.
HERE IS THE MESSAGE TWRP
" set perm: some changes failed
E: Error executing updater binary in zip / sdcar.....
Error flashing zip '/scard/wprshiprom.zip
updating partition details....
HERE IS MY ROM based on the latest official firm:
https://mega.co.nz/#!ecsUiYyQ!X0zuswEe75bEfZpfWJuPuviVaiy8_CMLhOwcLnslmSE
I repeated, changing update, binary or otherwise, I always get this error, so I turn around ...
Roma will flash the kernel anyway but remains on the former.
BROTHER DEVELOPER, I need your shoulder to support me, 2 nights I do not sleep.
You're using an outdated updater-binary I believe. Test a newer one
Sent from my Nexus 5 using Tapatalk
Sorry but if I'm posting this message, I tried the basic things.
I even tried to take a completely different folder META-INF
but without success.
so I need a real help, a detective will answer,
I provided the rom.
Sorry my language, i am french
:crying::crying::crying:
Related
I have an unlocked xperia z3 d6603 I bought brand new in january I believe. I just today rooted and installed recovery but am stuck on the 23.0A.2.93 tft rom which it shippped with. It would have normally been running unrooted the latest rom from sony which was just pushed out a couple months ago. I'm in california and need a rooted d6603 generic global rom, or even unrooted, and I can't seem to find the down link here. In xpreifirm 3.6a latest, I keep getting a java error so can't use that and I've already uninstalled and installed the latest 64bit java8 update 40. I was going to just flash it with the moonwalker rom but it days I need to be on a different tft altogether. Any help here would be appreciated. I have installed a firewall, changed dns servers, and uninstalled a few things using rom toolbox. Hoping to just update it to the recent tft or even better, a working custom rom which won't mess up the default phone capabilities. I'm on kitkat 4.4.4, at&t lte, rom 23.0.A.2.93
Again I need a rooted global generic 577 tft for a z3, a nonrooted one, or even better, a custom one I can just flash to it so I can get back to my life.
since you have a working recovery just flash this one 23-0-1-5-77-deodexed-zipaligned it's the latest KK
ps: I'm on AT&T in CA as well and running that firmware just fine for a while now, it's generic global so no worries...
awesome. THANKS. Gonna try it now. Been at it all day from like 10am to about 5 when I had to break
How do you flash a zip file
tweker said:
awesome. THANKS. Gonna try it now. Been at it all day from like 10am to about 5 when I had to break
Click to expand...
Click to collapse
I rebooted with TWRP in recovery mode, reset device (Wipe Data, Cache and Dalvik Cache), saw no way of flashing from recovery mode. Shut phone off. Plugged in in flash mode with the zip file in the firmwares folder and it was not recognized by flash tool. Where are the directions for flashing a zip?
Choose the second option in recovery
Install custom zip
I used NDR to reboot into recovery. The zip was on both internal and external at root. First time I selected the one from internal and it gave no errors. Wiped cache and rebooted and still on stock 93. Did the exact same thing again choosing zip on sd card and it still says 93. Third time I did it from sd card but no cache wipe. Still on23.0.A.2.93. WTF???
Where can I find a working ftf. NDR doesn't work for ****. BTW, phone is setup in dev mode with mock, airplane mode etc with supersu free working. I think
BTW, why in the hell does the thread with all the roms not have any current ones???? rooted or not
What for are you trying to flash? Please provide a link.
What does the recovery log say? It really helps if you tell us this.
FTF files are geberally not uploaded anymore as it is very easy to download any you want from the sony servers and create your own FTF using flashtool and Xperia firm.
Ps, it may be nice to watch your language. The issue is not NDR, it works fine.
I'm using D6603_23.0.1.A.5.77_deodex.zip from here: http://forum.xda-developers.com/z3/development/deodex-23-0-1-5-77-deodexed-zipaligned-t3015178 on top of D6603_23.0.A.2.93_Generic_20GLOBAL.ftf which was rooted and dual recovered. I have flashed the above 5.77 zip file like 5 times from recovery mode and still on 93. This last time I noticed I had no file mgr. Installed es, mounted system rw like it says to do after root, reflashed the 77 deodexed zip, wiped dalvik and cache, reupdated supersu zip in recovery, rebooted, and stil on93. What am I doing wrong? Is there not a dern ftf file I can use instead? OR, should and could I just wait for another official update?
tweker said:
I'm using D6603_23.0.1.A.5.77_deodex.zip from here: http://forum.xda-developers.com/z3/development/deodex-23-0-1-5-77-deodexed-zipaligned-t3015178 on top of D6603_23.0.A.2.93_Generic_20GLOBAL.ftf which was rooted and dual recovered. I have flashed the above 5.77 zip file like 5 times from recovery mode and still on 93. This last time I noticed I had no file mgr. Installed es, mounted system rw like it says to do after root, reflashed the 77 deodexed zip, wiped dalvik and cache, reupdated supersu zip in recovery, rebooted, and stil on93. What am I doing wrong? Is there not a dern ftf file I can use instead? OR, should and could I just wait for another official update?
Click to expand...
Click to collapse
That is not a ROM file, it does not contain a ROM. It just deodex's your system files if you are on that firmware.
And, No, there is not a FTF you can flash that is rooted. FTF files have to be completely stock as we cannot sign them with Sony's keys as we do not know them. The only way to flash something rooted is via recovery
Post#2 told me I could flash the zip over and it would work. No wonder it doesn't work because it doesn't do anything. I don't want to unlock boot because I may fail official updates. I really just want to update to a working global generic 77 rooted dual recovered system. So basically even if I had the official 77, unrooted, I still couldn't use (nor root) it right? Thanks for the help. I at least know to go another route.
tweker said:
Post#2 told me I could flash the zip over and it would work. No wonder it doesn't work because it doesn't do anything. I don't want to unlock boot because I may fail official updates. I really just want to update to a working global generic 77 rooted dual recovered system. So basically even if I had the official 77, unrooted, I still couldn't use (nor root) it right? Thanks for the help. I at least know to go another route.
Click to expand...
Click to collapse
Post #2 is wrong. Also the thread stated in the first line that a requirement for that to work is that you are already on .77 firmware.
There is no need to unlock your boot.
Just flash a .77 prerooted ROM.
If you cannot find one then make one yourself. Follow the guide in the thread called PRFCreator (Just google it)
Once you have the files downloaded it takes 7 minutes and it is all automated for you
Thank You Very Much. At present I have access to two pc's. One is my roomies (win8.1) and mine (win7). My roomies has some sort of java issue and xperifirm fails right when you click the file you want. Tried fixing java didn't work. Mine is wireless, dns disabled, mac changed, hosts file, and tiny wall fw. Experifrm says no net access even though it works fine. Tried a cable and for the life of me got the same error (couldn't quite reconfigure it to work correctly-pita). If I ever get the file I will do the prfcreator magic, and I'm assuming, flash it through ndr tools in recovery mode. In the mean, I might request an xda user in another thread to grab one for me and post it. Should help lots of people not just me. Again, thank you for your help, saved a lot of hair pulling.
tweker said:
Thank You Very Much. At present I have access to two pc's. One is my roomies (win8.1) and mine (win7). My roomies has some sort of java issue and xperifirm fails right when you click the file you want. Tried fixing java didn't work. Mine is wireless, dns disabled, mac changed, hosts file, and tiny wall fw. Experifrm says no net access even though it works fine. Tried a cable and for the life of me got the same error (couldn't quite reconfigure it to work correctly-pita). If I ever get the file I will do the prfcreator magic, and I'm assuming, flash it through ndr tools in recovery mode. In the mean, I might request an xda user in another thread to grab one for me and post it. Should help lots of people not just me. Again, thank you for your help, saved a lot of hair pulling.
Click to expand...
Click to collapse
Sorry about the confusion, indeed the first link that I provided was just a patch to deodex your room (I always use deodex so I can mod my rom)....anyway you can use this one it's a generic prerooted .77 from the z3 android development section in this forum, then you can patch it with the other one if you have the need to...just follow the instructions in this link and you should be on your way
Again sorry about that first post, I rooted my phone the minute root was available on locked bootloader so it's been some time now
I have been to that link. The only one I can see that says generic global is the 23.0.A.2.93 one. The others say, Generic_DE, Generic_NCB, or Generic_AU. Which looks to me like Deutch, Generic Nordic?, and Australian? Since I speak english and am nowhere near any of those places, I did not touch them. Which one is safe to use and will there be any post config for my locale and radios?? Plus I have no clue what the purpose is of de-odexing the file system (flashing that zip) does. I still have read write issues with apk's I install when I tell them to use my 128gb sd card. I did recover my setup prior to the zip flash you pointed me to which I still have-thank you.
tweker said:
I have been to that link. The only one I can see that says generic global is the 23.0.A.2.93 one. The others say, Generic_DE, Generic_NCB, or Generic_AU. Which looks to me like Deutch, Generic Nordic?, and Australian? Since I speak english and am nowhere near any of those places, I did not touch them. Which one is safe to use and will there be any post config for my locale and radios?? Plus I have no clue what the purpose is of de-odexing the file system (flashing that zip) does. I still have read write issues with apk's I install when I tell them to use my 128gb sd card. I did recover my setup prior to the zip flash you pointed me to which I still have-thank you.
Click to expand...
Click to collapse
1) its called a FTF file not a TFT file. It's a FlashTool File.
2) your sd write card issues are a feature of KK, and nothing to do with any error or bug to do with your phone. Just Google KK write to sd card to read more about it and how to circumnavigate this issue that was deliberately introduced by Google.
3) i have read some of the advice you have banded about in several of the thread here. Some of it is just plain wrong. Although not dangerous to anyones device it may be worth reading and learning a bit more first.
4) please stick to asking questions in just one thread, there is no need to ask in several thread because the first time you did not get an immediate answer
5) you can safely flash a FTF from any region as long as it is for the same model you have. Especially as you are only going to be on that version for a few minutes whilst you root them immediately upgrade.
Ok, great. I'll grab the de one. As for not trying to help; I put down what worked for me. If I don't know everything I can still give input with the little I know. That's how people learn, myself incl. I just got my pc running not two weeks ago so a little overwhelmed with having just rooted as well. Thanks very much for all your help.
tweker said:
Ok, great. I'll grab the de one. As for not trying to help; I put down what worked for me. If I don't know everything I can still give input with the little I know. That's how people learn, myself incl. I just got my pc running not two weeks ago so a little overwhelmed with having just rooted as well. Thanks very much for all your help.
Click to expand...
Click to collapse
No worries. I did not mean to imply that you should not help, only that you should be sure that what you are saying is in fact correct information.
We do all have to learn, but its hard to learn when incorrect information is posted and stated as "fact"
Greg
From install to booted took 4 min. Just had to update supersu and remove a few things. This is awesome! NDR Utils is worth paying for. Now I can finally encrypt my phone. TYSM
I still have bootloop issue on my oneplus one, running on Cyanogen.
First, I know nothing about developping, I have been self teaching myself over the past 2 days to solve this frustrating bootlopp issue on my oneplus one.
2 days ago I didn't know what was TWRP and adb and fastboot, I have downloaded Android SDK for developpers, Java plateform in between because it was (uselessly) needed, I have flashed images (TWRP), not knowing what flashing was about and not knowing TWRP, randomly following up scattered (and uncomplete) tutorials of forumers writing mysterious and random terms of totally unknown notions for me as a normal user.
This been written, please be clear in your answers, honestly please, maybe some readers may understand how frustrating it can be to read so called tutorials in vocabulary that only developpers can get.
So here what I did so far
1) flash TWRP with fastboot
2) Then I tried entering "make_ext4fs /dev/block/mmcblk0p15". Many posts refer to this as the ultimate solution. (I cannot post link since I am new forumer)
a) First from command, shift+right click in my "adb" folder:
"adb shell" + "make_ext4fs /dev/block/mmcblk0p15"
Didn't work
b)Then I retried in TWRP directly on my phone, going in Advanced>Terminal Command>Select, then type: make_ext4fs /dev/block/mmcblk0p15
Didin't work
3) update the system
Also, I have an update available in my android system, hoping that it could solve the bootloop. When I update, it reboots and goes to TWRP boot mode, is that normal ? If yes what am I suppose to do ? Can an update system actually solve this bootloop issue ?
So far it doesn't solve my bootlopp issue.
What do you think ? What else can we do ?
Have you tried installing (flashing) custom firmware? Go to Cyanogenmod.org, or google "Cyanogenmod 12.1 for oneplusone download", look around, download the custom firmware (Rom) should be a .zip file, move it to your phone, then install it. I can help you more if you need.
Sent from my iPhone using Tapatalk
Hey, thanks for your answer. I ll try later this week and I ll keep you informed.
Just one detail: when flashing cyanogen 12.1, does it mean I completely wipe out my phone to reinstall the rom? (As far as I understand it's like formating a computer and reinstalling window )
there after an cyanigen update. I tried and wiped out my data and so far It works. Very simple, no more than 5min (I spent hours on this problem up to now)
For other readers try this.
If not well try MeowDude advice.
Special note : it looks like update doesn't work though, when it reboots I end up on TWRP and get a message at the end of the update "file md5 not found ". A future problem oncoming? Hope not
So far everything works anyway.
And thanks to MeiwDude
Hello everyone, I hope I'm writing in the right section.
I'll go straight to the issue: after finally deciding to install a custom rom on my device (HUAWEI GX8), i decided to opt for this one: https://forum.xda-developers.com/moto-g4-plus/development/rom-aospextended-rom-v3-0-t3537792
The first problem i had to face was the "ERROR:7" (so the rom seemed to be made for a different phone than mine) that occured while installing the rom in the twrp, but being that the rom was specifically made for my phone I followed this guide: https://www.youtube.com/watch?v=wed03948gcg and fixed the issue, resulting in a perfect installation... or so I thought.
After rebooting, the phone didn't start the os but was stuck in the twrp (I tried rebooting multiple times and in different ways of course).
Being that I had made a backup before installing the new rom, I decided to restore that backup from the twrp... but still the phone is stuck in the twrp and I don't know what to do :crying:
I hope somebody can help me because I'm starting to panicking.
Cheers in advance.
PS: I'm a complete newb so this was the first time I installed a custom rom, I tried searching for this problem online but couldn't find a solution that fitted me. I hope I won't ask too many stupid questions.
SlimeAndroid said:
Hello everyone, I hope I'm writing in the right section.
I'll go straight to the issue: after finally deciding to install a custom rom on my device (HUAWEI GX8), i decided to opt for this one: https://forum.xda-developers.com/moto-g4-plus/development/rom-aospextended-rom-v3-0-t3537792
The first problem i had to face was the "ERROR:7" (so the rom seemed to be made for a different phone than mine) that occured while installing the rom in the twrp, but being that the rom was specifically made for my phone I followed this guide: https://www.youtube.com/watch?v=wed03948gcg and fixed the issue, resulting in a perfect installation... or so I thought.
After rebooting, the phone didn't start the os but was stuck in the twrp (I tried rebooting multiple times and in different ways of course).
Being that I had made a backup before installing the new rom, I decided to restore that backup from the twrp... but still the phone is stuck in the twrp and I don't know what to do :crying:
I hope somebody can help me because I'm starting to panicking.
Cheers in advance.
PS: I'm a complete newb so this was the first time I installed a custom rom, I tried searching for this problem online but couldn't find a solution that fitted me. I hope I won't ask too many stupid questions.
Click to expand...
Click to collapse
The ROM that you flashed was NOT made specifically for your device, you have HUAWEI GX8, the ROM was made for Moto G4 Plus. You would have know this if you had looked at the forum it was posted in. It was posted in in the Moto G4 forum, not in a Huawei forum.
The "fix" that you used didn't help.it successfully flash, it only help you "force" the ROM to flash. You bypassed a safety measure that was designed to keep you from flashing the wrong thing, now you're dealing with the results of forcing it to flash on a device it wasn't meant for.
Learn to pay attention to what you are reading.
You need to flash your stock firmware to fix this.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
The ROM that you flashed was NOT made specifically for your device, you have HUAWEI GX8, the ROM was made for Moto G4 Plus. You would have know this if you had looked at the forum it was posted in. It was posted in in the Moto G4 forum, not in a Huawei forum.
Learn to pay attention to what you are reading.
You need to flash your stock firmware to fix this.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I'm sorry I may have linked the wrong page, either way on the website of the rom I downloaded the right thing, I'm sure about it because I checked it multiple times (the error I made in writing the post may be cause by me panicking, sorry :crying: ).
While waiting for answers I installed a different twrp and it WORKS! I'm so happy I could cry. Thank you nonetheless for your help (Still dunno what the problem was though xD)
@SlimeAndroid as you installed ROM of different phone, it might not get installed as ROM zip contains script for Mobile verification.
I assume you had wiped /system and after installation of wrong ROM you rebooted your phone without reading if TWRP said you don't have any OS installed or what. (That means you have ran without any OS, that may be reason why you stuck with TWRP.)
But after Restoring Backup of Working ROM, it should boot your device, but it doesn't.
We (on G4 plus) have faced issue: when phone start, it always goes to TWRP/recovery instead of booting to system.
Are you facing similar ?
Solution for this problem was to clear bootloader data, by using fastboot commands (i assume you know how to do, otherwise ask for better explanation )
Run this two commands from Comand Prompt
-> fastboot oem fb_mode_set
-> fastboot oem fb_mode_clear
This worked for us. You can try, if doesn't work then flash Stock ROM.
____Mdd said:
@SlimeAndroid as you installed ROM of different phone, it might not get installed as ROM zip contains script for Mobile verification.
I assume you had wiped /system and after installation of wrong ROM you rebooted your phone without reading if TWRP said you don't have any OS installed or what. (That means you have ran without any OS, that may be reason why you stuck with TWRP.)
But after Restoring Backup of Working ROM, it should boot your device, but it doesn't.
We (on G4 plus) have faced issue: when phone start, it always goes to TWRP/recovery instead of booting to system.
Are you facing similar ?
Solution for this problem was to clear bootloader data, by using fastboot commands (i assume you know how to do, otherwise ask for better explanation )
Run this two commands from Comand Prompt
-> fastboot oem fb_mode_set
-> fastboot oem fb_mode_clear
This worked for us. You can try, if doesn't work then flash Stock ROM.
Click to expand...
Click to collapse
If you read the post above yours, you'll see they solved the issue.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
You always have to make sure the download is for your model of phone(settings -about) and always make sure the download has properly downloaded and I use md5 checksum as this verifies the download is not courupt.
Sent from my iPhone using Tapatalk
Hi everyone,
I'm a little in trouble and I'd need some help 'cause I'm getting an headache.
I temporary have to use a Galaxy S Duos 2, and given its really old OS I tried to flash it with something more recent. Problem is, there is something weird in the device preventing me to flash it.
In short, I'm stuck on two problems:
1) All the resources I've tried are either for the GT-S7580, kylepro, single SIM or for the GT-S7582, kyleprods, dual sim. Guess what? Mine is a GT-S7582, kylepro, dual sim. What the hell?
2) All the roms I've tried fail during the installation 'cause of an error on the sha1 of the system folder. I've tried everything, wiped the folders in the suggested order, restored the file system...nada.
So, any idea what's going on, and how to get out of this situation? I'd absolutely need to make the device work, but I'm clueless. I've even thought to reinstall the stock rom, but I've got no idea which version is the correct one for my device version.
Uh, just to add as much info as I can: I'm using Odin3 v3.12.10 and TWRP 3.2.1-0-kylepro
Help, please?
Well, exactly like last time I posted and asked for some help, I got totally ignored. Luckily, after a while yesterday I've done some thinking and I've found the possibile cause of the problem, tried and...yes, it worked; posting here in case someone else would ever find itself stuck on something similar in the future.
In short, the root of the problem is that for whatever reason the phone was thinking to be a kylepro instead of a kyleprods. I tried to correct the build.prop file, but there is no chance to do it from inside TWRP so I ended up tweaking the updater-script file. The procedure is explained on line in different sites, I cannot give a link as the forum system does not allow me to do it.
you can post the link with a minor mentioned edit, would be helpful for others who might face the same in future
So, I wanted to root my device in order to modify games, but haven't ever encountered Custom URL's before, so I decided to watch a YouTube tutorial, not realising that it was several months out of date.
So, the tutorial took me to Odin, and a custom ROM, which I then *tried* to install. Damned thing wiped my device with a "Verification failed" message. So the next morning, I reset my device as I couldn't find a way around it, I then tried to install Majisk v16.0 using TWRP. Though this seemed way easier than installing the custom ROM, I have had a lot of trouble with the installation of the .zip file, due to my earlier failures with the custom ROM.
TWRP keeps giving me the error:
! Boot image patched by other programs!
! please restore stock boot image
Updater process ended with ERROR: 1
Error installing zip file ' /sdcard/Magisk-v16.0.zip '
Other XDA threads have pointed me in the direction of a stock boot.img file, but I cannot seem to find one for my device (Since most of the threads with this problem are over a year old, and many updates have occurred since then).
Anyway, I am looking for either a link to an updated boot image, or a possible solution to this problem.
Thanks in advance.
Largestella said:
So, I wanted to root my device in order to modify games, but haven't ever encountered Custom URL's before, so I decided to watch a YouTube tutorial, not realising that it was several months out of...
Thanks in advance.
Click to expand...
Click to collapse
I kinda did the same thing with my S7 edge before. I believe you havent turned on OEM unlock so you got the error while flashing with Odin. Now i have installed GALAXY 8.0 rom on my s7. It comes rooted, with magisk, custom kernel. Everything you set up in aroma.
As for twrp part i used this https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
After installing twrp, flash rom with it. Hope that helps.
https://androidfilehost.com/?fid=24591020540823532
This is the link I got myself a boot.img
Used it on 935F, also im not responsible if you mess up your device even more but it worked for me.
BTW its worth mentioning my s7e using exynos
Cheers for this, this seems way more logical than what I have been trying to do. I will try this now.
Thanks