Database Info

Flashed I9020A ROM on a D720, now stuck at splash screen

Had to come out of lurking for this:
- phone is a D720
- flashed I9020A ROM: Android 2.3.4/GTJ61/UCKE1 Radio/KA3 Bootloader (I didn't do it)
- phone stuck looping at splash screen
- able to put phone into 'fastboot mode' - NOTHING happens in Windows Device Manager
- able to put phone into 'download mode' - NOTHING happens in Windows Device Manager
- no recovery installed
- I have a 2nd D720 that shows up in Device Manager fine in 'fastboot mode' and 'download mode'
What are my options?
- displayed in 'fastboot mode':
HW VERSION - REV 03 (JTAG)
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020UCKE1

Go into fastboot mode and hook up to your pc.
Get your fastboot driver installed.
Flash recovery thru fastboot.
http://android.modaco.com/topic/302508-solved-using-adbfastboot-help-to-flash-recovery/

Try this:
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
There is also a video what shows you to do.

Thanks for the quick replies but NOTHING happens in Windows Device Manager

You have to install the rite driver. Just cuz it installed, doesnt mean its the rite one.

snandlal said:
You have to install the rite driver. Just cuz it installed, doesnt mean its the rite one.
Click to expand...
Click to collapse
Hmm, even though (as stated in the OP):
- I have a 2nd D720 that shows up in Device Manager fine in 'fastboot mode' and 'download mode'.

I know. It is. But if your typing adb devices and nothing is showing, its the wrong driver.
Try a different usb port maybe

Adb is not for when the phone is at the splash screen. Or the bootloader screen. Or when the device is in fastboot.

Doesnt it use the same driver? Sorry don't use windows often. But OP if you can't get it to connect/ find the driver for a windows pc get a linux live cd and use terminal on that.
If you can get into fastboot you can fix it.
Avoid download mode unless you break fastboot. (which is really hard to do)

I appreciate any and all suggestions.
snandlal said:
I know. It is. But if your typing adb devices and nothing is showing, its the wrong driver.
Try a different usb port maybe
Click to expand...
Click to collapse
While the phone is in 'fastboot' mode I used USBDeview and see nothing. When I do the same with my 2nd D720, it shows.
I tried a different USB port.
themapleboy said:
Doesnt it use the same driver? Sorry don't use windows often. But OP if you can't get it to connect/ find the driver for a windows pc get a linux live cd and use terminal on that.
If you can get into fastboot you can fix it.
Avoid download mode unless you break fastboot. (which is really hard to do)
Click to expand...
Click to collapse
I'll report back after trying Linux Live.

themapleboy said:
Doesnt it use the same driver? Sorry don't use windows often. But OP if you can't get it to connect/ find the driver for a windows pc get a linux live cd and use terminal on that.
If you can get into fastboot you can fix it.
Avoid download mode unless you break fastboot. (which is really hard to do)
Click to expand...
Click to collapse
Tried LinuxLive on USB and it doesn't recongize it either.
When you say "If you can get into fastboot you can fix it", do you mean if I can boot the phone into 'fastboot mode' or accessing the phone from command prompt in 'fastboot mode'?
I made minor corrections to my previous posts.

[Q] Fastboot problem

hello,
I'm hoping someone here can help me sort out my current problem.
I've been trying to root so I can install the latest ICS port, but having problems at the Fastboot screen.
I apologize in advance if some of the references/names I'm using are incorrect.
So, I had originally unlocked my Nexus S sometime early this year. When I restart the phone, the "unlocked" lock picture shows up under the "Google" words, and when I go into fastboot mode, the Lock State is Unlocked.
I'm running 2.3.6 right now on the Tmobile version of the phone.
When the phone is on (not in fastboot mode), I can execute ADB commands and the device is recognized. As soon as I go into fastboot it isn't.
I'm running 64bit Win 7, and I have gone through the various threads that have listed this issue, and installed PDA Net drivers and still there is no solution.
In Fastboot mode, while connected to computer under device manager, it shows up under Universal Serial Bus Controllers as an Unknown Device... I'm unable to update any drivers for it, and even when I try to manually update the drivers by going to the PDANet drivers it does not allow it.
When the phone is on in regular mode in device manager it shows up as Android Phone and within that it has a listing called Android Composite ADB Interface.
As mentioned above, when phone on in regular mode everything is detected.
I installed clockwork app from market, assuming that the phone was "rooted" based on the "unlock state" in fastboot mode, but it immediately says that phone needs to be rooted because it was unable to find SuperUser file etc etc.
I've spent the better part of a few days trying to figure this out by checking all sorts of links, but I haven't found a solution. The main issue is that the phone is not being recognized when in fastboot mode when connected by USB. And I'm unable to install the proper drivers for fastboot mode.
Hopefully this makes sense, and someone can provide some insight.
Thanks in advance!

I'm not positive about this but couldn't you adb push the su binary and apk? I don't own the Nexus but I would think since its unlocked you could just push the files. If this would work I would think it's just a temporary solution to allow superuser permission. As I understand it, fastboot is the preferred method for the Nexus.
Sent from my PG06100 using Tapatalk

Did you try a fastboot command like fastboot devices?

Don't know if this applies to you but I had a similar sounding problem when trying to root my Nexus S where everytime I booted into fastboot mode I had an error message at the bottom of the screen saying something like 'fastboot status-fail Invalid command' and so I couldn't use any fastboot functions.
To get around it I used this one-click root . For some reason I got an error message halfway through for whatever reason and it wouldn't complete the root for me but it booted me into fastboot without receiving the error message and then once I was in I went and rooted manually.
The CWM is out of date on that site though (possibly the super-user zip too) so I replaced them with the latest versions and popped it in my dropbox for you, if you wanna try it out.
http://dl.dropbox.com/u/47770734/One-Click-Nexus-S.zip
Edit: just had a little look through the bat script and the initial commands that got me into fastboot properly is (with your phone in debugging mode):
adb start-server
adb reboot bootloader
Click to expand...
Click to collapse
So you could try that first if you wanna go through manually.

Know that you can't run adb command while in fastboot mode. Boot into your CWM and then you can start an adb shell and you'll be able to push all the files you want and execute all the commands you need.
Fastboot mode is for running fastboot indeed. Try 'fastboot devices' while you're in the bootloader and see if devices pop up. If not, you really have to figure out your drivers issue. Maybe remove the device completely from your PC (including driver files) and reinstall it using the PDAnet drivers.
Greetz

No green android when using flash or fastboot mode

Hi,
First of all the bootloader is already unlocked.
Two problems:
1. - I was trying to flash twrp.img on my mobile but I am not getting that green android to show up in my screen all I get a black screen with blue led light, I usually power off the mobile, hold volume up and then connect the USB cable to my mobile.
2. - Can't find mobile device while using flash or fastboot, my mobile Developer option and USB debugging are turn on, mobile drivers and adb-setup-1.4.3 are installed, I have access to my mobile on my PC , when I do the process of flashing or fastboot I turn off the mobile and I unplug USB cable from my mobile, I press the keys to do flash or fastboot (I don't see no green android just a led light turn on) and connect the USB cable, problem is my PC can't find the mobile device, I use adb function eg. adb devices or fastboot devices I get nothing no device no info.
Is this problem with Win 10?
Was my problem understood in 2. - ?

Sa9aX said:
Is this problem with Win 10? Was my problem understood in 2. - ?
Click to expand...
Click to collapse
Most likely a drivers problem, Windows10 fails to tell you that it's not installed the drivers that you pressed the install button on. It also fails to assign the right drivers when you add the phone in flashmode/fatsboot.
You will need to add them manually.
Go into safe mode and use 'driver signing disabled', try adding the drivers again. Then plug in you phone in flashmode/fastboot, then look in the device manager for the phone and change it
Several people have reported success with Zdiag drivers

Didgesteve said:
Most likely a drivers problem, Windows10 fails to tell you that it's not installed the drivers that you pressed the install button on. It also fails to assign the right drivers when you add the phone in flashmode/fatsboot.
You will need to add them manually.
Go into safe mode and use 'driver signing disabled', try adding the drivers again. Then plug in you phone in flashmode/fastboot, then look in the device manager for the phone and change it
Several people have reported success with Zdiag drivers
Click to expand...
Click to collapse
Thanks! Great Info.
I removed the drivers manually in device manager and then used Zadig, now in command mode I getting something.
Next I have to figure how root the phone, do I need to flash twrp.img ?
I have all this stuff and I got confused which one I need to do next:-
boot.img
boot-G8141-47.2.A.10.45-hideunlock-rooted.img
twrp.img
twrp-3.2.1-0-maple
xperifix.zip
ss_maple.zip
zestmaple-latest.zip
ScriptWINg-master.zip

Sa9aX said:
Thanks! Great Info.
I removed the drivers manually in device manager and then used Zadig, now in command mode I getting something.
Next I have to figure how root the phone, do I need to flash twrp.img ?
I have all this stuff and I got confused which one I need to do next:-
boot.img
boot-G8141-47.2.A.10.45-hideunlock-rooted.img
twrp.img
twrp-3.2.1-0-maple
xperifix.zip
ss_maple.zip
zestmaple-latest.zip
ScriptWINg-master.zip
Click to expand...
Click to collapse
Back again...
I figured all out:-
twrp-3.2.1-0-maple.img
boot-G8141-47.2.A.10.45-hideunlock-rooted.img (latest firmware)
Magisk Manager

Botched Graphene install on Pixel 3A - need help restoring default settings

Hello,
I am hoping for some advice on how to revert my phone back to its original "factory settings" after a botched instal of GrapheneOS onto an unlocked Google Pixel 3A.
I got to the point at which I needed to Flash the Graphene Rom to the phone, but rather than installing, I received a message from Smart Screen MS edge asking if I really wanted to run as it's protecting my PC - I clicked run anyway and a blank command line window appeared for a second. Now my pc doesn't seem to be recognising the pixel 3A when I type ADB devices. My phone is currently in Fastboot mode "unlocked" and I'm hoping for some advice on what to do next. I'm total noob, so unsure how to start the process over (return the phone to it's previous state) before, maybe, trying again on a different PC.
I have since turned on my phone and Android 11 is still present and seems to work fine (however it gives me a warning on startup that the bootloader is unlocked.
Any help would be very much appreciated - thank you in advance.

Is all what happened that your phone now:
complains about "'maybe not safe bootloader unlocked".
This is just what android does when the bootloader is unlocked.
This you did before trying the flash.
If you want the warning gone simply lock it again.
However if you into the market for graphene OS then I would recomend: along with following their guide to a t to also read up here on xda about the general rooting unlocking thing a bit more so you get the overall process a bit better perhaps next time.
About windows. There are so many tools out there to help ya with disabling some of it's spying, turning off smartscreen, auto - uploads of all your data to M$oft, etc etc.
It's not hard to find.

Thanks for the response - I think I've worked out what is going on.
Typing ADB devices, my PC recognises the phone until I put it into fastboot mode - typing adb devices when in fastboot comes back with nothing and therefore when I try to flash, I assume the devices aren't talking to each other.
Not sure if there's a work around or whether it's a case of finding a new PC to try it on?
Thanks again.

Ignore

deroller said:
Thanks for the response - I think I've worked out what is going on.
Typing ADB devices, my PC recognises the phone until I put it into fastboot mode - typing adb devices when in fastboot comes back with nothing and therefore when I try to flash, I assume the devices aren't talking to each other.
Not sure if there's a work around or whether it's a case of finding a new PC to try it on?
Thanks again.
Click to expand...
Click to collapse
try another USB port first; use USB 2.0 if available! Reinstall google ADB drivers, make sure to use latest!
If above will not help:
on your computer: open device manager; on your phone: put your phone into fastboot; connect your phone to the computer WHILE keeping an eye on device manager; as soon as you'll connect your phone new device will appear in device manager ("unknown device" most likely but it might be some "android device" or "ADB device" too); right click it —> update driver —> automatic driver update worked in most cases for me, if not, go manual way and select google's "android fastboot device" (or something like that, can't remember actual name of the device); after driver install confirmation you should be good to go

Tamsta_T said:
try another USB port first; use USB 2.0 if available! Reinstall google ADB drivers, make sure to use latest!
If above will not help:
on your computer: open device manager; on your phone: put your phone into fastboot; connect your phone to the computer WHILE keeping an eye on device manager; as soon as you'll connect your phone new device will appear in device manager ("unknown device" most likely but it might be some "android device" or "ADB device" too); right click it —> update driver —> automatic driver update worked in most cases for me, if not, go manual way and select google's "android fastboot device" (or something like that, can't remember actual name of the device); after driver install confirmation you should be good to go
Click to expand...
Click to collapse
Hey there,
This is brilliant - thanks for all the advice. Having this support is helping me gain the confidence to learn more, research more, and then give it a go.
All the best.

deroller said:
Thanks for the response - I think I've worked out what is going on.
Typing ADB devices, my PC recognises the phone until I put it into fastboot mode - typing adb devices when in fastboot comes back with nothing and therefore when I try to flash, I assume the devices aren't talking to each other.
Not sure if there's a work around or whether it's a case of finding a new PC to try it on?
Thanks again.
Click to expand...
Click to collapse
thats if I am not wrongly remembering my experience:
because now your phone is in fastboot mode thus it won't show up with that command anymore.
Try: 'fastboot devices'
I imagine you put it into fastboot through: 'reboot fastboot' when you where in adb?
When in fastboot you can go on and flash the recovery and such.
Are you still in need of help here?

Hey, thanks for the clarification - been away and so haven't implemented all suggestions, yet.
I typed "adb reboot booloader" which I assumed put it into fastboot mode and then unlocked it using "fastboot flashing unlock".
I tried fastboot devices but the PC still doesn't see the phone. I'm going to try the update usb driver suggested by Tamsta_T and see how it goes.
Thanks for your help.

Realme C21Y HardBrick - It says USB Device is faulty but disappears after 2 seconds - I can't enter download mode

I corrupted my phone's root/system/etc files and when I restarted it, it wouldn't turn on and got stuck on the realme logo. i hold my phone vol+ and - and power key and when the realme logo comes up, i release the power key, i think download mode opens, but it usb device is faulty for 1-2 seconds and disappears immediately, meanwhile in device manager it shows unknown device for 1-2 seconds and disappears. After 10-15 seconds there is a usb connection sound but nothing happens. I can send adb commands but I have to confirm the confirmation window but I cant.
Please help me, how can I fix it?

Does adb devices say "unauthorized"?
Are you sure that it's ADB and not fastboot or EDL that is appearing?
You can use usblog.exe to see what's popping up and down. Just run it.

Install Unisoc/Spreadtrum drivers and then see if your device is recognised as a SPD USB device under device manager and let me know here

Renate said:
Does adb devices say "unauthorized"?
Are you sure that it's ADB and not fastboot or EDL that is appearing?
You can use usblog.exe to see what's popping up and down. Just run it.
Click to expand...
Click to collapse
Yes, I get the unauthorized message as below. If I can somehow authorize it, I will be able to enter fastboot mode and flash the stock rom.
mvikrant97 said:
Install Unisoc/Spreadtrum drivers and then see if your device is recognised as a SPD USB device under device manager and let me know here
Click to expand...
Click to collapse
Okay, I'm trying

mvikrant97 said:
Install Unisoc/Spreadtrum drivers and then see if your device is recognised as a SPD USB device under device manager and let me know here
Click to expand...
Click to collapse
Please try a different usb port on your computer.
Don't use USB 3.0 port.
If nothing works then either the phone's usb is malfunctioning or your PC.
Don't use USB extension to connect your phone, plug directly to your computer port.
Also update your PC drivers using driver booster free software and then set restart and try again

mvikrant97 said:
Please try a different usb port on your computer.
Don't use USB 3.0 port.
If nothing works then either the phone's usb is malfunctioning or your PC.
Don't use USB extension to connect your phone, plug directly to your computer port.
Also update your PC drivers using driver booster free software and then set restart and try again
Click to expand...
Click to collapse
I updated with Driver Booster, no luck.
I only tried the front USB ports, do I need the back ones? There are 2 2.0 and 1 3.0 port on the front
The computer is new so I don't think it's defective, the phone is charging and I was using it before it went brick.

I also modified the boot file to install a new GSI and used the following guide.
Spoiler
First, you need to unlock fastbootd:
1. Download the stock ROM version 91: Download and extract the .pac file Link
2. Install the SPD research tool and drivers: GDrive
3. Open it
4. Click on the single gear icon
5. Select the .pac file of the stock rom
6. Wait until it loads
7. Click on the two gear icon
8. Find BOOT in the list
9. Right-click on the path next to it
10. Download here and select boot_r1.img
11. Click OK and then click the arrow icon
12. Turn off your phone
13. Press and hold Power + VolumeDown until you see the text "Downloading"
14. Release the buttons after seeing
15. Wait until you see the text "Passed"
16. Click on the Stop icon, disconnect your phone and turn it on
[/ISPOILER]

@leanord Can you help me?

The 0000/0002 is standard Linux goofiness when you enable USB gadget but you don't initialize anything or add any functions.
This often pops up during boot sequences. It means nothing. It does cause Windows to say "Invalid device".
The 22d9/2769 appears to be normal ADB and since you're getting "unauthorized" shows that everything is fine.
Are you in recovery or regular Android?
Stock recovery usually is ADB secure and you don't have the keys for it.

Renate said:
The 0000/0002 is standard Linux goofiness when you enable USB gadget but you don't initialize anything or add any functions.
This often pops up during boot sequences. It means nothing. It does cause Windows to say "Invalid device".
The 22d9/2769 appears to be normal ADB and since you're getting "unauthorized" shows that everything is fine.
Are you in recovery or regular Android?
Stock recovery usually is ADB secure and you don't have the keys for it.
Click to expand...
Click to collapse
I don't fully understand your question, but I have the stock recovery, I didn't install TWRP, and I installed dotOS 5.2 as GSI. I think I corrupted the fastboot, download mode boot files in the root files. I will take it to the service center, but if you have a solution, you can write, I don't want to give money.

It's gone to stock recovery and you don't have keys.
You need to try buttons to get it into bootloader (fastboot). Or did they disable that?

Renate said:
It's gone to stock recovery and you don't have keys.
You need to try buttons to get it into bootloader (fastboot). Or did they disable that?
Click to expand...
Click to collapse
It may have been disabled or because I corrupted system files.

Wanted? I came, to flash the phone, you do not need to press anything except the volume keys, the power button is only a catalyst, you need to hold it down until the screen goes out, and then just Keep the volume - and flash as usual, the main thing is to keep it immediately plugged into the PC with a ready-made flasher

What I have done:
1. The screen is off
2. I hold down the volume - and power button.
3. The phone vibrates and as soon as the realme logo appears, I plug the usb into the phone and release the power button.
4. The computer receives the message "USB Device not recognized, malfunctioning" and the unknown device is added to the device manager (It doesn't come anymore, I don't know what happened, I installed a lot of drivers.)
5. After 20 seconds, the USB connection sound is heard and the name of my phone is added to the "universal serial bus devices" section of the device manager.

Luuukie said:
What I have done:
1. The screen is off
2. I hold down the volume - and power button.
3. The phone vibrates and as soon as the realme logo appears, I plug the usb into the phone and release the power button.
4. The computer receives the message "USB Device not recognized, malfunctioning" and the unknown device is added to the device manager (It doesn't come anymore, I don't know what happened, I installed a lot of drivers.)
5. After 20 seconds, the USB connection sound is heard and the name of my phone is added to the "universal serial bus devices" section of the device manager.
Click to expand...
Click to collapse
Why are you doing it? You should sit in the flash driver, and not watch how the device is connected, Windows will not have time to see exactly what is connected until you start flashing

leanord said:
Why are you doing it? You should sit in the flash driver, and not watch how the device is connected, Windows will not have time to see exactly what is connected until you start flashing
Click to expand...
Click to collapse
SP Flash Tool doesn't see my device so I can't flash it. If you mean Fastboot, I can't get into it.

By the way, that font that's showing up in my UsbLog is UGLY.
I readjusted things, you can download a new copy that is prettier.

Oh, this is a Unisoc.
I know a lot about Qualcomm, some about Mediatek and almost nothing about Unisoc.
Surely there is some way to get this into Unisoc ROM bootloader mode?
There are either test points or you can disable the eMMC?
If you could pull recovery and mod ro.adb.secure=0 you'd have recovery with ADB at least.

Renate said:
Oh, this is a Unisoc.
I know a lot about Qualcomm, some about Mediatek and almost nothing about Unisoc.
Surely there is some way to get this into Unisoc ROM bootloader mode?
There are either test points or you can disable the eMMC?
If you could pull recovery and mod ro.adb.secure=0 you'd have recovery with ADB at least.
Click to expand...
Click to collapse
I'm sorry, I don't know that much. But if you tell me the steps how to do it, I can do it.

@leanord when installing GSI, I flashed boot_r1.img from your Realme C21Y GSI installation guide, did you disable fastboot or something?