I need to send my D2 back to Verizon for a replacement (Keyboard isn't registering presses, double letters, etc.)
I had rooted my D2 originally.
I have pushed the stock SFB to the Phone (Which did not wipe out my apps/settings?)
I then ran Root Checker which returned False, and indicated the folders + files did not exist.
I then did a System Reset, and went back to square one. I re-activated the phone (Did not add any accounts though).
Is there anything else I should do before sending it back to Verizon?
Thanks!
Edit:
On a similar note, What's the difference between an Oxidized and Deoxidzed SBF? Same with System-Only and Full.
(I pushed the Full SBF to the phone, but I'm curious what the other ones are)
Lord Ned said:
I need to send my D2 back to Verizon for a replacement (Keyboard isn't registering presses, double letters, etc.)
I had rooted my D2 originally.
I have pushed the stock SFB to the Phone (Which did not wipe out my apps/settings?)
I then ran Root Checker which returned False, and indicated the folders + files did not exist.
I then did a System Reset, and went back to square one. I re-activated the phone (Did not add any accounts though).
Is there anything else I should do before sending it back to Verizon?
Thanks!
Edit:
On a similar note, What's the difference between an Oxidized and Deoxidzed SBF? Same with System-Only and Full.
(I pushed the Full SBF to the phone, but I'm curious what the other ones are)
Click to expand...
Click to collapse
It didn't delete your apps or data? Interesting. You should have gone into a bootloop after the SBF, requiring you to go into the stock recovery to format system/cache....
As far as odex and deodex'd. Stock ROM's have odex files for every system app installed on the phone. Supposedly they are supposed to help speed up the startup time of the phone.
Deodex'd is obviously when the odex files have been removed, usually to save room in /system and also to allow themeing.
Full SBF includes EVERYTHING the phone came with (ROM, Kernel, Bootloader, Radio, etc.)
System only SBF is only the operating system. You would use this if your not worried about going back to complete stock, and just need to reload the OS.
Hope this has helped!
That's what I thought @ Still had data.
(Unless this process requires an SD card to work, I don't have one in my phone because it's dead )
I flashed it twice, once with the phone on and connected via RSD Lite 4.8, I just selected the phone there, picked the SBF and hit start... It restarted the phone into some boot-loader like menu, said it was recieved a SW Update, restarted itself and... nothing change.
So then I did it again but started it in the boot-loader like menu to no difference, so I just did a factory reset.
Thanks @ Explanation though!
You should be good. Just make sure your system version is 2.3.20 (I think that's the latest version, haven't had a d2 for a while). Make sure your boot logo and boot animation are stock, and that you don't have superuser install.
Sent from my HTC GingerBolt powered by the lastest Synergy ROM
They are indeed stock.
I took my D2 into the store today to see what they had to say, I have no idea if this is truthful or if the guy was just making it up to sound smart (Never can be sure after listening to other people talk about your own field )
Said that the missed keypresses + double repeats I was getting was from the phone having overheated at some point, and the keyboard is coming away from the keys a bit (The rubber mat is 'bubbled' a bit in some spots) were indicators of overheating too.
No idea if this is true or not, but he said warrenty should cover it and I just have to call into Verizon so I'll do that.
I'd have to say the phone would have had to get pretty damned hot to do that, but who knows. As long as warrenty will cover it its all good.
Sent from my HTC GingerBolt powered by the lastest Synergy ROM
I agree... The previous owner might have left it in the sun or something... Did that with my DS, turned itself off but it was fine in the end.
Gonna call Verizon tomorrow, too late now. Thanks for the help!
I'm still curious as to why the full-sbf didn't factory reset it though.
is Root Checker an app?
The Albatross said:
is Root Checker an app?
Click to expand...
Click to collapse
Yes. It attempts to do something that requires Root to do. If it fails, it tells you. It then checks if the superuser app exists and if the folders for root exist.
I have the same problem with double entries on the physical keyboard. I've had my phone for a year and I'm pretty sure I have never had an overheat (and definitely have never left my phone out in the sun). I attributed this to CM7 nightlies, but now I doubt that.
Anyone else have this problem?
Sent from my DROID2 using XDA Premium App
Related
Hey folks, I've read through all the JI6 OTA threads here and on the TMo forums and while I've seen a few people guess as to the cause of soft bricks, dosen't seem like anyone has nailed down the actual cause. I'm going to assume I'm not the only person out there with no access to a windows box to run ODIN so knowing what if anything can be done to prep my phone before accepting the OTA (that is sitting in my notification bar as we speak) would be immensely helpful.
So far the two best guesses I've seen are the existence of other update.zip files on SD and removal of bloatware, specifically Media Hub and possibly edited startup/shutdown screens.
Since I've got all these going on, I guess I'm staring down the barrel of a brick. But obviously one of these is easily rectified while the others, not so much.
Aside from those claiming bricks on vigin phones. Can we hear from those who have made mods to their rooted devices and either did or did not experience an OTA brick? I think this info will be helpful to many in sorting out what exactly is going on here.
I have black bar mod, I have naked swype, removed most t-mob app except media hub no change to start up or shut downtried to update. 50 % through it said update failed. Then rebooted fine. But I had an extra update.zip on my sd so maybe that's why. But no firmware now? Maybe I'm sol.
Sent from my SGH-T959 using XDA App
Mine wouldn't complete the update Rooted, most of the bloat removed, had an update on the sd. Was able to get into clockwork after the failed update and am performing a nandroid restore now.
this is great, thank you. beginning to look more like an issue with extra update.zip files than media hub. any successful OTA's with media hub removed prior to accepting the update?
Sent from my SGH-T959 using XDA App
I never uninstalled Media Hub. I have seen a correlation of about 5 people who had ROM manager installed and used that to install Recovery. Whether it be the installation of Recovery or a possible permissions issue with how it generates the update.zip that may have caused my issue.
just a question, why do people remove media hub? Does the application make the phone slow?
iynfynity said:
just a question, why do people remove media hub? Does the application make the phone slow?
Click to expand...
Click to collapse
Because up until now, it was a non-functional app. I didn't remove it, I use LauncherPro so I just removed it from my drawer. I'm still not touching this update. I got my Vibrant used so I would be out of luck if it jacked my phone up and I hate using ODIN. Too much hassle when my phone runs great on Bionix 1.4 as it is.
Wife's phone was toasted by OTA. Stuck at Vibrant screen. Rooted, unlocked, she did have an update.zip, if that turns out to be the culprit. Also had some apps removed, replacement startup animations, and removed shutdown junk.
She was set for always-on WiFi, too.
My rooted Vibrant soft bricked yesterday and I had to flash stock with Odin. I had the (what seems to be infamous) update.zip, removed Kindle, Mobi TV, Avatar Icon, Gogo. I had RyanZAOneClickLagFixV1+ installed but removed it. I also had the EXT2 Tools installed. @ the time of the update I was @ work and had a full charge on the phone. I flashed back to stock last night after work, and I haven't recieved the update notificaiton again...maybe TMo crossed me off some type of "update list"?
There are also different possible symptoms.
In my case the update appeared to have completed its cycle, except the tail end of the download of the new update wnt really fast then the system rebooted. System came back up into the Black Vibrant screen. I could start 'adb logcat' and the system had SurfaceFlinger repeatedly crashing.
Attempts in Recovery Mode after this to reinstall files didn't resolve the issue, reboots would still lead to a crashing SurfaceFlinger.
2 separate users in a thread, 1 had removed Boot Animations + Sounds, I only had removed Sounds.
Quite a few people had Stock Roms + Root, but some with Root didn't have any issues. Only correlation was with Titanium + Rom Manager, which a lot of people would have installed since it's listed in the Tips and Tricks thread. Titanium shouldn't do anything to the system unless you generate a backup Update.zip or install LZO support busybox.
One guess is that ROM Manager and Titanium can create a update.zip file that doesn't have the proper permissions. An OTA update that attempts to overwrite this file may get confused. Simply removing the file in advance may alleviate this issue. Another issue is ROM Manager installs ROM Recovery, which may change how the OTA perceives the phone.
Bionix 1.4...
I was running Bionix 1.4 KK OC/UV yesterday morning... Was a little dumbfounded when I received the update message from Tmo. Figured it wouldn't show w/ modded handset. Delayed install until I could read everything on here about it. Tried installing over Bionix last night just to see, and had no joy. I had removed all crapware, mediahub included. Hit 50%, said flash failed, rebooted and was back to my homescreen in no time. No ill effects to phone except being denied upgrade.
So I Odined back to Stock JFD FW (and wiped device for S&G), rooted, and updated from JI6 tar posted. Flashed perfectly, no ill effects as I've noticed. Reception is improved (for me anyway), and GPS functions similar to Bionix... No real incentive for update, but was curious.
I see Bionix 1.7 updated so it was all for nothing.
Now to play with other stuff...
Cheers
My girl friends phone bricked the other night from the OTA, it's rooted(update.zip) and has the bloatware uninstalled, nothing else like lagfix/roms on it etc.
T-Moible is sending her a replacement phone, which im pretty surprised about. Now since we have to send the old phone back so they can check for damage or anything that would void the warrenty.
We get to keep the external SD card(Avatar), now im sure there is a pretty good chance they will find that its been rooted. So we would have to pay $400 they said if its voided.
Now I can't get this phone to boot into download mode or even mount it, so what should I do? I know about ODIN but have never used it, can it mount the phone?
I got the soft brick and had to flash back to stock via Odin and then I flashed the JI6 tar file from the forum. All is working fine now.
I had root but no update.zip file on the sdcard root, had removed startup an shutdown sounds, had used both ROM Manager and Titanium (with LZO compression turned on), and had removed bloatware including the non-functioning Media Hub.
Next time I'll flash back to stock before doing an OTA update.
I am rooted have Titanium backup, ROM Manager, and clockwork mod. I also had an update.zip but I think it was from OCLF not from another source. My update went fine and I'm running without any problems on the new update.
PepeLasNoches said:
My girl friends phone bricked the other night from the OTA, it's rooted(update.zip) and has the bloatware uninstalled, nothing else like lagfix/roms on it etc.
T-Moible is sending her a replacement phone, which im pretty surprised about. Now since we have to send the old phone back so they can check for damage or anything that would void the warrenty.
We get to keep the external SD card(Avatar), now im sure there is a pretty good chance they will find that its been rooted. So we would have to pay $400 they said if its voided.
Now I can't get this phone to boot into download mode or even mount it, so what should I do? I know about ODIN but have never used it, can it mount the phone?
Click to expand...
Click to collapse
Woo, got it unbricked! finally got into download mode and ODIN saved the day.
this video was helpful for me: http://www.youtube.com/watch?v=AnY7P14JSWQ
^ODIN walkthrough
paxton said:
I'm going to assume I'm not the only person out there with no access to a windows box to run ODIN
Click to expand...
Click to collapse
there is a cross platform tool being developed called 'Heimdall'. It is currently a command line tool and is in beta. however people are successfully flashing their phones using it. It is obviously not a 'one click' solution, so you will have to go find the proper files and type out the command.
It can be found here http://forum.xda-developers.com/showthread.php?t=755265#
If you are the type of person with access to both a windows machine and a linux machine, I suggest you check this out. Testers are needed. Of course you can test if you don't have windows, but it's nice to have Odin as a back up. ;-) just incase....
-p
I had a failed update twice using Odin. It wasn't until I went back to stock T959JFD for the second time and deleted update.zip and all clockwork back ups that it finally worked. Runs perfect with no issues.
Sent from my SGH-T959 using XDA App
Was rooted with OCLF, Captive camera, gps fix, rom manager, titanium backup and add removal. Removed the OCLF and unrooted, ran the update, looked like it got to 100% (not sure cause I looked away and then back at it right before reboot) but said update failed. Got stuck at the vibrant screen blah blah. I'm pretty sure I had an update.zip on the sd, but not 100% on that. After pushing the update with ODIN I have noticed my phone lagging quite a bit.... Thoughts?
Sent from my Rooted Samsung Vibrant using XDA App
So, everyone has heard that team black hat has released the new moto gingerbread for D2 and DX. Has anyone gotten theirs to work properly? I'll list the problems.
1. I literally waited for my phone to actually call out for fifteen minutes after dialing a number and tapping the send button.
2. All around sluggish and slow like honeycomb.
3. Motorola stock launcher will not open. Period. And most blur widgets and actions will automatically shut you out when you try to access them. Sometimes even text messaging!
4. Desk clock takes about three to five minutes to actually show up after placing the phone onto the dock and then three to five minutes for the phone to realize that it's been taken off of its dock.
These are just some that I noticed. Am I doing something wrong or is team black hat's material simply junk? I tried the rooted version and overclock to 1.3 GHz and it still did not work, by the way. So if anyone has some good advice or tips or anything, let me know. And I would like to know if this has happened to anyone else. Thanks!
> Posted using my stock 2.2 Motorola Droid 2, (successfully!) Overclocked to 1.3 GHz.
When you upgraded, did you clear the cache and the data in recovery?
Tappin' and Talkin' with Tapatalk
You know I don't know that I did... Are you running on the team black hat?
I wiped everything and now it seems to be working perfectly. Thanks!
I'm glad to see that you got it running so smoothly, hope your enjoying it
Sent from my DROID2 using XDA App
No. I'm not on Team Blackhat. The instructions are that you clear the cache and wipe the data in the bootloader before applying the update.
Soooo.... Is anyone out there running any GB rom > 2.3.3 4.5.153? If so... How the F* did you do it???
Tried loading the Deodexed 4.5.595 from the STOCK VRZ_A955_2.3.20.sbf flashed phone... and upon reboot, All I got was a string of errors on the boot loader.
I also tried loading 4.5.588 and I can never get past part 1 of the 3 part zips. The beginning of the script looks for an app that should have come with the device (which it can't find) and then proceeds to fail the installation.
I have not tried downloading an accountandsyncsettings.apk (the file it is looking for) and dropping it into the app folder.
Installed multiple 2.3.20 sbf files
Downloaded part 1 of 588 from all 3 mirrors (MD5s are identical on all 3)
maderstocked the phone (I know it was a dx firmware) and cooked the bootloader
All 3 zips were in the root of the SDcard.
4.5.153 is actually working perfectly... I just like to keep things current is all.
robonutz said:
Soooo.... Is anyone out there running any GB rom > 2.3.3 4.5.153? If so... How the F* did you do it???
Tried loading the Deodexed 4.5.595 from the STOCK VRZ_A955_2.3.20.sbf flashed phone... and upon reboot, All I got was a string of errors on the boot loader.
I also tried loading 4.5.588 and I can never get past part 1 of the 3 part zips. The beginning of the script looks for an app that should have come with the device (which it can't find) and then proceeds to fail the installation.
I have not tried downloading an accountandsyncsettings.apk (the file it is looking for) and dropping it into the app folder.
Installed multiple 2.3.20 sbf files
Downloaded part 1 of 588 from all 3 mirrors (MD5s are identical on all 3)
maderstocked the phone (I know it was a dx firmware) and cooked the bootloader
All 3 zips were in the root of the SDcard.
4.5.153 is actually working perfectly... I just like to keep things current is all.
Click to expand...
Click to collapse
As far as I know, .153 is the current working leak for the Droid 2. The Droid X leaks have gone up to .595 I think, but not compatible yet with Droid 2 completely.
Honestly, .153 IMO is the best you're going to get until the OTA for Droid 2 arrives, which should hopefully be sometime soon after the Droid X and Droid X2.
Hello. I looked over all the forums and other site's forums. (Android forums, droid x forums etc...) and finally had to post. Sorry for the trouble.
I have a droid x I got 9/2010, one of the first ones out. Recently on a friend's advice i rooted and uninstalled some of the "bloatware". (NFS demo, Blockbuster, etc...). Then I made the mistake of OTA-ing to GB. You guys probably know what happened. So then I decided to factory reset, which just dug the hole deeper. Now I can't get past the "m" logo unless I go into safe mode. I'm thinking about calling VZ as a last resort
I have purchased a full version of clockwork as well as the dx bootstrap, but i understand that without getting into a normal boot I cannot run those programs to try and change the rom/run recovery.
I tried SBF-ing, as well as reinstalling the bloat, both with no luck. Any other ideas?
Thanks a million,
Danny
Did you do a full sbf? If worst comes to worst, and you have insurance, call verizon and tell them you lost it
Sent from my DROID X running MIUI
Yeah, i'm trying the SBF again, using the Linux instructions in the sticky. (My laptop runs Ubuntu) I still can only boot into safe mode. I'm probably gonna leave it in safe mode for now so I can call Verizon. I may not say i've lost it, maybe that it's broken and I don't want to ship a bag of metal parts through the mail/take to store. I figured I was up a creek, but I thought to check. Thanks!
Whenever you SBF and the phone misbehaves, you should do a factory reset. Did you try that?
Edit: Just reread your post and saw you did try that. Try the SBF again followed immediately by factory reset. Also, try the Droid2 bootstrap instead.
Try the bootstrap? If it's a program I need to run then your advice is moot. I can only get into safe mode, which doesn't allow me to run anything. And now my phone displays no icons, just the top status bar. The screen is blank, i can't switch panels and i can't access any menus. I think it's a paperweight.
Can you get to the bootloader screen? If so you can sbf with 1kds linux cd
Sent from my DROIDX using XDA App
I followed a thread explaining how to "sbf" using Ubuntu. (it's a sticky on this forum) I have Ubuntu Linux on my laptop so i did it. It still got stuck at the "m" logo. I "sbf"-ed again with a different sbf file supposed to be Gingerbread. Still stuck at the logo. I understand since my phone will boot it not considered a brick. (I work in the IT field and have dealt with bricked routers,etc...) But the last two sbf's failed.
I'm still open to suggestions. I may go to a VZ store tomorrow afternoon, but until then i'll try anything since it can't get much worse.
I'd try 1kds. One way or another you should be able to get back to froyo and start over. Just to be sure you are using d2 bootstrap?
Sent from my DROIDX using XDA App
I'm under the impression that this "bootstrap" thing is a program you have to run while in the phone's OS. If so i'm out of luck since I can't. My phone won't boot into safe mode anymore. Now it looks like a normal boot, but there's no icons, just a black background and the upper status bar. (signal, clock etc). i can't get any menus except the sliding unlock screen. The buttons on the bottom do nothing. (Holding HOME displays a screen saying I have no recent programs, ironic since I can't run anything/go anywhere)
So if Bootstrap is something I can load/run without being in the OS, i'm good. But everything I read says otherwise. Thanks either way.
D2 bootstrap is an app. You could run your phone forever without it. It's primary function is allow you to get into cwm to flash things or make a nandroid backup.
Sent from my DROIDX using XDA App
I just discovered that. So it's something I could have installed before it all went south. I'm trying this 1kds sbf thing, but i think it's gonna fail like the last time. I'll post the results later.
Well it lets me into the OS, and it's not safe mode, but I can't really do anything. The screens are still empty. I can get to the apps menu, but touching any of the icons does nothing. If it did i'd just run the z4root and then bootstrap from my SD card. But the icons won't do anything. I'll keep trying things until I can run stuff from my card. I'm determined to get this to work.
You successfully burned the 1kds discount, got your phone into bootloader mode, and ran the disc? What did your pc screen say the moment you ran the sbf?
Sent from my DROIDX using XDA App
You should be able to SBF your phone and then immediately boot it into the recovery menu (hold the Home key while turning on the phone, then press the Search key to get the recovery menu). From there, do a reset, wipe, or whatever it's called. That should get rid of whatever remaining software turds is causing your phone problems. If that still doesn't work, then I'd chalk it up to a hardware problem.
I did burn and run the CD. It didn't say anything special after it ran but i wasn't looking for something special. Now I can't get to the recovery menu. It's still frozen at the logo. I can get into safe mode, sometimes. I'm gonna take it into VZ tonight just to see. But I recently found out I haven't been paying for insurance this whole 11 months i've had it. So my idea of a replacement got more expensive.
Was trying to find out if you got to the "boot baby boot" screen before it did it's thing. Bummer it didn't work.
Sent from my DROIDX using XDA App
Yeah, i think it's a hardware issue so i'll see what Verizon says. Regardless thank you all for helping. I'll give you "thanks" after work today. Rock on!
i wiped everything in cwr...data/cache/dalvik/batt
i then pulled batt and put it back in and booted into moto recovery and wiped data and cache
i then sbf 4.5.596 official
i did the OTA to 4.5.602
at this point am i absolutely 100% stock?
i mean did i need to format /system in cwr to make sure it got it all?
if i am missing something please let me know.
does the procedure above take the phone to 100% factory 4.5.602 in the end?
Lol, sending your phone in 'eh?
And yep, you're stock.
I had to send my phone in twice...
Once I used Maderstock340 and then sbf'ed after to be double-sure.
The second time I just SBF'ed...
Booted into stock recovery and factory reset.
They never said a thing.
BUT...
I don't condone sending a phone in that was broken via something YOU did wrong trying to root/mod/etc.
I had screen problems, for example...not at all caused by root.
That is one reason Verizon hates root users! They get "bricked" phones and assume we're all idiots.
I've had a LOT of hardware related issues with the droid X (ive sent in 5 phones, plus 2 for my girlfriend) every time I maderstocked and sbf'd (sbf never got rid of custom boot animations for me), and sent it in - and I've never had a problem. You should be fine, just dont lie if you actually broke the phone yourself from hax.
While I agree with the overall sentiments of not making warranty claims for screwing your phone up with root/rom, it seems to me that if he's able to all he said he did,
then the phone isn't bricked
Since I installed Aura 1.2.1.0 on my phone the power button has been getting really hot. I just installed Homebase v5 and its still the same thing. So im thinking its not the rom. Any ideas?
That's odd. The bottom of my phone gets hot, but not the power button. If you're on att or even if youre not, I suggest trying to get a warranty replacement.
Sent from my Unlocked CM7 Atrix
http://forum.xda-developers.com/showthread.php?t=1268698&highlight=fingerprint+scanner+hot
someone here said they fixed it by doing a factory reset; i suggest wiping EVERYTHING through fastboot, then clearing data/cache/dalvik in CWM and then reinstalling a stock ROM (fruitcake for example)
I did a clear data, cache, and dalvik wipe. What would be the difference in doing a fastboot wipe?
replace it
replace it b4 your warranty is out. my power button failed. and to many of these scripts require the power button to select options
Odd this happened to a homebase mega build I set my old man up with just last week did a back factory wipe then restored data and no problems so far, I though he left it in the car or sun or something when he said it was the finger print/power button. Even sat down and checked it out couldn't reproduce the problem or guess what happened no fp profile was even set active so. As mentioned above when in doubt replace they just upped the insure deductable x.x the 1st of this month
I got this once
removed the battery and reboot the device .. problem solved
I've rebooted, pulled the battery, got it working off the power cable (doesn't get hot then). Theres a warrant service place by work so ill revert it back to stock and just get it replaced.
I've had random moments when the phone felt like it was heating up towards the bottom, especially using the HKTW 2.3.4 build, but never on the power switch. I'd suggest just get a warranty exchange to be on the safe side. Better replace it now than when your warranty is over.
I know im gonna get flamed but how do I go back to the stock rom? Do I flash fruitycakes or sbf? I've read the threads on reverting back but their didn't seem to be any consistency.
riotburn said:
I know im gonna get flamed but how do I go back to the stock rom? Do I flash fruitycakes or sbf? I've read the threads on reverting back but their didn't seem to be any consistency.
Click to expand...
Click to collapse
fruit cake is the safest way to go back to stock. you can also flash the 2.3.4 gingerbread sbf file with rsd lite, but do NOT attempt to flash back to Froyo if you ever did the Gingerbread OTA update. if you're not sure, then just be safe and never revert back to Froyo.
flashing the gingerbread sbf file with remove your unlocked text on bootloader and revert you to a pure stock state.
So I took it to the warranty repair center and they replaced it no problem. Said shes seen it happen a few times already.