I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Jeffril said:
I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Click to expand...
Click to collapse
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
NoDze said:
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
Click to expand...
Click to collapse
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Jeffril said:
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Click to expand...
Click to collapse
Okay, This is SFSP by @sgspluss which is a pretty fast, stable and battery-friendly slimmed down version of stock ICS. It is available for both Old and NewBL, so you might want to try that first. This is AIO Toolkit. I know that you've used it and bricked your phone, but try again, and for the love of God install the nvflash drivers because most people skip that part. You have to do it manually and if you're running Windows 8 you need to disable Driver Signature Verification. But yeah, you switch bootloaders with this.
Related
I have tried a couple of custom roms and they have all worked fine at first but then after a while most of them would do something like force close whenever i try to open anything. This is getting really frustrating. I have a build 1009 and im looking at phoenix 3.0 and perception 10.0 both look really nice. Could someone tell me what im doing wrong and how to fix it. Every time i try to enable third party apps recently or something else ( I can't remember specificly what it was but it was rooting it or something) it will do the blah blah something apcore stoped working force close so right now im just going to use my phone on stock firmware and use it like normal and see what happens but could someone help me. I have used gingerclone, Assonance (force close problem), Darky 8.0 with the captivate workaround (force close problem), and maybe a few others but those are the only ones i can remember.
Custom roms are rooted with side loading enabled. So if you are trying to do this after you have the rom loaded, that could be a problem. I also would like to know what you are restoring on these roms. Should only be user apps.
To pin point your problem please provide more detail
I have put apps from custom roms onto the stock rom and other roms. Could that be the problem? And also this is what im going back to.
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
Im only doing the first part im not going to jh7. would that have something to do with it. Any help is greatly appriciated.
yamato2 said:
I have put apps from custom roms onto the stock rom and other roms. Could that be the problem? And also this is what im going back to.
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
Im only doing the first part im not going to jh7. would that have something to do with it. Any help is greatly appriciated.
Click to expand...
Click to collapse
What apps?
I do not think only going back to jh7 would cause your issue. Tell me more about what you are trying to do to enable side loading, and why you are doing it on as custom rom
I had the ones i downloaded and i sideloaded one wireless tether app a long time ago then i backed it all up with titanium backup and i would install a custom rom and it would have roms preinstalled on it. I would want to put on a different custom rom so i backed up again and the flashed back to stock the to the new rom. and i would restore all the apps including the one from previous roms. If you are asking for the specifics it would take a while and about the side loading i followed the guide http://forum.xda-developers.com/showthread.php?t=738376 and did the method 3 it seemed to work fine until i rebooted and then it did the force close thing. And i didn't go to jh7 i went to jh6 or jh2 or something like that but im going to try going to jh7 and see if that helps.
dont restore ALL apps in Titanium Backup. safest option is "restore missing apps+data"
all the custom 2.2 roms have tethering/wifi hotspot built into them...no need for another app for it.
for custom roms, you DO NOT need to root or sideload...they are enabled by default on all custom roms.
Thank both of you for your help. I will probably for now only install roms specificly for captivate and with specific instructions.
hey guys i just got my nexus one 2.3.3
im confused what 2 do first
root, unlock bootloader
what 2 do first?
and i preffer to do all these things WITHOUT adb, bcoz adb never works with me
You can't unlock bootloader without ADB (or actually without fastboot, but if you can't get ADB to work, then you probably won't be able to get fastboot to work - since they work the same way).
My suggestion is - do nothing. At least until you'll be able to follow one of the guides and get ADB and fastboot to work. Then you can decide yourself, whether you want the bootloader unlocked or not, and how will rooting benefit you.
what are the benefits of unlocked bootloader?
i just wanted it to get it rooted and flash CM7 on it
It has been discussed a lot, please search to get A LOT of answers.
In a very short version, the benefits are:
Safe radio updates (using fastboot)
Ability to flash whatever you want whenever you want - which is, permanent ability to have root access, regardless of the currently used OS.
but is it possible to flash CM7 rom without unlocking bootloader?
whenever i boot my nexus one, there is this little lock icon on the bottem that is "unlocked"
is my bootloader unlocked?
shiyou said:
but is it possible to flash CM7 rom without unlocking bootloader?
whenever i boot my nexus one, there is this little lock icon on the bottem that is "unlocked"
is my bootloader unlocked?
Click to expand...
Click to collapse
If there's lock icon at the bottom of boot splash screen, it means the bootloader is already unlocked. Is it used one?
yes its used, i guess that guy alrdy unlocked it for me
another problem
i have serius wifi issue, its different from the other wifi problem
if i connect to my wifi its authenticating, then disabled
i dont even go to sleep its just says disabled after authenticating, i tried reconecctint but same things happens again...
i installed wifi fixer but that doesnt work either
also, my 3g drops after 4 sec and i cant get it to work afterwards
Flash a new ROM, wipe your data, and try.
Repeat.
If the problems will still persist - they're in HW and you can't do anything about them.
i tried factory reset but didnt work...
This is exactly the reason why I suggest not touching your phone.
You either don't understand what exactly I'm guiding you to do, or don't understand the difference between various maintenance/repair operations. Flashing a new ROM and wiping user data from custom recovery ISN'T the same as doing "factory reset" from within already-installed ROM. Flashing 2 ROMs with different base (for example, lightly modified stock and CM7, or CM7 and MIUI, etc) introduces enough difference on the SW size to (almost) make sure that any problem which persists in both new ROMs, is coming from HW.
In any case, I suggest either waiting for someone with much more patience than myself (which isn't hard - patience isn't one of my strengths) to explain you some basics that you're not willing to learn yourself by reading, reading and some more reading, or to give your phone to someone who knows what he's doing.
dude....
i rooted and flashed many roms b4, this isnt my first android phone
i just got confused data wipe with factory reset....
Ok well now I need to know if you have a custom recovery, if so then just 5X wipe plus 3X system wipe and flash a new ROM, if not then do you have root access if not I'll walk you through the process.
shiyou
You are in good hands with Dude
Couple points:
Don't use Clockwork Mod 3.+ as recovery--which seems to be your next step--get a lower version
I prefer Amon_Ra 2.2.1 for my recovery
BACKUP phone (NANDROID) as soon as you get the recovery
Look thru Cyanogen thread from OP page and last few dozen pages
Cyanogen flashes a little differnet with having to flash gapps separate and flashing Dark Tremor's a2sd after each Nightly flash
i know how 2 root,flash,wipe, nandroid and all
i did it many times b4
i think i wont use nightly builds, but a stable? or RC?
which should i take?
How about cm7.1 RC1 that is the latest version of cyanogen mod.
rugmankc said:
shiyou
You are in good hands with Dude
Couple points:
Don't use Clockwork Mod 3.+ as recovery--which seems to be your next step--get a lower version
I prefer Amon_Ra 2.2.1 for my recovery
BACKUP phone (NANDROID) as soon as you get the recovery
Look thru Cyanogen thread from OP page and last few dozen pages
Cyanogen flashes a little differnet with having to flash gapps separate and flashing Dark Tremor's a2sd after each Nightly flash
Click to expand...
Click to collapse
why not clockwork recovery 3? the cyanogenmod rc1 states that i need that?
should i use gingerbeak? im on 2.2.3 and install the recovery afterwards?
ok i rooted it with gingerbreak and flashed clockworkmod recovery on it
after that i went into recovery and couldnt find nandroid backup so i rebooted again
i tried to make a backup via rom manager and it ended up with a "!" icon
i tried to go into recovery again and again i got the "!" icon
I don't know anything about Gingerbreak
But, on CWMod 3.+, it has been unstable for a lot of people--I don't recommend it
If you have Rom Manager--flash something like 2.5.1.4??
Still recommend Amon_Ra
I am not sure, but if you get the exclamation, you may not be rooted
If you are experienced at flashing, I would as another poster suggested--get to know your phone and study hard info from the Rom threads you want to try before trying.
What color was recovery--did it say ClockWork
I don't think you will see the name Nandroid in Clockwork--just Clockwork backups
A couple more suggestions, if you want
Back up sd card regularly--you will lose it on occasion--if you need to reformat it, use sdformatter outside of phone
Partition sdcard with zero swap
Wipe all (data/caches) multiple times before flashing new rom, including System
I need a bit of urgent advice if possible. Having waited patiently for Samsung to release ICS for the P7310 which has never appeared in the UK, I'm trying to flash to JB (latest AOSP version) from the stock 3.2.
I've installed CWMOD 5.5.0.4 ok, and copied the update rom and gapps to the root of the tab. I've gone into CWMOD recover mode, wipe/reset and then selected the rom to install. It starts the install, then fails with the system error 7 message (seems to be fairly common). It obviously started the install but now I don't seem to be able to boot the tab into 3.2 anymore, it just sits at the boot logo and doesn't get any further. I'm happy to try another ROM (maybe CM10), but I need to transfer it to the device first, and ofcourse I can't do this within windows at the moment. Odin still runs and can talk to the tab, but I'm a bit lost at the moment.
I'm a bit new to all this, so could really do with some help.
Flash the stock Rom.with Odin. You can find it at sammobile.com. it'll bring you back to stock.and.you can start over again. You're soft bricked right now.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Cool. Thanks for that. I guess I just select the PDA option in Odin, and let it do its thing.
Any idea why this happens? I'd read a couple of threads about going from HC to ICS first, then to JB. Is this a requirement, or optional?
I'ver had similar problems finding a Rom that works on my i957. Never did find an ics that worked. I'm running jb from nrvate, but I think its specific to the i957. And, yes, flash just like you did the cm recovery.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Really appreciate the replies. I've managed to get the tab back working under 3.2 (stock rom downloaded from SamFirmware), so that's a start. I still want to upgrade to JB if possible (or ICS if not). Am I likely to experience the same problem again? Is it worth going to ICS first? I've downloaded the stock US ICS rom, which i can flash using Odin. I can't see why this wouldn't work on a UK spec 8.9 wifi, but can anyone confirm if it does?
So, I'm back at square one, but really want to try and get this sorted.
Did you do a clean install when you tried to flash the jb Rom? I.e. factory reset, format/clear system and data. If not that probably is the problem. There should not be any benefit of flashing ics before jb. The one difference between the two is you most likely will have to flash a gapps (Google apps) package after the the jb flash. Not sure where you got the Rom, but the developer should have the gapp they recommend and instruction on how to do the flash. Every jb to Rom I've flashed has the gapps package flashed after the Rom and before rebooting.
I'd stick with a Rom specific for your device. I hard bricked my phone with the wrong Rom once. The US Rom probably does not have the correct radio for.you in the UK. I only use WiFi so don't care too much if I have the right radio or.not.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
Did you do a clean install when you tried to flash the jb Rom? I.e. factory reset, format/clear system and data. If not that probably is the problem. There should not be any benefit of flashing ics before jb. The one difference between the two is you most likely will have to flash a gapps (Google apps) package after the the jb flash. Not sure where you got the Rom, but the developer should have the gapp they recommend and instruction on how to do the flash. Every jb to Rom I've flashed has the gapps package flashed after the Rom and before rebooting.
I'd stick with a Rom specific for your device. I hard bricked my phone with the wrong Rom once. The US Rom probably does not have the correct radio for.you in the UK. I only use WiFi so don't care too much if I have the right radio or.not.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
I've just tried again, and have hit the same problem, and have tried the AOSP rom and the CM10 rom this time. I did a wipe/factory reset beforehand, but the installer starts then just aborts with 'symlink: some symlinks failed' E:Error in /sdcard/<rom file name> (Status 7). Obviously the tab 8.9 doesn't have an sd card slot, but I thought the rom must be aware of this.
Where am I going wrong?
You might try to flash a different version of cwm I don't remember now how I found this link, but here is a link for Overcome_CWM_Recovery_v5.1.2.6_P73xx.tar
http://www.sendspace.com/file/507gjv
just flash in Odin, like the ROM itself (in PDA section)
I use twrp but don't know where to find a version for your p7310.
Have you tried a different Rom
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
You have a /sdcard directory despite the fact you have no physical external sdcard.
I had the same problem. Found this solution:
http://forum.xda-developers.com/showthread.php?t=1973712
tman24 said:
I've just tried again, and have hit the same problem, and have tried the AOSP rom and the CM10 rom this time. I did a wipe/factory reset beforehand, but the installer starts then just aborts with 'symlink: some symlinks failed' E:Error in /sdcard/<rom file name> (Status 7). Obviously the tab 8.9 doesn't have an sd card slot, but I thought the rom must be aware of this.
Where am I going wrong?
Click to expand...
Click to collapse
harry_fine said:
You have a /sdcard directory despite the fact you have no physical external sdcard.
I had the same problem. Found this solution:
http://forum.xda-developers.com/showthread.php?t=1973712
Click to expand...
Click to collapse
If reading that reply right, one specific stock rom does what's necessary, trouble is, that's a US stock rom, and I'm in the UK. Already had it confirmed that it wouldn't be good to install a US rom on a UK tab. Loads of people has flashed their tabs, so it can't be that difficult! I've just tried Overcome CwM v5.2.1.6 with the same AOSP and CM10 roms, but same error
Ok, silly question time, but does the tab need to be rooted to install these new roms successfully?
You don't need to be rooted, just the recovery installed. Not sure why you're having problems now other than I had a hell of a time getting a Rom installed too. I'd try a different Rom. I tried some yesterday and didn't get any of them to work well. At least you've learned how to recover from a soft brick. I've learned that lesson too, to many times!
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
I'd try to download CM10 again. As i see in the error message there is a problem with the zip, maybe caused by error in downloading?
tman24 said:
If reading that reply right, one specific stock rom does what's necessary, trouble is, that's a US stock rom, and I'm in the UK. Already had it confirmed that it wouldn't be good to install a US rom on a UK tab. Loads of people has flashed their tabs, so it can't be that difficult! I've just tried Overcome CwM v5.2.1.6 with the same AOSP and CM10 roms, but same error
Click to expand...
Click to collapse
Hi, dont know if this will help, but I have flashed the US ICS rom on my Swiss Tab 8.9, with no problems. There should be no issue with worrying about the wrong radio as stated previously, as the 7310 is the WIFI only model, so there should be no issue with 3G. The only thing which causes some issues is the screen flicker issue. If you flash the US gingerbread first, then the ICS, it seems to solve the issue. For mor info check out this thread http://forum.xda-developers.com/showthread.php?t=1573548&page=50
Good luck!
Aaarrgggh! Frustrating, now I'm just getting 'hardware id not found' when I connect the tab to the PC!!! I can browse the device in Windows, but of course, Odin won't connect. How difficult can this really be!
I've already uninstalled and re-installed the Samsung USB drivers, tried a different USB port etc, but same result.
As it stands, the tab is working, but on that horrible v3.2.
I might be getting somewhere, but nothing's easy! I have moved everything over to a laptop we have, and have gone through the whole process again. I installed CwM ok using Odin, copied over the AOSP beta13 for the 7310, and this time when I installed the ZIP, it said completed ok. Good so far.
I then rebooted, and while I see the Samsung logo, the screen then goes black and stays that way. I've left it ages, but it doesn't seem to get anywhere. I can still reboot it and get into download/recovery, so that's ok. Am I doing anything wrong? I did the wipe/reset beforehand, so It's not obvious why this is not working.
Quick update. I can get ICS running (CM9 works), so that's good. It does look like any JB rom (AOSP/CM10) just cause a blank screen on reboot, which is wierd. I've re-downloaded the ROM's just in case, but no dice. Install completes ok, and gapps reports no problems.
I often don't get a boot animation, just the black screen. Every once in awhile the animation comes back. Seems totally random. I'm using nravates jb Rom on the i957. Other than that it runs great.
Sent from my SGH-I727 using xda app-developers app
Hello!
I'm new to posting to this forum, so you can call me a noob. I'm sure I am a noob, I'm sure I did something wrong. I was just a customer for the time when GingerDX development started for Xperia X8, my previous phone. I'm not a dev, but I know know to flash stuff and what to avoid or do with care. If this thread is in the wrong section, then sorry, please move it where it should be.
Three months ago I got my new shiny GT-I9305, version for Poland (distributed by Plus), and as I did with my X8 previously, I decided to root it and dive into flashing many custom ROMs.
I made the EFS backup following lyriquidperfection's thread (http://forum.xda-developers.com/showthread.php?t=1946915), so my IMEI and NV items are safe and secure. I also did a backup of a stock 4.1.2 ROM.
I was using many different ROMs and kernels from XDA, both based on CM10.1 and Official Samsung ROM. I had PhilZ Touch 5 recovery installed. Everything worked fine, until I noticed something strange:
After I flashed an unofficial port of SlimBean to I9305 (http://forum.xda-developers.com/showthread.php?t=2297679), and Yank555 kernel for CM10.1 based ROMs, I noticed that in "About phone" section, my phone is shown as "GT-I9300", but I'm 100% sure I flashed the file that had I9305 in the filename, so it couldn't be my mistake. I didn't buy I9305 for 4G, but for 2 GBs of RAM, so I couldn't test if LTE was working (My carrier is T-Mobile.pl, which doesn't have 4G in Poland yet), but I didn't see the option to even search for LTE networks available. I didn't care much about that, since everything else was working just fine.
I decided to flash the previous ROM I was using - Sentinel Rom, because I found the bug with GPS and I wanted to see if the same happens in that rom. I rebooted to recovery, but... I couldn't install the package. It was all giving the "set_perm some changes failed (status 7)" error all the time. The same happened when I tried to install LiquidSmooth for i9305. I just couldn't flash any 4.2.2 ROM, I was able to flash a kernel just fine.
I decided to flash Ripper Rom instead. It installed with no error, it just said: "Root access is missing, root the device?" so I simply said to root it. But the phone couldn't normally boot. It stayed for a while at the "Samsung Galaxy SIII GT-I9305" splash screen with the little red exclamation mark in the top left corner, then it kept rebooting back to recovery. I had no idea what's going on. Wiping data/cache/dalvik cache/system didn't help at all. The only way to make the phone working again was to recover SlimBean from Nandroid backup I had done previously. Sadly, I had no Sentinel Rom backup. Deleted it. Shame on me.
I successfully restored Stock 4.1.2 rom from the nandroid backup, but I still couldn't install any custom ROM via recovery because of the same error.
After several tries to install different ROMs, redownloading everything and going through a lot of stress I gave up. I installed TriangleAway, reset the flash counter and, through Odin, flashed tar.md5 of the stock ROM delivered by Plus, downloaded from here: http://goo.gl/SMWEha. I installed a version build XXBLL3, which later updated itself to XXBMB4, and baseband updated from XXBLL3 to XXBMA2.
Right now, I have Official, Stock 4.1.2 ROM from Plus, with Baseband version I9305XXBMA2, build number JZO54K.I9305XXBMB4 and stock kernel.
What Download mode says:
Product Name: GT-I9305
Custom binary download: No
Current Binary: Samsung Official
System Status: Official
Now to the questions:
Why this started happening? Was the reason the wrong model of the phone in "About phone", hence installing SlimBean?
When I flashed the stock ROM, does it mean that I'm fully back to stock, with everything removed? Does it mean that my phone is like I got it from the box, with warranty? The recovery seems stock as well.
Can I root it again? If yes, how to do it safely, to not make something like that happen again?
Baseband got updated. Does it mean I have to make an EFS partition backup again?
Sorry if I ask too much, but I'm a very careful person, and I want to know everything before I start doing anything risky with my smartphone.
Thanks in advance.
General thread read the basics all stickied .
jje
I read every sticky thread and I can't find the answer to my questions. That's why I'm asking.
When I flashed the stock ROM, does it mean that I'm fully back to stock, with everything removed? Does it mean that my phone is like I got it from the box, with warranty? The recovery seems stock as well.
That is answered in the how to return to stock for warranty thread .
Root again yes follow the instructions .
EFS again that is in the faqs and guides no you dont have to but its safer to do so .
Why this started happening >>> User error who knows where as multiple roms stuff flashed .
jje
I rooted the phone again using the Galaxy S3 toolkit and every time I try to install the custom ROM through TWRP I get the error:
set_perm: some changes failed (status 7)
Then the phone doesn't want to boot (reboots to recovery all the time), only a restore of a Stock 4.1.2 from nandroid backup helps.
Ideas?
Seriously? Anyone?
Flashing 4.1.2 ROM (Ripper Rom) gives the same exact effect. Rom flashes correctly, but the phone cannot boot into system, reboots to recovery.
I have a rooted Droid 4 running 4.1.2. I have only flashed a ROM onto a phone once before, on an LG Ally a few years ago. So I'm proceeding cautiously. I've tried to do some research and just confused myself further. I'm just going to post my questions here and hopefully you guys can help. I appreciate it in advance.
1. I don't have custom recovery on the phone yet. It's just rooted at this point. What recovery would you guys recommend? I've seen some references to GooManager -- would that app automate the custom recovery installation for me, or do I need to download Safestrap or something like that to the computer and install from there?
2. Do I have to root again after that?
3. What is the highest current stable version of Cyanogenmod that will run on this phone?
Cannonball3804 said:
I have a rooted Droid 4 running 4.1.2. I have only flashed a ROM onto a phone once before, on an LG Ally a few years ago. So I'm proceeding cautiously. I've tried to do some research and just confused myself further. I'm just going to post my questions here and hopefully you guys can help. I appreciate it in advance.
1. I don't have custom recovery on the phone yet. It's just rooted at this point. What recovery would you guys recommend? I've seen some references to GooManager -- would that app automate the custom recovery installation for me, or do I need to download Safestrap or something like that to the computer and install from there?
2. Do I have to root again after that?
3. What is the highest current stable version of Cyanogenmod that will run on this phone?
Click to expand...
Click to collapse
1. I don't know anything about GooManager or if it is compatible with the D4 but safestrap is a really great piece of software that is easy to use. I highly recommend it. Just download and install the app on your phone. Then open the app and install recovery. From there, when you reboot, you will be given the option to boot into safestrap recovery where you can install your ROMs.
2. You will not need to re-root your phone.
3. I am running CM10.2 (Android 4.3) nightlies and have found them to be very stable. I've also heard the latest stable version of CM10.1 (Android 4.2.2) is very good as well.
Now I have a Wi-Fi problem
kwyrt said:
1. I don't know anything about GooManager or if it is compatible with the D4 but safestrap is a really great piece of software that is easy to use. I highly recommend it. Just download and install the app on your phone. Then open the app and install recovery. From there, when you reboot, you will be given the option to boot into safestrap recovery where you can install your ROMs.
2. You will not need to re-root your phone.
3. I am running CM10.2 (Android 4.3) nightlies and have found them to be very stable. I've also heard the latest stable version of CM10.1 (Android 4.2.2) is very good as well.
Click to expand...
Click to collapse
Thank you. I got CM10.2 nightly for 9/28 installed and working. There is only one problem I found so far -- I can't get wi-fi to connect at home. It says it's authenticating, then it saves, then it says there is an authentication problem. I have no problems when I run stock, but it will not work with CM 10.2
I researched online and found lots of people having problems. Some people re-flashed the ROM and it fixed it, others tried this, that or the other and weren't even sure what fixed the problem. Some never fixed it at all.
I did the Wipe/Factory Reset. I re-flashed the ROM. I went back and flashed the 9/27 nightly since 9/28 didn't work. I rebooted my router. I did a Forget on the network and re-added it. My password is correct. I'm at a loss. Not having WiFi with this ROM is like having a great new car that does everything you want except it doesn't do left turns.
Cannonball3804 said:
Thank you. I got CM10.2 nightly for 9/28 installed and working. There is only one problem I found so far -- I can't get wi-fi to connect at home. It says it's authenticating, then it saves, then it says there is an authentication problem. I have no problems when I run stock, but it will not work with CM 10.2
I researched online and found lots of people having problems. Some people re-flashed the ROM and it fixed it, others tried this, that or the other and weren't even sure what fixed the problem. Some never fixed it at all.
I did the Wipe/Factory Reset. I re-flashed the ROM. I went back and flashed the 9/27 nightly since 9/28 didn't work. I rebooted my router. I did a Forget on the network and re-added it. My password is correct. I'm at a loss. Not having WiFi with this ROM is like having a great new car that does everything you want except it doesn't do left turns.
Click to expand...
Click to collapse
Sounds like you have tried most of the things I would have tried to fix it. One other thing you can try: open the Terminal app. Type "SU" and press enter. Then type "wificall.sh" and press enter. That will recalibrate the wifi on the phone. One other thing that comes to mind is I remember some people mentioning when they flashed a new ROM the D4s MAC address got changed which screwed with the wifi connection to their router. I can't remember what the fix was for it, but might be something to google if wifical does not fix it.
kwyrt said:
Sounds like you have tried most of the things I would have tried to fix it. One other thing you can try: open the Terminal app. Type "SU" and press enter. Then type "wificall.sh" and press enter. That will recalibrate the wifi on the phone. One other thing that comes to mind is I remember some people mentioning when they flashed a new ROM the D4s MAC address got changed which screwed with the wifi connection to their router. I can't remember what the fix was for it, but might be something to google if wifical does not fix it.
Click to expand...
Click to collapse
Thanks for the wifical tip. Wi-Fi is now working at my office. When I get home, I'll see if it did the trick there.
Cannonball3804 said:
Thank you. I got CM10.2 nightly for 9/28 installed and working. There is only one problem I found so far -- I can't get wi-fi to connect at home. It says it's authenticating, then it saves, then it says there is an authentication problem. I have no problems when I run stock, but it will not work with CM 10.2
Click to expand...
Click to collapse
Wifi has been hit and miss lately. I had to go back to 9/26 nightly. Didn't have working wifi until 10/2 nightly.
Some of the guys in the development thread found some clues as to why. The must be working on the wifi drivers in the nightlies right now.
http://forum.xda-developers.com/showthread.php?t=2102723&page=83
I just flashed the latest CM (this is my first phone mod) and I working on getting gapps to instal. I have the latest downloaded and am looking for guidance as to how to install the package. This thread looks like a proper place to address that step as it appears to be exactly what you do after you get CM running.
Thanks!
Huli13 said:
I just flashed the latest CM (this is my first phone mod) and I working on getting gapps to instal. I have the latest downloaded and am looking for guidance as to how to install the package. This thread looks like a proper place to address that step as it appears to be exactly what you do after you get CM running.
Thanks!
Click to expand...
Click to collapse
Find the gapps for your version of cm and flash like you did the ROM. Usually you would flash the gapps when you do the ROM.
Sent from my XT894 using Tapatalk
Cannonball3804 said:
I have a rooted Droid 4 running 4.1.2. I have only flashed a ROM onto a phone once before, on an LG Ally a few years ago. So I'm proceeding cautiously. I've tried to do some research and just confused myself further. I'm just going to post my questions here and hopefully you guys can help. I appreciate it in advance.
1. I don't have custom recovery on the phone yet. It's just rooted at this point. What recovery would you guys recommend? I've seen some references to GooManager -- would that app automate the custom recovery installation for me, or do I need to download Safestrap or something like that to the computer and install from there?
2. Do I have to root again after that?
3. What is the highest current stable version of Cyanogenmod that will run on this phone?
Click to expand...
Click to collapse
1. I prefer safestrap, you can install up to 4 more ROMs in addition to stock ROM. And it's the safest method to try those ROMs
2. That depends on the ROM you are going to install. Most custom ROMs have been rooted already.
3. CM11 that is Android 4.4 KitKat, sweet eh? (correction : CM11 is not stable development yet, but it is latest and nicely working)