Related
i want to root my phone but Sprint seems to have patch the root exploit, so i am thinking of doing a factory restore.
does anyone know what software version it will resort back to, currently i am on 2.3.4.
You will still be on 2.3.4 you need to search for the method then reds until your head hurts
[.-.]
http://forum.xda-developers.com/showthread.php?t=1357157
This root method works wonders nothing is more better then to learn to manually root your device. Of course you can use the tool provided in the, the development forums, but I personally enjoy learning to do things without the use of developed tools.
If you need help feel free to ask we are here to help ^_^
Good luck don't turn your device into a brick READ READ AND READ FOLLOW INSTRUCTIONS EXACTLY HOW THEY ARE YOU WILL BE A OK.
Sent from my PG06100 using xda app-developers app
x2phrack said:
i want to root my phone but Sprint seems to have patch the root exploit, so i am thinking of doing a factory restore.
does anyone know what software version it will resort back to, currently i am on 2.3.4.
Click to expand...
Click to collapse
Use the manual method by Indirect if you want to have more control over what you're doing (also does not void your warranty) and definitely read read read
I would recommend at least going through the whole "user" section of xda-university before even touching your phone, it has tons of useful information
turkbot said:
You will still be on 2.3.4 you need to search for the method then reds until your head hurts
[.-.]
Click to expand...
Click to collapse
Definitely, also just FYI but when you do a factory restore that simply wipes all app data (both user and system apps)
x2phrack said:
i want to root my phone but Sprint seems to have patch the root exploit, so i am thinking of doing a factory restore.
does anyone know what software version it will resort back to, currently i am on 2.3.4.
Click to expand...
Click to collapse
Best advice I can give you is to Read, Read, Read, and Read some more. Use the search function a ton, as it will help you to get used to resolving issues in the future. Because sometimes even when people are willing to help, answers are hard to come by. Also there are a few links you can check out in my Signature. The Shift community is one of the Best anywhere, so you picked the right device to learn Android with . Welcome to a great forum.
yes yes, i have rooted like 5 phones, but this one is stuck in a boot loop and trying to fix that
x2phrack said:
yes yes, i have rooted like 5 phones, but this one is stuck in a boot loop and trying to fix that
Click to expand...
Click to collapse
Were you rooting with Indirects method and it got stuck in a bootloop on the 4G screen? If so, thats supposed to happen, its not a bug
CNexus said:
Were you rooting with Indirects method and it got stuck in a bootloop on the 4G screen? If so, thats supposed to happen, its not a bug
Click to expand...
Click to collapse
Na i was using you shift rootility tutorial, but i screwed up and put the wrong PG06IMG.zip in the $path. there was 2 versions a 12.7MB and a 227MB one. i didn't realize that i needed to do the 227MB to downgrade first then after it's downgraded then use the 12.7MB one.
so i stopped mid way through and tried to boot normally, which sent me into a boot loop. doing a factory restore fixed the boot-loop and now i am starting over again.
BTW CNexus you have some dead links in your Tut.
You will be on older radios after rooting. Download the ZIP with the most recent radios, WiMAX, and touchscreen firmware from HERE or HERE.
Click to expand...
Click to collapse
Points to dead files / links
x2phrack said:
Na i was using you shift rootility tutorial, but i screwed up and put the wrong PG06IMG.zip in the $path. there was 2 versions a 12.7MB and a 227MB one. i didn't realize that i needed to do the 227MB to downgrade first then after it's downgraded then use the 12.7MB one.
so i stopped mid way through and tried to boot normally, which sent me into a boot loop. doing a factory restore fixed the boot-loop and now i am starting over again.
BTW CNexus you have some dead links in your Tut.
Points to dead files / links
Click to expand...
Click to collapse
Thanks for pointing that out! There are more recent links in the last 2 pages if you want to grab that file right now
EDIT: Links fixed, thanks again
CNexus said:
Thanks for pointing that out! There are more recent links in the last 2 pages if you want to grab that file right now
EDIT: Links fixed, thanks again
Click to expand...
Click to collapse
not a problem, so i should use the 12.7 zip after i have rooted the 2.2 before i use add the Cyanogen Rom or after?
x2phrack said:
not a problem, so i should use the 12.7 zip after i have rooted the 2.2 before i use add the Cyanogen Rom or after?
Click to expand...
Click to collapse
It doesn't matter, you can do it anytime after you have rooted (make sure you flash it in bootloader and not through recovery though)
Is it possible to root one plus one, without deleting any data and apps from it? I just want root access but don't want any custom rom.
yes, of course..
root doesn't delete any of your data
senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
Thanks for that. How can I do that?
#newtorooting
senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
sourabhkejriwal said:
Thanks for that. How can I do that?
#newtorooting
Click to expand...
Click to collapse
Sorry you got your hopes up, but the other poster isn't right. As per my reply to him you need to unlock your bootloader first, which is going to wipe your device. I'd suggest backing up any files that you have that are important to you. As for your apps and settings, you'll have to set them up again afterwards. Go to my guide thread here:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
You need to follow (in order) sections 1, 2, 3, and 4. This will give you root access on your stock ROM. You should also follow section 10, it's very important that you make a backup of your EFS partition.
timmaaa said:
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.[
Click to expand...
Click to collapse
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
Step-7: If you want to root the phone without installing TWRP recovery, type the following command
fastboot boot twrp.img
Click to expand...
Click to collapse
I guess the real question being, why would you need a custom recovery?
pdhx said:
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
I guess the real question being, why would you need a custom recovery?
Click to expand...
Click to collapse
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Transmitted via Bacon
The default recovery will only flash cm signed zip, which is another reason for needing a custom recovery. That method you mention at ibtimes meant that it would allow you to, for one boot cycle, do a "live boot" of twrp
Sent From Lollipopified Bacon Goodness!
But how is anything going to be written to the system partition if it is locked ?
timmaaa said:
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Click to expand...
Click to collapse
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
pdhx said:
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
Click to expand...
Click to collapse
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
what do get when you type fastboot devices ?
bombadier said:
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
Click to expand...
Click to collapse
Which seems to be somewhat limiting for such an otherwise developer friendly device?
bombadier said:
what do get when you type fastboot devices ?
Click to expand...
Click to collapse
Nada, nothing, nil. however, "adb devices" works fine... WTF?
pdhx said:
Which seems to be somewhat limiting for such an otherwise developer friendly device?
Nada, nothing, nil. however, "adb devices" works fine... WTF?
Click to expand...
Click to collapse
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
bombadier said:
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
Click to expand...
Click to collapse
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
pdhx said:
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
Click to expand...
Click to collapse
They're "forcing" you to unlock the bootloader in order to root the device because that's the universally accepted standard (unlock bootloader, install custom recovery, flash root). Some devices have super secure bootloaders and that's why you end up needing to use hacks to get those devices rooted, but that isn't the normal way to go about it. Anyway, there's no advantage to leaving the bootloader at all. There's also no disadvantage to unlocking the bootloader at all. You might say that the fact that the device is wiped during the unlocking process is a disadvantage, but that fact is very well documented both here, on the OnePlus forums, and pretty much any other reputable tech site that mentions unlocking the bootloader on this phone. The point to that last sentence? It pays to research a device thoroughly before buying it, or before using it, the wiping of the device is no issue at all if you do it when you receive the phone (prior to using it), like many people have. But in your situation you're just going to have to backup any important media from the phone prior to unlocking.
Anyway, on to your fastboot issue. Exactly which drivers do you have installed on your PC? Do you have any other phone drivers or software installed on the PC? And do you have access to another PC in case the one you're using is the source of the issue?
Got it, 27th try (give or take) is the charm.... Had to use USBdeview and uninstall the Google and the Qualcomm drivers. Reinstalled the Google drivers (after a reboot) and got it to work. Guess I could have figured that out from dev manager by watching what drivers got activated while fastboot was active but nothing ever jumped out at me as an obvious culprit.
Interesting to note that TWRP now automatically prompts you to install SuperSU if you reboot after installing it. Maybe it found the zip but either way, nice touch!
Now to go and decide what ROM to install....
Thanks for your help!
I would suggest temasek unofficial cm12 ROM. Been using it pretty much as a daily driver since version 1.something of the ROM and no problems. At this point it's been almost a month of not having to boot into my cm11s ROM lol. I use it with AK kernel, seems like a good match cuz both devs are working together looks like. Flash AK ukm special edition after flashing his kernel and install synapse from play store if you want to play around with settings of the kernel
Sent From Lollipopified Bacon Goodness!
zenix23456 said:
I have been using AnyRooter for months and it is quite good to root OnePlus phones.
Click to expand...
Click to collapse
Except the Oneplus One.
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
Device-State:Recovery/Bootloader
Ellipsis 8
QTAQZ3
Vendor:Verizon Wireless
Build:KTO49
4.2KitKat
samson716 said:
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
?
Click to expand...
Click to collapse
You want help with a device but you don't tell us any kind of information about your device, how smart was that? What you need and how to do it can depend on what device model number you have.
Sent from my SM-S903VL using Tapatalk
SORRY
Droidriven said:
You want help with a device but you don't tell us any kind of information about your device, how smart was that? What you need and how to do it can depend on what device model number you have.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3/4.2Jellybean/KTO49
samson716 said:
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3
4.2Kitkat
KTO49
Thanks!
Click to expand...
Click to collapse
samson716 said:
samson716 said:
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3
4.2Kitkat
KTO49
Thanks!
Click to expand...
Click to collapse
are you using stock recovery or a custom recovery?
Click to expand...
Click to collapse
ayu321 said:
samson716 said:
are you using stock recovery or a custom recovery?
Click to expand...
Click to collapse
Stock
Click to expand...
Click to collapse
samson716 said:
ayu321 said:
Stock
Click to expand...
Click to collapse
Can you please tell me that what caused this problem ? what were you doing with the device? flashing roms ?
Click to expand...
Click to collapse
ayu321 said:
samson716 said:
Can you please tell me that what caused this problem ? what were you doing with the device? flashing roms ?
Click to expand...
Click to collapse
No I was literally doing nothing I was actually flashing my Samsung Device at that moment. From what I remember it occurred when I noticed at update to marshmallow updated then rebooted it. Ever since its been in this bootloop! Im not trying to root it put a custom rom on it just want it to function nothing special.
Click to expand...
Click to collapse
samson716 said:
ayu321 said:
No I was literally doing nothing I was actually flashing my Samsung Device at that moment. From what I remember it occurred when I noticed at update to marshmallow updated then rebooted it. Ever since its been in this bootloop! Im not trying to root it put a custom rom on it just want it to function nothing special.
Click to expand...
Click to collapse
You have soft bricked your phone . The only way to fix it is it flash its stock rom. If you are new to this stuff I would suggest you to read this article carefully and if you have any doubts , ask me.
https://www.maketecheasier.com/android-root-custom-recovery-and-roms/
Click to expand...
Click to collapse
samson716 said:
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
Device-State:Recovery/Bootloader
Ellipsis 8
QTAQZ3
Vendor:Verizon Wireless
Build:KTO49
4.2KitKat
Click to expand...
Click to collapse
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a device exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
ayu321 said:
samson716 said:
You have soft bricked your phone . The only way to fix it is it flash its stock rom. If you are new to this stuff I would suggest you to read this article carefully and if you have any doubts , ask me.
https://www.maketecheasier.com/android-root-custom-recovery-and-roms/
Click to expand...
Click to collapse
Okay not sure which Flash tool to use nor get my stock rom I dread to say but i dont think there is one available. Its a generic tablet its made by Quanta. Not sure how to put it in a download mode either I assume ADB is the only way to transfer any files.
Click to expand...
Click to collapse
Your device probably uses SPFlashtool or fastboot.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a deuce exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Its pretty easy to fix a soft bricked device , even if stock rom isnt available , any rom compatible with his device can fix the issue .
ayu321 said:
Its pretty easy to fix a soft bricked device , even if stock rom isnt available , any rom compatible with his device can fix the issue .
Click to expand...
Click to collapse
To be compatible, the ROM typically has to be ported and that usually requires the stock firmware or stock source from the device that the ROM is being ported over to. 99% of the time you can't just flash a ROM from a different model number, even if the CPU is the same, there's quite a bit more to it than that. The android operating system is built for the specific hardware it is installed on, the two devices would have to be exactly the same and have the exact same components, any differences in hardware make he firmwares incompatible.
For this particular device, I doubt the stock firmware or stock source code area available, even if it were, porting another ROM wouldn't be necessary because if it were available it could just be flashed with that instead of porting a ROM.
About the only time a ROM from a different model number can be used without any porting or edits being made is when the devices are exactly the same device just rebranded with a different "name".
But thanks for trying to tell me something that you thought I didn't know, now it seems I've told you something that you didn't know.
Sent from my SM-S903VL using Tapatalk
samson716 said:
ayu321 said:
Okay not sure which Flash tool to use nor get my stock rom I dread to say but i dont think there is one available. Its a generic tablet its made by Quanta. Not sure how to put it in a download mode either I assume ADB is the only way to transfer any files.
Click to expand...
Click to collapse
1.Search for your tablet's root package , download it and move it to your tablet's sd card. Then enter your recovery mode by pressing power button+ Home button+ Volume button at same time for 10sec. Once entered , go to option "apply update from sd card" and select the root package you downloaded. (CONGRATS YOU HAVE ROOTED YOUR PHONE!)
2.Search for your tablet's 'custom recovery' , download it and flash it through odin tool(pc) .
3.Final Step ! BASED ON THE RECOVERY YOU FLASHED THESE STEPS MAY DIFFER , SO REPLY ME IF YOU SUCCEED IN FLASHING CUSTOM RECOVERY
Click to expand...
Click to collapse
ayu321 said:
1.Search for your tablet's root package , download it and move it to your tablet's sd card. Then enter your recovery mode by pressing power button+ Home button+ Volume button at same time for 10sec. Once entered , go to option "apply update from sd card" and select the root package you downloaded. (CONGRATS YOU HAVE ROOTED YOUR PHONE!)
2.Search for your tablet's 'custom recovery' , download it and flash it through odin tool(pc) .
3.Final Step ! BASED ON THE RECOVERY YOU FLASHED THESE STEPS MAY DIFFER , SO REPLY ME IF YOU SUCCEED IN FLASHING CUSTOM RECOVERY
Click to expand...
Click to collapse
Odin is for Samsung devices, not other devices.
The device they are repairing is not a Samsung device. They have this device and a Samsung device. The issue on this device occurred while they were in the process of flashing their Samsung device.
I know you're trying to help but don't post anything unless you are absolutely certain that you know what you're talking about.
In this case, you didn't and that can easily lead to a hard bricked device because they followed your instruction.
Stick to answering questions about devices you personally have dealt with, don't go assuming that you understand someone else's device. They are all different, the methods, tricks and tools for one won't necessarily work on another.
You understand android somewhat but judging by your posts, you don't understand the differences in devices and methods. But you will after you've been here a while.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 10:39 PM ---------- Previous post was at 10:32 PM ----------
DO NOT USE ODIN ON YOUR DEVICE!!!
Odin is only for Samsung devices.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a device exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
thankyou so much for the fast responses much appreciated to take your time to explain. Okay i have a question what would be the course of detailed action to preform getting any and all missing .img's it may need. Also i know its a crazy question but would i be able to preform this in store with the displayed tablet that matches mine? How difficult is something like this, and is there any other methods at all I can try to boot past this bootloader. And now that i remember correctly from reading others this happened when I upgraded to 5.1 or 5.0 thank you everybody once again!
samson716 said:
thankyou so much for the fast responses much appreciated to take your time to explain. Okay i have a question what would be the course of detailed action to preform getting any and all missing .img's it may need. Also i know its a crazy question but would i be able to preform this in store with the displayed tablet that matches mine? How difficult is something like this, and is there any other methods at all I can try to boot past this bootloader. And now that i remember correctly from reading others this happened when I upgraded to 5.1 or 5.0 thank you everybody once again!
Click to expand...
Click to collapse
No, you wouldn't be able to get it from a tablet in the store, it's a rather involved process that requires connecting the device to PC, it also requires rooting the device and flashing a custom recovery, and that's all before you actually get to where you can pull the files. It'll take a couple of hours,or more to do it.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
No, you wouldn't be able to get it from a tablet in the store, it's a rather involved process that requires connecting the device to PC, it also requires rooting the device and flashing a custom recovery, and that's all before you actually get to where you can pull the files. It'll take a couple of hours,or more to do it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Is there absolutely anything i can try, just a long shot in the dark?
samson716 said:
Is there absolutely anything i can try, just a long shot in the dark?
Click to expand...
Click to collapse
The only other option is pretty risky. You can try a firmware from another device that has the same CPU and hardware as your device, you'd have to compare specs. It would have to have the same CPU, same screen resolution, same camera(front and rear), same amount of RAM, same amount of internal storage, same accelerometers, etc.. It has to have all the same components that yours has.
Sent from my SM-S903VL using Tapatalk
I do have experience flashing phones. I don't need help with adb and fastboot.
I am just confused at to what exactly TWRP is? Is that the recovery? What should I flash to my phone?
Either way, I just want to root my phone and install a custom rom to it...but I don't see many or any custom roms except for TWRP...so really just want root above all else
Please tell me what I need to do and in what order...lol.....thank you
ImIntoStuff said:
I do have experience flashing phones. I don't need help with adb and fastboot.
I am just confused at to what exactly TWRP is? Is that the recovery? What should I flash to my phone?
Either way, I just want to root my phone and install a custom rom to it...but I don't see many or any custom roms except for TWRP...so really just want root above all else
Please tell me what I need to do and in what order...lol.....thank you
Click to expand...
Click to collapse
TWRP is custom recovery. It's still in beta.
As far as I know, there are no custom roms. 8.1 is too new and they are still working on things.
Root with Magisk. Plenty of how to threads.
Sent from my Pixel 2 using Tapatalk
ImIntoStuff said:
I do have experience flashing phones. I don't need help with adb and fastboot.
I am just confused at to what exactly TWRP is? Is that the recovery? What should I flash to my phone?
Either way, I just want to root my phone and install a custom rom to it...but I don't see many or any custom roms except for TWRP...so really just want root above all else
Please tell me what I need to do and in what order...lol.....thank you
Click to expand...
Click to collapse
Diesel_Jeremiah said:
TWRP is custom recovery. It's still in beta.
As far as I know, there are no custom roms. 8.1 is too new and they are still working on things.
Root with Magisk. Plenty of how to threads.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
TWRP actually just came out of beta with 12/12 Walleye(12/14 Taimen) build, hopefully there will be some custom roms soon... You can use the Skipsoft Android toolkit to root, unlock, flash twrp etc. Or do it manually following guides here on XDA under development section https://forum.xda-developers.com/pixel-2/development, ADB has been updated so make sure to have the latest platform tools.
Currently theres no custom ROMs at all for Pixel 2.
TWRP is a recovery.
Rooting is pretty straight-forward I studied these 2 articles/thread:
http://highonandroid.com/android-smartphones/how-to-root-pixel-2-or-pixel-2-xl-easiest-method/
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
The kind of confusing part is when you want to change custom kernels and update TWRP.
As the recovery, kernel and root stuff all play around in the same partition now.
Read around the forum, since you got experience you will figure it out.
bland.life said:
Currently theres no custom ROMs at all for Pixel 2.
TWRP is a recovery.
Rooting is pretty straight-forward I studied these 2 articles/thread:
http://highonandroid.com/android-smartphones/how-to-root-pixel-2-or-pixel-2-xl-easiest-method/
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
The kind of confusing part is when you want to change custom kernels and update TWRP.
As the recovery, kernel and root stuff all play around in the same partition now.
Read around the forum, since you got experience you will figure it out.
Click to expand...
Click to collapse
Ok I have TWRP installed and have it rooted, because root checker confirmed it.
I am currently installing busybox, not even sure why but I think I want it. Anyone want to tell me what it is specifically for? Also the app runs, says installing busybox and just hangs forever. Currently trying to let the smart install do it's thing and not move focus away from the busybox installing page
ImIntoStuff said:
Ok I have TWRP installed and have it rooted, because root checker confirmed it.
I am currently installing busybox, not even sure why but I think I want it. Anyone want to tell me what it is specifically for? Also the app runs, says installing busybox and just hangs forever. Currently trying to let the smart install do it's thing and not move focus away from the busybox installing page
Click to expand...
Click to collapse
Oh, and android reports a problem with called "Android System - There's an internal problem with your device. Contact your manufacturer for details."
What is causing that to be reported every time I restart?
ImIntoStuff said:
Ok I have TWRP installed and have it rooted, because root checker confirmed it.
I am currently installing busybox, not even sure why but I think I want it. Anyone want to tell me what it is specifically for? Also the app runs, says installing busybox and just hangs forever. Currently trying to let the smart install do it's thing and not move focus away from the busybox installing page
Click to expand...
Click to collapse
Oh, and android reports a problem with called "Android System - There's an internal problem with your device. Contact your manufacturer for details."
What is causing that to be reported every time I restart?
ImIntoStuff said:
Oh, and android reports a problem with called "Android System - There's an internal problem with your device. Contact your manufacturer for details."
What is causing that to be reported every time I restart?
Click to expand...
Click to collapse
Pretty sure that is the same for everyone according to the reading I've done. I'm looking to do the same with mine. What method did you use? Any snags?
Sent from my Pixel 2 using Tapatalk
Tucker204 said:
Pretty sure that is the same for everyone according to the reading I've done. I'm looking to do the same with mine. What method did you use? Any snags?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Oh..so the android system error always happens? Ok..it does not seem to affect anything.
I used the Skipsoft package, which does all the things. Couple snags, it only wanted to accept the beta of magisk.
I'm thinking I got it all right now. I will report back if I find a problem
Tucker204 said:
Pretty sure that is the same for everyone according to the reading I've done. I'm looking to do the same with mine. What method did you use? Any snags?
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
So rooting your Pixel 2 will invariably trigger this error message on boot, for any user?
Are there other undesirable side effects to rooting your Pixel 2 at the moment?
Thanks
Hi all, I hope this isn't a thread that has already been posted... I found it interesting that there is no TWRP or any custom recovery for Pixel 7/7 Pro. I understand it's not needed to flash different rom's such as Paranoid Android or Spark OS but I figure it would be helpful no? My prior device was a iPhone 12, haven't run a rooted android since my Galaxy s4 way back in the day. Is this something somebody is actively pursuing or no as it's not needed? Curious on what the situation is with this, loving my p7 pro. Cheers!
TWRP has been nearly an entire Android version behind for awhile now so I haven't been able to use it on my last couple phones. I believe it is still being worked on but since it's been so far behind due to the changes to Android and it's migration to ramdisk installation it's mostly fallen out of use sadly. I do miss it sometimes as well.
jake.99x3 said:
I figure it would be helpful no?
Click to expand...
Click to collapse
No, its useless. Pixel devices have unlocked bootloaders and support fastboot, therefore recovery is not needed.
Well, a lot of old and new Samsung phones and tablets are running TWRP and root. Yes, with Android 13. Is it strictly because there is that A and B split thing going on ? Personally I have not written to my B partition in many months if ever.
Can there be a lesson learned from that ?
96carboard said:
No, its useless. Pixel devices have unlocked bootloaders and support fastboot, therefore recovery is not needed.
Click to expand...
Click to collapse
I don't know about that. It may not be needed but the advantages are profoundly easier than having to learn terminal commands
Also you can't do flashes and restores without a PC whereas when we had active working custom recovery it could be done anywhere at anytime.
JakeDHS07 said:
Also you can't do flashes and restores without a PC whereas when we had active working custom recovery it could be done anywhere at anytime.
Click to expand...
Click to collapse
Exactly! I used to do a complete backup, periodically. One day I screwed something up playing around at work, went to Recover and flashed my backup. Fixed it in a few minutes
Yeah it would be nice to have for sure
Same here, a nice custom recovery would be sweet. If I had any clue how to build one I would be all over it.
JakeDHS07 said:
Also you can't do flashes and restores without a PC whereas when we had active working custom recovery it could be done anywhere at anytime.
Click to expand...
Click to collapse
Is it even possible to do a nandroid backup anymore with the changes to Android filesystems and permissions? I mean you can't even flash a full firmware package in fastboot anymore, part of it has to be done from fastbootd.
old_fart said:
Well, a lot of old and new Samsung phones and tablets are running TWRP and root. Yes, with Android 13. Is it strictly because there is that A and B split thing going on ? Personally I have not written to my B partition in many months if ever.
Can there be a lesson learned from that ?
Click to expand...
Click to collapse
The A/B system is not for power users who manually flash things. It's so that updates for the 99% who use their phones normally can be done in the background. It also adds a failsafe in case one slot gets corrupted since it will automatically boot the other slot after so many failures. Previously such a failure would be an automatic brick.
Also, I think most of us power users are using the A/B system normally at this point too. You have to go out of your way to not flash an update to the other slot, all the defaults do.
HipKat said:
I don't know about that. It may not be needed but the advantages are profoundly easier than having to learn terminal commands
Click to expand...
Click to collapse
That's insane. And dangerous. When it messes up, good luck fixing it.
96carboard said:
That's insane. And dangerous. When it messes up, good luck fixing it.
Click to expand...
Click to collapse
Ummmm, what??
TWRP is a big miss for me. Nandroid Backups and phone based file explorer without having to boot to Android were just two of the numerous features I used regularly. To say it would be useless is ridiculous.
I for one would be very happy to have it make an appearance on the Pixel 7 Pro. I'm not holding my breath though, the Pixel 6 and 6 Pro still don't have it I believe.
I've used TWRP in the past. I've never understood the attraction.
Even with A/B a recovery is useful, but why would I want to play with volume buttons to express my wishes?
Just take a stock recovery, patch adbd to be rooted, patch the kernel to be permissive, done.
As Patrick Henry said, "Give me ADB or give me death!"
Renate said:
I've used TWRP in the past. I've never understood the attraction.
Even with A/B a recovery is useful, but why would I want to play with volume buttons to express my wishes?
Just take a stock recovery, patch adbd to be rooted, patch the kernel to be permissive, done.
As Patrick Henry said, "Give me ADB or give me death!"
Click to expand...
Click to collapse
You sure you've used it? TWRP is fully touch screen.
Beefheart said:
You sure you've used it? TWRP is fully touch screen.
Click to expand...
Click to collapse
You're right. I'm conflating stock recovery with TWRP.
I do remember big tiles and tapping on them.
Still, I prefer to keep my fingers on the (desktop) keyboard.
Renate said:
You're right. I'm conflating stock recovery with TWRP.
I do remember big tiles and tapping on them.
Still, I prefer to keep my fingers on the (desktop) keyboard.
Click to expand...
Click to collapse
I'm as much of a command line fan as the next nerd, but TWRP offers multiple features not available via ADB.
Renate said:
I've used TWRP in the past. I've never understood the attraction.
Even with A/B a recovery is useful, but why would I want to play with volume buttons to express my wishes?
Just take a stock recovery, patch adbd to be rooted, patch the kernel to be permissive, done.
As Patrick Henry said, "Give me ADB or give me death!"
Click to expand...
Click to collapse
Because when you don't have a computer to connect to do a restore, for example, it's imperative to have a Recovery that does backups so you can
HipKat said:
Because when you don't have a computer to connect to do a restore, for example, it's imperative to have a Recovery that does backups so you can
Click to expand...
Click to collapse
Ok. You're doing backups to a USB flash drive? Fair enough.
But, since this thread is questioning whether any custom recovery is in development wouldn't it be helpful if someone knocked off at least a custom recovery to the extent that I mentioned?
Renate said:
Ok. You're doing backups to a USB flash drive? Fair enough.
But, since this thread is questioning whether any custom recovery is in development wouldn't it be helpful if someone knocked off at least a custom recovery to the extent that I mentioned?
Click to expand...
Click to collapse
No, doing backups to internal storage, actually. How am I going to access a USB flash drive with a telephone if I’m sitting at a friend’s house and something gets corrupted, phone won’t boot, and I have to reboot to recovery where I can access an internal back up? Which cannot be done with stock recovery.