[Solved] No access to fastboot or bootloader, enters OS just fine.

[Solved] No access to fastboot or bootloader, enters OS just fine. - Fairphone 2

So earlier this year a friend of mine asked me to install lineageOS on his fairphone, do I did. It worked just fine back then, but now he has come to me with it, complaining that he can't update it. Tried to access fastboot and bootloader through physical buttons and through advanced restart, but it just reboots back into the OS. He doesn't get any OEM unlock warning when he reboots, so I thought that he might have locked it somehow. Saw in a reddit thread that you could re-unlock it though
Code:
adb root
adb shell setprop ro.oem_unlock_supported 1
and tick an option in the developer options menu, but nothing shows up when I type that. Is this classified as a hardbrick? Saw that you had a possible fix for that here, but I'm really out of my water here and want to know that this is what I'm supposed to do before I go forward.
Thank you for every little help you can give me.

I just saw that the guide I linked was for fairphone 1. Does anyone know of a flashtool that works with the 2nd phone?

Ok, so the problem is most likely due to a lineageOS bug with Fairphone 2's "new" camera module. Thread can be found over at fairphones forum. I cannot post a direct link but /t/los-15-1-reboot-to-recovery-unstable/42345 should be fine. One step closer to a solution, but not yet there.
Edit: A possible fix for this is to enable the flashlight before restarting. Will try it next time I have access to the phone.
Edit2: The flashlight reboot worked perfectly. Problem solved.

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

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.

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

Galaxy amp 2 rootable?

Have done a little research trying to find any thing about an easy rooting for this device but no hits. I do know of some apps that can give root access haven't tried them but don't exactly trust them to much as have had them soft brick a few devices.
But any way here is device specs.
Carrier: cricket wireless
Phone name: Samsung Galaxy amp 2
Model number: Samsung-sm-j120az
Android version: 6.0.1
Baseband: J120AZTUU1APC4
if need any other info on it can supply it

I'm looking for the same thing. No roms no nothing.

@jasperjax Don't worry about it, there's not such thing as a flawless security system.
Universal rooting methods:
Warnings:
You are modifying your own phone on your own risk.
There is a slight chance that your phone may brick,
and if it does I will not be held responsible for whatever you do to your phone.
If you have a warranty, after rooting it will no longer be valid.
If your phone has a flash counter, some methods may trip it
resulting in a void warranty or a bricked phone (or both).
If your phone has KNOX, it may be tripped by some methods,
resulting in, once again, a void warranty.
If your phone is encrypted, the data partition
may be wiped for some methods.
There are more warnings specific to certain devices. Do your own research on your particular device model.
Click to expand...
Click to collapse
Computerless methods:
1. Framaroot
2. Towelroot
3. Kingroot for Android
4. Kingoroot for Android (Not recommended, but often works)
5. iRoot for Android
6. z4root
Methods requiring a computer:
1. iRoot
2. Root Master
3. Kingroot
3. Kingoroot (Not recommended)
4. CF-Auto-Root
Root Checker - Check if your device is correctly rooted
SuperSU - the recommended superuser application
ADB and fastboot drivers:
ADB and fastboot are (extremely simplified) a way for your computer to talk to your phone. And installing them may be a bit of a problem for some users.
To install it on windows there is a handy tool called the 15 Second ADB installer which will install pretty much everything you need.
On Ubuntu install with:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
On Fedora:
Code:
sudo dnf install android-tools
On OS X using Homebrew:
Code:
brew install android-platform-tools
Recovery:
A custom recovery is an important part of device unlocking. It's the best and the most convenient way to fix your device if something goes wrong.
Root is required (in most cases) for installing the recovery.
The two most popular recoveries are:
1. Clockworkmod recovery (CWM) - CWM is a very stable recovery with many useful features. You can use the link here to download and install the official version via the ROM Manager app.
2. Team Win Recovery Project (TWRP) - TWRP is a stable recovery with a very nice UI and many features such as the terminal, partition management, file browser and so on. I personally use TWRP because of it's functionality, but if you're starting out CWM would be a better choice because of it's stability and compatibility. Also TWRP is a tiny bit more difficult to install as there is no one click installer.
If your device is not officially supported you can get an unofficial version, however there is no grantee the unofficial version will work, it might even forever break your device. In most cases it does work, just look at what other people who tested it say.
To find unofficial recoveries Google:
[your phone model] cwm recovery
or
[your phone model] twrp recovery
After installing the recovery the first thing you should do it do a nandroid backup.
If you have any questions first try to Google the answer, but if you can't find it feel free to ask me here with a post (not a PM).
Also remember to quote me or tag me with @janekmuric if you want me to respond.

most of those do not work for 6.0 correct? Amp2 comes with 6.0 stock

Has anyone heard anything more about rooting the Cricket Galaxy amp 2?
Just bought it yesterday for a friend and would love to root and possibly unlock it?

i have tried all the computer less ways of trying for root. none have worked. haven't done much with the ones requiring computer to root But does not mean i wont try them at some point. right now this is mostly a Backup phone Just in case i kill my Galaxy s4 (running goldeneye lollipop 5.0.1 rom) other then that have not seen anything New pop up around the net about it still on my todo list tho

2nd update to this. have tryed iroot root master and kingroot pc version best i get is blacked out screen with phone not responding to anything. Almost like a hard brick. pull battery hold power for a few put battery back in then kicks on just fine like nothing happened. but saddly no root havnt tried CF-Autoroot as to well phone not being listed. much less figuring out how to unlock bootloader. (If its even Able to be unlocked)
Tho i have noticed something in dev options. a switch to allow for OEM Unlocking. yet booting into recovery and doing the good old "fastboot oem unlock" just gives me the waiting for device that sits there for the next hour. any takes on this @janekmuric ?

jasperjax said:
2nd update to this. have tryed iroot root master and kingroot pc version best i get is blacked out screen with phone not responding to anything. Almost like a hard brick. pull battery hold power for a few put battery back in then kicks on just fine like nothing happened. but saddly no root havnt tried CF-Autoroot as to well phone not being listed. much less figuring out how to unlock bootloader. (If its even Able to be unlocked)
Tho i have noticed something in dev options. a switch to allow for OEM Unlocking. yet booting into recovery and doing the good old "fastboot oem unlock" just gives me the waiting for device that sits there for the next hour. any takes on this @janekmuric ?
Click to expand...
Click to collapse
Sorry for not posting for 20 days. I've been of xda for a while. Anyways the reason why it's stuck there is because you are trying to run fastboot commands in recovery. You are supposed to run them in fastboot mode.
Just Google "[phone name] how to enter fastboot mode" or try pressing random buttons to boot the phone into fastboot. From there you should be able to run "fastboot oem unlock" (This will erase ALL data).
If it still doesn't work even if you are in fastboot mode then you have incorrectly installed fastboot drivers on your PC. Google is your best friend here.

janekmuric said:
Sorry for not posting for 20 days. I've been of xda for a while. Anyways the reason why it's stuck there is because you are trying to run fastboot commands in recovery. You are supposed to run them in fastboot mode.
Just Google "[phone name] how to enter fastboot mode" or try pressing random buttons to boot the phone into fastboot. From there you should be able to run "fastboot oem unlock" (This will erase ALL data).
If it still doesn't work even if you are in fastboot mode then you have incorrectly installed fastboot drivers on your PC. Google is your best friend here.
Click to expand...
Click to collapse
your fine this has been a slow moving project for me anyway. and yes i know about running fastboot in fastboot mode BUT heres my issue. i have download mode or recovery. thats about it. attempted this in download mode also for giggles and got same thing expected that honestly but worth a shot. from adb have tryed "adb reboot fastboot , adb reboot bootloader" and a few others just to get close to anything that would give me a different screen. as for key combo's nothing has worked. tryed with normal shutoff and turn on and with taking battery out holding power then popping battery back in with no luck. as for googling how to get into fastboot just some info that covers "Most" devices still not a whole lot about this device on how to root it much less anything more. heck half my searching brings up this forum thread as the top item. so this really has me stumped.

jasperjax said:
your fine this has been a slow moving project for me anyway. and yes i know about running fastboot in fastboot mode BUT heres my issue. i have download mode or recovery. thats about it. attempted this in download mode also for giggles and got same thing expected that honestly but worth a shot. from adb have tryed "adb reboot fastboot , adb reboot bootloader" and a few others just to get close to anything that would give me a different screen. as for key combo's nothing has worked. tryed with normal shutoff and turn on and with taking battery out holding power then popping battery back in with no luck. as for googling how to get into fastboot just some info that covers "Most" devices still not a whole lot about this device on how to root it much less anything more. heck half my searching brings up this forum thread as the top item. so this really has me stumped.
Click to expand...
Click to collapse
If your device doesn't have fastboot mode there is no point in trying to do anything with it. Anyways try downloading Poot and rooting with that. It's just an app that you install on your phone. I've tried it on my phones, it never worked, but a lot of people on the internet are saying it worked for them so you should try it.

janekmuric said:
If your device doesn't have fastboot mode there is no point in trying to do anything with it. Anyways try downloading Poot and rooting with that. It's just an app that you install on your phone. I've tried it on my phones, it never worked, but a lot of people on the internet are saying it worked for them so you should try it.
Click to expand...
Click to collapse
yeah poot has never worked for me on any device so far. always get (Ministro can not satisfy your application depedencies) error. just as this time around. but as i have located an "updated" rom for this device (and as i forgot to turn off device last night it took on the update on its own anyway Yay me) i may just try doing some light flashing. with odin at the ready just to be safe.

Anyone figure this out? I have a cricket samsung galaxy amp 2 (SM-J120AZ). I've tried every way possible to root it with no luck. I've tried all the methods above and none of them work for the amp 2.

@imagetrekker Not yet. another device very close to this one is the SM-J120A (Samsung Galaxy Express 3) everything matchs up besides the android version is comes with.(6.0) would think if they root that one this one would be able to be rooted same way or if this one gets rooted first should work on other.

Anyone figure out how to root this phone yet? I have never had a device that can't be rooted one way or another but this one is being really tricky...

I'd like to bump this too! I've tried many methods with no success. Any other options to try?

Bump

Where did you find that SM-J120AZ ROM ?
jasperjax said:
yeah poot has never worked for me on any device so far. always get (Ministro can not satisfy your application depedencies) error. just as this time around. but as i have located an "updated" rom for this device (and as i forgot to turn off device last night it took on the update on its own anyway Yay me) i may just try doing some light flashing. with odin at the ready just to be safe.
Click to expand...
Click to collapse
Hey man, this is very very important. You said you located an updated ROM for the Samsung Galaxy Amp 2 (SM-J120AZ Cricket). I've been searching high and low, so if you could direct me to where you found it, I would so very much appreciate it.

Can't format SD card for internal use
So I guess Samsung have saw fit to disable the ability to format an SD card for internal storage, which means you can't move any apps to the SD card. With the limited memory on this Galaxy Amp2 this makes it near useless!
We need to get root on this so maybe we can fix this...
adb shell sm set-force-adoptable true
Should fix it, but only with root...

sorry had some computer issues shortly after a thunderstorm but im back up and running so Sorry for the very late replys
MuzicSoulWorldly said:
Hey man, this is very very important. You said you located an updated ROM for the Samsung Galaxy Amp 2 (SM-J120AZ Cricket). I've been searching high and low, so if you could direct me to where you found it, I would so very much appreciate it.
Click to expand...
Click to collapse
@MuzicSoulWorldly was actualy able to get it from http://updato.com/firmware-archive-select-model?r=&v=&q=j120az&exact=1
Greywire said:
So I guess Samsung have saw fit to disable the ability to format an SD card for internal storage, which means you can't move any apps to the SD card. With the limited memory on this Galaxy Amp2 this makes it near useless!
We need to get root on this so maybe we can fix this...
adb shell sm set-force-adoptable true
Should fix it, but only with root...
Click to expand...
Click to collapse
@Greywire Not quite you can do it with out root. commands are as this
Code:
adb shell
sm list-disks
sm partition <DISK> private
reboot
<DISK> needs to be replaced with the output of the previous command. For example sm partition disk:179,64 private. That will format the entire SD card and adopt it. Another way would be to use sm partition <DISK> mixed <VALUE> replace <DISK> same as with other way but value would be in a % of disk you want adopted example "sm partition disk:179,64 mixed 50" would make adopt half your sd card.

thanks..
I actually discovered this right after I posted. Hopefully anybody else having this issue will see your posting though for the solution.
Still would be nice to get root on this phone. Any ideas on how to carrier unlock it?

Moto G (falcon) - Recovery img problem

Ok, I've been reading around the forum for about a week, trying to solve a problem with an original moto g (falcon). Basically my cousin got the moto g a few years back, and I, in my ignorance, tried to root the device for him. What I can remember was oem unlocking the bootloader with Motorola's unlock code through their website and adb. then my cousin freaked about the warranty warning on the boot animation, and decided against it. So cut to now, I'm a little more experienced, the phone's years old now, and he'd like to refresh it with a new rom, which I suggested, trying to help him. So forgetting what I'd originally done those years ago, I started the process of rooting the phone, installing a custom recovery, to hopefully put a lighter rom on it for him.
OK so it's a UK Retail on tesco mobile, moto g xt1032 running Android 5.1.
in bootloader menu it says "Device Locked status 2", dunno what this is in relation to.
first I checked the bootloader was still unlocked, and adb said it was. so I tried to use CF-autoroot to finish the job, but there was issues. it restarted the phone into fastboot mode, but when the script started, pc end did nothing, on the phone it said, "flashing unlock" and just sat there for 10-15mins doing nothing (i left it the time, just incase it was doing it).
So i read a little more, and found because i'd already unlocked the bootloader, I could just flash a custom recovery and root from adb? so I downloaded the latest twrp and tried. I was unable to do so. it said the partition wasn't the right size? should have documented it, but really didn't expect to run into any problems.
So I restarted and tried to do my usual fallback, and flash the factory image and start again, But couldn't find a source for the specific img, and tried to keep fighting on.
So I noticed that the phone wouldn't respond to adb or fastboot once in fastboot mode, when in android with usb debugging, no problems, in fastboot, didn't show up as adb devices?
I tried booting into the recovery from the bootloader menu, and got a no command. So there isn't a recovery, and I can't flash a new one? if i could find the stock recovery, I would try that.
so apart from deleting all his apps and settings, I hadn't solved the problem at all, and had to leave the job there as I couldn't find a solution.
I know this isn't the most detailed, but I've done this with quiet a few phones now, and felt I was pretty competent. I see everyday as an excuse to learn more, and like to think I have humility. So, I'm assuming I did something those years ago to damage the recovery? I'm running out of ideas, and was hoping someone could point me in the right direction?
I've lurked on xda for years, and learned so much about this kind of thing through my past experiences, but I'm stumped this time, and feel obliged to resolve the problem, as it was me who caused it.
TL DR
Can't flash recovery, no command when I try to open recovery, trying to either factory image back, or root/custom recovery it.
any insight would be much appreciated.

Hi. I just rooted and installed CM13 on an old XT1034 about two days ago. I am also sort of a ROM noob, I have ROMed a few devices, but usually but following strict step by step guides I have found here on XDA. Over the years I have some minor understanding of the process now.
I also got the "No command screen" when trying to get into TWRP recovery. The issue seems to be that if you reboot via ADB and the ROM launches it will automatically rewrite the recovery to the stock one, and when you try to go to recovery from fastboot, it gives you the "no command" error. Apparently you can get to the stock recovery from there by a hardware key combo, something like holding up vol for 10 sec then a quick press of power (I can't remeber the exact key sequence or what forum I read it in). If it does this you have to reflash TWRP again. This issue is mentioned here (http://wiki.cyanogenmod.org/w/Install_CM_for_falcon) in step 8 about installing recovery. What I ended up doing was after the flash of TWRP via ADB, I manually powered down, then manually bood into fastboot by holding volume down and power, and selecting recovery. This was a bit fiddly and I had to attempt it a few times but eventually it worked and TWRP installed.
The issue with the phone not being recognized may be due to incorrect drivers. I had no issue with this because I installed the official driver package from Motorola. It is available in their website in the developer section. I don't have the URL right now.
Hopefully this helps, for me CM13 Official has been an a stable fresh start for this old device.

Bricked unlocked device

Hello,
I recently unlocked, flashed TWRP and flashed Pixel Experience onto my Mi Mix 2s. After some time a notification of an available update appeared. I tried to install it but it didn't work. After some troubleshooting it appeared that I couldn't get my device booted into TWRP recovery mode.
I tried reflashing it via fastboot but that didn't work. It did not give any errors upon executing the command lines in the fastboot command prompt but just nothing happened. It just sat still like it was waiting, and waiting, and waiting.
So i thought, let's just reset the phone via the normal settings menu in Android. In hindsight that was quite a dumb move I guess, because after all the phone used to be working. But still I followed through and now it wound up in a bootloop. I can still get it into the bootloader mode, and in fastboot it shows my device when I execute <fasboot devices> but flashing or erasing the recovery doesn't work. It looks as if it sees the phone, can get info from it but is not able or allowed to flash anything to it. But it doesn't give any errors, it just seems to keep waiting on something, I don't know.
I hope any of you guys can help me because searching this forum or googling hasn't helped me getting any further. All topics I found at least had some errors in fastboot/bootloader mode which gave them a direction to go into...
So please help me!

Whoops, I solved it myself. On another laptop it magically worked the first time. Probably an issue with either the USB port or the drivers.

Thread closed at OP request

Database Info

welcome