Related
is there a rom or is anyone able to make one with a fresh clean no pre apps installed on the phone?
killahax said:
is there a rom or is anyone able to make one with a fresh clean no pre apps installed on the phone?
Click to expand...
Click to collapse
I would imagine you are looking for either:
http://forum.xda-developers.com/showthread.php?t=1806145&highlight=deodexed
or
http://forum.xda-developers.com/showthread.php?t=1806017
I believe they are what you are looking for.
schmeerdawg said:
I would imagine you are looking for either:
http://forum.xda-developers.com/showthread.php?t=1806145&highlight=deodexed
or
http://forum.xda-developers.com/showthread.php?t=1806017
I believe they are what you are looking for.
Click to expand...
Click to collapse
hell yes. thank you,
are you currently running any of these?
will these wipe out everything on my phone so need to back it all up right?
do i use safestrap to install this? and if so what is the link and directions for
http://forum.xda-developers.com/showthread.php?t=1806145 he doesnt say how to install it or what to use to install it.
and is it as smooth and everything works just with out all the unnecessary crap from verizon on there
I'm not currently running either of these, but I did use this one (http://forum.xda-developers.com/showthread.php?t=1806145&highlight=deodexed) for a few weeks without any problems. Then I tried to switch to Eclipse and messed up, so I had to fastboot back to original stock. Haven't found a rom that I'm really excited to try so I'm sticking with stock (rooted, of course). My next attempt will probably be the JB build that hashcode is working on. Once It becomes more stable, anyways.
Yes, Use Safestrap to install, it will also allow you to back up your current system. It's pretty easy to do, just follow the directions on the post when you download the rom.
Worst case scenario, you'll have to do what I did and fastboot back to stock, but most of the time the phone will be recoverable, so have fun!
schmeerdawg said:
I'm not currently running either of these, but I did use this one (http://forum.xda-developers.com/showthread.php?t=1806145&highlight=deodexed) for a few weeks without any problems. Then I tried to switch to Eclipse and messed up, so I had to fastboot back to original stock. Haven't found a rom that I'm really excited to try so I'm sticking with stock (rooted, of course). My next attempt will probably be the JB build that hashcode is working on. Once It becomes more stable, anyways.
Yes, Use Safestrap to install, it will also allow you to back up your current system. It's pretty easy to do, just follow the directions on the post when you download the rom.
Worst case scenario, you'll have to do what I did and fastboot back to stock, but most of the time the phone will be recoverable, so have fun!
Click to expand...
Click to collapse
i installed the safestrap on the phone and when i go to run it it says unfortunately safestrap has stopped.
killahax said:
i installed the safestrap on the phone and when i go to run it it says unfortunately safestrap has stopped.
Click to expand...
Click to collapse
I had the same problem. Is the phone currently rooted? If not, safestrap needs root. There is a walkthrough to show you how. In my case the issue was that busybox didn't install correctly. I got JRumy's Busybox Installer from the play store and used it. Worked like a charm.
schmeerdawg said:
I had the same problem. Is the phone currently rooted? If not, safestrap needs root. There is a walkthrough to show you how. In my case the issue was that busybox didn't install correctly. I got JRumy's Busybox Installer from the play store and used it. Worked like a charm.
Click to expand...
Click to collapse
shizza, i installed busybox on phone, then when i click install button after i select which busybox v i want which i tried all and they say fail to install lol.. geeezzz
killahax said:
shizza, i installed busybox as well and it says failed to install lol.. geeezzz...
Click to expand...
Click to collapse
I'd make sure that root worked properly, and re-install busybox. If that doesn't work, take a look here and see if there is anything that could be of help. At worst, contact Hashcode (the developer)
schmeerdawg said:
I'd make sure that root worked properly, and re-install busybox. If that doesn't work, take a look here and see if there is anything that could be of help. At worst, contact Hashcode (the developer)
Click to expand...
Click to collapse
right now im trying to do this root
http://forum.xda-developers.com/showthread.php?t=1707214
but on cmd prompt i type in adb shell and it says not found.. thats how far im getting lol
I just used the .zip since everything is automated. Only took a few minutes.
Sent from my DROID4 using xda app-developers app
im updating my adb and motorola drivers, hopefully that works
alrigth i got it working updated drivers etc..
Rick #2 needs to word the directions a little better, he jumps the main steps to get it going lol.
thanks for your help really appreciate it a lot
killahax said:
alrigth i got it working updated drivers etc..
Rick #2 needs to word the directions a little better, he jumps the main steps to get it going lol.
thanks for your help really appreciate it a lot
Click to expand...
Click to collapse
No problem, good luck, and enjoy!!
First Question:
Is it safe to delete all contents of /mnt/sdcard ?
Second Question:
Is there a way to install to unsafe?
Third Question:
Liquid Smooth has parted ways. The two best ROMs that have been recommended to me were LS and Eclipse. I found Eclipse to be sluggish compared to Liquid Smooth. What is a good primary ROM with these two requirements: Stupid Fast and Everything Working?
mikemikemikexxx said:
First Question:
Is it safe to delete all contents of /mnt/sdcard ?
Second Question:
Is there a way to install to unsafe?
Third Question:
Liquid Smooth has parted ways. The two best ROMs that have been recommended to me were LS and Eclipse. I found Eclipse to be sluggish compared to Liquid Smooth. What is a good primary ROM with these two requirements: Stupid Fast and Everything Working?
Click to expand...
Click to collapse
1) I would say no. Safestrap and some others are located there as far as I know. I mean you could probably do that and then install fastboot or something and update that way but i'm not 100% sure. Also what is the purpose? As far as I know with SS there is no need to do this.
2) IDK about that.
3) I found Blurry Maxx Rom to be a very snappy and responsive ICS based rom so everything works. It is not blur based so you won't have the quick contacts but I just put 8 "people" card widgets up and it looks the same as a pulled down contacts widget. So far everything except smart actions seems to work flawlessly. I did find v 3.8 to be more stable and faster than 4.2 (not to be confused with android version 4.2.1 or 4.2.2 this is an ICS rom not JB).
Hope this helps.
neo1738 said:
1) I would say no. Safestrap and some others are located there as far as I know. I mean you could probably do that and then install fastboot or something and update that way but i'm not 100% sure. Also what is the purpose? As far as I know with SS there is no need to do this.
2) IDK about that.
3) I found Blurry Maxx Rom to be a very snappy and responsive ICS based rom so everything works. It is not blur based so you won't have the quick contacts but I just put 8 "people" card widgets up and it looks the same as a pulled down contacts widget. So far everything except smart actions seems to work flawlessly. I did find v 3.8 to be more stable and faster than 4.2 (not to be confused with android version 4.2.1 or 4.2.2 this is an ICS rom not JB).
Hope this helps.
Click to expand...
Click to collapse
1) Internal SD is starting to get crapped up and Android isn't very good at cleaning up after itself.
2) Not a huge deal until I find a new daily.
3) I was not clear and it was 100% my fault. I left out the detail that I am looking for a JB build. I have a near 100% Jelly Build from Liquid but there is an issue that I can't figure out.
mikemikemikexxx said:
1) Internal SD is starting to get crapped up and Android isn't very good at cleaning up after itself.
2) Not a huge deal until I find a new daily.
3) I was not clear and it was 100% my fault. I left out the detail that I am looking for a JB build. I have a near 100% Jelly Build from Liquid but there is an issue that I can't figure out.
Click to expand...
Click to collapse
Sorry I can't be of more help. The JB builds are really hit or miss and seems individual phone dependent. I had CM 10.1 and app drawer stops working after 10 minutes, just FC. I'm hoping Liquid will be better as I've heard. Also it is known you can't do pattern unlock on JB builds as of now and you will need 3rd party camera app like camera fx. Good luck.
neo1738 said:
Sorry I can't be of more help. The JB builds are really hit or miss and seems individual phone dependent. I had CM 10.1 and app drawer stops working after 10 minutes, just FC. I'm hoping Liquid will be better as I've heard. Also it is known you can't do pattern unlock on JB builds as of now and you will need 3rd party camera app like camera fx. Good luck.
Click to expand...
Click to collapse
My only issue is the whole mounting to /storage instead of /mnt everything else I can live with. I am thinking it is a JB thing. Other JB Roms are doing the same thing.
New question, to get as close to a stock phone as possible, is this the procedure?
1) Boot into Safestrap, remove safe-side ROM.
2) Boot into stock ROM, remove safestrap boot files followed by SafeStrap apk.
3) Do a factory reset.
Would this be the safe way about it?
mikemikemikexxx said:
My only issue is the whole mounting to /storage instead of /mnt everything else I can live with. I am thinking it is a JB thing. Other JB Roms are doing the same thing.
New question, to get as close to a stock phone as possible, is this the procedure?
1) Boot into Safestrap, remove safe-side ROM.
2) Boot into stock ROM, remove safestrap boot files followed by SafeStrap apk.
3) Do a factory reset.
Would this be the safe way about it?
Click to expand...
Click to collapse
If you really want stock then I would delete all partitions and then remove bootstrap then RSDLite the phone to completely stock.
neo1738 said:
If you really want stock then I would delete all partitions and then remove bootstrap then RSDLite the phone to completely stock.
Click to expand...
Click to collapse
Fresh in terms of stock leak, so that I can keep unsafe completely app free, only have contacts and use it in case of emergency for calls.
I will want to reinstall root, safestrap, and custom roms again but just want to decrapify the unsafe side.
mikemikemikexxx said:
Fresh in terms of stock leak, so that I can keep unsafe completely app free, only have contacts and use it in case of emergency for calls.
I will want to reinstall root, safestrap, and custom roms again but just want to decrapify the unsafe side.
Click to expand...
Click to collapse
Can you use RSDLite with the stock leak? I'm not 100% sure about that one but I don't see why not. If you are using a ROM anyway what's the point of using leaked SW for the stock? Seems like extra work to me.
I figured out the formatting but what do you mean with extra work?
Sent from my DROID BIONIC using xda app-developers app
mikemikemikexxx said:
I figured out the formatting but what do you mean with extra work?
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
my thought is if you can't just use RSDLite to install the "leak" SW than it may mean doing more work figuring it out.
I experience random restarts despite of the ROM I have flashed. I have tried JellyBeer ROM, PA ROM, Stunner ROM, Sweet ROM and many more with their respective default kernel. My stupid phone even restarts in CWM and trying to flash a new ROM.
What could be the issue? How can I get this fixed?
Random restarts are quite common with ROMs under development or if not flashed properly. Update the ROM to a stable version or re-flash the ROM wiping cache, factory reset and see. You can flash a stable ROM to get rid of the problem.
All wipes and reflash may solve your problem...
Varad297 said:
Random restarts are quite common with ROMs under development or if not flashed properly. Update the ROM to a stable version or re-flash the ROM wiping cache, factory reset and see. You can flash a stable ROM to get rid of the problem.
Click to expand...
Click to collapse
benito.brazil said:
All wipes and reflash may solve your problem...
Click to expand...
Click to collapse
I always flash a stable version of the ROM with a full wipe. Even I format preload,cache,system, etc. Whatever ROM I flash it does not help.
But I simply can not understand what cause the restarts on my phone ?
No harm in just re-flashing a ROM. I face random restarts on the PAC currently, this is a common problem. Else try one of the stable 4.1.2 TW ROMs. Hope you don't face a restart then!
It might be a app you are using. Install catlog from play store and find the cause. You say it happens on all ROMs you flash. Is there any particular app you restore
#Galaxtus - Over and Out
Varad297 said:
No harm in just re-flashing a ROM. I face random restarts on the PAC currently, this is a common problem. Else try one of the stable 4.1.2 TW ROMs. Hope you don't face a restart then!
Click to expand...
Click to collapse
Yes. I'm using sweet ROM v9. I still get random starts here and there.
Galaxtus said:
It might be a app you are using. Install catlog from play store and find the cause. You say it happens on all ROMs you flash. Is there any particular app you restore
#Galaxtus - Over and Out
Click to expand...
Click to collapse
Thanks I'll try this for sure and let you know. I have installed the app. Can you please tell me how can I use this to make sure what's the problem ?
If you're getting random reboots on TW and AOSP based Roms, I would suspect an app driving the system nuts.
AA1973 said:
If you're getting random reboots on TW and AOSP based Roms, I would suspect an app driving the system nuts.
Click to expand...
Click to collapse
I only use well reputed apps such as Facebook, solid explorer, google handouts, flipboard etc
Facebook App has a good reputation? Would be new to me. Look at their app reviews and star(s) on Google play.
try a proper stock rom with en see if it happens.
Galaxtus said:
It might be a app you are using. Install catlog from play store and find the cause. You say it happens on all ROMs you flash. Is there any particular app you restore
#Galaxtus - Over and Out
Click to expand...
Click to collapse
Can you please tell me how to use this app to pin point the issue? I have already installed it.
AA1973 said:
Facebook App has a good reputation? Would be new to me. Look at their app reviews and star(s) on Google play.
Click to expand...
Click to collapse
I mean like they are used by everyone plus I have been using it for a year now. Never had a problem. I always use the apps that I have been using for a long time. Nothing new
My stupid phone even restarts in CWM and trying to flash a new ROM. What could be the issue?
dasunh said:
My stupid phone even restarts in CWM and trying to flash a new ROM. What could be the issue?
Click to expand...
Click to collapse
Option 1>>>Open Catlog and press record and minimize it has it will start the log process. Use your phone normally and see anything happens.
Option 2>>>I would suggest you one thing flash any ROM best choose CM base ROM and flash gapps and reboot. Don't sign in to google just cancel the process and add it later from settings. Live it stock without loading any apps and see if it reboots for you.
Option 3>>>Might be a faulty motherboard don't know. Was the case when you brought the phone in the first place?
#Galaxtus - Over and Out
Galaxtus said:
Option 1>>>Open Catlog and press record and minimize it has it will start the log process. Use your phone normally and see anything happens.
Option 2>>>I would suggest you one thing flash any ROM best choose CM base ROM and flash gapps and reboot. Don't sign in to google just cancel the process and add it later from settings. Live it stock without loading any apps and see if it reboots for you.
Option 3>>>Might be a faulty motherboard don't know. Was the case when you brought the phone in the first place?
#Galaxtus - Over and Out
Click to expand...
Click to collapse
Thanks for the info. I really appreciate it mate. I have clicked the thanks button
Once I got the phone it was working fine. I'm not sure about the power button too. I'm working on it to figure out whether it's the kernel or the ROM the power button.
You can try the following:
1. re-flash the samsung stock rom ....i would recommend you go with Official ICS Rom 4.0.4. Perform a clean data wipe, cache and dalvik cahe.
2. Do not use any other apps other than whats included in stock rom. Observe carefully for 2-3 days.
3. If all goes smooth, you can try installing well-known apps like facebook, whatsapp, etc etc
4. if you still have issue, i suggest you change your battery. Go for the official samsung battery only. Observe your phone's behavior.
Hope it helps you
HAve you ever tried to change the battery. I saw lots of Note batteries gone bad after 9-12 months. I could be the reason. Not sure though.
So ive been trying to dual boot because i want to try aosp based rom but i need to be a ble to get back to touchwis. Now ive tried the patcher app which aome people said it worked but ive tried everything with no succes.
egren58 said:
So ive been trying to dual boot because i want to try aosp based rom but i need to be a ble to get back to touchwis. Now ive tried the patcher app which aome people said it worked but ive tried everything with no succes.
Click to expand...
Click to collapse
I dont't know if this helps but in the thread for the patcher app it was mentioned that if you needed to dual boot with a TW based rom it would need to be the primary in order for it to work properly otherwise the mods would need to be patched before flashing.
glm0025 said:
I dont't know if this helps but in the thread for the patcher app it was mentioned that if you needed to dual boot with a TW based rom it would need to be the primary in order for it to work properly otherwise the mods would need to be patched before flashing.
Click to expand...
Click to collapse
I swt tw as primary patched cm12 and gapps. But recovery was freezing so i tried to manually paych the file as stated. But than when i got to flash vie recovery it says fail. I have no idea what to do since i did exactly as it said.
My guess would be try asking in the dual boot thread. Others have gotten it to work.
BAD ASS NOTE 4
BACARDILIMON said:
My guess would be try asking in the dual boot thread. Others have gotten it to work.
BAD ASS NOTE 4
Click to expand...
Click to collapse
Good idea. But for some reason i cant find the dam thread now. Wtf.
egren58 said:
Good idea. But for some reason i cant find the dam thread now. Wtf.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3058835
All u need
BAD ASS NOTE 4
http://www.linuxmolecule.com/how-to-dual-boot-roms-on-the-galaxy-note-4/
I can confirm this works in T-Mobile note 4. You just have to follow the steps.
It works trust me, I'm a senior member
I managed to get it to flash but....
after i manually patch the gapps and rom, i flash the two files successfully and then i reboot into my secondary rom. I set the kernel then i set up my rom up with the apps i use. I went into the dual boot patcher app and tried to dual boot to my primary rom, it says "please wait"...then it says successfully switched ROM..but it never switches back to my primary rom. Any ideas?
Dhat Boi Swerve said:
after i manually patch the gapps and rom, i flash the two files successfully and then i reboot into my secondary rom. I set the kernel then i set up my rom up with the apps i use. I went into the dual boot patcher app and tried to dual boot to my primary rom, it says "please wait"...then it says successfully switched ROM..but it never switches back to my primary rom. Any ideas?
Click to expand...
Click to collapse
It should when you reboot the device.
Dhat Boi Swerve said:
after i manually patch the gapps and rom, i flash the two files successfully and then i reboot into my secondary rom. I set the kernel then i set up my rom up with the apps i use. I went into the dual boot patcher app and tried to dual boot to my primary rom, it says "please wait"...then it says successfully switched ROM..but it never switches back to my primary rom. Any ideas?
Click to expand...
Click to collapse
Struggling with this thing for the last 2 days. Same issue as your. Cannot switch back to the primary rom...
suhridkhan said:
Struggling with this thing for the last 2 days. Same issue as your. Cannot switch back to the primary rom...
Click to expand...
Click to collapse
you cant dual boot stock Samsung roms for some reason...
frr1 said:
you cant dual boot stock Samsung roms for some reason...
Click to expand...
Click to collapse
Just got it working, after so much trouble. Tmobile Note4 running TW Rapture as primary and CMRemix as secondary. Still no luck with the second step of patching, but manual patch has worked. This one is a better written guide, I suppose.
http://www.linuxmolecule.com/how-to-dual-boot-roms-on-the-galaxy-note-4/
I can't believe it's taken me this long to get into trying to dual boot my phone... both my desktop and laptop have ridiculous multi-boot schemes :laugh:
The main reason I haven't yet delved into this is a fairly simple question that I haven't been able to find the answer to: How much free storage space is required / will be used by installing an additional ROM and on which partition(s)?
I'd really appreciate if anyone who has this working could fill me in on that info
BTW another great thread with instructions, etc. is here: http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211
jazzmachine said:
I can't believe it's taken me this long to get into trying to dual boot my phone... both my desktop and laptop have ridiculous multi-boot schemes :laugh:
The main reason I haven't yet delved into this is a fairly simple question that I haven't been able to find the answer to: How much free storage space is required / will be used by installing an additional ROM and on which partition(s)?
I'd really appreciate if anyone who has this working could fill me in on that info
BTW another great thread with instructions, etc. is here: http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211
Click to expand...
Click to collapse
AOSP roms has very small footprint, that's why they are insanely fast... The roms itself with gapps only takes about a gigabyte, if it's CM or other aosp roms. If you dual boot 2 TW roms, of course it's gonna take huge space. It also depends on how many apps you are going to install on the second rom
Hi all, i am having a big trouble about the camera.
So i was using the official CM12, but since recently the camera keep FC or it kept saying can't connect to camera,
i decided to change to the other ROM. However, when i changed to Titan Prime 1.1, i can open the camera ONCE. After that same issue happen!!
it is not only the camera, also the screenshot function is not working! It kept saying due to limited storage the screenshot couldn't be taken
So i tried the following methods:
1. Force stop camera app, clean cache+data, reboot => didn't work
2. Install the CameraFiles-Signed.zip => didn't work
3. Wipe the system, data, cache and davik cache and install different versions of CM or Titan Prime 1.1 =>didn't work
Does anyone has the problem or know how to solve this??
Thanks!
Boseinstein said:
Hi all, i am having a big trouble about the camera.
So i was using the official CM12, but since recently the camera keep FC or it kept saying can't connect to camera,
i decided to change to the other ROM. However, when i changed to Titan Prime 1.1, i can open the camera ONCE. After that same issue happen!!
it is not only the camera, also the screenshot function is not working! It kept saying due to limited storage the screenshot couldn't be taken
So i tried the following methods:
1. Force stop camera app, clean cache+data, reboot => didn't work
2. Install the CameraFiles-Signed.zip => didn't work
3. Wipe the system, data, cache and davik cache and install different versions of CM or Titan Prime 1.1 =>didn't work
Does anyone has the problem or know how to solve this??
Thanks!
Click to expand...
Click to collapse
Try flashing stock with correct fast boot commands ..!! This should work
dj krishna said:
Try flashing stock with correct fast boot commands ..!! This should work
Click to expand...
Click to collapse
You mean flash back to the original motorola ROM?
what commands should i put??
Thanks!
you don't have a camera problem you have a file permission bug...
see here.
baybutcher27 said:
you don't have a camera problem you have a file permission bug...
see here.
Click to expand...
Click to collapse
Thanks for the help!
I tried the first method and it didn't work. And i used this http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167 method to restore to Stock.
But both method doesn't work still. When i open camera on stock rom, it said camera is busy. If this repeat please power off and restart your phone,
but the screenshot is now functioning.
I tried to flash just the Titan Prime 1.1 rom without PA Gapps, camera worked once. But after i install the gapps camera fc again.
Again i tried to restore to stock ROM, problem keeps occur. Then even i flash the Titan Prime again without gapps,
camera fc again !
It appears to be crashed with gapps and i don't know what to do next....
Boseinstein said:
Thanks for the help!
I tried the first method and it didn't work. And i used this http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167 method to restore to Stock.
But both method doesn't work still. When i open camera on stock rom, it said camera is busy. If this repeat please power off and restart your phone,
but the screenshot is now functioning.
I tried to flash just the Titan Prime 1.1 rom without PA Gapps, camera worked once. But after i install the gapps camera fc again.
Again i tried to restore to stock ROM, problem keeps occur. Then even i flash the Titan Prime again without gapps,
camera fc again !
It appears to be crashed with gapps and i don't know what to do next....
Click to expand...
Click to collapse
power off, and remove yours sd card.
power on and give a try.
if no good factory reset without the sd card and give a try.
you may have something in the sd causing it.
baybutcher27 said:
power off, and remove yours sd card.
power on and give a try.
if no good factory reset without the sd card and give a try.
you may have something in the sd causing it.
Click to expand...
Click to collapse
Oh my god you are right! how can you know that?
There is something wrong about the path for the camera to save photos.
Now the camera is smooth again!
Thank so much!!
Boseinstein said:
Oh my god you are right! how can you know that?
There is something wrong about the path for the camera to save photos.
Now the camera is smooth again!
Thank so much!!
Click to expand...
Click to collapse
Don't know was guess...
But i remember now, that my camera not the phone camera a digital camera that i have do that some times to some SD cards, probably from that i guess it.
Good that works. Try to format the card or use other to see if the problem is 100% resolved. Maybe a file in the SD is causing it, so be careful to what files you put back in the card.
baybutcher27 said:
Don't know was guess...
But i remember now, that my camera not the phone camera a digital camera that i have do that some times to some SD cards, probably from that i guess it.
Good that works. Try to format the card or use other to see if the problem is 100% resolved. Maybe a file in the SD is causing it, so be careful to what files you put back in the card.
Click to expand...
Click to collapse
It was the DCIM folder from older version of the rom caused it. I moved that folder to my pc and problem resolved.
I think the path just messed up. Thanks for the help anyway. I tried to fix it for two days!
Boseinstein said:
It was the DCIM folder from older version of the rom caused it. I moved that folder to my pc and problem resolved.
I think the path just messed up. Thanks for the help anyway. I tried to fix it for two days!
Click to expand...
Click to collapse
Hi guys i need help again. After a few week, without flashing any new roms, the problem pops out again.
Could it be problem about the path of camera? It is no longer in system/app
And if so how should i move it?
I searched for a long time and people said it could be permission problem.
I tried to use TWRP to fix ( which ends up in bootloop even with busybox),
and i try to clean wipe and install rom,
or even restore to stock rom, it still doesn't work.
Anyone can help.....?
the camera error
Hi guys so i tried to capture the error.
It said something about getting nullpointer, anyone know how to fix this?
I switched to CM12 rom, it has camera2. apk in system/app.
But it seems that the system still can't find the camera!