Related
Hi,
My warranty has just run out on my Nexus One so I've decided to unlock the bootloader.
My Aim is to get from stock non rooted Gingerbread to rooted Gingerbread with busybox, SU, and ultimately being able to boot into ubunto in chroot, I've been reading up on all this for a few days now but just need a small amount of help with Recovery, Gingerbread ROM choice, and the order that thing should be done, by someone who's done this before.
I take it the first thing is to install SDK and get The USB Driver working on PC, its running XP by the way.
Then I unlock the bootloader, !HELP! to do this do I enter hboot or fastboot, before connecting the phone to the PC? I have to copy 3 files somewhere and use ADB and run command for **** OEM unlock, can't remember the exact command, (I've got instructions for this) and then agree to void my warranty etc.
I then find and download the correct custom recovery image and copy this into the tools folder of the SDK. And install (got instructions for this to).
!HELP!
Which custom recovery image should I use? and which Rooted Gingerbread ROM is most popular ?
After installing the custom Recovery can I just flash a custom ROM? I've seen something about SU.zip mentioned, is this necessary?
If I can just flash a custom ROM, I do this by downloading and copying the custom ROM of choice to the root of my SD card. Start phone in recovery mode and install from SD? I then install the google add ons .zip (if required) using the same method.
Sorry for such a long post and so many questions but I can find all the information for what I'd like to achieve but not in one place and nowhere in any chronological order.
Any advice appreciated .
Please read the Wiki, "Root" guides, "Unlock bootloader and install custom ROM" thread. Execute until the point of installing custom ROM.
Look in "Recovery" section for recoveries, install the latest Amon_RA.
Ive Successfully Rooted Gingerbread by following this method http://chensun.net/android-development/root-nexus-one-with-android-2-3-3-gingerbread/8/
GB ROM
Im running CM7RC4 and am happy w/ it
MouseIdt said:
Ive Successfully Rooted Gingerbread by following this method http://chensun.net/android-development/root-nexus-one-with-android-2-3-3-gingerbread/8/
Click to expand...
Click to collapse
Thanks everyone, but this looks like the one for me, going to unlock bootloader now install custom recovery and flash su.zip.
I'll post back with how I went on. Wish me look
A apprehensive newbie ;-)
Flash this as well, otherwise you will lose your custom recovery...
http://db.tt/cp7De8G
Sent from my Nexus One using XDA Premium App
Good show with unlocking the bootloader, it's the best way.
However... looking at your flag, you're in the UK... this means your phone is still in warranty, as we get 24 months.
Nooooo
Rusty! said:
Good show with unlocking the bootloader, it's the best way.
However... looking at your flag, you're in the UK... this means your phone is still in warranty, as we get 24 months.
Click to expand...
Click to collapse
My understanding was 12 months but, your probably right. I've unlocked the bootloader now and fortunately my N1 is in good condition, funtioning correctly ( well at least for now, I'll have to cross that bridge if and when I get to it )
Getting on to custom recovery, I realised something wasn't quite right after my first attempt. I installed custom recovery but without su.zip on my SD card. I managed after rebooting my PC to complete the custom recovery with su.zip on the SD card and was successful in that I've got SU on my N1. However I am quite sure I do need to fix something with the recovery, can someone explain what method or how I do this now. I've unlocked the bootloader, I am rooted with gingerbread but with a dodgy recovery.
Or do I do exactly the same as I did with su.zip and push recovery from ADB and flash from SD card, making sure that fix-recovery.zip is indeed on the SD card.
Hope this makes sence?
Any help appreciated.
After I unlocked my n1 I used rom manager for everything else, first flashing clockwork mod, then selecting a stable cm 7 build and flashing that, since then I've done everything through recovery, flashing custom kernels and nightlie builds, I'm currently using cm7 rc4 highly recommend rover theme too!
Sent from my Nexus One using XDA Premium App
sparkyryan said:
After I unlocked my n1 I used rom manager for everything else, first flashing clockwork mod, then selecting a stable cm 7 build and flashing that, since then I've done everything through recovery, flashing custom kernels and nightlie builds, I'm currently using cm7 rc4 highly recommend rover theme too!
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
I've got ROM Manager installed and if I want to try anything it tells me I have to flash clockwork mod recovery, I was unsure if It was safe to do this after using a completely different recovery image to get where I am now.
Sorry for being such a paranoid newbie, but we all got to start somewhere ;-)
sparkyryan said:
After I unlocked my n1 I used rom manager for everything else, first flashing clockwork mod, then selecting a stable cm 7 build and flashing that, since then I've done everything through recovery, flashing custom kernels and nightlie builds, I'm currently using cm7 rc4 highly recommend rover theme too!
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
I think CM7 rc4 is next, I do want to get Linux up and running though, even if it's in a virtual environment (chroot). and deffinately would like to check some nice themes out, I've not even looked at themes yet, I suppose it's quite easy after unlocking bootloader, installing custom recovery then flashing su.zip though. But still any pointers where to start my quest wouldn't go a miss ;-)
Recovery
its safe to let rom manager flash clockwork,ive done it
I heared about amonRA but it seemed like clockworkmod was more commonly used so I went for that, but yeah it's fine to flash a new recovery, just remember that whilst it's rare things can go wrong, it's YOUR fault not anyone's here regardless of the advice you may get here if your phone gets bricked or screwed up.
That said I'm still new to this but I'm learning as I'm going, just remember to backup your phone using rom manager before doing anything major so that you can always recover your phone/rom.
I started out hacking my nokia 5800 so was keen to have a go with the android platform.
Sent from my Nexus One using XDA Premium App
CM7 stable
Have you upgraded to cm 7 stable? its a definate upgrade
Someone mentioned a way to use the new T-Mobile OTA on an AT&T Nexus S. It wasn't totally clear so I figured I'd put up a little more info. I'll get the rough guide up and fill in links later. This will require a computer with fastboot, and either a wifi connection for the phone, or using adb on a computer to push files to the phone while it isn't able to connect to AT&T.
I take no liability for anything going wrong with your phone, cat, significant other, or anything else, as a result of the contents of this guide.
Problems
- Stock recovery keeps replacing Clockwork Recovery. I have to reflash clockwork by fastboot every time.
- This method will leave you with a non-rooted phone
1) Get the phone onto T-Mobile Android 2.3.6 - I did this by using the "Stock" install in Rom Manager, which is 2.3.3. It automatically downloaded the update to 2.3.6, which I then installed. This step is needed because the ICS OTA is an upgrade, not a full install.
2) Update to ICS. I had already directly downloaded the zip from Google, but you might be able to get it by the system upgrade check, or by Rom Manager.
3) Install an AT&T radio - the original stock image (2.3.3) works fine, but once you upgrade to 2.3.6, you have a T-Mobile only radio. The upgrade to ICS will stick with a T-Mobile only radio. Grab an AT&T radio from this thread and get it on the phone. Use fastboot to reset the recovery to ClockworkMod Recovery, and use ClockworkMod to install it. UCKF1 didn't work for me, but UCKE1 did.
Reserved. At the bar.
Sent from my Nexus S using XDA App
FWIW
holtenc said:
yeah thats where got the radio. but it doesn't specify which is for att. just that they are for 9020a,
either way I figured it out. ATT needs the UCKE1 radio. and it works
so ive got GT-I9020A on AT&T working with this ICS ---- WOOT
Click to expand...
Click to collapse
Sent from my Nexus S using XDA App
Sent from my Nexus S using XDA App
***I saw he successfully posted he flashed the tmo version, had no cell service and I just quoted what he wrote.
UCKE1 works!!!!
you save me and my NS!!!!
laydros said:
Problems
- Stock recovery keeps replacing Clockwork Recovery. I have to reflash clockwork by fastboot every time.
Click to expand...
Click to collapse
Delete /system/etc/install-recovery.sh. This probably something people have long forgotten...
You can do that right after flashing 4.0.3 in CWM. Just
Code:
adb shell rm /system/etc/install-recovery.sh
Remember to mount /system if it's not mounted already.
Second that. Worked for me.
Instead of ROM Manager I downloaded T mobile 2.36, 3.04 and radio first.
Then flash CWM, 2.36, CWM, 4.03 & radio and then deleted recovery.sh as mentioned.
Working so far.
I assume we can do the same to revert back to official 9020a 4.03 when it drops.
Happy flashing.
---------- Post added at 07:52 AM ---------- Previous post was at 07:19 AM ----------
Market not working.
I am using adb install to push apk's directly to device.
How stable is the tmo ics on the at&t nexus s, I'm getting impatient waiting for the official update
vargasels said:
How stable is the tmo ics on the at&t nexus s, I'm getting impatient waiting for the official update
Click to expand...
Click to collapse
It works fine. I haven't had crashes. It is a bit slower than gingerbread but not terrible. I did a complete wipe after updating and I haven't had any major battery issues some reported.
Btw, you can flash the radio right after flashing 4.0.3. There is no need to boot into ICS, reboot into recovery, and then flash the radio. That way the initial setup can work of 3g not just wifi.
bozzykid said:
It works fine. I haven't had crashes. It is a bit slower than gingerbread but not terrible. I did a complete wipe after updating and I haven't had any major battery issues some reported.
Btw, you can flash the radio right after flashing 4.0.3. There is no need to boot into ICS, reboot into recovery, and then flash the radio. That way the initial setup can work of 3g not just wifi.
Click to expand...
Click to collapse
alright seems easy enough, when the official update comes i can just flash back gingerbeard and go from there right?
vargasels said:
alright seems easy enough, when the official update comes i can just flash back gingerbeard and go from there right?
Click to expand...
Click to collapse
Yes. You will just need to reflash clockworkmod recovery (since stock recovery doesn't let you downgrade) and flash the full the full 2.3.6 rom.
Checking in on this thread to see what radio i9020a people are using on 4.0.3. I currently have XXXKB3 but find that data loses connection when i'm deep indoors. Any suggestions?
I'm currently using UCKD1 but am not entirely satisfied. I occasionally lose my data connection and have to reboot the phone, although I don't know if it is radio-related or not. On ICS 4.04.
crabnebula said:
I'm currently using UCKD1 but am not entirely satisfied. I occasionally lose my data connection and have to reboot the phone, although I don't know if it is radio-related or not. On ICS 4.04.
Click to expand...
Click to collapse
I tried UCKD1 today and for the most part it worked well but I did experience the dreaded search bug about 4 times in one night. It has managed to keep the connection without dropping even once in something like 9 hours.
I also tried flashing UCKE1 earlier but it gave me some kind of error when flashing and was unsuccessful. From what i've read, UCKE1 is a bit better than KD1 but doesn't have the search bug problem.
i just updated my 9020a from 2.3.6 to 4.0.4 i justed flashed the update zip its working great
http://androidforums.com/nexus-s/465048-official-ics-4-0-x-discussion-links-thread.html
This is my FINAL VERSION of my Idiots Guide for the HP Touchpad. Now that a stable enough version of CM10 is available, I finally created a guide for you.
Here are links to the files you will need:
CM10 03/04/2012 Build
GAPPS 10/11/2012
ACMEInstaller3
Moboot 3.8
Anything else that you might need, you'll find on http://www.reverendkyle.com
Thanks for the video. It came just in time as I just purchased a used TP that had an older version of android ICS already on it and I wanted to upgrade but seeing as how this is the first device I have sort of inherited already rooted, it is hard to just jump in and know everything that I would have learned from the beginning like i did with my previous phones.
Anyways, I did everything you said except I used the newest AOKP rom. But my tp is still booting to the older version of android that I had on it. Any ideas? Feel free to pm me if you prefer that.
aujbman said:
Thanks for the video. It came just in time as I just purchased a used TP that had an older version of android ICS already on it and I wanted to upgrade but seeing as how this is the first device I have sort of inherited already rooted, it is hard to just jump in and know everything that I would have learned from the beginning like i did with my previous phones.
Anyways, I did everything you said except I used the newest AOKP rom. But my tp is still booting to the older version of android that I had on it. Any ideas? Feel free to pm me if you prefer that.
Click to expand...
Click to collapse
If the AOKP ROM is using a unique uImage file, then you may see two different entries on your moboot screen for two different Android builds.
What does your moboot menu have in it?
Maybe your install failed. Try downloading and flashing it again. If you're trying AOKP JB, you should wipe both /data and dalvik cache to avoid a boot loop!
If using AcmeInstaller3 remember to rename the ROM with ”update-” at the beginning so that it looks like update-AOKPJB_UnOfficial.zip
Sent from my SAMSUNG-SGH-T989 using xda premium
-SGA- said:
Maybe your install failed. Try downloading and flashing it again. If you're trying AOKP JB, you should wipe both /data and dalvik cache to avoid a boot loop!
If using AcmeInstaller3 remember to rename the ROM with ”update-” at the beginning so that it looks like update-AOKPJB_UnOfficial.zip
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I believe it was the "update-" thing that was keeping it from updating. I followed another video tutorial which provided files that had the "update" in front of them and it worked.
I haven't tried yet but now that it worked will the regular method of wiping and flashing through recovery work? (Like, if I want to try out different JB Roms) Are there any files that need to be in a particular place for the recovery method to work? I tried that method first and it would never take, would always revert back to the original version. Don't know if, because I just jumped in and haven't been here from the beginning, I am just missing a necessary step that is hardly even talked about anymore.
Love your work Rev! Thank you again for everything that you do!
Update went like clockwork, unfortunately I can't seem to get the camera to work (not a terrible loss, but I was sorta excited to see it actually working with this release).
Jubmasterflex said:
Love your work Rev! Thank you again for everything that you do!
Update went like clockwork, unfortunately I can't seem to get the camera to work (not a terrible loss, but I was sorta excited to see it actually working with this release).
Click to expand...
Click to collapse
I can attest to the improved battery life on this cm10 build. Amazingly, it holds battery life when it's sleeping now.
Thank you so much for taking the time in making the video for us. Your instructions are easy to follow, hard for anyone to mess up.
(The hosting site for the files is not working, not sure if you were aware)
Hi, I have CM9 running on my TP. With the latest release, the camera works great. But before updating it to CM10, I'd like to know about the issues currently in this build.
Thanks.
Where does one go when the goo.im site appears down, to get the needed files? Mirror somewhere?
ljderm said:
Where does one go when the goo.im site appears down, to get the needed files? Mirror somewhere?
Click to expand...
Click to collapse
Don't go for external mirrors unless some recognized developer suggests them. Best will be to wait for goo.im to come up again, being a prime site, it won't be down for long.
The goo servers do appear to go down on occasion. They always come back up a bit later.
Problem with installing GAPPS using ACMEInstaller3
Excellent tutorial for an idiot like me. Thanks for again for the guide! Question:
I followed the instructions step by step and was able to get CM10 installed successfully. However, I wasn't able to get GAPPS installed using this method. From researching I understand sometimes there is a problem installing GAPPS through ACMEInstaller3 and one can simply get GAPPS installed through CWM Recovery. However, I would like to use/have TWRP instead so is there a way to get GAPPS installed properly through ACMEInstaller3 and then I can install TWRP through GooManager?
Alternatively, is there a way to install GAPPS without using CWM Recovery?
Or, I guess I can install CWM Recovery first, then install TWRP Recovery, then remove CWM Recovery while keeping TWRP and not go back to the stock Recovery? I tried to search the forums and wasn't able to find instructions on removing CWM Recovery WHILE still keeping CM10 and not go back to the Stock recovery.
Any help would be much appreciated. Thanks in advance for your help.
@reverendkjr - appreciate your videos. they're awesome. definitely helped me (and several other friends) many times and saved a ton of time. super easy to follow.
Yes you can install TWRP normally, flash gapps in CWM then install goomanager app, open and click the 3 dot menu and install custom recovery script then it will install it
Now using a root file manager go to the directory called boot and delete uimage.cwm.img (this is from memory but still should be correct
Sent from my cm_tenderloin using XDA Premium HD app
waynekirby said:
Yes you can install TWRP normally, flash gapps in CWM then install goomanager app, open and click the 3 dot menu and install custom recovery script then it will install it
Now using a root file manager go to the directory called boot and delete uimage.cwm.img (this is from memory but still should be correct
Sent from my cm_tenderloin using XDA Premium HD app
Click to expand...
Click to collapse
Dumb question. I had dual boot installed with moboot and one day my dumbarse clicked erase SD card.well it did...EVERYTHING accept twrp. I successfully reinstalled webos and installed preware. Its actually pretty cool.its like a fledgling play store for webos. Now....where should i go from here.i no longer think twrp is on it. All i have is webos with preware.sorry if this is newbie
Sent from my Galaxy Nexus using xda premium
Crwolv said:
Dumb question. I had dual boot installed with moboot and one day my dumbarse clicked erase SD card.well it did...EVERYTHING accept twrp. I successfully reinstalled webos and installed preware. Its actually pretty cool.its like a fledgling play store for webos. Now....where should i go from here.i no longer think twrp is on it. All i have is webos with preware.sorry if this is newbie
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
My goodness you have forgotten everything, you will need to install acmeuninstaller 3, moboot, CMW and the rom you want along with the relevant gapps. Sounds complicated this thread will make it easy
http://forum.xda-developers.com/showthread.php?t=2147284 and has all the necessary links. Have fun.
Sent from my Transformer Prime TF201 using Tapatalk 2
Heck ya i did lol. That refreshed my memory instead of a long video. Thank yo very much
Awesome!
Sent from my cm_tenderloin using xda app-developers app
Great vid!! Finally got CM10 on my Touchpad.
This is my first TouchWiz device, a GS4 on Sprint. I've tried to install several custom ROMs and I keep getting errors that seem like GApps won't launch or isn't launching correctly. I've tried the FreeGS4 ROM and the ForceROM with the same effect. I am not allowed yet to post in either ROM's thread and neither seem to mention a specific GApps download. I have been using the Gapps that GooManager downloaded automatically as I have not found another.
Any tips would be appreciated. More information available upon request as I'm not sure exactly what is necessary.
:: Tyler
SalomonCascade said:
This is my first TouchWiz device, a GS4 on Sprint. I've tried to install several custom ROMs and I keep getting errors that seem like GApps won't launch or isn't launching correctly. I've tried the FreeGS4 ROM and the ForceROM with the same effect. I am not allowed yet to post in either ROM's thread and neither seem to mention a specific GApps download. I have been using the Gapps that GooManager downloaded automatically as I have not found another.
Any tips would be appreciated. More information available upon request as I'm not sure exactly what is necessary.
:: Tyler
Click to expand...
Click to collapse
Make sure and back up your current rom through recovery first then do a wipe of system and data partitions. Install new rom wipe cache and dalvik cache, fix permissions then reboot
****'ll Buff Out
stigrip and
Okay, I'm really new to TWRP. It's completely different from CWM or the process is. I'm having a lot of trouble. Please give me as straight forward of steps as possible.
All I need is to install a ROM and GApps. Mostly, I want to know if GApps is included in the ROMs I specified: FreeGS4 or ForceRom2.1.
If anyone would rather suggest a ROM that they prefer and the GApps to go with it, I would try that too.
If I can't get this to work soon I will try the UnRoot method to see if I can get this phone working.
:: Tyler
SalomonCascade said:
Okay, I'm really new to TWRP. It's completely different from CWM or the process is. I'm having a lot of trouble. Please give me as straight forward of steps as possible.
All I need is to install a ROM and GApps. Mostly, I want to know if GApps is included in the ROMs I specified: FreeGS4 or ForceRom2.1.
If anyone would rather suggest a ROM that they prefer and the GApps to go with it, I would try that too.
If I can't get this to work soon I will try the UnRoot method to see if I can get this phone working.
:: Tyler
Click to expand...
Click to collapse
You don't flash Gapps with any touchwiz rom. So any rom you find in the Android Development forum be sure to NOT flash Gapps.
And other than a few minor differences TWRP and CWM accomplish the same basic thing, instructions from what to do in recovery will be same in either recovery unless specified.
Sent from my SPH-L720 using xda app-developers app
Alright. That could have been my issue. Somehow my bootloader was corrupted too, so could only get into Download mode. Trying to format back to MDC right now, then will see if I can root and install TWRP again.
This is a lesson for everyone: Don't drink and mod.
One last question: Using ODIN to flash back to MDC, can anyone estimate the time it might take to reboot? I believe I waited around 20 minutes last night and the boot never finished. Not sure what to do at this point.
yea thats deff your problem bro.. u cant flash gapps on a touch wiz rom.. gapps is only for an aosp rom
SalomonCascade said:
Okay, I'm really new to TWRP. It's completely different from CWM or the process is. I'm having a lot of trouble. Please give me as straight forward of steps as possible.
All I need is to install a ROM and GApps. Mostly, I want to know if GApps is included in the ROMs I specified: FreeGS4 or ForceRom2.1.
If anyone would rather suggest a ROM that they prefer and the GApps to go with it, I would try that too.
If I can't get this to work soon I will try the UnRoot method to see if I can get this phone working.
:: Tyler
Click to expand...
Click to collapse
You need to flash forcerom 2.0 then the update 2.1 btw
Sent from my Nexus 10 using xda app-developers app
I got a good deal on the Cricket..formerly AiO... i337z model but apparently it is not supported as other versions here..
Is it possible to root, install custom recovery and flash this S4 variant? Should I sell it and get the At&t version?
kinvid said:
I got a good deal on the Cricket..formerly AiO... i337z model but apparently it is not supported as other versions here..
Is it possible to root, install custom recovery and flash this S4 variant? Should I sell it and get the At&t version?
Click to expand...
Click to collapse
Supposedly Safestrap works on it just the same as ours, but I don't know what root methods work. What system version are you on, 4.2 or 4.4?
DeadlySin9 said:
Supposedly Safestrap works on it just the same as ours, but I don't know what root methods work. What system version are you on, 4.2 or 4.4?
Click to expand...
Click to collapse
I can confirm that towel root works on the i337z from Cricket/AIO (now AT&T). However, I was not able to get the Safestrap for the AT&T i337 to work. I tried Safestrap 3.65, 3.71, or 3.72. They all install, but don't seem to activate. I am on Android 4.4.2, build TUUBNE2.
devzero said:
I can confirm that towel root works on the i337z from Cricket/AIO (now AT&T). However, I was not able to get the Safestrap for the AT&T i337 to work. I tried Safestrap 3.65, 3.71, or 3.72. They all install, but don't seem to activate. I am on Android 4.4.2, build TUUBNE2.
Click to expand...
Click to collapse
Did you try using SELinux Mode Changer and then installing? Since you install to the stock slot with 4.4 it will never register as active but as long as it says installed it should work.
DeadlySin9 said:
Did you try using SELinux Mode Changer and then installing? Since you install to the stock slot with 4.4 it will never register as active but as long as it says installed it should work.
Click to expand...
Click to collapse
Obviously, Safestrap won't be "active" if you're in the stock rom. What I meant was that safestrap would say it installed successfully, but wouldn't "activate" on boot, and give me the safestrap splash screen/menu. My previous phone was a Razr Maxx with a locked bootloader, so I'm familiar with how Safestrap works.
Well, I'm happy to report that after changing SELinux to permissive, I was able to get Safestrap working on 4.4.2. Safestrap 3.71 and 3.72 both seem to work. This is the first phone I've had that has had it set to enforcing by default, so it didn't even occur to me to check that. Thanks for the suggestion!
Now on to ROMs.. any recommendations? I've read that only TW ROMs will work on the S4 with Safestrap. My Razr Maxx has official CM11 (AOSP) builds available. What seems to be the issue with the S4 only working with TW ROMs?
devzero said:
Obviously, Safestrap won't be "active" if you're in the stock rom. What I meant was that safestrap would say it installed successfully, but wouldn't "activate" on boot, and give me the safestrap splash screen/menu. My previous phone was a Razr Maxx with a locked bootloader, so I'm familiar with how Safestrap works.
Well, I'm happy to report that after changing SELinux to permissive, I was able to get Safestrap working on 4.4.2. Safestrap 3.71 and 3.72 both seem to work. This is the first phone I've had that has had it set to enforcing by default, so it didn't even occur to me to check that. Thanks for the suggestion!
Now on to ROMs.. any recommendations? I've read that only TW ROMs will work on the S4 with Safestrap. My Razr Maxx has official CM11 (AOSP) builds available. What seems to be the issue with the S4 only working with TW ROMs?
Click to expand...
Click to collapse
The Razr has an AOSP compatible kernel by default since Motorola doesn't change the kernel that much, and kexec has been developed for Razr to allow loading of custom kernels. Neither of those is the case with the S4, as the kernel is modified for Touchwiz and kexec is not functioning yet. There is one Google Edition ROM that has been made to boot with some slight issues you could go with (no USB MTP, no WiFi hotspot, WiFi requires soft reboot, SELinux Mode changer is required to keep installed) but other than that check out our All Things MK2 and NB1 index thread for working 4.4 ROMs.
DeadlySin9 said:
The Razr has an AOSP compatible kernel by default since Motorola doesn't change the kernel that much, and kexec has been developed for Razr to allow loading of custom kernels. Neither of those is the case with the S4, as the kernel is modified for Touchwiz and kexec is not functioning yet. There is one Google Edition ROM that has been made to boot with some slight issues you could go with (no USB MTP, no WiFi hotspot, WiFi requires soft reboot, SELinux Mode changer is required to keep installed) but other than that check out our All Things MK2 and NB1 index thread for working 4.4 ROMs.
Click to expand...
Click to collapse
Ah, makes sense. Thanks for the explanation.
Update on the SS situation: While I've been able to 3.71 and 3.72 installed and seemingly operational on boot, neither seem to actually work in terms of booting from a rom slot. I've tried a few different TW 4.4.2 based roms, various module levels, and none of them seem to work.
With SS 3.71, I see some errors in the SS console about not being able to mount /systemorig, and I am not able to do a backup of the stock system partition, but otherwise it seems to work ok. However, when I try to boot from slot1, all I get is a black screen.
With SS 3.72, there are no /systemorig errors, and I am able to backup all partitions of the stock rom, and I am even able to boot from slot1, but it actually just boots to stock, and my cell radio doesn't work.
I tried simply restoring the stock rom to slot 1 and booting from it, since that should theoretically work, and I still had the same experience as above, so I'm thinking it doesn't matter what rom/modules try, SS 3.71/3.72 just isn't going to work
devzero said:
Ah, makes sense. Thanks for the explanation.
Update on the SS situation: While I've been able to 3.71 and 3.72 installed and seemingly operational on boot, neither seem to actually work in terms of booting from a rom slot. I've tried a few different TW 4.4.2 based roms, various module levels, and none of them seem to work.
With SS 3.71, I see some errors in the SS console about not being able to mount /systemorig, and I am not able to do a backup of the stock system partition, but otherwise it seems to work ok. However, when I try to boot from slot1, all I get is a black screen.
With SS 3.72, there are no /systemorig errors, and I am able to backup all partitions of the stock rom, and I am even able to boot from slot1, but it actually just boots to stock, and my cell radio doesn't work.
I tried simply restoring the stock rom to slot 1 and booting from it, since that should theoretically work, and I still had the same experience as above, so I'm thinking it doesn't matter what rom/modules try, SS 3.71/3.72 just isn't going to work
Click to expand...
Click to collapse
3.71 not being able to mount isn't surprising as it was never made for kitkat and thus had issues mounting system on kitkat (we had to flash the kernel from our 4.3 version to make it work). ROM slots not working with Kitkat is also another known issue, and all flashes have to be straight to stock slot. Since you have a backup, just flash any ROM from the Index thread and you should be fine.
DeadlySin9 said:
3.71 not being able to mount isn't surprising as it was never made for kitkat and thus had issues mounting system on kitkat (we had to flash the kernel from our 4.3 version to make it work). ROM slots not working with Kitkat is also another known issue, and all flashes have to be straight to stock slot. Since you have a backup, just flash any ROM from the Index thread and you should be fine.
Click to expand...
Click to collapse
You mean use SS 3.72 to flash over the stock ROM?
devzero said:
You mean use SS 3.72 to flash over the stock ROM?
Click to expand...
Click to collapse
Yes. That's how normal I337 users have to flash amd it's pretty safe if you use one of the listed ROMs. Just backup, wipe system, cache, and data, and then flash the ROM.
Sent from my SGH-I337 running GPE
DeadlySin9 said:
Yes. That's how normal I337 users have to flash amd it's pretty safe if you use one of the listed ROMs. Just backup, wipe system, cache, and data, and then flash the ROM.
Sent from my SGH-I337 running GPE
Click to expand...
Click to collapse
I installed a few different ROMs in the stock slot, and it seemed to work ok, but I was not able to get WiFi working. I was not able to find a kernel modules pack for NE2, so I'm guessing this is my problem. The closest I was able to find was NC1, and it didn't make any difference. Is there a way I can copy the modules from my stock rom, or somehow extract them from the backup, then create my own NE2 update zip?
I was able to extract the kernel modules from the stock TWRP backup and create a kernel modules update package for the NE2 build. WiFi works great now.
I am attaching the update package here in case anyone else needs the Cricket/AIO NE2 kernel modules. Perhaps a moderator could copy this to the SafeStrap downloads section? (http://forum.xda-developers.com/devdb/project/?id=680#downloads)
DeadlySin9 - Thanks again for your helpful info on this matter!
devzero said:
I was able to extract the kernel modules from the stock TWRP backup and create a kernel modules update package for the NE2 build. WiFi works great now.
I am attaching the update package here in case anyone else needs the Cricket/AIO NE2 kernel modules. Perhaps a moderator could copy this to the SafeStrap downloads section? (http://forum.xda-developers.com/devdb/project/?id=680#downloads)
DeadlySin9 - Thanks again for your helpful info on this matter!
Click to expand...
Click to collapse
Glad you got it working. Happy modding!
Sent from my SGH-I337 running GPE
Has anyone here with AIO/Cricket attempted to run a Cyanogen ROM? I got the SHOstock 8.1 working... Just interested in what else is avail out there. Go here:
http://download.cyanogenmod.org/?device=jfltecri
shakedown said:
Has anyone here with AIO/Cricket attempted to run a Cyanogen ROM? I got the SHOstock 8.1 working... Just interested in what else is avail out there. Go here:
http://download.cyanogenmod.org/?device=jfltecri
Click to expand...
Click to collapse
CM builds won't work unless you have an unlocked bootloader. Please refer to post #6. http://forum.xda-developers.com/showpost.php?p=54492289&postcount=6
devzero said:
CM builds won't work unless you have an unlocked bootloader. Please refer to post #6. http://forum.xda-developers.com/showpost.php?p=54492289&postcount=6
Click to expand...
Click to collapse
Makes sense. Have you run into any issues with shostock 8.1? So it's been a week or so now and the only issue I have is after my leaving my home's wifi the phone appears to not fall back onto the wireless network for data. I'll have full or next to full bars for phone but I've lost the data indicator. If I attempt to open an app When in this state I'll get an error that there is no data connection. A reboot fixes this. It also only appears to happen when the phone has been on wifi for a long time I.e. overnight. Could it be a battery saving feature? Could it be related to missing a couple of calls and getting just the vm icon?
Shakedown
shakedown said:
Makes sense. Have you run into any issues with shostock 8.1? So it's been a week or so now and the only issue I have is after my leaving my home's wifi the phone appears to not fall back onto the wireless network for data. I'll have full or next to full bars for phone but I've lost the data indicator. If I attempt to open an app When in this state I'll get an error that there is no data connection. A reboot fixes this. It also only appears to happen when the phone has been on wifi for a long time I.e. overnight. Could it be a battery saving feature? Could it be related to missing a couple of calls and getting just the vm icon?
Shakedown
Click to expand...
Click to collapse
I haven't seen any wifi issues. By default the cell connection type is hidden when you connect to wifi, but this can be turned on through 3rd party mods such as Wanam Xposed.
The only issue I've seen is the remove button doesn't work when long pressin on an app in the app drawer.
I was able to get Cyanogenmod to work after installing CWM. That or TWRP. System wouldn't boot, but i had the recovery and just installed the unified CM and all was fine. And from there I went crazy with roms. GPE from kryten, Kushan, wicked (which sucked) anything i could.
---------- Post added at 09:45 PM ---------- Previous post was at 09:40 PM ----------
I'm just throwing this out there, do not flash AIO / Cricket's MH1 update. it made everything audio crash. couldn't get the modem to work at all, nothing stuck when i tried to flash a different one