Related
I've tried searching for the solutions to this, but some of them are difficult to search and I'm struggling to get relevant results. So I apologize if any of this has been covered elsewhere.
Anyhow, I just installed the ParanoidAndroid ROM last night, and it all went very smoothly, and I was pleased. But, there seem to be a couple issues that either I need to iron out, or that the devs need to. And I'm fully willing to believe it's an issue on my end and not theirs, so, here we go:
1) In CWM, the top half of the screen or so has the rainbow glitch going on and there's a de-centered kind of effect happening that makes it very difficult to use.
2) I'm unable to get my external SD card to mount. I've seen plenty of threads about this similar issue, and I've tried tweaking the build.prop entry regarding this, but nothing I'm doing is helping.
3) The flash only works once per boot, even with included flashlight app. I haven't tested the flash's functionality in the camera yet. But in the flashlight app, the flash will turn on, and when I turn it off, it won't come back on until after a reboot.
4) I now have two installations of the stock Gallery app (com.android.gallery3d and com.google.android.gallery3d). I'm sure I can just uninstall one, but is there one that would be wiser to uninstall?
Otherwise, everything else seems to be working just fine. Thank you all very much in advance.
I've since discovered and fixed a new problem. My phone was apparently not sending or receiving any MMS messages, over WiFi or otherwise. But the APNs described in this post fixed that entirely:
http://forum.xda-developers.com/showthread.php?p=23806717#post23806717
As problem #4 from above goes, I deleted the com.android.gallery3d app and kept the com.google.android.gallery3d app as there were internet and syncing features that were omitted or nonfunctional from the former one.
Just so you know, if you read through the paranoid thread in the dev section or any of the ics ROM threads actually, all of your questions r covered. I cangive you answered/jumping off points for your questions.
1. The rainbow distortion comes from having Froyo bootloaders instead of GB. To fix this you will need to use Odin or Heimdall to flash the GB bootloaders. Look in the ISET Super Everything thread that's stickied in the dev section. BE SURE to flash something else with Odin or Heimdall (whichever you choose) before you try flashing the bootloaders. If you lose your connection while trying to flash bootloaders, you can hard brick your phone which basically means you have a shiny coaster.
2. Your external sd card is found in the emmc folder on ics ROMs. You need a root enabled file explorer to open it.
3. Using your camera flash as a flashlight which I believe is referred to as torch is one of the few known remaining bugs on Infuse ics ROMs. The flashlight app that is included is currently the only way to get it working. The flashlight should turn on everytime you open the app but it won't turn back on if you turn it off while in the app.
4. MMS is an issue with the APN settings. Look at the last few pages in the dev section. I know it was recently covered on a couple different ics ROMs threads. To get to the APN settings, go through the following path in the settings.
More (under data usage) > Mobile Networks > Access Point Names, click on the AT&T listing, then change MMS Proxy to 66.209.11.32
I'm pretty sure that is all you have to do to fix MMS but read some dev threads for more info. I think you can also try to look in the Dev Tools app if it is included with the ROM. In the app, click connectivity then start MMS. Again, further reading should give you more info.
Boz™
Sent from my SGH-I997 using xda app-developers app
Yeah, the flashlight thing, I knew was a known bug. But the latest update claiming that "all bugs squashed" misled me, I guess. Because that bug obviously persists. But, c'est la vie.
As the rainbow glitch goes, I never installed Froyo on here, I went from stock to Gingerbread to... actually, here's specifically what happened:
•Initially, I installed 3e Recovery and CWM on my stock Android 2.2 per the instructions here, http://www.youtube.com/watch?v=Y09p-J_g_Rg, and everything went fine.
•Then I flashed Gingerbread UCLB3 per this thread, http://forum.xda-developers.com/showthread.php?t=1508619, but unfortunately, I made a dumb mistake. I neglected to disable Voodoo Lagfix first and softbricked my phone.
•So, I went back to the Infuse Super Everything Thread and found this fix, http://forum.xda-developers.com/showthread.php?t=1092021, brought my phone back to stock, just fine.
•Then I flashed to UCLB3 the same way as before, only this time disabling Voodoo and it all worked perfectly.
•Then I immediately flashed to ParanoidAndroid and everything went as described in the thread and now here I am with the CWM glitch.
So I've only been stock or Gingerbread ever before on my phone.
Anyone know how to simply change the font or install a new one?
Sent from my SGH-I997 using xda premium
I use ROM Toolbox Pro.
Edit: Check the Paranoid Android dev thread end of page 32 and beginning of page 33. The guy that maintains the PA port just posted a link and instructions for the fix to rainbow recovery.
I'm no expert so I may b wrong but I'm pretty sure that if you had a stock AT&T infuse then it most likely came with Froyo originally. Just bc you flashed a GB ROM doesn't mean you got the bootloaders. To get the GB bootloaders, you need to run Heimdall a second time with the "Install Bootloaders" checkbox checked. I'm not exactly sure how it works in Odin but I think you have to have a file in the PDA slot in order to get the bootloaders installed.
I do know that if you have rainbows, it is bc you have Froyo bootloaders. Our at least that is the only reason I've ever heard of and I've read of people with the issue numerous times. I would just read through some of the dev ics threads bc there have been a few times in the last week that I've seen people pay steep by step instructions explaining exactly which Heimdall or Odin to use. I just know that you have to take extra steps to install GB bootloaders. With Heimdall that means checking the flash bootloaders checkbox. They do this bc it can hard brick your phone so they don't want you to install them unless absolutely necessary.
Boz™
Sent from my SGH-I997 using xda app-developers app
Ah-ha! Very good, someone else is having my same problems, lol. I'll definitely be using Odin, as that's how I fixed my softbrick issue and I could never get Heimdall to install on my computer properly (Java issues or something, couldn't figure it out and Odin worked anyway).
Do you know if flashing the bootloader will cause any loss of information or settings? Or will it affect nothing else?
I'm not 100% sure on that one. When I did it, I was using Heimdall to fix my soft bricked phone at the same time so I was basically starting fresh. I'm not sure if it is possible to just flash bootloaders in the Odin PDA slot and keep everything else. I would assume that you would lose everything and have to reflash the ROM from recovery but that's just an assumption.
I would get titanium backup (if u don't already have it) and backup everything and sync with your Gmail account just in case. That way u can save it apps and their settings.
You may b able to ask that question on the PA dev thread and get a better answer.
Boz™
Sent from my SGH-I997 using xda app-developers app
There's an XDA Forum restriction on newbies. I can't post in any Dev forums until I've... done something, I forget. Ten posts or ten thanks. I forget what. Either way, I'm not allowed in there yet. lol
Anyhow, based on some threads I've found, it seems possible to flash only the bootloader in Odin. I'm still just waiting to find out how much information is lost in the process before I dive into it.
But yeah, I do have Titanium, and now that I have everything installed and set up just the way I like it, it is time for a backup anyway.
Supposing I need to, is there any problem restoring system apps and data once I do this? Because everything will be identical, minus the bootloader. I just know I've read enough about the dangers of restoring system data on the threads here to be cautious. Even though I'll just be going from ParanoidAndroid to the same flash of ParanoidAndroid, plus a new bootloader, but better safe than sorry.
Thanks for all your help, man.
Appears as though that question's already been answered here:
http://forum.xda-developers.com/showthread.php?t=1603220&page=5
Bottom of page 5 states somewhat affirmatively that no data will be lost. So, lovely. Now I've just got to flash the bootloader, and then work on my forum searching skills. I can never find ****, when clearly it's somewhere. lol
dstarr3 said:
2) I'm unable to get my external SD card to mount. I've seen plenty of threads about this similar issue, and I've tried tweaking the build.prop entry regarding this, but nothing I'm doing is helping.
Click to expand...
Click to collapse
Figured out the emmc part but how do you actually open the external SD on your pc?
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
Thanks,
Reffu
Hi,
same issue here. Today the touchscreen stopped working suddenly after i flashed the Android Revolution HD 5.0 Rom yesterday. However, the S-Pen is still working fine. Installing other ROMs and the Stock ROM via Odin did not help. Issue allso appears in Touch-enabled-Recovery.
I see no reason, why this should be a hardware issue, although my N8000 came back from service a few days ago, where they also replaced the screen and digitizer.
Had anyone this issue before and was abled to resolve it?
Greets
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
to read this as a Note 10.1 newbie is not very encouraging. are there any similar facts between all of you like
which Note model do you have
how did you jaibreak (which method)
which rom did you have before
which rom do you have now
how did you flash a new rom
...
is there a way to find out whether the touchscreen is really "dead for touch"?
This is a bit scary - my Note 10.1 is arriving today, and I plan to root it at a minimum. I actually don't mind Touchwiz all that much on my Note 2 (which is running CleanROM ACE), so I think I might just root the 10.1 for now.
So restoring completely back to stock (via Odin) doesn't fix it? That is really odd that ROM-ing this thing might cause a hardware failure...
jiggyman said:
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
kkretch said:
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
Click to expand...
Click to collapse
Did anyone solve this, I'm having the same problem.
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
Just curious - did you just root, or did you root and install a ROM?
I am only rooted so far - haven't felt the need to ROM yet - partially due to worries about this happening. I bought a refurb from Best Buy and only get 90 days of warranty.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
If they say you got a new one, you got one. They'll tell you otherwise if there's an issue over the phone.
But I wouldn't be afraid of ROMs, but to be more diligent and wise when it comes to choosing them. It's like choosing a poisonous mushroom versus an edible one to make stroganoff or stir fry. If you know what to avoid for the next time and follow the correct process to doing the root and flashing, there will not be an issues.
This is from someone who has soft-bricked my first tablet and learned how to unbrick my SIM-less Captivate and Note 10.1. It's how you apply the method and how much attention you practice not getting stuck into these situations is what matters. Especially since I bricked my tablet via experimentation and un-bricked it on the same day with ease.
It's not some big complex deal of rocket science or something only the mere geniuses can do, its how you perceive yourself and how you act. If you believe that you will suck and brick it to kingdom come , it will happen intentionally or subconsciously.
In this case, it was a freak accident where the file/s accessed and deleted the wrong files which allowed for capacitive touchscreen use, and it should be reported to x developers if you have not done so already.
I have rooted and used the Revolution HD rom, the Rom where you customize the colors of the bar/other things, and on the Captivate, the AOKP Collective. I further customized the latter with the Xperia launcher as it zips.
Did anyone find a repair for this besides replacement? My Note 2 is doing the same thing now.
Has anyone found a fix for the touch screen not working yet??
Anyone have any ideas?
Technicians input for touch problem
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain that follows the instructions on the mod sites exactly as shown step by step will never have a problem, all those that do end up with paper weights or bricks didn't follow the instructions in numerical order.
Believe it or not even if after you have modded a rom and brought it back to standard they know it has been modded as they have a list of problems associated with repairs after roms have been modded so you are only fooling yourself they don't.
Same as the smoker that tells his Dr he has given up even though all the symptoms prove he really didn't.
So in my expert opinion if you play with modding and stuff it up why should you be eligible for a warranty claim ? The manufacturer has sold you or supplied a working item that you decided to f_ck around with and because of your stupidity expect some one else to pay for it.
I am not saying don't mod your phone with all the great roms out there but please to save yourself a lot of pain and cost some poor smuck trying to run a business in these economic times a lot of out of pocket from sending items back for replacement or warranty plus the time it takes to do all the paperwork and such, please please please read the instructions 300% or triple check you are doing everything exactly as the instructions say and you will be enjoying all the new benefits of that customised rom and laughing at all the noobs stuffing up their brand new device from not doing so.
I know this won't fix your problem but reread that last bit it was your problem as you are to clever to follow some one else's instructions
anyone have solution regarding this issue, mine have issue also, can anyone spare how to fix it without changing hardware?
---------- Post added at 06:47 AM ---------- Previous post was at 06:28 AM ----------
i hope anyone can solve my issue with touch not responding
WOW.. on TOPIC Flashing .pit might help ???
Gardum said:
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain
Click to expand...
Click to collapse
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
erica_renee said:
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
Click to expand...
Click to collapse
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
popohunters said:
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
Click to expand...
Click to collapse
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
erica_renee said:
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
Click to expand...
Click to collapse
thanks sir, im done the flashing with pit files+ official firmware but touch screen is still missing, is there a modem file for touch screen maybe i missed it while its in downloading process before i brick the touch screen
any hope out there?????
confused and need help
i have a n8000 , base band version N8000XXCLL1, my touch screen stoped responding while playing a game , only Spen works , tried resetting , but no help, I'm a no-voice when it comes to programing and need a step by step guide >>>> many thanks in advance for all your help
reffu said:
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
I got the same problem after rooting my phone.... I used the following method and got ride of that Problem. ..
type this star code in in it Phone dialler *#2663#
Now you should see "TSP"
<update>
TAP on TSP ......it will take 5 seconds only....
......
NOW ENJOY ☺☺
Click to expand...
Click to collapse
Ok, I'm a total noob at this so I'll try to provide whatever pertinent info I can.
Today I got it in me to root my Samsung Galaxy S3 (Verizon). After I did this I decided to flash cm-10.1.0-RC5-d2vzw.zip (Yes I wiped everything before I did it [after making a backup of course]) and gapps 4.2.2 http://goo.im/gapps in TWRP.
Everything went smooth and I had everything looking the way I liked until I tried to open the camera app, and then it said "Cannot connect to camera." So I tried flashing the stable build that was just released: cm-10.1.0-d2vzw.zip. Still didn't work.
I tried looking near and far, everywhere, on why my camera wouldn't work. I tried loading SlimISP_ZH.bin into the data folder based on one thread that was talking about camera problems http://forum.xda-developers.com/showthread.php?p=36933667 I read somewhere about checking camera firmware: http://forum.xda-developers.com/showthread.php?p=37328191 but it didn't pertain to my device, and the code didn't do anything. Nothing helped.
Now I have no idea what to do. I reloaded my original stock ROM and now the camera works again, but I REALLY don't want to keep it cause it's just... slow.. especially after I experienced Cyanogenmod. I couldn't find any other info on this problem so I am asking you, the people who actually know what they're doing, to help me out if possible. If there is already a thread on this exact problem, I am sorry, but I really searched hard and couldn't find anything related to this specific problem.
My current (stock and rooted) specs are as follows:
Model # - SCH-I535
Android Version - 4.1.2
Baseband version - I535VRBMF1
Kernal Version - [email protected] #1_SMP PREEMPT Sat Jun 8 17:20:08 KST_2013
Build number - JZO5K.I535VRBMF1
Hardware version - I535.10
Nobody seems to have a definite answer for this issue and I don't understand why. This is affecting a lot of people running AOSP with no reason as to why, specifically. I've tried many, MANY things, nothing is helping. I'm rerooting after I get a confirm in my post and will let you know how it goes from there.
http://forum.xda-developers.com/showthread.php?t=2337632&nocache=1
CZory91 said:
Nobody seems to have a definite answer for this issue and I don't understand why. This is affecting a lot of people running AOSP with no reason as to why, specifically. I've tried many, MANY things, nothing is helping. I'm rerooting after I get a confirm in my post and will let you know how it goes from there.
http://forum.xda-developers.com/showthread.php?t=2337632&nocache=1
Click to expand...
Click to collapse
Thanks for the reply. I'm glad to know it isn't just me and my ineptitude. I was SO excited to root my device and then this happens... oh well.
Sythrix said:
Thanks for the reply. I'm glad to know it isn't just me and my ineptitude. I was SO excited to root my device and then this happens... oh well.
Click to expand...
Click to collapse
Well. Good and bad news. Good news is it's fixed. Bad news is there is no way that I can find of updating the firmware/modem while running an AOSP ROM. The first try worked great, wanted to see if I could update the firmware, no go. Restarted from the beginning again to see if taking the OTA updates while not rooted would allow me to have it work when rooted. Updates went through, everything went fine. Camera didn't work on AOSP still. So at least it works... I can deal without the firmware I guess, definitely worth a working camera and fully stable CM10.1.
Had some issues with the root, however a few tries at it and it eventually worked. This requires no input on your screen (first try SU popped up on me and I granted access, it rebooted and didn't root correctly) Edit: This time around I granted it and it worked. Heck if I know what/why. Just just keep doing it until it works, worked for me. Don't press anything the first try, then do so the second, etc.. Start it as soon as your device is connected to your computer and let it do it's thing. Don't let it have the chance to switch from its "installer" mode on the phone to a media device (unsure if that was the problem, but that seemed to be the reason why after the second round, 4th attempt).
Also, I had to battery pull and wipe data on the stock recovery listed as optional on the first link after it was rooted (WAIT UNTIL ODIN SAYS PASS before pulling the battery out when it's at the boot logo).
The only other thing I would say is that my phone initially came with the VRBLK3, and that may be the reason why this worked for me. Don't know. If your phone shipped with a different version, and my process doesn't work for you, try finding an MD5 with your shipped firmware version that will odin you to that version, and then continue with the root.
This has been posted about many times. The fix is simple.
Flash this file in recovery:
http://invisiblek.org/sch-i535/firmware/I535VRBMB1_firmware.zip
Restola said:
This has been posted about many times. The fix is simple.
Flash this file in recovery:
http://invisiblek.org/sch-i535/firmware/I535VRBMB1_firmware.zip
Click to expand...
Click to collapse
Thank you so much! Works like a charm. :victory: I don't know why I couldn't find it anywhere if its been posted many times. Maybe this or something similar should be a sticky post so that people who have gotten the latest firmware updates will know why they can't get it to work. You know, for noobs like me who barely know what they're doing. Regardless, you are awesome, and I appreciate it.
Thanks to you too, CZory91, for the input. Apparently all of that (on my phone at least) wasn't necessary. I do appreciate the reply though. I hope you got yours to work the way you want it.
Sythrix said:
Thank you so much! Works like a charm. :victory: I don't know why I couldn't find it anywhere if its been posted many times. Maybe this or something similar should be a sticky post so that people who have gotten the latest firmware updates will know why they can't get it to work. You know, for noobs like me who barely know what they're doing. Regardless, you are awesome, and I appreciate it.
Thanks to you too, CZory91, for the input. Apparently all of that (on my phone at least) wasn't necessary. I do appreciate the reply though. I hope you got yours to work the way you want it.
Click to expand...
Click to collapse
It's in the first post on both CM10.1 threads (Q&A and Developer forums).
Sythrix said:
Ok, I'm a total noob at this so I'll try to provide whatever pertinent info I can.
Today I got it in me to root my Samsung Galaxy S3 (Verizon). After I did this I decided to flash cm-10.1.0-RC5-d2vzw.zip (Yes I wiped everything before I did it [after making a backup of course]) and gapps 4.2.2 http://goo.im/gapps in TWRP.
Everything went smooth and I had everything looking the way I liked until I tried to open the camera app, and then it said "Cannot connect to camera." So I tried flashing the stable build that was just released: cm-10.1.0-d2vzw.zip. Still didn't work.
I tried looking near and far, everywhere, on why my camera wouldn't work. I tried loading SlimISP_ZH.bin into the data folder based on one thread that was talking about camera problems http://forum.xda-developers.com/showthread.php?p=36933667 I read somewhere about checking camera firmware: http://forum.xda-developers.com/showthread.php?p=37328191 but it didn't pertain to my device, and the code didn't do anything. Nothing helped.
Now I have no idea what to do. I reloaded my original stock ROM and now the camera works again, but I REALLY don't want to keep it cause it's just... slow.. especially after I experienced Cyanogenmod. I couldn't find any other info on this problem so I am asking you, the people who actually know what they're doing, to help me out if possible. If there is already a thread on this exact problem, I am sorry, but I really searched hard and couldn't find anything related to this specific problem.
My current (stock and rooted) specs are as follows:
Model # - SCH-I535
Android Version - 4.1.2
Baseband version - I535VRBMF1
Kernal Version - [email protected] #1_SMP PREEMPT Sat Jun 8 17:20:08 KST_2013
Build number - JZO5K.I535VRBMF1
Hardware version - I535.10
Click to expand...
Click to collapse
Props on providing all that data with your question.. wish everyone was as thorough as that when needing help..
Sent from my Nexus 7 using Tapatalk 4 Beta
Restola said:
This has been posted about many times. The fix is simple.
Flash this file in recovery:
http://invisiblek.org/sch-i535/firmware/I535VRBMB1_firmware.zip
Click to expand...
Click to collapse
Did not and still does not work for me.
Sent from my SCH-I535 using Tapatalk 4 Beta
Hello, chaps! So, I've just got a XT925 and, basically, what I want is to get to CM11. I'm used to CM features and I'm sure this little beast runs even better on KK than it does on stock JB
I was looking for guides and stickies to read through, but there isn't much, really... Why is that? I need help rooting, unlocking the bootloader, flashing recovery and the ROM itself, but I'm far from a complete noob and the guides are enough for me, but I can't find them Could anyone point me in the right direction?
Also, I've got a couple questions about CM11 I'm planning to run the 3.0 kernel CM11 version until KK OTA shows up and I'll see where to go from there. How good is the CM11 on RAZR HD? Is there a list of known bugs? And does the HDMI port work? I find it to be a cool feature, although I don't use it often... Would be nice if it works on CM11, too. And the camera, how's it on CM11? I love the 60fps video recordings and hope that photo quality is at least the same, because it really isn't too great on stock JB :/ Using 3rd party camera apps helps to a degree...
Any help, info and answers would be greatly appreciated Thanks in advance!
Cheers
niksy+ said:
Hello, chaps! So, I've just got a XT925 and, basically, what I want is to get to CM11. I'm used to CM features and I'm sure this little beast runs even better on KK than it does on stock JB
I was looking for guides and stickies to read through, but there isn't much, really... Why is that? I need help rooting, unlocking the bootloader, flashing recovery and the ROM itself, but I'm far from a complete noob and the guides are enough for me, but I can't find them Could anyone point me in the right direction?
Also, I've got a couple questions about CM11 I'm planning to run the 3.0 kernel CM11 version until KK OTA shows up and I'll see where to go from there. How good is the CM11 on RAZR HD? Is there a list of known bugs? And does the HDMI port work? I find it to be a cool feature, although I don't use it often... Would be nice if it works on CM11, too. And the camera, how's it on CM11? I love the 60fps video recordings and hope that photo quality is at least the same, because it really isn't too great on stock JB :/ Using 3rd party camera apps helps to a degree...
Any help, info and answers would be greatly appreciated Thanks in advance!
Cheers
Click to expand...
Click to collapse
have a look at this post.
bweN diorD said:
have a look at this post.
Click to expand...
Click to collapse
Completely missed it... A great post, love it! Question about bootloader unlocking, though - there's the motocalypse way and there's the official way? Or is the official method not available anymore? Any reason why one is better than the other?
And the questions about CM11 remain :
niksy+ said:
Completely missed it... A great post, love it! Question about bootloader unlocking, though - there's the motocalypse way and there's the official way? Or is the official method not available anymore? Any reason why one is better than the other?
And the questions about CM11 remain :
Click to expand...
Click to collapse
The official BL unlock is still available as far as I know, but its not available for all phones. You basically have to try it to know if it will work.
I think the official way is reversible, it has always been said motopocalypse is not. Those facts may be wrong though. There was discussion about it in one of the threads but I don't recall exactly what was stated. If you don't care about ever locking it back, it wouldn't be relevant then.
About cm, I still have my rmhd but haven't used it other than for testing since last year. So I can't provide any current help on that, sorry.
Sent from my LG-VS980 using XDA Premium 4 mobile app
niksy+ said:
Completely missed it... A great post, love it! Question about bootloader unlocking, though - there's the motocalypse way and there's the official way? Or is the official method not available anymore? Any reason why one is better than the other?
And the questions about CM11 remain :
Click to expand...
Click to collapse
Just go to the Motorola web site and look for the unlocking program and attempt it there. Here is the link: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
You'll have to either sign in with your Google+ ID or register an account with Motorola. It's free and then you can attempt to unlock your phone.
The XT925's are always unlockable since they are not in the US. It's Verizon that won't allow it and the XT926s are US phones.
Okay, guys, I've ran into some problems :/
Current status: bootloader loads fine, CWM (6.0.4.4, touch version) loads fine, but the system wouldn't boot after making a backup. I've tried flashing CM11 (cm-11-20140710-NIGHTLY-moto_msm8960-epinter.zip which is supposedly with the 3.0 kernel) and it still will not boot. (I've wiped /system /data and /cache before flashing) All it does is sit at the "Warning bootloader unlocked" screen and it doesn't even become warm...
What I've done: basically, followed all the steps from the thread @bweN diorD posted. Rooted with MotoChopper, unlocked bl with MotoPocalypse and flashed CWM via adb. That was all fine. Then I noticed that CWM keeps disappearing, so I said yes when it asked me if I want it to remove that script from the stock ROM . It also asked "Fix root?" at the same time to which I said yes... Since then the system will not boot. Does anyone know what's gone wrong and what can I do to fix it? Is RSD the only way now?
@bweN diorD @iBolski and everybody else... pretty please :/
*EDIT* Got my stock firmware and flashed it via RSD-lite. Had to remove that check in the xml, but that was it, it has come back to life
Now what puzzles me... Why did the system die after saying yes to "remove the recovery remover script" and "fix root"? And why was CM11 dead on boot, too? Any ideas? :/
*EDIT #2* Nevermind, I'm on CM11 now Rooted again, the bl was still unlocked, installed latest PhilZ recovery and flashed CM11 straight up without even booting stock ROM after installing recovery. All is well! CM11 is so smooth on the R HD that I came a little bit. I loved my petite DEFY+ but this is freaking awesome!
glad you got it worked out
Drivers issue
Guys, I've now got a freaking drivers issue I cannot resolve... Need assistance
I am currently on CM11, on the jbbl. Last time I flashed an sbf was at the time of my previous post in this thread, so 5 months ago. Since then, I have changed my system drive (to an SSD, yay!) and lost the drivers set-up. Back then I was on Win7 x64, now I'm on Win8.1 x64.
At the moment, I cannot get ADB to work (it lists my device, but says it's offline) and cannot get RSD Lite (it's v6.1.6) to detect the phone when in fastboot. I'm attaching a screenshot of device manager's current status. The mot composite adb interface driver is fine, but the two in other devices remain question marks.
Motorola Device Manager (2.4.5) just looks for updates for my device and then quits after finding none. No matter if the phone is connected or not. Not sure if it's incompatible with win8.1 or just normal behaviour since my phone's not on the stock rom.
Does anyone know the right steps for setting up ADB and Fastboot drivers on win8.1 for our device? MTP works fine, no problems there.
*EDIT* Tried using [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer and ADB connects now, but RSD lite still doesn't detect the phone in fastboot. The device manager list looks the same... I hate driver issues >_< And just to be clear, RSD lite does not show anything while the phone is connect as MTP with debugging enabled, too.
*EDIT 2* All fine now. Just uninstalled everything and started from scratch. Drivers that come with Moto Manager are the only requirement.
So I have a problem with my phone [d2303] is just indicating that there is no SIM card. This ONLY happens on the stock lollipop rom. I'm currently on slimrom to test it but I will revert to stock. No the cyanogenmod rom isn't stable enough for me and I don't like kitkat even dough it fixes problems such as bad camera quality... And NO tis isn't just me. I know someone with the same problems but on KitKat ( he's too lazy to update). Recently I've been also getting some errors while moving files to SD card (with the automatic function and manualy). If it helps I can post some screenshots of the problems if it helps....
I'm starting to get frstrated with this phone and is it a software or hardware problem? Should I take it to service and if so will they accept my phone because I have allredy unlocked my bootloader? Is there an efficient method of relocking a bootloader (links to posts are enough)? I've used the flastool method to unlock the bootloader on my phone(link- http://forum.xda-developers.com/showthread.php?t=2743694).
Is anyone having the same problems?
I also have some experience in rooting and installing costom roms on a few phones so if you know a software solution or a fix I won't have problems installing it.
I am thankful for you at least reading this thread. Also thank you for all your responses in advance.
slole said:
So I have a problem with my phone [d2303] is just indicating that there is no SIM card. This ONLY happens on the stock lollipop rom. I'm currently on slimrom to test it but I will revert to stock. No the cyanogenmod rom isn't stable enough for me and I don't like kitkat even dough it fixes problems such as bad camera quality... And NO tis isn't just me. I know someone with the same problems but on KitKat ( he's too lazy to update). Recently I've been also getting some errors while moving files to SD card (with the automatic function and manualy). If it helps I can post some screenshots of the problems if it helps....
I'm starting to get frstrated with this phone and is it a software or hardware problem? Should I take it to service and if so will they accept my phone because I have allredy unlocked my bootloader? Is there an efficient method of relocking a bootloader (links to posts are enough)? I've used the flastool method to unlock the bootloader on my phone(link- http://forum.xda-developers.com/showthread.php?t=2743694).
Is anyone having the same problems?
I also have some experience in rooting and installing costom roms on a few phones so if you know a software solution or a fix I won't have problems installing it.
I am thankful for you at least reading this thread. Also thank you for all your responses in advance.
Click to expand...
Click to collapse
Did you used flash ftf? I think main reason is you didn't flashed baseband. If this still happens, go to the service with relocking bootloader. I went to the service for dead pixel with relocking bootloader, they swapped my device.
This started appearing before I flashed any rom or unlocked the bootloader, so basically when the phone was stock. Also I'm not sure what is a baseband. I flashed a tft from a xda post with a youtube video with downloads for all android versions and xpria m2 models. The problem seems to be less frequent if I don't use the phone as much. I'll tryt his method: [It's on techbeasts but i'm not alowed to link outside links yet] to restore to stock and relock bootloader maybe even kitat since it has better camera quality. If the problem doesn't go away I'll take the phone to service because I want a reliable phone.
Thanks for the reply I almost gave up on this post. I saw a lot views but no replies this might mean that a lot of people have the same problem.
I'll also post some status updates about my problem so this post can be as an instruction to people with the same problem.
slole said:
This started appearing before I flashed any rom or unlocked the bootloader, so basically when the phone was stock. Also I'm not sure what is a baseband. I flashed a tft from a xda post with a youtube video with downloads for all android versions and xpria m2 models. The problem seems to be less frequent if I don't use the phone as much. I'll tryt his method: [It's on techbeasts but i'm not alowed to link outside links yet] to restore to stock and relock bootloader maybe even kitat since it has better camera quality. If the problem doesn't go away I'll take the phone to service because I want a reliable phone.
Thanks for the reply I almost gave up on this post. I saw a lot views but no replies this might mean that a lot of people have the same problem.
I'll also post some status updates about my problem so this post can be as an instruction to people with the same problem.
Click to expand...
Click to collapse
You must go to the service bro, it seems a serious problem
JuniorCaesar said:
You must go to the service bro, it seems a serious problem
Click to expand...
Click to collapse
Yes, i will but it sounds like a a manufacturing problem since I also know someone else having the same SIM card problem
slole said:
Yes, i will but it sounds like a a manufacturing problem since I also know someone else having the same SIM card problem
Click to expand...
Click to collapse
This phone's problems not limited with sim card, also screen, camera and many more. M2 series are not good.
Don't agree with you sorry, my m2 hasn't missed a beat in over a year of serious use apart from when it's something I've done to it myself tweaking and changing things maybe I've been lucky even gonna keep it when I get my upgrade in a few months(Xperia of course).
[email protected] said:
Don't agree with you sorry, my m2 hasn't missed a beat in over a year of serious use apart from when it's something I've done to it myself tweaking and changing things maybe I've been lucky even gonna keep it when I get my upgrade in a few months(Xperia of course).
Click to expand...
Click to collapse
I love my 2303 too, but I used 4 m2, this doesn't mean all m2's are damaged But mostly of them are little produce damaged (Example, when you pushed screen on normal touch, you can see LCD liquid moving or find dead pixels)