Hi,
have to change my dell streak. The new one is already at home, have to send back the old one. problem is a often not working display (calibration does not help)
So my second problem is that the USB-Port does not worl since half a year. No promlem, I charge the battery outside.
But I don´t know how to go back to stock.
Cannot flash any pkg because I have a custom recovery which wants a update.zip.
Any ideas for me ?
Mike
solved
Hi
after hours I found a way to flash a other recovery with clockworkmod 4.3.3.0.
http://forum.xda-developers.com/showthread.php?t=1201584
flashed official recovery and then I could flash update.pkg from sdcard
Now I can send the old one back
Related
Hello All,
I was wondering if any of you were able to recover from this particular error:
I have a Qtek 1010 which I upgraded to ROM 3.16 and RS 3.19. I was really curious about ROM 3.15.15 as I had heard so much about it on the forums so I got my hands on a copy and tried to upgrade.
First, the Upgrade utility refused to work because I was trying to flash an older ROM with and already existing newer ROM. So I resorted to the Bootloader way. I backed up the existing Bootloader and ROM Image and wrote the 3.15.15 ROM back onto the SD Card. Unfortunately, I wrote the CLoader_usb.nb that came with the Upgrade Utility back onto the SD card. I booted up and flashed the ROM with the SD card, did a cold boot and nothing happens.
I charged the phone until the LED was a steady green and tried again. Nothing. I did note that I get a quick red LED flash whenever I press the Cold Boot button the second time, for example: press [red flash], press [no flash], press [red flash], etc.
If anyone has ever come across this problem and managed to undo it, please let me know.
Anyway, I guess it was my own fault, but it was not too clear on the website how to rewrite the bootloader because the example graphic says 5-15.nb0. So all you guys out there who are just getting into flashing you ROM the bootloader way, make sure you use the Boot Image that you backed up and not any other (unless you have a new Boot Image that you want to upload)
See you guys around.
I have exactly the same thing. See here: http://xda-developers.com/phpBB/viewtopic.php?t=3284
Have you found a solution yet?
CLoader_usb.nb does not contain a bootloader, so if you wrote that over the bootloader, you probably have permanently damaged your device.
you would have to look into this for a possible solution http://xda-developers.com/jtag/
Your guys' XDA are dead. How could your guys wrote "CLoader_usb.nb" to overwrite to bootloader!
Only hardware solution could bring the life back (I can help)!
If your phone is still on warranty, you could send back to them to repair or replace!
Please note, flashing is dangerous for newbie!
When I first became active, I rooted my phone, I made a recovery off the original recovery rom. I updated to the what my phone says is the unofficial modaco rom v1.3 + an update
+ a theme.... bu then me and my girl split and my recovery images were on a flash device she had. I see some stuff about an updated version of recovery... talk of radio's amongst other things.
I'm assuming I just most likely need to flash back to an original root and then possibly the instructions I need to get the new recovery image as well as the 2.0 stuff on my phone. <--- is this basically what I need to do???
Cloned2 said:
When I first became active, I rooted my phone, I made a recovery off the original recovery rom. I updated to the what my phone says is the unofficial modaco rom v1.3 + an update
+ a theme.... bu then me and my girl split and my recovery images were on a flash device she had. I see some stuff about an updated version of recovery... talk of radio's amongst other things.
I'm assuming I just most likely need to flash back to an original root and then possibly the instructions I need to get the new recovery image as well as the 2.0 stuff on my phone. <--- is this basically what I need to do???
Click to expand...
Click to collapse
Flash a new recovery....fisrt things first
Then do factory data wipe from recovery.
You should probably reformat your SD card...
Wipe Dalvik....
then flash any of the good ole' zips that are up now..
Personally before I do any more flashing I am waiting on sprint release OR this new "Toasts Awesome Sauce" I see in another thread...if it blows everyone else away speed wise....I hope they got OC working.
Only reason I am waiting for an official sprint is because I am sick of wiping my phone ~ to lazy to back up ~.
Cloned2 said:
I'm assuming I just most likely need to flash back to an original root and then possibly the instructions I need to get the new recovery image as well as the 2.0 stuff on my phone. <--- is this basically what I need to do???
Click to expand...
Click to collapse
You don't have to install the new recovery to flash the 2.x ROM's. However, the new RA 1.6.2 was updated and had some bugs fixed, with also a little more added features, so it's probably worth your time to download and flash.
To flash a 2.x ROM, just do as you did before, find one you think you might like, download it and then copy it to your SD Card, after that its a matter of Nadroid back up and then flashing the new ROM.
thanks for the heads up guys.
I just couldn't be sure if there were things that needed to be changed outside of just flashing the new roms.
Back when i was more active I recall there being some roms that you couldn't flash from but a factory reset will revert me out of my modoca flash so that, that problem doesn't potentially crop up?
Whats up everyone, quick help here. I got a hd2 from someone and they tried to flash the phone to dual boot android on it. The guy was unsuccessful in doing so as a result the phone now freezes when it boots up and i would have to take out the battery to turn it off.
Do I have to flash the phone back to the original windows 6.5 rom to resolve this?
any help is appreciated
Depends on what you finally want to have on that device.
If you want to go back to WinMo 6.5 as major OS, it certainly is the easiest way just to flash a stock ROM.
If you still want to continue with a NAND Android build, maybe it´s enough to check the versions of SPL, Radio ROM, and MAGLDR - as well as the Android ROM that was flashed. Could have been a bad flash after all.
But since your data is extremely meager, no way to give a generic and easy hint.
thanks for the incite..first i want to get it bak to factory settings so i will want to flash it back to the original rom.then ill look into flashing it myself with the droid rom without windows..no dual boot.
do you have a link i can follow to flash it back to the original windows rom?
same problem Please help
Hello there I was the same problem with my HTC, I can't flash it back to the original rom. It's just frozen at the boot loader... What should I do? It's not recognize on my pc...
what do you mean frozen at the bootloader? it won't recognize if you plug in usb at all?
Hi, I have recently bought HTC Wildfire, but next day I realised that there's no sound in my earphone. I can only talk on "normal speakers", or via headphones.
I've heard about some hardware problems with mini jack or something like this, but doesn't know what to do with this.
I couldn't get you. You mean that the speaker you use to hear other people when calling (that is, the 2 silver speakers right above the HTC logo on the front), is that not working?
In that case, I don't think its a normal / known issue, and would recommend you send it for repairs under warranty.
(I am assuming you have never rooted and are on the Stock ROM - Not that rooting should cause issues like these, though)
I found similar problem here: http://forum.xda-developers.com/showthread.php?t=267653, but for me, it's not working...
Unfortunately I rooted my phone first day, but now I changed everything (except from recovery) to stock. Do you think it'd be possible to take phone and ask for warranty and repair?
That's the original XDA II, don't think the procedures for that will be applicable to the Wildfire, and it indeed seems like a hardware fault.
Getting rid of the Custom Recovery is easy. Flashing a RUU will get back your Stock Recovery. Perform it, then definitely send it for repairs under warranty.
Ok, I got back to original ROM (2.2.1) and HBOOT 1.0001.01.
But I still have got custom recovery, and the app You listed doesn't work.
I didn't list any app :/
What do you get when you run an RUU? I hope you obtained one from here:
http://shipped-roms.com/index.php?category=windows mobile&model=Buzz
Yes, sorry, my fault, I was thinking about RUU.
Which version should I choose?
You can choose the RUU_WWE 2.22.405.1 one. (EXE file). I am assuming your phone is unbranded and is a non regional device.
I don't know how to do this, sorry.
I tried 4 different RUU, each time I had different bug - once it told that phone is not connected, then the battery was "below 30%" (although it wasn't), then it finally reinstalled hboot, but then it had some other USB Cennection Problem, and couldn't finich the installation.
What is it all about?
I'm running Win 7 x64.
Extract the rom.zip from the RUU, there is a video tutorial here (Performed on Windows 7, so should definitely work for you)
http://www.youtube.com/watch?v=PZe8HAFm3eU
Once you extract it, rename it to PC49IMG.zip, place on the root of your SDCard, and Restart your device in Bootloader mode. (Turn off, and then press Vol Down + Power simultaneously). It will scan the SDCard for the above file, and initiate the install.
But remember - flashing an RUU will format everything. Make sure you have everything backed up.
Thanks man, that worked!
Hey guys,
I was running CM 7.1 on my devy without problems for a year till my speaker broke yesterday. I wanted to return to stock to send it for repare on monday but somewhere I made a huge mistake.
To make a long story short, after trying all sorts of roms, I am stuck at the JORDN_U3_97.21.51.sbf rom. It is the only one that even boots! The other ones result in a dead black screen and I'm feeling lucky that I still even can use rsd-lite to get the 97.21.51 back....
What to do? Which retail version can I use? I have a dutch phone and had official Froyo before I installed CM 7.1. I already tried all ROMS from germany, western europe and [email protected] http://sbf.droid-developers.org/umts_jordan/list.php ...
Also I can't install clockwork mod because market doesn't work @ 97.21.51 and installing it by zip with 2nd init also gave a error... Going back to cm 7.1 by installing it with 2nd init didn''t work eather (bootloop) .
Please some help here to get my phone to retail status so I can send my phone for repair of the speaker!
Greatings Marc
Make sure that u r using the latest RSD and drivers.
Make sure that u r using the latest RSD and drivers.
If still after using the latest RDS u can't boot with the SBF u want, use the one which boots and boot to stock recovery (power + volume down) and clean every thing then try flashing with RSD the SBF u want.
I'm not responsible for any thing happens to your phone. (to don't get blamed if any thing happens)
Thank you for the reply. This is the method I have been trying for the last 24 hours (without result). RSD 4.9 and latest drivers as far as I know.
I think it more has to do with the type SBF. Anyone got a tip which SBF best to use in my situation?
Looks the desktop of your defy after flashing the ORDN_U3_97.21.51.sbf rom like the image in the attachement?
If yes, you have unfortunally flashed the strange eclair SBF with CG5 (bootloader 5).
All normal froyo-SBFs that you will flashing in future have only CG4 (bootloader 4).
If you flash the "normal" froyo-SBFs you will ending in a black screen after RSDLite finished his work. RSDLite will eventually show you, "FLASH suceed". But the flashed Bootloader is lower than CG5 and so you will ending in a dead black screen.
You cannot go back to official froyo, the only thing you can do is to install defy2ndinit, flash a a fitting nandroid froyo for the "strange eclair-SBF" and flash a fixed-SBF of a 4.5.1-128.
The service center will normally repair your speaker for free because the fault is not caused by OS.
But they also will flash a normal froyo for service, and this will ending in a black screen.
EDIT:
You can try this http://forum.xda-developers.com/showpost.php?p=24961811&postcount=2 to take back your defy to a froyo-version which contains Bootloader 6 but still a froyo OS.
@Rattor , thanks for your reply. It doesn't sound to well but at least I have hope again to bring my Devy in normal state... I have send it for repare of the speaker today. I wunder with what firmware it will return...
Got a mail from the service center today. They send the Devy to another (external) repair center... Curious how it will return.. THis could get interesting.... (temporarly on windows mobile 6.5 now (HTC TOPAZ) => going crazy!!!! 2 batterys per day and SOO slow)
BTW. the screen did look like the attached image RATTAR!
Devy back!
Hey,
Today I finally got my devy back! Speaker working and even an official ROM on it. Version.34.164.3.MB525.retail.en.FR.
Let's make a backup first!