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.
Hi all
A bit new to posting in here but am really hoping to receive some help from you all. Last night I installed all the standard USB drivers i.e. Android SDK pack and followed them all as mentioned. Then using the root tool from ChainFire I got to the little android guy after going through the process of unlocking the bootloader and gaining root, but the phone never actually rebooted.
Now when I try to flash the original fastboot files using the WUG kit I get "FAILED: remote: flash write failure" The same is the case with writing the boot img and recovery img. See attached.
I can put the phone into Fastboot mode only and it says lock state is "unlocked" but it would seem that I can no longer write anything to the internal disk as nothing will work or boot. I also get a status on my PC saying that the driver QHSUSB_Bulk could not be found.
Has anybody had a similar problem to this? Is there any way to somehow get this working again? And if I RMA with Google will they say my warranty is voided now that it says the lock state in Fastboot is unlocked?
Many thanks in advance guys any help is appreciated.
Meakii said:
Hi all
A bit new to posting in here but am really hoping to receive some help from you all. Last night I installed all the standard USB drivers i.e. Android SDK pack and followed them all as mentioned. Then using the root tool from ChainFire I got to the little android guy after going through the process of unlocking the bootloader and gaining root, but the phone never actually rebooted.
Now when I try to flash the original fastboot files using the WUG kit I get "FAILED: remote: flash write failure" The same is the case with writing the boot img and recovery img. See attached.
I can put the phone into Fastboot mode only and it says lock state is "unlocked" but it would seem that I can no longer write anything to the internal disk as nothing will work or boot. I also get a status on my PC saying that the driver QHSUSB_Bulk could not be found.
Has anybody had a similar problem to this? Is there any way to somehow get this working again? And if I RMA with Google will they say my warranty is voided now that it says the lock state in Fastboot is unlocked?
Many thanks in advance guys any help is appreciated.
Click to expand...
Click to collapse
Try flashing the factory images manually.
http://forum.xda-developers.com/showthread.php?t=2513701
Method 2.
Does fastboot work properly? What output does 'Fastboot devices" have?
abaaaabbbb63 said:
Try flashing the factory images manually.
http://forum.xda-developers.com/showthread.php?t=2513701
Method 2.
Does fastboot work properly? What output does 'Fastboot devices" have?
Click to expand...
Click to collapse
Thanks have tried flashing them manually but still the same error saying FAILED: remote: flash write failure
It as if nothing can be written to the phone at all.
Yea fastboot seems to work fine but sorry what do you mean by what ouput does fastboot devices have?
Thanks a lot
Meakii said:
Thanks have tried flashing them manually but still the same error saying FAILED: remote: flash write failure
It as if nothing can be written to the phone at all.
Yea fastboot seems to work fine but sorry what do you mean by what ouput does fastboot devices have?
Thanks a lot
Click to expand...
Click to collapse
write "Fastboot devices" in CMD while phone is in fastboot.
What happens when you boot in recovery? Try that, and do a factory data reset.
abaaaabbbb63 said:
write "Fastboot devices" in CMD while phone is in fastboot.
What happens when you boot in recovery? Try that, and do a factory data reset.
Click to expand...
Click to collapse
Ok see attached. Also it doesn't allow me to boot into recovery at all. I used the WUG kit to temporarily boot into TWRP and tried a factory reset there but it says there's no ROM installed. It's like everything has been wiped and it can't write anything to the internals to read from. Thanks for you help so far. Any other suggestions?
Meakii said:
Ok see attached. Also it doesn't allow me to boot into recovery at all. I used the WUG kit to temporarily boot into TWRP and tried a factory reset there but it says there's no ROM installed. It's like everything has been wiped and it can't write anything to the internals to read from. Thanks for you help so far. Any other suggestions?
Click to expand...
Click to collapse
Just... stop using toolkits for a second here! These automated processes got you here in the first place.
Try this command:
fastboot erase userdata
Does it succeed?
abaaaabbbb63 said:
Just... stop using toolkits for a second here! These automated processes got you here in the first place.
Try this command:
fastboot erase userdata
Does it succeed?
Click to expand...
Click to collapse
Ok ummm see attached. I'm so gutted any further thoughts or advice?
Meakii said:
Ok ummm see attached. I'm so gutted any further thoughts or advice?
Click to expand...
Click to collapse
It seems like a brick. Something got corrupted. I searched far an wide on XDA and other forums, but no one with this problem has found the solution.
It seems that your last chance is RMA.
abaaaabbbb63 said:
It seems like a brick. Your internal memory got corrupted. I searched far an wide on XDA and other forums, but no one with this problem has found the solution.
It seems that your last chance is RMA.
Click to expand...
Click to collapse
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
Who knows? Try it!
I don´t think the reason was CF-auto root. There must be something wrong with the device´s flash from the beginning. My thoughts are that you´r flash has a corrupted area which surprisingly wasn´t used for the stock factory flash and CF-autoroot triggered it while flashing a specific partition. Maybe i´m completely wrong.
I hope you´ll get it exchanged :good:.
Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
I don't really know what happened. I guess there are always risks when using tools like this. That's why I always recommend rooting using the manual method.
I have no idea how google will react. In theory, a simple unlocked bootloader won't affect warranty. In reality, anything can happen. Good luck, and sorry!
Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
abaaaabbbb63 said:
I don't really know what happened. I guess there are always risks when using tools like this. That's why I always recommend rooting using the manual method.
I have no idea how google will react. In theory, a simple unlocked bootloader won't affect warranty. In reality, anything can happen. Good luck, and sorry!
Click to expand...
Click to collapse
Absolutely gutted but thanks so much for your help. I'll report back with Googles response.
pert_S said:
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
Click to expand...
Click to collapse
It will respond, but the memory won't flash. Major no-fix problem.
pert_S said:
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
Click to expand...
Click to collapse
Hi nah it only boots into Fastboot mode where it says down the bottom in red "LOCK STATE - unlocked" . Have tried every trick posted on here but it seems that during the rooting process somehow corrupted internal storage meaning it can't write anything to the phone (therefore not being able to reset to factory etc etc).
What a disaster.
Would opening the command prompt window with administrative rights make a difference? Worth a shot.
Meakii said:
Hi nah it only boots into Fastboot mode where it says down the bottom in red "LOCK STATE - unlocked" . Have tried every trick posted on here but it seems that during the rooting process somehow corrupted internal storage meaning it can't write anything to the phone (therefore not being able to reset to factory etc etc).
What a disaster.
Click to expand...
Click to collapse
Oh I see.
Well like abaaaabbbb63 said, in theory it shouldn't affect warranty.
They would have to show that unlocking the bootloader caused the fault I presume.
Make sure you tell Google that this happened when using a toolkit and a script when asking for a new phone free of charge.
Sent from my Nexus 5 using Tapatalk
El Daddy said:
Make sure you tell Google that this happened when using a toolkit and a script when asking for a new phone free of charge.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
How would that help? I think pleading ignorance to how it happened would probably be best wouldn't it?
Thanks for all the replies.
It's sarcasm friend. ;3. Daddy isn't a fan of toolkits nor of people claiming new handsets after a problem occurs as a result of one.
Hey
I have HTC desire s, which is pretty old (i'v had about three years now). In recent months it has started to run more and more sluggishly. After I re-downloaded a game that I played when I first got the phone I realized that my phone had experienced some power-loss, as the game that used to run smoothly now lagged. It wasn't so big deal as I do not play games with my phone so often, but now it feels like apps that I use and pretty much need like whatsapp and internet browser are also starting to lag more.
So now I am trying to find some way to restore my phone do the state it was when I first got it.
I have done almost everything that you can do with an un-rooted phone. (Ram,cache,apps...) I also did "factory reset" which actually seemed to help for a while, but soon the problem came back.
I tried also rooting my phone with super-one-click, but even I followed instructions "perfectly" and the app said my phone is rooted it actually wasn't.
I can try it again if it's necessary.
Thank you for Answers and I apologize for being a noob.
vesaninja said:
Thank you for Answers and I apologize for being a noob.
Click to expand...
Click to collapse
No need to apologize for ask a question in a forum called "Questions and answers"
Do you know which Firmware / Stock Rom version is actually installed on your phone?
If you got this information, i can help you with rooting and speed up your Desire S
LS.xD said:
Do you know which Firmware / Stock Rom version is actually installed on your phone?
Click to expand...
Click to collapse
My software number is 2.10.401.8 and I have android 2.3.5
vesaninja said:
My software number is 2.10.401.8 and I have android 2.3.5
Click to expand...
Click to collapse
Pls google "HTC Desire S All-In-One Toolkit V2.0". first link should be a valid download. I'm not allowed to post a link
also download the latest recovery for your phone --> TWRP 2.6.3.0 for Desire S
When you got it we can go on
Hi
Remove bloatwares
Once rooted + CFW then use ROM CLEANER
FOLOL2011 said:
Hi
Remove bloatwares
Once rooted + CFW then use ROM CLEANER
Click to expand...
Click to collapse
We really have to thank you for such "detailled" informations... :good:
OK sorry for my lame answer
I just wanted to give the information about Rom cleaner
but I cannot help for rooting this phone model as I don't know it
FOLOL2011 said:
OK sorry for my lame answer
I just wanted to give the information about Rom cleaner
but I cannot help for rooting this phone model as I don't know it
Click to expand...
Click to collapse
Some more informations are always welcome So may be you can implement a downloadlink or informations how to get a suggested app in your next post(s).
I have now that toolkit and recovery downloaded on my computer.
vesaninja said:
I have now that toolkit and recovery downloaded on my computer.
Click to expand...
Click to collapse
The toolkit provides steps to "Unlock bootloader" via HTCdev.com. You need it unlocked to root or flash a custom recovery.
PLS read exactly and keep in mind that unlocking the bootloader will reset your phone to stock. MAKE SURE you safe ALL your PERSONAL DATA before you proceed.
LS.xD said:
The toolkit provides steps to "Unlock bootloader" via HTCdev.com. You need it unlocked to root or flash a custom recovery.
PLS read exactly and keep in mind that unlocking the bootloader will reset your phone to stock. MAKE SURE you safe ALL your PERSONAL DATA before you proceed.
Click to expand...
Click to collapse
When I press install HTC drivers a mesage pops up saying that it will install them, but after that nothing happens. I looked from youtube that a install wizard should pop up, but nothing happens. So what should I do as I think that those drivers aren't being installed.
vesaninja said:
When I press install HTC drivers a mesage pops up saying that it will install them, but after that nothing happens. I looked from youtube that a install wizard should pop up, but nothing happens. So what should I do as I think that those drivers aren't being installed.
Click to expand...
Click to collapse
If you have installed drivers just skip it
Latest drivers are here if needed --> Click me as you never clicked before
LS.xD said:
If you have installed drivers just skip it
Latest drivers are here if needed -->
Click to expand...
Click to collapse
I had not installed them, but now I have. :victory:
vesaninja said:
I had not installed them, but now I have. :victory:
Click to expand...
Click to collapse
Then read carefully. And let me know when your bootloader is unlocked.
Now when I am trying to Get the token ID, again message pops up saying what to do, but still nothing else happens. So I cannot get the Id as I do not get those command prom screens. Something wrong in my toolkit?
vesaninja said:
Now when I am trying to Get the token ID, again message pops up saying what to do, but still nothing else happens. So I cannot get the Id as I do not get those command prom screens. Something wrong in my toolkit?
Click to expand...
Click to collapse
There was re-installing solved the problem
vesaninja said:
Now when I am trying to Get the token ID, again message pops up saying what to do, but still nothing else happens. So I cannot get the Id as I do not get those command prom screens. Something wrong in my toolkit?
Click to expand...
Click to collapse
You connected your phone in "fastboot" mode?
It toolkit fails (its important that you haven't change the folder name of the toolkit!)
We can do manually --> Go to HTC dev --> http://www.htcdev.com/bootloader/ select "All other supported models" you also will have to register.
and you need this adb/fastboot http://d-h.st/KIP
My bootloader should now be unlocked
vesaninja said:
My bootloader should now be unlocked
Click to expand...
Click to collapse
does it show "unlocked" ??
LS.xD said:
does it show "unlocked" ??
Click to expand...
Click to collapse
Yes it does.
Hi everyone,
I need a little help here as I find myself stuck between a lot of possibilities and I don't know which one to take or generally what to do.
My girlfriend has an HTC One S4 with unlocked bootloader (HBOOT 2.15), recovery installed, running Viper ROM 3.1.
However because she only has the 1.15 RADIO on the device it tends to reboot quite a lot and she can't have a phone that reboots that often to use on a daily basis.
I want to S-OFF the device so I can upgrade the RADIO.
I've heard of Moonshine method and rumrunner method, however both of these only work with fastboot drivers installed and working.
This is not the case for her S4. I have a desktop (win 8.1, with USB 2 and USB 3.0) and a laptop (win 8.0 with only USB 3).
And none of them can find the device when it is connected while in fastboot. Therefore I can't S-OFF the device that way..
Could anyone point me in the right direction or have some suggestions on what to do?
Hammerbak said:
This is not the case for her S4. I have a desktop (win 8.1, with USB 2 and USB 3.0) and a laptop (win 8.0 with only USB 3).
And none of them can find the device when it is connected while in fastboot. Therefore I can't S-OFF the device that way..
Could anyone point me in the right direction or have some suggestions on what to do?
Click to expand...
Click to collapse
Did you try a Ubuntu Live CD? That's what I had to do to get things working reliably.
How did you install fastboot and adb?
808phone said:
Did you try a Ubuntu Live CD? That's what I had to do to get things working reliably.
How did you install fastboot and adb?
Click to expand...
Click to collapse
No I haven't tried with an Ubuntu Live CD, and tbh I'm not that well known in the Linux systems.
Well I installed the Google Drivers from the "Android SDK Manager" and I tried a lot of different methods I found on posts alike.
The problem is that neither of my two computers can find the device when it's connected and in fastboot.
Hammerbak said:
No I haven't tried with an Ubuntu Live CD, and tbh I'm not that well known in the Linux systems.
Well I installed the Google Drivers from the "Android SDK Manager" and I tried a lot of different methods I found on posts alike.
The problem is that neither of my two computers can find the device when it's connected and in fastboot.
Click to expand...
Click to collapse
How about using some friends computer /laptop?
LS.xD said:
How about using some friends computer /laptop?
Click to expand...
Click to collapse
Well I guess I could try out her PC when I get home later today, but I doubt there will be a lot of difference.
However her PC runs Win 7. I will return here as soon as I know more!
Hammerbak said:
Well I guess I could try out her PC when I get home later today, but I doubt there will be a lot of difference.
However her PC runs Win 7. I will return here as soon as I know more!
Click to expand...
Click to collapse
Is it a unbranded phone hboot 2.15 eu ??
For me Facepalm was the only wotking one.
The biggest problem is that without adb and fastboot working, you probably won't get anywhere.
The reason I mentioned the Ubuntu live CD is that I have working fastboot and adb and still had problems with windows 7.
I finally created the Ubuntu live CD (actually USB) and it worked. It doesn't take too long to create the live CD/USB and it's worth a try.
LS.xD said:
Is it a unbranded phone hboot 2.15 eu ??
For me Facepalm was the only wotking one.
Click to expand...
Click to collapse
Well tbh I don't know if it is unbranded - Since I don't know what that term means.
We live in Denmark and I think she got the phone from germany - bought on a sale somewhere.
Whenever it was booting up (before I rooted and unlocked the bootloader) it came with a splash screen saying "T-Mobile".
Does that mean it is branded to T-Mobile?
808phone said:
The biggest problem is that without adb and fastboot working, you probably won't get anywhere.
The reason I mentioned the Ubuntu live CD is that I have working fastboot and adb and still had problems with windows 7.
I finally created the Ubuntu live CD (actually USB) and it worked. It doesn't take too long to create the live CD/USB and it's worth a try.
Click to expand...
Click to collapse
The LiveCD/LiveUSB sounds like an idea and will be my first attempt after "trying" Win 7.
Does the moonshine S-OFF method only support Stock ROM/Firmwares?
I guess I am to try the rumrunner method once on the LiveCD/LiveUSB.
Thanks in advance and again I will return when I know more
Hammerbak said:
Well tbh I don't know if it is unbranded - Since I don't know what that term means.
We live in Denmark and I think she got the phone from germany - bought on a sale somewhere.
Whenever it was booting up (before I rooted and unlocked the bootloader) it came with a splash screen saying "T-Mobile".
Does that mean it is branded to T-Mobile?
The LiveCD/LiveUSB sounds like an idea and will be my first attempt after "trying" Win 7.
Does the moonshine S-OFF method only support Stock ROM/Firmwares?
I guess I am to try the rumrunner method once on the LiveCD/LiveUSB.
Thanks in advance and again I will return when I know more
Click to expand...
Click to collapse
moonshine only supports "supported" firmware versions listed on the moonshine.io homepage (page 3)..
LS.xD said:
moonshine only support "supported" firmware listed on the homepage...
Click to expand...
Click to collapse
So I will be using rumrunner then..
Thanks however.
Hammerbak said:
So I will be using rumrunner then..
Thanks however.
Click to expand...
Click to collapse
wish you best luck
LS.xD said:
wish you best luck
Click to expand...
Click to collapse
I am sitting on a LiveUSB right now, but I find that the instructions on the rumrunner webpage doesn't work.
Any suggestions?
It goes through the first steps and I will get to answer ''Yes'' twice.
After a please wait message I get: "ERROR: run rumrunner again and READ (no adb connection to device. Debugging on? Drivers?)
I followed the instructions to perfection. Will I need to install drivers on Linux?
Hammerbak said:
I am sitting on a LiveUSB right now, but I find that the instructions on the rumrunner webpage doesn't work.
Any suggestions?
It goes through the first steps and I will get to answer ''Yes'' twice.
After a please wait message I get: "ERROR: run rumrunner again and READ (no adb connection to device. Debugging on? Drivers?)
I followed the instructions to perfection. Will I need to install drivers on Linux?
Click to expand...
Click to collapse
Do you have USB Debugging on? When you are booted into the phone and connected to the computer. Type adb devices and see if it returns a valid value (not offline).
No, you don't have to install drivers on Linux. Also I never was able to get anything but moonshine.io working.
808phone said:
Do you have USB Debugging on? When you are booted into the phone and connected to the computer. Type adb devices and see if it returns a valid value (not offline).
No, you don't have to install drivers on Linux. Also I never was able to get anything but moonshine.io working.
Click to expand...
Click to collapse
Well USB debugging is enabled on the device, however it doesn't show the USB debugging icon on the phone that it does when connected to a Windows PC.
I will try to check is ADB is active later tonight.
hello everyone,
i'm developing a game with unity and sometimes when i compile and inject the game on the phone it crashes and forces me to factory reset the phone through fastboot. i've done it like 3 times already with no problems.
but today it happened again and the phone just wouldnt recover, i've tried the fix that this video (youtube.com/watch?v=laU6NQ0LxR0) shows but it still does not boot.
I am able to enter fastboot and my computer recognizes the mobile phone so that's a great start :victory:
not sure what guide to follow since i'm not sure whether the problem is on the rom or something else.
can someone give me a tip on what fix should I try? cant really afford to lose my phone right now
it has (had) a stock rom 4.4.2 with stock bootloader, tho i tried to install the fix in the video i've said earlier and i'm not sure whether it changed the rom or not.
thanks
pewtel said:
hello everyone,
i'm developing a game with unity and sometimes when i compile and inject the game on the phone it crashes and forces me to factory reset the phone through fastboot. i've done it like 3 times already with no problems.
but today it happened again and the phone just wouldnt recover, i've tried the fix that this video (youtube.com/watch?v=laU6NQ0LxR0) shows but it still does not boot.
I am able to enter fastboot and my computer recognizes the mobile phone so that's a great start :victory:
not sure what guide to follow since i'm not sure whether the problem is on the rom or something else.
can someone give me a tip on what fix should I try? cant really afford to lose my phone right now
it has (had) a stock rom 4.4.2 with stock bootloader, tho i tried to install the fix in the video i've said earlier and i'm not sure whether it changed the rom or not.
thanks
Click to expand...
Click to collapse
What about following this guide?
Landrea said:
What about following this guide?
Click to expand...
Click to collapse
got stuck here :/
dropbox.com/s/d3s378e9pvxs0ab/Screenshot%202014-03-30%2023.17.12.png
pewtel said:
got stuck here :/
dropbox.com/s/d3s378e9pvxs0ab/Screenshot%202014-03-30%2023.17.12.png
Click to expand...
Click to collapse
Have you configured the drivers on your pc? The phone is recognized? It looks like the pc can't dialogate with it
Sent from my Commodore 64 using Videotel
Landrea said:
Have you configured the drivers on your pc? The phone is recognized? It looks like the pc can't dialogate with it
Sent from my Commodore 64 using Videotel
Click to expand...
Click to collapse
the phone is recognized as motorola adb interface, i even re-installed the drivers. now trying a different rom but i'm pretty sure the ROM is not the issue
*edit: yep, still waiting for device even with different ROM
modaco.com/topic/366786-how-to-flash-to-the-standard-uk-rom/
:victory: :victory: :victory:
this worked for me,
posting the link just in case someone encounters the same problem. thanks
pewtel said:
modaco.com/topic/366786-how-to-flash-to-the-standard-uk-rom/
:victory: :victory: :victory:
this worked for me,
posting the link just in case someone encounters the same problem. thanks
Click to expand...
Click to collapse
Thank you for sharing
/Data gets corrupted
Even, I had the same issue. I tried flashing ROMs through recovery but it gave me error that/data/media/0/ can't be mounted. The only way to get out I found was to full format /data and /storage (philz recovery) and then to push ROM. zip to/sdcard through adb and then to flash it through recovery.
Hope it helps someone.:angel: