Related
I'm not too worried about undoing the rooting (unless there's an easy way) but how to I get back to Android 2.1 like I had when I first got the phone? Can I just install the stock ROM and where do I find it?
Thanks
kbeeveer46 said:
I'm not too worried about undoing the rooting (unless there's an easy way) but how to I get back to Android 2.1 like I had when I first got the phone?
Thanks
Click to expand...
Click to collapse
Why would you want an unlocked bootloader with the OTA stock ROM? There is no way to relock the bootloader and regain your warranty.
CM is Android 2.1, just a better, faster version.
If you are concerned about OTA updates, the features are generally included in Cyanogen's ROM immediately upon release, but usually far before any OTA release.
No big reason why I want to right now but I like knowing there's a way to get back to stock in case something goes horribly wrong and I mess something up (and for the same reasons some of us reformat our computers often). I don't even notice a huge difference (speed and battery) running CM. I haven't installed many apps or themes though.
kbeeveer46 said:
No big reason why I want to right now but I like knowing there's a way to get back to stock in case something goes horribly wrong and I mess something up (and for the same reasons some of us reformat our computers often). I don't even notice a huge difference (speed and battery) running CM. I haven't installed many apps or themes though.
Click to expand...
Click to collapse
you cant go back to stock...you will never have a locked bootloader again...yet
xsnipuhx said:
you cant go back to stock...you will never have a locked bootloader again...yet
Click to expand...
Click to collapse
That's different than the stock rom, right? Is it possible to be unlocked and run the default rom that comes with the phone? Or is that combination not a possibility?
Sure you can do that, but I guess I just don't understand why...
You can always go back to stock everything except your bootloader will remain unlocked (unless someone finds a workaround or hack)
Anything you can screw up (except a bad radio flash) can be fixed by having an up to date Nandroid backup...
Just do what I do and make sure to Nandroid every other day or so. (Or before every time you change anything in the system/framework/boot/kernel etc.)
forum.xda-developers.com/showthread.php?t=619801
i think you can get the stock rom from here if you didnt do a nandroid backup
If i were going to sell the nexus one some time in the future, it would be good to know where the stock rom can be found. Some people don't want to be flashing ROMs all the time, and would prefer OTA updates. Once the phone is over a year old, the unlocked bootloader will be meaningless.
Simple, in the android development section at the top of the list as a sticky, [ROM] 22/Mar ERD79 -> EPE76 - Stock Nexus One images / zip / online kitchen / rooted, or heres the link, http://forum.xda-developers.com/showthread.php?t=619801, it gives you the stock rom. happy flashing
ernvillanueva90 said:
Simple, in the android development section at the top of the list as a sticky, [ROM] 22/Mar ERD79 -> EPE76 - Stock Nexus One images / zip / online kitchen / rooted, or heres the link, http://forum.xda-developers.com/showthread.php?t=619801, it gives you the stock rom. happy flashing
Click to expand...
Click to collapse
The download links in that thread don't seem to work any longer. It just redirects me to the homepage. I probably need an account or something. Blarg.
EDIT: Still don't work even with an account.
kbeeveer46 said:
The download links in that thread don't seem to work any longer. It just redirects me to the homepage. I probably need an account or something. Blarg.
EDIT: Still don't work even with an account.
Click to expand...
Click to collapse
That site uses an anti bandwidth stealing feature, just right click the link and save as.
Love my N7, running stock rom (rooted and unlocked).
Is there any way to bring in some features (like the circle battery, or the recovery/reboot options in shutdown menu) from other roms without having to flash the whole rom?
My phone is old and abandoned by it's manufacturer and carrier, so I don't mind flashing it, but the N7 is still supported so I would like to stay official. These are some very useful features I would love to incorporate if they are available as apk or flash able zip addons.
Thanks!
rhcreed said:
Love my N7, running stock rom (rooted and unlocked).
Is there any way to bring in some features (like the circle battery, or the recovery/reboot options in shutdown menu) from other roms without having to flash the whole rom?
My phone is old and abandoned by it's manufacturer and carrier, so I don't mind flashing it, but the N7 is still supported so I would like to stay official. These are some very useful features I would love to incorporate if they are available as apk or flash able zip addons.
Thanks!
Click to expand...
Click to collapse
this post has an add in for reboot options for the stock rom. http://forum.xda-developers.com/showthread.php?t=1771307
but keep in mind, adding extra feature will probably bork an OTA.
ROM toolbox by jrummy will help with some of what you want. The shutdown menu wont be possible via the route you want though I'm pretty sure
BrianDigital said:
but keep in mind, adding extra feature will probably bork an OTA.
Click to expand...
Click to collapse
This. If you're modifying the stock ROM you might as well go with a custom ROM as far as OTA's go.
BrianDigital said:
but keep in mind, adding extra feature will probably bork an OTA.
Click to expand...
Click to collapse
It's also worth noting that - via the use of nandroid backups - that it's never an "all or nothing" deal.
There is absolutely nothing wrong with keeping a pure stock ROM "waiting in the wings" in the form of a complete Nandroid backup. When an OTA rolls out, you:
- back up your current ROM
- restore the older pure stock ROM from backup
- take the OTA (guaranteed to work!)
- take a Nandroid backup of the new version of Stock
- (restore custom recovery if needed)
- restore your custom ROM (from the Nandroid backup in first step), and then decide what you want to do about the OTA on this customized variant of stock.
That gives you the flexibility to revert to the current version of stock anytime you like - or use it as the base ROM for your favorite customizations.
bftb0 said:
It's also worth noting that - via the use of nandroid backups - that it's never an "all or nothing" deal.
There is absolutely nothing wrong with keeping a pure stock ROM "waiting in the wings" in the form of a complete Nandroid backup. When an OTA rolls out, you:
- back up your current ROM
- restore the older pure stock ROM from backup
- take the OTA (guaranteed to work!)
- take a Nandroid backup of the new version of Stock
- (restore custom recovery if needed)
- restore your custom ROM (from the Nandroid backup in first step), and then decide what you want to do about the OTA on this customized variant of stock.
That gives you the flexibility to revert to the current version of stock anytime you like - or use it as the base ROM for your favorite customizations.
Click to expand...
Click to collapse
Why are you quoting me?
Sounds like a lot of work to sit and wait for an ota, which don't come at specific time. Usually a nice person will compile a stock ROM, long before some users will get an ota notification.
I don't need the information why not quote the op, brah
Sent from my Nexus 7 using Tapatalk 2
BrianDigital said:
Why are you quoting me?
Click to expand...
Click to collapse
Because I can. There; I just did it again
Actually, the reason I quoted you was because I was responding to your point about customizing stock ROMs possibly jeopardizing application of OTAs. Quite true; but not a show-stopper for anyone willing to prepare in advance. And given that the device in question is a Nexus device, it is a virtual certainty that there will be more OTAs coming down the pike.
BrianDigital said:
Sounds like a lot of work to sit and wait for an ota, which don't come at specific time. Usually a nice person will compile a stock ROM, long before some users will get an ota notification.
Click to expand...
Click to collapse
You don't need to "wait"; you only do this at the time a new OTA comes out. Prior stock backups are just sitting there doing nothing until that time arrives. BTW, The current 4.2.2 "dev-stock" ROMs on this site can not accept OTAs because they have been zipaligned - none of the system .apks have hash checksums which match the factory files (even though they are functionally identical).
In addition to the previously mentioned advantages, someone that does this also has pure stock backups available to retrieve files from in the event they want to hand-patch their customized ROMs so they can get a failing OTA to "take". *That* is in fact a back-asswards way of doing things, but every time an OTA comes out, you observe a flood of stupid "please somebody give me file such and such" in this forum. That behavior comes from a lack of forethought and preparation (additionally made worse because Google pulls the *prior* factory install images well before the OTA has rolled out fully).
cheers ... and feel free to quote me
AW: add some features without flashing custom rom?
You can use "Pimp My ROM". You can find it here on xda. Works with stock too.
If you are running stock ROM, you can try these that I have been working on for the past week. I have a reboot menu among others.
http://forum.xda-developers.com/showthread.php?p=38749260
Sent from my Nexus 7 using Tapatalk 2
Over the next week or so I plan on making stock, deodexed roms from our fastboot system.img's. Other than Root, Busybox, init.d support, insecure adb, and being deodexed, they'll be completely stock -- nothing removed, nothing else added -- and are to be used as roms, the base rom for ports, whatever.
If you don't need insecured adb, delete /system/etc/init.d/AdbdInsecured
I include it because its a necessary feature for me.
All the roms* will be uploaded to my Goo.im page for Atrix HD
All the roms are for the locked AT&T Atrix HD running Jellybean 4.1.1.
Do not flash Gapps with the Stock Roms
Currently Done
Mexico Retail 4.1.2
AT&T 4.1.1* (not mine, see below)
To Do
Bell 4.1.2 (Jellybean)
ATT 7.7.1Q-115 (ICS)
Bell 7.7.1Q-115 (ICS)
ATT 7.7.1Q-144 (ICS)
Mods
Currently the only Mod available is the Extended Reboot Menu for stock AT&T DeOdexed, I'll make the same mod for other stock roms as I have the time.
Mexico Retail Info
Jellybean 4.1.2
Moto Blur 98.2.2 (oddly, AT&T JB 4.1.1 is Blur 98.4.20 -- this rom is higher Android Version, Lower Blur Version -- weird)
Very little bloat
WIFI didn't work until I added in the kernel modules from Stock AT&T. If you have errors, see first if it could be module related and replace the offending one.
* STOCK AT&T INFO
The stock AT&T rom is located on the Batakang FTP server and was not done by me. I assume Mattlgroff or SirHoover did that one. Someone let me know so I can give proper credits & thanks. It does not contain InsecuredAdb or init.d support. When I finish up the other stock roms on the list I'll make a Stock AT&T of my own, unless the current one's maker doesn't mind me adding init.d support and InsecuredAdb like the rest of mine on goo.im will have.
To Rom Cooks
For init.d support, I hid the init.d initialize command in /system/etc/init.qcom.bt.sh. Let me know if there's a better place to put that command or a script activated earlier in the init process we can edit.
Feel free to use my stock roms for whatever project you want. Thanks and credits are appreciated but not required.
I'm unsure if the ICS roms will even work with the Jellybean kernel & boot. I'll be finding out later on today.
Credit and Thanks
Gotta give Mattlgroff credit for the InsecuredAdb and reverse engineering Chainfire's
Thank You to whoever uploaded the Stock ATT Deodex on Batakang, I'm using its updater-script, su binary, & superuser.apk. I was lazy on the su part
I'm working on getting ICS to boot with the AT&T Jellybean kernel.
So far I'm able to get it to boot, do a complete gapps setup, but after that, it bootloops within a minute of accessing the homescreen.
Boots after that loop on the animation or will give ~30 seconds of usable display before looping.
Factory resetting allows for completing the initial setup.
If I sit on the Gapps setup page, it'll eventually start looping, but much longer than if I finished and accessed the homescreen.
I'm unable to pull any kind of logcat, ddms, etc since I can't get the PC to recognize it over usb (driver error???)
Any ideas?
I've tried replacing kernel modules with JB versions -- didn't work. By then it was after midnight so I went to sleep. That's where I'm at now. Gonna start testing out JB binaries and libs today.
Since we're able to get a working display, that makes me think that a stock ICS rom for JB users is possible. We just gotta figure out what needs to be backported from Jellybean. Maybe a new init script or an init.d script that'll fix what JB sets that ICS doesn't like.
Can someone running ICS please upload their init scripts? I'd like to compare them with JB's.
RAZRHD 4.1.2 firmware if you're still interested: http://sbf.droid-developers.org/vanquish/VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml.zip
As for getting ICS to boot, I think you're spot-on about the init files. Safestrap doesn't mess with / files, but it does create symlinks for /system, etc & execute init files that are placed in /system/etc/rootfs. This might be key to your efforts.
Epinter has a CM10 rom that uses a modified ICS kernel, but it has no problem running on my JB phone with SS (minus the camera). Although I had to repair his inits to fix a boot error & insert two /bin files. Perhaps you could use his rootfs/inits as a guide on getting ICS to work with SS on JB.
My safestrap fix for Epinter: http://forum.xda-developers.com/showthread.php?t=2178123
Epinter's ICS-based CM10: http://d-h.st/ML8
Update: Just found this: http://rootzwiki.com/topic/8794-bionic-safestrap-bootstrap-recovery-12142011/page__st__20
It says that SS moves anything in /system/etc/rootfs to /, so if you can get a hold of the ICS init files, that should be all you need to fix the boot.
SS, while convenient, is a serious pain in the ass as far as the init process goes....I miss Defy's 2nd-Init in that regard. Everything was in /system/bootmenu/*. The downfall with 2nd-Init is you lose and reinstall the bootmenu with every rom install -- Accidentally wipe /system and not install a rom? -- sbf time .
I'll take a look at the RAZR HD 4.1.2 fastboot today or tomorrow. Rainy day, so maybe today. I'm just hoping that the lapdock fix isn't kernel deep.
Thanks for the links, I'm sure they'll be invaluable.
I'm guessing here, but I think ICS's biggest issue is\will be USB -- I'm unable to get anything USB to work -- phone detecting USB or the PC detecting the Phone. Working blind with no logs, no usb, and a looping boot animation really sucks. With any luck, Moto didn't fully remove USB mounting via the kernel, only SW blocks in JB. While only briefly, I know that at least the display works, bluetooth turns on and off, I think audio works (can't remember if it beeped or not with the rocker presses),
Time to search for ICS init scripts then.
Later on tonight I'm going to upload the ICS dumps. They still don't work but I figured the libraries and binaries could be useful with CM10 porting. The Bell will be flashable since it has a working display -- if only until non stop looping .
For some interesting info...there are 2 different sets of ICS camera drivers. The first is 1st AT&T\Bell and the second is the other AT&T. Means ya got two different sets of drivers to test when porting .
/I really need to update my banner below :silly:
UPDATE
They're all uploading now. Should be done in 5-7 hours. My upload speed sucks.
All are flashable, but the ICS ones don't work. Only Tested 144-att and 115-bell.
I'm also uploading 4.1.2 Bell. It's untested but should work.
Obviously, only flash these on a rom slot. I've only used and tested on slot 1.
Skeevy , i really hope you or somebody else makes Paranoid Android available for AHD ( i know it's wishful thinking ).
For me its the only ROM worth flashing with the same android base version for the AHD . Not undermining the developer's efforts , all other ROMs (with same base version 4.1) that i came across here , I can get the same functionality and ui changes from a combination of custom launcher , root apps and some minor fixes here and there . I have not yet flashed a single custom ROM on my AHD , just rooted it and debloated it for the same reason .
I used to own a defy which was officially upgraded till froyo 2.2 only and boy did i flash the **** out of it . But that was only because of worthwhile functionalities in custom ROMs(be it CM 7,CM 10 by quarx, PA by you or MIUI) that couldn't be achieved by mere root apps or custom launchers .
thanks for this rom
AnkurBedi said:
Skeevy , i really hope you or somebody else makes Paranoid Android available for AHD ( i know it's wishful thinking ).
For me its the only ROM worth flashing with the same android base version for the AHD . Not undermining the developer's efforts , all other ROMs (with same base version 4.1) that i came across here , I can get the same functionality and ui changes from a combination of custom launcher , root apps and some minor fixes here and there . I have not yet flashed a single custom ROM on my AHD , just rooted it and debloated it for the same reason .
I used to own a defy which was officially upgraded till froyo 2.2 only and boy did i flash the **** out of it . But that was only because of worthwhile functionalities in custom ROMs(be it CM 7,CM 10 by quarx, PA by you or MIUI) that couldn't be achieved by mere root apps or custom launchers .
Click to expand...
Click to collapse
I'll be straight up with you, I could make PA for us but it wouldn't be the latest version. It would be 2.5.3 just like the Defy -- AOSPA (PA 3.0+) won't be possible until we're able to get AOSP to compile from source (the SourceForge crap). It would be based on Epinter's CM10, have the same bugs as CM10...basically I'd be making PA for another device then porting that over for us . It would probably take me 6-12 hours to do all the source merging, another 2 to compile, and a day to test then upload. There is no ETA cause I haven't started on anything nor is it on my to do list yet. Times are based on how long it took me to do the Defy merging, compiling, testing.
I'm unsure on the 4.1.2 Bell rom, but the 4.1.2 Mex Retail is worth using instead of stock -- less bloat, no entitlement checks.
I partially agree on the other 4.1 custom roms -- yes, you can do it all yourself, but not everyone can. Also, not everything is compatible, so if you don't know what you're doing and flash a bad, lets say audio tweak, and it doesn't work or loops you, you could be screwed simply by lack of knowledge. That's also why I released the one custom thing I've done as a standalone mod.
Rom cooks do a lot behind the scenes -- I've been working on a rom on and off since I've had my AHD. Only mentioned in here, in a PM, and maybe publicly once or twice. I've been testing various audio tweaks, launchers, scripts, mods....I don't want to give 2-3 week eta posts cause life happens, it might not work when I get to the moment of truth, and something always happens to make any specific eta I give wrong . I've been doing tons of testing, looking for something different than the AT&T stock base or RAZR port base(see this thread :silly, tons of apk decompiling (every 4.1.2 Atrix HD apk so far), and have been adding French\Canadian English to the MR base (25 apps in). Other than that, all I know is its gonna be PlayStation Certified (already have PS Store fully working). Can't say more cause I don't know any more than that :cyclops: Point is, other cooks do tons of crap behind the scenes to ensure a good, working environment that you can't get without doing\knowing some ****. If I wasn't trying to do so much I might have had something usable by now -- I've messed with ICS, CM10 porting, SF sources, stock smali mods, my own rom, alternate stock roms.
Luckily, I still have my Defy and Bravo. Quarx is still going strong and pushing out new CM's, kernels, and everything good. One can only hope that we'll have even a quarter of the roms the Defy has. I'm so glad my first Android phone was a Defy clone. I've learned a lot because of it.
Looking forward for your custom rom skeevy :thumbup:
Sent from my MB886 using xda app-developers app
Going to test out the Bell ROM and will report results later tonight or tomorrow. Thanks so much for the upload and the work youve done so far!
I'm trying to boot into the Bell ROM and am currently stuck at a bootloop when the boot image says "Android" not sure what to do to correct this problem, I have the zip file install in ROM Slot 1 with 2GB partition size
Edit: Tried again with 1GB size also just to see if there was any difference, the error im getting has to do with the md5 of the ROM, when i enable both checks it automatically fails, however if i bypass them and continue to flash the ROM it gets stuck in a bootloop as mentioned before
Thanks a lot for your hard work,skeevy. I had a Defy green lense two years ago and sold it a year ago. Luckily,I still can enjoy modding it coz my friend still got it. It's a beast phone with all those mods by you,quarx,epsilon and maniac103. With the lack of official updates and locked bootloader,Defy can do all the impossible things. I've even seen the newest 3.x kernel with CM10.1. You guys have done a great job. Let's hope Atrix HD got the same treatment.
Sent from my MB886 using Tapatalk 2
freshlycutlawn said:
I'm trying to boot into the Bell ROM and am currently stuck at a bootloop when the boot image says "Android" not sure what to do to correct this problem, I have the zip file install in ROM Slot 1 with 2GB partition size
Click to expand...
Click to collapse
Try replacing kernel modules with the stock AT&T ones. After that I'd be guessing and would need to see a logcat if possible. That's for Bell JB, btw. Not sure what to do with any of the ICS roms at the moment.
@huatz84
If we only had Quarx, Epsylon, and Maniac103....man, AHD development would really kick off. Those 3 get **** done. I mean, they only had JB running on a Froyo kernel with Froyo\GB hybrid drivers and only 317mb of /system space to work with.
skeevy420 said:
Try replacing kernel modules with the stock AT&T ones. After that I'd be guessing and would need to see a logcat if possible. That's for Bell JB, btw. Not sure what to do with any of the ICS roms at the moment.
@huatz84
If we only had Quarx, Epsylon, and Maniac103....man, AHD development would really kick off. Those 3 get **** done. I mean, they only had JB running on a Froyo kernel with Froyo\GB hybrid drivers and only 317mb of /system space to work with.
Click to expand...
Click to collapse
I will try that tonight when I get a chance and let you know how it works. The only thing im wondering is that since my device currently with bell is only on 4.0.4 that the kernel with jellybean roms wont work because I dont have the right kernel to go with the JB rom
freshlycutlawn said:
I will try that tonight when I get a chance and let you know how it works. The only thing im wondering is that since my device currently with bell is only on 4.0.4 that the kernel with jellybean roms wont work because I dont have the right kernel to go with the JB rom
Click to expand...
Click to collapse
Did not know that...could also be an init script issue then. Ignore the first suggestion, I assumed you were an AT&T JB user, use the Bell ICS modules instead.
skeevy420 said:
@huatz84
If we only had Quarx, Epsylon, and Maniac103....man, AHD development would really kick off. Those 3 get **** done. I mean, they only had JB running on a Froyo kernel with Froyo\GB hybrid drivers and only 317mb of /system space to work with.
Click to expand...
Click to collapse
Yeah..they are amazing. With the tiny system space,they can build a stable JB rom with Froyo kernel. They've made impossible things.
Btw,I just saw that Moto includes Razr HD and Razr M to their unlocked bootloader program. Hopefully,They add Atrix HD soon.
skeevy420 said:
Did not know that...could also be an init script issue then. Ignore the first suggestion, I assumed you were an AT&T JB user, use the Bell ICS modules instead.
Click to expand...
Click to collapse
I'm going to try to flash the Bell ICS file and see how that goes and if it triggers an OTA update, if theres anything I can do to help with the development of these ROMs please let me know, I have access to a Bell Atrix HD with an unlocked bootloader so id like to do all I can
Edit: Tried the 4.0.4 Bell ROM just now and I'm getting the same error while trying to flash
--Verify md5 for /external_sd/404-115-bell.zip
-- No md5 file found!
If I uncheck the boxes to verify the md5 I can successfully flash the zip but it still gets stuck in the bootloop like the JB ROM
EDIT:
Successfully booted into the ICS ROM since I was on 4.0.4 myself and am getting the prompt to update to 4.1.2 now, it looks like when you upgrade to 4.1.2 the kernel becomes incompatable with the older ROM's and vice versa. It looks like once one is on JB there is no going back. The flash worked without me ticking the boxes which doesn't seem to be the problem, only firmware, hopefully this helps and explains why the ICS ROMS begin to instantly bootloop once you try to boot into them since im assuming youve updated at this point. Since I used a 2GB ROM slot I was getting low memory errors so I'm going to remake the slot with 1GB and am going to reflash and try the update and see if the flash for 4.1.2 directly works and if I can boot back into 4.0.4 again.
huatz84 said:
Yeah..they are amazing. With the tiny system space,they can build a stable JB rom with Froyo kernel. They've made impossible things.
Btw,I just saw that Moto includes Razr HD and Razr M to their unlocked bootloader program. Hopefully,They add Atrix HD soon.
Click to expand...
Click to collapse
Me too. Sucks we have an unlockable bootloader that we can't unlock due to Moto not supporting it. Some HD's are unlockable which is the real teaser to the rest of us.
freshlycutlawn said:
I'm going to try to flash the Bell ICS file and see how that goes and if it triggers an OTA update, if theres anything I can do to help with the development of these ROMs please let me know, I have access to a Bell Atrix HD with an unlocked bootloader so id like to do all I can
Edit: Tried the 4.0.4 Bell ROM just now and I'm getting the same error while trying to flash
--Verify md5 for /external_sd/404-115-bell.zip
-- No md5 file found!
If I uncheck the boxes to verify the md5 I can successfully flash the zip but it still gets stuck in the bootloop like the JB ROM
EDIT:
Successfully booted into the ICS ROM since I was on 4.0.4 myself and am getting the prompt to update to 4.1.2 now, it looks like when you upgrade to 4.1.2 the kernel becomes incompatable with the older ROM's and vice versa. It looks like once one is on JB there is no going back. The flash worked without me ticking the boxes which doesn't seem to be the problem, only firmware, hopefully this helps and explains why the ICS ROMS begin to instantly bootloop once you try to boot into them since im assuming youve updated at this point. Since I used a 2GB ROM slot I was getting low memory errors so I'm going to remake the slot with 1GB and am going to reflash and try the update and see if the flash for 4.1.2 directly works and if I can boot back into 4.0.4 again.
Click to expand...
Click to collapse
Good to know that. Sucks JB doesn't work for you, but at least we're both able to get to the boot animation and loop it -- we could be stuck at the boot logo. With any luck I'm hoping that we can find the right combination of files to replace to get the roms to boot with the wrong kernels. We at least know its possible since JB kernel can have a working ICS rom for about 3 minutes .
Since you have an unlockable bootloader why don't you just flash a jellybean boot.img? Unpack and repack it so its not signed and you shouldn't have any issues. You could probably start using the RAZR HD unlocked bootloader roms and recoveries and never see us again.
Holy crap... I am running ICS on my JB AHD!!! It's been 10 minutes and no boot loops so far
I restored a Safestrap ICS backup, then put some ICS init files in etc/rootfs (I attached my flashable ZIP fix).
Camera doesn't work - same for WIFI but I'm sure it's a simple driver fix.
Also attached are the full ICS init files, in case you want to compare and contrast with JB inits. I omitted qcom inits in my fix.
Well that's awesome. 10 minutes beats what I've been able to do :highfive:
Wifi didn't work with MR either -- I needed AT&T wifi modules (or probably the wifi modules of the stock kernel currently running). -- /system/lib/modules/prima/* & system/lib/modules/config.ko
From what I can tell we have 3 sets of Camera Drivers (2 are ICS drivers, 1 more for JB) -- 115-att & 115-bell are the same\1st one, 144-att is 2nd, & all JB roms are the same\3rd. I'm unsure as to what all libs are necessary for the camera with us other than the obvious /lib/camera*, lib/hw/camera*, and bin/mm-qcamera-daemon. We might need to use the JB camera app as well. Also, the 144-att camera libs have more files than the 115's -- they're similar to the JB ones (1st driver doesn't have /lib/libchromatix_ov8820_hfr_60fps.so, everyone else does).
The biggest difference of the 3 JB roms, from what I can tell, are the kernel modules; libraries and drivers are the same.
I'm being a little optimistic, but hopefully whatever works for ICS on JB kernel will work for CM10 as well; and that we can invert what we're doing to get JB working with the ICS kernel.
I know what I'm doing today.
Does anyone know if there is a way to install HyperDrive Tweaks 2.0 on an SGH-i537 running 4.2.2 and MF3? How about just the Device Menu(shutdown menu)? I really like HyperDrive and run 10.2 from slot 1, but since I can't run it as my stock ROM, I was looking for ways to customize my stock ROM.
monkeyhouse said:
Does anyone know if there is a way to install HyperDrive Tweaks 2.0 on an SGH-i537 running 4.2.2 and MF3? How about just the Device Menu(shutdown menu)? I really like HyperDrive and run 10.2 from slot 1, but since I can't run it as my stock ROM, I was looking for ways to customize my stock ROM.
Click to expand...
Click to collapse
I know we've been talking a bit in the other thread, but is there a reason you want to customize your stock ROM with tweaks rather than just using Hyperdrive in slot 1? Ideally here's what I would do if I ever had to start over:
Flash phone to stock MF3 at local Best Buy
Before setting up my phone again, copy the entire phone and post a zip for the community
Do not set up stock ROM, simply root and install SafeStrap
Max out the memory settings on slot 1 and only use slot 1.
The benefit to doing this is I would have an almost completely untouched stock ROM that I could always use to receive official updates while still running a custom ROM as my default.
Devo7v said:
I know we've been talking a bit in the other thread, but is there a reason you want to customize your stock ROM with tweaks rather than just using Hyperdrive in slot 1? Ideally here's what I would do if I ever had to start over:
Flash phone to stock MF3 at local Best Buy
Before setting up my phone again, copy the entire phone and post a zip for the community
Do not set up stock ROM, simply root and install SafeStrap
Max out the memory settings on slot 1 and only use slot 1.
The benefit to doing this is I would have an almost completely untouched stock ROM that I could always use to receive official updates while still running a custom ROM as my default.
Click to expand...
Click to collapse
Well, so far, my experience has been that the stock ROM is the most stable. Since I have seen HyperDrive and GPE and have even added some things from Sony Zperia, I see things I like in all of those. If I can tweak my stock and have all the parts from other ROM's that I like, why wouldn't I? There is no local Best Buy here, but I rarely take my equipment to a business for service, too many kids who don't really know what they are doing, I guess. Also, I thought I read somewhere that unlocking my phone was what would prohibit me from installing updates? But since you mention that subject, couldn't I clean the slots, un-root, remove safestrap and do a factory rest and have my original ROM? I know last week I was trying to flash a widget and I did a factory reset, wiped cache and it seemed to be stock to me. I know I had to re-setup my accounts and re-download my apps. I was able to download the last AT&T update, just couldn't install, but I still had root and safestrap. So, from what I read, I could probably install the update if I wanted to and took care of root.
So, I guess to answer your question, I get a kick out of making changes in general, whether if be with my stock ROM or an added one. I'm not a developer, but I do wish I knew more about the OS so I could help with the bootloader issue.
One thing for sure, I definitely appreciate the help I get from the folks here. Pretty fun stuff.
So I finally got me a sweet deal and got a second hand XT1053.
Unlocked its bootloader, then flashed T-Mobile´s 4.4.3 and finally the OTA to 4.4.4, because here in Mexico all I was able to get was 4.4.2.
Now, I want to try custom ROMs, and Ive been reading about the procedure.
As any sane person would, I want a nandroid backup before messing around. Im guessing flashing TWRP will take care of this, like it did with my LG L9, right?
Is it wise to do this on the verge of Android L being ported to our Moto X?
How difficult is it to get the phone to a fully stock state (minus the bootlader, of course)? As far as I know, I only need to flash my nandroid backup then flash the stock recovery. Is it as simple as that?
I read somewhere that flashing custom ROMs messed up with Motorola´s active display/voice control, and I assumed they meant that custom ROMs lacked these features because of their proprietary nature. Am I correct? Or does some kind of unrepairable damage will forever afflict these features, even if I get back to stock?
And lastly, what ROM do you recommend? I´d like the active display feature if possible, guess I can do without it. CM theme chooser would be nice too.
Thanks in advance, eagerly awaiting some answers before I take a step forwards.
Attached a screenshot of my phone´s info.
You are right about everything you've mentioned. Good research done for sure! ?
Do a backup with twrp. And yes, you can restore it and flash the stock recovery and you're good for the OTA.
Aosp/cm roms don't have the Moto features. But yes, you can return to stock and have them again. There's a few stick based custom roms that of course still have the features. The other roms, unless something changed, do come with some bugs unfortunately as well.
Most use stock, with gravity box for customizing.
And in case you missed it.... Never try to downgrade from 4.4.4....or you risk your device bricking. You can flash lower version custom roms, cause they won't try to change the bootloader. But don't downgrade stock firmware. Ever. ?
Enjoy!
Thank you very much!
As soon as I read this I rooted my phone, I´ll check a ROM or two before settling on one for daily use, have heard nice things about krypto´s one.
And yeah, there can never be enough warnings, I´ll treat the T-Mobile stock ROM as if it were my very first one.
One question though, the latest version of T-Mobile firmware is 4.4.3 under http://sbf.droid-developers.org/phone.php?device=0 so Im gussing I should only use my nandroid backup, right?
Thanks in advance!
no_un_bot said:
Thank you very much!
As soon as I read this I rooted my phone, I´ll check a ROM or two before settling on one for daily use, have heard nice things about krypto´s one.
And yeah, there can never be enough warnings, I´ll treat the T-Mobile stock ROM as if it were my very first one.
One question though, the latest version of T-Mobile firmware is 4.4.3 under http://sbf.droid-developers.org/phone.php?device=0 so Im gussing I should only use my nandroid backup, right?
Thanks in advance!
Click to expand...
Click to collapse
Until there's a 4.4.4 SBF, yes. That's the safest bet.
newbie needs details
no_un_bot said:
So I finally got me a sweet deal and got a second hand XT1053.
Unlocked its bootloader, then flashed T-Mobile´s 4.4.3 and finally the OTA to 4.4.4, because here in Mexico all I was able to get was 4.4.2.
Now, I want to try custom ROMs, and Ive been reading about the procedure.
As any sane person would, I want a nandroid backup before messing around. Im guessing flashing TWRP will take care of this, like it did with my LG L9, right?
Is it wise to do this on the verge of Android L being ported to our Moto X?
How difficult is it to get the phone to a fully stock state (minus the bootlader, of course)? As far as I know, I only need to flash my nandroid backup then flash the stock recovery. Is it as simple as that?
I read somewhere that flashing custom ROMs messed up with Motorola´s active display/voice control, and I assumed they meant that custom ROMs lacked these features because of their proprietary nature. Am I correct? Or does some kind of unrepairable damage will forever afflict these features, even if I get back to stock?
And lastly, what ROM do you recommend? I´d like the active display feature if possible, guess I can do without it. CM theme chooser would be nice too.
Thanks in advance, eagerly awaiting some answers before I take a step forwards.
Attached a screenshot of my phone´s info.
Click to expand...
Click to collapse
hello, i a newbie to all of this
i have the same device as yours, how did you do that? details if it not much trouble
sherif2015 said:
hello, i a newbie to all of this
i have the same device as yours, how did you do that? details if it not much trouble
Click to expand...
Click to collapse
Hi there, Im at work and cannot explain in much detail, but when I get home i will help you out.
You can send me a private message if you want me to explain in español.
no_un_bot said:
Thank you very much!
As soon as I read this I rooted my phone, I´ll check a ROM or two before settling on one for daily use, have heard nice things about krypto´s one.
And yeah, there can never be enough warnings, I´ll treat the T-Mobile stock ROM as if it were my very first one.
One question though, the latest version of T-Mobile firmware is 4.4.3 under http://sbf.droid-developers.org/phone.php?device=0 so Im gussing I should only use my nandroid backup, right?
Thanks in advance!
Click to expand...
Click to collapse
SBF.Droid-Developers.org hasn't been updated in a while, at least as far as the X (2013 or 1st Gen edition) Roms.
Another possible source is -> http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1 however, they don't have a 4.4.4 SBF for the XT1053 either.
And you can keep an eye on https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images since Moto should post the 4.4.4 SBF for the Developer Editions. Eventually an XT1053 (GSM) and an XT1060(VZW) 4.4.4 should pop up there, whenever Moto finally gets around to it.
no_un_bot said:
Hi there, Im at work and cannot explain in much detail, but when I get home i will help you out.
You can send me a private message if you want me to explain in español.
Click to expand...
Click to collapse
Hi sorry for bothering you but i really need your help.
English will be fine .
other users might get here so it will be nice to help them as well
thanks for your time
sherif2015 said:
Hi sorry for bothering you but i really need your help.
English will be fine .
other users might get here so it will be nice to help them as well
thanks for your time
Click to expand...
Click to collapse
Alright, guess everything is out there but I don´t mind.
Can you tell me what system version have you got?
Its displayed under Settings > About phone
reply
no_un_bot said:
Alright, guess everything is out there but I don´t mind.
Can you tell me what system version have you got?
Its displayed under Settings > About phone
Click to expand...
Click to collapse
Kitkat 4.4.2 xt1053
same phone, problems loading roms
I have the same phone, I also recently got second hand.
Moto x xt1053 (gsm) carrier unlocked, currently in kitkat4.4.2, running Kangakat 2 rom (came with it), unlocked bootloader, rooted and using SuperSU, newest version of twrp like 2.8 or something like that.
I want to load a custom rom but am having problems, downloaded P.A.C. and AOKP (two i have tried to use) for the device msm8960 using there stable versions not the nightlies. Went into twrp, created backup, factory wiped, flashed rom and g-apps, was "successful" no errors but on reboot of phone it gets stuck in boot loop and won't start up. for the P.A.C i was able to get into twrp and reflash my back up, for the AOKP twrp kept getting stuck on that teamwin image and i could only finally access it by having the usb cable plugged into my computer. I am not a noob, but definately not an expert.
So did you have any luck flashing a new rom to your phone? Does anyone have any advice for me? I really would like to try some different roms.
Thanks
[emoji15]
I hate Tapatalk for all the time spent writing a quick reply and its gone.
Anyways, first of all, make sure you have the latest recovery available, I remember back with my old phone, funky installations happened if you weren't on the latest recovery. I recommend philz one, has support for some pesky partitions that sometimes get messed and other recoveries won't back up.
Now, in my particular case, I first upgraded my 4.4.2 Nextel stock to 4.4.3 T-Mobile stock using RSDLite, then took the OTA to 4.4.4, and until then I figured I'd play with ROMs. Have had no issues other than something I've addressed on another thread and I ultimately fixed.
My suggestion is going back to full stock then doing everything yourself so you know what's actually going on.
You'll have to flash a custom recovery and then root it again but with an unlocked bootloader that's ezpz.
Remember never to downgrade (that is, flashing a lower android version than what you currently run) stock official images (such as the ones from sbf-developers) because you WILL brick your phone. People say you can downgrade when flashing custom ROMs but I wouldn't risk it, and I don't really see why I'd want that.
Double check whatever file you'll try to flash, always use stuff intended for your model, and when that's not possible verify if other users with your model have reported it works for them. As per the version thing, I believe the most recent development unified models under the GHOST parameter but take my words for what they are, that is, my view on things, you should always make one for yourself.
Ask if you don't completely understand a step BEFORE doing it, there's good people willing to help you out.
Best of luck.