Develop Bugs

ROM upgrade failed !!!

Hi everybody,
I look through the threads and I couldn't find a solution to my troubles. So here it is: I just bought a htc touch pro 2 which came with a window mobile 6.1. Before I transferred anything from my old phone, I thought better to do the official upgrade to 6.5 ROM version 1.86.401.0.
I wanted to flash the ROM through a USB cable as described on the HTC site, but after after having done 22% of the work, everything got stuck. And 5' minutes afterward the update windows on the PC disappeared and I had to disconnect the phone!!!
So now I have a beatiful telephone, which cannot boot up. Indeed, it gets stuck in the 4 colors bootloader.
i) I tried to do a factory reset (pressing power, send hang up buttons) to no avail.
ii) I tried to take out the batteries and pull them in again, then switching on the phone holding down the vol down + power up buttons, then reset.
iii) reconnecting the phone back to the PC by usb, I was never able to get a switch from "serial" to "usb"
Nothing is working, if anybody has an idea what I could try next.... I am wondering if it is possible to flash the phone from the SD card. I am really a newbie here.
Thanks
Max

Yea .. same thing happened to me ..
Check Here For Full Info: Click Here
*Go into BootLoader Mode (do a Soft Reset while holding the "volume down" key on the left side of the device. Keep holding the "volume down" key until you see tricolour screen which is the bootloader mode, then release it)
Flashing Via MicroSD Card
1. Make sure your microSD is Formatted to fat32 (you dont have to delete all files but it is safer if you do)
2. Download your prefered Rom from the Rhodium Rom Develpoment Page and unzip/unrar it to your PC
3. Goto the Roms Folder and rename the .nbh file to RHODIMG.nbh
4. Copy the RHODIMG.nbh file to the root of your MicroSD Card
5. Plug the MicroSD Card into the phone
6. Enter the BootLoader screen, you will first see a tri-color screen with the phone and SPL Information at the top
7. Follow the On Screen instructions to start the update
8. After flash has completed, press the reset button with the stylus to reset the device.
Good Luck ! Worked For me !

Thanks for your help and the link to the thread!! I will use your approach next time. Indeed, in the day afterwards I was able to finally flash the phone from the same PC. I did the manipulation, which failed miserably, with a 64 bit Windows 7 RC. Then, I realised I had another version of W7 on the same PC, a 32 bit version this time. Thus, when I tried it with my dying telephone, the "serial" message on its screen switched "magically" to "usb" and I finally could flash the damned mobile! Frankly, I don't know what's wrong with my 64bit W7 if anything.
Cheers
Max

my htc pro2 failed upgrade: any help
WarlockW said:
Yea .. same thing happened to me ..
Check Here For Full Info: Click Here
*Go into BootLoader Mode (do a Soft Reset while holding the "volume down" key on the left side of the device. Keep holding the "volume down" key until you see tricolour screen which is the bootloader mode, then release it)
Flashing Via MicroSD Card
1. Make sure your microSD is Formatted to fat32 (you dont have to delete all files but it is safer if you do)
2. Download your prefered Rom from the Rhodium Rom Develpoment Page and unzip/unrar it to your PC
3. Goto the Roms Folder and rename the .nbh file to RHODIMG.nbh
4. Copy the RHODIMG.nbh file to the root of your MicroSD Card
5. Plug the MicroSD Card into the phone
6. Enter the BootLoader screen, you will first see a tri-color screen with the phone and SPL Information at the top
7. Follow the On Screen instructions to start the update
8. After flash has completed, press the reset button with the stylus to reset the device.
Good Luck ! Worked For me
i tried this option but didn't work, is there any help, the phone can't come up again
it show this Error msg at 0% "BOOTLOADER - FAIL" update terminated
Click to expand...
Click to collapse

larryike said:
i tried this option but didn't work, is there any help, the phone can't come up again
it show this Error msg at 0% "BOOTLOADER - FAIL" update terminated
Click to expand...
Click to collapse
\
Did you try the stock rom from HTC loaded over the usb first?
Information about what unlocker you tried to use, what kind of phone you have, what kind of rom you tried to load would be helpful.

SGS3 Connection Issues and Download Mode Help

There are three parts to this thread - How to get into download mode, how to get into recovery mode, and how to solve problems connecting your Android device to your computer. I think you should be able to find where each one begins without too much trouble.
----------------------------------------------------
GETTING INTO DOWNLOAD MODE
----------------------------------------------------
"Just get into download mode and..."
Ever find yourself with a phone that's misbehaving, and you can't seem to figure out how to get it to download mode?
Here's a list of things to try, sorted in a "where are you now" setup:
Note: You will need to use Vol+ to select download mode after you reach the mode selection screen.
FROM A POWERED-DOWN STATE - BATTERY REMOVED
- Insert battery, then press and hold Vol-, Home button, and Power.
- Press and hold Vol-/Home/Power, Insert Battery.
- Use a USB jig (can be manufactured jig or homemade chain of resistors)
FROM CLOCKWORKMOD RECOVERY MENU
- Position the cursor (highlighted selection) on "Restart device", hold Vol-/Home, then press power
- (Where available) Use the "Reboot Download" option in the "Advanced" menu
FROM A FULLY BOOTED PHONE STATE, WITH USB DEBUGGING ENABLED
Note: you may need to have ADB installed on your computer, and/or an Android Terminal Emulator installed on your Android device.
- Connect your Android device to your computer, navigate to your ADB directory, and type "adb reboot download"
- (Where available) Use the rom's power menu option to reboot into download mode.
- From a terminal, type "su", then "reboot download"
- Download the app "quickboot", follow the app directions to reach download mode.
----------------------------------------------------
GETTING INTO RECOVERY MODE (CWM RECOVERY)
----------------------------------------------------
FROM A POWERED-DOWN STATE - BATTERY REMOVED
- Insert battery, then press and hold Vol+, Home button, and Power.
- Press and hold Vol+/Home/Power, Insert Battery.
FROM A FULLY BOOTED PHONE STATE, WITH USB DEBUGGING ENABLED
Note: you may need to have ADB installed on your computer, and/or an Android Terminal Emulator installed on your Android device.
- Connect your Android device to your computer, navigate to your ADB directory, and type "adb reboot recovery"
- (Where available) Use the rom's advanced power menu (long press power in android OS) option to reboot into recovery.
- From a terminal emulator, type "su", then "reboot recovery"
- Download the app "quickboot", follow the app directions to reach recovery mode.
- Download the app "Rom Manager", select "Reboot to Clockwordmod Recovery"
----------------------------------------------------
UNIVERSAL FIRST STEPS FOR CONNECTION ISSUES
----------------------------------------------------
So you've got Odin up, the phone's in download mode, it's connected to the computer, but Odin is saying "What phone?". You've tried jiggling the handle, checking the blinker fluid levels, and even using the board stretcher, but the Android guy is smirking at you with that smug green face.
Although it is possible that there is something else at work that's preventing your phone from connecting, I would suggest trying these "universal first steps" to see if you can resolve the connection issues:
1. Turn off both devices (phone and PC) - and I do mean full power-down. Go ahead and pull the phone's battery, if necessary.
2. Disconnect your phone from your computer at all points - USB out of phone, USB out of computer.
3. Start up your computer. Don't touch it, don't do anything to it. Let it fully boot and completely settle.
(Obviously, log in if it's necessary, but then let it finish booting before moving on to step 4.)
4. Start up Odin. Let that get completely started and settled.
(If on Vista/Win 7, make sure to "Run as Administrator" in the right-click menu.)
5. Connect your USB cable to a different port than the one you last had it connected to.
(If you're on a Windows desktop, the ports in the back of the computer are generally more stable and should be used. If you're on a laptop, use USB port #1)
Do not connect the phone to the cable yet.
6. Start your phone in download mode. Wait until you see the Android guy with the 4-5 lines of text in the upper left corner.
7. Connect your cable to the phone. Let it sit until Odin recognizes it (which should only take a couple of seconds).
If, for some reason, Odin doesn't recognize the phone at this point, here are a few more things to check/try:
- Repeat steps 1-7 above, making sure to change USB ports. As dumb as it sounds, sometimes the phone or computer just doesn't like particular USB ports.
- With everything still up, switch USB ports.
- Try a different OS (if possible) - sometimes Ubuntu will recognize what Windows won't, and vice versa.
- Try doing this on a different computer - again, different OS, different USB ports, they're all links in a chain and sometimes you'll come across a configuration that doesn't have the weak link.
- Try a different cable. I've had a case where I couldn't do any flashing with one cable, but everything was rock-solid and smooth on the same machine with just a different cable.
- Fully uninstall your drivers, reboot the computer, reinstall the drivers, power down, and then start again from step 2. Sometimes faulty drivers are the problem.
--------------------------------------
Additional Note:
If you're moving from an AOSP-based rom (MIUI, CM10, etc) to a Touchwiz-based / Samsung Stock-based rom, remember to wipe data / factory reset prior to flashing a stock rom. You will hang on the "Samsung" logo if you don't.
Please note very carefully, though, to do the wipe in CWM recovery - not 3e recovery. If you do it in 3e recovery, you'll format the internal storage, meaning you lose all your pictures, music, etc.. (I learned this the hard way.)
--------------------------------------------
If anyone has any additional items / corrections, please reply and I'll update the OP accordingly. Thanks.

Reserved

Great guide!
I'd like to add my experiences, while using CWM 6.0.1.2 booting into Recovery is a bit tricky. It appears the default recovery boots instead of CWM. The only work around I know of is to Flash ClockworkMod Recovery first from ROM Manager v5.0.2.0 and then select Reboot into Recovery. Any other method I try seems to fail.
I'm running Stock At&t ROM, rooted.

Hey Mrhaley,
I just found your post. Wish I knew I had to wipe data and factory reset before flashing stock rom... well I followed another post to use kies and now Im stuck. Im hanging on samsung logo. Can you help me fix this?
Thanks

djtiko said:
Hey Mrhaley,
I just found your post. Wish I knew I had to wipe data and factory reset before flashing stock rom... well I followed another post to use kies and now Im stuck. Im hanging on samsung logo. Can you help me fix this?
Thanks
Click to expand...
Click to collapse
OP thanks for exelent post..I had one more problem with USB connection. Sticks in usb port did not connect correctly. Just jently squize USB male connector on samsung data cable so top of male connector will bend just enough to get good connection when you push back to PC port.
@djtiko - I answer on other post to your problem..

djtiko said:
Hey Mrhaley,
I just found your post. Wish I knew I had to wipe data and factory reset before flashing stock rom... well I followed another post to use kies and now Im stuck. Im hanging on samsung logo. Can you help me fix this?
Thanks
Click to expand...
Click to collapse
Do a factory reset again, should fix you up. If not, consider using Odin to flash a stock ROM package.

Thanks got it all fixed, just had to do a data wipe in the stock recovery and then I was golden

ondin
Hey guys when i run the bootloader file should i open it up in the pda tab on ondin or in the Bootloader tab?

Should be in the pda tab I believe.
Edit. Which bootloader file are you referring to? To know for sure, you could just flash the entire stock rooted jelly bean Rom.

If using Odin with Chainfire to auto root just to root I found that the file that you are using to root you HAVE to have in the SAME folder I made the mistake of downloading the Odin then Odin with chainfire from http://forum.xda-developers.com/showthread.php?t=1963790 then was opening the odin first downloaded then it would stall for not able to start the installation then rechecking the unzipped folder for the .tar.md5 file noticed that Odin was there too, loaded it and PRESTO rooted in less than 30 seconds... So for other that are just looking to root give chainfire a check, yes you would need to use the triangle away if you are worried about that however you don't loose anything when doing it this way so all a matter of what you are looking to do. THANK YOU so much for the help with the drivers issues!

A trick to dual boot Android and Ubuntu or other OS

I found a trick to enter hardware recovery mode without connecting SATV to PC.
In the past, I had to connect SATV to a PC using microUSB to USB cable to enter recovery mode by hold power button for ~3 seconds.
After flashed rooted ROM 3.0 I found behavior of HW recovery mode changed, i.e., I need to hold power button much longer than 3 seconds after power light turns green until entering recovery mode.
Then I found by accident, if I left a micro USB OTG cable like this connected to the SATV:
http://www.walmart.com/ip/27420736?wmlspartner=wmtlabs&adid=22222222222018938306&veh=sem
I can enter recovery mode without connecting to a PC.
Regular Micro USB Cable - A to Micro B cable like this needs to be connected to a PC to enter recovery mode:
http://www.amazon.com/StarTech-com-Micro-USB-Cable-UUSBHAUB6/dp/B0017K4CJC
I have Android in recovery partition and ubuntu in boot partition, I can boot to ubuntu after power up by default, or hold power button to enter recovery mode to boot to Android from recovery mode menu without connecting SATV to a PC.
It can also be done by leaving Android in boot partition and other OS in recovery partition to boot to Android by default.

yahoo2016 said:
I found a trick to enter hardware recovery mode without connecting SATV to PC.
In the past, I had to connect SATV to a PC using microUSB to USB cable to enter recovery mode by hold power button for ~3 seconds.
After flashed rooted ROM 3.0 I found behavior of HW recovery mode changed, i.e., I need to hold power button much longer than 3 seconds after power light turns green until entering recovery mode.
Then I found by accident, if I left a micro USB OTG cable like this connected to the SATV:
http://www.walmart.com/ip/27420736?wmlspartner=wmtlabs&adid=22222222222018938306&veh=sem
I can enter recovery mode without connecting to a PC.
Regular Micro USB Cable - A to Micro B cable like this needs to be connected to a PC to enter recovery mode:
http://www.amazon.com/StarTech-com-Micro-USB-Cable-UUSBHAUB6/dp/B0017K4CJC
I have Android in recovery partition and ubuntu in boot partition, I can boot to ubuntu after power up by default, or hold power button to enter recovery mode to boot to Android from recovery mode menu without connecting SATV to a PC.
It can also be done by leaving Android in boot partition and other OS in recovery partition to boot to Android by default.
Click to expand...
Click to collapse
Hi, nice finding!
May I ask for some assistance? I'd like to dual boot the stock rom (for video watching) and a full android rom (for unsupported games and apps). Do you think it's possible using your trick? I don't mind having to enter recovery to boot my second rom.
Thank you!

grievous2004 said:
Hi, nice finding!
May I ask for some assistance? I'd like to dual boot the stock rom (for video watching) and a full android rom (for unsupported games and apps). Do you think it's possible using your trick? I don't mind having to enter recovery to boot my second rom.
Thank you!
Click to expand...
Click to collapse
I have ubuntu kernel in boot partition and stock SATV ROM 3.0 in recovery because I mainly use ubuntu, I occasionally try stock SATV.
I believe you can leave kernel of stock ROM in boot partition and put kernel of alternative OS in recovery partition. Some versions of ROM had a bug that any alternative OS in recovery partition gets replaced after power cycle. I have not tried to put alternative OS in recovery partition.

This is fantantasic, I've been following your prior posts and links for booting Ubuntu, is this image stable enough to use as a daily PC, and I take it the GPU does not work yet? Or do the aarch64 drivers enable it on the satv

Afeld88 said:
This is fantantasic, I've been following your prior posts and links for booting Ubuntu, is this image stable enough to use as a daily PC, and I take it the GPU does not work yet? Or do the aarch64 drivers enable it on the satv
Click to expand...
Click to collapse
As far as I know, SATV ROM 3.0 and ubuntu kernels base on CM13 or L4T23.1 are stable for dual boot. I have not updated to SATV ROM 3.1 and L4T kernel 23.2. I have run Nvidia Cuda samples without issues. Bluethooth is not working and remote controller is not usable under ubuntu.

so is there a way to dual boot stock android tv ROM & custom ROM with full android support??

Slayerkodi said:
so is there a way to dual boot stock android tv ROM & custom ROM with full android support??
Click to expand...
Click to collapse
You will need to put full android kernel + ram disk in RECOVERY partition and put full android file system in external SD card (or USB drive) and use the trick to switch between stock SATV and alternative OS at power up.
The ram disk should have init file to load file system from external SD or USB drive.
The kernel for alternative OS should be compatible with stock SATV boot loader and device tree.

im sorry is there a guide i can follow as i partially understand what you mean but i have no idea how to do it, but would love this as i have the same adapter so can do the trick hopefully

I can't make this properly work.
Any news about U-boot? Want to use L4T24 and stock Android together smoothly.

I'd like a solution to dual boot too...

[Q]E988 bricked

I have bricked lg e988 indonesia firmware rooted,updated to kitkat 4.4.2,cwm 6.4.0.4
Due to some issue I factory reset from settg menu and the phone rebooted to cwm recvry mode
I tried to rebootd to system but fail
I tried to flash stock rom via adb sideload but fail too so does with lg flash tool
So I thght smtg wth cwm then I tried to flash twrp loki 2.6 and then stuck to lg logo only until now
Pls help

You're still soft bricked, just force your device into download mode and use LG Flash Tool to return back to stock and start again.

ShadySquirrel said:
You're still soft bricked, just force your device into download mode and use LG Flash Tool to return back to stock and start again.
Click to expand...
Click to collapse
Thank you for the respond. Mind if you share me on how to force my device into download mode?
I have tried the power + volume keys combination but nothing happened, back and stop at lg logo
Before i flash the twrp, i tried the LG Flash Tool, but i wont recognize the phone, something like usb connection issue

hotmatua.parulian said:
Thank you for the respond. Mind if you share me on how to force my device into download mode?
I have tried the power + volume keys combination but nothing happened, back and stop at lg logo
Before i flash the twrp, i tried the LG Flash Tool, but i wont recognize the phone, something like usb connection issue
Click to expand...
Click to collapse
If I remember correctly (please check threads here, it's been a long time since I've used this device, so memories are fading), download mode is activated when you press Volume Up (or both of volume buttons) and insert USB cable. I know that E98x has some strange button sequences, like rebooting to recovery is a two step operation (Volume Up + Power until navbar blinks, then power button twice, that's the only way mine wanted to boot into recovery), so please check around.
As far as USB connection issues, don't use USB3+ ports and if you're on Windows 8.1+ and later, run with Administrator privileges. I never experienced that one (used LGFlashTools from inside VirtualBox running Win XP for all my needs, I'm not a Windows user), so can't really help much but forums are full with explanations how.

ShadySquirrel said:
If I remember correctly (please check threads here, it's been a long time since I've used this device, so memories are fading), download mode is activated when you press Volume Up (or both of volume buttons) and insert USB cable. I know that E98x has some strange button sequences, like rebooting to recovery is a two step operation (Volume Up + Power until navbar blinks, then power button twice, that's the only way mine wanted to boot into recovery), so please check around.
As far as USB connection issues, don't use USB3+ ports and if you're on Windows 8.1+ and later, run with Administrator privileges. I never experienced that one (used LGFlashTools from inside VirtualBox running Win XP for all my needs, I'm not a Windows user), so can't really help much but forums are full with explanations how.
Click to expand...
Click to collapse
Thank you very much...now the phone is back to initial state. This what i've done:
1. Download LG Flash tool from http://lgflashtool.com/
2. Download LG USB Drivers from http://lgflashtool.com/
3. Install LG flash tool and LG USB Drivers
4. Plug usb cable to phone
5. Hold volume buttons and then plug the usb cable to PC (i use win 10)
6. Voila, the Download Mode icon is showed up
7. Run LG Flash Tool (Administrator privilege) & follow the instruction (i use e988 v20c stock firmware)
8. Phone back to normal (only if you use the correct stock firmware)
A very big thanks to ShadySquirrel
Hopefully this thread can also be used as reference for anyone who has the same issue as i had

Unable to boot Surface 2 RT - stuck on Windows Recovery

I have an old Surface 2 RT from my parents here, which I wanted to rejuvenate for my kids. I had reset it to the factory settings, but that process failed and the device ended up not booting anymore. Using some command line wizardry with dism, booted from USB, I was able to get Windows 8.1 back on the device. Because I was already working on it, I wanted the put Windows 10 on it, using this guide.
Step 1 went fine - I downloaded the recovery image
Step 2 - installing patched Windows RT image went fine too
Step 3 is where issues began
I was able to execute the "disabling UAC" step
When installing the secure boot policy and rebooting, I got an error that the secure boot policy could not be installed.
Because of this, I executed this step - by changing some files on the EFI partition
Now the device does not boot anymore because of error 0xc0000225 by which it cannot find "winload.efi" or it contains errors. Pressing the "WINDOWS KEY=recovery" it says the same error code but with a different description "A required device isn't connected or cannot be accessed". Eventually it reboots on its own and shows the error again, after the Surface boot logo.
I'm trying to follow the troubleshooting steps but the tablet does not boot from USB (anymore)
I properly safely eject the FAT32 formatted GPT partitioned USB drive of 4GB. I also tried a different USB stick of 8GB.
I use the volume down method in an attempt to get it booting, however, it always ends up at the same message. It does read the USB drive, because the light flickers a bit, but it doesn't act on it.
I cannot boot to UEFI either: I press power and volume up - it does not turn on. I am able to turn it on without the volume up button pressed however - but it does not boot of course.
My feeling is that it has forgotten that it needs to boot from USB, but I can't access the UEFI settings either. Besides, it often needs the "10 seconds power button" trick to even turn on.
What steps can I follow to at least get some more life out of it - or is it completely crapped out?

That EFI modification is for booting Windows 10 only, won't work if you have 8.1 installed instead of 10, to do the unlock you must not enter a Microsoft account or do any upgrade.
The Surface RT and 2 are very finicky about what USB they want to boot from power off, basically I have over 10 USB sticks, among which 4 are 4GB or smaller, the Surface RT and 2 only boot from one of them, which is a no brand Chinese one as well.
So basically just get the recovery image from Microsoft then try a lot of sticks till one boots.

Okay, I guess I need to scavenge some USB sticks

Use a SanDisk Ultra 3.0 drive. Worked best for me on my 1st and 2nd gen Surface RTs. Regular cruise gilded work fine, but the ultra 3.0 is better since it has better transfer rates and whatnot.

I only have three: a cheap marketing one of 4GB, a USB stick with SD card slot, and a 2GB one
But the weird thing is that I also had some connection issues in Windows itself, when it still was working. The USB sticks rapidly connected/disconnected sometimes - but I did not have this issue with the USB keyboard I plugged in. Still, perhaps the USB port is busted.