Hi guys,
New user here. I am not sure if this is the right way to reach the developers for Omni ROM but I hope it is.
I've recently started using Omni ROM and I absolutely love it. On January 18, 2014 you fixed a major problem I was having; having to re-root my phone manually after each update. However, my other issue is that system updates do not automatically flash itself on my phone.
I originally didn't know why, but I found out after installing Philz recovery and seeing the error log that the ROM was searching for OpenDelta\ROM.zip when it should be searching for sdcard\OpenDelta\ROM.zip in order to flash the update automatically.
I am using a Samsung S3 (i9300), if that makes a difference. I would love to see this issue resolved and I hope I can be of further help in the future.
NotSoNewbie said:
Hi guys,
New user here. I am not sure if this is the right way to reach the developers for Omni ROM but I hope it is.
I've recently started using Omni ROM and I absolutely love it. On January 18, 2014 you fixed a major problem I was having; having to re-root my phone manually after each update. However, my other issue is that system updates do not automatically flash itself on my phone.
I originally didn't know why, but I found out after installing Philz recovery and seeing the error log that the ROM was searching for OpenDelta\ROM.zip when it should be searching for sdcard\OpenDelta\ROM.zip in order to flash the update automatically.
I am using a Samsung S3 (i9300), if that makes a difference. I would love to see this issue resolved and I hope I can be of further help in the future.
Click to expand...
Click to collapse
Use TWRP and everything will be fine....It updates OTA
Nope, no such luck.
TKokab said:
Use TWRP and everything will be fine....It updates OTA
Click to expand...
Click to collapse
I use to love TWRP, I guess I still do, but there hasn't been an update to it in a while and version 2.6.3.0 has never been able to load an Android 4.4.2 based ROM. Whenever I tried it with CM11, it would boot once and then go into a boot loop after rebooting (all the time, and I tried for weeks). I just tried using TWRP to load an Omni ROM nightly (omni-4.4.2-20140121-i9300-NIGHTLY.zip) and got that error you get if you use an earlier version of CWM before 6.0.4.4 (set_metadata_recursive: some changes failed).
Then after trying the above I went back into a boot loop, so I had to use Odin to flash a CWM recovery I had and re-flash Omni to get it to boot again. TWRP needs a new version before I try it again.
TWRP has a 4.4.2 compatible version, I'm using it with OMNI ROM and it's 4.4.2 version. See their site:
http://teamw.in/project/twrp2
Sent from my Nexus 10 using XDA Premium HD app
NotSoNewbie said:
I use to love TWRP, I guess I still do, but there hasn't been an update to it in a while and version 2.6.3.0 has never been able to load an Android 4.4.2 based ROM. Whenever I tried it with CM11, it would boot once and then go into a boot loop after rebooting (all the time, and I tried for weeks). I just tried using TWRP to load an Omni ROM nightly (omni-4.4.2-20140121-i9300-NIGHTLY.zip) and got that error you get if you use an earlier version of CWM before 6.0.4.4 (set_metadata_recursive: some changes failed).
Then after trying the above I went back into a boot loop, so I had to use Odin to flash a CWM recovery I had and re-flash Omni to get it to boot again. TWRP needs a new version before I try it again.
Click to expand...
Click to collapse
that does not seem typical at all.
I'd guess you're having some other problem than the twrp version number.
bleggy said:
that does not seem typical at all.
I'd guess you're having some other problem than the twrp version number.
Click to expand...
Click to collapse
Not so sure that is true. Thanks to +3DSammy, I went searching for an update and found 2.6.3.1 through the Goo manager app. Now I am installing Omni ROM without a hitch:good: So I guess I'm gonna stick with TWRP once more. But my initial problem still remains: System updates are looking in the wrong place for the ROM download and needs to be completed manually.
I'm sure the developers will sort that out soon, unless I'm the only one with this problem.
"Bug report"
Woke up this morning and both of my omni devices (Note N7000 and Tab2 10.1 P5100) urged me to flash the update, which was ready to be installed. Already downloaded, patched and verified,everything done - I simply had to tap "flash now".
Excellent stuff! Amazing. ?
Why is my phone locking itself randomly? O.O hope this gets to the devs.
P.S. is there a site to report bugs? I'll love to bookmark that site and report a bug every other day.
Smack that Thanks button if I helped!
KitKat came in on my OmniROM, running on my Note 2.
Sent from a small country called Singapore.
P.S. Time for school, not much time for XDA
Irwenzhao said:
P.S. is there a site to report bugs? I'll love to bookmark that site and report a bug every other day.
Click to expand...
Click to collapse
http://jira.omnirom.org/
Truely
AA1973 said:
"Bug report"
Woke up this morning and both of my omni devices (Note N7000 and Tab2 10.1 P5100) urged me to flash the update, which was ready to be installed. Already downloaded, patched and verified,everything done - I simply had to tap "flash now".
Excellent stuff! Amazing. ?
Click to expand...
Click to collapse
The issue is truley resolved for me too. Who do I thank??? Awesome work guys. Updating is a breeze now. Just click flash now and wait.
Update would not flash
I have recently started facing the update problem which was till earlier a breeze - go to system update and click flash now and it was a cake walk. But since the update of 21st Jan for N7000, i click flash now and I go into reboot but nothing happens.
TWRP opens and i reboot but still updates would not install!!!
Any suggestions!!!?
twrp needs to be set at the internal sd or opendelta folder. you have yours set to open the external.
bleggy said:
twrp needs to be set at the internal sd or opendelta folder. you have yours set to open the external.
Click to expand...
Click to collapse
Can you guide me how to reset the same in TWRP - new to all this.
many thanks,
Z
I9505 update
I:command is: 'set' and I:value is: 'tw_signed_zip_verify 1'
Setting function disabled in CWMR: 'tw_signed_zip_verify' to '1'
I:script line: 'install OpenDelta/omni-4.4.2-20140130-jfltexx-NIGHTLY.zip
'
I:command is: 'install' and I:value is: 'OpenDelta/omni-4.4.2-20140130-jfltexx-NIGHTLY.zip'
Installing zip file 'OpenDelta/omni-4.4.2-20140130-jfltexx-NIGHTLY.zip'
E:unknown volume for path [OpenDelta/omni-4.4.2-20140130-jfltexx-NIGHTLY.zip]
-- Installing: OpenDelta/omni-4.4.2-20140130-jfltexx-NIGHTLY.zip
Finding update package...
I:Update location: OpenDelta/omni-4.4.2-20140130-jfltexx-NIGHTLY.zip
E:unknown volume for path [OpenDelta/omni-4.4.2-20140130-jfltexx-NIGHTLY.zip]
E:Can't mount OpenDelta/omni-4.4.2-20140130-jfltexx-NIGHTLY.zip
Installation aborted.
E:Error installing zip file 'OpenDelta/omni-4.4.2-20140130-jfltexx-NIGHTLY.zip'
Done processing script file
I:setting up /data/media(/0) for /sdcard.
I:using /data/media/0 for /sdcard
Camera Bug
Love the ROM. Most stable I have had on the i337M. I have noticed at least since the Jan 27 nightly the following bug. If the phone goes to sleep or if you hit the power button when in the camera app you will lose connection to the camera. You have to force close the camera and reboot to get it back. I reloaded my nandroid from jan 7 and still the same.
Zeusrocks said:
Can you guide me how to reset the same in TWRP - new to all this.
many thanks,
Z
Click to expand...
Click to collapse
its easy.
just reboot into twrp
browse to opendelta folder
or just internal.
reboot system.
if the last folder you were in
was your external or whatever
the update script wont run.
Sometimes on my GT-N7000 (which has the latest Omnirom 4.4.2 2014-01-31), when I'm listening to music (either on the buildt in app or the PowerAmp) my phone randomly crashes and reboots. This can occur once a day if I'm listening to music. But the music app themselves can also crash, and to fix it I must stop the processes in the settings menu to be able to play again. Does the occur for anyone else?
Thanks
ProShifu said:
Sometimes on my GT-N7000 (which has the latest Omnirom 4.4.2 2014-01-31), when I'm listening to music (either on the buildt in app or the PowerAmp) my phone randomly crashes and reboots. This can occur once a day if I'm listening to music. But the music app themselves can also crash, and to fix it I must stop the processes in the settings menu to be able to play again. Does the occur for anyone else?
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2612329
@bleggy
Sorrry for being a noob, but do you use install to browse to the omnirom folder? Auto flash is still not working for me.
twrp>install>select storage:internal>opendelta>reboot
Related
http://android.clients.google.com/p...553.signed-soju-GRH78-from-GRH55.a71a2082.zip
Download the OTA package here
Rename it to update.zip, and place it on the root of your internal storage
Shut down your phone, and reboot into the bootloader by holding volume up and powering back on
Choose "recovery" from the list, and select it with the power button
When you see the red triangle press volume up and choose to update
Credit Gbhil for the file
IF YOU ARE ON CWM:
Just got an Android 2.3.1 update for Nexus S. It's on ROM manager if you want it. Make sure you flash recovery 3.0.
Also, for this to work you must be on Stock Recovery. This will not flash properly if you are using clockwork recovery
momohammed20 said:
Also, for this to work you must be on Stock Recovery. This will not flash properly if you are using clockwork recovery
Click to expand...
Click to collapse
Correct. Koush is currently looking at fixing this for CWM.
Can we try to update and flash the zip using adb?
This was just tweeted:
Just got an Android 2.3.1 update for Nexus S. It's on ROM manager if you want it. Make sure you flash recovery 3.0.
edit nevermind got update
I just got prompted OTA for this update. Anyone know it I was to accept it, would I have any problems since I changed my recovery to ClockWork recovery?
I know it's been said it's on rom manager now, I am just curious if there would be any potential problems of accepting OTA updates with the stock recovery gone.
I have cwm recovery flashed and looked in Rom manager but is getting that "the rom you are using does not support ota updates etc" How did you manage to get Rom manager to update it to GRH78??
ive tried every way listed on xda but still get a "error 7" when trying to flash the update. i am using stock rom with clockwork 3.0. anyone having the same issue or any way to fix it?
usb disabled?
Got the message from Google to update. So I let it do its thing, said unable to update zip and now seems my usb connection is broken. Any help will be greatly appreciated. I'm on NS despite my sig Also on CWR 3.0 unlocked
are we supposed to be able to install this 2.3.1 update that we download from rom manager?
nsavani said:
ive tried every way listed on xda but still get a "error 7" when trying to flash the update. i am using stock rom with clockwork 3.0. anyone having the same issue or any way to fix it?
Click to expand...
Click to collapse
Koush is gonna repackage it later tonight for those with error 7
demo23019 said:
are we supposed to be able to install this 2.3.1 update that we download from rom manager?
Click to expand...
Click to collapse
How did you get it to download? I hope Koush gets CWM to play nice with the updates.
yungfresh said:
How did you get it to download? I hope Koush gets CWM to play nice with the updates.
Click to expand...
Click to collapse
Well there is very little info in OP
and could be worded little better to avoid confusion
You have to put on Wifi and go to download ROM for some reason if you on on mobile network it wont show the update in rom manager
Dont bother it wont. From what i gathered we have to wait for modified version
Download the zip, choose to open with rom manager and it will flash fine with cw recovery 3.0.0.
Sent from my Nexus S using XDA App
dirk1978 said:
Download the zip, choose to open with rom manager and it will flash fine with cw recovery 3.0.0.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
not for me
demo23019 said:
Well there is very little info in OP
and could be worded little better to avoid confusion
You have to put on Wifi and go to download ROM for some reason if you on on mobile network it wont show the update in rom manager
Dont bother it wont. From what i gathered we have to wait for modified version
Click to expand...
Click to collapse
Got great news! I got it to work! All I did was put the .zip file on the root of my sd and used Rom manager to "download rom" chose the .zip file and voila!! It installed everything fine. I am officially on GRH78. Hope that helps people out!
is this with the paid version or non-paid?
the CWM update will work of you have not used Koush's rooboot.img and are running a the rooted boot.img.
He said he will release a version later tonight that should work with rootbootimg installed as well.
glad im on stock recovery + root.
Many of us are facing this problem where after flashing a 10.2 ROM and rebooting, the device is stuck at boot screen- the Samsung N7000 screen!
This is a strange problem which seems to be affecting only some n7000 handsets as others can keep flashing the ROMs without any issues...wiping, reflashing ROM, etc doesn't work!
I myself faced this problem on almost all custom CM 10.2 Roms and am sharing the solution which worked for me. At the onset, this solution was suggested to me by another member @Super Prince in one of my posts and it worked!!
1. Reboot into recovery
2. Flash the correct gapps once again
3. Reboot
The problem should be gone now and no more stuck-iness for you...
Sent from my GT-N7000 using XDA Premium 4 mobile app
I tried that, and it did not work.
I'm not using the regular Gapps package, but this one:
http://forum.xda-developers.com/showthread.php?t=2012857
What package do you use?
knedge said:
Many of us are facing this problem where after flashing a 10.2 ROM and rebooting, the device is stuck at boot screen- the Samsung N7000 screen!
This is a strange problem which seems to be affecting only some n7000 handsets as others can keep flashing the ROMs without any issues...wiping, reflashing ROM, etc doesn't work!
I myself faced this problem on almost all custom CM 10.2 Roms and am sharing the solution which worked for me. At the onset, this solution was suggested to me by another member @Super Prince in one of my posts and it worked!!
1. Reboot into recovery
2. Flash the correct gapps once again
3. Reboot
The problem should be gone now and no more stuck-iness for you...
Sent from my GT-N7000 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Really? I'll try it next time when I flash some CM based ROM and will get this problem.
I hope it is really the reason.
SirRhor said:
I tried that, and it did not work.
I'm not using the regular Gapps package, but this one:
http://forum.xda-developers.com/showthread.php?t=2012857
What package do you use?
Click to expand...
Click to collapse
Which CM version are you on? This method has worked for me every time on CM 10.2 roms and official CM 10.2 gapps (the one dated 13/08/2013)
I used to get stuck on the GT N7000 screen after every reboot and resorted to all sort of stuff like reflashing, formatting and stuff but to no avail.
The only solution that worked for me was re-flashing the gapps!
Maybe you should try once again with the official gapps..and post your results.
jakuburban said:
Really? I'll try it next time when I flash some CM based ROM and will get this problem.
I hope it is really the reason.
Click to expand...
Click to collapse
The 'Reason', my friend, remains a mystery...
This solution, though worked!
Experienced developers might like to comment on this as to what might be the reason
knedge said:
Which CM version are you on? This method has worked for me every time on CM 10.2 roms and official CM 10.2 gapps (the one dated 13/08/2013)
I used to get stuck on the GT N7000 screen after every reboot and resorted to all sort of stuff like reflashing, formatting and stuff but to no avail.
The only solution that worked for me was re-flashing the gapps!
Maybe you should try once again with the official gapps..and post your results.
Click to expand...
Click to collapse
I'm on Carbon, but I tried another CM based ROM as well and it did not work.
I will try it with the official Gapps and Slim Gapps then report back.
EDIT 1: Well. I tried the lastest Carbon nightly 10/17, with both Slim Gapps and normal regular Gapps and the same result, stuck on boot logo.
Both times I flashed a clean install. I'm out of options now.
EDIT 2: When I'm using a kernel from 4.3 and I'm on CWM trying to format Preload, I always get this message:
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
Error formatting /preload
Could that be a possible reason?, does anyone else have that same message?
No suggestions?
Am I'm stuck on 4.2?
Sent from my GT-N7000
It's the same for all on the new Cwm. Preload cannot be formatted in Cwm 10.2.
What happens when you clean install a rom without gapps. And boot it.?
nokiamodeln91 said:
It's the same for all on the new Cwm. Preload cannot be formatted in Cwm 10.2.
What happens when you clean install a rom without gapps. And boot it.?
Click to expand...
Click to collapse
I tried that last night actually, clean flash and no Gapps and the same result, stuck on boot screen.
What I've tried so far:
- Flashing different 4.3 ROMs with three different Gapps combinations.
- Flashing Carbon with no Gapps.
Thank you in advance for any ideas you can provide.
I have never encountered such an issue after a clean flash ever. So not sure what's going on there.
When a clean install, do you format system, data and cache and then install the new rom?
nokiamodeln91 said:
I have never encountered such an issue after a clean flash ever. So not sure what's going on there.
When a clean install, do you format system, data and cache and then install the new rom?
Click to expand...
Click to collapse
Yeah, what I do is to do a factory reset twice, then clear cache, then preload twice, data once, system twice and dalvik twice, and only then I flash the ROM and then Gapps.
I let it settle for one hour and then I start the configuration.
It is weird, because if I leave it to boot up normally for the first time, without opening any apps or configurations, it reboots normally. And only when I open Settings or an app, and then I reboot the phone, it gets stuck on the boot logo.
I've even tried to format the SD Card and no difference.
tried without the external SD card inserted?
nokiamodeln91 said:
tried without the external SD card inserted?
Click to expand...
Click to collapse
No, gonna try that tonight.
EDIT 1: Tried lastest Carbon nightly with NO Gapps and no External SD Card. Same crap.
EDIT 2: I found this thread and it basically says that I have to flash Stock, then root it and then do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2427569
Sent from my GT-N7000
SirRhor said:
No, gonna try that tonight.
EDIT 1: Tried lastest Carbon nightly with NO Gapps and no External SD Card. Same crap.
EDIT 2: I found this thread and it basically says that I have to flash Stock, then root it and then do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2427569
Sent from my GT-N7000
Click to expand...
Click to collapse
@SirRhor Please try anothjer work-around before you do anything else:
1. Do all the wipes from a safe kernel
2. Flash Rom (only rom and no gapps)
3. Reboot the system without gapps
4. Now, reboot into recovery (I prefer to leave the system for 10-15 minutes to settle down before rebooting)
5. Flash the correct gapps
6. Reboot and set up ur google account etc.Restore apps or whatever u need from the play store. Dabble with rom settings
7. Reboot!
Did it work now?
knedge said:
@SirRhor Please try anothjer work-around before you do anything else:
1. Do all the wipes from a safe kernel
2. Flash Rom (only rom and no gapps)
3. Reboot the system without gapps
4. Now, reboot into recovery (I prefer to leave the system for 10-15 minutes to settle down before rebooting)
5. Flash the correct gapps
6. Reboot and set up ur google account etc.Restore apps or whatever u need from the play store. Dabble with rom settings
7. Reboot!
Did it work now?
Click to expand...
Click to collapse
I haven't tried that yet, I'll do it tomorrow, but I really doubt it's going to work. I think this whole problem it's caused by errors located on some blocks of memory.
Sent from my GT-N7000
SirRhor said:
I haven't tried that yet, I'll do it tomorrow, but I really doubt it's going to work. I think this whole problem it's caused by errors located on some blocks of memory.
Sent from my GT-N7000
Click to expand...
Click to collapse
Well, can be!
Much abused handset...and much loved too!
But do give it a try!
SirRhor said:
No, gonna try that tonight.
EDIT 1: Tried lastest Carbon nightly with NO Gapps and no External SD Card. Same crap.
EDIT 2: I found this thread and it basically says that I have to flash Stock, then root it and then do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2427569
Sent from my GT-N7000
Click to expand...
Click to collapse
maybe your bootloader corrupted already. Reflash the bootloader only or whole stock rom using ODIN may help ..
I'm glad to inform you that I was able to solve my problem following this guide:
http://forum.xda-developers.com/showthread.php?t=2427569
But instead of flashing the Stock Rooted ROM using Odin, I just flashed it within Philz Recovery.
Right now I'm changing settings and restarting on Carbon 4.3, and so far I have not had any problems.
To anyone experiencing this, just read this thread so you will not waste your time trying ALL the bullcrap I did and instead just try the guide above.
Thank you for everyone who helped me out.
EDIT: Maybe the OP can change the title of this thread to "FIXED" or "SOLVED".
So...which Stock Rooted ROM using to flash?...
heihei123 said:
So...which Stock Rooted ROM using to flash?...
Click to expand...
Click to collapse
Actually, I found a better more permanent solution.
Follow this guide to check for errors on the different partitions:
http://forum.xda-developers.com/showthread.php?t=1396366
Let me know if it helps.
And to answer your question, I flashed a stock ROM from Hungary I think, no problems.
EDIT: Forgot to mention, instead of using the switches described on that guide, I used -f and -y at same time.
Sent from my GT-N7000
Hey guys,
strange thing happened to me yesterday.
After I got fed up with Paranoid, I decided to pick one of the other AOKP derivatives.
Although I had initial problems with mounting sdcard1, I somehow managed to flash from there
and do have SOKP with android 4.4.4 running on my honami
the thing is, when I want to access recovery through vol+ or vol-, my phone freezes on boot,
otherwise everything is working fine.
Unfortunately I need to flash GAPPS and I need to find some kind of workaround...
What I have tried is flashing TWRP and Z1DualRecovery via fastboot with no success.
Any ideas?
Thanks in advance
What is SOKP? Any link you can give us?
Did the kernel for that ROM include a recovery?
TWRP cannot be installed via fastboot on xperia devices. Z1dualrecovery kernel is for stock based roms only.
Maybe you should flash a FTF and start again.
you have unlocked bootloader, let flash pimp kernel to have working recovery, so you can reflash the rom to check it.
Sent from my C6903
gregbradley said:
What is SOKP? Any link you can give us?
Did the kernel for that ROM include a recovery?
TWRP cannot be installed via fastboot on xperia devices. Z1dualrecovery kernel is for stock based roms only.
Maybe you should flash a FTF and start again.
Click to expand...
Click to collapse
SOKP is Sonic Open Kang, a newer AOKP derivate.
It is one of the top posts in Android Development Forum.
Thought you heard of it.
Ok thanks will try it with pimped kernel. Hope it works with AOKP.
lauchrecords said:
SOKP is Sonic Open Kang, a newer AOKP derivate.
It is one of the top posts in Android Development Forum.
Thought you heard of it.
Ok thanks will try it with pimped kernel. Hope it works with AOKP.
Click to expand...
Click to collapse
I have seen it now, try flashing and wiping again
Hey, thanks for the fast response guys.
So I've just flashed Pimped Kernel to this ROM
http://forum.xda-developers.com/xperia-z1/development/xperia-z1-t2834169
I am still getting stuck on boot when I'm trying to get into recovery.
Neither vol+ not vol- works, I hit it when the purple light flashes and the orange one comes up and stays like forever.
So unfortunately I cannot flash nor wipe.
And Android without GAPPS kinda sucks... especially when they have the new material design...
EDIT: And I don't want to stay on pimped kernel cuz it somehow causes battery drain for me...
Only possibility would be to somehow install the zip via ADB/Fastboot... does that work somehow?
Just keep pressing it throughout the boot sequence, don't forget you have to press, let go, press, let go etc..... Its not just one long press
gregbradley said:
Just keep pressing it throughout the boot sequence, don't forget you have to press, let go, press, let go etc..... Its not just one long press
Click to expand...
Click to collapse
Just tried that out, in both directions.
Same result - no success.
Really unusual since it was always a long press and I should also be getting into the recovery
by rebooting into recovery from inside the ROM.
What other possibilities are there to get gapps on your phone?
lauchrecords said:
Just tried that out, in both directions.
Same result - no success.
Really unusual since it was always a long press and I should also be getting into the recovery
by rebooting into recovery from inside the ROM.
What other possibilities are there to get gapps on your phone?
Click to expand...
Click to collapse
push them with adb
but that's not the point
have you booted into system and check to see if quick boot is enabled in developer options - root
gregbradley said:
push them with adb
but that's not the point
have you booted into system and check to see if quick boot is enabled in developer options - root
Click to expand...
Click to collapse
I dont seem to have that option,
all I have is the point "Update CM Recovery when installing system updates"
@gregbradley how do I push and flash those via ADB?
Check in the gapps zip where each file should be installed (Proabably all to system/app) and the associated permissions (Should be 0755 or 0644, I don't have time to check just now)
Then put all the files in the same folder where you have adb installed.
then
Code:
adb push "[I]name of file here[/I]" system/app/"[I]name of file here[/I]"
adb chmod 0755 system/app/"[I]name of file here[/I]"
Replace the name of the file with the extension where I have said, change the "0755" to "0644" if that's what it says in the updater script, and if the apks should be installed somewhere else (for example syste/priv-app) change the commands to that.
This method would take you a long time, proabably best to just push the play store and then download the google apps you want, or better still, fix your recovery
Ok guys, many many thanks for your help.
I solved the problem and got my recovery back.
I flashed PhilZ and I like it. Way better than regular CWM.
You can close the thread now.
Hello, yesterday I got for OTA (Samsung Tab 3 SM-T210R) upgrade to Kit Kat. I can´t do any test, but it gives the feeling that everything runs faster
chris1871 said:
Hello, yesterday I got for OTA (Samsung Tab 3 SM-T210R) upgrade to Kit Kat. I can´t do any test, but it gives the feeling that everything runs faster
Click to expand...
Click to collapse
only issue so far is that it wont let you install custom ROM's, After flashing a Custom ROM it just reboots back into recovery.
hello
first off cool but i think this needs to go some where else maybe wrong
sorry to be annoying i just dont want u to get yelled at if its in the wrong place
bnb25 said:
only issue so far is that it wont let you install custom ROM's, After flashing a Custom ROM it just reboots back into recovery.
Click to expand...
Click to collapse
Just don't reboot into recovery from any software.
Turn off the Tab and enter recovery with the 3 keys method (power+volume up+menu) and you will be able to flash anything in recovery and reboot into system.
Just DON'T EVER reboot into recovery using the "reboot into recovery" option on any software including power menu.
I have this issue for a long time, even when I was on 4.1.2 and that is how I got rid of the problem.
---------- Post added at 05:44 AM ---------- Previous post was at 05:41 AM ----------
[/COLOR]
RockasKane said:
Just don't reboot into recovery from any software.
Turn off the Tab and enter recovery with the 3 keys method (power+volume up+menu) and you will be able to flash anything in recovery and reboot into system.
Just DON'T EVER reboot into recovery using the "reboot into recovery" option on any software including power menu.
I have this issue for a long time, even when I was on 4.1.2 and that is how I got rid of the problem.
Click to expand...
Click to collapse
those reboot options work just fine before Upgrade to kitkat. I booted into recover from the off position. the first time after reinstalling recovery.
bnb25 said:
---------- Post added at 05:44 AM ---------- Previous post was at 05:41 AM ----------
[/COLOR]
those reboot options work just fine before Upgrade to kitkat. I booted into recover from the off position. the first time after reinstalling recovery.
Click to expand...
Click to collapse
But the first time you installed the update you rebooted via software command, right?
If you boot into recovery from off with the three buttoms... you can flash the 4.4.2 and it will load into system.
Just don't reboot into recovery via software command.
Test it.
chris1871 said:
Hello, yesterday I got for OTA (Samsung Tab 3 SM-T210R) upgrade to Kit Kat. I can´t do any test, but it gives the feeling that everything runs faster
Click to expand...
Click to collapse
I did the upgrade on my device no problems GOT ROOT then had issues. After root any changes ie: install zip, backup
The unit would get stuck in recovery mode. Recoveries tried TWRP, PhilZtouch, CWM
SDcard issues were fixed with Nextapp SDfix after root
Anyone having any other issues?
RockasKane said:
But the first time you installed the update you rebooted via software command, right?
If you boot into recovery from off with the three buttoms... you can flash the 4.4.2 and it will load into system.
Just don't reboot into recovery via software command.
Test it.
Click to expand...
Click to collapse
My [ROM] SM-T210R 4.4.2 Kitkat root via UPDATE-SuperSUv1.94.zip
Thanks for your tip I now can install zips without recovery boot loop.:good: That was a major issue with the new Samsung 4.4.2 update.
Next issue I'm working on is boot-animation. Tried [Aroma] boot-animation (no luck), ROM toolbox Pro boot-animation (no luck)
Since trying I now have no boot-animation. Next step I shall try and push the zip to get something..
The new 4.4.2 is very fast otherwise.:good:
andrewhall said:
My [ROM] SM-T210R 4.4.2 Kitkat root via UPDATE-SuperSUv1.94.zip
Thanks for your tip I now can install zips without recovery boot loop.:good: That was a major issue with the new Samsung 4.4.2 update.
Next issue I'm working on is boot-animation. Tried [Aroma] boot-animation (no luck), ROM toolbox Pro boot-animation (no luck)
Since trying I now have no boot-animation. Next step I shall try and push the zip to get something..
The new 4.4.2 is very fast otherwise.:good:
Click to expand...
Click to collapse
Give NoleKat a try... it is based on stock 4.4.2 and it has the kernel fix that brings back the boot animation.
You can find it here: https://www.androidfilehost.com/?w=files&flid=17472 Download V1.8
here's the topic: http://forum.xda-developers.com/galaxy-tab-3/development-7/rom-port-nolekat-v1-0-t210r-t2837338
RockasKane said:
But the first time you installed the update you rebooted via software command, right?
If you boot into recovery from off with the three buttoms... you can flash the 4.4.2 and it will load into system.
Just don't reboot into recovery via software command.
Test it.
Click to expand...
Click to collapse
no. I booted into recovery while the phone was off. 3 key Combo.
Ok, sorry to hear that.
The workaround seems to work with everybody, thats why I asked.
RockasKane said:
Give NoleKat a try... it is based on stock 4.4.2 and it has the kernel fix that brings back the boot animation.
You can find it here: https://www.androidfilehost.com/?w=files&flid=17472 Download V1.8
here's the topic: http://forum.xda-developers.com/galaxy-tab-3/development-7/rom-port-nolekat-v1-0-t210r-t2837338
Click to expand...
Click to collapse
Thanks Again RockasKane [NoleKat] is by far the nicest smoothest rom I have tried to date!
andrewhall said:
Thanks Again RockasKane [NoleKat] is by far the nicest smoothest rom I have tried to date!
Click to expand...
Click to collapse
Great!
But you must thank @gr8nole... Great and hardworking guy and all the development crew that contributed with great fixes
I am only just new and have been playing around with this custom rom stuff for a short while now, I have ClockworkMod Recovery v6.0.4.7 on my I9305T. I have tried a few different Roms so far but they don't work. I tried just today "RevolutionaryS5-V3" it obviously went through the installation process but did not boot into it, just came up with the samsung default ( samsung S III GT- I9305T ) logo in white. It disappeared then came back looping that way.
So now I have went into the "Advanced Menu" and then "show log" I don't know if this will help you but, it displayed this:-
ClockworkMod Recovery v6.0.4.7
persist.sys.root_access=1
persist.radio.adb_log_on=1
persist.radio.add_power_save=1
persist.radio.apm_sim_not_pwdn=1
service.adb.root=1
keyguard.no_require_sim=true
telephony.lteOnGsmDevice
mobiledata.interfaces=pdp0,wlan0,gprs,ppp0
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file no
t found...
I:Can't partition non mmcblk device: /devices/pl
atform/s3c-sdhci.2/mmc_host/mmc1
The roms I have downloaded are:- aicp_i9305_lp-10.0-RELEASE-20150708 (this one looped its boot logo), cm-11-20150907-NIGHTLY-i9305 (i have the recovery .img for this), cm-12.1-20150926-NIGHTLY-dogo (i have the recovery .img for this), FlashingDroid_S5_v2.2 and RevolutionaryS5-V3, if these roms are any good for my I9305T, Can anyone give me some advise on what or how to install these roms.
Regards,
Wayne
Something went wrong while flashing rom or maybe the rom data is corrupt.
Bootloop means your device fails to boot if system data is corrupt by flashing rom
You had soft brick.
Reboot into recovery and restore the stock rom if you had nandroid backup.
Sent from my MT27i using XDA mobile app
RevolutionaryS5-V3? that one is not for the i9305 unless i have missed a thread for it. The roms for your phone can be found here http://forum.xda-developers.com/galaxy-s3/development-i9305
but as stated flash stock rom again, flash custom recovery and then choose the rom for your phone
Hey Piyush,
Initially I did try do a Backup using Titanium Backup app, first try I think there wasn't enough room on the internal HDD, so I tried on the external HDD which I thought had done so.. So when I came to this problem, the backup did not work.
Now at first before I rooted the phone. It was done by odin v1.85 and of course it did root. So I know it has superSU, but I can't get onto a stock rom for this phone because of my **** sat internet bandwidth and also a good site to download from. I tried the samsung-update site, but the 2 links don't allow me to finish the download. Do you know of any links that i can download the stock rom for my i9305T my phone was running android v4.3. The link I just stated was for v4.3.
Can you give me some advise on how or what I should do?
Regards,
Wayne
wane72 said:
I am only just new and have been playing around with this custom rom stuff for a short while now, I have ClockworkMod Recovery v6.0.4.7 on my I9305T. I have tried a few different Roms so far but they don't work. I tried just today "RevolutionaryS5-V3" it obviously went through the installation process but did not boot into it, just came up with the samsung default ( samsung S III GT- I9305T ) logo in white. It disappeared then came back looping that way.
So now I have went into the "Advanced Menu" and then "show log" I don't know if this will help you but, it displayed this:-
ClockworkMod Recovery v6.0.4.7
persist.sys.root_access=1
persist.radio.adb_log_on=1
persist.radio.add_power_save=1
persist.radio.apm_sim_not_pwdn=1
service.adb.root=1
keyguard.no_require_sim=true
telephony.lteOnGsmDevice
mobiledata.interfaces=pdp0,wlan0,gprs,ppp0
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file no
t found...
I:Can't partition non mmcblk device: /devices/pl
atform/s3c-sdhci.2/mmc_host/mmc1
The roms I have downloaded are:- aicp_i9305_lp-10.0-RELEASE-20150708 (this one looped its boot logo), cm-11-20150907-NIGHTLY-i9305 (i have the recovery .img for this), cm-12.1-20150926-NIGHTLY-dogo (i have the recovery .img for this), FlashingDroid_S5_v2.2 and RevolutionaryS5-V3, if these roms are any good for my I9305T, Can anyone give me some advise on what or how to install these roms.
Regards,
Wayne
Click to expand...
Click to collapse
The phone was v4.3 before i rooted the phone. Do i need to flash the stock v4.3 rom again or can i use the older v4.2 or newer v4.4 to reflash the recovery?
regards,
wayne
maultasche said:
RevolutionaryS5-V3? that one is not for the i9305 unless i have missed a thread for it. The roms for your phone can be found here http://forum.xda-developers.com/galaxy-s3/development-i9305
but as stated flash stock rom again, flash custom recovery and then choose the rom for your phone
Click to expand...
Click to collapse
I'm not sure if you can downgrade from 4.3 to 4.2 or earlier. If the phone was running 4.3 then I'd install 4.3 or 4.4 to get stock recovery back. Then you can install a custom recovery. No need to root your phone for that.
Do you know a link that will take me to a compatible file for my GT-i9305T, I'm just not sure what to look out for. Also would you be able to give me a quick rundown/instructions on how to do this. Will I need odin, and which version will I need. Currently I have v1.85, that's what I used to start off. I really don't wanna brick this phone.
Regards,
Wayne
maultasche said:
I'm not sure if you can downgrade from 4.3 to 4.2 or earlier. If the phone was running 4.3 then I'd install 4.3 or 4.4 to get stock recovery back. Then you can install a custom recovery. No need to root your phone for that.
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...ck-rom-4-4-4-gt-i9305n-i9305nxxufni4-t2886807
there you'll find the Kitkat DBT for i9305. Will work with your phone as well. In the OP you'll find instruction on how to install this version via odin. Odin is included in the zip.
After that you put your phone into download mode again and flash the preferred recovery via odin. But don't use TWRP 2.8.7.0 from their site. That build is broken and is getting fixed atm. Either use TWRP 2.8.5.0 or latest Philz Touch. If you decide to flash a custom ROM again, make sure you're in the right forum, e.g. i9305
Thanks heaps for your help so far maultasche, I will let you know how I go with this.
Cheers,
Wayne
maultasche said:
http://forum.xda-developers.com/gal...ck-rom-4-4-4-gt-i9305n-i9305nxxufni4-t2886807
there you'll find the Kitkat DBT for i9305. Will work with your phone as well. In the OP you'll find instruction on how to install this version via odin. Odin is included in the zip.
After that you put your phone into download mode again and flash the preferred recovery via odin. But don't use TWRP 2.8.7.0 from their site. That build is broken and is getting fixed atm. Either use TWRP 2.8.5.0 or latest Philz Touch. If you decide to flash a custom ROM again, make sure you're in the right forum, e.g. i9305
Click to expand...
Click to collapse
From backup I actually meant if you had cwm and you did a nandroid backup of the stock rom from the recovery itself.
If you are getting bootloop you can easily fix it by restoring the backup.
Search on the net about recovery from soft brick and bootloops.
Nandroid backups can atleast get your device in running condition.
If you have custom recovery backup your rom first then you can flash any desired rom.
One more thing if you had flashed custom rom do not factory reset your device,this may result in soft brick.
Hope that helps!
Is your device booting now??
Sent from my MT27i using XDA mobile app
Hi Maultasche, how do I send pics from my PC of what's happening on my phone?
Regards,
wayne
wane72 said:
Thanks heaps for your help so far maultasche, I will let you know how I go with this.
Cheers,
Wayne
Click to expand...
Click to collapse
Yes, I successfully got the phone to boot up and run. I used the I9305XXUFNI3_I9305DBTFNI3_I9305XXUFNI3_HOME.tar file using the odin v3.09 and now it has asked the country and so on..
It was a bit daunting thinking if it was going to brick or fix the phone...
Thanks for your help, time and kindness for the files you gave me.
The next couple of days I will try attempt install Cyanogenmod 11. Will I need to use odin to install the recovery image, just like I did for the I9305XXUFNI3_HOME.tar file?
regards
Wayne
wane72 said:
Thanks heaps for your help so far maultasche, I will let you know how I go with this.
Cheers,
Wayne
Click to expand...
Click to collapse
You're welcome, glad it did help.
Yes, you need odin to flash the recovery again. No need to root your phone just to install the recovery, as mentioned. Then you can flash whatever ROM you'd like. One thing - although CM 11 still gets nightlies from time to time there is no maintainer left. He switched devices. If you encounter any issues which might be device related they probably won't get fixed.
Is sending pics on pc still an issue? Sorry, I wasn't online and I forgot to check the thread :/
HI Maultasche, so I have been looking at the" Resurrection-Remix-LP-v5.5.6" rom and have been downloading the files for it, but i am not sure what the "changelog" file is for or what it does. The page - forum . xda-developers.com / galaxy-s3 / development-i9305 / rom-resurrection-remix-4-4-2-kitkat-v5-t2704828 . It tells me I need these Installation Files:- ROM , Gapps & Changelog. Do you know if i can install this Rom using
CWM v6.0.4.7?
Oh, and about the send pic question, I wanted to send you a pic of the odin mode screen from my phone, but the only thing I could see was the "insert image" button. But it wanted me to enter a URL for the picture. Whats the go there?
Regards,
Wayne
maultasche said:
You're welcome, glad it did help.
Yes, you need odin to flash the recovery again. No need to root your phone just to install the recovery, as mentioned. Then you can flash whatever ROM you'd like. One thing - although CM 11 still gets nightlies from time to time there is no maintainer left. He switched devices. If you encounter any issues which might be device related they probably won't get fixed.
Is sending pics on pc still an issue? Sorry, I wasn't online and I forgot to check the thread :/
Click to expand...
Click to collapse
The change log file only shows what has been fixed and what has changed to previous builds. Nothing you need for the ROM
You only need the ROM, gapps and the recovery. Use the recovery rodman has mentioned in his post.
Insert image button? Via Tapatalk? Don't know what you mean to be honest.
Me Again, just above this message box there is the insert image icon. Doh... So now I have spotted the Paperclip icon above and now feel a **** for asking how to send a picture.. Sorry.
So again I thank you for your help, it is much appreciated.
Regards,
Wayne
maultasche said:
The change log file only shows what has been fixed and what has changed to previous builds. Nothing you need for the ROM
You only need the ROM, gapps and the recovery. Use the recovery rodman has mentioned in his post.
Insert image button? Via Tapatalk? Don't know what you mean to be honest.
Click to expand...
Click to collapse
Why won't my phone show up on Odin?
For what? Install lastest Samsung drivers and make sure Kies is not running
Need to install a ROM without a PC
Hi maultasche, Can you help me with this, I have my wife's phone which is a S3 i9305 as well. The USB connection on the phone has been damaged and so the cable can't be connected. I was wondering if I could still install the ROM without the use of a PC. Can you tell me the best software I could do this with? Also I am not sure the best way to back up the phone, not wanting to root it.
Regards,
Wayne
hi,
what ROM youre talking about? Official firmware? If you have a flashable zip yo could do that with flashfire, flashify, rashr etc. Or via custom recovery. For a custom recovery is no root needed.
As for backups depending on what you want to backup (whole system including data etc. or just apps with apps data). Without root your backup options are kind of limited. You can backup apps and app data via helium but not every app can be backed up using this tool. You could do a back up via adb but not sure how complete such a backup will be. I never did that. Or a backup with a custom recovery again. Might be the easiest way.