Alright, before I start describing by problem I'd just like to apologize if this thread is in the wrong forum or if the thread format is wrong or something. I just registered on these forums and everything is beyond confusing for me.
Anyway, I have a rooted Samsung Galaxy S Plus (I9001) and I've been trying to flash a custom ROM [THIS ONE] but unfortunately I managed to screw up somehow. That post describes that I need CWM 6.0.4.9 in order to flash the ROM but unfortunately I "installed" (if that's the correct term? I don't know) CWM 6.0.4.5 on my phone made by the same team (ADC Team). Yes, I know, I was an idiot and I didn't read the post completely to know that 6.0.4.9 is NEEDED to flash the custom ROM.
My problem is that I now can't flash the custom ROM because of the version mismatch (the installation process results in a Status 7 error and it aborts) but I also cannot update CWM made by the same team because trying to install the 6.0.4.9 ZIP file on my phone also results in the Status 7 error. So now I'm stuck on a version of CWM that I cannot upgrade to the version required to flash the ROM and I've no idea what to do. I tried searching everywhere for a solution but I found nothing and I don't think I can upgrade the CWM by ADC Team using ODIN (couldn't find the CWM 6.0.4.9 tar.md5 file).
I'm a relative newbie on rooting phones. My other phone is a Samsung Galaxy S3 with Cyanogenmod 11 on it which I flashed without any problems so trying to flash a ROM on an older phone and getting this type of error is extremely frustrating.
This post may be a little bit lacking in information but that's because I don't know what kind of information I should provide, so I'm sorry about that, I'll try to answer questions regarding it as best as I can.
If a mod or admin thinks that this thread is in a wrong forum or if there's anything else wrong with it then please PM me so that I can fix it.
Related
I have the Docomo version of the Galaxy S, SC-02B running 2.2.1 OMKA5 build. I have rooted the phone via Superoneclick. I have read through many posts but I have not really found a solid process or even if it is possible to get 2e recovery and CWM without having sim card or modem troubles.
Also, to my knowledge custom kernel and rom flashing cause similar issues. I would really like to do more with my phone, so if anyone has had stable success could you please post your method?
V300 said:
I have the Docomo version of the Galaxy S, SC-02B running 2.2.1 OMKA5 build. I have rooted the phone via Superoneclick. I have read through many posts but I have not really found a solid process or even if it is possible to get 2e recovery and CWM without having sim card or modem troubles.
Also, to my knowledge custom kernel and rom flashing cause similar issues. I would really like to do more with my phone, so if anyone has had stable success could you please post your method?
Click to expand...
Click to collapse
Follow this link if your not a Japanese reader use Google translate http://komugi.net/archives/2011/03/07104838.php
Thank you, I appreciate the response. I can read Japanese I will check it out and get to testing it out. I am surprised for the SC-02B being most popular phone in Japan, from what I have noticed not too many ppl are really doing much past rooting
Boo, he/she is basically confirming the same issues that the users on this forum encountered with their s-02b's.... Summarized from him other than getting 2e recovery on the phone, it does nothing
Actually you can have clockwork it is just inconvinient because it takes two steps to get to clockwork instead of one. Once you have 2e just download rom manager and your off and running. I'm doing nanodriod backups almost everyday so I can recover after I've failed to make a theme work or screwed up the phone in some other way. The big problem is their are no Japanese developers work on our phone and the other dev's are reluctant to develop for a platform that they don't have to test on.
According to that link the person said Rom manager didn't work...
If it does, than be able to make nandroid backups would definitely help me out a lot. Did you use his method to get 2e recovery, or another?
I used a different method but the results are the same. Can't find the link to the one I used. When he says it doesn't work I think he means that ROM manager doesn't boot directly into clockwork it boots into recovery and then you have to apply an update zip that puts you into clockwork the very first time you do it doesn't work and you have to apply it a second time. This is clearly explained somewhere deep in the ROM manager thread.
In his post shows clockwork running and mentions how long it takes to do the backup if your running OCLF.
Thanks for helpful information.
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.
Hi, I haven't find a post with this very same problem in a N7000 phone.
Like 2 years ago I had a problem with my Note, a friend helped me and that ended up in Rooting and ParanoidAndroid 2.x.
A few weeks ago I started feeling my phone quite slow, thought it was time for a fresh start.
I downloaded the latest ParanoidAndroid, 4.x, and tried to flash it using CWM and it failed, error status 7. So I tried with 2 or 3 more roms, same luck. So I started to look for this status 7 error. Found out that I could edit the file rom/meta-inf/com/google/android/updater-script to alter the assert lines. That didn't work either.
After reading a bit more I found out about twrp, lots of users had this very same problem and twrp had solved it for them. Well, that was frustrating, there wasn't any official release for the n7000 phone. I had found a post explaining how to compile it from a linux machine, post creator's posted an .img file but just as an example, it was outdated and I don't have a linux machine here with me nor the knowledge to feel confidence on compiling.
After trying some .tar.md5 flashes with ODIN, I got frustrated 'cause they were all working. But those roms are the least, most of the new ones (P.A. included, the one I got to fall in love with), come in .zip format. So, last try, started looking for some PA ROMs in .zip format. Again, no luck.
So, I'm running out of options. I was peacefuly hoping you could guide me in the right direction. I'm no guru but after reading for 2 straight days I think I'd be able to follow any sort of steps you'd suggest to me. I honestly feel confident enough to solve this issue.
Looking forward to your input people, I'm sure you're all more versed than me in the matter!
Thanks.
The rom you are trying to flash is a kitkat rom. To flash you will need newer version of cwm or twrp recovery. As recovery is merged with kernel in note, it's not possible to update without changing the kernel. So from your current pa recovery, flash raw r4 kernel. After that reboot into recovery. This should update the Cwm recovery to 6.0.4+. Now wipe data and cache and flash the new rom.
First off, let me apologize for posting what has been semi-answered in several other threads. Im a lifer when it comes to android but still a noob at rooting and custom roms. I've been rooting for about 4 to 6months. mostly basic beginner stuff. this was my first attempt at flashing a custom rom, and well, the fact that I'm here lets you know how that went for me. So I've read 30 or more threads between this site and some others and tried a handful of methods to fix but i lack the knowledge or lingo to properly understand some of the things that I've read. So anyone kind enough to break things down barney style like a bootloop for dummies for me id be forever in your debt. Here is my issue...
Once i found out that the note 3 n900a of mine is not compatible with clockwork mod or team win recovery i found and downloaded the SafeStrap recovery and flashed the biggins custom rom and even tho i tried going by the guide i read i must have went wrong somewhere and got myself stuck in boot loop or soft brick.
I've tried downloading a stock firmware for the note 3 and reflashing with heimdall. i thought it was going to work since everything went according to the guide i read 100% but it still failed.
from reading other forums I have also downloaded these programs:
1. android studio sdk
2. Java and latest JDK 7
3. zip devil
4. heimdall suite - heimdall frontend
maybe more I've forgot.
Could anyone please help explain to me the easiest method for a beginner to recover from boot loop? I can't even get my phone to boot back into safestrap recovery. only screens i can access is stock recovery mode...adb factory reset cear cache external sd etc. and Odin download mode. When i tried using the safestrap recovery i saved to my ext sd card saved as twrp file that the program mirrors, I'm not sure if I'm loading the wrong files within this folder or perhaps the wrong order or if this recovery won't even work for me at all.
I've downloaded all of the above mentioned programs but I'm not at all familiar with properly using them to do what i need with them. Please, anyone, explain this in english to someone who isn't skilled or long term rooter. if you need any more info on my issue please contact me any way you can or ask for a way to contact me externally and ill provide that as well.
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.