Rooting the LG G7 One Successfully/No Recovery Menu - Canadian - LG G7 One Questions & Answers

I've had some troubles trying to root my new phone, as above mentioned in the title. First off, when I try to boot into recovery mode via "adb reboot recovery" command, the phone restarts into a black screen with a dead android with a red triangle and 'no command' below. I haven't yet attempted to actually root my brand new phone yet because I wanted to backup my entire phone (stock ROM/Firmware, etc,.). I am afraid I will end up bricking it and have no ways to back it up. I had the same issue with my older LG G5 with the dead android. Why is there no recovery? And why have I been able to easily backup and root older phones from 2012 from LG but not my newer models?
It's really frustrating.
BTW, I posted this thread in the wrong area and I cannot find an option to delete it or move it to the Developers Section, my bad.

big bad brad 31 said:
I've had some troubles trying to root my new phone, as above mentioned in the title. First off, when I try to boot into recovery mode via "adb reboot recovery" command, the phone restarts into a black screen with a dead android with a red triangle and 'no command' below. I haven't yet attempted to actually root my brand new phone yet because I wanted to backup my entire phone (stock ROM/Firmware, etc,.). I am afraid I will end up bricking it and have no ways to back it up. I had the same issue with my older LG G5 with the dead android. Why is there no recovery? And why have I been able to easily backup and root older phones from 2012 from LG but not my newer models?
It's really frustrating.
BTW, I posted this thread in the wrong area and I cannot find an option to delete it or move it to the Developers Section, my bad.
Click to expand...
Click to collapse
The same thing happened to me. I was hoping to find a way to unlock the bootloader but unfortunately, I can't find any way at all. I was also trying to find a way to boot to recovery mode but the controls are not the same as the other Nexus, Pixel & Android One devices out there. When I press the power, it automatically restarts back to the full UI.

edwaine said:
The same thing happened to me. I was hoping to find a way to unlock the bootloader but unfortunately, I can't find any way at all. I was also trying to find a way to boot to recovery mode but the controls are not the same as the other Nexus, Pixel & Android One devices out there. When I press the power, it automatically restarts back to the full UI.
Click to expand...
Click to collapse
HI any recent discoveries???

helppppp
saad6 said:
HI any recent discoveries???
Click to expand...
Click to collapse
hello. can you backup g7 one phone system for me?my phone doesn't work. case I flash wrong firmware. so i need system backup to write in my phone. help me please .please save my phone s life.

edwaine said:
The same thing happened to me. I was hoping to find a way to unlock the bootloader but unfortunately, I can't find any way at all. I was also trying to find a way to boot to recovery mode but the controls are not the same as the other Nexus, Pixel & Android One devices out there. When I press the power, it automatically restarts back to the full UI.
Click to expand...
Click to collapse
Have you tried the simplest 'fastboot oem unlock' command (having checked the Allow OEM Unlock option in Developer's option; most Android One devices' bootloader can be unlocked this way)?
If it doesn't work, how about the below method, which I believe is the 'official' LG bootloader unlock:
https://www.getdroidtips.com/unlock-bootloader-lg-g7-thinq/
I don't own the LG G7 One, am hoping to, if the bootloader can be unlocked and Magisk be installed.
All the best

potatohead said:
Have you tried the simplest 'fastboot oem unlock' command (having checked the Allow OEM Unlock option in Developer's option; most Android One devices' bootloader can be unlocked this way)?
If it doesn't work, how about the below method, which I believe is the 'official' LG bootloader unlock:
https://www.getdroidtips.com/unlock-bootloader-lg-g7-thinq/
I don't own the LG G7 One, am hoping to, if the bootloader can be unlocked and Magisk be installed.
All the best
Click to expand...
Click to collapse
Done all of that. Unfortunately, the "adb reboot bootloader" command does not take it to the bootloader screen. It just simply restarted the device.

Related

Trying to root my g-slate

So I got bored with waiting around for someone else to do it, and decided to take a shot at rooting my G-Slate. I figure it's basically the same as the Xoom, so the same sort of process should work....
My initial game plan was this:
Get into Fastboot
Flash a recovery image
Boot the recovery image
Now "adb shell" is a root shell
Copy a "su" binary into /system/bin
Declare victory
That started out pretty well. Powering on and holding down volume-up gets into fastboot. The fastboot binary on my laptop sees the device. Typing "fastboot oem unlock" claims to work. Flashing the Xoom recovery image [1] claims to work.
But... I can't seem to boot to recovery. Running "adb reboot recovery" just reboots normally. Doing "fastboot boot recovery.img" freezes the device. Booting with down-volume gets me to some sort of LG updater state that might as well be freezing the device. Booting with both volume buttons down either 1.) doesn't boot or 2.) brings me to fastboot. That's all the button combinations.
So I guess my question is this: does anyone have any suggestions for how to proceed?
I really don't want to just blind-flash the Xoom boot.img from the unlock thread, because if that doesn't work my device is bricked until someone either makes a working kernel or somehow extracts the current one.
On the up side, my g-slate is *claiming* to have working fastboot that can flash images. It could be totally lying though.
[1] http://forum.xda-developers.com/showthread.php?t=1038870
Tried the same method. No dice. Right now there has been no luck on anyone's part that i know when it comes to rooting. Shoot we havent even been able to get one of the xda mods to create us our own forum for that matter...i had to go out and create my own. I have tried other methods that worked on my nexus one when none other would but alas still no luck.
I imagine since the g-slate is brand new that its not a question of if it can be rooted, but how and when. I'm going to try one more method i know of that worked on the lg optimus tonight. I'll post here if it works.
Soure code seems to be available too
It also appears the source code is available from LG here .lg.com/global/support/opensource/opensource-detail.jsp
I just did a search under mobile phones for the model number 909
Don't know if that will help anyone here.
I have been hunting all over for root access. fastboot says I unlocked the bootloader but nothing seems to want to take.
XDA Mods, please create a G-Slate Section
HA. member since 2006 and my first post just add a www in front of that link
When the fastboot says Ok it is not telling you that you have unlocked the device. It says ok no matter what you put in. Try unlock and it will say ok as well. If it unlocked the device then it would prompt you on your device with a popup that tells you that you are voiding your warranty and have you hit ok. The device is not unlockable using the 'fastboot oem unlock' command. I have rooted a lot of devices, but never have done anything on an LG device and it is awkward. Vol+ and power gets some form of fastboot. Vol- and power gets download mode, which I am used to from Samsung devices (if we can get an interface like Odin then this becomes a lifesaver and makes the device "virtually" unbrickable). I cannot find any form of recovery. 'Adb reboot recovery' just restarts the device. One interesting this is that pushing both Vol+ and Vol- and power puts the device into what would seem like a bricked device (just use reset button). This same button combination worked on some Samsung devices so something is happening there, but I have not tried enough combos yet to figure it out.
So far as root, well, I have tried z4 (works with nearly all Sammy devices and LG seems to be using a lot of Sammy ideas or at least it looks that way), but to no avail. Gingerbreak apk might work or even the Xoom Root, but the rootboot.img might be different and I have not opened any of that up yet. I did get SU loaded once and in the system, but I could not reproduce it.
I will be working on this some more this weekend (returning the device at some point as it reboots on its own about 5 times a day), and looking into the recovery issue. If anyone has any ideas then please post.
Also, it looks like LG hacked the crap out of the thing to get the SD card to mount and it is weird, so please be aware of that. The SD card mounts every time you plug the device in and there is no way to turn that off. The reason this is important is that some root methods require that the SD card not be mounted, so you will have to unmount the SD card via ADB and with the card being internal I am not too sure it is a good idea, but . . .
I will mark this thread as a favorite and update if I get any where. I know that Cyanogen and Kmobs got G-Slate's recently, so hopefully they can give us a little insight once the device gets to them. I have also contacted LG and @TheLGGirl and asked them to confirm that the bootloader is locked, but have not heard anything back.
Also, the the Acer HC tablet was rooted yesterday using the Gingerbreak root method, and so that is helpful, but it has an SD card (see above).
Sent from my LG-V909 using Tapatalk
I tried the Acer method (GingerBreak) and it does not work. Will look at the logcat in a bit.
Sent from my LG-V909 using Tapatalk
Thanks hourst
I am used to odin (also have a vibrant). Something like that would be a life saver.
Makes sense about the fastboot commands seeming to take.
I was also having reboot issues with mine. I had a handful of reboots each day (about 3 or 4) for the first two days but they have stopped completely now. I have had it for about a week now and have not noticed a reboot since day 2.
I will keep poking around to see if i can come up with anything as well.
Could this help?
Under the impression the G2x root method maybe helpful since they are both LG devices with somewhat similar hardware.
Does anyone know or tried this http://forum.xda-developers.com/showthread.php?t=1056847 to see if it works?
Not sure if I am brave enough yet. But it could be possible the vol up+vol down+power button combo that seems to lock the device is putting it into the mode needed to run the nvflash application.
This really is mostly speculation but could be something to try.
Success
So i got brave.
vol up+vol down+power Device seems to freeze. Plugged in the usb and got a new hardware pop in windows. Listed it as APX device using the drivers in the file listed in my previous link installed successful and the device was found.
That is a far as I went.
im doing the NVFLASH right now... wish me luck and see how far I can go
Any Luck?
Suzannemscott
How did it go? any results or do you have a large brick?
ok i tried. and no luck , i did manage to brick it tho, but i was able to unbrick it phew, back to square one
Did it seem like anything happened? Also what did you do to unbrick it?
To unbrick it i just press the reset button, in the back, quickly hold down Vol+ and Vol- then it goes to a the Gslate screen with the square and then i hold down the reset again and it reboots, maybe i am doin to much but hey it get my Tab back it works!
Gah! Why does it claim to have fastboot when *any* fastboot command except "fastboot devices" just makes it freeze?
I went ahead and built the kernel that LG released and packed it into the clockwork recovery image for the Xoom. Fastboot boot... freeze.
Computer always says this, but I think it's just making fun of me:
downloading 'boot.img'... OKAY
booting... OKAY
I also tried to build and boot a custom kernel with a fb console enabled just to get some feedback, but all it wants to do in response to "fastboot boot" is freeze.
I'm starting to get discouraged here. My 14 day return period ends on Tuesday and I don't really want to get stuck with an unrootable device.
Chandon, would you be able to send me the kernel you built?
I'm sure someone with more expertise and knowledge will be able to root this thing eventually...but right now it seems to be a lot trickier to root than I initially thought. It's not unrootable...just complicated. Over my head by a lot. I don't think I'm going to return it...but I've now resigned to the fact that I may not ever be able to find a working method to root the damn thing myself.
SmellyTunic -
I've uploaded the two kernels I built [1].
They're both built from the v909 kernel source posted by LG[2], following the instructions posted by adrynalyne[3] for building custom android kernels, but I don't have any way to test them aside from the fact that "fastboot boot" doesn't work either straight, with a ramdisk, or with a rebuilt recovery image using the tools in [4].
[1] http://pandion.ferrus.net/gslate/kernels
[2] http://opensource.lge.com
[3] http://forum.xda-developers.com/showthread.php?t=1039854
[4] http://forum.xda-developers.com/showthread.php?t=915808
hourst2 said:
When the fastboot says Ok it is not telling you that you have unlocked the device. It says ok no matter what you put in. Try unlock and it will say ok as well. If it unlocked the device then it would prompt you on your device with a popup that tells you that you are voiding your warranty and have you hit ok. The device is not unlockable using the 'fastboot oem unlock' command.
Click to expand...
Click to collapse
Not entirely true. You said that if you try simply typing in "fastboot unlock", it tells you "OK" as well, right?
Not for me. That only ended up displaying the whole list of fastboot commands.
I agree with you that "fastboot oem unlock" is not unlocking the device though. But what are the alternatives? Everything I've ever rooted has used "oem unlock". I've never even heard of a different command that can be used to unlock a bootloader. I tried a google search and came up with nada.
Hmm...
wich you the best make happen

Fastboot, Recovery question..

So, Ive tried to boot into fastboot and recovery on my xperia z3 and I get nothing but a black screen. Is this normal? Ive tried the adb commands to reboot into fastboot and recovery and still nothing but a black screen. Ive tried volume up and plugging in the USB cable and get the blue LED and a black screen. Ive tried the powering on and pressing volume up and down repeatedly and still nothing.
I have the T Mobile International supposedly Factory Unlocked version 6603.
Also, whats the point in having a SD card to expand memory if you cant install any apps to it? I understand that you can put music and such on there but if you start installing any large games the 16GB internal is gone quick and you cant put any apps on the SD Card.
This phone is great but cant install to the SD, cant change the install location as its not supported in Kit Kat. Sony's ROM doesn't allow move to SD anymore, cant boot to fastboot to flash can view recovery..perhaps there is something I have not read about this phone yet in the forums.
Anybody have any sugestions?
J
There is no stock recovery on xperia devices, you need to install one yourself. Also, there is no UI on the phone when in fastboot. You can just send fastboot commands from a terminal on your PC
Currently the only was to do that is to unlock the bootloader (Just google "Sony unlock bootloader" to find out how to do that) then flash a custom kernel from the development sections to get recovery and root
Terminal doesn't show any devices connected. Can't start a shell nothing in fastboot. I have not tried to use the command to flash the kernal I guess that works?
There is really no fastboot menu just a black screen huh? Strange
Jason0071 said:
Terminal doesn't show any devices connected. Can't start a shell nothing in fastboot. I have not tried to use the command to flash the kernal I guess that works?
There is really no fastboot menu just a black screen huh? Strange
Click to expand...
Click to collapse
Yes just a black screen.
Have you unlocked the bootloader? Have you installed ADB and fastboot drivers?
No I've not done these things yet. I was thinking there was something wrong with my device. It seems it's functioning correctly. I'll proceed with unlocking the boot loader and see how it goes
Jason0071 said:
No I've not done these things yet. I was thinking there was something wrong with my device. It seems it's functioning correctly. I'll proceed with unlocking the boot loader and see how it goes
Click to expand...
Click to collapse
Make sure you read the warning first
What's the worst besides bricking the phone?
Jason0071 said:
What's the worst besides bricking the phone?
Click to expand...
Click to collapse
You will loose some of what makes Sony camera so good on this phone + some audio / video post processing.
Myself, I have rooted immediately after getting this phone since coming from HTC phones I did not expect any noteworthy disadvantages only to learn later that I have reduced the phone's functionality forever.
I still like a phone a lot; but it bothers me that a lot of functionality in this phone is based on software wizardry rather than hardware quality.
Being so used to flash custom ROMs often I am beginning to realize that Sony might not be such a great choice, although, once again Z3 (dual) I own has a lot going for it compared to current HTC phones.
Agreed opted not to root

Need help rooting a RCA Voyager Pro RCT6773W42B tablet

Is there an easy way to root this tablet?
The tablet is a RCA Voyager Pro. Model number is RCT6773W42B. It's running Android 5.0.1 Lollipop. Build number is RCT6773W42B-ANDROID5.0-V 19-V1.12.50-KC-B.
I want to root it so I can use the WWE App (No luck with Google Play or 1Mobile or Aptoide). I would so like to use some videogame roms also if possible. That's what I mostly would like to do. Nothing much else. I am not too computer savvy but I do know the basics. So anything that would be pretty easy/simple would be awesome.
Looking for root also. Tried everything to no avail. Hopefully something comes out soon.
+1
MobileGo
brokenjimmy said:
Is there an easy way to root this tablet?
The tablet is a RCA Voyager Pro. Model number is RCT6773W42B. It's running Android 5.0.1 Lollipop. Build number is RCT6773W42B-ANDROID5.0-V 19-V1.12.50-KC-B.
I want to root it so I can use the WWE App (No luck with Google Play or 1Mobile or Aptoide). I would so like to use some videogame roms also if possible. That's what I mostly would like to do. Nothing much else. I am not too computer savvy but I do know the basics. So anything that would be pretty easy/simple would be awesome.
Click to expand...
Click to collapse
Wondershare MobileGo. Free trial, but it works. Download it to pc and connect tab. It will install a "connector" app on the tab, then hit the "one click root" button and let it reboot the tab 3 or 4 times. It may stick on the dog splash screen for a while but don't panic. I did at first, but when it came back up it had root.
Don't use wonder share!!!
This tablet is not root capable out of the box, the reason for this is that the boot loader is locked which prevents any kind of modification of firmware as well as root. Now, I have not unlocked my boot loader yet on mine so I can't tell you if unlocking will allow installation of root but to unlock the boot loader first, read all instructions before attempting and I'm not responsible if your device bricks!
1. Turn device off
2. Hold volume up key then hold power key
3. Let go of power key once it starts booting but continue holding power up key until you in the recovery menu
4. You will see option to reboot to boot loader, navigate to it using volume key then select it using power key
5. You should see fastboot in the corner, now you need android SDK tools and adb ect. Which if you don't have you can google it.
6. Open command prompt from the sdk/adb folder by holding shift, right click, open command prompt.
7. Type adb devices to make sure your device is connected. If not make sure you install correct drivers for this tablet.
8. If everything is good continue by typing "fastboot oem unlock" without quotes it should pop up a screen on the device asking to unlock boot loader or it will automatically unlock it. Now you can try different programs like kingroot or manually install root with command prompt.
I can not confirm this will work as I have not had time to unlock mine yet. And again I'm not responsible for anything that may happen to your device bricked ect
icy201 said:
Don't use wonder share!!!
This tablet is not root capable out of the box, the reason for this is that the boot loader is locked which prevents any kind of modification of firmware as well as root. Now, I have not unlocked my boot loader yet on mine so I can't tell you if unlocking will allow installation of root but to unlock the boot loader first, read all instructions before attempting and I'm not responsible if your device bricks!
1. Turn device off
2. Hold volume up key then hold power key
3. Let go of power key once it starts booting but continue holding power up key until you in the recovery menu
4. You will see option to reboot to boot loader, navigate to it using volume key then select it using power key
5. You should see fastboot in the corner, now you need android SDK tools and adb ect. Which if you don't have you can google it.
6. Open command prompt from the sdk/adb folder by holding shift, right click, open command prompt.
7. Type adb devices to make sure your device is connected. If not make sure you install correct drivers for this tablet.
8. If everything is good continue by typing "fastboot oem unlock" without quotes it should pop up a screen on the device asking to unlock boot loader or it will automatically unlock it. Now you can try different programs like kingroot or manually install root with command prompt.
I can not confirm this will work as I have not had time to unlock mine yet. And again I'm not responsible for anything that may happen to your device bricked ect
Click to expand...
Click to collapse
You're not going to be able to unlock it.. there's another thread on this and it's got nothing to do with any human.
Bootloader is locked. Gotta try other stuff. I've had this for months and it's a piece of junk.. frankly, to me, anyway.. it's worthless without root privileges.
---------- Post added at 03:01 PM ---------- Previous post was at 02:08 PM ----------
dogboy322 said:
Wondershare MobileGo. Free trial, but it works. Download it to pc and connect tab. It will install a "connector" app on the tab, then hit the "one click root" button and let it reboot the tab 3 or 4 times. It may stick on the dog splash screen for a while but don't panic. I did at first, but when it came back up it had root.
Click to expand...
Click to collapse
... nope. Still no root. Even said "root failed" .. I'm just gonna see if anything else is updated. I've had this tablet for a couple of months thinking there'd at least be a few exploits to use but there's almost zip that I've been able to see. and I'm not the only one that can't unlock the bootloader with fastboot. Not sure what else to think at this point.. but this was a waste of time.
So why is the boot loader non-unlockable?
Re: Wondershare
icy201 said:
Don't use wonder share!!!
This tablet is not root capable out of the box, the reason for this is that the boot loader is locked which prevents any kind of modification of firmware as well as root. Now, I have not unlocked my boot loader yet on mine so I can't tell you if unlocking will allow installation of root but to unlock the boot loader first, read all instructions before attempting and I'm not responsible if your device bricks!
1. Turn device off
2. Hold volume up key then hold power key
3. Let go of power key once it starts booting but continue holding power up key until you in the recovery menu
4. You will see option to reboot to boot loader, navigate to it using volume key then select it using power key
5. You should see fastboot in the corner, now you need android SDK tools and adb ect. Which if you don't have you can google it.
6. Open command prompt from the sdk/adb folder by holding shift, right click, open command prompt.
7. Type adb devices to make sure your device is connected. If not make sure you install correct drivers for this tablet.
8. If everything is good continue by typing "fastboot oem unlock" without quotes it should pop up a screen on the device asking to unlock boot loader or it will automatically unlock it. Now you can try different programs like kingroot or manually install root with command prompt.
I can not confirm this will work as I have not had time to unlock mine yet. And again I'm not responsible for anything that may happen to your device bricked ect
Click to expand...
Click to collapse
I wouldn't make up a story if it had not rooted. Yes it said "root failed" the first few cycles of rebooting, but after several cycles it rooted. Now... if Wondershare is malware, this may be related... a week or so later the touch screen developed two rectangular "dead" spots that no amount of factory resetting could fix. I could not even type wifi password without rotating it in circles to avoid the dead spots. If you want a decent tablet for under 100, spend 30 more and get the Nextbook Ares 8. Very hard to root as well, but TWRP did the trick.
Wish i could root mine. RCA voyager pro 16gb. Is this bootloader just so hard to crack its not worth it? Or is the device really that crappy that no one wants to bother? I've tried unlocking it manually with adb and i cant select the yes option. Why the hell not? The no option works just great, clicking yes does not a thing. Hitting power after or not. No option for bootloader unlock in the settings. Yes i don't know where to even start when trying to figure it out myself. Justdont think the thing is so worthless it cant be done. I haven't had any issues with it at all, other than not being able to unlock it.
SkyLo420 said:
Wish i could root mine. RCA voyager pro 16gb. Is this bootloader just so hard to crack its not worth it? Or is the device really that crappy that no one wants to bother? I've tried unlocking it manually with adb and i cant select the yes option. Why the hell not? The no option works just great, clicking yes does not a thing. Hitting power after or not. No option for bootloader unlock in the settings. Yes i don't know where to even start when trying to figure it out myself. Justdont think the thing is so worthless it cant be done. I haven't had any issues with it at all, other than not being able to unlock it.
Click to expand...
Click to collapse
That's exactly why I said you cannot unlock the boot loader.. that's the only way to do it unless you use some dev's app around here that types the same command and tries no matter what.
Regarding it being rooted.. I've been trying for months now.. I'm actually trying again after giving up for a lil' bit.. SRSRoot said they picked it up but that just says it roots and then reboots.. and I see no sign of superuser/supersu or any sort of system apk to manage it, even if the damn app says "unmounting /system" and "remounting /system, rebooting.. Root success!" ... yeah even after that, I saw nothing when it booted back up. Tried Kingo only God knows how many times.. even tried other little exploits, tried to manually root it but unless you have r/w access to /system, which a custom recovery can give.. it won't happen unless someone literally takes what's on the RCA and they more or less just have a pre-rooted stock rom to start.. 5.0.1, whichever.. I haven't done any updates and I'm not gonna try. I'm gonna going to try and cycle through six-seven more times before I just eventually give up. I'm sure something will come along eventually, but right now I'm not getting ****, and not being able to unlock the boot loader isn't much of a help. I can't even load MTK Droid Tools with this, yet, it's got the same 8127 chipset as a rooted Lenovo that I have (running KitKat 4.4.2) .. i was able to install PhilZ with that.. but the boot loader is still locked.. I didn't even try to unlock it.. it's just like how FlashFire operates.. stay in Android but mount only what needs to be mounted.
If anyone see's something that really does root this thing or has a damn /system partition that they can friggin' send to someone (I'd be happy to at least try) to wipe everything and install a custom rom.. I don't know. I'd rather just manually root and then have this as a backup. This is what makes me regret grabbing some RCA even if it was 40 bucks with a keyboard. Useless without superuser permissions.
---------- Post added at 10:38 AM ---------- Previous post was at 10:33 AM ----------
dogboy322 said:
I wouldn't make up a story if it had not rooted. Yes it said "root failed" the first few cycles of rebooting, but after several cycles it rooted. Now... if Wondershare is malware, this may be related... a week or so later the touch screen developed two rectangular "dead" spots that no amount of factory resetting could fix. I could not even type wifi password without rotating it in circles to avoid the dead spots. If you want a decent tablet for under 100, spend 30 more and get the Nextbook Ares 8. Very hard to root as well, but TWRP did the trick.
Click to expand...
Click to collapse
Oh, and um.. Wondershare just adds a service.. at least under Windows 7 x64.. it's easy to remove so I'm not really worried and.. honestly.. I don't see a correlation between dead pixels and software unless it's immediate impact.
dogboy322 said:
I wouldn't make up a story if it had not rooted. Yes it said "root failed" the first few cycles of rebooting, but after several cycles it rooted. Now... if Wondershare is malware, this may be related... a week or so later the touch screen developed two rectangular "dead" spots that no amount of factory resetting could fix. I could not even type wifi password without rotating it in circles to avoid the dead spots. If you want a decent tablet for under 100, spend 30 more and get the Nextbook Ares 8. Very hard to root as well, but TWRP did the trick.
Click to expand...
Click to collapse
Still no dice with Wondershare, but it does do exactly as you said.. I'm wondering if you were thinking of the correct model and OS. This specific model never had KitKat (4.4.x) for it.. it's 5.0.1 only. Some people mistake this model for the other one with the same NAME but one different thing.. at the end of the model number, the ones that have actually a possibility of being rooted... they have a 22 at the end.
this is a 42. 42B. Now if he has that, then me trying this for the 12th time might have a shot at working. I might just do a factory reset.. like... as it was out of box.. aside from enabling USB debugging mode. I might try a few different drivers as well. It just fails and fails and fails and you know what it suggests to "manually" root? It recommends SuperOneClick which is no longer even used unless you have a really old device..
lol. I'll update you guys if I somehow find something. I'll try all the one-click tools a try but SuperOneClick? I actually have that in my archive but.. I don't really think it's necessary nowadays. If only I could get this damn boot loader unlocked.. I mean there's no way that they'll send anything anyway.. I'll try using MTK Droid Tools due to it having an MT8127 chipset.. every time it just says it can't load adb.. makes no sense to me. I have it installed system-wide with Environment Variables..
I know this thing can be rooted.. it's just gonna take longer, probably a year or more.. mostly because no one even gives a ****. I think it's pretty good if I just had the su binary in /system actually there, even temporarily.. I could easily make it permanent if we have even a glimmer of it for just a few minutes.. that's all I'd need. I'm not a dev but I know my way if I'm given at least SOME time.. Just run an sudaemon and what happens is you can actually remove what's considered "root" regarding the app.. this is actually well-instructed in a post that has to do with removing KingRoot and putting SuperSU on it to replace it. .. and I'm not talking about SuperSUme.. I mean it takes a little bit of knowledge... but not that much.
SkyLo420 said:
Wish i could root mine. RCA voyager pro 16gb. Is this bootloader just so hard to crack its not worth it? Or is the device really that crappy that no one wants to bother? I've tried unlocking it manually with adb and i cant select the yes option. Why the hell not? The no option works just great, clicking yes does not a thing. Hitting power after or not. No option for bootloader unlock in the settings. Yes i don't know where to even start when trying to figure it out myself. Justdont think the thing is so worthless it cant be done. I haven't had any issues with it at all, other than not being able to unlock it.
Click to expand...
Click to collapse
For the record.. Most don't care about a 30 dollar device with a damn keyboard unless they're literally sitting at a Command Line or using ADB for transfers etc instead of copy/paste. The reason that KitKat/4.4 works here is simple.. It doesn't have any way to patch PIE unless you're rooted already or if you've somehow got your tablet looked at as another device for unlocking the boot loader.. and I do remember, one time, I saw this first install the driver for an HTC One..
it's just an idea.. I'm not responsible if you **** anything up for your tablet. If you don't need root, then just don't worry about it or keep using stuff. PIE just stands for Position Integrated Executable.. and the error it gives every single 5.0+ tablet that has barely anybody looking at it.. well, that's why they're not working.. it literally gives the message when you attempt to root it manually.. "error: only position independent executables (PIE) are supported." ... now there are plenty of threads on here with this and ways to "bypass" it.. hell they even have something called "patch-pie" to flash in a custom recovery.. not the manufacturer. So if you somehow unlock the boot loader and you know what to put on it.. Then you're in. That's usually what happens here.. the methods are fine, they all work, it's just some firmware isn't ever really looked at with brands that have barely any purpose. Most of these types of tablets run 4.4.x on there and that gives them no errors... so it's really easy to root it if you get past it. I've seen it in SRS root right before my eyes and even doing so when trying other things not root-related in adb. Fix that and you'll be able to do it.
Disclaimer: If anything happens to any of your devices as a result of anything in this entire thread, post, or even the links from this entire thread and entire post.. doesn't fall on me, not my fault. If your wife or side girlfriend decides unlocking the boot loader with a hammer, I'm very sorry, but it is not of my doing. This is all for testing purposes. That being said.. I don't see how you screw this up. Don't try to unlock the bootloader, by the way. It's not happening.
The latest KingRoot works. I did a Factory reset prior, I had no clue it'd actually work. just.. clear cache and dalvik basically, install this:
http://forum.xda-developers.com/devdb/project/dl/?id=18893
xda approved obviously... after that, either use Super-SUME or the following guide to remove and replace KingRoot. It's originally made for some Amazon Fire phone but the whole thing is perfect to replace KingRoot and furthermore the correct binaries; At times it'll say it's an incorrect command or that something does not exist.. don't worry about it. It's Ancient but works just fine.. I did this just two days ago. Copy/Paste it line by line, not all at once... or make a script. up to you:
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546
Need Custom Rom for custom rom rct6773w42b
Please where can I found a Custom Rom for RCA tablet 16 GB rct6773w42b, is bricked software for repair this.
Thank in Advance.
Bekel
Anyone have the original rom file? I did a factory reset in recovery and it keeps boot looping back to recovery. Would like to update via sd card option or adb. Please Help!!! I couldn't find anything online, it is the RCT6773W42B.
hey guys my bf found a way to unloclk the bootloader...once in recovery screen...when prompted ...go to bootloader but use the physical keys up/down and press enter to get it to work. volume keys dont work and it works . mines unlocked...just trying to find root solution now,. help??
Bootloader unlocked, full systemless root attained by using Kingoroot PC Version, SuperSU Me Pro to replace the Chinese binaries with proper SuperSU binaries. SuperSU 2.79-R3 installed on Android 6.0.1 Stock ROM. Bootloader is not encrypted. Only requires OEM Unlocking enabled in Developer options, connected to PC with micro USB syncing cable, rebooted into AP Fastboot Mode. Minimal ADB & Fastboot needs to be installed on PC (or the full Android SDK). Open a command prompt in the adb/Fastboot directory if using minimal adb & fastboot and simply type fastboot oem unlock and watch tablet screen for a prompt using the Volume buttons. Contrary to earlier statements this tablet is fully root ready out of the box, and bootloader is definitely not encrypted. Currently working on a TWRP port for this device as well as a deodexed and debloated stock ROM preinjected with root binaries, and optional insecure boot.img with init'd support running stock.
What wonderful work! And many thanks for your efforts. Do you think that your instructions and future ROMs would work with the RCT6873W42KC?
For more reference: https://www.amazon.com/gp/product/B01M7TSY16/ref=od_aui_detailpages00?ie=UTF8&psc=1
Well, well done,
Jake
jakfish said:
What wonderful work! And many thanks for your efforts. Do you think that your instructions and future ROMs would work with the RCT6873W42KC?
For more reference: https://www.amazon.com/gp/product/B01M7TSY16/ref=od_aui_detailpages00?ie=UTF8&psc=1
Well, well done,
Jake
Click to expand...
Click to collapse
Well, my objective is to modify a stock ROM that can be flashed on any RCA Voyager 7" variant running either Lollipop or Marshmallow. This includes the Voyager, Voyager II and the Voyager Pro. I would like to be able to offer both 5.1 and 6.0.1 ROMs. As long as the filesystem does not in anyway forbid a downgrade in firmware or OS, users running Marshmallow Builds would be able -- with an unlocked bootloader of course -- to flash either a Lollipop or Marshmallow Deodexed, Rooted, & Debloated Stock ROM. A Lollipop OS would offer the advantage of a System-Based Root versus the Systemless method required on the 6.x.x Builds.
Use KingRoot Worked for mine. Looking for custom ROMs

Question Device corrupted

Hi all.
I read that my oneplus 9 was able to test the beta of android 12 and found that I could do so in developer options and choose the dsu loader. Did that and now my device won't work at all. I can't get into recovery and factory reset it or anything it just restarts itself and i get an error message saying the device is corrupted and won't boot. Is it any way to fix this or have my own foolishness killed this phone? Please help
Illusions_887 said:
Hi all.
I read that my oneplus 9 was able to test the beta of android 12 and found that I could do so in developer options and choose the dsu loader. Did that and now my device won't work at all. I can't get into recovery and factory reset it or anything it just restarts itself and i get an error message saying the device is corrupted and won't boot. Is it any way to fix this or have my own foolishness killed this phone? Please help
Click to expand...
Click to collapse
Not all hope is gone. If there is an msm tool for your variant your in luck. I have the global unlocked op9 and there isn't one yet. Although you can use a fastboot rom from xda. And there is always last resort of calling OnePlus customer service and getting a remote session . Explain to them you tried the beta release and now phone is unuseable . Hope you get it fixed as I bricked my op8 a month or so ago and it's a bad feeling. I also read the developer previews were not for north American devices. Maybe you saw that as well.
Illusions_887 said:
Hi all.
I read that my oneplus 9 was able to test the beta of android 12 and found that I could do so in developer options and choose the dsu loader. Did that and now my device won't work at all. I can't get into recovery and factory reset it or anything it just restarts itself and i get an error message saying the device is corrupted and won't boot. Is it any way to fix this or have my own foolishness killed this phone? Please help
Click to expand...
Click to collapse
If you can boot to fastboot mode. Then fastboot format userdata I think
Didn't work. Think my bootloader is locked as well since I haven't unlocked it at all. Just read online that you could test the android beta by using that dsu thing and now my phone is gone. It was completely stock hadn't touched a thing except that I got into developer options. I didn't think i could brick a phone without mixing with ROMs and stuff.
Can you get it to bootloader?
Power off completely, then 3-button hold (vol up + vol down + power) till bootloader screen.
If you can, and you can get fastboot to recognize the device, you might have a shot at fastboot oem unlock, and then possibly a fastboot rom.
If not, then you might ask Oneplus support for an MSM tool
reaper000 said:
Can you get it to bootloader?
Power off completely, then 3-button hold (vol up + vol down + power) till bootloader screen.
If you can, and you can get fastboot to recognize the device, you might have a shot at fastboot oem unlock, and then possibly a fastboot rom.
If not, then you might ask Oneplus support for an MSM tool
Click to expand...
Click to collapse
No luck with OEM unlock. Contacted oneplus here in sweden and will send the phone to them on Monday hoping they can fix it. Never thought i could mess upp a phone so much by just tinkering with settings within the phone but you live and learn all the time i guess. Bit sad since I got the phone two days ago

Question I can't access the download mode

So here is the deal.
This device (Galaxy A32 5G - SM A326B - Android 12) does not let me boot into the download mode in order to unlock bootloader and for eventually rooting it.
OEM unlock has been selected in the dev options.
No button pressing configuration is working.
Trying to access the fastboot mode in the recovery mode only shows a black screen with a red writing on top that fastboot mode is being loaded, but nothing is happening and Odin doesn't recognize the device.
I just want that turquoise, blueish download mode screen, but for the love of it, it just doesn't work getting there.
This is my backup device and I just want to root it. Coming from OnePlus I am spoiled but the fact that I can't access this mode with all kinds of button tryouts is just nagging on me.
Anyone experienced something similar?
Some help would be greatly appreciated.
Cheers
mrjuniork said:
OEM unlock has been selected in the dev options.
Click to expand...
Click to collapse
I have the SM A326U but unfortunately I tried to see if I had the OEM Unlock options in the Developer Options Activity, and it's not there.
Do you know what the hidden activity might be when you click on the OEM Unlock? Maybe we can bring it up with an Activity Launcher?
mrjuniork said:
So here is the deal.
This device (Galaxy A32 5G - SM A326B - Android 12) does not let me boot into the download mode in order to unlock bootloader and for eventually rooting it.
OEM unlock has been selected in the dev options.
No button pressing configuration is working.
Trying to access the fastboot mode in the recovery mode only shows a black screen with a red writing on top that fastboot mode is being loaded, but nothing is happening and Odin doesn't recognize the device.
I just want that turquoise, blueish download mode screen, but for the love of it, it just doesn't work getting there.
This is my backup device and I just want to root it. Coming from OnePlus I am spoiled but the fact that I can't access this mode with all kinds of button tryouts is just nagging on me.
Anyone experienced something similar?
Some help would be greatly appreciated.
Cheers
Click to expand...
Click to collapse
Did you try plugging into usb while holding down the buttons?
TimmyP said:
Did you try plugging into usb while holding down the buttons?
Click to expand...
Click to collapse
Yes, among other things. It just never enters that mode. It either restarts, goes into charging mode or reboots to recovery.
It's weird
maybe try "Samsung 300k Tool?" It looks like its designed specifically to reboot Samsungs into Download mode
TimmyP said:
maybe try "Samsung 300k Tool?" It looks like its designed specifically to reboot Samsungs into Download mode
Click to expand...
Click to collapse
Thx for this useful information. I could enter the download mode with this program but interestingly there is no way to use volume up button for proceeding to unlock the bootloader. Odin recognized the device properly but no way to unlock the bootloader. Isn't that strange? Also I did not see the warning screen, it went straight to the download mode screen.
I did not expect this to be such a pain...
Glad it worked! Samsungs always seem to have some sort of strange issue. I was recently stuck in a bootloop for a half hour until I finally got the key combo for recovery to work. Since it never turns off it becomes a pain!
TimmyP said:
Glad it worked! Samsungs always seem to have some sort of strange issue. I was recently stuck in a bootloop for a half hour until I finally got the key combo for recovery to work. Since it never turns off it becomes a pain!
Click to expand...
Click to collapse
I actually figured it out without the need of any 3rd part software.
There was obviously one option that I haven't tried yet. Pressing both volume buttons and then plugging in the USB cable till the warning screen shows up. That's it
Anyway, thx for taking your time to reply.
Cheers
mrjuniork said:
I actually figured it out without the need of any 3rd part software.
There was obviously one option that I haven't tried yet. Pressing both volume buttons and then plugging in the USB cable till the warning screen shows up. That's it
Anyway, thx for taking your time to reply.
Cheers
Click to expand...
Click to collapse
Hello Pal, were you able to root the device? I have bought an A33 5G, not sure if I will be able to root it. Extracting the boot.img file from original rom, patching it with Magisk and flashing back to the phone works? Can you use fastboot for it or do you need ODIN?
GauchoTche said:
Hello Pal, were you able to root the device? I have bought an A33 5G, not sure if I will be able to root it. Extracting the boot.img file from original rom, patching it with Magisk and flashing back to the phone works? Can you use fastboot for it or do you need ODIN?
Click to expand...
Click to collapse
Hello again.
Yes, I managed to root the device.
I used Odin for flashing the patched boot image. AFAIK, using fastboot isn't possible, hence Odin.
But make sure you have a backup in place, coz in my case, initially applying a patched image, led to another factory reset (the second one after unlocking the bootloader).
mrjuniork said:
Hello again.
Yes, I managed to root the device.
I used Odin for flashing the patched boot image. AFAIK, using fastboot isn't possible, hence Odin.
But make sure you have a backup in place, coz in my case, initially applying a patched image, led to another factory reset (the second one after unlocking the bootloader).
Click to expand...
Click to collapse
Hello, I need help with unlocking the bootloader as well. I can't find the Oem option and there is no unlock the bootloader option in download mode.

Categories

Resources