Related
I successfully flashed to att ICS using Jim's method. Then I decided to roll back to 2.3.6 and used Jim's ICS back to 2.3.5 fxz fix zip file. The RSD stopped at 5/19 reboot bootloader for a long time and the screen was off. I hit the power button trying to turn on the screen without thinking. Then I realized that I was flashing! It was too late and I saw FAILED on RSD. My A2 cant turn on anymore. I did not unplug or pull the battery. Any help would be appreciate!
qtqt710 said:
I successfully flashed to att ICS using Jim's method. Then I decided to roll back to 2.3.6 and used Jim's ICS back to 2.3.5 fxz fix zip file. The RSD stopped at 5/19 reboot bootloader for a long time and the screen was off. I hit the power button trying to turn on the screen without thinking. Then I realized that I was flashing! It was too late and I saw FAILED on RSD. My A2 cant turn on anymore. I did not unplug or pull the battery. Any help would be appreciate!
Click to expand...
Click to collapse
DId you replace ALL of the files and then point the RSD to the xml?
Can you boot into fastboot by holding power button and vol down.If can you just reflash it using rsd lite.Tell me more detail about your atrix 2 current rom and which version of rom you are flash with rsdlite.
Sent from my MB865 using xda premium
Exact same problem has occurred to me as well.
I did replaced the files Jim created to FXZ back to 2.3.6 from ICS
My Battery was fully charged at the time of flashing. Flashing stopped at 5/19 reboot bootloader for 15 mins then tried rebooting it manually but it didn't started.
Now I've tried everything but it is not even starting in Fastboot
Please help me with this, I don't want to start any new thread so posted my problem here.
EDIT: I think this is a common problem as the OP here also have the same problem
http://forum.xda-developers.com/showthread.php?t=1781045
http://forum.xda-developers.com/showthread.php?t=1700775
I only flashed ICS when Jim confirmed that it was possible to revert back to 2..3.5
I think there is a problem in reverting back to 2.3.5 once applied ICS update and people should be aware of that.
Everyone should stop flashing ICS leaks otherwise they might end up bricking their phone forever.
100% same to me.
Up to ICS ok, back to Fxz with RSD and stuck at 5/19 reboot-bootloader step, I disconnected cable and phone black forever.
A lot of people they failed when flash with RSD but no problem, just take battery out and return, boot again to fastboot to re-flash. I think wrong file in Fxz not makes this problem, main cause I still don't know ! Maybe we are unlucky man ?
FXZ is not wrong one as I did used it when I had to flash back to stock from lithium Rom last week. I think phone is dead because it is not even booting into fastboot.. I've tried even booting to our stock recovery by pressing 3 buttons but no luck so far.
Its just very bad few hours back I was running ICS and now my phone is not even booting up.
OMG man!! I should have make a thread about this yesterday, but maybe nobody would of paid attention. I didn't really want this to happen to anyone, when flashing from 4.0.4 back to 2.3.5 it will get stuck at 5/20, something like that saying "rebooting loader". Now my phone with a blackscreen is getting hot when I insert the battery and when I plug it without a battery into my laptop or wallcharger and I dont have warranty. I call it white LED of death, when I plug it in to my laptop without a battery hehe , so I guess i'll be paying maybe 200$ dollar for it to be repaired, well if they repair it though, they charge so much here.. But i'm still trying to look what I can do, before I take it to a repair shop.
I heard about this problem when leak ICS for China/HK market 1 month ago, from xda man, and Jim he warned everybody here take care when coming back GB from ICS leak should make your phone bricked.
Now ATT ICS leak was released and all trusted Devs here confirmed that we can turn back to GB without problem, so I thought that it was safe to do with. Next day Jim posted new thread with new patch file. So sad ... I'm too late, we're too late ...
vinamilk said:
I heard about this problem when leak ICS for China/HK market 1 month ago, from xda man, and Jim he warned everybody here take care when coming back GB from ICS leak should make your phone bricked.
Now ATT ICS leak was released and all trusted Devs here confirmed that we can turn back to GB without problem, so I thought that it was safe to do with. Next day Jim posted new thread with new patch file. So sad ... I'm too late, we're too late ...
Click to expand...
Click to collapse
I didn't even flashed ICS leak first day, I did it second day when Jim confirmed and uploaded a link for new replace files.
prasannapmv said:
I didn't even flashed ICS leak first day, I did it second day when Jim confirmed and uploaded a link for new replace files.
Click to expand...
Click to collapse
So this is the point that I'm very confused, I think that even failed flashing phone still powered on normally : wrong boot.img --> just jamed at boot logo, wrong bootloader --> screen turn on and shows errors; need to be flashed again by RSD or script. Some man here even not flashed anything, just root then reboot and phone dead without any reason.
vinamilk said:
So this is the point that I'm very confused, I think that even failed flashing phone still powered on normally : wrong boot.img --> just jamed at boot logo, wrong bootloader --> screen turn on and shows errors; need to be flashed again by RSD or script. Some man here even not flashed anything, just root then reboot and phone dead without any reason.
Click to expand...
Click to collapse
I guess it has something to do with our bootloader, maybe it's stuck or not even working.
darkmixta said:
I guess it has something to do with our bootloader, maybe it's stuck or not even working.
Click to expand...
Click to collapse
I just talked to a Motorola service person he was saying in some rare cases a inbuilt ROM(read only memory) chip which stores bootloader files gets corrupted and in that case it might not even be possible to boot into fastboot.
I don't know how far he is right but one ting we are sure that our hardware was perfectly ok before flashing FXZ.
For me I even made sure that my battery was fully charged before starting FXZ.
prasannapmv said:
I just talked to a Motorola service person he was saying in some rare cases a inbuilt ROM(read only memory) chip which stores bootloader files gets corrupted and in that case it might not even be possible to boot into fastboot.
I don't know how far he is right but one ting we are sure that our hardware was perfectly ok before flashing FXZ.
For me I even made sure that my battery was fully charged before starting FXZ.
Click to expand...
Click to collapse
Same here I had like 90% battery or more, is you're phone becoming hot? When you plug it in or insert the battery?
darkmixta said:
Same here I had like 90% battery or more, is you're phone becoming hot? When you plug it in or insert the battery?
Click to expand...
Click to collapse
yes its getting heated when connected to a wall socket or on a battery.
Did anyone upgrade RSDlite to 5.7 before trying this by any chace?
That might be an issue.
Also, this could be something that was introduced to later model phones. My a2 was able to fxz back, but it ws made in SEPT 2011. Just another thought.
Sent from my SAMSUNG-SGH-I747 using xda premium
prasannapmv said:
yes its getting heated when connected to a wall socket or on a battery.
Click to expand...
Click to collapse
Hahaha, what should we do? Yesterday I felt like throwing my phone into the wall man and just %$#@ Motorola, this is like the biggest failure ever!! Hard bricked without doing something wrong.. Wish I could go back in time sometimes and I don't even have warranty which sucks, what are you gonna do?
Really hard to hard brick? http://forum.xda-developers.com/showpost.php?p=28324515&postcount=10
We hard bricked so easy..
jimbridgman said:
Did anyone upgrade RSDlite to 5.7 before trying this by any chace?
That might be an issue.
Also, this could be something that was introduced to later model phones. My a2 was able to fxz back, but it ws made in SEPT 2011. Just another thought.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I was already using RSD 5.7
jimbridgman said:
Did anyone upgrade RSDlite to 5.7 before trying this by any chace?
That might be an issue.
Also, this could be something that was introduced to later model phones. My a2 was able to fxz back, but it ws made in SEPT 2011. Just another thought.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I did not. It is 5.6. That may be the reason. I got my A2 from att in Nov 2011, so I guess it is the same earlier version, right?
To those with the issue, can you not get back into ap fast boot? Either hold both volume buttons down with power, then select it from the menu, or i have found that holding up with power will boot you right into fastboot.
Sent from my MB865 using xda premium
Fall of Enosis said:
To those with the issue, can you not get back into ap fast boot? Either hold both volume buttons down with power, then select it from the menu, or i have found that holding up with power will boot you right into fastboot.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Nope they can not even power on anymore. This is what we all feared. The hk leak had this same thing in it...
Looks like moto will be warrantying a bunch of phones.
I am just not sure why I can still do it...
We have had way too many of these now for it to be user error or an accident.
Sent from my SAMSUNG-SGH-I747 using xda premium
Just picked up my G3, rooted and unlocked bootloader as soon as i got home. Downloaded one of the jelly bean roms and cwm, did a backup then flashed the rom. Everything looked fine but the screen went dark after the boot animation then nothing. Wont power up or reset using the power home volume combo. What the heck do i do now, thanks for any help.
Might be a stupid question, but have you pulled the battery?
Be more specific.
VZW GALAXY S 3 4G LTE
Do YOUR homework first
How about reading all the threads about unbricking. It certainly seems you did not read all the threads about rooting the phone. Do that too.
Finally, and I know this is not that helpful. Don't screw with a new phone. Use it at least for a month to make sure there are no problems with it.
That being said, there is plenty of information about how to handle your problem here in xda. Read all that and try what has already been posted before asking people to solve your self inflicted problem.
BTW when you do ask for help specify exactly what you did, with what script. I.E. don't ask someone to solve your problem without you taking the time to be very specific about how you got there.
pull the battery and go into recovery or odin and fix it.
Dead battery?
Sent from my Transformer TF101 using xda premium
Skubacb - Don't be a douche buddy. If you do not have any thing to add then shut the **** up.
With that being said I have been rooting phones for years, never had an issue when I couldn't get the phone to at least go into recovery. The phone is dead. Battery was fully charged and I have done a battery pull. It is a Verizon G3. I have read the unbrick articles but none explain if the phone will not boot into recovery. If someone could could just point me in the correct direction I would greatly appreciate it.
How did you actually do the flash? Odin? Some other way? As noted, more details are needed.
I flashed the new rom using Rom manager, went in to revovery and flashed it
jmill75 said:
I flashed the new rom using Rom manager, went in to revovery and flashed it
Click to expand...
Click to collapse
I don't believe rom manager is supported for our phone yet. U need to flash straight from recovery. That said I'm sorry I'm not sure where u go from here.
Sent from my SCH-I535 using xda premium
If you can't get into either recovery , or download mode you maybe SOL. However I would take this to IRC and see if someone can help on there. #verizons3 channel.
If the phone is under warranty, one other alternate solution is to take it into a VZW store and say it won't start. Of course I'd only go that route if I couldn't get it going any other way. On the plus side, your could at least confirm that battery didn't die on you.
Looks like you forgot to flash the insecure bootloader, buddy.
Sent from my SCH-I535
Rom manager is supported I flashed clockwork there And the 3 cm nightlies
Sent from my SCH-I535 using Tapatalk 2
Keep this discussion to technical solutions only, please. Leave gray area ethics out of it.
JMink said:
I don't believe rom manager is supported for our phone yet. U need to flash straight from recovery. That said I'm sorry I'm not sure where u go from here.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Completely incorrect.
mikeew83 said:
Rom manager is supported I flashed clockwork there And the 3 cm nightlies
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Me too, been doing it since 6.0.1.2
abissel22 said:
Looks like you forgot to flash the insecure bootloader, buddy.
Sent from my SCH-I535
Click to expand...
Click to collapse
I'm gonna go with this one (possibly). Did you unlock the phone? Sorry, did you say it won't boot into anything? Download/Odin mode? Recovery? Anything at all when you do the vol up/down, home key, and power button?
Idk if this would help but I'd order a downloader jig off ebay for a couple dollars and use that to see if it'll boot to recovery
Sent from my GT-I9300 using xda app-developers app
Me too
I went to turn on my Verizon SGS3 on this morning and nothing happened. I have not even rooted it yet. It was charged when I turned it off 5 minutes before that and even did a battery swap. Phone is completely dead. Will not turn on. I have had it since it first came out, so I called Verizon and they are over-nighting me a "like-new" one. I hope I don't hear more of these stories.
jmill75 said:
Just picked up my G3, rooted and unlocked bootloader as soon as i got home. Downloaded one of the jelly bean roms and cwm, did a backup then flashed the rom. Everything looked fine but the screen went dark after the boot animation then nothing. Wont power up or reset using the power home volume combo. What the heck do i do now, thanks for any help.
Click to expand...
Click to collapse
I had a similar issue. If you do the volume/home/power combo (try both volume buttons separately, i forgot which one worked) and hold them through the initial Samsung logo it should put you into download mode, where you can Odin back to stock. I used PureMotive's Unbrick method in the Dev section (I think) and it took all of 20 min. Just make sure to follow the directions carefully.
Sent from my SCH-I535 using xda app-developers app
Is there a difference is button sequence between recovery and download mode? (I thought it was the same thing)
Sent from my SCH-I535 using XDA Premium App
Okay, so here's a long story short. I flashed AT&T ICS leak #2 when I first got my replacement due to a brick. I ran SCV7 for a week or so and decided to try out CM10. I restored my backup of stock/rooted backup. Uninstalled highjacks, packages and app (bootmenu) itself. I then installed our OG A2 bootstrap, installed fine, installed CM10, played around with it for awhile. Realized I didnt reinstall the OG A2 Bootstrap so went ahead and did that. (without booting into recovery yet) I then later in the day decided to REBOOT my phone to only find me stuck on the CM10 boot animation. I battery pulled, plugged in to see if any recovery would show, none, just the battery charge percentage. I then battery pulled again, got into stock recovery, tried a data and cache wipe to no effect. My problem is, there is NO FXZ for the AT&T leak #2, I have no recovery besides stock and the only thing I can do is take my 32GB SD card out and add/delete files/everything. I saddly did not make a copy of the system.img but was wondering if anyone else possibly did? This would be greatly appreciated as I am stuck with a soft brick until then or a new FXZ to work with AT&T leak #2. Any suggestions or help is very much appreciated. Thanks all for reading and I'm praying for a miracle in my phone right about now lol!
DX2Trip said:
Okay, so here's a long story short. I flashed AT&T ICS leak #2 when I first got my replacement due to a brick. I ran SCV7 for a week or so and decided to try out CM10. I restored my backup of stock/rooted backup. Uninstalled highjacks, packages and app (bootmenu) itself. I then installed our OG A2 bootstrap, installed fine, installed CM10, played around with it for awhile. Realized I didnt reinstall the OG A2 Bootstrap so went ahead and did that. (without booting into recovery yet) I then later in the day decided to REBOOT my phone to only find me stuck on the CM10 boot animation. I battery pulled, plugged in to see if any recovery would show, none, just the battery charge percentage. I then battery pulled again, got into stock recovery, tried a data and cache wipe to no effect. My problem is, there is NO FXZ for the AT&T leak #2, I have no recovery besides stock and the only thing I can do is take my 32GB SD card out and add/delete files/everything. I saddly did not make a copy of the system.img but was wondering if anyone else possibly did? This would be greatly appreciated as I am stuck with a soft brick until then or a new FXZ to work with AT&T leak #2. Any suggestions or help is very much appreciated. Thanks all for reading and I'm praying for a miracle in my phone right about now lol!
Click to expand...
Click to collapse
Hey, and sort of welcome back...
But I hate to be the bearer of bad, bad news... you have a softbrick, and there is NOTHING you can do.
Next time, read everything in an OP... LOL, look who I am telling this to....
The CM10 installs come with their own CWM built in, and flashing bootstrap is what bootlooped you, so after you get another warranty replacement (yes, you HAVE to do this), I would install leak #1 ONLY, then flash cm10 with bootstrap, then do not reinstall any boot hijacks or CWM "like" recovery (bootmenu), because all you have to do it hit the vol down button right as you see the blue led flash during the M dual core logo.
Or enter the CM10 recovery menu and so on and so forth.
This is how I got out of a cm10 boot-loop.
I just restored from bootmenu backup via adb.
tcf38012 said:
Or enter the CM10 recovery menu and so on and so forth.
This is how I got out of a cm10 boot-loop.
I just restored from bootmenu backup via adb.
Click to expand...
Click to collapse
he can't, he installed bootstrap while on cm10m, so he can't get to cwm anymore.
Scratch that ----- Deleted
Well, thanks everyone. Specially you jim. Anyone wanna throw me an fxz they think MIGHT work for the second ICS leak? I'm willing to take the risk since I have nothing else to lose. Ill be most likely calling AT&T tomorrow and give some excuse. Soft brick or hard brick...Ill get a replacement...
Sent From My Eclipsed DROID X2!
DX2Trip said:
Well, thanks everyone. Specially you jim. Anyone wanna throw me an fxz they think MIGHT work for the second ICS leak? I'm willing to take the risk since I have nothing else to lose. Ill be most likely calling AT&T tomorrow and give some excuse. Soft brick or hard brick...Ill get a replacement...
Sent From My Eclipsed DROID X2!
Click to expand...
Click to collapse
I will get with alteredlikeness and see if we can possibly think of something together on this one. The first thought would be to try an mearet/searet fxz for 2.3.6 since they can fxz back with out any mods to thier 2.3.6 or 2.3.5 fxz from thier ICS leaks, but I am thinking that will still brick you, but interested to see anyhow.
So I will see if alteredlikeness and I can think of some other way to try. He or I will PM you either way.
jimbridgman said:
I will get with alteredlikeness and see if we can possibly think of something together on this one. The first thought would be to try an mearet/searet fxz for 2.3.6 since they can fxz back with out any mods to thier 2.3.6 or 2.3.5 fxz from thier ICS leaks, but I am thinking that will still brick you, but interested to see anyhow.
So I will see if alteredlikeness and I can think of some other way to try. He or I will PM you either way.
Click to expand...
Click to collapse
he can flash just a system. img from ics though, And that should recover it
Sent from my MB865 using xda premium
lkrasner said:
he can flash just a system. img from ics though, And that should recover it
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
You know, I was seeing in recovery how youbcan flash an update through sd AND system which has a lost and found folder and recovery folder. Dont know if this is of any info but either way because I wouldnt know how to put anything in system since I cant seem to get adb to recognize or moto-fastboot...I'm in a very confused state of mind and almost came to the point of hard brick but I refuse. I'll leave it up to ya devs. Thanks againg everyone.
Sent from my MB870 using xda premium
i have same issue , any way to flash system img, and where whould i get system img from? i have preiviously backed up thru cwm
justdrew said:
i have same issue , any way to flash system img, and where whould i get system img from? i have preiviously backed up thru cwm
Click to expand...
Click to collapse
Try following this:
http://forum.xda-developers.com/showthread.php?t=1926873
First Softbrick it seems In Trouble
jimbridgman said:
Try following this:
http://forum.xda-developers.com/showthread.php?t=1926873
Click to expand...
Click to collapse
Guys need your urgent help i am into a trouble what is it called technically may be a Soft brick but this is what has happened.
I was trying the Magic mod the installation went superb booted the phone it worked properly and then i used the bootstrap :silly: and tried starting the phone in recovery after which my phone is now stuck at magic mod boot animation. PLEASE HELP.
I am upto a point where have installed drivers latest rsd lite 6.0 ready with the extracted fxz 6.7.2_EDEM-18-SEARET_cfc.xml but phone is not showing up in rsd lite so that i can flash my phone. Phone says USB connected in AP Fastboot mode have a look at the attachment of my desktop. Please HELP guys....
Thanks & Regards,
Beginner Android (Ravi D)
havent you just posted this in the any question answered here thread and getting help there ??
Wow, almost forgot I made this thread lol. But sounds like your drivers need a good updating. Reboot PC after updating and try again is all I can say. Hope this helps.
Sent from my MB865 using xda premium
Hello,
I'm truly hoping someone can help me. I spent all night installing new roms on my phone. Ok let me back up. This is bout the tenth phone I've rooted. I rooted my blaze about 2 months ago using a one step(I think can't remember.) I never really installed a custom Rom until last night. The first Rom I installed was cm10, which I liked. Only problem was I couldn't mount my sd card because I am no where near a computer. So I decided to install the baked Rom. I was ecstatic to find that everything worked. However, the cm10 Rom seemed to be running at the same time. I found that very weird. So I tried to figure out a way to get the cm10 off my phone. For hours I tried wiping and reformatting different things from recovery. My problem is the last time I rebooted my blaze out wouldn't go past the Samsung screen. I've tried all combos of the volume up down and power key and it never goes past Samsung. I'm assuming I've bricked my. It will show the battery charging screen. 1st it'll show the stock screen then the baked screen for charging. Please help me. I've searched xda for help and can't find anything to help.
Ps. I'm not at a computer now but please list help for when I'm able to get to one. And yes I've only gotten about 3hrs of sleep in the last 20hrs from messing with my phone.
Sorry for posting in development first meant to post here.
Odin to stock uvlh5. From sammobile.com/firmware
Edited... because I speak without thinking
^ what he means is download the stock ICS ulvh5 firmware from sammobile.com/firmware for the blaze/sgh-t769 and flash it on Odin.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Thats why I have the sammobile firmware and odin on a backed up. I've tried to learn from my mistakes well that's what I have learned a lot here hahahaha
Oh i remember reading you are not around a PC a lot... you need a PC for ODIN sounds like you can't get into recovery so PC only other way I know of. If I helped push thanks
how do you flash it exactly
myssdion said:
how do you flash it exactly
Click to expand...
Click to collapse
Dude just Google your quote plus a few more words and follow instructions.
Or this http://forum.xda-developers.com/showthread.php?t=1591601 . If your soft bricked you need to go back to gingerbread. Than upgrade accordingly ICS than jelly whatever. Hope works out for you
jbats said:
Dude just Google your quote plus a few more words and follow instructions.
Or this http://forum.xda-developers.com/showthread.php?t=1591601 . If your soft bricked you need to go back to gingerbread. Than upgrade accordingly ICS than jelly whatever. Hope works out for you
Click to expand...
Click to collapse
Yeah, I thought about that right after I asked. Thanks for the help. Got my phone back to working with a custom rom I'm too happy
myssdion said:
Yeah, I thought about that right after I asked. Thanks for the help. Got my phone back to working with a custom rom I'm too happy
Click to expand...
Click to collapse
Glad to hear that
Greetings. I found myself in a situation of being stuck at Alcatel splash screen after rebooting following a flash. Phone wouldn't respond to adb/fastboot commands, or upgrade tool. I kept powering off, and rebooting holding combo of power, vol up, down, and both. Finally after several tries, it booted into TWRP! I wish I could say it was a particular combo, but it was just repetition of power off, and combo of power/ vol buttons. Was able to do this twice with this "method". I have 60450 (Cricket). This Phone doesn't respond how I am used to getting into download (power+vol down), or recovery (power+vol up) Hope this helps if you find yourself in a similar situation.
I've developed an issue as well. I can get into twrp just fine and all is fine there but any combination of ROM or kernel even stock makes my phone reboot every 2-5 minutes. Last night after messing around with a few cm builds and then going back to stock after I couldn't get the phone to cool down..... Stock no longer wanted to cool down either. It's been running way to hot so I turned it off for the night. Turn it back on today and same issues. It even restarts on the powered off battery charging screen , I took it a step further and deleted system, data, cache, and internal storage as well as removing my external sd so no ROM or files was on it at all and it still wanted to reboot at the charging screen! Only place it doesn't is in TWRP. I'm not sure if it's a battery safety issue because it's noticing how hot the device is but I was proven wrong with that too, put it in the freezer for 3 mins and it rebooted then too lol. I'm not sure what to do as even download mode reboots. Wtf. Idk if maybe there's some stock files I could attempt to flash through adb? Can anyone help?
have you tried to flash some stock rom? there is a thread around here which has some twrp backups on stock roms. maybe it helps to get into download mode and repair the phone with the Q.
jani0417 said:
have you tried to flash some stock rom? there is a thread around here which has some twrp backups on stock roms. maybe it helps to get into download mode and repair the phone with the Q.
Click to expand...
Click to collapse
Just did. Damn i thought for sure it was the answer, but nope, the phone has rebooted 3 times since i just restored the backup from that thread 20 mins ago. It feeezes for a sscond and then will reboot. Whats even worse is it soemtimes doesent let me charge the phone when powered down. Instead of showing the charging battery screen it just boots up into Android. Its highly annoying. I can get into download mode, it just won't stay there.
that suxx. did you unlocked the bootloader? maybe you should relock it.... it's just an idea, really don't have any more idea
jani0417 said:
that suxx. did you unlocked the bootloader? maybe you should relock it.... iitt's just out oan idea, really don't have any more idea
Click to expand...
Click to collapse
i want to see if twrp is causing the pgone to reboot of download mode. i need ghe stock recovery img for 60450 bu i cant find it.
carnivalrejectq said:
i want to see if twrp is causing the pgone to reboot of download mode. i need ghe stock recovery img for 60450 bu i cant find it.
Click to expand...
Click to collapse
HEre's the original recovery
https://mega.nz/#!NsEXkJZY!S-W9OtDSHVi3EBVcHBKdLX_Ru0yKrGI8g4saaHAtgPY
aleksandar.d123 said:
HEre's the original recovery
https://mega.nz/#!NsEXkJZY!S-W9OtDSHVi3EBVcHBKdLX_Ru0yKrGI8g4saaHAtgPY
Click to expand...
Click to collapse
Thanks. Unfortunately it didn't work. No matter what I do the phone reboots out of DL mode during the process and ruins it. I'm at My wits end with this phone. Have never had this many issues before. I've done everything. I even used the backup from that old thread to restore stock for 6450. All should've been well but I got reboots even on stock at 90% charged. What's very strange is the only thing I can do to keep this from rebooting is use YOUR kernel from the latest Flyme ROM. No idea why but reboots are minimal with it. They still happen but a lot less. All other ROMs and kernels have issues.
carnivalrejectq said:
Thanks. Unfortunately it didn't work. No matter what I do the phone reboots out of DL mode during the process and ruins it. I'm at My wits end with this phone. Have never had this many issues before. I've done everything. I even used the backup from that old thread to restore stock for 6450. All should've been well but I got reboots even on stock at 90% charged. What's very strange is the only thing I can do to keep this from rebooting is use YOUR kernel from the latest Flyme ROM. No idea why but reboots are minimal with it. They still happen but a lot less. All other ROMs and kernels have issues.
Click to expand...
Click to collapse
Sorry for your trouble, but i dont know why you havent send your device to warranty repair allready and instead of that you wrote your troubles across several threads
DallasCZ said:
Sorry for your trouble, but i dont know why you havent send your device to warranty repair allready and instead of that you wrote your troubles across several threads
Click to expand...
Click to collapse
I found him a flashable stock that he got to work. Part of, if not all, of his problem is I think he only has access to a sub-par pc or tablet or something. Anyway, I remember when I didn't know how important it is to have patience and not freak out, and quite a few people had the patience for me , and guided me. I learned. Perhaps this is where he is at. I post things that I have run into, and figured out to try and repay the kindness shown to me. He was trying on his own to figure it out, and that is WAY better than people who don't even try to search, and expect others to do everything for them. This is a community, and just like life, people are at different places. As long as someone is trying, I will try to help if I can. You can't send a rooted phone running CM for warranty.
EDIT: Turns out the reason the upgrade app wasn't working is because i didn't have enough space for the update to download on the PC . I didn't realize because the app never stated why it was restarting my phone or disconnecting so I just assumed it was related to why my phone kept restarting on all ROMs. Wow lol I feel so damn stupid for not thinking of this 2 days ago. Its installing now and hopefully this fixes my reboot issues. Thanks to everybody here for helping and answering my 1000 question's on every post. Really appreciate it.
carnivalrejectq said:
EDIT: Turns out the reason the upgrade app wasn't working is because i didn't have enough space for the update to download on the PC . I didn't realize because the app never stated why it was restarting my phone or disconnecting so I just assumed it was related to why my phone kept restarting on all ROMs. Wow lol I feel so damn stupid for not thinking of this 2 days ago. Its installing now and hopefully this fixes my reboot issues. Thanks to everybody here for helping and answering my 1000 question's on every post. Really appreciate it.
Click to expand...
Click to collapse
Hey......we all get flustered and forget the basics sometimes. Plus, for me, this phone doesn't respond like all the HTC, Nexus, and Samsung phones I've rooted and modded. That, and the insistence for every carrier/region to have their own variant, even on these cheaper phones. The T-Mobile Note 3 and 4 were even different depending on whether you had the black or white one! Hope this gets you back to normal, and if you don't have an SD card, at least get a cheap 8gb, and keep a stock backup on it. I've had that be a lifesaver more than once. Good luck my friend, and maybe stick to stock rooted? Lol
dongarritas said:
Hey......we all get flustered and forget the basics sometimes. Plus, for me, this phone doesn't respond like all the HTC, Nexus, and Samsung phones I've rooted and modded. That, and the insistence for every carrier/region to have their own variant, even on these cheaper phones. The T-Mobile Note 3 and 4 were even different depending on whether you had the black or white one! Hope this gets you back to normal, and if you don't have an SD card, at least get a cheap 8gb, and keep a stock backup on it. I've had that be a lifesaver more than once. Good luck my friend, and maybe stick to stock rooted? Lol
Click to expand...
Click to collapse
All is back to normal, no reboots. I do have an SD card and did have a backup the thing is though I accidentally saved another back up over the original with custom kernel so it was useless lol. And oddly the reboots sort of stopped happening right before but I was using the custom kernel from Flyme which is the only one that seemed to be working. I'm hoping that the issue is with root and not a hardware one from the phone getting to hot flashing things.