Database Develop

Semi brick. Need help

Basically I've screwed over my phone.
It WILL boot. However I can't get it to go into USB mode.
I'm on Android 2.3.5 and I have this rom installed. http://forum.xda-developers.com/showthread.php?t=1779290
When I try to flash from a backup, it fails flashing system and renders my phone a brick until I reinstall the above ROM
I've also tried going into download mode so I can use the official LG updater to flash it back completely stock. However I can't seem to get that working.
Any help is appreciated. Thanks.

DracoAzule said:
Basically I've screwed over my phone.
It WILL boot. However I can't get it to go into USB mode.
I'm on Android 2.3.5 and I have this rom installed. http://forum.xda-developers.com/showthread.php?t=1779290
When I try to flash from a backup, it fails flashing system and renders my phone a brick until I reinstall the above ROM
I've also tried going into download mode so I can use the official LG updater to flash it back completely stock. However I can't seem to get that working.
Any help is appreciated. Thanks.
Click to expand...
Click to collapse
First you are posting in the wrong section.
Second, what baseband do you have installed. I am running on a Froyo baseband and can't run thrillseeker due to the baseband requiring the GB baseband. You can probably return to stock by using this guide http://forum.xda-developers.com/showthread.php?t=1491870
From what I am reading, the LG Updater sometimes will fail but you just have to continue using it.
Good luck with your issue. I am planning to do the same to my nephews phone later today. If i can figure something out I will post back.

I think its V20P which is Gingerbread. I know when I last updated it I used the official updating tool and grabbed it from their server. But again I'm on Android 2.3.5 Gingerbread. Will those update.zip files work?
Sent from my LG-P925 using xda app-developers app

DracoAzule said:
I think its V20P which is Gingerbread. I know when I last updated it I used the official updating tool and grabbed it from their server. But again I'm on Android 2.3.5 Gingerbread. Will those update.zip files work?
Sent from my LG-P925 using xda app-developers app
Click to expand...
Click to collapse
Everything works except USB ?.....does the phone charge through USB and just doesn't give you the option to connect SD cards?
Sent from my LG-P925 using xda premium

Bdadd34 said:
Everything works except USB ?.....does the phone charge through USB and just doesn't give you the option to connect SD cards?
Sent from my LG-P925 using xda premium
Click to expand...
Click to collapse
Yea it charges but that's it.
Luckily I have SwiFTP installed on my phone so I can still transfer things back and fourth between my phone and PC over my home network via FTP. Just much, MUCH slower.
EDIT: I just realized why this was in the wrong section. I TOTALLY thought I was posting in the general forum. Sorry. *derp*

Bump

First thing uninstall LG PC drivers then reboot PC and reinstall them. Or try to connect to a different PC to make sure it is not PC related. If that doesn't work then try wiping caches and instsall a different kernel. If that doesn't work I would then try full data wipe and reinstall rom of choice. You might try different rom as once its fixed you can always flash back...hope this helps you.
Sent from my LG-P925 using xda premium

Well I believe I've figured out what the problem was.
You see the other day while I was charging the phone I accidentally knocked it off. The USB cable got caught on my alarm clock and caught the phone, so the phone was hanging by the USB cable.
Well today I looked at the connector on it and I noticed it was bent a little. So I bent it back up and heard a small *click*
I was afraid I had broke it completely inside. However when I plugged it in my computer recognized my phone and USB mode showed up.

Touch Screen not working after ICS update

Hello all,
I have a GTab 8.9 from AT&T. I performed the ICS upgrade last night using Kies and it seemed to load correctly with no errors however the touch screen does not work now. It boots up fine but I cannot do anything with the screen. Power and volume buttons seem to be working fine.
I was able to reboot the device by holding the power button in and then go into download mode and do a factory reset. That went with no errors but the touch screen still does not work.
So, next I thought I would use Odin and try to push the factory rom back to it however Odin never sees the device, (tried multiple usb ports and 2 different pc's Win7 32b and 64b) However if I go ahead and let the GTab boot on up Odin does see it at that point. I can also get to the internal sdcard via my computer.
I also tried to copy the 7300_cwmr files to the sdcard and rebooted back to download mode. I selected apply update from sdcard and went into each of the directories but the device does not see any files in the directories, just the directories themselves.
So.... at this point I'm at a loss what to try next and I'm hoping someone on this forum can give me a nudge in the right direction.
I did reinstall the usb driver
Odin sucessfully recognized this device in download mode 'before' the ICS upgdate, not after.
I am using the factory usb cable and I did try a second one.
I was running version 3.2 before the upgrade.
Not ever rooted
Kies recognizes the device as well, can kies be used to flash my device? (sorry if that's a stupid question)
Thanks ahead

Are you sure you're in download mode, not recovery, when you try Odin. If kies recognizes the device I can't believe Odin won't.
Is the stock rom file you're trying to flash a zip file or a .tar.md5? The recovery is looking for a zip file and that may be why you didn't see it in any folder. Odin uses the tar file.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Thanks for the reply.
Yes I am in download mode. As I mentioned, Odin was able to see my GT before I upgraded to ICS, but not after. At least not in DL mode. If I let the GT go ahead and boot up Odin recognizes it with the port showing up in it's normal amber color.
It boots up fine, the touch screen is not working though so I can't use the GT. Once it boots up I can see it in my computer and place files on on it.
Thanks

Have you tried fixing permissions when you're in recovery mode? Do you have a custom recovery installed our the stock recovery, and if custom which one?
Sent from my SGH-I727 using xda app-developers app

I apologize, I'm not sure what you mean by fixing permissions while in recovery mode. I do not see that option on the screen. Everything is factory on the GT. I have not installed a custom recovery. The only change to the device from stock was the ICS upgrade that I just performed via Kies.
Is there a way that I can recover the device back to 3.2 using either Kies or while in DL/recovery mode? When the device boots I can see it and add files via my computer. Can I place the stock rom that I have downloaded from sammobile on the devices sdcard and reboot into DL mode and do a restore from sdcard? Is there a different way to do this without Odin?
Odin... I am not sure why it is not recognizing it while in DL mode. Odin will recognize it after the device boots. Actually Odin recognizes it just after the "Samsung" logo displays... while the AT&T "Rethink Possible" startup video is playing Odin will see it at that point. Not before. Quite frustrating actually. (I have tried multiple pc's and usb ports)
Thanks again for the help and apologies if I am asking stupid questions.

With the device off, hold down the power and both volume keys. When you see the Samsung logo release the power key but continue to hold down the volume keys for 2 seconds then release them. That should get you into down load mode. It'll say something about pressing the volume up key to continue. Have Odin running and then plug on the usb cable. Have you done something like that?
Sent from my SGH-I727 using xda app-developers app

ok... so I found an old "XP" laptop here at my office and downloaded the usb driver and Odin again and wnet into DL mode and for whatever reason Odin sees it on the XP machine. (whatever) grrr
Anyway... I downloaded and tried pushing both of the roms I found on sammobile.com for AT&T ( i957UCKJ7 and i957UCLK4) to my GT8.9, both times they completed successfully and when rebooting the touch screen would not work.
Is the rom still available for 3.2? Can I revert back to what came with it when it was originally released?
Thanks again for the assistance.

It sounds like you have a bigger problem than putting the stock Rom on it is going to fix. If you're still under warranty I'd take it in.
Sent from my SGH-I727 using xda app-developers app

Yeah I called them up and can toss it back at them, which I will do if I cant find an original factory rom to try and push to it.
I'm still searching for one though I have not been able to find one yet. Can anyone point me to a factory rom for this device?
I'd like to try and flash it back to stock before I send it back to them (if possible) as the touch screen was working just fine before I pushed out the update via kies the other day. Once the update finished and it rebooted, the touch screen did not work after that.
Thanks!

Go to sammobile.com for the stock roms. You'll have to sign-up but it's free.
Sent from my SGH-I727 using xda app-developers app

Yeah I've been to that site, that's where I got the 2 I mentioned above (i957UCKJ7 and i957UCLK4). I believe the UCLK4 file is ICS, correct? I'm not sure what version the UCKJ7 file is. I did try both. Those were the only 2 roms I could find there for the 8.9 ATT GT. I'll go back and look again. Maybe I missed it.
Thanks for your help

I'm sure those are the only two. The other one is honeycomb. They are the official Samsung roms. I think you've done what you can.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

This is the second reported occurrence of this happening. Weird
Sent from my SAMSUNG-SGH-I727 using xda premium

orlandoxpolice said:
This is the second reported occurrence of this happening. Weird
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Make that three ?? .. any resolution so far ?

orlandoxpolice said:
This is the second reported occurrence of this happening. Weird
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Yea, noticed that too. I used the rom from Sammy but didn't have an issue. I wonder if they got the wrong tab version.
OP, can you post what rom you flashed? And do you have an i957?
Sent from my SAMSUNG-SGH-I957
---------- Post added at 07:43 PM ---------- Previous post was at 07:23 PM ----------
wamaOnline said:
Make that three ?? .. any resolution so far ?
Click to expand...
Click to collapse
You're the second. Weird that a couple of you have had the same problem.
Sent from my SAMSUNG-SGH-I957

Regretfully my tab is not under warranty, and I don't know what to try next? Do you have any ideas

In a small way I'm glad to see that others are experiencing this also.
I wonder if anyone out there has a completely stock rom or knows where I can pick one up? I have tried the 2 over at sammobile and neither brought my touch screen back. I have searched and searched online and can't find anything.
I was reading on a different site while researching this issue and he said he reverted back to his original factory image and the touch screen functionality came back. I'd really just like to get my GT back up and running somehow until this ICS touch screen problem gets figured out.
Thanks ahead for any help.

Sammobile is the stock roms. Use the oldest one, honeycomb. The download is a zip file. To use Odin you'll need to extract the .tar.md5 file out of the zip. Use 7-zip to do that.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

Yeah I've tried both of the roms on sammobile. Didn't work.
Well, thanks very much for the help. I'll keep checking here through tomorrow to see if anyone else has a suggestion to try and if not I will just mail it back to Samsing on Monday. I hate doing that because I need it for a trip on the 15th. Grrr
Very frustrating.

EraserX33 said:
Yeah I've tried both of the roms on sammobile. Didn't work.
Well, thanks very much for the help. I'll keep checking here through tomorrow to see if anyone else has a suggestion to try and if not I will just mail it back to Samsing on Monday. I hate doing that because I need it for a trip on the 15th. Grrr
Very frustrating.
Click to expand...
Click to collapse
Any updates ? A question, did you try to use a non ATT card ?
Sent from my A500 using xda app-developers app
---------- Post added at 01:50 AM ---------- Previous post was at 01:43 AM ----------
EraserX33 said:
Yeah I've tried both of the roms on sammobile. Didn't work.
Well, thanks very much for the help. I'll keep checking here through tomorrow to see if anyone else has a suggestion to try and if not I will just mail it back to Samsing on Monday. I hate doing that because I need it for a trip on the 15th. Grrr
Very frustrating.
Click to expand...
Click to collapse
One more thing , can you please tell us where did you get your tablet from ? In case it is a he issue from the seller
Sent from my A500 using xda app-developers app

[Q] Problem android 4.2.2 [slimrom] n7000-computer conection (all information inside)

So i have installed android 4.2.2 slimrom
Baseband version N7000XXLPT
Kernel version 3.0.31-CM-ga034655
Slim version Slim-4.2.2.build.6-OFFICIAL
Build number JDQ39E
The problem is from what i can see, my computer is not finding my phone, but after a few apks i saw that my phone doesn't recognise my computer too, strange thing, anyway i have another problem, this android is charging with like 3%/hour, i do not have any backups from an stock rom, so because of the connection error i am unable to flash a stock with odin.
P.S If somebody have a stock backup made for his/her phone with a stock (4.0.3/4.0.4/4.1.2) and want to make a good thing and share, i would be greatfull, just upload it somewhere and i will download it, after i will install the update i will do a factory reset so no aware about

http://forum.xda-developers.com/showthread.php?t=1424997

joey_oggie said:
http://forum.xda-developers.com/showthread.php?t=1424997
Click to expand...
Click to collapse
Thank you man but this is not helping me cause I have to use Odin to flash them

Update! Tried to downgrade to 4.2.1 using CWM no results same problems,
Try to flash android 4.1.2 using CWM, no results same problem, what i still can do?

Sorry, I might have missed the part about Odin not recognising it.. Anyway, are you sure you installed the correct Samsung drivers? Try another PC and install the drivers and give Odin another shot. Also, try using another USB cable, it might help.
Sent from my GT-N7000 using xda app-developers app

joey_oggie said:
Sorry, I might have missed the part about Odin not recognising it.. Anyway, are you sure you installed the correct Samsung drivers? Try another PC and install the drivers and give Odin another shot. Also, try using another USB cable, it might help.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Man I tried on 2 computers with Samsung drivers installed + kies , 3 different cables , no result even in download mode.

Well, I can't think of anything but a defective USB port.. I assume you tried cleaning it as well?
Sent from my GT-N7000 using xda app-developers app

joey_oggie said:
Well, I can't think of anything but a defective USB port.. I assume you tried cleaning it as well?
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
3 times, IFK what else to do,really, but I am concern because it may be a problem with the hardware cause I have a problem too with charging and I can't send it to warrant cause it has a costume rom

oliviancool said:
3 times, IFK what else to do,really, but I am concern because it may be a problem with the hardware cause I have a problem too with charging and I can't send it to warrant cause it has a costume rom
Click to expand...
Click to collapse
try charging battery outside of phone (like external charger). use mobile odin to flash stock rom.
edit: or just borrow if someone you know has same phone.

Used to have problem of odin not recognizing my phone. Then I switched to xp from windows 7 with same driver installed, no issue.
So could be driver issue if you're using windows 7.

oliviancool said:
3 times, IFK what else to do,really, but I am concern because it may be a problem with the hardware cause I have a problem too with charging and I can't send it to warrant cause it has a costume rom
Click to expand...
Click to collapse
treacherous_hawk said:
try charging battery outside of phone (like external charger). use mobile odin to flash stock rom.
edit: or just borrow if someone you know has same phone.
Click to expand...
Click to collapse
^that. Since you're already rooted, get Mobile Odin from the Play Store and try and flash the stock ROM with it.

OK everything went smooth I was able to flash a new and a stock ROM but my battery problem is still there in 4 hours turned off I have 32% battery, idk what to say about this

oliviancool said:
OK everything went smooth I was able to flash a new and a stock ROM but my battery problem is still there in 4 hours turned off I have 32% battery, idk what to say about this
Click to expand...
Click to collapse
Well, since you have a stock ROM now, I guess you could try and take the phone to the retailer (or service center) and have them check the USB port.. It could be a battery problem too. My phone was doing weird stuff when I was using an unbranded battery (it didn't want to recharge and it kept making connected/disconnected sound even though I was nowhere near the charger).
Sent from my GT-N7000 using xda app-developers app

Slim-n7000-4.3.build.1 battery charging problems
oliviancool said:
So i have installed android 4.2.2 slimrom
Baseband version N7000XXLPT
Kernel version 3.0.31-CM-ga034655
Slim version Slim-4.2.2.build.6-OFFICIAL
Build number JDQ39E
The problem is from what i can see, my computer is not finding my phone, but after a few apks i saw that my phone doesn't recognise my computer too, strange thing, anyway i have another problem, this android is charging with like 3%/hour, i do not have any backups from an stock rom, so because of the connection error i am unable to flash a stock with odin.
P.S If somebody have a stock backup made for his/her phone with a stock (4.0.3/4.0.4/4.1.2) and want to make a good thing and share, i would be greatfull, just upload it somewhere and i will download it, after i will install the update i will do a factory reset so no aware about
Click to expand...
Click to collapse
I had problems installing the Slim-n7000-4.3.build.1-OFFICIAL-874.
Installed from the 4.1.2 stock.
Once connected, the N7000 did not carry the battery.
Tested various cables and chargers, even doing full wipe again the problem continued.
Had tested the Slim-n7000-4.3.beta.4-WEEKLY-424 and this problem did not occur.
The only solution was charging the N7000 with it off and go back to stock rom.
I had no problems with the Slim-n7000-4.2.2.build.7-OFFICIAL, Slim-n7000-4.2.2.build.8-OFFICIAL.

Has anyone else gotten this while rooting?

Hey guys. I ran into some trouble trying to root my note 3 and got this message. Now the phone won't turn on our connect to kies to try to repair it. I have the Samsung drivers installed and I believe I followed the directions closely. Can any of you tell me how to get back to factory settings or all the way through the root process. I'm stuck at this screen for now. Any help would be awesome.
Sent from my Nexus 7 using xda app-developers

Try using the one click oding to get back to the stock firmware. Put the phone in download mode and flash the first step of the root procedure and then stop and make sure your phone will work in stock form first before you try rooting it again.

Quickvic30 said:
Try using the one click oding to get back to the stock firmware. Put the phone in download mode and flash the first step of the root procedure and then stop and make sure your phone will work in stock form first before you try rooting it again.
Click to expand...
Click to collapse
Instead of Pass in a green box, I get Failed in a red box and the progress bar on the phone stops

That's not good, maybe try a new download. Which firmware are you flashing? MI1 or MI9?

That's actually what happened when I tried to root. It would sit forever and fail due to a timeout. What I did is after the failure..I left the phone in dl mode and connected and closed the odin..then relaunched odin and it worked the second time. That's my experience and your mileage may vary..

Same thing!
xavier6303 said:
That's actually what happened when I tried to root. It would sit forever and fail due to a timeout. What I did is after the failure..I left the phone in dl mode and connected and closed the odin..then relaunched odin and it worked the second time. That's my experience and your mileage may vary..
Click to expand...
Click to collapse
The exact same thing happened to me... I tried to install Kies 3 and add the drivers but to no avail. So from there on I just closed everything. Disconnected my note 3, reconnected it, and ran odin once more. It immeadiately passed and rooted my phone.

I have seen that in the past it is the sign of a brick you definitely have to Odin back to stock to fix that
Sent from my SAMSUNG-SM-N900A using xda app-developers app

Yes it happened to me too. I just figured it was my crappy computer so I continued to try and after the 4th try I was able to achieve root status. Like a previous commenter suggested, it's a timed out issue.

Yea. I must have tried a dozen times a dozen different ways and I was stuck. I just said eff it and got a new phone. Debating if I want to try again, but I don't feel like potentially going thru the same heart ache. Really the only reason I care to root this phone is to get rid of those damn bloat ware apps; especially My Magazine.
Sent from my SAMSUNG-SM-N900A using xda app-developers app

alpinesun said:
Instead of Pass in a green box, I get Failed in a red box and the progress bar on the phone stops
Click to expand...
Click to collapse
It was MI9
Sent from my SAMSUNG-SM-N900A using xda app-developers app

alpinesun said:
It was MI9
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Just went thru this on my Note 3 - chances are youre using a vm on a mac arent you?
Make sure you use a dedicated *windows* machine and not a vm (or at lest not a fusion VM) That was my issue, I havent tried parallels. I grabbed a dedicated win 7 machine and it works perfectly.
I was going to return it of that failed, which luckily it didnt.
Cheers

[Q] Help Re-Rooting after OTA Update

hey guys i tried searching for answers. but had no success. i have a note 3 that was rooted with kingo. AT&T automatically installed an OTA update and of course it un rooted my phone. i still get the custom boot screen as well as still have safestrap on my device. my question is how do i reroot my device? ive tried kingo again and it fails after rebootong the phone 5 or 6 times. im still running 4.3 build is JSS15J.N900AUCUBNB4
i know a little on some things but im not as technical as most of you. but any help would be greatly appreciated.

Survivor058 said:
hey guys i tried searching for answers. but had no success. i have a note 3 that was rooted with kingo. AT&T automatically installed an OTA update and of course it un rooted my phone. i still get the custom boot screen as well as still have safestrap on my device. my question is how do i reroot my device? ive tried kingo again and it fails after rebootong the phone 5 or 6 times. im still running 4.3 build is JSS15J.N900AUCUBNB4
i know a little on some things but im not as technical as most of you. but any help would be greatly appreciated.
Click to expand...
Click to collapse
What version of Kingo did you try? Use 1.1.5 or 1.1.8. People have had success with that. 1.1.8 worked for me. Just Google around and you will find the download on the net somewhere.

theorioles33 said:
What version of Kingo did you try? Use 1.1.5 or 1.1.8. People have had success with that. 1.1.8 worked for me. Just Google around and you will find the download on the net somewhere.
Click to expand...
Click to collapse
it was 1.2.0 ill try an older version

In case you have trouble finding a copy
https://mega.co.nz/#!AxdHUCCQ!86DzctSWlXK4VfbInPYBgC_4QYAM2wUR8cewrflAyk0

theorioles33 said:
In case you have trouble finding a copy
unfortunately that did not work. the root failed. that was version 1.1.5, last night i tried 1.1.8 failed and tried the latest 1.2.0 with no success. would you recommend something else? i did try theese root methods with the sd card inserted im not sure if that is a no no or not
Click to expand...
Click to collapse

I'm at a loss. I had my SD card in by the way. Maybe someone else will have some ideas.
Sent from my SAMSUNG-SM-N900A using Tapatalk

theorioles33 said:
I'm at a loss. I had my SD card in by the way. Maybe someone else will have some ideas.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
that sucks. factory reset? ill most likely still have the issue but maybe not. isnt there a way to completely wipe the phone from the boot screen? id rather not if i dont have to.

You can try a factory reset and then root. If not there is a thread in the general section to go back to stock. Works great. I used it.
Sent from my SAMSUNG-SM-N900A using Tapatalk

theorioles33 said:
You can try a factory reset and then root. If not there is a thread in the general section to go back to stock. Works great. I used it.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
but arent i technically back to stock? since i dont have root access? this is very confusing to me. if my carrier didnt push that update i wouldnt be in this boat

You are but we can't figure out why you can't root when others in your situation can. There is Kingo thread you can check out. Maybe you can find some answers there.
Sent from my SAMSUNG-SM-N900A using Tapatalk

anyone have any suggestions?? 139 views in less than an hour someone has got to know something lol

Survivor058 said:
anyone have any suggestions?? 139 views in less than an hour someone has got to know something lol
Click to expand...
Click to collapse
Factory Reset after the update to NB4, also go to recovery wipe cache, then try the 1.18, during the rooting process, look your phone screen, you need to click accept something twice,

I don't know how it all works terribly well but you said you still have Safestrap? Can you still install ROMs and can they have root?
Also, for when you eventually do get it working again. I recommend freezing the ATT updater. It can be awful when it eventually FORCES an update.
I got a free app called App Quarantine and froze "AT&T Software Update".

coolmingli said:
Factory Reset after the update to NB4, also go to recovery wipe cache, then try the 1.18, during the rooting process, look your phone screen, you need to click accept something twice,
Click to expand...
Click to collapse
ok yea this is all french to me. you want me to factory reset? im not sure what the NB4 is?. and i thing i know how to wipe the cache.

Gary3 said:
I don't know how it all works terribly well but you said you still have Safestrap? Can you still install ROMs and can they have root?
Also, for when you eventually do get it working again. I recommend freezing the ATT updater. It can be awful when it eventually FORCES an update.
I got a free app called App Quarantine and froze "AT&T Software Update".
Click to expand...
Click to collapse
safestrap is on my phone but it cant be removed and just says that the phone isnt properly rooted. so no i cannot install roms and i will make sure that once i resolve this ill freezr that app
sorry for the delay guys im back at this again. i do very much appreciate all who are trying to offer assistance

ok guys so ive wiped the cache. and have done the factory reset. kingo 1.1.5 and 1.1.8 both have failed...... what is going on here maybe someone can skype with me the steps to completely flash my phone to the day i got it i see the thread but im scared ****less to try it lol

You will just have to follow the restore to MJ5 thread. The instructions are simple and very easy to follow. Go slow and follow them to the T.
What they do not mention however is do not use a 3.0 USB port. Only 2.0 will work.
Just follow that.
It is literally impossible to brick this phone to the point of it being unrecoverable. There is a tutorial to restore from hard bricks without J-Tag.
Sent from my SM-N9005A using XDA Premium 4 mobile app

graydiggy said:
You will just have to follow the restore to MJ5 thread. The instructions are simple and very easy to follow. Go slow and follow them to the T.
What they do not mention however is do not use a 3.0 USB port. Only 2.0 will work.
Just follow that.
It is literally impossible to brick this phone to the point of it being unrecoverable. There is a tutorial to restore from hard bricks without J-Tag.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey graydiggy, I did the restore back to MJ5, but can't seem to get the last step for rooting to work. I tried every way with putting the rdlv on internal...unzipped and zipped. I even tried doing the same on the external sd as well. When I reboot supersu doesn't do anything. Any suggestion on how to get the last step to work?
Thanks in advance for your help.

chrispyutec said:
Hey graydiggy, I did the restore back to MJ5, but can't seem to get the last step for rooting to work. I tried every way with putting the rdlv on internal...unzipped and zipped. I even tried doing the same on the external sd as well. When I reboot supersu doesn't do anything. Any suggestion on how to get the last step to work?
Thanks in advance for your help.
Click to expand...
Click to collapse
It has to be unzipped and on the internal. You have to reboot a few times for it to activate. After the first reboot, let the phone sit for a few minutes and then reboot again. You should be good to go after that.
Sent from my SM-N9005A using XDA Premium 4 mobile app

graydiggy said:
It has to be unzipped and on the internal. You have to reboot a few times for it to activate. After the first reboot, let the phone sit for a few minutes and then reboot again. You should be good to go after that.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wow that did the trick!!! Thanks for holding my hand lol. I hit your thanks and I appreciate your help.