Hello,
I have LG G2X with Gingerbread 2.3.3. I decided to root it. So I came to this site, realised that I have to first install ClockWorkMod using NVFlash.
So I have followed the given instructions very meticulously. Everything seemed to go as it should until the part where I should click Flash CWM ...
When I do so I get the message USB DEVICE NOT FOUND.
But I have checked in device manager and have actually seen NVIDIA USB Boot-recovery driver for mobile devices and have even heard the toton sound when the phone is connected.
Please help me!!
I'm pretty sure u can root w/out nvflash. Nvflash is so u can flash roms. I used a program called super one click to root but that was a long time ago and not sure if it's compatible anymore
Sent from my LG-P999 using Tapatalk 2
hippiesky said:
I'm pretty sure u can root w/out nvflash. Nvflash is so u can flash roms. I used a program called super one click to root but that was a long time ago and not sure if it's compatible anymore
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
I have tried using super one click but I get stuck at step 7 : waiting for device !! So no luck there either.
Is it possible that the drivers are not working because I am on 64bits windows 7 ?
medwatt said:
I have tried using super one click but I get stuck at step 7 : waiting for device !! So no luck there either.
Click to expand...
Click to collapse
With Super One Click is USB debugging enabled?
Sent from my HTC Ruby using xda app-developers app
mansa_noob said:
With Super One Click is USB debugging enabled?
Sent from my HTC Ruby using xda app-developers app
Click to expand...
Click to collapse
Yes, of course. This is not the first time that I am rooting something.
Since the nvflash reports that no usb device the only logical explanation is that the driver is not installed. I typed in the command line adb devices when the phone is turned on and I got the positive reply.
When I entered into recovery mode, I didn't get the same reply.
You gotta try reinstalling the apx driver. That seems to be the part that's not working.
Sent from my Nexus 5 using XDA Premium 4 mobile app
So this is what I have done:
1. I am using a clean windows 7
2. I installed LG drivers
3. I turned off the phone, removed the battery, held the volume up & down buttons and immediately entered the S/W screen. Also I noticed that windows has not been able to find a driver.
4. I entered 'Device Manager' and looked for the device. I didn't see 'APX Device' as is in the written tutorial. Instead it was labelled 'LG Mobile USB Modem'.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. When trying to install the driver I was faced with two choices. I chose the second.
6. It installed as is shown.
7. I then disconnected the usb, pressed and held the volume up & down buttons and once more entered the S\W upgrade screen.
8. I clicked the OneClickRecoveryFlasher.exe and this is what I got.
I've repeated the process a lot of times.
I have to agree with Twitch. Reinstall APX drivers. I recall doing that a few times before I got everything working....although I was a complete newb and had no idea what i was doing lol.
Also, make sure you follow the directions as pertains to shutting the phone off, removing the battery and holding the volume keys in when you first plug in your phone via USB.
Pain-N-Panic said:
I have to agree with Twitch. Reinstall APX drivers. I recall doing that a few times before I got everything working....although I was a complete newb and had no idea what i was doing lol.
Also, make sure you follow the directions as pertains to shutting the phone off, removing the battery and holding the volume keys in when you first plug in your phone via USB.
Click to expand...
Click to collapse
Please look at the attached images. Everything seems to be installed.
Check all the images as see what is in my computer which is causing the problem.
See the attached images please.
Some people have had success with the battery in. I can't remember exactly but I thought the sw upgrade screen came up after the flashing part.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Seems like you installed the APX driver for the modem hardware. This it's not the same. APX shows as APX and nothing else.
Uninstall, rinse, repeat.
Sent from my HTC Ruby using xda app-developers app
mansa_noob said:
Seems like you installed the APX driver for the modem hardware. This it's not the same. APX shows as APX and nothing else.
Uninstall, rinse, repeat.
Sent from my HTC Ruby using xda app-developers app
Click to expand...
Click to collapse
I have been curious about it. I have a laptop and a desktop and in both I see 'modem' instead of APX. Maybe thats where the problem lies. Is there a setting in the phone where one can disable the phone to appear as a modem ?
Ok. Since I have a another computer that I can always revert to a previous state I tried to do things all over again. This time I installed the LG drivers first. When the phone was on everything was detected just as normal. Because this time I have already installed the LG drivers when I booted into S/W screen the phone was detected as normal. That is no LG USB modem showed meaning that the modem driver has already been installed.
I should have expected to see APX device with a little yellow triangle but I saw nothing. I really have no idea why.
Is there a switch or an internal setting that asks where one can set the phone to boot as an APX device. Its really baffling why this is happening.
So now its a question of making the phone boot as an APX device !! I would have wanted to downgrade the phone to Froyo since superoneclick can be used to root it but it seems that I first have to install CWM first.
Is there another way to root the phone if it failed to boot as an APX device because all I want to do is to run some apps that need super user privileges.
When you're in apx mode there shouldn't be at a s/w upgrade screen. I think that's the part you're missing. There are different button combinations that put the phone in different states. I can't remember that well but I think apx is just blank screen.
Sent from my Nexus 5 using XDA Premium 4 mobile app
medwatt said:
Ok. Since I have a another computer that I can always revert to a previous state I tried to do things all over again. This time I installed the LG drivers first. When the phone was on everything was detected just as normal. Because this time I have already installed the LG drivers when I booted into S/W screen the phone was detected as normal. That is no LG USB modem showed meaning that the modem driver has already been installed.
I should have expected to see APX device with a little yellow triangle but I saw nothing. I really have no idea why.
Is there a switch or an internal setting that asks where one can set the phone to boot as an APX device. Its really baffling why this is happening.
So now its a question of making the phone boot as an APX device !! I would have wanted to downgrade the phone to Froyo since superoneclick can be used to root it but it seems that I first have to install CWM first.
Is there another way to root the phone if it failed to boot as an APX device because all I want to do is to run some apps that need super user privileges.
Click to expand...
Click to collapse
Twitch is right. APX is achieved with battery out, both vol buttons held and plugging in the USB. Don't let go of the buttons until you have installed the driver (the exclamation mark is gone).
Sent from my HTC Ruby using xda app-developers app
When you're in apx mode there shouldn't be at a s/w upgrade screen. I think that's the part you're missing. There are different button combinations that put the phone in different states. I can't remember that well but I think apx is just blank screen.
Click to expand...
Click to collapse
Surprising that the only thing I get when I do what you say is the S/W screen !! What am I doing ?? I am really at a loss now !
4. Hold Volume Up and Volume Down at the same time keeping them held down. (Keep them held until you see the "S/W Upgrade" screen on your phone after you complete step7!).
Click to expand...
Click to collapse
The thing is I always end up at the S/W screen and I've been trying for the past days.
I write ashamed. The problem seems to have been from the start I not pressing the up button properly. Imagine fretting over so many things when it was just a button not pressed properly. I am sorry to have wasted your time. However I think had it not being point out that I shouldn't be seeing the S/W screen I wouldn't have known I had been doing something wrong. I would have been the 'Einstein fool' : doing the same thing over and over and expecting a new result.
Thanks again. Just one last question, in most of samsung phones, the pull down menu (the one that slides from the top) has Wifi, Bluetooth . . . it seems painful to always have to go to settings or some widget to change these settings. Is there some way to put them in the pull down menu.
Glad you got it working! The toggles you're talking about I think are available in cm7 but to be honest I don't even have this phone anymore so I can't be certain. If you're planning to keep it stock you can try the power toggles app or something like that.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Related
Yesterday, I tried a oneclick root application but turns out only to complete the mission halfway. After pushing volume up and power button, I see
Lock state- unlocked, but Rom manager told me I'm not rooted
Today I found several thread, including the sticky thread on the top of the forum page, to root it the regular way. However, when I proceed to
fastboot oem unlock
nothing happens on the phone screen
Then I tried next step
"fastboot flash recovery 3024v3-i9023.img"
the picture of what happened is attached
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
still nothing on the phone screen
I try the recovery option on the phone, but few seconds later exclamtion sign and android robot show up. I'm able to get out of it and go into android system recovery, which only has 4 option
reboot system now
apply update from /sdcard
wipe data/factory reset
wipe cache partition
I tried both wipe option but they are both fruitless except wiping out all my data. They didn't change the lock/unlock property.
My i9023 is on 2.3.6, don't know if it matters.
So here is my situation, this is my first attempt to root the phone.
Guys help me please.
Did you get it rooted?
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=1007782
Sent from my Nexus S 4G using xda premium
Look into my posts from my profile and look into my Topics Thread for rooting method... works with all Nexus S. Just follow the video.. download the file in description names NexusSRootNew ... just follow the video and Ull be fine. I used it and I'm doing well =]
Sent From In between Your Moms Boobies
Look at your screen shot. You left out the "flash" in the fastboot command.
irishrally said:
Look at your screen shot. You left out the "flash" in the fastboot command.
Click to expand...
Click to collapse
Lol good call.. missed that
Sent From In between Your Moms Boobies
irishrally said:
Look at your screen shot. You left out the "flash" in the fastboot command.
Click to expand...
Click to collapse
I'll try it later, thanks.
irishrally said:
Look at your screen shot. You left out the "flash" in the fastboot command.
Click to expand...
Click to collapse
Still fails. I get "wait for device" on the computer screen forever and get "fastboot status fail invalid command" on the bottom of the phone
mikel719 said:
Did you get it rooted?
Have you tried this?
h ttp://forum.xda-developers.com/showthread.php?t=1007782
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Tried and fail.
Did you install the pda drivers?
Sent from my Nexus S 4G using xda premium
YourMainDude said:
Look into my posts from my profile and look into my Topics Thread for rooting method... works with all Nexus S. Just follow the video.. download the file in description names NexusSRootNew ... just follow the video and Ull be fine. I used it and I'm doing well =]
Sent From In between Your Moms Boobies
Click to expand...
Click to collapse
It's oct 13th post right？Your youtube link fails. Several videos are alike, so I've got the idea of rooting but it simply fails after I input the commands, nothing happened on the phone screen and on computer it says wait for device
taylorzhang said:
It's oct 13th post right？Your youtube link fails. Several videos are alike, so I've got the idea of rooting but it simply fails after I input the commands, nothing happened on the phone screen and on computer it says wait for device
Click to expand...
Click to collapse
Go into my profile and look in my Topic Theads posted> Rooting Nexus S For Noobs... follow the steps and ill 100% guarantee you that Ull root it...
Sent From In between Your Moms Boobies
mikel719 said:
Did you install the pda drivers?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
You reminds me, thanks. However, instead of nothing happens, it now shows failed. Screen capture is attached.
wait... u gotta update your drivers man.. ur computer needs yo recognize your phone lol
Sent From In between Your Moms Boobies
YourMainDude said:
wait... u gotta update your drivers man.. ur computer needs to recognize your phone lol
Sent From In between Your Moms Boobies
Click to expand...
Click to collapse
Sent From In between Your Moms Boobies
your youtube link direct me to wrong place. Actually I've seen video that use Nexusrootnew.zip maybe that's the one you want me to watchbut I the zip I downloaded is 4kb and obviously didn't work...
No matter how I try, it's always android 1.0 device...
Just in case we are missing the obvious, when you run your fastboot command, is your phone plugged into your computer via usb, and with your phone on the bootloader screen (power button + volume up when your phone is off)?
also, try:
fastboot devices
Guys, finally get it rooted and installed cm7.1. But the driver still seems to have some problem. It still reads android 1.0 in the device manager on the computer but the cwm is flashed in accidentally. Everything after is easy.
i tried to flash a new rom using clockwork. something went horribly wrong, and now it just loops between the samsung screen to a colorful tapestry of bull**** back and forth. i tried searching the forums for similar problems, hopefully finding a solution in the process. it seems that odin is the answer, however when i put my phone into download mode, it odin doesnt detect it. at this point i could care less what rom i have installed on my phone, i just want it to work again, so if one of you more kind hearted devs wanna help this technologically ignorant bastard out, it would be greatly appreciated. thank you and god bless.
jwalters1123 said:
i tried to flash a new rom using clockwork. something went horribly wrong, and now it just loops between the samsung screen to a colorful tapestry of bull**** back and forth. i tried searching the forums for similar problems, hopefully finding a solution in the process. it seems that odin is the answer, however when i put my phone into download mode, it odin doesnt detect it. at this point i could care less what rom i have installed on my phone, i just want it to work again, so if one of you more kind hearted devs wanna help this technologically ignorant bastard out, it would be greatly appreciated. thank you and god bless.
Click to expand...
Click to collapse
I've seen where ODIN doesn't detect the phone if it's not in the same USB port as before. Taking ODIN out of the picture for the moment, when you plug the phone into the USB port, does Windows (I'm assuming Windows here) see anything (phone, USB storage device, unknown hardware, etc)?
jwalters1123 said:
i tried to flash a new rom using clockwork. something went horribly wrong, and now it just loops between the samsung screen to a colorful tapestry of bull**** back and forth. i tried searching the forums for similar problems, hopefully finding a solution in the process. it seems that odin is the answer, however when i put my phone into download mode, it odin doesnt detect it. at this point i could care less what rom i have installed on my phone, i just want it to work again, so if one of you more kind hearted devs wanna help this technologically ignorant bastard out, it would be greatly appreciated. thank you and god bless.
Click to expand...
Click to collapse
Sounds like you attempted to flash a gb ROM on froyo bootloaders... Seeing that you can get into dl mode you should be able to get into recovery mode, if so the easy fix is to flash a froyo ROM or restore your nandroid backup(you did backup, right?)
Sent from my SGH-T959V using xda premium
when i plug in the phone to the computer it prompts me to new hardware detected, and wants to search for software to install it with, but it invariably fails because it cannot find the right drivers, and yes im using windows xp
jwalters1123 said:
when i plug in the phone to the computer it prompts me to new hardware detected, and wants to search for software to install it with, but it invariably fails because it cannot find the right drivers, and yes im using windows xp
Click to expand...
Click to collapse
Ok, cool. Check the Bible for driverd or download and install Kied Mini from Samsung for the right drivers. After that ODIN should see the phone.
Once that works, check the.Dev section for Ravers KJ6 ROM (it's stock Gingerbread).
Sent from my SGH-T959V using XDA App
it reads it as "serial gadget"
Even after installing the right drivers?
Sent from my SGH-T959V using XDA App
yes i backed up and your totally right about what i did, thank you soooooo much, im gonna try it and see if it works.
ok so i got the right drivers, and now odin is detecting the device. however im runing the gb starter pack and after i try to run odin it fails me and says in the message box cant open the serial (com) port. any ideas?
Reboot? Plug into different port?
What version on odin?
Sent from my SGH-T959V using xda premium
i got it all straightened out, phone is back up and fully operational, i really appreciate the help, that was easier than i anticipated it was going to be.
Awesome, glad you got it working.
Sent from my SGH-T959V using XDA App
for future reference, you can still get into recovery if you soft bricked. from there, you can reflash things. its awesome. lol.
jager555 said:
for future reference, you can still get into recovery if you soft bricked. from there, you can reflash things. its awesome. lol.
Click to expand...
Click to collapse
No. You can get into download mode if you're soft bricked. Recovery is gone when you're soft bricked.
i've done it multiple times when i soft bricked/bootlooped ftw on drhonks kernels.
jager555 said:
i've done it multiple times when i soft bricked/bootlooped ftw on drhonks kernels.
Click to expand...
Click to collapse
bootloops are not soft bricks. That's boot looping.
Soft bricks displays the logo like at the top of my One-Click UnBrick app.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This logo is a Samsung imposed boot lock. the only way to get out of this mode is to interface with the Loke protocol.
if it goes into recovery mode it's not bricked. It's operating, and at least two operating systems have loaded.. The SBL contains an operating sytem accessible by UART and generally interfaced via Loke protocol, The Kernel contains recovery mode.. That's hardly bricked.
I can see calling the phone--/!\--pc display bricked because it physically wont do anything at all even though you can still access the SBL> prompt via UART but most people don't know anything about that. Recovery mode is a fully operational device that just won't load Android. Boot looping says there's a problem loading the Linux or Android layers.
Hard brick-no screen action at all, hardware recovery solution
soft brick-won't do anything, but displays something on screen, software recovery soloution
boot looping-loops through boot cycle and recovery is generally available, multiple recovery solutions are available.
There's a big difference and a large variety of what is called bricked... However, it's not functionally equivilant to a brick when you can click buttons and navigate interfaces.
I thought the starter pack was for cwm. Odin jk1 kernel, reboot into recovery and install zip (starter pack), enable voodoo and roll.
Sent from my SGH-T959V using XDA App
oh gosh im having huge trouble with my phone
Hello all,
Yesterday I was trying to flash JB, flash it successfully but then when i need to flash gapps the rainbows inside recovery was so annoying that i try to flash a GB bootloader, I think because the driver or something else the flash wasn't right and since then I got a expensive paperweight. Trying to boot in download mode the phone turn on showing a completely white screen for about 3 seconds then the phone turn off and thats is a eternal loop. turn on > white screen > turn off. When the screen is white ODIN and Heimdall recognize the phone but the device simply turn off after seconds so is impossible to flash something.
Today i got a JIG MicroUSB try to boot in Download Mode with it but does not work.
Help I read several threads along XDA but nothing could help by now.
Thanks in advance
I sure hope that you tried flashing some other things using Heimdall or Odin before using your choice of software to flash bootloaders.
In this state you're in, have you tried the battery pull, hold volume buttons, plug in usb, put battery back in, continue holding power button method to enter download mode?
If you can get to download mode this way, you aren't bricked.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Seems to me you have definitely bricked it :s A bootloader flash is practically the only way our phone can be bricked. That is why it is recommended to flash other things first to make sure odin has no issues with drivers and such
Sent from my sweet and buttery Infuse
Sure I flash another things, and yes I try all the combo buttons to enter in download mode. Nothings happens i can't get into download mode.
In case that I hardbrick my device there is another easy solution.
andros11 said:
Seems to me you have definitely bricked it :s A bootloader flash is practically the only way our phone can be bricked. That is why it is recommended to flash other things first to make sure odin has no issues with drivers and such
Sent from my sweet and buttery Infuse
Click to expand...
Click to collapse
You may be right, but we don't know for sure that he's bricked yet. We've seen several close calls where the Infuse has made it through - even after a borked bootloader flash.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
p|p3 said:
Sure I flash another things, and yes i try all the combo buttons to enter in download mode. Nothings happens i can't get into download mode.
Click to expand...
Click to collapse
Can you confirm that you pulled the battery?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
jscott30 said:
Can you confirm that you pulled the battery?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Yep a lot of times.
You mention that Odin sees the device for a moment before the device loops. As a last ditch effort, you may be able to issue an "adb reboot download" command using adb on your PC. No guarantee that this will work, but it's worth a shot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Gotta try to issue the command at the same moment that Odin sees the device.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
jscott30 said:
You mention that Odin sees the device for a moment before the device loops. As a last ditch effort, you may be able to issue an "adb reboot download" command using adb on your PC. No guarantee that this will work, but it's worth a shot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Bro i'll be so glad if may you can guide me on this or give a link. Much thanks. :laugh:
p|p3 said:
Bro i'll be so glad if may you can guide me on this or give a link. Much thanks. :laugh:
Click to expand...
Click to collapse
You can download what you need for adb from here: http://d-h.st/2mi
Extract the zip package, browse to the unzipped folder where you'll see adb.exe and some other files. Place all of those files in the Windows folder on your C:\\ drive. Then, press the Windows key on your keyboard + R so that the "Run" prompt appears. Type cmd and then press enter. In the command prompt, type this just as Odin sees your device (keep an Odin window open to be sure):
Code:
adb reboot download
The problem is, if both your primary and secondary bootloaders are screwed up, you may never get into download mode. It's worth a shot to try, though.
I agree jscott, I believe there's still hope !
I have managed to rescue my infuse from some dark moments.. once I used this one-click unbrick and I managed to save it.
See if you have my same luck with it
Through ADB Shell was imposible that recognize the device, JAVA One Click works for a moment like Odin but the device desconnected so is not much what i can do. Here post a PIC of what a can reach through ODIN so my question will be if i can make ODIN doesn't check MD5's and flash direct or something similar.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyway for now i aprecciate all your answers, i'm sure that out there there is a solution.
p|p3 said:
Through ADB Shell was imposible that recognize the device, JAVA One Click works for a moment like Odin but the device desconnected so is not much what i can do. Here post a PIC of what a can reach through ODIN so my question will be if i can make ODIN doesn't check MD5's and flash direct or something similar.
Anyway for now i aprecciate all your answers, i'm sure that out there there is a solution.
Click to expand...
Click to collapse
Sorry, but neither Odin or Heimdall will work unless you are able to get the phone into download mode. If it turns out that you really have borked the bootloaders, you won't be able to get into download mode. Someone will have to make a jtag repair like in the video below to restore your phone. The guys in this video are reputable and can fix it.:
http://www.youtube.com/watch?v=H4zwn_HMTek
jscott30 said:
Sorry, but neither Odin or Heimdall will work unless you are able to get the phone into download mode. If it turns out that you really have borked the bootloaders, you won't be able to get into download mode. Someone will have to make a jtag repair like in the video below to restore your phone. The guys in this video are reputable and can fix it.:
http://www.youtube.com/watch?v=H4zwn_HMTek
Click to expand...
Click to collapse
Thanks man, yep looks like I screw both bootloaders, unfortunately the guys in the video are in the states but I from Colombia so may be difficult and also expensive send my phone for that fix, anyway today looks like i find someone that could fix my phone using the JTAG cable and box for about USD$50.
Any solution that finallly find to fix my phone i'll be posting here.
Here's a thought have you tried a different USB cable and USB slots. I have 2 phones one likes to connect to front of my PC the other in the back. Plus USB cables get worn out a new one may connect better.
Sent from my SGH-I997 using xda premium
Try taking your battery out for a few hours..or better yet, a day. Charge your battery fully using an external source or use a different fully charged battery, after a day and then try again.
darkchyldx101 said:
Here's a thought have you tried a different USB cable and USB slots. I have 2 phones one likes to connect to front of my PC the other in the back. Plus USB cables get worn out a new one may connect better.
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Did it same result, definitely its not the cable. Thanks anyway
qkster said:
Try taking your battery out for a few hours..or better yet, a day. Charge your battery fully using an external source or use a different fully charged battery, after a day and then try again.
Click to expand...
Click to collapse
Did it too, same result thanks to you too.
JTAG will be
Did you have success restoring with Odin/Hiemdall???
You should of started off fresh, a complete wipe/restore and then the bootloaders <(assuming you had success with
wipe/restore....) It sounds like a JTag is ur only option
I was flashing a kernel and my cord came loose handbills couldn't get anywhere either. Didn't get white screen just a picture of a phone some dots a triangle more dogs and a computer. I found something called one click unbrick. I know you are a different situation than I am but it's worth a shot maybe.
This post brought to you by the letters Paranoid, Ice, Cream and Sandwich.
Hi all,
After using the Xoom 2 for a while as stock, and having experience rooting and installing custom ROMs to android phones I have, I decided to root my Xoom 2. I used Dan Rosenburg method and all was ok, got SU and installed Titanium backup and did full backup of system + user data. I know its always a good idea to backup
I have been on the lookout for a custom ROM for this device for a while but the bootloader is still locked and there is (to my knowledge) currently no way to unlock it, so that was out of the question.
After rooting and still having lag/performance issues, I decided to use ES File explorer in root mode to rename a few of Motorola's bloatware apps with the <insert bloatware app name>.apk and .odex to <insert bloatware app name>.apk.bak and .odex.bak.
I was following a list of apps that had been trial-removed by a developer and he had success. (I can't remember where I found the list).
All was still ok.
All these apps were in ~/system/apps by the way. I then renamed one starting with Moto, can't remember exactly, thinking it was bloatware, and the system crashes and now I am stuck in a boot loop and I can't access anything other than Fastboot Flash Mode, and even to get to there, I have to let it run dead flat, insert charger, wait for it to get to about 10%, then hold vol down key whilst pressing power. I have tried getting to recovery mode multiple times following instructions on motorola site, but each time it just gets stuck in boot loop.
Anyone got any ideas on how I could fix it?
I'm not really sure on how to use fastboot program on my PC, but when i enter "fastboot devices" in to command it just shows what looks to be a serial number. And "adb devices" returns a blank list, ie. not recognising anything plugged in.
Thanks in advance.
Hold down both vol + and vol - then press and hold the power button. Should take you to recovery mode. Pressing vol - to scroll and vol + to select. May have to do a factory reset if you have accidently edited a system file. Re-root install TB and hopefully your back up is still there...
Edit: im also an aussie telstra branded mz616 and have had to do this before so it will work for you.
Sent from my XOOM 2 using xda app-developers app
Thanks for the reply, what you said did help somewhat as I was able to get to to the boot menu. Problem is now, when I go to Recovery mode, it comes up with three following:
Invalid Flash Mode (S) (Boot Failure)
0A.6C (sha-c79f1fc, 2011-12-19 11:35:56)
eMMC Info: Size 32G
Device is LOCKED. Status Code: 0
Battery Low
Cannot Program
Connect USB
Data Cable
Invalid CG HAB (CG: mbr, status: 0X0056)
Any ideas?
Sent from my Sensation using xda app-developers app
Also, I think it may be doing that because, before I found out how to bring up that menu (because the poor instructions I followed on the Motorola web site) I tried using fastboot mode to flash a recovery image I found on the internet and some commands in the batch file were successful but some failed.
If I didn't know any better, I think I may have bricked it.
I may be up for a new motherboard for it
: (
Sent from my Sensation using xda app-developers app
Dont worry about the flash failure i have same thing from my noob days not realising i couldnt actually flash anything to it....
When you hold down all the buttons it should appear with a screen showing some info plus a menu with options to reboot normally, reboot in safe mode, wipe data and so on. Hit wipe data. And it will perform a factory reset.
Make sure you are hitting vol - vol + and then the power button last. Not all at the same time.
The screen you described is basically like download mode. Not the recovery screen.
Sent from my XOOM 2 using xda app-developers app
---------- Post added at 01:33 AM ---------- Previous post was at 01:28 AM ----------
If you manage to get to recovery and wiping everything doesn't work a new board is probably your best bet.
Tbh i would chuck the xoom 2 and put some cash towards a tab with flashing abilities. Or you could wait till at some point in the future for motorola to bring out a bootloader unlocking tool.
Sent from my XOOM 2 using xda app-developers app
Ok, thanks heaps for your ongoing help. Which one of these options would be safe mode?
Screen says:
Boot Mode Selection Menu (0A.6C)
Vol Up Selects, Vol Down Scrolls
Available boot modes:
Normal Powerup
Recovery
AP Fastboot
BP SBF Flash
BP Only
BP HW Diag & Boot AP
BP Tools
I tried going into a few of these and most of them end up leaving me on the Fastboot screen I described before. One of them, can't remember exactly, I think it was BP Only, leaves me with just the red Motorola logo and stays there.
I think I'm running out of options as the battery level its low and it doesn't seem to want to charge... : (
One last thought, its there a way I could reset/ wipe it using Fastboot, as that seems to be the only thing I can use...
Edit: The other thing it does other than Fastboot mode is comes up with a similar screen saying Invalid Flash Mode (S) (Boot failure) up the top... The rest of the screen looks like Fastboot mode
Sent from my Sensation using xda app-developers app
Just a general question.... If I was to use Fastboot to erase all the partitions, in effect all I could access would be Fastboot and nothing else, correct? And if so, would I then be able to flash a new recovery.img file to then use? Or for that matter, a new system.img and boot.img and the rest? Or would the fact that the boot loader is locked interfere with that?
Once again, sorry about all the questions and thanks for the help.
Sent from my Sensation using xda app-developers app
Im not a major flashing buff and my prominent knwledge sits with the sgs2 and ive only recently started researching into the xoom 2.
by the looks of it if normal booting and recovery (factory reset) do not work you have yourself a well bricked tablet. Im unsure about the image dump files being able to be flashed with a locked bootloader. I think it may be your last option and lets face it you dont have much to lose now hey?
As for the charging if your not using the charger that comes with the xoom you will experience very slow charge times. The charger that comes with it is optimized to produce a much higher voltage to charge the tablet within reasonable time... Using a standard usb charger you can face up to 10hrs before the device sits at 100%
Im unsure where you could find some stock image files but have a search around on xda maybe even post up what your looking for maybe someone will know exactly what problems you have and will be able to provide some more help.
But as i said, a locked bootloader leaves us xoom 2 users feeling rather left out with not muvh support when it comes to changing/flashing/fixing any part of the system firmware.
Sent from my XOOM 2 using xda app-developers app
Yeah I'm pretty sure I've got a brick. I'll have to get the motherboard replaced I think.
Yeah I knew about the slow charging if using non genuine charger, but I left it overnight on the genuine charger that it came with, (the wall outlet only one) and still had low battery the next day.... I half expected that because I could only access Fastboot and nothing else and from what I can gather, the device won't charge in Fastboot so short of pulling the case apart and wiring the charger direct to the battery, it's bricked
I think I'll leave it to the professionals to fix.
Thanks heaps for all your help.
Sent from my Sensation using xda app-developers app
Just had a quick search around and noticed that motorola have brung out a software tool to unlock bootloaders for their devices.
The mz616 is not yet supported as they are still updating and adding to their website.
But since the xoom 2 is the one device you can not manually unlock there would be great demand for it to be added to their list.
If you were able to unlock the bootloader you would have no problem at all flashing the stock firmware or third party rom to your device.
Have a search on google for motorola bootloader unlock tool and find the website. Keep updated with their changes and hopefully soon there will support for our devices.
If i find any other ideas i'll be sure to post them here for you. I know what its like to have a device that you have spent hundereds of dollars on and cant use it.
My little brother password locked my xoom and then could not remember it before i started becoming aware of flashing/rooting etc. And pretty much used my xoom as a large doorstopper for 3 months haha.
Sent from my XOOM 2 using xda app-developers app
Thanks for that. While I am definitely looking forward to Moto releasing a unlock for it (if they decide to), I think the fact that I can't charge it is going to be the main issue now.
Hopefully it won't cost too much to fix
Sent from my Sensation using xda premium
What are you doing to charge it? Are you using the charger that comes with the tab or a standard usb??
Sent from my XOOM 2 using xda app-developers app
I'm using the direct wall charger, (not the USB cord with charger attachment) so it should be getting full current charge. I left it overnight with it turned off (ie. black screen)
Sent from my Sensation using xda premium
h4ck3rc1 said:
I'm using the direct wall charger, (not the USB cord with charger attachment) so it should be getting full current charge. I left it overnight with it turned off (ie. black screen)
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
Hmmm does seem like you have truly bricked it. I would be sendind it in for repair. You may have to pay for it though because motorola will see you have tried flashing something over it which would void the warranty...
Sent from my XOOM 2 using xda app-developers app
Yeah I rung them up and got the nearest repairer details and just told them what I had done. I figured they could tell that I had messed with it, considering it will only enter Fastboot LOL. I'll send it in and when it comes back, at least I'll know how to fix it if I stupidly brick it again haha.
Sent from my Sensation using xda premium
Haha yeah oh well we learn from our mistakes. All good though sooner or later there will be a bootloader unlocking tool. There the android worl of flashing will be at our fingertips
Sent from my XOOM 2 using xda app-developers app
Indeed, won't be soon enough. Thanks for your time and suggestions, appreciate it.
Sent from my Sensation using xda premium
h4ck3rc1 said:
Indeed, won't be soon enough. Thanks for your time and suggestions, appreciate it.
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
No worries. Thought ide give as much info as possible cause there isnt that much support for the mz616, especially Australian carrier locked devices.
Sent from my XOOM 2 using xda app-developers app
The fastboot files are avail now for the Australian xoom 2....do a search for it and you will be able to get it running again....
h4ck3rc1 said:
Thanks for that. While I am definitely looking forward to Moto releasing a unlock for it (if they decide to), I think the fact that I can't charge it is going to be the main issue now.
Hopefully it won't cost too much to fix
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
You don't need charger ... all you need is Factory Cable. See pic below:-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Self made Motorola Factory Cable.
1. Use Motorola Stock USB Cable
2. Jumper Pin 1 to Pin 4
Today my USB port went crazy. I tell you my story:
I started to learn Java development a while ago. So I flashed stock FROYO 2.2 XXJPS to be on some "official" ROM to test my apps with (+ test my apps on my Galaxy S CM10.1).
Today I tried to run my app on the Galaxy S, ran fine, PC recognized it, adb working fine. No problems.
Then, I connected my Galaxy 3 to make sure my app has good backward-comatibility and it started charging because it was off. I clicked to run my app, then the phone turned on itself and there goes the craziness. Galaxy 3 shows only AC charger mode instead of USB when the cable is connected, no ADB acess and I have no way to flash new things via DOWNLOAD MODE, because my comp won't recognize it.
I have drivers for it, as I flashed ROMs without problems. I tried connecting the phone to other PCs too, without success.
So, I tried several things - factory reset. No succes. Tried flashing some different kernel, too... oops, cannot get my phone connected to PC in DOWNLOAD MODE (entering it and recovery works fine though). So, I'm out of ideas. I'm out of warranty, too. Uh-oh... I guess I'm in the same position as Chainfire, if I'll mess up some system files, guess what. BRICK. I don't want to say bye to this phone...
EDIT 13/5/2013 - OK, as I mentioned in the posts, some user fixed this problem by flashing ICS. OK I thought how about that? I asked in this thread how safe is going to ICS through recovery, nobody replied (I'm OK with that, not your fault ). So I thought there comes a challenge. I want to fix it. But looks like you cannot go from CM7 to CM9 directly via CWM (I told you CWM is buggy) and then wiped data factory reset and reboot. FAIL. Screen turning fast on/off cycle. Looks like boot.img flashed wrong, so now COMPLETELY NO RECOVERY. And, what's worse, my USB connection fail problems forced me to once more reinstall drivers, switch PCs, but NO DOWNLOAD MODE recognition. So here it is guys, complete BRICK (because of the USB). No way to recover phone that doesn't communicate via USB port and has no recovery.
EDIT 22/5/2013 - Good day G3 community! I'm back with my "partially unbricked" G3 It has Android 2.2 XXJPS fully up and running. No crazy things like AC charging, but I cannot say for sure, as I need to do some more testing. Looks like the screen is waking/turning off like before (that's why "partially unbricked" LOL), just the USB connection seems more stable. Maybe it had something to do with battery voltages? Anyway, I left my phone laying on the table for a week, thought battery will discharge a bit (sit down a bit, if you know what i mean) and some days ago I reinstalled my PC. I hated the fact that my G3 is bricked and connected to the PC to give it another go. WOOPS! Drivers installed, ODIN MODE ACTIVATED! I have my phone connected to PC, ADB working, ODIN working, no ROOT as of now, just want to let it fully charge. That's it, I hope it will get better and better. For now no flashing, who knows what might happen... Still testing...
had that problem too!
I just flashed via cmw a cmw flashable rom like experimental cm x
by marcellusbe and everthing worked again.
---------- Post added at 08:03 AM ---------- Previous post was at 07:56 AM ----------
or you could try mobile odin app by chainfire!
but i'm not sure if our device is supported
link: https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro&hl=de
Shadowcareful said:
had that problem too!
I just flashed via cmw a cmw flashable rom like experimental cm x
by marcellusbe and everthing worked again.
---------- Post added at 08:03 AM ---------- Previous post was at 07:56 AM ----------
or you could try mobile odin app by chainfire!
but i'm not sure if our device is supported
link: https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro&hl=de
Click to expand...
Click to collapse
Thanks, I thought about that too, but Im on stock ROM and also stock recovery. So that wont work. Anyways this is weird, yesterday evening I left my phone turned on on the table. Suddenly it turned the screen on and off. I thought what the... And USB worked right then But now it does the screen on/off sometimes. Will play with it a bit and see how it goes. Strange... I definitely have to get rid of stock recovery...
Sent from my GT-I9000 using xda app-developers app
Oh no... It loked like it's fixed, but now it goes crazy again. Still cannot get USB to work properly. Still AC mode and no way to make the phone recognized in download mode. Still trying to recover it though... I'm still with stock recovery, flashing anything through it won't work I guess...
EDIT: It looks again like it's fixed, don't know for how long though untill it goes crazy again... I hope it won't go crazy again! Testing how it goes...
twinky444 said:
Oh no... It loked like it's fixed, but now it goes crazy again. Still cannot get USB to work properly. Still AC mode and no way to make the phone recognized in download mode. Still trying to recover it though... I'm still with stock recovery, flashing anything through it won't work I guess...
EDIT: It looks again like it's fixed, don't know for how long though untill it goes crazy again... I hope it won't go crazy again! Testing how it goes...
Click to expand...
Click to collapse
hm...ma8....did you tear ur g3 apart already and checked if usb port has bad soldering contact ?
or maybe sth is in there that messes up things....
Sent fom my S-II running >>SlimBean build 5 OFFICIAL << powered with DorimanX kernel v. >>9.16<<
rkoby13 said:
hm...ma8....did you tear ur g3 apart already and checked if usb port has bad soldering contact ?
or maybe sth is in there that messes up things....
Sent fom my S-II running >>SlimBean build 5 OFFICIAL << powered with DorimanX kernel v. >>9.16<<
Click to expand...
Click to collapse
I think no hardware stuff needed, I found some users in galaxy s forum who has the same issue. He fixed it by flashing cm9 and it worked. But cm9 is not yet done. And we don't have 3.x kernel yet. That wouldn't be much of a solution. Now the problem is, if I turn off the phone, it turns on itself automatically after plugged into some power source. And if I leave the usb plugged in for a while, phone doesn't recognize it, won't charge, then if I unplug it and leave it untouched, it starts the screen to wake, then screen off. Wake again and Screen off again. And it continues like that. Phone is going crazy.
Now I'm stuck at CM7 (it has the power-off state battery drain bug). Don't know what to do.
Anyway I'll probably look into the phone and see... Thanks m8!
Sent from my GT-I9000 using xda app-developers app
i remember that you can root your stock rom using a .zip which is flashable via stock recovery. And after rooting, you can try to replace the recovery files with cwm recovery files. Then flash another rom via cwm.
Edit:- Ok i think that .zip was for eclair. Any other way to root it?
[email protected] said:
i remember that you can root your stock rom using a .zip which is flashable via stock recovery. And after rooting, you can try to replace the recovery files with cwm recovery files. Then flash another rom via cwm.
Edit:- Ok i think that .zip was for eclair. Any other way to root it?
Click to expand...
Click to collapse
I already mentioned I'm on cm7 alpha 9. Still the same problem. Flashing other ROM won't probably help. Tomorrow it'll be weekend so I'll do some hardware teardown, just worried about messing it up.
Will let you all know then.
Sent from my GT-I9000 using xda app-developers app
twinky444 said:
I already mentioned I'm on cm7 alpha 9. Still the same problem. Flashing other ROM won't probably help. Tomorrow it'll be weekend so I'll do some hardware teardown, just worried about messing it up.
Will let you all know then.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
don't worry....I ripped apart my s2........bricked amoled....lol....it's quite easy to disassemble it
Sent fom my S-II running >>SlimBean build 5 OFFICIAL << powered with DorimanX kernel v. >>9.16<<
rkoby13 said:
don't worry....I ripped apart my s2........bricked amoled....lol....it's quite easy to disassemble it
Sent fom my S-II running >>SlimBean build 5 OFFICIAL << powered with DorimanX kernel v. >>9.16<<
Click to expand...
Click to collapse
Cool... Never knew how this phone looks like after teardown
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looks like no problems here with the usb... Neither any dust So software is going weird...
The good thing is, it boots up again.
But I guess my galaxy 3 gave up?
EDIT: Now looks like SD-card is giving problems too, after removing SD-card and reinserting it, it says USB connected dialog even when not connected LOL. And when connected, the dialog does nothing after clicking connect button. Really weird. Also doesn't charge at all via USB now. I'm 55% on battery, hope I'll be able to charge it again (without the crazy loop I posted before at least via AC)!
Any advice now? Thanks in advance.
Sent from my GT-I9000 using xda app-developers app
twinky444 said:
Cool... Never knew how this phone looks like after teardown
View attachment 1951759
View attachment 1951762
Looks like no problems here with the usb... Neither any dust So software is going weird...
The good thing is, it boots up again.
But I guess my galaxy 3 gave up?
EDIT: Now looks like SD-card is giving problems too, after removing SD-card and reinserting it, it says USB connected dialog even when not connected LOL. And when connected, the dialog does nothing after clicking connect button. Really weird. Also doesn't charge at all via USB now. I'm 55% on battery, hope I'll be able to charge it again (without the crazy loop I posted before at least via AC)!
Any advice now? Thanks in advance.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Try a factory reset or installing a custom cm7 based rom
Sent from my GT-I5800 using Tapatalk 2
Arjav23 said:
Try a factory reset or installing a custom cm7 based rom
Sent from my GT-I5800 using Tapatalk 2
Click to expand...
Click to collapse
As mentioned earlier, all of this didn't work. I could try to flash ICS based rom as some SGS user recovered from this earlier using ics rom, but even by reinstalling drivers my phone doesn't get recognized in any way (including recovery and download mode). I know, I have recovery to flash with, but it can easilly go wrong and for me it worked only to flash rom based on the same os version. If someone can try going from GB to ICS succesfully via CWM, let me know if it goes well, because I used to flash ICS only via odin, as CWM is sometimes buggy I mean: failed to mount /system, /data, /cache partitions and so no way to flash anything through CWM again. Only ODIN can recover from that. And I have no way to get my phone recognized in download mode. So no ODIN.
Sent from my GT-I9000 using xda app-developers app
twinky444 said:
As mentioned earlier, all of this didn't work. I could try to flash ICS based rom as some SGS user recovered from this earlier using ics rom, but even by reinstalling drivers my phone doesn't get recognized in any way (including recovery and download mode). I know, I have recovery to flash with, but it can easilly go wrong and for me it worked only to flash rom based on the same os version. If someone can try going from GB to ICS succesfully via CWM, let me know if it goes well, because I used to flash ICS only via odin, as CWM is sometimes buggy I mean: failed to mount /system, /data, /cache partitions and so no way to flash anything through CWM again. Only ODIN can recover from that. And I have no way to get my phone recognized in download mode. So no ODIN.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
ma8 ....can you make a logcat while all this weird things are happening?Maybe logcat will show what might to pinpoint the cause of your issue....if you can get log please post it....and...you're rooted...or....i'm I don't know which rom are you running atm....
Sent fom my S-II running >>SlimBean build 5 OFFICIAL << powered with DorimanX kernel v. >>9.16<<
rkoby13 said:
ma8 ....can you make a logcat while all this weird things are happening?Maybe logcat will show what might to pinpoint the cause of your issue....if you can get log please post it....and...you're rooted...or....i'm I don't know which rom are you running atm....
Sent fom my S-II running >>SlimBean build 5 OFFICIAL << powered with DorimanX kernel v. >>9.16<<
Click to expand...
Click to collapse
OK, here are some details:
ROM: CM7 alpha 9
Kernel: the one that comes with alpha 9
Rooted: yes, obviously with CM7
No way to flash via ODIN. No way that phone gets recognized in recovery and in Android either.
No ADB.
Removing micro-SD card causes the system to display USB Connected dialog. What the...?
For short, NO USB CONNECTIVITY. Except charging via wall adapter (even this is kinda buggy).
I attached logcat, it's kinda messy, because I recorded that with terminal emulator and then used the microsd adapter to get this to the PC. Cannot get logcat for the sdcard unmounting, as was recording logcat here. notice the line "UMS Mount failed, media unmounted" line in the logcat. What the...?
twinky444 said:
OK, here are some details:
ROM: CM7 alpha 9
Kernel: the one that comes with alpha 9
Rooted: yes, obviously with CM7
No way to flash via ODIN. No way that phone gets recognized in recovery and in Android either.
No ADB.
Removing micro-SD card causes the system to display USB Connected dialog. What the...?
For short, NO USB CONNECTIVITY. Except charging via wall adapter (even this is kinda buggy).
I attached logcat, it's kinda messy, because I recorded that with terminal emulator and then used the microsd adapter to get this to the PC. Cannot get logcat for the sdcard unmounting, as was recording logcat here. notice the line "UMS Mount failed, media unmounted" line in the logcat. What the...?
Click to expand...
Click to collapse
Does your sgs work perfectly with adb and odin?
Sent from my GT-I5800 using Tapatalk 2
Arjav23 said:
Does your sgs work perfectly with adb and odin?
Sent from my GT-I5800 using Tapatalk 2
Click to expand...
Click to collapse
As said in OP, yes. Perfectly.
Sent from my GT-I9000 using xda app-developers app
Check OP for progress.
Sorry if someone already mentioned, but
Following steps might help.
A. Re install Samsung drivers.
B. Go to force upload mode by vol up + home button + power
C. Flash Zero fill.tar and do not reboot, let odin show pass.
D. Reboot by button combo in force upload mode again and flash data fixer.tar
E. Flash any rom.
I am an excessive flasher and at some point of time have experienced similar problems.
Hopefully that will help.
Sent from my GT-I5800 using xda app-developers app
So no more layout fixes and other good things made by you on our g3 :crying: . Good luck to you in your further theming on other devices and thanks for all good things you have made there :thumbup:
Sent from my GT-I5800 using xda app-developers app
Abhijeetsinghvsf said:
Sorry if someone already mentioned, but
Following steps might help.
A. Re install Samsung drivers.
B. Go to force upload mode by vol up + home button + power
C. Flash Zero fill.tar and do not reboot, let odin show pass.
D. Reboot by button combo in force upload mode again and flash data fixer.tar
E. Flash any rom.
I am an excessive flasher and at some point of time have experienced similar problems.
Hopefully that will help.
Sent from my GT-I5800 using xda app-developers app
Click to expand...
Click to collapse
Unfortunately I'm stuck on point 2. My phone doesn't get recognized by ODIN in any way - swapping cables, PCs, didn't work. Reinstalling drivers worked once, but then it broke to the state when it just doesn't work AT ALL. Just reinstalled again to check... Still nothing.
Thanks for the kind words, I still hope I can get it fixed, but there's not much chance I suppose as I'm out of ideas. The main problem here is the USB connection between ODIN, as this is the only way to get this phone recovered now. I recovered from this bootloader loop/missing kernel situation before, but that was when my USB was working perfect... It's not lost yet... But I think also the battery is a problem, I bricked it when it was 50% on charge and when I connect the phone now when it's off, it doesn't display the charging animation, because the kernel is missing. UH-OH... Does the phone charge when it's in download mode? (<- LOL sounds weird )