Database Users

Vista problems with adb

cant seem to get this adb going on vista...am trying to get to root but adb just isnt happening, have installed all the correct drivers, the phone is in developer mode but in windows vista when i open command prompt and check adb theres no devices attached? I have checked in device manager and under usb root hub the phone isnt there, it is under portable devices as android phone and trying to update the usb drivers on there doesnt install saying that the current drivers are up to date. I can get into fastboot and the phone is picked up with the usb drivers from the sdk package.
Can anyone help on this? I have tried method 2 of getting to root http://android-dls.com/wiki/index.php?title=Magic_Rooting but the phone just hangs at the vodafone screen (i have to sut the phone down from the fastboot menu as adb doesnt work).
Any help would be appreciated, there was a small update on friday to the phone have they fixed everything or is it just an issue with vista?
Was trying to follow the instructions found here to flash the spl but I'm not sure what it means, I'm sure I'm nto just being thick....
http://forum.xda-developers.com/showthread.php?t=529019
How to flash :
1. Download the appropriate recovery here, and rename it to update.zip.
2. Copy update.zip to the root of your SD-card
3. Switch the Magic to fastboot mode
4. $fastboot boot <moddedrecovery.img>
5. Apply the update
point 1 takes me to RAv1.0G.img, do i just force it to name as a zip file from file extension or physically zip it?
part 2 is fine if I understand part 1
part 3 I'm ok on
part 4, I'm taking it this is the spl file however its a zip package, do i unzip it and place both the hboot.img and the meta folder into the folder i am using for fastboot and adb? the instructions arent very cear for doing this, can anyone correct me if above is wrong?
thanks.

fixed now skipped a whole load of steps and its working lol

Can't flash HERCIMG.zip

Im using the fastboot method to flash the original sprint RUU in zip format.
I used:
-fastboot oem rebootRUU
-fastboot flash zip HERCIMG.zip (or HERCIMG, HERCIMG.ZIP, hercimg.zip etc etc)
But i keep getting "Error: cannot load "HERCIMG.zip" or whatever i type.
Stuff i tried:
*Unlocked bootloader to s-off - still wont let me flash and zip files from the bootloader. I'm 100% ive done this before several months ago, and i even used the same HERCIMG file that i left in the /sdcard main directory.
*Delete the old HERCIMG and download a new one from the dev section of the hero forums.
*Manually placed in root of sdcard by mounting the sdcard on my computer.
*Used adb to push the HERCIMG file to the root directory of sdcard
Anyone can tell me whats going on?
Also right now i have CM7, bootloader 1.47 unlocked.
Maybe i have a bad version of fastboot.exe? I copied it from /tools/ folder of android sdk and placed it in /platform-tools/ since it needed adbwinapi.dll which is located in that folder along with adb.exe
Thanks for any help

Ok guys. I have no idea whats up, but eventually i was able to fix by loading the unlocked bootloader and running the RUU.exe from windows. Still wasnt able to flash the HERCIMG.

I had a huge issue with HERCIMG not working for me. I noticed that I had HERCIMG.zip and changed it to HERCIMG.ZIP - make sure it is all caps on your sdcard, how it gets there does not matter, I copied it in windows. Next, you must boot into bootloader - there are many commands, but it has to be a white screen on your phone and text will scroll...at some point, it will ask you what you want to do with the file...This is all done on the phone. You must have s-off too. If you are not using the ENG hboot, I dont think fastboot will work, btw (and the eng hboot is 1.46)

Yup. Flash darchs eng-spl and you should be good to go. Oh and you have to take into account your radio/baseband ver. If its .29 then you have to flash it a certain way or downgrade your radio then flash it then hercimg your current radio again.
Locked & Loaded

Cool thanks for the help. Where can I get the eng-spl so i can flash from bootloader directly?

Well the last time I checked you have to flash it from recovery. If you search the hero dev section for it I'm sure you wil find it. Also I'd highly recommend Flashing it with Ra1.6/1.7 or Cwm2.5 and remember to check your baseband/radio version. If you can't find it let me know and I'll post it after church. But you should read as much as you can about the mod to get a better understanding of the risks and benfits of the mod.
Locked & Loaded

Don't forget that your SDcard has to be formatted to Fat32 so the bootloader can find it.

When I use/have used any HERCIMG.zip, I have never done it through fastboot, I have always done it by using the H-Boot screen. The HERCIMG.zip cannot say "HERCIMG.zip.zip (so don't name the zip file with a .zip in the name- check the details of the file to make sure).
If you are in the bootloader, press the volume button down to get into H-boot from the Fastboot or restart the phone (press volume and start button at the same time).
If you used Regaws to become S-off, then I know the H-boot method will work fine. As far as using fastboot commands, you would need to flash Darch's Eng Spl mod that changes the bootloader to 1.46.2. There is a thread by jasonmaloney that has to do with flashing an RUU from fastboot without being S-Off. This needs to be done from Windows, that's why jason includes fastboot.exe along with the RUU. Is the RUU you are using all images, or are there other files as well (binary types)?
Good Luck

unable to load from fastboot

I am trying to flash the kernal for 5.1.1 after a restore to stock and get my wifi going again. I placed the kernal zip in the adb folder
where I have the adb and fastboot exe files. I opened the command prompt in that folder after I unziped the kernal to get the img.
I can fastboot reboot bootloader, and fastboot devices, which shows the s.n for the phone. When I used the, fastboot flash boot v4tk-kernel-uber-alias.img, command I get an "unable to load"? Whats going on and how do I fix this. Same thing happened when I tried to flash non-hlos.bin. Help please....I am using windows 10.

Garyalp said:
I am trying to flash the kernal for 5.1.1 after a restore to stock and get my wifi going again. I placed the kernal zip in the adb folder
where I have the adb and fastboot exe files. I opened the command prompt in that folder after I unziped the kernal to get the img.
I can fastboot reboot bootloader, and fastboot devices, which shows the s.n for the phone. When I used the, fastboot flash boot v4tk-kernel-uber-alias.img, command I get an "unable to load"? Whats going on and how do I fix this. Same thing happened when I tried to flash non-hlos.bin. Help please....I am using windows 10.
Click to expand...
Click to collapse
Somebody? Im sure Im not the only one with this problem.....

Flashing boot and modem are pretty straight forward. Not sure what your issue is.

Garyalp said:
I am trying to flash the kernal for 5.1.1 after a restore to stock and get my wifi going again. I placed the kernal zip in the adb folder
where I have the adb and fastboot exe files. I opened the command prompt in that folder after I unziped the kernal to get the img.
I can fastboot reboot bootloader, and fastboot devices, which shows the s.n for the phone. When I used the, fastboot flash boot v4tk-kernel-uber-alias.img, command I get an "unable to load"? Whats going on and how do I fix this. Same thing happened when I tried to flash non-hlos.bin. Help please....I am using windows 10.
Click to expand...
Click to collapse
The only things I can think of that would cause that would be either the file is not in that directory or it's not spelled correctly. For the modem are you typing non-hlos or NON-HLOS? It should be all caps. As for the boot image, try renaming it. That's about all I can think of.
Sent from my XT1575 using XDA-Developers mobile app

''Could not do normal boot'' error and odin doesnt recognise my phone! Please help :(

(SOLVED) Hello, today i decided to root my phone( Galaxy Grand Prime SM-G530F)using odin but i guess i used the wrong file. Odin said ''Restart'' and nothing happened, then i unplugged my phone. I wish I hadnt done this
When i try to turn my phone on, I only can see download mode and i guess it is called ''bootloop''. It says ''could not do normal boot''. I couldnt solve this problem using Odin because Odin doesnt see/recognise/find my phone. I checked the USB port drivers and my wire but i still cant fix the problem. Please help me, I am so desperate and cant afford a new phone :crying:

Does your Phone have fastboot and is your phone recognized by fastboot?
If yes Download your Firmware from sammobile.com (Registration needed) and unpack it
At this point I want to state, that I'm not Responible for any Hard- or Software-Damage. I'm just trying to help, because I think, that it can't get any worse
Windows:
Open up cmd as Administrator
Go into the Folder where fastboot is installed
Copy all the extracted .img files into the fastboot-folder
Run the following commands:
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img
fastboot.exe flash data data.img
If there are any other img files than these four, or if one of those four didn't exist, you are free to ask
Linux:
Open up terminal as root (or use sudo before every command)
Go into the folder, where all the img files are stored
Run the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash data data.img
If there are any other img files than these four, or if one of those four didn't exist, you are free to ask
Sent from my SM-G350 using XDA-Developers mobile app

TimSchumi said:
Does your Phone have fastboot and is your phone recognized by fastboot?
If yes Download your Firmware from sammobile.com (Registration needed) and unpack it
At this point I want to state, that I'm not Responible for any Hard- or Software-Damage. I'm just trying to help, because I think, that it can't get any worse
Windows:
Open up cmd as Administrator
Go into the Folder where fastboot is installed
Copy all the extracted .img files into the fastboot-folder
Run the following commands:
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img
fastboot.exe flash data data.img
If there are any other img files than these four, or if one of those four didn't exist, you are free to ask
Linux:
Open up terminal as root (or use sudo before every command)
Go into the folder, where all the img files are stored
Run the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash data data.img
If there are any other img files than these four, or if one of those four didn't exist, you are free to ask
Sent from my SM-G350 using XDA-Developers mobile app
Click to expand...
Click to collapse
Wot? Samsung phones don't have fastboot lol
Anyway try to remove the battery and enter ODIN mode normally, this should do it.

Oh, crap, i forgot
Sent from my SM-G350 using XDA-Developers mobile app

fabiossilva21 said:
Wot? Samsung phones don't have fastboot lol
Anyway try to remove the battery and enter ODIN mode normally, this should do it.
Click to expand...
Click to collapse
I tried to remove the battery but it didnt work

tunasdf said:
I tried to remove the battery but it didnt work
Click to expand...
Click to collapse
OMG IT WORKED AFTER TRYİNG THOUSAND TİMES thank you so much

tunasdf said:
OMG IT WORKED AFTER TRYİNG THOUSAND TİMES thank you so much
Click to expand...
Click to collapse
No problem! Glad you managed to fix it! Now remember to flash the right file

HowTo "Unbrick" U-Ultra

Hi all,
this may be helpful for all that have similar problems as I had.
After experiencing with custom ROMs, I wasn't able to boot into System and also not into Recovery anymore (ended in a bootloop).
Because I tried to flash back to a Stock ROM via RUU I also relocked my bootloader and unlocking wasn't possible anymore because the unlock option was not active and not accessible without a system.
Unfortunately there's only the Nougat RUU available and I previously had Oreo installed.
As I also have S-ON, it's not possible to flash back to the Nougat RUU.
I was only able to access the phone in bootloader mode and with fastboot.
Prerequisites:
You should be able to access your phone via fastboot, so the correct USB drivers should be installed on your PC
How did I solve this:
I downloaded the following RUU.exe from US HTC website - I'm not able to post links, but you can find it via Google: HTC U Ultra Firmware Update
Start it and go to "C:\Users\Username\AppData\Local\Temp" (on Windows 10), there you can find a temporary folder of the RUU.exe, for example {50F2F878-636A-496F-A7CB-544C067E0C4B}
You can find some files like adb.exe, htc_fastboot.exe, rom.zip, ...
Copy the folder to any location you want and close the RUU application
I then downloaded the Oreo OTA zip for my phone from androidfilehost (Thank you minhnewpro ) - see: https://forum.xda-developers.com/u-ultra/development/ruu-collection-htc-ultra-nougat-t3830999
Unzip the OTA and copy the firmware.zip to the previously copied folder from RUU (here: {50F2F878-636A-496F-A7CB-544C067E0C4B})
Start the phone into Bootloader or Download Mode and connect it to the PC
Open the commandline on the PC and cd to the copied folder from RUU
Enter the following Commands:
htc_fastboot oem rebootRUU​htc_fastboot flash zip firmware.zip​htc_fastboot flash zip firmware.zip​
htc_fastboot flash zip firmware.zip needs to be done twice, in the first run I got the following error: FAILED (remote: 90 hboot pre-update! please flush image again immediately )
The second time it went through without any error.
Now my phone works again and has the Oreo Stock ROM installed!
I hope this method also works for other phones and not just mine
Greetings

Thank you.
This method works with my HTC U Ultra dual sim.
Thank you very much.

oesiblah said:
Hi all,
this may be helpful for all that have similar problems as I had.
After experiencing with custom ROMs, I wasn't able to boot into System and also not into Recovery anymore (ended in a bootloop).
Because I tried to flash back to a Stock ROM via RUU I also relocked my bootloader and unlocking wasn't possible anymore because the unlock option was not active and not accessible without a system.
Unfortunately there's only the Nougat RUU available and I previously had Oreo installed.
As I also have S-ON, it's not possible to flash back to the Nougat RUU.
I was only able to access the phone in bootloader mode and with fastboot.
Prerequisites:
You should be able to access your phone via fastboot, so the correct USB drivers should be installed on your PC
How did I solve this:
I downloaded the following RUU.exe from US HTC website - I'm not able to post links, but you can find it via Google: HTC U Ultra Firmware Update
Start it and go to "C:\Users\Username\AppData\Local\Temp" (on Windows 10), there you can find a temporary folder of the RUU.exe, for example {50F2F878-636A-496F-A7CB-544C067E0C4B}
You can find some files like adb.exe, htc_fastboot.exe, rom.zip, ...
Copy the folder to any location you want and close the RUU application
I then downloaded the Oreo OTA zip for my phone from androidfilehost (Thank you minhnewpro ) - see: https://forum.xda-developers.com/u-ultra/development/ruu-collection-htc-ultra-nougat-t3830999
Unzip the OTA and copy the firmware.zip to the previously copied folder from RUU (here: {50F2F878-636A-496F-A7CB-544C067E0C4B})
Start the phone into Bootloader or Download Mode and connect it to the PC
Open the commandline on the PC and cd to the copied folder from RUU
Enter the following Commands:
htc_fastboot oem rebootRUU​htc_fastboot flash zip firmware.zip​htc_fastboot flash zip firmware.zip​
htc_fastboot flash zip firmware.zip needs to be done twice, in the first run I got the following error: FAILED (remote: 90 hboot pre-update! please flush image again immediately )
The second time it went through without any error.
Now my phone works again and has the Oreo Stock ROM installed!
I hope this method also works for other phones and not just mine
Greetings
Click to expand...
Click to collapse
Hello, I tried this method, but it can't flash the firmware, "FAILED (remote: cannot flash this partition in s-on state)" . Bootloader is the only way I can enter, Download mode or Recovery mode doesn't work("Can't enter download mode, use volume + or - to go back"). Any other methods available?

BOOT problem issue
hard disk recovery
"jtag"