Devic:
XT1032 GPe
Last successful OS: 5.1 one away from the last OTA
I'm having some issues getting my device to work. In my attempts to re-acquire root access, I ran into some roadblocks. Most of the tutorials dealt with earlier versions of Android and I should have been using CF Autoroot from the beginning. Instead I followed various different instructions all without success and messed something up. I think it may have been something to do with using adb shell to remount the system as rw. For some reason though, I've now lost the ability to do adb commands when the phone is in the bootloader, though fastboot still works perfectly fine. (I know it's not a driver issue, because I installed all the drivers in Windows, and also did it in Linux where the drivers are preinstalled) ADB works fine when the phone is booted, and when I temporarily flashed TWRP and Clockwork it worked while booted into either of them.
I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2542219 in order to restore the factory firmware. I did this on both Linux and Windows. When done with Linux I ended up with a bootable system, but still no adb at bootloader and recovery takes me to the dead android. When done with Linux I can access the bootloader, but any attempt to boot the system leaves me stuck at the screen with the Google logo and the icon showing the bootloader is unlocked.
What's my next step here? XDA has always been a supportive community ever since I was flashing Football roms on my old Windows Mobile PDAs and such. If someone can help me sort this out and get a working rooted device I'll make a $10 donation to the EFF or a comparable organization as a thankyou! I'm out of work right now, just my minimally profitable small business, so I don't really want to drop 400-500 bucks on a nice new phone... plus I like my Moto G.
ADB commands never worked in Fastboot mode. Only Fastboot commands work in Fastboot mode. Provide a log of what happens when flashing the firmware image. Copy and paste command prompt / terminal screen. Take screenshots.
Hi everyone. Thanks for your attention
I have a HTC Mini. Today I wasn't able to connect my phone into the wifi. Then, I restarted and afterwards the phone didn't boot at all. It goes only to the bootloader menu. Last two days I was looking for the solution. In the HBOOT menu when I tried to the factory reset it only jumps into the fastboot menu, same thing for the recovery. When I am in the fastboot menu, if I click on reboot, or reboot bootloader it just reboot and the HBOOT menu comes again.
However, my HBOOT menu is locked and when I wanted to try unlock it. following problem happen :
- when I connect the phone to a Mac, Fastboot Devices detect (but only fastboot, ADB devices return nothing) the phone and I could get the token for unlocking procedure, but when I load the the unlock token which sent to me by mail from HTCDEV, nothing happen. it just say everything was successful on Terminal, but nothing shows up on the phone to Confirm unlocking procedure and sometimes it hangs and if I try pushing the token again (the bin file), I receive an error, fail to splash the screen (something like this). However, I already installed the HTC Sync Manager and every other possible driver I could find on the internet.
- When I use windows, after installing HTC Sync and all of the drivers several time, still the command for Fastboot devices or ADB Devices return nothing. I don't care about the phone data or anything. I just want to like Flash the whole operating system and everything . thats fine. But nothing is working properly.
Please guide me if you have any idea about this problem.
Hello,
My friend gave me his locked out phone AppTab Dual talk...( a company name unheard of) and asked me to unlock it for him. He doesn't know his account password. Now I tried booting into recovery or anything. I held power and vol down. Some stuff in Chinese came up. Image attached.
And language barrier apart, only vol down and up buttons work in that to scroll through the options . I've tried everything to try and select an option in that. But no luck!
If I hold down vol up and power buttons, something like a broken Android logo screen comes up which I believe is recovery mode for this device.
Then I plugged it on to my PC and installed the adb drivers for it.
adb devices --> I can see the device listed
Fastboot devices --> I can't see the device
adb reboot bootloader --> the stupid phone just reboots into actual rom instead of bootloader.
I tried to see if the bootloader is locked..now how do I unlock it? fastboot OEM unlock? Damn thing doesn't get recognised in fastboot.
I thought I'll enable USB debugging..which I believe isnt enabled.
So I searched online and came across this command.
adb pull /data/property/persist.sys.usb.config ~/
But the out put of this is either "error: no device" or "permission denied"
I don't know what to do. Here it doesn't go into bootloader. If I want to flash a custom recovery, fastboot commands ain't working, if fastboot shud work I shud enable USB debugging some how, and that too isn't working. If I hold down some random buttons also there is no bootloader mode or anything.
And the options which it gives and which I believe will have the factory reset option also doesn't work bcoz I can't select any option in that.
And yeah...I tried one more thing
adb shell recovery --wipe_data
Which also dint work
I tried
adb shell
Wipe /data
Wipe /system
Wipe /all
I also tried to side load one zip package which could disable the pattern lock
Bt that also dint work.
I tried adb USB and then adb side load <file>
Still no luck.
I might just recommend my friend to throw this phone into the water!
Thanks in advance
I've never heard of that device either and I couldn't find much information here. The adb commands that you tried won't work unless the phone's rooted. You can't access /system or /data or any other nested folders hence the "permission denied." It also looks like the bootloader isn't unlockable since adb reboot bootloader doesn't work. If you just need to unlock the phone you can check this thread but you need to have usb debugging enabled.
Art Vanderlay said:
I've never heard of that device either and I couldn't find much information here. The adb commands that you tried won't work unless the phone's rooted. You can't access /system or /data or any other nested folders hence the "permission denied." It also looks like the bootloader isn't unlockable since adb reboot bootloader doesn't work. If you just need to unlock the phone you can check this thread but you need to have usb debugging enabled.
Click to expand...
Click to collapse
Well, that still keeps me in the loop. I have to enable usb debugging & if i have to do that i have to root & so on.
Thanks for the reply. No luck with the thread you linked either.
I have found an easier to follow way to root the version 5.0 security update, it follows basic logic for rooting with twrp and magisk after the bootloader is unlocked with the boot.img I patched based off of the most recent security update with the help of @tarkus1000
Reboot to the fastboot interface "adb reboot bootloader" or see my youtube video for the keystroke on the unit itself (useful if you break somthing, it happens)
flash the patched boot.img **see link bellow** now you must reboot to system and select the option in settings "allow oem unlocking"
reboot to fastboot using whichever method suits you, just remember this is an old boot-loader so be patient with it as always
1) enter the command "fastboot oem unlock" sometimes it reboots and you know you have success sometimes it says failed... but it is usually unlocked (The more I study this the more I think its a problem with the android 5.1 dalvik heap its interpreter sometimes skips lines of code)
reboot from the fastboot state is required for unlocking so you have to enter the command "fastboot reboot" even if you get the failed command then wait for about 30 seconds for the device to respond if it does not respond reboot using the power button
2) check for the orange state of the bootloader enter command "fastboot getvar all" if you have orange continue to flash the hacked recovery
3)if boot state is green flash the new boot.img again and repeat step 1, remember to be patient and use commands like "fastboot devices"..ect we are working with android lollipop after all
The bootloader is unlocked and you can flash twrp with "fastboot flash recovery (drag and drop .img here)"
Now we enter the hacky recovery by either going to system and "adb reboot recovery" or with fastboot via "fastboot boot (drag and drop .img here)"
Its a little difficult to have the recovery recognize your mouse I had luck with the logitech M100 doing this;
after you hear the device disconnect from your computer (chirp or whatever) plug in the mouse so the device boots up getting input from the mouse
Twrp will tell you it needs a password (will never be able to decrypt your partition no matter what you tell it ) hit cancel and navigate to the backup tile make a backup and include the recovery.img in your nandroid backup
now to root
flash dissable dm-verity/force encrypt (find on xda)
flash magisk (find on xda)
reboot to system. you may have to download magisk manager app to detect magisk and finish the installation
When you have success remember to reboot back to recovery and make a backup before you make any changes to the system or were gonna have to work something out
how to boot into fastboot manually https://youtu.be/766TR5hFEqs
patched v5.0 boot.img [url]https://drive.google.com/open?id=1KDpLxhYBa2Nto9dTaHFOqEKCfs6B1RjV[/URL]
check out the hacked recovery image (you must use mouse) https://drive.google.com/file/d/1fcLoHw0CTAs7qIYZi2xoaAgImVREHz8O/view?usp=sharing
awesome!
alecthenice said:
@amg314 pointed out to me that the most direct way to do this is through adb since any failure could be catastrophic... In the past we used a recovery that almost worked for Moverio Bt300s, I will link it bellow for academic purposes; anyways (fastboot under some situations requires something special...I really wanna know, I think I got it once by holding power and volume down as it booted and plugged into the computer, can't be replicated so idk what happened)
So start tutorial here
"adb devices"
"adb reboot-bootloader"
"fastboot devices"
"fastboot OEM unlock"
......
"fastboot reboot"
.......
"adb reboot-bootloader"
"fastboot devices"
"fastboot format user data" (all user data lost)
"Fastboot update /path_to_zip/DM-verity_force..." Drag and drop "payload" into cmd after space in update
"Fastboot update /path_to_magisk (same deal)
" fastboot reboot"
Like magic your rooted. Sometimes you have to download magisk manager from the aurora store in order to use all the features.
For this install you need a working adb environment
the latest Intel drivers
dm-verity dissable.zip
Magisk.zip
I believe this to be the cleanest safest way to achieve root (no zombie recovery.img) even though that recovery may be fine I'm cautious to use it more than I did. Anyways. I recommended this. I'll also advise on installing a google ecosystem without twrp if y'all would like. It would be great to grow this device's community
Now that we are rooted though we can combine our boot.img and stick recovery and make a twrp...I'll probably set that aside for another day since I don't have an immediate need for it (unless some genius makes a ROM)
check out the hacked recovery image (you must use mouse) https://drive.google.com/file/d/1fcLoHw0CTAs7qIYZi2xoaAgImVREHz8O/view?usp=sharing
Click to expand...
Click to collapse
Alec!!! You are a GOD in my eyes. I'll give this a go this weekend and report back.
chuck1026 said:
Alec!!! You are a GOD in my eyes. I'll give this a go this weekend and report back.
Click to expand...
Click to collapse
Not to shoot my own post in the foot here but we can install virtual xposed installer and then microg through an included module all without touching our computers. Have fun though guys hahaha I love finding work a-rounds.
https://forum.xda-developers.com/xposed/virtualxposed-xposed-root-unlock-t3760313/page39
^^^^This is pretty much cutting edge android software development so use this as a way to create the right environment on an app by app basis (no root or unlocked boot loader required) kids have been using this to cheat on mobile android games since they dont know how to root. this works for us because we want gapps and there is no hardware command for fastboot mode. be advised my root method still works if you are not intimidated by Epsons' annoying attempt to keep their hardware stock also if you mess up I was informed you are still covered under warranty for "damaged operating system" as if they know its buggy and annoying to work on
google services independent google.map.apk
Use this apk for an easy way to use google maps without google services (less background precessing=more flying) https://drive.google.com/file/d/1GqTrR27gpYXeRl-XtHPbojIwbg89X-9i/view?usp=drivesdk
(No root required)
bricked, thinking about warranty
So I downloaded the nanodroid MicroG installer from the magisk manager (I flashed gapps and google wouldn't whitelist the device ID so I went to microG) and it caused my device to boot loop. It seems my adb key was changed in my device as a result of the install. I don't think this device is worth having root access anymore since i only wanted google services. I do have a usable twrp but the device won't boot to it by default upon boot loop recognition. If I could find a way to tell the device to boot to twrp upon issues (some phones automatically go to recovery upon this situation) I could continue to find ways to make the device more useful. At this point the device responds to adb as (embt3c offline) thoes tricky guys locked me out of fastboot too. Upon boot loop it seems you can get to fastboot only once by repeating the same button inputs you would to get into recovery in the powered off state. Please offer any ideas you may have. Perhaps there is a way we can model the android environment the bt300s operate under with the SDK in order to test our mods? I want to continue but the lack of a button combination to get to recovery just kills me. I hope an engineer of some sort will offer me some guidance on how to proceed. I have seen references of a test plug in order to supply the correct voltage to the chip to trigger fastboot mode but at this point we might as well be hacking with JTAG? I have a small research budget... A spare unit may help development quite a bit. I believe I will use my warranty on this unit so i can continue to enjoy my drone but this is where I stand with this unit. I look forward to insight from the community.
transitioning from script kiddie to developer
So I decided I'm going to learn how to build what we need on this device.
We need
-more test pin info for the hardware fastboot mode (I can build but I'm not good with theory I need help here)
-I'm working on building a virtual moverio bt300. Some guides would be useful. I'm using the android development studio so I can test modules before I brick my device. These babies are too cool for my to resist really. I also downloaded droid explorer in hopes of manually uninstalling the magisk module that bricked my all time favorite waste of time.
-update exactly 24hrs from last time I was able to get into fastboot I was able to get in by holding power and volume down for 10 seconds. I was not able to replicate. Will try again in 24hrs. The device responded to my commands but did not carry them out
recovery mode
We need to find out how to manually put the device into recovery mode. I'm really frustrated this high end "developer" device is so hard to work on. Does anyone know how to do this with code? Idk where to even start my research
Fastboot mode and recovery fix
Hold volume down and power
When green light comes on click volume down while holding power and hold
After first vibration click volume down
Fastboot mode
Repair
My moverio Firmware (FULL ROM) v4.0
Here is a copy of the firmware I am running on my device right now https://drive.google.com/file/d/1xZx6xuubQ-P58LL_-vcuCjPkx-hPTk_v/view?usp=sharing
This is the stock recovery
https://drive.google.com/file/d/1uOofDprPNw4Dqy-euyQwpW3A0LWEZLpy/view?usp=sharing
Stock system
https://drive.google.com/file/d/1f3Xcr4gdKAkG_kiARB3NmEYyjPi41pxA/view?usp=sharing
Twrp prototype (use a mouse that supports linux)
https://drive.google.com/file/d/1fcLoHw0CTAs7qIYZi2xoaAgImVREHz8O/view?usp=sharing
alecthenice said:
Here is a copy of the firmware I am running on my device right now https://drive.google.com/file/d/1xZx6xuubQ-P58LL_-vcuCjPkx-hPTk_v/view?usp=sharing
This is the stock recovery
https://drive.google.com/file/d/1uOofDprPNw4Dqy-euyQwpW3A0LWEZLpy/view?usp=sharing
Stock system
https://drive.google.com/file/d/1f3Xcr4gdKAkG_kiARB3NmEYyjPi41pxA/view?usp=sharing
Twrp prototype (use a mouse that supports linux)
https://drive.google.com/file/d/1fcLoHw0CTAs7qIYZi2xoaAgImVREHz8O/view?usp=sharing
Click to expand...
Click to collapse
Alec, I have to commend you on what you have accomplished with the Bt-300's. Kudos Sir! Keep up the excellent work. :good: We have posted this thread in our facebook group so that all can benefit. If you haven't checked us out, please feel free. You probably have rock star status by now. lol. https://www.facebook.com/groups/269299563510341/
Thanks and Happy New Year!
dvegaman said:
Alec, I have to commend you on what you have accomplished with the Bt-300's. Kudos Sir! Keep up the excellent work. :good: We have posted this thread in our facebook group so that all can benefit. If you haven't checked us out, please feel free. You probably have rock star status by now. lol. https://www.facebook.com/groups/269299563510341/
Thanks and Happy New Year!
Click to expand...
Click to collapse
Thank you for the accolades I am flattered! As for development progress I am trying to figure out what google maps APIs are called upon in the "NLD DJI go 4.22" app developed by the No Limits Drones group. I need this information to know how to patch the system apks and apply the correct form of microG package (basically for google apps and related). On the topic of facebook I have yet to create one but am evaluating cost/benifit on an ongoing basis and will join your community if i do ever make one! I look forward to colaborating on the bt300s now that another creative avenue is unlocked with root access to this cool gadget. Happy new year!
Awesome work!
But I need help, because I am stuck.
I tried different ways with the on and down buttons, but it seems I am doing something wrong.
Everytime the Bt300 boots up normally.
I tried the adb reboot-bootloader, it restarts immediately, but then it`s getting stuck in a
Moverio Boot screen, with the note below "Is now under process"....!?!?! and nothing happens anymore, even after 5minutes it is stuck.
Also it isn`t shown in fastboot devices, just nothing there.
So it seems I can`t get into fastboot by adb command nor manually with the buttons.
ADB Debugging and untrusted sources are enabled, not my first device I try to root, did this on a couple of phones already and are familiar with the process.
But fastboot and the Moverio BT-300 seem to be special.
I tried it now more then 10 times and any hint or advise is greatly appreciated.
My Moverio has the 1.5.0 Firmware installed.
guili2 said:
Awesome work!
But I need help, because I am stuck.
I tried different ways with the on and down buttons, but it seems I am doing something wrong.
Everytime the Bt300 boots up normally.
I tried the adb reboot-bootloader, it restarts immediately, but then it`s getting stuck in a
Moverio Boot screen, with the note below "Is now under process"....!?!?! and nothing happens anymore, even after 5minutes it is stuck.
Also it isn`t shown in fastboot devices, just nothing there.
So it seems I can`t get into fastboot by adb command nor manually with the buttons.
ADB Debugging and untrusted sources are enabled, not my first device I try to root, did this on a couple of phones already and are familiar with the process.
But fastboot and the Moverio BT-300 seem to be special.
I tried it now more then 10 times and any hint or advise is greatly appreciated.
My Moverio has the 1.5.0 Firmware installed.
Click to expand...
Click to collapse
That "moverio is now under processes" screen is your fast boot interface. You should be able to adb pull any .img you need after you pull the boot.img, patch with magisk manager and flash patched_boot.img. Remember the twrp recovery image requires a linux compatable mouse. (You can get "adb su" with twrp recovery if needed) Lemme know if you have any other questions, epson didnt do the cleanest job of with their android implementation most likely for proprietary purposes, we expect better from the parent company Seiko. Have fun.
Yes thanks!
Figured this out in the same second.
I was under the impression that the intel usb/adb driver was already installed, but it wasn`t...
So now I can see it with fastboot devices
Got now the "too many links" message but I follow the guide, this was already explained.
Thanks!
---------- Post added at 02:30 AM ---------- Previous post was at 02:11 AM ----------
Ah now, I need your help/advise.
I need this android-help.text file, which need to be included into the DM-verity_force.zip
guili2 said:
Yes thanks!
Figured this out in the same second.
I was under the impression that the intel usb/adb driver was already installed, but it wasn`t...
So now I can see it with fastboot devices
Got now the "too many links" message but I follow the guide, this was already explained.
Thanks!
---------- Post added at 02:30 AM ---------- Previous post was at 02:11 AM ----------
Ah now, I need your help/advise.
I need this android-help.text file, which need to be included into the DM-verity_force.zip
Click to expand...
Click to collapse
Set the path according to this https://stackoverflow.com/questions/5846197/error-could-not-load-android-info-txt
Dont have android-info.txt? Ill track it down for you within the day. I got it from the original bt300 thread somewhere.
Flashing zips through Bt300 hacked recovery has been tested and is the easiest way to accomplish customization at this point. Please use caution to chose the hacked recovery rather than 4.0 stock. Check your work with "fastboot getvar all" as always.
-cheers
An update on how to manually boot to fastboot "incase you have issues"
Hold power and volume down button while device is powered off
You will feel a vibration and see the epson logo. In this same moment release volume down
Quickly press volume down again (hold power the whole time) and you will be brought to the "moverio is now under processes screen"
Here you will be able to flash/boot to the prototype recovery to rescue yourself.
****prototype is safe you just have to use mouse*****
It is possible to root this device classically with twrp and magisk as a flashable zip. Remember the order is DM-verity dissable, then Magisk.
prototype TWRP cannot decrypt the userdata partition so make sure you act accordingly
alecthenice said:
@amg314 pointed out to me that the most direct way to do this is through adb since any failure could be catastrophic... In the past we used a recovery that almost worked for Moverio Bt300s, I will link it bellow for academic purposes; anyways (fastboot under some situations requires something special...I really wanna know, I think I got it once by holding power and volume down as it booted and plugged into the computer, can't be replicated so idk what happened)
So start tutorial here
"adb devices"
"adb reboot-bootloader"
"fastboot devices"
"fastboot OEM unlock"
......
"fastboot reboot"
.......
"adb reboot-bootloader"
"fastboot devices"
"fastboot format user data" (all user data lost)
"Fastboot update /path_to_zip/DM-verity_force..." Drag and drop "payload" into cmd after space in update
"Fastboot update /path_to_magisk (same deal)
" fastboot reboot"
Like magic your rooted. Sometimes you have to download magisk manager from the aurora store in order to use all the features.
For this install you need a working adb environment
the latest Intel drivers
dm-verity dissable.zip
Magisk.zip
I believe this to be the cleanest safest way to achieve root (no zombie recovery.img) even though that recovery may be fine I'm cautious to use it more than I did. Anyways. I recommended this. I'll also advise on installing a google ecosystem without twrp if y'all would like. It would be great to grow this device's community
Now that we are rooted though we can combine our boot.img and stick recovery and make a twrp...I'll probably set that aside for another day since I don't have an immediate need for it (unless some genius makes a ROM)
check out the hacked recovery image (you must use mouse) https://drive.google.com/file/d/1fcLoHw0CTAs7qIYZi2xoaAgImVREHz8O/view?usp=sharing
Click to expand...
Click to collapse
Flashing zips through the prototype recovery is now the easiest way to make your A/R goggles custom. Im glad I initially did it the old school way for the sake of understanding epson file systems. This twrp works traditionally and has all partitions correct!!!
Bootloader unlock problem with v5.0
It has come to my attention that there is a problem with the bootloader unlock command for version 5.0 firmware
to solve this please boot this boot.img
use the command "fastboot boot boot.img"
****note the command "fastboot flash boot boot.img" may cause issues****
after you boot this boot.img
"fastboot oem unlock"
disregard the response. enter this command after to check your unlock status
"fastboot getvar all"
you should be in the orange state and this will be persistent upon the next reboot
DOWNLOADhttps://drive.google.com/file/d/1_2qwuL85SkirnEu7bHLRigBWrJlPnYXj/view?usp=sharing
Correct getvar all response[/B]https://drive.google.com/file/d/0BzLMyqznaCbVVnFXQ2NqNnppXzg4LVQ0ajNmMmU2c2hjTktJ/view?usp=sharing
Does anyone know where the ota updates are stored on this device? I will pull the updated boot.img and patch accordingly so the bootloader unlock is more simple if i can find the ota...OGs in the original hacking forum have fell silent on this, furthermore it seems that the epson file systems team only wants to utilize my input for their own development so I have stopped communications with the contact I had.
I can post a full nandroid backup on here if others would like to revert to software 4.0
Hello. I wont lie.... im very frustrated. Its hard to find straight forward instructions.
I'm using linux ububtu. Ive also tried FWUL and mAid
Sdk tools installed, tried androud and google sdk
I have enabled oem unlock from the developer settings menu, along with usb debugging. file transfer mode is recognized as mtp.
I tried exalab's non-root busybox for some functions. Superuser x from k shark apps. I get bad system call.
I can only adb sideload and adb shell from pc. i cannot access anything else!
The most annoying part? When the sideload fails, it takes me into recovery mode, but adb doesnt work there!!! I have options like erase cache, reboot to bootloader, and mount /system (which mounts) but useless because i cant adb pull the build.prop file to change ro.secure 1 , ro.adb.secure 1, and ro.flash.locked 1.
Through getprop, i found the oem key but fastboot doesnt recognize anything at all.
I inspected the init.rc file Just to try and understand.
Adb setprop doesnt work.
How do i allow adb in recovery mode, or modify these syrstem properties? yes, manually and the ultra hard way. Even though im annoyed about it i want and love to learn.
edit: power, vol + and - at boot brings up a white screen saying 'device information' with the imei and s/n #'s with barcodes.
power with vol - to reboot, then at logo: release power and hold again : brings up factory reset screen with yes/no option (not recovery screen).
I cant figure anything else out
I opened up 2 androids now and i notice some pins, maybe for a debug mode? Forced bootloader ?
oliverbell760 said:
Hello. I wont lie.... im very frustrated. Its hard to find straight forward instructions.
I'm using linux ububtu. Ive also tried FWUL and mAid
Sdk tools installed, tried androud and google sdk
I have enabled oem unlock from the developer settings menu, along with usb debugging. file transfer mode is recognized as mtp.
I tried exalab's non-root busybox for some functions. Superuser x from k shark apps. I get bad system call.
I can only adb sideload and adb shell from pc. i cannot access anything else!
The most annoying part? When the sideload fails, it takes me into recovery mode, but adb doesnt work there!!! I have options like erase cache, reboot to bootloader, and mount /system (which mounts) but useless because i cant adb pull the build.prop file to change ro.secure 1 , ro.adb.secure 1, and ro.flash.locked 1.
Through getprop, i found the oem key but fastboot doesnt recognize anything at all.
I inspected the init.rc file Just to try and understand.
Adb setprop doesnt work.
How do i allow adb in recovery mode, or modify these syrstem properties? yes, manually and the ultra hard way. Even though im annoyed about it i want and love to learn.
edit: power, vol + and - at boot brings up a white screen saying 'device information' with the imei and s/n #'s with barcodes.
power with vol - to reboot, then at logo: release power and hold again : brings up factory reset screen with yes/no option (not recovery screen).
I cant figure anything else out
I opened up 2 androids now and i notice some pins, maybe for a debug mode? Forced bootloader ?
Click to expand...
Click to collapse
Can you help me root my lg journey the same way you did pls ?
You can't fix it the LG L322L CAN NOT be unbootlocked or rooted especially StraightTalk, tracphone or t-moble phones. ANYONE WHO CLAIMS THEY CAN OR HAVE IS A BOLD FACE LIAR!
IF YOU visit lg's website the K30 LG L322L is NOT on the list of devices that can be unlocked they have been houndreds of people tried in the last 4 years and not one has successfully done so
It's sounds like you soft bricked it and their is not a fix for it.. sorry but best of luck!
MountainMan42 said:
You can't fix it the LG L322L CAN NOT be unbootlocked or rooted especially StraightTalk, tracphone or t-moble phones. ANYONE WHO CLAIMS THEY CAN OR HAVE IS A BOLD FACE LIAR!
IF YOU visit lg's website the K30 LG L322L is NOT on the list of devices that can be unlocked they have been houndreds of people tried in the last 4 years and not one has successfully done so
It's sounds like you soft bricked it and their is not a fix for it.. sorry but best of luck!
Click to expand...
Click to collapse
Ah, I see.
I didnt mean the phone doesnt work, actually, it works just fine....my bad. just the adb/fastboot/root attempts didnt work.
if only i could modify those system service variables somehow. .. or even access the /system after mount?
getting access to adb via recovery? i had thoughts that if adb isnt shown via recovery, it isnt implemented there but can be done...
i havent tried since, been playing with my solder tools xd.
oliverbell760 said:
Ah, I see.
I didnt mean the phone doesnt work, actually, it works just fine....my bad. just the adb/fastboot/root attempts didnt work.
if only i could modify those system service variables somehow. .. or even access the /system after mount?
getting access to adb via recovery? i had thoughts that if adb isnt shown via recovery, it isnt implemented there but can be done...
i havent tried since, been playing with my solder tools xd.
Click to expand...
Click to collapse
oliverbell760: Do you STILL have the LG Journey phone??
I just came across your post here , while investigating this secon-hand phone ,the lgl322dl . I picked it up right after my LAST economy LG phone lgl355dl ,2022 model running Android 10 slipped into a bootloop.
I have found some very interesting "root-like" methods of running Linux distros "natively" along side of Android.
Please get in touch with me if you care to
expand on your 19-month old concern.
Also reach me at [email protected]