Hi,
I guess the title gives it away... I have a Bell Atrix and I tried to install the de-odexed files from this thread.
I started off with a clean state, a factory reset.
Got root and Superuser without any problems...
Then I had some trouble running the ApplyMods.bat (had to run it as administrator)... anyway, got that done, pushed files to phone... now wait a minute... I was doing this in order as it is written in the guide. I guess I had to run the deodex script before no? DUH!
And, being a genius, when I saw the blinking red light I immediately did a factory reset from the recovery menu. heh.
ADB doesn't see the phone with early USB enumeration.
Is RSD the only thing that I can use now? (which means I'm screwed because there is no Bell SBF?)
In any case, I'm still under the 30 day warranty from Bell, and I've already called and I can get it replaced at no cost on the spot...
So... what else can I try? Worst case it's going back to Bell...
Related
I'm fairly new to the whole rooting business, and got my phone rooted the first day I had it and customized it how I wanted. Now I want to wipe it to try some new stuff. I've already backed everyone up with Titanium Backup and made a Nandroid recovery, but when I performed a factory reset/data wipe, I reset my phone and it still loaded my rom (the dasBAMF 3.0). Since I wiped but my Rom loaded (my assumption at least) something isn't working correctly and my keyboard won't pop up when I need to type in text for anything. Did I miss a step to completely wipe my phone...?
EDIT***
Really, I just want to try and get my phone either back to stock, or as close as I can (since I don't know what they check for when trying to exchange at the verizon store, if possible) so that my warranty is voided and stuff....
Yeah... You missed the who step of flashing another ROM. It's going revert back to the last ROM that was there if it isn't replaced.
Oh :/ Where would the vanilla TB rom be? Cause I might just be missing it, but I can't seem to find it in Android Development.
I would prefer to exchange it for another phone, so I'm trying to get it back to stock (or as close to it as I can if all they do is look at it without checking so I can exchange).
You're gonna want what's called an RUU. I'm not sure where the most recent OTA RUU is or who's been taking care of those. It should be in the dev forum. The version number should start with 1.70. To flash it, change the name to pg51img.zip and flash it like you would a radio. It will snap your phone right back to factory stock. If you can't find it, let me know and I'll try to hunt it down.
There's this:
http://forum.xda-developers.com/showthread.php?t=997724&highlight=RUU
but none of the file names start with 1.7? Also, the TS has in caps red: "DO NOT FLASH THESE OVER ROOTED DEVICES, UNLESS YOU KNOW WHAT YOU ARE DOING." and I wouldn't know what to do with it even if I got the RUU that started with 1.7.
EDIT***
Well, I found this:
http://forum.xda-developers.com/showthread.php?t=1009423
Since I'm new, that will work for me too, correct? I see nothing stating that it shouldn't...
iImmortality said:
There's this:
http://forum.xda-developers.com/showthread.php?t=997724&highlight=RUU
but none of the file names start with 1.7? Also, the TS has in caps red: "DO NOT FLASH THESE OVER ROOTED DEVICES, UNLESS YOU KNOW WHAT YOU ARE DOING." and I wouldn't know what to do with it even if I got the RUU that started with 1.7.
EDIT***
Well, I found this:
http://forum.xda-developers.com/showthread.php?t=1009423
Since I'm new, that will work for me too, correct? I see nothing stating that it shouldn't...
Click to expand...
Click to collapse
That last link, got to restore to stock for root and non-root users... That will work. Basically, after you flash the first one you'll be stock without root. The second flash will restore S-on.
After countless hours of research, I decided to unlock my bootloader and to root my Motorola Atrix 4G. With success, I was happy to have everything working and installed the Darkside Custom Rom. I let a friend borrow my phone, and they saw the AT&T system update and they decided to install it. They bring back the phone and the system update has finished and was installing. The phone powers off and starts to install the update. 10% into the install, it stops, and I got the little green droid man with the /!\ behind him. I take out my battery, place it back in after 30seconds. It powers on, boots up, powers off and tries to load the update again. I restart it, but this time quickly going into RomManager and starting it up in Recovery Mode. I go to restore the phone using the file I backed up from the TitaniumBackUp app, everything backs up except the system. I plug my phone into my laptop, and everything is in the folder. I performed a system/factory reset, downloaded the last Gingerbread update, but nothing helps. Anything I try to load it says "Installation aborted". No matter if it's the original update or a ROM I download. Looking up other forums, I notice others that have downloaded the Darkside ROM have had the same; if not similar issues. I apologize for the length of this message, but I wanted to put in as much detail as I could so you know exactly what the issue is. I look forward to hearing from someone, and thank you in advance!!!
You probably need to sbf it back to a stock ROM and start over. I had a similar problem when I first got my Atrix and the AT&T update first came out. I had already rooted it and didn't unlock the bootloader yet. It tried to update and bricked the phone. Got AT&T to give me another though as I had just got the thing.
nickdeal said:
You probably need to sbf it back to a stock ROM and start over. I had a similar problem when I first got my Atrix and the AT&T update first came out. I had already rooted it and didn't unlock the bootloader yet. It tried to update and bricked the phone. Got AT&T to give me another though as I had just got the thing.
Click to expand...
Click to collapse
Thanks a ton! How would I go about doing that?
You need to download motorola RSD app to you computer. Search XDA for stock firmwares and download one. You will then need to use the button combo to get in to RSD. Connect the phone to your computer and make sure it recognizes. I had an issue where one of my laptops would not recognize the phone for anything. I had to use a different laptop. Once it's done you should be back to stock. The bootloader should be unlocked still. Just root and flash your ROM of choice.
Sent from my MB860 using XDA App
Hello guys, you'll have to excuse me for the wall of text, but it is necessary to fully describe my ordeal.
I bought an used atrix about 4 months ago from ebay (and i'm now deeply regretting it, too many issues). When I first received the phone I was unable to hear callers, even though they could hear me (badly, but could). I resolved that the easiest way possible: I bought a headset. Even with that issue and since it was impractical for me to return the phone because I'm in a different country (customs alone were over $100) I continued to use it. I flashed CM7 and ATT N_.37, flashed TWRP 2.1 and I enjoyed my phone for a couple months (even with the audio issue). Then one day, I went to bed with my phone on a full charge and in the morning I found it turned off. I tried to turn it back on and nothing happened. I thought maybe the battery had been drained by something, because I had left 3G data enabled. I tried to charge it and nothing happened, except the phone started to get really really hot in the lower part so I decided to disconnect it. I tried again a couple hours later and same thing happened. Next day I hit the power button and was able to enter android recovery. I wiped and factory reset, reinstalled cm7, gapps and radio and phone turned on and showed around 60% charge and it seemed fine and then all of a sudden the led started glowing light blue. Then the phone shut down and started to boot loop. I took off the battery, let it rest a while and then when I turned it back on everything worked fine (still, minus audio). That was two weeks ago. Today, it started to do the something similar but worse. Blue led flashing and boot loop are there but if I enter recovery I can't find anything in the sdcard, and if I place a microsd in the slot it isnt recognized. Also, led is flashing blue even while in recovery so I doubt it is a CM7 issue.
tl;dr My phone is dead. Can it be fixed or do I now own a $250 paperweight?
Try to flash your phone with your stock firmware using rsd lite
here a list of firmwares ... http://forum.xda-developers.com/showthread.php?t=1125944
WARNING! : flash it with YOUR stock sbf !!!
isn't that dangerous? from what i understand with this post it seems as if it isn't advisable to use an sbf on an unlocked bootloader.
not.a.troll said:
isn't that dangerous? from what i understand with this post it seems as if it isn't advisable to use an sbf on an unlocked bootloader.
Click to expand...
Click to collapse
Only if you're downgrading. It can work if you do it properly, but it's not recommended. Fruitcakes are the more foolproof way to go.
well i chickened out of the .sbf flash and just tried the moto-fastboot stock restore available elsewhere. while everything seemed to flash correctly i am still bootlooping/shut down. also, light blue led still there and sometimes i get stuck on bootscreen and can't even enter recovery. guess ill have to take it to a shop and see if something can be done. else S>atrix 4g for parts.
D:
hello to all
my atrix 4g originally was in firmware 4.5.141.MB860 ATT, i unlocked the bootloader succesfully and flash CM7... but for reasons of life (silly excuse jejeje) i want to take it back to the original fw... with this files: Blur_Version.4.5.141.MB860.ATT.en.US and 1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf.gz can i go back to stock fw? with this stock files i lose the boot unlock? is this a safe method? and what is the safest?
thanks for your help and greetings from Colombia (and sorry for my bad english)
Flash the latest sbf for your phone. I've done several with no problems. Yes, you do lose the unlocked bootloader though.
This will return you to stock. I used the same files.
not.a.troll said:
well i chickened out of the .sbf flash and just tried the moto-fastboot stock restore available elsewhere. while everything seemed to flash correctly i am still bootlooping/shut down. also, light blue led still there and sometimes i get stuck on bootscreen and can't even enter recovery. guess ill have to take it to a shop and see if something can be done. else S>atrix 4g for parts.
D:
Click to expand...
Click to collapse
I also have been through several phones with this issue. Although you can flash the sbf with no troubles, that is really only good for sending it into warranty. From my experience, this is a hardware issue, and flashing the stock sbf doesn't solve the problem. If you do not have warranty, a repair shop is your best bet.
Good luck.
Repy
x-geo said:
hello to all
my atrix 4g originally was in firmware 4.5.141.MB860 ATT, i unlocked the bootloader succesfully and flash CM7... but for reasons of life (silly excuse jejeje) i want to take it back to the original fw... with this files: Blur_Version.4.5.141.MB860.ATT.en.US and 1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf.gz can i go back to stock fw? with this stock files i lose the boot unlock? is this a safe method? and what is the safest?
thanks for your help and greetings from Colombia (and sorry for my bad english)
Click to expand...
Click to collapse
Hi,
Yes you can go back to your stock rom. Another yes, you will lose all your files and your bl unlock too. You have to start everithing from the begining. this is a safe method if you flash your own rom.
Hey guys, I was running stock ZVC (with stock recovery and bootloader) until just a few minutes ago, when I finally gave in and told the phone to apply the OTA update that was pushed out last week (the "ZVE" one). It started doing its thing, but next time I looked back at the device it was in recovery mode, just sitting there at the menu prompt...
I've since tried rebooting and powering off about half a dozen times, but it just keeps looping back to recovery mode. I also tried wiping the cache and rebooting, with no luck... It still loops back to recovery mode. I don't know what went wrong, but I'm assuming it could be related to one of two things that I didn't think about until afterwards:
1) The phone was rooted via Kingoroot, and root was still active when I tried to apply the update.
2) Just a FEW programs were frozen via TitaniumBackup (as well as Android's own app management system, using the "disable" feature), but these weren't system- or kernel-critical apps. They were things like LG Health, Sprint Money, etc...
Can anyone suggest a fix? Right now it just keeps rebooting into stock recovery and I've never had to deal with an issue like this, so I'm not sure what to do. I was obviously running the stock ROM, so I'm not set up to flash stuff. Although if it can be done with the default recovery, I suppose I could obviously do that... Once again, everything was stock on the phone except for Kingoroot, which was still enabled during the update.
I'm in a pickle here, guys. It's not like I'm any different than everyone who "needs their phone for work," but yeah, I need my phone for work... If I have to wipe data/factory reset, there's probably no way to pull some data off of the phone via PC first, is there? I suppose it's not that big of a deal, but I have some data and some program data that I hadn't gotten around to backing up yet, because I didn't think I'd need to until before I attempted to flash a new ROM or custom recovery.
Any help would be HUGE. Thanks...
EDIT: I took it into the Sprint store today a couple hours after I posted this, and they said I'd have to send it in to LG for warranty service. I don't know if the Sprint tech person knew what she was doing or not (because she had to use Google to figure out how to put the phone into download mode, even though she owns the same model), but she said that she couldn't establish a connection between the PC and the phone...
Now I'm not sure if that's the case, or if she just didn't have the right drivers installed, or if she was even in the right mode (I think she was using some Sprint-made flashing tool, but she did get it into download mode). She also seemed bored and like she just didn't wanna deal with it, so I don't know...
Assuming I can flash back to an earlier build like ZVB (and assuming I can even find it online), is that done from download mode or from recovery? By the way, we also tried just doing a factory reset and that didn't work either; just keeps rebooting to recovery...
Thanks...
EDIT 2: Fixed by flashing to stock via these instructions. Had to select Board DL and use a different key sequence as described here.
I thought you guys might find this amusing, and hopefully it will help some people that get into a similar situation as myself. First, a little background - I rooted and installed Alliance Rom years ago back before the bootloader was unlocked. This worked amazing for me for a long time but I've recently had some weird issues with my phone so I decided to do a factory reset.
I went into settings, clicked factory reset, and then my phone got into a boot loop on recovery. I remember from before I had to do a regular boot then click recovery at the prompt instead of doing the factory recovery so I did that.
Instead of doing a normal wipe, I wanted to wipe everything on my phone and start from scratch so I did the full wipe (in what I think was TWRP or safestrap or whatever). When I went to reboot my phone it had a message like "are you sure? there's no OS installed" and I clicked ok. Well now I couldn't get the phone to boot into anything except download mode so at least I can use Odin.
I'm frantically searching google to try and find ways to install some sort of recovery so I could load AllianceRom again since I still had the zip file for it. Eureka, I found TWRP for my phone! I tried to flash TWRP through Odin but that doesn't work because my bootloader wasn't unlocked.... I remember this from last time ... all of the places I found online to install any sort of recovery required the phone to be booted into android.
So I'm clicking around and someone has a recovery randomly posted in a thread so I install it thinking, what the hell, what's the worst that could go wrong. So I install it through Odin and boot into normal recovery and I get this message saying my phone has been tampered with and to go to a verizon store immediately! Oops... upon further investigation (looking at the download screen), I tripped the knox flag... oh well, it's not like my phone is in warranty anymore (I got it on release day).
I search around looking for what I should do next and I found a thread that talked about being on complete stock, rooting, then unlocking the bootloader. I download all the files I need (newest firmware here - https://www.sammobile.com/firmwares/galaxy-note3/SM-N900V/ and thread here - https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010) to go back to stock and flash in Odin. Actually I didn't download from sammobile.com because it was downloading too slow so I just googled the file name and found it somewhere else faster, go figure.
Everything seems to be going ok then all of a sudden FAIL in Odin... Ahhh what the heck do I do now? Try again obviously! Second try works woo hoo! Phone start booting up, things are looking good!!! hooray!! But wait... it's taking forever to start and it's stuck on the Verizon logo... uh oh... taking way too long to boot up so I pull the battery and try again. Boots right in saying that android is upgrading so I think I'm finally in the home stretch here.
I try to run the ArabicToolApp for Root but I installed the latest firmware which isn't supported DAMN IT! Downloaded the correct firmware (OB6!), flashed in Odin, same problem before where it was stuck on the red verizon screen, pulled battery, rebooted, finally time to get root!
Phone finally boots into OS and I get a popup "unfortunatley com.google.process.gapps has stopped" great... and it keeps coming up over and over again after I hit ok... just my luck! Reboot again to see if that fixes the issue. Seems weird that I didn't have to go through all the initial setup stuff I did on the other version I installed... hmm... or maybe it was because I pulled the battery on the red verizon screen? Whatever. I somehow manage to get to options to do a factory reset and I let the verizon screen stay on a while this time. I'll go take my contacts out and give my wife some love while I wait
Come back and the phone is at the setup wizard, this is good news. Enabled USB debugging, installed root, done! Thank god!
Next I want to unlock the bootloader. I follow the steps here which aren't very clear (I'm guessing on purpose for novice computer users) - https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
1. I installed eMMC from the play store to make sure my CID started with a 15, it does so I know I'm good to use the hack.
2. I installed both files in the unlock kit (adb and driver setup)
3. Fired up adb, navigated to where I had unlock_n3, and ran through the first part of the code once, reboot my phone, checked that the CID was the developer CID, and then ran the second part of the code three times before it worked
I verified the bootloader was installed correctly by trying to install TWRP through Odin, which worked!
I'm going to try out Jasmine Rom since it's a popular one that is on 5.0. My SD card only showed 30 megs free or something like that, so I formatted it from within android and copied the zip file over and installed the Rom through TWRP. Rom installed just fine, so I did one last factory reset which worked great and I think I'm finally good to go!
If you have any questions or run into any issues feel free to reply here and I'll try to help as much as I can.
Glad it worked out for you in the end.
From making a few mistakes I know that sinking feeling "oh no, what have I done?"
FWIW, the bootloader unlock method (in principle) works from nearly ANY ROM which is rooted - so, you would have saved yourself a bunch of time if you had started with that before you wiped the Alliance ROM. So long as you have root and a CID value that starts with 0x15, you just need root privileges - no need to return to stock and re-root.
(The "in principle" part is that there were several bugs in the "safety checks" portion of the unlocker binary that were sensitive to the OS revision, so you might have to search through the unlock thread to find a version of the unlock binary that is compatible with whatever rooted ROM is on the phone when the unlocking is attempted.)
good luck
PS The AryaMod ROM (w/ phantomOne kernel) is pretty solid - Marshmallow w/ S-Pen apps, too! As with any other dev ROM, there are a few sharp edges, but mostly everything works (except NFC).
.