Related
Hello people
I think my HTC Hero is what you call softbricked.
When I hold Home + Power on to go to recovery mode I get this single line of text:
Build : RA-hero-v1.5.2
If I hold Home and press power on the text disappears leaving an all black screen. Pressing home + power on again brings the text back.
When I boot normally it just keeps saying "Hero"
I think I did a full wipe, installed VillainROM 6.0.0 and then did a OTA update to VillainROM 6.1.0. I did notice the latest rom being rather slow and hanging sometimes. Then three days ago it froze. I pulled the battery and when I put it back in I was left with what I've described above.
Can't access VillainROM's official website
Another frustrating thing is that w w w. villainrom .co .uk has seemed down to me this whole softbrick-period. But they've announced a new version and no one have commented on their site being down. Apparently I'm the only one who can't access it.
Vol. down + power on
I've never used this boot mode. But it's the only one which seems to work.
HBOOT says Sd checking and all the tests results in:
No image! or No image or wrong image!
FASTBOOT just gives a red box with the white text FASTBOOT in it.
What can i do?
I did a nandroid backup before installing VillainROM 6.0.0 but I can't access recovery mode.
I would like to install the official 1.5 RUU-rom but HTC Sync can't find my phone, neither can adb shell.
I can insert the SD card in my computer and put an update.zip file in the root. Is this a solution? I don't know how to make the phone boot the update.zip file or how this works.
Sorry for this long post. I've been searching the web ever since thursday without any luck. So now I'm just putting all I've experienced out.
I hope someone can help me. I would be very glad
Alright, if you can get to the fastboot screen, this is what you should do:
Plug your hero in fastboot mode into a computer with the latest android sdk installed.
DL the latest recovery for your device: I don't think I can post links yet so search the forum for Amon RA's recovery (1.6.2) and place it in the tools folder of the sdk.
Then:
Open a command prompt (or terminal for linux, idk for mac)
Go to the tools folder with cd
(./)fastboot boot recovery-RA-hero-v1.6.2.img
(./ is for linux ^^,) And that should normally work
From there your best bet is to use Nandroid to recover one of your backups.
Thank you for your response
But I got an error:
Code:
C:\android-sdk-windows\tools\fastboot boot recovery-RA-hero-v1.6.2.img
downloading 'boot.img' ... FAILED (remote: not allow)
finished. total time: 0.010s
The site I downloaded the recovery image from suggestion this installation:
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.6.2.img adb shell mount /sdcard adb push recovery-RA-hero-v1.6.2.img /sdcard/recovery-RA-hero-v1.6.2.img adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img adb shell reboot
I've also tried this but it resulted in: error: device not found
I've noticed how my phone says "fastboot usb" when connected to my computer.
Re: Hangs on boot to recovery mode and normal mode
NessGuard said:
Thank you for your response
But I got an error:
Code:
C:\android-sdk-windows\tools\fastboot boot recovery-RA-hero-v1.6.2.img
downloading 'boot.img' ... FAILED (remote: not allow)
finished. total time: 0.010s
The site I downloaded the recovery image from suggestion this installation:
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.6.2.img adb shell mount /sdcard adb push recovery-RA-hero-v1.6.2.img /sdcard/recovery-RA-hero-v1.6.2.img adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img adb shell reboot
I've also tried this but it resulted in: error: device not found
I've noticed how my phone says "fastboot usb" when connected to my computer.
Click to expand...
Click to collapse
Have you flashed the official 2.1 rom thats been floating round?
Sent from my HTC Hero using Tapatalk
AndroHero said:
Have you flashed the official 2.1 rom thats been floating round?
Click to expand...
Click to collapse
No, I haven't.
Just now I did this:
Code:
C:\android-sdk-windows\tools\adb devices
List of devices attached
And none was shown...
Then I did:
Code:
C:\android-sdk-windows\tools\fastboot devices
HT97TL903447 fastboot
Is this some sort of serial number of my phone?
Re: Hangs on boot to recovery mode and normal mode
Your sd card is seen by your phone or not ?
sebxd said:
Your sd card is seen by your phone or not ?
Click to expand...
Click to collapse
How can I check this?
Hboot says Sd checking and all the tests results in:
Code:
No image! [I]or[/I] No image or wrong image!
The site isn't down, but some people can't get to it due to their DNS setup.
Use 8.8.8.8 and 8.8.4.4 to get it, or go to http://villainrom.grense.no/villainrom.co.uk to get in.
Re: Hangs on boot to recovery mode and normal mode
Mmm if i'm right you can't boot normaly ? It's strange..
Have you tried to boot without your sd card ?
I don't really know what the answer of fastboot means..
anon2122 said:
The site isn't down, but some people can't get to it due to their DNS setup.
Use 8.8.8.8 and 8.8.4.4 to get it, or go to
[url not allowed] to get in.
Click to expand...
Click to collapse
Thanks, but I think I will just stick to this forum. Hope I can get a solution
sebxd said:
Mmm if i'm right you can't boot normaly ? It's strange..
Have you tried to boot without your sd card ?
I don't really know what the answer of fastboot means..
Click to expand...
Click to collapse
Yes, I have tried booting without SD card and without simcard aswell. My simcard is now in a good old Nokia 3310
I have updated the radio earlier
A while ago I updated the radio to this version: 63.18.55.06JU_6.35.09.26
Is that an android 2.1-radio? And is that what's causing "not allow" when running fastboot flash?
What recovery image would I then be allowed to flash? An official one?
Or is it my bootloader (that's SPL, right?) that needs to be flashed to a version that allows the fastboot flashing?
I haven't been able to find a guide on flashing SPL on HTC Hero.
Is this the way to go?
Still need help or is this now sorted?....
It's now working
My phone is now working. I did the following:
1. Connected my phone to a computer with HTC Sync and drivers installed.
2. Started the bootloader on my phone (vol. down + power on, hold until bootloader starts).
3. Pressed back to start fastboot. It said fastboot usb because it was connected to my computer.
4. I tried to install an official 1.5 RUU rom. The phone responded and began the process. It cleared/deleted some caches/files or something. But then my computer and my phone said that the ROM installation had failed and that I should find the right rom.
5. Somehow this cleaned up the phone so I now could boot in recovery mode as I used to (I didn't try a normal boot, so can't say if that worked). I did a full wipe and flashed a custom rom (not VillainROM 6.0.0 ).
Even though VillainROM has made me sad I will now go for VillainROM 10.
Wish me luck
And thanks for your responses.
Brilliant. Just edit the title of your thread to put [SOLVED] on.
And good luck, but i'm sure you wont need it.
EDIT...... Excellent, done it already.
ddotpatel said:
EDIT...... Excellent, done it already.
Click to expand...
Click to collapse
Hehe, yes, even though it's my first post I am a little bit smart
Oh nice ! You have done it ! It is really smart indeed and I'm happy for you !
its not solved for my hero
i tried everything within last two days. but i havent succeess. (i tried your solition too)
i did nondroid backup and then restore. finaly my phone doesnt open.
and after i have given the same your errors (from adb and phone)...
but i havent success..
where i do wrong?
thanks...
Can you explain what you did, what are the errors and when does it appears please
EDIT...... Excellent, done it already.
Click to expand...
Click to collapse
Hehe, yes, even though it's my first post I am a little bit smart
Click to expand...
Click to collapse
Indeed. I'm sorry, I never meant to sound like an ass.
-------------------------------------
Sent via the XDA Tapatalk App
Updated: 5/30/2012
100% NOOBS GUIDE TO FULL UNLOCKING ROGERS/T-MOBILE RM-809 (ALSO WORKS ON RM-803)
Note: this tutorial WILL also de-brand your Rogers/T-Mobile branded phone.
5/30/2012 WARNING (For those who have previously carrier-unlocked their phones): This tutorial involves using Nokia care suite, which WILL relock the carrier lock.
You may use the same unlock code you used previously to carrier-unlock the phone again after the procedure.
As a fellow noob, you might be asking yourself, what is inter-who? full unloc-what?
Interop-unlock = Exactly the same as your regular phone with the ability to install unsigned? XAP (apps)
Full-unlock = 100% developer unlocked phone with ability to install unsigned apps aswell
Earlier this month, when I purchased my ROGERS Lumia 710 (RM-809) I was looking through these forums and found a great community of developers that found methods to interop-unlock and full-unlock the Lumia 710.
However, there was no clear-cut step-by-step tutorial on how to do it.
To make matters worse, most of the available vague tutorials were for the RM-803 model for the 710, and not the RM-809.
I am making this tutorial to clear the confusion for noobs (such as myself) and offer a complete step-by-step tutorial to flashing your Lumia 710.
This tutorial is 100% based on MY EXPERIENCE flashing my RM-809, I CANNOT guarantee you will get the same results that I did.
I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE! READ ALL THE STEPS BEFORE ATTEMPTING THIS TUTORIAL!!
Instructions:
1. First you must determine which bootloader you have, there are two different bootloaders, NOKIA DLOAD, and QUALCOMM.
Nokia Dload = Locked Memory (Unflashable)
Qualcomm = Unlocked Memory (Flashable)
The one we need is the Qualcomm bootloader.
In order to determine which bootloader you have on your phone, you must first power down your phone with NO wires plugged in, then while holding the VOL + button, plug in the usb cable, remain holding the VOL + buton until you feel a short vibration, then let go.
Your (windows) computer will start trying to install drivers, double click on the little moving icon in your task bar to bring up the driver software installation window.
Note: If you previously tried to determine your bootloader, windows might not try to install the drivers, instead click start --> Devices and printers, it should be listed there.
If it says Nokia DLOAD, well you have Nokia Dload, if there a bunch of things getting their drivers installed, one being Qualcomm, then you have Qualcomm xD.
IF YOU HAVE QUALCOMM WINDOWS WILL TELL YOU THAT YOU MUST FORMAT THE DRIVE, DO NOT I REPEAT DO NOT FORMAT THE DRIVE, IF YOU DO THE PHONE WILL BECOME BRICKED!
Now, you might be asking yourself, "Okay, so I have Nokia DLOAD, Am i out of luck?". The answer is step 2, where we downgrade your Nokia DLOAD into Qualcomm. (If you already have Qualcomm skip to step 3)
2. This was by-far the most frustrating step about my RM-809, I had no idea if flashing with the RM-803 procedure would brick my phone. I am going to guide you step by step to downgrade your Nokia DLOAD into a Qualcomm bootloader.
Here it goes:
2.1: The first thing you have to do is download a program called Nokia care suite: HERE
And the Qualcomm files: Part 1 & Part 2
2.2: Extract both, and install Nokia care suite (I'm going to assume you can do this basic task)
2.3: I'm not sure if you have to do this for windows 32-bit, but with windows 64-bit you must navigate to: C:\Program Files (x86)\Nokia\Nokia Care Suite\Drivers
2.4: Inside that folder you'll find "WinUSB Drivers x64.msi", install it.
2.5: The next step is to place your extracted Qualcomm files into the appropriate location.
2.6: Copy-paste the extracted RM-803 folder (Should have a bunch of files inside) into this directory:
C:\ProgramData\Nokia\Packages\Products
Note: the "ProgramData" folder might be hidden, to view hidden folders, Press start, search "folder options", open Folder Options, click the "view" tab and press the radio button "Show hidden files, folders, and drives"
2.7: The next step is to open the nokia product support tool.
(I think there was a bug in my version of nokia care suite as i couldnt find it in the start menu, I had to open it manually from this location: C:\Program Files (x86)\Nokia\Nokia Care Suite\Product Support Tool For Store 5.0\ProductSupportToolForStore.exe)
2.8: Once you have the product support tool open, make sure the drop down on the upper left says "No connection" and "Automatic product selection" is enabled".
Note: Phone should NOT be plugged in at this point
2.9: Click file.. "open product".. and choose "RM-803" and click open
2.10: Click Programming on the lower left and click "recovery".
2.11: Click on update list and a list item called "Nokia 710 RM-803 Country variant Russia RU BLACK_BLACK V3" should come up.
2.12: Click "Start" (Phone should not be plugged in at this point)
2.13: It will say that it has lost connection with your device, this is where you power down your phone, hold VOL+ and plug USB until you feel a short vibration, and let go.
2.14: Click "Retry" and it should begin Flashing your bootloader (It will like like 5 mins)
2.15: When it is complete, unplug your phone and it will reboot into a russian language, press the right button and choose english.
2.16: That's it, you now have a Qualcomm bootloader.
3. The next step involves installing linux.
Linux is a free and open source operating system. The reason we need linux is because we need the built-in "dd" command, which helps us flash the phone, and is not readily available nor stable in windows. You can use any distribution of linux, however in this tutorial i will be using Ubuntu.
Note: I have not heard of a single success story of someone using dd in windows, everyone who has tried it has bricked their phone. You have been warned.
3.1: Go HERE and press "Start download". (It's the ubuntu installer for windows)
3.2: Install Ubuntu side-by-side with windows (Just follow the installation wizard it's very easy to follow)
Note: Now that you have Ubuntu installed you need to BOOT into Linux. You'll that if you restart your computer, you'll get a purple screen with different Operating systems to boot from, one being windows.
3.4: Highlight "Ubuntu" (I think it's the first one) from the list on the purple menu (Don't choose recovery), and press enter.
3.5: That's about it, Ubuntu will begin to load and you'll eventually be inside the operating system.
Note: To switch between ubuntu and windows just restart the computer and choose from the purple menu
Note: If you are a complete noob and do not understand step 3 read THIS
Also: Before you boot into Ubuntu, download and extract the latest version of the Rainbow mod custom firmware for the Lumia 710 to a USB drive in windows:
LUMIA 710 RAINBOW MOD FULL UNLOCK FIRMWARE BY LUCIFER 3006
Now boot into Ubuntu and place it in your Ubuntu home folder as shown:
{
"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"
}
4. Now that you're in Ubuntu, you're ready to backup and flash your phone, however, you must first determine the partition letter of your phone.
4.1: To do this, first open up a terminal window (ctrl + alt + t)
4.2: Next you must type the following command into the terminal window and press enter to raise your privileges:
Code:
sudo su
Note: You may need to enter your password to raise privileges
4.3: For this step make sure your phone is NOT plugged in.
Type in the following command to list all of the detected partitions:
Code:
ls /dev/
Note: You may need to expand the terminal window so you can see all of the partitions.
You should get something like this:
What we want to do is find all of the partitions that start with "sd" We need to take note of their third letter, and the number of partitions.
For example, in my case, I had two devices that start with "sd", "sdA" with 1 partition, and "sdB" with 6 partitions.
Note: Every computer will have different combinations of third drive letters and partitions.
Because my phone is unplugged, I can take note that neither of these devices is my phone.
4.4: Now plug your phone in to your computer in Qualcomm mode (Power down.. Hold Vol+ and plug in USB)
and you might get this popup window:
Just press X and close it.
Go back to the terminal window and type the same command as before:
Code:
ls /dev/
You should get something like this:
We can clearly see a new device that starts with "sd" has appeared after plugging in the phone in Qualcomm mode.
Note: If the new sd device is your phone, it MUST show exactly 9 partitions.
We now have our partition letter! (In my case its c)
Note: I'll repeat this again, your partition letter might NOT be c, every computer is different.
4.5: Now that we know our partition letter, we can determine the partition to backup/flash to.
Just plug in your partition letter in-place for X into this: sdX9
In my case, my partition that I must backup/flash is: sdc9
5. Now that we have determined the partition, we are now ready to back it up before flashing.
5.1: If you do not already have a terminal window open from the last step, open one now (ctrl + alt + t).
5.2: To back up the partition, enter this command into the terminal, replacing X with your partition letter determined in step 4:
Code:
dd if=/dev/sd[B]X[/B]9 of=backup9.nb
For example, because my partition letter is c I will replace X with c and type in this command:
Code:
dd if=/dev/sd[B]c[/B]9 of=backup9.nb
Note:
The dd command has no progress bar, it will be a white blinker until it is done.
The dd command will take a while 15-30 minutes to backup your entire partition.
The backup9.nb file will be around 8GB in size and will be stored in the Ubuntu Home folder.
5.3: Store backup9.nb somewhere safe! You will need it if your phone gets bricked!
6. The last step is to finally full unlock flash the firmware.
6.3: Now open up a terminal window if not already open (ctrl + alt + t)
Enter this command to elevate privileges:
Code:
sudo su
Note: You may need to enter your password to raise privileges
6.4: Now using the partition we obtained in step 4 (In my case: sdc9) use this command to flash your phone with the unlocked firmware:
Code:
dd if=os-new.nb of=/dev/sdX9
Replace X with your partition letter (In my case it's c)
so in my case I would enter:
Code:
dd if=os-new.nb of=/dev/sdc9
Note:
The dd command has no progress bar, it will be a white blinker until it is done.
The dd command will take a while 15-30 minutes to flash your entire partition.
6.5: Once it is done flashing, unplug your phone and exit Qualcomm mode by removing and replugging in your battery.
6.6: You must now do a hard reset by:
Holding POWER + VOLUMEDOWN + CAMERA until you feel the phone vibrate.
After that, RELEASE power button but KEEP HOLDING VOL- and the camera button for five or more seconds.
This will trigger the hard reset and your phone will start.
6.7: That is all, you now have a fully unlocked Lumia 710.
7. Now that you have a fully unlocked phone, you'll notice that if you try to sign in with your windows live ID, it will ask you for an activation code.
7.1: You can obtain an activation code from Microsoft here: http://support.microsoft.com/contactus/cu_sc_selector_chat?ws=support#
7.2: Click on "General Inquiries about Microsoft Products and Services or Genuine Advantage Questions"
7.3: Now you'll need to chat with the Microsoft representative; tell the person that you accidentally did a hard-reset on your phone and it's now asking for an activation code.
7.4: Once you get an activation code, enter it in on your phone, and you're good to go.
8. How to install XAP apps...
To install XAP apps to your windows phone, You can do either of these two things:
A. Download an XAP app on the phone browser and install it from there.
-OR-
B. Deploy it to your phone from your pc.
In this step we will cover how to do procedure B.
Note: There are many custom XAP installers on xdadevelopers, however most are outdated/buggy, It's best to follow these steps with the official SDK.
8a. Download and install Windows Phone SDK 7.1
Note 1: Zune must be installed and OPENED before proceeding.
Note 2: The phone must be CONNECTED to zune and not in the lock-screen.
8b. Open the XAP deployment tool from here:
Start --> All Programs --> Windows phone developer tools --> Application Deployment
8c. In the Target drop-down box, select Windows Phone Device.
8d. Click Browse and locate the XAP file that you want deploy to the phone.
8e. Click the Deploy button. (It will take some time depending on the file-size)
Done.
nice!! that might help me to unbrick my lumia 800 . i cannot power it on. can you tell me the links to downlod the Qualcomm files and the nokia care suit ?
i bought my lumia yesterday and now its dead please help!
lenarass said:
nice!! that might help me to unbrick my lumia 800 . i cannot power it on. can you tell me the links to downlod the Qualcomm files and the nokia care suit ?
i bought my lumia yesterday and now its dead please help!
Click to expand...
Click to collapse
Sorry but Nokia care suite only works with Nokia DLOAD, and you cannot downgrade a lumia 800 from DLOAD to Qualcomm.
Do you have Qualcomm on your lumia 800 right now?
How did you manage to brick it anyways?
nima158 said:
Sorry but Nokia care suite only works with Nokia DLOAD, and you cannot downgrade a lumia 800 from DLOAD to Qualcomm.
Do you have Qualcomm on your lumia 800 right now?
How did you manage to brick it anyways?
Click to expand...
Click to collapse
my lumia 800 is Qualcomm. i turned it off then pressed volume+ and power button and my pc detected my lumia as drive c. i press no to NOT format my drive and then i open cmd. i downloaded the dd files and tried to flash the new software on my lumia with dd command. i think it was sucessful. cmd wrote some values in: and out: then i hardreset my phone and now its dead. i put it for 2 hours on wall charger(still on) and i just pressed power button and nothing at all....any clue what to do ?
i have seen that post http://forum.xda-developers.com/showthread.php?t=1457341 and i think i will be able to unbrick it BUT i need the files i asked before.. if u cannot post them here can u email them to me at [email protected] ?? PLEASE!?
lenarass said:
my lumia 800 is Qualcomm. i turned it off then pressed volume+ and power button and my pc detected my lumia as drive c. i press no to NOT format my drive and then i open cmd. i downloaded the dd files and tried to flash the new software on my lumia with dd command. i think it was sucessful. cmd wrote some values in: and out: then i hardreset my phone and now its dead. i put it for 2 hours on wall charger(still on) and i just pressed power button and nothing at all....any clue what to do ?
i have seen that post http://forum.xda-developers.com/showthread.php?t=1457341 and i think i will be able to unbrick it BUT i need the files i asked before.. if u cannot post them here can u email them to me at [email protected] ?? PLEASE!?
Click to expand...
Click to collapse
dd in cmd? You used dd in windows or linux?
The phone could possibly still be in Qualcomm mode, in my case I had to remove the battery, and put it back then, THEN do a hard reset.
Although if you used dd in windows, you could have possibly messed something up, so i don't recommend leaving Qualcomm mode until you use dd successfully in linux.
And one more thing, Nokia care suite will NOT work with your Qualcomm lumia 800, in the link you posted the person had Nokia DLOAD.
If you still insist on using it, I sent you the link via PM
Edit: did you use dd to the right partition? sdX9?
If this helps anyways, this was one of my post in one of my other thread. Might help people understand the dd command more.
I will try to explain this as best as I can, to make sure I am correct, and to try to clarify the command for other people confused.
dd if=./os-new.nb of=/dev/sdX9
"if=./os-new.nb"
This specifies the file path of where your os-new.nb file is. So for example, the location of my .nb file is:
"/home/david/os-new.nb" so I would do "if=/home/david/os-new.nb"
of=/dev/sdX9
This specify the location of where you are copying the .nb file to.
For this, you would just have to replace the "X", and only the X, which is in terms of the letter your device turns up in linux as. This was the part I got confused on. It showed up as sdb3 on my machine, which I thought that I would have to replace the entire sdx9 with it.
To find out the letter, in terminal, type in
"df"
It will lists all your active drives. Mine shows up as the latter B, under the name windows device. So I would do
"of=/dev/sdb9"
So to put it all together, the command I would type in is:
"dd if=/home/david/os-new.nb of=/dev/sdb9"
Am I correct?
And also, if there a way to flash your lumia from within windows? Cause it still shows up as a USB drive in windows like usual but it refuses to show up in ubuntu.
Click to expand...
Click to collapse
Nice post BTW.
nima158 said:
dd in cmd? You used dd in windows or linux?
The phone could possibly still be in Qualcomm mode, in my case I had to remove the battery, and put it back then, THEN do a hard reset.
Although if you used dd in windows, you could have possibly messed something up, so i don't recommend leaving Qualcomm mode until you use dd successfully in linux.
And one more thing, Nokia care suite will NOT work with your Qualcomm lumia 800, in the link you posted the person had Nokia DLOAD.
If you still insist on using it, I sent you the link via PM
Edit: did you use dd to the right partition? sdX9?
Click to expand...
Click to collapse
i use dd on windows. thats the link i used : http://forum.xda-developers.com/showthread.php?t=1587650
and http://www.chrysocome.net/dd
you said you remove the battery from your phone. my phone is lumia.. i have to remove the screws to do that. if i do so is it possible to work ?
also now u have the link i used to flash my lumia so you might hv a clue how to fix it
thanks and please send me the links and i will hv a try and inform you
thanks again!!
lenarass said:
i use dd on windows. thats the link i used : http://forum.xda-developers.com/showthread.php?t=1587650
and http://www.chrysocome.net/dd
you said you remove the battery from your phone. my phone is lumia.. i have to remove the screws to do that. if i do so is it possible to work ?
also now u have the link i used to flash my lumia so you might hv a clue how to fix it
thanks and please send me the links and i will hv a try and inform you
thanks again!!
Click to expand...
Click to collapse
It was a terrible idea to use dd in windows..
Just to be clear, Are you still able to access Qualcomm mode? Does windows still ask you to format when you plug in your phone?
And one more thing, what EXACT dd command did you use in windows? I need to know what partition you flashed!
nima158 said:
It was a terrible idea to use dd in windows..
Just to be clear, Are you still able to access Qualcomm mode? Does windows still ask you to format when you plug in your phone?
And one more thing, what EXACT dd command did you use in windows? I need to know what partition you flashed!
Click to expand...
Click to collapse
I flashed my phone incorrectly. Shows up in windows, asking me to format, but not in Ubuntu though.
Useless to show up in windows as I can't really do anything about it.
nima158 said:
It was a terrible idea to use dd in windows..
Just to be clear, Are you still able to access Qualcomm mode? Does windows still ask you to format when you plug in your phone?
And one more thing, what EXACT dd command did you use in windows? I need to know what partition you flashed!
Click to expand...
Click to collapse
i went into cmd then into dd folder and typed dd if=./os-new.nb of=c
now i hv my lumia disassembled and i removed the battery. i will try to power it on after connecting the battery back in.. and no im not able to see the nokia drive in my computer :// as i press the power button and my nokia does NOTHING
edit: removed the battery, put it back on press power button, nothing... connected to pc .. nothing..
this guy from the post i hv shown u says that dd works under windows and he gave the link i hv shown u....
HE IS WRONG right ?? and he made me brick my lumia .....
wardoc22 said:
I flashed my phone incorrectly. Shows up in windows, asking me to format, but not in Ubuntu though.
Useless to show up in windows as I can't really do anything about it.
Click to expand...
Click to collapse
You might be inluck, try this command in the terminal (With phone in Qualcomm mode):
Code:
ls /dev/
If you see a drive with 9 partitions, then you can go back and reflash the incorrect partition:
lenarass said:
i went into cmd then into dd folder and typed dd if=./os-new.nb of=c
now i hv my lumia disassembled and i removed the battery. i will try to power it on after connecting the battery back in.. and no im not able to see the nokia drive in my computer :// as i press the power button and my nokia does NOTHING
edit: removed the battery, put it back on press power button, nothing... connected to pc .. nothing..
this guy from the post i hv shown u says that dd works under windows and he gave the link i hv shown u....
HE IS WRONG right ?? and he made me brick my lumia .....
Click to expand...
Click to collapse
Yeah I thought it was stuck in Qualcomm mode, which is why i told you to remove the battery, but it appears to be completely dead.. Maybe try another hard-reset? (Hold power + VOL- + camera) until it vibrates, then let-go of power but keep the other two for 5 more seconds until you see the phone start-up..
Edit: The guy said that it was untested, there's another thread where people are saying how they bricked their phones using the windows dd..
nima158 said:
You might be inluck, try this command in the terminal (With phone in Qualcomm mode):
Code:
ls /dev/
If you see a drive with 9 partitions, then you can go back and reflash the incorrect partition:
Yeah I thought it was stuck in Qualcomm mode, which is why i told you to remove the battery, but it appears to be completely dead.. Maybe try another hard-reset? (Hold power + VOL- + camera) until it vibrates, then let-go of power but keep the other two for 5 more seconds until you see the phone start-up..
Edit: The guy said that it was untested, there's another thread where people are saying how they bricked their phones using the windows dd..
Click to expand...
Click to collapse
I did the ls /dev/ thing and there were wayy too many drives with 9 partition that showed up.
So then I just did diskutil list and I managed to get it to show up. Now if anyone can upload their unlocked lumia 710 partition 3 for me :S
wardoc22 said:
I did the ls /dev/ thing and there were wayy too many drives with 9 partition that showed up.
So then I just did diskutil list and I managed to get it to show up. Now if anyone can upload their unlocked lumia 710 partition 3 for me :S
Click to expand...
Click to collapse
I'll see if I can upload mine either today or tomorrow..
nima158 said:
I'll see if I can upload mine either today or tomorrow..
Click to expand...
Click to collapse
mmmm, thanks.
can you also pm me the Qualcomm files too please?
by Qualcomm files you mean the lumia firmware right?
thanks again!
lenarass said:
can you also pm me the Qualcomm files too please?
by Qualcomm files you mean the lumia firmware right?
thanks again!
Click to expand...
Click to collapse
I don't have to, this is my 8th post!
Let me edit the original post..
nima158 said:
I don't have to, this is my 8th post!
Let me edit the original post..
Click to expand...
Click to collapse
Edit: Yes, I mean the Lumia 710 Qualcomm files used to downgrade your Nokia Dload
Edit 2: Fail.. edited the wrong post..
oh i see that rm803 is for lumia 710
i have lumia 800 rm801..
where can i download the files for 800?
thanks
lenarass said:
oh i see that rm803 is for lumia 710
i have lumia 800 rm801..
where can i download the files for 800?
thanks
Click to expand...
Click to collapse
There are none,
It's currently impossible to downgrade a lumia 800 bootloader from Nokia DLOAD to Qualcomm.
my friend, thanks for the help.
i want to inform you that i left my iphone on charger over night and while im pressing the power button my phone doesnt vibrate or power on...its literally dead!
first off, i just wanted to state, before i get ripped into, i have spend the last 1.5 days reading everything i can find on any forum that comes back with search results for my issue. i've tried numerous drivers, different PC's, even a Linux Live CD system.
I cannot get my PC (win 7, 32 bit) to see my TF201 via ADB.
It is installed in the device manager with the "universal naked driver 0.7", and shows up as "Asus Transformer Prime ADB Interface". But whenever i try to connect via ADB to run the fix in this thread - http://forum.xda-developers.com/showthread.php?t=1514088 - i cannot see the device.
I have tried all of the mount/unmount options in CWM. nothing is working for me.
is there anyone that has run into this? And if so, have you found a resolution?
sorry if i'm coming off as the typical noob here, but i really have put in time researching the issue and attempting other fix-it routes before posting up a help thread.
Thanks!!
perch_44 said:
first off, i just wanted to state, before i get ripped into, i have spend the last 1.5 days reading everything i can find on any forum that comes back with search results for my issue. i've tried numerous drivers, different PC's, even a Linux Live CD system.
I cannot get my PC (win 7, 32 bit) to see my TF201 via ADB.
It is installed in the device manager with the "universal naked driver 0.7", and shows up as "Asus Transformer Prime ADB Interface". But whenever i try to connect via ADB to run the fix in this thread - http://forum.xda-developers.com/showthread.php?t=1514088 - i cannot see the device.
I have tried all of the mount/unmount options in CWM. nothing is working for me.
is there anyone that has run into this? And if so, have you found a resolution?
sorry if i'm coming off as the typical noob here, but i really have put in time researching the issue and attempting other fix-it routes before posting up a help thread.
Thanks!!
Click to expand...
Click to collapse
Update****
I was able to get it out of the boot loop, so that it will boot to the splash screen. well following instructions i've found online, when in CWM, i connected through ADB and pushed a copy of cm9.zip up to the internal storage.
yet, whenever i choose "install from zip" in CWM, it never finds the zip file.
i have done it a few times now and it says it copies up completely, but never actually shows up.
syntax i'm using: adb push cm9filename.zip "/sdcard/cm9filename.zip"
it takes about two minutes and gives me confirmation that it pushed x amount of bytes of data for the file, and says its done. I then go back to the tablet in CWM and choose install from sdcard, and it says there are no files.
I'm about ready to throw this thing in the trash and be done with it......
First of all make a small text file and zip it up for a test file that wont take long to push.
Now type adb push test.zip /data/media/
look if the file is showing where you go to install a rom.
If it is showing then push the rom to the same place then install it
flumpster said:
First of all make a small text file and zip it up for a test file that wont take long to push.
Now type adb push test.zip /data/media/
look if the file is showing where you go to install a rom.
If it is showing then push the rom to the same place then install it
Click to expand...
Click to collapse
If that fails, I had the same issue with cwm, I installed twrp via fastboot and haven't had the problem of the file not showing up after adb push. Fustrating I know.... I tired everything I could think of in cwm multiple reboots different usb ports... on an on......
Please HELP CWM Roocovery Loop!!!
perch_44 said:
Update****
I was able to get it out of the boot loop, so that it will boot to the splash screen. well following instructions i've found online, when in CWM, i connected through ADB and pushed a copy of cm9.zip up to the internal storage.
yet, whenever i choose "install from zip" in CWM, it never finds the zip file.
i have done it a few times now and it says it copies up completely, but never actually shows up.
syntax i'm using: adb push cm9filename.zip "/sdcard/cm9filename.zip"
it takes about two minutes and gives me confirmation that it pushed x amount of bytes of data for the file, and says its done. I then go back to the tablet in CWM and choose install from sdcard, and it says there are no files.
I'm about ready to throw this thing in the trash and be done with it......
Click to expand...
Click to collapse
I am having the same exact problem. It started when I tried to restore my stock backup that I made using CWM 5.8.2.0 coming from the CM rom. I am stuck in the CWM recovery screen and cant get ADB to see the TF Prime. I just get error: device not found. How did you manage to push a zip if ADB wasn't seeing your device? I have been looking for a fix for the last week now.
Forget CWM fastboot flash TWRP then load your rom via microsd.....
Danny80y said:
Forget CWM fastboot flash TWRP then load your rom via microsd.....
Click to expand...
Click to collapse
How do I flash TWRP when Im stuck CWM?
hellshavoc said:
How do I flash TWRP when Im stuck CWM?
Click to expand...
Click to collapse
The answer is in the post you quote, did you read it? Fastboot, see on twrp site.
Striatum_bdr said:
The answer is in the post you quote, did you read it? Fastboot, see on twrp site.
Click to expand...
Click to collapse
the problem is whenever it try to fastboot it just keeps saying waiting for device. I can put my TF prime in fastoot mode when I power on while holding down on vol it just goes right to CWM recovery and any adb command gives me no device found and I tried APX mode (holding vol up during power on) and tried to use NVFlash but that just gives me an error device not recognized. I have all the drivers installed. I used the naked drivers .7 and have cleared out all the old drivers too.
hellshavoc said:
the problem is whenever it try to fastboot it just keeps saying waiting for device. I can put my TF prime in fastoot mode when I power on while holding down on vol it just goes right to CWM recovery and any adb command gives me no device found and I tried APX mode (holding vol up during power on) and tried to use NVFlash but that just gives me an error device not recognized. I have all the drivers installed. I used the naked drivers .7 and have cleared out all the old drivers too.
Click to expand...
Click to collapse
you hold the volume down until the screen starts, then you let go and wait
whycali said:
you hold the volume down until the screen starts, then you let go and wait
Click to expand...
Click to collapse
As I stated above holding down Val down while turning on does not bring up the menu it still just boots right into CWM recovery. i have no option for fastboot or anything.
hellshavoc said:
As I stated above holding down Val down while turning on does not bring up the menu it still just boots right into CWM recovery. i have no option for fastboot or anything.
Click to expand...
Click to collapse
No, you hold Vol down + power then when the first screen with sentences appears you release everything DON'T touch anything, after 5 secondes you will end in a screen with three icons, with volume down youu select the usb icon in the middle, then volume up.
This procedure works even on locked devices except that in this case you don't have the usb icon, only the factory reset and cold reboot ones. So it's impossible you don't obtai this screen, it's hardware coded.
It is confusing but just keep trying till you get it!! Once there go to the TWRP site they have the file and the fastboot commands all set in a guide.
I have exactly the same problem than you.
I had the fastboot/adb connection (I used to push the rom by adb), but i tried to install a wrong version on gapps. Since then, I'm stock in the recovery mode without adb/fastboot connection.
If you find a solution for that, pleaze post it !!
Striatum_bdr said:
No, you hold Vol down + power then when the first screen with sentences appears you release everything DON'T touch anything, after 5 secondes you will end in a screen with three icons, with volume down youu select the usb icon in the middle, then volume up.
This procedure works even on locked devices except that in this case you don't have the usb icon, only the factory reset and cold reboot ones. So it's impossible you don't obtai this screen, it's hardware coded.
Click to expand...
Click to collapse
Please guys, help me, i'm desperate, so i was trying to unlock the bootloader and found this thread about L90 D405 which is similar to our phone and i noticed that a recognized developer had created a modified aboot.bin and also a custom recovery.So i pushed the aboot.bin into mmcblk0p6.img and then i reboot the device....which killed my phone. Everytime i try to open it up it shows on the display the screen i was seeing before i rebooted the phone with ADB. I want to say that the USB somehow still recognize the phone because i hear the BEEP when i plug it into the phone.I can't enter neither stock recovery or download mode and also KDZ doesn't work it says that the USB is not recognized, so please help me out. :crying:
Here is the link : http://forum.xda-developers.com/showthread.php?t=2770938&page=31
Rephosix said:
Please guys, help me, i'm desperate, so i was trying to unlock the bootloader and found this thread about L90 D405 which is similar to our phone and i noticed that a recognized developer had created a modified aboot.bin and also a custom recovery.So i pushed the aboot.bin into mmcblk0p6.img and then i reboot the device....which killed my phone. Everytime i try to open it up it shows on the display the screen i was seeing before i rebooted the phone with ADB. I want to say that the USB somehow still recognize the phone because i hear the BEEP when i plug it into the phone.I can't enter neither stock recovery or download mode and also KDZ doesn't work it says that the USB is not recognized, so please help me out. :crying:
Here is the link : http://forum.xda-developers.com/showthread.php?t=2770938&page=31
Click to expand...
Click to collapse
WAIT THE PHONE ACTUALLY REBOOTS the problem is that i don't see the screen but i can tap on it and i hear that beep when i unlock the screen i just need aboot.bin because the adb after all still recognize the device, please someone can give me aboot.bin pleaseee!
Rephosix said:
WAIT THE PHONE ACTUALLY REBOOTS the problem is that i don't see the screen but i can tap on it and i hear that beep when i unlock the screen i just need aboot.bin because the adb after all still recognize the device, please someone can give me aboot.bin pleaseee!
Click to expand...
Click to collapse
Okay this is getting weirder, it booted....and guess what i see the screen rotated 180 but the buttons are working as they weren't been rotated, plus that the resolution is lower, i mean i can see the pixels for some reason.
Rephosix said:
Okay this is getting weirder, it booted....and guess what i see the screen rotated 180 but the buttons are working as they weren't been rotated, plus that the resolution is lower, i mean i can see the pixels for some reason.
Click to expand...
Click to collapse
Okay, i was so desperate that i didn't pay attention there was already a aboot.bin on the forums but the problem is that everytime i try:
-dd if=/sdcard/aboot.bin of=/dev/block/mmcblk0p6 through the ADB it says /sdcard/aboot.bin : cannot open file : aboot.bin doesn't exist.
Any solutions?
Hi Reposix,
if you would tell us the ADB commands you used before we might be able to help.
Did you put the about.bin on external SD? /storage/external_SD/about.bin
Did you push it with adb?
Did you adb shell?
Did you su?
Zaaap
Zaaap72 said:
Hi Reposix,
if you would tell us the ADB commands you used before we might be able to help.
Did you put the about.bin on external SD? /storage/external_SD/about.bin
Did you push it with adb?
Did you adb shell?
Did you su?
Zaaap
Click to expand...
Click to collapse
about.bin was put on the SD with the usb, i used this adb command to patch it : dd if=/sdcard/aboot.bin of=/dev/block/mmcblk0p6
The last two questions are invalid since without i wouldn't have been able to use the previous command.BTW, i fixed by replacing destroyed mmcblk0p6 with the stock one, i asked a guy on the forums to give me one, anyways i appreciate your conscientiousness :good: .
The reasons why I asked is:
dd ist not a an adb command, it is a shell command.
So you did 'adb shell', right?
I was not able to dd a block device without root rights.
So, I had to use the commend 'su'.
You put the about.img to SD, my question was real (external) SD or fake internal SD. This could be a reason why the file was not found.
So, happy that you got your phone fixed.:thumbup:
Sent from my Nexus 7 using XDA Free mobile app
Zaaap72 said:
The reasons why I asked is:
dd ist not a an adb command, it is a shell command.
So you did 'adb shell', right?
I was not able to dd a block device without root rights.
So, I had to use the commend 'su'.
You put the about.img to SD, my question was real (external) SD or fake internal SD. This could be a reason why the file was not found.
So, happy that you got your phone fixed.[emoji106]
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
/sdcard/ is a symlink to /storage/emulated/0/
So, he probably put it at the internal SD.
Sent from my D620R [Stock 4.4.2]
Zaaap72 said:
The reasons why I asked is:
dd ist not a an adb command, it is a shell command.
So you did 'adb shell', right?
I was not able to dd a block device without root rights.
So, I had to use the commend 'su'.
You put the about.img to SD, my question was real (external) SD or fake internal SD. This could be a reason why the file was not found.
So, happy that you got your phone fixed.:thumbup:
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Right..i forgot...i used adb shell just like this :
-adb shell
-su
-dd if=/sdcard/%imagename%.img of=/dev/block/mmcblk0p17
-reboot
And it's aboot.BIN not .IMG(i'm writing with caps so you can notice no offense )
And Vagelis is right, i put it on the internal SD not the external.
Thank you for clarifying this. :thumbup:
May help others with a similar problem.
Zaaap
can you help me too
Rephosix said:
Please guys, help me, i'm desperate, so i was trying to unlock the bootloader and found this thread about L90 D405 which is similar to our phone and i noticed that a recognized developer had created a modified aboot.bin and also a custom recovery.So i pushed the aboot.bin into mmcblk0p6.img and then i reboot the device....which killed my phone. Everytime i try to open it up it shows on the display the screen i was seeing before i rebooted the phone with ADB. I want to say that the USB somehow still recognize the phone because i hear the BEEP when i plug it into the phone.I can't enter neither stock recovery or download mode and also KDZ doesn't work it says that the USB is not recognized, so please help me out. :crying:
Here is the link : http://forum.xda-developers.com/showthread.php?t=2770938&page=31
Click to expand...
Click to collapse
HI my pone is bricked, it's dead
i was trying too root my phone and put twrp on it than it got me in recovery mode but i got frustrated because i didn't know how to select the options so i took my battery out with the hope that my phone would just reboot like normal but it didn"t. now i tried the buttons : home and volume down or volume up and connect with usb it just won't work, can you pleas help me... it does connect to my pc but nothing else
@Teamsvg
Don't you think one thread is enough for your issue?
Teamsvg said:
...it does connect to my pc but nothing else
Click to expand...
Click to collapse
And it connects in which mode? ADB? Recovery? Download? Media?
Have you tried the method I recommended in your thread?
http://forum.xda-developers.com/showthread.php?p=54325341
And if you don't answer questions no one can help!
Zaaap
Zaaap72 said:
@Teamsvg
Don't you think one thread is enough for your issue?
And it connects in which mode? ADB? Recovery? Download? Media?
Have you tried the method I recommended in your thread?
http://forum.xda-developers.com/showthread.php?p=54325341
And if you don't answer questions no one can help!
Zaaap
Click to expand...
Click to collapse
I've got the same problem ; phone is not response to ADB , Download, USB , nothing , when i connect to my pc , nothing happens, the only time i see anything is when i pull the battery and plug in USB the sign of no battery is visible
Any things i can try ?
Tried:
Pulling battery and restart
Starting with volume up + power
Starting LG soft and holding volume up while plugging in usb
Al these things diden't help , still screen stays black and no response from usb on pc...
HELP !!
:crying:
please help i have the same promblem.. i copied wrong aboot.img how did you fix it???
Rephosix said:
Right..i forgot...i used adb shell just like this :
-adb shell
-su
-dd if=/sdcard/%imagename%.img of=/dev/block/mmcblk0p17
-reboot
And it's aboot.BIN not .IMG(i'm writing with caps so you can notice no offense )
And Vagelis is right, i put it on the internal SD not the external.
Click to expand...
Click to collapse
please help i have the same problem.. i copied wrong aboot.img how did you fix it???
thanks in advance
please email to me your solution.. if you have time thanks.
[email protected]
tengskie said:
please help i have the same problem.. i copied wrong aboot.img how did you fix it???
thanks in advance
please email to me your solution.. if you have time thanks.
[email protected]
Click to expand...
Click to collapse
http://forum.xda-developers.com/g2-mini/help/bricked-phone-help-t3192435/page2?nocache=1
My wife, unfamiliar with rooting, agreed to update my rooted Moto C Plus when it requested an update. Needless to say, that didn't turn out well. It started booting to TWRP.
I tried finding a solution online. That led me to... https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325 where it gives the following method as a solution:
matiashl said:
TWRP Method:
1- Go into TWRP -> Go to Advanced -> Go to Terminal:
Enter
2- Please make a backup first of these files in SD card:
Code:
cp /dev/block/platform/soc.0/7824900.sdhci/by-name/mota /sdcard/mota2
cp /dev/zero of=/dev/block/platform/soc.0/7824900.sdhci/by-name/misc /sdcard/misc2
3- Type this exactly:
Code:
dd if=/dev/zero of=/dev/block/platform/soc.0/7824900.sdhci/by-name/mota
HIT ENTER
Code:
dd if=/dev/zero of=/dev/block/platform/soc.0/7824900.sdhci/by-name/misc
HIT ENTER
4- Restart the phone.
Click to expand...
Click to collapse
On my phone, there is no "soc.0" in the platform folder, instead there is "mtk-msdc.0". I tried searching online for a similar solution with the folder "mtk-msdc.0", but i couldn't find any...except for this chinese page. Desperate (not knowing which file to go with), i tried "dd if=/dev/zero of=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot". That executed something. But later, when i restarted the phone, it stopped booting to TWRP. Instead, it is now just showing this logo (Moto) screen (the one that shows fist when you turn on the phone, before the TWRP) for about 30 secs or so, and then the phone restarts back to the same screen...restart... screen...and so on. Basically a bootloop, i believe its called.
What do i do now? The fix i was looking for is one where i don't loose my files. Everything is on the internal memory. No SD card. I want to be able to get my phone to start working again without losing my files. If i could get it to start working again without everything just the way it was before this problem, i would be super grateful.
Please help!
Anyone?