Database Info

[q] nexus s 4g cant flash stock plz help!!!!

I can do everything with my phone except for flash stock no matter how many times and ways I try it won't work. Have tried using SW Updater and it gives me the following message:
"Error Occured! Cancel Download!"
I also tried with fastboot and after the phone reboots I get this message:
<waiting for device>
For some reason the phone continues to show these two lines at the bottom of the bootloader screen:
USB Control Init
USB Control Init End
I am really in need of help. Can somebody please help me?

KJOM said:
I can do everything with my phone except for flash stock no matter how many times and ways I try it won't work. Have tried using SW Updater and it gives me the following message:
"Error Occured! Cancel Download!"
I also tried with fastboot and after the phone reboots I get this message:
<waiting for device>
For some reason the phone continues to show these two lines at the bottom of the bootloader screen:
USB Control Init
USB Control Init End
I am really in need of help. Can somebody please help me?
Click to expand...
Click to collapse
Hi,
What are coming from? rooted with what ROM.. what recovery?
And are you trying to flash the newest ICS from stock recovery?
I guess Im just trying to see what you did and what you had before it all happened.
Thanks

Im currently running the [AOSP][4.0.4]Codename Android 2.0.0RC|Fully Open Source+Nightly Builds Rom and I have CWM Recovery and I am trying to flash the OTA ICS Update.

http://forum.xda-developers.com/showthread.php?p=24297394
[OFFICIAL][ROM][CWM] NS4G IMM76D 4.0.4 | Rooted | Zipalign | ETC
This is what u want if ur already rooted
Good luck
Vs Nexus S 4G

I already know how to do everything else, my problem is flashing back to stock because of those messages. I only want to flash back to stock.

I had an issue where fastboot wouldn't recognize my device when I was in bootloader. For whatever reason it worked if I hooked up my phone via usb then rebooted into bootloader.
Anyway you can use this method
http://forum.xda-developers.com/showthread.php?t=1575502
Sent from my Nexus S 4G using Tapatalk 2

Did you install the wrong bootloader by any chance?

KJOM said:
I already know how to do everything else, my problem is flashing back to stock because of those messages. I only want to flash back to stock.
Click to expand...
Click to collapse
That's why I asked for some clarity on ur post.
U want to Unroot and return to stock.
Its a big difference when someone reads and tried to help.
What root method did u use?
Vs Nexus S 4G

@vidaljs, I used the fastboot method to install IMM26D & @psg190, I don't think so.

KJOM said:
@vidaljs, I used the fastboot method to install IMM26D & @psg190, I don't think so.
Click to expand...
Click to collapse
Boot into the bootloader (volume up + power button) and tell me what it says for bootloader version.

It says:
FATBOOT MODE
PRODUCT NAME -HEARING
HW VERSION - D720SPAKE1
BASEBAND VERSION - D720SPALC1
CARRIER INFO - SPR
SERIAL NUMBER - 32************EC
LOCK STATE - UNLOCKED
SELECT - VOL UP or VOL DOWN
EXCUTE - POWER
REBOOT BOOTLOADER
REBOOT
RECOVERY
POWER OFF
USB Control Init
USB Control Init End

KJOM said:
It says:
FATBOOT MODE
PRODUCT NAME -HEARING
HW VERSION - D720SPAKE1
BASEBAND VERSION - D720SPALC1
CARRIER INFO - SPR
SERIAL NUMBER - 32************EC
LOCK STATE - UNLOCKED
SELECT - VOL UP or VOL DOWN
EXCUTE - POWER
REBOOT BOOTLOADER
REBOOT
RECOVERY
POWER OFF
USB Control Init
USB Control Init End
Click to expand...
Click to collapse
Well, that's good that you have the right bootloader. Mine had the same problem, but I accidentally flashed the wrong bootloader. Pretty sure that's why I had no fastboot or USB mount. I had to send mine into Samsung for repairs.

So what's wrong with it?

KJOM said:
So what's wrong with it?
Click to expand...
Click to collapse
With yours? I don't know.
With mine? I don't know.

lol dam

KJOM said:
lol dam
Click to expand...
Click to collapse
Sent my jacked up phone into Samsung. It was unlocked and had TWRP on it (like I said before, no fastboot and none of my computers with any combination of OS/USB cable would recognize the phone). Samsung either repaired or replaced it and it is shipping back to me today.

Thats good for u. But I still can't flash stock, other than that, I'm doing great with mine.

RESOLUTION: Assuming you've installed the correct Samsung ADB drivers, you will have had to go to Device Manager, and tell it which driver to use. Good job at getting to to the fastboot screen! You're almost done.
At this point, (on fast boot) open up Device Manager again on your computer. Now your phone is being recognized as something completely different: Android 1.0 was what mine said. Right click on it, 'update driver software', 'browse my computer for...', 'let me select from a list of...", then choose "ADB Interface" from the list. If ADB interface is missing from the list, you haven't installed the drivers.
It will then give you a list of ADB Samsung phone drivers to choose from. I just chose the most updated ones (2012 was at the end of the strand of information about it, as opposed to 2010 which was further down). The second you click next, your phone (assuming you still have the command prompt up on your computer, saying its searching or waiting for your phone) will start to fly through the process of returning you back to stock.
DONE!
Good luck.

Thanks jackharvest. I didn't know Samsung had their own ADB drivers. That was the key! After I configured Windows Device Manager, as you indicated, to use the Samsung driver, all I had to do was run the windows batch file "flash-all.bat" which I had downloaded from google's "Factory Images for Nexus Devices." Unfortunately, their instructions don't tell use about the steps you identified!

[Q] Help Needed: bricked or not and what to flash with Odin

Hi,
I have an issue with a Nexus S i9023 of a friend
I installed the latest stock ICS CF_YAKJU_IMM76D some months ago and everything was fine.
I broke the glass of the screen and it was substitued: after a couple of months, the phone entered in a bootloop.
I tried to access recovery but was impossible, I could get to Fastboot and Download mode but choosing recovery from the first started bootlop again.
I flashed a latest CWM in fastboot via adb but no joy.
On top of that, handset behaviour is strange because only 1 on 20 times it is recognized by the PC as a Samsung device, in all other cases it is a "unknown device".
I remove all drivers from Windows and reinstalled the naked version, but again only sometimes I get it... I found out I need to have connected another handset (my HTC currently...) to have it recognized!
Now I can enter in download mode using the USB jig and I can see it from Odin, but if I use the
CF_YAKJU_IMM76D_full.tar
I get "verify image ipbl (fail)" on the handset.
If I use
CF_YAKJU_IMM76D_nowipe_nobootloaders_norecovery.tar
I get an "invalid volume size"
Do I have an hardware issue here? Some partition/internal memory with failure?
What else can I try to flash via Odin?
Obviously now after the fail I can't even get fastboot...
I also tried Unbrickable resurrector under Linux but it doesn't recognize the handset when I connect it.
Any suggestion? :crying:

SergioBigred said:
Any suggestion? :crying:
Click to expand...
Click to collapse
Ok, update. Using this thread I was able to flash via Odin 1.82 the 2.3.4
However I am still in a bootloop and I can't get fastboot but not recovery... and in fastboot I can't via USB the handset because it says "usb device not recognized"

Galaxy Fit GT-S5670 - MIBIB Download & SETUP CONNECTION

This thread is for those friends who are new to android.
I found that many of us, who wants to move from custom roms to stock roms through odin, have faced some big problems like MIBIB download or SETUP CONNECTION . This happened with me as well... when I moved from cyanogenmod to froyo. So, based on my experience, here are some suggestions which may help you:-
When you select the OPS file, check its name. Its name should be "BENI_v1.0.ops" (without quotes) otherwise odin will not show your device's model number at the top and will stop at MIBIB Download. Please Note that as soon as you select the ops file, odin will show the model number of the device in its title bar regardless of whether the phone is physcally connected to PC or not. In my case, the mbib download problem is solved by renaming the OPS file. You can now install the stock firmware as normal.
If odin is showing the message "setup connection" and your Galaxy Fit is still connected to PC (i.e. COM port mapping box is yellow), then try another stock firmware. In my case, odin stopped at setup connection when I was installing froyo, so then I tried the One Package Gingerbread firmware. And Odin successfully installed it(you can also try another usb port). After then, I went for Froyo once again & Odin successfully installed it too.
Please remember that doing things unknowingly may damage your device. Once the phone is in DOWNLOAD MODE, it can not be switched on either normally or in recovery. It can only enter in DOWNLOAD MODE. I had the two firmwares when I did all this.
Hope this helps...
Press thanks if I helped you...

U saved my day ....

stuck at mibib download HELP!!
sir i am stuck at this mibib download....my file name "BENI_v1.0.ops" is exactly same as yours but my odin is not moving further than mibib and whne i tried to go to recovery mode its show a sign displaying a phone disconnected to a pc monitor.....is this sign is harmful for my fit???
Plzzz sir help me out.....

Shubhrank said:
sir i am stuck at this mibib download....my file name "BENI_v1.0.ops" is exactly same as yours but my odin is not moving further than mibib and whne i tried to go to recovery mode its show a sign displaying a phone disconnected to a pc monitor.....is this sign is harmful for my fit???
Plzzz sir help me out.....
Click to expand...
Click to collapse
Note that if ur usb port malfunctions then odin will not proceed further. I recently noticed this major issue. Other errors like "checking plact platform verification" appear due to usb error. Try another pc or laptop(recommended).
1st & 4most, it's necessary that u tick "USB debugging" under "Android Settings->Application Development" b4 going to download mode.
Also, disable any antivirus, firewall...uninstall kies...& at last install/re-install ur Samsung Mobile Drivers. Use Odin 4.38.
The screen u mentioned appears when u exit download mode & try to switch it on either normally or in recovery. Don't worry...!!
1. Take out & re-insert battery.
2. Press "Volume Down & Home & Power button" & you'll again enter downloading mode.
If u want...I can provide u the firmware files that I always use
Hope this helps...!!!

MBIB and setup connection
I have got the same problems of MBIB download or setup connection error and after trying to on it in recovery mode it display image of mobile phone not connected to pc.
Please sort my problem ASAP, as I have only that one phone.:crying:crying:

gaurav.gupta180687 said:
I have got the same problems of MBIB download or setup connection error and after trying to on it in recovery mode it display image of mobile phone not connected to pc.
Please sort my problem ASAP, as I have only that one phone.:crying:crying:
Click to expand...
Click to collapse
Check ur pm.

gaurav.gupta180687 said:
have got the same problems of MBIB download or setup connection error and after trying to on it in recovery mode it display image of mobile phone not connected to pc.
Click to expand...
Click to collapse
Me too. Except on a GT-S5830i. Any help anyone? I have a .pit file etc but not sure what it is. Can't see the device in fastboot either

Feiteng H7100 Bricked

Hello,
I managed to brick my new Feiteng H7100 phone, i flashed wrong rom to it and got a greenish screen when trying to start the phone.
So i formatted the phone in SPFT tool "Format whole flash" and from then it stopped responding, i cant start the phone anymore, and the charging indicator wont light up when charging.
When connecting the phone to try and reflash it the computer recognizes that i have connected the phone to the computer, but flashing doesnt work.
It is the S7180 with 1GB ram.
I hope there is a solution to it and it can be fixed, iam not sure if this can be called had brick or soft brick.
Was very close to throw it out of the window yesterday, but then thought i can give it a chance
Thanks

Have you found a solution to the problem? I have a similar problem. Dead after flash ROM
please help me
Thanks

Mine is dead also
jemmars said:
Have you found a solution to the problem? I have a similar problem. Dead after flash ROM
please help me
Thanks
Click to expand...
Click to collapse
Same mine is completely dead after I flash it - Its not recognized by the originally drivers in windows 7. Showing up as an Unknown Device.

if it is showing up as an device, it isn`t bricked. you need to get the right firmware and flash it again. force install the drivers for the unknown device or take the drivers for Rom you flashed. (e.g. flashed wrong preloader from ZTE to a Star device, need to install ZTE drivers)

While I don't know the specifics of the Feiteng H7100, I've "bricked" many an android phone and tablet. Fortunately it's usually easy to fix.
1) Reboot the device into CWM Recovery Mode (usually by holding power and volume buttons at the same time)
2) Plug it into your computer & run "adb devices" - if you device comes up as a Recovery device, then you're probably home free
3) Run an "adb push newly_downloaded_cyanogenmod_rom.zip /sdcard/" - the data location (/sdcard/ in this example) might vary depending on your device
4) Wipe Cache
5) Install Zip from sdcard and choose your new_rom.zip

[Completed] [Q] Interrupted flashing process

Hello friends,
I was using a General Mobile etab4 tablet,
rooted,
bootloader locked,
not backed up, i tried but apps wont recognize the brand,
the stock rom is not available anywhere but I managed to find some custom ones.
This tablet is actually a given by government for educational purposes, and it has no download mode, I can only initiate recovery mode with volume up+power button combo, and there is no sd card in it.
Here is what happened. It was running with problems so I decided to flash a custom rom I find on this forum. First I tried flashing using adb sideload. I got an error message "Installation aborted" with no error codes after verification step but it does not state whether verification is failed or not. I don't know what actually failed. Then I tried to flash it using adb shell as root (the system image was in /sdcard directory). It freezed, I exit the shell using Ctrl+C command. Then whenever I try to start shell i got "error:closed" message. I see my device with adb devices with sideload, but it is not seen in fastboot devices.
When I try to open it, I guess it enters in a small boot loop (screen flickers multiple times with brand name on it) and after some time I got dead android with no command written.
I tried,
reflashing it again with Android AIO Flasher,
use fastboot to unlock bootlader (it says "waiting for device") although adb devices sees it,
re-installing the adb drivers after uninstalling them,
disassembling the device to see if I can detach memory to edit it and to see if disconnecting the battery helps,
I even used a simple jig to see if i can initiate download mode (know it works for specific devices but you know hope)
Apparently, I messed up the device but the hardware must be all fine. So I think there must be a way out. What can you suggest, I wish I have unlocked the bootloader. I can send the pictures of its motheboard it helps,
Thanks in advance.

Hi,
Thanks for using XDA Assist please post here Android Q&A, Help & Troubleshooting
Good Luck!