[Q] [help]wifi doesn't work after unbrick D2G - Droid 2 Global General

hi, my d2g was brick, i m already solve the problem (thx to the develop made happed) and work perfect but just the wifi stay connecting... and dont wanna work
i was trying with 5 different routers with different method (WEP WAP... on/off, reset, etc...) but doesn't work yet :s
any idea???? what's the problem???
thank you in advantage
ps: i know of others user with d2g had the same problem after unbrick their phone.

done
i could solve the problem of wifi, now i got another one, is the Airplane Mode stay turning on and off with out stop!!!!

fulvi0 said:
i could solve the problem of wifi, now i got another one, is the Airplane Mode stay turning on and off with out stop!!!!
Click to expand...
Click to collapse
Flash unbrick sbf again and wipe before update to 629
Sent from my DROID2 GLOBAL using xda premium

Thx u. I just wipe. (Hard restore ) i working good
Sent from my DROID2 GLOBAL using xda premium

I can't wipe in recovery I can't see options

when you see android guy with! , press both volume buttons
Sent from my DROID X2 using xda premium

I try wipe and nothing change wifi not working

roxsy said:
I try wipe and nothing change wifi not working
Click to expand...
Click to collapse
Did you do all the steps (applying the update as well)? Does the system show as 2.3.4?

yea 2,3,4 but I can't Root by superoneclick and pete's motorola root tool

roxsy said:
yea 2,3,4 but I can't Root by superoneclick and pete's motorola root tool
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1592154
Sent from my DROID2 GLOBAL using xda premium

hi, i got same problem, can you help me?
i just only unbrick and unlock band to use AT&T network
and now wifi can search but cant connect...!

Your phone was on 4.5.629 or you flashed it to 4.5.629 during the unbrick/rooting process.
You did not update to 4.5.629 after that.
This issue manifests on devices that were updated to 4.5.629 (Android 2.3.4) and then were left on 4.5.608 after the unbrick & rooting process.

1. Flash 608 SBF using RSDLite (VRZ_A956_4.5.608_1FF_01.sbf)
2. Flash Repack_629 SBF using RSDLite (BL=2 BOOT REC CDTf__Repack_629.sbf)
3. Reboot, wipe data and cache
4. Enable Unknown Source and Development features in Setting
5. Root D2G with SuperOneClick v2.3.3
6. Install OtaRootKeeper, Run Protect-root then temp-unroot
7. Reboot to recovery then install 629 OTA update.zip then reboot(Blur_Version.4.5.608.A956.Verizon.en.US.zip)
8. Open OtaRootKeeper and restore Root
9. Install Droid 2 Recovery Bootstap.apkthen Reboot to Recovery
10. At Clockwork Recovery, run Backup the nan-droid
11. Flash 330 SBF suing RSDLite (VRZ_A956_2.4.33_1FF_01.sbf) --> After flash completed, phone will BRICKED, don’t worry
12. Flash 608 using EzSBF on USB stick (1KDStaz_D2G_4.5.608.iso) --> After flash completed, phone will BRICKED, don’t worry
13. Flash Repack_629 SBF using RSDLite (2_BL=2 BOOT REC CDTf__Repack_629.sbf)
14. Reboot, wipe data and cache
15. Enable Unknown source and Development features in Setting
16. Root D2G with SuperOneClick v2.3.3
17. Install Droid 2 Recovery Bootstap.apk then Reboot to Recovery
18. At Clockwork Recovery, Wipe Cache and install band unlock (TBH_Band_Unlock_v2.0.zip)
19. At Clockwork Recovery, run RESTORE the nan-droid (the one that backup on step 10)
20. Reboot phone then it should be able to us AT&T, T-Mobile and Verizon and enjoy
Click to expand...
Click to collapse
i do like this. pls help me!!!
i use AT&T network

wipe data again

i try third times but nothing happen ! wipe cache, data....

If you followed the instructions above, did you restore a nandroid backup of .608, or a nandroid backup of .629? Originally you said you were on .608, so if you made a nandroid backup of that, and restored it, you would be experiencing the issue you mention.

Hi,i have the same issue,at first when bootloader was accepting downgrade i could go on froyo where wifi worked perfect,but on neither GB release wifi just have turning on/turning off disease,tried every possible thing but nothing is working except MIUI.us but its CDMA rom and i'm gsm user.according to this its something with firmware related in my case.

Related

Milestone 2 Firmware

hello,
during the restore with clockworthmod recovery, the phone hangs up.
now is the system damage and no boot the phone. bootloader and menu for hard-reset(X+power works).
i need a sbf file for the european milestone 2 with motoa953 chipset for flashing with rsd lite.
gives a update.zip for the sdcard with clockworthmod revory to start from the menu "apply sdcard update.zip) with verifying
many thanks
try data wipe/factory reset and wipe cache in the clockwork or stock recovery..might fix the problem.
Sent from my DROID2 using XDA App
this only delete cache and data. during the restore with clockworthmod, the system is erasing and then copied the system from backup. and in copy mode the sdcard hangs and now is the systems files all erased an the phone doesn´t boot:-(
Rennert said:
this only delete cache and data. during the restore with clockworthmod, the system is erasing and then copied the system from backup. and in copy mode the sdcard hangs and now is the systems files all erased an the phone doesn´t boot:-(
Click to expand...
Click to collapse
Look on the forums and see how to sbf, that should fix the problem. And if not, you "bricked" it..if you can get into the stock recovery by holding the x button down and it comes up and what not then its salvageable but if all you get is the motorola m then it might be toast. Give sbf'ing a try.
Edit: Sorry I didn't really read your original post, sorry, you know how to sbf but don't have the file..I couldn't tell you where to get that...go to androidforums.com or droidlife.com and maybe someone can help over there because obviously im the only one responding...
Sent from my DROID2 using XDA App
The problem is, the milestone 2 have another chipset (a953) like droid2. Rsd lite says: firmware is not compatible with this phone. On recovery mode with update.zip can i only flash original firmware (verifization).
Today i go in the vodafone shop, the phone is only 1 week old.
Can i create a working sbf file from my clockworthmod* .img? I have many complete backups on my sdcard.
Or how can i make a sbf file from the system of another milestone 2. This would i flash into my ms2 with rsdlite
Sent from my Milestone using XDA App
http://www.mydroidworld.com/forums/android-hacks/1207-milestone-sbf-files.html
Stumbled apon this but im not sure if this is for the milestone 1 or 2...
Sent from my DROID2 using XDA App
@Rennert,
How did you get the Clockwork recovery installed on the Milestone 2 (A953) ?
I have the same phone myself but I've not found any information on how to proceed. I've rooted permanently with the z4root-app but that is about it.
I stumbled on this one (similar) to the one above when looking up bootstrapping the Milestone 2
hXXp://and-developers.com/sbf:milestone2
Dunno if it helps (sorry as I'm a lurker I have to HXXP).
dogei22 said:
@Rennert,
How did you get the Clockwork recovery installed on the Milestone 2 (A953) ?
I have the same phone myself but I've not found any information on how to proceed. I've rooted permanently with the z4root-app but that is about it.
Click to expand...
Click to collapse
With Droid X/2 recovery Bootstrap you can install ClockworkMod v2.5.0.8.
Edit: Please read instructions before you try the application.
Thx,
Installed ClockworkMod recovery with Droid 2 Bootdtrap. Not sure if there is any joy out of it as there are no ROMs around yet... nandroid backups works well though.
dogei22 said:
Thx,
Installed ClockworkMod recovery with Droid 2 Bootdtrap. Not sure if there is any joy out of it as there are no ROMs around yet... nandroid backups works well though.
Click to expand...
Click to collapse
For now only backup just in case.
I am doing some tests and hoping that if something goes wrong I can restore my phone with that backup.
Edit: Droid Overclock can be useful for example to change some Build Props(Dalvik VM, Max EVTs, etc)
Sent from my MotoA953 using Tapatalk
Try it, appear the original european firmware.
http://modmymobile.com/forums/593-m...558715-milestone-2-firmwares-superthread.html
Tell us if everything is ok.

Fix Vibrant 4G Clockword recovery Mod and use ROM Manager for Backup and ROM Flashing

I am modifying this post removing some steps:
Note that you can always go back to orignal Odin ROM using Vibrant Download Mode in the link below:
http://forum.xda-developers.com/showthread.php?t=978836
You should know what you are doing, otherwise I am not reponsible for any device brick.
1- Use SuperOneClick 1.7 to gain root (USB debugging enabled).
Open SuperOneClick and run Shell Root with your phone plugged in.
Use Rage option, then once done, reboot the phone and verify root using "Root Checker" from the Market.
http://forum.xda-developers.com/showthread.php?t=803682
2. Download "3e_recovery_installer.zip" from here:
http://forum.xda-developers.com/showthread.php?t=833423
run the 3e Recovery Installer. When finished, close.
3. Flash ClockWorkMod Recovery via ROM Manager from market by selecting "Vibrant" when asked for phone type. Then reboot into recovery. (You may need to reboot your phone if you get stuck on the ROM Manager "Reboot to Recovery" screen) (Just reboot, then attempt to reboot into recovery again)
At the blue recovery select "reinstall packages". The first time will fail, run it once more, and you should now have the green CWM Recovery menu.
4. Install Kernel Flasher from the Market and backup the kernel.
5. use Rom Manager to flash Data and Dalvik init.d-busybox with data to SD update.zip to fix Data and Dalvik init.d-busybox from below link:
http://forum.xda-developers.com/showthread.php?t=744655
6- When finshed you should be able to backup and restore the ROM using Rom Mananger.
What do you mean by no network
bryandrew19 said:
What do you mean by no network
Click to expand...
Click to collapse
I think it means no signal or cell service until you re flash your kernal back up..
Does this fix get cwm working for all features? Or just backup and restore?
Sent from my SGH-T959V using XDA Premium App
I tested backup, restore and rom flashing
arahma said:
I tested backup, restore and rom flashing
Click to expand...
Click to collapse
Thanks for this. Btw what rom did you flash?
Sent from my SGH-T959V using XDA Premium App
Can anyone confirm this?
I have created a deodex zip file for orignal vibrant 4G rom and used rom manager to successfully flash it. I will post the rom later today.
Sgs4g apparently has a new rockstar.. bravo
Sent from my SGH-T959V using XDA App
I guess I'm the first casualty of this. I did everything to the letter in the post up to step five. Once i flashed 4g_sd-fix_New in rom manager it the phone rebooted and did the exact opposite of what it was supposed to do. It no factory reset my phone and neither the sd card nor the internal storage mount.
Any help would be appreciated here.
treobwoy said:
I guess I'm the first casualty of this. I did everything to the letter in the post up to step five. Once i flashed 4g_sd-fix_New in rom manager it the phone rebooted and did the exact opposite of what it was supposed to do. It no factory reset my phone and neither the sd card nor the internal storage mount.
Any help would be appreciated here.
Click to expand...
Click to collapse
I got the same issue. Flashing back to stock now. It also wiped my entire SD card.
arahma said:
5. Flash 4g_sd-fix_New using ROM Manager to fix Data umount issue from below link:
Click to expand...
Click to collapse
For this step do you mean go into recovery and flash or do you mean use ROM Manager and "Install ROM from SD Card"?
Beefvvl said:
For this step do you mean go into recovery and flash or do you mean use ROM Manager and "Install ROM from SD Card"?
Click to expand...
Click to collapse
doing it through rom manager worked
aloneinshadow said:
I got the same issue. Flashing back to stock now. It also wiped my entire SD card.
Click to expand...
Click to collapse
Let us know if you get it working. And what you did.
Sent from my SGH-T959V using XDA Premium App
Is anyone able to get data back?
I tried using Odin to flash to stock and I'm still unable to get data connection unless I connect to Wifi.
I sure hope you modified the SD Fix.....
That fix was created by Eugene and I to fix mounting for the Vibrant. If flashed to a 4G, it'll break.
I wouldn't recommend this method at all, this looks risky. Just wait for krylon or koush to come out with a proper release of cwm. I have offered to lend my phone to either of them and im sure as soon as either one has the time they will get it going.
I don't like doing things half ass, and while the work is appreciated i wouldn't recommend this guide to the average user as i lost my first 4g to a similar guide.
spockmeat said:
I wouldn't recommend this method at all, this looks risky. Just wait for krylon or koush to come out with a proper release of cwm. I have offered to lend my phone to either of them and im sure as soon as either one has the time they will get it going.
I don't like doing things half ass, and while the work is appreciated i wouldn't recommend this guide to the average user as i lost my first 4g to a similar guide.
Click to expand...
Click to collapse
Im back from my Android break...as you can tell.. LOL
Hit me up and we'll work out something for the device loan.
krylon360 said:
I sure hope you modified the SD Fix.....
That fix was created by Eugene and I to fix mounting for the Vibrant. If flashed to a 4G, it'll break.
Click to expand...
Click to collapse
Are you talking about step 5?
I tried all the steps till 5 and get the data not being able to connect and then after I Odin back to stock and I'm unable to do step 6.
Krylon can you load up the 2 ROM's you have available for us to try if we can get this damn thing to work?
Beefvvl said:
Are you talking about step 5?
I tried all the steps till 5 and get the data not being able to connect and then after I Odin back to stock and I'm unable to do step 6.
Krylon can you load up the 2 ROM's you have available for us to try if we can get this damn thing to work?
Click to expand...
Click to collapse
Yes, Step 5 was created by us to allow both Internal and External SD to auto mount to the phone and PC on the VIBRANT.
We had to modify the stock 4G files to allow this due to the 4G only having a external SD.
For now, I'm reporting this thread due to it being just like the last "CWM for Vibrant works on the 4G" thread which caused bricks, which resulted in me having to create the ODIN image for everyone.
Please do not jump the gun. Be patient.

Help Please!!!

Alright, I rooted my Nexus S 4G this guide. My phone was running 2.3.5 but I figured that these steps in Terminal wouldn't really change. When I flashed the "recovery-clockwork-3.0.0.5-crespo.img" it didn't install properly (I assume because it was out of date/wrong version) Anyway, I flashed this instead with no problems.
In my euphoria over solving my clockwork problem, I forgot to flash the "su-2.3.6.1-ef-signed.zip" and flashed the current version of MIUI. I am now stuck in a bootloop and I cannot enter recovery by using power+volume. I cannot turn the phone off. I can load the bootloader screen using Terminal while I plug it into my computer, but I don't know what to flash to fix the phone, and start over/end up with a Nexus running MIUI.
i dont know much about macs but you can flash the img files through fastboot.
imgs files are here
thank buglesspete
chewbz said:
i dont know much about macs but you can flash the img files through fastboot.
imgs files are here
thank buglesspete
Click to expand...
Click to collapse
I can handle the mac part if you can show me which files to flash in which order to make my phone work again.
Okay this will take your phone back to stock. Download the grj22 image files. When you open it up it should have like 4 or 5 img files. After that open up cmd and type in the commands buglesspete has in his first post. It should be under "return to stock" or sometime like that.
Sent from my Nexus S 4G using XDA App
XikkeN said:
Alright, I rooted my Nexus S 4G this guide. My phone was running 2.3.5 but I figured that these steps in Terminal wouldn't really change. When I flashed the "recovery-clockwork-3.0.0.5-crespo.img" it didn't install properly (I assume because it was out of date/wrong version) Anyway, I flashed this instead with no problems.
In my euphoria over solving my clockwork problem, I forgot to flash the "su-2.3.6.1-ef-signed.zip" and flashed the current version of MIUI. I am now stuck in a bootloop and I cannot enter recovery by using power+volume. I cannot turn the phone off. I can load the bootloader screen using Terminal while I plug it into my computer, but I don't know what to flash to fix the phone, and start over/end up with a Nexus running MIUI.
Click to expand...
Click to collapse
Just a general hint... if oyu own a Nexus S 4G, Crespo isn't the right codename to look for.. it's crespo4g. Get the cwm recovery from here and flash the 4G version via "fastboot flash recovery <recoveryname>.img": http://forum.xda-developers.com/showthread.php?t=988686
rentaric said:
Just a general hint... if oyu own a Nexus S 4G, Crespo isn't the right codename to look for.. it's crespo4g. Get the cwm recovery from here and flash the 4G version via "fastboot flash recovery <recoveryname>.img": http://forum.xda-developers.com/showthread.php?t=988686
Click to expand...
Click to collapse
I know. I linked to that thread in my first post. What step am I skipping to run MIUI without a bootloop?
XikkeN said:
I know. I linked to that thread in my first post. What step am I skipping to run MIUI without a bootloop?
Click to expand...
Click to collapse
I have no experience with the 4G version of this phone but I can tell your that bootloops are usually caused by failing permissions (fix permissions in cwm rec) or missing wipes before isntalling the actual rom.
So I'd go back to start, flash the 4g recovery, wipe everything (including "mount and storage"'s /boot and then flash MIUI for 4g from here afterwards.
Basically, that MIUI (and most other custom roms) includes superuser.zip aka root. No need to root the devices before, all you need is an unlocked bootloader.
rentaric said:
I have no experience with the 4G version of this phone but I can tell your that bootloops are usually caused by failing permissions (fix permissions in cwm rec) or missing wipes before isntalling the actual rom.
So I'd go back to start, flash the 4g recovery, wipe everything (including "mount and storage"'s /boot and then flash MIUI for 4g from here afterwards.
Basically, that MIUI (and most other custom roms) includes superuser.zip aka root. No need to root the devices before, all you need is an unlocked bootloader.
Click to expand...
Click to collapse
What he said, I always wipe 3x everything just to make sure it is a clean install. And some people will also suggest to let the rom boot up normally before flashing a different kernel.
Sent from my Nexus S 4G using XDA App
chewbz said:
What he said, I always wipe 3x everything just to make sure it is a clean install. And some people will also suggest to let the rom boot up normally before flashing a different kernel.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
wiping 3 times is senseless! and the kernel should be flashed right after the rom install!
oh and wiping the dalvik cache and chache after a rom-update is also senseless! the updater-script do this automatic!
Sent from my Nexus S using XDA Premium App
Borky_16 said:
wiping 3 times is senseless! and the kernel should be flashed right after the rom install!
oh and wiping the dalvik cache and chache after a rom-update is also senseless! the updater-script do this automatic!
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
your assuming that the devs took the time to make sure to include that

[Q] HTC evo 4g stuck in bootloop (I know)

Ok first of all, this is my dad's phone he wanted rooted with a custom ROM. I'm not new at all to flashing but I have the Droid X and Droid Bionic so I only know MOto. SO I performed the root (*****) and installed CM7 build on his Evo. A week later he was experiencing ploblems with gmail and GPS and not wanting to constantly hear complaining, I opted to install a new ROM that had an RC build . I chose Synergy with god mode (wanting to wipe it twice) and proceeded with the dalvik and cahce wipes only. I didn't format sys because the op didn't state that I had to.....well I left his house letting the ROM settle and now its in a bootloop. He's telling me via gtalk that it trys to come on but says "storage is full" and "android.acor" has stopped. Any solutions that I can give him to get him back up and running?
Did you nandroid...if so just restore that
Sent from my PC36100 using XDA App
You'll have to flash a new rom or restore a previous backup (if any was made).
jboyer0000 said:
Did you nandroid...if so just restore that
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I made a CWM back-up but how do I get back into CWM recoovery to flash?
Theonew said:
You'll have to flash a new rom or restore a previous backup (if any was made).
Click to expand...
Click to collapse
How do I flash the new ROM? It's bootlooped and I have no idea how to get to his CWM recovery from a bootloop.
jkoldha said:
How do I flash the new ROM? It's bootlooped and I have no idea how to get to his CWM recovery from a bootloop.
Click to expand...
Click to collapse
Turn off the device, hold down the volume button and then the power button.
make sure you follow the 3 main steps before flashing/ restoring any rom or backup
1. wipe data/factory reset
2. wipe cache
3. go to advance->wipe dalvik
then proceed, and even though your motorola, it's the same through out all the phones
(have a photon and an evo3d)
A2CKilla said:
make sure you follow the 3 main steps before flashing/ restoring any rom or backup
1. wipe data/factory reset
2. wipe cache
3. go to advance->wipe dalvik
then proceed, and even though your motorola, it's the same through out all the phones
(have a photon and an evo3d)
Click to expand...
Click to collapse
Yea I should've data wiped but it said it would....
I always just restore to my previous rom the when I go to flash a new one I use amon ra recovery and wipe everything 3X before flashing.
Sent from my highspeed rooted Evo.

[Q] Help needed: Softbrick while using Bootstrap to flash ROM

Dear guys, so here is my issue. I previously used the 4.2.2 rom by edison and has managed to flash it using the Atrix 2 bootstrap methodhttp://forum.xda-developers.com/showthread.php?t=1346977. And now, I wanted to try out the 4.4 ROM using the same bootstrap method as well. However, after I pressed "Bootstrap Recovery" and "reboot Recovery", the phone reboots into the M logo, and then its screen just stays black and blank forever.
The first method I tried to fix it is by getting into the Recovery (Home+Vol Up+Vol Down), and after trying out several reboot options, still to no avail. And now, I have performed "wipe data factory" and "wipe cache" in the recovery option. So what should I do now? I cant access the CWM or bootstrap to install my ROM or to perform any restorations.
Sorry guys that I have to asked this, but I did it to prevent myself from further plunging into the hard brick state.
kenlohwj said:
Dear guys, so here is my issue. I previously used the 4.2.2 rom by edison and has managed to flash it using the Atrix 2 bootstrap methodhttp://forum.xda-developers.com/showthread.php?t=1346977. And now, I wanted to try out the 4.4 ROM using the same bootstrap method as well. However, after I pressed "Bootstrap Recovery" and "reboot Recovery", the phone reboots into the M logo, and then its screen just stays black and blank forever.
The first method I tried to fix it is by getting into the Recovery (Home+Vol Up+Vol Down), and after trying out several reboot options, still to no avail. And now, I have performed "wipe data factory" and "wipe cache" in the recovery option. So what should I do now? I cant access the CWM or bootstrap to install my ROM or to perform any restorations.
Sorry guys that I have to asked this, but I did it to prevent myself from further plunging into the hard brick state.
Click to expand...
Click to collapse
You installed rom with bootstrap. That's outdated method which only works with wang's CM10/10.1 builds. Newer builds is using BMM only. So with any 4.2< ROM you must use Boot Menu Manager. So you'll need to reflash stock rom via RSD Lite. By the way what's your phone model (MB865 Retail, ME865 China or MB865 at&t?)? First thing before flashing is correct fxz.
-edited-
turffe said:
You installed rom with bootstrap. That's outdated method which only works with wang's CM10/10.1 builds. Newer builds is using BMM only. So with any 4.2< ROM you must use Boot Menu Manager. So you'll need to reflash stock rom via RSD Lite. By the way what's your phone model (MB865 Retail, ME865 China or MB865 at&t?)? First thing before flashing is correct fxz.
Click to expand...
Click to collapse
thank you so much for the prompt reply. So my location is in Malaysia>South East Asia, and it should be MB865. Do i use the 'Android 4.0.4
Blur_Version.67.220.3.ME865.Retail.en.05' file to fxz it? found from the sbf developer site
My previous OTA was 4.0.4, i was worried that if i used it on the earlier custom ROM 4.2.2 that i had, i will hard brick it. So will there be any cause for concern?
and what do they do with the .xml file in the file prior to fxz it? is it fine if i skip that step?
On the phone's back is written ME865 or MB865? Is there any AT&T logo on it? If your phone model is Retail MB - you should flash 6.7.2-EDEM-18.
Sent from my Atrix 2 using Tapatalk
turffe said:
On the phone's back is written ME865 or MB865? Is there any AT&T logo on it? If your phone model is Retail MB - you should flash 6.7.2-EDEM-18.
Sent from my Atrix 2 using Tapatalk
Click to expand...
Click to collapse
MB865, therefore i suppose it should be Blur_Version.672.1.18.MB865.PSHAsiaRetail.en.03. Unfortunately I had sent the phone to a repair guy, so no chance for me to try it out yet. Will update you tomorrow!
that guy wasnt able to repair it, so I did it myself using "Blur_Version.672.1.18.MB865.PSHAsiaRetail.en.03" as the sbf file, and TADAA, problem solved within 10 minutes! Thanks alot for the help, RSD is truly the all-in-1 safe kit
kenlohwj said:
that guy wasnt able to repair it, so I did it myself using "Blur_Version.672.1.18.MB865.PSHAsiaRetail.en.03" as the sbf file, and TADAA, problem solved within 10 minutes! Thanks alot for the help, RSD is truly the all-in-1 safe kit
Click to expand...
Click to collapse
I'm glad you got it figured out. :thumbup:

Categories

Resources