Lately, I've been trying to flash 3 custom roms on my ace.
Everytime I was dissapointed to see a status 7 error in CWM.
First, I thought it was something in the particular rom that i'd tried to flash. But when I tried to flash PAC rom this morning, I started to think whether it might be caused by my current rom: CM9 final from Mclaw.
At first, I've tried to flash the cm7.2 rc3 blackhawk/firekernel roms. One suggestion that was made by someone was that It might me a problem to flash cm7.2 over cm9. He advised me to try to flash stock again and then try again.
But I've tried to flash pac rom this morning, and again, I received a status 7 error. I cannot believe that it is just bad luck that I download roms with errors in the updater-script.
Is it possible there is some incompatibility flashed by cm9 so other roms cannot be flashed right now?
please, close/delete topic. I've tried to delete it myself.
Posted the question in the Q&A section....
Related
Hi,
I wish to revert back to cm 7.2 from cm10. I wasn't able to find a conclusive thread which could help with the same. I tried wiping and flashing cm7.2 using CWM but later realized it only flashes update packages. Since cm10 is more updated, nothing happened except a format. Kindly help me with this. I am having lots of trouble with cm10 and its affecting my work
princegoyal88 said:
Hi,
I wish to revert back to cm 7.2 from cm10. I wasn't able to find a conclusive thread which could help with the same. I tried wiping and flashing cm7.2 using CWM but later realized it only flashes update packages. Since cm10 is more updated, nothing happened except a format. Kindly help me with this. I am having lots of trouble with cm10 and its affecting my work
Click to expand...
Click to collapse
I think the smartest way is get back to a stock GB rom using smartflash so you can root, mount a cwm and flash cm7.2 based on that old bootloader
Hello!
I'm new to posting to this forum, so you can call me a noob. I'm sure I am a noob, I'm sure I did something wrong. I was just a customer for the time when GingerDX development started for Xperia X8, my previous phone. I'm not a dev, but I know know to flash stuff and what to avoid or do with care. If this thread is in the wrong section, then sorry, please move it where it should be.
Three months ago I got my new shiny GT-I9305, version for Poland (distributed by Plus), and as I did with my X8 previously, I decided to root it and dive into flashing many custom ROMs.
I made the EFS backup following lyriquidperfection's thread (http://forum.xda-developers.com/showthread.php?t=1946915), so my IMEI and NV items are safe and secure. I also did a backup of a stock 4.1.2 ROM.
I was using many different ROMs and kernels from XDA, both based on CM10.1 and Official Samsung ROM. I had PhilZ Touch 5 recovery installed. Everything worked fine, until I noticed something strange:
After I flashed an unofficial port of SlimBean to I9305 (http://forum.xda-developers.com/showthread.php?t=2297679), and Yank555 kernel for CM10.1 based ROMs, I noticed that in "About phone" section, my phone is shown as "GT-I9300", but I'm 100% sure I flashed the file that had I9305 in the filename, so it couldn't be my mistake. I didn't buy I9305 for 4G, but for 2 GBs of RAM, so I couldn't test if LTE was working (My carrier is T-Mobile.pl, which doesn't have 4G in Poland yet), but I didn't see the option to even search for LTE networks available. I didn't care much about that, since everything else was working just fine.
I decided to flash the previous ROM I was using - Sentinel Rom, because I found the bug with GPS and I wanted to see if the same happens in that rom. I rebooted to recovery, but... I couldn't install the package. It was all giving the "set_perm some changes failed (status 7)" error all the time. The same happened when I tried to install LiquidSmooth for i9305. I just couldn't flash any 4.2.2 ROM, I was able to flash a kernel just fine.
I decided to flash Ripper Rom instead. It installed with no error, it just said: "Root access is missing, root the device?" so I simply said to root it. But the phone couldn't normally boot. It stayed for a while at the "Samsung Galaxy SIII GT-I9305" splash screen with the little red exclamation mark in the top left corner, then it kept rebooting back to recovery. I had no idea what's going on. Wiping data/cache/dalvik cache/system didn't help at all. The only way to make the phone working again was to recover SlimBean from Nandroid backup I had done previously. Sadly, I had no Sentinel Rom backup. Deleted it. Shame on me.
I successfully restored Stock 4.1.2 rom from the nandroid backup, but I still couldn't install any custom ROM via recovery because of the same error.
After several tries to install different ROMs, redownloading everything and going through a lot of stress I gave up. I installed TriangleAway, reset the flash counter and, through Odin, flashed tar.md5 of the stock ROM delivered by Plus, downloaded from here: http://goo.gl/SMWEha. I installed a version build XXBLL3, which later updated itself to XXBMB4, and baseband updated from XXBLL3 to XXBMA2.
Right now, I have Official, Stock 4.1.2 ROM from Plus, with Baseband version I9305XXBMA2, build number JZO54K.I9305XXBMB4 and stock kernel.
What Download mode says:
Product Name: GT-I9305
Custom binary download: No
Current Binary: Samsung Official
System Status: Official
Now to the questions:
Why this started happening? Was the reason the wrong model of the phone in "About phone", hence installing SlimBean?
When I flashed the stock ROM, does it mean that I'm fully back to stock, with everything removed? Does it mean that my phone is like I got it from the box, with warranty? The recovery seems stock as well.
Can I root it again? If yes, how to do it safely, to not make something like that happen again?
Baseband got updated. Does it mean I have to make an EFS partition backup again?
Sorry if I ask too much, but I'm a very careful person, and I want to know everything before I start doing anything risky with my smartphone.
Thanks in advance.
General thread read the basics all stickied .
jje
I read every sticky thread and I can't find the answer to my questions. That's why I'm asking.
When I flashed the stock ROM, does it mean that I'm fully back to stock, with everything removed? Does it mean that my phone is like I got it from the box, with warranty? The recovery seems stock as well.
That is answered in the how to return to stock for warranty thread .
Root again yes follow the instructions .
EFS again that is in the faqs and guides no you dont have to but its safer to do so .
Why this started happening >>> User error who knows where as multiple roms stuff flashed .
jje
I rooted the phone again using the Galaxy S3 toolkit and every time I try to install the custom ROM through TWRP I get the error:
set_perm: some changes failed (status 7)
Then the phone doesn't want to boot (reboots to recovery all the time), only a restore of a Stock 4.1.2 from nandroid backup helps.
Ideas?
Seriously? Anyone?
Flashing 4.1.2 ROM (Ripper Rom) gives the same exact effect. Rom flashes correctly, but the phone cannot boot into system, reboots to recovery.
I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Jeffril said:
I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Click to expand...
Click to collapse
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
NoDze said:
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
Click to expand...
Click to collapse
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Jeffril said:
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Click to expand...
Click to collapse
Okay, This is SFSP by @sgspluss which is a pretty fast, stable and battery-friendly slimmed down version of stock ICS. It is available for both Old and NewBL, so you might want to try that first. This is AIO Toolkit. I know that you've used it and bricked your phone, but try again, and for the love of God install the nvflash drivers because most people skip that part. You have to do it manually and if you're running Windows 8 you need to disable Driver Signature Verification. But yeah, you switch bootloaders with this.
Hi all!
First sorry if this is not the right Forum.
I have flashed many roms In my xt1502
But by now it does not matter the ROM i try, WiFi will not work
I am using clockmod recovery.
Thanks of backup i can still keep using pac-man ROM but none of the other roms based on CM11
Thanks for your help.
I have googled and the answers are not clear
I have tried to change kernels and recovery but issues remain still!
When flashing CM12 based ROM, WiFi works again... So i guess the problem is the build?
Solution
Thanks to myself...
I solved the problem: install TWR 2.6 version, then factory reset. Version 2.8 of TWRP makes sometimes "update binary" error.
You must install a ROM based on any CM11 before 20141104, and then you always do a dirty flash of later version of the choosen rom
I guess there must be something ROM in The versions of cm11 after that date, at least form xt1502 model.
I wanted to bring my phone back to life just to run some updated apps so i tried to install several roms in my phone but i always get status 7 error. The only one it worked so far was Mackay 2.999 but i wanted to try Marshmallow but not even Lolipop i could flash. I already followed some tips like removing the assert line from the updater-script file but it was worthless. I also read that it may be a problem related with recovery version so i tried looking for PhilZ Touch but it looks like there isnt any download link available so right now im using twrp 2.6.0.0 from Mackay build. Sorry if I repeated a thread but i looked in the forum and i havent seen any problem solved.