I am taking no credit in the release of the OTA files these were from lightningdude and credit goes to him for his efforts to bring these files out. Files size is around 43mb, but I am guessing that it is compressed and when it flashes it uncompresses to 63mb.
Link to original post from lightningdude,
http://forum.xda-developers.com/showthread.php?t=1621431&page=35
DB link from lightningdude
http://dl.dropbox.com/u/21955004/fota.zip
What we know so far it looks like flashing the OTA removes all possibility for root and early signs suggest that the methods for unlocking our bootloaders has been patched. So anyone who OTA's is not able to root and or unlock your BL.
I dont know much about developement of these files and am merely bringing them out to the masses in hopes of some good stuff to come from it, and again dont thank me, thank lightningdude.
DON'T THANK ME, Hit THANKS for lightningdude
Dang, j-greg, I didn't think it needed such bold font.
On-point: Is there any way to actually open this thing? I mean, there's got to be, if our phones update from it, right? There must be a way!
lightningdude said:
Dang, j-greg, I didn't think it needed such bold font.
On-point: Is there any way to actually open this thing? I mean, there's got to be, if our phones update from it, right? There must be a way!
Click to expand...
Click to collapse
I am messing with the files now trying to see if it can uncompressed if it is. And the font is so big because someone already thanked me for the post, and I dont think its right I get the thanks as you were the one who brought them out... I'm just a messenger. So big font to get peoples attention to thank you not me
I think these are compressed with some sort of compression method, maybe proprietary.
I'm guessing this patches the bootloader.
If so, time we overthrow Verizon. With a lawsuit.
KeiranFTW said:
I think these are compressed with some sort of compression method, maybe proprietary.
I'm guessing this patches the bootloader.
If so, time we overthrow Verizon. With a lawsuit.
Click to expand...
Click to collapse
My Mom was just saying today how she wants to sue Verizon in a class action for raising fees and what not. Maybe we should all get together and start that badn wagon. Haha.
KeiranFTW said:
I think these are compressed with some sort of compression method, maybe proprietary.
I'm guessing this patches the bootloader.
If so, time we overthrow Verizon. With a lawsuit.
Click to expand...
Click to collapse
I dislike VZjust as much as the next guy, but VZ feels that if you are a subsidized phone with a plan then the phone is not yours until the contract is up. For me i bought my phone off ebay to replace the total crap that is Motorola Droid 2 Global (loved the keyboard, hated the Motorblur and locked BL)
But I agree, VZ is raping everyone who has a wirelss plan with them, but no news here all Carriers do that.
My phone was free so they have no right to say what we can and can't do with our phones
Sent from my R800x using XDA
droidjunkie said:
My phone was free so they have no right to say what we can and can't do with our phones
Sent from my R800x using XDA
Click to expand...
Click to collapse
Free with a 2 year contract or free from someone you knew? If its free from a contract of 2 years to them they own the device for the length of the contract. I am not trying to support VZ, just saying that I have seen attempts (not firsthand) of people trying to sue VZ or other carriers for the same thing and they are always squashed
jgregoryj1 said:
I am taking no credit in the release of the OTA files these were from lightningdude and credit goes to him for his efforts to bring these files out. Files size is around 43mb, but I am guessing that it is compressed and when it flashes it uncompresses to 63mb.
Link to original post from lightningdude,
http://forum.xda-developers.com/showthread.php?t=1621431&page=35
DB link from lightningdude
http://dl.dropbox.com/u/21955004/fota.zip
What we know so far it looks like flashing the OTA removes all possibility for root and early signs suggest that the methods for unlocking our bootloaders has been patched. So anyone who OTA's is not able to root and or unlock your BL.
I dont know much about developement of these files and am merely bringing them out to the masses in hopes of some good stuff to come from it, and again dont thank me, thank lightningdude.
DON'T THANK ME, Hit THANKS for lightningdude
Click to expand...
Click to collapse
Hey, maybe it's because my BL was unlocked with the testpoint method, but I still have full root. I returned to stock with the .88 ftf file and then rooted it. I ran tha OTA Rootkeeper also. Once the FOTA was finished, I checked and I still have root without even touching the OTA Rootkeeper program. I ran Root Checker, and it verified I have full root access as well.
netizenmt said:
Hey, maybe it's because my BL was unlocked with the testpoint method, but I still have full root. I returned to stock with the .88 ftf file and then rooted it. I ran tha OTA Rootkeeper also. Once the FOTA was finished, I checked and I still have root without even touching the OTA Rootkeeper program. I ran Root Checker, and it verified I have full root access as well.
Click to expand...
Click to collapse
Can you PM me a Nandroid backup of this?
Did a baseband update come with this?
Leraeniesh said:
Can you PM me a Nandroid backup of this?
Click to expand...
Click to collapse
oohh, that would be awesome...... net.... got lucky. But in a good way.
netizenmt said:
Hey, maybe it's because my BL was unlocked with the testpoint method, but I still have full root. I returned to stock with the .88 ftf file and then rooted it. I ran tha OTA Rootkeeper also. Once the FOTA was finished, I checked and I still have root without even touching the OTA Rootkeeper program. I ran Root Checker, and it verified I have full root access as well.
Click to expand...
Click to collapse
I'm also rooted on 2.3.4 but with locked bootloader. Same method of flashing as you minus the ota rootkeeper.
Sent from my R800x using xda premium
kelvenha55 said:
I'm also rooted on 2.3.4 but with locked bootloader. Same method of flashing as you minus the ota rootkeeper.
Sent from my R800x using xda premium
Click to expand...
Click to collapse
Any chance you can make a nandroid backup? And if so post a download link for it here so Devs can browse its files?
You can try and fastboot recoveryplay.img and do a nandroid, dont need an unlocked BL for that.....
jgregoryj1 said:
Any chance you can make a nandroid backup? And if so post a download link for it here so Devs can browse its files?
You can try and fastboot recoveryplay.img and do a nandroid, dont need an unlocked BL for that.....
Click to expand...
Click to collapse
Seriouslly?!?
I thought you needed to be unlocked to hotboot recovery.
Leraeniesh said:
Seriouslly?!?
I thought you needed to be unlocked to hotboot recovery.
Click to expand...
Click to collapse
I might be wrong, been on an unlocked BL since last Aug so maybe my memory is boinked but I thought anyone can do a recoveryplay.img boot and do a nandroid that way? If I am wrong someone please correct me
jgregoryj1 said:
I might be wrong, been on an unlocked BL since last Aug so maybe my memory is boinked but I thought anyone can do a recoveryplay.img boot and do a nandroid that way? If I am wrong someone please correct me
Click to expand...
Click to collapse
Ill re-lock and try it using both Keiran's recovery and FXP's recovery.
Lets hope for luck
Edit: Dident work. Just as expected
jgregoryj1 said:
I might be wrong, been on an unlocked BL since last Aug so maybe my memory is boinked but I thought anyone can do a recoveryplay.img boot and do a nandroid that way? If I am wrong someone please correct me
Click to expand...
Click to collapse
Don't think you can hotboot without unlocked boot. But if has kept root he can install the recovery installer app or the manual way to install it (thread in this section of the forum).
Leraeniesh said:
Ill re-lock and try it using both Keiran's recovery and FXP's recovery.
Lets hope for luck
Click to expand...
Click to collapse
Just a reminder, now that I am thinking on it I am not so sure it will work.... not 100% sure, so you might relcok and find you cannot unlock.....
poo-tang said:
Don't think you can hotboot without unlocked boot. But if has kept root he can install the recovery installer app or the manual way to install it (thread in this section of the forum).
Click to expand...
Click to collapse
Oh yeah that right! We have the custom recovery app from google play store.... sweet, that will help..
https://play.google.com/store/apps/details?id=com.pvy.CWMinstaler&hl=en
Related
All credit for this goes to Chainfire and The Android Exploit Crew
Apk has been updated. Previous steps to delete tmp folder no longer needed.
Updated instructions and apk you will find here
http://forum.xda-developers.com/showpost.php?p=13086954&postcount=1
How long does it take? mine was stuck at the rooting device popup for more than 10 minutes......
edit: solved. Deleted the tmp folder (rmdir /data/local/tmp) and its contents and rebooted and superuser is there in the program list. heh
Confirming that this Root works on Xperia Play........
Confirming that the root worked in Xperia Play with locked bootloader.
I just followed the steps here:
http://forum.xda-developers.com/showthread.php?t=1044765
No extra steps done.
Root gained and works with no problems.
Thanks
This works
Used Root Uninstaller to get rid of apps I dont want.
v1.1 works like a charm^^
Could this brick my phone? I really want to try it, but I'm scared of what will happen if something goes wrong. Please help?
i am not sure but rooting a droid device never broke a device not or never heard about that so i think not
McGinty13 said:
Could this brick my phone? I really want to try it, but I'm scared of what will happen if something goes wrong. Please help?
Click to expand...
Click to collapse
No. You only flash system partition.
Sent from my R800i using XDA Premium App
So no chance of anything going wrong? If that's true I will be doing it immediately
Sent from my Xperia Play using XDA App
McGinty13 said:
So no chance of anything going wrong? If that's true I will be doing it immediately
Sent from my Xperia Play using XDA App
Click to expand...
Click to collapse
the only way to brick is if you abused Titianum backup and removed important stock apps. To know what is safe check here:
http://forum.xda-developers.com/showthread.php?t=1046699
even if you did brick it this way, it should be fairly easy to recover.
First there was play, then there was root
Worked like a charm, took about 10 min. though
Regards Dousan...
That's weird, when I ran Gingerbreak it literally took 30 seconds, then booted in the usual time.
V1.2 worked like a charm
Sent from my R800a using XDA App
Have any of you guys done a OTA after rooting your device with gingerbreak? If yes how did it go? I have an update waiting, but I'm a bit worried it will 'brick' my play and I don't want go through all that flashing work for an update
Regards Dousan...
As mentioned in other thread please un sticky the "Boot Loader Unlock root method" and make this as sticky.
As many users are unlocking bootloader just for the sake of root
Saw this, wonder if it's included in a new OTA update:
http://mobiputing.com/2011/05/google-security-update-patches-gingerbreak-root-exploit/
jassired said:
As mentioned in other thread please un sticky the "Boot Loader Unlock root method" and make this as sticky.
As many users are unlocking bootloader just for the sake of root
Click to expand...
Click to collapse
Yep your right about that I just did and now trackid dont work no more oh well still greatful for all the work that went into getting root access.
Hey guys
I'm a bit worried, I have gingerblur on the phone now, and apparently OTAing from it can be bad juju
I read the fastboot way of doing it, but just want to make sure I got this right so I dont mess it up
1. DL fastboot
2. download all the images from the link provided on the thread
**here is where I need to make sure I got this right***
3. I have to put all the images in the same folder as the fastboot.exe I guess
4. use the commands given on the link
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
5. I wipe the data and reboot
moto-fastboot -w
moto-fastboot reboot
6. should be gtg
now my questions are
is it going to be rooted when I do this, or will I have to reroot the phone (is it posisble to root the 2.3.4?)
and can I do this coming from gingerblur? I don't wanna mess anything up
and lastly, what about all the other img files? webtop, radio etc...
thanks!
ps. sorry I'm in a rush, supposed to goto dinner and then see captain america, so I figured I put this up real quick b4 i leave, gf is waiting at the door! lol
razorseal said:
Hey guys
I'm a bit worried, I have gingerblur on the phone now, and apparently OTAing from it can be bad juju
I read the fastboot way of doing it, but just want to make sure I got this right so I dont mess it up
1. DL fastboot
2. download all the images from the link provided on the thread
**here is where I need to make sure I got this right***
3. I have to put all the images in the same folder as the fastboot.exe I guess
4. use the commands given on the link
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
5. I wipe the data and reboot
moto-fastboot -w
moto-fastboot reboot
6. should be gtg
now my questions are
is it going to be rooted when I do this, or will I have to reroot the phone (is it posisble to root the 2.3.4?)
and can I do this coming from gingerblur? I don't wanna mess anything up
and lastly, what about all the other img files? webtop, radio etc...
thanks!
ps. sorry I'm in a rush, supposed to goto dinner and then see captain america, so I figured I put this up real quick b4 i leave, gf is waiting at the door! lol
Click to expand...
Click to collapse
Don't make things so complicating, just flash this if you're on 1.8.3.
http://forum.xda-developers.com/showthread.php?t=1182526
Are you unlocked??
Sent from my MB860 using XDA App
Paschalis said:
Are you unlocked??
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
As long as he's on 1.8.3. that shouldn't matter.
Yes, but if he's locked, I think he won't be able too use fastboot..
Edit: if the images he want to flash using fastboot, are for unlocked device, he will end bricked.
Sent from my MB860 using XDA App
Paschalis said:
Yes, but if he's locked, I think he won't be able too use fastboot..
Edit: if the images he want to flash using fastboot, are for unlocked device, he will end bricked.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Refer to the link I sent him...
Unlocked as in rooted?
I'm running gingerblur, so yes, I'm rooted so i have access to cwm...
Can I just flash that? And yes I'm on 1.8.3
Flashing via sbf?
Sent from my MB860 using XDA App
mpalatsi said:
Don't make things so complicating, just flash this if you're on 1.8.3.
http://forum.xda-developers.com/showthread.php?t=1182526
Click to expand...
Click to collapse
So what are allll these posts about phones hard bricking? Why isn't everyone just doing this?
I realized unlocked as in bootloader unlocked... That part I'm not sure, I did the OTA 1.8.3 update, so I assume not...
I doubt I'll be downgrading though, so is it safe to just use that link? I'd hate to hard brick
Sent from my MB860 using XDA App
razorseal said:
So what are allll these posts about phones hard bricking? Why isn't everyone just doing this?
I realized unlocked as in bootloader unlocked... That part I'm not sure, I did the OTA 1.8.3 update, so I assume not...
I doubt I'll be downgrading though, so is it safe to just use that link? I'd hate to hard brick
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
@razorseal,
You will not hard-brick if you use the link posted by @mpalatsi.
It appears to be the official SBF version of the OTA. Edit: actually, that one is modified with the unlocked bootloader.
However, you will not be able to go back to any other SBF after you flash this thing. It modifies the bootloader in a way that will cause damage if you try to revert. This is ok if you have no plans to revert, but one never knows when they need to take a step back.
So, you can commit to this SBF or you can do the sensible thing: unlock your bootloader (if you haven't already done so) and follow with your procedure (or use the Fruit Cakes which are equivalent to the fastboot flashing, but using the recovery).
I would recommend staying away from SBF's in general, especially from the ones that cause irreversible changes to the bootloader.
Edit: If you need help unlocking your bootloader, look up the Pudding thread in the Dev section. Everything is straightforward and has been done by many users successfully.
Edit2: If it makes you feel any better, I personally used the method you described in the OP to upgrade. Wasn't that hard or "complicated".
feisty_noodle said:
@razorseal,
You will not hard-brick if you use the link posted by @mpalatsi.
It appears to be the official SBF version of the OTA.
However, you will not be able to go back to any other SBF after you flash this thing. It modifies the bootloader in a way that will cause damage if you try to revert. This is ok if you have no plans to revert, but one never knows when they need to take a step back.
So, you can commit to this SBF or you can do the sensible thing: unlock your bootloader (if you haven't already done so) and follow with your procedure (or use the Fruit Cakes which are equivalent to the fastboot flashing, but using the recovery).
I would recommend staying away from SBF's in general, especially from the ones that cause irreversible changes to the bootloader.
Edit: If you need help unlocking your bootloader, look up the Pudding thread in the Dev section. Everything is straightforward and has been done by many users successfully.
Click to expand...
Click to collapse
ok, got it...
I understand no downgrading, but how about upgrading in the future?
so if I want to do it the 'safe' way, how do I do that? the way I mentioned it? (the thread via fastboot)
How can I check if i'm unlocked my bootloader or not?
I'm in the same boat. I'm on ginger blur and 1.83 and I just want to update, unlock and root.I would like to revert back if need be.
Sent from my MB860 using XDA App
razorseal said:
ok, got it...
I understand no downgrading, but how about upgrading in the future?
so if I want to do it the 'safe' way, how do I do that? the way I mentioned it? (the thread via fastboot)
How can I check if i'm unlocked my bootloader or not?
Click to expand...
Click to collapse
This link was exactly what I used.
As far as upgrading in the future, you can use the resources found here, on XDA. People will be dissecting new updates to remove the nasty bits (bootloaders and such).
If you decide that you want to play with custom ROMs, you can do that, too.
You will NOT be able to use OTA's unless you backtrack to a fully stock ROM via official OTA's or SBF's. This can be done, but will require some careful work on your part.
For the bootloader unlocking--go read the Pudding thread here. It is very a straightforward procedure.
Edit: if your first Motorola boot screen has the word "Unlocked" in the upper left corner, then you are unlocked. If not, then ...
Don't you remember if you unlocked your bootloader?
There is a method to check that I think in the pudding thread.
With unlocked bootloader, when moto makes an OTA, the devs here take it, mod it, made it a flashable zip, and you can upgrade your phone.
For downgrading.
Personally I m on gingerblur 4.5. With unlocked bootloader, and tenfars port of cwm recovery installed.
I currently have CWM nandroid backup.
I can install the 2.3.4 cherryblur e.g( with cwm installation also), and whenever I want I can restore this backup..
I can also have 2 backups of 2.2 and 2.3 and switch between the 2 backups.
Its very good advice to stay away from sbf's.
Safer seems the cwm zip files.. Of known devs..
Sent from my MB860 using XDA App
Paschalis said:
Its very good advice to stay away from sbf's.
Safer seems the cwm zip files.. Of known devs..
Click to expand...
Click to collapse
well then I should stay from that link that was provided here considering it's an sbf file...
Paschalis said:
Don't you remember if you unlocked your bootloader?
There is a method to check that I think in the pudding thread.
With unlocked bootloader, when moto makes an OTA, the devs here take it, mod it, made it a flashable zip, and you can upgrade your phone.
For downgrading.
Personally I m on gingerblur 4.5. With unlocked bootloader, and tenfars port of cwm recovery installed.
I currently have CWM nandroid backup.
I can install the 2.3.4 cherryblur e.g( with cwm installation also), and whenever I want I can restore this backup..
I can also have 2 backups of 2.2 and 2.3 and switch between the 2 backups.
Its very good advice to stay away from sbf's.
Safer seems the cwm zip files.. Of known devs..
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I agree with almost everything.
The 'almost' part is that using stock system.img can be a good idea. Whenever new firmware updates come out, I am always curious to see what the OEM envisioned to be the 'normal' look for their device.
Flashing these is perfectly safe because you are only touching the system partition. As long as you have functional fastboot (unlocked bootloader) or recovery, you will have two fallback positions in case something goes wrong (like a bad flash).
Trusting OEM's to give you a good product has historically been a losing proposition. They always take waaay too long. And they make stupid mistakes (like the ****ed up battery monitor in the new Gingerbread ROM, the 4.5.91). And to fix those mistakes they take their sweet time again.
Anyway, @razorseal:
After you upgrade, you will likely see poor battery performance. The way to fix this is to flash the new radio 01.77.30P found here; this will be done through recovery. I am not sure if Ken's thread here is the same thing. The image files look different.
Also, to fix the aforementioned screw-up by Motorola, follow the instructions here.
feisty_noodle said:
I agree with almost everything.
The 'almost' part is that using stock system.img can be a good idea. Whenever new firmware updates come out, I am always curious to see what the OEM envisioned to be the 'normal' look for their device.
Flashing these is perfectly safe because you are only touching the system partition. As long as you have functional fastboot (unlocked bootloader) or recovery, you will have two fallback positions in case something goes wrong (like a bad flash).
Trusting OEM's to give you a good product has historically been a losing proposition. They always take waaay too long. And they make stupid mistakes (like the ****ed up battery monitor in the new Gingerbread ROM, the 4.5.91). And to fix those mistakes they take their sweet time again.
Anyway, @razorseal:
After you upgrade, you will likely see poor battery performance. The way to fix this is to flash the new radio 01.77.30P found here; this will be done through recovery. I am not sure if Ken's thread here is the same thing. The image files look different.
Also, to fix the aforementioned screw-up by Motorola, follow the instructions here.
Click to expand...
Click to collapse
Thanks bud
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
I looked at that, and that says it will unlock it... isn't the link provided here already unlocked?
razorseal said:
Thanks bud
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
I looked at that, and that says it will unlock it... isn't the link provided here already unlocked?
Click to expand...
Click to collapse
Yes, zomgunlock-lite.sbf is the contents of "pudding".
That is your bootloader that has the unlock code. Just follow Ken's instructions from the page you linked to.
Also, here is the link for an easy root method after you are done.
If you are still scared, watch the videos of the process here. I didn't have time to look too carefully, but it clearly shows what the bootloader screen should look like when you've successfully unlocked.
Good luck, I have to sleep now.
ah ****... not working
I have something that says 'failed to boot 4'
starting RSD mode
uh oh
razorseal said:
ah ****... not working
I have something that says 'failed to boot 4'
starting RSD mode
uh oh
Click to expand...
Click to collapse
You are not in a bricking situation! Take a deep breath.
I have not seen this, but others have ...
http://forum.xda-developers.com/showthread.php?t=1062727
Do some homework.
I am really going now.
I just reflashed.... I guess something got corrupted it works now
alright, off to unlocking, and doing the radio tweak along with battery % and att logo removal
125mb 45.4.12.en.us 2.3.5
For those that dont care about unlock and want the update you can get the app here http://forum.xda-developers.com/showthread.php?t=1226664
server qa1 is near the top of the list. As a reminder this is one way to get leaks as they are being tested so if one person scans each day at different times the chances we might pull a new ota are good.
Details?
2.3.5
mind posting the zip
^ this
Sent from my mopho
wheres the location shabby i looked in cache and it wasnt there before installing, install cheesecake and query qa1 server and it should pull for you.
beware kills unlock just tested and get
SVF :106:1:2
sec_exception: b655, eddc, eb
So much time for developing this... lol
We dont need GB
we need ICS :|
better yet, how the **** do you change servers on this app. the scroll screen is one entry high, i get it to move like 2 spots up and thats all
shabbypenguin said:
better yet, how the **** do you change servers on this app. the scroll screen is one entry high, i get it to move like 2 spots up and thats all
Click to expand...
Click to collapse
yeah the scrolling is ****ty, just hold down and pull down you can scroll all the way down the screen. Just keep holding and scrolling until it moves....
ok i have ota root keeper installed and its got a backup of my root, so ill be doing dd dumps of this and hopefully joker or someone with some spare time can make it into a flashable cwm without locking the bootloader for everyone else
shabbypenguin said:
ok i have ota root keeper installed and its got a backup of my root, so ill be doing dd dumps of this and hopefully joker or someone with some spare time can make it into a flashable cwm without locking the bootloader for everyone else
Click to expand...
Click to collapse
Yeah i dont unlock much so it dont bug me really....cant go without 4g, root is still attainable via photon torpedo method. Unlock killed & downgrade not possible via sbf.
ah ok so that method still works for rooting? good to know
and id rather lock my photon and give me the feul to look into kexec so we can have a bootloader bypass than a bunch of people get theirs locked for 1080p video recording
also the zip is right in cache Blur_Version.45.3.6.MB855.Sprint.en.US.zip
shabbypenguin said:
ah ok so that method still works for rooting? good to know
and id rather lock my photon and give me the feul to look into kexec so we can have a bootloader bypass than a bunch of people get theirs locked for 1080p video recording
also the zip is right in cache Blur_Version.45.3.6.MB855.Sprint.en.US.zip
Click to expand...
Click to collapse
weird i looked and wasn't there just recovery and lost&found, boot loader bypass would be nice
kexec is basically a way to load a kernel off the sdcard, well if we boot up normal and then booted a cm9 kernel off internal storage then in theory you could get cm9 going with a locked bootloader
problem is i know nothing of kexec and making it work for us, but its a pipe dream
shabbypenguin said:
kexec is basically a way to load a kernel off the sdcard, well if we boot up normal and then booted a cm9 kernel off internal storage then in theory you could get cm9 going with a locked bootloader
problem is i know nothing of kexec and making it work for us, but its a pipe dream
Click to expand...
Click to collapse
yeah, well gotta start somewhere. Just erks me that even after their unlocked boot loader promise they would still send out a ota locked down. Photon is best phone i have owned thus far but being so locked down will make me question buying another.
zip is uploading, i would highly recommend against flashing this
www.shabbypenguin.com/ACS/devices/Moto/Sprint/Photon-4G/Blur_Version.45.3.6.MB855.Sprint.en.US.zip
http://pastebin.com/GhLuvxd0
as you can see
ui_print("updating AP20 bootloader ...");
assert(package_extract_file("ap20bl.img", "/tmp/ap20bl.img"),
write_raw_image("/tmp/ap20bl.img","nvmotota"),
delete("/tmp/ap20bl.img"));
assert(ap20bl.set_bl_update(00300000));
assert(ap20bl.set_mb_update(00080000));
Click to expand...
Click to collapse
at the bottom is where your getting your new bootloader
shabbypenguin said:
zip is uploading, i would highly recommend against flashing this
www.shabbypenguin.com/ACS/devices/Moto/Sprint/Photon-4G/Blur_Version.45.3.6.MB855.Sprint.en.US.zip
http://pastebin.com/GhLuvxd0
as you can see
at the bottom is where your getting your new bootloader
Click to expand...
Click to collapse
125MB is that the correct file size? I'm gonna pull it and play with it a bit but wanted to make sure first.
Edit:
Pulled it and am going through it right now mainly looking at Webtop. Thanks for posting it.
www.shabbypenguin.com/ACS/devices/Moto/Sprint/Photon-4G/254/boot.img
there is teh kernel
www.shabbypenguin.com/ACS/devices/Moto/Sprint/Photon-4G/254/system.zip
zipped it to compress their padding, its double in size when you unpack it
Hey guys,
Do any of you know how I can place my rom, and push it as an OTA Update like Sprint. What files do I need to accomplish this? I have already looked at OTA update center and its great, I would just like to push them without my people having to root. I have a server set up, just don't know how to have everything point to the right place. I'm familiar with the boot_delta.bin and android_delta.bin files along with others needed for an OTA Update. Also, i know you have to edit things in the build.prop as well. I hope someone can point me in the right direction. Thanks
I want it too, I think it's a great idea.
You wan't to add it to your custom rom which is not even rooted? WHAT???
Sent from my GT-S7500 using xda premium
lokeshsaini94 said:
You wan't to add it to your custom rom which is not even rooted? WHAT???
Sent from my GT-S7500 using xda premium
Click to expand...
Click to collapse
My custom rom is rooted, but I am wanting people who get the device from a specific company to not have to go through the rooting process and just push my Rom OTA to their device using a server just like Sprint does. Hope this makes some sense, thanks
jd3107 said:
My custom rom is rooted, but I am wanting people who get the device from a specific company to not have to go through the rooting process and just push my Rom OTA to their device using a server just like Sprint does. Hope this makes some sense, thanks
Click to expand...
Click to collapse
Not possible....the way sprint or other carriers are able to do it is because they pass the security/verification checks...unless you can figure out an exploit/hack its not possible
Basically you would need to figure out how to first root the phone, and then get a custom recovery...there have been some apps in the past that can achieve root...but most phones have those patched by now...so it definitely is possible, just not probable
Sent from my SGH-I997 using Tapatalk 2
You can take a look at goo.im the users will still have to have a custom recovery to flash the ROM
Sent from my LG-P990
mg2195 said:
Not possible....the way sprint or other carriers are able to do it is because they pass the security/verification checks...unless you can figure out an exploit/hack its not possible
Basically you would need to figure out how to first root the phone, and then get a custom recovery...there have been some apps in the past that can achieve root...but most phones have those patched by now...so it definitely is possible, just not probable
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, by any chance do you think this will work?
http://www.igottadroid.com/ModMarke...746F6D20726F6D73207B44455653204F4E4C597D.html
C0D3N1N3R said:
You can take a look at goo.im the users will still have to have a custom recovery to flash the ROM
Sent from my LG-P990
Click to expand...
Click to collapse
Thanks, I already have a custom recovery I have made, I just wanted to try to push my custom roms with an OTA without having people need root or a recovery. Just like Sprint and Verizon. Thanks
jd3107 said:
Thanks, I already have a custom recovery I have made, I just wanted to try to push my custom roms with an OTA without having people need root or a recovery. Just like Sprint and Verizon. Thanks
Click to expand...
Click to collapse
You can't bro, get over it. THEY need too root, THEY need to flash it. Period.
lithid-cm said:
You can't bro, get over it. THEY need too root, THEY need to flash it. Period.
Click to expand...
Click to collapse
Thanks man, I appreciate your answer. I was hoping their was a way but I guess not.
jd3107 said:
Thanks man, I appreciate your answer. I was hoping their was a way but I guess not.
Click to expand...
Click to collapse
Well, with a custom recovery it IS possible without root.
What you also could do is make an app who's exploiting a bug in the Android system to gain root. Do this with the permission of your users. If you execute the exploit, you have a root prompt, you could fetch the device name, and download a suitable recovery for it. Let the user confirm this, and download it.
I recommend to wrap it in a nice UI, like this.
- Get root
- Fetch recovery (menu to choose device)
- Flash recovery
From there, you CAN execute your OTA updater app. Note this only works on devices where all partitions are writable with root. For example my phone's (i9300) recovery partition is writable with root.
Hope this helps,
CodeOMG
CodeOMG said:
Well, with a custom recovery it IS possible without root.
What you also could do is make an app who's exploiting a bug in the Android system to gain root. Do this with the permission of your users. If you execute the exploit, you have a root prompt, you could fetch the device name, and download a suitable recovery for it. Let the user confirm this, and download it.
I recommend to wrap it in a nice UI, like this.
- Get root
- Fetch recovery (menu to choose device)
- Flash recovery
From there, you CAN execute your OTA updater app. Note this only works on devices where all partitions are writable with root. For example my phone's (i9300) recovery partition is writable with root.
Hope this helps,
CodeOMG
Click to expand...
Click to collapse
Very cool, you come up with that idea all by yourself? Reguardless, there is user intervention required. Whether it be for the custom recovery, bootloader unlock, root. Nothing, when it comes to this comes that easy. ****, even the Nexus phones you need to reboot into the bootloader, no app from the device can do it all sorry.
I have a vzw max and i recently reverted everything back to stock and unrooted; or so i believed. The kernel still says 3.4.10 etc. and the phone has no signal nor can it find my location. It keeps rebooting every 30 secs or so and no matter what mode I put the device into, it isn't recognized by my PC. the bootloader is locked and I am S-Off. This all happened after I tried to flash CWM's HTC M7 recovery because the Max isn't listed and I couldn't figure out how to flash TWRP. Help please because this is getting crazy and I can't figure out what to do...
bump
nobody at all eh...
LocBox said:
nobody at all eh...
Click to expand...
Click to collapse
So if you boot to bootloader keeps rebooting there too?
Sent from my Nexus 7 using Tapatalk
dude i feel for you.
why did you put m7 cwm on there. clearly not for this device.
can you still get to bootloader? if you can flash the correct recovery! then find a backup someone has done and restore. or flash the correct boot.img
dude here's the correct recovery
http://forum.xda-developers.com/showthread.php?t=2498749
Well the only problem is my any pc won't even detect that it's connected when I plug it into it. So I can't use any fastboot or adb methods and even when I put the phone into fastboot mode it doesn't connect either. I'm able to put it into bootloader mode and it doesn't reset but still no connection; just charges. I've tried flashing through stock recovery manually and it aborts every attempt I'm assuming because my BL is locked..
No it doesn't
dottat said:
So if you boot to bootloader keeps rebooting there too?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
no it doesnt'
LocBox said:
no it doesnt'
Click to expand...
Click to collapse
Ok. I know how we can fix then. Let me pm you
Sent from my HTC6600LVW using Tapatalk
Thanks
Dottat has helped me and not a moment too soon, I was seconds from printing out the return label for HTC and sending it in for a refurb exchange. smbh. thanks man.:good:
dottat said:
Ok. I know how we can fix then. Let me pm you
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
hey mate, whats the secret sauce
Flashing the zip from bootloader ?
pradeepvizz said:
hey mate, whats the secret sauce
Flashing the zip from bootloader ?
Click to expand...
Click to collapse
I agree, it would be nice for that stuff to be posted on here so we can all see it. And maybe not have to ask for help ourselves.
JBS976 said:
I agree, it would be nice for that stuff to be posted on here so we can all see it. And maybe not have to ask for help ourselves.
Click to expand...
Click to collapse
haha, okay chill mate. i was kidding there.
i am guessing it was full flash of rom / kernel using the zip in the bootloader.
pradeepvizz said:
haha, okay chill mate. i was kidding there.
i am guessing it was full flash of rom / kernel using the zip in the bootloader.
Click to expand...
Click to collapse
That is correct, full flash from bootloader. 0P3PIMG.zip on root of sd. and boom with some pow.
JBS976 said:
I agree, it would be nice for that stuff to be posted on here so we can all see it. And maybe not have to ask for help ourselves.
Click to expand...
Click to collapse
I wasn't trying to hide anything. I typically will walk a user through using the encrypted RUU (my person preference as i know it's intact) to restore their phone as long as it can boot to bootloader. I take it offline because the mods didn't take kindly to the encrypted RUU being posted in the past. I don't have an answer as to why that was case so I just keep that part off the main threads. If its someone in need (like the OP) i have no problem helping one on one.
dottat said:
I wasn't trying to hide anything. I typically will walk a user through using the encrypted RUU (my person preference as i know it's intact) to restore their phone as long as it can boot to bootloader. I take it offline because the mods didn't take kindly to the encrypted RUU being posted in the past. I don't have an answer as to why that was case so I just keep that part off the main threads. If its someone in need (like the OP) i have no problem helping one on one.
Click to expand...
Click to collapse
It's cool, I didn't mean it to sound like anything was being hidden, I just like to read all this stuff and take it in for future reference as I don't want to bother you guys unless I just cannot figure it out on my own. Believe me i really appreciate all you guys do on here as this is an invaluable resource if people take the time to read through things. I was unaware that they didn't want the RUU's on here which really sucks because they are nice to have like I had them for the rezound and it came in real handy at times. Not having them for this device yet has been one of the reasons I have been hesitant to do much else than to S-OFF and root. At this point I guess I am waiting for the OTA Kit Kat update then I will probably dive in.
Bryon
JBS976 said:
It's cool, I didn't mean it to sound like anything was being hidden, I just like to read all this stuff and take it in for future reference as I don't want to bother you guys unless I just cannot figure it out on my own. Believe me i really appreciate all you guys do on here as this is an invaluable resource if people take the time to read through things. I was unaware that they didn't want the RUU's on here which really sucks because they are nice to have like I had them for the rezound and it came in real handy at times. Not having them for this device yet has been one of the reasons I have been hesitant to do much else than to S-OFF and root. At this point I guess I am waiting for the OTA Kit Kat update then I will probably dive in.
Bryon
Click to expand...
Click to collapse
Check your pm shortly. S-off later today ?
Sent from my HTC6600LVW using Tapatalk