Related
i have version 1.8.3 with root and with unlocked bootloader if i want to upgrade 2.3.4, i need to flash a clean 1.8.3 and after that to unlocked again ?
or if i do that i will be in risk getting a hard brick??
liranm2 said:
i have version 1.8.3 with root and with unlocked bootloader if i want to upgrade 2.3.4, i need to flash a clean 1.8.3 and after that to unlocked again ?
or if i do that i will be in risk getting a hard brick??
Click to expand...
Click to collapse
When in doubt, use the fruit cakes! =D Mmmmmmm
But yeah, honestly, you don't need to re-lock or un-root. You can just use the Automated Upgrade found here. That will save all your data and stuff, and it'll upgrade you to Gingerbread! =D
BEFORE YOU DO ANYTHING THOUGH (I don't know how many times i emphasize this, but I guess it's worth emphasizing), BACK UP ALL YOUR DATA. In the event you lost all of it, we MIGHT be able to recover some, but expect to loose it all if you just screw my warning over. Oh, and if you want to root again, use the pre-install method. That works well for lots of people (use search bar above to find it =])
Happy upgrading!
BTW if you want unlocked bootloader again, it doesn't come with this Gingerbread build (god only knows why). Just use pudding and you'll be good to go =]
~jojojohnson7410~
jojojohnson7410 said:
When in doubt, use the fruit cakes! =D Mmmmmmm
But yeah, honestly, you don't need to re-lock or un-root. You can just use the Automated Upgrade found here. That will save all your data and stuff, and it'll upgrade you to Gingerbread! =D
BEFORE YOU DO ANYTHING THOUGH (I don't know how many times i emphasize this, but I guess it's worth emphasizing), BACK UP ALL YOUR DATA. In the event you lost all of it, we MIGHT be able to recover some, but expect to loose it all if you just screw my warning over. Oh, and if you want to root again, use the pre-install method. That works well for lots of people (use search bar above to find it =])
Happy upgrading!
BTW if you want unlocked bootloader again, it doesn't come with this Gingerbread build (god only knows why). Just use pudding and you'll be good to go =]
~jojojohnson7410~
Click to expand...
Click to collapse
The link in your post points to the official OTA.
It contains the new bootloader as a part of the payload.
This bootloader will make it impossible to go back to 1.8.3 SBF (or any other SBF) without the risk of hard brick.
For your safety, use Fruit Cakes or any of the ROMs floating around.
Stay away from official OTA or anything that does not have the new bootloader disarmed (or removed).
liranm2 said:
i have version 1.8.3 with root and with unlocked bootloader if i want to upgrade 2.3.4, i need to flash a clean 1.8.3 and after that to unlocked again ?
or if i do that i will be in risk getting a hard brick??
Click to expand...
Click to collapse
In general, you do not need to go back to anything to flash a new ROM.
Just back up your phone (through CWM) and flash a zip file with the ROM of your choice.
Most of the time, you will need to recreate your setup (download the apps and regenerate your preferred settings). To make your life much easier, I would highly recommend investing in Titanium Backup.
lol sorry forgot to mention the fruitcake part X_X made so many posts in the past hour or so, I tend to leave out information I've repeated over a lot of times. I honestly don't have a problem with the OTA (minus the fingerprint, but i think that's with everyone), so that is another viable method. So long as he stays away from SBF (which we technically should anyways) and sticks with eating his Fruitcake, I don't see what's the big deal =]
That's just my two cents on that matter. However, feisty_noodles is probably right about flashing ROMs, as they are usually well tested and don't blow the Odmfuse like the new bootloader does when you unlock with it. It's really your choice, but I preferred having an OTA (until my ROM-itis kicks back in >.>), so I just gave you the method I used.
Good luck!
~jojojohnson7410~
feisty_noodle said:
In general, you do not need to go back to anything to flash a new ROM.
Just back up your phone (through CWM) and flash a zip file with the ROM of your choice.
Most of the time, you will need to recreate your setup (download the apps and regenerate your preferred settings). To make your life much easier, I would highly recommend investing in Titanium Backup.
Click to expand...
Click to collapse
Oh, and yeah. These are important too =] Kenneth made a ROM from the Gingerbread, so you can probably use that (make sure it's not fastboot images though! A lot of people (soft?)bricked their phones that way. And Titatium ftw =D
~jojojohnson7410~
jojojohnson7410 said:
Oh, and yeah. These are important too =] Kenneth made a ROM from the Gingerbread, so you can probably use that (make sure it's not fastboot images though! A lot of people (soft?)bricked their phones that way. And Titatium ftw =D
~jojojohnson7410~
Click to expand...
Click to collapse
There is nothing wrong with fastboot images. I am running a stock from system.img (from Ken's archive) at the moment.
1.8.3 with unlocked bootloader you have 3 way to have official GB 2.3.4/4.5.91
1. Flash 1.83 "WITH" Pudding and then apply OTA by settings->about phone->system update
2. Flash 2.3.4/4.5.91 Official Motorola SBF, you can get this one by Motorola Software Updater or Development forum -> stickie -> SBF thread
3. Download 2.3.4/4.5.91 extract img's and moto-fastboot
Option 1 and 2 update the bootloader
Option 3 preserve old bootloader
liranm2 said:
i have version 1.8.3 with root and with unlocked bootloader if i want to upgrade 2.3.4, i need to flash a clean 1.8.3 and after that to unlocked again ?
or if i do that i will be in risk getting a hard brick??
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
thanks you all....
i will decide today what to do.
mramirezusa said:
1.8.3 with unlocked bootloader you have 3 way to have official GB 2.3.4/4.5.91
1. Flash 1.83 "WITH" Pudding and then apply OTA by settings->about phone->system update
2. Flash 2.3.4/4.5.91 Official Motorola SBF, you can get this one by Motorola Software Updater or Development forum -> stickie -> SBF thread
3. Download 2.3.4/4.5.91 extract img's and moto-fastboot
Option 1 and 2 update the bootloader
Option 3 preserve old bootloader
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Continuing on with the list--options that do not mess with the bootloader:
4) Flash the .img files from Ken found here plus the CWM-flashable radio
5) Fruit cakes!!!
Is it possible for anyone to create/point me to a downloadable stock ROM? I mean literally STOCK, as in, nothing changed. I think that might be the only way for me to get back to being able to receive OTA updates without fastbooting (which I have tried to no avail).
Thanks!
there you go http://forum.xda-developers.com/showthread.php?t=1416058
Yeah, see...fastboot doesn't work for me - already tried it a bunch of times. For some odd reason. I mean, does someone have a stock ROOTED ROM I could flash. As in, something with all apps preserved as if the device were not rooted. That way, I can take the OTA update (and break root, but at this point I just don't want to be trapped in OS 2.3.5 forever). Thanks (again)!
Are you able to access stock recovery?
Yes, I am. Will that help?
on my maxx, having the same issue as you, i factory restored, i guess that might have replaced/fix any corrupt files and i was able to fastboot. Unfortunately, i speak from personal experience and not knowledge of the operating system. good luck.
I did a factory data reset and it did not fix the problem, sadly. Looks like I'm in a hole with no ladder out lol. I can always hope that a stock rooted ROM is available so I can use my recently-recovered root to flash and then take the OTA over that, if possible.
http://www.droidrzr.com/index.php/topic/457-rom-totally-stock-rooted-748/page__pid__14816#entry14816
Link is dead; they're looking to fix it though I think. Thanks though! I'll give it a shot.
If you can take the update, this http://forum.xda-developers.com/showthread.php?t=1492708 can root the new 2.3.6
Doomlords method still can unroot if need be.
Sent from my DROID RAZR using xda premium
Thanks! I'll keep it in mind. Right now I'm looking for a way to be able to get the update though
Yeah I'm in the same boat. Need this link to work!!! Can someone please post another working link?
http://forum.eternityproject.eu/mot...f7/official-motorola-razr-roms-thread-t4.html
I hope this helps
I think we just need a stock ROM, not the OTA. We can't flash the OTA (even an older one) like a ROM, right?
Atlas.rouge said:
I think we just need a stock ROM, not the OTA. We can't flash the OTA (even an older one) like a ROM, right?
Click to expand...
Click to collapse
That is the stock rom. The second post includes 2 stock versions and 2 OTA. Just download the stock Rom. Atleast i think thats a flashable ROM
Theres this also
http://forum.xda-developers.com/showthread.php?t=1362956
Is the only option to flash these via adb and rsd lite?
Question: (rather than creating new thread)
what's the different between ROM and Fastboot files? Examples?
Coz i downloaded Brazil.en fastboot, use RSD Lite, and flashed my GSM Rogers RAZR. works great.
But i also have SafeStrap installed, and I can make backup (and restore) from it. Are those ROMs? Or just backup files?
I thought people flash their phones using mod ROMs using CWM/Safestrap too?
I know OTA is over-the-air, but u can also download and manually install "OTA" updates? so... are they OTA ROM then?
or just OTA "files". like backup files CWM made?
thx for explanations
MBL85 said:
Is the only option to flash these via adb and rsd lite?
Click to expand...
Click to collapse
That was the way I did it, Ive read about a few others like;
motofail
DroidRAZRUtility1.4LITE
vulnfactory.org/blog/2012/02/11/rooting-the-droid-4-a-failed-bounty-experiment/
But flashing with RSDlite was how I did it and it worked fine, just wish I had the original ROM with all the bloatware just in case....
Yeah, see for some reason fastboot doesn't like me, which is why I'm trying to get ahold of a complete stock ROM lol. I know that fastboot *works* all the time, but rather than go through the hassle I was just hoping someone had a spare total stock ROM floating around haha
I understand that this may have been asked, and I've been looking at similar threads, but I'm having a hard time finding a direct answer, so I apologize.
I have some experience rooting with an Atrix, but I just got this phone two days ago, this morning I used the 1-click method from rootwhiz to install the ICS leak. No problems having it run at all. I need to know, directly, did this install change my bootloader and change the binary count? I can't remember if I saw anytime of yellow triangle as people talk about. If it changed the bootloader what is there a safe method to return to the older bootloaders, and or do I even need to do so to root and install other roms?
I know that the Atrix had some problems in terms of returning to prior versions of things, and in my research I haven't found a direct answer to this question too.
Basically, did my bootloader change? Can I root using the heimdall method I keep seeing about safely? What would be the best way to root and install custom roms, neglecting the binary counter if I can get a jig or something?
Forgive me again for asking, I just need to have better answers before I try anything.
Are you asking for info for your Atrix or SGS2 device?
Sorry, I am asking about the SGS2.
ds1904.ds said:
I understand that this may have been asked, and I've been looking at similar threads, but I'm having a hard time finding a direct answer, so I apologize.
I have some experience rooting with an Atrix, but I just got this phone two days ago, this morning I used the 1-click method from rootwhiz to install the ICS leak. No problems having it run at all. I need to know, directly, did this install change my bootloader and change the binary count? I can't remember if I saw anytime of yellow triangle as people talk about. If it changed the bootloader what is there a safe method to return to the older bootloaders, and or do I even need to do so to root and install other roms?
I know that the Atrix had some problems in terms of returning to prior versions of things, and in my research I haven't found a direct answer to this question too.
Basically, did my bootloader change? Can I root using the heimdall method I keep seeing about safely? What would be the best way to root and install custom roms, neglecting the binary counter if I can get a jig or something?
Forgive me again for asking, I just need to have better answers before I try anything.
Click to expand...
Click to collapse
If you used the 1-Click method, yes. Your bootloaders are changed. Wouldve been much better to use the Heimdall method or just root your phone then flash the Leak ROM that task650 and Fenny made. As far as reverting bootloaders to stock, thats out of my range of knowledge. Im sure there is a way to do it though.
EDIT: For rooting, best way is to be on stock 2.3.4 and use the Zergrush exploit.
I've seen you're using the past tense a lot, I thought you already DID.
Anyway, for rooting and installing custom ROM, follow this thread:
http://forum.xda-developers.com/showthread.php?t=1311081
I can't pinpoint exactly what to do since having no info.
Thanks for the answers so far, now that I know my bootloaders have been changed I need to figure out how to either change back / and how to safely root. I may just have to wait it out I think though, no problem with that really, working just fine now. And never use the alarm
For clarification, my rooting experience is limited to the Atrix, the SGS2 is new as of Monday, and I am having trouble sifting through information. What I've learned so far is that maybe it was a little hasty to install the ICS leak the way I did. Prior to the ICS leak there was nothing changed on the phone.
You're going to have to get some experience with ODIN. Here is the bootloader you'll want to flash back to, however, then you'll probably need to flash a kernel with CWM (clock work mod) and then boot into cwm to flash a rom such as Tasks stock ICS leak. http://forum.xda-developers.com/showthread.php?t=1316726
So if I follow correctly the ICS leak I installed added newer bootloaders that prevent jigging in the future if it was needed. My two options are apparently to use the method that bypasses the counter, which was posted, or to use ODIN and flash the older bootloader, but this can be dangerous if done incorrectly.
The danger of bricking scares me a little, but I successfully used RSD Lite to unlock the bootloader on my Atrix, don't know if it's similar. Perhaps I should take the Atrix and attempt to install an older bootloader on it to get a feel for things? I figure that it wouldn't make much of a difference however...
I figured out that even though I have a newer bootloader now I still have a 0 for the binary counter, as the leak is considered a samsung official release, of course I don't know how that would effect any given warranty.
So, I still feel that these following questions are unanswered, I apologize if I am not understanding correctly:
1. Is it safe for me to root with the heimdall method even with the newer bootloaders
2. Is it safe for me to install custom roms without reverting the bootloader, as long as I am using the bypass method to prevent my counter from changing?
3. What is the exact risk to flashing the older bootloader, and what precautions should I take before doing so? If I flash the older bootloader without reverting to stock firmware will that cause a brick? Or is the risk just associated with fudging up the process of the flash itself, and hoping that the connection doesn't get cut (on that note, the phone, usb cord, and computer I'm using are all less than 4 months old, so that risk doesn't concern me a whole lote).
Sorry if these are stupid questions, I hope I am asking good enough questions to help others out in the future
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
ds1904.ds said:
1. Is it safe for me to root with the heimdall method even with the newer bootloaders
Click to expand...
Click to collapse
Dont believe you can root since you already flashed it with ODIN 1-Click
ds1904.ds said:
2. Is it safe for me to install custom roms without reverting the bootloader, as long as I am using the bypass method to prevent my counter from changing?
Click to expand...
Click to collapse
You cannot install custom ROM's because you dont have CWM.
ds1904.ds said:
3. What is the exact risk to flashing the older bootloader, and what precautions should I take before doing so? If I flash the older bootloader without reverting to stock firmware will that cause a brick? Or is the risk just associated with fudging up the process of the flash itself, and hoping that the connection doesn't get cut (on that note, the phone, usb cord, and computer I'm using are all less than 4 months old, so that risk doesn't concern me a whole lot).
Click to expand...
Click to collapse
Really not sure on these questions. Any takers?
ds1904.ds said:
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Click to expand...
Click to collapse
No; Only download mode (Odin/Heimdall) flashes trigger changes to the warning screen.
ds1904.ds said:
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
Click to expand...
Click to collapse
Kernel is a set of drivers that tells the hardware what to do. Firmware is like a new base. (XXLPQ, DXLP7 etc.) A ROM is the whole package.
Please if I missed anything or am incorrect about some/all of this, somebody correct me.
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
ds1904.ds said:
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
Click to expand...
Click to collapse
Should be fine. NONE of the ROMs you find on the I777 boards in Ported or Original will have bootloaders so no worries. And yes after root use Mobile ODIN to install a zImage which will give you CWM. Highly recommend Siyah 2.6.14. Please stick to just trying some GB ROM's and get the hang of making nandroids etc before moving on the ICS ROM's.
D3M3NT3D_L0RD said:
Should be fine. NONE of the ROMs you find on the I777 boards in Ported or Original will have bootloaders so no worries. And yes after root use Mobile ODIN to install a zImage which will give you CWM. Highly recommend Siyah 2.6.14. Please stick to just trying some GB ROM's and get the hang of making nandroids etc before moving on the ICS ROM's.
Click to expand...
Click to collapse
All I get is an apk file, I've been searching all night for a zimage... The file says i777 flashkernal, and it's just an .apk. Mobile Odin can't see it unless I name it zimage with no file extension. I tried that and it seemed like it was soft-bricked so I used odin on the PC to reflash the stock root think mentioned in the thread.
I was thinking of CM7 if it will work flashing as a zip from CWM, if I can get CWM on there that is.
ds1904.ds said:
All I get is an apk file, I've been searching all night for a zimage... The file says i777 flashkernal, and it's just an .apk. Mobile Odin can't see it unless I name it zimage with no file extension. I tried that and it seemed like it was soft-bricked so I used odin on the PC to reflash the stock root think mentioned in the thread.
I was thinking of CM7 if it will work flashing as a zip from CWM, if I can get CWM on there that is.
Click to expand...
Click to collapse
Where in the hell are you getting an apk from? If you dl Siyah or Entropy kernel, the zImage is in the zip. Pull that and put it on your SD card
I am interested because I was in your position. Did the ICS leak 1 day too early and lost root. So what method did you use to go back to GB? Did you have to flash a new bootloader or was that all done in one package? Was it Entropy's "return" method?
I was seeing if I can keep the ICS leak and root. A dev here advised that all I need to do is re-flash the zip filed ICS leak. However since I have no root, I can't CWM recovery...I don't know another method to flash the rooted ICS leak.
So I'm thinking I have to wait for an exploit, or flash back to an old GB, root, ensure I have CWM, nandroid (I nandroided my rooted GB before upgrading to ICS leak), then flash the zip ICS leak.
Does anyone else have alternatives?
ds1904.ds said:
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
Click to expand...
Click to collapse
SMH...root is not needed for CWM... a custom kernel is
Pirateghost said:
SMH...root is not needed for CWM... a custom kernel is
Click to expand...
Click to collapse
True but to do it with Mobile ODIN you need root
ds1904.ds said:
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
Click to expand...
Click to collapse
"ROM" is an improper name for the firmware flashed to a phone. (the memory in question isn't read-only by any means. In Windows Mobile devices, you had to flash the firmware image all in one go - but on Android, /system contents can be modified on the fly as they're a normal file system.) garyd9 started a little crusade against the term ROM and I try to continue it (but I slip up sometimes).
Kernel contains the most basic low-level hardware drivers for a device. It's a small portion of the firmware for a phone. The remaining portion is the system partition - /system - kernel and /system together make a complete firmware package.
And you are correct - our bootloaders are fundamentally unlocked, the only code signing enforcement is the custom binary counter. It can be reset either with the jig or with TriangleAway (TriangleAway requires ICS)
Entropy512 said:
"ROM" is an improper name for the firmware flashed to a phone. (the memory in question isn't read-only by any means. In Windows Mobile devices, you had to flash the firmware image all in one go - but on Android, /system contents can be modified on the fly as they're a normal file system.) garyd9 started a little crusade against the term ROM and I try to continue it (but I slip up sometimes).
Kernel contains the most basic low-level hardware drivers for a device. It's a small portion of the firmware for a phone. The remaining portion is the system partition - /system - kernel and /system together make a complete firmware package.
And you are correct - our bootloaders are fundamentally unlocked, the only code signing enforcement is the custom binary counter. It can be reset either with the jig or with TriangleAway (TriangleAway requires ICS)
Click to expand...
Click to collapse
Glad you chimed in. I now feel stupid at my lack of knowledge
I almost think that the issue is that your "unzipping" the zip image files that you are downloading.
Why is it so important that you keep the phone in a reversable mode? Are you planning on returning it or perhaps selling it and do not want it to be known that you have flashed it?
Personally I am not knowledgeable enough to offer much advice, I just read the forums as most and try to put together the peices of information that fit my situation.
The Dev forum is by far the best place to look and get your questions answered and there are a bunch of guides on step by step processes. The only real advice I can give you is to google each term and understand what it is you need and then post your question.
I got Motorola Photon 4G with Android 2.3.4. Already rooted it and install Bootstrap.apk. I want to flash roms but I don't want to unlock bootloader so I can keep my 4G. So i dont need to flash SBF files thingy? And do i need to do Nandroid too? Also what are the some stable roms with working 4G? I heard about Rocko Locked and MOF 2.3.5ish Locked? Is both roms good? If you have any tips, please do tell me
silverhawknike said:
I got Motorola Photon 4G with Android 2.3.4. Already rooted it and install Bootstrap.apk. I want to flash roms but I don't want to unlock bootloader so I can keep my 4G. So i dont need to flash SBF files thingy? And do i need to do Nandroid too? Also what are the some stable roms with working 4G? I heard about Rocko Locked and MOF 2.3.5ish Locked? Is both roms good? If you have any tips, please do tell me
Click to expand...
Click to collapse
No, there is no SBFing required if you don't want to unlock. If youve got bootstrap recovery installed (it doesnt come in an apk so im not sure what you mean) and can boot into it you can start flashing locked roms. The only one that you can flash that is still in development is Mof's rom, though. But it is a good upgrade from stock and everything works swimmingly. To flash it, just download the zip, throw it on your SD card, boot up into bootstrap recovery and flash the zip. No need to wipe anything, the installation will do it automatically.
Acvice said:
No, there is no SBFing required if you don't want to unlock. If youve got bootstrap recovery installed (it doesnt come in an apk so im not sure what you mean) and can boot into it you can start flashing locked roms. The only one that you can flash that is still in development is Mof's rom, though. But it is a good upgrade from stock and everything works swimmingly. To flash it, just download the zip, throw it on your SD card, boot up into bootstrap recovery and flash the zip. No need to wipe anything, the installation will do it automatically.
Click to expand...
Click to collapse
great news ,
Acvice , could u plz educate me also where i can find the bootstrap recovery and how i can flash it
regards
Bootstrap Recovery is an .apk file needs to be side loaded like any app not installed from the Play Store. It can be located by searching the term Bootstrap Recovery Motorola Photon in the search bar.
It never hurts to ask for help, Ill try to help
Hey there mate. Once i had first purchased my photon, cm9 wasnt out as far as i remember, or maybe it was, but it was in really unstable alpha's, but anyways, off topic. Have you read around the developers section yet? As you go through and get farther into the pages, you'll see less of cm10, cm9, and you will see stuff like homebase rom, alien rom, yada yada. As for all of the older roms that dont require you have an unlocked bootloader, i recommend you use rocko. It offers great speed, stability, and it doesnt look half bad. I dont really know where to start as far as helping you in terms of explaining all of the flashing process, but i will point you in the right direction.
When i first began flashing roms these 2 threads became my best friend;
This one covers about it all
This one is even quite educational
For visual aid, qbking helped me just to assure i followed steps correctly with his line of tutorial videos (he also reviewed some roms if you are curious)
I hope those links at least get you pointed in the right direction. It seems like an aweful lot to take in, but, its organised allowing for quick navigation and in reality, you only really have to skim through it.
If you have any questions, feel free to reply and il get back to you when im available, best of luck flashing, and enjoy your photon! :good:
silverhawknike said:
I got Motorola Photon 4G with Android 2.3.4. Already rooted it and install Bootstrap.apk. I want to flash roms but I don't want to unlock bootloader so I can keep my 4G. So i dont need to flash SBF files thingy? And do i need to do Nandroid too? Also what are the some stable roms with working 4G? I heard about Rocko Locked and MOF 2.3.5ish Locked? Is both roms good? If you have any tips, please do tell me
Click to expand...
Click to collapse
unlock the bootloader and use a custom recovery. bootstrap isn't a true recovery and should only be used if you can't unlock the bootloader.
so i'd go with the custom recovery that way you'll never have to flash an sbf to repair the phone if it gets messed up from flashing locked roms.
na7q said:
unlock the bootloader and use a custom recovery. bootstrap isn't a true recovery and should only be used if you can't unlock the bootloader.
so i'd go with the custom recovery that way you'll never have to flash an sbf to repair the phone if it gets messed up from flashing locked roms.
Click to expand...
Click to collapse
As the OP states he wants to keep 4g unlocking the bootloader will kill the 4g.
mof9336 said:
Bootstrap Recovery is an .apk file needs to be side loaded like any app not installed from the Play Store. It can be located by searching the term Bootstrap Recovery Motorola Photon in the search bar.
Click to expand...
Click to collapse
Woops, my bad on the false info about the bootstrap file Silver. Its been like a year since I had to install bootstrap. Just had a brain fart.
Acvice said:
Woops, my bad on the false info about the bootstrap file Silver. Its been like a year since I had to install bootstrap. Just had a brain fart.
Click to expand...
Click to collapse
No worries bro.
Sent from my MB855 using xda app-developers app
Well, I've pretty much had it with this latest update (ATT, 4.5.145). I'd like to go back to .141 as its easily rootable. My Atrix is boot unlocked, and I have no interest in the custom ROMs. I dont have squat on the phone I need to keep, so I can blow the whole thing away as needed. I have the latest USB drivers and RSDlite ready to go.
I located the following ROM, and downloaded it... "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", appears to be the correct one.
I've been reading and reading and reading on the forums here (i.e. I've searched a lot), but theres a lot of cross-info, its hard to tell whats applicable in some situations.
So the question....
Which HowTo/Method/Guide would be most appropriate for my situation? Or is there something that would prevent this back-rev?
Thanks for any help or suggestions.
K
KetoSoi said:
Well, I've pretty much had it with this latest update (ATT, 4.5.145). I'd like to go back to .141 as its easily rootable. My Atrix is boot unlocked, and I have no interest in the custom ROMs. I dont have squat on the phone I need to keep, so I can blow the whole thing away as needed. I have the latest USB drivers and RSDlite ready to go.
I located the following ROM, and downloaded it... "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", appears to be the correct one.
I've been reading and reading and reading on the forums here (i.e. I've searched a lot), but theres a lot of cross-info, its hard to tell whats applicable in some situations.
So the question....
Which HowTo/Method/Guide would be most appropriate for my situation? Or is there something that would prevent this back-rev?
Thanks for any help or suggestions.
K
Click to expand...
Click to collapse
Never flash an SBF unless you have no other choice. Major hard brick risk.
In this section I have a stickied thread with the answers you need.
If your bootloader is still unlocked and you still have a custom recovery installed, flashing a fruit cake should work fine.
upndwn4par said:
Never flash an SBF unless you have no other choice. Major hard brick risk.
In this section I have a stickied thread with the answers you need.
If your bootloader is still unlocked and you still have a custom recovery installed, flashing a fruit cake should work fine.
Click to expand...
Click to collapse
At this point, I dont have much choice. Unless some one figures out what motorola/att did with 145 to completely screw root (its beyond my abilities), I need to press forward. If I brick it, I brick it. I'll use your sticky as my guide then, seems reliable.
Bootloader is unlocked, though I've never installed a 'custom recovery'. Looks like the various fruitcakes links are unavailable for download?
What is the advantage of the fruitcake version over the version I posted?
Thanks for the guidance
K
KetoSoi said:
At this point, I dont have much choice. Unless some one figures out what motorola/att did with 145 to completely screw root (its beyond my abilities), I need to press forward. If I brick it, I brick it. I'll use your sticky as my guide then, seems reliable.
Bootloader is unlocked, though I've never installed a 'custom recovery'. Looks like the various fruitcakes links are unavailable for download?
What is the advantage of the fruitcake version over the version I posted?
Thanks for the guidance
K
Click to expand...
Click to collapse
I just sold mine but will look in PC history. My matrix was stock 4.5.145 and I rooted it. I remember failing a few methods till I found one that worked. If I figure out what I did I will post it for you. If not fruitcake is best way
KetoSoi said:
At this point, I dont have much choice. Unless some one figures out what motorola/att did with 145 to completely screw root (its beyond my abilities), I need to press forward. If I brick it, I brick it. I'll use your sticky as my guide then, seems reliable.
Bootloader is unlocked, though I've never installed a 'custom recovery'. Looks like the various fruitcakes links are unavailable for download?
What is the advantage of the fruitcake version over the version I posted?
Thanks for the guidance
K
Click to expand...
Click to collapse
The difference between what you posted (an SBF) and what I suggest (a fruit cake) is that an SBF is full stock firmware (bootloader, boot, system, radio, etc). It is the bootloader that causes the problems. Flashing an SBF is a crap shoot. You might do it 10 times without a problem, and the 11th time you hard brick your device. By hard brick I mean hard brick = your device is now a paperweight.
A fruitcake is essentially the same as a custom ROM. You are only flashing the boot and system images. This is always the best option for returning to stock.
However, you are in a different situation - uncharted waters so to speak. No one knows what to expect from 145. And since you don't have a custom recovery installed (CWM, TWRP, etc.) you can't just flash a fruit cake like you would flash a ROM. You should be able to use the fastboot method to flash the fruit cake, but again...uncharted waters.
I suggest trying the following in this order based on your current situation (options 1 and 2 assume you do in fact have an unlocked bootloader):
1) Fastboot flash a custom recovery, then try to flash the zip I posted on my rooting guide thread. If this works you will have rooted 145.
2) Fastboot flash a custom recovery, then flash the 141 fruit cake I made.
3) Fastboot flash the boot and system fruitcake images.
All the files and info you need can be found on my "Answers" thread and my rooting guide.
Do not flash an SBF until all else has failed. Let me know how things go with the above before you even consider this.
Edit:
Before you try any of the above, did you try UnlockRoot? It may work.
upndwn4par said:
A fruitcake is essentially the same as a custom ROM. You are only flashing the boot and system images. This is always the best option for returning to stock.
I suggest trying the following in this order based on your current situation (options 1 and 2 assume you do in fact have an unlocked bootloader):
1) Fastboot flash a custom recovery, then try to flash the zip I posted on my rooting guide thread. If this works you will have rooted 145.
2) Fastboot flash a custom recovery, then flash the 141 fruit cake I made.
3) Fastboot flash the boot and system fruitcake images.
All the files and info you need can be found on my "Answers" thread and my rooting guide.
Do not flash an SBF until all else has failed. Let me know how things go with the above before you even consider this.
Edit:
Before you try any of the above, did you try UnlockRoot? It may work.
Click to expand...
Click to collapse
Understood, thanks for the explanation.
UnlockRoot couldnt gain root access
I will attempt your suggestions Thanks very much for the guidance, its invaluable
http://forum.xda-developers.com/showthread.php?t=1769497.
I am pretty sure this is the method I used to root 4.5.145 before I sold it
KetoSoi said:
Unless some one figures out what motorola/att did with 145 to completely screw root ...
Click to expand...
Click to collapse
From what I hear, the only thing that Moto "screwed up" (I wouldn't really call it that) is that on .145 they filled up /system. That is actually trivial to resolve - delete a few apps from /system/app that you don't need/want (you can install them later if you want to, some can live happily on /data) and - this is crucial - wipe /preinstall, since that is what fills up /system. If you don't wipe /preinstall, just deleting apps from /system will only last until next boot. Or, well, you don't need to wipe /preinstall, you can just flash the rooting preinstall image.
upndwn4par said:
Let me know how things go with the above before you even consider this.
Click to expand...
Click to collapse
I was able to flash CWM Recovery no problem. I was able to flash your superuser zip as well, however it did not root the system. All indicators showed it as being successful, but ultimately it was a no-go.
At that point I flashed your fruitcake 141 images, good to go there. I then applied the preinstall method, and viola, rooted again.
I am good to go, thanks to your knowledge and skills Thank you!
Now, all I have to do is email a scan of my middle finger to motorola/att.... lol
ravilov said:
From what I hear, the only thing that Moto "screwed up" (I wouldn't really call it that) is that on .145 they filled up /system. That is actually trivial to resolve - delete a few apps from /system/app that you don't need/want (you can install them later if you want to, some can live happily on /data) and - this is crucial - wipe /preinstall, since that is what fills up /system. If you don't wipe /preinstall, just deleting apps from /system will only last until next boot. Or, well, you don't need to wipe /preinstall, you can just flash the rooting preinstall image.
Click to expand...
Click to collapse
I tried several variations of what youre refering to, however it was to no avail.
I went as far as to delete several useless items (apps) out of the dir, the free space indicated never changed. The amount I removed was more that enough copy su in... yet, it always reports not enough space.
I tried an experiment. I renamed the 'fake' su (always zero bytes) in the bin dir to 'su.old'. Within 30 seconds, *something* renamed it back to 'su', happened right in front of my eyes in Root Explorer.
When you say 'wipe preinstall', specifically you mean?
KetoSoi said:
I tried several variations of what youre refering to, however it was to no avail.
I went as far as to delete several useless items (apps) out of the dir, the free space indicated never changed. The amount I removed was more that enough copy su in... yet, it always reports not enough space.
I tried an experiment. I renamed the 'fake' su (always zero bytes) in the bin dir to 'su.old'. Within 30 seconds, *something* renamed it back to 'su', happened right in front of my eyes in Root Explorer.
When you say 'wipe preinstall', specifically you mean?
Click to expand...
Click to collapse
Wow, that's just bizarre. Not sure what to think here.
I meant something like
Code:
moto-fastboot erase preinstall
KetoSoi said:
I was able to flash CWM Recovery no problem. I was able to flash your superuser zip as well, however it did not root the system. All indicators showed it as being successful, but ultimately it was a no-go.
At that point I flashed your fruitcake 141 images, good to go there. I then applied the preinstall method, and viola, rooted again.
I am good to go, thanks to your knowledge and skills Thank you!
Now, all I have to do is email a scan of my middle finger to motorola/att.... lol
Click to expand...
Click to collapse
Awesome!
I really don't understand why the superuser zip did not give you root access.
Moreover, I don't understand why some users seem to be able to root 145.
I guess I shouldn't be surprised since this device has always been a PITA.
upndwn4par said:
Awesome!
I really don't understand why the superuser zip did not give you root access.
Moreover, I don't understand why some users seem to be able to root 145.
I guess I shouldn't be surprised since this device has always been a PITA.
Click to expand...
Click to collapse
Very odd some cannot root. I was on permalocked bootloader and still rooted after soak
Its sad, because the 145 update seemed like it made the phone a little snappier, and the screen was a pinch smoother.
What do you guys think about applying the CWM Zip for update 4.5.145 in my situation? Would that be safer?
Uh oh.... you guys ran away! LOL
I was able to flash the 145 update via CWM from NYG-SBXLII's handy zip file
No real problems, 145 running fine WITH root intact. Awesome
Had to blow away the recovery-from-boot.p file afterwards, and re-flash CWM Recovery, but it was all good.
Updated SU and bin's, good to go.
affiatic said:
http://forum.xda-developers.com/showthread.php?t=1769497.
I am pretty sure this is the method I used to root 4.5.145 before I sold it
Click to expand...
Click to collapse
This worked for me too with 4.5.145, followed it exactly and had no problems. Thanks!
KetoSoi said:
Well, I've pretty much had it with this latest update (ATT, 4.5.145). I'd like to go back to .141 as its easily rootable. My Atrix is boot unlocked, and I have no interest in the custom ROMs. I dont have squat on the phone I need to keep, so I can blow the whole thing away as needed. I have the latest USB drivers and RSDlite ready to go.
I located the following ROM, and downloaded it... "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", appears to be the correct one.
I've been reading and reading and reading on the forums here (i.e. I've searched a lot), but theres a lot of cross-info, its hard to tell whats applicable in some situations.
So the question....
Which HowTo/Method/Guide would be most appropriate for my situation? Or is there something that would prevent this back-rev?
Thanks for any help or suggestions.
K
Click to expand...
Click to collapse
How did you unlock the bootloader for firmware 4.5.145? I've been looking everywhere on how to do it safely!
upndwn4par said:
The difference between what you posted (an SBF) and what I suggest (a fruit cake) is that an SBF is full stock firmware (bootloader, boot, system, radio, etc). It is the bootloader that causes the problems. Flashing an SBF is a crap shoot. You might do it 10 times without a problem, and the 11th time you hard brick your device. By hard brick I mean hard brick = your device is now a paperweight.
A fruitcake is essentially the same as a custom ROM. You are only flashing the boot and system images. This is always the best option for returning to stock.
However, you are in a different situation - uncharted waters so to speak. No one knows what to expect from 145. And since you don't have a custom recovery installed (CWM, TWRP, etc.) you can't just flash a fruit cake like you would flash a ROM. You should be able to use the fastboot method to flash the fruit cake, but again...uncharted waters.
I suggest trying the following in this order based on your current situation (options 1 and 2 assume you do in fact have an unlocked bootloader):
1) Fastboot flash a custom recovery, then try to flash the zip I posted on my rooting guide thread. If this works you will have rooted 145.
2) Fastboot flash a custom recovery, then flash the 141 fruit cake I made.
3) Fastboot flash the boot and system fruitcake images.
All the files and info you need can be found on my "Answers" thread and my rooting guide.
Do not flash an SBF until all else has failed. Let me know how things go with the above before you even consider this.
Edit:
Before you try any of the above, did you try UnlockRoot? It may work.
Click to expand...
Click to collapse
hello, ive been using 4.5.145 and was unable to root it, the problem with mine is that when I try to use the preinstall method it chokes when i type the "cp /preinstall/su /system/bin/... there was a message cp write error: no space left on device.. I have tried everything (almost) to root it but was unlucky.. then i saw this thread http://forum.xda-developers.com/showthread.php?t=2153422 ... i wanna try your suggestion but cant find the zip file in suggestion 1 and the 141 fruitcake you made on suggestion 2 and cant find file on option 3.. please do help me.. I have unlocked bootloader and have rom racers cwm.. thank you and more power..