Related
so a buddy of mine rooted his wifes eris, and sorta messed up the root, he can get to clockwork mod and all, BUT any rom he tries to flash will say error at line 9 or line 6 not enough space on device, aborting operation....
he also failed to make an nand back up so basically we are stuck in clockwork
someone help! how do we either fix this to flash a rom or unroot/return to stock this device??
we have tryed the RUU method but it doesnt reconize the drvice because we are in clock work
and we have try the pbm img but s=on so were locked out
If s=on then i dont think he got root
Cyostrife said:
If s=on then i dont think he got root
Click to expand...
Click to collapse
he followed the method on theunlockr.com
worked just fine for his eris, but his wifes is giving said errors...
with just bootloader and cwm avalible what can we do to fix this?
mytouchguy said:
he followed the method on theunlockr.com
worked just fine for his eris, but his wifes is giving said errors...
with just bootloader and cwm avalible what can we do to fix this?
Click to expand...
Click to collapse
How full is the battery? I get errors if I try to flash and the battery is ~30% or less.
lp4261 said:
How full is the battery? I get errors if I try to flash and the battery is ~30% or less.
Click to expand...
Click to collapse
not sure, i was doing a remote help, i do alot of rooting for tmo phones ive just never seen this error... i plan to go help him in person just trying to get some advice
will it still charge with no rom? if so ill have him charge it overnight
mytouchguy said:
not sure, i was doing a remote help, i do alot of rooting for tmo phones ive just never seen this error... i plan to go help him in person just trying to get some advice
will it still charge with no rom? if so ill have him charge it overnight
Click to expand...
Click to collapse
I would assume so, but I'm still a novice. I just noticed this from my own experience.
lp4261 said:
I would assume so, but I'm still a novice. I just noticed this from my own experience.
Click to expand...
Click to collapse
what type of errors have you seen?
his says not enough space on device... could this relate the cwm bricking devices?
more so is the device bricked at this point or are we still ok?
mytouchguy said:
what type of errors have you seen?
his says not enough space on device... could this relate the cwm bricking devices?
more so is the device bricked at this point or are we still ok?
Click to expand...
Click to collapse
if u can power the device on , i believe it aint bricked
Can he get to hboot and usb from there. if so let me know and also can he get to recovery...
Sent from my froshedyo using XDA App
mytouchguy said:
what type of errors have you seen?
his says not enough space on device... could this relate the cwm bricking devices?
more so is the device bricked at this point or are we still ok?
Click to expand...
Click to collapse
That sounds like the type of stuff i would get. that or a push file via adb thing. It doesn't sound like a clockwork bricking. The problem with CWM is that it doesn't have the verification step that amon-ra does. Are you flashing roms from these forums? I trust the devs here, but I don't think I would flash a rom that isn't from here w/o a recommendation from one of the devs. I would plug the phone in and let it go for a bit and try again after it has a charge.
lp4261 said:
I would assume so, but I'm still a novice. I just noticed this from my own experience.
Click to expand...
Click to collapse
tazzpatriot said:
if u can power the device on , i believe it aint bricked
Click to expand...
Click to collapse
yes we can power on we can use cwm mod hell we can place a pbmimg on the sd card, it just wont read it because s=on at the time
in doing a massive google search
any chance this would work
http://www.droidforums.net/forum/hacking-help/37717-unroot-unbrick-using-sbf-post-ikithme.html
if not anyone got any ideas?
3 more questions
a: is there a way to get s=off without android loaded, between just the bootloader and cwm avalible? this way we can hopefully just use the pbmimg
B: is there a way to replace cwm with amon ra in this current state to use flashback21? http://forum.xda-developers.com/showthread.php?t=792026
and this is a really crazy thought but can we take the backup we created tonight from his eris... both phones are EXACTLY alike, purchased at the same time and all...and use it to flash in cwm to recover the dead phone?
there is way to flash S=OFF through recovery. Flash the file from here..
In order to use a nandroid from a different phone you need to change a few things to make it work. I read it somewhere. If I find it ill let ya know
Sent from my KaosGingerbread using XDA App
CCCP4ever said:
there is way to flash S=OFF through recovery. Flash the file from here..
Click to expand...
Click to collapse
This is only supposed to work if you have bootloader version 1.49. If you're lucky like me and have 1.47 it won't work. That's according to bftbo. He's tried both.
lp4261 said:
This is only supposed to work if you have bootloader version 1.47. If you're lucky like me and have 1.49 it won't work. That's according to bftbo. He's tried both.
Click to expand...
Click to collapse
ill have this on standby, idk what bootloader he has we kinda gave up for the night
erismaster said:
In order to use a nandroid from a different phone you need to change a few things to make it work. I read it somewhere. If I find it ill let ya know
Sent from my KaosGingerbread using XDA App
Click to expand...
Click to collapse
awesome ill do a little looking myself and see, but thanks. figured it was a crazy but possible idea
mytouchguy said:
ill have this on standby, idk what bootloader he has we kinda gave up for the night
Click to expand...
Click to collapse
here's bftbo's answer to my question:
http://forum.xda-developers.com/showpost.php?p=10501766&postcount=69
within moments i found this...
anyone know how to achive this? both phones in this instance are the droid ERIS
http://androidforums.com/incredible...ansferring-nandroid-backup-another-phone.html
lp4261 said:
here's bftbo's answer to my question:
http://forum.xda-developers.com/showpost.php?p=10501766&postcount=69
Click to expand...
Click to collapse
any way to roll back the bootloader as he mentioned in the event that he has 1.49?
and this is a really stupid question , but im so brain fryed... how do we check his bootloader version?
Hi everyone,
I am in a big problem it seems. This is what happened: My phone was working fine with CM7 and latest version of CW Mod but suddenly everything started force closing. So what I did was to factory reset the phone from recovery wiping cache and davlik cache. After doing factory reset it stopped at splash screen itself and not booting up. Does factory reset removes rooting for mt4g?
After that, I tried to install ADB and root again but adb devices doesnt show my device when I am in recovery. But when I go to fastboot it, fastboot devices cmd shows my device.
I then tried to go back to stock by applying PD15IMG and it successfully applies it but now it gets stuck at "my"splash screen. What should I do now?
Thanks in advance.
Uh oh... Sounds like bad eMMc chip which no, can't be fixed. I'd see if you can check your eMMc but if not I believe your screwed and will have to send back to tmo.
Sent from my HTC Glacier using XDA Premium App
Do you get any cache errors in recovery when wiping?
Did you upgrade your radio to a version other than stock before attempting to restore to factory using PD15IMG?
It's starting to sound like a bad eMMC at this point though. Those things are starting to fail left and right!
I will check eMMC and post it here. But yes, while wiping cache I get error E: cant open /cache/ or something like that so i assumed that it might be because i got unrooted and I wanted to root again (but i cant adb). When applying ROM, it exits saying Status 1. No, I didn't upgrade radio images.
Fc followed by bootloop followed by cache errors...definitely eMMc
Sent from my HTC Glacier using XDA Premium App
Because of applying PD15 image I got original h-boot version (not engineering h-boot) so couldn't check eMMC. But I have radio version which is 26.03.02.26_M
If I assume that eMMC is gone then, Is there any other option of doing ANYTHING except sending it to TMobile as I am using it outside US.
sagarparmar said:
Because of applying PD15 image I got original h-boot version (not engineering h-boot) so couldn't check eMMC. But I have radio version which is 26.03.02.26_M
If I assume that eMMC is gone then, Is there any other option of doing ANYTHING except sending it to TMobile as I am using it outside US.
Click to expand...
Click to collapse
Bootloader version has nothing to do with being able to check eMMC version.
http://forum.xda-developers.com/showthread.php?t=1081243
Somewhere in there there's instructions for checking without root if you've lost it already.
Thanks for the link but I can't adb. fastboot shows my device but adb doesn't. I don't know if there is any problem with my drivers. because when i plug the phone in is shows ADB Interface in Device manager. Still I will check them again will try to put eMMC version ASAP.
sagarparmar said:
Thanks for the link but I can't adb. fastboot shows my device but adb doesn't. I don't know if there is any problem with my drivers. because when i plug the phone in is shows ADB Interface in Device manager. Still I will check them again will try to put eMMC version ASAP.
Click to expand...
Click to collapse
Someone posted some instructions a while back that allowed you to check your eMMC version using terminal commands, so you could do it without root or ADB, but for the life of me I can't find them! I thought they were in the main eMMC serial thread, but maybe not. I'll keep looking.
TeeJay3800 said:
Someone posted some instructions a while back that allowed you to check your eMMC version using terminal commands, so you could do it without root or ADB, but for the life of me I can't find them! I thought they were in the main eMMC serial thread, but maybe not. I'll keep looking.
Click to expand...
Click to collapse
This is the terminal cmd it seems:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
But right now, my phone is not even booting up. how would I go to terminal emulator?
sagarparmar said:
This is the terminal cmd it seems:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
But right now, my phone is not even booting up. how would I go to terminal emulator?
Click to expand...
Click to collapse
I'm suffering from brain fade today. I forgot about the fact that your phone wasn't booting. If memory serves, there is a terminal option in CWM recovery. If your recovery is still usable, try selecting the terminal feature and enter those commands there. Honestly though, this would only serve to confirm what we already know. Your eMMC has failed, so there's isn't much hope. The good news is most people have had no trouble doing a warranty exchange, even when sending in a rooted phone. Good luck!
As I tried to flash PD15IMG it is now into stock recovery. Need to flash CWM using fastboot but dont know whether it would work or not because last time I tried (before applying PD15) it failed saying Status 1. Need to check that.
But you know what the bigger problem is, I bought it from Swappa.com and I don't even know whether I can exchange it or not. I will have to send it to my friend who is in the US as I am outside.
Do they give warranty card or something when you buy (I dont know as I am not the original buyer ) ??
TeeJay3800 said:
I'm suffering from brain fade today. I forgot about the fact that your phone wasn't booting. If memory serves, there is a terminal option in CWM recovery. If your recovery is still usable, try selecting the terminal feature and enter those commands there. Honestly though, this would only serve to confirm what we already know. Your eMMC has failed, so there's isn't much hope. The good news is most people have had no trouble doing a warranty exchange, even when sending in a rooted phone. Good luck!
Click to expand...
Click to collapse
There's a terminal in cwm...? Since when?
Sent from my HTC Glacier using XDA Premium App
Nope, bought mine from eBay and htd fixed it when mine quit. Just called for a rma, advised it was bootloopimg then went blank, shipped it and got another or it back fixed. Call it won't hurt.
sagarparmar said:
As I tried to flash PD15IMG it is now into stock recovery. Need to flash CWM using fastboot but dont know whether it would work or not because last time I tried (before applying PD15) it failed saying Status 1. Need to check that.
But you know what the bigger problem is, I bought it from Swappa.com and I don't even know whether I can exchange it or not. I will have to send it to my friend who is in the US as I am outside.
Do they give warranty card or something when you buy (I dont know as I am not the original buyer ) ??
Click to expand...
Click to collapse
knothead said:
Nope, bought mine from eBay and htd fixed it when mine quit. Just called for a rma, advised it was bootloopimg then went blank, shipped it and got another or it back fixed. Call it won't hurt.
Click to expand...
Click to collapse
Hey I'm in the situation where my phone won't even turn on now... I called HTC already and they're actually mailing in a battery thinking that it's the reason the phone won't charge or turn on...
What were the steps you went through to get the to take it in? Did you end up getting a new one or the one you sent in for repairs? You paid for shipping or any repair fees? Any input would be useful... let me know!
Thanks!
Nicgraner said:
There's a terminal in cwm...? Since when?
Click to expand...
Click to collapse
It doesn't. As I said in that post, I wasn't sure. It turns out I was thinking of Amon-RA's recovery which does have a terminal option.
TeeJay3800 said:
It doesn't. As I said in that post, I wasn't sure. It turns out I was thinking of Amon-RA's recovery which does have a terminal option.
Click to expand...
Click to collapse
CWM does have adb shell though.
Sent from my HTC Glacier using Tapatalk
knothead said:
Nope, bought mine from eBay and htd fixed it when mine quit. Just called for a rma, advised it was bootloopimg then went blank, shipped it and got another or it back fixed. Call it won't hurt.
Click to expand...
Click to collapse
Yeah, It would be great if you tell the procedure. You directly called HTC guys or TMobile? What else do you need to ship along with the phone?
Flashing CWM??
Guys,
As I described my phone is in a boot loop but I can see it in fastboot but when i go to recovery it jst goes to bad state and have to remove battery. Is there a way to flash CWM recovery and opening adb shell as I might want to see what is eMMC and need to try this out http://forum.xda-developers.com/showpost.php?p=15299273&postcount=66 and http://forum.xda-developers.com/showthread.php?t=1039504&page=2
I know we can flash recovery from fastboot but when i tried that it gave me an error saying you remote not allowed (android sdk on Win 7).
You weren't in fastboot mode, but in hboot mode.
Choose "fastboot" to be able to flash.
hi guys ...i hav some big problem n i really need ur help pls.
i hav tried to root my xoom but it failed n now im afraid i hav bricked my xoom
- unlock ok
- fastboot flash boot boot.img ok
- fastboot reboot fail ( dual core technology frozen)
the only thing that it shows is the dual core technology screen nothing more and when i reset it it starts alone by itself again and stock
i hav a motorola xoom 3g titan i guess before i try to root it was 3.0.1 or may be 3.1
but i never try to use a sd card so i dont know if it works
while trying to fix it i wipe the factory, cache but still bricked
best regards
daddymaths said:
hi guys ...i hav some big problem n i really need ur help pls.
i hav tried to root my xoom but it failed n now im afraid i hav bricked my xoom
- unlock ok
- fastboot flash boot boot.img ok
- fastboot reboot fail ( dual core technology frozen)
the only thing that it shows is the dual core technology screen nothing more and when i reset it it starts alone by itself again and stock
i hav a motorola xoom 3g titan i guess before i try to root it was 3.0.1 or may be 3.1
but i never try to use a sd card so i dont know if it works
while trying to fix it i wipe the factory, cache but still bricked
best regards
Click to expand...
Click to collapse
The sd card should not be an issue since you use your computer connected to the Xoom with adb/fastboot when rooting.
Which rooting guide are you using? It does matter, especially for 3G non-US models.
I'm sure you are not bricked. You will need to start again but make sure you have all of the correct files in you platform tools folder (or whatever folder you are using for adb).
If you have successfully unlocked you can skip that step.
You are frozen at the dual core screen because you have flashed an incorrect boot.img for your specific model of xoom, and the android version you have on your xoom a.k.a 3.0-3.2. Since you are on the 3g version make sure you get a 3g boot.img and might as well get both the 3.1 and 3.0.1 boot.Hold the power button and the volume up button at the same time to reboot, wait 3 seconds,and then press only the the volume up button. you should now have a message at the top that says starting fastboot protocol support. begin flashing the images.
rootfan said:
You are frozen at the dual core screen because you have flashed an incorrect boot.img for your specific model of xoom, and the android version you have on your xoom a.k.a 3.0-3.2. Since you are on the 3g version make sure you get a 3g boot.img and might as well get both the 3.1 and 3.0.1 boot.Hold the power button and the volume up button at the same time to reboot, wait 3 seconds,and then press only the the volume up button. you should now have a message at the top that says starting fastboot protocol support. begin flashing the images.
Click to expand...
Click to collapse
Ditto, you will know for sure whenu brick when your screen is black only. You have a little work to do as notedbut stay calm.. You will get things fixed.
rockhumper said:
Ditto, you will know for sure whenu brick when your screen is black only. You have a little work to do as notedbut stay calm.. You will get things fixed.
Click to expand...
Click to collapse
+1 dont jump the gun and read everything over 5x before moving forward... Its a lil work like said but you will probably be more knowledgeable after its all said and done and be able to help others that may be stuck like you one day..
Good luck
Hey guys... I have bricked my xoom too. It's a wifi only xoom. I missed the last step in the guide I was using "fastboot oen lock" and rebooted... so now it stays on the dual core screen. I tried vol up and power buttons to get fastboot and it stays on the starting fastboot protocol... the computer doesn't recognize it. Just don't know what to do next...
Please help...!
Sent from my T959 using XDA App
rickyx said:
Hey guys... I have bricked my xoom too. It's a wifi only xoom. I missed the last step in the guide I was using "fastboot oen lock" and rebooted... so now it stays on the dual core screen. I tried vol up and power buttons to get fastboot and it stays on the starting fastboot protocol... the computer doesn't recognize it. Just don't know what to do next...
Please help...!
Sent from my T959 using XDA App
Click to expand...
Click to collapse
Read the sticky on page one... That says a guide to all your rooting needs... Proceed
This is what scares people
Don't freak out if your xoom won't boot. Your xooms are certainly not nowhere near bricked. >.>
Kippui said:
This is what scares people
Don't freak out if your xoom won't boot. Your xooms are certainly not nowhere near bricked. >.>
Click to expand...
Click to collapse
The word "bricked" gets way too much use... 95% of folks saying they bricked are no where near it...
rockhumper said:
The word "bricked" gets way too much use... 95% of folks saying they bricked are no where near it...
Click to expand...
Click to collapse
I have only seen one bricked xoom so far.
Sent from my PG86100 using Tapatalk
bwcorvus said:
I have only seen one bricked xoom so far.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Dont you know that 50 percent of all statistics are made up? And thats 99 percent of the time
thx guys
i was unfortunately little bit busy with work and exams ....i m relieve ..i will try to follow ur advices and keep u in touch.
thx a lot.
best regards
daddymaths
Is your Xoom still "bricked?" If so, shoot me a PM and I'll help you out. I HIGHLY doubt it is truly bricked.
rooting guide?
okantomi said:
The sd card should not be an issue since you use your computer connected to the Xoom with adb/fastboot when rooting.
Which rooting guide are you using? It does matter, especially for 3G non-US models.
I'm sure you are not bricked. You will need to start again but make sure you have all of the correct files in you platform tools folder (or whatever folder you are using for adb).
If you have successfully unlocked you can skip that step.
Click to expand...
Click to collapse
i have as i say a 3G motorola titan ....could anyone provides me the right routing files ? thx
I have a completely and 100% bricked Xoom. Was in the rooting process, and did something wrong, but the device is totally dead.
No response when plugging in via USB, although white LED illuminates when the power is plugged in.
cdinoz said:
I have a completely and 100% bricked Xoom. Was in the rooting process, and did something wrong, but the device is totally dead.
No response when plugging in via USB, although white LED illuminates when the power is plugged in.
Click to expand...
Click to collapse
Hit power and volume up to reboot...there is nothing the root process can do to brick it. Stop by the irc channel.
Sent from my PG86100 using Tapatalk
Have tried that.... Is still dead, and get no response from the device. Apparently I may have totally wiped the NAND storage....?
cdinoz said:
Have tried that.... Is still dead, and get no response from the device. Apparently I may have totally wiped the NAND storage....?
Click to expand...
Click to collapse
What exactly did you do (or try to do)?
okantomi said:
What exactly did you do (or try to do)?
Click to expand...
Click to collapse
I tried to root the device and install the Tiamat kernel. I was enabling the micro SD slot (or so I thought) and when I dropped in my SD card, there was a warning that the device needed to be re-partitioned. So I did. Didnt format the microSD, seems to have formatted the entire device.
Related to this issue:
http://forum.xda-developers.com/showthread.php?p=14462676#post14462676
cdinoz said:
I tried to root the device and install the Tiamat kernel. I was enabling the micro SD slot (or so I thought) and when I dropped in my SD card, there was a warning that the device needed to be re-partitioned. So I did. Didnt format the microSD, seems to have formatted the entire device.
Related to this issue:
http://forum.xda-developers.com/showthread.php?p=14462676#post14462676
Click to expand...
Click to collapse
That's one of the only two ways to brick it. I would stop by the irc channel, but I think you may have actually bricked it.
Sent from my PG86100 using Tapatalk
Hey guys, a few days ago I finally decided to root my phone and flash cynagen mod 7...
However yesterday evening my touch screen suddenly stopped working, so I can't unlock my phone...
its still showing screen but its not responding when I press anything...
Things ive tried: removing battery for 20 sec, removing battery to turn off the phone and start it up again.
Is it possible to fix this?
or does anyone have the stock Vodafone firmware so I can try flashing it and return it for warranty?
Try reflashing the Rom from recovery again maybe that will help, I think I saw a thread on here about a fix for that problem a few months ago but not sure as I never needed it so didn't read it.
Sent from my HTC Wildfire using XDA Premium App
Scratch0805 said:
Try reflashing the Rom from recovery again maybe that will help, I think I saw a thread on here about a fix for that problem a few months ago but not sure as I never needed it so didn't read it.
Sent from my HTC Wildfire using XDA Premium App
Click to expand...
Click to collapse
You mean re flashing the stock Vodafone rom?
Any place where I can find it?
Btw even clockworldmod doesn't seem to respond to my buttons(the ones below the screen)
Only the physical buttons work...
Sorry I meant try reflashing your cm7 Rom again from recovery, use the volume buttons and the trackball to navigate in clockwork.
Sent from my HTC Wildfire using XDA Premium App
Scratch0805 said:
Sorry I meant try reflashing your cm7 Rom again from recovery, use the volume buttons and the trackball to navigate in clockwork.
Sent from my HTC Wildfire using XDA Premium App
Click to expand...
Click to collapse
ill give it a shot, by the way when I tried to flash with RUU it didn't detect my phone.
Also when I boot up my phone with charge cable it stops responding and only the red charging light will burn(even when the battery is full, because it did this for hours a few days ago)
Also in clockwork when I go to advanced and key test it doesn't do anything when I press a key, It doesn't show anything in the log.
So I think its really broken.
Update: reflashed with cyanogen didn't fix it
And when I try to flash with WUU it says my phone is not connected
ofc I can't access my usb settings on the phone...
The charging bug comes with clockwork, when the phone is off if you plug in the charger it happens so I always make sure to hit the power button first wait till the splash screen has gone and then plug it in, its annoying but just pop the battery out and then reboot the phone. There's a fix for that too but it didn't work for me.
As for the other problems I'm not sure as I've never come across them on my phone before, I would definitely try reflashing first before using an ruu. If that doesn't help hang fire till someone a bit smarter than me sees this.
Sent from my HTC Wildfire using XDA Premium App
Scratch0805 said:
The charging bug comes with clockwork, when the phone is off if you plug in the charger it happens so I always make sure to hit the power button first wait till the splash screen has gone and then plug it in, its annoying but just pop the battery out and then reboot the phone. There's a fix for that too but it didn't work for me.
As for the other problems I'm not sure as I've never come across them on my phone before, I would definitely try reflashing first before using an ruu. If that doesn't help hang fire till someone a bit smarter than me sees this.
Sent from my HTC Wildfire using XDA Premium App
Click to expand...
Click to collapse
I just tried re flashing and that didn't help, I think my screen is really broken.
Including those home, menu back and search button.
only the power and the volume buttons and track ball work...
Update: sometimes my screen seems to work for a few seconds and then it doesn't again...
Depends on how I hold my phone...
gijs007 said:
I just tried re flashing and that didn't help, I think my screen is really broken.
Including those home, menu back and search button.
only the power and the volume buttons and track ball work...
Update: sometimes my screen seems to work for a few seconds and then it doesn't again...
Depends on how I hold my phone...
Click to expand...
Click to collapse
Especialy by saying that last thing, one would think about a bad contact in the cable that connects your motherboard with your screen. I could be wrong, but I think the softkeys belong to the screen as well, so that would explane it. But I'm not sure about that last one.
You can try opening up your phone and see if the connection of the cable to the motherboard is still good. To open up the phone, you can folow the guide for the htc desire, it is said that they are alike.
Keep in mind that the bad connection can be IN that cable as well. So perhaps you have to look if you can buy a seperate cable somewhere (don'y know if that is possible).
I must stress out that I never opened this phone myself, so all the things I say here are based on what I've read on this forum. It just seems logic to me
One more thing: this all sounds risky. But since you are out of waranty, and since your phone doesn't work, I personally would give it a try.
Erwin
ErwinP said:
Especialy by saying that last thing, one would think about a bad contact in the cable that connects your motherboard with your screen. I could be wrong, but I think the softkeys belong to the screen as well, so that would explane it. But I'm not sure about that last one.
You can try opening up your phone and see if the connection of the cable to the motherboard is still good. To open up the phone, you can folow the guide for the htc desire, it is said that they are alike.
Keep in mind that the bad connection can be IN that cable as well. So perhaps you have to look if you can buy a seperate cable somewhere (don'y know if that is possible).
I must stress out that I never opened this phone myself, so all the things I say here are based on what I've read on this forum. It just seems logic to me
One more thing: this all sounds risky. But since you are out of waranty, and since your phone doesn't work, I personally would give it a try.
Erwin
Click to expand...
Click to collapse
I would give it a try, but im not out of warranty, its just voided until I re flash a stock Vodafone firmware.
So if anyone could give me one id be really happy.
Preferably a Dutch/nl one with hboot 1.02
There's links to some ruu's in here, hope you find what your looking for.
http://forum.xda-developers.com/showthread.php?t=1029318
ErwinP said:
Especialy by saying that last thing, one would think about a bad contact in the cable that connects your motherboard with your screen. I could be wrong, but I think the softkeys belong to the screen as well, so that would explane it. But I'm not sure about that last one.
You can try opening up your phone and see if the connection of the cable to the motherboard is still good. To open up the phone, you can folow the guide for the htc desire, it is said that they are alike.
Keep in mind that the bad connection can be IN that cable as well. So perhaps you have to look if you can buy a seperate cable somewhere (don'y know if that is possible).
I must stress out that I never opened this phone myself, so all the things I say here are based on what I've read on this forum. It just seems logic to me
One more thing: this all sounds risky. But since you are out of waranty, and since your phone doesn't work, I personally would give it a try.
Erwin
Click to expand...
Click to collapse
I've changed the touchscreen on mine and can confirm the softkeys are attached to it, there's 2 separate cables though I think the one from the softkeys is only for the led's as mine broke, the buttons work fine but I have no lights behind them.
Sent from my HTC Wildfire using XDA Premium App
gijs007 said:
I would give it a try, but im not out of warranty, its just voided until I re flash a stock Vodafone firmware.
So if anyone could give me one id be really happy.
Preferably a Dutch/nl one with hboot 1.02
Click to expand...
Click to collapse
As you are looking for a ROM with hboot 1.02, I assume that before rooting you had the same hboot? Because then you must have gained root using AlphaRevX/Revolutionary, which installs a custom bootloader. This hboot can, to my knowleadge, not be downgraded to the original one. In other words: you have voided your waranty and there is no way to cover it up...
Erwin
ErwinP said:
As you are looking for a ROM with hboot 1.02, I assume that before rooting you had the same hboot? Because then you must have gained root using AlphaRevX/Revolutionary, which installs a custom bootloader. This hboot can, to my knowleadge, not be downgraded to the original one. In other words: you have voided your waranty and there is no way to cover it up...
Erwin
Click to expand...
Click to collapse
Damn, will they figure this out or is their a change they are just like oh yeah the screen is broken lets fix it?
As its clearly a hardware issue and not a software issue...
Other whys ill just fix it my self or go to a phone store...
update: I tried flashing SUU but it keeps giving me a message that my phone is not connected...
But the phone store told me rooting does not void my warranty as its a hardware issue and not a software issue.. they told me they could send it for me to a special company that repairs phones and is qualified by mayor factories like HTC,Samsung,etc.
But they also told me it would be easier to just contact Vodafone for repairs as that is free and if not I could always come back.
I'd send it back to Vodafone, best case they'll switch the touchscreen power it up for a quick test then send it back, worst case is they may check your software versions... then send it back unrepaired.
I used to fix iphones and ipads for an insurance company and hardly ever had enough time for checking software, just fix it, send it out and crack on with the next one!
Sent from my HTC Wildfire using XDA Premium App
dont panic your phone is all right
It also happened in my case.Go to the following link
http://shipped-roms.com/index.php?category=android&model=Buzz
and flash a suitable ruu rom .it will definitely fix ur phone.or u can just boot into recovery by pressing volume and power button simultaneously during the boot and flash cm 7 rom.
rashmifantasy said:
dont panic your phone is all right
It also happened in my case.Go to the following link
http://shipped-roms.com/index.php?category=android&model=Buzz
and flash a suitable ruu rom .it will definitely fix ur phone.or u can just boot into recovery by pressing volume and power button simultaneously during the boot and flash cm 7 rom.
Click to expand...
Click to collapse
I already re flashed cm7, and at first it didn't help then suddenly it did help and now its doing nothing all over again...
Update: re flashed again and still nothing.
AFAIK reflashing a custom rom from a custom recovery should not solve the issue.
But reflashing a stock ROM (= RUU) should solve that. Also reflashing a stock ota update will solve that. Ota update needs to be flashed from stock recovery. Do either of these things depending on what your hboot version is (if hboot is latest then ota will be option for most times) Also remember PC49IMG method if you presently have custom recovery.
P.S : what all I said is thinking that it is software issue. this shouldn't help if it is related to hardware.
Sent from my Blade using XDA App
I was wondering if there was a way to flash using that method, as I said I never needed to flash an ruu yet so don't know much about em. Just saw your other post explaining how to use PC49IMG to flash an ruu. Thought i'd copy it here as it may help.
bharatgaddameedi said:
If it still had the issue, then install the RUU by pc49img method. Download the correct ruu for your phone. Donot connect phone to PC. On windows PC click on start and type %temp% and enter. This opens the user temporary folder of your PC. Now run the ruu. Now if you observe the temp folder, there will be extra folders created which have folder name enclosed in {} brackets. Search in these folders for the file ROM.zip. Copy the ROM.zip to a safe location. Now format your memory card to fat32 (must) and put the ROM.zip to the root of memory card. You should use memory card reader. Then rename the ROM.zip to PC49IMG.ZIP . Then insert memory card in phone and reboot to hboot menu from where you can update/reflash the partitions. If still not working, clear storage again from hboot menu.
Sent from my Blade using XDA App
Click to expand...
Click to collapse
if ur stock screen is showing a date of 1980(after flashing a custom rom)
Just flash the RUU_Buzz_Froyo_hTC_Asia_WWE_2.24.707.1_Radio_13.55.55.24H_3.35.20.10_release_161113_signed.exe
it will help
Scratch0805 said:
I was wondering if there was a way to flash using that method, as I said I never needed to flash an ruu yet so don't know much about em. Just saw your other post explaining how to use PC49IMG to flash an ruu. Thought i'd copy it here as it may help.
Click to expand...
Click to collapse
Did that and now its on stock Vodafone firmware
But the touch screen still isn't working.
Oh well now I can send it back to Vodafone for repairs.
Thanks for the help
Btw: is their anyway to get the original hboot back?
For maybe some more like me that want to go back to what it use to be with the hboot S-OFF, S-ON issue.
I had my phone S-OFF with alpharevx beta. Used CM7 -stable for couple days but decided i wanted to go back to all original. I first RUU my phone with the RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.2 4H_3.35.20.10_release_160191_signed.exe file. Boot it up, made sured it runs, then did what is instructed below here;
To be able to do this you need HTC USB drivers installed. Install the HTC pakage, reboot, uninstall the HTC-
Sync software, keep the drivers! reboot PC again.
Power off your phone. Plug in your USB cable to phone. Press volume down and powerup your phone. After it
settle navigate down and choose fastboot option.
1. Unpack these files to your c:\fastboot
2. Open up your windows command promt (WinVista/7 users rightclick choose run as Administrator)
3. in command promt type CD\ then press enter
4. then your should be in C:\
5. type cd fastboot
6. then you should now be in dir C:\fastboot
7. Im bored to death typing, look below. Beware of each command ends with enter. After success, reboot.
C:\fastboot>fastboot oem mb 9C068490 1 30
... OKAY
C:\fastboot>fastboot flash hboot hboot_buzz_7225_1.01.0001.nb0
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... OKAY
Files needed (Windows version): megaupload.com/?d=UO9L74I9
Works perfectly for me.
* NOTE: Im not responsible for your phone if you brick/kill it. These steps worked for me!
I have the att s4 with the mf3 build which I received via an ota update. I recently did the root for this build which worked perfectly, afterwards I read through 47 pages of forums and was trying to do the work around djrbliss put out, around page 40 someone says if your phone is rooted just download goomanager and installscriptrecovery. then reboot recovery. I downloaded goomanager then installed script, after this I hit the reboot recovery and the phone went into download mode. and it will stay there. If i restart it returns to download mode. Any Ideas?
Im not 100% but u may hve read wrong. This has happened to everyone who has tryed to flash a recovery on mf3. You can only have root there is no custom recovery for this build. Ok now this is wat you do take your phone to bestbuy tell them kies f'd ur phone up nd they can reflash mf3.at this moment mf3 isnt available to general public
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Yeah, read the forums. I mean seriously, almost every other post, including the one you read, tells you that drjbliss's exploit was patched in mf3, and can brick your device if you attempt to install a custom recovery. It is, quite literally, the biggest topic in the S4 forums. Also, there is no odin flashable image for mf3, so you cannot return to stock without taking it to bestbuy. Read more in the q&a section, as this same mistake has been made and asked about at least a hundred times. Literally.
In conclusion, you have a paperweight till you take it to get it flashed back to normal.
ok thanks for the help
cooljg said:
ok thanks for the help
Click to expand...
Click to collapse
Read this thread. Best buy can flash the stock mf3 firmware and get your recovery back. http://forum.xda-developers.com/showthread.php?p=45457012
Either that or J-Tag.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Hey guys thanks for chiming in. I want to give a thank you to those who have gave me a serious answer. I will go back to best buy and try again, but I sent my wife up there and she said the cell phone department told her they do not flash firmware there. She said she asked them if the service section did and the lady told her no again. I am fairly familiar with flashing the firmware on an s3 I just haven't messed with the s4 that much,and obviously I didn't read as well as I thought I did or it wouldn't be bricked. I do have one other question tho if Best Buy can flash it back to stock firmware, is it safe to assume at some point I should be able to flash it back via odin when the mf3 build is released by sammobile? Either way if best buy doesn't flash it back i'm screwed on this one and i'll just have to pick up another s4 tomorrow. I just want to know if this one can be fixed i'd really hate to waste a perfectly good phone.
If and when mf3 firmware is available you should be able to flash with odin. Best buy seems to be using a new software package other than Odin so who knows if an odin package will be available.
I believe at best buy they have to have a "Samsung Experience" booth or area to do the flashing. The normal best buy service counter can't do it.
~wolverine~ said:
I believe at best buy they have to have a "Samsung Experience" booth or area to do the flashing. The normal best buy service counter can't do it.
Click to expand...
Click to collapse
Correct
Question on brick fix
Hey guys thanks for the helpful info. I took it to the samsung experience part of best buy and the guy fixed it. He didn't have to flash the firmware tho, he took the back off and replaced the battery then I don't know what combination of buttons he hit or what but he held something and it was able to reset the phone and came up normally. Does anyone know what he could of hit? The phone was stuck in download mode no matter what you hit it would only reset to it. I had tried booting and holding volume up and home and releasing home for the recovery boot. As a recap of what happened I had rooted the phone and then downloaded goomanager and ran the installed script option under settings then I reset and was stuck in download mode. I just found it crazy that he never had to hook it to his computer to fix it.
cooljg said:
Hey guys thanks for the helpful info. I took it to the samsung experience part of best buy and the guy fixed it. He didn't have to flash the firmware tho, he took the back off and replaced the battery then I don't know what combination of buttons he hit or what but he held something and it was able to reset the phone and came up normally. Does anyone know what he could of hit? The phone was stuck in download mode no matter what you hit it would only reset to it. I had tried booting and holding volume up and home and releasing home for the recovery boot. As a recap of what happened I had rooted the phone and then downloaded goomanager and ran the installed script option under settings then I reset and was stuck in download mode. I just found it crazy that he never had to hook it to his computer to fix it.
Click to expand...
Click to collapse
Hmm, that is interesting. Did he replace the battery temporarily while 'resetting the phone with combination of buttons'?
Or did he place the battery inside and let you have it?
Sounds like a simple factory reset...
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
haremmon said:
Hmm, that is interesting. Did he replace the battery temporarily while 'resetting the phone with combination of buttons'?
Or did he place the battery inside and let you have it?
Click to expand...
Click to collapse
He originally plugged my phone up when I gave it to him but it wouldn't come on so he unplugged it and replaced the battery. The battery I had was completely dead. After he replaced the battery he turned it on and it went to the download screen with the little green alien. After that he held some buttons and kept looking at the back and then the front of the phone. I couldn't really see what he hit but shortly afterwards it came up with my lock screen picture. After that he said it doesn't need flashing but he would flash the firmware if I wanted so I said ok and he did. I have the phone now working great but it doesn't show rooted anymore.
Omg how do people not know this already. I have had my S4 for 2 days even i know better and I cant believe people dont read