Did this end up in the right place this time..?
I've been trying to follow this very helpful guide by bigrammy on getting root/recovery (SuperSU and TWRP) on MM. However, something seems a little messed up on my device.
I can get as far as flashing the patched boot.img through TWRP, but from that point onwards I end up with a bootloop (even before installing SuperSU). Trimmed logcat here.
I have already attempted to figure out the issue with bigrammy's help (mostly telling me to follow the steps exactly, which I have been doing...), but I've got nowhere.
Anyone know what could be causing this despite me following the steps exactly?
Note: I've never rooted this particular device before or flashed anything to it prior to this, but it may have been a refurbished unit so heck knows what the last person did to it...
Have you unlocked your bootloader?
Related
So back when i got my nexus 4 with a stock 4.2(or 4.2.x) The first thing I did was to root it with, im pretty sure i used this guide
Now im pretty sure that after 4.3 came out i didnt do the steps to root it back, I might have though, and i wasnt sure on the status of my custom recovery either(nor the bootloader), now please forgive my ignorance for forgetting what exactly the bootloader is and what does unlocking it provide on the technical level.
Anyway my phone works well, with 4.4.2 installed, problem is i need it rooted, now i try to launch SU but it tells me there was a problem and it might have something with 4.3 . So before going here i tried to to launch custom recovery, but it says "no command" there, now im a little worried.
I might be left without a recovery.
The phone launches normally though.
As it stands the issue might be a little over my head, and I not sure on how to approach the whole situation as it seems a little complicated.
So an explanation on what have might have happened with all the nexus updates, and a clarification if its safe to flash a custom recovery the normal way? And how do i proceed to reroot the device from there(since im aware its a different matter than rooting from scratch).
Thanks in advance and hope I didnt miss anything i could do for myself before asking here.
I've this phone for a good awhile now and I followed tenfar's thread on rooting without unlocking the bootloader. A lot has transpired since I've done that and I'm a bit confused on what is the correct route for me take in order to upgrade. I have TWRP flashed also and would like to go to Lineage. If anyone could point me into the right step that would be highly appreciative.
fadetoj said:
I've this phone for a good awhile now and I followed tenfar's thread on rooting without unlocking the bootloader. A lot has transpired since I've done that and I'm a bit confused on what is the correct route for me take in order to upgrade. I have TWRP flashed also and would like to go to Lineage. If anyone could point me into the right step that would be highly appreciative.
Click to expand...
Click to collapse
use axon7toolkit...?
^Thank you. I wasn't aware of the axon 7 toolkit. I was able to unlock the bootloader and now running Lineage OS.
Hi. Couple years back, I used Towelroot to mindlessly root my SM-G900V on version 4.4.2 (no CWM, stock bootloader, locked, thanks Verizon!). Google Now crashes the minute I open it and I figure it's time to update from 4.4.2 to 5 or whatever is stable these days. I'm paranoid to do this without running it by you gurus here, because I don't want to lose root, brick my phone, or turn it into a flaming fireball of doom. Can someone point me to a thread I overlooked or just type a few easy-to-follow steps with link to ROM so I can upgrade my Galaxy S5?
Is a downgrade back to 4.4.2 possible if I don't like the upgrade?
Thanks in advance!
androidman807 said:
Can someone point me to a thread I overlooked
Click to expand...
Click to collapse
https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Thanks. I've spent a couple of hours and am on post 171 of the thread. I'm a CID 11 that needs to follow those steps on post 3. Regardless, this seems to be designed to take me from Kitkat to Marshmallow, skipping me right past the land of Lollipop. I haven't tried it yet, but 2 questions:
1) once in Marshmallow, can I get back to Lollipop or Kitkat?
2) the intro to the steps say that CID=11 needs SafeStrap or Flashfire, but the actual steps never mention Flashfire (only safestrap). Is it truly either/or, or is there an advantage to SS?
Thanks!
bbsc said:
https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Click to expand...
Click to collapse
1. Lollipop - yes, Kitkat - no.
2. You still can use SS on MM. It's a little tricky but still possible.
Flashfire requires root so it will not work on MM for CID 11.
This thread may also be useful for understanding the things: https://forum.xda-developers.com/ve...al/guide-painiacs-essential-guide-to-t3319848
I'll check out that thread (thank you for that), but I'm confused by something you wrote: "Flashfire requires root so it will not work on MM for CID 11." My Kitkat currently has root. Are you suggesting that when I throw Marshmallow on it I'll lose it?
And if you all will allow me to hijack my own thread, is Marshmallow really worth the upgrade from Lollipop? Heck, is Lollipop that much better than Kitkat? I've got a (mostly) working rooted system now, and it sounds like I can go up to 6 and back down to 5, but never again back to 4, hopefully keeping root the whole journey.
Thanks for reading and helping a new guy out. I figure others will find this information helpful down the road, as 4.4.2 was easy to root.... but where (if anywhere) from here?
bbsc said:
1. Lollipop - yes, Kitkat - no.
2. You still can use SS on MM. It's a little tricky but still possible.
Flashfire requires root so it will not work on MM for CID 11.
This thread may also be useful for understanding the things: https://forum.xda-developers.com/ve...al/guide-painiacs-essential-guide-to-t3319848
Click to expand...
Click to collapse
androidman807 said:
My Kitkat currently has root. Are you suggesting that when I throw Marshmallow on it I'll lose it?
Click to expand...
Click to collapse
Yes.
You say your phone has CID11. For SM-G900V it means it has a locked bootloader that cannot be unlocked (currently, but most likely - never).
Locked bootloader is called so because it's locked to boot only certain digitally signed kernel (aka boot.img)
Root on MM requires a modified kernel which cannot be booted by a locked bootloader.
That's why you cannot have root on MM and will lose it when upgrading.
androidman807 said:
is Marshmallow really worth the upgrade from Lollipop?
Click to expand...
Click to collapse
Only you can answer for yourself.
What are you using root for?
I have 4 or 5 S5s (G900V) here running MM and only one (mine) is rooted. No claims so far They just work.
BTW, all of them are running Devbase-4.2 from Alexndr.
If you're on Verizon you may like one of stock debloated ROMs which can be found in this section.
Thanks for all your help.
Reading the first few posts here really helped a lot to get a background. Then I attempted the steps here you provided on post 3 for my 11.
I thought I could pick my build after reading painiac's post, and was shy about going all the way up to PB1, but all the ones I chose wouldn't TowelRoot. I really did have to follow the instructions as written and use the COMBINATION EMMC ROM provided there. It freaked me out at first that it ended me up in Kitkat, but the final step brought up Lollipop and completed the process well.
The one scary point is after I ran Titanium getting ready to put some apps back on and used the "restore previous ID" it gave a panic, took me back to recovery and froze... required removing the battery, where normally that just causes a reboot. I did read the part in Painiac's post where he says don't restore system app (I had to export and import my contacts using the phone app to SD card and not Titanium - that worked). I hope my "restore previous ID" didn't go against his advice.
Other than that, things seem to be working smoothly now. I'm on Lollipop PB1 and not sure I even need Marshmallow. Thanks for all your help.
bbsc said:
Yes.
You say your phone has CID11. For SM-G900V it means it has a locked bootloader that cannot be unlocked (currently, but most likely - never).
Locked bootloader is called so because it's locked to boot only certain digitally signed kernel (aka boot.img)
Root on MM requires a modified kernel which cannot be booted by a locked bootloader.
That's why you cannot have root on MM and will lose it when upgrading.
Only you can answer for yourself.
What are you using root for?
I have 4 or 5 S5s (G900V) here running MM and only one (mine) is rooted. No claims so far They just work.
BTW, all of them are running Devbase-4.2 from Alexndr.
If you're on Verizon you may like one of stock debloated ROMs which can be found in this section.
Click to expand...
Click to collapse
A couple of months back, I updated from Kitkat to Lollipop using the instructions below, and ever since, I've had two persistent problems, and I'm wondering if anyone else has:
1) Wi-fi cuts out every few days requiring a reboot fix. This seems to be related to DNS.
2) Receiving picture texts (MMS) show up as "Message size: 2KB Expires: (date)" with no way to download or view. I see no workaround other to tell friends to email me pictures instead of texting them.
I've tried a factory reset, but haven't gone back to Odin yet to try to put PB1 on again (or a different ROM?). The good news is SafeStrap recovery is on the phone now. What can I try next to resolve these two problems? I can live with them with the reboot and avoiding MMS, but they are not trivial.
Thanks for any guidance or advice. Please help.
androidman807 said:
Thanks for all your help.
Reading the first few posts here really helped a lot to get a background. Then I attempted the steps here you provided on post 3 for my 11.
I thought I could pick my build after reading painiac's post, and was shy about going all the way up to PB1, but all the ones I chose wouldn't TowelRoot. I really did have to follow the instructions as written and use the COMBINATION EMMC ROM provided there. It freaked me out at first that it ended me up in Kitkat, but the final step brought up Lollipop and completed the process well.
The one scary point is after I ran Titanium getting ready to put some apps back on and used the "restore previous ID" it gave a panic, took me back to recovery and froze... required removing the battery, where normally that just causes a reboot. I did read the part in Painiac's post where he says don't restore system app (I had to export and import my contacts using the phone app to SD card and not Titanium - that worked). I hope my "restore previous ID" didn't go against his advice.
Other than that, things seem to be working smoothly now. I'm on Lollipop PB1 and not sure I even need Marshmallow. Thanks for all your help.
Click to expand...
Click to collapse
Well the title says alot... let me explain..
I've got a note 5 and LG g5. This note 3 is an extra phone. So I figured I would root and rom it.
I started on 4.4.2 and it wouldn't boot...
Ran Odin 3.09 and loaded pl1...couldn't root.
Ran Odin 3.09 again with ob6. Root success.
I then followed instructions for unlock_n3 for the bootloader and also installed twrp.
Last night I went on a spree with roms trying to find a working rom with data... no success... I felt like I was doing something wrong so I went back to Odin and ran ob6 again which is where I'm at now.
In the process I dev'd my phone... and now I cannot get root and lost twrp in the process.
Did I eff up?
What's next from here? I don't care about Knox and like I said I've got 2 other phones both working and paid off. This is my "car phone". I use it for music and that's about it. That being said I would rather have working data instead of using my note 5 with Hotspot mode.
My device is now hlte... not hltevzw... I think I did something very wrong. Please halp.
If it helps I did take pictures along the way when running the unlock_n3 over adb. I've got the original emmc ID but I'm not sure if this step is reversable.
I also made a backup with twrp... but it seems my SD card was wiped at some point last night.
Please don't flame... I admit this was my stupidity and I'm sure I'm not the only one who makes mistakes. At this point I'll be happy with anything 5.0 and root. As I said above if Knox is a concern I don't really care. Phones paid off... and I've got a note 5 and when that dies I'll get a 7. Also have LG g5 as a backup.
What are my options now oh wise xda gods?
Edit: I ran arabictool again, and got a 5.0 not found error. Decided to try kingoroot, and it says succeeded, however upon running root checker, it says "Sorry! Root access is not properly installed on this device"
Edit2: After trying edit 1... im now im a bootloop, and I check vol+, home, and power and twrp is indeed gone.
When I get home I plan to Odin OB6 again, as it worked, and since i've already done it once I assume I cant do any further damage :\
Edit3: I've successfully flash back to OB6, and as expected, ive finally tripped knox. Damn near 5 years with a note 3, and JUST tripped it. Not bad if I do say so my self... although, theres still more work to be done :\
GGRRRR, I wont give up so easily! But I could use some advice
tbonedude said:
Well the title says alot... let me explain..
I've got a note 5 and LG g5. This note 3 is an extra phone. So I figured I would root and rom it.
I started on 4.4.2 and it wouldn't boot...
Ran Odin 3.09 and loaded pl1...couldn't root.
Ran Odin 3.09 again with ob6. Root success.
I then followed instructions for unlock_n3 for the bootloader and also installed twrp.
Last night I went on a spree with roms trying to find a working rom with data... no success... I felt like I was doing something wrong so I went back to Odin and ran ob6 again which is where I'm at now.
In the process I dev'd my phone... and now I cannot get root and lost twrp in the process.
Did I eff up?
What's next from here? I don't care about Knox and like I said I've got 2 other phones both working and paid off. This is my "car phone". I use it for music and that's about it. That being said I would rather have working data instead of using my note 5 with Hotspot mode.
My device is now hlte... not hltevzw... I think I did something very wrong. Please halp.
If it helps I did take pictures along the way when running the unlock_n3 over adb. I've got the original emmc ID but I'm not sure if this step is reversable.
I also made a backup with twrp... but it seems my SD card was wiped at some point last night.
Please don't flame... I admit this was my stupidity and I'm sure I'm not the only one who makes mistakes. At this point I'll be happy with anything 5.0 and root. As I said above if Knox is a concern I don't really care. Phones paid off... and I've got a note 5 and when that dies I'll get a 7. Also have LG g5 as a backup.
What are my options now oh wise xda gods?
Edit: I ran arabictool again, and got a 5.0 not found error. Decided to try kingoroot, and it says succeeded, however upon running root checker, it says "Sorry! Root access is not properly installed on this device"
Edit2: After trying edit 1... im now im a bootloop, and I check vol+, home, and power and twrp is indeed gone.
When I get home I plan to Odin OB6 again, as it worked, and since i've already done it once I assume I cant do any further damage :\
Edit3: I've successfully flash back to OB6, and as expected, ive finally tripped knox. Damn near 5 years with a note 3, and JUST tripped it. Not bad if I do say so my self... although, theres still more work to be done :\
GGRRRR, I wont give up so easily! But I could use some advice
Click to expand...
Click to collapse
You need to go thru your original steps again, root, unlock and then TWRP make sure it is the hltevzw version,
Sent from my SM-N900V using Tapatalk
donc113 said:
You need to go thru your original steps again, root, unlock and then TWRP make sure it is the hltevzw version,
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply, as of edit 3, I am back on OB6, and cannot seem to get root. Are my chances better with OF1?
Ive tried yemen tools (says 5.0 not found)
I've tried kingo root (says successful, never reboots, and shows "this phone root isnt properly setup" when checking with root checker from joey kilm (think thats his name)
Does it matter my emmc ID is ending with 43100?
https://cdn.discordapp.com/attachments/221482708063223809/378367914388094981/image.png <- image from unlock_n3 after success, emmc checker shows same value AFTER odin ob6 (this held, nothing else did)
Edit: After taking donc's recommendation of OF1, I am now able to run yemen tools. As a side note, I seem to have more bars of service with OF1... coincidence?
Edit2: I HAVE ROOT! on OF1 using yemen tools (downgraded from PL1 to OB6 finally to OB1 and it worked.) Now to re-unlock bootloader. Thanks guys for the support thus far, this is a journey and having qualified accomplices makes this SOOOO much easier.
So heres where im at now.. as a recap for personal use, and anyone else who may be on a similar path.
Start to finish, this is what I did, where im at now, and where I want to be by tonight
Got phone, 4.4.2 with bootloop, couldn't find 4.4.2 firmware online
Flashed 5.0 (PL1), no root available.
Flashed 5.0 (OB6) rooted, unlocked boot loader, twrp, played with roms, got frustrated, re-flashed OB6 and couldn't root again (seems flimsy)
Flashed 5.0 (OF1) rooted, unlocked boot loader, verified several times root is working. Installed SuperSu and busybox.
This is where im at now, about to install twrp since i've done this already with ob6, and was working fine (though, I would prefer to have philz, and multi rom slots)
This entire process i've been using Odin 3.09, Twrp 3.0.2-1. My note 3 has been changed to a dev ID ending in 3100 (see above posts) this seems to have held through entire process with multiple recoveries.
I am going to make a full backup (again...) and unlike last time... store this copy onto my PC instead of SDcard alone... this was my mistake, and I need to learn from it.
For the @dev's out there, is there anything I can provide to help this overall process and community in general? I'm fairly literate in adb/linux and have no issues running commands, uploading files, or anything similar.
Shout out to @donc113 above for stating the obvious (since i failed to search and find the proper methods) as well as giving me the kick in the pants I needed to push onwards and succeed. Thanks brotha. :good:
tbonedude said:
So heres where im at now.. as a recap for personal use, and anyone else who may be on a similar path.
Start to finish, this is what I did, where im at now, and where I want to be by tonight
Got phone, 4.4.2 with bootloop, couldn't find 4.4.2 firmware online
Flashed 5.0 (PL1), no root available.
Flashed 5.0 (OB6) rooted, unlocked boot loader, twrp, played with roms, got frustrated, re-flashed OB6 and couldn't root again (seems flimsy)
Flashed 5.0 (OF1) rooted, unlocked boot loader, verified several times root is working. Installed SuperSu and busybox.
This is where im at now, about to install twrp since i've done this already with ob6, and was working fine (though, I would prefer to have philz, and multi rom slots)
This entire process i've been using Odin 3.09, Twrp 3.0.2-1. My note 3 has been changed to a dev ID ending in 3100 (see above posts) this seems to have held through entire process with multiple recoveries.
I am going to make a full backup (again...) and unlike last time... store this copy onto my PC instead of SDcard alone... this was my mistake, and I need to learn from it.
For the @dev's out there, is there anything I can provide to help this overall process and community in general? I'm fairly literate in adb/linux and have no issues running commands, uploading files, or anything similar.
Shout out to @donc113 above for stating the obvious (since i failed to search and find the proper methods) as well as giving me the kick in the pants I needed to push onwards and succeed. Thanks brotha. :good:
Click to expand...
Click to collapse
You're welcome. Just an FYI, the ending of the CID doesn't matter, it's the first 2 numbers that count, and they MUST be 15
I used Flashify (available on Google Play) to load TWRP... worked great (but you must have root and busybox installed to use it to flash TWRP)
Sent from my SM-N900V using Tapatalk
I've been combing the forums for a couple of weeks trying to get information about upgrading my old note 4 (Verizon, MarshMellow). I wanted to use the Lineage OS 18.1 but I can't find a way to unlock the bootloader. I've tried every method without success. None of the temp root programs seem to work. Odin gets close and then fails at the end. Same for ADB. I can't seem to get a clear answer to a question: Do you have to downgrade to 5.11 before attempting any of this? If so, how is that done on this phone? It is alluded to but not clearly stated anywhere. I'm willing to do the legwork, I just need a clear starting point.
Thanks
To unlock a device's bootloader it's NOT required device's Android is got rooted.
To flash a custom ROM like LOS you have to find a suitable custom Recovery for your device and flash this as 1st thing of all things.
Thanks for the response. That's what has been confusing. Most of the procedures I've read (some of them older) state the the first step is to temp root with Kingroot or similar. These don't work on my phone so I haven't gotten very far. Others want you to unlock the bootloader first. Same problem, can't find a way to to that in this phone that works. I'm pretty OCD so I'll keep searching.
@docsquic
[Official] Note 4 Verizon Bootloader Unlock
Enjoy. Don't forget to thank beaups too, he discovered the eMMC backdoor and exploited it! UPDATE: [8/2/16] I have recompiled the binary to fix issues with older ROMs like 4.4. This should fix all the issues with "This is for samsung device...
forum.xda-developers.com
If you are using an SM-910 with a locked bootloader, like the 910V, then the answer is an unequivocal YES you must first unlock the bootloader before you can accomplish anything substantive with it, and to do that YES you must also downgrade to 5.1.1 to root it and unlock the bootloader. And your device must have a CID 15 eMMC chip to achieve any of this.