Database Info

[SOLVED] gt-i9023 help please - no usb,adb,fastboot access

I am a beginner at this so please excuse me.
I successfully rooted my phone, installed clockwork, super user was working, could connect like a dream with usb to the phone. Flashed stuff using fastboot in command line - all was good.
When I say successfully it did take a long time, the phone didnt work for a while but I flashed clockwork on then flashed the rom for my phone from here http://forum.xda-developers.com/archive/index.php/t-1063664.html
I used this one:
Android 2.3.3/GRI40/KB1 Radio/KA3 Bootloader (http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip)
Works on: I9020T, I9023
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
Which was great - sorted the phone a treat - I had the super user working - I installed the clockwork rom app - worked a treat - even did a backup (I think)
Then the phone tried to update to 2.3.4 which failed - right now I should of check the forums but thought I know I'll just flash the update from the above page - which failed - not to be defeated I tried harder using different roms through clockwork recovery or clockwork rom mod until sucess 2.3.4 GRJ22 build.
Then I find the super user app doesnt work or the clockwork rom - no problem boot into clockwork recovery - uh oh thats gone as well though i can get to android recovery.
I'll just flash clockwork recovery on but I cant as I've no access with adb or fastboot the phone is not connecting to the pc in fastboot mode with the android logo and phone details.
When I'm trying to use USB connection on the phone normally the USB man goes orange then back to green - and the phone prepares the USB storage again.
I can use a app to get files on to the sd card for use with android recovery so i try to reflash the 2.3.3 rom above that worked but I get the status 7 error with a long number 1297306095
I try the update again and this is where i realise that the update ROM i put on was the wrong one.
I flashed this: Android 2.3.3 (Build GRI54/KB3 Radio/KA3 Bootloader) (whole rom)
I should of flashed this Android 2.3.3 (Build GRI40/KB1 Radio/KA3 Bootloader) (smaller update)
I can flash the correct update above but it doesnt change anything.
I have spent a few days now trawling the forum with little success and having got all the correct drivers on the pc and had it connecting fine I am assuming it is a phone issue now
the base band details have changed from XXKB1 to XXKD1 and the build from GRI40 to GRJ22
I am at my wits end here and before I put a hammer to my phone and send it back as an insurance job I'd like to mend my stupid mistakes.
Thanks
Acne

it doesnt matter if you flashed the whole rom. (provided you didnt use odin)
first thing, try to format sd card through the phone,
then enable usb debugging and try using adb n fastboot.
also, try to flash a newer recovery.img ( be careful no to use one not meant for ur phone e.g ns4g...)
post ur results.
good luck

can't find an option from within the phone to format the SD card - found an app on the store that is called "format sd" which did something and allowed me to connect to the USB once but it was very flaky and took a few attempts at the "turn on usb" screen to get it to connect. I'm not sure that it wasnt just deleting the data from the sd rather than formatting as it took maybe 10 seconds first time and now its done straight away if I try again.
Edit - i've used the stock erase usb command within the phone and the USB connection within the phone seems to becoming more stable - I can read and write data to it from the pc but it still struggles to connect first time.
No change with command line commands abd or fastboot neither are connecting.
I've come to the conclusion that maybe I need to flash a newer recovery image (ROM?) myself but where do I find one? And how do i check that it really is the correct one for my phone - which of the details are important - should i use the original stock details? I'm confused, remembering all I can use is the "Android system recovery <3e>" that only gives me the option of reboot, apply update from sd card, wipe data/factory reset, & wipe cache partition.
I flashed the wrong ROM with the clockwork rom app from within the phone I dont know what odin is.
Thanks for the pointer anymore ideas or direction appreciated.
Acne

Try to wipe from the stock recovery and then install this
http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip
It is the full 2.3.3. It will return your phone to complete stock 2.3.3
P.s sorry i am not being able to help more. I am myself in a far bigger trouble

I tried that rom but got the status7 error. That one worked before under clockwork but won't reflash now. I can do a factory reset under stock but will that make a difference? I thought all that did was reset user data not the system data. I think l need to wait for a new stock Tom to be issued.
Acne

Tried the reset phone from within the phone and reset using stock recovery, still cant flash the old 2.3.3 rom above getting the status 7 error:
assert failed ! less_than _int(1297306095. getprop(ro.build.date.utc"))
so the usb works fine from within the phone when the phone is running normally, when I connect the phone in fastboot mode it shows as an Android ADB interface on the "safely remove hardware" window but i cant use any command prompt instructions on the phone - using fastboot devices to show connected devices I get no reponse.
Any ideas?
Any pointers to a later rom that will correct my problems?
Thanks
Acne

After a bit of experimenting I find that when the phone is switched on normally I can use the ADB devices command to return the ID of the phone. The fastboot devices command still returns a blank.
Is this normal?
Does this mean I could flash the clockwork recovery image onto the phone? or can all that malarkey only be done in fastboot mode?
thanks
Acne

You need the fastboot devices command to return your phone info then you can fastboot flash recovery in order to try flashing a recovery that will allow you to flash the rom you are getting a failed message from. The stock recovery can only flash official updates put out by Google iirc.
I am thinking you are having driver issues on the PC you are using. Try another PC with fresh drivers or uninstall and reinstall the drivers on the one you have been using.
sent from the nexus of the 4g universe

I've read up on the driver problems, I tried the phone on two different pcs using two different methods on each to install the correct drivers. none work. The phone used to connect fine which is how i rooted the phone. I'm using the same pc, same supplied cable and can see the ADB mounted in the "safely remove hardware" window
The adb command works when the phone is switched on normally, but not fastboot command.
When in fastboot mode neither works. Looking in device manager the android adb interface is listed fine under android phone.
I'm pretty sure its not the drivers.
Doesn't the above prove that the pc connects fine but the phone is broken in fastboot mode?

You could still flash the latest 2.3.4 full ROM with ODIN. The Phone will be restored completely and then you can root it again.

Thats great Odin looks like it will be the way forward, just so I dont make another noob error could someone point me in the right direction for the correct version of odin and a guide on how to use it. I have looked around the forum but am struggling to find the relevant thread
I have tried the usb/2 button and it enters download, the version od odin that i found (1.81) does see the phone but I think that version is for the 9020 only I have the GT-i9023 so dont want to use the wrong programme/rom
Thanks
Acne

Ok took a chance and flashed the phone with odin - great it worked reset all the fastboot mode values back to their original ones when i got the phone. (seems I chose the correct rom) the only difference is that the Carrier info is now EUR not VDF as it was when I first got the phone.
Applied the auto update to 2.3.4
Tried at every step but I still have no fastboot or ADB access the phone just doesnt connect. Tried different leads, tried different usb ports - nothing.
I'm stumped now unless there are any advanced settings in odin I should try.
Acne
The

Discovered after the auto update to 2.3.4 that the USB connection from within the phone was "broken" again, To sort this i did a format cache and reset phone from the stock recovery which sorted the usb connection. so thats that one solved then.
tried again to connect via command prompt, unistalled drivers - reinstalled drivers - no change still no devices detetcted.
Any good ideas?

Solved
using the usbdeview mentioned here I uninstalled all the usb drivers on my pc that looked like they could be anything remotely connected to the nexus and samsung.
I ran and updated/download pretty much everything i could through SDK
Then I did everything I read in this thread
Up till then I had been using the fastboot command found and downloaded through this thread
That continued not to work but when i tried the fastboot in the android-sdk/tools folder I finally got fastboot access.
Solved Solved Solved
to get my phone unlocked and updated I did an odin restore to 2.3.3 let it auto update to 2.3.4 copied the su(superuser zip) to the sd card. flashed clockwork recovery and then installed the su.zip with clockwork. after that I installed the rom manager from the android shop and Inow have the phone just how i want it.
To all those that have helped with their ideas here many many thanks.
Acne

[Q]

First off I am sorry for posting this, however I DID use the search tool. I recently got a USA spec Wifi only Xoom. It came with 4.1.1 preinstalled. I have sucessfully unlocked the bootloader.
My problem is this. I cannot gain root or even get CWM installed. I have tried oneclick, i have tried cmd prompt. I have followed every guide I can find to a "T". Is there something missing, is it an issue with Jellybean being preinstalled?

Use http://forum.xda-developers.com/showthread.php?t=1468298 to get CWM installed (and when you reboot from fastboot flashing the recovery image, and this is very important, DO NOT LET IT FULLY REBOOT INTO THE OS. You have to get into recovery in the next boot or the OS will just overwrite it with the stock recovery and you will just have to go back into fastboot and flash the recovery again.
http://forum.xda-developers.com/showpost.php?p=30464067&postcount=408 has the root once you get CWM installed.

airesch said:
Use http://forum.xda-developers.com/showthread.php?t=1468298 to get CWM installed (and when you reboot from fastboot flashing the recovery image, and this is very important, DO NOT LET IT FULLY REBOOT INTO THE OS. You have to get into recovery in the next boot or the OS will just overwrite it with the stock recovery and you will just have to go back into fastboot and flash the recovery again.
http://forum.xda-developers.com/showpost.php?p=30464067&postcount=408 has the root once you get CWM installed.
Click to expand...
Click to collapse
Thanks for the reply, however this is one of the utilities I have tried,..
Here is a bit more info.
I am running windows 7 64bit if it makes a difference. Whenever I get the device into fastboot and try to flash anything, it just hangs at the original fastboot screen. I have let it sit there from 3 hours and eventually I have to reboot it. The Lord AIO Tool you linked just gives me and error message that the device is not a 2.2/2.3 device. If I were at home I would take a screenshot.
Could my bootloader be corrupt? The device still boots up and runs jellybean fine, but I am not loving the stock experience thus far...
Thanks again for the links!

Actually sounds like your drivers aren't right. I will look them up and link them when I get home
Try installing the driver from http://developer.motorola.com/tools/usb_drivers/, rebooting your pc, and try fastboot again. If that still doesn't work, then there may be something wrong with your pc setup OR your Xoom, not sure at that point.
Sent from my SPH-D710 using xda premium

Thanks a million, I am going to try it fresh on my pc at work. Thanks!

That did the trick THANKS A BUNCH!!!!!

[Q] Anyway to root and install roms without a microsd card?

Apparently I just have tons of regular SD cards laying around and none of the micro variety. Ive rooted and put custom roms on 6 phones and kindle fires in the last two weeks so it seems a bit strange that this device would be the only one that would be different, but everything ive been able to read uses a micro card. Any info would be really appreciated. Thanks! (using US wifi board by the way)

Nada?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

You sure can.
Unlock the boot loader, ( note doing so will wipe all data from your device )
Reboot into android download a ROM and place on internal memory.
Fast boot flash a custom recovery ( see my SIG for twrp recovery for xoom)
Boot into the custom recovery ( see my SIG for my YouTube videos, there is a quick video on how to enter recovery)
Once in twrp recovery select install and the flash your ROM from internal memory.

runandhide05 said:
You sure can.
Unlock the boot loader, ( note doing so will wipe all data from your device )
Reboot into android download a ROM and place on internal memory.
Fast boot flash a custom recovery ( see my SIG for twrp recovery for xoom)
Boot into the custom recovery ( see my SIG for my YouTube videos, there is a quick video on how to enter recovery)
Once in twrp recovery select install and the flash your ROM from internal memory.
Click to expand...
Click to collapse
I used The Lord all in One tool to unlock the boot loader. Im pretty sure that worked, device was seen and after it rebooted its like a completely wiped machine.
Now, then I reboot into recovery all i get is the green droid on its side with the warning triangle. I went to the TWRP post in your sig and there are 4 different install methods. I cant get any of them to work, but I havent tried option 2 because I dont have any idea how to use the adb commands. The windows script adb never sees my device although the LAIOT adb script does. I guess Im stuck on how to get TWRP onto this damn thing.

Roseysdaddy said:
I used The Lord all in One tool to unlock the boot loader. Im pretty sure that worked, device was seen and after it rebooted its like a completely wiped machine.
Now, then I reboot into recovery all i get is the green droid on its side with the warning triangle. I went to the TWRP post in your sig and there are 4 different install methods. I cant get any of them to work, but I havent tried option 2 because I dont have any idea how to use the adb commands. The windows script adb never sees my device although the LAIOT adb script does. I guess Im stuck on how to get TWRP onto this damn thing.
Click to expand...
Click to collapse
download this zip Install_Scripts_v2.3.3.0.zip - 10.03 MB
and extract
open your cmd ( command prompt )
cd ( change directory to where you extracted the above zip)
now connect your tablet to pc,
from the cmd type
Code:
adb devices
ensure that your pc sees your device, should read out sn#
now click the runme.bat
and follow onscreen instructions.
once the recovery img has been flashed ( you can verify on the xoom's screen.)
from the runme.bat select option 3 to reboot, you MUST reboot straight into recovery ( again see video for video steps here http://www.youtube.com/watch?v=koxgbdQuzOQ ) and flash rom, if you dont catch the boot process in time it will boot into android, and the custom recovery you just flashed will be replaced by the stock android recovery, and you will need to repeat the whole process. after you flash the rom your custom recovery will stick and you will be good from here on out

Hey, thanks for all your help. I finally got it going, and im really glad I wont have to do all of that stuff again, but your help was greatly appreciated.

Roseysdaddy said:
Hey, thanks for all your help. I finally got it going, and im really glad I wont have to do all of that stuff again, but your help was greatly appreciated.
Click to expand...
Click to collapse
Any time

I need help with this tablet - few questions

Background:
I attempted to root the device. so I installed CWM... Well it doesnt stick. once you boot it never stays. When I go into recovery mode from the boot loader it says "no command" But if I flash it and then reboot right into the bootloader then go into recovery it works fine.
First issue: CWM doesnt stick
which led me to another issue..
ADB doesnt work in CWM (which I thought). So I decided to flash PhilZ recovery and found it didnt work there either! So I figured it had to be my drivers - but they worked fine in Windows and when the device is booted normally in the OS. (I am using Nvidia latest drivers)
Then I figured let me restore the unit back to the original image (i signed up as a developer) downloaded the Nvidia 1.2 Image and reflashed everything using fastboot (system, boot, recovery, data, etc.)
Since I had never tried to go into the stock recovery maybe it was CWM or PhilZ...
Leads to my next issue:
The stock recovery doesnt work no matter how many times I flash it. When I go into the bootloader and click on recovery mode I get "no command" with the andorid guy dead.
1. How can I get back the stock recovery using Nvidia's image. The recovery is not working
2. How can I get CWM to stick?
3. Why isnt ADB working in recovery mode but working fine when booted in the device?

stanglx said:
Background:
I attempted to root the device. so I installed CWM... Well it doesnt stick. once you boot it never stays. When I go into recovery mode from the boot loader it says "no command" But if I flash it and then reboot right into the bootloader then go into recovery it works fine.
First issue: CWM doesnt stick
which led me to another issue..
ADB doesnt work in CWM (which I thought). So I decided to flash PhilZ recovery and found it didnt work there either! So I figured it had to be my drivers - but they worked fine in Windows and when the device is booted normally in the OS. (I am using Nvidia latest drivers)
Then I figured let me restore the unit back to the original image (i signed up as a developer) downloaded the Nvidia 1.2 Image and reflashed everything using fastboot (system, boot, recovery, data, etc.)
Since I had never tried to go into the stock recovery maybe it was CWM or PhilZ...
Leads to my next issue:
The stock recovery doesnt work no matter how many times I flash it. When I go into the bootloader and click on recovery mode I get "no command" with the andorid guy dead.
1. How can I get back the stock recovery using Nvidia's image. The recovery is not working
2. How can I get CWM to stick?
3. Why isnt ADB working in recovery mode but working fine when booted in the device?
Click to expand...
Click to collapse
All has been fixed except for #2. Cant get CWM to stick... but for 1 and 3:
OK.. got the stock recovery - I didnt actually know you had to do volume up when at the "no command" screen..
and also I figured out how to fix the driver issue...
For anyone else having the issue you need to uninstall the driver until it shows up as Shield with the exclamation. You must be in the recovery in an area like sideload.. (Not in android OS)
Then Update Driver, Browser and then click on "Let Me Pick from a list on my computer"... find Android then select "Android Composite ADB Interface".
Now the driver works in ADB and in the OS

Same Problem
I'm having the same problem with CWM reverting to stock recovery after system boot. I didn't see your post until after I posted my own thread -- I probably should have titled it specifically about the stock recovery reversion so others will find it. Anyway, not that there's at least one other person besides me having this problem, I'm less worried that it's just me being stupid. Although that's always a possibility. Maybe someone will come along and help.

Recovery Reversion Problem Solved
Okay, I solved my recovery reversion problem -- I wasn't using either a custom boot.img or the Beta SuperSu (currently BETA-SuperSU-v2.42.zip), one of which is needed to keep root on Lollipop. (Apparently I knew this a month ago when I first went to 5.0.)

Only recovery

Hello! I recently dropped my OPO and the screen cracked. The touch also stopped working. But except that, everything looked fine, to me at least. I ordered a new display and replaced it some days ago. Everything went alright, except when I reconnected the antenna cable... It was too short, so I tried to pull a little bit, and then the cable popped off. I'm going to find a solution to this, I'll see if it is possible to replace the antenna cable. Anyway, I put everything else together and started the phone. I was surprised to find out that I ended up in the recovery. I rebooted and I ended up in the recovery AGAIN! So I formatted the internal memory, transferred CM13 + stock Gapps to the phone, installed and booted. I ended up in my recovery, again. I began thinking that the recovery might be corrupt or something like that (TWRP). I tried booting to the bootloader, but ended up in the recovery, once again. These are the different methods I used, trying to reach the bootloader:
- Volume up + power button
- Recovery reboot options
- adb reboot bootloader
All of these methods brought me to the recovery. My goal is to reach the bootloader so fastboot works, and then use this tool to reset my phone. Do you guys have any ideas? Thanks in advance!

What recovery ? Twrp or stock ?
If you are in twrp there is option to boot into bootloader ,then you can flash firmware via fastboot or use otg port,
If you in stock , I think otg port can be used .

drmuruga said:
What recovery ? Twrp or stock ?
If you are in twrp there is option to boot into bootloader ,then you can flash firmware via fastboot or use otg port,
If you in stock , I think otg port can be used .
Click to expand...
Click to collapse
This is the problem... I am using TWRP, but even if I use the reboot options, which is booting into bootloader, I will only end up in the recovery anyway...
Any other idea?

There is no OS, so not booting. Use any compatible ROM via otg preferably COS 13 TWRP signed ROM ( no gapps needed ).