Develop Bugs

black screen

i rooted my device but some games wont play like need for speed and asphalt 7 so i installd and its the last thing i did on my device (chainfire3d) then my device reboot and keep reboot wont open help please wait for answer

Sounds like this is a very similar problem to something someone else posted in the last few days. Take a look through the last couple of days posts in this forum and see if you can see it. The general suggestion if i remember right was to use ODIN to fix.

wisewood said:
Sounds like this is a very similar problem to something someone else posted in the last few days. Take a look through the last couple of days posts in this forum and see if you can see it. The general suggestion if i remember right was to use ODIN to fix.
Click to expand...
Click to collapse
can u show me the link i still searching for now and the only solution i found is change my stock ROM and i wont do that wanna get my official updates i think that's better
wanna know what to do by Odin to fix my device and in the same time keep my official system

i seen other problem got the same name but i mean my device wont open just galaxy note ii welcome screen and keep it my device wooont open any one help please what to do by odin ??????

no one answer developers forums xD
thanks will leave google helps more

Read before you install, chain fire 3d does not work with jellybean 4.1.
I think the description in the play store also said enough

Amazes me why people dont read ?
It clrearly says not for jelly bean
You need to find your desired stock rom and flash it via odin. Only solution

Why do you install things which aren't supported?
It's the first thing people should do when installing unconfirmed stuff.
Chainfire 3D isn't supported for JB.
What you need to do now is go into DOWNLOAD mode, and flash your stock ROM via Odin, if you want official.

thanks all its my mistake am new , and i said sorry for my note lmao , well now i need to search for good custom room

i download nandroid and platinum backup and i backup my apps&system wz data got .gz files i think on my sd-card and got nandroid backup on my sd-card (nandroid back up like 4 files) one of them .md5 and its 1kb others .tar 500mb and 700mb cach and system and est i think didnt remember they are on my sd-card is that help me by odin ? because i cant open my device any way my only solution by odin mode but is there any file in my back up files can help ? forget i tried to restore my device by nandroid.md5 and odin closed not response , dont say iam lucky new in android world understand nothing for now

You don't need to flash custom ROM, bro. If you want official rom, just go to sammobile.com, find the firmware of your country and flash it through odin. There, you have official stock ROM again.
Also your English is extremely hard to understand. Try to use commas and full-stops.

[Q] Failed Sprint Note 2 Root Stuck in Loop, Dev not answering

I attempted a root on Samsung Note 2 Sprint version (in white). Followed all steps, however phone got stuck in a reboot loop right after I put the option 2 (root only) Odin step in. Sprint ver LPH889 (I believe that is what Odin is calling it, option 72). Toolkit used was ADB 4.1.0.
Original symptoms were that the Android updater was looping trying to load everything; being new I made it worse and tried recoveries and reloads which also failed. Now it boots, goes to splash, circling blue oval image and...it stays there.
Good news: I have access to download mode and recovery reset mode (including sideloading).
Bad news: every thread I've followed has given me an issue.
I have recovery access but I need some idea of where to go from here and searches have shown near but not exact symptoms. I have unplugged it from the pc, removed the battery, done a factory reset, attempted to reflash via Odin (root) attempted to reflash stock via Odin and so far I am still stuck in a reboot loop. Windows detects the phone but shows a problem in device manager because possibly it won't stop rebooting. Any help you can provide is appreciated and if at all possible I need to recover some form of working phone here, and soon. My girl needs it for work and Sprint's network in my area barely works from day to day (which they admit but don't credit my account for). This phone has problems sending/receiving calls, they claim it's fine, and I was forced to try a root to get some form of working device. That failed too.
I'm a newb at this...it's been years since I flashed a phone (Razor v3), so...any help would be appreciated, otherwise I have to crawl to sprint/samsung and get it replaced, which I don't want to do. Thanks.

doesitwork? said:
I attempted a root on Samsung Note 2 Sprint version (in white). Followed all steps, however phone got stuck in a reboot loop right after I put the option 2 (root only) Odin step in. Sprint ver LPH889 (I believe that is what Odin is calling it, option 72). Toolkit used was ADB 4.1.0.
Original symptoms were that the Android updater was looping trying to load everything; being new I made it worse and tried recoveries and reloads which also failed. Now it boots, goes to splash, circling blue oval image and...it stays there.
Good news: I have access to download mode and recovery reset mode (including sideloading).
Bad news: every thread I've followed has given me an issue.
I have recovery access but I need some idea of where to go from here and searches have shown near but not exact symptoms. I have unplugged it from the pc, removed the battery, done a factory reset, attempted to reflash via Odin (root) attempted to reflash stock via Odin and so far I am still stuck in a reboot loop. Windows detects the phone but shows a problem in device manager because possibly it won't stop rebooting. Any help you can provide is appreciated and if at all possible I need to recover some form of working phone here, and soon. My girl needs it for work and Sprint's network in my area barely works from day to day (which they admit but don't credit my account for). This phone has problems sending/receiving calls, they claim it's fine, and I was forced to try a root to get some form of working device. That failed too.
I'm a newb at this...it's been years since I flashed a phone (Razor v3), so...any help would be appreciated, otherwise I have to crawl to sprint/samsung and get it replaced, which I don't want to do. Thanks.
Click to expand...
Click to collapse
What method are you using to root.....I used the "toolkit" and had no problems at all.
http://forum.xda-developers.com/showthread.php?t=1957155....try this if you haven't already

vel7wil said:
What method are you using to root.....I used the "toolkit" and had no problems at all.
http://forum.xda-developers.com/showthread.php?t=1957155....try this if you haven't already
Click to expand...
Click to collapse
I thought it would to but I did not want to dig through 70+ pages of the thread when searching failed...unless I really needed to. Most of it is old and doesn't apply.
I was directed by the referenced Youtube vid. I used the options referenced for the phone in this thread with that toolkit. I backed up existing files (not as one unit, but internal files and I think OS), went for the option 2, followed the instructions and things went great through odin...until android went to update and started looping with the 'updating files' percentages. At that point I tried to restore to basic and started clearing caches and such and that is how I got to where I am.
When that failed I started looking at the leaked stock flash and that failed on shoot.ini which that guy never addressed because he thought his international version was all versions (that's why I choose 'doesitwork?' as screen name ). So i'm down to sideloading or something. I really need guidance, and I emailed the toolkit author but I'm still waiting on a reply.
Any thoughts?

doesitwork? said:
I thought it would to but I did not want to dig through 70+ pages of the thread when searching failed...unless I really needed to. Most of it is old and doesn't apply.
I was directed by the referenced Youtube vid. I used the options referenced for the phone in this thread with that toolkit. I backed up existing files (not as one unit, but internal files and I think OS), went for the option 2, followed the instructions and things went great through odin...until android went to update and started looping with the 'updating files' percentages. At that point I tried to restore to basic and started clearing caches and such and that is how I got to where I am.
When that failed I started looking at the leaked stock flash and that failed on shoot.ini which that guy never addressed because he thought his international version was all versions (that's why I choose 'doesitwork?' as screen name ). So i'm down to sideloading or something. I really need guidance, and I emailed the toolkit author but I'm still waiting on a reply.
Any thoughts?
Click to expand...
Click to collapse
When used the toolkit a year ago, I found that I had to turned off all firewalls and antivirus apps for it to work properly. Once I did that it worked fine....give it a shot...can't hurt......might even be able to repair what you've done so far.....Good Luck!!!

I'll give this my best shot...download a rooted rom from the development section and place it on your SD card.
Download toolkit from here (I take no credit for this) http://d-h.st/iu0
Put phone in download mode.
Open ODIN and uncheck "auto reboot". Then click "PDA" and add the .tar file (recovery).
Plug phone into PC (make sure to have samsung drivers installed).
Once ODIN sees the phone you can click "start".
When the recovery flash is complete, pull your battery to ensure power down.
Boot into recovery : volume up, home, power all at the same time.
Flash rooted rom.

Toolkit is an extra and unnecessary step.
http://rwilco12.com/downloads.php?d...ung Galaxy Note II (SPH-L900)/Stock ROMs/MC2/
Grab the one click flavor of choice. Use the one with 1090526 in the name as that's the full version.
Open in windows, put phone in download mode and flash. Easy Peasy.
Let me know if you have any issues with this.

Sorry for the late reply, I had some issues with the "catchpa".
The one click fix worked like a charm, thank you! I will soon be making a contrib to the site. It's a shame I couldn't root as easily :laugh: .
I know the level of work that goes into this stuff and the desire to keep on top of new gear while maintaining support for the old and I appreciate the community coming to my aid, so again, thank you!

---------- Post added at 08:14 AM ---------- Previous post was at 07:36 AM ----------
[/COLOR]
doesitwork? said:
Sorry for the late reply, I had some issues with the "catchpa".
The one click fix worked like a charm, thank you! I will soon be making a contrib to the site. It's a shame I couldn't root as easily :laugh: .
I know the level of work that goes into this stuff and the desire to keep on top of new gear while maintaining support for the old and I appreciate the community coming to my aid, so again, thank you!
Click to expand...
Click to collapse
It is usually a pretty common courtesy to hit the "thanks button" when someone helps you out.
I am not at all trying to be mean, just letting you know.

garwynn said:
Toolkit is an extra and unnecessary step.
http://rwilco12.com/downloads.php?d...ung Galaxy Note II (SPH-L900)/Stock ROMs/MC2/
Grab the one click flavor of choice. Use the one with 1090526 in the name as that's the full version.
Open in windows, put phone in download mode and flash. Easy Peasy.
Let me know if you have any issues with this.
Click to expand...
Click to collapse
hello @garwynn im trying to do this same thing.. its been so long since ive odin'd, how would i put TWRP on this now after these steps? i tried goomanager and that didnt work. (couldnt find recovery) and i tried flashing in stock recovery and got a fail . im kind of lost right now and am wondering if there is another way or do i have to do the toolkit? thanks
edit: for some reason, the tool kit links have been pulled by a mod. ..but this video helped me get twrp back. phew. zedomax to the rescue.. http://www.youtube.com/watch?v=7leb9OznhqY

[Q] Odin can't read PIT

Phone Stats
Sprint Galaxy S3 (SPH-L710)
Cyanogenmod 10.2 (Stable)
Last ROM update flash was months ago, no issues
TWRP latest
Can not get into recovery
Can get into download mode (using HOME+VOL-DOWN+POWER)
Using Odin 3 (1.85)
Phone was sitting on table, just started boot looping.
Tried to flash (everything) - stock Sprint image, CM ROM, etc.
Odin fails when it gets to reading the PIT information.
I looked everywhere for a Sprint GS3 PIT file, only found one, but it was labeled "i710" (probably by accident) and did not work.
If anyone has or can dump an image of their partition information (PIT) I would be extremely grateful, and willing to compensate you, because I'm an Android developer and kinda need my phone =)
More information:
Yes drivers are all installed and working. Phone is recognized as usual on three different laptops.
Yes phone was charged at least over 80% when trying anything.
Yes, tried multiple cables and USB ports (esp. powered ones) - phone connects fine.
Brought it to Sprint - they actually tried to flash it for me (nice guys!) but the software denied b/c of the custom binary.
Yes, I read every post here/elsewhere containing the keywords "PIT", "S3", and "brick" - many solutions would work, except for the fact that Odin won't get past reading the PIT.
No, I didn't do anything dumb like flashing GSM, international, custom crap, or by checking "repartition" or anything like that.
Not using any custom kernel or anything else - only the recovery (TWRP) and ROM (CM10) are custom.
Even more information (yes, I'm desperate!):
I tried all methods I could find - literally days worth of searching - including reinstalling the drivers, installing drivers while in download mode, connecting from Windows 7, Windows 8, Windows 8.1, and Linux (Ubuntu - Mint).
Tried flashing stock recovery.
Tried flashing stock Sprint/Samsung image.
Tried flashing various PIT files claiming to be Sprint SGS3.
I basically gave in and was going to buy a new phone, but the dude at Sprint even said "this is fixable - you just need that PIT file", so I'd like to give it one last try before calling it. The phone really has been good to me, otherwise.
Any help is greatly appreciated! If you read all of this, you're a saint =)

Adding Odin output

CorporalMaxSterling said:
Adding Odin output
Click to expand...
Click to collapse
Relevant thread for anyone following:
http://forum.xda-developers.com/showthread.php?p=48376031#post48376031

DELETE: I see you have another thread about this already
sent from my GS3

joeyhdownsouth said:
DELETE: I see you have another thread about this already
sent from my GS3
Click to expand...
Click to collapse
Thanks. That's real helpful. It's not my thread, it's a related one I found after I posted, and this info is still relevant.

[Q] Phone stuck at logo after flashing stock ROM

Hi,
This is my first post here on the XDA forum so if I make any mistakes, please do tell.
So, I got a Galaxy Ace 2 (I8160) which was running unrooted and stock at Android 2.3.6 (if I recall correctly).
I decided I wanted the phone to run at a newer Android version (KitKat preferred), so I decided to look into Cyanogenmod 11.0.
I succesfully installed the Clockworkmod Recovery after soms attempts and after that I was able to install Cyanogenmod 11.0 running on Android 4.4.4.
My first impression was positive, until I noticed I regularly got some error messages about com.android.phone which stopped working.
On top of this, the phone had no service and I was unable to make any calls (also selecting a service provider made com.android.phone crash).
After a lot of looking around on the internet, I found out this could be caused because I flashed Cyanogenmod 11.0 directly from Android 2.3.6.
On another tutorial I read I should've flashed Cyanogenmod 11.0 from any Jellybean version but as I stated earlier, I flashed it from a Gingerbread version.
On another forum I found someone who used to have the same issue and stated that he made the same mistake as I did (flashing from a non-Jellybean version).
He said he flashed a stock Jellybean ROM to his phone, installed Clockworkmod Recovery and at last flashed Cyanogenmod again and everything seemed to be working just fine.
I decided to do the same and flashed a stock Jellybean ROM for the I8160 using Odin v3.07.
After Odin told me the flash process passed, the phone rebooted but was stuck at the Samsung Galaxy Ace 2 logo.
When trying to get into the recovery, I got the same problem and the only thing I saw was the startup logo.
If I'd turn off the phone and plug in to my computer (which normally shows the battery percentage) it'd be stuck at the loading icon (normally this loading icon is visible for about 5 seconds and after that the battery percentage is visible).
I'm still able to get into download mode, so I tried reflashing the same ROM but unfortunately without success.
I used the following stock ROM: samsung-updates.com/details/28857/Galaxy_Ace_2/GT-I8160/XEN/I8160XXNB1.html.
I've been using the Cyanogenmod 11.0 and GApps files from: maclaw.pl/downloads/.
Does anybody have any idea about how I coud fix this?
Thanks in advance.
EDIT: Just tried flashing a stock ROM with Android 2.3.6, problem is still there: samsung-updates.com/details/18868/Galaxy_Ace_2/GT-I8160/H3G/I8160NELG2.html

In my opinion, You should flash 3-parted Firmware
http://forum.xda-developers.com/showpost.php?p=53921158&postcount=8
PS. Sorry for my bad English.

ChuckMichael said:
In my opinion, You should flash 3-parted Firmware
http://forum.xda-developers.com/showpost.php?p=53921158&postcount=8
PS. Sorry for my bad English.
Click to expand...
Click to collapse
Thanks for you reply.
I came across this 3-parted firmware flash a few hours ago.
I'm trying it right now. I'll let you know what the results are.

Alright, another update. (My problem seems to be fixed!)
At first I tried downloading the 3 files neccessary for the new flash method, but for some reason it'd take me hours to download them.
I started looking on the internet for the same files and found a torrent link on another forum leading to a torrent file uploaded here, on the XDA forums: http://forum.xda-developers.com/attachment.php?attachmentid=1757643&d=1361735404.
I downloaded the files in the torrent and used them properly in Odin.
The flashing process started and at about 80% Odin gave me a nasty error message saying the flash failed...
At that moment I was seriously hopeless and pretty sure I've just succesfully hard-bricked my phone.
I tried to start it and I got a weird message saying a firmware update went wrong and that I should fix it using Samsung Kies.
As it stated, I tried using Samsung Kies but was unable to get my phone to work.
I was out of options so I decided to give the 3-way flashing method a second chance.
Oding started flashing and for some reason finished succesfully this time.
The phone reboots, and shows the 'Samsung Galaxy Ace 2 GT-I8160' message for a few minutes.
After that the Samsung logo pops up and I've waited for another few minutes until a new screen pops up.
I see the Android guy and a blue progress bar underneath and patiently waits untill it's done.
After this I see the Samsung logo again and the phone finally boots to Android! Great Success!
Conclusion in my case: The 3-parted firmware seemed to do the trick for me.
As I stated above, the first flash failed but the second one was totally succesfully and revived my phone.

kolsthoorn said:
Alright, another update. (My problem seems to be fixed!)
At first I tried downloading the 3 files neccessary for the new flash method, but for some reason it'd take me hours to download them.
I started looking on the internet for the same files and found a torrent link on another forum leading to a torrent file uploaded here, on the XDA forums: http://forum.xda-developers.com/attachment.php?attachmentid=1757643&d=1361735404.
Click to expand...
Click to collapse
Yeb - you can use also the 3-parted MB4 (which was an very early JB FW).
But as the MB4 is not 100% complete - I still recommend only to use the 3-parted FWs linked by me (which ChuckMichael shows you)
But anyway - If your Phone booted you are done - You do not need to to it again. Just flash afterwards the newst original FW available.

Failed root attempt left tablet at the Samsung screen

I have been searching the forum and google and have been unable to reach a solution yet.
I am not a noob, but i am not an expert either so use small words ha.
I have a Samsung Galaxy Tab 3 10.1 5210 with the most recent OTA update.
Last night I attempted to root my device using this:
androidxda (DOT) com/root-samsung-galaxy-tab-3-10-1-gt-p5210
It claimed successful and my device started to reboot and hung up at the Samsung GALAXY TAB 3 screen. I am unable to get to recovery mode on the device. Only able to go to download mode. I have tried several options but have been unable to find a way to flash it successfully. The flashes i have tried downloading were all in .zip and that obviously isn't able to be used in Odin. I have researched how to convert the files into a .tar but I don't have linux. Can someone please help me because I need my tablet. I know it can be saved but I can't seem to locate the answers. I am also getting concerned that it is unable to charge the battery being in the condition it is in now so I am trying to conserve the battery on the tablet until it is absolutely needed. Thanks.

cameron72 said:
I have been searching the forum and google and have been unable to reach a solution yet.
I am not a noob, but i am not an expert either so use small words ha.
I have a Samsung Galaxy Tab 3 10.1 5210 with the most recent OTA update.
Last night I attempted to root my device using this:
androidxda (DOT) com/root-samsung-galaxy-tab-3-10-1-gt-p5210
It claimed successful and my device started to reboot and hung up at the Samsung GALAXY TAB 3 screen. I am unable to get to recovery mode on the device. Only able to go to download mode. I have tried several options but have been unable to find a way to flash it successfully. The flashes i have tried downloading were all in .zip and that obviously isn't able to be used in Odin. I have researched how to convert the files into a .tar but I don't have linux. Can someone please help me because I need my tablet. I know it can be saved but I can't seem to locate the answers. I am also getting concerned that it is unable to charge the battery being in the condition it is in now so I am trying to conserve the battery on the tablet until it is absolutely needed. Thanks.
Click to expand...
Click to collapse
First of all - Welcome to xda
Your tab is soft bricked, something has gone wrong with your system files... Honestly it seems like you know enough to get it done, but are struggling a bit with the file formats. You are correct in saying that Odin won't use zip files, but you shouldn't have to convert anything to tar or download linux! If you extract the zip files, you should find a .tar or .tar.md5 file (inside the zip file) that Odin can use, put it in the PDA mode box, etc etc... If your downloads don't have the correct files inside them, try THIS thread.
Let me know if you get it sorted :good:

bob23bk said:
First of all - Welcome to xda
Your tab is soft bricked, something has gone wrong with your system files... Honestly it seems like you know enough to get it done, but are struggling a bit with the file formats. You are correct in saying that Odin won't use zip files, but you shouldn't have to convert anything to tar or download linux! If you extract the zip files, you should find a .tar or .tar.md5 file (inside the zip file) that Odin can use, put it in the PDA mode box, etc etc... If your downloads don't have the correct files inside them, try THIS thread.
Let me know if you get it sorted :good:
Click to expand...
Click to collapse
I had already tried the method and file in the forum you linked me to. It failed almost instantly. That's when I turned everything off and tossed it all to the back seat of my work truck before it got thrown at the windshield. I keep seeing people saying they have trwp or whatever. I don't even know what that is haven't researched that. Is it something i need as well?
I've never successfully rooted a Samsung device. I used to do this stuff a lot back with the droid x with Linux and everything was pretty simple. Does Samsung change their bootloader with each update like Motorola did then? I was wondering that when trying to install a firmware of a previous version that maybe that was the problem.
All I wanted root for was to just tweak some things and be happy. It has turned into a nightmare.

C,
hi,
the consistent/common thread of this problem is/seems to be taking the ota and trying unverified/gimmicky
root methods.
there are recoveries for the gt-p52xx in the tab 10.1 forum
the majority of samsung devices root as follows;
if a custom recovery exist, flash it.
then download recent or latest version of chainfire's supersu update zip, reboot to recovery
backup your rom first, then flash supersu, if everything goes well, once you have set up your stock rom with root in place
make a new backup.
samsung ota's are death incarnate, reject them.
goto the tab 10 forum and get busy ! you said it yourself, you're not a noob, you know the drill. :good:
m

moonbutt74 said:
C,
hi,
the consistent/common thread of this problem is/seems to be taking the ota and trying unverified/gimmicky
root methods.
there are recoveries for the gt-p52xx in the tab 10.1 forum
the majority of samsung devices root as follows;
if a custom recovery exist, flash it.
then download recent or latest version of chainfire's supersu update zip, reboot to recovery
backup your rom first, then flash supersu, if everything goes well, once you have set up your stock rom with root in place
make a new backup.
samsung ota's are death incarnate, reject them.
goto the tab 10 forum and get busy ! you said it yourself, you're not a noob, you know the drill. :good:
m
Click to expand...
Click to collapse
I have tried the recoveries in the forum and it failed seconds after starting.
I don't do this stuff regularly as I don't hardly have the time. I haven't done anything of this nature in years so I'm well out of the loop on things..

cameron72 said:
I have tried the recoveries in the forum and it failed seconds after starting.
I don't do this stuff regularly as I don't hardly have the time. I haven't done anything of this nature in years so I'm well out of the loop on things..
Click to expand...
Click to collapse
okay, hmm, when you say it fails, do you mean odin fails to flash and if so what is the reason/ouput ?
or do you mean that you are now in a recovery bootloop ?
note- though i go the full route of packing recovery.img's for odin flashing, the md5 checksum always seems to
come up as invalid, the working "remedy" is to remove the .md5 extension from the "odin-flashable-recovery".tar.md5 file
by renaming the file to "odin-flashable-recovery".tar
odin will no longer attempt the checksum verification but the recovery file will flash.
make sure you have samsung-usb-drivers for windows installed. on the main page of my devhost archive [link is in my signature]
you will find the tools you need. the possible problem is that the ota you installed may have overwritten your bootloader, for that i don't
have a reliable fix, so if anything make sure you also have the stock recovery ready to go as well as supersu update zip
already downloaded onto your device for rooting.
after you flash the custom recovery [with auto-restart in odin disabled] run the flash and wait for the res-ok message, give it another second or two then disconnect the tab and force reboot to recovery, home,vol-up and power, once in recovery make a full backup, then flash supersu zip and reboot, if you do go into recovery loop, force reboot to odin mode, home,vol-down and power, follow the on screen instruction, now reconnect your tab to pc and use odin to flash back stock recovery.
m

Okay guys I appreciate the help. I finally got it. I tried the method on Zachisimo's post on unbricking and finally got it installed.
After it installed, it left me with a bootloop and I was actually able to go into recovery mode this time and do a factory data reset and wipe cache then everything went well. I am a happy dude now.
Going to attempt rooting it again and does anyone have any suggestions on what ROM to install? I have never used any custom ROM's before so that is a new area for me. Feeling more confident knowing how to save it from the dead. :good::good::good:

cameron72 said:
Okay guys I appreciate the help. I finally got it. I tried the method on Zachisimo's post on unbricking and finally got it installed.
After it installed, it left me with a bootloop and I was actually able to go into recovery mode this time and do a factory data reset and wipe cache then everything went well. I am a happy dude now.
Going to attempt rooting it again and does anyone have any suggestions on what ROM to install? I have never used any custom ROM's before so that is a new area for me. Feeling more confident knowing how to save it from the dead. :good::good::good:
Click to expand...
Click to collapse
Hi,
Alright !'m glad you got it working, as to roms , all available roms currently are stock modifications , I use cag-rom, there's also pimp-droid
both kitkat.
m

moonbutt74 said:
Hi,
Alright !'m glad you got it working, as to roms , all available roms currently are stock modifications , I use cag-rom, there's also pimp-droid
both kitkat.
m
Click to expand...
Click to collapse
If you use it then thats what i shall try. First i gotta find a root, then I have seen many people recommend philz recovery, and then the rom?
question why does Restl3ss say wait 10minutes after installing a rom before doing anything?

cameron72 said:
If you use it then thats what i shall try. First i gotta find a root, then I have seen many people recommend philz recovery, and then the rom?
question why does Restl3ss say wait 10minutes after installing a rom before doing anything?
Click to expand...
Click to collapse
for root look up supersu update zip
ask Restl3ss :silly:
m

cameron72 said:
Okay guys I appreciate the help. I finally got it. I tried the method on Zachisimo's post on unbricking and finally got it installed.
After it installed, it left me with a bootloop and I was actually able to go into recovery mode this time and do a factory data reset and wipe cache then everything went well. I am a happy dude now.
Going to attempt rooting it again and does anyone have any suggestions on what ROM to install? I have never used any custom ROM's before so that is a new area for me. Feeling more confident knowing how to save it from the dead. :good::good::good:
Click to expand...
Click to collapse
Glad it worked out, recovering from brick does set you free from the stress induced by the disclaimers imo :silly: