Related
I'll give as much info as i can and will REWARD whoever can help me with this situation!
I have experience with different samsung phones rooting through odin and others never having much issues. This is first attempt with a tablet fyi.
Samsung tab 2 lte edition from at&t i497 5100
Attempted http://forum.xda-developers.com/showthread.php?t=1957165
root method through odin and everything was going alright until halfway through it said failed. I then rebooted into download and attempted this version http://forum.xda-developers.com/showthread.php?t=2101044
This method seemed to work as i was able to boot into recovery cwm and go through the options. I then ran the supersu zip and verified that the appdrawer had it in there. things looked ok i thought. so now i was ready to download a rom. Attempted the most current CM10 nightly through recovery.- it failed giving me the status 7 error. i then went to the only post about status 7 in the all things tab 2 thread and attempted to download mobile odin but when i loaded the app it said not compatible with my device.
I then attempted to download a stock rom and remove root from phone because sometime in this all i lost the ability to use wifi and my imei showed missing in the settings. no attempt at unrooting seems to work because of the cwm not allowing me to use roms. I attempted to recover the nandroid i made the minute i "rooted" and its giving me the md5 sum error as well.
Please help!!
circa_rider said:
I'll give as much info as i can and will REWARD whoever can help me with this situation!
I have experience with different samsung phones rooting through odin and others never having much issues. This is first attempt with a tablet fyi.
Samsung tab 2 lte edition from at&t 5100
Attempted http://forum.xda-developers.com/showthread.php?t=1957165
root method through odin and everything was going alright until halfway through it said failed. I then rebooted into download and attempted this version http://forum.xda-developers.com/showthread.php?t=2101044
This method seemed to work as i was able to boot into recovery cwm and go through the options. I then ran the supersu zip and verified that the appdrawer had it in there. things looked ok i thought. so now i was ready to download a rom. Attempted the most current CM10 nightly through recovery.- it failed giving me the status 7 error. i then went to the only post about status 7 in the all things tab 2 thread and attempted to download mobile odin but when i loaded the app it said not compatible with my device.
I then attempted to download a stock rom and remove root from phone because sometime in this all i lost the ability to use wifi and my imei showed missing in the settings. no attempt at unrooting seems to work because of the cwm not allowing me to use roms. I attempted to recover the nandroid i made the minute i "rooted" and its giving me the md5 sum error as well.
Please help!!
Click to expand...
Click to collapse
I'm worried for you, in that you have corrupted your efs folder - did you make an efs backup? as far as i'm aware, you can only recover your efs if you have backed it up. good luck.
If it helps I am an At&t store manager, and i do have access to a identical tab that is about to be sent back from a return. I am scared though of corrupting that one and then being in a worse situation. If i knew i could create a backup that could be moved to my personal one i would do it. is that possible? I'm not familiar with an efs backup but am researching it to check now.
squ89r97 said:
I'm worried for you, in that you have corrupted your efs folder - did you make an efs backup? as far as i'm aware, you can only recover your efs if you have backed it up. good luck.
Click to expand...
Click to collapse
circa_rider said:
If it helps I am an At&t store manager, and i do have access to a identical tab that is about to be sent back from a return. I am scared though of corrupting that one and then being in a worse situation. If i knew i could create a backup that could be moved to my personal one i would do it. is that possible? I'm not familiar with an efs backup but am researching it to check now.
Click to expand...
Click to collapse
I'm not sure it would, as a store manager you will know imei numbers are specific to each device!...you could swap the tabs over, but I don't condone that
Did you by chance rename the backup after making it? That has caused me problems in the past.
Sent from my SPH-L900 using Tapatalk 2
circa_rider said:
Samsung tab 2 lte edition from at&t 5100
Click to expand...
Click to collapse
Sorry I can't help, but is this the 7" tab? I have the 10.1" tab 2 and my model number is i497... LTE edition.
I totally understand what you mean now, i wasn't thinking a backup would switch over the imei i just thought it would contain whatever identifiers needed not realizing it would have the actual number in that.. I used total commander to look into the root file and there is a efs folder with all the separate folders "bluetooth, wifi, and other folders".
patrao_n said:
Did you by chance rename the backup after making it? That has caused me problems in the past.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
I did rename it when i was going through a fix for the md5 sum issue, i was going through adb and couldn't navigate to the folder so i did rename it... i cant imagine that the recovery would have an issue just because of that? i wouldn't be sure what to name it back to.
I wonder if Samsung has any option for me to send it in and get them to reboot the thing. This sucks!
circa_rider said:
I totally understand what you mean now, i wasn't thinking a backup would switch over the imei i just thought it would contain whatever identifiers needed not realizing it would have the actual number in that.. I used total commander to look into the root file and there is a efs folder with all the separate folders "bluetooth, wifi, and other folders".
Click to expand...
Click to collapse
There will be, but unforunately they are corrupt now. :crying:
I wonder if Samsung has any option for me to send it in and get them to reboot the thing. This sucks!
i'm pretty sure samsung has an option for you to send it in, but depending on what firmware your running/whether the flash counter has increased in download mode - your warranty would be void - or you may have to pay some $$$$ - they may even refuse. i don't know for sure though.
squ89r97 said:
There will be, but unforunately they are corrupt now. :crying:
I wonder if Samsung has any option for me to send it in and get them to reboot the thing. This sucks!
i'm pretty sure samsung has an option for you to send it in, but depending on what firmware your running/whether the flash counter has increased in download mode - your warranty would be void - or you may have to pay some $$$$ - they may even refuse. i don't know for sure though.
Click to expand...
Click to collapse
I appreciate you talking me through the different things, even if it doesn't fix my issue. I am probably going to call samsung to see but my flash counter is reset from triangle away and the firmware looks like it did before i ever rooted. but it says modified when i go to download mode so im sure they would know in a second that its my fault
circa_rider said:
I appreciate you talking me through the different things, even if it doesn't fix my issue. I am probably going to call samsung to see but my flash counter is reset from triangle away and the firmware looks like it did before i ever rooted. but it says modified when i go to download mode so im sure they would know in a second that its my fault
Click to expand...
Click to collapse
if the counter is at 0 it sounds like you still have root access, do you?
you could try flashing a stock firmware through odin , which ever came with the tab - 4.0.4??? get the firmware from sammobile.com - that may :fingers-crossed: get rid of the modified status.
---------- Post added at 05:20 PM ---------- Previous post was at 04:40 PM ----------
never thought to ask either - whats the *REWARD?
Try flash this jamaican firmware it works on at&t
http://www.hotfile.com/dl/189517896/ee3001a/I497UMAMA1_I497JDIAMA1_JDI.zip.html
mihaidenis said:
Try flash this jamaican firmware it works on at&t
http://www.hotfile.com/dl/189517896/ee3001a/I497UMAMA1_I497JDIAMA1_JDI.zip.html
Click to expand...
Click to collapse
You're missing the point! He has a corrupt imei number. He can flash that but still won't be able to get signal.
I had a simaler issue with my S3 (d2tmo) as well as many others. Qpst I believe is what I used to get the imei back. I had the links all save on the laptop but it died 3 moths back. (10 year old dell). http://forum.xda-developers.com/showthread.php?t=1801997 try that out see if it will help. I have some of the other stuff saved that I will upload to you. Search the issue on S3 (us variants) it could help.
Samsung Rocks!
Great news! Samsung had me send it in and they repaired it in less than 2 days of having it. their ticket email says this
Problem found: ESN corrupted
Solution: Replaced PBA
-- not sure what a pba is but they didn't charge me for the repair! I'm taking this as a gracious sign from above that i should leave it well enough alone and enjoy it the way it was made! I'll just stick to rooting my s3 and doing what im comfortable with. I appreciate all your words of help and advice to try and narrow down a solution.
First of all, you flashed some things not meant for your device. the CF-Autoroot method is designed for the Pxxx models, NOT the SGH/SCH models. Flashing this on your device flashed partitions it shouldn't have.
Second, the PBA is the mainboard. I bricked my tab a few weeks ago (typo in my updater script) and they replaced the PBA also. Samsung warranty is pretty great. Glad you got it fixed.
Always, ALWAYS, be sure you flash a ROM/recovery/etc designed for your specific device. The pxxx tabs and sgh/sch tabs are 100% different in hardware AND partition layout. If you flash a ROM for the Pxxx tab on a SGH/SCH tab, it will overwrite imei. Moderators REALLY need to suck it up and create separate forums for the lte tabs.
MrHyde03 said:
If you flash a ROM for the Pxxx tab on a SGH/SCH tab, it will overwrite imei. Moderators REALLY need to suck it up and create separate forums for the lte tabs.
Click to expand...
Click to collapse
Don't think this will happen, too small community and even no CM.
I think the verizon Tab is the Xperia Pro in the Xperia Arc Forum
Dexxmor said:
Don't think this will happen, too small community and even no CM.
I think the verizon Tab is the Xperia Pro in the Xperia Arc Forum
Click to expand...
Click to collapse
I know... very unlikely which is why I'm currently setting up my own forums to alleviate the issue :good:
get my tab 2 imei back to normal
Dexxmor said:
Don't think this will happen, too small community and even no CM.
I think the verizon Tab is the Xperia Pro in the Xperia Arc Forum
Click to expand...
Click to collapse
How I can get my tab 2 10.1 original imei back ? I lost my orignal imei and network not registered after my tab is root...please tell me how I can get it back, hope to have a solutions soon...
I have been notified of an update for my EK-GC120 (6ca5626c77cd.update_EK-GC120_GC120VRALL2_To_GC120VRAMC4_FWD-1.zip) is the file i pulled from the cache folder but it refuses to apply to my camera. Is there an alternate recovery available anywhere for this device? TWRP or CWM? I have posted the update here I am hoping it includes the remote viewfinder functionality that was originally missing from this version.
http://d-h.st/users/swjpilot/?fld_id=16995#files
Update: I had changed the GmsCore.apk file...luckily i had backed it up. After restoring the original file the update applied is applying....Hopefully Root will remain will post update as soon as it completes.
Update: SuperSU says it was able to restore Root Access whoohoo!
Last Update: This does finally bring the Remote Viewfinder capability to the stock camera app.
swjpilot said:
I have been notified of an update for my EK-GC120 (6ca5626c77cd.update_EK-GC120_GC120VRALL2_To_GC120VRAMC4_FWD-1.zip) is the file i pulled from the cache folder but it refuses to apply to my camera. Is there an alternate recovery available anywhere for this device? TWRP or CWM? I have posted the update here I am hoping it includes the remote viewfinder functionality that was originally missing from this version.
http://d-h.st/users/swjpilot/?fld_id=16995#files
Update: I had changed the GmsCore.apk file...luckily i had backed it up. After restoring the original file the update applied is applying....Hopefully Root will remain will post update as soon as it completes.
Update: SuperSU says it was able to restore Root Access whoohoo!
Last Update: This does finally bring the Remote Viewfinder capability to the stock camera app.
Click to expand...
Click to collapse
I give up. How did you root this device in the first place?
perlmane said:
I give up. How did you root this device in the first place?
Click to expand...
Click to collapse
ExynosAbuseAPK before the first update. You may be able to ODIN back to 4.1.1, run that tool then keep your root through the subsequent OTA's.
Where does one find 4.1.1
Sent from my SCH-I605 using XDA Premium HD app
perlmane said:
Where does one find 4.1.1
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I would try installing Kies and having it restore the firmware. It will most likely put you back on the original firmware but i don't know that for sure. Worst thing that could happen is a factory reset of your device and you stay on your current code level.
swjpilot said:
I would try installing Kies and having it restore the firmware. It will most likely put you back on the original firmware but i don't know that for sure. Worst thing that could happen is a factory reset of your device and you stay on your current code level.
Click to expand...
Click to collapse
VZW products do not support Kies firmware updates. 4.1.1 does not seem to be available anywhere for this device.
perlmane said:
VZW products do not support Kies firmware updates. 4.1.1 does not seem to be available anywhere for this device.
Click to expand...
Click to collapse
Well i saw this post as well not sure if you have been through it or not..... but this is the last thing i got for you. I have not been able to find the original firmware anywhere either myself.
http://forum.xda-developers.com/showthread.php?t=2086636
Sorry......
swjpilot said:
Well i saw this post as well not sure if you have been through it or not..... but this is the last thing i got for you. I have not been able to find the original firmware anywhere either myself.
http://forum.xda-developers.com/showthread.php?t=2086636
Sorry......
Click to expand...
Click to collapse
Since VZW does not support Kies firmware updates, I am afraid to try it. I will have to wait until someone finds the 4.1.1 release of this device and ODIN it.
Anyone still have the boot.img for the latest verizon? Even the full update will work to extract it. This is the only missing piece to extending the custom kernel to all variants.
perlmane said:
I give up. How did you root this device in the first place?
Click to expand...
Click to collapse
swjpilot said:
ExynosAbuseAPK before the first update. You may be able to ODIN back to 4.1.1, run that tool then keep your root through the subsequent OTA's.
Click to expand...
Click to collapse
If you are still around can you confirm you used the "Exynos" Abuse apk to root your Verizon GC120. The Samsung specs page for it aren't clear about whether it's an Exynos quad core using a qualcomm board or an entire qualcomm chipset/board. Thanks!
And if anyone Verizon has found a way to root the current Verizon version and/or the odin file for 4.1.1 please reply here or let me know! Thanks!
swjpilot said:
I have been notified of an update for my EK-GC120 (6ca5626c77cd.update_EK-GC120_GC120VRALL2_To_GC120VRAMC4_FWD-1.zip) is the file i pulled from the cache folder but it refuses to apply to my camera.
http://d-h.st/users/swjpilot/?fld_id=16995#files
Click to expand...
Click to collapse
That link is dead end. Can you please repost that firmware update?
Another thing I learned while I had my ATT galaxy tab 8.9 was that Samsung likes to use the same hardware in their South Korean version of their devices with cellular and in their US devices with cellular. It's almost certainly because of the LTE requirement. Wouldn't you know that such is the case with the Galaxy Camera. The South Korean version of the camera has a Qualcomm board just like the Verizon one. Maybe the firmware for it, which can be found on Sammobile at the link below, can be helpful.
http://www.sammobile.com/firmwares/1/?model=EK-KC120S&pcode=0
EDIT: To clarify more, the Korean version uses a Qualcomm 9215 baseband board with Exynos 4412 while the Verizon version (based on Samsung own specs page) uses a Qualcomm 9615 which has it's own applications processor.
CPU Z says the Verizon GC120 DOES use the Exynos 4412 (smdk4x12). It makes no mention of the Qualcomm board on Samsungs' own specs page. They don't make this easy...
Still need any Verizon build anyone has (original 4.1.1 or 4.1.2 update which should be found in /cache).
Newest JZO54K.GC120VRAMC4
Previous JZO54K.GC120VRALL2
The one in the op should then be the 4.1.2 update
twistedumbrella said:
Newest JZO54K.GC120VRAMC4
Previous JZO54K.GC120VRALL2
The one in the op should then be the 4.1.2 update
Click to expand...
Click to collapse
I know you think no one else could possibly know better than you but the link in the op leads to nothing.
Jiggity Janx said:
I know you think no one else could possibly know better than you but the link in the op leads to nothing.
Click to expand...
Click to collapse
E:V:A said that a few posts up. I dunno what your problem is, but the more specific the file name, the better chance of finding the right file. If this section were labelled "Jiggity Janx" and not "Galaxy Camera Android Development" I would be directing every post to you. It isn't, and I'm not.
Edit: Did you try editing the build.prop with the values for the old version and attempting to do a system update? I have not researched how FOTA determines eligibility, but if it is like any normal system app, it uses the system properties.
twistedumbrella said:
E:V:A said that a few posts up. I dunno what your problem is, but the more specific the file name, the better chance of finding the right file. If this section were labelled "Jiggity Janx" and not "Galaxy Camera Android Development" I would be directing every post to you. It isn't, and I'm not.
Click to expand...
Click to collapse
edited out...
You can still likely see what was written in your thread quote notification but it doesnt need to be hashed out here.
Jiggity Janx said:
My problem here starts and ends with you. You cant expect to come across the way you do belittleing or correcting everyone every chance you get and then wonder why someone responds that way to something that appears to be a comment directed at the very last thing stated in the post immediately before yours. You dont get to have it both ways and then act innocent and deflect when you are called out on it.
Click to expand...
Click to collapse
It isn't about feelings, its about development.
Did you try editing the build.prop with the values for the old version and attempting to do a system update? I have not researched how FOTA determines eligibility, but if it is like any normal system app, it uses the system properties.
twistedumbrella said:
It isn't about feelings, its about development.
Did you try editing the build.prop with the values for the old version and attempting to do a system update? I have not researched how FOTA determines eligibility, but if it is like any normal system app, it uses the system properties.
Click to expand...
Click to collapse
Github/Sourcforge - post technical information for development, no interaction or FEELINGS required
XDA - development FORUM that requires HUMAN interaction
Now....
I appreciate the robotic side of you not taking anything to heart and continuing to want to assist. Unfortunately I have to return the model I received as I immediately noticed it had the vzw demo app on it and that the screen wouldn't time out. That means it was a verizon floor model and is unusable as intended. I am returning that one for a full refund but already have another on the way that I have been guaranteed does not have that problem (for $25 less even).
So long story short I am only willing to mess with the files so much. I know one wrong move with the build.prop could cause it not to boot and without a way to restore am not willing to take that chance with one I have to return. I will be able to do more than pull files from the other one once I receive it (and have time).
Thank you again for assisting us all with development on this device.
Jiggity Janx said:
Github/Sourcforge - post technical information for development, no interaction or FEELINGS required
XDA - development FORUM that requires HUMAN interaction
Now....
I appreciate the robotic side of you not taking anything to heart and continuing to want to assist. Unfortunately I have to return the model I received as I immediately noticed it had the vzw demo app on it and that the screen wouldn't time out. That means it was a verizon floor model and is unusable as intended. I am returning that one for a full refund but already have another on the way that I have been guaranteed does not have that problem (for $25 less even).
So long story short I am only willing to mess with the files so much. I know one wrong move with the build.prop could cause it not to boot and without a way to restore am not willing to take that chance with one I have to return. I will be able to do more than pull files from the other one once I receive it (and have time).
Thank you again for assisting us all with development on this device.
Click to expand...
Click to collapse
Look at the number of developers who have left xda butt-hurt about some comment a nameless, faceless text blob made about them because of how they read it. The device suffers, the users suffer, and some kid is up in his room crying about a hobby gone wrong.
As for the rollback, it was only theory anyway so if there is any doubt about what to change its better to find an alternative. If you could get images of the partitions from stock condition, it is possible to build the install. At least that is all done off the device where it won't corrupt anything. You could root, get the system, data, cache, and boot then merge those with the Korean release to fill in the missing parts. To the best of my knowledge, the bootloader and such are not region specific. That should be verified first, though, because you can't go back later.
ON: Galaxy S3 4.4.2 Verizon(d2vzw) -->OK, I know you all may think I didn't read the other debrick threads, your wrong. I made this new thread because i HAVE tried endlessy every method of debrick on this forum and the internet, and no success. I was messing around with safestrap and decided to try and flash a rom called flashingdroid: for some reason. So i did as usual, boot into recovery(safestrap 3.75) and wipe current os and flash the new one. So i wiped my stock rom(after making a backup) and installed/flashed the new one(flashingdroid) and after seemingly a successful flash, i pressed reboot. Then it went downhill. One second after i pressed reboot, the screen flashed quickly, then shutoff, for good. I couldn't boot it or get into recovery or odin or ANYTHING. I tried the microsd method of debricking with minimal success. It will only give me one vibration, then black scree with that method. Nothing else has worked. I know this was a noob mistake somehow, but does anyone know any special tricks or something? Will a good jig maybe work? I have doubt verizon or samsung will accept it back(it was well rooted!). Please anything/anybody help! I really don't want to buy a new phone or jtag it. Thanks!:crying:
You may have read the debrick threads, but what you should have done from the beginning was read and pay attention to which forum you were in. You flashed a ROM for the International version of the S3 onto your Verizon S3. You almost certainly turned your phone into a shiny paper weight. JTAG may be your only hope. If you don't have one, check out mobiletechvideos.com. I'm not familiar enough with safestrap to know if that may have actually saved you since it is not a traditional recovery and I don't know if it touches all the partitions. In the future, research, research, and research, and pay very close attention to exactly what you are flashing onto your phone. For the Verizon S3, you should only flash ROMs from this sub-forum. And when using safestrap, you are restricted to only flashing ROMs with the same build number as what your phone is currently on in a stock condition.
Ok...Thanks
landshark68 said:
You may have read the debrick threads, but what you should have done from the beginning was read and pay attention to which forum you were in. You flashed a ROM for the International version of the S3 onto your Verizon S3. You almost certainly turned your phone into a shiny paper weight. JTAG may be your only hope. If you don't have one, check out mobiletechvideos.com. I'm not familiar enough with safestrap to know if that may have actually saved you since it is not a traditional recovery and I don't know if it touches all the partitions. In the future, research, research, and research, and pay very close attention to exactly what you are flashing onto your phone. For the Verizon S3, you should only flash ROMs from this sub-forum. And when using safestrap, you are restricted to only flashing ROMs with the same build number as what your phone is currently on in a stock condition.
Click to expand...
Click to collapse
Im kinda tired of my so confined locked bootloader and phone model anyways. Im going to purchase a $20 JTAG service off ebay, hope that works.
Root Wizard said:
Im kinda tired of my so confined locked bootloader and phone model anyways. Im going to purchase a $20 JTAG service off ebay, hope that works.
Click to expand...
Click to collapse
I'd be very careful with eBay, they tend to be junk. I've been an eBay member over 10 years and ran into a lot of it
Sent from my Nexus 5
Try MicroSD 16GB (2GB not work)
Confused About What's Possible for Modding a Stock Verizon S3
Can someone please steer me in the right direction? I have a Verizon Galaxy S3 running 4.4.2 stock. I recently rooted my phone, but I realize I am very limited as to any mods I can make due to the locked bootloader. Am I able to modify my OS in some way at all (Safestrap) to make my phone run better, or am I just too late in going about this? I've read so much on this subject, but the more I read, it seems the more confused I get. I want to be careful not to brick my phone and would love to see some precise directions on what I could do. Thanks a million for any help at all!
straykat said:
Can someone please steer me in the right direction? I have a Verizon Galaxy S3 running 4.4.2 stock. I recently rooted my phone, but I realize I am very limited as to any mods I can make due to the locked bootloader. Am I able to modify my OS in some way at all (Safestrap) to make my phone run better, or am I just too late in going about this? I've read so much on this subject, but the more I read, it seems the more confused I get. I want to be careful not to brick my phone and would love to see some precise directions on what I could do. Thanks a million for any help at all!
Click to expand...
Click to collapse
You should be able to install xposed but as far as mods your very limited to what you can do with it
Sent from my Nexus 5
ShapesBlue said:
You should be able to install xposed but as far as mods your very limited to what you can do with it
Sent from my Nexus 5
Click to expand...
Click to collapse
Hey, thanks a lot for that! As much as I've read, I've never heard of xposed. I'll research it and see what it takes and what it will do for my phone. If it helps at all, which I'm sure it will, that would be great. Thanks again for your reply!
straykat said:
Hey, thanks a lot for that! As much as I've read, I've never heard of xposed. I'll research it and see what it takes and what it will do for my phone. If it helps at all, which I'm sure it will, that would be great. Thanks again for your reply!
Click to expand...
Click to collapse
Your very welcome. That's what xda is all about. Helping others
Sent from my Nexus 5
XDA Forum - the best place for learning...
ShapesBlue said:
Your very welcome. That's what xda is all about. Helping others
Sent from my Nexus 5
Click to expand...
Click to collapse
ShapesBlue-
It's hard to compare this forum with the others. I believe the people here are the most knowledgeable and, like you, very helpful. Funny enough, or not, I posed a related question on another site (initials AC), and it took over 150 views and a week later before anybody offered a reply. Anyway, I can see there is lots of information on this forum about xposed, so now I'll go and learn as much as I can about it. Thanks again for your help!
Btw, here's a link for others like me who are clueless about xposed: http://forum.xda-developers.com/showthread.php?t=2299428
straykat said:
ShapesBlue-
It's hard to compare this forum with the others. I believe the people here are the most knowledgeable and, like you, very helpful. Funny enough, or not, I posed a related question on another site (initials AC), and it took over 150 views and a week later before anybody offered a reply. Anyway, I can see there is lots of information on this forum about xposed, so now I'll go and learn as much as I can about it. Thanks again for your help!
Btw, here's a link for others like me who are clueless about xposed: http://forum.xda-developers.com/showthread.php?t=2299428
Click to expand...
Click to collapse
I've been around the web going on nearly 20 years and I'd have to agree some are more helpful than others. I find xda to be a great resource for anything android or windows phone related. And yes I agree some are a lot more helpful than others. The guys and gals still lurking around the VZW S3 forums have been here since the beginning for this phone and even though mine is no longer active I still use it daily, mostly for games but will probably never give it up. It was my first true (I'm comparing it to the HTC thunderbolt) android phone
Sent from my Nexus 5
Can't Believe What I - did! - - - Need Help Rebooting Phone
ShapesBlue said:
I've been around the web going on nearly 20 years and I'd have to agree some are more helpful than others. I find xda to be a great resource for anything android or windows phone related. And yes I agree some are a lot more helpful than others. The guys and gals still lurking around the VZW S3 forums have been here since the beginning for this phone and even though mine is no longer active I still use it daily, mostly for games but will probably never give it up. It was my first true (I'm comparing it to the HTC thunderbolt) android phone
Sent from my Nexus 5
Click to expand...
Click to collapse
ShapesBlue-
I seem to have gotten into big trouble - I hope there's a solution. I learned all about Xposed and installed it along with about a dozen modules. Everything was working great, except the torch/flashlight... [I wanted that! ] so, I saw a download for a module on this forum to fix the flashlight... http://forum.xda-developers.com/xposed/modules/xposed-flashlight-fixer-fix-devices-t2867267 . Well, since doing that, I think I realized that I should have left the flashlight alone! When I tried to reboot after adding the module to xposed, I ended up in what i believe is a boot loop. The Samsung screen comes on, and then it gets stuck on the red Verizon screen. I never dreamed that a module installation could cause this; and I guess I figured if it ever happened I could get into recovery mode and restore everthing. Btw, I had done a complete backup of my phone using Titanium on my sd card.
So, here's what I can/can't do now. I can push "down-volume-button" + home + power to get to screen where you can download a cusom OS - then pushing volume-up-button goes to screen that says "Downloading...Do not turn off target!! (Nothing seems to happen from here.) - - - I cannot enter recovery mode by pressing "volume-up" + home + power keys. When I do that I get the big yellow triangle with message - System software not authorized...go to nearest Verizon store. hmmmm.... So, am I hard bricked or soft bricked? Do I have a way out? Thanks very much for any help with this!
straykat said:
ShapesBlue-
I seem to have gotten into big trouble - I hope there's a solution. I learned all about Xposed and installed it along with about a dozen modules. Everything was working great, except the torch/flashlight... [I wanted that! ] so, I saw a download for a module on this forum to fix the flashlight... http://forum.xda-developers.com/xposed/modules/xposed-flashlight-fixer-fix-devices-t2867267 . Well, since doing that, I think I realized that I should have left the flashlight alone! When I tried to reboot after adding the module to xposed, I ended up in what i believe is a boot loop. The Samsung screen comes on, and then it gets stuck on the red Verizon screen. I never dreamed that a module installation could cause this; and I guess I figured if it ever happened I could get into recovery mode and restore everthing. Btw, I had done a complete backup of my phone using Titanium on my sd card.
So, here's what I can/can't do now. I can push "down-volume-button" + home + power to get to screen where you can download a cusom OS - then pushing volume-up-button goes to screen that says "Downloading...Do not turn off target!! (Nothing seems to happen from here.) - - - I cannot enter recovery mode by pressing "volume-up" + home + power keys. When I do that I get the big yellow triangle with message - System software not authorized...go to nearest Verizon store. hmmmm.... So, am I hard bricked or soft bricked? Do I have a way out? Thanks very much for any help with this!
Click to expand...
Click to collapse
No problem. Your soft bricked and it seems your on the latest firmware, correct me if I'm wrong
4.4.2 NE1? If so you can use Odin to flash back to stock 4.4.2 and you should be ok
Sent from my Nexus 5
ShapesBlue said:
No problem. Your soft bricked and it seems your on the latest firmware, correct me if I'm wrong
4.4.2 NE1? If so you can use Odin to flash back to stock 4.4.2 and you should be ok
Sent from my Nexus 5
Click to expand...
Click to collapse
ShapesBlue-
That's great news!!! Thanks!
I believe my phone was on 4.4.3. A file I used in my rooting process using Towelroot was I535VRUDNE1_I535VZWDNE1_VZW; I used Odin before for the root procedure, so the program of course is on my PC. Is there a thread around with instructions how to flash back to the stock firmware? Thanks again a million for getting back to me!
straykat said:
ShapesBlue-
That's great news!!! Thanks!
I believe my phone was on 4.4.3. A file I used in my rooting process using Towelroot was I535VRUDNE1_I535VZWDNE1_VZW; I used Odin before for the root procedure, so the program of course is on my PC. Is there a thread around with instructions how to flash back to the stock firmware? Thanks again a million for getting back to me!
Click to expand...
Click to collapse
But of course. Check this out which should get you what you need
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my Nexus 5
Try kies
straykat said:
ShapesBlue-
That's great news!!! Thanks!
I believe my phone was on 4.4.3. A file I used in my rooting process using Towelroot was I535VRUDNE1_I535VZWDNE1_VZW; I used Odin before for the root procedure, so the program of course is on my PC. Is there a thread around with instructions how to flash back to the stock firmware? Thanks again a million for getting back to me!
Click to expand...
Click to collapse
Instead of odin, you could try using samasung kies 3 and use its emergencey firmware recovery tool which dl's and intalls the correct, latest firmware on your device.
What you do:
Install kies 3 on your computer.
Boot to odin mode on your phone.
Click on tools in kies.
Select emergency firmware recovery option.
Follow on screen directions.
Hope I helped!
ShapesBlue said:
But of course. Check this out which should get you what you need
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my Nexus 5
Click to expand...
Click to collapse
Shapes Blue & Root Wizard,
Thanks much for your replies. Is it possible for me, having had 4.4.3 on phone, to go to 4.3 instead of 4.4.2? Seems some people think that's an advantage, but I'm not sure. If I did do that, could I still run xposed?
Btw, RW, I tried using your idea, but when I was attempting to do the emergency Firmware Recovery, it asked for a computer code...??? So, that method doesn't seem to be a good route for me, but thanks for the tip!
You guys don't know how happy I am to have you come to the rescue! I've been using an old iPhone 4 for calls, etc.... during the day which I don't like at all! I'll be real glad to get back to AndroidLand. Thanks again!!!
straykat said:
Shapes Blue & Root Wizard,
Thanks much for your replies. Is it possible for me, having had 4.4.3 on phone, to go to 4.3 instead of 4.4.2? Seems some people think that's an advantage, but I'm not sure. If I did do that, could I still run xposed?
Btw, RW, I tried using your idea, but when I was attempting to do the emergency Firmware Recovery, it asked for a computer code...??? So, that method doesn't seem to be a good route for me, but thanks for the tip!
You guys don't know how happy I am to have you come to the rescue! I've been using an old iPhone 4 for calls, etc.... during the day which I don't like at all! I'll be real glad to get back to AndroidLand. Thanks again!!!
Click to expand...
Click to collapse
I'm 100% sure the last update on the VZW S3 was 4.4.2 NE1. As long as you can root the phone you should be able to run xposed without an issue
And no you cannot downgrade to anything other than what your currently on
Sent from my Nexus 5
---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------
Root Wizard said:
Instead of odin, you could try using samasung kies 3 and use its emergencey firmware recovery tool which dl's and intalls the correct, latest firmware on your device.
What you do:
Install kies 3 on your computer.
Boot to odin mode on your phone.
Click on tools in kies.
Select emergency firmware recovery option.
Follow on screen directions.
Hope I helped!
Click to expand...
Click to collapse
Kies won't always work as it should
Sent from my Nexus 5
Still Not Up & Running...
ShapesBlue-
Believe-it-or-not, I still haven't been able to get my s3 back up & running. When I open Odin3 v 3.09 and try to flash the firmware 1534VRUDNE1 . . . . .tar.md5 , it doesn't successfully load to the s3. I've attached a screenshot showing the Odin screen. It show "All threads completed. (succeed 0 failed 1) - btw, when I click on the firmware file within Odin, nothing appears in the box to the right of the AP field; is that correct?
Thanks for any guidance you can provide.
straykat said:
ShapesBlue-
Believe-it-or-not, I still haven't been able to get my s3 back up & running. When I open Odin3 v 3.09 and try to flash the firmware 1534VRUDNE1 . . . . .tar.md5 , it doesn't successfully load to the s3. I've attached a screenshot showing the Odin screen. It show "All threads completed. (succeed 0 failed 1) - btw, when I click on the firmware file within Odin, nothing appears in the box to the right of the AP field; is that correct?
Thanks for any guidance you can provide.
Click to expand...
Click to collapse
I can't open it. It's in the newest word format docx. I personally haven't had to do this myself and it's been awhile since I've used Odin. Damn MS having to have all files in there own format
Edit: trying to download docs by Google and seeing if it opens
Sent from my Nexus 5
---------- Post added at 08:48 PM ---------- Previous post was at 08:40 PM ----------
straykat said:
ShapesBlue-
Believe-it-or-not, I still haven't been able to get my s3 back up & running. When I open Odin3 v 3.09 and try to flash the firmware 1534VRUDNE1 . . . . .tar.md5 , it doesn't successfully load to the s3. I've attached a screenshot showing the Odin screen. It show "All threads completed. (succeed 0 failed 1) - btw, when I click on the firmware file within Odin, nothing appears in the box to the right of the AP field; is that correct?
Thanks for any guidance you can provide.
Click to expand...
Click to collapse
Can you get into recovery?
I was able to open it once I downloaded docs by google. It's been so long since I used it though. I can't recall off hand how to use it to be honest
Sent from my Nexus 5
My TAB 2 7.0 was not rooted and was in the bootloop all of a sudden. The issue is when it reboots, it lets me enter lock screen password and when I try to use something - It reboots. I tried to do the Clear cache partition and Factory Reset from android boot menu (power + volume up button) which says that DATA WIPE COMPLETE but when I reboot the tab nothing changes, not even the WIFI connections and their passwords. The WiFi remains on and connected to my router.
I deleted those connection from Settings but again it reboots and all deleted wifi connections (which were successfully deleted) are back with their passwords.
I also tried RESET DEVICE from settings, it asked me for my password but when i entered it and tapped on reset my device option - BOOM! it reboots again without resetting.
I searched a lot on net and tried ODIN option with proper firmware but of no use. And most importantly, I did visit authorized service centre before doing any of these, they returned it after trying couple of time to flash it and asked me to change the motherboard(Which would cost me about the price of good android phone - $120).
Can anybody please suggest me any other option than changing the motherboard (which is way much higher than my budget). The option you suggest may be hardware repair or anything else, I may not be able to get it done myself if it is hardware thing but atleast it will help to search the repair option by precisely telling the guy (technician) - what to do?
I have posted this after i saw mentions online about this forum and experts here, I hope you guys help me out as this TABLET is of great use to me.
:crying:
notsogeeky said:
My TAB 2 7.0 was not rooted and was in the bootloop all of a sudden. The issue is when it reboots, it lets me enter lock screen password and when I try to use something - It reboots. I tried to do the Clear cache partition and Factory Reset from android boot menu (power + volume up button) which says that DATA WIPE COMPLETE but when I reboot the tab nothing changes, not even the WIFI connections and their passwords. The WiFi remains on and connected to my router.
I deleted those connection from Settings but again it reboots and all deleted wifi connections (which were successfully deleted) are back with their passwords.
I also tried RESET DEVICE from settings, it asked me for my password but when i entered it and tapped on reset my device option - BOOM! it reboots again without resetting.
I searched a lot on net and tried ODIN option with proper firmware but of no use. And most importantly, I did visit authorized service centre before doing any of these, they returned it after trying couple of time to flash it and asked me to change the motherboard(Which would cost me about the price of good android phone - $120).
Can anybody please suggest me any other option than changing the motherboard (which is way much higher than my budget). The option you suggest may be hardware repair or anything else, I may not be able to get it done myself if it is hardware thing but atleast it will help to search the repair option by precisely telling the guy (technician) - what to do?
I have posted this after i saw mentions online about this forum and experts here, I hope you guys help me out as this TABLET is of great use to me.
:crying:
Click to expand...
Click to collapse
I never encountered a problem like this before but 2 years screwing with my tab (well bootlooping it with myself) I would suggest rooting it via Odin and Flash TWRP (CWM works too but I prefer TWRP) through odin as well.
After that find a custom ROM, preferably a stable build since you'll be using it for daily use and flash it using TWRP. I would suggest downloading SlimKat or Cyanogen Mod 13 and GAPPS.
You can find a lot of guides (some are step by step) about rooting it through Odin, and flashing TWRP on your tab.
As well as custom ROMS and how to flash it.
Tell me how it goes dude. Goodluck
Edit:
Hmm before flashing custom ROMs, when you try to flash a firmware. Did you make sure that you're using a correct driver for your PC? Samsung Kies does the job but make sure to close Samsung Kies in order to avoid conflicts with Odin. Make sure also to switch your tab to Download Mode when you flash with Odin.
Factory reset but asif nothing happened? I'm sorry but your tab has the dreaded eMMc bug. Only an emmc replacement or a new motherboard can fix it. Sorry.
Sent from my espresso3g using XDA Labs
DeepBricked said:
I never encountered a problem like this before but 2 years screwing with my tab (well bootlooping it with myself) I would suggest rooting it via Odin and Flash TWRP (CWM works too but I prefer TWRP) through odin as well.
After that find a custom ROM, preferably a stable build since you'll be using it for daily use and flash it using TWRP. I would suggest downloading SlimKat or Cyanogen Mod 13 and GAPPS.
You can find a lot of guides (some are step by step) about rooting it through Odin, and flashing TWRP on your tab.
As well as custom ROMS and how to flash it.
Tell me how it goes dude. Goodluck
Edit:
Hmm before flashing custom ROMs, when you try to flash a firmware. Did you make sure that you're using a correct driver for your PC? Samsung Kies does the job but make sure to close Samsung Kies in order to avoid conflicts with Odin. Make sure also to switch your tab to Download Mode when you flash with Odin.
Click to expand...
Click to collapse
Dude, firmware flashing was already tried by the technician at the authorised service center, even he couldnt flash it. I tried flashing as you said. But when i went through all the step by step tutorials on flashing or rooting through odin, they all wanted me to turn on the developers options in settings which I can't. Even if i manage to do that, it will just reverse right away after reboot.
The TWRP thing and rooting through odin that you told me are the options left with me. But I am not familiar with all those things so It would be great if you can share any link about the step by step method.
Lightracer said:
Factory reset but asif nothing happened? I'm sorry but your tab has the dreaded eMMc bug. Only an emmc replacement or a new motherboard can fix it. Sorry.
Sent from my espresso3g using XDA Labs
Click to expand...
Click to collapse
New motherboard is way beyond my budget, so I am left with only one option i.e. eMMC replacement. Is eMMC readily available in the market, if yes then is there any trusted brand or something like that.
notsogeeky said:
New motherboard is way beyond my budget, so I am left with only one option i.e. eMMC replacement. Is eMMC readily available in the market, if yes then is there any trusted brand or something like that.
Click to expand...
Click to collapse
Unfortunately, I am not familiar with eMMc replacement although @Android-Andi does have a friend in Austria who can replace/upgrade it for you according to one of his posts.
Although if you ask me, you're better off buying another more recent tablet.
Sent from my espresso3g using XDA Labs
Lightracer said:
Unfortunately, I am not familiar with eMMc replacement although @Android-Andi does have a friend in Austria who can replace/upgrade it for you according to one of his posts.
Although if you ask me, you're better off buying another more recent tablet.
Sent from my espresso3g using XDA Labs
Click to expand...
Click to collapse
Thanks man. At least now I know what the issue is and what may be the best solution. I am from India so will have to search someone who replaces eMMC here.
It's only 11 screws & 25 bucks (USA) for a motherboard
http://www.ebay.com/itm/like/131488094589
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
Device-State:Recovery/Bootloader
Ellipsis 8
QTAQZ3
Vendor:Verizon Wireless
Build:KTO49
4.2KitKat
samson716 said:
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
?
Click to expand...
Click to collapse
You want help with a device but you don't tell us any kind of information about your device, how smart was that? What you need and how to do it can depend on what device model number you have.
Sent from my SM-S903VL using Tapatalk
SORRY
Droidriven said:
You want help with a device but you don't tell us any kind of information about your device, how smart was that? What you need and how to do it can depend on what device model number you have.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3/4.2Jellybean/KTO49
samson716 said:
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3
4.2Kitkat
KTO49
Thanks!
Click to expand...
Click to collapse
samson716 said:
samson716 said:
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3
4.2Kitkat
KTO49
Thanks!
Click to expand...
Click to collapse
are you using stock recovery or a custom recovery?
Click to expand...
Click to collapse
ayu321 said:
samson716 said:
are you using stock recovery or a custom recovery?
Click to expand...
Click to collapse
Stock
Click to expand...
Click to collapse
samson716 said:
ayu321 said:
Stock
Click to expand...
Click to collapse
Can you please tell me that what caused this problem ? what were you doing with the device? flashing roms ?
Click to expand...
Click to collapse
ayu321 said:
samson716 said:
Can you please tell me that what caused this problem ? what were you doing with the device? flashing roms ?
Click to expand...
Click to collapse
No I was literally doing nothing I was actually flashing my Samsung Device at that moment. From what I remember it occurred when I noticed at update to marshmallow updated then rebooted it. Ever since its been in this bootloop! Im not trying to root it put a custom rom on it just want it to function nothing special.
Click to expand...
Click to collapse
samson716 said:
ayu321 said:
No I was literally doing nothing I was actually flashing my Samsung Device at that moment. From what I remember it occurred when I noticed at update to marshmallow updated then rebooted it. Ever since its been in this bootloop! Im not trying to root it put a custom rom on it just want it to function nothing special.
Click to expand...
Click to collapse
You have soft bricked your phone . The only way to fix it is it flash its stock rom. If you are new to this stuff I would suggest you to read this article carefully and if you have any doubts , ask me.
https://www.maketecheasier.com/android-root-custom-recovery-and-roms/
Click to expand...
Click to collapse
samson716 said:
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
Device-State:Recovery/Bootloader
Ellipsis 8
QTAQZ3
Vendor:Verizon Wireless
Build:KTO49
4.2KitKat
Click to expand...
Click to collapse
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a device exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
ayu321 said:
samson716 said:
You have soft bricked your phone . The only way to fix it is it flash its stock rom. If you are new to this stuff I would suggest you to read this article carefully and if you have any doubts , ask me.
https://www.maketecheasier.com/android-root-custom-recovery-and-roms/
Click to expand...
Click to collapse
Okay not sure which Flash tool to use nor get my stock rom I dread to say but i dont think there is one available. Its a generic tablet its made by Quanta. Not sure how to put it in a download mode either I assume ADB is the only way to transfer any files.
Click to expand...
Click to collapse
Your device probably uses SPFlashtool or fastboot.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a deuce exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Its pretty easy to fix a soft bricked device , even if stock rom isnt available , any rom compatible with his device can fix the issue .
ayu321 said:
Its pretty easy to fix a soft bricked device , even if stock rom isnt available , any rom compatible with his device can fix the issue .
Click to expand...
Click to collapse
To be compatible, the ROM typically has to be ported and that usually requires the stock firmware or stock source from the device that the ROM is being ported over to. 99% of the time you can't just flash a ROM from a different model number, even if the CPU is the same, there's quite a bit more to it than that. The android operating system is built for the specific hardware it is installed on, the two devices would have to be exactly the same and have the exact same components, any differences in hardware make he firmwares incompatible.
For this particular device, I doubt the stock firmware or stock source code area available, even if it were, porting another ROM wouldn't be necessary because if it were available it could just be flashed with that instead of porting a ROM.
About the only time a ROM from a different model number can be used without any porting or edits being made is when the devices are exactly the same device just rebranded with a different "name".
But thanks for trying to tell me something that you thought I didn't know, now it seems I've told you something that you didn't know.
Sent from my SM-S903VL using Tapatalk
samson716 said:
ayu321 said:
Okay not sure which Flash tool to use nor get my stock rom I dread to say but i dont think there is one available. Its a generic tablet its made by Quanta. Not sure how to put it in a download mode either I assume ADB is the only way to transfer any files.
Click to expand...
Click to collapse
1.Search for your tablet's root package , download it and move it to your tablet's sd card. Then enter your recovery mode by pressing power button+ Home button+ Volume button at same time for 10sec. Once entered , go to option "apply update from sd card" and select the root package you downloaded. (CONGRATS YOU HAVE ROOTED YOUR PHONE!)
2.Search for your tablet's 'custom recovery' , download it and flash it through odin tool(pc) .
3.Final Step ! BASED ON THE RECOVERY YOU FLASHED THESE STEPS MAY DIFFER , SO REPLY ME IF YOU SUCCEED IN FLASHING CUSTOM RECOVERY
Click to expand...
Click to collapse
ayu321 said:
1.Search for your tablet's root package , download it and move it to your tablet's sd card. Then enter your recovery mode by pressing power button+ Home button+ Volume button at same time for 10sec. Once entered , go to option "apply update from sd card" and select the root package you downloaded. (CONGRATS YOU HAVE ROOTED YOUR PHONE!)
2.Search for your tablet's 'custom recovery' , download it and flash it through odin tool(pc) .
3.Final Step ! BASED ON THE RECOVERY YOU FLASHED THESE STEPS MAY DIFFER , SO REPLY ME IF YOU SUCCEED IN FLASHING CUSTOM RECOVERY
Click to expand...
Click to collapse
Odin is for Samsung devices, not other devices.
The device they are repairing is not a Samsung device. They have this device and a Samsung device. The issue on this device occurred while they were in the process of flashing their Samsung device.
I know you're trying to help but don't post anything unless you are absolutely certain that you know what you're talking about.
In this case, you didn't and that can easily lead to a hard bricked device because they followed your instruction.
Stick to answering questions about devices you personally have dealt with, don't go assuming that you understand someone else's device. They are all different, the methods, tricks and tools for one won't necessarily work on another.
You understand android somewhat but judging by your posts, you don't understand the differences in devices and methods. But you will after you've been here a while.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 10:39 PM ---------- Previous post was at 10:32 PM ----------
DO NOT USE ODIN ON YOUR DEVICE!!!
Odin is only for Samsung devices.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a device exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
thankyou so much for the fast responses much appreciated to take your time to explain. Okay i have a question what would be the course of detailed action to preform getting any and all missing .img's it may need. Also i know its a crazy question but would i be able to preform this in store with the displayed tablet that matches mine? How difficult is something like this, and is there any other methods at all I can try to boot past this bootloader. And now that i remember correctly from reading others this happened when I upgraded to 5.1 or 5.0 thank you everybody once again!
samson716 said:
thankyou so much for the fast responses much appreciated to take your time to explain. Okay i have a question what would be the course of detailed action to preform getting any and all missing .img's it may need. Also i know its a crazy question but would i be able to preform this in store with the displayed tablet that matches mine? How difficult is something like this, and is there any other methods at all I can try to boot past this bootloader. And now that i remember correctly from reading others this happened when I upgraded to 5.1 or 5.0 thank you everybody once again!
Click to expand...
Click to collapse
No, you wouldn't be able to get it from a tablet in the store, it's a rather involved process that requires connecting the device to PC, it also requires rooting the device and flashing a custom recovery, and that's all before you actually get to where you can pull the files. It'll take a couple of hours,or more to do it.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
No, you wouldn't be able to get it from a tablet in the store, it's a rather involved process that requires connecting the device to PC, it also requires rooting the device and flashing a custom recovery, and that's all before you actually get to where you can pull the files. It'll take a couple of hours,or more to do it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Is there absolutely anything i can try, just a long shot in the dark?
samson716 said:
Is there absolutely anything i can try, just a long shot in the dark?
Click to expand...
Click to collapse
The only other option is pretty risky. You can try a firmware from another device that has the same CPU and hardware as your device, you'd have to compare specs. It would have to have the same CPU, same screen resolution, same camera(front and rear), same amount of RAM, same amount of internal storage, same accelerometers, etc.. It has to have all the same components that yours has.
Sent from my SM-S903VL using Tapatalk