Related
[SOLVED. READ BELOW FOR DETAILS]
HI all.
I've managed to brick my Hero (T-Mobile G2) by flashing the wrong SPL file.
To make things more difficult I've lost the USB cable.
I can still:
Power+Menu (three vibrations + blinking green)
Power+Back (Fastboot)
Power+Search (Storageclean)
Power+VolumeDown (HBOOT, SD checking ...)
Is there a way to reflash the right SPL with one of these menus?
I've not found any similar case here and in MoDaCo.
Thanks in advance.
[SOLUTION]
This case is particular as there is no system available to use the "adb shell" commands. Nonetheless it's recoverable.
At least in one case
Almost everything comes from MoDaCo.
Despite I would say I'm not a real newbie, this time was a little bit harder than with other embedded devices for some reasons I'll explain later.
What do you need?
1. A miniUSB cable. Now I know that any miniUSB can work.
2. A Windows XP PC. A Linux or Mac OS X should also work. Read below.
3. The right USB software driver (I used this one) otherwise it won't work.
4. A modified recovery image (I used this one) that has flashing capabilities from the SD.
5. A working SPL (Second Program Loader) image (I used this one, thanks to the enlightner.
6. A system ROM image (again, I used this one).
What was the problem?
I used to play also with a Magic and still had an SPL zip of its on my SD.
I already had rooted and modded my Hero with MoDaCo's mod.
By mistake I flashed that SPL zipped image into my Hero and since then nothing was working any more.
The boot process was simply stopping at the "G2 Touch T-Mobile" screen up to the complete battery drain.
The directions found here were ineffective due to the fact that there was no running system to execute the "adb shell" commands.
I am using 99.99% of the time a Linux laptop but decided to get a Windows XP PC in order to simplify the troubleshooting while asking people for help and hints.
Maybe in the future I'll dare to reproduce the problem and solution with Linux. Maybe,
But let's see a stepwise procedure.
How I solved it (impossible to me without MoDaCo's and englightner's help, kudos to them)!
0. Unpack the USB driver and the recovery image ZIP files somewhere into your PC. Put the SPL and the system ROM image zip files into the SD card. Use the root directory of the FAT partition in case you have already partitioned it.
1. Switch off the Hero (by pulling the battery out).
2. Turn it on again without the USB cable in by pressing the back and the power keys. I've noticed some different behaviour if you keep the cable plugged in.
3. A white screen (the Initial Program Loader aka IPL aka Fastboot) will pop up.
4. Plug the USB cable in both the Hero and the PC. The screen will now show in red "FASTBOOT USB".
5. Windows should warn you about some unknown hardware having been plugged (Android 1.0). Ask for a manual installation by browsing to the directory where you unpacked the USD driver. Install it. No reboot is required (unbelievable!).
6. Open a command line session on your PC (Start-->Execute-->CMD on Windows), change the current directory (cd) to where modified recovery image has been unpacked and where both the fastboot.exe and cm-hero-recovery.img files are located.
7. From the command line run this command (without the quotes): "fastboot boot cm-hero-recovery.img". You'll see a green progression bar rising on the right side of the Hero screen and after 1 second you'll see the modified recovery image running.
8. At this point I tried to recover a previously saved nandroid backup. But for some reason this time the recovery was complaining about a chown/chmod not being able to change the permissions on a system file! So it's useless to try it.
9. Instead I asked to flash the SPL zip file. It worked fine and I asked for a reboot.
10. the final step was to pop the recovery tool again (Home+power, keep the home pressed until you'll see the friendly black and green screen) and to slash the system ROM zip file.
I also reset all user data before doing it. I'm not sure whether this reset is required.
11. At the reboot the flashed system ROM was happily waiting for me to customise the settings.
12. As a last check, I rebooted once again the Hero to see whether the solution was permanent. And it was.
Few suggestions for seniors.
Please, please be patient with newbies. This could be the first time they hit the wall and panic and frustration can play an important and irritating role.
Please, please be as precise as possible. What a senior thinks is an implicit piece of information, can lead to hours of frustration for the newbie. For example, the SUB driver installation is not mentioned very often in any thread. It looks trivial. It's not.
Please, please be positive to newbies. By encouraging them they'll become less newbies than they are now.
And a few suggestions for juniors (like me).
Please, please don't panic! If there's a solution, you don't need to panic. If there's none, you don't need to panic as well.
Please, please be precise in describing the problem (I've not been myself). Small unseen details can matter a lot.
Please, please don't blame people for late answers. Very probably they are busy with their own job, life or hobbies.
Please, please remember that if you are in trouble is very probably due to your own mistakes. Not someone else's. You are playing with low level stuff, not just application settings.
If you decide to follow someone's directions, please do it carefully. If you take some decisions on your own, please document them in the thread.
If you can get to fastboot with power and back, then all is not lost. And most importantly it's not a 'brick'. A 'brick' is a device that won't turn on.
You can flash the recovery via fastboot (using this guide) then a new ROM (I suggest my custom ROM) but, er, you're obviously gonna need a USB cable!
P
I was already using your marvelous mod, though.
I only took the SPL file from the wrong directory (I have been playing also with Magic, aka G1).
The cable is a huge problem, now.
At the moment I'm using a mini-USB cable which is good for charging the battery, but has no effect on the communication side.
Can I put some file in the SD card from my PC in order to have it booted into?
I still have a couple of nandroid backups in the SD but have no idea whether this makes any difference.
Anyway, thanks not just for the hints. Your 1.5 (1.5.1 when I'll fix my problem) rocks!
A real miniUSB cable should work fine. Yours must be only wired for charging. Go and buy one.
There's no other way to do it unless power+home gets you into recovery (which it sounds like it should?)
P
The mini-USB comes from my USB 2.5" HD.
It works with cameras and other mini-USB devices for full dvice access.
But it does not work with the Hero.
The original cable looked different from this one because of the asymmetric shape (and possibly an extra pin or two).
The Hero cable looks like it's proprietary design and buying one seems quite difficult. Would any HTC USB cable work?
Now I'm not in the Netherlands anymore and here the HTC stuff looks quite uncommon to have a cable lent.
I never use my HTC cable, I use a standard mini USB cable.
P
OK.
I've bought a brand new mini-USB cable. It works with my Nokia phone, my digital camera dnd also my USB disk.
1. I've donwloaded the file from the guide MoDaCo referred previously.
2. I've unpacked the ZIP file, opened the CMD session, CDed to the directory containing the adb.exe file
3. I've booted the phone to the FASTBOOT (VOLUMEDOWN+POWER)
4. I've connected the phone to the cable.
5. The HERO screen says now "FASTBOOT USB"
6. I've run the command "adb shell reboot bootloader"
7. I get "error: device not found".
What's next?
P.S.
Steps 3 and 4 are not mentioned in the guide, though.
You can't use adb shell from the fastboot screen, you need to boot a recovery image using the "fastboot boot <filename>" command.
Just of curiousity. What is the HBOOT version displayed on your fastboot screen?
Could you type all the text it displays?
I might be able to help you out.
Try following the guide linked above.
You can't do ADB until you've done the 'fastboot boot cm-hero-recovery.img'.
Seriously... how hard can it be to read thru a handful of steps!
P
You are right! It's hard unless you already know how to.
I quote:
- download this file and extract it to your PC or mac
- open a command prompt to the directory containing the extracted files
- type the following commands (prefix each command with ./ if you're on a mac)
So far it's trivial ...
adb shell reboot bootloader (wait for device to reboot into bootloader)
fastboot boot cm-hero-recovery.img
adb shell mount /sdcard
adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img
adb shell flash_image recovery /sdcard/cm-hero-recovery.img
That could also be trivial if:
1. I knew about the driver installation (quite later in the thread)
2. I knew in which initial status the phone is to be
Of course, a bit at a time I find everything.
Maybe re-editing the original post to include all the bits in one single place would both boost the success rate of n00bs like me (really) and lower the amount of stupid questions (really) like mine.
Anyway, I need to thank you very much!!!
Hmm, bad news, ust spoken to an extremely knowledgeable friend of mine, and he says your device is knackered.
P
I'm impressed the SPL actually booted on a Hero.
It's is a "real" Hero you have right? aka T-Mobile G2 Touch?
Fastboot can be used when you are in HBOOT, with FASTBOOT USB being displayed.
So, if this doesn't work, you're screwed.
- download this and extract the rom.zip
- copy the .zip to your SD card and name it HEROIMG.zip
- turn on your device with volume down+ power
If it doesn't start flashing, buy a new Hero.
P
packetlss said:
You can't use adb shell from the fastboot screen, you need to boot a recovery image using the "fastboot boot <filename>" command.
Click to expand...
Click to collapse
Good to know. I have no idea about this specific device!
And the help is quite fragmented among a large number of threads.
packetlss said:
Just of curiousity. What is the HBOOT version displayed on your fastboot screen?
Could you type all the text it displays?
Click to expand...
Click to collapse
HERO CVT
HBOOT-1.33.2005 (HERO10000)
MICROP-010e
RADIO-6.35.05.15
Apr 20 2009,15:30:43
packetlss said:
I might be able to help you out.
Click to expand...
Click to collapse
I hope so.
Try doing what modaco suggested and see where that ends up.
modaco said:
So, if this doesn't work, you're screwed.
- download this and extract the rom.zip
- copy the .zip to your SD card and name it HEROIMG.zip
- turn on your device with volume down+ power
If it doesn't start flashing, buy a new Hero.
P
Click to expand...
Click to collapse
I hope to fix mine.
Anyway, is there any comprehensive guide about the booting (not rooting) process with the software stack and the "cheat codes"?
I don't think I'm really a n00b, but the fragmentation of information is quite large for these marveloous Android phones.
The HEROIMG.zip has been flashed, I presume, as a vertical blue bar appeared on top right screen.
After fre minuted the process ended ... with no news.
At the reboot everything is again as before.
Home+Power won't make the CyanogenMode+JF menu pop up.
The simple boot itself won't make my Hero botting in any system.
Only a big "G2 Touch T-Mobile" on the black background.
Now what?
That HEROIMG.zip contained a hboot. When you boot to bootloader is still the same?
You say 'fastboot boot recovery.img' (as per my instructions) didn't work?
P
'fastboot boot recovery.img' works.
It's the subsequent step that doesn't. I cannot mount /sdcard (error: device not found)!
And even recovering a previous nandroid backup won't help.
What I understand there's something in between the fastboot and the actual image (the SPL?) that is missing doe to my original error.
Does the bootloader still show the old version?
P
Hoi Hoi people
i got myself a GT540 Optimus <yes total newbeee to android>
It came with a deal for free and its my 1st android :0
anyway
After USING the official way (silly me )to update I now have some odd Portuguese apps installed ? Stuff from SAPO.pt ???
I didn't do any Sync backup as i just got the phone and its basically empty
I used the Updater tool from LG connected and all went well But after I look I was able to change the language to ENG but it has quiet a few Portuguese Apps installed...
I am in Holland so i cannot see how this updater decided to give me a POR image ?
Now i could make a guess and say the IMEI is for Portuguese market(?) and the dutch INTERNET cheapo middleman I got the deal from has bought a bunch on the gray market ..
Whatever it is i don't care
I would like you guys now to point me the right way
I just flash the thing myself
I think the tool i need is called KDZ ?
Please someone point me to the right post I am looking but seem to get nowhere
just more confused
Thanks guys
B.T.W I am not too inept . I am used to flashin me HTC HD all the time ..
Follow the thread: http://forum.xda-developers.com/showthread.php?t=802895
to update to v2.1 Eclair.
or
follow
http://forum.xda-developers.com/showthread.php?t=857213
to update to Quarx's OpenSwift project v2.2.1.
Make sure you read the instructions very carefully.
Toen je de officele lg updater gebruikte, welke taal was hij toen?
Het kan zijn dat je dat aan het begin verkeerd heb ingesteld.
Joost
Thanks a lot guys
I followed the hints and now my LG is dead ..
LOL
This is rather annoying
1st I get a Crap gray import from 2call
then LG puts a Portuguese update rom on it??WTF!>?
while i choose NETHERLANDS with language english
but nevermind
buy **** buy twice thats life
My 1st and last lg phone ?/
What kind of rubbish is this
u update using the official LG tool and they play a freckin foreign rom onto my LG (SAPO.PT) then I cant update it at all anymore using the tool . So i look for alternatives but thats just made it worse ...
Really really poor this ..
Now ...I followed the guide but it didn't work ..well it did until restarted
My lg is now black. Dead ! doesn't start up at all !
Doesn't start no-matter what i try !
not even emergency mode.
And no guys I read the instruction word for word !!!!
I followed it to the letter !!!!! and the update did work ..Just now it doesn't start at all anymore.
I should of known reading around
there are too many update ways people are doing this ..Hack tool or original KDZ ..or just Black system way ..Too many loopholes for things to go wrong ..but now too late
Hmm...
Try a reflash...
This is a guide I followed from another forum, and posted elsewhere with some minor additions in case anyone had problems.
The guide is from a forum post at the android forums,it is NOT my work, the added bits are mostly what I have found from browsing here and from asking questions. While I can't be held liable if you mess your phone up having done so myself I thought this could helpa few people and save them searching various threads for answers so hope it helps
The guide
To install this ROM you need to have fastboot enabled on your phone. If you have Android 1.6/2.1 installed from LG, then fastboot is not enabled. I will explain how to enable fastboot on your phone (this involves re-flashing/replacing your currently installed firmware):
I am unable to post links yet so you will have to copy and paste the appropriate link into your browser replacing the ** with tt
KDZ Updater Carphone Warehouse Unlocked.zip can be downloaded at h**p://goo.gl/7aRTc - A link to a zip archive with all the files needed to flash to Android version 2.1 with fastboot (Carphone Warehouse Unlocked)
KDZ Updater Europe Open.zip can be downloaded at h**p://goo.gl/BOcYT - A link to a zip archive with all the files needed to flash toAndroid version 2.1 with fastboot (Europe Open)
Download the version that best applies to you, if you live in the UK, I'd recommend you download the Carphone Warehouse Unlocked version, whereas if you live in Europe, I'd recommend the Europe Open version (simple right? )
I live in the UK and used the open rom from Europe as the Carphone Warehouse rom would not install
Now, how to flash these versions; I'll explain in detail how to flash the ROM's from starting with backing up.
Instructions to install ROM with Fastboot:
1. Before you start, make sure you backup all your data by installing the z4root.1.3.0.apk file onto your phone, then open it and choose 'Permanent Root'. Your phone will root and reboot. Then go to the Market and install 'MyBackup Root', open it and do a backup of your apps and personal data (contacts, sms, call log etc.) Once this is done, go to Settings>SD Card and Phone Storage>Unmount SD Card, a notification in the notification bar should appear saying 'SD Card safe to remove'. Remove the battery cover and remove the SD card and store it in a safe place. Then continue to step 2.
2. Extract the .zip file you downloaded to your computer (e.g. your desktop). Open the folder and install MSXML 4.0 SP3 Parser (msxml.msi).
3. Once that has finished, install LGAndroidDriver_WHQL_ML_Ver1.0_All_Win7.exe which are the drivers so your computer will recognize your phone.
4. Next, open KDZ_FW_UPD.exe
(i) Change 'Type' to '3GQCT' *THIS IS A MUST, THE UPDATE WILL NOT WORK OTHERWISE AND YOU MAY BRICK YOUR PHONE*
(ii) Make sure 'PhoneMode' is set to 'DIAG'
(iii) Browse for the 'V20B_00+Fastboot.kdz' file.
5. Prepare the phone by enabling USB Debugging by going to Settings>Applications>Development>Enable USB Debugging and connect the phone to the computer via USB cable and wait for the drivers to install for the phone.
6. Click 'Launch software update' and do not use your computer until the update is complete. The update will take roughly 10-20 mins to complete.
If you have a problem with this try a different rom, this guide offers two to choose from.
Instructions to install CyanogenMod:
Once the update is complete, your phone will reboot, what you need to do is power off the phone and whilst the phone is off, press and hold the 'Camera' button all the way ANDpower on the phone, make sure you hold the 'Camera' button. The phone will display the LG logo and disappear, then display a blank screen. The phone is now in fastboot mode!
Now you want to download this file: Flashing CyanogenMod.zip and extract it to a folder called 'Android' (without the quotes '') on the C: drive (you'll probably need to make this folder yourself.
1. Now open CMD with administrator privileges (Search for CMD in the start menu and right click on 'cmd' and click 'Run as Administrator' )
2. Connect the phone to your computer via USB cable and wait for the necessary drivers to install.
If when connected with a usb cable the computer says "waiting for device" and nothing else happens try installing the fastboot drivers. You can do this by going to the control panel of your pc, from the Windows start menu, opening the list of devices and where you see the one representing your phone (likely, as was the case with me, it will say android and have a yellow exclamation mark over it). Different versions of Windows do things slightly different but what you need to do is simply update the driver by choosing the icons properties box choosing UPDATE or INSTALL DRIVER and when asked pointing it to the folder where you unzipped the drivers.
3. Then go back to the cmd window and type:
Code:
cd C:\Android
(i) Then type:
Code:
fastboot.exe -w
(ii) Once that's completed, type:
Code:
fastboot.exe erase system
(iii) Once that's completed, type:
Code:
fastboot.exe flash system system.img
(iv) Once that's completed, type:
Code:
fastboot.exe flash boot boot.img
(v) Once that's completed, type:
Code:
fastboot.exe reboot
4. Your phone will now reboot with CyanogenMod 6.1.1 (Android 2.2.1). The first boot might take longer than a normal boot.
If your phone stays at a blank screen you simply forgot to do one of the above steps, in which case simply repeat them. It is likely if that happens that you simply forgot the flash boot image instruction.
5. You can now re-insert your SD card and go to Settings>SD Card and Phone Storage>Mount SD Card
Enjoy!
The instructions for flashing both the firmware with fastboot and flashing CyanogenMod are included in the zip archives called 'Readme'. I'll update the links so that you'll always have the most up to date version of CyanogenMod available for download, note that if you choose to update your phone you will loose all your data including apps etc. so backup before you update
And that, with a few comments added by myself, is the guide.
Once you have set your phone up the way you want power off your phone. Hold the HOME and POWER buttons down while the LG logo appears and you will see a menu appear on screen.
Using the volume down key to navigate the different menu choices, and the camera button to select an option choose the BACKUP OR RESTORE option and from the sub menu that it will give you choose BACKUP.
This will make a backup of your phone AND all your data, if you ever mess up an update or think you have damaged your phone in the future simply holdthe POWER and HOME buttons down and when the menu appears choose the RESTORE option
Click to expand...
Click to collapse
And...
Don;t forget to install Fastboot drivers.
Dude
thanks a lot for your lengthy post and effort .I appreciate it .
but unfortunately U seem to miss the post I wrote.
MY LG doesn't even start anymore after using the Hack tool to upgrade it ...
SO its futile ??
I cant start the phone at all ...
After following yesterdays advice Its dead ..
Great init
Oh dang. Doesn't even turn on? No LG boot logo?
Well...if it's bricked...the only three ways are:
1) Get it repaired/replaced.
2) Buy a new phone.
3) Use it as a paperweight.
=)
No my friend ..its DEAD !!!!
following the guide to the letter
Installed parser got the hack tool
run all as admin and made sure I started windows enabler
All the things in the guide
worked a charm until reboot
Not its black and dead!!!
ANY IDEAS !!!!?????
Have you tried this...
If you did it with kdz updater than:
pull out battery, sim and sd
connect phone with computer
disable lg modem in the device manager
flash a rom with fastboot
go in fastboot by camara+power
connect to computer
type 'fastboot -w' and 'fastboot reboot' in cmd
Click to expand...
Click to collapse
I cannot see why this could work
The phone is dead ! it doest charge! it doesn't connect to the pc ! USB cable in out makes no difference !
I d love to try but how ??
contact303 said:
I cannot see why this could work
The phone is dead ! it doest charge! it doesn't connect to the pc ! USB cable in out makes no difference !
I d love to try but how ??
Click to expand...
Click to collapse
You can try by pulling out your battery, SIM card and SD card...
Note to you: Try everything that is possible and don't give up. Maybe you will fix it if you try.
Yes of course man I ll try thanks for the encouragement and your effort
It doesn't power at all
I DOESN'T connect to the pc
It Makes no difference if i have battery in or out .
sd card and sim are long removed ..and I tried with and without battery as well.
It updated, then rebooted to never come back ...
update tool reported Finished at the end
but its dead !!!
I understand id have a chance if i had at least a boot but I dont It dotn boot it dont Power up
Try getting into Emergency/Download mode by holding down "Volume Down" button and plugging into PC.
After that...try reflashing.
GL man.
Nope
Tried that combination as well
contact303 said:
Nope
Tried that combination as well
Click to expand...
Click to collapse
Opps sorry..."Volume Down" + "Power BUtton" while plugging into PC.
Try a hard reset as well...
Hold down VOLUME UP + HOME + SEARCH buttons for 5 seconds. (But phone needs to be turned on...)
MegaBubbletea said:
Opps sorry..."Volume Down" + "Power BUtton" while plugging into PC.
Click to expand...
Click to collapse
LOL yeah i knowww
I tried that as well
NO luck
hard reset i cant Its not on ...
Well...does anything happen when you press the "Power button"?
Dude LOLOL
Read again my 1st 2 posts
ITS dead ! nothing happens!
With battery or without makes no difference
NO BOOT! No power nothing
i followed the upgrade post in your 1t reply
it went all very well as i say
then it reboot and never got back
Hmm...probably give it a rest for a while...and then try again.
If all else fails..last resort.
Send back to LG for repairs or replacement.
mmh
So I gues iam screwed ..
I didn't even want to get into moddin the gt540 . Just the OFFICIAL 2.1 release really ..
And even that LG cant do without f&*kin me phone to Portuguese
So Well done LG )
Hi guys
Let me start off by saying..I should have never attempted this myself.
I'm hoping somebody could please help me with my somewhat-bricked device..bricked in the sense that I don't know what to do with it. (i'm a noob to this). I've tried installing a custom rom and completely screwed up my dell streak 5.
So the phone doesn't boot anymore and just takes me to the option to install update.pkg off the sd card. I added the file along with recovery.img to the sd card.
360 17397 00 May 31, 2011 PKG Recovery Hash Latest Retail rom
My problem is that I cannot for whatever reason get Flashboot to work in order to flash the recovery.img first. under device manager you see android phone/android adb interface but still can't manage the connection to use cmd prompt/fastboot.
Is there any other way of getting the recovery.img to work without fastboot..maybe thru the sd card. I have no idea what i'm doing anymore. I've tried installing the update.pkg but after installation it just stays on the dell logo loading screen forever.
PLEASE help if you can.
Well lets start off to get you back on a stock rom, as it sounds like that would be the easiest at this point. We can move on to a custom rom from there.
The pkg file you downloaded....did you rename it update.pkg ?
If not, rename it update.pkg and make sure it is on the root of your sd card. Get to the recovery menu where you have the option of upgrading from update.pkg and choose it. In about 5 minutes, you'll have a clean stock rom.
I tried installing the 360 rom listed on http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak
I did name it update.pkg
It went through the installation phase but on reboot it doesn't get past the Dell Logo loading screen. Any suggestions?
On the screen where you choose upgrade from update.pkg, choose factory reset and see if that helps
Tried both..unfortunately, same end.
Is flashing recovery a required step prior to doing this..because I was unable to do that.
Also, Thank you for taking an interest. I really appreciate it.
yes, you need to have the recovery for the rom you are flashing (at least when it comes to stock roms). My understanding is that the pkg file is encrypted and the recovery decrypts it.
I'm going to try to start from scratch here. I am also assuming you are using a Windows PC.
Download the drivers from Dell. Here's the link:
http://support.euro.dell.com/suppor...dateid=-1&formatid=-1&source=-1&fileid=433681
Install them and reboot your pc.
Download MultiRecoveryFlasher from here:
http://forum.xda-developers.com/showthread.php?t=1000455
Extract it to somewhere on you pc where you can find it.
Now this hasn't been updated to include 360's recovery, but that's ok. We don't have to run the utility. It's the support files that are included that we are going to use.
Download the recovery.img for 360 (which I think you have already done)
Put the recovery.img in the root folder of MultiRecoveryFlasher. There should be other files in there such as fastboot.exe, adb.exe, etc.
Power down your phone and restart it in fastboot mode (hold down camera and power button together until you get a white screen. When fastboot appears in upper right, select it and plug your phone into your pc)
Verify the phone displays fastboot ready
Open a command prompt on your PC
Type in the following command: fastboot.exe -i 0x413c flash recovery recovery.img
Once that is done type in the following command: fastboot.exe reboot
Get ready to hold down the Volume + and - as soon as the screen goes black.
Now choose Upgrade from update.pkg
It should work now. If not, someone else may have to help you with another method such as QDL tool. I've never had to use that.
This is a screenshot of the problem i keep running into. i installed the drivers just as you said and am at the step with fastboot.
imgur [dot] com/gw2A0
Any advice? Thanks again
im an idiot.
i got fastboot to run and send over the recovery.img
currently installing the update.pkg but its still stuck at the Dell Logo screen upon reboot. No idea what is going on.
FIXED. You're a miracle worker. Thank you so much.
Only problem I have now is an irritating sequence of flashing buttons every now and then. Have you had a similar issue in the past?
THANK YOU so much again!
Are you on a stock rom still? Or have you moved on to a custom rom? Typically the flashing led's happen when you are running a rom with an "incompatible" baseband, but that should be pretty near impossible if you are running a rom installed from an update.pkg rather than an update.zip.
running the update pkg off the wiki site.
Only other problem I've noticed is that I can't get it to root. I've tried gingerbreak and superoneclick..both of which worked flawlessly in the past.
Baseband GAUSB1A134700-US
KERNEL 2.6.32.9-PERF
BUILD 17397
I really want another crack at getting streakdroid, but the phone just isn't budging. Tempted to flash/install another rom but worried as heck that this same incident is going to come up. (the flashing lights started after i updated the AMSS and DSP last night--my first attempt at installing streakdroid 2.3).
Installing the stock rom via the update.pkg file will overwrite the amss and dsp1. That's the biggest difference to the end user on update.pkg vs update.zip. It's the actual recommended way to install a baseband. There are several firmwares, besides amss and dsp1, that get installed with a pkg.
Now that you have MultiRecoveryFlasher on your pc, installed StreakMod (custom recovery) should be a breeze for you. The only thing to watch out for is since you have a stock rom now, the first time it boots it will rewrite the recovery back to stock. Here is how to get around this:
Download the custom rom of your choice.
Place the zip file on the root of your sd card.
Get your phone back in fastboot mode
Using MultiRecoveryFlasher, flash StreakMod
As soon as the screen goes black for the reboot, hold the volume +/- keys.
Choose option 2 again, this time it should take you into StreakMod
Choose flash from update.zip
On the next screen, choose search for zip file (similar wording)
Choose the custom rom from earlier
Let it do it's thing.
Choose reboot system now
Again, as soon as the screen goes dark, hold Volume +/-
Now choose option 1 - Factory Rest
Let it do it's thing.
It should boot up now and your custom recovery will stay intact.
Let me give you some friendly advice: Streakdroid 2.3 is too much of a work in progress. Install one of the other Streakdroids, Longhorn, Simple Streak, or even my Streakin' 354. Play with it for a while and learn a little more before jumping into one that may not be as stable.
As far as rooting a stock rom, the preferred method is via superuser.zip. I'm not at home, so I don't have the file to upload for you, but its on these Dell Streak forums somewhere. You have to have a custom recovery to use it though. The custom roms are all rooted already.
Thank you for everything
No problem. Did you get it working?
Sent from my Dell Streak using xda premium
Absolutely and I couldn't have done it without you. If you had written out just one of the x number of tutorials out there, I don't think anyone would have run into the problems I did at first.
Streakdroid 191 runs like a charm---snappy and more responsive than stock ever was.
Glad to hear it...I was lost when I first started too. Someone helped me out and I just like to pay it forward. It's what makes this forum my favorite.
lordmorphous said:
Glad to hear it...I was lost when I first started too. Someone helped me out and I just like to pay it forward. It's what makes this forum my favorite.
Click to expand...
Click to collapse
Hi guys.. Hi Mr Lordmorphous.. im a super noobie in dell streak 5.. i got my dell streak a month ago.. today my phone doesnt work.. im stuck on Dell logo when i am going to switch it to on.. i really dont know where to start and how to type the codes like you are talking about like .pkg ing. etc. .. when im pressing the factory reset nothing happens.. i also tried to click software upgrade via update.pkg on SD card and nothing happens .. i clicked also the screen calibration it says *successful calibration done*.. im totally lost.. can u help me how to start from beginning (like for super noobie like me)? also the codes that im going to type in pc.. thanks in advance!
dwadetiu said:
Hi guys.. Hi Mr Lordmorphous.. im a super noobie in dell streak 5.. i got my dell streak a month ago.. today my phone doesnt work.. im stuck on Dell logo when i am going to switch it to on.. i really dont know where to start and how to type the codes like you are talking about like .pkg ing. etc. .. when im pressing the factory reset nothing happens.. i also tried to click software upgrade via update.pkg on SD card and nothing happens .. i clicked also the screen calibration it says *successful calibration done*.. im totally lost.. can u help me how to start from beginning (like for super noobie like me)? also the codes that im going to type in pc.. thanks in advance!
Click to expand...
Click to collapse
RTFM
http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak
Hi again guys.. and mr lordmorphous!
im following what you told him (aaivazi)..
I'm going to try to start from scratch here. I am also assuming you are using a Windows PC.
Download the drivers from Dell. Here's the link:
http://support.euro.dell.com/support...&fileid=433681
Install them and reboot your pc.
Download MultiRecoveryFlasher from here:
http://forum.xda-developers.com/show....php?t=1000455
Extract it to somewhere on you pc where you can find it.
Now this hasn't been updated to include 360's recovery, but that's ok. We don't have to run the utility. It's the support files that are included that we are going to use.
Download the recovery.img for 360 (which I think you have already done)
Put the recovery.img in the root folder of MultiRecoveryFlasher. There should be other files in there such as fastboot.exe, adb.exe, etc.
Power down your phone and restart it in fastboot mode (hold down camera and power button together until you get a white screen. When fastboot appears in upper right, select it and plug your phone into your pc)
Verify the phone displays fastboot ready
Open a command prompt on your PC
Type in the following command: fastboot.exe -i 0x413c flash recovery recovery.img
(im already here but this is what the command prompt says:
'fastboot.exe' is not recognized as an internal or external command, operable program or batch file.)
what should i do ?
Streak4ever said:
RTFM
http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak
Click to expand...
Click to collapse
hi streak4ever thanks for reply.. what does RTFM means? thanks
Hi Guys,
I am a noob to xda so please bear with me...
Hoping someone can help me out here.. I will try and explain in as much detail as possible and provide you with as much Info from my phone as I can.
Firstly my phones details
Motorola Atrix 4g (UK version) Second phone as busted the last one. Bought outright as a retail sale.
Orange UK
System Version: 45.31.0.MB860.Retail.en.GB
Android Version: 2.3.4 (After UK released update)
Baseband Version: N_01.100.00R
Webtop Version: WT-1.2.0.133_38
Kernel Version: 2.66.32.9 [email protected]#2
Ok so, decided to root my phone. To do so I used petesMotorolaRootTools_V1.07 found on the website psouza4.com/bionic/
This worked fine and an app installed from the App Market confirmed that the phone was Rooted and had Superuser permissions.
Next I downloaded ClockWorkMod Rom Manager from the Market Inc Premium, SetCPU, Rom Toolbox & Titanium Backup Free. I had a quick look at these apps once downloaded but didnt really do a lot,
However, when Rom Manager opened it promted me to Flash ClockWorkMod Recovery, Which I did and then selected Back up current Rom. I also did this, (bear with me it gets a little vague here as to what I remember seeing)
Now I'm sure it said something like Nandroid Backup, which I selected. It proceeded to say something along the lines of, Backing up or phone will now reboot??
Anyhow, what ever it said, it started to reboot. The Motorola Red Circle logo came up but then at the top it said reboot failed and something ilse that didnt make sense then froze. I pulled the battery and rebooted. Seemed to work fine. Maybe a touch laggy but nothing to bad.
Next did my research into what ROM I'm likely to want to try. Found a few but seemed from what I have read on various forums that they dont work well for uk phones. Then decided perhaps then flashing should be left alone and went back to PetesMotorolaTools and unrooted. before I unrooted however i removed all apps that required root access first. Possibly a mistake?
I noticed that a few preinstalled apps werent working, nothing important or anything I use but there icons were like Blue settings icons all the same.
Did a factory reset through the handset also, in an attempt to return to factory settings.. not much changed really. Also tried to update software though the Motorola website but it said I was all up to date.
I thought maybe that something went wrong so I rooted again. This time the unroot failed. I then dowloaded all the rooted apps that I had before and then unrooted. This worked. Not sure if coincedence or not but it worked and when unrooting it said unfreezing apps about 6 times, before the complete message. Then uninstalled the root apps again.
Most, not all but most of those preinstalled apps were then working ok.
I read a little bit more bout Roms and decided to have another bash. Found and downloaded a few to comp. Then I place an SD card into phone and Flashed it. then tranferred a copy to its root.
Rooted the phone in the same way as before. Downloaded all the apps again opened CWM RM, Flashed CWM Recovery again as was unsure that the time I did it before would work. Then selected back up Current ROM. Without any message this time the phone started to reboot.
It came up with the recovery screen (Android man and !) From what I have read the next step is to tap the bottom right of the screen to bring up the menu.
This did not work nor did anything else happen. After waiting about 25mins with nothing more happening I pulled the batt again.
Decided I'd boot into recovery mode manually and see if the bottom right of screen would work that way. turned off then held On and down Vol. Fastboot showed at top, Scrolled and selected Android recovery. Same Android Man and ! came up, tried tapping the bottom right of screen again.... It didnt work.
Read more on the forums where someone said that pushing up and down on the Vol buttons works. Tried this and hey presto.. a new menu appears. Shown as follows.
Android system recovery <3e>
Android system recovery utility
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
No back up options so rebooted....
Anyway thought I'd try a few times to use CWM RM to flash a rom to device. Each time it took me throught this same process.
Eventually I though what the hec just try and flash it...
So I selected the apply update from sdcard option.
Then selected the ROM I saved to SD Card.
Then the following text appears on screen in yellow.
--Install /sdcard...
finding update package...
Openeing update package...
Verifying update package...
E:signature verification failed
Installation abborted
I tried this a few times to no avail. even tried downloading the roms from CWM RM with no change.
Read some more on the forums and somewhere read to rename the ROM update.zip
Did this and tried again.... No Joy!!!
Selected Fix permissions in an attempt to clean up and thats as far as I have got...
I'm at the end of my tether and dont know what to do...
Please, please, please someone help me get to the bottom of my dilemma..
Thanks for reading and any help in advance.
Just a little more info to help diagnose
CWM RM Details
Rom Manager Premium v4.8.1.3
Current Recovery: ClockworkMod 5.0.2.0
Latest Recover;ClockworkMod 5.0.2.0
Thanks again peoples for taking the time to at least read this..
No where in there did I see "I unlocked my bootloader"
That's fine that you're rooted, but to use CWM Recovery, install ROMs, make Nandroid Backups, etc. you need to unlock your bootloader first! See the international part of the Pudding thread (since your in UK) in the dev section.
Sent from my CM7 Atrix 4G
Ah Hah! You are correct at no point did I unlock my Booty, Thank you I shall give that a go and report back...
Ok so, I have trawled the forum and many others this avo on my research quest to unlock the bootloader as advised above but have been unsucessful so far.
I used the Pudding thread as you said.
when downloading the files advised I noticed that some were downloading as unrecognised files. I still proceeded to follow instructions as written.
Some of them like the RSD Lite I managed to unzip and extract with a programme I have however the next one needed said it was Undefined File type.
Anyway I deleted those files and tried following the other method listed underneath the driver via the link at "Guide for beginners provided by..."
This was unsucessfull as the "fastboot oem unlock" command was not recognised.
Pulled the batt and rebooted into normal mode and I'm back at SQ1
Bit stuck if anyone has any ideas..
Ok, here goes...
1) Make sure you have the drivers installed on your computer. (Available in Pudding Thread)
2) Go to pudding thread, and grab the Unlock Only IHOP sbf file (assuming your not on AT&T).
http://forum.xda-developers.com/showthread.php?t=1136261
"Unlock:
Unlocker only SBFs - These small 1mb SBF files will get your phone ready to fasboot oem unlock. They are the files most people should use.
ATT ONLY - Unlocker for 1.8.3 and 4.5.91 ATT firmwares
Orange/Bell/Telestra/Latin America/International users ONLY - Download IHOP"
3) Download & install RSD Lite. (Available in Pudding Thread)
4) Put phone in RSD Protocol Mode.
a) Power off phone
b) Upon Powering ON, hold Power Button + Volume UP
5) Connect Phone to computer via USB
6) unzip the IHOP sbf file to root of your C:\, open RSD Lite program, and drag sbf file onto File Name Box. Make sure RSD Lite sees your device connected to it, and then flash away.
7) After the sbf has flashed (hopefully without any errors), reboot your phone into fastboot mode (Power Button + Volume Down; when you see fastboot, press volume up to enter fastboot mode).
8) Re-connect phone to computer if you disconnected it.
9) In the folder where your fastboot files are located (if you don't have fastboot files, go download them from sticky in General Section), press Shift + Right Click, select Open Command Window Here.
10) With phone in fastboot mode, connected to PC and command window open in fastboot file location, type:
fastboot oem unlock
*This will give you your device #
Then type:
fastboot oem unlock [insert your # here]
10) Bootloader should unlock, then type fastboot reboot to reboot the phone. Should say Unlocked on boot screen now, if all went well.
11) Install Rom Racer's Recovery or Rom Manager, and you're good to go.
Think that about cover it... if you have any problems, give details of what is happening and at what step. Also, check the Pudding thread for possible solutions, as most problems have already been solved there.
Thank you for your explanation... I will give it a go when I get back from work tomorrow...
I appreciate you taking the time to help..
Sent from my MB860 using XDA App
Dcskeete said:
Thank you for your explanation... I will give it a go when I get back from work tomorrow...
I appreciate you taking the time to help..
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
You should definatly also install busybox
Swiftks said:
Ok, here goes...
1) Make sure you have the drivers installed on your computer. (Available in Pudding Thread)
2) Go to pudding thread, and grab the Unlock Only IHOP sbf file (assuming your not on AT&T).
http://forum.xda-developers.com/showthread.php?t=1136261
"Unlock:
Unlocker only SBFs - These small 1mb SBF files will get your phone ready to fasboot oem unlock. They are the files most people should use.
ATT ONLY - Unlocker for 1.8.3 and 4.5.91 ATT firmwares
Orange/Bell/Telestra/Latin America/International users ONLY - Download IHOP"
3) Download & install RSD Lite. (Available in Pudding Thread)
4) Put phone in RSD Protocol Mode.
a) Power off phone
b) Upon Powering ON, hold Power Button + Volume UP
5) Connect Phone to computer via USB
6) unzip the IHOP sbf file to root of your C:\, open RSD Lite program, and drag sbf file onto File Name Box. Make sure RSD Lite sees your device connected to it, and then flash away.
7) After the sbf has flashed (hopefully without any errors), reboot your phone into fastboot mode (Power Button + Volume Down; when you see fastboot, press volume up to enter fastboot mode).
8) Re-connect phone to computer if you disconnected it.
9) In the folder where your fastboot files are located (if you don't have fastboot files, go download them from sticky in General Section), press Shift + Right Click, select Open Command Window Here.
10) With phone in fastboot mode, connected to PC and command window open in fastboot file location, type:
fastboot oem unlock
*This will give you your device #
Then type:
fastboot oem unlock [insert your # here]
10) Bootloader should unlock, then type fastboot reboot to reboot the phone. Should say Unlocked on boot screen now, if all went well.
11) Install Rom Racer's Recovery or Rom Manager, and you're good to go.
Think that about cover it... if you have any problems, give details of what is happening and at what step. Also, check the Pudding thread for possible solutions, as most problems have already been solved there.
Click to expand...
Click to collapse
A BIG THANKS!!!
Thanks so much for the advice and instructions... Unlocked beautifully... Now to find the ideal ROM....
Dont suppose there are any suggestions for International (UK) Atrix users??
Really appriciate the help..
Regards
Danny
I would recommend that you flashed TWRP 2.0 through CWM direct link. It lets you have touch screen in recovery; much easier! Then if you like CM7 you could try this or if you like the MIUI style (like me!) you would want to try this! It hasn't in-game audio yet but it's much cooler in my opinion. But Neutrino CM7 is really great!
Im not sure, maybe someone else can confirm. You should be using moto-fastboot to unlock & not regular fastboot, right?
Sent from my MB860 using xda premium
draken_1337 said:
I would recommend that you flashed TWRP 2.0 through CWM direct link. It lets you have touch screen in recovery; much easier! Then if you like CM7 you could try this or if you like the MIUI style (like me!) you would want to try this! It hasn't in-game audio yet but it's much cooler in my opinion. But Neutrino CM7 is really great!
Click to expand...
Click to collapse
People have had problems with TWRP.............stick with Romracers CWM, it's tried and trusted. If the touch screen in CWM gets you off, so be it, but I'd rather have a recovery that works with all ROM's, and not just some.
Hello, I've a problem with my htc U Ultra (ocedugl). In fact, I upgraded supersu and when the phone was supposed to restart, I was stuck at the htc logo. I then had a backup of the boot and the system in reserve on my SD card, but when I wanted to restore them, I had the error 255. Only during the restoration of the system.
I do not know what to do, this phone is a real mystery to me. I have an internship tomorrow, not very practical suddenly. :/
The most problematic in all this is that twrp asks me for a password to decrypt the data at startup and I have the impression that I have only worsened the case. If anyone could help me quickly enough please.
PS: Me who I usually do alone, I must admit that I dry.
PS 2: I installed root switch for snapchat just before too, I do not know if that affects.
SofianeLasri said:
Hello, I've a problem with my htc U Ultra (ocedugl). In fact, I upgraded supersu and when the phone was supposed to restart, I was stuck at the htc logo. I then had a backup of the boot and the system in reserve on my SD card, but when I wanted to restore them, I had the error 255. Only during the restoration of the system.
I do not know what to do, this phone is a real mystery to me. I have an internship tomorrow, not very practical suddenly. :/
The most problematic in all this is that twrp asks me for a password to decrypt the data at startup and I have the impression that I have only worsened the case. If anyone could help me quickly enough please.
PS: Me who I usually do alone, I must admit that I dry.
PS 2: I installed root switch for snapchat just before too, I do not know if that affects.
Click to expand...
Click to collapse
Try TWRP 3.2.1-1
minhnewpro said:
Try TWRP 3.2.1-1
Click to expand...
Click to collapse
Ho to install without an accessible system?
SofianeLasri said:
Ho to install without an accessible system?
Click to expand...
Click to collapse
Turn off your phone. Press Power and volume down at the same time to boot in to download mode. connect to PC and flash TWRP
Install via ADB
Open the folder where your TWRP Recovery .img file is saved.
Then open a CMD window inside that folder. To do that, Shift + Right click on any empty white space inside the folder and then select Open command window here.
Connect your Android device to the PC. Type the following into the command window to boot your device into bootloader/fastboot mode:
Once your device boots into download mode, type this into the command line.
fastboot flash recovery twrp-3.2.1-1.img
Once TWRP is successfully flashed on your device, you can use TWRP now
minhnewpro said:
Turn off your phone. Press Power and volume down at the same time to boot in to download mode. connect to PC and flash TWRP
Install via ADB
Open the folder where your TWRP Recovery .img file is saved.
Then open a CMD window inside that folder. To do that, Shift + Right click on any empty white space inside the folder and then select Open command window here.
Connect your Android device to the PC. Type the following into the command window to boot your device into bootloader/fastboot mode:
Once your device boots into download mode, type this into the command line.
fastboot flash recovery twrp-3.2.1-1.img
Once TWRP is successfully flashed on your device, you can use TWRP now
Click to expand...
Click to collapse
thanks, i have now the twrp-3.2.1-1-oce but it still asks me for a password at startup and my restore still fails with error 255.
SofianeLasri said:
thanks, i have now the twrp-3.2.1-1-oce but it still asks me for a password at startup and my restore still fails with error 255.
Click to expand...
Click to collapse
Maybe you need flash a new rom. Viper, Ledroid,...
minhnewpro said:
Maybe you need flash a new rom. Viper, Ledroid,...
Click to expand...
Click to collapse
Okay, I was saying that too. I try your custom rom then.
PS : Ah, I just saw that the post requests the latest version of the system, except that I do not have access ...
unmout data in internal storage and retore
SofianeLasri said:
Okay, I was saying that too. I try your custom rom then.
PS : Ah, I just saw that the post requests the latest version of the system, except that I do not have access ...
Click to expand...
Click to collapse
You can try flash rom without have same firmware. I'm using Oreo on Nougat firmware
Oh no, I just understand! My SD card seems locked in read only. I really have a bad day me! Between my hard drive doing anything and my phone ... xD
SofianeLasri said:
Oh no, I just understand! My SD card seems locked in read only. I really have a bad day me! Between my hard drive doing anything and my phone ... xD
Click to expand...
Click to collapse
Oh it's good, it was really my card sd the problem.
SofianeLasri said:
Oh no, I just understand! My SD card seems locked in read only. I really have a bad day me! Between my hard drive doing anything and my phone ... xD
Click to expand...
Click to collapse
i don't know what extractly happened with your phone. You can access your storage by connect to PC when your phone in TWRP Recovery. Backup your personal data. Choose wipe => format data => type "yes" => copy Rom into your internal storage or SD Card and flash
minhnewpro said:
i don't know what extractly happened with your phone. You can access your storage by connect to PC when your phone in TWRP Recovery. Backup your personal data. Choose wipe => format data => type "yes" => copy Rom into your internal storage or SD Card and flash
Click to expand...
Click to collapse
No, in fact my sd card is dead. I can't write anymore on. I have save mys backup and restore my system. Thanks for the help!
HTC u ultra Oreo messed up my phone and now I need help.
My story:
Bought a HTC U Ultra European.
I was kind of satisfied with it. The device didn't really live up to my expectations. But when it was upgraded to Oreo the screen start to flash when opening apps and Bluetooth sound went bad. It looks like the app opens twice. After a while it went even worse with the flashing.
Anyways I unlocked the bootloader and flashed TWRP 3.2. That process went fine then I wanted to flash leedroid to test something else (yes I saved a recovery file).
The result is now my device is working but I'm unable to flash twrp again. Since Oreo still sucks to u ultra and I want to downgrade to nougat since it works.
My adb (Linux) detects my device but when I start my HTC in download mode I'm unable to flash to since my PC says:
<waiting for device>
When I try to start it in recovery mode it sticks in a reboot loop.
And BTW I can't restore factory settings.
So if anyone can give me any answers it would be great.
ibringthemadness said:
My story:
Bought a HTC U Ultra European.
I was kind of satisfied with it. The device didn't really live up to my expectations. But when it was upgraded to Oreo the screen start to flash when opening apps and Bluetooth sound went bad. It looks like the app opens twice. After a while it went even worse with the flashing.
Anyways I unlocked the bootloader and flashed TWRP 3.2. That process went fine then I wanted to flash leedroid to test something else (yes I saved a recovery file).
The result is now my device is working but I'm unable to flash twrp again. Since Oreo still sucks to u ultra and I want to downgrade to nougat since it works.
My adb (Linux) detects my device but when I start my HTC in download mode I'm unable to flash to since my PC says:
<waiting for device>
When I try to start it in recovery mode it sticks in a reboot loop.
And BTW I can't restore factory settings.
So if anyone can give me any answers it would be great.
Click to expand...
Click to collapse
Try reinstall driver, buy or borrow an other usb-c cable.
minhnewpro said:
Try reinstall driver, buy or borrow an other usb-c cable.
Click to expand...
Click to collapse
I already installed drivers and tried other cables. Did the procedure again bit with no results.
I think the big problem actually is that since the phone can't boot into recovery mode it get messed up.
I try to do a hard reset but every time I either get stuck in a bootloop or the phone boots into regular mode. So I literally can't do anything to fix this problem as far as I know.
Getting a little bit of frustrated over here.
Why you need reflash TWRP after used Leedroid's rom?
minhnewpro said:
Why you need reflash TWRP after used Leedroid's rom?
Click to expand...
Click to collapse
Because I can't boot to recovery mode. Either I get stuck in a boot loop or the device boots just like I rebooted it. So I can't get to twrp and I can't flash anything. I can't hard reset either. All I can do is reboot, enter bootloader and enter download mode.
So I guess I'm stuck with Oreo that's a mess on my device.
ibringthemadness said:
Because I can't boot to recovery mode. Either I get stuck in a boot loop or the device boots just like I rebooted it. So I can't get to twrp and I can't flash anything. I can't hard reset either. All I can do is reboot, enter bootloader and enter download mode.
So I guess I'm stuck with Oreo that's a mess on my device.
Click to expand...
Click to collapse
Try boot into Download mode and Flash new TWRP https://dl.twrp.me/oce/twrp-3.2.2-0-oce.img.html
If your PC can not recognize your phone, try another PC.
minhnewpro said:
Try boot into Download mode and Flash new TWRP https://dl.twrp.me/oce/twrp-3.2.2-0-oce.img.html
If your PC can not recognize your phone, try another PC.
Click to expand...
Click to collapse
Already tried to flash twrp-3.2.2...
Same result. None.
My PC finds my phone with no problem until I boot into download mode then it doesn't find it anymore.
Still another PC?