I am stuck with my HTC Hero and I need help to find my way out of the maze.
I was having trouble with my RCMix v2.2 WWE instalation. I decided to flash a new ROM.
What I did:
I tried to boot into recovery but it didn't work. I believe recovery was damaged. I went to installed Rom Manager and tried to reinstall RA Recovery. When it was rebooting, phone got stuck in the first white screen.
Now that's where I am stuck:
Even though I try all the rebooting shortcuts, it doesn't load regular ROM and doesn't load recovery. It keeps showing the white screen with HTC logo and "quietly brilliant" slogan. And it starts it over and over.
If I try to go into recovery with power+home button it freezes in HTC logo on white screen, without looping and without showing "quietly brilliant" slogan.
My two options were:
1) Flash a recovery using ADB. It didn't work. I think that's because phone doesn't really goes to the point where the desktop software can reach it through debug mode. Doesn't know where to go from here. I go to Windows CMD line, in ADB folder and try to run "adb shelll". It shows me "Error: device not found".
2) Install a stock/shipped ROM. My hope was to start from a shipper rom and go from there all the way to rooting and flashing a custom ROM. The installation of a shipped ROM worked until the point where it checks the ID. Since I don't have a goldkey (and there is not way I can create one) it doesn't allow me to finish shipped ROM instalation. Is there an universal shipped ROM file which doesn't demand a specific ID or goldkey?
So... What do I do? Any one can give me a clue?
Thanks!
I've been trying to use ADB + Fastboot to install RA Recovery, as described here:
http://forum.xda-developers.com/showthread.php?t=561124
The problem is that the instructions below don't work:
via fastboot + adb -> In case you don't have a custom recovery, so when you get signature fail errors
Code:
adb shell reboot bootloader
fastboot boot recovery-RA-hero-v1.7.0.1.img
adb shell mount /sdcard
adb push recovery-RA-hero-v1.7.0.1.img /sdcard/recovery-RA-hero-v1.7.0.1.img
adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.7.0.1.img
adb shell reboot
Click to expand...
Click to collapse
As you can see here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What am I doing wrong? (I wish I could have asked in the related thread, but I was not allowed).
Related
Have a LG Optimus V version 2.2.1 that i did a factory reset on with the stock rom that was working at the time. The phone had to go back to Virgin Mobile for a swap as it has CyanogenMod on it. I didn't want Virgin to know i messed with there phone/get charged, etc.
After rebooting from a factory reset, the screen looked like this, NEVER DO A FACTORY RESET.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This blue screen is called fast boot mode, it basically will say
Code:
fastboot mode started
gpio_i2c: invalid khz: 0
bl: i2c write error
udc_start()
In this state, there is no access to ClockworkMod Recovery or the mod itself. The phone is a dead stick.
After spending hours researching this, I found a resolve.
If your running Windows XP, follow this guide to fix it
If your running Windows 7:
Install the LG VM670 Drivers here. File is named LG VZW United WHQL v2.5.2.exe
Once the Fastboot Drivers Installed. Continue with all the commands from the above link under 2) Usage
Open Cmd and type or copy and paste these commands ONE BY ONE with the USB cable plugged in.
Code:
cd C:\Fastboot\android-sdk-windows\tools
fastboot erase boot
fastboot erase recovery
fastboot erase system
Now we need to flash recovery via Fastboot. Type or copy and paste this command on Cmd:
Code:
fastboot flash recovery C:\Fastboot\Recovery\recovery-RA-optm-2.2.1-GNM.img
Then type this on Cmd to reboot to recovery:
Code:
fastboot reboot
Now your phone will reboot to recovery. All you have to do now is to install a rom and your phone will be back to normal.
Hope this helps.
Removed
Sent from my LG-P500 using xda premium
*deleted*
*deleted*
*deleted*
Hi, i can't help you for now, but i have your same smartphone and i want to make a cwm recovery.
I've been rooted succesfully the phone and i made a cwm for this device, does anyone know how put the you25 in fastbootmode?
*deleted*
your help will be apprecciated,
the phone if of my girlfriend and now, after tryng to flash a cwm recovery built by the online builder,the you25 is still in bootloop.
Fortunately, I made a backup of the stock recovery and now i have to reflash it.
I need to know how put the phone in fastboot mode or eventually how reflash all the entire system, (before my girlfriend knows what i did:crying.
If you are interested, i made a cwm porting that works for 50%, you can backup and restore all entire system; then i tried the online builder to make it 100% working but with no success.
*deleted*
*deleted*
No, i can't access adb, i need to put it in fastbootmode by pressing at startup a sequence of buttons. (Es, power+vol down or whatever else for this devise).
Now i see the android logo only plugyng the power cable, it still appears for about 3-4 seconds, then the backlight of the three buttom buttons lights on and then the device reboots.
Initially, I flashed the recovery by adb, after rooted the mobile and mounted the filesystem in r/W mode with:
Code:
dd if=/sdcard/recovery.img of=/dev/blocks/mtdblocks10
.
You can find the right number by typing in adb shell:
Code:
cat /proc/partitions/
I have experience with other device, generally you can flash with adb, fastboot and by download mode, if the device boots you can always fix it, but you need the right tools.
*deleted*
mgbrain said:
what happens when you boot the device by normal start, does it also go into the 3-4 seconds bootloop or does it get stuck on the android logo?
i had my device stuck there already too but i was still able to access adb.
Click to expand...
Click to collapse
The device starts only if i plug the power cable, after 5-6 second the android logo shows up and then after 4 seconds the device reboots.
Adb doesn't work for me, but if you have adb working i think i can help you.
What is the last think you made to the device before beeing stock on the boot?
*deleted*
Thank you, but that doesn't work for me.
What about jtag? i have experience with decoders but nothing about smartphones.
Reading about how restore nexian a850, i founded that is possible to reflash the you25 with the sprocoom tool and the same driver of the nexian a850. Unfortunately I do not have the firmware for the you 25. Has anyone it, please?
I think that it is possible to flash the device using the img files that i created before and a prebootloader.
I have also to edit a file with a list of all partitions with their address in hex format.
Unfortunately i do not know these values, and i cannot see them from my device because it doesn't work. can anyone help me, please?
here is a list of all partitions:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Dear all,
I've used device name EBEN T4 (e人e本 T4 - from china). I rooted device and deleted/modified system. So, now it can not boot, it stuck at manufacter logo. I wiped data/factory reset or wipe cache but not success. So it need to be reflashed device roms.
Device allowed me to enter recovery mode and select update rom from zip file on SDCard (internal memory). I saved zip file on SDCard. BUT SDcard have so many folders and files in root folder, and zip file names "update.zip" - it means that it is on near last of list, and recovery limited number of line to view, so i could not browse to update file.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Device has Vol +/-, home, left, right, back, menu and power button. (Home + Power will bring me to recovery mode)
Device use CPU Freescale i.MX535, android 2.3.4, origional recovery system.
Please suggest me how to fix that by anyway.
P/S: I found that Back + Power will bring me to fastboot interface?
Need help so much
That's why you should backup your system before rooting etc. Do you have a stock image of your device?
eagleeyetom said:
That's why you should backup your system before rooting etc. Do you have a stock image of your device?
Click to expand...
Click to collapse
Thank you for reply.
This is stock image: http://update.eben.cn/t4/update.zip
I found that my device could enter fastboot mode by press back + power button.
When connect usb, screen show:
[fastboot mode]
fastboot is in init......
fastboot transfer buffer: 0x0000000
flash <1 word i cant recoginze> is MMC: 1
USB Mini b cable Connected!
fastboot initialized
USB_SUSPEND
USB_RESET
USB_RESET
Windows device Manager (on WIndows 7 32bit) shows that device connect (ADB), i'm used to use many ADB universal driver (google, ClockworkMod). When i used "fastboot devices" command, it reponsed nothing.
Could i connect to fastboot to update file update.zip to device? If ok, how i connect?
Fastboot will give you nothing, mate. Try to set up the ADB and use adb sideload <path/to/zip> without "<>" or delete folders in recovery by going to adb shell and changing the dir by cd command and removing them by rm -r foldername.
Good luck.
This phone is my brother's. He said he just downloaded a system update, I think it is OTA. And when update starts (from the stock recovery? not sure) It stucks at 50% progress bar, and it reboots. And update starts again, and reboots again. It won't boot even after removing battery, putting battery back on and turning the phone on, it persistently go back to loop update system. Should I flash it with a stock ROM? which one? The build no. I think is 1.0020? Can I flash the 1.050 one? Here is a pic of what's happening in a loop.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Follow this guide to reboot into recovery
http://www.hardreset.info/devices/acer/acer-liquid-z630/recovery-mode/
After entering recovery , try factory resetting your device.
This will reset all data.
If the above method didnt work , only option is to flash a Rom manually using SP Flash Tool
Stock Rom
http://vache-android.com/hubicAcer/Z630/OS Images/Acer_AV0L0_T03_1.020.00_EMEA_GEN1.zip
Hello there. Please take a look at this guide by Shreps.
Download a compatible custom recovery (CWM or TWRP) for your device. Also download the firmware (ROM) for your device (list by Shreps). Please refer to the guide (there should be one). You would need to (a) Install necessary drivers, and (b) ADB and Fastboot interface (try this)
Copy the custom recovery image into the root folder of your ADB and Fastboot program. Copy the firmware to your device (via external sdcard since you cant copy directly into the internal sdcard).
Go to recovery via (a) volume up + power buttons, or if device accessible via ADB, (b) adb reboot recovery
In the recovery options, choose 'fastboot' (or simply, via adb: adb reboot bootloader)
Go to your terminal/cmd: fastboot devices - and see if your device is recognized
Then: fastboot boot "recovery.img" (replace "recovery" with the name of the recovery image)
In the recovery, navigate and select "Install" and select the firmware on the external sdcard. (wiki)
If you cant install via fastboot (bootloader must be unlocked first before using fastboot), then flash the rom via SP Flash tool (refer to the guide)
Just for fun I changed the boot logo of my phone. Since it was such an easy a thing to do, here are some logos you can use.
Just boot in to TWRP and flash.
This is how I did it (in linux):
1. extract an original miui-rom. As long as it has the logo.img, it will do.
2. download the wonderful logo-xiaomi.py-script that penn5 has created.
(Link: https://github.com/penn5/logo-xiaomi)
3. extract the logos from logo.img
$ python3.9 logo-xiaomi.py extract -i logo.img -o output
4. edit (using what ever editor or tool you prefer) the images logo-0.bmp (boot logo for locked phone) and logo-2.bmp (boot logo for unlocked phone). Don't edit either of the other two. They're familiar for people, so they know their phone is either in fastboot mode or has been soft bricked. If you do edit logo-1.bmp and/or logo-3.bmp people will be confused if either something soft bricks the phone, or they try to enter fastboot mode. Yes, if you haven't done so in a while this might confuse you. Leave logo-1.bmp and logo-3.bmp alone.
logo-0.bmp and logo-2.bmp is what you want to edit.
IMPORTANT - remember to save as bmp and in the correct resolution. If you save it in the wrong format and/or the wrong resolution, your phone might not show any boot logo on boot.
5. repack the logo.img-file.
$ python3.9 logo-xiaomi.py -i logo.img -o logo.new.img -a logo-0.bmp -a logo-1.bmp -a logo-2.bmp -a logo-3.bmp
Yes, in that order. The logo-xiaomi-script creates the new image of the files in that order. If you change the order of the logo-files, they'll end up in the wrong order on the new logo.img.
6. either create a flashable zip, using one of my zips, adb push the logo and adb dd it on the logo-partition, or fastboot flash the logo.
fastboot flash logo logo.new.img
OR
adb push logo.new.img /tmp
adb shell dd if=/tmp/logo.new.img of=/dev/block/bootdevice/by-name/logo
This is what the bootlogos I've made look like:
AOSCP
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
G-BLACK
GOOGLE-BLACK
HAVOC
SNAPDRAGON
XIAOMI-EU
Standard is just the standard boot logo, in case you wish to revert back to the normal one.
This is great As soon as I get a little free time I am going to change my boot logo to something personal. Even if it's just for showing off to some friends
@Verbato isn't xiaomi logo in logo.bin not logo.img?
i've try and its gave me error
langithitam said:
@Verbato isn't xiaomi logo in logo.bin not logo.img?
i've try and its gave me error
View attachment 5752805
Click to expand...
Click to collapse
No, it's in logo.img. I did all this in linux (Arch). You might get this to work in WSL. But I'm not guaranteeing anything other than I had no problems under linux (others might not have the same luck).
@Verbato
Sir, can you please make this logo?
device unlocked
twrp and magisk installed