*removed*
So this update patch does the radio hack without using radiocomm?
I thought half the fun was knowing you might brick your phone the process lol
This may work with the modified safestrap 1.08f as it allows you to flash to the non-safe system. Just a thought.
Sent from my DROID3 using xda premium
buckmarble said:
This may work with the modified safestrap 1.08f as it allows you to flash to the non-safe system. Just a thought.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
Good thought, but I already tried with 1.08e and it didn't work; you're welcome to try with 1.08f, if it works let is know!
install update from sdcard? correct?
Jason Roach said:
install update from sdcard? correct?
Click to expand...
Click to collapse
Yes, with Koush's clockwork recovery or Hashcode's tweaked clockwork recovery.
Ive already done the radiocomm hack, so i cant verify for you.
Sent from my DROID3 using xda premium
Q9Nap said:
Good thought, but I already tried with 1.08e and it didn't work; you're welcome to try with 1.08f, if it works let is know!
Click to expand...
Click to collapse
The install to unsafe didn't work with 1.08e but was fixed with 1.08f..
I can confirm it works
cool
ovelayer said:
The install to unsafe didn't work with 1.08e but was fixed with 1.08f..
I can confirm it works
Click to expand...
Click to collapse
Are you confirming that you used 1.08f to install this tether patch or confirming that installing to unsafe mode works on 1.08f?
Q9Nap said:
Are you confirming that you used 1.08f to install this tether patch or confirming that installing to unsafe mode works on 1.08f?
Click to expand...
Click to collapse
Just that you need 1.08f to flash to unsafe..I have had no need to do the radio hack as android-wifi-teather has always worked for me
buckmarble said:
Ive already done the radiocomm hack, so i cant verify for you.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
You could verify whether the unpatch works, & if it does you could repatch. I highly doubt it will work though.
Safestrap won't perform this update properly because it doesn't have the motorola.update_nv() function in its updater handling; however, it wouldn't be very hard to incorporate. (If you extract the updater-script from this .zip file and open it up in a text editor, you'll see what I mean.)
I'm hoping to bust out another release fixing a few more bugs, I'll see if I can squeeze this in there too. I don't have an XT862 to test this on unfortunately but any guinea pigs who want to help me test it out are more than welcome to PM me.
Rick#2 said:
Safestrap won't perform this update properly because it doesn't have the motorola.update_nv() function in its updater handling; however, it wouldn't be very hard to incorporate. (If you extract the updater-script from this .zip file and open it up in a text editor, you'll see what I mean.)
I'm hoping to bust out another release fixing a few more bugs, I'll see if I can squeeze this in there too. I don't have an XT862 to test this on unfortunately but any guinea pigs who want to help me test it out are more than welcome to PM me.
Click to expand...
Click to collapse
See why your my hero lol...ya gotta love this guy! Im in for helping ya test things out.
Rick#2 said:
Safestrap won't perform this update properly because it doesn't have the motorola.update_nv() function in its updater handling; however, it wouldn't be very hard to incorporate. (If you extract the updater-script from this .zip file and open it up in a text editor, you'll see what I mean.)
I'm hoping to bust out another release fixing a few more bugs, I'll see if I can squeeze this in there too. I don't have an XT862 to test this on unfortunately but any guinea pigs who want to help me test it out are more than welcome to PM me.
Click to expand...
Click to collapse
I'd be willing to test also, but looks like it may not be necessary; just saw this post:
http://forum.xda-developers.com/showthread.php?p=25553417
I knew about this method for unlocking tethering on razr but didn't even think about trying it on d3...
dsw361 said:
"I have not confirmed that this works for Droid 3 it may only work on Motorola 4g phones so maybe someone can confirm if it works or not as i have already done the radiocomm hack."
Click to expand...
Click to collapse
I think he posted this as an idea, since it worked on another device, without verifying it worked on the Droid 3, then prematurely posted it to the other threads telling folks the other methods were not needed. There are at least two confirmed instances where it does not work on the Droid 3.
I am sticking with the radiocomm method.
Q9Nap said:
I'd be willing to test also, but looks like it may not be necessary; just saw this post:
http://forum.xda-developers.com/showthread.php?p=25553417
I knew about this method for unlocking tethering on razr but didn't even think about trying it on d3...
Click to expand...
Click to collapse
entitlement check doesn't work for d3 i tried this back when it was out for the bionic
mattdavis523 said:
entitlement check doesn't work for d3 i tried this back when it was out for the bionic
Click to expand...
Click to collapse
Thanks for confirming that method doesn't work; was going to experiment with it today & you saved me some wasted time.
So getting back to tweaked safe strap, Rick#2 please incorporate NV editing functionality into your next build!
Hey bud just ta let you know.
Last night i softbricked my phone and had to sbf somehow i lost the ability to wifi teather
So i tried to use your zip through cwm sence safestrap wont alllow it yet,and unfortuneately
It did not work for me..but i did find a solution i posted in my thread..
Just a heads up!
ovelayer said:
Hey bud just ta let you know.
Last night i softbricked my phone and had to sbf somehow i lost the ability to wifi teather
So i tried to use your zip through cwm sence safestrap wont alllow it yet,and unfortuneately
It did not work for me..but i did find a solution i posted in my thread..
Just a heads up!
Click to expand...
Click to collapse
Could you please be more specific on how it didn't work?
Related
Just wanted to let everyone know I finally updated the Build.Props on Rom Manager to be safe to use with the new .320/.340 system update. Have at it... (and stop asking me, lol)
LexusBrian400 said:
Just wanted to let everyone know I finally updated the Build.Props on Rom Manager to be safe to use with the new .320/.340 system update. Have at it... (and stop asking me, lol)
Click to expand...
Click to collapse
Thanks!!!!
Would you ever advise not using this file? I am curious if I should implement it on Liberty....
cbaty08 said:
Thanks!!!!
Would you ever advise not using this file? I am curious if I should implement it on Liberty....
Click to expand...
Click to collapse
This is EXACTLY what I'm using on Liberty
SaaaaWEET! Thanks!
WARNING: DO NOT FLASH THIS ON ANY PHONE
IT CONTAINS A NEW BOOTLOADER THAT WILL HARD BRICK YOU AND NOT FEEL GUILTY
All of the credit belongs to devs. Samcripp for setting up Project Cheesecake, the effort to find as many international builds as possible located on cloud servers. Navalynt for cloud test CWM mod. Tenfar for CWM bootstrap. Nate_benji for retrieving the update and uploading it for development purposes.
samcripp said:
SUCCESS
I have in my position a full OTA update. This has Bell GB, but no unlock and it also has the new dreaded ap20 BL, thats been hard bricking ATT phones when people try to sbf to older builds.
Click to expand...
Click to collapse
This is what we know so far about the build. I'm making this thread only to supply the link for the update so that hopefully we can start figuring out how we can use it (if at all). 2nd-init is a possibility, and sifting through the folders might yield to some breakthroughs.
Before I supply the link I want to remind everyone not to flash this on their phone.
Link:
Nate_benji's Megaupload
Multiupload link
Folders in root:
META-INF
patch
preinstall
recovery
system
webtop
ap20bl.img
bp.img
cdrom
cdt.bin
logo.bin
metadata.gpb
Looking forward to see if we can get anything from this, and lastly, thanks again to the devs.
Reserved for devs
You guys realize you can simply use the files to create an update-zip that takes out Motorola's assert checks and bootloader flash?
Very good news!
EDIT: Oops... I forgot that you don't have an unlocked bootloader to work with. It should be a bit more difficult then.
Would it be possible to re-package it with our current bootloader? I imagine this already would have been tried with other updates if it was possible.
D_one said:
Would it be possible to re-package it with our current bootloader? I imagine this already would have been tried with other updates if it was possible.
Click to expand...
Click to collapse
I can't say for sure but what would be great is if we could manufacture a "fruitcake" like package that would leave our BL alone. But once again, we don't have an sbf to fall back to, so we'd need to backup all of our partitions.
kennethpenn said:
You guys realize you can simply use the files to create an update-zip that takes out Motorola's assert checks and bootloader flash?
Very good news!
EDIT: Oops... I forgot that you don't have an unlocked bootloader to work with. It should be a bit more difficult then.
Click to expand...
Click to collapse
Indeed it will be tricky... Is there a way you can help out w/o using an atrix?
Where to download Bell sbf？ U4_0.37.?
cctv35 said:
Where to download Bell sbf？ U4_0.37.?
Click to expand...
Click to collapse
I highly suggest you don't download anything since you clearly didnt read the post
The most important part is that you shouldnt be flashing anything, also, its an OTA
Ok what about this nv flash where you have to have the special cable? Would it be possible for non at&t ATRIX phones to use that method to flash our unlockable bootloader then use the the files from the rom you now have and make a fruit cake? Just theory I don't think I've read of anyone doing nv flash.
Sent from my MB860 using XDA Premium App
*Facepalm ^
Do you guys even have a stock sbf yet? I forget if NFHimself managed to make something crazy for you guys or not. *goes digging for threads*
http://forum.xda-developers.com/showthread.php?t=1059643&page=5
You can just replace some of the files, the rest need to be patched which will be a pain.
Can a dev who has installed this please post some screenshots? I'd love to see how the Bell version of Gingerbread looks!
the2dcour said:
Do you guys even have a stock sbf yet? I forget if NFHimself managed to make something crazy for you guys or not. *goes digging for threads*
http://forum.xda-developers.com/showthread.php?t=1059643&page=5
You can just replace some of the files, the rest need to be patched which will be a pain.
Click to expand...
Click to collapse
What files need to be patched?
Can't all the necessary partitions + system.img be backed up?
IrshaadH said:
Can a dev who has installed this please post some screenshots? I'd love to see how the Bell version of Gingerbread looks!
Click to expand...
Click to collapse
No one has installed this, because it contains the new ap20bl.
I'm pretty sure we'll have a bell-version 2nd-init soon though.
yes setevendeb25 is surely working on something
Magnetox said:
No one has installed this, because it contains the new ap20bl.
I'm pretty sure we'll have a bell-version 2nd-init soon though.
Click to expand...
Click to collapse
kennethpenn said:
You guys realize you can simply use the files to create an update-zip that takes out Motorola's assert checks and bootloader flash?
Very good news!
EDIT: Oops... I forgot that you don't have an unlocked bootloader to work with. It should be a bit more difficult then.
Click to expand...
Click to collapse
Its UNLOCKED now!!! Hopefully someone can create a cwm4 flashable zip for us..
nate_benji said:
Its UNLOCKED now!!! Hopefully someone can create a cwm4 flashable zip for us..
Click to expand...
Click to collapse
Mhm... hopefully sam is able to get us some Fruitcake!
bongd said:
Mhm... hopefully sam is able to get us some Fruitcake!
Click to expand...
Click to collapse
Any idea what Gingerbread build he's basing the Fruitcake on?
nate_benji said:
Any idea what Gingerbread build he's basing the Fruitcake on?
Click to expand...
Click to collapse
He's kindly asked which SBFs he should prepare Fruitcake for (lol that sounded so weird).
I'm pretty sure he'll do it for Bell, French/Orange SBF, the popular ones for sure... man, I'm so pumped!!!
Hi,
Is this the latest Bell GB build?
Can't you just use CWM and edit out the bits in updater that reference ap20bl? And delete ap20bl.img as well of course.
Is there a better boot loader out there that fixes the ram issue? Maybe a swap in would be a better idea.
This OTA is a patch so you will have to be on Bell's 37.23. I backed up all my .23 partitions if anyone needs them. I was able to get back to .23 without unlocked boot header from ORGB using edited French 2.1.1, just removed all fs code groups basically. Fuse still the same though (cat /sys/firmware/fuse/ReservedOdm=20002000200004000) .
Cheers!
This thread is out of date and has been deprecated.
Please visit the link below for up-to-date information.
http://www.droidhive.com/forums/ind...-2233-235-find-out-here-download-links-in-op/
Reviews from XDA Users
Translated to Spanish!
¿Hables español?
jmshupin said:
Just followed your instructions and it worked quickly and flawlessly coming from .902, you sir, tuckmobile, are a scholar and a gentleman
Click to expand...
Click to collapse
jake1066 said:
It really is easy. This is coming from a guy that has never even rooted before and now I am running eclipse 2.2 thanks to your guide. Thank you tuck for your clear step by step guide that made this painless for even a noob like me.
Click to expand...
Click to collapse
nobe1976 said:
I have to say this this is absolutely the best guide to get this phone rooted and customised. Got my Bionic on Monday and after a little bit of light reading on these forums I now have a rooted stock system and with Safestrap I have a system that I can mess around with.
Click to expand...
Click to collapse
rtfelt said:
Thank you. Thank you, you are the man. I had rooted my bionic right after getting it in September 2011, but then with the automatic updates, I lost root and was unable to get it back. This guide worked perfectly!
Click to expand...
Click to collapse
bjscrdt said:
Thanks for the great/easy instructions, it is like having a whole new phone after I rooted my Bionic. Running Eclipse now, very smooth
Click to expand...
Click to collapse
Nice guide... very easy to follow!
I'm curious what happens if I follow this and I'm on .896. I'm already rooted, but nothing like roms, themes or mods have been installed.
Any objection with me making a video tutorial following all these steps?
Sent from my DROID BIONIC using XDA App
Is it good to do a factory reset before doing a root? Or any other tips or suggestions before starting?
Sent from my DROID BIONIC using XDA App
Pretty sure when you do this it will wipe you phone so factory reset eould be a wasteof time
Sent from my DROID BIONIC using XDA App
No need for a factory reset.
Sent from my DROID BIONIC using XDA App
CC Lemon said:
Nice guide... very easy to follow!
I'm curious what happens if I follow this and I'm on .896. I'm already rooted, but nothing like roms, themes or mods have been installed.
Click to expand...
Click to collapse
No idea what .896 is.
thereisone said:
Is it good to do a factory reset before doing a root? Or any other tips or suggestions before starting?
Click to expand...
Click to collapse
bfitzpatrickd2d said:
Pretty sure when you do this it will wipe you phone so factory reset eould be a wasteof time
Click to expand...
Click to collapse
Darca said:
No need for a factory reset.
Click to expand...
Click to collapse
You shouldn't reset anything before you begin. This method will create a backup of your stock system using SafeStrap. You can always return to your original setup using SafeStrap. Just reverse the toggle setting for Safe system (step 21). The wipe in step 22 is all you'll need.
I'd recommend reading a little about how SafeStrap works if you're feeling uncertain. There's a link to the Safestrap website in the "Credits" section of the OP.
Loving KIN3TX. Thanks Tuck! How do you know which themes we can run on this 901 version?
Sent from my DROID BIONIC using Tapatalk
ms0chez said:
Loving KIN3TX. Thanks Tuck! How do you know which themes we can run on this 901 version?
Click to expand...
Click to collapse
I'm using [H]on3yScr3am: http://rootzwiki.com/topic/10340-tpax-hon3yscr3am/ (Props to MasturMynd).
I'm not sure its technically built for 901, but its working fine for me and looks awesome. Basic steps to installing are 1)Download .zip to SD-card 2)Backup (step 20 in OP) 3)Install .zip in Safestrap (steps 23 and 24 in OP). Wipe shouldn't be necessary for this theme, it is built into the script.
Always backup before you do anything.
Other themes ("Tpax") for Kin3tix are here: http://rootzwiki.com/forum/264-th3oryrom/
When I get some time I'll break this down further and add to OP.
K cool. Not to sound like complete dumbfounded noob but does it matter which we backup to? Meaning the internal sd and external sd?
Sent from my DROID BIONIC using Tapatalk
ms0chez said:
K cool. Not to sound like complete dumbfounded noob but does it matter which we backup to? Meaning the internal sd and external sd?
Click to expand...
Click to collapse
Nope. I use the external sd cuz I have more room there. Just keep it organized.
When it comes to the .901 file, the file reads Blur_Verzion.5.5.893.XT875.Verizon.en.US.zip
The file name makes it look like the one pre .901. Can you confirm the file is correct and just named wrong? With MegaUpload gone, I'm not sure the MediaFire link is correct. I'm looking for another source for .901, but in case I don't find it....
technomaje said:
When it comes to the .901 file, the file reads Blur_Verzion.5.5.893.XT875.Verizon.en.US.zip
The file name makes it look like the one pre .901. Can you confirm the file is correct and just named wrong? With MegaUpload gone, I'm not sure the MediaFire link is correct. I'm looking for another source for .901, but in case I don't find it....
Click to expand...
Click to collapse
Motorola names their updates based on the filesystem they are REPLACING. So yes, this is correct. I did my homework before I wrote this up, promise
Thank you. I appreciate that. Seemed odd, but was thinking that exact thing. Running a backup with Bootstrap first, then will install this and move on to test out some ROM's.
Has anyone made progress with unlocking the bootloader? I just got the Bionic a few weeks ago. Sure isn't like the Xoom when it comes to customization.
I just wanted to thank you for the excellent guide. I'm now running the ROM w/ the HON3YSCR3AM mod. It's really cool. Apparently there's been some issues between the dev's who made some of this though.
I really hate that there is so little out there for the Bionic. Hoping the bootloader can be unlocked so we can see some real developments come about. I like Moto phone's, but will avoid anything with a locked bootloader in the future.
I followed the steps verbatim. I could have sworn that last night I was on 901 and now it shows me on. 893. Should I run the update again or what should I do? Eclipse is running.
I also am getting the default tether or mobile hotspot notification when I run wifi tether... Is there a fix for this?
I also usually run the application Klink by faveset and since the root it will not recognize my phone when I hook up the usb.
Any ideas.
Sent from my DROID BIONIC using XDA App
thereisone said:
I followed the steps verbatim. I could have sworn that last night I was on 901 and now it shows me on. 893. Should I run the update again or what should I do? Eclipse is running.
I also am getting the default tether or mobile hotspot notification when I run wifi tether... Is there a fix for this?
I also usually run the application Klink by faveset and since the root it will not recognize my phone when I hook up the usb.
Any ideas.
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Just explained in the several post above you but since you missed it. You are on 901 but for some reason when you flash a 901 compatible rom it'll say 893 in phone info. But if you had just did the update and boot up your phone before flashing a rom it would've verified you are actually on 901. Weird I know. I did this this morning cause I was worried too that I wasn't on 901.
Perfect thanks!
Sent from my DROID BIONIC using XDA App
Thanks pfak for finding http://sbf.droid-developers.org/umts_solana/list.php which has a verified legit Bell 2.3.6 sbf available for download.
The OP is here In This Post. Remember to hit the "Thanks" button for him.
Mirrored here http://www.multiupload.nl/D4SZTM40Y9
pfak said:
Bell SBF available at the following URL:
http://sbf.droid-developers.org/umts_solana/list.php
Click to expand...
Click to collapse
Willis111 said:
Thanks pfak for finding http://sbf.droid-developers.org/umts_solana/list.php which has a verified legit Bell 2.3.6 sbf available for download.
The OP is here In This Post. Remember to hit the "Thanks" button for him.
Click to expand...
Click to collapse
That sites has had it awhile but the link isn't easy to find. Can you maybe get this stickied?
Sent from my GT-P5113 using xda premium
Endoroid said:
That sites has had it awhile but the link isn't easy to find. Can you maybe get this stickied?
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Got it's own thread now, no need. I'll add mirrors for the actual file in a bit.
Edit: Mirrors Added, OP Updated. If anyone is having trouble with them and in need of the file shoot me a private message and I'll see if I can shoot you another link but there were at least 8 mirrors on multiupload once it finished propagating.
anyone tried flashing this to xt862? would be nice to have 2.3.6, but wondering whether i'd be stuck on it, unable to get back to 5.7.906.
Q9Nap said:
anyone tried flashing this to xt862? would be nice to have 2.3.6, but wondering whether i'd be stuck on it, unable to get back to 5.7.906.
Click to expand...
Click to collapse
Why would it be nice to have 2.3.6??
DoubleYouPee said:
Why would it be nice to have 2.3.6??
Click to expand...
Click to collapse
just because it's newer than 2.3.4. just compared the 906 cdt with this one; 906 is 04, this one is 02, so it won't even flash. oh well, 2.3.4 is still pretty nice and will have fully functional kexec soon
Q9Nap said:
just because it's newer than 2.3.4. just compared the 906 cdt with this one; 906 is 04, this one is 02, so it won't even flash. oh well, 2.3.4 is still pretty nice and will have fully functional kexec soon
Click to expand...
Click to collapse
I agree, higher numbers = win. I would just copy libmoto_ril.so, my apns-conf.xml and build.prop from my original rom, boot and see what happens and then if I didn't have data/phone I would swap back my original files, wipe data/cache and boot and see what happened, hopefully you would have a fully working bell 2.3.6 on your vzw phone. Let us know.
Thanks for the tip, but if it's not as easy as flashing fxz and radio, not gonna mess around with it.
Q9Nap said:
Thanks for the tip, but if it's not as easy as flashing fxz and radio, not gonna mess around with it.
Click to expand...
Click to collapse
yeah,you might have to do more than click a button... welcome to *nix/android
Willis111 said:
yeah,you might have to do more than click a button... welcome to *nix/android
Click to expand...
Click to collapse
yeah, i might brick my device beyond repair. no thanks. with fully fuctional kexec so close, no point in risking it.
Q9Nap said:
yeah, i might brick my device beyond repair. no thanks. with fully fuctional kexec so close, no point in risking it.
Click to expand...
Click to collapse
i dont see how you will brick your device beyond repair... we've been switching these libs since the beginning with no negative effects and if something does go wrong(the only thing that could possibly happen is a temporary bootloop, until you reflash the sbf) you just use rsd and reflash the bell sbf to have a fully working phone again. If you need more help, need to know which libs, where to put the or permissions etc, anyone can help you, feel free to ask if you decide top give it a try though I think I already posted instructions in a few other threads. I'll look around and update the OP if I find them
tried your bell 2.3.6 rom with libmoto_ril.so and build.prop from 906; persistent "com.motorola.phone has stopped working" error.
This is just that... A Verizon Stock Rooted ROM based on Build VS98011A (OTA Build)!
A stock rooted ROM
Pre-rooted
Busybox
zipaligned
Odex. De-Odex later!
Must be on latest OTA!
Includes boot.img that is pre-lokied.
You dont not need to worry about loki or OTA's.
Thanks
Jparasita and mbroseAI for helping test it, djrbliss, dees_troy, chainfire, Anonymous Donator!
MOD EDIT: Link removed as domain has expired. Thread closed until new links can be installed
Please Hit Thanks!
Its just as easy as hitting download!
[/CENTER][/SIZE][/I][/B]
Sharing Policy
The spirit of Open Source is to share your knowledge and files with the rest of the world so they can improve on what you do when possible. This is also my philosophy and I would never compromise that!
You are free to use this ROM or any part of this ROM any way you like as long as you give proper credits!
Do not use my work if you cannot give proper credits!
Consider this your permission! Please do not PM me asking if its OK to build off this ROM. Permission granted!
However this does not include my CleanROM series of ROMS. Please do not use those without contacting me first!
This ROM is not a CleanROM. Its a stock rooted and all yours!
Hit Thanks!
General Info
It takes a LONG TIME to flash this ROM. Accept it. ITS HUGE! Biggest stock ROM I have ever seen!
Wiping in recovery can take near 3 to 5 minutes... Let it go. Dont stop it!
You Sir are my hero. Nuff said.
Sent from my VS980 4G using Tapatalk 4
Thanks for all your hard work on this!
just wondering, what is the difference between flashing this, and rooting after the OTA update? i assume you bypass any pushed OTA's and thats all
nice, scott! thanks for getting to work on the verizon version
Viper76269 said:
just wondering, what is the difference between flashing this, and rooting after the OTA update? i assume you bypass any pushed OTA's and thats all
Click to expand...
Click to collapse
This may not be for you...
This ROM is for someone...
Who wants to tinker and build there own personal ROM from the stock base.
Another developer that may not have the ability to get a stock base (Like me, I only have the AT&T phone)
When you hose your phone trying to "modify" things because you "read it on the internet" somewhere you can then use this ROM to get your anus out of trouble.
You flash someone else ROM and realize its not what you were expecting, you didn't make nandroid back up, and your rebooting every time you try to make a phone call. This ROM would come in real handy
You see where I am going with this?
tombepa said:
You Sir are my hero. Nuff said.
Sent from my VS980 4G using Tapatalk 4
Click to expand...
Click to collapse
inkdrink said:
Thanks for all your hard work on this!
Click to expand...
Click to collapse
jayochs said:
nice, scott! thanks for getting to work on the verizon version
Click to expand...
Click to collapse
Click to expand...
Click to collapse
You are all welcome!
Glad I could help get it started off for Verizon!
scrosler said:
You are all welcome!
Glad I could help get it started off for Verizon!
Click to expand...
Click to collapse
haha i always downloaded cleanrom, or your stock rooted roms, on every phone i had that you dev'ed for..which was every phone i had lol..and they're all under each phones specific folder on my hard drive as my just-in-case i mess something up and need a fresh clean flash back to stock. it's helped numerous times lol so i've got this bad boy downloading right now..
2 gigs, that's crazy. i can't believe the roms are bigger than samsungs!
scrosler said:
This may not be for you...
This ROM is for someone...
Who wants to tinker and build there own personal ROM from the stock base.
Another developer that may not have the ability to get a stock base (Like me, I only have the AT&T phone)
When you hose your phone trying to "modify" things because you "read it on the internet" somewhere you can then use this ROM to get your anus out of trouble.
You flash someone else ROM and realize its not what you were expecting, you didn't make nandroid back up, and your rebooting every time you try to make a phone call. This ROM would come in real handy
You see where I am going with this?
Click to expand...
Click to collapse
gotcha. just making sure. wouldn't be bad to have it on the computer just in case. i was just curious. i'm personally waiting for a deodexed AOSP ROM, but i can keep this in case i screw anything up. thanks for the info!
jayochs said:
haha i always downloaded cleanrom, or your stock rooted roms, on every phone i had that you dev'ed for..which was every phone i had lol..and they're all under each phones specific folder on my hard drive as my just-in-case i mess something up and need a fresh clean flash back to stock. it's helped numerous times lol so i've got this bad boy downloading right now..
2 gigs, that's crazy. i can't believe the roms are bigger than samsungs!
Click to expand...
Click to collapse
Dude, tell me about it!
Do you know how long it takes to upload this isht?
I had to TeamView into jparista's PC, dump his phone, build the ROM, then upload it all using his internet connection because he has twice the upload speed I did.
I would still be uploading now!
you say must be on latest OTA, what happens if we flash this on non OTA?
Scott,
In the OP you say we need to be on the latest OTA?
I had flashed TWRP and have not been able to get the OTA.
I was surprised when I read we needed to be on the latest OTA to flash your ROM.
I have been holding off getting the OTA because I figured I would just flash a ROM to get the on the latest OTA is there a reason we need to be on it to flash your ROM?
Do you happen to have a Stock Recovery IMG and I get in order to get the OTA if I am going to need the OTA I will have to get it through stock recovery
neckbonest said:
you say must be on latest OTA, what happens if we flash this on non OTA?
Click to expand...
Click to collapse
I would like to know this as well.
Walter21026 said:
I would like to know this as well.
Click to expand...
Click to collapse
Because its built from the OTA and I didn't include a boot image. I don't have the phone so I didn't want to risk bricking someone else's trying to flash a boot image.
In all reality it will prolly be 100% fine on the non OTA but I cannot say for sure... Havent tried it.
So nandroid, flash and report results and all questions will be answered.
scrosler said:
Because its built from the OTA and I didnt include a but image.
In all reality it will prolly be 100% fine on the non OTA but I cannot say for sure...
Click to expand...
Click to collapse
looks like im going to be your beta tester on this. will report back after flashing
scrosler said:
Because its built from the OTA and I didn't include a boot image. I don't have the phone so I didn't want to risk bricking someone else's trying to flash a boot image.
In all reality it will prolly be 100% fine on the non OTA but I cannot say for sure... Havent tried it.
So nandroid, flash and report results and all questions will be answered.
Click to expand...
Click to collapse
Thanks for chiming in on this Scott, however I won't test this till someone else has. Already went through hell yesterday with TWRP loops
neckbonest said:
looks like im going to be your beta tester on this. will report back after flashing
Click to expand...
Click to collapse
Sounds good!
Let us know!
Good luck!
neckbonest said:
looks like im going to be your beta tester on this. will report back after flashing
Click to expand...
Click to collapse
Let us know how it goes. Thanks
Sent from my VS980 4G using Tapatalk 2