Database Develop

[Q] [REQUEST] System.img!

So what I would like for someone to help me with is to get the system.img for the first somehow on my the computer so i can flash it via ADB-Fastboot and get my phone to at least power up to the homescreen; this is because just a few days ago i was testing out some 'things' though they didn't work and decided to wipe the phone. The problem is that I erased EVERYTHING on the phone including system, etc. So now because the first doesn't have an sd card slot I cannot get a way to mount a rom and flash a new system.
All i ask for is a system.img or any tutorial that would work, (I've literally spent 2 nights looking for something but they aren't compatible with the first) using the RUU is out of the question because it's apparently encrypted and won't detect my phone since it just hangs on the facebook logo, also the system dumps on the forum that I've seen don't contain the system.img file. Thank you in advance for your help and troubles!
(note that I do not have a way to access ubuntu or any linux computer right now because of various reasons, what i do have is a spare first!)

What's stopping you from flashing a ROM from recovery? ADB push the ROM file into /sdcard from recovery.
The most common fix to get RUU working is to relock your bootloader. You can run RUU from fastboot.

killall-q said:
What's stopping you from flashing a ROM from recovery? ADB push the ROM file into /sdcard from recovery.
The most common fix to get RUU working is to relock your bootloader. You can run RUU from fastboot.
Click to expand...
Click to collapse
Well recovery works perfectly but there is no rom or file in the sd card at all because of the total system wipe, and ADB doesn't seem to detect my phone since it requires USB debbuging (or am i wrong?) and usb debugging isn't accessible since it hangs on the facebook logo. Only when it's in fastboot does it get recognized; but im not aware of a way to push the rom files through fastboot? I would very appreciate a tutorial if there is! that's why im looking for a system.img that i can flash using fastboot.
And as for the RUU I can't get to the Fastboot screen on the program because it first needs to confirm my phone model and system which it can't because it requires USB Debugging to be turned on on the phone. Also would relocking the bootloader still be necessary even though I have S-off?
About doing the ADB push through recovery to sd card, I don't see any option like that on the menu. I have CWM would I need TWRP for that?

USB debugging is only needed in the OS. In recovery you can do a lot of things even without root. ADB just has trouble detecting a device that's gone through a firmware change, just type "adb kill-server" and try again. You don't need to mount anything to push to /sdcard.
Do RUU as a last resort, since getting S-off again after relocking the bootloader is an elaborate process. But don't worry about the warnings. RUU will work when your phone is in fastboot, the first thing it does is reboot your phone anyway.

Does this help?

HTC One Stuck in Bootloader and Can't Get Into Recovery

I've got an HTC One with Sprint running 4.2.2 (3.05.651.6). I unlocked the bootloader and rooted it using qbking77's tutorial. I haven't flashed any ROMs on my phone.
Everything has been working fine until yesterday. I took my phone out of my pocket and it was dead. I charged it up and when I turned it on it was stuck in a boot loop on the htc screen. I can get into bootloader fine and fast boot usb shows up on my phone when connected to the computer, but I can't access my TWRP recovery. It shows TeamWin screen then boot loops again.
I have re flashed the recovery and erased the cache. I have also tried to lock the bootloader using Hasoon2000's HTC One All-In-One Toolkit and by connecting to fastboot and typing in "fast boot oem lock. For the toolkit i get device not found and an error and when using the command prompt I get FAILED (status read failed (No such file or directory)). I think its possible my usb debugging may be off since I can't find any devices using adb but my pdanet can find my phone (which needs usb debugging) so I'm not sure.
If I can get it locked, I can use RUU to get back to stock.
I'm running out of options. I'm thinking I can still flash a non-stock rom to get the phone running again and then relock and go to stock. Any ideas on what my issue is and how to fix it? Any input is appreciated.

[Solved] Stuck on white hboot screen while downgrading

Hi,
I had unlocked boot loader through HTCdev on latest GB stock ROM. So, obviously I was S-ON.
Meanwhile, I tried many ROMs but manually flashing boot image in hastboot.
I had following status of last running mobile when I tried to get S-OFF
Bootloader status: unlocked
S-ON
HBOOT 2.00.0000
Recovery: CWM
ROM: CynovivoX (JB 4.1.2)
Yesterday, I tried to get S-off by downgrading as per following thread
http://forum.xda-developers.com/showthread.php?t=1705913
There were lots of error while script was running, but one I remember was related to goldcard.
While running RUU, It goes well till I find something Error 131, Customer ID related and than exit.
After trying script and RUU many times, my status is
Bootloader status: Relocked
S-ON
HBOOT 2.00.0000
Recovery: ? (can't see or access anymore)
ROM: -
when running fastboot devices, my device is appearing
but in adb devices, nothing there
So, is there still any possibility to recover from this bricked state?
Desperately looking for expert help as I am not developer but somehow....tried this thinking would not be that difficult business....so help.

Try running the latest RUU and restarting everything over. Make sure to pick the right RUU for your region. The latest build number should be 4.14.XXXXX...
Also, in fastboot, your device isn't supposed to be visible with command of adb devices.
Another thing u could try is to unlock the bootloader again and see if u can access recovery again. Adb works in recovery
Sent from the head of the Hammer

If you can get into fastboot but don't have a recovery installed, can't you just flash a new recovery? E.g. grab clockworkmod, connect your phone to your computer via usb and:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-vivo.img
(obviously replace above code with actual name of .img file)

err this might be stupid, but click on bootloader > recovery.
Looks like you are already in a sub menu when you boot the bootloader.
The error while downgrading is related to you not relocking your phone before downgrading. Always relock before downgrading with an RUU.
Sent from my Nexus 5

Thanks all guys.
But problem fixed. I have unlocked the bootloader again through htcdev and it worked.
Now let me share issue for all other nondevelopers like me who may also face such issue...
runme script is suppose to push some files through adb commands and then reboot to fastboot mode to lock bootloader.
I had adb drivers installed as I got prompt from statusbar.
However still, while running downgrade script (runme), phone was not detected in adb mode and hence no file was pushed to phone. After reboot, phone detected in fastboot and OEM successfully relocked.
I am really surprised why device not found error not appeared and script not stopped. Later I came to know this by running the script without connecting phone and it ran with asking Q&A with found device, and also reading log file.
Then I ran RUU who wiped everything.
So, my device left without any ROM and with OEM locked. I can't access or install recover, ROM etc and RUU was having goldcard error.
Somehow tried to unlock again through token provided by HTCDev earlier (around 2 years back).
And thing become normal and in my control.
My advise: always check "adb devices" before running the script as I found script is misleading of found device and finally locking device. And if such thing happen, easiest one is to get in unlocked from HTCDev and restart whole process.

RmatriX1218 said:
Thanks all guys.
But problem fixed. I have unlocked the bootloader again through htcdev and it worked.
Now let me share issue for all other nondevelopers like me who may also face such issue...
runme script is suppose to push some files through adb commands and then reboot to fastboot mode to lock bootloader.
I had adb drivers installed as I got prompt from statusbar.
However still, while running downgrade script (runme), phone was not detected in adb mode and hence no file was pushed to phone. After reboot, phone detected in fastboot and OEM successfully relocked.
I am really surprised why device not found error not appeared and script not stopped. Later I came to know this by running the script without connecting phone and it ran with asking Q&A with found device, and also reading log file.
Then I ran RUU who wiped everything.
So, my device left without any ROM and with OEM locked. I can't access or install recover, ROM etc and RUU was having goldcard error.
Somehow tried to unlock again through token provided by HTCDev earlier (around 2 years back).
And thing become normal and in my control.
My advise: always check "adb devices" before running the script as I found script is misleading of found device and finally locking device. And if such thing happen, easiest one is to get in unlocked from HTCDev and restart whole process.
Click to expand...
Click to collapse
From what I'm reading, I'm getting a much clearer image of what happened. I believe your problem to be just driver errors...
The script itself is supposed to run regardless of whether phone is properly connected with proper drivers and whatnot. After all, it's just a set of commands in cmd.
But seeing as you ONLY got Error 131, you could have solved this by simply creating a goldcard.

072665995 said:
From what I'm reading, I'm getting a much clearer image of what happened. I believe your problem to be just driver errors...
The script itself is supposed to run regardless of whether phone is properly connected with proper drivers and whatnot. After all, it's just a set of commands in cmd.
But seeing as you ONLY got Error 131, you could have solved this by simply creating a goldcard.
Click to expand...
Click to collapse
Phone was connected in adb mode. This I can say by checking notifications in android and statusbar prompt in windows 7. While running script only, something got wrong getting adb mode not detected.
Anyway, Goldcard was also in my next line of action, but not sure even after creating Goldcard, I may stuck as version-main was not downgraded to 2. However, tried and got resolved with much simpler effort of unlocking through htcdev.
May be, I am also not that competent to understand developing world and only good enough to simply flash ROMs and updates as per instructions.
Anyway, thanks.

[Q] Phone is Dead :(

Ok, first off i was soff unlocked.. i then updated my phone to the latest OTA sense 6. I then tried to install customs roms which ended up not booting and forcing my phone to have no OS. so not being able to access the OS or sideloading roms, i tried RUUing but couldnt get the side to side error fixed. so then i continued to try and downgrade my firmware so i can ruu the official htc 3.xx one. as soon as i downgraded to hboot 1.55, my phone isnt recognized in fastboot anymore. so i can not access my phone from either adb or fastboot. anyone have any suggestions?

here you are
firespitta said:
Ok, first off i was soff unlocked.. i then updated my phone to the latest OTA sense 6. I then tried to install customs roms which ended up not booting and forcing my phone to have no OS. so not being able to access the OS or sideloading roms, i tried RUUing but couldnt get the side to side error fixed. so then i continued to try and downgrade my firmware so i can ruu the official htc 3.xx one. as soon as i downgraded to hboot 1.55, my phone isnt recognized in fastboot anymore. so i can not access my phone from either adb or fastboot. anyone have any suggestions?
Click to expand...
Click to collapse
I recently had the same issue, you should be able to fix this by following these steps, keep in mind, continuing this process will unroot your device. Thus, you will loose all of your data on your phone.
first begin by booting into bootloader, then plugging in your device via usb cable to your computer, it should now say "fastbootusb" on the device's screen.
if you don't already have the the fastbooot files required for your computer, you can download them here: ftp.qbking77.(com)/Files/OneDrivers_Fastboot.zip
after that, extract the zip file somewhere on your computer, and open the fastboot folder. Now hold down shift and click on an empty space in the folder and choose open new command window here, or something along those lines.
Now that you've done this, type fastboot oem lock and press enter, this will relock your phones bootloader.
Now, unplug your phone from usb, and reboot back into fastboot, and once again, plug the device into the computer. Just as before, your phones screen should now say fastboot usb. You can now flash this file via fastboot by following the instructions below.
androidfilehost.(com)/?fid=23329332407568410
rename the file downlaoded to firmware.zip and copy it to the folder containing your fastboot.exe file
now in the command prompt window, type in Fastboot oem rebootRUU
you should now see a black screen with the HTC logo, type Fastboot flash zip firmware.zip,
once that is complete, type fastboot reboot and once more, reboot into fastboot
you can now download this RUU file from the following link: androidfilehost.(com)/?fid=23329332407573774
extract the zip folder somewhere on your computer
boot into bootloader, and once again choose fastboot,
plug in your usb cable to your phone and computer, and the phone should once again say fastboot usb.
now open the folder you extracted and run ARUWizard.exe, this will unroot your device and return you to stock.
now, if you wish, you may re root your device.
Hope this works, if none of this makes sense, mention it. I typed this up in a bit of a rush.
also, you will have to copy and paste the links, as I have not made 10 general posts, so I can't add direct links to my post. Sorry mate.
as far as your fastboot issue, try re installing the htc and fastboot drivers.

HTC Desire 626s Not Recognized in DL Mode

Hello,
I have a 626s that is recognized in its normal boot state, but not in Download Mode. Fastboot gives "Waiting for Device"; ADB gives "Device Not Found"; and HTC Sync gives "No device connected."
The phone does have an unlocked bootloader and USB debugging is turned on.
The phone's history:
Bootloader unlocked, TWRP flashed, SuperSU installed.
Root uninstalled by SuperSU app. (It asks if I want the original bootloader [?] flashed. Clicked "No". This is where problems started.)
Made a backup of my phone through TWRP, in which it refuses to backup the System partition in any way.
Decided to revert phone to stock through RUU.
Need to replace misc.img to do so.
ADB cannot find the device.
And this is where I'm stuck. I don't know if any of what I just listed is what is causing the main problem, but it could help. If anyone knows of a way I could revert the phone to the stock ROM any easier, it would be appreciated. I don't care about loss of any data.
Thanks.

Eh, I explained this to another guy earlier so I'll just dumb it down a bit.
Download the RUU for you specific carrier and such from the HTC site.
Go through the .exe until it prompts the install to the phone, but don't start it.
Go to %temp% in Windows Explorer and find rom.zip
Rename the .zip to "0PM9IMG.zip" and place it in the root of your external sd.
From here you can do as you please with it. I used the bootloader to install it. :laugh: