Related
I have searched a bit and can't find what I am looking for. I have a rooted tbolt and not new to rooting but not familiar with the d2global(my son's phone). So I rooted via the 4z method and everything went smooth. Downloaded cw bootstrap and loaded liquid gingerbread 2.5. I am very upset as I forgot to make a backup prior. Anyway I did a factory reset, cache wipe, etc.. and loaded the rom. Now there is no service and I am stuck in aiplane mode. I am hoping there is a simple fix. Any help is appreciated.
Thanks!
Nevermind, figured it out Loaded CM7, must have been something within the liquid rom.
there is no liquid rom for the d2g, if you try installing a rom for the d2 (which i assume liquid is for) your radio wont work, which is why its always in airplane mode.
cm7, on the other hand, is made for the d2g.
onedrops said:
I have searched a bit and can't find what I am looking for. I have a rooted tbolt and not new to rooting but not familiar with the d2global(my son's phone). So I rooted via the 4z method and everything went smooth. Downloaded cw bootstrap and loaded liquid gingerbread 2.5. I am very upset as I forgot to make a backup prior. Anyway I did a factory reset, cache wipe, etc.. and loaded the rom. Now there is no service and I am stuck in aiplane mode. I am hoping there is a simple fix. Any help is appreciated.
Thanks!
Click to expand...
Click to collapse
i did the same thing, and now i'm stuck, i tried to do a recovery and somehow it won't let me i tried holding the power and volume down to try to do a manual recovery, cause i did a backup so i can restore, unfortunately i can't get to that recovery...if i knew liquid 2.5 was bad i shouldn't have installed that POS...any help will be good, thanks
Your baseband is FUBAR, so you need to reflash an SBF.
Instructions here.
Finding the images and RSDLite with Google should be easy enough; if not (and only in that case), PM me.
JFYI: there is no way to get to CWM if you cannot boot the OS to at least a bootloop after the point where adb shell becomes available.
Thank you
Thanks, i will def give it a try...i can get to bootloader by holding power button and both volume button...i just didn't know what to do from there...
The problem i'm having is :
phone does boot up running liquid 2.5, problem no service stuck in airplane mode
all function of the phone works just can't make calls etc without service
i do see the backup files when i open file manager, just can't get it to open up, hopefully that bootloader thing works,
if rom manager was working that would help solv e everything cause i would be able to restore, but the app is not there when loaded liquid, usually when you ask to rebbot it would give you an option to reboot or recover...oh well
thanks so much hopefully i can try to resolve it later tonight...
by the way what is CWM, what does that mean
CWM is ClockworkMod Recovery, the “custom” recovery that lets you perform backup and restore of your phone's flash memory and install various custom ROMs and modifications. See http://droid.koumakan.jp/wiki/ClockworkMod_Recovery for a bit more information on it.
Question where would i find the images and what rev RSDLite do i use 4.9 or 5.0, sorry, just asking...
Google the file names, should net you some results.
4.9 or 5.0, doesn't really matter. 5.0 is reported to work better than 4.9 on Windows 7 systems.
thanks, i got it to work....thanks so much...
Had just flashed the latest CM9 nightly (clean install, fresh wipe) yesterday and everything was running fine.
This morning, woke up, my phone was turned off. When powering it on it hung on the google screen. Fastboot still working, booted into recovery only to find that I would get error messages when trying to load my backs "E:unable to mount /sdcard". Apparently it also couldn't mount /data. So I was unable to flash any images or restore or boot up.
Seeing that fastboot was still working I assume I'm not bricked yet. I tried flashing a new boot and cwm recovery via fastboot - no dice. Same errors.
I don't have a recent backup of anything in sdcard, but at this point I'm willing to sacrifice it.
Found this thread http://forum.xda-developers.com/showthread.php?t=1078213
and I'm trying to follow the steps to flash back to stock GB. using the GRJ22 images
It flashed the boot and recovery without issue but seems to hang while flashing the system.img. I know it's a big file, but it was up to ~2hrs with it still transferring. I pulled the plug on it and tried again, lost patience after an hour.
Now I had the idea of maybe locking and unlocking the boot loader would help things.....not sure why I thought this. Anyway, now it seems to hang on the unlock bootloader screen.
So my question now - am I screwed?
- anything else to try?
- is it really "hanging" or do I need to give it more time?
- have I screwed myself even more by now locking my bootloader and flashing the stock recovery?
Any help would be very much appreciated....
Some new additions and new insights from the reddit android community:
- this probably has nothing to do with CM9. My phone has been wonky for about two weeks - random reboots, sometimes rebooting into recovery. That's why I thought I'd throw on the latest nightly and do a fresh wipe yesterday.
- There's definitely something up with /data. Anytime I tried wiping all/factory reset in cwm recovery I got errors about not being able to mount /data or being able to find files in /data
- basically anything I do involving /data partition causes the phone to lock-up -- flashing the boot.img and recovery img worked, but not system. Also, I think the reason I can't re-unlock the bootloader is because during the unlock process it tries to do a factory reset/data wipe
Basically I think there are two things I need to know if I can do - 1) unlock the bootloader again, via some way that won't try to reset the /data partition and thus won't freeze the phone. 2) try repartitioning /data
I really hope I didn't screw myself by locking the bootloader. I'd actually feel a lot better if it was something in my phone that just failed hardware-wise rather than something I could've fixed if I wasn't too quick to try poorly thought out ideas.....
Any help at all would be appreciated!
Possibly (and likely) a corrupted nand flash. Fairly common problem sadly. I'd say it's a good thing your bootloaders locked, no dramas sending it back to samsung. It might've been possible to reset the partitions and flash fastboot images but i don't think i've seen anyone who has done this to sort any similar problem. Hopefully your phones still under warranty
Well thank God that it turns out that I'm still on warranty.....sending the phone back to Samsung tomorrow.
Like you said, it's actually a good thing the bootloader is now locked and the stock boot img and recovery img are now back on! Hopefully this makes it more likely that they weren't turn away my phone.
I've yet to hear someone not getting work done under warranty because of an unlocked boot loader but it's always good to have it as stock as can be. Hope they don't take too long with your phone.
Harbb said:
I've yet to hear someone not getting work done under warranty because of an unlocked boot loader but it's always good to have it as stock as can be. Hope they don't take too long with your phone.
Click to expand...
Click to collapse
I bricked my nexus s 4 days before Christmas last year... and i was using a custom rom obviously with an unlocked bootloader and custom recovery image, and i handed it to vodafone, and guess what? they repaired without asking any questions, and the day before Christmas! sooo happy maybe because i was thirteen then, they didn't suspect a thing
I've looked around quite a bit, but can't find anyone who has had this problem when restoring. I was trying out Paranoid Android 3.10 D2VZW on my Galaxy SIII, and decided to go back to JellyBam 8.2.0 D2VZW. Both are 4.2.2 ROMs. I rebooted into CWM Recovery, wiped data and cache (can't remember if I wiped the Dalvik), and restored my JellyBam backup. The restore went fine, and I rebooted the system from CWM...nothing! Phone is completely black, no boot up at all. I tried the power button, a battery pull, booting into recovery, and booting into download. When I plug my phone into my computer (a Mac with Windows running in Parallels), I get QHSUSB_DLOAD. So far my research tells me this means my phone is hard-bricked. If I plug in without a battery, I get a red LED light that extinguishes after a few minutes. My understanding of hard-bricking is that it's caused by flashing ROMs not intended for my phone (i.e. an international version ROM). Why would my phone hard-brick if the last thing I did is restore a backup from a previously-working ROM built for my phone? I didn't check the md5, but if the md5 failed wouldn't the restore fail too? I literally can't do anything with my phone. No display, no Odin/download, no recovery. The only indications that it isn't completely fried are the red LED and my computer recognizing the QHSUSB_DLOAD and making a notification sound when it's connected or disconnected. I have no problem sending it to be JTAGed if need be, but I'm not 100% that it's hard-bricked. Any suggestions?
ransdell2 said:
I've looked around quite a bit, but can't find anyone who has had this problem when restoring. I was trying out Paranoid Android 3.10 D2VZW on my Galaxy SIII, and decided to go back to JellyBam 8.2.0 D2VZW. Both are 4.2.2 ROMs. I rebooted into CWM Recovery, wiped data and cache (can't remember if I wiped the Dalvik), and restored my JellyBam backup. The restore went fine, and I rebooted the system from CWM...nothing! Phone is completely black, no boot up at all. I tried the power button, a battery pull, booting into recovery, and booting into download. When I plug my phone into my computer (a Mac with Windows running in Parallels), I get QHSUSB_DLOAD. So far my research tells me this means my phone is hard-bricked. If I plug in without a battery, I get a red LED light that extinguishes after a few minutes. My understanding of hard-bricking is that it's caused by flashing ROMs not intended for my phone (i.e. an international version ROM). Why would my phone hard-brick if the last thing I did is restore a backup from a previously-working ROM built for my phone? I didn't check the md5, but if the md5 failed wouldn't the restore fail too? I literally can't do anything with my phone. No display, no Odin/download, no recovery. The only indications that it isn't completely fried are the red LED and my computer recognizing the QHSUSB_DLOAD and making a notification sound when it's connected or disconnected. I have no problem sending it to be JTAGed if need be, but I'm not 100% that it's hard-bricked. Any suggestions?
Click to expand...
Click to collapse
It's definitely hard bricked, whatever happened is very strange though, as a nandroid doesn't usually mess up your boot partition.
Flashing a rom not intended for your phone can cause a hard brick, but that's not the only way it can happen. Somewhere in the restore process your boot partition got corrupted. Your base coding somehow is not being recognized, and your computer and phone can't tell what's supposed to run. A jtag is really your only option.
TWRP offers you the option to disable the boot and recovery partition when restoring. After you fix your phone, I'd recommend trying that out so you're absolutely sure your boot partition doesn't get touched. Those really don't need to be restored anyway.
Sorry that happened to you.
Sent from my SCH-I535 using Tapatalk 2
Bummer. Thanks for the input. I kinda figured that was the case, but was hoping I was missing something. Guess I'm going to have it JTAGed, probably by Mobile Tech Videos. The process looks fairly simple. If the equipment costs were comparable to having someone else do it I might do it myself, but if that were the case everyone else would be doing that too! I'll let you know how it goes.
ransdell2 said:
Bummer. Thanks for the input. I kinda figured that was the case, but was hoping I was missing something. Guess I'm going to have it JTAGed, probably by Mobile Tech Videos. The process looks fairly simple. If the equipment costs were comparable to having someone else do it I might do it myself, but if that were the case everyone else would be doing that too! I'll let you know how it goes.
Click to expand...
Click to collapse
I think the price is reasonable if you factor in equipment and labor.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
I think the price is reasonable if you factor in equipment and labor.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Got my phone JTAGed by Patrick Walls (whose service is available on eBay for ~$35), and it works great. Fast service and great communication from Patrick. The phone came back unrooted with a stock 4.1.2 ROM. Of course I immediately re-rooted it and flashed a fresh JellyBAM ROM to it (with a huge feeling of trepidation), and so far everything is working, with the exception of the camera (I get "Can't connect to camera" after taking one picture, and a reboot is the only thing that enables the camera again, for one pictures, then can't connect, reboot, one pic, can't connect, etc.).
Having never hard-bricked before after many, many ROM changes on a Fascinate and about 10 ROM changes on my S3, I'm a little nervous about changing them now. Is my hesitation unfounded providing I don't mess with the bootchain? To root my phone I flashed the VRALEC bootchain, then TWRP, then rooted, then JellyBAM, then the VRBMD3 bootchain, as per this rooting guide:
http://forum.xda-developers.com/showthread.php?t=2046439
Now that I've put my phone back to the Jelly Bean bootchain, I should be free to flash ROMs built for my device without a serious concern about hard-bricking, right?
ransdell2 said:
Got my phone JTAGed by Patrick Walls (whose service is available on eBay for ~$35), and it works great. Fast service and great communication from Patrick. The phone came back unrooted with a stock 4.1.2 ROM. Of course I immediately re-rooted it and flashed a fresh JellyBAM ROM to it (with a huge feeling of trepidation), and so far everything is working, with the exception of the camera (I get "Can't connect to camera" after taking one picture, and a reboot is the only thing that enables the camera again, for one pictures, then can't connect, reboot, one pic, can't connect, etc.).
Having never hard-bricked before after many, many ROM changes on a Fascinate and about 10 ROM changes on my S3, I'm a little nervous about changing them now. Is my hesitation unfounded providing I don't mess with the bootchain? To root my phone I flashed the VRALEC bootchain, then TWRP, then rooted, then JellyBAM, then the VRBMD3 bootchain, as per this rooting guide:
http://forum.xda-developers.com/showthread.php?t=2046439
Now that I've put my phone back to the Jelly Bean bootchain, I should be free to flash ROMs built for my device without a serious concern about hard-bricking, right?
Click to expand...
Click to collapse
Glad you got it working.
There's always a risk of something going wrong and a hard brick reoccurring, you just had bad luck. I don't think your brick had anything to do with your bootchain.
I think what probably happened was when you made a nandroid in cwm, the boot partition somehow got corrupted. CWM by default restores your boot, recovery, data, system, and cache partitions. In the advanced restore section, you can restore one at a time but you have no way of simply disabling a particular partition from being restored. I think since the boot partition was messed up, it erased your good data and hard-bricked your phone.
TWRP by default only backs up your data, cache, and system partitions and leaves your boot and recovery partitions alone. If you restore that backup, then there's pretty much no way a hard brick can happen. I can't think of any reason why you really need to backup your recovery or boot partition.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Glad you got it working.
There's always a risk of something going wrong and a hard brick reoccurring, you just had bad luck. I don't think your brick had anything to do with your bootchain.
I think what probably happened was when you made a nandroid in cwm, the boot partition somehow got corrupted. CWM by default restores your boot, recovery, data, system, and cache partitions. In the advanced restore section, you can restore one at a time but you have no way of simply disabling a particular partition from being restored. I think since the boot partition was messed up, it erased your good data and hard-bricked your phone.
TWRP by default only backs up your data, cache, and system partitions and leaves your boot and recovery partitions alone. If you restore that backup, then there's pretty much no way a hard brick can happen. I can't think of any reason why you really need to backup your recovery or boot partition.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Great, thanks for the info! I'll make sure that the boot and recovery partitions aren't touched in the future. I've primarily used CWM, but am probably just going to stick with TWRP.
So, after being on 19.6.3 (or something similar), Droid MAXX (XT1080M), rooted and unlocked running TWRP, I started getting a lot of FC, so I used RSD lite to return to complete stock, and took all the OTA updates to 24.3.7. Now, I can't even get the phone to boot past the unlocked bootloader message unless I go into the stock android recovery (or even TWRP when I reflashed it) and perform a factory reset/wipe cache. Even then sometimes after doing that, the phone won't boot past the Droid Eye unless I factory and wipe cache a few more times and get lucky. Then, if it boots, and I set everything back up, the same thing happens if I reboot, where the phone won't boot past the unlocked bootloader message.
Does anyone have any ideas as to why this is happening? I'm at a complete loss. Everything at the current moment is stock. Maybe if someone has the FXZ for 24.3.7, that might work? Help?
Storm0203 said:
So, after being on 19.6.3 (or something similar), Droid MAXX (XT1080M), rooted and unlocked running TWRP, I started getting a lot of FC, so I used RSD lite to return to complete stock, and took all the OTA updates to 24.3.7. Now, I can't even get the phone to boot past the unlocked bootloader message unless I go into the stock android recovery (or even TWRP when I reflashed it) and perform a factory reset/wipe cache. Even then sometimes after doing that, the phone won't boot past the Droid Eye unless I factory and wipe cache a few more times and get lucky. Then, if it boots, and I set everything back up, the same thing happens if I reboot, where the phone won't boot past the unlocked bootloader message.
Does anyone have any ideas as to why this is happening? I'm at a complete loss. Everything at the current moment is stock. Maybe if someone has the FXZ for 24.3.7, that might work? Help?
Click to expand...
Click to collapse
Try this http://motofirmware.center/files/file/50-1ff-obake-maxx_verizon-user-444-su6-7-release-keysxmlzip/
I actually used this on my Maxx (I believe it's the mini image, but it works fine, I may try the maxx version linked above if I run into any issues) http://motofirmware.center/files/file/52-cfc-obakem_verizon-user-444-su6-7-release-keysxmlzip/
Just use RSD to flash the image (you'll need to edit out the line in the XML file that reads <step operation="getvar" var="max-download-size" />)
osucowboy96 said:
Try this *link removed because of XDA's rules*
I actually used this on my Maxx (I believe it's the mini image, but it works fine, I may try the maxx version linked above if I run into any issues) *link removed*
Just use RSD to flash the image (you'll need to edit out the line in the XML file that reads <step operation="getvar" var="max-download-size" />)
Click to expand...
Click to collapse
Well, now the phone will boot, but I keep getting a "com.android.phone" forceclose every time the phone attempts to connect to data (it'll show the "no sim" icon, that will go away, it will get 1x, try to connect to 4G, then the process crashes, and the whole process starts over again).
I just don't understand how a completely stock image on a non-rooted phone doesn't work. The ONLY modification I have right now is the unlocked bootloader. Sigh.
Did you try a full wipe/factory reset?
osucowboy96 said:
Did you try a full wipe/factory reset?
Click to expand...
Click to collapse
Yup. No dice. It'll work fine, and then at some point (at random), it will start the FC loop again.
Did you try both images I provided, and did you edit out the line beforehand? I don't know what else to suggest, other than maybe a hardware issue?
osucowboy96 said:
Did you try both images I provided, and did you edit out the line beforehand? I don't know what else to suggest, other than maybe a hardware issue?
Click to expand...
Click to collapse
I didn't try the mini image. I'll give that a shot. And the MAXX image does not have that line in the first place.
Storm0203 said:
I didn't try the mini image. I'll give that a shot. And the MAXX image does not have that line in the first place.
Click to expand...
Click to collapse
Alright, so I tried the Mini image as well. That one automatically factory resets when I reboot.
I don't know what else to suggest. I searched for quite a while to find those images when I needed one. I guess I got lucky on using it for mine, it's been solid with no issues. Literally the only issue I have had was one force close of "contacts" when I made a call, but that only happened once. It's been a long while since I used House of Moto, not sure if it's even relevant anymore, but you might research it.
Storm0203 said:
So, after being on 19.6.3 (or something similar), Droid MAXX (XT1080M), rooted and unlocked running TWRP, I started getting a lot of FC, so I used RSD lite to return to complete stock, and took all the OTA updates to 24.3.7. Now, I can't even get the phone to boot past the unlocked bootloader message unless I go into the stock android recovery (or even TWRP when I reflashed it) and perform a factory reset/wipe cache. Even then sometimes after doing that, the phone won't boot past the Droid Eye unless I factory and wipe cache a few more times and get lucky. Then, if it boots, and I set everything back up, the same thing happens if I reboot, where the phone won't boot past the unlocked bootloader message.
Does anyone have any ideas as to why this is happening? I'm at a complete loss. Everything at the current moment is stock. Maybe if someone has the FXZ for 24.3.7, that might work? Help?
Click to expand...
Click to collapse
Hardware or rather memory issues!
Did you check the md5 of each xlm.zip?
im new to all this rooting and flashing stuff and i did search quite thoroughly before resorting to posting on here. Ok so somehow i rooted and took the system app TextNow off of the phone since then ive tried hard resetting but now all the phone does after booting it has a little txt box that pops up over and over so much so that its impossible to do anything but power down and it reads" unfortunately TextNowOOBE has stopped...... Ok" . How can i fix this.... Ive reset the phone through recovery and cache partition both have been wiped. Plz someone help me
sjrjr4364 said:
im new to all this rooting and flashing stuff and i did search quite thoroughly before resorting to posting on here. Ok so somehow i rooted and took the system app TextNow off of the phone since then ive tried hard resetting but now all the phone does after booting it has a little txt box that pops up over and over so much so that its impossible to do anything but power down and it reads" unfortunately TextNowOOBE has stopped...... Ok" . How can i fix this.... Ive reset the phone through recovery and cache partition both have been wiped. Plz someone help me
Click to expand...
Click to collapse
#1 rule make a backup in recovery before tinkering
Aside from restoring a backup, the easiest way to get your phone working again would be to flash a fresh ROM. For example, Albertos AOSP is quite stable and up to date. You will need that ROM.zip and a compatible gapps.zip. wipe everything clean and flash those in recovery.
You will lose all your data.
I do not know what TextNow is, but if you need the "stock ROM" you may need to restore factory firmware via PC- you will lose all your data
What exactly are you trying to do?