Related
hello everyone, i just got an unlock streak to use with t-mobile. im the second owner but the other guy said he just received it as a replacement from dell. this are the specs
baseband:GAUSB1A140514-US
build number:2.2
my problem:the phone is unlock so when i put my sim and boot i get the led flash 3 times and then goes on a boot loop. and it will keep doing it unless i take out my sim. i manage to get it to somewhat work by booting w/o sim, then put phone on airplane mode then off. place sim and boot. then i take it off plane mode and quickly turn of data. then wait for it to recognize tmobile towers, then turn on data and it works for a few mins then goes on a boot loop again. has anyone had this issue?
my second problem is i try to flash several GB base roms and it flashes but i get a lot of FC and cant run the rom. I currently have (miui 2.3.2 ENG DS5 ) and it runs fine w/o my sim. as soon as i put my sim its back to the boot loop.
btw i am not a noob to android, but am a noob to the dell streak. any help,tips,comments is appreciated thanks.
JDM-Bb said:
hello everyone, i just got an unlock streak to use with t-mobile. im the second owner but the other guy said he just received it as a replacement from dell. this are the specs
baseband:GAUSB1A140514-US
build number:2.2
my problem:the phone is unlock so when i put my sim and boot i get the led flash 3 times and then goes on a boot loop. and it will keep doing it unless i take out my sim. i manage to get it to somewhat work by booting w/o sim, then put phone on airplane mode then off. place sim and boot. then i take it off plane mode and quickly turn of data. then wait for it to recognize tmobile towers, then turn on data and it works for a few mins then goes on a boot loop again. has anyone had this issue?
my second problem is i try to flash several GB base roms and it flashes but i get a lot of FC and cant run the rom. I currently have (miui 2.3.2 ENG DS5 ) and it runs fine w/o my sim. as soon as i put my sim its back to the boot loop.
btw i am not a noob to android, but am a noob to the dell streak. any help,tips,comments is appreciated thanks.
Click to expand...
Click to collapse
You need to flash gingerbread baseband files which are amss.mbn and dsp1.mbn through fastboot.
If you are not new to Android I'm assuming you have fastboot and adb drivers setup on your computer and/or the androidsdk installed to the C: drive and paths set to make command line flashing easy... if not then now would be the time to get all that done, if not then you will be back every other day asking for help and getting flamed..
on a side note, had you bothered to read QUITE A BIT MORE the answers I just gave you are provided in the stickies, not even much need to search really, so please don't be one of those newbies that starts a new thread or posts each time your Streak hiccups, ALL the info you need has already been gone over more times that I care to remember
Your baseband indicates the Streak at one point was running 405, the beta Gingerbread build. It's no wonder you're having problems given you're attempting to run Froyo with a beta Gingerbread baseband.
Where this Streak is used, it's best to flash a stock ROM first to ensure the Streak works properly. 407 would be perfect for this as it's the stock Gingerbread build but you could also use one of the stock Froyo ROMs as well. After flashing the stock ROM and making sure everything is working, then go to your chosen ROM, using the information in the stickies.
Strephon Alkhalikoi said:
Your baseband indicates the Streak at one point was running 405, the beta Gingerbread build. It's no wonder you're having problems given you're attempting to run Froyo with a beta Gingerbread baseband.
Where this Streak is used, it's best to flash a stock ROM first to ensure the Streak works properly. 407 would be perfect for this as it's the stock Gingerbread build but you could also use one of the stock Froyo ROMs as well. After flashing the stock ROM and making sure everything is working, then go to your chosen ROM, using the information in the stickies.
Click to expand...
Click to collapse
thanks for the reply, so then what you are saying is that the phone was on GB at one point? man, i knew this guy tryed to flash a dif rom before he sold it. He told me he just got it replace by Dell and decided he didn't want it. i fixed my second problem but im still having the issue with the phone rebooting when data is turned on and then freezes at boot screen.
cdzo72 said:
You need to flash gingerbread baseband files which are amss.mbn and dsp1.mbn through fastboot.
If you are not new to Android I'm assuming you have fastboot and adb drivers setup on your computer and/or the androidsdk installed to the C: drive and paths set to make command line flashing easy... if not then now would be the time to get all that done, if not then you will be back every other day asking for help and getting flamed..
on a side note, had you bothered to read QUITE A BIT MORE the answers I just gave you are provided in the stickies, not even much need to search really, so please don't be one of those newbies that starts a new thread or posts each time your Streak hiccups, ALL the info you need has already been gone over more times that I care to remember
Click to expand...
Click to collapse
thanks for the reply
correct i do have drivers and adb in my PC and this is not my first time using adb commands. and yes i did bother reading many threads and using the search tool and found lots of great info but nothing pin pointing to the same problem im having with the phone not liking it when i turn my data on.
Btw i figure out why non of the GB roms were working, when i was doing the factory reset i was only doing it through streakmod recovery. but when i FR on the previous menu it worked.
i also made the diagnostic test through fastboot menu to test the sim and every thing else and everything is fine
Sorry for the late reply. I believe your data issues will resolve themselves by installing 407. From there you can install one of the custom ROMs.
hmm ok ill try that
isimobile along with pershoot has found a faster and better way of fixing this!:good:
I suggest you use isimobile's method found " HERE !!" Don't forget to thank him!!! or we'll fallow you home and poop in your driveway!
If for some reason that does not work try my method!
Sorry Mods I wasn't sure which forum I should put this in please move if incorrect!
A little history before I continue!
I recently decided to Root my TELUS GT-P7510/16GB/WIFI so I went to the Galaxy Tab 10.1 Android Development Forum and fallowed S0ckM0nk3y's [ACSyndicate] [How-To] Root/Unroot The SGT 10.1 GT-P7510 USA Retail WiFi Only
.
Everything was going fine until I was to put it into Recovery Mode (At this point Its CWM-based Recovery v5.0.2.7) to Flash Samsung_Galaxy_Tab_10.1_root.zip, but as soon as it booted into Recovery the screen was scrolling as shown here http://www.youtube.com/watch?v=GhGm6kq_4dg&feature=player_embedded by castiel19.
There is nothing you can do to correct this except fallow my Guide (OR) download and install the only CWM Recovery that works for us with this problem which is ClockworkMod_Recovery_v5.5.0.4_P75xx.tar
... I have tried all of them and this is the only one that works....For me anyways!
I was not satisfied with this as I Purchased ROM Manager and it shows that the latest update for my device is V4.0.0.4, so I decided to try all I could to find a solution and I did.... By accident!
Before You continue, Please back up all your personal stuff to your PC or any other media but do not leave anything you can not loose on the TAB it will be gone if you continue!
Meat, Potatoes and Gravy!
Follow S0ckM0nk3y's Guide HERE you want to follow the Unroot part!
Click on the very first Blue DOWNLOAD link in his guide which will open another forum with a similar layout and click the first Blue DOWNLOAD link at the top of that guide save it to your desktop. The file is called sgt10.1_root_unroot.zip and it is 381MB. Once downloaded, extract to a new folder on your desktop, now open that new folder on your desktop and extract the ODIN3_v1.85.zip!
Put your Tab 10.1 into Download Mode by using S0ckM0nk3y's guide.
Open Odin3_v1.85.exe that is in the folder that you extracted the two downloads too on the desktop.
Click the PDA button and choose P7510XABKMP_P7510UEKMP_HOME.tar.md5.
Plug the USB into your PC
Plug the other end into the Tab
In the Odin Software on your PC the box below ID:COM should be yellow with stuff in it click the start button it will take a few minutes. 1min 59sec for me. once finished the Tab will reboot and do some stuff then it will reboot again to the OS.
Your Unrooted with an to up to date stock ROM!
This is optional but recommended! Power off your device now, and then put it in Recovery Mode.
Once Android System Recovery comes up click "wipe data/factory reset" then click "wipe cache partition" then click "reboot system".
Now Root using HERE and install any of the appropriate CWM Recovery versions without having the rolling screens!
I will clean this up later it is 2am and I have to Tow a car 800km tomorrow! There are fellow members that need this so it was rushed sorry!
I would like feedback on this as to wether it works or not for you!
I had my wife follow this guide with her Tab that was doing the same thing and it worked for her first time, but i'm more worried that my wording might not be understood by some and if that is the case it may not work for you and i would like to help you understand!
Update: 1
I can not confirm this but thanks to "isimobile and vladin79" it also works on 3g P7500 version!
Update: 2
P7510XABKMP_P7510UEKMP_HOME.tar.md5 is now included in S0ckM0nk3y's Package! Upated this guide to reflect that change.
Update: 3
After you fallow this Guide and all goes well but then you notice that when your screen goes to sleep then you wake it up and it is scrambled in the center of the screen and the only way you can stop it is to reboot, follow this Guide! http://forum.xda-developers.com/showthread.php?t=1680738
Major Update: 4 Major Thanks To "isimobile"
Please Read his post Here I am going to test it and will post back!
Don't forget to hit the Thanks button over there! -------------------------------->
Hi
I have same behaviour with the recovery, i fond the overcome recovery who works fine.
But if i install a rom i get same behaviour as recovery during boot. The only way to get endless scroll off is to lock and unlock the screen
Does your process remove endless scroll off curtom rom too?
Yes you should be able to install any CWM without the screen rolling, I'm thinking that there is something about the stock software that came on our particular Tabs that is trying to stop us from replacing Stock Recovery!
I flashed every CWM version mentioned in the Tab 10.1 WIFI forum and the only one that did not roll in Recovery was v5.5.0.4 and if I flash another CWM with the working one installed I would boot up to a rolling CWM Recovery until I reflash the v5.5.0.4.
This is the stock info that was causing CWM to screen roll!
SKU: GTP7510UWR
SW-VER: VLKL2
Kernel Version: [email protected] #1
Build Number: HTJ85B.VLKL2 P7510VLKL2
great write up. thanks!
Did anyone tests this method ?
I don't have enought time during this week, but I'll try this week end.
I'm interessed to know if you succeed to install roms (and not recovery) without flickering.
Thanks
Omg, u rocks
I will test this method this evening (since the time I was looking for)... I hope it works !!
In facts, I think this issue is due to the version of stock (EUKL1 when I bought my GT... then passed to KL2 but same issue).
But, with Task ROM #14 and stock Kernel KMP I have no problem. Once I install Pershoot's Kernel, I have the rolling boot screen (same as CWM) => Turn off / turn on the Unlock screen and is ok.
Have you tried to install Pershoot's Kernel after your handling ?
Azertouf said:
I'm interessed to know if you succeed to install roms (and not recovery) without flickering.
Thanks
Click to expand...
Click to collapse
Not yet! I am not quite interested in trying any Cooked Roms as of yet due to cameras not working.
But I am willing to try Tasks 15 when it becomes available!
Neums said:
Omg, u rocks
I will test this method this evening (since the time I was looking for)... I hope it works !!
In facts, I think this issue is due to the version of stock (EUKL1 when I bought my GT... then passed to KL2 but same issue).
But, with Task ROM #14 and stock Kernel KMP I have no problem. Once I install Pershoot's Kernel, I have the rolling boot screen (same as CWM) => Turn off / turn on the Unlock screen and is ok.
Have you tried to install Pershoot's Kernel after your handling ?
Click to expand...
Click to collapse
I currently am trying the CWM Recovery from pershoot's thread HERE Works a treat! Thanks Pershoot " not sure if it's CWM but Superuser cannot see a network connection to get updated Binaries it just says fail, going to Unroot and start over and see if it is something I missed!<------NEVER MIND THIS! "
Edit
It seems Gmail doesn't like something either, I click on it and it opens and closes repeatedly about 15 times can’t see my Gmail! Time to wipe!<------NEVER MIND THIS!
Hey, dude, it works perfectly !
I can install Pershoot's CWM, Pershoot's Kernel and all others ICS Roms without any freacking rolling screen !!
---------- Post added at 08:08 PM ---------- Previous post was at 08:07 PM ----------
Azertouf said:
Did anyone tests this method ?
I don't have enought time during this week, but I'll try this week end.
I'm interessed to know if you succeed to install roms (and not recovery) without flickering.
Thanks
Click to expand...
Click to collapse
Try to install AOKP Build 28, it works perfectly !
Perfect, that works !!
I'm now on CWM 5.0.2.7 and AOKP Build 28 and no more screen flickering.
PERFECTS, thank's a lot !
Brilliant!
It works me too! Thanks a lot!
This post also very much helped me... so thanks again good sir!
You mentioned you got yours from Telus, I got my 32GB WIFI version from Futureshop, so maybe it's a Canadian version thing?
rAy
PS: I was also very disappointed to find that it has a white back when all of the googled pics of it had a black one... and the fact that it is white is not shown on the Futureshop website, nor shown or written anywhere on the box is baffling! It was almost a deal-breaker as I do NOT endorse white gadgets, but I'll give it a chance first haha.
It works.. Perfect. Thank you so much
I have P7500 model, which is 3G version. I decided to root it and installed several CWM recoveries, but all of them caused a scrolling screen when booted in recovery. Then I came to your guide and installed the ClockworkMod_Recovery_v5.5.0.4_P75xx.tar from your first post. It worked like a charm and the screen was steady as a rock. No more scrolling. Then I used it and rooted my tab.
Thank you so much for your efforts!
vladin79 said:
I have P7500 model, which is 3G version. I decided to root it and installed several CWM recoveries, but all of them caused a scrolling screen when booted in recovery. Then I came to your guide and installed the ClockworkMod_Recovery_v5.5.0.4_P75xx.tar from your first post. It worked like a charm and the screen was steady as a rock. No more scrolling. Then I used it and rooted my tab.
Thank you so much for your efforts!
Click to expand...
Click to collapse
I can confirm, also did it on a 3g(P7500) version, it worked. Thanks!
[Edit1] If you flash ICS, screen also scrolls.
[Edit2] Flashed the 7510 ROM mentioned in first post on the 7500. It worked. So I could flash then latest recovery from Pershoot. Flashed ICS, no Scrolling in ROM.
OP maybe you can edit first post to say it also works on the 7500?
Wow!!!! It DOES work!!!! After days of researching.
I bumped to your thread before but it wasn't make sense, why the hell should the stock ROM interfere with the process lol?
But it makes sense now, like S-OFF concept on the phone, NA stock is "s-off" while my stock (NZ) is not!
Thanks again man! CM9 + latest pershoot kernel now, all smooth no flickering
i've used your guide, thanks it works...the only problem i get now, is screen on/off (screen doesn't switch on after a screen lock or sleep..i can hear email notifications when i send it a mail)
this happens only after i flash Task 14..doesnt happen on the stock ROM for unrooting
so, i used your guide but instead, used Asian firmware to flash stock rom..however CWM screen flicker is back, and the only way for me to flash Task is to use Overcome CWM
I will maybe try your method again and flash ICS (just to test since i really need the camera)
I'm now really thinking there is something in the Asian Tabs that is doing this...
marjoejoejoe said:
i've used your guide, thanks it works...the only problem i get now, is screen on/off (screen doesn't switch on after a screen lock or sleep..i can hear email notifications when i send it a mail)
this happens only after i flash Task 14..doesnt happen on the stock ROM for unrooting
so, i used your guide but instead, used Asian firmware to flash stock rom..however CWM screen flicker is back, and the only way for me to flash Task is to use Overcome CWM
I will maybe try your method again and flash ICS (just to test since i really need the camera)
I'm now really thinking there is something in the Asian Tabs that is doing this...
Click to expand...
Click to collapse
Just the Asian stock, it might have other settings which prevents custom kernels and CWM from being fully functional. I have an Asian Tab but stocked it with American How you say, ummm Asian skin American flesh lol
awesome guide!
hylde said:
Just the Asian stock, it might have other settings which prevents custom kernels and CWM from being fully functional. I have an Asian Tab but stocked it with American How you say, ummm Asian skin American flesh lol
Click to expand...
Click to collapse
finally another one with an asian tab..
did you get the screen off/on problem after flashing task 14?
i want to try out ICS since this method (Stocking with US firmware) removes screen rolling of CWM and successfully applies the necessary CWM for pershoots ICS...have you already flashed ICS in yours?
but then, its May and official ICS might be rolling out soon (i hope)
** which US firmware did you flash? im lookin to try that out
Tab boots to "welcome" screen but does not register touches, leaving me unable to move forward. Ready for the long story?
I am helping a friend who bought this tab from a third party. When he received it, the previous owner stated that they did a factory reset back to Honeycomb but he noticed that it did in fact still have ICS on it. Probably OTA'd when the previous owner did the reset. Tab worked fine for about two weeks until one day he came home and the lockscreen would not register touches. That's where I come in.
I did the "erase, wipe" (booting while switching the screen rotation back and forth.) Tab wiped and brought me to the "Welcome" screen where you select country and language and still does not register touches. I have tried blackthund3r's flash and manager tools, as well as multiple guides to recover from what I have seen referred to as "flu." The main problem I have is that I cannot get a valid UID. Using USBDeview gives me an 11 digit serial but it returns as invalid when plugged into DotNetDetector and I am unable to use SDB because the non working touchscreen has left me unable to enable USB debugging.
Any suggestions, help, advice, on things I can try? I am really stumped and would like to help my friend/conquer this problem. Thanks for anyone who has taken the time to read this/offer help.
generalagony said:
Any suggestions, help, advice, on things I can try? I am really stumped and would like to help my friend/conquer this problem. Thanks for anyone who has taken the time to read this/offer help.
Click to expand...
Click to collapse
Get ready for some Ubuntu... Here is the guide that will get you a valid sbk. My nephew just brought his tab to me after forgetting his password. So I was in the same boat as far as UID/SBK. This is gonna take a while so put some time aside.
JdgM3NT4L said:
Get ready for some Ubuntu... Here is the guide that will get you a valid sbk. My nephew just brought his tab to me after forgetting his password. So I was in the same boat as far as UID/SBK. This is gonna take a while so put some time aside.
Click to expand...
Click to collapse
As sure as I am reading yoru reply the damn thing just started working. I was able to get to USB debugging and via ADB I was able to pull the UID; which was the same as the one I got from USBDeview btw. Still an 11 digit code. The only thing I can guess is that it has a faulty touchscreen, or maybe the battery was just too low to register touches? Thanks for your reply though. Always nice to be able to rely on the folks at XDA.
That is too cool. The other way is a learning experience to be sure. Enjoy.
JdgM3NT4L said:
That is too cool. The other way is a learning experience to be sure. Enjoy.
Click to expand...
Click to collapse
I have now realized that the touchscreen does work but is very glitchy and have found that lots of people have had problems with the OTA ICS update. Any suggestions on a good custom ROM for this tab? It isn't mine so I have not been following this section. Would like something close to stock ICS but with fixes that resolve the problems associated with OTA.
generalagony said:
...I was able to get to USB debugging and via ADB I was able to pull the UID; which was the same as the one I got from USBDeview btw. Still an 11 digit code...
Click to expand...
Click to collapse
generalagony said:
I have now realized that the touchscreen does work but is very glitchy and have found that lots of people have had problems with the OTA ICS update. Any suggestions on a good custom ROM for this tab? It isn't mine so I have not been following this section. Would like something close to stock ICS but with fixes that resolve the problems associated with OTA.
Click to expand...
Click to collapse
First check in Settings>About Tablet>Build Version - this will tell you what rom you are currently running -
Then, if you can, download and install Acer Recovery Installer
This tells you what bootloader and recovery is installed.
The glitches you speak of and the 11 digit uid point to an ICS Rom and unpatched HC bootloader - updating to the new BL often fixes these weird glitches BUT if you flash a custom rom as well, you'll be running sweet!!!
If you wanna stay close to Stock then I'd recommend ezterrys one here comes pre-rooted and busy box installed - and if you want to you can install his Over clocked kernel too.... plus its well maintained and supported
there are many tools and guides around to help you...the ones in my sig for instance the cpuid one has a lot of general info in it too re bootloaders, sbk and flash tools.
If you have any q just ask, there's always someone round willing to help...good luck!!
Hello everyone! My names Danny, sorry I'm extremely frustrated at the moment and apologize for not introducing myself properly in what ever you call your newcomer section here, but I'm ripping my hair out at the moment.
So last night for the 4th time I tried to root my Galaxy S4, again unsuccessfully. While I admit I am no programmer, computer whiz, or rocket scientist, I have previously rooted my old S3 and my girlfriend's Moto Photon successfully in the past, on the 1st try (although they were pretty simple 1 click roots no more difficult than the one I used here, or so I thought.) Now last night I tried to use the CF-Autoroot again for the 3rd time, which i figured after the first 2 attempts was doomed to failure also. This may be due to the fact that I updated it, but I don't know. I'm hoping someone here can point me in the direction of a root that will work with my phone, show me where I may have went wrong in the install,or give some instruction on how to delete the update so I can use the CF-Autoroot. As long as my phone will still function as normal, I could care less which option is used, however I do not have any programming experience whatsoever, so a simpler root would be excellent. I'll give you all the info I can below.
Software version: L720VPUAMF9
Hardware version: L720.08
Model #: SPH-L720
Android version: 4.2.2
Baseband version: L720PUAMF9
Kernal version: 3.4.0-953334
[email protected] # 1
Tue Jun 25 09:36:29 KST 2013
Build #: JDQ39.L720VPUAMF9
SE Linux Status: Permissive
Secure boot status: Type: Samsung
Device Status: Custom (No Triangle Away quite yet, as I'm not sure if it is yet supported on the S4, or if I even need it since I plan on keeping the phone)
Root was done on HP Windows 7 laptop 64-bit, with the phone in camera mode prior to turning off and going into download mode.
I followed the instructions on honai-android.blogspot(dotcom) using CF-Autoroot and Odin V3.07 to the T, except I have yet to get the drivers to install correctly (or so it tells me, everything works fine,) and in Step 4 it says the box should turn yellow and a port number displays, but in my case did not. It did display the "Added" message in the little box like it should have, but it did go through the whole process and I got a PASS notification as it says I should have. I have no idea why it won't work, other than maybe the drivers are screwing me. Ran Root Checker and it tells me "Please wait for Root Check to complete. System appears to be running very slow," and Titanium Backup won't work either. Root checker stayed like this all night last night while I slept.
Also I would appreciate some help reverting it back from the root I apparently didn't install, although I know some of it went through, or Root Checker would just say I didn't have superuser access.
I'm hoping one of you guys here might be able to help me out with this problem, and I greatly appreciate any help I can get. If anymore information is needed, just ask. Much thanks in advance.
You said you used Odin in camera mode? Did you mean download mode? I didn't have to install any drivers to get Odin to work. If you didn't get a yellow box with a com number in it the Odin didn't write anything to your phone. If you look here in the dev section there is a thread titled cf auto root. Download the zip file there and follow those directions and give it another try.
SGS4 Sent
ifly4vamerica said:
You said you used Odin in camera mode? Did you mean download mode? I didn't have to install any drivers to get Odin to work. If you didn't get a yellow box with a com number in it the Odin didn't write anything to your phone. If you look here in the dev section there is a thread titled cf auto root. Download the zip file there and follow those directions and give it another try.
SGS4 Sent
Click to expand...
Click to collapse
No my S4 was in camera mode. There are 2 options when I plug my phone in via USB to the PC, either camera mode or media device mode, PTP and MTP respectively. This is how it was set up before I turned the phone off to go into download mode, didn't think it made a difference, but I wanted to give as much info as possible. The phone went through all the downloading stuff on-screen with the red pirate android guy and everything while Odin was downloading to the phone, and Odin also said Added in the message box so I figure Odin recognized the device was present. I'll check out that thread though, thank you:good: I'll be back here if it doesn't rectify the situation.
I see my first problem, stupid tutorial I used the first time said to put Odin in Repartition and F-Reboot. QBKing says only Autoreboot. Man I hate crappily done tutorials.
Just also noticed he mentions the yellow box and com/port number are vital to the success of the root, something I overlooked all 3 times I tried it.
Stuck at the stupid com box again, now it wont change at all and i'm not getting the added message either....
Downloaded the drivers for the phone he gave also and still nothing....tried 3 different USB cables like he suggested too and still stuck.
Think I might need to unroot or delete the other crap I installed before? I'm out of ideas.
pumpdatbass420 said:
Stuck at the stupid com box again, now it wont change at all and i'm not getting the added message either....
Downloaded the drivers for the phone he gave also and still nothing....tried 3 different USB cables like he suggested too and still stuck.
Think I might need to unroot or delete the other crap I installed before? I'm out of ideas.
Click to expand...
Click to collapse
ok try this from the beginning
1. reset phone factory reset via recovery ( hold power up - home - and power button ) simultaneously and once you see blue recovery text top left corner let all the buttons go. select factory reset and proceed with reboot.
2. press ##3424# and select pda and make sure you have MTP-ADB selected
3. try rooting your phone via ODIN
PS: if it does not work change step 2 under PDA setting to DM-MODEM-ADB then root and once rooted change it back to step MTP-ADB
let us know if this works for you
saj070 said:
ok try this from the beginning
1. reset phone factory reset via recovery ( hold power up - home - and power button ) simultaneously and once you see blue recovery text top left corner let all the buttons go. select factory reset and proceed with reboot.
2. press ##3424# and select pda and make sure you have MTP-ADB selected
3. try rooting your phone via ODIN
PS: if it does not work change step 2 under PDA setting to DM-MODEM-ADB then root and once rooted change it back to step MTP-ADB
let us know if this works for you
Click to expand...
Click to collapse
Step 2...am I doing this on the phone or in Odin? MTP-ADB as well?
pumpdatbass420 said:
Step 2...am I doing this on the phone or in Odin? MTP-ADB as well?
Click to expand...
Click to collapse
step 2 is open dialer on the phone - how else you going to press ##3424#
i thought that was a given sorry
It's cool, I ask just in case. While I do consider myself a bright individual, I do not know very much about newer cell phones or android (this is only my 2nd smart phone, before the Photon I had been using my Blackjack without net. That phone lasted forever!) And before the Photon had never modded any cell phone in any way save an extended battery.
pumpdatbass420 said:
It's cool, I ask just in case. While I do consider myself a bright individual, I do not know very much about newer cell phones or android (this is only my 2nd smart phone, before the Photon I had been using my Blackjack without net. That phone lasted forever!) And before the Photon had never modded any cell phone in any way save an extended battery.
Click to expand...
Click to collapse
no problem better be safe than sorry ')
let us know how it went.
It's aliiiiiiive
Ok so oddly enough, after I performed steps 1 & 2, when I rebooted my phone I notice SuperSU was in my apps list. So for $#*^$ and giggles I downloaded Root checker to test it out and sure enough it says device is rooted. Go figure.
Thanks so much for your help guys, my girlfriend was starting to worry about me out here smashing keys and grunting like an animal trying to get this to work. :highfive:
pumpdatbass420 said:
Hello everyone! My names Danny, sorry I'm extremely frustrated at the moment and apologize for not introducing myself properly in what ever you call your newcomer section here, but I'm ripping my hair out at the moment.
So last night for the 4th time I tried to root my Galaxy S4, again unsuccessfully. While I admit I am no programmer, computer whiz, or rocket scientist, I have previously rooted my old S3 and my girlfriend's Moto Photon successfully in the past, on the 1st try (although they were pretty simple 1 click roots no more difficult than the one I used here, or so I thought.) Now last night I tried to use the CF-Autoroot again for the 3rd time, which i figured after the first 2 attempts was doomed to failure also. This may be due to the fact that I updated it, but I don't know. I'm hoping someone here can point me in the direction of a root that will work with my phone, show me where I may have went wrong in the install,or give some instruction on how to delete the update so I can use the CF-Autoroot. As long as my phone will still function as normal, I could care less which option is used, however I do not have any programming experience whatsoever, so a simpler root would be excellent. I'll give you all the info I can below.
Software version: L720VPUAMF9
Hardware version: L720.08
Model #: SPH-L720
Android version: 4.2.2
Baseband version: L720PUAMF9
Kernal version: 3.4.0-953334
[email protected] # 1
Tue Jun 25 09:36:29 KST 2013
Build #: JDQ39.L720VPUAMF9
SE Linux Status: Permissive
Secure boot status: Type: Samsung
Device Status: Custom (No Triangle Away quite yet, as I'm not sure if it is yet supported on the S4, or if I even need it since I plan on keeping the phone)
Root was done on HP Windows 7 laptop 64-bit, with the phone in camera mode prior to turning off and going into download mode.
I followed the instructions on honai-android.blogspot(dotcom) using CF-Autoroot and Odin V3.07 to the T, except I have yet to get the drivers to install correctly (or so it tells me, everything works fine,) and in Step 4 it says the box should turn yellow and a port number displays, but in my case did not. It did display the "Added" message in the little box like it should have, but it did go through the whole process and I got a PASS notification as it says I should have. I have no idea why it won't work, other than maybe the drivers are screwing me. Ran Root Checker and it tells me "Please wait for Root Check to complete. System appears to be running very slow," and Titanium Backup won't work either. Root checker stayed like this all night last night while I slept.
Also I would appreciate some help reverting it back from the root I apparently didn't install, although I know some of it went through, or Root Checker would just say I didn't have superuser access.
I'm hoping one of you guys here might be able to help me out with this problem, and I greatly appreciate any help I can get. If anymore information is needed, just ask. Much thanks in advance.
Click to expand...
Click to collapse
try doomlord easy root
Thanks for the tip but I already got it rooted. Just took a few more steps than I thought due to some overlooked details with the initial install.
New problem!
Trying to get QBKings Native Hotspot mod to work and it wont let me transfer services.odex to the system folder but services.jar is transferring fine? Any ideas? I'm baffled here yet again. Tried 3 different root browsers but JUST services.odex wont transfer!!!!!
Sorry for joining late, but how are you transferring the file? ADB, SD?
Last night I’ve replaced my spare GS4 i337 AT&T (US) stock ROM with Hyperdrive RLS17.1 KitKat (http://forum.xda-developers.com/showthread.php?t=2520418).
Evidently the device was rooted and Safestrap installed. The Hyperdrive install went smooth and the phone booted properly, with poorer signal reception than usual, but with wi-fi. I also installed the AT&T Module (http://forum.xda-developers.com/showthread.php?t=2616221). I’ve used my SIM card and was able to make at least one phone calls without changing any settings.
However, when I look at the About Device, I see that “Model Number” is SCH-I545 (while it should have been I337), but the “Baseband Version” correctly reads I337UCUFNB1.
Now I’m planning to do the upgrade to my main (also S4) phone, but should I be concerned about the Model Number being wrong? Or is this a developer oversight? Did I missed a step (like replace Kernel)?
Did anyone else had this problem?
Thanks in advance
tsaxman said:
Last night I’ve replaced my spare GS4 i337 AT&T (US) stock ROM with Hyperdrive RLS17.1 KitKat (http://forum.xda-developers.com/showthread.php?t=2520418).
Evidently the device was rooted and Safestrap installed. The Hyperdrive install went smooth and the phone booted properly, with poorer signal reception than usual, but with wi-fi. I also installed the AT&T Module (http://forum.xda-developers.com/showthread.php?t=2616221). I’ve used my SIM card and was able to make at least one phone calls without changing any settings.
However, when I look at the About Device, I see that “Model Number” is SCH-I545 (while it should have been I337), but the “Baseband Version” correctly reads I337UCUFNB1.
Now I’m planning to do the upgrade to my main (also S4) phone, but should I be concerned about the Model Number being wrong? Or is this a developer oversight? Did I missed a step (like replace Kernel)?
Did anyone else had this problem?
Thanks in advance
Click to expand...
Click to collapse
That ROM usually has multiple device / carrier options in Aroma. You probably chose Verizon instead of AT&T, or as you suggested, the dev made an error on the build.prop.
Either way, nothing to worry about as long as the device is working properly.
upndwn4par said:
That ROM usually has multiple device / carrier options in Aroma. You probably chose Verizon instead of AT&T, or as you suggested, the dev made an error on the build.prop.
Either way, nothing to worry about as long as the device is working properly.
Click to expand...
Click to collapse
Thanks upndwn4par!!!
Yes, I made the correct AT&T carrier choice, in Aroma. I also made sure the Module file matched the NBI file.
Will keep on going and will report if anything is not working as expected.
Once again, thanks for the replay.
Cheers :good:
tsaxman said:
Thanks upndwn4par!!!
Yes, I made the correct AT&T carrier choice, in Aroma. I also made sure the Module file matched the NBI file.
Will keep on going and will report if anything is not working as expected.
Once again, thanks for the replay.
Cheers :good:
Click to expand...
Click to collapse
My experience is that without the proper I337 configuration, certain apps wouldn't install from Google Play. This included some expected issues, such as ATT apps (like ATT Messaging app) that would be expected to be specific to ATT supported phone models, but also lots of other apps just wouldn't show up in the store when I browsed on the phone that identified itself wrongly as a Verizon phone. Sort of random hit or miss.
You can restore the identification of the phone by flashing the ATT build.prop/APN file, but that somehow interferes with hyperdrive tweaks app.
The dev has said build 18 should work better for ATT phones... if so, it would be awesome. He put an incredible amount of effort into this ROM. I had to leave it due to the "+" addition messing up incoming/outgoing calls, plus the phone model ID issue. Prefixer app apparently can fix for some the + issue, but I never found enough details to properly edit the build.prop to identify the phone for google play. However, I was in a hurry and didn't have a lot of time to mess with it.
I look forward to investigating version 18 when it comes out.
Marc
upndwn4par said:
That ROM usually has multiple device / carrier options in Aroma. You probably chose Verizon instead of AT&T, or as you suggested, the dev made an error on the build.prop.
Either way, nothing to worry about as long as the device is working properly.
Click to expand...
Click to collapse
Frankenscript said:
My experience is that without the proper I337 configuration, certain apps wouldn't install from Google Play. This included some expected issues, such as ATT apps (like ATT Messaging app) that would be expected to be specific to ATT supported phone models, but also lots of other apps just wouldn't show up in the store when I browsed on the phone that identified itself wrongly as a Verizon phone. Sort of random hit or miss.
You can restore the identification of the phone by flashing the ATT build.prop/APN file, but that somehow interferes with hyperdrive tweaks app.
The dev has said build 18 should work better for ATT phones... if so, it would be awesome. He put an incredible amount of effort into this ROM. I had to leave it due to the "+" addition messing up incoming/outgoing calls, plus the phone model ID issue. Prefixer app apparently can fix for some the + issue, but I never found enough details to properly edit the build.prop to identify the phone for google play. However, I was in a hurry and didn't have a lot of time to mess with it.
I look forward to investigating version 18 when it comes out.
Marc
Click to expand...
Click to collapse
Thanks for the information, Marc. But the link is dead!!!:crying:
After reading some more about this problem, I've decided to try a few more things. The first one was the most basic: Restart the phone! And guess what? It got stuck on the Samsung logo screen for a long time. After 30 minutes starring at the swirling logo I got dizzy and decided to restart it again. Same thing happen, over and over again
After some [yet] more reading, I've decided to reflash (see steps below) the Hyperdrive ROM again, but got stuck on the Samsung logo screen for over 30 min. Back to reading some more, and at this time I've reflash the GE (GoldenEye) ROM. Same result: got stuck on the Samsung logo screen!!
Any advices?
These are the steps I'm doing:
(Root steps were done only once, when the phone was stock)
1 - ROOT:
Note: Good video (just skip the step to set Permissive - see easier approach on #1.4) -http://youtu.be/2bDe_-mB7Rw
1.1 - Root with towel root (https://towelroot.com/)
1.2 - Install SuperSU (PlayStore) and let it disable Knox.
1.3 - Install BusyBox (PlayStore) and let it cook
1.4 - Install SELinux Mode Changer (PlayStore). Run and set it to Permissive.
1.5 - Install Safestrap (http://forum.xda-developers.com/showthread.php?p=45693712)
2 - Replace/Install Hyperdrive ROM
2.1 - Flash Hyperdrive (http://forum.xda-developers.com/showthread.php?t=2520418)
2.2 - Flash SuperSU.zip file. (http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip)
2.3 - Flash NB1 modem zip file (http://forum.xda-developers.com/showpost.php?p=46762296&postcount=1).
2.4 - Flash I337 Build.prop/APN (http://forum.xda-developers.com/showpost.php?p=51112381&postcount=9)
3 - Replace/Install GoldenEye ROM
3.1 - Flash Goldeneye (http://forum.xda-developers.com/showthread.php?t=2313469)
3.2 - Flash SuperSU.zip file. (http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip)
3.3 - Flash NB1 modem zip file (http://forum.xda-developers.com/showpost.php?p=46762296&postcount=1).
3.4 - Flash I337 Build.prop/APN (http://forum.xda-developers.com/showpost.php?p=51112381&postcount=9)
I've also followed these steps http://forum.xda-developers.com/showthread.php?t=2313469&highlight=stuck+on+boot&page=151), but still the same issue:
if ur device gets stuck after flash at att boot animations for a long time .. dont freak out .. do this
1. hold power till device is off or remove battery then put in back in after 30 secs
2. hold power and vol up til u see blue text top left of screen, now let go of buttons
3. choose wipe factory reset
4. wipe cache for the hell of it
5. choose reboot system
Click to expand...
Click to collapse
Which link was dead?
I've seen in the past month several posts of problems of people with NB1, so I recommend starting over via ODIN to Stock NB1, flash to NC1, then re root / safestrap and try the rom again. Also, when you flash the ROMs in safestrap, were you wiping system/cache/dalvik etc.. first?
Marc
Frankenscript said:
Which link was dead?
I've seen in the past month several posts of problems of people with NB1, so I recommend starting over via ODIN to Stock NB1, flash to NC1, then re root / safestrap and try the rom again. Also, when you flash the ROMs in safestrap, were you wiping system/cache/dalvik etc.. first?
Marc
Click to expand...
Click to collapse
Mark,
The link you posted initially
You can restore the identification of the phone by flashing the ATT build.prop/APN file, but that somehow interferes with hyperdrive tweaks app.c
Click to expand...
Click to collapse
Yikes, I was fearing not go the ODIN route (or root? :silly. Does anyone know where I can get ODIN and the NB1 and NC1 stock? (I'm not being lazy and will search for it. I just want to make sure I'm getting the right files)
I still don't understand why did the phone booted, setup, and I was able to make a call and then simply failed to reboot? Do you believe that maybe the Build.prop/APN was broken? what happened if it was not installed?
Thanks.
T.
Mark,
I've realized the 'broken link' problem. I've copy/paste the text Build.prop/APN and noticed that it has a URL property "Link added by VigLink', which points to nowhere.
tsaxman said:
Mark,
I've realized the 'broken link' problem. I've copy/paste the text Build.prop/APN and noticed that it has a URL property "Link added by VigLink', which points to nowhere.
Click to expand...
Click to collapse
Oops. Not sure where the viglink thing came from. Here's the download page for the build.prop file:
http://d-h.st/6tN
Links to ODIN stuff including NB1 ODIN-flashable file and NC1 update (flashed from stock recovery after NB1 return to stock is done) are found in the all things ATT thread:
http://forum.xda-developers.com/showthread.php?t=2616221
See post 1, the Returning to Stock / ODIN section.
FWIW, I always use the stock NB1 (not the rootable NB1 variant) then flash the NC1 update. I had one bad experience with the rootable NB1 (couldn't get wifi to work after ROM flash), and never quite figured out why. Doing NB1-NC1 only takes a few extra minutes, so I stick with that.
Marc
Frankenscript said:
Oops. Not sure where the viglink thing came from. Here's the download page for the build.prop file:
http://d-h.st/6tN
Links to ODIN stuff including NB1 ODIN-flashable file and NC1 update (flashed from stock recovery after NB1 return to stock is done) are found in the all things ATT thread:
http://forum.xda-developers.com/showthread.php?t=2616221
See post 1, the Returning to Stock / ODIN section.
FWIW, I always use the stock NB1 (not the rootable NB1 variant) then flash the NC1 update. I had one bad experience with the rootable NB1 (couldn't get wifi to work after ROM flash), and never quite figured out why. Doing NB1-NC1 only takes a few extra minutes, so I stick with that.
Marc
Click to expand...
Click to collapse
Thanks a million, man. Downloading and trying that now.
BTW, other than I should have done NB1 to NC1 prior to install the ROM and since you've already done all this (on GE 36, right?), are the steps I've outline correct?
By now with some luck you are on GoldenEye, but yeah, the steps you outlined are correct.
1. Get to NC1 stock.
2. Root / SuperSU / SeLinuxModeChanger (sometimes needed sometimes not) / SafeStrap
3. In safestrap: advance wipe everything but SD card then: Golden Eye / SuperSU / NC1 module / ATT APNw/Build.Prop
Should be golden. Let us know how it went!
Frankenscript said:
By now with some luck you are on GoldenEye, but yeah, the steps you outlined are correct.
1. Get to NC1 stock.
2. Root / SuperSU / SeLinuxModeChanger (sometimes needed sometimes not) / SafeStrap
3. In safestrap: advance wipe everything but SD card then: Golden Eye / SuperSU / NC1 module / ATT APNw/Build.Prop
Should be golden. Let us know how it went!
Click to expand...
Click to collapse
Marc,
I am up and running. Lot's of work, but everything seems to be working in order now. Loving the debloated GoldenEye.
Just one more thing: The Build Number now reads: Venomous-Droid v1
Is that right? Shouldn't it say something like GoldenEye?
Maybe I should stop looking at the Build Number from now on, but I can't resist :cyclops:
Again, thanks for the help man. Forever grateful :good:
tsaxman said:
Marc,
I am up and running. Lot's of work, but everything seems to be working in order now. Loving the debloated GoldenEye.
Just one more thing: The Build Number now reads: Venomous-Droid v1
Is that right? Shouldn't it say something like GoldenEye?
Maybe I should stop looking at the Build Number from now on, but I can't resist :cyclops:
Again, thanks for the help man. Forever grateful :good:
Click to expand...
Click to collapse
Glad it's working out. Hit thanks if I helped. (EDIT: Just noticed you did! :good: )My build also shows venomous. My guess has been that our GoldenEye dev used some pieces of Deadly Venom, and acknowledges it via this method, but I don't know for sure. The important thing is that as far as Google Play is concerned, our device is an I337.
I presume Wifi is working for you? I was chatting with another user similar to us earlier this week, and going through the steps he had trouble getting wifi working, even after flashing the modules and everything. Not sure what caused it but glad you seem to be up and running.
In other news, I've just bought a phone on Swappa, a T-Mobile version of the S4, sim unlocked (so should work fine with ATT), and the T-Mobile phones come with unlocked boot loader. So, as long as I don't care about knox, I can install full recoveries and play with different kernels and such. I'll get the phone in-hand next week. After checking it out, it's bye-bye locked boot loader.
HAve fun with Golden Eye. It's been rock steady for me.
Frankenscript said:
Glad it's working out. Hit thanks if I helped. (EDIT: Just noticed you did! :good: )My build also shows venomous. My guess has been that our GoldenEye dev used some pieces of Deadly Venom, and acknowledges it via this method, but I don't know for sure. The important thing is that as far as Google Play is concerned, our device is an I337.
I presume Wifi is working for you? I was chatting with another user similar to us earlier this week, and going through the steps he had trouble getting wifi working, even after flashing the modules and everything. Not sure what caused it but glad you seem to be up and running.
In other news, I've just bought a phone on Swappa, a T-Mobile version of the S4, sim unlocked (so should work fine with ATT), and the T-Mobile phones come with unlocked boot loader. So, as long as I don't care about knox, I can install full recoveries and play with different kernels and such. I'll get the phone in-hand next week. After checking it out, it's bye-bye locked boot loader.
HAve fun with Golden Eye. It's been rock steady for me.
Click to expand...
Click to collapse
Yes, Wifi is working fine. I'll continue testing over this weekend and will report back Monday.
Seems like you're reading my mind. I'm just looking into the Unlock Sim threads and found this... http://forum.xda-developers.com/showpost.php?p=54772758&postcount=286, which points to the Saferoot thread/download http://forum.xda-developers.com/showthread.php?t=2565758.
The important part (at least to me) was the comments..
2. Resetting the "Custom" and open padlock indication during boot can be worked around using the Xposed Framwork and Wanam Xposed. Get those two from the Play Store. In Wanam, tick "Security Hacks", "Fake System Status".
Click to expand...
Click to collapse
I don't know much about Wanam or Xposed, but do you think these can unlock the SIM on just trick the system at a higher lever (as indicated) for some other reasons?
Oh, the last link on the page points to file to NC1 users
Method 3 (For those on NC1 or higher) @NewToGalaxy
Link for the files needed:
https://www.dropbox.com/s/16fu4havwvbt59c/NC1unlock.zip
Click to expand...
Click to collapse
tsaxman said:
Yes, Wifi is working fine. I'll continue testing over this weekend and will report back Monday.
Seems like you're reading my mind. I'm just looking into the Unlock Sim threads and found this... http://forum.xda-developers.com/showpost.php?p=54772758&postcount=286, which points to the Saferoot thread/download http://forum.xda-developers.com/showthread.php?t=2565758.
The important part (at least to me) was the comments..
I don't know much about Wanam or Xposed, but do you think these can unlock the SIM on just trick the system at a higher lever (as indicated) for some other reasons?
Oh, the last link on the page points to file to NC1 users
Click to expand...
Click to collapse
I bought a factory-unlocked one from Swappa. No need to fuss with SIM unlocking :laugh: :good: