Related
title says it all. running stock rooted. turns out, it has gone out of date. i am not running an alternate rom bcuz i need to return my evo in a few days (little bro cracked the screen). i just tried to unroot today, and got the main version older fail. i am on a mac, so any help would be much appreciated.
i have simular prob shipped roms .co has them as exe file run them in order full unroot i sadly have toasted usb which is needed to do this and right now can get fixed for like 30n bucks but cant figure how to get them on fone need flashable ,,,, ithink hope helps
pretty noobish just read alot recently with my prob
I know about these exe files. They are the sprint ruu files, and are common knowledge. The problem is, I don't have a pc. It would be great if I got a Mac fix.
http://www.megaupload.com/?d=108Z9R8Y
Dont know if this is what you wanted but i've unrooted fine using this file just put in sd card and enter bootloader. I got it from the how to unroot thread in the dev forum the name of the guy i got it from escapes my mind at the moment.
Sent from my PC36100 using Tapatalk
Do you know ...did it wipe recovery and all ffrom what ive heard they havent been looking real close but i dont believe in luck but i dont seem to get away with much these days this phone was from fist day releaseits beat up, but i did the 60 step toast method about 20 trimes getting it rooted too work but i hate idea of parting with it thamks for info though much appreciation
OK so I'm on my 3rd htc evo 4g since its release, 2nd in the last 2 weeks. something keeps happening every i root it. i used the 3step root the first time i rooted, i then proceeded to use the autoroot that's currently out the last time, the phone constantly reboots itself non stop and feels warm to the touch, really warm. does anyone have an idea on what methods i should take to root my phone and what roms to use.
the last 2 times my phone broke down was running on myns 2.2 rsl4 or w/e.
i placed this is devs because it really has alot to do with the dev of this phone, the guy at sprint just gave me my phone back and he said its been fine for 2 days with original software on it...
please move if you feel it needs to be moved.
I'm confused, is your phone already rooted or not? If your phone is overheating and rebooting I'd be willing to bet it's your KERNEL that's causing issues, not your rooting method
Yeah and I'm confused why you would be needing the new phones unless you had a real hardware issue?
first phone was rooted, it went haywire so i took it in, kid there flashed original software, phone was STILL restarting every time i played a game or w/e. he gave me new phone, rooted it, flashed myns through rom manager, restarted alot, tried new kernal, restarted ALOT more, took it, flashed original software and took root away again, new phone, currently just got it 2 hours ago....any set up ideas now?
b_allert said:
first phone was rooted, it went haywire so i took it in, kid there flashed original software, phone was STILL restarting every time i played a game or w/e. he gave me new phone, rooted it, flashed myns through rom manager, restarted alot, tried new kernal, restarted ALOT more, took it, flashed original software and took root away again, new phone, currently just got it 2 hours ago....any set up ideas now?
Click to expand...
Click to collapse
Why don't you use it for a few days without rooting it - see what you experience? You also didn't mention what HW version and HBoot you had.... there are a lot of factors which could potentially cause something like this...
But I think the first thing you should do is do nothing. Use it without rooting and see what happens.
buy a blackberry haha
I resent people that attempt to trade in phones at their mistakes when it's just pure laziness.
I'm glad you're at least asking rather than repeating this process.
1st use Unrevoked3 to root.
Now, you should download a stock ROM to prevent from having to go into the store each time.
I'd recommend actually using this over a stock ROM anyways (it's a modified stock to run better).
And after that just browse through many ROM's, as far as kernel's I'd recommend trying Ziggy's.
isawred53 said:
buy a blackberry haha
Click to expand...
Click to collapse
+1
Sounds like a SD format bootloop or your tryin to flash to much at one time. Also remember some new find take a lot of time to load giving the appearance of a bootloop
thanks ill do that.
info.
hardware-0003
baseband-2.15.00.07.28
build-3.26.651.6 cl218634 release-keys
software-3.26.651.6
pri-1.90_003
prl-60674
b_allert said:
thanks ill do that.
info.
hardware-0003
baseband-2.15.00.07.28
build-3.26.651.6 cl218634 release-keys
software-3.26.651.6
pri-1.90_003
prl-60674
Click to expand...
Click to collapse
You still don't have an hboot listed
Neotelos_com said:
I resent people that attempt to trade in phones at their mistakes when it's just pure laziness.
I'm glad you're at least asking rather than repeating this process.
1st use Unrevoked3 to root.
Now, you should download a stock ROM to prevent from having to go into the store each time.
I'd recommend actually using this over a stock ROM anyways (it's a modified stock to run better).
And after that just browse through many ROM's, as far as kernel's I'd recommend trying Ziggy's.
Click to expand...
Click to collapse
it wasnt something i never tried fixing, i flashed over the opriginal software myself and then re rooted, i tried plenty of kernals and roms i even debated buying a new battery. i posted plenty of help signs, no one came, so i took to the store, trust me, i WANT to learn about this phone i really do, however being a full time student and working, i have very little time to learn in-depth
about this phone.
khshapiro said:
You still don't have an hboot listed
Click to expand...
Click to collapse
i just had to check, 2.10
b_allert said:
i just had to check, 2.10
Click to expand...
Click to collapse
I think I see your problem, you need to downgrade your PRI, the PRI is fine if you don't want to use any new kernels, but with custom Kernels you need the lower one. I had a lot of problems until I downgraded.
bigupurself7 said:
I think I see your problem, you need to downgrade your PRI, the PRI is fine if you don't want to use any new kernels, but with custom Kernels you need the lower one. I had a lot of problems until I downgraded.
Click to expand...
Click to collapse
and is it easy or hard to downgrade it?
I'm on my 6th since its release
Sent from my PC36100 using Tapatalk
You don't need to downgrade your hboot, the only reason for that is to get an engineering hboot for fastboot commands and modifications, if your just flashing roms you don't need to do that. Make sure your following unrevoked very carefully, and before flashing any rom make sure you wipe eveyrthing, flash amon ra recovery and the option to wipe all is easy. So wipe all data, flash new rom and wait for reboot, takes a while now on first reboot. Also use your phone for a week to make sure its not hardware related before you root and flash.
b_allert said:
and is it easy or hard to downgrade it?
Click to expand...
Click to collapse
Just as easy as flashing a rom or kernel.
http://forum.xda-developers.com/showthread.php?t=715485
I would also downgrade nv to 1.77
Everything else is fine though.
Third one, huh? I'm almost sure it's something that you're doing if it's a reoccurring problem.
b_allert said:
and is it easy or hard to downgrade it?
Click to expand...
Click to collapse
You don't need to downgrade your PRI. I am on the same PRI as you (1.90_003) as well as hardware version (HW 003) and I have no issues.
Use the Z... somthing like that for rooting it and i use myns rom nothing is wrong with it , B.O.S sacs roms are very nicly made to
I followed instructions to root it and its rooted, but have never been able to get Cyanogenmod to Install (I always get the same error everyone else does), and when I try to check out different ROMS, no one even posts many pics to show what the difference will be to use that ROM.
My phone looks the same as before and I'm just using ADW launcher to set it up the way I want it to look.
So how can I tell exactly what point of rooting my phone has reached? Do I actually have a different ROM, etc? I don't know much about this stuff and I'm not bricking my phone messing around with it until I know exactly where to start.
What custom recovery and bootloader are currently loaded on the phone?
kmodek said:
So how can I tell exactly what point of rooting my phone has reached? Do I actually have a different ROM, etc?
Click to expand...
Click to collapse
Hi!
Go to your phone's System Settings --> About phone.
In there, you should be able to figure out which Android version is currently installed on your phone; if you have a custom ROM, most of the time ROMs developers will also add an additional line somewhere on that screen to tell exactly what revision of their ROM is installed. If not, you may be able to grab some more information by checking your build number or your kernel revision.
If you tap a few times on where it says Android Version, under Settings>More>About Device , it usually does a little animation of the rom version. Im trying to decide on a rom so mine is kit kat 4.2.2 at the moment and dislpays an Android logo in the Kit Kat logo style.
Since the bootloader version is not displayed on the About Phone page, you will need to determine that with another method. A simple way would be with the Samsung Info app from the PlayStore, the one posted by vndnguyen.
I personally use Terminal Emulator commands to determine phone info.
Code:
getprop ro.bootloader
getprop | grep version.baseband
I got the app from the Play store and it shows I'm on 4.4.2, but that the Knox has been tripped (I know it's rooted because I have an app that verifies root), but other than that, I can't tell any difference from how it was originally.
Guess I just thought rooting it would make it look a lot different and after reading through all of the forums, there seems to be 100 steps just to try out one new ROM and I don't even know what you do if you get it and decide you don't even like it. I just don't want to brick my phone.
kmodek said:
Guess I just thought rooting it would make it look a lot different and after reading through all of the forums, there seems to be 100 steps just to try out one new ROM and I don't even know what you do if you get it and decide you don't even like it. I just don't want to brick my phone.
Click to expand...
Click to collapse
i was watching youtube videos of reviews of the different custom ROMs gave a good idea on the features and layout of each rom. I as well am having difficulty deciding on a ROM to flash as this is my first smart phone and am new to it. ive been reading and watching a bunch of tutorials but finding information on whats currently stable for our particular phone can be somewhat dated. i know moderators want to avoid a "best roms" thread but for those of us just starting out with a rooted phone it sure would be handy to have opinions on what ppl use for the SGH-I747 and why, so its easier to decide on one.
is it reccommended to upgrade or downgrade? in order to compare ROMs its watching a video for 15 min to see what features it had at the time the vid was made and reading the developer forums on each mod to see what bugs are present in the current release but its not all compiled anywhere. its that or randomly flash ROMs on there to test them out and risk making mistakes. its usually always better to have advice from those with expertise and perhaps avoid making commonly made mistakes. ive read a bunch of helpful and handy guides on here but doesnt seem any way to easily compare roms or get feedback on what users have decided on sticking with or anything additional specific to this phone that should be considered before flashing certain ROMs.
kmodek said:
I got the app from the Play store and it shows I'm on 4.4.2, but that the Knox has been tripped (I know it's rooted because I have an app that verifies root), but other than that, I can't tell any difference from how it was originally.
Guess I just thought rooting it would make it look a lot different and after reading through all of the forums, there seems to be 100 steps just to try out one new ROM and I don't even know what you do if you get it and decide you don't even like it. I just don't want to brick my phone.
Click to expand...
Click to collapse
this thread may help to explain some badic things.
http://forum.xda-developers.com/showthread.php?t=2343223
my advice , for what its worth ...
1) READ READ READ
2) make a backup of your current setup so you have it to fall back on.
3) NEVER downgrade your bootloader , flash any ROM/kernel not meant for your device (sure way to brick it).
theres always risk when flashing anything , but the risks can be minimized by understanding what your doing , or rather the process.
as far as flashing roms , its pretty simple once you understand it (as with most things. lol). reading thru a ROMs thread will give a general idea of any features , issues that the users have. the OP , first post ; will tell you alot about the ROM/features.
good luck and happy flashing.!
"all i can really do , is stay out of my own way and let the will of heaven be done"
kmodek said:
.... (I know it's rooted because I have an app that verifies root), but other than that, I can't tell any difference from how it was originally.
Guess I just thought rooting it would make it look a lot different and after reading through all of the forums, there seems to be 100 steps just to try out one new ROM and I don't even know what you do if you get it and decide you don't even like it. I just don't want to brick my phone.
Click to expand...
Click to collapse
The act of rooting does not outwardly change the look and feel of a ROM in any way. It's what you do after rooting that makes the difference.
Some like the Stock Rom of a device and/or do not want to lose some of its unique features. These people will root but not flash a custom ROM.
I've had two android phones and one tablet. Initially I root a new device but leave it on the stock ROM. At that time I will use an app that requires root to freeze any of the pre-installed apps that I don't use (My definition of bloat.) I don't remove/delete them at the beginning. If freezing them breaks some other functionality I want that app still on the device so that I can unfreeze it and make everything work again. Both of my phones have been Samsungs, a SGS Captivate and a SGS3. After a while on rooted stock I have changed to custom ROMs on each. The Captivate went from stock to CyanogenMod to a CM derived ROM. The SGS3 went from stock to a re-themed, custom ROM based on stock but with much removed (carrier bloat) and some other functions added. I expect to soon change to a later version of the same ROM with even more removed. Others want to have a ROM with every bell and whistle possible to have present. It's all individual preference.
havok6669 said:
i was watching youtube videos of reviews of the different custom ROMs gave a good idea on the features and layout of each rom. I as well am having difficulty deciding on a ROM to flash as this is my first smart phone and am new to it. ive been reading and watching a bunch of tutorials but finding information on whats currently stable for our particular phone can be somewhat dated. i know moderators want to avoid a "best roms" thread but for those of us just starting out with a rooted phone it sure would be handy to have opinions on what ppl use for the SGH-I747 and why, so its easier to decide on one.
is it reccommended to upgrade or downgrade? in order to compare ROMs its watching a video for 15 min to see what features it had at the time the vid was made and reading the developer forums on each mod to see what bugs are present in the current release but its not all compiled anywhere. its that or randomly flash ROMs on there to test them out and risk making mistakes. its usually always better to have advice from those with expertise and perhaps avoid making commonly made mistakes. ive read a bunch of helpful and handy guides on here but doesnt seem any way to easily compare roms or get feedback on what users have decided on sticking with or anything additional specific to this phone that should be considered before flashing certain ROMs.
Click to expand...
Click to collapse
There are so many variations on what is possible that a compilation thread to cover all situations would seem as huge as wikipedia. Your approach, reviewing videos and checking rom OPs, has merit but it also has limitations. Unfortunately some of the devs give you almost no information about the features and customizations of their ROMs. Others will simply state that they have made a change or two to some base, expecting you to be familiar with the base. Which means a lot of more reading/reviewing for a person new to customizing their phone.
To advise any one questioner on what can be installed on their phone a responder must first know what bootloader and modem is on the device, are you already rooted, do you have a custom recovery installed yet, are you willing to risk breaking your warranty; the list goes on. Then the hard part comes - they have to recommend something that is in the realm of what you are expecting, even if you do not know what you are expecting.
dawgdoc said:
To advise any one questioner on what can be installed on their phone a responder must first know what bootloader and modem is on the device, are you already rooted, do you have a custom recovery installed yet, are you willing to risk breaking your warranty; the list goes on. Then the hard part comes - they have to recommend something that is in the realm of what you are expecting, even if you do not know what you are expecting.
Click to expand...
Click to collapse
well i made sure i learned a bunch before even attempting to ask a question so i got as much as possible prepared i'll try to provide the best information i can. my phone is rooted with superuser su2.0 i have cwm 6.0.1.2 installed, ive done a cwm nandroid backup which i copied to my pc as well as a backup of my efs folder and done a titanium backup as well. i have odin 3.07 on my pc and am currently running kitkat 4.4.2 on my sgh-i747m (sasktel version) currently trying to figure out how to determine the modem and bootloader versions . i followed the galaxys3root.com guide galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3-on-android-4-34-4-2-new and the highonandroid youtube vid in order to root my phone and made sure i read re read and was very cautious to follow instructions to the letter also read some worst case scenario information first like how to cause a phone to become bricked and how to fix it should it happen etc so before ive done anything else ive made sure to back everything up and ask a few more questions befor ei take the final plunge :] as for what ROM would tickle my tailfeathers was liking how carbon looked but it seems it hasnt been maintained :[ something good on battery life that runs fast n stable and is has a bunch of customization features is what i was hoping for. the main reason i decided to root my phone was to learn more about it and customize my os away from the stock look and feel and unlock some of the potential it has that a stock rom would otherwise neglect. the more i learn the sooner i can help by giving back to the community :]
havok6669 said:
....
my phone is rooted with superuser su2.0 i have cwm 6.0.1.2 installed, ive done a cwm nandroid backup which i copied to my pc as well as a backup of my efs folder
Click to expand...
Click to collapse
CWM 6.0.1.2 is a bit dated, their latest version is 6.0.4.7 and even it is a bit dated. You may find that to flash a current ROM you will need to update CWM. For some of the newer ROMs even 6.0.4.7 is not current enough. You will need to change to Philz Recovery, based on CWM, or TWRP. Bear in mind that if you change to TWRP you will not be able to use your CWM nandroid. I don't know if the same applies to Philz Recovery.
https://www.clockworkmod.com/rommanager
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/ (page is down at the moment)
http://teamw.in/devices/samsunggalaxys3canada.html (d2can TWRP, though I think you can use d2att, check before using d2att)
There is definitely a newer version of SuperSu (by Chainfire) available. It went through a lot of development to handle issues related to Knox that came out with Touchwiz 4.3. SuperSu is now up to 2.49 and I would recommend upgrading it no matter what ROM you should end up choosing. http://forum.xda-developers.com/showthread.php?t=1538053 There is a zip you can flash from you current CWM there.
It's not a bad idea to have several fallbacks for imei/nvdata. Give this tread a look: http://forum.xda-developers.com/showthread.php?t=1852255&highlight=synergy+nvbackup I used the reboot nvbackup from there and EFS Backup developed by wanam
... am currently running kitkat 4.4.2 on my sgh-i747m (sasktel version) currently trying to figure out how to determine the modem and bootloader versions .
Click to expand...
Click to collapse
Sasktel has released 4 versions of Android 4.4.2, each with a different bootloader and modem. Any should be fine no matter what ROM you choose, even a Lollipop based ROM. But to check you can get Phone Info - Samsung by vndnguyen from the Playstore. Or you could use a pair of commands in Terminal Emulator
Code:
getprop ro.bootloader
getprop | grep version.baseband
... as for what ROM would tickle my tailfeathers was liking how carbon looked but it seems it hasnt been maintained :[ something good on battery life that runs fast n stable and is has a bunch of customization features is what i was hoping for. the main reason i decided to root my phone was to learn more about it and customize my os away from the stock look and feel and unlock some of the potential it has that a stock rom would otherwise neglect. the more i learn the sooner i can help by giving back to the community :]
Click to expand...
Click to collapse
You could either go straight a Lollipop based ROM or start with a KitKat ROM. The KK ROM would probably be a bit more stable, although some of the nightly 5.1.1 LP ROMs are looking good according to many of the people installing the nightly versions. If you want something already customized with options for your choosing look to CM and its derivatives or one of the AOSP roms that are already tricked out. The other direction would be to install the most barebones AOSP ROM you could find and use XPosed with the GravityBox or Wanam module to tweak just about everything, but not both at the same time.
wow thanks that all helps a ton ill work on locating and updating all of that :]
First off, I am a newbie here, so please be kind.
I have a Samsung Galaxy Note 4 (SM-N910V), running Android 6.0.1 stock Verizon ROM.
I have been getting some strange battery issues. Not charging to 100%, shutting off at 35%, stuff like that.
I have wiped the cache partition and done a factory reset with no luck.
I have replaced the battery.
When I boot into recovery mode, I get dead Android, no command.
I don't know if the problems are related, but I suspect so.
Don't know what else to do. Any help would be appreciated.
soccerplayer00321 said:
First off, I am a newbie here, so please be kind.
I have a Samsung Galaxy Note 4 (SM-N910V), running Android 6.0.1 stock Verizon ROM.
I have been getting some strange battery issues. Not charging to 100%, shutting off at 35%, stuff like that.
I have wiped the cache partition and done a factory reset with no luck.
I have replaced the battery.
When I boot into recovery mode, I get dead Android, no command.
I don't know if the problems are related, but I suspect so.
Don't know what else to do. Any help would be appreciated.
Click to expand...
Click to collapse
Do you have an unlocked bootloader (root)? You could try reflashing twrp with odin to get recovery back.
No, not rooted. Have always been afraid to brick the device. If that is the direction that I have to go then I will give it a shot. I figure there are enough directions on here I could probably figure it out.
soccerplayer00321 said:
No, not rooted. Have always been afraid to brick the device. If that is the direction that I have to go then I will give it a shot. I figure there are enough directions on here I could probably figure it out.
Click to expand...
Click to collapse
If you don't want to root, you could try flashing the cpd1 firmware with odin and that should overwrite what might be throwing off your battery calibration. Unless it's a hardware problem that is. Are you comfortable using odin? Also if you have no interest in rooting, you could flash the most recent firmware.
I am a little familiar with Odin. I used it to put Android 6.0.1 onto my phone. Cpd1? This is the first that I am hearing (or reading) anything about cpd1. I would be interested in rooting, the biggest problem that I have with doing so is that most of the instructions that I have found are written for someone who has a better grasp of this stuff that I do. Do you know of any simple step-by-step walkthroughs? One that a newbie like myself could actually follow.
From what I've read about rooting, I am definitely interested, but still paranoid about bricking the phone. I do have an S5 as a backup if need be, so I am reluctantly willing to give it a shot.
soccerplayer00321 said:
I am a little familiar with Odin. I used it to put Android 6.0.1 onto my phone. Cpd1? This is the first that I am hearing (or reading) anything about cpd1. I would be interested in rooting, the biggest problem that I have with doing so is that most of the instructions that I have found are written for someone who has a better grasp of this stuff that I do. Do you know of any simple step-by-step walkthroughs? One that a newbie like myself could actually follow.
From what I've read about rooting, I am definitely interested, but still paranoid about bricking the phone. I do have an S5 as a backup if need be, so I am reluctantly willing to give it a shot.
Click to expand...
Click to collapse
I was just referring to the first mm firmware that ends with cpd1 and the reason I suggested that particular one was just in case you were thinking of rooting. If you use any of the "safe" firmwares you should be ok though. I agree about the rooting process, it's not the most user friendly thing I've ever seen, but it really isn't as bad as it looks. As long as your using the files provided in those threads there really isn't a huge risk in bricking your phone. Worst case scenario, you get into a jam that takes a little while to get out of so be sure that you leave yourself time to recover in case you can't use your phone for a couple hours. I think the worst part is the instability of kingroot which means you have to do all the adb commands as quick as possible and the fact that if you want mm you have to do the root process twice. These are the two posts that got me through it:
Lollipop
Marshmallow
Start with Lp first, it's necessary to unlock that before going to mm. If your problem is software related, installing the firmwares to root should fix things. Best of luck!
kevintm78 said:
I was just referring to the first mm firmware that ends with cpd1 and the reason I suggested that particular one was just in case you were thinking of rooting. If you use any of the "safe" firmwares you should be ok though. I agree about the rooting process, it's not the most user friendly thing I've ever seen, but it really isn't as bad as it looks. As long as your using the files provided in those threads there really isn't a huge risk in bricking your phone. Worst case scenario, you get into a jam that takes a little while to get out of so be sure that you leave yourself time to recover in case you can't use your phone for a couple hours. I think the worst part is the instability of kingroot which means you have to do all the adb commands as quick as possible and the fact that if you want mm you have to do the root process twice. These are the two posts that got me through it:
Lollipop
Marshmallow
Start with Lp first, it's necessary to unlock that before going to mm. If your problem is software related, installing the firmwares to root should fix things. Best of luck!
Click to expand...
Click to collapse
First off, thanks for your help. I appreciate it.
I finally got around to trying to do this with my phone and I can't even get past the first step. Install King Root, 4.8.5. I've tried 4.8.5 and 5.0, and neither one of them can get root access. Don't know what else to try.
soccerplayer00321 said:
First off, thanks for your help. I appreciate it.
I finally got around to trying to do this with my phone and I can't even get past the first step. Install King Root, 4.8.5. I've tried 4.8.5 and 5.0, and neither one of them can get root access. Don't know what else to try.
Click to expand...
Click to collapse
Did you ever have any luck with kingroot? If you haven't tried already, do a factory reset before you start the process and if it fails uninstall, reboot, reinstall and try again. I know it's a frustrating process and it seems to take most people many tries. When it fails on you how far does it get?
Kingroot was really frustrating. It would never get past 52%. After countless tries I moved to kingoroot. Kingo root worked on first try. Glad I unlocked and rooted my note 4
Sent from my SM-N910V using XDA-Developers mobile app
kevintm78 said:
Did you ever have any luck with kingroot? If you haven't tried already, do a factory reset before you start the process and if it fails uninstall, reboot, reinstall and try again. I know it's a frustrating process and it seems to take most people many tries. When it fails on you how far does it get?
Click to expand...
Click to collapse
No luck on Kingroot. It usually dies around 25% or so. Sometimes a little before that and sometimes after that. It never even got into the 35% range.
What I think I am going to do is go back to kitkat, original samsung rom. Try Kingoroot and see if that works. If not, I will push lolipop to it and try kingoroot again. If that doesn't work, I will try to push Marshmallow to it and try one more time. Hopefully one of them will be successful.
Ive never had issues bringing a device back on OS but this N4 is kicking my a&% bad. bought a used ( basically new ) sm-n910v it was updated to 6.0.1 mm and I'm not crazy about the MM I like KK and ive tried every firmware file known to man ive tried to slowly step back from 6.0 to 5.1.1 then 5.0 then 4.4.4 and they all fail says binary fused to boot 1 or something else and with 5.1.1 gets right to the end 99% then fails. would like to root and BL unlock any suggestions would be great. thanx in advance.
fastjohnson said:
Ive never had issues bringing a device back on OS but this N4 is kicking my a&% bad. bought a used ( basically new ) sm-n910v it was updated to 6.0.1 mm and I'm not crazy about the MM I like KK and ive tried every firmware file known to man ive tried to slowly step back from 6.0 to 5.1.1 then 5.0 then 4.4.4 and they all fail says binary fused to boot 1 or something else and with 5.1.1 gets right to the end 99% then fails. would like to root and BL unlock any suggestions would be great. thanx in advance.
Click to expand...
Click to collapse
I believe you can only get root on kk with a developer edition version of the v model. If it's a retail version and you want root it has to be at least 5.1.1 unfortunately. Have you tried the links in this post? Imo those are the best guides that I've seen to get your bootloader unlocked.
kevintm78 said:
I believe you can only get root on kk with a developer edition version of the v model. If it's a retail version and you want root it has to be at least 5.1.1 unfortunately. Have you tried the links in this post? Imo those are the best guides that I've seen to get your bootloader unlocked.
Click to expand...
Click to collapse
Yah I've tried most of them 5.1.1 gets to 98% then pooches out its exciting then bombs out, lol 4.4 doesn't get passed cache then fails. I'm using Odin 30.9, high quality data cable, thing is I can't move 》 till I can root to unlock the bootloader. My CID is 150 so that's good and I'm factory resetting the phone and pulling the SD card so it cannot mess with the flash. I'm running the NO_ A boot firmware that flashed perfect. Maybe I'm doing something wrong but I'm following the directions to the point.
fastjohnson said:
Yah I've tried most of them 5.1.1 gets to 98% then pooches out its exciting then bombs out, lol 4.4 doesn't get passed cache then fails. I'm using Odin 30.9, high quality data cable, thing is I can't move 》 till I can root to unlock the bootloader. My CID is 150 so that's good and I'm factory resetting the phone and pulling the SD card so it cannot mess with the flash. I'm running the NO_ A boot firmware that flashed perfect. Maybe I'm doing something wrong but I'm following the directions to the point.
Click to expand...
Click to collapse
It may not make a difference, but there is a newer version of Odin here that you could try.
kevintm78 said:
It may not make a difference, but there is a newer version of Odin here that you could try.
Click to expand...
Click to collapse
I'll give it a shot, right now I'm a Lil burned out on trying this because my other phone LG g4 is boot looped for no reason so I'm down to just my N4 and my N3 my gf has it. I forsee a big cup of coffee at 3am and let the flashing begin. Oh FYI I did try I think Odin 3.10 version it failed quicker so I'll try this version in the morning. I appreciate your help very much you'll be the 1st to know if it pushes through. Merry Christmas btw.
back on topic, I'm seeing kernel wakelocks for msm_hsic_host on Oscar kernel v1.3 but I'm pretty sure that was not always the case. Since that kernel hasn't been updated in a little while, I'm looking at others. Anyone got a preferred kernel with JasmineROM 7?
fz798 said:
back on topic, I'm seeing kernel wakelocks for msm_hsic_host on Oscar kernel v1.3 but I'm pretty sure that was not always the case. Since that kernel hasn't been updated in a little while, I'm looking at others. Anyone got a preferred kernel with JasmineROM 7?
Click to expand...
Click to collapse
Reflashed and thought the wakelocks were gone, but not so. msm_hsic_host appears to be related to cellular.
flyers00 said:
Kingroot was really frustrating. It would never get past 52%. After countless tries I moved to kingoroot. Kingo root worked on first try. Glad I unlocked and rooted my note 4
Click to expand...
Click to collapse
What I've noticed with this bootloader unlock is, like right now I'm 5.1.1 and my bootloader is unlocked but not rooted. OK if I use the the no A boot 6.0.1 file to flash mm it's stay unlocked and you can be rooted but if you use the normal full firmware 6.0.1 cpd1 file you lose your unlocked BL and back to start. Normally you unlock a BL it's stays unlocked no matter what you do. OK bugs with the no A boot 6.0.1 mm file no WiFi that's it. I really dislike 5.1.1 it sucks so there's not a lot of choices here. Good work on this exploit though.
Hello guys , i wanna know if the custom roms in this forum are compatible with my moto g5 Brazil version(baseband version : M8937_22.29.02.56R CEDRIC_BRAZILDSDS_CUST), a have some serious issues flashing some roms in my samsung gran prime because the version released in the world is a little different of the one released in brazil , anyone can answer me that pls ?
(Sorry my english)
Your question has been answered multiple times. Why it is so hard to use the search function?
well , i search terms like compatibility , brazil and xt1672, and nothing related show up , then i went page after page and still i found nothing related (just hardbrick under this variant)
FrancyelZelling said:
well , i search terms like compatibility , brazil and xt1672, and nothing related show up , then i went page after page and still i found nothing related (just hardbrick under this variant)
Click to expand...
Click to collapse
Hello...
Go to the guides session, there you will find some discussions on how not to brick your phone.
Read them and you should be good to go.
Basically what happens with the G5 is that you can't very simply go back to a stock Rom once you unlocked the bootloader and flashed a custom ROM.
This has to do with Custom ROMs and TWRP being 64 bit while stock firmware being 32 bit.
The hardbricks that you've mentioned happened when you've installed a custom ROM then you reverted back to stock and received an OTA update, that will definitely hard brick your device. But from what I've been reading, people going back to stock without reading anything hardbrick their G5's in general. Right way to go back to stock seems to be flashing 32 bit TWRP then finding a Stock ROM Zip file to flash with it.
But take my word with a grain of salt, I've just skimmed through some threads, don't know if I'm correct.
But it seems that as long as you use only custom roms you're good to go, the problem is if you try to go back to stock, it's not as simple as other phones, but anyways, I haven't done any of these myself, so read yourself through all of it, take A LOT of care if you ever want to go back to stock.
I personally haven't done any mods to my G5 yet, which is quite unnusual of me, simply because l don't think the Oreo ROMs available are worth unlocking the bootloader.
Namely, when we have official Oreo from Lenovo or Official lineageOS, then I think it's worth ( or not, maybe I'll root before that)
I want to add just one information, once u put a custom ROM on your phone, VoLTE is gone, in other words you won't be able to make calls using the LTE network, so your calls will be made under 3-g or GSM.
freeZbies said:
Hello...
Go to the guides session, there you will find some discussions on how not to brick your phone.
Read them and you should be good to go.
Basically what happens with the G5 is that you can't very simply go back to a stock Rom once you unlocked the bootloader and flashed a custom ROM.
This has to do with Custom ROMs and TWRP being 64 bit while stock firmware being 32 bit.
The hardbricks that you've mentioned happened when you've installed a custom ROM then you reverted back to stock and received an OTA update, that will definitely hard brick your device. But from what I've been reading, people going back to stock without reading anything hardbrick their G5's in general. Right way to go back to stock seems to be flashing 32 bit TWRP then finding a Stock ROM Zip file to flash with it.
But take my word with a grain of salt, I've just skimmed through some threads, don't know if I'm correct.
But it seems that as long as you use only custom roms you're good to go, the problem is if you try to go back to stock, it's not as simple as other phones, but anyways, I haven't done any of these myself, so read yourself through all of it, take A LOT of care if you ever want to go back to stock.
I personally haven't done any mods to my G5 yet, which is quite unnusual of me, simply because l don't think the Oreo ROMs available are worth unlocking the bootloader.
Namely, when we have official Oreo from Lenovo or Official lineageOS, then I think it's worth ( or not, maybe I'll root before that)
I want to add just one information, once u put a custom ROM on your phone, VoLTE is gone, in other words you won't be able to make calls using the LTE network, so your calls will be made under 3-g or GSM.
Click to expand...
Click to collapse
Well , if i cant go back to stock rom , it's not worth, i am in the same sittuation as you , have my phone for 8 months and i didnt even root him , my others smartphones i did within a month, but anyway , thanks man
FrancyelZelling said:
Well , if i cant go back to stock rom , it's not worth, i am in the same sittuation as you , have my phone for 8 months and i didnt even root him , my others smartphones i did within a month, but anyway , thanks man
Click to expand...
Click to collapse
It's not that you can't go back to stock...you can go but it's just not intuitive. If it was you I was just going to read through the forum because I saw some tutorials on how to go back to stock it's pretty possible it's just not simple as it was in previous Moto G edition, but it's possible.
---------- Post added at 03:33 PM ---------- Previous post was at 03:15 PM ----------
FrancyelZelling said:
Well , if i cant go back to stock rom , it's not worth, i am in the same sittuation as you , have my phone for 8 months and i didnt even root him , my others smartphones i did within a month, but anyway , thanks man
Click to expand...
Click to collapse
For example, This Thread shows you how to go back to stock using fastboot. Don't know how reliable that can be, you should research it by yourself: https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897