Related
I was attempting to get the Nandroid back up feature going on my phone. I downloaded the recent RC30 for the multi-touch (I couldn't help it), and I was given this error about the application settings not responding and to force quit. Then I downloaded the SPL bootloader and the modified RC30 with the busybox. It's in this post (http://forum.xda-developers.com/showthread.php?t=459830). I did a successful backup, but now my phone won't work right.
When I boot the phone none of the buttons respond until a good 30 seconds into the full boot up, and only after I slide open the keyboard. When I press the power key the screen flashes and the blank wallpaper comes up for 5 seconds. There is no way for me to get into the recovery mode. When I tried that it gives me the phone with the exclamation point.
I think I am just at or 1 day past my 14 days. It's really going to suck if I have to pay for a new phone b/c I got cocky and thought I knew what I was doing. Hopefully you guys have a solution or T-mobile will be forgiving.
Oh, and when I look under settings it says: kila user 1.0 TC4-rc30 so T-mobile will know I rooted the phone and F'ed up.
You could try restoring with DREAIMG.nbh
and you didnt brick it, a brick doesnt do anything, yours sounds like it boots.
I can't get into recovery mode. I can get into fastboot. I found a thread on installing cupcake will help get it back to RC30, but I didn't understand where to type in the prompts.
When I tried that it gives me the phone with the exclamation point.
Click to expand...
Click to collapse
Try Alt-L at this point.
I forgot about that. Thank you! Now I just need to find a way to get my phone back to full functionality. Do I need to just find RC29 or JF RC30 and reinstall as update.zip?
It says "E: Can't open /cache/recovery/command"
We will see if reinstalling RC30 will work. Does anyone have the orignal RC30 that comes installed on the G1? I understand I'll lose root access and that might be the smartest thing for me now.
I reinstalled RC30 and it worked! Thank you guys, and thanks for putting up for my temporary insanity!
I would do a wipe and then update to jf's latest 1.4. But at this point you should be able to update to whatever you want.
Sorry if this is a stupid question but I have made a NANDROID Backup and I would like to know how to restore my phone with the backup I made.
ow to Restore your phone on a Windows PC using a Nandroid backup
I am going to assume you already have a Nandroid backup created on your SD card using JF 1.31's recovery Alt-B feature. The backup will create a folder called nandroid on your SD.
What you need:
The Android SDK:
Fastboot Windows Binary in this post:http://forum.xda-developers.com/show...53&postcount=1
From your Nandroid backup you need three files:
data.img
system.img
boot.img
Steps to restore your phone
1) Put the files Adb and AdbWinApi.dll from the tools folder in the Android SDK into C:\WINDOWS\System32 folder on your PC. Substitute the correct drive letter if windows is not installed on you C: drive
2) Put the Windows Fastboot.exe into the C:\WINDOWS\System32 folder on your PC
3) Create a folder on the C: drive of your PC called android. The path should be C:\Android.
4) Copy the Nandroid backup files data.img, system.img, and boot.img from your SD card to the folder called Android you created by mounting your SD card as removable disk.
5) Unplug the USB cord and power off your phone
6) Power up your phone by holding CAMERA+POWER, you should see three androids on skateboards. If you don't see this go install the Engineering boot loader
7) Plug the USB cord back into your phone and press back. The screen on your phone should say fastboot.
8) Make sure your pc is using the correct driver. Open the device manager on your pc. It is helpfull to have all other USB storage devices besides your phone unplugged for this part. Look for a USB Mass Storage device in the list of the USB devices. Right click on it and update the driver. Pick the option to browse for a driver on your pc. The driver is located in the Android SDK your downloaded in the folder called usb_driver. If this is done right you will now see a device called HTC Dream
9) Press start, go to run and type cmd (If you are on Vista just type cmd in the search box and hit enter). The command prompt will pop up.
10) Type cd C:\android
then enter the following commands:
fastboot flash system system.img
it will say Sending, then writing and say OKAY if it was successful
then type
fastboot flash userdata data.img
wait for the second OKAY and type
fastboot flash boot boot.img
wait for the second OKAY and type
fastboot reboot
Your phone should now be restored exactly as you had it when it was backed up.
Hi there,
I am such an idiot, I deleted the framework-res.apk from /system/framework/ and rebooted. You all know what had to happen: the Nexus with FRF91 won't boot anymore.
So I am asking for help: Is there any way to restore (i.e. put a stock framework-res.apk) in that folder? I have ADB tools and stuff installed.
Or is there any way to access the sdcard without booting the system? I could put an update.zip there and apply it.
Of course, I'd rather not delete my apps and stuff but still better than a bricked phone.
Any help would be great. Thanks a lot.
try this:
1. put a copy of framework-res.apk in your sdk/tools folder (this can be taken from a copy of the rom that you have installed at the moment)
2. boot your phone like usual; when the bootscreen appears, enter this into a command window directed at your adb (SDK/tools is the tools folder in my adb):
Code:
cd/
cd SDK/tools
adb reboot recovery
adb remount
adb push framework-res.apk /system/framework/framework-res.apk
adb reboot
this should put it into the correct folder and reboot the phone. give it a little time, whenever I flash a new FW-res it seems to take a little longer than when I have not to boot up. I have a desire, I am only presuming thats where it needs to go
Thank you very much for your answer.
Code:
adb reboot recovery
worked flawlessly when the boot animation was showing. Although it took quite a while until the device was recognized.
Now the Android dude with the exclamation mark is on the screen (recovery). Right now the device is not recognized. Therefore I cannot execute
Code:
adb remount
or any other adb commands.
This was one of my initial questions: how do I get to access the file-system from recovery?
Btw: is there any difference from manually (trackball + powerbutton) going to recovery to using adb?
Thanks
can you get into the green recovery screen by executing the .bat file after doing the reboot/recovery? I find sometimes it can take up to five tries to push the files correctly.
if you can do that, then you can execute the rest pretty easily.
you can even turn it into a 'mass storage device' to put an update.zip on the sdcard
edit: this one was the recovery I was meaning.
the other way to get into that is
Code:
How to boot in Recovery Mode
Boot the phone while holding down the VOLUMEDOWN-key.
Navigate to RECOVERY with the the VOLUMEDOWN-key.
Press the POWER-key to select.
anything other than the information above and I can't be much use, this is about as far as my adb and android knowledge extends sorry.
GL
yes, I do get the recovery screen but I cannot execute adb commands from there. Any hints?
Well, if you can't access terminal (console) from recovery, try fastboot, and reflash the whole firmware WITHOUT wiping. That should do the trick!
Ok, will try to do that. What I've done so far is copied update-nexusone-FRF91-stock-noradio-signed.zip to the sdcard's root, renamed it to update.zip and tried to install it via the stock bootloader (recovery with Volume UP + Powerbutton). This failed. Am I using a wrong Rom? Should I try to install this via fastboot?
wouldnt hurt. my next suggestion would then be an untouched rom (maybe 2.1 so you dont have a problem with the bootloader changing versions)
wouldn't fastboot allow me to copy the file to the system? I found this command for fastboot:
Code:
flash <partition> [ <filename> ] write a file to a flash partition
I think I will just have to flash the system-image:
Code:
fastboot flash XXX YYY - This will flash XXX partitionn with YYY image.
e.g: fastboot flash system system_update.img will flash/update your system partition with an image called system_update
Taken from http://forum.xda-developers.com/showthread.php?t=619153
Correct?
Then I need to find a system.img
Sorry for this double-post but I guess you guys don't come back, otherwise...
Can anyone provide a system.img for me? I've just tried the one from the stock PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_release_signed.zip but received
Code:
sending 'system' (116663 KB)... OKAY
writing 'system'... INFOs
FAILED (remote: signature verify fail)
Edit: I have a LOCKED bootloader
can you either try using a stock rom rather than a cooked one, or try resigning the rom you are trying to flash?
Sent from my HTC Desire using XDA App
I have also accidentally deleted my framework-res.apk, and my X10 won't boot (duh). Now When I use the command "adb remount", I get the error message: "remount failed: Operation not permitted". How do I push framework-res.apk to my phone now?
I thought I was using a stock rom with
PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_relea se_signed.zip
update-nexusone-FRF91-stock-noradio-signed.zip
How does resigning work? I guess there are tools for this. Never used a cooked rom so far.
signing roms: http://androidforums.com/developer-101/8665-how-signing-roms.html
try signing it again, then installing it.
the -signed extension to me sounds like someone dl'd the original, edited and resigned it (eg: to remove the radio). This edit may have been the reason why they are failing the verification. I dont know enough about the difference between fastboot and recovery to know any other reasons why it might fail in there.
this may be why it is not working in FASTBOOT
back to ADB, if you try it via that method and it fails, try killing the adb task in task manager, then try again. for me adb works after that more often than not.
nzdcoy said:
signing roms: http://androidforums.com/developer-101/8665-how-signing-roms.html
try signing it again, then installing it.
the -signed extension to me sounds like someone dl'd the original, edited and resigned it (eg: to remove the radio). This edit may have been the reason why they are failing the verification. I dont know enough about the difference between fastboot and recovery to know any other reasons why it might fail in there.
this may be why it is not working in FASTBOOT
back to ADB, if you try it via that method and it fails, try killing the adb task in task manager, then try again. for me adb works after that more often than not.
Click to expand...
Click to collapse
Okay, signing worked for the zip file. But the system.img is still not working.
What do you mean with adb? What should I do? I guess the problem is that the system is not fully booted and I don't get root at that stage.
which rom have you tried to flash in FASTBOOT? I would expect PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_relea se_signed.zip to work since it is a stock rom, but the other one looks like it has been repackaged.
knox420 said:
Ok, will try to do that. What I've done so far is copied update-nexusone-FRF91-stock-noradio-signed.zip to the sdcard's root, renamed it to update.zip and tried to install it via the stock bootloader (recovery with Volume UP + Powerbutton). This failed. Am I using a wrong Rom? Should I try to install this via fastboot?
Click to expand...
Click to collapse
can you try doing this with the PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_relea se_signed.zip one?
if possible try doing it without resigning the zip first.
Alright, none of this worked. I tried it all but in the end I had to realize I lack too much knowledge.
I wiped everything and reinstalled Cyanogen Mod 6 RC3. System's up and running.
Thanks for any help, though.
Or is there any way to access the sdcard without booting the system? I could put an update.zip there and apply it.
Click to expand...
Click to collapse
You mean get the card out of the phone and plug into a card reader?
cryshop said:
You mean get the card out of the phone and plug into a card reader?
Click to expand...
Click to collapse
What I meant -back in the days- was that I wanted to access the card while still in the phone. From the bootloader. Now this is possible with ClockworkMod or AmonRa Recovery.
Thanks anyway
My phone is unlocked and rooted. My problem is that when I go to FASTBOOT MODE, then go into RECOVERY, then when I press 'apply update from /sdcard' it shows nothing in there. So, I just stuck and unable to flash any rom at all. I tried to go into the SD card through my computer to install a ROM so that I have something to flash, but nexus s has only internal storage. Please help?
Hi
Hi, I bought my nexus s, immediately after I tried to root, and failed, this left me in the same situation as you.
You NEED to install the adb drivers, and boot using odin files. It was pretty tricky but i got there in the end, i was bricking it too , but dont worry, there's a 98% chance its not bricked, ill find the files for you now...
Go to mount drives and mount your storage from there. That's what I did.
Right, first of all, boot into the bootloader on your Nexus S, and i'm assuming that all your drivers are working fine because you have already unlocked your bootloader.
Place the files in the zip download inthe following places
WIN32bitOS: Program files/Android/Android-sdk/tools
WIN64bitOS: Program files (x86)/Android/Android-sdk/tools
Next, open a command prompt, and type in the following commands, (C: is your windows installation hard drive letter, leave as default if you dont know what this means)
if your 32bit type this w/o quotes "cd C:/Program files/Android/Android-sdk/tools
64bit "cd C:/Program files (x86)/Android/Android-sdk/tools
and click enter.
Next you want to make sure that your Nexus S is in bootloader mode, connected to your pc.
Type the following.
fastboot flash boot boot.img
[click enter & wait until it says successful]
fastboot flash recovery recovery.img
[click enter & wait until it says successful]
fastboot flash system system.img
[click enter & wait until it says successful]
fastboot flash userdata userdata.img
[click enter & wait until it says successful]
Reboot and you should go into android 2.3
Next time make a nandroid backup in clockwork mod!
Download link : http://www.megaupload.com/?d=GI9P4F5I
cdaly985 said:
Right, first of all, boot into the bootloader on your Nexus S, and i'm assuming that all your drivers are working fine because you have already unlocked your bootloader.
Place the files in the zip download inthe following places
WIN32bitOS: Program files/Android/Android-sdk/tools
WIN64bitOS: Program files (x86)/Android/Android-sdk/tools
Next, open a command prompt, and type in the following commands, (C: is your windows installation hard drive letter, leave as default if you dont know what this means)
if your 32bit type this w/o quotes "cd C:/Program files/Android/Android-sdk/tools
64bit "cd C:/Program files (x86)/Android/Android-sdk/tools
and click enter.
Next you want to make sure that your Nexus S is in bootloader mode, connected to your pc.
Type the following.
fastboot flash boot boot.img
[click enter & wait until it says successful]
fastboot flash recovery recovery.img
[click enter & wait until it says successful]
fastboot flash system system.img
[click enter & wait until it says successful]
fastboot flash userdata userdata.img
[click enter & wait until it says successful]
Reboot and you should go into android 2.3
Next time make a nandroid backup in clockwork mod!
Download link coming in 9 mins... data uploading
Click to expand...
Click to collapse
hi cdaly, can you point me to some information on how to install nandriod backup and making/restore a backup right after installing CWM (right after "unlocked" but didnt install Super user yet)?
Yeah
Yeah sure,
Root your phone, go to market place, download rom manager. Open the app and click the button that says, Fash Clockwork Recovery.
Shut down your phone when the operation has completed. Go inot bootloader mode, click recovery. Navigate to backup and restore. Go into backup and restore, click backup. Voila.
If you ever need to restore do the same but click restore. Pretty simple when you know what to do
If this has left you confused, look around on XDA/google, there are a ton of guides
Link added!
Thanks, appreciate it.
Thanks for that. I am using mac computer. Would it be the same typing command for mac as you had mentioned?
cdaly985 said:
Yeah sure,
Root your phone, go to market place, download rom manager. Open the app and click the button that says, Fash Clockwork Recovery.
Shut down your phone when the operation has completed. Go inot bootloader mode, click recovery. Navigate to backup and restore. Go into backup and restore, click backup. Voila.
If you ever need to restore do the same but click restore. Pretty simple when you know what to do
If this has left you confused, look around on XDA/google, there are a ton of guides
Link added!
Click to expand...
Click to collapse
Thanks very much cdaly.. I am just a bit confused regarding phone is rooted or not.
I got to the point flash recovery was sucessfuly in command prompt, but when i try to install "su-2.3.6.1-cd-signed.zip" from SD card, it wasn't successful, as in there is no "superuser" icon after reboot and i have tried wifi tether and it says my phone is not root.
Now i havent tried "su-2.3.6.1-ef-signed.zip" because i accidently bricked my phone for some stupid things i did. but my phone is NOT root as long as I don't see the superuser program right?
I thought nandroid is an actual program but it just means backing up through bootloader?
Thanks for all your help!!!
Thanks very much cdaly.. I am just a bit confused regarding phone is rooted or not.
I got to the point flash recovery was sucessfuly in command prompt, but when i try to install "su-2.3.6.1-cd-signed.zip" from SD card, it wasn't successful, as in there is no "superuser" icon after reboot and i have tried wifi tether and it says my phone is not root.
Now i havent tried "su-2.3.6.1-ef-signed.zip" because i accidently bricked my phone for some stupid things i did. but my phone is NOT root as long as I don't see the superuser program right?
I thought nandroid is an actual program but it just means backing up through bootloader?
Thanks for all your help!!!
Click to expand...
Click to collapse
I dont know if NANDROID is a program or not, it just use it via clockwork mod recovery menu and it works so I'm not complaining aha
If you want to root your nexus s, download this zip file and extract, make sure that your nexus s is in bootloader mode and double click "install-superboot-windows" Bingo, you have root.
Thanks for that. I am using mac computer. Would it be the same typing command for mac as you had mentioned?
Click to expand...
Click to collapse
It wouldn't hurt to try but I dont think so. If you can go into boot-camp or use a friends PC. Or you can try this.
Change your folder to the plaform-tools folder. I dont know how to do this, just referencing off of http://rootzwiki.com/wiki/index.php/Samsung_Nexus_S
Next type
"./fastboot flash boot boot.img"
"./fastboot flash recovery recovery.img"
"./fastboot flash system system.img"
"./fastboot flash userdata userdata.img"
Hi cdaly985
I'd tried it and it works 100%. And, just to share for mac to add on the command "./fastboot-mac ....". I am really impressed with your help. Thanks very very very much.
Hi cdaly985
Now everything is ok with the phone except that it won't be able to go into recovery mode. I had tried by using Rom manager v.4.. and also by pressing vol + power, all failed.
Please help me on this problem. Thanks.
I flashed a ROM from the forum , but afterwards the phone didnt work normally.
I can still get into recovery, and I can get into bootloader.
The sd card I believe, can not be mounted anymore, not with mount /sdcard or with mount usb
(With my ohter htc phones, I could use these to connect to the pc whilst in recoverymode)
i do have nandroid backups on the pc, but cant get them on the phone.
When i reset the phone it hangs in the white screen: HTC quietly Brilliant "this build is for dev purp......."
Ive tried several posts about similar problems on xda, but no succes
I also tried a RUU 1.47... but it gave me an error 155.
Please help, thanx.
ADB
Lacuna666 said:
I flashed a ROM , afterwards the phone didnt work.
I can still get into recovery, and I can get into bootloader.
The sd card can not be mounted anymore, not with mount /sdcard or with mount usb
i do have nandroid backups on the pc, but cant get them on the phone.
When i reset the phone it hangs in the white screen: HTC quietly Brilliant "this build is for dev purp......."
Ive tried all the posts to be found about similar problems on xda, but no succes
I also tried a RUU 1.47... but it gave me an error 155.
Please help, thanx.
Click to expand...
Click to collapse
your post is going to get moved but before it does may I suggest re-flashing Rom then go into bootloader and fastboot flash boot.IMG. sounds like this is what you are missing
solrac.dc said:
your post is going to get moved but before it does may I suggest re-flashing Rom then go into bootloader and fastboot flash boot.IMG. sounds like this is what you are missing
Click to expand...
Click to collapse
I cant reflash a rom, i cant get anything on the phone now !
Lacuna666 said:
I cant reflash a rom, i cant get anything on the phone now !
Click to expand...
Click to collapse
Are you able to get into fastboot you can push RECOVERY, BOOT, and ZIP to SDCARD... if you can let me know and will tell you what you need to do
fabiane79 said:
Are you able to get into fastboot you can push RECOVERY, BOOT, and ZIP to SDCARD... if you can let me know and will tell you what you need to do
Click to expand...
Click to collapse
recovery; yes i can get in there
then you said "boot" : that's not in there !
I do see a "install zip from sdcard" then i get a choise of:
choose zip from sd
apply; /sdcard/update.zip
what did you want to try ?
Lacuna666 said:
recovery; yes i can get in there
then you said "boot" : that's not in there !
I do see a "install zip from sdcard" then i get a choise of:
choose zip from sd
apply; /sdcard/update.zip
what did you want to try ?
Click to expand...
Click to collapse
It sounds like you may have corrupted your SD card. similar situation happened to my friends HTC Surround and how I was able to fix was open the phone (warranty gets voided of course) and change out the SD Card.
now........i could be wrong but you may want to do what homie posted above and put your phone into "fastboot" mode and ADB push. good luck!!
solrac.dc said:
It sounds like you may have corrupted your SD card. similar situation happened to my friends HTC Surround and how I was able to fix was open the phone (warranty gets voided of course) and change out the SD Card.
now........i could be wrong but you may want to do what homie posted above and put your phone into "fastboot" mode and ADB push. good luck!!
Click to expand...
Click to collapse
Okay, but opening the phones not really an option for me.
The adb command: i assume you mean adb push (something)
Thanks anyway
ADB push is the best option. Its easiest and most effective.
Sent from ICS device!
itsmikeramsay said:
ADB push is the best option. Its easiest and most effective.
Sent from ICS device!
Click to expand...
Click to collapse
Thanks, but whats the whole command ?
Lacuna666 said:
I can still get into recovery, and I can get into bootloader.
Click to expand...
Click to collapse
That means you're not bricked.
Lacuna666 said:
Thanks, but whats the whole command ?
Click to expand...
Click to collapse
- Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly.
- Once this has completed, unplug your phone from your computer and close the Command Prompt window
- Back in Recovery, go to Recovery's main screen and Do a "Factory Reset", "Wipe Cache Partition", and "Wipe Dalvik Cache [which is in the Advanced menu of Recovery]"
- When these are all done, from Recovery's main screen, select "Install ZIP from SD Card" and then "Choose file from SD Card" and select the ROM.zip file you just pushed from your computer to the SD Card. If you do not see the file, go back to Mounts and Storage and toggle them to say "Mount /sdcard/" and "Mount /system/" and then go back and try to fine the ROM.zip file. If you still do not see it, it was not pushed correctly...go back and ensure you were letter for letter with the name and the file path.
- Once the screen in Recovery says "Install from SD Card Complete.", go back to Recovery's main screen yet again and select "Reboot system now" - If your device fails to Install the ROM.zip, I had this happen to me. You must push the CWM SuperSU ZIP (the .zip file is found at the end of this thread)file as outlined before and Install THAT .zip file in Recovery, then reboot Recovery and Install the ROM.zip from SD Card.
- Let your phone have some time to boot up...initial boot from installing a new ROM have histories of taking a couple minutes.
- You should now be on a working HTC One S running whatever ROM you decided to flash.
fabiane79 said:
- Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly.
- Once this has completed, unplug your phone from your computer and close the Command Prompt window
- Back in Recovery, go to Recovery's main screen and Do a "Factory Reset", "Wipe Cache Partition", and "Wipe Dalvik Cache [which is in the Advanced menu of Recovery]"
- When these are all done, from Recovery's main screen, select "Install ZIP from SD Card" and then "Choose file from SD Card" and select the ROM.zip file you just pushed from your computer to the SD Card. If you do not see the file, go back to Mounts and Storage and toggle them to say "Mount /sdcard/" and "Mount /system/" and then go back and try to fine the ROM.zip file. If you still do not see it, it was not pushed correctly...go back and ensure you were letter for letter with the name and the file path.
- Once the screen in Recovery says "Install from SD Card Complete.", go back to Recovery's main screen yet again and select "Reboot system now" - If your device fails to Install the ROM.zip, I had this happen to me. You must push the CWM SuperSU ZIP (the .zip file is found at the end of this thread)file as outlined before and Install THAT .zip file in Recovery, then reboot Recovery and Install the ROM.zip from SD Card.
- Let your phone have some time to boot up...initial boot from installing a new ROM have histories of taking a couple minutes.
- You should now be on a working HTC One S running whatever ROM you decided to flash.
Click to expand...
Click to collapse
+1,000,000
nxt said:
That means you're not bricked.
Click to expand...
Click to collapse
If it won't startup properly, i'm calling it bricked, you know what i mean.
Bricked means useless and that's what it is.
Lacuna666 said:
If it won't startup properly, i'm calling it bricked, you know what i mean.
Bricked means useless and that's what it is.
Click to expand...
Click to collapse
you should be able to do it... I F&&&& up my phone many times and was able to get it working... make sure you have the correct boot.img for the correct rom your installing that will make the phone not work...
ADB push ROM to a phone
This should really be stickied
Thanks, now ive got some stuff to try out tomorrow, i will report back !
Thanks for linking my thread.
And thanks for quoting my thread without any credit. -_-
Moved To Q&A
This section is for development only!
did you try cannodale's thread here
http://forum.xda-developers.com/showthread.php?t=1630459
his key is clearing storage thru stock recovery to get sdcard mounted
also on flashing ruu, i think you need to relock bootloader and have sense rom on phone--not sure you are in that position atm and not 100% sure on both these
Hi, my G6-U10 is hard bricked and has gone to QDLoader 9008 mode so i cant go to recovery, fastboot,adb mode .
i need EMMC image of a similare device (G6-U10) so i can fix it following instructions in this thread .
i dont need whole EMMC image, just first 100-200 MB .
to extract EMMC, you need to be on stock rom with root access.
to do so:
1. Enable "USB debugging" in "Developer Options". then connect your device to Windows PC.
2. download and extract ADB. then run the following command through CMD:
Code:
adb shell
su
dd if=/dev/block/mmcblk0 of=/sdcard/EMMC.img bs=100m count=1
note that you must enter each row separately and confirm the dialogs appeared on your device screen to grant root and adb access for pc. the option bs=100m mean that the dd command will only extract first 100MB of EMMC. and FYI, this file is only backup from system partition, not from any private files, no need to worry.
the extracted file will be in internal SD, named EMMC.img , compress it in ZIP or RAR so it will have much less size, then send it here to solve many people's problems. anybody does that, i'll appreciate.
Thanks for reading.
Credits and references:
@majdinj http://forum.xda-developers.com/showthread.php?t=2450045
@Jimmyz0r http://forum.xda-developers.com/yureka/help/guide-unbrick-hard-bricked-yureka-t3303112
@tirta.agung http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
http://linoxide.com/linux-command/linux-dd-command-create-1gb-file/
http://unix.stackexchange.com/questions/134299/dd-bs-count-seek
https://yadi.sk/d/wtaBNFaUraZyg
washichi said:
https://yadi.sk/d/wtaBNFaUraZyg
Click to expand...
Click to collapse
Thanks bro, but it's just 100bytes, not 100Mbytes. i think you used bs=100 instead of bs=100m
please consider reuploading , you are my saviour
info on the progress:
I got EMMC image thanks to @washichi :good: (download it from attachments).
then i could finally wake my device up, in the fastboot and recovery, following instructions in this thread(first post).
i can go into Fastboot mode but though i had unlocked bootloader (before), but i can only flash recovery, system(partly) and boot partitions. other partitions give me error ((Remote: Not Allowed)).
the only recovery that i could go into, was the latest TWRP 3 . in recovery i can even connect my device in MTP mode to pc and see files on the internal SD! but i was not successful with flashing roms, it always gives me error mounting cache, system, data. ADB mode is also accessible, used adb sideload to flash rom, but it didnt worked too!
i think part of internal SD is damaged and need to be fixed somehow. still havent found out how.
so, for guys who are having problems similar to me or "Internal Storage Damaged blah blah" i recommend trying to follow these steps to see if their internal SD is still flashable or not:
1. Download an official Rom for your device and unpack it using HuaweiUpdateExtractor.
2. download and extract latest (at least 1.0.32) fastboot in the same folder as extracted huawei IMG files are (Gush bless me! there's too much grammatical erros in my texts )
3. connect your device in fastboot mode (instructions above).
4. go to the directory where all extracted files place. Hold shift and right click on empty space, chose "Open command window here".
Note: you must have an unlocked bootloader to be able to continue, type this command to see if its unlocked:
Code:
fastboot oem get-bootinfo
if you're unlocked, then continue reading, if not, i dont think there is a way to find unlock key for your device.even DC unlocker cant recognize your device in fastboot and adb.
5. now that you know you have an unlocked BL, type these commands one bye one:
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash aboot aboot.img
fastboot flash tz tz.img
fastboot flash userdata userdata.img
fastboot flash [COLOR="RoyalBlue"]XXX [/COLOR][COLOR="SeaGreen"]XXX[/COLOR].img
as i said before, i could only flash 3 partitions with success. but if you where able to flash all parts with success, your extremely have a chance to revive your device. at last, type fastboot reboot to see if you boot up successfully, if not, you will go again in fastboot mode or recovery mode.
for me, default recovery mode just freezes, so i flashed TWRP 3 instead of default recovery. you can try that too.
one more thing: you might not be successful to reboot into recovery, you must restart until you succeed. if you stuck in freezed recovery, open the device back, unscrew the little steel plate (it has 2 screws) and dettach the battery cord, wait 3 secs, re-attach it. i have done it more than 300 times now i dont even know where is the steel plate
FYI, EMMC image in the attachment is for G6-U10 only and probably will not work for other G6 models. if you want G6-L11 emmc, i can share it for you.
if anything was not clear for you, ask me.
@bugggmenot Everytime i insert the sd card and try to enter fastboot mode by holding the Volume+, the PC keeps beeping and refreshing the device manager, tho i can't see any hardware detected. The phone isn't recognizable as fastboot device and the LED is lighting in a blue color.
Any ideas?
Sashko98 said:
@bugggmenot Everytime i insert the sd card and try to enter fastboot mode by holding the Volume+, the PC keeps beeping and refreshing the device manager, tho i can't see any hardware detected. The phone isn't recognizable as fastboot device and the LED is lighting in a blue color.
Any ideas?
Click to expand...
Click to collapse
Do as follows:
1. detach the battery and retach it again.
2. connect the device to pc WITHOUT holding any buttons.
3. if you go into fastboot mode, you will see a blue "Fastboot mode" in middle of texts (and Blue LED).
4. type in cmd: fastboot devices
if your device is listed, you are good to go for flashing procedure.
oh and one more important thing: install fastboot and adb drivers. it's a global driver not device specific, so install any you van find ( sorry I can't Google it for you right now).
bugggmenot said:
Do as follows:
1. detach the battery and retach it again.
2. connect the device to pc WITHOUT holding any buttons.
3. if you go into fastboot mode, you will see a blue "Fastboot mode" in middle of texts (and Blue LED).
4. type in cmd: fastboot devices
if your device is listed, you are good to go for flashing procedure.
oh and one more important thing: install fastboot and adb drivers. it's a global driver not device specific, so install any you van find ( sorry I can't Google it for you right now).
Click to expand...
Click to collapse
Did everything still doesn't want to boot in fastboot mode.
Edit: I made it to the fastboot, thank you very much.
Sashko98 said:
Did everything still doesn't want to boot in fastboot mode.
Edit: I made it to the fastboot, thank you very much.
Click to expand...
Click to collapse
Happy to hear that. would be great if you share your way of success and your current progress on reviving the device. it might help many people.
bugggmenot said:
Happy to hear that. would be great if you share your way of success and your current progress on reviving the device. it might help many people.
Click to expand...
Click to collapse
I got it to the progress you did. Was able to flash only boot.img recovery.img and like 950MB of system.img. Yet smth makes me to think that everything i do flash is being flashed in the SDcard memory not in the internal one, is it supposed to be like that?
Edit1: Tried to flash an update.zip which i made by using huawei tools extractor from the stock recovery but the verification aborted the update. Tried with CWM by using adb sideload but there was some error while sending, also tried with TWRP which seems to erase its memory everytime when i restart the phone, the adb sideload doesnt work and couldn't found the flashable zip after i pushed it in by using adb
Sashko98 said:
I got it to the progress you did. Was able to flash only boot.img recovery.img and like 950MB of system.img. Yet smth makes me to think that everything i do flash is being flashed in the SDcard memory not in the internal one, is it supposed to be like that?
Click to expand...
Click to collapse
i dont think so.
i thought like you, but to test it i went to TWRP recovery and removed SD card, Formated SD (via MiniTool Partition) and reinserted SD into device. at this level , device cant recognize SD anymore, so i reformatted SD via TWRP (i dont remember the exact path, sorry), and this time SD appeared in PC ! so i simply put flashable SlimStock and flashed it via TWRP. but it exactly took the time that it had taken before when i tried to flash SlimStock via Sideload. and in both ways, it takes about 30 min to pass the system.img flashing ! so this can be a proof that in the both ways, images are being flashed on the internal SD, not ExSD.
any way, at this point it seems that we cannot go any further. but who knows? we made a dead device into TWRP, so why not...
bugggmenot said:
i dont think so.
i thought like you, but to test it i went to TWRP recovery and removed SD card, Formated SD (via MiniTool Partition) and reinserted SD into device. at this level , device cant recognize SD anymore, so i reformatted SD via TWRP (i dont remember the exact path, sorry), and this time SD appeared in PC ! so i simply put flashable SlimStock and flashed it via TWRP. but it exactly took the time that it had taken before when i tried to flash SlimStock via Sideload. and in both ways, it takes about 30 min to pass the system.img flashing ! so this can be a proof that in the both ways, images are being flashed on the internal SD, not ExSD.
any way, at this point it seems that we cannot go any further. but who knows? we made a dead device into TWRP, so why not...
Click to expand...
Click to collapse
Well i did try flashing img files via TWRP but it allows me to modify just recovery or boot partition. Tried also making flashable zip of the partition to run it from CWM but i get stuck.
I also tried
Code:
fastboot flashing unlock_critical
and
Code:
flashing unlock
but i recieve 3 dots, maybe i should be more patient next time to see what will happen.
===========================================================================
@bugggmenot i've found the file for G6-C00 for qualcomm bootloader platform. Will they work on G6-U10???
Sashko98 said:
Well i did try flashing img files via TWRP but it allows me to modify just recovery or boot partition. Tried also making flashable zip of the partition to run it from CWM but i get stuck.
I also tried
Code:
fastboot flashing unlock_critical
and
Code:
flashing unlock
but i recieve 3 dots, maybe i should be more patient next time to see what will happen.
===========================================================================
@bugggmenot i've found the file for G6-C00 for qualcomm bootloader platform. Will they work on G6-U10???
Click to expand...
Click to collapse
Greate! i dont know if they are similar or not but who cares, i'll give it a shot! please share files here i'll try and report back.
bugggmenot said:
i dont think so.
i thought like you, but to test it i went to TWRP recovery and removed SD card, Formated SD (via MiniTool Partition) and reinserted SD into device. at this level , device cant recognize SD anymore, so i reformatted SD via TWRP (i dont remember the exact path, sorry), and this time SD appeared in PC ! so i simply put flashable SlimStock and flashed it via TWRP. but it exactly took the time that it had taken before when i tried to flash SlimStock via Sideload. and in both ways, it takes about 30 min to pass the system.img flashing ! so this can be a proof that in the both ways, images are being flashed on the internal SD, not ExSD.
any way, at this point it seems that we cannot go any further. but who knows? we made a dead device into TWRP, so why not...
Click to expand...
Click to collapse
Why not try to repartition your device?
You can you the parted binary (google will find it) and put it on your /sdcard or / (the root folder). NOT your internald memory or any other partition thats your EMMC.
Now umount ALL partitions in recovery, except for the external sdcard. Go to the commandline in the recovery and cd to the parted binary. Now typ 'parted /dev/block/mmcblk0'.
Type 'print' to see your partition table.
You can now modify your partition table (only ext2 and fat32 partitions support, BUT you can format it whit your recovery soo it will be ext4. (Dont check RM format in settings!).
Hope this will fix the flashing problem.
Hard Brick
Hello guys, i don't know if this is the right place, but do you know how to unbrick Huawei Y550 - L03 from hard brick? My pc recognizes it in the device manager just as Android adapter PCUI (COM10) but the device itself doesn't show.
Thank you in advance if you can help me please. :crying:
Here i put EMMC for G6-L11 for people who need it:
Hello, can you explain how you made it from dead phone QDLoader 9008 to recovery?
bugggmenot said:
Here i put EMMC for G6-L11 for people who need it:
Click to expand...
Click to collapse
We should use the Yureka tutorial with this file to bring the G6-L11 to life right?
henrucci said:
We should use the Yureka tutorial with this file to bring the G6-L11 to life right?
Click to expand...
Click to collapse
only if your phone is G6-L11, then the answer is yes.
Win32disk killed for good all sdcards with g6-l11 image