From leak 320. To stock 2.3.315 - Droid X General

Thx to blade765. Doing just as simple as a restore.
http://www.droidxforums.com/forum/d...oll-your-320-dx-back-2-3-151-now-you-can.html
Sent from my DROIDX using XDA App

Works like a charm! I was running the 2.3.320 leak on the 30.04 bootloader, the nandroid brought me back to 2.3.151, factory reset also works for 2.3.151.

Very handy
Sent from my DROIDX using XDA App

I'm surprise not many people are on the leak lol. This Guy got the new ota and then kept the bootloader and other crap to help people downgrade using the newest bootloader keys etc. Pretty cool.
Sent from my DROIDX using XDA App

I would read this before continuing this process of reverting back to 2.3.151
by P3droid:
"There is a lot of bad info and danger going on, if you restore a nandroid you have not reset your phone to 2.3.151 or 2.3.15, what you have done is put your phone's system on the lower system but not the entire firmware. One of the major parts is the kernels which is not backed up or restored with a nandroid, but needs to be exact for a patch to work...be careful..it may work it may not"
You could end up bricking your phone. Just wait for TBH to come out with the fix is my recommendation.

was just passing along since people were having good results with this. for some people that don't wanna wait or so. just waiting for tbh app to notify me lol.

bouchigo said:
I would read this before continuing this process of reverting back to 2.3.151
by P3droid:
There is a lot of bad info and danger going on, if you restore a nandroid you have not reset your phone to 2.3.151 or 2.3.15, what you have done is put your phone's system on the lower system but not the entire firmware. One of the major parts is the kernels which is not backed up or restored with a nandroid, but needs to be exact for a patch to work...be careful..it may work it may not
You could end up bricking your phone. Just wait for TBH to come out with the fix is my recommendation.
Click to expand...
Click to collapse
I just recently saw his twitter post, good thing I made a backup before doing anything. I am back on 2.3.320 and watching the team black hat app

Geeze....here too? Ugh.... this file was NOT meant to allow people to use older sbf's (which is what a lot of people tried to do). It was ONLY meant to make the phone appear to be stock again, for those that had to bring their devices in for warranty, etc. It was not meant for HALF of what people were doing with it.
As for the .340 update, we are unclear on whether that would work without a hitch. I'd LOVE to wash my hands of this, lol. My mistake I suppose. Should have been clearer. P3 brought this up to me, and I went around and updated all the threads I could find, only to think I was done, and stumble upon it here.
Just trying to help, I swear...

Just tested something, thought I would share it here as well:
If you try to install the official OTA from either .320 OR this nandroid, you will fail a fingerprint check that the system automatically does. You will have to upgrade to the newest firmware the same way you upgraded to the leaked version.

Related

Force close loop

Hey. Well, let me first say I've literally spent the past 12+ hours working on my phone. I am exhausted mentally. I searched the forums and I was shocked to see that only one topic came up about it and it wasn't even about force closes. It was a 100+ page CM post.
I rooted for the first time today using a method posted on these forums + extra info I found about adding the OTA radio leak, and installed UV Hydra kernels. I got Rom manager and flashed Skyraider 2.2 Sense. I booted a few times too and all was good. I swear I thought I was doing it all right taking it slow, rreading all of the info over and over. A true noob. Everything was all cozy until I got my old apps and tried to make a backup with Titanium.
It's so cliche to say it but I need serious help. I don't know what to do and I'm near tears after all this work. I have dozens of force closes going on immediately after boot and even thereafter. At one point it asked me to reset up the phone. I can't run any app because they force close immediately.
I don't know if it's the Rom, something else, or me.
I know this is long winded. Please forgive me. And if this is in the wrong forum section, please forgive that too.
Do a full wipe in recovery and flash the rim and kernel again...but upon restoring, only restore downloaded apps, not system apps.
I remember when it took 12+ hours just to get root (for some people anyway) those were the days.
Sent from my ADR6300 using XDA App
lilsaphyre said:
Hey. Well, let me first say I've literally spent the past 12+ hours working on my phone. I am exhausted mentally. I searched the forums and I was shocked to see that only one topic came up about it and it wasn't even about force closes. It was a 100+ page CM post.
I rooted for the first time today using a method posted on these forums + extra info I found about adding the OTA radio leak, and installed UV Hydra kernels. I got Rom manager and flashed Skyraider 2.2 Sense. I booted a few times too and all was good. I swear I thought I was doing it all right taking it slow, rreading all of the info over and over. A true noob. Everything was all cozy until I got my old apps and tried to make a backup with Titanium.
It's so cliche to say it but I need serious help. I don't know what to do and I'm near tears after all this work. I have dozens of force closes going on immediately after boot and even thereafter. At one point it asked me to reset up the phone. I can't run any app because they force close immediately.
I don't know if it's the Rom, something else, or me.
I know this is long winded. Please forgive me. And if this is in the wrong forum section, please forgive that too.
Click to expand...
Click to collapse
Wow, That sounds like a seriously horrific days. Not sure if I can help, but i'll sure as hell try to. Can you verify that you Baseband Version is 2.05.00.06.11?
Did you create a nandroid backup of before you flashed any of the kernels? If you did I would restore that backup as I know some people have had issues running the old .29 hydra kernels with 2.2 roms. Or was this the new .32 kernels you flashed?
If you did not create a nandroid backup I would recommend flashing the leaked OTA from 8/1 located here, http://forum.xda-developers.com/showthread.php?t=742242, this is a leak of what will be close to the stock 2.2 htc will release in the near future. Remember to wipe data, wipe cache, and wipe dalvik cache(located in "advanced" of recovery.) As soon as you flash that and can verify it is working create a nandroid backup of it before you add any apps, I would recommend signing into your gmail, testing camera and camcorder, make a call, sending and receiving both an sms and mms, 3g data check, and then creating the nandroid when you see those are working. After you create that nandroid then start installing apps. Hopefully this can help you out a little bit. If you have any questions, you can pm me and i'll do my best to try and help you out more.
jdkoreclipse said:
Indeed that does seem horriffic. I think he restored system apps from ti backup tho. Ive never saw anything like this that wasnt ti backup related.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I didn't see you response until after I posted and you are most likely correct. I remember now, when i tried to restore system apps when i had a droid eris, that was not a fun day. Hopefully it's an easy fix and a learning experience, easiest way to learn is to make a mistake. Even though my answer is most likely not the solution to his problem, IMHO it's essential to always keep a nandroid of stock on your sdcard at all times, just in case.
Wow I see alot of info and I'm going to work with some of it but let me add this before I start dinking around today.
Right after I posted last night, I sat on the edge of my bed and had a thought. I had made a nandroid backup when I had almost every app back on my phone. The only ones I ones I didn't have when I got stuck were, Shoot me, Titanium backup, Adfree Android, and Tasker. Tasker being the only one I had before root. The others I picked up after.
SO! I told the phone to use the backup I had and I passed out to sleep.
I'm up now lol and thankfully I'm a stay at home mom so I can mess with this.
The backup made it a working phone again! Which is good. And this morning I had a second thought. When I opened Titanium backup last night, I got a message at the bottom of my screen that said Titanium had set itself up right... but it wouldn't go away. It kept looping itself. I thought it was just a fluke. Oh god... and NOW to think about it, that's WHY I rebooted in the first place. BECAUSE in the midst of it being weird, I tried to do a backup OMG. I wonder...
My Software says
Baseband 2.05.00.06.11
Kernel has a 32 in it
Alright I'm doing this nice and slow making backups along the way.
The only quirky thing that has happened is Titanium backup started spamming me again that it had been given superuser permissions so once again I had to reboot but this time it came up. Slow.... but it came up.
I guess what I"m trying to say is that I don't have a clue now what caused it.
OH! And my kernel is a 32 that came with the rom? The UV one I forgot to put on lol. It's on my SD card but I hadn't installed it. That one is a 29.
I just found a post on Android Forums where 2 people has this happen to them last night as well on Incredibles. They were without root.
If they were without root it could be a phone defect, I was going to recommend selecting fix permissions from rom manager.
EDIT: If ur running froyo try to only use .32 kernels. New kernels r up on Hydra website that are .32 check those out
Sent from my ADR6300 using XDA App

[Q] Can you remove Droid X Bootstrap?

Any help is appreciated, I'm still fairly new with Android, but trying to learn my way around.
When the OTA update for 2.2.1 came out, I decided to do a factory reset because I'm just picky like that, and I like to be fresh coming out of OTA updates. Prior to the factory reset, I was running stock 2.2, though I was rooted using the manual (D2) method through adb, I had bloat frozen with Titanium Backup, and I had Droid X Bootstrap installed.
I unfroze the bloat and did the 2.2.1 update prior to factory reset. I did not unroot prior to the OTA. After the OTA I did a factory reset. I expected the bootstrap to go as well. It didn't, and I noticed immediately because I was booting into its recovery every other reboot because I was no longer rooted.
I still had the superuser icon (ninja) in the app drawer, however was no longer rooted of course, so I loaded z4root and let it "unroot" me, and then let it root again, which fixed the Bootstrap recovery issue.
Here's my problem. Obviously the factory reset did not wipe everything because bootstrap was still trying to load. My phone is definitely more sluggish than it was prior to the factory reset. Different types of screen lag are very noticeable and the phone really lags later in the day if I don't reboot. I loaded less apps after the reset than I had prior to, but otherwise did nothing different. I want to try to remove the bootstrap too, as well as anything residual to try to figure this out, even if I do have to factory reset again, because it's definitely not stable the way it is. Is it possible to remove it, and how so?
I'm aware that this may not fix the problem, and to me it doesn't even make sense that it would, but I definitely feel something "off" here and for my own peace of mind I'd like to remove it at least for now just to see. I've done factory resets before and the phone always feels much snappier once it's back up and running. This time it's worse than when I started.
Any assistance would be greatly appreciated.
You would have to flash a stock sbf. Correct me if I am wrong but I think that stands for system boot file. That should take care of everything. I am sure u can find the thread on the forum on how to do it. Just to mention I think that all the boot strap does is hijack your normal boot process by interrupting it allowing u access. It doesn't actually replace the boot process.
Sent from my DROIDX using XDA App
Info on the bootstrapper can be found here:
http://www.koushikdutta.com/2010/08/droid-x-recovery.html
Basically it replaces the logwrapper.bin file which gets executed very early in the boot process. This allows bootstrapper to control the rest of the boot sequence.
To *just* remove bootstrapper, I think there is a backup of the original logwrapper executable stored in /system, so you could just replace the exploited version with the original.
However, if you are having issues, I would suggest you just go ahead and flash back to complete stock:
http://rootzwiki.com/index.php/Main-Page/Droid-X-Full-2.2-SBF.html
Make sure you are still on the 2.3.15 version before using this. Once you take the OTA (to 2.3.340) I don't think this SBF will work any longer.
So the sbf flash method wont work if u took the update?
Sent from my DROIDX using XDA App
sorry to hijack this thread. But I am having major issues with bootsrap. I accidently moved it from my sd card to internal storage. How do I move it back. It wont allow me.
crxin said:
So the sbf flash method wont work if u took the update?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
The .340 update "upgrades" your bootloader to 30.04. I've read that the 2.3.15 SBF will not work with this bootloader.
There are some SBF files produced by Team Black Hat (at Leaked 2.3.320 and patch files to put you to 2.3.340), but I've not used them.
I think you can find more info on those at mydroidworld (or you can support TBH by buying their app in the marketplace and downloading direct from there)
jaynyc22 said:
sorry to hijack this thread. But I am having major issues with bootsrap. I accidently moved it from my sd card to internal storage. How do I move it back. It wont allow me.
Click to expand...
Click to collapse
I'm not sure what you mean?
Try uninstalling from Manage Applications and re-install?
Do you mean the DroidXBootstrapper UI or the logwrapper exploit?

I just rooted my N1 for the first time

OK, congratulate me!! Thanks. I did it on the first try, no issue or hiccups what-so-ever.
Now for the info. I'm not sure that anyone will be interested, but I'm guessing other people in my position at least might be.
I'm very experienced with computers, but not working directly with rooting/unlocking devices. But I would say anyone who reads up a bit and can follow directions properly could pull it off pretty easily.
So I run 2.2.2, and I used superoneclick 1.6.3.
After opening superoneclick, I switched it from psneuter to rageagainsthecage. I had no idea if I was supposed to do this, but I read all about rageagainstthecage, and never heard of psneuter.
I had my phone connected to my PC, and I left my SD in the phone, but I unmounted it in settings. I have used ADB before, so I knew the drivers were installed and working, and I hit the button root.
After reading this site, http://forum.xda-developers.com/showthread.php?t=803682, I started with debugging off, and turned it on as it said. I then turned it off, but didn't get a chance to turn it back on and off and on, so I just turned it back on (debugging) when it got to "Waiting for device" for the second time.
That was it! It asked to test and see if root was in fact accomplished, and it was. I then installed setCPU (which is basically the only reason I wanted to do this) and as far as I can tell it seems to be working fine.
I have been reading a lot about this for the past few days, but the actual procedure only took a couple of minutes. Keeping in mind, of course, that I already had ADB and drivers working.
Nothing was wiped off my phone, which surprisingly was hard to confirm on the web. I did read somewhere that only unlocking wipes data, but still, you never know.
I hope this helps anyone else who is new and unsure of the process, and I'd be happy to answer any other specific questions based on what I have learned of the last week or so. I know that people hesitate to ask questions in case they have already been asked lots of times, but are buried and hard to find (because that's the position I was in ).
Thanks for posting your "rooting" experience. I'm sure there are people that will find it helpful.
I think when I did mine, it was something along the lines of:
fastboot-oem-unlock
fastboot flash recovery <whatever>
reboot into recovery and flash rom
Other than the ability to install custom ROM's I've yet to see a huge deal in rooting my phone. Anyone care to tell me what I can do with a rooted N1 that is a must have? So far I tried to change some fonts, which didn't work, and discovered that I have to install a custom ROM to change the color of the notification bar, and I can't make the default Google music and news widgets slightly transparent. So educate me, what's the huge deal with rooting, aside from a custom ROM?
Set cpu of course like being said. I remember the first time I rooted my phone was universal androot it was a breeze. Then I lost root and use super one click to gain out back. Root really easy as well
Sent from my Nexus One using XDA App
- Backup application, like MyBackup, can backup your app data(including game save...) if your device is rooted.
Hi N1 owners.
I also just root my N1 with superoneclick 1.6.3
After that I flashed CM 6.1.1 and yesterday I tried CM7. Everything has worked fine for me so far, but I have some questions, I hope someone can answer.
1/Can I just flash random roms on top of each other, like i did from cm6 - cm7?
2/ Can I always restore backups, nomatter what rom I come from or to?
3/ when/if official GB come out, can I flash a stock rom and get the OTA update right away?
Sorry, if I ask silly questions ..
Built in trackball colors, call blocker, hide frequently called list in the favorites tab, remove unnecessary apps, tmobile wifi calling, notification bar power toggles, trackball wake and unlock, quiet hours, themes, etc., etc., etc. Just off the top of my head. Oh, and Gingerbread!!!
Sent from my Nexus One using Tapatalk
Some apps want to bypass the home screen "5 second rule" like widget locker, you need root. I setup a widget to reboot (nice!).
brettbellaire said:
...I did read somewhere that only unlocking wipes data, but still, you never know.
Click to expand...
Click to collapse
Unlocking the Bootloader wipes data, rooting does not. This is probably what you read.
offenberg said:
Hi N1 owners.
I also just root my N1 with superoneclick 1.6.3
After that I flashed CM 6.1.1 and yesterday I tried CM7. Everything has worked fine for me so far, but I have some questions, I hope someone can answer.
1/Can I just flash random roms on top of each other, like i did from cm6 - cm7? Yes you can. Often if the ROM is the next version in a series, you can flash without wiping data or cache, but some ROMs require you to do this first.
2/ Can I always restore backups, nomatter what rom I come from or to? A Nandroid backup can be reinstalled from any ROM, or even just from Recovery if there is no ROM.
3/ when/if official GB come out, can I flash a stock rom and get the OTA update right away? Yes. Either restore your stock ROM Nandroid backup or a passimg.zip.
Sorry, if I ask silly questions ..
Click to expand...
Click to collapse
offenberg said:
Hi N1 owners.
I also just root my N1 with superoneclick 1.6.3
After that I flashed CM 6.1.1 and yesterday I tried CM7. Everything has worked fine for me so far, but I have some questions, I hope someone can answer.
1/Can I just flash random roms on top of each other, like i did from cm6 - cm7?
2/ Can I always restore backups, nomatter what rom I come from or to?
3/ when/if official GB come out, can I flash a stock rom and get the OTA update right away?
Sorry, if I ask silly questions ..
Click to expand...
Click to collapse
1. As a rule, if you are going from 1 ROM to another totally different ROM, it's always a good idea to wipe. It only takes a few seconds to sign back in to everything. You can bypass immediate sign in and activate wifi if you need it.
2. Nandroids can be reinstalled anytime. However, a nandroid does not contain your HBOOT and Radio. So if you updated those to use a specific ROM, they would stay in place with the nandroid restore.
3. When GB does finally make it out to our specific device, there is no way you would get an OTA before the ROM devs here had you up and running.
***Also note, the 1-click root tools may or may not work right away with the OTA 2.3. So to anyone that rooted using those tools and unrooted to hurry up and get an OTA, you may be stuck on stock until it gets fixed.
Know-Fear said:
1. As a rule, if you are going from 1 ROM to another totally different ROM, it's always a good idea to wipe. It only takes a few seconds to sign back in to everything. You can bypass immediate sign in and activate wifi if you need it.
Click to expand...
Click to collapse
I agree, do a full wipe if it's a new ROM. Titanium Backup is a great way to get all of your apps and data back after installing the new ROM.
bigmout said:
I agree, do a full wipe if it's a new ROM. Titanium Backup is a great way to get all of your apps and data back after installing the new ROM.
Click to expand...
Click to collapse
So what do you lose (if anything) when flashing a new ROM if you backup and do things the right way?
Another question would be if you just flash a new kernal do you lose any/all data?
brettbellaire said:
So what do you lose (if anything) when flashing a new ROM if you backup and do things the right way?
The only thing you'd lose is the old rom
Another question would be if you just flash a new kernal do you lose any/all data?
Click to expand...
Click to collapse
Nope
Sent from my Nexus One using XDA App
kmiloco49 said:
Nope
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Interesting... Thanks!
@ brettbellaire
I've rooted before, and lost root when ota's came. I've rooted again using superoneclick, and am contemplating cm7. But I feel very cautious about flashing a different rom, I'd cry if I bricked my phone. However, I'm probably going to do it during the next week (unless gingerbread ota arrives).
Andy
Sent from my Nexus One using XDA App
Hmmm, I have been anxious for GB too.... but I'm not sure it's worth it. I don't think it's such a big update. I don't think there's too much of a danger of brinking these days.
I have been contemplating doing what I have to to overclock, see what kind of a difference that makes...
bigmout said:
I agree, do a full wipe if it's a new ROM. Titanium Backup is a great way to get all of your apps and data back after installing the new ROM.
Click to expand...
Click to collapse
I am a newbie to root. Can Titanium Backup restore the paid apps? because some apps require online verification with Google at the first time of use.
Also, Z4root does not work on my N1. I want to use superoneclick but where can I find the driver for my win7? thanks
unroot
is it possible to go back and unroot the phone? i.e. hide the padlock during phone startup ..I am using N1 ForYo 2.2.2..Thanks
zmalach said:
is it possible to go back and unroot the phone? i.e. hide the padlock during phone startup ..I am using N1 ForYo 2.2.2..Thanks
Click to expand...
Click to collapse
If you see the padlock, you've got an unlocked boot-loader. This can't be re-locked.
Sent from my Nexus One using XDA App

[REQ] Nandroid backup request (offering cash)

Just wondering if anyone who's flashing and rooting could please do a backup and upload it somewhere. Myself and a couple others have accidentally partitioned our internal SD incorrectly causing a catastrophic touch screen issue.
I'm hoping it'll have the properly partitioned SD storage because I'm having difficulty doing it manually. If someone could upload this it'd be hugely appreciated!!!
BUMP!!!
Can anyone please provide me with a Nandroid backup using Tenfar's recovery??? I can throw some money once I get my Paypal sorted out. I'm desperate, fellas!
Can someone please help? I'd like to try anything I can to get my phone working this weekend. It's been an entire week without my Atrix.
bongd said:
Can someone please help? I'd like to try anything I can to get my phone working this weekend. It's been an entire week without my Atrix.
Click to expand...
Click to collapse
Im relatively new to android...is this backup you are speaking about a TB backup. Or what method of backup are you looking for?
Sent from my MB860 using Tapatalk
You actually need to be rooted and have Tenfar's custom Recovery menu. In there it has an option to do a Backup.
If you're new it may be too engaging but I appreciate the offer nonetheless. If you could help, it'd be great. If it's too much trouble, I thank you anyway!
yeah what does the nandroid backup...back.. up? the apps?
What I'm HOPING and PRAYING for is that it'll also copy something in the internal SD which was partitioned due to my stupidity. dev/block/mmcblk0p18 is what that is in particular.
I tried manually formatting and partitioning it but I'm unable to do so. Fastboot freezes and Early USB Enumeration goes by so quickly I can't run the commands that I need through ADB. And I don't even know if that'll work because I made a script that executes the commands and I get weird errors. I'm far from an expert and monkeyed around too deeply where I shouldn't have.
About 4-5 others are reporting the same problem. The ****ty thing is that I'm in Canada and it'd be a huge pain to send it to Motorola. They're giving me a lot of grief and I've had to put up a big fight. Waiting to see if they'll send an RMA because I may need to send it in. When I get it back I might sell it and buy a Bell Atrix because I live in Canada and if something bad happens, it'll be easier to send to Bell or Motorola Canada.
from what i understand you have to have an unlocked bootloader to backup or restore using a nandroid backub
Maybe I'm using the wrong terminology then.. just need a backup from Tenfar's customer Recovery. I don't even know if it'll work but I'm out of ideas.
I'm at least thankful that the Xperia X10's bootloader was cracked. I forgot to send a replacement back to Rogers and I phoned them asking if I could use it for now. They thankfully said yes because they forgot to charge me for it lol... it's got some really great ROMs, but looking at this beautiful, mangled Atrix makes baby Jesus cry!
i can do that but im wondering why you dont try SBF file?? should work better than Backup
zen kun said:
i can do that but im wondering why you dont try SBF file?? should work better than Backup
Click to expand...
Click to collapse
i was just wondering the same thing... it also be more stable as nandroid restore are not so good on some phones and im guessing especially on a locked bootloader one.
also a nandroid backup would also restore some else's settings and information on your device....
Ronaldo_9 said:
i was just wondering the same thing... it also be more stable as nandroid restore are not so good on some phones and im guessing especially on a locked bootloader one.
also a nandroid backup would also restore some else's settings and information on your device....
Click to expand...
Click to collapse
I've already tried the SBF files but it doesn't do anything to the internal SD. I need an actual backup because the user settings are exactly what I'm looking for. Normally you'd want a fresh flash from stock but I hope you now understand why I'm asking this constantly.
Flashing to stock was naturally my first step. Unfortunately it had failed. About 5 others reporting the same problem.
bongd said:
I've already tried the SBF files but it doesn't do anything to the internal SD. I need an actual backup because the user settings are exactly what I'm looking for. Normally you'd want a fresh flash from stock but I hope you now understand why I'm asking this constantly.
Flashing to stock was naturally my first step. Unfortunately it had failed. About 5 others reporting the same problem.
Click to expand...
Click to collapse
What maybe you could do is? go into tenfars cwm recovery go to mounts and storage and format the internal sdcard and system and boot and data. This is safe as far as I know and me and tenfar have both done this.I literally formatted every single thing in the option menu. just to see if I could do it. Which was stupid but I was curious and used to do that before I installed new roms on my old backflip all the time! Also might wanna do a factory reset through cwm and clear dalvik cahe as well for good measure. Now after you format all that. reboot system which will send you in a boot loop/wont boot past first screen. Pull the battery and unplug usb cable from charger. Then reboot and enter rsdlite mode by holding volume up and the power button. Now just flash your 4.1.26 sbf file through rsdlite 5.0
As long as you flash back to retail 4.1.26 afterwords using rsdlite 5.0 that should put everything right! As I have done this and my phone is working normal.
I better put one of them warnings here though anyway lol
Disclaimer: You are doing this at your own risk! I am not responsible for any damage you do to your phone.
(^Yeah I think that covers it)
Gutterball said:
What maybe you could do is? go into tenfars cwm recovery go to mounts and storage and format the internal sdcard and system and boot and data. This is safe as far as I know and me and tenfar have both done this.I literally formatted every single thing in the option menu. just to see if I could do it. Which was stupid but I was curious and used to do that before I installed new roms on my old backflip all the time! Also might wanna do a factory reset through cwm and clear dalvik cahe as well for good measure. Now after you format all that. reboot system which will send you in a boot loop/wont boot past first screen. Pull the battery and unplug usb cable from charger. Then reboot and enter rsdlite mode by holding volume up and the power button. Now just flash your 4.1.26 sbf file through rsdlite 5.0
As long as you flash back to retail 4.1.26 afterwords using rsdlite 5.0 that should put everything right! As I have done this and my phone is working normal.
I better put one of them warnings here though anyway lol
Disclaimer: You are doing this at your own risk! I am not responsible for any damage you do to your phone.
(^Yeah I think that covers it)
Click to expand...
Click to collapse
JUST got your PM as I was clicking this thread. Thanks, broski.
I've got nothing to lose. It's easy enough to recover from soft-brick. I'll give it a shot right now. Wish me luck!
*** UPDATE ***
Still no dice. Bummer.
bongd said:
JUST got your PM as I was clicking this thread. Thanks, broski.
I've got nothing to lose. It's easy enough to recover from soft-brick. I'll give it a shot right now. Wish me luck!
*** UPDATE ***
Still no dice. Bummer.
Click to expand...
Click to collapse
mmm weird..
IMO if sbf dont help i really doubt a recovery will....
perhaps i highly recommend if someone do this, create a new account of gmail and flash a sbf file since the OP will have all sensitive data as email,contacts and so on as previous post say
zen kun said:
mmm weird..
IMO if sbf dont help i really doubt a recovery will....
perhaps i highly recommend if someone do this, create a new account of gmail and flash a sbf file since the OP will have all sensitive data as email,contacts and so on as previous post say
Click to expand...
Click to collapse
That won't work either. I have reasons for wanting a backup versus a new SBF flash as stated multiple times.
I have a nand if you still need one
Sent from my MB860 using XDA App
sgtmedeiros said:
I have a nand if you still need one
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Your motoblur account information is stored in plaintext and your google contact information is also in a nandroid backup. Be weary.
knigitz said:
Your motoblur account information is stored in plaintext and your google contact information is also in a nandroid backup. Be weary.
Click to expand...
Click to collapse
I was not aware of this and was so focused on correcting the challenge that this was a complete oversight. On second thought, I don't want to compromise anyone's security.
I had in mind a fresh backup, preferably for AT&T's 1.2.6 SBF but it's a bit of trouble and a lot of space. I retract my request due to the amount of work involved and that I don't want to compromise anyone's security in case they don't clear their user details, etc.
Thanks for pointing that out, knigitz. I think ADB access in the Recovery is our best bet. Crossing my fingers.
bongd said:
You actually need to be rooted and have Tenfar's custom Recovery menu. In there it has an option to do a Backup.
If you're new it may be too engaging but I appreciate the offer nonetheless. If you could help, it'd be great. If it's too much trouble, I thank you anyway!
Click to expand...
Click to collapse
Ill help you with your backup if you can help me root and flash the gladix rom on mine.
Sent from my MB860 using XDA App

[Q] Stuck on 4.1.2.6--Can Somebody throw me a bone?

Just as a precursor and in advance--I apologize if I missed a thread on this topic here. I searched a number of different times and ways but didn't find any so hopefully I am speaking for others with the same problem with this newly generated one!
So I got a brand new Atrix about 2 days ago and just like every Android I get, I came straight to XDA right after initial boot and a little play-around with it to get the rooting process started . I downloaded the Gingerbreak .apk (I believe it was v 1.0) and rooted with no problem. However, later on while checking the phone out a little more, I stumbled upon the "System updates" section under the "About phone" category in the settings and out of curiosity (and not knowing anything about software updates etc.) thought I'd check it. Well it detected that the 1.57 update was available as the phone obviously came stock with the 1.26 to begin with. So I went and ahead, downloaded it and then attempted an install.
It would get about...oh, I'd say 40% of the way through the install process and then fail (I'm guessing this was the case anyway as the arrow coming out of the package pointing to the android suddenly just turned into the dreaded "!". So I just pulled the battery and rebooted and thought, "Hmm, well it's probably because I've got it rooted--must be something in the system files that's preventing it from pushing the update through successfully."
Next, I figured I'd try a different route and push the update through RSD Lite 5.0. Followed all instructions to a T and just about the same thing happened during install THAT way (i.e. Process failed about 40% or so of the way through).
Following that, I searched to see what unrooting methods were available following the previously botched attempt at a solution. I found a thread mentioning that v 2.0 of Gingerbreak had an unroot option>followed instructions>unrooted (no detected problems there)>attempted to push OTA update again and no dice. Same issue again. I'm both beginning to run out of solutions and am exhausting myself as I usually only have time to do this late at night when I should probably be sleeping (pssh, who needs that, right? )
Anyway, if someone who has experienced similar issues or knows what is going on here could point me in the right direction it would be GREATLY appreciated as I feel like I've got a phone that's not working to it's full potential (after having read what all the updates do)! Thanks a TON in advance for any help!
Save yourself some frustration..
Backup your stuff using titanium backup
Download the stock 1.2.6 SBF
-flash it using RSD lite
-root your phone using gladroot
-update to .57 from your phone (system updates)
-run afterupdate.bat
-update to .83 from system updates again
-run afterupdate.bat
Done.
Restore from titanium backup (batch restore is your friend..)
Sent from my MB860 using XDA App
FYI - you don't need to run afterupdate between 157 and 183 upgrades. Worked fine for me twice.
Sent from my MB860 using XDA App
nsaia said:
FYI - you don't need to run afterupdate between 157 and 183 upgrades. Worked fine for me twice.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I figured that from the part of the script that asks if you intend to update. I did it anyway, it was reassuring to see I still had root before the upgrade lol. Good to know for next time though
Sent from my MB860 using XDA App
Save yourself some frustration..
Backup your stuff using titanium backup
Download the stock 1.2.6 SBF
-flash it using RSD lite
-root your phone using gladroot
-update to .57 from your phone (system updates)
-run afterupdate.bat
-update to .83 from system updates again
-run afterupdate.bat
Done.
Restore from titanium backup (batch restore is your friend..)
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Thank you kindly sirs (knlgSeeker and nsaia) for the help. Cool. Sounds like a plan. I've already got a backup w/ Titanium on my phone actually (it's always something I keep a copy of on the trusty ext SD) so that should be good to go. Do you by chance have the links for the SBF's you were referring to? I think I might already have the 1.57 one (as I had mentioned in the original post) but I'm sure it wouldn't hurt to post it again. Thanks again in advance!
jz4467 said:
Thank you kindly sirs (knlgSeeker and nsaia) for the help. Cool. Sounds like a plan. I've already got a backup w/ Titanium on my phone actually (it's always something I keep a copy of on the trusty ext SD) so that should be good to go. Do you by chance have the links for the SBF's you were referring to? I think I might already have the 1.57 one (as I had mentioned in the original post) but I'm sure it wouldn't hurt to post it again. Thanks again in advance!
Click to expand...
Click to collapse
No problem..here's all the info/ links you should need:
http://forum.xda-developers.com/showthread.php?t=991072
Just remember, 1.26 is the only one you will need to flash from RSD.. Just do an OTA update for .57 & .83
Sent from my MB860 using XDA App
No problem..here's all the info/ links you should need:
http://forum.xda-developers.com/showthread.php?t=991072
Just remember, 1.26 is the only one you will need to flash from RSD.. Just do an OTA update for .57 & .83
Click to expand...
Click to collapse
Cool. I had actually gone ahead last night and eventually found it myself. Was good to come back though and get some reaffirmation as to whether or not the location I had found and instructions were the correct ones. After clicking on the link you provided I found that it was the exact same thread/post that I had used to do it. So thank you again!
I also had some interesting info to pass along as well. I just thought after flashing 1.2.6 again from RSD Lite that I'd go ahead and just do the OTA updates for .57 and .83 to make sure that they worked and they did. Obviously my concern while going ahead and skipping to those steps was whether or not I'd still be able to get root and I'm happy to report that I was still able to get root after doing so. I just sideloaded the Gingerbreak 2.0 app and it rooted no problems at all! Thanks again for your help guys!
Another random question to throw out there (I figured I might as well just post it in here to see if there's an easy fix: I've got ClockworkMod Recovery on here and I was trying to flash the recovery for the Atrix. However, when the "Confirm Phone Model" comes up, I don't see/find an option for the Atrix. Are we supposed to use a different phone model's version of recovery? Thanks again in advance for any help!
jz4467 said:
Cool. I had actually gone ahead last night and eventually found it myself. Was good to come back though and get some reaffirmation as to whether or not the location I had found and instructions were the correct ones. After clicking on the link you provided I found that it was the exact same thread/post that I had used to do it. So thank you again!
I also had some interesting info to pass along as well. I just thought after flashing 1.2.6 again from RSD Lite that I'd go ahead and just do the OTA updates for .57 and .83 to make sure that they worked and they did. Obviously my concern while going ahead and skipping to those steps was whether or not I'd still be able to get root and I'm happy to report that I was still able to get root after doing so. I just sideloaded the Gingerbreak 2.0 app and it rooted no problems at all! Thanks again for your help guys!
Another random question to throw out there (I figured I might as well just post it in here to see if there's an easy fix: I've got ClockworkMod Recovery on here and I was trying to flash the recovery for the Atrix. However, when the "Confirm Phone Model" comes up, I don't see/find an option for the Atrix. Are we supposed to use a different phone model's version of recovery? Thanks again in advance for any help!
Click to expand...
Click to collapse
All's well that ends well! Not sure what exactly you're trying to flash, but I use Tenfar's CWM..
http://forum.xda-developers.com/showthread.php?t=1019143
It's pretty straightforward, you can boot to recovery in 2 steps
Sent from my MB860 using XDA App
All's well that ends well! Not sure what exactly you're trying to flash, but I use Tenfar's CWM..
http://forum.xda-developers.com/show....php?t=1019143
It's pretty straightforward, you can boot to recovery in 2 steps
Click to expand...
Click to collapse
Sweet. I think I had run into that same thread earlier on (and had actually already installed that same app on my Atrix) and had completely forgotten about it. So thank you for refreshing my memory on it and directing me to it again! Thanks for all your guys' help in general as well!
Got another question for ya: How do you delete all the bloatware off of the phone? I've got Root Explorer and what I usually do is just navigate in like fashion: system>app>and then just delete any of the bloatware apps. However, I've found with this phone that there isn't a single one of the at&t apps found inside this "app" folder. I HAVE found them in the following way however: system>preinstall> BUT there's no way to change how the files found within are accessed (i.e. mounting them as r/w rather than r/o) and so as a result there is no way to delete them. The option to mount the files as r/w is simply not there. Any info on this would be great! Thanks in advance again.
By the way, if you have any questions concerning the Samsung Captivate, I'm pretty knowledgeable about that phone--gained quite a bit of knowledge during the time that I owned it which was probably about 6 months.

Categories

Resources