Related
OK so I did the HTCDev unlock perfectly fine, then flashed the Leedroid rom (using cwm) and the kernel (using fastboot), it loaded up and was working great until I made a phone call! Within about 2 minutes of the call it cut out completely (had about 70-75% battery), and I mean it literally just completely shut off and now it won't turn back on. I have done battery pulls, tried a different battery, plugging into charger (but light doesn't even come on!). What is going on?
Sounds like leedroid is your problem
Sent from my PG86100 using XDA
fpineda101 said:
Sounds like leedroid is your problem
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
Yeah I guessed that problem is I can't boot the phone at all, so can't get into fastboot or recovery to get rid of it
Atomix86 said:
Yeah I guessed that problem is I can't boot the phone at all, so can't get into fastboot or recovery to get rid of it
Click to expand...
Click to collapse
Weird... Have u tried vol down+power?
What you could try, take the SD card out and use either another phone or sd adaptor and place on it the PG86IMG.zip file (you can find this in one of the root threads)..........try the volume-down, power button method to see if it boots into recovery.........if this works, then it will read the .zip file.
---------- Post added at 08:34 AM ---------- Previous post was at 08:33 AM ----------
of course, after placing the .zip file on the card, put back into your phone before trying to boot into recovery.
wikdNoob said:
Weird... Have u tried vol down+power?
Click to expand...
Click to collapse
Yes it was one of the first things I tried.
ycats said:
What you could try, take the SD card out and use either another phone or sd adaptor and place on it the PG86IMG.zip file (you can find this in one of the root threads)..........try the volume-down, power button method to see if it boots into recovery.........if this works, then it will read the .zip file.
of course, after placing the .zip file on the card, put back into your phone before trying to boot into recovery.
Click to expand...
Click to collapse
I wish I could do that but I can't boot using any button combination at all
the volume-down/power button method, hold them both down simultaneously for awhile................in the past I've had to do this for about a minute to get it to work.............you may have tried that already but doesn't hurt to try again.
ycats said:
the volume-down/power button method, hold them both down simultaneously for awhile................in the past I've had to do this for about a minute to get it to work.............you may have tried that already but doesn't hurt to try again.
Click to expand...
Click to collapse
Counted two whole minutes while holding them down, nothing :/ beginning to regret buying this now.
that sucks.........did you try finding that .zip file, put on the sdcard, then hold down those buttons for awhile? bTW, when you plug in the charger, do you get a red light?
ycats said:
that sucks.........did you try finding that .zip file, put on the sdcard, then hold down those buttons for awhile? bTW, when you plug in the charger, do you get a red light?
Click to expand...
Click to collapse
Yes I tried placing the file on the memory card, no dice. And no I don't get a red light when plugging into charger. It's as if the ROM or whatever the issue is, has completely destroyed it.
Atomix86 said:
Counted two whole minutes while holding them down, nothing :/ beginning to regret buying this now.
Click to expand...
Click to collapse
Sounds like a hardware issue. How long did you have it before unlocking it? Did you even make sure that the phone ran a few days before screwing around with installing a ROM and Kernel?
Would you buy a new car and not break it in before replacing the factory parts with aftermarket parts?
tgruendler said:
Sounds like a hardware issue. How long did you have it before unlocking it? Did you even make sure that the phone ran a few days before screwing around with installing a ROM and Kernel?
Would you buy a new car and not break it in before replacing the factory parts with aftermarket parts?
Click to expand...
Click to collapse
Used it for about an hour as stock, but that is irrelevant. I wasn't "screwing around" either, I have flashed many phones in my time and always follow the guides provided to completion. The car analogy isn't anything like this, rooting or installing a ROM wouldn't cause a hardware issue any different to a stock ROM would.
Atomix86 said:
The car analogy isn't anything like this, rooting or installing a ROM wouldn't cause a hardware issue any different to a stock ROM would.
Click to expand...
Click to collapse
That is halfway correct. But you said in your original post that you installed a kernel. The kernel is what runs the hardware. If the kernel is set to run the phone out of spec, this could cause hardware issues.
Did you change the max CPU? What about undervolting?
tgruendler said:
That is halfway correct. But you said in your original post that you installed a kernel. The kernel is what runs the hardware. If the kernel is set to run the phone out of spec, this could cause hardware issues.
Click to expand...
Click to collapse
The kernel was the leedroid one, but I thought it only started running that if you booted regularly eg not into fastboot?
Atomix86 said:
The kernel was the leedroid one, but I thought it only started running that if you booted regularly eg not into fastboot?
Click to expand...
Click to collapse
If you installed the ROM and Kernel, you were running it when you made the phone call and the phone went dead. Leeroids kernel, even though he is an excellent developer and I am not saying anything bad about him or his work, changes cpu and undervolting settings which could cause issues with the phone. I am not saying that that is what caused your issue, but it could have been your phone not playing nice with the kernel.
only other thing I would try is leave the battery out for an hour and try again...........but you've probably been down that road.
Yep... sounds to me like a hardware failure. Shiat! :-/
tgruendler said:
If you installed the ROM and Kernel, you were running it when you made the phone call and the phone went dead. Leeroids kernel, even though he is an excellent developer and I am not saying anything bad about him or his work, changes cpu and undervolting settings which could cause issues with the phone. I am not saying that that is what caused your issue, but it could have been your phone not playing nice with the kernel.
Click to expand...
Click to collapse
That is very true, I was just hoping that the kernel "boot up" so to speak could be avoided by opening fastboot and flashing a stock rom back. But as you stated perhaps the undervolting has messed something up. Thank you very much for your insight and help.
ycats said:
only other thing I would try is leave the battery out for an hour and try again...........but you've probably been down that road.
Click to expand...
Click to collapse
Funnily enough this is what i'm going to do now, having a quick google search shows a few people suggesting to do this (im not quite sure what it does, something to do with the phone dispersing the charge it has inside it or some such?), so thanks for the suggestion!
Jakedude2011 said:
Yep... sounds to me like a hardware failure. Shiat! :-/
Click to expand...
Click to collapse
Indeed
ycats said:
only other thing I would try is leave the battery out for an hour and try again...........but you've probably been down that road.
Click to expand...
Click to collapse
Holy crap, this actually worked! Now I just have to find a way of removing that nasty kernel xD
AWESOME! I believe the stock kernel would be in that .zip file if it flashed from recovery.
Ok I did my first root and install for my rezound. I messed with rooting more back when I had my TB and Eris but nothing more than doing some walk-throughs getting some new roms and such. I got Nils business sense 3.6 working great and what a great ROM! However I ran into a (in my head) major problem. With the knowledge of some people here I'm sure 30 minutes with my phone would get it going, but alas I am a noob, but good at following instructions. I'm good with all things tech until we start talking cmd and coding . Build a comp, fix a computer, OCing that kind of thing.
Anyhow, this morning I woke up to a dead phone forgot to charge, no biggy, I put in a new battery and booted...then got stuck at HTC white screen. So I boot into bootloader and all i get is the IMG updating thing and only an option to reboot. Now I'm in a loop. So I take the PHIMG out of root folder and try to boot into recovery and it goes to the white HTC screen with the small loading bar to a black screen that never changes. Cant get into recovery. Next step, using the Hasoon all in one toolkit (though I know I could use cmd myself, this makes my life easier as it accomplishes the same goal) I try to reflash recovery as recommended by someone here. No change. Alas I know my battery is probably getting low and it does NOT charge while turned off!! Lame...So any help would be greatly appreciated!
volcaicstrad37 said:
Ok I did my first root and install for my rezound. I messed with rooting more back when I had my TB and Eris but nothing more than doing some walk-throughs getting some new roms and such. I got Nils business sense 3.6 working great and what a great ROM! However I ran into a (in my head) major problem. With the knowledge of some people here I'm sure 30 minutes with my phone would get it going, but alas I am a noob, but good at following instructions. I'm good with all things tech until we start talking cmd and coding . Build a comp, fix a computer, OCing that kind of thing.
Anyhow, this morning I woke up to a dead phone forgot to charge, no biggy, I put in a new battery and booted...then got stuck at HTC white screen. So I boot into bootloader and all i get is the IMG updating thing and only an option to reboot. Now I'm in a loop. So I take the PHIMG out of root folder and try to boot into recovery and it goes to the white HTC screen with the small loading bar to a black screen that never changes. Cant get into recovery. Next step, using the Hasoon all in one toolkit (though I know I could use cmd myself, this makes my life easier as it accomplishes the same goal) I try to reflash recovery as recommended by someone here. No change. Alas I know my battery is probably getting low and it does NOT charge while turned off!! Lame...So any help would be greatly appreciated!
Click to expand...
Click to collapse
You could download and install the latest global RUU. Rename it to PH98IMG.zip and place it on root of SD. Make sure if your S-On to re lock your bootloader. Also stay away from CWM recovery, Amon Ra or TWRP is your best recoveries of choice.
Samsung Galaxy S3
Trying to do what is suggested but it seems my phone is too dead to boot into hboot, I cannot hold volume down and power to get there when plugged into the computer either.
volcaicstrad37 said:
Trying to do what is suggested but it seems my phone is too dead to boot into hboot, I cannot hold volume down and power to get there when plugged into the computer either.
Click to expand...
Click to collapse
Your going to have to pop in a new battery or find a way to charge your battery externally.
Samsung Galaxy S3
luis86dr said:
Your going to have to pop in a new battery or find a way to charge your battery externally.
Samsung Galaxy S3
Click to expand...
Click to collapse
I was afraid of that...As I look at my desk with 2 OEM batteries and an extended...all dead... :silly:
volcaicstrad37 said:
I was afraid of that...As I look at my desk with 2 OEM batteries and an extended...all dead... :silly:
Click to expand...
Click to collapse
It happens lol. Just stay away from CWM recovery in the future. It doesn't allow you to charge your device when powered off.
Also, I think there is a thread someone made on how to charge your battery externally. Might have to dig it up in the general section.
Samsung Galaxy S3
luis86dr said:
It happens lol. Just stay away from CWM recovery in the future. It doesn't allow you to charge your device when powered off.
Click to expand...
Click to collapse
I am not sure if you ever go into the Development thread but http://forum.xda-developers.com/showthread.php?t=1914215
A great tool to keep around http://www.amazon.com/eForCity-Batt...50853249&sr=8-14&keywords=htc+rezound+charger
Flyhalf205 said:
I am not sure if you ever go into the Development thread but http://forum.xda-developers.com/showthread.php?t=1914215
Click to expand...
Click to collapse
Yeah, I was going to post this:
http://forum.xda-developers.com/showthread.php?t=1711408
Just dug that up, you can use CWM Touch as well. Either or should set you straight.
Samsung Galaxy S3
I actually used the Amon recovery I did hear issues with CWM as I was doing research. So am I to assume amon has similar issues to CMW then?
Flyhalf205 said:
I am not sure if you ever go into the Development thread but http://forum.xda-developers.com/showthread.php?t=1914215
A great tool to keep around http://www.amazon.com/eForCity-Batt...50853249&sr=8-14&keywords=htc+rezound+charger
Click to expand...
Click to collapse
Just placed an order. Thanks, I was hoping to find one in a store around here to get up and running this week, but I guess I'll be out of commission for a couple days.
volcaicstrad37 said:
Just placed an order. Thanks, I was hoping to find one in a store around here to get up and running this week, but I guess I'll be out of commission for a couple days.
Click to expand...
Click to collapse
Amon recovery does not have the battery charging issue. I don't know if you ordered the battery already. But have you tried charging all the batteries?
jdm2008315 said:
Amon recovery does not have the battery charging issue. I don't know if you ordered the battery already. But have you tried charging all the batteries?
Click to expand...
Click to collapse
Yeah I've tried all three with 2 different chargers.
Tonight was second time in about one week when my phone shut itself down at night. Because of that I slept in both times Both times it was connected to charger and battery was full, also there was a lot of updated apps (notifications in status bar). Right before first time this happened I recovered from soft brick. First after recovering phone didn't work well it use to freeze on higher load so I re-installed stock ROM one more time and everything seemed fine.
Now I wonder if it's software or hardware issues. Any ideas?
Cheers in advance.
kaiseris said:
Tonight was second time in about one week when my phone shut itself down at night. Because of that I slept in both times Both times it was connected to charger and battery was full, also there was a lot of updated apps (notifications in status bar). Right before first time this happened I recovered from soft brick. First after recovering phone didn't work well it use to freeze on higher load so I re-installed stock ROM one more time and everything seemed fine.
Now I wonder if it's software or hardware issues. Any ideas?
Cheers in advance.
Click to expand...
Click to collapse
Did you UV/UC your device? And which rom/kernel are you on?
Sent from the Matrix
Donnie Sins said:
Did you UV/UC your device? And which rom/kernel are you on?
Sent from the Matrix
Click to expand...
Click to collapse
No, I didn't UV/UC. I was on rooted stock kernel.
Made factory reset today and installed custom JB ROM today to see if it helps.
I think your problem is a software related one, try using the latest stock Rom, also it may be induced bya virus or a new program which you May have installed, if this didn't help them you should think of a hardware problem.
iper said:
I think your problem is a software related one, try using the latest stock Rom, also it may be induced bya virus or a new program which you May have installed, if this didn't help them you should think of a hardware problem.
Click to expand...
Click to collapse
I was using 4.0.4 official ROM (NEE). And most of my apps are from Play store and only few from a reputable forum.
But as I said, I wiped everything today and installed a different ROM. If everything's OK for a week it will be clear that it was a software glitch.
Maybe it's tired?
****Non of this is of any importance. Just chill the f**k out and relax****
One week after installing custom ROM my SGSII has shutdown at night again. Like last times it was connected to a charger but this time there were no updated apps. So it's not ROM's fault because it happened with custom and stock ROMs.
Is it possible that soft brick damaged some part of phone's hardware (internal flash memory)? When recovering from brick I re-partitioned it.
...
MistahBungle said:
1) There's no such thing as a 'soft brick'. Your phone is either bricked (unfixable other than by authorised repairer/JTAG) or it ain't.
2) Highly unlikely anything firmware related would cause hardware issues like that.
It may well be a hardware issue given it's happened on different roms. If you're still on stock & haven't reset the flash counter, do that & send it in to Samsung/authorised repairer to be looked at assuming your warranty is still good. If it isn't, take it to a local mobile repair shop & have them take a look (if you've gone back to a custom rom, reset the flash counter & back to stock).
Click to expand...
Click to collapse
There's no warranty, therefore I won't be taking it to service center just to hear it needs new motherboard etc. because it'll cost me almost same as to buy another SGSII.
At this moment I'm only interested if there's anything I can do by myself. If not it's time for a new phone I'm afraid. The phone is still perfectly usable but I don't want to risk sleeping in and being late for work and I don't want to buy an alarm clock.
Common sense dictates you try a different battery.
TheATHEiST said:
Common sense dictates you try a different battery.
Click to expand...
Click to collapse
How can it be caused by battery when all times this happened phone was connected to a charger? All times after I turn it on I find a full battery.
...
MistahBungle said:
Do a completely clean install of stock (format cache, data, system, & internal sd card in CWRecovery first, Odin flash after), do not restore any apps (or app data with the exception of contacts/calendar/call logs/sms) via Ti or whatever, clean reinstall a few apps at a time, test for a day or two. Install a few more apps, test for a day or two. And so on.
If it's still happening after you do that, "it's time for a new phone" in your words.
Click to expand...
Click to collapse
Thing is that when the phone got bricked I had no backup of any kind and since internal storage was re-formated we can say that it was fully wiped. I installed stock ROM first. But phone was rebooting on higher load so I did factory reset and wiped dalwik and data. Reinstalled stock ROM again (even re-downloaded to make sure it's not corrupted). This time it wasn't rebooting. But after a couple of night shutdowns I decided to try a custom ROM. I did a full wipe (including internal storage) before installing it. Clearly it didn't help
BTW night shutdown happens about once in a week.
kaiseris said:
How can it be caused by battery when all times this happened phone was connected to a charger? All times after I turn it on I find a full battery.
Click to expand...
Click to collapse
I tried a different battery and Ive noticed when Ive connected it to the charger,a couple of times my phone has switched off as I was facing the screen wanting my sim pin.
This doesnt happen with my original battery.
So it must be the battery.
theunderling said:
I tried a different battery and Ive noticed when Ive connected it to the charger,a couple of times my phone has switched off as I was facing the screen wanting my sim pin.
This doesnt happen with my original battery.
So it must be the battery.
Click to expand...
Click to collapse
But I'm using my original battery. Also like I mentioned earlier all this started after the brick. Therefore I don't think it's the battery.
P.S.Before SGSII I owned HTC Desire for couple of years. I flashed and re-flashed it again and again, never had a brick etc. But when I decide to flash a custom ROM on SGSII for the first time phone gets bricked and even after recovering from brick phone is still f*****-up. Don't get me wrong I love this phone, it's better in every way but it's not exactly "flash friendly". Forums are full of stories of bricked SGSII. That makes me thinking should I choose a Samsung device if I'll be forced to buy a new phone...
kaiseris said:
How can it be caused by battery when all times this happened phone was connected to a charger? All times after I turn it on I find a full battery.
Click to expand...
Click to collapse
Simple, Because you cant run your phone just via charger, it goes from charger to device via battery so if your battery is faulty you could have lost power to device.
kaiseris said:
Thing is that when the phone got bricked
Click to expand...
Click to collapse
You're devcie was never "bricked". If it was your devcie would simply not power on or if it did it wouldnt go into download or recovery mode via buttons or jig.
If you can do the above yor devcie is not bricked. There is no such thing as a "soft brick", that is just a label n00bs like to use as a label for when they cant boot to system. Liek when they get a boot loop etc.
kaiseris said:
But I'm using my original battery. Also like I mentioned earlier all this started after the brick.
Click to expand...
Click to collapse
No it didnt.
kaiseris said:
P.S.Before SGSII I owned HTC Desire for couple of years. I flashed and re-flashed it again and again, never had a brick etc.
Click to expand...
Click to collapse
And you haven't on SGS2 either.
kaiseris said:
But when I decide to flash a custom ROM on SGSII for the first time phone gets bricked
Click to expand...
Click to collapse
No it doesnt.
kaiseris said:
and even after recovering from brick phone is still f*****-up.
Click to expand...
Click to collapse
No you didnt, you simply re-flashed a rom. When you're bricked this cannot be done (without hardware access/replace) hence the word "bricked"[/QUOTE]
kaiseris said:
Don't get me wrong I love this phone, it's better in every way but it's not exactly "flash friendly".
Click to expand...
Click to collapse
Wrong, its very flash friendly. Only thing you need to look out for is wiping data on leaked stock kernel.
kaiseris said:
Forums are full of stories of bricked SGSII.
Click to expand...
Click to collapse
1000% Untrue. They are full of stories from n00bs who "think" they have bricked their device, ie all the silly "soft-brick" topics.
My advice to you would be to check battery pins for bends or corrosion and also swap battery and see if you get different results.
Before any of this though you should try a kernel cleaning script, flash stock rom via ODIN and then flash Siyah kernel.
Jeez man! Why do you waste your an my time typing this long but pointless post?! To show how "l33t" you are? If so please stay away from this thread.
As for battery, if it is faulty why it's still fully charged? Also why does it act-up just once in a while? IMHO battery is quite a simple thing, either it charges or not. It looses it's capacity over time. Mine is about six months old and still lasts me about 36 hours.
kaiseris said:
Jeez man! Why do you waste your an my time typing this long but pointless post?! To show how "l33t" you are? If so please stay away from this thread.
As for battery, if it is faulty why it's still fully charged? Also why does it act-up just once in a while? IMHO battery is quite a simple thing, either it charges or not. It looses it's capacity over time. Mine is about six months old and still lasts me about 36 hours.
Click to expand...
Click to collapse
Because I was trying to help you [email protected] ungrateful moron! How on earth was it trying to sound "l33t" (By the way its "1337").
Your problem is that you create a thread about a problem you have with device and then dont even listen to what you get told with regards to advice from multiple people, ie check rom/kernel/battery. What the hell do you expect any of us to do give you some magic words you can say to solve your problem?
What I wrote was correcting your misconceptions and giving you on advice on how to resolve your issue, Did you even bother to read what I wrote at bottom??
Also you're been very narrow minded if you think that the only symptoms of a faulty battery is if it cant charge or hold charge. Symptoms can also include random drops of output which result in your phone losing power and rebooting or powering off which is exactly what is happening to you. Now I'm not saying this is your exact problem but the fact that you are ignoring this possibility shows how much of a fool you are been especially when been hostile towards people who are trying to "waste their time" helping you.
If you dont want our advice then I suggest you GTFO and find another site to post your problem on.
TheATHEiST said:
n00bs
Click to expand...
Click to collapse
TheATHEiST said:
n00bs
Click to expand...
Click to collapse
TheATHEiST said:
[email protected] ungrateful moron
Click to expand...
Click to collapse
TheATHEiST said:
a fool you are
Click to expand...
Click to collapse
Wow, you're a real "keyboard cowboy". Do you tell same thing to people you don't know in real life? I bet you don't.
I already wrote this but I will repeat it one more time. I did full wipes, flashed a few different ROMs and kernels since this problem started. It didn't affect the problem in any way!
TheATHEiST said:
Now I'm not saying this is your exact problem
Click to expand...
Click to collapse
Reading your posts makes me think opposite. I will repeat myself shutdowns started right after recovering from "soft brick"/"NAND rw corruption" (which ever suits you better). Other reason I don't believe it's battery's fault is that I have never heard about:
TheATHEiST said:
random drops of output
Click to expand...
Click to collapse
in otherwise perfectly working battery.
Like everyone else I owned a bunch of cellphones, laptops, cordless drills, MP3 players and other battery-powered devices but never had such problem or heard about anyone having this exact problem. Would you care to elaborate about it?
TheATHEiST said:
GTFO and find another site to post your problem on.
Click to expand...
Click to collapse
I'm not going to do that only because there are a few "anal" people in this great community.
Ok, you're obviously an idiot and its pointless trying to help you. Good luck trying to find somebody who will help you now after showing how much of a **** you are to people trying to offer advice.
I'm off to play on my fully working i9100.
Bye.
Hi
Got my digitizer replaced and the new one is unresponsive in either cwm or aroma. It works after it boots up.
(haven't tried it with twrp yet but I'm pretty sure that doesn't work either)
What do you guys think? Is it because of a s***ty digitizer?
Another thing is if I let it boot not touching the screen untill it goes to sleep it becomes unresponsive so that I need to do a battery pull.
If I unlock it right after the locckscreen comes up, it works fine...
Thanks
n1c00_ said:
Hi
Got my digitizer replaced and the new one is unresponsive in either cwm or aroma. It works after it boots up.
(haven't tried it with twrp yet but I'm pretty sure that doesn't work either)
What do you guys think? Is it because of a s***ty digitizer?
Another thing is if I let it boot not touching the screen untill it goes to sleep it becomes unresponsive so that I need to do a battery pull.
If I unlock it right after the locckscreen comes up, it works fine...
Thanks
Click to expand...
Click to collapse
It can by digitizer fault but it can bee your phone fault, for example my atrix digitizer become randomly unresponsive until it die (at that moment I think so) then I buy new one and it too don't work, but it can bee so I take magnifier and start look at cables an found microscopic crack. In picture red dot.
So first check your cables and reinstall recovery.
firecode95 said:
It can by digitizer fault but it can bee your phone fault, for example my atrix digitizer become randomly unresponsive until it die (at that moment I think so) then I buy new one and it too don't work, but it can bee so I take magnifier and start look at cables an found microscopic crack. In picture red dot.
So first check your cables and reinstall recovery.
Click to expand...
Click to collapse
Thanks a lot
Me not that brave! Haven't replaced it myself. Suppose I'll just go back with it but need to know what to tell the blocks...
As I said, it does work but not before the system boots up.
Did reinstall cwm. No luck
cheers
LE: Strange enough TWRP is working! It's most probably not a hardware thing...
n1c00_ said:
Thanks a lot
Me not that brave! Haven't replaced it myself. Suppose I'll just go back with it but need to know what to tell the blocks...
As I said, it does work but not before the system boots up.
Did reinstall cwm. No luck
cheers
LE: Strange enough TWRP is working! It's most probably not a hardware thing...
Click to expand...
Click to collapse
You can try to reinstall your ROM, make factory reset, clean caches but if the glitch still exist then I think it is PDS fault. You can try to recalibrate touch screen but make PDS backup before any changes or you can completely kill touch or brick your device.
P.S I think that TWRP is the best recovery.
firecode95 said:
You can try to recalibrate touch screen but make PDS backup before any changes or you can completely kill touch or brick your device.
Click to expand...
Click to collapse
Hi. Thanks. Why would I recalibrate? It works fine after the rom loads
Also flashed pdsfix. Nope. No good
Any other ideas?
n1c00_ said:
Hi. Thanks. Why would I recalibrate? It works fine after the rom loads
Also flashed pdsfix. Nope. No good
Any other ideas?
Click to expand...
Click to collapse
Did you try to reinstall your android ROM?
firecode95 said:
Did you try to reinstall your android ROM?
Click to expand...
Click to collapse
Man, I'm dualbooting GB on emmc and PA299 on sdcard!
http://forum.xda-developers.com/showpost.php?p=37554860&postcount=13
n1c00_ said:
Man, I'm dualbooting GB on emmc and PA299 on sdcard!
http://forum.xda-developers.com/showpost.php?p=37554860&postcount=13
Click to expand...
Click to collapse
Maybe you can make a backup and try to reinstall your rom to clean state?
Well I think it is because you have dual boot but I am not sure.
Thanks. I'm flashing my Atrix 3 times / day
Sent from my MB860 using Tapatalk 2
Mine having same problem can some one help go this thread
http://forum.xda-developers.com/showthread.php?t=2181311
Sent from my MB860 using xda premium
I just cracked the screen on my i605 yesterday, and they're sending me a replacement today. What are the odds that it'll have 4.3 on it? Because, I'd really like to unlock the bootloader.
crbnfbr said:
I just cracked the screen on my i605 yesterday, and they're sending me a replacement today. What are the odds that it'll have 4.3 on it? Because, I'd really like to unlock the bootloader.
Click to expand...
Click to collapse
Just got my "new" replacement phone, and yep 4.3 on it. So, no unlocking the boot loader. Is there any way I can installed sophisticated ROM, or better yet CWM recovery?
crbnfbr said:
Just got my "new" replacement phone, and yep 4.3 on it. So, no unlocking the boot loader. Is there any way I can installed sophisticated ROM, or better yet CWM recovery?
Click to expand...
Click to collapse
No there is not at this moment.. sad to say.. There is one option but it might cost you about a $100.. You could look online for a 4.1.2 motherboard for i605, the specific model.. it very simple to swap out..took me only about 15 mind and I have never done it before.. If your not comfortable PM me and I can recommend someone you can send it to that guarantees their work/parts for 3 months.. good luck man!:good:
lacoursiere18 said:
No there is not at this moment.. sad to say.. There is one option but it might cost you about a $100.. You could look online for a 4.1.2 motherboard for i605, the specific model.. it very simple to swap out..took me only about 15 mind and I have never done it before.. If your not comfortable PM me and I can recommend someone you can send it to that guarantees their work/parts for 3 months.. good luck man!:good:
Click to expand...
Click to collapse
I actually tries "saferoot" and so far so good. I'm still waiting to see if it'll restore my data through Titanium Backup. Root checker does show it is rooted though.
I though about taking the mobo out of my cracked screen phone and swapping it once I booted this replacement and saw it was 4.3.
crbnfbr said:
I actually tries "saferoot" and so far so good. I'm still waiting to see if it'll restore my data through Titanium Backup. Root checker does show it is rooted though.
I though about taking the mobo out of my cracked screen phone and swapping it once I booted this replacement and saw it was 4.3.
Click to expand...
Click to collapse
Dude thats a GREAT idea! You should.. as long as it was not damaged with the phone..
You can root 4.3 just fine.. that is the same method I used when I did it.. Make sure evrything is installing properly and you have no errors when the script runs through..
If you need any helping swapping motherboard out.. Hit me up in a PM and I can maybe provide some pointers..
lacoursiere18 said:
Dude thats a GREAT idea! You should.. as long as it was not damaged with the phone..
You can root 4.3 just fine.. that is the same method I used when I did it.. Make sure evrything is installing properly and you have no errors when the script runs through..
If you need any helping swapping motherboard out.. Hit me up in a PM and I can maybe provide some pointers..
Click to expand...
Click to collapse
Is it just a matter of taking out all the baby silver screws, and connecting some ribbon cables? Also, will I still keepxmy CWM recovery and old sophisticated root?
I've done dzens of pc mobos but never a phone.
crbnfbr said:
Is it just a matter of taking out all the baby silver screws, and connecting some ribbon cables? Also, will I still keepxmy CWM recovery and old sophisticated root?
I've done dzens of pc mobos but never a phone.
Click to expand...
Click to collapse
Yes..thats all it takes.. Umm not to sure.. Whatever you had on your old one might still be there.. not sure if it resets or anything..
If you have done PC's then it should be no problem for you.. take your time..just smaller pieces..
Good Luck!:good::highfive:
lacoursiere18 said:
Yes..thats all it takes.. Umm not to sure.. Whatever you had on your old one might still be there.. not sure if it resets or anything..
If you have done PC's then it should be no problem for you.. take your time..just smaller pieces..
Good Luck!:good::highfive:
Click to expand...
Click to collapse
I've already sealed it up in the return envelope, but I'll cut it open for a chance to run a custom recovery and better root. I just don't think I can last a full year before my contracts up.
Even if it does reset my CWM backup I'd hope would restore everything.
crbnfbr said:
I've already sealed it up in the return envelope, but I'll cut it open for a chance to run a custom recovery and better root. I just don't think I can last a full year before my contracts up.
Even if it does reset my CWM backup I'd hope would restore everything.
Click to expand...
Click to collapse
Worse case scenario is just running CASUAL again and unlocking it. Let me know what happens:good:
lacoursiere18 said:
Worse case scenario is just running CASUAL again and unlocking it. Let me know what happens:good:
Click to expand...
Click to collapse
At the very least I'll at least I'll get my boot loader unlocked, CWM recovery and sophisticated rom all back.
crbnfbr said:
At the very least I'll at least I'll get my boot loader unlocked, CWM recovery and sophisticated rom all back.
Click to expand...
Click to collapse
Well, I swapped the old mobo with the new one. Now, neither the old mobo or new mobo works with the replacement phone. I made sure everything was connected the same way, but still it won't even power on.
crbnfbr said:
Well, I swapped the old mobo with the new one. Now, neither the old mobo or new mobo works with the replacement phone. I made sure everything was connected the same way, but still it won't even power on.
Click to expand...
Click to collapse
That does not make any sense... Did you watch that video? and stupid ? is your battery charged?
I watched the video. Battery was at like 90%. Now with the now mobo in the new phone if I hit the power button 3 times the LED will turn red, but when it's pliugged in charging it doesn't do anything.
I did leave the speaker and antenna from the new mobo in the replacement phone. Do I need to swap those too?
crbnfbr said:
I watched the video. Battery was at like 90%. Now with the now mobo in the new phone if I hit the power button 3 times the LED will turn red, but when it's pliugged in charging it doesn't do anything.
I did leave the speaker and antenna from the new mobo in the replacement phone. Do I need to swap those too?
Click to expand...
Click to collapse
I can now get the green LED light to come one with the new mobo and charger plugged in if I hold the power button, but that's all it will do.
crbnfbr said:
I can now get the green LED light to come one with the new mobo and charger plugged in if I hold the power button, but that's all it will do.
Click to expand...
Click to collapse
Sounds like something wasn't put together right.. I would start over and make sure all is connected properly.. And this motherboard was from same device correct? Not like one from tmobile, sprint etc ect Verizon to Verizon..
Yeah, it was from a i605 I got two weeks short of a year ago. I also agree about something not being put together right. I'm going to swap the antenna and speaker too.
crbnfbr said:
Yeah, it was from a i605 I got two weeks short of a year ago. I also agree about something not being put together right. I'm going to swap the antenna and speaker too.
Click to expand...
Click to collapse
Ok..I didnt have to that.. and i was in the same scenario.. but just make sure you go over everything carefully...:highfive:
lacoursiere18 said:
Ok..I didnt have to that.. and i was in the same scenario.. but just make sure you go over everything carefully...:highfive:
Click to expand...
Click to collapse
Well, I've made some progress. It boots up with the blue LED and I can hear the Verizon chime, but I get absolutely nothing on the screen. It's completely black.
crbnfbr said:
Well, I've made some progress. It boots up with the blue LED and I can hear the Verizon chime, but I get absolutely nothing on the screen. It's completely black.
Click to expand...
Click to collapse
Weird sounds like something is not hook up to the screen? You didn't force it open and mess the screen up right..
Sent from my SCH-I605 using xda app-developers app
I'm thinking I must have messed up a ribbon cable by accident. The insurance company is going to send me a new one, and I'll just keep the locked bootloader and "saferoot" so I can use Titanium Backup and Rom Toolbox.