Related
So I am trying to Re-Flash my T-Mobile Wing.
I HAD TouchIT Vista on my Phone and wanted to put on a new version.
While trying to re-flash, like i did before, I would connect to my phone, then it would drop while starting the flash. So I decided to flash on the Stock ROM. Now, being a complete idiot, I started the Flash (BAT file) before putting Itsutils.dll into the Windows folder... Now I cannot boot into my phone. But I CAN boot into BootLoader.
I dont know how to use BootLoader tho. What do I do to get this back up and running? Dear god, I hope I didn't brick my Phone!
Try the Following:
Got to this link, post #2:
http://forum.xda-developers.com/showthread.php?t=421304
-download the Herald-USPL-Beta 3 file found on post#2
-extract the flash center folder to your desktop
-extract the nbh file from your stock rom using winrar or 7zip
-place the nbh file in the ruu folder within the flash center folder
-run the utility
*if my instructions arent clear to you, there is a full tutorial on the link that i gave you
hope this helps!!
spacemonkey333 said:
Try the Following:
Got to this link, post #2:
http://forum.xda-developers.com/showthread.php?t=421304
-download the Herald-USPL-Beta 3 file found on post#2
-extract the flash center folder to your desktop
-extract the nbh file from your stock rom using winrar or 7zip
-place the nbh file in the ruu folder within the flash center folder
-run the utility
*if my instructions arent clear to you, there is a full tutorial on the link that i gave you
hope this helps!!
Click to expand...
Click to collapse
Thank you so much for your quick response... I have been looking at that file, and have downloaded everything... but my phone wont boot into TouchIT anymore... Can i do these from Bootloader? How?
Fenopy said:
Thank you so much for your quick response... I have been looking at that file, and have downloaded everything... but my phone wont boot into TouchIT anymore... Can i do these from Bootloader? How?
Click to expand...
Click to collapse
-press and hold your camera button on the side of your phone
-while holding the camera button, press and release the soft reset button
-dont let go of the camera button until you enter a tri-colored screen.
-now you are on your bootloader screen
Yes, I know how to get into Bootloader, but How do I execute this stuff in bootloader?
I do not show a connection to ActiveSync (Or in this case, Windows Mobile Device Center) when I am in BootLoader.
Fenopy said:
Yes, I know how to get into Bootloader, but How do I execute this stuff in bootloader?
I do not show a connection to ActiveSync (Or in this case, Windows Mobile Device Center) when I am in BootLoader.
Click to expand...
Click to collapse
-remove sim and storage card
-hook your phone to your computer, and then go into bootloader while hooked to the computer
-try to run the regular stock rom utility while in bootloader
-if that does not work, then follow my instructions from above
OK...
I can ONLY get into Bootloader.
My Process:
-Load Bootloader...Ok
-Connect USB...Ok
-Start ActiveSync...Ok
-ACTIVESYNC, NOT CONNECTED..
-Start Stock ROM Utility
-No Device Connected
Going to try it with HERALD-USPL-beta3 instead of Stock-ROM now..
while in bootloader, read your spl number. is it lower than 4.0.0.0?
No.
Bootloader Screen:
IPL 4.10.0002
SPL 4.70.Yang
USB
EDIT:
How long Should I let herald-uspl.exe from Flash Center run before I give up on it?
your device should be able to run the ruu.exe provided by tmobile.
any luck with the uspl?
spacemonkey333 said:
your device should be able to run the ruu.exe provided by tmobile.
any luck with the uspl?
Click to expand...
Click to collapse
uspl doesnt seem to be going anywhere (10 min now, still step 1)
I am downloading a different Tmo rom (not the bat files i hope)
Will be trying that soon.
Thank you for your suggestions btw
are you getting any error messages?
if the ruu.exe doesn't run on the bootloader and uspl isn't working, then unfortunately, i am at a loss.
there are a few sites out there on tutorials for bricked wings... here is a link to one of them:
http://forum.xda-developers.com/showthread.php?t=417930
good luck man...wish i could help you more
spacemonkey333 said:
are you getting any error messages?
Click to expand...
Click to collapse
Okay, So now I am in a bit of a pickle... lolz
Ran the TMo Stock ROM...
It Kills my ActiveSync connection immediatly.. Doesnt see my phone.
So I reinstalled, restarted.
Retry...
Saw my phone.
Started to install. Got to 1%, then my phone booted out of BootLoader, now is back at the TouchIt Loading screen (where it is frozen).
EDIT1:
Yeah, I did the Recovery Process... It keeps going to 1% then Restarting.
EDIT2:
OMG, loading now!
Next Update Soon! (42%)
if you are getting to 1% and it is rebooting, then you should be able to use uspl to fully flash a rom. just put the nbh from your stock rom into the ruu folder and run uspl. that worked for me.
spacemonkey333 said:
if you are getting to 1% and it is rebooting, then you should be able to use uspl to fully flash a rom. just put the nbh from your stock rom into the ruu folder and run uspl. that worked for me.
Click to expand...
Click to collapse
OMG Back to Stock ROM! ****in Yey!
The Stock RUU was able to complete (When it rebooted @ 1%, I forced it back into BootLoader) it then rebooted again, but actually finished this time.
congrats
i've been through that process a long time ago i know how u feel lol
sweet. next time you want to flash a rom, just use uspl. it works for me flawlessly every time.
spacemonkey333 said:
sweet. next time you want to flash a rom, just use uspl. it works for me flawlessly every time.
Click to expand...
Click to collapse
Well, my problem came from ActiveSync... No matter what I did, It would disconnect. (This is after trying 6 DIFFERENT PCs [2 Vista] and failing) so I was trying other ways to Flash. Never again. Lolz.
EDIT:
Back at it... Flashing Hard-SPL now. lolz.
USPL totally works better... lolz.
well, its good to see that you are back in business
Hi,
I intended to do the Froyo OTA update for my Legend today. Started the download, it finished and wanted to start the installation.
During the installtion it started to boot loop, it got to around 98% every time and then booted again, doing that over and over several times.
After about 30st boot loops I plugged the battery to see if it would help, nope... now i get the white screen with green HTC text and after that I get
to a black background with a dark phone and a red triangle with an exclamation mark in it, waiting ca 2min and it will reboot again.
Is my phone bricked or is there something I can do?
Any help or suggestions would be very appriciated.
My phone is an unbranded HTC Legend, swedish.
HBOOT-0.43.0001
//Rightfoot
This should be in general. You need an RUU. Search the forums using the search tools provided
Well since I can't start the phone I can't use the RUU.
Beacause I can't use the RUU from the bootloader can't I?
Try entering the recovery mode and then use RUU update from a PC. Your phone is not branded and i think that you don't need goldcard to flash RUU.
And you should read more! There must be a hundreds of posts about this...
Thanks for the help.
Where do I find the RUU?
Tried http://shipped-roms.com/index.php?category=android&model=Legend but they dont start on my computer. Generating some kind of windows error message.
Rightfoot said:
Thanks for the help.
Where do I find the RUU?
Tried http://shipped-roms.com/index.php?category=android&model=Legend but they dont start on my computer. Generating some kind of windows error message.
Click to expand...
Click to collapse
The size of the Froyo update is wrong (only 4 MB). Try to download from different place.
You can use also LEGEIM image from here:
LEGEIMG_Legend_HTC_WWE_2.03.405.3_Radio_47.39.35.09_7.08.35.21_release_130330_signed.zip
Just put the files in the root of your SD and enter bootloader.
ogo2 said:
You can use also LEGEIM image from here:
LEGEIMG_Legend_HTC_WWE_2.03.405.3_Radio_47.39.35.09_7.08.35.21_release_130330_signed.zip
Click to expand...
Click to collapse
So downloaded the rom and renamed to update.zip, trying to update from recovery only gives me a signature verification failed
Am I doing anyhing wrong, feels like you leave som information for me to search for myself Thanks anyway.
Rightfoot said:
So downloaded the rom and renamed to update.zip, trying to update from recovery only gives me a signature verification failed
Am I doing anyhing wrong, feels like you leave som information for me to search for myself Thanks anyway.
Click to expand...
Click to collapse
Rename it to LEGEIMG.zip. Put it at the root of your SD card. Boot into recovery. It'll search for and then flash it automatically.
Or you can use the RUU, as suggested, following the guide in this post from the USB Brick thread http://forum.xda-developers.com/showpost.php?p=9889284&postcount=60.
E.E.
RUU actually contains what is called LEGEIMG.zip. This is not the ordinary update zip that can be flashed from recovery mode!
Hi everyone,
I bricked my friend's One.
1. Phone is brand new & I went through the steps to Unlock Bootloader, flash TWRP, Rooted.
2. Then copied custom ROM to sdcard. & went back to Recovery to flash it but couldnt find it. (it showed the ROM.zip in Window Explorer when I plugged the phone in, but didnt show in the Recovery).
So, I decided to format data (thinking I'll just boot up the phone & copy the custom ROM.zip into the phone again).
However, after I formatted data, Recovery says no OS to boot.
When i boot the phone, i'm stuck on the HTC white screen.
I downloaded 3 RUU.exe files (2 asia & 1 euro, my phone is for Asian market) but they are all incorrect versions.
I'm using Hasoon tool to ADB sideload the custom ROM.zip, the screen appears: Starting ADB sideload feature... & it takes forever....
nothing moving...
Please advice & help.
Thank you
--
ok, I found http://forum.xda-developers.com/showthread.php?t=2317986
I didnt put the ROM.zip in the right folder. my bad.
Everything's fixed.
Thanks for reading :laugh:
dsymbol said:
I'm using Hasoon tool...
Click to expand...
Click to collapse
That's your problem right there...don't use toolkits as they don't teach you anything!
Edit: nevermind, just saw you manged to find it...
( I posted this elsewhere, but i guess its beter in the actual HTCONE section) , mod feel free to delete my other one, thank you.
Good afternoon, !!!
First and foremost , I want to thank you all in advance for ANY and help, time & consideration with my current issue. I will try my best to be clear, and give all relevant info here in my first post. Please bear with me, I am pretty good when it comes to following directions, but i havent been able to find a CLEAR solution to this yet, and worried about further screwing up my phone.
** I use a mac. I currently dont have access to a PC, so i am looking for a mac remedy if possible.
I have an HTCONE m7. Tmobile.
- Bootloader - Unlocked
- S- ON
- Rooted
I kept getting a OTA software update notice for 5.14xxx, i understand the install kept failing due to the bootloader being unlocked and/or root. So after being annoyed for not able to get it, i began googling ways to get the update but to no avail. So i decided to do CM11, & recovery which i installed with no problem via, Cyanogenmod Installer.
After doing so, i realized i lost my Tmobile Wifi Calling (Yes, my own fault for not further checking that scenario before doing cm11), The wifi calling is needed 10000%, due to bad service in my apartment. Prior to finding out that cm11 doesnt contain the tmobile wifi calling , I attempted another system update thru the phone, (I assume it was updating cm11).
This is where the problem began, phone rebooted to Cyanogenmod simple recovery ,
1st few times that i tried = "apply update" > choose from internal storage , i searched different folders for the "update" file, but to no avail. The phone wouldnt start up, or install anything , and will just stay on the simple recovery. I even attempted an adb sideload. But couldnt figure that out correctly either.
After a few failed attempts, I tried wiping the phone, cache, factory reset etc. now the phone still stays on simple recovery, and all folders are gone, except for an o/ folder, that contains a clockworkmod folder, which contains nothing.
So now basically,Do i have to eventually get back to STOCK on this phone, to regain tmobile wifi calling ? IF So i need the easiest, mac friendly route to go .
Again, i thank you ALLLLL in advance, & my apologies if this is in the wrong section. Please note ive done my fair share of googling , and reading up on this. But consistently run into a problem.
OnlyEYEShine said:
Good afternoon, !!!
First and foremost , I want to thank you all in advance for ANY and help, time & consideration with my current issue. I will try my best to be clear, and give all relevant info here in my first post. Please bear with me, I am pretty good when it comes to following directions, but i havent been able to find a CLEAR solution to this yet, and worried about further screwing up my phone.
** I use a mac. I currently dont have access to a PC, so i am looking for a mac remedy if possible.
I have an HTCONE m7. Tmobile.
- Bootloader - Unlocked
- S- ON
- Rooted
I kept getting a OTA software update notice for 5.14xxx, i understand the install kept failing due to the bootloader being unlocked and/or root. So after being annoyed for not able to get it, i began googling ways to get the update but to no avail. So i decided to do CM11, & recovery which i installed with no problem via, Cyanogenmod Installer.
After doing so, i realized i lost my Tmobile Wifi Calling (Yes, my own fault for not further checking that scenario before doing cm11), The wifi calling is needed 10000%, due to bad service in my apartment. Prior to finding out that cm11 doesnt contain the tmobile wifi calling , I attempted another system update thru the phone, (I assume it was updating cm11).
This is where the problem began, phone rebooted to Cyanogenmod simple recovery ,
1st few times that i tried = "apply update" > choose from internal storage , i searched different folders for the "update" file, but to no avail. The phone wouldnt start up, or install anything , and will just stay on the simple recovery. I even attempted an adb sideload. But couldnt figure that out correctly either.
After a few failed attempts, I tried wiping the phone, cache, factory reset etc. now the phone still stays on simple recovery, and all folders are gone, except for an o/ folder, that contains a clockworkmod folder, which contains nothing.
So now basically,Do i have to eventually get back to STOCK on this phone, to regain tmobile wifi calling ? IF So i need the easiest, mac friendly route to go .
Again, i thank you ALLLLL in advance, & my apologies if this is in the wrong section. Please note ive done my fair share of googling , and reading up on this. But consistently run into a problem.
Click to expand...
Click to collapse
Here is a TWRP nandroid backup. You will have to put TWRP 2.6.3.3 on your phone. You will unzip the file and the resulting folder you will put on your phone in the following directory: //sdcard/TWRP/BACKUP/<Serial #>/<Name_of_folder>. If you are not able to get TWRP on your phone and the folder on your phone then you will need to find a Windows machine. Here is what you will need to do:
** Extract the RUU and grab the rom.zip file. This is the most important file you need from the RUU and afterwards you can delete the RUU exe if you want. To get the rom.zip from your RUU exe file, you just need to run the RUU exe file once, and then when the window is ready and waiting for you to press on the "Next" button, just leave it open and go to your temp folder. I'm using Windows XP SP3 32-bit and my temp folder is located at this path: C:\Documents and Settings\Administrator\Local Settings\Temp. Now, you will see several files and folders. Sort everything in that temp folder based on "Date Modified" with the most recent folder showing up above all other folders. This is the folder you want. The folder name will be bunch of letters and numbers. Inside that folder you will find several files, but what you need is rom.zip and android-info.txt. Copy both these files and paste them somewhere safe on your hard drive. The android-info.txt contains crucial information about the compatibility of that RUU for your phone.
** Go to your bootloader. Do:
Code:
fastboot oem lock
fastboot oem rebootRUU
This will reboot your HTC One and you will see a black screen with a silver HTC logo. Now, you will need to access the rom.zip file and flash it. I have copied my rom.zip to my adb folder located at: C:/mini-sdk/rom.zip. So, type:
Code:
fastboot flash zip C:/mini-sdk/rom.zip
Don't touch anything during the flash process. It will start and after some time, you will see FAILED error. Don't worry; it's the file preparation process if you have firmware higher than that of the RUU. Just do the same command again and the flash process will complete successfully this time. Look at the Command Prompt to know when the flash is complete. At the same time if you look at your phone, you will notice a green progress bar. When the flashing is complete on the Command Prompt, you will notice that the green bar is stuck at about 95%. This is normal. It's just a bug in the progress bar - what matters is the output from the Command Prompt window.
** Then, you reboot. Do:
Code:
fastboot reboot
This will restart your phone. Let it boot up. It might take a little longer for the first boot up sequence. You will then have completely stock software (firmware & ROM). Go to your bootloader and check that you are S-ON/OFF and Bootloader lock/unlock are unchanged from before the RUU rom.zip flashing procedure. You can now also receive OTA updates.
majmoz said:
Here is a TWRP nandroid backup. You will have to put TWRP 2.6.3.3 on your phone. You will unzip the file and the resulting folder you will put on your phone in the following directory: //sdcard/TWRP/BACKUP/<Serial #>/<Name_of_folder>. If you are not able to get TWRP on your phone and the folder on your phone then you will need to find a Windows machine. Here is what you will need to do:
** Extract the RUU and grab the rom.zip file. This is the most important file you need from the RUU and afterwards you can delete the RUU exe if you want. To get the rom.zip from your RUU exe file, you just need to run the RUU exe file once, and then when the window is ready and waiting for you to press on the "Next" button, just leave it open and go to your temp folder. I'm using Windows XP SP3 32-bit and my temp folder is located at this path: C:\Documents and Settings\Administrator\Local Settings\Temp. Now, you will see several files and folders. Sort everything in that temp folder based on "Date Modified" with the most recent folder showing up above all other folders. This is the folder you want. The folder name will be bunch of letters and numbers. Inside that folder you will find several files, but what you need is rom.zip and android-info.txt. Copy both these files and paste them somewhere safe on your hard drive. The android-info.txt contains crucial information about the compatibility of that RUU for your phone.
** Go to your bootloader. Do:
Code:
fastboot oem lock
fastboot oem rebootRUU
This will reboot your HTC One and you will see a black screen with a silver HTC logo. Now, you will need to access the rom.zip file and flash it. I have copied my rom.zip to my adb folder located at: C:/mini-sdk/rom.zip. So, type:
Code:
fastboot flash zip C:/mini-sdk/rom.zip
Don't touch anything during the flash process. It will start and after some time, you will see FAILED error. Don't worry; it's the file preparation process if you have firmware higher than that of the RUU. Just do the same command again and the flash process will complete successfully this time. Look at the Command Prompt to know when the flash is complete. At the same time if you look at your phone, you will notice a green progress bar. When the flashing is complete on the Command Prompt, you will notice that the green bar is stuck at about 95%. This is normal. It's just a bug in the progress bar - what matters is the output from the Command Prompt window.
** Then, you reboot. Do:
Code:
fastboot reboot
This will restart your phone. Let it boot up. It might take a little longer for the first boot up sequence. You will then have completely stock software (firmware & ROM). Go to your bootloader and check that you are S-ON/OFF and Bootloader lock/unlock are unchanged from before the RUU rom.zip flashing procedure. You can now also receive OTA updates.
Click to expand...
Click to collapse
Thanks for the info !!!,
But right off of the top, i am confused. I am currently downloading TMRP nandroid back up, as you said in beginning. Thing is i am unaware how to get that file onto my phone. Since it is stuck on the recovery page.... (DL is going to take a while on this machine), But if this fails, ill probably end up just tossing the phone, as i dont know anyone , nor have access to a PC machine. Sadly.
update - will attempt to push this thru via Terminal / adb will keep u posted !
-Update .. @majmoz well, i got hold of a PC laptop, did an adb / fastboot installed, dl'd the RUU, but i cant find the file from it after running the RUU. I even did cmd - Echo %temp% to make sure i was in the correct temp folder etc. Searched every sub folder there , and no zip files , or android.txt files was found . and i sorted them as u said as well.
Will continue trying tho...
Updated again - Well this time as RUU was installing again, i went to the temp files faster, and found 2 files Rom_01 & Rom_02 both zip files. But was unable to find any android text file. So now im at a standstill.
OnlyEYEShine said:
update - will attempt to push this thru via Terminal / adb will keep u posted !
-Update .. @majmoz well, i got hold of a PC laptop, did an adb / fastboot installed, dl'd the RUU, but i cant find the file from it after running the RUU. I even did cmd - Echo %temp% to make sure i was in the correct temp folder etc. Searched every sub folder there , and no zip files , or android.txt files was found . and i sorted them as u said as well.
Will continue trying tho...
Click to expand...
Click to collapse
The RUU Update Window should still be on the computer when you are looking for the files. Once the RUU goes past the first screen, the folder will be erased. You should also sort the /Temp folder by date so the most recent folder is at the top.
majmoz said:
The RUU Update Window should still be on the computer when you are looking for the files. Once the RUU goes past the first screen, the folder will be erased. You should also sort the /Temp folder by date so the most recent folder is at the top.
Click to expand...
Click to collapse
If i would of refreshed the page i would of seen your response, as i just re-editted my last post. with another update. =0)
I found 2 files with rom, Rom_01 & Rom_02 , both are zip files. but i cant find any android text file .
another thing, i am trying to find adb devices , but it is not locating my phone . I was able to earlier reboot into bootloader , etc. Now it tells me repeatedly that device is not found , i have tried adb kill-server, start-server etc. .. and phone is still on cyanogen simple recovery screen . .
Thanks again for ur time & help .. .definetly is appreciated !
OnlyEYEShine said:
If i would of refreshed the page i would of seen your response, as i just re-editted my last post. with another update. =0)
I found 2 files with rom, Rom_01 & Rom_02 , both are zip files. but i cant find any android text file .
another thing, i am trying to find adb devices , but it is not locating my phone . I was able to earlier reboot into bootloader , etc. Now it tells me repeatedly that device is not found , i have tried adb kill-server, start-server etc. .. and phone is still on cyanogen simple recovery screen . .
Thanks again for ur time & help .. .definetly is appreciated !
Click to expand...
Click to collapse
Keep both ROM files and save them for future use. Since you are able to use the PC, I would just run the RUU from the PC. Then in the future try to figure out how to run the two ROM files on your Mac. Just start the RUU again and let it do its thing.
majmoz said:
Keep both ROM files and save them for future use. Since you are able to use the PC, I would just run the RUU from the PC. Then in the future try to figure out how to run the two ROM files on your Mac. Just start the RUU again and let it do its thing.
Click to expand...
Click to collapse
Hey hey , good morning. Had some errands to do last nite then fell asleep. Going to attempt this again today . Oh, and i did run the RUU on the PC so thats where ill keep them also.
Will attempt to see if i can even connect to the phone with ADB, it seemed as if i was unable to last nite.
-update I got the phone to load to bootloader, & to fastboot usb I will try now to attempt this after coffee.. =0)
HAHAHAHHAHA ,, Oh man. Ok well being that it was pretty late last nite, and i had just woken up earlier .... I didnt realize that the RUU actually does the entire process on the PC. and that i DIDNT need to use cmd., and adb etc.
I want to thank you a TON @majmoz With my day or two of aggravation , then to just not get it right last nite.. I think i wasnt there mentally to actually read and pay attention.
My phone is in set up mode now. So i am 99% sure it is all good... Again, thanks , i definetly appreciate it !
OnlyEYEShine said:
HAHAHAHHAHA ,, Oh man. Ok well being that it was pretty late last nite, and i had just woken up earlier .... I didnt realize that the RUU actually does the entire process on the PC. and that i DIDNT need to use cmd., and adb etc.
I want to thank you a TON @majmoz With my day or two of aggravation , then to just not get it right last nite.. I think i wasnt there mentally to actually read and pay attention.
My phone is in set up mode now. So i am 99% sure it is all good... Again, thanks , i definetly appreciate it !
Click to expand...
Click to collapse
Glad you are back in business! :good:
@majmoz Hey i tried sending a PM earlier . but i see it never went thru in my sent Messages.
Just wondering if you can help me one last time. As i stated, i MUST have tmobile wifi calling. I initially had my bootloader unlocked months ago, and only rooted it few days before this brick issue.
Now since i did this process to fix the phone, i see bootloader = Relocked.
I dont want to add any custom roms etc, I simple want to root the device again. I know when i just did it , it was quick n easy and simple. But as im googling for the process now, i cant seem to find any that is similar to what i just did a few days ago. The processes seem extremely long. I think i just added a superuser apk of sorts , and it rooted.
Thanks again !
OnlyEYEShine said:
@majmoz Hey i tried sending a PM earlier . but i see it never went thru in my sent Messages.
Just wondering if you can help me one last time. As i stated, i MUST have tmobile wifi calling. I initially had my bootloader unlocked months ago, and only rooted it few days before this brick issue.
Now since i did this process to fix the phone, i see bootloader = Relocked.
I dont want to add any custom roms etc, I simple want to root the device again. I know when i just did it , it was quick n easy and simple. But as im googling for the process now, i cant seem to find any that is similar to what i just did a few days ago. The processes seem extremely long. I think i just added a superuser apk of sorts , and it rooted.
Thanks again !
Click to expand...
Click to collapse
Here is a step by step guide with pictures. This is called the HTCDev method and it is pretty standard. It just looks like a lot of steps but it isn't that bad.
majmoz said:
Here is a step by step guide with pictures. This is called the HTCDev method and it is pretty standard. It just looks like a lot of steps but it isn't that bad.
Click to expand...
Click to collapse
Gotcha, will try this in an hour or so . Have some errands to run. Thanks again !
OnlyEYEShine said:
Gotcha, will try this in an hour or so . Have some errands to run. Thanks again !
Click to expand...
Click to collapse
Keep this for future reference on how to flash the two RUU ROM zip files:
From nkk71's SuperGUIDE to returning 100% back to stock - Post #1211
http://forum.xda-developers.com/showpost.php?p=55921790&postcount=1211
How to flash two RUU ROM zip files
Code:
[B]fastboot oem rebootRUU
fastboot flash zip RUU_ROM_1.zip [COLOR="Red"][I]<-- hboot preupdate[/I][/COLOR]
fastboot flash zip RUU_ROM_1.zip[COLOR="Red"][I] <-- rest of the files in "1"[/I][/COLOR]
fastboot flash zip RUU_ROM_2.zip [I][COLOR="Red"]<-- files in "2" (kernel, touchscreen drivers 2, wipe userdate)[/COLOR][/I]
fastboot reboot-bootloader
[/B]
Click to expand...
Click to collapse
Help! My Motorola RAZR I XT890 cannot be "unbricked" and I tried several methods...
Hello!
I unlocked the bootloader successfully, then I tried to root my phone using The Razr guy method and I used the "RAZRi_Root_Windows" file, while rooting my phone went to the "warning bootloader unlocked" screen and it just loops forever from that screen, the bat file, showed that it successfully rooted my phone. I tried to fix it using rsd lite, but it never detects my phone, so I searched for a way to make my pc able to detect it, so I found I could use Intel xFSTK, installed it but still nothing it doesn't appear as shown in the tutorial, I even downloaded the dll file that it needed to run, but after running the xFSTK DLDR or something like that, the application is completely empty, and I saw it should show some tools to download something. Also tried using Linux Zorin, but it only says that my XT890 cannot be accessed and shows an usb error code.
I am able to enter the fastboot screen, the one you get by pressing POWER and VOLUME DOWN, also it charges my batter completely normal. Also my pc is able to show that the XT890 is connected, but only before installing the drivers and it shows the CD installer for the Motorola Device Manager and some other files (all this while looping), and if I enter the fastboot flash mode, it appears as "fastboot smi S", with a yellow triangle and an exclamation sign while in Windows device manager. It has Jelly Bean update from telcel (mexico), and I already have the xml.zip file to reinstall it.
I use windows 8.1 , and as mentioned Linux Zorin on my PC.
Could some help me with it...if you now how to fix it please list every single step on how to do it T_T, THANKS IN ADVANCE!!!!
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Hazou said:
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Click to expand...
Click to collapse
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
weird_user said:
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
Click to expand...
Click to collapse
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Thanks again!!!
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
I am able to enter RECOVERY MODE NOW (I installed CWM, before this I was only able to see the android lying on the floor ans saty dead right there, I was supposed to press Volume + and - and the camera button at the same time, but nothing happened), it seems to be easier to unbrick it this way, but now the problem is that after I follow the steps to reinstall the original ROM, it aborts installation. I read this may be caused due to a file on the zip file, I looked for it, but nor the Folder META-INF, whic is supposed to contain a "update-script" file, nor that file is anywhere in the ROM folder...
I've even tried cyanogenmod (after first trying Telcel original ROM and then the retail GB ROM) cuz it actually contains the folder previously mentioned and the file is in a different path, but it is there, I modified it, but got a "Can't open tmd/update.zip (bad) Installation aborted" error...I don't know what else to do T_T...
Note: I also used sideload and CWM to install it, but the same thing happens. Also checked some other post about this issue, but none has helped me...
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Hazou said:
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Click to expand...
Click to collapse
It's done! Thanks!
I actually used another computer with windows 10, also I used RSD Lite and it worked just fine, now I have the stock ROM from Telcel and it it is working almost normal. The only abnormality I've seen is that my phone turns itself off when battery is at 20%, I searched info about that problem and it says I may re calibrate the battery, so it may work fine again, but now I need to root again to be able to do that T_T, hope it works this time...
THANKS! again!