Related
Thoughts?
I've been noticing that there doesn't seem to be much activity around the Sprint Version of the HTC One. Correct me if i'm wrong. I did manage to get the recovery changed and the device rooted.
Recovery didn't go too smoothly because i didn't realize there was a different TWrp for sprint and i assume the same goes for clockwork. I tried using both and wouldn't work until i found a very brief mention of a sprint TWRP file that ended in wls.
I really wanted to try the Revolution HD ROM but quickly noticed that it seemed like most all version of the htc one are supported except the sprint version. There is a v9.4 but i have yet to find it.
Question: Is the sprint version that different from the others? That difficult to work with? or is the interest just too low?
I was thinking i'd try to have this thread (easily searchable for sprint users) with some quick info on how to deal with those devices. Though i will admit i'm not that skilled in software mods. Just a member of the community that appreciates all the work you guys put in on all these devices and supporting the freedom we enjoy to use our devices as WE please.
If anyone want to join in and commenting about Sprint specific devices and issues.. feel free.
Sorry the sprint version tends to lag behind others because of the cmda chip. Since all international leaks are probably going to be from gsm models, they are only going to be usable on gsm versions of the phone. Until someone leaks a cdma version of 4.2.2 there's not much we can do.
Sent from my HTC One using Tapatalk 4 Beta
This thread shouldn't be here. This should be in the General thread.
Thread Moved
Please only post development related threads in the dev section.
Recovery Experience
Step 1 - Unlocking Boot Loader
I used the Revolution HD thread as a start point. It is very detailed and easy to follow. It directed me to this flashing Guide http://forum.xda-developers.com/showthread.php?t=2265618... The bootloader process is easy and pain free.
Step 2 - Flashing to a more advanced recovery
The guide doesn't suggest which to use. I went to the Device essentials (sticky thread of the forum). The choices seem to be TWRP and Clockwork ... (if there are more feel free to suggest). Unfortunately this didn't go as planned because I was unaware that the recoveries for a sprint device were different ... So for you ... if you are using TWRP you must use the recovery specifically for Sprint devices .. currently the file name is "openrecovery-twrp-2.5.0.0-m7wls.img". I will try to find a link or anyone can volunteer it.
1. The first thing it allows you to do is save your current recovery. I was unable to do this because i had the wrong recovery and by the time realized it i had tried to flashboot flash. However, you can flashboot boot .. which basically allow you to load the recovery and save your current recovery. then you can flash and replace your recovery with the new one.
That is it.. that is kind of where i am at for now. I haven't flashed a ROM .. and i will say i am having some difficulty with both "superuser" it keeps asking to update but then fails and Wifi Tether .... so i'll return with answers to that when i find them.
Hope this helps someone
seemed like a development issue to me ..
original_ganjaman said:
Thread Moved
Please only post development related threads in the dev section.
Click to expand...
Click to collapse
instructions on how to avoid some development / installation problems? I thought that would fit into development. Apologies if it doesn't fit. Thanks for the move.
makes sense ..
syaoran68 said:
Sorry the sprint version tends to lag behind others because of the cmda chip. Since all international leaks are probably going to be from gsm models, they are only going to be usable on gsm versions of the phone. Until someone leaks a cdma version of 4.2.2 there's not much we can do.
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks. That both sucks and makes sense.
_sunz said:
instructions on how to avoid some development / installation problems? I thought that would fit into development. Apologies if it doesn't fit. Thanks for the move.
Click to expand...
Click to collapse
That's just it, it is an issue. If you have issues with a particular custom ROM then you should post in that thread. Development thread is for development and not "issues" with a development.
_sunz said:
instructions on how to avoid some development / installation problems? I thought that would fit into development. Apologies if it doesn't fit. Thanks for the move.
Click to expand...
Click to collapse
Nope, this contains no development, its more of a discussion thread. I can see the confusion, so no problem.
_sunz said:
Step 1 - Unlocking Boot Loader
I used the Revolution HD thread as a start point. It is very detailed and easy to follow. It directed me to this flashing Guide http://forum.xda-developers.com/showthread.php?t=2265618... The bootloader process is easy and pain free.
Step 2 - Flashing to a more advanced recovery
The guide doesn't suggest which to use. I went to the Device essentials (sticky thread of the forum). The choices seem to be TWRP and Clockwork ... (if there are more feel free to suggest). Unfortunately this didn't go as planned because I was unaware that the recoveries for a sprint device were different ... So for you ... if you are using TWRP you must use the recovery specifically for Sprint devices .. currently the file name is "openrecovery-twrp-2.5.0.0-m7wls.img". I will try to find a link or anyone can volunteer it.
1. The first thing it allows you to do is save your current recovery. I was unable to do this because i had the wrong recovery and by the time realized it i had tried to flashboot flash. However, you can flashboot boot .. which basically allow you to load the recovery and save your current recovery. then you can flash and replace your recovery with the new one.
That is it.. that is kind of where i am at for now. I haven't flashed a ROM .. and i will say i am having some difficulty with both "superuser" it keeps asking to update but then fails and Wifi Tether .... so i'll return with answers to that when i find them.
Hope this helps someone
Click to expand...
Click to collapse
Resolved SuperSU and Wifi Tether Issue. The issue was the binary update. HOwever i am not sure how i fixed it. i just tried using the TWRP/CWM method for a third time and it work. it rebooted into recovery, installed the binary file and booted back into the OS. SuperSU worked and then i tried Wifi Tether and it started to work as well .. FYI "settings for Wifi Tether" that i use
1. Device profile "Generic ICS/JB (wlan0)". 2. Wifi-Driver reload (checked).
Now I just need the awesomest best ROM .. any suggestions!?
it seems to me that something happened recently that bricked everyone's a500, because it's all I'm seeing on the front page and all are recent posts...
but most people are using JB and such, I just have a stock ROM unlocked, and overclocked... still can't pass the acer logo boot screen. it just crashed before my eyes the other day, I was watching a video about lasers
I've tried to update with the latest update.zip... nothing.
I'm at a loss at what is the best next step, I'm no noob, but, I'm no pro either.
any help? ideas?
And have u read any of the posts in those recent threads that are marked as solved?
Sent from my GT-I9300 using Tapatalk 4
yeah, they all involve custom recovery bootloaders, TWRP, CM10, JB and/or V8, if I had made those mods I'd have more options on how to fix it.
so far the only option I seem to be able to have is loading an update.zip, which I got the latest one and doesn't work.
MOD EDIT: Inflammatory comments removed.
Ok, let's cool off and take 5.
Bricked tablets are frustrating, and depressing. Trust me, I know this personally, on more than 1 occasion. But no need to let tempers flare. After all, the primary goal is to get things working.
I can personally vouch for @dibb_nz in his willingness to help a ton of people get tabs working. So no need for people to get "testy".
Not all tablets can be unbricked, but most can. It requires a lot of searching, and reviewing threads which had success. As with the 500/501, the very first step is to get the UID number. If a user does not have their UID number written down, then it requires installing Ubuntu on their pc, and getting it that way.I believe dibb has a link for it in the signature I believe. If not, lots of info for it in Q & A recently with some of the Solved cases.
Oh, and the 500/501 is not the only tab having issues like this. All the tabs do (currently working the same issue in the 700 forums, but we don't have NVFlash).
So no more testy comments from anybody please.
Cheers.
MD
Hey guys, I don't post here often, but I'm not new to this. It was through this forum that I first started rooting with mfy s3.
I just got a note 3 through Sprint. I've gotten used to getting off the grid, so I immediately jumped to root it. I decided on Jellybomb after reading some reviews. Then I downloaded everything necessary to make the jump: Odin, 1.85 and 3.09, jellybomb, cwm 6.0, twrp 7, auto-root, and the original roms in case I had to hop back.
First I went with Chainfires auto-root. I didn't seem to have any problem flashing that. The problem came with flashing twrp and the new rom. I can't remember which one was giving me trouble (I've been fighting it almost a week now). Somehow some way the phone has been stuck in an autoboot that says "seandroid not enforcing" and either "warranty bit: recovery" or "warranty bit: kernel". I tried new kernels. I tried things in different order. I can get into recovery but only after going immediately after autoroot. Even there you have a broken android.
Please help. I've been without a phone for a week.
KoolCharisma said:
Hey guys, I don't post here often, but I'm not new to this. It was through this forum that I first started rooting with mfy s3.
I just got a note 3 through Sprint. I've gotten used to getting off the grid, so I immediately jumped to root it. I decided on Jellybomb after reading some reviews. Then I downloaded everything necessary to make the jump: Odin, 1.85 and 3.09, jellybomb, cwm 6.0, twrp 7, auto-root, and the original roms in case I had to hop back.
First I went with Chainfires auto-root. I didn't seem to have any problem flashing that. The problem came with flashing twrp and the new rom. I can't remember which one was giving me trouble (I've been fighting it almost a week now). Somehow some way the phone has been stuck in an autoboot that says "seandroid not enforcing" and either "warranty bit: recovery" or "warranty bit: kernel". I tried new kernels. I tried things in different order. I can get into recovery but only after going immediately after autoroot. Even there you have a broken android.
Please help. I've been without a phone for a week.
Click to expand...
Click to collapse
This one is the International Note 3 forum.
You should ask for actual details in the specific Sprint Note 3 forum:
http://forum.xda-developers.com/note-3-sprint
You should also pay more attention to the fact that the questions should be posted in the Q&A subforum.
Thanks
xclub_101 said:
This one is the International Note 3 forum.
You should ask for actual details in the specific Sprint Note 3 forum:
http://forum.xda-developers.com/note-3-sprint
You should also pay more attention to the fact that the questions should be posted in the Q&A subforum.
Click to expand...
Click to collapse
Cheers! It looks from your sig though that you have found a work around on your international version. Are they really that different, that need entirely separate instructions. Obviously I downloaded all of the suggested software for Sprint and followed Sprint suggested, but I'm frustrated because I simply don't understand how I could do something the same way everyone else did and yet have it fail on me like this.
I am having the exact same problem...at first i was able to flash 'openrecovery-twrp-2.6.3.0-hltetmo.img.tar and it would boot my phone back to normal. I have now run into this problem again and my first original fix isn't working anymore. If I can figure out a way I will definitely let you know!
Getting Answers
Anonymous777 said:
I am having the exact same problem...at first i was able to flash 'openrecovery-twrp-2.6.3.0-hltetmo.img.tar and it would boot my phone back to normal. I have now run into this problem again and my first original fix isn't working anymore. If I can figure out a way I will definitely let you know!
Click to expand...
Click to collapse
Hey man, thanks for reaching out. I realized I should probably have been in the Sprint form so I created a new thread there and I've been getting some help!
If you want: shoot over there and see if the tips can help you: http://forum.xda-developers.com/showthread.php?p=51096673
Anonymous777 said:
I am having the exact same problem...at first i was able to flash 'openrecovery-twrp-2.6.3.0-hltetmo.img.tar and it would boot my phone back to normal. I have now run into this problem again and my first original fix isn't working anymore. If I can figure out a way I will definitely let you know!
Click to expand...
Click to collapse
Hey man we've made a lot of headway at the above thread Thanks to Macmars. You should check it out and see if we can help each other.
Sent from my SM-N900P using xda app-developers app
KoolCharisma said:
Hey man we've made a lot of headway at the above thread Thanks to Macmars. You should check it out and see if we can help each other.
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
I figured out what to do, use odin 3.9 and flash this, it took about 15 minutes to go through the whole process. Once my phone boot up it froze at the T-Moble logo or whatever, so I waited like 20 minutes and then powered it off, went into recovery and did a factory reset which then solved all my problems. I lost root, but no big deal to me. Better than buying a new phone!!! Btw the only place I could find this file is off sammobile.com. You have to sign up for a free membership thing but at least they give you the stock firmware.
TMB-N900TUVUCNB4-20140305155920/N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md5
KoolCharisma said:
Hey man we've made a lot of headway at the above thread Thanks to Macmars. You should check it out and see if we can help each other.
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Right on man!
Sent from my SM-N900P using xda app-developers app
I really need help, my Samsung Galaxy S7 Edge has just got a red screen since i installed a Kernel and i cant use my phone at all.
Any help would be greatly appreciated.
The Kernel I uses was Super Kernel and I also had the Super Man ROM
Thanks A Lot Guys
Just flash stock boot.img from TWRP recovery and you will be fine if you cant get into recovery go to download mode and flash stock firmware with odin
Sent from my SM-G935F using Tapatalk
Why did you flash a kernel? Do you know what a kernel is, and what is does? Do you know how to recover in case things go wrong? Nope, so you should probably do some reading before you decide to modify anything next time.
You probably flashed the "Flat" kernel. Download the Edge kernel and install it.
I always do a nandroid,and back up recovery and boot via Flashify.
Your phone will live.
Sent from my SM-G935F using XDA-Developers mobile app
J.Biden said:
Why did you flash a kernel? Do you know what a kernel is, and what is does? Do you know how to recover in case things go wrong? Nope, so you should probably do some reading before you decide to modify anything next time.
Click to expand...
Click to collapse
he asked for help not a lecture.
simonhcai said:
he asked for help not a lecture.
Click to expand...
Click to collapse
He still needs to do his research and tons of reading
"And on that bombshell!"
Sent from my Gorgeous Echoe driven AEL Kernel Powered G935F
simonhcai said:
he asked for help not a lecture.
Click to expand...
Click to collapse
Do you really think that people are lining up here to help people that have not read a single guide or anything? Do you think people are getting paid helping around here? I'm not giving him a lecture, but it's expected that you know what the F you're doing before doing anything. You must be new around here.
J.Biden said:
Do you really think that people are lining up here to help people that have not read a single guide or anything? Do you think people are getting paid helping around here? I'm not giving him a lecture, but it's expected that you know what the F you're doing before doing anything. You must be new around here.
Click to expand...
Click to collapse
How do you know he hasnt read a single thing?everyone's a noob at some point and if hes made a genuine mistake then maybe asking for help from people who could stop him from ruining his phone which he might have a long contract on,if you know how to help him the time you spent replying you maybe could of solved this problem for him.
simonhcai said:
How do you know he hasnt read a single thing?everyone's a noob at some point and if hes made a genuine mistake then maybe asking for help from people who could stop him from ruining his phone which he might have a long contract on,if you know how to help him the time you spent replying you maybe could of solved this problem for him.
Click to expand...
Click to collapse
He would know how to recover from this if he had done some proper reading. If he isn't even aware what a kernel is, or how to recover, he hasn't been reading, has he? The solution is not to first flash, fail, and then ask questions. Read, read and read, then flash and succeed.
TL;DR: Read.
J.Biden said:
He would know how to recover from this if he had done some proper reading. If he isn't even aware what a kernel is, or how to recover, he hasn't been reading, has he? The solution is not to first flash, fail, and then ask questions. Read, read and read, then flash and succeed.
TL;DR: Read.
Click to expand...
Click to collapse
Basically sums up XDA. Also don't like people who go on spamming "HALP" without posting a logcat (or a last_ksmg in case of kernels) or any other info that could possibly help identify the issue and expecting devs to magically help them. People really need to read this: http://forum.xda-developers.com/showpost.php?p=2031989&postcount=45
Although I would like to add that sometimes it's not totally the user's fault, as many kernel threads don't really provide any information regarding the behavior of the kernel in certain conditions, or the OP of the thread does a poor job at explaining which files to grab or how to flash and whether to wipe any cache partitions (or whatever the post-flash requirements are) or the requirements of the kernel. For example, I installed jesse's kernel and it caused my phone to fail verification on bootup, even when I had dm-verity disabled. Now, people should read the thread before flashing, because there's a possibility that someone else had a certain issue that you may face upon installation, but I feel the OPs should have a section called "Common/Rare Issues" in the thread where user-verified solutions to common/rare problems found when flashing the OP's kernel/ROM are available, so you don't have to search hundreds of pages to find a fix. If you look at the threads of some popular ROMs/kernels, they have one, for the same reason. In my case, I was the first one to face it, so I had to figure out on my own why it happened and find my own fix, that took me a couple of hours. But having such a section saves you time, which is helpful regardless of whether you're capable of identifying the cause of a problem and fixing it yourself or not. I have a "Common problems" section in my app's descriptions for the same reason, because I like to think from the user's perspective as well, plus I don't want my users to be spamming my inbox asking for fixes to common problems, it's more efficient to have a FAQ.
But yeah, READ, UNDERSTAND, LEARN, instead of just expecting people to magically help you with your problems.
Hello !
1. Download Samsung-smart-switch.
2. Install it and run it.
3. Choose more on Top of program and choose the first Part of the menu (intialize software...or so)
4. Follow the instructions on screen and voila .....
YOUR PHONE IS BACK WITH ALL ON STOCK
Hope it helps you
This is an effort to consolidate fixes, tweaks and mods specific to the rooted G955U/G955U1 SnapDragon S8+ via SamPWND.
The initial release of root for this version by the development, contributions and tireless efforts from elliwigy, Harry44, akiraO1, BotsOne, GSMCHEN and jrkruse are obviously being enjoyed by many, as is evident by the visits to elliwigy's release page.
Unfortunately, that thread is in dire need of clean-up because it has become a hodgepodge of redundant rooting questions, helpful answer posts (and complaints), all infused with a few mods and tweaks mentioned.
So let's share what can be done (and what cannot thus far) with this rooted version.
Please (!!!), already be aware of which device you have, and if SamPWND works on your device. "How do / Can I root my..." questions simply don't belong here!
Let's try to keep it clean in here by looking around the forum first before posting, but also by being helpful and not condescending to those of us enjoying root who are perhaps not as knowledgeable about such matters as others.
Some of the most common questions being asked, and their answers from that thread
Flashfire infinitely spinning for part 2 root steps
Turn on airplane mode
Is there a fix for the 80% battery max capacity?
No, and it seems unlikely at this stage. Make yourself happy and hide your battery percentage.
Green/glitchy screen
Most (including myself) have resolved or heavily mitigated this via the AQI1 fw posted recently.
S8+: https://forum.xda-developers.com/ga...sampwnd-root-green-screen-corruption-t3673810
S8: https://forum.xda-developers.com/ga...ampwnd-green-screen-corruption-fixed-t3673782
Does Magisk work with this root?
No.
Does Xposed work on this root?
Unofficially yes, search for unofficial Xposed s8, it will be in the device forums. Edit-or use this link: https://forum.xda-developers.com/galaxy-s8+/how-to/unofficial-xposed-guide-snapdragon-s8-t3663728
Can I install custom roms?
No, the BL is still locked. The last I read is there are some ideas around how we might achieve an unlock, but nothing so far. There's is the modified stock rom available in the OP of the root thread that provides csc and superSU but beyond that, no.
Screen rotation is messed up / reversed
You downloaded the wrong step 1 files. Try again for your device (plus or non-plus)
I can't think of any other recurring questions, but I've been keeping up to date on that post for more of the 318-or-so pages, and there's a lot of other useful information held within them. Worth a read.
Awesome first response!
So can I start with this:
"Unofficial Xposed'...
Where are the where's & how's located for our specific device, along with the yeahs & no's about what Xposed can do? I've looked and read, but there really is no clear post (that I have found) saying that our model can (or can't) DL Xposed and make things work.
Out of level 8, I'm probably a level 2 coming from rooting back in the days of the first Droid LOL! So I figure if we can keep things down to a level 3 or 4 here, we can learn and teach about WHY certain things won't work.
I'm also very interested in the capabilities of our camera. I used to use chdk to hack Cannon P&S cameras, and despite all my hours doing so, the hardware could never deliver night shots like this phone!
AddictedToGlass said:
Awesome first response!
So can I start with this:
"Unofficial Xposed'...
Where are the where's & how's located for our specific device, along with the yeahs & no's about what Xposed can do? I've looked and read, but there really is no clear post (that I have found) saying that our model can (or can't) DL Xposed and make things work.
Out of level 8, I'm probably a level 2 coming from rooting back in the days of the first Droid LOL! So I figure if we can keep things down to a level 3 or 4 here, we can learn and teach about WHY certain things won't work.
I'm also very interested in the capabilities of our camera. I used to use chdk to hack Cannon P&S cameras, and despite all my hours doing so, the hardware could never deliver night shots like this phone!
Click to expand...
Click to collapse
You may have read my post just before I edited it to add the links. The link I posted for the s8 is where all if the Xposed info is held for our devices. I am currently running it with the latest fw I also linked to with no problems. That thread also contains a few modules the OP has verified working. I am currently only using it for a couple of tweaks from "all my.." and xVoice++. I also was utilizing this Xposed version before flashing the fw mentioned, and it's worked perfectly for both. I can't remember which fw I was on previously though.
regarding camera mods, I made an attempt the moment I got the phone to replace the stock camera with a ported pixel, before researching how to do it properly these days. Wound up with crashing camera warnings every 30 seconds and my backup wouldn't restore properly in titanium and had to reset completely and start fresh.
I used to root back in the Motorola Droid (original) days, when root required 30-or-so lines of commands, I'm sure you remember funny how we've come full circle. I swapped to iPhone for the iPhone 4, enjoyed a bootrom exploit for several iOS versions, and stuck with apple up until just last weekend so it's been a while since I've been on the root scene myself, much has changed indeed. It's the first Android device (S8+ here) that actually made me want to switch away from apple, and I don't yet regret it.
nice concept.. just a forewarning tho, these posts typically go in general discussion..
elliwigy said:
nice concept.. just a forewarning tho, these posts typically go in general discussion..
Click to expand...
Click to collapse
Thanks! And it's alright if it gets moved there so long as it still helps everyone out and you wizards walk through once in a while to bless us all with a bit of wisdom. LOL!
Meanwhile, for as long as it's allowed to stay here, it might serve well to keep distractions off your release thread.
elliwigy said:
nice concept.. just a forewarning tho, these posts typically go in general discussion..
Click to expand...
Click to collapse
Considering less than one hour after I replied with the common questions and answers, someone asked about flashfire on page like 318 again, I'm sure this post is pretty low on priority for the people who tend to ask the questions.
I just finished rooting my sprint s8+ with sampwned. I installed my 256gb micro sdcard and I get the kernel panic reboot to error screen. Am I unable to use the sdcard? I'm scouring xda for any info. Just looking for a little help if anyone knows anything I don't. Thanks.
Nice idea OP.
Some fixes may be had by using the @partcyborg ROM for S8. It is in the S8 ROMs, Kernels, ... Forum https://forum.xda-developers.com/galaxy-s8/development/root-partcyborgrom-aqi6-deodexed-t3702988
For the S8+ @jrkruse has some good info in the S8+ Verizon, ROMs, Kernels, ... Forum. https://forum.xda-developers.com/verizon-galaxy-s8+/development
monroe0328 said:
I just finished rooting my sprint s8+ with sampwned. I installed my 256gb micro sdcard and I get the kernel panic reboot to error screen. Am I unable to use the sdcard? I'm scouring xda for any info. Just looking for a little help if anyone knows anything I don't. Thanks.
Click to expand...
Click to collapse
i think u pmd me but flashing a newer combo boot.img fixes it.. its a known issue with samsungs older combo firmwares, not related to root
elliwigy said:
i think u pmd me but flashing a newer combo boot.img fixes it.. its a known issue with samsungs older combo firmwares, not related to root
Click to expand...
Click to collapse
Yea thats what I did. Problem solved.
Just want to add that the Official xposed app and framework, work on this device
Sent from my SM-G955U using Tapatalk