Ever since the Gingerbread update my phone has had a noticable amount of lag. This occurs between screens, apps, button presses and even typing. Sometimes it wont do anything for a couple of seconds and then type the whole word I was trying to type.
I have also noticed a very long boot time when I power it off and back on. Takes several minutes...
My phone is rooted with Gingerblur.
Any ideas of what I can do to fix this?
1)Unlock bootloader
2)Flash a diff non-doodoo ROM, there are plenty of them
3)??????
4)Profit
Sent from my MB860 using XDA App
kisnerct said:
1)Unlock bootloader
2)Flash a diff non-doodoo ROM, there are plenty of them
3)??????
4)Profit
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Thank you for the response : )
Number 3? Not sure what you mean on that one....
Is this a common problem? Does anybody else recommend to do what was mentioned above?
Exchange before warreny is void
Tenacious--M said:
Thank you for the response : )
Number 3? Not sure what you mean on that one....
Is this a common problem? Does anybody else recommend to do what was mentioned above?
Click to expand...
Click to collapse
#3 is did it fix your problem. The answer will be no its not going to. I work for at&t and have sold this phone with the update and it is a reported problem. My suggestion flash the stock gingerbread sbf and exchange with a device support center near you.
[email protected] said:
#3 is did it fix your problem. The answer will be no its not going to. I work for at&t and have sold this phone with the update and it is a reported problem. My suggestion flash the stock gingerbread sbf and exchange with a device support center near you.
Click to expand...
Click to collapse
I bought this phone from at&t WITH the update and had 0 problem unlocking rooting flashing etc. I haven't even had a single experience with lag yet. Doodoo Motoblur is the source of the lag.
Sent from my Atrix 4g (MB860) using XDA app.
I hate doodoo
Wtf is WP7
Funny, I just left At&t for work : )
I noticed the Atrix phones coming with the Gingerbread have had a big percentage of glitches out of the box. Ive had a few even reluctant to do a full boot.
I got mine before Ginger with Froyo.
What is recommended? Its a shame as 2.2 worked fantastic! I like the idea of being able to update the software when the patches come out. You guys arent even messing with the Moto 2.3 update then? Just going to custom roms?
Tenacious--M said:
Funny, I just left At&t for work : )
I noticed the Atrix phones coming with the Gingerbread have had a big percentage of glitches out of the box. Ive had a few even reluctant to do a full boot.
I got mine before Ginger with Froyo.
What is recommended? Its a shame as 2.2 worked fantastic! I like the idea of being able to update the software when the patches come out. You guys arent even messing with the Moto 2.3 update then? Just going to custom roms?
Click to expand...
Click to collapse
I'll just share my experience with you.
Whenever I get a new phone I'm not quick to root/flash etc. as I like to play around with it to be sure I really want to flash it. Plus, this was my first experience with motoblur so I wanted to give it a shot.
This phone was garbage IMO without a ROM. So much worthless bloat and a LOT of lag problems. The speed of this phone (for it's hardware) was extremely disappointing and I was seriously regretting my purchase. I was coming from a captivate, so to say I was disappointed (which coming from that phone) is huge. Lag between screens, god-awful boot up times, and confusing motoblur had me ready to return this and wait for something else. That being said, decided to give the ROMs a chance. I was coming from the latest software and I don't know if I just got lucky but I had 0 problems rooting, unlocking, and flashing....a lot less problems than I had with my captivate. Went with cm7 and haven't looked back. Aside from a few relatively minor bugs with cm7 (which WILL be fixed), I am now extremely pleases with this phone...I guess the better term would be in love with it. Its blazing fast, good battery life, and just feels smooth all-around.
It really a shame that we have to go through these kind of hoops to unleash the phones potential...so many users that will never know how great of a phone they have.
Sent from my Atrix 4g (MB860) using XDA app.
Make a nandroid
Unlock your bootloader
flash cm7
I PROMISE you won't regret it!!
I've been using Android for a while now & the only competition that cm has is miui (and that isn't even available yet)
Tenacious--M said:
Funny, I just left At&t for work : )
I noticed the Atrix phones coming with the Gingerbread have had a big percentage of glitches out of the box. Ive had a few even reluctant to do a full boot.
I got mine before Ginger with Froyo.
What is recommended? Its a shame as 2.2 worked fantastic! I like the idea of being able to update the software when the patches come out. You guys arent even messing with the Moto 2.3 update then? Just going to custom roms?
Click to expand...
Click to collapse
i got my first phone from AT&T and bricked it unfortunately, went back into the AT&T store and explained my situation to the rep and asked how much it would be to replace it, but he gave me a new one free of charge.
after i got my second one, i updated it to GB right away and was satisfied with the phone, the AT&T rep played with it showing me all sorts of things about Android since it's my first Android phone. after about 30 minutes of showing me all sorts of cool things i could do with it, he said he was confident that the phone was bug free so i walked out of the store and updated it right there. i noticed a lag increase with gingerbread that wasn't there in his froyo presentation, which was kind of disappointing. after i got home and rooted my phone though, i was able to tweak things and get the ball rolling, only slight lag on certain transitions and games. (still disappointing with these specs though)
shortly after, i unlocked the bootloader and flashed ninja speed freak, which cleared up almost all my lag problems. i didn't experience any real lag in transitions, but every once in a while i'd get slight lag in games.
then CM7 came out, and i installed it, and i'm experiencing 10-15 second boot screen times, compared to multiple minute boot times on stock. no lag with any animation or game i've played so far, great quality videos and extremely satisfied all around. the different without motoblur is extremely noticeable. i can't wait for it to be finished so all our wonderful devs can go back to their own little side projects, and we can see what this phone is really capable of
Flash a newer Rom.
If you like the blur features use homebase.
Cm7 is GREAT! But not If you like blur.
Alien rom was my favorite rom till cm7 tho.
You wont regret flashing eaither of those.
Sent from my CM860
tenacious--m said:
ever since the gingerbread update my phone has had a noticable amount of lag. This occurs between screens, apps, button presses and even typing. Sometimes it wont do anything for a couple of seconds and then type the whole word i was trying to type.
I have also noticed a very long boot time when i power it off and back on. Takes several minutes...
My phone is rooted with gingerblur.
Any ideas of what i can do to fix this?
Click to expand...
Click to collapse
cyanogenmod 7!
read op wrong fist post
Cm7 is the answer
I gave thanks to all of you! I very much appreciate the feedback. CM7 is what I have been researching as well and it sounds like the bomb!
However, I am really spinning my wheels here on getting the bootloader unlocked. Getting CM7 on there is not hard at all. Ive done that kind of stuff before on other phones, but Im not getting sucess on the bootloader.
Im running 2.3.4 if that makes any difference and am rooted.
When I attempt to unlock the bootloader I get a message on cmd saying "oem unlock is not implemented"
Can one of you guys/gals gently walk me through unlocking this guy? Maybe Im missing one little thing? I have spend two days researching and trying the different methods and keep coming up against this wall.
Thank you so much in advance! : )
I am on stock GB and experienced a little lag. But after I installed SGS TOUCHSCREEN BOOSTER and bought ADW EX I've never had a problem. When I used Zedge to download wallpapers my Atrix crashed and rebooted. So uninstalled that and I'm good again.
Stock Motorola Atrix 4G
Tenacious--M said:
When I attempt to unlock the bootloader I get a message on cmd saying "oem unlock is not implemented"
Can one of you guys/gals gently walk me through unlocking this guy? Maybe Im missing one little thing? I have spend two days researching and trying the different methods and keep coming up against this wall.
Thank you so much in advance! : )
Click to expand...
Click to collapse
It would help if we knew what method you were using to try and unlock .
Sent from my MB860 using XDA App
Sorry... : )
Ive tried this version. Automatic unlocker
http://forum.xda-developers.com/showthread.php?t=1182871
Ive tried the BriefMobile version
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader]
And I tried the IHOP Pudding
http://forum.xda-developers.com/showthread.php?t=1136261
Ive flashed ROMs on several phones, made nandroid backups etc... I just dont have alot of experience with cmd or bootloader unlocking. I tried over and over and did the instructions to the letter, unless Im missing something. Being new, Im sure im missing something small.
Ok, finally! I got it done and flashed to CM7. WOW! I love it!
I did notice some differences so I will post my experience here. I will highlight the differences I found that worked for my 2.3.4 Rooted Atrix. Maybe it will help other newbs like me : )
By the way, credit to BriefMobile and the2dcour for the original guide
***I marked the differences I noticed when unlocking my 2.3.4 unlocked At&t Gingerbread***
How To: Unlock the Atrix 4G Bootloader
Prerequisites
• Backed up /data partition
You will lose all of your /data during this process!
• Unlock SBF file [Mirror]
• RSD Lite 5.3.1 or sbf_flash [Download if Atrix is Froyo]
• Fastboot package [Mirror]
Also found in the Android SDK tools folder
Instructions
1. If you’re on Gingerbread, skip to step 13. (I was on 2.3.4 Gingerbread and I also had to do all the steps. Dont skip!!!)
2. Power down your Motorola Atrix
3. Take out your microSD card and SIM card for the flashing process
4. While turning the phone on, hold the Volume Up button until it acknowledges RSD
5. Your device will say “Starting RSD protocol support”
6. Run “RSD Lite” on your computer
7. Press the “. . .” button next to the box labeled “Filename”
8. Load up the SBF file
The SBF file is located inside of the .zip file, you must extract it out before loading it into RSD Lite
Use WinRAR or 7-Zip to extract the .zip file on your computer
9. Plug your device into your computer
Use the USB ports on the back side of your computer for safety
10. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…” (Mine said SE Flash Olympus, not NS)
11. Press the “Start” button
12. Be patient while the phone reboots. It will take a long time. (Phone didn’t reboot. It went to a menu and said “5 seconds to select Fastboot”. You have to use Vol down to move in the menu and the Vol up button to select “Fastboot”)
13. Open and extract the Fastboot package from above
14. Open a command prompt window
On Windows, press Start and type “cmd” then press the enter button
15. Type the following command. Your directory will be the folder where you extracted the Fastboot package.
(Example: cd C:\Users\Kenneth\Desktop\fastboot-package) (I extracted mine to the C:\ drive. Then you don’t have to type so much. Just cd C:\fastboot )
cd your directory here
16. Power down your Atrix device
17. Hold the power button and the downward volume button until you see “Fastboot”
18. Let go of the buttons and press the upward volume button once
19. You will now see “Starting Fastboot protocol support”
20. Plug your device into a USB port in the back slot of your computer
Front slots sometimes do not have enough power to stay connected to the device.
21. Type the following command:
fastboot oem unlock
22. You will now receive a warning along with a unique device ID
23. Type the following commands using your unique device ID in place of the ####:
fastboot oem unlock ####
fastboot reboot
24. Wait for your device to reboot. Congratulations! You now have an unlocked bootloader! (Mine said “unlocked” in upper left hand corner, but didn’t reboot. I pulled the battery and restarted. Been working fantastic ever since!)
Source: the2dcour
Related
I'm in a bit of a panic and think I need help.
I bought the HTC Hero from Bestbuy roughly Nov. 2009. And like everyone else love it, but was frustrated with all the bugs and slowness, lag ext. Reading and waiting for 2.1, getting impatient weekly...blah blah blah....but horrified to try to root the phone, because im not the techiest guy in the world, so when I saw that there was a 2.1 leak that I could just click from my computer, I did it like an impatient child.
RUU_Hero_C_Sprint_2206511_signed_test.exe
and have had a major problem ever since. The phone will shut off if its not plugged in. I have to constantly turn it back on and wait for it to reboot.
So I followed "How-To repair your bootloader after using the 2.1 RUU" to the T! With no error messages and got it back to "stock" which still looked like 2.1 to me. I formated the SD card from the phone, did a full wipe in that black/green boot page and flashed Beezy's "option 4",
I believe I did a nanbackup right before the "option 4". But I don't think it matters, since the phone was shutting down before that anyway.
So that's where I am. If I'm messing around with the phone (on a call, web, playing with apps) it will stay on, but as soon as I set it down and the screen goes to sleep, thats it, when I pick it up and hit the menu or power button, it reboots (white screen, HTC logo). Am I F'ed? I do have insurance through sprint, but believe that is void now, since I stated messing around with it.
I swapped Batteries with my wife's phone and it still happend, so it's not a bad battery.
I'm sorry if I posted in the wrong forum. I did a search for "constant rebooting" and couldn't find anything similar to my problem.
Thanks in advance.
If all you see is the white htc screen you probably aren't actually rebooting just rosie is restarting. Probably because the ruu doesn't work too well on its own. I suggest you just take the plunge and root, wipe, and flash fresh 2.0d or damage 2.07.2 ( your choice really, both are excellent roms)
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
Well, first off it doesn't sound like you are rebooting, it sounds like sense might just be restarting.
Also, don't panic. Whatever you have done is fixable
surely someone who is not posting from their phone will be along to help soon, if not I'll be back home and on my pc in a few hours
Just to confirm
Can you go into settings > about phone > software information (1.5 maybe slightly different I can't remember any more) and tell us what Firmware version says? this way we can make sure that you are running the appropriate version to RUU back to 1.5 and reroot.
I am not sure exactly what is still on your phone.
Also have you ever flashed a radio update from flipz?
I agree, that it isn't rebooting, but its the sense crashing and restarting. I would also agree, that your best option would be to root.
Honestly, the guides are laid out as plain as they could be. It isn't that difficult, you just have to check and re-check typed commands, if done manually.
I think you will be pleasantly surprised and find it simpler than you think.
However, ALWAYS make sure to do to the following:
1. nandroid before you do anything.
2. NEVER EVER NEVER EVER touch anything that doesn't say CDMA HERO. (gsm hero radio flashes can literally fry your nice phone into a nice paperweight)
3. Don't be afraid to ask questions here. I'm pretty new to this, but there are a lot of cool helpful people.
4. nandroid again. (copy nandroids to your PC/Mac and keep a whole library of them.) I even have some extra google space that I've been uploading them to incase I'm not at my computer and I need one...lol)
5. Don't get too sucked into it.
Thank you guys for responding, as I was worried I would get flamed for being an idiot for doing what I did.
"I suggest you just take the plunge and root, wipe, and flash fresh 2.0d or damage 2.07.2 ( your choice really, both are excellent roms) "
Isn't "How-To repair your bootloader after using the 2.1 RUU" basically rooting the phone? Because after I follow those instructions, I get the the recovery menu. I just haven't tried Damage roms yes.
Also, "Well, first off it doesn't sound like you are rebooting, it sounds like sense might just be restarting."
Looks like a full boot...
HTC Logo white screen, green text
HTC Quietly Brilliant
Sparkly Sprint thing
HTC Quietly Brilliant
Lock Screen
Loading apps
I should mention that I have been testing things like, Turning off "Screen Timeout" completely, 10 mins, 1 min, 30 seconds...ext. And it still shuts down after a few minutes when the screen is off......HOWEVER, it is random as far as how long it has been sitting.....Sometimes the screen will be black for a minute and when I hit the menu or power it will reboot....sometimes it will sit for 10 mins and will turn on.....very random, but it WILL reboot eventually.
Thanks again, guys
Chaid said:
Looks like a full boot...
HTC Logo white screen, green text
HTC Quietly Brilliant
Sparkly Sprint thing
HTC Quietly Brilliant
Lock Screen
Loading apps
Click to expand...
Click to collapse
Do you see the first black HTC screen? I know I've done the HTC quietly brilliant screen, but then it goes right to lock screen and loading apps.
I still don't think it is a full reboot, but I'm not THAT up to speed with most of this stuff.
Also, RUU'ing back to stock, then rooting and installing a 2.1 rom by Damagless or Flips should be your best bet.
RUUing back to stock has some problems in and of itself, but it should go ok.
Chaid said:
Looks like a full boot...
HTC Logo white screen, green text
HTC Quietly Brilliant
Sparkly Sprint thing
HTC Quietly Brilliant
Lock Screen
Loading apps
Click to expand...
Click to collapse
Weird...
Regardless, this is fixable.
As Kcarpenter asked, post your system info if you can get to it.
What is your:
Firmware
Baseband
Kernel
Build
Software Number
PRI
PRL
Firmware: 2.1 -update1
Baseband: 2.42.00.03.10
Kernel: 2.6.29-d30020a8
[email protected] #1
Build: 2.20.651.1 CL157175 test-keys
Software Number: 2.20.651.1
PRI: 2.10_003
PRL: 60664
Chaid said:
Looks like a full boot...
HTC Logo white screen, green text
HTC Quietly Brilliant
Sparkly Sprint thing
HTC Quietly Brilliant
Lock Screen
Loading apps
Thanks again, guys
Click to expand...
Click to collapse
Sounds like you are using a 2.1 rom not the stock 1.5
I would try using this guide http://forum.xda-developers.com/showthread.php?t=608434 to correct your issues it will take you back to stock 1.56.651.2 that come with the phone
Oh and if you get any errors this will help too http://forum.xda-developers.com/showthread.php?t=654119
Guys, since he used the 2.1 RUU, isn't he only able to use the 2.1 RUU now? Not the 1.5?
I too am experiencing this.
Factory reset my phone and then flashed from 1.6 to 2.1. I have tried two different 2.1 roms (the sprint leak one and Freshrom) and both of them are causing spontaneous reboots of my phone. I never experienced reboots when on 1.6.
Software information:
2.1 fresh
baseband 1.04.01.09.21
Kernel is 2.6.29-d30020a8
build is fresh rom 2.0d
Software number is 2.20.651.1
PRI is flipz_01
PRL is 60660
any suggestions from anyone?
mrinehart93 said:
Guys, since he used the 2.1 RUU, isn't he only able to use the 2.1 RUU now? Not the 1.5?
Click to expand...
Click to collapse
I believe you are correct, although I have yet to use any RUU
OP, you really should just root the thing flash a rom and succumb to the new obsession you don't even know you have yet
Personally, I'm a fan of RegawMODv2.1, it's lean and stable.
I think that even though you have run 2.1 RUU we can take you back to a bone stock 2.1
When I get home tonight I will try to link to all of the appropriate guides to get you there.
Once we have you back at a stock 1.5 I think we can all say "ROOT IT!" but I would feel more comfortable knowing that you came from the begining in the right order of things.
And get you on a solid stable Rom. I have recently started having issues with my damage rom and all of the aps2sd stuff that has been going on. Not sure what I am going to move to next. But that's besides the point, and none of it is Damageless's fault.
Ok, Kcarpenter, I'll be waiting LOL. I have been f'ing with this thing for a few days now, reading different forums and searching and searching. I finally broke down and posted here, because I'm at a loss. So I REALLY appreciate you guys taking the time to help me. Plugging the phone into my work truck laptop and running to the house to plug it in is wearing me down...
You just need to get over the fear of f*ing up your phone and root it. I'm not sure where the treads are on everything you need, but it's pretty straight forward.
If you had rooted while still running 1.5 you probably would not be in this mess. And Flipz has Fresh Kitchen which makes it even easier to Root and put a recovery console on.
"If you had rooted while still running 1.5 you probably would not be in this mess." You are absolutely correct, &RoidRage. I got excited when I saw the word "Official" 2.1, and jumped the gun.
Chaid said:
"If you had rooted while still running 1.5 you probably would not be in this mess." You are absolutely correct, &RoidRage. I got excited when I saw the word "Official" 2.1, and jumped the gun.
Click to expand...
Click to collapse
That probably created lots of people to get excited.. Anyway, here is what I got
Okay first I looked here
http://forum.xda-developers.com/showthread.php?t=661057&page=6
Which directed me to
http://forum.xda-developers.com/showthread.php?p=6013606#post6013606<--------This is the one you really want.
If you get it to work then you can flash a custom rom. But make sure you download it and put it on the sdcard before doing anything else.
I know it says it is for the 110 error, but people have used it to get back to 1.5 from 2.1
Thanks, man. I'll give it a shot......I have nothing to loose at this point, so I'm over my fear of F'ing up the phone.
I would read everything first, I didn't have the time look it all over.
Editamn predictive text said wetting instead of everything.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
Tomorrow is my 46th birthday, and I have tried to stay on top of technological advancements as best possible given my busy schedule. What I have noticed is that my ability to digest the latest techno trends and techniques does have a limit, especially when it interferes with the approaching martini hour at afternoon's end!
I don't know if this is a question or a mid-life existential moment. I bought the Samsung Epic 4G last fall because it was supposed to be cutting edge in terms of hardware for Android, and I as many of you have expressed, I made the decision to buy the Epic because of the promised firmware update that was imminent.
Fast forward half a year, and I now have the 2.2.1 EB13 firmware, which is rooted. I received the SMS yesterday (Wednesday) afternoon from Sprint about Sprint ID coming, but no update. Since I am rooted on EB13 I have no idea whether or not I will ever get the OTA and the last time I tried ODIN I had to take a tranquilizer, so I have no desire to go back to 2.1 to get the OTA.
Will the EC05 OTA be appearing given rooting on EB13? EB13 is giving me problems. I loved moving many (most) apps over to SD (I have a 32 gig card). But WiFi is not good, and I lose the ability to play movies, audio files, visual voicemail, or even hear my phone ringer (all seem connected in terms of the error -- I get an "unable to play message" or "unable to open file" error). I have to turn the phone off completely, then back on, wait for the media scan, etc. for it to go back to normal, then the errors will come back. I was hoping that EC05 would fix this. Maybe not. In perusing and searching I see nobody else has reported these problems which did not exist on DI18 (although I do see reports of WiFi connectivity problems that appear similar).
Does anyone have a bag phone from 1988 they want to trade for my Epic? As I recall, it worked without any hassles or firmware updates. Although it didn't have Angry Birds...
UPDATE: Life is grand at 46 (almost!). I posted later the following URL:
hxxp://forum.androidcentral.com/epic-4g-rooting-roms-hacks/71389-odin-ec05-froyo-ec05-prerooted-cwm-v2-5-1-0-rfs-odexed.html#post761525
When I got home I did as instructed using ODIN, and now I have EC05, with root, no data erasure, all is well! I still see so much consternation going on in the other threads. If you go to this URL and follow the directions, it works without any issues. I noticed immediately my WiFi issues are issues of the past. You can either wait for Sprint/Google to OTA you, under certain limited conditions, or do this, and be whole. Your choice. JJP
There should be an ota coming for those on eb13. As long as you didn't remove any bloatware you should be able to install the update. Besides there might Even be an update.zip on here that you can use before you get the ota. And Odin isn't that bad. I know you worry that it might brick your phone but I've used it about 10 times so far and no problems here. As far as technology goes its developing extremely fast these days. Its hard to keep up with it. Good luck and if you have anymore questions or decide to Odin and need something don't hesitate to ask or even pm me. I answer really quick cause I have it send be an email when.I get a pm.
Sent From My Evo Killer!
Thank you, what a nice response. Hopefully an update.zip will appear for EB13. Stranger things have happened.
drplaud said:
Does anyone have a bag phone from 1988 they want to trade for my Epic? As I recall, it worked without any hassles or firmware updates. Although it didn't have Angry Birds...
Click to expand...
Click to collapse
Unfortunately, all the AMPS and Digital TDMA networks have long since been shut down, so it would do you no good
But I do have a bag phone haha
Sent from my SPH-D700 using XDA Premium App
I wish I was 18 again, but for other reasons.
Yeah it is hard to keep up with tech these days,it changes by the hour now. And Ill have to say that Android is fragmented,this makes it harder; Look at what 2 updates to 2.2.1 and a 2.2.1 leak has done to this Epic forum,it has become a mess,I just hope now that we have CM7 and probably the last update for atleast 6 months,we should start to see some serious progress.
Sent from my SPH-D700 using XDA Premium App
Odin is only a pain the first time around. Now that you have the proper drivers installed its just a matter of selecting the file and clicking the start button. The only thing you have to watch out for is finding the correct usb port that the driver was installed on. As long as you're plugged into the correct one you're golden.
I do not think I will receive the OTA as I used one click to root after installing EB13. Perhaps this is the time to go Bonsai as I understand it now has EC 05 built in. I apologize, but is there a primer on how specifically to go to Bonsai? I have never flashed before (as I thought I might be arrested). Thanks.
Sent from my Samsung Epic™ 4G
You mentioned you're rooted. Do you know if you have CWM3 installed?
Its all a little trial and error but once everything is properly installed flashing roms is a cinch. I'm a big fan of the ACS roms. Bonsai worked well on my phone but there were a handful of idiosyncracies present that I could not put up with. Of course YMMV but don't hesitate to try different roms until you find one that your phone works well with.
stir fry a lot said:
You mentioned you're rooted. Do you know if you have CWM3 installed?
Click to expand...
Click to collapse
I believe so. I used one click root (update.bat).
Sent from my Samsung Epic™ 4G
drplaud said:
I believe so. I used one click root (update.bat).
Sent from my Samsung Epic™ 4G
Click to expand...
Click to collapse
Cool. If you want to give EC05 a shot, go to this thread and download the modem.
http://forum.xda-developers.com/show....php?t=1003447
Insert the modem into the Phone section of odin and hit start
Put aside some time before proceeding. If you have the correct CWM installed it won't take more than ten minutes but play it safe.
Download a rom of your choice, plug your phone into your computer and place it in the root of your SD card. You can download multiple roms if you want to see which works best for you. You will lose all your data the first time installing any new rom as it is not really recommended that you transfer settings of apps between different roms. Once you find a rom your're happy with you can simply update it it with the newest version without having to wipe your data however. Its really not as bad as it sounds and the ACS rom comes with an excellent app recovery program called MyBackup Pro Root that you can backup your apps and data with. You can use it to transfer apps between different roms and even some data but data from different roms can sometimes give you problems and is not really recommended. I have transferred data with some apps without any problems however. Its really just data that is tied to the system itself that will probably give you problems.
Unplug your phone from your computer and long press the Power Button, select Reboot, and then quickly hold down the Power, Volume Down and Camera Buttons.
Now press and hold down the Power, Camera, and volume down buttons. It should boot to the samsung logo and then to a black screen with orange text on it.
Use the volume keys to navigate and the power button to make selections. Choose Wipe Data/Factory Reset and wipe it 3x, then do the same for the Cache Partition and Dalvik Cache which can be found in the advanced options.
Select Go Back and navigate to Install Zip from SD card. Choose the rom you downloaded to it and you're good to go.
If after you do the three finger boot and you're not brought to a black screen with orange text you will need to install the correct CWM. If its black with green you have an old version and if you get a different screen than that this means that you do not have CWM at all. If this is so, just navigate to reboot and press the Home key to select it.
Something to think about
Thank you for the very helpful responses. I will ponder what the best option is, but it may indeed be time to explore custom ROMS, and your responses have given me the courage to do so. Many thanks! Joe
If he doesn't have cwm3 then he's gonna have to run the one click root with cwm3 for eb13 to be able.to flash bonsai. If I were to guess he has cwm 2.5.1.0 installed. On another note HAPPY BIRTHDAY!!!!
Sent From My Evo Killer!
I would Odin to EC05 first and see if it fixes anything for you. If not, reboot your phone into CWM and if you have the correct (orange and black) version, just reboot load the ACS rom onto to your phone and give it a try. If you're not happy with it or even if you are make a backup with Mybackup Root and explore other roms until you find one that works for you.
If you make a backup I would advise making separate backups of your apks, data for your apks, and photos as it makes it much faster to get back to where you were originally. Another tip for my backup is after making one go to View and double check that it actually made one as sometimes it will not.
I would have thrown this phone away by now if it weren't for the ACS rom btw. Its much smoother, has better battery life, doesn't skip keys even without the patch that they will be implementing soon and doesn't have all the god awful bloatware.
musclehead84 said:
If he doesn't have cwm3 then he's gonna have to run the one click root with cwm3 for eb13 to be able.to flash bonsai. If I were to guess he has cwm 2.5.1.0 installed. On another note HAPPY BIRTHDAY!!!!
Sent From My Evo Killer!
Click to expand...
Click to collapse
Where do I obtain one click root with cwm3? Thanks.
musclehead84 said:
There should be an ota coming for those on eb13. As long as you didn't remove any bloatware you should be able to install the update. Besides there might Even be an update.zip on here that you can use before you get the ota. And Odin isn't that bad. I know you worry that it might brick your phone but I've used it about 10 times so far and no problems here. As far as technology goes its developing extremely fast these days. Its hard to keep up with it. Good luck and if you have anymore questions or decide to Odin and need something don't hesitate to ask or even pm me. I answer really quick cause I have it send be an email when.I get a pm.
Sent From My Evo Killer!
Click to expand...
Click to collapse
stir fry a lot said:
Odin is only a pain the first time around. Now that you have the proper drivers installed its just a matter of selecting the file and clicking the start button. The only thing you have to watch out for is finding the correct usb port that the driver was installed on. As long as you're plugged into the correct one you're golden.
Click to expand...
Click to collapse
I agree with all of these except that odin never gave me trouble even the first time i used it..
Odin is cake just read the simple directions and everything should be fine, people dont use there heads when they get that android dude and the computer on there epic, the most ive been through is acore of force closes but its so easy to fix,
people just dont read the instructions all the way through,
Yesterday i was scared to update the prl manually but i read step by step instructions had to play around and find what i needed to do which wasnt on the instructions, and it was cake, almost just as easy as clicking the system updates/update prl button in the settings
but 98% of the time the instructions are flawless and work as long as you read carefully and do step by step.
drplaud said:
Where do I obtain one click root with cwm3? Thanks.
Click to expand...
Click to collapse
Development section stickied
Called One Click Clockwork 3.0.0.6
Oh yes happy birthday as well, have a great one!!
IMO, if you are on EB13, and want to update to EC05, the EASIEST way to do it, if you can wait a bit, is to use the stock SWUpdate for EB13, which will convert your phone back to a clean fresh stock install of EB13, then once/when it is released, install the EB13 to EC05 update via the over the air process, then reroot and move forward.
that all depends on samsung/sprint releasing a EB13 to EC05 OTA update, and your ability to wait for it though
Here's how I bricked my phone, for the ones who're interested:
I think it's a pretty funny story, so keep reading if you're searching for some entertaining story.
So I Bought a flipout because I wanted a small phone. I was pretty satisfied by the phone and it's performance, althought it's kinda an effeminate phone. Anyways, before I knew it (When I booted up the phone for the first time) I was disgusted by Orange's laggy intro: it was supposed to be an explosion followed by an implosion which created the Orange logo (sort of XBOX style). The reality was less: a very laggy 2 or 3 fps intro. Bravo Orange if you were actually aiming for this rate.
When I boot up the phone it shows the menu just like any other phone, but it came with another disgusting fact: MotoBlur. Lag, lag and lag. There it was, in all it's glory:
- It's laggy (not as much as Orange's intro...)
- Uses default services (calendar, gallery) with some unfinished 3D features (that caused needless lag)
- "Happenings" which connects your twitter, facebook and other things.
Although I have to say, I did like the lil tab that shows above and tells you on which screen you were. It looks kinda like the following (excuse me my drawing skills):
.: : . |^| . : :.
resp. -3 -2 -1 0 +1 +2 +3
Anyways, I had to get rid of this "MotoBlur" and the first thing I had to do was to root my device. I remember the days with the G1 which were a hassle to just root your phone, so I was hesitating if I really wanted to go through all this again...
But after a lil search, I found that nowadays we have superoneclick, androot, z4root, etc... etc... So I tried one of these "new" apk's which gave me a small error, so then I tried z4root which was quite easy, fast and simple. I was in. Things were going my way, hell, I even found a brand-new-looking 4GB microSD on my work. Just out of nowhere there it was, very small, laying down on the ground waiting for me to get picked up.
What goes up, must go down...
So there I was with my first steps trying to remove MotoBlur, and although I knew there were tut's about how to remove Orange and Blur, I just couldnt wait. I made backups of my system apk's with Titanium which was quite easy, and it was that precise moment when I was like "GET!", i'm sick of this MotoBlur, let's remove these "things". They are right in front of me, just get rid of them... And while continuously hitting the "remove" button I was daydreaming of a simple usefull handy phone. Bam, bam, bam, I deleted one app after the other, even Google Talk didn't had a chance. Everything was going smooth, bye Blur.Calendar.apk, bye odex, bye Blur.gallery.apk, bye Blur.happenings.apk,... ... ... about 20 apk's later, I was quite satisfied.
But you know how it goes when you just delete stuff without greater knowledge. You BRICK your phone. But people, this was just the start. I had some force close after this one man operation, but my phone was smoother. I have to admit, things were comming unexpected. First I couldnt find my gallery (removed). Then I found out I couldnt download anymore from the Android Market because I deleted Blur.calendar.apk which is connected with Calendar.apk which syncs my G-Mail account which is needed before you can download anything from the Market. Hah! Owned.
Backups.
So there I was having these problems, but the phone still works great. I have to admit I silently thought: luckely I made a backup, and was kinda proud I wasn't one of those noobs who just goes forward without a save game, right? Right? Guys...? Anyone...? . ... ...Wrong! The reality was I couldn't even "restore" with Titanium. The backups weren't real backups, but just data-backups which were stored on my sdcard in .tar format. Aaarrgh!
No problem, no problem. There has to be a way to fix this, someone did this stupidity before me. Obviously. Ofcourse. No?
When I was searching about why I couldn't fix my Titanium backups, someone answered to someone else that's because he couldn't sideload the apps. He needs to root his phone in a way so sideloading is enabled. Great! Sideloading it will be then.
Sideloading is def a great way to install .apk's without the market, because I tried a factory reset (hoping that would solve everything) and I couldn't download anymore from the market. I had to sideload ASTRO which was successful with the right ADB drivers - even though I didn't knew what ADB meant I did register on MotoDev's website (so I can download the little bastard).
Easy peasy. Now I'm back on track with ASTRO and an easy install of Flan Gallery (fixed camera) replaced my gallery. We're off to set!
Despite this minor victory I was aware I'm still not were I wanted to be. Factory reset doesn't get me were I want to be and I'm still having issues. But no problem no problem. This time I'll turn my questions to the community, not google. That's eventually why there is a community? That's why we are open source? Yes. Score. Win.
So maybe some knowledgeable people will reply because they can help the ones who are trying to learn. I think I'll start with how to fix the calendar-issue and then I'll try to make a ROM-backup, so I can install a new ROM or whatever. That's probably a better idea then before. Cool, I even got a quick reply by someone who told me to go to this-and-this site, which is better for noobs. Allrighty then...
Trying my own way.
Since things weren't going were I wanted to, I thought now it's time to give it a real last try by searching about this mystery "ADB" and eventually to push some apps into system/app/ so I could fix all this misery. I found what I was searching for, however the tut about how to push apps sounded like someone was holding a gun against the writer's head. It really sounded like he wrote it against his will.
Desperate attempts.
I started today (15 april) around 5pm local time with this whole pushing-thing because I thought I had the knowledge that I needed and even surprised myself by actually successfuly pushing some apk's using a quick and nice XDA how-to, but then things went from worse to worser. I pushed Blur.calendar.apk, Blur.service.apk, Blur.email.apk, Blur, Blur, Blur... Ironically thát what I wanted to remove at the start came voluntary back in my system/app/ of my phone.
That's quite funny especially when I rebooted my phone and I kept getting force close com.motorola.blur.service.main and I couldn't get around this except by using voice-commands (double tap home button). "Find ASTRO" I said. Finding ASTRO... Opening ASTRO... Ingenious! It was quite amazing that this feature actually works without any bugs or misunderstandings. So I started root manager, rebooted the system with r/w settings so I can try a final attempt by trying to remove blur-service.apk from the system/app/ which actually didn't had any impact. Nothing really happened.
The end.
And there I was having these problems, and the phone doesn't work. A friend of me adviced me on Steam-chat to hard-reset the phone. I could care less, but we had a little discussion about what has more effect hard-reset or factory-reset? Btw... Holding down the power button and the camera button...?! The phone doesn't even has a camera button! Hilarious.
I eventually did the hard-reset with another tut and now the phone is... ehm... kinda... pretty... bricked. It just boots up and then gives 1 continously looping force close of the blur service (which I allready had), and another force close when I finish setting up the blur account wizard. At the end of the wizard it just force close and shows the wizard again,... and again... and again...
Mathematical summon:
+1 noob
+1 bricked phone
- $$$
- (a lot of) time
+ frustrations/stress
+1 story
Equals a possitive outcome?
i've not rooted my Flipout as it seems there's not much you can do with a rooted one anyway
but I've done bad flashes before...many times
and i've always been able to rescue those phones by flashing the original rom. just wondering if this might be an option for you..
See if you can flash that device using RSDLite, I can see some tuts in this board that features this, likely that debranding guide. Hold up+power when it's off and boot into flash mode, not camera+power
A brick = a dead phone, no boot, no flicker, nothing. If it acts like a brick it's a brick, otherwise it's just a messed up phone. I'm sure you'll be able to recover yours...
Sent from my HTC HD2 using XDA Premium App
Moto phone + rsdlite + flipout sbf= fixed phone. Just find those two things and you can restore your phone back to fresh out of the box state again. Promise.
Sent from my SGH-I897 using Tapatalk
Yeap i just did it first try hold "up" button on the keyboard + power for 4 sec then plug usb. in flex options i checked everything and it all went god then
I'm sure most know this on here but it seemed to be a new idea over at rootz.
Whenever the dinc freezes and locks up, instead of waiting for it to reboot on its own, hold power, volume down and then press the trackball. That should knock off those annoying wait times if you have a rom that like to randomly freeze.
Yep, the "Three Finger Salute". It's been around for a while.
Thanks bobAbooE. Learn something new everyday - even after power-using my Dinc for 2 years. I could never understand why the Dinc, a god of a phone, couldn't reboot without a battery pull or got that stupid Low Memory error. Well, I found the EXT4ALL memory solution a month or so ago, and now I find the 3 Finger Salute. It's a good universe we live in...
Sent from my ADR6300 using Tapatalk 2
I have owned this phone since day 1 and never knew this lol. Thanks.
I know this technique has been around for a while, 'cause I've seen references to the "3 fingered salute" before, but I never saw what it actually meant. Now that I'm getting into custom ROMs and have experienced a couple of random lockups, I'm glad to know this trick. Thanks for posting!
Wow, after two years of rooting my dinc this is the first time I have heard of this this reboot option.
First time I've run across this method of rebooting, useful info.
This is a great tip. Especially, if you have a Seido multipart case!
Good tip, I use this one all the time.
thought I knew everything about the Inc, but apparently not!! thanks!
Great tip. Never knew that you could reboot the incredible this way. Thx.
BTW, I briefly ran with the Touch of Blue GB ROM over the weekend, and it did not support this "3-fingered-salute" reboot method. (I also couldn't get it to boot into the Bootloader via the Vol-down+Power buttons, which I thought was a ROM-independent feature, but I tried it multiple times without success, so I dunno what was going on there.)
Now that I'm on Tiny's CM10.1, the buttons are back to working as expected both for reboots and boots.
MysticCobra said:
BTW, I briefly ran with the Touch of Blue GB ROM over the weekend, and it did not support this "3-fingered-salute" reboot method. (I also couldn't get it to boot into the Bootloader via the Vol-down+Power buttons, which I thought was a ROM-independent feature, but I tried it multiple times without success, so I dunno what was going on there.)
Now that I'm on Tiny's CM10.1, the buttons are back to working as expected both for reboots and boots.
Click to expand...
Click to collapse
It was fast boot mode on sense that caused this.
To expand upon this discussion, fast boot is also a feature in Sense starting with GB -- on by default -- that when enabled, allows the phone to boot up faster. Details unknown but with it on, the phone doesn't truly shut down so you can't access bootloader from an off position. It is likely what prevented you from doing the 3-finger-salute.
I got mine from Amazon yesterday, I already bricked it a few hours ago by messing with the recovery. It should be an easy fix once I get hold of the stock firmware. I got another one coming tomorrow, so I'll focus on just extracting the rom from that one
Bricking aside, I got 20/10mbs down/up on speedtest using my T-mobile US SIM, and the signal indicator showed LTE. Forcing it off LTE I got 10/5mbs down/up.
Battery life is awesome, I used it constantly for 8hrs and only got down to 50%, my note4 would have been dead after that much use with the screen on. The overall feel of Android 6.0 was smooth, no stuttering. There is no bloatware, just a few utilities for fancy wallpapers.
The phone charges faster than any other phone I have. The included TPE case doesnt increase the thickness of the phone too much and I like that It keeps the camera lens off the desk when I set the phone down.
Dual SIM functionality works nice. It was one of the main features I was looking for, though I will miss T-Mobile wifi calling.
Some notes:
I used adb & fastboot in my attempts to root. After running
Code:
fastboot oem unlock
fastboot reboot
the display now showed
Code:
Orange state
Your device has been unlocked and can't be trusted
Your device will reboot in 5 seconds
So it appears that it is best to oem relock it when you're done updating, as the message goes away if you relock.
Backing up the ROM
I found SP Flash Tool v5.1632 for Linux and I've been practicing saving chunks of ROM from my bricked phone. I should be able to grab the recovery portion of the new phones' ROM tomorrow.
Based on the scatter.txt file I've found for the Gionee S8 AmigOS Marshmallow ROM, recovery starts at 0x8000 and is no more that 16Mb is size. So, in theory, I should be able to grab that range of the ROM and flash it using fastboot back to my bricked unit. I'm using the word "bricked", but its far from that, I should just say "unbootable" to be more clear.
Earlier today I was trying to get MTK droid tools to detect my Blu Pure XR so I could extract the scatter file, but It never was detected. All the drivers installed ok, so maybe its not compatible, I'm not sure yet. I'll get back onto that after my first unit is back up and working, hopefully tomorrow.
Edit: I just found a modified MTK Droid Tools for 64bit cpu phones, I'll give this a try too.
Edit next day: I got the second phone this morning. I used SP Flash Tool to grab the recovery.img portion of the new phone, then I used fastboot to flash it to the damaged phone, and it worked fine. The bootloader unlock/relock caused the phone to wipe itself and then re-encrypt the file system, so I lost a few test photos, no big deal. FWIW, I could have flashed the recovery back to the damaged phone using SP Flash Tool, but I wanted to make sure it worked with fastboot, which it did.
Heres the recovery.img for those that may need it and don't have two phones
View attachment xr-recovery.zip
Monday or so my mom gets her phone, so I'll be able to test LTE on AT&T with her SIM card. I just got 34Mbs download on a speed test (T-Mobile), which is is fine, considering all the naysayers reviewing on Amazon who didn't have the guts to buy the phone, saying LTE wouldn't work at all.
I just heard of this device today. I wonder how quick Android 7.x can be flashed over to this, but for $299 it's a good looking phone.
It may be a while since there's not much activity happening on this device yet.
I'm focusing on creating a rooted boot.img right now, as I'll be happy with 6.0 and root. I plan on having this done today. I've never created a custom twrp recovery, but I may try that next.
I need to figure out how to prevent the full wipe after oem unlocking/relocking, that's a real pain having all my setup deleted after every test, as it makes it hard to use the phone while developing.
Got root
Firstly, I'm still learning about Mediatek based devices, so I feel like a noob again. I haven't edited a ROM in several years and there's a lot of crap info on the internet. Most articles that write up "how to root a phone" basically say "Install twrp, then supersu", yeah, thanks
After struggling with all the selinux controls in 6.0, I switched to hack mode. As per phhusson's super-bootimg script, I used his sed technique to force the init in boot.img to not enforce security policy and added his bits to init.rc to load su. I put su and in system.img along with a suid root shell just in case. Its working, I have SuperSu installed, and it pops up to ask me to grant permissions. It won't update its su binary, I've got some permission problem there, but it's not a show stopper. Also,I found its easiest to just leave the bootloader unlocked while testing, I just have to get used to the annoying boot message and 5 second delay.
This week I'll start from scratch and document the procedure I used and hopefully make it repeatable for anyone else who may want to try it. Maybe someone will just port twrp and save me the time of learning how to do it
Some notes on the software I used:
Windows:
* SP Flash Tool with a bogus scatter file to grab the stock ROM sections of my phone as the Linux version would timeout reading large ranged of flash.
Linux:
* mktool to unpack/repack the boot.img
* loopback mounted the system.img to add su to it.
* used img2simg to convert system.img to a sparse image
* fastboot to flash the boot & system images to the phone.
AT&T Speed Tests
No good, ~500kbs up/down, even though signal strength showed 4 bars on 4G. No LTE at all. Changing the band set to 3g/4g had no real effect either way. Don't buy this phone I you plan on using it with AT&T, although my mother hasn't noticed the ****ty 4G in actual use yet (I'll switch her to T-mobile soon).
Update: After using the phone for 1 week, I am extremely pleased with it. I chuckle when I read the negative reviews on all the big phone web sites. Reviewers hate the wiggly button, LOL, but it doesn't bother me as I'm used to it on my Samsungs. Other than the wiggly home button, its a solid phone. I prefer the metal back as opposed to glass. By the way, who's brilliant idea was it who thought an all glass phone was a good idea?
It's not AOSP, but I find it's AmigOS Carefree launcher very pleasant to use, and I've used countless launchers over the years. It's got way better specs than the Nexus 5X and after struggling with the security in 6.0, I'm not in any rush to find out what security bull**** awaits me in 7.0 (for my benefit of course).
On the flip side, I don't use NFC payments, Google Pay, Google Play, no Google anything. All Google stuff disabled. I run my own calendar/contacts/tasks sync server, use oandbackup to save/restore all my apps and settings, the majority of my apps come from f-droid. I don't play games. So I'm not an average user. I've been using Android devices since the Nexus One and I have a pile of phones in front of me. Blu (or Gionee) has shown it can make quite a competitive device that I enjoy using all day, (though I wouldn't be using it at all unless it was rooted, so luckily for both of us that is the case).
Rant: Things that are actually more annoying than a wiggly button:
* Dozens of phone review websites that all publish a review of this phone within 2 days of each other after the phone was released on Aug 29th ,with all the same content. It's like they are all run by the same hack, just to get advertising dollars.
* Websites like rootoreviews.com that use a template on how to root this particular phone using twrp, when twrp doesn't exist yet for the device. WTF is that? Why would someone think this is a great idea? They have the same instruction set for every phone on the site with the make/model info swapped out. Are they just hoping twrp becomes available soon so they have the first post on the topic by default? Lame!
rotohammer said:
No good, ~500kbs up/down, even though signal strength showed 4 bars on 4G. No LTE at all. Changing the band set to 3g/4g had no real effect either way. Don't buy this phone I you plan on using it with AT&T, although my mother hasn't noticed the ****ty 4G in actual use yet (I'll switch her to T-mobile soon).
Update: After using the phone for 1 week, I am extremely pleased with it. I chuckle when I read the negative reviews on all the big phone web sites. Reviewers hate the wiggly button, LOL, but it doesn't bother me as I'm used to it on my Samsungs. Other than the wiggly home button, its a solid phone. I prefer the metal back as opposed to glass. By the way, who's brilliant idea was it who thought an all glass phone was a good idea?
It's not AOSP, but I find it's AmigOS Carefree launcher very pleasant to use, and I've used countless launchers over the years. It's got way better specs than the Nexus 5X and after struggling with the security in 6.0, I'm not in any rush to find out what security bull**** awaits me in 7.0 (for my benefit of course).
On the flip side, I don't use NFC payments, Google Pay, Google Play, no Google anything. All Google stuff disabled. I run my own calendar/contacts/tasks sync server, use oandbackup to save/restore all my apps and settings, the majority of my apps come from f-droid. I don't play games. So I'm not an average user. I've been using Android devices since the Nexus One and I have a pile of phones in front of me. Blu (or Gionee) has shown it can make quite a competitive device that I enjoy using all day, (though I wouldn't be using it at all unless it was rooted, so luckily for both of us that is the case).
Rant: Things that are actually more annoying than a wiggly button:
* Dozens of phone review websites that all publish a review of this phone within 2 days of each other after the phone was released on Aug 29th ,with all the same content. It's like they are all run by the same hack, just to get advertising dollars.
* Websites like rootoreviews.com that use a template on how to root this particular phone using twrp, when twrp doesn't exist yet for the device. WTF is that? Why would someone think this is a great idea? They have the same instruction set for every phone on the site with the make/model info swapped out. Are they just hoping twrp becomes available soon so they have the first post on the topic by default? Lame!
Click to expand...
Click to collapse
Hi theer just curious on how you get it to root then??
Thanks for potentially inspiring some activity here regarding this phone. It looks like an impressive device, but I won't pull the trigger until there're some solid rom options.
Hey brother hope you r doing well. Glad to see this thread with the smartphone similar to mine. My phone is symphony helio s20, mtk6755 helio p10 processors, 4gb ram 64gb rom with the similar system.img and boot.img of gionee s8 & blu pur xr.
I was desperately looking for a pre rooted rom or a custom, custom recovery and rooting tool for almost 2 months, requested so many times all around this site, but unfortunately didn't get any respons (really frustated). I just badly need to root my device but I'm just a noob on modding and tweaking with Roms. I got my stock rom from Service Center, when I bricked my phone flashing a custom recovery. Later I tried all the method found all over the website but non of them are working only misleading. Bricked my phone several times but luckily I managed to reflash the stock rom by sp flash tool. Please keep this good work up and help us root our devices without any hassle. You are doing a really great work so keep it up bro!
Here is the link of my stock firmware with sn write tool if you need it for anything bro.
Best regards
https://drive.google.com/open?id=0BywTv6KKZO4jX3BMMGRGVUFRa28
http://www.mediafire.com/download/7...N_Writer_tool_exe_v1.0_1604.00_All_In_One.rar
http://www.mediafire.com/download/pa2f3wqpf24t0db/Helio_S20_flashtool.zip
thanks in advance
Hey guys, thanks a lot for all your info and everything you posted Could you be so kind to describe how did you root your Pure XR devices??? Big hug from Cuba
I'm going to guess something with KingRoot. This is a rebranded Gionee S8, so China is already no stranger to this phone.
Not surprised about AT&T performance considering I've never seen an unlocked phone support so few LTE bands (2, 4, 7). Ridiculous. It supports less than half of all the LTE bands AT&T uses. Unless your area uses primarily band 2 or 4 you're screwed if you're on AT&T. Even worse if you're on T-Mobile. It only supports ONE band on T-Mobile. Does Blu even realize it's 2016?
bailsafe said:
I'm going to guess something with KingRoot. This is a rebranded Gionee S8, so China is already no stranger to this phone.
Click to expand...
Click to collapse
I tried every rooting tool, including KingRoot, none worked. There's an OTA update for the stock firmware, but I wont be able to install it until after I un-root. I probably retrace the steps I did the first time: backup all my apps, flash the stock firmware, do the OTA, then save/edit it to have root, then flash the result. The phone works so good right now that I'd hate to mess it up.
Tikerz said:
Not surprised about AT&T performance considering I've never seen an unlocked phone support so few LTE bands (2, 4, 7). Ridiculous. It supports less than half of all the LTE bands AT&T uses. Unless your area uses primarily band 2 or 4 you're screwed if you're on AT&T. Even worse if you're on T-Mobile. It only supports ONE band on T-Mobile. Does Blu even realize it's 2016?
Click to expand...
Click to collapse
This was a Gionee S8 originally, which only supported FDD-LTE bands not in use in the USA. It's a miracle they got FDD-LTE in here at all, I guess, but if you're gonna sell in the US market... they really need more bands.
Rotohammer said:
I tried every rooting tool, including KingRoot, none worked. There's an OTA update for the stock firmware, but I wont be able to install it until after I un-root. I probably retrace the steps I did the first time: backup all my apps, flash the stock firmware, do the OTA, then save/edit it to have root, then flash the result. The phone works so good right now that I'd hate to mess it up.
Click to expand...
Click to collapse
That's probably your best bet. I'm surprised KingRoot wouldn't work, even on the newer updates...
hey I was wondering for some reason my blu pure xr does not receive notifications at all except for certain apps and it keeps on disconnecting from messenger and such is there any remedy for this?
orlandotisk said:
hey I was wondering for some reason my blu pure xr does not receive notifications at all except for certain apps and it keeps on disconnecting from messenger and such is there any remedy for this?
Click to expand...
Click to collapse
Press left button to bring up the running apps list, long press the button with 3 rectangles in it, then press "Clean white list". Here, you press"Add into white list" and choose "messenger" and any other apps you don't want "auto cleaned".
For example, my white list includes Alarm Klock, K-9 mail, CSipSimple, Silence (all apps that I want running all the time)
rotohammer said:
I got mine from Amazon yesterday, I already bricked it a few hours ago by messing with the recovery. It should be an easy fix once I get hold of the stock firmware. I got another one coming tomorrow, so I'll focus on just extracting the rom from that one
Bricking aside, I got 20/10mbs down/up on speedtest using my T-mobile US SIM, and the signal indicator showed LTE. Forcing it off LTE I got 10/5mbs down/up.
Battery life is awesome, I used it constantly for 8hrs and only got down to 50%, my note4 would have been dead after that much use with the screen on. The overall feel of Android 6.0 was smooth, no stuttering. There is no bloatware, just a few utilities for fancy wallpapers.
The phone charges faster than any other phone I have. The included TPE case doesnt increase the thickness of the phone too much and I like that It keeps the camera lens off the desk when I set the phone down.
Dual SIM functionality works nice. It was one of the main features I was looking for, though I will miss T-Mobile wifi calling.
Some notes:
I used adb & fastboot in my attempts to root. After running
Code:
fastboot oem unlock
fastboot reboot
the display now showed
Code:
Orange state
Your device has been unlocked and can't be trusted
Your device will reboot in 5 seconds
So it appears that it is best to oem relock it when you're done updating, as the message goes away if you relock.
Click to expand...
Click to collapse
Hey bro how are you? How's family? I hope that everything is well for you and yours. Basically I just wanted to say thanks for sharing such great info. And I'm really glad that there's someone who's onto something like einstein. I just hope that you can figure out a way to get root with your own custom build of twrp recovery using chainfire's supersu to work with this smartphone. Cos that'll be super-awesome right? But I'm just a noob so all I can do is just wish you the best of luck. So best of luck until you crack the code. And I have complete faith in you. You will achieve it I know that for sure. Wish you and yours all the best. And thanks again in advance. Peace!
Does anybody succeed rooting ?
Please share the method!!
so no one knows how to root?
rotohammer was able to achieve root and said he would get back to us with the method on how it was done, but he hasn't posted it yet...