Hi guys,
I have just started playing with my GSG3 lte after upgrading from a SGS1 that I rooted and put a cg7 rom on it. That was many years ago and I am just relearning how to get along with it all again.
I have managed to get CWM on it (and to stay there!!!) and have superSU on as well. I am trying to flash this kernel mentioned in the title but every time it does not stick. The old kernel remains.
I have tried clearing the cache and that dilyic cashe (or what ever it is) then flashing but to no avail. I have read the entire thread but came across nothing that helps. Do you guys have any info or ideas I can try? The phone is running the stock rom.
Here is the thread for the kernel i am trying to flash.
Android 4.3.0 AGNi pureSTOCK v3.8 NA2+
Flashing by getting into CWM, choosing the clear cache options and then flashing from the sd card.
Thanks for any help you guys may have!
Spaz.
What is your ROM base? I had the same problem until I flashed a ROM with an NA2 or greater base, then it worked fine. My suggestion, is to use Amcha's ROM.
Sent from my GT-I9305 using Tapatalk
I've been running the kernel along with xxueml9 firmware, so no <NA2 fw neccessary.
do you have latest CWM? as there are numerous posts about problems while flashing new roms/files using old recoveries
in case of problems with that I'd advise using skipsoft utility and let it find the newest compatible recovery image and let you guide through the flashing process
Ok, looks like i am running the xxuena2 rom???? It is the standard software that came with the phone. CWM version is v5.5.0.4 : CF- v1.5
It was sorted out by updating the CWM to latest version.
Thanks guys for the replys and help.
Related
Hey guys, sorry if this a dumb question but I am not sure if flashing stock firmware is good enough to remove all evidence of rooting and such since I dont know what exactly happens in the process of rooting / flashing.
I just realized I have an hardware issue but I already rooted my GN using zergrush v4 and flashed the CF-Root kernel after that (using the already-rooted.bat by CF).
Someone wrote something about simply flashing stock firmware so I
- flashed stock firmware (full firmware, not only kernel)
- rebooted twice
- used every factory reset / wipe option stock offers in recovery mode
- booted and reformatted internal sd after unmounting it
(Yes I seem to be blind or stupid because only after I did that I saw I could have simply flashed stock kernel and used unroot script...)
For a noob like me it seems like it did the trick, I am not rooted anymore, SU, CWM... are gone but I just want to be sure there aren't any traces anymore.
Thank you in advance for answers (hopefully).
You should probably flash the stock recovery as well. As soon as they boot into recovery they will know.
Edit: guess I should have read it more thoroughly, I see you don't have cwm anymore.
Sent from my LG-P999 using XDA App
Thanks for the reply rogerski1, I already checked before you edited and it is stock.
There is so much to read and learn for a first time android device owner and since there are a lot of contradicting statements all over the threads (concerning wipes and such) it is hard to guess who is right or wrong and if I understood it right, so I had the urge to ask.
Thank you, gotta go to sleep.
From what I understand, a flash of a complete ROM, including the kernel, should get rid of Clockwork Recovery, because CWR is stored in the kernel.
From what I understand the kernel is like the engine. The rom is the car. Overclocked kernels will make your car run faster and better. The recovery maybe a repair shop? Flashing a rom and kernel will still leave you with a custom recovery. Its there in case **** goes wrong. Fwiw, I am not a developer or programmer at all, just an android enthusiast.
Sent from my LG-P999 using XDA App
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,
at first i try to post in the related thread, but i havn't enough posts to do this.
http://forum.xda-developers.com/galaxy-s3/development-i9305/rom-beta-t2535996
After flashing the latest ROM my phone can't get a network connection. Wifi works. I used CWM 6.0.4.7, SlimKat Build 3.6 and the latest gapps from SlimRom (Build 3). I can't receive baseband, network, phone number or IMEI in the settings. All is unknown. Also when the phone starts, it doesn't ask for my PIN.
Re-install doesn't work. Another SIM doesn't work, too. CM 10.1.3 works fine.
Model: GT-I9305
Provider: Vodafone
Baseband: I9305XXUEMK1
Some ideas?
That is not a rom problem, for sure.. What can I say, you are doing everything right, but I might recommend using Philz recovery, I've never had any problem with it. Reboot recovery, full wipe and then flash
Try to flash with Odin latest stock 4.3 kernel and then try again with wiping everything before.
Hey guys,
thanks for your advices. I wasn't at home, so I couldn't response or even try it.
Today I flashed the new SlimKat 3.8 (still with CWM) and it works Maybe it was a problem with the ROM.
Thanks anyway :good:
Druffbold said:
Hey guys,
thanks for your advices. I wasn't at home, so I couldn't response or even try it.
Today I flashed the new SlimKat 3.8 (still with CWM) and it works Maybe it was a problem with the ROM.
Thanks anyway :good:
Click to expand...
Click to collapse
For sure it was problem with ROM. Actually with radio ROM, not the Android itself.
Make a backup of your ROM and save radio image from it.
Then you can flash some other ROM you like and flash this working radio image after that.
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.
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.