Related
Hi
I made a very stupid mistake
I used the tool to root my xoom wifi model
I used the tool in this thread
http://forum.xda-developers.com/showthread.php?t=1011196
I tried to post this issue in the thread but I did not have the permissions.
by mistake I used the root of the 3G model
I followed the steps and everything was ok
I tried the unroot and here is the deadly (hopefully not) mistake
the xoom stops and first screen and refuses to boot
Did I brick my device??
Is there a way to resolve this problem??
Thanks
Yes, you have bricked it. Fastboot won't work at this point, so your only option is probably to return it.
-Jim (who's on his 2nd xoom)
Sent from my Xoom using Tapatalk
nawialkair said:
Hi
I made a very stupid mistake
I used the tool to root my xoom wifi model
I used the tool in this thread
http://forum.xda-developers.com/showthread.php?t=1011196
I tried to post this issue in the thread but I did not have the permissions.
by mistake I used the root of the 3G model
I followed the steps and everything was ok
I tried the unroot and here is the deadly (hopefully not) mistake
the xoom stops and first screen and refuses to boot
Did I brick my device??
Is there a way to resolve this problem??
Thanks
Click to expand...
Click to collapse
what does the first screen say? failed boot image?
BeagleBoy said:
Yes, you have bricked it. Fastboot won't work at this point, so your only option is probably to return it.
-Jim (who's on his 2nd xoom)
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
That's the thing I did not want to hear but expected it.
============================================
znfrazier said:
what does the first screen say? failed boot image?
Click to expand...
Click to collapse
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
nawialkair said:
That's the thing I did not want to hear but expected it.
============================================
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
Click to expand...
Click to collapse
Can you see the xoom in /fastboot devices? See if you can access you xoom from the computer. I actually did the same thing and got mine in working order.
nawialkair said:
That's the thing I did not want to hear but expected it.
============================================
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
Click to expand...
Click to collapse
Try doing this real quick, the best that can happen is that you can turn this around. You may NOT in fact be bricked. I made the mistake of doing this also, but I figured it is just like when I was using the Danger SPL on the G1 and I had to at least find a way.
So, do this real quick if you know how.
1. Power on and press Vol - at the same time
2. Open a command prompt to your ADB file and type in fastboot oem unlock
3. If this lets you in (it may not) go through the regular procedure of pressing Vol -+-+
4. It will format and you should know if it is in fact bricked or not because it won't boot up.
5. ******
6. Profit???
Let us know how it goes.
znfrazier said:
Can you see the xoom in /fastboot devices? See if you can access you xoom from the computer. I actually did the same thing and got mine in working order.
Click to expand...
Click to collapse
Yes I can see it
Thank you
stevenege said:
Try doing this real quick, the best that can happen is that you can turn this around. You may NOT in fact be bricked. I made the mistake of doing this also, but I figured it is just like when I was using the Danger SPL on the G1 and I had to at least find a way.
So, do this real quick if you know how.
1. Power on and press Vol - at the same time
2. Open a command prompt to your ADB file and type in fastboot oem unlock
3. If this lets you in (it may not) go through the regular procedure of pressing Vol -+-+
4. It will format and you should know if it is in fact bricked or not because it won't boot up.
5. ******
6. Profit???
Let us know how it goes.
Click to expand...
Click to collapse
I did that
and it started the format
After the boot, it stopped at the same place
Motorola's Logo and Dual Core
What's next??
thanks
root using the instructions in this thread it should fix your problem
http://forum.xda-developers.com/showthread.php?t=1010568
nawialkair said:
Yes I can see it
Thank you
I did that
and it started the format
After the boot, it stopped at the same place
Motorola's Logo and Dual Core
What's next??
thanks
Click to expand...
Click to collapse
you should try flashing the boot.img used to root i believe its tiamat 1.1.6 and the system.img for wifi. i have the stock system.img if you need it. hopefully that would git ya to boot atleast. MAKE SURE THAT IT IS WIFI ONLY.
Go here and follow the second post I posted. This will help you do this without downloading the files because they are already there.
Give it a shot at least
stevenege said:
Go here and follow the second post I posted. This will help you do this without downloading the files because they are already there.
Give it a shot at least
Click to expand...
Click to collapse
did they fix the boot prob with the one click? i haven't tried it.
znfrazier said:
did they fix the boot prob with the one click? i haven't tried it.
Click to expand...
Click to collapse
Yes, it has all been fixed. There still seems to be an issue with SU rights until you download BusyBox and no clue why.
I have been testing the WiFi one constantly and have not had any major hickups.
stevenege said:
Yes, it has all been fixed. There still seems to be an issue with SU rights until you download BusyBox and no clue why.
I have been testing the WiFi one constantly and have not had any major hickups.
Click to expand...
Click to collapse
good good. ill have to check it out. i still need to try out the pimp my xoom. ill post over there haha. gotta stay on topic.
Thanks ALL
I flashed Tiamat 1.1.6 boot.img
the problem is that when using this command:
adb remount
I get
error: device not found
The xoom is defined in the device manager as
Android adb Interface
nawialkair said:
Thanks ALL
I flashed Tiamat 1.1.6 boot.img
the problem is that when using this command:
adb remount
I get
error: device not found
The xoom is defined in the device manager as
Android adb Interface
Click to expand...
Click to collapse
Sounds like you are probably bricked :-/
Can I get the stock boot image
I just want to try that last option
I flashed the stock img and system img
It works fine
Yaaaaa
Thanks very much
Thanks very much
nawialkair said:
I flashed the stock img and system img
It works fine
Yaaaaa
Thanks very much
Thanks very much
Click to expand...
Click to collapse
Told ya haha, save those files on your computer for next time. I keep them in close reach just incase something happens. if you have any other problems give me a holla. glad everything is working again.
I think I'm more screwed than OP because I was already unlocked and rooted. Then locked my wifi xoom with the 3g one click tool. Yes I know that was very stupid but I was wondering what are my options?
Take it back to Amazon?
Use the following method in this thread?
Wait for SBF?
Thank you your time and sorry if I hijacked this thread.
jarretf said:
I think I'm more screwed than OP because I was already unlocked and rooted. Then locked my wifi xoom with the 3g one click tool. Yes I know that was very stupid but I was wondering what are my options?
Take it back to Amazon?
Use the following method in this thread?
Wait for SBF?
Thank you your time and sorry if I hijacked this thread.
Click to expand...
Click to collapse
It relocked? Yikes... I don't trust those 1-click things. I need to know what's going on step by step. My first Xoom got bricked when I thought I had untainted OEM image files and relocked it. There's really no reason to relock a Wifi Xoom right now.
Anyway, if it relocked, you might have been in the same boat I was where the computer wouldn't recognize the Xoom in Fastboot mode or RSD mode. And I went and got it exchanged at that point.
Oh, if RSD Lite can't see your Xoom in RSD mode, you might be out of luck. SBF won't help if RSD Lite can't see your Xoom. BUT, if it does see it, it sounds like you can flash the 3G/4G SBF from Motorola/Verizon and to get sorta running, then use Fastboot to overwrite the boot and system partitions.
Hey Guys.
So i am having this problem for about 2 weeks now. You won't believe how many threads i read, to find a solution to my problem.
So it seems like i soft bricked my sgs4g. It is in a mode, where i can't do anything.
There is a phone on the left, a warning triangle in the middle, and a computer on the right side. Under that it says "firmware upgrade fail! Try using recovery mode".
So, i really don't know much about flashing, rooting, cwm etc.. So i got some help by a friend of mine to install some rom i can't quite remember the name. It had a lag-fix in it, cwm, root and also a overclocked processor. It worked perfectly except that it didnt' recognize my Sim. So i tried to flash it to a coupel other roms, but everywhere the same problem. Eventually, odin had an error, and now i am in this freaking mode where i can't get out of. Volume up + volume down and plugging in usb cord won't work. since my phone doesnt work, i can't really install adb, to fix the download mode, and even a usb jig won't bring me to the download mode. I really have no idea how i can get out of here. I would really appreciate any kind of help, and i hope that i can get this thing fixed.
If you need any further information about my phone, just ask.
Thanks for everybody who can or wants to help!!
max aka de4dw0lf
de4dw0lf said:
There is a phone on the left, a warning triangle in the middle, and a computer on the right side.
Click to expand...
Click to collapse
Does it look like the attached pic? Or similar?
it looked like that before. than i tried to falsh it a couple times and now it looks different. It looks more modern now. and there is an actual text below it!
de4dw0lf said:
Hey Guys.
So i am having this problem for about 2 weeks now. You won't believe how many threads i read, to find a solution to my problem.
So it seems like i soft bricked my sgs4g. It is in a mode, where i can't do anything.
There is a phone on the left, a warning triangle in the middle, and a computer on the right side. Under that it says "firmware upgrade fail! Try using recovery mode".
So, i really don't know much about flashing, rooting, cwm etc.. So i got some help by a friend of mine to install some rom i can't quite remember the name. It had a lag-fix in it, cwm, root and also a overclocked processor. It worked perfectly except that it didnt' recognize my Sim. So i tried to flash it to a coupel other roms, but everywhere the same problem. Eventually, odin had an error, and now i am in this freaking mode where i can't get out of. Volume up + volume down and plugging in usb cord won't work. since my phone doesnt work, i can't really install adb, to fix the download mode, and even a usb jig won't bring me to the download mode. I really have no idea how i can get out of here. I would really appreciate any kind of help, and i hope that i can get this thing fixed.
If you need any further information about my phone, just ask.
Thanks for everybody who can or wants to help!!
max aka de4dw0lf
Click to expand...
Click to collapse
First off, you are in an alternate download mode. Just flash Odin as normal with a stock ROM and all will be good again.
Second off, what ROM did you flash that has an overclocked processor? We don't have a kernel that supports overclocking yet, at least for gb.
As for the SIM card, I've had that problem before. It's from not wiping /data /system /cache before flashing. Once you Odin back to stock, it should work. If not, you will have to contact your service provider to get a new one.
de4dw0lf said:
it looked like that before. than i tried to falsh it a couple times and now it looks different. It looks more modern now. and there is an actual text below it!
Click to expand...
Click to collapse
That is still download mode. Use Heimdall One Click.
i already tried to flash back to stock a couple times. but it just won't work, because odin always gets an error. Could you send me a link to the right stock version for my sgs4g? maybe i am just using the wrong one..
also, i want to avoid sending it back to t-mobile, because my phone is a refurbished one, and i am not quite sure about the warranty..
de4dw0lf said:
i already tried to flash back to stock a couple times. but it just won't work, because odin always gets an error. Could you send me a link to the right stock version for my sgs4g?
Click to expand...
Click to collapse
Use Heimdall One Click. The one with bootloaders. It will work. Read the OP to a T.
de4dw0lf said:
i already tried to flash back to stock a couple times. but it just won't work, because odin always gets an error. Could you send me a link to the right stock version for my sgs4g? maybe i am just using the wrong one..
also, i want to avoid sending it back to t-mobile, because my phone is a refurbished one, and i am not quite sure about the warranty..
Click to expand...
Click to collapse
Click on the Lightning Zap link in my signature... Then click on the link called Removing the Gremlins in the OP
Read the whole post. The link will give you KG4 and Odin and the necessary drivers...
If you already have odin setup use this http://forum.xda-developers.com/showthread.php?t=1353176 It's the official update to Gingerbread.
alright
Alright. i will try the things you guys sent me, and i will tell you later if it worked.
Thanks a lot!!! i hope it works^^
I'm going through the exact same problem right now! But this happened to me using Heimdall. My phone is still recognized by Heimdall but when I try to reflash it I get this in the command prompt:
[C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB 3DC9DDF\heimdall-win32\heimda
ll.exe, flash, --pit, C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB 3DC9DDF\
Sgs4g.pit, --6, C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB 3DC9DDF\zImage
, --7, C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB 3DC9DDF\zImage-1, --22,
C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB 3DC9DDF\factoryfs.rfs, --23,
C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB 3DC9DDF\data.rfs, --24, C:\DOC
UME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DD F\cache.rfs, --11, C:\DOCUME~1
\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\mod em.bin]
and this in the Heimdall window:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
KERNEL upload failed!
Ending session...
i am too stupid
Ok, i am probably just way too stupid, but i can't find the download for heimdall one-click.
ohh. i get it now. but when i hit enter after typing in:
"java -jar T959V-UVKJ6-One-Click.jar"
the following message comes up:
Unable to access karfoöe T959V-UVKJ6-One-Click
Any ideas?
de4dw0lf said:
ohh. i get it now. but when i hit enter after typing in:
"java -jar T959V-UVKJ6-One-Click.jar"
the following message comes up:
Unable to access karfoöe T959V-UVKJ6-One-Click
Any ideas?
Click to expand...
Click to collapse
Did you download java?
---------- Post added at 11:18 PM ---------- Previous post was at 11:16 PM ----------
DarsOnMars said:
I'm going through the exact same problem right now! But this happened to me using Heimdall.
Click to expand...
Click to collapse
You may have a bad download. You might try redownloading the file.
java is installed, i might have fixed that problem though. i think my download wasn't quite finished, because when i updated java, it wanted me to close firefox..
so, because my phone is not in the actual download mode, it won't find any drivers to install.. can't i just install them manually?
de4dw0lf said:
so, because my phone is not in the actual download mode, it won't find any drivers to install.. can't i just install them manually?
Click to expand...
Click to collapse
Here is my recommendation...
First used the attached .zip (assuming you are on a 64 bit machine) and uninstall all samsung and android drivers.
Then start over with Heimdall One Click. It will tell you whether you have the drivers you need or not, and if you do not, it will put up directions, send you to zadig and tell you what you need to do.
And you are in download mode.
Heimdall uses different drivers then ODIN.
Go here then and download 32 bit USBDeView.
I recommend restarting your machine after uninstalling drivers.
im on 32 bit
de4dw0lf said:
im on 32 bit
Click to expand...
Click to collapse
By the way... I recommended downloading the bootloader one click in case whatever you previously flashed was not for our device and changed your bootloaders.
"java -jar T959V-UVKJ6-One-Click.jar" --> is not the bootloader download.
SMS-KJ6-beta2d_Stock-Rom_with_Bootloaders-One-Click.jar = bootloader download.
hmm.. so it tells me to select Samsung USB Composite device, but it's not there.. :/
i am downloading the one "Download SMS KJ6 (beta2d) Kernel Stock Rom with Bootloaders" right now.
And after i am done im gonna restart my computer.
Okay, so I have used RSD Lite before with no problem. I need to flash my entire device back to stock before tomorrow, but the program is not reading my phone. Motorola Device Manager is installed, same setup I had last time I had to flash after soft bricking...I can't figure it out. Any help would be very appreciated. Thank you.
Moto Q stock with Arrrghhh's kernel v.0.10
Have you entered AP Fastboot mode? Hold both volume button and power. You'll see bootmenu. And navigate using volume down and select AP Fastboot using volume up.
Sent from my XT897 using Tapatalk 2
No Go in Fastboot AP
huatz84 said:
Have you entered AP Fastboot mode? Hold both volume button and power. You'll see bootmenu. And navigate using volume down and select AP Fastboot using volume up.
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, totally know what to do, and what order to do it in, only RSD Lite will not acknowledge my device! Crazy, cause I just flashed stock image ASA 14 about 3 weeks ago, no problems.
Nevermind... hehe
---------- Post added at 09:25 PM ---------- Previous post was at 09:10 PM ----------
Are you in Windows? I find Windows pretty annoying when it comes to certain drivers. You might have a look in Device Manager while your phone is plugged in(maybe check with the phone is fastboot mode too), and see if there are any Moto related drivers that have a yellow exclamation point. If so, perhaps reinstalling Device Manager will fix it? Good luck
yogi2010 said:
Nevermind... hehe
---------- Post added at 09:25 PM ---------- Previous post was at 09:10 PM ----------
Are you in Windows? I find Windows pretty annoying when it comes to certain drivers. You might have a look in Device Manager while your phone is plugged in(maybe check with the phone is fastboot mode too), and see if there are any Moto related drivers that have a yellow exclamation point. If so, perhaps reinstalling Device Manager will fix it? Good luck
Click to expand...
Click to collapse
Tried uninstalling and reinstalling Moto Device Manager 3 times...no. Tried RSD Lite versions 5.7 through 6.1...nothing. Is there an actual driver pack I can install that would have the appropriate drivers?
(I have a dual boot laptop, Ubuntu and Win 7, using Windows)
Moto Q stock with Arrrghhh's kernel v.0.10
galacticservant said:
Tried uninstalling and reinstalling Moto Device Manager 3 times...no. Tried RSD Lite versions 5.7 through 6.1...nothing. Is there an actual driver pack I can install that would have the appropriate drivers?
(I have a dual boot laptop, Ubuntu and Win 7, using Windows)
Moto Q stock with Arrrghhh's kernel v.0.10
Click to expand...
Click to collapse
I do have a driver installer downloaded on my computer, but I don't know if it would help you. I will attach it here just in case.
I had this issue a month back, but Moto Device Manager ended up being the solution for me. I have RSD Lite 6.1.5, and it sill recognizes my device in fastboot mode.
edit: the site wouldn't let upload the files for some reason, so I used Dropbox. here is the driver installer I have, but i'm not sure, it might not have solved the issue for me. also, here is RSD Lite 6.1.5 in case you don't have it and wanna try it:
https://dl.dropboxusercontent.com/u/18474790/USB_Drivers_64_bit_4.6.5.zip
https://dl.dropboxusercontent.com/u/18474790/RSDLite6.1.5.zip
hope you get it working,,, i'm sure you will somehow..
yogi2010 said:
I do have a driver installer downloaded on my computer, but I don't know if it would help you. I will attach it here just in case.
I had this issue a month back, but Moto Device Manager ended up being the solution for me. I have RSD Lite 6.1.5, and it sill recognizes my device in fastboot mode.
edit: the site wouldn't let upload the files for some reason, so I used Dropbox. here is the driver installer I have, but i'm not sure, it might not have solved the issue for me. also, here is RSD Lite 6.1.5 in case you don't have it and wanna try it:
https://dl.dropboxusercontent.com/u/18474790/USB_Drivers_64_bit_4.6.5.zip
https://dl.dropboxusercontent.com/u/18474790/RSDLite6.1.5.zip
hope you get it working,,, i'm sure you will somehow..
Click to expand...
Click to collapse
Yeah, I'm sure somehow that I will...thanks for the files, I'll try that now. Oh, by the way, you should check out the Dev Host site (google it), they provide free file uploading and sharing for, well, developers (or anyone for that matter). Only 500 MBs worth of storage is provided for free, but that really is all I need. Anyway, I'll try your advice and let ya know.
***by the way, I need drivers for 32 bit, not 64***
Moto Q stock with Arrrghhh's kernel v.0.10
yogi2010 said:
I do have a driver installer downloaded on my computer, but I don't know if it would help you. I will attach it here just in case.
I had this issue a month back, but Moto Device Manager ended up being the solution for me. I have RSD Lite 6.1.5, and it sill recognizes my device in fastboot mode.
edit: the site wouldn't let upload the files for some reason, so I used Dropbox. here is the driver installer I have, but i'm not sure, it might not have solved the issue for me. also, here is RSD Lite 6.1.5 in case you don't have it and wanna try it:
https://dl.dropboxusercontent.com/u/18474790/USB_Drivers_64_bit_4.6.5.zip
https://dl.dropboxusercontent.com/u/18474790/RSDLite6.1.5.zip
hope you get it working,,, i'm sure you will somehow..
Click to expand...
Click to collapse
No dice, RSD still not reading device...no freaking clue
galacticservant said:
No dice, RSD still not reading device...no freaking clue
Click to expand...
Click to collapse
damn, that sucks! did you ever check Device Manager in the Control Panel. i remember seeing a missing Moto driver there, but then again, that led me on a driver search, which led me to Moto Device Manager. did you completely uninstall it first before reinstalling it?
i dunno, just throwing out ideas here lol. otherwise, you might be able to just fastboot flash the necessary components from the FXZ file to get your setup back to stock. or else use a stock TWRP backup, then reflash stock recovery. hope you get it
yogi2010 said:
damn, that sucks! did you ever check Device Manager in the Control Panel. i remember seeing a missing Moto driver there, but then again, that led me on a driver search, which led me to Moto Device Manager. did you completely uninstall it first before reinstalling it?
i dunno, just throwing out ideas here lol. otherwise, you might be able to just fastboot flash the necessary components from the FXZ file to get your setup back to stock. or else use a stock TWRP backup, then reflash stock recovery. hope you get it
Click to expand...
Click to collapse
Yup, used moto-fastboot.exe to push files FZB fles to device. All was okay until trying to flash system.img.ext4. Had error message. My battery was okay though, but said there was problem with multiflash...any ideas
Sent from my SPH-M930 using xda app-developers app
Try another SD-Card, I had problems with my 32GB Samsung SD-Card.
Loader009 said:
Try another SD-Card, I had problems with my 32GB Samsung SD-Card.
Click to expand...
Click to collapse
RSD Lite will have a hard time reading device due to a SD card?
Sent from my SPH-M930 using xda app-developers app
Sorry, I was thinking about nandroid and TWRP, not of RSD Lite...
My mistake.
Entering AP Fastboot
huatz84 said:
Have you entered AP Fastboot mode? Hold both volume button and power. You'll see bootmenu. And navigate using volume down and select AP Fastboot using volume up.
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
You can also hold power and the camera button to enter bootloader, then choose AP Fastboot (just saying for users who may not know).
Loader009 said:
Sorry, I was thinking about nandroid and TWRP, not of RSD Lite...
My mistake.
Click to expand...
Click to collapse
Yeah, I have no problem using TWRP or flashing stuff from Internal or External SD
yogi2010 said:
damn, that sucks! did you ever check Device Manager in the Control Panel. i remember seeing a missing Moto driver there, but then again, that led me on a driver search, which led me to Moto Device Manager. did you completely uninstall it first before reinstalling it?
i dunno, just throwing out ideas here lol. otherwise, you might be able to just fastboot flash the necessary components from the FXZ file to get your setup back to stock. or else use a stock TWRP backup, then reflash stock recovery. hope you get it
Click to expand...
Click to collapse
Okay, now this is weird! I have my system back up and running, but I can only load it by starting the bootloader and choosing "normal startup"; otherwise my device boots into fastboot automatically every time I power down. Seems like I can't utilize stock recovery either when I flash it (otherwise I am using TWRP). My entire purpose behind unrooting and going back to stock was to update to JB as I participated in Moto's soak test. I am still stumped...?
System Up, Stock Recovery Down
Guess I'll try re-flashing the bootloader? or a version from a different/newer image?
galacticservant said:
Okay, now this is weird! I have my system back up and running, but I can only load it by starting the bootloader and choosing "normal startup"; otherwise my device boots into fastboot automatically every time I power down. Seems like I can't utilize stock recovery either when I flash it (otherwise I am using TWRP). My entire purpose behind unrooting and going back to stock was to update to JB as I participated in Moto's soak test. I am still stumped...?
System Up, Stock Recovery Down
Guess I'll try re-flashing the bootloader? or a version from a different/newer image?
Click to expand...
Click to collapse
hmm ok, that's good you made some progress, not sure what's up there. which file did you restore with RSD? i tried restoring the asa14 one last night and got an error immediately, but i'm not sure if i edited the xml properly.
so what i ended up doing was restoring this one: http://forum.xda-developers.com/showpost.php?p=33942232&postcount=12. it will restore everything to the original factory firmware that came with the phone.... except for the system. but i had already restored the stock system with a TWRP backup posted by rangerbry, so it was ok. then i had to run the 2 OTA updates on the phone to get up to the most recent official release. it's a bit convoluted, but it's an option, hehe.
yogi2010 said:
hmm ok, that's good you made some progress, not sure what's up there. which file did you restore with RSD? i tried restoring the asa14 one last night and got an error immediately, but i'm not sure if i edited the xml properly.
so what i ended up doing was restoring this one: http://forum.xda-developers.com/showpost.php?p=33942232&postcount=12. it will restore everything to the original factory firmware that came with the phone.... except for the system. but i had already restored the stock system with a TWRP backup posted by rangerbry, so it was ok. then i had to run the 2 OTA updates on the phone to get up to the most recent official release. it's a bit convoluted, but it's an option, hehe.
Click to expand...
Click to collapse
I think the problem is with the cdrom...my phone keeps booting into AP fastboot automatically like I said...and I was never able to get RSD Lite to recognize my device, so I only used fastboot and TWRP. RSD Lite is sadly not an option for me at this point...
Oh, the image that I previously restored with RSD was odexed and purely stock, ASA 14-15 Sprint. Now it wont read in RSD...
Sent from my XT897 using xda app-developers app
yogi2010 said:
hmm ok, that's good you made some progress, not sure what's up there. which file did you restore with RSD? i tried restoring the asa14 one last night and got an error immediately, but i'm not sure if i edited the xml properly.
so what i ended up doing was restoring this one: http://forum.xda-developers.com/showpost.php?p=33942232&postcount=12. it will restore everything to the original factory firmware that came with the phone.... except for the system. but i had already restored the stock system with a TWRP backup posted by rangerbry, so it was ok. then i had to run the 2 OTA updates on the phone to get up to the most recent official release. it's a bit convoluted, but it's an option, hehe.
Click to expand...
Click to collapse
Something else that I totally overlooked...the red Motorola ripple boot animation doesn't even play anymore! It goes right to the sprint_bootanimation...something's not quite right in Moto Land!
Sent from my XT897 using xda app-developers app
galacticservant said:
Okay, now this is weird! I have my system back up and running, but I can only load it by starting the bootloader and choosing "normal startup"; otherwise my device boots into fastboot automatically every time I power down. Seems like I can't utilize stock recovery either when I flash it (otherwise I am using TWRP). My entire purpose behind unrooting and going back to stock was to update to JB as I participated in Moto's soak test. I am still stumped...?
System Up, Stock Recovery Down
Guess I'll try re-flashing the bootloader? or a version from a different/newer image?
Click to expand...
Click to collapse
Stock recovery still not functioning, but phone doesn't auto load fastboot anymore. Still can only load system from bootloader. But also TWRP doesn't disappear after reboot. I flashed cdrom, but is what is the extension? Is it a .img, or is it supposed to be? In details it just said "file".
Sent from my XT897 using xda app-developers app
I apologize in advance if this all seems basic, but I've googled and googled and I'm not getting anything but confused. My girlfriend has a Photon Q that she OTA upgraded to Jelly Bean, and she absolutely hates it. She desperately wants to go back to ICS. Is that possible, and if so how can I do it?
Use the FXZ thread.
There's the getvar lines to remove, and there's some additional lines which need to be removed if you're downgrading.
Edit - this post may help you with the additional lines that need to be removed in order to downgrade.
arrrghhh said:
Use the FXZ thread.
There's the getvar lines to remove, and there's some additional lines which need to be removed if you're downgrading.
Edit - this post may help you with the additional lines that need to be removed in order to downgrade.
Click to expand...
Click to collapse
Okay, so I think I get it for the most part. I download RSD Lite and the proper FXZ file for what I'm downgrading to, which would be 4.0.4 in my case since I'm going ICS. I edit the XML file to remove the line <step operation="getvar" var="max-download-size" /> and should be good to go. Assuming I'm correct with my understanding, I'm still confused about one three. There appear to be three different FXZ for 4.0.4, I'm not sure which of the three I should use.
dereckbarker said:
Okay, so I think I get it for the most part. I download RSD Lite and the proper FXZ file for what I'm downgrading to, which would be 4.0.4 in my case since I'm going ICS. I edit the XML file to remove the line <step operation="getvar" var="max-download-size" /> and should be good to go. Assuming I'm correct with my understanding, I'm still confused about one three. There appear to be three different FXZ for 4.0.4, I'm not sure which of the three I should use.
Click to expand...
Click to collapse
Well since you're downgrading there are some additional lines which you have to remove from the XML file. Read my edit, I linked you to another post which talks about that.
As for which one to download, that is up to you. Motorola released 3 OTA's for ICS, and one for JB. I have no clue which one was being used previously on your device, but it's likely ASA-14 as it was the last ICS firmware.
arrrghhh said:
Well since you're downgrading there are some additional lines which you have to remove from the XML file. Read my edit, I linked you to another post which talks about that.
As for which one to download, that is up to you. Motorola released 3 OTA's for ICS, and one for JB. I have no clue which one was being used previously on your device, but it's likely ASA-14 as it was the last ICS firmware.
Click to expand...
Click to collapse
Well it appear I may be SOL anyways as I can't seem to get into recovery mode. Upon starting up and pressing power + Vol up I get nothing but a screen of an android with an ! coming out of its chest for about a minute or two and then the phone reboots. Damn thing isn't rooted or anything, it's a stock phone.
dereckbarker said:
Well it appear I may be SOL anyways as I can't seem to get into recovery mode. Upon starting up and pressing power + Vol up I get nothing but a screen of an android with an ! coming out of its chest for about a minute or two and then the phone reboots. Damn thing isn't rooted or anything, it's a stock phone.
Click to expand...
Click to collapse
That's stock recovery. You need to put the phone in fastboot mode, not recovery mode.
Code:
adb reboot bootloader
should bring you to fastboot mode. Or, use cam+power to get the menu when the phone turns on.
arrrghhh said:
That's stock recovery. You need to put the phone in fastboot mode, not recovery mode.
Code:
adb reboot bootloader
should bring you to fastboot mode. Or, use cam+power to get the menu when the phone turns on.
Click to expand...
Click to collapse
Boy you must be real sick of hearing from me already. Even in fastboot mode, the phone doesn't show up under my list of devices in RSD Lite
dereckbarker said:
Boy you must be real sick of hearing from me already. Even in fastboot mode, the phone doesn't show up under my list of devices in RSD Lite
Click to expand...
Click to collapse
Nah, I'm here to help.
So do you have fastboot functioning?
What is the output of
Code:
fastboot devices
arrrghhh said:
Nah, I'm here to help.
So do you have fastboot functioning?
What is the output of
Code:
fastboot devices
Click to expand...
Click to collapse
Absolutely nothing. The command prompt gives me a blank space.
dereckbarker said:
Absolutely nothing. The command prompt gives me a blank space.
Click to expand...
Click to collapse
Well, I'd guess you don't have adb or fastboot setup.
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
If you'd like, I can help you out "live" on IRC. Freenode, I'm in a few rooms... I spose #oudhitsquad is the best.
Thanks.
Okay I figured out why I wasn't getting anything to show in RSD, I didn't have the stupid phone unlocked yet. I do now, and everything seemed to be working out until I actually tried flashing. I get the error:
Failed flashing process. 1/21 flash partition "gpt_main0.bin" -> Phone returned fail.
Click to expand...
Click to collapse
The lines I deleted were two instances of
<step operation="oem" var="fb_mode_set" />
Click to expand...
Click to collapse
and two instances of
<step operation="getvar" var="max-download-size" />
Click to expand...
Click to collapse
The error on the phone itself says
preflash validation failed for GPT, downgraded security version
Click to expand...
Click to collapse
From that other guy's post, it looks like you need to also remove the gpt_main0.bin lines.
Danger!!
Maybe it's too late for you as it's for me now: but doing this erased my IMEI data. I hope nobody else try this.
arrrghhh said:
From that other guy's post, it looks like you need to also remove the gpt_main0.bin lines.
Click to expand...
Click to collapse
msxisalive said:
Maybe it's too late for you as it's for me now: but doing this erased my IMEI data. I hope nobody else try this.
Click to expand...
Click to collapse
No, I never tried to downgrade to ICS... I still have a stock backup of ICS, never saw the need to flash it.
Sorry, I misunderstood the original problem.
In my case, my phone came already with jelly bean, so I did'nt have an ICS backup. I wanted to downgrade in order to get MSL number, and ended with a phone with IMEI 00000... :crying:
Fortunately I did a bull nandroid backup before that, so I restored it and my IMEI came back. :victory:
Edit: Finally I could downgrade without losing IMEI using TWRP and the ICS backup from this thread.
With that, I could get my MSL and then return to CM11.
arrrghhh said:
No, I never tried to downgrade to ICS... I still have a stock backup of ICS, never saw the need to flash it.
Click to expand...
Click to collapse
Hello friends I have a problem with my phone : cry : .. past days I made a mistake of firmware and install a rom on my phone of xt925 and is a ' ' xt926 ' ' I need lots of help to return to the rom Original Verizon
VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-4_VQW_CFC.xml
I am trying to install via RSD Lite , but I get the following error appears in the image :crying:
please help dont know what else to do to install the rom on my phone, this unlocked and root for procedures
try this, hope you understand how to use it.
Resp
TOYEP said:
try this, hope you understand how to use it.
Click to expand...
Click to collapse
Thanks buddy , I'll try ... I imagine these are only replacing the I have ..
Js.Vicious said:
Thanks buddy , I'll try ... I imagine these are only replacing the I have ..
Click to expand...
Click to collapse
TOYEP said:
try this, hope you understand how to use it.
Click to expand...
Click to collapse
there is no way to flash an equal version of trust zone with rsd.
he needs to replace all the files anyways.
2 possible solutions come to mind,
1. flash the next newer firmware with rsd, if that fails,
2. flash the same version with Mfastboot, if that fails, try the newer version.
figuring out how to bypass the tz fail is easy, but it will just throw another error when it gets to the next file you cant downgrade or re-write equal. thats why the steps i have suggested should be tried.
bweN diorD said:
there is no way to flash an equal version of trust zone with rsd.
he needs to replace all the files anyways.
2 possible solutions come to mind,
1. flash the next newer firmware with rsd, if that fails,
2. flash the same version with Mfastboot, if that fails, try the newer version.
figuring out how to bypass the tz fail is easy, but it will just throw another error when it gets to the next file you cant downgrade or re-write equal. thats why the steps i have suggested should be tried.
Click to expand...
Click to collapse
yes, he must replace files IF current rom defferent from mine, i use latest stock rom released.
and i assume he know how to put md5-hash to the .xml file if he wish do some experimental :laugh:
Keep in mind he flashed 925 FW to a 926, he could be toast.
Sent from my HTC6525LVW using Tapatalk
correct. i think he stuck at bootloader.
You may be right, but it doesn't hurt to at least try the most correct method to fix it.
Sent from my G3, with mods made possible by team Codefire.
RegiArt exceptional
i think what he got when research with "firmware" or "ROM".. worst case is softbrick. correct?
TOYEP said:
i think what he got when research with "firmware" or "ROM".. worst case is softbrick. correct?
Click to expand...
Click to collapse
not really, depending on what files flash, if not all, it surely could be toast also.