Related
Hi,
I am using XXLSA-UNP right now. Can i use PhilZ-cwm6-XXLSC-XJB or will i have to use PhilZ-cwm6-XXLSC-XJB-v3.99...i know that only LS should matter but just making sure if XXLSC would work or not?
Attaching screenshot
treacherous_hawk said:
Hi,
Can i use PhilZ-cwm6-XXLSC-XJB or will i have to use PhilZ-cwm6-XXLSC-XJB-v3.99...
Click to expand...
Click to collapse
What does this mean.? Both are the same. Yes you can use lsc kernel on lsa rom as well.
will i again have to do factory reset and wipe cache and all...also when ever i try to move any app using TBP to external memory and after that when i restart my phone that app gets uninstalled and have to reinstall them...is there something that could be done to avoid this?
Changing kernel does not need any kind of wipe. Apps. Moved to sd removes its icon from the home screen. This was a bug in some ics versions, and it's in JB too. So this may be resolved in the official JB
nokiamodeln91 said:
Changing kernel does not need any kind of wipe. Apps. Moved to sd removes its icon from the home screen. This was a bug in some ics versions, and it's in JB too. So this may be resolved in the official JB
Click to expand...
Click to collapse
so there is no fix till the time official JB is out? i mean someone might have tried to create a fix for this or not?
It only happens on apps that you force using tbp. The ones that give the option to be moved to sd in applications Works fine.
yes that is what happens, and i have another problem for which i do not want to create another thread, please help me with this...
i installed JB xxlsa to my frnds phone (no root), i installed PhilZ-cwm6-XXLSC-XJB...from pc odin and did factory reset and also reset system, data, cache and also clean cache and clean delvik cache...and now it is stuck on samsung logo with yellow triangle...i am able to go to recovery mode n download mode...in recovery mode it says "failed to mount exfat"...there is no external sd card...please tell me what needs to be done....
treacherous_hawk said:
yes that is what happens, and i have another problem for which i do not want to create another thread, please help me with this...
i installed JB xxlsa to my frnds phone (no root), i installed PhilZ-cwm6-XXLSC-XJB...from pc odin and did factory reset and also reset system, data, cache and also clean cache and clean delvik cache...and now it is stuck on samsung logo with yellow triangle...i am able to go to recovery mode n download mode...in recovery mode it says "failed to mount exfat"...there is no external sd card...please tell me what needs to be done....
Click to expand...
Click to collapse
Can someone help me..answer me...here is the exact error code "failed to mount exfat/dev/block/mmcb1k1p1/sd card"...
Sent from my GT-N7000 using xda app-developers app
Well if there is no (removable) extSdCard then it stands to reason that recovery will report an error when it looks for it. Yellow triangle will occur when flashing any custom kernel with PC Odin and can be removed with Triangle Away app.
JB leaks sometimes get stuck on reboot. Try installing a custom LSC version and use recovery to install zip from (non removable) internal SD card.
Sent from my GT-N7000 using xda app-developers app
In your last post you said reset system, data, cache. Does that mean format? If that's th case there is no rom on the phone to boot. You need to install a custom rom using recovery or stock rom using the download mode. :thumbup:
I missed the "system" part this time.
Sent from my GT-N7000 using xda app-developers app
you guyz were late in responding and i realised it already that already that ROM is missing and flashed ROM again..thanks to all the members of this forum...you guyz help so many people and hats off to nokiamodeln91 i usually see him as the first one to respond to any thread...(no sarcasm, i mean it)
I just got a nexus one for $35 that i plan on using mostly as an mp3 player. I rooted it using the one click method but it's still S-on. Part of my issue is that booting into recovery using CWM only works maybe 25% of the time. Not sure why that is. A couple times I've been able to flash a rom via recovery but after seeing the X screen, the phone bootloops on the next splash screen. This has happened on two GB roms - MIUI and CM 7.2.
Any guess on why this happens? One reason I want to flash a rom is that the camera doesn't work so I'm curious if it would work in a different rom.
nvillamob said:
I just got a nexus one for $35 that i plan on using mostly as an mp3 player. I rooted it using the one click method but it's still S-on. Part of my issue is that booting into recovery using CWM only works maybe 25% of the time. Not sure why that is. A couple times I've been able to flash a rom via recovery but after seeing the X screen, the phone bootloops on the next splash screen. This has happened on two GB roms - MIUI and CM 7.2.
Any guess on why this happens? One reason I want to flash a rom is that the camera doesn't work so I'm curious if it would work in a different rom.
Click to expand...
Click to collapse
Before flashing a ROM, clear cache/ dalvik-cache from recovery. If you don't do these, then you will see bootloops.
I had been doing that through rom manager but just did it through recovery. still bootlooping.
I wiped cache but did not factory reset
Sent from my Nexus 4 using xda app-developers app
nvillamob said:
I had been doing that through rom manager but just did it through recovery. still bootlooping.
I wiped cache but did not factory reset
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
If you are changing ROMs, its always advisable to do a factory reset in addition to clearing cache and dalvik. Try it
Sent from my Nexus One
Best advice is to skip ROM manager and always do everything manually in recovery, this has never been a problem for me
And just because, I would suggest using 4ext recovery as in my opinion it is by far the most superior recovery... Just saying
Sent from my Nexus 4 using xda premium
Unfortunately, I've tried flashing manually via recovery too...still bootloops
Check md5sum of ROM (maybe bad download)
Make sure you wipe fully (manually in recovery or with fastboot)
Make sure you meet requirements of ROM in op (as in you flashed gapps if needed or you have a large enough system partition etc)
Sent from my Nexus 4 using xda premium
yeah, i haven't checked the md5's but it's odd that it's happened with both official miui and cyanogenmod. i did wipe cache and dalvik. i think i'm just going to give up. i'd do a factory restore but don't want to do that because then i'd have to root my phone again. i rooted the phone using a Vista computer but now I'm back home and my computer runs windows 8. from what I can tell, installing the android SDK is kinda complicated on W8.
Factory reset is needed and will not mean you have to reroot your phone, this is something that would be done before each flash, in fact the cleaner the wipe the less chance of an issue.
Also there is no need for the SDK to root (but its easy to get for windows 8 anyway and tools such as fastboot and adb are very handy... Also there are other ways to get these tools without the SDK) but all that besides the point, these are your steps
Nandroid backup
Wipe everything as clean as possible
Flash ROM and anything else needed (gapps etc)
Reboot
This is the procedure you should follow for any ROM flash for any android and never a need to reroot in between
Best of luck
Sent from my Nexus 4 using xda premium
I really appreciate the help. the reason I mention the SDK is that my computer doesn't recognize my phone unless I install the SDK and the associated drivers. So I'd hate the wipe my phone so that I can flash a rom, but then be unable to flash a rom because I'm not rooted!
But you feel confident that if I factory reset, I won't loose root?
I factory reset daily! You'll be just fine, when you factory reset and wipe all partitions you are following the proper procedure to change roms. When you flash the new one you are sure to still have root access
Sent from my Nexus 4 using xda premium
well, did a factory reset last night but i'm still having the same problem. I'm at a loss.
Hi.
After unlocking my HTC, installing recovery and a custom ROM (ARHD 13.3) I have a problem with flashing kernels through recovery. Every time when it starts, phone reboots into system, just after the flashing starts, withough flashing the kernel. Any ideas?
Anyone? :-\ tried reflashing Rom with full wipe, tried other roms, changed the recovery...always the same.
Sent from my HTC One using Tapatalk 4
s_o_r_e_n said:
Anyone? :-\ tried reflashing Rom with full wipe, tried other roms, changed the recovery...always the same.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Sounds strange! What kernel are you trying to flash? Did you also make sure your download's MD5 is correct; could be a bad download.
Yes, md5 sum is correct. I'm trying to flash anything strange is that after full wipe and reflashing Rom I can flash anything before first boot. After first boot can't flash zip files, like Rom cleaner or kernel. Phone always reboots just after flashing starts.
Once I've found that someone had such problem and formating something through adb helped...but can't find this info again
I tried flashing almost every kernel available.
Sent from my HTC One using Tapatalk 4
s_o_r_e_n said:
Yes, md5 sum is correct. I'm trying to flash anything strange is that after full wipe and reflashing Rom I can flash anything before first boot. After first boot can't flash zip files, like Rom cleaner or kernel. Phone always reboots just after flashing starts.
Once I've found that someone had such problem and formating something through adb helped...but can't find this info again
I tried flashing almost every kernel available.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
I think Rom Cleaner should be flashed before first boot anyway, but not the kernel. Are you clearing cache and dalvik before trying to flash?
Yes. I even clean cache through sdk :-\ yep, the Rom cleaner should be flashed before first boot, but anyway it shouldn't reboot even later as I think.
Sent from my HTC One using Tapatalk 4
s_o_r_e_n said:
Yes. I even clean cache through sdk :-\ yep, the Rom cleaner should be flashed before first boot, but anyway it shouldn't reboot even later as I think.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Weird
Just for the sake of trying, a couple of ideas:
1- wipe the cache from recovery (not fastboot) and also wipe dalvik, then immediately flash kernel
2- perhaps there's a permission issue with the zip(s) / folder(s)
EDIT: perhaps you need to update recovery?
I reflashed recovery, tried CWM, TWRP...same on both think about going back to stock with RUU, then trying everything again from the start:-\
First advance...tried.
Second...U mean fixing permissions? Don't know if it's related to that problem, but of course will try.
Sent from my HTC One using Tapatalk 4
s_o_r_e_n said:
I reflashed recovery, tried CWM, TWRP...same on both think about going back to stock with RUU, then trying everything again from the start:-\
First advance...tried.
Second...U mean fixing permissions? Don't know if it's related to that problem, but of course will try.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Though I don't think custom recovery would have issues with permissions (since it's su privilege), it could be the folder where your zip files are doesnt have rw permission, and the recovery attempts to access the folder, is unable to, and therefore just reboots.
Try putting the zip file in a different directory (or maybe even the root folder) and try again.
In root folder? Don't understand where exactly...tried to place it on different locations in storage.
Sent from my HTC One using Tapatalk 4
s_o_r_e_n said:
In root folder? Don't understand where exactly...tried to place it on different locations in storage.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
sorry, what I meant was /sdcard
which recovery are you using? send the link
Latest TWRP. I found that I can't even change the permissions to any file on sd card. But I have root access:-\ also tried fixing permissions.
Sent from my HTC One using Tapatalk 4
s_o_r_e_n said:
Latest TWRP. I found that I can't even change the permissions to any file on sd card. But I have root access:-\ also tried fixing permissions.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Sorry, all out of ideas
No problem thank's for helping, will probably flash the RUU and start from beginning.
Sent from my HTC One using Tapatalk 4
Obvious question, but the kernel is for your version of Android isn't it? You're not flashing a 4.3 kernel on to 4.2.2?
of course not I'm on android 4.2.2 and flashing the 4.2.2 kernel version
---------------------------
as for now everything's ok. Frankly speaking I didn't do anything new. reflashed recovery for the third time i believe, did the full wipe also few times, flashed arhd, rom cleaner and the kernel one by one and it works...for now
---------------------------
and no..it's still the same. After first boot, I rebooted into recevery, tried to flash different zip and what....and reboot just after flashing:/ it makes me sick...:/
Thanks to one and all. I was facing the same issue of being unable to install the Bulletproof kernel on my HTC One having ViperOne 4.2.0 custom rom and TWRP 2.6.3.3 recovery.
I followed the advice here and wiped 'Dalvik cache' and 'cache' and (without rebooting) directly dirty flashed the Bulletproof kernel which did the trick.
Hope this helps someone else too.
Got the same problem. Tried with TWRP 2.6.6.3, 2.6.6.4 & actual CWM with failed tries to flash kernel,bootscreens,themes & the 360 camera fix.
Also tried to flash these recovery via fastboot and at least the m7&m7ul versions.
It happens suddenly
Btw: i'm on an tampered,unlocked hboot 1.54
Any help or ideas are much appreciated
Thesinistah86 said:
Got the same problem. Tried with TWRP 2.6.6.3, 2.6.6.4 & actual CWM with failed tries to flash kernel,bootscreens,themes & the 360 camera fix.
Also tried to flash these recovery via fastboot and at least the m7&m7ul versions.
It happens suddenly
Btw: i'm on an tampered,unlocked hboot 1.54
Any help or ideas are much appreciated
Click to expand...
Click to collapse
idky but after flashing arhd41 it seems to be better. I can flash in 90% of tries successfully...
This is my first time installing a custom ROM. The phone has been rooted for some time now. I downloaded the AOSP ROM and GAPP 2012011, and flashed both packages. I did not use any third-party software to flash, and it appears the process was successful. When the phone reboots, it hangs at the point where the glowing X (like when my Nexus 7 starts up) appears, and nothing else happens.
Where did I go wrong?
Thanks to anyone who has a suggestion.
Maybe it was a corrupted download or you forgot to wipe
DaddyRick said:
This is my first time installing a custom ROM. The phone has been rooted for some time now. I downloaded the AOSP ROM and GAPP 2012011, and flashed both packages. I did not use any third-party software to flash, and it appears the process was successful. When the phone reboots, it hangs at the point where the glowing X (like when my Nexus 7 starts up) appears, and nothing else happens.
Where did I go wrong?
Thanks to anyone who has a suggestion.
Click to expand...
Click to collapse
Did you forget to wipe your data, cache, and dalvik cache before you flashed. Also are you sure your downloads are not corrupted :cyclops:
Assuming you mean this AOSP right http://forum.xda-developers.com/showthread.php?t=2081011&highlight=aosp
I would just use Supernexus 4.2.2 plus AOIP kernel whitescreen fix or if you want 4.1 use camcorys 4.1.2 build
Also what recovery and build are you using?
Sent from my SGH-T679 using XDA Premium 4 mobile app
mwhitt said:
Also what recovery and build are you using?
Sent from my SGH-T679 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't know what you mean by recovery. I used the file AOSP_ancora_tmo_tim1928-4.1.2-Build 6.
And no, I did not wipe the data before I installed the ROM the first time. However I have tried that, and then reinstalled the ROM. Same results.
I feel there is some app or more detailed procedure to installing this ROM, but I don't find specific instructions anyplace.
Thanks for the help I've gotten so far. Any other pointers or suggestions?
DaddyRick said:
I don't know what you mean by recovery. I used the file AOSP_ancora_tmo_tim1928-4.1.2-Build 6.
And no, I did not wipe the data before I installed the ROM the first time. However I have tried that, and then reinstalled the ROM. Same results.
I feel there is some app or more detailed procedure to installing this ROM, but I don't find specific instructions anyplace.
Thanks for the help I've gotten so far. Any other pointers or suggestions?
Click to expand...
Click to collapse
Are you using clockwork mod or twrp to flash the rom
Sent from my SGH-T679 using XDA Premium 4 mobile app
Hey there, I registered because i recently bought a used galaxy i9000.
It came with the 2.3.6, so I wanted to upgraded it, so I had to use this custom rom's, which I've never heard about before.
After some research i decided to use the Mackay_ROM_4.1.7 to upgrade my phone, but after i did it, some problems appeared:
-The Play Store disapeared; (Meanwhile I was able to fix this error)
-It's always appearing this message on the screen "Unfortunately, the process android.process.media has stopped."
Is there a way to change to another ROM?
If yes, is there any way to fix these problems without need to change the ROM?
I would appreciate your help and opinion.
Thanks!
And sorry for my bad english and all my questions, I am kind of a noob in these things
-------------------------------------------------------------------------------------------------------------------------------
Meanwhile I was able to fix both errors.
1- I fixed the google play store problem by trying with another "gapps" file, the first one maybe was corrupt.
2- The other error I fixed it by doing a factory reset
Hey
If u are new to things then i would recommend using cyanogen mod..
get.cm
Download from that link and also install gapps from goo.im/gapps
Steps:
1. TAKE EFS FOLDER BACKUP
2. Boot recovery
3. Wipe data/factory reset
4. Wipe cache & dalvik cache (under advance)
5. Install zip from sdcard
6. Choose zip
7. Install gapps
8. Reboot, first boot will b about 5-10 mins..
Done..
Sent from my GT-I9300 using xda app-developers app
tchindalia said:
Hey
If u are new to things then i would recommend using cyanogen mod..
get.cm
Download from that link and also install gapps from goo.im/gapps
Steps:
1. TAKE EFS FOLDER BACKUP
2. Boot recovery
3. Wipe data/factory reset
4. Wipe cache & dalvik cache (under advance)
5. Install zip from sdcard
6. Choose zip
7. Install gapps
8. Reboot, first boot will b about 5-10 mins..
Done..
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thank you for your answer!
I will do that when i get back home, but there isn't any problem to do that while I am using Mackay? Because now when i press the keys to the recovery menu, I don't go to the samsung recover, I go to the Mackay recovery...
And what link are you talking about?
Now I have a different problem, my back camera is all blurry, is there a way to fix it?
Try to clean data of camera app and reboot the phone....
Enviado desde mi GT-N5110 mediante Tapatalk
vasco1120 said:
Now I have a different problem, my back camera is all blurry, is there a way to fix it?
Click to expand...
Click to collapse
Are pictures fine once you focus it?
Clear data of Camera and Gallery (they're seperate on Kitkat), or push another apk from another rom to see kf there is any difference. Also try apps from the market like Focal
Sent from my GT-I9300 using Tapatalk
Soryuu said:
Are pictures fine once you focus it?
Clear data of Camera and Gallery (they're seperate on Kitkat), or push another apk from another rom to see kf there is any difference. Also try apps from the market like Focal
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
I've already cleared the data, but continues the same.
What do you mean with "push another apk from another rom"? I am kind a noob in this questions, sorry.
Thanks for your help!
vasco1120 said:
I've already cleared the data, but continues the same.
What do you mean with "push another apk from another rom"? I am kind a noob in this questions, sorry.
Thanks for your help!
Click to expand...
Click to collapse
From another rom's zip file (CM, Omni etc), extract the Camera.apk and try install it.
Sent from my GT-I9300 using Tapatalk
Hi to all
I'm using this rom but unfortunatelly when i try to pair the phone in BT with the "car" (spleakers, rubrica...) i get an error, a force close (on the mobile) and often an "unable to update the data" ....
Someone can help me?
Thank you in advance
Runner75