• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Developer's Team

I haven't seen this posted anywhere and took me hours of searching and trying to fix my phone to find it.

It's the Motorola Devour 01.15.08P Monster SBF Flash File. You can get it here...
CALAND_X_01.15.08P_MONSTER_01.sbf

I obtained the link from the root procedure located at...
Devour

Here's my Devour story with a happy ending (well, at least for having a working Devour again)...

I rooted my devour and then ran a backup both with ADB (pulling all files from phone) and with Titanium Backup. Then, like an idiot, I went through removing some system apps (which I thought were just bloatware) but apparently I hit something that wasn't. After rebooting my phone was stuck in boot screen. If I connected USB cable then it would continue on like it was going to fully boot but as soon as boot loader went away and home screen was "about" to come up, I then would get constant crash messages of google apps and motorola blur setup. The only thing I could access was task bar at top. I couldn't run apps, I couldn't go into any menu's (other than setting USB to motorola pc tools or sd card), etc... So I could copy files to SD Card, but because I couldn't get into the menu to enable USB Debugging, I couldn't access the system directory at all through ADB (it won't connect without USB Debugging enabled). I was absolutely screwed!

I tried using another Devour with Titanium Backup (it was also rooted) to create the update.zip and then run from boot loader (boot with power + space + 'r' held down) by pressing Z + B and then running option Z + N to update from update.zip on sdcard, but it would fail with signature error. I tried every single signature process out there (had like 6 different versions) and all would fail.

So then I said ok, let's try the full reset to wipe the phone, after all I can re-load Titanium Backup and my files are still on the SD Card so I should be good. However, after performing the full reset (option Z + M from bootloader) it still behaved exactly the same. So again, I was REALLY screwed!

But luckily I finally found the monster flash posted at the location above. I simply downloaded the file, ran RSDLite 4.6 (which detected my phone just fine), selected the SBF flash file and clicked Start. It kicked my phone into USB Bootloader mode (as a side note, you can actually access this by turning the phone off, removing battery and SDCard, plugging in USB and holding down keys E+R at the same time until blue screen shows up) and started the flash update. It only took a couple minutes and showed success after rebooting my phone. I held my fingers crossed and (drumroll)...... BOOYA! It worked perfectly! It started the motorola blur setup screen and I used existing account and everything installed perfect and went into original home screen.

I downloaded Titanium Backup and restored my previous backup and all was good.

One note, this Monster Flash File is version 1.15.08P but the latest update (which includes some good performance fixes) is 1.15.10P I believe. After I flashed the file above and went home it did prompt me immediately to run the 1.15.10P update. If I knew how to capture these files I would and post it. If anybody knows the process, let me know and I'll grab it as I haven't updated it yet and can always go back and do it again if necessary.

Anyway, I wanted to post this as it might save some people some big headaches or even possible unnecessary returns. Plus, it should give a little peace of mind for being able to recover when trying out things such as testing a working 2.1 build so we can all enjoy. :-)

Once again, the monster flash file is located at...
CALAND_X_01.15.08P_MONSTER_01.sbf

And I got this file from the root procedure outlined at...
Devour

Thanks,
~Andy
 
thank you very much, yeah i searched forever and couldnt find any sort of dump till yester someone posted the default apps.

i was trying to get rid of some bloatware and deleted gtalkservice.apk thinking it was the google talk well i was wrong lmao it actually destroyed my android market and i just took the default apps copied them all to /system/app and still didnt work then i did a full system reset using the r+spacebar to boot into recovery menu and hitting z+b to show the text the the fullreset z+m

found default apps apps at this forum: Anyone Have Backup of Original APKs? - Android Forums

here is the direct link to the files: DefaultApps.zip download free - FileSwap.com
 
so????
did somebody still trying to make update.zip for devour??????????
what about rebuilding Huawei Ascend or LG VS660 Vortex firmware (because they are based on the same chip, and other specs are familiar)??
 
The Devour has a locked bootloader like the Droid X i believe, i remember hearing that somewhere. right now i have both the X and the Devour. I love both of them but i use the X more because yeah, custom roms higher android stronger etc.
 
snowboarderxd1 said:
The Devour has a locked bootloader like the Droid X i believe, i remember hearing that somewhere. right now i have both the X and the Devour. I love both of them but i use the X more because yeah, custom roms higher android stronger etc.
Click to expand...

yes, but devour is rooted, and maybe we can try to load clockworkmod or sbsrecovery... ect.

or... perhaps there is a method to sign mod firmware like original motorola's rom
 
A weekend project? You think you can make progress on this over the weekend? Best of luck, it's something that's long overdue. Shoot for Gingerbread. :D
 
I guess we're hoping to put together the software needed to that Devour users can attain a stable and permanent root and flash a stable ROM that makes it a better phone. I think we're going to explore SmokedGlass 6.0 since some people have mentioned it worked for them. So instead of rumors, let's make it a reality.
 
Count me in. I don't have much coding or Linux experience but I'll be more than happy to test, and give my two cents if I can.

Personally, I'd prefer Eclair or Gingerbread to some third party ROM. But if this Smokedglass is indeed a good stepping stone then I'll be more than happy to help however I can.
 
I'm actually thinking about maybe creating our own ROM. Go to the linux website and download ubuntu and burn it to a cd. thats how i run linux. i never partitioned my hard disk or nothing.
 
Im currently pulling all the files off of my devour and i'm going to try and alter them and push them as maybe a ROM or something. We'll see how this turns out. I'll post a download link later.
 
I tried to push all the files I have in /data/app, /data/data and /sys/app onto the Android emulator running 1.6 SDK (there's probably a better way to do this) and I couldn't. If anyone winds up with a workable file (AVD isn't it?) then can they upload it somewhere?
 
im pulling every single file thats on my phone onto an external sd card because adb couldnt process certain files for some reason. its been goin for 3 hours. just hold up a bit.
 
does anybody know, is droid x's bootloader the same, as devour's?
and, if yes, can we use it for cracking devour... (maybe patch droid x clockwork mod)
 
I emailed koush today about maybe him building a recovery for us. He has yet to reply but I think he might go for it since we are a relatively active community.
 
Don't need to partition anything to run Linux. Read: Wubi. Windows sees it as just a big file on the hard drive. Linux sees it as its own partition.

As for our "own ROM," what kind of ROM were you thinking? Android 2.3? Something altogether different? I'd rather shoot for a ROM with a custom kernel, to allow wifi tethering as an infrastructure access point.
 
Whatever we choose we'll have to start with the barebones vanilla android and build up from there. I think achieving stability on the devour hardware will be key.
 
As long as it has a custom kernel with netfilter whatsits so I can wifi tether as an infrastructure access point. I've been trying everything to connect my Nintendo DS to the internet, Connectify.me, Barnacle, even any public access point I can find. I'm at the end of my rope with this thing. Stupid DS doesn't support WPA2 or ad-hoc networking. But I digress.

I know basically nothing about Cyanogen since the Devour is my first Android. What's different about it?
 
Well i think if we like. "Copy paste" our keylayout and other essential files into a droid x or something similar's ROM it'll be a great test.
 
If it were that easy it would have been done by now. The problem is getting into the bootloader if I remember correctly. Then one other potential big problem is drivers... I wouldn't assume the bootloading process will be the same or even similar to any of the mainstream Droids or anything else, though if it is then a lot of the work is done for us.
 
You must log in or register to reply here.
Back
Top Bottom