Related
I have searched around and can't seem to find a similar problem with a solution that I can understand. I used superoneclick to root my Verizon Galaxy 7" tablet. Everything seemed to go fine, but I really didn't have time to do anything "techy" with it. After a couple of weeks the tablet was acting kind of glitchy, nothing terrible, so I should have just left it alone. Instead I tried to do a complete factory reset. I tried several times, but it would never completely reset. My personalized wallpaper would show up, then all my apps were still there, settings didn't appear to change, etc.
I tried using Hemdall and loading new cache, param, system & zImage files. Now I am stuck in a boot loop. The machine will power up to the setup wizard, but every step generates multiple FCs until the setup wizard itself FC. Then it powers down and starts all over again. "Wipe data/factory reset" produces no change to the problem.
At this point I just want to restore my tablet to stock. No root, nothing fancy.
Can someone recommend a clear, easy to follow, current tutorial for me. I have downloaded Odin, but am uncertain which ROM I need to use. I really don't care which method you recommend as long as it is detailed (ie. written for a complete idiot to follow).
Thanks for any help.
2 things. Are you talking about a regular 7" galaxy or the 7.7? And this will most likely be moved because its a question and questions go in the general section.
mmcounts said:
i have searched around and can't seem to find a similar problem with a solution that i can understand. I used superoneclick to root my verizon galaxy 7" tablet. Everything seemed to go fine, but i really didn't have time to do anything "techy" with it. After a couple of weeks the tablet was acting kind of glitchy, nothing terrible, so i should have just left it alone. Instead i tried to do a complete factory reset. I tried several times, but it would never completely reset. My personalized wallpaper would show up, then all my apps were still there, settings didn't appear to change, etc.
I tried using hemdall and loading new cache, param, system & zimage files. Now i am stuck in a boot loop. The machine will power up to the setup wizard, but every step generates multiple fcs until the setup wizard itself fc. Then it powers down and starts all over again. "wipe data/factory reset" produces no change to the problem.
At this point i just want to restore my tablet to stock. No root, nothing fancy.
Can someone recommend a clear, easy to follow, current tutorial for me. I have downloaded odin, but am uncertain which rom i need to use. I really don't care which method you recommend as long as it is detailed (ie. Written for a complete idiot to follow).
Thanks for any help.
Click to expand...
Click to collapse
wrong section...please post in q&a section...........
Moving?
Should I repost in the Q&A section or will the post be moved automatically? I don't see an option to move the post myself.
Moved To General
Please Post all questions in the General section
7 or 7.7
Regarding the 7 or 7.7 question: I don't know which it is because I can't get it to boot up long enough to go into settings. According to the label it is an SCH-i800. It was purchased from Verizon in March 2011. I am pretty sure that it is a 7. Is there any way to tell just by looking at it?
Just determined it is a 7.0 per the Samsung webpage.
I guess I am in the wrong forum again. I am going to post in the General Galaxy Tablet forum.
Googled your model # you listed and stock rom and found this tutorial. Hope this helps you.
Thanks. I have tried that one a couple of times. It is close, but no cigar. I appreciate you thinking of me.
Some boot loop problems can be solved by letting the battery go flat overnight to get out of the loop, recharging then booting normally and doing a factory reset. If that doesn't work then re-flashing using Odin followed by a factory reset is worth trying.
You can get the firmware for flashing here:
http://www.samfirmware.com/
and a guide how to do the flashing here:
http://forum.xda-developers.com/showthread.php?t=1469635
I hope this helps and good luck
mmcounts said:
Regarding the 7 or 7.7 question: I don't know which it is because I can't get it to boot up long enough to go into settings. According to the label it is an SCH-i800. It was purchased from Verizon in March 2011. I am pretty sure that it is a 7. Is there any way to tell just by looking at it?
Just determined it is a 7.0 per the Samsung webpage.
I guess I am in the wrong forum again. I am going to post in the General Galaxy Tablet forum.
Click to expand...
Click to collapse
Verizon only sells the silver version of the 7.7, for which the model number is SCH-I815. If you have a plastic back, it's the 7, and an aluminum back is the 7.7. Of course, since posted your model I can tell you for sure it's the 7, so you might have better luck posting in the appropriate forum.
Depending on how SuperOneClick works for the tab (I have no idea personally), you might just be best taking it to Verizon and asking for a replacement. I find it unlikely that they'd be able to detect that it has been rooted if it's totally fubar'd.
big ol' noob here. i just flashed the Jelly-Bean_4.1.2_CM10-FLEX_v6supercharged_Aroma rom on my a500 which previously had lightspeed 4.8 on it. now when it boots it shows the android guy with gears for a second then just a blank black screen. the backlight is on so you can tell the tablet is still on. i can still get into recovery with no issues though("aman ra-iconia-3.17-ics" via "scrilax_CZ bootloader v8") i dont know what it could be though. installation of rom gave no errors. so please, I ask for assistance in resolving the issue. i was looking into (and learning about) fastboot fixes but i'm not sure if it applies to me nor have i tried it before. any help in fixing the darn thing would be much appreciated.
raotheconqueror said:
big ol' noob here. i just flashed the Jelly-Bean_4.1.2_CM10-FLEX_v6supercharged_Aroma rom on my a500 which previously had lightspeed 4.8 on it. now when it boots it shows the android guy with gears for a second then just a blank black screen. the backlight is on so you can tell the tablet is still on. i can still get into recovery with no issues though("aman ra-iconia-3.17-ics" via "scrilax_CZ bootloader v8") i dont know what it could be though. installation of rom gave no errors. so please, I ask for assistance in resolving the issue. i was looking into (and learning about) fastboot fixes but i'm not sure if it applies to me nor have i tried it before. any help in fixing the darn thing would be much appreciated.
Click to expand...
Click to collapse
You should change the title to "Stuck in APX Mode". Refine your search. I've never had the issue, however, I believe 1 or more partitions are messed up. Which means you will probably have to revert back using TimmyDeans V4 rollback tool at the worst.
Just a guess. But search the forum for those terms. You should be able to find some threads as I've seen several references to being stuck in APX mode.
One place you may want to post your issue, is Skrilax_CZ's bootloader thread. He may know some fastboot commands to wipe the data.
MD
cool. I'll do that. thanks man. I'm still learning the lingo so that sheds a bit of light for me and gives me some direction to start. thanks again.
raotheconqueror said:
cool. I'll do that. thanks man. I'm still learning the lingo so that sheds a bit of light for me and gives me some direction to start. thanks again.
Click to expand...
Click to collapse
Also remember, before you install a different rom, you must; in CWM
1. Wipe User Data/Factory Reset
2. Wipe Cache
3. Wipe Dalvik
Then go to Mounts and Storage and;
1. Format System
2. Format Flexrom
Then you can install the rom. If you haven't done this, you should try again.
MD
raotheconqueror said:
big ol' noob here. i just flashed the Jelly-Bean_4.1.2_CM10-FLEX_v6supercharged_Aroma rom on my a500 which previously had lightspeed 4.8 on it. now when it boots it shows the android guy with gears for a second then just a blank black screen. the backlight is on so you can tell the tablet is still on. i can still get into recovery with no issues though("aman ra-iconia-3.17-ics" via "scrilax_CZ bootloader v8") i dont know what it could be though. installation of rom gave no errors. so please, I ask for assistance in resolving the issue. i was looking into (and learning about) fastboot fixes but i'm not sure if it applies to me nor have i tried it before. any help in fixing the darn thing would be much appreciated.
Click to expand...
Click to collapse
Try the wipe commands suggested in post #4 and then reflash your JB ROM. A lot of time it helps with reflash the ROM after wipes.
thanks for the tips. i believe i've actually performed them like you guys told me but it seems i've made it worse. my ridiculousness is currently going on in this thread here
I'm having the same issue with this ROM. I'm using the same recovery you are.
if you have any progress let me know cause i'm still stuck in apx land...
final update
Back to stock HC 3.2.1 right now. my issue ended up being unable to format the /data directory causing all my newly flashed roms to not load properly. per JdgM3NT4L's guidance i used the tutorial and tools here which took me back to a working status. now my only problem lies with what delicious rom should i have next? an ICS or a jellybean? if any XDA tutorials or assistance help bring you tablet back, make sure to click those ":good: thanks" buttons guys.
This is my first post on here, but I've used these forums before to root my S3 and at one time my current S4. My problem is with MF3... I used
this post [http://forum.xda-developers.com/showthread.php?t=2387577] to root my phone once, but since I couldn't install TWRP or CWM, I thought I could downgrade the software version with Odin. Well, I was wrong, and I unrooted my phone in the process... Upon trying the same technique I mentioned earlier, it now says "permission denied" upon entering the first prompt <<cd /mnt/extSdCard>>
AND, I can't use Odin to factory reset. Using posts such as this [http://www.youtube.com/watch?v=hZTTTk7vbVM] doesn't seem to work either. When putting my phone into download mode, I pull up Odin, and select the file in the link (the software file .tar I think), it says it fails shortly after starting.
Really, I need help with two things:
1. Obtaining root access
2. Resetting phone to factory settings
I might not have to do a factory reset, but I've noticed my wifi will NOT enable since I unrooted and this is a big concern for me. I know that all my troubles are because the bootloader is locked (and I'm messing with stuff I don't fully understand...), which is why I'd like help obtaining root again in the final hope that Safestrap [http://forum.xda-developers.com/showthread.php?t=2448925] is the answer I'm looking for so I can use my favorite ROM, LiquidSmooth!
PLEASE help me any way you can! I've tried to provide as much information as I can think of, but I'm new to this stuff, so bear with me. I have no real experience in rooting and whatnot, but so far, I've followed directions by users of this forum, so I have faith that there's a solution to this mayhem. Thanks for any help you can provide! =)
Your first mistake was not reading about what you can and can not do while on mf3. Your second was trying to put a recovery on. And your third was trying to use Odin to down grade your firmware.
I'm surprised your not having issues booting. The only way right now to get your phone back to normal is to see if best buy will flash the mf3 firmware for you
Edit, read this http://forum.xda-developers.com/showthread.php?p=45359306
jd1639 said:
Your first mistake was not reading about what you can and can not do while on mf3. Your second was trying to put a recovery on. And your third was trying to use Odin to down grade your firmware.
I'm surprised your not having issues booting. The only way right now to get your phone back to normal is to see if best buy will flash the mf3 firmware for you
Edit, read this http://forum.xda-developers.com/showthread.php?p=45359306
Click to expand...
Click to collapse
I guess you're trying to be helpful, but your condescending tone isn't helping. I READ everything, I just don't UNDERSTAND everything... The second paragraph actually provided some help, so thanks for that. I was just hoping for something I could do myself to re obtain root so that I can try the Safestrap method I provided in my original post. I will post a reply to the root method post and see if anyone can help me there, since that's my main issue is not being able to get root access back. I don't have any problems booting though, only when I boot into recovery mode do I get a loop in which I just have to get to the Samsung warning screen and select "cancel (reboot phone)". Thanks for reading this and providing some direction.
jeremythetree said:
I guess you're trying to be helpful, but your condescending tone isn't helping. I READ everything, I just don't UNDERSTAND everything... The second paragraph actually provided some help, so thanks for that. I was just hoping for something I could do myself to re obtain root so that I can try the Safestrap method I provided in my original post. I will post a reply to the root method post and see if anyone can help me there, since that's my main issue is not being able to get root access back. I don't have any problems booting though, only when I boot into recovery mode do I get a loop in which I just have to get to the Samsung warning screen and select "cancel (reboot phone)". Thanks for reading this and providing some direction.
Click to expand...
Click to collapse
No, your main issue is that you don't understand what you are reading and you shouldn't be doing anything to your phone until you do. Dozens of people just like you pass through this forum everyday with similar issues because they didn't read or take the time to understand what it was that they did read. Someone takes the time to tell them to read and learn and they don't listen or think they don't have to. Then, they screw their phones up and come back here crying for help. So it's not a condescending tone, it's people getting tired of the same crap. You admitted that you didn't understand everything you read so why would you do anything to your phone before you do understand it? Can you not see the problem?
Ok, so I've been lost as far as for what is going wrong with my device, I managed to downgrade to VS99513b from the 14b update through kdz, and I got TWRP installed successfully, but when I install ANY custom rom made for my device it gives me graphical glitches on the Boot logo, and even when it boots into the actual OS itself?
I don't know what's causing this, I mean TWRP looks to be just fine while I'm flashing these ROMS I did make a back-up prior, but I'd prefer a custom firm if I can get it any suggestions, or any explanations would be nice
Ok, I found the issue
It had to do with the kernel somehow? I just successfully flashed a Rom, and repeated the steps with a previously "broken" rom the only change is my use of a Stock Kernel Mod zip which seems to fix the graphical bug entirely... why that is I don't know, but hell if it works IDC
ProtoPropski said:
Ok, I found the issue
It had to do with the kernel somehow? I just successfully flashed a Rom, and repeated the steps with a previously "broken" rom the only change is my use of a Stock Kernel Mod zip which seems to fix the graphical bug entirely... why that is I don't know, but hell if it works IDC
Click to expand...
Click to collapse
this has been discussed so many times is why no one is responding.
if you googled v20 and static screen you would have had 1000 posts discussing this or even when you read disclaimer on root.
The static is due to changing your aboot aka bootlaoder for the us996 unlock one, casuing ALL stock boot.img to display static. Fortunately months after root had been released the devs developed fixes to hide static and return a normalish boot experience. with the exception 1st boot takes a little longer.
The static can be overcome by locking screen after bootup, then covering the proximity sensor until 2nd screen falls asleep then unlock and use as normal.
This was the initial fix that was the ONLY way to use the device after root, but now most stock kernels being built include the fix, and dont require this.
Hope this helps, and i dont mean to be rude by my response but theres a ton of this info everywhere on the forum and these questions that have been asked 1000 times wont keep getting answered. Please use the search function or read the disclaimers us devs are putting out there before using the methods to gain root and be using cfw.
Team DevDigitel said:
this has been discussed so many times is why no one is responding.
if you googled v20 and static screen you would have had 1000 posts discussing this or even when you read disclaimer on root.
The static is due to changing your aboot aka bootlaoder for the us996 unlock one, casuing ALL stock boot.img to display static. Fortunately months after root had been released the devs developed fixes to hide static and return a normalish boot experience. with the exception 1st boot takes a little longer.
The static can be overcome by locking screen after bootup, then covering the proximity sensor until 2nd screen falls asleep then unlock and use as normal.
This was the initial fix that was the ONLY way to use the device after root, but now most stock kernels being built include the fix, and dont require this.
Hope this helps, and i dont mean to be rude by my response but theres a ton of this info everywhere on the forum and these questions that have been asked 1000 times wont keep getting answered. Please use the search function or read the disclaimers us devs are putting out there before using the methods to gain root and be using cfw.
Click to expand...
Click to collapse
I was looking up info on "LG V20 Graphical Glitched Boot Screens" prior to posting this, and in that process I had only found one dead post, trust me I looked guess the search term I used was too descriptive, or uncommonly used? thanks for the reply though, I kinda fixed it on my own (by accident) through patching in a Stock Kernel Mod through TWRP after writing a fresh VS995 custom ROM it's all good now, my last post wasn't a bump, it was a poorly explained solution lol
Sry, I'm still not use to how this forum is ran, I kinda bounce between forums like a drunk whore on prom night
Link To Kernel Mod Used | ModStock
Hello there,
Yesterday, I successfully rooted my new Samsung Galaxy S10+ (Android 11) using Magisk and Odin. Before, I used a rooted S8+. During the process, I noted that there were some significant changes which complicated the process of rooting for the S10+, one of them being that you need to press specific buttons and connect the phone via it's port for Magisk to actually boot. Naturally, I found that quiet annoying to always do and looked for a workaround. I did some reading and if I understand correctly, the reason why we must use this workaround is because the S10+ lacks a writable ramdisk part, which is why Magisk is installed in the "recovery" part. Can someone confirm this to me? And with all that being said, I still have some lingering question which I hope some kind soul could provide me the answer to?
Will there every be a way to boot Magisk directly or what would need to happen in order for it to work?
What should I avoid doing to not brick my device? Just the most important things like "Don't try to wipe you data when" etc.
Is there a way to disable the warning notification (the non-original software) during boot?
Should I be concerned because of vaultkeeper?
Should there already be a thread or answer for some of my questions which I overlooked during my search, I would appreciate if you could link them!
With kind regards,
DasMalzbier
Edit: Somehow, I got the achievment "thread poster Lv.3 [You created 100 threads!]" just from this? lol
Yes, the ramdisk is in the recovery.img of your device. There's an easy way to boot with magisk, power+bixby+Vol ↑.
The warning you see is controlled by the bootloader. Once a device is unlocked it will always show that, and there's no way to get rid of it. It used to be controlled by the logo partition, but that changed with Android 9+ for most oems. So unfortunately you're stuck with it. For further issues or questions about your device, please post in the appropriate forms. The S10+ forums can be found here. https://forum.xda-developers.com/c/samsung-galaxy-s10.8693/
I don't blame you for posting here though. The S10+ forums aren't easy to find. But now you know for the future.
Thanks for the quick response and answers
I didn't notice that I posted my inquiry in the wrong thread. Sorry about that, I'll move this thread now.