yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] kamilloo83:
I am afraid that most :( :( :(

What do you think should I do to try to flash with the hope of GB?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] kamilloo83:
you're right, I have not written anywhere that I can not enter download mode .. but have not tried ... charge the phone at the moment - in the evening I'll be ready ....

or should I do as I wrote above - this example ROM, and my description is OK?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] andreww88:
Okay cool, that's fairly good news because if you CAN enter download mode you are not bricked and you can ODIN a pre-rooted GB rom or a stock GB rom. If your phone will charge, let it charge up and then ODIN away.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] kamilloo83:
ufff... I hope...

ask again:

Will it be ok as I flash in PC ODIN from:

http://xdaforums.com/show....php?t=1424997

it:

Older ROMs (Directly Rootable)

N7000XXKKA ------ 2.3.6 2011 November------- N7000PLSKK1 -----------------Poland (PLUS) ----------------------- Download

and next I'll be root, and I will be able to upload the recovery CheckROM NoteHD ™ V6 ??? ....
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] andreww88:
Yes, that is thread you need to follow.

You can root by following Dr.Ketan's steps too.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] kamilloo83:
OPERATION FAIL:

<ID:0/003> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> N7000XXKKA_N7000OXXKK6_N7000XXKK5_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> boot.bin

<ID:0/003> NAND Write Start!!

<ID:0/003>

<ID:0/003> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

WHAT IS WRONG?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] andreww88:
Not sure. Can you try another ROM file on that thread? That doesn't look promising, but maybe someone else can help that knows more.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] kamilloo83:
I must download anotheher ROM... one moment...
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] andreww88:
Maybe even try LPF ICS?

It might just have been a bad download, but the MD5 checked good it looks like so I don't know. I'd like someone else to say something to try to help.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] rupalazzi:
Try repartitioning the device. To do so use simply set the right pit file in odin.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] kamilloo83:
can I use it with ROM: N7000XXKKA_N7000OXXKK6_N7000XXKK5_HOME.tar.md5

together in PC ODIN?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] eitama:
Fail advice. You are suggesting someone who is trying to escape the ICS menace to flash yet ANOTHER ics rom that is suspected to have the same eMMC killing bug??? Are you Human? Maybe you are infact Diablo III?

Do not flash LPY or LPF until proven safe!
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] kamilloo83:
GUYS SUCCES!!!! :) I think so :)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] sotiris20:
I'm happy for you mate. I told you from the beginning not to panic. I didn't think your device was bricked. Thank god we have Odin! :rolleyes:

Next time be more careful though...lot of dangers out there!
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] bhasg1007:
Same thing happened to me Abyss kernel not flashing stuck in progress bar and rebooting. So wat i did was i tried to flash franco10 kernel and it got flashed and i rebotted into franco cwm and flashed abyss kernel and restarted into abyss kernel cwm and wiped everything and restored my Darky GB rom all went well and my note booted up fine
[Android Q&A, Help & Troubleshooting] yamyoume:
hey guys i just bought the new HTC ONE X THe global version and in my country google play store is not working at all

is there any way to get it work ???

to access us market i mean

something like market enabler (which don't work for google play)

thanks
[Android Q&A, Help & Troubleshooting] DarkhShadow:
You need Market Enabler and a proxy/vpn in the country you want to fake to do it

Sent from my ice cream powered Nexus S
[Android Q&A, Help & Troubleshooting] yamyoume:
thank you for answering

but are you sure market enabler would work for google play store ??
[Android Q&A, Help & Troubleshooting] DarkhShadow:
Well I used droidVPN(America server) and market enabled(T-Mobile USA), cleared store cache then loaded it and it was US store! Of course you will need to remain connected to it for as long as you want to use market.

Also I suggest activating Google music while using above method, once active it works anywhere

Sent from my ice cream powered Nexus S
[Android Q&A, Help & Troubleshooting] edbertin:
I noticed that most market enabler apps from Play Store was removed. I download the apk from dev here http://code.google.com/p/market-enabler/downloads/list and then I used proxpn free vpn account (mine is premium) and works.

Note: tick the option to install apk from unknow sources on security settings before install the apk

Have fun :-)
[Fascinate Q&A, Help & Troubleshooting] mvmacd:
I just flashed THS cm9 build 10 over build 9 on my fascinate, with CWM-based recovery v5.5.0.4, before I flashed it I wiped cache & dalvik-cache.. and now when I try to boot it goes straight to recovery.

Is there anything I can do? or do I have to do a full wipe & start over?

edit: I wiped data, and re-flashed the zip and it still keeps rebooting into recovery. I guess I'll try restoring to stock, and then re-flashing THS build 10

edit 2: UGH..I wiped my data for nothing. At least I have a who-knows-how-old titanium backup of my apps. After I wiped data and it still would not work, I found "fix ics fascinate recovery boot loop" on google. I entered download mode for some reason by accident, and then I did the 3-finger-recovery. >_< so anyway I heimdall'ed a CWM from a Vanilla GB rom, and it's all fixed now.
[Fascinate Q&A, Help & Troubleshooting] droidstyle:
Section 9: How to get out of a bootloop situation on cm9 mtd based roms without using odin!!

-Power device off, pull sd card, and push a cm7 based rom(see section 3 for link) to the sd card via your PC, then reinstall the sd card on your device

-three finger into recovery

-wipe data

-flash cm7 and and it will bootloop back into recovery

-flash cm7 again, then let it boot

-boot into recovery via power menu

-wipe data

-flash ics build 2 and let it boot

-boot into recovery again via power menu

-wipe data

-flash ICS rom of choice and gapps, reboot
[Kindle Fire Q&A, Help & Troubleshooting] pwned3:
What is the most reliable recovery currently? I'm using twrp at the moment. It's probably an older version so I'm curious what is recommended before i update it.
[Kindle Fire Q&A, Help & Troubleshooting] kinfauns:
My suggestion would be for you to stay with TWRP. Version 2.1.1 is the latest.
[Kindle Fire Q&A, Help & Troubleshooting] autosdafe:
I agree
[Kindle Fire Q&A, Help & Troubleshooting] mdaa83:
You already know that TWRP is intuitive and easy to use. I'm using TWRP 2.1.1 and I have used recovery many times when trying out new ROM builds. Occassionally with 2.1.1 I find that the operation that you want to do just fails with either an error outright or will fail during the recovery process. It even failed on me once while creating a backup. I didn't pay much attention to the backup output log text once and I did want to recover that backup and could not due to an image file being zero bytes in size. I have my own app and data backup script that I wrote that keeps me current so recovery in such a failed case is simply flashing a new ROM and executing my recovery script; couldn't be simpler.

If you pay attention to TWRP's output and not just make an assumption that the backup or recovery succeeded then you can just repeat the operation until it's successful. This is rare but has happened to me more than once but even with that issue, I still like TWRP 2.1.1 (plus my own app backup script).

I'll include my app backup and recovery script here in case others can find it useful (I make no claims that will work to your liking however or that it will even work for you) :)

rebaseline.sh

#!/system/xbin/bash

cd /sdcard/BACKUP/

for i in `/system/bin/pm list packages -3 -f`
do
read junk apk pkg <<< =`echo $i | sed -e 's/[=:]/ /g'`

echo "Processing $pkg..."

echo " backing up $apk..."
cp $apk baseline/
touch /sdcard/BACKUP/baseline/`basename $apk`

echo " backing up data..."
busybox tar czf /sdcard/BACKUP/baseline/$pkg.tar.gz --exclude lib --exclude cache /data/data/$pkg 2>/dev/null
done

echo "Processing accounts..."
echo " backing up data..."
busybox tar czf /sdcard/BACKUP/baseline/accounts.tar.gz /data/system/accounts.db 2>/dev/null

Here is my recovery script:

restore-from-baseline.sh

#!/system/xbin/bash

cd /sdcard/BACKUP

pm set-install-location 1

chmod 777 /data/data

for i in baseline/*apk
do
X=${i/-[0-9].apk}
Y=`basename $i`
Y=${Y/-[0-9].apk}
echo $X

pm install -r $i

# Find out what the new app ID is for the package
OWNER=`/system/bin/ls -l /data/data | grep $Y | awk '{print $3;}'`
echo $OWNER

# Restore data as the app owner ID
chmod 777 /data/data/$Y
su --command "tar xvf /sdcard/BACKUP/$X.tar.gz -C /" $OWNER
echo "tar rc=$?"
chmod 751 /data/data/$Y
echo

done
chmod 771 /data/data

echo "Restoring accounts.db - reboot will be required"
tar xvf /sdcard/BACKUP/baseline/accounts.tar.gz -C /

There is one limitation that I haven't worked into the script yet. Any time there is an app update you will see a duplicate app in the baseline folder differentiated by -1 or -2. Before recovery you can just get rid of the oldest version of the apk file; the data is always current.

I'm sure that there are a lot of apps that this script would not work with but it does work very well with mine and cuts down recovery to a minute or two. I don't use Titanium Backup myself.
[Kindle Fire Q&A, Help & Troubleshooting] YayILikePie:
I've been sticking with TWRP 2.1.1, simply because I really like how it can compress backups, meaning more space for music and videos. Haven't had any issues with it, but I do prefer the look of CWRecovery, particularly Hashcode's latest release.
[G2 and Desire Z Themes and Apps] patnmn:
Can anybody hook me up with the T Mobile Wifi calling app? I am running CM7.
[G2 and Desire Z Themes and Apps] demkantor:
Look @ various roms in the development section. Many have various addons and I have seen wifi calling in a few, of hand check ilwt
[G2 and Desire Z Themes and Apps] bradley_e_smith:
I thought with CM7 it gets auto installed (at least for me it did when I ran CM7)
[G2 and Desire Z Themes and Apps] patnmn:
I am using ILWT. I tried downloading from the link in his thread but it is a dead linnk.
[G2 and Desire Z Themes and Apps] EdKeys:
I have a copy in my dropbox:

http://dl.dropbox.com/u/17578272/add_tmobile_wifi_calling.zip
[General Questions and Answers] profmed:
Best Rom For Arc S? I'm no expert :D
[General Questions and Answers] olyloh6696:
CyanogenMod! :p
[Galaxy S II Q&A, Help & Troubleshooting] ehmeds:
Hello everyone..

I am a new user of android, bought SG2 few days back.. I have spent a whole day on understanding how to upgrade my gs2 from 2.3.4 to ICS.

The biggest problem i am facing that i cant understand the terminologies and steps in upgrading os.. SO please guide me in easy language, lol :)

Info of my gs2 is..

Model GTi9100

Android Version 2.3.4

Baseband Version I9100XXKI1

Kernel Version 2.6.35.7-I9100XWKI4-CL575468

root@DELL143 #2

Build number GINGERBREAD.XWKI4

Current Firmware PDA:KI4 / PHONE:KI1 / CSC:KI1

(XFM)

Please guide me step by step.. Will be waiting for your reply guys :)

Thanks in advance!
[Galaxy S II Q&A, Help & Troubleshooting] ZACQ8:
aprat from KIES update there are 2 ways,

1) official ICS flash from ODIN, 2) Custom Roms flash from CWM

for official you dont need Rooting,

for flashing Custom Roms from CWM you need Rooting & CWM.

Official Roms :http://xdaforums.com/showthread.php?t=1544487

custom Roms you can find here : http://xdaforums.com/forumdisplay.php?f=1204

rooting and Odin flash guides are there in my signature links

to learn more : http://xdaforums.com/showthread.php?t=1442549
[Galaxy S II Q&A, Help & Troubleshooting] JJEgan:
OP Kies is your official update path download it from Samsung .

Or the XDA path as posted above but you will need to read and understand .

jje
[Galaxy S II Q&A, Help & Troubleshooting] ehmeds:
thank you Zacq8 and Jjegan..

thanks for quick response, suggest me which is the best and less battery consuming ROM for sg2? Official or custom?
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
Neither. No such thing as best. Less battery depends on how you have the phone setup & how you use it (everyone is different). Try some roms out for yourself to find out which works best for you.
[Galaxy S II Q&A, Help & Troubleshooting] ZACQ8:
What suggested by Mistahbungle +

only what we can answer as per the rule is, By flashing official ROM you will not get any suppot from Samsung, by flasing a custom rom you may get support from it's Developer through his thread in this forum.

in development section, there are not only a single post of ROM of each custom Rom thread but there are prolonged discussions on each one, go through them before selecting one...
[Droid 2 Global General] key5000:
[/SIZE][/SIZE]

Start Updated on 7-20-2012

****** Due to heavy download from wordwide users, Dropbox has temporay disabled my Public share because the traffic. ******

I had to created a new PRIVATE share to keep ALL files alive

In-order to download the files you need to have account with

DropBox

and click here

to download

To help keep all links alive, please open new account with Dropbox by click here http://db.tt/AxpJcW9F ,

you will receive 2.5 GB of FREE cloud storage which can acces anywhere, anytime.

End Updated on 7-20-2012

After spend days reading hundred threads on multiple sites, I have come up with a quick instruction in 1 page on how to unbrick D2G and unlock the band to use on CDMA, GSM network such as Verizon, AT&T and T-Mobile. (Sim must be unlocked by calling Verizon or using third parties unlocked from internet search)

All credit will go to the original posters; I'm just combined all together to create an instruction easy for new users plus all the files download are in one place too.

Copy files from step 5, 6, 7, 9 and 18 to SD card before perform "How to" steps below:

How to un-bricked and band-unlock Droid 2 Global:

1. Flash 608 SBF using RSDLite (VRZ_A956_4.5.608_1FF_01.sbf) (press up arrow on keyboard while power up to enter flash mode)

2. Flash Repack_629 SBF using RSDLite (BL=2 BOOT REC CDTf__Repack_629.sbf)

3. Reboot, wipe data and cache (press x on keyboard while power up then press volume Up+Down at the same time )

4. Enable Unknown Source and Development features in Setting (To Bypass activation, press TopLeft, TopRight, BottomRight, BottomLeft (above Emergency))

5. Root D2G withSuperOneClick v2.3.3

6. InstallOtaRootKeeper, 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. InstallDroid 2 Recovery Bootstap.apk then 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

If you have any questions or problems, please post it here so we can help.

Please post

your feedback

here after your phone is unlocked.

Also, please select

your RATING

:good: at the Top Right of this post

Regard,

KEY
[Droid 2 Global General] Boster27:
It worked!!

I am one of the (un)lucky owners of a non-unlockable D2G. I was able to use it to make calls with a SIM interposer (i-smartsim), but wasn't able to get data working on the 850Mhz band (900Mhz worked fine on EDGE, with another carrier). After following this how-to, now I get full speed 3G (H+) on my "locked" D2G using i-smartsim!

I know that I shouldn't use data with the interposer, that it will probably burn out, but I just feel better knowing that I can use data now if I need to :)

Hope this helps, and thank you for the post, key5000!
[Droid 2 Global General] bhigham:
Key5000, thanks for posting this over here. BEH from rootzwiki here, and I was just looking here to see if this topic had been covered here yet.

I also wanted to add a little explanatory note explaining why the different flashing methods need to be used, for those who might wonder why use Rsdlite one time, and EzSbf another.

Rsdlite flashes the radio baseband, and sbf_flash (used by EzSbf) does not flash the radio. So, by flashing 330 with RsdLite, we flash the Froyo band unlock-able radio (actually the complete system, but all we are interested in is the radio). If you try flashing 330 with EzSbf, the radio will not be flashed, Rsdlite must be used.

Now that we have the radio we want, we need to get back to Gingerbread, but if we flash GB with Rsdlite, we will overwrite the radio we need be able to do the band unlock. Since sbf_flash flashes everything except the radio, we are able to use it to get back to a recoverable state (608+629-repack). the 629 repack contains no radio baseband, so it is able to be flashed from Rsdlite.

At this point, if we were to take the OTA update, we would overwrite the radio we are trying to preserve again, so we need to restore a nandroid backup to prevent doing that.

Incidentally, I have a clean nandroid backup of 629, if someone has somewhere to host it. This would effectively eliminate all of the initial rooting steps (1-10) other than the copying of files to the SD card. Let me know, and I can get the file to you.

Hope this is helpful or interesting to someone.
[Droid 2 Global General] chigo17:
This trully works, I rooted My D2g on 2.3.4

:)Thank you Key 5000 for the final summary.

I just rooted, unbanded and now am on AT&T on my Droid 2 Global. and this is my very first attempt at the bootloader of android. Everything works now.

Thank s to everyone, starting from someone from china "my wife got milk", shadow, etc.

Let me contribute from my own experince working on my 2.3.4 version od D2g.

I had issues with:

Rooting with item #5, Superone click and the zip files on #10 and #12.

I had to download a program to run the superoneclick on my computer with the phone attached,

I also had to download clockworkmod from google play store, and finally,

for #12, using the usb method, you need to look up the instruction on booting your computer on USB.

Key5000, please double check the zip files, EZsbf and the band unlock. i had to get them elsewhere, they appear to be invalid. the same files though.

Also double check the item #11 zip file. I had to get it from Shadow's post.

Thanks again. You've made my day.
[Droid 2 Global General] key5000:
All files has been re-upload again.
[Droid 2 Global General] cellzealot:
Nice job! Convoluted but it has to be to accomplish the right sequence of flashes.

Very clever work.
[Droid 2 Global General] hitmantony:
Thanks for the How-To easy to follow and was able to unbrick one of my two phones.

The other phone already has the Band Unlock and is running on .608 I was wondering to upgrade to .629 do I just follow the same instructions but start at step 13, skip the Band Unlock, and use the nandroid from the recovered bricked phone?

By the way can't thank you enough for the unbrick solution.
[Droid 2 Global General] bhigham:
Not sure if there is any benefit to updating to 629 if you don't have to, I don't know what the real differences between .608 and .629 really are (I got my phone with 629 already on it). One advantage to doing this that I can think of would be not accidentally taking the OTA update and getting the baseband overwritten at a later date. There are other ways to prevent the OTA update, such as renaming the updater file.

I am thinking, and someone else might be able to correct me if I am wrong, that in order to update from 608 to 629, without updating the baseband, the proper way would be to flash an updated kernel file, much as the method mentioned at

http://xdaforums.com/showthread.php?t=1345071

and then flash the nandroid backup. I am not sure of the differences between the kernels of 608 and 629, but am thinking that they are different, and that it might cause issues to simply flash the Nandroid backup, without also updating the kernel. For some reason, I am thinking I read that one of the reasons that wifi etc don't work during the unbricking step of 629 is that 608 is running with the 629 kernel, and they aren't completely compatible. In your case, you would be running 629 with the 608 kernel, and you would probably be the first one to ever try that combination.

Someone else can likely fill more in, hope this helps.
[Droid 2 Global General] dabigserver:
Hello, thank u 4 the info, I don't even know how to sbf :s... I really want to unlock the bands but when you say it will brick. Don't worry, I actually worry lol, you mean that rsdlite will brick after flashing and rebooting? Then I have to enter in bootloader again? How it is? Am sorry for my ignorance
[Droid 2 Global General] bhigham:
First off, if you are wanting to unlock the bands, is your phone sim-unlocked? If not, unlocking the bands will not sim-unlock the phone, it just allows an already unlocked phone to work on AT&T or T-Mobile.

Regarding to worry or not to worry, as with anything, there is a potential danger anytime the phone is flashed. The same is true when the phone receives an OTA update from Verizon, it is rare, but there is the potential for mishaps.

In this case, we are deliberately "bricking" the phone temporarily, as it is the only way to get the it rooted and band-unlocked.

After the latest ota update, the .629 update, any attempt to flash the phone to a previous version will "brick" the phone, but since there is a method to recover from the bricking, he says don't worry.

When we flash 330 to the phone, it flashes the software to the phone, but then the bootloader recognizes that it isn't the proper software, so it won't boot past the bootloader. It is necessary to flash 330, as that gives us the unlockable radio. Then, we have to flash .608 using ezsbf (or another method to flash without using rsdlite), to flash back to a recoverable state, without losing the radio. It is still bricked at this point and won't boot past the bootloader, but now recoverable with the repacked .629 sbf. We don't flash the whole 629 sbf, just enough parts of it to enable the phone to work.

After this, the phone is back to a partially usable state, where we can root it, and then restore the backup file, bringing it back to a fully usable state.

Hope this answers your questions.
[Droid 2 Global General] jabberwockish:
It is not difficult. Follow this how-to: http://droid.koumakan.jp/wiki/SBF
[Droid 2 Global General] nyfwireless603:
hi

I think i followed the instruction to do this. But my phone does not work for sim card and I need some help. My phone acts little weird. Can I start this steps all over from #1? Please help. Thanks