Hello, using my husband's old skyrocket as main driver, pleasantly surprised with how much I'm enjoying using it...thought there'd be more lag etc. And was thrilled to find continued development. (Couldn't find my old sign in info BTW) Anyway apparently I'd rooted and unlocked it and put a gingerbread debloated stock rom on it when he first got it, as that was there...tried candy 5, loved, but needed more app space. Tried app2sd and just messed that up...Tried cyanogen, read instructions, did things a little differently (unintentionally) at first, somehow not registering the fact that the official twrp was for virtually repartitioning, tried to repartition it in the modified version, of course it didn't work, finally gave up and flashed ROM anyway and gapps (tried both nano and pico from link. )
I'm not sure how but it did install and basically seemed tp work, the only issue seemed to be keyboard force closing and later the browser and root issues. I wondered if something I had done originally with phone contributed to why it installed if it shouldn't have been able to. MMS (cricket) won't work on this or candy5, tried several radios and apns.
Anyway I saw what I did wrong with twrps, figured that would fix things, virtually partitioned correctly, seemed to have same issues and intact kept adding more... tried many times: wiping reformatting, clean install, dirty, reflashing whatever...it just seemed worse every time...everything force closing including settings.
I have no clue what happened, what I was doing wrong, gapps I read should have a script added to the ROM to prevent the force closing, and Im assuming it is there....also though a couple times offered to have rooted in twrp it never seemed to do it, never worked right if I tried anything manually instead, caused more shutdowns. Something abt pit file in instrutions makes me wonder if something i had done before could cause issues? Cant remember what that was specifically though. Thanks! And I apologize if this is hard to follow or or makes no sense. Probably. BC it really doesn't haha....BTW I did read anything I could find so if I a missed something obvious I apologize.
T.Leela said:
Hello, using my husband's old skyrocket as main driver, pleasantly surprised with how much I'm enjoying using it...thought there'd be more lag etc. And was thrilled to find continued development. (Couldn't find my old sign in info BTW) Anyway apparently I'd rooted and unlocked it and put a gingerbread debloated stock rom on it when he first got it, as that was there...tried candy 5, loved, but needed more app space. Tried app2sd and just messed that up...Tried cyanogen, read instructions, did things a little differently (unintentionally) at first, somehow not registering the fact that the official twrp was for virtually repartitioning, tried to repartition it in the modified version, of course it didn't work, finally gave up and flashed ROM anyway and gapps (tried both nano and pico from link. )
I'm not sure how but it did install and basically seemed tp work, the only issue seemed to be keyboard force closing and later the browser and root issues. I wondered if something I had done originally with phone contributed to why it installed if it shouldn't have been able to. MMS (cricket) won't work on this or candy5, tried several radios and apns.
Anyway I saw what I did wrong with twrps, figured that would fix things, virtually partitioned correctly, seemed to have same issues and intact kept adding more... tried many times: wiping reformatting, clean install, dirty, reflashing whatever...it just seemed worse every time...everything force closing including settings.
I have no clue what happened, what I was doing wrong, gapps I read should have a script added to the ROM to prevent the force closing, and Im assuming it is there....also though a couple times offered to have rooted in twrp it never seemed to do it, never worked right if I tried anything manually instead, caused more shutdowns. Something abt pit file in instrutions makes me wonder if something i had done before could cause issues? Cant remember what that was specifically though. Thanks! And I apologize if this is hard to follow or or makes no sense. Probably. BC it really doesn't haha....BTW I did read anything I could find so if I a missed something obvious I apologize.
Click to expand...
Click to collapse
You need to flash stock GApps. Dunno why, but for some reason it just works.
And with the repartition, you have more than enough space for that.
By the way, the Settings FCs are from a bad update. Flash 12/6 and you're good.
Sent from my SGH-I727 using Tapatalk
Related
I said I would flash cyanogenmod on a friends G1 because he was fed up with 1.6. I've flashed many custom ROM's on several different devices before but I've made a mess of things with this G1 and I can hardly hand back an unusable phone so I would really appreciate your help.
I rooted the phone using Androot, backed up the apps and settings using titanium backup and then the texts using a text backup app. I then downloaded Rom manager and flashed the latest clockworkmod recovery. Next I downloaded the latest official cyanogenmod rom for the dream/g1 and placed it on the phones SD card using my computer. I then re-opened rom manager and used it to select the zip file from the sd (to flash it) on prompt I checked two boxes one to wipe data and one to wipe the dalvik cache and pressed ok.
The phone rebooted into the recovery wiped the stuff, supposedly flashed the rom and rebooted. However it got stuck on the t-mobile g1 boot screen(it never showed anything else first or anything after) I left it for ages with no joy. I then tried wiping from the recovery and flashing again - same thing so i put cm5 on and tried flashing that. Same problem. Then i realised that it probably would not work because I would need to use DangerSPL as the /system partition is too small on the dream/g1. To be honest at this point I can't be bothered with to do that and this guy will be happy with anything above 1.6 to be honest so I thought I would try and flash CM4 because that's based on Eclair I believe (and so it not require I use DangerSPL or any other method to repartition the NAND). However, I tried it twice and still no luck.
At this point I'm somewhat panicking as I cannot seem to make the phone boot and it isn't even mine! Is anyone able to help?
Anyone? Please?
Look, at this stage I will forget custom roms etc. If anyone can tell me the easiest way to get this phone booting android again i would be very grateful.
Even if you could just tell me exactly how to restore it to stock 1.6 from here?
I have flashed roms on phones before - never had a problem but this is driving me crazy - please help!
wollac11 said:
Hi I said I would flash cyanogenmod on a friends G1 coz he was pissed off with 1.6 but im having trouble and I can hardly hand back an unusable phone so i really need your help.
I rooted the phone using Androot, backed up the apps and settings using titanium backup and then the texts using a text backup app. I then downloaded Rom manager and flashed the latest clockworkmod recovery. Next I downloaded the latest official cyanogenmod rom for the dream/g1 and placed it on the phones SD card using my computer. I then re-opened rom manager and used it to select the zip file from the sd (to flash it) on prompt I checked two boxes one to wipe data and one to wipe the dalvik cache and pressed ok.
The phone rebooted into the recovery wiped the stuff, supposedly flashed the rom and rebooted. However it got stuck on the t-mobile g1 boot screen(it never showed anything else first or anything after) I left it for ages with no joy. I then tried wiping from the recovery and flashing again - same thing so i put cm5 on and tried flashing that. Same problem. Then i realised that it probably would not work coz i would need to use DangerSPL coz the /system partition is too small on the dream/g1. Tbh i'm tired so I cba to do that and this guy is not that technical so he will be happy with anything above 1.6 so I thought I do CM4 coz thats 2.0 or 2.1 i seem to remember (and it not require I use DangerSPL) - tried it twice and still not luck.
HOW THE HELL CAN A GET THIS STUPID THING TO WORK AGAIN!??
MAJOR PANIC AS THIS IS NOT MY PHONE - PLEASE HELP!!!
Click to expand...
Click to collapse
Try this thread: http://forum.xda-developers.com/showthread.php?t=803482. I hope it helps.
It's been way too long since I rooted mine to be of any real help but I shall try nonetheless.
Firstly, there is a guide in the G1 forum to unroot and get back to stock firmware: Here (but note that I've never done this).
I must stress though (admittedly from memory) that if you have flashed an SPL or radio image at all, be VERY careful about the order in which you revert back to stock (or go to get a custom ROM depending on which way you decide to go). The G1 is very picky, and flashing things (mostly SPL and radio IIRC) in the wrong order will brick the device. That said, if you follow the instructions you find to the letter you should be OK. But yeah, read twice, flash once.
There is a lot of information in the stickies in the G1 forum. It could take a while to wade through but it should all be there. Failing that, post in the Q&A or General G1 subforums and I'm sure a current user will help you out.
I apologise if I've just posted a bunch of stuff you already know/have read - like I said, I've not used the phone in a while - just trying to offer what I can.
Thanks
No worries now guys i've done it! It was quite complicated but its all sorted now. If anyone is trying this and has the same (or similar) issue then pm me and I will tell you how I sorted it.
Otherwise thanks guys and you can conciser this thread:
---------------------closed--------------------------
So I originally rooted my S3 using odin and a stock verizon software followed by using ez bootload unlock, ez recovery, and clockwork mod. I used the custom rom cyanogen mod, and eventually continued to update those roms when they rolled out the OTA updates. When the latest update came out on the 18th I noticed an issue with my contacts. Due to this I reverted to the 16th rom, but something went terribly wrong. At this time I tried re-rooting, tried different types of rooting and got my device working along with my contacts back, but it rendered my sim card useless. I tried everything I could find on the internet. I finally covered my tracks and took it to the verizon store. They replace the sim card, but it still didn't work. They replaced my device, and me being dumb I rooted it again. Same original rooting that worked the first time. It worked at first, but then the same issue occurred. I'm not sure what to do, I can't go back to verizon again. They will expect something this time. It makes no sense. The hardware is not an issue, there is some data error somewhere. PLEASE HELP!!!
TLDR; Crazy weird data issue maybe? Whoever can solve this will be the House of Android rooting.
a.p.mahaney said:
So I originally rooted my S3 using odin and a stock verizon software followed by using ez bootload unlock, ez recovery, and clockwork mod. I used the custom rom cyanogen mod, and eventually continued to update those roms when they rolled out the OTA updates. When the latest update came out on the 18th I noticed an issue with my contacts. Due to this I reverted to the 16th rom, but something went terribly wrong. At this time I tried re-rooting, tried different types of rooting and got my device working along with my contacts back, but it rendered my sim card useless. I tried everything I could find on the internet. I finally covered my tracks and took it to the verizon store. They replace the sim card, but it still didn't work. They replaced my device, and me being dumb I rooted it again. Same original rooting that worked the first time. It worked at first, but then the same issue occurred. I'm not sure what to do, I can't go back to verizon again. They will expect something this time. It makes no sense. The hardware is not an issue, there is some data error somewhere. PLEASE HELP!!!
TLDR; Crazy weird data issue maybe? Whoever can solve this will be the House of Android rooting.
Click to expand...
Click to collapse
Why don't you try to Odin a pre-rooted Verizon stock can be found here http://forum.xda-developers.com/showthread.php?t=1984436 to see if it addressed both our your issues?
I just had some major issues with this as well. There is something wrong with the nightly versions of CM 10.1.
Like you - I flashed CM 10.1 12/18 and found that my data was not working. I then searched this forum and found that other users were having the no data issue as well. I decided that I would do the same and flash back to an earlier CM 10 release from December, but the update did not go as expected. Due to going 10.1 to 10 I had to wipe data/cache/dalvik. At this point I got CM 10 reinstalled, but the phone came up with NO cell coverage. I went to System Settings -> About -> Status and found that the phone was no longer registering my cellular network (Verizon) or phone number. My IMEI data was dead.
Luckily in my case I had already made backups of my IMEI data per this post: http://forum.xda-developers.com/showthread.php?t=1852255
I restored my IMEI and reflashed CM 10 12/16. Everything is now working as expected. Your issue sounds identical to mine - I just spent half the day fighting with the exact same issue. I definitely learned my lesson about staying so current with the NIGHTLY builds for day-to-day non-dev use. I knew it before, it just never bit me like this.
Anyways, I hope this information helps you somewhat. Good luck!
a.p.mahaney said:
So I originally rooted my S3 using odin and a stock verizon software followed by using ez bootload unlock, ez recovery, and clockwork mod. I used the custom rom cyanogen mod, and eventually continued to update those roms when they rolled out the OTA updates. When the latest update came out on the 18th I noticed an issue with my contacts. Due to this I reverted to the 16th rom, but something went terribly wrong. At this time I tried re-rooting, tried different types of rooting and got my device working along with my contacts back, but it rendered my sim card useless. I tried everything I could find on the internet. I finally covered my tracks and took it to the verizon store. They replace the sim card, but it still didn't work. They replaced my device, and me being dumb I rooted it again. Same original rooting that worked the first time. It worked at first, but then the same issue occurred. I'm not sure what to do, I can't go back to verizon again. They will expect something this time. It makes no sense. The hardware is not an issue, there is some data error somewhere. PLEASE HELP!!!
TLDR; Crazy weird data issue maybe? Whoever can solve this will be the House of Android rooting.
Click to expand...
Click to collapse
You most likely lost you imei/min or something, you can check in settings>about phone>status. Easy way to correct it is to flash a older stock ICS image and use the reprovision code. Flash this in odin then type this in the dialer *2767*3855# and that should fix ya back up. Flashing anything carries a risk of dropping your imei but it happens much more on AOSP roms.
Alrighty, this is one of the weirdest things I've had happen with a phone since I started doing this on the original Droid. Lately I've been using Jellybeans Rom, its been great and my longest running ROM so far, but like a lot of people here I have to try out new stuff quite often just to try it. Well anymore I cant seem to try much else, I wanted to run the newest Liquid Smooth 2.3 ROM that just hit and it wont work at all really, before I redid the whole phone every time I flashed LS 2.3 I couldnt even hit the start button when the ROM first installed, when I did it wouldnt do anything and then the screen would go black and I would have to hard reset or battery pull. Next boot up seemed to go fine, got my gmail up and running and titanium downloaded and then after that, hitting settings options would lock up the phone in just about any app I had, never even got around to trying to restore anything with titanium.
Re-flashed LS 2.3 three or four times and nothing changed, tried fixing permissions, fully wiping, etc. didnt matter. So naturally I figured it was simply the ROM on my phone (mind you LS 2.2 worked fine before) so I went and decided I would try out Avatar ROM, CM based with MIUI themes, this ROM did pretty much the same thing. No idea why...
Next I figured something maybe was wrong with my phone so I went back to the drawing board and started from factory with ODIN, I redid my ROM with stock/root, unlocked the boot loader again and redid custom recovery and all the same thing with LS 2.3 happened all over again, Stock ROM worked great for the bit of time I used it before I tried to reflash LS 2.3 again, Now I'm back running Jellybeans v.15 and it runs perfectly fine as well.
I really have no idea what the problem is, both of those ROMs I've tried are CM based original development, so I'm wondering if its something in there thats causing an issue over the TW ROMs I've used. I've used other TW ROMs with decent success, but I've had some issues with those too that you wouldnt think should happen but it wasnt anything worth noting, just like Jellybeans the best, but even some of those would give me slow down problems and occasional lock ups when Jellybeans doesnt.
Anyone have any clue as to what could be causing this? I used to be able to run non TW roms just fine and its only been in the past month that this has started happening that I've noticed, I've had the phone since January and have been flashing away this whole time and now I cant seem to try out any more ROMs without having major issues......ugh
Your situation is a very random situation but I have something similar happened to me involving TW ROMs in that some of them froze on me. I had to flash the stock ROM.
Bump, anyone having any kind of similar problems?
Sent from my SCH-I535 using xda premium
Vidfreek said:
Bump, anyone having any kind of similar problems?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
If you've only had these issues in the last month, it could be attributed to the Linux 3.4 kernel that every AOSP rom has moved to. I wouldn't let that stop you though. Are you downloading these rom zips over WiFi or mobile data? Were your downloads taking awhile as well? I know either GOO or AFH was having server issues recently which may have coincided with your downloads. I'd suggest using WiFi if you aren't already and trying again?
Sent from my SCH-I535 using xda app-developers app
Yeah its only been fairly recent and all roms I've tried have been updated since the very end of april, if my phone has major problems with that linux kernal am I going to be able to flash anything again? Everything I downloaded was over wifi but I can try all the downloads again but I'm thinking that won't fix anything, just weird stuff
Sent from my SCH-I535 using xda premium
So...I have had a captivate and SGS3 and have never had so much trouble with a phone. This infuse is frustrating and complicated to work with. I have blue CWM which was acquired by using Entropy's guide and the other numerous helpful tips out there. I had rootbox running which would eventually start FC'ing and acting dumb. I wiped everything the other day and flashed unofficial CM 10.2, it worked perfect then random reboots to stuck at samsung then cyanogen mod then back again. Sometimes it would randomly reboot in CWM, which has never happened to me on other phone. I feel like going back to stock and back again is the only answer, but it seems like a lot of work and I already did that and it was fine.
So, all you guys that understand whats going on behind that scenes, what do you think the issue is?
UPDATE: I found a video that may link this behavior to a hardware issue caused by poor design by Samsung having too many contacts that can get gunked up and causing issues.
Might be a problem with the version of the Gapps you're using. Consider changing and even going back to older versions. I found v 12/12 signed very stable on cm10.1.
If still stuck, consider Odin back to stock in download mode and flash cm9 and cm10.2 again!
So after doing a wipe to my phone (was becoming slow) my phone randomly restarts itself for no reason as if it just crashes. I am running the latest version of the beanstalk rom. http://forum.xda-developers.com/showthread.php?t=2091900 I don't have the greatest understanding of flashing, roms, blah blah blah, but managed to get kit kat working for the last year or so, I don't understand why this is happening now, did I choose a bad rom or something? Everything else on the phone works but obviously constant restarts get to be very annoying.
Any help would be appreciated,
thank you!
Infused4life said:
So after doing a wipe to my phone (was becoming slow) my phone randomly restarts itself for no reason as if it just crashes. I am running the latest version of the beanstalk rom. http://forum.xda-developers.com/showthread.php?t=2091900 I don't have the greatest understanding of flashing, roms, blah blah blah, but managed to get kit kat working for the last year or so, I don't understand why this is happening now, did I choose a bad rom or something? Everything else on the phone works but obviously constant restarts get to be very annoying.
Any help would be appreciated,
thank you!
Click to expand...
Click to collapse
Try leaving it turned on in recovery mode (CWM). If it still reboots, then you have a hardware issue. If it stays stable, I would blame the ROM and try a different version or a different distro.
Sent from my MyTouch 4G Slide
joel.maxuel said:
Try leaving it turned on in recovery mode (CWM). If it still reboots, then you have a hardware issue. If it stays stable, I would blame the ROM and try a different version or a different distro.
Sent from my MyTouch 4G Slide
Click to expand...
Click to collapse
Thanks for the reply,
I don't think it is a hardware issue as it never did this when I had Jelly Bean or even the last time I had Kit Kat, never know though! Also, I will try to leave it in recovery and see if it does it but a few questions:
-What is "distro" (does it has to do with the OS of the phone?)
-Is there some ROM you could recommend to me for this phone that is stable.. When I install the beanstalk ROM there are like 10 to choose from, I'm guessing they are all older/newer versions!?
-Finally something I was wondering for the longest time but wasn't sure of is can I go back to say, Jelly Bean? Or is it "irreversible"?
Thanks again, glad there's people out there who can help the noobs like me!
Infused4life said:
Thanks for the reply,
I don't think it is a hardware issue as it never did this when I had Jelly Bean or even the last time I had Kit Kat, never know though! Also, I will try to leave it in recovery and see if it does it but a few questions:
-What is "distro" (does it has to do with the OS of the phone?)
-Is there some ROM you could recommend to me for this phone that is stable.. When I install the beanstalk ROM there are like 10 to choose from, I'm guessing they are all older/newer versions!?
-Finally something I was wondering for the longest time but wasn't sure of is can I go back to say, Jelly Bean? Or is it "irreversible"?
Thanks again, glad there's people out there who can help the noobs like me!
Click to expand...
Click to collapse
Methinks it is the specific ROM. I call the different types of OM out there distributions (or "distros" - in light of what is commonly used in the Linux world), but there may be a better term. It could be the version of Beanstalk you are using, it could be any version of BeanStalk with your phone. Hard to say.
In light of above, I would try CarbonROM. I tried it out briefly, and haven;t had a problem with it (and have heard no issues form the guy I sold the phone to with it installed).
But if you want to go back to JellyBean, there is still a version of 4.2 kicking around (CM 10.1) in the development threads. You can downgrade, at worst you may have to ODIN back to stock. But try to flash in CWM first. I was quite satisfied with that version. My biggest gripe is that the mobile data quick setting didn't work fully (but the long way around did). There is CM 10.2 as well, but I could never get that one installed on my phone (installer would break). Between the two, I would try 10.1 (and if you cannot find a copy, I can dropbox it to you).
5529
joel.maxuel said:
Methinks it is the specific ROM. I call the different types of OM out there distributions (or "distros" - in light of what is commonly used in the Linux world), but there may be a better term. It could be the version of Beanstalk you are using, it could be any version of BeanStalk with your phone. Hard to say.
In light of above, I would try CarbonROM. I tried it out briefly, and haven;t had a problem with it (and have heard no issues form the guy I sold the phone to with it installed).
But if you want to go back to JellyBean, there is still a version of 4.2 kicking around (CM 10.1) in the development threads. You can downgrade, at worst you may have to ODIN back to stock. But try to flash in CWM first. I was quite satisfied with that version. My biggest gripe is that the mobile data quick setting didn't work fully (but the long way around did). There is CM 10.2 as well, but I could never get that one installed on my phone (installer would break). Between the two, I would try 10.1 (and if you cannot find a copy, I can dropbox it to you).
Click to expand...
Click to collapse
YES!
So, after I left the phone in CWM for 25 minutes or so and it being fine I decided to get Carbon as I seen in your "signature" that you had that ROM on your Infuse, it has been good for 2 hours+, looking good! I guess it was the Beanstalk ROM after all.
Thanks for the downgrading information as well, wasn't sure if you could downgrade or what would happen!
Finally, what is flashing? (I could google it but since your here, could you give me a noob friendly definition!?)
Thanks for all your help
Infused4life said:
YES!
So, after I left the phone in CWM for 25 minutes or so and it being fine I decided to get Carbon as I seen in your "signature" that you had that ROM on your Infuse, it has been good for 2 hours+, looking good! I guess it was the Beanstalk ROM after all.
Thanks for the downgrading information as well, wasn't sure if you could downgrade or what would happen!
Finally, what is flashing? (I could google it but since your here, could you give me a noob friendly definition!?)
Thanks for all your help
Click to expand...
Click to collapse
Went to reply about the camera issue and notice it was no longer in the post. Glad you got it sorted.
So flashing, as I understand it, is just another term for installing something via recovery. Not sure of the origin, maybe have something to do with installing to flash memory.
joel.maxuel said:
Went to reply about the camera issue and notice it was no longer in the post. Glad you got it sorted.
So flashing, as I understand it, is just another term for installing something via recovery. Not sure of the origin, maybe have something to do with installing to flash memory.
Click to expand...
Click to collapse
Ah ok, so it's essentially as I thought it was. I thought I was doing something wrong in terms of "flashing" but guess not! Sounds like it should just be called "Installing custom ROM".. !
Yeah, in terms of the camera thing, I'm an idiot and had USB storage turned on *facepalm*, So it wouldn't let me open the camera app!
Infused4life said:
Ah ok, so it's essentially as I thought it was. I thought I was doing something wrong in terms of "flashing" but guess not! Sounds like it should just be called "Installing custom ROM".. !
Yeah, in terms of the camera thing, I'm an idiot and had USB storage turned on *facepalm*, So it wouldn't let me open the camera app!
Click to expand...
Click to collapse
I am not sure if you are still facing the same issue but if you are facing reboots, then considering doing a fresh install after cleaning your internal storage as well since the remnants of the apps from previous installs have caused me problems. Ever since I started doing a fresh install (Factory reset, wiping the cache, wiping the dalvik cache and even the cache partition along with the wiping of the internal storage), there have been no reboot issues.