Database Info

[Q] Help! Bricked Skyrocket!!!

I don't really know what happened actually...I was on quickwiz 1.0.3 for about a week and last night my battery drained off completely and the skyrocket shut itself off...after I charged it up this morning, I saw a series of force closes and I did see some interesting message about "system UDI" or something not being compatible...dont remember what it was exactly though...
after that, i thought the device was soft bricked and used k0nane's method of odin to revert it back....the odin said that it was successful and rebooted my device...but, my mobile is now stuck at the bootlogo(at&t rethink possible) and keeps running that boot animation over and over without booting up entirely...
Any suggestions on how to recover from this plz?
I saw that the counter was incremented...so returning this is an issue now...trying to order my jig for that...any help will be greatly appreciated

Did you revert back to stock recovery? If so have you tried flashing cwm recovery using Odin?
Sent from my SAMSUNG-SGH-I727 using xda premium

If you can get into cwm recovery try restoring a nandroid if you made one if not try flashing a rom but wipe data and cache first
Sent from my SAMSUNG-SGH-I727 using xda premium

LoGaN- said:
I don't really know what happened actually...I was on quickwiz 1.0.3 for about a week and last night my battery drained off completely and the skyrocket shut itself off...after I charged it up this morning, I saw a series of force closes and I did see some interesting message about "system UDI" or something not being compatible...dont remember what it was exactly though...
after that, i thought the device was soft bricked and used k0nane's method of odin to revert it back....the odin said that it was successful and rebooted my device...but, my mobile is now stuck at the bootlogo(at&t rethink possible) and keeps running that boot animation over and over without booting up entirely...
Any suggestions on how to recover from this plz?
I saw that the counter was incremented...so returning this is an issue now...trying to order my jig for that...any help will be greatly appreciated
Click to expand...
Click to collapse
you should go into stock recovery Which you have if you flashed Konanes stock file.....and wipe data. if that does not do the trick. i would try wiping data again....doing the stock one more time. i been in that exact same boat, as have others. this is what i did to get out. but others have had luck just flashing 3e recovery and wiping data 3 times, flash CMW via odin and restore a nandroid to get back up and running or staying at stock. its up to you.
hope this helps.

Thanks for the reply man...but I didnt really follow what u said back there ...odining back the tar that k0nane gave should return the unit back to stock-meaning i should have the stock recovery as well...but I dont know why my skyrocket didn't boot up the whole way
Lemme explain what I did initially with my device actually- After I got my skyrocket, I used copperhed's method to flash clockwork cwm thru odin and rooted the device..after that, I flashed the quickwiz 1.0.3 thru the clockwork recovery and the thing I mentioned before happened to me...nothing more, nothing less...after this force close thing I had initially on quickwiz, I tried restoring my previous nandoid backups and all of them stopped at the bootanimation looping...nothing booted the whole way up and yes, I wiped for each restore...with none of them working, I started the k0nane's odining
I actually got this all worked out somehow now and want to share this info as it might help someone who had the same issue...After flashing the k0nane's tar thru odin, I went into the 3e recover and tried a factory reset...it asked me for a password there and i typed in the wrong password a couple of times as i dont know what the right one is...after some wrong attempts, it formatted everything(/data, cache and even the sdcad) and voila...my skyrocket booted up fine...i didnt worry much to do this as I had nothing on my sdcard and also since i have nandroid's of all my previous ROM's
But I still wanna know why this all happened..
all this panic cost me about 30 bucks to order a jig faster thru EMS....and my counter is up by 2 as I odin'd the tar twice thinking it might work

Thanks for the reply man...just figured it out...

A similar thing happened to me once, i flashed cm7 then i flash da_g kernal. After that, my phone was stuck on cm7 logo. I went back to stock and i was stuck at the rethink possible logo. After that i restared my phone into the stock recovery mode and i wiped everything and i was able to get my phone back.

LoGaN- said:
Thanks for the reply man...just figured it out...
Click to expand...
Click to collapse
i think you made this harder than it was, i honestly STILL dont know WHY this happens. but alot of people have had it happen. some say its undervolting( but i never did any of that) others thinks its Da 'gs Kernel which you were on if you flashed QuickWiz and i had his running as well. some think its the CWM itself that that is causing this because it is not for advice.
Over the past week i have STOPPED using Da g's kernel and have not that happen again.
either way, i think you went into a panic, the steps i listed WILL work weather you flashed 3e with odin or Return to stock to get 3e with Odin and WIPE ALL DATA, and CACHE. im glad you got it going though. sorry you waisted your 30 bucks bruh.

thanks for ur concern bro...i just panicked coz i wanted a working phone asap and i thought of returning mine at the att store...so used the ems shipping for faster delivery of the jig...and minutes after I ordered it, I got it all working...u can see the heights of irony here ...nyway....am glad to see it happen atleast once as I will know what to do if this happens again...for the moment, am gonna stay away from the OC kernels...

Did the flash counter reset?
Sent from my SAMSUNG-SGH-I727 using XDA App

LoGaN- said:
After flashing the k0nane's tar thru odin, I went into the 3e recover and tried a factory reset...it asked me for a password there and i typed in the wrong password a couple of times as i dont know what the right one is.....
Click to expand...
Click to collapse
So.... is there some secret 3e factory reset password we need??

DoctorQMM said:
So.... is there some secret 3e factory reset password we need??
Click to expand...
Click to collapse
i have never seen this in 3e.....i would like to know how to get to that screen.

Yeah wtf? Ive never seen a password in any recovery post a picture of this please

hmn...i will try to see if i can do this on the weekend...my flash counter is already up by 2...what harm will it do for one more
if you want,you can follow my procedure and it will ask for it again...just odin the tar given by k0nan and go into the 3e recovery by holdin volume up+down and power on...do a wipe and it will ask for it...
and no, my flash counter didnt reset...have to wait for my jig and try resetting it
silver03wrx said:
Yeah wtf? Ive never seen a password in any recovery post a picture of this please
Click to expand...
Click to collapse

now my skyrocket back screen wont turn on, everytime i tried to get into download my computer pop up messege that cant not find QHSUSB_Dload, anyone can help me out?

So you phone wont so anything? No download mode and no recovery? If so order a usb jig

Bricked G2X

GUYS HELP PLEASE I nullifed my device, left it on all night (unplugged) because I fell asleep. Now, I can't boot to CWM.. I've tried to install stock recovery, but once I turn it on it just stays on the plain, white LG logo. If I hold down volume down + power buttons the same thing happens. Can you guys help me please. I hope I didn't permanently brick my G2X.

U cant permanently brick it. Search the forums there's been a thread like this in the past week
Sent from my LG-P999 using XDA

Use this: http://forum.xda-developers.com/showthread.php?t=1590523
Next time read the little part which is in big bold letters about not turning off your phone with out flashing a ROM or restoring a nandroid immediately afterward.

MrFdhigsKp said:
GUYS HELP PLEASE I nullifed my device, left it on all night (unplugged) because I fell asleep. Now, I can't boot to CWM.. I've tried to install stock recovery, but once I turn it on it just stays on the plain, white LG logo. If I hold down volume down + power buttons the same thing happens. Can you guys help me please. I hope I didn't permanently brick my G2X.
Click to expand...
Click to collapse
Try this method, this will bring your phone back to life. Make sure you root your phone again and install CWM.
http://forum.xda-developers.com/showthread.php?t=1248644
Good luck

thanks guys. I think I lost root access

MrFdhigsKp said:
thanks guys. I think I lost root access
Click to expand...
Click to collapse
Just root your phone again and install CWM and you are good to go

ratza66 said:
Just root your phone again and install CWM and you are good to go
Click to expand...
Click to collapse
No need to root, just nvflash cwm and flash a ROM.

buru898 said:
No need to root, just nvflash cwm and flash a ROM.
Click to expand...
Click to collapse
really? but I when I installed TB it says I have no more root access =( and also my internal storage got wiped. LIFE'S HARD. I blame LG. lol

MrFdhigsKp said:
really? but I when I installed TB it says I have no more root access =( and also my internal storage got wiped. LIFE'S HARD. I blame LG. lol
Click to expand...
Click to collapse
Flash a ROM which is rooted
Sent from my LG-P999

Hey guys, I rooted my friends G2x and everything went fine until I flashed the ROM. Like an idiot, I did not make a nandroid backup...I downloaded BionixReloaded and up it on the sd card. Rebooted to recovery and went through the usual steps. I did a factory reset and formatted the system. However, when I went to flash the ROM, I got the "E: Can't open /sdcard/zROM/*name of ROM*.zip (bad). Now the phone won't reboot which I'm assuming is from formatting the system. I can still get into recovery and download mode....will this method fix the problem? http://forum.xda-developers.com/showthread.php?t=1248644#
Like I said, I'm not very familiar with the G2x, so any help be be appreciated!

I cannot remember for the life of me remember what that error means, but you can just re-download the rom you want and place it in the sdcard by mounting USB storage through mounts and system, and then flash.
Sent from my LG-P999 using xda premium

drscott333 said:
Hey guys, I rooted my friends G2x and everything went fine until I flashed the ROM. Like an idiot, I did not make a nandroid backup...I downloaded BionixReloaded and up it on the sd card. Rebooted to recovery and went through the usual steps. I did a factory reset and formatted the system. However, when I went to flash the ROM, I got the "E: Can't open /sdcard/zROM/*name of ROM*.zip (bad). Now the phone won't reboot which I'm assuming is from formatting the system. I can still get into recovery and download mode....will this method fix the problem? http://forum.xda-developers.com/showthread.php?t=1248644#
Like I said, I'm not very familiar with the G2x, so any help be be appreciated!
Click to expand...
Click to collapse
Make sure the Rom.zip isn't named Rom.zip.zip. if so rename correctly, also can check md5 of the zip to ensure its a good download prior to flashing.
Sent from my ADR6425LVW using xda premium

Thanks everyone for the quick responses. I'm guessing it boiled down to a bad download, but for some reason I could not connect via USB from recovery on my laptop, so I brought it to my friends house and was able to get it to connect so I redownloaded the ROM along with another incase I got the same error, but it worked flawlessly. Thanks again to all that offered help instead of sending me a useless link via LMGTFY!

[Q] Stuck on SGSIII Bootscreen

Before you post, "BLAKDSKF READ OTHER FORUMS BLUSDFLU!!!!!!!111!!!", please, PLEASE, read the whole post. I am not illiterate or a fool. I've spent the last few days researching similar posts, both on xda and other sites, and as far as I've found, this is the only post of this kind on the Verizon SGSIII forums, though there are some that are somewhat similar in the other SGSIII forums (though I think the root of the problem is different). If you can prove me wrong, please redirect.
The Long Story:
ok. SO. I was trying to root my SGSIII, unlock the bootloader, and install CM10. Simple enough, right? Not so. I got through the rooting tutorial at Link 1 relatively smoothly. For the record, I did the composite root and bootloader combo, and I installed CWM Touch Recovery, as per the guide. I also restored the Jellybean Bootchain. I think it was at this point I downloaded Titanium Backup (because forethought is not my forte) and backed up all my apps. I also made a backup with CWM Recovery, but there were errors. I forget the reason, but it aborted backup. I then tried to make a backup onto my external sd card, and some other errors popped up. Mainly that it couldn't find /android.secure (something along those lines) or /sd-ext (might have been something else. I'm going off memory) and skipped them. It still made the backup, so my illiterate, foolish self decided to roll with it and go ahead.
I then went ahead to Link 2, and with it being 2 AM, I stupidly decided to screw trying to figure out how to use Heimdall 1.4rc1 and continue to use ODIN for flashing. After all what's the difference, I thought. One flashing program is the same as another. I flashed the first two files. Well, in truth, I'm not sure if I flashed the first file. Since I just made a single folder for all the SGSIII Verizon flashing stuff, I had two files with similar names at the time. One from Link 1 and one from Link 2. The only difference was one was a boot chain, the other was a boot loader. Also, one ended with .md5 while the other ended with .tar. Sadly I tiredly picked one and flashed it. I think it was the .md5 one, but I'm not sure. Around this point, my micro sd card reader broke, so I decided to just use my other phone (Motorola Photon 4g running Joker's CM9) as a reader of sorts. I swapped them, used my phone to put the zip from Link 2 on it, and swapped them back. I say this because I'm not sure if that is what broke my md5sums or not (more on that in a sec).
Well, surprise, surprise, my phone got stuck on the animated, colorful "4G LTE" boot screen, except it was fully black, though the noise was playing. I think to myself, "No biggie. I'll just restore my previous backup," so I go back to restore it when I get the error 'md5sum mismatch'. I look up the problem, and after extensive, 3AM research (read: clicked the first link on google and blindly followed), I went with one guys advice, which was to create a blank nandroid.md5 file to force the restore. I figured, "Hey. This is pretty risky. I think I'll just restore the bootloader instead of the whole restore." Or at least that's what was going through my head as I went through with restoring the whole backup. Lo and behold, /system was corrupted, I assume, and it aborted restoring it. I reboot my phone only to find out that my phone gets stuck on the SGSIII boot logo. This is where I am now. I would go through with flashing a stock rom onto it to undo everything I've done, but ODIN won't recognize my phone anymore. I can still get into Download and Recovery Mode. All my backups are useless at the moment.
In Short:
I tried to root, unlock the bootloader, and flash CM10 on it
I messed up and ended up restoring a broken backup, md5sums be screwed.
Now ODIN won't recognize my phone and it's stuck at the SGSIII boot screen.
Is there any way to fix this or at least return it back to stock so I can start again?
If there's any other information you need, just ask. I'd be happy to give it. :laugh: This is my first post on these forums, so I'm not sure what information is standard. If you have any idea of what it might be, please drop a comment or something rather than just leaving. I'd like to know that people are actually reading this post.
And on an unrelated note, every time I try to flash with Heimdall, I get an error about there not being a certain .dll file, even though I downloaded the package from Link 2. Am I doing something wrong?
EDIT: I've already tried factory resetting and wiping the cache/dalvik cache. Most of my info is backed up anyway.
Links:
Link 1: http://forum.xda-developers.com/showthread.php?t=2046439
Link 2: http://wiki.cyanogenmod.org/w/Install_CM_for_d2vzw

What happens when you plug your phone into your PC? Have you tried deleting the drivers then reinstalling them either from Samsung or from the Kies program? You really have to try to mess up this phone and it seems like you definitely tried very hard in this regard.
Edit: Idk anything about Heimdall, I use Odin only so I can't help you there.

SlimSnoopOS said:
What happens when you plug your phone into your PC? Have you tried deleting the drivers then reinstalling them either from Samsung or from the Kies program? You really have to try to mess up this phone and it seems like you definitely tried very hard in this regard.
Edit: Idk anything about Heimdall, I use Odin only so I can't help you there.
Click to expand...
Click to collapse
I hadn't noticed before, but my phone doesn't even show a charge screen when plugged in, but that might just be the settings on the phone pre-root. I'm not sure because I left the phone on to see if it was just a time thing. The phone died and I have to recharge it.
After goofing around with the phone while on the charger for a while, I can get a charge screen to show up for a second. The standard "battery with a loading circle" type symbol for this type of error.
I just reinstalled the drivers. I'll let the phone charge for about 10 minutes or so, then test the phone.

dudeman9199 said:
I hadn't noticed before, but my phone doesn't even show a charge screen when plugged in, but that might just be the settings on the phone pre-root. I'm not sure because I left the phone on to see if it was just a time thing. The phone died and I have to recharge it.
After goofing around with the phone while on the charger for a while, I can get a charge screen to show up for a second. The standard "battery with a loading circle" type symbol for this type of error.
I just reinstalled the drivers. I'll let the phone charge for about 10 minutes or so, then test the phone.
Click to expand...
Click to collapse
Well if it died you should leave it on the charger longer than ten minutes if it is charging. If Odin recognizes it, your first step would be to try flashing a stock image.

SlimSnoopOS said:
Well if it died you should leave it on the charger longer than ten minutes if it is charging. If Odin recognizes it, your first step would be to try flashing a stock image.
Click to expand...
Click to collapse
Thanks. It would seem that it now recognizes the phone, from what I can tell. As soon as I get a stock rom, I'll flash it and post an update.

dudeman9199 said:
Thanks. It would seem that it now recognizes the phone, from what I can tell. As soon as I get a stock rom, I'll flash it and post an update.
Click to expand...
Click to collapse
Great! Use Droidstyle's guide or MrRobinson's thread for the proper images. Should be a good starting point.
Sent from my SCH-I535 using xda app-developers app

I just wanted to add that THIS is how you do a first post or any help needed post! Great details and is obvious you researchedyour problem as well.
The errors in cwm are actually normal. I think the corrupt backups are unrelated.
Sent from my SCH-I605 (AKA NOTE 2)

SlimSnoopOS said:
Great! Use Droidstyle's guide or MrRobinson's thread for the proper images. Should be a good starting point.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I've finally booted up into the setup wizard. I guess from here on I can re-root, unlock the bootloader, and *hopefully* get a working backup and eventually flash CM10.
I guess this means Problem Solved? Again, Thanks.
kintwofan said:
I just wanted to add that THIS is how you do a first post or any help needed post! Great details and is obvious you researchedyour problem as well.
The errors in cwm are actually normal. I think the corrupt backups are unrelated.
Sent from my SCH-I605 (AKA NOTE 2)
Click to expand...
Click to collapse
Thanks. I'm just gonna assume that the problems stemmed from swapping the sd card and leave it at that.

dudeman9199 said:
Thanks. I've finally booted up into the setup wizard. I guess from here on I can re-root, unlock the bootloader, and *hopefully* get a working backup and eventually flash CM10.
I guess this means Problem Solved? Again, Thanks.
Thanks. I'm just gonna assume that the problems stemmed from swapping the sd card and leave it at that.
Click to expand...
Click to collapse
Perfect! Which thread did you end up using btw?
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
Perfect! Which thread did you end up using btw?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I used droidstyle's thread for getting the stock rom.

Soft Brick?

Hey guys,
Just experienced what I think is a soft brick. I know that this has been talked about a dozen times, and I have searched. I just want a more experienced yes or no to be sure.
Basically, last night I tried flashing PAndroid on my skyrocket and I went through the format system, format data, factory reset, and wipe cache. Then when I went into flash a zip it said something to the effect of "E: Can't access SD Card". So then I tried to use my band road but that also gave me the error. I then tried to mount the SD card, but it gave me another error. So, guessing that it would just factory reset me, I rebooted.
Now, my phone will vibrate and flash the Samsung logo before going to a black screen (but the screen is on). It also had the symptom of sticky power button for a while with the few second interval buzzing, but I jammed the power button and it seemed to stop doing that and is now doing the aforementioned thing instead.
Should I go use Vincom's soft Brick guide? Also, does anyone have a link to a 7zip extractor that isn't riddled with viruses? (had a hell of a time getting rid of them the first time I rooted haha)
Again, I know this is probably a fairly obvious answer, but yall have just been so helpful in the past that it makes me want to come here before just winging it. And I'm really nervous with this being my first time haha.
Thanks a lot guys, yall are the best!
Sent from my Nexus 7 using Tapatalk HD

Use vincoms guide and Odin back to stock. I just googled for 7-zip and didn't get any viruses. Don't have the original file or I'd put it up on dev host for you
Sent from my SGH-I727 using xda app-developers app

You wiped system. That's why nothing is happening. You should still be able to enter recovery. Now why your recovery was giving you that error is a different story. Go to recovery and copy the version down here.

hechoen said:
You wiped system. That's why nothing is happening. You should still be able to enter recovery. Now why your recovery was giving you that error is a different story. Go to recovery and copy the version down here.
Click to expand...
Click to collapse
Okay, I managed to get into recovery, but I'm still getting the error about the SD card not being mounted. I was looking on Google and I found two different solutions. One was to re flash CWM with Odin, but would that mess up my phone because it already has CWM on it? The other was to reformat my SD card on the computer, but I have no honest idea how to do that haha.
EDIT: v6.0.1.4
Sent from my Nexus 7 using Tapatalk HD

SlushySolid said:
Okay, I managed to get into recovery, but I'm still getting the error about the SD card not being mounted. I was looking on Google and I found two different solutions. One was to re flash CWM with Odin, but would that mess up my phone because it already has CWM on it? The other was to reformat my SD card on the computer, but I have no honest idea how to do that haha.
EDIT: v6.0.1.4
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Re-Flashing cwm won't mess anything up. Formatting the sd card will remove everything on it including the rom you're trying to flash.
Sent from my SGH-I727 using xda app-developers app

Fixed it! Luckily I saved a backup I made yesterday, so I'm back up and running. Thanks for all the help everybody!
Sent from my Nexus 7 using Tapatalk HD

Nice :thumbup:

Getting into TWRP from soft brick

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.