Alright, so I know what went wrong. I messed up, I know I did, so please try not to mention it.
I accidentally deleted my lib folder in the /system directory using root explorer. What I was trying to do is replace it with the one found in a different thread (as I was missing some files that I needed to receive the BELL OTA update)
So now the phone will not boot past the above mentioned logo (thread title)
I have tried going into android recovery and wiping and restoring all data but that did not help, my phone is not unlocked and I have never installed a different ROM.
What should I do?
I may be wrong, but if you are not unlocked, you may have to do a full SBF flash to get back up and running. If you were unlocked you could just flash a system.img via fastboot.
Alright, I will look into that, right now I am at school so if you could give me a link to a guide for the Bell Motorola Atrix I would appreciate it, if not I will search through the forums for it later.
Thanks for the help!
what did you make on your case.
I have the same problem.
Please help me
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..
Okay guys, I've been trying to do all of my research and think I've got it pretty well sorted out but just want to verify.
I'm new to android. The last android phone I messed around with was the gf's Droid Eris which I put Froyo on like 3 years ago.
I got my GS4 and was excited to find how easy you can flash custom recoveries with apps from the market. I installed ROM Manager and flashed CWM. I was surprised when it didn't really work and have since done my research to find that ME7 breaks all that. I'm rooted and everything is cool but I'm trying to take the OTA update to MI1.
I know I need to restore the stock recovery, the question is, how? I've found threads for other phones that says you can flash "recovery.img" from the OTA update in the cache folder. I don't see recovery.img. I see a recovery.sh but no recovery.img.
So I found this thread: http://forum.xda-developers.com/showthread.php?t=2357235&highlight=stock+recovery and downloaded the .zip in the first post. I found a recovery.img file in this tar file. Is this what I need to flash to my phone? If so how? My guess is with Odin? If so is it the PDA slot (everyone always asks which slot)?
I've seen a lot of people say "flash stock me7" but I'd rather not have to do that. I guess I could just flash stock MI1 but once again I'd rather not have to completely wipe the phone, nor do I see why you would have to wipe the whole phone if you can flash recoveries without wiping the phone.
Thank you all for your help. Sorry if there's already a thread for this, if there is please just point me in the right direction. I'm surprised ROM Manager doesn't have some kind of option to "restore recovery" or something like that.
I also see talks of RUU but that looks like an HTC thing? Thanks again.
videogmike said:
Okay guys, I've been trying to do all of my research and think I've got it pretty well sorted out but just want to verify.
I'm new to android. The last android phone I messed around with was the gf's Droid Eris which I put Froyo on like 3 years ago.
I got my GS4 and was excited to find how easy you can flash custom recoveries with apps from the market. I installed ROM Manager and flashed CWM. I was surprised when it didn't really work and have since done my research to find that ME7 breaks all that. I'm rooted and everything is cool but I'm trying to take the OTA update to MI1.
I know I need to restore the stock recovery, the question is, how? I've found threads for other phones that says you can flash "recovery.img" from the OTA update in the cache folder. I don't see recovery.img. I see a recovery.sh but no recovery.img.
So I found this thread: http://forum.xda-developers.com/showthread.php?t=2357235&highlight=stock+recovery and downloaded the .zip in the first post. I found a recovery.img file in this tar file. Is this what I need to flash to my phone? If so how? My guess is with Odin? If so is it the PDA slot (everyone always asks which slot)?
I've seen a lot of people say "flash stock me7" but I'd rather not have to do that. I guess I could just flash stock MI1 but once again I'd rather not have to completely wipe the phone, nor do I see why you would have to wipe the whole phone if you can flash recoveries without wiping the phone.
Thank you all for your help. Sorry if there's already a thread for this, if there is please just point me in the right direction. I'm surprised ROM Manager doesn't have some kind of option to "restore recovery" or something like that.
I also see talks of RUU but that looks like an HTC thing? Thanks again.
Click to expand...
Click to collapse
Maybe this thread can help. http://forum.xda-developers.com/showthread.php?t=2301259
I suppose that would work, but my phone's not bricked and I'm not trying to restore any kind of factory settings. I just want to restore the stock recovery. A lot of people appear to have problems and have to wipe their phones anyway doing that it looks like.
Bump. No one? Really? I'm just looking for someone to confirm whether or not this is correct. At least I didn't just ask the question without doing the research.
videogmike said:
Bump. No one? Really? I'm just looking for someone to confirm whether or not this is correct. At least I didn't just ask the question without doing the research.
Click to expand...
Click to collapse
I was rooted so I had to restore stock to get the OTA update. I used the thread that Riker attached below your original message and it worked fine for me. It doesn't matter that your phone is not bricked, this method will Odin flash a stock image onto your device.
Good luck.:good:
Just seems like overkill to flash the entire thing (no wipe or not). Okay, thanks all.