What is the most convenient way to downgrade ICS to cm7?
Thanks
When I was trying out earlier BETAs (teamhacksungs BETA 8 and 9) I just booted into recovery and flashed my 2.3.5 ROM like I would anything else. But this was before they started implementing separate kernels and bootloaders and whatnot, so I'm not sure if the process is the same =/
Turns out one can simply restore an earlier nandroid! Now anyone else wondering knows
Hi Guys
bit of a newb her, I tried to flash a jellybean rom and after doing plenty of research followed the instructions to the letter. The result was that it didnt work and reverted back to honeycombe 3.2. The problem i have is that it no longer allows me access or set up my google account and some buttons such as the home button no longer seem to work. I have been unable to go back to stock and am lookign for a little guidance.
I did carry out a factory reset.
Kies is also not recognising my tablet.
I apologise for starting a new thread if this has been asked before. I have not seen an identical problem on this forum so far
Did you make a backup in cwm recovery for the stock honeycomb before flashing the jellybean? And what method did you use to revert back to stock?
For the factory reset, did you do it after reverting back to stock or before?
Sent from my GT-P7300
x24 said:
Did you make a backup in cwm recovery for the stock honeycomb before flashing the jellybean? And what method did you use to revert back to stock?
For the factory reset, did you do it after reverting back to stock or before?
Sent from my GT-P7300
Click to expand...
Click to collapse
I did do a backup in CMW recovery. The flash to jellybean didn't failed. It took a few minutes and then restarted and booted up as 3.2. The factory reset and wipe cache partition were carried out as per the instructions online prior to installing the zip file.
I'm just hoping it is possible to resolve this problem.
thanks for any help
Just to provide an update. I have now resolved the problem
After trying to factory reset my tab then became stuck was stuck on the galaxy tab screen. Using the stock rom for 3.2 found here http://forum.xda-developers.com/show....php?t=1483168 i was able to flash this using Odin and much to my relief it booted up again in 3.2.
Much to my amazement once it was flashed onto my device and booted up i was able to get an OTA update to ICS 4.0.4 which was a bit of a suprise. Not sure how or why this happened but i am very pleased with the result. ICS is a huge improvement from honeycombe and is like having a new tablet. It is so much smoother and more responsive.
I was using CWM 5.2.0.4
Since you have figured out how to resolve the problem please change the title from [Q] to [solved] this way if someone else has a similar problem they will know that they can find a answer here.
Sent from my Nocturnalized One XL using Forum Runner
To start this is not my phone but my girlfriend's brother's phone. I have a Samsung Galaxy SII on Sprint and am used to rooting and flashing with Samsung phones. It has never been rooted or anything and all these problems started after the ICS OTA.
The problems that are occurring are there constantly apps that give the message "Unfortunately [APP] has stopped." including ones that are not in use and gapps. So I figured I could fix this with a factory reset by going to settings and factory reset. That didn't work so I tried in recovery mode and that did not work either. I moved on to using RSD to flash an unrooted stock rom. I have tried 905, 902, and 246. 246 successfully flashed but actually did nothing and reboots in the exact same state as before the flash. 905 and 902 would get stuck on step 6 of 22 of the flashing process.
Please do not flame me if I missed something or I'm using the incorrect terms or whatever. I'm just trying to get this phone fixed and any help would be appreciated.
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.
So, I'm a total newbie at android rooting but, I decided to take a shot at it a few months ago. I flashed the kernel of my Android 5.1 Note 5 to a rooted one, now, I'm about to give the phone back to T-Mobile, but I certainly want the root gone before I do that just for the sake of things going as smoothly as possible.
I didn't flash any custom roms or anything, its still the stock rom, just a rooted kernel. Would doing a simple phone reset through the normal settings put everything back to normal/unroot and get rid of that "Kernel is not seandroid, enforcing" message on boot? Or would it require just simply flashing a stock kernel back through Odin? Or something else? I really just need that damn message gone.
If need be, I have TWRP flashed as the recovery as well.
// NEVERMIND, problem solved.
how do you solved it?
I think Odin should do the trick.